Update Layer Names in Profile Popout Menu

Description
This issue focuses on updating the names of the three Layers of UnlockEd as they appear in the profile popout menu on the lower left-hand side of the page (at the bottom of the sidebar navigation). The current names are functional but not intuitive for end users. This task updates the Layer names to ensure they are more user-friendly and aligned with the product’s overall purpose.
Current Names:

Layer 1: Knowledge Center
Layer 2: Provider Platform Integrations
Layer 3: Program Management

Updated Names:

Layer 1: Knowledge Base
Layer 2: Connected Learning
Layer 3: Program Hub

These updates reflect clearer, more user-friendly terms while retaining the core meaning of each Layer.
Task List

[x] Update the profile popout menu to display the new Layer names:

Change "Knowledge Center" to "Knowledge Base".
Change "Provider Platform Integrations" to "Connected Learning".
Change "Program Management" to "Program Hub".

[x] Ensure the new names are styled consistently with the existing design and do not break the layout.
[x] Check if the Layer names are stored or referenced in backend configurations or APIs.
[x] Update any backend logic or configurations referencing the old names, if applicable.

Acceptance Criteria

Frontend:

The profile popout menu displays the updated Layer names:

Layer 1: Knowledge Base
Layer 2: Connected Learning
Layer 3: Program Hub

Backend (if applicable):

Any backend references to Layer names are updated to match the new terms.
The name changes do not impact the functionality or navigation for any Layers.

Outstanding Questions

Are there any other areas of the product (e.g., tooltips, documentation) where these Layer names appear and need to be updated?

closed with #536


Federated Store logs wrong field when getting delegate store status

The FederatedStore logs a delegate stores status description, rather than the status in checkDelegateStoreStatus(). Correct this so that it logs the status.

Merged into develop


Formatter fails if there's a line comment following a delay

Test case
task t;
  #20
  //test
  x = 1;
endtask

Actual output
task t;
    #20
    //test
    x = 1;
endtask
test_case.sv: Error lex/parsing-ing formatted output.  Please file a bug.
First error: token: "endtask" at 3:1-7:; problematic formatter output is
task t;
  #20  //test    x = 1;
endtask
<<EOF>>

Expected or suggested output
task t;
  #20
  //test
  x = 1;
endtask

I guess this issue can be closed?

Thanks for pointing it out. As stated in the PR the indentation is still wrong but indeed it does not fail.


Updates to LICENSE and NOTICE

What changes were proposed in this pull request?
LICENSE and NOTICE changes as per ASF policy
How was this patch tested?
N/A
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

ok to test

Test build #92199 has started for PR 21610 at commit b9d12d7.

Test build #92199 has finished for PR 21610 at commit b9d12d7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92199/
Test FAILed.

Is this patch trying to make this into LICENSE/NOTICE appropriate for a source release? then they wouldn't work for a binary release. Maybe we can

address any gaps in the binary release version
simplify it as some of your suggested changes maybe I didn't know we could do, and
clone and chop it down for a source release version
modify release scripts to use the right one

We can do the last one separately, even second to last, but would like to capture the fixes parts here if possible and get those in.

Yes it 's trying to correct if for the source release. As per the guiding principle [1] the LICENSE and NOTICE needs to represent what in the release this often mean you get different LICENSE and NOTICE files. [2]
I think the above steps sound fine. It looks like there a couple of things are missing (the licenses I've added) and there's license info in the NOTICE file that should be in LICENSE.

http://www.apache.org/dev/licensing-howto.html#guiding-principle
http://www.apache.org/dev/licensing-howto.html#binary

Test build #92252 has started for PR 21610 at commit ddb32e5.

Test build #92252 has finished for PR 21610 at commit ddb32e5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92252/
Test PASSed.

You'll note on that link you give that public domain or CC0 licenced bits
should be treated the same way as other permissive licenced software like
MIT or BSD. i.e you add the text of the license (or a pointer to it) to the
LICENCE file.
On Tue., 26 Jun. 2018, 8:12 am Sean Owen<EMAIL_ADDRESS>wrote:

@srowen commented on this pull request.
@justinmclean https://github.com/justinmclean have a look at my attempt
at #21640 https://github.com/apache/spark/pull/21640 which I hope takes
care of these and more issues. It's a complete overhaul.
In licenses/LICENSE-kittens.txt
https://github.com/apache/spark/pull/21610#discussion_r197957062:

@@ -0,0 +1,121 @@
+Creative Commons Legal Code

Do we need this? CC0 is treated like public domain, as per
http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products
. I found the image online that prompted this and it's also described as
public domain.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/21610#pullrequestreview-131801721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAI0eBI1VcUoXlASoB7POK1fQNIIIWtHks5uAWBigaJpZM4UzH3I
.

Oh I missed this: "Attribution is required (in a similar fashion to permissive licenses)." Hm, I wonder why (other than being nice). But it's easy enough to revise this to attribute several other public domain deps.

Just to be clear it's not dependancies that need to be listed only what is actually bundled in the release artefact.

Certainly. I'm saying that these are nearly the same thing, because the binary release is, mostly, a collection of compiled Spark code and all its transitive dependencies. This is why it's correct to start from that list. It's not 100% what makes it into the release: some bundled code doesn't show up this way (shaded stuff). It also bears some manual sense checking. But it appeared to give the correct list of dependencies.

Nope they are not. It's best to inspect the binaries by hand and see what is actually bundled.

Justin can you be more specific? I'm looking at our last binary release and it certainly has (what appear to be) all of Spark's transitive dependencies in jars/. What are you seeing?

BTW I think this can be closed. I separately overhauled the LICENSE/NOTICE.


cmd/gitcheckout: run git config with repo path

Also fix https git repo parsing
Part of: NSL-3898

LGTM


Setup Docker container and Nix Flake

The docker image is currently under ghcr.io/fhilgers/ziofa-builder. We should look into whether we can host it under the project namespace.
You can now pull the docker image: docker pull ghcr.io/fhilgers/ziofa-builder:latest.
We should also wait for the license setup before merging (#18).
Closes #11.

Android 13 and aarch64-linux android target for rust was added.


Authenticating with Azure using Certificate

I am trying to authenticate with Azure Active Directory using Certificate. I get following error when I try authentication using SDK
Authorizer failed: failed to get oauth token from certificate auth: failed to decode pkcs12 certificate while creating spt: pkcs12: expected exactly two safe bags in the PFX PDU
Same certificate works if I use powershell commandlet to login to azure.
Code Link
There is one more concern I like to raise - Golang SDK forces to provide the certificate in pfx format where as Login-AzureRmAccount powershell commandlet not only works with certificate without private key but also only requires certificate thumbprint. Why is there a discrepancy in the API for different languages?

Hi @udbhav-sharma  I've tagged this bug so that the right team member can take a look.

Is there a update?

@jhendrixMSFT Hi would you please check if this is related with auth in go-autorest?

Yes this is from the adal package in go-autorest.  Do you have a code sample how you're using the API?

Thanks.  We use pkcs12.Decode() to extract the cert/private key which expects there to be only one cert/private key pair in the data.  How are you creating the cert?
Regarding authentication with certificate thumbprint I've opened https://github.com/Azure/go-autorest/issues/468 to track it.

Hi @jhendrixMSFT - I'm also seeing similar issue as above while trying to authN with certificate using Go auth SDK: "github.com/Azure/go-autorest/autorest/azure/auth"   NewAuthorizerFromEnvironment()
"Error": "failed to get oauth token from certificate auth: failed to decode pkcs12 certificate while creating spt: pkcs12: expected exactly two safe bags in the PFX PDU"
Wondering if there has been an update for this issue or any workaround to that matter?
Regards.

No update here as we don't have a repro to investigate further.  How was your cert created?

I see. I have generated the cert in the KeyVault with OneCert CA.
In the PEM file, I can see one private key and but 3 certificate sections.

@jhendrixMSFT i'm also hitting the same issue..i created sslcert from azure keyvault. Can you please let us know how you tested it?

Presumably your certificate contains multiple sections too.  Are these intermediate authorities?  I don't have a repro but this is my current assumption.
The guts of this code was written before I joined the Go SDK team.  Presumably the original authors tested it with a cert that contained only the root authority (will try to find more info).

@jhendrixMSFT  Repro steps: create cert issued by ssladmin(choose integrated CA) from azure keyvault and download the pfx file. Then run the above sample code.
No issues with self signed certificate but certificates issued by integrated Authority CA are failing
we should have supporting api to decode pfx data issued by integrated authority CA

I figured out a way. Since it contains more than one cert, we have to use pkscs.ToPEM and then convert to x509 certs.

Thanks for the info, I will try to repro this.  Can you share the code changes you made that fixed it for you?

func decodePkcs12(pkcs []byte, password string) (*x509.Certificate, *rsa.PrivateKey, error) {
blocks, err:= pkcs12.ToPEM(pkcs,password)
if err != nil {
return nil, nil, err
}
    var (
       cert *x509.Certificate
       priv *rsa.PrivateKey
   )

   for _, block := range blocks {
      if block.Type == "CERTIFICATE" {
        if _, ok := block.Headers["localKeyId"]; ok {
          cert, err = x509.ParseCertificate(block.Bytes)
          if err !=  nil {
              fmt.Printf("Error parsing certificate from pem block:%v\n", err)
              continue
          }
        }
      } else if block.Type == "PRIVATE KEY" {
          priv, err = x509.ParsePKCS1PrivateKey(block.Bytes)
          if err != nil {
            fmt.Printf("Error parsing private key from pem block: %v\n",err)
          }
        }
    }

return cert, priv, nil

}``

This has been fixed in autorest/azure/auth/v0.5.1.


HEY i need help with making the RAT or yk, how to get the bot running? My discord is goofycat123 but uh yeah please help, im not a skid, im doing this for a good cause.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 11, Windows 10]
Python Version: [e.g. 3.11.3]

Additional context
Add any other context about the problem here.

Added on Discord.

Can you add  me too my user is erikltu

I will later

alr

Added you


UPD some tests modified to use AddressSpaceList for creating addr-space

atuhService moved into the AddressSpace class
tests rewrited to set authService within address spaces

this PR can be closed without merge because 'issue-1040-reachable-routes' branch is based on this branch. 'issue-1040-reachable-routes' branch will be merged with 'rest-api-tests' branch and then with master


develop soca code failed with exception

Description
After update the soca code to current develop branch, compile and run, got error:
Test     : layer_depth   min=    0.838614   max= 6376.155029   mean=  911.245570
Test     :   cicen   min=    0.000000   max=    1.000000   mean=    0.219001
Test     :   hicen   min=    0.000000   max=    2.472954   mean=    0.240000
Test     :   hsnon   min=    0.000000   max=    0.743529   mean=    0.050114
Exception: InsituTemperature does not exist in ufo::ObsOperatorFactory
Exception: oops::LocalEnsembleDA<SOCA, UFO and IODA observations> terminating...
OOPS Ending   2022-08-02 16:15:34 (UTC-0500)
The yaml file, and run script works fine last week.

—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204043967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH65VP7DEMQEI2ZWDZGDVXKASBANCNFSM55MS7HMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Given the warning, it's acting like UFO can't find GSW when it is compiling, which is weird.

are you able to run the ctests successfully?
can you recursively set read permissions for /work/noaa/gsienkf/weihuang/jedi/src/bld.soca and /work/noaa/gsienkf/weihuang/jedi/src/src.soca so I can see if I can find anything obviously wrong.

Have set permission to: /work/noaa/gsienkf/weihuang/jedi/src/bld.soca and
/work/noaa/gsienkf/weihuang/jedi/src/src.soca
Running ctest now.
On Wed, Aug 3, 2022 at 9:15 AM Travis Sluka @.***>
wrote:

Given the warning, it's acting like UFO can't find GSW when it is
compiling, which is weird.

are you able to run the ctests successfully?
can you recursively set read permissions for
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca and
/work/noaa/gsienkf/weihuang/jedi/src/src.soca so I can see if I can
find anything obviously wrong.

—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204085141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH64Q75ESJYG3PFRVV7DVXKEIDANCNFSM55MS7HMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

most ctest failed for me:
28% tests passed, 785 tests failed out of 1096
See /work/noaa/gsienkf/weihuang/jedi/src/bld.soca/log.ctest
On Wed, Aug 3, 2022 at 9:23 AM Wei Huang - NOAA Affiliate <
@.***> wrote:

Have set permission to: /work/noaa/gsienkf/weihuang/jedi/src/bld.soca and
/work/noaa/gsienkf/weihuang/jedi/src/src.soca
Running ctest now.
On Wed, Aug 3, 2022 at 9:15 AM Travis Sluka @.***>
wrote:

Given the warning, it's acting like UFO can't find GSW when it is
compiling, which is weird.

are you able to run the ctests successfully?
can you recursively set read permissions for
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca and
/work/noaa/gsienkf/weihuang/jedi/src/src.soca so I can see if I can
find anything obviously wrong.

—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204085141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH64Q75ESJYG3PFRVV7DVXKEIDANCNFSM55MS7HMQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@weihuang-jedi for future reference, you can just cd to the soca dir and run ctest there to not have to run all the JEDI ctests.
The ctests (mostly) work for me with the compiler you note using. I would recommend deleting your src and build directories and trying to rebuild. There seems to be something odd with your build/environment

I will do a fresh checkout and then a fresh build.
On Wed, Aug 3, 2022 at 10:25 AM Travis Sluka @.***>
wrote:

@weihuang-jedi https://github.com/weihuang-jedi for future reference,
you can just cd to the soca dir and run ctest there to not have to run
all the JEDI ctests.
The ctests (mostly) work for me with the compiler you note using. I would
recommend deleting your src and build directories and trying to rebuild.
There seems to be something odd with your build/environment
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204190973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH65WJ47BRQKS5CEBXYTVXKMQRANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

After a fresh checkout and build, run ctest in soca directory, got:
Label Time Summary:
executable    =  27.78 secproc (21 tests)
mpi           = 196.02 secproc (67 tests)
script        = 170.75 secproc (48 tests)
soca          = 198.53 secproc (69 tests)
Total Test time (real) = 200.39 sec
The following tests FAILED:
3 - test_soca_convertstate (Failed)
8 - test_soca_static_socaerror_init (Failed)
9 - test_soca_static_socaerrorlowres_init (Failed)
12 - test_soca_enspert (Failed)
13 - test_soca_sqrtvertloc (Failed)
23 - test_soca_errorcovariance (Failed)
24 - test_soca_linearmodel (Failed)
36 - test_soca_ensvariance (Failed)
39 - test_soca_ensrecenter (Failed)
40 - test_soca_hybridgain (Failed)
45 - test_soca_dirac_soca_cov (Failed)
46 - test_soca_dirac_socahyb_cov (Failed)
47 - test_soca_dirac_horizfilt (Failed)
48 - test_soca_dirac_soca_mask (Failed)
49 - test_soca_dirac_soca_nomask (Failed)
50 - test_soca_hofx_3d (Failed)
51 - test_soca_hofx_4d (Failed)
53 - test_soca_enshofx (Failed)
54 - test_soca_3dvar_soca (Failed)
55 - test_soca_3dvar_single_ob (Failed)
56 - test_soca_3dvarbump (Failed)
57 - test_soca_3dvar_godas (Failed)
58 - test_soca_addincrement (Failed)
59 - test_soca_convertincrement (Failed)
60 - test_soca_3dvarlowres_soca (Failed)
62 - test_soca_3dvarfgat (Failed)
63 - test_soca_3dvarfgat_pseudo (Failed)
64 - test_soca_3dhyb (Failed)
65 - test_soca_3dhybfgat (Failed)
66 - test_soca_letkf (Failed)
67 - test_soca_letkf_split_observer (Failed)
68 - letkf_split_observer_post (Failed)
69 - test_soca_letkf_split_solver (Failed)
70 - test_soca_checkpointmodel (Failed)
Errors while running CTest
Output from these tests are in:
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca/soca/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases
verbosely.
On Wed, Aug 3, 2022 at 10:43 AM Wei Huang - NOAA Affiliate <
@.***> wrote:

I will do a fresh checkout and then a fresh build.
On Wed, Aug 3, 2022 at 10:25 AM Travis Sluka @.***>
wrote:

@weihuang-jedi https://github.com/weihuang-jedi for future reference,
you can just cd to the soca dir and run ctest there to not have to run
all the JEDI ctests.
The ctests (mostly) work for me with the compiler you note using. I would
recommend deleting your src and build directories and trying to rebuild.
There seems to be something odd with your build/environment
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204190973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH65WJ47BRQKS5CEBXYTVXKMQRANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

rerun with:
ctest --rerun-failed --output-on-failure | tee log.ctest2
Got:
12% tests passed, 30 tests failed out of 34
Label Time Summary:
executable    =   2.83 secproc (2 tests)
mpi           = 188.53 secproc (33 tests)
script        = 186.78 secproc (32 tests)
soca          = 189.61 secproc (34 tests)
Total Test time (real) = 191.80 sec
The following tests FAILED:
3 - test_soca_convertstate (Failed)
8 - test_soca_static_socaerror_init (Failed)
9 - test_soca_static_socaerrorlowres_init (Failed)
12 - test_soca_enspert (Failed)
13 - test_soca_sqrtvertloc (Failed)
36 - test_soca_ensvariance (Failed)
39 - test_soca_ensrecenter (Failed)
40 - test_soca_hybridgain (Failed)
45 - test_soca_dirac_soca_cov (Failed)
46 - test_soca_dirac_socahyb_cov (Failed)
48 - test_soca_dirac_soca_mask (Failed)
49 - test_soca_dirac_soca_nomask (Failed)
50 - test_soca_hofx_3d (Failed)
51 - test_soca_hofx_4d (Failed)
53 - test_soca_enshofx (Failed)
54 - test_soca_3dvar_soca (Failed)
55 - test_soca_3dvar_single_ob (Failed)
56 - test_soca_3dvarbump (Failed)
57 - test_soca_3dvar_godas (Failed)
58 - test_soca_addincrement (Failed)
59 - test_soca_convertincrement (Failed)
60 - test_soca_3dvarlowres_soca (Failed)
62 - test_soca_3dvarfgat (Failed)
63 - test_soca_3dvarfgat_pseudo (Failed)
64 - test_soca_3dhyb (Failed)
65 - test_soca_3dhybfgat (Failed)
66 - test_soca_letkf (Failed)
67 - test_soca_letkf_split_observer (Failed)
69 - test_soca_letkf_split_solver (Failed)
70 - test_soca_checkpointmodel (Failed)
On Wed, Aug 3, 2022 at 11:37 AM Wei Huang - NOAA Affiliate <
@.***> wrote:

After a fresh checkout and build, run ctest in soca directory, got:
Label Time Summary:
executable    =  27.78 secproc (21 tests)
mpi           = 196.02 secproc (67 tests)
script        = 170.75 secproc (48 tests)
soca          = 198.53 secproc (69 tests)
Total Test time (real) = 200.39 sec
The following tests FAILED:
3 - test_soca_convertstate (Failed)
8 - test_soca_static_socaerror_init (Failed)
9 - test_soca_static_socaerrorlowres_init (Failed)
12 - test_soca_enspert (Failed)
13 - test_soca_sqrtvertloc (Failed)
23 - test_soca_errorcovariance (Failed)
24 - test_soca_linearmodel (Failed)
36 - test_soca_ensvariance (Failed)
39 - test_soca_ensrecenter (Failed)
40 - test_soca_hybridgain (Failed)
45 - test_soca_dirac_soca_cov (Failed)
46 - test_soca_dirac_socahyb_cov (Failed)
47 - test_soca_dirac_horizfilt (Failed)
48 - test_soca_dirac_soca_mask (Failed)
49 - test_soca_dirac_soca_nomask (Failed)
50 - test_soca_hofx_3d (Failed)
51 - test_soca_hofx_4d (Failed)
53 - test_soca_enshofx (Failed)
54 - test_soca_3dvar_soca (Failed)
55 - test_soca_3dvar_single_ob (Failed)
56 - test_soca_3dvarbump (Failed)
57 - test_soca_3dvar_godas (Failed)
58 - test_soca_addincrement (Failed)
59 - test_soca_convertincrement (Failed)
60 - test_soca_3dvarlowres_soca (Failed)
62 - test_soca_3dvarfgat (Failed)
63 - test_soca_3dvarfgat_pseudo (Failed)
64 - test_soca_3dhyb (Failed)
65 - test_soca_3dhybfgat (Failed)
66 - test_soca_letkf (Failed)
67 - test_soca_letkf_split_observer (Failed)
68 - letkf_split_observer_post (Failed)
69 - test_soca_letkf_split_solver (Failed)
70 - test_soca_checkpointmodel (Failed)
Errors while running CTest
Output from these tests are in:
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca/soca/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases
verbosely.
On Wed, Aug 3, 2022 at 10:43 AM Wei Huang - NOAA Affiliate <
@.***> wrote:

I will do a fresh checkout and then a fresh build.
On Wed, Aug 3, 2022 at 10:25 AM Travis Sluka @.***>
wrote:

@weihuang-jedi https://github.com/weihuang-jedi for future reference,
you can just cd to the soca dir and run ctest there to not have to run
all the JEDI ctests.
The ctests (mostly) work for me with the compiler you note using. I
would recommend deleting your src and build directories and trying to
rebuild. There seems to be something odd with your build/environment
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204190973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH65WJ47BRQKS5CEBXYTVXKMQRANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

it would be useful if you look to see why they are failing.
Either run in verbose mode -V or check the existing log /work/noaa/gsienkf/weihuang/jedi/src/bld.soca/soca/Testing/Temporary/LastTest.log for one of the tests.
I do not have permission to look at the file myself

Travis,
I have changed the permission.
You may also check:
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca/soca/log.test_soca_letkf
Which I run:
ctest -R test_soca_letkf -V | tee log.test_soca_letkf
and have error as:
66: Relative tolerance: 3.4548694513948700e-05
66: Absolute tolerance: 0.0000000000000000e+00
66: Test Line: '   socn   min=10.7210460395083924   max=40.4416591897031168
mean=34.5508108724416090'
66: Ref Line : '   socn   min=10.7210460395083924   max=40.4416591897031168
mean=34.5465781554557978'
66: srun: error: Orion-24-53: task 1: Aborted
66: srun: launch/slurm: _step_signal: Terminating StepId=6357402.0
66: srun: error: Orion-24-52: task 0: Aborted
1/3 Test #66: test_soca_letkf ..................***Failed   19.04 sec
test 67
On Wed, Aug 3, 2022 at 1:28 PM Travis Sluka @.***>
wrote:

it would be useful if you look to see why they are failing.
Either run in verbose mode -V or check the existing log
/work/noaa/gsienkf/weihuang/jedi/src/bld.soca/soca/Testing/Temporary/LastTest.log
for one of the tests.
I do not have permission to look at the file myself
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1204385298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH63VJOYQP4PGFQQYSZTVXLB6XANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@weihuang-jedi The error indicates that your letkf runs successfully, but that references answers do not match exactly. This is because you are using a compiler that we ourselves on the soca team have not used yet. See https://github.com/JCSDA-internal/soca/issues/797

Re-tried with previous compiler, still got:
0% tests passed, 9 tests failed out of 9
Label Time Summary:
mpi       =  81.89 secproc (8 tests)
script    =  81.91 secproc (9 tests)
soca      =  81.91 sec*proc (9 tests)
Total Test time (real) =  82.23 sec
The following tests FAILED:
3 - test_soca_convertstate (Failed)
45 - test_soca_dirac_soca_cov (Failed)
46 - test_soca_dirac_socahyb_cov (Failed)
56 - test_soca_3dvarbump (Failed)
58 - test_soca_addincrement (Failed)
59 - test_soca_convertincrement (Failed)
60 - test_soca_3dvarlowres_soca (Failed)
68 - letkf_split_observer_post (Failed)
69 - test_soca_letkf_split_solver (Failed)
Errors while running CTest
As mentioned, most of the above code run parts passed, but failed at
comparison.
On Fri, Aug 5, 2022 at 9:00 AM Travis Sluka @.***>
wrote:

@weihuang-jedi https://github.com/weihuang-jedi The error indicates
that your letkf runs successfully, but that references answers do not match
exactly. This is because you are using a compiler that we ourselves on the
soca team have not used yet. See #797
https://github.com/JCSDA-internal/soca/issues/797
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1206553550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH62CDXFODUCC4UTQKSLVXUT6PANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@travissluka It seems like soca generates quite different results under different compilers. There is an example here and in the related issue on Chayanne. Any thoughts on what to do about it? Is changing the tolerance an option?

@frolovsa investigate the failure and if this is a tolerance issues, report to @travissluka and ignore ... If you need to replicate the tests exactly, just use the JCSDA singularity container on Orion.

@travissluka It seems like soca generates quite different results under different compilers. There is an example here and in the related issue on Chayanne. Any thoughts on what to do about it? Is changing the tolerance an option?

@frolovsa, yes I'm working on a PR that cleans up the tests. As part of that, tolerances will be fixed, and several of the tests that rely on test_soca_enspert will instead us a pregenerated ensemble. The enspert step seems to be a large source of tolerance issues across compilers.

Re-run with previous compiler with newly cloned, re-built code, still got
same error:
Test     : Initial state for member 80:
Test     :   Valid time: 2015-12-01T12:00:00Z
Test     :    socn   min=    3.683630   max=   38.016514   mean=   34.362863
Test     :    tocn   min=   -1.895580   max=   31.775337   mean=    7.698882
Test     :     ssh   min=   -1.914767   max=    1.337421   mean=   -0.262997
Test     :    hocn   min=    0.001000   max=  250.045295   mean=   43.648247
Test     :     mld   min=    0.838614   max= 5348.085716   mean=  216.514473
Test     : layer_depth   min=    0.838614   max= 6376.155029   mean=
911.245570
Test     :   cicen   min=    0.000000   max=    1.000000   mean=    0.219001
Test     :   hicen   min=    0.000000   max=    2.472954   mean=    0.240000
Test     :   hsnon   min=    0.000000   max=    0.743529   mean=    0.050114
Exception: InsituTemperature does not exist in ufo::ObsOperatorFactory
Exception: oops::LocalEnsembleDA<SOCA, UFO and IODA observations>
terminating...
OOPS Ending   2022-08-05 14:46:33 (UTC-0500)
On Fri, Aug 5, 2022 at 12:43 PM Travis Sluka @.***>
wrote:

@travissluka https://github.com/travissluka It seems like soca
generates quite different results under different compilers. There is an
example here and in the related issue on Chayanne. Any thoughts on what to
do about it? Is changing the tolerance an option?
@frolovsa https://github.com/frolovsa, yes I'm working on a PR that
cleans up the tests. As part of that, tolerances will be fixed, and several
of the tests that rely on test_soca_enspert will instead us a
pregenerated ensemble. The enspert step seems to be a large source of
tolerance issues across compilers.
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1206749967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH6ZZIYU4BPHTFO5MQEDVXVODFANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm fairly confident this is a problem with your personal build environment. Your build is somehow finding a version of UFO that was not compiled with GSW enabled.
@weihuang-jedi I took a look at your ~/intelenv file and noticed that you set LD_LIBRARY_PATH to point to /work/noaa/gsienkf/weihuang/jedi/src/my.compile/lib. I see that your my.compile directory does NOT contain GSW. This is your problem.

closing, this is a problem with personal build environment being set wrong, not a problem with SOCA

Thank you @travissluka for figuring this out.

Change yaml file:
bash-4.2$ pwd
/work2/noaa/gsienkf/weihuang/ufs/soca/new-soca-solver/soca_solver.32t2n_64p
bash-4.2$ diff ../soca_solver.40t2n_80p/letkf_solver.yaml .
339c339,340
<       name: InsituTemperature

 #name: InsituTemperature
  name: Identity

369c370,371
<       name: MarineVertInterp

 #name: MarineVertInterp
  name: Identity

bash-4.2$ tail stdoutNerr/stdout.00000000
Test     :     ssh   min=   -1.914767   max=    1.337421   mean=   -0.262997
Test     :    hocn   min=    0.001000   max=  250.045295   mean=   43.648247
Test     :     mld   min=    0.838614   max= 5348.085716   mean=  216.514473
Test     : layer_depth   min=    0.838614   max= 6376.155029   mean=
911.245570
Test     :   cicen   min=    0.000000   max=    1.000000   mean=    0.219001
Test     :   hicen   min=    0.000000   max=    2.472954   mean=    0.240000
Test     :   hsnon   min=    0.000000   max=    0.743529   mean=    0.050114
Unable to find field metadata for: sea_water_temperature
OOPS Ending   2022-08-05 11:43:32 (UTC-0500)
On Fri, Aug 5, 2022 at 10:56 AM frolovsa @.***> wrote:

@travissluka https://github.com/travissluka It seems like soca
generates quite different results under different compilers. There is an
example here and in the related issue on Chayanne. Any thoughts on what to
do about it? Is changing the tolerance an option?
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA-internal/soca/issues/793#issuecomment-1206658745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMCH6ZUQF2UECSQ5XYFZQDVXVBRZANCNFSM55MS7HMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fix airflow UI oops if delete manual triggered task

Currently airflow UI failed with "oops" when we delete the tasks that are triggered manually. The execution_time of a manual triggered task contains fraction of second and it breaks the parser.
I have manually tested the fix and it worked.
https://jira.lyft.net/browse/DPTOOLS-2109

@astahlman @feng-tao @lyft/dp-tools-viz

Codecov Report

Merging #128 into data-platform-upgrade will decrease coverage by 0.21%.
The diff coverage is 0%.

@@                    Coverage Diff                    @@
##           data-platform-upgrade     #128      +/-   ##
=========================================================
- Coverage                  69.17%   68.96%   -0.22%
=========================================================
  Files                        142      142
  Lines                      11287    11287
=========================================================
- Hits                        7808     7784      -24
- Misses                      3479     3503      +24

Impacted Files
Coverage Δ

airflow/www/views.py
68.11% <0%> (-0.35%)
:arrow_down:

airflow/utils/state.py
86.66% <0%> (-13.34%)
:arrow_down:

airflow/executors/__init__.py
64.51% <0%> (-3.23%)
:arrow_down:

airflow/settings.py
91.13% <0%> (-2.54%)
:arrow_down:

airflow/www/app.py
94.11% <0%> (-2.36%)
:arrow_down:

airflow/utils/dag_processing.py
85.77% <0%> (-0.82%)
:arrow_down:

airflow/configuration.py
83.91% <0%> (-0.51%)
:arrow_down:

airflow/utils/helpers.py
43.06% <0%> (-0.5%)
:arrow_down:

airflow/jobs.py
73.8% <0%> (-0.2%)
:arrow_down:

... and 1 more

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 0086508...7dcc546. Read the comment docs.

👍 Nice


Match Collect relevance behavior

PR should be merged for release with v2022.3

Do we expect that other changes will be needed for this PR? Is it OK if I merge the PR into the release branch for v2022.3?

Yes, it's ready to merge!


DMP-2701: Users not being removed from group

Aligning users in a security group with those specified in a patch request
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Can you please link the Jira ticket in the PR description


Filter by projects lead to an error

This page isn’t working
If the problem continues, contact the site owner.
HTTP ERROR 400
How to reproduce

Open this url https://spring.io/search?q=controller
Check checkbox "Project"
Click on "Filter"

We've retied the search page for now.


Using the latest Swift release binaries (3.0), test cases fail on linux.

See https://bugs.swift.org/browse/SR-2551.
Waiting on resolution from Apple.

Determined that creating an instance of the Calendar class was not a must do to meet the required functionality. Hence, refactored the code to remove this dependency so we could move forward; closing issue.


Restored my wallet with the backup file and the SEED Phrase -- my receiving adress is missing

Current DeFi App Version: 2.1.12
Previous DeFi App Version: 2.1.11
Operating System (OS): Windows 10

I had to reinstall my Windows System. Afterwards I installed DeFi app 2.1.11 and updated it to 2.1.12.
Loaded my backup file (I have overwritten it with every new update). Coins are there, but I cannot see my receiving adress. Therefore I cant perform LM and the DEX.

I typed in the commands for listing the tokens, followed by the command to get the associated address:
gettokenbalances {} true true
"DFI": xxxxxx
"BTC": xxxxx
"BTC-DFI": xxxxx
listaccounts {} false false true
{
"key": "xxxxxxxxxxx",
"owner": "xxxxxxxxxxxxx",
"amount": "xxxxxxx@DFI"
},
{
"key": "xxxxxxxxx",
"owner": "xxxxxxxxx",
"amount": "xxxxxxxx@BTC"
},
{
"key": "xxxxxxx",
"owner": "xxxxxxxxxx",
"amount": "xxxxxxxx@BTC-DFI"
}
]
There i see my adress. But it doesnt show me the receiving adress to receive DFI, to use Liquid Mining or the DEX  (as shown in the pic above).
App log / binary log / app config
applog.log
binarylog.log

Hi @iceman999sod , thanks for your feedback, screenshots and logs. Please give us time to investigate this.

Hi @iceman999sod , thanks for your feedback, screenshots and logs. Please give us time to investigate this.

Hi @iceman999sod , update v2.1.15 is out.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

Hi @iceman999sod , update v2.1.15 is out.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

Hi @iceman999sod , the team investigated your issue, solution to your issue is that you've to manually add your addresses again.


Removed unused call of contarct function, fixed problem with init a…

removed unused call of contarct function, fixed problem with init…
… and default functions (with missed attribute name)
Removed unused call of contarct function (strange extra call of already called function), fixed problem with init… _ and default functions (with missed attribute name)
What was wrong?
Incorrect work of vyper-run
Issue #18
How was it fixed?
Removed extra call,
For init case  added comparsion by type,not by name
Summary of approach.
Cute Animal Picture

Thanks for the fix @NikitaMishin  !


Change ClipTransformer to a uniform HuggingfaceImageTransformer, rename HuggingfaceEncoder to HuggingfaceTextTransformer

@EdenWuyifan,  I made some changes and it's ready to merge now, please merge it.


good

It's a nice application, but I found it eats too much momery when I play a big gif image file

It is. To render a .gif we have to fetch each frame as a Bitmap into memory, and it is, unfortunaly, not that easy on .Net to quicly free it.
Though .Net seems to handle large memory consumption rather well, OutOfMemoryException isn't registered on avarage sized (~10Mb) .gif files yet.
If you run into a large .gif that breaks gifer, I would be really appretiate if you would share such.


fix(debugger): Fix potential debugger lockups

merged via https://github.com/angular/protractor/commit/f9b0a92079b55384d4560fef9400bb473672ce9c


Cardinal direction for NE is missing in all the language-files

As the title says, the cardinal direction for NE is missing in all the language-files. I can make a PR for the English and Swedish translations but that's the only languages I speak. Should make a PR for those?

Fixed! https://github.com/MichMich/MagicMirror/commit/611627ca97a9828fdf39e5889eb3ac54359330de


Omnipay 3.0 support?

What are the plans for supporting omnipay 3.0?

I'm at a Thinking Digital conference l, and a little drunk, so am going to promise the Earth.  Unless anyone beats me to it,  I'll aim to get it done this weekend.

Can you check with 3.x@dev?


⚠ AGEG website (prod) has degraded performance

In 5aff5dd, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 1727 ms

Resolved: AGEG website (prod) performance has improved in 3b98b5b.


[Event Request] Application “Tests-Misc”, Codeunit 136149 "Chart Configuration Tool"

[Event Request] Application “Tests-Misc”, Codeunit 136149 "Chart Configuration Tool"

Could you please insert the OnTestInitialize Event at the beginning of each test procedure?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


fix: validate skill empty & add duplicate dialog

Description
Warning style beside Start Bot button
Show warning in toolbar, if both has error and warning, will show error at first priority.

When bot call a skill

check dialog used skills exist (Error)
check skill required info (Warning)
.

When add a dialog
Prevent create same id dialog, ignore case

Task Item
close #3284
close #3401

Screenshots

I feel a little tricky is the endpoint url is produced after start bot, and it's required by skill, so the user have to

Start bot get endpoint url
Fill it in composer skill page form, restart bot.

First start bot would cause error when it run into call skill step, we should avoid this. but if we forbidden start bot, user can never get endpoint url. Discussed with @hibrenda, issue filed by @xieofxie

Coverage increased (+0.04%) to 57.873% when pulling 0c627aae5e7cfa376380b4e183b2752117c67dd2 on zhixzhan:validation into 0a2bfa402088ec16f6acc263da3c0503c73e4c86 on microsoft:main.


issues with loaded UICollectionViewCells after reloadData() when layout.currentPage > layout.numberOfVisibleItems

I have 10 UICollectionViewCell (each with an image inserted) in UICollectionView, and initially due to restrictions on the rate of downloading images I had reduced the number of visible items to 5
layout.numberOfVisibleItems = 5
When I go to change my data model and do a full reload of the UICollectionView, depending on what UICollectionViewCell Im on....ie the value for layout.currentPage and layout.currentScrollOffset determines which 5 cells will be loaded in memory after the reloadData()....
.e.g. currentPage is 9, do a reloadData(), and cells 5,6,7,8,9 are loaded into memory. then I setCurrentPage() to 2
for the UICollectionViewCells 0 and 1 behind page 2, the images displayed are from the recycled UICollectionViewCell taken from memory like if they were cached - even though the new images have been downloaded again and set in the imageView in the UICollectionViewCell
Initially I was thinking:

could be an issue between the reloadData() call and setCurrentPage() but these are both performed on the main thread.
I played around with forcing invalidateLayout() before and after the reloadData()
I was thinking if I should reset layout.currentPage before doing the reload.

DispatchQueue.main.async {
  self.carouselView.collectionViewLayout.invalidateLayout()
  self.carouselView.layoutIfNeeded()

  self.dataModel = newDataModel
  self.carouselView.reloadData()

  layout.setCurrentPage(index, animated: true)
}

But when I don't set layout.numberOfVisibleItems and leave it at the default, the issue with showing the wrong images behind the currentPage does not happen. There is also no need for invalidateLayout() here
So I am wondering if I'm missing something when using layout.numberOfVisibleItems or if there is a bug there

Hi,
the way that you use numberOfVisibleItems seems okay, I think the issue is about invalidating, could you try invalidating layout via performBatchUpdates like this?
        collectionView.reloadData()
        collectionView.performBatchUpdates({
            self.collectionView.collectionViewLayout.invalidateLayout()
        })

if this didn't work, can you make a simple project and share it here, it's probably not related to downloadable images!
it might be a bug but I need to find a way to reproduce it.

Hi Amir,
Thanks for the response, I had tried the way you suggest... the same way as its done in viewDidLayoutSubviews() method  but it had the same problems. By the way I was using the configuration for the inverted cylinder which I took from the mac layout designer app. I will look at creating a sample project to reproduce the issue.
Thanks
Jonathan

Hi Jonathan,
With the new version the issue should be fixed, no need to call performBatchUpdates or invalidateLayout anymore,
Check the version 1.0.0 or higher and feel free to open a new ticket if needed


Updates and export manifest

Plan was to test standard export, and logging responses. I've been making cURL requests from a shell within this container.
docker exec -it "databox-app-template-node" /bin/bash
apk add --update curl
TOKEN=$(curl -k https://databox-arbiter:8080/token -H "Content-Type: application/json" -H "X-Api-Key:$ARBITER_TOKEN" -X POST -d '{"target":"databox-export-service","path":"/lp/export","method":"POST"}')
curl -k https://databox-export-service:8080/lp/export -H "Content-Type: application/json" -H "X-Api-Key:$TOKEN" -X POST -d '{"id":"","dest":"https://export.amar.io/","data":{"foo": "bar"}}'

I already have a version of node-databox that has export functions, but before I publish a broken version, I'm seeing if the above works first.

Oh, package and datasource definitions are probably not needed in this case. I was seeing if I could have everything pretend the export service is a store, but it wouldn't be since it doesn't have a catalogue.


Missing vals body

Function body and tests are done and ready to be reviewed and merged.

It's interesting that I pulled the latest update to my local computer and switched to your branch missing_vals_body, I'm not able see the function body and the testing file in the branch.  Not sure if it's only mine issue.
I went the the files changed tab and copied the function body and tests to my local computer, I ran pytest with no issue.  The function body and test functions indicated in the files changed tab look good to me.


AI Based heuristics for the Find API

This PR depends on #424
Includes models for gfx906 and gfx908 for all three directions

@atamazov This PR is based off of imm-fallback-improv to reduce dependence of unopened PRs. Also, there was no code in getwti-wino2111 that would have been helpful to this PR.

@JehandadKhan

@atamazov This PR is based off of imm-fallback-improv to reduce dependence of unopened PRs. Also, there was no code in getwti-wino2111 that would have been helpful to this PR.

It's Ok so far, as a concept check.
However I have the following design in mind. If AI-based classifier fails to find the "fastest" solution due to some reason, then getwti-wino2111 should be used as a "spare". I can perform integration of AI-based classifier on top of getwti-wino2111.
getwti-wino2111 optimizes Immediate Mode Fallback better than #424 and fully tested.

Converted to draft to avoid spoiling docker image cache on CI. You can continue work as usual. But please change this back to "normal" PR only after ending of CI moratorium (see mail). Then first merge from develop. Push the [Ready for review] button only after that. Thanks.


Can you provide a more detailed guide to fine-tuning operations?

I want to fine-tune a mt5 Chinese model on my own dataset！
Extremely grateful.

@asahi417

Hey, do you have your dataset on HuggingFace?
On Wed, 8 May 2024 at 13:37, 小陈 @.***> wrote:

@asahi417 https://github.com/asahi417
—
Reply to this email directly, view it on GitHub
https://github.com/asahi417/lm-question-generation/issues/23#issuecomment-2099725254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEXCDHOM3DPB3MD224BJZLZBGTYBAVCNFSM6AAAAABHLM45SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZG4ZDKMRVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

hello! thanks your reply!
I have the dataset organized ~ not uploaded to huggingface at the moment, would like to load the dataset locally for mT5 fine-tuning

@asahi417

Cool.  If it
uses the HuggingFace dataset, it should be pretty straightforward, but
otherwise can be a bit tricky.
On Wed, 8 May 2024 at 14:08, 小陈 @.***> wrote:

hello! thanks your reply!
I have the dataset organized ~ not uploaded to huggingface at the moment,
would like to load the dataset locally for mT5 fine-tuning
—
Reply to this email directly, view it on GitHub
https://github.com/asahi417/lm-question-generation/issues/23#issuecomment-2099750423,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEXCDAQRSUHA4UC5YXDZ4TZBGXMZAVCNFSM6AAAAABHLM45SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZG42TANBSGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Very excited to see your feedback! I will upload the dataset to huggingface, how do I need to fine tune it after that?

@asahi417

Try the following command.
lmqg-train-search -c "tmp" -d "{your-hf-dataset-alias}" -m "mt5-small" -b 64 --epoch-partial 5 -e 15 --language "zh" --n-max-config 1 -g 2 4 --lr 1e-04 5e-04 1e-03 --label-smoothing 0 0.15

That will launch the fine-tuning with hyperparameter gridsearch. you might need to play around with the parameter. See the full description at lmqg-train-search -h.

For example, following command is used to train https://huggingface.co/lmqg/mt5-base-zhquad-qag.
LA='zh'
MODEL="google/mt5-base"
MODEL_SHORT='mt5-base'
lmqg-train-search --use-auth-token -d "lmqg/qag_${LA}quad" -m "${MODEL}" -b 8 -g 8 16 -c "lmqg_output/${MODEL_SHORT}-${LA}quad-qag" -i 'paragraph' -o 'questions_answers' --n-max-config 2 --epoch-partial 5 -e 15 --max-length-output-eval 256 --max-length-output 256 --lr 1e-04 5e-04 1e-03

See more example here
https://github.com/asahi417/lm-question-generation/blob/master/misc/2023_acl_qag/model_finetuning.end2end.sh

Very excited to see your feedback! THANKS


Add form field align.

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Coverage remained the same at 89.979% when pulling 5f08ad4b2afaa4c8663eacf689e6b8a8ffe52eab on Wesamgerges:field-align into 721a4eebbde77040a1318e60aa9ef21229bbcf99 on vue-generators:master.

Could this not be better handled already  With fieldStyleClasses ?

This is mainly for fields that require the text to me on its right like checkbox or radio.
I have tried to use css, however, I couldn't get it right.
You may have more experience in css than me.
If you have a better solution, please let me know :)
Thanks

labelClasses and  fieldClasses classes are available. Perhaps they need to be implemented better or additional hooks for clases to be added?

As @DelfsEngineering stated, you should use CSS for this.
If you find there is t enough support with the existing fieldClasses and labelClasses, please provide a JSFiddle example of your use case so we can take a look.

I just need to do this.
I don't know if this can be done with just css.

Use the required attribute and :after pseudo class?


[v2.1.1] NoSuchMethodError on ByteBuffer when trying to play a track

Versions

Lavaplayer v2.1.1
JVM 1.8.0_402

Description
Hello,
When trying to play any track, I keep getting NSM on ByteBuffer (see stacktrace) even after mentionning in my gradle file that the source/target compatibility is Java 8
Stacktrace
[LocalAudioTrackExecutor/ERROR]: Error in playback of mLxI-q9Fi0s com.sedmelluq.discord.lavaplayer.tools.FriendlyException: Something broke when playing the track. 	at com.sedmelluq.discord.lavaplayer.tools.ExceptionTools.wrapUnfriendlyExceptions(ExceptionTools.java:45) 	at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:113) 	at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$2(DefaultAudioPlayerManager.java:330) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:750) Caused by: java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer; 	at com.sedmelluq.discord.lavaplayer.container.matroska.format.MutableMatroskaBlock.getNextFrameBuffer(MutableMatroskaBlock.java:56) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.processFrameInBlock(MatroskaStreamingFile.java:368) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.parseClusterSimpleBlock(MatroskaStreamingFile.java:332) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.parseNextCluster(MatroskaStreamingFile.java:317) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.provideFrames(MatroskaStreamingFile.java:293) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.lambda$process$0(MatroskaAudioTrack.java:40) 	at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.executeProcessingLoop(LocalAudioTrackExecutor.java:284) 	at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.executeProcessingLoop(LocalAudioTrackExecutor.java:257) 	at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.process(MatroskaAudioTrack.java:39) 	at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25) 	at com.sedmelluq.discord.lavaplayer.source.youtube.YoutubeAudioTrack.processStatic(YoutubeAudioTrack.java:64) 	at com.sedmelluq.discord.lavaplayer.source.youtube.YoutubeAudioTrack.process(YoutubeAudioTrack.java:51) 	at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:101)
build.gradle
plugins {
    id 'java'
    id 'application'
    id 'com.github.johnrengelman.shadow' version '8.0.0'
}

application.mainClass = "net.vadamdev.jafarbot.Main"
group 'net.vadamdev.jafarbot'
version '2.4.2'

repositories {
    mavenCentral()

    maven {
        url 'https://jitpack.io'
    }
}

dependencies {
    implementation group: 'net.dv8tion', name: 'JDA', version: '5.0.0-beta.21'
    implementation group: 'ch.qos.logback', name: 'logback-classic', version: '1.3.14'

    implementation group: 'dev.arbjerg', name:'lavaplayer', version:'2.1.1'

    implementation group: 'me.carleslc.Simple-YAML', name: 'Simple-Yaml', version: '1.8.4'
    implementation group: 'com.google.code.findbugs', name: 'jsr305', version: '3.0.2'
    implementation group: 'com.googlecode.json-simple', name: 'json-simple', version: '1.1.1'
    implementation group: 'com.google.code.gson', name: 'gson', version: '2.10.1'
}

java {
    sourceCompatibility = JavaVersion.VERSION_1_8
    targetCompatibility = JavaVersion.VERSION_1_8
}

compileJava.options.encoding = 'UTF-8'

Try using a newer version of Java

Hello.
It works on Java 17. But what if i wanna keep using java 8 ? :x
This errors occurs when the build bytecode is in Java9+ since they changed the ByteBuffer class (see: https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/)
But the source compatiblity in the Lavaplayer build.gradle file is Java 8 (line 36) so i guess just adding targetCompatibility = JavaVersion.VERSION_1_8 would fix the issues
Otherwise, it would be cool to mention what minimum version of Java you need to use this fork ^^'

But what if i wanna keep using Java 8 ? :x

Unless you have a specific requirement that forces you to use Java 8 I would really advise you upgrade. Aside from legacy software there's no real reason to continue using such an outdated version

It's not a issue for this project, I can update but I have other legacy bots that I will need to update which will take time :x
Would be cool to have a fix honestly

Could you give 08fe37dad9c0a2bb42240dab5401726cada0cc95 a try and see if it fixes your issue?

Still get the same error (Same bot, JVM version etc...)
Gradle file juste in case:
dependencies {
    implementation 'com.github.lavalink-devs:lavaplayer:set-target-compatibility-SNAPSHOT'
}

tasks.withType(Tar).configureEach {
    duplicatesStrategy = DuplicatesStrategy.INCLUDE
}

tasks.withType(Zip).configureEach {
    duplicatesStrategy = DuplicatesStrategy.INCLUDE
}

34f8ca076291ba4c0a1c98f50da91520874f33cc?

Same issue

Out of curiosity, I tried your fork (https://github.com/devoxin/lavaplayer) and it works with Java 8

I'd just stick with my fork then tbh. There's speculation as to whether we leverage Java language features from versions after 8, or it could equally be due to a fault in how Gradle is being configured to compile the project, but extensive testing isn't worth it as I think the general consensus is that we don't want to retain support for super old Java versions so are ultimately looking at bumping the minimum version required to 11.
Just keep in mind with my fork, that it's missing a lot of the custom stuff like audio track isrcs and artwork URLs. If you don't need that then it should be no issue.
I'm going to go ahead and close this issue as I don't think there's much more to be said. If there is, you're free to join the Lavalink Discord server


Add constraint on sysroot

The fix for #23 in #24 was incomplete. In particular, 733742d0a153591ca37ac2b597616937a3b965e5 should be reverted. The failure can be seen in https://github.com/conda-forge/pytorch-cpu-feedstock/pull/299
+ pip check
No broken requirements found.
+ python -c 'import torch; torch.tensor(1).to('\''cpu'\'').numpy(); print('\''numpy support enabled!!!'\'')'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
    import torch; torch.tensor(1).to('cpu').numpy(); print('numpy support enabled!!!')
    ^^^^^^^^^^^^
  File "$PREFIX/lib/python3.13/site-packages/torch/__init__.py", line 367, in <module>
    from torch._C import *  # noqa: F403
    ^^^^^^^^^^^^^^^^^^^^^^
ImportError: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by $PREFIX/lib/python3.13/site-packages/torch/../../../././libcufile.so.0)
WARNING: Tests failed for pytorch-2.5.1-cuda126_py313hb62db30_205.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken

CC @carterbox

test environment
TEST START: /home/conda/feedstock_root/build_artifacts/linux-aarch64/pytorch-2.5.1-cuda126_py313hb62db30_205.conda
WARNING: Multiple meta files found. The meta.yaml file in the base directory (/tmp/tmp9b6ayz23/info/recipe) will be used.
 The next step that I am taking is to create a smaller reproducing example that doesn't require rebuilding the entirety of pytorch as this issue shouldn't be libcufile/pytorch specific.
My initial findings are that this issue only happens when cross-compiling as is currently done in the pytorch feedstock (building inside an aarch64 container using emulation is too slow). If building natively/emulated in our default containers, this is not a problem because the system glibc is the latest.

I have written a debugging recipe (mentioned above) to reproduce this issue and adding a runtime constraint on the sysroot package did not solve the issue.
My vague (and possibly partly incorrect) understanding is that conda-build does not support testing cross-compiled packages natively. It only supports existence tests for those packages, so normally importing pytorch (which triggers the loading of libcufile) is not allowed. However, conda-forge does some extra things to automatically provide emulation for the test section of cross-compiled recipes.
Those extra things live in the conda-forge-ci-setup package in cross_compile_support.sh. When I locally modified the cross_compile_suport.sh to set GLIBC_VERSION always to 2.34, the cross-compiled tests succeeded. This is because it is here in this script that the sysroot which the test-time emulator uses is created.
Looking at the logs of a cross-compile build, we see something like this:
++++ shyaml get-value c_stdlib_version.0 2.17
+++ GLIBC_VERSION=2.17
+++ HOST_PLATFORM=linux-aarch64
+++ CUDA_COMPILER_VERSION=None
+++ GLIBC_VERSION=2.17
+++ [[ linux-aarch64 != \l\i\n\u\x\-\6\4 ]]
+++ echo 'export CONDA_BUILD_CROSS_COMPILATION=1'
+++ export CONDA_BUILD_CROSS_COMPILATION=1
+++ CONDA_BUILD_CROSS_COMPILATION=1
+++ '[' -f /home/conda/feedstock_root/.ci_support/linux_aarch64_.yaml ']'
+++ echo build_platform:
+++ echo '- linux-64'
+++ [[ linux-64 == \l\i\n\u\x\-\6\4 ]]
+++ [[ linux-aarch64 == linux-* ]]
+++ mamba create -n sysroot_linux-aarch64 --yes --quiet sysroot_linux-aarch64=2.17

This is when the cross-compilation emulation environment is setup I guess? By default it uses shyaml to get the sysroot version from whatever has been set for c_stdlib_version. This is why cross-compiles fail but emulated/native builds succeed! Because for native/emulated builds, the sysroot during the test phase comes from the container which is defined by conda-forge.yml -> os_version, but the cross-compile sysroot comes from conda_build_config.
Furthermore, the cross-compile sysroot is set before conda-build starts, so we cannot control it from inside the recipe.
Therefore, I believe the solution is to choose the cross-compile sysroot based on the conda-forge.yml -> os_version so that is consistent with non-cross-compile builds.

Thanks for debugging this. I'm happy to close this as fixed by https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/368 (which was an aspect of the whole setup I hadn't fully grasped yet).


To decode a repeating group more than once, resetting of the limit is needed

According to the example in the wiki, to decode a repeating group we can use a foreach loop:
for (CarDecoder.PerformanceFiguresDecoder performanceFigures : car.performanceFigures())
{
    sb.append("\ncar.performanceFigures.octaneRating=").append(performanceFigures.octaneRating());

    for (AccelerationDecoder acceleration : performanceFigures.acceleration())
    {
        sb.append("\ncar.performanceFigures.acceleration.mph=").append(acceleration.mph());
        sb.append("\ncar.performanceFigures.acceleration.seconds=").append(acceleration.seconds());
    }
}

Looping using the foreach moves the limit of the decoder (i.e. the car object in this case).
If, for some reason, I need to loop through the repeating group more than once, it will not work.
In order to workaround this, I would have to (as done in the generated toString() method):

get the original limit before start processing the repeating group (i.e. originalLimit = car.limit())
set the limit to its original value after repeating group processing is ended (i.e. car.limit(originalLimit)

Is it the expected behavior?
Is there any reason why the limit cannot be reset when calling the car.performanceFigures() method?
Thank you

You could use the limit to reset before to iterating if you are careful. You cannot rerun a single iteration of the loop as this would throw off the loop index.


Allow capture of raw functions

This fixes #814 by just making capture work for raw functions.

LGTM, but the lambda in the decorator doesn't accept kwargs, so you get a weird bug if you try to do:
lm = lm + capture(rawfunc(), name="scott")

instead of
lm = lm + capture(rawfunc(), "scott")

I just added a fix + test for this if that's OK :)


added maximum votes limit per comment

feel free to correct me if I did something not as expected

Missing a change for README params

done
BTW do you think it is better to change unlimited to 0 as in other similar places? The only downside is that It will make impossible to disable voting by setting 0.

thx, LGTM
fix #207

change unlimited to 0 as in other similar places?

to me default -1 makes sense as in this case 0 can be the real value.


EvalError: call to eval() blocked by CSP

Cannot progress past Javascript section: Basic Algorithm Scripting: Return Largest Numbers in Arrays, error in console: "EvalError: call to eval() blocked by CSP"  Running Firefox 72.0.1 on Macbook Pro High Sierra

Duplicate of #38044

Thanks for reporting this, @opalko.  @brandon-thenaro is right, though, so I'm closing this so we can track the issue in one place.


Fix SQL Upsert Compatibility Issue for Android 10 and Lower

Using upsert when inserting non-existing chapters the app shows an error. When I change it to insert, it works just fine. I don't really understand SQL, but this fixes the issue.
I've also collected some logs, if my changes are not a desired behavior please give some advice xD
ExceptionString(e=android.database.sqlite.SQLiteException: near "ON": syntax error (code 1 SQLITE_ERROR): ,
while compiling: INSERT INTO chapter(_id,book_id,url,name,scanlator,read,bookmark, last_page_read,chapter_number,source_order,date_fetch,date_upload,content,type)
VALUES (?, ?, ?,?,?,?,?,?,?,?,?,?,?,?)
ON CONFLICT(_id)
DO UPDATE
SET
url = ?,
read = ?,
bookmark = ?,
last_page_read = ?,
content = ?,
type = ?

WHERE _id IS ?)

I use upsert in order to update chapters when it exist and if it doesn't exist then just insert a new chapter into db

when this error happens and what is your phone model?

Got the idea, but somehow when it try insert a new chapters, it shows an error message

I tried to insert chapter using a samsung device with android 11 and then nothing happed

I'm using Android 10, maybe the SQLite version on the device is causing this issue,
As mentioned in Android SQLite Javadoc, Android 9-10 is still using an SQLite version 3.22
The phrase "ON CONFLICT" is also part of UPSERT, which is an extension to INSERT added in version 3.24.0 (2018-06-04).

Found the solution, we can use INSERT OR REPLACE to fix compatibility issues.
If you agree I can push my changes

Insert or Replace are very different from  using Insert ..... Do Update Set

it's better to not change the current database queries

Insert or Replace are very different from using Insert ..... Do Update Set

when operation use replace, a completely new object is created in database that is completely unrelated to the previous one and because of that is cause a very serious issue in lazyColumn widget

Hmm, it's true, maybe use a conditional statement to imitate upsert behavior?

I tried on android 7 device and there was not an issue or break in app functionality?
which android device do you have problems with

Android 10, Poco X3 NFC

Just tested the lastest release, seems fine.
I only get issue crashing on latest commit build.
Don't know what's wrong with it.


TypeError: window.Dashboard.revive_payload is not a function

First, thank you for the awesome package.
I suspect that this PR is breaking for all Stipple apps running on previous versions in ENV=PROD.
The reason is that our mini app has stopped working after the release with the following error:
app/:228 TypeError: window.Dashboard.revive_payload is not a function
    at window.parse_payload (app/:386:22)
    at app/:213:14
    at WebSocket.<anonymous> (app/:157:11)

The local version that uses corresponding JS helper files works fine. The PROD version that grabs scripts from GenieFramework CDN throws the above error in the browser console.
Is there a way to add an alias to be backwards compatible?
It's a minor version release, so I wouldn't expect it to be breaking.

@hhaensel can you please check this - if you can fix quickly great, otherwise we need to have a new release to rollback the change until it's backwards compatible.

@svilupp sorry for this and thank you for bringing this up. But for future reference, please beware that in Julia minor versions at version 0.x are considered breaking. Normally Pkg won't update - so if you put your compat properly, this would not auto-upgrade.
https://pkgdocs.julialang.org/v1/compatibility/#compat-pre-1.0

I will also take a look as the CDN should use the versioned script, not the master.

Thank you for the quick response.
Re. versioning, agreed. But I misspoke -- this was a patch version difference (eg, I was on 0.27.0 and the breaking release was 0.27.18)
Since I updated to the latest Stipple, I noticed another bug in the Sessions from some recent changes. I'll open the issue with the git blame.

@svilupp May I ask, when revive_payload() is called? Are you calling it in private scripts?
I removed that function and replaced it by adding a simpler reviver to Genie's revivers.
If you provide a snippet of your script, I could either propose a solution (most probably it can be simply left out) or I could bring back the function in a new version of Stipple.
As that function was not part of the official API, I considered the release non-breaking. Sorry that this caused some trouble for you.

Oh, I begin to  understand. @essenciary  is probably right that the CDN version and the Stipple version don't fit.
Then Stipple's watchers.js has changed.
@essenciary I was never involved in releasing CDN versions of the assets. How is that done?

I am not calling the function directly. It’s a normal Stipple dashboard on Stipple 0.27.0, which calls revive_* as part of the JavaScript codegen.
It was an issue only when running in prod env, when the scripts are sourced from CDN, so perhaps the issue is simply that it wasn’t versioned.
My Stipple locally created model that required the function, but it was no longer available on the CDN.
——
Simply updating to the latest Stipple solves the problem, but not everyone can do it / it might break some dashboards.

I just checked that there are, indeed different (and correct) versions of watchers.js on
https://cdn.statically.io/gh/GenieFramework/stipple.jl/v0.27.17/assets/js/watchers.js

and
https://cdn.statically.io/gh/GenieFramework/stipple.jl/v0.27.18/assets/js/watchers.js

I suspect that you have deved  Stipple and are running from master. In that case Stipple will call
https://cdn.statically.io/gh/GenieFramework/stipple.jl/master/assets/js/watchers.js

and you will run in the difficulties above.
If you still want to run a deved version you can, but you have to manually set the correct version number, e.g.
using Pkg
ver = filter(x-> x.second.name == "Stipple", Pkg.dependencies()) |> x -> first(x)[2].version
Genie.Assets.assets_config!(Stipple, version = string(ver))

@essenciary could it be that we always use version = "master"?
If so it's our job to include above snippet in Stipple.jl ...

We might add
function version_string(package::String)::String
    endswith(package, ".jl") && (package = String(package[1:end-3]))
    pkg_dict = filter(x -> x.second.name == package, Pkg.dependencies())
    isempty(pkg_dict) ? "master" : string(first(pkg_dict)[2].version)
end

version_string(m::Module) = version_string(String(nameof(m)))

function Genie.Assets.AssetsConfig(m::Module)
    package = "$(nameof(m)).jl"
    version = string(package_version(m))
    Genie.Assets.AssetsConfig(; package, version)
end

function Genie.Assets.AssetsConfig(package::String)
    version = version_string(package)
    Genie.Assets.AssetsConfig(; package, version)
end

so that we then can
Genie.Assets.AssetsConfig("Stipple.jl")
# or
Genie.Assets.AssetsConfig(Stipple)

That would be breaking, though, because the files would no longer reside in master but in the respective branch

@svilupp
I've fixed the issue and brought back revive_payload() in watchers.js.
Thanks for reporting.
@essenciary We should consider the above changes for the next minor Stipple release ...

https://cdn.statically.io/gh/genieframework/stipple.jl/master/assets/js/watchers.js
is not yet updated, but
https://cdn.statically.io/gh/genieframework/stipple.jl/v0.27.19/assets/js/watchers.js
is already available.

@essenciary could it be that we always use version = "master"? If so it's our job to include above snippet in Stipple.jl ...

FWIW, I believe that was driver of my issue. I didn’t clock that. It’s always set for version=“master”: https://github.com/GenieFramework/Genie.jl/blob/2128aa0147770f5944af4b46d7a902ae88a24083/src/Assets.jl#L25C10-L25C10
I didn’t dev the package, that was the behaviour on 0.27.0 that was added as a normal package.

Yes, using master is the issue.
@hhaensel adding the version_string part to Genie.Assets and I'll tag a release.

OK - I pushed on master... Not sure how to test the tagged assets without actually tagging the Genie release first. So I'll do that.

@hhaensel thank you very much for the fix! ♥

You need to modify:
isa(package, Module) && (package = string(package))

to
isa(package, Module) && (package = String(nameof(package)))

because string(Stipple.JSON) == "Stipple.JSON3", while String(nameof(Stipple.JSON3) = "JSON3"
That's why I wrote two methods.

@hhaensel got it! I'll update and release

@svilupp can you please update to latest Genie and Stipple and check if everything works as expected? You should now be getting versioned assets.

Thank you for the quick turnaround.
It all worked fine on Stipple.jl 0.27.18.
When I upgraded Genie and Stipple to the latest, it stops working.
I get the following errors:

app/:331
GET https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/keepalive.js net::ERR_ABORTED 404 (Not Found)

Scripts seem to be properly injected into the main js file:
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/underscore-min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/vue.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/stipplecore.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/vue_filters.js" defer></script>
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/watchers.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stipple.jl/0.27.19/assets/js/keepalive.js" defer></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleui.jl/0.22.10/assets/js/quasar.umd.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/plotly2.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/resizesensor.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/lodash.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/vueresize.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/vueplotly.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/sentinel.min.js"></script>
<script src="https://cdn.statically.io/gh/genieframework/stippleplotly.jl/0.13.11/assets/js/syncplot.js"></script>

However, they do not seem available on the CDN.
I get the following when I try to open the files directly:

Not Found
Remote or internal content not found. Back to homepage or Ask the Community.`

Oh ugh, the CDN does not support URLs with Git tags.

OK, it works but it needs the v as in vX.Y.Z

@svilupp releasing new patch versions. Sorry for the issues and thanks for the info.

Woohoo! Everything looks good with the current releases.

https://cdn.statically.io/gh/genieframework/stipple.jl/master/assets/js/watchers.js
is not yet updated, but
https://cdn.statically.io/gh/genieframework/stipple.jl/v0.27.19/assets/js/watchers.js
is already available.

see above 😉 it had the 'v' already.
The master is now updated, so any version should currently run with master as well

@hhaensel Mmmm yes... but not the version I initially released...

master should be the current master, right?

FWIW, I can confirm that the latest master works well. This issue can be closed from my perspective.

@svilupp thanks for confirming, closing.


New package: LibraryAugmentedSymbolicRegression v0.0.1

Registering package: LibraryAugmentedSymbolicRegression
Repository: https://github.com/trishullab/LibraryAugmentedSymbolicRegression.jl
Created by: @atharvas
Version: v0.0.1
Commit: e3b524584677d6d02ea367e35541c192896b37e6
Reviewed by: @atharvas
Reference: https://github.com/trishullab/LibraryAugmentedSymbolicRegression.jl/issues/6#issuecomment-2348248188
Description: Language aided Symbolic Regression in Julia
Release notes:

# Initial code release for LibraryAugmentedSymbolicRegression

This version contains the base code to allow SymbolicRegression.jl to induce programs with LLMs in a way that accelerates search. I want to have up-to-date documentation before releasing v0.1.0.

More information about this method is available at: https://trishullab.github.io/lasr-web/

Hi, congrats on the registration (which is the new version of #115078).
However, I think the comment https://github.com/JuliaRegistries/General/pull/115078#issuecomment-2348062107 should be resolved before merging is allowed. A new package should rarely be a fork of an existing one, and if it is the justification should be clear and I would ask the initial author @MilesCranmer for approval.

Approved, I work with these guys!

[noblock] @MilesCranmer Thanks for the clarification! You will have to edit your comment to contain [noblock]


java.lang.NullPointerException: Cannot invoke "org.apache.hop.core.row.IRowMeta.clone()" because the return value of "org.apache.hop.pipeline.transforms.filterrows.FilterRows.getInputRowMeta()" is null

Apache Hop version?
2.1
Java version?
java 11
Operating system
Linux
What happened?
Now and then we encounter a NullPointerException. It is not al the time, it just comes and goes on different places of our 4 hours process.
java.lang.NullPointerException: Cannot invoke "org.apache.hop.core.row.IRowMeta.clone()" because the return value of "org.apache.hop.pipeline.transforms.filterrows.FilterRows.getInputRowMeta()" is null
I think it is always when 2 datastreams come into a filter:

But 1 time it goes well and in the next run it failes.

I try to fix it by only send 1 stream to a filter. I hope this helps but we have a lot of pipelines with more of these situations that can go wrong one day.
Issue Priority
Priority: 1
Issue Component
Component: Actions

we are going to need a reproduction path/sample.
One of the reasons could be that the metadata of the 2 streams doesn't match. make sure all field names, field lengths, data types are completely identical

It is hard to produce a sample because sometimes it goes well and sometimes not. And sometimes it is in pipeline A and sometimes in pipeline B. But always on a spot where more than 1 stream goes to another transform. This other transform can also be a 'dummy' one.
That is also the reason that it can not be a mismatch of the metadata of the 2 streams.

Can we get the metadata structure of the 2 table inputs? guess the only way to try and reproduce will be to simulate the structure generate random number of rows and loop until it fails (if it fails)

preferably also database type and field types from the source table

.take-issue

postgres db

De first 2 fields are int and the last is a string
Both streams have the same input fields. I never have this problem when I run it via the gui.

We are experiencing the same issue here. We found that a common pattern for this issue is that it is failing on a transform that has more than one hop as input. Another thing to say is that we experienced the same issue but less frequent on PDI so it seems that is something we inherited. We are investigating about that but the issue is very very hard to be reproduced ans infact we were unable to provide a sample of the failing situation till now

The issue might have been resolved with https://github.com/apache/hop/issues/3056
You can test it in a test environment using an unreleased version of hop fetched from here
If it is not the case feel free to re-open


Add support for JAXB 3.0.0

This is a first draft at implementing support for JAXB 3.
I would appreciate any feedback on the code or testing...
I should likely add more Integration Tests yet!

Okay, will check if I have time

Nice initiative! In the end this 'jaxb3' stuff is needed. So the "com.sun.tools.xjc" packages are not renamed?

So you suggest I merge it? Haven't had the time yet...

@phax I would be happy to wait for your review before merging.

@phax thanks for your review. I pushed some updates. Do you want to merge this before I fork it, or should I fork it first?

I would merge and change the version.
Do you want me to build a release as well, or are you able to push to Maven Central as well?

I can push under our groupId. If you would like a release under your groupId I can't do that though

Great if you can do it. To avoid redundancies I guess it would be smarter to have only one Jaxb 3 release

If you are chaning the group ID anyway, you can change the version as well.
So I am merging this anbd you are taking it from there.
Thanks for your effort!

I apologize for intruding – the README says

We are happy for users to open issues, however we make no claims that we will investigate or resolve them.

but GitHub Issues are disabled in this repository.

I'm trying to use the 3.0 functionality and I'm seeing

A required class was missing while executing com.evolvedbinary.maven.jvnet:jaxb30-maven-plugin:0.15.0:generate: javax/xml/bind/JAXBException

Is this a known issue, or does it make sense for me to investigate and try to fix it?
If I figure out the issue, would a PR be accepted?
Sorry again if you did not intend to receive issues/question.
Thanks,
Simon

Well, the situation is a bit tricky.
I was happy as EvolvedBinary was able to publish the 0.15 version with JAXB 3 support under their name.
Unfortunately they struggeled with the update PR to JAXB 4 so I published again under my coordinates as 0.16.1 version - but I hadn't yet had the time to update the README accordingly.
So if you use com.helger.maven:jaxb30-maven-plugin:0.16.1 you get the latest version of JAXB 3.
A PR definitively gets accepted if it effects the latest version :)

And Issues are enabled again - I disabled then when moving to EvolvedBinary - thanks for the reminder

@phax Thank you, I will try to reproduce it tomorrow and report back!
In general, should I expect that changing the namespace of the binding element from sun/java to jakarta and updating its version attribute to 3.0 is required to run the tool successfully?

I would assume so. But there is also a namespace change from http://java.sun.com/xml/ns/jaxb to https://jakarta.ee/xml/ns/jaxb


Fix for ghc-7.10 and change maintainer

This PR:

Adds a travis file,
adds support for ghc-7.10,
changes the maintainer in the cabal file to me,
changes the url to point to my github repo,
adds a repo section pointing to my github repo and
bumps the version on the patch-level.

I've changed this PR to keep @batterseapower as a maintainer.


Handle overflow target i18n

we can either have the generator try to create the i18n values, or maybe just move this to a hook in the parent?

since overflow is only root level, we can find it by name. this is a bit hacky, and should probably move to a hook


Make Azata's superpower "Favorable Magic" work with spell-like abilities, especially with witch Hexes!!

Thanks for your efforts!!

Are you sure that's not already the case? The code looks like it would work on anything.

After your reply, I did some more testing and found out that the issue stems from "TTT-Reworks - Favorable Magic - reoccurring saves" ... after disabling it, it worked on the first save (guess as intended?) but still fails on incense fog i.e


Support for task lists

How about add support for the task lists?
https://www.markdownguide.org/extended-syntax/#task-lists

Great idea! ❇ Contributions are welcome!

It could be closed 👀


Crop a mesh with bounds param

In the crop function for meshes, until version 2022.4.1, the bounds parameter could be used. This way you could get the crop at a specific point. Now it is only allowed to make a percentage, isn't there another way to get the crop with the bounds again?

Hi, I think I removed that because in principle you may use the cut_with_box() method...
https://vedo.embl.es/autodocs/content/vedo/vedo/pointcloud.html#Points.cut_with_box
Check also
https://vedo.embl.es/autodocs/content/vedo/vedo/pointcloud.html#Points.cut_with_plane
https://vedo.embl.es/autodocs/content/vedo/vedo/pointcloud.html#Points.cut_with_planes


Help to process the apply

Hi @MoonInTheRiver ,
I have apply, please help to process.
Thank you!
Kevin

@MoonInTheRiver
Thank your for release!
But where to find "metadata_phone.csv" or how to generate it?
https://github.com/MoonInTheRiver/DiffSinger/blob/b54d0ef0948f13ecf009386bcbba6a43fcb2a7f8/data_gen/tts/base_binarizer.py#L41

Hi  @MoonInTheRiver
Where is th midi file or how to get the note information?


LUN-132: Tidy up

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.
This PR renames ExercisesScreens to ExercisesScreen (no trailing s) and merges WriteExercise into WriteExerciseScreen.

This makes sense. The merging of WriteExercise and WriteExerciseScreen is now possible as the loading of documents is not done there anymore. So it would be the same for other exercises, maybe you can have a look (or already had) if a refactoring would also make sense there, too?

I did, but I think it only makes sense for the WriteExerciseScreen since for the choice exercises the code is shared and the VocabularyListScreen is way bigger then the WriteExerciseScreen already.


add pose_test to pose_format/

since a method of mine could not find this module before

This file is under src/python/tests, i'm not sure why it was duplicated?

Because one file could not find the module I remember, that's why I have copied it and then it worked fine. I am checking it again.

jup it works just fine even without duplication, sorry!


how to get data from multiple threads?

Currently, a thread-local library is used to collect frames. However, this fails when using multiple threads; the report will only ever contain frames for the thread that started the reporting. So how to report for multiple threads?
I think using a thread local library for collection is the only viable choice (otherwise we'd synchronize cores and thus destroy the performance we intend to measure). Using this for multiple threads would probably require some kind of global library registry (where each thread local would need to be registered on construction, and would also require moving out of the thread on drop). Also we'd need a way to display data from multiple threads without thoroughly confusing users.

Yep, that's a good summary.  I have plans (and something of an implementation) for the data visualization aspect, but haven't really thought about an implementation yet.  Particularly, I don't want to incur any costs for any threads that don't use flame.
I'll do some prototypes when I get the time.

There is a threads() method that has been available for a while!


picocom: fix cross compilation

nix-build -A pkgsCross.aarch64-multiplatform.picocom now succeeds

cross compilation distinguishes between pkg-config to find build-time dependencies and pkg-config to find runtime dependencies, hence we have to reference it via the $PKG_CONFIG environment variable supplied by the stdenv.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build pkgsCross.aarch64-multiplatform.picocom

Sorry about that one! Thanks for the fix, will try to remember to do the cross‐correct thing in future.


fix: Fix processing sparse vector size for getFeatureShaps

Currently getFeatureShaps does not work neither on dense vectors nor sparse ones.
For dense vectors getDenseFeatureShaps is not implemented.
But for sparse vectors error comes earlier: vector.size is int and should be passed further as it is.
This pull request fixes the error with processing field size of sparse vectors

/azp run

Thank you @alexandrseverinov


List all remediation activities incorrect permission

The application permissions show as "RemediationTask.Read.All"; however, the true permission is "RemediationTasks.Read.All" (with an 's').

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

ID: aef23eda-5f78-cdcf-ec94-ea5db4734a84
Version Independent ID: 8b5f28a6-e988-e992-a49e-1d99b3d3687e
Content: List all remediation activities
Content Source: microsoft-365/security/defender-endpoint/get-remediation-all-activities.md
Product: m365-security
GitHub Login: @jweston-1
Microsoft Alias: v-jweston

@MastaDisasta Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6091
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @MastaDisasta Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


TASK: fix deleting problem for web Link

Hi @FahimNsr I miss the compiled plugin code in your PR. You need the commit the compiled plugin code otherwise your changes will not be use, when this package is installed in a project. Please the missing code changes. Thank you.

Hi @andrehoffmann30, I added the compiled file.


Fix / old password form error after validation

This PR

Adds a missing translation for when the old password is not correct after submitting the 'Password reset' form (I've used the error message obtained from the API)
Updates the password fields to include the autocomplete attribute to improve accessibility
Solves: OTT-1071

You're now trying to match the filled in old password with the new password. That's never what we want, right? The user wants to change it.
We should let the backend validate the old password and just present the api error.


overly strict type inference?

The following throws an error that 0 is not a single-float:
(TEDDY/DATA-FRAME::MAKE-DATA-FRAME
   '("subject" "time" "conc")
   :ROWS '(("1" 0.5 0.94) ("1" 0 0.78)))

Perhaps we should be a bit more flexible with the types of values passed to make-data-frame?

I think that being strict on typing makes sense. However, here you would need to scan for the common type, and it seems to be complicated? Why even bother, either assume T or expect explicit type information.

I'm not quite sure what you're suggesting. My take is that the example I provided should work. If I were to supply a type, sure, use that, but if I don't, don't just use the type of the first seen element. I guess there's a use case for that but the default should be more developer/user-friendly IMO.

I am suggesting that everything should be assumed to be T, unless the explicit type is provided by the user (which is what CL ordinarily does in most places).


Bug Report: when i use a new use a new chart insted of the normal one the game makes me go on the basic stage it doesn't depend on witch week

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
What version of the game are you using? Look in the bottom left corner of the main menu.
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Please describe your issue. Provide extensive detail and images if possible.

Stages don't load as they are no longer hard coded to the weeks, but instead being loaded by the chart #334

just go in the chart editor and change the stage property


Loc Update

@khoiph1 do we still need this update since I merged your newer PR https://github.com/Microsoft/azuredatastudio/pull/3548?


compare two files

Im not yet good at perl , and cant understand easily how your software works.
But I tried to run it on my files, and the result not obvious for me. Could you answer a questions.

Is it compare files cell by cell ? I saw this on my initial test files with just 2 rows and 2 columns. But when I tried on my little bigger files with 20 rows and 20 columns, your package always returned to me "Files identical" even when I change data in one cell in one file.

My files are very easy to compare, no formulas and not as big, just ~20 rows and ~20 and I do not want to write my own solution on languages I know better. More likely I will learn perl deeper if your package can help me. But in a description of it "It compares 2 files visuality" what is mean ?

Thanks you.

Hi,
I can explain you how this work but before that I would like to test why you are getting incorrect result. Therefore can you please send me your sample excel file (with 20 rows/20 columns) that failed your test?
Thanks for using my code.
Best Regards,
Mohammad S Anwar

Mailed to your @yahoo mail account.
Thanks

Hi,
I have just pushed the patch to resolve the issue you raised as below (Test::Excel v1.30):
https://github.com/Manwar/Test-Excel/commit/46f19f76e198cc658720b492ea19f8a7cdc59f27
Hope this should solve the issue. Please let me know if you have any problem.
Many Thanks.
Best Regards,
Mohammad S Anwar

Hi,
Thanks for sample files. I used my own sample files to re-create the issue at my end. It now works with your sample files as well.I have pushed another quick fix to the DEBUG field in (Test::Excel v1.31) as below:
https://github.com/Manwar/Test-Excel/commit/d69ff512f420a7e058b2d5abebb81c51918c6988
use strict; use warnings;use Test::Excel;
if (compare_excel("1.xls", "2.xls")) {   print "EXCELs are identical.\n";}else {   print "EXCELs are NOT identical.\n";}
Please refer to the documentation as the interface has slightly changed, to make it simple.
Best Regards,Mohammad S Anwar
"You can sometimes write faster code in C but you can always code faster in Perl."
 On Saturday, 14 February 2015, 20:27, Alexander Pletnev<EMAIL_ADDRESS>wrote:

Mailed to your @yahoo mail account.
Thanks
—
Reply to this email directly or view it on GitHub.

Hi Alexander,
I have made further changes and added two new methods to ease the use (Test::Excel v1.33).
https://github.com/Manwar/Test-Excel/commit/af94d12397dd8a386c798b6edacda75f7ebddf91
use strict; use warnings;
use Test::More;
use Test::Excel;
cmp_excel_ok("1.xls", "1.xls");
cmp_excel_not_ok("1.xls", "2.xls");
done_testing();

Here is the output of of last example
no_plan takes no arguments at ./test.pl line 4.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
ok 1
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
Use of uninitialized value $iFnt in array element at  line 2621.
ok 2
1..2
The plan was already output at perl5/lib/perl5/Test/Builder.pm line 2510.
1..2

Suppose it still not compare them correctly.

Except the warning, which is thrown by package outside of distribution, the  result is correct.

Ah yes, sorry noticed now that first test compares the same file.
Do you plan to show at least positions of different cells?
I remember, that when I first time run your software with simple files there was an output:
BBB not equal to CCC

Yes, you can get that if you set the environment variable DEBUG to 1.

Thank you very much for sorting my issue.
I will be using your package in my project. It will be first perl
dependency. But I suppose it's only a start.
Thanks

Hi Alexander,
Just to let you know, I have disabled the warning thrown by the external package. Also documented the use of environment variable DEBUG. And added SYNOPSIS as well.
The updated package is Test::Excel v1.36
Best Regards,
Mohammad S Anwar


fix transient blossom icd reset timing

correction to the transient blossom icd reset timing, where the timing is now after the construct has been created, as opposed what used to be when the skill was used. source: https://discord.com/channels/763583452762734592/763610791839924224/1001895536552595536
this issue used to give rise to bugs like what happens in here (https://gcsim.app/viewer/share/heOJY9AJNuV7PON6x3psV) at the 25.92s mark.

@MrPillow1 Shizuka added fix to next on https://github.com/genshinsim/gcsim/pull/652 so will be closing this


Add max a saga execution time, and fail the saga if it reaches this point

Add rerun with retries for the complete saga


Add basic background jobs

Adds the following background jobs:

[x] save-received-messages
[x] get-received-messages
[x] save-tosend-message
[x] get-tosend-messages
[x] save-grant-call
[x] get-grant-calls
[x] save-profile
[x] get-profiles

The latest work on the AI Python API has been merged. Having the call-plugin makes no sense anymore as the supervisor is in Python.


Use commonjs for dependency management

@jbeezley does your branch need something from @manthey on-going work?

I'm rebasing now.  It's still going to take a solid few days of work to finish up.

I'm rebasing now. It's still going to take a solid few days of work to finish up.

Sounds good @jbeezley