audio sources not showing

Trying use this plugin to change audio output sources, but the dropdowns on any audio related action are not populated. What info can i provide to things can i do to check.

Disregard, i clicked the releases and downloaded the most recent one thinking that was it "main" but that was incorrect, downloaded the v1.0 pre-release one and that works.


Things to do on 0.2.22 release

Improve the wiki page
Right now, this isn't linking into the examples as much as it could. It is instead providing relative paths.
Once we make a new release (and thus push develop to master) we can then link to the correct examples in the master branch.
Did it

Make a new release for the tts_netflow_b repo to take advantage of the better clone functionality vis-a-vis adding adding and deleting tables/fields.

Make a new release of tts_diet, tts_netflow_a, tts_netflow_b to include the tooltips for the input and solution schemas.

Update ticdat status wiki page

Update docs. Instructions here

Make sure you have pydocmd installed ("pip install pydoc-markdown")
Checkout the branch you want to use the documentation on
CD to the "docs" folder.
run "pydocmd build"
run "pydocmd gh-deploy"
When it's done running the "gh-pages" branch of ticdat should have been updated.

Closing, but this issue is handy for review later.


erase on iterators

Trees should provide erase on iterators, returning the next iterator, for consistency with other containers.
The alternative is to use remove, but that's not compatible with algorithms.

Might also consider add erase_and_dispose in boost intrusive style.

You are right. I added erasing by iterator in https://github.com/tinloaf/ygg/commit/e073e6358ffe44416dcf776f3b9f4459f828f60f
I'm hesitant to also allow erasing by const_iterator - in an intrusive tree, erasure changes the underlying node, thus I would have to cast away constness there. Does this solve your problem?

erase should return the iterator to the next element

You are right - Ygg deviates from STL in this regard. Returning an iterator to the next element introduces a (small, but still…) performance penalty. Thus I'm reluctant to add that as a default.
I have added a TreeFlag named STL_ERASE which will make the erase() methods adhere to STL standards - returning an iterator to the next element, etc. Does that help you?

I'll assume that the STL_ERASE option solved your problem. If you still experience problems, feel free to reopen this resp. create a new issue. Thanks for reporting!


feat: support custom telegram bot api

in some cases, we need to use custom telegram apis.
ref: https://core.telegram.org/bots/api#using-a-local-bot-api-server

@Hentioe

Great, I'll make some simple changes and merge soon.

I modified and rebased your commit and merged it into the master branch. Because GitHub doesn't recognize it automatically, I will close this PR manually.


Replace server-side API library for web implementations

Problem
This package currently uses the server-side library for all API calls. This works fine on iOS/Android, but causes CORS errors on web.
See this thread:
googlemaps/google-maps-services-js#59
Solution
Replace with client library for web implementations
https://developers.google.com/maps/documentation/javascript/tutorial

One of the great things about this library, in my opinion, is that it doesn't require any of the Google SDK's in order to work.  React Native is a non-web browser platform first.  Adding the Javascript SDK to it seems a little counter intuitive to me.
My 2¢

I'm open to other suggestions on how to do it, but the fact of the matter is that this implementation throws CORS errors on web. Based on my read of google's docs, this is because they force you to use the JS SDK for browser implementations.
A big part of RN's value prop is reusability of code / lower maintenance. RN usage on web is increasing rapidly, and dependencies like this need to support web-specific minutiae. Even if the primary usage of RN is still non-web, dependencies shouldn't treat web implementations as second-class citizens.
Now, it's certainly possible that the CORS errors are popping up for another reason.... but after weeks of troubleshooting I'm pretty convinced that it's down to how google treats browser usage. I found a workaround using CORS-anywhere, but this isn't a good long-term solution.

RN usage on web is increasing rapidly, and dependencies like this need to support web-specific minutiae. Even if the primary usage of RN is still non-web, dependencies shouldn't treat web implementations as second-class citizens.

While I agree with you that this is where RN is trying to head, all the web implementation have come from outside RN itself.  At the moment, there isn't robust support for React Native on the web, it is still sort of one giant hack.  I'm not sure it's fair to say that open-source libraries which are built around RN are treating the web as second class citizens because they don't support this.  I see web support as a feature which has to be evaluated for its merits for each project individually. (Full disclosure, I use RNW pretty heavily at work, so I am pretty aware of the pain points).
That all being said, I do think there is merit in allowing a prop to be set to determine where the request should be sent (by default to the google api).  This sort of meets web support halfway.  It will require having the backend setup to handle this, which may not be helpful to beginners, or people who can't/don't want to setup a server to pass along the requests. It is still a hack, because now you would have to send the query to the server, who send it to google who sends it back to the server which send it back to the client. This would also open up the possibility of using a data provider other than google.  This way we don't have to include any SDKs in the library.
If you have any implantation that you are thinking of, feel free to details it here (or open a PR).

Let me take a look and see if I can put something together.
Not sure if this is out of scope, but that prop could also theoretically allow people to pass requests to open source autocomplete engines.

And maybe "second-class citizen" was strong wording -- I guess I generally feel that to the extent possible, projects should include the most robust web support that they can. Even if RNW has a number of problems, we should be trying to build out the OSS infrastructure to support it. As you said, it's kind of a giant hack... and I'd rather not hack more things than I need to.

And maybe "second-class citizen" was strong wording -- I guess I generally feel that to the extent possible, projects should include the most robust web support that they can. Even if RNW has a number of problems, we should be trying to build out the OSS infrastructure to support it. As you said, it's kind of a giant hack... and I'd rather not hack more things than I need to.

No worries.

Let me take a look and see if I can put something together.
Not sure if this is out of scope, but that prop could also theoretically allow people to pass requests to open source autocomplete engines.

Thanks!  No, definitely not out of scope, I think that providing that flexibility is key.
Thinking about this programmatically, allowing the prop to accept any URL  makes the library more flexible as a whole, instead of just coding against a specific problem.
It looks like this is basically implemented in #514. I'll have to take a look at it.  There may need to be some changes around error handling, i'll see when I test it out.

I spent a some time thinking about this and doing some testing.  Bottom line, I don't know of a way to get around the CORS requirements of the browser without adding the Javascript SDK.
At this point I will look into merging some of form of #514 which would make this compatible with the web if you pass in your own URL.  I will do a a platform check, and if the remoteURL prop is not set then we will return an error. I will have to create doc explaining how this all works with some pointers about getting started with a proxy server. I would love some help with this, if someone can put in a PR that would help get this out faster.

Yeah, that makes sense.
Definitely an antipattern, but a quick-and-dirty hack is just to preface the URL with "https://cors-anywhere.herokuapp.com/".

Have you tried that as a permanent solution?  I was under the impression it only works for a bit until it is rate limited.
I created a new branch, you can follow along there. Feel free to chime in, or take a task off the project board as a PR.

I used it for ~1.5 months in a production environment before setting up my own proxy server.
I didn't experience any problems, but we were only working with ~1500 users and comfortably < 1 call / user / day. I can't speak to high request volume...

I used it for ~1.5 months in a production environment before setting up my own proxy server.

Cool!  I don't think I want to code it into the app (yet - although it would be something to consider enableing in development mode).

@hthillman can you take a look at the PR?

Yes! Will take a look first thing tomorrow.
On Mon, May 11, 2020 at 4:47 PM Steven Bell<EMAIL_ADDRESS>wrote:

@hthillman https://github.com/hthillman can you take a look at the PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FaridSafi/react-native-google-places-autocomplete/issues/525#issuecomment-627024718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIR5IWFXMNBIBHYYYNTFSBTRRCFAJANCNFSM4MCUCY2Q
.

--
Hunter Hillman
Co-Founder, Kinder Inc.
401.932.7606

ping @hthillman

Sorry, got totally sidetracked. Reviewing late tonight and will have
comments (if any) morning PT
On Tue, May 12, 2020 at 5:27 PM Steven Bell<EMAIL_ADDRESS>wrote:

ping @hthillman https://github.com/hthillman
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FaridSafi/react-native-google-places-autocomplete/issues/525#issuecomment-627670609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIR5IWDVYECM3Y6YP2JREL3RRHSODANCNFSM4MCUCY2Q
.

--
Hunter Hillman
Co-Founder, Kinder Inc.
401.932.7606

Thanks!

Reviewed!

Very well explained and a great solution to prevent loading useless files from Google. We are using another JS framework but this is quite helpful, thanks.


Running of Program

Hi Michael,
I have been trying to run your program from a different set of ways. Could you possible provide a comprehensive list of step by step commands(which includes pre-reqs such as kotlin) that I can use to execute the program?

Hi,
what exactly do you want to achieve? Do you want to use the library in a project of yours or do you just want to provide a data set to the algorithm?
If you want to use the library as part of your own program, the easiest way is to include it as a Maven or Gradle dependency as stated in the Readme. If you don't use a build management tool, you can also download the latest jar file from the "releases" section of this Github page and add it to your project's classpath.
If you just want to provide some data set to the algorithm to see how it works, the easiest way would be to checkout the source code and built it from with the IDE of your choice. The project uses Gradle for dependency management so all required dependency should automatically be fetched. There are some small example datasets included to be used by the JUnit tests. Just run these tests to see how things work. As this project is intended to be used as a library, there is no main class provided to run the algorithm as standalone.

Hello,
I am trying trying to use the library to apply in my data set. I followed the instruction on Searching frequent item sets. using a minimum support and i have also implemented the DataIterator class and the Named Item class.
However, I am getting the error "Failed to  open file".  I cannot access my text file. Can you please provide an instruction on how to access text file and is there a specific location where should I put my text file?
I am new to Kotlin and I cannot find a solution online. I would really appreciate the help!


(1.12) Pkgpanda: Copy systemd unit files instead of symlinking

High-level description
This is a 1.12 port of #2383.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-1587 Support DC/OS install on non-root LVM volume

Checklist for all PRs

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label shipit


📫 Send kOps cluster alerts to PagerDuty

I keep receiving emails from CloudWatch about Alpha and Dev clusters e.g. "ALARM: "alpha-kubernetes-master-alerts_api-alpha-surge-queue-length-alarm" in EU (Ireland)", we should send these to PagerDuty analytical-platform-compute service

😿 https://github.com/ministryofjustice/analytics-platform-ops/blob/main/infra/terraform/platform/modules/sns_alerts/sns.tf


Update parseoperator.md

Fix punctuation in kusto query examples

@triangularcover : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@triangularcover Thanks for your feedback. We're submitting your suggestion, and the updated article should be live by tomorrow. Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.

FYI: @orspod
#sign-off

@shsagir: I'm sorry - only the author of this article, @orspod, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


could not execute all movements successfully, did not grasp anything and could not reach target location

how can I deal with the problem of "could not execute all movements successfully, and did not grasp anything, and  could not reach target location " when training, I am trained with the file of Grasping_Agent_multidiscrete.py,
 appreciate very much.

@PaulDanielML  thank you very much!!!

i am train with the file of Grasping_Agent_multidiscrete.py

could anyone give me some solution to fix this , thanks very much.

Did you solve it? I had the same problem

this is not an error, just an arm manipulation output log, means this step could not finish the task.

this is not an error, just an arm manipulation output log, means this step could not finish the task.

i think u can give a larger "max_steps" for the arm to find a solution.


Bootstrap support in yii\jui\DatePicker

I have to use
<?= $form->field($model,'activeUntilDate')->widget(DatePicker::className(),['clientOptions' => ['dateFormat' => 'yy-mm-dd'], 'options' => ['class' => 'form-control']]) ?>

to produce themed output.
Eg. default behavior:

Themed look:

The masked text field is implemented based on the
jQuery input masked plugin.
and has
public $options = ['class' => 'form-control'];

by default
Shouldn't all jui widgets be ported to yii widgets or used only from jui?


Self-nomination as tooling contributor

In keeping with the Paketo Buildpacks Governance document, I am self-nominating as a contributor to the Tooling subteam.
I have recently contributed:

work on the Serve() matcher in occam: https://github.com/paketo-buildpacks/occam/pull/75
changing fs.Sum() to accept variadic args: https://github.com/paketo-buildpacks/packit/pull/90
builders' shared workflows to github-config: https://github.com/paketo-buildpacks/github-config/pull/228
commit signing capability to the create-commit action: https://github.com/paketo-buildpacks/github-config/pull/229
actions checking for human commits and unverified commits on PRs: https://github.com/paketo-buildpacks/github-config/pull/219

Approved! @fg-j you should now have Contributor status across all of the Tooling repos in the paketo-buildpacks and paketo-community organizations.


Add -A x64 to the cmake command not -A 64

Compile on Windows
Add -A 64 to the cmake command
This sentence may have been a clerical error.
Try this：
cmake -DUSE_CUDA=ON -DCUDA_TOOLKIT_ROOT="E:/Program Files/NVIDIA GPU Computing Toolkit/CUDA" -DGPU_ARCH=M -A x64 ..
Replace "E:/Program Files/NVIDIA GPU Computing Toolkit/CUDA" with yours own CUDA directory.
It generated a visual studio project on windows.

Thanks for the correction, we'll update the document.


grpc fails to compile on windows under arm64 architecture

What version of gRPC and what language are you using?
At the time of writing, I've tried both the latest released version (v1.30.0) and the latest master (e4973325a07f576951eea40dc079e4bade0b0f0d)
What operating system (Linux, Windows,...) and version?
Host machine is Windows 10 - x64
I'm building for Windows 10 - arm64
What runtime / compiler are you using (e.g. python version or version of gcc)
I'm currently using cmake which is compiling with msvc. I'm using cmake version 3.17.0, and Visual Studio 2019
What did you do?
// Create a build folder
cd grpc; mkdir build-arm64; cd build-arm64

// Configure. This step works fine.
cmake -A ARM64 ..

// Build. I'm only building the crypto / ssl targets because the issue seems to be local to boringssl
cmake --build . --target crypto ssl

What did you expect to see?
$ cmake --build . --target crypto ssl
Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  crypto.vcxproj -> grpc\.build-arm64\third_party\boringssl-with-bazel\Debug\crypto.lib

Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  ssl.vcxproj -> grpc\.build-arm64\third_party\boringssl-with-bazel\Debug\ssl.lib

(This is what it looks like after I successfully compile for x64 on Windows)
What did you see instead?
$ cmake --build . --target ssl
Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  Building Custom Rule grpc/third_party/boringssl-with-bazel/CMakeLists.txt
  bio_ssl.cc
grpc\third_party\boringssl-with-bazel\src\include\openssl/base.h(122,1): fatal error C1189: #error:  "Unknown target CPU" [grpc\.build-arm\third_party\boringssl-with-bazel\ssl.vcxproj]
  d1_both.cc
grpc\third_party\boringssl-with-bazel\src\include\openssl/base.h(122,1): fatal error C1189: #error:  "Unknown target CPU" [grpc\.build-arm\third_party\boringssl-with-bazel\ssl.vcxproj]
  d1_lib.cc

...

Anything else we should know about your project / environment?

If I omit the -A ARM64 argument (which defaults to x64 on my computer), everything builds perfectly.

From looking at base.h, it looks like __aarch64__ or __arm64__ should be defined, but it's not.

Max

That's technically not on us, but on BoringSSL. @agl, what would be the proper location for these sort of issues?

fwiw, it looks like these patches will fix it: https://github.com/microsoft/winrtc/blob/master/patches_for_WebRTC_org/m80/6401-Arm64-is-a-thing-and-has-intrinsic-to-mul-two-64bit-.patch
Max

The BoringSSL bug tracker is https://bugs.chromium.org/p/boringssl/issues/list
In this case I don't want to look at the linked patch because it's not being submitted under CLA. Aarch64 Windows is not a platform that we have any ability to build, but it sounds like gRPC would like it supported? I'll make the obvious change that should clear the “unknown target CPU” error, but I don't know if what results will be functional. Maybe, once I do that, someone here can build and run tests?

https://boringssl-review.googlesource.com/c/boringssl/+/41945 to do the obvious fix.

That's the fix I tried originally, but it will fail with an error saying "BN_UMULT_LOHI" is not defined

fwiw, I think BN_UMULT_LOHI just needs to be defined for arm64 when building for Windows as it does have an equivalent built-in.

That's the fix I tried originally, but it will fail with an error saying "BN_UMULT_LOHI" is not defined

Thanks. Could you try out the latest version of the same change? (Am coding blind here.)
At best, this will get the NO_ASM version building, but that might be sufficient for gRPC. We'll (i.e. BoringSSL) will look into whether we want to fully support this platform, buy hardware, etc.

I've blindly attempted a fix in the referenced change.

By the way, regarding our willingness to support AArch64: we don't mind accepting patches to increase compatibility, but we don't want to make any promises, given the poor testability.

@maxweisel  is this still an issue? We've upgraded the boringssl version we use several times since this issue was filed, so the boringssl fix @agl has accepted is already in place under third_party/boringssl and there's a good chance that the windows arm64 build already works.
One possible workaround is to not use boringssl in your cmake build, but instead depend on a pre-installed version of OpenSSL.
See https://github.com/grpc/grpc/blob/0e20a5fce8e53510255fa1a5199544a86ebfcd8e/test/distrib/cpp/run_distrib_test_cmake.bat#L26 and https://github.com/grpc/grpc/blob/0e20a5fce8e53510255fa1a5199544a86ebfcd8e/test/distrib/cpp/run_distrib_test_cmake.bat#L85 for how to depend on a pre-installed version of OpenSSL instead of building boringssl from source.

I'm going to close this issue since:

there's a good chance that the original issue has already been fixed
the workaround is to build without boringssl and use openssl instead (by setting -DgRPC_SSL_PROVIDER=package)
we don't support win arm64 officially anyway


Support for .NET Core v3

I want to use this package. But when i tried to use it on my project (which use .NET Core v3) it doesn't work, it gives error:
Could not load file or assembly 'System.ComponentModel.Annotations, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
it still work perfectly tho if i don't use any annotations in my model.

I had the same problem. I simply remove all annotations from models that related on System.ComponentModel. Thats not a solution but workaround.


Value converter is not firing

I have the following lambda converter:
    public static readonly IValueConverter SignalStrengthImage = ValueConverter.Create<int, string>(e =>
    {
        logger.Info("wtf");
        var root = "pack://application:,,,/MyLibrary;component";
        var path = $"{root}/assets/signal_strength_unknown.png";
        switch ((int)e.Value)
        {
            case 0: path = $"{root}/assets/signal_strength_0.png"; break;
            case int n when n <= 20: path = $"{root}/assets/signal_strength_20.png"; break;
            case int n when n <= 40: path = $"{root}/assets/signal_strength_40.png"; break;
            case int n when n <= 60: path = $"{root}/assets/signal_strength_60.png"; break;
            case int n when n <= 80: path = $"{root}/assets/signal_strength_80.png"; break;
            default: path = $"{root}/assets/signal_strength_100.png"; break;
        }
        return path;
    });

With the corresponding xaml:
    <Image Source="{Binding Status.SignalStrength, Converter={x:Static c:Converters.SignalStrengthImage}, FallbackValue={StaticResource UnknownSignalStrength}}" Width="70" Height="70"/>

Unfortunately, the converter seems as though it is never called.  When the property on the viewmodel is updated, the Image goes from displaying the fallback image to displaying nothing.  The log statement in the converter is never fired, and if I set a breakpoint it is never reached.
If I create a normal IValueConverter class the traditional way, with the exact same code, it works properly.

Is the property Status.SignalStrength of type int/Int32?

Yes, I found the problem, in Converter, there's an IsAssignable check on targetType.  Normally this makes sense, but the case of Source on <Image is different.  The type is ImageSource but if you pass in a string that is a path to a resource image, the property handles it correctly.


MOTR-154 Internal Patch Release Candidate Fixes

Key Changes:

Updated metadata for documentation UI rendering in each of the releases.

Merged MOTR-154


Merge stable back into master

@Patrick1904 @picturepan2 may you help resolving conflicts here?

@Patrick1904 @picturepan2 may you help resolving conflicts here?

@vgrichina I added this PR instead so none of the translations in this PR are needed.

@Patrick1904 we still need to merge this PR to resolve conflicts between stable and master
Otherwise we'll have conflicts merging to stable as we do have here:
https://github.com/near/near-wallet/pull/1390


Improve Android button appearances (closes #849, #896)

This implements proper behavior for Material Design flat buttons and icon toggles - these buttons ripple as soon as the touch starts. Conveniently, React Native supports masking these ripples to the parent View's border radius. This also fixes a breakage introduced in #808 that closes #896.
This does not completely fix the ripples for regular buttons with rounded corners. However, once React Native actually supports masking bounded ripples (likely if something like facebook/react-native#6515 is reimplemented) they should be fixed here as well.
This also fixes a bug where if you click on a child of the button, the ripple origin is misplaced (see the gif of the before screen with the block button).
I have a demo repo if you want to see what I've tested so far.
Before:

Proposed:

I've also brought most the button stylings up to MD specs. The way ripple color is determined is as follows:

Use variables.androidRippleColorDark by default.
Use the background or androidRippleColor attributes above everything.
If the transparent prop is true, use the backgroundColor with alpha 0.26 from the styles prop
If the button is not transparent, use the light ripple color (variables.androidRippleColor) if the contrast ratio between backgroundColor and rgb(0, 0, 0) is less than 3:1.

I still need to test that this doesn't dramatically impact layouts and styles on iOS. I'll update with that here soon.

Ok, I just made a few adjustments and now iOS looks pretty good.
iOS before:

after:

@rockmacaca Looks great, but this breaks some of the others components. Like Bordered/Outline Button, left padding of Left Header Button seems more.

Do check you patch with demo app on NativeBase https://github.com/GeekyAnts/NativeBase-KitchenSink

Closing this due to breaking changes.
You can resolve the above mentioned issues and submit a new PR


Janlikar

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Ugh, I tried specifically to not send this to cargo, so closing.


Fix unused imports

This PR fixes the following error:
error: unused import: `psutil::sensors`
 --> src/widgets/temp.rs:2:5
  |
2 | use psutil::sensors;
  |     ^^^^^^^^^^^^^^^
  |
  = note: `-D unused-imports` implied by `-D warnings`

So it's actually only unused on macOS since temperatures aren't implemented on macOS yet. If you want you can make it so it's only imported on Linux to fix the linting.

So it's actually only unused on macOS since temperatures aren't implemented on macOS yet. If you want you can make it so it's only imported on Linux to fix the linting.

I had these same thought after my initial commit.  Please let me know if this looks good.  It now works on both Linux & macOS.

That looks good. If you could squash the commits then I can merge it.

That looks good. If you could squash the commits then I can merge it.

Thanks.  I've squashed the commits.

Nice, thanks!


removed unused code

removed unused code

:tada: This PR is included in version 0.33.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Plugins do not guard against invalid values in initialState

Plugins do not guard against invalid values passed through initialState in the same manner they do from method calls.
Because of interactions between different plugins, it might not be possible for the caller of useTable to know whether a given value is valid at the time initialState is defined either. For example, if there is an initial filter state, there's no easy way to validate a page index ahead of time.
Codesandbox Example
https://codesandbox.io/s/bold-wildflower-h0blz (kitchen sink example with initialState)
Steps To Reproduce

Pass invalid value(s) in initialState

Expected behavior
When consuming from initialState, the same validity checks and cleanup should occur as when state updates are triggered by method calls.
Examples of existing guarded behavior

usePagination's gotoPage will guard against a negative or out of bounds page from being set.
useFilter's setFilter and setAllFilters will automatically remove empty values based on filter.autoRemove

Not every plugin's method calls have such guards in place either (useRowSelect and useSortBy methods don't gracefully handle invalid column ids), but for ones that do, I think it might make sense for the same behavior to exist at the time of initialization or after a reset.

So if it’s invalid you would want a layoutEffect to happen and correct it with a new call to setState?

Since the existing guards happen at the reducer-level already, I was thinking it should go in the "___Reset" action of each plugin (the one triggered on mount by a useMountedLayoutEffect in the useInstance hook or by a reset method call), as that's where initialState gets consumed.
Using useFilters as an example, I was thinking it would look like something like this:
  if (action.type === actions.resetFilters) {
    return {
      ...state,
      filters: (instance.initialState.filters || []).filter(filter => {
        const column = allColumns.find(d => d.id === filter.id)
        const filterMethod = getFilterMethod(
          column.filter,
          userFilterTypes || {},
          filterTypes
        )

        if (
          shouldAutoRemoveFilter(filterMethod.autoRemove, filter.value, column)
        ) {
          return false
        }
        return true
      }),
    }
  }

But maybe without duplicating

Thinking about it some more... Maybe a more comprehensive solution would be to run a validation check after every state update, given that invalid state values could come from other places besides initialState, such as useControlledState or even another plugin's stateReducers hook.

This will likely be more "possible" in v8 given the internal state architecture changes. So let's wait until we get closer and discuss it again then.


Documentation update w.r.t. MAYA Garment Viewer

Hi,
I think some documentation is missing w.r.t. visualising sewing pattern in MAYA Garment viewer

Installation instructions point to a blob file and not the Instructions doc in main branch.
It directs user to add ./external to PYTHONPATH. It looks like ./external has been updated to ./pygarment.
It would help to include the location of the garment viewer script: ./gui/maya_garmentviewer.py

Hi @NagabhushanSN24

Yes, installation instructions point to Github web version of files for link stability (e.g. being accessible from pygarment page on PyPI)
and 3. Which documentation file are you referring to? Both questions are addressed in the documentation provided with GarmentCode: docs/Running_Maya_Qualoth.md


make this work

The existing configuration did not work due to 1 script error (?) and 1 unnecessary dependency. Now everything starts as intended.

hold off for a sec - more changes incoming.


python3.7.0+opencv_python<IP_ADDRESS>, "from .cv2 import *" says "DLL load failed:"

I install python3.7 and opencv-python <IP_ADDRESS> (using pip install), all are ok.
when "import cv2", it says:
Traceback (most recent call last):
File "", line 1, in
File "XXXX\lib\site-packages\cv2_init_.py", line 3, in
from .cv2 import *
ImportError: DLL load failed: could not find this module.
I read some solutions, but not resolved.
I install python3.6.3 and opencv-python <IP_ADDRESS> on the same windows 7. it runs ok.
That means, the os env could be ok.
any suguesstions?

Thanks. Resolved!
by #114, I download depends from http://www.dependencywalker.com/.
Shows:
API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL
PYTHON37.DLL
IESHIMS.DLL
Error open File.
Then, I compare the dependency of cv2.cp36-win32.pyd and cv2.cp37-win32.pyd.
may be API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL is missing on windows 7.
Download api-ms-win-downlevel-shlwapi-l1-1-0.dll from 'https://www.dll-files.com/api-ms-win-downlevel-shlwapi-l1-1-0.dll.html', choose x86 version.
copy it to C:\Windows\System32 and C:\Windows\SysWOW64.
And 'import cv2' is ok.
Thanks very much!

@tianxiawuzhe
Which version of the dll did you download?  There are 5 on the site!
Were using 32 or 64 bit Python 3.7?
I'm trying to port some Linux python code to windows 7, all the other pip installs seem fine, but I'm dead before I start without import cv2 working.
I've been given a 64-bit Windows 7 Professional machine to work with, so I've startedwith the 64-bit Python3.7

Followup.
I needed the 64-bit version 6.3.9600.16384:
https://www.dll-files.com/download/9cada7cc00753250c1beda32c23e22ee/api-ms-win-downlevel-shlwapi-l1-1-0.dll.html?c=NUlOeGlpQkZoankwNVNGVmUveUZ2UT09
Added it to both system32 and syswow64
I'm using 64-bit python 3.7.0 on windows 7 professional.  I was getting depressed as it was the 4th one I tried :(
At least now I've reached first base.

@tianxiawuzhe
Which version of the dll did you download? There are 5 on the site!
Were you using 32 or 64 bit Python 3.7?
I'm trying to port some Linux python code to windows 7, all the other pip installs seem fine, but I'm dead before I start without import cv2 working.
I've been given a 64-bit Windows 7 Professional machine to work with, so I've startedwith the 64-bit Python3.7

Sorry for late.
windows7 professional-64bit, python3.7-32bit ( installed by anaconda)
dll is the first one on 'https://www.dll-files.com/api-ms-win-downlevel-shlwapi-l1-1-0.dll.html' (17.3kb)
maybe you should download x64 dll for python3.7.

I thought I posted a follow-up after I started trying them all in sequence
and got it to work.  But thanks for the reply.
On Thu, Sep 13, 2018 at 1:08 AM tianxiawuzhe<EMAIL_ADDRESS>wrote:

@tianxiawuzhe https://github.com/tianxiawuzhe
Which version of the dll did you download? There are 5 on the site!
Were you using 32 or 64 bit Python 3.7?
I'm trying to port some Linux python code to windows 7, all the other pip
installs seem fine, but I'm dead before I start without import cv2 working.
I've been given a 64-bit Windows 7 Professional machine to work with, so
I've startedwith the 64-bit Python3.7
Sorry for late.
windows7 professional-64bit, python3.7-32bit ( installed by anaconda)
dll is the first one on '
https://www.dll-files.com/api-ms-win-downlevel-shlwapi-l1-1-0.dll.html'
(17.3kb)
maybe you should download x64 dll for python3.7.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/skvark/opencv-python/issues/116#issuecomment-420894501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeB7JjJcxvHi0mngiXyeu6B7lwuOkpULks5uafZugaJpZM4V1Aea
.

Encountered this and fixed it by downloading the missing dll, mentioned above.
"api-ms-win-downlevel-shlwapi-l1-1-0.dll" v10.0.14393.0 32bit (17.3 kb)
Win7 Pro 64bit, Python 3.6.5 32bit (without Anaconda)
Already had the dependencies recommended on PyPI: "Visual C++ redistributable 2015" and "Universal C Runtime" update.
#!/usr/bin/env python3
import os

# Include a bundled dll in the search path.
script_dir = os.path.realpath( os.path.dirname( __file__ ) )
os.environ['PATH'] = os.environ['PATH'] + os.pathsep + script_dir
import cv2

# Do stuff with OpenCV...

@wb666greene Did it work out? I used Windows server 2008, and the above problems also appeared, but I did not lose the api-ms-win-downlevel-shlwapi-l1-1-0 in system32 and syswow64. Do I still need to download and replace the DLL, or do I have other solutions? This has been bothering me for several days.

@azhaoaigaga   As far as I can tell it did.  I'm not much of a Windows user anymore, I was helping a friend setup a system.  This was a 64-bit system, you may need differnet for 32-bit.
I ultimately needed to install:
api-ms-win-downlevel-shlwapi-l1-1-0.dll
Windows6.1-KB2999226-x64.msu
vc_redist.x64.exe
vc_redist.x86.exe
To get everything to work.
Hope this helps, but I haven't touched a Windows system since I initially posted and eventually got his Python3 system working.

Windows server is probably missing some dependencies since it's headless by default. Never download DLL files from the internet, they are most likely malware / viruses. You could try to install the opencv-python-headless version which is targeted for headless server environments. Just remember to uninstall opencv-python first.
If that does not work, the issue is probably related to other missing DLL files which are not present on Windows Server versions. See for example https://withinrafael.com/2017/09/09/windows-container-app-compat-opencv-python/. In that case it might be that you have to build OpenCV manually and disable some Cmake flags to turn off features which are not supported by Windows Server 2008.

@wb666greene @skvark thanks,i‘ll try.


[Ember-Migration] Created a navbar

Resolves Issue
Closes #288
What is the change?

Create a navbar

Is Development Tested?

[x] Yes

Before / After Change Screenshots

Note for the Reviewer

CI is failing due to package-lock.json being not found as we are using yarn.lock here. Therefore, need to update the Workflows or create a new workflow. Issue for the same - #327
SignIn Sign Up flow is not completed yet. It will be handled separately #326

NIT: .gitkeep within the controllers, route, and model can be removed, We have one on the root level, that should be enough I think

Why is build failing?

NIT: .gitkeep within the controllers, route, and model can be removed, We have one on the root level, that should be enough I think

Will remove all the .gitkeep in another PR, as the code is still progressing and folders are being filled out with files

Why is build failing?

It is due to the CI failing because of the old GitHub workflow. I have mentioned in the description also as a `Note for the reviewer


Bugs in HTML Sanitization

The AJAX Control Toolkit \19.1.0\
The installation method

[ ] NuGet package

Minimal steps to reproduce the bug
Go to demo page
Type "Hello world!"
Submit content
Actual result
"Hello worldalert()"
Script tags and semicolon are removed as well as the exclamation point.
If you try submitting "Hello world! ", the space before  (underlined as well).  Instead, it is blank.  When I reload the page thru an Update button, it displays "" instead of the rich text format.  In my database, the value is stored as "".  What am I doing wrong?  Do I have something configured incorrectly?  Thanks in advance for the help.
Browser(s) used
Chrome
A site deployment method

[ ] VS development web-server,
[ ] IIS

Script tags and semicolon are removed as well as the exclamation point.

I cannot confirm this. Here is the request/response trace from https://ajaxcontroltoolkit.devexpress.com/HtmlEditorExtender/HtmlEditorExtender.aspx:

As for your additional questions, I acknowledge the behavior you're describing.
txtBox1.Text = "<script>alert();</script>"

The Decode function corrupts the text.

I cannot suggest any immediate workaround. Consider another HTML editor component for your project: Quill, CKEditor, etc.

I swear to you it was doing it yesterday.  I tried it on the demo before I made the post in order to double check it wasn't just locally.  I cannot get it to repeat on the demo now either (I wish I had captured it).  Here is the sequence on my local (request/response):
Typing (three spaces between 2020 and ":

Result (the script tags and one space are removed):

Another run with

An update.  I had an old tab open, and I did reload to record the request/response.  This is what I got:

It removed the space with the tags.
The only difference I noticed between the new vs old tab was that these errors popped up in the new one:


Gallgher > create cardholder: Return  new cardholder id

Gallagher Command Centre REST API documentation states that the href of newly created objects (like Cardholder) is returned but not in the body - it's in the response HEADER (yes annoying but true, we are utilising this in PROD for an old Engine deployment)
In the current PlaceOS driver, only the response.body data is used to create the new Cardholder object:
https://github.com/PlaceOS/drivers/blob/c919d26b513fc9ed5fa784f222405aadf6380b83/drivers/gallagher/rest_api.cr#L209-L211
Here is an example from the old ruby Engine Gallagher lib which pulls the new Cardholder href from the response's Location HEADER:
https://github.com/acaprojects/ruby-engine-drivers/blob/beta/lib/gallagher/rest.rb#L421-L423

ACTUALLY @cacique-coder, my mistake. The current placeos gallagher driver is already returning the full Cardholder object even for creation:
https://github.com/PlaceOS/drivers/blob/master/drivers/gallagher/rest_api.cr#L284
That line requests the newly created object and returns it (which will include the href).
So I'll close this issue.


Frequncy Interval and data quantification

Hi Everyone,
Has anyone run an anlysis to quantify how much data is used per min if we configure the apps frequency intervals.
Suppose if we keep the frequency like below:
1 sec
5 sec
10 sec
60  sec
120 sec
240 sec
Will appreciate any quantification analysis on the above frequency intervals.

Each message is about 215 bytes, then there is a 60 bytes response. On top of that there is 20 bytes TCP overhead. So total is about 315 bytes. There is some connection overhead on top as well, so let's say 350 per report.
That would be around 15mb a month with 60 seconds interval. Note that calculation assumes ideal conditions where device doesn't lose network connection. In reality if you lose connection, your telco will round data to nearest chargeable unit. That's usually 1kb, sometimes more. It means if device sends only a single report, and then loses connection, you will still get charged for 1kb even though you send only 350 bytes.

30s - 25MB I get such bill from my Operator

Thank You very much!


'BorrowFailed' using Input::set_default_cursor_shape in _process callback

Using Input::set_default_cursor_shape in the _process callback of the GDNative library triggers an error, as long as the _unhandled_input callback is also defined.
Full error is:
gdnative-core: method call failed with error: BorrowFailed
gdnative-core: check module level documentation on gdnative::user_data for more information

It could be related to this behavior of set_default_cursor_shape:

Note: This method generates an InputEventMouseMotion to update cursor immediately.

Repro project: gdnative_test.zip

Due to what's stated about set_default_cursor_shape in the docs, I believe this is the expected behavior. Consider that in Rust, you can have only one mutable reference to a particular piece of data in a particular scope. In your example, both _process and _unhandled_input take &mut self as the first argument. When set_default_cursor_shape is called from within _process, self is still being mutably borrowed. If _unhandled_input is allowed to be called, then from the perspective of the borrow checker, two mutable references to self will be present at the same time, even if we know that _process is still being blocked and it's in fact safe to modify self.
The solution here is to use the interior mutability pattern to ensure that the borrowing rules are followed at runtime:
use std::cell::RefCell;

#[derive(NativeClass)]
#[inherit(Node)]
pub struct HelloWorld {
    internal: RefCell<Internal>,
}

struct Internal(f32);

// __One__ `impl` block can have the `#[methods]` attribute, which will generate
// code to automatically bind any exported methods to Godot.
#[methods]
impl HelloWorld {
    /// The "constructor" of the class.
    fn _init(_owner: Node) -> Self {
        HelloWorld {
            internal: RefCell::new(Internal(0.0)),
        }
    }

    // Note that the first argument is a shared reference now
    #[export]
    fn _process(&self, _owner: Node, dt: f32) {
        let value = {
            let mut internal = self.internal.borrow_mut();
            internal.0 += dt;
            internal.0
        };

        let mut input = Input::godot_singleton();
        let cursor = if value % 1.0 < 0.5 {
            Input::CURSOR_POINTING_HAND
        } else {
            Input::CURSOR_ARROW
        };
        input.set_default_cursor_shape(cursor);
    }

    // Note that the first argument is also a shared reference now
    #[export]
    fn _unhandled_input(&self, owner: Node, event: InputEvent) {
        let mut internal = self.internal.borrow_mut();
        do_thing_with(&mut *internal);
    }
}

fn do_thing_with(internal: &mut Internal) {
    // - snip -
}

The above code snippet compiles and runs as expected. Note that both _process and _unhandled_input take &self now: this tells the bindings that you are handling your own interior mutability, so it will allow multiple concurrent borrows to happen.

Thanks for the explanation! Hopefully it will help other people as well. I've learned that the mutability annotations can affect the emitted code.


Coding Challenges - Arrange by difficulty/experience?

Would it be possible to arrange the Coding Challenges by difficulty or maybe have a challenge suggested after watching a certain tutorial video?
As someone new to coding i've started watching a few of Daniels Challenges but quickly get lost in all the unfamiliar information. I stumbled across one that was at my level of understanding and really got a lot out of it.
This is my first post here btw so apologies if i'm not following any guidelines properly.
Thanks

Thanks for your suggestion, @LWoodall. Some sort of "difficulty indicator" would be a great idea! This could also help others to find challenges that are on a similar "level" based on what they've already watched; like a "where to go from here" section.
I don't think that it is fully possible within the current system (we're using Jekyll - a static site generator - to build the website) but could maybe be partially added with other features (like automatic suggestions or sorting) coming at a later point?
What are your thoughts @shiffman?

I do like this idea!
If we come up with a scale to use beginner, intermediate, advanced or similar we could add it as a field and use group_by or sort in Jekyll I think? (We might have to hack around this by giving them numerical values so sorting works)

I also love this idea! It would also be great for each challenge to somehow elegantly reference what tutorial videos are "pre-requisites" for the topic?

An indicator of what required knowledge or videos watched would be ideal for someone like myself. Also the opposite would be helpful, like after you finish a video or a series of videos, a challenge is recommended to help reinforce the materials taught in the tutorials?


can this handle UTF-16?

I'm getting
     c:/Ruby193/lib/ruby/1.9.1/rexml/encoding.rb:41:in `encode': "<?" on UTF-16 (Encoding::InvalidByteSequenceError)
        from c:/Ruby193/lib/ruby/1.9.1/rexml/encoding.rb:41:in `decode'
        from c:/Ruby193/lib/ruby/1.9.1/rexml/source.rb:58:in `encoding='

I don't know if it can handle UTF-16. Most of the library is tested using UTF-8. The problem of mixed encodings in input is that there's little way to specify the original encoding of the input data. Try this:
RUBYOPT="-E utf-8" gorgeous ...

where you replace "utf-8" string with the encoding that you're certain that the input data is in.


Total distance not showing

Total distance not showing when choosen to be displayed in any of the widgets.

I had completely forgot to initialize the code of the widgets ^_^
Fixed on commit d52d994368c7f220c5c44823ad7412e11f2d709b
I also fixed the units not showing when screen is on for both daily/total distance widgets.
Commit 1365ea804d2340e49a11a04a30e36116cc5f0490


Support richer snapshot tests

Node 22.3 added snapshot tests, we should make sure they're supported nicely and can be updated with UI flows


Make awesomplete a CJS/AMD module

does the module dance from https://github.com/umdjs/umd
adds a package.json file, based on @blocka's fork
will not assume the presence of document, in case you're running this in node

Hi there,
Thanks for contributing!
Please, please, please send separate pull requests per chunk of changes, as now I cannot reject some and accept others.  What's the point of this without a GUI? I’m probably missing something here, but what?

Hello,
I'm happy to split up the changes. But, I'm not sure what the package.json will buy you unless awesomplete is at least a CJS module. I don't particularly care about UMD, I just need to be able to require() the module using webpack and in Node in my isomorphic React application. Would you accept a change that just sets module.exports = Awesomplete and avoids direct use of document so that will work for me? Otherwise I'll have to look elsewhere for my auto-completing needs :-)
Thanks!

On Feb 27, 2015, at 4:04 PM, Lea Verou<EMAIL_ADDRESS>wrote:
Hi there,
Thanks for contributing!
Please, please, please send separate pull requests per chunk of changes, as now I cannot reject some and accept others.  What's the point of this without a GUI? I’m probably missing something here, but what?
—
Reply to this email directly or view it on GitHub.

In my fork, I just added a package.json and now when I do require('awesomplete') I have access the Awesomplete object on window. So, yes I'm "littering" window a little bit, but it works fine for me.

@drd Probably, but keep in mind that document isn't only used in the init code. It’s also used to create elements, for the Selectors API and pretty much everywhere, so I worry that adding checks everywhere might end up being too messy and verbose.
Given that Awesomplete isn't really useful without a DOM, could you perhaps explain your needs a bit, in case there's a better solution? E.g. can we convert document to a local variable that resolves to something else in your environment? I don’t really use React or webpack, so you need to elaborate a bit more for me to understand how to help :)

+1

Simply put, using webpack, browserify or spm, you can easily import js modules via a simple require('awesomplete'), only demands module's code shall be CommonJS.

@LeaVerou I totally agree — there is no point in using Awesomplete without a DOM. However, if I have a component running on the server that depends on Awesomplete, it should be able to safely require('awesomeplete') without a ReferenceError. Then, once the same component is mounted in the client browser, all the document references will work just fine. So, all I need to do is allow the module to parse and execute top-level code in node. None of the other uses of document need to be checked.

@drd We can definitely work around that! I guess your solution is probably the best way (checking if document exists).

@LeaVerou,
I've updated and rebased the pull to only export as a CJS module. I've tested the CJS on our internal application and also as a normal script in this fiddle: http://jsfiddle.net/v8upqxhj/
Thanks!

Merci!

@drd could you please apply the changes @arthurvr mentioned? Or, even better, @arthurvr could you send a PR?

@LeaVerou Already done. https://github.com/LeaVerou/awesomplete/commit/47ba3d1edb10760fc231483df60ce337e735868f


Add lang tag to url

Incorporate the functionality from WarVictimSampo

Lang tag is always added, if it is not provided.


[Bug] SparkSQL can not exec in Scriptis

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-cg-entrance, linkis-cg-manager
What happened + What you expected to happen
Create SparkSQL In Scriptis run failed ， return error log
2022-01-27 09:58:51.058 ERROR Task is Failed,errorMsg: errCode: 12003 ,desc: hostname-xxxxx:9101_8 Failed  to async get EngineNode FeignException.NotFound: status 404 reading RPCReceiveRemote#receiveAndReply(Message) ,ip: hostname-xxxxx: ,port: 9104 ,serviceKind: linkis-cg-entrance
linkis-cg-linkismanager.log :

Relevent platform
Linkis1.0.2  NOT with CDH
Reproduction script
SparkSQL: show tables
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Maybe you can find some detial log info in  engine workdir(ENGINECONN_ROOT_PATH/youruser/workDir, ENGINECONN_ROOT_PATH is configured in linkis-env.sh)

This is similar to question Q18


Rendering order issue

I added some canvases with render mode set to world space, but they always appear in front of the Gaussian model. Is there any way to modify the rendering order? I tried adjusting the CameraEvent in the CommandBuffer and the ZWrite in the shader, but it had no effect.
PS: I'm using URP.

Well, the problem has been solved. I didn't realize that in URP, CameraEvent needs to be changed to RenderPassEvent, just like Camera.onPreCull needs to be replaced with RenderPipelineManager.beginCameraRendering. These changes were already implemented in the GaussianSplatURPFeature script. Thank you very much for also preparing the functionalities for both URP and HDRP in advance.

@YuEBuZu114514 Apologies for digging up this old thread. I'm not very familiar with the respective render setup - would you mind letting me know what exactly you did in Unity to get the correct render order? Your second comment seems to suggest that no code changes were needed. Was there anything else you did? Thank you!

@YuEBuZu114514 Apologies for digging up this old thread. I'm not very familiar with the respective render setup - would you mind letting me know what exactly you did in Unity to get the correct render order? Your second comment seems to suggest that no code changes were needed. Was there anything else you did? Thank you!

In the GaussianSplatURPFeature script, around line 60, in the function named create, there is a line renderPassEvent = RenderPassEvent.BeforeRenderingTransparents. You can change BeforeRenderingTransparents to AfterRenderingTransparents. However, this still has some issues.
Before the change, the canvas in the scene is rendered before the Gaussian model, meaning it will be obscured. After the change, since it is rendered afterward, the model will be obscured regardless of which one is actually in front. However, if your canvas is an image or does not leave any blank space, you can place a quad behind the canvas to replace modifying the render order. This way, the model will be blocked by the quad first, and then the quad will be blocked by the canvas.

Thank you for your quick response, @YuEBuZu114514 . Appreciate it!


raspbian bullseye, humble, error on node startup with arducam-pivariety camera

I have arducam-pivariety B0353 (AR0234) running on bullseye (verified with libcamera-raw).
Tried to run camera_ros (73f7cedf44d37a512688ac2ee0ac8069e7716a4e), but getting a runtime_error:
ros2 run camera_ros camera_node --ros-args -p width:=1920 -p height:=1200 -p format:=RGB888
[65:43:51.897428496] [30680]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3875-5eb7be6a
[65:43:51.942223710] [30693]  WARN CameraSensorProperties camera_sensor_properties.cpp:174 No static properties available for 'arducam-pivariety'
[65:43:51.942315135] [30693]  WARN CameraSensorProperties camera_sensor_properties.cpp:176 Please consider updating the camera sensor properties database
[65:43:51.952599892] [30693] ERROR IPAProxy ipa_proxy.cpp:149 Configuration file 'arducam-pivariety.json' not found for IPA module 'raspberrypi'
[65:43:52.397740961] [30693]  INFO RPI raspberrypi.cpp:1374 Registered camera /base/soc/i2c0mux/i2c@1/arducam_pivariety@c to Unicam device /dev/media2 and ISP device /dev/media3
>> cameras:
0: arducam-pivariety (/base/soc/i2c0mux/i2c@1/arducam_pivariety@c)
>> stream configurations:

[... long list of configurations, including   "- Pixelformat: RGB888 (64x64 - 1920x1200)" ...]

[65:43:52.417725543] [30680]  INFO Camera camera.cpp:1035 configuring streams: (0) 1920x1200-RGB888
[65:43:52.506216179] [30693]  INFO RPI raspberrypi.cpp:761 Sensor: /base/soc/i2c0mux/i2c@1/arducam_pivariety@c - Selected sensor format: 1920x1200-SGRBG10_1X10 - Selected unicam format: 1920x1200-pgAA
camera "/base/soc/i2c0mux/i2c@1/arducam_pivariety@c" configured with 1920x1200-RGB888 stream
[WARN] [1662366193.047733808] [camera]: control NoiseReductionMode (39) not handled
terminate called after throwing an instance of 'std::runtime_error'
  what():  unsupported ControlValue cast
[ros2run]: Aborted

(Probably unrelated: The arducam wiki says not to worry about the missing .json file. Not sure if that is the right approach, but it didn't seem to bother libcamera-raw...)

You need the default_info_init branch of my fork at https://github.com/christianrauch/libcamera/tree/default_info_init. I submitted this to the libcamera-devel mailing list and hope this gets merged soon.
Generally, I am tracking the most recent libcamera version and I am also rebasing the main history until an initial release. If you continue to use this repo, you will have to hard reset from time to time.

Ok, understood. Thank you. I have to on another project first and will revisit my ROS setup in a few days, maybe I get lucky and it's already merged then. Is there a way on the official repo to follow merge requests?

Works as expected.

Ok, understood. Thank you. I have to on another project first and will revisit my ROS setup in a few days, maybe I get lucky and it's already merged then. Is there a way on the official repo to follow merge requests?

For the complete discussion, you have to watch the libcamera-devel mailing list. To get an overview of the submitted patches, you can check out patchwork. E.g. the latest version of my patches is at https://patchwork.libcamera.org/project/libcamera/list/?series=3467. You can use the pwclient to apply and test patches.
Unfortunately, everything works via mailing lists. There is no web interface to follow and contribute to discussions.


Publish only necessary files in package

To prevent publishing wrong files.

published v7 🎆

Awesome, thanks!


Leverage docker build cache

This will leverage docker build cache as suggested in Best practices for writing Dockerfiles.
Files: package.json and package.lock.json are not changing as often as files in /src or /bin.
Before every change in files in  /src or /bin invalidates docker build cache for layer with npm install.
After it works like that (simple change in .src):
 => CACHED [2/7] WORKDIR /app                                              0.0s
 => CACHED [3/7] COPY package*.json ./                                     0.0s
 => CACHED [4/7] RUN npm install --production && npm cache clean -f        0.0s
 => CACHED [5/7] COPY bin/ bin/                                            0.0s
 => [6/7] COPY src/ src/

Thanks!

Thanks!


Ethers V6

As I understand, Ethers v6 makes it possible to include only required sub modules. The version I use in this project (v5x) is loading as whole package which effects the initial page load drastically. Watch ethers v6 package updates periodically, and when it seems stable, upgrade ethers to latest version and update EthersWalletAPI service class.
PS: Current package name is: ethers@beta-exports => until "beta" removed from package name, no need to try to integrate it. Wait stable package name.

Consider using viem

Instead of replacing EthersV5 with EthersV6, it's better to include all alternatives.
-services
--EthersV5
--- EthersV5WalletAPI
--- EthersV5AvvyAPI
--EthersV6
--- EthersV6WalletAPI
--- EthersV6AvvyAPI
--Viem
--- ViemWalletAPI
--- ViemAvvyAPI
This task will be used for EthersV6
Viem version is here


MD5 output not same as openssl on Mac

In the sample app, the MD5 of text: abc shows
900150983cd24fb0d6963f7d28e17f72
In Mac bash: echo "abc" | openssl dgst -md5 shows
0bee89b07a248e27c83fc3d5951213c1

The MD5 Hash from the sample app above is correct

Thanks, found why.


Typescript getters/setters generator for ECMAScript syntax private properties

When you declare a property with ECMAScript new private property like #property , the system does not recognize is as a property for the purpose of generating the corresponding getters/setters.

Thank you, I really enjoy VSCode!

This feature is powered by the TypeScript project. Please file a feature request upstream


Duplication/Configuration Issues Related to ICEES+ Asthma & ICEES DILI, Development & Production Instances

This issue is focused primarily on issues related to the ICEES+ Asthma and ICEES+ DILI development and production instances, with the December 2021 Translator Demo in mind.
The results of various tests can be found here.
A summary of testing efforts follows below (from a Slack exchange between Kara, Kenny, and Max).

Okay, I just ran what I think is the final definitive test.
I looked up identifiers for DILIDx and AsthmaDx and also SexDILI and Sex2, using all four ICEES instances. DILIDx and SexDILI should only return responses from ICEES DILI; AsthmaDx and Sex2 should only return responses from ICEES Asthma.
Instead, all four ICEES instances returned responses to all four queries. The ICEES DILI and ICEES Asthma production instances returned incorrect identifiers, presumably because they are pointing to the outdated config files. The ICEES DILI and ICEES Asthma development instances returned correct identifiers, presumably because they are pointing to the ground truth config files.
Kenny: I bet if you ran the same asthma and DILI tests but pointed the asthma test at the DILI prod instance and the DILI test at the asthma prod instance, you'd receive the same results.
The actual data that are being returned to each query of dev and prod are correct. As noted above, but perhaps more firmly here, I'm proposing that we merge the asthma & DILI, dev & prod instances and expose one ICEES dev instance and one ICEES prod instance, using the ground truth config files.

Regarding my proposal, and looking forward to new use cases, a merger of all use cases into one ICEES dev instance and one ICEES prod instance will only work if we are very careful about distinguishing feature variable names. For example, "Race" can be reused for all UNC Health data, but not for DILI Network data or EPR data.

Related is issue #182.

Note that my proposal would simplify #175 and #203.

Update on port 16340 tests:

Ground truth feature variables, names and identifiers, are being returned for both asthma and DILI.
The non-Translator, non-KG functionalities seem to return data for asthma, but not DILI, although some of them appear to be broken, so this may be a separate issue. (See "association to all features" example below for Sex2 (asthma variable), but same results for SexDILI (DILI variable). Also, the "features" functionality times out.
The one-hop KG queries are timing out after spinning for a long time. The results of these tests are needed to confirm that separate KGs are created for asthma and DILI. Tests are for MONDO:0004979 (asthma) and MONDO:0005359 (DILI).
For the Dec demo, the ICEES DILI instance should be able to respond to B.1 with input MONDO:0005359 and C.1 with input MONDO:0013433 or MONDO:0005388. According to the 11/29/2021 workflow tracker, ICEES asthma and ICEES DILI are responding to B.1, with identical results; ICEES asthma and ICEES DILI are timing out to C.1.

https://files.slack.com/files-pri/T0450N0TQ-F02NM1XBF52/image.png
https://files.slack.com/files-pri/T0450N0TQ-F02NM1XBF52/image.png

Next steps:

Kara will split the current ground-truth all_features and identifiers YAML files into four sets of files, one per use case, beginning with DILI, then asthma, then COVID, then PCD.
Kara will add biolink:SmallMolecule to relevant variables in each set of YAML files.
Hong will redploy the ICEES asthma dev instance and the ICEES DILI dev instance at their respective ports after (1) and (2) are complete.
Kenny will review the code used to support the KG one-hop endpoint.
Kenny will update the SmartAPI registrations after (1-4) are complete and also take down any ICEES instances that are either broken or not needed.

@hyi @kennethmorton @maximusunc : I ran a few KG one-hop tests using the three CURIES that only ICEES DILI should respond to. I also viewed Max's test results, using both QGraph and the ARAX viewer. I'm pretty sure that the KG one-hop endpoint is running pairwise correlations based on biolink:XXX categories/types, not the underlying data or input CURIES. For instance, ICEES DILI dev is returning results for the ICEES COVID instance and the ICEES PCD use case that hasn't even been deployed yet. This issue might explain why the Swagger UI is no longer reliable, apart from the most simplistic queries.
There are other issues, but perhaps not worth mentioning right now.
I think that Hao's 'master plan' was to create a set of three YAML config files and then run code to break them into Dhall files, with me selecting variables for each ICEES instance, like this one. What he may have overlooked in the interim is a need for a fourth YAML config file to map between biolink:XXX and csv column headers.
Regardless of the above, I think that fixes (1-5) above should resolve the issues in the near term, with an implementation of our planned redesign needed for the longer term.

Issue resolved by splitting master ground truth all_features and identifiers YAML files into separate sets of files for each use case: asthma, dili, pcd, and covid. Completed for asthma, dili, and pcd.

ICEES asthma prod and ICEES DILI prod deployed and tested.

Resolved.


[Feature Request]Support HTTP query interface

Support HTTP query interface
Is your feature request related to a problem? Please describe.

To provide users with a more common and convenient way to execution sql. Such as Druid, ClickHouse provided.
eg:
POST  fe_host:http_port/api/sql?db=test  post_data=queryStatement
return format as json array:
[{"result_field_name_1": "value1", "result_field_name_2" : number}, {row2}, {...}, ...]
Describe the solution you'd like

I think there are three implementation of solution:

Implement a stmt submitter on FE
refer to apache doris Statement Execution Action

This is a simple stmt submitter for submitting a statement to the local FE.
It uses a fixed-size thread pool to receive query requests,
so it is only suitable for a small number of low-frequency request scenarios.
Now it support submitting the following type of stmt:
QueryStmt
ShowStmt
InsertStmt
DdlStmt
ExportStmt

It's simple enough but lack of performance.

Deserialize the mysql packet from BE to JSON in FE
The performance of deserialization needs to be considered. Fortunately, BE does not need to change.

Add a new fetch_data interface between FE and BE for JSON result data
This includes new a json_result_writer in BE, new ResultReceiver in FE and so on. Most important of all, these modification needs to be based on a sufficiently abstract code framework, I tried to implement the this solution, but the code of mysql protocal is too coupled to do modify.Could somone can gives some suggention?

Describe alternatives you've considered

Is there any alternative solutions?

I have serval question to clarify:

I think we should obey the Restful specification. How to handle error code? I see your PR handled 500 and 401 only? Should we maintain a lookup table for the error code? For example, They will be more error code 403 ...
How to handle a large result set? Should we add a default limit for it?
Whether to add metadata to the return result, such as the number of rows returned, the format of the result object?
How to handle NULL / array / Bitmap / HLL ?


useOverlay will dismiss a modal if the user left-clicks on the modal content's scrollbar and drags

🐛 Bug Report
Create a scrollable modal.  The modal will close unexpectedly when the user clicks + holds to drag on the scroll bar after releasing the click.  The user can scroll with the mouse wheel as expected.
🤔 Expected Behavior
The modal should not close when releasing the left mouse button after clicking a scroll bar and dragging.
😯 Current Behavior
The modal will close when the user clicks to drag on the scroll bar and releases the click.
🔦 Context
My users may often use the mouse to scroll a scrollable modal.  Doing so will close it unexpectedly.
💻 Code Sample
https://codesandbox.io/s/suspicious-sun-89uvk
🌍 Your Environment

Software
Version(s)

react-spectrum
3.1.0

Browser
Chrome, IE, Firefox

Operating System
OSX, Windows

A code example would be great. We can also try to reproduce this .

I was able to get an interim fix in by turning isDismissable in useOverlay to false and then setting an onClick handler to the dimmer used behind the modal, but agree - I'll try to get that example up soon.

Working example added.  I wasn't able to reproduce it until I added in the Transitions, so I think this actually has to do with that vs. React Spectrum.  Can you confirm?

Hmmm we use Transitions as well, though not css Transitions https://github.com/adobe/react-spectrum/blob/c700898916bbd076bcc63e49d77c16d80623a8e7/packages/%40react-spectrum/overlays/src/Overlay.tsx#L47
I wonder if you can reproduce it with our Dialog component. I don't see any problems in our documentation https://react-spectrum.adobe.com/react-spectrum/DialogTrigger.html

I think the issue is that the div outside the dialog is what's scrolling rather than the dialog itself – the Transition element has the overflow-y-scroll class on it. The useOverlay hook detects clicks outside the element its attached to, and in this case, clicking on the scrollbar fires an event on the div that's outside the dialog. If you made the dialog itself scrollable instead of the container, that should fix the issue since the event would fire on the dialog itself.

Thanks guys!  @devongovett I'll try re-arranging that tonight and see if that fixes the issue.  Really appreciate the guidance.

I believe I have it.  Would you guys mind giving it a look over?
https://codesandbox.io/s/suspicious-sun-89uvk

Will close this in the meantime, confident this does not have to do with React Spectrum.

Nice! Looks good to me. 😄


[Bug] The action image dialog shows up behind the action dialog

When setting an image for an action, the dialog pops up behind the one for the action. This is likely due to the fact that one is a TRL Svelte dialog, and the other is a basic Foundry one. Foundry's bringToTop method isn't able to account for the Svelte dialogs, which would have been an easy fix.
It does not appear that we can pass in an explicit z-index to the FilePicker either. We should look into whether there's a TRL version of the FilerPicker. If not, we need to figure out a way to fix this.
Overall, this is a minor inconvenience, but it makes the system look less polished.

Fixed


Extract getWorkspaceFlag(pm) to also detect Yarn workspace configurations

This refactor improves the detection of workspace configurations by adding a check for Yarn workspaces. The function now returns the appropriate flag (-w/W) for both Yarn and PNPM workspaces, ensuring correct package installation in multi-package repositories.
closes https://github.com/webpro-nl/knip/issues/754

Thanks Hendrik! Much appreciated.

Sorry I forgot to publish, it's on npm in v1.0.3 :)

:rocket: This pull request is included in v5.27.3. See Release 5.27.3 for release notes.
Using Knip in a commercial project? Please consider becoming a sponsor.


looping of mp4 video doesn't work.

In DJV 2.0.8, looping an mp4 (H.264, AAC) doesn't work.
The clip plays to the end and then stops.

Hi,I have also seen this with some movie files. I will try to get it fixed for the next version.


Commits with description/body content are being left out

It is entirely possible I'm missing something obvious in the documentation but I'm facing an issue fairly detrimental to how myself and my team write commits.
A typical commit being added to the changelog via auto-changelog consists of: 🔨 Update functionality for feature
However I noticed when commits were tied to a story ID, or had extra description, they are not included in the automated updates and are left out entirely:
🔨 Update functionality for feature

PID-123

or
🔨 Update functionality for feature

Due to change in requirements, needed
to change how thing is handled

Both of those examples are not included in the changelog created by auto-changelog. They exist in the Git history locally and on the remote, so they do exist, but auto-changelog seems to be skipping over any commit that is not only a subject line.
Am I, like I mentioned, missing or misusing an option or template? Both can be found below:

For extra context here is the point where I noticed this occuring:
In GitHub, and locally, this was the history I expected to see (minus release commits of course):

After running auto-changelog, the changelog created was this:

The "Add new styles" commit, which has description area content (where I store my story links), is left out of the generated log.

Merge commits and commits that fix an issue are grouped into separate lists (merges and fixes) which is why they don’t appear in commits.
I guess in your case you need a flag that doesn’t do any clever grouping of commits based on the content, so they all appear in the commits array and can be filtered by your handlebars template.

@geebru Hi, have you figured out the issue "commits with description/body content are being left out "?
I experience the same issue.
The command I use:
auto-changelog --output CHANGELOG.md --commit-limit false --template keepachangelog --ignore-commit-pattern '.*\[skip ci\].*'
For the commit, I expect to have both commit title and body message, like
Author: Jiyang Ye<EMAIL_ADDRESS>Date:   Sat Dec 9 14:02:40 2023 +0100

    This commit has both title and message

    Dummy message. xxxx

The result I got missed the body message,
Commits
This commit has both title and message b0bedf8

Any chance we could have an option to include the commit body in the changelog? I use it to describe breaking changes and how users can migrate. Would be useful to have in the changelog


[SMALLFIX] Remove a file "test_path" that is unused in the codebase

I guess it is checked in by mistake.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12153/
Test PASSed.

LGTM


Fix various shading pattern regressions (issue 6287)

Fixes #6287.
Note: This PR fixes the regressions, the remaining (and already tracked) shading pattern issues should be addressed separately.

/botio-linux preview

/botio-linux preview

/botio test

/botio makeref

Great work!


(fix): URI path traversal in serve_uploads is no longer possible

Part of this sprint is to implement the recommendations
from the recent PenTest, this was one of those recommendations
See '2.1.3 Fix the local file include in the new-members-only plugin'
of the report

Resolves: https://trello.com/c/NE9JaSb0/235-1-2-1-3-fix-the-local-file-include-in-the-new-members-only-plugin

(I added a bunch of files called x.txt which contain their locations.)
Testing on the master branch with whippet server:
% cat req.txt && cat req.txt | nc `docker inspect -f '{{.NetworkSettings.IPAddress}}' whippet_wordpress` 80
GET /wp-content/uploads///..//./..//.//x.txt HTTP/1.1
Host: localhost

HTTP/1.1 200 OK
Date: Tue, 29 Nov 2016 16:05:40 GMT
Server: Apache/2.4.10 (Debian)
Last-Modified: Tue, 29 Nov 2016 16:04:31 GMT
ETag: "27-54272be5ca1c0"
Accept-Ranges: bytes
Content-Length: 39
Content-Type: text/plain

/var/www/html/wp-content/uploads/x.txt

% cat req.txt && cat req.txt | nc `docker inspect -f '{{.NetworkSettings.IPAddress}}' whippet_wordpress` 80
GET /wp-content/uploads///..//./..//.//..//.//x.txt HTTP/1.1
Host: localhost

HTTP/1.1 200 OK
Date: Tue, 29 Nov 2016 16:12:49 GMT
Server: Apache/2.4.10 (Debian)
Last-Modified: Tue, 29 Nov 2016 16:04:31 GMT
ETag: "27-54272be5ca1c0"
Accept-Ranges: bytes
Content-Length: 39
Content-Type: text/plain

/var/www/html/wp-content/uploads/x.txt

Hmm I'm unable to reproduce the bug.
Oh yes. I think you need to add something special to Apache to get it to handle uploads.
So I think we need to test this on staging.

Rebased against master.

Looks good, nice catch with the trailing slash.


can not run baichuan-13B  in v100

hello
when I run code as below:
`from vllm import LLM
llm = LLM(model='baichuan-inc/Baichuan-13B-Chat', trust_remote_code=True)  # Name or path of your model
output = llm.generate("Hello, my name is")
print(output)`
and error occur:
ValueError: Bfloat16 is only supported on GPUs with compute capability of at least 8.0. Your Tesla V100-SXM2-32GB GPU has compute capability 7.0.
v100 can not run baichuan-13B-Chat in vllm??
could you help me?

add parameters in cli : --dtype half

这个问题怎么处理哇？ValueError: Bfloat16 is only supported on GPUs with compute capability of at least 8.0. Your Tesla V100-SXM2-32GB GPU has compute capability 7.0.

直接在llm = LLM(model='baichuan-inc/Baichuan-13B-Chat', trust_remote_code=True) # Name or path of your model参数里加 dtype='half'即可。
具体可以看 https://github.com/vllm-project/vllm/commit/1ac4ccf73c91370f1fcb4f60c1117646cd7a7502
相关的问题在：https://github.com/vllm-project/vllm/issues/1157


added the file 2.api-authentication.md

@varadtote any update on this??

Closing due to inactivity!


HTTP/2 SimpleChannelPromiseAggregator don't fail fast

Motivation:
Http2Codec.SimpleChannelPromiseAggregator currently fails fast if as soon as a tryFailure or setFailure method is called. This can lead to write operations which pass the result of SimpleChannelPromiseAggregator.newPromise to multiple channel.write calls throwing exceptions due to the promise being already done. This behavior is not expected by most of the Netty codecs (SslHandler) and can also create unexpected leaks in the http2 codec (DefaultHttp2FrameWriter).
Modifications:

Http2Codec.SimpleChannelPromiseAggregator shouldn't complete the promise until doneAllocatingPromises is called
Usages of Http2Codec.SimpleChannelPromiseAggregator should be adjusted to handle the change in behavior
What were leaks in DefaultHttp2FrameWriter should be fixed to catch any other cases where ctx.write may throw

Result:
SimpleChannelPromiseAggregator won't generate promises which are done when newPromise is called.

@normanmaurer @nmittler - FYI

LGTM

@Scottmitch LGTM

Cherry-picked 4.1 (6a2425b)


Stream metrics/index.json

With large numbers of metrics in Graphite, I get a 504 Gateway Timeout when requesting metrics/index.json.  This is because the timeout on the web server is set too small for the amount of time Graphite takes to produce metrics/index.json.  Graphite does not send even 1 byte of the HTTP header back.
Instead, Graphite should send an HTTP header back immediately.  Then as Graphite finds metrics, it should immediately send the metrics back.  For example, in the output below, Graphite would send the HTTP header (not shown) and the first [.  Then as each metric is found it would send a string.  When all metrics have been returned, Graphite would then send the last ].
[
"collectd.host1.load.longterm",
"collectd.host1.load.midterm",
"collectd.host1.load.shortterm"
]
This will keep the web server from timing out and reduce the amount of data Graphite buffers as it scans for metrics.
Perhaps, the sorted requirement needs to be dropped so that Graphite can return metrics faster.

I'm not a big Django expert, but I'm suspecting that it will be quite hard to implement behavior which described above. It's much easier to tune web server for a bigger timeout. @cbowman0 @DanCech ?


FuseBox Quantum

And finally, 2.1.0 is out with its grand, the most challenging-to-implement feature.
Quantum
http://fuse-box.org/page/quantum
Make sure to check it out and let us know what you think. It required lots of effort and thinking. I hope you guys could start testing it and submit your ideas and of course, our favourite - bugs.
https://github.com/fuse-box/angular2-example
https://github.com/fuse-box/react-example
node fuse dist

Tree shaking example is here It manages to shake out some code of angular2 btw
Cheers!

The docs mention that uglify is enabled by default but it requires an { uglify: true } passed to Quantum.
Also, why does it generate
var A = $fsx.r('index.js');
when I can only see number ids? The code works when I change the 'index.js' into the correct number, that I have to find by going through $fsx.r.
Also what's the correct way of using it with the babel plugin? The docs on removeExportsInterop is a little hard to read and I can't tell if it should be true or false. Setting it to false causes  exports is not defined

> Also, why does it generate $fsx.r('index.js')
It wasn't able to find a node module (and it is an invalid node module that you put there)
Check your bundle without Quantum.
You should import "./index.js" and not import("index.js") furthermore, please read up on javascript import statement basics.
You can use any plugin you like, Quantum does processing after everything else (babel, typescript it doesn't care). And use it for production builds.
Regarding uglify, that i will fix, thanks

The build worked before adding Quantum, and I am also not doing imports like that
I am doing import * as Abc from "abc"; as instructed from http://fuse-box.org/page/faq#imports-exports

Ok, could you reproduce the error, please?  (in a GitHub repository)

Try this: https://github.com/yihongang/test_quantum
Thanks for the fast response. If it's an issue with how I am doing stuff, I apologise in advance.

@yihongang that was an easy one
fuse.bundle('vendor').instructions('~ client.tsx')
fuse.bundle('client').instructions('!> [client.tsx]')
fuse.run()

Make sure you have the right order.
First vendor then client
All started working after I have swapped them.

Welps that was embarrassing. Is there somewhere where this is documented? Thanks for the help! 😅

@yihongang no worries, I don't think so but, I though it goes without saying ;-) As vendor should be loaded first ;-)


Configure what counts as a failure?

Should the user be able to configure what counts as a failure, a request that can be retried and a successful request? And how should this be specified? Just http status codes, specific errors from Apples NSURLErrorDomain?

One way is to have a delegate that gets the NSError from the request and then the delegate can choose to keep the request in the queue to retry or remove it to continue with the next one. For example:
- (BOOL)shouldRetryRequest:(NSURLRequest *)request afterError:(NSError *)error {

}

We can let the user specify this on a per model class basis or we can let them configure it generally. Depends on the needs. Maybe it is nicer to handle it in each class. Then you can handle any specific errors there?


Update comparemerge to 2.05y

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Error: It seems the App source '/usr/local/Caskroom/comparemerge/2.05y/CompareMerge 2.05y/CompareMerge 2.05y.app' is not there.


Detox/E2E: Added missing comment guideline

Summary

Added missing comment guideline for previously merged PRs

Ticket Link
NA

Also, please add related doc to https://developers.mattermost.com/contribute/mobile/e2e/guide-for-writing/.

Also, please add related doc to https://developers.mattermost.com/contribute/mobile/e2e/guide-for-writing/.

@saturninoabril Created a PR --> https://github.com/mattermost/mattermost-developer-documentation/pull/710


Get-TestsFromBcContainer fails with Client Session State is uninitialized

Describe the issue
Running command GetTestsFromBCContainer on Azure build pipeline is failing only on BC15 and BC18 (Runs fine for BC19,20,21,22 and 23), with error Client Session State is uninitialized.
Scripts used to create container and cause the issue
Write-Host "Retrieving Tests from Container $containerName"
#get all the tests we want to run
$tests = Get-TestsFromBCContainer             -containerName $containerName
-credential $credential             -extensionId $app.AppId
-ignoreGroups
Full output of scripts
2024-02-29T12:10:57.4633513Z ##[section]Starting: Run Tests
2024-02-29T12:10:57.4835498Z ==============================================================================
2024-02-29T12:10:57.4835818Z Task         : PowerShell
2024-02-29T12:10:57.4836061Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2024-02-29T12:10:57.4836294Z Version      : 2.235.1
2024-02-29T12:10:57.4836509Z Author       : Microsoft Corporation
2024-02-29T12:10:57.4836816Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2024-02-29T12:10:57.4837205Z ==============================================================================
2024-02-29T12:10:58.5009120Z Generating script.
2024-02-29T12:10:58.6202273Z Formatted command: . 'c:\Agent\_work\20\s\Git-BuildScripts\scripts\Run-Tests-Updated.ps1' -version "18" -credential ([PSCredential]::new("admin", (ConvertTo-SecureString -String "xxxxxx" -AsPlainText -Force))) -testAppName "Zetadocs Tests" -containerName "Z5236518" -bcHelperForcedVersion "6.0.3"
2024-02-29T12:10:58.6346350Z ========================== Starting Command Output ===========================
2024-02-29T12:10:58.6540722Z ##[command]"C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'c:\Agent\_work\_temp\898133a2-cf78-40d6-80c4-ea76d89af198.ps1'"
2024-02-29T12:10:59.3647071Z BcContainerHelper version 6.0.3
2024-02-29T12:10:59.9222315Z Setting usePsSession = False
2024-02-29T12:10:59.9337650Z BC.HelperFunctions emits usage statistics telemetry to Microsoft
2024-02-29T12:11:08.2202889Z WARNING: The names of some imported commands from the module 'BcContainerHelper' include unapproved verbs that might
2024-02-29T12:11:08.2213614Z make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the
2024-02-29T12:11:08.2223885Z Verbose parameter. For a list of approved verbs, type Get-Verb.
2024-02-29T12:11:08.2292050Z Getting App Info
2024-02-29T12:11:11.4240171Z Retrieving Tests from Container Z5236518
2024-02-29T12:11:19.1118516Z CommunicationError : Response status code does not indicate success: 500 (Internal Server Error).
2024-02-29T12:11:19.1129387Z at <ScriptBlock>, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\ClientContext.ps1: line 93
2024-02-29T12:11:19.1140721Z at AwaitState, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\ClientContext.ps1: line 222
2024-02-29T12:11:19.1153066Z at OpenSession, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\ClientContext.ps1: line 200
2024-02-29T12:11:19.1162909Z at Initialize, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\ClientContext.ps1: line 61
2024-02-29T12:11:19.1173552Z at ClientContext, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\ClientContext.ps1: line 28
2024-02-29T12:11:19.1185592Z at New-ClientContext, C:\ProgramData\BcContainerHelper\Extensions\Z5236518\PsTestTool\PsTestFunctions.ps1: line 40
2024-02-29T12:11:19.1198477Z at <ScriptBlock>, C:\ProgramData\BcContainerHelper\b479c5ca-0d5b-4e47-9523-255258ed8a62.ps1: line 94
2024-02-29T12:11:19.1212787Z at <ScriptBlock>, C:\ProgramData\BcContainerHelper\b479c5ca-0d5b-4e47-9523-255258ed8a62.ps1: line 43
2024-02-29T12:11:19.1226795Z at <ScriptBlock>, <No file>: line 1
2024-02-29T12:11:29.1029334Z ClientSession State is Uninitialized (Wait time 10 seconds)
2024-02-29T12:11:29.1039151Z
2024-02-29T12:11:29.2262610Z Container Free Physical Memory: 6.0Gb
2024-02-29T12:11:29.2269498Z
2024-02-29T12:11:29.2280663Z Services in container Z5236518:
2024-02-29T12:11:29.2425198Z - MicrosoftDynamicsNavServer$BC is Running
2024-02-29T12:11:29.2458202Z - MSSQL$SQLEXPRESS is Running
2024-02-29T12:11:29.2474088Z
2024-02-29T12:11:29.8909068Z Get-TestsFromBCContainer Telemetry Correlation Id: 21c9767e-56bc-4ecd-9f8d-33992a3c19b8
2024-02-29T12:11:30.1487267Z ##[error]ClientSession State is Uninitialized (Wait time 10 seconds)
At C:\Program
Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.3\ContainerHandling\Invoke-ScriptInNavContainer.ps1:285 char:25
+                         throw $errorMessage
+                         ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (ClientSession S...ime 10 seconds):String) [], RuntimeException
    + FullyQualifiedErrorId : ClientSession State is Uninitialized (Wait time 10 seconds)
2024-02-29T12:11:30.1548133Z ##[error]PowerShell exited with code '1'.

**Additional context**
no code changes have been made, the only thing I could see different between the runs was when creating the container, looks like we're using a newer image (though I did try reverting back to the old image and still had the same issue).

This is from the first failing run:

2024-02-29T11:59:49.3463403Z Host is Microsoft Windows Server 2019 Datacenter - 10.0.17763.5458
2024-02-29T11:59:49.5061887Z Docker Client Version is 19.03.2
2024-02-29T11:59:49.5076165Z Docker Server Version is 19.03.2
2024-02-29T11:59:50.0272928Z Removing Desktop shortcuts
2024-02-29T11:59:50.4817022Z Fetching all docker images
2024-02-29T11:59:50.6601354Z Fetching all docker volumes
2024-02-29T11:59:51.2566763Z Using image mcr.microsoft.com/businesscentral:10.0.17763.5458
2024-02-29T11:59:51.4020742Z Disabling Health Check (always report healthy)
2024-02-29T11:59:51.7757405Z Creating Container Z5236518
2024-02-29T11:59:51.7768996Z Style: onprem
2024-02-29T11:59:51.7779884Z Multitenant: No
2024-02-29T11:59:51.7793565Z Version: 18.0.23013.23795
2024-02-29T11:59:51.7806000Z Platform: 18.0.22893.23773
2024-02-29T11:59:51.7821879Z Generic Tag: <IP_ADDRESS>
2024-02-29T11:59:51.7866938Z **Container OS Version: 10.0.17763.5458 (ltsc2019)**
2024-02-29T11:59:51.7877982Z Host OS Version: 10.0.17763.5458 (ltsc2019)
2024-02-29T11:59:51.7990392Z Using process isolation
2024-02-29T11:59:51.8046705Z Using locale en-GB

Note the Container OS Version

Then from the final working run:

2024-02-17T04:45:14.5917271Z Host is Microsoft Windows Server 2019 Datacenter - 10.0.17763.5458
2024-02-17T04:45:14.7591706Z Docker Client Version is 19.03.2
2024-02-17T04:45:14.7608760Z Docker Server Version is 19.03.2
2024-02-17T04:45:15.2396175Z Removing Desktop shortcuts
2024-02-17T04:45:15.7142099Z Fetching all docker images
2024-02-17T04:45:15.8406185Z Fetching all docker volumes
2024-02-17T04:45:16.4460793Z Using image mcr.microsoft.com/businesscentral:10.0.17763.5329
2024-02-17T04:45:16.6124970Z Disabling Health Check (always report healthy)
2024-02-17T04:45:16.9947754Z Creating Container Z5215218
2024-02-17T04:45:16.9961533Z Style: onprem
2024-02-17T04:45:16.9973934Z Multitenant: No
2024-02-17T04:45:16.9985407Z Version: 18.0.23013.23795
2024-02-17T04:45:16.9996741Z Platform: 18.0.22893.23773
2024-02-17T04:45:17.0011516Z Generic Tag: <IP_ADDRESS>
2024-02-17T04:45:17.0051973Z **Container OS Version: 10.0.17763.5329 (ltsc2019)**
2024-02-17T04:45:17.0065125Z Host OS Version: 10.0.17763.5458 (ltsc2019)
2024-02-17T04:45:17.0144929Z WARNING: Host OS and Base Image Container OS doesn't match and process isolation is specified. If you encounter issues, you could try to specify -isolation hyperv
2024-02-17T04:45:17.0155584Z Using process isolation
2024-02-17T04:45:17.0194065Z Using locale en-GB

But like I mentioned I tried using the .5329 image but had no luck still

does it happen all the time?
All the time for BC15, BC15.3 and BC18
did it use to work?
Stopped working on the 24th of Feb, last run before that was the 17th and that ran fine.

Please update to the latest containerhelper, retry and provide a new log
Please do format the log as code, using the toolbar like:
this is code

Yup that fixed the issue, thanks


REL: bump version to 2024.12.19a1

Summary by Sourcery
Bump version to 2024.12.19a1 and update changelog with enhancements and deprecations. Improve load balancing in parallel execution for performance gains and enhance compatibility of new_type core objects. Deprecate annotate_from_gff() methods and delay default setting of new_type to 2025.1.
Enhancements:

Improved load balancing in parallel execution of new_alignment.Alignment.distance_matrix() calculations for better performance with large sequence numbers.
Enhanced compatibility of new_type core objects with the rest of the codebase, though some issues remain.

Chores:

Updated version number to 2024.12.19a1.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.43%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
205565

Relevant Lines:
224832

💛  - Coveralls


Use better return values for elab server functions

          I don't think you need to return the status code explicitly here. In case of an error in the download I would rather raise a IOError in our function here.

Originally posted by @JuliaSprenger in https://github.com/INT-NIT/DigLabTools/pull/73#discussion_r1212816417

I can do it, yes, but don't we have to merge the GH-84 first?


Cannot update NVTs

@stu93303148, have you read https://github.com/mikesplain/openvas-docker/issues/263?
Please, verify if it helps.

Thanks your help. Updated success.


New ECO term : Radioligand binding assays recording evidence

Hi,
Here is a suggestion for a new ECO term related to a technique to prove protein binding.
Protein binding evidence; ECO_0000024
Radioligand binding assays recording evidence; ECO_xxx
Regards

Hi @FJungo! Thank you for your request. Could you provide a source for a definition for this term, such as a PMID or other published journal article?

Hi @rctauber !
Here are two papers where the protein binding is proved thanks to "radioligand binding assays": PMID:11707459 and PMID:12488533
As a definition, I suggest:
A type of affinity evidence which involves measurement of competitive binding between a protein or a protein complex and a radioligand.
Tell me if you need other papers.
Thanks

Thank you! I agree that it is a type of protein binding evidence.
It looks like there are multiple types of radioligand binding assays, one of which is the competitive binding assay. My proposal for a definition for radioligand binding assay evidence is as follows, as it appears there are different subtypes of radioligand binding assays:

A type of protein binding evidence in which radioactive ligands are used to measure receptor-ligand interactions, such as in determining selectivity for a particular ligand.

That said, I would include competitive binding assay evidence as a narrow synonym.
I also found this resource for the definition: PMID:27471749. I only mention this because it is more recent (2015) than the papers you provided (2002, 2003), but I think it gets the same idea across.
Alternative labels (synonyms):

radiometric ligand-binding assay
radioactive ligand binding assay

Many thanks Rebecca
I like your definition and completely agree with the synonym you propose.
Just one additional question, but more practical: Do you have an idea when the new term will be available in OLS ?
Best

I'm going to put it into eco-edit today. We do releases on the 1st Friday of the month, so the next release will be January 5th. That said, if it's urgently needed, I can do an unscheduled release.

Thanks. No, it's not urgent, it was just to have an idea. Thanks!

Great, I'm putting in ECO:0007008 (radioligand binding assay evidence) and ECO:0007009 (radioligand binding assay evidence used in manual assertion). I'll close this issue with that commit, but if you need anything else please just reopen!


URL Aliases aren't prioritized over previously visited websites

Please add a description of what you mean exactly.

Go to apple.com
apple.com is now in your history
A url-alias a will now no longer be prioritized over apple.com.
I don't know if this is a fixable bug due to how Chrome works, but I figured I
may as well submit an issue.
![](https://link.nylas.com/open/9amy9cwla2lax9ut4oqgujtq/3beb13d7bbf94d578c26c
a11d8135f18)
On Apr 2 2016, at 1:13 pm, Karan Goel<EMAIL_ADDRESS>wrote:

Please add a description of what you mean exactly.

—
You are receiving this because you authored the thread.
Reply to this email directly or [view it on GitHub](https://github.com/karan
/chrome-url-alias/issues/4#issuecomment-204794378)![](https://github.com/notif
ications/beacon/ALiDiKObIPUhyQ2P_rMgBsudvo6Mn8IBks5pzs3ngaJpZM4GKICw.gif)

a/ should work. Maybe not quite as nice as simply a, but seems pretty good.

What @JesusFreke said. Or you could clean your history and it will then work.

Yeah a/ works but a now just does a Google search


[WIP] Bugfixes

Needs to be tested on hardware, but it builds right now.

Benchtop testing results:

#169 fixed
#172 fixed

#170 and #171 aren't causing errors to be reported or stopping the autopilot from arming

With latest commit, #170 and #171 also work

It flew!


AsciidocFX 1.7.4 bundles old log4j 1.2.17

AsciidocFX showing up on local vulnerability reports.
AsciidocFX //lib/log4j-1.2.14.jar contains Log4J-1.X <= 1.2.17, which is considered a critical vulnerability.

Thank you, it has already been fixed.