Provide account Id to traits for burn and mint methods

Caller must not be the account in question for mint and/or burn methods

This is incompatible with ERC20's burn/mint methods and PSP22 is following that standard.
Secondly, your implementation allows for burning someone else's tokens. For example, I could burn your USDT tokens effectively "robbing you".

Recall that the users are meant to make a custom implementation that derives this as you mentioned in the README.md and they are directed to use allow only one "owner" to call that method successfully.
The closest mint() in ERC-20 standard (as also implemented by OpenZeppelin) is an internal method _mint() that takes two arguments similar to those provided here - think also of a use case where an external contract has the ability to mint tokens of a PSP22 token to a given account as per business logic for the given dApp.
Just saying, though.


GetFunctionAppHostKeysArgs should take Input instead of string

I'm trying to setup a situation in which I can provision a Function App and pull its hostkey for use in configuring some other resource in the same stack. I think GetFunctionAppHostKeys can be used to achieve this. However, it seems like the GetFunctionAppHostKeysArgs type expects strings for the resource group name and the functionApp name. This means that I cannot pass values of type Output<string> into the args.. This is problematic since a lot of values that I work with in Pulumi are of type Output<T>. Can I get some guidance on this?

The typical way to handle this is to use Apply on the Output<string> and call GetFunctionAppHostKeys inside the Apply, where the value will be a string.

I suppose that's true. Is there a concern it could get unwieldy to be using Output.Apply() all over the place?
Anyway, I ended up doing this to set things up:
// get node function info
var hostKeysArgs = Output
    .Tuple(functionApp.Name, resourceGroup.Name)
    .Apply(t => new GetFunctionAppHostKeysArgs()
    {
        Name = t.Item1,
        ResourceGroupName = t.Item2
    });

var hostKeys = hostKeysArgs.Apply(async (x) => await GetFunctionAppHostKeys.InvokeAsync(x));
var defaultFunctionKey = hostKeys.Apply(result => result.DefaultFunctionKey)

For posterity, there's now a cleaner way to do this:
var defaultFunctionKey = GetFunctionAppHostKeys.Invoke(new()
{
    Name = functionApp.Name,
    ResourceGroupName = resourceGroup.Name,
}).Apply(result => result.DefaultFunctionKey);


Added PDF malware Detection Pipeline

Related Issues or bug

Issue : #198

Fixes: #198
Proposed Changes
Pipeline is created and usage and info is mentioned in readme file
Additions:

Model Training notebook
Pdf feature extraction notebook
Data processing and model prediction notebook
Dataset used
Trained Model
Readme.md

Additional Info

Anything related Issues

Screenshots

Original
Updated

original screenshot
**updated screenshot **

@DarshAgrawal14 can you please show results here and also attach in the readme file


Request to service failed for Sagemaker endpoint creation

Hi,
I'm trying to enable llama2 70b chat, I added the configuration below to aws-genai-llm-chatbot-stack.ts but the cloudformation fails during endpoint creation (model and config went fine) with the error: Request to service failed. If failure persists after retry, contact customer support.
It works fine if created from sagemaker studio.
  const llama2chat = new SageMakerModel(this, 'LLamaV270bChat', {
      vpc: vpc.vpc,
      region: this.region,
      model: {
        type: DeploymentType.ModelPackage,
        modelId: 'meta-textgeneration-llama-2-70b-f',
        instanceType: 'ml.g5.48xlarge',
        packages: (scope) =>
          new cdk.CfnMapping(scope, 'Llama2ChatPackageMapping', {
            lazy: true,
            mapping: {
              'eu-west-1': { arn: 'arn:aws:sagemaker:eu-west-1:985815980388:model-package/llama2-70b-f-v4-38616f307d8b3fcebba49bd88e19888c' }
            },
          }),
      },
    });
    // Make model interface aware of the sagemaker endpoint and add the necessary permissions to the lambda function
    langchainInterface.addSageMakerEndpoint({
      name: 'LLama2-70b-chat',
      endpoint: llama2chat.endpoint,
    });

Do you have any suggestion on what could be the issue? Thank you

@calcac The error could be caused by a number of things (such as account limitations, deploying with a non-existing role) but it is hard to debug without additional information. You can check the reason for failure in the SageMaker Console or by checking the FailureReason field when running describe-endpoint with the AWS CLI.

I think this failed for me becauset he mapping was tied to the eu-west-1 region. I am looking for hte mapping in the us-east-1 region.

It seems we need access to a publicly accessible model-package in the deployed region. I am looking for the us-west-2 one. Is there a documented list?

I am facing the same issue for eu-west-1 region when trying to deploy Llama2-70b-chat, getting the error Request to service failed. If failure persists after retry, contact customer support. in the FailureReason after checking the endpoint with describe-endpoint. Code is very similar to @calcac one:
const llama2chat = new SageMakerModel(this, 'LLamaV2Chat', {
      vpc: vpc.vpc,
      region: this.region,
      model: {
        type: DeploymentType.ModelPackage,
        modelId: 'meta-LLama2-70b-chat',
        instanceType: 'ml.g5.48xlarge',
        packages: (scope) =>
          new cdk.CfnMapping(scope, 'Llama2ChatPackageMapping', {
            lazy: true,
            mapping: {
              'eu-west-1': { arn: 'arn:aws:sagemaker:eu-west-1:985815980388:model-package/llama2-70b-f-v4-38616f307d8b3fcebba49bd88e19888c' },
            },
          }),
      },
    });
    langchainInterface.addSageMakerEndpoint({
      name: 'LLama2-70b-chat',
      endpoint: llama2chat.endpoint,
    });

I cross checked the Model Package ARN is the correct one via deploying the model via SageMaker Jumpstart hub. As stated in this issue, deploying 13b works fine.

Llama2 70b model package is not available to pull outside SageMaker JumpStart environment at this time. You can use the HuggingFace model and deploy it with HF TGI container. Below code snippet worked for me -
const Llama270bChat = new SageMakerModel(this, 'Llama270bChat', {       vpc: vpc.vpc,       region: this.region,       model: {         type: DeploymentType.Container,         modelId: 'meta-llama/Llama-2-70b-chat-hf',         container: ContainerImages.HF_PYTORCH_LLM_TGI_INFERENCE_LATEST,         instanceType: 'ml.g5.48xlarge',         containerStartupHealthCheckTimeoutInSeconds: 600,         env: {           SM_NUM_GPUS: JSON.stringify(8),           MAX_INPUT_LENGTH: JSON.stringify(2048),           MAX_TOTAL_TOKENS: JSON.stringify(4096),           MAX_BATCH_TOTAL_TOKENS: JSON.stringify(8192),           HF_MODEL_ID: 'meta-llama/Llama-2-70b-chat-hf',           HUGGING_FACE_HUB_TOKEN: 'hf_xxxxxxx',         },       },     });


[ZoneTelechargement] Add support for Streaming links

The bridge retrieves Streaming links now. It permits to list only
Direct Download Links, Streaming Links or both. The existing feeds will
show both ; this prevents to break the existing feeds.
To retrieve Streaming links, an additionnal HTTP request is necessary,
as the unprotected URIs shows only Streaming or Direct Download links/

This commit follow your suggestion !

Looks like I missed it my notification list
gj @sysadminstory !


feature: SSR

Since the DOM is used directly, SSR does not work properly.
https://github.com/konstantinmuenster/lexical-floating-menu/blob/9073b6bdfa18eb1ead8eb0a8510396bb75954f6b/src/FloatingMenuPlugin.tsx#L14
https://github.com/konstantinmuenster/lexical-floating-menu/blob/9073b6bdfa18eb1ead8eb0a8510396bb75954f6b/src/FloatingMenuPlugin.tsx#L96-L111

I opened a PR #6 , can you check and merge it? I saw that the repository has a github action, so I update the library's version. If the npm token is still valid, The merged code should be automatically released.


Clarify recommended ordering of groups, even without rustfmt support?

There's an original issue, https://github.com/rust-lang-nursery/fmt-rfcs/issues/24, which discussed imports and ordering of imports.
It was closed with https://github.com/rust-lang-nursery/fmt-rfcs/pull/129, but that pull request seems to only address the part of the issue which rustfmt can currently format (ordering within import groups).
I'm particularly partial to the ordering stated in https://github.com/rust-lang-nursery/fmt-rfcs/issues/24#issuecomment-252161813. Specifically, imports should be split into at least three groups, consisting of:

imports from 'std'
imports from external crates
imports from within the same crate

There don't seem to be any major objections to this in #24 - the only problem is that rustfmt doesn't (or didn't at the time) have enough information to enforce this.
If a PR were made, could fmt-rfcs take stance on this issue and recommend these three groups?
If not, does anyone know a more appropriate place where this convention could be established?

I was looking for the same functionality from rustfmt. I don't believe this was ever implemented, was it? Given the lack of comments, I guess this slipped through, and won't be considered anymore for a 1.0 release? Is this something that can be added later?
I believe this comment by @alexcrichton is solved with the new import rules in Rust 2018, right?

I imagine it could be hard for rustfmt to distinguish between internal/external crate imports, however :(, so it may not end up making it all the way through.

If I recall correctly, it was a conscious decision to not re-order import groups as there was no consensus?
https://github.com/rust-lang/rfcs/blob/master/text/2437-rustfmt-stability.md does allow for some formatting changes in minor version bumps so this could be included later.

Understand why folks would like some prescriptions for this, but I don't see this ever coming to any kind of consensus and rustfmt simply won't have sufficient information to be able to do it well/cover everything.
We have introduced a new(ish), unstable, config option in rustfmt called group_imports that provides a non-default variant to support that std/external/crate regrouping. I'm skeptical that many (if any) other substantive groupings and variants will be possible, but motivated users should feel free to experiment and submit a PR to rustfmt with new variants/groupings for that option if they'd like something different

The group_imports option works great, thanks for adding it!
Is there an issue to track stabilising the option? I'm not in any rush, especially as you can configure rust-analyser to group imports, and to use nightly rustfmt, just curious as to how features progress from rustfmt nightly -> stable.

The group_imports option works great, thanks for adding it!
Is there an issue to track stabilising the option? I'm not in any rush, especially as you can configure rust-analyser to group imports, and to use nightly rustfmt, just curious as to how features progress from rustfmt nightly -> stable.

https://github.com/rust-lang/rustfmt/issues/5083
https://github.com/rust-lang/rustfmt/blob/master/Processes.md#stabilising-an-option
Stabilization of options is a different beast than the standard propagation of changes (config options or otherwise) from nightly -> beta -> release.
To be fully transparent, there's a number of outstanding issues afflicting the various import related options, and I doubt any of them will be candidates for stabilization any time soon


Disable bar middle circle on the right side

please how can i disable right bar, who have been add on latest update?
(Changelog v5.1.8- second point)

Duplicate of #101


SDK diagnostic data is missing when generate_diagnostic_data is called via execute_command API

It seems to work through the CLI and swift uniffi (tested on RN iOS). Could it be a limitation of Flutter? It can be a fairly large string response

It seems to work through the CLI and swift uniffi (tested on RN iOS). Could it be a limitation of Flutter? It can be a fairly large string response

@dangeross CLI implementation calls generate_diagnostic_data directly, when it comes to uniffi, I believe you're calling generate_diagnostic_data directly as well. The issue is when this command is called via execute_command / execute_dev_command API's.
See implementation for missing generate_sdk_diagnostic_data call.

@erdemyerebasmaz I tested via execute_dev_command

Ignore me, I misread the issue.


Unify the returned type of validate

Change the returned type of validate as list.

@keeprocking Can you publish the version? 😁

Sure thing but not right now. Will do it today.

Sorry for making you wait.
0.1.3 is on pypi.

thx


create sysu.txt

create sun yat-sen university txt. offical website: http://www.sysu.edu.cn/2012/en/index.htm

I am sorry, I have to close this request without merging, because you requested to add a non-existent domain to this repository:
$ host sysu.edu
Host sysu.edu not found: 3(NXDOMAIN)

Please ensure you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information. Thank you for the understanding!


Add no-std and baremetal features

This is an ongoing attempt at addressing #131. Heavily based on this fork. cc @chrysn @malishav

Adding a baremetal and a no_std feature is contrary to the addititvity of Cargo features. If there is an actual need for std (for #131 I don't think we need an extra feature, it can be no_std and no_alloc all the time), and it's on by default now, it should become a default feature "std", so that all dependencies that are themselves no_std would use this with no-default-features, but as soon as any dependent crate needs std, std is in.

Thanks for the feedback.
Before I spend more time on this, I would like to hear what the maintainers think of addressing this issue.

Hi!
Thanks for the patch, it looks good to me. In my opinion, making it no_std is a good step forward, but happy to hear other views too.
I wanted to ask whether it would be possible/make sense to enable it for psa-crypto too.
Also, the one thing I'd like added is some mention in the README about the new features. :)

Thank you @ionut-arm.
Regarding psa-crypto, it seems to already be no-std except when using the std feature (which I think is more like what @chrysn was proposing to have it working).
In addition, I realized I need some extra build flags to be passed to mbedtls when building this in no-std mode for an embedded target (nRF52840). Unfortunately, it requires patching mbedtls. I added a patch and the required logic in build.rs, but I am still not sure how general this solution is, i.e. will others wanting to build in baremetal configuration need this same patch? (cc @malishav)


Routing error with Attribute error if coupling_map is None

Information

Qiskit Terra version: main
Python version:
Operating system:

What is the current behavior?
All the routing passes StochasticSwap, SabreSwap (after #7111 ), LookaheadSwap, and BasicSwap all enable you to initialize the pass with coupling_map=None but when you call run() on the pass they all fail with the same attribute error:
AttributeError: 'NoneType' object has no attribute 'physical_qubits'

This doesn't come up in the preset pass managers because they skip the execution of routing passes if the coupling_map is not set.
Steps to reproduce the problem
from qiskit.circuit.random import random_circuit
from qiskit.transpiler.passes import StochasticSwap, SabreSwap
stoch = StochasticSwap(coupling_map=None)
qc = random_circuit(5, 5)
stoch(qc)

What is the expected behavior?
Either the pass fails with a TranspilerError describing that routing can't be run without a coupling map, or we simply return the dag because without a coupling map there is no routing to be done so it should be a no-op.
Suggested solutions
Fix the logic in the routing passes to handle coupling_map=None

Hi,
I would like to attempt to resolve this issue.
Best,

@mcbennet: in case you didn't see, the issue was assigned to you (I don't think you get notified).


Corr. link

A correction so that spaces are replaced by underscores ( _ ), and not + .

Examples:

https://fr.wikipedia.org/wiki/Spécial:CentralAuth/Mr+Tortue DOESN'T WORK
https://fr.wikipedia.org/w/index.php?title=Spécial%3ACentralAuth/Mr+Tortue WORK

Will merge and deploy. Thanks!


Test ManageIQ w/Rails 6

Currently only updates the Gemfile.  The PR will most likely be part of a long running effort, and can be used to track all of the necessary changes for the Rails 6 effort.
Rails 6 PRs

[x] https://github.com/ManageIQ/manageiq/pull/20778
[x] https://github.com/ManageIQ/manageiq-gems-pending/pull/503
[x] https://github.com/ManageIQ/manageiq-schema/pull/531
[x] https://github.com/ManageIQ/inventory_refresh/pull/95
[x] https://github.com/ManageIQ/manageiq-postgres_ha_admin/pull/23
[x] https://github.com/ManageIQ/activerecord-id_regions/pull/18
[x] https://github.com/ManageIQ/manageiq-providers-openstack/pull/663
[x] https://github.com/ManageIQ/manageiq-providers-lenovo/pull/322
[x] https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/246
[x] https://github.com/ManageIQ/ovirt_metrics/pull/35
[x] https://github.com/ManageIQ/vmware_web_service/pull/90
[x] https://github.com/ManageIQ/manageiq-ui-classic/pull/7481
[x] https://github.com/ManageIQ/manageiq-api/pull/963

Current Error
$ bundle exec rspec
DEPRECATION WARNING: Single arity template handlers are deprecated. Template handlers must
now accept two parameters, the view object and the source for the view object.
Change:

#Hamlit::RailsTemplate:0x00007f8ed68b2bc8.call(template)
To:
#Hamlit::RailsTemplate:0x00007f8ed68b2bc8.call(template, source)
(called from <top (required)> at ~/code/redhat/manageiq/config/environment.rb:5)
** Using session_store: ActionDispatch::Session::MemoryStore
DEPRECATION WARNING: Single arity template handlers are deprecated. Template handlers must
now accept two parameters, the view object and the source for the view object.
Change:
#ActionView::Template::Handlers::RJS:0x00007f8ecf616cb8.call(template)
To:
#ActionView::Template::Handlers::RJS:0x00007f8ecf616cb8.call(template, source)
(called from <top (required)> at ~/code/redhat/manageiq/config/environment.rb:5)
** ManageIQ master, codename: Kasparov

An error occurred while loading spec_helper.
Failure/Error: require 'rspec/rails'
TypeError:
superclass mismatch for class TestSession
~/.gem/ruby/2.6.3/gems/actionpack-<IP_ADDRESS>/lib/action_controller/test_case.rb:179:in `module:ActionController'
~/.gem/ruby/2.6.3/gems/actionpack-<IP_ADDRESS>/lib/action_controller/test_case.rb:13:in `<top (required)>'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
~/.gem/ruby/2.6.3/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
./spec/spec_helper.rb:11:in `<top (required)>'
No examples found.
Finished in 0.00005 seconds (files took 8.53 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

This has been merged.  Closing.

This has been merged.  Closing.


Order of addition matters for dataset operator==

Both Variable and Dimensions also overload op ==.
Adding new test to test_dataset.cpp
TEST(Dataset, equality) {
  Dimensions dimsXY;
  dimsXY.add(Dim::X, 2);
  dimsXY.add(Dim::Y, 2);
  Dimensions dimsYX;
  dimsYX.add(Dim::Y, 2);
  dimsYX.add(Dim::X, 2);
  Dataset d1;
  d1.insert(Data::Value, "xy", dimsXY);
  Dataset d2;
  d2.insert(Data::Value, "yx", dimsXY);
  ASSERT_EQ(d1, d2);
}

Order is important. We should either (1) test explicitly for this as above, or (2) change to Dataset::operator==(const Dataset&) operator to apply sorting before comparing the above collection of objects.

I think there are several separate questions here:

Should datasets with identical variables but different variable order be the same? Definitely! I agree this is a bug, the order should not matter.
Should variables that are identical after transposition be considered identical? Sounds useful, but I actually think in practice this could cause too much surpising behavior. (I assume your example has a typo, you intended  to use dimsYX in d2?).
Should variables with different names ("xy" and "yx" in your example) be considered equal? I would say no.

I agree with your last point and yes typo in example


GH-1090: added IllegalArgumentException when mimeTypes isEmpty in FileFormat.java

GitHub issue resolved: #1090
Briefly describe the changes proposed in this PR:
Instead of silently failing with the assert check previously used, an empty mimeType list now throws an IllegalArgumentException
assert !mimeTypes.isEmpty() : "mimeTypes must not be empty"

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[x] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Also looks as if the Java formatting checks don't like something in your PR. You may want to run a mvn process-resources on your branch before committing/pushing.

Fixed the formatting issues and added the upgraded tests @jeenbroekstra.

@Sanchit-Trivedi I just noticed this is targeted against the develop branch. As this is a bug fix: could you rebase it against the main branch instead?

@jeenbroekstra
I did run the mvn process-resources and got a Successful message after running the command. Still, the Github actions fail.
Is there something else I need to do before running this command?
Also will this require rebasing ? I created the fork from the main branch only but just targeted the PR to the develop branch

At a guess: did you format and then make some other changes? It seems to complaining about your test code this time.
And no need to rebase if you started off main, we can just retarget this PR.

Marked this as stale to signal that the PR hasn't been active for a while and that we should consider closing it.


Go-ws data streaming SDK for review

Go implementation of data streaming API.
Coverage:

Implementation of all message types
Message processing handled by uniform InvokeFunction for all message types
Versioning & configuration of the SDK
Documentation of the message types in the InvokeFunction examples.

Connection handling:

Basic methods implemented: Open, Close & Reset
Reconnect messages are handled through a custom reset InvokeFunction
The basic idea is to use a custom InvokeFunction to trigger an event or signal to another event listener or go channel that will handle the complete re-connect based on the specific requirements of the integration. For simple cases or testing, a hard connection reset without buffering can be used.

Heartbeat handling

The underling gorilla websocket handles the ping / pong. No custom implementation provided.
Again, a custom InvokeFunction  can be provided upon receiving a heartbeat message although its a closure with no access to its outer scope.

Example code (in main)

Sample sdk usage
Sample invoke functions
Sample utils to speed up development

Known issues:

Not thread-safe
Limited testing.
Requesting volume data closes connection with error 1006.

The folder x_test contains an isolated test to replicate the volume data issue. It is unclear if the free API key can request volume data, or submitted hello message is valid , or if there is any other cause at play. It would be great if someone with more detailed knowledge could run a test maybe with a proper API key & a different configuration to resolve this issue.
Thank you for considering this PR!
Marvin Hansen,
July, 6, 2021

Closed to resolve issue #110


Error Submitting Heartbeat Data: 400 Bad Request

Describe the bug
I've been using Wakapi for a while now, and love all of the metrics it provides :) Thanks for all of your hard work! I try to avoid making bug reports, but I've reached a dead end :(
Unfortunately, as of around a week ago it stopped accepting heartbeats, resulting in no metrics. The container logs show the following (first request to demonstrate that auth and URL are correct, second request to represent the issue):
2024-03-07T10:59:21.422553409Z [INFO ] [request] status=200, method=GET, uri=/api/users/current/statusbar/today, duration=11.600352ms, bytes=431, addr=IP_HERE, user=wolveix
2024-03-07T10:59:23.641782719Z [INFO ] [request] status=400, method=POST, uri=/api/users/current/heartbeats.bulk, duration=1.986689ms, bytes=24, addr=IP_HERE, user=wolveix

I tried adding debug = true to my ~/.wakatime.cfg file to no avail. I'm not too sure how to go about debugging this further, as the local logs in ~/.wakatime/wakatime.log only contain the following:
{"caller":"cmd/run.go:341","file":"/Users/PATH_REDACTED/main.go","func":"cmd.runCmd","level":"error","message":"failed to run command: sending heartbeat(s) failed: bad request at \"https://DOMAIN_REDACTED/api/users/current/heartbeats.bulk\"","now":"2024-03-07T12:32:55Z","os/arch":"darwin/arm64","plugin":"intellijidea/2023.3.4 intellijidea-wakatime/14.3.11","time":1709814755.05,"version":"v1.90.0"}

Please let me know if I can provide any further useful information! Hopefully it's a simple fix, though I'm curious as to what may have caused this. I may have updated the Docker container around the time that the error started occurring, though I can't be sure.
System information

Wakapi version: v2.10.5
Operating system

Docker: ghcr.io/muety/wakapi:latest

Database: Postgres
IDE: JetBrains IDEA Ultimate
IDE Plugin: WakaTime v14.3.11

Thanks a lot for reporting this! I'm traveling at the moment, but will look into it as soon as I get back in a few days.

Looks like I need your help to further debug this. Can you please do me a favor an try the following?
1. Send a crafted request and check the response
Use curl / Postman / an HTTP client of your liking to send a request with the following JSON body to https://YOUR_SERVER/api/users/current/heartbeats.bulk.
[{
    "entity": "/tmp/foo/bar/baz.go",
    "project": "Wakapi Debugging",
    "language": "Go",
    "is_write": true,
    "type": "file",
    "category": null,
    "branch": null,
    "time":<PHONE_NUMBER>.113417
}]

Please replace the time field with the output of:
python -c "import time; print(time.time())"

See if that works and, if not, what the response text is.
2. Debug wakatime-cli request
Create a request basket at https://rbaskets.in/web, copy its URL, temporarily set it as the api_url inside ~/.wakatime.cfg, do some coding and then investigate the requests. Possibly send me a link to the basket or, if you want to redact some parts, send the received requests bodies.
3. Provide additional info

Is your Wakapi server running in (much) different time zone than your PC? Please post the output of running date in- and outside the container.
Can you imagine anything special about the heartbeats (such as weird Unicode characters in file paths or something)?

Hah, I started filling out a full response to you (with the cURL request showing invalid heartbeat object and such). It was entirely down to the timezone of the server! It seems that when my provider recently migrated the server to new infra, the system time was wrong. While it's 13:52 where I am (in the UK), the server (also in the UK) was reporting 12:01. I've configured NTP, re-deployed the Docker container and everything is working! I'm terribly sorry for the hassle, but I really appreciate your quick and thorough support.
Is there any way to retroactively obtain the lost heartbeats from the past few weeks?

Glad you got it sorted!
The WakaTime CLI keeps heartbeats stored locally as long as there was an error sending them to the server, so there might be a chance they are still not synced. You can check with
~/.wakatime/wakatime-cli-linux-amd64 --offline-count

Otherwise, there's no way to get them back, unfortunately.


"Show more" feature for related and nearby items

Have links the user can click to load a bunch of related/nearby items.

Also needed for identifiers.


Section content as sub sections as opposed to bolded paragraph.

First, really neat solution you have put together. Came across it by chance while I was actively using ChatGPT to achieve similar (just in a much more manual fashion).
Now, I would like to see if section content could be treated as sub sections/pages instead of just bolded paragraphs. Example
For example, currently I get:
# Course title

## Section title

**Subsection 1 title**

Whatever content...

**Subsection 2 title**

Whatever content...

### Quiz

While I would like:
# Course title

## Section title

### Subsection 1 title

Whatever content...

### Subsection 2 title

Whatever content...

### Quiz

That is certainly very possible and even can be a setting.


Make Beaker more secure on multiuser systems

We should never allow untrusted connections on localhost.
It should be possible to do this without interfering with the UX we have now.
To achieve this we can combine part of the public-server option (the part that asks for a password) with some extra code, so that when we start up the web browser we do so via a private HTML file that has the password in it, and fills out the form automatically.  we just to to make public-server work with <IP_ADDRESS>.

aiming to include this in electron/native version.


How to recover your paper "HyperPower: .." in DATE 2018?

Heollo,
I have read your paper which is very valuable and enlightening.
I installed the software package follow your instructions, and then I ran the run_tool.sh script. After a day and night, sadly I can not find any training procedure except for the massive same content python files.
Can you give me more detailed training instructions about it ?

@MrLinNing this could be due to compatibility issue (our init code relied on older spearmint etc versions). I will try to reproduce the issue and get back to you promptly.


Offer to navigate to implementation(s) of a function

Currently navigation using VS commands ends at interfaces. A "navigate to implementation(s)" action on function definitions would be great.

like it

Duplicate of #6209 (even though this issue is older). This now exists in the form of Go To Implementation. You can view the command via the Command Palette in VS Code.


StbImage is undefined

Hey :wave:
I was trying to fidget with Nx and Axon today but it seems like the new 0.1.6 release is broken (Released just today) due to a missing struct called StbImage.
== Compilation error in file lib/scidata/caltech101.ex ==
** (CompileError) lib/scidata/caltech101.ex:153: StbImage.__struct__/0 is undefined, cannot expand struct StbImage. Make sure the struct name is correct. If the struct name exists and is correct but it still cannot be found, you likely have cyclic module usage in your code
    (elixir 1.13.4) expanding macro: Kernel.|>/2

Thank you for the great work :+1:

My bad, I should have caught this and Elixir should have a better mechanism for testing compilation without optional dependencies. A new version is out!


Allow disabling IMDS via env vars

This allows customers to disable fetching credentials from IMDS by
setting AWS_EC2_METADATA_DISABLED to true.

The reason I put it there was to make sure that the environment variable disables all IMDS features. Right now we aren't using that class for anything but credentials, but that might not be the case in the future.

Just to reiterate, I stand by my original feedback.  Curious to see what others think.
cc @kyleknap

Capturing offline discussions, while I'm personally not a fan of this and would prefer this is done at the credential level, given this API is not public, it still has the same end result for users.  I think we should take a serious look at changing this if we expose a general IMDS interface.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@3d636b9). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop    #1394   +/-   ##
==========================================
  Coverage           ?   80.62%
==========================================
  Files              ?       87
  Lines              ?    12129
  Branches           ?        0
==========================================
  Hits               ?     9779
  Misses             ?     2350
  Partials           ?        0

Impacted Files
Coverage Δ

botocore/utils.py
98.22% <100%> (ø)

Continue to review full report at Codecov.

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


Missing SDF files in sdf/1.8/CMakeLists.txt

I've been toying with this repo because I want to create type-annotated python bindings for the SDFormat. Both for validation and for a better time while programming (IDE auto-completion). To make a long story short, I am generating python stub files from the schemas generated during this repo's build and the stub generator (external: xsdata) warns that a few class schemas could not be found for v1.8 (haven't tested others yet).
For some warnings the cause seems to trace back to CMakeLists.txt which is missing 3 SDFs:

lidar.sdf
air_pressure.sdf
particle_emitter.sdf

which leads to missing *.xsd files. Adding the respective lines solves this issue as expected and generates the missing *.xsd files.
Is this intentional or a bug? If the latter, I can submit a PR.

Nice catch, it's unintentional, these are the latest files added and were simply forgotten.

I want to create type-annotated python bindings for the SDFormat.

Nice! Let us (and the community) know when you're done, we'd love to try it out!


make shortcut reports work (again)

To test this, run
docker run --name=foo --rm -ti alpine sleep 10

On master it can take several seconds for the container to appear on the topology view, and then several seconds for it to disappear when it stops.
After the first commit, it disappears immediately when stopped, but still takes time to appear. The latter is cured by the 2nd commit.
Fixes #3113.
In the process I discovered #3120.

Both these changes do have a performance impact.

The fix to Report.Copy() means shortcut reports now trigger delivery via the special shortcut path, and a render in the app (as they should).
The fix to updateContainerState results in more shortcut reports being delivered - previously they'd only be sent for containers when they were stopped, now they are sent on all state changes (as they should). This results in more report processing in general.

If we deem these too costly then we should ditch shortcut reports altogether, since in their current state they are pointless.


Remove GraphQLAny scalar type

Coverage decreased (-0.001%) to 93.776% when pulling 211074be7e1a4d0a60fef47bdbe3cec76be72416 on remove-graphql-any-type into 7d2845b9597c7fde289d5d18f901c67724fbc2b8 on refactor-schema-graph.


Consider implementing top-level .keys() method as pass-through for tree.keys()

This seems reasonable since we already provide top-level __getitem__ as a pass-through as well.

For that matter, maybe the AsdfFile class should just be the tree, although this would be a pretty big API change. It would be possible to provide backwards compatibility, though. Maybe for 3.0.


Fix OpenAPIKey and MongoDBService class

Hello @LuceCarter, I've fixed some things in the project, since wasn't even building.

Add the OpenAPIKey string in appsettings
Remove the OpenAPI instance that hasn't been used
Add inside the aggregation the Poster outcome, because the movies wasn't showing

Obrigada @jhomarolo! I think my forks got out of sync so you've saved me a job transitioning over the changes! 🧡


update to go1.19.4, go1.18.9

Includes security fixes for net/http (CVE-2022-41717, CVE-2022-41720), and os (CVE-2022-41720).
These minor releases include 2 security fixes following the security policy:

os, net/http: avoid escapes from os.DirFS and http.Dir on Windows
The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permitted access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") would open the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.
In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.
The behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.
This is CVE-2022-41720 and Go issue https://go.dev/issue/56694.

net/http: limit canonical header cache by bytes, not entries
An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests.
HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.
This issue is also fixed in golang.org/x/net/http2 vX.Y.Z, for users manually configuring HTTP/2.
Thanks to Josselin Costanzi for reporting this issue.
This is CVE-2022-41717 and Go issue https://go.dev/issue/56350.

View the release notes for more information:
https://go.dev/doc/devel/release#go1.19.4
And the milestone on the issue tracker:
https://github.com/golang/go/issues?q=milestone%3AGo1.19.4+label%3ACherryPickApproved
Full diff: https://github.com/golang/go/compare/go1.19.3...go1.19.4
The golang.org/x/net fix is in https://github.com/golang/net/commit/1e63c2f08a10a150fa02c50ece89b340ae64efe4

Could someone give the rocky-linux CI a kick? I guess it's not related; vagrant had some issues?
from /usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.7.0/lib/vagrant-libvirt/action/set_boot_order.rb:80:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.7.0/lib/vagrant-libvirt/action/create_network_interfaces.rb:190:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.7.0/lib/vagrant-libvirt/action/create_networks.rb:93:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.7.0/lib/vagrant-libvirt/action/share_folders.rb:22:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.7.0/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:21:in `call'

it's re-running now @thaJeztah

Happened again; re-started, but if it still fails in vagrant up deep in Ruby, I think we can safely ignore for this particular PR :)

The rockylinux/8 image on Vagrant Cloud was updated recently, that would be the reason of the failure
https://app.vagrantup.com/rockylinux/boxes/8


breakpoint not hit in node 5.2

@jrieken this bug targets the problem #1264 for node 5.2

This was a problem with node 5.2.
Breakpoints are hit in node > 5.2.


WIP: top up feature

This looks to be a good start in this direction, but I've encountered a few bugs testing this out:

[ ] If the validator has deposited, but has bot been processed by the beaconcha.in queue, it technically doesn't exist in eth2 yet and therefore the second request (to the the effective balance) doesn't return anything for that address which causes the page to crash. Instead if nothing is returned for a given address, we should not allow more deposits.
[ ] If there is only 1 deposit for a given eth1 address, then beaconcha.in doesn't return a length 1 array, but returns the object inside. This also causes the page to crash.

This looks to be a good start in this direction, but I've encountered a few bugs testing this out:

[ ] If the validator has deposited, but has bot been processed by the beaconcha.in queue, it technically doesn't exist in eth2 yet and therefore the second request (to the the effective balance) doesn't return anything for that address which causes the page to crash. Instead if nothing is returned for a given address, we should not allow more deposits.
[ ] If there is only 1 deposit for a given eth1 address, then beaconcha.in doesn't return a length 1 array, but returns the object inside. This also causes the page to crash.

As per our discussion the other day, let's get this merged! 💪
I'm happy with how it works now save two items:

The linting error about React Hook React.useMemo missing a dependency (showDepositVerificationWarning): ∫https://github.com/ethereum/eth2.0-deposit/pull/291/files#diff-f810da4dbf04ce49a49c3ae5db5acff4dee8737c515068c44945b393fbceac58R126
re-enable the validity checks on the submit button: https://github.com/ethereum/eth2.0-deposit/pull/291#discussion_r555918723

@CarlBeek I've made the changes you requested & removed a few unnecessary packages from this PR. I believe it's ready to go - please merge if you agree! Thanks.


modify setup method of Board object

Using setPiece method to locate the Piece

Wait on merging this PR! Let's wait for Tuan Anh finishing the setPiece method in Cell.py


Add SonarCloud Checking

Description
Please include a summary of the change.

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

#41  👈
#40
#39
#38
#37
#36
#35
#34
main

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

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Sep 22, 12:26 PM EDT: @JackPlowman merged this pull request with Graphite.


ESP SDK

Does it matter where I pull the esp sdk?
I have been fighting my GNU gcc install this evening but I think I have it fixed.

I strongly suggest using the ESP NON OS SDK that is referenced in the project.  As far as the rest of it, I usually use esp open sdk.

I cannot get the code to compile on my Mac.  The make file is looking for a file in sep-open-sdk
/bin/sh: /Users/MarkIngle/esp-open-sdk/xtensa-lx106-elf/bin/xtensa-lx106-elf-gcc: No such file or directory
Xcode is on my Mac too and I thing its causing a problem with the compile.....

Could you provide a link to the ESP open sdk you are using as referred to in your make file?

Well I have conquered the compile demons on my Mac and burned the firmware on to the ESP.  Where did you get the line driver and manchester chip from?

I /think/ I was using the ISL3177

Thanks!  I found a Bel fuse S558-5999-R3 magnetics chip on a old 3Com net card....should be perfect for the job!

Oh you meant the magnetics!


Feature request: set generator

Is there any way to set generator on iOS 15.7?
I tried
https://github.com/Cryptiiiic/dimentio
https://github.com/opa334/TrollNonce
but no one works
I want to upgrade my iPhone XR to iOS 16 using my shsh blob

shshd and dimentio output
Failed to initialize IOSurface primitives, add "IOSurfaceRootUserClient" to the "com.apple.security.exception.iokit-user-client-class" dictionary of the binaries entitlements to fix this. KRW plugin /var/jb/usr/lib/libkrw/libkrw-plugin.dylib did not provide functions it purported to provide

That error only refers to kcall, kernel read/write should still work. The actual issue is probably that dimentio is not updated for iOS 15.7.
I checked and it works fine for me on A15, 15.1.1 and A12, 15.4.1.

i had the same problem


Make BSP task processing more resilient

Since BSP clients can handle incomplete result lists (e.g. they request a task on 5 build targets, but only receive the results for 3 of them), we just don't include the failed targets in the final request result. This is also what sbt and Bloop does to handle failures.
In addition, we send a log message to the server, so the failure doesn't go unnoticed.
Fix: https://github.com/com-lihaoyi/mill/issues/3011
Pull request: https://github.com/com-lihaoyi/mill/pull/3022

How do I test it?


Two issues with the build

I couldn't find how to load this with observable's require(), and had to run it through a local instance of packd to get a usable format.
the package exports two methods called default and renderSelection; not sure what default is for, and I would expect to have render.

https://observablehq.com/d/6f1627b8f1f3d109

I see you solved (1) at https://observablehq.com/@unkleho/hello-d3-render ; ideally it would just be "d3-render" but it's quite usable already (as an aside, I had tried this file, but forgot to remove the /browse/ part from<EMAIL_ADDRESS>! 🙄  ).

Hi Fil,

I've just updated the package.json to have an explicit reference for unpkg to the UMD build. It should work in observable now without the crazy link!

As a total newbie to building for the D3 ecosystem, i didn't read up on best practises. I may rethink how I'm exporting the package. default is the full render function, which can actually be named anything when imported.

Great! I can't help you with the exports, the only thing I do for my own module is to copy from one of @mbostock's modules ;-)


For a nullable reference type don´t emit the ‘CannotCall…WithInvalid…’ test or omit the [DataRow(null)] case if it’s a string

Given a method like this:
public string GetFullName(string first, string? middle, string last) =>
            middle != null ? $"{first} {middle} {last}" : $"{first} {last}";

I think it should not be expected to get this test:
[DataTestMethod]
[DataRow(null)]
[DataRow("")]
[DataRow("   ")]
public void CannotCallGetFullNameWithInvalidMiddle(string value)
{
    Assert.ThrowsException<ArgumentNullException>(() =>
     _testClass.GetFullName("TestValue2088905246", value, "TestValue1083861687"));
}

Thank you for the issue!
I definitely agree, we shouldn't be emitting the 'null' case in that instance. I am in two minds about whether we should still emit the empty string and whitespace cases.
However, in this specific instance, this requires us to use Roslyn 3 - which would tie us to Visual Studio 2019 only. I do think we will be able to support both Visual Studio 2017 and 2019, but it involves implementing a mechanism where we build the core project twice - one for each level. So it's a little more involved than it might seem!
But it's definitely something that I will progress.
Thanks again for the issue

I've now implemented this in https://github.com/mattwhitfield/unittestgenerator - a new version should be out in a couple of weeks - but it will have to be a different item in the marketplace as I no longer work for SentryOne 👍

@kristofferjalen I had another look at this, and I think how it is above is backwards. If you're in a project with nullable ref types enabled, then middle is the only parameter that you would want to get [DataRow(null)] for - and you wouldn't want it for first or last. Am just fixing that in Unitverse so it's not doing stuff backwards - so just wanted to ping you to see if you agreed?

Actually, never mind. I'm obviously having a daft day. Sorry for the pointless notification!


[path_provider] Cast NSInteger to long

For arm32, arm64 compatibility

LGTM. In the future, can you please push your changes to a public fork of flutter/plugins, instead of a branch on the flutter/plugins repo? We're trying to avoid having lots of branches on the main repo.


Regex parsing: parsing [^something] results in an unexpected automaton

I am using the python binding, library version 1.6.9.
Parsing a regex containing a negated element results in an automaton that does not seem correct.
Code:
import libmata.parser as parser
regex = "[^a]"
m_nfa = parser.from_regex(regex)

The generated automaton has five states, accepts some words with length 2, 3 and 4, and contains symbols up to the value 245, which are not standard ASCII symbols. However, when all edges with symbols above 127 are deleted, the resulting automaton is what I would expect from this regex.
I am attaching a jupyter notebook with an image of the automaton.
https://gitlab.fi.muni.cz/xstepkov/aligater/-/blob/main/notebooks/regex_parsing_mata_error.ipynb?ref_type=heads

I am sorry, this is my mistake. I did not notice that the encoding used by the from_regex function is UTF-8, not ASCII.


How to use it

First of all, the package doesn't seem it's been published:
https://www.npmjs.com/package/phantomjs-promise-es6
Second, can you please help with a small write-up how to install your library and the dependencies?
I assume I need Babel with ES7 support.
Thank you

Hello, thanks a lot for your interest in my library! It's still a work in progress; so, that's why it hasn't been published yet. I'll be working on this more in the coming weeks. When it's ready for use, I'll add detailed usage instructions to the readme and update this issue.
Thanks!

@opcodewriter, I renamed the tool to phantomjs-adapter and have since published it.
This tool hasn't seen very much usage; so, I don't know what failure conditions haven't been covered yet.
I am working on this adapter at a steady pace and am using it to test some of my other projects. But, I haven't had the chance to use it to power end-to-end testing on a web frontend.


Add clickable link to current weather source

Add a link to the current source of the weather data.  This might be a better solution than some of the other feature requests.  Make it easy for a user to click somewhere on the app in order to open a web page showing more detailed weather for their selected location.

As of now, Open Meteo does not provide a web page/app with weather forecast.
We may add support for this when we properly decouple provider and internal API/logic and add more providers.


Update rancher/helm to support 1.22

Currently, we use rancher/helm in 2 ways:

In rancher/rancher dockerfile for v1 apps,  https://github.com/rancher/rancher/blob/release/v2.6/go.mod#L17
In rancher/shell for v2 apps, https://github.com/rancher/shell/blob/master/package/Dockerfile#L2

https://github.com/rancher/rancher/issues/34054

https://github.com/rancher/helm/pull/33

Verified the following on 1.22.3-rancher 1-1 downstream clusters on 2.6.3-head and 2.6.3-rc4

v1 app deployment
v2 app deployment
v2 app upgrade


[MOVED] Add mobility data for Colombia

Background
The mobility data we currently have in place for Columbia is by specific dates in a year (e.g. 2015/02/03). Recently, we are given mobility data by day-of-week (e.g. Monday) and are informed that will be the direction moving forward.  We need to add this new dataset to our API and adjust the front-end apps (e.g. unicef/magicbox-maps and unicef/magicbox-maps-prototype to correctly fetch and visualize the data.
Task breakdown

[ ] Add the new dataset to magicbox-open-api/public/aggregations/mobility (and maybe the private server as well?). This could be as straightforward as placing a the .csv. files, which we readily have, into the said folder.
[ ] Adjust the code logic in the front-end app(s) to fetch and visualize this data. This can be broken down to sub-tasks, such as:

[x] First, add activity data as the default mobility to be visualized as soon as the app is loaded. This task is hosted at unicef/magicbox-maps-prototype#8
[ ] Add actual mobility data. This task is hosted at ... //TODO: add Vinit's PR here.

This issue has been moved to unicef/magicbox-maps-prototype#13


Fix lifecycle hook function types

Summary
Fixes #10066
Test plan
Not sure? Need some guidance.

Ideally this'd include type tests (based on #10407), but we don't have any tests for these globals, so possibly out of scope?

Added a new test file for the globals. The test _successfully fails_™ before the suggested changes, but is now passing.
It doesn't test exactly what I wanted (I wanted to test the argument types, but it's testing the function return types), but it does the job.

Wasn't sure where to put it, left it on the master's Fixes section.

Wasn't sure where to put it, left it on the master's Fixes section.

Exactly right 👍


Error when try to import the package

I try to import import { ChatOpenAI } from "langchain/chat_models";
But got an error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './chat_models' is not defined by "exports"

Hi, that error suggests you're missing "type": "module" in your package.json, you can see the full install instructions here https://hwchase17.github.io/langchainjs/docs/install

I get error  Unknown file extension ".ts" after adding "type": "module"

Same issue here. Even with "type": "module" in my package.json file, I get the error:

Package subpath './<submodule_name>' is not defined by "exports"

For whichever module is imported first. In my case, it's agents

[ERROR] 15:33:01 Error: Must use import to load ES Module: /Users/lukebechtel/localdev/lib/apps/scripts/src/agents/simple-notion-agent.ts

I ended up copying this package.json from the examples directory, and things started working again:
https://github.com/hwchase17/langchainjs/blob/main/examples/package.json
Not a viable long-term solution though.
Using the tsx packages instead of ts-node also helped me track down another issue I was facing.

@Marviel that error means that your tsconfig was setup to output CJS, see the instructions here https://js.langchain.com/docs/getting-started/install#typescript
@atulmy can you share more about your setup?
@asibilia I'd suggest opening an issue on the next-with-linaria repository. As for the peer dependencies, sadly it seems some tools in the JS ecosystem are implemented incorrectly and treat peer dependencies / dynamic imports as if they were required. There are two solutions for working with these tools (it appears nextjs is one of them?)

You can install the peer dependencies in your project
or, You can mark the peer dependencies as external in the tool config. For nextjs this would be in https://nextjs.org/docs/api-reference/next.config.js/custom-webpack-config. eg.

module.exports = {
  webpack: (
    config,
    { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack }
  ) => {
    config.externals = {
      'typeorm': 'typeorm',
      // add others here
    }
    return config
  },
}

@nfcampos
Executing:
ts-node ./src/index.ts
tsconfig:
"target": "esnext",
"module": "commonjs",

@atulmy your issue might be fixed by changing to "module": "nodenext",

Hi, we've released a new version 0.0.49 which adds a CJS build and fixes this issue.

Changing the import statement to the following worked:
import { ChatOpenAI } from 'langchain/chat_models/openai';
import { AIMessage, HumanMessage } from 'langchain/schema';
↓↓↓
import { ChatOpenAI } from '@langchain/openai';
import { HumanMessage, AIMessage } from '@langchain/core/messages';


Add support for  and  tags

Add support for <br> and <tab> tags that replace the \n and \t escape sequencies.

Added to Development Release


Call php artisan cache:clear made sidebar menu disapear forever

Version information

Laravel: v6.18.3
Voyager: v1.3.2
PHP: 7.4
Database: [Postgresql] [12]

Description

Call php artisan cache:clear made sidebar menu disapear forever.
Steps To Reproduce
Steps to reproduce the behavior:

Call 'php artisan cache:clear'
See error

See error

There is no way for us to know what's happening if you don't post the error.

I don't have any problem with the following command

Call 'php artisan cache:clear'


Playwright warnings on most pull requests

While the Playwright tests do not outright fail, they seem to be a little bit unstable and cause warnings to appear all the time:

A screenshot from one of the failing tests reveals that the interface is still empty:


Missing one of BOTBUILDER_APP_ID, BOTBUILDER_APP_PASSWORD,     LUIS_MODEL, KB_ID, QNA_KEY, QNA_URL, BING_SEARCH_CONFIG, BING_SEARCH_KEY,     TEXT_ANALYTICS_KEY, TEXT_ANALYTICS_URL, DIALOG_ANALYZER_CLIENTID, DIALOG_ANALYZER_KEY or DIALOG_ANALYZER_URL     in environment variables!

I am following the instructions for installing stackoverflow bot. I am at the npm run start but keep getting:
Missing one of BOTBUILDER_APP_ID, BOTBUILDER_APP_PASSWORD,     LUIS_MODEL, KB_ID, QNA_KEY, QNA_URL, BING_SEARCH_CONFIG, BING_SEARCH_KEY,     TEXT_ANALYTICS_KEY, TEXT_ANALYTICS_URL, DIALOG_ANALYZER_CLIENTID, DIALOG_ANALYZER_KEY or DIALOG_ANALYZER_URL     in environment variables!
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
How do I resolve this? Do I even need a key etc? The instructions seem to imply I should only need to run start and then Navigate to http://localhost:3978/ to start interacting with your bot.
Is this a known issue?

Closing this issue as we are no longer maintaining the repo for samples. The official Bot Builder Samples repo is here: https://github.com/Microsoft/BotBuilder-Samples/ for both V3 and V4 bots.


Failed to resolve: com.github.developer-shivam:crescento:1.2.0

Hi, I'm trying to add version 1.2.0 to my project, but i get this error. version 1.1.0 works fine though.

Please provide the error log.

The title is all i get!

Fixed! Please try again.

Unfortunately I still get the same error.

Copy as it is - compile 'com.github.developer-shivam:Crescento:1.2.0'

Awesome, worked. thanks

@developer-shivam in the home page the dependency is in lowercase instead uppercase

@developer-shivam please update the readme with the correction @agustinsivoplas pointed out. Will help others.

Done!


Browser support request

Browser Support Request
Browser Details:

Name: SigmaOS
Version (optional): <IP_ADDRESS>
Platform (optional): MacOS Sequoia 15.1 (24B2082)

Additional Info:

Link to the browser website: SigmaOS.com

Hello @ozer85,
Thank you for being so interested in my extension.
I have some good news – the next version of the plugin will be compatible with the Sigma OS browser.
While the extension currently works flawlessly, and the planned future features are unlikely to change this, I want to inform you that this support is somewhat experimental. My plugin is primarily designed for Chrome-based browsers (Sigma OS is powered by WebKit), so I cannot fully guarantee the functionality of all future features in this browser.
Thank you for your understanding.

@ozer85 Good news! A new version has been published in the app store.
Now you can try the extension in your favorite browser.

Thank you!


Implement our own Peek() which blocks

Fixes #48
StreamReader.Peek() just returns -1 instead of blocking, we mitigate that by using Read() which does block.

https://github.com/SteamDatabase/ValveKeyValue/pull/51

I moved BlockingStream inside the test class so it's more clear it should not be reused.


Add Rubocop

Pull Request Test Coverage Report for Build 8

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

Totals

Change from base Build 5:
0.0%

Covered Lines:
29

Relevant Lines:
29

💛  - Coveralls

Rubocop docs & gems

rubocop

rubocop docs

rubocop-rspec
rubocop-performance


TextFormatter treats anything with a dot as url

https://github.com/seattle-uat/civiform/blob/main/server/app/views/components/TextFormatter.java
We use this in static questions and it would create a link for anything "something.something".
This is especially bad for emails with a dot like<EMAIL_ADDRESS>because it would generate two links for two parts of the email.

Leyla to spend a bit of time investigating. Potential workaround by linking to contact us page instead of including an email


Review CL terms created for HCA/SCA

Note for self:
As discussed at CL editors meeting on Nov 18th 2020,

[x] review CL terms created for HCA/SCA before then: if these are grouping terms that encompass potentially heterogeneous cell types, flag them with the new subset term "location_grouping"; optionally, add a comment / xref for traceability; if added for HCA, tag with appropriate subset property. Ideas: for HCA, refer to HCAO tracker (tickets closed before Nov 2020) (DONE); search CL tracker for (closed) tickets opened by HCA curators/developers and/or with "HCA/DCP" label. For SCA, search CL tracker for (closed) tickets opened by SCA curators/developers. (Developers: Dani, Zoe, David.)

Update: potentially relevant tickets opened by David and not already included in HCA/DCP group above: #633 , #656 , #657 , #658 ; no closed tickets authored by Dani or Zoe.
=>

[x] Add subset tag "added for HCA" to all terms created for closed tickets opened by David and with label HCA/DCP
[x] Evaluate if any of them should also be flagged with subset "location_grouping"

Update: added subset tag "added_for_HCA" to 7 CL terms created by @dosumis ~February 2020.


A bug where paying for TLC in the Post Browser doesn't seem to unlock the content

Looks like this was also fixed in https://github.com/Novusphere/discussions-vue/commit/c0b9c209c71dc213b3733836e163260d584a6e5d


RuntimeError in ssml_to_speech_async

An RuntimeError occurred while calling ssml_to_speech_async of instance of SpeechToFileService.
CRITICAL: Traceback (most recent call last):
  ......
  File "E:\***\tts.py", line 17, in tts
    return provider.ssml_to_speech_async(ssml,path=path)  # type: ignore
  File "F:\ProgramData\Miniconda3\lib\site-packages\aspeak\api\api.py", line 110, in wrapper
    self._setup_synthesizer(kwargs['path'])
  File "F:\ProgramData\Miniconda3\lib\site-packages\aspeak\api\api.py", line 139, in _setup_synthesizer
    self._synthesizer = speechsdk.SpeechSynthesizer(self._config, self._output)
  File "F:\ProgramData\Miniconda3\lib\site-packages\azure\cognitiveservices\speech\speech.py", line 1598, in __init__
    self._impl = self._get_impl(impl.SpeechSynthesizer, speech_config, audio_config,
  File "F:\ProgramData\Miniconda3\lib\site-packages\azure\cognitiveservices\speech\speech.py", line 1703, in _get_impl
    _impl = synth_type._from_config(speech_config._impl, None if audio_config is None else audio_config._impl)
RuntimeError: Exception with an error code: 0x8 (SPXERR_FILE_OPEN_FAILED)
[CALL STACK BEGIN]

    > pal_string_to_wstring

    - pal_string_to_wstring

    - synthesizer_create_speech_synthesizer_from_config

    - synthesizer_create_speech_synthesizer_from_config

    - 00007FFE37F772C4 (SymFromAddr() error: 试图访问无效的地址。)

    - 00007FFE37FC76A8 (SymFromAddr() error: 试图访问无效的地址。)

    - 00007FFE37FC87A8 (SymFromAddr() error: 试图访问无效的地址。)

    - PyArg_CheckPositional

    - Py_NewReference

    - PyEval_EvalFrameDefault

    - Py_NewReference

    - PyEval_EvalFrameDefault

    - PyFunction_Vectorcall

    - PyFunction_Vectorcall

    - PyMem_RawStrdup

    - Py_NewReference

[CALL STACK END]

tts.py
from aspeak import SpeechToFileService,AudioFormat,FileFormat

provider=None
fmt=AudioFormat(FileFormat.MP3,-1)

def init():
    global provider
    provider=SpeechToFileService(locale="zh-CN",audio_format=fmt)

def tts(ssml:str,path:str):
    if provider is None:
        init()
    return provider.ssml_to_speech_async(ssml,path=path)  # type: ignore

The thing is, this error seemed to occurred randomly, and only when I created(Finished) over 20 ssml_to_speech_async instance does it occurs.
This error seems can't be catch through try

This is probably a bug in azure-cognitiveservices-speech, which I can do nothing about it.
You should open an issue in https://github.com/Azure-Samples/cognitive-services-speech-sdk .


Add section to retworkx for networkx users guide on matrix converters

This commit adds documentation to the retworkx for networkx users guide
on the differences between networkx and retworkx when it comes to matrix
generation. Right now retworkx only has an adjacency_matrix() function
which is equivalent to networkx's to_numpy_array() and returns a numpy
array of the adjacency matrix. This is different from networkx's
adjacency_matrix() function which returns a scipy sparse array (and is
just an alias for networkx's to_scipy_sparse_matrix()). Documenting
this gap is important because it's easy to get confused by these API
differences.
This difference is fundamentally because we can effeciently create numpy
arrays in retworkx by just pass a pointer to numpy with a 2d array
that was constructed natively in rust (using rust-numpy) while other
matrix formats (such as scipy sparse matrices) don't expose a C api so
to create those objects we'd have to go through Python. Eventually we
might expand the API to include pure python functions to do additional
conversions (although I worry about increasing the external dependency
list) but numpy arrays will still be the default because of the inherent
performance benefits.
Fixes #342

Pull Request Test Coverage Report for Build 885401416

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.07%) to 95.524%

Totals

Change from base Build 883642412:
-1.07%

Covered Lines:
5890

Relevant Lines:
6166

💛  - Coveralls


Invoice Editor: focus first cell (in edit mode) after user clicks "add credit card transaction"

Dup of #17 ?

Yes, dup.


[improve][broker] Fix non-persistent system topic schema compatibility

Motivation
When upgrading broker version from 3.0.x to 3.3.x with ExtensibleLoadManagerImpl enabled, it will have an Unable to read schema exception. And the broker will fail to start. This issue is caused by https://github.com/apache/pulsar/pull/22055 .
***************
*** 23,29 ****
      "default" : null
    }, {
      "name" : "bundleCount",
!     "type" : "int"
    }, {
      "name" : "cpu",
      "type" : [ "null", "org.apache.pulsar.policies.data.loadbalancer.ResourceUsage" ],
--- 23,29 ----
      "default" : null
    }, {
      "name" : "bundleCount",
!     "type" : "long"
    }, {
      "name" : "cpu",
      "type" : [ "null", "org.apache.pulsar.policies.data.loadbalancer.ResourceUsage" ],
***************
*** 59,65 ****
      "type" : "long"
    }, {
      "name" : "topics",
!     "type" : "int"
    }, {
      "name" : "updatedAt",
      "type" : "long"
--- 59,65 ----
      "type" : "long"
    }, {
      "name" : "topics",
!     "type" : "long"
    }, {
      "name" : "updatedAt",
      "type" : "long"

Modifications
Add a new class NonPersistentSystemTopic, and it will use for system non-persistent topic.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.56%. Comparing base (bbc6224) to head (c21eccc).
Report is 576 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #23286      +/-   ##
============================================
+ Coverage     73.57%   74.56%   +0.99%
- Complexity    32624    33794    +1170
============================================
  Files          1877     1928      +51
  Lines        139502   145063    +5561
  Branches      15299    15860     +561
============================================
+ Hits         102638   108167    +5529
+ Misses        28908    28634     -274
- Partials       7956     8262     +306

Flag
Coverage Δ

inttests
27.91% <100.00%> (+3.33%)
:arrow_up:

systests
24.66% <0.00%> (+0.33%)
:arrow_up:

unittests
73.90% <100.00%> (+1.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

...rg/apache/pulsar/broker/service/BrokerService.java
81.93% <100.00%> (+1.15%)
:arrow_up:

...ervice/nonpersistent/NonPersistentSystemTopic.java
100.00% <100.00%> (ø)

... and 564 files with indirect coverage changes

@codelipenghui Did you mean to set the SchemaCompatibilityStrategy to BACKWARD?


fix(e2e): restore e2e fix

See #266

See https://github.com/angular/webdriver-manager/issues/121 which describes how Travis is stuck on an old version of Chrome and ONLY by pinning to "old" versions of protractor and webdriver can we make tests pass in Travis.
The sad consequence (for now) is that consumers of this QuickStart get an old, arguably "wrong" version of protractor and webdriver.  We don't control Travis. We will fix as soon as possible.


Disable fix_segments_intersections for now

When the bounding boxes had intersections and were exported with the COCO JSON format they were often cut off. I commented out the line with the function fix_segments_intersections and replaced it with lines of that function. This helped with the bounding boxes and keeps the masks as they are created with CVAT. It is probably inconvenient for the user to get something fixed in the export without an active agreement. Secondly letting a function automatically fix segments could result in a bad fix.

This helps with https://github.com/opencv/cvat/issues/718.

@azhavoro , could you please review?

@Johannes222 , thanks for your time and help. Great contribution!


Clean up getting substitution expressions

Changes

Prior to this change, the functions for fetching substitution expressions were inconsistent in the codebase.
This change updates the functions for fetching substitition expressions from Parameters and Pipeline Results such that they are member functions, in line with related functions.
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
~- [ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps~

[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep

~- [ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.~
~- [ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release~
Release Notes
NONE

/test check-pr-has-kind-label

/retest

/assign

/lgtm


Story title in the editor is limited to 23 chars which is mismatched from the Prepublish checklist guidance.

Bug Description
The display of the story title in the editor is limited to 23 chars, whereas our guidance in the Prepublish checklist is to keep the title less than 40 chars.
There seems to be a mismatch in what we recommend, what we permit, and what the editor will display to the user.
Expected Behaviour

Unsure if this was intentional - @samitron7 ?

Steps to Reproduce

In the editor create a story with a title that is longer than 40 characters
Note that the editor only displays 23 chars
Note that the prepublish checklist correctly advises the creator to limit the title to 40 chars.

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

This could be as simple as making the input field larger or adjusting the check to match the size of the input field.

Duplicate of #41 I believe
This has come up many many times before.


Update Pairwise data

@mmahdigh do you want to submit this PR? It's still in draft mode

@mmahdigh do you want to submit this PR? It's still in draft mode

Hi! Thanks for approving it!
I'm waiting for some team members to approve the changes I have made. Will make it ready to merge once I get the greenlight from them.

@ccerv1 please merge this if everything is okay on your side.

/validate f045afd47f3e91bccc0e9c7335deee76af0c75e8


Support mounting app via new Vue({el: "#app"})

Potentially to #34 (needs alias: { vue: require.resolve("vue/dist/vue.esm.js") })
Two ways to init (Vue 2):
// App.vue
const app = createApp({
  render: () => h(App),
});

// No App.vue — init on #app el
 var app = new Vue({
   el: "#app",
});

The latter will fail to register/find components.
If this is expected behavior, forgive me and close, but took me embarrassingly long to troubleshoot.
Hopefully this scenario can be supported. If a minimal codesandbox is needed, let me know.

Sorry, this feature only works for Vue SFC, and I don't really see it's feasible for inline components.

@antfu technically, all the components are SFC, but the app itself is initialized onto the #app element. This scenario let's everyone doing backend integration (Laravel, Rails) to still use backend templates, while also pulling in SFCs (and slotting content into them).
If it was possible to slot <App> that would be nice, but unfortunately you can't, thus inlining for app is required and we can use SFCs everywhere else.

This plugin is relaying on .vue SFC's compile result and transform it to support auto importing (eg. __resolveComponent('Foo') will be resolved to import Foo from './components/Foo.vue' and replace the usage to Foo. If you can find a solution to your cases I am happy to review the PR.


[docs-infra] Document bundle size of each component

Summary
Bundle size matters. I think it's important we document it in the docs. Documenting:

Forces us to measure it
Means developers know we know what it is
Means developers easily know if it's good enough for their use cases

For example, see https://github.com/propeldata/ui-kit/issues/157 who are looking for a select component, there is a reputation for bloat to debunk (Base UI) and solve (Material UI).

Examples
I tried two iterations:

https://github.com/mui/material-ui/pull/40592
https://github.com/mui/material-ui/pull/40549

but never had time to work on this to finish it (It's why I was eager to fill: https://www.notion.so/mui-org/React-Engineer-Docs-infra-02023ab7104241888ca2ab3bcb32e19d). I was more trying to fix a regression in the DX.
Motivation
It's related to #201.
Closing this I think involves two steps:

[ ] Implementing it for Base UI
[ ] Supporting it for docs-infra so Material UI can also show components' size (assuming we fix their size)

Search keywords: -

Displaying bundle size accurately is a difficult problem. If you only use one single component from the library, then it’s fully accurate. However once you start using multiple components, the numbers become inaccurate as the sizes don’t add up simply/cumulatively as displayed due to shared dependencies/logic/compression, etc.
I propose we take a non-naive approach to this. https://bundlejs.com allows you to export the specific components you're actually using, treeshaking enabled, to see a true picture. We could have a UI for this on the website where they select all the components they're using/will decide to use to get a true picture of the bundle size.

Oh, I forgot I had opened https://github.com/mui/material-ui/issues/40591


Decouple SparkEnv.scala

What changes were proposed in this pull request?
Add a ShutdownHook(OapRuntime#stop) to ShutdownHookManager, it's execution priority is higher than SparkContext, so OapRuntime#stop() will before than SparkEnv#stop()
How was this patch tested?
exits test

Good Job！

@LuciferYang
Let merge this?

@ivoson will do relevant tests first

I have made some tests, it works fine when shutdownhook called. If we call SparkContext.stop before shutdown, spark env stop will be called first, but it seems fine we stop OapRuntime after spark env stop.

@ivoson merge master done


Extending partial causes error (handlebars.compile is not a function)

Trying to implement handlebars-layouts, I get error when extending a partial:
ERROR in Template execution failed: TypeError: handlebars.compile is not a function

I registered the helpers and partials (handlebars.js):

const Handlebars = require('handlebars/runtime')
const layouts = require('handlebars-layouts')
const fs = require('fs')

Handlebars.registerHelper(layouts(Handlebars))

const partial = fs.readFileSync('./src/components/partial.hbs', 'utf-8')
Handlebars.registerPartial('partial', partial)

module.exports = Handlebars

Added the handlebars runtime to handlebars-loader options in webpack config (webpack.config.js):

/* ... */
test: /\.hbs$/,
loader: 'handlebars-loader',
options: {
    runtime: SRC_PATH + '/helpers/handlebars',
    helperDirs: [SRC_PATH + '/helpers']
}
/* ... */

Partial component partial.hbs
Extending partial webpack-layouts.hbs

What am I missing?
When I register the partial as follows, no error is appearing, but the partial is not extended (handlebars.js)
Handlebars.registerPartial('partial', () => {
  return partial
})

Repro repository:
https://github.com/martyan/start-coding/tree/handlebars-layouts
Commit with handlebars-layouts implementation:
https://github.com/martyan/start-coding/commit/ad7583023342c73f41fd90a1cfc4df30677f9b58

What was the solution to this?


Updated image for respectful issue# 211

Updated the source narration of an image.

@Aini-Bashir please review this pull request.

@Aini-Bashir please review this PRs.


Player frame

Added missing info to details component as per #37, ready for styling now.

sweet, I will forward it to Alex.

@asherman-ca looks good. merging now.


Migrate from UA Google Analytics to GA4

The deadline is July

(Part 1 was https://github.com/DIYGPSTracker/DIYGPSTracker.github.io/commit/d271ffba4cac8425187d250eaadc6ae644855674 - wring commit message)


Update configure-liveness-readiness-startup-probes.md

Hi,
Just some translate fixes in french.

/lgtm

/check-cla

Hey there! @muadhib, looks like you haven't signed the CLA yet. Could I please have you do that? https://github.com/kubernetes/community/blob/master/CLA.md

Hi @muadhib .
Have you signed the CLA?


update readme to document how to add to oauth client

to preview in cluster
OPENSHIFT_HOST=master.<name>.openshiftworkshop.com yarn start:dev
fails with oauth error. To workaround:
oc edit oauthclient tutorial-web-app
add entry at bottom of file:
- http://localhost:3006

out of date


AllGather incorrect output / hangs for certain test cases in dram

Seeing weird behaviour of all gather getting mismatches/hangs.
Note that this is the older implementation of all gather. The newer one where sender always pulls from memory each hop has not been tested with these cases yet.
The most common case are RM tensors in DRAM, where going above 13 rows of input I start seeing these issues.
There is also one hang case if Tile layout in DRAM when num_links=2.
It seems like some of these hang/mismatch cases can go away when introducing a delay after the sender core reads from dram.
Debug branches/tests:
aho/all-gather-debug and aho/all-gather-debug2
The first one has everything stripped out of all gather except reading data into l1 and dprinting a couple values. I'm seeing that the second value dprinted is garbage, but it’s correct if I write to erisc_info and readback or remove the first dprint or add some delays after the async_reads or even after the dprint? Delay fixing after dprint is very strange.
Second one is full all gather test with a dprint/added delay after read barrier.
If you increase input rows above 12 you start seeing incorrect output/hangs. If I dprint after the barrier output for 13 rows is correct, but 33 still hangs. If I add a delay after then 13 has incorrect output, but 33 now passes
For both of these the test is tests/tt_eager/python_api_testing/unit_testing/test_all_gather.py and kernel is tt_eager/tt_dnn/op_library/all_gather/kernels/dataflow/interleaved_eth_ring_gather_send_stick_layout.cpp

For falcon we are always pulling from L1 so there haven't been any issues so far.

I don't know if any of this applies anymore with the most recent implementation.
What I can say is I did sometimes see a hang where one of the worker cores never receives its "go" signal and so it sits idle. Moving the workers around gets around the issue. It wasn't root caused.
I also noticed an occasional non-deterministic PCC issue. It looks like it might be an issue with the API somewhere? Still needs to be root caused but some interesting details I noticed is it's only the last part of the tensor that ever mismatches, never the beginning or middle. Additionally, I only ever see a mismatch for Tensor 0 (the one on chip 0). I was seeing this with bidirectional, which means that it's the last tensor data that should be committed to DRAM that's mismatching. It's as if the write barriers aren't actually waiting for the payload to land in DRAM.

I'm going to close this now as there are no known hanging all-gather test cases, except in certain circumstances, which have more concrete issues opened for them, and they are opened against runtime.


Improve Docker image

The purpose of this issue is to solicit community feedback and hopefully reach some consensus.
As of v0.135.0 I can do things like[^1]:
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0 config
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0 env
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0 list all
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0 new foo.md
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0 server

But I can't build the site; perhaps I'm missing something. For example, this doesn't work:
docker run -v .:/site -u $(id -u):$(id -g) ghcr.io/gohugoio/hugo:v0.135.0

The above would be addressed with https://github.com/gohugoio/hugo/issues/11391, but that shouldn't be necessary.
Additionally, the current version:

Is not the extended version
Does not support Hugo modules
Does not support AsciiDoc, Pandoc, or reStructuredText (which is probably fine)
Does not support PostCSS
Does not support GitInfo
Does not write to host cache directory (cacheDir / HUGO_CACHEDIR / os.CacheDir)

But now that we can build an image, it would be good to define what we actually want it to do.
Some time ago I created a repo to test docker images:
https://github.com/jmooring/hugo-docker-test
Our Docker image doesn't need to pass that test, but we should consider what we want to support:
https://github.com/jmooring/hugo-docker-test?tab=readme-ov-file#site-characteristics
[^1]: The -u $(id -u):$(id -g) flag is required to set correct permissions on published files.

So, the image will need to be able to build a Hugo site. If that's not the case, please create a bug, but I'm not taking improvement requests for this particular feature. It was supposed to be a simple thing and we have already spent hundreds of hours on it.
@jmooring I'm closing this, create a new bug track the actual bug.

I'm reopening this, the timing of this got me a little grumpy. We have spent a stupid amount of time just getting the build setup working, and I kind of assumed that the people who started that process found the Docker image we've had living in the project for years both working and useful.
That said, I'm already maintaining 2 complex Docker files for the Hugo build, I'm not adding another to that plate, so let us focus on the "getting it in a working state",.


Drop support for Python 3.6

In order to update the dependency on jsonschema (https://github.com/eclipse-basyx/basyx-python-sdk/commit/80913ef9ad5dc1bbf673b84acbc54dbfc1a3915f), Python 3.6 must be dropped. Python 3.6 is EOL since 23.12.2021 and all major distributions have updated to more recent releases.
Also disable skipping of a unit test on Python versions < 3.7, since this is no longer supported and tested anyways.
This PR is required by #24.

Looks good to me


String.prototype.lastIndexOf()

Added a binding for String.prototype.lastIndexOf(). :smile: Let me know if there's any issues with this!

Just saw the commit on master regarding fixes for nightly! I can rebase this, expecting it won't pass the CI build.

@sendilkumarn of course! Was fun to learn more a little about wasm-bindgen. I might try and add a few other bindings today :)

Made a minor punctuation edit to the comments above the binding for the sake of consistency.

👍

Referencing #275 so people don't duplicate work :)


Why are "Args" classes sealed?

I would like to inherit from the "Args" classes as a means of setting default values, such as:
    public class FunctionAppArgsWrapper : FunctionAppArgs
    {
        public FunctionAppArgsWrapper()
        {
            HttpsOnly = true;
        }
    }

Unfortunately, these classes are sealed, and, therefore, the wrapper cannot be accomplished.
Do the "Args" classes need to be marked sealed? What is the recommended practice for setting custom settings? In particular, I'd like to share these defaults via a NuGet package.

I believe it is a common design principle for .NET libraries: seal a class unless it's deliberately and carefully designed to be extensible.
If a class is unsealed, there are more ways to introduce breaking changes, since someone might have subclassed it and depend on all kinds of its behavior. It may also lead to confusion if somebody extends the args with extra properties and expects them to be set on the resource.
You could have a factory or a bulder to produce instances of an args class. A very simplistic example:
public static class ArgsFactory
{
    public static FunctionAppArgs MakeAwesomeFunctionAppArgs(string planId)
    {
        return new FunctionAppArgs
        {
            PlanId = planId,
            // all other props
        };
    }
}


[GHSA-pfm2-mqwj-ggm5] In MediaWiki before 1.34.1, users can add various...

Updates

Affected products
Summary

Comments
The vulnerability description directly mentions the affected package mediawiki, which is included in npm, https://www.npmjs.com/package/mediawiki

I believe this advisory is referring to the php mediawiki and not the js tool which seems to be for making test agents.


[FLINK-12476] [State TTL] Consider setting a default background cleanup strategy in StateTtlConfig

What is the purpose of the change
This pull request sets a default background cleanup strategy in StateTtlConfig
Brief change log

Added a general config method cleanupInBackground
Changed document

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@azagrebin Can you review this PR?

@azagrebin What do you think about the new changes?

Hi @azagrebin thanks for your suggestion, I have accepted most of them, there are few suggestions I left some comments. Please review again.

@aljoscha and @azagrebin Any more suggestions?

@azagrebin Thanks and any further suggestions?

@azagrebin thanks for your suggestion, I have fixed issues.

@azagrebin Really thanks for the review! cc @aljoscha

@yanghua could you also squash the commits and add the description from jira issue as a detailed description in the main commit?

Thanks @azagrebin , have done.

Merging


Add sync button to context menus

As a followup to #10:

Add a "Sync all to Notion" button to collection context menu
Add a "Sync to Notion" button to item context menu

from #6

Would a "sync to Notion" button as described in #21 solve your use case?

For my use case, adding the sync button would improve the flexibility of the plugin. I think an option should be added for the user to choose between automatic or manual syncing

I think an option should be added for the user to choose between automatic or manual syncing

I like this idea. Once a sync button is added, could this be achieved by just unchecking the collections in the Notero preferences that you don't want to automatically sync?

Do you mean, in the Notero preferences :

collection is selected: Automatic synchronization ( while, Manual synchronization is disabled)
collection is not selected: Manual synchronization (auto-sync is disabled)

I think it's a viable solution

@panyuz, good news! This feature has finally been released in version 0.4.4. I hope you find it useful!


Save code

probably better to start for a single object type first, perhaps programs
Requires #13 and #14

partially working, without activation or transport selection


Ammend in a line

https://github.com/commclassroom/commclassroom/blob/aa923fd1dd840255357dea8dd88faee876979d6a/index.html#L192
i would like to amend this line as-
"Get expert guidance with career, Open Source, internships and jobs around the world."

Can i take up this issue ?

@Preranasingh2001 if this issue is open, can i work ont this?

@kaiwalyakoparkar can i work on this?


I want to use this shop system as a multi-site system

Hi dear friend.
First of all I appreciate for your good job.
My question is how can I use this system as a multi-site system?
My example address is shop.com
I want to have multiple subfolders as multiple shops. the subfolders are shopfolders actually.
I want to have one core system/code and use it for any shop subfolder.
like this:
main domain: http://shop.com
shopping1: http://shop.com/shopping1
shopping2: http://shop.com/shopping2
could you help me to solving this problem?

@saeedisfahani you have to search on google is there option for codeigniter to work with one system and multiple applications.
This platform doesn't support multiple domains


[BUG] Longhorn volume random detachment from the workload in Rancher

I am experiencing random malfunctions to Longhorn volumes with the pods of my Rancher environment.
They are seen as attached to a pod from Longhorn UI, but I cannot access their data from inside the container. In particular, I see I/O errors from the logs or when accessing the mounted directories via shell. If I run mount from inside the container I can still see the mount point from the PVC to the local directory, but it's not accessible anymore.
It is sufficient to scale down and then up again the workload to re-connect the volume.
To Reproduce
Steps to reproduce the behavior:

From Rancher, create a new workload and create a new PVC by leveraging the Longhorn storage driver.
After some time (this is random to me) try to access the workload and cd to the volume dir
Receive I/O errors and malfunctions from the container
Scale down the workload from Rancher UI by reducing Config Scale from 1 to 0
Scale up the workload again from Rancher UI by incrementing Config Scale from 0 to 1
Try to access the workload and cd to the volume dir
You don't receive I/O errors anymore and can see the contents

Expected behavior
I expect the Longhorn volume to not detach from the container at any given time, as it can make the workload fail unexpectedly (e.g. if a volume is used to persist a private Docker registry).
Log
N/A.
Environment:

Longhorn version: 1.0.0
Kubernetes version: 1.17.5 (RKE)
Node OS type and version: Ubuntu Linux Server 18.04.4 LTS
Rancher version: 2.4.3

@mrcdb a volume detachment can happen for example when the volumes engine process crashes or there are resource exhaustions (network, cpu, etc). To mitigate this you should setup a liveness probe on your workload deployments, see example in the docs here: https://longhorn.io/docs/1.0.2/high-availability/recover-volume/
This will make sure that your workloads are automatically restarted in the case of a volume failure, which will then lead to a correct volume attachment/mount.

Hi @joshimoo , thanks for the suggestion. I have enabled liveness probes on the volume-equipped workloads as you proposed. I think this issue can be closed now.

@mrcdb
FYI, in the incoming version (v1.1.0), we have changed the logic to handle the situation when Longhorn volume is detached unexpectedly. Basically, you will not have to do any extra setup. See more at:
Implementation: https://github.com/longhorn/longhorn-manager/pull/722
Docs: https://github.com/longhorn/website/pull/211

@PhanLe1010 this looks pretty good! I'm glad Longhorn will be able to automate the pod deletion if a volume detachment happens.


Fix constructor

[ ] Auto call base class's constructor

Development on this issue has been canceled because implemention of this feature was impossible


Fix two bugs in HierarchicalIterative::rightHandSideFromConfig.

This commit has been tested on gepgitlab
It does not improve the poor performance of benchmark romeo-placard.

Looks good to me. You can merge if ready.


samples: add therabot

Pull Request Title
Description
Please include a summary of the change or the feature being introduced. Include relevant motivation and context. List any dependencies that are required for this change.

[ ] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
This PR addresses issue #X
Screenshots
If relevant, please add screenshots.
Notes
Please add any relevant notes if necessary.

@RohittCodes you added an extra commit in your PR that belongs to another contributor. Please remove that commit

@Tpuljak reverted!!


It does not work anymore

Here's the full error we're seeing:
[33m    Liquid Warning: Liquid syntax error (line 5): Expected id but found open_square in "item in site.[item.label]" in feeds/feed.json[0m
[31m  Liquid Exception: nil is not a symbol nor a string in feeds/feed.json[0m
[31m             Fatal: TypeError[0m
It looks like the error is caused by the syntax of this line in your feeds.json

Yep, same for me. The latest GitHub Jekyll refuses to build because of the feeds.json validation error.

Changing line 7 of feeds/json.feed from:
{% for item in site.[item.label] %}

to:
{% for item in site.item.label %}

Allows Jekyll to build and on my site search now works as before. However, since I don't use 'collections' on my Jekyll site I can't guarantee that the above is a fully working fix for everyone.


In Why use LCEL Page, navigation is not working in docs properly

Fixes # (issue)
Next page navigation leads to the main heading of LangChain Expression Language.
[image]: (https://github.com/langchain-ai/langchainjs/assets/106463254/d829403e-9cc2-444f-b22c-9cfe9c65ec73)
[Link] : (https://js.langchain.com/docs/expression_language/why)

Thank yoU!


ClassCastException while trying to iterate over performance metrics

While trying to iterate the list from getMetrics in Performance interface, I am encountering this error :
java.util.LinkedHashMap cannot be cast to com.github.kklisura.cdt.protocol.types.performance.Metric"
Sample code: https://gist.github.com/varun85gupta/7ceab06ad7db39a45f8c49454b0dcf21

Although we can still achieve it using this, it would be better if we can iterate directly.
for(Object metric: metrics)
{
       LinkedHashMap<String, Double> metric1 = (LinkedHashMap<String, Double>) metric;
       System.out.println(metric1.get("name")+":"+ metric1.get("value"));
}

Hi, thanks for using this library and for opening this issue. The fix for this should be available in 1.3.6 that has just been released. You can use getMetrics (and similar methods) without that casting.

Thanks for the fix. I'll validate it.


Incorrect encoding of open and close double quotes and of ligatures

The attached PDF contains a single line of text:
This PDF contains ligatures, for example in “file” and “floor”.
(And of course the PDF really does have curly double quotes and fi and fl ligatures.)
However, this code:
require 'pdf/reader'
filename = ARGV.pop
reader = PDF::Reader.new(filename)
reader.pages.each do |page|
  puts page.text
end

Produces this incorrect output:
This PDF contains ligatures,for example in …‡le†and …ˆoor†.
test.pdf

Huh. This is a super simple case (a built-in font with a difference table for non-standard characters) and I can confirm it's broken. In fact, it's been broken since #64 merged (gem versions >= 1.3.0).
I guess there's a gap in the spec suite...