Plumb "not yet seen by server" bit up from transport layer

In progress

[trickle] No significant performance differences

[microbenchmarks] Performance differences noted:
Benchmark                                   cpu_time    real_time
------------------------------------------  ----------  -----------
BM_ErrorGetStatusCode<ErrorCancelled>       +4%         +4%
BM_HasClearGrpcStatus<ErrorCancelled>       +12%        +12%
BM_HasClearGrpcStatus<ErrorNone>            +11%        +9%
BM_HasClearGrpcStatus<ErrorWithGrpcStatus>  +6%         +7%
BM_HasClearGrpcStatus<ErrorWithHttpError>   +5%         +4%
BM_HasClearGrpcStatus<SimpleError>          +8%         +8%
BM_SliceFromStatic                          +15%        +13%

[trickle] No significant performance differences

[microbenchmarks] Performance differences noted:
Benchmark                                   cpu_time    real_time
------------------------------------------  ----------  -----------
BM_ErrorGetIntFromNoError                   -4%         -4%
BM_ErrorGetMissingInt                       -9%         -8%
BM_HasClearGrpcStatus<ErrorWithGrpcStatus>  -4%         -4%

[trickle] No significant performance differences

[microbenchmarks] Performance differences noted:
Benchmark              cpu_time    real_time
---------------------  ----------  -----------
BM_ErrorGetMissingInt  -8%         -9%

Fixes #9884.

We've recently decided that we need to be able to differentiate between these two cases:

The bytes were never sent on the wire.
The bytes were sent on the wire but the server told us (either via a GOAWAY or a REFUSED_STREAM) that the stream was not processed.

We'll need some way to differentiate between these two cases in the grpc_error attribute.

@ncteisen, can you take over this PR (or just start a new one to do the same thing)?  Thanks!

This is too old to be useful.  We'll eventually need to get back to this, but when that happens, we'll probably just start from scratch.


Remove star rating support

Google removed star ratings from Google Music (https://productforums.google.com/forum/#!topic/play/HwKmVF5N5YA) - this PR removes everything related to star rating support.
There's also a bunch of changes related to pod install which means CocoaPods has updated stuff on their end.

:+1: All looks good to me :shipit:

:+1:


Web-ui: remanent bugs from the past

This PR fixes two bugs:

Partial fix for #626. There were two bugs in one. The Build header for the table disappeared as the JS script did not rebuild it. This PR completely removes the header, as it's not needed in the current version (correction 1). This bug didn't appear in the GitLab version, as the links to the API weren't available in the GitLab routes. This PR introduces these links in the GitLab router (correction2). @benmandrew mentioned that we could merge the router as the behaviour is the same, and I agree with his suggestion as it will make the code easier to maintain.
It also fixes a bug in the Organisation page by conforming it with the "two organisations" pages. Indeed, the design for one organisation differs from the one from the mixed organisation page. These two functions should be merged at some point and display the organisation we ask.
Fixes #626 for good. It improves the rendering by caching the fonts for a month (for now, as we still move fast), blocking the rendering until the font is loaded and specifying the type of screen for render optimisation.

I opened an issue to track the refactoring we could do: #746

👍👍👍


angular.equals issue with objects containing custom toString methods.

angular.equals({}, { 'toString': function() { return 'custom'; } });
// => true (expected false)

I think this is due to the isFunction check in.

The angular.equals purposefully ignores methods on objects as it is assumed that they are helper methods and do not define the object's identity. This is important for duck-typing behaviour.
Closing since this is the expected behaviour and documented in the API docs: https://docs.angularjs.org/api/ng/function/angular.equals

During a property comparison, properties of function type and properties with names that begin with $ are ignored.

OK, so let's put this in the ice box and return to it if we get a real life use case that is breaking someone's app.


Issue in invoke event

Hello,
I subscribed for a custom event using
SRHubProxy *chat = [connection createHubProxy:@"ChatHub"];
 [chat on:@"MessageReceived" perform:self selector:@selector(MessageReceived:messageId:message:senderId:)];
but i am getting method signature argument cannot be nil exception
I attached an image

Thanks in advance

According to the documentation the signature will be nil under the following condition

An NSMethodSignature object that contains a description of the method identified by aSelector, or nil if the method can’t be found.

My best guess is the selector @selector(MessageReceived:messageId:message:senderId:) does not exist on the object self.  Maybe you have a typo?

thanks @abillingsley 😄

thanks @abillingsley 😄


Fix date timer in top-right to display current date/time

Currently the date timer counts up from a static date in 2017. It should use the current date/time.

Fixed in #120


PIMD does not appear to listen to Docker user networks on startup

I have iterated further from the situation described in #121 and disabled the docker0 default bridge network and instead created a new Docker network. What I now observe is that after server restart, PIMD does not operate on this network. If I restart PIMD, it starts operating as expected.
On Ubuntu 16.04 I install Docker and then disable the default bridge network by adding "bridge": "none" to the Docker configuration. Then I create a new Docker network using docker network create --driver bridge --gateway <IP_ADDRESS> --subnet <IP_ADDRESS>/24 asdf.
I also install pimd and keep its default configuration untouched.
After system restart, I currently manually execute sudo iptables --policy FORWARD ACCEPT as per #121 findings.

Then I create a container. Ifconfig now has a new entry:
vethd12df9d Link encap:Ethernet  HWaddr 7e:bb:5e:26:d5:5d
          inet6 addr: fe80::7cbb:5eff:fe26:d55d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13885 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19871 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1227631 (1.2 MB)  TX bytes:26850819 (26.8 MB)

This interface appears to be the one used by Docker for communicating to the container. I have no understanding of how it works (it has no ipv4?) beyond the fact that I see the container's traffic if I monitor this interface (e.g. when I do apt update the HTTP traffic goes over this interface).
I immediately notice that performing a packet capture on this new "veth" interface shows no PIM traffic. I would expect PIMD to start using this interface. When I start a listener, I see the listener's IGMP traffic but nothing from PIMD:
 37 55.147483747 <IP_ADDRESS> → <IP_ADDRESS>   IGMPv3 54 Membership Report / Join group <IP_ADDRESS> for any sources
   38 55.431623082 <IP_ADDRESS> → <IP_ADDRESS>   IGMPv3 54 Membership Report / Join group <IP_ADDRESS> for any sources

Indeed, PIMD is unaware of this join:
saares@michaelscarn:~$ sudo pimd -r | grep <IP_ADDRESS>
saares@michaelscarn:~$

After restarting PIMD, it immediately starts operating normally on this interface:
   39<PHONE_NUMBER>67 <IP_ADDRESS> → <IP_ADDRESS>    IGMPv3 50 Membership Query, general
   40<PHONE_NUMBER>67 <IP_ADDRESS> → <IP_ADDRESS>   PIMv2 60 Hello
   41<PHONE_NUMBER>04 <IP_ADDRESS> → <IP_ADDRESS>   IGMPv3 70 Membership Report / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources
   42<PHONE_NUMBER>57 <IP_ADDRESS> → <IP_ADDRESS>   IGMPv3 70 Membership Report / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources
   43<PHONE_NUMBER>17 <IP_ADDRESS> → <IP_ADDRESS>   IGMPv3 70 Membership Report / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources / Join group <IP_ADDRESS> for any sources

I would expect PIMD to not require to be restarted in this situation. Is the behavior I observe normal? Do I need to perform some additional configuration to get it to automatically use this interface?
If I restart pimd before creating the container (before the "veth" network is created) it works fine immediately when I start the container. Perhaps the veth network is just a red herring and the key factor is something that happens earlier on startup (related to the Docker created br- network?).

This looks like a duplicate of #21.  Currently pimd needs to be restarted to see new interfaces.  I have no idea how docker networking is integrated in Linux, so I cannot help you there.

Understood. Closing as duplicate then!


add seccomp markers for RHEL and CentOS Dockerfiles

Signed-off-by: Lokesh Mandvekar<EMAIL_ADDRESS>

@lsm5 is this fixing make test in RHEL? I'll merge and cherry-pick to other branches if it's the case

yes, it works for pulling rhel|centos image on rhel|centos host respectively.


[doctests] section requires too many things

$ ~/src/cppdoc/target/release/cppdoc build
Error reading config file: TOML parse error at line 12, column 1
   |
12 | [doctests]
   | ^^^^^^^^^^
missing field `run`

$ ~/src/cppdoc/target/release/cppdoc build
Error reading config file: TOML parse error at line 12, column 1
   |
12 | [doctests]
   | ^^^^^^^^^^
missing field `compiler_invocation`

I have enable = false specified, so it shouldn’t care what value I give for these options.

Thank you! This is was fixed.


Update: GM GN Wallet integration with Wallet Connect to support all DApps

Description

Integrate Wallet Connect into GM GN Wallet to support all DApps on Kaia
Overall cleanup to improve UX

Reference issue

#160

Category

Other

Approved. Revert back with implementation

Check the implementation here:
https://dev.gmgn.app/connect?network=kaia-kairos&address=0x3e747fE6Ccd221B9601324d8d76fca9CE0232108
you can interact with: https://www.blockcmd.com/drop/native
comments and docs included: https://github.com/gmgn-app/gmgn/blob/main/app/connect/page.tsx

Approved for 2000 KLAY bounty payout


Add rake task to export custom buttons

We need to be able to import/export custom buttons. This is basically a generic active record object export that works on custom buttons.
The related import PR:
https://github.com/ManageIQ/manageiq/pull/17726
Related:
https://github.com/ManageIQ/manageiq/pull/17726
Exporting
Create a directory for the exports:
mkdir /tmp/custom_buttons
Export cbs:
rake evm:export:custom_buttons -- --directory /tmp/custom_buttons
The export has a list of custom_button_sets with nested custom_buttons and associated resource actions as well as custom_buttons without sets and their associated resources.
export looks like this:

@miq-bot add_label enhancement

@tinaafitz @syncrou @eclarizio
@whoever_wants_to_review_me

@miq-bot remove_label wip

Test failures unrelated to this code!

@d-m-u Looks good.  My only comment is around exporting the userid for custom_button.  It makes sense to include it here for when import/export is used as a backup solution.  My concern is what to do during import into a new system when that userid does not exist.
At the moment this ID is only used for tracking who created the button.  I'll comment on the import PR so we can address this.

Hi, it seems I've found the problem in https://github.com/ManageIQ/manageiq/blob/master/spec/lib/task_helpers/imports/custom_buttons_spec.rb
Namely, the certain example is passed, but not for good reason.
The example at line 28 is about raising error, when we have 'bad file' in directory
It is passed, but this is not due to right flow, but due to error in
https://github.com/ManageIQ/manageiq/blob/master/lib/task_helpers/imports/custom_buttons.rb
The glob on line 6 is about *.yaml, BUT rspec generates temp 'bad' file with extension yamlXXXXX
where XXXX is some random thing.
So the glob does not include this file and the actually repeats " context "with existing identical buttons""
It seems the glob should be like '.yaml' in order to test this case
Also, line 33 should be deleted.
Am I right?

Hi @borisko123, thanks for reporting this issue.  Can you please open a git issue and someone can take a look.  Thanks.

Hi @borisko123, thanks for reporting this issue. Can you please open a git issue and someone can take a look. Thanks.

Hi @gmcculloug,
Among others things at PR #20137(add dialog support, ability to update existing buttons), I also fixed this issue.The solution was to use another Tempfile initializer, which enables to retain file extension.
The glob is untouched.
Please take a look


Pulumi outputs for Kafka cluster creation

Your Pulumi provider worked great for creating a Kafka cluster and topic! I have a couple of small enhancements I'd like to recommend:

The cluster info outputs include the cluster restEndpoint, but the endpoint does not include the port number.
Another useful output would be an link to the cluster page with a note that the password can be obtained from there. The link is shaped like: https://console.upstash.com/kafka/<clusterId>

All in all, great work! Thanks for making this.

Hey, you're right. We should add the port data


cannot find moments minted event using flow go-sdk

i am trying to  get all events for moment minted in flow go-sdk, and tried with all mainnet endpoints from 1 to 5 but get an empty array . all works well with moment listed
can anyone tell me what range of block or endpoint should i use in which i can get a event for moments minted?

It seems to me like you might be using the wrong event specification when querying the events. Can you make sure your event definition is A.0b2a3299cc857e29.TopShot.MomentMinted? You might accidentally be querying the wrong account or something

@joshuahannan  i can now find it at one specific block. but in case i need to get list of all moment minted events?
querring all mainnet and candidate sporks is very tedious and again for some mainnet we have to search batches

I'm sorry that it is so difficult for you. We're going to make this process easier in the future, but unfortunately this is how it is for now

@joshuahannan, can you please do me a favor. can i somehow get at least the starting block from where i should start querrying events that way may be save sometime? like may be all moments minted events are after block x?

@vijaytabhatt There are moment minted events that go all the way back to June. The Top Shot team mints moments all the time. so you should be able to find it from almost any week

@joshuahannan is there way

where i can check if a minted moment is present in a pack?
In Moment purchased event we get, seller but not buyer. from where can get buyer or who owns the moment currently

Packs are an off-chain construct, so you can't see if moments are in packs on chain
You can get the buyer by finding the deposit event that was emitted in the same transaction as the moment purchased event

thank you @joshuahannan

@joshuahannan
i am trying to scan "MomentPurchased" events from NBA topshot contract and storing it in database
i was doing a comparison to check if the data captured is proper by comparing it with data on graph at https://evaluate.market/
evaluate.market
Analyze Top Shot and digital collectibles
however to my suprise i have more record , i have 70880  transactions for momentPurchased for 29th April, but evaluate.market shows only 24,015
not sure what am i missing

It looks like evaluate.market is showing 96k transactions. Where are you seeing the 24k? They might be querying a different time range than you. Maybe you should reach out to them?


filtering error log: https://github.com/metanorma/metanorma-utils/iss…

…ues/34
Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

The behaviour that comments are only rendered if the document has :draft: was removed years ago, although I cannot find when.

@opoudjis how about doing a blog post for the new logging capabilities and debugging?

I've been moving mountains for years on Metanorma: this is what you want a blog on?
If you want any task out of me whatsoever, ticket. I cannot keep track of things as is.


Bump spikeinterface and neo versions

This PR objective is to synch with the latest release and catch any bugs on the CI if they appear

Already in progress on https://github.com/catalystneuro/neuroconv/pull/132
Also, let's try using lower bound versioning whenever possible with the new structure in order to minimize chance of conflicts (which have potential to arise any time we use exact pinning or upper bounds).
Individual conversion projects should still generally use a frozen set of exact version pins however, to ensure that the code functions well into the future.

Already in progress on #132

I needed to do some changes as they modify the format of the probe as I mentioned on the other issue. Now it seem to be working and I will set the base of this PR to #132.
@weiglszonja, feel free to just copy and paste the changes or merge from here to there.


whitespace commit: troubleshooting circle ci

circleci appears to be working again, so i made the checks required again.


[PE-D][Tester D] Improvement

I think a student's name and parent's name should not be allowed to contain numbers

Labels: type.FeatureFlaw severity.VeryLow
original: lilythchu/ped#8

See #226


1721563732748-base.js

Describe the bug
Please report this issue with the "1721563732748-base.js" file on https://github.com/distubejs/ytdl-core/issues.
Debug File
1721563490715-base.txt
Environment

@distube/ytdl-core version:
Node.js version:
Operating system:

Please update @distube/ytdl-core to ver. 4.13.5 using npm install @distube/ytdl-core@latest command.

i will do it

Duplicated #22


Mamba missing in snakemake environment

Thank you for the workflow catalog, it is a great initiative.
There is an inconsistency in the 'Usage' instructions for the 'standardized usage packages'.
In step 1 (install Snakemake and Snakedeploy) the conda environment is generated
mamba create -c bioconda -c conda-forge --name snakemake snakemake snakedeploy
In step 4 (run workflow) the recommendation to run the workflow is
snakemake --cores all --use-conda
By default the local conda environments are generated and loaded using mamba, however mama was never installed. I recommend installing mamba within step 1.

Hi! We mention that in the first sentence of step 1. Maybe it should be highlighted more? I intentionally did not put the explicit steps to install mamba there, because there are many different ways, which also might change further in the future. Hence I thought it might be better to link to the mamba docs.


Adding hover effect on drop down menu

Adding hover effect in the drop-down menu and border-radius.

hey @Arjundotadex
I am a Gssoc'23 contributor.
I would like to work on this. Please assign me this issue.
Thank you :)


Create IG route for International payments

Description

[ ] Create Route on Ig routes project openbanking-demo routes
[ ] Create if necessary specific groovy script to implement on IG the international payments.
[ ] Methods to support: GET, POST

Endpoints

Endpoints

Acceptance criteria

[ ] The route is deployed in Ig with no errors.
[ ] Proper response expected by the spec
[ ] Errors expected match with the OBIE specs
[ ] Route documented

[ ] Route source commented
[ ] Add the route documentation to the wiki route section

Hey team! Please add your planning poker estimate with ZenHub @andra-racovita @mariantiris


Migrate from sun.misc.BASE64Decoder and sun.misc.BASE64Encoder to  java.util.Base64

See https://stackoverflow.com/questions/13109588/encoding-as-base64-in-java

Thanks @yeikel, this will probably be similar to
ApacheBase64ToJavaBase64 in rewrite-migrate-java


[BUG] Cannot build go library on M1 mac (arm64)

Description
Trying to run the go examples
clone https://github.com/informalsystems/modelator.git
cd modelator/go
go test -v ./examples/...

# github.com/informalsystems/modelator/go/pkg/core
Undefined symbols for architecture arm64:
  "_generate_json_traces_from_tla_tests_rs", referenced from:
      __cgo_f7cf0de42a51_C2func_generate_json_traces_from_tla_tests_rs in _x002.o
      __cgo_f7cf0de42a51_Cfunc_generate_json_traces_from_tla_tests_rs in _x002.o
     (maybe you meant: __cgo_f7cf0de42a51_C2func_generate_json_traces_from_tla_tests_rs, __cgo_f7cf0de42a51_Cfunc_generate_json_traces_from_tla_tests_rs )
ld: symbol(s) not found for architecture arm64
clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
FAIL	github.com/informalsystems/modelator/go/examples/numbersystem [build failed]
FAIL

Expected behavior
=== RUN   TestFixedExecutions
=== RUN   TestFixedExecutions/test_0
=== RUN   TestFixedExecutions/test_1
--- PASS: TestFixedExecutions (0.00s)
    --- PASS: TestFixedExecutions/test_0 (0.00s)
    --- PASS: TestFixedExecutions/test_1 (0.00s)
=== RUN   TestModelBased
2021/11/08 15:15:26 Generating traces using Modelator cgo-binding...
=== RUN   TestModelBased/[test:_AMaxBMaxTest,_trace:_0]
=== RUN   TestModelBased/[test:_AMaxBMinTest,_trace:_0]
=== RUN   TestModelBased/[test:_AMinBMaxTest,_trace:_0]
--- PASS: TestModelBased (2.79s)
    --- PASS: TestModelBased/[test:_AMaxBMaxTest,_trace:_0] (0.00s)
    --- PASS: TestModelBased/[test:_AMaxBMinTest,_trace:_0] (0.00s)
    --- PASS: TestModelBased/[test:_AMinBMaxTest,_trace:_0] (0.00s)
PASS
ok  	github.com/informalsystems/modelator/go/examples/numbersystem	2.792s

System information
OS: OSX Big Sur 11.4
Model Name:	MacBook Pro
Model Identifier:	MacBookPro17,1
Chip:	Apple M1
Total Number of Cores:	8 (4 performance and 4 efficiency)
Memory:	16 GB
System Firmware Version:	6723.120.36
OS Loader Version:	6723.120.36
Serial Number (system):
Hardware UUID:	C9CCDB30-8E85-5D8D-BA75-878942A3E5BC
Provisioning UDID:	00008103-000978E83ADA001E
Activation Lock Status:	Disabled
Additional context
I will try to figure out a workaround

I see I probably have to simply create the right entry in target/

Thanks @danwt. I am having trouble compiling for arm64 target (it is aarch64-apple-darwin in rustup target list). Can you create a PR with appropriate library at go/third_party/mbt/target/aarch64-apple-darwin/release/?

Looks like it is a build script issue from ring crate. I can't cross-compile or use Github action at Linux x86_64 until it is fixed.

Also this calls for separating asset downloading code from core code. ring is a dependency from rustls from ureq.

Thanks @danwt. I am having trouble compiling for arm64 target (it is aarch64-apple-darwin in rustup target list). Can you create a PR with appropriate library at go/third_party/mbt/target/aarch64-apple-darwin/release/?

Thanks @rnbguy I will take a look at this.

Hey @rnbguy - is this issue still up for grabs? I notice this branch has something that seems relevant?
https://github.com/informalsystems/modelator/tree/rnbguy/go/rust-lib-precompiled

yes, you can commit a arm64-apple-darwin library to it :)
I will setup the CI for precompiled releases soon.


fix: release and build information PT-1652

Description :sparkles:
Issues :bug:
Closes :no_good_woman:
PT-1652
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

kultus-ui branch is deployed to platta: https://kultus-ui-pr284.dev.hel.ninja :rocket::rocket::rocket:

kultus-ui branch is deployed to platta: https://kultus-ui-pr284.dev.hel.ninja :rocket::rocket::rocket:

kultus-ui branch is deployed to platta: https://kultus-ui-pr284.dev.hel.ninja :rocket::rocket::rocket:

kultus-ui branch is deployed to platta: https://kultus-ui-pr284.dev.hel.ninja :rocket::rocket::rocket:


Unbuffered Stream Reader

Adds UnbufferedStreamReader. A stream reader that does not buffer data from the backing BaseStream.
This implementation is less performant than StreamReader but doesn't read ahead on the underlying stream ensuring the BaseStream's position to remains lockstep with the characters read out of UnbufferedStreamReader.
This stream is useful when reading files with mixed encoding or where the BaseStream needs to be advanced the minimum amount required.
What is the current behaviour?
StreamReader fills a buffer of characters when responding to read requests. The characters buffer is filled by repeatedly reading blocks of its BaseStream and converting them into characters until the character buffer is full.
This means that the BaseStream is advanced beyond the point that the StreamReader has been read.
What is the new behaviour?
UnbufferedStreamReader effectively functions the same as StreamReader with a byte and character buffer size set to 1. The UnbufferedStreamReader reads one byte at a time out of BaseStream until it has enough to resolve a full character. That one character is then evaluated by the read method to decide whether to continue reading or return.
Note: The implementation does not currently cover the complete features set of StreamReader. New features will be developed as needed. This effort is captured in #87
Why don't you just calculate actual the BaseStream position based on StreamReader's unused buffer contents?
TL;DR

Invalid bytes are replaced with a pre-defined fallback character which may not equal the byte size of the invalid bytes.
The reflection relies heavily on Microsoft not changing the way StreamReader is implemented
It does not work for variable-byte encodings (Ex: UTF-7)

I went down that path. It's not possible. This StackOverflow post covers the issue in detail. Read the linked post + all comments to understand.
If you really want to dig into this read through StreamReader's source: https://referencesource.microsoft.com/#mscorlib/system/io/streamreader.cs,b5fe1efcec14de32
What issues does this resolve?
None, This class allows developers to continue reading a BaseStream beyond the lifecycle of the UnbufferedStreamReader.
What PRs does this depend on?

None

Does this introduce a breaking change?

[ ] Yes
[x] No

Feedback addressed


Re-sync account properties to session

The following four account properties may be changed remotely – either by a client in another session for the same account, or by an administrator:
email
username
status
roles_mask

During the lifetime of a session, these properties should regularly be fetched from their authoritative source in the database and synchronized back to the session. This should happen after a defined interval, e.g. every 5 minutes, which may also be configurable. The following fields in the session should be affected:
$_SESSION[UserManager::SESSION_FIELD_EMAIL]
$_SESSION[UserManager::SESSION_FIELD_USERNAME]
$_SESSION[UserManager::SESSION_FIELD_STATUS]
$_SESSION[UserManager::SESSION_FIELD_ROLES]

Additionally, a new flag should be introduced that is stored in a new column (and table) in the database. It will hold the information whether all sessions for a given account (except for one session, optionally) must perform a logout. This will allow for remote logouts and for revoking any (other) open sessions for an account as an additional security instrument that can be offered to users.

if we have to sync with db, then why not try with https://github.com/phpauth/phpauth
I tried with that as this is good, only with email login, not with a username.  East pdo debugging than this one.

With regard to a user’s email address, username, status, and list of roles, this is supported now and turned on by default.
Implemented in:

https://github.com/delight-im/PHP-Auth/commit/21341d3c185928fe5f92ce04484c9a9b648fc4c8
https://github.com/delight-im/PHP-Auth/commit/89e99d727dbaa3955b5b49dd9d1538307314033a

The support for remote logouts will be tracked here: https://github.com/delight-im/PHP-Auth/issues/85


Looking at the actions documentation, it looks like I should be able to use {{ env }} in my jinja expression, but this is actually failing:
---
description: T
enabled: true
entry_point: 't.sh'
name: t
runner_type: local-shell-script
parameters:
    t:
        type: "string"
        description: "T"
        required: true
        default: "action: {{ action_context }} execid: {{ env }}"
        position: 1
...

The t.sh script just echoes its given parameters
Results in this:
  stdout: '{u''trace_context'': {}, u''user'': u''stanley'', u''pack'': u''oiobuild''}'

What I want to do is use execution ID in a "notify" to let user have a back link to st2:
notify:
  on-success:
    message: "To find more details, go to: https://stackstorm.openio.io/#/history/{{ env.ST2_ACTION_EXECUTION_ID }}/general"

I didn't find any help in the doc, even if the env() one, from here looked promising...
What am I missing ?

I believe issue is related to a life-cycle phase of an execution (those environment variables are set in a later phase of action execution) - in short, those environment variables can only be accessed inside a running action and not inside the metadata file which is rendered before action runs and before action execution object with an assignment id is created.
It's also worth noting that parameter default attribute and notify sections are not handled in the same manner - as mentioned above, parameter attributes are rendered before action runs and notify section is rendered at the end when execution finishes so different information is available in the context in those two scenarios. So it might actually work in the message, but I'm not 100% and would need to confirm.
In the documentation page you linked - env() is a utility function which is available inside Mistral workflows during run-time and that's different than what variables are available in the default context. So that's also different because env() function runs during the life-time of an execution aka when execution is running so information is available then.

As far as your original problem goes - I believe you might also be able to utilize web_url attribute of the execution_db object, but the actual root cause of "chicken and the egg" problem still persists, and afaik, there is no way around that, at least as far as action params are concerned, notify section is a different story.

Here is the context which is available when rendering notify.message attribute - https://github.com/StackStorm/st2/blob/master/st2actions/st2actions/notifier/notifier.py#L197.
So perhaps something like {{action_parameters.env.FOO}} should work. If that doesn't work, we can explicitly add execution_id to the context there (it's easy enough).

OK, that's all technical stuff, explaining why it is working (or not) like that.
But rereading the cited doc, I expected it to work:
When configuring the metadata, there are several built-in parameters that can be used and overwritten to change the default functionality of the various runners:
env - (local-shell-script, local-shell-script-script, remote-shell-script, remote-shell-script-script, python-script) Environment variables which will be available to the executed command/script.
Maybe this is because I'm not a native english speaker, but this looks misleading to me.
{{action_parameters.env.FOO}} or {{ execution_db.web_url }}
in params (at least there) leads to that:
Dependecy unsatisfied in action_parameters
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2api/controllers/v1/actionexecutions.py", line 180, in _schedule_execution
    liveaction_db.context)
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/util/param.py", line 230, in render_live_params
    _validate(G)
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/util/param.py", line 145, in _validate
    raise ParamException(msg)

@vincent-legoll Yeah, it's very possible that documentation is not accurate and needs updating. Need to dig in and confirm for sure first though.
Also, where did you try {{action_parameters.env.FOO}} - action param default value or notify section? Because as mentioned above, that's only available in notify.foo.message section.


Add progress monitoring

For small graphs like BioGRID, it might be reasonable to wait for 30 seconds or so in the different steps, but as the graphs start getting large and training time gets into the minutes/hours, it would be nice to communicate progress to the user.
I would normally suggest using tqdm, but after modifying the code myself, it doesn't look like it plays nicely with numba's parallelization. I found this thread: https://github.com/numba/numba/issues/4267 that describes the issue a bit more in detail, and the outlook is a bit grim.
It's not a dealbreaker, but it would make your package much more user friendly.

Many tries have been made to exchange progress information among threads during numba jit parallelism, which is necessary to print the overall progress, in particular, for the simulate_walk function. One of the thoughts was to use atomic operation to sync progress among threads, but cpu atomic is not available yet: numba/numba#2988. Another thought was to use reduction on iteration count, but the reduction only happens after all threads are done.

It is also attempted to use only one of the threads to print the progress as the estimation to the overall progress by using numba.np.ufunc.parallel._get_thread_id(). However to print out progress bar in a nice format, it is necessary to be able to flush out the previous stdout line with current print, which is made possible in Python either by print(flush=True) or sys.stdout.flush(), and yet neither is supported in nopython mode: numba/numba#3475

Interesting discussion, one I've been following for some time (across other threads).
In my case I've been using a manual progress bar (just hash symbols printed as strings from no python mode) and when in parallelised mode it scrambles the order, e.g.:
|                                 | 0.0 %
|############################     | 87.87 %
|########################         | 75.75 %
|################                 | 51.51 %
|####################             | 63.63 %

Though I suppose this still gives some indication that something is happening. I suppose one way is to change the progress bar to read something like "one of x number of batches completed..." instead of a percentage and progress bar...

Hi @songololo, thanks for your comment! That's a good idea and I've tried something similar along this line. But as you've pointed out at the end, there's some issue with the scheduling being random. And also the main issue that hold this kind of counting base approach back is due to inability to communicate progress information across threads during parallel execution in Numba, as briefly discussed above. So it is at the moment impossible to get an overall progress by counting the number of iterations done across all threads.
With that being said, we could instead monitor the progress in each thread separately, and output similarly "x% of iterations completed in thread i / N", where i is the thread id and N is the total number of threads. However this makes the monitoring very messy and might not be a good idea to do so. One work around is to flush out previous prints whenever next monitoring message is being printed. But the flushing option is not currently supported by Numba nopython mode (see above).

@RemyLau I don't fully understand the numba.np.ufunc.parallel._get_thread_id() approach, but if it works in principle, then would this be worth pursuing?
i.e. just making peace with a not-so-nice progress bar that doesn't flush between prints?

@songololo so the main idea of the _get_thread_id() approach is to keep track of the progress of each individual thread instead of the overall progress since we numba threads are not capable of communicating with each other at present. I did try to make it print out the progress just now and I realized that even if we're only keeping track of progress within a single thread, there's a complication: the total number of jobs (or iterations) assigned to a thread is not known a priori so we can't compute the percent of iteration done by individual thread either.
Update: after some more searching, it seems like prange by default perform static scheduling and assign (roughly) equal number of jobs to each thread, see this reply in an issue with numba scheduling. So perhaps I could still output to the progress for each thread. Another complication I've encountered is that nopython mode does not support string formatting (see numba/numba#3250). In another thread numba/numba#3475, this is linked to an StackOverflow thread, which uses the objmode() context manager to resolve this issue.

@RemyLau thanks, this makes sense compared to what I've experienced with plotting progress from prange.
For example, I've now switched to really simple updates which report a non-sequential bundle number:
Completed non-sequential bundle 1 of 33
Completed non-sequential bundle 30 of 33
Completed non-sequential bundle 26 of 33
etc.

From a function which looks like this:
@njit(cache=False)
def progress_bar(current: int, total: int, steps: int = 20):
    '''
    Printing carries a performance penalty
    Cache has to be set to false per Numba issue:
    https://github.com/numba/numba/issues/3555
    TODO: set cache to True once resolved
    '''
    if steps == 0:
        return
    step_size = int(total / steps)
    if step_size == 0:
        return
    if current % step_size == 0:
        chunk = round(current / step_size) + 1
        print('Completed non-sequential bundle', chunk, 'of', steps)

and called like this:
  for idx in prange(n):
      # numba no object mode can only handle basic printing
      # note that progress bar adds a performance penalty
      if not suppress_progress:
          progress_bar(idx, n, steps)

Thanks for the suggestion @songololo! I've just pushed some changes (see commit:9c6ca6f
) to implement the suggested progress monitoring, here's an example of the output with --verbose option set to enable progress monitoring:
$ pecanpy --input karate.edg --output karate.emd --dimensions 8 --workers 4 --verbose

Took 00:00:00.00 to load graph
Took 00:00:00.00 to pre-compute transition probabilities
Thread #  3 progress: |###                      | 9.41 %
Thread #  0 progress: |###                      | 9.41 %
Thread #  1 progress: |###                      | 9.41 %
Thread #  2 progress: |###                      | 9.41 %
Thread #  3 progress: |#####                    | 18.82 %
Thread #  1 progress: |#####                    | 18.82 %
Thread #  2 progress: |#####                    | 18.82 %
Thread #  0 progress: |#####                    | 18.82 %
Thread #  3 progress: |########                 | 28.23 %
Thread #  1 progress: |########                 | 28.23 %
Thread #  2 progress: |########                 | 28.23 %
Thread #  0 progress: |########                 | 28.23 %
Thread #  3 progress: |##########               | 37.64 %
Thread #  1 progress: |##########               | 37.64 %
Thread #  2 progress: |##########               | 37.64 %
Thread #  3 progress: |############             | 47.05 %
Thread #  1 progress: |############             | 47.05 %
Thread #  0 progress: |##########               | 37.64 %
Thread #  2 progress: |############             | 47.05 %
Thread #  3 progress: |###############          | 56.47 %
Thread #  1 progress: |###############          | 56.47 %
Thread #  2 progress: |###############          | 56.47 %
Thread #  0 progress: |############             | 47.05 %
Thread #  3 progress: |#################        | 65.88 %
Thread #  1 progress: |#################        | 65.88 %
Thread #  2 progress: |#################        | 65.88 %
Thread #  3 progress: |###################      | 75.29 %
Thread #  1 progress: |###################      | 75.29 %
Thread #  0 progress: |###############          | 56.47 %
Thread #  2 progress: |###################      | 75.29 %
Thread #  1 progress: |######################   | 84.7 %
Thread #  3 progress: |######################   | 84.7 %
Thread #  0 progress: |#################        | 65.88 %
Thread #  2 progress: |######################   | 84.7 %
Thread #  1 progress: |######################## | 94.11 %
Thread #  3 progress: |######################## | 94.11 %
Thread #  2 progress: |######################## | 94.11 %
Thread #  0 progress: |###################      | 75.29 %
Thread #  0 progress: |######################   | 84.7 %
Thread #  0 progress: |######################## | 94.11 %
Took 00:00:05.70 to generate walks
Took 00:00:00.03 to train embeddings

I guess the couple other things that I'll do right after is to add progress bar to the preprocessing phase for PreComp mode. I'll also try to see if using the latest Numba release would allow me to use objmode to enable flushing to make the printing prettier.

Interesting approach! Thanks for sharing.

https://github.com/mortacious/numba-progress


Wrong link the deployment doc

Bug Report

General Information
In the deployment file self-managed k8s is redirecting to the deployment page itself.
To Reproduce
I think it should redirect here

@Amishakumari544  what the url about deployment file self-managed k8s


Text widget annotations: support read-only/multiline fields and improve testing

This pull request is a part of #7613 and completes the support for text widget annotations. More details are provided in the commit messages.

As a follow-up PR, I think that we should get rid of PDFJS.renderInteractiveForms as soon as possible.
In hindsight we should not have added it in the first place, since using these global variables is making it more difficult to have multiple PDFJS instances running at the same time.
Considering that the intention is to remove these global variables in the future, we really shouldn't be adding any more of them at this time!
Since we've only just added PDFJS.renderInteractiveForms, and considering that it's not used by default yet, I think that we should remove it as soon as possible.
Instead, let's pass in renderInteractiveForms to PDFViewer/PDFPageView/AnnotationLayerBuilder from app.js in the same way as we currently do with enhanceTextSelection.
I'll happily review a follow-up PR that fixes this :-)

I have added a note to the tracking issue about removing the global.

/botio-linux preview

/botio test

I verified that the test failure above is correct. This field is actually a multiline text field that is positioned one pixel below the other field next to it. Now that this is supported, we notice this. Comparing a screenshot from the Adobe Reader rendering to the new PDF.js rendering shows that it is the same now.
/botio makeref


Delete unavailable package version

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

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

Microsoft Reviewers: Open in CodeFlow

8:50:23: NordSecurity.NordPass prVersion 5.2.12 is less than ManifestVersion 5.3.15


3.5.1 build fails with fPIC linker error

Hi,
first off, I  have to wonder about your lax attitude here.
This bug was closed without so much as a snarky remark by akallabeth.
I suggest you fix this asap, as the build currently fails with freerdp 3.5.1 and gstreamer 1.24.3 due to your referring to a static gstreamer lib built without PIC.
You either have to coordinate with gstreamer or provide your own compatible version of libswscale!
why is the build configured to link a .so to a gstreamer .a which might or might not have fPIC enabled?
Debian 12, gstreamer 1.24.3, freerdp 3.5.1
24.96 [ 77%] Linking C shared library libfreerdp3.so
47.62 /usr/bin/ld: /opt/gst/lib64/libswscale.a(libswscale_x86_swscale.c.o): warning: relocation against ff_M24B' in read-only section .text'
47.69 /usr/bin/ld: /opt/gst/lib64/libswscale.a(libswscale_x86_swscale.c.o): relocation R_X86_64_PC32 against symbol `ff_M24A' can not be used when making a shared object; recompile with -fPIC
47.69 /usr/bin/ld: final link failed: bad value
47.73 collect2: error: ld returned 1 exit status
47.74 make[2]: *** [libfreerdp/CMakeFiles/freerdp.dir/build.make:2857: libfreerdp/libfreerdp3.so.3.5.1] Error 1
47.74 make[1]: *** [CMakeFiles/Makefile2:2836: libfreerdp/CMakeFiles/freerdp.dir/all] Error 2
47.75 make: *** [Makefile:156: all] Error 2

well, this is your issue and you still fail to provide information that might help us to find out what you did wrong.

duplicate https://github.com/FreeRDP/FreeRDP/issues/10188


templates: Enforce a Zulip-specific standard for hr/br tags.

@andersk thoughts on the policy change proposed here?

I think I would prefer to have something that lets us run our templates through the real HTML validator (we could even use the coverage data that #13941 lets us collect), instead of collecting ad-hoc rules derived without reference to the specification.
There’s nothing wrong with
 and
, and nothing different or legacy about  and <input />. The actual rule is that there are 14 void elements (including all of the above) for which the self-closing syntax is optional and an end tag is forbidden, while for other elements the self-closing syntax is forbidden and an end tag is either required or implied.

I think I would prefer to have something that lets us run our templates through the real HTML validator (we could even use the coverage data that #13941 lets us collect), instead of collecting ad-hoc rules derived without reference to the specification.

The main purpose of this tool is to produce consistent formatting of the template source code.  We should also validate HTML that gets produced from these templates, where possible; I don't see those as mutually exclusive goals.

There’s nothing wrong with
 and
, and nothing different or legacy about  and <input />.

The "legacy" refers to our codebase, not any external requirement.  The "legacy" in the comments refers to the fact that we use <input ... /> in lots of places.
I'm fine with backing out the ''/'<br' changes, although I think there's some value in having them consistently be the concise form, just so folks don't wonder why we're inconsistent about it.

@timabbott I responded to the comments here, and I also split out the biggest commit (for HR/BR tags).
Hopefully the first three commits here are no-brainers to merge.
The fourth commit addresses this inconsistency in our codebase:
(zulip-py3-venv) ~/zulip (master)$ git grep '
' templates/zerver | wc -l
11
(zulip-py3-venv) ~/zulip (master)$ git grep '
' templates/zerver | wc -l
21
(zulip-py3-venv) ~/zulip (master)$ git grep '
' templates/zerver | wc -l
11

I merged the prep commits.  I'm fine with making a consistent choice about how to write hr and br tags for codebase consistency reasons as it can help with readability; but I'm actually not sure which style is preferred; we should make sure we're switching to whatever that is.

@timabbott Here are the results of the poll where I asked people whether they prefer
 or

More discussion here: https://chat.zulip.org/#narrow/stream/6-frontend/topic/.3Chr.3E.20tags/near/862384
My recommendation:

enforce the concise forms for
 and

be unopinionated for SVG tags (since you often copy/paste them)
punt on any changes related to img/input for now

I'm fine with that proposal.

But really I'd describe this as unimportant and easy to change later; it's not common formatting for us in any case.

(Does this PR do what that proposal says?)

Yes this pr implements my proposal...I should have made that more explicit.

Merged, thanks @showell!


juggle.py: timeless routes not supported

Describe the bug
When providing a timeless route, we get a panic. This comes from timeless routes being introduced from this PR https://github.com/commaai/openpilot/pull/31119
(openpilot-py3.11) ➜  plotjuggler git:(master) ✗ ./juggle.py "4203853bc02e087a/0000004e--2f809c6660/0"
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:1002)'))': /4203853bc02e087a/None/0/rlog.bz2
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:1002)'))': /4203853bc02e087a/None/0/rlog.bz2
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:1002)'))': /4203853bc02e087a/None/0/rlog.bz2
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:1002)'))': /4203853bc02e087a/None/0/rlog.bz2
Traceback (most recent call last):
  File "/home/mau/Dev/openpilot/tools/plotjuggler/./juggle.py", line 133, in <module>
    juggle_route(route_or_segment_name, args.can, args.layout, args.dbc)
  File "/home/mau/Dev/openpilot/tools/plotjuggler/./juggle.py", line 79, in juggle_route
    sr = LogReader(route_or_segment_name, default_mode=ReadMode.AUTO_INTERACTIVE)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mau/Dev/openpilot/openpilot/tools/lib/logreader.py", line 256, in __init__
    self.reset()
  File "/home/mau/Dev/openpilot/openpilot/tools/lib/logreader.py", line 279, in reset
    self.logreader_identifiers = self._parse_identifiers(self.identifier)
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mau/Dev/openpilot/openpilot/tools/lib/logreader.py", line 239, in _parse_identifiers
    identifiers = source(sr, mode)
                  ^^^^^^^^^^^^^^^^
  File "/home/mau/Dev/openpilot/openpilot/tools/lib/logreader.py", line 191, in auto_source
    raise Exception(f"auto_source could not find any valid source, exceptions for sources: {exceptions}")
Exception: auto_source could not find any valid source, exceptions for sources: [MaxRetryError("HTTPSConnectionPool(host='data-raw.comma.internal', port=443): Max retries exceeded with url: /4203853bc02e087a/None/0/rlog.bz2 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: EE certificate key too weak (_ssl.c:1002)')))"), AssertionError(), UnauthorizedError('Unauthorized. Authenticate with tools/lib/auth.py'), AssertionError()]

[ ] Update docs to have timeless routes
[ ] Should still support both route id versions (maybe?)

OS Version
Ubuntu 20.04
openpilot version or commit
c95404d564a9a8d168f8f587887e9c33f96db861
Additional info
No response

The new format is supported. Your route is likely just missing rlogs being uploaded. Add "/q" at the end if you want the qlogs.


Update fstab.yaml

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--wknd--vvedagiri.hlx.page/
After: https://branch1--wknd--vvedagiri.hlx.page/

Completing the fstab.yaml fix


Issue with the pickle protocol for big images

Hi,
I'm running CellPose on really big images (about 30K x 30K), and I get an error coming likely from the pickle protocol:
Traceback (most recent call last):
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/site-packages/cellpose/__main__.py", line 458, in <module>
    main()
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/site-packages/cellpose/__main__.py", line 342, in main
    io.masks_flows_to_seg(image, masks, flows, diams, image_name, channels)
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/site-packages/cellpose/io.py", line 285, in masks_flows_to_seg
    np.save(base+ '_seg.npy',
  File "<__array_function__ internals>", line 5, in save
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/site-packages/numpy/lib/npyio.py", line 529, in save
    format.write_array(fid, arr, allow_pickle=allow_pickle,
  File "/home/groups/graylab_share/OMERO.rdsStore/thibaulg/Python/Python38_Test/lib/python3.8/site-packages/numpy/lib/format.py", line 680, in write_array
    pickle.dump(array, fp, protocol=3, **pickle_kwargs)
OverflowError: serializing a bytes object larger than 4 GiB requires pickle protocol 4 or higher

Is there a workaround?
I run CellPose on a cluster running on CentOS with Slurm, on P100 or V100 GPUs with 700Go or RAM.

I was having the same error on mesoscale datasets until I disabled npy output with --no_npy.


Plz support definition for typescript users

I could not use it at all because of one of my compilation options
So I made it myself. I hope others don't have the same issues as me.
import { Locale } from 'locale';

export declare module 'locale' {
  interface Locale {
    code: string;
    language: string;
    country: string;
    normalized: string;
    score: number;
  }
  declare function Locales(language: string): Locale[];
}

Hi there, I don't use TypeScript at all but is there anything the repo could include to better support it?

You can also submit a PR to https://github.com/DefinitelyTyped/DefinitelyTyped/

I wrote one https://github.com/DefinitelyTyped/DefinitelyTyped/pull/42968


Custom colors

Hello,
Thank you for creating this! I was wondering how I can add custom colors?

Good timing, I ran into this problem well. Currently this addon uses Tailwind default theme colors with no ability to add your own.
What you can do instead and what I did is add this addon to your project locally and make changes to it how you want.
https://statamic.dev/extending/control-panel#adding-css-and-js-assets
https://statamic.dev/extending/bard#prosemirror-rendering
Just copy the source files, register the service provider in config/app.php by adding service provider class in providers array.
ServiceProvider.php (original will work as well I think)
class ServiceProvider extends AddonServiceProvider
{
    public function boot() {
        parent::boot();
        Augmentor::addMark(TextColor::class);
        Statamic::script('textcolor', 'textcolor.js');
    }
}

For JS part, copy the files but to add your own colors, modify TextColorMenu.vue
I swapped out default Tailwind theme to parse my own Tailwind theme with my own colors. Tailwind can help reference your theme easily. https://tailwindcss.com/docs/configuration#referencing-in-java-script
So I have something basic like this:
import resolveConfig from 'tailwindcss/resolveConfig'
import tailwindConfig from '../../../tailwind.config.js'

const resolvedConfig = resolveConfig(tailwindConfig)
const colors = resolvedConfig.theme.colors

export default {
  mixins: [ BardToolbarButton ],
  data() {
    return {
      showColorMenu: false,
      availableColors: colors,
      getMarkAttrs: this.editor.getMarkAttrs.bind(this.editor),
    };
  },
  methods: {
    setColor(color) {
      this.editor.commands.textColor({ color: color })
      this.showColorMenu = false
    },
  },
  mounted: function() {
    // this probably can be done better but I just wanted to add single color
    this.availableColors = Object.assign({highlight: '#C50B67'}, this.availableColors);
  }
};

Most problematic was sorting out compiling the JS / Vue part. I am using Laravel Mix 6. Make sure you have these things installed to have it compile.
"vue-loader": "^15.9.5",
"vue-template-compiler": "2.6.14"
"vue": "^2.6.14"

and in webpack.mix.js
.vue() // this is important
.js('resources/js/textcolor/bard.js', 'public/vendor/textcolor/js/textcolor.js')

and you may have to change how you import the files, depending how is your project configured.
import TextColor from "./TextColor.js"; // with file extension
import TextColorMenu from "./TextColorMenu.vue";

Thanks for posting this issue.
I'll be looking into adding custom colors into the official package.
Thank you!

Okay so I've released a v2 of the package thinking it was okay, only to realise it was only working fine for my project.
I can't figure how to load the tailwind.config.js file dynamically from the project that it's installed on, or attach it to webpack to at least build it when you build your project (run dev/watch/prod).
Got any ideas?
I've tried pretty much everything and I'm out :(

@xndbogdan
I do not have a solution but personally I would be okay if I could just pass my own colors through PHP config file. For my use case that would be fine as I only realistically need just one color to have a design specific color highlighting. This package does not have to limit itself to just Tailwind colors.
The current solution should work but yeah you need to figure out the dynamic import part. Maybe passing the Tailwind config from PHP side to Vue component prop could work.
Could maybe ask around on Statamic Discord server, people there are helpful and nice.

I released a new version that should support custom colors via config file.
Please confirm that it works well for you.

Hey,
I just tested this and it seems to be reading the color correctly from config file. I see that you were able to get help in #extending channel on Discord. Pretty simple solution.
Thanks!

I'm glad it's working good for you.


Data doubts

Remove the
A clickable icon and text saying ""DATA DOUBTS" below

( the bubble chart has doubt in the lower right corner.

Color:

When clicked it opens a modal panel in front of the chart with a custom text (one text for income mountain and one for bubble chart )
Some thing like this (Allowing links in the text)

FYI: In the future this feature will be more advanced and allow users to quickly see a quantified measure of our doupts. If we believe te data might be 20% wrong, that will display in the chart, when clicking the button. We need a second column in the data next to every indicator, that displays the doupt as a numeric value between 0 and 100 ) The text will thne be a more info about the doubts levels .

Icon in svg : http://www.flaticon.com/free-icon/warning-sign-on-a-triangular-background_25411


omitempty restources

see the origin of the discussion https://github.com/gdg-garage/space-tycoon/pull/40#discussion_r937650690

This indicates that it is omitted in the json right? It is still present in the classes/structs in the generated code?

In Go, the omitted fields are filed with default values (0 for ints/numbers, "" for strings, etc.).
In Python, I would expect the generated code to just not add the missing fields to the object.
If the omitted values are replaced with defaults in all languages (Go style) then I think that using omitempty works. But if some clients end up with fileds being omitted in the objects then I think we should not use "omitempty".
Btw does our swagger spec allow omitted damage and cargo capacity?

https://github.com/go-swagger/go-swagger/issues/1707

Works nicely in the end. Used in https://github.com/gdg-garage/space-tycoon/pull/57

Works nicely in the end. Used in #57

I would not call that solution "nice". I would call that a dirty workaround. But such is the world we live in...

You need a way to tell if something is present or not. Something like
optional. Pointer works nicely for that. I do not see nullable as a hack at
all. Why do you?
Omitempty is also needed in parts of our api, it is just not great as a
default :/
On Sat, 6 Aug 2022, 19:58 Tomáš Malý, @.***> wrote:

Works nicely in the end. Used in #57
https://github.com/gdg-garage/space-tycoon/pull/57
I would not call that solution "nice". I would call that a dirty
workaround. But such is the world we live in...
—
Reply to this email directly, view it on GitHub
https://github.com/gdg-garage/space-tycoon/issues/53#issuecomment-1207256006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZ4LI2HEWZKJ5NFBYTJZP3VX2RVZANCNFSM55T545KQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

In swagger you define what is optional or required by listing required things in the required clause.
Changing the semantics of the declarations just to change some behavior in the generated code is wrong.
But the actual issue is in the design of the swagger. Nullable should have been an option of the generator and not part of the document.


Invoke-PaginateResults is breaking and not sending all the results back

In PSSailpoint>1.0.2>Pagination.ps1>function invoke-PagnateSearch, looks like a bug.

if the $Result.length  is less than the $Increment it's breaking.
However there can be results. e.g. paging by 50, and there were 1 - 49 results.
it's throwing those away by breaking out of the while loop without adding the remaining items.
I added the last result to the total results before the break and it now returns all results
        if($Result.Length -lt $Increment) {
            $Results += $Result
            break
        }

        $Results += $Result
        $InitialOffset += $Increment;

Hello @rob-buskens-sp, good catch! This is fixed by https://github.com/sailpoint-oss/powershell-sdk/pull/10 and will be included in the next release!


Update to Swift 4.1 and dependencies

Codecov Report

Merging #250 into master will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #250      +/-   ##
==========================================
- Coverage   74.86%   74.74%   -0.12%
==========================================
  Files          31       31
  Lines        4181     4181
==========================================
- Hits         3130     3125       -5
- Misses       1051     1056       +5

Flag
Coverage Δ

#CHTTPParser
57.52% <ø> (ø)
:arrow_up:

#KituraNet
74.74% <ø> (-0.12%)
:arrow_down:

Impacted Files
Coverage Δ

...ces/KituraNet/Server/ServerLifecycleListener.swift
79.16% <0%> (-4.17%)
:arrow_down:

Sources/KituraNet/HeadersContainer.swift
96.72% <0%> (-3.28%)
:arrow_down:

Sources/KituraNet/HTTP/HTTPServer.swift
79.88% <0%> (-1.12%)
:arrow_down:

Continue to review full report at Codecov.

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


Rich Changelog generation

Description
Example Changelog from current configuration in comment
Related issue(s)
https://github.com/kyma-project/serverless/issues/388

for github_changelog_generator -u kyma-project -p serverless -t ${{ secrets.GITHUB_TOKEN }} --enhancement-labels kind/feature,area/ci  --bug-labels kind/bug --future-release ${{ github.event.inputs.name }} --unreleased-only
Changelog
3.0.0 (2023-11-06)
Full Changelog
Implemented enhancements:

Propose changes in conditions #221
State calculation based on conditions #220
Support native dockerconfigjson secrets when configuring docker registry for serverless #121
namespaced scope secrets warning #382 (pPrecel)
Align the default Serverless name to the agreed format #376 (grego952)
Move github actions scripts to .github/scripts #357 (MichalKalke)
Move serverless-manager config files to config/operator #350 (MichalKalke)

Fixed bugs:

Fix dependency code editor configuration #391 (kwiatekus)

Closed issues:

Warn user when serverles-registry-config is used #383
Document how to configure custom docker registry per registry provider #381
serverless integration tests are flaky #359
Move resource profiles defaulting from mutating webhook to function controller. #248
[rl-reuse_tool-3] Violation against OSS Rules of Play #215
[rl-reuse_tool-1] Violation against OSS Rules of Play #214
[rl-security_policy-1] Violation against OSS Rules of Play #213
[rl-reuse_tool-2] Violation against OSS Rules of Play #212
[rl-vulnerability_alerts-1] Violation against OSS Rules of Play #211
Adjust retryable module deletion timing #87
Investigate how to test serverless module on multiple hyperscallers  #45

Merged pull requests:

Fix formatting #395 (grego952)
add gcr and acr examples #392 (grego952)
Remove additional make targets with -operator sufix #390 (MichalKalke)
unify quotation in doc #386 (anoipm)
Remove module chart #385 (MichalKalke)
Adjust go.mod, go.sum, Dockerfile, makefiles to new structure #379 (MichalKalke)
Temporary copy module-chart also to components/operator #378 (MichalKalke)
Provide sample python function #377 (kwiatekus)
add simple for secretMount validation #375 (dbadura)
Add collect logs script to serverless integration tests #374 (dbadura)
Add source validation #372 (dbadura)
Copy internal to components/operator #371 (MichalKalke)
Move internal, controllers and main to components/operator #370 (MichalKalke)
Update deps #369 (dbadura)
Add onError loggers and fix proxy mock #368 (dbadura)
Add env names validation #367 (dbadura)
Copy api to components/operator #366 (MichalKalke)
Add runtime validation #365 (dbadura)
Add annotations validation #364 (dbadura)
Add labels validation #363 (dbadura)
Reaarange test cases #362 (dbadura)
Move api to components/operator #361 (MichalKalke)
Upgrade k8s deps #356 (dbadura)
Extract testenv #355 (dbadura)
Improve flag builder impl #353 (dbadura)
Reflect used presets in status #351 (pPrecel)
Add first version of x-kuberneets impl with unit tests #338 (dbadura)

* This Changelog was automatically generated by github_changelog_generator


Search on landing page shows loading forever

Reproduced in Firefox and Chrome.

Thanks @udp for the help!


abTestName key not found

With 2.3.1 i get this error. It seems that _Keys.abTestName is null for my paywall (free user):
[AdaptyFlutter v2.3.1] - VERBOSE: --> Adapty.identify()
[AdaptyFlutter v2.3.1] - VERBOSE: --> Adapty.get_paywall()
[AdaptyFlutter v2.3.1] - VERBOSE: <-- Adapty.identify()
[AdaptyFlutter v2.3.1] - VERBOSE: <-- Adapty.get_paywall()
┌──────────────────────────────────────────────────────────────────────────
│ type 'Null' is not a subtype of type 'Map<String, dynamic>' in type cast
├┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
│ #0   MapExtension.object (package:adapty_flutter/src/models/private/json_builder.dart:45:56)
│ #1   AdaptyPaywallJSONBuilder.fromJsonValue (package:adapty_flutter/src/models/private/adapty_paywall_json_builder.dart:27:29)
│ #2   Adapty.getPaywall (package:adapty_flutter/src/adapty.dart:101:37)
│ #3   <asynchronous suspension>
│ #4   PaywallMiddleware._showPaywall (package:sleeptales_app/usecase/paywall/paywall_middleware.dart:22:29)
│ #5   <asynchronous suspension>
├┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
│ ⛔ Manual BugSnag Notification
└───────────────────────────────────────────────────────────────────────────

Hey, @tonbert! Could you specify on which platform the error occurred, iOS or Android?

It was iOs on iPhone 14 Pro and the local simulator as well. I added an empty default string to abTestName and it worked again. It seems like this data should be nullable

@tonbert could you please clarify, what do you mean by "I added an empty default string to abTestName"?
When you create an ab-test, this field is required (see screenshot).

I also do not fully understand why you think that the problem was exactly in the abTestName parameter, while the stackTrace error points to another location.
May I ask you to describe your steps in a little more detail, as well as attach the verbose log from the Flutter SDK and iOS SDK?

The class declaration in the adapty_paywall.dart file states that the abTestName field is not nullable. However, since I am Free free user I cannot create AB tests. The json data from Adapty when querying the paywall sends no or a null abTestName field. That's why it crashes on deserialization.

The point is that the ab_test_name field is actually required and should always be present, even if the paywall is not an AB-test. So I don't think your plan is the problem.
I suppose our next steps should be this:

Send me as a email your Company name and a email address, to which the account is registered;
Add the full verbose log that comes from Adapty-Flutter and Adapty-iOS so that we can see all the errors that occur during the process;
"I added an empty string so that the deserialization works" – please attach a code snippet, where exactly did you add this?


Write forward algorithm in C

Doesn't seem necessary at this time since the forward algorithm is very fast.