[bug] Window doesn't fully implement Send

Describe the bug
I believe there has been a regression between the last Tauri beta release and the next branch.
i.e. this works when I set my tauri deps to be:
tauri = { version = "1.0.0-beta.8", features = ["api-all"] }

but not:
tauri = { git = "https://github.com/tauri-apps/tauri", branch = "next", features = ["api-all"] }

When trying to spawn a task that requires an instance of window (in order to emit events), I am unable to send Window as the compiler throws a number of errors that sub-components don't to implement Send (see errors in stack trace section)
I think that this bug is macOS only, and suspect that this may have to do more with the tao crate, rather than the tauri crate, although I am filing this bug in the tauri repo since I am trying to access the instance of Window from a tauri::command
Reproduction
Attempt to compile the following in your src-tauri/main.rs file (requires Tokio)
#![cfg_attr(
all(not(debug_assertions), target_os = "windows"),
windows_subsystem = "windows"
)]

use std::time::Duration;
use tauri::Window;
use tokio::time::sleep;

struct Task {
    name: String,
    window: Window,
}

impl Task {
    fn new(name: String, window: Window) -> Task {
        Task { name, window }
    }

    async fn run(&self) -> Result<(), String> {
        println!("Doing task {}", self.name);
        sleep(Duration::from_secs(5)).await;
        println!("Task {} finished", self.name);
        self.window.emit("taskFinished", &self.name).expect("Failed to emit event");
        Ok(())
    }
}

#[tauri::command]
async fn do_task(name: String, window: Window) -> String {
    let task_name = name.clone();
    tokio::spawn(async move {
        let task = Task::new(task_name, window);
        match task.run().await {
            Ok(_) => (),
            Err(e) => println!("Error: {}", e),
        };
    });
    format!("Task {} spawned", name)
}

fn main() {
    tauri::Builder::default()
        .invoke_handler(tauri::generate_handler![do_task])
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

Expected behavior
tauri::Window should fully implement Send to be allowed to be sent across threads safely, especially for long-running tasks that may need to emit events to the window that it belongs to (for example, I have written code to upload large files in a separate thread, and notifying the parent window of the progress of that upload)
Platform and versions
Operating System - Mac OS, version 12.1.0 X64

Node.js environment
  Node.js - 16.13.1
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 8.1.2
  yarn - 1.22.17

Rust environment
  rustc - 1.59.0-nightly
  cargo - 1.59.0-nightly

App directory structure
/dist
/node_modules
/src-tauri
/.idea
/src

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../dist
  devPath - http://localhost:3000
  framework - React

Stack trace
error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `Task`, the trait `Sync` is not implemented for `*mut ()`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `tao::global_shortcut::ShortcutManager`, the trait `Send` is not implemented for `*mut c_void`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `(tao::window::WindowId, tauri_runtime_wry::WindowWrapper)`, the trait `Send` is not implemented for `Rc<tao::window::Window>`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `(tao::window::WindowId, tauri_runtime_wry::WindowWrapper)`, the trait `Send` is not implemented for `*mut objc::runtime::Object`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `(tao::window::WindowId, tauri_runtime_wry::WindowWrapper)`, the trait `Send` is not implemented for `*mut (Box<(dyn for<'r> Fn(&'r tao::window::Window, wry::webview::RpcRequest) -> Option<wry::webview::RpcResponse> + 'static)>, Rc<tao::window::Window>)`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: within `(tao::window::WindowId, tauri_runtime_wry::WindowWrapper)`, the trait `Send` is not implemented for `*mut (Box<(dyn for<'r> Fn(&'r tao::window::Window, wry::webview::FileDropEvent) -> bool + 'static)>, Rc<tao::window::Window>)`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: future cannot be sent between threads safely
   --> src/main.rs:32:5
    |
32  |     tokio::spawn(async move {
    |     ^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: the trait `Send` is not implemented for `*mut Box<(dyn for<'r> Fn(&'r wry::http::request::Request) -> Result<wry::http::response::Response, wry::Error> + 'static)>`
note: future is not `Send` as this value is used across an await
   --> src/main.rs:34:25
    |
34  |         match task.run().await {
    |               ----      ^^^^^^ await occurs here, with `task` maybe used later
    |               |
    |               has type `&Task` which is not `Send`
...
37  |         };
    |          - `task` is later dropped here
help: consider moving this into a `let` binding to create a shorter lived borrow
   --> src/main.rs:34:15
    |
34  |         match task.run().await {
    |               ^^^^^^^^^^
note: required by a bound in `tokio::spawn`
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.15.0/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ^^^^ required by this bound in `tokio::spawn`

error: could not compile `app` due to 7 previous errors

Additional context
No response

I'd love to help out in debugging/fixing this I am just not sure where to start, so any pointers would be very helpful

same problem here, it works on beta.8 but not on next branch,

Seems like the problem is not on tao or wry, but on tauri-runtime-wry. I'll see what change caused this.

Also, this:

I think that this bug is macOS only

isn't the case either. It's the same on windows.

Caused by #2659. We need a unit test for this, it has happened twice now :|

I think we should force the Send+Sync impl for tauri-runtime-wry types since we're managing the thread usage ourselves on fn send_user_message.


Limit logger output on ALREADY_EXISTS error

Limited logger output when TdiSdeWrapper::InsertTableEntry returns a TDI_ALREADY_EXISTS error.

Downgraded severity to INFO and omitted dump_args() when logging the condition in TdiSdeWrapper.

Downgraded severity to INFO and suppressed error details when logging the condition in TdiTableManager.

The SDE will log BF_PIPE_ERROR when the error is detected. This message is outside the scope of infrap4d.
Es2kNode::WriteForwardingEntries returns a consolidated error code (ERR_AT_LEAST_ONE_OPER_FAILED) if any of the write requests fail.
The net effect of this PR should be to reduce the logger output to:

BF_PIPE_ERROR - duplicate entry found in table...
generic::already_exists: Duplicate table entry (may not be an error)
Duplicate table entry (may not be an error)
StratumErrorSpace::ERR_AT_LEAST_ONE_OPER_FAILED...
Failed to write forwarding entries...

The second and third lines will be suppressed if the logging level is WARNING or above.

We could propagate the error status without logging for lines 2 and 3, but that would be at the cost of reduced context when an error is returned. I think downgrading the severity to INFO and setting the logger severity filter to WARNING is the better choice.

We do not know, at this point, whether the attempt to fix the .severity() modifier was successful.
It is also not clear that the changes to the logging message for ERR_AT_LEAST_ONE_OPER_FAILED were successful.
Notwithstanding which, Sabeel says that this PR has met the immediate its immediate objectives.
The Google Standard of Code Review  says:

In general, reviewers should favor approving a CL once it is in a state where it definitely improves the overall code health of the system being worked on, even if the CL isn’t perfect.

That being the case, I going to go ahead and merge this PR.


using --- automatically trigger yaml syntax even if there was no ` or ```yaml

normal text here
---
everything here is  a yaml syntax

it's a problem because --- is used as a separator.
by the way, thanks! this project makes markdown usable in sublime text

yeah this was a pain initially, I tried to find a compromise but it seems to be a no-win scenario from an implementation standpoint - well, more of a tradeoff...
Since --- is commonly used in front matter - jekyll, assemble, metalsmith, verb, etc, and front matter is used for data, IMHO it's better to err on the side of providing a better experience for users who need to see their data highlighted, versus a separator. Because of this, I personally use ***, instead of---`. It works the same and everyone wins.
That said, I'm totally open to a solution that distinguishes front-matter from other separators in ST. I'm by no means an expert

but maybe there is a hack, the ability to chose what languages supported manually. than we can disable the problematic languages when they're not being used.
also it might be helpful, so we can use built in languages support for this scope. (not sure if it's supported but i believe it is):
{
 "javascript": "js",
 "python": "python"
 ...
}


add_exit_button

Add an exit button in the home sliding menu

I do not understand why people seems to be happy with this feature. Calling System.exit(0) in an Android application is not a recommended practice.
I may missed something...


suggestion: add CBOR encoding/decoding

Deno's stdlib has msgpack support. msgpack and CBOR each have pros and cons compared to each other, but this limitation is what gives me the desire to have CBOR:

maximum byte size of a String object is (2^32)-1

A CBOR implementation alongside msgpack here.
Describe alternatives you've considered
There are third party libraries, but this is something I'd like to see in the standard library.
Another nice thing about CBOR is its support for indefinite length items which is good for streaming.

For the record, CBOR is still streamable with definite length items. Indefinite length items are for streaming content when you don't know the size before starting. Like applying  compression algorithm to some data or converting a file format from one type to another.

In looking into the logistics of implementing this format, CBOR has several types (Integers, Decimals, Byte Strings, Text Strings, Arrays, and Maps), what types should these be converted into in JavaScript, and likewise, what JavaScript types should be acceptable to be converted into these types?
I'm thinking for encoding:
type CborInput = number | bigint | Uint8Array | ReadableStream<Uint8Array> | string | ReadableStream<string> | CborInput[] | ReadableStream<CborInput> | Record<string, CborInput> | ReadableStream<[string, CborInput]>

Integers: number | bigint
Decimals: number
Byte Strings: Uint8Array | ReadableStream
Text Strings: string | ReadableStream
Arrays: CborInput[] | ReadableStream
Maps: Record<string, CborInput> | ReadableStream<[string, CborInput]>

and for decoding:
type CborOutput = number | bigint | ReadableStream<Uint8Array> | ReadableString<string> | ReadableStream<CborOutput> | ReadableStream<[string, CborOutput]>

Integers: number | bigint
Decimals: number
Byte Strings: ReadableStream
Text Strings: ReadableStream
Arrays: ReadableStream
Maps: ReadableStream<[string, CborOutput]>

What are other people's thoughts?

Streaming implementations already in @std:

archive
json
csv

Also looked at the state of DOMParser:

closed issue about DOMParser and others
dealing w/ html in the manual

I did look into the Cbor spec and started working on an implementation of it. So far I've gotten a:

CborEncoder
CborDecoder
CborByteEncoderStream
CborTextEncoderStream
CborArrayEncoderStream
CborMapEncoderStream
CborSequenceEncoderStream

The only one I need to make left is a CborDecoderStream. At the moment this implementation only supports accepting the CborType and CborTypeStream in their respective spaces, and the complex structures you can make with them. I also need to implement some stuff for it to accept dates.
type CborPrimitiveType =
	| undefined
	| null
	| boolean
	| number
	| bigint
	| string
	| Uint8Array
type CborType =
	| CborPrimitiveType
	| CborType[]
	| { [k: string]: CborType }
type CborTypeStream =
	| CborPrimitiveType
	| CborTypeStream[]
	| { [k: string]: CborTypeStream }
	| CborByteEncoderStream
	| CborTextEncoderStream
	| CborArrayEncoderStream
	| CborMapEncoderStream

So an update from my last comment is that I have now made a streaming decoder. I am just in the process of testing everything.
export type CborOutputStream =
  | CborPrimitiveType
  | CborOutputStream[]
  | { [k: string]: CborOutputStream }
  | CborByteDecodedStream
  | CborTextDecodedStream
  | CborArrayDecodedStream
  | CborMapDecodedStream

The last four classes are just extensions of readable streams so you're able to evaluate what type of data will be in the readable stream. These types are only returned for indefinite length items or if the definite length is greater than 2^32


Checkbox state

Continuing our conversation from ydkhatri/mac_apt/issues/13:
I've gotten it up and running. Super exciting! Thanks for the hard work!
When I'm using either the -m or -h args, I get checklist items decorated with the following html:
<div style="103">
Regardless of whether or not the checkbox is checked.

  (Mostly haven't had time to get back to this.)
How do you think a checklist item should be formatted in html or markdown?

I would think markdown. I find this notation pretty reasonable:
https://github.github.com/gfm/#task-list-items-extension-
On Sun, Apr 14, 2019 at 2:35 PM Bill Shannon<EMAIL_ADDRESS>wrote:

Ya, there's a bunch of stuff I haven't tried to handle yet. (Mostly
haven't had time to get back to this.)
How do you think a checklist item should be formatted in html or markdown?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bshannon/savenotes/issues/1#issuecomment-483060291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM9cpq3N7wGPVFnqWtGDiUmMIJ9SSIWks5vg58DgaJpZM4cuaZP
.

(But I can deal with any way of indicating checkbox state)

I just noticed something. When you copy and paste a checklist out of notes, the resulting text follows the GFM convention:
- [ ] Unchecked item
- [x] Checked item

Just to let you know I haven't forgotten about this...
I started working on this, but it's not as straightforward as I was hoping.
I'm having to do more significant work than expected to get all but the
most trivial cases to work correctly.

Ah, bummer. I appreciate the effort!
On Fri, May 31, 2019 at 12:18 PM Bill Shannon<EMAIL_ADDRESS>wrote:

Just to let you know I haven't forgotten about this...
I started working on this, but it's not as straightforward as I was hoping.
I'm having to do more significant work than expected to get all but the
most trivial cases to work correctly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bshannon/savenotes/issues/1?email_source=notifications&email_token=AABT24SRLTNJE7Z5SYWNZBDPYCKHBA5CNFSM4HFZUZH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUCXCQ#issuecomment-497560458,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABT24VQJR3HMI7MGDYJHR3PYCKHBANCNFSM4HFZUZHQ
.

I think I've got it working now.  Try the 1.1 release.

Oh awesome! I’ll give it a try!
On Fri, Jun 7, 2019 at 9:09 PM Bill Shannon<EMAIL_ADDRESS>wrote:

I think I've got it working now. Try the 1.1 release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bshannon/savenotes/issues/1?email_source=notifications&email_token=AABT24WFAVYX4QPAICK7AB3PZMWG3A5CNFSM4HFZUZH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXHMZIY#issuecomment-500092067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABT24UWFUTKLSFJFZORU2TPZMWG3ANCNFSM4HFZUZHQ
.

Working! Thank you!!


Add "Items Kept on Death" item examines to Examine plugin

Do you mean show if the item will be kept or lost on death via the examine options?

No, I mean if you examine the item, it doesn't show item price

Apparently the menu option for that interface is "Item:", not "Examine" :upside_down_face:


set ELASTIC_APM_ACTIVATION_METHOD in code rather than values.yaml so it works for custom webhookConfig.agents.* names

Currently ELASTIC_APM_ACTIVATION_METHOD is set in webhookConfig.agents.{name} in the chart's values.yaml. E.g.:
webhookConfig:
  agents:
    java:
      image: docker.elastic.co/observability/apm-agent-java:latest
      artifact: "/usr/agent/elastic-apm-agent.jar"
      environment:
        JAVA_TOOL_OPTIONS: "-javaagent:/elastic/apm/agent/elastic-apm-agent.jar"
        ELASTIC_APM_ACTIVATION_METHOD: "K8S_ATTACH"

An issue with setting the envvar this was is that a custom webhookConfig.agents. name requires one to repeat that envvar. As noted at https://www.elastic.co/guide/en/apm/attacher/current/apm-webhook-add-pod-annotation.html

The only webhookConfig.agents values defined in values.yaml are java and nodejs. When using other values, you must explicitly specify image, artifact, and *OPTIONS values.

Instead, it would be more helpful to set that envvar always in the webhook code, then the config becomes simpler.
One requirement of doing this is that we need to use a common value for all APM agents. We decided to use the value currently being used by the Java agent: K8S_ATTACH. That means that new versions of the Node.js and .NET agents will be needed that support ELASTIC_APM_ACTIVATION_METHOD=K8S_ATTACH. I plan to change the Node.js APM agent to support both values so that the newer APM agent will work with current and newer versions of the Helm chart.

/cc @elastic/apm-agent-node-js  @elastic/apm-agent-net


README.md file of Website update

Website
In simple words, we can describe a README file as a guide that gives users a detailed description of a project you have worked on.
It can also be described as documentation with guidelines on how to use a project. Usually it will have instructions on how to install and run the project but we're already worked on it which is the main README file our project.

This  section contain information of website like how's your website look like, you can see instructions videos, layers section and lots of images that are used to make website and lot more options

and this website section also contain files like html, css, and js by which you can make necessary changes in this project

Hey @SaptarshiSarkar12, can you check it again...is there any correction required please let me know

@SaptarshiSarkar12 commit suggested changes, it would be awesome if you check it


Create a branch for norESM

Several outstanding branches contain code that is necessary for the interface with norESM. Until these are all pulled into main it would be good to have a single branch that contains all of the relevant changes. This would provide a working target for the norESM coupling development which should be largely unchanged when all of the relevant code is finally combined into developand main.

Derive from the branch jun23_demo when that is complete and clean.
Merge a ModelArrayRef version 3 branch. topaz_era_mar3

The required branch has been created: aug23_mar3


3D anatomical structures animation

3D anatomical structures animation

GIFs are needed for the HRA Dashboard specification's Data page.

Male and female organ expansion and collapsing, ideally in a perfect loop.

Resources

Figma comment thread: Animation discussion
Figma design file: Data Dashboard

@LibbyUX
Can you please also tag Ushma in this TODO? I will work with her.

Yes, @andreasbueckle! I will assign her as soon as she accepts the invite for this repository. Thanks so much!

Per conversations today: we may use the organ icons that Ushma has designed. More on this before EOB May 10th.

Update: This issue may be closed as not planned.
We are not doing animations for this component, and we may not have this component at all. I will follow up here as the flexible spec evolves for Dashboards.


JAV-2 [Github #226] MosaicDefinition refactoring

MosaicProperties removed
New MosaicFlags class added
Made duration mandatory
Fully matching E3 mosaic schema
Fixed tests

Pull Request Test Coverage Report for Build 654

17 of 17 (100.0%)  changed or added relevant lines in 6 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 69.031%

Files with Coverage Reduction
New Missed Lines
%

src/infrastructure/MosaicHttp.ts
2
52.5%

Totals

Change from base Build 651:
0.1%

Covered Lines:
6274

Relevant Lines:
8373

💛  - Coveralls


skip plugin test on non x86 architectures

Because the plugins in dockerhub aren't multi-arch, they will
fail on non x86-64 platforms. Comment this test out like we do with
the others.
should fix the p, z and an issue on the arm CI
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

windows failure and z failure are known flakey ☹

Yeah a bug has already been filed. So this is independent to this change. Which does the right thing.


Fix TypeScript scriptPath on Windows

scriptPath in function.json should always be in posix format
/cc @duncan

@anthonychu I have a guess - but can you confirm why this change in necessary?

Becomes an issue when collaborating with folks on macOS/Linux or deploying to Linux. And func new generates posix paths here on all platforms so this would match that.

It's all about the x-platform experience. In my case, I hit this faster than you might expect when I created a function using VSCode on Windows using WSL. "scriptFile": "..\\dist\\..." means that the function won't run locally when in Bash. Of course, flipping the slashes around to /` fixes everything.


Bug Report: Unintended text updating

Environment
Windows build number: 18362.239
Windows Terminal version: Latest from the microsoft store

Steps to reproduce
Open an application like ranger and browse around.
Expected behavior
Only the intended text updates.
Actual behavior
The intended area updates, but other areas update too garbling the UI.
Ranger:

Emacs:

What distro are you running, and could you share the output of infocmp?

I'm running Debian. Here's the ouptut of infocmp: output.txt.
At the time the issue was with the terminal only, it worked fine on both wsl.exe and conhost.exe. However when I tried to replicate the issue again today I'm no longer able to replicate it on windows temrinal. Maybe a restart had something to do with it.

I've had some issues with emacs in the last 24 hours. I had three erc buffers open and my terminal rendering was way off. It printed a newline character but jumped to the beginning of the terminal emulator on the left side and not to the middle of the buffer.
My guess is that terminal/conhost2 has a special case in which a newline will always jump to the beginning of the terminal emmulator line and not to the beginning of the multiplexed terminal line.
In terms of newline windows terminal should always default to the ansi compliant way of moving the cursor and printing.
Furthermore, some programs have different issues with ansi-compliance. It is important to prioritize them from most used to least.
Vim and emacs are some of these. They need the terminal to be rendered absolutely properly because of the insane style of text editing they both do.
The best program to look to in terms of ansi compliant terminals is probably tmux. tmux it not a terminal emmulator per se but it gets everything right in terms of how it renders things.

The OP issue is no longer reproducing. Closing.

For the record, there is another issue tracking the emacs issue - #1474 is probably the issue you're describing.


sync to live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/windows-iotcore-docs, working directory: W:\ussj-s, target branch: live, target branch commit: 003b85ce80a874f4b7335bd34810b17bbdbec703, source branch: master, source branch commit: .

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/GetStarted.md
:white_check_mark:Succeeded

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/connect-your-device/SSH.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboard.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboardLayouts.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/SignInDialogTitleBars.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/WakeOnTouch.md
:white_check_mark:Succeeded

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded

windows-iotcore/release-notes/CurrentInsider.md
:white_check_mark:Succeeded

windows-iotcore/release-notes/Insider/17744.md
:white_check_mark:Succeeded

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


Iron Ore & Coal

🚀 Feature Proposal

Either add the Ring of Forging or remove the 50% chance to fail smelting iron ore. At current iron ore is not even worth the time smelting.

Any decent way of obtaining coal - right now smithing is completely bottlenecked by the lack of coal supplies in the game. Aside from mining it, zulrah is the only reasonable way to get it.

iron fail chance follows the game, that will not be changed, ring of forging will likely become an option when enchanting gets released
coal is also normally difficult to obtain without 50k f2p bots mining it all the time so i dont think mining rates should be changed just to let you smelt more


[1.2] kill k8s latest boskos resource

We used to have dedicated boskos resources for the "Latest" GKE version. At the time this was 1.11, and other tests ran on 1.10.
Today, we cannot even create a 1.10 GKE cluster, since they bumped the minimum version, so we can just consolidate these to save on the number clusters we have.
This will fail until https://github.com/istio/test-infra/pull/1953/files is merged

/test integ-mixer-k8s-presubmit-tests-release-1.2


getting an issue after downloading a continent

Hi, I seem to be getting this error when I download a continent. This happens when I launch xp after installation.

Did you click run and get the Firewall Window that asked for allow?


oauth2:OutboundOAuth2Provider is not renewing access token when downstream web API returns 403

Description:
We are using Azure log analytics REST API and authenticate requests using client_credentials grant type with https://login.microsoftonline.com as the token endpoint.
We noticed that Azure log analytics REST API returns an HTTP response with403 status code and the below payload when the token is expired.
{
    "error": {
        "message": "The provided authentication is not valid for this resource",
        "code": "InvalidTokenError",
        "innererror": {
            "code": "InvalidTokenError",
            "message": "Could not validate the request. Challenge failed: TokenExpired"
        }
    }
}

Due to this (not received 401 response), the oauth2:OutboundOAuth2Provider is not attempting to renew the token, instead uses the same expired token.
Affected Versions:
Ballerina Swan Lake Preview 2

@madushajg Shall we verify the issue with the attached .jar in SLP5?
oauth2-ballerina-1.0.1.jar.zip

@madushajg Shall we verify the issue with the attached .jar in SLP5?
oauth2-ballerina-1.0.1.jar.zip

Ack. Will verify with the provided jar.

@madushajg Shall we verify the issue with the attached .jar in SLP5?
ballerina-oauth2-1.0.1.jar.zip

@ldclakmal The issue is not there with the provided .jar

This issue is fixed with https://github.com/ballerina-platform/module-ballerina-http/pull/142 and no longer valid with the new design.

This issue is fixed with https://github.com/ballerina-platform/module-ballerina-http/pull/142 and no longer valid with the new design.


chore(main): release 0.1.3

:robot: I have created a release beep boop
0.1.3 (2024-01-12)
Bug Fixes

workaround for multiplatform/gradle 8 signing bug (92ccf38)

Miscellaneous

main: release 0.1.3-SNAPSHOT (6b4a337)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/momentohq/client-sdk-kotlin/releases/tag/v0.1.3 :sunflower:


Updating the TODO on the chartResetButton

Ran into this issue today, not having a strongly defined theme for the reset zoom button.
Didn't go any further than the first level as the states are branches of HTML elements which are not highcharts specific.

@klexas thanks mate!

note
http://api.highcharts.com/highcharts#chart.resetZoomButton


Fix NDEBUG unsetting issue

From @benvanik:
RelWithDebInfo should set NDEBUG by default. I think there's something (LLVM?) unsetting it. We really need to fix that - it's very unexpected behavior (and would break anyone integrating IREE into their project that is assuming the default cmake behavior of RelWithDebInfo/Release sets NDEBUG).

I touched this in #3370 but forget if this was a followup for that or dupe. Needs investigation.

Looking into it

Disabling IREE_ENABLE_ASSERTIONS causes a build failure due to a PDL code. (PatternMatch.h:1100)
After guarding the problematic code with not defined(NDEBUG), the compilation error went away, but now I got this error:
[968/1146] Generating simple_mul.h, simple_mul.o, simple_mul.vmfb
FAILED: samples/static_library/simple_mul.h samples/static_library/simple_mul.o samples/static_library/simple_mul.vmfb /usr/local/google/home/okwan/iree/build/samples/static_library/simple_mul.h /usr/local/google/home/okwan/iree/build/samples/static_library/simple_mul.o /usr/local/google/home/okwan/iree/build/samples/static_library/simple_mul.vmfb
cd /usr/local/google/home/okwan/iree/build/samples/static_library && /usr/local/google/home/okwan/iree/build/tools/iree-compile --iree-mlir-to-vm-bytecode-module --iree-hal-target-backends=dylib-llvm-aot --iree-llvm-link-embedded=false --iree-llvm-link-static --iree-llvm-static-library-output-path=simple_mul.o /usr/local/google/home/okwan/iree/samples/static_library/simple_mul.mlir -o simple_mul.vmfb
malloc(): corrupted top size

I had to turn off LLVM_ENABLE_ASSERTIONS=OFF too. Need to double check with a fresh build.


Standardize Image Resizer naming

Following names are currently in use

Image Resizer: Used in the Enabled field in the global settings file at %userprofile%/appdata/local/microsoft/powertoys/settings.json
ImageResizer: Used in folder name to store settings in %userprofile%/appdata/local/microsoft/powertoys

This change will not be backward compatible but will ensure a consistent naming between module key associated with runner and folder naming on disk, similar to other modules.

This change will not be backward compatible

That's why the old version is uninstalled with every update, not?

@Jay-o-Way
the uninstaller doesn't remove the settings folder, we can add code to detect if the ImageResizer folder is present in the settings folder and rename it to Image Resizer if Image Resizer is not already present and delete it if Image Resizer is already present.
This will only break backwards compatibility if the user uninstalls the current version and installs an older version.

This is fixed in 0.53, get it at https://aka.ms/installPowerToys


chore: Add release branches to the playbooks for release 24.7

hmm, there's an error that perhaps @fhennig needs to check out
https://github.com/stackabletech/documentation/actions/runs/10165503435/job/28113439427#step:5:22


Updates i've made using this extension in my projects.

Renamed $_table to $table_name;
$log_user set to TRUE by default;
Concatenate table name with the column name to avoid ambiguous
queries errors in order_by(), find(), find_all() using join();
Included empty_table() method;
Fixed user logging on insert() and update();

you can have a try,if use  public function count_all_results() {  $this->dbr->count_all_results($this->table_name); return $this;} the result is object,


Expose trackStyle prop in inner slider.

Expose the trackStyle prop to add inline styles to slick-track div.

You can add css with classname slick-track

I think this is needed other than the classname.
Considering you want to add multiple instances dynamically. Rather than adding class name one by one. Each easier to just pass the styles itself specially if you are using external css.


Layout Update operation doesn't work on existing 16.2 layout

Similarly to #1385, I'm still preparing offline layout packages for use within my organization (to save bandwidth), and it worked ok until now.
Going from an existing 16.2 layout, attempting to run vs_Enterprise.exe --layout "path\to\layout" errors out:
Visual Studio Setup Command Line Utility, version 2.3.2276.2797
c Microsoft Corporation. All rights reserved.

Download of 'https://aka.ms/vs/16/release/channel' succeeded using engine 'WebClient'
Download of 'https://download.visualstudio.microsoft.com/download/pr/1d102ee6-9263-4353-8676-6430f0cc5998/53e26f3ff75e1f860c7528b99ce05b7d391578094bfd88faec5630b445284c34/VisualStudio.vsman' succeeded using engine 'WebClient'
Catalog load operation correlation: {"id":"b3f095d7-a11b-4947-b728-61a55f4af23a"}
UpdateLayout operation correlation: {"id":"1d42adda-a00e-44fe-9794-c1eb53bb88e0"}
Planning 'UpdateLayout' operation
Error: The package 'Microsoft.NetCore.ComponentGroup.DevelopmentTools.2.2' is not recognized.
Error: Failed to plan for UpdateLayout.
Error: Setup completed with errors.
Error: The package 'Microsoft.NetCore.ComponentGroup.DevelopmentTools.2.2' is not recognized.

16.3 only just released (with all the announcements at DotNetConf, including .NET Core 3), so I'm wondering if this is just temporary or some other issue.
I've also redownloaded the setup utility to verify it is the most recent (and yet running it still insists on downloading yet another one), no change.

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

ID: dc51a257-b7a9-4660-7e12-88cdfcd9cd53
Version Independent ID: dad2fd97-7244-6802-e853-5d5974838996
Content: Update a network-based installation - Visual Studio
Content Source: docs/install/update-a-network-installation-of-visual-studio.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@BhaaLseN -- Bhaal, thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/
As well, you might also consider using the Report a Problem tool to report the issue.

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.

I understand this is closed, but I had the similar issue.  I updated the 2.2 to 2.1, issue was resolved.
My question to the OP is; do you use a custom.json?

Nope, I've been using vs_enterprise.exe --layout "path/to/layout" --add payload.names to create it from scratch, then vs_enterprise.exe --layout "path/to/layout" for all subsequent runs (at least until the point where packages are removed, and the layout update just throws the errors mentioned above).
I wanted to use an expected settings.json once but this isn't supported by the layout operation.

I felt comfortable changing it from 2.2 to 2.1 when I didn't locate a "2.2" pkg here:
https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-professional?vs-2019&view=vs-2019
This was in process and just now completed successfully.  Funny how I did a verify before updating and came back "clean".

Same, except that I already had 2.1 in that list; and having it twice felt weird.
Verify also worked just fine.

One question if I may.  My version I has of vs_professional.exe was 16.2, never updated?  I downloaded it again and it is 16.3.  I wonder if I can replace it?
Question is, did your vs_enterprise.exe update?

I tried both the one that was in the layout folder, the one that was named vs_setup.exe instead and a newly downloaded one. Neither worked, which is why I finally opened this issue (and afterwards another one on the developer community; which was shot down as well with the resolution "just make a new layout").
Since my coworkers were eager to update I just caved and made a new layout in the end 🤷♂


Looks reasonable to me


API Access

Hi and sorry for using issues to communicate here but I've not had any response after contacting support through the website chat.
I registered for API access a couple of weeks ago and have heard nothing since. Not sure if there's supposed to be any kind of email confirmation after registration but haven't received anything like that.
Is this API access still a thing?
Can anyone point me to someone I can contact about it?
Thanks in advance.

@damianpeterson - sorry for the late response. The API is still working and we processed the registration on the 7th July. Can you please check your spam folder of your email address you used to signup for Electric Kiwi for a response from<EMAIL_ADDRESS>to your registration?
The email has your client id and secret and some information about what to do and how to develop an app using our API.
If you don't find the email there - can you message us and we will resend the email.
Cheers, Matt

Strange. I don't have anything from EK from that time period. Spam or otherwise. It's possible I entered my email address incorrectly. Can you try resending it? My email address is my first name dot my last name .nz

@damianpeterson - I will resend the registration in the next 5 minutes ...

@damianpeterson - just sent it ... let me know if it is received else I will look to alternate ways to get you the details.

Perfect. Got it. Thanks!


Remove version: taers232c.GAMADV-XTD3 version 6.72.08

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.72.08/gamadv-xtd3-6.72.08-windows-x86_64.msi
OK
(Automated message - build 910)


fix(ui): do not show duplicate entries if not installed by gallery

Description
This PR fixes https://github.com/mudler/LocalAI/issues/3011

my listmodels PR was also intended to provide a related solution to this - I'll merge things either way, but I think the SKIP_IF_CONFIGURED flag in that PR will accomplish this as well.

got it - this PR is aiming just at fixing the bug that I noticed today when importing a model, there are other bugs yet that needs special addressing that'd make room for another patch release


Implement # 223 -- Create notices to report suspicious numeric values

Summary:
This PR provides code to report suspicious numeric values as warnings.
Expected behavior:
Two new notices are created. This PR includes support to export their content as Json or proto files.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "Fix #<issue_number> - " (for example - "Fix #1111 - Check for null value before using field")
[x] Linked all relevant issues
~[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)~

This PR is no longer valid. Specific use case will be implemented for each numeric field.


fix(cli): org:search:dump issues when dump is fetched across multiple queries

Proposed changes
Context:
The org:search:dump command executes queries under the hood. When we execute this command, it's possible that we hit the Search API maximum response size. The likelihood of hitting that limit is increased in the HIPAA environment, as the HIPAA maximum response size is 4x smaller than in PROD.
When the dump is executed across multiple queries, we ensure that results are fetched from the same index by passing the indexToken of the initial query to each subsequent queries. This is, be definition, incompatible with using the index cache, as stated in the indexToken parameter documentation:

The Base64 encoded identifier of the index mirror to forward the request to. See also the index parameter.
If you do not specify an indexToken (or index) value, any index mirror could be used.
Note: Passing an indexToken (or index) value has no effect when the results of a specific request can be returned from cache (see the maximumAge parameter).

Another issue is that in order to know what result to start from in each subsequent query after the first, we request results to be ordered by ascending rowid value, and we request only results whose rowid is greater than the rowid of the last result returned in the previous query. However, the rowid value is returned as a very large integer (greater than the maximum safe integer size JavaScript can handle without losing precision). Therefore, the expression rowid>ROW_ID_OF_LAST_RESULT typically behaves like rowid>=ROW_ID_OF_LAST_RESULT because JavaScript rounds the rowid during the JSON.parse conversion of the response body.
Fix:

Setting maximumAge: 0 on every query performed for fetching source dumps trivially addresses the index cache issue.

Passing a custom response handler to the platform client that uses the new context parameter of the JSON.parse reviver (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#parameters) allows us to avoid losing precision when converting rowid values. However, this new parameter is only available from Node 21, so we have to polyfill it for now.

Breaking changes
None
Testing

[ ] Unit Tests:

[ ] Functionnal Tests:

[ ] Manual Tests:

I moved the bulk of the changes to the platform-client project: https://github.com/coveo/platform-client/pull/834
So basically all I'm doing in this PR now is setting maximumAge: 0 on dump queries.


Input Field Number - placeholder is shown instead of value (0) when readonly is true

Step-by-Step Guide to reproduce

Open Input Field Number in Storybook
Set a value = 0
Set readonly to true
See that value is not shown

If a different value is set than 0, the bug is not occuring.

Bug Description / False Behaviour
When the Input Field Number has a value and readonly=true, it does not display the value.

Correct Behaviour
When the Input Field Number has a value and readonly=true, it displays the value.

Testing
Check existing unit tests of the component(s) and adjust the tests to prevent this bug from occurring again in the future, if you see a way.

Background

When a placeholder is set, the placeholder is shown, even in readonly state.

Hi @thrbnhrtmnn ,
Since it's related to my last PR I had a look.
The reason that value is being reset here to placeholder  or if we remove the condition I introduced in my last PR then to 0 is when readonly or disable or any other parms is set, it rerenders with a new instance with default params hence overwriting the existing set values.
For example if we set the value to 24 in defaultParams, then on readonly set to true, the value will be reset to 24 instead of the placeholder.
So, this is just not the case with readonly but with all the parameters even when you change the theme from light to dark.
Maybe I am missing something here but let me know what do you think.

@usmanreal1 i think this is how storybook does things. instead of changing one attribute on the web-component, it replaces the thing with an entirely new instance.
in order to determinate if that's the issue here, we could place the number input into the example app and see how it behaves over there. i would suggest to give this a shot. if you need any help with that, you can write here :)

in order to determinate if that's the issue here, we could place the number input into the example app and see how it behaves over there. i would suggest to give this a shot. if you need any help with that, you can write here :)

@ChristianHoffmannS2 could you maybe explain to me what expect from that approach of putting the input into the example app.
Should I just put the current input into the example app with the readonly state and see if it behaves accordingly?


Error: Invalid: File is smaller than indicated metadata size

I get the above error when attempting  to read in a file with read_feather()  which I have been doing on a daily basis without issues
I believe this is probably as I have upgraded to the recent new version of feather
looking at RStudio blog, it does say feather files should not be used for long-term storage so completely my fault (although it would be a nice feature) . However, i reinstalled the 0.0.1 version and still get the same error
Is there anyways around this?

Can you provide a reproducible example or an example file? Also, can you give information about your platform?

Thanks for swift reply. I have tried a toy example - creating in old feather version and reading back in update but cannot replicate error. The real-world file is 214MB. I was just hoping the error message would be a clue
library(feather) #0.0.1
library(tibble)

test_df <- tibble(a=c(1,2),b=c("a","b"))

write_feather(test_df,"problem.feather")
df <- read_feather("problem.feather")

library(feather) #0.3.0
df <- read_feather("problem.feather")
#This Feather file is old and will not be readable beyond the 0.3.0 release

# The file I want to read
df <- read_feather("data/allCranLogs.feather")
#Error: Invalid: File is smaller than indicated metadata size

sessionInfo()

R version 3.3.1 (2016-06-21)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows >= 8 x64 (build 9200)

locale:
[1] LC_COLLATE=English_Canada.1252  LC_CTYPE=English_Canada.1252
[3] LC_MONETARY=English_Canada.1252 LC_NUMERIC=C
[5] LC_TIME=English_Canada.1252

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] feather_0.3.0

loaded via a namespace (and not attached):
[1] assertthat_0.1 hms_0.2        tools_3.3.1    tibble_1.2     Rcpp_0.12.6

Any chance you can share the real world file with me privately? It may be malformed (we fixed a number of bugs related to file handling on Windows) -- my e-mail is wesm at apache dot org

I have managed to locate a slightly earlier version of this file which should save me having to recreate from scratch as it appears as though the other one did get malformed somehow.
The real world file is very  big for email so maybe unless this issue arises again - with me or someone else - we can call it a day. Thanks again for responding on a Sunday

Feel free to send a Dropbox or Google Drive link if you want to share that way


:lipstick: UI and language fixes in Control Panel

[x] Review and fix language and grammar, ensuring tone, branding

An example of this would be the bucket message, it read a bit informal

We are on the edge of hitting the limit of AWS S3 bucket (1000).
Before we implement the long term solution, could you make sure you remove the buckets you do not need any more? also make sure not create more buckets than your need, try to use sub-folders to manage different datasets rather than multiple buckets.

[x] Review and fix links to Slack and user guidance
[x] Remove link to AP Grafana, its broken
[x] Remove emojis from UI, for accessibility
[ ] Check user session length

Extend so that the user is not forced to log in so often?
Or add automatic redirect to login from the "Your session expired" page

Language has been reviewed and reworded where appropriate
Removed broken Grafana link
Changed slack support links to Github support request page
Removed emojis

The current session length is a setting in control panel, OIDC_RENEW_ID_TOKEN_EXPIRY_SECONDS, rather than Auth0. It is currently set to 1 hour. This can be lengthened or shortened depending on security policy.


Apply changes from trac ticket 103.

See http://cf-trac.llnl.gov/trac/ticket/103
@rhattersley Opinion of my interpretation?

Thanks @mo-g ... looks very promising. Would you mind creating a back-link on the trac ticket (e.g. as at http://cf-trac.llnl.gov/trac/ticket/71#comment:4).

Other than the tiny issue of a single comma ... all good. :+1:

Pushed the comma change, applied for a trac account.
Cheers,
Gray.

Super, thanks @mo-g. :+1:
I'll merge this once #71 has been merged.

Sorry, I forgot that there's one more thing to do: the change needs a corresponding addition to the "Revision History" appendix. I'm trying to clarify (via a separate e-mail thread) what date to use, but if you're keen then I'd suggest starting with the date you applied the changes (i.e. now-ish), rather than the dates from the trac ticket.

I'm trying to clarify (via a separate e-mail thread) what date to use, but if you're keen then I'd suggest starting with the date you applied the changes (i.e. now-ish), rather than the dates from the trac ticket.

Please do use the date you applied the changes. I've had clarification from @JonathanGregory:

Yes, the date when the change was applied would be fine.

Rebased to current master. ;)

Hi Richard,
I think this is ready to merge. Are you happy?
Cheers,
Gray.

Thanks @mo-g :+1:


Allow for quoted empty strings with double-quotes (fixes #16)

@andyjansson I have also added explicit task for regenerating parser.js to package.json so it is easier for people to contribute


Konnected hardware support WP2 Personal (AES) or WPA3 authentication?

Currently I can use it with WPA AES+TKIP which not too secure...
Thank you

Sorry, WPA3 is not available at this time. Konnected supports WPA2 authentication.
It would be dependent on the chip-maker to support WPA3 in the underlying SDK, which may or may not ever happen.


Build error using MSVC

Steps to reproduce:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat"
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DJPEGXL_ENABLE_PLUGINS=OFF -DBUILD_TESTING=OFF -DJPEGXL_WARNINGS_AS_ERRORS=OFF -DJPEGXL_ENABLE_SJPEG=OFF ..
nmake

Error message:
C:\Devel\libjxl\third_party\skcms\skcms.cc: fatal error C1083: Cannot open include file: '"C:/Devel/libjxl/lib/jxl/enc_jxl_skcms.h"': No such file or directory
File C:\Devel\libjxl\lib\jxl\enc_jxl_skcms.h exists.

Is it maybe the issue that it is quoted? Could you try removing the " around the filename in third_party/skcms.cmake:35?

When I removed the quotes it started to work.


[BUG] RUSSIAN localization didn't work properly

Describe the bug
A clear and concise description of what the bug is.
ru localization translates half of the text
To Reproduce
Steps to reproduce the behavior:

Create a world.
Start a world

Expected behavior
A clear and concise description of what you expected to happen.
I expect russian localization
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Browser [e.g. chrome, safari] Vivaldi
FoundryVTT Version [e.g. 22] 11.315
Foundry-V5 Version [e.g. 22] 4.2.1

Additional context

Hello! It seems you're using the Russian localization module, which offers a separate localization from our now-built-in Russian localization. I've confirmed there's issues with it and the World of Darkness localization.
If you are using that module for Russian localization, my recommendation would be the following:

Go into your "FoundryData" folder.
"Data"
"modules"
"ru-ru"
"i18n"
"systems"
Delete the vtm5e.json file
Restart your game

Hope this helps! I honestly don't think I can fix this in the system itself, but as we now officially support Russian localization in the system, I would go to the module developer and ask them to please remove vtm5e translations on their end or to fix it so that it doesn't interfere with the system.

Hello! Just an update, I finally narrowed down the issue of what was conflicting between the Russian localization module and the WOD5E system. The latest update should be compatible with the Russian localization module: https://github.com/Rayji96/foundry-V5/releases/tag/4.4.0


[Bug] [ChatKnowledge] RuntimeError: probability tensor contains either inf, nan or element < 0

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Linux
Python version information
3.10
DB-GPT version
main
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[X] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[X] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
GPU：Count 1 Memory 46G
Models information
LLM_MODEL=yi-34b-chat-8bits; EMBEDDING_MODEL=text2vec
What happened
The error occurs when I attempt to generate output using the model. Here is the full error message I received:
RuntimeError: probability tensor contains either inf, nan or element <
This error seems to happen during the generation phase in the transformers library. I suspect it might be related to the input data or model parameters, but I'm not entirely sure.
What you expected to happen
ChatKnowledge can generate output message.
How to reproduce
Build a knowledge base and ask questions
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

it seems like a llm problem, what llm you use ?

The LLM MODEL I use is yi-34b-chat-8bits. I met this problem when I try to use DB-GPTv0.5.0 yesterday. But when I used the same operation for deployment and configuration, my local DB-GPTv0.4.6 and 0.4.3 can generate answers normally. So I think it might not be LLM's problem? I haven't had time to study v0.5.0 carefully. So I want to know if there are any changes in LLM generation module? I'm wondering if any of you have ever encountered this problem.
Thank you for your attention and looking forward to your reply!

------------------ Original ------------------
From: @.>;
Date:  Wed, Mar 6, 2024 09:12 AM
To: @.>;
Cc: @.>; @.>;
Subject:  Re: [eosphoros-ai/DB-GPT] [Bug] [ChatKnowledge] RuntimeError: probability tensor contains either inf, nan or element < 0 (Issue #1255)

it seems like a llm problem, what llm you use ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@YuansuHao  What is your transformers package version?

Thank you for your attention. My transformers package version is transformers 4.37.2. After submitting the problem to you, I tried to change to an LLM (chatglm3-6b), and then the problem was solved. I thought there might be a compatibility issue with yi-34b-chat-8bits(the LLM I used before).

------------------ Original ------------------
From: @.>;
Date:  Wed, Mar 6, 2024 11:04 AM
To: @.>;
Cc: @.>; @.>;
Subject:  Re: [eosphoros-ai/DB-GPT] [Bug] [ChatKnowledge] RuntimeError: probability tensor contains either inf, nan or element < 0 (Issue #1255)

@YuansuHao  What is your transformers package version?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

My transformers package version is transformers 4.37.2. I later tried to change to an LLM (chatglm3-6b), and then the problem was solved. I thought there might be a compatibility issue with yi-34b-chat-8bits(the LLM I used before).

It is ok for me with transformers 4.37.2.
Can you try again with following env:
LLM_MODEL=yi-34b-chat-8bits
QUANTIZE_8bit=False
QUANTIZE_4bit=False

I tried, but it still doesn't work.

Message ID: @.***>

so,how do you solve this problem.now i have same problem


Terminal is not start

I reinstall it but terminal not start:(

Thank you for reaching out to use with this issue report.
Please do not ignore the issue template fields in future, this sort of disregard isnt helpful in any case, in this instance the issue is well know, and, many duplicates to #700 have been filed including yours.
There is a workaround (for Windows only), its been posted in this issue https://github.com/platformio/platformio-atom-ide-terminal/issues/760#issuecomment-517757440 < click that.
Thanks for your understanding.


Support "Create branch" link form Jira

The link in Jira sends to Bitbucket instead of Github

Any planning for creating a branch in Github?

Hi @arieteter and @mikhaelsantos. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
This is something my team is actively working on. Due to several factors while we are in the process of the migration, we won't be able to merge our changes for 'create branch', but plan to deploy as soon as we have full ownership of the app. Stay tuned 😄

Any update on this issue?

@rbehle Very sorry for the wait.  It's been quite hectic here while we try to migrate the app to full Atlassian ownership.  This sadly fell through the cracks in that process.  We are very close to completing the migration work and we can continue the work done for this.  My estimate would be that it would be done in the next few weeks - migration first, then this would be a quick win as we already have most of the work already done.
Thanks for your patience.

@mboudreau Appreciated

Really would appreciate this feature, create the branch from jira and get the branch <> issue linked! any news regarding this?

@mboudreau Any ETA on this issue? Developers keep asking about this feature.   ;)

Hey @tykim-hd, @ricardf, @lucduong, @rbehle, @arieteter, and @mikhaelsantos. Apologies for the slow movement on this. Post-migration the team has had to focus on some reliability work but we are now able to start picking up feature work. The stream of work for this hasn't been assigned to anyone on the team yet but I know it is one we want to start focusing on soon.
Thanks for your patience. I will update here again when I have more information.

Any update on this matter please ? we really need this feature ! I appreciate if you could provide an estimate date for delivering this feature ? we are all awaiting for create branch within Jira for Github repo  !

Hi, sorry for the radio silence.  We've been hard at work trying to improve reliability and scalability for our customers and haven't had the time to concentrate on the create branch functionality.  We are having internal talks about it - we had a design review for it just a few days ago - to try to consolidate the experience between the Bitbucket and Github create branch.
I think this might be a long term approach though and doesn't solve your current issue.  We might look into create a short term solution to get the functionality working first before improving upon it further.  I'll bring this concern with the team to see where the prioritization should be.
Cheers.

mboudreau, thanks for the update. It's encouraging to hear that it's being discussed.  We are committed to Jira Software and look forward to this feature.

I notice that the Create Branch feature of the GitHub for Jira integration has changed.  It now provides you with a git command to generate a branch on your machine. It's a nice step forward (see image). @mboudreau is this the short term solution you were proposing?  Still keen to see this integration create a branch in the GitHub repo.

Hey @tony-stecca-d2l,
this is a general improvement to the "Create Branch" functionality that was made independently from our own plans.
We still have the "create branch" support for GitHub in our scopes. We want to explore a solution this quarter and implement it next quarter. That's the plan, at least :). Sorry, I can't promise more right now :(.

Any status on this?  According to this Atlassian video it looks like it should be working but I can't get it to work.

Any status on this?  According to this Atlassian video it looks like it should be working but I can't get it to work.

The part or the video is working. What is missing is the Create GitHub button (we only have gitlab and bitbucket options).

Would be great to see when will this be available

Love the create branch shortcut. We would like to customize the branch name suggested to match our naming strategy.  What's the right way to give feedback on adding feature?
Also added a +1 to https://jira.atlassian.com/browse/JSWCLOUD-22152

Sad to see that this is still not implemented :-(

Love the create branch shortcut. We would like to customize the branch name suggested to match our naming strategy. What's the right way to give feedback on adding feature?
Also added a +1 to https://jira.atlassian.com/browse/JSWCLOUD-22152

Fyi

Love the create branch shortcut. We would like to customize the branch name suggested to match our naming strategy. What's the right way to give feedback on adding feature?
Also added a +1 to https://jira.atlassian.com/browse/JSWCLOUD-22152

FYI - instead of +1, please use the vote option

Hey all. Thanks for your patience on this one. We're officially kicking off work next week to support Create Branch for GitHub.

Hey again. Just a quick update. The team working on this is very close to wrapping up and then will start rolling this out in prod. Will update again when that's done.

@rachellerathbone glad to hear this! Will it take into account which repo "should" be associated with a project, so that the branch is created in the correct repo? #585

Hey @timothywlewis. Yes 😄 When you click the create branch link, you'll be navigated to a screen where you will select the org and repo you want to create the branch in. Keep in mind, you'll only see the orgs you've connected to via our integration, and the repos you've given permissions to.
We're keeping our fingers crossed this will start rolling out tomorrow. Waiting on a couple of things on the Jira side of things but we're very close 🙏

Hi @rachellerathbone, any updates on this? Thanks :)

I think a couple of weeks ago I saw this flash up for a moment or two on my Jira instance. It disappeared after an hour or so. Assuming this was intentional and this still hasn't rolled out?

Hi @rachellerathbone
Is this feature rolled out yet ? Because we cannot see it in
We would love to know updates / ETA for this feature.

Cool, that looks great! This is for the cloud version right? is there any plan for the Data Center version of Jira?

@rachellerathbone I just checked, and it is working but it is not using the format I have set!

It seems like we should be able to configure the template for the branch name - but it isn't being honoured, and always uses -
Doesn't matter what template I try to use (with the collection of possible fields) - the url that 'create branch' navigates to is always
https://github.atlassian.com/github/create-branch?issueKey=xxx&issueSummary=yyy&....
which results in the the branch name being xxx-yyy.
The generated command (to run locally) seems to be correct :)

@rachellerathbone is there any plans to resolve this issue? Thanks

Hi all, this feature has been rolled out a few months ago. I'm closing this issue but please feel free to raise a new one if you encounter any issues when creating a branch.
Cheers :)


Can't use the icon set on a remote server session

Hi.
I connect VS Code to a Linux server using the Remote-SSH extension. On the remote servers the Symbols plugin is disabled:

On the remote servers VS Code is using the Seti icon set, in local it uses the Symbols set correctly. I installed the Material Icons Theme as well, and it doesn't need to be installed on the remote server, just like the default Seti and Minimal sets.
I'm using a Mac with M1 processor and macOS 12.5.1 and VS Code 1.70.2.
Thanks, regards.

Hmm...I'm not sure why that doesn't work. Let me investigate...

@mmontagnana what happens when you click "install in SSH"? I tried this in a Codespace, which is also a remote env, and got a similar message but clicking install will install it.

If I install it in remote it works.
The issue is that, for example, the Material File Icon theme and the Fluent product icon theme are working from the local install, with no need to install them in SSH.

Yes, that's because each extension is created differently. The symbol icon extension runs javascript to dynamically create the non-chevron tree items, so that's why it needs to be installed.

Ok, if it's by design I'll install it on the other VMs I'm using.
Thank you, regards
Marco

Closing in favor of https://github.com/miguelsolorio/vscode-symbols/issues/46


Tilda chrome extension saves as html

Generating java doc by embedding html generated from chrome app.
@ldhasson Please review

@ldhasson  Added ability to save link's vertices


v1 or v2 storage type support

documentation needs to be updated to reflect appropriate option for storage account type (ie v1 vs v2)

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

ID: 8621ec19-98d2-d173-09f6-f8e26f769dd4
Version Independent ID: e85e619c-4ec7-34cb-9620-2b725712d858
Content: Create resources for use with Azure Site Recovery | Microsoft Docs
Content Source: articles/site-recovery/tutorial-prepare-azure.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@cloudinnovating
Thanks for the feedback! We are currently investigating and will update you shortly.

v1 supported, v2 not.  Found answer here - [(https://docs.microsoft.com/en-us/azure/site-recovery/vmware-physical-azure-support-matrix#replicated-machines)]

Looks like no action required

We should close this. No action required
#close

@cloudinnovating
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

I have got an error with the latest


Remove mount_type from models

Remove mount_type from models:

TrafficSignPlan
TrafficSignReal
TrafficLightPlan
TrafficLightReal
SignpostPlan
SignpostReal

Add migration and update tests.
Refs LIIK-142

Specification has changed, this PR is not valid anymore.


"Error: Failed to convert to UTF-8: invalid code unit" when building vcpkg-cmake

Operating system
Windows 11
Compiler
No response
Steps to reproduce the behavior
PS C:\src\vcpkg> .\vcpkg install colmap[cuda,tests]:x64-windows
Computing installation plan...
The following packages will be built and installed:
  * blas:x64-windows@2023-04-14
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>    colmap[core,cuda,tests]:x64-windows@2023-10-01
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * egl-registry:x64-windows@2024-01-25
  *<EMAIL_ADDRESS>  * flann:x64-windows@2019-04-07#7
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * gklib:x64-windows@2023-03-27
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * lapack:x64-windows@2023-06-10
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * metis:x64-windows@2022-07-27
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * opengl:x64-windows@2022-12-04#3
  * opengl-registry:x64-windows@2024-02-10#1
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  * vcpkg-boost:x64-windows@2024-04-25
  * vcpkg-cmake:x64-windows@2023-05-04
  * vcpkg-cmake-config:x64-windows@2022-02-06#1
  * vcpkg-cmake-get-vars:x64-windows@2023-12-31
  * vcpkg-gfortran:x64-windows@3#3
  * vcpkg-pkgconfig-get-modules:x64-windows@2023-09-06
  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>  *<EMAIL_ADDRESS>Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
-- Automatically setting %HTTP(S)_PROXY% environment variables to "<IP_ADDRESS>:7890".
Compiler found: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe
Restored 0 package(s) from C:\Users\feima\AppData\Local\vcpkg\archives in 1.23 ms. Use --debug to see more details.
Installing 1/152<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
error: Failed to convert to UTF-8: invalid code unit
PS C:\src\vcpkg> chcp
Active code page: 65001
PS C:\src\vcpkg>

Failure logs
In the vcpkg/buildtrees/vcpkg-cmake/stdout-x64-windows.log,only have:
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
Additional context
vcpkg is the newest
PowerShell Version:7.2.16
System Region:China(Simple),I checked "Beta: Use Unicode UTF-8 for global language support"

Try checking: https://github.com/microsoft/vcpkg/issues/37420#issuecomment-1996253121

Try checking: #37420 (comment)

I tried,this method doesn't work.
The same error:
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
-- Automatically setting %HTTP(S)_PROXY% environment variables to "<IP_ADDRESS>:7890".
Compiler found: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe
Restored 0 package(s) from C:\Users\feima\AppData\Local\vcpkg\archives in 1.39 ms. Use --debug to see more details.
Installing 1/152<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/src/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
error: Failed to convert to UTF-8: found continue code unit in start position

I saw this error message today, too. Using Process Monitor, I discovered that I had a vcpkg.json file encoded in UTF-16 in a directory above my clone of the vcpkg repo. I'm surprised that vcpkg continues looking for vcpkg.json files above the .vcpkg-root folder.
In any case, removing the errant vcpkg.json file solved the issue.
The error message should really print which file it was reading at the time.

I saw this error message today, too. Using Process Monitor, I discovered that I had a vcpkg.json file encoded in UTF-16 in a directory above my clone of the vcpkg repo. I'm surprised that vcpkg continues looking for vcpkg.json files above the .vcpkg-root folder.
In any case, removing the errant vcpkg.json file solved the issue.
The error message should really print which file it was reading at the time.

I haven't paid attention to this for a long time, but I found this to be a good tool.Great!

@MonicaLiu0311 -- here are steps to reproduce the issue on macOS:
mkdir repro
cd repro
git clone https://github.com/microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh -disableMetrics
export VCPKG_ROOT=$PWD
iconv -f utf-8 -t utf-16 < ports/abseil/vcpkg.json > ../vcpkg.json
./vcpkg install abseil

At this point, you will get the error: Failed to convert to UTF-8: invalid code unit message.

In PowerShell, you may use the following command instead of iconv:
Get-Content ports\abseil\vcpkg.json | Out-File ..\vcpkg.json -Encoding Unicode

Here, Unicode refers to UTF16 (no BOM).


Teams cloud recording says incorrect details it is Teams Async Media Services not Azure Media Services

On this page: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/cloud-recording.md
It says in the middle of the page:

Users won't need a Microsoft Stream license assigned if you want users to only record and download the recordings. This will mean that the recordings aren't stored in Microsoft Stream but are instead stored in Azure Media Services (AMS) with a 21-day limit before it's deleted. It's not something at this point that an admin can control or manage including the ability to delete it.

It is not stored on Azured Media Services but Teams Async Media Services.  Can we please correct this?  Thank you!

@descapa Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@nam please can you ask for checking and merge as PR was done 14 Jan. Thanks so much.

Closing via #6493
Thank you


41 random jwt signature verification failed error

Add  Depends(get_current_user) to each protected route. When session expired, decode_token still works but userinfo will complain about expired signature (suspect related to user session expiration). To unify their behavior, check userinfo
Change frontend action to logout user properly when refresh failed.
Note don't set the session idle time to a small value. The minimum of those four will decide the life span of refresh token. If set too small this will cause refresh token expiration too soon and can never refresh; and other weird behaviours

Ready to be reviewed again


Add fade-in fade-out support

The following example can be used to adapt current project:
https://github.com/rokudev/samples/blob/master/screen savers/fading-screensaver.zip

Closed by ccf7209

Closed by ccf7209


TDR-2523 - Show password hints on the reset password page

Once its deployed onto intg, could you do a manual test just double check it look

Yeah, sure.


Update to Swift 2.3

Can you make a new branch for the swift version 2.3?
Thank you!

Hello, thanks a lot for your PR! 🙏
I've merged #118 which adds Swift 4 support.


libdasd: add common dasd ioctls to the lib

This avoids code duplication on dasd-related programs.
Signed-off-by: Rafael Fonseca<EMAIL_ADDRESS>

@hoeppnerj that's for you.

Sure, I can divide the patch into several smaller commits. I'll do that for the next version.

@hoeppnerj Hopefully I addressed all your raised points. I also added 2 more commits fixing the coding style in dasdinfo and dasdview.
Let me know if there is anything else.

@r4f4 I just found a major issue that I didn't pay attention to or rather didn't remember while reviewing.
Dasdfmt currently doesn't work since we're closing the file descriptor after each IOCTL call. Before BIODASDFMT can be called, a DASD has to be disabled (or rather put into a BASIC state) via BIODASDDISABLE. However, if you disable the DASD, close the file descriptor, and then try to reopen it, it won't work as the device isn't fully usable anymore. For BIODASDFMT to work, the file descriptor opened for BIODASDISABLE has to be kept open until BIODASDFMT has finished.
One approach now would be, as BIODASD{DISABLE,ENABLE} and BIODASDFMT only make sense together, to put the calls for BIODASDDISABLE and *ENABLE into the dasd_format_disk() function and not expose dasd_disk_{enable,disable} at all. However, then it gets a bit fiddly to figure out the state of the disk in case the program gets interrupted and we want to re-enable the disk.
Therefore, my suggestion now would be to have dasd_disk_disable() return the file descriptor and change dasd_format_disk() to take an fd as an additional parameter (You already had this approach in the first iteration were you could pass a file description to some functions). I think thats less effort for now and the other approach could be worked on at a later time.
Sorry for the inconveniences, I just noticed it while doing some basic function tests with your patches. (Should've tested it earlier really).

@hoeppnerj thank you for testing. I tested some of the tools, but I couldn't get hold of a s390x machine where I could run the formatting commands. I'll fix that and update the patches.

but I couldn't get hold of a s390x machine where I could run the formatting commands.

@r4f4 Red Hat has a Mainframe with attached DASDs for testing. IMHO it is important that you organize a test setup when you write DASD related s390-tools code.

dasdfmt is working now but I really dislike the way dasd_(dis|en)able and dasd_format_disk don't conform to the same structure as the other functions.
What if we made dasd_ioctl.c context-based? dasd_ioctl_init() could initialize a ctx struct containing some info (like file descriptor and disk state) and all operations would use that context on an open device. We would only close the device upon dasd_ioctl_deinit();

dasdfmt is working now but I really dislike the way dasd_(dis|en)able and dasd_format_disk don't conform to the same structure as the other functions.
What if we made dasd_ioctl.c context-based? dasd_ioctl_init() could initialize a ctx struct containing some info (like file descriptor and disk state) and all operations would use that context on an open device. We would only close the device upon dasd_ioctl_deinit();

I'm not entirely happy with it as well, but I think the solution is fine for now. A better way to handle this issue can be worked on at a later point. I'm not sure about the context-based either. I appreciate the suggestion though and will take it with me to our internal discussion.
A few more review comments following in a bit.

Alright, looks fine now. I merged and pushed it to our devel branch.
It'll be put upstream with the next sync.
Thanks @r4f4 for the effort!

@hoeppnerj Any idea when the next sync is going to happen? I'd like to rebase my zipl_helper branch onto  master with the libdasd changes so that I can submit a new patch version.

I will do the sync within this week as soon as possible.


canot println!("{}", String::from_utf8_lossy(&*next_token.detokenize()));

when run the example, as the next_token is Token which has not detokenize method? or may I miss something?
I checked the doc from https://docs.rs/llama_cpp/latest/llama_cpp/struct.Token.html

The documentation was a bit out of date, I'm updating with a correct example.


feat: add onRequest hook to createAPIClient

Description
Allow for usage of the onRequest interceptor that's provided by ofetch. Added onRequest to the ApiClientHooks and applied it in a similar way that was done for other hooks.
Added four testcases to make sure it works in the way you'd expect when using this hook.
Added a bit of info to the readme to make sure people know they can use it.
Type of change
New feature (non-breaking change which adds functionality)
ToDo's
None

[x] Changeset file provided read more
[x] Documentation added/updated
[x] Unit-Tests added/updated

I wouldn't encourage people to add custom headers via the hook, rather use global headers or headers option in request. I see the usecase for analytics purpose as an example. When would you feel you need to modify headers with this hook?


Editing file using code  -w in terminal does not return focus to terminal when closed

VS Code Version: 1.55.0
OS Version: macOS 11.2.3

Steps to Reproduce:

Open terminal
Run command code -w file
file will open in the editor
make some changes or add text to file
Close file, such as with CMD-W
Focus remains in the editor, and does not return to the terminal

Does this issue occur when all extensions are disabled?: No. This problem doesn't seem to occur when have my extensions disabled.

I used the extension bisect but it failed on the first attempt. It said it disabled 62 extensions, I tried reproducing the problem, and it succeeded, so I clicked "This is bad" and the bisect ended immediately saying it might be a problem with VS Code. The unique thing is that my project was running inside a remote container.

Based on your testing, it seems an extension is to blame for this


Make fails when GOPATH contains more than one entry

If GOPATH contains more than a single entry, the dep section in Makefile fails:
https://github.com/operator-framework/operator-lifecycle-manager/blob/7f78dc9900df26d0c1fbfa195f4ef61b91ac7b6b/Makefile#L75-L77

@bostrt - OLM now uses go modules for dependency resolution, so all make rules referencing dep have been removed in newer releases.
Our Makefile is generally for development purposes, so it won't impact the release itself. Could you explain your use-case for using the Makefile with an older release? Is it possible for you to use a more recent release (with the failing rules removed)?

@njhale

OLM now uses go modules for dependency resolution, so all make rules referencing dep have been removed in newer releases.
Our Makefile is generally for development purposes, so it won't impact the release itself. Could you explain your use-case for using the Makefile with an older release? Is it possible for you to use a more recent release (with the failing rules removed)?

Ah, good to know! Yes, I'm building a version based on 0.6.0 released by Red Hat for troubleshooting a startup hang issue. Just came across this Makefile issue while building a debug image.

/close


updating README.md

Changes:

Modified the Install into a Quick Start
Added a long set of instructions on how to go from the binary to files everywhere and freedit running as a service.
Added a quick section about administration

WIP for now as there is some contentious stuff:

For the snapshots
For for static folders
Maybe one can use environment variables as configuration too (I'm not versed in Rust so I'm not sure if it is an option)

There seems to be typo. And I prefer to place everything in /opt directory to make it easier to manage.


Partition column comparison is an assertion rather than if block with raise exception

Environment
Delta-rs version:
0.16.0
Binding:
python
Environment:
MacOS

Bug
What happened:
An assertion is done between partition columns from incoming data and target table. If this fails an AssertionError is raised.
https://github.com/delta-io/delta-rs/blob/15538b9b42ba3d0d20ffd287bb4cc463ff8dfb1d/python/deltalake/writer.py#L340
What you expected to happen:
This should be an if block, and raise an exception if the two values aren't the same. ValueError would be fine.
How to reproduce it:
Try to write a table with the wrong partition columns specified in the incoming data.
More details:
This exception should also be changed, maybe something like FileExistsError
https://github.com/delta-io/delta-rs/blob/15538b9b42ba3d0d20ffd287bb4cc463ff8dfb1d/python/deltalake/writer.py#L333
Edit:
assert statements are ignored when running in optimise mode, so this could cause issues for a user running in optimised mode

@joe-sharman do you want to make a contribution to address this?

I'll put something together :)

Hey @ion-elgreco I've had a go making the change. I've tried to follow the commit conventions in the repo and have used built-in exceptions rather than custom as that seems to be the convention here.


Checks for ArrayStoreExceptions and NegativeArraySizeExceptions.

Alternative to #4711. We rename Semantics.arrayIndexOutOfBounds to arrayErrors, then implement checks for ArrayStoreExceptions and NegativeArraySizeExceptions under that unique semantics config.

Rebased.

Rebased to address conflicts in the checksizes.

Superseded by #4711.


Export edge data and event functions.

Export edge data and event functions for custom connections.
Self evaluation:

Build test: [* ]Passed [ ]Failed [ ]Skipped
Run test: [* ]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #217. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Questions about the usage of this project

Hi, I'm a new comer to the optical flow field, and I am attracted by this excellent project. As for as I know, the grid_sample function in pytorch solves the problem about backward flow warping. For example, if I have frame1 and frame2, I can use the flow1->2 to warp the information from frame2 to frame1. What about your codes? Does flow forward warping mean I can adopt the flow1->2 to warp the information from frame1 to frame2? I'm looking forward to your reply, thank you.

First of all, if you use grid sample (backward warp) you sample the output from the input, specifically I know the input image and where each point of the output will be mapped to in the input, so you can sample the output from the input. But this sampled position is a float point number, and quantization to pixels is not precise. The forward warp is the opposite, it also knows the input image, but it also knows where each point in the input will be mapped to in the output, and samples the output from the mapped image (of course, the mapped points are also float point numbers, and quantization will be imprecise, so we generally use forward and backward together). Simply put, backward is to first sample and then map, forward is to first map and then sample.
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Kaidong Zhang @.>
发送时间: Monday, June 28, 2021 7:06:33 PM
收件人: lizhihao6/Forward-Warp @.>
抄送: Subscribed @.***>
主题: [lizhihao6/Forward-Warp] Questions about the usage of this project (#9)
Hi, I'm a new comer to the optical flow field, and I am attracted by this excellent project. As for as I know, the grid_sample function in pytorch solves the problem about backward flow warping. For example, if I have frame1 and frame2, I can use the flow1->2 to warp the information from frame2 to frame1. What about your codes? Does flow forward warping mean I can adopt the flow1->2 to warp the information from frame1 to frame2? I'm looking forward to your reply, thank you.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/lizhihao6/Forward-Warp/issues/9, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJEKREGGYBTVARGFC3YHLLTVBJTTANCNFSM47NXPRCA.

@lizhihao6 Thanks for your answer! So, your codes solve the latter condition, which uses the flow1->2 to warp frame1 to frame2?

Yeap
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Kaidong Zhang @.>
发送时间: Monday, June 28, 2021 9:59:16 PM
收件人: lizhihao6/Forward-Warp @.>
抄送: lizhihao6 @.>; Mention @.>
主题: Re: [lizhihao6/Forward-Warp] Questions about the usage of this project (#9)
@lizhihao6https://github.com/lizhihao6 Thanks for your answer! So, your codes solve the latter condition, which uses the flow1->2 to warp frame1 to frame2?
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lizhihao6/Forward-Warp/issues/9#issuecomment-869709113, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJEKRCKHFZFFRAV3PPHI7TTVB53JANCNFSM47NXPRCA.

Thanks for your help, god bless you!


cleanup(init/meta/tactic) removing obsolete meta constants

These meta constants are not defined in the VM, and should be removed.

merged


Enhance CS Form

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3395  👈
#3392 : 1 other dependent PR (#3393 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


Support overriding the a single browser's support in dist build

In https://github.com/web-platform-dx/web-features/pull/797 I wanted to override the Chrome Android data, but found that this minimal override wouldn't work:
status:
  baseline: false
  support:
    chrome_android: "121"

The generated YAML then had only Chrome Android, not the Chrome+Edge data that could be correctly generated.
There's a catch if we try to support this however. How would we erase a key that shouldn't be there? I would suggest setting support to false to achieve this.

Now that I've thought this through a bit (see below), I have one big question:
How does overriding a single browser affect the calculation of baseline and baseline_low_date, if at all? For instance, does setting a version imply setting the version for the purposes of determining the baseline_low_date? Or is it like giving a directive to edit the YAML in a certain way?

Thinking through alternatives here, just to get my head around how it'd work.
Explicitly generate
A special "accept calculated" value
status:
  baseline: accept
  support:
    chrome: accept
    chrome_android: "121"
    edge: accept
    # etc. …

Semi-explicit pass-through
Undefined values get generated
status:
  baseline:
  support:
    chrome:
    chrome_android: "121"
    edge:
    # etc. …

Some sort of special override notation
editorial:
  - status.baseline: false
  - status.support.chrome_android: 121

How does overriding a single browser affect the calculation of baseline and baseline_low_date, if at all?

I think it needs to affect the Baseline low date by taking the date from the override as one of the candidate dates for the keystone date.
This is indeed different from overriding a single field of the output.
In a similar way, overriding the Baseline status to false also needs to clear the Baseline low and high dates if they were computed.

OK, in that case, I guess the next step is to figure out how we want to change compute-baseline to support this. Some off the cuff ideas:

Some option to computeBaseline() (e.g., something like computeBaseline( { compatKeys: […], overrides: ["chrome", "123"] }))
Some method on the return value of computeBaseline() (e.g., computeBaseline(…).override(browser, version))
Some function that does something similar (e.g. override(computeBaseline(…), browser, version))

Something else?

I think something like the first option sounds good. It is a set of overrides used somewhere in computeBaseline, but the caller shouldn't need to worry about where in the calculation it happens or remember which things it will affect in turn. Just override the information you know is wrong, and everything else will be adjusted.


Fixed #7 compatibility with #6

I fixed the compatibility of my changes (#7) with ahmedflix25 changes (#6).

Fixed in #12