Error for circular dependency is not clear

When a circular dependency occurs the call stack blows up, and provides no meaningful error.
Need a way to short-circuit the loop, fail, and provide fix instructions.

I created a small debug util that I use to spot the error, I used a lot simpler way to create the graph — but it might be a way that is not suitable for yarn.build.
I am gonna push it on git later today and share it with you.

https://github.com/lodmfjord/yarn.build.debug

(the UI is quite similar to the build query … but this is a lot smaller code and just for debugging at the moment :)
I am not sure if this solution might be helpful.  This solution has already saved time even though it is just a hack.
Instead of travelling every package and then recursively following every deps, I only visit every package in the project once. Thus I do not have loop problems but enough information to create a dependency tree.
This solution seems too simple, so I guess it might not be perfect, but I am just putting this here to start a discussion.
The drawback I see right away is that in a big project, graph-class visits every package, even when only building a small package, but the graph could be cached in the future (?).

If we can catch or deliberately check for a circular dependency, and then show a visual of what is causing it, that would go a long way to solving this.

The drawback I see right away is that in a big project, graph-class visits every package, even when only building a small package, but the graph could be cached in the future (?).

I think the issue probably is somewhere in the code this is happening, but not catching the circular dependency. I'm certain there's some optimisation's that can be done to the traversal algo. There's likely plenty of prior art on this I need to dig into.

Ahh you made me and my team happy @ojkelly.
Thanks again!


Feat: Endpoint to export Archive

This PR introduces a new endpoint to download archive entities for specific partner.
Depends on #263

moved to draft until go from sec stream.


fix(discovery): add state_class to kwh sensors

Add missing state_class attribute required for HA and energy statistics/dashboard

Fixes #2943

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 23.792%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/Constants.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
3791

Relevant Lines:
16837

💛  - Coveralls


Multiple ways to express like / ilike / not like / not ilike

Describe the bug
There  are two ways to express pattern matching in datafusion Exprs.
Expr::Like(Like)
..

https://github.com/apache/arrow-datafusion/blob/3abbffb5c83395e8e6e68e5529835e72e7769d0d/datafusion/expr/src/operator.rs#L55-L61
As well as
BinaryExpr {
 left: ..
 op: Operator::Like,
 right: ..
}

This causes issues such as the simplification in https://github.com/apache/arrow-datafusion/pull/4646 only affects the BinaryExpr form, not the Expr::Like form
The Expr::Like form is more full featured (can have pattern substitution)
Expected behavior
I would like to have a single way to represent these operators. I believe it should be Expr::Like, Expr::ILike, Expr::NotLike and Expr::NotILike as they have more features.
Thus, I would like to remove Operator::Like, Operator::ILike, Operator::NotLike, and Operator::NotILike and update all tests / code to use Expr::Like
Additional context
Noticed while reviewing  https://github.com/apache/arrow-datafusion/pull/4646  from @crepererum
I am marking this as "good first issue" as it is mostly a software engineering exercise and would be guided by the compiler -- it would be a good exercise to get familiar with DataFusion's codebase

Note that the expression variant supports specifying escape characters (as the SQL does) but the binary expression doesn't support options / a third input (its binary after all) and the arrow kernels don't support escape characters at the moment.


Helpful error message when undefined passed as cookie name

Hey there,
Totally an unnecessary nice-to-have, but right now TypeError: Cannot read property 'replace' of undefined is thrown from within the library if undefined is passed as the name.
Not too hard to be debug but would be awesome to instead see "Cannot set cookie with blank name" or something like that.
No worries either way; thanks for a great library!
Cheers,
Alex

Thanks for your feedback Alex!
Adding input validation seems like a fair request, could do something like:
  // Input validation
  if (!(typeof name == "string" || name instanceof String)) {
    throw 'cookie name is not a string'
  }
  if (!name) {
    throw 'cookie name is empty'
  }
  if (!(typeof value == "string" || value instanceof String)) {
    throw 'cookie value is not a string'
  }

Adding the input validation listed above increases the (minified and gzipped) size of browser-cookies by 73 bytes to 596 bytes. Not a large increase in absolute terms, though given the goal of being a tiny cookies library the size increase is important to take into account nevertheless.
If input validation is not a must-have or should-have I would prefer not add the functionality to keep the file size low, is this acceptable for you?

Hi there! Thanks so much for your thoughtful response! I think that looks like a great solution though I can't speak to the tradeoff -- I certainly appreciate how small the library is, but wouldn't mind the extra 70 bytes or so. I'd leave it up to others or yourself as to what the best way to go is.
Maybe something smaller like if (!(name && typeof name === 'string')) throw 'Cookie name must be nonblank string' could help. But really up to you :-)

I will look into adding the input validation.
As for the file size I didn't manage to get it any smaller:

All unnecessary syntax and white space is removed by minifying
Combining the two errors for the cookie name actually increased the gzipped size (due to gzip de-duplication)
The check on whether the variable is of the type string needs to unfortunately use both typeof and instanceof because strings can also be created as object:

typeof 'cookie name here' === 'string' // true
'cookie name here' instanceof String // false

typeof new String('cookie name here') === 'string' // false
new String('cookie name here') instanceof String // true

To keep the file size in check I won't add any input validation on the options (cookie path, date, etc) for now.
A disadvantage on checking for string type is that it may break existing client code, for example it's currently possible to use a number as cookie name. Perhaps the next release should be numbered 2.0.0 or 1.1.0 instead of 1.0.9 to warn users against the API being enforced more strictly?

Wow, nice!
I'm not sure what the right call there is then. If numbers work as cookie names they certainly shouldn't be invalidated.
Perhaps leaving it without the validation is fine; after all, googling the error will now hopefully lead to this github issue.

True, I'll leave the validation out then.
Thank you @rattrayalex for your help.


How do I access the documentation to know the implemented methods and variables of  tdlib?

I want to build a basic android app for testing purposes and I am not able to access the documentation as the pages are unresponsive and not loading.
Please help as there are very few sources to learn this for android and if you know please share some.

I go to the javadoc folder in tdlib and open index.html, works normally
but honestly i don't really find the methods descriptions very useful sometimes

@levlam In the Java Example while creating a client we run the following code :
`
// disable TDLib log
Client.execute(new TdApi.SetLogVerbosityLevel(0));
if (Client.execute(new TdApi.SetLogStream(new TdApi.LogStreamFile("tdlib.log", 1 << 27))) instanceof TdApi.Error) {
throw new IOError(new IOException("Write access to the current directory is required"));
    }

`
Even though I have provided read and write permissions it is still throwing the IOError "Write access to the current directory is required".
I am really new to this. Please Help.


PortAudio library not found

When launching computerassistant, I get this error :
Traceback (most recent call last):
  File "/home/molives/.local/bin/computerassistant", line 8, in <module>
    sys.exit(start())
  File "/home/molives/.local/lib/python3.10/site-packages/gpt_computer_assistant/start.py", line 19, in start
    from .gpt_computer_assistant import QApplication, MainWindow, sys
  File "/home/molives/.local/lib/python3.10/site-packages/gpt_computer_assistant/gpt_computer_assistant.py", line 8, in <module>
    from .gui.button import *
  File "/home/molives/.local/lib/python3.10/site-packages/gpt_computer_assistant/gui/button.py", line 4, in <module>
    from ..audio.record import *
  File "/home/molives/.local/lib/python3.10/site-packages/gpt_computer_assistant/audio/__init__.py", line 1, in <module>
    from .record import *
  File "/home/molives/.local/lib/python3.10/site-packages/gpt_computer_assistant/audio/record.py", line 4, in <module>
    import sounddevice as sd
  File "/home/molives/.local/lib/python3.10/site-packages/sounddevice.py", line 71, in <module>
    raise OSError('PortAudio library not found')
OSError: PortAudio library not found

I fixed it by installing the libportaudio2 package in Ubuntu 22.04.
I think it would be a good idea to either install it from pip (I don't even know if this is possible) or to list it as a necessary package for Ubuntu.

I followed the above steps and I'm still getting the same errors.

I am on windows and I get this error when I try running my game which uses sounddevice and pyaudio I think:
Traceback (most recent call last):
File "sounddevice", line 71, in
OSError: PortAudio library not found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main", line 5, in
File "importlib._bootstrap", line 1027, in _find_and_load
File "importlib._bootstrap", line 1006, in _find_and_load_unlocked
File "importlib._bootstrap", line 688, in _load_unlocked
File "importlib._bootstrap", line 856, in exec_module
File "screenrec", line 5, in
File "importlib._bootstrap", line 1027, in _find_and_load
File "importlib._bootstrap", line 1006, in _find_and_load_unlocked
File "importlib._bootstrap", line 688, in _load_unlocked
File "importlib._bootstrap", line 856, in exec_module
File "sounddevice", line 85, in
StopIteration
I am using build_apps with panda3d and I have a portaudio_x64 but I'm not sure where to put it.

Sorry for the late reply. We will have a new version soon


[Feat]hover effect on 2nd card is not proper

Description
i will add hover effect on the 2nd card which is not properly alligned and the size is it up and down
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[ ] I am willing to work on this issue (optional)

@beRajeevKumar plz assign me this


ConnectException on https://api.github.com/emojis

Hi all,
After a fresh install on a server with no internet access I have the following error on the dashboard page.

Is it mandatory to load emojis ? could I use a proxy with cachet to use github api?
thanks

If you don't have Internet support on your status page, you can edit config/app.php and remove the:
'AltThree\Emoji\EmojiServiceProvider',

Line 152.

Remember to run the config clear command too, and you should be sorted.


Integrate some of the lessons/wording from other CoCs

For example, I really appreciate how concise the one from EA Global is.

@kern I don't think it has enough coverage.

It just says don't harass people, basically.

I'd rather have something lean + appendix so I don't have to keep typing people things over and over.
Also that leaner CoC ignores HH nuances such as hiring, buy/sell, posting private information, and the reversals.

What other Code of Conducts have we seen that we like?

@evaz mentioned Snapchat's Code of Conduct was recommended at one point, I think.

I think ours is pretty good now. :)


Safari 9: Component doesn't work

Clipboard.js relies on execCommand, which is not supported in Safari 9 - see https://clipboardjs.com/ - should consider alternative implementation, or use of feature detection on our demo pages? May be mitigated by the fact that Safari 11 will be out soon and we will be able to drop support for Safari 9.

With release of Safari 11 last month, we only need to support Safari 10 & 11.


does cython support inheritance only from python class？ Even more， multiple inheritance only from python classes? [ENH]

example for inheritance only from python class:
Like: cdef class mydict(OrderedDict):
example for multiple inheritance only from python classes:
Like: cdef class myReader(Readable, Seekable):

No. Cython doesn't support this.
Please ask support questions to the Cython-users group and not the bug tracker


Union-type data in Numba

Currently, union-type data can pass through Numba, but it can't be operated on (__getitem__). This is a particularly hard problem because Numba has no dynamic types (unlike C++, which at least has runtime polymorphism/virtual methods). It could be represented by a new ArrayView that holds multiple possibilities, some MultiArrayView, and it can raise exceptions at runtime if the tag is inappropriate for any one of those views. However, the view that does not raise an exception, which ultimately resolves to a number, has MultiArrayView type in Numba but must satisfy all the operations of a number. "All the operations of a number" is an extremely wide-open set—this is the hard part, figuring out how to make a new type that satisfies everything a number satisfies.
We might need help from Numba experts on this one.

Old references to this same issue: #85 (first consideration) and #95 (was going to include UnionArray, but I saw how hard that would be).

I don't think it would be possible.


add recordSeparatorForInput

add recordSeparatorForInput

i add field recordSeparatorForInput:Character for input file  split line

Coverage decreased (-0.5%) to 92.528% when pulling d6ff3237bab161522f6473e48271aec60d6d360b on wawzw123:master into a7757849d3e9b2a37967ce208ab22f6d14567c98 on apache:master.

Coverage decreased (-0.5%) to 92.528% when pulling d6ff3237bab161522f6473e48271aec60d6d360b on wawzw123:master into a7757849d3e9b2a37967ce208ab22f6d14567c98 on apache:master.


"No Pip installer" when ancestor folder contains poetry

Type: Bug
In /foo poetry init
In /foo/bar create a .venv and x.ipynb
Open x.ipynb, select our .venv/bin/python
Execute a cell (e.g 1+1) and VSCode dialog-prompts to install ipykernel
However, it's getting tangled with the /foo/poetry stuff.
The dialog-prompt says "Running cells with 'Python 3.10.0 ('.venv': poetry)' requires ipykernel package."
And clicking 'ok' gives "There is no Pip installer available in the selected environment (Source: Jupyter (Extension)" error.
So VSCode's not applying pip install ipykernel to the selected Python.
Extension version: 2022.9.1002791758
VS Code version: Code 1.72.0 (64bbfbf67ada9953918d72e1df2f4d8e537d340e, 2022-10-04T23:21:58.256Z)
OS version: Darwin x64 21.5.0
Modes:
Sandboxed: No

In case anyone has gotten stuck with this, as a workaround that we can . .venv/bin/activate and pip install ipykernel.

@p-i-
I'm sorry for not getting back to you on this issue. Please could you confirm this is still and issue with the latest vsocde insiders and latest pre-release versions of the Jupyter and Python extensions.

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.

This is still an issue for me with vscode 1.81.0 (July 2023 update).
I'm starting to migrate projects to poetry, and I cannot launch a notebook in a poetry project for the first time as the automatic jupyter installation fails.


add missing/ remove non-existing functions from Modules section in readme

https://github.com/cieslarmichal/faker-cxx?tab=readme-ov-file#-modules
cleanup, add new functions if some were added to specific module and remove non existing

if possible assign this to me. i promise to complete it asap

Assigned

Sure


feat: add plugin for Backblaze B2 CLI

Overview
Add plugin for Backblaze B2 CLI
Type of change

[x] Created a new plugin
[ ] Improved an existing plugin
[ ] Fixed a bug in an existing plugin
[ ] Improved contributor utilities or experience

How To Test

Sign up for Backblaze Cloud Storage (free tier available)
Create application key in Backblaze Cloud Storage portal
op plugin init b2
b2 list-buckets etc.

Changelog
Authenticate the Backblaze B2 CLI using Touch ID and other unlock options with 1Password Shell Plugins.

At last minute (and after having created this to explore 1Password CLI plugins), I realise this plugin will not make sense. It does work, but the b2 cli always loads the credentials into a local sqlite file so credentials will stay on disk.
https://b2-command-line-tool.readthedocs.io/en/master/

This program caches authentication-related and other data in a local SQLite database. The location of this database is determined in the following way:
If profile arg is provided: * XDG_CONFIG_HOME/b2/db-.sqlite, if XDG_CONFIG_HOME env var is set * ~/.b2db-{profile}.sqlite

I wanted to open this pull request anyway, as I have the code, in case they change that behaviour later, or if someone else looks for existing issues why B2 CLI is not included.
I don't think this should be merged.
I'll leave it open in case you have experience with other applications with similar behaviour, otherwise best close this and leave it for others to find later.

I tested setting environment variable where the account info is written to /dev/null and it didn’t work. Also setting to :memory: didn’t work.
I think options are to set it to a non-disk backed storage such as tmpfs or to implement non-persistent credentials handling upstream. I’m not sure if tmpfs approach is portable or the performance overhead, e.g. unnecessary API calls cost.

Thank you for taking the time to do so much research on this! We have 2 main goals for shell-plugins: increase security for CLIs, and make it more convenient. You make a valid point that with the credentials getting written to disk, we're not adding to the security, but I would argue that we are adding convenience, so this might not be as much of a write-off as you think. That being said, we are still having internal discussions regarding how to approach this use case, do you think the added convenience here would still make it a worthwhile plugin for you, personally? (purely an opinion question)

In my opinion, the convenience is minor and the surprise is large.

I agree with @joneskoo, this is not a road we wish to take.

I tested setting environment variable where the account info is written to /dev/null and it didn’t work. Also setting to :memory: didn’t work.

These sound promising in this specific case. Are these officially documented somewhere? If these don't work because of a bug it could be worth keeping this PR around until those get solved and then taking this approach.

I think options are to set it to a non-disk backed storage such as tmpfs

Indeed, theoretically this could work pretty nicely for our use case. We'll need to do some research on this, but thanks for the hint!

I tested setting environment variable where the account info is written to /dev/null and it didn’t work. Also setting to :memory: didn’t work.

These sound promising in this specific case. Are these officially documented somewhere?

No, not as fas as I know.

Closing for now - if the referenced bug gets fixed we can look at re-opening it in the future.


Searches are slow

Particularly drug-based searches.

part of #149

Believe this was addressed with PR #190.


replace ADD by COPY in Dockerfile

ADD does not copy the directory properly not letting the container to run, COPY fixes it.

By following the exact instructions from the tutorial at this URL: http://testdriven.io/part-one-docker-config/
I could not run the application due to this error: python: can't open file 'manage.py': [Errno 2] No such file or directory

ADD is an extension of COPY:
https://github.com/moby/moby/blob/670c8696a29825b23208496bd4d8e88b5faa7773/builder/dispatchers.go#L77
Strange that it doesn't work.

Also, by using COPY, you will have a problem in part 2 when I change the build context to a remote URL. I'm going to close this.


Simplify persist

For func, and also for perframe and func_ease. perframe and func_ease are slightly different.
New Behavior
persist=
When true (default), the function will always be called.
When false, the function will only be called if at least one frame has happened before beat.
When its a number, the function will only be called if at least one frame has happened before beat + persist.
(The function is always guaranteed to run in gameplay, but will be skipped in the editor if the part being played is more than persist away from the func)
Current Behavior
When true (default), the function will always be called.
When false, the function will only be called when a frame happens between beat and beat + 0.5.
When its a number, the function will only be called when a frame happens between beat and beat + persist.
(The function is guaranteed to either run between beat and beat + persist, or not at all)

I don't believe there is high demand for this, so it is probably not worth the effort. If anyone was looking forward to this feature in v6, please let me know because right now I think this will get skipped


[bug] Prevent exit and then try to get main window crashed?

Describe the bug
.run(|app, event| match event {
            tauri::RunEvent::ExitRequested { api, .. } => {
                let win = app.get_window("main").unwrap();
                let visible = win.is_visible().unwrap();
                println!("{}",visible);
                api.prevent_exit();
            }
            _ => {}
 });

I set prevent_exit() and then try to get window,but crashed.

Reproduction
No response
Expected behavior
No response
Platform and versions
Environment
› OS: Mac OS 12.5.1 X64
› Node.js: 16.7.0
› npm: 7.20.3
› pnpm: 7.13.2
› yarn: 1.22.18
› rustup: 1.25.1
› rustc: 1.63.0
› cargo: 1.63.0
› Rust toolchain: stable-aarch64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.1.1
› @tauri-apps/api [NPM]: 1.1.0
› tauri [RUST]: 1.1.1,
› tauri-build [RUST]: 1.1.1,
› tao [RUST]: 0.14.0,
› wry [RUST]: 0.21.1,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:1420/
› framework: React
App directory structure
├─ dist
├─ node_modules
├─ public
├─ src-tauri
├─ .git
├─ .vscode
├─ .idea
└─ src
Stack trace
No response
Additional context
No response

ExitRequested is meant to stop the app from closing not the window, I think you are looking for CloseRequested event instead.
The crash happens because you called .unwrap() and you can never be sure that get_window() will return a Window because the label could be wrong or the window doesn't exist anymore.

Thanks, i fixed it.

@southorange1228 Getting same issue, plz provide the fix ?

Using WindowEvent like this.
run(|app, event| match event {
            tauri::RunEvent::WindowEvent {
                label,
                event: win_event,
                ..
            } => match win_event {
                tauri::WindowEvent::CloseRequested { api, .. } => {
                    let win = app.get_window(label.as_str()).unwrap();
                    win.hide().unwrap();
                    api.prevent_close();
                }
                _ => {}
            },
            _ => {}
 })

@shanu-mol

@southorange1228 Thanks, It helped.

Thanks, this worked for me


[insets-ui] topBar slot in Scaffold comes after content slot in Talkback ordering

Since the topBar is placed visually above the rest of the main content in the custom Scaffold implementation, it's expected that it would come before the content when navigating with Talkback. However, this is not the case: the body content is navigated to first, and then the topBar. This appears to be due to the semantic sorting logic here: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/semantics/SemanticsSort.kt;l=130;drc=627183600bfd9920c47bd26bdfe5ec906b54d2a7
Since both the topBar and content are placed in the same location, the tiebreaker that eventually resolves the issue is the height of the two slots. Since content is taller than topBar, it wins the tiebreaker, and comes first.
Configuring that order doesn't seem to be possible in any way current, as that is an outstanding feature request: https://issuetracker.google.com/issues/186443263

This was solved upstream by a change in the talkback order:
https://android-review.googlesource.com/c/platform/frameworks/support/+/2166612

Was this fix released ?
i am still experiencing this issue on androidx.compose:compose-bom:2023.09.00


Duplicate grid entries allowed

Eg this package https://www.djangopackages.com/packages/p/django-rest-assured/ appears twice in the REST framework grid, and cannot be rectified.

Project detail:

Grid display:

Also thank you so much for Django packages - super wonderful & really happy to see it now linked from the docs proper, as it should be :)

Fixed!
We're delighted it's useful to you. FWIW, in the very near future we plan to migrate to using Django REST Framework for the API. How cool is that?

in the very near future we plan to migrate to using Django REST Framework for the API. How cool is that?

Fab. :) I'd better reciprocate, and use the API to include the list of REST framework packages directly on one of the docs pages.


Guzzle4Bridge doesn't exit

fxmlrpc can be used but this example does not work because Guzzle4Bridge has been deleted.
$client = new Client(
    'http://<IP_ADDRESS>:9001/RPC2',
    new Guzzle4Bridge(new \GuzzleHttp\Client(['defaults' => ['auth' => ['user', '123']]]))
);

We used to ship our own bridges for interoperability with various HTTP clients but moved that responsibility to a 3rd party library called Ivory HTTP Adapter
...But Ivory HTTP Adapter is now deprecated... (https://github.com/lstrojny/fxmlrpc/issues/56)

Hey @hlecorche,
It is not deprecated yet, but it is very close to it. As you might have realized, I am the developer of httplug, fxmlrpc and supervisor as well. Httplug is already in alpha. As soon as it hits beta (in a few days) I am going to release an alpha of fXmlRpc's next version. After that Supervisor comes.
However, Guzzle 4 is already EOL, you might want to use a more recent HTTP Client in the meantime as Guzzle 4 is not going to be available in Httplug (at least not in the near future).
Thanks for the heads up anyway.

Ok, thanks. Good news :-)

With fxmlrpc 0.20 , the README corection is :
Before :
use Supervisor\Supervisor;
use Supervisor\Connector\XmlRpc;
use fXmlRpc\Client;
use fXmlRpc\Transport\Guzzle4Bridge;

// Pass the url and the bridge to the XmlRpc Client
$client = new Client(
    'http://<IP_ADDRESS>:9001/RPC2',
    new Guzzle4Bridge(new \GuzzleHttp\Client(['defaults' => ['auth' => ['user', '123']]]))
);

// Pass the client to the connector
// See the full list of connectors bellow
$connector = new XmlRpc($client);

$supervisor = new Supervisor($connector);

After :
use Supervisor\Supervisor;
use Supervisor\Connector\XmlRpc;
use fXmlRpc\Client;
use fXmlRpc\Transport\HttpAdapterTransport;
use Ivory\HttpAdapter\Guzzle6HttpAdapter;

//Create GuzzleHttp client
$guzzleClient = new \GuzzleHttp\Client(['auth' => ['user', '123']]);

// Pass the url and the guzzle client to the XmlRpc Client
$client = new Client(
    'http://<IP_ADDRESS>:9001/RPC2',
    new HttpAdapterTransport(new Guzzle6HttpAdapter($guzzleClient))
);

// Pass the client to the connector
// See the full list of connectors bellow
$connector = new XmlRpc($client);

$supervisor = new Supervisor($connector);

Thanks for the example update, I just pushed it to the master branch.


Circle: Deploy PR on creation

Currently, a PR isn't deployed until there's been a new commit to it, after the PR has been created. The latest commit on a PR should be deployed as soon as the PR exists.
[dmohs] There is a bug open to address this. According to this thread, Travis supports this.
[dmohs] git commit --allow-empty might be a workaround.

Closing because there isn't a good option to do this using Circle's API. Instead, we can rerun the workflow from Circle's UI.


Field parameter to support adding quotes around field data

Slightly related to https://github.com/netlify/netlify-cms/issues/3486
Is your feature request related to a problem? Please describe.
Background: I oversee Digital.gov, a site provides guidance around making better digital services for people in government. All of our websites are built using static site generators (Jekyll, Hugo), and use a mix of Federalist and GitHub to publish the pages.
Currently, most of the edits to our sites are made directly in the GitHub website from people not in our org, but people from around the government.
To make the process of editing fields easier, we are specifying that certain fields always have double quotes wrapped around them, regardless if there is a need for them or not.
For example, in the YML spec, the title field in the example below would not require it to be wrapped in quotes (title: "Introduction to Accessibility"), but because we have many editors and content designers going in to update the text fields, having double quotes around certain fields helps to ensure that the text they add will not break the build. This can be adding a colon, apostrophe, markdown formatting, etc... (title: "NEW: Introduction to Accessibility"). We have found that asking editors to remember to add quotes around an item if it has special chars is not something we coach them on in the workflow.
Here is an example of data fields and text fields 👀
slug: introduction-accessibility
date: 2019-12-04 8:00:00 -0500
title: "Introduction to Accessibility"
deck: ""
summary: "An introduction to accessibility, and why it matters."

Here's the full file
Describe the solution you'd like
We are now making a switch to use Netlify CMS, and we'd like to be able to keep the ability to specify if a field should be automatically wrapped in double-quotes. This could be done by adding an optional parameter to the field you'd want wrapped in quotes (e.g. quotes: true)
Example:
      - label: "Agency Acronym"
        name: "agency"
        widget: "string"
        hint: "e.g. GSA"
        quotes: true
        required: false

When it renders, the field would get wrapped in quotes automatically. Ideally, the field in Netlify CMS would also look for the insertion of double quotes in the field and escape them.
title: "The \"Best\" Introduction to Accessibility"

Thank you for considering this 🌈✨

Yes, +1 for quotes: true option..
Currently having an issue with a jekyll static site, where the liquid template interprets a field written as 12:12 as hours:minutes and mis-processes it.
Of course it is a Jekyll front-matter issue, implicitly interpreting a field without giving handles to modify that behaviour, but I imagine similar issues could appear in other YAML processes, and the quoting options seems a useful addition for helping with that.

+1 for quotes: true option.

same issue with Astro when since:

Decap CMS writes them like this: publishDate: 2023-09-08T15:55:00.972Z
but Astro expects them like this: publishDate: "2023-09-08T15:55:00.972Z"

same issue with Astro when since:

Decap CMS writes them like this: publishDate: 2023-09-08T15:55:00.972Z
but Astro expects them like this: publishDate: "2023-09-08T15:55:00.972Z"

same issue with Next.js.
I also want to wrap Image fields in quote strings because they are saved as URIs for the Next.js build step to find them.
I have attempted several workarounds, none of which have worked:

using the format parameter to explicitly specify IS08601 date strings
modifying my procedure for loading markdown and its frontmatter to 'stringify' the date and image URL property
replacing git-gateway with 'github' in the backend settings inside DecapCMS' config.yml (this creates another issue entirely)

Really wish there was a quotes: true for ALL DecapCMS fields


Integration Test - Release - 2022/01/27 10:17:06

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#reassign PRMergerTest2

#reassign NonAllowedUser

#please-close

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#unassign PRMergerTest1

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#unassign NonAllowedUser


file:///e%<REDACTED: user-file-path> does not exist and can not be deleted

Error: file:///e%<REDACTED: user-file-path> does not exist and can not be deleted
at s.perform in src/vs/workbench/contrib/bulkEdit/browser/bulkFileEdits.ts:245:12
at async d.apply in src/vs/workbench/contrib/bulkEdit/browser/bulkFileEdits.ts:396:20
at async $.n in src/vs/workbench/contrib/bulkEdit/browser/bulkEditService.ts:137:10
at async $.perform in src/vs/workbench/contrib/bulkEdit/browser/bulkEditService.ts:120:20
at async c.apply in src/vs/workbench/contrib/bulkEdit/browser/bulkEditService.ts:245:22
at async in src/vs/workbench/contrib/files/browser/explorerService.ts:193:4

Go to Errors Site

Should these just be ignored as the file is missing?

Depends on your use-case. It looks fishy that the explorer wants to delete a file that doesn't exist but maybe concurrent operations cause this? If you want to ignore such errors use ignoreIfNotExists

Duplicate of https://github.com/microsoft/vscode/issues/172792


Architectural Schema Draft 1

This is the initial attempt at a schema. Please note that the focus of this PR is to better understand how to create the 'architecture' of a subgraph schema. The details of the field types will be hashed out as I work through the mapping whilst referencing the intricacies of the smart contracts for this subgraph.
Please provide a quick review on the schema entities and fields for now.
The README.md at the repo root also has a Questions section that would be great to have your feedback on.
Thanks!
Steve
PS: Just realized that I rushed this and didn't even put in a .gitignore file (had one before but reverts deleted it). I'll add another one after this PR Review.

First attempt at writing schema for first subraph
Building off of this start for adjusted schema as per PR Review comments with David Kajpust


Fix brew audit offense.

== /usr/local/Library/Taps/neovim/homebrew-neovim/Formula/neovim.rb ==
C:123: 72: Avoid comma after the last item of an array, unless each item is on its own line.
1 file inspected, 1 offense detected

I'm pretty sure at some point (11f258c766bfeecf2c2d53fbd2f11727ce40d929) the audit asked for the trailing comma to be added, I don't think I would have changed it otherwise.. oh well.

Ha, yeah I noticed that too and thought similar.


Just FYI - Your CodePen no longer works

Your referenced CodePen (http://codepen.io/mebibou/pen/pjEjOv) no longer works because the files hosted at https://rawgit.com/mebibou/ no longer resolve.
Great work btw.

fixed, thanks


update pdf definitions of unit payment correction note

Coverage increased (+0.2%) to 63.944% when pulling 8ba3ca16e09e8010e421c681999adb36cbe5886e on indriHutabalian:dev into 334b936c1b298617caf361913862e13031d01f3f on danliris:dev.


Release 1.0

Reorganization of getParameterSamples & sampling options
Cleanup
Backward compatibility
Documentation
...

Seems fine for me so far. Not yet perfect, but fine enough for a merge. (Hopefully very soonish fine enough for the application note)


ippeveprinter.c: Check the created path string instead of command

If a user passes the command by only its name, we have to check the path string we created instead of command string alone.

Thank you, Mike!


[USM] Support index 4 in http2 decoding

What does this PR do?
Supports the use case where the path is sent with index 4.

Motivation
Supports all possible cases in gRPC/HTTP2 decoding to improve accuracy.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Feature request: @platformatic/client - send header parameters

Currently @platformatic/client only sends request body and url parameters, but not any headers defined in the openapi spec.
This is somewhat confusing as the client cli includes the header parameters in the types it creates, so an editor will suggest you add a property that won't actually be sent.

This is indeed a bug! Would you like to take a stab at fixing it? It should be fairly simple!

Hi! Yeah I've actually already done it I just need to write some tests. I'll get something ready soon when I have some time, thanks!


ability and flexible for using specific image tag from local environment or difference registry

I would like we have a way to specific an image tag whenever I or somebody else want to test with new OCI image from local environment or difference registry
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes https://github.com/pipe-cd/pipecd/issues/4506
Does this PR introduce a user-facing change?: N/A

How are users affected by this change: N/A
Is this breaking change: N/A
How to migrate (if breaking change): N/A

@khanhtc1202  thanks for your feedback, solved


SEC-1051: refactored to comply with new CSP

Changelog: None
Signed-off-by: Mikita Pilinka<EMAIL_ADDRESS>

Thanks for submitting a PR! Maybe @larsewi can review this?

@mineralsfree please check staging and open production <- master PR if OK


Bot randomly fails to place blocks when scaffolding

scafolding (for search)
When a bot is bridging to a goal and has to place blocks (e.g. when traveling over void) it sometimes randomly fails to place a block but continues to move, which often causes it to fall down (and place blocks mid-air, #181).
I was able to reduce the occurences of this issue by removing
https://github.com/PrismarineJS/mineflayer-pathfinder/blob/56a02b9af715029f884cd392aa7f0836e0284c03/index.js#L500
It seems like nothing is really affected by this change except the bot is bridging slower, which is imo a fair trade off for it to not fall.
Is there another recommended solution for this issue?
Ideal solution would be to fully pause (or find another way) until the block was placed successfully, but it seems like that's not working currently.

 The issue I see with removing this line is that the bot might in some cases not stop crouching.

The bot always unsneaked for me when it had to jump - but as I said, another solution is probably better.

I have been digging into this for a while, and turns out it is a timing issue.
The bot triggers a jump here while checking if it is in correct height.
https://github.com/PrismarineJS/mineflayer-pathfinder/blob/56a02b9af715029f884cd392aa7f0836e0284c03/index.js#L486-L489
Then it gets to placing the block like this:
https://github.com/PrismarineJS/mineflayer-pathfinder/blob/56a02b9af715029f884cd392aa7f0836e0284c03/index.js#L490-L497
Two big problems here:

bot.equip(block, 'hand') takes time.
By the time the block is equipped, the bot might be already gone from the correct position to place it.
bot.placeBlock() takes possibly even more time before the actual block place packet is sent (up to 1 second).

That is because if we look at the implementation of the block placemet, couple of calls down the stack (bot.placeBlock() --> bot._placeBlockWithOptions() --> bot._genericPlace()) we can see this, just before the packet is sent:
plugins/generic_place.js
if (options.forceLook !== 'ignore') {
  await bot.lookAt(referenceBlock.position.offset(dx, dy, dz), options.forceLook)
}

I'm guessing that the lookAt is playing some head movement animation, so we're waiting for this before the packet is sent. By this time, it would be a sheer luck to have the bot in a correct position for the block placemet.
TLDR
The bot stands in its way when placing a block because it is waiting for too long before sending the place packet. It falls back down and obstructs the block placement.

Yes, equip can take time to select the item, but only when the item is not already in any of the hotbar slots. Placeblock should also send the packet in the same tick if the force look option is trueish. Look will set the bot looking direction and return the promise in the same tick if the force look option is true. Maybe a better approval would be to only start jumping if the item has been equipped. But someone would have to test how well that works.


Refactoring function creation, div fix, array fixes and helpers

TITLE
Description
Main goal of this PR was to refactor all region handling, and function creation into a single function to be called after the blocks for a function have been created and filled. Along the way, I also:

Replaced match and generic args with helper
Added and used more array helpers, which seems to have fixed something as the pop_front_valid test now passes
Fixed an array append bug where capacity wasn't multiplied by the size of the element before being passed to realloc
Reimplemented felt_div with the extended euclidean algorithm which should be faster than exponentiation. Div tests now pass
Replaced Block::new with self.new_block as it's more concise and easier to read
Replaced large if lets with smaller let (x,y) = if let, both to reduce scope nesting and to prepare for SierraType refactors that'll replace such things with a function call

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #139 (eb9f310) into main (79b9051) will increase coverage by 3.10%.
The diff coverage is 97.81%.

@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
+ Coverage   86.17%   89.27%   +3.10%
==========================================
  Files          23       24       +1
  Lines        6235     6323      +88
==========================================
+ Hits         5373     5645     +272
+ Misses        862      678     -184

Impacted Files
Coverage Δ

sierra2mlir/src/compiler/mlir_ops.rs
71.00% <ø> (+3.09%)
:arrow_up:

sierra2mlir/src/sierra_type.rs
82.24% <ø> (-10.29%)
:arrow_down:

sierra2mlir/src/libfuncs/sierra_enum.rs
91.37% <90.69%> (+0.47%)
:arrow_up:

sierra2mlir/src/userfuncs/mod.rs
95.10% <95.83%> (+0.18%)
:arrow_up:

sierra2mlir/src/utility.rs
87.78% <96.05%> (-0.68%)
:arrow_down:

sierra2mlir/src/compiler/helpers/array.rs
96.13% <96.99%> (+0.40%)
:arrow_up:

sierra2mlir/src/compiler/helpers/maths.rs
99.26% <99.26%> (ø)

sierra2mlir/src/libfuncs/mod.rs
97.82% <99.44%> (+4.33%)
:arrow_up:

sierra2mlir/src/compiler/helpers/panic.rs
98.11% <100.00%> (ø)

sierra2mlir/src/compiler/helpers/sierra_enum.rs
96.39% <100.00%> (-0.41%)
:arrow_down:

... and 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Merged main here and fixed conflicts, also some test issues


PMM-2715: Start init script after rc job.

Coverage remained the same at 7.838% when pulling 59cab2ddbcb93aaf57684f68b919d1767a0da0c1 on PMM-2715_start_after_rc into acdc9090d60b1763410d42052a29e62e73a3552d on master.


Flaml/AutoML with Distributed MARS sample?

Hello, I'm trying to run a distributed AutoML with MARS + LightGBM for huge (TB) csv input file. I can't find how to do it any idea?
TY!
(https://docs.pymars.org/en/latest/user_guide/learn/lightgbm.html)

Hi @wil70, do you have an example of distributed training using MARS + LightGBM?
Without that information, the most probable solution I can recommend is to modify the example in: https://microsoft.github.io/FLAML/docs/Getting-Started/#tune-user-defined-function
by replacing the normal LigthGBM training with the MARS + LightGBM training.

Duplicated isssue with https://github.com/mars-project/mars/issues/3273 .
Let's have a discussion here.

I have other issues going on with MARS when big dataset, I posted on their forum
What do you guys use for huge CSV input file (let's say >1TB) + LightGBM + Flaml
I can make

LightGBM c++ work and distribute it but I do not have parameter tuning in that case (may be I can sample on small data set with FLAML and then feed the parameter to LightGBM but that won't be exactly the same)
ML.net is great but no distributed + no way to continue a LightGBM training and other issues
I also try with DAS but there were also issue for those large input

Any idea?
TY!

For LightGBM c++, do you use a cmd line to train models? How do you pass hyperparameters? You can wrap the cmd line in a python function which takes the hyperparameter configuration as an argument. Follow the same example given above.


Take descriptors in the configuration

Abusing the compiler to generate the Miniscript descriptors was only a temporary solution until we figure out how we are going to generate the descriptors. Turns out we have not figured out much and are just going to generate them in advance and let them be duplicated between the config and the DB (i don't think it's that bad actually). The GUI wrapper could then take care of generating them for the user with a setup wizard.
This PR:

Is based on #208
Removes our reliance on the xpubs from the config
Updates revault_tx to benefit from the "smart" xpub getters from the descriptors
Removes the scattered xpubs from the config altogether in favour of taking three descriptors (Deposit, Unvault, Cpfp)

Fixes #108

@edouardparis can you skim through it rapidly to tell me if it's reasonable from the GUI point of view?

Flaky CI :( Re-running

Hope it won't anymore post https://github.com/revault/revaultd/pull/215


Deprecate/remove vscode plugin?

Is there any reason to keep the vscode extension alive? Its functionality seems to have been improved upon in Metals (with completions and navigation in sbt build files, and all the BSP goodies), and it hasn't seen code changes in years so I'm not even sure it works these days.

Yea. It's essentially subsumed by BSP server, so I don't think there's any reason to keep the VS Code plugin around.

It should be off the marketplace now - https://marketplace.visualstudio.com/vscode

oh, great! I was thinking if we should have a final release mentioning the deprecation. This makes the removal much easier for me :P I'll drop a PR later.

Fixed in https://github.com/sbt/sbt/pull/7307


Cannot run D2gs

system win10 x64
in D2SVC.LOG
08/22 10:47:59.898 ServerSetParameter: set working directory to "D:\server_data\legacy_server\bnet\d2gs"
08/22 10:47:59.899 D2GSControler: started, process id 14344
08/22 10:47:59.899 D2GSControler: D2GS Server is not running
08/22 10:47:59.901 RunServer: Using CmdLine "D2GS.EXE"
08/22 10:47:59.931 RunServer: Server started successfully, process id: 14520
08/22 10:48:00.517 D2GSControler: D2GS Server is not running
08/22 10:48:00.520 RunServer: Using CmdLine "D2GS.EXE"
…………
…………

Which of versions? 1.09d?
http://forums.harpywar.com/viewtopic.php?pid=7769#p7769

1.13c

I think the problem in wrong configured D2GS. You should check the configs files and make sure that all D2GS files belong to the same version (if you didn't use Magic Builder for that or try any D2 mods).
http://forums.harpywar.com/viewtopic.php?id=1287

Try set up a compatibility mode for all users if you run D2GS on the newest Windows http://forums.harpywar.com/viewtopic.php?pid=7773#p7773


Complexity is set as undefined in the DOM elements

Something is wrong with the transferring of complexity value to the DOM elements created.

This is fixed in the issue100 branch.


[BUG] My account section on home page

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
As a logged in user, go to my account and then go to the home page (by clicking on the logo) effect? my account section is displayed on the main page :O
https://github.com/shopware/frontends/assets/30267600/cd502d95-05de-494b-9438-d9b873fa1909
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS:
- Node:
- pnpm:

Anything else?
No response

https://github.com/nuxt/nuxt/issues/13309


Add small improvements related to introducing React strict mode

Details

this PR is related to introducing react concurrent mode and StrictMode in here: https://github.com/Expensify/App/pull/42592
in the original PR there were some cleanups that I believe to be useful to make code cleaner, but are not strictly necessary for the strict mode and concurrency to work, so I moved them here (read this: https://github.com/Expensify/App/pull/42592#issuecomment-2180482844)
Ideally this should be merged before: https://github.com/Expensify/App/pull/42592
this changed no feature so I provide no screenshots, there is 1 thing to verify and the rest is just code changes

changes:

ReportScreenIDSetter - moving forward we want to use only useOnyx, as a test I rewritten this one screen to useOnyx for safety and performance; old withOnyx is not fully safe to use with concurrent react
removed import 'shim-keyboard-event-key - Internet Explorer is not supported by MS since 2022, and I believe we should not be supporting "dead" browsers
removed forwardRef because it was not used

Fixed Issues

$ https://github.com/Expensify/App/issues/33531
PROPOSAL:
Tests

enter a report and make sure report screen works and switching between reports also works

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@mountiny FYI this is the PR with less important changes from the other PR like we discussed

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.0.2-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.0.3-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[TEST] Add negative test cases for volume live migration

What's the test to develop? Please describe
To improve the volume live migration resilience, we need to add negative test cases for the feature.
Describe the tasks for the test

Additional context

@yangchiu Let's see if we can make it in v1.8.0. Thank you.

Possible test cases:

Initiate live migration. Delete the engine process of the volume.
While live migration is in progress, reboot the target node.
While live migration is in progress, reboot the source node.
While writing in the volume, trigger the volume migration, check the data after migration.

We can try these manually first to see the behavior first.

Hi @longhorn/qa
I wrote a bunch of skeleton for migration negative test cases here https://github.com/longhorn/longhorn/issues/6361#issuecomment-2537547340
You can take a look when doing this ticket. Thank you
@khushboo-rancher @yangchiu @derekbit


MM-16392 Split view support & hide sidebar on tablets

Summary
Now when the app is opened on a tablet with split screen the drawer will not be present at all times but it will behave like it does on phones allowing more real state to display the messages.
Ticket Link
https://mattermost.atlassian.net/browse/MM-16392
Device Information
This PR was tested on: iPad Pro 11" and Android Tablet running Pie

@enahum Is this PR related to this bug report: https://forum.mattermost.org/t/new-mattermost-ruined-ipad-split-windows/7509?

@amyblais yes, this will fix that ;)

cherry-pick to 1.20 for a dot release


can u add chinese

if you give me the translations haha

ok i will give u<EMAIL_ADDRESS>

Hello i have translated

Thanks, i got it


added windows 11

after reading this article, i confirmed windows 11 is supported

Learn Build status updates of commit 6f5f49b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/network-security-allow-local-system-to-use-computer-identity-for-ntlm.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Cilium agents start duplicate Service/Endpointslice informers

Is there an existing issue for this?

[x] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
Starting from v1.16, each Cilium agent starts two services and endpointslices informers, introducing extra load on the Kubernetes API Server. The main commits that appear to contribute to the regression are 99268e7ba1c7, cce40804c3ac and 0e8c5a64f37a,  because a few consumers leverage the filtered resources, while a few others the unfiltered ones.
The best fix is probably dropping the filtered resource altogether (assuming it is possible, adapting the consumers accordingly), to prevent regressions in the future due to the mixed usage of the two resources.
How can we reproduce the issue?
This issue can be validated checking the apiserver_longrunning_requests Kubernetes API Server metric. For instance, on a four nodes kind cluster:
# Cilium agents are not running
$ kubectl get --raw /metrics | grep apiserver_longrunning_requests | egrep '"services|endpointslices"'
apiserver_longrunning_requests{component="apiserver",group="",resource="services",scope="cluster",subresource="",verb="WATCH",version="v1"} 13
apiserver_longrunning_requests{component="apiserver",group="discovery.k8s.io",resource="endpointslices",scope="cluster",subresource="",verb="WATCH",version="v1"} 7

# Cilium agents are running
$ kubectl get --raw /metrics | grep apiserver_longrunning_requests | egrep '"services|endpointslices"'
apiserver_longrunning_requests{component="apiserver",group="",resource="services",scope="cluster",subresource="",verb="WATCH",version="v1"} 21
apiserver_longrunning_requests{component="apiserver",group="discovery.k8s.io",resource="endpointslices",scope="cluster",subresource="",verb="WATCH",version="v1"} 15

Cilium Version
Cilium v1.16 and above
Code of Conduct

[x] I agree to follow this project's Code of Conduct

/cc @MrFreezeex FYI. Would you be interested working on the fix?

Ah indeed that's a very nice catch!

The best fix is probably dropping the filtered resource altogether (assuming it is possible, adapting the consumers accordingly), to prevent regressions in the future due to the mixed usage of the two resources.
/cc @MrFreezeex FYI. Would you be interested working on the fix?

Yes I agree, I can definitely check to do that fix indeed! :D


TfLite floor_mod.cc compilation warning fix

Compilation warning fix.

@Dayananda-V can you please check failed build errors

@gbaned
Am not able to find failure test case, just one broken test suite able to seen. Can you force trigger build again?

@Dayananda-V  Thank you. Yes, I can force trigger the build again.


Solving rendering issues for examples documentation

As title says. After merging #1649 we realized that there were some issues:

[x] Links not properly rendered
[x] Missing title

This PR will solve those issues

We need to merge it before Thursday @germa89 - we are planning on showing this at the PyAnsys API meeting


[pie] improvements to pie charts (#5236)

This PR cherry-picks https://github.com/apache/incubator-superset/pull/5236 which fixes an issue with the pie chart.
to: @graceguo-supercat @kristw @michellethomas @timifasubaa @williaster

Codecov Report

Merging #95 into airbnb-master will increase coverage by 9.37%.
The diff coverage is 0%.

@@                Coverage Diff                @@
##           airbnb-master      #95      +/-   ##
=================================================
+ Coverage          53.87%   63.24%   +9.37%
=================================================
  Files                306      351      +45
  Lines              13181    22035    +8854
  Branches            2470     2468       -2
=================================================
+ Hits                7101    13937    +6836
- Misses              6068     8086    +2018
  Partials              12       12

Impacted Files
Coverage Δ

superset/assets/src/explore/controls.jsx
45.8% <ø> (ø)
:arrow_up:

superset/assets/src/explore/visTypes.jsx
57.14% <ø> (ø)
:arrow_up:

superset/assets/src/visualizations/nvd3_vis.js
9.37% <0%> (-0.02%)
:arrow_down:

superset/assets/src/reduxUtils.js
74.57% <0%> (-0.84%)
:arrow_down:

...rset/assets/src/SqlLab/components/TableElement.jsx
95.23% <0%> (ø)
:arrow_up:

.../assets/src/SqlLab/components/SqlEditorLeftBar.jsx
92.52% <0%> (ø)
:arrow_up:

...t/assets/src/SqlLab/components/CopyQueryTabUrl.jsx
78.57% <0%> (ø)
:arrow_up:

.../assets/src/SqlLab/components/TabbedSqlEditors.jsx
91.74% <0%> (ø)
:arrow_up:

superset/views/core.py
73.69% <0%> (ø)

superset/connectors/sqla/models.py
78.08% <0%> (ø)

... and 43 more

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 64e8e0d...f8b6bef. Read the comment docs.


Allow logging request body

Confirm this is a feature request for the Python library and not the underlying OpenAI API.

[X] This is a feature request for the Python library

Describe the feature or improvement you're requesting
It would be nice to be able to be able to log the body of the requests.
I needed to see what was sent over the wire, so I checked how to log body requests.
Turns out, there's no way.
I needed to modify this, in order to do it.
https://github.com/openai/openai-python/blob/58bec2ffe5274b37fed3adad8da188f0cbc5406c/src/openai/_base_client.py#L447-L448
Could you add support to log body requests?
I'm not sure if this is the only place that has to change.
In fact, I just ended capturing network traffic just to be sure.
Having to resort to this kind of technique, is not nice.
I'm aware that you can log request/response using a custom httpx client with a custom transport: https://github.com/encode/httpx/discussions/3073
EDIT: the same applies to responses body
Additional context
No response

Thanks for the request, I agree this would be nice to provide! I don't expect we'll be able to get to it soon, but we do want to make logging & tracing comprehensively nicer to deal with.
We invite anyone visiting this issue to add other use-cases they'd like to see supported with logging etc.

@rattrayalex we're defining GenAI/LLM conventions for distributed tracing and metrics in OpenTelemetry - https://github.com/open-telemetry/semantic-conventions/tree/main/docs/gen-ai and have a group of people working on otel and GenAI observability behind it.
Would love to share more and collaborate, we're always available at
https://github.com/open-telemetry/community/blob/fd765d9cc37bd1aac431f7f194e3842e02349530/README.md?plain=1#L141

| Semantic Conventions: LLM | Every Wednesday alternating between 10:00 and 16:00 PT | Google Doc | #otel-llm-semconv-wg | calendar-semconv | Alolita Sharma,Liudmila Molkova | Alolita Sharma |

Thanks for the request, I agree this would be nice to provide! I don't expect we'll be able to get to it soon, but we do want to make logging & tracing comprehensively nicer to deal with in the coming months.
We invite anyone visiting this issue to add other use-cases they'd like to see supported with logging etc.

@rattrayalex - As mentioned by @lmolkova in the comment above, there is a CNCF open telemetry working group that is driving standardization of tracing across LLM vendors. We have a initial spec which we are currently iterating on and it would be great if this project adopts to the standard conventions.

@karthikscale3 @lmolkova unfortunately we will not likely be able to prioritise this soon, however I would be interested in seeing a sample of what the changes we would have to make would look like if anyone is able to share?

@karthikscale3 @lmolkova unfortunately we will not likely be able to prioritise this soon, however I would be interested in seeing a sample of what the changes we would have to make would look like if anyone is able to share?

I am happy to put something over and share it here. Give me a couple of days

Thank you. We are supportive of the CNCF / OTel work here. Please email me with a specific proposal once there is something ready for review.

@karthikscale3 Awesome! I'll share in case it helps - awhile back I had experimented with instrumenting the library using a decorator approach: https://github.com/kristapratico/openai-python/pull/7


Keyboard shortcuts to move app windows left/right between zones is not working.

Microsoft PowerToys version
0.56.2
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Create a layout with one eft and two right zones on the screen. Configure Fanzy Zones to override Windows Snap and configure it to use relative positioning. Focus on one of the right zones
✔ Expected Behavior
Pressing Windows + left arrow should move one of the right zone apps to the left zone and the app moves to the zone.
❌ Actual Behavior
Nothing happens. In fact Windows + left or right arrow does not work as it did with previous release. Windows + up/down arrows do work between the two right zones.
Other Software
None

Sorry, contributed too soon. Found the problem.


Added contact details

closes #27

You can write a menu mod for king of thieves?

You can write a menu mod for king of thieves?

Please open a feature request.


Testing with Rspec and Hydra This will be a reprise of a workshop given at HC 2...

Testing with Rspec and Hydra This will be a reprise of a workshop given at HC 2014, but improved and updated to cover new issues with the PCDM stack of gems, as well as strategies for test refactoring and speed improvement. The workshop will go over testing practices for each of the principle unit components of an application (models, controllers, views, jobs, services, etc.) and also contrast that with how feature tests and written. Takeaways will include some "boilerplate" examples for each kinds of test, test suite configuration, continuous integration, and if time permits, one-on-one help with individual questions or blockers that anyone might be currently having.
Suggested by: Adam Wead
Presenter: Adam Wead
Format: Workshop
Audience: Developers, new and old

2016-07-06
Let's say no more than 20, but I won't turn anyone away.  I'd say that if there's a lot of interest, ex. 30+ people, it would depend on getting some TAs to help out.
Having a laptop and working Hydra application is a must, even if it's just the barebones. Ideally, this workshop is geared towards current Hydra adopters or people who have just started working on applications. Someone who has never used Hydra or Rspec and doesn't have the environment setup would have trouble. I wouldn't turn them away, but would recommend something else if it was available.


./latencies-riscv.h:96:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FNMADDS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:97:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FADDS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:98:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FSUBS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:99:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FMULS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:100:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FDIVS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:101:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FSQRTS]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:102:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FSGNJS]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:103:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FSGNJNS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:104:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FSGNJXS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:105:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FMINS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:106:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FMAXS]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:107:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FCVTWS]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:108:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FCVTWUS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:109:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FMVXW]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:110:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FEQS]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:111:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FLTS]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:112:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FLES]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:113:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FCLASSS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:114:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FCVTSW]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:115:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FCVTSWU]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:116:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32F_OP_FMVWX]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:119:18: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FLD]          {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:120:18: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSD]          {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:121:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FMADDD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:122:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FMSUBD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:123:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FNMSUBD]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:124:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FNMADDD]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:125:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FADDD]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:126:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSUBD]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:127:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FMULD]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:128:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FDIVD]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:129:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSQRTD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:130:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSGNJD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:131:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSGNJND]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:132:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FSGNJXD]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:133:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FMIND]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:134:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FMAXD]        {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:135:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTSD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:136:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTDS]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:137:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FEQD]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:138:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FLTD]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:139:19: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FLED]         {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:140:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCLASSD]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:141:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTWD]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:142:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTWUD]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:143:20: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTDW]       {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:144:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32D_OP_FCVTDWU]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:147:21: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNUPGS]      {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:148:22: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNGCOVS]     {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:149:22: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNSVARS]     {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:150:23: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNCLVARS]    {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:151:23: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNCPVARS]    {1,     1,      1,      1,      1},
^
=
./latencies-riscv.h:152:22: warning: use of GNU 'missing =' extension in designator [-Wgnu-designator]
[RV32UN_OP_UNPART1]     {1,     1,      1,      1,      1},
^
=
617 warnings generated.
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c merror.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c mmalloc.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c mmu-hitachi-sh.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c network-hitachi-sh.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c op-hitachi-sh.c -o op-hitachi-sh.o
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c op-riscv.c -o op-riscv.o
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c pau.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c physics.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c mass.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c propulsion.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c pic.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c pipeline-hitachi-sh.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c pipeline-riscv.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c power.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c regaccess-riscv.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c syscalls.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c tokenhandling.c
bison -t -v -Wno-other -Wno-conflicts-sr -Wno-conflicts-rr -p sf_superh_ sf-hitachi-sh.y
clang -g -DSF_L_ENDIAN  -Wall  -g -m32 -O0  -c sf-hitachi-sh.tab.c -o sf-hitachi-sh.o
sf-hitachi-sh.y:2089:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2129:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2170:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2210:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2250:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2288:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:2326:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-hitachi-sh.y:3290:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
8 warnings generated.
bison -t -v -Wno-other -Wno-conflicts-sr -Wno-conflicts-rr -p sf_riscv_ sf-riscv.y
clang -g -DSF_L_ENDIAN  -Wall  -g -m32 -O0  -c sf-riscv.tab.c -o sf-riscv.o
sf-riscv.y:2041:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2081:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2122:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2162:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2198:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2246:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2291:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2336:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2381:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2426:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2471:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2528:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2567:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2607:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2647:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2687:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2727:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2763:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2803:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2844:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2884:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2929:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:2974:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3015:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3056:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3097:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3137:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3177:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3218:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3259:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3300:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3341:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3382:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3423:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3468:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3509:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
sf-riscv.y:3549:50: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
if (yyengine->cp->PC - yyengine->cp->MEMBASE < 0 ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~
37 warnings generated.
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c taint.c
clang -g -DSF_L_ENDIAN  -Wall   -g -m32 -O0  -c uncertain-histogram.c
./mkmantex gawk > commands.tex
clang -g randgen.o arch-linux.o batt.o bit-utils.o decode-hitachi-sh.o decode-riscv.o dev7708.o devsim7708.o fault.o fdr.o machine-hitachi-sh.o machine-riscv.o inst_uncertain.o main.o merror.o mmalloc.o mmu-hitachi-sh.o network-hitachi-sh.o op-hitachi-sh.o op-riscv.o pau.o physics.o mass.o propulsion.o pic.o pipeline-hitachi-sh.o pipeline-riscv.o power.o regaccess-riscv.o syscalls.o tokenhandling.o sf-hitachi-sh.o sf-riscv.o taint.o uncertain-histogram.o  -m32 -lm -lpthread  -o sf
make[1]: Leaving directory '/home/billtsou/Desktop/sunflower-simulator/sim'
Host OS (please complete the following information):

OS: Ubuntu 16.04.6 LTS
Kernel: 4.4.0-169-generic #198-Ubuntu SMP Tue Nov 12 10:38:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Clang Version: clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) - Target: x86_64-pc-linux-gnu - Thread model: posix

You can't simply change the compiler from gcc to clang as they take compiler different flags. Please see the diff between the macOS and linux.

Closing this.


In Aid of the Myreque

Need to add following silver sickle to 'Relocating'
-"You can give him a SILVER SICKLE, steel med helm / chainbody / platelegs, and salmon"

fixed with https://github.com/Zoinkwiz/quest-helper/commit/78ab3b207974b271b4469b11d2edcea5634cabd1.


fix(scripts): allow generating a QR code from a filename

(supersedes #1681, submitted to the wrong branch, sorry about that).
The last couple times I've used the qr generation functionality, I make the mistake of passing the filename instead of the client name. This time it annoyed me enough to do something about it :).
Thanks for this great tool!

Hi thanks a lot for your Pull Request, sorry it has taken so long, I genuinely though I had taken care of it.
this feels more like a feature to me rather than a fix.
Would you mind to amend your commit header from fix to feat? other than that all looks good.

Merged. Thanks a lot for your contribution.

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


IANA has assigned numbers for 2 hybrid PQ KEX widely used in tests

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Merged to the master branch


If the heading of the csv contain " quote it fails.

Maybe the heading has to be escaped.

Could you provide an example CSV?

FYI. I am using the module on the browser.
I have attached 2 files. Sample 1 will run fine. Sample 2 will error out since it has quotes on the heading.
http://cl.ly/0k0N1z0v2Q3d/sample.csv - sample 1
http://cl.ly/3O1X26362L2Z/sample2.csv - sample 2


added 'Change my password' link to password mail template

It solves rubygems/rubygems.org#908 problem.

@jessieay updated pr to use i18n.
yes rubygems uses clearance :sparkles:

@farukaydin awesome, thanks for the update! This looks good to me. I will let @tute have the final say on this before merging.

And by @tute, I mean @derekprior :space_invader: forgot which library we were in here! :)

Introducing a new key for existing text might be tricky to get right. If your language is set to french, for instance, you don't get the benefit of the default translations we provide. So now your password reset mailer has a link with the text "link text". We can't rely on apps using clearance to have configured english as a fallback.
We may need to provide a default: Change your password option to the translate call. Thoughts?

Updated and merged in 41f06bef59563cad535a339431a1b7f5623c6e44

Thank you @farukaydin.

@derekprior you're right, default option looks good :+1:


feature(eip): Add Dynamic Route EIP

Fixes #210

Codecov Report

Merging #251 (4e51fb6) into main (4672257) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head 4e51fb6 differs from pull request most recent head 9a27875. Consider uploading reports for the commit 9a27875 to get more accurate results

@@             Coverage Diff              @@
##               main     #251      +/-   ##
============================================
- Coverage     80.36%   80.33%   -0.03%
  Complexity      114      114
============================================
  Files            45       45
  Lines          2139     2141       +2
  Branches        317      317
============================================
+ Hits           1719     1720       +1
- Misses          275      276       +1
  Partials        145      145

Impacted Files
Coverage Δ

...ployment/generator/kamelet/KameletRepresenter.java
89.36% <ø> (ø)

...src/main/java/io/kaoto/backend/KamelPopulator.java
90.35% <100.00%> (+0.08%)
:arrow_up:

.../backend/api/metadata/catalog/AbstractCatalog.java
97.22% <0.00%> (-2.78%)
:arrow_down:

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


Add bindings for Julia

I don't think there's a good binding library like pyo3 or wasm-bindgen, but this should be doable via straight FFI:
https://github.com/felipenoris/JuliaPackageWithRustDep.jl
I'm not exactly sure what the best record format on the Julia side would be? Maybe there's something in their DataFrames library:
https://juliadata.github.io/DataFrames.jl/stable/

There appear to be two libraries for binding to Julia and neither can really support this without a lot of work so this might be another year or two off.

julia-rs is four years old and appears to be unmaintained. It does have all of the low-level jl_ calls though so things like returning errors to Julia are possible.
jlrs appears to be currently maintained, but allowlists all the low-level calls it/jl-sys generates so it's missing jl_error and a couple other ones (which require nasty workarounds like returning a null pointer for error cases and then checking on the Julia side). It's also not totally clear with its scope/global system how to create a Julia object and then return it back to Julia.


Request For Enhancement - Homing Feature

Expected Behavior
I would like the bot to drive to physical (0,0,0). Software (0,0,0) can be wrong, especially when setting up and installing Farmbot for the first time. I would like to have a button that drives to x_min, y_min, z_min and sets zero position via G-code. Speed should be adjustable.
Actual Behavior
The calibration feature sort of does this, however the outcome is seems rather odd to me. For each axis, it drives to min, drives to max and then stops at max. Software setting for this point is (0,0,0). In my configuration (no inverted endpoints, no inverted motors, no negatives allowed) it is then stuck there as driving to the actual physical 0 is forbidden as software thinks I am at 0. Solving this always requires fiddling around and is quite cumbersome.

Could you implement such a homing feature? Would really appreciate it !
How do you use the calibration feature? Am I doing something wrong ?

Thanks for you time !

Hi @bautze we've spotted some bugs on the calibration feature and have been working on it all this week.
Will keep you posted and sorry for the slow response (it's been a busy week for everyone on the software team).

Hi, thanks for the reply. Actually, I was thinking that such a homing feature would actually be nice to use with the sequence builder as well !

Well, I tried the Calibration button and the Home button, however it is still rather inconvenient. Calibration drives to min, then to max and then set 0 at max. This leaves my bot stuck at max and I have to allow negatives and manually drive it to physical 0.
I would have expected the home button to drive to the minimum endstop and stay there, it however drives to software defined zero (which is usually wrong after booting the bot).

@bautze We've revamped our homing button and added a "set zero" button for all axes. Hope that helps! Please let me know if you need anything else and we can re-open as needed.


instantiation error

During instantiation,error may occur because lack of pakages:
I solved it by addtional running:
pip install chardet
pip install --force-reinstall charset-normalizer==3.1.0

Thanks for reporting!


Cannot find module './lib/transform'

H there, I have installed "npm i magento-api-rest" and it didnt install the ./lib/transform folder, any guess what could be wrong?
Thank you,

Sorry for the late reply, It looks like an issue with the Babel Config and the lib folder is not getting updated at npm.

Hi !
Thanks for using the package, the problem was with the "files" part in package.json. It has been fixed.