[hi] [new term] DevSecOps for Hindi

Please describe why this term needs to be added
What this term is about? (briefly)

DevSecOps stands for development, security, and operations. It's an approach to culture, automation, and platform design that integrates security as a shared responsibility throughout the entire IT lifecycle

Why this term needs to be added? (briefly)

This term to be Entered in Hindi Language because I don't find it in hindi.

Languages that use this term? (briefly)

@SahityaGupta25 We can assign you one term at a time, so please choose the term that you want to translate for this time, between DevSecOps and Microservices. 😊

DevSecOps ready & in few hours I will merge it.

Closing this for #1183


Remove unnecessary, and broken, inspect

What do you mean with "broken" here? But I'm all for removing this 👍

Broken in the sense that it generates an error, previously it was a PID but now it's a tuple (:gproc) and that IO.inspect/1 doesn't like it.
See: https://sentry.io/organizations/dazzle-rocks/issues/3167013841/?project=6257667&referrer=slack


[engflowapis] Test with 8.x

Hello @TheGrizzlyDev, modules you maintain (engflowapis) have been updated in this PR. Please review the changes.


doc: fix misspellings in Kconfig files

Fix misspellings in Kconfig files missed during regular reviews.
Signed-off-by: David B. Kinder<EMAIL_ADDRESS>

This needs the fix in #20179 to pass CI.


(Dropdown list) Programming languages with alphabet "Z"

Many projects need to show a list of programming languages as a dropdown list in their application. Hence the idea. Can someone help me finish the alphabet Z in A-Z-dropdown.html?
Here is the list from which I have referred to the list of programming languages
https://en.wikipedia.org/wiki/List_of_programming_languages

Hello @chilarai !! Can this issue be assigned to me? I want to contribute in this repo!

Thank you for accepting!

dropdown of z is not yet complete i want to work on it

Closed with #124


Wind parameters - configurable hair physics

We can configure wind parameters in scene file with:
{
"type": "application/windsettings",
"content": {
"forceFactor": 1.0,
"direction": [0.1, 0, 0.01],
"gravity": [0, -0.2, 0]
}
},
forceFactor is wind force
direction is amount of variance in x,y,z direction
gravity is fixed amount of gravity added to randomized direction
Related to issue:
https://github.com/webaverse/app/issues/1598
PR for webaverse/metaversefile is here:
https://github.com/webaverse/metaversefile/pull/39
Previous PR is deleted because it is outdated.
Steps for testing:
Add configuration param (described at the begging) to any .scn file.
Observe players hair
Equip another avatar, and observe his/hers hair
Change direction,gravity and forceFactor to see is there any change in behaviour

https://user-images.githubusercontent.com/4487857/144086763-820e7f44-e143-45a2-9654-ac037772b958.mp4

Device: Mac m1
The PR is working fine with Hairs. I have attached some videos to see. Also I tested it by changing parameters inside the above provided code too.
https://user-images.githubusercontent.com/35926530/144288890-9104dbf8-5b4d-4d89-978d-dc3d586ac14b.mp4
https://user-images.githubusercontent.com/35926530/144288962-3cdaf85d-3fb0-41a1-85e8-7ca8587a8bc9.mp4
https://user-images.githubusercontent.com/35926530/144288990-03101a76-9218-4faa-b309-8c82e91407ad.mp4
-Changed Parameters:
https://user-images.githubusercontent.com/35926530/144289313-35b2c13f-e1ea-49cc-b60c-12e9bebea488.mp4
https://user-images.githubusercontent.com/35926530/144289292-e1a79b6f-9171-4f49-825c-94ed8d3eb5c2.mp4
It works fine and can be merged.

Shipped in #3029


Unchain into multiple statements for TYPES

I'd like to see this rule extended to work also for TYPES. Ideally we should unchain these just like constants, variables, methods, etc.
Before:
TYPES: BEGIN OF type1,
         field1 TYPE data,
       END OF type1,
       type2 TYPE STANDARD TABLE OF type1.
       BEGIN OF type3,
         field3 TYPE data,
       END OF type3.
       type3 TYPE STANDARD TABLE OF type3,

After:
TYPES:
  BEGIN OF type1,
    field1 TYPE data,
  END OF type1.
TYPES type2 TYPE STANDARD TABLE OF type1.
TYPES:
  BEGIN OF type3,
    field3 TYPE data,
  END OF type3.
TYPES type3 TYPE STANDARD TABLE OF type3.

Hi Josh,
yes, that absolutely makes sense, and guess which comment I found inside the ChainRule code:
   // TODO: chains that just *contain* a BEGIN OF ... END OF section may nevertheless be partly unchained ...
   if (command.getFirstToken().matchesOnSiblings(true, TokenSearch.ASTERISK, "BEGIN OF"))
      return false;

So, currently, the rule skips any TYPES command that contains BEGIN OF anywhere, but it would be nice to unchain those, while keeping BEGIN OF ...
Kind regards,
Jörg-Michael

Hi,
I must admit I prefer chaining structure and table declaration. The finest result would be to have an option for the following result
TYPES:  BEGIN OF ty_type1,
          field1 TYPE data,
        END OF ty_type1,
        tty_type1 TYPE STANDARD TABLE OF ty_type1.

TYPES:  BEGIN OF ty_type2,
          field3 TYPE data,
        END OF ty_type2,
        tty_type2 TYPE STANDARD TABLE OF ty_type2.

but I agree it complicates a bit the rule.

Hi Josh,
thanks for bringing this up! With the next release, "Unchain into multiple statements" will now also work on TYPES chains that contain BEGIN OF … END OF definitions, if they are not interrupted by an INCLUDE (sorry, that case would really complicate things too much, but I think most cases are simple cases):

@AlexandreHT: Nice point! For this, I added the following option, which is activated by default:

With that, you get:

Kind regards,
Jörg-Michael

Hi Josh,
thanks for pointing this out – the enhancement (as described above) is now available in version 1.11.0 which was just released!
Kind regards,
Jörg-Michael


refactor: optimize AccountsTable component with useMemo and limit query end value

TL;DR
Optimized the Accounts Table component by adding useMemo hooks to calculate total accounts and limit the end value of queries. Adjusted the logic to ensure safe conversion of total accounts to a number type.
What changed?

Added useMemo for calculating totalAccountsNum and maxQueryEndValue.
Adjusted the accountsQuery to use maxQueryEndValue for its end parameter.
Simplified the total pages calculation.

How to test?

Navigate to the Accounts tab.
Ensure the total number of accounts loads correctly.
Check that pagination works as expected, especially when navigating to the last page.

Why make this change?
This change improves the performance and reliability of the Accounts Table component by ensuring that calculations and query parameters are optimized and accurate.

#2670  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


What is the method to remove the actions dropdown using this binding.

Removing the 3 dot actions menu is a giga-irritating odyssey.   Please advise.

This library only builds the spec. How it is rendered is completely up to how you load the spec in JavaScript. Here is an example: https://stackoverflow.com/questions/63715640/how-to-hide-the-three-dot-dropdown-menu-on-a-vega-chart

Cheers,   That helped, thank you!


d3.extentDiverging?

It’d be nice to have a variant of d3.extent that returns a three-element array with zero in the middle for use with d3.scaleDiverging.
function extentDiverging() {
  const [x0, x1] = extent.apply(this, arguments);
  return [Math.min(0, x0), 0, Math.max(0, x1)];
}

It was a bit odd that the pivot for extentDiverging would be 0, while it is 0.5 for the default domain of scaleDiverging.
Also, this might be served better by a more intelligent scaleDiverging.domain based on domain.length:
ie d3.scaleDiverging().domain([x0, x1], pivot=0) would be similar to .domain([max(pivot,x0), pivot, min(pivot,x1)])
see https://github.com/d3/d3-scale/pull/215 for a proposal

Not planning on doing this.


Discord link doesn't work

Hello, the Discord link is down, can you update it ?

You're sure? https://discord.gg/qTq92FQzKb seems to work.

Oh, it's work when you have the discord app already launched.
Thanks

👍


Build fails for Rune v0.7.0 on Mac Big Sur

cargo build on master  fails with
   Compiling tempfile v3.2.0
error: failed to run custom build command for `wasm3-sys v0.1.2`

Caused by:
  process didn't exit successfully: `/Users/kartikthakore/Documents/Hammer/Rune/rune/target/debug/build/wasm3-sys-e6b1b74c65417786/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'Unable to generate bindings: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /Users/kartikthakore/.cargo/registry/src/github.com-1ecc6299db9ec823/wasm3-sys-0.1.2/build.rs:78:35
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...```

Duplicate of #283 and #293.
You need to cargo install bindgen if you want to install rune from source. See the docs for the full list of build dependencies.


Since upgrading to v5, getting warning "export 'AngularFireObject' was not found in 'angularfire2/database'"

Version info

Angular: 4.4.6
Firebase: 4.6.0
AngularFire: 5.0.0-rc.3
Other (e.g. Ionic/Cordova, Node, browser, operating system):
** Errors in the JavaScript console **
** Output from firebase.database().enableLogging(true); **
** Screenshots **

Expected behavior
I should be able to upgrade to AngularFire2v5 without getting warnings in my console.

Actual behavior
I get warnings in my angular-cli build. The warning appears each time I save a file. Would to get rid of it.

AngularFire 5.0 is a refactor of the AngularFireDatabase module. It removes theFirebaseObjectObservable
you should change from FirebaseObjectObservable  to AngularFireObject.
onDisconnect error answer here replied

I read the upgrade docs, and followed them. I did it twice, before submitting this issue. I have swapped out all the things it says to, and am getting this random warning in my console. I did remove all references to FirebaseObjectObservable. In the screenshot of the log, you can see that the error is referencing AngularFireObject, not FirebaseObjectObservable.

I am using AngularFireObject, have a look at objRef in remove() at
https://stackblitz.com/edit/angular-iqq9xo?file=app%2Fnote.service.ts

Hey @aaronfrost! Can you check your node_modules/angularfire2/package.json and see what the version number is? Sometimes npm lies about version it installs.

I checked this last night before I submitted the feedback.

Had the same problem, solved itself by restarting Visual Studio Code.


Add .github CI scripts

Missing release cutting, validating release, scorecard, build, codeql. Copy from Rekor

Codecov will require setup, asking about it now
Setting up Scorecard


Vaillant server problem?

HA OS Core: 2021.12.08
Home Assistant OS 7.1
Multimatic: 1.12.1
Today between 16:39 and 17:04 I have no data for many sensors like sensor.domestichotwatertanktemperature, sensor.flowtemperaturesensor and others.
At 17:02 an automation to set the temperature in 2 rooms run, but the temperature wasn't changed.
Around 17:30 I run the automation manually and it worked.
My log shows:
This error originated from a custom integration.
Logger: custom_components.multimatic.coordinator
Source: custom_components/multimatic/coordinator.py:104
Integration: Multimatic (documentation, issues)
First occurred: 4:39:32 PM (12 occurrences)
Last logged: 5:02:05 PM
Unexpected error fetching multimatic_rooms data: Cannot get token at https://smart.vaillant.com/mobile/api/v4/account/authentication/v1/token/new, status: 503, response: Service Unavailable,payload: None
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
return await self.update_method()
File "/config/custom_components/multimatic/coordinator.py", line 516, in _fetch_data_if_needed
return await self._fetch_data()
File "/config/custom_components/multimatic/coordinator.py", line 509, in _fetch_data
return await getattr(self.api, self._method)()
File "/config/custom_components/multimatic/coordinator.py", line 104, in get_rooms
return await self._manager.get_rooms()
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 43, in wrapper
return await func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 336, in get_rooms
rooms = await self._call_api(urls.rooms, schema=schemas.ROOM_LIST)
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 84, in wrapper
raise ex
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 80, in wrapper
return await func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 844, in _call_api
await self._ensure_ready()
File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 878, in _ensure_ready
await self._connector.login()
File "/usr/local/lib/python3.9/site-packages/pymultimatic/api/connector.py", line 66, in login
token = await self._token()
File "/usr/local/lib/python3.9/site-packages/pymultimatic/api/connector.py", line 109, in _token
raise ApiError(
pymultimatic.api.error.ApiError: Cannot get token at https://smart.vaillant.com/mobile/api/v4/account/authentication/v1/token/new, status: 503, response: Service Unavailable,payload: None
I think the Vaillant server was offline at that time. Is that a correct conclusion?

Yes same here. Status 503 means there is something wrong at server side. If you try the app, you will have an error message

I was not at home, so I couldn't try at that time but was wondering why the automation hadn't worked...
Thanks.


llnl rzhound + xquartz garbled windows

Describe the bug
From LLNL user:
Various issues when cloning a window,  2nd or further windows are blank or turn black, or the graphics are garbled in them.
Commands issued for one window are executed in another window.
Further details:
Happens from two different Mac (a 2023 Mac Studio and a 2023 MacBook Pro).
Does not happen when connecting to rzhound from RZVNC.
Happens in ViSit serial mode or parallel ('sxterm') mode.
These problems were not occurring with rztopaz.
Current Mac is OS 14.6.1.
Rzhound ViSit version is 3.4.1.
Reinstalling XQuartz on Mac did not fix the issue.
I (Cyrus) see similar things when using my laptop screen, but not when using an external monitor.

may be related to #19544

Ok, so I played around with rzhound displaying back to my macOS system for a while. Please see the video I recorded of all the issues I ran into in /usr/workspace/visit/bug_data/VisIt_341_rzhound_issues.mp4. There are many subtle issues.

FYI...I realize that when I updated XQuartz to 2.8.5 from 2.7.11 (2016'ish), I did not have indirect glx enabled. I had to fix that with
 defaults write org.xquartz.X11 enable_iglx -bool true

But, I made the recording above before doig that.

I expirimented with SR mode and got mostly same behavior. There was maybe slightly less issues but all issues still occurred eventually. I even got the viewer to core dump. I recorded log data but couldn't get a useful stack dump.
Handling AddPlotRPC RPC.
ViewerPlotList::GetDefaultSILRestriction(): Trying to find SIL restriction for key: localhost:/usr/gapps/visit/data/globe.silo:0
Found key. Copying SIL restriction.
Setting SIL restriction's top set to 0
signalhandler_core: SIGSEGV! (Segmentation fault)

I managed to get a kind of stack trace from logru...
Loguru caught a signal: SIGABRT
Stack trace:
27            0x40217e /g/g11/miller86/visit/visit/3.4RC/build/exe/engine_ser() [0x40217e]
26      0x15554479b7e5 __libc_start_main + 229
25            0x40261d /g/g11/miller86/visit/visit/3.4RC/build/exe/engine_ser() [0x40261d]
24            0x4024da /g/g11/miller86/visit/visit/3.4RC/build/exe/engine_ser() [0x4024da]
23      0x1555554afb91 Engine::EventLoop() + 515
22      0x1555554afd56 Engine::ProcessInput() + 92
21      0x15554da34436 Xfer::Process() + 544
20      0x15554d8a4ed4 AttributeSubject::Notify() + 28
19      0x15554d9f727f Subject::Notify() + 163
18      0x1555554b9615 EngineRPCExecutor<SetWinAnnotAttsRPC>::Update(Subject*) + 53
17      0x1555554a5d4f EngineRPCExecutor<SetWinAnnotAttsRPC>::Execute(SetWinAnnotAttsRPC*) + 305
16      0x1555554cdbbf NetworkManager::SetWindowAttributes(WindowAttributes const&, std::string const&, double const*, std::string const&, int) + 195
15      0x1555554ce113 NetworkManager::SetWindowAttributes(EngineVisWinInfo&, WindowAttributes const&, std::string const&, double const*, std::string const&) + 1361
14      0x15554fcf2b58 avtColorTables::SetColorTables(ColorTableAttributes const&) + 54
13      0x15554d8d0c81 ColorTableAttributes::operator=(ColorTableAttributes const&) + 51
12      0x15554d8cfd36 ColorTableAttributes::Copy(ColorTableAttributes const&) + 206
11      0x15554d8c8c12 ColorControlPointList::~ColorControlPointList() + 24
10      0x15554d8c8bd2 ColorControlPointList::~ColorControlPointList() + 188
9       0x15555548536f std::vector<std::string>::~vector() + 65
8       0x1555554853f4 std::_Vector_base<std::string>::~_Vector_base() + 62
7       0x15555548951a std::_Vector_base<std::string>::_M_deallocate(std::string*, unsigned long) + 50
6       0x15555548c6a3 std::allocator_traits<std::allocator<std::string> >::deallocate(std::allocator<std::string>&, std::string*, unsigned long) + 43
5       0x155555492c58 __gnu_cxx::new_allocator<std::string>::deallocate(std::string*, unsigned long) + 46
4       0x1555447f95b4 /lib64/libc.so.6(+0x985b4) [0x1555447f95b4]
3       0x1555447f7a2c /lib64/libc.so.6(+0x96a2c) [0x1555447f7a2c]
2       0x1555447f0727 /lib64/libc.so.6(+0x8f727) [0x1555447f0727]
1       0x155544782e65 abort + 295
0       0x1555447af52f gsignal + 271
2024-10-02 14:52:30.519 ( 428.021s) [main thread     ]                       :0     FATL| Signal: SIGABRT

I tried with scalable rendering. While there was a modest reduction in issues...all issues eventually did happen. In fact, I even got VisIt to core a few times...
Handling AddPlotRPC RPC.
ViewerPlotList::GetDefaultSILRestriction(): Trying to find SIL restriction for key: localhost:/usr/gapps/visit/data/globe.silo:0
Found key. Copying SIL restriction.
Setting SIL restriction's top set to 0
signalhandler_core: SIGSEGV! (Segmentation fault)


Ghost message when accidentally hitting return

when user accidentally hits return without any message content ghost message appears

This is already fixed in 5e155380f4dbfbf17ea836e31308d076ea0b403f, but not yet pushed up to the demo site.


Add FIDO support

This PR adds FIDO report descriptors.
The descriptors have been tested on live hardware against the CTAP2 testbench and no compliance issues were found.

Hi @bunnie. Thanks for the contribution.
To include the FidoInterface in the library I'd want to have a stronger encapsulation of the read and write report formats than just a [u8; 64]. From a quick scan of the FIDO U2F HID Protocol Spec, there are two types of packet with a fixed field layout, initialization packets and continuation packets. This looks like it would naturally map onto a rust enum. Even better would be the ability to read and write U2FHID commands with the mapping onto init and continuation packets handled by the interface.
I'd be happy to have this on a development branch and merge this into main once the higher level functionality is added or  keep the pull request open until the interface supports higher level operations.
I'd be interested in work with you on this, but I'm unlikely to find the time until later on in the year.

...or you could rename this to a RawFidoInterface taking a [u8;64] for read and write report, leaving the name FidoInterface to be implemented later with higher level protocol support.

Sure thing! I just did that.
The reason we went with opaque packets is because that's what OpenSK was expecting. I also originally had more structure in the packets -- there's two forms that packets can take, initialization or continuation, and it depends on the value of a high bit at offset 4 -- but since OpenSK already had code to handle this, it was more efficient to just shuttle raw packets to and from their stack.
But I agree not all implementations will take this form so making space for both representations might be a good option?

@bunnie - available in 0.2.1 - https://crates.io/crates/usbd-human-interface-device/0.2.1


fix(routing): support parsing URLs with up to 100 refinements

Description
Backport of #3671 for InstantSearch v2.
Original description:

An issue raised by a customer is that when selecting more than 20 values with the routing option activated, the data structure returned by the parseURL function changes.
qs by default converts arrays with more than 20 items to an object. We want to avoid this because the data structure manipulated can therefore vary.
Setting the limit to 100 seems a good number because the engine's default is 100. It can go up to 1000 but it is very unlikely to select more than 100 items in the UI.
Reference

qs doc: https://github.com/ljharb/qs#parsing-arrays
Algolia maxValuesPerFacet doc: https://www.algolia.com/doc/api-reference/api-parameters/maxValuesPerFacet/
Original customer issue: https://algolia.slack.com/archives/C2XP6HBKQ/p1553005092109200

@Haroenv Since this is an easy fix and that this one was implemented already, I guess it's fine?


Launch refactor

@UNiQ10 refactored your pull request:

No more sleeps between adding agents - instead the Trainer waits until they respond to (look).
Agent now broadcasts when it gets and incoming connection and uses non-blocking poll() to listen for incoming connections.
Trainer waits to start game until all agents have gotten connections. This fixes the issues with the --no-sync flag.
Still Terminates un-necessary agents

Please take a look and let me know if I've missed anything.

On running with command:
./HFO --offense-npcs 1 --defense-npcs 0
The trainer reports that the some episodes end with defense capture.
I had faced this problem earlier. When we terminate an npc it internally send the message "(bye)" to the server and then server clears the npc from the world. If the server doesn't see this message (usually because lots of agents and npcs are trying to communicate with at the same time) the npc remains as a ghost.

Good point! The defense captured goes away if --no-sync is added, so I
think it's an issue not with players ghosts, but with the Trainer not
getting too little information (since the game runs so quickly) or bad
information from the server.
On Wed, Oct 14, 2015 at 3:56 PM, UNiQ10<EMAIL_ADDRESS>wrote:

On running with command:
./HFO --offense-npcs 1 --defense-npcs 0
The trainer reports that the some episodes end with defense capture.
I had faced this problem earlier. When we terminate an npc it internally
send the message "(bye)" to the server and then server clears the npc from
the world. If the server doesn't see this message (usually because lots of
agents and npcs are trying to communicate with at the same time) the npc
remains as a ghost.
—
Reply to this email directly or view it on GitHub
https://github.com/mhauskn/HFO/pull/12#issuecomment-148197857.

Actually, not it is happening even with no-sync enabled. How did you fix this problem?

Using a new coach message to disconnect players in addition to kill/terminating their processes. This sidesteps the problem of some players not saying 'bye' when killed.


esds-build Getting Started [Doc]

Acceptance Criteria

As a build tool user I need to know how to override various parts of the build to tailor it to fit my Product.

Duplicates #13


Typo reponse in yes-no answering instructions

https://github.com/expectedparrot/edsl/blob/f7b23f66636af211f1b16080f8af7c2930b5e822/edsl/questions/templates/yes_no/answering_instructions.jinja#L2-L5
Should be respond then response.
I think this explains the other instances of reponse in the repo: https://github.com/search?q=repo%3Aexpectedparrot%2Fedsl reponse&type=code

Thank you!


Feedback Plugin: 401 Unauthorized error

Describe the bug
We are implementing the feedback on our backstage instance, but we are getting a 401 Unauthorized when the front end plugin is making API calls to the backend. I think this is happening because the API calls from the front end are not using backstage's fetchApi and is not including any auth headers.
Expected Behavior
The frontend should not have issues making API calls to the backend even if backend auth is enabled.
What are the steps to reproduce this bug?

Enable backend auth on backstage
Setup feedback plugin's backend according to the docs
Setup feedback plugin's frontend according to the docs
Run backstage and try to provide feedback through the plugin

Versions of software used and environment
@janus-idp/backstage-plugin-feedback version 1.2.5
@janus-idp/backstage-plugin-feedback version 1.1.6
Backstage version 1.26.5

I am working on fix, that will support backstage fetch API, which will automatically add auth headers to fetch calls

I am working on fix, that will support backstage fetch API, which will automatically add auth headers to fetch calls

Thank you very much!


chore: add kitty version 0.32.2 to test matrix

closes #193

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


Services do not always start when the Docker Image starts up

When starting the image, sometimes services do not start.
This seems to apply - sporadically - to both Airflow and Superset. Either the webserver and/or the Airflow scheduler.
Work around is to run one or more of the commands from startup.sh manually. Specifically:
meltano invoke airflow scheduler &
meltano invoke airflow webserver &
meltano invoke superset:ui &

I am not currently aware how to solve this.


Settings ui for switching the scheme based on the app's theme

Description of the new feature/enhancement
Add settings ui for config https://github.com/microsoft/terminal/pull/14064
Proposed technical implementation details (optional)

https://github.com/microsoft/terminal/issues/14475


API Breaking Update needed: Rename setAllBlockLFPs

@keckler's comment about setAllBlockLFPs:

I know that it would be an API-breaking change, but the name of this method no longer appears to represent well what the method does. It is no longer focused solely on LFPs.
Looking around our codebase, it appears that a few of our plugins call to it... :-/

@jhader's reponse:
    I would prefer to keep this the same for now so I don't have to update more stuff that is dependent on it and possibly risk downstream impacts on others. I can make an issue.

Originally posted by @jakehader in https://github.com/terrapower/armi/pull/1022#discussion_r1055032783

If this needs to happen, cool.  There are 4 downstream repositories that I see will need to be updated.   But they are one-line updates.
I would prefer if this change were it's own ARMI PR though, and not mixed into one of our current, larger PRs.

I'm not sure this needs to happen unless someone gets a couple minutes of down time in the future. The name change is just for semantics.

This isn't needed because #1067 refactored this code.


Small refactoring to improve readability and reduce method complexity

Small method extraction to reduce complexity and improve readability of the assign method.
Private methods were created for:

Get the assignment suppliers based on the subscriptions (decoding of subscriptions info is also done at this point, where it is used)
Calculate the number of partitions for internal topic
Add tasks to state change log topic subscribers

These methods are being called inside the assign method.

The failures are somewhat non-deterministic and seem to be unrelated with the change, can someone please double check?
Btw, in general all builds running against ubuntu-5 jenkins instance are failing due to timeout. There's a open infra jira issue to sort this out.

Hello @picadoh thanks for the patch. Could you take a look at https://github.com/apache/kafka/pull/2012 and see if it covers your concerns?

yep :) thanks @guozhangwang, great stuff.


Take the pixelRatio into account when computing the gutter

Fixes #5272

An additional test that verifies the correct gutter size for a tile of known size and pixel ratio would be great.

Hi, I've tested your modifications with this conditions:
Tile size: 350
Pixelratio: 2.5
gutter: 150
I get a request to mapserver with this dimensions:
&WIDTH=1625&HEIGHT=1625
(350+150*2)*2.5 = 1625
This means it is working perfectly!!! Thanks a lot

Actually I was hoping for a unit test.

Sorry, this is the first issue I post on github.
Of course, I am aware of the concept of unit test, but can you extend what you mean by "unit test" in this context? I will be pleased to make any test required.

@agustincaballero My comment was addressed to @fredj, because he created the pull request.

I've planned to add unit tests (probably next week)

Rendering tests added, thanks for any review (ping @ahocevar )

Thanks @fredj. Looks great, please merge.

Thanks for the review


Github pages URL gives a 404 error

Am getting a 404 on my github pages entry despite (I think) following all the necessary steps, any ideas?  url is https://tomkeddie.github.io/tinytapeout-2022-2a/ settings are shown below, deploy reports success.  Thanks.

Ok, I think I've found the problem.  I downloaded the github-pages artifact from the gds action.  Its contents look like
(venv) tom@x570:~/git/TomKeddie/tinytapeout-2022-2a/tmp$ tar xvf artifact.tar
./
./gds_render.svg
./viewer/
./viewer/LICENSE
./viewer/tinytapeout.gds.gltf
./viewer/README.md
./viewer/tinytapeout.html
(venv) tom@x570:~/git/TomKeddie/tinytapeout-2022-2a/tmp$

There's no README.md in the parent directory, I think that's why we're getting a 404.  If I change the URL to https://tomkeddie.github.io/tinytapeout-2022-2a/gds_render.svg it works fine.  I'm not sure why I can't see the README in the viewer directory at https://tomkeddie.github.io/tinytapeout-2022-2a/viewer/ but browsing to https://tomkeddie.github.io/tinytapeout-2022-2a/viewer/tinytapeout.html works.
Perhaps this is old news?  Seems like it would be easiest to add a README to the parent folder with a redirect (as per https://dev.to/steveblue/setup-a-redirect-on-github-pages-1ok7) to the viewer html page?


Users/omeshp/package task changes

Fix options url used for quering.
Rename Task to DownloadPackage.

@omeshp,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Trying to install loops for Garageband, loopdown says I'm missing flags

Trying to install any/all loops for garageband, using
"loopdown -a garageband -m -o -i"
And just getting back "loopdown: error: argument -i/--install: not allowed without: -m/--mandatory and/or -o/--optional"
I've tried shifting arguments around, adding/eliminating/etc and can't seem to get install flag to work.

Nevermind, looks like https://github.com/carlashley/loopdown/releases/tag/v1.0.20230726 fixes this issue.


🚸 TinaCMS | rich text editor - Obscured Toolbar Items in CMS Window

Pain
It may appear Tina is missing a few rich-text options (e.g. the embed) as they can be obscured in the thin TinaCMS editor, and the toolbar isn't possible to scroll on.
My late afternoon brain came to the conclusion that those options just didn't exist for a page I was editing.
I also reckon I'm not the first victim of this one. This is on Firefox / Mac.
I think we could improve the UX.
Additionally, to note, if you click on a half-obscured toolbar item the hidden items will be opened in a floating menu (but nothing in the UI really indicates this).
Screenshots

Figure 1 – missing toolbar items??

Figure 2 – revealed on a wider screen size

Figure 3 – clicking a half-obscured toolbar item to reveal the hidden toolbar items
Steps to reproduce
Open a CMS instance where a rich-text field is being edited.
Resize the subwindow.
System Info
System:
OS: macOS 13.6.1
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 60.18 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm
pnpm: 9.6.0 - /usr/local/bin/pnpm
Browsers:
Safari: 16.6
Validations

[x] Follow our Code of Conduct
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug.

@wicksipedia @JackDevAU
We are facing the same issue on the SSW website: the access to more rich text options is unclear
Screenshot

Figure: More rich text options are hidden

Hey all, just tested this in<EMAIL_ADDRESS>and wasn't able to reproduce the issue (even tried Firefox on MacOS).
Can you install the latest version and retry please.

I've just updated to 2.2.5 and am encountering the same problem – looks like it works great with the vertical ellipses but I wonder why they're not showing up for me 🤔
Could it be that something else in the SSW website / tina.io is interfering with it?

✅ Done
PR - https://github.com/tinacms/tinacms/pull/5004


add rabbit chain

Make sure these boxes are checked! 📦✅

[x] You ran ./run_tests.sh
[x] You ran pre-commit run -a
[x] If you want to add your network to setup_service.py, provide a link to your
safe-deployments PR and check network name
exists in safe-eth-py

What was wrong? 👾
Closes #
How was it fixed? 🎯

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

Let us know when https://github.com/safe-global/safe-deployments/pull/123 is merged

https://github.com/safe-global/safe-deployments/pull/123 is merged

please merge https://github.com/safe-global/safe-transaction-service/pull/1109 .
I will appreciate .

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
14 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 87.668%

Files with Coverage Reduction
New Missed Lines
%

safe_transaction_service/tokens/clients/coinmarketcap_client.py
14
47.17%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5950

Relevant Lines:
6787

💛  - Coveralls


Don't throw, run all error and finally hooks

We need to implement the changes described here: https://github.com/open-feature/spec/pull/90

Done with https://github.com/open-feature/node-sdk/pull/25


doc/README: adding some specific instructions for Windows users

r? @krishnaIndia
(maidsafe_highfive has picked a reviewer for you, use r? to override)


some enhancements

add customized logger middleware into options(e.g log4js other than
koa2-logger)
add koa router sensitive flag into options
add customized exceptionWrapper into options

Nice additions @yrong :thumbsup:


Remove dependency on ceed/hash.h for newer libCEED versions

Resolves #3785.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


[tests] Update Dockerfile to use cuda 12.2

An attempt to fix the current example tests being skipped - according to the logs:
./../../../opt/conda/envs/peft/lib/python3.8/site-packages/torch/cuda/__init__.py:138
  /opt/conda/envs/peft/lib/python3.8/site-packages/torch/cuda/__init__.py:138: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 11080). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org/ to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:108.)
    return torch._C._cuda_getDeviceCount() > 0

../../../../opt/conda/envs/peft/lib/python3.8/site-packages/bitsandbytes/cextension.py:34
  /opt/conda/envs/peft/lib/python3.8/site-packages/bitsandbytes/cextension.py:34: UserWarning: The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
    warn("The installed version of bitsandbytes was compiled without GPU support. "

Will investigate more and report back here
cc @BenjaminBossan

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

After some investigation, that seems to be indeed the culprit, I think torch 2.1 somehow fails with old CUDA versions leading to torch.cuda.is_available() to be set to False. I also had to add NVIDIA_DISABLE_REQUIRE: "1" (ref: https://github.com/NVIDIA/nvidia-docker/issues/1409#issuecomment-778089784) so that the docker image can run without the check of nvidia versions


SAK-47775: Direct request failure: IllegalArgumentException:Invalid reference (/assignment/my)

SAK-47775: Direct request failure: IllegalArgumentException:Invalid reference (/assignment/my)

It would be ideal if a test could added to:
org.sakaiproject.entitybroker.rest.EntityHandlerImplTest
to check the logic of the changes in this issue.


Resolve dynamic variables while converting to OAS

Postman uses the faker library to generate sample data, including random names, addresses, email addresses, and much more. These are present as dynamic variables in the Postman collection. However, when converting the collection containing these variables, it is necessary to resolve them accurately.
Presently, the conversion process converts {{$randomInt}} into a string i.e. "{{$randomInt}}" , instead of a random number like 802, which is the expected behavior.
Here's the list of supported dynamic variables.

We can see if this dependency will work for faker-like functionality: https://crates.io/crates/fake


Bazel binary path (sometimes?) gets reset after version upgrade

Hi,
Developers internally report that after they upgrade a plugin version their build doesn't work because the binary path gets reset to bazel instead of /usr/local/bin/bazel.
I took a look in BlazeUserSettings.java and saw that for blaze you have a better default than bazel.
Can we have the same default for bazel binary path? I can send the PR if needed

For blaze we know exactly where the binary will be, because we only have to worry about internal corp machines and development environments. For bazel, it's up to the user where they install it. We came to the conclusion that 'bazel' covers more use cases than '/usr/local/bin/bazel', and is relatively intuitive. Happy to reconsider if that's not actually the case.
That said, it shouldn't be getting reset unless you're somehow wiping the user settings along with updating the plugin -- the base plugin itself won't be doing that.

Using Bazel from the path is a better default. Some systems have /usr/bin/bazel, /usr/local/bin/bazel, and it works very differently on Windows and NixOS / nixpkgs-based systems.
I also haven't encountered a settings reset for the PATH after an upgrade.

👍 Fair enough. I'll try to see if it's something we do that messes up the bazel binary path on upgrade. Thanks!


MNF DOUBLE HEADER

IN CONFIG SHEETS, DOES MNFDOUBLE MEAN DOUBLE HEADER OR MNF WORTH DOUBLE POINTS?

I'm amused by the full caps too.
@chammy510 the MNF Double means that it counts for 2X the value for the MNF game(s). If you have the bonus feature enabled, in addition to the MNF Double feature, you'll see a 2 in the bottom row of the weekly sheet.

@NadlesKVs my jobs require me to type in all cap for everything. im used to having my cap lock on lol

thanks for the amazing sheets and quick response. sending some coffee for the support

Thanks for the support! I really appreciate it. Hopefully it continues to
serve you well.
On Mon, Oct 21, 2024 at 12:30 PM chammy510 @.***> wrote:

thanks for the amazing sheets and quick response. sending some coffee for
the support
—
Reply to this email directly, view it on GitHub
https://github.com/boilermaker-ben/Google-Sheets-NFL-Pick-Ems-and-Survivor-Pool/issues/19#issuecomment-2427160387,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDWGY74ONJ3D57CRUJLPHTZ4UTY5AVCNFSM6AAAAABP7YOJJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGE3DAMZYG4
.
You are receiving this because you commented.Message ID:
<boilermaker-ben/Google-Sheets-NFL-Pick-Ems-and-Survivor-Pool/issues/19/2427160387
@github.com>


Cli Mode to add comments

Add a simple cli mode to add comments, this should not be that hard given it would just be some template literals like decode x and such and in langs like grain or assemblyscript for instance these get optimized away so size isnt really a worry.

I'm visualizing something along these lines.
Either through a config file or the cli, the user can define a debug (or verbose?) option which would generate comments that explain the resulting binary format and the version it was compiled with.
fass build Vec3.fass -o build/ --assemblyscript --debug
/** @fass v0.1.0
 * Generated AssemblyScript code from Vec3.fass
 *
 * quad = u8
 * x = f32
 * y = f32
 * z = f32
 * Binary format = [quad, x, y, z]
**/
export class Vec3 {
    quad!: Quadrant;
    x!: f32;
    y!: f32;
    z!: f32;
    public __FASS_SIZE: u32 = 13;
    @inline __FASS_SERIALIZE(output: ArrayBuffer, input: Vec3): void {
        store<u8>(changetype<usize>(output), input.quad, 0);
        store<f32>(changetype<usize>(output), input.x, 1);
        store<f32>(changetype<usize>(output), input.y, 5);
        store<f32>(changetype<usize>(output), input.z, 9);
    }
    @inline __FASS_DESERIALIZE(input: ArrayBuffer, output: Vec3): void {
        output.quad = load<u8>(changetype<usize>(input), 0);
        output.x = load<f32>(changetype<usize>(input), 1);
        output.y = load<f32>(changetype<usize>(input), 5);
        output.z = load<f32>(changetype<usize>(input), 9);
    }
}

export enum Quadrant {
    TL = 1,
    TR = 2,
    BL = 3,
    BR = 4
}

Pretty much maybe you support like an ```
/*

@description: Vector
*/

also instead of having the fass version on the binding put that in a comment at the top of the module.


GUVNOR-3070: Guided Decision Tables: Column Wizard - Edit mode

See https://github.com/kiegroup/drools-wb/pull/541

@paulovmr Could you please take a look?

This PR does not have any dependency with drools-wb PR. It can be merged right now. ;-)


Going fullscreen on an app makes other monitors go black

I'm running Aerospace on a 3 monitor set-up and whenever I go into fullscreen mode in an app like Chrome or Firefox, it goes into fullscreen mode correctly on the monitor that the app with the workspace is on, but it hides all other windows in the other 2 monitors leaving them just black.
Ideally the app would go fullscreen on the workspace it's on but the other monitors keep showing their apps. I'd like to be able to leave the app running in fullscreen mode and still be able to use my shortcuts to switch to other workspaces at least on the other monitors, but it would be brilliant if I could switch workspaces even on the monitor that the app is running fullscreen on.
Is this a bug or a feature request or PEBKAC?

Checklist

[x] I've searched for duplicates. My search queries were (please don't forget to search in closed issues too):

fullscreen

[x] I've read the documentation https://nikitabobko.github.io/AeroSpace/guide & https://nikitabobko.github.io/AeroSpace/commands
[x] I've searched in the documentation. My search queries were:

fullscreen

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

This is expected behavior since all monitors/desktops share one and the same MacOS space.

This is expected behavior since all monitors/desktops share one and the same MacOS space.

Yep, understand that. As I'm not familiar with the code, I wondered if this is just a limitation of Aerospace due to the nature of virtual workspaces or if there is any way around it.

I guess this limitation is covered in:
https://nikitabobko.github.io/AeroSpace/guide#a-note-on-displays-have-separate-spaces

Yes, it's a macos limitation https://nikitabobko.github.io/AeroSpace/guide#a-note-on-displays-have-separate-spaces
You can enable Displays have separate Spaces back, but there are possible drawbacks. See the table and choose


Sequelize

sql file is not same modle design
sql:
CREATE TABLE users(
id VARCHAR(255) PRIMARY KEY,
username VARCHAR(255) UNIQUE NULL,
password VARCHAR(100),
views INT DEFAULT 0,
gravatar VARCHAR(255) UNIQUE NULL,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP NOT NULL DEFAULT NOW() ON UPDATE NOW()
);
model:
id: {
type: DataTypes.UUID,
allowNull: false,
primaryKey: true,
defaultValue: DataTypes.UUIDV4,
},

Hi @AiPacino,
Yes, I know about this, the thing is that I have recently migrated to sequelize, so the sql files are redundant/outdated now.
I haven't updated the docs yet as I am currently working on some archtectural changes.
If you want to setup the project, then for the backend do not follow the documentation provided completely, and,

First setup your .env file as stated in the docs.
Then just create the database with whatever name you want to give it and update your .env accordingly
You don't need to create the tables just the database
After this is done just run npm start and the server will automatically create the required tables with the updated schemas.

After that, just have fun with the product 🎉

@AiPacino Checkout the updated SQL files, those are the correct ones


Replace redux div to json script

This change is

@JasonYCHuang why did you close this?

@justin808  I was going to merge this to my repository for travisCI test only, not for pull request.
This is just wrong operation, so I close this.


Get Auth System working.

Having an issue with the Auth system and users are not able to login.
No error messages are displayed either.

@ddmler - Can you take a look at my Auth.php and see if you can help?

Changed from Cookie to Session and script is now working!  :boom:

What did you change from Cookie to Session? I think I have a similar problem.

I went from using the Cookie helper file to using the Session helper file within \Helpers\Auth\Auth
https://github.com/davarravad/UserApplePie-v-2/blob/master/app/Helpers/Auth/Auth.php
I just replaced Cookie:: to Session:: throughout the file.
Here is my current test site:  http://testsite.userapplepie.com/
Username: demouser
Password: demopass
I am still trying to get the error messages to work.  But I can login and logout.

The thing with Session::,  a user has to sign back in each time they re-open the browser. The cookie will just be fine. This site , I used SMVC....www.afrolinked.com. But I had to hard code the cookie to last a life time.  In the project I am doing now, I want to use the Auth Addon which seems to be great. Just this weird cookie problem.

Good point.  I will see what I can come up with when I get a chance.  I have never used cookies before so it will be a good lesson for me.

The first time I login with a browser for the first time it works with cookie.  When I logout then try to login it does not work.  I think the cookie is not getting destroyed properly.  Looking into a solution.

Found it.  Repo has been updated with changes.

This has been fixed and looks to be working well.


Start module load function name from the last '/' in the path

This does seem right - I would have to check the history but I think this might have been using the dotted name previously and I missed this when changing to file paths.
However, I can not merge a change from what is effectively an anonymous account, so I will apply this fix myself unless you want to come back with a legitimate email address.


[Loc] removed one string for sql-migration

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28089

Relevant Lines:
62304

💛  - Coveralls


Error when running ionic build --prod

Ionic version:

[] 4.x
[x] 5.x
I'm submitting a ...

[x] bug report
[ ] feature request

Current behavior:
ionic build --prod throws an error An unhandled exception occurred: Maximum call stack size exceeded.
Works fine without the --prod flag.
Expected behavior:

Steps to reproduce:

Related code:

`
ionic build --prod
> ng run app:build:production
Generating ES5 bundles for differential loading...
An unhandled exception occurred: Maximum call stack size exceeded
See "/tmp/ng-6SoqBf/angular-errors.log" for further details.
[ERROR] An error occurred while running subprocess ng.

        ng run app:build:production exited with exit code 127.

        Re-running this command with the --verbose flag may provide more information.

Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 6.1.0 (/home/sachith/.nvm/versions/node/v12.16.1/lib/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.0.4
   @angular-devkit/build-angular : 0.803.25
   @angular-devkit/schematics    : 8.3.25
   @angular/cli                  : 8.3.25
   @ionic/angular-toolkit        : 2.2.0

Capacitor:

   Capacitor CLI   : 1.5.0
   @capacitor/core : 1.5.0

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   NodeJS : v12.16.1 (/home/sachith/.nvm/versions/node/v12.16.1/bin/node)
   npm    : 6.13.4
   OS     : Linux 5.3

Was able to run ionic build --prod successfully by changing  "target": "es2015" to "target": "es5" on tsconfig.json.
https://forum.ionicframework.com/t/ionic-cordova-build-get-stuck-at-generating-es5-bundles-for-differential-loading/180202/4
The default ionic project setting was "es2015" so please advise.

Thanks for the issue. Can you provide a repo with the code required to reproduce this issue?

It turns out that , one of my functions which has about 650 lines of "text.replace()" methods. causing ionic build --prod to throw this exception.
I was able to resolve it by writing the function in a different way or when I build it after changing the "target": "es2015" to "target": "es5" on tsconfig.json. (With the es5 method I'm not sure if it can cause issues when run on different devices)
It seems that this is an Angular issue rather than Ionic.

Thanks for the follow up. In that case, I am going to close this issue. If you later determine that this is an Ionic issue please feel free to open a new issue. Thanks! 🙂


chore: Allow the usage of the breaking-change trailer for changelog entries

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

Project coverage is 90.28%. Comparing base (c2efa95) to head (c4a2ebc).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #195   +/-   ##
=======================================
  Coverage   90.28%   90.28%
=======================================
  Files          34       34
  Lines        1905     1905
=======================================
  Hits         1720     1720
  Misses        185      185

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Delete array of keys in redis using node-redis

I have arrays of keys like ["aaa","bbb","ccc"] so I want to delete all these keys from redis using one command . I donot want to iterate using loop . I read about redis command DEL and on terminal redis-client it works but using nodejs it does not work
Redisclient.del(tokenKeys,function(err,count){
Logger.info("count is ",count)
Logger.error("err is ",err)
})
where tokenKeys=["aaa","bbb","ccc"] , this code is work if I send one key like tokenKeys="aaa"

client.del can take a variable number of arguments. You can use apply to convert your array into arguments (but you'll need to also push on your callback). It would look something like this:
var tokenKeys = ["aaa","bbb","ccc"];

tokenKeys.push(function(err,count){
Logger.info("count is ",count)
Logger.error("err is ",err)
});

Redisclient.del.apply(Redisclient,tokenKeys);

It's a bit weird, but it will get the job without iterating.

@abhaygarg This should work out of the box just as you wrote it. Could you provide more of your code? I guess the error is somewhere in your code. And what version do you use?
@stockholmux this is not the solution to the issue. Actually it is better to use the array notation right away instead of using arguments (they will be rewritten to an array internal).

yeah its working you can directly pass array in Redisclient.del(tokenKeys,function(err,count){
Logger.info("count is ",count)
Logger.error("err is ",err)
})
it delete fine you can pass array in Redisclient.del() it works fine

        app.redis.keys('key_*', (err, keys) => {
          keys.forEach(key => {
            app.redis.del(key)
          })
        })

@knoxcard FYI - Don't use KEYS - it's dangerous on large production system.


New cuts cannot be used if they don't have a name

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

#!python

ds = data.channel[11]
ds.cuts.cut(28, ds.p_pulse_rms[:]>3500)  # This does nothing
ds.cuts.cut(14, ds.p_pulse_rms[:]>3500)  # This applies the cut

The latter works because cuts 0-14 have names. This leaves us no way to use cuts 15-31.
#!python

In [122]: print data.boolean_cut_desc
Out[122]:
array([('pretrigger_rms', 1L), ('pretrigger_mean', 2L),
       ('pretrigger_mean_departure_from_median', 4L), ('peak_time_ms', 8L),
       ('rise_time_ms', 16L), ('postpeak_deriv', 32L),
       ('pulse_average', 64L), ('min_value', 128L),
       ('timestamp_sec', 256L), ('timestamp_diff_sec', 512L),
       ('peak_value', 1024L), ('energy', 2048L), ('timing', 4096L),
       ('p_filt_phase', 8192L), ('smart_cuts', 16384L), ('', 0L), ('', 0L),
       ('', 0L), ('', 0L), ('', 0L), ('', 0L), ('', 0L), ('', 0L),
       ('', 0L), ('', 0L), ('', 0L), ('', 0L), ('', 0L), ('', 0L),
       ('', 0L), ('', 0L), ('', 0L)],
      dtype=[('name', 'S64'), ('mask', '<u4')])

The problem appears to be all those 0L values as the 2nd member of the tuples. @oneilg can watch this.

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

As Young said, it is intended that you never use a cut number directly, instead always naming your cuts. The number syntax exists for backwards compatibility. It should not fail silently however.
This is mainly a documentation (mass documentation?? it could happen) issue.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Well, this is a reasonable design choice, but it breaks every existing script that does use a cut number (i.e., every special-purpose cut I have ever made).
So...apart from any so-called documentation, we need the use of a cut-by-number to fail with an explicitly raised error instead of silently just not cutting anything.

Original comment by Young Il Joe (Bitbucket: jojo978, GitHub: jojo978).

In order to use non-builtin cut, you need to register first.
It's reasonable to call that boolean cut field "pulse_rms", so you can register like this. Then you can use the name of this cut field.
#!python

data.register_boolean_cut_fields("pulse_rms")
ds.cuts.cut("pulse_rms", ds.p_pulse_rms[:] > 3500)
ds.cuts.cut(16, ds.p_pulse_rms[:] > 3500)  # this might work too.

cut_num of "pulse_rms" field would not be 15 because "calibration" categorical field takes bit #15. If "pulse_rms" is the first non-buildin cut field, its cut_num will be 16.

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

Agreed. I guess it could work instead of throwing an error. I think we will be better off moving people to use the API for named cuts by fast by having it error out. We all agree failing silently is not acceptable.
Check out my first attempt at documentation
https://bitbucket.org/joe_fowler/mass/src/3c2f19e866da7e641d7389b21f4bdff63d3e7df5/doc/multibitcutsdoc.md?at=master&fileviewer=file-view-default

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Okay. We can use cuts-by-name only, but don't close this issue until an explicit error is raised when someone tries to cut-by-number.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Young fixed this in ce800784

Original comment by Young Il Joe (Bitbucket: jojo978, GitHub: jojo978).

You can use cut_num for ds.cuts.cut. And In the setup_cleanup branch, it will raise an exception when you use an unregistered cut_num (not operating with a 0x0000 mask (because it's is the bit mask of unregister boolean fields.), which means it doesn't anything.).


Set spark.executor.cores for integration tests.

Fixes #9135. (By workaround.)
This change sets spark.executor.cores to 10, if it is unset. This allows integration tests to work around the failure seen in parquet_test.py:test_small_file_memory, where the COALESCING Parquet reader's thread pool accidentally uses 128 threads with 8MB memory each, thus consuming the entire heap.
Note that this is a bit of a workaround.  A more robust solution would be to scale the Parquet reader's buffers based on the amount of available memory, and the number of threads.

Build

Build

we need to really fix the underlying problem ASAP instead of trying to work around it.

This was an attempt to get a clean build on CDH, as quickly as possible.  But I'm supportive of closing this in favour of a proper fix.


OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: labels_ids

请问报如下错误怎么解决。不太会用tensorflow。tf1.14，python3.7。
tensorflow.python.framework.errors_impl.InvalidArgumentError: Key: label_ids.  Can't parse serialized Example.
[[{{node ParseSingleExample/ParseSingleExample}}]]
[[IteratorGetNext_1]]
`2022-07-19 17:54:06.585078: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.585078: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585079: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585080: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.585079: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585081: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585078: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585078: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585261: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585425: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.585578: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.585726: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.585881: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.586023: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.586179: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.586350: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.586478: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.586596: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.586753: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.586914: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.587075: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.587216: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.587381: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.587516: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.587719: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.587903: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.588029: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.588155: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.588301: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.608222: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.608370: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.608543: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.608761: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.608971: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.609096: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.609239: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.609370: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.609532: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.609641: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.609754: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.609894: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.610038: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.610166: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.610324: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.610455: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.610613: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.610730: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.610822: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.610985: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.611127: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.611255: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.611406: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.611544: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.611700: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.611819: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.623638: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.623781: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.624002: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.624212: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.624389: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.624663: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.624811: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.624945: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.625097: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.625244: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.625382: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.626553: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.626724: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.626893: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.627058: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.627226: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.627397: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.627583: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.627769: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.625681: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.625821: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.625961: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.626121: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.626261: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.626419: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.625539: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.652520: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.652642: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.652770: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.652943: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.653093: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.654222: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.653344: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.653500: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.653614: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.653802: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.653912: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.654072: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.653206: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.654397: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.654578: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.654736: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.654877: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.655011: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.655160: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.655329: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.655450: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.655606: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.668172: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.668292: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.668497: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.668630: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.668789: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.668895: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.669051: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.669212: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.669367: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.669502: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.669628: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.669761: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.669867: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670014: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670158: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670295: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670432: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670564: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670709: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.670840: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.670992: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.671124: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.671257: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.683611: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.683673: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.683768: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: label_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.683947: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.684041: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: lmask.  Can't parse serialized Example.
2022-07-19 17:54:06.684181: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_mask.  Can't parse serialized Example.
2022-07-19 17:54:06.684352: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: input_ids.  Can't parse serialized Example.
2022-07-19 17:54:06.684491: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at example_parsing_ops.cc:240 : Invalid argument: Key: segment_ids.  Can't parse serialized Example.
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1356, in _do_call
return fn(*args)
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1341, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1429, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Key: label_ids.  Can't parse serialized Example.
[[{{node ParseSingleExample/ParseSingleExample}}]]
[[IteratorGetNext_1]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:/workspace/pycharm/CRASpell/src/train_eval_tagging.py", line 193, in
train(FLAGS)
File "D:/workspace/pycharm/CRASpell/src/train_eval_tagging.py", line 148, in train
f1 = evaluate(FLAGS, sess, model, test_data_processor)
File "D:/workspace/pycharm/CRASpell/src/train_eval_tagging.py", line 40, in evaluate
inputs, loss_value, preds, golds, gmask = sess.run([input_ids, pred_loss, pred_result, gold_result, gold_mask])
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 950, in run
run_metadata_ptr)
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1173, in _run
feed_dict_tensor, options, run_metadata)
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1350, in _do_run
run_metadata)
File "C:\ProgramData\Anaconda3\envs\b4k\lib\site-packages\tensorflow\python\client\session.py", line 1370, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Key: label_ids.  Can't parse serialized Example.
[[{{node ParseSingleExample/ParseSingleExample}}]]
[[IteratorGetNext_1]]
`

这个可能是tf版本不对，具体原因还得自行排查


chore: disable Escape event listener earlier in lifecycle

This PR prevents User from closing the Transaction modal by hitting Escape. It gives a false sense that the tx has been cancelled when in fact it hasn't.
I've created a function which removes an event listener upon hitting the Confirm button. Using this lifecycle, should I remove the windows.removeEventListener() from onUnmounted hook, since it should be disabled by then?

I'm not seeing a Cancel button render for Part 1 of this story(checkbox 1) re: Hardware ledgers. I've gone through the notions of
1: Creating a TX by sending token
2: Confirming PIN and hitting Confirm
3: While in the loading/Submitting TX, I still don't see any cancel buttons
4: While signing on my ledger, i still don't see any Cancel buttons render.
Let me know if i should be seeing a Cancel button render on Olympia
@caleboller @saminakh


[Bug]: When the structural comparison results are only consistent, initiating structural synchronization should not be available

ODC version
odc424
OB version

What happened?

What did you expect to happen?
Initiate structure synchronization should be grayed out
How can we reproduce it (as minimally and precisely as possible)?
Select two identical tables to initiate structural comparison
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit d5975f2e39efb8f003a60dc52b710c41182ac7ca
------
陈朝俊
Mon Mar 4 15:59:03 2024 +0800

pass


Changed the documentation URL to match Karma version 0.12

Actual: "Karma's docs http://karma-runner.github.io/0.8/plus/RequireJS.html"
Expected: "Karma's docs http://karma-runner.github.io/0.12/plus/requirejs.html" OR
"Karma's docs http://karma-runner.github.io/0.12/plus/RequireJS.html"
Also links from the 0.8/plus/RequireJS.html to the 0.12 version are broken due to differences in letter captitalization. Signed-off-by: Bogdan Bivolaru<EMAIL_ADDRESS>

Fixed


Why am I getting a 'not_allowed_token_type' error from the Slack API?

I am trying to open a modal when a user clicks my app's Global shortcut.

But when I try, I receive the following error message:
<IP_ADDRESS> - - [08/Jun/2021 15:54:37] "POST /slack/events HTTP/1.1" 200 -
Error creating conversation: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_allowed_token_type'}

I'm not sure what the source of the issue is, since I am able to successfully use a separate function (update) to collect the text of a slack message when a user mentions my app (see @app.event("app_mention").
Note: In both Interactivity & Shortcuts and Event Subscriptions, both the Request URLs are my ngrok.io link at /slack/events (i.e. https://...ngrok.io/slack/events)
I also checked in previously logged issues on this github, and saw this. Afterwards, I checked the views.open method page here and see that it works with both bot and user token types with no scopes required.

What am I doing wrong?
Reproducible in:
The slack_bolt version
slack-bolt==1.6.1
slack-sdk==3.6.0
slackclient==2.9.3
slackeventsapi==2.2.1
Python runtime version
Python 3.9.2
OS info
ProductName:	macOS
ProductVersion:	11.3.1
BuildVersion:	20E241
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Steps to reproduce:

source venv/bin/activate
python3 main.py
./ngrok http 3000
Click shortcut using Bolt icon.

Source code:
.env
export MONDAY_API_KEY="..."
export SLACK_BOT_TOKEN="xoxb-..."
export SLACK_SIGNING_SECRET="..."

main.py
import os
# Use the package we installed
from slack_bolt import App
from slack_sdk.errors import SlackApiError
import requests
import json

# Initializes your app with your bot token and signing secret
app = App(
    token=os.environ.get("SLACK_BOT_TOKEN"),
    signing_secret=os.environ.get("SLACK_SIGNING_SECRET")
)

@app.event("app_mention")
def update(client, event, logger):
    try:
        apiKey = os.environ.get("MONDAY_API_KEY")
        apiUrl = "https://api.monday.com/v2"
        headers = {"Authorization" : apiKey}
        board_id = "1029994357"
        query5 = 'mutation ($myItemName: String!, $columnVals: JSON!) { create_item (board_id:'+board_id+', item_name:$myItemName, column_values:$columnVals) { id } }'
        vars = {
        'myItemName' : event["blocks"][0]["elements"][0]["elements"][1]["text"]
        }
        data = {'query' : query5, 'variables' : vars}
        r = requests.post(url=apiUrl, json=data, headers=headers) # make request
        print(r.json())
    except Exception as e:
        logger.error(f"Error publishing home tab: {e}")

# The open_modal shortcut listens to a shortcut with the callback_id "open_modal"
@app.shortcut("file_bug")
def open_modal(ack, shortcut, client, logger, body):
    # Acknowledge the shortcut request
    ack()

    try:
        # Call the views_open method using the built-in WebClient
        api_response = client.views_open(
            trigger_id=shortcut["trigger_id"],
            # A simple view payload for a modal
            view=
                {
                    "title": {
                        "type": "plain_text",
                        "text": "File a bug",
                        "emoji": True
                    },
                    "submit": {
                        "type": "plain_text",
                        "text": "Submit",
                        "emoji": True
                    },
                    "type": "modal",
                    "close": {
                        "type": "plain_text",
                        "text": "Cancel",
                        "emoji": True
                    },
                    "blocks": [
                        {
                            "type": "section",
                            "text": {
                                "type": "plain_text",
                                "text": "This form will submit your bug to the #dev-bugs board on monday.com",
                                "emoji": True
                            }
                        }
                }
        logger.info(api_response)
    except SlackApiError as e:
        logger.error("Error creating conversation: {}".format(e))

# Start your app
if __name__ == "__main__":
    app.start(port=int(os.environ.get("PORT", 3000)))

Expected result:
Modal is opened, as shown in "Modal Preview" in Block Kit Builder.
Actual result:
Error message in terminal tab running bolt app:
<IP_ADDRESS> - - [08/Jun/2021 15:54:37] "POST /slack/events HTTP/1.1" 200 -
Error creating conversation: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_allowed_token_type'}

Error message in Slack app:

Hey @chxw, thanks a bunch for the detailed issue!
☑ You're right that views.open should work with either a bot or user token. And it looks like you're using the bot token right now (xoxb-).
☑ I was also able to setup your example on my local machine and open the modal successfully. (I just had to edit a typo in the views= and I used SocketMode instead of ngrok). So, everything looks good at a glance!
Would you mind double-checking your SLACK_BOT_TOKEN to ensure that it starts with xoxb- by adding a print statement to your code? I know you confirmed it in your .env above, but it would be good to know that it's also output in your app:
print("SLACK_BOT_TOKEN:", os.environ.get("SLACK_BOT_TOKEN"))

In the meantime, I'll spend some time digging deeper into whether this another reason why you may be experiencing this problem.

@chxw would you mind also confirming that your xoxb- token matches the token on api.slack.com/apps? You may sometimes receive not_allowed_token_type if the previous token was revoked/expired/changed.

Hi @mwbrooks, thanks for the quick response.
Wow you got it, I had previously run source .env when the .env file had an old/incorrect token, but after updating the .env file, I had forgotten to re-run source .env.
Thank you for help!


Markdown makes extra paragraphs

The GitHub and BitBucket markdown processor only creates a new paragraph after a blank line. However, gitbucket makes a new paragraph after every newline. For example, imagine that the following lines were not surrounded by quad-quotes; GitHub and BitBucket would display these as one paragraph:
This
should
be one
paragraph

I expect this problem will be fixed in GitBucket 3.7 by new markdown processor markedj.
See also #912.


Fix checklist dependency when field is cleared

WHY
BEFORE - What was wrong? What was happening before this PR?
We introduced a new CRUD rule, that is: if the field is not present in the request Backpack will not attempt to touch it by any means, it's just ignored. Previously Backpack would consider that the field was cleared by the developer when not present in the request and would clear anything related with it.
Checklist_dependency setup the values with JS in some fashion way, so if you remove all associations from the interface nothing would be posted for those two fields, and following the new rule, since nothing is posted, nothing happens.
AFTER - What is happening after this PR?
Now, when the user clears all the associations, we will send an empty value for those two fields so Backpack can kick in and know that the field was cleared.
HOW
How did you achieve that, in technical terms?
Added hidden inputs that get sent when user clears the selections.
Is it a breaking change or non-breaking change?
non after the breaking one 🙃
How can we test the before & after?
@tabacitu tested the before in #4071 and could do the same with this PR to test the after.

Works like a charm! I think we've finally got checklist_dependency bug free, for the first time ever 😅
Thank you @pxpm .


fix circular dependencies in tooltip

Noticed some errors when building with webpack 5. the index.js is requiring the files, but then they require other imports through the index.js as well which causes problems. Resolves the errors from issue: https://github.com/bangle-io/bangle.dev/issues/151

I have moved 3ea3339 to #154  which should partly fix the problem and I am laying down other things that will help the original problem in #153


Add param block and use the actual script location for finding YARA

Add a param block similar to the following:
[CmdletBinding()]
param (
    [Parameter(Mandatory=$false)][int]$usrScanscope = $env:usrScanscope,
    [Parameter(Mandatory=$false)][bool]$usrUpdateDefs = $env:usrUpdateDefs,
    [Parameter(Mandatory=$false)][char]$usrMitigate = $env:usrMitigate
)

Use this to get the location of the script itself, not the current directory:
$scriptObject = Get-Item -Path $script:PSCommandPath
$script:workingPath = $($scriptObject.DirectoryName)

So that this:
foreach ($iteration in ('yara32.exe','yara64.exe')) {
    if (!(test-path $iteration)) {
        write-host "! ERROR: $iteration not found. It needs to be in the same directory as the script."
        write-host "  Download Yara from https://github.com/virustotal/yara/releases/latest and place them here."
        exit 1
    } else {
        write-host "- Verified presence of $iteration."
    }

becomes this
foreach ($iteration in ('yara32.exe','yara64.exe')) {
    if (!(test-path "$script:workingPath\$iteration")) {
        write-host "! ERROR: $iteration not found. It needs to be in the same directory as the script."
        write-host "  Download Yara from https://github.com/virustotal/yara/releases/latest and place them here."
        exit 1
    } else {
        write-host "- Verified presence of $iteration."
    }

Hope this helps 😊

Hi;
This is a great resource for people looking to bolster the script, thank you for adding it.
The reason the script is written the way it is is because originally it was intended for use with the Datto RMM solution which does not require the above steps to be taken; however, if we make "generic" scripts in future I will endeavour to bridge this gap a little closer.
I won't close this case so everyone can see it.
Cheers – SL

For completeness sake, and because with the initial proposed edits alone the script would break, I forked the repo and edited the script to include these edits. I'll also edit the initial issue with the link to the fork. https://github.com/ProVal-Tech/log4shell-tool


Added options attribute addition documentation

I was tasked to create a product that would be out-of-the-box available to our users, so I added the attributes in a data migration but I had a hard time finding any resource that describes adding options via code and had to dig through Oscar's code on GitHub to figure this out. People would benefit from an addition like this, at least save time from digging through code to figure this out.

Lovely addition, thank you very much.

@maikhoepfel I don't see this addition in the Oscar documentation. Is something wrong with it?