Is it a way to access options within the tailwind.js file from vue SFC?

I wanted to access the colors object in tailwind.js from vue SFC in order to apply changes to css variables base on component props.
I could just declare these variables in a global css file and assign the colors manually, but what's the point then of having them stored in tailwind.js besides of generating class utilities?
Probably there is a better way of doing this but I would like to do something like this:
props: {
    color: {
      type: String
    }
  },
computed: {
    style() {
      return {
        "--card-color": this.$tailwind.colors[this.color]
      };
    }
  }

.card {
  --card-color: white;
  background-color: var(--card-color);
}

Why not use Tailwind's config()?

Where? In the javascript? It will undefined. You can't assign config to a css variable it doesn't compute to a color

On your (Post)CSS:
.card {
  background-color: config(colors.nameOfYourColor);
}

I know but you can't change it dinamically from javascript. Somebody mention to add the object colors to Vue prototype, thanks anyway, i think I'll do that

Ahhhhh. I misunderstood the question. Sorry 😅

Hi there I know this post is closed but I think this might still be useful to mention as I struggled myself to find the information in the TailwindCSS doc :
https://tailwindcss.com/docs/configuration/#referencing-in-javascript
Cheers and I hope you don't see this comment as a noise on this backlog..?


update packages

:white_check_mark: Build TheIdServer 4.4.1-fix-dependencies1-0075 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/f105fec55f by @)


against discord Terms of service

Just letting the creator and this program users know, that this is against discord ToS and can cause you're account in getting banned from Discord

And yes @WaterTheDev I saw what you wrote at line 227-228, but still why would you publish such a thing?

imagine following tos

imaging not 🙄

i can tell that you're a furry and a discord mod

kys lmao
.

Just letting the creator and this program users know, that this is against discord ToS and can cause you're account in getting banned from Discord

it's obvious it's against tos but the chances of discord doing anything is low, just don't be stupid using the program and don't blatantly show people ur self botting and you will most likely be fine

Just letting the creator and this program users know, that this is against discord ToS and can cause you're account in getting banned from Discord

it's obvious it's against tos but the chances of discord doing anything is low, just don't be stupid using the program and don't blatantly show people ur self botting and you will most likely be fine

well, if someone will report this to Discord, I'm 99.9% sure that they will take actions and warn / disable the user account. why taking any risk for this and braking the ToS of Discord?

Just letting the creator and this program users know, that this is against discord ToS and can cause you're account in getting banned from Discord

it's obvious it's against tos but the chances of discord doing anything is low, just don't be stupid using the program and don't blatantly show people ur self botting and you will most likely be fine

well, if someone will report this to Discord, I'm 99.9% sure that they will take actions and warn / disable the user account. why taking any risk for this and braking the ToS of Discord?

i've seen loads of people self botting in the past, they've been reported, and their accounts are still up right now, since a fair amount of people do tos violation stuff like this (not even counting the amount of people who have been reported for using betterdiscord / powercord, considered against tos for modifiying the client)
it's probably hard for discord to keep up with all the reports they recieve for these type of tos violations + people can do as they wish and it does state in the program it is against tos, so it's mainly the self-botter's fault if they get banned for blatantly self-botting infront of others; discord can only have proof of self-botters from message links, ids, etc (screenshots etc do not count as, ofc, they can be easily edited)
however, when a message gets deleted discord's servers no longer store that message link, message id etc, so the self-botter can easily just delete the message id and then there's pretty much hardly any proof left for discord to obtain about someone self-botting to get their account deleted, warned, disabled etc.
in reality, it's more of a "don't be stupid using the program and you will be fine" situation, but your issue / concern about breaking tos is completely reasonable 😄

@dromzeh It's true they have thousands of tickets to take handle of, and sometime even missing stuff. but once you send a good report with all the information needed and everything related to the case most of the time they will actually take care of it. after it, users come to discord with new accounts and literally spamming then and asking why i got banned for doing "nothing". those kids are mostly skidz(s), and when someone like @WaterTheDev is coming here and uploading  those kind of things to skidz It's not ok.

urm u should already know the punishments of using a selfbot if u read the ToS and if u didn't read tos u should not be on discord.


The forwardAsync method is not available

Although the forwardAsync method appears in the documentation and code, I believe it is not included in the latest build... or could I be mistaken about something? Thank you very much.

You a right! Thank you very much for creating this issue. I will fix that with the next version.

v0.28.0 is available

Thank you!!


Convert Favourites to Kotlin

Part of #237

Done in #394

Sorry for error, this issue is still open

Done in #404


RUM-1924: Use tracestate header to supply vendor-specific information

What does this PR do?
This PR adds tracestate header with Datadog-specific information in case of TRACECONTEXT tracing. This header will contain the following Datadog-specific tags:

p - parent ID
s - sampling decision
o - origin, if exists. In case of instrumentation with RUM, it will have rum value.

Full spec https://www.w3.org/TR/trace-context/#tracestate-header
iOS counterpart https://github.com/DataDog/dd-sdk-ios/pull/1536
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1694 (c4a7806) into develop (7e80c37) will decrease coverage by 0.14%.
The diff coverage is 22.92%.

@@             Coverage Diff             @@
##           develop    #1694      +/-   ##
===========================================
- Coverage    83.73%   83.59%   -0.14%
===========================================
  Files          463      463
  Lines        15896    15934      +38
  Branches      2371     2377       +6
===========================================
+ Hits         13310    13319       +9
- Misses        1951     1978      +27
- Partials       635      637       +2

Files
Coverage Δ

...datadog/android/okhttp/trace/TracingInterceptor.kt
82.03% <91.67%> (+1.39%)
:arrow_up:

.../datadog/opentracing/propagation/W3CHttpCodec.java
3.30% <0.00%> (-1.88%)
:arrow_down:

... and 16 files with indirect coverage changes


Artifact Resolution not using Torrents

When trying to setup this plugin locally on TeamCity 10 to test it, I've had no luck getting the artifacts to resolve via torrent, it just seems to fallback to HTTP. However, I've verified that the file itself is seeded and can be downloaded via the torrent obtained from TeamCity.
The artifact I'm trying to use is just an arbitrary binary file that's 80 MB, which should pass the 10 MB default threshold. I've also modified MIN_SEEDERS_COUNT_TO_TRY to default to 0 (0 should throw 'no seeders', but this should mean 1 is fine).
My teamcity properties file is:
torrent.transport.enabled=true
torrent.download.enabled=true
torrent.enabled=true

I've pulled the plugin and modified it to add logging, and I'm seeing that the agent itself seems to be failing to use the torrent protocol when the following returns null:
TorrentTransportFactory.java#L249
     final String torrentRelativePath = myTorrentsForArtifacts.get(parsedArtifactUrl.getArtifactPath());

From my understanding, it would normally receive this list from a teamcity-ivy.xml, but from what I see, 'parseArtifactsList' never gets called. This is a clean TeamCity 10 setup, and the torrent plugin is the only plugin I've manually installed.
Is there an additional step required that I'm missing? Is there also documentation beyond just the blog post?
Let me know if you need any other information from my end.

Sorry, I found that torrent plugin is not compatible with teamcity 10.x and 2017.1. We will update documentation.


Generic camera view widget

Let's hold off on using this for the road camera for now and just do driver view in this PR. It'll be easier to review and test.

got it

No need to make a UIVision class, just put it all in the widget. Don't worry about duplicating code, since we'll move the road camera to use this after the PR. I'm thinking the steps are:

merge this for driver view
I'll finish up #20825
move road cam to Qt

Continued in #21063


Agent Manager API Authentication

Prove to the agent manager that you have been authorized to use the Agent Manager.
Register your identity with the manager, with some means of authenticating subsequent requests (e.g. a credential written to HALO)
Authenticate Agent CRUD operations.

landed in prod agenthosting and staging in dxos.


Update Index

Edit Doctype
Add lang attr.
Add alt attr.

Please note that these wont reflect on a new project right away. We sync from this repo at certain points

@sachinma
Okay! Thanks for the Info! :)


ubunntu14 install pyspider fail

I am using sudo pip install pyspider to install.
python version is 2.7.
The installation stopped "wsgidav".
`
Requirement already up-to-date: pyspider in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: Flask>=0.10 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Requirement already up-to-date: Jinja2>=2.7 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Downloading/unpacking chardet>=2.2 (from pyspider)
Downloading chardet-2.3.0.tar.gz (164kB): 164kB downloaded
Running setup.py (path:/tmp/pip_build_root/chardet/setup.py) egg_info for package chardet
warning: no files found matching 'COPYING'
warning: no files found matching '*.html' under directory 'docs'
warning: no files found matching '*.css' under directory 'docs'
warning: no files found matching '*.png' under directory 'docs'
warning: no files found matching '*.gif' under directory 'docs'

Requirement already up-to-date: cssselect>=0.9 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Downloading/unpacking lxml from https://pypi.tuna.tsinghua.edu.cn/packages/4f/3f/cf6daac551fc36cddafa1a71ed48ea5fd642e5feabd3a0d83b8c3dfd0cb4/lxml-3.6.4.tar.gz#md5=6dd7314233029d9dab0156e7b1c7830b (from pyspider)
Downloading lxml-3.6.4.tar.gz (3.7MB): 3.7MB downloaded
Running setup.py (path:/tmp/pip_build_root/lxml/setup.py) egg_info for package lxml
Building lxml version 3.6.4.
Building without Cython.
Using build configuration of libxslt 1.1.28
warning: no previously-included files found matching '*.py'

Requirement already up-to-date: pycurl in /usr/local/lib/python2.7/dist-packages (from pyspider)
Requirement already up-to-date: pyquery in /usr/local/lib/python2.7/dist-packages (from pyspider)
Downloading/unpacking requests>=2.2 from https://pypi.tuna.tsinghua.edu.cn/packages/ea/03/92d3278bf8287c5caa07dbd9ea139027d5a3592b0f4d14abf072f890fab2/requests-2.11.1-py2.py3-none-any.whl#md5=b4269c6fb64b9361288620ba028fd385 (from pyspider)
Downloading requests-2.11.1-py2.py3-none-any.whl (514kB): 514kB downloaded
Requirement already up-to-date: tornado>=3.2 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Requirement already up-to-date: Flask-Login>=0.2.11 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Requirement already up-to-date: u-msgpack-python>=1.6 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Requirement already up-to-date: click>=3.3 in /usr/local/lib/python2.7/dist-packages (from pyspider)
Downloading/unpacking six>=1.5.0 from https://pypi.tuna.tsinghua.edu.cn/packages/c8/0a/b6723e1bc4c516cb687841499455a8505b44607ab535be01091c0f24f079/six-1.10.0-py2.py3-none-any.whl#md5=3ab558cf5d4f7a72611d59a81a315dc8 (from pyspider)
Downloading six-1.10.0-py2.py3-none-any.whl
Downloading/unpacking wsgidav (from pyspider)
Downloading WsgiDAV-2.1.0.zip (142kB): 142kB downloaded
Running setup.py (path:/tmp/pip_build_root/wsgidav/setup.py) egg_info for package wsgidav
`

Is this the full log? I don't see any failure here.


HMR of next.config.js is broken for all examples using server.js

note: This issue is specifically for HMR of next.config.js requiring a server restart.
Bug report
The next.js/examples using server.js do not HMR next.config.js
To Reproduce

Use one of the examples which includes a server.js
Modify next.config.js while server is running
HMR does not occur

Expected behavior
HMR of next.config.js
System information

OS: macOS, Windows, Linux
Version of Next.js: 8.0.1

+1 for this.
We have a fairly simple custom server, not too different from the examples, and when making a code change the console will display "[HMR] bundle rebuilding". The network shows requests for both the update check, and the patched component, and both look correct to me.
http://localhost:3000/_next/static/webpack/51255de6f7bd9c29505b.hot-update.json:
{"h":"9160ba30e149d0ed69d9","c":{"static/development/pages/index.js":true}}

http://localhost:3000/_next/static/webpack/static/development/pages/index.js.51255de6f7bd9c29505b.hot-update.js:
webpackHotUpdate("static/development/pages/index.js",{
/***/ "./src...
[expected updated source]

But it will just hang on "[HMR] bundle rebuilding" and never apply the changes.

+1
HMR has suddenly stopped working for existing and new projects across different next.js versions. Perhaps one of the dependencies released an update that is causing this issue for any new npm installation of next.js?

@marlonicus @elishaterada this issue has nothing to do with HMR of pages, it's aimed at changing next.config.js requiring a server restart.
Please provide a clear and concise reproduction in a new issue. Preferably in a repository.

@timneutkens you are right this wasn't the HMR about the page changes, I will see if there is a similar report.

@elishaterada I'm not aware of a similar report, so you can create a new issue, we need a reproduction to be able to debug this issue though 🙏 Thank you!

HMR has suddenly stopped working for existing and new projects across different next.js versions.

I have the same issue.
@marlonicus @elishaterada do you find any solution?
my project stucked and it's hard to investigate the cause.

@samanmohamadi this issue has nothing to do with HMR of pages, it's aimed at changing next.config.js requiring a server restart. I'm not aware of a similar report, so you can create a new issue, we need a reproduction to be able to debug this issue though 🙏 Thank you!

@marlonicus Seeing something similar here. I make changes and save them, and will see the console log "[HMR] bundle rebuilding", but only the changes prior to the save are rendered, so I'm one save behind.

@dreamthink this issue has nothing to do with HMR of pages, it's aimed at changing next.config.js requiring a server restart. I'm not aware of a similar report, so you can create a new issue, we need a reproduction to be able to debug this issue though 🙏 Thank you!
FYI I'm not a robot, I just keep repeating myself for the third time 😅

Once again we'd be super happy to look into these issues! But they're impossible to debug from our side if you don't provide a reproduction.

@samanmohamadi @dreamthink - Afraid I haven't found a solution. I've checked out the example custom server projects, and it looks like HMR is working for them. So I believe the title of this issue is incorrect and the problem likely lies on my end (as per usual).
@timneutkens I'll hopefully have a stab at putting together a reproduction of the issue this week; although I suspect that if I manage to narrow it down that far, I'll probably figure out what is causing the issue in the first place.

Looks like @dfvalero has narrowed down the issue and provided a temporary fix:
https://github.com/zeit/next.js/issues/6497

@marlonicus This issue is specifically for HMR of next.config.js requiring a server restart.

🤦♂ Oh right... You'd think I might have figured that out by now based off @timneutkens comments.

Is this also affecting everybody's production deployments? My Links are no longer working and I can't figure out why.
I see the same thing as @marlonicus in my dev environment. After deploying I no longer see any console output (as would be expected), and I do see a successful network request for my page (eg, about.js), but nothing changes on my screen.
I would say that there's a broader issue of the HMR not providing any debug hooks. It's nice when it works but incredibly frustrating to deal with when it doesn't work.

@timneutkens
Unfortunately, they're difficult to debug from our side, too, because there is such little debug output from within the nextjs / nowjs cli. I'm seeing the same issues as @marlonicus , my routing is not working, and I have absolutely no information about what's going on & no clear way to enable verbose logging from next or now

I would say that there's a broader issue of the HMR not providing any debug hooks. It's nice when it works but incredibly frustrating to deal with when it doesn't work.

Well it's incredibly hard to even know what that would entail, as there really is no way to tell what issue you're running into without having a reproduction. If we have a reproduction it'd be easier to add debug output, if at all needed. We have a super extensive test suite covering HMR, and the only issues I've seen come up with HMR recently are either around customizing the next.config.js and adding plugins (next-css has one issue I believe).
What logging would you like specifically?
We'd be super happy to look into any issues, a reproduction would be a tremendous help though, as we still have no idea what you're doing in your app that causes HMR to not work.

in my case, removing all imported CSS files fix the issue.
I have removed all import path/to/style.css and put all those files in head section of parent page:
<Head>
<link href="static/style.css" rel='stylesheet' />
</Head>

The current amount of information that we have is:

Next: "[HMR] bundle rebuilding"
Network request
Compilation on the server-side (successful)
200 Network response
Nothing happens and no output from HMR

In addition to that, the issue I made in #6554 means that step no. 3 takes a really long time, which makes it even more difficult to track down the bug.

Well it's incredibly hard to even know what that would entail, as there really is no way to tell what issue you're running into without having a reproduction.

That's so untrue, there are many ways to debug code without reproductions, although I agree that nextjs' design choices make reproductions the only way to debug (that's not a good thing). Most bugs from other frameworks (react, apollo, mui, etc.) don't require a reproduction case because those frameworks output debug logging information or enough clues to get you on track. Needing to do a full reproduction to isolate a bug is really rare in my experience, especially for a full framework with complex integrations
Desirable debug output would be something like (I don't know the intimates of HMR so I'm mostly guessing -- that's why I'm using next):

HMR is retrieving "about.js"
HMR is requesting hot-reloader.json
HMR received hot-reloader.json
HMR is applying updates
HMR failed to update [Error code: ]

There are also clues that might help to isolate the issue.
Things that do work:

Requesting /about directly by entering the url into the browser (that works)

a next/Link with as=/some-page/hello and href=/some-page?param="hello" does work (while a Link with /about does not work)

Things that don't work:

a next/Link with href=/about

@ajhool
Even without reproductions I agree and you are right about needing more debug information.

HMR is retrieving "about.js"
HMR is requesting hot-reloader.json
HMR received hot-reloader.json
HMR is applying updates
HMR failed to update [Error code: ]

The only problem is that it's "noisy" and there's no extendedDebugOutput mode to enable extra debug info output. But 'noisy' should not be a legit reason to hold back on solving an issue.
Since this issue is reoccurring, it may be more helpful to solve it with comprehensive error reporting instead of fixing single issues.
Maybe extendedDebugOutput is a valid feature request.

@ajhool
Even without reproductions I agree and you are right about needing more debug information.

HMR is retrieving "about.js"
HMR is requesting hot-reloader.json
HMR received hot-reloader.json
HMR is applying updates
HMR failed to update [Error code: ]

The only problem is that it's "noisy" and there's no extendedDebugOutput mode to enable extra debug info output. But 'noisy' should not be a legit reason to hold back on solving an issue.
Since this issue is reoccurring, it may be more helpful to solve it with comprehensive error reporting instead of fixing single issues.
Maybe extendedDebugOutput is a valid feature request to consider.

@timneutkens can you tell me which files should I check to find the problem and solve the issue hopefully

@timneutkens I think that the only clean way to restart the server after next.config.js change is to use nodemon there is the possibility of doing the same thing as in bin/next but that will be the same as telling the user to update packages/next/server/lib/start-server.js directly and it's not clean at all. So should I make a PR to update the custom server examples to use nodemon

We've removed this feature and have added a warning that is printed to the console that tells you that you must reboot the server yourself.

in my case, removing all imported CSS files fix the issue.
I have removed all import path/to/style.css and put all those files in head section of parent page:
<Head>
<link href="static/style.css" rel='stylesheet' />
</Head>

So random, thanks this fixed next rebuilding the app on every link click :/


Add Gitter

What about adding gitter support?
https://gitter.im/deployphp/deployer

:+1:

Added on dff3dbf99a0f4824ee269bda299dd16ed6375190


tf code question?

Good works! I have two question about your tf codes.
The first:
In the paper, query vector is calculated using previous layer's hidden state rather than the concatenated pre-layer's memory and hidden state. However, in the tf code, I found the query vector is calculated the same as key vector and value vector.

The second:
Each layers has memory tensor with shape [mem_len, batch_size, d_model].  When calculating query, key and value vector, the input vector of tf.layers.dens is the concatenation of current layer's memory and pre-layers' output. which seems be conflict with the paper. Besides, why stop gradient in _cache_mem method rather than in rel_multihead_attn, the later seems to make better sense.

mark


Annotate generated classes with @Generated

Generated classes should be annotated with javax.annotation.Generated.
Similar to how AutoValue annotates its generated classes:
@ Generated("com.google.auto.value.processor.AutoValueProcessor")

Thank you for calling this to my attention, Shahar :) Can you review the code?
I invited you as a collaborator. Here is the invitation link: https://github.com/google/CallBuilder/invitations
Here is the PR: https://github.com/google/CallBuilder/pull/6


apt-get: replace deprecated "force-yes" option with equivalent settings

Connects to #300

LGTM 👍


Fresh profile leaks auth info from original profile

my default profile has the pr-pinger installed
created a fresh new profile
have not installed extensions
there is a prompt to login for pr-pinger (which isn't installed)

@sandy081 what's the best mechanism for reacting to profile change? Over here I append these menu items:
https://github.com/microsoft/vscode/blob/989f0dfa694d7a153d960185ad36cd48aadbd081/src/vs/workbench/services/authentication/browser/authenticationService.ts#L598-L643
I wanna basically "recompute" these on profile change.


DBZ-7761 Add orai18n.jar to improve Oracle NLS character set support

https://issues.redhat.com/browse/DBZ-7761

/packit test --labels oracle


ci: Create workflow dispatch for releases (PROJQUAY-3310)

Enable workflow dispatch for the release job

/cherrypick 3.7

/cherrypick redhat-3.7


How to remove a control from a FormGroup?

Hey,
I'm trying to figure out how to remove a control from a FormGroup.
I didn't find any function like removeControl or something like that on the FormGroup object.
There is an addAll function which i'm using to add a control dynamically, and because it's dynamic, I also need to remove it dynamically.
Please help,
Thank you

Don't add controls dynamically, instead add them all at the start and disable those that you don't need. If you need to add groups, you can use a FormArray whichg supports adding and removing.

@kuhnroyal I can't agree with you on this one.
It comes to code readability for this issue.
I prefer to check that a control doesn't exist rather than checking if it's disabled.
Because it is actually doesn't need to be there.
If I check for disabled, than the next person that reads that code may think that the control is visible on the screen but disabled.
In my case it is not visible and it should be gone from the form group.
Angular (which this package take a lot of inspiration from) has these two function
group.addControl()
group.removeControl()

So I really don't see any reason why this package shouldn't do the same.

I agree, this is just how I had to use it until now as I don't want to rebuild the whole form group every time.
Although this is mostly up to the use-case. You always have to know what you are doing, a disabled control can be readyOnly, disabled or actually removed in Flutter depending on your needs. It is the same for angular.

Hi @naamapps,
You are completely right when asking for a method for deleting a control from a group. I haven't included it yet because I haven't needed it before. I usually add features when I need them or other developers need them.
Normally when I want to ignore a value (or pretend it does not exist) in a Form, I disable it, that way the value of the control will not be included in the value of the FormGroup and the validations will not take into account the disabled controls, so is like it does not exists in the Form. And later when I wanted to include it back I just enable it: myControl.markAsEnabled().  For example:
// the email is disabled
final from = FormGroup({
   'name': FormControl<String>(value: 'John'),
   'email': FormControl<String>(value<EMAIL_ADDRESS>disabled: true)
});

print(form.value) // output: {'name': 'John'}

form.control('email').markAsEnabled();

print(form.value) // output: {'name': 'John', 'email'<EMAIL_ADDRESS>
That's the approach that I usually use, but of course, maybe in some cases somebody else could be wanted to remove completely the control from the Group, that's totally fine, and as you said it should be a reasonable behavior.
So please if you still need to completely remove the control, just let me know and I will include the functionality in the next release.
Thanks again for your support and Best regards.

Hey @joanpablo, thanks for your reply.
It would be great if you could add it to the next release please.
For now I will settle for the disabled solution, but in terms of code readability, it is not obvious that the control is not appearing on screen and its not actually disabled, but ignored.
Thanks a lot!

I will include it in the next release. Thanks to all of you.

Hi @naamapps,
I have just released the version 10.3.0. In this version you can remove a control from a group by its name.
Please test it and if you find another issue don't hesitate to reopen this one or create a new one.
Best regards


connection reset by peer

Connection was reset by peer. Then I had to restart the chatp-telegram program, and it could work again.
This error occurred very often.
2022/12/08 22:59:08 Post "https://api.telegram.org/bot888888888:Secrete_Token/getUpdates": read tcp <IP_ADDRESS>:46326-><IP_ADDRESS>:443: read: connection reset by peer
2022/12/08 22:59:08 Failed to get updates, retrying in 3 seconds...

Does it have something to do with Telegram's offical server or the program needs a proxy to access Telegram?
I saw a pull request about adding socks5 proxy from here: https://github.com/m1guelpf/chatgpt-telegram/pull/38
I saw another request about adding http proxy from here: https://github.com/m1guelpf/chatgpt-telegram/issues/34
I don't know if there is anyone else who has the same issue like me.

Is it possible to add a command to manually restart the service?


widget.py - TypeError: can't convert float to int

Re this thread:
https://forums.adafruit.com/viewtopic.php?f=47&t=186239
Added a dump of the values just before this line:
https://github.com/adafruit/Adafruit_CircuitPython_DisplayIO_Layout/blob/48b512a391732c03aff8556a0a2d688777e672a9/adafruit_displayio_layout/widgets/widget.py#L230
thusly:
print(self._anchored_position[0], self._anchor_point[0], self._bounding_box[2], self._bounding_box[0])

and get:
6.0 0.0 93 0

So some of the values are float making the result also float. displayio.Group.x requires int.

Interesting. I'm not sure why it was able to run successfully in the past.
anchored_position should generally be a tuple of ints since it represents a pixel location on the display. There are several places where the double divided by // operator is used convert the results of dividing to an int. Maybe there one or more spots where I missed that and it's dividing with /
No matter how it got the float into anchored_position though the Widget should handle it more gracefully. I think we can convert to int here before setting the value of x and y properties on the Group instance. https://github.com/adafruit/Adafruit_CircuitPython_DisplayIO_Layout/blob/48b512a391732c03aff8556a0a2d688777e672a9/adafruit_displayio_layout/widgets/widget.py#L231-L240
I can look into this more and make a PR for it tonight. There is a similar (but not exact same) issue resolved by one of the current PRs so I'll check that out tonight as well.

I did a quick test of simply adding a final int cast in the assignment:
self.x = int(

and same for self.y, and it fixed it.
But if this indicating an issue somewhere else, then might not be best fix.

Off the top of my head I think it indicates a possible bug in the Touch Deck code. But if that does exist I'm not sure why it would have ever run in the past, so possibly there is nothing needing fixing in there after all.
I do think adding the int cast like you did is a good solution. Even if there is a bug elsewhere causing float values to get set to the anchored_position I think Widget should handle it more gracefully. Someone could do something like:
widget.anchor_point = (0.5, 0.5)
widget.anchored_position = (180.0, 140.0)

And I think we should not crash in that case ideally, which the int cast should allow us to avoid.


⚠ Cioos National CKAN has degraded performance

In 7eb3688, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 9537 ms

Resolved: Cioos National CKAN performance has improved in 5ddb825 after 5 minutes.


Iam facing issue with the bot composer like(Local host 3980 not working: error message: timeout) when i run my bot after creating some dilaogs. My bot composer version is 1.4. I created 11 dialogs . Is there any limitation for the creation of the dialogs @KoradaRajesh

Describe the bug

Version

Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

HI @HabeebunnishaMohammad The only error is a timeout? It should run with 11 dialogs. Are you able to share your bot (sanitized of personal/sensitive info) in a repository?

Hi @dmvtech. Yes the only error is timeout. No, iam unable to share.

@HabeebunnishaMohammad There should not be an issue with the amount of dialogs, related to timeout. Can you give simple steps on how to reproduce? Without more to go on, there's not much we can do.

@dmvtech Actually when I deleted the dialogs from my composer. It started running again. We I exceed my dialogs above 10. Its showing time out error.

Hi @HabeebunnishaMohammad I am unable to reproduce this, but I tried with version 1.4.1.
Can you please test with 1.4.1 and see if it still has the same issue? If not, can you try with the simple repo I used? If it doesn't reproduce with that, can you please alter it and make it available so that I have a workable repro?

Hi @HabeebunnishaMohammad Can you provide an update?

Hi @dmvtech. Yaa actually I tried doing with 1.4.1. Its not showing any issue like before.


Reduce tolerance for MFCC

test_batch_mfcc fails not only on Windows but also on GPU linux machine.
I suspect this is resulted from the different version of CPU architecture ( amd64-6_85 vs GPU amd64-6_79 Windows amd64-1_) but cannot be sure.
Looking at the error rate, more than 99.9% of elements are within the range of 1e-5 so I think it's safe to reduce it to 1e-4 so that Windows and GPU can pass this test.

Let me double-check: but this seems to indeed be the issue I run into for #593, and in particular why float64 was needed.

I located the cause to torch.log10 producing the different result. https://github.com/pytorch/pytorch/issues/37833
I think for functions that use amplitude_to_DB we can reduce the threshold.

Thanks for opening the issue! Yup, I confirm torch.log10 is where the difference was coming from in #593.

I did further digging and with float64, it is fine. So we can convert the dtype before and passing a Tensor to torch.log10.

Yeah, that's the solution I used here.

@mthrok -- are you suggesting the following?

[ ] test_librosa_consistency can be reactivated
[ ] tests for amplitude_to_DB can be reactivated

@mthrok -- are you suggesting the following?

[ ]  test_librosa_consistency can be reactivated
[ ]  tests for amplitude_to_DB can be reactivated

Yes, if you are fine with that approach, we can do that. I will file an open task for that.

Filed #611

In general it's useful to do a quick check on performance before working with float64 in performance critical sections of this code (I'm assuming that's the case here). It can cause major slowdowns.


Add W|A attribution and trademark info

Suggesting more precise information and proper attribution for the Wolfram|Alpha API. Thanks!

Sure. I'm just happy this thing is available :)
Disregard the build failure.


Adds allArtistSeries for iOS

context_module and owner_type for the all artist series screen on iOS. slack thread here - https://artsy.slack.com/archives/C9SATFLUU/p1598447162147200

Removed context_module because that was a mistake!

:rocket: PR was released in v1.33.0 :rocket:


WIP: ESM Support

Adds support for esm modules

Security Insights
The items listed below may not capture all security relevant changes. Before providing a security review, be sure to review the entire PR for security impact.

(4) Security relevant changes were detected
Watched keyword dangerouslySetInnerHTML in dist/react_with_react_dom.esm.js line(s) ['7901', '8752', '8754', '8954', '8956', '8960', '8963', '8966', '8968', '12437', '21888', '23433', '24314'] added
Watched keyword dangerouslysetinnerhtml in dist/react_with_react_dom.esm.js line(s) ['22875'] added
Watched keyword dangerouslySetInnerHTML in lib/react_with_react_dom.esm.js line(s) ['2866', '3717', '3719', '3919', '3921', '3925', '3928', '3931', '3933', '7402', '16853', '18398', '19279'] added
Watched keyword dangerouslysetinnerhtml in lib/react_with_react_dom.esm.js line(s) ['17840'] added

Action Items

Obtain a security review; reviewer should pay special attention to insights listed above
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.


Greengrass SecureTunneling component crashes with "Unable to open lockfile: /run/lock/devicecl.lock"

Describe the bug
I cannot connect to a secure tunnel via the aws.greengrass.SecureTunneling component, as the component crashes with Unable to open lockfile: /run/lock/devicecl.lock Secure tunnel process completed with exit code: 255.
To Reproduce
1.Install Amazon Linux 2 on a device of your choice (I used a kvm virtual machine).
2.Install the nucleus using automatic provisioning
3.Create a deployment which contains the SecureTunneling component, e.g.
{
   "targetArn":"arn:aws:iot:eu-central-1:[ACC]:thing/[DEVICE]",
   "deploymentName":"testDeployment2",
   "components":{
      "aws.greengrass.SecureTunneling":{
         "componentVersion":"1.0.9",
         "configurationUpdate":{
            "merge":"{\"OS_DIST_INFO\":\"amzn2\"}"
         }
      },
      "aws.greengrass.LogManager":{
         "componentVersion":"2.2.6",
         "configurationUpdate":{
            "merge":"{\"logsUploaderConfiguration\":{\"systemLogsConfiguration\":{\"uploadToCloudWatch\":\"true\",\"minimumLogLevel\":\"INFO\",\"diskSpaceLimit\":\"10\",\"diskSpaceLimitUnit\":\"MB\",\"deleteLogFileAfterCloudUpload\":\"false\"},\"componentLogsConfigurationMap\":{\"com.example.PythonHelloWorld\":{\"minimumLogLevel\":\"INFO\",\"diskSpaceLimit\":\"20\",\"diskSpaceLimitUnit\":\"MB\",\"deleteLogFileAfterCloudUpload\":\"false\"}}},\"periodicUploadIntervalSec\":\"300\"}"
         }
      },
      "aws.greengrass.Cli":{
         "componentVersion":"2.7.0"
      }
   }
}

Create a secure tunnel and select a device as the destination to which the component was deployed. Choose SSH as the service.
Check the logs of the SecureTunneling component on the destination device, e.g. by using sudo cat /greengrass/v2/logs/aws.greengrass.SecureTunneling.log. See "logs" for my complete output.
Try to connect to the tunnel using localproxy and ssh. The connection will timeout.

Expected behavior
I expected the ssh connection to be established.
Actual behavior
The ssh connection could not be established.
Logs

Logs
2022-08-25T14:13:14.727Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [INFO ] 2022-08-25 14:13:14.726 [Thread-1] SecureTunnelingTask - Successfully subscribed to topic: $aws/things/[DEVICE]/tunnels/notify. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.356Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [INFO ] 2022-08-25 14:16:26.356 [Thread-1] SubscribeResponseHandler - Received new tunnel notification message.. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process:. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "key": "replace_with_private_key_file_location",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "jobs": {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: },. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "cert": "replace_with_certificate_file_location",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "file": "/var/log/aws-iot-device-client/aws-iot-device-client.log". {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "type": "STDOUT",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.364 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: 2022-08-25T14:16:26.361Z [WARN] {Config.cpp}: Path replace_with_root_ca_file_location to RootCA is invalid. Ignoring... Will attempt to use default trust store.2022-08-25T14:16:26.361Z [WARN] {FileUtils.cpp}: Permissions to given file/dir path '/tmp/' is not set to recommended value... {Permissions: {desired: 745, actual: 777}}. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "endpoint": "replace_with_endpoint_value",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "level": "ERROR",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "logging": {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: 2022-08-25T14:16:26.361Z [INFO] {Config.cpp}: Successfully fetched JSON config file: {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "thing-name": "replace_with_thing_name",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.365 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "root-ca": "replace_with_root_ca_file_location",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: }. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "csr-file": "replace_with_csr-file-path". {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "template-name": "replace_with_template_name",. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "enabled": true. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "enabled": false,. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "fleet-provisioning": {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: },. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "interval": 300. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.366Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "enabled": false,. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "enabled": false,. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "device-defender": {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.373Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: },. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.367Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.367 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "tunneling": {. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.367Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: },. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.367Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.366 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: "handler-directory": "replace_with_path_to_handler_dir". {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: }. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: 2022-08-25T14:16:26.361Z [ERROR] {Main.cpp}: *** AWS IOT DEVICE CLIENT FATAL ERROR: Error obtaining lockfile: Can not write to lockfile.. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: 2022-08-25T14:16:26.361Z [DEBUG] {Config.cpp}: Did not find a runtime configuration file, assuming Fleet Provisioning has not run for this device. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.374Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [ERROR] 2022-08-25 14:16:26.368 [pool-3-thread-1] SubscribeResponseHandler - Secure Tunneling Process: 2022-08-25T14:16:26.361Z [ERROR] {LockFile.cpp}: Unable to open lockfile: /run/lock/devicecl.lock. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
Unable to parse log message:
2022-08-25T14:16:26.376Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [INFO ] 2022-08-25 14:16:26.376 [pool-3-thread-1] SubscribeResponseHandler - Secure tunnel process completed with exit code: 255. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}

Environment (please complete the following information):

OS: Amazon Linux 2 LTS 2.0.20220719.0
Version: Secure Tunneling Component 1.0.9
Architecture: x86-64
JDK version:  java --version openjdk 11.0.13 2021-10-19 LTS OpenJDK Runtime Environment 18.9 (build 11.0.13+8-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.13+8-LTS, mixed mode, sharing)
Nucleus version: 2.7.0

Additional context
I've already verified that the sudoers file contains the line root    ALL=(ALL:ALL) ALL
A temporary but ugly fix is running chmod 777 /run/lock. This works until the next reboot.
These also seems to be an environment variable to change the path where the lock file is written, but I have no idea how to configure that in the context of the SecureTunneling Component.
I've already created an issue in the Nucleus repository, but was redirect to this repository by the folks there.

Hello, thanks for providing details about your issue. The original motivation for this lockfile behavior was to prevent users from inadvertently starting multiple instances of device client using the same thing name, as they can interfere with each other's MQTT connection, but in some cases, it seems like creating and writing to this file may introduce some problems of its own. I'll investigate this issue and see if we can change the behavior of the init logic and add some exception handling so device client can keep running within its permissible parameters.

Also, I believe this may help you with environment variables: https://docs.aws.amazon.com/greengrass/v2/developerguide/component-recipe-reference.html#lifecycle-setenv-definition


Why don't you share on the marketplace? Is it possible to disallow some routes?

Hi Scott,
I've found this repo which could be helpful in a project I'm currently working on where I need to share an auth session between a Laravel app and an OctoberCMS installation.
I've looked on the marketplace and didn't find it there so I'm asking why? Does it contain some kind of issue or that kind of stuff? Maybe I can help.
Also a little question: is it possible to disallow some routes? Basically I just want to be open the login/logout routes. I know I can prevent users to access it by creating a custom routes.php with the same routes and require it before you're but if it's directly possible in your package, it's nice!

Hi, no this library is pretty stable, I've been using it for ages. As for why I don't publish it, 🤷. This plugin is generally used with Vuetober themes, which are pretty atypical for October. I feel like publishing this on the marketplace wouldn't be useful for most people, and might confuse traditional usage of RainLab.User.
As for enabling / disabling certain routes, I would totally accept a PR for this. The best way to do this would probably be by using config values. Sort of like this, where we're using a config value to enable/disable the API as a whole 👍


Build failure: ueberzugpp

Steps To Reproduce
Steps to reproduce the behavior:

using flakes and home-manager, added to home manager's package. I attached a lockfile

Build log
ueberzugpp>
ueberzugpp>
ueberzugpp> -- Configuring incomplete, errors occurred!
error: builder for '/nix/store/cjfdi947ivzx2pv29d0xpql6rql63a5c-ueberzugpp-2.9.6.drv' failed
       last 10 log lines:
       > -- Found WaylandProtocols: //nix/store/6w627naapy17padgxzkn6w0yzdyjgjwr-wayland-prot
       > CMake Error at /nix/store/sa1yjb7xxrzcbd1bysj3r561vidfxxvb-cmake-3.29.6/share/cmake-
       >   Could NOT find WaylandScanner (missing: WaylandScanner_EXECUTABLE)
       > Call Stack (most recent call first):
       >   /nix/store/sa1yjb7xxrzcbd1bysj3r561vidfxxvb-cmake-3.29.6/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
       >   /nix/store/kdbjfq8zvpzjjxpnp4r8xc65bs2bfn2f-extra-cmake-modules-5.116.0/share/ECM/find-modules/FindWaylandScanner.cmake:74 (find_package_handle_standard_args)
       >   CMakeLists.txt:150 (find_package)
       >
       >
       > -- Configuring incomplete, errors occurred!
       For full logs, run 'nix log /nix/store/cjfdi947ivzx2pv29d0xpql6rql63a5c-ueberzugpp-2.9.6.drv'.
error: 1 dependencies of derivation '/nix/store/z0fss25gkzf1mg28vr5my9v9dmw9ws5x-home-manager-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rjgiid561gw90nla0plxhpw1ymbkl1p0-home-manager
-generation.drv' failed to build

Additional context
I switched back to ueberzug which builds fine.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.45, NixOS, 24.11 (Vicuna), 24.11.20240814.c3aa7b8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/store/sfycwi72zfjsspidinx56ajaiffpyh17-source`

flake version:
 • Updated input 'nixpkgs':
        'github:nixos/nixpkgs/a58bc8ad779655e790115244571758e8de055e3d' (2024-08-11)
      → 'github:nixos/nixpkgs/c3aa7b8938b17aebd2deecf7be0636000d62a2b9' (2024-08-14)

flake.lock.txt
Add a :+1: reaction to issues you find important.

Duplicate of https://github.com/NixOS/nixpkgs/issues/334820
Seems to be fixed on master with https://github.com/NixOS/nixpkgs/pull/334833


Multiple calls to SimpleServerFactory.configure() - http://bit.ly/2uaLo88

When I run a dropwizard application, I see aforementioned SimpleServerFactory.configure()  invoked a couple of times via

EnvironmentCommand.java#L40
EnvironmentCommand.java#L44

Following are the stack full stack traces for the paths leading up to SimpleServerFactory.java#L141
Via  EnvironmentCommand.java#L40
"main"@1 in group "main": RUNNING
configure:141, SimpleServerFactory {io.dropwizard.server}
run:40, EnvironmentCommand {io.dropwizard.cli}
run:85, ConfiguredCommand {io.dropwizard.cli}
run:74, Cli {io.dropwizard.cli}
run:89, Application {io.dropwizard}
main:12, Main {io.myapp}

Via EnvironmentCommand.java#L44
"main"@1 in group "main": RUNNING
configure:141, SimpleServerFactory {io.dropwizard.server}
build:103, SimpleServerFactory {io.dropwizard.server}
run:49, ServerCommand {io.dropwizard.cli}
run:44, EnvironmentCommand {io.dropwizard.cli}
run:85, ConfiguredCommand {io.dropwizard.cli}
run:74, Cli {io.dropwizard.cli}
run:89, Application {io.dropwizard}
main:12, Main {io.myapp}

Perhaps, remove this line or include it only if the configure has not been run already?

Why are all the link through bitly? I didn't click on any of them, because it seems kinda phishy.

This looks like the issue that was resolved with #1965

@mattnelson Thanks for pointing me to https://github.com/dropwizard/dropwizard/pull/1965. Maybe you are already aware but please note that https://github.com/dropwizard/dropwizard/pull/1965 fixes DefaultServerFactory.java, not SimpleServerFactory.java


Can't run rust

/piston/packages/rust/1.50.0/run: line 4: ./binary: No such file or directory

Why do I get the error above when I try to run rust code?

this is because your code has a syntax effort. if you're doing this via the api, check the stdout and stderr for more info.

My bad, thanks.


Cannot process file

https://github.com/wrklst/docxmustache/blob/95420aab35efdcb423573da3f8b14cffbcf3ad6c/src/WrkLst/DocxMustache/DocxMustache.php#L379
I've commented this line to fix no processing file.

I would definitely not comment this out. Have you done some debugging to understand why you get the processing error? By default just accepting the image in the format you receive is not good practice and will not make it into this class. If anything this could be rewritten to reformat the image into any docx compatible format. Thanks


fix(example): unlisten to event on tab change in api example

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Otherwise when switching tabs it will emit 1 message for every time the component was initialized.

I rewrote it just because the previous code wasn't easy to read for a Tauri rookie.


Add css inside js support

Sometimes css included inside js files (for example, via https://emotion.sh libs or similar) and sublime already detects the syntax correctly (for example, via Naomi lib) with source.css.embedded.js scope. This PR adds support such embedded css to Hayku.

Thanks! Merged and pushed a version update, should appear in the Package Control shortly.


fix(ComponentRelation): use component from all applications

Fixes

https://issues.redhat.com/browse/HAC-5657
Description

Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Tested locally
/approve
/lgtm


Make ajax cache work with catbox 4.x

I am not sure about this line https://github.com/walmartlabs/fruit-loops/compare/catbox-4?expand=1#diff-2dd9daca757e2378de6a629d4b2f3c0dR52. We are basically replacing existing rules, which may have been set  up somewhere else. In fact, we do pass expiresIn when constructing the cache policy in scotsman: https://github.com/walmartlabs/scotsman/blob/master/lib/index.js#L120. It seems like it doesn't matter in this case because generateFunc provides ttl explicitly, but generally this is not safe. Doing _.extend(ajaxCache.rule, {generateFunc: generateFunc} is also not safe because ajaxCache.rule is not public API.

Released in 0.16.0


AWS + Dynamo store mode, Dynamo tables could not be found

I'm getting following error, once enabling aws-dynamo store mode:
failed to flush user" err="ResourceNotFoundException: Requested resource not found"
NOTE:
This works with default bolt shipper... But indexes are created in S3.
Config:
`
schema_config:
configs:
- from: 2018-10-24
store: aws-dynamo
object_store: s3
schema: v11
index:
prefix: <my_index_prefix>
period: 24h
row_shards: 32
storage_config:
  aws:
    s3: s3://<my_region>/<my_bucket_name>
    http_config:
      idle_conn_timeout: 90s
      response_header_timeout: 0s
    dynamodb:
      dynamodb_url: dynamodb://<my_region>

  boltdb_shipper:
    active_index_directory: /tmp/loki/boltdb-shipper-active
    cache_location: /tmp/loki/boltdb-shipper-cache
    cache_ttl: 24h
    shared_store: s3
  filesystem:
    directory: /tmp/loki/chunks

limits_config:
  enforce_metric_name: false
  reject_old_samples: true
  reject_old_samples_max_age: 168h

table_manager:
  retention_deletes_enabled: true
  retention_period: 672h

compactor:
  working_directory: /tmp/loki/boltdb-shipper-compactor
  shared_store: s3

memberlist:
  abort_if_cluster_join_fails: false
  max_join_backoff: 1m
  max_join_retries: 10
  min_join_backoff: 1s

distributor:
  ring:
    kvstore:
      store: memberlist

ingester:
  lifecycler:
    ring:
      kvstore:
        store: memberlist
      replication_factor: 1
    final_sleep: 0s
  chunk_idle_period: 1m
  chunk_retain_period: 30s

`

Can you try with this instead?
schema_config:
  configs:
  - from: 2020-10-24
    store: aws
    object_store: s3
    schema: v11
    index:
      prefix: index_
      period: 24h
      tags: {}

 storage_config:
  aws:
    s3: s3://us-east-1/rocky-dev-loki
    dynamodb:
      dynamodb_url: dynamodb://us-east-1

Hi,
Could it be if I am already having the objects in S3 created with bolt shipper, and than I switched to aws store mode...
The compactor service can't actually find the corresponding tables for existing objects?

@alexsorkin the error ResourceNotFoundException: Requested resource not found has nothing to do with boltdb-shipper.
It has to do with dynamodb. read here: https://stackoverflow.com/questions/40192304/aws-dynamodb-resource-not-found-exception

@alexsorkin Have you tried using access key and secret? (if you're not using IRSA, which i suspect, since your current configuration will only work with IRSA)
https://grafana.com/docs/loki/latest/configuration/examples/#aws-basic-configyaml
As mentioned (again) referenced from the document, you should try like this:
schema_config:
  configs:
  - from: 2020-05-15
    store: aws
    object_store: s3
    schema: v11
    index:
      prefix: loki_
storage_config:
  aws:
    s3: s3://access_key:secret_access_key@region/bucket_name
    dynamodb:
      dynamodb_url: dynamodb://access_key:secret_access_key@region

NOTE: dynamodb_url: dynamodb://access_key:secret_access_key@region

Hi, unfortunately I had to abandon this solution.
The traces being produced are malformed and the performance haven't met our requirements.
This solution could be used only for one collector producer.
Distributed traces are not supported at all.

@alexsorkin Where do you view the distributed traces? Is it in Jaeger-UI or Kiali?
jaeger-objectstorage supports multiple collectors, which was solved with the latest version. Older versions have a problem with performance, until we rewrote it to use loki to save the data. Internally we use loki - if it works with loki, it will work with jaeger-objectstorage.


docker-compose not functional

Describe the bug
I am unable to start with the provided docker-compose.yml.
To Reproduce
Steps to reproduce the behavior:

Create docker-compose.yml as per the wiki
Touch file whitelist.txt
Run docker-compose up

Expected behavior
A functional docker image
Output
Creating network "rss-bridge_default" with the default driver
Creating rss-bridge ...

ERROR: for rss-bridge  a bytes-like object is required, not 'str'

ERROR: for rss-bridge  a bytes-like object is required, not 'str'
Traceback (most recent call last):
  File "site-packages/docker/api/client.py", line 261, in _raise_for_status
  File "site-packages/requests/models.py", line 940, in raise_for_status
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.22/containers/d0590211cdd0abc7f39ed9c942d3ba94987877fd5cb19899ae21f42b0b018ccf/start

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "compose/service.py", line 625, in start_container
  File "compose/container.py", line 241, in start
  File "site-packages/docker/utils/decorators.py", line 19, in wrapped
  File "site-packages/docker/api/container.py", line 1095, in start
  File "site-packages/docker/api/client.py", line 263, in _raise_for_status
  File "site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
docker.errors.APIError: 500 Server Error: Internal Server Error ("b'driver failed programming external connectivity on endpoint rss-bridge (c01eaa84bea45b4aaad6990e668d39c9f764a2210042e684145927a6537eb2e7): Bind for <IP_ADDRESS>:3000 failed: port is already allocated'")

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bin/docker-compose", line 6, in <module>
  File "compose/cli/main.py", line 72, in main
  File "compose/cli/main.py", line 128, in perform_command
  File "compose/cli/main.py", line 1107, in up
  File "compose/cli/main.py", line 1103, in up
  File "compose/project.py", line 570, in up
  File "compose/parallel.py", line 112, in parallel_execute
  File "compose/parallel.py", line 210, in producer
  File "compose/project.py", line 556, in do
  File "compose/service.py", line 546, in execute_convergence_plan
  File "compose/service.py", line 467, in _execute_convergence_create
  File "compose/parallel.py", line 112, in parallel_execute
  File "compose/parallel.py", line 210, in producer
  File "compose/service.py", line 465, in <lambda>
  File "compose/service.py", line 457, in create_and_start
  File "compose/service.py", line 627, in start_container
TypeError: a bytes-like object is required, not 'str'
[32507] Failed to execute script docker-compose

OS: CentOS Linux release 7.8.2003
my docker-compose:
version: '2'
services:
  rss-bridge:
    container_name: rss-bridge
    restart: unless-stopped
    volumes:
      - ~/rss-bridge:/app/whitelist.txt
    build:
      context: .
    image: rssbridge/rss-bridge:latest
    ports:
      - 4000:80

no clue why, but it works now.


Why not use higher compression ratio in VAE?

In the paper, I saw that you have conducted experiments with higher compression ratio and would like to understand why you did not use them in the final diffusion model and continued to choose to use the 8x8x4 compression multiples in the VAE, is there any reason or experimental support for this?

Temporal compression by 8x can result in significant ghosting artifacts, which cannot be reflected in the evaluation metrics.

Well, any idea to alleviate the ghost artifacts?

Temporal compression by 8x can result in significant ghosting artifacts, which cannot be reflected in the evaluation metrics.


Unit test changes

Use the MSTest NuGet packages, rather than a direct assembly reference. Fixes some problems with the Live Unit Testing of VS 2017.

Add a new base class to make mocking and cleaning up the GoogleCloudExtensionPackage easier. It will also be a good place to place most global resource cleanups.

Make a bunch of unit test classes inherit from the new base class.

Referencing #917 since this PR lays the groundwork for solving that issue.

PTAL


issue 527.1: ensure the cause of the failure is reported to the user

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/3385/


fix little bug translation

Hi @fontainejp
Thanks i find the bug here and fixed, the problem is now for French it shows in English. :S

Hi,
sorry but it's not a good alternative
i think this week i made a commit to fix it ;-)

Hi
Yes not the best way to have the translations.
Is it possible to make the software for MAC or Linux as well?

it's possible to do it but i don't have mac(or linux) to test it.
Perhaps with a virtual machine when i will have time...
see here --> https://www.electron.build/ for details
and change options in package.json
probably something like that
build --mac "dmg": {       "contents": [         {           "x": 240,           "y": 150,           "type": "link",           "path": "/Applications"         }       ]     },
for mac
test it and tell me
i will modify if it's ok

Sounds good i just have no experience packing with electron.
How to pass from web to packed?

Hi,
to understand how it works you must go here --> https://electronjs.org/docs/tutorial/first-app
a new release is available (more things are translated but not all)

thanks i will give a try


Cline fails to read terminal output of commands run by Deepseek model

Problem
When using Cline with OpenRouter's Deepseek model, the assistant fails to read and process terminal output. This fundamental limitation prevents any interactive workflow where the assistant needs to read command output and take further actions based on that output.
Environment:

Provider: OpenRouter
Models: Claude 3.5 Sonnet and Deepseek
Scenario: Any terminal command requiring output analysis and subsequent actions

Expected behavior:
The assistant should operate in an interactive loop:

Execute a command
Read terminal output
Analyze the result
Determine next action
Repeat until task completion

Current behavior with Claude 3.5 Sonnet (Working):
The model maintains a continuous workflow by reading terminal output after each command execution, analyzing results, and taking appropriate follow-up actions until the task is complete.
Current behavior with Deepseek (Bug):
The model executes initial commands but cannot engage in interactive workflows because it fails to read terminal output. It incorrectly reports task completion after the first command, regardless of the actual outcome shown in the terminal.
Impact:
This limitation severely restricts Deepseek's utility in Cline for any task requiring terminal interaction. Common development workflows like Git operations, build processes, test executions, and debugging sessions become impossible to automate effectively. Users must manually interpret terminal output and guide the assistant through each step, defeating the purpose of AI-assisted development.
Testing Steps:
The simplest way to reproduce this issue is by prompting either model with "run git status and tell me what's up". Claude 3.5 Sonnet will read the output and provide an analysis of your repository's state, while Deepseek will execute the command but fail to read or interpret its output, effectively ending the interaction without providing any useful information about your repository's status.
The same pattern occurs in more complex scenarios. For example, when working with Git commit hooks:
Claude 3.5 Sonnet reads the hook's error message and adjusts the commit format accordingly
Deepseek fails to read the error and considers the task complete despite the visible failure
Debug Console Logs
build version: 1.4.7, build environment: PROD
Gemini CodeAssist version 2.23.1
Noxide Loader: Loading noxide library
DelegatingProxy: Loaded 181 CA certs from noxide
USER LOGIN PROFILE API CALLED
 application environment ::  PROD
PROFILE INFORMATION IS :- (1) [{…}]
Profile IDE Info is:- {profiles: Array(1), defaultEmail<EMAIL_ADDRESS>IDEName: 'vscode', loggedInEmail<EMAIL_ADDRESS>Logged in EMAIL ID is:-<EMAIL_ADDRESS>UPDATE EMAIL Updated Profile Data is :-  (2) [{…}, {…}]
 is file exists  /Users/username/.bito/profile/lock.txt
 ENOENT: no such file or directory, access '/Users/username/.bito/profile/lock.txt'
calling to: initialize cra scheduler for userid = 1353152 and wsid = 783177
Code review directory path: /Users/username/.bito/codeReviewAgent/PROD/vscode/1353152/783177
read all cra job status from file: /Users/username/.bito/codeReviewAgent/PROD/vscode/1353152/783177/jobStatus.json
git.enabled :::  true
create bito config  /Users/username/.bito/bito_config.json
is git installed  true
 device id from file  fb382c2e073cda3e3e1d5c6c1a7db56863cba2f4e6fe734f32c8cfce2a8a6f28
received request to store device id
Activating plugin Gemini Code Assist
rejected promise not handled within 1 second: Error: AuthStatus is not initialized
stack trace: Error: AuthStatus is not initialized
    at currentAuthStatus (/Users/username/.vscode/extensions/lib/shared/src/auth/authStatus.ts:57:15)
    at /Users/username/.vscode/extensions/sourcegraph.cody-ai-1.54.0/src/main.ts:625:32
    at kh.value (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:157:35593)
    at P.B (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:746)
    at P.C (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:816)
    at P.fire (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:1033)
    at ib.onDidChangeWindowProperty (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:123:15744)
    at ib.$onDidChangeWindowFocus (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:123:15555)
    at Dy.S (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:115275)
    at Dy.Q (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:115055)
    at Dy.M (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:114144)
    at Dy.L (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:113249)
    at kh.value (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:112046)
    at P.B (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:746)
    at P.fire (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:964)
    at Vn.fire (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:9457)
    at kh.value (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:175:13296)
    at P.B (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:746)
    at P.fire (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:30:964)
    at Vn.fire (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:32:9457)
    at MessagePortMain.<anonymous> (file:///System/Volumes/Data/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:175:11588)
    at MessagePortMain.emit (node:events:518:28)
    at MessagePortMain.emit (node:domain:489:12)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2949)
    at Object.topLevelDomainCallback (node:domain:161:15)
    at Object.callbackTrampoline (node:internal/async_hooks:128:24)
api ::  t.ApiImpl {_model: b, git: d}
repositories ::  (0) []
get git provider remote url is undefined
error occurred to get git remote origin url  Error executing command: Command failed: git config --get remote.origin.url
Failed to parse remote URL: Invalid URL
initialize link handler registration for command: 'link1', link: 'link:https://bit.ly/3GvWOqD'
command 'link1' successfully registered.
initialize link handler registration for command: 'link2', link: 'link:https://bit.ly/3GvWOqD'
command 'link2' successfully registered.
VSCode IDE is running on remote: local
disposable did change window state
Cache has been initialized
LOG OUT STATUS RESET AS LOGIN IS DONE
CODE COMPLETION SET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
VS Code version : 1.96.2
VSCode IDE is running on remote: local
Server will start on HOST: localhost
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
Listening on port 60352
server address ::  {port: 60352, host: 'localhost', isServerRunning: true, serverInstance: Server}
inside extension .ts file :::   60352
readGlobalStatus {didUserChangeLineCompletion: true, didUserChangeCommentCompletion: false, didUserChangeDelay: false}
Code Completion Status File to be created true {didUserChangeLineCompletion: true, didUserChangeCommentCompletion: false, didUserChangeDelay: false, expiryTime: 0, messageDisplayCount: 0, …} 0 0
getUserIdAndWsId {userIdKey: '0', wsIdKey: '0'}
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
INITIAL DATA IS:- {PROD: {…}}
undefined updateCodeCompletionStatusFile {userIdKey: '0', wsIdKey: '0'}
FINAL DATA IS:- {PROD: {…}}
DATA ADDED IN THE FILE
USER LOGIN PROFILE API CALLED
VSCode IDE is running on remote: local
 application environment ::  PROD
PROFILE INFORMATION IS :- (1) [{…}]
Profile IDE Info is:- {profiles: Array(1), defaultEmail<EMAIL_ADDRESS>IDEName: 'vscode', loggedInEmail<EMAIL_ADDRESS>Logged in EMAIL ID is:-<EMAIL_ADDRESS>Session file created at: /Users/username/.bito/last-session-info/lastSessionInfo.json
UPDATE EMAIL Updated Profile Data is :-  (2) [{…}, {…}]
 is file exists  /Users/username/.bito/profile/lock.txt
 ENOENT: no such file or directory, access '/Users/username/.bito/profile/lock.txt'
editorInfo {productName: 'Visual Studio Code 1.96.2', uId: '85def1f3-7d5c-4cde-acd3-cf6a94a8d791', userLoginStatus: 'ws', bitoVersion: '1.4.7', fontSize: 12, …}
DYNAMIC CONFIGURATION API CALLED with :-  https://service.bito.ai/ai-mgmt/ide-configuration {headers: {…}} {bitoUserId: 1353152, email<EMAIL_ADDRESS>ideName: 'VSCODE', uId: '85def1f3-7d5c-4cde-acd3-cf6a94a8d791', wsId: 783177, …}
Payload is valid
check if extension is in use
get minimum supported version from:https://mgmtapi.bito.ai/api/client/4
/Users/username/Library/Application Support/cloud-code/cloudcode_cli/cloudcode_cli/darwin_arm64/cloudcode_cli does not need update
Starting AIPP Language Client
DYNAMIC CONFIGURATION API RESPONSE :-  {auto_completion: 'true', comment.completion.api.timeout: '14000', comment.completion.trigger.delay: '300', comment_to_code: 'true', line.completion.api.timeout: '8000', …}
Dynamic Configuration API Response :-  {status: 200, statusText: 'OK', headers: {…}, config: {…}, request: ClientRequest, …}
config after process {enableAutoCompletion: true, enableCommentToCode: true}
Updated Dynamic Configurations are:-  {lineCompletionTimeout: '8000', commentCompletionTimeout: '14000', lineCompletionTriggerDelay: '250', commentCompletionTriggerDelay: '300'}
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
CODE COMPLETION GET FILE PATH IS:-  /Users/username/.bito/codeCompletion/vscode.json /Users/username/.bito/codeCompletion
readGlobalStatus {didUserChangeLineCompletion: true, didUserChangeCommentCompletion: false, didUserChangeDelay: false}
config {oldConfig: {…}, globalStatus: {…}}
AIPP Language Client Started
Created the Gemini Code Assist completion provider
Language client state is Running
 Current Bito version :: 1.4.7
 Min Supported version :: 1.3.0
compared result::::    1
ListExperimentsResponse result: {experimentIds: Array(19), flags: Array(75), debugString: 'Cq9gUHJpbWFyeSBTbmFwc2hvdCBDTCBOdW1iZXI6ID…RlOiBURVNUSU5HX01PREVfVU5TUEVDSUZJRUQKfQo='}
Client experimentation flags:  {enableQuickpickChat: true, enablePromptRecitationsCheckForTransform: true, enableCodeTransformM2Features: true, generationPaneViewDefaultConfig: false, enableOnboardUserCallFromLegacyFlow: true, …}
  },
    ]
}
" is not valid JSON
    at JSON.parse (<anonymous>)
    at WJt (/Users/username/.vscode/extensions/saoudrizwan.claude-dev-3.0.6/dist/extension.js:838:9)
    at R5e (/Users/username/.vscode/extensions/saoudrizwan.claude-dev-3.0.6/dist/extension.js:838:562) {stack: `SyntaxError: Unexpected token ']', ..."  },
…n.claude-dev-3.0.6/dist/extension.js:838:562)`, message: `Unexpected token ']', ..."  },
    ]
}
" is not valid JSON`}
OpenRouter models fetched and saved {deepseek/deepseek-chat: {…}, google/gemini-2.0-flash-thinking-exp:free: {…}, sao10k/l3.3-euryale-70b: {…}, inflatebot/mn-mag-mell-r1: {…}, openai/o1: {…}, …}
Server "@modelcontextprotocol-memory" stderr: Knowledge Graph MCP Server running on stdio
Server "@modelcontextprotocol-server-github" stderr: GitHub MCP Server running on stdio
Server "@modelcontextprotocol-server-filesystem" stderr: Secure MCP Filesystem Server running on stdio
Server "@modelcontextprotocol-server-filesystem" stderr: Allowed directories: [ '/users/username/repos', '/users/username/.ssh' ]
Server "text-editor" stderr: INFO:mcp-text-editor:Starting MCP text editor server v1.0.2
Server "text-editor" stderr: INFO:mcp.server:Processing request of type ListToolsRequest
Server "text-editor" stderr: INFO:mcp.server:Processing request of type ListResourcesRequest
Server "text-editor" stderr: INFO:mcp.server:Processing request of type ListResourceTemplatesRequest
Server "@modelcontextprotocol-server-sequential-thinking" stderr: Sequential Thinking MCP Server running on stdio
Server "aindreyway-codex-keeper" stderr: npm warn config cache-max This option has been deprecated in favor of `--prefer-online`
Server "aindreyway-codex-keeper" stderr:
FileSystemManager paths:
Server "aindreyway-codex-keeper" stderr: - Base path: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data
- Sources file<EMAIL_ADDRESS>- Cache directory: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data/cache
- Current working directory: /

==================================================
🔧 RUNNING IN LOCAL DEVELOPMENT MODE
Server name: local-codex-keeper
Data directory: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data
Server "aindreyway-codex-keeper" stderr: To run production version use: npx @aindreyway/mcp-codex-keeper
==================================================

Available Documentation Categories [LOCAL VERSION]:

Starting server...
Ensuring directories...
Server "aindreyway-codex-keeper" stderr:
Ensuring directories:
- Creating docs path: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data

Starting server...
Ensuring directories...

Ensuring directories:
- Creating docs path: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data
Server "aindreyway-codex-keeper" stderr: - Docs path created: true
Server "aindreyway-codex-keeper" stderr: - Docs path permissions: 40755
- Creating cache dir: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data/cache
- Docs path created: true
- Docs path permissions: 40755
- Creating cache dir: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data/cache
- Cache dir created: true
Server "aindreyway-codex-keeper" stderr: - Cache dir permissions: 40755
- Testing write permissions<EMAIL_ADDRESS>- Cache dir created: true
- Cache dir permissions: 40755
- Testing write permissions<EMAIL_ADDRESS>Server "aindreyway-codex-keeper" stderr: - Write test completed with cleanup warning: Error: ENOENT: no such file or directory, unlink<EMAIL_ADDRESS>    at async Object.unlink (node:internal/fs/promises:1065:10)
    at async FileSystemManager.ensureDirectories (file:///Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/build/utils/fs.js:108:17)
    at async DocumentationServer.run (file:///Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/build/server.js:505:13) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'unlink',
  path<EMAIL_ADDRESS>}
Directories ensured

Loading documentation sources...
Server "aindreyway-codex-keeper" stderr:
Loading sources:
- Path<EMAIL_ADDRESS>
Ensuring directories:
- Creating docs path: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data
- Write test successful
Directories ensured

Loading documentation sources...

Loading sources:
- Path<EMAIL_ADDRESS>
Ensuring directories:
- Creating docs path: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data
Server "aindreyway-codex-keeper" stderr: - Docs path created: true
- Docs path permissions: 40755
- Creating cache dir: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data/cache

Server "aindreyway-codex-keeper" stderr: - Docs path created: true
- Docs path permissions: 40755
- Creating cache dir: /Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/data/cache
Server "aindreyway-codex-keeper" stderr: - Cache dir created: true
- Cache dir permissions: 40755
- Testing write permissions<EMAIL_ADDRESS>
Server "aindreyway-codex-keeper" stderr: - Cache dir created: true
- Cache dir permissions: 40755
- Testing write permissions<EMAIL_ADDRESS>Server "aindreyway-codex-keeper" stderr: - Write test successful
- Directories ensured
- File exists: true
Server "aindreyway-codex-keeper" stderr: - Write test completed with cleanup warning: Error: ENOENT: no such file or directory, unlink<EMAIL_ADDRESS>    at async Object.unlink (node:internal/fs/promises:1065:10)
    at async FileSystemManager.ensureDirectories (file:///Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/build/utils/fs.js:108:17)
    at async FileSystemManager.loadSources (file:///Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/build/utils/fs.js:195:13)
    at async DocumentationServer.run (file:///Users/username/.npm/_npx/ff546287808dbd0a/node_modules/@aindreyway/mcp-codex-keeper/build/server.js:508:31) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'unlink',
  path<EMAIL_ADDRESS>}
- Directories ensured
- File exists: true
- File content length: 3115
- Parsed docs count: 10
Loaded docs: 10

Using existing docs
Server "aindreyway-codex-keeper" stderr: Categories: [ 'Standards', 'Tools', 'Languages' ]
Docs: [
  {
    "name": "SOLID Principles Guide",
    "url": "https://www.digitalocean.com/community/conceptual-articles/s-o-l-i-d-the-first-five-principles-of-object-oriented-design",
    "description": "C...

Initial Documentation State [LOCAL VERSION]:
Documentation Overview:

Standards:
- SOLID Principles Guide
  Comprehensive guide to SOLID principles in software development
  Tags: solid, oop, design-principles, best-practices

- Design Patterns Catalog
  Comprehensive catalog of software design patterns with examples
  Tags: design-patterns, architecture, best-practices, oop

- Clean Code Principles
  Universal Clean Code principles for any programming language
  Tags: clean-code, best-practices, code-quality

- Unit Testing Principles
  Martin Fowler's guide to unit testing principles and practices
  Tags: testing, unit-tests, best-practices, tdd

- OWASP Top Ten
  Top 10 web application security risks and prevention
  Tags: security, web, owasp, best-practices

- Conventional Commits
  Specification for standardized commit messages
  Tags: git, commits, versioning, best-practices

- Semantic Versioning
  Semantic Versioning Specification
  Tags: versioning, releases, best-practices

- Unblu Documentation

Tools:
- Git Workflow Guide
  Comprehensive guide to Git workflows and team collaboration
  Tags: git, version-control, workflow, collaboration

Languages:
- TypeScript Documentation
  Official TypeScript documentation including handbook, tutorials, and reference guides.
  Tags: typescript, javascript, programming-language, static-typing
Server "aindreyway-codex-keeper" stderr: Documentation MCP server running on stdio [LOCAL VERSION]
Server "aindreyway-codex-keeper" stderr: - File content length: 3115
- Parsed docs count: 10
Loaded docs: 10

Using existing docs
Categories: [ 'Standards', 'Tools', 'Languages' ]
Docs: [
  {
    "name": "SOLID Principles Guide",
    "url": "https://www.digitalocean.com/community/conceptual-articles/s-o-l-i-d-the-first-five-principles-of-object-oriented-design",
    "description": "C...

Initial Documentation State [LOCAL VERSION]:
Documentation Overview:

Standards:
- SOLID Principles Guide
  Comprehensive guide to SOLID principles in software development
  Tags: solid, oop, design-principles, best-practices

- Design Patterns Catalog
  Comprehensive catalog of software design patterns with examples
  Tags: design-patterns, architecture, best-practices, oop

- Clean Code Principles
  Universal Clean Code principles for any programming language
  Tags: clean-code, best-practices, code-quality

- Unit Testing Principles
  Martin Fowler's guide to unit testing principles and practices
  Tags: testing, unit-tests, best-practices, tdd

- OWASP Top Ten
  Top 10 web application security risks and prevention
  Tags: security, web, owasp, best-practices

- Conventional Commits
  Specification for standardized commit messages
  Tags: git, commits, versioning, best-practices

- Semantic Versioning
  Semantic Versioning Specification
  Tags: versioning, releases, best-practices

- Unblu Documentation

Tools:
- Git Workflow Guide
  Comprehensive guide to Git workflows and team collaboration
  Tags: git, version-control, workflow, collaboration

Languages:
- TypeScript Documentation
  Official TypeScript documentation including handbook, tutorials, and reference guides.
  Tags: typescript, javascript, programming-language, static-typing

Documentation MCP server running on stdio [LOCAL VERSION]
inside onDidChangeWindowState {focused: false, active: true}
inside onDidChangeWindowState {focused: true, active: true}
{"stack":"Error: Timeout\n    at Timeout._onTimeout (/Users/username/.vscode/extensions/node_modules/.pnpm/@opentelemetry+sdk-trace-base@1.27.0_@opentelemetry+api@1.7.0/node_modules/@opentelemetry/sdk-trace-base/src/export/BatchSpanProcessorBase.ts:177:16)\n    at listOnTimeout (node:internal/timers:581:17)\n    at processTimers (node:internal/timers:519:7)","message":"Timeout","name":"Error"}
OS: Darwin darwin arm64 24.2.0
Shell: /bin/zsh
Shell Version: zsh 5.9 (arm64-apple-darwin24.0)
Node.js Version: v20.18.1
VSCode Version: 1.96.2
Running command: git status
Waiting for shell integration...
Shell integration changed for terminal shell-integration-problems
Shell integration changed for terminal shell-integration-problems
Shell integration changed for terminal shell-integration-problems
Shell integration available
Shell execution started in terminal shell-integration-problems
Read chunk: 'g\bgit status\x1B[?2004l\r\r\n' +
  '\x1B]633;E;git status;cb859804-5fe0-445d-a3b0-13a0d64077f3\x07\x1B]633;C\x07'
Shell execution ended in terminal shell-integration-problems with exit code 128 for command "git status"
inside onDidChangeWindowState {focused: false, active: true}
{"stack":"Error: Timeout\n    at Timeout._onTimeout (/Users/username/.vscode/extensions/node_modules/.pnpm/@opentelemetry+sdk-trace-base@1.27.0_@opentelemetry+api@1.7.0/node_modules/@opentelemetry/sdk-trace-base/src/export/BatchSpanProcessorBase.ts:177:16)\n    at listOnTimeout (node:internal/timers:581:17)\n    at processTimers (node:internal/timers:519:7)","message":"Timeout","name":"Error"}
inside onDidChangeWindowState {focused: true, active: true}
inside onDidChangeWindowState {focused: false, active: true}

It seesm to work fine in the openai-compatable provider, but through openrouter it doesn't work

Just to expand it runs tests eg 'yarn test' and reads output fine, but when it runs git status it reckons it can't read it, but it definitely did read that early. Not entirely sure what's going on, apologies for the inconsistent reports, will keep trying and see if I can get anymore solid results on what is / isn't working


travis: do not mark integ_slow tests as allowed to fail

Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

Coverage remained the same at ?% when pulling a3bc0f57e93516ef629bcce2c94792c8ab57377d on ffmancera:slowt into ae82a331e7956c5f279e5b5ee55e5234067d28e2 on nmstate:master.

Merging without rebase since it only changes the travis file and travis started all jobs as expected.