connection failed

Hi,
I just tried the sketch in the library and I get an error: do you have any idea what went wrong?
IP address: <IP_ADDRESS>
connection failed
_ERROR
connection failed
_ERROR
Thanks.
Peter

I've got the same error.

I think it is a transient issue.
how often does it happen?

I get it always.

But I using esp8266, I wrote someware that it only works fine on a esp32? Is esp8266 a problem?

no, it can work on esp8266.
i can make it work using both

The title is esp8266-google-tts. So I think it is also for the esp8266. It would be nice if it can work on the esp8266. Let me know if you finnish the adaptation for the esp8266.
Thanks

I also have problem with this code. It looks like Google changed the URL.
niedz., 24 maj 2020, 13:38 użytkownik pvdw0310<EMAIL_ADDRESS>napisał:

The title is esp8266-google-tts. So I think it is also for the esp8266. It
would be nice if it can work on the esp8266. Let me know if you finnish the
adaptation for the esp8266.
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/horihiro/esp8266-google-tts/issues/8#issuecomment-633218005,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQELGHJIBB6SSVOVSCYMFLRTEBK3ANCNFSM4LFPQOGQ
.

I don't think the URL is changed because I confirmed that this library on ESP8266 works fine now.

Thanks alot, I will try it next week.

Ok, I'm gonna check on that.
niedz., 24 maj 2020, 14:02 użytkownik horihiro<EMAIL_ADDRESS>napisał:

I don't think the URL is changed because I confirmed that this library on
ESP8266 works fine now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/horihiro/esp8266-google-tts/issues/8#issuecomment-633220801,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQELGADL33E5WC4VTBOXTTRTEEGFANCNFSM4LFPQOGQ
.

Well, I just uploaded your example sketch to ESP8266 and the error still happens.
IP address: <IP_ADDRESS>
connection failed
_ERROR
connection failed
_ERROR

Please try 1.0.10
https://www.arduinolibraries.info/libraries/esp8266-google-tts
This version doesn't try to connect to Google Translate.


fix(system-restore): replica crash during EngineImage update

https://github.com/longhorn/longhorn/issues/5134#issuecomment-1365604838

@Mergifyio backport v1.4.x


Fix build

Fixes #106
I just ran npm ci && npm run build
I noticed that after you merged yesterday you did a change to commit the dest after building when releasing, so maybe just (re)triggering a release is good enough? (No need to merge this PR)
Demo: https://github.com/Nef10/sync-test/actions/runs/1207485142

Triggered another release and it should be fixed now, thanks!
I manually rebuild the files after your changes yesterday, the problem is GitHub doesn't publish a release created with the API to the marketplace automatically. I had to go and edit the release for it to show up on the marketplace.


Chainable immutable lazy sequence provided by functor

Combine the power of lazy sequences with our home-baked API and maintain purity That means that we don't do this._numbers = this._numbers.filter(func), which can be considered impure. Instead the functor (Rando) receives the result of the last filter call which in turn is a new immutable sequence from a functional point of view.
Because we don't mutate Rando's inner state (re-assign _numbers) and always return a new instance of Rando with it's own state (functor) we could assign the result of a computation of Rando like const filterResult = Rando.range(1, 10).filter(filters something) and use it like filterResult.filter(filter something on top of this result) as often as we like, or create new results from that, which in turn can be re-used. The point is that we could do that already but not without mutating the innser state (_numbers) of our Rando instance. When we save this instance/state and run more than one filter on it we would not get the same results as if we would always return a new instance in each filter call. The new approach makes this safe though.
Example:
const allEvenNumbers = Rando.range(1, 10).even(); // ORIGINAL state

const squared = allEvenNumbers.square(); // creates new state from ORIGINAL state
const randomNumber = squared.random(); // single number

const prime = allEvenNumbers.prime(); // creates new state from ORIGINAL state
const listOfNumbers = prime.numbers(); // list of numbers/array

Next optimisation steps could be cacheResult() of _.memoize() to reduce call of map().
https://facebook.github.io/immutable-js/docs/#/Seq/cacheResult

@myabc @mmrwoods can we merge this or is there a disagreement of its usefulness?

@Nudelsieb I really like that this allows an instance of Rando to be assigned to a variable, and be used as the basis for further number generation. This definitely makes Rando more useful :-)
Having said that, I don't think the commit messages do these changes justice. The first one says it makes class a functor, but there's nothing explaining why. The second adds a map() method because functors should have a map method, but that kind of "just because" commit message isn't very helpful.
As the commit messages don't explain why the class instance must be a functor in order to support this idea of using an instance of Rando for further number generation, it makes me question whether it actually must be a functor at all. I don't know the answer to this question, but it's a question I probably wouldn't ask if the commit messages explained how a functor achieves this goal, and why a functor is the best way to achieve this goal.

@Nudelsieb btw, I am aware that there are other benefits to using a functor. Being able to treat an instance of Rando as something that's iterable is really quite handy, but again, the commit messages don't explain this.

@mmrwoods I agree that the CM's lack why a functor is useful. They should have been more descriptive.
On the other hand I don't think I should explain why a functor needs a map method. The rules are available for everyone to be searched and found on the WWW.
I am currently not aware of any other pattern to achieve the same goal other than using a functor in a clean way. you have to return a new instance to represent a unique state.
I will amend these CM's in due time and will try to improve them in the future :).

@Nudelsieb I agree that you don't need to explain why a functor needs a map method. A functor is not a functor unless it's mappable, which is js means it has a map method (I think, correct me if I'm wrong on that).
The confusion for me arises because your first commit seems to achieve the goal of returning a new instance to allow an instance of Rando with some filters applied to be used as the basis for further filtering. As it does this without adding a map method, and a functor needs a map method, the goal is achieved without actually using a functor, right?
If a functor needs a map method, then it's the second commit that makes Rando a functor, which is useful, but not necessary to achieve the goal of this PR. I'm not saying I don't think it should be added, just that it seems to be a separate feature and as such requires a separate explanation for why it's being added - yes, to make Rando an actual functor, but why?).

@mmrwoods I see your angle now ;-). So basically I have to review if we need a map method (if we call it functor or not is a separate problem). What do we try to solve with a map method? That's a really good question. You could also use values() (or in our case numbers()) to return an array and use the array's map method. That adds a bit more boilerplate for the user of the library but is also more explicit. It boils down in what you believe in. I prefer more abstraction, so directly map on the Instance (functor) rather than the instance's values.

@mmrwoods I've re-committed this, please give feedback. If you're happy, merge it please :). Also, @myabc your opinion on this is appreciated too!

@Nudelsieb Thanks, the updated commit messages are really helpful :-)
The tests fail on CI, but that's a separate issue. I think this should be merged.

@mmrwoods thanks 👍 . Please go ahead and merge it, maybe approve the review first :). Ask @myabc if it is acceptable.


Remove html comments from PR's body before merge.

Checklist

[x] I have read the Contributor Guide
[x] I have read and agree to the Code of Conduct
[x] I have added a description of my changes and why I'd like them included in the section below

Description of Changes
Most HTML code comments in PR texts are remains of PR templates that get embedded into the PR's commit message; that may pollute commit logs in the future, if users aren't careful enough and don't remove those manually. This PR proposes a very bespoke hacky method to remove them from the PR's text just before an attempt to merge.
Related Issues
n/a

I'll merge and deploy this :)


fix(nonce): duplication

Environment
- Operating System: Linux
- Node Version:     v22.12.0
- Nuxt Version:     -
- CLI Version:      3.16.0
- Nitro Version:    -
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      -
- Runtime Modules:  -
- Build Modules:    -

Nuxt Security Version
v2.1.5
Default setup used?
Yes, the bug happens even if the security option is not customized
Reproduction
will provide if necessary
Description
Currently a nonce is added to elements regardless of a nonce being applied already. For example, the nuxt/image module allows to set nonces for image preload links. The regexes could be changed to not match elements which already have a nonce added.

Hi @dargmuesli
I'm a bit annoyed by this one.
On the one hand you have a valid point. Duplicate nonce attributes are not valid, so if a nonce is already present our code should definitely not result in invalid tags.
On the other hand, I think the @nuxt/image implementation is wrong, if not dangerous. Allowing users to inject a nonce by themselves opens a whole can of worms security-wise:

How do you make sure the user is not injecting the same value always?
Is that value cryptographically secure and generated in accordance with the RFC?
How does the user then copies the nonce into the CSP header?
In order to properly implement the nonce, users should always rely on Nuxt Security to achieve that.
Which then means that the nonce property of @nuxt/image is useless.

I would seriously recommend to never use the @nuxt/image nonce property. Installing Nuxt Security takes care of injecting nonces automatically and seamlessly, and provides the necessary security guarantees.
In conclusion, the best way to address the situation should be:
The regexes could be changed to not match replace elements which already have a nonce added
WDYT?

Yes, I agree with this train of thought 👍
Alternatively, I thought about changing nuxt/image so that it doesn't add a duplicate nonce when nuxt-security is detected. But your approach fixes this behavior in a general manner, also for other such sources of confusion.

Pinging our regex czar @GalacticHypernova here 😊
Would you have an idea on how to do this ?

Hey! Sorry for the late response, I've gotten caught up a bit with personal life. I think I know how to do that, would you like me to make a PR?

Hey! So sorry for the late response, I've gotten caught up a bit with personal life. I think I know how to do that, would you like me to make a PR?

Hey @GalacticHypernova yes a PR would be great, thanks

Should it replace instances with a nonce, essentially removing the existent one and overriding with the nonce from Nuxt Security?

Yes, that’s exactly it

The only downside with this is that technically it would indeed make the nonce feature useless in Nuxt Image, which could inadvertently act as a sort of deterrent from using Nuxt Security for people who for some reason would want to use their own nonce. I think the best move here would indeed be to just deprecate the nonce in Nuxt Image, to allow only Nuxt Security to handle, well, security.
I think it’s ok, as long as we only replace the nonce attribute in the html tag and we don’t delete the nonce value in the CSP header itself, we are not modifying any existing functionality in Nuxt Image, but we are improving security

I think it’s ok, as long as we only replace the nonce attribute in the html tag and we don’t delete the nonce value in the CSP header itself, we are not modifying any existing functionality in Nuxt Image, but we are improving security

Yea, I'm looking into the regex, but this one is very tricky as it can reach catastrophic backtracking. All in all however, I believe it is more of a workaround than a solution, really.


Build fails with Node versions 6, 7, 9, 12

Operation System: macOS 10.14.5
Beaker version: 0.8.8 release (7206281)
README.md and CONTRIBUTING.md say that building from source "requires node 6 or higher." However, not all Node versions >= 6 actually built on my machine.
Steps to reproduce
I tried building with Node versions 6–12 with the following script:
for i in $(seq 6 12)
do
nvm install $i
npm i -g gulp node-gyp
npm run burnthemall > "../beaker-logs/using-node-$i.txt" 2>&1
done

Results:
I've attached the build logs for each version of Node. I've glanced at the logs—it appears that the problem comes from dependencies.
using-node-6.txt
using-node-7.txt
using-node-8.txt
using-node-9.txt
using-node-10.txt
using-node-11.txt
using-node-12.txt
Node 6, 7, 9:
node-gyp complains about XCode tools not being installed. nodejs/node-gyp#569 may be related.
In this issue, a core contributor says that you should update to Node 10.x.
Node 8, 10, 11
Builds successfully! 🎉
Node 12:
node-gyp build error. This electron-userland/electron-installer-dmg#39
Though the issue is on Windows, #1351 might be related.
Conclusion
I'm not sure if this is specific to my operating system. The build instructions might have to be updated with compatible versions of Node. Let me know if I can do anything related to this issue.

It would be interesting, which node version @pfrazee uses to build the stuff.

with windows 10, node 10.16 on the "blue" branch I do get the same error message, as shown in using-node-9.txt
'URL' is imported from external module 'url' but never used
'default' is imported from external module 'mime' but never used
[23:31:47] 'bundleTask' errored after 3.58 s
[23:31:47] Error: Cannot find module '@beaker/core/webview' from '/Users/jason/Documents/Code/beaker/app'
    at /Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:46:17
    at process (/Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:173:43)
    at ondir (/Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:188:17)
    at load (/Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:69:43)
    at onex (/Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:92:31)
    at /Users/jason/Documents/Code/beaker/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47
    at FSReqWrap.oncomplete (fs.js:170:21)
[23:31:47] 'bundle' errored after 3.58 s
[23:31:47] 'build' errored after 3.58 s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! beakerbrowser@ build: `gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the beakerbrowser@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/jason/.npm/_logs/2019-06-25T06_31_47_175Z-debug.log
[23:31:47] Finished '<anonymous>' after 6.23 s
[23:31:47] Finished 'rebuild' after 6.23 s

Interesting. I use v11.11.0. I'll keep an eye on the v12 situation. Thanks for the detailed research.

@pfrazee ... do you still use node v11.11.0 to build branch: blue-hyperdrive10?

I'm using 11.15 right now
On Wed, Nov 20, 2019 at 7:13 AM Mario Pietsch<EMAIL_ADDRESS>wrote:

@pfrazee https://github.com/pfrazee ... do you still use node v11.11.0
to build branch: blue-hyperdrive10?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/1430?email_source=notifications&email_token=AAJWCUZJXHKXTTTABN4P2PLQUUZY5A5CNFSM4H3FIJUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEER5WGQ#issuecomment-555997978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWCU47LKBBDJWN4ZAHLSTQUUZY5ANCNFSM4H3FIJUA
.

Are you able to compile beaker with unix and windows? ... Which node version does work atm?


Patch ui tooltips 419b

fixes #419

otherwise lgtm

@kschzt please take a look

lgtm, and if you add a unit test, looks awesome to me


Link ID doesn't update when link is already html, rather than markup

Hi Chris
Hoping this is this something fixable.
When a journal entry is DisplayName
Rather than @JournalEntry[EntityId]{DisplayName}
The ID's are not updated and the links break on import

So normally it would be. But specifically in the KaKaRoTo's Roll20 Converter.
He uses HTML, rather than the link string. There's something about the link string that doesn't work for him. So it get's preconverted into the displayed HTML.
In the journal, the only way to edit it is to open the HTML viewer. And we see:
Lighthouse
My understanding is that Foundry does this behind the scenes when it see's the markup link string to produce the nice buttons.
But in this case, it's not a link string, it's already HTML.

That will be a little more difficult, but I am aware of this trick, in fact use it in the system I'm working on.  This is on my todo list.


add monitor module

This module's feature:

get all SQL's metrics during runtime
monitor the sqlOperation
for auto-configuring

Codecov Report

Merging #737 (2c5807a) into master (84c07a6) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 2c5807a differs from pull request most recent head 9a6a68c. Consider uploading reports for the commit 9a6a68c to get more accurate results

@@           Coverage Diff           @@
##           master     #737   +/-   ##
=======================================
  Coverage   80.49%   80.49%
=======================================
  Files         122      122
  Lines        4748     4748
  Branches      576      576
=======================================
  Hits         3822     3822
  Misses        605      605
  Partials      321      321

Continue to review full report at Codecov.

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

Thanks, merged!


Reenabled fixed source tests in jdk_build

please note, that the fix should go to stable release  version too. Please note, that the test was alone in its group in jdk11. That was a bit dangerous.

It is not our checker, it is the Eclipse Foundation checker, you bend to it, it does not bend to you.
Options to try for troubleshooting:

Set your default commit email address (sounds like you already tried this, if so, push another change to the PR to see if the validation check will pass... doubtful to work, I reran the check and it still fails)
try using "Signed-off by" mechanism
try creating a new PR now that the commit email address matches the ECA account...

I will create second EF account. TYVM~

I tried that siggned off, did not worked.   I create second EC account. Do not work.. any more hints?

The ECA validation tool is checking this particular PR and the commits within it, if any of the commits are associated with an 'invalid account' it will fail.  When others have hit this issue, its often easiest to create a fresh PR with the git email is aligned with the one from the ECA account.

hm. the new pr indeed have passed.. :( 21st century :((


Override cookie_id on media_events

Detailed question
Hello, on Android we have the same request opened for IOs https://github.com/SRGSSR/pillarbox-apple/issues/945, the UDP (SRF) team about an issue related to the media_events and our native events.
Here is a quote of the received message:
Becker, Gosia (SRF) 11:22
Hello Guys, we noticed, that we receive different cookie_id from native events and TC events. In TC, the sdk_id or TcId are used as an unique user identifier. They do not match the cookie_id we receive with page_views and other ui_events. I cannot find any value in media_events in TC, which matches our cookie_id from page_views and other native events. It is problematic, because we cannot build a correct session without matching IDs.
In each event (page_view and ui_event) we include a "cookie_id" parameter in order to track the user sessions.
The problem is that obviosly this ID is different from the one generated by Pillarbox.
Our question is:
There is a way to override the ID sent by the player with the one generated by the app?
Can your answer be found elsewhere?

[X] I have searched existing issues and found no similar question.

[X] I have browsed the available documentation and found no answer to my question.

Like on iOS you can have access the same way to the unique identifier from TagCommander
val cookieId = TCPredefinedVariables.sharedInstance().uniqueIdentifier()
You can also add constants to any TagCommander call with
SRGAnalytics.putPersistentLabels

As the apple issue has been closed, could ew close it ? @antoniodamico1


trailing a prefix slash for composed routes

Hi I am using platformatic runtime for monolith modular. I create a composer and a user service and exposed user to composer. Now my api path is '/user' but it is throwing error Get request path is not found but when i hit '/user/' then it is working fine.
generally last  '/' should be ignored  Right !?

Thanks for reporting!
Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that.


Local sedup doc added

https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/82

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 11
- Added 9

See the complete overview on Codacy


Add per-call configuration options to Client APIs

Overview
This would offer a general framework for implementing a solution to something like #4926. (In addition to timeouts, it could be used to add Metadata, serve some service specific function, etc.).
The Client calls would all gain an Options parameter:
// calls like:
Status Foo(FooRequest const& request);
// ...become:
Status Foo(FooRequest const& request, Options const& options = {});

The Connection calls would also gain an Options parameter.
Details / Open Questions
Jotting down some thoughts from a previous discussion with the team:

We probably don't want to default a parameter for a virtual member function in Connection.
We should consider making these non-pure virtual functions. This could prevent breaks of Connection mocks when a new RPC is added to a service for users that do NOT use our provided mocks + the Google Mock framework.
Implementing this for GA services constitutes a breaking change. (Maybe the code will compile, but the implementation details will change, making any current mocks useless).

We will need to add a configuration setting to the generator to enable/disable the generation of the Options parameter.
How and when to migrate currently GA libraries to using per-call options is an open question.

While we probably have enough direction to start implementing the API surface, I think we need a clearer picture of what a per-call option implementation looks like.

gRPC configuration

Could be applied to configure the context just before it is passed to the stub layer
Could be applied in our generic loop helpers (e.g. RetryLoop)
Could be applied as another stub decorator. We would need to think about whether this decorator takes effect before or after other decorators (e.g. auth).
Would these Options apply for poll and cancel operations?

REST configuration (currently just Storage)

Has storage::DownloadStallTimeoutOption and storage::TransferStallTimeoutOption
They are applied to the CurlClient. (So all requests with the same client have the same timeouts. Is this a problem? I don't know.)
They set CURLOPT_CONNECTTIMEOUT - (transfer) (download)

Service-specific configuration

Do they exist?
If so, I think they would be handwritten. The developer can decide how to implement them when the time comes.

Appendix
Just to give an idea of what I currently have in mind (setting deadlines) (for gRPC):
/// FILE: google/cloud/common_options.h
namespace google::cloud {
struct DeadlineOption {
  using Type = std::chrono::time_point<std::chrono::system_clock>;
};
}  // namespace

/// FILE: google/cloud/grpc_options.h
namespace google::cloud::internal {
struct GrpcSetupOption {
  using Type = std::function<void(grpc::ClientContext&)>;
};

// TODO : Whether this alters a ClientContext& or returns a new, configured
//              ClientContext can be figured out at a later date.
void ConfigureContext(grpc::ClientContext& context, Options const& opts) {
  // TODO : Which option takes precedence, and whether they are exclusive
  //        can be decided later.
  if (opts.has<GrpcSetupOption>()) {
    opts.get<GrpcSetupOption>()(context);
  } else if (opts.has<DeadlineOption>()) {
    context.set_deadline(opts.get<DeadlineOption>());
  }
}
}  // namespace

This looks like a duplicate of #7198, I will let @devjgm and @dbolduc decide which one should be closed.

Whoops. I did not do my homework before writing up this issue. I am going to close this one, but copy the text over to the original issue as a comment.


fix: Terraform example

Related with #1088

That's a good compromise for now, I still plan to look into fixing #1088


Investigate: Endless wheel turning error

In different scenarios transactions can not be submitted successfully. Myself I have encountered the case when submitting attestations and even after waiting 5+ minutes the wheel was turning but nothing was happening.
Last Monday (17.7.23) before the cycle we had 3 cases where this happened during a transaction. With one person we have the contact details and know her phone iPhone 8.

When does a submitted transaction time out? Can we introduce an automatic resend and inform the users?

I have now 3 reported cases for Monday. 3x during a transaction and once during the cycle. There might be a forth one on the way.

I will close this, as I believe that the switch to the dart sending process (#1529) and the follow-up websocket fix (#1553) have resolved most sending issues.


Just use Github Issues and not Mailing List

Hi,
I know that mailing lists are an established way of discussing stuff for programming languages but maybe can just use the Github Issues section of the repo?
It is much easier to read and write stuff and it is already grouped by topic. Using labels you can add even more context to a discussion and since everyone is anyway using Github we can leverage Github’s notification system :)
What do you think?
P.S.: Thanks for initiating that discussion in the first place. Logging is fundamental to every programming language and having a great, simple solution will be key for all the new developers coming from other programming languages to the hot and newly open-sourced Swift 2 :smile:
Sebastian

+1 to GitHub issues.

Works for me if everyone else agrees, what do you think @emaloney?

:+1:

:+1:

Fine by me.

We should update the Contributing section of the README to remove the mailing list reference & to reflect how we'd like people to communicate with us.

Could someone edit README and make a pull request or just merge it directly?

I've created a pull request with a first attempt at describing a workflow.
Comments welcome!

Once we've merged this (or something like this) in, we should send a note to the mailing list letting people know it's being decommissioned.


Objective-C file incorrectly identified as Matlab file

(Original issue 696 created by louisfeng on 2011-09-01T03:55:14.345094+00:00)
There's a bug posted for bitbucket that depends on Pygments:
https://bitbucket.org/site/master/issue/1532/code-highlighting-for-objective-c-m-files#comment-630115
If you look at the actual code for ObjectiveCLexer https://bitbucket.org/birkenfeld/pygments-main/src/28711fa3f32f/pygments/lexers/compiled.py
{{{
#!python
def analyse_text(text):
if '@"' in text: # strings
return True
if re.match(r'[[a-zA-Z0-9.]:', text): # message
return True
return False
}}}
It's simply inadequate to analyse Objective-C files correctly. If anything it should try to detect keywords like @import, @interface, and @implementation. Another issue is in the MatlabLexer, where by default analyse_text returns 0.1 https://bitbucket.org/birkenfeld/pygments-main/src/28711fa3f32f/pygments/lexers/math.py
{{{
#!python
def analyse_text(text):
if re.match('^\s*%', text, re.M): # comment
return 0.9
elif re.match('^!\w+', text, re.M): # system cmd
return 0.9
return 0.1
}}}
So when these two competes, MablabLexer simply wins by default.

(Original issue 696 last updated on 2012-02-05T07:49:44.567937+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by louisfeng on 2011-09-01T04:50:31.116756+00:00)
See attached example objective-c code and the results from Pygments 1.4 output.
{{{
#!text

python hightlight_code.py
<pygments.lexers.PerlLexer>
<pygments.lexers.MatlabLexer>
<pygments.lexers.ObjectiveCLexer>
objc 0.0
matlab 0.1

}}}

(Original comment by birkenfeld on 2012-02-05T07:49:44.564914+00:00)
Closes #696: better analyse_text for objective-c lexer.
→ <<cset 6f83c1a1ef7b>>


Added ".bzrignore" to list of VCS ignore files

Adds support for the Bazaar DVCS.

Since every entry in ignore_pattern_files is another call to fopen() in every directory ag looks at, I'm not too keen on adding more to it. Also, development on bazaar has stalled. There hasn't been a release in over two years. New projects aren't choosing it and old projects are moving off it.
In other words, the performance penalty is paid by everyone, but the feature benefits only a few. IMO, that trade-off isn't worthwhile. Sorry.

On Sun, 14 Feb 2016 at  7:15:59 am GMT, Geoff Greer<EMAIL_ADDRESS>wrote:

Since every entry in ignore_pattern_files is another call to fopen() in every
directory ag looks at, I'm not too keen on adding more to it. Also, development
on bazaar has stalled. There hasn't been a release in over two years. New
projects aren't choosing it and old projects are moving off it.
In other words, the performance penalty is paid by everyone, but the feature
benefits only a few. IMO, that trade-off isn't worthwhile. Sorry.

Fair enough. Thanks for looking at it.
--
Phil Hudson                   http://hudson-it.ddns.net
@UWascalWabbit                 PGP/GnuPG ID: 0x887DCA63


webcam audio

Hi,
I have problem with audio from a webcam, audio is not valid on both sides, but in same RDP session if you run a youtube video works greats, but seems that sound with mic on a webcam not working..
Tried multiple options like but all failing
xfreerdp /cert-ignore /sec:tls /vc:ftrdpbr /v:<IP_ADDRESS> /u:user /d:dom /f /sound /mic
also tried
xfreerdp /cert-ignore /sec:tls /vc:ftrdpbr /v:<IP_ADDRESS> /u:user /d:dom /f /sound /mic /microphone
xfreerdp /cert-ignore /sec:tls /vc:ftrdpbr /v:<IP_ADDRESS> /u:user /d:dom /f /sound:sys:alsa /mic:sys:alsa
xfreerdp /cert-ignore /sec:tls /vc:ftrdpbr /v:<IP_ADDRESS> /u:user /d:dom /f /sound:sys:pulse /mic:sys:pulse
Any suggestion how to solve this audio issues with webcam?
Thanks

All local sound devices work if they work locally. Check if you selected the correct input device.
(Only exception is if you use /usb which redirects the whole USB device to the server before the local os can do anything with it)


Change state on scroll

How can I change the color state on page scroll? I'm using an animated gradient as the page background color. I need to change colors as the user scrolls down the page to each new section. Thank you.

You can use the changeState() method.
You can check the API page of the documentation.


Const assertions are not guaranteed to cause compile failures

In sealed.rs, there are a number of associated constants which are used in const fns to try and trigger compile failures when const generics don't match particular requirements.
These const fns contain constant expressions, which may (but are not guaranteed to) evaluate at compile time. AFAICT from https://doc.rust-lang.org/reference/const_eval.html while this works now it might stop working in the future and instead cause a runtime panic.
Running cargo check on an example which we know won't build:
% cat examples/bad_indexmap.rs
fn main() {
    // needs N to be a power of 2
    let _map = heapless::FnvIndexMap::<u8, u8, 3>::new();
}

% cargo check --example bad_indexmap
    Checking heapless v0.8.0 (~/Code/heapless)
    Finished dev [unoptimized + debuginfo] target(s) in 0.17s

% cargo build --example bad_indexmap
   Compiling heapless v0.8.0 (~/Code/heapless)
error[E0080]: evaluation of `heapless::sealed::Assert::<3, 0>::POWER_OF_TWO` failed
  --> ~/Code/heapless/src/sealed.rs:57:37
   |
57 |     pub const POWER_OF_TWO: usize = 0 - (L & (L - 1));
   |                                     ^^^^^^^^^^^^^^^^^ attempt to compute `0_usize - 2_usize`, which would overflow

note: the above error was encountered while instantiating `fn heapless::sealed::power_of_two::<3>`
   --> ~/Code/heapless/src/indexmap.rs:541:9
    |
541 |         crate::sealed::power_of_two::<N>();
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0080`.
error: could not compile `heapless` due to previous error

We know this is a bit of a hack evidenced by the comments: // Const assert hack. It would be good to try and add coverage for these compile fails in the cfail test suite so that we can detect if/when this stops being a compile-time error. Unfortunately the trybuild crate is using cargo check under the hood and would not be able to hit this.

This is not actually related to the issue.
This line can be rewritten like:
pub const POWER_OF_TWO: () = assert!(L.is_power_of_two());

This is not actually related to the issue. This line can be rewritten like:
pub const POWER_OF_TWO: () = assert!(L.is_power_of_two());

I tried this out for MpMcQueue, but it did not assert at compile time.
    /// ```compile_fail
    /// use heapless::mpmc::MpMcQueue;
    /// let q: MpMcQueue<i32, 1> = MpMcQueue::new();
    /// ```
    const _ASSERT1: () = assert!(N > 1);
    /// ```compile_fail
    /// use heapless::mpmc::MpMcQueue;
    /// let q: MpMcQueue<i32, 3> = MpMcQueue::new();
    /// ```
    const _ASSERT2: () = assert!(N.is_power_of_two());

---- src/mpmc.rs - mpmc::MpMcQueue<T,N>::_ASSERT1 (line 141) stdout ----
Test compiled successfully, but it's marked `compile_fail`.
---- src/mpmc.rs - mpmc::MpMcQueue<T,N>::_ASSERT2 (line 146) stdout ----
Test compiled successfully, but it's marked `compile_fail`.

failures:
    src/mpmc.rs - mpmc::MpMcQueue<T,N>::_ASSERT1 (line 141)
    src/mpmc.rs - mpmc::MpMcQueue<T,N>::_ASSERT2 (line 146)

I'm surprised this compiles successfully :thinking:

From https://doc.rust-lang.org/reference/const_eval.html:

In const contexts, these are the only allowed expressions, and are always evaluated at compile time.

As long as we always evaluate the const expressions in const context (so in const variables, for example), it will always evaluate at compile time. We can also use the static_assertions crate so we don't have to roll this ourselves.


Document how to connect Deadline Monitor to Render Queue

Customers need to be able to connect the Deadline Monitor to the render farms that are deployed with RFDK, yet there is currently no documentation explaining this is done.
This was originally requested in https://github.com/aws/aws-rfdk/issues/105#issuecomment-683802301

This is a 📕 documentation issue

Any news on this so I can further test the RFDK?

Any news on this so I can further test the RFDK?

We do have a developer working on writing up some documentation on this, but I cannot provide an expected completion date.
The jist of the documentation will be some information to help you set up a VPN connection to your deployed VPC -- https://aws.amazon.com/vpn/ -- then connect your Deadline Monitor to the Application Load Balancer endpoint that is created by the RenderQueue construct.

Thanks for your reply. I got it to work in the meantime!

Thanks for your reply. I got it to work in the meantime!


implement adding of PlayerProfile when creating User

for now, PlayerProfile can only be linked to User after User can be created
I think this is ok but wouldn't hurt to implement it later

done


retain DestinationRule func name in push context

https://github.com/istio/istio/pull/37413/files#r809621216

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test gencheck_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test gencheck_istio

integ-ipv6_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test integ-ipv6_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test gencheck_istio

integ-ipv6_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test integ-ipv6_istio

integ-cni_istio
cd91eff55643e551c3bc5e4ae748b8c75f5611eb
link
true
/test integ-cni_istio

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

/retest


create pitch deck

pitch deck

Designs given feedback to and now will be incorporated to slide deck master

2024-03-01_PORTERS_SLIDE_DECK.pdf

Change raid guild logo colour

What is the best way to provide feedback on this? I mostly have minor tweaks or questions.

@plor I sent you an invite to the google slide deck, but you should be able to access this link too. https://docs.google.com/presentation/d/1aTFTVUai0n1Xs6PeieY_odmiIGZFEZeeJk-ASQ6yfrs/edit?usp=sharing

Shared with Plor's associated acct

@benedictvscriticus to incorporate comments and new version coming tomorrow


Support multiple "cards"

Currently wlc is hardcoded to card0, but multiple cards is possiblity and even render nodes.
It should also be possible to have outputs tied to cards instead of whole drm system, this would allow multiple GPUs used with multiple outputs.

I wonder how xwayland applications would behave in this scenario? Is there something like multi-gpu support for xwayland?!

Good question. I have no idea and it should be tested. We may need to open xwayland for each GPU.

We should also autodetect primary card here, instead of assuming card0.

This info might be related: Wayland On Mesa Now Supports DRI_PRIME, Render Nodes https://phoronix.com/scan.php?page=news_item&px=Wayland-DRI-PRIME-Mesa-Nodes

Can anyone provide a little insight on what is needed to support DRI_PRIME in wlc. I have a Docking Station for the Dell XPS (displaylink) that shows up as a second GPU in X11.

Prime needs basically drm backend instance for each card. Same kind of thing is needed to support multiple displays on different GPU's. All the dirty work regarding support between GPUs should be handled by mesa as far I understand. That is copying rendered buffer as texture to another GPU so it can push it to the display controller. This has bit of cost though, this is unavoidable with hybrid GPUs I guess, but with multi GPU + multi display setup, as long as you keep the buffer on the connected display controller there is no overhead.


Split out @medplum/react-hooks package

coverage: 93.25% (-0.02%) from 93.272% when pulling da5c71fd8d3e8a5337e0739c47411b70e283b585 on cody-split-react-hooks into 999a60b0193b3dfa27a6b5e359ea07326bceb3df on main.

Deployed and tested on staging: https://app.staging.medplum.com/


MH-13155: Make weekday preselection optional

When scheduling multiple events, this will make the preselection of the day of the week optional by introducing the prop.admin.event.new.preselect_day property.
Resolves: MH-13155

@lkiesow, I have implemented your suggestion. After testing every imaginable scenario, I can confirm that in all of these scenarios we now get the desired result.

Merged into develop.
Thanks for the patch.


NuGetToolInstallerTask@1 relies on NodeJS 6 which is blocked

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: NuGetToolInstallerTask@1
list here (V# not needed):
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/NuGetToolInstallerV1
Environment

Server - Azure Pipelines or TFS on-premises?

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
https://dev.azure.com/grinding/UGG/_build/results?buildId=109606&view=results

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
The pipeline is not valid. Job Phase_1: Step 'NuGetToolInstaller' references task 'NuGetToolInstaller' at version '1.179.0' contains an execution handler that relies on NodeJS version '6' which is restricted by your administrator. Job Phase_1: Step 'NuGetCommand_2' references task 'NuGetCommand' at version '2.194.0' contains an execution handler that relies on NodeJS version '6' which is restricted by your administrator.

Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Pipeline doesn't exen start.
Error logs
See screenshots above.

Same problem with CopyFilesTask@2


Creating private endpoint missing from post-provisioning steps

[Enter feedback here]
If Synapse Workspace is using Managed Virtual Network, adding Private Endpoint should be added to post provising steps.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 97b78dce-a2a7-5ae1-b3da-6e9523eaa737
Version Independent ID: 1b1add52-1e0f-5750-1b23-31cfb193332d
Content: Enabling Synapse workspace features - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/workspace-connected-create.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @Antvgski
Microsoft Alias: anvang

Thanks for the feedback! I have assigned the issue to the doc author to update appropriately.

#reassign:nanditavalsan

#reassign:rRonyMSFT

The following users don't have valid GitHub IDs, or are not collaborators on this repo: rronymsft

#reassign:Antvgski

#reassign:SnehaGunda

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


WireGuard-Go in the dashboard shown as not running

When running OPNsense 23.1.r_20-amd64 (updated from 22.x) it shows me (on dashboard /services) that WireGuard-Go is not running.
WireGuard as a VPN-server is running and up and working.
Perhaps this might be a cosmetic error ?

The plugin does not support service status for kmod variant yet which is the new default on 23.1. And yes it is cosmetics only. PRs welcome.

It's not just in the services widget, but also in status_services.php. wireguard-go should only be displayed there if os-wireguard-go is actually installed, not when using os-wireguard.

True, but nobody cared before so we start with this and go from here😊

I've just filed PR #3273 with my proposed changes. I think it would be a good idea to hide the service when applicable, to avoid any confusion or anger when e.g. the buttons are not working. Not sure if the solution fits.
I hope it's still manageable before 23.1 GA? (I've filed multiple PRs today)

23.1 is too late not even factoring in code freeze. I’ve made a comment on the PR.

ahhh... was just about to write the same. But yes... confirmed. Just in case I restarted the service manually without any issues. So it's definately just a cosmetical issue.

wireguard-go is going to be removed in 24.1


@unocss/webpack Can't compile styles in RSC(React Server Components) in Next.js 13

UnoCSS version
0.56.5
Describe the bug

@unocss/webpack could not scan React Server Components and compile the related styles.
Updated: transformers works as normal, but the styles can't be compiled.
Related: https://react.dev/blog/2022/03/29/react-v18#server-components-experimental
Configration
uno.config.ts
import {
  defineConfig,
  presetUno,
  presetIcons,
  presetAttributify,
} from 'unocss';
import presetRemToPx from '@unocss/preset-rem-to-px';
import transformerCompileClass from '@unocss/transformer-compile-class';
import transformerVariantGroup from '@unocss/transformer-variant-group';
import transformerDirectives from '@unocss/transformer-directives';
import transformerAttributifyJsx from '@unocss/transformer-attributify-jsx';

export default defineConfig({
  content: {
    pipeline: {
      // include: [/src\/.*\.(s?css|[jt]sx?)$/],
      include: [/\.([jt]sx|mdx?|html|s?css)($|\?)/],
      exclude: [],
    },
  },
  presets: [
    presetUno({
      dark: {
        dark: '.dark-mode',
        light: '.light-mode',
      },
    }),
    presetIcons(),
    presetAttributify(),
    presetRemToPx(),
  ],
  transformers: [
    transformerDirectives({
      enforce: 'pre',
    }),
    transformerCompileClass(),
    transformerVariantGroup(),
    transformerAttributifyJsx(),
  ],
});

next.config.js
const UnoCSS = require('@unocss/webpack').default;

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack(config) {
    // UnoCSS Support
    config.plugins.push(UnoCSS());
    return config;
  },
};

module.exports = nextConfig;

Reproduction
See here: https://stackblitz.com/edit/stackblitz-starters-uirmkr?file=app%2Fpage.tsx
System Info
Ubuntu 22.04 LTS
Chrome Latest
Next.js 13 with App Dirs and webpack bundled
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I personally have zero experience with React Server Component, and no really much interest in it. Open to contributions as long as the solution is straightforward or easy to maintain in the long term.

It mostly works with @unocss/postcss but transformerAttributifyJsx() breaks instead. Maybe a better option for now!

It mostly works with @unocss/postcss but transformerAttributifyJsx() breaks instead. Maybe a better option for now!

No, PostCSS can't transform the code in files like tsx directly, to my understanding. So complie classes transformer and transformerVariantGroup(https://github.com/unocss/unocss/issues/3192) is not work yet.

I guess cause React Server Component already becomes to backend file, we need to use backend way
ref: https://unocss.dev/integrations/cli
export default defineConfig({
  cli: {
    entry: {
      patterns: ['app/**/*.tsx'],
      outFile: 'app/uno-cli.css',
    }, // CliEntryItem | CliEntryItem[]
  },
  ....
}

then import  'app/uno-cli.css' instead of uno.css, which seems work, but this way for me looks not very right

I guess cause React Server Component already becomes to backend file, we need to use backend way ref: https://unocss.dev/integrations/cli
export default defineConfig({
  cli: {
    entry: {
      patterns: ['app/**/*.tsx'],
      outFile: 'app/uno-cli.css',
    }, // CliEntryItem | CliEntryItem[]
  },
  ....
}

then import  'app/uno-cli.css' instead of uno.css, which seems work, but this way for me looks not very right

As fas as I investigate, unocss/webpack in NextJS ignores server components and does not create corresponding utility classes in final css in development mode. In production mode (npm run build), both NextJS and uno.css/webpack do not create corresponding utility classes with transformerVariantGroup (either server or client components)

I don't seem to have these issues.  Both client and server components work and I get styles with the build.  Also the variant transformer works fine.
I do have an issue, that when I update the styles.  There is no refresh with the HMR.  I have to exit out of the process and restart for styles to take effect.
Can someone confirm they get the same for the styles?
Thanks!

I forked the webpack plugin specifically for nextjs: https://pastebin.com/raw/Pdf1GgqL
The key takeaway is that the webpack plugin runs in cycles where only certain files are available and also for the different server and client trees.  The second is a guess on my part (in relation to webpack).
Why am I saying this?  Prior to the fork, when running use client, the layout file has all the tokens needed for the styling.  Without use client there are no tokens present and therefore the time when the stylesheet needs to be overwritten only the preflight is available.

How did I overcome this?  Simply put, I am collating any and all stying pertaining to the pages, saving to a file.  Then finding the layout.css file and overwriting it with the preflight and styles from the file.  I am using a file as an interlocutor as an ordinary variable becomes undefined in the process.
This works on server and client pages, also includes the build process.
I've tested this only in the confines of the unocss repo.  I'm not making a PR due to not having the capacity to test against real-world scenarios.
Would appreciate if anyone wants to do the same and report back.  Thanks!


datapath: remove unused ENCRYPT_NODE macro

It's safe to remove this unused macro.

conformance-test is hitting https://github.com/cilium/cilium/issues/22168.


Remove white flash on boot up

When the electron app is started appear a white flash before show the
MagicMirror system.
This patch remove the white flash on boot up.

Nice! Thanks.

Hello sir,
I am facing same issue .... my electron(v1.7.10) app going to run 365 days 24 hours...previously i was using ia32 package on 64bit... now m using x64 on 64 bit
node version v8.11.3
npm version 5.6.0
see following cmd....
electron-packager . --overwrite --asar=true --platform=win32 --arch=x64 --icon=assets/icons/win/icon.ico --prune=true --out=release-builds --version-string.CompanyName="CompanyName" --version-string.FileDescription=CE --win32metadata.requested-execution-level=requireAdministrator --version-string.ProductName="project_name"
will it be useful ?
should i update my electron

@amolngt Please use the forum for support. Thanks.

@amolngt Please use the forum for support. Thanks.

Forum is Not helpful sir..
i updated electron --- v4.0.6
m using 64bit windows OS
Packaging app for platform win32 x64 using electron v1.7.16-- command while packaging
blank screen after one day..
Please Help

Hi @amolngt , This place (MR) is not the where you can search some help. Please go the forum, or is are sure is a bug so .. open the new issue with details information


rviz: execute selected solution uses unactuated joints

The rviz execute button tries to actuate all joints. Task.execute(solution) uses the correct joints.
e.x.:
ERROR [ros.moveit_task_constructor_capabilities.ExecuteTaskSolution]: Could not find JointModelGroup that actuates {caster_back_left_1_joint, caster_back_left_2_joint, caster_back_right_1_joint, caster_back_right_2_joint, caster_front_left_1_joint, caster_front_left_2_joint, caster_front_right_1_joint, caster_front_right_2_joint, suspension_left_joint, wheel_left_joint, suspension_right_joint, wheel_right_joint, torso_lift_joint, arm_1_joint, arm_2_joint, arm_3_joint, arm_4_joint, arm_5_joint, arm_6_joint, arm_7_joint, gripper_finger_joint, head_1_joint, head_2_joint}

Hi, I am having the same issue. Did you figure it out?

Duplicate of https://github.com/ros-planning/moveit_task_constructor/issues/93. See for workaround there.


Use PKCS1 encoding to be compatible with Go 1.9

Signed-off-by: Patrick Uiterwijk<EMAIL_ADDRESS>

https://golang.org/doc/go1.10#crypto/x509

Go 1.11 is almost out, and I am not particularly interested in letting mkcert compile with Go 1.9.
ParsePKCS8PrivateKey has always been there, so the generated keys are compatible with all past versions of Go.
But thanks for the contribution!


1.12.2 Using Not Defined Headers Class

I got the following error with the newest 1.12.2 version packages.
ReferenceError: Headers is not defined
    at Api.request (/xxx/node_modules/arweave/node/lib/api.js:43:25)
    at Api.get (/xxx/node_modules/arweave/node/lib/api.js:29:27)
    at Wallets.getBalance (/xxx/node_modules/arweave/node/wallets.js:41:25)

I checked with the implementation. Seems like it's using fetch API (and expecting fetch.Headers) in the newest update.
Is 1.12.2 missing dependency of fetch in package?

What version of NodeJS are you using?

What version of NodeJS are you using?

v16.15.1

I met the same problem.

ah dang, this is not working how i thought it was. thanks for reporting!
for now, you can either:

revert to<EMAIL_ADDRESS>upgrade to nodejs@18
or specify in your startup script:

for JS: node --expermimental-fetch ...
for TS: NODE_OPTIONS='--experimental-fetch' ts-node ...

cc @martonlederer

Ahhh no... We might need to look into a nodejs fetch pkg anyway

ah dang, this is not working how i thought it was. thanks for reporting! for now, you can either:
1. revert to<EMAIL_ADDRESS>
2. upgrade to nodejs@18

3. or specify in your startup script:

* for JS: `node --expermimental-fetch ...`

* for TS: `NODE_OPTIONS='--experimental-fetch' ts-node ...`

i'm marking this as closed, with these as the solutions.

With node version 16.19.0 we get the headers is not defined issue -
ReferenceError: Headers is not defined
We don't get that issue with node 18.13
its looks like the required engine is 16.15.0 in package.json
This is with the latest arweave-js, thanks guys!

With node version 16.19.0 we get the headers is not defined issue -
ReferenceError: Headers is not defined
We don't get that issue with node 18.13
its looks like the required engine is 16.15.0 in package.json
This is with the latest arweave-js, thanks guys!

in your case you can start your node v16 app by adding the --experimental-fetch flag. it's safe to add this flag to node v18+ apps too.
if the warning is annoying, you can also add --no-warnings

I've updated the Release Notes for v1.12


index on sql database to allow hass to startup quickly with a large sql database

Description:
hass starts up very slow with a large SQL database. This adds an index to the states table to help (tremendously) with startup speed.
Related issue (if applicable): fixes #8176
Checklist:
If user exposed functionality or configuration variables are added/changed:

[na ] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[na] Tests have been added to verify that the new code works.

@pvizeli Hi - I believe I've seen you deal with the issue of a stuck cla-bot before? If not, do you know how I can go about getting the bot working agian?

@balloob @pvizeli I believe I have submitted the changes as requested, however Travis is failing for reasons unknown to me - tox passes in my dev env:
Results (303.52s):
2204 passed
50 skipped
Please advise?

Ah - looks like my email wasn't correctly set in the first round of commits. What would be the best way to deal with this? I presume this is why CLA-bot is stuck?

We can merge it, you need no change for cabot

Can you please squash all your commits and make sure they have the right email attached

@balloob Done!

Awesome! Cherry-picked for 0.48


Runtime error when served with Docker

Hello,
I am facing the same problem as #225 when attempting to add a client when serving with Docker. The fix specified involved changing Go versions, which is not applicable to Docker. Is this a known problem?

Also to add context, upon opening the "add client" dialog, I get a message:

Cannot suggest ip allocation: failed to get list of allocated ip addresses
I don't see any way to set this allocation block, which tells me it's trying to read from the file and can't. I have tried the following four things:

My existing config
Existing config without the client declarations
3: A blank config file
4: rm the config file

All of these result in the same two errors. I can open the "add client" dialog but upon pressing the confirm button it breaks.

And the error is
echo: http: panic serving REDACTED:49698: runtime error: invalid memory address or nil pointer dereference
goroutine 15 [running]:
net/http.(*conn).serve.func1()
	/usr/local/go/src/net/http/server.go:1802 +0xb9
panic({0x8ac940, 0x1461eb0})
	/usr/local/go/src/runtime/panic.go:1047 +0x266
net.networkNumberAndMask(0xc000383ba0)
	/usr/local/go/src/net/ip.go:498
net.(*IPNet).Contains(0xc000383b10, {0xc000383ba0, 0x10, 0x0})
	/usr/local/go/src/net/ip.go:522 +0x27
github.com/ngoduykhanh/wireguard-ui/util.ValidateIPAllocation({0xc00009d8c0, 0x2, 0xc0004ae690}, {0x0, 0x0, 0xc0004f31f0}, {0xc00009d840, 0x1, 0xc0004f3270})
	/build/util/util.go:370 +0x2f0
github.com/ngoduykhanh/wireguard-ui/handler.NewClient.func1({0x114f450, 0xc000176960})
	/build/handler/routes.go:414 +0x20c
github.com/ngoduykhanh/wireguard-ui/handler.ContentTypeJson.func1({0x114f450, 0xc000176960})
	/build/handler/middlewares.go:17 +0xed
github.com/ngoduykhanh/wireguard-ui/handler.ValidSession.func1({0x114f450, 0xc000176960})
	/build/handler/session.go:22 +0x182
github.com/labstack/echo/v4.(*Echo).add.func1({0x114f450, 0xc000176960})
	/go/pkg/mod/github.com/labstack/echo/v4@v4.1.16/echo.go:512 +0x6d
github.com/labstack/echo/v4/middleware.LoggerWithConfig.func2.1({0x114f450, 0xc000176960})
	/go/pkg/mod/github.com/labstack/echo/v4@v4.1.16/middleware/logger.go:111 +0x491
github.com/labstack/echo-contrib/session.MiddlewareWithConfig.func1.1({0x114f450, 0xc000176960})
	/go/pkg/mod/github.com/labstack/echo-contrib@v0.9.0/session/session.go:70 +0x105
github.com/labstack/echo/v4.(*Echo).ServeHTTP.func1({0x114f450, 0xc000176960})
	/go/pkg/mod/github.com/labstack/echo/v4@v4.1.16/echo.go:617 +0x132
github.com/labstack/echo/v4/middleware.RemoveTrailingSlashWithConfig.func1.1({0x114f450, 0xc000176960})
	/go/pkg/mod/github.com/labstack/echo/v4@v4.1.16/middleware/slash.go:118 +0x1fb
github.com/labstack/echo/v4.(*Echo).ServeHTTP(0xc000260000, {0x113d360, 0xc000192700}, 0xc000416d00)
	/go/pkg/mod/github.com/labstack/echo/v4@v4.1.16/echo.go:623 +0x3bc
net/http.serverHandler.ServeHTTP({0x113bf68}, {0x113d360, 0xc000192700}, 0xc000416d00)
	/usr/local/go/src/net/http/server.go:2879 +0x43b
net/http.(*conn).serve(0xc000176460, {0x113fbc0, 0xc00047dec0})
	/usr/local/go/src/net/http/server.go:1930 +0xb08
created by net/http.(*Server).Serve
	/usr/local/go/src/net/http/server.go:3034 +0x4e8

Can you try again on the latest image? It uses go 1.21 and has some fixes.

I ran docker pull to be safe (the docker compose file specifies latest) and re-ran the container, and the same two issues happened. In the logs it shows the git commit as b3c22aa, the current one as of writing.

I ran docker pull to be safe (the docker compose file specifies latest) and re-ran the container, and the same two issues happened. In the logs it shows the git commit as b3c22aa, the current one as of writing.

Can you provide more information to help me reproduce the issue?

How does your docker-compose file look like?
What is your OS version?
What are your configured Server Interface Addresses?
What are the configuration (IP Allocations, Allowed IPs, etc) when you create a new client?

My docker-compose file is as follows:
version: "3"
services:
  wireguard-ui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    cap_add:
      - NET_ADMIN
    network_mode: host
    environment:
      - BIND_ADDRESS=<IP_ADDRESS>:51821
      - SESSION_SECRET=REDACTED
      - WGUI_USERNAME=REDACTED
      - WGUI_PASSWORD=REDACTED
      - WGUI_ENDPOINT_ADDRESS=REDACTED
      - WGUI_DNS=<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>
      - WGUI_PERSISTENT_KEEPALIVE=25
      - SMTP_HOSTNAME=smtp.gmail.com
      - SMTP_PORT=587
      - SMTP_USERNAME=REDACTED
      - SMTP_PASSWORD=REDACTED
      - SMTP_AUTH_TYPE=PLAIN
      - SMTP_ENCRYPTION=STARTTLS
      - WGUI_SERVER_INTERFACE_ADDRESSES=<IP_ADDRESS>,fc00::1:5:1
      - WGUI_SERVER_LISTEN_PORT=51820
      - WGUI_DEFAULT_CLIENT_ALLOWED_IPS=<IP_ADDRESS>,::/0
      - WGUI_DEFAULT_CLIENT_USE_SERVER_DNS=true
      - WGUI_DEFAULT_CLIENT_ENABLE_AFTER_CREATION=true
      - WGUI_MANAGE_START=false
      - WGUI_MANAGE_RESTART=false
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - /etc/wireguard/db:/app/db
      - /etc/wireguard:/etc/wireguard

I am on CentOS 7 Linux, and I am attempting to migrate (or rather recreate) my existing server. It has the internal IPs of <IP_ADDRESS>/24 and fc00::1:5:1/112. As for the last question, do you mean what I have current clients use, or what the interface has prefilled?

WGUI_SERVER_INTERFACE_ADDRESSES=<IP_ADDRESS>,fc00::1:5:1

This seems to be a problem. Server addresses must be in CIDR format. Please check the current applied "Server Interface Addresses" to see if you have them in CIDR format.
I tried the above environment variable value, and I got the same error Cannot suggest ip allocation: failed to get list of allocated ip addresses

As for the last question, do you mean what I have current clients use, or what the interface has prefilled?

I meant what configuration you used when creating a new client and got the error.

Ah, my bad. I should've thought of that since they're all CIDR in the actual conf file. Is this supposed to match the Address field of the [Interface] section one-to-one? I guess my question is if I use /32 and /128, or if I should use the appropriate mask for the entire network.
As for config, I pretty much just used test values, I set the name and email to test and<EMAIL_ADDRESS>IP allocation to <IP_ADDRESS>/32 (ignoring IPv6 for now), and left endpoint blank assuming the default would be used. I also tried filling in the endpoint with both IP and IP:port.

Is this supposed to match the Address field of the [Interface] section one-to-one?
Yes, they should have the same value.

Can you correct the WGUI_SERVER_INTERFACE_ADDRESSES and test if it works? In you case, it should be <IP_ADDRESS>/24 and fc00::1:5:1/112?

After making this change it initially didn't work, but then I realized I was reusing the folder created by the last container, so I went on the web UI and added the CIDR values, which did in fact fix it. Thank you! Sorry for the hassle.


Chinese input problem

Does this issue occur when all extensions are disabled?: Yes
VS Code version: 1.70.2 (user setup)
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042
Steps to Reproduce:
My input method

I want to append -1 to become -1-1

When I enter '-' in Chinese state

This happens only if the next input character is a symbol.
The strange thing is that restarting vscode returns to normal, but after a while or maybe I press a certain key combination, this problem occurs.

The strange thing is that restarting vscode returns to normal, but after a while or maybe I press a certain key combination, this problem occurs.

To be able to debug this, we would need a reproducible case. Did you in the meantime discover reproducible steps?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Align newsfeed buttons when  hide-noisy-newsfeed-events  is disabled

Issue Number: #4760
The button was out of position on the github main page.
Therefore, the issue was resolved.
Please comment if there is a problem.

I tested it simply with the code below.
It doesn't seem to affect anything other than follow.

<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
    <link rel="stylesheet" href="./test.css">

follow

test

.rgh-clean-dashboard .dashboard .body > .border-bottom {
	margin: 0;
	padding-left: 16px;
	padding-right: 16px;
}

/* When there are two or more following */
.rgh-clean-dashboard .dashboard .follow > .body > .border-bottom {
	padding-right: 16px !important;
}

.rgh-clean-dashboard .js-news-feed-event-group {
	padding-right: 0 !important;
}

I built it myself.but it appears there is no problem.

Is it right to want a screenshot like this?

Screenshots always need to be on GitHub itself. They're useful to reviewers to determine whether a PR works as expected. The last screenshot is right. I'd also like to see the current code working when hide-noisy-newsfeed-events is disabled

My previous review is not addressed at all. The code still overrides this: https://github.com/sindresorhus/refined-github/blob/239636cea448c11c488490badb83c7060e194e35/source/features/clean-dashboard.css#L72-L75
Instead, it's this line that should be changed, probably to:
.rgh-clean-dashboard.rgh-hide-low-quality-newsfeed-events .js-news-feed-event-group {
	padding-right: 0 !important;
}

Because it should only apply when both features are enabled

I found the option and turned it off, but I don't know if it was applied. Do I just need to uncheck it?

And can I know exactly what function 'hide-noisy-newsfeed-events' is?
It says 'Hides other input new safe events (commits, forks, new followers)', but I think I can see new followers and forks well.

This picture is a screen with all the styles below applied.
.rgh-clean-dashboard.rgh-hide-low-quality-newsfeed-events .js-news-feed-event-group {
	padding-right: 0 !important;
}

.rgh-hide-noisy-newsfeed-events .news :is(.push, .fork, .delete, .follow, .release) {
	display: none !important;
}

So yes I identified two issues on main:

follow buttons appear but shouldn't
buttons inside grouped events lack spacing

One event ✅

Grouped events ❌

It also applies to Sponsor buttons

I think this has been fixed by https://github.com/sindresorhus/refined-github/pull/4764
Leave a comment on the issue if it hasn't


Prepdocs.py crashing with module error, not able to create/load the search index

Please provide us with the following information:

This issue is for a: (mark with an x)
- [X ] bug report -> please search issues before submitting

Minimal steps to reproduce
Running prepdocs.ps1 into prepdocs.py from a newly cloned copy of the repo today

Any log messages given by the failure
Running "prepdocs.py"
Traceback (most recent call last):
File "C:\Files\repo1\scripts\prepdocs.py", line 10, in
from prepdocslib.blobmanager import BlobManager
File "C:\Files\repo1\scripts\prepdocslib\blobmanager.py", line 7, in
import fitz  # type: ignore
^^^^^^^^^^^
File "C:\Files\repo1\scripts.venv\Lib\site-packages\fitz_init_.py", line 22, in
from fitz.fitz import *
File "C:\Files\repo1\scripts.venv\Lib\site-packages\fitz\fitz.py", line 14, in
from . import _fitz
ImportError: DLL load failed while importing _fitz: The specified module could not be found.

Expected/desired behavior
Prepdocs would work

OS and Version?
Windows 11 22h2, also repro on Windows 10 22h2

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?
azd version 1.5.0 (commit 012ae734904e0c376ce5074605a6d0d3f05789ee)

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

What version of Python is this in?

we see this in python 3.11.6 , 3.11.7

Introduced in https://github.com/Azure-Samples/azure-search-openai-demo/pull/1056
fitz is missing from the prep docs dependency input, it might be a transient dependency that's unique to certain platforms.
Thanks for the report. I'll test this out on a Windows machine

Update after trying to reproduce this. Fitz is part of pymupdf so it seems that package didn't install correctly.
This is a known issue with PyMuPDF on certain versions of Windows. They have a solution here https://github.com/pymupdf/PyMuPDF/blob/main/docs/installation.rst#problems-after-installation

thanks i'll test this out and update here if any further issues


Insert version number for 0.23.0 in CHANGELOG

The CHANGELOG is missing the Mesos version number for the 0.23.0 section.
This commit adds the proper section topic.

Was already fixed in the meantime ...


Move all non-tooling libraries into a Recommended libraries page

Which Section of the Documentation Needs Improving?
The pages on libraries we recommended for non-tooling purposes (e.g. GUIs, CLIs, etc.)
What Can be Improved About This Section
Clearer organisation of recommended libraries
How to Improve This Section
Rename Utility libraries to Recommended libraries (as suggested in https://github.com/UCL-ARC/python-tooling/issues/355#issuecomment-2069093754).
Move the GUI libraries page (added in #373) into Recommended libraries.
What other pages, if any should be moved? Parallel and asychronous processing?

Hmm, I still remain unconvinced by this 😄 - perhaps a definition of tooling vs non-tooling would help me get on board with this change?
To be honest I think splitting the "Utility libraries" page up into three more (CLI, GUI, Logging) would be nicer and make what's currently there more discoverable. I worry that having a generic "Recommended libraries" reduces discoverability of the tools from the home page, because "libraries" is a very generic catch-all term.

We could make use of the Just-the-docs parent attribute? Does that make it better or worse?
Then it could be one page-per-theme and all libraries are under a subdirectory...

👍 https://github.com/UCL-ARC/python-tooling/issues/427#issuecomment-2233271059 makes sense and clarifies it for me. And having the parent arrow thing in the comment above would fix my discoverability concern 👍


Add multi-language support to the dApp

As our international community is growing quite quickly, we should allocate some time and effort to adding language support to the dApp.
The functionality could be a flag drop down for people to choose from.
Suggested languages to focus on (in order of priority for now):

Turkish
Arabic
German
Spanish

We expand on this list as each community starts to expand and there is a need.

I can help with the Turkish.


Activate pythonPath on vscode startup or python extension startup

Currently, once the python extension is activated, any new terminal will automatically enable any set virtualenv, but a terminal opened on vscode startup does not activate activate immediately.
I would suggest that if "python.PythonPath" is set up, the virtualenv should be activated on vscode startup, so that users do not have to close the current terminal and open a new one every time.

You can set python.terminal.activateEnvInCurrentTerminal to true to activate the current terminal at startup.


In-line notebook plotting is broken in iPython 3.0/ Jupyter

Our notebook checking function in_pynb() doesn't work anymore.

In particular, this iPython issue killed the hook we were using.  They really seem to want to force you to use display system and that's it.

I guess we can make startup() take an argument about whether to enable inline plotting. Maybe startup(inline=False) to make the default thing still work at the console?

I think I have another hack workaround by checking whether instantiating a widget throws but I need to double check it doesn't break iPython 2.x

Hack workaround doesn't work in iPython 2.x so I think we'll have to adopt the output_notebook, output_file convention and have the user manually start interactive plotting.

That's fine with me.

So should we have people run output_notebook before trying to plot anything in IPython 3?

No, I haven't committed that fix yet.  It's currently just broken.

Close?

Yep.  I didn't get the magic words right in the commit message for 09e5fd8f79b06e19419fae3773ea12e7ede7d2ae.  I used "Closes issue" instead of just "closes.


Use # prefix on private class field with eslint-plugin-flowtype cause "Cannot read property 'type' of undefined"

My plugins and parser versions:
"babel-eslint": "^9.0.0",
"eslint": "^5.5.0",
"eslint-plugin-babel": "^5.2.0",
"eslint-plugin-flowtype": "^2.50.1",
"flow-bin": "^0.81.0",

My eslint configs:
	"env": {
		"browser": true,
		"commonjs": true,
		"es6": true
	},
	"extends": [
		"eslint:recommended",
		"plugin:react/recommended",
		"plugin:flowtype/recommended"
	],
	"parser": "babel-eslint",
	"parserOptions": {
		"ecmaFeatures": {
			"jsx": true
		},
		"ecmaVersion": 2018,
		"sourceType": "module"
	},
	"plugins": ["react", "babel", "flowtype"],

I got the problem when write this:
...
class Popup extends React.Component {
	#previousRange: ?Range = null;
...
}

Class Popup
TypeError: Cannot read property 'type' of undefined

TypeError: Cannot read property 'type' of undefined
    at isForInRef (..\node_modules\eslint\lib\rules\no-unused-vars.js:410:24)
    at variable.references.some.ref (..\node_modules\eslint\lib\rules\no-unused-vars.js:447:21)
    at Array.some (<anonymous>)
    at isUsedVariable (..\node_modules\eslint\lib\rules\no-unused-vars.js:446:40)
    at collectUnusedVariables (..\node_modules\eslint\lib\rules\no-unused-vars.js:569:26)
    at collectUnusedVariables (..\node_modules\eslint\lib\rules\no-unused-vars.js:576:17)
    at Program:exit (..\node_modules\eslint\lib\rules\no-unused-vars.js:621:36)
    at listeners.(anonymous function).forEach.listener (..\node_modules\eslint\lib\util\safe-emitter.js:47:58)
    at Array.forEach (<anonymous>)
    at Object.emit (..\node_modules\eslint\lib\util\safe-emitter.js:47:38)
    at NodeEventGenerator.applySelector (..\node_modules\eslint\lib\util\node-event-generator.js:251:26)
    at NodeEventGenerator.applySelectors (..\node_modules\eslint\lib\util\node-event-generator.js:280:22)
    at NodeEventGenerator.leaveNode (..\node_modules\eslint\lib\util\node-event-generator.js:303:14)
    at CodePathAnalyzer.leaveNode (..\node_modules\eslint\lib\code-path-analysis\code-path-analyzer.js:630:23)
    at CodePathAnalyzer.overrideLeaveNode (..\node_modules\eslint-plugin-node\lib\rules\process-exit-as-throw.js:127:27)
    at Traverser.leave [as _leave] (..\node_modules\eslint\lib\linter.js:1000:32)
Process finished with exit code -1

Do you have the right babel plugin? ["@babel/plugin-proposal-class-properties", { "loose": false }] if you're on Babel 7. See the README here for more info, but basically, you have to include the plugins individually now.

Yes i use babel 7:
"@babel/core": "^7.1.2",
"@babel/plugin-proposal-class-properties": "^7.1.0",
"@babel/plugin-proposal-json-strings": "^7.0.0",
"@babel/plugin-proposal-object-rest-spread": "^7.0.0",
"@babel/plugin-proposal-unicode-property-regex": "^7.0.0",
"@babel/plugin-syntax-dynamic-import": "^7.0.0",
"@babel/plugin-syntax-import-meta": "^7.0.0",
"@babel/plugin-transform-dotall-regex": "^7.0.0",
"@babel/preset-env": "^7.1.0",
"@babel/preset-flow": "^7.0.0",
"@babel/preset-react": "^7.0.0",

This is my config:
...
options: {
	presets: [
		'@babel/preset-env',
		'@babel/preset-react',
		'@babel/preset-flow'
	],
	plugins: [
		'@babel/plugin-proposal-object-rest-spread',
		'@babel/plugin-proposal-unicode-property-regex',
		'@babel/plugin-transform-dotall-regex',
		'babel-plugin-styled-components',
		['@babel/plugin-proposal-class-properties', { loose: false }],
		'@babel/plugin-proposal-json-strings',
		'@babel/plugin-syntax-dynamic-import',
		'@babel/plugin-syntax-import-meta'
	]
},
...

I still have this error when ever i type prefix# when declare a member in class. I think it must be an issues

Does it output correctly at least, or is just when you're linting? If you're doing a babel.config.js file, you don't need to wrap them in the options key. You can just
module.exports = (api) => {
  const presets = [
	'@babel/preset-env',
	'@babel/preset-react',
	'@babel/preset-flow'
  ];
  const plugins = [
	'@babel/plugin-proposal-object-rest-spread',
	'@babel/plugin-proposal-unicode-property-regex',
	'@babel/plugin-transform-dotall-regex',
	'babel-plugin-styled-components',
	['@babel/plugin-proposal-class-properties', { loose: false }],
	'@babel/plugin-proposal-json-strings',
	'@babel/plugin-syntax-dynamic-import',
	'@babel/plugin-syntax-import-meta',
	api.env('test') ? 'babel-plugin-istanbul' : '' // if you use special environmental plugins/presets, here's how to do it
  ];
  return { plugins: plugins, presets: presets }; // or { plugins, presets }, as is usually preferred
};

I'm not trying to say that it isn't a bug, just that babel changed the way it works vastly, so if you're taking advantae of the new configuration features, there's a chance that the problem could be with babel as well/instead.

yes i just got when linting, babel is fine

@philong6297 did you figure out the linting issue?

Seems in my case (check your yarn.lock/package-lock.json) there were conflicting versions of babel-eslint in play.  Adding a resolution to package.json seems to fix for me:
"resolutions": {
    "babel-eslint": "^10.0.1"
  }

I have created a demo of an issue:
https://github.com/SleepWalker/bug-eslint-no-unused-vars-private-fields

Adding a resolution to package.json seems to fix for me

@jamiehill In my case that haven't fix anything :( the error still persists

Seems like the reason is that espree has no support for private properties

Seems like the reason is that espree has no support for private properties

But, isn't that why we use babel-eslint? To allow eslint to work properly with features espree does not support yet?

Minimal reproducible test:
      verifyAndAssertMessages(
        `
            type Something = { };

            class C {
              #obj: Something;
            }

            console.log(new C());
        `,
        { "no-unused-vars": 1 }
      );
    });```

Probably we need to reimplement the no-unused-vars rule in eslint-plugin-babel.

This might be another relevant note,
Private fields and variables was linting fine for me before i added 'plugin:flowtype/recommended' to my extends array in my .eslintrc.js
extends: [
		'eslint:recommended',
		'plugin:prettier/recommended',
		'plugin:flowtype/recommended'
	]

This exact issue still persists for me even if I crank all eslint & bable dependencies to their latest version. What's more, this doesn't always fail. For example in my case
This fails
  #publicDeriverId: number;
  #bip44Wallet: IBip44Wallet;
  #derivationId: number;
  #pathToPublic: Array<number>; // only this specific private field causes an error.

This passes
  #publicDeriverId: number;
  #bip44Wallet: IBip44Wallet;
  #derivationId: number;
  #pathToPublic: string; // note: this changed

Adding this totally unrelated type makes it work
type TotallyUnrelatedType = Array<number>;
export class Foo {
  #publicDeriverId: number;
  #bip44Wallet: IBip44Wallet;
  #derivationId: number;
  #pathToPublic: Array<number>;
}

Yes, this still persists today.  Interesting @SebastienGllmt your note is correct that having a type before the class is defined seems to fix it which is pretty crazy

This still occurs and from what I can tell it has a lot to do with imported types

Hi! I just experienced this bug at work today :/ However, I found a different workaround that I didn't see listed here, so I'll share it, in case it can be helpful to anyone!
Basically, instead of typing the property using proper Flow annotations, I tried to cast a dummy value, and it prevented eslint from crashing on the 'type' of undefined error:
class MinimalExample {
  // Toggle the comments between these two properties, the second line works!
  #privateProp: Array<number> = [] // Breaks eslint :(
  // #privateProp = ([]: Array<number>) // This works :) !
}

One downside is that it does not prevent the type to be "unioned" with other types in your methods if you happen to change it, say, from an array of numbers to a number proper. It will keep track of the union, at least, but I'd rather get the error at the reassignment (which works fine without the workaround, but then eslint is broken instead) than when I try using it later.
However, it does prevent inserting improper data inside the array for this example, so you couldn't push a string into it by accident, at least!
You can see that behavior if you add this to the class and uncomment one method at a time:
// Only uncomment one at a time, since the reassignment to a number breaks
// the addString below, where #privateProp will be treated as
// `Array<number> | number`.

// setNumber() {
//   this.#privateProp = 42 // Shouldn't work :(
//   // But at least, you'll catch it when you try to read from the array later.
// }

// addString() {
//   this.#privateProp.push('42') // But this does trigger an error properly :)
// }

So I guess if you can tolerate a bit of fuzziness in the type safety in exchange for eslint working properly, this might be another good workaround!

However, this might not be necessary, as playing around with @SebastienGllmt's suggestion using @bradennapier's example made me see that adding an extra type alias seems to fix the problem, at least it did in our code where we encountered the issue. Here's the example from above:
// Fails indeed :(
type Example = string;

class Something {
  #config: Example
}

So trying the "totally unrelated type" solution from above, I realized that creating a dummy alias for another alias... works? Just make sure not to use the dummy alias, but the original alias after having declared the dummy alias, strangely enough.
// Works :O !
type Example = string;
type WhyDoesThisWork = Example;

class Something {
  #config: Example
  // #config2: WhyDoesThisWork // This does not work actually, only the original alias works...
}

So, I guess there's two different workarounds for the problem, at least, for others that will get it.

Thank you for the issue. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.


connecting to wifi and updating nightscout

I had trouble getting onto the dev branch of nightscout and Chris Oattes gave me some command lines that worked beautifully.  The update to connecting to wifi was a question I answered for Berat Kurar and now I see it's already been updated so ignore that part.

If you merge https://github.com/julieraines/docs/pull/1 that should remove the wifi part from the diff.


issue #33 fix

this pull request fixes this issue

@torsten-liermann,
Thanks for contributing this fix!
Can you please join our contributors community by signing JFrog's CLA so that we can merge your code?

I signed JFog's CLA a few days ago and now I need a released version for our Artifactory (version 5.10.1) administrator.
Thanks,
Torsten


Rule idea: warn about unsafe usage of $ in regular expressions

In Python's implementation of re the $ does not only match the end of the line, but also before any line break, even without multiline mode.
There's an article by the OpenSSF about this issue suggesting to use \Z instead, or prefer the fullmatch function.
An example of the issue:
>>> re.search(r'cat$', 'cat\n')
<re.Match object; span=(0, 3), match='cat'>

Using \Z fixes this:
>>> re.search(r'cat\Z', 'cat\n')  # no match
>>> re.search(r'cat\Z', 'cat')
<re.Match object; span=(0, 3), match='cat'>

Or using fullmatch:
>>> re.fullmatch('cat', 'cat\n')  # no match
>>> re.fullmatch('cat', 'cat')
<re.Match object; span=(0, 3), match='cat'>

Should Ruff warn about using $ with search?

In Python's implementation of re the $ does not only match the end of the line, but also before any line break, even without multiline mode.

This is incorrect. In non-multiline mode, $ matches either the end of the entire input or the position right before the trailing newline (only \n, not \r\n). It is similar to PCRE's \Z, whereas Python's \Z resembles PCRE's \z:

Thank you for the clarification.
Based on your example here's a series of calls to highlight the specific behavior of $:
>>> re.search(r'$', 'foo\nbar')
<re.Match object; span=(7, 7), match=''>
>>> re.search(r'$', 'foo\nbar\n')
<re.Match object; span=(7, 7), match=''>    # still matches at pos 7, before the final new line
>>> re.search(r'$', 'foo\nbar\n\n')
<re.Match object; span=(8, 8), match=''>    # matches at pos 8, before the final new line

>>> re.search(r'\Z', 'foo\nbar')
<re.Match object; span=(7, 7), match=''>
>>> re.search(r'\Z', 'foo\nbar\n')
<re.Match object; span=(8, 8), match=''>
>>> re.search(r'\Z', 'foo\nbar\n\n')
<re.Match object; span=(9, 9), match=''>


drivers: modem: gsm_ppp: Enable hooking the setup process

This enables quirky modems, non-standard radio techs etc to work under
Zephyr without forcing developers to maintain huge patches. Previously,
there was no interface for:

configuring NB-IoT or LTE CAT-M1,
specifying the bandmask,
disabling 3G

or a whole slew of other things that one might have to do to accomodate
modems that require slightly non-standard setup steps. This commit
should solve this problem, at least for most modems.
Signed-off-by: Benjamin Lindqvist<EMAIL_ADDRESS>

This requires more work, but first I'd like general input.
This at least enables us to run LTE CAT M-1 and NB-IoT on U-Blox SARA R4, and configure some roaming settings on a SIMCOM7600E, without having to maintain out-of-tree patches. This would not have been possible without this patch.

Is there any updates on the subject? To me it looks quite interesting at least as an idea. I would even prefer if all AT commands are out in the user code and there's no CONFIG_MODEM_GSM_GENERIC / CONFIG_MODEM_GSM_QUECTEL. This way I can support multiple add-on modems based on mdm_model string without the need of different firmware. @ycsin

Are there any updates on the subject? To me it looks quite interesting at least as an idea. I would even prefer if all AT commands are out in the user code and there's no CONFIG_MODEM_GSM_GENERIC / CONFIG_MODEM_GSM_QUECTEL. This way I can support multiple add-on modems based on mdm_model string without the need of different firmware.

I also like the idea that vendor specific configuration would be out of generic driver, although I am not sure that all AT commands would be in user code.  If user has a generic GSM modem without any vendor stuff, there should be no need to do anything special in application part. If the application defines any callbacks, it can override configurations but if it does not define any callbacks, then the default would be used.

@jukkar @ycsin @HrMitrev I am still looking for general comments on this approach (let's hold off on bickering about indentation etc), what looks iffy and what more will be required? For example, this still requires the hooks to do stuff like:
#include "../drivers/modem/modem_cmd_handler.h"

Should we perhaps make these internal headers a bit less internal somehow?
Also, the hook prototypes are pretty weird, but I believe those args are required. An alternative would be to expose the gsm struct.

I am still looking for general comments on this approach

I'd probably have a function to register callback when the state of the gsm driver changes, I think this might be easier after the merge of the FSM implementation, that way I think user can have better control over the gsm driver.
int gsm_ppp_change_state(struct gsm_modem *gsm, enum gsm_state target_state, void *user_data) {
	int ret = 0;

	gsm->state = target_state;
	if (gsm->state_change_cb) {
		ret = gsm->state_change_cb(gsm, target_state, user_data);
	}

	return ret;
}

We probably can have a cb for things like the registration state / rssi as well (application might be able to use these data), but I dont have any real use case for these.

I am still looking for general comments on this approach

I'd probably have a function to register callback when the state of the gsm driver changes, I think this might be easier after the merge of the FSM implementation, that way I think user can have better control over the gsm driver.
int gsm_ppp_change_state(struct gsm_modem *gsm, enum gsm_state target_state, void *user_data) {
	int ret = 0;

	gsm->state = target_state;
	if (gsm->state_change_cb) {
		ret = gsm->state_change_cb(gsm, target_state, user_data);
	}

	return ret;
}

We probably can have a cb for things like the registration state / rssi as well (application might be able to use these data), but I dont have any real use case for these.

So the gsm setup state is an external API now?

So the gsm setup state is an external API now?

It could be public when necessary

So the gsm setup state is an external API now?

It could be made public when necessary

Well... I think internal state should be kept hidden as much as possible. This was discussed in another issue already I believe. External APIs need to be stable. The gsm FSM doesn't seem like a stable API to me.


Colour customisation

Hello again! I really like the colour customisation update, but I have a problem, they only show in edit mode, when I go back to read mode bold color and italic color they show in pink.

I'm pleased to inform you that the issue you mentioned has been resolved. Please update to the latest version of the theme to see the improvements.


[SPARK-32426][SQL] ui shows sql after variable substitution

What changes were proposed in this pull request?
When submitting sql with variables, the sql displayed by ui is not replaced by variables.
Why are the changes needed?
See the final executed sql in ui
Does this PR introduce any user-facing change?
No
How was this patch tested?
manual test

set hivevar:XX=123;
select '${XX}';

Before

After

Can one of the admins verify this patch?

Can one of the admins verify this patch?


[datasets] UnicodeEncode error for € when drawing with default PIL font.

🐛 Bug
UnicodeEncode error for € when drawing with default PIL font.
To Reproduce
Steps to reproduce the behavior:

Set font=None in the train loader of references/classification/train_tensorflow.py
launch python references/classification/train_tensorflow.py mobilenet_v3_small --show-samples

Traceback (most recent call last):
  File "references/classification/train_tensorflow.py", line 245, in <module>
    main(args)
  File "references/classification/train_tensorflow.py", line 124, in main
    train_set = CharacterGenerator(
  File "/home/laptopmindee/doctr/doctr/datasets/classification/tensorflow.py", line 29, in __init__
    super().__init__(*args, **kwargs)
  File "/home/laptopmindee/doctr/doctr/datasets/classification/base.py", line 58, in __init__
    self._data = [synthesize_char_img(char, font_family=self.font_family) for char in self.vocab]
  File "/home/laptopmindee/doctr/doctr/datasets/classification/base.py", line 58, in <listcomp>
    self._data = [synthesize_char_img(char, font_family=self.font_family) for char in self.vocab]
  File "/home/laptopmindee/doctr/doctr/datasets/classification/base.py", line 36, in synthesize_char_img
    d.text((4, 0), char, font=font, fill=(255, 255, 255))
  File "/home/laptopmindee/venv3.8/lib/python3.8/site-packages/PIL/ImageDraw.py", line 469, in text
    draw_text(ink)
  File "/home/laptopmindee/venv3.8/lib/python3.8/site-packages/PIL/ImageDraw.py", line 429, in draw_text
    mask = font.getmask(
  File "/home/laptopmindee/venv3.8/lib/python3.8/site-packages/PIL/ImageFont.py", line 149, in getmask
    return self.font.getmask(text, mode)
UnicodeEncodeError: 'latin-1' codec can't encode character '\u20ac' in position 0: ordinal not in range(256)

Expected behavior
Display of samples
Environment
DocTR version: 0.3.1a0
TensorFlow version: 2.5.0
PyTorch version: 1.9.0+cu111 (torchvision 0.10.0+cu111)
OpenCV version: 4.5.1
OS: Ubuntu 18.04.5 LTS
Python version: 3.8
Is CUDA available (TensorFlow): Yes
Is CUDA available (PyTorch): Yes
CUDA runtime version: 11.4.100
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 2060
Nvidia driver version: 470.57.02
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.2.

Correct, I think we should add OS automatic detection and take a basic font that is compatible (Arial for windows & Mac for instance, FreeMono for Linux)

Closed by #418


Made a change. Yay!

This commit changed a thing.

Coverage remained the same at 55.34% when pulling ef34460a6624b9c36fee43f58f3df53a83b758b8 on briansage:ui2000 into 7ee9198d1460a57e65346cf47b7cf73d8ae5b772 on supergiant:ui2000.


fix: keep diff sig capacity const, reset total samples each pass

Since creating the difference signals shrinks the total number of samples (passed by reference) by one each time, we need to reset to the full capacity each time. This fixes a bug where the total samples in each message got progressively smaller and smaller over time during a deployment.

Great questions @evanShap. Thanks.

Edge case to ponder that I don't fully grok: we're not guaranteed to receive (rawSampleS * 100) / rbrCodaReadingPeriodMs samples from the pressure sensor.
-- If we receive more than this, I expect we just truncate those.

Yes, because of https://github.com/bristlemouth/bm_protocol/blob/04d2a0db7e5c1eb8c5836567f1f469f9dffb07c5/src/lib/common/differenceSignal.cpp#L25 where r_i is the number of readings added so far and r_n is the capacity of the buffer, we only add to the difference signal buffer up to the end and then just ignore subsequent readings.

If we receive less than this, do we only send what we received, or do we end up with random data or 0s to fill out the buffer up to diffSignalCapacity?

We only send what was received, because here https://github.com/bristlemouth/bm_protocol/blob/04d2a0db7e5c1eb8c5836567f1f469f9dffb07c5/src/lib/common/differenceSignal.cpp#L50-L51 num_samples is passed by reference and updated to contain only as many as we've actually received (minus one, because it's the first-order difference signal).
Then when encoding to cbor, we only encode num_samples values from the second-order difference signal here https://github.com/bristlemouth/bm_common_messages/blob/2a44e0ca19ce4eae3174c7ec77a16e95d4c49966/bm_rbr_pressure_difference_signal_msg.cpp#L156-L157


bpf/tests: fix mac addresses definitions in egressgw test

To make it work with 0e3b0bbd3fdfec ("bpf/tests: move mac_one through mac_six to .rodata")

BPF unit/integration Tests is :heavy_check_mark: , marking as ready


Error message when Finch background is not working.

Description
When there is an error in the background process of the extension, the error message is an empty object. I think this is because the background process of the other extension is there and potentially consuming events, but I assume not responding with anything good.
Let's see if we can catch this case and allow the client to resolve a better error message in the errors.

Going to need some better replication to this, kinda created this on a whim, but found it was not exactly defined in the ticket. Going to close, until we run into this again.


Firestore Send Email: Handlebar dynamic Partial not working

Hi everyone. I have a problem with Firestore-send-email extension regarding dynamic partials of Handlebar.Js. Basic Partials are working perfect.
I'm using<EMAIL_ADDRESS>Can someone help me to solve this issue?
Error in email_out entry
error: TypeError: (lookupProperty(...) || (depth0 && lookupProperty(...)) || container.hooks.helperMissing).call is not a function
My entry to email_out
{
    toUids: [someUid],
    template: {
        name: 'myEmailTemplate',
        data: {
            useSpecialFooter: 'mySpecialFooter1',
            firstname: 'UsersFirstname'
        }
    }
}

myEmailTemplate
{
   html: "Hey {{firstname}},
 some content ...

              {{#if useSpecialFooter}}
                     {{>(useSpecialFooter)}} // not working
              {{else}}
                     {{>defaultfooter}} // this is working perfect
              {{/if}}",
   subject: "Hey {{firstname}",
   text: "Hey {{firstname"
}

mySpecialFooter1
{
   html: "
special wishes!",
   text: "\nspecial wishes!",
   partial: true,
   messageId: "mySpecialFooter1"
}

Thank you very much!

Well, my mistake. Finally got it to work with:
myEmailTemplate
{
   html: "Hey {{firstname}},
 some content ...

              {{#if useSpecialFooter}}
                     {{>(lookup . 'useSpecialFooter')}} // use lookup
              {{else}}
                     {{>defaultfooter}} // this is working perfect
              {{/if}}",
   subject: "Hey {{firstname}",
   text: "Hey {{firstname"
}