ValueNotifier is not disposed by tooltip.

To repro, attach leak_tracker to the counter app.
flutter --version
Flutter 3.7.0-7.0.pre.8 • channel master • git@github.com:polina-c/flutter.git
Framework • revision cd9a439c35 (20 hours ago) • 2022-12-13 14:40:48 -0500
Engine • revision 9872cc7add
Tools • Dart 3.0.0 (build 3.0.0-19.0.dev) • DevTools 2.20.0

# For memory leaks troubleshooting tips see
# https://github.com/dart-lang/leak_tracker

not-disposed:
  total: 1
  objects:
    ValueNotifier<bool>:
      identityHashCode: 16539540
      context:
        start: >
          #0      ObjectTracker.startTracking (package:leak_tracker/src/_object_tracker.dart:63:64)
          #1      dispatchObjectEvent (package:leak_tracker/src/_dispatcher.dart:38:19)
          #2      dispatchObjectEvent (package:leak_tracker/src/leak_tracker.dart:71:14)
          #3      main.<anonymous closure> (package:leak_tracker_minimal_flutter_example/main.dart:12:43)
          #4      MemoryAllocations.dispatchObjectEvent (package:flutter/src/foundation/memory_allocations.dart:238:23)
          #5      MemoryAllocations.dispatchObjectCreated (package:flutter/src/foundation/memory_allocations.dart:272:5)
          #6      new ValueNotifier (package:flutter/src/foundation/change_notifier.dart:473:34)
          #7      new OverlayEntry (package:flutter/src/widgets/overlay.dart:138:52)
          #8      TooltipState._createNewEntry (package:flutter/src/material/tooltip.dart:608:14)
          #9      TooltipState.ensureTooltipVisible (package:flutter/src/material/tooltip.dart:552:5)
          #10     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:18:15)
          #11     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:398:19)
          #12     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:429:5)
          #13     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:192:26)

Thanks for the report @polina-c
I tried replicating this but didn't get the log you shared above.

 code sample with leak tracker
import 'package:flutter/material.dart';
import 'package:leak_tracker/leak_tracker.dart';

void main() {
  enableLeakTracking();
  runApp(MyApp());
}
class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or press Run > Flutter Hot Reload in IntelliJ). Notice that the
        // counter didn't reset back to zero; the application is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Hello World'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  _MyHomePageState createState() => new _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug paint" (press "p" in the console where you ran
          // "flutter run", or select "Toggle Debug Paint" from the Flutter tool
          // window in IntelliJ) to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.displayMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

flutter: 0 memory leak(s): not disposed: 0, not GCed: 0, GCed late: 0
Maybe I might have missed something to properly replicate it. Based on the report and error log, labeling this issue for team's attention.

what platform did you use?
I used macos

I am preparing the fix and test coverage for it


postgres: filter PR's by project ID

Resolves https://sentry.io/share/issue/d02a242a9d6d4584b0c41d0296b12dfd/

I'll fix #434 and create tests
recheck

I added the test - but since requre is down I had no way to test it...

Or @TomasTomecek give me a minute please so I can finish it

Or @TomasTomecek give me a minute please so I can finish it

never

I usually run the tests_requre/test_db tests using postgres from docker-compose (by doing export on all the required env vars)

Your test is better than mine https://github.com/packit-service/packit-service/pull/441

But mine still doesn't pass, so if you have it done and passing, though cleptonless, I close this :)

oki, carrying your commit then in #441


How to give blur property to the background

hi,
I am using this component and when the modal opens I want the background to be blur
How can I do this. ?

blurring the content under a translucent  doesn't seem to be possible in React Native without using an external library, I'm afraid.


Managing multiple Apps in a single repo

dokku command app

You mean one repository that has multiple dokku remotes?

Yes. Same as having multiple remotes on heroku https://devcenter.heroku.com/articles/multiple-environments

Thats a great idea. I will try to put something together today :)

Great, thanks!

Took a bit longer, but its now in the v0.2.0 release and on RubyGems :)

Great :+1:


[Typescript] CI/CD {WIP}

[Typescript] CI/CD {WIP}

skipping lint, needs fixes

Stack created with Sapling. Best reviewed with ReviewStack.

-> #46
#42
#43

Disabled Lint, repo isn't implemented to lint rules yet

expected tests to fail, fixing

split into two diffs, ci/cd ontop. This diff contains test fixes


Added toggle function and associated code for enable/disable RDNSS in…

… dhcpv6
Per Issue 4537. Added ability to toggle RDNSS in dhcpv6 settings

I suspect the checkbox goes to services_router_advertisements.php instead?

I suspect the checkbox goes to services_router_advertisements.php instead?

Muppet.. Brain fart moment. Yeah.. I'll move it. :)

Muppet.. Brain fart moment. Yeah.. I'll move it. :)

Via 8ded045

Via 8ded045


feat(plugin-chart-echarts): echarts funnel chart

add funnel of echarts and the demo into plugin-chart-echarts
thx superset, thx your work.
I hope I didn't make you in trouble.
this is a link from funnel of echarts.apache: https://echarts.apache.org/examples/en/editor.html?c=funnel
this is a pic from funnel of superset-ui

@xiezhongfu Thank you Zhongfu, for your contribution! Would you mind attaching a video? I can help you update the description accordingly

@xiezhongfu Thank you Zhongfu, for your contribution! Would you mind attaching a video? I can help you update the description accordingly

sorry, i can not bootstrap the image because of https://github.com/apache/superset/issues/11322
i can not solve the problem

Please resize thumbnail for Funnel Chart, Thanks.

sort and orient control can be aligned vertically

The code all looks good! There are several changes suggested by myself and others in controlPanel.tsx that I think should be addressed. I'd be happy to help with those modifications, too!
Thank you for the awesome contribution.

Thank you. I try to solve the bug  in controlPanel.tsx because I bootstrap superset-frontend in superset after I solved the DNS problem.
You can try those modifications.
SORRY for response the comment after a lone time.

The code all looks good! There are several changes suggested by myself and others in controlPanel.tsx that I think should be addressed. I'd be happy to help with those modifications, too!
Thank you for the awesome contribution.

@xiezhongfu Thank you Zhongfu, for your contribution! Would you mind attaching a video? I can help you update the description accordingly

add a gif instead of video. https://github.com/apache-superset/superset-ui/pull/1006#issue-592363604


[Bug]: Emails are not received when user try to reset the password

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Emails are not received when user try to reset the password
Steps To Reproduce

go to https://ce-26692.dp.appsmith.com/
sign up as<EMAIL_ADDRESS>go to edit profile
under general tab
click on reset password
the user is logged out
But not seeing a reset password emails

Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
v1.9.35

This seems to be working now. Closing and adding QA label.


[BUG] Installation of Helm Charts failed

Willingness to contribute
Yes. I can contribute a fix for this bug independently.
Feathr version
0.9.0
System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.0): MacOS
Python version: 3.9.16
Spark version, if reporting runtime issue:

Describe the problem
When running helm install for installing feathr to kubernetes, connection is refused.
helm install feathr-online feathr-helm-charts/feathr-online

Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "https://kubernetes.docker.internal:6443/version": dial tcp <IP_ADDRESS>:6443: connect: connection refused

Works in @blrchen environment

Connected to AKS and installed Feathr successfully.


Drop special headers from redirected requests

Checklist

[x] I've checked that all new and existing tests pass
[x] I've updated the documentation if necessary
[x] I've added an entry in the CHANGELOG to credit myself

Description
The change in https://github.com/AliSoftware/OHHTTPStubs/pull/263 means a redirected request had the same headers as the original request (because it was a copy and not a brand new NSURLRequest instance).
While the new behavior was correct, it didn't account for "special headers" that URLSession "handles". The docs aren't entirely clear what that means, but we've at least confirmed it removes the "Authorization" headers as that poses a security risk, so this PR removes all those headers + a test.

I think these test failures are related to your changes @sberrevoets ? It looks like master is mostly green (besides some flakes)

I was able to reproduce this once (via rake, I never saw them fail in Xcode 10), but now even rake is succeeding locally.
@AliSoftware any idea what might be going on?

I think the build failures might be related to the race condition bug we discovered in URL session in https://github.com/AliSoftware/OHHTTPStubs/issues/230#issuecomment-380931933 (don't hesitate to duplicate the radar to help us make Apple fix it btw)

Ah thanks for the heads up, I've duped the radar. What would you like to see here in the meantime?

Friendly ping @AliSoftware :)

Sorry for the late reply.
I honestly don't really know. I mean those redirect tests are probably always gonna fail until that Apple bug gets fixed or we find a workaround.
So maybe we should merge that anyway given that the failures are not our fault?
Or a better solution might be to introduce a small delay in the redirection (like what we done in the other PR to confirm the bug was a race condition) as it seemed to at least reduce a lot the bug from happening; even if that means introducing a delay and slowing down stuff a little, that's probably better than failing 70% of the time…?

Yeah that's a very good question. For me it'd probably depend on how much it fails. If it really is 70% of the time right now then adding a delay seems worth it. If it's every now and then, it might be possible to (somehow) auto-retry the affected tests, or take a simpler approach of adding a comment explaining the problem.
I'm also open to alternatives, framework bugs like these are a huge PITA 😕

@sberrevoets - we're reviewing all outstanding PRs before making a release, and then updating the version of Swift being used.  the hope is to do all of this before Xcode 10.2 comes out, so our timeline is a bit tight.
If you are still interested in getting this in, please resolve the conflicts. If you are not interested, having that feedback would be helpful too.

Happy to resolve conflicts (though can't promise I'll have time for that before the 10.2 release), but how depends on what approach is preferable. Based on the conversation above I'm not sure if there's a clear path forward.

@sberrevoets - the flaky tests were disabled in CI (#301 & #302), so you don't need to worry about that part.  We only need the conflicts resolved.

Ah I missed that, that makes resolving conflicts a bit easier. Pushed an update but also gave edit access just in case.

@AliSoftware I updated this branch with the for loop, and I still see the conditional tests.

I was talking about a new test case that @sberrevoets wrote in his initial commits, and that I remember about from when I reviewed the diff on that PR before the conflict resolution today. That new test case which was added in that PR was essentially creating a request, with all the headers of interest here + another header — named "preserved" iirc —, and after using that dummy request and redirecting it, did XCTAssertNil() on all proper headers to check they were properly removed and an XCTAssertEqual() on the one named "preserved" to check it wasn't removed.
That test case seems not to be there anymore (or is my GitHub view of the PR diff on my phone making me missing something?). It probably was removed by the force-push done by @sberrevoets today I guess. While I think it would be worth to have that test case back (even if it ends up not being run on CI because we disabled them there, but they would still be able to be run locally in Xcode)

Oh! My bad man. I thought you meant the buggy test.
Sent with GitHawk

I did remove that test case because it was one of the conflicts. Working on adding that back now.

Added that back and ran it locally - it still passed.

Thanks @sberrevoets :tada:

Thanks for the reviews and suggestions!


[Feature Request] "Migration Guide" from TravisCI to LambCI

Completely self-serving for https://github.com/joemccann/dillinger
Would prerfer to build against LambCI instead of TravisCI

Yeah, good idea – I mean, basically, everything's done in one single command in LambCI – there's no separate phases or anything like that – I find that all a bit confusing to be honest w/ Travis, CircleCI, etc – it just seems easier to me to put that stuff in scripts in your package.json
But yeah, would be good to have it documented I guess.

Right the docs would be nice...I'm gonna give it a go
On Friday, July 8, 2016, Michael Hart<EMAIL_ADDRESS>wrote:

Yeah, good idea – I mean, basically, everything's done in one single
command in LambCI – there's no separate phases or anything like that – I
find that all a bit confusing to be honest w/ Travis, CircleCI, etc – it
just seems easier to me to put that stuff in scripts in your package.json
But yeah, would be good to have it documented I guess.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lambci/lambci/issues/21#issuecomment-231513167, or mute
the thread
https://github.com/notifications/unsubscribe/AAC8alqOBnzHVPQTwqi0bISGLTa-Z1sUks5qTxqmgaJpZM4JIhEw
.

--
Sent from Joe In Real Life


[Bug]: Edit taxon name- Persons- Clone from Source: Author order for taxon name does not match author order of source

Steps to reproduce the bug
When using "Clone from Source", the author order of the taxon being created does not match the author order of the source.

Screenshot

Source is Makhan and Hawkeswood

But taxon authors are switched to Hawkeswood and Makhan
Expected behavior
No response
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
No response
Browser Used
chrome

Confirm


Is it possible to add a min-length for data live search?

Not really a bug, but I was wandering if it's possible, either out of the box or do it myself, to add a minlength for the data-live-search box?, so it starts filtering when you type more than 3 character, for example

tell me if you find a solution man, i need it too


Numpy compatibility

This allows compatibility with the latest version of numpy (1.10.1), as discussed in https://github.com/PyAbel/PyAbel/issues/51. Only change was to explicitly cast nx and ny to floats in index_coords. I think that they were being automatically being cast to floats previously, so the behavior should be the same.

This looks good!
Also, I think it could be a good practice when we encounter a bug to add a small unit test that fails with this bug, and then passes with the fix. For instance, here, @DanHickstein would you mind adding
 def test_speeds_non_integer_center():
     n = 101
     IM = np.random.randn(n, n)
     calculate_speeds(IM, origin=(50.5, 50.5))

to abel/tests/test_tools.py (or something similar), before merging this ? This would make sure that if somebody were to edit the speed generation function at some later time, this bug would not be reintroduced again by accident...

Good idea to add the test. It's in there now.


Add a code formatting check to CI

Stacked on top of #6; please review that first. I will update this PR if/when PR #6 is merged.

Updated this PR branch, which includes:

formatting all our code using black
adding a configuration for black in pyproject.toml
adding black --check . to a CI step

Tests still will not pass; that will happen in a follow-up PR.


Fix: Do not leak Random seed in fmt::Debug implementation in spinoso-random

Previously, printing a spinoso_random::Random with the debug format specifier would output something like:
---- random::tests::fmt_debug_does_not_leak_seed stdout ----
thread 'random::tests::fmt_debug_does_not_leak_seed' panicked at 'Random { mt: Mt {}, seed: [123456, 0, 0, 0] }', spinoso-random/src/random/mod.rs:325:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    random::tests::fmt_debug_does_not_leak_seed

which leaks the internal seed.
It is typical for PRNGs to hide internal state in fmt::Debug implementations.
This commit alters the debug repr of Random to print Random {} and enforces this behavior with a test.

This latest commit adds similar tests to the internal Mt mersenne twister for completeness.


[IOTDB-2038] MqttService accesses to BasicServiceProvider

see : https://issues.apache.org/jira/browse/IOTDB-2038

Coverage increased (+0.04%) to 67.011% when pulling fa091afb8df3328605a189360d8be4b4862cd290 on jun0315:mqtt_access_basic_provider into d9d8733f17878cd07e4510a7f9b3af92049863c3 on apache:master.


imx95: Fix eDMA compilation

Summary
imx95: Fix eDMA compilation
Also clarify that the imx95 uses eDMA5 instead of eDMA4 (imx93 has eDMA4)
Impact
imx95
Testing
imx95-19x19-evk

[Experimental Bot, please feedback here]
No. The PR description lacks crucial information required by the NuttX guidelines.  Here's a breakdown:

Insufficient Summary: While it mentions the "what" (fixing eDMA compilation and clarifying eDMA5 usage), it omits the "why" (why was the compilation broken?), "how" (what code changes were made to fix it?), and related issue references.

Incomplete Impact: Simply stating "imx95" isn't enough.  The PR author needs to explicitly answer the YES/NO questions for each impact category (user, build, hardware, documentation, security, compatibility) and provide descriptions where necessary.  Even if the answer is NO, stating it explicitly is important.

Missing Testing Details:  "imx95-19x19-evk" is insufficient.  The author must specify the build host details (OS, CPU, compiler) and provide actual testing logs from before and after the change to demonstrate the fix.  Simply stating the target board doesn't prove the fix works.

The PR author needs to revise their description to address these missing points before it can be considered complete.

let's igore ci break which is fixed by: https://github.com/apache/nuttx/pull/15240


Way to communicate more information between libraries

I'm trying  to thinking about a way for pydantic to communicate extra field information to hypothesis which is:

reusable by other libraries - e.g. doesn't use hypothesis types
doesn't require any understanding of pydantic internals - e.g. not based on pydantic core schema
can be extended without further integration discussion - e.g. is a proper protocol, not a list of types

For reference here is the hypothesis plugin from pydantic V1. The types we'd like to support with this system are as follows:

EmailStr - a string that is a valid email address, could crudely be just a regex
NameEmail - email and name in the name <email> format, can be a regex + email
PyObject (now ImportString) - string that can represent anything, the hypothesis plugin used a random attribute of math
Color - could be a regex
luhn valid card number - currently generated by trial and error
IPvAnyAddress - either IPv4 or IPv6
JsonWrapper - a JSON string, possibly with a type hint

Everything else I think is covered by using Annotated and things already defined by annotated-types.
Note in V2 some of the above are implemented as arguments to Annotated (albeit with an alias), some are legitimate custom types.
One idea I thought of was to use JSON Schema - you provide a method or property on either type or argument to
Annotated which returned some JSON Schema. But looking at the above list, I don't think JSON Schema would help with many.
Therefore here's my proposal:
annotated-types defines a new property or method on types and arguments to Annotated which returns the following
pieces of information (could be a tuple, a dict with specific keys, or a dataclass defined herein):

documentation_example - a canonical example of the datatype as might be shown in documentation, e.g<EMAIL_ADDRESS>random_example - a random varying example of the datatype, e.g<EMAIL_ADDRESS>type_code - a string that libraries can use to identify the type (e.g. email), and thereby decide to do more powerful things - e.g. hypothesis has a better strategy for generating random email addresses than pydantic will. Would be None if no type_code exists for a field.

The idea is that annotated-types defines:

the above data structure
a list of agreed type_codes, starting with the ones from above

Example usage
EmailStr: would emit ExtraTypeInfo('email'<EMAIL_ADDRESS>'ad90cj-i3ljlkd@dk33w4poedd.co.uk').
hypothesis would ignore the crude random example and use it's own strategy for email addresses since it recognises the email type code.

Color: would emit ExtraTypeInfo('color', '#ff0000', '#00ff00'), if hypothesis doesn't recognize color it could
fallback to using the random example generated by pydantic.

If a user wanted their own UKPostCode type (alias of Annotated[str, UKPostCodeMetadata]), then UKPostCodeMetadata could emit ExtraTypeInfo(None, 'W1A 1AA', 'sp119dg'), None for type code since no type code exists for uk post codes, hypothesis would use just use the random example 'sp119dg'.

In theory another tool could use this data (e.g. for generating documentation) with no knowledge of hypothesis or pydantic.

I'd love to get this agreed in principle fairly quickly so we can release V1 with at least a strategy in place (pun intended) to solve this, and ideally the pydantic side written.

Should random_example be an iterable maybe? Just to allow adding some more randomness to it 🤷🏻♂

yes good idea. I was thinking (but forgot to add) that the library would call the function multiple times to generate different examples. But an iterator, would be best as it could either be a simple list, or an infinite generator.

Hmm, this seems like a lot of stuff that is very specific to Pydantic and Hypothesis. I would rather this package remain more neutral. Could this instead be something that Hypothesis provides? I haven't written a Hypothesis plugin but maybe something like:
from hypothesis.plugin import Analyzer, MetadataProtocol, HypothesisMetadata

class PydanticHypothesisMetadataTransfer(MetadataProtocol):
    def gather(self, type: Any) -> HypothesisMetadata | None:
        # do internal stuff

Analyzer(gather_metadata=PydanticHypothesisMetadataTransfer)

And if PydanticHypothesisMetadataTransfer.gather returns a HypothesisMetadata then Hypothesis can stop recursing/analyzing the type. If it doesn't, then Hypothesis does its thing.
Essentially, Hypothesis would have to define what metadata it needs from a type and Pydantic would have to figure out how to transform it's json schema or other already done analysis into Hypothesis' metadata.

I think this could already be done with a hypothesis plugin, I just thought a general solution would be more powerful.
I don't think the the idea of:

an agreed unique string with describes a type, or
an example of the data

Are that unique, but I understand if this is too much of a step for annotated-types.

The random_example is an antipattern for Hypothesis, because it breaks shrinking, so we need a way to generate from strategies in the first place.  I think there are two parts here:

For custom types, have a Hypothesis plugin which registers a strategy for that type.  luhn valid card numbers, IPvAnyAddress, and JsonWrapper might be in this category?
For Annotated[T, ...] types, we can use a neat deferred-resolution hack using Hypothesis resolution of st.from_type(Annotated[T, ..., some_strategy, ...]) to some_strategy and the GroupedMetadata annotation:@dataclass
class MaybeStrategy(GroupedMetadata):
    def __iter__(self) -> Iterator[object]:
        if hypothesis := sys.modules.get("hypothesis"):
            yield st.builds()  # or whatever you want here

This is basically @adriangb's idea but without needing any new features 😁
(ok, we might want to document that iterating a GroupedMetadata might produce non-BaseMetadata objects)

and I think that those two probably cover all the motivations in this issue.

Mostly sounds good.
Does that mean all arguments to Annotated that want to have to inherit from GroupedMetadata? I guess that's a price worth paying in this case.
The if hypothesis := sys.modules.get("hypothesis") looks a bit brittle, e.g. what happens if you want to expand a MaybeStrategy to get the normal stuff, but happen to have imported hypothesis?
Do you think hypothesis could set a contextvar or similar so there's a safer way to detect that I'm being expanded by hypothesis?

Does that mean all arguments to Annotated that want to work with hypothesis have to inherit from GroupedMetadata?

Yep, price seems pretty low though.

The if hypothesis := sys.modules.get("hypothesis") looks a bit brittle, e.g. what happens if you want to expand a MaybeStrategy to get the normal stuff, but happen to have imported hypothesis?

Then you also get a SearchStrategy object in the annotations, which the rest of your code presumably ignores.

Do you think hypothesis could set a contextvar or similar so there's a safer way to detect that I'm being expanded by hypothesis?

Unfortunately this would miss some cases... I think the sys.modules approach is the best option available.

Does that mean all arguments to Annotated that want to work with hypothesis have to inherit from GroupedMetadata?

Yep, price seems pretty low though.

Speaking of: #36

@Zac-HD Sadly this doesn't seem to work
@given(data=st.data())
def test_hypothesis_uuid_version_pure(data):
    from hypothesis import strategies as st

    @dataclass
    class UuidVersion(GroupedMetadata):
        uuid_version: Literal[1, 3, 4, 5]

        def __iter__(self) -> Iterator[object]:  # type: ignore
            if 'hypothesis' in sys.modules:
                from hypothesis import strategies as st

                yield st.uuids(version=self.uuid_version)

    value = data.draw(st.from_type(Annotated[UUID, UuidVersion(1)]))

    assert isinstance(value, UUID)
    assert value.version == 1

Using hypothesis 6.75.3

Ah, https://github.com/HypothesisWorks/hypothesis/issues/3356 jjst hasn't been implemented yet 😅
Hypothesis runs strictly on a "no roadmap, features happen when someone volunteers to write them" basis, I've been kept busy by work and bugfixes and my phd and other features, and nobody else has taken it on yet.

@Zac-HD, please do not apologize - your work in open source is a gift, not an expectation.

Looking at this again, I think an annotatedtypes.JsonSchema annotation would actually get most of these working - and hypothesis-jsonschema already exists, so I could easily defer to that to generate examples.
We already support emails, IP addresses, and colors via string formats, and Schemathesis can pass in strategies for custom formats like card numbers.  Handling the remaining items on the list could be done interoperably by moving the custom-formats registry to hypothesis-jsonschema (for Pydantic and Schemathesis to share), and then I think we'd be done!

Would love to get involved in this effort! I'm thinking about how to revamp the pandera data synth strategies and came across this project. Is this library something I can start testing out in the pandera codebase?

Yep, you can start testing it out now!
Unfortunately that won't help with strategy inference until we get https://github.com/HypothesisWorks/hypothesis/issues/3356 working - complete support on the Hypothesis end will indeed "totally solve the problem" but also be enough work that it's unclear when it'll happen.  I'm hoping to set aside a few days in August or September for this, but it depends on how busy I am at work.
In the meantime, https://github.com/unionai-oss/pandera/issues/404#issuecomment-784806773 would make Pandera-derived strategies for integers and floats much more efficient 🙂


Migrate from facility to metro lingo

The Equinix Metal API has deprecated¹ use of the facility² keyword back in 2023-05 and now after 2024-03-31 it will be removed.
It has been replaced by the metro³ keyword, that serves a same purpose.
The "any" metro can be used to set no restriction on instance creation.
[1] https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros
[2] https://deploy.equinix.com/developers/docs/metal/locations/facilities/
[3] https://deploy.equinix.com/developers/docs/metal/locations/metros/

Deployed on rhea.

Apparently facility is still a required field on the create device API.
systemd[1]: Started hydra-scale-equinix-metal.service.
scale[2756758]: Work summary:
scale[2756758]: System("aarch64-linux") BigParallel = 22
scale[2756758]: System("aarch64-linux") Small = 0
scale[2756758]: System("x86_64-linux") BigParallel = 25
scale[2756758]: System("x86_64-linux") Small = 5803
scale[2756758]: WARNING: System("aarch64-linux")/BigParallel has no hardwarecategory in the hardware map
scale[2756758]: WARNING: System("aarch64-linux")/Small has no hardwarecategory in the hardware map
scale[2756758]: Creating: HardwarePlan {
scale[2756758]:     bid: 2.0,
scale[2756758]:     plan: "c3.medium.x86",
scale[2756758]:     netboot_url: "https://netboot.nixos.org/dispatch/hydra/hydra.nixos.org/equinix-metal-builders/main/c3-medium-x86--big-parallel",
scale[2756758]: }
scale[2756758]: Error: failed to parse json, here's the raw content: Object {
scale[2756758]:     "errors": Array [
scale[2756758]:         String("You must specify a valid facility parameter"),
scale[2756758]:     ],
scale[2756758]: }
scale[2756758]: Caused by:
scale[2756758]:     missing field `hostname` at line 1 column 58
scale[2756758]: Location:
scale[2756758]:     src/device.rs:92:10
systemd[1]: hydra-scale-equinix-metal.service: Main process exited, code=exited, status=1/FAILURE


fix #35, we now can ignore all devDependencies folders !

I also ignore all files under src/ ! We don't need them when building an application :)


Remove delay and timeout config; add random jitter

Timeout really doesn't need to be exposed to the end users for each request.
I think the configurable delay should be replaced with a random delay randomly selected from a range. This increases the opsec of Respotter in case an adversary runs Responder in audit mode before poisoning responses.

This is a breaking change -- I'm going to move it to the v1.0.0 milestone


Diffs are applied as they are received (as soon or as late)

Client changes their world as soon (or as late) as they receive diff from network. That means that the experience is immediately not smooth if the network is not smooth (loss, latency, jitter).
We need a way to synchronise with the server and pace applying of the changes, we might need interpolation first (#662).

Unity time synchronisation<EMAIL_ADDRESS>


Feature/fluent theme tidy

What does the pull request do?

Embeds open sans font.
sorts out the default background colours
fixes the control corner radius
only use avares for theme

TODO

[ ] notifications
[ ] remove remaining references to old resource names
[ ] release 0.10-preview1


Question about upgrading CSE from 1.12 to 1.13

File: cs-engine/1.12/upgrade.md
Change version from 1.12 to 1.13
Use these instructions to update APT-based systems.
Add the docker engine repository.
$ echo "deb https://packages.docker.com/1.13/apt/repo ubuntu-trusty main" | sudo tee /etc/apt/sources.list.d/docker.list

Closing per triage discussion, @joaofnfernandes is going to file replacement bug.


context provider for @selection that only provides currently selected code under cursor?

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
The @code context requires selecting files
I was thinking of having a @selection context that will provide the code currently selected
Solution
No response

When the selected code is selected, is it better to automatically add the selected code during the session

@championswimmer curious to understand why this over ctrl+L? I can see the scenario perhaps where it reduces the necessary number of keystrokes/mouse movements

@sestinj This might be a habit issue. Tools like GitHub Copilot , Cody typically only require selecting the code.

Quite some time ago we automatically included the selected context but overwhelmingly got feedback that this made it difficult to select more than one range, and that many users frequently highlight code as they are reading it, which causes a lot of unnecessary flashing in the input box. Right now we're going to stick with using cmd+L, but if we hear enough feedback that there's a clear improvement to make, we'll definitely be willing to change!
In the meantime I do think the @ selection idea is a good one

Hello!
I missed the same feature (including currently selected content in chat) in Continue. In this way we can precisely provide most relevant code to LLM, which I certainly am more sure than letting LLM itself to pick out from provided whole file. And in my usecase a large percent of requests are in the following process: when I select relevant code and ask my question without any instruction, the plugin I use (ali tongyilingma most, which is based on Qwen LLM) will automatically insert selected code below my question. I feel this very convenient, though in few cases I do wrongly select irrelevant code, but it does not make more trouble than convenience it brings. So I think it's worth supporting implicit insertion of selected code into chat (without explicit @selection mark), or maybe add an option to let user choose?
Regarding providing multiple selection code ranges, I think this is a useful feature, though maybe not so frequently used. It can solve some problem, without which it would be hard or even impossible to instruct LLM to do thing right. (because providing too few or too much information).
I think multiple selection is most useful when:

working on larger source file, where relevant code may not stay together so you cannot include them with one selection range, and if you select them all in one range you would include too much irrelevant code, which may confuse LLM.
or well structured code base which tends to cut code into Single Responsibility pieces, but in order to resolve actual problems you have to chain pieces together from different places.

regarding how to add single or multiple selected code range into chat, I agree @selection is a good way. when input @selection in chat window, maybe the plugin can record current selected code range inline, just like follows:

I defined XXX in following code: @selection file1.py: 25~50, but it reports YYY problem in following code: @selection file2.py: 100~120. Help me check what's wrong.

in which file1.py: 25~50 and file2.py: 100~120 is automatically extracted from selection range at the moment @selection is input into chat box. And when chat content is sent to LLM, the plugin automatially replace @selection marks with corresponding code.
It may seem a little cumbersome, but I think it's useful when needed, just like cherrypicking in git.


Error

Please tick all applicable boxes.

[x ] I am using Python 3.5.3 or higher (run python --version on the command line)
[x ] I have followed the official guides to install the bot for my system
[ x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[ ] The latest master version (release-260419)
[x ] The latest review version

What type of issue are you creating?

[x ] Bug
[ ] Feature request
[ ] Question

Description of issue
File "run.py", line 373, in main
m.run()
File "E:\Barf\Bots\djtemps\musicbot\bot.py", line 902, in run
self.loop.run_until_complete(self.start(*self.config.auth))
File "D:\Python\lib\asyncio\base_events.py", line 568, in run_until_complete
return future.result()
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\client.py", line 543, in start
await self.connect(reconnect=reconnect)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\client.py", line 457, in connect
await self._connect()
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\client.py", line 421, in _connect
await self.ws.poll_event()
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\gateway.py", line 469, in poll_event
await self.received_message(msg)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\gateway.py", line 423, in received_message
func(data)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\state.py", line 663, in parse_guild_create
guild = self._get_create_guild(data)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\state.py", line 638, in _get_create_guild
guild._from_data(data)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\guild.py", line 391, in _from_data
self._sync(guild)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\guild.py", line 420, in _sync
self._add_channel(VoiceChannel(guild=self, data=c, state=self._state))
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\channel.py", line 504, in init
self._update(guild, data)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\channel.py", line 535, in _update
self._fill_overwrites(data)
File "C:\Users\Kaden\AppData\Roaming\Python\Python37\site-packages\discord\abc.py", line 271, in _fill_overwrites
self._overwrites.append(_Overwrites(id=overridden_id, **overridden))
TypeError: new() got an unexpected keyword argument 'deny_new'
Steps to reproduce

I updated and now I'm getting this
musicbot.log

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.

I started my bot, but there's and error!
__new__() got an unexpected keyword argument: 'deny_new'
If you are on windows, simply do py -m pip install -U discord.py[voice] and that should fix it.
If you are on linux or mac os, do pythonx.x -m pip install -U discord.py[voice] and replace x.x with your python version, for example python3.7 and your error should be gone aswell.
You can also change the requirements.txt file so that it looks like this:
discord.py[voice]==1.3.4
pip
youtube_dl
colorlog```

Then run update.bat(if your on windows, if not chose the appropriate update file for your system OS) once it's all up to date, then do run.bat(same note as before)


Offckb always displays a deprecation warning.

The offckb tool always displays the following warning:
(node:12542) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead

We need to find a way to remove or suppress this warning so new developers are not distracted by it.
This was observed using Node v20.12.0 LTS (newest LTS via nvm).

-https://github.com/RetricSu/offckb/pull/50
not sure if this will work

Yes, this is fixed in v0.1.0.


Can't get range

I'm attempting to test 1 tag and 1 anchor with DW1000_Ranging_ANCHOR and DW1000_Ranging_ANCHOR to get distance values. However, I kept getting "Not found", "blinks" and "delete inactive device" messages on the anchor end and never received any distance results on either end.
The screenshot here shows one of my testings

I also tested the BasicConnectivity and BasicSender/Receiver examples to make sure connections are good and the tag and anchor are able to communicate. They seems to be working fine.

Could anyone tell me what part might have gone wrong that's causing it and how to fix it? Thank you!

Hello, I'm starting to learning code, but it seems that Tag is not receiving Ranging Init and Anchor is deleting Tag for inactive time. But it seems that you receive a frame from Tag (or another device) that is not listed in Anchor list. This is when you see "not found".
Did you change any define timings?
A good way to know code is to put printf in every action of send and receive in order to know where you are.

@xforus Thanks for your comments. And no, I didn't change anything on the code. And when you said the Anchor list, does it mean it's predefined?
I'm still pretty new to this, so any suggestions would be appreciated!

Hi, this happened to me when I increased the number of anchors to 3 but not 1. Anyway, you can try what I suggested in issue #179 . Hopefully, it helps.

Hi @ybc82
I hope I followed your method correctly,
DW1000Ranging.h file
static volatile uint8_t getNetworkDevicesNumber() { return _networkDevicesNumber; }; (line 96)
static volatile uint8_t      _networkDevicesNumber; (line 126)
DW1000Ranging.cpp file
volatile uint8_t      DW1000RangingClass::_networkDevicesNumber = 0; (line 41)
Though, I tested the DW1000Ranging_Anchor/Tag code, and got the similar results as before.
May I ask you how you powered your device? I've been using the USB to power both of my Arduino UNO so I wonder if it might have something to do with lack of power supply that's causing my device to be "inactive"? Thank you!

UPDATES:
I tried out the RangingAnchor/Tag examples since I'm able to read the code a little easily through them. I found out that @xforus was correct about my previous results. I added serial.print on every steps of the message sending between my anchor and tag, and I noticed -

Tag constantly sends POLL to Anchor.
Anchor occasionally gets POLL from Tag and tries to send POLL_ACK back.
Tag never detects any POLL_ACK message from Anchor and Anchor never gets RANGE from Tag, so the cycle stops.

I switch over my Tag and Anchor devices to test the program but got the same results. So my guess is that, the Anchor can find the Tag but the Tag doesn't recognize the Anchor.
I also tried changing operation mode to MODE_SHORTDATA_FAST_ACCURACY etc.., still no luck. I'm not sure if anyone has had this exact issue but I'm hoping to get some different ideas for me to try out.
Thank you!

@hu265 I did not do the 'line 96' change, and other changes you made were exactly the same with what I did. Besides, since you are having this problem when there are only 1 anchor and 1 tag, and I had this issue when there were 3 anchors and 1 tag, it might be possible that there are some other causes.
On my board, the USB 5V power is connected to an LDO with 3.3V output, which provides power to both the Arduino chip and the DWM1000 module. I don't know how you're powering the DWM1000 module, but it can be a problem if its power source cannot provide enough current.
Besides, I'm using Arduino Pro mini. I'm not sure if things would be different on UNO.
Btw, I tried hard-code to stop sending all blinking messages, which theoretically would be helpful to communication condition. But this did not help in my case anyway. And this solution is probably more complicated.
Thank you!

@ybc82 what mode are you using and are you getting all three ranges consecutive like
from anchor 1
then anchor 2
then anchor 3 so on

Hi!
Tell me please how you connect dw1000 to arduino... I not receive any thing

@Rotzbua
hello sir,
i have created 3 anchor modules and a tag and everything works fine. Whn i connect the anchors and tag, my tag recieves a flow of data like in the attached picture from each anchor at a time sequentially. All i want to do is to store these values in a 3by 1 matrix like as follows,
`float mat[3][1];
mat[0][0]=value from 1st anchor node;
mat[1][0]= value from 2nd node;
mat[2][0]= value from 3rd node;
`
likewise. but when i initilaize and save values to the matrix (inside the newRange function) it saves like follows,
mat[0][0]=value from 1st anchor node;
mat[1][0]= value from 1st node;
mat[2][0]= value from 1st node;
are there any way to correct this issue.?


@react-email/tailwind Package dist size is too large

Describe the Bug
I am trying to use react-email with TRPC and Next.js I ran a profiler on the output of next build with @next/bundle-analyzer It said the largest package was coming from @react-email/tailwind/dist/index.mjs
I am running Next.js with Open-Next deployed with SST on a Lambda in AWS. The larger the Node.js portion of the next.js code is, the longer it takes for the lambda to start. Currently it looks like @react-email/tailwind is 6.5MB
At first glance, it looks like it's pulling in all of tailwindcss and postcss here: https://github.com/resend/react-email/blob/canary/packages/tailwind/src/utils/get-css-for-markup.ts#L1-L4
Is there a way we can make this package smaller?
Which package is affected (leave empty if unsure)
No response
Link to the code that reproduces this issue
https://github.com/resend/react-email/tree/canary/packages/tailwind
To Reproduce
Run next build with @next/bundle-analyzer
Expected Behavior
The dist folder to be smaller.
What's your node version? (if relevant)
No response

Is there a way we can make this package smaller?

It certainly is something that we want to improve on and that isn't in the least optimal. The best way I found to do it was to bundle it as it is,
it might not just be postcss and tailwind that make the biggest impact on this though but rather the necessary
polyfills for internal tailwind dependencies. We polyfilled because it was either that, or patching tailwind to remove all imports for non-browser stuff.
I think there might be a way for this by not using postcss necessarily but it would need a bit of a change of the way
we do things currently. Might also avoid rendering twice for generating the styles.

I have the same problem. I can't push the code to the next.js edge runtime because react emails bundle is way too large. A main problem I see is the js-beautify lib.

Same problem here
➜  node_modules du -sh -- */ | sort -rh
509M	react-email/
275M	@next/
182M	canvas/
103M	next/
65M	typescript/
62M	next-translate-plugin/

509mb of disk sizes in my docker image any way to reduce it?

@jlopezxs This issue is about the @react-email/tailwind package, not the react-email one.
For the react-email package, you should be able to just move it to a dev dependency, as it is just the CLI, and if installed with npm install --production it will not be included.
Also, there was an issue we fixed a while ago that might improve the size for you, so upgrading is also something you can do.

@jlopezxs This issue is about the @react-email/tailwind package, not the react-email one.
For the react-email package, you should be able to just move it to a dev dependency, as it is just the CLI, and if installed with npm install --production it will not be included.
Also, there was an issue we fixed a while ago that might improve the size for you, so upgrading is also something you can do.

Is this something that should be documented in the docs? I was also having trouble with my bundle size, and your suggestion worked wonderfully. I can't imagine it would hurt having a smaller production bundle size, especially for serverless environments.

@PCRinus, Certainly. Wonder where you would think we could best fit a mention of this?

I'd say that the places which would need to be better documented are in the manual setup page and the monorepo setup page for each package manager. There might be additional places as well, so I'll look into it more.
I can also open a PR with the documentation changes, if that's okay

@PCRinus That would be lovely if you could! Feel free to open the PR and I'll review it.

For those having this issue in their project, try deleting your repo's folder, re-cloning, and re-installing the packages. It worked for me.

Hey @gabrielmfern, here is the PR link for this small docs change: https://github.com/resend/react-email/pull/1522, I imagine you folks have a lot of work going on, so this might get lost

I am facing a similar issue where the react-tailwind package is one of the largest. What's the best way to reduce size?

Can we use cssnano to decrease dist bundle size for react-email/tailwind?

We just merged #1383 and released it under canary<EMAIL_ADDRESS>should be fixed


Wrong score calculation in variant of most crossing

Hi,
I've found a bug when you calculate the score in the variant of most crossing.
https://github.com/quibbble/go-tsuro/blob/a30d5867d5ecc0c5cd35dfb1d8f2e1469d43e240/state.go#L326-L349
This algorithm runs incorrectly in the following example, because it should worth 4=1+3 points, but it gives only 3=1+2 points:

Solution: Instead of choosing the highest element in pathScores you have to sum the scores in pathScores and divide by two.
This algorithm will clearly work for all tiles except the following one:

Here you have more options for how many points it is worth, when 3 or 4 paths (of the same player) are crossing in the middle of tile.

If 3 paths are crossing in the middle of tile, it should worth 3 points, and if 4 paths then 6 points.
If 3 paths are crossing in the middle of tile, it should worth 2 points, and if 4 paths then 3 points.
It should always worth 1 point.

The first case does not need any further implementation, but the other two one should handle this special tile.
I personally think that the first option is the fairest, because if you move the lines a bit so, that there will be no 3 paths of them, that intersects in one point, then there will be 6 points.

Hey @fraknoiadam thanks for opening this issue. I agree that the first option is the fairest and probably the best path forward. If you would like to take a stab at fixing this and open a PR I'd appreciate the help. Otherwise I'll look into fixing this when I have some spare time.
Either way thanks for the detailed writeup and help in improving Quibbble!

The change has been made and is now deployed. Thanks again for posting this issue.


Gremlin API

Does the connector support gremlin APIs ?

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

ID: 5c77b390-e483-d7d4-3ea8-813a296c9e89
Version Independent ID: 3b1e6865-894e-9958-3e6d-4b04bf40e892
Content: Connect Apache Spark to Azure Cosmos DB
Content Source: articles/cosmos-db/spark-connector.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @tknandu
Microsoft Alias: ramkris

@vikasgoyal We are looking into this and will get back to you

@vikasgoyal Could you please explain what you are trying to achieve and which connector you are talking about because Cosmos DB has Spark connector , Spring data connector and both support SQL API only.

@Oury-MSFT I didn't know you were referring to the question on Gitissue. This issue is on the spark connector doc see the content in the above description.
@vikasgoyal this connector currently doesn't support the Gremlin API.

@SnehaGunda Thank you for your clarification.

@SnehaGunda Thank you for the guidance here.
@vikasgoyal We are going ahead and closing this question. If you have any other, please get back to us.


Modified write_hex_file() to support big endian mode

I used a simple reverse algorithm to reverse the data bytes before writing them to the bin dictionary. Use it by specifying new argument "endian_mode" as "big" when calling write_hex_file().

All of the "duplicate" commits were just me removing annoying whitespace changes that my text editor added

Sorry for not working on your pull request. I'm looking for a new maintainer for Python IntelHex project. I hope someone will help.

OK, I see - you're modifying data inplace, so after write_hex_file the IntelHex object is totally modified. I don't like such side-effects, and I think it's counter-intuitive to expect them from method that should be just "export" data. So I think your addition is better to make as a separate method. Sorry, I reject your patch.


Hard fault

Hey. Trying to run the gif library on stm32f407. I get hardfault after launch. I get "invalid signature" in the console. But the process continues to run after that.

It seems there is no proper error handling in the lib.
"Invalid signature" means the GIf file was invalid.

I've added error handling here:
https://github.com/lvgl/lv_lib_gif/commit/d64a40001fe01e35e01533b8deee942756943617

can you send any correct gif file for test?

it works for me:

Hardfault is passed. But "invalid signature" is in place. I use your gif file placed in the root of SD-card.
I also have a problem reading images from the card. All UI elements are created successfully. But the images are not loading. Maybe this is a common problem?

How do you set the path of the files? Do you use LVGL's files system API?
E.g. S/path/to/image.gif

"S:/path/to/image.gif"
But images with errors in .bin format
Problem with cache start after include lv_lib_gif and replace lvgl version (feat/new-fs-api) and lv_fs_if(new-api)

You don't need to convert it into bin, just use the gif as it is.

I do not convert .GIF to .bin. The cache issue was with old files that were loaded from SD card(background pictures). Images from flash(button icons) are loaded and displayed normally.

I suggest using a simulator (I use Eclipse you can use other) to have a common platform to investigate the issue.
If you place the images to the projet's root folder and you enable  LV_FS_IF_PC       'P' it should work for "normal images":
lv_img_set_src(img, "P/my_image.bin");

Is it working?

.bin working good with master-branch jf lvgl
can i use lv_lib_gif with master branch or only with new-fs-api?

When i use without lv_fs_if library have this errors http://joxi.ru/n2Ybe6hbDObbA6 (with master branch of lvgl .bin files are open good with "S:/path/to/image.bin"). Where i can add disk letter for new-fs-api branch of lvgl?

can i use lv_lib_gif with master branch or only with new-fs-api?

No, I made some changes in the FS API when added the GIF library.

When i use without lv_fs_if library have this errors http://joxi.ru/n2Ybe6hbDObbA6 (with master branch of lvgl .bin files are open good with "S:/path/to/image.bin"). Where i can add disk letter for new-fs-api branch of lvgl?

If you don't use lv_fs_if you need to register a driver yourself. See here https://docs.lvgl.io/latest/en/html/overview/file-system.html


[BUG] Vision OS - 'UIScreen' is unavailable in visionOS

New issue checklist

[ ] I have reviewed the README and documentation
[ ] I have searched existing issues and this is not a duplicate
[ ] I have attempted to reproduce the issue and include an example project.

General information

Superwall version:
iOS version(s):
CocoaPods/Carthage version (if applicable):
Xcode version:
Devices/Simulators affected:
Reproducible in the demo project? (Yes/No):
Related issues:

Describe the bug
'UIScreen' is unavailable in visionOS

Thanks for spotting this, will be fixed in the next update!

This issue is still happening on the latest release. Would it be possible to fix it? Otherwise, visionOS App with the SDK can't be updated. Thank you!

Oops, you're right. Have fixed now and will be in the next release, sorry about that!

Thank you so much! 🙌


AMQ-8613 Improve performance of selectors with a big sequence of OR and AND logical expressions

@eolivelli can you please squash all commits in one ? Thanks !

@jbonofre I have a followup patch, regarding Equals and Not expressions.
I will do have numbers within the end of the week.

@jbonofre I have a couple of additional enhancements.
I have some numbers on our applications (with this PR + the follow up patches, all stacked), we are saving some good amount of CPU cycles and we decided to commit these changes in our repo.
@dave2wave has some numbers, but I am not sure they are meaningful here.

Great ! I will do a new pass. Thanks !

@jbonofre thank you for merging this patch.
I will follow up with a second part.


chore: 🐳 add commitizen

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: Format msgpack serialization in bberg

Description
When msgpack was added it was missing the formatting pre-commit hook. Thus, any work interacting with msgpack was also not formatted. I also added a new .clang-format file into the msgpack-c folder. Msgpack is a third party package which we bundled into barretenberg so we want to exclude it from our clang format rules, however, any code in barretenberg that uses msgpack should still be formatted.
Checklist:

[X] I have reviewed my diff in github, line by line.
[X] Every change is related to the PR description.
[X] I have linked this pull request to the issue(s) that it resolves.
[] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[X] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[X] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
X ] The branch has been rebased against the head of its merge target.
[X] I'm happy for the PR to be merged at the reviewer's next convenience.
[] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[ ] If existing code has been modified, such documentation has been added or updated.

Thanks for this
On Mon, May 22, 2023, 1:56 PM Maxim Vezenov @.***>
wrote:

Merged #467 https://github.com/AztecProtocol/barretenberg/pull/467 into
master.
—
Reply to this email directly, view it on GitHub
https://github.com/AztecProtocol/barretenberg/pull/467#event-9305589808,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIBGJTK4TS2Z7KKHJRSZLXHOSDHANCNFSM6AAAAAAYKXBWQA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


Onvif Cameras not loading in BETA - 093.b0

Home Assistant release with the issue:
093.b0
Last working Home Assistant release (if known):
092.2
Operating environment (Hass.io/Docker/Windows/etc.):
docker
Component/platform:
https://www.home-assistant.io/components/onvif/
Description of problem:
Onvif cameras not loading, error message in logs
Traceback (if applicable):
2019-05-09 08:33:47 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform onvif
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/src/app/homeassistant/components/nvif/camera.py", line 99, in async_setup_platform
    hass_camera = ONVIFHassCamera(hass, config)
  File "/usr/src/app/homeassistant/components/onvif/camera.py", line 140, in __init__
    .format(os.path.dirname(onvif.__file__)))
  File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 216, in __init__
    self.update_xaddrs()
  File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 223, in update_xaddrs
    self.devicemgmt  = self.create_devicemgmt_service()
  File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 333, in create_devicemgmt_service
    return self.create_onvif_service('devicemgmt', from_template)
  File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 312, in create_onvif_service
    xaddr, wsdl_file, binding_name = self.get_definition(name, portType)
  File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 292, in get_definition
    raise ONVIFError('No such file: %s' % wsdlpath)
onvif.exceptions.ONVIFError: Unknown error: No such file: /usr/local/lib/python3.7/site-packages/onvif/wsdl/devicemgmt.wsdl

Additional information:
Only change in release notes for onvif are related to this PR. https://github.com/home-assistant/home-assistant/pull/22972

Hello,
I got the same issue on my side.
Intel NUC6, Ubuntu 16.04 Desktop, docker, HassIo.
On my side it didn't work before either but there was no error message in the logs.
Thank you.

I originally wrote the ONVIF support, I had this when i tried to use zeep as it wouldn't work with hassio, so i gave up on using it and used an alternative which was used. I suspect hassio needs something adding to use zeep.

With the latest 0.93.b3 the ONVIF component is working.
Thank you.

on 0.93.0 and 0.93.1 component don't work for me.

My original error was fixed in beta.


chat bot does not run

My GitHub chat does not work, when I install the app, they ask me to log in . i log in and the app, The message tab disappear. I pay for the enterprise and the one use that is me. and it is not working.
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

Hi @gag0000, I need a little more assistance in understanding what you're seeing. So you're in Codespaces, are you trying to log in to Copilot? Do you have multiple GitHub accounts at play here?

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!


Update endpoint-dlp-learn-about.md

@chrfox

@Tewchen
capture your work here and save it off .  Recreate this next week


close remote input stream incase of exception in CachedRRC

Missed to fix this as well in the previous change.


Add shield for Inner Loop, Rochester, NY

The Inner Loop of Rochester, New York has an idiosyncratic shield: a Bus Carrell-style white trapezoid with rounded corners, with the black text "INNER LOOP" (example 1, example 2).
For the shield, I chose to omit the "INNER" and use just the text "LOOP", as there is no other loop route with similar signage in Rochester (the Outer Loop is instead signed as a sequence of Interstate and State routes). I considered "IL" as well, but I would expect that to be less intuitive.

I think the orange color is more proper; while it's sometimes in white I see that as akin to the Pennsylvania Turnpike signs sometimes being in white simply to contrast with a green background (when on guide signs vs standalone). It's also careening towards being a historical object so I expect the signage in its current state is pretty much "what you see is what you get".

I think the orange color is more proper; while it's sometimes in white I see that as akin to the Pennsylvania Turnpike signs sometimes being in white simply to contrast with a green background (when on guide signs vs standalone).

While it may have been historically signed in orange, I couldn't find any extant examples of this color scheme on street-level imagery. Even the standalone signs are black-and-white, despite the lack of a green background.

Wondering if it would be a little nicer to vertically center the LOOP text, perhaps with a shallower angle on the sides?

Street View at the (checks notes) Southern terminus, East Main Street.
Sep 2014: Orange https://maps.app.goo.gl/rsUnk4REQr6Mci9b8
Nov 2015: White https://maps.app.goo.gl/V8BgvAg7VWvMLrrZ8
White shield SGTM.

Just for kicks, I tried evening out the top and bottom padding for trapezoidDownShield to 3px each instead of 2px/4px:

Padding values adjusted to vertically center the text.


Avoid memory error

I found memory error with Python3.7.
tests/cupy_tests/linalg_tests/test_einsum.py::TestEinSumError::test_invalid_diagonal1 Traceback (most recent call last):
  File "cupy/cuda/memory.pyx", line 521, in cupy.cuda.memory.PooledMemory.free
    pool = pool()
TypeError: 'NoneType' object is not callable
Exception ignored in: 'cupy.cuda.memory.PooledMemory.__dealloc__'
Traceback (most recent call last):
  File "cupy/cuda/memory.pyx", line 521, in cupy.cuda.memory.PooledMemory.free
    pool = pool()
TypeError: 'NoneType' object is not callable

This PR fixes it.

jenkins, test this please.

Jenkins CI test (for commit 417c81b684fddf6d6fec2deb56c82291c9a4e6ee) succeeded without errors!

LGTM!

I merged this fix as this works as a workaround, but we should find the root cause to avoid memory leak. I raised another issue #1461. (It seems like a Cython issue?)

Jenkins CI test (for commit 417c81b684fddf6d6fec2deb56c82291c9a4e6ee) succeeded without errors!


build(scripts): maestro build scripts

This PR resolves PHIRE-774
Description
Creates ios and android build scripts that generate the needed files for maestro copilot trial.
Added also comments on the steps to remember what happens and why.

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

maestro copilot build scripts - gkartalis

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (maestro copilot build scripts - gkartalis)

  Generated by :no_entry_sign: dangerJS against 55cb5de4304c99a060d19f2fd41a3ae36aa57197


build issue: create_table_with (emscripten)

Hi, I'm getting the following error while building on emscripten:
In file included from D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/sol.hpp:58:
In file included from D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state.hpp:27:
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:855:11: error: call to member function 'create_table_with' is ambiguous
  855 |                         return create_table_with(lua_state(), std::forward<Args>(args)...);
      |                                ^~~~~~~~~~~~~~~~~
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:77:14: note: in instantiation of function template specialization 'sol::state_view::create_table_with<const std::string &, void *&>' requested here
   77 |                                 loaded = create_table_with(key, sr);
      |                                          ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:96:5: note: in instantiation of function template specialization 'sol::state_view::ensure_package<void *>' requested here
   96 |                                 ensure_package(key, static_cast<void*>(L));
      |                                 ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:219:11: note: in instantiation of function template specialization 'sol::state_view::require_core<(lambda at D:\a\Light.vn-core\Light.vn-core\_deps\sol2\9d60b8d5f5d9991dfff0de5dea2635b2925ea792\include\sol\state_view.hpp:218:18) &>' requested here
  219 |                         return require_core(key, action, create_global);
      |                                ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:854:9: note: candidate function [with Args = <lua_State *, const std::string &, void *&>]
  854 |                 table create_table_with(Args&&... args) {
      |                       ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:868:23: note: candidate function [with Args = <const std::string &, void *&>]
  868 |                 static inline table create_table_with(lua_State* L, Args&&... args) {
      |                                     ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:855:11: error: call to member function 'create_table_with' is ambiguous
  855 |                         return create_table_with(lua_state(), std::forward<Args>(args)...);
      |                                ^~~~~~~~~~~~~~~~~
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:77:14: note: in instantiation of function template specialization 'sol::state_view::create_table_with<const std::string &, sol::stack_reference &>' requested here
   77 |                                 loaded = create_table_with(key, sr);
      |                                          ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:102:4: note: in instantiation of function template specialization 'sol::state_view::ensure_package<sol::stack_reference &>' requested here
  102 |                         ensure_package(key, sr);
      |                         ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:219:11: note: in instantiation of function template specialization 'sol::state_view::require_core<(lambda at D:\a\Light.vn-core\Light.vn-core\_deps\sol2\9d60b8d5f5d9991dfff0de5dea2635b2925ea792\include\sol\state_view.hpp:218:18) &>' requested here
  219 |                         return require_core(key, action, create_global);
      |                                ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:854:9: note: candidate function [with Args = <lua_State *, const std::string &, sol::stack_reference &>]
  854 |                 table create_table_with(Args&&... args) {
      |                       ^
D:/a/Light.vn-core/Light.vn-core/_deps/sol2/9d60b8d5f5d9991dfff0de5dea2635b2925ea792/include\sol/state_view.hpp:868:23: note: candidate function [with Args = <const std::string &, sol::stack_reference &>]
  868 |                 static inline table create_table_with(lua_State* L, Args&&... args) {

      |                                     ^

2 errors generated.

No minimal repro?
Can you reproduce this issue on other platforms?

No minimal repro?

Nope, my code doesn't even use create_table_with.
Seems like a similar issue to https://github.com/ThePhD/sol2/issues/1611

Can you reproduce this issue on other platforms?

Nope, just emscripten. With code that worked prior - now failing to build after perhaps an emscripten update.

Without a minimal repro I doubt anyone could help you then.
You need to isolate your issue so we can assist you further.

Without a minimal repro

As stated above, the function is not used in my code hence a minimal repo doesn't seem feasible.
As also stated above, and the linked closed PR, this is likely due to the emscripten compiler doing more checks.

Considering 1 and 2, I believe that a minimal reproducible example would be created by just adding a github action to this repo that attempts to compile the sol code with emscripten.

I am afraid to tell you that your issue won't likely be solved without a repro.
I even was able to compile sol2 from develop branch, with lua and box2d from vcpkg to webassembly via emscripten with complete ease.
Here my sample example which I compiled:
#include <iostream>
#include <sol/sol.hpp>

int main() {
  sol::state lua;
  int x = 0;
  lua.set_function("beep", [&x] { ++x; });
  lua.script("beep()");
  std::cout << "The value was: " << x << std::endl;
}

So again, I am on Windows11, develop branch of sol2, with no problems compiling with emscpriten.


Fix message disabling tests

Description
Changes
Known Issues
Notes
Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.
[ ] I have updated the documentation to reflect my changes.
[ ] My code changes have been verified by automated tests and pass all relevant test scenarios.

/trunk merge


[Bug]: Improve the app menu

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The app menu has unnecessary help items. We'd like to funnel all help through intercom.
Steps To Reproduce

Click the app menu from the app name in the editor
Click help and see 4 option.
It should only show Chat with us, Report a Bug, Documentation

Public Sample App
No response
Environment
Production
Severity
Low (Inconsistent UI/UX)
Issue video log
No response
Version
Cloud

Fixed with #31986


Temporary account lockout for repeated auth failure

Overview
Enhance couchdb to efficiently reject requests for a given user if repeated requests have failed for authentication reasons, from the same IP address. This helps slow brute-force password attacks and is especially helpful if each authentication attempt is very expensive (pbkdf2 with a high iteration count, typically).
Testing recommendations
will be covered by automated tests
Related Issues or Pull Requests
Checklist

[x] Code is written and works correctly
[x] Changes are covered by tests
[x] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[x] Documentation changes were made in the src/docs folder
[ ] Documentation changes were backported (separated PR) to affected branches

Would couch_auth_lock[out].erl be a clearer name for the module instead of couch_lockout.erl?

lockout is its own thing, e.g. https://en.wikipedia.org/wiki/Lockout_(industry)

What is the config option to disable it? The 3.4 changelog only says:

#5032: Temporarily block access by client IP for repeated authentication failures. Can be disabled in config.

And I can't spot it in https://docs.couchdb.org/en/stable/config/http.html (or any other docs pages so far).

@DarrenCook see https://docs.couchdb.org/en/stable/config/auth.html#chttpd_auth_lockout

Thanks. The changelog made it sound like it is on by default, but the docs say off is the default, which makes more sense.


Use converter from Literal to actual values when dumping model to json

When dumping yaml we use:
contents = self.model_to_dict()

        yaml.add_multi_representer(
            LiteralValue,
            lambda dumper, data: dumper.represent_data(data._value),
            yaml.SafeDumper
        )

        fp = open(filename, 'w')
        yaml.dump(contents, fp, Dumper=yaml.SafeDumper)

We should have a similar method when dumping json. We could probably create our own json.JSONEncoder and use it in json.dump(..., cls=OurJsonEncoder) (see json.JSONEncoder
Awaiting #13 to merge

Is there a need to support JSON in particular when dumping models? Do we expect to integrate with 3rd party tools? If not, why not make yaml the only supported format? Even if we encounter a json file somewhere whose format is compatible with what we support, we can still load it as yaml as yaml is a superset of json.

There are some other people using the mal-toolbox with json models right now so it's best to still have it there just in case. I do think we may softly push towards yaml, because I really prefer the cleaner look, but I do not see any meaningful problems with supporting both. The explicit conversions I had to reintroduce to make it work with both aren't terrible anyway.


bug: "--version" flag cannot be used

When I followed the development guide development.md Line58 ./bin/envd --version.
It gives a problem that
Incorrect Usage: flag provided but not defined: -version
I think it may be a typo. If this means a version flag, then it shoule be ./bin/envd version

/assign

I think there is an error in our doc. You should use envd version

I can provide a pr to fix it.
/assign @dqhl76

I can provide a pr to fix it. /assign @dqhl76

That would be very nice of you! Thx!


Deprecate @virtual from package:meta

None of the backends should be giving any meaning this this annotation anymore - we should deprecated it so that is stops spreading via copy/paste.

Fixed in https://github.com/dart-lang/sdk/commit/e58e3fbb55d2c2276b80ecaf6ee7a1923d295f11


[Bug]: Can't load any gemma 2 model

Your current environment
I'm using vllm==0.5.3.post1
exposed the flashinfer environment variable
export VLLM_ATTENTION_BACKEND=FLASHINFER
and tried to load the model using this script
from vllm import LLM
import flashinfer
import os

os.environ['VLLM_ATTENTION_BACKEND'] = 'FLASHINFER'
model = LLM(model="google/gemma-2-9b-it",
                         tensor_parallel_size=2,
                         trust_remote_code=True, gpu_memory_utilization=0.9)

🐛 Describe the bug
I am trying to load gemma 2 model and keep running into this error
RuntimeError: RuntimeError: Out of workspace memory in AlignedAlloactor
What happens is that the GPUs keep filling up until I get a Cuda OOM error

Which GPU deployment did you use?


missing files -> will break your t3 installation

the vendor directory of dompdf is incomplete.
at least dompdf_config.inc.php and include folder is missing.
neither ter nor githib version has the mssing files. needed to replace dompdf files with dompdf from github to make my backend working again.

Same problem.
To get your TYPO3 Backend working again you can remove the extension folder and clear the caches over the install tool.
The issue remains that these files are missing in the repo/packages.

I've just pushed 0.0.6 to TER. Can you please try that version now?
Report back if you found any issue.

Thanks for responding.
ext/typdom3/vendor/dompdf/dompdf/dompdf_config.inc.php still missing.

It's because I'm installing it through composer. I cannot understand why that file is still required.

Fixed with v0.0.7 :) Just pushed to TER.

No closed. Sorry :-)
Class 'DOMPDF' not found in ext/typdom3/Classes/TypDom3.php on line 42

Done. Pushed 0.0.8 to the TER :D
You were right, I forgot to port the API calls to the new DomPDF 0.7 version. Now everything should be ok :) Thanks for the quick feedback!

Thanks. Works now.


QUESTION: How to achieve nested routes, with there own data

Is there an easy way to achieve nested routes, with there corresponding data.
Id like to have a bucket route, with a particular bucket as data. the bucket template would get the bucketData, and list its items as link. The item would appear next to the bucket, with the selected items as data to the temp ate, showing the item.

Hurrah for Ember-style route nesting!
While the iron router comes with a gazillion features, I prefer to use routing as an organisational tool. Lacking nesting support, this is precisely what the iron router does not facilitate.
In theory, a feature set as rich as the iron router's combined with nesting should be a 1 + 1 = 3 type of valuable.

+1

+1


Silent-Mode possible for scriptings?

we are using HealthChecker for several scriptings and it would be preferred, if there is an additional "silent" parameter for it.
e.g. running "HealthChecker.ps1 -ScriptUpdateOnly" results in
...
No update of the script performed.
Do you like the script? Visit https://aka.ms/HC-Feedback to rate it and to provide feedback.
...
which is not preferred by us due to several scriptings running after it - so the output we are generating has too much infos we don't like to see.
Is there a possibility to implement this in future versions?

@airathere are you talking about just the update functionality or the entire output possibility that Health Checker does provide?

it would be nice to have it for all parameters, so "-ScriptUpdateOnly" was only an example. We are also using the others, like checking for vuln reports ect.

PowerShell already supports redirecting all output to $null. I don't think we need to implement this in the script. Syntax:
.\HealthChecker.ps1 *>$null

Example:

Redirecting output streams is documented here:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_redirection

We run, as mentioned at the beginning, the HealthChecker in scripts.
So here for example, i run test.ps1:
`Add-PSSnapin Microsoft.Exchange*
$mylogtemp = "C:\temp"
$myscriptpath = "C:\scripts"
cd $myscriptpath
.\HealthChecker.ps1 -ScriptUpdateOnly -OutputFilePath $mylogtemp *>$null`
Result:
we get an unwanted output:
`PS C:> C:\Users\Administrator.INTRA\Desktop\test.ps1
No update of the script performed.
Do you like the script? Visit https://aka.ms/HC-Feedback to rate it and to provide feedback.
PS C:\Scripts>`

You are right ;-)
After your hint we recognized, that it has to do with the PS Version we are laying on.
e.g. on older machines (wss 2012r2 or 2016) we have this problem, with the new ones (wss 2019, 2022) not.
so: solved!


Making login page more attractive by adding CSS gradient effects

could you please assign me thus issue under hactoberfest2022.

Can you pls assign me this issue?

Hii! can you please assign me this task. I want to fulfill this issue.please!

@Ankita-278 please go ahead!
Others please try finding another issues. Have a good day!


pip2 install av won't work

Overview
{{When running the command  " pip2 install av " i get an error}}
Expected behavior
{{ A successful instalation of av for python 2}}
Actual behavior
{{error: "Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-g2EbQt/av/" }}
Build report:
{{$ ~/catkin_ws$ pip2 install av
Collecting av
  Using cached https://files.pythonhosted.org/packages/40/e6/da37b548e9e1312fb11ffd0f31f8679e1b96d3859790a77e93a113394d34/av-8.0.3.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-g2EbQt/av/setup.py", line 9, in <module>
        from shlex import quote
    ImportError: cannot import name quote

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-g2EbQt/av/
}}

Investigation
{{tried to install it in python3 and it worked, but because of the use of  ros the python version has to be 2}}
Reproduction
{{pip2 install av}}
Versions

OS: {{ Ubuntu 18.04 }}
PyAV runtime:

{{ Complete output of `python -m av --version` if you can run it. }}

PyAV build:

{{ }}

FFmpeg:

{{ }}

Research
I have done the following:

[X] Checked the PyAV documentation
[X] Searched on Google
[X] Searched on Stack Overflow
[X] Looked through old GitHub issues
[ ] Asked on PyAV Gitter
[ ] ... and waited 72 hours for a response.

Additional context
{{ }}

Python 2 has reached end of life and is no longer supported by PyAV.


[flake8-django] DJ001 is not raised for models not directly inherited from Model

DJ001 is not raised for models which doesn't directly inherits from django.db.models.Model. The source of bug is in https://github.com/charliermarsh/ruff/blob/f7515739acc0a7b5c580bf05aac6055181739c65/crates/ruff/src/rules/flake8_django/rules/helpers.rs#L6 It should lookup whole mro for the Model class.
Affected version: 0.0.246
Snippet reproducing bug:
from django.db import models
from django.utils.translation import gettext_lazy as _
from utils.models import BaseModel

class ExampleModel(BaseModel):
    name = models.CharField(max_length=255, verbose_name=_('Name'), null=True)
    description = models.TextField(verbose_name=_('Description'))

    def __str__(self) -> str:
        return self.name

I think in this case it would also be fine to skip the base model check. If a class has a django.models.CharField, that's good enough IMO.


NuGet packages are old and alpha, is the project dead?

Hi,
I was skimming through some Google Cloud documentation when I stumbled over the NuGet package Google.Cloud.AspNetCore.DataProtection.Kms, this package provides handy extension methods for ASP.NET Core, but the package was last released in 2020, and is alpha.
Can you please clarify the plans/future for this package before I depend on the package? Thanks.

Please see the discussion in #24 for more information.


tsc with --target ESNext fails but the same configuration succeeds on the playground.

Bug Report
tsc causes errors for  --target ESNext for some order of initialized variables and variables initialized in the constructor.
Why does the code produce errors for ESNext and no error for any other target?
🔎 Search Terms

ESNext

🕗 Version & Regression Information
The command line fails on the code where the playground succeeds.
⏯ Playground Link
You have to set the --target to ESNext for this script Playground link with relevant code
💻 Code
Compiling this code with
./node_modules/.bin/tsc --target ESNext x.ts
function writeVal(a: number, b: any): number {
    console.log(‘writeVal’, a, b);
    return a;
}
class TestClass {
    a: number;
    public b = writeVal(2, this.z);
    constructor(public z: number) {
        this.a = writeVal(1, this.z);
    }
    public c = writeVal(3, this.z);
}

I get the following error:
x.ts:7:33 - error TS2729: Property ‘z’ is used before its initialization.

7     public b = writeVal(2, this.z);
                                  ~

  x.ts:8:17
    8     constructor(public z: number) {
                      ~~~~~~~~~~~~~~~~
    ‘z’ is declared here.

x.ts:11:33 - error TS2729: Property ‘z’ is used before its initialization.

11     public c = writeVal(3, this.z);
                                   ~

  x.ts:8:17
    8     constructor(public z: number) {
                      ~~~~~~~~~~~~~~~~
    ‘z’ is declared here.

Found 2 errors.

🙁 Actual behavior
Running the code above in the playground there is no error, but tsc throws errors and fails to compile.
🙂 Expected behavior
Playground and the compiler should produce the same errors.

This is the las version where the code compiles successfully:
npm i<EMAIL_ADDRESS>This is the first version when the code breaks:
npm i<EMAIL_ADDRESS>

It is broken up to version npm i<EMAIL_ADDRESS>

I get the same error in the playground: https://www.typescriptlang.org/play?useDefineForClassFields=true&target=99&ts=4.4.0-beta#code/GYVwdgxgLglg9mABAdwE4ygUwGoEMA2AFLgFyJggC2ARpqgDSLVm5gCeAlGRTXYgN4AoRCMQQEAZzj5MAOnxwA5oQDkaDDgIrGuRtQ4BuYaNSYoIVElxGAvoIj5cEiYgAqmCVADCj5wOMipORUtKhGoogADiDU+DAQTIgAvCjoWHhEAEyMUAAWMBKyAF6GEQFiklCoINBwqITRsfGIRdwhdBz+ERF5BbK4yakaGYQAjDn5hSXhonYRjXEJCSnq6QSEAMwTfdOCNkA
Note that useDefineForClassFields is by default true when targeting ESNext, but it needs to separately enabled in the Playground.


[ast,pwrmgr] Strange glitch in usb clock

This is a strange issue, and may not be a problem at all, but it is weird enough we should consider it.
Imagine a low power transition when the usb clock was disabled in active mode, but is configured on when in low power. Yes, this is bizarre. On top of that, imagine we set main_pd_n to 0. So main power is off, yet we have the clocks configured on and main power off during low power.
Well, in this strange situation, the AST will actually turn the clocks off as it does to low power, regardless the pwrmgr's intentions. But the clocks go off after power clamping. Not sure it this mixes well with retention and all the low power circuitry.
To make things even more goofy, the USB clock briefly turns on before going off... remember it was configured to to turn on when the low power transition happens.
Here are some waves:

yeah this is indeed kind of odd. i wonder if it would be better if we just removed the lp / active indication for usb, and just leave one of them. Then we leave the control unambiguously in software's hand all the time.
Ie, if software wishes to have usb clock active for some reason, they will simply just leave it on all the time.

Hmm, my concern is that we are saying any of the clocks should remain active when main_pd_n is low, yet we end up turning the clock off anyway. In fact, I think the control reg spec may say when main_pd_n is low all clocks will be turned off regardless of their config bit.
I looked more closely at the waves in full chip: when pwrmgr sets main_pd_n low the AST treats it as a main power glitch, and sends a rst_main_n to pwrmgr, and ast also turns all clocks off at the same time. But this time is much later than the slow fsm's SlowPwrStateClocksOff, so it is "suspicious". If main_pd_n is active low there is no reason for the clocks to continue to run, so just turning them all off seems to be the cleanest way to deal.

o fair point.

I think this misses the case of non-deep sleep low power. If main_pd_n remains high then each of the clk_en bits in control just control the clock, and we can independently choose which clocks remain active. It seems what you propose simply removes this clock gating functionality, even if only for usb. Why?

And I also think the weird extra activity of the usb clock before power is shut off would go away if we turned clocks off in the correct slow fsm state, which my proposed fix should end up doing.

I think this misses the case of non-deep sleep low power. If main_pd_n remains high then each of the clk_en bits in control just control the clock, and we can independently choose which clocks remain active. It seems what you propose simply removes this clock gating functionality, even if only for usb. Why?

no actually what i intended is what you're describing. In "low power", ie real deep sleep, just kill the enables, because as you say, there's no point in keeping them up.  When we are in non-low-power deep sleep (ie, normal sleep), we do not force USB to a particular value, instead just allow it to remain under software control.  So in this world, we only need 1 bit, whose value is ignored when we are in deep sleep.

If I understand correctly, the usb_clk_en bit would behave differently from the main and io_clk_en: the latter are ignored in active power, but you propose usb_clk_en would not? We would need to explicitly update the usb_clk_en prior to entering shallow low power for active-enable switching to shallow_sleep-disable, and conversely we would need to update it upon wakeup to have shallow_deep-disable to active-enable.
I think the current scheme with two bits for usb is simpler. But I definitely agree whenever we enter deep sleep (main_pd_n == 0) we should turn all three clocks off regardless of their control enables.

Yes what you're saying is right, that's what I had in mind.
Mostly I think this is simpler because I wanted to make it "deep sleep" vs all other cases.

o wait i see what you mean.
yeah let's go with what you're suggesting then. Low power usb control for lighter sleep, active control for active region, and then when in deep sleep a more defined behavior.


Weird space at the top

Thanks @kapoorsahil ! Can you provide more info?

library version
iOS version
devices/simulators
repro steps

I am using latest version, downloaded via Cocoapods. It's happening on both iOS 8 and iOS 9.On both device and simulator. I copy pasted your code from github, except for URL.
_____________________________

From: Jesse Squires<EMAIL_ADDRESS>Sent: Friday, September 25, 2015 9:31 AM
Subject: Re: [JSQWebViewController] Weird space at the top (#4)
To: jessesquires/JSQWebViewController<EMAIL_ADDRESS>Cc: Sahil Kapoor<EMAIL_ADDRESS>Thanks @kapoorsahil ! Can you provide more info?       library version    iOS version    devices/simulators    repro steps
—
Reply to this email directly or view it on GitHub.

Oh damn. I think I know the issue.
Try making your navigation bar translucent and see it this goes away. If it does, the issue is with topLayoutGuide.

Yeah, it fixes the problem.


Using with woocommerce

Please see this stackoverflow post.

hi, I have some problem.
https://woocommerce.github.io/woocommerce-rest-api-docs/?shell#list-all-products
in woocommerce, there are parameter filter. that executed like this for example:
filter[orderby]=meta_value_num
how can I input that parameter to oauth_data?
var oauth_data = {
order: 'asc',
oauth_consumer_key: 'ck_key',
oauth_signature_method: 'HMAC-SHA1',
oauth_timestamp: timestamp,
oauth_nonce: nonce,
oauth_version : '1.0'
};

@DeLonge This is not a valid syntax:
{
  filter[orderby]: 'meta_value_num',
}

I cannot help you with specific examples for woocommerce.
You need to consider that the parameter object needs to be serialisable to a query string (?foo=bar&baz=qux), so you will need to understand what kind of encoding you need to get woocommerce to handle complex object encoding.


Small TF bug fixes

Related Issue or Background Info
#1360
Quick bug fixes to ensure terraform apply runs smoothly in ops/*/persistent
Changes Proposed

Existing Private Endpoint resources were created with an Environment tag which wasn't reflected in the TF resource added in #2053
An output in ops/*/persistent/_output.tf needs to be marked sensitive but was not

Checklist for Author and Reviewer
Cloud

[n/a] DevOps team has been notified if PR requires ops support
[x] If there are changes that cannot be tested locally, this has been deployed to our Azure test environment for verification

LGTM!
Is there any remediation necessary from the fact that the sensitive tag was previously missing on those outputs?

Nope! We're not running this in the pipeline, and if we're running it locally we were using -target, and so this wasn't an issue we were running into until now. This ensures we can run a blanket terraform apply without -target when it comes time to do so.


Remove invalid flow when WireGuard is enabled

After merging #5885, the OVS tunnel port is no longer created when enabling WireGuard, as it is not being used. However, we were still trying to install flows referencing the tunnel port. Even though the port was non-existent, flow creation would succeed, but the condition matching on the tunnel port was being dropped silently. This would lead to invalid datapath behavior. We update the code to prevent installing these invalid flows when WireGuard is enabled.
Fixes #5905

/test-all
/test-ipv6-all

/test-all
/test-ipv6-all

 TestTraceflow/testTraceflowIntraNode/traceflowGroupTest/intraNodeTraceflowIPv6 failed because the test itself is wrong, introduced by https://github.com/antrea-io/antrea/pull/5667. It seems we haven't ran ipv6 test since then.
=== NAME  TestTraceflow/testTraceflowIntraNode/traceflowGroupTest/intraNodeTraceflowIPv6
    traceflow_test.go:2535: Observations should be [{SpoofGuard  Forwarded      0    } {NetworkPolicy EgressRule Forwarded   K8sNetworkPolicy:testtraceflow-7kmgj1vz/test-networkpolicy-allow-all-egress   0    } {NetworkPolicy IngressDefaultRule Dropped   K8sNetworkPolicy:testtraceflow-7kmgj1vz/test-networkpolicy-allow-all-egress   0    }], but got [{SpoofGuard  Forwarded      0    } {NetworkPolicy EgressRule Forwarded   K8sNetworkPolicy:testtraceflow-7kmgj1vz/test-networkpolicy-allow-all-egress   0    } {NetworkPolicy IngressDefaultRule Dropped      0    }]

/test-e2e

/test-conformance
/test-networkpolicy

/skip-conformance
/skip-networkpolicy