NPC Drops

Add a drop system for npcs

I'd suggest making a DSL for this which would allow for all sorts of possibilities which are not possible to represent in JSON, such as dropping an item with a given rarity if a particular quest is at a certain stage while wielding a specific item.

@notmeta Been thinking of the best way to approach it. A global npc drop system may not be worth it, but still thinking it over. It's either

Define all drops as plugins in KotlinScript (similar to how all drops are defined on 07)
Define "misc" drops for npcs externally and handle complex drops through plugins

@notmeta It's either
1. Define all drops as plugins in KotlinScript (similar to how all drops are defined on 07)

2. Define "misc" drops for npcs externally and handle complex drops through plugins

Personally I'd keep them all in one place and go for the former choice.

@notmeta I was also leaning towards that option, so will probably move forward with that. Thanks for the feedback!


Can order between JSON and files be controlled in multipart form?

I'm wondering if the order between JSON fields and file attachments can be controlled.
I need to test my api by having files come before JSON data in the stream. It seems that httpie always sends JSON first and then files.

Currently it's not possible but I'll see if something can be done about that.

@jakubroztocil That would be awesome. This should be useful for everyone with my use case.
My use case:

Receiving multipart form via email
Attached files needs to be processed
Email needs to be validated by checking field data

In some rare cases I'm receiving files before fields (I'm using Sendgrid mail parse). When this happens I need to buffer the files and wait for the fields in order to know what to know with the files.
It would be great to use httpie to test this edge case.

Buy Valid Cvv CC Dumps Track 1/2 CC SSN DOB Track-1/2-FULLZ-Transfer/Western union Bank-Log-In-PayPal-Transfer-and-Log-In Buy/sell CVV CC DOB SSN FULLZ - Dumps Pin...
Telegram.@Ykidven
Cc Format Is
Format is:
Card Number | Exp. Date | CVV/CVV2 | First Name | Last Name | Street | City
| State | Zip Code | Country | Phone | Type Of Card | Bank Name
I'm Loading All Types Of Paypal Account With No ChargeBacks... Cash app Loading I Can Load All Non Verified Account with No Problem Or Verified PayPal Account..I Even Sell Paypal Logs At Cheap Prices....Pm Me If You Interested In Loading Your Paypal Account
Telegram.@Ykidven
Paypal Transfer Price List
20$ for 250$
30$ for 350$
40$ for 400$
50$ for 500$
60$ for 600$
70$ for 700$
80$ for 800$
90$ for 950$
100$ for 1500$
CashApp Transfer Price List
20$ for 250$
30$ for 350$
40$ for 400$
50$ for 500$
60$ for 600$
70$ for 700$
80$ for 800$
90$ for 950$
100$ for 1500$
200$ for 3000$
Telegram@Ykidven
Doing Wu Transfers
I Am Doing Wu Transfer Here And I Need I Very Serious Buyer Who Also Want To Work With Me And Make Money With Me Here...
Note...i will Do The Transfer Then After you Track The Mtcn You Make Payment Before you have the sender's Info
Western Union Price List
30$ for 350$
40$ for 400$
50$ for 500$
60$ for 600$
70$ for 700$
80$ for 800$
90$ for 950$
100$ for 1500$
200$ for 2500$
Telegram.@Ykidven
Telegram.@Ykidven
Telegram.@Ykidven
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

You can't

@msageryd HTTPie in master preserves the field ordering (will be included in v2.3.0).

Wow, great work!
Sent from my iPhone
On 28 Sep 2020, at 13:55, Jakub Roztocil<EMAIL_ADDRESS>wrote:

@msagerydhttps://github.com/msageryd HTTPie in master preserves the field ordering (will be included in v2.3.0).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/httpie/httpie/issues/903#issuecomment-699960371, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABCGQDMRIZ25DRFUOCQGGE3SIB2SLANCNFSM4MQAYRSQ.


The OptimizeMiddlewarePlacement option doesn't exist

It's mentioned in the documentation (README), but I don't see anything in the code?

Good spot. It's no longer needed. It's always optimized ;)


[3.x] Composable not auto-imported

Environment
nuxt 3.13
Reproduction

Describe the bug
It seems that useGtag() composable is not auto-imported in layout file
Additional context
No response
Logs
No response

Thanks for the report! Please follow the issue convention and provide a reproducible example. You can use one of the templates below to create a minimal reproduction:
👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/p/github/nuxt/starter/v3-codesandbox
Thanks in advance!

Ok i've got it... it seems that now when enabled flag is false, nuxt doesn't import the composable anymore

You're right. With v3, the enabled module option now controls whether the module should be active for your project at all. If the module is disabled, the composables won't be importable.

Hi,
Sorry to add to a closed ticket, but we also got hit by a similar issue.
As per the documentation, we started using the following:
gtag: {
    enabled: process.env.NODE_ENV === 'production',
    id: 'G-XXXXXXXXXX'
}

Which in fact disables the module when in development.
But then everywhere that we're calling useTrackEvent, we're now getting console errors that the function is not defined.
On some cases, for example if we're calling it inside a try/catch block, then the catch get's triggered when on development.
It would be useful to have a way to disable the sending of analytics when not in production without disabling the importing of the composables which forces us to add an if check everytime we call the composable.
Maybe have the composables just return void when disabled or something (?)
Just a thought.
Thank you, cheers

I hear your! With the latest version, composables like useGtag and useTrackEvent are still importable when the module is disabled. In this case, the functions are replaced with no-ops to avoid type and logic errors.


GCC/MinGW 32-bit compilers don't work on 'windows-latest'

Description:
There are two 32-bit C compilers that come with the MSYS2 installation on 'windows-latest':
/c/msys64/mingw32/bin/gcc (the GNU GCC)
/c/msys64/mingw32/bin/i686-w64-mingw32-gcc (the MinGW GCC)
Both of these seem to not have been installed properly on the 'windows-latest' runner machine.
I am unable to compile a simple helloworld.c file with them (and no error is given: the process simply exits out, returning exit code '1').
Furthermore, simply attempting to show the compiler version info (with the -v verbose flag) does a similar crash/exit:

/c/msys64/mingw32/bin/gcc -v --version
/c/msys64/mingw32/bin/i686-w64-mingw32-gcc -v --version

Both of the commands written above crash and return exit code 1, which should never be the case. Because of this behavior, I am confident there was a problem during installation of MSYS2 (perhaps windows "run as administrator" mode was not enabled when installing ?)
Area for Triage:
C/C++
Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Expected behavior
The two 32-bit compilers should not crash halfway when showing version info, and should be able to compile a helloworld test.
Actual behavior
The two 32-bit compilers seem to be corrupt in some way, invoking these 2 programs always fails.
Repro steps

On a 'windows-latest' runner, try the following commands:

/c/msys64/mingw32/bin/gcc -v --version
/c/msys64/mingw32/bin/i686-w64-mingw32-gcc -v --version

Also, try to use both compilers to compile a simple helloworld, like this one for example:

#include <stdio.h>

int main(int argc, char** argv)
{
	printf("Hello world!\nprogram args:\n");
	for (int i = 0; i < argc; ++i)
	{
		printf("\t%s\n", argv[i]);
	}
	return (0);
}

@MSP-Greg , @eregon, as MSYS2 experts, could you please help us with it? We install these compilers in  mingw32 packages via pacman, maybe there are any additional settings to install it?

@MSP-Greg , @eregon, as MSYS2 experts, could you please help us with it? We install these compilers in  mingw32 packages via pacman, maybe there are any additional settings to install it?

@vsafonkin
I'm looking at it...

@vsafonkin
I'm looking at it...

@LexouDuck
Not sure about this.  Both the below run from steps using the default shell.  See MSYS2 gcc 32 bit.
Your above comment shows *nix paths, so you may need to adjust $PATH to run the 32 bit?
$env:Path = "C:/msys64/mingw64/bin;C:/msys64/usr/bin;$env:Path"
gcc -v --version

$env:Path = "C:/msys64/mingw32/bin;C:/msys64/usr/bin;$env:Path"
gcc -v --version

@LexouDuck
Not sure about this.  Both the below run from steps using the default shell.  See MSYS2 gcc 32 bit.
Your above comment shows *nix paths, so you may need to adjust $PATH to run the 32 bit?
$env:Path = "C:/msys64/mingw64/bin;C:/msys64/usr/bin;$env:Path"
gcc -v --version

$env:Path = "C:/msys64/mingw32/bin;C:/msys64/usr/bin;$env:Path"
gcc -v --version

Ah, my bad - I forgot to mention that I do use the bash shell as default (in fact, you did find, and linked, the previous issue I made where i mentioned this as a solution)
defaults:
  run:
    shell: bash

I believe this uses the "git bash" shell that typically comes with windows installations of git, right ? I am not very familiar with that shell, I typically use cygwin.
It might be, like you say, a $PATH problem - but then that would mean i need to replace the exisiting mingw64 folder in the PATH with the mingw32 one instead ?
Note that I am using the' windows-latest' runner to both compile 64-bit, and "cross-compile" 32-bit.
Furthermore, here is the YML script for the job I was running to test that it functions properly:
    - name: Build (with ${{matrix.compiler}}, for 'windows-latest')
      if: matrix.os == 'windows-latest' && matrix.compiler == 'gcc'
      run: |
        /c/msys64/mingw64/bin/x86_64-w64-mingw32-gcc -v --version
        echo "debug"
        /c/msys64/mingw32/bin/i686-w64-mingw32-gcc -v --version
        echo "debug"
        /c/msys64/mingw32/bin/i686-w64-mingw32-gcc -o main -Wall -Wextra -Winline -Wpedantic -D__USE_MINGW_ANSI_STDIO=1 ./lib/libccc/test/_helloworld.c
        echo "COMPILED HELLOWORLD"
        ./main
        echo "RAN HELLOWORLD"
        make release CC=/c/msys64/mingw32/bin/i686-w64-mingw32-gcc OSMODE=win32

What is surprising to me is that /c/msys64/mingw64/bin/x86_64-w64-mingw32-gcc (64-bit) works just fine, but /c/msys64/mingw32/bin/i686-w64-mingw32-gcc (32-bit) can't even show version info ? What sort of PATH problem would cause that ?

Ah, my bad - I forgot to mention that I do use the bash shell as default (in fact, you did find, and linked, the previous issue I made where i mentioned this as a solution)
defaults:
  run:
    shell: bash

I believe this uses the "git bash" shell that typically comes with windows installations of git, right ? I am not very familiar with that shell, I typically use cygwin.
It might be, like you say, a $PATH problem - but then that would mean i need to replace the exisiting mingw64 folder in the PATH with the mingw32 one instead ?
Note that I am using the' windows-latest' runner to both compile 64-bit, and "cross-compile" 32-bit.
Furthermore, here is the YML script for the job I was running to test that it functions properly:
    - name: Build (with ${{matrix.compiler}}, for 'windows-latest')
      if: matrix.os == 'windows-latest' && matrix.compiler == 'gcc'
      run: |
        /c/msys64/mingw64/bin/x86_64-w64-mingw32-gcc -v --version
        echo "debug"
        /c/msys64/mingw32/bin/i686-w64-mingw32-gcc -v --version
        echo "debug"
        /c/msys64/mingw32/bin/i686-w64-mingw32-gcc -o main -Wall -Wextra -Winline -Wpedantic -D__USE_MINGW_ANSI_STDIO=1 ./lib/libccc/test/_helloworld.c
        echo "COMPILED HELLOWORLD"
        ./main
        echo "RAN HELLOWORLD"
        make release CC=/c/msys64/mingw32/bin/i686-w64-mingw32-gcc OSMODE=win32

What is surprising to me is that /c/msys64/mingw64/bin/x86_64-w64-mingw32-gcc (64-bit) works just fine, but /c/msys64/mingw32/bin/i686-w64-mingw32-gcc (32-bit) can't even show version info ? What sort of PATH problem would cause that ?

What is surprising to me is that...

I did try to repo locally, and couldn't.
I've never used the bash shell much on Windows, and lately I've been working with WSL2/Ubuntu.
Re MSYS2, most of the work I've done is is 'configure, make, make check/test, make install', and that often requires the path to be setup correctly.  Hence, I always do that.  I also haven't used the 32 bit tool chain for a while...

What is surprising to me is that...

I did try to repo locally, and couldn't.
I've never used the bash shell much on Windows, and lately I've been working with WSL2/Ubuntu.
Re MSYS2, most of the work I've done is is 'configure, make, make check/test, make install', and that often requires the path to be setup correctly.  Hence, I always do that.  I also haven't used the 32 bit tool chain for a while...

@LexouDuck , I've tried to add mingw32 to the PATH and it works for me:
- name: add mingw32 to path
      shell: bash
      run: |
        echo "C:\msys64\mingw32\bin" >> $GITHUB_PATH

    - run: i686-w64-mingw32-gcc --version

    - name: compile helloworld.c
      run: |
        i686-w64-mingw32-gcc -v helloworld.c -o helloworld
        $LASTEXITCODE

build: https://github.com/vsafonkin/test-repo/runs/1804678077?check_suite_focus=true
@MSP-Greg thank you for your help!

Closed, @LexouDuck feel free to reopen it if you have any issues.


pass surveyEngine instance on response changed

Add surveyEngine in the onResponseChanged
This allow an external component to capture the current evaluation context and check expression evaluation (needed for survey_viewer evaluation inspector extension)

Would it work if the argument is optional? (So interface form outside does not need to include this necessarily?

I think yes (if the engine instance is actually passed), but If you prefer I can add an extra callback (so it's provided only if the callback is defined and the interface of response callback wont change)


Make it possible to handle local variables.

First of all: Thank you for creating this repo - idea is amazing!
This PR adds support for node.type=:lvar (i.e.: local variable). Effectively enabling this code:
# defintions
macro validate_num(name)
  fail "Invalid number #{~{name}.inspect}" unless ~{name}.is_a?(Numeric)
end

# code
def add(a, b)
  validate_num(a)
  validate_num(b)
  r = a + b
  validate_num(r)
  r
end

While adding support for this, I have noticed, that parameters of macro get converted from AST to string before inserting doing substitution. This way lvar (local variable) loses its context and there is no possibility to understand if it is a local variable when it tries to parse it back to AST.
Solved this problem in very hacky way: local variable string representation include assignment to itself, forcing it to be a local variable at parse time, but not changing behavior.
It looks ugly:
def add(a, b)
  unless (a = a
  a).is_a?(Numeric)
    fail("#{(a = a
    a).inspect} is not a number")
  end
  unless (b = b
  b).is_a?(Numeric)
    fail("#{(b = b
    b).inspect} is not a number")
  end
  r = (a + b)
  unless (r = r
  r).is_a?(Numeric)
    fail("#{(r = r
    r).inspect} is not a number")
  end
  r
en

WDYT? Any other ideas how to make them work?

Might be possible to fix this hack if this resolves successfully: https://github.com/whitequark/parser/issues/200

Hm, now that I think about it. Let me mark this PR as a WIP, since I think I have found a problem: it will not handle nested AST tree with local variables deeper than first level.


Enhancement: func (s *DB) And(query interface{}, args ...interface{}) *DB

How can Go users form the intersection of two Where sub-conditions?
I see an Or() but no And().

db.Where("id = ?", 1).Where("name = ?", "test").Find(...)

generate
SELECT * FROM `tests`  WHERE (id = 1) AND (name = 'test')


Update cloudwatch, dynamodb, kinesis, s3, sns, ... to 2.16.31

Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:dynamodb
software.amazon.awssdk:kinesis
software.amazon.awssdk:s3
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:sts

from 2.16.25 to 2.16.31.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #642.


Config options

Can`t use localized-strings options in constructor described here
Need to modify TS types

You linked to another package, this is react-localization. Use this API: https://github.com/stefalda/react-localization#api


Remove Create a public IP address

On line 216 it mentions to create a new public IP using VNet-Onprem-GW-pip as the name so you don't need to create it before hand.

@markaldridge : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


[SPARK-29022][SQL][test-hadoop3.2][test-java11] Fix spark 'add jar', CliSessionState's hiveConf 's classLoader ClassNotFound

What changes were proposed in this pull request?
For issue mentioned in SPARK-29022
Spark SQL CLI can't use class in jars add by SQL 'ADD JAR'.
When we create table with Serder class added by SQL 'ADD JAR', we can create table with class check success since when we call HiveClientImpl.createTable, it's under withHiveState method, it will add sparkSession.sharedState.jarClassLoader to SessionState.hiveConf.classLoader. when we check serder class, it will use HiveCLientImple's SessionState's classLoader. 'ADD JAR''s jar will be add to sparkSession.sharedState.jarClassLoader. Then it will success.
When we select data from this table, when call method HiveTableScanExec#addColumnMetadataToConf()
, when check for table desc serder class.
val deserializer = tableDesc.getDeserializerClass.getConstructor().newInstance()
    deserializer.initialize(hiveConf, tableDesc.getProperties)

getDeserializer will  use CliSessionState's hiveConf's classLoader in SparkSQLCLI case.
But when we call 'ADD JAR' in spark, the jar will add to Spark's Jar classLoader.
So when we use 'ADD JAR ' to add jar for Serder, will failed, since jar was add to Spark's jar classLoader.
Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
ADD UT

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Hi, @AngersZhuuuu . Is the JIRA issue ID correct? SPARK-29051 ?

Hi, @AngersZhuuuu . Is the JIRA issue ID correct? SPARK-29051 ?

Sorry, I forgot to change it.  This PR should wait for  https://github.com/apache/spark/pull/25542

@dongjoon-hyun @srowen Maybe we can fix this issue by another PR: #25775

OK so this should resolve the same issue? are there arguments for against this change vs the other?

@srowen @dongjoon-hyun @wangyum
I have add a new UT for this issue to cover case  use hive.aux.jars jar's class as serde.
#25775  can't solve problem of this issue.

Can one of the admins verify this patch?

Test build #110645 has started for PR 25729 at commit ce45394.

Test build #110645 has finished for PR 25729 at commit ce45394.

This patch fails Spark unit tests.
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/110645/
Test FAILed.

Test build #110673 has started for PR 25729 at commit 1d60b90.

Test build #110673 has finished for PR 25729 at commit 1d60b90.

This patch fails Spark unit tests.
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/110673/
Test FAILed.

Test build #110714 has started for PR 25729 at commit 5486f75.

Test build #110714 has finished for PR 25729 at commit 5486f75.

This patch fails PySpark unit tests.
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/110714/
Test FAILed.

@dongjoon-hyun  latest build failed , seems not my change's problem.

This PR should test with default behavior, [test-hadoop3.2] and [test-hadoop3.2][test-java11].

Test build #110755 has started for PR 25729 at commit 5be7f3e.

Test build #110764 has started for PR 25729 at commit 927130b.

Test build #110755 has finished for PR 25729 at commit 5be7f3e.

This patch fails PySpark unit tests.
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/110755/
Test FAILed.

Test build #110764 has finished for PR 25729 at commit 927130b.

This patch fails PySpark unit tests.
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/110764/
Test FAILed.

The last python two failures look consistent. Could you take a look if it's relevant?

The last python two failures look consistent. Could you take a look if it's relevant?

Look the test of python, it won't use code I have changed. and you can see the third  build from last  BUILD  and my latest two commit, I just modify UT and add some comment.  Two test result  success no w

Test build #110899 has started for PR 25729 at commit 88169fc.

Test build #110899 has finished for PR 25729 at commit 88169fc.

This patch fails to generate documentation.
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/110899/
Test FAILed.

Test build #110900 has started for PR 25729 at commit 4a18ceb.

Test build #110900 has finished for PR 25729 at commit 4a18ceb.

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/110900/
Test PASSed.

https://github.com/apache/spark/pull/25775 is merged. I'm not clear if this change is still needed, and if so, if it just needs to be retested?

retest this please

Test build #111545 has started for PR 25729 at commit 4a18ceb.

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-K8s/16558/
Test PASSed.

Test build #111545 has finished for PR 25729 at commit 4a18ceb.

This patch fails to build.
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/111545/
Test FAILed.

#25775 is merged. I'm not clear if this change is still needed, and if so, if it just needs to be retested?

Not same issue, still need this. Checking for reason of build failed.

This PR is needed. but this change can not handle isolatedLoader is enabled(spark.sql.hive.metastore.jars != builtin). It seems this commit can handle this case. But we can not add a test case for this case because of SPARK-29268.

Test build #111551 has started for PR 25729 at commit 7692893.

Test build #111551 has finished for PR 25729 at commit 7692893.

This patch fails to build.
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/111551/
Test FAILed.

Test build #111553 has started for PR 25729 at commit d070059.

Test build #111554 has started for PR 25729 at commit fcfd7af.

Test build #111553 has finished for PR 25729 at commit d070059.

This patch fails Spark unit tests.
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/111553/
Test FAILed.

Test build #111554 has finished for PR 25729 at commit fcfd7af.

This patch fails Spark unit tests.
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/111554/
Test FAILed.

Test build #111565 has started for PR 25729 at commit db63cf2.

Test build #111565 has finished for PR 25729 at commit db63cf2.

This patch fails Spark unit tests.
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/111565/
Test FAILed.

Test build #111568 has started for PR 25729 at commit 918941e.

Test build #111568 has finished for PR 25729 at commit 918941e.

This patch fails PySpark pip packaging tests.
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/111568/
Test FAILed.

Test build #111583 has started for PR 25729 at commit 72d4d84.

Test build #111583 has finished for PR 25729 at commit 72d4d84.

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/111583/
Test PASSed.

@dongjoon-hyun
Passed jdk11 test,  I have changed the title, thanks for trigger build for jdk8 & hadoop3.2.

retest this please

Test build #111598 has started for PR 25729 at commit 72d4d84.

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-K8s/16601/
Test PASSed.

Test build #111598 has finished for PR 25729 at commit 72d4d84.

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/111598/
Test PASSed.

retest this please

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-K8s/16602/
Test PASSed.

Test build #111599 has started for PR 25729 at commit 72d4d84.

Test build #111599 has finished for PR 25729 at commit 72d4d84.

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/111599/
Test PASSed.

Merged to master


Add reference to central entities table in EEA

Summary
This adds a nullable reference to the central entities table in the EEA
tables. This will simplify the EEA as we won't need to check multiple
tables anymore. However, we can't just migrate to it in one go; we need
to first duplicate the data then do it.
Closes: https://github.com/stacklok/minder/issues/4167
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.937% (-0.008%) from 53.945%
when pulling 3d5d368c854f7a58c0af5742c1ff7086be25138f on eea-entity-instance-in
into 6657fd84fa8cabef1678b37f9ac47949e6a9c838 on main.


Assertion error when comparing field by field is no longer as informative

class Person {
    public String getFirstName() {
        return firstName;
    }

    public String getLastName() {
        return lastName;
    }

    private String firstName, lastName;

    public Person(String firstName, String lastName) {
        this.firstName = firstName;
        this.lastName = lastName;
    }
}

class PersonDAO {

    public String getFirstname() {
        return firstname;
    }

    public String getLastname() {
        return lastname;
    }

    public Long getId() {
        return id;
    }

    public Integer getAge() {
        return age;
    }

    private String firstname, lastname;
    private Long id;
    private Integer age;

    public PersonDAO(String firstname, String lastname, Long id, Integer age) {
        this.firstname = firstname;
        this.lastname = lastname;
        this.id = id;
        this.age = age;
    }
}

Person person = new Person("John", "Doe");
PersonDAO personDAO = new PersonDAO("John", "Doe", 1L, 23);

assertThat(person).isEqualToComparingFieldByFieldRecursively(personDAO);

In AssertJ 3.6.2, an IntrospectionError was thrown when a field or property was missing/different when comparing one object to another of two different types. In this case, Person contains FirstName and LastName whereas PersonDAO contains Firstname and Lastname.
Exception in thread "main" org.assertj.core.util.introspection.IntrospectionError:
Can't find any field or property with name 'firstName'.
Error when introspecting properties was :
- No getter for property 'firstName' in PersonDAO
Error when introspecting fields was :
- Unable to obtain the value of the field <'firstName'> from <PersonDAO@506c589e>
	at org.assertj.core.util.introspection.PropertyOrFieldSupport.getSimpleValue(PropertyOrFieldSupport.java:79)
	at org.assertj.core.internal.DeepDifference.initStack(DeepDifference.java:327)
	at org.assertj.core.internal.DeepDifference.determineDifferences(DeepDifference.java:153)
	at org.assertj.core.internal.Objects.assertIsEqualToComparingFieldByFieldRecursively(Objects.java:711)
	at org.assertj.core.api.AbstractObjectAssert.isEqualToComparingFieldByFieldRecursively(AbstractObjectAssert.java:632)
	at Main.main(Main.java:20)

In 3.7.0 and above, only the following is returned:
Exception in thread "main" java.lang.AssertionError:
Expecting:
  <Person@7aec35a>
to be equal to:
  <PersonDAO@67424e82>
when recursively comparing field by field, but found the following difference(s):

Path to difference: <>
- expected: <PersonDAO@67424e82>
- actual  : <Person@7aec35a>

Requires a lot more work to figure out exactly why the assertion fails, especially when the objects become much more complex and interfaces are included. Would be good if the original error information could be returned like it was in 3.6.2.

I was thinking to change the error returned to show all the missing fields, ex:
Employee employee = new Employee();
EmployeeOfTheMonth employeeOfTheMonth = new EmployeeOfTheMonth();

assertThat(employeeOfTheMonth).isEqualToComparingFieldByFieldRecursively(employee);

The assertion fails with the error:
Expecting:
  <org.assertj.examples.custom.EmployeeOfTheMonth@6591f517>
to be equal to:
  <org.assertj.examples.custom.Employee@345965f2>
when recursively comparing field by field, but found the following difference(s):

Path to difference: <>
- expected: <org.assertj.examples.custom.Employee@345965f2>
- actual  : <org.assertj.examples.custom.EmployeeOfTheMonth@6591f517>
- reason  : org.assertj.examples.custom.EmployeeOfTheMonth can't be compared to org.assertj.examples.custom.Employee as Employee does not declare all EmployeeOfTheMonth fields, it lacks these:[month]

@markstamatiades WDYT ?

Looks reasonable to me. So if there is more than one missing field it will list them all rather than just the first one it hits, right?

What would the message be if the fields had the same name but were of differing types?

@markstamatiades yes it would show all the missing fields
@rossmasday I haven't tried but there would be no message as the field names are matching but when comparing their values it will likely fail.


Build processes for Canada and mexico for import to US

We had existing code for this that worked for the template writer. This has not been updated to work for JSON-LD output. This would include flow name updates.  I have moved the old code for this to a new branch

This is partially complete - using ELCI_1, processes from Canada are created using a combination of Canada technology mixes (coal, gas, hydro, etc.) and applying those mixes against US-average profiles for those same technologies.
I'll rename the issue to reflect only Mexico.


nuxt run dev takes too long after adding dynamic URLs with options: urls

Details
I made a function that creates dynamic routes with various number of URLs. And, after this npm run dev started taking too long to process since it's generating the sitemap preview for each build. Is it possible to only generate a sitemap on nuxt build command?
['nuxt-simple-sitemap',
    {
        hostname: process.env.BASE_URL,
        urls: () => {
            return Promise.all([
                axios.get(URL),
            ]).then(([courses]) => {
                return [
                    convertObjToSitemapByCourse(courses, 'course', 'monthly'),
                ].reduce((accumulator, currentValue) => accumulator.concat(currentValue), []);
            }).catch((e) => {
                console.log(e);
            });
        }
    }
]

You can check NODE_ENV.
urls: () => {
  if (process.env.NODE_ENV === 'production') {
    return []
  }
}

Hi, you can check NODE_ENV
{
  enabled: process.env.NODE_ENV === 'production'
  urls: () => {
    ...
  }
}

why didn't I come up with that!? Thank you!


Remove docs/setup/production-environment/turnkey/clc.md to follow v1.18 of the original text

I removed the content/ja/docs/setup/production-environment/turnkey/clc.md to follow v1.18 of the original (English) text.
The following link is the differences between v1.17 and v1.18:
https://gist.github.com/38797d234b49a7181f9939aefc3bd020
This PR fixes this issue:
#26518
Note:
The en file has been removed.
#17514 is the issue at that time.

/approve

/lgtm

@makocchi-git mergeされたら元Issueが閉じてるかどうかまで見てもらえると～


Multiple entities of the same kind

Rasa NLU version: 0.11.3
Operating system : Windows 10
Content of model configuration file: I have used the following pipeline. ner_crf and ner_duckling are used for entity extraction.
"pipeline": ["nlp_spacy", "tokenizer_spacy", "intent_entity_featurizer_regex", "intent_featurizer_spacy", "ner_crf", "ner_synonyms", "ner_duckling", "intent_classifier_sklearn"]

Issue:
Hello everyone.
I have trained a model to detect activities as entities. And I have included the duckling extractor for extracting structured time values. But when I parse a sentence like
I want to go running in the morning
ner_crf does give me 'go running' as an activity and duckling does detect 'in the morning' as a time entity. - But ner_crf is doing something I didn't train it for and is detecting 'the morning' as an activity entity. (What I expected the NLU to give me is 'go running' as the only activity entity.)
Based on @tmbo 's answer in #427 I can see that this is due to how ner_crf works. And trying some more examples I found that it is misclassifying words with suffix 'ing' as activities (maybe caused by the training data).
So my questions are:

How do I prevent this misclassification? (It's blatantly wrong to understand morning as an activity).
How would you suggest one could resolve issues where the NLU returns more than one entity of the same kind, if only one is expected, and is to be stored in a slot? (Right now I am not using Rasa Core due to lack of data. But I imagine more people have/also face this issue and could give some pointers.)

Here is a sample of my training data:
## intent:inform_activity
- i want to [learn drama](activity)
- i want to [go running](activity)
- i would like to [go bodybuilding](activity) everyday
- i like to [practice juggling](activity)

I have generated and used ~900 such sentences for the same intent and with activity entities.

actually, can you try updating to rasa_nlu==0.11.5 first ? We recently noticed some bugs with ner_crf, so this might also be causing the problem.

@akelad Thanks for the suggestion. I will try that.
Also I have managed to temporarily overcome the problem by adding some more training data like :
- i want to [play basketball](activity) in the morning
- i want to [play basketball](activity) in the evening

But I could still use help with general ways to handle situations where the NLU extracts multiple entities of the same kind, that would be great.

I guess I'll have to figure something out on my own.   If you want version 0.11.5, run pip install rasa_nlu==0.11.5
The approach you're going with should work fine, and i think with the upgrade it shouldn't recognize "in the morning" anymore. Try upgrading and then let us know if you're still having those issues

I am planning to upgrade to the latest and try the new tensorflow embedding pipeline.
Thanks for the help.
Closing the issue now.

What type of bug in ner_crf you guys noticed? @akelad

it was only training on examples with labeled entities and therefore had no negative examples of sentences with no entities. so it was wrongly recognising entities in pretty much all sentences


Issue with k8s.io/docs/concepts/overview/working-with-objects/namespaces/

This is a...

[ ] Feature Request
[x ] Bug Report

Problem:
At the bottom of the page it talks about "kubectl api-resources" command.
I am running version v1.10.0 of kubectl and that command is invalid.  Here's the output i see.
$> kubectl api-resources --namespaced=true
Error: unknown command "api-resources" for "kubectl"
Run 'kubectl --help' for usage.
unknown command "api-resources" for "kubectl"
Proposed Solution:
update documentation to say in which versions of kubectl that command will work.
Page to Update:
https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/

$> kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.11", GitCommit:"1bfeeb6f212135a22dc787b73e1980e5bccef13d", GitTreeState:"clean", BuildDate:"2018-09-28T21:35:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

@tpstaples "kubectl api-resources" command is only exists in v1.11 and later versions.
ref: https://github.com/kubernetes/kubernetes/pull/42873
The default version of site-docs is following the K8S release, and now the "https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/" is describe the v1.12.
You can select a different version via the drop down button in the top right corner of the page.
And there are no "kubectl api-resources" command describe in v1.10/v1.9:
https://v1-10.docs.kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
https://v1-9.docs.kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/

If there are no more questions, I will close this issue, thanks.
The following is the execution result of v1.12, for reference. :smiley:
 ⚡ root@k8s  /home/ubuntu  kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"archive", BuildDate:"2018-10-29T06:56:23Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"archive", BuildDate:"2018-10-29T06:56:23Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
 ⚡ root@k8s  /home/ubuntu  kubectl api-resources --namespaced=true
NAME                        SHORTNAMES   APIGROUP                    NAMESPACED   KIND
bindings                                                             true         Binding
configmaps                  cm                                       true         ConfigMap
endpoints                   ep                                       true         Endpoints
events                      ev                                       true         Event
limitranges                 limits                                   true         LimitRange
persistentvolumeclaims      pvc                                      true         PersistentVolumeClaim
pods                        po                                       true         Pod
podtemplates                                                         true         PodTemplate
replicationcontrollers      rc                                       true         ReplicationController
resourcequotas              quota                                    true         ResourceQuota
secrets                                                              true         Secret
serviceaccounts             sa                                       true         ServiceAccount
services                    svc                                      true         Service
controllerrevisions                      apps                        true         ControllerRevision
daemonsets                  ds           apps                        true         DaemonSet
deployments                 deploy       apps                        true         Deployment
replicasets                 rs           apps                        true         ReplicaSet
statefulsets                sts          apps                        true         StatefulSet
localsubjectaccessreviews                authorization.k8s.io        true         LocalSubjectAccessReview
horizontalpodautoscalers    hpa          autoscaling                 true         HorizontalPodAutoscaler
cronjobs                    cj           batch                       true         CronJob
jobs                                     batch                       true         Job
leases                                   coordination.k8s.io         true         Lease
events                      ev           events.k8s.io               true         Event
databases                                example.com                 true         Database
daemonsets                  ds           extensions                  true         DaemonSet
deployments                 deploy       extensions                  true         Deployment
ingresses                   ing          extensions                  true         Ingress
networkpolicies             netpol       extensions                  true         NetworkPolicy
replicasets                 rs           extensions                  true         ReplicaSet
networkpolicies             netpol       networking.k8s.io           true         NetworkPolicy
poddisruptionbudgets        pdb          policy                      true         PodDisruptionBudget
rolebindings                             rbac.authorization.k8s.io   true         RoleBinding
roles                                    rbac.authorization.k8s.io   true         Role
 ⚡ root@k8s  /home/ubuntu 

/close


Fix recently-introduced bug in ci_build.sh re. cmake builds

Commit 4316aeb inadvertently made cmake builds depend on bazel. This PR removes this dependency.

Thanks, @vrv


Cache Issue

It’s been like a year since changing and the skin still shows as my old one.

https://crafthead.net/helm/2ce90d65f2534e3c8e4b3d5fb1e4c927

...I can't notice a difference. Have you cleared your cache?

...I can't notice a difference. Have you cleared your cache?

This is what my skin actually is.

I have the same issue. Is the server caching player skins indefinitely?

i have the same issue
https://crafthead.net/helm/2ce90d65f2534e3c8e4b3d5fb1e4c927

http://cravatar.eu/helmavatar/2ce90d65f2534e3c8e4b3d5fb1e4c927

https://mc-heads.net/avatar/2ce90d65f2534e3c8e4b3d5fb1e4c927

https://minotar.net/helm/2ce90d65f2534e3c8e4b3d5fb1e4c927

https://heads.discordsrv.com/head.png?uuid=2ce90d65f2534e3c8e4b3d5fb1e4c927&overlay

Contrary to popular belief, I haven't forgotten about this project, it's just that work has kept me busy.
Unfortunately I need to spend some time migrating this project to the new-fangled Wrangler 2 so it'll take a while.

I've done a cache bust so that everything starts fresh.

I'll have to continue investigating the issue some more. There's multiple layers of caching at work and it's not clear which one is not expiring as expected. It's probably the local cache layer, I've had issues with it before.

@Pantera07 that just looks like a bug, it's not a caching problem.

Seems like this is an ongoing issue... or is there a timeframe when I should expect the cache to expire?
https://crafthead.net/avatar/1be4963b-c9a0-4b59-adfd-4341ec5bc73b
https://mc-heads.net/avatar/1be4963b-c9a0-4b59-adfd-4341ec5bc73b


chore(main): release 1.4.0

:robot: I have created a release beep boop
This release adds the option to ignore unavailable entities when determining whether a scene is on or not.
1.4.0 (2024-11-15)
🚀 Features

add option to ignore unavailable entities (#136) (dff74e5)

🐛 Bugfixes

correct documentation link (#132) (c096a14)

🔧 Miscellaneous Chores

dev: add recommended extensions for Python development (#135) (18c682d)
dev: update Python image version and install dependencies (#134) (06c72ae)

👷 Continuous Integration

use uv in lint.yaml (#137) (5bc5c6e)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.4.0
:sunflower:


helm repo add problem: is not a valid chart repository or cannot be reached

I'm trying to use this helm chart, but it seem that there is a problem:
# helm repo add cmak-operator https://eshepelyuk.github.io/cmak-operator/
Error: looks like "https://eshepelyuk.github.io/cmak-operator/" is not a valid chart repository or cannot be reached: failed to fetch https://eshepelyuk.github.io/cmak-operator/index.yaml : 404 Not Found
It's quite perplexing that I seem to be the only one experiencing this issue. I've made attempts to resolve it on multiple computers where I have Helm installed, yet the error persists consistently across all of them
Thanks in advance.

Following your doc: https://artifacthub.io/packages/helm/kubegemsapp/cmak I was able to install it without adding repo.

the repository you referred is a scam, you are using it on your own risk.
installation instructions are provided in readme, i have no idea why you hadn't used it.


Update node check

Hi @mattdesl!
This package ignores node, though there are drawille-canvas and canvas (at least), which are able to provide canvas in node.
Could you pls update to detect context of passed canvas?
Thx.

Thanks! Pushed


Design Review: Create Side Panel

Design review guidelines
Standards

[x] All pattern updates/changes/iterations have been discussed with the component developer
[x] Patterns have been approved by either DSAG or another approving entity

Pattern and behavior

[x] The component behaves according to the guidelines set by the pattern maintainer
[x] The component’s UI matches the pattern specifications set by the pattern maintainer
[x] The component’s motion matches the specifications set by the pattern maintainer(s)
[x] The UI produced is responsive, cross-browser, and responds to the currently set Carbon theme.
[x] Colors, themes, sizes and additional props are true and correct, aligning with Carbon set tokens (unless otherwise specified by the pattern)
[x] Paddings/margins/spacings are true and correct, in both desktop and mobile views

Storybook

[x] A functioning component renders in Storybook
[x] The Storybook displays multiple scenarios that show how the component can be used
[x] Changing props in the Storybook updates the component

[ ] The side panel header should behave like the SidePanel component.

[ ] The scrollbar goes out of view under the header and under the footer. Take a look at CreateTearsheet's body scroll for comparison. I will also open an issue for SidePanel, which doesn't have this issue with the header, but it does with the footer.

[ ] Another SidePanel issue - on entry the scrollbar appears last and squeezes the content, making the form fields resize. Will open issue.

[ ] For the last form item, let's keep the margin bottom. It gives it a bit of healthy room there.

[ ] Since it seems Carbon are not planning to fix the number input styling anytime soon (?), can you please replace most of those with normal/nice-looking form fields like text fields, dropdowns, radio buttons, anything.

[ ] I don't recall if we did this on purpose, but there's a little more space between the form group legend in our example than there is in Carbon's

[ ] The dropdowns act weird near the footer on scroll. Some thought needed for this one 🤔 They should also go under the header.

Issue created for side panel https://github.com/carbon-design-system/ibm-cloud-cognitive/issues/1109

Everything will be addressed in https://github.com/carbon-design-system/ibm-cloud-cognitive/pull/1141


[TASK] Hubble Stats Data should be updated and refetched in the background

Currently, the data for both the home page and pool detail page is cached for one hour (according to NextJS doc), resulting in the UI is not updated up-to-date with the back-end when users navigate around. Each page should perform data refetching every 5 seconds.
Current behavior:
Home page -> Detail Page -> go back to Home page but data is not updated on home page
Expected behavior:
Home page -> Detail Page -> go back to homepage, the data is updated up-to-date

@drewstone let me know if this task resolves the problem you mentioned during the demo about updating the data in the background. Also I find 5 seconds is good enough to get the latest data. Let me know if you suggest a different time interval to refetch data from the backend.

Yes, another framing is to see if the graphQL system can hook into a reactive API. Then you can consume data from subscriptions to the API rather than timing queries. Updating every 5,10 seconds is good. We can also consider only updating what's actively in view and not everything (say in the future if there are lots of pools being tracked). These types of thoughts and trade offs should be considered.

Some useful docs for this issue:

@live queries in graph-client
The Graph Client Architecture


Web component tests, storybook for button

Kevin's changes were moved into new PR that includes some additional changes


Support submitting UCAN Invocations as jobs

This commit adds support for submitting UCAN Invocations in JSON form as defined by the draft spec using the Bacalhau client.
Submitted invocations are converted into Bacalhau job specs on the client side and submitted to the requestor node API as usual. Users can do this using the bacalhau create <invocation.json> command.
Note that this means there is no support for sharding, concurrency or minimum bidding for these jobs as these are not supported in the invocation spec. (This is because they are about defining how many jobs are done and how the executor is selected, which is not in scope for the Invocation spec which only focuses on execution itself).
Support has been built into the client rather than the server as an MVP because it's much easier to add support there quickly and without changing any existing APIs. The same technique of parsing an invocation into a job spec could also be applied on the server but will require a new API endpoint or e.g. content-type detection.
Unfortunately this conversion is not as straight-forward as we would like:

UCAN models storage specs as just URIs, so we have to manually convert these into our own StorageSpec objects
because the Go IPLD library does not currently support inline unions, we have to do some of manual re-parsing ourselves.

Some of this pain would go away if we just wholesale adopted the UCAN objects as our internal data model, but this is quite a big change to make. And of course, would require using these objects on our API as well.

re: UCAN objects. Are they stable/definitive enough to be used as our internal data model? Also, I think it'd make sense to adopt them directly at some point; are other CoD platforms keen?

I agree that using UCAN internally would be a good step and I also agree that it's a rather large job so this is an awesome way to support it right away

re: UCAN objects. Are they stable/definitive enough to be used as our internal data model? Also, I think it'd make sense to adopt them directly at some point; are other CoD platforms keen?

Indeeed, if we want to stablise our API ahead of our own 1.0 release, we presumably want to settle on something that isn't going to change much very quickly! The spec is still very much in draft, here: https://github.com/ucan-wg/invocation/pull/1. So I think it is open to change (probably not in significant ways, mostly around how it handles config and metadata AFAIU) and therefore maybe not something we should internally just yet.
Other CoD platforms like DAG House seem keen, and there are a bunch of people in the IPVM group who are also keen.

OK, I'm going to merge this PR (as I've just demo'd it to the IPVM WG, and it works!) I'm still keen for feedback on the how and when, and will be creating some tickets to cover that future work.


Package update

What
What does this PR add or remove?
Why
Why are these changes needed?
How
How do these changes achieve the goal?
Test
How has this been tested? How can a reviewer test it?
Checklist

[ ] I have self-reviewed this PR
[ ] I have added tests that prove the feature works or the fix is effective

These changes are now addressed as part of  https://github.com/rdkcentral/Ripple/pull/511


Add checks, nodejs, fourmolu-0.14

This adds nodejs versions 16.20.{0, 1, 2}.
Also bumped the default fourmolu from 0.13.0 to 0.13.1, and added 0.14.0 (though it is not yet set as the default).
I've also just learned about how to write flake tests (aka "checks"). To run the checks from the root of the repo:
$ nix flake check ./main

Probably this should run in CI, but I haven't looked into it yet.
Each of the packages provided by this flake now has a check that runs the provided executable with the --version option and asserts that the version number is what we expect. This accomplishes two things:

It's a very basic check that the package actually builds and produces a working executable
For packages "re-exported" from nixpkgs, it's useful to assert that our flake is actually providing the version that it claims to be providing. For example, the definition nodejs-16-20-2 = nixpkgs.stable.nodejs_16; is fragile in that nixpkgs might bump the version, and then if we upgrade stable it would no longer be 16.20.2. Now that it is tested, when we upgrade the flake inputs we can run the checks, and if needed we can hold back the version of nixpkgs that we get that nodejs package from.

An example of holding back nixpkgs for a specific package can be seen in this PR. I did it for fourmolu, not because getting fourmolu from the latest version of the stable channel wouldn't work, but simply because I didn't want to trigger a long recompile. It is good to keep things following the head of a release branch, but some of the builds are too slow to be upgrading things higgledy-piggledy until we have some binary caching infrastructure in place.
I've adopted here a new convention for naming the nixpkgs flake inputs that don't simply follow a branch head. Previously I was naming them based on the reason I wanted a specific old revision (e.g. ghc927). Here I'm naming them as a combination of the branch name and commit date: nixpkgs-stable-2023-07-25, nixpkgs-master-2023-05-06, nixpkgs-master-2023-07-18. For one thing, I want to be able to easily see how old something old is. But the main motivation is that I want to be able to minimize the number of nixpkgs flake inputs. The more versions of nixpkgs we have in use simultaneously, the more chances there are that we end up redundantly building slightly different versions of things. And so when searching back in nixpkgs history for a version that has some particular thing I'm looking for, it's good to be able to connect the timeline to the set of nixpkgs revisions we already have pinned, to try reusing an existing input if possible rather than adding a new one.
Running the nix flake check command revealed something I didn't know, which is that the nix tooling expects a flake's packages to be a flat, not nested, attribute set. So unfortunately I already need to make a change to what I just did earlier today, which is e.g. fourmolu.v0-13 is being renamed to fourmolu-0-13 (no dot).

Okay, that was actually really easy to set up. It'll be building for a while, though. I guess we'll find out tomorrow whether it passed.

CI caught a mistake already :smile:


VS code zoom is not working

The window size of my VS code app is too small. Please help! The zoom level is not working at all.

I uninstalled the app and installed it again, then I pressed ctrl+ Numbpa0and it worked.

I'm happy you managed to unblock yourself. If you manage to find reproducible steps, please let us know.


error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65

error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening MeiTuan.xcodeproj. Run CLI with --verbose flag for more details.
React Native version:
0.60
Xcode: 10.2.1

@hepf888 open your project(ios/app.xcworkspace) in Xcode -> Product -> Build -> Check error messages

Hello there 👋 this issue doesn't have a repro (which means, a react-native init-ed project with the minimal changes that leads to creating the same issue you are reporting). Unfortunately, I have no way of helping you in a meaningful way – there is no easy way for me to recreate the situation and check that the issue reported is still there when changing the code.
Because of this, we are going to close this issue - but if a repro is shared, we are happy to reopen it 🤗

I just got this error after upgrading to 0.60.4 (from 0.59.2).
To fix it I've had to rename the xcworkspace folder from gazella.xcworkspace to Gazella.xcworkspace.
I could successfully run the project from within XCode, but got the error when doing react-native run-ios on the terminal. Now everything works fine.

gazella.xcworkspace

please location this file

@septe01 it will have a different name in your project, but it will end with .xcworkspace


[Task] Updating Merlin Merlin examples with new Merlin logo

Description
Updating all example notebooks to have a customized NVIDIA logo

It was closed via https://github.com/NVIDIA-Merlin/Merlin/pull/569


feat: Adds view.resolutions and layer config options

This patch will add the support following capabilities:

ol.View: supports the resolutions parameter

All of the standard configuration parameters of the ol.layer.Layer interface are now supported:

opacity
visible
extent
zIndex
minResolution
maxResolution

Hi there,
any responds on this PR?

@maveric1977 Awesome work, thx for contributing.


Link to actual Jenkins plugin

Applicable Issues
Fixes #6
Description of the Change
Use the correct URL in the links to the Eiffel Jenkins plugin. The repository previously linked to (in the eiffel-community GitHub organization) is just an empty placeholder. The active repository resides in the jenkinsci organization.
Alternate Designs
None.
Benefits
Link leads to a useful location.
Possible Drawbacks
None.
Sign-off

Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I    have the right to submit it under the open source license    indicated in the file; or
(b) The contribution is based upon previous work that, to the best    of my knowledge, is covered under an appropriate open source    license and I have the right under that license to submit that    work with modifications, whether created in whole or in part    by me, under the same open source license (unless I am    permitted to submit under a different license), as indicated    in the file; or
(c) The contribution was provided directly to me by some other    person who certified (a), (b) or (c) and I have not modified    it.
(d) I understand and agree that this project and the contribution    are public and that a record of the contribution (including all    personal information I submit with it, including my sign-off) is    maintained indefinitely and may be redistributed consistent with    this project or the open source license(s) involved.
Signed-off-by: Magnus Bäck<EMAIL_ADDRESS>

With the caveat that I'm unfamiliar with the plugin, I'm happy to approve, with two assumptions:

The Broadcaster plugins fulfills both roles
The Eiffel Jenkins Plugin is actually dead (if not, we should link to both)

With the caveat that I'm unfamiliar with the plugin, I'm happy to approve, with two assumptions:
The Broadcaster plugins fulfills both roles

Well, I guess it does. It certainly sends ActT and ActC but it doesn't perform any orchestration on its own, i.e. it just translates what Jenkins does.

The Eiffel Jenkins Plugin is actually dead (if not, we should link to both)

The repo has been essentially empty since its inception three years ago so I don't think there's any reason to link to it. If things get added to it we should of course reintroduce the link.


cname and txt records update

Description
there are now toggles for creating cname / txt records for the custom domain:

create_cname_records
create_txt_records

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] I did run all  pre-commit checks

Introduced some breaking changes, and there seems to be a provider error with cname records and custom domains that I would like to discuss


Logout/End Session not workign correctly with AWS Cognito Hosted UI

Issue and Steps to Reproduce
When using AWS Cognito as an OIDC provider, the way Cognito handles ending sessions and logging out doesn't quite work for this package. Since Cognito doesn't provide a dedicated /end-session endpoint, it is necessary to use the /logout endpoint instead. Documentation for this endpoint can be found here: logout
The full list of provided endpoints can be found here: Hosted UI and federation
Versions
7.7.3
Expected
When calling logout(), the session is ended and the user is sent to the desired logout callback location
Actual
The tokens are removed from storage, but not revoked by Cognito and the user is returned to the same page from which they logged out. If that page is protected, the user is signed right back in
Additional Details
I believe this can be worked around by adding another option to the authority_configuration part of the config; a logout_endpoint that is handled here during the logout function call. In order for this to not be a breaking change, it can be handled as an else condition in the if/else block linked earlier.
I'll see if I can get this working locally and make a PR :)

Upon further inspection of the code, you can get around this by passing in the extras parameter to the logout() function and if end_session_endpoint is set to cognito's /logout endpoint.
logout(null, {
   client_id: <client ID>
   logout_uri: `${window.location.origin}/<logout path>`,
 });

works as expected

Thank you @dhaub-exelixis for the feedback!


[Yidong]update twitter timeline api related to https://github.com/rai…

Twitter have upgraded their widgets api, replace by https://publish.twitter.com/, customer are not available to create new widget now, and we can add timeline with only username which is simpler.
According to this issue: https://github.com/rainlab/twitter-plugin/issues/13
If you accept this PR, you'd better also remove twitter_widget_id from _config.yml.
BTW, I love this theme you create, it's looks fancy.
Thanks,

I merged in this change in 8199bfcf5fe30386282eb145bda39fe03763fa60
Thank you!


How to configure vs code debugger to use dotnet watch?

I want to run my application in debug mode, whilst using dotnet watch.
Is it posible? If so, is it as a matter of configuring my launch settings?
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": ".NET Core Launch (web)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            "program": "${workspaceRoot}/bin/Debug/netcoreapp1.0/test-api.dll",
            "args": [],
            "cwd": "${workspaceRoot}",
            "stopAtEntry": false,
            "launchBrowser": {
                "enabled": true,
                "args": "${auto-detect-url}",
                "windows": {
                    "command": "cmd.exe",
                    "args": "/C start ${auto-detect-url}"
                },
                "osx": {
                    "command": "open"
                },
                "linux": {
                    "command": "xdg-open"
                }
            },
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceRoot}/Views"
            }
        },
        {
            "name": ".NET Core Attach",
            "type": "coreclr",
            "request": "attach",
            "processId": "${command.pickProcess}"
        }
    ]
}

Not sure if this is possible, unfortunately. The problem is that dotnet-watch is one process and it launches a dotnet process. You need the debugger to attach to the dotnet proc but you can't get that process ID easily.
Maybe @troydai has an idea?

I don't think this is feasible. If you configure the launch.json to start the dotnet watch, the debugger is attached to the "watch" process instead of the process dotnet watch starts. Unless my understanding of how dotnet watch operates wrong.
It is tricky here. The same issue happens to dotnet test as well. In that scenario, dotnet test process itself doesn't run test. It starts another process to execute tests. That makes the launch.json unusable. We have to build specified feature to enable test debugging scenario.

Yeah, we'd probably have to drop a pid file or something similar to let VS code know about the actual process id. VS Code would have to understand that file though (and watch it?)

In the case of dotnet test it works because of the protocol it defines. The protocol allows omnisharp to communicate with dotnet cli to generate the actual start command. VS code API allows extensions to build launch configuration programmatically. So maybe this can be a feature for OmniSharp.

So omnisharp would need a generic protocol that any tool can implement?

no, dotnet watch need a protocol so that omnisharp can be aware of either 1) what's that start command  therefore ask debugger to start the process; or 2) what's the eventual process ID for each newly started process.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Updated validations.py pthon script.

Updated validations.py pthong script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


CI of latex compilation

It will be ideal to automatize the workflow of compilation of the tex files (currently included in Makefile) after every commit/PR. For PR, we should use this as a test before integrating new text to the code.
We should:

Create a new workflow that compiles the tex and makes sures the new pdf is build with no problem.
Test that this happens after every commit/PR

A new workflow latex has been created that makes the compilation of the latex code and generates an artifact that is accessible using the UI of GitHub under the Action tabs. This allows us to download the pdf after the execution is completed.
It still remains to see how we can do make an git add, git commit of this artifact file into the main repository, instead of being accessible just though this means.


Addition of events that travel through CRV only

Hi @oksuzian,
You have proposed changes to files in these packages:

JobConfig

which require these tests: build.
@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.
:hourglass: The following tests have been triggered for 358ace57407895388cb82479dba5664a1009f9b9: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 358ace57407895388cb82479dba5664a1009f9b9.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 358ace57407895388cb82479dba5664a1009f9b9 at c3c163b75350c8ea54059c842190160676c7cae7

build (prof)
:white_check_mark:
Log file. Build time: 11 min 52 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 358ace57407895388cb82479dba5664a1009f9b9 after being merged into the base branch at c3c163b75350c8ea54059c842190160676c7cae7.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

@FNALbuild run build test

:hourglass: The following tests have been triggered for 60c107c9d8c84bd8f3afa9a1a529f056fe17783e: build  (Build queue is empty)

:sunny: The build tests passed at 60c107c9d8c84bd8f3afa9a1a529f056fe17783e.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 60c107c9d8c84bd8f3afa9a1a529f056fe17783e at c3c163b75350c8ea54059c842190160676c7cae7

build (prof)
:white_check_mark:
Log file. Build time: 11 min 33 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 60c107c9d8c84bd8f3afa9a1a529f056fe17783e after being merged into the base branch at c3c163b75350c8ea54059c842190160676c7cae7.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


Added solution 9

This PR will add solution 9.

Binder: https://mybinder.org/v2/gh/andersle/chemometrics/add_solution_9?filepath=solutions%2F09_Solution.ipynb


Fixed tab completion parser issue and the issue when doing 'dockerComposeRestart -useStaticPorts'"

The fix includes two things:

The previous parser for tab completion put extra parenthesis around the argument, which would make the argument parsing in some places fail.

When doing 'dockerComposeRestart' and not suppling instanceId as a parameter, if we supply other valid parameter such as '-useStaticPorts', it would not restart the running instance.

Thanks @edward720!


Support sliding window computations

Consider the following code:
import dask.array as da
import numpy as np

d = da.arange(8, chunks=4)

g = d.map_overlap(np.mean, depth=0, boundary=0, trim=False, keepdims=True)

After computing g, this will return the mean of the two chunks [0:4] and [4:8]. Currently, there seems to be no way to specify a step size different (smaller) than the chunk size for each dimension. One could want a step size of 2, result in the mean for ranges [0:4], [2:6], [4:8].
Being able to specify a step size is very useful for filtering images, for example, as the user may be fine with computing every the filter for only every second or third pixel to reduce compute time. The user may want an arbitrary step size, which I think will normally be anything from 1..len(chunk[dim]).
I would be interesting in knowing what options do we currently have (if any), otherwise, what people think may be a good direction for the implementation of a step size.
cc @mrocklin @jakirkham

I've renamed this issue to "Support sliding window comptutations" (I hope that that's ok).  The map_overlap function is more specifically for mapping a function over chunks of data, my guess is that it would be used internally by some sort of sliding window function, but may not be the user level API directly.
Today, NumPy lacks a sliding window API.  This is discussed in more depth here: https://github.com/numpy/numpy/issues/7753
If such an API existed, then we might consider copying it.  Given that it doesn't exist, we might consider creating our own, and collaborating with upstream NumPy to make sure that they're ok with it in case they ever go in that direction.
If I were to do this today I would probably make a block-wise function that did a sliding window computation, probably using either NumPy stride tricks (a hack described in that issue and known to expert numpy users) or just for loops with Numba, and then I would apply that function with map_overlap

Thanks for your input @mrocklin. I'm definitely gonna take a look at the NumPy discussion in detail.
I have a feeling you're right, we're probably gonna need the block-wise function, or Numba as a last resort. I'm particularly concerned about the memory footprint, certainly making a copy of every window+boundaries to use it as a chunk will be too expensive.

I think that we can use either Numba or stride tricks to do an efficient sliding window computation in low memory.
I think that we can use map_overlap to handle the boundaries between large blocks.
I think that with both of these we can achieve what you want in small space.

I'll continue to investigate this, thanks for the suggestions @mrocklin.

There's a sliding window PR https://github.com/numpy/numpy/pull/10771, it seems to be what we want. The progress has stalled for quite some time, the author mentioned he would pick it up again, but that hasn't happened yet, presumable he's got no time for that. I can probably suggest there that I continue with it. Do you think that looks good @mrocklin ?
I'd nevertheless have to find a more immediate solution, since we'll need the same for CuPy, and I don't think we can get that PR in NumPy, do the work for CuPy as well and have it merged in less than 1-2 months.

I think it would be good for that PR to be finished.  In principle having anyone finish it would be good.
Putting on my NVIDIA hat I don't currently know where this task fits into our current priorities.  It's not clearly tied to any particular task that I know of, so I would prioritize is somewhat low.  That being said, if you're excited about doing it then please don't let me get in the way :)

I am quite interested in having this functionality in Dask. Now that Numpy has implemented a sliding_window_view (https://github.com/numpy/numpy/pull/17394) which is now available in Numpy 1.20, I was wondering what the status of this issue is.

@theXYZT see https://github.com/dask/dask/pull/7234


Error: Class "Spatie\ErrorSolutions\SolutionProviderRepository" not found in /var/www/mysite/vendor/spatie/ignition/src/Ignition.php:68

I just upgraded to Laravel 11, and this is not allowing my Jobs to dispatch properly.  I can properly dispatch them on my local machine, though, and build with vite with no errors.
What can I do to get this error to go away?  I tried all the solutions others used in another post for a different version of Laravel, and none of them worked.
My composer:
{     "name": "laravel/laravel",     "type": "project",     "description": "The Laravel Framework.",     "keywords": [         "framework",         "laravel"     ],     "license": "MIT",     "require": {         "php": "^8.2",         "barryvdh/laravel-dompdf": "^3.0",         "guzzlehttp/guzzle": "^7.2",         "jeroendesloovere/vcard": "^1.7",         "laravel/fortify": "^1.11",         "laravel/framework": "^11.9.0",         "laravel/tinker": "^2.7",         "nyholm/psr7": "^1.8",         "spatie/error-solutions": "^1.1",         "spatie/ignition": "^1.15",         "spatie/laravel-backup": "^8.1",         "spatie/laravel-csp": "^2.8",         "spatie/laravel-webhook-client": "^3.1",         "square/square": "^38.0",         "symfony/http-client": "^6.3",         "tightenco/ziggy": "^1.0",         "twilio/sdk": "^8.2",         "unisharp/laravel-filemanager": "^2.4",         "yajra/laravel-datatables": "^11.0"     },     "require-dev": {         "barryvdh/laravel-debugbar": "^3.7",         "fakerphp/faker": "^1.9.1",         "mockery/mockery": "^1.6",         "nunomaduro/collision": "^8.0",         "phpunit/phpunit": "^11.0.1",         "spatie/laravel-ignition": "^2.8"     },     "autoload": {         "psr-4": {             "App\\": "app/",             "Database\\Factories\\": "database/factories/",             "Database\\Seeders\\": "database/seeders/"         }     },     "autoload-dev": {         "psr-4": {             "Tests\\": "tests/"         }     },     "scripts": {         "post-autoload-dump": [             "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",             "@php artisan package:discover --ansi"         ],         "post-update-cmd": [             "@php artisan vendor:publish --tag=laravel-assets --ansi --force"         ],         "post-root-package-install": [             "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""         ],         "post-create-project-cmd": [             "@php artisan key:generate --ansi"         ]     },     "extra": {         "laravel": {             "dont-discover": [             ]         }     },     "config": {         "optimize-autoloader": true,         "preferred-install": "dist",         "sort-packages": true,         "allow-plugins": {             "php-http/discovery": true         }     },     "minimum-stability": "dev",     "prefer-stable": true }
I'm using Ubuntu and Nginx, but I don't think that matters in this instance since I'm using nginx on my local machine as well.

I have same issue with you. Any update ?

This one works for me https://github.com/spatie/laravel-ignition/issues/204#issuecomment-2348215874

I am experiencing the same issue, job works fine on my local, but fails with this error message on the server, Tried every possible solution posed on #204

I'm also facing the error: Class "Spatie\ErrorSolutions\SolutionProviderRepository" not found in /var/www/mysite/vendor/spatie/ignition/src/Ignition.php:68.
I solved it by uploading the entire vendor directory to the server, which fixed the issue by ensuring all dependencies were in place.


Tests and fixes for unexpected journeys

This PR adds specs and fixes for journeys that are outside the expected path, i.e. where the session expires, or where the back button is used.
This seems to rule out session expiry as a cause of 500 errors, but does identify a large class of problems that can happen when a visitor jumps straight to a later page without the expected information in their session.
After the first step, the session must contain a visit, which has a prisoner, who has a prison name. Without this, the prison data cannot be retrieved and an exception results.
Now, if the session doesn't contain this information, we'll redirect the visitor back to the first step and get them to start again. This won't solve every possible 500 error, but it should make a difference.

Tested and working on preprod.

This is great stuff, nice work @threedaymonk.


Consistency in the confirmation modals

Ref - https://github.com/bigbinary/neeto-engineering-ui-ux/issues/147
@thomas-mathai _a

Closing this issue since it's already fixed.
Ref: https://github.com/bigbinary/neeto-editor/issues/811


EXTCODEHASH gas costs

The cost of EXTCODEHASH is currently set to 100 and indicates a dynamic cost. However, AFAICT the gas cost should be a constant amount of 700 as of EIP-1884. Where does this information come from? Perhaps it should be changed.
Geth params:
https://github.com/ethereum/go-ethereum/blob/8798cd3a09d693ce038fa4a2a93348d3de010d72/params/protocol_params.go#L105
Geth gas function:
https://github.com/ethereum/go-ethereum/blob/8798cd3a09d693ce038fa4a2a93348d3de010d72/core/vm/jump_table.go#L143-L145

It comes from reading the code of the evm js, but can very well have been done incorectly.
Thanks for notifying us, will take a look to fix it.

In fork Istanbul, the gas of EXTCODEHASH is 700. But after Berlin, the extcodehash calculate has been changed.
The eip:  https://eips.ethereum.org/EIPS/eip-2929
The code of go-ethereum's gas calculator: https://github.com/ethereum/go-ethereum/blob/d740d6e741562e98b3d75a98e7decdfee3bdd904/core/vm/operations_acl.go#L148
We use the ethereumjs to calculate the gas price. the method's code link is: https://github.com/ethereumjs/ethereumjs-monorepo/blob/a60b878c377a55cd17a6e633a59bc4400713eddb/packages/evm/src/opcodes/gas.ts#L156
So, you can switch the fork to berlin. You can see the static gas of extcodehash is 700.

doing some housekeeping; @0xalpharush, @jonahcui (thank you!!) covered it and I'll close the ticker


Refactor Shared Logic Between TonicClient and WebTonicClient

What should be done?
After this PR is merged, the miden-client will now have a WASM-compatible rpc client. As noted in this comment, the WebTonicClient and the TonicClient currently share a lot of logic after the client is created in each function. This code duplication opens the door to potential bugs in the future as it becomes easy to update the code in one place but not the other. As a result, we should refactor the code slightly so that each RPC client method calls share logic once the client is created and the request is sent.
How should it be done?
We should pull out shared logic for each of the RPC client functions into the src/rpc folder and refactor the logic for each function in both src/rpc/tonic_client/mod.rs and src/rpc/web_tonic_client/mod.rs to use this shared logic.
When is this task done?
This task is done when the refactor described above is complete and both RPC clients build successfully.
Additional context
This issue is blocked on https://github.com/0xPolygonMiden/miden-client/pull/409

I think we should be able to do something like what we did for the RemoteTransactionProver struct in order to deduplicate code for each environment. We generate the code twice (one with transport and one without, for wasm), and then re-export them conditionally on a single module, which the struct code then uses.


Fix benchmark typos

Just spotted and fixed a few typos in the benchmark docs.

Sorry for the late reply @ferki. Not sure how I missed this.  The benchmark API has been removed as it was never released in ES.  thanks anyway

@clintongormley: no problem, I also forgot to close it when the API went away.


Add basic parsers for CLI args

Fixes: https://github.com/runtimeverification/pyk/issues/260
This adds basic CLI parsers from KEVM to here.

The helpers cli_utils is moved to cli.utils instead, to create the submodule.
The helpers for parsing individual arguments from KEVM are upstreamed to cli.utils.
Promote several things from cli.utils to utils, including: run_process, BugReport, and check_*.
A new module cli.args is added with KCLIArgs, which contains the basic common K cli tool arguments from KEVM.
The pyk cli is adapted to use the new upstreamed argument parsers. Unfortunately, this does not mean very much of the CLI is captured here, because the pyk cli has not been fleshed out to handle all the ktools yet.

Related (it will make us have to implement more of the CLI): https://github.com/runtimeverification/pyk/issues/483


Design docs

This PR is intended to add design documentation for PluginPlay.
At present this includes:

[x] PluginPlay itself
[x] ModuleManager
[x] Module
[x] PropertyType
[x] Fields
[x] Cache
[x] Database

I think this is r2g at this point. I still want to go through the user documentation/tutorials before calling the documentation set, but I'm going to do that in another PR.


Inline-template Issues from http://vuejs.org/guide/components.html#Inline-Templates

Inline-template components must have exactly one child element.

This issue is in vuejs2.0

Thanks for your reporting @matisha001 .  This should be an issue of vuejs/vuejs.org
We will update the document as soon as possible.


Update PTLM constants; change tests to snapshots

Closes #32

Changes in calculated PLC50 values due to changes in constants can be seen here.


better explain in docs that langchain is independent from LLMs providers

suggested label: documentation imporvement

One of the langchain strong points is its independence "by design" from any LLM provider.
IMMO this is not fully clear in the current documentation. By example, the getting started page start to mention Openai:
from langchain.llms import OpenAI

The fact langchain can currently operate not just with openai models is described in the integrations page. That's fine, but I'd point out at first (maybe in the initial llm page), this foundamental feature.

hi I updated the documentation to reflect this change


activate-normal-mode inserts latin letters on cyrillic keyboard

There was a problem with remapping ESC https://github.com/atom/vim-mode/issues/334, it was fixed, so now I can remap that using only keymap.cson, like this:
# Vim normal mode
'atom-text-editor.vim-mode.insert-mode':
  'j j': 'vim-mode:activate-normal-mode'
  'k k': 'vim-mode:activate-normal-mode' # bcoz I always confuse this
  'k j': 'vim-mode:activate-normal-mode' # bcoz I always confuse this

Now, there is a new problem:
When I use cyrillic keyboad and type о or л (match to j and k on latin keyboar), I get j and k instead of о or л. For example, if I try to type орел, I'll get jреk instead.
Is there way to fix this?

My init.coffee is clean.

@maxbrunsfeld do you know if this is specific to vim-mode, or if it's likely to be a general keymap issue?

I think this is a general keymap issue. It was probably introduced by https://github.com/atom/atom-keymap/pull/94, which fixed the handling of multi-key printable character bindings like j j.
Basically, when a multi-key binding like that fails to match after one or more characters, we attempt to figure out which characters would have been inserted, and fire text insertion events for those characters. Our logic for determining the characters must not work for these cyrillic characters.
@denysdovhan Could you run this code in the Atom javascript console, and report its output after typing о and л? You'll need to click on the KeyboardEvent object to expand it.
window.addEventListener('keydown', function(event) {
  console.log(event, atom.keymaps.keystrokeForKeyboardEvent(event));
}, true);

After typing о:

After typing л:

/cc @nathansobo, so these events keyCode and keyIdentifier correspond to j and k, but @denysdovhan actually typed о and л on a cyrillic keyboard. Is this a symptom of the same underlying problem described in https://github.com/atom/atom-keymap/issues/37?

So, will it be fixed?

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


Creation of service instance with name more than 50 characters fails

Issue
Service instance creation fails when I tried to create the instance with name more than 50 characters.
Context
When I tried to create a service instance of name more than 50 characters, it failed with error: You have requested an invalid service instance name. Names are limited to 50 characters.
What is the reason behind this limitation? Is it possible to bypass this length restriction somehow as it breaks our live scenario? Also, I observed that the service key name has no length restriction, then why only service name?

There is no work around for this because it is hard coded: https://github.com/cloudfoundry/cloud_controller_ng/blob/8887877b9dfc9237a34ffcbf54ac3cf58d680d48/app/models/services/service_instance.rb#L118
The reason behind it is unknown since this commit was made long ago, 2013. The database seems to hold the row to 255 chars. If there are strong arguments against this, we can bump up the length.

As @weymanf says the limit was added in 2013:

story: (which may not be public): https://www.pivotaltracker.com/n/projects/254145/stories/50667131

makes it clear that there should be a limit of 50 characters for user-provided service instances

commits:

https://github.com/cloudfoundry/cloud_controller_ng/commit/037a6d031c9d4227e1031a81c718ac4debc6ae55
https://github.com/cloudfoundry/cloud_controller_ng/commit/071297d5ada09f5e619ad3f99c5378c86f397766

Also it seems that the database limit of 255 is accidental due to a mistaken migration and an a revert that doesn't match:

https://github.com/cloudfoundry/cloud_controller_ng/commit/94d17a3cde61ed5033d302f9b80aff398f80fffe
https://github.com/cloudfoundry/cloud_controller_ng/commit/6c64161ba91df6e809d1e509f503e4b9aa85798b

It's clear that the limit of 50 characters is for a reason, but why?
I did find this bug (https://www.pivotaltracker.com/story/show/59171806) which mentioned an issue with AppDirect when a service name was longer than 50 characters. Perhaps the reason for a 50 character limit was because of a restriction in a particular service broker? My caution with increasing the limit is that we might just end up repeating history and discover the issue that caused folks to impose the limit in the past. Then again we might find that things have changed and it's all ok now.

I agree with keeping this limit unless someone has a valid reason for going pass 50 characters.

Since you mentioned that this restriction was added in 2013 and it's possible that the issue isn't relevant anymore, can you please relook into this length restriction?
Our application creates service instances for dynamic string and this string can sometime be very huge (we don't have control over that). Hence, service creation of such instances fail. It is breaking in our production environment and it would really help if this limit could be increased.

Business case: SAP Business Technical Platform is the platform for the Intelligent Enterprise where customers can achieve agility, business value, and continual innovation through integration, data to value, and extensibility of all SAP and third-party applications and data assets.
When customer signs a contract with SAP a new Global Account is created and as a self-service activity customers can create sub-account where they can get different product offering like SAP Cloud Platform Integration etc. While creating the sub-account they are required to provide an id which is the subdomain. Now if the customer wants to use some of the services then it is fine if the subdomain id length is up to 63 chars. However for the SaaS Integration service length more than 29 chars is a problem since we append certain pre-fixes for different bindings with the platform. Due to this the actual length which they can create is only 29 chars. Now we are facing escalations from some critical customers who already have subdomain ids longer than 29 chars which earlier they were using for other SaaS offering on the platform and they are not willing to change the sub-account as all SaaS products have to be then moved to new sub-account.
Technical problem: We use the subdomain name as the unique identifier for creation of service instances. The length of the sub domain can go up to 63 characters. With prefix of max 21 characters, our requirement is to be able to create service instances of max 63+21 =84 characters

Business case: SAP Business Technical Platform is the platform for the Intelligent Enterprise where customers can achieve agility, business value, and continual innovation through integration, data to value, and extensibility of all SAP and third-party applications and data assets.
When customer signs a contract with SAP, a new Global Account is created and as a self-service activity customers can create sub-account where they can get different SaaS offerings like SAP Cloud Integration etc. While creating the sub-account they are required to provide an id which is the subdomain. Now, different SaaS service offerings are creating a platform resource (which in turn uses the cloud controller) with different length using the subdomain id.
Now we are facing escalations from some critical customers who already have subdomain id defined and are using some SaaS offerings. If they have to add certain other SaaS services then they are getting length restrictions from the platform. As a mitigation step we asked customers to change to new sub-account with a shorter length so that all the SaaS offerings are within the required length but they are not agreeing to move all SaaS offerings to new sub-account.
In order to address this we would like to have a uniform length and would like the Cloud controller team to extend this in general to 120 chars
Technical problem: Our SaaS offering uses the subdomain name as the unique identifier for creation of platform resources(like- service instances). The length of the sub domain can go up to quite a huge number (>50). So, our requirement is to be able create service instances with atleast max length of 120 characters.


motoman_sia20d.launch error

When launching the motoman_sia20d, I get this error.
RLException: error loading <rosparam> tag:  	file does not exist [/home/alex/Code/catkin_ws/src/jog_control/jog_controller/config/motoman_sia20d_jog.yaml] XML is <rosparam command="load" file="$(find jog_controller)/config/motoman_sia20d_jog.yaml"/> The traceback for the exception was written to the log file
The launch file is looking for the config file in the wrong package. It should look in the jog_launch package. I fixed it locally and it worked fine.
This is an awesome package btw..

Could you make a PR of your fix? Thanks!

#35 fixed this. Thank you!


Update the version that check you can use _get_default_root to Python3.9.2rc1

Because I searched the tags in the cpython repo and I found the _get_default_root
was created in Python3.9.2rc1. So I changed the version number to Python 3.9.2 rc1
(3, 9, 2, 'rc', 1)

fix #98

lol, it was added in python 3.9.2

Interestingly the tests on Github Actions don't fail with Python 3.8

I fixed this in 79c068e using an EAFP approach, because I don't want to worry about exact releases, but thank you for your discovery and work!

Thanks for you check out.
Maybe I have figure out why GitHub Actions why don’t fail.
If it downloads from gitHub/python/cpython/blob/3.8
There is really _get_default_root function in the tkinter.
But there is no _get_default_root function in the release, so people who download version before python 3.9.2 will fail.
That’s ok if you use try and except, but I suggest to use a exact version.

I fixed this in 79c068e using an EAFP approach, because I don't want to worry about exact releases, but thank you for your discovery and work!

Thanks for you review!
Maybe I had figure out why GitHub Actions why don’t fail.
If it downloads from gitHub/python/cpython/blob/3.8
There is really _get_default_root function in the tkinter.
But there is no _get_default_root function in the release, so people who download version before python 3.9.2 will fail.
That’s ok if you use try and except, but I suggest to use a exact version instead of try and except. (If you want)