[VL] Rename parsePartitionAndMetadataColumns to parseColumnTypes

What changes were proposed in this pull request?
Velox side row index meta data column support for parquet scan is ready https://github.com/facebookincubator/velox/pull/9174 , i am working now for gluten part chagne.
The row index column is a new addtional column handle type kRowIndex which need be passed from engine part.
This PR use to refactor  parsePartitionAndMetadataColumns to let it support parse NameStruct to store all availale column type, not only partition or metadata column into only one ColumnType vector, otherwise, for support rowindex , we need pass additional thrid bool vector to store for row index column.
(Fixes: #5047)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@zhouyuan / @rui-mo / @FelixYBW / @zhli1142015

@zhouyuan / @rui-mo / @FelixYBW / @zhli1142015

thanks @yma11 for approve, @zhli1142015 / @zhouyuan  could you help merge ?


Compilation Error:  looking for <err.h>

/Arduino/libraries/heatshrink-master/heatshrink.c:32:17:
fatal error: err.h: No such file or directory
#include <err.h>
Where can I download err.h?

What OS are you compiling on?

MacOS

Was a solution to this ever found?

You should already have err.h as /usr/include/err.h, but the build failure may have more to do with building in an Arduino context -- the Arduino platform is based on C++, not C, which impacts the build setup in many ways.
Are you building with the included makefile? heatshrink.c is the main source for the command line tool, which really doesn't make sense to build for an Arduino, but has built without issue on macOS. I haven't tried since Yosemite, though.
If that's not enough to get you unstuck, I need more details about how you're trying to build.


(TEST) IGNORE THIS PR

Testing that logic for CI works, will open another PR in main with actual PR to merge.
Summary

Changelog

Test Plan

Closing, see https://github.com/facebook/react-native/pull/35667


Exporting Transparency

Hello,
Im probably doing something wrong, but I cant get anything to export with any trans values. Any help would be much appreciated.

This seemed to be working before, but I'm now explicitly setting the alphaMode property on the material and it seems to be working again on some of the viewers that I tested.
@Miikka61, I've merged the fix in.  Please download the latest from this repo.  Let me know if you run into any issue or have any questions.


New cri-containerd after reorg is not compatible with the old one.

In cri-containerd, we use containerd/typeurl for the extra metadata we stored in container extension.
Previously the typeurl was github.com/kubernetes-incubator/cri-containerd/pkg/store/sandbox.
Now the typeurl is changed to github.com/containerd/cri-containerd/pkg/store/sandbox.
Given that cri-containerd is still beta, and Kubernetes doesn't support in-place upgrade today, it might be fine to let user drain the node before upgrading cri-containerd from beta to GA.
However, we should document this properly in the release note.

I'll update document for this. And we should also mention this in release note.


German dates and timezones

Hello,
I'm trying to use moment.js with german dates but the following problem occurs:
For example I use the Date (YYYY-MM-DD) 2015-05-15 and the following code:
<script type="text/javascript" src="bower_components/moment/moment.js"></script>
<script type="text/javascript" src="bower_components/moment/locale/de.js"></script>

var d = moment("2015-05-15", "Y-m-d", "de", true);
d.format("YYYY/mm/DD");

Format outputs: 2015-05-12
Im using PHP to calculate the date (PHP uses timezone "Europe/Berlin").
How can i fix this?

Pay close attention to the input and output format strings.  They are case sensitive, and different than PHP.
var d = moment("2015-05-15", "YYYY-MM-DD");

d.format("YYYY/MM/DD");


Deleting the cluster does not delete the backend pods on appGW

Describe the bug
A clear and concise description of what the bug is.
When I have deleted the cluster which I had AGIC on it, the appGW still shows the backend pools which were running on the deleted cluster. Now AppGW shows those pools in unhealthy status
To Reproduce
Steps to reproduce the behavior:
Delete the AKS cluster which has the AGIC, but AppGW is not able to remove the pools were running on the deleted cluster

@mhsh64 This is as expected.
When a pod is getting deleted, it gets SIGTERM and SIGKILL signals from the OS. This could happen because there is rolling update on the POD or the node is being taken down or the AKS cluster is getting deleted. Since there is no way to distinguish these events, there is no special routine in AGIC to reset the App Gateway config. If we handle delete for AKS cluster by reseting the App gateway config, it would also affect the case where you are just trying to upgrade AGIC version. So, this is by design that we don't reset the App Gateway config.

Thanks.
@akshaysngupta Have a question.
Is this possible to configure one AppGW for multiple AKS clusters? Which the pods running onthose clusters share one identical domain name.
I mean we want to have an AppGW in front of multiple Clusters (which running AGIC on each of them ). Imaging having multiple clusters for dev, multiple clusters for qa . Now we want to have one AppGW for dev and one for qa


[Bug]: Struct and Map TypeEngine subclasses are missing type information

What happened?
This is more of a feature request, but it appears that the Struct and Map types are missing type information, which makes them not so useful for type inference for duckdb inside of ibis. We have our own sqlalchemy types to deal with this, so it's not a huge problem at the moment, but I thought I'd raise it here.
DuckDB Engine Version
0.7.2
DuckDB Version
0.7.1
SQLAlchemy Version
1.4.48
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Heya,
I'd actually begun work on this after the PR yesterday already, so I'll put it up once it's ready (in the next few days hopefully), and see if it's fit for your purposes

Sounds good!


Uncaught TypeError

Error suspected on Line 79 to 89. Below is the error it keeps running in the DOM without end.
To replicate error:

Go to git checkout to frontend branch
open "Go live" server in VScode
Open DOM in browser
Click on Console tab at top of DOM
click " START" button and watch the errors fly! They should looking something like this:

jquery.min.js:2 Uncaught TypeError: w.easing[this.easing] is not a function
    at init.run (jquery.min.js:2:55877)
    at u (jquery.min.js:2:59193)
    at w.fx.tick (jquery.min.js:2:62643)
    at at (jquery.min.js:2:56980)

Resolved by Calico


IOS app goes full screen after opening the barcode scanner

Expected Behaviour
[IONIC v 2.2.2]On IOS when you open qr scanner, after scan the application goes full screen
I have set in config xml

Actual Behaviour
Application should not go full screen
Reproduce Scenario (including but not limited to)
Scanning / canceling QR Code scanning
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
IOS 10.3.2
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
iPhone 5s
Cordova CLI version and cordova platform version
cordova --version = 6.5.0
cordova platforms =

Installed platforms:
android 6.1.2
ios 4.3.1
Plugin version
phonegap-plugin-barcodescanner 6.0.6 "BarcodeScanner"

What do you mean by "app goes full screen"?

@jcesarmobile I mean the application is overlapping the status bar.

That is a bug on the statusbar plugin that was fixed long time ago, make sure you are using latest version


Fix an integer overflow during packer construction.

Hey, thanks for the PR; looks good! I'm just going to pull and test to make sure everything's good and then I'll merge it.

Actually, would you mind adding yourself to the AUTHORS file and resubmitting the PR?

Done, I amended my commit.
Another thing I've been tempted to add is the ability to specify the endianness to use, with the gopack tag.  Would you be interested?
I'm using this to decode some crappy protocol-designed-by-committee, and I found gopack very useful.  Of course most protocols use network endianness (big endian).

When you say endianness, do you mean bit or byte endianness? I'd definitely be interested, but we should discuss the design further. There are a number of ways to go about this, and there are some subtle design considerations.

Maybe submit an issue and we can discuss there?

Sure, I'll put out a proposal.

Actually, I just realized: why int and not uint64, as we were already using? Not that anyone is going to try making a 2^31- or 2^63-byte packer, but still...

Yeah I picked int out of simplicity.  Feel free to change it to whatever pleases your heart.  :)

OK, just making sure there wasn't a specific reason. Will do.


Investigate cwl-utils and deprecating this project

There have been advancements in the schema-salad to generate Python classes that more directly mirror the functionality this project provides. As a consequence, it's probably worth investigating migrating some of the generator tests to the new repo and deprecating this project.
I've used the grammar from https://github.com/common-workflow-language/cwl-utils/pull/5 for these initial tests. From migrating some of the cwlgen tests, I've noticed some differences:

Identifiers and derived fields are based on the file path are different (for the tests test_unit_import_workflow):

Current cwlgen identifier = 1stWorkflow
New cwl-utils identifier = file:///path/to/import_workflow.cwl#1stWorkflow
This affects identifier derived fields, including: format, source, run.

Some method similarities (cwlgen → cwl-utils):

get_dict() → save()
parse_cwl(cwlfile) → load_document(cwlfile)
parse_dict → No super clear analogue, but loaded through _RecordLoader(CommandLineTool) || _UnionLoader((CommandLineToolLoader, ...workflow + other loaders)

Additionally, to avoid conflicting with Python keywords we made some specific keyword changes when creating cwlgen, here's how some at least might be mapped back on the initialiser.

tool_id | workflow_id | input_id | etc→id`
StepInput: inputs→in_`

Other little differences (more investigation required):

Optional fields don't default to None on init_, which means you'd always have to include them. Refer to https://github.com/common-workflow-language/schema_salad/issues/262 for more information.
After save(), requirements is a `List[CommentedMap] == ordereddict[] which I don't know how to unit test..

The big difference is that any issues can be solved by regenerating the file based on the schema-salad definition of CWL, so it should always be right. When I get a chance, and once optional init fields are in schema-salad I'd be interested in migrating a real world project to using it.
FYI @mr-c

So we're still waiting for schema_salad to support optional args before cwl-utils is particularly usable?

@TMiguelT It is usable now, just annoying to have to specify None everywhere. See https://github.com/common-workflow-language/schema_salad/issues/262 for more details

Dear all,
I've fixed the related issues, and now cwl-utils is the recommended approach for generating (and parsing) cwl. It's generated right from the spec so you can have confidence it's right and has support for every version of CWL.
My notes above will guide you on the migration path, but a few notes:

The parameters are named with camelCase and not snake_case like we've generally used.
Take care if you're migrating to a newer spec, as some classes might have changed names (notably: InputParameter -> WorkflowInputParameter)
Don't forget to catch all references of cwlgen, as missing one will cause:raise RepresenterError('cannot represent an object: %s' % (data,))
ruamel.yaml.representer.RepresenterError: cannot represent an object:
<cwlgen.common.CommandInputArraySchema object at 0x1100a5780>

None of my tests failed because of the List[CommentedMap] == ordereddict, I do use self.assertDictEquals.

I migrated my project Janis, which heavily relied on this library, and it only took a few hours: https://github.com/PMCC-BioinformaticsCore/janis-core/pull/21/files. If you have questions, feel free to tag me in this issue or send me a message. Gitter is the best place for this.

Also, come along this Tuesday to the CWL call where I'll talk about the changes I've made and we'll discuss cwlgen and what will happen to it.

I marked this issue for closing, but reopening as a placeholder.


SunsetAtSea-Irtaza

[x] I have read the steps to getting a blot

[x] I am submitting art that...

[x] is algorithmically generated (will change each time the program is run)
[x] is drawable on a blot (fits in the work area & doesn't overlap too much)
[x] is original (not copied from somewhere else)

[ ] Optional, if you used a tutorial or based your art on something else, please include the link here:

[x] Optional, if you remixed this from something else, mention it here: I got the idea for the birds from this blot art in the gallery

Sunset At Sea
I created a Sunset scene at the sea with some sailboats and randomly placed birds. It was my first time using a drawing library and drawing using a programming language, thus I wrote the code using the .Turtle() function, which I understood the most easily.
Here is an image of what my code can generate:

I have added all of your recommendations! I hope it looks better now!

I fixed it!

Seeing as this hasn't been updated in over a month, I'm going to close the PR for now. You're free to make a new one in the future with the same artwork if you'd like! Reach out to me @ alexren on the slack if you have any questions!


when will the data be released

Hi, thanks for the great work. And when will the data be released?

please remember to call me after the cvpr2022 deadline (Nov. 23) .

Really nice work, hope for the release

Really nice work, hope for the release too.

The dataset has been released, please drop a email to<PHONE_NUMBER> at qq dot com to obtain the well-defined dataset.


failure when deleting a transfer

Describe the bug
When trying to delete a transfer, a failure will happen due to a foreign key constraint, here's the log:
  1) test delete (TransfersLiveTest)
     test/countbean_web/lives/transfers_test.exs:63
     ** (EXIT from #PID<0.22080.0>) an exception was raised:
         ** (Ash.Error.Unknown) Unknown Error

     * ** (Ecto.ConstraintError) constraint error when attempting to delete struct:

         * "balances_transfer_id_fkey" (foreign_key_constraint)

     If you would like to stop this constraint violation from raising an
     exception and instead add it as an error to your changeset, please
     call `foreign_key_constraint/3` on your changeset with the constraint
     `:name` as an option.

     The changeset defined the following constraints:

         * "transfers_pkey" (unique_constraint)

       (ecto 3.11.1) lib/ecto/repo/schema.ex:815: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3
       (elixir 1.15.7) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
       (ecto 3.11.1) lib/ecto/repo/schema.ex:799: Ecto.Repo.Schema.constraints_to_errors/3
       (ecto 3.11.1) lib/ecto/repo/schema.ex:780: Ecto.Repo.Schema.apply/4
       (ecto 3.11.1) lib/ecto/repo/schema.ex:571: anonymous fn/13 in Ecto.Repo.Schema.do_delete/4
       (ash_postgres 1.3.64) lib/data_layer.ex:2178: AshPostgres.DataLayer.destroy/2
       (ash 2.17.9) lib/ash/actions/destroy.ex:328: anonymous fn/9 in Ash.Actions.Destroy.as_requests/5
       (ash 2.17.9) lib/ash/changeset/changeset.ex:2209: Ash.Changeset.run_around_actions/2
       (ash 2.17.9) lib/ash/changeset/changeset.ex:1808: anonymous fn/3 in Ash.Changeset.with_hooks/3
       (ecto_sql 3.11.1) lib/ecto/adapters/sql.ex:1358: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4
       (db_connection 2.6.0) lib/db_connection.ex:1710: DBConnection.run_transaction/4
       (ash 2.17.9) lib/ash/changeset/changeset.ex:1806: anonymous fn/3 in Ash.Changeset.with_hooks/3
       (ash 2.17.9) lib/ash/changeset/changeset.ex:1936: anonymous fn/2 in Ash.Changeset.transaction_hooks/2
       (ash 2.17.9) lib/ash/changeset/changeset.ex:1787: Ash.Changeset.with_hooks/3
       (ash 2.17.9) lib/ash/actions/destroy.ex:303: anonymous fn/9 in Ash.Actions.Destroy.as_requests/5
       (ash 2.17.9) lib/ash/engine/request.ex:1111: Ash.Engine.Request.do_try_resolve_local/4
       (ash 2.17.9) lib/ash/engine/request.ex:284: Ash.Engine.Request.do_next/1
       (ash 2.17.9) lib/ash/engine/request.ex:213: Ash.Engine.Request.next/1
       (ash 2.17.9) lib/ash/engine/engine.ex:712: Ash.Engine.advance_request/2
       (ash 2.17.9) lib/ash/engine/engine.ex:637: Ash.Engine.fully_advance_request/2
             (ash 2.17.9) lib/ash/error/error.ex:524: Ash.Error.choose_error/2
             (ash 2.17.9) lib/ash/error/error.ex:252: Ash.Error.to_error_class/2
             (ash 2.17.9) lib/ash/actions/destroy.ex:148: Ash.Actions.Destroy.do_run/4
             (ash 2.17.9) lib/ash/actions/destroy.ex:37: Ash.Actions.Destroy.run/4
             (ash 2.17.9) lib/ash/api/api.ex:2221: Ash.Api.destroy!/3
             (countbean 0.1.0) lib/countbean_web/live/transfer_live/index.ex:101: CountbeanWeb.TransferLive.Index.handle_event/3
             (phoenix_live_view 0.20.1) lib/phoenix_live_view/channel.ex:487: anonymous fn/3 in Phoenix.LiveView.Channel.view_handle_event/3
             (telemetry 1.2.1) /home/tw/code/countbean/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
             (phoenix_live_view 0.20.1) lib/phoenix_live_view/channel.ex:246: Phoenix.LiveView.Channel.handle_info/2
             (stdlib 5.1.1) gen_server.erl:1077: :gen_server.try_handle_info/3
             (stdlib 5.1.1) gen_server.erl:1165: :gen_server.handle_msg/6
             (stdlib 5.1.1) proc_lib.erl:241: :proc_lib.init_p_do_apply/3

You could reproduce this issue using the default transfer live generated by mix ash_phoenix.gen.live API Transfer, and click the delete button on the web.
After a quick look at the lib/transfer/changes/verify_transfer.ex, I think we should handle the destroy action properly.

I think at the current moment it's not accounting for deleting transfers, but there isn't a reason that we can't account for it. We'll need to first delete any balances associated with that, and then verify the balances again.

Just pushed a new version that supports destroying transfers. Something we don't currently support (and may not ever support?) is updating transfers. Although...we can support it potentially as long as the amount, to or from account id isn't changing...will do that later.

Alright, pushing a new version that support modifying fields aside from the source/destination of the transfer, the amount, or the id.

nice👍 thanks @zachdaniel


Add tests for new Datacollector Configuration usage

To support the new fakes implementation, a new configuration generator was added which is retrieved from FakesUtilities.TryGetFakesDataCollectorConfigurator(out Func<IEnumerable<string>, bool, DataCollectorSettings> configurator) in this #2339 .
Tests for this need to be added once the new Fakes implementation is pushed.

@vritant24 If you have some time to add these tests, that would be awesome!


Stack test hanging

Stack test hangs toward the end while attempting to remove a network:
$ go test -v github.com/appcelerator/amp/api/rpc/stack
..... lots of tests passing ....
Stopping stack a2170c0d58780278d0feaa779560291012561e670dd3184100e30fe752374e5a
Service removed 263mpbo8qv8ezql7qp87xg2wo
Service removed e28sysl9xc0dmf67fhu86sq6b
Service removed 3bi9cnxs7t7drwvnuelfpdq0y
Service removed 4fp6prxra265dq33pqlknjdz3
Removing network: b4fkbc4sir6jtwebpchvmph6v
...HANGS.....

At the same time, other Docker operations appear to be blocked (such as docker network ls). This is possibly related to this issue, which has been fixed here and due to be released with Docker 1.12.3.
When this happens, the only way to get out of this state is to restart the docker engine. Sometimes, that's not enough for Docker for Mac (Version 1.12.2-beta28 (12906)) and requires resetting to initial settings (losing all cached images).
If this issue can't be resolved now, then we should at least ensure the operation context has a timeout so that the process doesn't hang indefinitely.

Some observations regarding this issue:

the stack test which shows the issue is a test on network stack 1 feature (creating private and public network and remove them during stack up and stop)
it happened after moving to docker 1.12.2, on docker 1.12.1 we won't get hanging so often using stacks
it's not systematic, but it happened for sure after a while. we make tests run with success on Ubuntu and mac, but after a given number of repetition, we got docker hanging
the hanging in Docker internal, there is no way to prevent it, removing a network seems enough to trigger it
Tack i propose to dig on:
verify if the docker hanging is related to some specific network parameters
verify if the docker hanging is related to the way the network are created trying to get docker hanging with only network docker commands

These updates have been done to lower the docker freeze risk:

wait after deleting a service that the service is well deleted
wait afer deleting a network that the network is well deleted

Even, with the previous update, the freeze continue to happend to often, so this workaround have been temporary apply, until the 1.12.3 fix the docker issue:

do not delete network
when a network is created if it already exist, it's reused

The freeze frequency lower a lot with this workaround, it still occur on a network ls this time.

Fixed by Docker 1.12.3 and PR#389


Dashboard release branches should show LUCI task results for that branch, not prod

Release branches show LUCI tasks for prod instead of the relevant branch.

Related to https://github.com/flutter/flutter/issues/51807
\cc @CaseyHillers

FYI the way LUCI determines which builder group to use via a regex against the git refs in the flutter/infra config: https://github.com/flutter/infra/blob/master/config/main.star#L20
HOTFIX_REFS = 'refs/heads/v.+hotfixes'

Since everything is now standardized in the ci.yaml, this should be do-able (previously it was non-trivial to get the builders for a branch)

Closing as the Cocoon scheduler migration is complete.
Starting for releases after 3.3, this will be complete (granted we may CP these changes into 3.3)


Preparing Staging Env Incase Needed

Synk vulnerabilities all marked as caused by the .NET Framework Version with no mitigations available.  Marked approved.


Remove remnant EntityHash and related types from bevy_utils

Objective
EntityHash and related types were moved from bevy_utils to bevy_ecs in #11498, but seemed to have been accidentally reintroduced a week later in #11707.
Solution
Remove the old leftover code.

Migration Guide

Uses of bevy::utils::{EntityHash, EntityHasher, EntityHashMap, EntityHashSet} now have to be imported from bevy::ecs::entity.

1dtgr6~~``7nff```98djhoik@alice-i-cecile ex oh hk  ocy 5ggcckyx67`


GDNative memory leak upon passing any Array

Similar to issue #19676
Godot version:

Still active in commit e9be875 of Godot, 0220045 of godot-cpp.
OS/device including version:
Arch Linux x64, with proprietary NVIDIA drivers.
Issue description:
Passing any array to a GDNative function causes a memory leak, as the array never gets freed.
The Array class causes a constant increase in static memory according to the debugger.
The PoolArray classes cause a constant increase in dynamic memory according to the debugger, and eventually causes a stack overflow after enough function calls (which is static memory; are these two stats switched around?).
Steps to reproduce:
void MyClass::memory_leak(Array anythingNotEmpty) {
  // Do nothing
}

Open the debugger in the editor when calling this function with an array of size >0. Go to Monitors->Memory->Static/Dynamic. Watch as your memory slowly (or quickly, depending on the size of the array) leaks away into oblivion. Faster for larger arrays. Weirdly, passing in the array as a Variant fixes the leak, but casting it back into an Array makes it leak again.
Minimal reproduction project:
Attached. I kept thinking my constant stack overflow segfaults were an issue with my C++ coding, until I switched from using PoolVector2Array to Array and my project ended up taking up a total of 8GB of RAM after a few minutes (all static).
Godot_Memleak.zip

I think this bug is same with #29128. Pass Array or PoolByteArray  to c++ will memory leak

Oof, this is a bad one.
Is there any way around this, for the time being?
E.g., does it still leak when you pass the array as a Variant?

This is really a bad one. Basically making use of Arrays impossible in GDNative.
Anyone having an idea what the cause of this could be?

I found a commit(https://github.com/GodotNativeTools/godot-cpp/pull/355/commits/95feb486c9968c4489f092df4232326d8ab7debf) in godot-cpp can fix this bug, The cast implicitly calls the C++ type's copy constructor. (You can find it in the gdb disassembly.) This increases the ref-count twice instead of just once through godot_variant_as_*. For PoolArrays, it caused an error message on exiting Godot

Fixed by GodotNativeTools/godot-cpp#355.

Is there any fix for this in the C version?


Dark mode for Invisible variant

Hi @sarneeh, firstly I'd like to thank you for implementing reaptcha, it works great and is a true pleasure to use.
Not sure if it's an issue however, is there a reason why dark mode is not accessible when using Invisible variant of the ReCaptcha? Is it just an oversight?
https://github.com/sarneeh/reaptcha/blob/3ac319111e08fd0fc75e36d8275289fa78c5c2f6/lib/index.js#L144
Thanks,
Tom

@id-kemo I'm happy you like it! :smile:
According to the dark mode... how does the invisible captcha behave in dark mode? Does the floating ReCAPTCHA indicator show in dark? If yes, that's surely an oversight :)

@sarneeh yes it does - I have only tried simple change from rc-anchor-light to rc-anchor-dark and it works as expected.

Published in 1.5.0. Thank you @id-kemo!


[BUG] Screen touch on mobile devices results in TypeError

How to reproduce:

open any room on mobile device or in chrome in development mode as mobile device
do any touch on player screen
got an error

TypeError: this is not a Date object.
    at getTime (<anonymous>)
    at so (framework-5f4595e5518b5600.js:1:60187)
    at co (framework-5f4595e5518b5600.js:1:60641)
    at Object.useState (framework-5f4595e5518b5600.js:1:66579)
    at t.useState (framework-5f4595e5518b5600.js:1:125433)
    at l ([id]-c3e0dd1c96b5a8f3.js:1:1445)
    at oo (framework-5f4595e5518b5600.js:1:59412)
    at Wo (framework-5f4595e5518b5600.js:1:68979)
    at Ku (framework-5f4595e5518b5600.js:1:112703)
    at Li (framework-5f4595e5518b5600.js:1:98953)

TypeError: this is not a Date object.
    at getTime (<anonymous>)
    at so (framework-5f4595e5518b5600.js:1:60187)
    at co (framework-5f4595e5518b5600.js:1:60641)
    at Object.useState (framework-5f4595e5518b5600.js:1:66579)
    at t.useState (framework-5f4595e5518b5600.js:1:125433)
    at l ([id]-c3e0dd1c96b5a8f3.js:1:1445)
    at oo (framework-5f4595e5518b5600.js:1:59412)
    at Wo (framework-5f4595e5518b5600.js:1:68979)
    at Ku (framework-5f4595e5518b5600.js:1:112703)
    at Li (framework-5f4595e5518b5600.js:1:98953)

My proposal on resolving this bug is implemented here: https://github.com/Web-SyncPlay/Web-SyncPlay/pull/14


Add description

Can you add a description to the package so we know what it's for? I was about to share it, but there's no info to help the dev know what it is and how to use it

@ThinkDigitalSoftware You mean more content in the README? Yeah, that is a bit lacking right now...

Yes please :)

yes please, I am new and can't build complex query. how to build a complex query?

if you could show me some way to build query like following, I am willing to contribute to your repository, I am new to Dart, but working with elastic from many years.
my question is this.
`My user search
"the avenger infinity war"
so i need complex query in three part
Part 1: importance 1.5
phrase search : "the avenger infinity war"
PArt 2: importance 1.0
Word search "the" and "avenger" and "infinity" and "war"
PArt 3: importance 0.5
Fuzzy search
"the"~0.5 and
"avenger"~0.5 and
"infinity"~0.5 and
"war"~0.5
combining this search to one. well i am willing to contibute if you show me some way to build this, in string version i can made this, but don't know how to build in Map<dynamic,dynamic>

is there any way, just a small hint will also be much helpful.
	`


@import inside a selector (feature request)

Allowing imports inside of selectors would open up an awesome collection of possibilities for code reuse and style scoping.  Something like:
.foo{
    @import "bar";
}

Would prove especially useful for creating less modules for CSS backed widgets. For example, if I author e.g., AutoRotator and a StackContainer and had the ability to nest imports inside selectors, then I could do:
# AutoRotator/pane.less
.pane{
    border: 1px solid gray;
    width: 300px;
    /* etc. ... */
}

# StackContainer/pane.less
.pane{
    border: 1px solid orange;
    width: 200px;
    /* etc. ... */
}

And the user of either library would be able to decide the scope of the various styles like:
# main.less
.myRotator {
    @import "AutoRotator/pane";
}

# main.less
.myStack {
    @import "StackContainer/pane";
}

Notice how simple the selectors seem inside the files. I think this basically just simulates http://www.w3.org/TR/css3-namespace/

+1. Would definitely be helpful.

+1

+1
Please add this!

I've found a dirty hack to allow namespaced imports. Just comment the following lines:
https://github.com/cloudhead/less.js/blob/master/lib/less/tree/ruleset.js#L20
and
https://github.com/cloudhead/less.js/blob/master/lib/less/tree/ruleset.js#L27
to look like
// Evaluate imports
//if (ruleset.root || ruleset.allowImports) {
    for (var i = 0; i < ruleset.rules.length; i++) {
        if (ruleset.rules[i] instanceof tree.Import) {
            Array.prototype.splice
                 .apply(ruleset.rules, [i, 1].concat(ruleset.rules[i].eval(env)));
        }
    }
//}

But I have no clue what this also affects on compiling. I've done a small test with bootstrap from Twitter:
#test {
  @import "../../bootstrap/less/bootstrap";
}

Compiles down to:
#test article,
#test aside,
#test details,
#test figcaption,
#test figure,
#test footer,
#test header,
#test hgroup,
#test nav,
#test section {
  display: block;
}
...

And It has worked in my case. Can anyone confirm this on a larger project?
@cloudhead Why is importing only executed on the root level? And why is ruleset.allowImports always undefined and how can I overwrite it to be always true? :)
Thanks

Here's the patched fork:
https://github.com/marcboeker/less.js/commit/5a2bdbcdaa03b7ded032f7a484f7f9843416fe8d
Just checkout and do a npm install less.js
-Marc

@marvboeker awesome, thanks for pointing this out

*marc sorry

gonna fix this

@cloudhead +1 & thanks

allowImports is used for @media blocks... but I guess there is no reason why it shouldn't be allowed in any block.

Ah yes, there was a reason, it's a performance issue. I'll see if I can add a cli flag.

Ok, done.. it's on by default, as performance hit was not that high.. option to disable is --strict-imports

Thanks! This is a great improvement.

Thanks @marcboeker and @cloudhead Saved me a ton of work with this change. :)


Add install step

Currently, use of the library is quite cumbersome for us because it's lacking an install step.
This PR ensures that make install works correctly, and that users can reliably find it using find_package after make install has completed without any additional files or work.

Coverage remained the same at 96.231% when pulling cd5659bfa47308f8bab0250888c01902ecce179d on timrae:add-install-target into 4d6356f700833d6fd6fbdb4a8ec74457401d74c7 on SRombauts:master.

Coverage remained the same at 96.231% when pulling 8387b594eb42f089c0a5b4979bc62b152efff5db on timrae:add-install-target into 4d6356f700833d6fd6fbdb4a8ec74457401d74c7 on SRombauts:master.

Hi, thanks for this!

Hey @timrae, could you please have a look of the issue with this "install" step I have just discovered?
Cheers!

Ok I'll try and take a look!

Does the issue only occur with #111 or even without it?

The error occurs only with #111 si I commented if out temporarily

I think it's more usual for library users to link in both libraries, no?


multi language support

Do you plan to release multiple language support on the lapce? for example, Portuguese, would it be possible to do this with plugins? if yes, how? would it be difficult? would I be able to do?

See https://github.com/lapce/lapce/issues/2053


Added documentation

:white_check_mark: Build windows-openstack-imaging-tools 1.0.70 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/a83593e075 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.71 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/a4f19d0bc0 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.72 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/92ebb428a9 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.73 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/32a3620317 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.74 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/2fb37d18a8 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.75 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/3b2ddfe7d2 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.76 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/5df61ef644 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.77 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/c079f9491f by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.78 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/4cbabd6cb3 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.79 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/d30ca67412 by @ader1990)


  Sooo let's leave out those changes.  There's also something weird going on where it's trying to load RespiraWorks.lib but with a few of the slashes in the path missing.

  Sooo let's leave out those changes.  There's also something weird going on where it's trying to load RespiraWorks.lib but with a few of the slashes in the path missing.

Looks like there was an extra "../" added to all the paths in sym-lib-table and fp-lib-table for some reason (do you have Ventilator checked out in the same place as KiCad-Library?).

Looks like there was an extra "../" added to all the paths in sym-lib-table and fp-lib-table for some reason (do you have Ventilator checked out in the same place as KiCad-Library?).

Ok.  So I went and did a lot of search-and-replace (gotta love text files) and now it should be ok-ish.  But LET'S NOT DO THAT AGAIN :)

Check your folder locations.  If, as the KiCAD wiki page says, you have Ventilator in the same directory as KiCad-Library then you shouldn't need to change any of the paths.  I'm suspicious of something having gotten accidentally moved because of the extra "../" that was apparently needed on your end.
Don't say "yes" if KiCAD offers to move some things to a "rescue" library, it means there's something wrong
Look at the files that git is showing as changed, before committing: if it changes a ton of schematic sheets you haven't touched (and it's not just re-numbering the schematic sheets) then there's something wrong

Ok.  So I went and did a lot of search-and-replace (gotta love text files) and now it should be ok-ish.  But LET'S NOT DO THAT AGAIN :)

Check your folder locations.  If, as the KiCAD wiki page says, you have Ventilator in the same directory as KiCad-Library then you shouldn't need to change any of the paths.  I'm suspicious of something having gotten accidentally moved because of the extra "../" that was apparently needed on your end.
Don't say "yes" if KiCAD offers to move some things to a "rescue" library, it means there's something wrong
Look at the files that git is showing as changed, before committing: if it changes a ton of schematic sheets you haven't touched (and it's not just re-numbering the schematic sheets) then there's something wrong

(And sorry if that came off as harsh, it really wasn't meant to)
As for the stepper driver schematic, looks good for the most part, only issues were:

There's a broken wire on pin 16 (~FLAG) at the bottom right
I'd vote to change the "D2" and "D4" off-sheet connectors to something more descriptive, not a fan of the original FoundryM naming there
LEDs should get a footprint assigned: should these be little 0805-size ones, as they're just living on the board for debug? (there's already a footprint in RespiraWorks_Std).  In that case the 330-ohm resistors for ~FLAG and ~BUSY/SYNC should also be a lot larger (1K or more); the little guys are super efficient and get plenty bright on only 1 mA or even less.
Get rid of serial comms jumpers?
Change all the really-small component value text to the standard 1.27 mm
Is there a reason to have +12V_Step1 as a separate net if it's all still connected to +12V anyways?  Maybe we should take advantage of that and put a 1206-size 0-ohm jumper in between +12V and +12V_Step1 to do current measurements later?
Looks like the diode on VSREG which connects to itself can be deleted?
The SW off-sheet connector's actually an input (and should probably be 1.27 mm like the other labels)
Since there doesn't seem to be a case where OSCIN and OSCOUT actually should get connected together (see section 7.8, page 29 in datasheet), maybe the DNP resistor between them should get replaced by a testpoint on each pin instead.
The power supply connections are a bit confusing in the datasheet, but it looks like if we're using both the internal regulators for gate drive (Vcc) and internal logic (Vreg), then Vccreg shouldn't be connected to Vreg (Vccreg is the input to the internal Vreg regulator, and Vreg is the output), and instead Vccreg should be connected to Vcc.  Alternatively, maybe we could supply the internal logic directly from +3.3V_Ctrl (Vreg = +3.3V_Ctrl, not sure what to do with Vccreg in that case).  Vccreg's max voltage is the same as the gate driver voltage (Vcc), so that's why it's connected to Vcc in the recommended application schematic, instead of directly to the input power.  See figure 4 on page 21 of the datasheet, and section 2.2 on page 11.
Probably worth adding the datasheet-recommended RC filter to the SW pin, can be bypassed (R=0, C=DNP) for now.
I'm a little confused by the Schottkys on the internal power rails, and why one of them has a 0-ohm series resistor.  Only thing I can think of is to forcibly discharge the caps when the main power rails go down, if residual voltages do some weird power-sequencing stuff on the way out otherwise?  Will look at the powerstep01 shield docs to see if that explains.

(And sorry if that came off as harsh, it really wasn't meant to)
As for the stepper driver schematic, looks good for the most part, only issues were:

There's a broken wire on pin 16 (~FLAG) at the bottom right
I'd vote to change the "D2" and "D4" off-sheet connectors to something more descriptive, not a fan of the original FoundryM naming there
LEDs should get a footprint assigned: should these be little 0805-size ones, as they're just living on the board for debug? (there's already a footprint in RespiraWorks_Std).  In that case the 330-ohm resistors for ~FLAG and ~BUSY/SYNC should also be a lot larger (1K or more); the little guys are super efficient and get plenty bright on only 1 mA or even less.
Get rid of serial comms jumpers?
Change all the really-small component value text to the standard 1.27 mm
Is there a reason to have +12V_Step1 as a separate net if it's all still connected to +12V anyways?  Maybe we should take advantage of that and put a 1206-size 0-ohm jumper in between +12V and +12V_Step1 to do current measurements later?
Looks like the diode on VSREG which connects to itself can be deleted?
The SW off-sheet connector's actually an input (and should probably be 1.27 mm like the other labels)
Since there doesn't seem to be a case where OSCIN and OSCOUT actually should get connected together (see section 7.8, page 29 in datasheet), maybe the DNP resistor between them should get replaced by a testpoint on each pin instead.
The power supply connections are a bit confusing in the datasheet, but it looks like if we're using both the internal regulators for gate drive (Vcc) and internal logic (Vreg), then Vccreg shouldn't be connected to Vreg (Vccreg is the input to the internal Vreg regulator, and Vreg is the output), and instead Vccreg should be connected to Vcc.  Alternatively, maybe we could supply the internal logic directly from +3.3V_Ctrl (Vreg = +3.3V_Ctrl, not sure what to do with Vccreg in that case).  Vccreg's max voltage is the same as the gate driver voltage (Vcc), so that's why it's connected to Vcc in the recommended application schematic, instead of directly to the input power.  See figure 4 on page 21 of the datasheet, and section 2.2 on page 11.
Probably worth adding the datasheet-recommended RC filter to the SW pin, can be bypassed (R=0, C=DNP) for now.
I'm a little confused by the Schottkys on the internal power rails, and why one of them has a 0-ohm series resistor.  Only thing I can think of is to forcibly discharge the caps when the main power rails go down, if residual voltages do some weird power-sequencing stuff on the way out otherwise?  Will look at the powerstep01 shield docs to see if that explains.

I think the diodes are there for protecting the internal regulators from reverse-conduction by making sure that as the input voltage comes down, it pulls the output down too for each one.  So it doesn't need the 0-ohm in series with VCC.
The power connections are still confusing.  The nucleo shield connects VCCREG and VREG together, unless ST's schematic is wrong, but that doesn't make any sense from what the datasheet says or shows.

I think the diodes are there for protecting the internal regulators from reverse-conduction by making sure that as the input voltage comes down, it pulls the output down too for each one.  So it doesn't need the 0-ohm in series with VCC.
The power connections are still confusing.  The nucleo shield connects VCCREG and VREG together, unless ST's schematic is wrong, but that doesn't make any sense from what the datasheet says or shows.

One final thing: it looks like the changes to the indicators, UI computer, and cycle controller sheets are also included in this branch, which kind of defeats the purpose of separating the PRs/branches (especially since those other branches either have or will be getting their own changes).  I'm not sure how to remove a set of file changes from an existing branch, or I'd remove those....

One final thing: it looks like the changes to the indicators, UI computer, and cycle controller sheets are also included in this branch, which kind of defeats the purpose of separating the PRs/branches (especially since those other branches either have or will be getting their own changes).  I'm not sure how to remove a set of file changes from an existing branch, or I'd remove those....

Might be useful to pull my notes over from the previous PR:
Stepper Driver:

Recommend porting SDI and SDO directly to the hierarchical connectors. No need for resistor selection of daisy-chaining since we can do that directly on the parent page.
Recommend porting the stepper outputs to hierarchical connectors so that we can either (a) make the connectors different, or (b) have both steppers on one connector. Either of these options will make it less likely to accidentally swap the steppers.
We should pipe out SW to the connector pins (and include GND and 3.3V at the connector) so that we can use it for a future homing sensor.
VSREG (source for gate drive regulator) should be connected to 12V input power directly.
Make sure to call out voltage on the caps that need to handle 12V, recommend 25V caps.
VCCREG, VREG, and VDDIO should all be connected to 3V3 rail, with sufficient decoupling capacitance. (ref design has 220nF + 22uF on VREG and 100nF on VDDIO). Diode should go from 3V3 to VCC (not mentioned in datasheet, but present in ref design, probably for power sequencing protection)
Be careful about putting DNP text on components without putting DNP into the actual parameters of the part. This can pass silently into the BOM and the assembly house will not know. (ADCIN resistor bridge and elsewhere)

Might be useful to pull my notes over from the previous PR:
Stepper Driver:

Recommend porting SDI and SDO directly to the hierarchical connectors. No need for resistor selection of daisy-chaining since we can do that directly on the parent page.
Recommend porting the stepper outputs to hierarchical connectors so that we can either (a) make the connectors different, or (b) have both steppers on one connector. Either of these options will make it less likely to accidentally swap the steppers.
We should pipe out SW to the connector pins (and include GND and 3.3V at the connector) so that we can use it for a future homing sensor.
VSREG (source for gate drive regulator) should be connected to 12V input power directly.
Make sure to call out voltage on the caps that need to handle 12V, recommend 25V caps.
VCCREG, VREG, and VDDIO should all be connected to 3V3 rail, with sufficient decoupling capacitance. (ref design has 220nF + 22uF on VREG and 100nF on VDDIO). Diode should go from 3V3 to VCC (not mentioned in datasheet, but present in ref design, probably for power sequencing protection)
Be careful about putting DNP text on components without putting DNP into the actual parameters of the part. This can pass silently into the BOM and the assembly house will not know. (ADCIN resistor bridge and elsewhere)

Because it's no secret that the ST datasheet and reference design are confusing AF, please accept this crude drawing of what I think the power configuration should be (we're bypassing the VREG internal regulator and supplying it with our own 3.3V, which also happens to be the VDDIO voltage.  There's a diode to enforce power sequencing on Vcc.  Decoupling caps for each pin, and a bulk 22uF in the area for the whole circuit).

Because it's no secret that the ST datasheet and reference design are confusing AF, please accept this crude drawing of what I think the power configuration should be (we're bypassing the VREG internal regulator and supplying it with our own 3.3V, which also happens to be the VDDIO voltage.  There's a diode to enforce power sequencing on Vcc.  Decoupling caps for each pin, and a bulk 22uF in the area for the whole circuit).

Note I also think we're going to need the nCS signal connected for SPI, so I think that DNP resistor can be a 0ohm

Note I also think we're going to need the nCS signal connected for SPI, so I think that DNP resistor can be a 0ohm

are VDD and VDDIO interchangable in this datasheet?

are VDD and VDDIO interchangable in this datasheet?

but makes sense about vreg! I'll make some mods and add a little text about that

but makes sense about vreg! I'll make some mods and add a little text about that

VDD is internal logic power, VDDIO is the reference for the SPI interface.
In our case both are 3.3V, but if the uC IO voltage was 2.5V for example,
VDDIO would be 2.5V.  VCC is the FET gate driver power.
On Sat, Jan 30, 2021 at 12:56 PM stephmusinsky<EMAIL_ADDRESS>wrote:

are VDD and VDDIO interchangable in this datasheet?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/RespiraWorks/Ventilator/pull/988#issuecomment-770279334,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCCNNNGKG6TK24OFVIGCZLS4RXBDANCNFSM4WP2G5UQ
.

VDD is internal logic power, VDDIO is the reference for the SPI interface.
In our case both are 3.3V, but if the uC IO voltage was 2.5V for example,
VDDIO would be 2.5V.  VCC is the FET gate driver power.
On Sat, Jan 30, 2021 at 12:56 PM stephmusinsky<EMAIL_ADDRESS>wrote:

are VDD and VDDIO interchangable in this datasheet?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/RespiraWorks/Ventilator/pull/988#issuecomment-770279334,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCCNNNGKG6TK24OFVIGCZLS4RXBDANCNFSM4WP2G5UQ
.


how can i delete existing api chat history

I can`t access that , soon reach token limit, how can i delete all talk history? there should be a file or a setting button to delete it
and why it has the right to reset my all plugin

oh my god what the hell it is doing
using whisper voice to edit plane and some random Japanese test show up and change my blender scene

New version has been pushed so you can clear chat history now.  Closing for now, pls feel free to re-open if there is a major issue with the features, cheers.


Documentation for active class on buttons?

I'm looking in the documentation for the active class to be used on buttons, and while it works as expected, I can't find it anywhere.
Our website (Canadian Institutes of Health Research) is currently working with the Web Experience Toolkit framework which will be migrating to Bootstrap in the next major release.
In the current iteration, buttons have no active class (you cannot create a “pushed” state) but we want to implement it to create a Pills-like navigation, which we're currently using with some sort of a hack (see: https://github.com/wet-boew/wet-boew/issues/2890).
Obviously, since we're going to be using Bootstrap, we don't want to reinvent the wheel, and we're really glad to see the active class already exists, although there's no documentation for it (as far as I know, anyway).
Our other issue, or question if you will, is the preferred approach we should take to create such a navigation, because Bootstrap doesn't use the same methodology.
Namely, Bootstrap Pills use the active class on the list item to create what looks like a reserved color segmented control, similar to the one used in iOS 7:

Home

Profile

Messages

To achieve our desired style, we'd use it this way, but I'm not sure this is compliant with Bootstrap at all; looking for comments on this:

2013

2012

2011

We also remove the href, which tells the user this is a placeholder link, and add a bunch of WAI-ARIA code because we have very strict accessibility requirements as the Government of Canada, but I haven't included this here given it doesn't seem to be part of Bootstrap's development.
If the a element has no href attribute, then the element represents a placeholder for where a link might otherwise have been placed, if it had been relevant, consisting of just the element's contents.
WHATWG - HTML Living Standard - The a element
This all readily works in Bootstrap 3, minus the cursor which remains a "pointer" while it should go back to "default" when the href is removed, so it almost seems as if it's actually a supported scenario, but I think it's by accident.
We want to do something similar for the pagination.
Now, it's somewhat obvious that this is not the correct solution at all, so I'd like to get feedback on this. What would be the best approach? Should we / is it possible to change the style of the Pills and Pagination to something which looks like OS X's segmented controls instead of iOS 7's?

OMG

What's up, @Bartmax? :)


Syntax errors and globals are not being catch with the new version

I was already getting this issue for some days and seemed to be solved deactivating the beta version.
I tried opening a single Lua file, and no matter what non-sense thing I code, errors are not showing up.

v1.0.6 with beta disabled work as expected

I'm using MacOS with Big Sur installed.
I don't get any error message nor warning from VSC.

Can confirm the same thing on Neovim (built-in client) and GNU/Linux (Void). Attached screenshot shows non-beta on top and beta at the bottom.
Log files:

service.log
file_home_hiphish_Desktop.log

Can confirm the same thing on Neovim (built-in client) and GNU/Linux (Void). Attached screenshot shows non-beta on top and beta at the bottom.
Log files:

service.log
file_home_hiphish_Desktop.log

The log tells the server has shutdown just in 1 second.
DId you push the correct log?

The log tells the server has shutdown just in 1 second.

I opened an already existing file and then closed the editor, mabe that's why. I have now opened an empty file and typed all those same lines by hand. Here is the new log:

file_home_hiphish_Desktop.log
service.log

I still can not find the way to reproduce it in Windows, but I have some guess.
Please help me do a test, remove this line manual and check if it works: https://github.com/sumneko/lua-language-server/blob/68e39a2cb1511e4307603a0913950a2b1dde1f08/script/provider/diagnostic.lua#L163

I would like to try it, but I cannot build the current master because one of the tests fails. When I run ./3rd/luamake/luamake rebuild I get the following error:
Cleaning... 62 files.
[1/66] Compile C   build/linux/obj/source_lua/lctype.obj
[2/66] Compile C   build/linux/obj/source_lua/linit.obj
...
[63/66] Link    Dll build/linux/bin/bee.so
[64/66] /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/install.lua linux
[65/66] /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/unittest.lua linux
FAILED: build/linux/_/unittest
/home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/unittest.lua linux
/home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake: ...im_lsp/sumneko_lua/lua-language-server/make/unittest.lua:22: /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/bin/Linux/lua-language-server: ...e/nvim/nvim_lsp/sumneko_lua/lua-language-server/test.lua:3: attempt to call a nil value
stack traceback:
	...e/nvim/nvim_lsp/sumneko_lua/lua-language-server/test.lua:3: in main chunk
	[C]: in ?

stack traceback:
	[C]: in function 'error'
	...im_lsp/sumneko_lua/lua-language-server/make/unittest.lua:22: in main chunk
	...eko_lua/lua-language-server/3rd/luamake/scripts/util.lua:58: in function 'util.sandbox'
	.../lua-language-server/3rd/luamake/scripts/command/lua.lua:58: in main chunk
	...eko_lua/lua-language-server/3rd/luamake/scripts/util.lua:51: in function 'util.command'
	...eko_lua/lua-language-server/3rd/luamake/scripts/main.lua:6: in main chunk
	[C]: in function 'require'
	...lsp/sumneko_lua/lua-language-server/3rd/luamake/main.lua:5: in main chunk
	[C]: in ?
[66/66] build/linux/bin/bootstrap 3rd/bee.lua/test/test.lua
OS:       	Linux
Arch:     	64
Compiler: 	GCC 9.3.0
CRT:      	libstdc++ 20200312
DEBUG:    	false
.........................................................................................
Ran 89 tests in 0.264 seconds, 89 successes, 0 failures
OK
ninja: build stopped: subcommand failed.

I would like to try it, but I cannot build the current master because one of the tests fails. When I run ./3rd/luamake/luamake rebuild I get the following error:
Cleaning... 62 files.
[1/66] Compile C   build/linux/obj/source_lua/lctype.obj
[2/66] Compile C   build/linux/obj/source_lua/linit.obj
...
[63/66] Link    Dll build/linux/bin/bee.so
[64/66] /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/install.lua linux
[65/66] /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/unittest.lua linux
FAILED: build/linux/_/unittest
/home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake lua make/unittest.lua linux
/home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/3rd/luamake/luamake: ...im_lsp/sumneko_lua/lua-language-server/make/unittest.lua:22: /home/hiphish/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server/bin/Linux/lua-language-server: ...e/nvim/nvim_lsp/sumneko_lua/lua-language-server/test.lua:3: attempt to call a nil value
stack traceback:
	...e/nvim/nvim_lsp/sumneko_lua/lua-language-server/test.lua:3: in main chunk
	[C]: in ?

stack traceback:
	[C]: in function 'error'
	...im_lsp/sumneko_lua/lua-language-server/make/unittest.lua:22: in main chunk
	...eko_lua/lua-language-server/3rd/luamake/scripts/util.lua:58: in function 'util.sandbox'
	.../lua-language-server/3rd/luamake/scripts/command/lua.lua:58: in main chunk
	...eko_lua/lua-language-server/3rd/luamake/scripts/util.lua:51: in function 'util.command'
	...eko_lua/lua-language-server/3rd/luamake/scripts/main.lua:6: in main chunk
	[C]: in function 'require'
	...lsp/sumneko_lua/lua-language-server/3rd/luamake/main.lua:5: in main chunk
	[C]: in ?
[66/66] build/linux/bin/bootstrap 3rd/bee.lua/test/test.lua
OS:       	Linux
Arch:     	64
Compiler: 	GCC 9.3.0
CRT:      	libstdc++ 20200312
DEBUG:    	false
.........................................................................................
Ran 89 tests in 0.264 seconds, 89 successes, 0 failures
OK
ninja: build stopped: subcommand failed.

No need to build binay files, just edit the lua file.

I deleted my old build because I wanted to be sure that everything was fresh. I cannot go back to it, so I need to build it again.

Oh, i will check the build failure tomorrow.
Maybe you have to build them in elder version then copy the binary files to new version.

Still not working after removing those lines.
I'm not sure if these log files are the correct, I found them inside the server folder.
Should I send something else?
log.zip

I also noticed that the Lua diagnostics disappeared after I updated to macOS Big Sur. Linux is alright though, so it looks like it might be a Mac-only thing, due to some of the bigger changes in Big Sur?
@HiPhish The build works fine in spite of the test error (except for the diagnostics thing on Big Sur of course).

Please help me check if this fix works.

@sumneko With ad192cc99096f717b1a59f8f8bc7b0dac0230a4e, the diagnostics are back on macOS Big Sur, well done! :tada:
(Why does the commit message refer to Linux though? The affected platform was the newest macOS. Maybe just a typo?)
(The failing test is still there though.)

Why does the commit message refer to Linux though? The affected platform was the newest macOS. Maybe just a typo?

Should be Linux and Windows. I

The failing test is still there, which you're probably aware of, just so that other people know that the language server works in spite of it.

I will open a separate issue

It's working like a charm.
Thank you so much!


Launching Minecraft

This issue is still active

This is planned I am waiting for my laptop to get fixed.


docs: fix simple typo, explit -> explicit

There is a small typo in misaka/hoedown/document.h.
Should read explicit rather than explit.
Semi-automated pull request generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Thanks!


readyForStable: close old issues if outdated

readyForStable should close issues if either the stable or the latest revision does no langer match and a new issue should be created.
Currently an unclosed update suggestion from 1.0.2 to 1.2.0 will block any new issue even if the new suggstion would be 1.1.0 to 2.0.0.
As both releases are embedded into the title an easy filteriung should be possible. So closing should be possible (see dependabot commnted "replaced by" ...
In addition a reminder comment could be evaluated every 30 days ...

implemented


default login not working.

I installed opeduty application and  database migrate everything. its running perfectly but default login username and password not working. so please help me. how to solve the issue?
Thanks,
ashok

i'll check it out.

until then please use the manage.py createsuperuser command

@deathowl  Hi!
Already fixed this issue. And Thanks

i create superuser its working fine now. thanks @deathowl.


Remote Update (v9-interactions): catboi8/interactions

This pull request has been superseded by #197


Caching of files and folders

Is your feature request related to a problem? Please describe.
It seems, that when entering any folder, Files UWP is reloading the files and folders, that are contained inside this folder every time. Also navigating back and forth results in reloading the contained files and folders every time.
Describe the solution you'd like
I would like them to get cached, so that it is much faster to enter folders. (and I hope the slow loading animation is also gone afterwards.)
Describe alternatives you've considered
Also if e.g. a file or folder is added via another program or file explorer, Files UWP should show the new files or folders inside the folder instantly without having to reload the whole folder.
Additional context
The file explorer is able to do that, so it feels much faster then the current Files UWP.
I don't know, if this behaviour is meant with #213 so I opened this feature request.

Please fill out the info in the comment of your proposal.

Please fill out the info in the comment of your proposal.

@yaichenbaum Sry, but I don't understand what you want me to do, because I have filled out the whole feature request template as you can see...

It must be I wrote my comment before your changes went though, thanks!

Virtualization for items is something I would definitely want to implement. Unfortunately, there doesn't exist documentation on this feature for the Toolkit DataGrid, so I assume the control doesn't support it. @yaichenbaum Can you verify whether the DataGrid supports virtualization?

My mentality is: "Sure, the Windows.Storage namespace is slow, but users never really need to retrieve the properties of all filesystem items at once" That's where random-access virtualization would come in, but the DataGrid, to my knowledge simply doesn't support it.

As far as I know it does not but I believe it was requested for the new Win UI DataGrid control.

As far as I know it does not but I believe it was requested for the new Win UI DataGrid control.

@yaichenbaum Do you have a link? I would like to read about that.
Or is this what you are refering to?

@szaimen I am talking about this one.

Would be really nice, if that would provide a way to show the size of folders.
Alternatively I imagine that if you right-click on one or more folders (after selecting a few folders and right-click then), then you could show an option in the right-click menu to calculate the current size (and show it directly in the list), so that you are able to sort all files and folders based on their size for the current directory afterwards. (until you change something inside the folders and then reset the calculated size)
Shall I open a new issue for this idea or does it fit here?

@szaimen Probably add that suggestion to https://github.com/duke7553/files-uwp/issues/259

@szaimen We did work to prevent reloading the extended properties of a storage item if it's not scrolled into view. Since performance has improved from these changes, I do not believe caching items is particularly useful.

Please re-open this if you can find a technical rationale for for caching files and folders. For instance, what properties should be cached and how would it benefit performance?
Thanks for the great feedback. Please keep it coming!


♻ Improve memory driver

The memory driver has two deficiencies:

Before a memory device is set to a value, it is "typeless". In other words, if a client tries to read a memory device that has never been set, it doesn't know what type it is. This is a problem in the DrMem browser app. When the browser receives the first value from a device, it knows the type and creates appropriate widgets to view and set it. But with memory devices that haven't been initialized, it doesn't know what setting widget to use. This means, when you create a new memory device, it's difficult to set its first value (I end up using a GraphQL client.)
The current driver only allows one variable to be create per driver instance. If a site uses many memory devices, the config file can get quite large and confusing.

To fix these problems, this issue proposes to change the driver configuration and driver itself. The base config key will be vars and it will return an array of maps. In the maps are two keys, name and initial. name takes a String and represents the name of the memory device. initial can take any value DrMem device value. If the memory device has not yet been set, this value will be immediately reported.
All the variables will be handled by the one instance.
Note that all variables defined in one instance of the driver will have the same path prepended to their names. If different paths are desired, then multiple instances of the driver will have to be used.

#109 adds the initial value to the config parameters. This driver still needs updating to allow a list of devices to be created using one instance.


Karavi topology cert prom

Is this a new chart?
No
What this PR does / why we need it:
Prevents cert-manager from modifying passed certificates and ensures that self-singed certificates can be used for CA verification
Which issue(s) is this PR associated with:

https://github.com/dell/karavi-observability/issues/52

Special notes for your reviewer:
The topology self-signed certificate is missing Key Usage and will get illegal characters if used for CA verification. Now the certificated looks:
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            2a:f9:d2:63:30:b9:17:4d:38:9e:21:e3:0e:fd:89:b4
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: O=dellemc
        Validity
            Not Before: May 25 20:26:43 2021 GMT
            Not After : Aug 23 20:26:43 2021 GMT
        Subject: O=dellemc
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:d9:b8:06:7d:a5:a2:a7:f9:d7:66:02:05:13:34:
                    be:ac:b6:65:35:9a:57:09:bd:86:89:34:c2:5a:b7:
                    63:04:de:63:2d:0a:f6:1e:32:af:1e:e0:45:ab:b0:
                    dd:e2:d1:e5:dc:5e:ca:13:3d:39:43:a6:e0:b4:64:
                    62:d5:6b:63:07:60:3d:19:4e:aa:5d:5c:23:7c:2e:
                    47:e9:d5:76:52:da:25:14:e6:91:4b:54:77:8a:a4:
                    7e:10:83:cd:25:7f:64:a4:45:d2:cc:3d:34:c0:cb:
                    af:0f:b2:a3:97:d8:d0:35:64:f4:66:93:c2:67:89:
                    27:eb:3f:00:fa:3c:a6:50:15:56:31:e1:ff:33:c4:
                    ef:9a:dc:64:45:1e:8a:6b:3b:a0:54:93:47:4e:03:
                    af:a4:8c:e4:38:80:8b:b6:0b:00:f9:a5:8e:19:9e:
                    b2:9c:c6:39:44:f4:30:cf:26:21:46:9b:ea:d6:fa:
                    d2:73:83:44:0f:c8:68:0f:ac:d0:b1:25:ea:b7:53:
                    18:f8:31:31:ac:9b:d4:83:02:d0:f7:c6:60:af:c3:
                    77:4c:19:c3:d4:0b:ff:d9:0a:8e:cf:07:7b:a2:58:
                    9b:15:f9:4f:55:ce:c1:77:47:2b:a1:c7:4c:29:02:
                    38:54:50:da:13:5f:a5:71:05:c6:92:43:26:f4:66:
                    1b:45
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Certificate Sign
            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier:
                62:C6:48:B7:D7:F7:B3:E4:C1:79:4C:EC:AD:87:F0:09:16:C9:DF:6D
            X509v3 Subject Alternative Name:
                DNS:karavi-topology, DNS:karavi-topology.karavi.svc.kubernetes.local
    Signature Algorithm: sha256WithRSAEncryption
         05:8f:2f:6c:35:e5:47:30:90:c0:28:aa:fd:52:5c:5f:02:4c:
         59:98:02:b6:71:94:60:ef:31:09:02:5c:5f:de:2d:d0:3a:c8:
         1b:2c:d8:3e:94:c9:ef:98:a5:f3:de:df:6a:4a:65:9d:f6:42:
         d5:0c:51:a2:63:71:1e:34:bb:bd:46:26:ab:5e:b8:92:62:ce:
         de:78:68:ca:5a:9a:6f:52:18:70:6b:52:3f:49:88:a6:1d:5a:
         19:57:6a:9a:14:d8:5a:b3:30:e3:1b:e6:93:03:df:b9:10:e4:
         48:43:d3:e3:5c:6c:a7:ac:01:fd:37:4e:05:f5:9b:16:c3:ce:
         85:3f:12:46:6d:75:a1:3a:bf:27:6e:ce:04:fe:03:70:c2:75:
         ca:78:da:53:12:e6:21:96:25:5d:12:30:63:62:05:5c:1c:1c:
         60:11:71:dc:1a:30:1c:06:d3:9c:6c:5a:a4:cd:c5:33:5d:e1:
         91:ce:79:75:ba:7a:4a:05:b0:21:2f:ef:16:9b:78:77:7c:13:
         46:cb:b0:c9:22:40:e8:64:47:b6:3c:38:0a:dc:c1:19:73:de:
         b0:45:8e:e3:de:fe:e6:fd:65:85:98:ab:45:7f:a5:f7:e8:e4:
         6c:b0:16:57:33:9b:f3:c0:03:96:ef:bc:df:69:ff:0e:00:f3:
         4a:12:75:42

Checklist:
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the chart README.md
[ ] Title of the PR starts with the chart name (e.g. [charts_dir/mychartname]) if applicable

Closing this PR as the content does not align with the intended plan for the cert manager. Cert-manager should be able to modify(generate a new certificate from the provided CA root certificate)  when the user-provided certificate expires


[VL] Enable Spark legacy date formatter if spark.sql.legacy.timeParserPolicy is set to 'LEGACY'

What changes were proposed in this pull request?
Velox#10966 introduced simple date time formatter that aligns with Spark legacy date parsing/formatting behavior. This PR enables Velox simple date time formatter if spark.sql.legacy.timeParserPolicy is set to LEGACY.
Relates Velox issue: #10354
How was this patch tested?
Integration tests with Spark

@rui-mo Could you help to take a look please? Thanks.

@rui-mo Could you help to merge this PR? Thanks.

@surnaik This PR only works for spark.sql.legacy.timeParserPolicy, seeing gluten#7375


Inference time on the HICO-Det test set

Excuse me,

how is the inference time calculated on the iCAN / TIN, including which parts of the inference time (if divided into pre-processing, HOI inference , post-processing) ?
and, for iCAN, do you use the test code of iCAN to calculate the inference time? thanks.

For two-stage methods, e.g., iCAN/TIN, we calculated the inference time including the human/object detection and HOI prediction, if using additional human pose features, we will add the inference time spent by the pose estimator (more details can be seen in our paper).
The inference time presented in the paper from running the open-source test code or get the inference time from the authors directly.
The inference time provided by the test code of iCAN only calculated the process of HOI prediction without human/object detection.

Thank you, I have read your paper, for iCAN in the table 2, your inference time is '92 + 112 = 204' (ms), i guess '92' is the human/object detection time, '112' is the HOI prediction time, am I right ?
2. if right, i think iCAN is related to the number of humans(N) and objects(M), is your ‘112’ the average of HOI prediction for iCAN ?
3. if right, in another paper I read (Classifying All Interacting Pairs in a Single Shot), iCAN's inference time is like this : from less than 1 second to more than 30 seconds

Why is the iCAN recorded in your paper millisecond level, i'm confused. Sure, your job is really great.

The inference speed reported in our paper for iCAN is the average time of all images (112ms/image) in test set of HICO-DET where we ran the official test code of iCAN on single Titan XP. Additionally, iCAN also reported the inference speed for VCOCO  in Table 3c of the paper, which is similar to 112ms.


includeBuild fails on WSL with "Included build /wsl$/Ubuntu-20.04\wsl$\Ubuntu-20.04...\my-plugin has build path :my-plugin which is the same as included build /home/..."

Expected Behavior
To build as it did before.
Current Behavior
I'm currently facing a problem, which might be related to caching, as it does not always appear.
Running Gradle sync / build etc causes
Included build /wsl$/Ubuntu-20.04\\wsl$\Ubuntu-20.04\home\user\workspace\my-project\plugins\my-plugin
has build path :my-plugin which is the same as included build
/home/user/workspace/my-project/plugins/my-plugin

inside a project in WSL.
The path of the included build within the error looks suspicious

/wsl$/Ubuntu-20.04\wsl$\Ubuntu-20.04\home\

Not sure why.
The project worked for quite a while now and this issue re-appeared out of the sudden.
I had it couple of times and it most of the time went away by cleaning caches, rebuilding etc.
Context (optional)
No response
Steps to Reproduce
The plugin is included in settings.gradle with
these are enabled by default in my project, but I also tried disabling caching and configureondemand to resolve the issue
#Gradle properties
org.gradle.priority=low
org.gradle.caching=true
org.gradle.configureondemand=true

pluginManagement {
  repositories {
    mavenLocal()
    mavenCentral()
    gradlePluginPortal()
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  plugins {
    id "${quarkusPluginId}" version "${quarkusVersion}"
  }
}

includeBuild "plugins/my-plugin"
//includeBuild "./plugins/my-plugin" also not working

and used in the top-level build.gradle of my monorepo
import com.my.project.plugin.MyPlugin

buildscript {
  dependencies {
    classpath 'com.my.project:my-plugin:*'
  }
}

apply plugin: 'java'
apply plugin: 'idea'
apply plugin: MyPlugin

subprojects {
  apply plugin: 'java'
.
.
.
}

Gradle version
8.1.1 but happens under other versions as well
Build scan URL (optional)
No response
Your Environment (optional)
No response

It seems to be related to IntelliJ IDEA. I'm currently able to run it via terminal, while it fails with this error using IntelliJ run configs


WIP - revise XDP API to be header-only, support KM and UM

Description
Describe the purpose of and changes within this Pull Request.
Testing
Do any existing tests cover this change? Are new tests needed?
Documentation
Is there any documentation impact for this change?
Installation
Is there any installer impact for this change?

nit: does this mean if there is a change / fix in the APIs, the end application will need to recompile their code?

nit: does this mean if there is a change / fix in the APIs, the end application will need to recompile their code?

The existing APIs will be supported indefinitely. If we make a breaking change release (currently not planned) then we would consider removing support for the existing APIs.
As it stands, there's not really any additional maintenance costs for the old APIs, but new features we add may take dependencies on newer API versions.

nit: does this mean if there is a change / fix in the APIs, the end application will need to recompile their code?

The existing APIs will be supported indefinitely. If we make a breaking change release (currently not planned) then we would consider removing support for the existing APIs.
As it stands, there's not really any additional maintenance costs for the old APIs, but new features we add may take dependencies on newer API versions.
At a higher level, the IOCTL interface is ABI back- and forward-compatible, and these header wrappers are very thin.

Actually my question was more generic, and not specific to breaking changes. If there is a bug fix done to an API, (and there is no breaking change), with header-only approach, the application will need to rebuild their code to get the new fix. Is that desirable?

Actually my question was more generic, and not specific to breaking changes. If there is a bug fix done to an API, (and there is no breaking change), with header-only approach, the application will need to rebuild their code to get the new fix. Is that desirable?

We originally designed our API functions to be as thin as possible, so hopefully there is no need to service them.  That said, yes, if there is a bug, apps will have to recompile.


[CLOSED] Allow MoJ and HMCTS to edit specialist documents for all Tribunals Decisions Finders

 Issue by marksheldonGDS
Friday 04 December 2015 at 15:24 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/610

Users in Signon with their organisation set to either Ministry of Justice or HM Courts & Tribunals Service, and Editor permission in Specialist Publisher, need to be able to view and edit specialist document formats for all the Tribunal Decision Finders:

Asylum Support Decision
Employment Appeal Tribunal Decision
Employment Tribunal Decision
Tax Tribunal Decision
UTAAC Decision

This PR adds Ministry of Justice and HM Courts & Tribunals Service as additional owning organisations to each of those specialist document formats.

marksheldonGDS included the following code: https://github.com/alphagov/specialist-publisher/pull/610/commits

 Comment by boffbowsh
Friday 04 December 2015 at 15:46 GMT

This branch needs rebasing.


Desktop app product name

Hello:
The documentation is not clear about how you get the product name when adding a desktop apps. I assume that you get this information using the get-applockerfileinformation ps command, but want to make sure.
In addition the documentation says "Regarding to how to get the Product Name for the Apps you wish to Add, please reach out to our Windows Support Team to request the guidelines"
Please provide the details for getting the product name in this documentation.
Thank you.

Just to get a clearer picture of which part of the documentation you are referring to, do you have a link to the page that brought you here?

Just to get a clearer picture of which part of the documentation you are referring to, do you have a link to the page that brought you here?

Sure thing, here is the link
https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure#add-desktop-apps

Sure thing, here is the link
https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure#add-desktop-apps

Thank you. The following is what your issue ticket would have looked like if you had pressed the button [ This page ] at the bottom:

[Enter feedback here]

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

ID: c1ad3f92-24de-5eb5-8454-c72d85737183
Version Independent ID: 900125eb-31ea-faf3-ac30-7c3d7b30f611
Content: Create a Windows Information Protection (WIP) policy with MDM using the Azure portal for Microsoft Intune (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
Product: w10
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Thank you. The following is what your issue ticket would have looked like if you had pressed the button [ This page ] at the bottom:

[Enter feedback here]

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

ID: c1ad3f92-24de-5eb5-8454-c72d85737183
Version Independent ID: 900125eb-31ea-faf3-ac30-7c3d7b30f611
Content: Create a Windows Information Protection (WIP) policy with MDM using the Azure portal for Microsoft Intune (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md
Product: w10
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Please be patient, since this repository is made to improve the documentation and not as much for direct user support.
Just in case you find that the wait for response posts from the MS Docs team takes more time than expected, please consider using the following forums to ask and see if the response is quicker:
Try the following resources to get in touch with users who may be able to help you:

TechNet forums: https://social.technet.microsoft.com/Forums/en-US/home
MSDN: https://social.msdn.microsoft.com/Forums/en-US/home
Microsoft Community: https://answers.microsoft.com/

Disclaimer: I am not affiliated with Microsoft or the Microsoft Docs teams here on GitHub.

Please be patient, since this repository is made to improve the documentation and not as much for direct user support.
Just in case you find that the wait for response posts from the MS Docs team takes more time than expected, please consider using the following forums to ask and see if the response is quicker:
Try the following resources to get in touch with users who may be able to help you:

TechNet forums: https://social.technet.microsoft.com/Forums/en-US/home
MSDN: https://social.msdn.microsoft.com/Forums/en-US/home
Microsoft Community: https://answers.microsoft.com/

Disclaimer: I am not affiliated with Microsoft or the Microsoft Docs teams here on GitHub.

PowerShell reference:

https://docs.microsoft.com/powershell/module/applocker/get-applockerfileinformation?view=win10-ps
https://docs.microsoft.com/powershell/module/applocker/?view=win10-ps

PowerShell reference:

https://docs.microsoft.com/powershell/module/applocker/get-applockerfileinformation?view=win10-ps
https://docs.microsoft.com/powershell/module/applocker/?view=win10-ps

@nhoj01 Correct, you get the Product Name by using the Get-AppLockerFileInformation Powershell cmdlet.

@nhoj01 Correct, you get the Product Name by using the Get-AppLockerFileInformation Powershell cmdlet.

@nhoj01 : If I read your initial ticket comment, it looks like you are asking for the addition of a better description with the command
Get-AppLockerFileInformation

added, alongside a reference link to the PS page on how to use it.

@nhoj01 : If I read your initial ticket comment, it looks like you are asking for the addition of a better description with the command
Get-AppLockerFileInformation

added, alongside a reference link to the PS page on how to use it.

I believe those updates should address my concerns.

I believe those updates should address my concerns.