Test in web chat giving "There was an error sending this message to your bot: HTTP status code GatewayTimeout"

After following the instructions and publishing the bot to Azure I get an error when testing it in the Web chat:
"There was an error sending this message to your bot: HTTP status code GatewayTimeout".
It would be great to have some common issues in the end of the tutorial to fix these types of errors.
If you can provide any insight how I can fix it I'd really appreciate it.
I have tried StackOverflow but have not found anyone that has provided an answer to solve this.
The Bot worked locally through the emulator without any issues. It's only after publishing it to Azure that it gives errors.

@CharLind87 - the troubleshooting section Bot does not work in Web Chat might help you track down the issue. I'll schedule some time to add strategic links from the how to articles to the troubleshooting articles.
If this information doesn't help, I can see if I can get someone to help you.

Thank you, I looked over the link you provided. And when I paste in my messaging endpoint in my browser I get "The page isn't working wring now. HTTP Error 405" indicating that the bot is reachable and able to respond to messages. It's the Echobot that I have deployed and in Test in Web Chat it doesn't initiate the same message it does when I tried on local machine. And when I write any input it sends but the bot doesn't echo it like it should.
Any ideas?

Without diving into your bot's code, I don't. I'll try to get an engineer to reach out to you.

The steps I have taken are from these two tutorials:
Deploy with Bot Framework Emulator: https://docs.microsoft.com/en-us/azure/bot-service/bot-service-quickstart-create-bot?view=azure-bot-service-4.0&tabs=csharp%2Cvs
Deploy on Azure: https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli?view=azure-bot-service-4.0&tabs=csharp
And the code is from this: https://marketplace.visualstudio.com/items?itemName=BotBuilder.botbuilderv4
I used the EchoBot, which is suggested as a first bot to test with.

Hi @CharLind87,
I'm a Bot Support Engineer, and I will try to help you out with this.
First of all, here's a list of common errors or mistakes that can be made when trying to deploy a sample bot to Azure. Let's see if any of them might apply to your situation before we go further.

It seems straightforward, but double-check the syntax of each command to verify that you are entering them correctly. If you copied and pasted the commands, did you miss a letter?
Did you fill in all the required fields correctly? No typos?
Ensure that your appId and password are correct at all stages
Which deployment path did you choose? A new or existing resource group? Did you make sure you followed the correct steps? It's quite easy to accidentally copy the wrong Azure command
Did you make sure to put your appId and password in your bot's code?
Did you make sure you built in Release Mode if using Visual Studio?
Did you remember to run the command that generated the .deployment file in your project directory?
Did you zip up the correct directory?
When you selected a name, region, resource group, or anything else for your deployments, were you consistent across all commands?

If any of these are true, it might be the cause of your issues.

I didn't alter the code from the one in the link. And it runs perfectly locally. It's only after following the tutorial and deploying it to Azure that I get an error.
App ID and password are correct and in the appsettings.json
I made sure to build it in Release mode according to tutorial.
.deployment is generated according to tutorial.
I created from a pre-made resource group and followed the script provided in the tutorial. Everything deployed as expected.
I did zip the directory according to tutorial, from where the folder csproj-file is.
I selected West Europe and can see that that is reflected in my Azure portal. I believe it's only one command in the tutorial that requires region.
Everything seemingly deployed as it should. The only issue is that when I test the bot in web chat and send a message, and it's suppose to echo my message, it doesn't. And when I go into channel it gives the error "There was an error sending this message to your bot: HTTP status code GatewayTimeout". And I can't figure out why it would throw this error?
I saw in some forums that TLS/SSL settings to HTTPS Only would help, but it has not.

Ok, let's try using the steps that would create the bot with a new resource group. This way we can try to eliminate any potential variables caused by having an existing resource group. The following points are the steps needed (I assume you're already signed in to Azure in the CLI). Just fill in the parameters as needed. (I have pulled these from the same tutorial document. If you wish to reuse the name of a resource group, please remember to delete it first.

Run az ad app create --display-name "<bot app name>" --password "<password>" --available-to-other-tenants
Make a note of the appId and password
Run az deployment sub create --template-file "<file path to>\template-with-new-rg.json" --location <azure region> --parameters appId="<appId>" appSecret="<password>" botId="<bot name>" botSku=<pricing tier> newAppServicePlanName="<app service plan name" newWebAppName="<bot web app name>" groupName="<bot resource group name>" groupLocation="<azure region>" newAppServicePlanLocation="<azure region>" --name "<bot app service name>"
Wait until that finishes
In the meantime, run the Build in VS in Release mode, and then navigate to the .csproj directory
Run az bot prepare-deploy --lang Csharp --code-dir "." --proj-file-path "<bot project name>.csproj"
Now zip up everything in this directory
Once the az deployment sub create command has completed, run az webapp deployment source config-zip --resource-group "<bot resource group name>" --name "<bot name>" --src "<file path to your bot name>.zip"
Wait till that finishes, then wait some more time for your bot to respond to web chat testing

If this works, there may be something wrong with that resource group. Another possibility is that your region might not be fully supported. We'll take a look at each potential situation in turn. Give this a try first and see what happens.

No, and I have no other issues accessing the Azure or M365 portals for anything else.
I get "Deployment endpoint responded with status code 202" when I ran the Azure CLI commands.
And when I paste the messaging endpoint into a web browser I get HTTP error 405 which according to the Docs page below indicates that "If the endpoint returns HTTP Error 404 or 405, that means the bot is reachable and the bot is able to respond to messages."
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-troubleshoot-bot-configuration?view=azure-bot-service-4.0#:~:text=If the endpoint returns HTTP Error 404 or,or fails with an HTTP 5xx error articles.

Just because a bot is reachable, doesn't necessarily mean it's working correctly. Could you potentially provide me with an exact copy of the bot you are using, sans any keys or passwords? I'd like to test it on my end and see if I can figure out what's going wrong. You can send the bot to my work email address (on my profile), and please mention this issue in your email.

You can find the code in previous comment I made :)
It's not my own code. It is what is suggested to use when following the Bot Framework Emulator tutorial.
It's called EchoBot, which essentially just is suppose to echo whatever you type in the chat. Nothing advanced :)

Are you 100% sure that you filled in your appId and Password correctly in the bot's code and in the commands?
Just to be sure, I tried to reproduce your issue one more time using the following steps:

Using the Azure CLI, create a new app.
Using Visual Studio, create a clean new Echo Bot using the template
Add my appId and Password to the appsettings.json file, then save, clean, build, and zip up the bot
Create the deployment in Azure CLI in a new resource group in the West Europe region
Upload the zipped bot to Azure

After waiting a few minutes, I attempted to test in Web Chat and received an echo from the bot, as you can see below.

Closing due to inactivity


PLElog.py running problem(numpy version)

Hello, Dr. Yang. I mentioned the problem of library conflicts in # issue19. You removed the required version of numpy. I tested it today and found that it entered an endless cycle.
Numpy=1.21.2 is compatible with mkl_fft=1.3.1 and mkl_random=1.2.2, provided that numpy, mkl_fft and mkl_random cannot be installed with requirement.txt. When I tested it, I installed numpy=1.21.2 first, and then installed mkl_fft and mkl_random manually, thus solving this problem.
When I thought everything ok, I found that PLElog still can not run, the program gave me an error: ValueError: numpy.ndarray size changed, may indicate binary incompatibility.
Expected 96 from C header, got 88 from PyObject .
I checked this problem because the numpy version is too low, and when you upgrade numpy, you will get an error: RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf.
I found the answer to this question in the rest of the github code: lower the version of numpy, https://github.com/tensorflow/tensorflow/issues/57106       he reduced the numpy version from 1.22.4 to 1.21.
in this situation， I don't know how to run the code, and I hope you take the time to look at this problem.thanks a lot.
(1)problem will happen  when i changed numpy version from 1.21.2  to 1.22.4 :
Traceback (most recent call last):
File "F:\code\PLELog\approaches\PLELog.py", line 9, in
from preprocessing.AutoLabeling import Probabilistic_Labeling
File "F:\code\PLELog\preprocessing\AutoLabeling.py", line 3, in
from models.clustering import Solitary_HDBSCAN
File "F:\code\PLELog\models\clustering.py", line 7, in
from hdbscan import HDBSCAN as dbscan
File "E:\app\anaconda\envs\PLElog_py\lib\site-packages\hdbscan_init_.py", line 1, in
from .hdbscan_ import HDBSCAN, hdbscan
File "E:\app\anaconda\envs\PLElog_py\lib\site-packages\hdbscan\hdbscan_.py", line 21, in
from ._hdbscan_linkage import (single_linkage,
File "hdbscan/_hdbscan_linkage.pyx", line 1, in init hdbscan._hdbscan_linkage
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
(2)problem will happen  when i changed numpy version from 1.22.4 to 1.21.2:
2023-05-18 23:45:45,332 - Statistics_Template_Encoder - SESSION_fbd73c53bc62b07b79da9e657917a461 - INFO: Construct Statistics Template Encoder success, current working directory: F:\code\PLELog\approaches, logs will be written in F:\code\PLELog\logs
2023-05-18 23:45:45,354 - StatisticsRepresentation. - SESSION_fbd73c53bc62b07b79da9e657917a461 - INFO: Construct StatisticsLogger success, current working directory: F:\code\PLELog\approaches, logs will be written in F:\code\PLELog\logs
Traceback (most recent call last):
File "init.pxd", line 882, in numpy.import_array
RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf . Check the section C-API incompatibility at the Troubleshooting ImportError section at https://numpy.org/devdocs/user/troubleshooting-importerror.html#c-api-incompatibility for indications on how to solve this problem .
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "F:\code\PLELog\approaches\PLELog.py", line 9, in
from preprocessing.AutoLabeling import Probabilistic_Labeling
File "F:\code\PLELog\preprocessing\AutoLabeling.py", line 3, in
from models.clustering import Solitary_HDBSCAN
File "F:\code\PLELog\models\clustering.py", line 7, in
from hdbscan import HDBSCAN as dbscan
File "E:\app\anaconda\envs\PLElog_py\lib\site-packages\hdbscan_init_.py", line 1, in
from .hdbscan_ import HDBSCAN, hdbscan
File "E:\app\anaconda\envs\PLElog_py\lib\site-packages\hdbscan\hdbscan_.py", line 21, in
from ._hdbscan_linkage import (single_linkage,
File "hdbscan/_hdbscan_linkage.pyx", line 1, in init hdbscan._hdbscan_linkage
File "hdbscan/dist_metrics.pyx", line 13, in init hdbscan.dist_metrics
File "init.pxd", line 884, in numpy.import_array
ImportError: numpy.core.multiarray failed to import
Process finished with exit code 1

thanks a lot, docker image is a good choice, I will continue to try as you suggest

I solved  this problem  by  conda and pip command. if you are experiencing the same problem as me, maybe try this method instead of installing through the requirement .txt


Sync with Digital-MOB's fork + bugfix

Linked to https://github.com/protofire/filecoin-CID-checker/issues/84
Linked to https://github.com/protofire/filecoin-CID-checker/issues/81
Includes

Based on latest Digital-MOB's master branch.
Bugfix #81

The test/build action failed but I'm merging this anyway because it's the version that is already running in prod. Besides it blocks https://github.com/protofire/filecoin-CID-checker/issues/86


Para goomba pattern is not accurate

Para goombas are supposed to
-follow the player
-do a big jump after the third(?) jump
attempts were made according to this https://stabyourself.fandom.com/wiki/Custom_Enemy_Properties#Movement_2 but I couldn't get it to work, might need to make the paragoomba a .lua enemy instead of a .json enemy, unsure

Since there can only be one "transformtrigger", can't make it so it both turns into a normal goomba when stomped AND have it switch on the third jump (and so follow the player when that happens)
wont fix unless we code the enemy as a .lua or something, very minor anyway


#608 Revert to defaulting to stylish select

Cool, looks fine to me - I see the main change is the support for specifying the render type, and then rest is a revert.
And I understand @doolse is going to update the auto tests and check locally, then once that is working a merge will be done.


Print diff between expected and actual messages in e2e tests

Description
The return type of function MessageAssertion is updated from bool to (bool, int, string). Other corresponding changes are made base on this change.

The returned int value indicates the number of matched blocks between expect message and actual got message.
The returned string value is the diff between expect message and actual got message.

Related issue
Resolves: #772

One example of failed e2e test case result:


Recognize arbitrary length string

Hi,
I have followed the steps and successfully trained a machine to recognize characters from 0 to 9,
Currently it is able to recognize images with a single character, but unable to recognize arbitrary length of characters,
Please suggest me a way to make the OCR recognize arbitrary length of characters and properly arrange them as per the image

Hi,
Aside from training character recognition, you also need to train the attention part of the model. That means that if it hasn't ever seen multi-character strings before, it will not be able to "understand" them.
You should train the model on multi-character images instead of single characters. Ideally, your training images should be close to what you need the model to recognize, or the training set should be vast (like Synth90k).


Unable to select xx:01 times on station announcements

The drop down option gives 00 - hundred, 00 - hundred-hours, 02, 03, 04, [...], 58, 59

This prevents being able to announce the "Oh one oh one one service from platform one"

Hah, yeah that's definitely an issue!


[joss] dfs_edges() invalid result on multigraphs

dfs_edges() does not seem to support multigraphs properly:
g = rx.PyGraph()
g.extend_from_edge_list([(0,0), (0,1), (1,2), (1,2), (2,3)])

print(rx.dfs_edges(g, 0))

EdgeList[(0, 1), (1, 2), (2, 3)]

I would expect every edge to be traversed, since this function specifically returns edges (not merely nodes). One possible correct result would be (0,0), (0,1), (1,2), (2,3), (1,2).

This is related to #512.

dfs_edges returns only edges that are part of the DFS tree. Documentation should be more clear on this.

I see, so this is basically a spanning tree function, comparable to minimum_spanning_edges(). In that case the behaviour is correct, but the docs should really be updated. Now they state:

Get edge list in depth first order

which I assumed referred to the edge list of the graph.


feat: bump kcl lib to v0.7.0-alpha.1 and impl path selectors for the run API.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

feat: bump kcl lib to v0.7.0-alpha.1 and impl path selectors for the run API.

2. What is the scope of this PR (e.g. component or file name):

pkg/kcl/opt.go
pkg/spec/gpyrpc/gpyrpc.proto
scripts/kclvm.go

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 9 (22.22%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 65.891%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/kcl/opt.go
1
8
12.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
2635

Relevant Lines:
3999

💛  - Coveralls


Echidna doesn't like commas after the document status.

See https://twitter.com/robinberjon/status/591543288336932864.

Huzzah, w3c/specberus#188 fixed it. :)


ACME 400 ISSUE

Hi there,
I have setup new domain(mymicro.bio) and pointed to a linode server.
i'm trying to use 0365 phishlet.
I have added A and NS records in Linode (cloud platform similar to digital ocean) as guided.
However, when i launch phishlet 0365, I get the below error.

I got the domain from namecheap and here is the dns settings (Nam server settings) :

NS records settings in Linode:

Let me know if anyone can help me out with this issue.
Regards!

Well, it just worked now :)


Test: add an AsyncRuntime test suite

What does this PR do
Implements the test suite for AsyncRuntime and tests the built-in TokioRuntime impl with it.
Checklist

[ ] Updated guide with pertinent info (may not always apply).
I think we need to mention this in getting-started.md but I am not sure about where to add it.
[ ] Squash down commits to one or two logical commits which clearly describe the work you've done.
[x] Unittest is a friend:)

This change is

Well, I will handle those CI failures, they are easy to deal with, I simply need to correct the import path.

but we should strive to minimize disruption to user applications by maintaining the existing paths to these functions wherever possible.

AH, right, I forgot they're public APIs, will try to maintaining their current import path.

but we should strive to minimize disruption to user applications by maintaining the existing paths to these functions wherever possible.

Ah, right, I forgot they're public APIs, will try to maintaining their current import path.

@schreter, hi, would like to have your review as well, could you please take a look:)

openraft/src/testing/runtime/mod.rs line 227 at r3 (raw file):
Previously, schreter wrote…
It would be good to take this future also before send() to verify that it indeed changes state afterwards (in a second test/next step of the test). For that, you can do something like this:
let fut = rx.changed();
let fut = Pin::new(&mut fut);
assert!(poll_in_place(fut), matches!(Poll::Pending));
tx.send(...);
assert!(poll_in_place(fut), matches!(Poll::Ready(...)));

There is some support for such feats in futures crate. For example, you can do this:
pub fn poll_in_place<F: Future>(fut: Pin<&mut F>) -> Poll<F::Output> {
    let waker = futures::task::noop_waker();
    let mut cx = Context::from_waker(&waker);
    fut.poll(&mut cx)
}

You can also use it elsewhere to fine-grained check when the future becomes ready, especially for sync primitives.

done, see this commit: https://github.com/datafuselabs/openraft/pull/1219/commits/46ffc3ef0112aa37b0fd612bb6922b85ad753c14

Commits squashed.

Let me rebase my branch to handle the conflicts:)


Improve shape function of tf.image.draw_bounding_boxes

The tf.image.draw_bounding_boxes requires boxes to be 3-D shape though there was no check on shape function.
This fix improves the shape function by restricting the boxes to 3-D.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Thanks @rmlarsen for the review. The PR has been updated. Please take a look.

Thanks!


VSTS modal dialog close event

Hi,
I am using microsoft VSTS modal dialog and I want a confirmation message when modal dialog is closed from 'x' (closed button of modal dialog), I get close event which fired after event dialog is closed.
I want an event before closing the dialog. How can I do that?
here is the code:
VSS.getService(VSS.ServiceIds.Dialog).then(function(dialogService)
{
       var contributionId = //id
       var dialogOptions = { title: "ABC", close: onDialogCloseByCrossButtonClick };
       dialogService.openDialog(contributionId, dialogOptions).then(
               function (dialog) {
                    // do something
        });
}

like its appearing in TFS WorkItem window.

This repo deals only with the Azure Devops Task extensions that are built and published in marketplace.visualstudio.com.
I am closing this issue, since this does not seem related to the tasks that are present in this repo.


Channel "Apply" button changed to "ON"

We may also want multiple channels to be on simultaneously and then those "ON" would need to have their Control Bar highlighted.

I'm not sure if the LED hardware supports this. Lets discuss.

It would just be the label in the button
C

On Apr 7, 2021, at 3:27 PM, Anna Hickerson @.***> wrote:

I'm not sure if the LED hardware supports this. Lets discuss.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I can change the label, but the hardware does not support turning on more than 1 LED at a time. I can send it commands to turn on  an LED, then another, and the first automatically turns off.

Moving label change request to another thread.

Whoops, forgot about that
From: Anna Hickerson @.***
Sent: Friday, April 9, 2021 11:29 AM
To: EtalumaSupport/LumaViewPro @.>
Cc: Etaluma Support<EMAIL_ADDRESS>Author <
@.>
Subject: Re: [EtalumaSupport/LumaViewPro] Channel "Apply" button changed
to "ON" (#6)
I can change the label, but the hardware does not support turning on more
than 1 LED at a time. I can send it commands to turn on an LED, then
another, and the first automatically turns off.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EtalumaSupport/LumaViewPro/issues/6#issuecomment-816876601,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARWSEZOITFSYWR64ZHPF6CDTH5BQHANCNFSM42FBQVUQ
.[image: Image removed by sender.]


image_demo output difference (CUDA_VISIBLE_DEVICES=1 <-> model.to('cuda:1'))

Hi
I tried to inference the segmentation model(mask2former_beit_adapter_large_896_80k_cityscapes_ss) and got some weird point.
(1)
Run image_demo.py as
CUDA_VISIBLE_DEVICES=1 python image_demo.py
configs/cityscapes/mask2former_beit_adapter_large_896_80k_cityscapes_ss.py
released/mask2former_beit_adapter_large_896_80k_cityscapes.pth.tar
data/sample.png
(2)
Run image_demo.py as
python image_demo.py
configs/cityscapes/mask2former_beit_adapter_large_896_80k_cityscapes_ss.py
released/mask2former_beit_adapter_large_896_80k_cityscapes.pth.tar
data/sample.png
--device cuda:1
There are 2 kinds of command, commands mean inference with cuda(index: 1), but outputs are different.
Here is (1) output

Here is (2) output

Please let me know the reason If you know what the problem is.
Thank you

It's really weird, and I don't know why at the moment.
Usually, I use the first command to inference a single image.

Hi
I tried to inference the segmentation model(mask2former_beit_adapter_large_896_80k_cityscapes_ss) and got some weird point.
(1) Run image_demo.py as CUDA_VISIBLE_DEVICES=1 python image_demo.py configs/cityscapes/mask2former_beit_adapter_large_896_80k_cityscapes_ss.py released/mask2former_beit_adapter_large_896_80k_cityscapes.pth.tar data/sample.png
(2) Run image_demo.py as python image_demo.py configs/cityscapes/mask2former_beit_adapter_large_896_80k_cityscapes_ss.py released/mask2former_beit_adapter_large_896_80k_cityscapes.pth.tar data/sample.png --device cuda:1
There are 2 kinds of command, commands mean inference with cuda(index: 1), but outputs are different.
Here is (1) output
Here is (2) output
Please let me know the reason If you know what the problem is.
Thank you

@PigBroA
May I ask if your Python version number is 3.7.11 and the torch version number is 1.9.0？ Is the mmcv version number 1.4.2?
Thank you!

@InterstellarFang
I can't remember that exactly. but, I think I used higher versions what you mention. Thanks
(maybe, python was 3.8.15, torch was 1.9.1, mmcv was 1.7.0, but I can't make sure that)


Update links in web application

Can we please make the following updates to various links in the web application?
Homepage

[x] Change the label "Download all of our datasets" to "Download all of our open datasets" and link to /downloads

Footer

[x] Link "Terms of use" to https://platform-docs.opentargets.org/terms-of-use
[x] Link "Documentation" to https://platform-docs.opentargets.org

Navigation menu

[x] Link "Documentation" to https://platform-docs.opentargets.org/getting-started
[x] Link "Data downloads" to /downloads

Ticket closed as work completed and reviewed in opentargets/platform-app#350 and merged into main


Milestone Link / Buttons visible while using external issue tracker or issue tracker is turned off

Gitea version (or commit ref): Gitea Version: 1.14.0+dev-290-gb1cf7f4df
Git version: See try.gitea.io
Operating system:
See try.gitea.io

package -->

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[X] Yes (https://try.gitea.io/khmtestorga/testrepo/pulls/5)
[ ] No

Description
First I have configured a repository to use internal issue tracker ... everything fine.

Now I can look into pull request and see of course thing like Issues 1 entry, the entry Milestone on the right sight bar ... just fine.

But if I change the configuration of the repository and disable Enable Repository Issue Tracker like the following:

What I can now see that after disabling the issue tracker I keep seeing the button Milestones in the upper left and in the side bar as well...

This looks like a bug in the UI.
One point where I'm not sure how to handle that is the display of labels? From my understanding labels are only related to issues? If yes then they have to removed from displaying as well otherwise not.
I would like to take the opportunity to solve this issue if this is Ok?

If the PR will be accepted does it make sense to back port this to 1.13.0?


Exception Handling - Chain over Chain

I'm trying to create an error policy where I have a Chain inside a Chain of policies, but the whole chain is not working as expected.
Looks that Silverback is not ready to work with chained Chains.
To solve it I developed my own "ErrorPolicyChain" to wrap it.
 public class NonStoppingErrorPolicyChain : ErrorPolicyChain
 {
        private readonly ILogger<ErrorPolicyChain> _logger;
        private readonly IEnumerable<ErrorPolicyBase> _policies;
        private readonly MessageLogger _messageLogger;

        public NonStoppingErrorPolicyChain(
            IServiceProvider serviceProvider,
            ILogger<ErrorPolicyChain> logger,
            MessageLogger messageLogger,
            params ErrorPolicyBase[] policies)
            : this(policies.AsEnumerable<ErrorPolicyBase>(), serviceProvider, logger, messageLogger)
        {
            _logger = logger ?? throw new ArgumentNullException(nameof(logger));
            _policies = policies ?? throw new ArgumentNullException(nameof(policies));
            _messageLogger = messageLogger ?? throw new ArgumentNullException(nameof(messageLogger));
        }

        public NonStoppingErrorPolicyChain(
            IEnumerable<ErrorPolicyBase> policies,
            IServiceProvider serviceProvider,
            ILogger<ErrorPolicyChain> logger,
            MessageLogger messageLogger)
            : base(policies, serviceProvider, logger, messageLogger)
        {
            _logger = logger ?? throw new ArgumentNullException(nameof(logger));
            _policies = policies ?? throw new ArgumentNullException(nameof(policies));
            _messageLogger = messageLogger ?? throw new ArgumentNullException(nameof(messageLogger));

            if (this._policies.Any(p => p == null))
                throw new ArgumentNullException(nameof(policies), "One or more policies in the chain have a null value.");
        }

        protected override ErrorAction ApplyPolicy(
            IReadOnlyCollection<IRawInboundEnvelope> envelopes,
            Exception exception)
        {
            var ret = ApplyPolicyNonStop(envelopes, exception);

            if (ret != null)
            {
                return ret.Value;
            }

            _messageLogger.LogDebug(this._logger, "All policies have been applied but the message(s) couldn't be successfully processed. The consumer will be stopped.", envelopes);

            return ErrorAction.StopConsuming;
        }

        private ErrorAction? ApplyPolicyNonStop(
            IReadOnlyCollection<IRawInboundEnvelope> envelopes,
            Exception exception)
        {
            foreach (ErrorPolicyBase policy in _policies)
            {
                if (policy is NonStoppingErrorPolicyChain subChain)
                {
                    var ret = subChain.ApplyPolicyNonStop(envelopes, exception);

                    if (ret != null)
                    {
                        return ret;
                    }
                }
                else if (policy is ErrorPolicyChain)
                {
                    throw new InvalidOperationException("Native chains are error prone and therefore not supported by Common.Silverback, please switch to `policy.NonStoppingChain(...)`.");
                }
                else if (policy.CanHandle(envelopes, exception))
                {
                    return policy.HandleError(envelopes, exception);
                }
            }

            return null;
        }
    }

It worked perfectly in my case.

Why would you want a chain of chains instead of a simple flat one?
What's the problem you are trying to solve?

Closed because of no activity.


Documentation not rendering well

https://click.palletsprojects.com/en/8.1.x/api/#click_group doesn't render well on web browser.
Tried Chrome and Safari on Mac OS X, Chrome and Firefox on Ubuntu 20.04

Duplicate on the theme repo

What does that mean?


More comprehensive unit tests

Built on top of #293.

Rebased onto current master, resolved a couple merge conflicts.
Fixed compatibility of the unit tests with various device/iOS version combinations.
Fix #260

Currently tests under iOS 7 are failing because reference images for testButtonWithGradient and testSegmentedControlColorsRenderCorrectly are missing.
@PabloLerma said he would help out with these tomorrow, as I currently can't get the iOS 7 Simulator to run on my machine. See discussion on #284.

@PabloLerma The images you provided work with iOS 7.1, but not with 7.0.3. Can you please provide those images for 7.0.3? That should get the Travis CI check to pass and I will be able to merge.

I don't have a 7.0.3 simulator :(
At this time we only support >= 8.0 so having a 7.1 was luck because I didn't delete XCode 6.4. I will ask my teammates anyway.
Sidenote: With 9.1 out there, supporting 7.0.3 is not too much? :P

Thank you. I would like to forgo iOS 7 support as well. But since we are maintaining a library I feel that we should strive to support as many iOS versions within reason. If this was a standalone app that would be a different story but considering many apps utilize our code it is entirely possible that the popular apps that utilize our code still have thousands of iOS 7 users. I think it would be shameful if we couldn't support them, especially if we didn't have to go far out of our way to do so.

@PabloLerma @Stunner I'd drop this single unit test on <7.1 though.
Chances are, that if it works on iOS 7.1, 8.x and 9.x, it will work as expected on 7.0.
These snapshot tests are only a form of integration test anyways, that double checks the unit test for the respective renderer classes.

@timbodeit Fair enough.

:+1:

Anyway for the record, it would be good if someone supporting <7.1 could provide us such images :smile:

Well theoretically, we could tweak the travis build script to send the images back to us, but that seemed to be too much work for a test that essentially just compares two screenshots.


Does this still work?

Hi! I know this is a fork from https://bitbucket.org/xoseperez/fauxmoesp/src/master/ .. but Im running into an issue, and just wondering if this still works. I had it all working a year ago, but with a fresh install of sketch, esp2866, fauxmo Alexa never recognizes it.
Thought if you were still active, you may know - thanks

Sorry, haven't used this in a while. I'd check with the upstream, I just had this for access through github.


'Access denied' to jdbc:mariadb socket connection in DBeaver.  OK from shell.

I've got MariaDB 10.2.12 installed on linux.
It's set up for socket access,
	ls -al /var/run/mariadb/mariadb.sock
		srwxrwxrwx 1 mysql mysql 0 Jan  6 12:19 /var/run/mariadb/mariadb.sock=

Via shell, socket connection works perfectly,
	mysql -h localhost -u root -D mysql
		Reading table information for completion of table and column names
		You can turn off this feature to get a quicker startup with -A

		Welcome to the MariaDB monitor.  Commands end with ; or \g.
		Your MariaDB connection id is 1371
		Server version: 10.2.12-MariaDB-log Source distribution

		Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.

		Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

		MariaDB [mysql]>

I'm trying to get a socket connection to it using DBeaver 4.3.2 GUI.
I've got JDK 1.8 installed
	java -version
		OpenJDK Runtime Environment (IcedTea 3.6.0) (build 1.8.0_151-b12 suse-281.2-x86_64)
		OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

I grabbed latest MariaDB Connector-j,
	ls -al /root/.dbeaver-drivers/maven/maven-central/org.mariadb.jdbc/mariadb-java-client-2.2.1.jar
		-rw-r--r-- 1 root root 553K Dec 22 03:48 /root/.dbeaver-drivers/maven/maven-central/org.mariadb.jdbc/mariadb-java-client-2.2.1.jar

In Dbeaver, I have a DB connection defined:
	@Database connection settings ->
		Server Host: localhost
		Port: 3306
		Database: mysql
		User name: root
		Password: xxxxxxxx

		Local Client: /usr/local/mariadb
		Driver Name: MariaDB

	@Database connection settings -> Edit Driver Settings
		Driver Name: MariaDB Driver       Type: MySQL
		ClassName: org.mariadb.jdbc.Driver
		URL Template: jdbc:mariadb://localhost:3306/mysql?socket=/var/run/mariadb/mariadb.sock
		DefaultPort: 3306       [ ] Embedded

		Libraries
			/root/.dbeaver-drivers/maven/maven-central/org.mariadb.jdbc/mariadb-java-client-2.2.1.jar

But when I try to access the connection, I just get:
	"Could not connect: Access denied for user 'root'@'localhost'"

What am I missing in my DBeaver config?

its 2020, I'm on linux mint, dbeaver community version 7 and this bullshit is still unresolved even by trying the stuff above... why the frickin hell do I have to go through debugging this stuff right after installing mariadb???

I second that @catalin560

@ahenry2 using google cloud sql locally the only option is a socket. I was previously using valentina studio which handles this use case and its restricting me from switching over to dbeaver. I tried the options above but closest I got was authentication error root no password.

step 1: find out mariadb Unix socket file

strategy 1: via filesystem: grep -rin socket /etc/mariadb /etc/mysql
strategy 2: via SQL query: mysql -e "show variables like 'socket';"
in my case it is socket=/run/mysqld/mysqld.sock

step 2: use a fresh/untinkered installation of DBeaver, Version <IP_ADDRESS>309040911

select "New Database Connection". a pop-up "Connect to a database. Select your database" appears.

select "MariaDB", click "Next >". the pop-up becomes "Connect to a database. Connection Settings. MariaDB connection settings".
click button "Driver Settings" (lower right). a pop-up "Edit Driver 'MariaDB'" appears.

select "Libraries" pane. select "org.mariadb.jdbc:mariadb-java-client:RELEASE [x.y.z]". click on "Download/Update". a pop-up "Driver settings. Download driver files. Download MariaDB driver files" appears.

under "Files required by driver", within row "org.mariadb.jdbc:mariadb-java-client:RELEASE [x.y.z]", click on the "Version" cell. a drop-down appears.
select the latest version (in my case, "3.2.0"). click "Download". The "Driver settings. ..." pop-up closes.

back in the "Edit Driver 'MariaDB'" pop-up, click "OK". This pop-up closes.

back in the "Connect to a database. Connection Settings. MariaDB connection settings" pop-up, on the "Main" tab, under "Server":

for "Connect by:", select "URL"
for "URL.", provide "jdbc:mariadb://localhost:3306/?localSocket=/run/mysqld/mysqld.sock" - adapt "localSocket=..." to the file path identified during the previous "step 1".

configure "Username:" as appropriate
click "Test Connection ..." (lower left). if everything goes well, a pop-up "Connection test" with a successful "Connected ..." information should appear. click "OK" to close this pop-up.
back in the "Connect to a database. Connection Settings. MariaDB connection settings" pop-up, click "OK" to finish the connection setup.

Finally, still had 23.0.2 in Fedora Linux 39 repos, not 23.2.3.  Updating provided the MariaDB 3.2.0 library by default, and the Host Connect By URL additional settings!

step 1: find out mariadb Unix socket file

strategy 1: via filesystem: grep -rin socket /etc/mariadb /etc/mysql
strategy 2: via SQL query: mysql -e "show variables like 'socket';"
in my case it is socket=/run/mysqld/mysqld.sock

step 2: use a fresh/untinkered installation of DBeaver, Version <IP_ADDRESS>309040911

select "New Database Connection". a pop-up "Connect to a database. Select your database" appears.

select "MariaDB", click "Next >". the pop-up becomes "Connect to a database. Connection Settings. MariaDB connection settings".

click button "Driver Settings" (lower right). a pop-up "Edit Driver 'MariaDB'" appears.

select "Libraries" pane. select "org.mariadb.jdbc:mariadb-java-client:RELEASE [x.y.z]". click on "Download/Update". a pop-up "Driver settings. Download driver files. Download MariaDB driver files" appears.

under "Files required by driver", within row "org.mariadb.jdbc:mariadb-java-client:RELEASE [x.y.z]", click on the "Version" cell. a drop-down appears.
select the latest version (in my case, "3.2.0"). click "Download". The "Driver settings. ..." pop-up closes.

back in the "Edit Driver 'MariaDB'" pop-up, click "OK". This pop-up closes.

back in the "Connect to a database. Connection Settings. MariaDB connection settings" pop-up, on the "Main" tab, under "Server":

for "Connect by:", select "URL"
for "URL.", provide "jdbc:mariadb://localhost:3306/?localSocket=/run/mysqld/mysqld.sock" - adapt "localSocket=..." to the file path identified during the previous "step 1".

configure "Username:" as appropriate

click "Test Connection ..." (lower left). if everything goes well, a pop-up "Connection test" with a successful "Connected ..." information should appear. click "OK" to close this pop-up.

back in the "Connect to a database. Connection Settings. MariaDB connection settings" pop-up, click "OK" to finish the connection setup.

This is it!! Thanks man...

This fixed it!  Also, I did have to uninstall dbeaver and reinstall to get a fresh install of 24.0.1 in order for this to work.  The only visible change I noticed was that on Connection Settings under Advanced: Local Client was now set to /usr.  Maybe try that before reinstalling.

For future reference : the snap version of dbeaver (dbeaver-ce) did not allow me to connect through the unix socket. I installed the .deb file and all went well.
Special thanks @Abdull for your precise step-by-step: it gave me enough confidence that the problem was somewhere else.


Not an issue - A little more information about the fan

Hi. First of all, thanks for this amazing project! I really want to do it, and during the analysis, I had some questions regarding the fan.
If I understand correctly, the firmware of the Ikea board toggle the fan every minute. Surely the firmware does a reading with the fan on. The doubt is the next one: If you replace the 5v output of the ikea board for the 3v3 output of the esp. Does the toogle function hold? Or would you have a fan that is always running?
Thanks

That results in the fan running constantly as it completely bypasses the FAN outputs of the Ikea PCB

Thanks @Hypfer.
What do you think about applying a step down to the FAN outputs of the Ikea PCB in order to reduce voltage to 3.3V? In that way the toggle function should work.

That would require more hardware. The permanent 3.3V were just there for the taking
I wasn't able to spot any downsides of running the fan continuously
Actually I'm more worried about the 5V UART to the 3.3V ESP8266 regarding long-term reliability
Only time will tell

Thanks @Hypfer for the information. I will test with the step down and I will share the results here :-)

Actually I'm more worried about the 5V UART to the 3.3V ESP8266 regarding long-term reliability

I did extensive Googling on this and it appears the ESP8266 UART is 5V safe for receiving.

I use a ~470ohm resistor from the IKEA to the Wemos-D1 Mini pin D7 (GPIO-13) with a surface mount Schottky diode (they have a low V-Forward drop) from D7 with its cathode connected to +3.3v, this clamp the voltage to 3.3V + V-forward drop of the diode... this makes it safer for the ESP8266 (I now see 3.7V on my unit on D7)... Using pin D7 makes it an easy fit for the diode to 3.3v pin on the Wemos-D1 circuit board. ( 3.3v - D8 - D7 ......) so the diode is set on top of D8, with just enough room to solder it to 3.3V and D7.

Just as a note: I move my unit from this codebase to Tasmota

Sounds great, I was also thinking of adding more so I'm curious... any notable issues to report using Tasmota to accomplish this?

Just as a note: I move my unit from this codebase to Tasmota

Sounds great, I was also thinking of adding more so I'm curious... any notable issues to report using Tasmota to accomplish this?

useing an esp32, works just fine....
~~ _/) ~~~~ _/) ~~~~ _/) ~~~~ _/) ~~
Tom Lafleur
On Sat, Jan 1, 2022 at 2:53 PM Greg Smith @.***> wrote:

Just as a note: I move my unit from this codebase to Tasmota
Sounds great, I was also thinking of adding more so I'm curious... any
notable issues to report using Tasmota to accomplish this?
—
Reply to this email directly, view it on GitHub
https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/issues/7#issuecomment-1003631144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABC4EK76TIBXXYLVC53V2C3UT6AVLANCNFSM5AXKPTIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***
com>

useing an esp32, works just fine....
~~ _/) ~~~~ _/) ~~~~ _/) ~~~~ _/) ~~
Tom Lafleur
On Sat, Jan 1, 2022 at 2:53 PM Greg Smith @.***> wrote:

Just as a note: I move my unit from this codebase to Tasmota
Sounds great, I was also thinking of adding more so I'm curious... any
notable issues to report using Tasmota to accomplish this?
—
Reply to this email directly, view it on GitHub
https://github.com/Hypfer/esp8266-vindriktning-particle-sensor/issues/7#issuecomment-1003631144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABC4EK76TIBXXYLVC53V2C3UT6AVLANCNFSM5AXKPTIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***
com>


Click events not returning properly on AR.JS objects

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When clicking on an entity (object) with a cursor, no id returns to the event listener, producing no behavior.
If the current behavior is a bug, please provide the steps to reproduce.
Click the link below, point camera to a Hiro marker and try LMB while gazing at the AR object (an orange).
https://lookit.io/webar/ARJS/AO/scenes/ar_test.html

What is the expected behavior?
The object should be detected  (return an event.target.id) and should scale up.
*Note: The object does spin when the cursor is over the object (so events are working to some degree), using begin="mouseenter", but click does not.
If this is a feature request, what is motivation or use case for changing the behavior?
No.
Please mention other relevant information such as the browser version, Operating System and Device Name
OS: Win10
Device: Desktop
Browser: Chrome 66.0.3359.139

Although you mark it as bug, this is a feature that has to be implemented
see https://github.com/jeromeetienne/AR.js/issues/328
and https://github.com/jeromeetienne/AR.js/issues/335

try looking at :
https://medium.com/chialab-open-source/how-to-handle-click-events-on-ar-js-58fcacb77c4

Did you just post that today?
Thanks!
On Wed, Aug 8, 2018 at 1:50 AM, Nicolò Carpignoli<EMAIL_ADDRESS>wrote:

try looking at :
https://medium.com/chialab-open-source/how-to-handle-
click-events-on-ar-js-58fcacb77c4
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeromeetienne/AR.js/issues/349#issuecomment-411334757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAczCN2MorEMirFNCGRFAe8Eb6WNRHQwks5uOqZZgaJpZM4UCPO_
.

as far i get at with ar js , i found that ar js may have some limitations but if we try to make it work through aframe js onclick events are working
this code is allowing me change the opacity of other element when another element is clicked.
thats i found that with triggering aframe js events it is working,
smoothly

	<a-marker preset='hiro'>

  <a-box

position="0 1 -5"
color="#6173F4"
rotation=""
opacity=" 0.2"
depth="0.1"
change-opacity="opacity: 1"
change-color="color: #f00"
material="src: url(https://i.imgur.com/wjobVTN.jpg)"

        <a-box

id="ch" position="0 0.5 -3"
color="#6173F4"
rotation=""
opacity=" 0.2"
depth="0.1"
change-opacity="opacity: 1"
change-color="color: #f00"

        <a-camera position="0 -0.5 0">


vue3-jsx直接报错

编译出来的文件ref直接丢失了？

<EMAIL_ADDRESS>说明这些案例都是没有测试过的，建议都自己去尝试一下

I will fix this issue, thank you.
One problem is that it is difficult for us to ensure that all examples can be continuously available. If you find any problems, welcome to submit a PR ❤.


automatic merge step for samples with replicates that differ in size

Hi there,
I've noticed that samples where there is a big difference in size between replicates (on different lanes), tend not to get merged to crams. For this reason it would be nice if there is an option to merge fastqs for rows in the samplesheet with the same sample prior to starting the pipeline. I'm testing now if its really the difference in size between the replicates that causes the issue, but it would be cool to have this feature in the future anyway. For some samples it is important to keep per lane stats, so I would suggest to make this feature optional.
Regards
M

I can confirm that concatenating fastqs before running the pipeline does fix the issue I was experiencing. So a flag for a pre-run merge step would be amazing.
Regards
M

Fixed in #115 by fixing the groupTuple flow, no more concatenation needed


Access AllEvaluatedItems (not just ordered with respect to items of the same item type) from within .csproj

Feature Enquiry
Is it possible from inside a .csproj file (perhaps using a custom MSBuild task) to access an ordered list of project items that are not just ordered with respect to the same item type? So, in the example below, being able to determine that one dog comes before the cat and another one comes after it.
<ItemGroup>
    <dog Include="bark" />
    <cat Include="meow" />
    <dog Include="woof" />
</ItemGroup>

<!--
@(dog) is only ordered with respect to other dogs :(
!-->

I'm aware that this property appears to provide this behaviour, but I only know how to access this from a VS extension project, not from inside MSBuild. Is this possible?

No, that's not possible.
As a rule, MSBuild doesn't make it possible to observe project state from inside a project; rather it requires explicit reference to the items or properties you are referencing. This makes it easier to reason about what a given snippet of code will do.
May I ask what you're doing that led you to ask about this?

That's a shame. It would be nice if MSBuild exposed a way to enumerate all project items in the order that they are declared (irrespective of item type).
What I would like to be able to do is declare some ProjectReferences before some PackageReferences and vice versa in a project file, like below ↓, and then be able to determine the exact ordering at build time in a task:
<ItemGroup>
   <PackageReference Include="somePackage">
   <ProjectReference Include="someProject">
   <PackageReference Include="someOtherPackage">
   <ProjectReference Include="someOtherProject">
</ItemGroup>

<!--  or even...  -->

<ItemGroup>
   <PackageReference Include="somePackage">
</ItemGroup>
<ItemGroup>
   <ProjectReference Include="someProject">
</ItemGroup>
<ItemGroup>
   <PackageReference Include="someOtherPackage">
</ItemGroup>
<ItemGroup>
   <ProjectReference Include="someOtherProject">
</ItemGroup>

<!-- and then... -->

<Task Name="WriteOrderedRefsToFile" BeforeTargets="BeforeBuild">
<!-- write the ordered references to a file for lookup at runtime -->
</Task>

Essentially I would like the order that a project's dependencies are declared in to be meaningful (regardless of whether they are project or package references), and at runtime I can use this order to affect the execution order of 'jobs' exposed by those dependencies.
Can you think of a way to achieve this? At the moment I'm stuck doing something like this (unless of course I want to depend on a custom VS extension).
<ItemGroup>
  <ProjectReference Include="someProject" RefOrder="1">
  <PackageReference Include="someProject" RefOrder="2">
  <ProjectReference Include="someProject" RefOrder="3">
</ItemGroup>

↑ this approach isn't very convenient/maintainable as new references are added or when reordering is required :(

And why do you need to implement such approach? What are you trying to achieve with that. I believe the manual approach is the only thing that I can think of. Though, in my opinion, neither of them would be particularly maintainable.

There are three reasons I can think of;

Why order matters: The dependencies in question each encapsulate a handler that's responsible for participating in a chain of responsibility. The ordering may need to change from time to time (as new handlers are added / some are no longer needed / handler responsibilities evolve / etc.).
Why use the declarative project item ordering instead of some imperative C# code: Project item order has recently been given UI support (although there is further work to be done). The SortByDisplayOrder project capability provides support for ordering project tree nodes in VS according to their project item ordering in the .csproj file, and for re-ordering those project items using 'Move up' and 'Move down' commands exposed by the Solution Explorer.
Why put the handlers in separate assemblies in the first place: Separating the 'handlers' into assemblies provides easy reuse in other projects that can compose and chains these handlers quickly and easily. The handlers themselves may be non-trivial, and deserve to be separate projects.

All in all, this means that the behaviour of the 'chain of responsibilities' is apparent simply by peeking at the composing project in the solution explorer, and that is also where the developer performs the reordering, at the click of a button / tap of the keyboard ↑ ↓. It's also naturally where the developer can add and remove handlers, and pull them into other composing projects.
Note: SortByDisplayOrder doesn't quite work out-of-the-box for the reference tree, but this enhancement can be provided fairly simply with a custom VSIX extension


missing crypto import is failing test

cross referencing this issue

the fix was adding an explicit import in the pino logger

Updated example. Thanks!


Only build NuGet packages in Release and special Debug build configurations

Fixes #389.
See individual commit messages for more details.

Thanks Drew!


less agressive cookie timeouts

it seems i get logged out after around 5 minutes in Cachet. while I can appreciate the effort to secure the software, I actually think that, in specific case of this software, being permanently logged in would actually be more useful than aggressively logged out.
in fact, what I was thinking here was that i would preventively login my phone, laptop, workstation and so on in advance, so that i don't need to scramble to find the password when i have an emergency update to send out.
at least having this configurable would be helpful.

This is configurable. :)

https://github.com/cachethq/Cachet/blob/master/app/config/session.php#L32

The default lifetime is 600 seconds, which is 30 mins. That seems like a good default to me.

@GrahamCampbell 600 seconds = 10 minutes ;)

I'm in agreement that we should increase this though.

oh i see. then maybe there's some documentation improvements to be done here, as i didn't find this on the documentation site...
how do i configure this anyways? in env.local.php?

600 seconds = 10 minutes ;)

Ha ha ha. I can math really, lol.

You can't configure the login expiration from Cachet itself, it's a Laravel thing.

 I can math really, lol.

I hope so, Mr Maths ;)

ah, so those are hardcoded defaults? would there need to be a patch to get this from the environment if i would want to make that customizable?
how about secure cookies? are those hardcoded as well?

I'd rather we just increase this value ourselves. At least then everyone is on the same page.
Secure cookies aren't handled either actually.

or to put this another way: it looks like there's a shitton and a half of awesome settings I could tweak in app/config - do i need to learn Laravel first? :)

Yeah, but I'd look at L5, we're migrating to it pretty soon.

ok.
as for a default, if we are to bikeshed for the default timeout, i would argue for 24h+ (86400s), personnally i would set it to "one week" (604800s). (Yes, mr. math replacement is in tha house! ;)

@GrahamCampbell what do you think about 24 hours? I think that's a good value, because ideally people will be logging back in to update the status of something anyway.

Let me check what the laravel default is. I think I lowered it in cachet.

https://github.com/laravel/laravel/blob/v4.2.11/app/config/session.php#L32

Ohhh, the time out is in mins, lol. Then we have a 600 min timeout. No where near to 5 mins!

:laughing:

ok, then something else is kicking me out. are we sure it's minutes there? the comment seems to say so...

i can confirm i was logged out in less than 10 hours. i was logged in when i posted the last comment here, and now i am logged out. even though on the frontpage of the site, i had a "disconnect" link, when i clicked on the dashboard link, i was presented with a login screen.

This seems to be fixed in the L5 branch. I've been kept logged into the dashboard for 4 hours now and still going.


BackgroundPlotter doesn't show when use plotter.show()

Hi, this is my code
import pyvista as pv
from pyvistaqt import BackgroundPlotter

p = BackgroundPlotter(show=False)
p.show()

I set the BackgroundPlotter show=False, according to the doc, after I call plotter.show(), it should show, but not.

OK, I use plotter.app_window.show() and it shows again. But when I call it again after closing the window,
it's got nothing like this


Update CodeBuild Compute Type

The CodeBuild Compute Type is set to BUILD_GENERAL1_2XLARGE causing an unexpectedly large cost to run this tool. Compute type has been dropped down to BUILD_GENERAL1_SMALL.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

https://github.com/aws-samples/aws-nuke-account-cleanser-example/issues/10
This needs to be merged

ok updated changes to main with BUILD_GENERAL1_SMALL. Please feel free to test/open other requests if arm container works. Thanks


Array lookup before bounds check in percentiles

The code which calculates a collection of percentile points from the histogram reads a value from the array immediately before checking that the value is in-bounds. This causes an index out of bounds exception every time I call percentiles with a small number of samples.
Expected behavior
Check the bounds before reading from the array, not after.
Actual behavior
Calling percentiles consistently causes an index out of bounds panic.
Steps to reproduce the behavior
fn main() {
    let splits = [25.0, 75.0];
    let h = histogram::Histogram::builder().build().unwrap();
    h.increment(1, 1).unwrap();
    h.increment(10000000, 1).unwrap();
    let answer = h.percentiles(&splits).unwrap();
    println!("Successfully retrieved the percentiles!");
    for p in answer {
        println!("{} {}",
            p.bucket().low(),
            p.bucket().count());
    }
}

thread 'main' panicked at 'index out of bounds: the len is 2 but the index is 2', ...

Thanks for opening this @willmurnane
I've prepared a fix in #28 and will update once the fixed version is available on crates.io

histogram 0.7.2 has been published to crates.io and fixes the reported issue.


add fill_func to fillna

What does this PR do?
I add the parameters a fill_func for filling NA
default is the same as the original
and
we can expand the function to fill the NAs
Where should the reviewer start?
the constructer of the autoclean function
How should this PR be tested?
I add the test function in tests.py
Any background context you want to provide?
 python dynamically import and numpy nanfunctions modules

What are the relevant issues?
[you can link directly to issues by entering # then the number of the issue, for example, #1  links to issue 3]
Screenshots (if appropriate)
Questions:

Do the docs need to be updated?
If my pull request is admitted, I will add docs
Does this PR add new (Python) dependencies?
Nope.

Coverage increased (+1.1%) to 80.377% when pulling f90e94de2ff8c7e3fa2ed8cf3243bff62545cde4 on ghk829:master into f6f92d763ab385013b72776acf990857d4949e66 on rhiever:master.


"/nix/store/... is not in the nix store"

I'm doing something like
{
  sops.secrets.foo.sopsFile = "${secretsPath}/foo"; # where secretsPath = "/nix/store/..."
}

but this fails because of this check:
https://github.com/Mic92/sops-nix/blob/b0d764fccdd35588ebda2907911099198f73c89a/modules/sops/default.nix#L154
I could use secretsPath + "/foo" instead, but I feel like I shouldn't have to. Is there a better way to check whether a path is in the Nix store?

One could check if it starts with builtins.storeDir.
nix-repl> builtins.storeDir
"/nix/store"

Maybe with a round-trip through builtins.toPath and builtins.toString first in order to normalise it.

I don't want to force it to be a path otherwise it might be copied to the nix store without the user intending to do so.

toString converts a path to a string without copying anything to the store.
The manual says toPath is deprecated, so it would rather look like:
lib.hasPrefix builtins.nixStore (toString (/. + sopsFile))

Ok. Do you mind open a PR for this?

Upon further investigation, the scenario I was describing can only work if nix.useSandbox is set to false (which I don't really want), because otherwise the builder for checked-manifest.json doesn't have access to secretsPath, even if it's in the store.
So I think it's actually sane to require a path if validateSopsFile is enabled.
The error message is a bit confusing though, maybe I'll make a PR to change that.

Thanks!


move elastic datadog integration to ES machines

We're already running the agent on the ES machines. This just puts the ES integration on those machines instead of on the PG machine. This should make the builtin dashboards work better: https://app.datadoghq.com/screen/integration/elasticsearch

@ben / @calellowitz
cc @kaapstorm

nice this is sweet. i was looking at the actual dashboard too, do you know why it has queries from hqdb0? it also says our disk is 86% full which seems kind of high

It lists hqdb0 because we were running the integration on hqdb0. I think
that will stay there until there is no data from hqdb0 in the time window.
Disk space does seem a high though it's ~22GB per node so probably not
serious for now.

ah gotcha. should've realized it would take time to propagate the changes to the dashboard


[turbopack] esm interrupt error when transform to lower browserslist_query

What version of Turbopack are you using?
1.6.3
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
import a cjs module in esm module with a lower browserslist_query, will throw Uncaught ReferenceError: module is not defined.
Expected Behavior
should not have the ReferenceError.
To Reproduce
Change the browserslist_query:

// index.js
import lib from './lib.js';
console.log(lib());

// lib.js
module.exports = async function() {
  return 1;
}

Reproduction Repo
No response

It seems caused by SWC inject_helpers, lib.js should be a cjs module but after inject_helpers it was transformed to a esm module, and this will not happen in babel

swc now creates var helper = require() for Program::Scripts.
https://play.swc.rs/?version=1.3.46&code=H4sIAAAAAAAAA8vNTynNSdVLrSjILyopVrBVSCyuzEtWSCvNSy7JzM9TSMvTSCwq0lSo5lJQKEotKS3KUzDkquUCAOxwi%2Bc3AAAA&config=H4sIAAAAAAAAA22OSw7CMAxE95yiypotG07AhkNYwSmp8pPtSq2q3p0k%2FRAkNnH8ZjSe5dJ1amCt7t2Sv3lJQIx07pnwHASmTBRqD6zJJlHXQx24SAYcY0XrpiicBCmAe6BLSJw9QiPuogD1KDWSb3uWcjEyHlk78zZYM7dtdPSJkPnXWKwQeod%2FuwhBYBPJt0GEoKUBFZkc%2FS5w3ek2y1vDvoXO48ryM77G5vT6Ae4%2F33lWAQAA


[!] Wall of Flippers >> Error: Failed to scan for BLE devices >> [WinError -2147020577] The device is not ready for use

https://github.com/hbldh/bleak/issues/792


Remove the example app from the dependencies

Currently, I'm not able to include the project in my app because my minSdk is 16 and the app has 18.
Is minSdk 18 is not necessary for rxfeedback, right?

Fixed (by lowering minSdk)


SumType becomes less memory efficient when any variant contains a non-isbit type

I noticed this when developing https://github.com/JuliaDynamics/MixedStructTypes.jl e.g.
using MixedStructTypes

@sum_struct_type @kwdef A{X,Y} begin
    mutable struct B{X}
        a::Tuple{X, X} = (1,1)
        b::Tuple{Float64, Float64} = (1.0, 1.0)
        const c::Symbol = :s
    end
    mutable struct C
        a::Tuple{Int, Int} = (1,1)
        const c::Symbol = :q
        d::Int32 = Int32(2)
        e::Bool = false
    end
    struct D{Y}
        a::Tuple{Int, Int} = (1,1)
        c::Symbol = :s
        f::Y = 2
        g::Tuple{Complex, Complex} = (im, im)
    end
end

vec_a = A[rand((B,C,D))() for _ in 1:10^5]

now
Base.summarysize(vec_a) #5053868 (wow!)

let's use instead
using MixedStructTypes

@sum_struct_type @kwdef A{X,Y} begin
    mutable struct B{X}
        a::Tuple{X, X} = (1,1)
        b::Tuple{Float64, Float64} = (1.0, 1.0)
        const c::Symbol = :s
    end
    mutable struct C
        a::Tuple{Int, Int} = (1,1)
        const c::Symbol = :q
        d::Int32 = Int32(2)
        e::Bool = false
    end
    struct D{Y}
        a::Tuple{Int, Int} = (1,1)
        c::Symbol = :s
        f::Y = "s"  ### non isbit
        g::Tuple{Complex, Complex} = (im, im)
    end
end

vec_a = A[rand((B,C,D))() for _ in 1:10^5]

now
Base.summarysize(vec_a) #8863933

Is there a way to improve this? Or is this expected? Notice that in the second case the memory occupied is very similar to just a compactification of all fields in a unique struct

ok actually changing struct D{Y} in mutable struct D{Y} gets a better memory efficiency, in this case vec_a requires 6933221 bits, still I'm a bit puzzled by these results.
(What all of that expands to in relation to SumType.jl  (in the first case here)
SumTypes.@sum_type A{X, Y} begin
        B{X}(ht::var"##B#225"{X})
        C(ht::var"##C#227")
        D{Y}(ht::var"##D#228"{Y})
    end

where the inner types are mutable/immutable structs with all fields defined as above.)

So one thing to notice is that your vec_a abstractly typed (missing parameters). I suspect you actually wanted to do
vec_a = A{Int, Int}[rand((B,C,D))() for _ in 1:10^5];

which brings it down to 4860060 bytes. (48 bytes per element) which seems pretty reasonable, since the biggest variant you have is D and, D{Int} should have a footprint of 40 bytes, and then there needs to be a discriminator for the union (i.e. a flag for whether it stores a  B, C, or D), which presumably gets bumped to 8 bytes for the purposes of padding.
And with the non-isbits definition that stored a string, I get
julia> vec_a = A{Int, Int}[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
4325972

julia> Base.summarysize(vec_a) / 10^5
46.94708

so that's also good.

Regarding the increase in footprint from the non-isbits "a", I'm not totally sure what's causing that to be honest. I guess just more pointer indirection meaning there needs to be a pointer in D and also the actual string out there somewhere.

thank you a lot (I always forget to add parameters :( )
so the last case where memory increase is just when the vector is abstractly typed, right? Then I think this is not really problematic, so I think this can be closed

And with the non-isbits definition that stored a string, I get

mmh I tried it now, I think that you mean the one which stores an Int right? Then I think I misunderstood you in my last comment above

Yes, with a String it is less efficient, but also strangely Base.summarysize oscillates
julia> vec_a = A{Int, String}[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
6561005

julia> Base.summarysize(vec_a)
6204757

julia> Base.summarysize(vec_a)
6039637

julia> Base.summarysize(vec_a)
5999493

julia> Base.summarysize(vec_a)
6170045

julia> Base.summarysize(vec_a)
6450517

Yes, with a String it is less efficient, but also strangely Base.summarysize oscillates

Yikes, that is weird, I have no idea what could cause that.

No I meant the String one I think?

okay, but I think then that the memory usage is more on 6 million bytes than on the 4.3 million in this case, not totally sure about the amount because Base.summarysize is not totally sure either :D
Do you think this is worth an issue in the Julia repo?

Opened an issue about Base.summarysize: https://github.com/JuliaLang/julia/issues/53061, seems like it happens also in simpler structs

just an update because the issue was fixed on Julia nightly, on it:
# first version in the main comment
julia> vec_a = A[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
4526700

julia> vec_a = A{Int, Int}[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
3739036

# second version in the main comment
julia> vec_a = A[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
5866653

julia> vec_a = A{Int, String}[rand((B,C,D))() for _ in 1:10^5];

julia> Base.summarysize(vec_a)
5066685

it seems better now with the right numbers

Actually now that I investigated it a bit more, in Julia 1.11 where the issue with Base.summarysize has been fixed, I actually see very often that sum types outperform Union types by quite a bit usually, see https://github.com/JuliaDynamics/DynamicSumTypes.jl?tab=readme-ov-file#micro-benchmarks, there a sum type is 3 times more memory efficient than a Union!! And relooking on the updated numbers here I posted before it seems alright also


Pod Installation (pod repo update / pod install)

Description
Apparently, I am having hard time installing / updating pod.
I get this error message whenever I try to do so.
 [!] Unable to add a source with url `https://github.com/AudioKit/Specs.git` named `audiokit`.
I have researched and invested some time to resolve my issue. Now, I am guessing that "https://github.com/AudioKit/Specs.git" link has become invalid as link itself shows 404 error message when I search for it.
May I get assistance on this issue by any chance? I really want to contribute on this project by providing Korean translations.
P.S. Sorry that I had to use bug label as my type of issue was not applicable for any of AudioKit's issue type.

You can comment source 'https://github.com/AudioKit/Specs.git' in the pod file.

@billchen2k Hey, thank you for answering question. But, don't I need 'source https://github.com/AudioKit/Specs.git' part in the pod file? Would you be able to provide more details in your suggestion? (I have tried your suggestion, but I just couldn't understand what it really does.) Thank you in advance.

Actually, as mentioned in the repo's readme file:
You may uncomment the line in Podfile to switch to our cutting-edge staging (unstable) releases of AudioKit, as opposed to the stable releases in the mainstream CocoaPods specs.

This line tells pod to install packages from the source 'https://github.com/AudioKit/Specs.git', which contains unstable packages under development. Uncomment it just let you download those stable release dependencies. (I don't think that unstable repo is publicly available by the way)


Add https and http proxy support for fetch

Let swift build be aware of the http proxy variables.

I wonder if we should inherit all of the env

I did it this way to be consistent with the other function that inject the environment variable into the system function.
Do you think it would be better to split the variable list passed ?

I am coming around to thinking that we should inject the full environment when we are running git clone commands, rather than cherry pick variables. That should solve the problem here, can we do that instead?

As suggested, I updated the PR to read all the environment variable for the cloning operations.

LGTM

@swift-ci please test


CDN considerations

How?

This is auto:
https://github.com/jsdelivr/jsdelivr

jsDelivr can instantly serve any file from any npm package in the public registry. New versions pushed to npm are instantly available via our CDN as well. No maintenance is required.

/npm/package@version/file
<EMAIL_ADDRESS>


[Feature Request] Support "block" text objects (e.g. vib 'caB`, etc.)

It would be great if there was support for "block" selection objects. For example:

vib: "select inner block" (between parens)
caB: "change a Block" {including brackets}
etc.

List of selection objects:
http://vimdoc.sourceforge.net/htmldoc/motion.html#object-select
Follow-up to https://github.com/jeffreytse/zsh-vi-mode/pull/140#issuecomment-970206861

Hi @milesfrain
Thanks for the delay, I'm happy that you commit this issue. Currently, I'm busy, but I will work on this feature in the future. Hope you have a good day! : )
Thanks and Regards


Library is not compatible with CloudFlare Workers / Vercel Edge functions

It uses axios which is not supported by neither of those two solutions :/

More detailed error from a Next.js app, API route:
 [AxiosError: There is no suitable adapter to dispatch the request since :
- adapter xhr is not supported by the environment
- adapter http is not available in the build] {
  message: 'There is no suitable adapter to dispatch the request since :\n- adapter xhr is not supported by the environment\n- adapter http is not available in the build',
  name: 'AxiosError',
  code: 'ERR_NOT_SUPPORT'
}

Next.js edge runtime does not support full Node.js API. In particular, it doesn't support http module. It does support Fetch API though: https://nextjs.org/docs/app/api-reference/edge.
With Fetch API becoming stable in Node.js 21, it'd be nice to declare axios as an optional dependency and use Fetch API as the default request caller.

Just ran into this issue too, better to use the native fetch API instead of Axios :?

Just ran into this - a potentially quicker fix could be to use this adapter that I have used with other libraries that rely on Axios, however would require some work to either pass the adapter in or expose the Axios object.
https://www.npmjs.com/package/@haverstack/axios-fetch-adapter


npm ERR! notarget No matching version found for<EMAIL_ADDRESS>

Bug report
Describe the bug
I am not able to install the npm package because of<EMAIL_ADDRESS>dependency, I tried to install the<EMAIL_ADDRESS>from npm but not able to install the specific version (even i see its available on npm)  and i updated the node-fetch package and it got updated to version 3.2.0, but still i am not able to install @supabase/supabase-js
please let me know how to fix this, thanks.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to cmd
run npm install @supabase/supabase-js

Expected behavior
It should install the package.
Screenshots

System information

OS: Windows 10
Browser (if applies) firefox
Version of supabase-js: 1.30.6
Version of Node.js: v16.13.0

Additional context

Can you try running npm install<EMAIL_ADDRESS>on a fresh (npm init -y) npm project? If there's likely something odd with your system/node installation since<EMAIL_ADDRESS>exists on npm.

Ah, just saw your edit. Does it work if you do the npm install above?

Yes, when I tried to install on a fresh project, it worked. Then took the "@supabase/supabase-js": "^1.30.6", form that package.json and added in my project's package.json and ran npm i and it worked again, i don't how but i was able to install the<EMAIL_ADDRESS>Thank you so much for your help

Probably it was my system issue, edit package.json and run npm i


Continue from #224: fromarrow and toarrow.

99.5% of the work on this PR was done by @trickarcher.  So I have to close his and open a new PR to put my last touch-ups on it, but most of the work is his.

Thank you so much for this! @jpivarski, I never knew there were so many things hidden away. I'll write better test suites from now on! Thanks again!

Don't worry about it—I don't think these issues could have been solved by "more diligence." There's just a lot of things that need to be considered and it will take time to get them all in the documentation.
One thing that none of these tests would have triggered, including the ones I ported over from old Awkward, is that contents can be longer than the enclosing container needs it to be (e.g. a ListOffsetArray might have "10" as offsets[-1], but its content can have a length that is longer than 10). This is valid in Awkward Array, though rare and not included in any tests, but I don't think it's valid in Arrow. So when to_arrow goes down to the next level with recurse, I've just added a slice of the content so that it's exactly the right length, all the way down. This is an example of where 100% test coverage fails: even though the tests now have 100% coverage, they would not have caught this.

Wow yeah, I never tested it out with that possibility. However, strangely enough, I did catch this issue during the to_arrow conversion of ByteMaskedArray. So beyond the masks, the content array was copied as-is, which was not what awkward-1.0 was doing. awkward-1.0 stopped when the masks ran out of indices to apply masks on. So I just sliced them after the entire conversion was done.
Also, are we testing the conversions out with some large dataset?

Also, are we testing the conversions out with some large dataset?

I don't have plans to do so, but it wouldn't be a bad idea. However, @kyungeonchoi might end up doing this as part of ssl-hep/ServiceX#131. That will involve large datasets pretty soon.

Yup, makes sense. Thanks!


Item drops from cursor slot when killed while in a keep-inventory: true region

If you are holding an item with your cursor while killed in a region set with keep-inventory:true, that item will drop.

Well this is just unfortunate side effect of dying. The inventory closes which then causes the current item to be dropped, all normal behavior. After that the actual dead occurs and the handling of item drops etc. I don't think I can do much about this without making it a bit clunky.

I see, this would be the case with vanilla gamerule keep-inventory as well?

I would be surprised if it didn't.

Confirmed.
Same behavior in the vanilla gamerule.
Not ideal Mojang
Thanks!

any chance of a WorldGuardExtraFlags fox for it?

Its something I can look at

Thanks,
I'll also submit a ticket to Mojang as they may consider this a bug to fix as well.


Add in BlockHeight in protobuf for dposV3 for Delegation Type

In order to show delegation statistics for analysis, it is useful to know the block height the delegation was created. This was available previously in dposV2

Now that it's possible to combine delegations, it isn't clear what the block height field should contain. The field wasn't used in DPOSv2 and it would be confusing with multiple delegations. It should be possible to calculate all the necessary statistics by checking events.

Ok, let us try that


Mappy

some current issues:

address search full row overrides a decent amount of the map functionality (ie can't + or - with the zoom interface, or touch the map portions of the address search row)
Address search shifts slightly on search

But let me know the general structure. Minor things can be cleaned up / adjusted later.

FYI - copying over these TODOs from #12 cause they're still needed w/ this PR:

[ ] zoom map to address once it is selected
[ ] make the example web maps pretty (turn layers on/off at scales, etc)
[ ] prob need to add options like no scroll wheel zooming when initializing map

oh and tests are failing like it's going out of fashion, but for me that's also true on master (see #19)

@MarkhamShofner what's the deal w/ this?

@tomwayson Looking to close it out before the end of this sprint. Have a version working locally but when deploying to surge, ember-esri-loader is causing issues.


Detecting memory errors with lwaftr check

I've been thinking on how to detect memory errors.
Bugs #439 in #437 were due to memory errors. Our test suite included tests for these cases but since the end-to-end test only sends one packet these memory errors were not triggered. To trigger these errors it would have been necessary to send the same packet several times.
Instead of creating specific datasets with the same packet repeated several times, I think it would work better if we make "lwaftr check" to do this job for us.  I would keep "lwaftr check" as it is and additionally run another test that sends a packet several times in a loop and direct its output to a sink.
Why not modifying lwaftr check and make it run in a loop always? There are some difficulties. Snabb runs for a certain period of time and the number of packets sent may vary in different runs. Having a different number packets sent spoils the test (output wouldn't match and neither the counters). Using done instead of duration has the same problem (done is not called in deterministic time). Even if we could hack a work around the output files would increase considerably, increasing the total size of the project. For this reason, I prefer to keep lwaftr check as it is and additionally run a "memory test".

Yep.... that's one of the reasons why I've repeatedly said we should run overnight tests (and on mixes of packets, not just one repeated 50 times or something), and keep talking about needing more test coverage.

Implemented in #443


Kotlin upgrade to 1.3.41

Automatically prompted by IDE

If we have a defined policy, then happy to follow it.  Otherwise I'll follow Intellij prompts.

I will next time.  It looks like a lot of type inference fixes, which are unlikely to help once we already have compiling code and explicit return types on public api.
https://github.com/JetBrains/kotlin/releases/tag/v1.3.41


merge from konsum-frontend-svelte

package.json

chore(deps): add ^10.7.3 remove ^10.7.1 (devDependencies.npm-pkgbuild)

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

npm package (@latest dist-tag)
v1.31.18
GitHub release

Your semantic-release bot :package::rocket:


Add --remove-uncalled-funcs

Fixes most of #85. Not enabled by default but is a relatively safe optimization. It might break some indirects? (if they don't use funcRef somehow)
Example:
$ ./porf -e "console.log(1)" -b --no-run
wasm size: 39234 bytes
$ ./porf -e "console.log(1)" -b --no-run --remove-uncalled-funcs
wasm size: 27428 bytes
$ ./porf -e "console.log(1)" -b --no-run --remove-uncalled-funcs --uncalled-funcs-runs=5
wasm size: 22441 bytes

Some other examples for comparision:
$ ./porf -e "Porffor.miniLog(1)" -b --no-run
wasm size: 23326 bytes
$ ./porf -e "Porffor.miniLog(1)" -b --no-run --remove-uncalled-funcs
wasm size: 15604 bytes
$ ./porf -e "Porffor.miniLog(1)" -b --no-run --remove-uncalled-funcs --uncalled-funcs-runs=5
wasm size: 11970 bytes
$ # and our obvious winner:
$ ./porf -e "Porffor.numberLog(1)" -b --no-run
wasm size: 115 bytes

A 30% wasm size reduction for console.log :tada: (and potentially up to 42% :eyes:)

I don't think this is needed anymore with latest rewrites?

I agree yes, I'll close it now.


Fully integrate polymorphic verifier

A new abstraction for polymorphic verifier's has been introduced to help ease the link between compile configuration and unit tests. However, in order to keep the cost of integrating this small within in the context of the PR it was introduced in, it was integrated into the transition frontier in a non-type safe way. It is easy to integrate it in a type safe way, but will involve adding extra type parameters to types such as the staged ledger diff, external transition, breadcrumb, and transition frontier. Until this is done, there is some runtime type checking which occurs and may throw and exception if ledger proof and verifier types are mismatched by accident. The likelihood of this ever happening outside of unit and integration tests is very low as the current pattern for default implementation selection is still in place.

Took the partial integration of this out for now. Need to have a discussion regarding whether or not it makes sense to use this abstraction or not. Leaving it in the code for now.


Document CLI best practices

We follow the 12 Factors CLI principles https://medium.com/@jdxcode/12-factor-cli-apps-dd3c227a0e46 for our CLI and plugins.
By documenting best practices and sharing the above link we would help developers who write plugins for aio to avoid common pitfalls and provide unified experience to end users a

this extended guide could be useful too: https://clig.dev
especially for developers aiming for guidance in concrete cases

this extended guide could be useful too: https://clig.dev
especially for developers aiming for guidance in concrete cases


Update voi.py

This seems like a cosmetic change. What is the reasoning behind replacing the dictionary keyword?

I get a key error for line 164:
KeyError: 'VOIVTCs'
test.txt
when saving this example voi file

Got it, thanks.


Workfiles tool event arguments fix

Issue
Avalon event emit expect that second argument is list or tuple of arguments but workfiles tool is sending string which is not expected.
Changes

emit workfile arguments as list instead of path

NOTE
I found it out in maya. When I saved workfile there is an error in scriptsmenu telling that callback did expect only one argument.

Can't test it as don't have Maya


Update SEO changes to match final gem

Change over SEO handling from local test gem to final production gem after it is released on https://rubygems.org/gems/jekyll-seo-tag.

Changes image structure

Updates path dependencies as well.

Removes node_modules/ from the fist of RuboCop

JSON-LD Testing added against Google Structured Data Testing Tool using rspec.


Smuggle fields-path param can dereference maps, arrays & slices

Pull Request Test Coverage Report for Build 710911977

164 of 164 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 99.828%

Totals

Change from base Build 707949090:
0.003%

Covered Lines:
8130

Relevant Lines:
8144

💛  - Coveralls


feat: add a RecordResource to log the received record from tis stage

No more logic is needed this sprint, just created a api to make sure the record sent by aws lambda is received by this service.
TISNEW-4306

To fix the vulnerability reported by Sonar, I added an entity and a mapper for the Dto.


importer.call is not a function

Somehow using the cli importer seems not to work anymore
./node_modules/.bin/node-sass --importer node_modules/node-sass-json-importer/dist/cli.js --recursive ./src --output ./dist
"node-sass": "^4.11.0",
"node-sass-json-importer": "^4.1.2",

node_modules/node-sass/lib/index.js:338
        var result = importer.call(options.context, file, prev, done);
                              ^

TypeError: importer.call is not a function
    at options.importer (node_modules/node-sass/lib/index.js:338:31)

Hi,
I just discovered the same problem and I think this is somehow related to the conversion of the es6 modules to common-js modules.
In node-sass the importer is actually an object and the correct function is buried in importer.default, so using importer.default.call produces the expected output.
I can have a look at this and and open a pull request, if I find a solution.

:tada: This issue has been resolved in version 4.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow PostgreSQL connections to EnterpriseDB

This PR allows the pg client to connect to an EnterpriseDB instance. I've been using a local modification for this for a couple months, and haven't encountered any issues yet. It's been brought up before (#1176), but didn't receive any follow-up.

[x] Tests - Tried to replicate existing tests. Happy to make suggested changes, as necessary!
[x] Coding Style - Couldn't find any specific documentation. I can switch the var to const (prefer-const) in tests, but kept it for backwards-compatibility with older Node versions.
[x] PR on master
[x] Documentation - No updates, unless EnterpriseDB should be added.
[x] Passing Tests - Everything, with the exception of batchInsert currently failing on master. Verified this PR does not affect those tests.

I couldn't figure out any patterns in the tests, so wasn't sure if additional tests are needed. Adding another database (EnterpriseDB) to the testing list seemed excessive, so I've only added a few unit tests to cover the specific functionality.

@qjroberts Does EnterpriseDB has same version numbers that normal postgres so that EnterpriseDB 9.4 for example is based on the same features that postgres 9.4?

It looks that way from their documentation, and from the versions I've used. The do seem to add an additional point release (for example, 9.3.13 vs <IP_ADDRESS> in the PR tests). I forgot to check to see how that might affect the version check elsewhere, but it looks like the only spot is in src/dialects/postgres/schema/columncompiler.js, which already uses parseFloat to grab the major/minor version. I just tested it, and it looks like parseFloat will work the same with the 4-part release numbers as it does with the 3-part ones.
It does look like the tests are failing on the older versions of Node, compared to master, so I'll have to take a look at those tomorrow!

@qjroberts Try pulling latest master, timing issue should be fixed, sorry.

Thanks! I tried looking into it yesterday, but didn't have any luck. It looks like it still exists though, I'm getting the failure locally, both on current master and my (rebased) fork.
I'll keep poking around the changes to batchInsert to see if I can dig up anything else.

@qjroberts also this PR is somewhat related to this https://github.com/tgriesser/knex/pull/1959#discussion_r107582373
Maybe parsed version info could be limited to first x.y or x.y.z. That way parsed version should be compatible and still provide enough information for knex.

That might be a better solution. I like what #1959 does as well, but the current code looks like it would just ignore the version check if one was specified. I'm happy to close this one if that's the direction you'd like to go.
The regex solution itself seems a bit weird, especially if there are more Postgres variations that modify that version string. I can take a look if you think it's worth trying to modify the regex into something a bit more generic, in addition to #1959.

@qjroberts I don't believe that we should modify that regex to be much more generic.
I was fine with this addition though since the EnterpriseDB versions follows to real postgres version and is closely related to the open source postgres project.
So I don't have anything against this, but I believe that 100% of our current user base can be served with the solution in #1959.
One hypothetical usecase for this could be project, which supports some json columns and would like to still support postgres / enterprisedb < 9.2
I leave it up to you if you like to get this to master or to close it.

Since #1959 seems to satisfy the requirements for this, I'll close this for now. If I find anything that needs an additional solution, I'll open another PR.
Thanks!


Use cuda-toolkit in release container build

Description

Update conda recipe to use cuda-toolkit for build
cuda-toolkit no longer gets installed as run dependency by cudf (via cuda-python)

Checklist
[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


CI: Only use coveralls on Core, PetriNet and STG

The plugins have near-zero coverage, so skip them for now.

Ugh, the paths can't be relative to a subdirectory. I need to fix this.

@danilovesky PTAL. For some reason coveralls is lagging and its result isn't showing here, but if you look at https://coveralls.io/github/tuura/workcraft, you'll see that coverage is now 19%.


Update filter queries to pull tissue_ancestors from /datasets/index

Approach

Remove hard-coded PoC data and re-enable existing mapping functionality.

Implemented in cc/ontology-filter-ii.


fix: update packages.json

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


Issue 920 Make uses show up in templates clean and responsive

With this PR the @uses tags show up in the clean and responsive templates.
The @throws tags and the @used-by tags have not yet been fixed.
A behat scenario is included to test the correct working for tags referring to the same file. However, it has been manually tested that referrals to other files also work.

I don't see any issues in this. Thanks again for this great job!


Documentation cleanup

Mostly removes pages that have not yet been written from the index, and reorganizes the index a bit.

This looks useful, thanks @dnicolodi. Not sure if you're still adding things? I'll review/merge if ready.

I think the documentation would need some more love, but this is IMHO already a nice step forward while being minimally invasive. I'll open another PR for further work. I'll be happy if you could review this PR in its current form.

I've pushed two more commits with the suggested changes to the TODOs-only pages. PTAL.

Last two commits LGTM.


Feature/Generate Freeze- and Defrost Plans

Automated resumption of scheduled TOSCA applications
Two new bpel plan builder added.
They create new backup plans if the interface "http://opentosca.org/interfaces/backup" is added

Start and end date:  25.04.18 - 25.10.18
Supervisor: Lukas Harzenetter

works with {http://opentosca.org/servicetemplates}MyTinyToDo-MySql_OpenStack-w2-wip1 at https://github.com/OpenTOSCA/tosca-definitions-internal/pull/50/commits/fbc90682381cbda14eb70ceee9109139a689b670


[DOCS]

Description
Hello,
Suggestion:- My suggestion is an about section more detail could be added. Please assign this task to me under GSSOC'2023.
Screenshots

Additional information
No response

@mahak-dev kindly start work send the pull request


serde serialization of crs and edges should be skipped when None

Per https://github.com/geoarrow/geoarrow-r/issues/34#issuecomment-1925872634 crs and edges shouldn't return null when not set. Rather, they should be omitted. This can be configured with serde #[serde(skip_serializing_if = "Option::is_none")] on the Option field
https://github.com/geoarrow/geoarrow-rs/blob/eb94df3d998801be3c55128b4535fc9f58652b66/src/array/metadata.rs#L28-L32

good to know about that serde option but we should be checking if all fields are null and not even writing the metadata key in that case

This is solved now. Helped by https://github.com/geoarrow/geoarrow-rs/pull/719 but solved separately before that I think.


Uncaught Error: Can not find frame with name: undefined

Hi @bluepnume ,
I'm updating from version 1.0.112 to 5.0.3, and encounter this error:
Uncaught Error: Can not find frame with name: undefined
I found out that the error above raise because it cannot find the window.name.
And I found that https://github.com/krakenjs/xcomponent/blob/820a42521cbde1b8c78a52bc09c98bd2eaf487a1/src/component/window.js#L64 is where it deconstructing and assign the window.name.
But from the console screenshot, the only key I found that match with the deconstruction assignment is windowName, but I cannot find where windowName is being assigned to window.name.  Perhaps I'm in the wrong direction.

Hi @andychong1996 -- are you loading 5.0.3 in both the parent and child window? "Can not find frame with name" is not an error message which should exist in  5.0.3...

Hi @bluepnume ,
this is the version in my yarn.lock:
<EMAIL_ADDRESS>  version "5.0.3"   resolved "https://registry.yarnpkg.com/xcomponent/-/xcomponent-5.0.3.tgz#2e8261f643f94e4d3dbf544d8ffad6cdf6bdf62a"   dependencies:     beaver-logger "^3"     cross-domain-safe-weakmap "^1.0.8"     cross-domain-utils "^1.0.5"     hi-base32 "^0.1.1"     post-robot "^7.0.1"     zalgo-promise "^1.0.4"

Hi @bluepnume ,
I found the problem, the source is from an abstracted docker service. Seems that the codebase in the container is not in sync. Thanks for the help and the team for building such great library!

Awesome! Glad it's working now


infinite "downloading resources"

macOS, v.0.6.4
I selected Transcribe, Spanish, Very High, Microphone
machine is MacBook Air M2, 24Gb RAM
as soon as I pressed "Record", it popped out a window showing "downloading resources", it's been a couple hours, it's still the same, says it's about a trillion percent progress in downloading :)
however it seems to have transcribed some loose words from a conversation I was having, don't know at what point it did.
Screenshot attached.

This is being fixed in an upcoming version. What happens when you try with quality set to Very Low/Low?

I guess it's just an UI issue, when I look at ~/.cache/whisper I can see the large-v2.pt file is continuously growing so it's downloading, and it's roughly the same as the percentage shown. So the UI assumed a size of 1 byte and it's showing the percentage based on that.
But... it shouldn't do that when you press "record" and by all means it shouldn't keep the microphone open.
There should be some UI to download the models first.
Ideally, one would download the models independently (via URL, using the browser) and import them into Buzz.

And indeed my Mac shows the microphone is being used by Buzz all this time (hours) while "downloading resources".
And the transcription window shows some Spanish text (I had selected Spanish), while I've been totally silent, it seems to be text from some YouTube channel (it says the Spanish equivalent of  "suscribe", "buy this is the last chance"), this is eerie... I have no video running, and I'm alone now... it might have picked up words from some videos my wife was watching an hour ago, but also I don't recall such words...

Great app! Audio file transcription works impressively, but I have the same problem with "downloading resources" using live recording (from internal audio).
English transcribe, high quality, RealTek ASIO (default internal input)
Windows 10, 32GB RAM, NVIDIA RTX 3090 24GB RAM
If it's a UI issue then it sounds like it's on Mac and Windows.

Great app! Audio file transcription works impressively, but I have the same problem with "downloading resources" using live recording (from internal audio). English transcribe, high quality, RealTek ASIO (default internal input) Windows 10, 32GB RAM, NVIDIA RTX 3090 24GB RAM
If it's a UI issue then it sounds like it's on Mac and Windows.

Thanks! Does version 0.7.1 work for you?


ConfigureSwaggerGen doesn't do anything

If I put a breakpoint in options.DescribeAllEnumsAsString(), it is never hit.
Also the UI comes up empty.
            services.ConfigureSwaggerGen( options =>             {                 options.DescribeAllEnumsAsStrings();                  try                 {                     options.IncludeXmlComments(pathToDoc);                     options.IncludeXmlComments(modelPath);                 }                 catch                 {                 }             });

Scratch that!


Wish: serialize decimal crate objects

The decimal crate implements decimal floating point arithmetic in rust. JSON supports decimal numbers.
It would be nice if there were an obvious way of how to serialize (and deserialize) d128 objects exactly in your json crate.
Right now, the only obvious way is to first convert to/from f64, which loses precision.

Related issue: https://github.com/maciejhirsz/json-rust/issues/140

Related issue: #140

Also my issue, but I filed both for completely different reasons :)