text:
UnicodeDecodeError: 'utf-8' codec can't decode byte

For trial to have streaming of response, below error occurs
File [~/miniconda/envs/fastapi/lib/python3.10/site-packages/llama_cpp/llama.py:482](https://file+.vscode-resource.vscode-cdn.net/Users/jinwhan/Documents/Coding/Solidity/Page/cloudRun/cloudrun-fastapi/app/~/miniconda/envs/fastapi/lib/python3.10/site-packages/llama_cpp/llama.py:482), in Llama._create_completion(self, prompt, suffix, max_tokens, temperature, top_p, logprobs, echo, stop, repeat_penalty, top_k, stream)
    473     self._completion_bytes.append(text[start:])
    474     ###
    475     yield {
    476         "id": completion_id,
    477         "object": "text_completion",
    478         "created": created,
    479         "model": self.model_path,
    480         "choices": [
    481             {
--> 482                 "text": text[start:].decode("utf-8"),
    483                 "index": 0,
...
    488     }
    490 if len(completion_tokens) >= max_tokens:
    491     text = self.detokenize(completion_tokens)

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xec in position 0: unexpected end of data

My code snippet was prepared as below referring Example.
from llama_cpp import Llama
import json

model_path = /my/model/path/for/ko_vicuna_7b/ggml-model-q4_0.bin"
prompt = "Tell me about Korea in english"
llm = Llama(model_path=model_path, n_ctx=4096, seed=0)

stream = llm(
    f"Q: {prompt} \nA: ",
    max_tokens=512,
    stop=["Q:", "\n"],
    stream=True,
    temperature=0.1,
    )

for output in stream:
    print(output['choices'][0]["text"], end='')

Not only 0xec, but also 0xed, 0xf0 occurred for other trial cases. I cannot assure but it may be caused by language of model which is fine tuned for korean from vicuna 7b.
For your reference, several letters were given but it stops suddenly with above error.

May be fixed in #118

authors: gjmulder mozzipa

repo: abetlen/llama-cpp-python


text:
Create prowjobs-lint-presubmits.yaml

Add linting presubmit job.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@abhay-krishna: Updated the job-config configmap in namespace default at cluster default using the following files:

key prowjobs-lint-presubmits.yaml using file jobs/aws/eks-distro-prow-jobs/prowjobs-lint-presubmits.yaml

In response to this:

Add linting presubmit job.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

source: gharchive/pull-request

repo: abhay-krishna/eks-distro-prow-jobs

license_type: permissive

license_source: github-api


text:
[Question]: OPen multiple Same Camera, ValueError: Invalid source with no decodable audio or video stream provided. Aborting!

Issue guidelines

[X] I've read the Issue Guidelines and wholeheartedly agree.

Issue Checklist

[X] I have searched open or closed issues for my problem and found nothing related or helpful.
[X] I have read the Documentation and found nothing related to my problem.

Describe your Question
OPen multiple Same Camera, ValueError: Invalid source with no decodable audio or video stream provided. Aborting!
Terminal log output(Optional)
ValueError: Invalid source with no decodable audio or video stream provided. Aborting!

Python Code(Optional)
decoder = FFdecoder("0", frame_format="bgr24",custom_ffmpeg="./ffmpeg/bin", verbose=True,**ffparams).formulate()
decoder = FFdecoder("1", frame_format="bgr24",custom_ffmpeg="./ffmpeg/bin", verbose=True,**ffparams).formulate()
decoder = FFdecoder("3", frame_format="bgr24",custom_ffmpeg="./ffmpeg/bin", verbose=True,**ffparams).formulate()

DeFFcode Version
0.2.3
Python version
3.10
Operating System version
windows
Any other Relevant Information?
No response

ValueError: Invalid source with no decodable audio or video stream provided. Aborting!
@GavinJIAW This error means that one of the source value is invalid, meaning there's no device at "0" or "1" or "3" index, check logs to get more insight. And it is perfectly fine to open multiple cameras, as long as your system allows it.

source: gharchive/issue

authors: GavinJIAW abhiTronix

repo: abhiTronix/deffcode


text:
NetGear_Async: Add bi-directional data transfer mode

Detailed Description

This issue will oversee implementation of NetGear's bi-directional data transfer exclusive mode for NetGear_Async API.
Context

Currently, NetGear_Async is far efficent than its NetGear counterpart, but lacks in terms of flexibility with Exclusive modes. This issue will attempt to introduce first of them, NetGear's bi-directional data transfer exclusive mode for NetGear_Async API.
Your Current Environment

VidGear version:  v0.2.2-dev
Branch:  development
Python version:  all
Operating System and version: all

Any Other Important Information

https://abhitronix.github.io/vidgear/latest/gears/netgear/advanced/bidirectional_mode/

Where are the new codes, development branch?

@rubar-tech not yet. Only after #106 resolved, be patient.

@rubar-tech This was harder to pull off but I did it. Please wait till I upload related doc commits. But the bare-minimum example for bidirectional video-frames transfer will be as follows:
Server End
# import library
from vidgear.gears.asyncio import NetGear_Async
import cv2, asyncio
import numpy as np

options = {"bidirectional_mode": True}
# initialize Server without any source
server = NetGear_Async(logging=True, **options)

# Create a async frame generator as custom source
async def my_frame_generator():
    # !!! define your own video source here !!!
    # Open any video stream
    stream = cv2.VideoCapture("foo.mp4")
    # loop over stream until its terminated
    while True:

        # read frames
        (grabbed, frame) = stream.read()

        # check if frame empty
        if not grabbed:
            # if True break the infinite loop
            break

        # do something with the frame to be sent here

        recv_data = await server.transceive_data()
        if not (recv_data is None):
            if isinstance(recv_data, np.ndarray):
                cv2.imshow("Reciever Frame", recv_data)
                key = cv2.waitKey(1) & 0xFF
            else:
                print(recv_data)

        target_data = "Hello, I am a Server."
        # yield frame
        yield (target_data, frame)
        # sleep for sometime
        await asyncio.sleep(0)
    stream.release()

if __name__ == "__main__":
    # set event loop
    asyncio.set_event_loop(server.loop)
    # Add your custom source generator to Server configuration
    server.config["generator"] = my_frame_generator()
    # Launch the Server
    server.launch()
    try:
        # run your main function task until it is complete
        server.loop.run_until_complete(server.task)
    except (KeyboardInterrupt, SystemExit):
        # wait for interrupts
        pass
    finally:
        # finally close the server
        server.close()

Client End
# import libraries
from vidgear.gears.asyncio import NetGear_Async
import cv2, asyncio

options = {"bidirectional_mode": True}
# define and launch Client with `receive_mode=True`
client = NetGear_Async(receive_mode=True, logging=True, **options).launch()

# Create a async function where you want to show/manipulate your received frames
async def main():
    # !!! define your own video source here !!!
    # Open any video stream
    stream = cv2.VideoCapture("big_buck_bunny_720p_1mb.mp4")
    # loop over Client's Asynchronous Frame Generator
    async for (data, frame) in client.recv_generator():
        if not(data is None):
            print(data)

        # {do something with received frames here}

        # Show output window
        cv2.imshow("Output Frame", frame)
        key = cv2.waitKey(1) & 0xFF

        (grabbed, target_data) = stream.read()
        # check if frame empty
        if grabbed:
            # if True break the infinite loop
            await client.transceive_data(data=target_data)

        # await before continuing
        await asyncio.sleep(0)
    stream.release()

if __name__ == "__main__":
    # Set event loop to client's
    asyncio.set_event_loop(client.loop)
    try:
        # run your main function task until it is complete
        client.loop.run_until_complete(main())
    except (KeyboardInterrupt, SystemExit):
        # wait for interrupts
        pass

    # close all output window
    cv2.destroyAllWindows()
    # safely close client
    client.close()

@rubar-tech Btw, if not clear yet, you can install vidgear from source as follow:
 # clone the repository and get inside
  git clone https://github.com/abhiTronix/vidgear.git && cd vidgear

  # checkout the latest development branch
  git checkout development

  # install normally
  pip install .

  # OR install with asyncio support
  pip install .[asyncio]

Bidirectional data transfer mode for NetGear_Async API successfully added and merged in commit: https://github.com/abhiTronix/vidgear/commit/c73428dff35aded6b598f3486e11d53477468ec1

Related Doc is available here: https://abhitronix.github.io/vidgear/v0.2.2-dev/gears/netgear_async/advanced/bidirectional_mode/

authors: abhiTronix rubar-tech

repo: abhiTronix/vidgear


text:
Apply regressions to find board-image homography

This is a continuation of issue #37 .
Here, you have to develop a RANSAC-like algorithm with linear and geometric regressions to find indices of vertical and horizontal    lines from the Hough transform and assign each remaining image point to an integer pair representing a board point.

I'll take up this issue.

license: MIT


text:
Updates

Github actions version updates.
Test refactoring.
build.yml - Node version 18.x addition.

Codecov Report
Base: 99.02% // Head: 99.02% // No change to project coverage :thumbsup:

Coverage data is based on head (d0c0a74) compared to base (a1597bc).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   99.02%   99.02%
=======================================
  Files           1        1
  Lines         103      103
=======================================
  Hits          102      102
  Misses          1        1

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: abhinavminhas codecov-commenter

repo: abhinavminhas/qtest-mstest-parser


text:
Add my profile README

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
I added my own profile README.md
Add Link of GitHub Profile

Done


text:
Office staff update

closes #15

@utkarsh-tf141 This is not the kind of link we use in emails, mailto: has to be used. Also, don't put any HTML content inside objects. Render the emails inside anchor tags inside the Description tag.

repo: abhishekshree/spo-website


text:
django.utils.importlib is removed in Django 1.9

The module sdjango.py imports django.utils.importlib, which has been deprecated since Django 1.7 and was removed in Django 1.9. Django's importlib had been a copy of Python 2.7's importlib, so the fix should be relatively straightforward.

Should be fixed by acf095b78208edb59b5873662653e12773add3cc. Can we close this ticket?

authors: hartwork jakebuhler

repo: abourget/gevent-socketio

license_source: bigquery


text:
Chore: Upgrade GraphiQL to 1.11.4

So, this is the first step on a bigger journey to get the GraphiQL client(s) up to date.
I might need little guidance here and there since I only started wokring with the codebase this evening, and not everything might be optimal ( looking at you, build_asset_path/2)
I also have s semi-functional version of graphiql 2.0 behind a new :beta interface key, but that one needs some more work to get headers to work, and to figure out whether we still need the @absinthe/absinthe-socketlibs or whethercreateGraphiQLFetcher()from@graphiql/toolkit` can solve whatever prompted the creation of that in the first place out of the box now.

If someone has more context/knows, why some decisions were made, that would be greatly appreciated!
This PR
the package still used the 5 year old graphiql@0.11.10, which has a bunch of security issues and could benefit from an update in general (bundle size reduction from react@16 among others). This PR updates graphiql and introduces a way to have two react versions in the asset list, so graphiql-workspace(the :advanced interface) stays functional, since it break with newer react versions.
Next Steps
The next big step would be to get graphiql@2 working, especially with headers and subscriptions. The is quite a bit of plumbing going on atm, which I will need to figure out first, plus the new createGraphiQLFetcher function is not shipped in a browser-compatible version, so we might need another intermediary package... 😨
Once 2.0 ships and graduates beta stage, we can probably remove/alias the :advancedinterface, since graphiql provides those enhancements out of the box. Also,graphiql-workspace` hasn't seen an update in ~4 years, so I wouldn't expect and update on that front.
Happy about any and all feedback !

@benwilson512 can't request a review formerly yet, would be great if you could take a look at this after your parental leave :)

Thanks for your work on this @luhagel, I don't have time to help with the initial work, but can definitely try it when you think it's ready for testing as we are using the old version at the moment.

Adding to the convo to say this would be a huge boost for Absinthe on my team. Due to the age and limitations of the available GraphiQL interfaces we are currently dropping in Apollo Sandbox. Now that GraphiQL is up to a stable 2.2.0 release it might be reasonable to target an update to 2.x.

Bump. Curious if an upgrade will be merged in the near term?
cc: @benwilson512 @luhagel

Bump. Curious if an upgrade will be merged in the near term? cc: @benwilson512 @luhagel

Probably needs an upgrade at this point, given that graphiql 3 is underway, I'll try and find some time to get this all cleaned up in the next few weeks @derekbrown

Looking forward to this very needed refresh.

authors: aglassman derekbrown drewble duksis luhagel


text:
🛑 AbsorFlix is down

In 1c4a25b, AbsorFlix (https://player.absor.top) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AbsorFlix is back up in ea8b8ed after 22 hours, 23 minutes.

repo: absortian/AbsorStatus


text:
I need to create POST requests with different body each one

Hello
I have a big model (generating using Bogus lib - it has unique email, id etc) - I want to run Post Requests to create a lot of entities. Are there any ways to implement this?
I'v found you advised to use PreProcessor here - https://github.com/abstracta/jmeter-java-dsl/issues/7 - but there is no PreProcessor class in dotnet dsl.
Tnanks!

Hello, thank you for bringing this into attention!
We can easily add the jsr223PreProcessor to the dotnet library with support for specifying code in groovy. Providing support for using c# code and dotnet libraries is not that simple though.
Can you provide an example code of what you would like the DSL to support or how would your think you could express in code what you need?
One alternative for generated and distinct data might also be implementing the csvDataSet element in dotnet library (easy to do as well) so you can generate in dotnet/c# code a CSV with whatever content you may like (and using whatever library you desire) and then just use the proper variables in the HTTP Post request.
In any case, I would like to understand a little better what would be the ideal scenario for your use case and then provide a good approximation to it .

Hello, thank you for bringing this into attention!
We can easily add the jsr223PreProcessor to the dotnet library with support for specifying code in groovy. Providing support for using c# code and dotnet libraries is not that simple though.
Can you provide an example code of what you would like the DSL to support or how would your think you could express in code what you need?
One alternative for generated and distinct data might also be implementing the csvDataSet element in dotnet library (easy to do as well) so you can generate in dotnet/c# code a CSV with whatever content you may like (and using whatever library you desire) and then just use the proper variables in the HTTP Post request.
In any case, I would like to understand a little better what would be the ideal scenario for your use case and then provide a good approximation to it .

Tnx for fast reply, this is my code:
.............
using Bogus;

    [Fact]
    public async Task LoadTest()
    {
        // Arrange
        var requestDto = Create_CreateCompanyRequestBogus();
        var request = JsonSerializer.Serialize(requestDto);

        // Act
        var stats = TestPlan(
            ThreadGroup(2, 5,
                HttpSampler("https://tst-api.purpleunity.dev/company-and-contact/api/companies")
                    .Post(request, new MediaTypeHeaderValue(MediaTypeNames.Application.Json))
                    .Header("Authorization", AuthToken)
            ),
            JtlWriter("jtls")
        ).Run();
        stats.Overall.SampleTimePercentile99.Should().BeLessThan(TimeSpan.FromSeconds(5));
    }

    private CreateCompanyRequest Create_CreateCompanyRequestBogus()
    {
        var faker = new Faker<CreateCompanyRequest>()
            .CustomInstantiator(f =>
                new CreateCompanyRequest(
                    IdentityId: Guid.NewGuid().ToString().OrNull(f, 0.2f),
                    Name: f.Company.CompanyName(),
                    VatNumber: f.Random.Replace("??#########").OrNull(f, 0.2f),
                    Iban: f.Random.Replace("??######################").OrNull(f, 0.2f),
                    Bic: f.Finance.Bic().OrNull(f, 0.2f),
                    ChamberOfCommerceNumber : f.Random.Replace("??-???-########").OrNull(f, 0.2f),
                    ExternalId: Guid.NewGuid().ToString().OrNull(f, 0.2f),
                    IsBuyerEvaluated: f.Random.Bool().OrNull(f, 0.2f),
                    Remarks: f.Lorem.Sentences(1).OrNull(f, 0.2f),
                    AddressLine: f.Address.StreetAddress().OrNull(f, 0.2f),
                    Zipcode: f.Address.ZipCode().OrNull(f, 0.2f),
                    City: f.Address.City().OrNull(f, 0.2f),
                    Region: f.Address.State().OrNull(f, 0.2f),
                    CountryCode: f.Address.CountryCode().OrNull(f, 0.2f),
                    Phone: f.Phone.PhoneNumber().OrNull(f, 0.2f),
                    Mobile: f.Phone.PhoneNumber().OrNull(f, 0.2f),
                    Fax: f.Phone.PhoneNumber().OrNull(f, 0.2f),
                    Email: f.Internet.Email().OrNull(f, 0.2f),
                    WebsiteUrl: new Uri(f.Internet.Url()),
                    DefaultContact: null,
                    UseTheSameAddressForPostal: f.Random.Bool().OrNull(f, 0.2f),
                    PostalAddressLine: f.Address.StreetAddress().OrNull(f, 0.2f),
                    PostalZipCode: f.Address.ZipCode().OrNull(f, 0.2f),
                    PostalCity: f.Address.City().OrNull(f, 0.2f),
                    PostalRegion: f.Address.State().OrNull(f, 0.2f),
                    PostalCountry: f.Address.CountryCode().OrNull(f, 0.2f)
                )
            );
        return faker.Generate();
    }

I join the question. For each request in each iteration, a new request must be created.
My code:
`[Test]
public void RegisterTest()
{
var stats =
TestPlan(
ThreadGroup(5, 2,
HttpSampler("http://localhost/BonusWebApi/api/processing/register/")
.Post(GetRegRequest(), new MediaTypeHeaderValue("application/json")
))).Run();
Assert.That(stats.Overall.SampleTimePercentile99, Is.LessThan(TimeSpan.FromSeconds(2)));
}
//Random random = new Random();
private SecureRandom random = new SecureRandom();
public string GetCardCode()
{
var getCard = random.Next(0, cardsCount - 1);
logger.Debug(getCard);
var cardCode = cards.Skip(getCard).Take(1).FirstOrDefault()?.CardCode;
logger.Debug(cardCode);
while (cardCode == null)
{
cardCode = cards.Skip(random.Next(0, cardsCount - 1)).Take(1).FirstOrDefault()?.CardCode;
}
return cardCode;
}
public string GetRegRequest()
{
var license = cashes.ToList().ElementAt(random.Next(0, cashCount - 1));
Guid accessTokenGuid = license.AccessTokenGuid;
var cardCode = GetCardCode();
return JsonConvert.SerializeObject(new RegisterRequestDto
{
LicenseGuid = license.LicenseGuid,
AccessTokenGuid = accessTokenGuid,
CardCode = cardCode,
CardRegisterDateTime = DateTime.Now,
RegisterDetailDtos = new List
{
new RegisterDetailDto
{
PositionId="1",
ProductCode="12345",
Quantity=1,
TotalPrice=100
}
}
});
}`

Great, thank you! The information you two provide is very helpful and we have some ideas that we would like to implement to support these scenarios. It is great to see the community interest in this feature.
If some other have similar interests please let us know!

We just released 0.4 which includes CsvDataSet and Jsr223PreProcessor.
None of these are optimal solutions for your use cases, but you can use them in the meantime as workarounds or approximations while we come up with some better solution.
Regards

repo: abstracta/jmeter-dotnet-dsl


text:
using PostGateway for authorize.net API as HTTP GET requests not supported

using PostGateway for authorize.net API as HTTP GET requests not supported

Hi thank you for merging this in ...
If you're working towards a new version can you give us an idea of when it will be available via the
PIP packaging system?

repo: abunsen/Paython

license: mit


text:
Question: logbook dependency

Quick question, why is the logbook used instead of logging? I didn't dig through the codebase much, but it doesn't look like the features of logbook are being used in a way that necessitates using it?

At some point logging was deprecated and logbook was the replacement.  I made the change, but then started using warnings more and kept logging for more informational output.

If you have a compelling reason to change things, I have a deprecation warning that needs to be propagated from the develop to the master branch and am willing to do some additional stylistic fine-tuning.

logging was deprecated? I can't find any information about this with a Google search. It's included in python 3.7 even: https://docs.python.org/3/library/logging.html
Mostly just curious. The most compelling reason to use logging instead of logbook is that users don't need to install another dependency if logging is used, especially if none of the logbook functionality is being used.

I wish I could point you somewhere, but it was a few years ago and I don't remember.  Clearly it didn't happen.
Removing dependencies is a good enough reason for me.  I will put it on the to-do list.

No worries. I am mostly curious because we use logging a lot and if it were deprecated I would want to be moving away from it to something else!

Addressed in new branch, will be out in the next version.

authors: aburrell asreimer


text:
Changing number of states does not change model fitting

Changing states to 3 produces model fitting with 4 states:

Could you please add where you changed number of states and what code you ran to fit the models and generate the plots?

I rat fit_with_fit_handler.py and changed only the states variable to 3

Could you please attach the updated scripts you used here. Thanks.

Issue selecting correct model
https://github.com/abuzarmahmood/pytau/blob/d0a2d6e697579bc934ae802a26a41fd2fa059e33/pytau/how_to/scripts/fit_with_fit_handler.py#L57C1-L61C49
dframe = fit_database.fit_database
wanted_exp_name = 'pytau_test'
wanted_frame = dframe.loc[dframe['exp.exp_name'] == wanted_exp_name]
# Pull out a single data_directory
pkl_path = wanted_frame['exp.save_path'].iloc[0]

Plots came out fine once correct model was selected.

authors: abuzarmahmood cmazzio

repo: abuzarmahmood/pytau


text:
🛑 AceBlock Swagger UI is down

In d525056, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in 0d54921.

repo: aceblockID/monitoring


text:
🛑 AceBlock Swagger UI is down

In 6ba8e20, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in bce7efb.


text:
🛑 AceBlock SSI - IPFS endpoint is down

In 3041bd9, AceBlock SSI - IPFS endpoint ($ACEBLOCK_SSI_IPFS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock SSI - IPFS endpoint is back up in 28ddecc.


text:
🛑 Aceblock SSI registration is down

In e7c2eff, Aceblock SSI registration ($ACEBLOCK_SSI_REGISTRATION) was down:

HTTP code: 503
Response time: 13961 ms

Resolved: Aceblock SSI registration is back up in 185ef1f after 11 minutes.


text:
🛑 AceBlock Swagger UI is down

In f19f035, AceBlock Swagger UI ($ACEBLOCK_SWAGGER_UI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AceBlock Swagger UI is back up in e1bb1ce.


text:
ERROR about cv_reader when using MSVD

I converted the video according to the method you provided. I found that some errors occurred in the batch of videos（num_workers=12, 4 were correct and 8 were wrong) , the wrong videos are:
./dataset/msvd/videos_240_h264_keyint_60/Nd45qJn61Dw_0_10.avi
./dataset/msvd/videos_240_h264_keyint_60/5P6UU6m3cqk_57_75.avi
./dataset/msvd/videos_240_h264_keyint_60/PD6eQY7yCfw_32_37.avi
./dataset/msvd/videos_240_h264_keyint_60/77iDIp40m9E_159_181.avi
./dataset/msvd/videos_240_h264_keyint_60/9Wr48VFhZH8_45_50.avi
./dataset/msvd/videos_240_h264_keyint_60/HxRK-WqZ5Gk_30_50.avi
./dataset/msvd/videos_240_h264_keyint_60/UgUFP5baQ9Y_0_7.avi
./dataset/msvd/videos_240_h264_keyint_60/PqSZ89FqpiY_65_75.avi

and I converted these wrong videos to mp4 but got the same error.
I wonder if there is something wrong with the MSVD dataset or cv_reader (I can train normally on MSRVTT).
Your help will be greatly appreciated.

I converted the video according to the method you provided. I found that some errors occurred in the batch of videos（num_workers=12, 4 were correct and 8 were wrong) , the wrong videos are:
./dataset/msvd/videos_240_h264_keyint_60/Nd45qJn61Dw_0_10.avi
./dataset/msvd/videos_240_h264_keyint_60/5P6UU6m3cqk_57_75.avi
./dataset/msvd/videos_240_h264_keyint_60/PD6eQY7yCfw_32_37.avi
./dataset/msvd/videos_240_h264_keyint_60/77iDIp40m9E_159_181.avi
./dataset/msvd/videos_240_h264_keyint_60/9Wr48VFhZH8_45_50.avi
./dataset/msvd/videos_240_h264_keyint_60/HxRK-WqZ5Gk_30_50.avi
./dataset/msvd/videos_240_h264_keyint_60/UgUFP5baQ9Y_0_7.avi
./dataset/msvd/videos_240_h264_keyint_60/PqSZ89FqpiY_65_75.avi

and I converted these wrong videos to mp4 but got the same error.
I wonder if there is something wrong with the MSVD dataset or cv_reader (I can train normally on MSRVTT).
Your help will be greatly appreciated.

Hello, i met the same problem on MSVD dataset. Do you solve this problem?? How to solve this problem??

I converted the video according to the method you provided. I found that some errors occurred in the batch of videos（num_workers=12, 4 were correct and 8 were wrong) , the wrong videos are:
./dataset/msvd/videos_240_h264_keyint_60/Nd45qJn61Dw_0_10.avi
./dataset/msvd/videos_240_h264_keyint_60/5P6UU6m3cqk_57_75.avi
./dataset/msvd/videos_240_h264_keyint_60/PD6eQY7yCfw_32_37.avi
./dataset/msvd/videos_240_h264_keyint_60/77iDIp40m9E_159_181.avi
./dataset/msvd/videos_240_h264_keyint_60/9Wr48VFhZH8_45_50.avi
./dataset/msvd/videos_240_h264_keyint_60/HxRK-WqZ5Gk_30_50.avi
./dataset/msvd/videos_240_h264_keyint_60/UgUFP5baQ9Y_0_7.avi
./dataset/msvd/videos_240_h264_keyint_60/PqSZ89FqpiY_65_75.avi

and I converted these wrong videos to mp4 but got the same error.
I wonder if there is something wrong with the MSVD dataset or cv_reader (I can train normally on MSRVTT).
Your help will be greatly appreciated.

I find that it can run normally on MSRVTT.  Does the MSVD dataset have some problems?

并没有得到解决，所以我只做了MSRVTT的实验o(╥﹏╥)o

I converted the video according to the method you provided. I found that some errors occurred in the batch of videos（num_workers=12, 4 were correct and 8 were wrong) , the wrong videos are:
./dataset/msvd/videos_240_h264_keyint_60/Nd45qJn61Dw_0_10.avi
./dataset/msvd/videos_240_h264_keyint_60/5P6UU6m3cqk_57_75.avi
./dataset/msvd/videos_240_h264_keyint_60/PD6eQY7yCfw_32_37.avi
./dataset/msvd/videos_240_h264_keyint_60/77iDIp40m9E_159_181.avi
./dataset/msvd/videos_240_h264_keyint_60/9Wr48VFhZH8_45_50.avi
./dataset/msvd/videos_240_h264_keyint_60/HxRK-WqZ5Gk_30_50.avi
./dataset/msvd/videos_240_h264_keyint_60/UgUFP5baQ9Y_0_7.avi
./dataset/msvd/videos_240_h264_keyint_60/PqSZ89FqpiY_65_75.avi

and I converted these wrong videos to mp4 but got the same error.
I wonder if there is something wrong with the MSVD dataset or cv_reader (I can train normally on MSRVTT).
Your help will be greatly appreciated.

I find that it can run normally on MSRVTT. Does the MSVD dataset have some problems?

可以加个微信吗？我也是研究字幕生成的，我也有一些伙伴在群里，要不要一起加个群，以后大家可以一起讨论下？
发自我的iPhone
------------------ Original ------------------
From: Mc @.>
Date: Wed,Aug 14,2024 2:17 PM
To: acherstyx/CoCap @.>
Cc: 习泽宇 @.>, Comment @.>
Subject: Re: [acherstyx/CoCap] ERROR about cv_reader when using MSVD (Issue#12)

Refer to https://github.com/acherstyx/CoCap/issues/13.

authors: NCU-MC Xiyu-AI acherstyx

repo: acherstyx/CoCap


text:
soundSensor.ino changed

I have added ambulance sensor to the program.

reviewing!

@sumukhacharya03 could you please come meet me in room 001?


text:
Knowledge - Ingestion time field overlaps with the "Unsupported" status.

Steps to reproduce the problem:

Create agent with knowledge files that are unsupported like .xlsx files.

Notice that Ingestion time field overlaps with the "Unsupported" status when ingestion status is reported for these files.

we changed the UX a bit, this should no longer be revelant

This issue is not relevant anymore.

repo: acorn-io/acorn


text:
Some solvers ind CMF can yield negative source strength results

including:

FISTA
Split-Bregman
LassoLars
LassoLarsBIC(?)

Reproduce with:
import acoular
from acoular import L_p, Calib, MicGeom, Environment, PowerSpectra, \
RectGrid, MaskedTimeSamples,BeamformerCMF, SteeringVector

# other imports
from os import path
from pylab import figure, imshow, colorbar, title

# files
datafile = 'example_data.h5'
calibfile = 'example_calib.xml'
micgeofile = path.join( path.split(acoular.__file__)[0],'xml','array_56.xml')

#octave band of interest
cfreq = 4000

t1 = MaskedTimeSamples(name=datafile)
t1.start = 0 # first sample, default
t1.stop = 16000 # last valid sample = 15999
invalid = [1,7] # list of invalid channels (unwanted microphones etc.)
t1.invalid_channels = invalid

t1.calib = Calib(from_file=calibfile)

m = MicGeom(from_file=micgeofile)
m.invalid_channels = invalid

g = RectGrid(x_min=-0.6, x_max=-0.0, y_min=-0.3, y_max=0.3, z=0.68,
             increment=0.05)
env = Environment(c = 346.04)
st = SteeringVector(grid=g, mics=m, env=env)
f = PowerSpectra(time_data=t1,
               window='Hanning', overlap='50%', block_size=128, #FFT-parameters
               ind_low=8, ind_high=16) #to save computational effort, only
               # frequencies with indices 8..15 are used
bcmf = BeamformerCMF(freq_data=f, steer=st, method='LassoLars')

figure(1,(10,6))
smap = bcmf.synthetic(cfreq,1)
print(smap.min())

For sklearn solvers there is a new positive parameter which can be set to enforce strictly non-negative results.

repo: acoular/acoular


text:
Use Sonar GitHub Action

Remove downloading sonar build exexutable and running action manually, instead use out of box action provided by Sonar source
https://github.com/marketplace/actions/sonarcloud-scan

There is no SONAR action out of the box available for classic dot net projects. The default SONAR action oly works on ubuntu image and can be used for dotnet core projects but not for windows based dotnet projects

repo: acrolinx/sidebar-sdk-dotnet


text:
The horse rider case

A special question in Path Check that trickles down elsewhere

This is mostly done. The formulas on row 475 of Lookups1 are complex. If PA25 is N/A, then it uses PA22. If PA29 is N/A, then PA26. To sanely match this behavior, we need the unit tests to be working, and vary some of these things.


text:
Debug logs need review

One example
ActionsSdkAssistant.prototype.ask = function (inputPrompt, possibleIntents, dialogState) {
debug('ask: inputPrompt=%s, possibleIntents=%s,  dialogState=%s',
inputPrompt, possibleIntents, dialogState);
all variables are Objects, so the output is pretty meaningless if the variables are not "stringified"

Thanks. Will fix in next update. Also, see new method signature: ActionsSdkAssistant.prototype.ask = function (inputPrompt, dialogState)

authors: entertailion rotero


text:
"Unable to reserve cache with key"

Hi, I've got a workflow where I'm using this action, however, it doesn't seem to be caching anything. I get the error:
Unable to reserve cache with key Linux-xmltv-cache, another job may be creating this cache.

Obviously, because of it, subsequent jobs do not find any caches.
Cache usage (full workflow):
      - name: XMLTV cache
        id: cache-xmltv
        uses: actions/cache@v2
        with:
          path: /config/.xmltv/cache
          key: ${{ runner.os }}-xmltv-cache

Link to workflow

Hi @fugkco, this is usually a symptom indicating the creation of the cache failed.  To avoid wasting unnecessary time creating the cache if it already exists, the cache is first "reserved", then the runner creates the compressed tar with the cache contents, and finally that is uploaded to the server.  If something breaks between when the cache is reserved and when the upload finishes, the cache gets stuck in the "reserved" state.  You will then see the "Unable to reserve cache...another job may be creating this cache" message until that cache is automatically removed (it could take up to 24 hours but work is underway to reduce this delay).
Instead of waiting that long, you can also change the cache key, for example:
key: ${{ runner.os }}-xmltv-cache-v2

After making this change, take a look at the Post Cache step on the next run.  It will show an error if there is any issue creating the cache.
If I had to guess, the failure may have to do with the cache being rooted at /config.  If you see any errors related to that path, try moving that folder to within the GitHub workspace (this is the default folder each step runs in).

I realise that I saw this response, and used gave it a cache key, which worked, but I forgot to reply and close this issue. Anyway, so it worked. Thanks for the help!

@dhadka what is the point of creating a new cache key? If this is what it seems, the best course of action would be to ignore the error. You start X concurrent jobs, they all produce the same artifact, then they try to save it using the same cache key. You need only one of these to succeed.
Ideally, you should be able to run only one of those jobs, then make the other X-1 wait on it to get its artifact from the cache, but AFAIK, there is no easy way to do this.

authors: dhadka fugkco mmomtchev

repo: actions/cache


text:
Restore original behavior of cache-hit output

#1262
#1466

As described in #1466, #1404 broke workflows that relied on the previous behavior of cache-hit being an empty string when there was a cache miss:
if: ${{ steps.cache-restore.outputs.cache-hit }}

If cache-hit is an empty string, this would work as expected. When cache-hit is false, this is a non-empty string and treated as "true".
Actions outputs do not support proper boolean values, and we can't guarantee how users are interpreting this string output.
This PR reverts #1404 and updates the README to clarify all possible values of cache-hit:

'true' if there's an exact match
'false' if there's a cache hit with a restore key
'' if there's a cache miss

This is likely confusing to users, but we should maintain the existing behavior to avoid breaking existing workflows.

@joshmgross
Thank you 🙏

@joshmgross
Thank you!

This is likely confusing to users, but we should maintain the existing behavior to avoid breaking existing workflows.

I can see the reasoning here but this shouldn't mean a weird behaviour should be kept just because it's breaking. IMO having it in the release notes and making the necessary change in version number should be enough, which was already done. Having this PR merged feels like a step in the wrong direction and there should be a plan to properly handle that breaking change.

IMO having it in the release notes and making the necessary change in version number should be enough, which was already done.

Per https://semver.org/, a breaking change needs to be a major version bump (i.e. v5 of this action).
I agreed that we should fix this confusing behavior, but we're not ready to create a new major version of this action.
https://github.com/actions/cache/issues/1466#issuecomment-2400480945

authors: AnimMouse Jason3S joshmgross ulgens


text:
[docs] remove star search from yarn.lock

i dunno, some recent change to cache caused the **/yarn.lock lookup to start failing for me. I just have a standard project with a yarn.lock in the top level and this fixed it.

@lookfirst Changing the path of yarn file in example may not help everyone. That path is for the yarn.lock file which can be at different location for different projects.
Thanks for your contribution.

@lookfirst Can you try it again with the current recommendation and latest version of cache? It seems to work fine for me

authors: Phantsure lookfirst


text:
Update Android NDK to r25b LTS

Tool name
Android NDK
Tool license
Same as before
Add or update?

[ ] Add
[X] Update

Desired version
25.1.8937393
Approximate size
No response
Brief description of tool
No response
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Virtual environments where you need the tool

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[X] Ubuntu 22.04
[X] macOS 10.15
[X] macOS 11
[X] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Will be deployed next week.

Deployed

authors: Javernaut mikhailkoliada

repo: actions/runner-images


text:
Timeout waiting for SSH.

Description
Syntax-only check passed. Everything looks okay.
Show Packer Version
1.9.1
Build ubuntu2204 VM
==> azure-arm.build_vhd: Running builder ...
==> azure-arm.build_vhd: Getting tokens using client secret
==> azure-arm.build_vhd: Getting tokens using client secret
azure-arm.build_vhd: Creating Azure Resource Manager (ARM) client ...
==> azure-arm.build_vhd: Warning: You are using Azure Packer Builder to create VHDs which is being deprecated, consider using Managed Images. Learn more https://www.packer.io/docs/builders/azure/arm#azure-arm-builder-specific-options
==> azure-arm.build_vhd: Getting source image id for the deployment ...
==> azure-arm.build_vhd: Creating resource group ...
==> azure-arm.build_vhd: Validating deployment template ...
==> azure-arm.build_vhd: Deploying deployment template ...
==> azure-arm.build_vhd: Getting the VM's IP address ...
==> azure-arm.build_vhd: Waiting for SSH to become available...
==> azure-arm.build_vhd: Timeout waiting for SSH.
==> azure-arm.build_vhd:
==> azure-arm.build_vhd: Deleting individual resources ...
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Current hosted runner is version: '2.305.0'
Is it regression?
n/a
Expected behavior
no errors
Actual behavior
it's broken
Repro steps
see description

@sivakolisetti this means there are the problem in your setup, packer can not connect to a newly created vm, it is outside of our scope

@sivakolisetti as it already said, it looks like issue not on our side. Our builds work fine the same time. Please provide more info about what are you tried to do.

Hello @sivakolisetti!
I am forced to close the issue due to the fact that it is not repeated in our infrastructure and on test runners. If you still have any questions related to this problem, then you can ask them here - we can always reopen the issue. In case of other problems, please open a new issue.
Separately, I can add that the described problem can be both transitive and related to local settings in your organization, but not with the work of the scripts themselves at the moment.

@mikhailkoliada is correct our vnet has does not internet connectivity once vm created. We created separate vnet then actions running successfully .
thanks for guys who reply this issue.

Hi @sivakolisetti, what did you add to the created vnet to accomodate ssh from the created vm? Did you need to add an outbound or inbound ssh rule?
Thanks.

authors: erik-bershel greadtm mikhailkoliada sivakolisetti


text:
Heavy cache miss count

Description:
A large collection of "cache miss" and only a handful of "cache hit".
Action version:
actions/setup-node@v3
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:
    - name: Setup node
      uses: actions/setup-node@v3
      with:
        node-version: 18
        cache: 'npm'

Repro steps:
    - name: Setup node
      uses: actions/setup-node@v3
      with:
        node-version: ${{ inputs.node-version }}
        cache: 'npm'

    - run: npm ci --verbose
      shell: bash

Expected behavior:
A restore of previously downloaded artifacts
Actual behavior:
npm http fetch GET 200 https://registry.npmjs.org/locate-path 2237ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/json-stable-stringify-without-jsonify 2232ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz 777ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/update-browserslist-db 2424ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/mime-types 2300ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/lodash.merge 2297ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/json-schema-traverse 2291ms (cache miss)
npm http fetch GET 200 https://dl.fontawesome.com/signed/fontawesome-pro/npm/fortawesome/fontawesome-common-types/6.4.0/fortawesome-fontawesome-common-types-6.4.0.tgz?created=xxx&expires=xxx&source=xxx&signature=xxx 6157ms (cache miss)

tons and tons of cache miss.

Like why was yocto-queue a hit but not fontawesome?

So this is being reported because you get charged for using bandwidth when using Font Awesome. Sadly in our case - the basic example used here does not properly cache all items and I'm not following why. We get a hit restoring the cache blob, but it appears its quite small to what I expect.
/home/runner/.npm
Received 24691139 of 24691139 (100.0%), 30.4 MBs/sec
Cache Size: ~24 MB (24691139 B)
Cache restored successfully
Cache restored from key: node-cache-Linux-npm-912ac010d33c9c8d3694535a04cbea9be930f020a6b09d60b707ae2ce2d4db8b

I know this action does NOT cache node_modules, but then I struggle to understand the benefit I'm gaining here. Its clearly caching and restoring something, but since it doesn't cache the thing that costs us money then :(
We then get billed for overages and Font Awesome support just tells us to follow this guide which we clearly do.

So the large collection of misses was resolved by manually deleting/purging all the caches from that repository. The default cache key I assume is the lockfile hash, so why this happened - I'm not sure. Now the only thing not caching is the links from a private registry.
This private registry (Font Awesome) does not appear to ever successfully cache itself. I assume since the non node_modules cache is HTTP responses and these expire after 20 minutes. So the cache is respecting the TTL and thus becoming misses on builds.
I don't know if this means we should go back to rolling our own cache - (caching node_modules, skipping install if cache hit, etc) or just missing something here.

Hello, @iBotPeaches ! Thanks for reporting this issue, we will take a closer look and see what can be done :)

I too am experiencing this same issue with FontAwesome. It is having a large impact on us and our budgets with overage charges.
We have many repositories that are facing this issue.
The only difference that I can see is that we are using yarn rather than npm.

@codepuncher - I dug into this a lot with FA, who honestly just kept redirecting me back to official GitHub docs on caching. You can't really use setup-node, etc with FA Pro and expect to keep your bandwidth.
We mixed two forms of cache now.
    - name: Setup node
      uses: actions/setup-node@v3
      with:
        node-version: ${{ inputs.node-version }}
        cache: 'npm'

    - uses: actions/cache@v3
      id: npm-cache
      with:
        path: node_modules
        key: ${{ inputs.node-version }}-node-${{ hashFiles('**/package-lock.json') }}
        restore-keys: ${{ inputs.node-version }}-node-${{ hashFiles('**/package-lock.json') }}

    - run: npm ci
      if: steps.npm-cache.outputs.cache-hit != 'true'
      working-directory: ${{ inputs.directory }}
      shell: bash

(this is in a composite action)
We restore cache using regular setup-node, but then we attempt to restore a 1-1 cache based on the exact hash of the lock file. If we find a match for that, we skip npm ci - which is what would eventually hit FA Pro servers again and bleed bandwidth due to what I described above.
If that cache is a miss, we already restored the npm global cache (the 1st cache) so our cold/miss timing is still pretty fast as we are just installing the FA Pro, the private packages and whatever caused the miss (new version, etc)
This has kept us under the 2gb bandwidth limit for Sept.

Hello @iBotPeaches,
The problem is not reproducible
1st run https://github.com/akv-demo/setup-node-test/actions/runs/7251833566/job/19755011576#step:4:9
Run npm ci --verbose
...
npm http fetch GET [20](https://github.com/akv-demo/setup-node-test/actions/runs/7251833566/job/19755011576#step:4:21)0 https://registry.npmjs.org/font-awesome/-/font-awesome-4.7.0.tgz 93ms (cache miss)
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 357ms

2nd run
Run npm ci --verbose
...
npm http fetch POST [20](https://github.com/akv-demo/setup-node-test/actions/runs/7251833566/job/19755025500#step:4:21)0 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 127ms

The idea of action is to cahce ~/.npm directory which contains downloaded packages. Caching the node_modules does not seem a good idea because they its content can be out of sync.
It is impossible to find the exact reason why the ~/.npm directory does not contain the whole bunch of packages but in the theory it can be caused the repository has outdated package-lock.json.
Did it help?

Hi @dsame,
My experience was more for the Pro/Private option of FA, which does not appear to be cachable. Your test appears to be the public version of Font Awesome - so I don't think a true comparable replicable test.
I'm not saying my method is the cleanest, but it did solve our immediate problem of exceeding rate limits

Since my comment I've yet to hit a month where we exceed limits. I don't want to cache node_modules, but I did what I had to stay under usage limits.

Hello @iBotPeaches, thank you for the clarification, i supposed there's something related to the private package and wanted to get the confirmation.
Nevertheless, it puzzles me with the dependencies from https://registry.npmjs.org are not cached as well despite I expect them to be stored in ~/.npm folder and cached.
I understand you've solved the problem with the workaround, but can you please double check does the build on the local host has to reload the awesomefonts npm with its dependencies? I still suspect the action has some flaw with the generating .npmrc config that might cause the problem.
In case if the local build has the same problem or you don't have a time, please let us to close the issue with "it does not relate to the action"

Hi @dsame,
I ran a few tests in a private repo like your configuration. With each change I got closer to our affected application, but each time I re-ran it - it seemed fine.
npm verb cli /opt/hostedtoolcache/node/18.19.0/x64/bin/node /opt/hostedtoolcache/node/18.19.0/x64/bin/npm
npm info using npm@10.2.3
npm info using node@v1[8](https://github.com/sourcetoad/actions-node-test/actions/runs/7264253745/job/19791375113#step:5:9).1[9](https://github.com/sourcetoad/actions-node-test/actions/runs/7264253745/job/19791375113#step:5:10).0
npm verb title npm ci
npm verb argv "ci" "--loglevel" "verbose"
npm verb logfile logs-max:[10](https://github.com/sourcetoad/actions-node-test/actions/runs/7264253745/job/19791375113#step:5:11) dir:/home/runner/.npm/_logs/2023-[12](https://github.com/sourcetoad/actions-node-test/actions/runs/7264253745/job/19791375113#step:5:13)-19T15_53_14_549Z-
npm verb logfile /home/runner/.npm/_logs/2023-12-19T15_53_14_549Z-debug-0.log
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 494ms
npm info run @fortawesome/fontawesome-common-types@6.5.1 postinstall node_modules/@fortawesome/fontawesome-common-types node attribution.js
npm info run @fortawesome/fontawesome-svg-core@6.5.1 postinstall node_modules/@fortawesome/fontawesome-svg-core node attribution.js
npm info run @fortawesome/fontawesome-common-types@6.5.1 postinstall { code: 0, signal: null }
npm info run @fortawesome/fontawesome-svg-core@6.5.1 postinstall { code: 0, signal: null }

{
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^6.5.1",
    "@fortawesome/pro-solid-svg-icons": "^6.5.1"
  }
}

@fortawesome:registry=https://npm.fontawesome.com
//npm.fontawesome.com/:_authToken=${FONTAWESOME_NPM_AUTH_TOKEN}

This worked fine. So I removed my workaround on the actual affected application and it was immediate misses again. Unfortunately the difference between the real affected application and this sample is 98,000~ different node packages.
So at this point - I can't replicate in my test, but my real application continues to replicate. I'm happy with a workaround, but I understand if you can't replicate - you can't fix.
I'll close this and if others stumble upon this with FA Pro and have the same bandwidth overage issue - maybe they can use my sample that works and/or discover the root cause themselves.
Thanks

@iBotPeaches / @dsame / @codepuncher - Is this issue still occurring using actions/setup-node@v4?

Occuring for me!

Hello Everyone, Thank you for bringing this to our attention. We understand your concerns regarding Font Awesome and the caching behavior you're seeing.
Based on our investigation, we were unable to reproduce the issue you're experiencing with actions/setup-node@v4. The caching mechanism in actions/setup-node is designed to cache local npm dependencies (i.e., those fetched from the npm registry), but it does not extend to external resources like CDN assets. Since CDN resources such as Font Awesome are not part of the npm ecosystem, they aren't included in the npm cache and therefore are not cached by the GitHub Actions workflow.
Regarding your concern about npm dependencies from https://registry.npmjs.org not being cached as expected, please note that actions/setup-node caches the npm package cache (~/.npm), but it does not directly cache the node_modules directory. This means that dependencies fetched from the npm registry are cached in the npm cache folder, but they may not be restored directly into the node_modules folder on every run. If local caching is properly configured, there should be no need to reload Font Awesome (or other dependencies) on every build.
For more information on the caching behavior in GitHub Actions and actions/setup-node, you can refer to the following documentation:
GitHub Actions Cache Documentation
setup-node Action Documentation
We hope this helps clarify the caching behavior. Please feel free to reach out if you have any further questions or need additional assistance!

Thank you @iBotPeaches for the suggested workaround. We will give it a try tomorrow.
Our workaround was to use Kits as a way to reduce the significant bandwidth usage caused by our CI/CD because of pro icon packages. Our plan was to configure the Kit to include only the specific icons used in our project, which would have allowed us to uninstall the larger packages containing all icons. Unfortunately, this idea also proved to be a dead end since Kits are not supported in React Native.
As a result, we're left with either caching the entire node_modules folder as you suggested, or disabling CI/CD entirely... for the sake of icons 🤷♂
We hope this caching issue can be addressed soon.

Hello @iBotPeaches, Thank you for your response, and apologies for the delay. You're absolutely right that the behavior around CDN assets like Font Awesome isn't fully addressed in the current documentation. It’s also true that the caching mechanism in actions/setup-node is primarily designed for npm dependencies, not node_modules and external CDN assets.
I’m glad to hear that your workaround caching node_modules alongside setup-node is working well for you. I agree that using a cold cache to handle potential misses is a solid approach, as it ensures both your npm dependencies and external assets are reliably available. However, please note that caching node_modules or external CDN assets (e.g., Font Awesome) is not implemented by default to avoid inconsistencies across environments (OS, Node.js versions).
We are actively working to update the documentation to provide more clarity on caching behaviors, and we’ll definitely consider your feedback when addressing future caching use cases.
If anything changes or you need further assistance, please don't hesitate to reach out.

Hello @iBotPeaches, Thanks for the response! The setup-node action already keys the cache based on variables such as Node.js version, OS, and architecture. This ensures that the cache is environment-specific, helping to avoid issues with mismatched dependencies and improving cache hit rates across different Node.js versions and platforms.
We are proceeding to close this issue, but we will keep it open for a documentation update in the setup-node action.

authors: MostefaKamalLala aparnajyothi-y codepuncher dsame dusan-trickovic gzurbach iBotPeaches

repo: actions/setup-node


text:
Update/Add azure cli to 2.1.0

Tool information

Tool name: az cli
Add or update? update
Desired version: 2.1.0

Area for Triage:

Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[x ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[x ] Windows Server 2019

Can this tool be installed during the build?
Don't know
Are you willing to submit a PR?
No

Hi @gregorybleiker!
Az-Cli 2.1.0 is already rolling out. You can find it in pre-release readmes here:
https://github.com/actions/virtual-environments/releases

Feel free to reopen the issue if you have any concerns.
Thanks!

Can I use this in my pipelines somehow? What is the ETA for the rollout?

authors: gregorybleiker miketimofeev

repo: actions/virtual-environments


text:
Update arithmeticController.js

modificamos suma2

listo...

guardamos

repo: actionsdemos/calculator


text:
⚠ Processors has degraded performance

In c248588, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 94 ms

Resolved: Processors performance has improved in 411518f.

repo: acumenlabs/status-page


text:
⚠ Processors has degraded performance

In b6e451f, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 95 ms

Resolved: Processors performance has improved in 26696f8.


text:
⚠ Processors has degraded performance

In 6bb5d44, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: Processors performance has improved in e49e544.


text:
Update Qleverfile.pubchem

Fixing error:
qlever index --system=native

To enable autocompletion, run the following command, and consider adding it to your `.bashrc` or `.zshrc`:

eval "$(register-python-argcomplete qlever)" && export QLEVER_ARGCOMPLETE_ENABLED=1

Command: index

echo '{ "languages-internal": [], "prefixes-external": [""], "ascii-prefixes-only": false, "num-triples-per-batch": 1000000 }' > pubchem.settings.json
ulimit -Sn 1048576; zcat pubchem.additional-ontologies.nt.gz nt.2024-02-03/*.nt.gz | IndexBuilderMain -F ttl -f - -i pubchem -s pubchem.settings.json --stxxl-memory 10G | tee pubchem.index-log.txt

No file matching "pubchem.additional-ontologies.nt.gz" found

Did you call `qlever get-data`? If you did, check GET_DATA_CMD and INPUT_FILES in the QLeverfile

@eltonfss @Qup42 The problem is that these ontologies are many and have to be downloaded from various websites, which change frequently. Hence the comment at the top of the Qleverfile. As is, the file should be removed from INPUT_FILES, as @eltonfss suggests. Right now, I am trying out whether it still works. If it does, I will make the change and close this.

@eltonfss There is now a brand-new Qleverfile for PubChem, which also dowloads the latest version of the ontologies, see 589d5b97ba2ffb68681423c3d844e4c249ae094a . Please try it out and let me know if it works for you.

authors: eltonfss hannahbast

repo: ad-freiburg/qlever-control


text:
Infinite Loop Trying to run listdir Example

When attempting to run the listdir example https://github.com/adafruit/Adafruit_CircuitPython_BLE_File_Transfer/blob/main/examples/ble_file_transfer_listdirs.py it's resulting in getting stuck in an infinite loop inside of here: https://github.com/adafruit/Adafruit_CircuitPython_BLE_File_Transfer/blob/main/adafruit_ble_file_transfer.py#L147 I added print statements and can see that the value of read is always 0. I also printed buffer and it was filled with \x00s
It's unclear to me if this worked in the past and perhaps the workflow API was changed, but the library was not, or perhaps this functionality was not ever working.
I tested with a Feather Sense with BLE Workflow enabled and an Itsy Bitsy nrf52840 as the client running the listdir script. I did originally notice this behavior first on the PC using Blinka_Bleio, but then moved off the PC to using two MCUs and confirmed seeing the same infinite looping behavior.

Did you figure this out?

I think I understand it a bit better, but wouldn't say I figured it out completely.
When everything is working as expected this library does run successfully on the micro-controller and does not infinitely loop.
It does still have an infinite loop when run on a PC under blinka_bleio. So this could be closed and if there is a desire to support that environment then an issue could be created over in that repo. For now I've moved to just using bleak module directly without blinka and blinka_bleio and I'm making progress that way.
The times that I did see this library infinite loop on the MCU (mentioned in the original comment), I believe it was due to the "server device" (the one running BLE workflow) had gotten into a "bad state" ultimately caused by partially broken implementations while working on the PC / blinka_bleio version. I did not document specific examples that led to the bad state, but I did experience it a few times. I found that using ctrl+C / ctrl+D to restart the code.py or REPL would typically get it back into a good state. I think maybe once I ended up having to unplug / replug to let it fully reboot.
I'll close this one.

authors: FoamyGuy tannewt


text:
Different pool, different ConnectionManager

Update ConnectionManager, to support multiple different pools at the same time.
Testing steps:
Have a device with onboard WiFi and either a ESP32SPI or WIZNET5K
Connect both and make requests on both and see that they are from different devices.
You can also use a WIZNET5K create it's request session first, and then disconnect it and verify the other device still works.

@anecdata here's another one that would be awesome if you could test (with everything else in main)

Since you easily have the ability to see where requests are coming from

Looks good from a testing perspective, maybe someone wants to code review.

@dhalbert once this is merged, I can take care of any conflicts and open up the 3x use new socketpool PRs

@justmobilize is this a bugfix version bump, or minor or major version bump, in terms of behavior?

@dhalbert I would consider it minor. It shouldn't break anything as it's only changing how pseudo private data is stored.

authors: anecdata dhalbert justmobilize


text:
rtc libary in visual studio code

hey,
i am trying to youse the exampel  code . but every time i get this error .
i think dear is a libary to short in visual studio code but i dont now witch.( i already installed TinywireM).
can enyone help me?
this is  the errors i get:
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'void USI_TWI_Master_Initialise()':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:64:3: error: 'PORT_USI' was not declared in this scope
PORT_USI |=
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:66:11: error: 'PIN_USI_SDA' was not declared in this scope
<< PIN_USI_SDA); // Enable pullup on SDA, to set high as released state.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:69:11: error: 'PIN_USI_SCL' was not declared in this scope
<< PIN_USI_SCL); // Enable pullup on SCL, to set high as released state.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:71:3: error: 'DDR_USI' was not declared in this scope
DDR_USI |= (1 << PIN_USI_SCL); // Enable SCL as output.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:74:3: error: 'USIDR' was not declared in this scope
USIDR = 0xFF; // Preload dataregister with "released level" data.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:3: error: 'USICR' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:17: error: 'USISIE' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:33: error: 'USIOIE' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:76:17: error: 'USIWM1' was not declared in this scope
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:76:33: error: 'USIWM0' was not declared in this scope
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:77:17: error: 'USICS1' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:77:33: error: 'USICS0' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:78:17: error: 'USICLK' was not declared in this scope
(1 << USICLK) | // Software stobe as counter clock source
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:79:17: error: 'USITC' was not declared in this scope
(0 << USITC);
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:3: error: 'USISR' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:17: error: 'USISIF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:33: error: 'USIOIF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:49: error: 'USIPF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:81:17: error: 'USIDC' was not declared in this scope
(1 << USIDC) |    // Clear flags,
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:82:19: error: 'USICNT0' was not declared in this scope
(0x0 << USICNT0); // and reset counter.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'unsigned char USI_TWI_Start_Transceiver_With_Data(unsigned char*, unsigned char)':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:13: error: 'USISIF' was not declared in this scope
(1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:29: error: 'USIOIF' was not declared in this scope
(1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:45: error: 'USIPF' was not declared in this scope
he terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it.

Executing task: platformio run <

Processing uno (platform: atmelavr; board: uno; framework: arduino)
Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/atmelavr/uno.html
PLATFORM: Atmel AVR 2.2.0 > Arduino Uno
HARDWARE: ATMEGA328P 16MHz, 2KB RAM, 31.50KB Flash
DEBUG: Current (simavr) On-board (simavr)
PACKAGES:

framework-arduino-avr 5.0.0
toolchain-atmelavr 1.50400.190710 (5.4.0)
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 9 compatible libraries
Scanning dependencies...
Dependency Graph
|--  1.10.0
|   |--  1.1.0
|   |--  1.0
|--  1.0.12
Building in release mode
Compiling .pio/build/uno/lib9ac/TinyWireM_ID797/USI_TWI_Master.cpp.o
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'void USI_TWI_Master_Initialise()':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:64:3: error: 'PORT_USI' was not declared in this scope
PORT_USI |=
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:66:11: error: 'PIN_USI_SDA' was not declared in this scope
<< PIN_USI_SDA); // Enable pullup on SDA, to set high as released state.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:69:11: error: 'PIN_USI_SCL' was not declared in this scope
<< PIN_USI_SCL); // Enable pullup on SCL, to set high as released state.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:71:3: error: 'DDR_USI' was not declared in this scope
DDR_USI |= (1 << PIN_USI_SCL); // Enable SCL as output.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:74:3: error: 'USIDR' was not declared in this scope
Compiling .pio/build/uno/liba29/Wire/utility/twi.c.o
USIDR = 0xFF; // Preload dataregister with "released level" data.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:3: error: 'USICR' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:17: error: 'USISIE' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:75:33: error: 'USIOIE' was not declared in this scope
USICR = (0 << USISIE) | (0 << USIOIE) | // Disable Interrupts.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:76:17: error: 'USIWM1' was not declared in this scope
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:76:33: error: 'USIWM0' was not declared in this scope
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:77:17: error: 'USICS1' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:77:33: error: 'USICS0' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:78:17: error: 'USICLK' was not declared in this scope
(1 << USICLK) | // Software stobe as counter clock source
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:79:17: error: 'USITC' was not declared in this scope
(0 << USITC);
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:3: error: 'USISR' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:17: error: 'USISIF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:33: error: 'USIOIF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:80:49: error: 'USIPF' was not declared in this scope
USISR = (1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:81:17: error: 'USIDC' was not declared in this scope
(1 << USIDC) |    // Clear flags,
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:82:19: error: 'USICNT0' was not declared in this scope
(0x0 << USICNT0); // and reset counter.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'unsigned char USI_TWI_Start_Transceiver_With_Data(unsigned char*, unsigned char)':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:13: error: 'USISIF' was not declared in this scope
(1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:29: error: 'USIOIF' was not declared in this scope
(1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:161:45: error: 'USIPF' was not declared in this scope
(1 << USISIF) | (1 << USIOIF) | (1 << USIPF) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:162:13: error: 'USIDC' was not declared in this scope
(1 << USIDC) |    // Prepare register value to: Clear flags, and
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:163:15: error: 'USICNT0' was not declared in this scope
(0x0 << USICNT0); // set USI to shift 8 bits i.e. count 16 clock edges.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:229:7: error: 'PORT_USI' was not declared in this scope
PORT_USI &= ~(1 << PIN_USI_SCL);         // Pull SCL LOW.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:229:26: error: 'PIN_USI_SCL' was not declared in this scope
PORT_USI &= ~(1 << PIN_USI_SCL);         // Pull SCL LOW.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:230:7: error: 'USIDR' was not declared in this scope
USIDR = *(msg++);                        // Setup data.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:234:7: error: 'DDR_USI' was not declared in this scope
DDR_USI &= ~(1 << PIN_USI_SDA); // Enable SDA as input.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:234:25: error: 'PIN_USI_SDA' was not declared in this scope
DDR_USI &= ~(1 << PIN_USI_SDA); // Enable SDA as input.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:266:7: error: 'DDR_USI' was not declared in this scope
DDR_USI &= ~(1 << PIN_USI_SDA); // Enable SDA as input.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:266:25: error: 'PIN_USI_SDA' was not declared in this scope
DDR_USI &= ~(1 << PIN_USI_SDA); // Enable SDA as input.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:272:9: error: 'USIDR' was not declared in this scope
USIDR = 0xFF; // Load NACK to confirm End Of Transmission.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:274:9: error: 'USIDR' was not declared in this scope
USIDR = 0x00; // Load ACK. Set data register bit 7 (output for SDA) low.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'unsigned char USI_TWI_Master_Transfer(unsigned char)':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:295:3: error: 'USISR' was not declared in this scope
USISR = temp;                          // Set USISR according to temp.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:297:16: error: 'USISIE' was not declared in this scope
temp = (0 << USISIE) | (0 << USIOIE) | // Interrupts disabled
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:297:32: error: 'USIOIE' was not declared in this scope
temp = (0 << USISIE) | (0 << USIOIE) | // Interrupts disabled
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:298:16: error: 'USIWM1' was not declared in this scope
Compiling .pio/build/uno/lib864/RTClib_ID83/RTClib.cpp.o
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:298:32: error: 'USIWM0' was not declared in this scope
(1 << USIWM1) | (0 << USIWM0) | // Set USI in Two-wire mode.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:299:16: error: 'USICS1' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:299:32: error: 'USICS0' was not declared in this scope
(1 << USICS1) | (0 << USICS0) |
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:300:16: error: 'USICLK' was not declared in this scope
(1 << USICLK) | // Software clock strobe as source.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:301:16: error: 'USITC' was not declared in this scope
(1 << USITC);   // Toggle Clock Port.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:304:5: error: 'USICR' was not declared in this scope
USICR = temp; // Generate positve SCL edge.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:305:14: error: 'PIN_USI' was not declared in this scope
while (!(PIN_USI & (1 << PIN_USI_SCL)))
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:305:30: error: 'PIN_USI_SCL' was not declared in this scope
while (!(PIN_USI & (1 << PIN_USI_SCL)))
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:309:28: error: 'USIOIF' was not declared in this scope
} while (!(USISR & (1 << USIOIF))); // Check for transfer complete.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:312:10: error: 'USIDR' was not declared in this scope
temp = USIDR;                  // Read out data.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:314:3: error: 'DDR_USI' was not declared in this scope
DDR_USI |= (1 << PIN_USI_SDA); // Enable SDA as output.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:314:20: error: 'PIN_USI_SDA' was not declared in this scope
DDR_USI |= (1 << PIN_USI_SDA); // Enable SDA as output.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'unsigned char USI_TWI_Master_Start()':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:324:3: error: 'PORT_USI' was not declared in this scope
PORT_USI |= (1 << PIN_USI_SCL); // Release SCL.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:324:21: error: 'PIN_USI_SCL' was not declared in this scope
PORT_USI |= (1 << PIN_USI_SCL); // Release SCL.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:330:22: error: 'PIN_USI_SDA' was not declared in this scope
PORT_USI &= ~(1 << PIN_USI_SDA); // Force SDA LOW.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:336:9: error: 'USISR' was not declared in this scope
if (!(USISR & (1 << USISIF))) {
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:336:23: error: 'USISIF' was not declared in this scope
if (!(USISR & (1 << USISIF))) {
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp: In function 'unsigned char USI_TWI_Master_Stop()':
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:349:3: error: 'PORT_USI' was not declared in this scope
PORT_USI &= ~(1 << PIN_USI_SDA); // Pull SDA low.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:349:22: error: 'PIN_USI_SDA' was not declared in this scope
PORT_USI &= ~(1 << PIN_USI_SDA); // Pull SDA low.
^
Compiling .pio/build/uno/lib631/SimpleDHT_ID849/SimpleDHT.cpp.o
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:350:21: error: 'PIN_USI_SCL' was not declared in this scope
PORT_USI |= (1 << PIN_USI_SCL);  // Release SCL.
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:351:12: error: 'PIN_USI' was not declared in this scope
while (!(PIN_USI & (1 << PIN_USI_SCL)))
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:358:9: error: 'USISR' was not declared in this scope
if (!(USISR & (1 << USIPF))) {
^
/home/jeroen/.platformio/lib/TinyWireM_ID797/USI_TWI_Master.cpp:358:23: error: 'USIPF' was not declared in this scope
if (!(USISR & (1 << USIPF))) {
^
*** [.pio/build/uno/lib9ac/TinyWireM_ID797/USI_TWI_Master.cpp.o] Error 1
============================================= [FAILED] Took 1.02 seconds =============================================
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

Why are you using TinyWireM? This is a Wire replacement for ATtiny microcontrollers that do not have a real I2C port. It instead relies on the “universal serial interface” (USI) to provide this functionality.
The Uno does not have an USI, but it does have a regular I2C port: you should use the regular Wire library with it. Note that RTClib.cpp uses the TinyWireM library only when being compiled for the ATtiny85, which is clearly not your case.

hey ,
i am not using the tinywirelibary i just addit the libary.
this is the exapel code i am yousing:
RTC_DS1307 rtc;
char daysOfTheWeek[7][12] = {"Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"};
void setup () {
Serial.begin(9600);
#ifndef ESP8266
while (!Serial); // wait for serial port to connect. Needed for native USB
#endif
if (! rtc.begin()) {
Serial.println("Couldn't find RTC");
Serial.flush();
abort();
}
if (! rtc.isrunning()) {
Serial.println("RTC is NOT running, let's set the time!");
// When time needs to be set on a new device, or after a power loss, the
// following line sets the RTC to the date & time this sketch was compiled
rtc.adjust(DateTime(F(DATE), F(TIME)));
// This line sets the RTC with an explicit date & time, for example to set
// January 21, 2014 at 3am you would call:
// rtc.adjust(DateTime(2014, 1, 21, 3, 0, 0));
}
// When time needs to be re-set on a previously configured device, the
// following line sets the RTC to the date & time this sketch was compiled
// rtc.adjust(DateTime(F(DATE), F(TIME)));
// This line sets the RTC with an explicit date & time, for example to set
// January 21, 2014 at 3am you would call:
// rtc.adjust(DateTime(2014, 1, 21, 3, 0, 0));
}

What do you mean by “i just add it the libary”? You should not need to “add” TinyWireM anywhere to compile this example. If you can't prevent platform.io to try to compile it anyway, you should ask for help in a forum dedicated to platform.io.

What do you mean by “i just add it the libary”? You should not need to “add” TinyWireM anywhere to compile this example. If you can't prevent platform.io to try to compile it anyway, you should ask for help in a forum dedicated to platform.io.

ok thank you for the help.

@edgar-bonet this is a feature in platformio where all dependancies are compiled, even when dependancies are not referenced in code for a platform, we've let @ivankravets know, for now folks have to manually remove the unused library

Sorry for this issue. Please use lib_ignore option and skip libraries from a build process.

This provided some more clarity for me on the TinyWireM issue in VS Code:
https://github.com/platformio/platformio-core/issues/3543
Here is an example of the suggested fix in the platformio.ini file:
[env:featheresp32]
platform = espressif32
board = featheresp32
framework = arduino
lib_ignore = TinyWireM

authors: edgar-bonet ivankravets jeroen24 joshlikespics ladyada

repo: adafruit/RTClib


text:
Noob qstn

Can this be installed to sit on a website rather than a server?
How would I do that?

You would install this onto a server. The server will then expose an IP address:port to the public.
You can access that IP address:port in your web browser.

I'm afraid I can't help with this issue through GitHub issues. These issues are just for making suggestions or submitting bug reports with Staytus. I cannot help individually with installing or running the application in the wild. I'd suggest trying posting your issues on a site like Stack Overflow.

authors: SKSJeffrey TomasHurtz adamcooke

repo: adamcooke/staytus


text:
🛑 mastodon-relay.moew.science is down

In 8bb68c5, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in 638770b after 29 minutes.


text:
🛑 relay.froth.zone is down

In 7f563fb, relay.froth.zone (https://relay.froth.zone/actor) was down:

HTTP code: 503
Response time: 100 ms

Resolved: relay.froth.zone is back up in 60b155d after 23 minutes.


text:
🛑 relay.fedi.agency is down

In d93d22d, relay.fedi.agency (https://relay.fedi.agency/actor) was down:

HTTP code: 502
Response time: 533 ms

Resolved: relay.fedi.agency is back up in ba983fe.


text:
🛑 relay.homunyan.com is down

In 3662ded, relay.homunyan.com (https://relay.homunyan.com/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.homunyan.com is back up in f5a4338.


text:
🛑 relay.wagnersnetz.de is down

In 71039ac, relay.wagnersnetz.de (https://relay.wagnersnetz.de/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.wagnersnetz.de is back up in 4146357.


text:
🛑 relay.wagnersnetz.de is down

In e2f72dd, relay.wagnersnetz.de (https://relay.wagnersnetz.de/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.wagnersnetz.de is back up in 0a816a8.


text:
🛑 relay.masto.social is down

In 73e53b6, relay.masto.social (https://relay.masto.social/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.masto.social is back up in 8247ee2.


text:
🛑 relay.mstdn.live is down

In 20aa525, relay.mstdn.live (https://relay.mstdn.live/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.mstdn.live is back up in 609ea60 after 1 hour, 4 minutes.


text:
🛑 relay.fedi.agency is down

In f621722, relay.fedi.agency (https://relay.fedi.agency/actor) was down:

HTTP code: 502
Response time: 4564 ms

Resolved: relay.fedi.agency is back up in 67e4fdb after 15 minutes.


text:
README: Update setup/development instructions

Verify that the current docs are correct and improve if we can.

@gauntface Current workflow I'm using:
Development:
nodemon server/app.js && gulp dev`
Production build:
gulp
Otherwise, we drop anything to do with AppEngine that's already in there. Anything else worth adding?

repo: addyosmani/app-shell


text:
Is development stopped on this extension?

I want to know that is development stopped on this extension?
Asking since last update is more than 2 years ago.

Hi @akash07k - it's a good question.
It's true that no new functionality has been added for a while, but I believe the debugger still works in the latest version of VSCode and I'm happy to accept PRs for any bug fixes or new features people want to add.

Ok, so does the last release work well with latest versions of VS Code?
Also, will we get code autocompletion support?
On 8/3/2022 1:28 AM, Dave Holoway wrote:

Hi @akash07k https://github.com/akash07k - it's a good question.
It's true that no new functionality has been added for a while, but I
believe the debugger still works in the latest version of VSCode and
I'm happy to accept PRs for any bug fixes or new features people want
to add.
—
Reply to this email directly, view it on GitHub
https://github.com/adelphes/android-dev-ext/issues/135#issuecomment-1203156498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQWBM3SALXED3PEGTCP4G3VXF4WPANCNFSM54R2VT6A.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, the current release of the Android extension still works with the latest version of VSCode.
It includes:

Debugging support (breakpoints, stepping, evaluate local variables, etc)
View logcat
Java code-completion

Also, will we get code autocompletion support?
Java code-completion for standard Android libraries should work. Pressing ctrl + space should bring up relevant identifiers if they don't appear automatically.

repo: adelphes/android-dev-ext