fix(module:select): Console error when interacting with searchable input using keyboard

Console error when interacting with searchable input using keyboard
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
In searchable select input (when list in empty) click on search input and press down/up key it will console error for nzValue of undefined, This PR avoid this exception and first check the list have item when user press down/up key.

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
In searchable select input (when list in empty) click on search input and press down/up key it will console error for nzValue of undefined.
Issue Number: 6699
What is the new behavior?
In searchable select input (when list in empty) click on search input and press down/up key it will console error for nzValue of undefined, This PR avoid this exception and first check the list have item when user press down/up key.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@vthinkxie Please review this PR


Aerial Dataset Presentation - Dataset Handling

Code:
input_folder = utils.prepare_input_folder(DATAPATH, DATASET) preprocess_folder = utils.prepare_preprocessed_folder(DATAPATH, DATASET, 224, "full")
Output:
TypeError                                 Traceback (most recent call last)
 in
1 input_folder = utils.prepare_input_folder(DATAPATH, DATASET)
----> 2 preprocess_folder = utils.prepare_preprocessed_folder(DATAPATH, DATASET, 224, "full")
TypeError: prepare_preprocessed_folder() takes 3 positional arguments but 4 were given

Hi @AhmadAmmar,
Thanks for the bug insight. Indeed this should have been modified with the last major modification of the dataset. However, a fix has been committed recently (cf commit 07c1913). Everything should be OK now.
Could you confirm that it is fine for you?

No update there since a long time, I close the issue.


Phone verification not working on emulator: invalid_app_credential

Hello

Android device: API 26
Android OS version: 7.1
Google Play Services version: 3.1.0
Firebase/Play Services SDK version: 11.0.1
FirebaseUI version: 2.0.1

Step 3: Describe the problem:
I'm getting issue when I try to use firebase UI authentication phone verification on an emulator. I get an error says

Internal error has occurred [invalid_app_credential: app validation failed]

Observed Results:
Error description received from server: INVALID_APP_CREDENTIAL : App validation failed
BasicNetwork.performRequest: Unexpected response code 400 for https://www.googleapis.com/identitytoolkit/v3/relyingparty/sendVerificationCode?alt=proto&key=AIzaSyDWGycBk58rjdR5IlyaUMhT4XXkzhKaxQE

same issue in moto g 1st gen

My issue was in the emulator but when I install the app on my Samsung Galaxy. It works perfectly.

Hi all this is by design.  Phone Authentication uses a lot of signals to prevent fraud which means it can't work on an emulator.  You'll need to test on a real device.

I though It was done to prevent abuse.
Any how. At least the error message should indicate this. @samtstern

What i do for this error on my android device?

@kishansinhparmar does the email and password works perfectly ?. if it is not you may have issue with firebase configuration see the documentation. Otherwise,  firebase auth may think your device is an emulator or rooted.

yup rooted...but what about sign in with google?

@kishansinhparmar try to re-sync firebase or redo the firebase configuration. I've no idea

@MuBoori thanks...try to re-sync

Is this problem also occurs on rooted devices?

Phone Auth doesn't work on emulators.
Phone Auth does work on rooted device, but features like instant validation won't work.
Google Sign-In works on emulators
There are many reasons to invalid_app_credential, e.g.
a) Missing right package name + SHA1 registration
b) Phone Auth not turned on in console
c) emulators
...
If your Google Sign-In also doesn't work, at least you should check 3a)

Phone auth works in emulator but only with testing phone numbers.
Please read the stackoverflow answer here

Anyone know how it detects if the device being used is a physical device?

I tried to add my testing phone number in firebase console but it didn't worked also

Your problem related to SHA1 and SHA256 keys. You have to add them to authenticate your certs.
Goto
Firebase Console of your project
Authentication
Project Setting (From Setting button near Project Overview)
Add fingerprint
Add SHA-1 and SHA-256 values of your keystore.
You can get keystores from gradle like this.
./gradlew signingReport
Read this for more information: https://firebase.google.com/docs/auth/android/phone-auth#enable-app-verification


Implemented arm canonicalization

using armv7 for now.  Easy to update to thumbv7 later.

I don't mean to step on your toes, but if you want to use this canonicalization code, feel free.

No worries, thanks :-) I'll merge yours with mine, yours has all the arm processors mine just armv7.

I'll work on this tonight (I'm in Europe), this weekend I'm not at home.

Sounds good! :) I just went through the list of SubTypes listed in llvm/include/AST/triple.h (I think) and put ‘em in there.

On Dec 20, 2015, at 6:14 AM, tienex<EMAIL_ADDRESS>wrote:
I'll work on this tonight (I'm in Europe), this weekend I'm not at home.
—
Reply to this email directly or view it on GitHub https://github.com/tienex/swift/pull/1#issuecomment-166119977.

Support for ARMv6 done.  Needs testing.

What do you think about submitting this to Apple to hopefully get it into 2.2 (they're not accepting new features on the 15th), then we can move forward on your fixes to have them in swift 3.0?


Add event store for managing lifecycle of an event

Add event store for managing lifecycle of an event. This manages basics like updating timestamps, but also editing of recurring events.
Adds examples on python doc for how to invoke the library.

Codecov Report

Merging #114 (e6a129a) into main (2c3f620) will decrease coverage by 0.60%.
The diff coverage is 91.48%.

@@            Coverage Diff             @@
##             main     #114      +/-   ##
==========================================
- Coverage   96.85%   96.25%   -0.61%
==========================================
  Files          41       42       +1
  Lines        2132     2136       +4
==========================================
- Hits         2065     2056       -9
- Misses         67       80      +13

Impacted Files
Coverage Δ

ical/__init__.py
100.00% <ø> (ø)

ical/types/recur.py
92.05% <81.81%> (-4.53%)
:arrow_down:

ical/store.py
94.66% <94.66%> (ø)

ical/component.py
95.03% <100.00%> (ø)

ical/event.py
96.35% <100.00%> (-0.66%)
:arrow_down:

ical/journal.py
100.00% <100.00%> (ø)

ical/timeline.py
95.60% <100.00%> (+0.14%)
:arrow_up:

ical/todo.py
98.52% <100.00%> (ø)

ical/types/__init__.py
100.00% <100.00%> (ø)

ical/types/data_types.py
100.00% <100.00%> (ø)

... and 14 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


On Safari card avatars' border is square

On Safari card avatars' border is square instead of circle. Seems to be an issue for all cards.
Example:

Works properly without solving.


Dynamic array of arrays is pared wrong

Similar to https://github.com/chipsalliance/Surelog/issues/2018
When the following file is parsed by Surelog:
module top;
   int dynamic [1:0][];
endmodule;

the dynamic range is parsed wrong. I think that it should have vpiArrayType 2 and int dynamic [1:0] should be in vpiElemTypespec or vpiReg.
Here is uhdm:
slpp_all/surelog.uhdm: Restored design Pre-Elab:
design: (work@top)
|vpiName:work@top
|uhdmallModules:
\_module: work@top (work@top) array_types.sv:1:1: , endln:3:10, parent:work@top
  |vpiDefName:work@top
  |vpiFullName:work@top
  |vpiNet:
  \_logic_net: (work@top.dynamic), line:2:8, parent:work@top
    |vpiName:dynamic
<EMAIL_ADDRESS>|uhdmtopModules:
\_module: work@top (work@top) array_types.sv:1:1: , endln:3:10
  |vpiDefName:work@top
  |vpiName:work@top
  |vpiVariables:
  \_array_var: (work@top.dynamic), line:2:8, endln:2:15, parent:work@top
    |vpiArrayType:1
    |vpiName:dynamic
<EMAIL_ADDRESS>    |vpiAutomatic:1
    |vpiRandType:1
    |vpiVisibility:1
    |vpiSize:2
    |vpiReg:
    \_int_var: (work@top.dynamic<EMAIL_ADDRESS><EMAIL_ADDRESS>    |vpiRange:
    \_range: , line:2:17, endln:2:20
      |vpiLeftRange:
      \_constant: , line:2:17, endln:2:18
        |vpiConstType:9
        |vpiDecompile:1
        |vpiSize:64
        |UINT:1
      |vpiRightRange:
      \_constant: , line:2:19, endln:2:20
        |vpiConstType:9
        |vpiDecompile:0
        |vpiSize:64
        |UINT:0
    |vpiRange:
    \_range:
      |vpiLeftRange:
      \_constant: , line:2:21, endln:2:22
        |vpiConstType:9
        |vpiDecompile:0
        |vpiSize:64
        |UINT:0
      |vpiRightRange:
      \_constant: , line:2:21, endln:2:22
        |vpiConstType:6
        |vpiDecompile:unsized
        |STRING:unsized

Could you change vpiTypespec to vpiElemTypespec?
slpp_all/surelog.uhdm: Restored design Pre-Elab:
design: (work@top)
|vpiName:work@top
|uhdmallModules:
\_module: work@top (work@top) array_types.sv:1:1: , endln:3:10, parent:work@top
  |vpiDefName:work@top
  |vpiFullName:work@top
  |vpiNet:
  \_logic_net: (work@top.dynamic), line:2:8, parent:work@top
    |vpiName:dynamic
<EMAIL_ADDRESS>|uhdmtopModules:
\_module: work@top (work@top) array_types.sv:1:1: , endln:3:10
  |vpiDefName:work@top
  |vpiName:work@top
  |vpiVariables:
  \_array_var: (work@top.dynamic), line:2:8, endln:2:15, parent:work@top
    |vpiArrayType:2
    |vpiName:dynamic
<EMAIL_ADDRESS>    |vpiAutomatic:1
    |vpiRandType:1
    |vpiVisibility:1
    |vpiSize:2
    |vpiTypespec:        <--------- here
    \_array_typespec:
      |vpiRange:
      \_range: , line:2:17, endln:2:20
        |vpiLeftRange:
        \_constant: , line:2:17, endln:2:18
          |vpiConstType:9
          |vpiDecompile:1
          |vpiSize:64
          |UINT:1
        |vpiRightRange:
        \_constant: , line:2:19, endln:2:20
          |vpiConstType:9
          |vpiDecompile:0
          |vpiSize:64
          |UINT:0
      |vpiElemTypespec:
      \_int_typespec:

The vpiTypespec should be related to the whole array. Here we need the vpiTypespec of the element (here the element has type int [1:0]).


Add example invocation of insert()

This should make the exercise more newbie-friendly. It took me ages to figure out this one, as the official document doesn't even mention that insert() can take a callback.
Also fixed a minor typo.

:+1: love the idea.
Instead of saying doc, might be worthwhile to have an example document like some of the other examples
Taking inspiration from https://github.com/evanlucas/learnyoumongo/blob/master/exercises/update/problem.md :
// inserting document
// { a: 2 }

collection.insert({
  a: 2
},function(error,result) {
// handle error
// log result
})

Also, changing data to result may be a bit more verbose.

Good call. I like the addition of an actual document.

Landed in 2be53cee55944788cb5d7422f11d9099b85defe2. Thanks!


Publicly expose enum StlinkError

Is your feature request related to a problem? Please describe.
In probe-run we are not able to cleanly handle a StlinkError::CommandFailed(JtagNoDeviceConnected), because the enum StlinkError isn't publicly exposed.
https://github.com/probe-rs/probe-rs/blob/b7e7cfd667a0a85fe012017f3cf865038001970e/probe-rs/src/probe/stlink/mod.rs#L1109-L1131
Describe alternatives you've considered
Currently we transform the error into a string and then check if it contains a specific string. This is not optimal.
if e.to_string().contains("JtagNoDeviceConnected") {
    // ...
}

Describe the solution you'd like
We'd like to be able to handle this directly and therefore need this type to be exposed.
Additional context
This issue came up in https://github.com/knurling-rs/probe-run/pull/253#discussion_r698359959.

Exposing this shouldn't be a problem.
Maybe it might be better to add a more generic error for this case? This error indicates that no device seems to be connected, which can also occur with other probes. I'm not sure what kind of error is returned for other probes right now.
Do you need to handle the ST-Link differently, or would a more generic error for this kind of problem also be suitable?

Exposing this shouldn't be a problem.

Great! 😄

Maybe it might be better to add a more generic error for this case? This error indicates that no device seems to be connected, which can also occur with other probes. I'm not sure what kind of error is returned for other probes right now.
Do you need to handle the ST-Link differently, or would a more generic error for this kind of problem also be suitable?

A more generic error would probably be even better to be able to handle more probes.
Is there a way to get the specific probe from the probe_rs::Probe, in case we want to differentiate?

The enum was made publicin #2027


Exclusion Report

#1399 #1400 #1401
Added save functionality for the exclusion report
Changelog:

Added Backend models for Exclusion Report
Added Serializers to save the records
Added a check in the viewset so it knows which serializer it should use
Added toastr alert for saving an exclusion report draft
Clicking on an exclusion report should show the proper details

 Exclusion Report | Save a draft |5|

 System Alerts | Save a Draft Exclusion Report |1|

 Exclusion Report | Edit a draft |3|

I'll add unit tests for this later

@amichard the migration number conflicts with existing one, need to be renamed


Run browser tests to node 14

Currently they run in node 10, node 14 fails.

Currently most tests pass, 6 fail in Headless chrome.


Refine Traffic Proxy GRPC Protocol

Requirements

proxy -> trafficproxy
delete ADD
add subregion ?
more delta rule? e.g. speed change threshold, etc.
option cc_enable_arenas = true;  (https://github.com/protocolbuffers/protobuf/issues/4327)
timestamp for every flow/incident
unit of speed
transction id

Some functions will be postpond to implement even though we defined them in .proto:

subregion
request timestamp for archived traffic
trasctionID

The request for archived traffic function can be tracked by https://github.com/Telenav/osrm-backend/issues/182.
So I'd like to close this issue since codes have been merged.


[1.1.1] Client crash when autocrafting

Issue description:
Tried to autocraft 32 Atomic Alloy from Mekanism.
Insert the amount clicked "Start", Preview Screen didn't show up, client crashed.
What happens:
Client crashed.
What you expected to happen:
No crash :-D
Steps to reproduce:
Can't reproduce. Tried 1, 10, 32 after relog, went fine.
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge:<IP_ADDRESS>3
Refined Storage: refinedstorage-1.1.1

Does this issue occur on a server? [yes/no]
Yes. But only client crashes.
If a (crash)log is relevant for this issue, link it here:
http://pastebin.com/BLYHRHxz

Just hit that crash while trying to autocraft a draconic energy core. Same versions of everything as Gepett0. My log from the console: https://www.dropbox.com/s/andaoix85gjsisb/rs-crash1.log?dl=0
Right before the "Rendering screen" stack trace, I got a ConcurrentModificationException that seems to have something to do with JEI, and it's present in the next stack trace as well. Possibly still something wrong with the new JEI code, I would hazard a guess.

Same crash as RealGrep now.
Using JEI 1.10.2-<IP_ADDRESS>2 FYI

The ConcurrentModificationException is already fixed, however I have to look in the NullPointerException you got, @Gepett0.

Thanks in advance!
Nice new textures btw!


Fix nats test

Motivation for this change
The nixos test for nats is broken atm (see https://github.com/NixOS/nixpkgs/pull/158847). This fixes the broken test.
I also noticed that the natscli package had the wrong hashes. The version that was build didn't have support for the count flag on nats sub, while that flag should be in the latest version. Updating the hashes resolved the problem.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@c0deaddict natscli has been bumped to 0.0.29 in the meantime.
Could you please rebase this and keep the one commit fixing the test?

@c0deaddict natscli has been bumped to 0.0.29 in the meantime. Could you please rebase this and keep the one commit fixing the test?

Done!

@ofborg test nats


Adding ability to inline assembly into pom file (#157)

Change is not backward compatible: descriptor is renamed into descriptorFile
Signed-off-by: Oleg Sigida<EMAIL_ADDRESS>

i'm going to say that i'm not a fan of the descriptor element changing here. descriptor and descriptorRef were specifically chosen b/c they match what is used by the assembly plugin itself.
i would rather see this functionality added using a different element.

@jgangemi any hint what would be a good name for it?
I cannot make up any better naming on myself...

how about assemblyDef?

@jgangemi, done, please review

I wonder, whether it works correctly with XML namespaces (the assembly XSD is different from Maven's pom, but this shouldn't matter). I will try this soon. This change is in fact backwards compatible since it only adds a new tag (and doesn't modify or remove one), so we could put it into 0.11.4 as well (which I want to release this week because of some quite important fix)

@rhuss, not sure for complicated assembly, but this works for me quite well, testing it for a week already
<assembly>
    <basedir>/</basedir>
    <descriptor>
        <files>
            <file>
                <source>${project.build.directory}/${project.build.finalName}-with-dependencies.jar</source>
                <outputDirectory>/</outputDirectory>
            </file>
            <file>
                <source>${project.basedir}/src/main/config/active.json</source>
                <outputDirectory>/</outputDirectory>
            </file>
        </files>
    </descriptor>
</assembly>

Sounds good, I will try to experiment a bit with namespaces tomorrow a bit (which is somewhat cool since a decent IDE can then autocomplete on the tags properly). Will add this as a profile to the sampe app.
But if it works with Maven, we are save even without namespaces. Unfortunately I still have not real integration tests checking this automatically.

Added it to branch integration. Renamed the tag to inline though since the context "assembly" is clear from the parent tag. Also added an example in data-jolokia-demo sample under the profile "inline".


fix: hierarchy model with namespace should inherit from the superclass of basic model

#382
FYI: In my case, I have a namespace AAA for billing, and billing model inherits from AAA::ApplicationRecord.
Like the following code:
module AAA
  class Billing < ApplicationRecord
    connects_to database: { writing: :foo_service, reading: :foo_service}
    has_closure_tree
  end
end

module AAA
  class ApplicationRecord < ActiveRecord::Base
    connects_to database: { writing: :aaa, reading: :aaa }

    self.abstract_class = true
  end
end

Therefore if I follow the unmodified code to execute, AAA::BillingHierarchy will inherit from ApplicationRecord, not AAA::ApplicationRecord, then it will connect to primary database, not aaa database.
PTAL.Thank you.

While this code works, the implementation is not correct. We need to inherit just the connection.  This PR take in consideration that everyone will use ApplicationRecord inside a namespace.
What if i have 1 model inheriting from PostgresqlRecord and Another From MysqlRecord for example ?
What we need to do is to inherit still from Base, use the connection of the model with the tree.

@seuros I have made some changes for inheriting the connection. PTAL. Thank you.

While this code works, the implementation is not correct. We need to inherit just the connection. This PR take in consideration that everyone will use ApplicationRecord inside a namespace.
What if i have 1 model inheriting from PostgresqlRecord and Another From MysqlRecord for example ?
What we need to do is to inherit still from Base, use the connection of the model with the tree.

I think if our goal is to use the connection of the model with the tree, maybe we need to reproduce the logic of rails to make the models inherit from the same superclass use the same one database connection. Shall we use model_class.superclass to replace ActiveRecord::Base? Then we do not need to mind whether the model inherits from PostgresqlRecord or MysqlRecord.

I was thinking at that solution at first.
But since we can override the connection at the model level , we impose this on other devs.
We should update the README to state that the hierarchy is going to inherit the connection from the model. If a Dev has some custom setup that need special setting, there is always the ability to create the Hierarchy model manually and assign it.

Let use your fix for now. We can inherit the connection once we drop support for old AR version.  Good job

Thank you!
I did some attempts to override the connection at the model level, then I found that I can override with different connections easily but cannot make the hierarchy model and the basic model use the same connection within a short time. So I think superclass is a not bad choice for me.

It would be nice if the class being used was configurable (rather than model_class.superclass or even ActiveRecord::Base) in the same way the hierarchy_class_name is configurable right now.
This change breaks our code base because of how we use Rails engines. The model_class.superclass is not what we want as that causes other problems for us.

@mbandrewfoster can you explain your use case ?

@mbandrewfoster can you explain your use case ?

Same problem here. See my issue regarding this: https://github.com/ClosureTree/closure_tree/issues/395


Use with event filter to reconcile less often

What this PR does / why we need it:
Avoid reconciling if the event triggering the reconciliation is related to incremental status updates
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:

[ ] squash commits
[ ] include documentation
[ ] add unit tests

implemented in #1359


Incompatible Host and Port Config Changes in >= 3.5?

Looking through the code, I'm not sure I see where this change might have happened, but we think version 3.5 introduced an incompatibility. We used to be able to use atoms for host names. Now it seems we have to specify binaries. We've been discussing it a bit in a Kaffe issue here.
Is this a known change?

Hi.
brod only supports Erlang string() (single quoted string in Elixir) as hostname, not atom() not binary() (double quoted string in Elixir) either.

There were no changes with regards to brod:endpoint() spec from 3.4 to 3.5 either.

I'm not sure I'm tracing it correctly, but in 3.4 if I pass an atom, I end up here and then here with still having an atom and all goes well.
With the newer versions, I end up inside kpro_connection from kafka_protocol and get an error:
2019-05-30 08:45:44.984 [error] GenServer :s1 terminating
** (FunctionClauseError) no function clause matching in :kpro_connection.host/1
    (kafka_protocol) src/kpro_connection.erl:579: :kpro_connection.host(:kafka)
    (kafka_protocol) src/kpro_connection.erl:101: :kpro_connection.start/3
    (kafka_protocol) src/kpro_brokers.erl:304: :kpro_brokers.connect_any/3
    (brod) src/brod_client.erl:524: :brod_client.ensure_metadata_connection/1
    (brod) src/brod_client.erl:279: :brod_client.handle_info/2

I'm going to try converting everything to Erlang strings and see if that works across versions.

Looks like if we always transform to Erlang strings (Elixir charlists) it works for both newer and older versions of Brod.

will be fixed here: https://github.com/klarna/kafka_protocol/pull/56


fix(*): Function handler syntax and update extension.yaml/PRE/POSTINSTALL

Fixes: #1 #2 #5 #6 #7 #8

Left some minor inline suggestions for typos.
There's also this other typo but probably not in the scope of this PR:

Typo in variable name: https://github.com/mailchimp/Firebase/pull/9/files#diff-6c53bf76483f89e4e126787e25a40c3d7001cf6590b587c621e2e462cdbc8060R211-R215

- prevMergeFieldVaue
+ prevMergeFieldValue

Hi @desoukya
Can you confirm that now all handler fields are now required by default? I remeber we had some issues installing as these fields were originally optional?
If they are now required, most other extensions use a pattern for the document Path which looks similar to...
projects/${param:PROJECT_ID}/databases/(default)/documents/${param:COLLECTION_PATH}/{documentId}

Would we be able to update to match this pattern?
This would also allow the parameter descriptions to be simplified and similar to other extensions.
For example. Big Query simply has...
Listens for document changes in your specified Cloud Firestore collection,
then exports the changes into BigQuery.

```js
projects/${param:PROJECT_ID}/databases/(default)/documents/${param:COLLECTION_PATH}/{documentId}

@dackers86 Yes all field are required now. Do you have samples examples I can reference?

Hi @desoukya
Can you confirm that now all handler fields are now required by default? I remeber we had some issues installing as these fields were originally optional?
If they are now required, most other extensions use a pattern for the document Path which looks similar to...
projects/${param:PROJECT_ID}/databases/(default)/documents/${param:COLLECTION_PATH}/{documentId}

Would we be able to update to match this pattern?
This would also allow the parameter descriptions to be simplified and similar to other extensions.
For example. Big Query simply has...
Listens for document changes in your specified Cloud Firestore collection,
then exports the changes into BigQuery.

@dackers86 I really like this suggestion and agree it would simplify the description section. The problem is this field is quasi-required since we have to support the "optional" route. Thus, it's possible we get a value that is N/A for the path. So if we assume:
projects/${param:PROJECT_ID}/databases/(default)/documents/${param:COLLECTION_PATH}/{documentId}
We are currently asking the users to enter either: COLLECTION_PATH/{documentId} or N/A. We can update the documentation such that the user provides:

COLLECTION_PATH (no longer asking user to explicitly specify /{documentId})
N/A

** This assumes we are always using a wildcard listener (/{documentId}) on all documents - which should be Ok as I don't imagine anyone will want to apply the listener on a specific document.
As a result, the above would resolve to either:

projects/${param:PROJECT_ID}/databases/(default)/documents/registrations/{documentId}
projects/${param:PROJECT_ID}/databases/(default)/documents/N/A/{documentId}

Would the latter resolution pass the regex validation pattern implemented by Firebase? If so, we could make this change.


RWARE with MAPPO training

Hi!
Whenever I try to run the MAPPO algorithm, executing:
python3 src/main.py --config=mappo --env-config=gymma with env_args.time_limit=500 env_args.key="rware:rware-tiny-2ag-v1"

I obtain the following error:
Traceback (most recent call last):
  File "/Users/miguelferreira/PycharmProjects/AASMA/venv/lib/python3.8/site-packages/sacred/experiment.py", line 312, in run_commandline
    return self.run(
  File "/Users/miguelferreira/PycharmProjects/AASMA/venv/lib/python3.8/site-packages/sacred/experiment.py", line 276, in run
    run()
  File "/Users/miguelferreira/PycharmProjects/AASMA/venv/lib/python3.8/site-packages/sacred/run.py", line 238, in __call__
    self.result = self.main_function(*args)
  File "/Users/miguelferreira/PycharmProjects/AASMA/venv/lib/python3.8/site-packages/sacred/config/captured_function.py", line 42, in captured_function
    result = wrapped(*args, **kwargs)
  File "src/main.py", line 36, in my_main
    run(_run, config, _log)
  File "/Users/miguelferreira/PycharmProjects/AASMA/epymarl/src/run.py", line 55, in run
    run_sequential(args=args, logger=logger)
  File "/Users/miguelferreira/PycharmProjects/AASMA/epymarl/src/run.py", line 127, in run_sequential
    learner = le_REGISTRY[args.learner](mac, buffer.scheme, logger, args)
  File "/Users/miguelferreira/PycharmProjects/AASMA/epymarl/src/learners/ppo_learner.py", line 37, in __init__
    if self.args.standardise_rewards:
AttributeError: 'types.SimpleNamespace' object has no attribute 'standardise_rewards'

During handling of the above exception, another exception occurred:

Does anyone have any tip on how to fix it?
Thanks in advance!

I've found the problem: in the mappo.yaml file, and regarding this commit, the flag standardise_rewards was changed to standardise_returns, but the 'standardise_rewards: False' wan't set.
I was able to use IPPO because in the ippo.yaml file, both flags were set!

I'm seeing this same issue. Any idea when this fix will be merged?


[BUG] hauler registry doesn't accept images pushed by crane

Environmental Info:

Hauler Version:

1.1.0
Describe the Bug:

crane push or a docker image saved as tar fails
crane push --verbose --insecure testdata/hello-world-amd64.tar localhost:5000/hello-world:latest

2024/12/05 15:34:08 --> POST http://localhost:5000/v2/hello-world/blobs/uploads/
2024/12/05 15:34:08 HTTP/1.1 405 Method Not Allowed
Content-Length: 19
Allow: GET, HEAD
Content-Type: text/plain; charset=utf-8
Date: Thu, 05 Dec 2024 15:34:08 GMT
Docker-Distribution-Api-Version: registry/2.0
X-Content-Type-Options: nosniff

Method not allowed

Steps to Reproduce:

https://github.com/hauler-dev/hauler/compare/main...valentin-nasta:hauler:crane-upload-test
I mainly saved the hello-world docker image and tried it to push it with crane
docker pull --platform linux/amd64 hello-world
docker save hello-world -o testdata/hello-world-amd64.tar
crane push --verbose --insecure testdata/hello-world-amd64.tar localhost:5000/hello-world:latest

::1 - - [05/Dec/2024:15:22:04 +0000] "HEAD /v2/hello-world/manifests/latest HTTP/1.1" 404 96 "" "crane/0.20.2 go-containerregistry/0.20.2"
time="2024-12-05T15:22:04.471055244Z" level=error msg="response completed with error" err.code="blob unknown" err.detail="sha256:d2c94e258dcb3c5ac2798d32e1249e42ef01cba4841c2234249495f87264ac5a" err.message="blob unknown to registry" go.version="go1.23.4 X:boringcrypto" http.request.host="localhost:5000" http.request.id=51976079-ee52-4937-a6e1-e52b359ad8db http.request.method=HEAD http.request.remoteaddr="[::1]:60256" http.request.uri="/v2/hello-world/blobs/sha256:d2c94e258dcb3c5ac2798d32e1249e42ef01cba4841c2234249495f87264ac5a" http.request.useragent="crane/0.20.2 go-containerregistry/0.20.2" http.response.contenttype=application/json http.response.duration="125.003µs" http.response.status=404 http.response.written=157 vars.digest="sha256:d2c94e258dcb3c5ac2798d32e1249e42ef01cba4841c2234249495f87264ac5a" vars.name=hello-world version=v3.0.0+unknown
::1 - - [05/Dec/2024:15:22:04 +0000] "HEAD /v2/hello-world/blobs/sha256:d2c94e258dcb3c5ac2798d32e1249e42ef01cba4841c2234249495f87264ac5a HTTP/1.1" 404 157 "" "crane/0.20.2 go-containerregistry/0.20.2"
::1 - - [05/Dec/2024:15:22:04 +0000] "POST /v2/hello-world/blobs/uploads/ HTTP/1.1" 405 19 "" "crane/0.20.2 go-containerregistry/0.20.2"
Error: POST http://localhost:5000/v2/hello-world/blobs/uploads/: unexpected status code 405 Method Not Allowed: Method not allowed

Expected Behavior:

image should be pushed to registry
Actual Behavior:
if fails with 405 method not allowed

Additional Context:

complete test case is on this commit:
https://github.com/hauler-dev/hauler/commit/e4958f3267df43d8826cdef4a32240410509aef8

Additional info:
I saw that with hauler version 1.0.4 crane push is working, but not with the versions starting with 1.0.5-rc.1
couldn't pin point the exact commit yet.
https://github.com/hauler-dev/hauler/compare/v1.0.4...v1.0.5-rc.1

hey @valentin-nasta... we introduced new behavior to the registry in v1.0.5 that defaults the registry to be readonly. You can opt into allow writes to the registry with the --readonly false flag, but we don't support updates to a store when manually writing to the registry or fileserver...
Hauler has a source of truth known as the store and I don't see us supporting manual updates to registry or fileserver right now... but let us know if you have a good use case and we can consider it!


Migrate OAuth Client ID to the correct GCP project

The OAuth Client ID / consent screen is currently configured under google.com:ruslanh-vulncodedb.
Instead, it should be running fully under vulncode-db.

Agree. Otherwise I cannot login locally and cannot use admin_required functions.

Thanks for your comment we08guyy!
Logging in locally should actually be possible now independent of the described issue.
I've explicitly added http://localhost:8080 and http://<IP_ADDRESS>:8080 as valid OAuth login origins.
The only thing you should be required to do is to replace the<EMAIL_ADDRESS>account with your own Gmail account at the bottom of the app.yaml as can be seen in the example_app.yaml, too.
Please let me know if that doesn't work or you need any assistance.

Thanks for helping~ But the Google's login page just says "Missing required parameter: client_id".

I realized my answer above is incomplete. To make this work you actually have to provide a correct OAuth consumer key and secret in the app.yaml in addition:

OAUTH_CONSUMER_KEY: ''
OAUTH_CONSUMER_SECRET: ''

The one the application on vulncode-db.com is using is not shared in the repository.
I'll add a simplified login screen which will allow to select one of the app.yaml admin accounts and bypass OAuth for the local development environment completely. I'll update this thread once this is done.

I've just addressed this with https://github.com/google/vulncode-db/commit/4ba82da9221c94a59c912706eda71ac3c3ee1a80.
It should now be possible to select and login with any specified admin on the local dev environment bypassing OAuth. Please let me know if that doesn't work :).

Created new a new OAuth service account in the vulncode-db GCP project.


Latest version list

I was looking for an API that will return to me list of newest version for browsers then I found this website. Is it possible to make something like versions.json which will return only list of latest versions for each browser. This should be easy since you already maintain that list in update.js.
For example page would display something like {Chrome: 56.0, Firefox: 51, Opera: 43}
P.S.
Also it would be useful to have release date for that version like
{
"Chrome": {version: 56, releaseDate: "01-01-2017"},
"Firefox": {version: 51, releaseDate: "01-01-2017"},
"Opera": {version: 43, releaseDate: "01-01-2017"}
}

You mean something like this one:
http://browser-update.org/browsers.json ?
https://github.com/browser-update/browser-update/blob/master/browsers.json
the release dates are a good idea.
I will add this soons

I addes some more information to the json file. But dont rely on api stability yet
http://browser-update.org/browsers.json


Web Payments API update.

Web Payments API update.

Build PaymentRequest object on page load, so that querying of slower payment apps does not result in showing a spinner when .show() is called.

Check if user has a payment instrument by calling .canMakePayment() in the new sample at paymentrequest/can-make-payment/.

Use the built-in serializer for PaymentResponse and PaymentAddress.

Add support for Basic Card payment method.

Add support for MIR credit card type.

Show 'Cannot ship outside of US' in the dynamic shipping example.

Make the shipping price "pending" until user selects a valid shipping address.

Warn that these tests work only on Android for now.

Ping.

Ping.


fix bug with sourcemaps

Fix the following bug:
[10:16:54] Error in plugin 'gulp-stylus'
Message:
    Source map to be applied is missing the "file" property
Details:
    domainEmitter: [object Object]
    domain: [object Object]
    domainThrown: false

@stevelacy : does this look ok to you? If you need me to change something about this, please ask ^^.

Could you remove the patch to the version? I bump and git tag before publishing

done

Excellent, thank you.
Travis is broken - merging anyway

Thanks. I don't see why this change would break only io.js ^^. Probably something else anyway.

It is a break in ios v2.2.0, v2.1.0 is fine


Handle ReprojTile in ol/layer/WebGLTile

Fixes #12975
The WebGL tile layer renderer handles instances of ImageTile as in the WebGL Tiles example but if the tile source is reprojected the tiles are instances of ReprojTile which should be handled in the same way.  Also as the tile cache is always that for the view projection tile grid, that is what should be expired, if it is different to the tile source projection that cache is needed for further reprojection.

Thanks, @mike-000


Option for blank line after description

Would it be possible to have an option to insert a blank line after the description, similar to the --blank option for docformatter
def factorial(x):
    """Return x factorial.

    This uses math.factorial.
    """
    import math
    return math.factorial(x)

would get reformatted to
def factorial(x):
    """Return x factorial.

    This uses math.factorial.

    """
    import math
    return math.factorial(x)

I have recently added a commit that makes it so that such lines get automatically removed.
But there is nothing stopping us from adding them again.
Just wondering, what is the reason for wanting an additional line? That might give me some inspiration for a sensible option name.

Sorry, totally missed your response Daniel!
It's mostly out of preference and I liked that the stale docformatter had the option though given that it's not had a release in a long time I probably wouldn't use it.
I think I will actually just omit this since it's probably less proper to have a useless new line in there at the end for my own readability preferences.


Installed via CocoaPods, stuck in Japanese

I've installed v2.5.1 through CocoaPods, since my app needs to support iOS 7. Now, whenever I display the picker, the title is always アルバム. My project is all-English and does not have any kind of i18n code in it.
I did have a Japanese keyboard added in Settings, which I removed, and the issue continues. It also happens on the simulator.
How can I force QBImagePickerController to display only in English?
よろしくお願いします。😀

I had the same problem lol, how should I fix it? XD

Hey I just found the solution, so in QBImagePicker, you can find the two folders named "Base.lproj" and "ja.lproj", and inside both folders there is a string file. So basically just copy the content of the string file in the Base.lproj to that of ja.lproj, and it works like a charm :+1:

@tspangler
I've just fixed and release 2.5.2.
Please try it.

@DrakeW

So basically just copy the content of the string file in the Base.lproj to that of ja.lproj, and it works like a char

It's not a solution.
You should rename Base.lproj to en.lproj.

@questbeat Fixed in 2.5.2. Thank you!

I'm having this issue using cocoapods on 3.2.0

I had same issue with 3.2.0(cocoapod). So I've manually added source code to project. And it solved the problem.


Customise css issue

how can i change date-popover  style,
Please help me any one.

This component will have class name vue-monthly-picker. If you're using less or scss, you can use deep selector  to set style for date-popover
For example:
<style lang="scss">
.vue-monthly-picker {
  /deep/ .date-popover {
    background-color: black !important;
    color: white;
  }
}
</style>


Some config can be immutable to save gas

Rationale
Some constant variables used in put() path can be replaced by immutable and save gas:

shardEntryBits
storageCost
startTime
dcfFactor
maxKvSize

This will save about 2100 * 5 = 10500 gas per put()
Implementation
Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?

Reference:

https://github.com/wighawag/clones-with-immutable-args
An idea is to use ClonesWithImmutableArgs.sol (employed by OP) https://goerli.etherscan.io/address/0x666C3d298B9c360990F901b3Eded4e7a9d7AD446#code#F2#L5

Has been fixed


Wrong ASN1 encoding of RSASSAPSSparams

Hi Castle Bouncers.
The ASN1 encoding in RSASSAPSSparams.java#L146 is really weird, because it leaves out default values. As far as I can read, none of the fields are optional according to rfc8017#appendix-A.2.3.
With this encoding, the class becomes useless for applications where receivers comply with rfc8017 and requires all the fields to be mandatory.
Am I missing something?
Thanks in advance.

Okay, I guess it is following rfc4055.
Why oh why is rfc8017 not stating that it is overriding rfc4055? 🙄
Can I ask to add a note in RSASSAPSSparams about it following rfc4055? Just to help future developers be slightly less confused.
However, I still think the rfc4055 encoding is terrible, though I understand if you need to keep it for compatibility.

A colleague pointed out that according to X.690-0207 section 8.9, DEFAULT values can be omitted, so apparently rfc8017 is not even disagreeing with rfc4055.
I guess I'll just close this issue.

Yes, it's just a general ASN.1 rule that fields with a DEFAULT may be omitted from encodings (for DER or CER, MUST be omitted) when the actual value matches the default.

Hi Peter, thanks for the hint about DER, much appreciated:)


How to add class to thead

I want to custom class names to thead, but I didn't find any ways.
Styling is for table, tr, th, and td. but I want thead or tbody.
How can I solve this?

There is a styling section in the README that will explain this: https://github.com/arnedesmedt/vue-ads-table-tree#styling use the 0-index for the header.

I know 0-index is for the header, but it doesn't indicate  tag exactly.
I want styling for thead tag.

The styling is on the tr tag in the thead.
Why not using a custom css file to style the thead?


fix: support controlled table selections for server side pagination in DataTable

Coverage decreased (-3.0%) to 87.262% when pulling c31a77989657926a5ccad66fc8b6708933f0ceaa on astankiewicz/controlled-table-selection into 942ceb2c46d8ff0d8d1045f2fee62ed2d58e4741 on master.


Certain PDF is blocked by the WAF rules

Describe the bug

Steps to reproduce

If i upload a certain PDF the Azure WAF rule kicks in and blocks stating DefaultRuleSet-1.0-LFI-930100.
The pdf is not liked by the rule. If I open the pdf in chrome and save as pdf and upload file, the path traversal rule has no problem
The original pdf is produced by iText 2.1.7 by 1T3X and version 1.4.

Expected behaviour
The

Actual behaviour

Additional context

Your Environment
This is the production environment

CRS version (e.g., v3.2.0):
Paranoia level setting:
ModSecurity version (e.g., 2.9.3):
Web Server and version (e.g., apache 2.4.41):
Operating System and version:

I also have this from the logs

action
Block

clientIP
<IP_ADDRESS>

clientPort
41099

details {

dataMatched Data: ------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10  found within InitialBodyContents: ------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10 matches [0 {matchVariableNameInitialBodyContentsmatchVariableValue------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10
data

data
Matched Data: ------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10  found within InitialBodyContents: ------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10

matches [

0 {matchVariableNameInitialBodyContentsmatchVariableValue------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10
0 {matchVariableNameInitialBodyContentsmatchVariableValue------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10

0 {matchVariableNameInitialBodyContentsmatchVariableValue------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10
0 {

0 {

matchVariableNameInitialBodyContentsmatchVariableValue------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10
matchVariableName

matchVariableName
InitialBodyContents

matchVariableValue
------WebKitFormBoundaryfXJczxhuExBuEJNi Content-Disposition: form-data; name="DocumentType"  10

msg
Path Traversal Attack (/../)

What part of the regex should we decipher to see why it is blocked?

Hi!
Thank you for reporting your false positive.
From your logs, I am not able to see why the PDF triggered the "Path Traversal Attack" rule 930100.
I don't see any ../ or so, not even encoded.
Are you able to reproduce your request with a curl request so that we could reproduce the request against https://sandbox.coreruleset.org/ for example?

A couple of things:

The rule to state does not correlate with the data. The data fits rule 920470, which validates the Content-Type header, and as part of that, multipart/form-data boundaries
It is possible that rule 930100 also triggered but that is not shown in this output
The matched string is clearly a space separated concatenation of headers, which is why it is invalid
The headers are part of a variable called InitialBodyContents, which we don't know where it comes from; it could be a query argument, a body parameter, header...

Is there any chance that you could share the PDF? Or is there some other way we could reproduce this?
Can you provide request logs for those failures?

Hi @priyanka-raghavan-maersk,
Could you please give us the needed information so that we can help you??

Hi I am not able to regenerate a document with the information like the one that is producing the problem.
However the InitialBodyContents comes from the multipart form body that is causing the issue.

This is also a screenshot of the log

While I do see the InitialBodyContents in the screenshot, I am none the wiser. The rule IDs leave me equally puzzled.
You are using a paid service from Microsoft Azure. I think it's time for their support.

Good luck. I'm closing this now on our side. If you have additional information or find out that it's really our fault, then please re-open.


Publish test results for PreCommit and PostCommit Python workflows

Publish step EnricoMi/publish-unit-test-result-action was added to the PreCommit and PostCommit workflows with Python.
https://github.com/apache/beam/issues/29075

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Thanks for the quick fix! Is this confirmed to work as expected (e.g. in a fork) or is there a preview?

Thanks for the quick fix! Is this confirmed to work as expected (e.g. in a fork) or is there a preview?

Hello,
Sure, example workflow run https://github.com/magicgoody/beam/actions/runs/6603686608


[Screen Reader - Bot Framework Web Chat- Help]: Headings are not defined programmatically on cards showing for Help keyword

User Experience:
If headings are not defined programmatically on cards showing for Help keyword, then screen reader user will be disoriented and will not be able to navigate in heading mode. The user will also be facing issues while accessing and navigating on the page.
Note: Login Credentials must not be provided within the bug.
Test Environment:
OS Version: 21H1
OS Build: 19043.1110
Browser: Microsoft Edge Version 94.0.972.2 (Official build) dev (64-bit)
Screen Reader: Narrator
Repro steps:

Open URL Provided by product owner.
Web chat bundle will open.
Navigate on the web chat bot and select microphone icon.
Speak "help" keyword in Type your message box, then select send button.
Cards related to the keyword will appear, navigate on the cards.
Verify the issue.

Actual Result
Headings are not defined programmatically on cards showing for Help keyword. 'Accessibility' heading is not defined in heading tags.
Expected Result
Headings should be defined programmatically on cards showing for Help keyword. 'Accessibility' heading should be defined in heading tags.
Note: This issue exists with similar controls throughout the application.
MAS Reference
WCAG 2.4.6 – Headings and Labels
Reference Links
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.

@v-duku could you try this out when using Adaptive Cards independently? You can use the Adaptive Card designer in preview mode to check its accessibility.
FYI, our help command is actually sending multiple Adaptive Cards.

@v-duku are you saying the "XML message" text in the screenshot below should be defined as <h1> (or <h2>...)?

In Adaptive Cards, there is no way for us to define whether a TextBlock is a header or not. You can see the schema here, https://adaptivecards.io/explorer/TextBlock.html.
Seems this is a bug/ask on Adaptive Cards side to add indication of header in TextBlock.

Adaptive Cards schema 1.5 will support style: 'heading' in TextBlock element, which will resolve this issue.
https://github.com/microsoft/AdaptiveCards/pull/5698

Talked to AC team. They are expecting to ship AC library 2.10.0 with support of AC schema 1.5 in a couple of weeks ahead.
They have 2.10.0.beta-2 up and asked us to try it out and see if the behavior is desirable or not. Will have an update soon.


luci-mod-network: wireless.js Disable 802.11b by default

The time has long come where 802.11b DSSS/CCK data rates should be disabled
by default in OpenWRT. Users in need of 802.11b client support can reasonably
enable these where they are needed.
The balance of equities has significantly, and for a long time, tipped
such that dropping backwards compatibility by default with 802.11b
devices is appropriate, proportionate and justified. By doing so,
management and control traffic is moved by default to a 20
MHz wide 6 Mb/s OFDM data rate instead of a 22 MHz wide 1 Mb/s data rate.
This is significantly more airtime efficient.
Signed-off-by: Nick Lowe<EMAIL_ADDRESS>

Taking in to account David Bauer's legitimate concerns in the PR that this depends on, I have updated the proposed LuCI patch this morning for discoverability:
Moving the option from the Advanced Settings to the General Setup tab.
Adding a description explaining potential compatibility implications. This states:
Poorly behaving 802.11g or 802.11n devices may require legacy 802.11b rates to interoperate. Airtime efficiency may be significantly reduced where these are used. It is recommended to disable this option where possible.

Received feedback suggesting to change in the wording "poorly behaving" to "badly behaving" to be clearer for those with a foreign language to English. Change made.


Add examples for MemoryStorage

Current files in examples are focused on using SledStorage.
Users might want to know how to use MemoryStorage.

Please @MRGRAVITY817 , can i have more explanation about it?

Just adding an example for memory storage in a folder at https://github.com/gluesql/gluesql/tree/main/examples

Ok thanks.


error C2065: 'NBGV_INFORMATIONAL_VERSION': undeclared identifier

NBGV_INFORMATIONAL_VERSION is a constant used in
vswhere\Program.cpp(156)
I can't see it defined anywhere in the project, but I suspect you need some build steps to get it created somehow. Please advise.

You need to run nuget restore on the solution prior to building.

nuget restore

OK I ran nuget in vswhere git root, like so:
nuget restore <vswhere>
I got a prebuilt binary with the message
"Adding package 'vswhere.1.0.62' to folder 'vswhere\packages'"
Sorry I'm still a bit lost, where can VS find NBGV_INFORMATIONAL_VERSION?

In the solution root, just run: nuget restore. No arguments. The symbol is generated automatically from one of the packages (Nerdbank.GitVersioning) that gets restored.

Admin console in git root repository:
F:\dev\vstools\vswhere\vswhere>nuget restore
MSBuild auto-detection: using msbuild version '4.0' from 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319'.
All packages listed in packages.config are already installed.

I guess it should show up in some props file but I can't it.

What do you mean you upgraded the packages? All that's necessary is to restore the solution from the solution root directory (the .sln file) and build. Also, if you're using MSBuild 4.0 (which I see from above) it may not support everything. Use a developer command prompt or update your PATH to use MSBuild 15.0 from within VS.

Rightclick solution -> "Restore NuGet packages"
As I said, I did it early on in troubleshooting the failures.

"and build"
No, the projects need to be retargeted unless I install the VS2017 XP toolset and then some.

To try again, I did a reset from git to get a clean tree and executed nuget restore. I ended up in exactly the same situation.
It's not difficult to patch the failing parts and get a working binary and a build can be done in many ways. The NBGV_INFORMATIONAL_VERSION constant isn't as far as I can tell vital for functionality. I just defined it to 0.

A nuget package generates that symbol. I reviewed the change to the project that did it (I also wrote a prototype but someone beat me to merging such a change). But if you're changing the solution and/or project instead of installing the required components, I can't really tell you why it's not working. If you check out the project as-is and restore/build without changes, it should work. It's worked across a myriad of machines with different combinations of VS2017 and VS2019, as well as Azure hosted machines. If there's problems building the unaltered repo with the required components installed, I'm happy to assist further but would need logs.


Ugoira error message when converting to mkv

Prerequisites

[ x] Did you read FAQ section in readme.md?
[ x] Did you test with the latest releases or commit ?
[ x] Did you search for existing issues in Issues?

Description
I downloaded and converted some ugoira files to mkv however during the conversion I got several error messages like the following:

The specified filename 'C:\Users\xxxxxxxxxxxxxx\AppData\Local\Temp\convert_ugoiradhgs1ckk\000003_temp.jpg' does not contain an image sequence pattern or a pattern is invalid.

The conversion ended and each mkv files were created for each ugoira. I played them with a video player and as far I can tell they seem to play without any problem. I'm unsure why it shows this error message if nothing bad happen, unless there is something I have not noticed yet.
Steps to Reproduce

Open PixivUtil2.exe and select option 2
Enter the image IDs 71702827 and 71681882 and hit Enter

Expected behavior: [What you expected to happen]
Ugoira files are converted to mkv and there are no error messages.
Actual behavior: [What actually happened]
Ugoira files are converted but multiple error message shows up during the process.
Log file:
Pixiv ugoira.log
Config
[FFmpeg]
ffmpeg = ffmpeg.exe
ffmpegCodec = libvpx-vp9
ffmpegExt = webm
ffmpegParam = -lossless 0 -crf 15 -b 0 -vsync 0
mkvCodec = copy
mkvParam =
webpCodec = libwebp
webpParam = -lossless 0 -compression_level 5 -quality 100 -loop 0 -vsync 0
gifParam = -filter_complex [0:v]split[a][b];[a]palettegen=stats_mode=diff[p];[b][p]paletteuse=dither=bayer:bayer_scale=5:diff_mode=rectangle -vsync 0
apngParam = -plays 0 -vsync 0
verboseOutput = False
[Ugoira]
writeUgoiraInfo = False
createUgoira = True
createMkv = True
createWebm = False
createWebp = False
createGif = False
createApng = False
deleteUgoira = False
deleteZipFile = False
Versions
20230105
Windows 10 Pro 22H2

Does it show up with webm  as well?

It doesn't look like a problem with the program but with the file. It seems to be harmless

FFmpeg uses the image2 demuxer for JPEG files. This demuxer can be used for single images (like in your case) or to assemble a video stream from a series of images.
This message is completely harmless but you can suppress it by specifying -pattern_type none before the input filename.


Ethereal Ember Sprite is Darker than Intended

Mod Version
v<IP_ADDRESS>
Terraria and tMod Version
v<IP_ADDRESS> and v2<IP_ADDRESS>
Steps to Recreate

Open a World
Acquire an Ethereal Ember
Sprite is Darker than Original in all Instances

Further Details
Side by Side,
Original on Left,
Maximum Ingame Brightness on Right

Other Enabled Mods
Better Zoom
Shift-Click Crafting
Tome of Research Sharing
Realistic Sky
Concise Mods List
Smarter Cursor
Particle Library
Heart Crystal & Life Fruit Glow
High FPS Support
Recipe Browser
Echo Dye
Fancy Lighting
Instant Platform Fallthrough
DragonVault
imkSushi's Mod
ArmamentDisplay
ShorterRespawnTime
Max Luck
Auto Trash

This seems to be intentional for some reason, the color of the item is set to rgb 180, 180, 180. I just made it 255, 255, 255 because why is it slightly darker?


Define Color Scheme

This should make for a consistent experience
across terminals. This defines a basic black/white
color scheme.
#Hacktoberfest
Each terminal defines its concepts of Black and White.
In iTerm2

Inside JetBrains Rider (Dark Theme)

Thanks!

Found an issue with JetBrains Rider not capture the Shift+Tab keystroke. It seems to work fine in iTerm2.

Fixes #9

Thanks @khalidabuhakmeh! I inverted the color scheme as the other one felt too bright in Windows Terminal.


"Warn" log setting misfunctioning

The "warn" log setting is printing all messages. I found what to fix:
In utils.ts in lines 91 and 92,
replace this:
    case "warn":
      return !["debug","info","log"].includes(logLevel);

with this:
    case "warn":
      return !["debug","info","log"].includes(logEvent.level);

like in lines 93 and 94 below it.

Thanks for the report, I'll see that I'll release a fixed version later today!


rework example notebook

It would be nice if the current example https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io/blob/main/Notebooks/temp_sense_gencollab.ipynb only contained the required section header, so that people can more easily use it as a base template for their project.
It should also named as "example" or "template" to make it more explicit, it is documenting the base structure of the notebook.

Reworked the example notebook here:
https://colab.research.google.com/gist/proppy/4c441683a02dbb87004d449955102156/template_notebook_to_follow.ipynb#scrollTo=aKoPD8cKw2UL

Thanks @proppy
Can you send a PR here: https://github.com/sscs-ose/sscs-ose-chipathon.github.io

Done https://github.com/sscs-ose/sscs-ose-chipathon.github.io/pull/6


BishiBashi not saving scores?

IBB connection looks fine but scores don't save for the next session...

Yeah, the game has no provisions for this as far as I could ever tell. No packets for where to store scores, nothing from the client to the server with said scores. I don't think it ever did this. The services basically let you do the character unlock gacha and support the optional extra hand, as well as enable/disable global game options.


mdbook-admonish: 1.14.0 -> 1.15.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tommilligan/mdbook-admonish/releases.
meta.description for mdbook-admonish is: A preprocessor for mdbook to add Material Design admonishments
meta.homepage for mdbook-admonish is: https://github.com/tommilligan/mdbook-admonish
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.0 with grep in /nix/store/mw6671nkdqkw9nwhnmajqfds4qnxvady-mdbook-admonish-1.15.0
found 1.15.0 in filename of file in /nix/store/mw6671nkdqkw9nwhnmajqfds4qnxvady-mdbook-admonish-1.15.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mdbook-admonish

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mw6671nkdqkw9nwhnmajqfds4qnxvady-mdbook-admonish-1.15.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mdbook-admonish https://github.com/r-ryantm/nixpkgs/archive/4ab598b846b83d0c7440de0477eb068626b15ae6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4ab598b846b83d0c7440de0477eb068626b15ae6#mdbook-admonish

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mw6671nkdqkw9nwhnmajqfds4qnxvady-mdbook-admonish-1.15.0
ls -la /nix/store/mw6671nkdqkw9nwhnmajqfds4qnxvady-mdbook-admonish-1.15.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mdbook-admonish

Maintainer pings
cc @jmgilman @Frostman for testing.

Result of nixpkgs-review pr 277932 run on x86_64-darwin 1

1 package built:

mdbook-admonish


perf(build): enhanced routing from nginx to django

Issue link
Relates #177
What does this PR do?
What does not include in this PR?

24-03-08 11:50:03 git/bennu-official [perf/177/staticfiles] % curl -D - -o /dev/null -s -X GET https://bennu-official.page/assets/bennuhp/img/20150708-live.png
HTTP/2 200
date: Fri, 08 Mar 2024 02:50:08 GMT
content-type: image/png
content-length: 130066
last-modified: Fri, 08 Mar 2024 02:36:28 GMT
etag: "65ea79ac-1fc12"
expires: Sat, 09 Mar 2024 02:50:08 GMT
cache-control: max-age=86400
x-frame-options: SAMEORIGIN
accept-ranges: bytes
strict-transport-security: max-age=31536000; includeSubDomains


Update README to new GOV.UK standard

The list of formats is probably incomplete, but it's a start.
I expect the instructions for running the app to be the most helpful bit of this documentation.

LGTM, huge improvement. :+1:

@alext updated and force pushed. Good to merge?

Looks good to me.


Travis: _srcdist, not _srcdir

+1 assuming builds pass

If you take a look, the Travis builds on this PR have passed a long time ago ;-)

Merged


[Bug] Even after SparkContext stopped in yarn-client mode, Kyuubi plugin is fetching updated policies from Ranger. Spark driver does not end.

Code of Conduct

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

Search before asking

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

Describe the bug
I am submitting a SparkSql job through spark-submit. Spark version 3.3.1 and Kyuubi version 1.8.0. I am using Open Source Spark Engine with Kyuubi Authz module running on top of the Spark Driver in client mode. The Spark job is successful, but the Spark Driver does not stop and keeps on running and I see the PolicyRefresher keeps on polling policies from Ranger.

If you see the logs, PolicyRefresher is still running even after Spark Context has stopped. This is leading to the Spark Driver not ending and therefore after sometime I have to manually kill the job.
Can someone please help in this issue?
Affects Version(s)
1.8.0
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[ ] No. I cannot submit a PR at this time.

Sounds like non-daemon threads blocks the Driver JVM to exit, you can find them from the jstack, I roughly remember that Ranger's solr and es audit plugin has such issues, not sure if they get fixed.

Thanks @pan3793 for replying
"org.apache.ranger.audit.queue.AuditBatchQueue1-EventThread" #200 daemon prio=5 os_prio=0 tid=0x00007f1bec01b000 nid=0x4ca3 waiting on condition [0x00007f1bc3c03000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x00000007b20c9c88> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:559)
"org.apache.ranger.audit.queue.AuditBatchQueue1-SendThread(zk1-abc3.aadds.xyz.com:2181)" #199 daemon prio=5 os_prio=0 tid=0x00007f1bec019800 nid=0x4ca2 runnable [0x00007f1bc3d04000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x00000007b20c8050> (a sun.nio.ch.Util$3)
- locked <0x00000007b20c8040> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000007b20c7c50> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:332)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1290)
"MdsLoggerSenderThread" #157 daemon prio=5 os_prio=0 tid=0x00007f1bd265c000 nid=0x4c52 sleeping[0x00007f1bc7027000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at com.microsoft.mdsdclient.MessageSendingRunnable.run(Unknown Source)
at java.lang.Thread.run(Thread.java:750)
"policyDownloadTimer" #138 daemon prio=5 os_prio=0 tid=0x00007f1d4feab800 nid=0x4c3d in Object.wait() [0x00007f1bf59e2000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:552)
- locked <0x00000006c2b54748> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:505)
"PolicyRefresher(serviceName=abc3-azsuu004-hive)-137" #137 daemon prio=5 os_prio=0 tid=0x00007f1d4feab000 nid=0x4c3c waiting on condition [0x00007f1c4416e000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x00000006c2b54838> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:213)
I think you are right in the sense I see AuditBatch threads in the jstack. Anyway to fix this?

@amanraj2520 all the above you listed is daemon threads, but the matter is those non-daemon threads

"zkConnectionManagerCallback-5-thread-1" #202 prio=5 os_prio=0 tid=0x00007f1cbc003000 nid=0x4ca7 waiting on condition [0x00007f1bc3a01000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x00000007b218dad8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
"DestroyJavaVM" #453 prio=5 os_prio=0 tid=0x00007f1dfc019000 nid=0x4ab5 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"VM Thread" os_prio=0 tid=0x00007f1dfc09a000 nid=0x4ac3 runnable
"VM Periodic Task Thread" os_prio=0 tid=0x00007f1dfc10e800 nid=0x4ad4 waiting on condition
@pan3793 These are the non-daemon threads running. Any clues?

zkConnectionManagerCallback-5-thread-1 is likely created by Solr, that what I said the Ranger Solr audit plugin issue.
You may want to temporary disable Ranger Solr audit plugin to verify that.

Thanks a ton for suggesting this @pan3793 . I will check this and get back to you in sometime. Really appreciate your prompt and useful response on this. I will update this thread accordingly and if needed will raise a PR to fix this as well.

@pan3793 Thanks a lot for your suggestion. The issue of Spark Driver getting stuck is fixed now!!
The temporary fix was to set xasecure.audit.destination.solr to false thereby disabling logging to solr and in the jstack there was no more non-daemon thread running.
Having said this, it is our use case to enable Solr logging, is there any way that comes to your mind to fix solr side of things? Is there a discussion going on somewhere that you are aware of?

This should be a Ranger/Solr issue and I recommend you report it to the Ranger community.

Sure we can close this for now. Thanks again!!

@amanraj2520 NP, and you are welcome to add cross-links here if you have better solutions to this problem.

Perhaps we can enhance our documentation to assist others in understanding this problem and resolving it as well.

Sure @yaooqinn Will do that.
@pan3793 After some debugging found that the SolrZkClient creates threads with daemon as false, that's why they are non-daemon threads

So as per my understanding solr client runs on top of spark driver and when spark context is shutdown, ideally there should not be any solr client thread running right? Do you think making it as daemon as done for the PolicyRefresher thread in Ranger in this - https://issues.apache.org/jira/browse/RANGER-1083 work? I will give it a try and update this thread.
So in a nutshell the issue is this that the non-daemon thread of SolrZkClient are not exiting thereby leading to Spark Driver to run even if spark context is shutdown. Ideally this issue will not be for long running spark-shells or livy/zeppelin sessions, since they end by manual intervention of the end user. But in cases of spark-submit where the sparkContext has to run for a definite amount of time, SparkContext needs to have a way to end the SolrZkClient threads. This issue might not have impacted other services of Ranger (like hive, yarn etc) since they are long running sessions as well.

@amanraj2520 Basically right, all third party components should use non-daemon threads in the Spark Driver. AFAIK, Spark YARN/K8s client mode and K8s cluster mode will hit non-daemon threads issues, but YARN cluster mode will not.

@pan3793 So you think making SolrZkClient as daemon will not work?

I think it will work

Sure then will try my scenario with this patch

@pan3793 Good news it worked by making solrZkClient as daemon thread. Thanks a lot for your help in this. I have filed for an OSS PR in SOLR as well - https://github.com/apache/solr/pull/2376
Raised a JIRA ticket for the same as well - https://issues.apache.org/jira/browse/SOLR-17220


enable automatic publish after dependabot

I've tried several approaches:

publish on push to develop
it looks most as the most natural, but push event isn't triggered after dependabot pr was merged if this automerge was set from action
separate action on PR event "closed" that, if status is "merged", triggers publish event
this way we rely on the fact that we never actually push to develop directly and always merge PRs there. But triggering other action via scripts didn't really work. Nothing in the logs. Looks like it can't find the actor who did this and skipped it. When I've triggered it manually - all worked.
trigger publish of PR "closed" and publish merge commit.
this one may have some quirks if there are several PRs opened simultaneous, but even this didn't work and never triggered PRs on "merged" status. It triggered once dependabot closed PR as unneeded, but not on merge. Strange

[ ] try logging all PR events, it's a bit strange that in (2) actions were triggered on "closed", but for (3) they aren't. Is it due to target branch?
[ ] the worse case would be adding my personal token to trigger action with it for case (2), but let's postpone this


WIP: Network stack enh.

Code for #303
This contains the final dev version of code, needs another pass of code review.
This code has been profiled though instruments with one adverse leak detected in existing code (added a #warning).
Please review at your convenience, I will update the Pull Request before it is ready for merge.
During the refactor I also updated several places to modern objc. and removed some dead code.

@Wizecoder @aaronbrethorst Any input for @beliyd here?
Looks like you were close to finishing this -- it would be awesome to have this merged in (looks like it will take some rebasing first, unfortunately) for the next version if possible.

@caitbonnar — I think the changes are expansive enough that I'd need to run it on my phone for a day or two to ensure that everything's ok. A cursory glance suggests everything's good, though.
@beliyd — can you fix the merge conflicts and give me a head's up when those changes are added to this PR? I'll check out your branch and then run it on my phone. Thanks!

@aaronbrethorst I'll pull the parent and resolve conflicts on Saturday.  Thanks for testing this out!

Thank you!
Sent from my iPhone

On Feb 2, 2015, at 6:52 PM, Dima Belov<EMAIL_ADDRESS>wrote:
@aaronbrethorst I'll pull the parent and resolve conflicts on Saturday. Thanks for testing this out!
—
Reply to this email directly or view it on GitHub.

@beliyd - any chance to bring your branch back in sync with develop?

@aaronbrethorst working on it.

Awesome, thanks!
Sent from my iPhone

On Feb 15, 2015, at 4:01 PM, Dima Belov<EMAIL_ADDRESS>wrote:
@aaronbrethorst working on it.
—
Reply to this email directly or view it on GitHub.

Pulled in the upstream & fixed a few clang warnings.

@beliyd - I have your code running on my phone. I'll test it for the rest of the day and—if all goes well—get it merged in tomorrow or Thursday. Thanks!

Looks good, merging. @beliyd — Thanks again!


Add packs using packid

Fix: https://github.com/Open-CMSIS-Pack/cpackget/issues/19
This PR does the following

Allows packID to be used to install packs:
1.1. Now the following pack add options are supported: cpackget pack add ARM.mbedClient or cpackget pack add ARM.mbedClient.1.1.0 or cpackget pack add http://www.keil.com/pack/ARM.mbedClient.1.1.0.pack or cpackget pack add ARM.mbedClient.1.1.0.pack
It can find pack urls either using the pdsc URL + packID or via the url attribute in the release tag
2.1. If the url in the release tag end with some other file name, cpackget will make sure to name it to its proper pack file name when placing it under ".Download"
If a pack content is contained within a subfolder in the compressed file, cpackget will decompress that in the pack root folder, without the subfolder
3.1. If the pack content is under "compressedPack/contents", it'll be decompressed as "$CMSIS_PACK_ROOT/Vendor/PackName/x.y.z/contents", removing the "compressedPack" subfolder.

Great stuff. Please address the failing windows test.

Yeah, Windows didn't like one of the renaming operations. Investigating why


New package: JD.JoyMeeting version V<IP_ADDRESS>907

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

This installer reported ShellExecute error: 1 as a failure, but installed successfully. Verify while here:


WorkBox does not perform update method

Version
3.0.0-beta.6
Steps to reproduce
Phases:

Run vue create app and select PWA.

Run yarn build and serve ./dist to test the site in production.

After accessing the site and waiting for the cache to be done, disable the internet and check for offline access.

Edit the App.vue by putting some more content.

Run yarn build and serve ./dist to test the production site again.

What is expected?
The workbox message is expected: New content is available; please refresh.
What is actually happening?
The message is not displayed, so the workbox is not detecting that the content of the application has been updated.
I've already checked that the service worker is in the cache and is not.

I have seen that although the updated register-service-worker method is not called, the service-worker collects the update and waits to install. As in the image below:

So maybe this can help.

I do not know if it was the right solution, but I managed to circumvent it. I put the workbox to skip the wait, in vue.config.js:
module.exports = {
  lintOnSave: false,
  pwa: {
    workboxPluginMode: 'GenerateSW',
    workboxOptions: {
      skipWaiting: true
    }
  }
}

And in registerServiceWorker.js I changed all content, registering my SW and whenever it is registered I check the temporary cache of the workbox, if it has any content is because the workbox has captured an update and is ready to replace the cache:
/* eslint-disable no-console */

const updated = () => {
  console.log('Has new content!')
  // use window.location.reload(true) to get new cache
}

const register = async (path) => {
  const registration = await navigator.serviceWorker.register(path)
  console.log('SW registred!')

  const cacheList = await caches.keys()
  cacheList.forEach(async (cacheName) => {
    if (!cacheName.includes('-temp')) return

    const tempCache = await caches.open(cacheName)
    const tempCachesKeys = await tempCache.keys()
    if (tempCachesKeys.length > 0) {
      updated()
    }
  })

  registration.onupdatefound = () => updated()
}

const { NODE_ENV, BASE_URL } = process.env

if (NODE_ENV === 'production') {
  if ('serviceWorker' in navigator) {
    register(`${BASE_URL}service-worker.js`)
  }
}


Can't install CrackMapExec v5.0.2dev

Describe the bug
Can't install CrackMapExec on Linux Kali. Error:
Installed /usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg Processing dependencies for crackmapexec==5.0.2.dev0 error: asn1crypto 0.24.0 is installed but asn1crypto>=1.3.0 is required by {'minikerberos'}
To Reproduce
Steps to reproduce the behavior:
Run commands:
#~ apt-get install -y libssl-dev libffi-dev python-dev build-essential #~ git clone --recursive https://github.com/byt3bl33d3r/CrackMapExec #~ cd CrackMapExec #~ python3 setup.py install
Expected behavior
Successfully installed tool.
Crackmapexec info

OS: Kali
Installed by instructions from https://github.com/byt3bl33d3r/CrackMapExec/wiki/Installation

Much better, I will investigate :)

Hello @vezjak can you try to upgrade asn1crypto ?
pip3 install asn1crypto --upgrade --user

People confirm me this issue comes from Impacket, update to 0.21

First make sure you have pip3 installed
sudo apt update
sudo apt install python3-pip
then;
pip3 install asn1crypto==1.3.0
pip3 install asn1crypto --upgrade --user
followed by
pip3 install prompt-toolkit==2.0.9
Hope it was helpfull :), mine worked tho.

Sharing my experience in case that helps
for me error was this:

Installed /usr/local/lib/python3.7/dist-packages/crackmapexec-5.1.0.dev0-py3.7.egg
Processing dependencies for crackmapexec==5.1.0.dev0
error: asn1crypto 0.24.0 is installed but asn1crypto>=1.3.0 is required by {'minikerberos'}

I resolved by installing that asn1crypto directly in that directory itself

$ sudo pip install asn1crypto==1.3.0 -t /usr/local/lib/python3.7/dist-packages/

Same problem on Python 3.9. None of solutions suggested worked for me.

Same here, having the same problem with CME.   ;)


split too large method MarathonDiscoveryClient.getInstances on several small

Coverage increased (+0.2%) to 70.57% when pulling be3d6700970ee4a968ee8845af25c9d103891627 on vatarasov:MarathonDiscoveryClient_refactoring_3 into 31f7473219e1bd67689c7fb9bf5be87c764457fc on aatarasoff:master.


Use Resurrection ability if more than half of the players on the lane are dead

I'd say this isn't always optimal, such as if players have been AFK for so long that they haven't upgraded armor and will die quickly even with resurrection.
Maybe take into account number of active players?

If auto-buying of upgrades was implemented then you wouldn't need to worry quite as much about AFK. But an active player check would be a good idea either way.

What do you guys mean by 'active'? I'm not sure if there's a way to see the number of players who are signed out. I have a resurrection policy on mouseas: https://github.com/mouseas/steamSummerMinigame/pull/61. Check out useReviveIfRelevant()


docker compose vs docker-compose

The script is currently using compose sub-command of the docker executable.
It is v2 of the standalone docker-compose and it is fairly new so some environments may be outdated and show the lack of this sub-command.
We should check if docker compose sub-command exists before using it and use docker-compose otherwise.

Solved in 1.1.0 release #3


WIP: < 75 ms/step on 7900XTX: examples/hlb_cifar10.py while keeping 90% (float16/bf16 okay)

So far, changed linearizer to do calculations based on buffer dtypes, and also made grouping generic to vector dtypes
a = Tensor.rand(10,10, dtype=dtypes.float16) # also works for int32
(a+a).realize()

gives a nice kernel output
#pragma OPENCL EXTENSION cl_khr_fp16 : enable
__kernel void E_25_4(__global half* data0, const __global half* data1) {
{ int gidx0 = get_group_id(0);  /* 25 */
    half4 val1_0 = (half4)(*((__global half4*)(data1+(gidx0*4))));
    half4 alu0 = (val1_0+val1_0);
    *((__global half4*)(data0+(gidx0*4))) = (half4)alu0;
  } /* global+local */
}

The Dtypes could be cleaned up a bit.
Need to test actual training with float16 tensors

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/codegen/cstyle.py                 1               1
tinygrad/codegen/linearizer.py            17              18
tinygrad/helpers.py                       12               3
tinygrad/lazy.py                           1               1
tinygrad/runtime/ops_gpu.py                1               1
------------------------------------------------------------
total                                     32              24
------------------------------------------------------------
lines added in the tinygrad folder: 8

Still need to test other backends, only tested with OpenCL.
CI for OpenCL fails because
91:1:26: warning: unsupported OpenCL extension 'cl_khr_fp16' - ignoring

I'll get you a computer with a 7900XTX, give me a few hours.

Progress summary:

dtype used in all kernels used to be float32: changed this to use dtypes based on buffers

Tests pass for:

GPU (locally, cl_khr_fp16 needs some workaround for CI)
CLANG
CPU
CUDA
TORCH

Fails for

webgpu
LLVM
Metal

have kept accumulate vars in float32, can be controlled with ACCUM_FLOAT env var (because accumates in half might overflow)

Backward pass for cifar with HALF - but the training diverges

This is a known problem with fp16, need to do mixed precision  https://arxiv.org/pdf/1710.03740.pdf

Added HALF to test_speed_v_torch, though there are variations b/w runs heres a summary (similar fp16 numbers with ACCUM_FLOAT=1 and 0)
add                             8192 x 8192    4.83 ms  (   13.89 GFLOPS   166.66 GB/s) in tinygrad fp32  805.31 MB
exp                             8192 x 8192    4.23 ms  (   31.72 GFLOPS   126.87 GB/s) in tinygrad fp32  536.87 MB
gemm                            2048 x 2048    2.13 ms  ( 8048.53 GFLOPS    23.58 GB/s) in tinygrad fp32   50.33 MB
gemm                            4096 x 4096    12.82 ms (10718.67 GFLOPS    15.70 GB/s) in tinygrad fp32  201.33 MB
conv bs: 32 chans:128 -> 128 k:1               6.15 ms  ( 2793.23 GFLOPS    87.30 GB/s) in tinygrad fp32  536.94 MB
conv bs: 32 chans:128 -> 128 k:3               9.76 ms  (15843.48 GFLOPS    55.94 GB/s) in tinygrad fp32  545.91 MB

add                             8192 x 8192    0.78 ms  (   86.37 GFLOPS   518.25 GB/s) in tinygrad fp16   402.65 MB
exp                             8192 x 8192    0.35 ms  (  378.64 GFLOPS   757.28 GB/s) in tinygrad fp16   268.44 MB
gemm                            2048 x 2048    1.21 ms  (14163.54 GFLOPS    20.75 GB/s) in tinygrad fp16    25.17 MB
gemm                            4096 x 4096    5.89 ms  (23322.78 GFLOPS    17.08 GB/s) in tinygrad fp16   100.66 MB
conv bs: 32 chans:128 -> 128 k:1               1.08 ms  (15927.31 GFLOPS   248.89 GB/s) in tinygrad fp16   268.47 MB
conv bs: 32 chans:128 -> 128 k:3               13.10 ms (11806.21 GFLOPS    20.84 GB/s) in tinygrad fp16   272.96 MB

3x3 convs are somehow slower in FP16

Running cifar in HALF (even with ACCUM_FLOAT=0) isn't acutally faster currently

time is still ~150ms / step

What I'm working on:

with OpenCL, there's no control on what assembly instructions it emits. DOT2ACC instructions in RDNAv3  are what actually enable 2x fp16 throughput. maybe HIP backend will emit DOT2ACC instructions, or we need to get to into RDNA assemler.
Its know that using vector dtypes is faster in OpenCL. try to increase use of vector dtypes in kernels, maybe improve some hand_coded_optimizations.
Mixed precision training
getting tests to pass on webgpu, LLVM, Metal

Great to see this moving, happy to see this work have an impact! Hope to do another release in the next few weeks or so.
I'll update if I see anything here, but Re: "Backward pass for cifar with HALF - but the training diverges"
There's a note that says This is a known problem with fp16, need to do mixed precision https://arxiv.org/pdf/1710.03740.pdf It's true that you can do mixed precision, but the casts are a bit dicey and add some extra complexity. I don't know if bfloat16 is supported in tinygrad but it adds a lot of stability for a tiny speed hit (and is often simpler/faster than mixed precision IIRC)
I don't know if that helps, the code looks good from here and some brief browsing. I spent about a month banging my head against the wall trying to do a byte-for-byte rewrite of David Page's code, so I guess it's a rite of passage!
Happy to share any technical quirk tips or whatever, I'm in the thread now so I should get pinged if you have any thoughts/questions.
Good stuff! <3 :)))) :D 🎆 🐧

Okay, I've done a little more thorough of a review, and hopefully this is helpful! Format is diffs [line: diff+notes] + reasons/extra thoughts behind it. It might be a bit overwhelming, but hopefully this answers any major questions and helps point out where a lot of the training instability is very likely coming from. :')))) <3 :D :D :) I don't know the ins and outs of tinygrad so if at all I have some horridly fruitless ignorance here, please excuse me (and we can leave it on the big ol' TODO pile for later! :D <3 <3 <3 <3 :)))) )
Diffs:
--l46 couple of .numpy() calls, which looks like it might bottleneck things a tad w/ CPU moves. I don't know if there's a special pass-by-reference happening here to the Tensor class, but if it's a copy then that's going to be quite slow (especially since we do use this function ~30-40+ times or so during training.
--l56 track_running_stats=False -> True (!!!!!), eps 1e-4 -> 1e-12, momentum 0.8 consider -> 0.5
--l57 relu -> gelu is important, the full version too with the CDF and not the fast approximation. Both gradient stability and training speed. Gelu gives good gradient coverage as well a decent boost to expectations + training stability (ironically before selu, the OG, came out, iirc :'OOOO). Yay for self-normalizing, gated units! :)
--l59 more of a 'novel invention'-oriented kind of note, but how you manage your buffers here at the lower levels is where we have some room for improvement. A lot of separate operations that maybe with some tiny changes could be fused together nicely in a way that's quite snappy.
--l61 id personally move the max pool to a new line as its sorta easy to miss, but hybrid is not the end of the world. basically, i think having an expectation of a novel operator on each line or all at once is a good one (since this code layout seems to set an expectation of one per line). just minor 'bug surface for the casual dev' kind of thought. Hotz I think likes chained commands so maybe in this repo slopping lines 61-65 into a long chained expression in 61 is okayish (and logically does one 'block chunk' per line)
--l62 reminder to eventually remove casts, hopefully these other changes will stabilize it a bit.
--rest of the function looks good! :D :)
--l76 ! whitening. this is probably why training is unstable, not the float16 issues. Whitening can seem hard but it's really not too terrible if you transcribe the code. The earliest layers of the network are always the most important for training stability. Basically, always always.
--l79 kernel size of 1 will probably, uh, not do too much for you! That's basically BASE_DIM vectors of size 3, which more than spans the input space, so its more or less redundant and the training thrash isn't worth the extra expressivity. It's sorta the whitening thing -- a very unfun chore, but necessary. LMK and we can get on a voice call and pair program this section together if you want. It's really worth it! :D :))))
--l77 BASE_DIM, Looks good, though I think we can trim this up a lot! I'd just steal whatever the dims are from the latest hlb-cifar10 (v0.7.0 coming out...soonish....), since network dimensions can be a huge limiting factor in speed. Once you get the ratios right, then using a scaler against the semi-hardcoded base values becomes more effective, as it seems that that kind of scaling works, er, generally enough-ish. 64 Is pretty overkill for a base dim, ive gotten away with much less and that might help with speed/overfitting/etc! :D :))))
--l83 relu occurence
--l92(93 and 101) log_softmax can be a bit funky sometimes, so just keep this in mind. I'd recommend returning the raw unnormalized logits instead of the log_softmaxed ones since that's a bit more standard (and can avoid some other issues down the road....)
--l151 Small reminder on the batchsize -- it can be easier to get higher accuracies due to more steps, pushing this to 1024 (or whatever it is live, I think that's it....) can help tho if you copy hyperparams. The others look pretty okay to me, though pct_start is extremely agressive in this version (I may have had it that aggressively in the past, can't recall, but .2 is a good safe-ish number to use. See latest version for more info). Momentum I can't remember exactly where it is, but that's a somwhat sensitive parameter, I think it's .85 in the latest version IIRC? WD should be an exact value not a rounding as it's quite sensitive. Label smoothing on and at .20 (very important for stability!)., and cutmix >= mixup as A. it's easier (can just slice out different pixels instead of blending, and can just...reference swap in the right scenarios?!?!?), and B. performance!, so I'd go with the cutmix_epochs and cutmix_size parameters if possible. Whew, that's a lot! All very important though! <3 :)))) :D :D
--l176 Don't know if the lr hardcode here is critical or not, but might as well set it to something like max_lr*final_lr_ratio for posterity/reducing accidental bug fallthru status
--l183 highly highly highly recommend doing this before doing any network training at all! It's not counted in the training time as it's basically part of the dataset download and prep, and only should be done once (before the dataset is saved to disk in an easy-and-fast-to-load-format. Free speed right 'dere ! :)))) Remember, if we think about fusing as much as possible, doing it in a pre-epoch and/or pre-training step is a great way to help ourselves out. :))))
--l188 This almost looks like entropy regularization (https://arxiv.org/abs/1701.06548) instead of label smoothing. While ER is my first love, LS is what the repo came with and was tuned around -- it works pretty well! Maybe some benefits to be had, but I'd save the swap for later. (I believe it should be out.mul(1-Y).mul(-LABEL_SMOOTHING).mean() in the last factor IIRC).
--l189 FP32 vs FP16 debugging
--l207 same as before w.r.t. normalization.
--l208 Keeping the running stats here is what lets the model perform well in eval, ideally.
--l209 maybe micro op is a gather vs a mul, would also save having to make one hots (I guess I should update the base repo for this too)
--l226 If you create a virtual array w/ cutout and do it before the epoch, you can avoid having a left- and right-batcher. little bit less data flying overhead to and from things
--l235 per same caveats before, appears to be a device-swap thrash. all-gpu and only-slicing is good! :D :))))
--l243 oddly enough I would return last_eval over best_eval, possibly simply for the reason that the last_eval should be the best eval, it simplifies things, and oftentimes eval performance near the end is gaussian with noise, so when it's done best, returning the last should actually give better performance overall instead of cherrypicking based on eval set noise (basically, our eval performance is distributed in a gaussian way, and we don't want to arbitrarily bias the stats in our favor unnecessarily. Since every step counts, we want the model that's used every step, and for that to be as good as possible! <3 :)))))
And that should be about it! Hope this helps, lots of little technical notes, but I can assure you that on many, many, many of these points I have spent countless silent hours forming a hole in the wall with my head.
Happy to answer any questions as necessary. <3 :)))) :D :))))) :D <3

@tysam-code thank you for the detailed notes! unfortunately, this PR is a bit messed up, it has a lot of code we don't really need now. Also, we've had @g1y5x3 clean up a lot of this code already, and it reaches 94% in 1000 steps! it is already merged in master.
on top of his changes, fp16 were minimal.
here's the diff
essentially doing batch norm in fp32, changed loss scaler, and label smoothing to 0.1 and got me
999   90.23 ms run,    4.23 ms python,   86.00 ms CL,  289.50 loss, 0.000000 LR, 3.73 GB used,   7473.38 GFLOPS
eval 9413/10000 94.13%,    0.29 val_loss STEP=1000

I'm gonna close this PR and create a cleaner one with only the required changes.
one of them for doing math in same dtype as buffer type : https://github.com/tinygrad/tinygrad/pull/1545
after that's merged, then another PR based on this branch


Proposal : unsubscribe all message & conversation event

Description:
Building upon the insights gained from issue #187, this pull request introduces a refined approach to proper unsubscription from the methods returned by stream and streamAllMessages. Simultaneously, it recommends the removal of the static methods cancelStream() and cancelStreamAllMessages().
This adjustment serves to eliminate redundant listeners and prevent the occurrence of duplicated events.

iOS
Android

I'll go ahead and close this one, as issues with cancelStream functions was addressed in a PR here: https://github.com/xmtp/xmtp-react-native/pull/290


Add unit tests for useRecordingContext

Summary
Related to #264. Adds test for useRecordingContext.
Implementation details
Adds unit tests.
How to validate this change
If the test looks like it makes sense and it is passing CI no further testing needed.

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.