[Docs] no-useless-path-segments: add docs for option commonjs

fixes #1459.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.3%) to 96.174% when pulling 22df045b60700f9c02b16c7b0510966b056b9405 on golopot:docs-useless-path into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.


loading page after clicking on element

I have a page loaded using puppeteer and I have list of elements rendered in this page. Each of the elements can be clicked and on click it will expend the element and add additional element with more data. Kind of like en accordion. How can I make it worked? I tried couple of things like:
    await page.evaluate(() => {
      let elements = Array.from(document.querySelectorAll(".feeditem"));
      elements.map(async element => await element.click());
      return;
    });

    let site = await page.evaluate(
      () => document.querySelector("body").innerHTML
    );

or
    const example = await page.$$("feeditem");
    const newExm = await example.map(async i => await i.click());

    let site = await page.evaluate(
      () => document.querySelector("body").innerHTML
    );

and also
  await page.evaluate(() => {
    let elements = document.querySelectorAll(".feeditem");
    elements.forEach(async i => {
      const el = i.parentElement;
      await el.click();
    });
  });

  const elementsExtcArr = await page.evaluate(() => {
    let elements = Array.from(document.querySelectorAll(".accordion_opened"));
    const elementsExtc = elements.map(i => i.innerHTML);

    return elementsExtc;
  });

but none of those not work. I still getting the page as it was before the clicks events. Any idea?

@obiwankenoobi there's no silver bullet - this all depends on the "accordion" implementation details. If you give us exact URL, than we'll probably be able to help.


Is this still even working ????

I'm struggling with this library a lot,
First - Load data async
inside the ViewModel Constructor my HTTPGet cannot be done, I have to end up moving that logic to the code behind inside the OnAppearing()
Second - the loadmore() event not even invoke, I break point that but that VM just go pass it

Same here , have you find any work around ?

Same here , have you find any work around ?

Same here , have you find any work around ?

I ditch this and move on the collectionview have a look at ItemsTresholdReached keywords on Google you will find a better way

Same here , have you find any work around ?

I ditch this and move on the collectionview have a look at ItemsTresholdReached keywords on Google you will find a better way


Dragging the bubble view its movement is not as smooth as facebook chat heads

While dragging the bubble view its movement is not as smooth as facebook chat heads or BuMp player. Is there any way to make the movement much more natural??

We'll put this to the list of enhancements for future releases.
You can try to play with TouchManger and it's VelocityAnimator. If you will make movement smoother, you can send us a pull request into develop branch.

Widget's movement in v.1.0.0 became much smoother. Give it a try.


New extractor ready for pull request, 2 questions

Checklist

[ x] I'm asking a question
[ x] I've looked through the README and FAQ for similar questions
[ x] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE
New extractor from pornhubpremium is ready:

shall I rename yourextractor.py to pornhubpremium.py ?
test require username/password, I'd prefer not to let them in the file, or I can for a small period so you can run the test, whot sould I do ?

You must place it in pornhub.py.
You must provide account credentials to core developer.


Version v3 not work in IE11

Version: 3.0.0-alpha.2
When I open the demo site of metisMenu occurs the error. The menu is not collapse your levels.
The console of IE11 show this message: "The object does not support the property or method 'entries'"

Regards,
Lucaino

@llutti
Hi Lucaino,
Will you try now?

@onokumus
Hi,
I tried now and all worked very well.
Congratulations for your great work and thanks for your help.
I will download the new v3 beta version to use in my project.
Best Regards,
Luciano

@llutti
Please close this issue.


Sentry 2.0 [base]

Base version for Sentry-PHP 2.0.

Namespace Raven instead of prefix "Raven_"
Removes Raven_Compat
Renew dependencies in composer.json and .travis.yml

#192, #197 & #424

fyi https://wordpress.org/about/stats/
I'm ok with us dropping support, but we'd likely want to document "If you're using 5.2, the last version of sentry/sentry that supports it is X"

If I'm not mistaken, composer supports downloading these versions of packets what supports needs versions of other packets. So if someone will write
composer require getsentry/sentry-php
It will install old version.
Please don't merge this pull request at this state (798805b). At first I must add
Raven_Client extends \Raven\Client { }
otherwise we will crush all packets depends on getsentry/sentry-php.

Please, there is no point in supporting a version of PHP as old as PHP 5.2 that reached end of life more than 6 years ago. Symfony supports PHP >=5.3.9 in their 2.x branches and >=5.5.9 for their 3.x branches. Also, I see a lot of PRs about raising the requirements of PHP, but this does not mean that we should move all classes to namespaces because it's a BC. I did not verify if it works, but looking at how the guys of PHPUnit updated their PHP requiremens we should release a new 1.x version that drops PHP 5.2.x support by updating the Composer constraint to at least >=5.6 and remove the custom autoloader Raven_Autoloader. Then, all changes related to PSR-4 support, namespaces, etc should be done in a 2.0 branch because they all break BC. On my fork a week ago I pushed the first commit that is similar to the one of this PR, which makes the directory structure compatible with PSR-4 and introduces namespaces. I have a lot of ideas for new 2.x version of this library, but this discussion should be done in a new issue.

At my own project I am even more radical https://github.com/nokitakaze/ascetcms/blob/v079/.travis.yml#L3

all changes related to PSR-4 support, namespaces, etc should be done in a 2.0 branch because they all break BC.

I don't think it's necessary. All people calls only Raven_Client.
At this moment I fix this joking branch. I thought it will be rejected and won't be discussed at all.

I just noted that even if this library claims to support PHP 5.2, Travis does not test it. So how can the maintainers be sure their versions work on a so old version?

I don't think it's necessary. All people calls only Raven_Client. Just give it next minor version

Minor versions can't break BC, this is how SEMVER works. It's not important if users just have to update a line of code, a BC is a BC and cannot be done imho. There is nothing wrong in making a 2.x release that adds everything we want and let 1.x as is.

Okay. Now there is file Legacy.php contains old classes.
And I deleted old "compatible" calls. But I didn't delete Compat.php so this version should works with any code

I think I didn't broke back compatibily. I am not sure.

When deprecating things I like the approach of Symfony that triggers deprecation notices by putting line of codes like these at the start of a file:
@trigger_error('The '.__NAMESPACE__.'\MyClass class is deprecated since version x.x and will be removed in x.x. Use the NewNameSpace\NewClass class instead.', E_USER_DEPRECATED);

Errors can then be catched by frameworks (e.g. Symfony shows deprecations in the profiler) and the users know they are using something that it's going to be removed. However, if you have a single file with all classes I don't know how we could do something like this. I think Symfony guys don't put that lines in the constructors because if someone extended the class then the parent constructor would not be called implicitly, but honestly I'm not sure about this. Please note that I take Symfony as example because it's the framework I use daily, there could be other ways to do the same thing.

I think I didn't broke back compatibily. I am not sure.

I think you broke it. Taking as example people not using Composer, previously they were probably including the Raven_Autoloader.php file and then instantiating the class inside it (see here for an example). But with your changes the Raven_Autoloader class should be defined inside a new file called Legacy.php, that is not included and so it will fail. I said should because I can't find the definition in that file anyway, so it's for sure a BC.

You're still breaking compatibility, because if someone did not use the autoloader but manually loaded the files they do not exists anymore. You should keep the old files with the old classes in it, and maybe have a new folder with the new classes. Also, in PSR-4 libraries usually the code is located inside a src directory.

I can add "require once legacy" into every file. But in this case I must delete E_USER_DEPRECATED

But in this case I must delete E_USER_DEPRECATED

Wouldn't moving the trigger_error from the Legacy.php file to each file fix the problem?

We can lose backward compatibility or we can suppress E_USER_DEPRECATED. But not both at the same time. You must pull deprecated classes to files for backward compatibility.
...
Or we can pull spl autoload into any files so it will autoload deprecated classes and trigger E_USER_DEPRECATED.

We can lose backward compatibility

This is a no-go, as I said before only major versions can break BC.

we can suppress E_USER_DEPRECATED. But not both at the same time. You must pull deprecated classes to files for backward compatibility

I do not understand this part, Which problems would arise by moving the trigger_error to each old file? If someone uses the new classes he has no problems because no errors are thrown, if he uses one of the old classes then it's correct to get notified of deprecation

I don't understand. You want to pull into old files something like this
trigger_error...
require_once 'new/Client.php';
/**
 * @deprecated
 */
class Raven_Client extends \Raven\Client
{
}

?

This is exact, but it would pollute the files with a lot of code just to maintain BC, so I'm not sure all this is worth the work for a 1.x release

The main maintainer should make his views

Just a side note ; upgrading a dependency's version in a minor is fine if it doesn't break the public api... http://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api
But +1 on dropping dead versions. Even php 5.3 is not on debian etc anymore, and it's not updated at all (not mentionning that php 5.5 has reached EOL).
If you want a better graph on what versions are used, you should use the one the maintainer of composer made : https://seld.be/notes/php-versions-stats-2016-2-edition as this is using composer and all (rather than wordpress who is detecting "what is using wordpress", which also counts the "dead" blogs).

As I said before my opinion is to drop all old version. Only PHP 5.6+
All old version can use 1.7.0 with #409 & #412. And all new versions of PHP will use 2.0 with dropped EOLed versions.

Just a side note ; upgrading a dependency's version in a minor is fine if it doesn't break the public api...

This is right, but renaming old classes or not being able to load them anymore is breaking the public API. This is why I continue to say that it would be easier to just release a 2.x version where we can make all adjustment or improvements without any concern about compatibility. A minor version should just be a drop-in replacement that eventually adds new features, but it should never change or remove things

As I said before my own opinion is to drop all old version. Only PHP 5.6/7.0+

I agree

This branch has conflicts that must be resolved

I will fix conflicts, after @dcramer says he want to merge this pull request. We could use this pull request as a base for #424 (Sentry PHP 2.0).
But I don't know how to test PSR-4 compatibility.

If this is going to be the base for 2.0, we don't need the @trigger_error, nor the autoloadear, nor the Legacy.php file

Of course

@nokitakaze Please just keep this PR updated with the latest master changes until it's merged, and if you can squash all commits, but please do not add any commit that does not belongs to PSR-4 switch (e.g. deleting legacy things like the Compat class). For that you should open a new PR

please do not add any commit does not belongs to PSR-4 switch

I want @dcramer merging this commit to new branch so anyone else could do another pull requests

Sure, but removing legacy things like the Rave_Compact class is not in the scope of this PR. The scope of this PR was to move to PSR-4 (you should rename the lib directory to src and the test directory to tests) and use Composer, not starting the work for 2.x

The scope of this PR was to move to PSR-4

No. This PR was just a joke. But after the maintainer approves the idea of version 2.0 (#424) I changed the description and the title of this pull request.

I could delete commits with deleting Raven_Compat, but why should I do it?

Because having too many things in a single PR makes review difficult. Removing legacy classes is a thing that should be done separately

Ok. I will remove some commits if @dcramer says so.

you should rename the lib directory to src

As I see on http://www.php-fig.org/psr/psr-4/ & https://getcomposer.org/doc/04-schema.md folder "lib" is fine too as long as we save link to it in autoloading section in composer.json

You're correct, but if you look at most of the other libraries they all tend to use src and tests as folders

It looks you missed to add namespaces to the tests classes and rename all them to PSR-4 format. You also renamed only the test directory, not to be rude but I found only one of nearly 20 starred repositories I looked at that used lib. Also, one more thing: we could add the following to composer.json
"autoload-dev": {
    "psr-4": {
        "Raven\\Tests\\": "tests/"
    }
}

you missed to add namespaces to the tests

I didn't miss it. I missed it on purpose. I don't think it's necessary to add namespaces to tests

It's not necessary, but as we're moving to PSR-4 we should move everything to that. Tests classes are source code, and they should be namespaced

It's not necessary, but as we're moving to PSR-4 we should move everything to that. Tests classes are source code, and they should be namespaced. Just look at https://getcomposer.org/doc/04-schema.md#autoload-dev to see that tests are namespaced and they use src in all examples

Renaming the main folder just because everyone do it isn't the best thing you can do. Yet again I'll do it if @dcramer says so. Same goes for namespaces in test classes

Renaming the main folder just because everyone do it isn't the best thing you can do.

If 90% of the people does it, I think we should too because it's a sort of "standard". Also lib seems more a directory containing third-parties code, not the source code of the library itself.

Let's start by merging this in. I'll change the branch to 2.0 for now, and we can consider moving to master once we're a bit more prepared with things.

fyi im giving you both commit bit -- the 2.0 and master branches are protected, but you can push to 2.0 as long as the PR is up, and passes status checks (i would aim to go through a brief review on things though)


Test coverage reporting

will wait on https://github.com/google/labs-prototypes/pull/284

Breadboard has graduated to a new dedicated repo! 🎉 🎓 We were able to transfer everything except for open PRs, so this one will need to be re-created at https://github.com/breadboard-ai/breadboard/pulls if it is still relevant. Thank you! Sorry for the disruption.


Fixed failing tests

One was a bug in Selenium we triggered; one didn't reflect new server behavior

Back to 100% passing for Sinatra version.


Calculate the intensity of a sound source

The current code uses an estimate of sound's intensity to estimate the distance. A way to calculate the intensity in dB should be found

Moved the issue to the Acoustics project since the Refactoring project mainly revolves around the bigger structural changes to the codebase :smile:


groups: notification for mention in private group after leaving

Describe the bug, optionally with screenshots
I left the Tlon group but still get notified when I am mentioned there.

To Reproduce
Steps to reproduce the behavior:

Leave a private group after interacting for a while
Someone mentions you
Notification appears with message content but no group name
Clicking on notification takes you to "just a second" loading screen, URL shows group that was left

Expected behavior
Leaving a group means no longer receiving notifications from that group.
Additional context:

Ship type: planet
Instance type: self-hosted on Linux
OS/browser: Brave on Linux

Tracking internally as LAND-435

I've seen this too.


How to get the 3d boxes of the culsted points?

Hi, Sorry for not understanding your question very well. We don't need 3d boxes. We directly get segments from 2d frames with SAM, and then project them to 3d space.


CDB-17: Introduce Guardrails for CollectionSizeWarnThreshold / FieldsPerUDT / ItemsPerCollection

closing in favor of https://github.com/datastax/cassandra/pull/13


Add color to GUI (pygame)

Using pygame, add colours to the GUI!
https://stackoverflow.com/questions/66264628/add-text-into-a-colored-input-text-box-pygame

i know only python basics, am i applicable to do that?

ok

I would like to work on this issue... Would you assign me .

Contributor

Sure.

Thank You .... assigning me this issue.
Now, I want to know what color to add for which segment like

The Input text color is fine, the 'Hi! What is you name?" 's color is not so good for reading

If you see chapters.py for every print or answer = input it jas
Fore.(COLOR) use that color, but if it looks bad then use any color of your
choice. If the system is setup, I can always change the colors.
On Fri, 17 Mar 2023, 12:55 am M.SAKSHAM, @.***> wrote:

Thank You .... assigning me this issue.
Now, I want to know what color to add for which segment like
https://user-images.githubusercontent.com/69385787/225731261-535583c9-0685-415b-b680-295d819c0b3d.png
The Input text color is fine, the 'Hi! What is you name?" 's color is not
so good for reading
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/Choose-Your-Own-Adventure-Game/issues/50#issuecomment-1472620195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTJK7WFABNCYTB2LZNTW4NSKLANCNFSM6AAAAAAV5HA5IU
.
You are receiving this because you authored the thread.Message ID:
<KendallDoesCoding/Choose-Your-Own-Adventure-Game/issues/50/1472620195@
github.com>

@KendallDoesCoding  Hey! I have changed the color of the text from black to white. Improves the visibility of the text. If it looks good, can I make a pull request?

@KendallDoesCoding Hey! I have changed the color of the text from black to white. Improves the visibility of the text. If it looks good, can I make a pull request?

Can you do this throughtout the project too?
Yes, please make a PR.

@KendallDoesCoding Hey! I have changed the color of the text from black to white. Improves the visibility of the text. If it looks good, can I make a pull request?

Can you do this throughtout the project too?
Yes, please make a PR.

Sure

@KendallDoesCoding I have made the PR, can you review it and let me know if you need any changes?


Use .sync variants of shfl/vote for CUDA 9+.

Non-sync variants have been deprecated and are now completely gone
in CUDA-10.1 when we compile for sm_7x.

Ping. Is there anybody out there?

Looking after it :)
On Wed, May 22, 2019 at 2:58 AM Artem Belevich<EMAIL_ADDRESS>wrote:

Ping. Is there anybody out there?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NVlabs/cub/pull/164?email_source=notifications&email_token=AALILQCNKUNBK4VDZI5MFODPWTVJPA5CNFSM4HNP6OK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6C6ZI#issuecomment-494677861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALILQAOCWRNTJC5QV7NT6TPWTVJPANCNFSM4HNP6OKQ
.

I'm not sure what the point of these edits is: CUB already uses the *sync versions exclusively when compiled with CUDA tookits >= 9x.  This is enabled by the CUB_USE_COOPERATIVE_GROUPS macro, which is defined https://github.com/NVlabs/cub/blob/master/cub/util_arch.cuh#L48:
#if (__CUDACC_VER_MAJOR__ >= 9) && !defined(CUB_USE_COOPERATIVE_GROUPS)
    #define CUB_USE_COOPERATIVE_GROUPS
#endif

Further, blindly using 0xffffffff would be inappropriate, as that could mean a hang when member_mask is a subwarp.

Oh! I think I see what the problem is. We're compiling all CUDA sources with clang and _CUDACC_VER* is only defined by NVCC. Enabling CUB_USE_COOPERATIVE_GROUPS should indeed make this patch unnecessary.
In general, is there particular reason for using nvcc-specific __CUDACC_VER* macros for checking CUDA SDK version? Shouldn't CUDA_VERSION be used instead? Granted, nvcc used to be the only CUDA compiler, and those macros would produce equivalent results, but this is no longer the case.

Further, blindly using 0xffffffff would be inappropriate, as that could mean a hang when member_mask is a subwarp.

AFAICT shfl will not hang. In diverged context it will produce undefined results for inactive threads. shfl.sync has the same behavior -- with all-ones mask, shfl.sync will also result in undefined data for inactive threads. For all practical purposes both old and new code assume that execution is non-diverged. There's no practical way to guarantee that in practice -- divergent branch may have happened way up the call chain where the code had no idea that one of the functions at the bottom may require non-diverged context. The bottom line is that the new assembly should be functionally equivalent to the one it replaces.
E.g. PTX ISA says this for for shfl:

Note that results are undefined in divergent control flow within a warp, if an active thread sources a register from an inactive thread.

for shfl.sync:

Note that results are undefined if a thread sources a register from an inactive thread or a thread that is not in membermask.

vote will produce 0 for inactive threads, so there's no hang either.
I may be missing something, though.

Hi Artem,
I'll look into replacing the *CC macro with CUDA_VERSION.
For SM7+, the *sync() methods can hang if your mask requires certain
threads to show up, yet the application's control flow prevents them from
doing so.  (The compiler literally inserts a spin loop to wait for them all
to show up.)  For example, suppose some control flow in which lane0 skips a
shuffle in which lane31 shares a value with other threads:
if (threadIdx.x > 0)
y = __shfl_sync(0xffffffff, x, 31);   // inappropriate mask (hang)
__warp_sync(0xffffffff);                 // all threads reconverge here
will deadlock because the other threads will wait indefinitely for thread0
to either (a) show up at the shuffle (per the mask), or (b) exit the
program, which it can't do until the warpsync is satisfied, which requires
the other threads waiting on the shuffle.
Secondly, the particular text you're referencing from the PTX ISA has to do
with what happens when you have a proper mask, but try to source data
from an inactive lane, e.g.:
if (threadIdx.x > 0)
y = __shfl_sync(0xfffffffe, x, 0);   // appropriate mask (no hang), but
undefined value of y
Hope that helps,
Duane

Duane G Merrill III, PhD
Principal Research Scientist
NVIDIA Corporation
<EMAIL_ADDRESS>On Fri, May 24, 2019 at 3:23 AM Artem Belevich<EMAIL_ADDRESS>wrote:

Oh! I think I see what the problem is. We're compiling all CUDA sources
with clang and _CUDACC_VER* is only defined by NVCC. Enabling
CUB_USE_COOPERATIVE_GROUPS should indeed make this patch unnecessary.
In general, is there particular reason for using nvcc-specific
__CUDACC_VER* macros for checking CUDA SDK version? Shouldn't
CUDA_VERSION be used instead? Granted, nvcc used to be the only CUDA
compiler, and those macros would produce equivalent results, but this is no
longer the case.
Further, blindly using 0xffffffff would be inappropriate, as that could
mean a hang when member_mask is a subwarp.
AFAICT shfl will not hang. In diverged context it will produce undefined
results for inactive threads. shfl.sync has the same behavior -- with
all-ones mask, shfl.sync will also result in undefined data for inactive
threads. For all practical purposes both old and new code assume that
execution is non-diverged. There's no practical way to guarantee that in
practice -- divergent branch may have happened way up the call chain where
the code had no idea that one of the functions at the bottom may require
non-diverged context. The bottom line is that the new assembly should be
functionally equivalent to the one it replaces.
E.g. PTX ISA says this for for shfl:
Note that results are undefined in divergent control flow within a warp,
if an active thread sources a register from an inactive thread.
for shfl.sync:
Note that results are undefined if a thread sources a register from an
inactive thread or a thread that is not in membermask.
vote will produce 0 for inactive threads, so there's no hang either.
I may be missing something, though.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NVlabs/cub/pull/164?email_source=notifications&email_token=AALILQGMRR67EYZPEGHY77DPW6JW5A5CNFSM4HNP6OK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEMFSY#issuecomment-495502027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALILQEO4H3BPHPYMLY7363PW6JW5ANCNFSM4HNP6OKQ
.

OK. Thank you for clarification.


ISPN-12803 Don't warn on evict() when eviction strategy is MANUAL

https://issues.redhat.com/browse/ISPN-12803

Merged, thanks!


Override bridgeERC20 for custom fee token

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Override bridgeERC20 and bridgeERC20To functions for the custom fee token
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Override functions and add unit tests

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.
Unit tests are added

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

Project coverage is 29.14%. Comparing base (d9ab039) to head (9a4d4af).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                  Coverage Diff                  @@
##           custom-fee-token     #203       +/-   ##
=====================================================
- Coverage             40.13%   29.14%   -10.99%
=====================================================
  Files                    75       65       -10
  Lines                  5183     4104     -1079
  Branches                826      826
=====================================================
- Hits                   2080     1196      -884
+ Misses                 2996     2833      -163
+ Partials                107       75       -32

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
27.14% <ø> (ø)

common-ts-tests
26.72% <ø> (ø)

contracts-ts-tests
12.25% <ø> (ø)

core-utils-tests
44.03% <ø> (ø)

sdk-tests
34.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 10 files with indirect coverage changes

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

Project coverage is 29.14%. Comparing base (d9ab039) to head (041144e).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                  Coverage Diff                  @@
##           custom-fee-token     #203       +/-   ##
=====================================================
- Coverage             40.13%   29.14%   -10.99%
=====================================================
  Files                    75       65       -10
  Lines                  5183     4104     -1079
  Branches                826      826
=====================================================
- Hits                   2080     1196      -884
+ Misses                 2996     2833      -163
+ Partials                107       75       -32

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
27.14% <ø> (ø)

common-ts-tests
26.72% <ø> (ø)

contracts-ts-tests
12.25% <ø> (ø)

core-utils-tests
44.03% <ø> (ø)

sdk-tests
34.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 10 files with indirect coverage changes

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

Project coverage is 29.14%. Comparing base (d9ab039) to head (f4e3b8a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                  Coverage Diff                  @@
##           custom-fee-token     #203       +/-   ##
=====================================================
- Coverage             40.13%   29.14%   -10.99%
=====================================================
  Files                    75       65       -10
  Lines                  5183     4104     -1079
  Branches                826      826
=====================================================
- Hits                   2080     1196      -884
+ Misses                 2996     2833      -163
+ Partials                107       75       -32

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
27.14% <ø> (ø)

common-ts-tests
26.72% <ø> (ø)

contracts-ts-tests
12.25% <ø> (ø)

core-utils-tests
44.03% <ø> (ø)

sdk-tests
34.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 10 files with indirect coverage changes


What estimator did you use to score the result?

What estimator did you use to score the result? Did you verify the scoring result across different interfaces? I downloaded your .swf files and load them in sabaki and the scoring result is completely different. From the result of your article I believe that you used an outdated estimator where the dead stones have to be hand picked or if you wrote it yourselves then I believe you completely misunderstood how the Go scoring system works.

I think you may find our explanation in https://boardgames.stackexchange.com/questions/58127/is-adversarial-policies-beat-professional-level-go-ais-simply-wrong?newreg=951faac0dc544fdd8d02936ddee40e9b informative.
I'm going to leave this issue open for now as a kind of FAQ, and close once we have an updated version of the paper on arXiv that clarifies this.


Prep for Release v0.25.6

This PR does the following:

prep for release v0.25.6

Tugboat has finished building the preview for this pull request!
Link:

https://pr808-awr7y38qgkquqi9gshiujtaetsbvpbcw.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61bb59d25f46ed13d8129701


Job locking

Hello!
Thanks for this lib :)
I was reading the docs and the source and I think that the example given (see below) isn't up to date.
  forever $ do
    -- Attempt get a payload or block until one is available
    payload <- lock conn

    -- Perform application specifc parsing of the payload value
    case fromJSON $ pValue payload of
      Success x -> sendEmail x -- Perform application specific processing
      Error err -> logErr err

    -- Remove the payload from future processing
    dequeue conn $ pId payload

The lock function seems to have been removed. What's the right way to use this now?
Thanks,
Louis

It's not up to date. Will update when I find this "free time" I've heard so much about. PRs welcome!


Upgrade deps

Coverage remained the same at 100.0% when pulling fc67d3adcc951d77508d44597739efbc1707c7b9 on upgrade-deps into 9b26b4a2773d3c19ebc60f476bfc2a4d48198cba on master.


Google search result has fallen off a cliff

For some reason, the app's Google search ranking has fallen off a cliff. It is still the top result for queries like "Eco game calculator" on Bing, Yahoo, Duck Duck Go. But the GitHub repository is a higher result ranking than the actual app on Google.
Also, the develop url (https://eco-crafting-tool.vercel.app/) seems to have better Google result ranking than https://eco-calc.com. Need to tell search engines to ignore that url.

Seems like this is resolved. Problem may have been having two identical sites with different domains? Modifying robots.txt to exclude non-prod env seems to have worked.


Allowed MAC addresses in Captive Portal

If i enter a allowed MAC address in Captive Portal i don't see it so the list is empty. What i'm doing wrong or is this a bug in the gui?

forgot to press enter after inserting the value? it turns blue, like this:

Hello. I'm sorry, you are right i didn't press enter but i didn't also found in any documentation to press enter. I thought alway i'm wrong in the format of MAC because some devices need 00:00:00:00:00:00, some<PHONE_NUMBER>00 and others 00-00-00-00-00-00. Maybe it will be useful to show the exptected format in the help.
Thank you very much for the fast response.


Sometimes the referenced objects and methods may appear as Unknown

Environment data

Language Server version: vscode-pylance-2023.8.10
OS and version: Win11 22H2
Python version (& distribution if applicable, e.g. Anaconda): python 3.11 & python.org

Code Snippet

PP.zip
Repro Steps

Open the project using VSCode, place the mouse over self.brain.generate_reaction(objective), and both "brain" and "generate_reaction" will display as "unknown"
Note that not every time you open VSCode will result in a failure displaying "unknown." I don't know how to reproduce it consistently; sometimes the occurrence rate is surprisingly high, and other times, it might only happen once after opening it twenty-something times in a row.

Expected behavior
It should complete indexing normally and display the corresponding type.
Actual behavior
Didn't see 'index done' in the log, and the type is 'Unknown'.
Logs

trace_log.txt

This isn't the kind of issue that we can figure out from a log. Please file a new issue when you are able to provide code the reproduces what you are seeing.

Okay, I will try to provide a small code that can be shared publicly, and then file a new issue.

This issue is not reproducible 100%. I would like to ask what possible factors need to be taken into consideration to narrow down the scope

Well, I don't have a lot of context so it's tough to speculate, but here are some ideas:

the libraries you're using
whether you have stubs for them
your settings

Thank you for your suggestion.

I've tried to provide a reduced-scope project code, but I can't reliably reproduce the issue. It still occurs probabilistically. I've updated the issue description.

Could you reopen this issue? I have to go to the hospital now and might not have time to filea new issue.

After updating the extension and reloading the window, I also encounter this issue.

Hello, can the information currently provided help identify the problem?

Sorry for the delayed response. I was on vacation last week.
I was just able to reproduce the issue! Only once so far, but that's promising. I wasn't seeing it when just starting VS Code. But you mentioned that it repro'd after reloading the window due to updating an extension. The same thing happened when I downgraded Pylance from 2023.8.20 to 2023.8.10 and reloaded the window.
I'll continue investigating.

No problem, hope you had a great vacation!
I'm glad you were able to reproduce this issue. It has indeed caused some inconvenience to my current work.

Repro steps:

Unzip https://github.com/microsoft/pylance-release/files/12257143/PP.zip
poetry install
Open folder in VS Code
Select the poetry environment.
After Pyright/Pylance initializes, mouse over brain in _action__todo.
If hover says that the type is Unknown, congrats you repro'd it. If not, try one of the following: Developer: Reload Window, restart VS Code, or delete + re-paste file contents.

@erictraut, could you take a look at this? I think it's a type evaluation issue. A race condition of some sort? It repros in both Pylance (2023.8.10+, and possibly earlier) and Pyright (1.1.322 and tip of main).
See repro steps in my previous comment.
The type shown when hovering over self.brain in _action__todo is inconsistent. Usually, it's GenerativeAgent (the type assigned in __init__), but sometimes (this issue) it's Unknown.
There are a couple other symbols, all base class-related, that are also curiously Unknown when it repros:

super().__init__
self._send
self.id

I can repro it fairly easily -- maybe 10-20% of the time -- but have never managed to repro it in the debugger.
I was able to simplify main.py to the following while still getting an occasional repro. I wasn't able to repro it after removing the unused imports or the 3 lines of code above BrainAgent though.
import openai
import langchain
import faiss

from langchain.cache import SQLiteCache
from langchain.chat_models import ChatOpenAI
from langchain.embeddings import OpenAIEmbeddings
from langchain.vectorstores import FAISS
from langchain.docstore import InMemoryDocstore
from langchain.retrievers import TimeWeightedVectorStoreRetriever

from pydantic import BaseModel
from agency.agent import Agent, access_policy, ACCESS_PERMITTED
from agency.amqp_space import AMQPSpace
from pp import GenerativeAgent, GenerativeAgentMemory

langchain.llm_cache = SQLiteCache(database_path=".langchain.db")

llm = ChatOpenAI(client=openai.Completion)
embeddings_model = OpenAIEmbeddings(client=openai.Embedding)

class BrainAgent(Agent):
    def __init__(self, id: str):
        super().__init__(id)
        self.brain = "str"

    def _action__todo(self, objective: str) -> None:
        res = self.brain

This isn't a race condition, since we don't have any asynchronous code within the type evaluator. However, it does smell like a case where different evaluation order produces different results. A hover request is a high priority, so if it gets queued before the lower-priority full type check of the file, it will cause the types of some nodes to be evaluated.
I've done my best to repro the problem, but I'm not able to. I even tried increasing the _userActivityBackoffTimeInMs time to 10s to delay the full type check. Normally that makes it easier to repro bugs like this. But alas, I haven't been able to repro it.
If you're able to repro it semi-consistently, let's take advantage of that and try to diagnose the problem on your machine. Here's the process I recommend. First, set _userActivityBackoffTimeInMs temporarily to 10000 (ms). Now run the language server and set a breakpoint in the hover provider. Then carefully move the mouse pointer over the node that repros the problem. You should then be able to use the debugger to step through the type evaluator and figure out where the Undefined type is coming from.

set _userActivityBackoffTimeInMs temporarily to 10000 (ms)...

I wasn't able to repro the issue that way. But I also remembered that when reproing this I've been waiting for the variable res in _action__todo to get grayed out ("res" is not accessed) before hovering over brain. I'm assuming that that diagnostic hint indicates that the file has been checked?

To be clear, I'm saying that the issue repros when I hover after that diagnostic hint appears. Any other theories as to what might be going on here?

No, but if you can repro it on a semi-deterministic basis, you could set a conditional breakpoint and step through the code when it hits. For example, if the problem appears to be with evaluating self.brain, you can set a conditional breakpoint toward the top of getTypeOfMemberAccessWithBaseType right after memberName is assigned. The condition would be memberName == 'brain'. Once that hits, step through the code and see if you can figure out how Unknown is being produced. Let me know if you get stuck. Happy to help.

Sadly I still can't repro this in the debugger, but I was able to make some progress by adding extra logging and reproing the issue on a custom vsix.
When the bug repros, the classType object passed to synthesizeTypeVarForSelfCls has zero entries in classType.details.fields. This is the class that is eventually passed by getTypeOfMemberAccessWithBaseType to getTypeOfObjectMember and therefore the brain member isn't found.
I haven't dug into where that classType is coming from and why it's empty yet. But, since synthesizeTypeVarForSelfCls appears to clone the class, I wondered if maybe it is sometimes called before details.fields has been populated and then that field-less clone is not replaced once we have the fields. I don't have any evidence to back this up -- just a guess.

OK, that's a good clue. It sounds like there's some circular dependency in the code being analyzed. That can lead to type evaluation behaviors that differ based on where in the cycle the evaluation begins.
At the point where synthesizeTypeVarForSelfCls is called, you should be able to see what else is on the stack. That will tell us what else is being evaluated at that time. I'm guessing that the class referenced by classType is partially evaluated. You can look back up on the stack for a frame within the getTypeOfClass function. You can see where fields is assigned within getTypeOfClass; search for classType.details.fields =. This value is  assigned only after all of the base classes and the metaclass (if specified) within the class statement are processed.

Stack is below. Turns out that getTypeOfClass has fully completed before synthesizeTypeVarForSelfCls is called. evaluateTypeOfParameter calls getTypeOfClass before calling inferParameterType.
And strangely, when the bug repros, the type returned by getTypeOfClass is pulled from the type cache. Prior to that the class's cached type is correct (has fields) but at some point either the fields are removed or the whole cached type is replaced. Not sure which yet.
at synthesizeTypeVarForSelfCls (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeUtils.ts:1919:28)
at inferParameterType (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:17213:28)
at evaluateTypeOfParameter (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18586:35)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20247:17)
at evaluateTypeForSubnode (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18730:9)
at getInferredTypeOfDeclaration (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20246:20)
at forEach (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20579:36)
at Array.forEach (<anonymous>)
at getEffectiveTypeOfSymbolForUsage (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20523:15)
at getTypeOfName (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:4222:43)
at getTypeOfExpression (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:977:30)
at evaluateTypesForExpressionInContext (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18521:9)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:799:13)
at evaluateTypeForSubnode (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18730:9)
at getType (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:798:20)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:19640:28)
at a.getDeclarationsForNameNode [as timeOperation] (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\common\timing.ts:40:20)
at I._getHoverResult (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageService\hoverProvider.ts:204:48)
at I.getHover (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageService\hoverProvider.ts:129:41)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageServerBase.ts:964:106)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\program.ts:694:64)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:579:20)
at a.runWithCancellationToken [as timeOperation] (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\common\timing.ts:40:20)
at k.run (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\program.ts:694:26)
at S.run (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\service.ts:388:30)
at E.onHover (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageServerBase.ts:963:34)

@erictraut, I finally figured it out. An OperationCanceledException is thrown within getTypeOfClass. See the stack below.
There are two sets of writeTypeCache calls in getTypeOfClass. One set before classType.details.fields is assigned, and one after. This exception is thrown between these two sets of writeTypeCache calls, leaving an incomplete ClassType in the type cache.
at throwIfCancellationRequested (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\common\cancellationUtils.ts:42:15)
at checkForCancellation (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:587:13)
at getTypeOfExpression (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:968:9)
at forEach (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:15676:29)
at Array.forEach (<anonymous>)
at getTypeOfClass (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:15659:28)
at evaluateTypeOfParameter (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18621:49)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20309:17)
at evaluateTypeForSubnode (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18792:9)
at getInferredTypeOfDeclaration (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20308:20)
at forEach (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20641:36)
at Array.forEach (<anonymous>)
at getEffectiveTypeOfSymbolForUsage (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:20585:15)
at getTypeOfName (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:4230:43)
at getTypeOfExpression (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:985:30)
at evaluateTypesForExpressionInContext (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18578:9)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:807:13)
at evaluateTypeForSubnode (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:18792:9)
at getType (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:806:20)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:19702:28)
at a.getDeclarationsForNameNode [as timeOperation] (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\common\timing.ts:40:20)
at I._getHoverResult (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageService\hoverProvider.ts:204:48)
at I.getHover (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageService\hoverProvider.ts:129:41)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageServerBase.ts:964:106)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\program.ts:694:64)
at callback (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\typeEvaluator.ts:579:20)
at a.runWithCancellationToken [as timeOperation] (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\common\timing.ts:44:28)
at k.run (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\program.ts:694:26)
at S.run (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\analyzer\service.ts:388:30)
at E.onHover (c:\Users\erikd\.vscode-insiders\extensions\ms-pyright.pyright-1.1.322\dist\pyright-internal\src\languageServerBase.ts:963:34)

Ah, good find. That explains why I wasn't able to repro this in pyright. I have cancellations disabled in the debug build because they make debugging very difficult.
Removing the type from the type cache would eliminate this problem some of the time, but it's not sufficient to completely fix the problem. Circular references can result in legitimate cases where there are references to a partially-constructed class. For example, one of the base classes of class Foo could use list[Foo] as one of its base classes. The class object is later fully constructed, so those references become valid at that time. If we were to remove the class from the type cache, we'd still have those partially-constructed classes referenced in some cases. :(
The safest thing to do is to completely discard the entire type evaluator instance (i.e. call this._createNewEvaluator in _runEvaluatorWithCancellationToken) when a cancellation exception is caught, but that's a pretty big sledge hammer.
A variant of that idea is to say that cancellation exceptions that happen within certain pieces of code, such as getTypeOfClass, are rethrown as a variant of the OperationCanceledException that indicates that the type evaluator state is potentially corrupt and should be discarded. That way, we could use the sledge hammer only in specific cases where it's needed.
Any other ideas?

cancellation exceptions that happen within certain pieces of code, such as getTypeOfClass, are rethrown as a variant of the OperationCanceledException that indicates that the type evaluator state is potentially corrupt and should be discarded. That way, we could use the sledge hammer only in specific cases where it's needed.

Ok, that sounds good. I'll give that a shot.

This issue has been fixed in prerelease version 2023.8.41, which we've just released. You can find the changelog here: CHANGELOG.md

Thank you


Heroku bot keeps going offline after some time

Hello! first of all, thank you for making such an amazing bot and providing it to us free of charge!
im currently running it on a heroku app, and it works exactly as intended but after some time of not using the bot it decides to turn itself on and i have to manually turn it on again
i've googled it a bit and it seems like it's a problem of the dyno type.. mine is a web type but i don't get the option to change it into a worker type.. if anyone could help i would greatly appreciate it!

It's not a problem, it's doing as intended.

So that's 1000 free hours every month.
Because of this your app will go sleeping after 30 min of inactivity I guess.
You can fix this by setting up some sort of pinging that pings your heroku app url every 30 min.
Can be done using New Relic's addon for heroku you can also use something like pingdom.
Just note that if you don't add your creditcard you will have 550 hours, which is not enough to keep the app running 24/7.
So you will need to make sure it sleeps around 6-7 hours every day, but not pinging the app at certain hours.

Alright, ill look into it! ty very much


[WIP] feat: Inline const variables in CSS

Fix #167

awesome change!

left some comments :) awesome first pass

@madou this is ready for review now. :)

awesome work - just left some comments to add some stuff back to tests 😄

@madou I think this is ready for another review. Took longer than what I expected. templateLiteralToCss is a beast :D

love it


add option to byte-compile python at install time

Problem description
uv by default does not compile python files to bytecode at installation, but provides an option to do so via the compile-bytecode setting in the toml file and the UV_COMPILE_BYTECODE env variable and the --compile-bytecode CLI flag.
As far as I can tell (apologies if I'm mistaken) pixi also does not create a __pycache__ folder at install time. I searched the global rattler/uv-cache and local .pixi folders, and although there were some pyc files, they were only for packages that had already been imported and run previously, not for newly installed packages.
It would be great if pixi provided the option to byte compile python packages at install time. As the uv docs state:

Compiling Python source files to bytecode is typically desirable for production images as it tends to improve startup time (at the cost of increased installation time).

This is the use-case I have in mind as well. For our python application in particular, the difference between the first run and subsequent ones (after the pyc files have been created) is drastic. I'd like to use pixi as part of the multi-stage build we have for our application, but currently I need to first install dependencies via pixi and then manually compile the python files e.g. via compileall.
This blogpost gives an example of the sort of dockerfile I'd like to create.

This is definitly something we want to support but we also need support for conda packages.
https://github.com/conda/rattler/issues/431 tracks conpiling python files in rattler.


initial change to support both N. and S. Hemisphere

Hi,
My first PR using gitHub.
Caution : Noaa pahm not tested with my modfications, only pahm in schism project was tested with similar changes.
Thanks
Jerome

@josephzhang8 @NeaLab-NC
Thank so much Jerome. I'll look at it next week and implement the changes as they fit into PaHM. I'll update SCHISM/PaHM as well

Jerome, thank you so much. I will update SCHISM and ADCIRC as well. Please check SCHISM/PaHM from your side.


Return isSystem when using ldap

Coverage decreased (-0.02%) to 54.801% when pulling 689994fa93b08a03aba87a69be7c0bd8cf23a572 on ywk253100:170808_bug_fix into 5ba363657fabd0335dc4149ce6cc0aa68bceada1 on vmware:master.


Nodejsversions

should we bring up tools like nvm or fnm

@roastlechon I tried to cover that in:

We discussed in the last Ref Arch team meeting and feedback was that it looked good. Landing


What would be the best way to dynamically change content of overlay from scene?

Moved question to https://github.com/facebook/react-native/issues/8350

See my comment here. In terms of react-router-native, we should probably make this easier by passing the overlay ref in props to route components as soon as this lands in a stable release.

Excited for new changes in NavigationExperimental!

Same here. I think we are only a couple weeks away from calling it just Navigation. ⌛
🍺

@jmurzy Hey, posting the gist I linked to from Discord so others can follow-along/help. This is my attempt (not a runnable example, but has all relevant redux code) at using redux to control the title of a overlayComponent. The issue is that the actions do not fire when routes change from pop/back/etc because the components have already rendered.
https://gist.github.com/cpsubrian/278ad43f79f2301c4aba1cb5401fca99

@cpsubrian Thanks for the gist. I'll try to reproduce this on my end, and get back to you in the next few days.

Yeah no rush, in the meantime just adding the header in the component. Would be nice to get the animations driven by the interpolators back at some point though.

Thanks for taking a look.

Is it possible to pass information in  to compoent and overlay?
I have the two paths below and only need to add title of the header and the text inside of TextView.
<Route path="/help" component={TextView} overlayComponent={HomeHeader}/>
<Route path="/information" component={TextView} overlayComponent={HomeHeader} />

something like
<Route path="/help" component={TextView} overlayComponent={HomeHeader} title="Help" text="Help Text"/>
<Route path="/information" component={TextView} overlayComponent={HomeHeader} title="Information" text="bla bla..."/>


Cannot import web-sdk

Project details:
node: 14.15.1
vue: 2.x
(let me know if there's any other details you need)
Im aware thats not much to go on but I'm hoping you may have some context that may assist me getting this setup.
Cannot import the sdk (version 2.22.1) It's defiantly the import causing this error as when I comment it out the site renders correctly without error

@mk-ryan1988 Sorry to hear you're having trouble. Would it be possible to include your package.json file and a brief snippet of how you're importing the SDK?
I haven't tested our SDK this on Vue but it should work with Webpack. We currently have a sample app built for React that uses Webpack and haven't seen these issues. Here's a link in case that offers some more insight: https://github.com/mParticle/mparticle-web-sample-apps/tree/main/core-sdk-samples/higgs-shop-sample-app

Sure, I can's share the code as it private but I've setup a mock sandbox with the same package,json and example usage.
The sandbox is unlikely to compile due to some private dependancies being included
Let me know if you need anything else :)

hey @alexs-mparticle did you get a chance to take a look at the sandbox? I doesn't seem to recreate the issue but I'm at a complete loss here

@mk-ryan1988 I'm taking a look right now and just getting things set up. Nothing is jumping out at me right now, but I'll reach out if I have any further questions.
For now, please tell me what version of node you are using.
Also, can you try rolling back your version of mParticle you're importing? I want to rule out that maybe we recently introduced something that is colliding with something in your code base.

We're currently on node 14 atm I'm afraid. Any version you'd recommend?

I pulled your sample project locally and set it up based on the same version you are using and have had no issues building or running the code.
I am not as familiar with Vue as I am React, but I do wonder if there is a race condition caused between the time your application mounts vs when mParticle initializes.
In React, I've often used useEffect to initialize mParticle after the main app mounts. Not sure if there's something similar in Vue.
Perhaps you can also try wrapping mParticleInit(); in a setTimeout in your main.js, like so:
setTimeout(function () {
  mParticleInit();
}, 100);

Lastly, try reaching out to your CSM/TSE to open a ticket if you need a faster support.

Hi @mk-ryan1988,
Do you have an existing support ticket regarding this issue? If not, can you please file one using this link?
Thanks,

Hey, I've not opened a support ticket yet as I went ahead an got a POC using the code snipped rather than self hosting.
I did recently try installing an earlier version, I went back to 2.10.1, and this resolved the error. So there must be a breaking change in a later version

Okay I did some further installing of various version and on our setup:
Project details:
node: 14.15.1
vue: 2.x
The error was introduced into version 2.16.2.
2.16.1 loads without error but 2.16.2 and above all I replicate this issue

Thanks for that feedback. I took a look at what changed between those versions and the main thing that jumps out at me is that we updated some things in our build process to more "modern" standards. Granted, that was over a year ago, and "modern" is relative.
I would be curious to know if the issue goes away using a more recent version of node. If memory serves, there were several projects were working with around that time that had issues on Node 14 and required some extra updates to get them to work on Node 15 and 16.

Yep "modern" in web today is subjective :)
We may we try and bump the node versions of our project but in the meantime do you see any issues with us pinning the sdk version to 2.16.1


Optional nested objects not working correctly

I have the following code. The data object is created from a request which may or may not have an address in the payload.
class NewRegularUserDto extends Data
{
    public function __construct(
        #[Required] #[Email]
        public string $email,
        #[Required] #[StringType]
        public string $role,
        #[Required]
        public ProfileDto $profile,
        #[Sometimes]
        public AddressDto|Optional $address,
    ) {
    }
}

When it doesn't have an address in the payload I would expect it to create the data object without an address but it is throwing a validation error related to the validation in the AddressDTO. I also tried
        public ?AddressDto $address = null,
But it still tries to validate an address and returns an error.
How do I make it so that if there is an address in the payload it is validation and if there is no address then do not try to validate it and set $address to null. Is this linked to Issue #441 ?

I cannot reproduce this:
it('ca', function(){
    class AddressDto extends Data{
        public function __construct(
            public string $a,
        )
        {
        }
    }

    class NewRegularUserDto extends Data
    {
        public function __construct(
            public AddressDto|Optional $address,
        ) {
        }
    }

    NewRegularUserDto::validate((new Request())->merge([])); // works
    NewRegularUserDto::validate((new Request())->merge(['address' => ['a' => 'b']])); // works
    NewRegularUserDto::validate((new Request())->merge(['address' => null])); // fails validation
});

Please provide me a test like this fails.

It turns out that the latest version fixes this issue so I think it is OK now. I believe it must have been a bug in a prior version


Create README.md

retest this please

retest this please

@ericvaandering, Eric, can I close this one?

No, please leave it open. I want to play with this w.r.t. Jenkins.

retest this please

retest this please

retest this please

retest this please

retest this please

Retest this please

retest this please

retest this please

retest this please

retest this please


add hover effect to github icon in footer

maybe animate, or just have the colour change

I can do this, assign this to me.

Create PR #18 for the issue.

resolved by #19


Research: determine steps required to upgrade our CRDs

We want to upgrade our CRDs from alpha to either beta or v1.
The purpose of this card is to research what are the steps required to bump our current CRDs to a new maturity level. Users with alpha resources should still be able to operate their clusters and should not lose their already defined resources.
Acceptance criteria

[x] determine the list of actions that have to be performed
[x] have a rough estimation about the time required by each operation that has to be done
[x] ensure no data loss is caused by users

@raulcabello can you estimate how hard would it be to implement the conversion?

@flavio I don't believe it will take long around two days (or even less than that)
Closing this since we just agreed to go for v1 and keep v1alpha2 with the conversion https://github.com/kubewarden/kubewarden-controller/issues/245 . Feel free to reopen if you still want to discuss this.


Components PathPrefix:false in nuxt.config.ts breaks Lib

Describe the bug
Hi, at first very promising lib! Would love to get it working in my project.
I've set the path prefix option to false in my nuxt.config.ts.
// https://v3.nuxtjs.org/api/configuration/nuxt.config
export default defineNuxtConfig({
  modules: ['nuxt-og-image', 'nuxt-icon'],
  components: [
    {
      path: '~/components',
      pathPrefix: false, // <-- this
    },
  ],
});

This seems to break the support for the internal lib components llike <OgImage />. I also tried to play a little bit with the liv config:
...
 ogImage: {
    componentDirs: ['~/components/OgImage']
  }
...

I see some errors in my console where nuxt is running:
[nuxt] [request error] [unhandled] [500]  (500 The path / is missing the og-image payload. (/api/og-image-options?path=/))          3:55:16 PM
  at async $fetchRaw2 (./node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:234:14)
  at async $fetch2 (./node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:239:15)
  at async fetchOptions (./.nuxt/dev/index.mjs:1559:15)
  at async ./.nuxt/dev/index.mjs:2420:19
  at async Object.handler (./node_modules/h3/dist/index.mjs:1284:19)
  at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1359:7)

and also in the Browser Console like in the Reproduction:
blitz.e809191e.js:42 [nuxt] [request error] [unhandled] [404]  (404 Island component not found: undefined (/__nuxt_island/MyTemplate_NBc25afyoU?

But this has no effects. Would love the get some help on this problem.
Reproduction
https://stackblitz.com/edit/nuxt-starter-ubcxwu?file=nuxt.config.ts
System / Nuxt Info
- Operating System: `Darwin`
- Node Version:     `v18.14.2`
- Nuxt Version:     `3.6.2`
- Nitro Version:    `2.5.2`
- Package Manager<EMAIL_ADDRESS>- Builder:          `vite`
- User Config:      `ssr`, `modules`, `directus`, `image`, `gsap`, `app`, `runtimeConfig`, `build`, `components`, `sitemap`, `nitro`, `experimental`, `ogImage`
- Runtime Modules:  `<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS><EMAIL_ADDRESS>`<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    `-`

Hey, thanks for the issue.
I think this is a limitation with Nuxt Islands, they need the path prefix, will need to investigate more. For now, you can see if the following helps
 components: [
    {
      path: '~/components',
      pathPrefix: false, // <-- this
    },
   {
      path: '~/components/OgImage',
      pathPrefix: true
    },
  ],

This is fixed in the latest version :)


ledger-live-desktop: 2.17.1 -> 2.18.0

Motivation for this change
Fix a bug with the historical price chart
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 106064 run on x86_64-linux 1

1 package built:

ledger-live-desktop


Fix typo in resize error message.

Coverage remained the same at 92.346% when pulling 38d926bf82147269afd1ee29ec1c1745447b2852 on Web-Assembler:master into 5c9d981b463146ddfb8026dca6cd31561f007770 on timber:master.


Update  BizTalk Server CEIP Privacy Policy

Remove Microsoft BizTalk Server CEIP Privacy Policy broken link

Docs Build status updates of commit 9a53b7e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/install-and-config-guides/upgrade-to-biztalk-server-2016.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ccc93d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/install-and-config-guides/upgrade-to-biztalk-server-2016.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Why cannot I find Adamixer in  the mmdetection?

Thanks for your work!! but I cannot find the Adamixer...

Is my mmdetetion version wrong? (mmdet=2.25.3 and mmcv-full=1.7.0)

Ooops, you should git clone this repo rather than the official mmdetection repo as our code has not yet been integrated into the official mmdetection repo now.

Thanks!!!!


DNS zones

I'm using a roku TV and trying to use vudu, but it doesn't work, it tells me my country error instead of logging in.
All the other services work and even on my phone, such as Spotify and Pandora.
Any ideas? Maybe they changed their url?

Try something along the lines of https://github.com/ab77/netflix-proxy/wiki/Apple-TV-4,-Roku,-Google-Chromecast-and-any-other-device-with-hard-coded-DNS

So I should  block Google DNS servers?

Yes, try that first if going blind. Otherwise put a packet sniffer between router and Roku and find out what it is actually doing..

Please re-open if required.


Gateway not redirecting

I just added the plugin to a client site for testing.
When submitting the payment form, the page will often return/reload the page, with no errors shown in the code or logs. When clicking the submit button multiple times, I can get the gateway to redirect to QuickPay and finish the payment as expected.
The logs show Undefined property: stdClass::$id' in cart errors, but I don't know whether this relates to the issue or something else.
Is any special setup needed for this gateway compared to some of the "official" plugins (e.g., Stripe)?
Craft Version: 4.3.1
Commerce Version: 4.2.2
Plugin Version: 4.0.0

Hi,
We are aware of this error issue not being handle properly. This error usually happens if the orderId that is sent to Quickpay isn't unique.
We have on our todo, to make a better error handling of the specific error.

Closed, as version 4.1.0 returns better error messages now


Skip modules from package-lock.json in react-app in VSCode (checkJs: true)

If this is not case of vscode settings, this should be fixed in vscode update?:
https://stackoverflow.com/questions/49075658/skip-modules-from-package-lock-json-in-react-app-in-vscode-checkjs-true

Well, I asked the question on stackoverflow!
I also added them here, because it seems to me that it is a thing to fix, that this is not happening now.


Update thermostat behavior and update fork branch to be in line with current WyzeAccessory updates

This PR should address four things:

Refactor of WyzeAccessory to remove thermostat relevant components that were left previously
Update WyzeThermostat to hold all needed functionality inside it's own class and not rely on WyzeAccessory - this is to fall in line with the new structure of the project
Push a fix to an issue where you cannot set the thermostat temp above or below the arbitrary thresholds imposed by Homekit - #203
Fix for constant reboot when using thermostat - #228

@jfarmer08 feel free to take a look at this and give it a test locally. Works locally on my side but would appreciate a few other people trying it to make sure I did not break anything outside the thermostat. I only have two cameras and thermostat so not a great range of variables being tested.

The CHANGELOG.md log should reflect the change of this PR.

@jfarmer08 any other notes on this?

I don't have a thermostat so I cannot test that, but I didn't test with my 83 other products and didn't see any issue.

@jfarmer08 do you actually have 83 wyze products or you just have a bunch?

Yeah I have about that many.


ListView and GridView sample, binding error

When the project is changed from Arm to x64 so it will run on the desktop, recompiled and run, a binding error occurs, to wit:
System.InvalidCastException occurred
HResult=0x80004002
Message=Unable to cast object of type 'System.Char' to type 'System.String'.
Source=
StackTrace:
at ListViewSample.SimpleListViewSample.SimpleListViewSample_obj10_Bindings.Update_Key(Object obj, Int32 phase) in C:\dev\Windows-universal-samples-master\Windows-universal-samples-master\Samples\XamlListView\cs\obj\x64\Debug\Samples\SimpleListViewSample\SimpleListViewSample.g.cs:line 318
at ListViewSample.SimpleListViewSample.SimpleListViewSample_obj10_Bindings.Update_(GroupInfoList obj, Int32 phase) in C:\dev\Windows-universal-samples-master\Windows-universal-samples-master\Samples\XamlListView\cs\obj\x64\Debug\Samples\SimpleListViewSample\SimpleListViewSample.g.cs:line 307
at ListViewSample.SimpleListViewSample.SimpleListViewSample_obj10_Bindings.Update() in C:\dev\Windows-universal-samples-master\Windows-universal-samples-master\Samples\XamlListView\cs\obj\x64\Debug\Samples\SimpleListViewSample\SimpleListViewSample.g.cs:line 277
at ListViewSample.SimpleListViewSample.SimpleListViewSample_obj10_Bindings.DataContextChangedHandler(FrameworkElement sender, DataContextChangedEventArgs args) in C:\dev\Windows-universal-samples-master\Windows-universal-samples-master\Samples\XamlListView\cs\obj\x64\Debug\Samples\SimpleListViewSample\SimpleListViewSample.g.cs:line 230
This happens because the Key is of type Char and the TextBox cannot bind this.  The fix is in Contacts.cs, at line 116, simply change the g.GroupName type to string as you store it in info.Key
         //   info.Key = g.GroupName;
               info.Key = g.GroupName.ToString();

Thanks for the diagnosis. Will fold this fix into the update v5.0.4.


Fixed one hell of typos and unified indentation and strings

Thanks for the help, I found it easier to merge these changes with my latest set of commits (since I'm foolishly tackling this from mobile). All respective credit was given through mattata's official Telegram channel.

 Why is your comment und my name?? Is GitHub broken?

Also, I still would suggest to properly merge this pull request. I standardized all strings to use single quotes while respecting already escaped double quotes as well as the need to escape single quotes. Tabs and spaces were used irregularly, too, so I also got rid of that.


Merge master into VanDerCorput Sequence (#37)

This PR merges current master into #37 (VanDerCorput Sequence) resolving conflicts.

This change is

Changes Unknown when pulling 0f2d3203928ca50045a2fec64c4a56216a5cbd0f on feature/vandercorput_merge_master into ** on feature/vandercorput**.

@ClintLiddick Could you take a look at this PR? I hope this resolves the conflicts without changing the intention of #37.

This looks good to me. I remember the code and the tests, and all makes sense/passes. :+1:


Error: webpack:///(webpack)/buildin/harmony-module.js?:39

Big brother, I also want to ask you a question, that is, when I pack vue, configuration error, can you help me solve it? ，please help me. thank you very much!
Address at https://github.com/webfrontup/mini-webpack/tree/vueproBuild
some bad message
Html Webpack Plugin:
  Error: webpack:///(webpack)/buildin/harmony-module.js?:39
  /* WEBPACK VAR INJECTION */}.call(this, __webpack_require__(/*! ./harmony-module.js */ "./node_modules/webpack/buildin/harmony-module.js")(modul  e)))
                                                                                ^
  TypeError: __webpack_require__(...) is not a function

  - index.html:2778 Module../node_modules/webpack/buildin/harmony-module.js
    /Users/saoshuai/newbee/provue/index.html:2778:1

  - index.html:684 __webpack_require__
    /Users/saoshuai/newbee/provue/index.html:684:30

  - index.html:61 fn
    /Users/saoshuai/newbee/provue/index.html:61:20

  - index.html:2766 Module../node_modules/webpack/buildin/global.js
    /Users/saoshuai/newbee/provue/index.html:2766:1

  - index.html:684 __webpack_require__
    /Users/saoshuai/newbee/provue/index.html:684:30

  - index.html:61 fn
    /Users/saoshuai/newbee/provue/index.html:61:20

  - lodash.js?:17101 eval
    [.]/[lodash]/lodash.js?:17101:41

  - index.html:2754 Object../node_modules/lodash/lodash.js
    /Users/saoshuai/newbee/provue/index.html:2754:1

Please help me !!!!!! Thank you very much~~~~

Hi, I just cloned your repo and ran both the dev and prod scripts and both ran without error.
You might be using different package versions that I am though, I think you should add the package-lock.json to your repo so I can get the same versions as you.

thanks immediately

Same question： I uploaded my package.json file
https://github.com/webfrontup/mini-webpack/tree/vueproBuild

vueproBuild

vueproBuild
On the vueproBuild branch

OK, the errors I am seeing are all related to scss variables. You have a lot of variables declared in skin.scss, in every component where they are used you need to import that file.

Are you sure?  at index.js , the code is this
import Vue from 'vue'
import App from './App.vue'
import router from './router'
import VueLazyload from 'vue-lazyload'
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
Vue.use(VueLazyload, {
    error: require('./assets/img/error_img.png'),
    loading: require('./assets/img/icon_loadingimage.gif')
  })

I have introduced skin.scss globally, and I have solved the error reporting of the variable you mentioned. What I have encountered is the problem behind this problem

Found it, the issue is in webpack.config.base.js, in the loader for .js files where it uses babel-loader, add this after the test node:
exclude: /node_modules/,

{
				test: /\.js$/,
				use: {
                    loader: "babel-loader",
					options: {
						//预设
						presets: ["@babel/preset-env"],
						//插件
						plugins: ["@babel/plugin-syntax-dynamic-import"]
                    },
                    exclude: /node_modules/
				}
			},

like this, Unable to run, error reported
npm ERR<EMAIL_ADDRESS>dev: `webpack-dev-server --progress --config build/webpack.config.dev.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.

Found it, the issue is in webpack.config.base.js, in the loader for .js files where it uses babel-loader, add this after the test node:
exclude: /node_modules/,

Oh, my god. did you pack it? How do I configure it, except for node_modules

Webpack ran in both dev and prod, I got errors in the app but they appeared to be more application errors than webpack.
Adding that line is fine, everything in node_modules is already packaged for use so doesn't need to go through babel. It's an oversight on my part and I have updated the template project to include this.

thank you very much!  It`s success!
I don't even know why. It's amazing. Good sense of achievement

Webpack ran in both dev and prod, I got errors in the app but they appeared to be more application errors than webpack.
Adding that line is fine, everything in node_modules is already packaged for use so doesn't need to go through babel. It's an oversight on my part and I have updated the template project to include this.

 Please enable it to continue.

Hi, sorry I don't have time to help any further on this, good luck with your project.


Feedback Ticket

First steps of feedback
Subscription for secured information?
No Private information will be saved for users, only accessible by our team and antonia, through secure log in.
Process feedback-
How can we improve our process and efficiencies
They enjoy how we are incorporating zillow into our website as it incorporates key information into our website about real estate
Additional ideas-
improved aesthetic to beat the competition and attract the customers


CE Enchant duplication, CE book and lore not match, CE performance probem

1 CE enchant will duplicate itself when a new CE enchant is added in or restart server
2 CE book lore does not match CE books' name usually occurs when server is restarted.
3 CE is installing too much listener on players? if the server have too many players , listeners will stress the server ram and cpu alot, it uses so much ram and makes the cpu and java need to frequently do garbage collections
Paper 1.15.2 324
CE DEV 1.15.2 8.1 #150
There is no error message shown in log
However, timings do show CE heavy load
https://cdn.discordapp.com/attachments/696002416239444008/740524264784134255/m.png

Added to our new bug tracker.


[SUPPORT]org.apache.hudi.utilities.HoodieCleaner cleanup, but spark-submit don't quit

use org.apache.hudi.utilities.hoodieCleaner realize asynchronous cleaning, after the completion of the spark-submit don't quit, need  CTRL + c to exit
/opt/spark-3.2.2-bin-3.0.0-cdh6.2.1/bin/spark-submit \
--class org.apache.hudi.utilities.HoodieCleaner \
--jars /opt/hudi-utilities-bundle_2.12-0.12.1.jar \
/opt/hudi-utilities-bundle_2.12-0.12.1.jar \
--target-base-path /db/dwm_http_scan \
--spark-master yarn \
--hoodie-conf hoodie.cleaner.policy=KEEP_LATEST_BY_HOURS \
--hoodie-conf hoodie.cleaner.hours.retained=1

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.12.1

Spark version : 3.2.2

Hive version : 2.1.1

Hadoop version : 3.0.0

Storage (HDFS/S3/GCS..) : HDFS

Running on Docker? (yes/no) : no

Additional context
Add any other context about the problem here.
Stacktrace

Add the stacktrace of the error.

sure, will look into it.
https://issues.apache.org/jira/browse/HUDI-5065
thanks for reporting.


"Error: Unprocessable Entity" response for Tutorial -> FastAPI Body - Nested Models -> Bodies of arbitrary dicts

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from fastapi import FastAPI

app = FastAPI()

@app.post("/index-weights/")
async def create_index_weights(weights: dict[int, float]):
    return weights

Description

Just copy and run the sample code provided by official doc,
It should return a 200 response for this request:

{
  "test":{
    "1":"3.14"
  }
}

Operating System
macOS
Operating System Details
No response
FastAPI Version
0.88.0
Python Version
Python 3.10.8
Additional Context
I have tried many other possible 'answers' to the endpoint but didn't worked.

As per docs - "In this case, you would accept any dict as long as it has int keys with float values"
You have to pass in a dict of int and float. You are passing in a dict of str, float and int
For the example to work you need to pass:
Works:
{   "1" : 3.44 }
Doesn't work
{   "one" : 3.44 }


[WIP] Ansible integeration

This PR is intended to implement the design
https://github.com/open-cluster-management/backlog/issues/4555
This PR will changes:
1, the CRD updates, since we are going to add the prehook/posthook to SubscriptionSpec as optional fields.
2, refactor of some utils functions in order to reuse them for git related options(such as download, sort, parse YAMLs from git source)
3, defined an Hookprocessor interface for the pre/post Hook, the Hookprocessor will be used by the ReconcileSubscription for handling the pre/posthook logic
4, refactor the constructor of the ReconcileSubscription to accommodate the Hookprocessor
Need to be done:
1, update the subscription status to mirror the ansible job status
2, how to avoid reconcile that come from the subscription status change
3, how to tell if the subscription is actually deployed to the managed clusters
If you have any suggestions, please let me know.
Also, the following lib is used to define the ansibleJob spec. In addition, the following lib has a running controller, which can update the ansbilejob status based on certain annotation. You can use it to do test.
https://github.com/open-cluster-management/ansiblejob-go-lib

DegisterSubscription -> DeregisterSubscription ?

Yup, good catch


Missing checks in API response

Describe the bug
While comparing the scoring with the API:

Request1: Nodejs (bd31d489615b424202553ffe1a5093a19d5e5e1f)
Request2: Nodejs (1fbd908497ece0c5b08c7cc8f7494d7a12e7001f)

In the Request2 the payload does not include all the checks, for example "CI-Tests" is missing inside the checks.
Reproduction steps
Steps to reproduce the behavior:

You can check this in action at: https://kooltheba.github.io/openssf-scorecard-api-visualizer/#/projects/github.com/nodejs/nodejs.org/compare/1fbd908497ece0c5b08c7cc8f7494d7a12e7001f/bd31d489615b424202553ffe1a5093a19d5e5e1f (explore the network request in the chrome dev tools) or do the HTTP request directly in the browser and compare the payloads

Expected behavior
I will expect both payloads to include all the checks included in the scorecard, or at least an error code that explains this behaviour, so the API consumers can control the error.
Additional context
This bug is affecting:

openssf-scorecard-api-visualizer cc: @kooltheba
OpenSSF Scorecard Monitor

I believe this is a matter of where the result is sourced. The API pulls from the GitHub action published results if available, or the weekly cron if not.
https://github.com/ossf/scorecard-webapp/blob/e7be60069b18df32c7d3b003dd9daca6a622e6c5/app/server/get_results.go#L70-L88
diff checks1 checks2
4d3
< "CI-Tests"
6d4
< "Contributors"
8d5
< "Dependency-Update-Tool"

These are the checks disabled in the weekly cron:
https://github.com/ossf/scorecard/blob/b68ef18c9691a7be16dbbc60c32cd736dd372d1d/cron/config/config.yaml#L48
The output is basically tied to the checks requested, so
scorecard --repo foo/bar --checks Vulnerabilities

will only have the Vulnerabilities check in its result. Which is why those 3 are missing.
Your second request comes from before the action was installed, so there's no other data to grab.
I believe this is working as intended.

Thanks @spencerschrock this makes sense! Thanks for the complete response 👍


Convert to Glimmer components, drop block form support

@ijlee2 I added a code-base component to extend from, since our components code was identical. I also removed all the old code in favor of the new stuff and fixed the acceptance test. It looks like the only thing left to fix is the test checking if the code updates. It does not seem to update when the content is updated. Mind taking a look?

@ijlee2 I ultimately decided to remove support for the block form, and require passing code all the time.

@ijlee2 any ideas why 3.12 is failing? I'm not sure what version started supporting colocated components.

Hi, @rwwagner90. Thanks for reaching out to me for feedback and continuing the work on converting to Glimmer components! I saw updates to tests and readme as well, much appreciate your working on them.
I'm not too familiar with addon history (only recently got into making one). From a recent Discord chat, it looks like colocation works for addons starting 3.13. Can you try updating the ember-try scenario from 3.12 to 3.13?
With regards to your two recent commits, I think I'd provide three feedback:
1. I agree that we could practice inheritance for <CodeBlock> and <CodeInline>, but only because the backing classes are currently the same. In general, for components, I think I'd prefer to avoid inheritance in favor of duplication or composition. In apps, at least (I lack experience with addons), I feel like a business requirement for a component can change often, so it's better to avoid inheriting early.
2. I'm personally okay with removing the block form for <CodeBlock> and making a breaking change. Off the top of my head, I'm not sure how to listen to a change in the block content and recreate the <div> element (this.blockElement) in order to recalculate this.code. (That's a lot of side effects! 😄) Hopefully, not many people are using the block form. Asking people to migrate to always using @code seems reasonable to me.
3. For <CodeBlock>, I think it may be better to apply ...attributes to the <code> element. Currently, I can't think of a use case where it's better to apply style to the <pre> element. If we apply ...attributes to <code>, we could reuse <CodeInline>:
{{!-- addon/components/code-block.hbs --}}
<pre
  class="code-block {{this.languageClass}} {{if @showLineNumbers "line-numbers"}}"
>
  {{~! ~}}
  <CodeInline
    @code={{@code}}
    @language={{@language}}
    ...attributes
  />
  {{~! ~}}
</pre>

The composition would also allow us to remove inheriting CodeBase class.

@ijlee2 thanks for that detailed feedback! I applied your suggestions about reusing the <CodeInline/> component inside the <CodeBlock/> template and removing the base class.
Are we okay with dropping support for Ember < 3.13? I suppose it's close enough to the 3.12 default.

Hmm, it's up to you. I think there's merit to keeping the old component structure, so that you can support 3.12 LTS users for a few more months (based on https://emberjs.com/releases/lts/, it seems 3.12 support is dropped on October 1).

@ijlee2 I would be fine moving components to the old structure, but I tried that and it didn't work either. Maybe I did something wrong. Want to take a stab at moving back to classic structure?

@rwwagner90 Yep, if I have time before Wednesday evening (CST), I'll have a look. If not, please feel free to go with 3.13.

I tried reverting the component folder structure and export statements in app/components, but the tests (for <CodeBlock> only, maybe?) continued to fail when I ran ember try:one ember-lts-3.12.
I now think it's okay to up the minimum support version to 3.13 while we make a breaking change with dropping block form support.

Thanks @ijlee2. I agree. No point in spending a ton of time supporting 3.12.


Allow property values to be null when creating an edge

OrientDB Version: orientdb-community-2.2.17
Java Version: 1.7.0_91
OS: centOS 06
Seems like orientDB intentionally does not allow for properly values to be null when creating an edge.
in OrientElement.java:

    if (settings.isStandardElementConstraints() && null == value)
          throw ExceptionFactory.propertyValueCanNotBeNull();

This issue was pointed out before in issue #3365. Some workarounds have been suggested in this original ticket.  Not sending the property at all or altering the standardElementConstraints are as such:
alter database custom standardElementConstraints=false

However, the first workaround is not an optimal solution for us (i.e. not sending the property at all).
We preferably do not want to alter the "standardElementConstraints" as it requires us to do this for every test db and make it part of the server connection. We are also worries about the possible side effects of altering the "standardElementConstraints".
It would be great if a feature could be added to allow us to turn off the null constraint without having to set "standardElementConstraints" and turn off all blueprint checks.

Hi @amirmhzadeh
Unfortunately that constraint is part of Apache TinkerPop standard, so as long as you use TP the only way to disable it is to set standardElementConstraints to false.
In V 3.0 we will have a core multi-model API with graph capabilities that does not have this limitation, but in 2.2 there is no alternative unfortunately.
Thanks
Luigi


adding drum kit project

I want to add my project. please assign me this issue.

pls assign me this @Seew0


remove env provers

Codecov Report

Merging #574 (f49f309) into main (6a860dd) will increase coverage by 0.28%.
The diff coverage is 69.28%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##             main     #574      +/-   ##
==========================================
+ Coverage   28.66%   28.94%   +0.28%
==========================================
  Files          53       53
  Lines       21367    21380      +13
==========================================
+ Hits         6125     6189      +64
+ Misses      15242    15191      -51

Flag
Coverage Δ

test
28.94% <69.28%> (+0.28%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/database/mod.rs
92.81% <ø> (-0.24%)
:arrow_down:

src/prover/batch_insertion/mod.rs
99.13% <ø> (+0.28%)
:arrow_up:

tests/common/mod.rs
39.34% <28.12%> (+3.24%)
:arrow_up:

tests/insert_identity_and_proofs.rs
99.59% <97.43%> (-0.41%)
:arrow_down:

src/app.rs
74.31% <100.00%> (-3.99%)
:arrow_down:

src/task_monitor/tasks/process_identities.rs
95.36% <100.00%> (+3.09%)
:arrow_up:

tests/dynamic_batch_sizes.rs
99.50% <100.00%> (-0.01%)
:arrow_down:

tests/malformed_payload.rs
100.00% <100.00%> (ø)

tests/multi_prover.rs
100.00% <100.00%> (ø)

tests/unavailable_prover.rs
100.00% <100.00%> (ø)

... and 1 more

... and 4 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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