Dashboard shows test as in process when it has already passed

Type of Request
bug
Infrastructure Environment
Flutter build dashboard (packages)
What is happening?
After a few retries, a test has now passed, but is still yellow on the board. This is actively blocking the tree.
Steps to reproduce
Step 1: Repeatedly fail and retry test
Expected results
Test should show as passing, but shows as in process.

This is a dup of https://github.com/flutter/flutter/issues/147007.
Please try avoiding the GitHub UI Re-run, which is missing some logics to handle retry logics. Please use the internal API  instead to kick a manual post-submit retry.
I manually reset the tree status, and it is open now.

I think there may be another bug with the dashboard, when I click on any test on the current build, it opens a new page that doesn't have the rerun option on it. Clicking on any older tests opens the normal menu with the re-run button.

Yes, that's https://github.com/flutter/flutter/issues/145849


ESP01 Serial Error Output

We are having problems connecting with the ESP01 through the Serial port on the Arduino IDE. I have been debugging this issue for almost 4 days and I am a bit stuck. Let me describe the issue in case there is something we are not seeing.
1- ESP01 is plugged to the computer through the USB adapter and is properly oriented in the direction of the arrow (see image attach). The USB adapter is set to "PROG".
2- The libraries for the ESP01 (ESP8266) have been installed to the Arduino IDE. The IDE recognizes the Port and allows to select the Arduino setting in board type (Tools -> Board -> esp8266 -> Arduino).
3- A blinking program compiles, gets uploaded and works.
4- When we start a serial connection, garbage is received on the other end (see image attached).
I have tried this experiment with multiple configurations:

(Arduino IDE 1 & Arduino IDE 2)

(Change USB A port)

(Change PROG and UART accordingly)

(Try at multiple baud rates in sketch and reciving, 9600, 19200, 115200, 921600)

(Try the second esp01 that we have)

I can confirm that the output of the ESP01 "corresponds" to real output of the program. For instance if a print "."
I have read the manuals uploaded on the campus and I don't see anything that can help solve this issue.
I have also read the official library/board documentation: https://arduino-esp8266.readthedocs.io/en/latest/index.html
I have searched the web for multiple solutions (e.g https://github.com/esp8266/Arduino/issues/4005) and I can't find any valid solution.
I speculate that it may be related with the USB connection, but I cannot confirm the issue and I don't know how to make it work.

Solution: Turns out the solution was to select the board as "Generic 8266"


[ Kernel ] AWQ Fused MoE

SUMMARY:

Picks up #6259 2761 to support AWQ MoE models via a fused kernel, after the refactor I did in #5970. The kernels for this PR were developed by @chu-tianxiang
Adds AWQMoEmethod, supporting loading AutoAWQ models
Refactors FusedMoE.weight_loader, to enable loading AWQ models, which have transposed weights (input_dim, output_dim) on disk. Fp16 and Fp8 models have share (input_dim, output_dim). This required more complex logic for handling indexing in the TP case and MergedColumn case
Refactors expert_params_mapping, which was overfit to fp16 and fp8 checkpoints. This required renaming the scale parameters in fp8 which to better match the state dicts that we create in autofp8, limiting the amount of remapping we need to do in the model files
Updates layers to use fused_topk/grouped_topk and fused_experts, rather than calling fused_moe directly, such that we can reuse the logic across fp16, fp8, and awq

TODO:

investigate why DQ is not giving contiguous tensors
add back the kernel tests
benchmarking
illegal memory access with TechxGenus/DeepSeek-V2-Lite-Chat-AWQ

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

PR 1/2: https://github.com/vllm-project/vllm/pull/7334


PWM driver: pca9685_pwm_out improvement

Describe problem solved by this pull request
Fixed some bugs about that driver. Listed here:

Switched CDev name so that "/dev/pca9685" is pointed to I2C driver and "/dev/pwm_outputX" is pointed to the function wrapper
Parameters doesn't take effect when change back to default -1.

Added new features:

Now supports esc calibration executed from QGC(not being tested, for that my new ADC driver is not merged into upstream).But it works only if the driver is the only one that registered "/dev/pwm_outputX" due to commander logic.

Some critical changes:
-New parameters are defined. this will make PCA9685 able to run together with other PWM output devices.
Note this driver allows parameters to be changed run-time without reboot, which will lead to some performance issue. But it is not critical on embed Linux.
Test data / coverage
This driver still works properly on my RPi.
Additional context
This driver has a "wrapper" layer which is abstracted from the real driver. Those code can be easily picked up and quickly be deployed with other pwm drivers, such as Navio2, BBB and OCPOC. I mean, we are able to purge linux_pwm_out by setting up board specific pwm drivers in their board folder. This driver can be the template.

Ready.

BTW, I have figured out how we can purge src/drivers/pca9685 safely. That implement can be fully replaced with this driver. I'd like to start another PR for that once this gets merged.

Generally looks good, but I'm hesitating on the parameter change. Doesn't it make the simple case (only output is pca9685) more complicated from a user perspective?
I was considering extending the mixer module lib for the PWM case.
In terms of the pca9685 as an additional output (or having multiple) aren't we just missing visibility into the mapping (MAIN, AUX, etc)?

Generally looks good, but I'm hesitating on the parameter change. Doesn't it make the simple case (only output is pca9685) more complicated from a user perspective?
I was considering extending the mixer module lib for the PWM case.
In terms of the pca9685 as an additional output (or having multiple) aren't we just missing visibility into the mapping (MAIN, AUX, etc)?

It will. But currently no board depends on it as the only output. Those parameters are already defined here. I just implemented them.
PWM channel mapping is done though mixer files, as it always be. Simply bind the mixer to this driver with mixer command should work.

@SalimTerryLi Couldn't we just use the PWM_MAIN parameters for this? All the user documentation explains how to use them and the ground station software knows how to set them. That is a lot better for an end user than having a new set of parameters.
Why did you introduce new ones and what problem are you trying to solve?

@SalimTerryLi Couldn't we just use the PWM_MAIN parameters for this? All the user documentation explains how to use them and the ground station software knows how to set them. That is a lot better for an end user than having a new set of parameters.
Why did you introduce new ones and what problem are you trying to solve?

This driver may have two use case:

as the only output device for some new boards( actually I'm in this way
as an extra pwm output device, to extends the boards which has limited pwm channels( most people is in this way.

It is OK to reuse old parameters if I try to use it on my own board. but definitely can not if someone want to extend PWM channels because of conflicts. There is already a person who want to use PCA9685 on Pixhawk Cube to extend max PWM channels to control a complex VTOL.

Because these new parameters make it very hard to set up the system through a GCS and they are not documented, I'm not convinced this is an improvement. I would retain the PWM_MAIN parameter mapping instead.

I'm willing to update those document, although there may be not too much people will use this driver.

You can't update the GCS source code and it doesn't make sense for us to carry documentation that a low number of users are actually using.
Back to the question you haven't answered: Why can't you just use the existing PWM_MAIN parameters and read those? Why do you need your own?

You can't update the GCS source code and it doesn't make sense for us to carry documentation that a low number of users are actually using.
Back to the question you haven't answered: Why can't you just use the existing PWM_MAIN parameters and read those? Why do you need your own?

That will lead to conflicts if I want to use this driver on standard Pixhawk which has its own outputting driver.

Are you using the driver on a Pixhawk? Because the better solution would be to go straight to UAVCAN (albeit not instant).

Are you using the driver on a Pixhawk? Because the better solution would be to go straight to UAVCAN (albeit not instant).

I'm speaking for at least two people now.
For myself, it is ok to just read old parameters. as I use PCA9685 as the primary PWM out.
There is also someone on slack who want to use it with Pixhawk Cude to extend maximum available PWM channels. For him, new parameters are necessary.
Moreover, a badly designed pca9685 driver already exists in PX4, named src/drivers/pca9685. I want to make this new driver a better replacement of that driver. Also this driver has a developed wrapper which can be ported to other similar devices, such as linux_pwm_out. @ dagar expects to purge it, as this PR maybe a part of that action.

Switch back to original parameter names. Please review it.


fix: disable multiplexing on macOS for some versions of curl

What does this PR try to resolve?
Fixes #12202.
Zulip topic.
In certain versions of libcurl when proxy is in use with HTTP/2
multiplexing, connections will continue stacking up. This was
fixed in libcurl 8.0.0 in curl/curl@821f6e2a89de8aec1c7da3c0f381b92b2b801efc
However, a custom built Cargo can still link against old system libcurl.
Multiplexing needs to be disabled when those versions are detected.
We only take care of macOS now, since it is one of the major platforms.
For other OS we encourage not to stick to older versions of licurl.
How should we test and review this PR?
 Please call it out if you
feel uncomfortable to this.
The second one did the trick only for macOS, and a unit test is added.
Manual test the behavior
To manually test the behavior, you need to build cargo with
the all-static feature, which despite its name links libcurl
dynamically on macOS. It is a feature used by rustup distributions.
cargo b -F all-static

I don't really understand curl internals so had no luck to figure
out the relationship between proxies and HTTP/2 multiplexing.
I use hinata/nginx-forward-proxy to spin up a proxy to test curl's behavior.
It turns out that if there are fewer dependencies to download,
or we set MAX_CONCURRENT_STREAMS to a lower value in curl,
it largely affects the happening of the error no filter connected.
That implies multiplexing and http proxy are really influencing
each other in some way.
My patch to curl and curl-sys

diff --git a/Cargo.toml b/Cargo.toml
index ec9f878b3..3a687c309 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -205,3 +205,7 @@ vendored-libgit2 = ["libgit2-sys/vendored"]
 pretty-env-logger = ["pretty_env_logger"]
 # This is primarily used by rust-lang/rust distributing cargo the executable.
 all-static = ['vendored-openssl', 'curl/static-curl', 'curl/force-system-lib-on-osx']
+
+[patch.crates-io]
+curl = { git = "https://github.com/weihanglo/curl-rust", branch = "curlmopt" }
+curl-sys = { git = "https://github.com/weihanglo/curl-rust", branch = "curlmopt" }
diff --git a/src/cargo/sources/registry/http_remote.rs b/src/cargo/sources/registry/http_remote.rs
index 7e1f2a587..21ae3ca10 100644
--- a/src/cargo/sources/registry/http_remote.rs
+++ b/src/cargo/sources/registry/http_remote.rs
@@ -246,6 +246,8 @@ impl<'cfg> HttpRegistry<'cfg> {
                 .status("Updating", self.source_id.display_index())?;
         }

+        self.multi.set_max_concurrent_streams(10)?;
+
         Ok(())
     }

BTW. Although this is not really a regression, with sparse registry the number of connections is easier to exceed MAX_CONCURRENT_STREAMS (default to 100 in libcurl). Should we backport it at least for https://github.com/rust-lang/cargo/labels/beta-nominated?

If you want to backport this to beta, that sounds good to me!
I think at some point it would be good to set up a proxy test using the container tests.

Thanks for the review!
@bors r=ehuss

I think at some point it would be good to set up a proxy test using the container tests.

Was thinking the same thing, though it feels a bit too hard to write one. I'll try when I have time. Thanks for the suggestion!

:pushpin: Commit 6af8cb24689190cd899c81a617770abb4f17bc6a has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 6af8cb24689190cd899c81a617770abb4f17bc6a with merge 41d662bc7ef05fa3496fb032e0c98ef4a9a66aa5...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 41d662bc7ef05fa3496fb032e0c98ef4a9a66aa5 to master...


Zooz ZEN27 (zwave) - can't set ramp rate or min/max brightness

Home Assistant release with the issue:

0.86.3
Last working Home Assistant release (if known):
None that I'm aware of
Operating environment (Hass.io/Docker/Windows/etc.):

Docker with the Aeotec Z-Stick Gen5 passed through to it. I'm pulling down a copy of the latest zwave xml configs from the openzwave project.
Component/platform:

light.zwave
Description of problem:
I'm trying to set the ramp rate parameter (to 10 seconds, but I tried a variety of values) on my ZEN27 dimmer and it just flips back to the previous setting.
Edit: min/max brightness doesn't appear to work either.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
just using the auto discovery

Traceback (if applicable):
2019-01-29 04:26:48.298 Info, Node022, Value::Set - COMMAND_CLASS_CONFIGURATION - Ramp Rate Control - 9 - 1 - 10
2019-01-29 04:26:48.299 Info, Node022, Configuration::Set - Parameter=9, Value=10 Size=2
2019-01-29 04:26:48.299 Detail, Node022, Queuing (Send) ConfigurationCmd_Set (Node=22): 0x01, 0x0d, 0x00, 0x13, 0x16, 0x06, 0x70, 0x04, 0x09, 0x02, 0x00, 0x0a, 0x25, 0x70, 0xd1
2019-01-29 04:26:48.299 Detail, Node022, Queuing (Send) ConfigurationCmd_Get (Node=22): 0x01, 0x0a, 0x00, 0x13, 0x16, 0x03, 0x70, 0x05, 0x09, 0x25, 0x71, 0xdb
2019-01-29 04:26:48.299 Detail,
2019-01-29 04:26:48.299 Info, Node022, Sending (Send) message (Callback ID=0x70, Expected Reply=0x13) - ConfigurationCmd_Set (Node=22): 0x01, 0x0d, 0x00, 0x13, 0x16, 0x06, 0x70, 0x04, 0x09, 0x02, 0x00, 0x0a, 0x25, 0x70, 0xd1
2019-01-29 04:26:48.306 Detail, Node022,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-29 04:26:48.306 Detail, Node022,   ZW_SEND_DATA delivered to Z-Wave stack
2019-01-29 04:26:48.349 Detail, Node022,   Received: 0x01, 0x07, 0x00, 0x13, 0x70, 0x00, 0x00, 0x05, 0x9e
2019-01-29 04:26:48.349 Detail, Node022,   ZW_SEND_DATA Request with callback ID 0x70 received (expected 0x70)
2019-01-29 04:26:48.349 Info, Node022, Request RTT 50 Average Request RTT 67
2019-01-29 04:26:48.349 Detail,   Expected callbackId was received
2019-01-29 04:26:48.349 Detail,   Expected reply was received
2019-01-29 04:26:48.349 Detail,   Message transaction complete
2019-01-29 04:26:48.349 Detail,
2019-01-29 04:26:48.349 Detail, Node022, Removing current message
2019-01-29 04:26:48.349 Detail,
2019-01-29 04:26:48.349 Info, Node022, Sending (Send) message (Callback ID=0x71, Expected Reply=0x04) - ConfigurationCmd_Get (Node=22): 0x01, 0x0a, 0x00, 0x13, 0x16, 0x03, 0x70, 0x05, 0x09, 0x25, 0x71, 0xdb
2019-01-29 04:26:48.357 Detail, Node022,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-01-29 04:26:48.357 Detail, Node022,   ZW_SEND_DATA delivered to Z-Wave stack
2019-01-29 04:26:48.422 Detail, Node022,   Received: 0x01, 0x07, 0x00, 0x13, 0x71, 0x00, 0x00, 0x07, 0x9d
2019-01-29 04:26:48.422 Detail, Node022,   ZW_SEND_DATA Request with callback ID 0x71 received (expected 0x71)
2019-01-29 04:26:48.422 Info, Node022, Request RTT 72 Average Request RTT 69
2019-01-29 04:26:48.422 Detail,   Expected callbackId was received
2019-01-29 04:26:48.494 Detail, Node022,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x16, 0x05, 0x70, 0x06, 0x09, 0x01, 0x01, 0x9c
2019-01-29 04:26:48.494 Detail,
2019-01-29 04:26:48.494 Info, Node022, Response RTT 144 Average Response RTT 224
2019-01-29 04:26:48.494 Detail, Node022, Initial read of value
2019-01-29 04:26:48.494 Info, Node022, Received Configuration report: Parameter=9, Value=1
2019-01-29 04:26:48.494 Detail, Node022,   Expected reply and command class was received
2019-01-29 04:26:48.494 Detail, Node022,   Message transaction complete
2019-01-29 04:26:48.494 Detail,
2019-01-29 04:26:48.494 Detail, Node022, Removing current message
2019-01-29 04:26:48.494 Detail, Node022, Notification: ValueChanged

Additional information:
I am able to set other parameters like the LED indication control with no problem.

Odd, the log indicates the device accepted the request for the parameter change.  But then queried right afterwards, it has not been updated.
Sounds odd, but have you tried manually toggling the device just shortly after setting the parameter?  I have personally had issues with certain devices accepting the parameter change request, but not applying the parameter (Zooz motion sensors) unless I trigger or toggle the device after the set request has been made.

It's possible the OZW XML might be incorrect for that setting, due to the parameter size value. It has already been corrected before:
https://github.com/OpenZWave/open-zwave/commits/c10d8a5a7f72c8f4215315d2b5c7964406f0e8b6/config/zooz/zen27.xml
If the size is wrong, the device might be rejecting the setting. The Zooz documentation says that parameter 9 is is 1-byte. The XML config for this device is setting it to a 2-byte value (size=2). What happens if you change that?
To test you can hand edit your zwcfg*.xml file. Make sure you stop HA first and make a backup. You should see something like:
<Value type="short" genre="config" index="9" label="Ramp Rate Control" size="2" min="1" max="99" value="99" units="seconds">
    <Help>Time, in seconds, for ramp rate.</Help>
</Value>

You'll want to change it so the type is "byte" and the size is "1". The manual also says the default is 1, so I'd modify value (which is the default) to say "1".
<Value type="byte" genre="config" index="9" label="Ramp Rate Control" size="2" min="1" max="99" value="1" units="seconds">
    <Help>Time, in seconds, for ramp rate.</Help>
</Value>

Some other parameters also don't match the manual. I wonder if there were multiple revisions or if the switch has changed...

good call...changing those does fix the issues with ramp rate and min/max brightness (max needs setting 11 to be set to max level)
doesn't seem like any others take an input, rest are lists.

can this be closed? That PR was merged and presumably open-zwave was updated in Home Assistant.


Scroll position is not remembered correctly for Release Notes

Issue Type: Bug

Scroll down in the Release Notes (in this example to "Increased limit to 1000 lines...")
Switch to another tab
Switch back to the Release Notes tab

Expectation: The scroll position for the Release notes is remembered and restored.
Actual behaviour: The scroll position changes each time the tab is changed (sometimes a bit scrolled up and other times a bit scrolled down)

I am not sure whether this behaviour was present in previous versions.
VS Code version: Code 1.55.0 (c185983a683d14c396952dd432459097bc7f757f, 2021-03-30T16:01:55.261Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz (8 x 3400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.93GB (17.42GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Let me randomly choose one that's still open from the bot's suggestions: #115791

This report is different from all the suggested issues in that the issue is not that the scroll position jumps back to the top and instead jumps around (up and down by a fair bit). I should have made this more clear in the initial report.

pinging @mjbvz who worked with me when I submitted PR #85982 to deal with a similar issue on extension README sub-tabs.

I noticed that the scroll position is calculated differently every time the iframe loads. Wondering if this is happening because there is content that is still being added to the view when this is calculated.
https://github.com/microsoft/vscode/blob/401554bc4512bd686b286b0a91ba990c60832a4b/src/vs/workbench/contrib/webview/browser/pre/main.js#L452

My guess is that the images take different times to load and the height of the images is only taken into consideration once the loading has finished. This could be tested by adding the "height"-parameter to all images so that they take up the same vertical space even if they are not loaded yet.

I am experiencing this bug with VS code 1.65.0

A workaround to this problem is to drag the Release Notes tab to the side and keep it loaded there - while trying new features from the notes. :)

My guess is that the images take different times to load and the height of the images is only taken into consideration once the loading has finished. This could be tested by adding the "height"-parameter to all images so that they take up the same vertical space even if they are not loaded yet.

I think you nailed the reason: when release notes viewed offline, this issue is not reproducible. Or it exponentially scrolls down faster the more images it scrolled by.

My guess is that the images take different times to load and the height of the images is only taken into consideration once the loading has finished. This could be tested by adding the "height"-parameter to all images so that they take up the same vertical space even if they are not loaded yet.

I think you nailed the reason: when release notes viewed offline, this issue is not reproducible. Or it exponentially scrolls down faster the more images it scrolled by.

Furthermore, you can see the issue unfold just as it happens if you use a slow internet connection or limit its speed intentionally.
For example, if the document has five sections (A through E), each with images, and you left the tab when viewport was on section C, you’ll initially see section C on return to the tab, but then images in sections A and B would load, moving viewport up to one of the previous sections.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Trade API

Would like an API endpoint for querying trades from the database. This task can be split into three parts:

API Specification (#308)
Database Preparation (#316)
Exposing the API endpoint (#314)

TODOs after the fact:

[ ] Include transaction hash in the trade table so that we can use this for a new field batchTx in the Trade struct.

Thanks for adding the hash in the TODO
If this comes from the comment https://github.com/gnosis/gp-v2-services/pull/308#discussion_r575327800 , I'd love that we consider to add the executionTime of the trade, and if possible the batchId and the tradeFee
Basically we would like to be able to work in this beauty:

It is my impression that a nice clean batchIdcan be constructed as blockNumber * 10^4 + transactionIndex since there can be at most 595 (= 12.5M / 21K) transactions in a single block at the current block gas limit and this still allows for the gas limit to go as high as 21M. executionTime is the timestamp of the transaction and tradeFee should be computed by you on the fly as the difference of sellAmount - sellAmountBeforeFees (I am only willing to return two of three three values and we have concluded that what should be returned is the same as what is currently returned for the orders). I hope this is alright.

I also see the batchId as something something like blockNumber || something. One thing to note that it is techincally possible to have two settlements in the same transaction. So for batch ID we should probably use blockNumber || settlement_log_index instead of transaction_index.

I like the settlement log index idea, but not the OR. Would still need to add them for uniqueness.

executionTime is the timestamp of the transaction

Yes, exactly. I mentioned because I didn't see it in the return data. But maybe I'm wrong. Basically very relevant if we return trade info to say the execution time.

tradeFee should be computed by you on the fly as the difference of sellAmount - sellAmountBeforeFees

Aha, ok, if sellAmountBeforeFees for trades too perfect.

It is my impression that a nice clean batchIdcan be constructed as blockNumber * 10^4 + transactionIndex

I think that a public API should return the IDs abstracted away from its implementation (it should be opaque as Felix mentioned in the trade schema PRs). Otherwise, you add a dependency that is unnecessary, and also makes a less comprehensive API. If you for some reason have to change the ID generation at a later point.

Is batchID supposed to be the same as what you have as Fill ID there in your image? If so, then it looks like the txHash will suffice.

Batch ID and Fill Id are different. Fill Id would identify a single trade. Batch id would identify a single batch

but not the OR.

Hehe, || in that sense meant concatenate bytes not logical OR operator. I've seen this notation used quite a bit in the context of encoding bytes. For example: https://eips.ethereum.org/EIPS/eip-712#specification

This will be closed as the PR #314 fulfills the minimal criteria of this task. A new issue #334 will take care of the open TODOs.


No Suitable Driver when dynamically loading hive-jdbc jar

I'm trying to use the Hive JDBC drivers to connect to Impala, but getting "No Suitable Driver"
Similar to the SQL Tutorial ... in my SQL notebook cells:

%classpath add jar /tmp/hive-jdbc-2.3.2-standalone.jar
%defaultDatasource impala=jdbc:hive2://<hostname>:21050/default
SELECT 1;
com.twosigma.beakerx.sql.DBConnectionException: Connection URI:impala=jdbc:hive2://<hostname>:21050/default; No suitable driver

When I run %classpath, it lists the hive jar as expected.  I'm using the hive-jdbc shaded standalone jar.  I see the work done in #6222 and #6223 to dynamically load drivers, so looks like this should work.  Any suggestions on what to try next, or other known issues with dynamically loading JDBC drivers?
Environment: BeakerX 0.12.0, Jupyter 4.4.0, Conda Python 3.6.4, CentOS 6.9
Thanks!

Hi Dave thanks for the report.  I'll try it and get back to you.
I don't have a DB to connect to but I should be able to get past the loading error...

Ok your 2nd cell should be:
%defaultDatasource jdbc:hive2://<hostname>:21050/default

then you should be able to connect.  the %datasources magic could take an argument with the impala=.  sorry the documentation isn't clear, i will take this opportunity to improve it.

Awesome thanks Scott - it's registering the Hive driver now.
FYI - %lsmagic shows the incorrect usage parameters - looks like the usage strings are flipped here when calling registerMagicCommandType() on defaultDataSource and datasources.
Is there a suggested way to increase the kernel logging for troubleshooting? (short of jdwp attaching to the kernel).  Sorry for the noob question, I'm still figuring out how all the configs, scripts, and process invocation work from Jupyter->beakerX kernels.

I'm facing the same issue. I have added the jar in classpath using %classpath add jar <path to jar>. also set connection url to default datasource using %defaultDatasource <url> so that by default sql kernel will access hive datastore. But there is no way to specify the main driver class inside the jar. I have checked the documentation but there is no such information available about how to specify the main driver class.
While in Apache Zeppelin there is a default.Driver argument available which is user to specify the main driver class. There is no such option available here.
I guess this is the reason that's why i'm getting com.twosigma.beakerx.sql.DBConnectionException: No suitable driver exception.


Losing indexes with a large number of translations

Hi - I've run into the problem that I'm getting errors with a lot of translations:
WARNING:root:No original text found for index 378
WARNING:root:No original text found for index 379
WARNING:root:No original text found for index 380
WARNING:root:No original text found for index 381
WARNING:root:No original text found for index 382
WARNING:root:No original text found for index 383
WARNING:root:No original text found for index 384
WARNING:root:No original text found for index 385
WARNING:root:No original text found for index 386
WARNING:root:No original text found for index 387
WARNING:root:No original text found for index 388
WARNING:root:No original text found for index 389
WARNING:root:No original text found for index 390
WARNING:root:No original text found for index 391
WARNING:root:No original text found for index 392
WARNING:root:No original text found for index 393
WARNING:root:No original text found for index 394
WARNING:root:No original text found for index 395
WARNING:root:No original text found for index 396
WARNING:root:No original text found for index 397
WARNING:root:No original text found for index 398
WARNING:root:No original text found for index 399

The result further is a translation turnout:
msgid "number"
msgstr "Bokning av plats för buss."

msgid "Booking date."
msgstr "Tillvaltvätt."

msgid "Booking data."
msgstr "Bokning av VIP-plats."

msgid "Number of people."
msgstr "VIP Access."

Additionally, it is not possible to run the program without the bulk parameter:
INFO:root:Discovered .po file: ../mysoft-test/locale/sv/LC_MESSAGES/django.po
INFO:root:Attempting to infer language for .po file: ../mysoft-test/locale/sv/LC_MESSAGES/django.po
INFO:root:Inferred language for .po file: ../mysoft-test/locale/sv/LC_MESSAGES/django.po as sv
INFO:root:Translating text 1/380 in file ../mysoft-test/locale/sv/LC_MESSAGES/django.po
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
INFO:root:Raw API response: 0: Det går inte att redigera denna bokning.
ERROR:root:Error processing file ../mysoft-test/locale/sv/LC_MESSAGES/django.po: cannot unpack non-iterable int object

Exact same issue here, tried installation from git and pip.

Can you deliver some files that we can test?

Closing for now please let us know if this is still an issue, later and we will reopen it.

Okay this should be all fixed with this release:
https://github.com/pescheckit/python-gpt-po/releases/tag/0.2.2


implement google translate api or some language conversion

related to #5

requires a .env.local file that contains the API key.


App crashing on sign up link

This was reported. Not sure if there's a crash log somewhere...

I upgraded to the latest version so I could create an account and log in to update some machine conditions for some local games. (They were broken, now fixed.). However, the app crashes as soon as I click the "sign up" link.
I'm running iOS version 8.4 on an iPhone 5s.
Thanks for the great app!

8.4 is really old.

2015, yeah... my hunch is that this is related to that last REJECTION we
got from the Apple store. Remember how they said we were doing our embedded
webpage stuff wrong?
I'm guessing the embedded webpage stuff we are using isn't available in 8.4?
On Thu, Apr 20, 2017 at 1:50 PM, RyanTG<EMAIL_ADDRESS>wrote:

8.4 is really old.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scottwainstock/pbm-ios/issues/143#issuecomment-295906597,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK-Lchr3cYAJoAJDYMAuhDb8DF0wyQKks5rx8UFgaJpZM4NDhPf
.

Alright, I'll close this. And if we ever get a sign up page added to the app, it'll probably fix this.


[minor] add disable swap command

Proposed changes

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

@xiaokang Hi, Do we need this pr?

@xiedeyantu Yes, can you submit a pr for branch-2.0

run buildall

@xiaokang Hi, do we need to merge to master?

run buildall


fix(fluent bit): update filters to work for various k8s distros

Description: The previous filter needed its regex to be updated to match the specific distro osm is being run on. This update makes the log level filter work on moby, containerd and cri-o.

Affected area:

New Functionality      [ ]
Documentation          [x]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [x]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
no, no

Codecov Report

Merging #2170 (992a429) into main (f493bfa) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2170      +/-   ##
==========================================
- Coverage   58.34%   58.32%   -0.02%
==========================================
  Files         145      145
  Lines        6143     6143
==========================================
- Hits         3584     3583       -1
- Misses       2556     2557       +1
  Partials        3        3

Impacted Files
Coverage Δ

pkg/envoy/route/config.go
95.23% <0.00%> (-0.80%)
:arrow_down:

Continue to review full report at Codecov.

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


test: Do not require netpols in 'waitNextPolicyRevisions()'

'waitNextPolicyRevisions()' currently returns 'true' when no k8s
network policies are applied, bypassing the Cilium agent policy
revision wait in this case. As our tests typically (never?) have no
NPs applied, we have not actually waited for CNP or CCNP changes to
take place in all Cilium PODs before proceeding with the tests. This
may have caused CI flakes.
Fix this by removing the code that checks for the presence of NPs.
Reported-by: Paul Chaignon<EMAIL_ADDRESS>Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

/test

/test

Reviews are in. All affected test suites passed except for k8s-1.20-kernel-5.4 which failed with known flake https://github.com/cilium/cilium/issues/16852. Marking ready to merge and merging.


Need to apply path validation to object-to-write

Allow:

{
  '.a': 'x'
}
{
  '*': 'x'
}

Not allow:

{
  '.': 'x'
}
{
  'a.': 'x'
}
{
  'a.b': 'x'
}
{
  '*a': 'x'
}
{
  'a*': 'x'
}
{
  'a*b': 'x'
}

Full list of reserved characters: https://docs.ainetwork.ai/ai-network-design/blockchain-database/states/predefined-structures

Does it mean not to allow ref with char '.'?

@minsulee2  Yes, the same policy applied to the db path will be applied to the state object: https://github.com/ainblockchain/ain-blockchain/issues/50

Indeed! edited one is way clearer!! thanks for the updates!


Consistent log_level after knife bootstrap

Linux nodes are bootstraped with no 'log_level' entry in client.rb, defaulting to :auto
Windows nodes are bootstraped with 'log_level        :info' in client.rb
I haven't tested other operating systems, but please have consistency of log_level across platforms.
Workstation:
[07:53:29 ~/gitin/chef-repo (master) ]$ chef -v
Chef Development Kit Version: 0.3.5
Nodes:
CentOS 6.6 and Windows2012r2 bootstrapped with chef-client 12.0.3

"knife bootstrap windows" is from knife-windows so this issue should probably go under that repo to remote that default?


Clustermesh cluster connection is abnormal     clustermesh  can't  attach  two  clusters

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After creating two Kubernetes clusters under the same VPC on Alibaba Cloud, I attempted to use Cilium Clustermesh to connect the pod networks of the two nodes. However, I discovered that while I can resolve the IPs generated by MetalLB, they are unreachable via telnet. The Cilium Clustermesh cluster connection is abnormal, despite having confirmed that all security group rules are set to allow traffic.
Cilium Version
root@node02:~/cilium# cilium  version
cilium-cli: v0.16.10 compiled with go1.22.4 on linux/amd64
cilium image (default): v1.15.5
cilium image (stable): v1.15.6
cilium image (running): 1.15.6
root@node02:~/cilium# helm ls -A
NAME   	NAMESPACE     	REVISION	UPDATED                                	STATUS  	CHART         	APP VERSION
cilium 	kube-system   	4       	2024-06-20 06:48:06.92243168 +0800 CST 	deployed	cilium-1.15.6 	1.15.6
metallb	metallb-system	1       	2024-06-20 06:19:48.793677708 +0800 CST	deployed	metallb-0.14.5	v0.14.5
Kernel Version
root@node02:~/cilium# uname -ra
Linux node02 5.15.0-107-generic #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
ubuntu2204
Kubernetes Version
root@node02:~/cilium# kubectl  get nodes
NAME     STATUS   ROLES    AGE   VERSION
node02   Ready    master   8h    v1.28.1
also  the node
Regression
No response
Sysdump
No response
Relevant log output
root@node02:~/cilium# ^C
root@node02:~/cilium# cilium   clustermesh  connect  --context  context-cluster2  --destination-context  context-cluster3
✨ Extracting access information of cluster cluster3...
🔑 Extracting secrets from cluster cluster3...
ℹ  Found ClusterMesh service IPs: [<IP_ADDRESS>]
✨ Extracting access information of cluster cluster2...
🔑 Extracting secrets from cluster cluster2...
ℹ  Found ClusterMesh service IPs: [<IP_ADDRESS>]
ℹ Configuring Cilium in cluster 'cluster2' to connect to cluster 'cluster3'
ℹ Configuring Cilium in cluster 'cluster3' to connect to cluster 'cluster2'
✅ Connected cluster cluster2 and cluster3!

root@node02:~/cilium# cilium   clustermesh  status
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
✅ Cluster access information is available:
  - <IP_ADDRESS>:2379
✅ Deployment clustermesh-apiserver is ready
ℹ  KVStoreMesh is disabled

⚠  1/1 nodes are not connected to all clusters [min:0 / avg:0.0 / max:0]

🔌 Cluster Connections:
  - cluster3: 1/1 configured, 0/1 connected

🔀 Global services: [ min:0 / avg:0.0 / max:0 ]

❌ 1 Errors:
  ❌ cilium-mkk5z is not connected to cluster cluster3: Waiting for initial connection to be established
     💡 Run 'kubectl exec -it -n kube-system cilium-mkk5z -c cilium-agent -- cilium-dbg troubleshoot clustermesh cluster3' to investigate the cause

root@node02:~/cilium# cilium   clustermesh  status
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
✅ Cluster access information is available:
  - <IP_ADDRESS>:2379
✅ Deployment clustermesh-apiserver is ready
ℹ  KVStoreMesh is disabled

⚠  1/1 nodes are not connected to all clusters [min:0 / avg:0.0 / max:0]

🔌 Cluster Connections:
  - cluster3: 1/1 configured, 0/1 connected

🔀 Global services: [ min:0 / avg:0.0 / max:0 ]

❌ 1 Errors:
  ❌ cilium-mkk5z is not connected to cluster cluster3: Waiting for initial connection to be established
     💡 Run 'kubectl exec -it -n kube-system cilium-mkk5z -c cilium-agent -- cilium-dbg troubleshoot clustermesh cluster3' to investigate the cause
root@node02:~/cilium# kubectl exec -it -n kube-system cilium-mkk5z -c cilium-agent -- cilium-dbg troubleshoot clustermesh cluster3
Found 1 remote cluster configurations
Troubleshooting filtered subset of clusters: cluster3

Remote cluster "cluster3":
📄 Configuration path: /var/lib/cilium/clustermesh/cluster3

🔌 Endpoints:
   - https://cluster3.mesh.cilium.io:2379
     ✅ Hostname resolved to: <IP_ADDRESS>
     ❌ Cannot establish TCP connection to cluster3.mesh.cilium.io:2379: dial tcp <IP_ADDRESS>:2379: i/o timeout

🔑 Digital certificates:
   ✅ TLS Root CA certificates:
      - Serial number:       52:7e:f0:59:44:20:e9:fb:83:03:02:59:6f:88:a7:4d
        Subject:             CN=Cilium CA
        Issuer:              CN=Cilium CA
        Validity:
          Not before:  2024-06-19 22:16:22 +0000 UTC
          Not after:   2027-06-19 22:16:22 +0000 UTC
   ✅ TLS client certificates:
      - Serial number:       60:32:72:63:10:46:c7:81:c8:1d:fa:c5:c3:7b:12:5b:f1:23:1d:f0
        Subject:             CN=remote
        Issuer:              CN=Cilium CA
        Validity:
          Not before:  2024-06-19 22:43:00 +0000 UTC
          Not after:   2027-06-19 22:43:00 +0000 UTC

⚙ Etcd client:
   ❌ Failed to establish connection: context deadline exceeded

root@node02:~/cilium# kubectl -n kube-system exec -ti cilium-mkk5z -- cilium-health status
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
Probe time:   2024-06-19T23:06:09Z
Nodes:
  cluster2/node02 (localhost):
    Host connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=231.813µs
      HTTP to agent:   OK, RTT=291.149µs
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=267.205µs
      HTTP to agent:   OK, RTT=329.638µs

root@node02:~/cilium# kubectl -n kube-system exec -ti cilium-mkk5z -- bash
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
root@node02:/home/cilium# cilium-dbg monitor --type drop
Listening for events on 8 CPUs with 64x4096 of shared memory
Press Ctrl-C to quit
time="2024-06-19T23:07:55Z" level=info msg="Initializing dissection cache..." subsys=monitor
xx drop (Unsupported L3 protocol) flow 0x0 to endpoint 0, ifindex 27, file bpf_lxc.c:1496, , identity 177135->unknown: fe80::b494:61ff:fe15:f42 -> ff02::2 RouterSolicitation

Anything else?
I  have  tested   over   5  times
k8s  node02    mteallb   <IP_ADDRESS>:2379
k8s  node03    mteallb   <IP_ADDRESS>:2379
Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

k8s02  podcidr   # K8S Service CIDR, not overlap with node(host) networking
SERVICE_CIDR="<IP_ADDRESS>/16"
Cluster CIDR (Pod CIDR), not overlap with node(host) networking
CLUSTER_CIDR="<IP_ADDRESS>/16"
NodePort Range
NODE_PORT_RANGE="30000-32767"
k8s03  podcidr# K8S Service CIDR, not overlap with node(host) networking
SERVICE_CIDR="<IP_ADDRESS>/16"
Cluster CIDR (Pod CIDR), not overlap with node(host) networking
CLUSTER_CIDR="<IP_ADDRESS>/16"
NodePort Range
NODE_PORT_RANGE="30000-32767"
Cluster DNS Domain
CLUSTER_DNS_DOMAIN="cluster.local"
cilium  cidr  with  helm---k8snode02
ipam:
-- Configure IP Address Management mode.
ref: https://docs.cilium.io/en/stable/network/concepts/ipam/
mode: "cluster-pool"
-- Maximum rate at which the CiliumNode custom resource is updated.
ciliumNodeUpdateRate: "15s"
operator:
# -- IPv4 CIDR list range to delegate to individual nodes for IPAM.
clusterPoolIPv4PodCIDRList: ["<IP_ADDRESS>/8"]
ipv4NativeRoutingCIDR: "<IP_ADDRESS>/8"
k8snode03  is  the same
by the  way,ihave  tested  differernt  podcidr  3times

Hi @15927561940,
The error is that the node in the first cluster cannot access the clustermesh-apiserver in the second one:
- https://cluster3.mesh.cilium.io:2379
     ✅ Hostname resolved to: <IP_ADDRESS>
     ❌ Cannot establish TCP connection to cluster3.mesh.cilium.io:2379: dial tcp <IP_ADDRESS>:2379: i/o timeout

This typically indicates issues in the underlying VPC or security groups configuration, or in the LoadBalancer settings. I'd suggest trying to ssh into the node and verifying that you can correctly curl <IP_ADDRESS>:2379, as well as that the clustermesh-apiserver pod is correctly up and running in both clusters.


Content-Type: PUT java.nio.charset.UnsupportedCharsetException: 1

I'm trying to do a PUT with the following Content-Type:
Content-Type : application/vnd.app.test+json;ton-version=1
Getting the following error:
java.nio.charset.UnsupportedCharsetException: 1
at java.nio.charset.Charset.forName(Charset.java:531)
at org.apache.http.entity.ContentType.create(ContentType.java:234)
at org.apache.http.entity.ContentType.withCharset(ContentType.java:426)
at com.intuit.karate.http.apache.ApacheHttpUtils.createContentType(ApacheHttpUtils.java:103)
at com.intuit.karate.http.apache.ApacheHttpClient.getEntity(ApacheHttpClient.java:218)
at com.intuit.karate.http.apache.ApacheHttpClient.getEntity(ApacheHttpClient.java:77)
at com.intuit.karate.http.HttpClient.getEntityInternal(HttpClient.java:93)
at com.intuit.karate.http.HttpClient.buildRequestInternal(HttpClient.java:188)
at com.intuit.karate.http.HttpClient.invoke(HttpClient.java:207)
at com.intuit.karate.StepDefs.method(StepDefs.java:357)
at ✽.When method put...
But the same Content-Type was able to do a GET.
Background:
* Calling common.feature
* def someData = { Authorization: #(authToken),  'Content-Type': 'application/vnd.app.test+json;ton-version=1' }
* headers someData
Scenario: Create data
Given path '/data/test/id'
And request read(jsonData.json)
When method put
Then status 201
This will throw java.nio.charset.UnsupportedCharsetException: 1 exception
Also tried to add headers in the scenario, if i add 'Content-Type'  (single quote ) then its getting adding the Content-Type to the request but also adding the single quotes as well. This will throw unsupported media type error.
Scenario: Create data
Given path '/data/test/id'
And request read(jsonData.json)
And header  'Content-Type' = 'application/vnd.app.test+json;ton-version=1'
And header Authorization = 'authtoken'
When method put
Then status 201
Any help is much appreciated.

Well seems like Karate setting the Content-Type by default based on data type of the request.
In my case though i'm sending the type as json data but Content-Type is different.

PUT request:

ref #302 and #298 some changes went into content-type handling recently.
can you try version 0.7.0.RC7 - here is the upgrade guide: https://github.com/intuit/karate/wiki/Upgrading-To-0.7.0
leaving this open because some extra work went into this commit: https://github.com/intuit/karate/commit/3c1f1916a020ab083810dc7f911b1840e8bf9d12 - and needs testing

Tested with the 0.7.0.RC7. Now its unable to run any .feature files.
Getting the following error:

Trying to run Simple  feature file:
Feature: Test
Scenario: Testing
Given def color = 'red '
And def num = 5
Then assert color + num == 'red 5'
In the test report we dont see anything, just Scenario:Heading...

Its working if i add the headers in the Scenario with the 0.7.0.RC7 but setting headers in the Background its not.
Background:
*** configure headers = { Authorization: #(authToken), 'Content-Type': 'application/vnd.test.t+json;o-version=1' }**
Scenario: Test
Given path '/metadata/ecpregistry/dataset/ecp:1-a9bc14d9-30e9-431c-b738-ed5a1f3a7e4a'
And request test
When method put
Then status 200
This still sets the Content-Type as : application/json
Where as if i add headers in the scenario, it works:
Scenario: Test
Given path '/test'
And request test
And header Authorization = authToken
And header Content-Type = 'application/vnd.test.t+json;o-version=1'
When method put
Then status 200
It would be great if we can add headers in the Background so that we dont need to add for every scenario.

are you able to build from source, please try the develop branch.

@g-one forgot to mention, if you switch to karate-jersey from karate-apache in your pom.xml, it should work. so you can use that until the next version is released.

@g-one can you try with 0.7.0.RC8 and confirm please, thanks.


Feature/typescript sample app pneely

Issue #, if available:
Description of changes:
Add async flow for writing batches of products to dynamodb
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I merged main into my branch, which has bloated the number of changed files. I'll take main out and resubmit.


Scroll down using trackpad in the main menu doesn't work

I expect to be able to scroll down using my trackpad in the main screen, but it doesn't register it. Instead I have to either drag or click on the arrow for it to go to the page:
https://github.com/user-attachments/assets/5fc01a98-36b8-4ea9-946a-d3c4401cf260

This might be "by design", but we also may want to revisit the design.

Dragging works, but dragging is mobile's way of scrolling. So as a user I'd expect trackpad scrolls to do the same as dragging on my phone.
https://github.com/user-attachments/assets/2d0dd5db-475c-4dd3-bc1a-72ae3bef548c

This is by design, but mainly due to a technical limitation where we couldn't get it to feel right. Because this is a page transition, and not a signle scrollable page, it just didn't feel "right" when when tied the page transition to the scroll wheel.
We can take another stab at this, and see if we can nail it down with a second pass.


Display tooltip when pressing a point in a line containing multiple points that all have the same x value.

** Don't make a duplicate issue.
It does not appear to a similar issue for this (if there is, i apologise).
Thank you for a great package!
After many tries there does not seem to be a way to display a tooltip when pressing a singular point in a line that has multiple points that all have the same x value in a graph.

Am i missing something. The touchCallback function always returns the lowest point on the line when clicking other points.

Hi. What do you prefer? Showing tooltip on the point, you touch? Or the highest one?

It seems like you want to show the tooltip for the dot you press? By default only the x distance between the touch to the dot is used to find the closest one. Using LineTouchData.distanceCalculator you can write your own function that uses the Euclidean distance. This would then select the dot you press.

Hi. What do you prefer? Showing tooltip on the point, you touch? Or the highest one?

Showing the tooltip on the point (or right above the point)

It seems like you want to show the tooltip for the dot you press? By default only the x distance between the touch to the dot is used to find the closest one. Using LineTouchData.distanceCalculator you can write your own function that uses the Euclidean distance. This would then select the dot you press.

Cool i will try it out!

how did it work out? currently trying out a similar thing

Can you please add some sample code how to use LineTouchData.distanceCalculator to show the tooltip for the dot you press?


dynamic function in ng-repeat not working.

Hi I am facing one problem in ng-repeat.
When I iterate an a list using ng-repeat and binding a dynamic function using ng-click.
When I click on that list, the function binded through ng-repeat is not getting triggered. Instead throwing some error.
Please help in solving this . Thanks.

Hi rajzshkr,can u give example here then easily i can understand will solve your problem.

this is html

{{dt.name}}

js file looks like(test.js)
angular.module("testApp", []).controller('testController', function(
$scope, messageService)
{
$scope.data = [
{
"name": "veeru",
"function": "one()"
},
{
"name": "veeru1",
"function": "two()"
},
{
"name": "veeru2",
"function": "three()"
},
{
"name": "veeru3",
"function": "four()"
},
{
"name": "veeru4",
"function": "five()"
},
{
"name": "veeru5",
"function": "six()"
}, ]
$scope.clickMe = function(data)
{
console.log(data);//here you will get trigger what ever you clicked that object data will come.
}
});
this is dynamicallu binding ng-click and getting current triggered object.i think this useful useful for you if you not clear please ping me mail<EMAIL_ADDRESS>

Hi, please ask support questions on one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question
Btw, you'll increase the chance of getting help by including the error message and a runnable example of your problem in a plnkr.co or similar.

I did not find out here how to ask support question in this https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question, site.
can u give please give exact place in this site.

http://jsbin.com/fofelu/1/.
Please check the above bin. Still it is not working.

here we cant this way because what ever u mentioned inside json  "action":
"test1()"
it will take string type only but not function
so here i did example please see this.
http://jsfiddle.net/veerendrakumarfiddle/nkuDW/77/
Thank Q,with your regards..
vallepu veerendra kumar.
On Mon, Mar 2, 2015 at 6:14 PM, Raja Sekar<EMAIL_ADDRESS>wrote:

http://jsbin.com/fofelu/1/.
Please check the above bin. Still it is not working.
--
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/issues/11218#issuecomment-76705478
.


Add support for enum descriptions

Currently enum descriptions are not being translated to the OpenAPI result.
The conversion process should leverage x-ms-enum extension for the time being, until OpenAPI.net supports 3.1

https://github.com/Azure/autorest/blob/main/docs/extensions/readme.md#x-ms-enum


Location argument returns wrong location in v1.5

In version 1.5 the location argument doesn't work properly, It returns the wrong location.
Example:
If I'm at the coordinates 50 10 20 and run:
/test ~ ~1 ~
(So the first argument is type location)
The expected location to return is: 50 11 20
But the actual location is I get back is: 50.5 50.5 50.5

I have been unable to reproduce this issue in version 1.5:
My code:
//Generate arguments and command
LinkedHashMap<String, Argument> arguments = new LinkedHashMap<>();
arguments.put("loc", new LocationArgument());
CommandAPI.getInstance().register("myloc", arguments, (sender, args) -> {
    //Resultant location from argument
    Location loc = (Location) args[0];
    sender.sendMessage("Location argument: (" + loc.getBlockX() + " " + loc.getBlockY() + " " +  loc.getBlockZ() + ")");

    //My current location
    Location currentLoc = ((Player) sender).getLocation();
    sender.sendMessage("Current location: (" + currentLoc.getBlockX() + " " + currentLoc.getBlockY() + " " +  currentLoc.getBlockZ() + ")");
    sender.sendMessage(" ");
});

Result from the command /myloc ~ ~1 ~:

This is the code I use:
(It's a command that set's the motion of the selector)
private void motionCommand() {
    LinkedHashMap<String, Argument> arguments = new LinkedHashMap<>();
    arguments.put("motion", new LocationArgument());

    CommandAPI.getInstance().register("motion", arguments, (sender, args) -> {
        CommandSender callee = sender;

        //when using execute, differentiate sender and caller
        if (sender instanceof ProxiedCommandSender) {
            callee = ((ProxiedCommandSender) sender).getCallee();
            sender = ((ProxiedCommandSender) sender).getCaller();
        }

        if (callee instanceof Entity) {
            Entity entity = (Entity) callee;
            Location loc1 = (Location) args[0];
            Location loc2 = entity.getLocation();
            sender.sendMessage("Location argument: (" + loc1.getBlockX() + " " + loc1.getBlockY() + " " +  loc1.getBlockZ() + ")");
            sender.sendMessage("Current location: (" + loc2.getBlockX() + " " + loc2.getBlockY() + " " +  loc2.getBlockZ() + ")");
            Vector motion = loc1.toVector().subtract(loc2.toVector());
            setVelocity(motion, entity, sender);
        }
    });
}

My output to /motion ~ ~1 ~ is:

In version 1.4 everything works just fine.

I believe the issue relates to issue #20.
This is resolved in version 1.6.

Yep! Works fine again in 1.6!


Support BOOST_ASIO_NO_TS_EXECUTORS

This adds support for using Boost Asio with BOOST_ASIO_NO_TS_EXECUTORS being defined.
It adds a preprocessor definition MQTT_NO_TS_EXECUTORS to determine which executor style to use.
This is present as a CMake option as well.
The preprocessor argument is either defined by CMake or is forced in case BOOST_ASIO_NO_TS_EXECUTORS have been defined w/out MQTT_NO_TS_EXECUTORS - see addition to mqtt/config.hpp.
Thus mqtt_cpp code will still be compliant even if the user did not explicitly enable the CMake option.
Even though a CMake option has been added, the CI tests have not been modified.
Hence automatic testing does not include MQTT_NO_TS_EXECUTORS yet.
If this is to be added to the tests on the CI, boost.sh would also have to be modified.
It currently builds Boost 1.72.0 but at least 1.74.0 / Asio 1.18.0 is required to use the standard executors.

This is linked to #829

Now, I accepted CI run. It requires for the first time contribution.
I think that the PR is not tested by CI.
So the option BOOST_ASIO_NO_TS_EXECUTORS  should be added to one of the CI builds.
I think that the following one is a good candidate.
https://github.com/redboltz/mqtt_cpp/blob/117155f8ee803f5bd046d05970c98d59a2617a52/.github/workflows/gha.yml#L80
The parallel builds are limited by the Github Actions. So I picked up some of typical case based on orthogonal array.
https://en.wikipedia.org/wiki/Orthogonal_array
In order to use BOOST_ASIO_NO_TS_EXECUTORS, maybe boost should be updated.
https://github.com/redboltz/mqtt_cpp/blob/117155f8ee803f5bd046d05970c98d59a2617a52/.github/depends/boost.sh#L36-L39
https://github.com/redboltz/mqtt_cpp/blob/117155f8ee803f5bd046d05970c98d59a2617a52/.github/workflows/gha.yml#L59
Could you update CI ?

Thanks for the feedback.
I'm happy to add the test to the CI.
Thank you for already suggesting / picking a test case candidate.
About updating the boost version:
https://github.com/redboltz/mqtt_cpp/blob/117155f8ee803f5bd046d05970c98d59a2617a52/.github/workflows/gha.yml#L59
Is there any specific pattern in the date part of the cache key 20200107?
Do you want me to add any specific date - e.g. boost verion's release date?
Or should it just be the commit date 20210816?

Thanks for the feedback.
I'm happy to add the test to the CI.
Thank you for already suggesting / picking a test case candidate.
About updating the boost version:
https://github.com/redboltz/mqtt_cpp/blob/117155f8ee803f5bd046d05970c98d59a2617a52/.github/workflows/gha.yml#L59
Is there any specific pattern in the date part of the cache key 20200107?
Do you want me to add any specific date - e.g. boost verion's release date?
Or should it just be the commit date 20210816?

I don't know much about cache mechanisim.
I guess that the commit date is good.
Here is a document for cache. https://github.com/actions/cache#creating-a-cache-key

Maybe security reason, the first time contributor for the project like you cannot run CI automatically.
I need to click "accept CI run" button. Even if I did it one time but github asks me anytime the PR updated.
So my response would become slow.
You can also run CI on your github account. If you want to test CI with quick turn around time, you can use it.

I'll try setup CI runs on my account for now and change the branch to avoid triggering CI here until it works.

In order to run CI on your github account, I recommend modifying as follows:
https://github.com/redboltz/mqtt_cpp/blob/master/.github/workflows/gha.yml#L8
Before
on:
  pull_request:
    types: [opened, synchronize]
  push:
    branches:
    - master
    tags:
    - '*'

After (for only temporary)
on:
  pull_request:
    types: [opened, synchronize]
  push:
    branches:
    - '*'
    tags:
    - '*'

When you push something, the CI always run.
You can see CI on the top "Actions" menu.
Azure build pilelines is different from Github Actions. It is more complicated. I think that you don't need to run it.
NOTE: Github Actions has windows build. But I use Azure build pipelines for windows build because it can avoid parallel builds limits. (Many builds can run parallelly). Unfortunately it is less convenient that Github Actions.

Changes are in.
I've used a using strand = as::strand<as::io_context::executor_type> scheme instead of #define MQTT_STRAND as::strand<as::io_context::executor_type> though.
This looked cleaner to me but can change to #define if you favor this one.
The CI is supposed to test MQTT_NO_TS_EXECUTORS as part of the test you selected (linux 4) which passed on my CI.

using strand is better than macro. Thank you.
The similar approach has been applied to null_strand. It is good too.

It seems that CI has been passed and codecov reported a coverage. The result is good. So I merge it soon.

Merged. @DinoMe , thank you for your contribution !!

Great. @redboltz, thanks a lot for merging and accepting my changes.


Use openstreetmap with react-native-maps

Hello!, i'm curious to know if we can use openstreetmaps with this component instead of google or apple's maps. Anything about this?

We'd like to add MapBox support, which would open the door to OpenStreetMaps.
Feel free to submit a PR :)

?

is it Possible to use OSM yet?
Please...

Yes it is, but for some reason you still need a google api key. Without it, nothing renders. For me it looks like, as if it would get google maps tiles and re-render it with osm tiles (weird). You can see the google tiles for a fraction of a second, eventually it looks like re-rendering with osm tiles. I will check my connection with a sniffer, whether I'm getting tiles from google or osm and tell you more.

we can use openstreet maps ? and this lib not request to google maps API ?


Support password authentication

In #148 we introduced token authentication that ensures the app is not accessible by anyone else by default. For cloud deployment ideally we should be able to use --no-token and then specify an arbitrary password that people can use to authenticate.
The password should probably be set as an environment variable, so that it's not visible when listing processes (like ps aux). Although one may argue that if someone has access to the server, it doesn't really matter ^^

So basically you want ability to set permanent token from ENV variable?

Actually these are slightly different things. The token only serves as a default protection when running the notebook locally. The primary difference is that a password shouldn't be passed as a URL param, but be send via form.
Making it possible to specify the token does sound like an alternative, but then it's not really a password per se and such model is less secure.
Theoretically we could reuse Plug.BasicAuth, but we don't really need a username, so ideally we would have a form similar to the token one, but for the password (although the token form does a simple GET and reuses the query logic, while for the password it should make a proper POST).
That's how I see the authentication, happy to hear opinions on security :>

I see. I'll take a look on that issue then, seems interesting to me.
So as a result, when user loads app first time, he will see a form similar to token form we have now, but it's POST instead, and password is static and defined by ENV. One question though, I'm not that familiar with configuration options, how can I serve --no-token to the app?

Yeah, the CLI configuration is not really visible at this point because temporarily we suggest using mix phx.server. The options refer to Escript, specifically those handled here, but eventually they simply update relevant applications' configurations (so that we have a unified way of configuring things, regardless how the app is started).
Given the above, if you want to look into that, the best way to start would be to simply hardcode a password in the configuration files (something like config :livebook, :auth_password, "password" here) and then work from there.

Yeah I found that mix is actually resets System.argv(), so no CLI arguments there.
I found this row:
config :livebook, :token_authentication, true

But it seems that it disables auth completely. I don't want to change this behaviour since it might be in use for someone else. Really that's the only thing I stuck now huh. I'll add one more config var for now, but it's a subject of discussion for sure.

We override this config in development, so that token auth is disabled. These are two distinct auth schemes though :>

I actually think that we might use this kind of config:
config :livebook, :authentication_schema, :token # or :password, :disabled

And call token_authentication deprecated. WDYT?

This way we enforce a single auth scheme, but this sounds good to me. Then we could check the specific scheme here. Note that the given scheme may require further configuration (e.g. the actual password value), but we can use a separate config option for that. @josevalim WDYT?


Make it compatible with @ember/test-helpers and ember-qunit v5

Unblocks san650/ember-cli-page-object#524

Because ember-qunit v5 has complex setup, this addon is not used by modern apps it does not seem feasible to spend time at this point and add ember-try scenario.
@cibernox would you be able to release a patch version of this so that apps using ember-cli-page-object could upgrade to Ember 3.24?

Because ember-qunit v5 has complex setup, this addon is not used by modern apps it does not seem feasible to spend time at this point and add ember-try scenario.
@cibernox would you be able to release a patch version of this so that apps using ember-cli-page-object could upgrade to Ember 3.24?

@rwjblue safari as I remember settled has same behavior as wait so should be simple swap.
BTW would it require major version bump? I'm not sure if it's small enough change

@rwjblue safari as I remember settled has same behavior as wait so should be simple swap.
BTW would it require major version bump? I'm not sure if it's small enough change

Merged and released in 0.7.0

Merged and released in 0.7.0


feat: Parse markdown in conversation greeting

Summary
I added support for Markdown in modelSpecs.greeting similar to the implementation of Markdown support in the enviroment variable CUSTOM_FOOTER.
Change Type
Please delete any irrelevant options.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Testing
I run all tests of npm run test:client, all passed.
I then built the container and started the app. With modelSpecs configured as described below. All types of greetings were rendered.
Test Configuration:
modelSpecs:
  list:
    - name: markdown-greeting
      default: false
      label: Markdown Greeting
      description: "Test Markdown"
      preset:
        endpoint: "azureOpenAI"
        model: gpt-4
        modelLabel: Markdown Greeting
        greeting: |
          ## Welcome to Markdown Greeting

          [LibreChat](https://www.librechat.ai/)
    - name: plain-greeting
      default: false
      label: Markdown Greeting
      description: "Test Plain"
      preset:
        endpoint: "azureOpenAI"
        model: gpt-4
        modelLabel: Markdown Greeting
        greeting: |
          Welcome to Plain Greeting
    - name: no-greeting
      default: false
      label: No Greeting
      description: "Test no greeting"
      preset:
        endpoint: "azureOpenAI"
        model: gpt-4
        modelLabel: No Greeting

Checklist
Please delete any irrelevant options.

[x] My code adheres to this project's style guidelines
[x] I have performed a self-review of my own code
[x] I have made pertinent documentation changes
[x] My changes do not introduce new warnings
[x] Local unit tests pass with my changes
[x] A pull request for updating the documentation has been submitted.

See https://github.com/LibreChat-AI/librechat.ai/pull/118 for documentation change

Seems very needed improvement for the greeting message !


We really want this to happen!

Please fill in the gaps:
Windows
TODO: write me. If you really want to see this happen, let us know by filing a bug report!

Thanks for checking out Chisel and for filing an issue about the stub Windows section of the README.
As this is written, it sounds like Windows is unsupported, but this is incorrect... While these are famous last words, Chisel should work just fine on Windows. Once you have sbt installed (https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Windows.html) you should be do Chisel development in this repo or build out a project (with chisel-template being a better repo to start from). As far as I'm aware, the known issues with Windows relate to Verilator, specifically some of the problems outlined here: https://github.com/freechipsproject/chisel3/issues/874.
I do not have access to any Windows machines, so some of the other devs can see about expanding the instructions here. However, you're more than welcome to take a stab at that.

I do regular development in chisel3 on Windows, and as has been said before, everything but Verilator works fine. The practical implication is that you won't be able to run the chisel3 regressions natively, but in general for simulation you can:

run Verilator in WSL or Cygwin. I've run the Chisel regression suite in WSL, and it works fine.
for pure Chisel code, you can use treadle, a Scala-based FIRRTL simulator. There is also some support for writing Scala models of blackboxes, eg AsyncResetReg. You'll either need to use the chisel-testers (http://github.com/ucb-bar/chisel-testers) or testers2 (http://github.com/ucb-bar/chisel-testers2), since chisel3 base currently doesn't have support for anything but Verilator.

Note that you'll be able to generate Verilog from Chisel just fine, which can be pushed to downstream (eg FPGA) tools.
As for this issue in particular, we should probably add instructions to the main README, I think it's mainly just 'download and install SBT'. And a discussion of limitations and trade-offs.


Document current files

All current files should include updated and accurate documentation.

Documentation is up to date in 9ed8134c8b26fced21a9d7ba5c714dc7eeda0cf5.


Docs

Aware that this is already planned by the readme, but I thought that I might open this issue to track it anyways. Might suggest a few things, since documenting svelte components can be made a lot easier than expected.
Few neat things that can help:

https://mdsvex.pngwn.io/ is useful for embedding components in markdown (svx files can also serve as SvelteKit routes).
https://github.com/mattjennings/vite-plugin-sveld automatically generates component API documentation based on typescript definitions and JSDoc comments in your components.

Thanks for filing & for the tooling suggestions! I definitely do intend on including project-specific docs here.
At the moment I think the https://headlessui.dev React docs hopefully work well enough to be usable & so I've been focusing on porting over the test files. After that's finished I'll turn back to the docs.

Thanks for filing & for the tooling suggestions! I definitely do intend on including project-specific docs here.
At the moment I think the https://headlessui.dev React docs hopefully work well enough to be usable & so I've been focusing on porting over the test files. After that's finished I'll turn back to the docs.

Are all of the components listed there available here as of now or are there some that are still to be ported over?

Thanks for filing & for the tooling suggestions! I definitely do intend on including project-specific docs here.
At the moment I think the https://headlessui.dev React docs hopefully work well enough to be usable & so I've been focusing on porting over the test files. After that's finished I'll turn back to the docs.

Are all of the components listed there available here as of now or are there some that are still to be ported over?

Yep, they're all available! It's a full port :)

Yep, they're all available! It's a full port :)

Fantastic news. A couple of months ago I was thinking of doing this myself so it's definitely nice to see. Thanks for doing this

Fantastic news. A couple of months ago I was thinking of doing this myself so it's definitely nice to see. Thanks for doing this

Fantastic news. A couple of months ago I was thinking of doing this myself so it's definitely nice to see. Thanks for doing this

Exactly the same thought!
Thank you so much @rgossiaux for this!
I suppose we can piggy back of the React docs, but just show how to transform into the svelte version?

I started porting the official Tailwind UI components which were given away free by Tailwind Labs here: https://codeberg.org/vhs/svelte-tailwindui-freebies.
Having the freebies ported to Svelte would serve as living documentation as well as a test scaffold for this library. I've already ported the navigation and slide-out examples. If anyone wants to help porting the others, open the $lib folder and pull up the official component docs for React/Vue and have at it.

I just (finally) shipped initial docs in #61. They're accessible at https://svelte-headlessui.goss.io/


tree and adminLTE have some conflicts

Gijgo tree and the newly updated version of adminLTE have some conflicts.
In the background built by adminLTE, Gijgo tree is used, but it doesn't work.
before:

after:

Do you have any javascript errors in the console? Can you provide a sample code that could be in use for replication of the issue.

no.There's has no error in the console.Sorry, I can't provide you with demo.
If you can, use this plug-in on the basis of updating the latest version of adminLTE, and you may find the same problem.

Could you try to include gijgo.js after all other javascript files. I guess that this is going to fix the issue.

[图片]
Tree in the latest version of adminLTE also uses similar usage as yours. I think it's conflict here. I don't know if you can fix anything. Oh, yeah, you said that. I tested it. Still no effect.

In this case I think that would be best if you submit an issues in adminLTE and referance this ticket.
Can you try to exclude your referance of gijgo.js and see how it goes. Do you know what is the version of gijgo that is in use by adminLTE. I'm not able to see where gijgo is in use from their website at adminlte.io

No, no, no, I think you misunderstood.
AdminLTE doesn't use gijgo. it's just that its internal use of left navigation is similar to yours.
It's just a coincidence.
I'm sorry I can't provide you with demo. I'm really sorry.

I see. AdminLTE and gijgo define jquery function with same called tree, which is making some conflicts. We are going to think about that and improve it in future versions. We may change the name of the tree function to .gijgoTree(). Thanks for the feedback. Unfotunatelly we can't help you in a short term.

Ha ha, okay. Got it.
You can let me know when it's up to date. Thank you first.
I figured you'd change your name to .gijgoTree().
After all, this naming is unique.

For me it worked to include gijgo after admin-lte. thanks for the hint @atatanasov


Update reservation.html

Fix rendering issue: Reservation.html

Thank you for the fix ! I hope you liked this project !


Uncaught ReferenceError: Bloodhound is not defined

Have included google map and typeahead.Jquery is added through a gem and referenced in application.js

<script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=false&libraries=places&language=en-US"></script>
<script type="text/javascript" src="//cdnjs.cloudflare.com/ajax/libs/typeahead.js/0.9.3/typeahead.min.js"></script>
<script type="text/javascript" src="https://rawgithub.com/sgruhier/typeahead-addresspicker/master/dist/typeahead-addresspicker.js"></script>

2)Have added input text
<input id="address" type="text" placeholder="Enter an address">

3)Have instantiated address picker and typeahead.
$(document).on('ready page:load', function () {

    var addressPicker = new AddressPicker();

             $('#address').typeahead(null, {

                              displayKey: 'description',

                              source: addressPicker.ttAdapter()

              });

});

you should include typeahead.bundle.js which has typeahead + bloodhound
look at demo here https://twitter.github.io/typeahead.js/examples/, they include https://twitter.github.io/typeahead.js/releases/latest/typeahead.bundle.js
I don't know which version is on cloudflare

Yes that was the issue.You can close the issue,thanks


Unity version and packages update

Changes

Update Unity to 2021.3.41f1

Update existing packages

Add Acknowledgement file (for 3rd part assets and packages)

Add the following new packages:

Recorder
Fast Script Reload
SuperUnityBuild BuildTool
SuperUnityBuild BuildAction
Editor Toolbox
Better Attributes
DOTween
Animation Sequencer
PlayerPrefsEditor
Compilation Visualizer

Known Bugs/Issues
None found yet.
Testing Scene and Script
Just open Unity and test that everything is stable. Programmers may also want to test C# project with access to new packages.
Issue ticket number/link
None
Checklist before requesting a review

[X] I have performed a self-review of my code
[X] Make sure I am merging my features into the develop branch
[X] I have notified the other members of the programming team that my task is ready to review

Thank @KallenXCC, I'll wait for two more approvals before merging it in

Thanks @rwchaneyjr, I'll wait for one more approval before merging


TypeError in loading the model

Hi, I am trying to load the model in HuggingFace style. The following line in the code is giving the error:
model = MplugOwlForConditionalGeneration.from_pretrained(
pretrained_ckpt,
torch_dtype=torch.bfloat16,
)
The error I am getting is: TypeError: Object of type method is not JSON serializable
I have tried loading the model from a local repository as well. But no luck so far.

One things you can try is to install the transformer package with version 4.29.0. It may help.

It worked, thanks!

So what is the core cause of this? It is not a good solution to downgrade to an older version of transformers to use the model.

How I can I get it to work in 4.34.1? I have other models in the same project that can only work with recent versions of transformers.

How I can I get it to work in 4.34.1? I have other models in the same project that can only work with recent versions of transformers.

when hf tries to get string representations of the model, there's a module that cannot be converted to string. The fastest but dirty way is to modify the source code of hf where gives u the error, adding a try-except. If the module cannot be stringtized just set it to a certain string instead.

Thanks, I used
from transformers.configuration_utils import PretrainedConfig
from mplug_owl.configuration_mplug_owl import MplugOwlConfig

MplugOwlConfig.to_json_string = lambda *args, **kwargs: ''

as a temporary hack for loading.


rename MONDO:0016002 Ehlers-Danlos syndrome, kyphoscoliotic type 1

and add def to MONDO:0034024 kyphoscoliotic ehlers-danlos syndrome
addresses #1764

I think you linked to the wrong ticket?

yes - I fixed the link to the ticket, thanks!


Move file picker into StereoKitC

File picker is currently in Framework, and is not fully cross-platform compatible. For systems like UWP a custom file-picker UI cannot be used, since permissions are then not granted for that file. So, this needs:

[x] Native file picker for UWP
[x] Native 2D file pickers for Flatscreen
[x] Fallback StereoKit UI picker for MR platforms that don't have native pickers.

Only remaining platform without a native file picker in flatscreen mode is Linux.

Flatscreen file picker for Linux will come later. 🕙


Implemented yolo dataset support

I have implemented yolo dataset support to load data in the YOLO format as mentioned in #10. I have used the existing XML-to-COCO dataset and adapted it to support the yolo format.
The loader expects the image files to be either ".png", ".jpg", ".jpeg", ".bmp", ".tiff" and tries to find the best-matching one. Usually the img_path and ann_path are the same and contain .txt files as well as the image files.
Loading YOLO datasets can be slower because we have to open every image to determine the image size. This could be enhanced by using multi-processing, which currently is not implemented.

Thanks for your contribution! Would you like to add a brief introduction to the Yolo format dataset in the README?
You can add the introduction at here:
https://github.com/RangiLyu/nanodet/blob/d8ba391e33f9092314d1a0b204a8d3172852774b/README.md?plain=1#L218
Also, please run pip install pre-commit and then run pre-commit run --all-files to fix the lint.

Thank you for the hint about the formatting, I have updated the code using the pre-commit command.
Btw it was necessary to update the isort package to 5.12.0: https://github.com/PyCQA/isort/issues/2077

@RangiLyu Readme has been adjusted as well. Would be great if you could have a look again.


out of date I think

I think many are calling OpenTracing version 1 or something and it is here 0.20.7 including methods marked deprecated. If these methods are in fact no longer in the api, they should be removed instead of leading people on. If the api is version 1, then it should probably be marked so..
sound sensible?

Maybe we should release OpenTracing-java 1.0, remove all @deprecated APIs, and only follow the Spec 1.0

The OpenTracing spec itself is at v1.0; OT-Java is at whatever version it's at. :)
I am still grumpy that it has all of these impl helper classes (AbstractSpan, etc) in the core repo... they do not need to be there and tend to confuse people. And getting rid of the deprecated bits also makes plenty of sense.

The whole opentracing-impl thing is not part of Official OpenTracing-Java. :P
For me, these AbstractSpan classes (in opentracing-impl module, including NoopSpan)  like demonstrations or  reference implementations. Because OT does not require them.
@adriancole thoughts?

@bhs

I am still grumpy that it has all of these impl helper classes (AbstractSpan, etc) in the core repo...

:+1: Plus that you can't actually use them unless you move yourself into the io.opentracing.impl package (which may become overcrowded real soon for this exact reason!)

Spring cleaning (for issues) here: closing this issue as it is out of date. There is a milestone for v1.0.0 release of java, which can be found here: https://github.com/opentracing/opentracing-java/milestone/1
Feel free to create a new issue discussing what should be in the v1.0.0 milestone if you are interested.


Business model

Concept: “This package is free for apps with up to X data points per month. For apps which need to collect more than X monthly data points, you can get an unlimited site package for $Y”

So, would this be a solution that a user signs up for and we collect/store the data? Or would the data still be stored on their machine?

I think it would just limit the system to collecting X data points per month unless it was unlocked
But still be data that lives on their servers.
I'm sure there are other paths to monetization but that was one that I thought was interesting.

The X data points always seemed like something that I've always hated in services 🤪 but I'm down to explore that.
I was thinking we could offer unlimited data points since the data is self hosted, then when the user wants to get info like locations via an IP because they need to hit our API we could give them ~100/day and then allow them to unlock all locations for all visitors if they upgrade.
We could also offer a handful of other pro features like:
Session Replay - There are a number of open source self-hosted solutions like https://openreplay.com/ and https://www.rrweb.io/
Events - We could also make things like button clicks, form submissions, and other events a premium feature.
This way users can still use the package for free and gain Analytics counts, views, and more. Then when they want more they can upgrade.
Totally open to discuss more 👍

Totally. Let's cut the "X data points" thing. Unlimited it is!
Here's my pitch for a feature set...totally open to changes, just where my head is at.
Feature set
Free
- unlimited data points
- one dashboard report
- a basic set of cards ("referrals", "pages", "devices", etc.)
- one domain
- password-protected dashboard sharing
$199 pro
- Install on as many domains as you want
- Signal.fire custom event tracking
- Real-time metrics
- More cards for richer reports
- Email reports
$499 agency
- Multiple domains in one install
- Clickhouse integration
- White label
- User management
- CRM mode with reports on individual user activity


When is the next release planned?

When will the next version be updated? I find that there is now a big difference between the stable version and the main branch. The main branch has fixed some stable releases and is still updating, so I'm worried that when I'm coding from the last release, a new version will be released and I won't be able to fit in well.

We don't have scheduled releases, but we will likely release another Pub version very soon, before we start breaking things for #748
As for your comment about main vs stable - there shouldn't be any functional difference between main and stable. We cherry pick every commit that we can from main to stable. What differences are you seeing between those two branches?

We don't have scheduled releases, but we will likely release another Pub version very soon, before we start breaking things for #748
As for your comment about main vs stable - there shouldn't be any functional difference between main and stable. We cherry pick every commit that we can from main to stable. What differences are you seeing between those two branches?

Sorry, I'm talking about the last release of super_editor, which is somewhat different from the current main branch.

Ok. I expect us to release another version, probably within the next couple of weeks.


Support JSON stats output

Operating System: macOS 10.13.4
Node Version: 10.0.0
NPM Version: 6.0.0
webpack Version: 4.8.1
webpack-command Version: 0.2.0

This issue is for a:

[ ] bug
[x] feature request
[ ] modification request

Code
CLI Command
  $ webpack --json

webpack.config.js
n/a
Expected Behavior
webpack-cli (and formerly the bundled webpack CLI) has a --json arg which causes the stats to be printed out as JSON. This is extremely useful for piping into files which can then be uploaded to web-based bundle analysis tools.
It would be great if webpack-command could support this flag or something equivalent -- perhaps through a reporter. Since webpack-command is already working with the JSON stats, I assume this would be a low-overhead feature to support.
I'm about to take a vacation but I might be able to get a PR out before I leave if this sounds reasonable to you.
Actual Behavior
There is currently no way to get the build stats as JSON.
New Feature Use Case
See expected behavior above.

Cool. I will PR a JSON reporter either before or after my vacation.
These lines will be a problem because there is no way to disable them, and it's important that this reporter print only a single valid JSON object. Do you mind if I change the internals to allow the reporter to disable all other output, or is there a better option?

You can actually pull some trickery with that log object. In the constructor for your reporter:
this.log = weblog({ name: 'webpack', id: 'webpack-command' });
this.setLogLevel = log.logLevel;
log.logLevel = 'silent';

And then in the render method for your reporter, restore the level:
this.log.logLevel = this.setLogLevel;

Though I'm not sure if that's needed, especially if your reporter is only intended to report JSON and nothing more. Something else to consider: writing the JSON output to stderr so you can still allow the logging as per usual, but then could redirect stderr to a file or for examination by another process. That'd be the best of both worlds.

Something else to consider: writing the JSON output to stderr so you can still allow the logging as per usual, but then could redirect stderr to a file or for examination by another process. That'd be the best of both worlds.

Could we instead do the opposite? If I'm not mistaken, it's common practice to log informational output to stderr if stdout will be used for e.g. piping.
Here's one nice blog post summarizing what I've understood stderr and stdout should be used for: https://www.jstorimer.com/blogs/workingwithcode/7766119-when-to-use-stderr-instead-of-stdout

@valscion welcome to the nuances of writing tooling in the webpack ecosystem: no matter how many considerations you make for how people are going to work with a thing, someone will always have another method they're asking to account for 😄
There hasn't been a huge demand for this yet, so I really have no preference for how this functions. No one has stepped up to provide this in a PR yet.

I hope my comment wasn't coming through as assertative. Didn't mean to bring bad feelings. (I feel the need to apologise as your reply comes off a bit snarky, and I worry it's my fault)

Tangent: I believe people anymore are way too worried about the mere possibility of offending someone. My reply contained no snark, it was straight truth. And it even had a smiley face. If your reply offended anyone, they can go jump in a lake, because it was perfectly fine and properly illustrated the nuances I mentioned.


Directory name is invalid when saving certificate

I've been having this problem since I upgraded to the latest release, and it seems to happen now to any release even if I clear all files from both the LetsEncrypt directory and from the directory in %AppData%\Roaming.
Upon trying to create a certificate, all works as is should up until the point where it tries to save and apply the new certificate. I'll find the -crt.der in my AppData directory, but IIS doesn't see a usable certificate, and the LetsEncrypt console reads:
Requesting Certificate
  Request Status: Created
  Saving Certificate to C:\Users\<myusername>\AppData\Roaming\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\example.mydomain.com-crt.der
System.IO.IOException: The directory name is invalid.

    at System.IO.__Error.WinIOError(Int32 errorCode, String maybefullPath)
    at System.IO.__Error.WinIOError()
    at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
    at LetsEncrypt.ACME.Simple.Program.GetIssuerCertificate(CertificateRequest certificate, CertificateProvider cp)
    at LetsEncrypt.ACME.Simple.Program.GetCertificate(Target binding)
    at LetsEncrypt.ACME.Simple.Program.Auto(Target binding)
    at LetsEncrypt.ACME.Simple.Plugin.Auto(Target target)
    at LetsEncrypt.ACME.Simple.Program.Main(String[] args)
Press enter to continue.

I tried running as Administrator assuming it was a permission issue, but that hasn't solved anything. (Plus the file is showing up in the directory, just not in IIS)

I don't think it will show anything else, but could you enable Debug Logging and see if you see anything else in the Event Logs?

It doesn't provide any new information, just sort of repeats itself. It's still just claiming the save location is in an invalid directory despite the fact that I can see the file there.

#146 Might help with this. Otherwise i'm not sure what's causing it.

v2 will feature a configurable path for the output directory (see https://github.com/Lone-Coder/letsencrypt-win-simple/pull/394).
Since this has been inactive for a few months I'll close it now. Please feel free to re-open this if you have steps to reproduce.