[BUG] Issue with extracting release archives in seedfarmer 5.0.0

Describe the bug
In the module manifest we are trying to use http archive as a dependency.
name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

My archive(which is stored in artifactory) contains folder structure as below
infra/modules/
├── shared_module
│   ├── app.py
│   ├── deployspec.yaml
│   ├── requirements.in
│   ├── requirements.txt
│   ├── src/
So, when executing the seedfarmer apply, I'm getting below error

raise seedfarmer.errors.InvalidPathError(f"No deployspec.yaml file found in module directory: {p}")
seedfarmer.errors.seedfarmer_errors.InvalidPathError: No deployspec.yaml file found in module directory: /home/repo/seedfarmer.archive/_artifactory_shared_module-1.0.0/modules/shared_module/deployspec.yaml

Below is the folder structure after seedfarmer is extracting the archive.
Could see that all files are not extracted to modules/shared_module instead got extracted in the archive root.
seedfarmer.archive
└── _artifactory_shared_module-1.0.0
├── app.py
├── deployspec.yaml
├── pyproject.toml
├── README.md
├──modules
│       └── shared_module
├── requirements.in
├── requirements.txt
To Reproduce
Steps to reproduce the behavior:
seedfarmer - 5.0.0
This can be reproduced when the modules folder contain only shared_module folder.
I'm not seeing the issue when there are multiple sub folders under the modules directory.

Update your manifest with archive path'
The archive zip should contain modules/<only_common_folder> and make sure it doesn't contain other folder inside the modules dir
execute seedfarmer apply

Expected behavior
Extracting the archive should preserve the folder structure

@jayanthmandavilli  Hi - thanks for your issue submission.
I think you are missing the archive designation in your path?  For example: I just tested with the following:
path: archive::https://github.com/awslabs/idf-modules/archive/refs/tags/v1.13.0.zip?module=modules/dummy/blank
You have provided the following:
name: networking
path: https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

but I think you want the following:
name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

Please confirm?

@jayanthmandavilli Hi - thanks for your issue submission.
I think you are missing the archive designation in your path? For example: I just tested with the following: path: archive::https://github.com/awslabs/idf-modules/archive/refs/tags/v1.13.0.zip?module=modules/dummy/blank
You have provided the following:
name: networking
path: https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

but I think you want the following:
name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

Please confirm?

I'm sorry for the typo in my description and now I've corrected it, yes I've archive designation in my code already.

Ok..thanks for this.   I am not able to replicate the issue with the archives I have.  Can you compare your archive / zip to the one located at https://github.com/awslabs/idf-modules/archive/refs/tags/v1.13.0.zip
Though I don't disagree that this is a problem, I just cannot reproduce it in order to triage

the archive which you have shared contains more than one sub folder inside the modules,
modules/
|---- testing
|---- storage
|---- network.
In my case, modules folder contains only one sub folder
modules/
|---- network

Just to confirm, your archive looks like this:
infra/
|---- modules/
|----|----- network
?

yes

I will have to take a look after the US holiday

the issue is possibly caused by line 79 and 100 in https://github.com/awslabs/seed-farmer/blob/main/seedfarmer/mgmt/archive_support.py  and removing the module and using root level archive is possible cause to line 116

@jayanthmandavilli
I have pushed a patch release (5.0.1) after testing with an archive that matches your description and with multiple other variations and have had successful results (where the archive is extracted as-is and the relative path of the module is unchanged).  Please try that version?

@jayanthmandavilli
Version 5.0.1 has been yanked.  This broke the backward compatibility with the other archives.
The recommendation is to change your manifest path from:
> name: networking
> path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=infra/modules/shared_module

to
name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=modules/shared_module

I could not replicate the issue in which the archive did not extract to the proper location

Reopening this issue for communication

@dgraeber , thanks for the communication

@dgraeber
How about the idea of making the module parameter optional?
In the case of nested folders, the old implementation would unpack the zip and moves all files of the module to the root directory.
This means the deployspec.yaml is at the root of the unpacked module and we don't need to specify a path anymore

@smarkus577 I am not sure I agree with that recommendation.
BACKGROUND: the archives are designed to be structured like a SeedFarmer project, where you have a root dir (the project) and the supporting dirs nested and accessed via relative paths (modules, manifests, etc).  Using the dir names modules or manifests or datafiles is just a semantic, and not required (you can name them whatever you want) as long as you reference that name.
I disagree with your suggestion for two reasons:

it violates the design (more importantly it would remove a standard)
It masks the real problem

Item 2 is what I want to focus on.  I have not been able to replicate the issue (multiple configuration of the archive to match was was described in this issue and numerous variations pulled from S3 over HTTPS and from GitReleases).  I cannot seem to reproduce the issue.
This is where I suggest we focus.

to

name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=modules/shared_module

I could not replicate the issue in which the archive did not extract to the proper location

Hi @dgraeber, we did try above approach as well, but the modules are downloading directly in the parent folder of archive(_artifactory_shared_modules-1.0.0) instead of _artifactory_shared_modules-1.0.0/modules/shared_module.
But seedfarmer throwing below error
No deployspec.yaml file found in module directory:  /home/jayanth/repo/seedfarmer.archive/_artifactory_shared_modules-1.0.0/modules/shared_module/deployspec.yaml
I even tried just giving only shared_module

name: networking
path: archive::https://artifactory.com/artifactory/shared_module-1.0.0.zip/?module=shared_module

This one also having the same issue and seedfarmer is throwing below error
No deployspec.yaml file found in module directory: /home/jayanth/repo/seedfarmer.archive/_artifactory_shared_modules-1.0.0/shared_module/deployspec.yaml
Which means the zip contains only modules with only one sub folder, it is unziping in the parent directory.

@jayanthmandavilli
Email me directly at<EMAIL_ADDRESS> ?


Automatic addition of missing keys into locale json files

I added an option to the command report, which is -a
It allows to add every missing keys into every json locale files
It supports nested keys
The vue files and the json locale files are still selected with the options -l and -v you already had implemented, but now you can add -a true at the end for example
I noticed you already had an option that allowed a write into a json files (-o output.json) but i didnt quite get why/when it would be helpfull
Example with the new addition :

node ./pkg/dist-node/index.bin.js report -v '{example.path/src}/**/*.?(js|vue)' -l '{example.path/i18n/locale}/**/*.?(json|js)' -a true

This command would still display missing and unused key, but it will also put every missing keys into the json selected by the -l glob
In a typical development workflow this allow a developer to write new vue code, and add new i18n traduction keys {{ $t(new.nested.keys.for.example) }}
Then he can run the script with the option -a set as true as shown above, and every new key he added into his vue files, would be set nested at the correct place in every json languages files
Now the developer only has to hand over the json locale files to a traduction team, or modify new empty keys by himself.
This process is less error prone than writing new keys by hand in every json locale files, it avoids typing mistake
It would be nice if you could review and if its ok integrate the changes into your plugin

Hello @aleduc1.
Thank you for contributing
I would like to merge the PR, but could you please add some.documentation?
It would.be easier for.the users to understand how to.use your command.
It would.be also great if you could add a test :)

Documentation added
Feel free to update me on it if you dislike anything about it

Thank you, @aleduc1! Well done!


Ideas for making context diagrams more compact

Implement lossless "stacking" for references:  if there are multiple connections from A to B that only differ in name, then stack them with a combined name: [first | second | third] or similar (perhaps separated with line breaks).  This would improve, e.g.:

For really large diagrams, ignore packages when stacking and place the stack in the outermost package (or none, or their common root package)


PhoneNumberValidator Throws Compiler Error During MacOS Build

While running a macOS build ($HAXE_HOME/haxelib run lime test mac -release) of the application using feathersui-validators, compiler returns the following error and terminates:
: Error: ./src/feathers/validators/PhoneNumberValidator.cpp:245:50: error: member reference type 'String' is not a pointer; did you mean to use '.'?
: HXLINE(  51)            int len = ( (int)(value->toString()->__Field(HX_("length",e6,94,07,9f),::hx::paccDynamic)) );
:                                           ~~~~~~~~~~~~~~~~~^~
:                                                            .
: ./src/feathers/validators/PhoneNumberValidator.cpp:266:91: error: member reference type 'String' is not a pointer; did you mean to use '.'?
: HXLINE(  64)                            ::String temp = (HX_("",00,00,00,00) + ::Std_obj::string(value->toString()->__Field(HX_("substring",51,f2,e7,e2),::hx::paccDynamic)(i,(i + 1))));
:                                                                                ~~~~~~~~~~~~~~~~~^~
:                                                                                .
: 2 errors generated.

While I encountered the type of error in other places it appeared I was trying to enforce Dynamic.toString() .

Thank you @joshtynjala . Is the fix available with haxelib update feathersui-validators now (?)

@rat-moonshine Not yet, but I plan to release it later today.

feathersui-validators v1.0.1 is now available on Haxelib.


Add support for Metaltech Battledrome *.HMP / Manually change playback speed

Metaltech Battledrome *.HMP files playback incorrectly, at roughly 2x the normal speed, in foo_midi compared to their Metaltech Earthsiege *.HMP counterparts. libADLMIDI also does not have the ES Expansion or BD soundbanks which are distinct compared to the stock ES one.
foo_midi <IP_ADDRESS>, LibADLMIDI
see also: https://github.com/Wohlstand/libADLMIDI/issues/279

Without a copy of the files it is hard to fix this.

ES Banks.zip
ES Music.zip
the games themselves have been freeware since 2015 so ill attach some examples here. contains *.hmp examples for all 3 as well as the sound banks.

ES Banks.zip ES Music.zip the games themselves have been freeware since 2015 so ill attach some examples here. contains *.hmp examples for all 3 as well as the sound banks.

Thx. It seems the HMP/HMI don't have tempo information in them? Doubling the default tempo seems to fix the problem. I'll leave it like that for now.
https://github.com/stuerp/foo_midi/releases/tag/v<IP_ADDRESS>-alpha6

Hi, this change caused issues with several HMP/HMI soundtracks. With this change, the soundtracks for games such as Descent, Descent 2 and Abuse now play at the wrong tempo. Here are some example files.
HMP.zip
References for how these tracks are supposed to sound.
Descent - game01.hmp
Descent - Game02.hmp
Descent 2 - Game01.hmp
Abuse - ABUSE01.HMI

foo_midi adds a hard-coded tempo track before converting the sequence. Any tempo information coming after that should overrule the default.
Is there a way, that you know of, to determine the 'correct' tempo?
If there is none letting the user override the default seems to be the only solution.

@Jenetrix ,
The default tempo for HMI/HMP sequences can be configured in alpha7.

Setting tempo to 80 and setting the Bank to HMI (Earthsiege) gets it most of the way there. The Battledrome and ES Expansion tracks still sound slightly off due to using the incorrect bank as those are not options.

Is there a more recent version that supports the banks? I'd rather not patch the code myself.

Released as v<IP_ADDRESS>.

.


Redshift: add element_content to link_click

@fblundun - looks like we haven't done this one yet. Can you confirm?

Migrated to https://github.com/snowplow/iglu-central/issues/524


AWS Provisioning UI

initial implementation of AWS prov through the UI

volume sizes are currently hardcoded, will make configurable in a subsequent pr

Coverage increased (+0.3%) to 41.46% when pulling 192516b12f84740209cf257962506371033c59fa on josephkane:aws-pro into 127b2f074e118eaabd7c332d17d018b64f1eb881 on supergiant:master.


FW Mission Start - Wheel increases to max deflection (max pwm value)

When starting a mission the nose wheel servo instantly increases to ~2000 pwm and there is no time to recover (turns much too much) - need to actually decrease max angles at which the servo can turn but this is a new issue. Here are three logs with this occurring several times during each log. I was able to fly the missions due to some manual offsetting of the wheel but if left centered it would not work every time.
Using an fmu_v2 during these tests. Logging is on from boot so there is a lot of nothing prior.
https://review.px4.io/plot_app?log=02711563-1bd4-40ee-8107-16fa14017b9e
https://review.px4.io/plot_app?log=0285460d-d71f-422b-9d55-b42bccc66cbb
https://review.px4.io/plot_app?log=732a5f97-563d-4141-ae9b-c4c8691277af

@dagar

I’d be interested to know if anyone else has experienced anything similar.

@ryanjAA We will resolve this within the week as part of the v1.8 sprint.

@LorenzMeier great! looking forward to testing when resolved.

@dagar Could you look into this?

https://review.px4.io/plot_app?log=0285460d-d71f-422b-9d55-b42bccc66cbb

@ryanjAA can you try setting FW_W_RMAX to something reasonable (maybe 30 degrees/s)?

@dagar The first log (https://review.px4.io/plot_app?log=02711563-1bd4-40ee-8107-16fa14017b9e) did have FW_W_RMAX set to 30 (see and and was changed at minute 35 to 1 and then 0 to see the result (see attached photo) so the wheel issue was occurring when set like that (at 30). Only changing it to something unlimited (0) was enabling the post manual offset of the servo linkage to then correct for takeoff but this was very much happening at the 30 deg/s. The following logs are flights after the this initial one and show that even when setting to some other number, it is still present.

Flew master today and all was fine.
https://review.px4.io/plot_app?log=e6d82fe3-9b3b-4f4b-b8c6-5af1e930e1a9


Documentation on reducing the binary size of tflite library on iOS

System information

TensorFlow version: r1.12
Doc Link: https://www.tensorflow.org/lite/

Describe the documentation issue
The tflite library seems to add around 2.5 MB to my iOS binary, which is far bigger than the 700 kB claimed in the documentation. Are there custom build options for tflite like there was with tfmobile that can help get this library size down? I haven't been able to find documentation on how to do this.
For context, I've tried using both the Pod and also used the build_ios_universal_lib.sh script, but the library size still seems to be around 2.5 MB.

@lenaevans Hi, i encounter same problem. I got a binary of libtensorflow-lite.a for arm64, it's around 7.5MB. Do you have any idea on how to reduce the size? Thanks in advance.

I got the library from the build_ios_universal_lib.sh script, and then compiled in xcode with optimizations for space in the compiler settings. At first it looked a lot bigger than it actually was for me because I was looking at the size of the universal framework but once I looked at the size increases of the builds for the individual architectures, the size was a little over 1 MB.

@lenaevans Hi, What did you mean by "compiled in xcode with optimizations for space in the compiler settings", you meant to set some settings in Xcode when compile project which use libtensorflow-lite.a  ?  if so, can you tell me what settings you specified ?  I'm a newbie in this area. Thanks a lot.

Here's a diff of changes that worked for me to reduce the minimal binary size from ~2.9Mb to ~1.1Mb for Aarch64. Note that not all are necessary and I can't guarantee it works for everyone. My binary was running happily just fine:
diff --git a/tensorflow/lite/tools/make/Makefile b/tensorflow/lite/tools/make/Makefile
index 6d4b0c0ce3..f0c398e8a3 100644
--- a/tensorflow/lite/tools/make/Makefile
+++ b/tensorflow/lite/tools/make/Makefile
@@ -55,11 +55,12 @@ LIBS := \
 # There are no rules for compiling objects for the host system (since we don't
 # generate things like the protobuf compiler that require that), so all of
 # these settings are for the target compiler.
-CXXFLAGS := -O3 -DNDEBUG -fPIC
+CXXFLAGS := -Os -DNDEBUG -fPIC -ffunction-sections -fdata-sections -s
 CXXFLAGS += $(EXTRA_CXXFLAGS)
 CFLAGS := ${CXXFLAGS}
 CXXFLAGS += --std=c++11
 LDOPTS := -L/usr/local/lib
+LDFLAGS += -Wl, --gc-sections
 ARFLAGS := -r
 TARGET_TOOLCHAIN_PREFIX :=
 CC_PREFIX :=


Update Install-Instructions

Instructions out of date...

Will include conda/ mamba setup and minimal dvc pull info soon

Also: explain that .env with the path to the dataset has to be created...
export TRAIN_DATASET_PATH="/data/repos/deadtrees/data/dataset/train"


Made some changes in test file

I just copy pasted what you gave me in the issue to every test file Isn't that what you told me to do, please explain me further on what to do ?

I gave an example of an accessibility test to add to files that didn't already have it, but you need to adjust the variable path for each page to make sense, otherwise each test is testing the same page not the page for that specific test

Can you be more specific, i didn't get it

I have converted the issue to an EPIC, so that people can do a PR for individual pages, have a look at the discussion in the issue and keep an eye on the related PRs. Also ask questions in the EddieHub Discord, people are there to help

@iamvbenz49 here is a good first issue to get you started, let me know in the issue if you would like me to assign it to you https://github.com/EddieHubCommunity/LinkFree/issues/6008


add challenge output big test

This expands a related PR #593 with a (passing) test added.
TODO:

[ ] decide whether doing all the cases with pytest.parametrize is the good way. It produces 100 cases each lasting a few seconds. But it seems like a safer first bet, so optimizing the test experience might be a different story

cc/ @boolafish @pik694 @kevsul

Hi, do you mind to PR this against master directly as there is no dependencies on the two PRs so we don't need to wait/block each other.
I do like the idea though, will play around in my PR too.

ah.....so just realize this PR itself is adding 30 mins to the py test job. I doubt is is acceptable to do this for all scenario we would like to cover?
Probably we could lower down to 2 dimensions, which is the num of inputs and outputs. The index always be num - 1 which would cover all indexes as well.

Agreed on that the test running time might be off the limits, however:

Probably we could lower down to 2 dimensions

I'd not go there TBH. I see alternatives:

put the loop inside the test (@pik694 's suggestion)
speed up the test setup-teardown somehow, for example by snapshotting ganache-cli's state. I imagine this could be possible.
paralelize tests in CircleCI with -n option maybe?

We can consider adding those long-running tests now and optimizing the testing experience later too.

changed base to master, so need to merge #593 before this one

put the loop inside the test (@pik694 's suggestion)

How does this help???

put the loop inside the test (@pik694 's suggestion)

How does this help???

Hm, you setup/teardown once per all the parameter combinations, right @pik694 ? My understanding is that the setup (contract deployment) takes a significant portion of those 30 minutes

test would run for ~8 seconds, whereas the setup and teardown would take only ~2 seconds altogether

ah gotcha


Create Telemetry.md

@JuaneloJuanelo @nokafor @TCourtneyOwen This file needs to be renamed and the content double-checked for any needed changes following the review.


[Android] Fix Android publishing configuration

Problem
Android compose library fails to publish with error 403.
Solution

Configure Sonatype repository host to S01
Configure signing

Codecov Report
Patch coverage has no change and project coverage change: +1.78% :tada:

Comparison is base (ed3fe6e) 88.16% compared to head (c692126) 89.95%.
Report is 7 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #780      +/-   ##
============================================
+ Coverage     88.16%   89.95%   +1.78%
============================================
  Files           122       82      -40
  Lines         16296    14708    -1588
  Branches        251        0     -251
============================================
- Hits          14368    13231    -1137
+ Misses         1721     1477     -244
+ Partials        207        0     -207

Flag
Coverage Δ

uitests
?

uitests-android
?

unittests
89.95% <ø> (+1.84%)
:arrow_up:

unittests-android
?

unittests-rust
89.95% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 40 files with indirect coverage changes

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


Add support for Host header

If I want to provide an IP and give a custom Host header (like in cases of hosts behind Cloudflare for example), I have to provide a custom Host header. However, it's passed into the headers argument and is ignored by Go's http lib. See: https://github.com/golang/go/issues/7682
This issue can usually be worked around by adding the IP to your hosts file, but when proxying the requests, this won't help. I have fixed this issue in a way that every Host header passed to -H will be passed as .Host in the requests.
Also, in addCommonHTTPOptions, the function call to mark the URL flag as required was written incorrectly. It was called on the cmdDir instance everytime, and therefore gobuster vhost --wordlist file would not detect the URL flag was missing and ran anyway (with an empty url)

@Vigorwasp thanks for your contribution. Our current development branch is v3.1-working. Can you please rebase your PR to this branch?

I think this might also need a rebase the the cmdDir error is aleady fixed on that branch

Working on it.

Should be sorted now. I kept the Host option in the HTTPOptions struct and and not in BasicHTTPOptions. The way parseCommonHTTPOptions is written atm makes it harder to parse the 'Host' header out of the -H argument without breaking the function's idea (BasicHTTPOptions is parsed in a different function - parseBasicHTTPOptions).
Seems to be working the same way, and gives precedence to the host argument given in the request function, so it doesn't break the vhost functionality.
gobuster dir --url http://localhost -H 'Host: site.com' should work as expected.

@Vigorwasp looks like there are still some errors

@FireFart Not sure why, no conflicts on my end right now.

Looks like because your branch is based on master, not on v3.1-working:

Not sure what's wrong - looks OK on my end.

Are you able to see what are the conflicts?

I would say it's because your branch is based of master and not the working branch but I can only see the grey button on github. Maybe it's best to create a new PR with the changes

@FireFart I'll try to recreate, see if it works then.


How to drag item from nested grid into out grid?

As in jQuery UI droppable.

@ivansglazunov Have you been able to find a solution to this yet? I'm not sure this is supported or even meant to be supported.

At that moment, I did not find a solution. I'll need it again soon and look for it.

+1

+1


Flutter doctor does not evaluate the same version of java that is used when building

Run
flutter config --jdk-dir=<path to java 11>
flutter doctor --verbose

Flutter doctor will show a different version of java.

I was unable to repro on my MacBook nor my Linux VM.
Here is the flutter doctor -v output from my MacBook.

 flutter doctor -v output
[!] Flutter (Channel master, 3.23.0-13.0.pre.162, on macOS 14.5 23F79 darwin-arm64, locale en)
    • Flutter version 3.23.0-13.0.pre.162 on channel master at /Users/andrewkolos/Documents/GitHub/flutter
    ! The flutter binary is not on your path. Consider adding /Users/andrewkolos/Documents/GitHub/flutter/bin to your path.
    ! The dart binary is not on your path. Consider adding /Users/andrewkolos/Documents/GitHub/flutter/bin to your path.
    ! Upstream repository https://github.com/andrewkolos/flutter.git is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to https://github.com/andrewkolos/flutter.git to dismiss this error.
    • Framework revision 6bdebcf58d (4 hours ago), 2024-06-07 13:20:25 -0700
    • Engine revision 1cdbebee19
    • Dart version 3.5.0 (build 3.5.0-236.0.dev)
    • DevTools version 2.36.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/andrewkolos/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_SDK_ROOT = /Users/andrewkolos/Library/Android/sdk
    • Java binary at: /Users/andrewkolos/Downloads/my-jdk/bin/java
    • Java version OpenJDK Runtime Environment Zulu22.30+13-CA (build 22.0.1+8)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    ! CocoaPods 1.12.0 out of date (1.13.0 is recommended).
        CocoaPods is a package manager for iOS or macOS platform code.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To update CocoaPods, see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/andrewkolos/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/231.9392.1.2311.11076708/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.90.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.91.20240529

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554         • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 14.5 23F79 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 14.5 23F79 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 126.0.6478.36

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Here is the output of flutter config --list to confirm that I have --jdk-dir set:

 flutter config --list output
All Settings:
  enable-web: (Not set)
  enable-linux-desktop: true
  enable-macos-desktop: true
  enable-windows-desktop: (Not set)
  enable-android: (Not set)
  enable-ios: (Not set)
  enable-fuchsia: (Not set)
  enable-custom-devices: (Not set)
  cli-animations: (Not set)
  enable-native-assets: true
  enable-flutter-preview: (Not set)
  enable-swift-package-manager: (Not set)
  jdk-dir: /Users/andrewkolos/Downloads/my-jdk

I'm curious, where did flutter doctor display an incorrect java version? Were you reading the version that's displayed under the Android Studio validator? flutter, when building an Android app, will use whatever version you see under the Android toolchain section.
I could definitely see this as being confusing to users—I certainly didn't think of this when you ran this issue by me earlier.

Ah you are correct i was looking at android studio not android toolchain.
❯ flutter doctor --verbose
[✓] Flutter (Channel main, 3.23.0-13.0.pre.154, on macOS 14.5 23F79 darwin-arm64, locale en)
    • Flutter version 3.23.0-13.0.pre.154 on channel main at /Users/reidbaker/flutter-work
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision d849b91ffc (3 days ago), 2024-06-07 10:37:28 -0400
    • Engine revision 98e9393bf2
    • Dart version 3.5.0 (build 3.5.0-234.0.dev)
    • DevTools version 2.36.0

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/reidbaker/Library/Android/sdk/
    • Platform android-34-ext8, build-tools 34.0.0
    • ANDROID_HOME = /Users/reidbaker/Library/Android/sdk/
    • ANDROID_SDK_ROOT = /Users/reidbaker/Library/Android/sdk/
    • Java binary at: /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Zulu11.72+19-CA (build 11.0.23+9-LTS)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[!] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    ! CocoaPods 1.11.3 out of date (1.13.0 is recommended).
        CocoaPods is a package manager for iOS or macOS platform code.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To update CocoaPods, see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version unknown)
    • Android Studio at /Applications/Android Studio with Blaze Beta.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.17-11446219)

[✓] VS Code (version 1.89.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.90.0

[✓] Connected device (3 available)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 14.5 23F79 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 14.5 23F79 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 125.0.6422.142

[✓] Network resources
    • All expected network resources are available.


Add in CMS hints

DESC

subtexts for entry fields / inputs at CMS like below selection of tags

TODOs

[x] add more todos here

added hints


CRAB-39458: Package UDF Editor for Add-on Manager

This PR introduces the coding portion of the packaging and delivery of the UDF Editor Add-on via Add-on Manager. This changes in this PR will then be exercised by a build step, as seen here . Note: this build step will be added to our existing udf-editor build (here) once this PR merges.
To create a .addon, run python package.py from the top directory after pip installing all the requirements in requirements.txt (pip install -r requirements.txt). It will produce a .addon file in the same directory.
The work in this PR is very similar to the work done in this PR.

If you don't mind adding it to your PR, I noticed that requirement.txt should be requirements.txt in the README. https://github.com/seeq12/seeq-udf-ui/blob/96a7151abc46ad18b6faae78be27a420ddbd1a48/README.md?plain=1#L73

Suggest updating the README.md with instructions on how to package the Add-on. Something like what your wrote in the PR description.

To create a .addon, run python package.py from the top directory after pip installing all the requirements in requirements.txt (pip install -r requirements.txt). It will produce a .addon file in the same directory.

If you don't mind adding it to your PR, I noticed that requirement.txt should be requirements.txt in the README.
https://github.com/seeq12/seeq-udf-ui/blob/96a7151abc46ad18b6faae78be27a420ddbd1a48/README.md?plain=1#L73

fixed in the next push!

Suggest updating the README.md with instructions on how to package the Add-on. Something like what your wrote in the PR description.

To create a .addon, run python package.py from the top directory after pip installing all the requirements in requirements.txt (pip install -r requirements.txt). It will produce a .addon file in the same directory.

Fixed in the next push!

For some reason the builds broke after this commit and I'm having trouble identifying why. I'll work on it on Monday.

😑 Okay so the build is now passing with no changes, running one more time to be safe and then I'll merge

The second build passed. I'll merge now.


Add a summary for examples

It seems that only *.wy files can be in this directory.
I want to add a README.md so we can know the examples more.

Failed with message:
Error: ENOENT: no such file or directory, open '/home/runner/work/wenyan-lang/wenyan-lang/examples/README.wy'
I think the test script should ignore non-*.wy files.

Hi @cuixiping , thank you so much for making the summary!
Can you put the README file in ./documentation folder like ./documentation/EXAMPLE.md instead? The example folder is read automatically and the .md files are causing our tests to fail.
Technically we can add an extension filter every time we read the example folder in code, but I think it would be nicer if all the documentation goes into one place. I can add a link to it in the main README to make it more visible. How does that sound?
Thanks!

If we put the README.md file in ./documentation, the summary content cannot present automatically once we enter this examples directory.

Hi, what I was saying is that we put a link to the documentation/EXAMPLES.md in the readme, so presumably users will be able to know its existence before following the link to the ./examples folder. The documentation folder already has a lot of docs of similar nature in there, and I think EXAMPLE.md would fit :)
If you really want to have it in ./examples folder. Please fix the tests/checks. I think you'll need to change runAll in test/examples.test.js, and prgms in tools/make_site.js so that they filters out non-.wy files.
Thank you very much for your help and understanding!

I will take a try. Thank you.

How about we just change the name of examples to hanzi? The stdlib is already in hanzi. Making examples to hanzi can also be imported by other scripts in a better form.

Tests passed, you can take a review. I didn't add documentation/EXAMPLES.md yet. I can write one if necessary.

Awesome! Thank you so much!


Truncate program synthesis

Simplifying the problem by asking the model to generate one line function and then trimming the model output to one line. Also adding a clear separator in the query end to mark where the program should start.

Thanks for the comments, I have incorporated them into the PR.

Great. Thank you for making these changes! Merging now.


Chat bubble colors stay as default

The speech bubbles in chat don't change with the colors I've defined. I have tried all settings and even tried to mess around with the CSS, but nothing seems to work.

I'm using the style avaliable when clicking "Install style" (?) on the README.md.
Edit: I used to use the old version (before 17th September), and now I've installed the style on a new machine with the latest update. Not sure if the version has anything to do with it.

They broke it with their new update. I'll fix it shorty, but you'll have to update it manually to get the latest changes.

Fixed in f26704d, just forgot to add a comment. :sleeping:

Oh my god thank you so much that was so quick! Really love this style and I appreciate your work on it!

Thanks for being so quick!

I'm afraid this is back with the newest update :(

Wouldn't it be possible to target the messages div by structure instead of "._Xxxxx" classes (like ._1lxsr) ?


Frontend performance

Benchmarks using Vagrant to spin-up a "CWP-like" environment, on a SilverStripe site traditionally having a ~15s av response time (Siege stress-testing with 10 concurrent users, 10s nominal request-interval over 60s) without caching, results in a 6s average with the module.
However, standard partial caching in the same tests yielded results in the ~2s range. This is likely because of a). A single cache file measuring ~2Mb, pulled from disk into memory and PHP still having to execute list-based logic in memory.
This ticket is therefore a placeholder for improvements we can make to performance viz the following suggestions;

Reduce the size of the serialized object that is ultimately cached
Benchmark use of RAM disk such as tmpfs and /dev/shm (where available).
Look at improvements to Zend_Cache_Frontend_Class and the options being passed to it

Note: Subsequent similar tests, have yielded results much closer to Partial Caching performance speeds. Need to re-run and ensure it wasn't the fact that APC was enabled with PHP5.5 that skewed results...


Incorrect memory values

HS premium memory optimized tier has double the amount of ram available per vCore. Only 24, 64 and 80 core columns had the right values.

Messed up


port to python3

Hello, is there any plan to merge this PR to support Python3?
I tested it on Debian 11 and seems to work as expected.


Adds support for inferred project isolation by projectRootPath

This adds early support to create multiple "inferred projects" isolated by a project root path. Currently this requires providing an additional --useInferredProjectPerProjectRoot argument to tsserver. We may choose to fold this functionality into the existing --useSingleInferredProject, but that could constitute a breaking change.
This also adds support to define the default configuration for inferred projects under a project root path, though the addition of an optional projectRootPath property on SetCompilerOptionsForInferredProjectsArgs.
Fixes #16961

@mjbvz Does this meet the needs of VS Code?


Fix Spanish copy in a few places

Details
Just some copy
Fixed Issues
$ https://github.com/Expensify/App/issues/17184
Tests / QA Steps

Open the app

Enter an email address of an account that already exists.

Continue to the next screen

Under the Sign in button, the copy to go back should say: Not <email?>? Go back

Change the language to Spanish and repeat the process. Now the copy under Conectarse should say: ¿No eres <email>? Volver.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@thesahindia @beamanator One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

It's all Spanish copy changes, so just leaving @iwiznia as reviewer.

Updated, I cleaned even more copy and retested it for the change in the login page.

@iwiznia Ok, went through everything we changed to add more "por favor" when the english copy has it.

Not emergency, but just copy changes, so I did not do the reviewer checklist

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/iwiznia in version: 1.3.1-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


More than one demolition at the same time only counts as one demolition

We need to handle the demolitions better

done ez
we might want to deal hp to the boss in other ways than demolitions, but we can just add some class that handles the "alternative demolition" resources. The player stats state can then use that class to check other ways that the boss might have lost HPs.


use request URI when servlet path is not available

What does this PR do?
In some cases, the servlet path is not available, for example when a filter is handling the request.
As a result, the transactions that are created by a filter do not always get properly filtered, and the ignore_urls configuration is ignored.
Checklist

[x] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[x] I have added tests that would fail without this fix

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-08-31T14:08:28.738+0000

Duration: 19 min 26 sec

Commit: 1326715e4e0bdaca848a5c1fa8778f8021c9b8ff

Trends :test_tube:

Steps errors
Expand to view the steps failures

mvn install

Took 5 min 1 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 3 min 30 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 3 min 35 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 3 min 38 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 3 min 32 sec . View more details on here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

Log output
Expand to view the last 100 lines of log output

[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-javalin-plugin .................. SUCCESS [  0.357 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:elastic-apm-agent ................... SUCCESS [ 13.789 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-agent-benchmarks ................ SUCCESS [  5.198 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-spring-resttemplate-test ........ SUCCESS [  0.643 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-logback-plugin-legacy-tests ..... SUCCESS [  0.480 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-es-restclient-plugin-7_x ........ SUCCESS [  0.892 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-jms-spring-plugin ............... SUCCESS [  0.624 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-jedis-2-tests ................... SUCCESS [  0.653 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-jedis-3-tests ................... SUCCESS [  0.489 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-lettuce-3-tests ................. SUCCESS [  0.625 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-grpc-test-1.6.1 ................. SUCCESS [  9.585 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-grpc-test-latest ................ SUCCESS [  8.046 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-rabbitmq-test-3 ................. SUCCESS [  0.499 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-rabbitmq-test-4 ................. SUCCESS [  0.515 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-okhttp-test ..................... SUCCESS [  0.509 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-vertx3-test-latest .............. SUCCESS [  0.634 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-opentracing ..................... SUCCESS [  1.014 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:integration-tests ................... SUCCESS [  0.185 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:simple-webapp ....................... SUCCESS [  0.736 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:jsf-app ............................. SUCCESS [  0.187 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:jsf-app-dependent ................... SUCCESS [  0.338 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:jsf-app-standalone .................. SUCCESS [  0.637 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:cdi-app ............................. SUCCESS [  0.187 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:cdi-app-dependent ................... SUCCESS [  0.304 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:cdi-app-standalone .................. SUCCESS [  0.456 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:soap-test ........................... SUCCESS [  0.371 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:external-plugin-test ................ SUCCESS [  0.203 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:plugin-instrumentation-target ....... SUCCESS [  0.251 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:external-plugin-app ................. SUCCESS [  0.232 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:external-plugin ..................... SUCCESS [  0.585 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-agent-attach .................... SUCCESS [  1.550 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:apm-agent-attach-cli ................ SUCCESS [  5.117 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:application-server-integration-tests  FAILURE [  0.637 s]
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-1-5 ..................... SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-2 ....................... SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-2-base .................. SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-2-jetty ................. SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-2-tomcat ................ SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] co.elastic.apm:spring-boot-2-undertow .............. SKIPPED
[2021-08-31T14:27:38.681Z] [INFO] ------------------------------------------------------------------------
[2021-08-31T14:27:38.681Z] [INFO] BUILD FAILURE
[2021-08-31T14:27:38.681Z] [INFO] ------------------------------------------------------------------------
[2021-08-31T14:27:38.681Z] [INFO] Total time:  02:30 min
[2021-08-31T14:27:38.681Z] [INFO] Finished at: 2021-08-31T14:27:38Z
[2021-08-31T14:27:38.681Z] [INFO] ------------------------------------------------------------------------
[2021-08-31T14:27:38.681Z] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project application-server-integration-tests: Compilation failure
[2021-08-31T14:27:38.681Z] [ERROR] /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-2099/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests/src/test/java/co/elastic/apm/servlet/AbstractServletContainerIntegrationTest.java:[331,12] error: cannot find symbol
[2021-08-31T14:27:38.682Z] [ERROR]   symbol:   method executeStatusRequestAndCheckIgnored(String)
[2021-08-31T14:27:38.682Z] [ERROR]   location: class AbstractServletContainerIntegrationTest
[2021-08-31T14:27:38.682Z] [ERROR] -> [Help 1]
[2021-08-31T14:27:38.682Z] [ERROR]
[2021-08-31T14:27:38.682Z] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[2021-08-31T14:27:38.682Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2021-08-31T14:27:38.682Z] [ERROR]
[2021-08-31T14:27:38.682Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2021-08-31T14:27:38.682Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[2021-08-31T14:27:38.682Z] [ERROR]
[2021-08-31T14:27:38.682Z] [ERROR] After correcting the problems, you can resume the build with the command
[2021-08-31T14:27:38.682Z] [ERROR]   mvn <args> -rf :application-server-integration-tests
[2021-08-31T14:27:38.713Z] Sleeping for 10 sec
[2021-08-31T14:27:50.216Z] Stage "Tests" skipped due to earlier failure(s)
[2021-08-31T14:27:50.434Z] Stage "Unit Tests" skipped due to earlier failure(s)
[2021-08-31T14:27:50.447Z] Stage "Smoke Tests 01" skipped due to earlier failure(s)
[2021-08-31T14:27:50.458Z] Stage "Smoke Tests 02" skipped due to earlier failure(s)
[2021-08-31T14:27:50.470Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2021-08-31T14:27:50.481Z] Stage "Javadoc" skipped due to earlier failure(s)
[2021-08-31T14:27:50.663Z] Failed in branch Unit Tests
[2021-08-31T14:27:50.672Z] Failed in branch Smoke Tests 01
[2021-08-31T14:27:50.681Z] Failed in branch Smoke Tests 02
[2021-08-31T14:27:50.689Z] Failed in branch Benchmarks
[2021-08-31T14:27:50.698Z] Failed in branch Javadoc
[2021-08-31T14:27:50.980Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2021-08-31T14:27:51.081Z] Stage "JDK Compatibility Tests" skipped due to earlier failure(s)
[2021-08-31T14:27:51.300Z] Stage "Matrix - JAVA_VERSION = 'openjdk12'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.307Z] Stage "Matrix - JAVA_VERSION = 'openjdk13'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.314Z] Stage "Matrix - JAVA_VERSION = 'openjdk14'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.320Z] Stage "Matrix - JAVA_VERSION = 'openjdk15'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.326Z] Stage "Matrix - JAVA_VERSION = 'openjdk16'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.430Z] Stage "Matrix - JAVA_VERSION = 'openjdk12'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.440Z] Stage "Matrix - JAVA_VERSION = 'openjdk13'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.447Z] Stage "Matrix - JAVA_VERSION = 'openjdk14'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.453Z] Stage "Matrix - JAVA_VERSION = 'openjdk15'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.459Z] Stage "Matrix - JAVA_VERSION = 'openjdk16'" skipped due to earlier failure(s)
[2021-08-31T14:27:51.834Z] Failed in branch Matrix - JAVA_VERSION = 'openjdk12'
[2021-08-31T14:27:51.843Z] Failed in branch Matrix - JAVA_VERSION = 'openjdk13'
[2021-08-31T14:27:51.853Z] Failed in branch Matrix - JAVA_VERSION = 'openjdk14'
[2021-08-31T14:27:51.861Z] Failed in branch Matrix - JAVA_VERSION = 'openjdk15'
[2021-08-31T14:27:51.870Z] Failed in branch Matrix - JAVA_VERSION = 'openjdk16'
[2021-08-31T14:27:52.136Z] Stage "Stable" skipped due to earlier failure(s)
[2021-08-31T14:27:52.232Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-08-31T14:27:52.280Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-08-31T14:27:53.494Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-2099
[2021-08-31T14:27:53.777Z] [INFO] getVaultSecret: Getting secrets
[2021-08-31T14:27:53.830Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-08-31T14:27:54.819Z] + chmod 755 generate-build-data.sh
[2021-08-31T14:27:54.819Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-2099/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-2099/runs/1 FAILURE 1165797
[2021-08-31T14:27:54.819Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-2099/runs/1/steps/?limit=10000 -o steps-info.json
[2021-08-31T14:27:55.069Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-2099/runs/1/tests/?status=FAILED -o tests-errors.json
[2021-08-31T14:27:55.070Z] Retry 1/3 exited 22, retrying in 1 seconds...
[2021-08-31T14:27:55.981Z] Retry 2/3 exited 22, retrying in 2 seconds...

:grey_exclamation: Flaky test report
No test was executed to be analysed.


undefined is not an object (evaluating 'this.config.loggerProvider')

Expected Behavior
Events are logged without errors.
Current Behavior
Crashed in non-app<EMAIL_ADDRESS>in SpecialEventType
Possible Solution
none
Steps to Reproduce
import { init as amplitudeInit, track } from "@amplitude/analytics-react-native";
amplitudeInit("xxxxxxxx");
track(eventName);
Environment

expo 46 / react native

"<EMAIL_ADDRESS>  version "1.4.5"
  resolved<EMAIL_ADDRESS>  integrity sha512-ELAP6ivg+13uSk+TOirGZE/92M+tTbeiQ/i7eXgDO4Hiy00Abf/UxO/rp9WovtxCyeFYTILrujEYxPv5cRQmFw==
  dependencies:
    "@amplitude/ua-parser-js" "0.7.31"

"<EMAIL_ADDRESS>  version "0.6.4"
  resolved<EMAIL_ADDRESS>  integrity sha512-RuWkLGO89O/8x88J7OPMIB1sSZ+toAJQeEI+KFkZGU1uQ0znhF1nLe64UUi39mP7qLMFYtQfXVD8IfNLIJt7IQ==
  dependencies:
    "@amplitude/analytics-types" "^0.6.1"
    tslib "^2.3.1"

"<EMAIL_ADDRESS>  version "0.2.1"
  resolved<EMAIL_ADDRESS>  integrity sha512-9Cvascq1XpkvNPzMDdh90qKaeDILZD9E99M/nI+x4VjHUW0f+ytoDTuOcTG5ItO8baEmY2xBMu5UgTPSPnu33g==
  dependencies:
    "@amplitude/analytics-connector" "1.4.5"
    "@amplitude/analytics-core" "^0.6.4"
    "@amplitude/analytics-types" "^0.6.1"
    "@amplitude/ua-parser-js" "^0.7.31"
    "@react-native-async-storage/async-storage" "^1.17.7"
    tslib "^2.3.1"

"<EMAIL_ADDRESS>  version "0.6.1"
  resolved<EMAIL_ADDRESS>  integrity sha512-6XWxxt0LYMkOLZHnAzLoDRwhMcOeNviXEdba6tVVjYOM9zW6ZOCLZWO3N+/s+UF6tYOvDZyLH6a1PqAlNUvHqQ==

"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>  version "0.7.31"
  resolved<EMAIL_ADDRESS>  integrity sha512-+z8UGRaj13Pt5NDzOnkTBy49HE2CX64jeL0ArB86HAtilpnfkPB7oqkigN7Lf2LxscMg4QhFD7mmCfedh3rqTg==

Hi @ahilles107, thanks for choosing Amplitude! This was a known issue but has been fixed. Looking at the versions you have in your lock file, I do not expect this issue to show up anymore.
I have created an expo app here: https://github.com/kevinpagtakhan/TS-185 to try to reproduce the error you are seeing, specifying the same amplitude dependencies in my lock file and added calls to amplitude in App.js. I am not able to reproduce the issue.
Is it possible that you recently upgraded to the specified version and the old version was somehow still cached and being loaded onto your app? I am able to reproduce the error in an older version.
In addition, we also have released more patch versions for @amplitude/analytics-react-native and it would be best to bump up to get the latest and greatest.

@ahilles107 , thanks for reporting this! Based on @kevinpagtakhan 's investigation, could you try a fresh install of latest @amplitude/analytics-react-native, clear caches, and run expo with --clear? See https://docs.expo.dev/troubleshooting/clear-cache-macos-linux/.

Hey folks! You are right, sorry for the trouble. An error was caught by Sentry on a production where we have older versions of libraries installed. After deps upgrade, I can't reproduce it anymore.


Add time_limit option

Closes #27

Apologies for the delay. I have two main concerns:

The solve function happens to perform factorizations as well. These are not fully interruptible and the issue you pointed out in

It would be very surprising to set a 50ms total time limit and see a setup phase for a large problem take a few seconds.

can exactly happen during the solve function.

Many solvers implementing the time_limit option do not separate the setup/preprocessing phase from the solve phase. I have a few examples.

In CPLEX they have the timelimit parameter https://goo.gl/b5BsJr which consists of

The time limit for an optimizer applies to the sum of all its steps, such as preprocessing, crossover, and internal calls to other optimizers.
In a sequence of calls to optimizers, the limit is not cumulative but applies to each call individually. For example, if you set a time limit of 10 seconds, and you call MIP optimization twice then there could be a total of (at most) 20 seconds of running time if each call consumes its maximum allotment.

In GUROBI they have ‘TimeLimit’ http://www.gurobi.com/documentation/7.5/refman/timelimit.html consisting of

Limits the total time expended (in seconds). Optimization returns with a TIME_LIMIT status if the limit is exceeded

In IPOPT they do not have a special interrupt callback but they just state that the time limit is checked at certain places. See the max_cpu_time option: https://goo.gl/Htia3x

Maximum number of CPU seconds. A limit on CPU seconds that Ipopt can use to solve one problem. If during the convergence check this limit is exceeded, Ipopt will terminate with a corresponding error message.

Nobody splits the time_limit in setup vs solve phases. That’s why I am concerned. For simplicity, code maintainability and library-free solutions I would try to stick with a compromise similar to what they did in Ipopt, i.e., setting a time_limit without having fully interruptible routines.

@ebarnard I have to ask you to sign the CLA before being able to merge.

I completely agree that time_limit should limit the total time.
Given factorisations take place in osqp_solve the idea of limiting only solve time seems pretty pointless so I'm happy to land this PR as is.
However, the current time limit situation isn't ideal. In my mind this is what it should look like:

time_limit limits the time taken for a logical solve i.e. the total time of osqp_setup, any osqp_update_* calls, and osqp_solve.
osqp_setup and osqp_update_* queue any expensive operations to take place during the next call to osqp_solve. Frequent termination checks are added to osqp_solve.
(maybe eventually) osqp_setup is fully interruptible.

If you agree with 1 & 2 I'll have a look at how easy this would be to implement.

@bstellato I think this is ready to merge.

Great! Merging this version for now. I like the idea of queuing the expensive operations inside osqp_solve. It will make it easier to track the execution time. However, we should make sure there are no extra memory allocations required in doing so (e.g., more matrices or vectors stored).


Lexicographic sort in table visualizations

It would be nice to be able to sort tables lexicographically instead of just by metric. This would be especially nice for time tables, since it would let you see the rows in time order.

This is fixed in the latest release :-)


Adding user agent for outgoing requests

Will make it easier to track usage

:) open to PRs if you want to contribute :)

We have some client meetings & pitches next week so won't be able to work
on this till after.
On Thu, Nov 3, 2016 at 8:40 AM James Campbell<EMAIL_ADDRESS>wrote:

:) open to PRs if you want to contribute :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Bottr-js/Bottr/issues/35#issuecomment-258131506, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuQtBVRs_549ZtK4B4rXcvmqGbNXrmmks5q6dZZgaJpZM4KYBEG
.

No worries :)


Custom title bar

Slack enables this features when more then one workspace is logged in. It would be nice if Mattermost has this by default. This would make the app more unique between others. The default title bar does not fit into the design.
Here a screenshot:

Closing via feature request ticket here: https://mattermost.uservoice.com/forums/306457-general/suggestions/36818959-desktop-custom-title-bar.


How to check the "maxResponse" that the Ollama model supports?

What is the issue?
I wanna know How to check the "maxResponse" that the Ollama model supports?  and how to set this parameter.
I can obtain the context length information using the following command:
(base) [root@gpu ~]# ollama show glm4:9b
  Model
    architecture        chatglm
    parameters          9.4B
    context length      131072
    embedding length    4096
    quantization        Q4_0

  Parameters
    stop    "<|system|>"
    stop    "<|user|>"
    stop    "<|assistant|>"

  License
    The glm-4-9b License

The following output content is incomplete, apparently due to the content being truncated by the maxResponse setting. Could you please tell me how to set the maxResponse parameter?
````````````glm4:9b``````````````````
Based on the provided document, here is a summary of China World Trade Center Co., Ltd.'s (CWT) 2024 half-year report:

Company Overview: CWT is primarily engaged in property investment and management, including office buildings, shopping malls, apartments, and hotel operations. It manages its business through its own efforts, except for the hotel business which is managed by Shangri-La International Hotel Management Limited.

Financial Highlights:

Revenue: Increased by 1.4% to RMB 19.7 billion.
Net Profit: Increased by 5.18% to RMB 0.68 per share.
Net Profit attributable to shareholders: Increased by 4.19% to RMB 674.6 million.
Operating Cash Flow: Decreased by 5.06% to RMB 9.42 billion.
Market Analysis:

Office market in Beijing faced challenges with low demand

OS
No response
GPU
No response
CPU
No response
Ollama version
No response

The maximum response is essentially the size of  the context window minus the length of the input.  You can lower this by setting num_predict in the API call.

Thank you for your reply. I don't quite understand this part --- "lower this by setting num_predict". I hope to get as much output information as possible. Should I increase the num_predict parameter?
Or, is there another approach? Can I achieve more output information by reducing the length of the input content without adjusting the num_predict parameter?

Where in the log files can I find information about num_predict, maximum response, and the length of the input?
Is the number 105811 means length of the input content  in the  log?
ollama.log
10月 16 16:13:58 gpu ollama[24746]: DEBUG [update_slots] slot progression | ga_i=0 n_past=0 n_past_se=0 n_prompt_tokens_processed=105811 slot_id=0 task_id=3 tid="139848999747584" timestamp=1729066438

The issue I'm facing now is that the model's output is always incomplete. I need to resolve this problem.

hi bro, I found these two pieces of information in the log. Please don't respond for now, as I've discovered a new issue: when the input context is relatively large, the response tokens sent to Ollama default to updating to 200 tokens (if the context is smaller, this generation token is the actual value I pass to Ollama). This is why the model's responses are incomplete. I will look into this 200-token issue and update the information. I'll come back to you for advice then
prompt eval time     =     469.81 ms / 52919 tokens
generation eval time =   11332.11 ms /   200 runs
10月 16 20:50:49 gpu ollama[24746]: DEBUG [print_timings] prompt eval time     =     469.81 ms / 52919 tokens (    0.01 ms per token, 112638.67 tokens per second) | n_prompt_tokens_processed=52919 n_tokens_second=112638.6724902727 slot_id=0 t_prompt_processing=469.812 t_token=0.008877945539409286 task_id=209 tid="140372587372544" timestamp=1729083049
10月 16 20:50:49 gpu ollama[24746]: DEBUG [print_timings] generation eval time =   11332.11 ms /   200 runs   (   56.66 ms per token,    17.65 tokens per second) | n_decoded=200 n_tokens_second=17.6489638734534 slot_id=0 t_token=56.66055 t_token_generation=11332.11 task_id=209 tid="140372587372544" timestamp=1729083049
10月 16 20:50:49 gpu ollama[24746]: DEBUG [print_timings]           total time =   11801.92 ms | slot_id=0 t_prompt_processing=469.812 t_token_generation=11332.11 t_total=11801.922 task_id=209 tid="140372587372544" timestamp=1729083049
10月 16 20:50:49 gpu ollama[24746]: DEBUG [update_slots] slot released | n_cache_tokens=53119 n_ctx=128032 n_past=53118 n_system_tokens=0 slot_id=0 task_id=209 tid="140372587372544" timestamp=1729083049 truncated=false


Protein Family Sorter tool not working on beta when contains private genome

2 Ochrobactrum
40 Public Brucella
1 Private Brucella
Never returned results

fixed on beta

Checked. PFS ins now working with private genomes.


Chore 127 flakey webassembly tests

Introduces test reliability in GitHub Actions CI
Trial and error.... I found that specific tests in test/basic.test.js fail regularly when tap tests are run in parallel (as they are by default). I think there were some 0x generated resources being shared across tests.
Specifying -j1 in the npm ci test command forces parallelism off globally, but when doing so, the specific test for wasm  regularly failed (times out) - so I've added a specific t.jobs=2 for the wasm test.
Tests are now all passing reliably in CI.

Fixes #127

I would recommend the use of a .taprc file.


fixed typo in testEncryptWithoutSalt

This cannot be changed anymore, as it would be a BC break.
Sorry, closing as inapplicable.

@Ocramius
This is an unit test and not a part of the public API!

Urgh, I really need to read namespaces better -.-
Sorry @AshishThakur, re-opening.

Manually merged to develop via zendframework/zend-crypt@40b29b5f4c7a6a8fc0b36d9d07351f86f01036a4


Question: about task scheduling in laravel

Describe you feature request
The laravel docs say "when using Laravel's scheduler, we only need to add a single cron configuration entry to our server that runs the schedule:run command every minute. If you do not know how to add cron entries to your server, consider using a service such as Laravel Forge which can manage the cron entries for you  * * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1 ", which relies on cron, but when we build a static binary, does that mean we can't use laravel's task scheduler?

I think you can still use the task scheduler, you just need  to have cron on the system where you are running the binary. Then instead of calling php artisan schedule:run, you would call ./frankenphp php-cli artisan schedule:run, if that's what you mean. I haven't tried it myself tough.


LLVM updates & green commit tracking

There's an ongoing experiment to keep mhlo, torch-mlir and onnx-mlir in sync with respect to their llvm commit. These projects historically have different update cadences and rarely converge on a single commit. The current effort is to make sure that they converge at least sometimes with mhlo and torch-mlir having weekly updates and onnx-mlir having roughly monthly updates (though more frequent is possible for each of the projects).
The commit tracking is happening here: https://github.com/llvm/torch-mlir/issues/1178 and the "green" commit is guaranteed to have a green build and lit tests for llvm, lld, lldb and mlir on Ubuntu and Windows, though we can expand the testing to including more platforms if necessary.
The latest update to the llvm commit in onnx-mlir put it in sync with torch-mlir, further updates should attempt to do the same and it would be beneficial for everyone if anyone working on an update tries to pick up a green commit from the experiment and comments here to let others know that an update is in progress.

@AlexandreEichenberger

PR #1628 updates LLVM with this green commits:
Week of 8/22/2022:
Green LLVM commit: e5d5146323ffaa13eb5185616c6ae5c36b69352d
Green MHLO commit: ace4030dd55fce2a74e46f71f1937feb61ed1e3f (branch greencommit/2022-08-22-e5d51463)

PR #1628 merged

@AlexandreEichenberger @tungld
It seems https://github.com/llvm/llvm-project/commit/e5d5146323ffaa13eb5185616c6ae5c36b69352d fails some installation tests (cmake --build . --target check-mlir) on Linux s390x. This seems to be fixed by https://github.com/llvm/llvm-project/commit/df4e637ca7ef4ef17b662845120864921e65bb67 I confirmed that on buildbot and my own environment. The error is the same with this build bot results
I think these errors are not critical for onnx-mlir, but it might be better to update the commit again after the green commit is updated.

This seems to be fixed by https://github.com/llvm/llvm-project/commit/df4e637ca7ef4ef17b662845120864921e65bb67

Does this really fix the issue on s390x? I saw it just marked them as UNSUPPORTED and the comment says: // Bytecode currently does not support big-endian platforms

We're in the process of preparing an update PR for the green commit from Nov. 14, and realize we may be unknowingly duplicating effort with others.

There is no duplicating effort from our side as far as I know. Thanks!

I see contributors to the torch-mlir project have organized a rotation scheme for managing updates to green commits: https://github.com/llvm/torch-mlir/wiki/Weekly-LLVM-Update, as a result of discussion to see if there was enough support.
I see the topic of updating was discussed in https://github.com/onnx/onnx-mlir/wiki/Informal-meeting-agenda-and-notes#september-13rd-2022 and wonder if there was any support for adopting a more predictable approach?

@AlexandreEichenberger : Can we add this to the agenda for the community meeting in the next couple of weeks if it hasn't been discussed yet?

@christopherbate @gargaroff
We are trying to get two folks from each actively participating company to help out with the LLVM update. The process has been pretty smooth the last couple of iterations, largely because by doing it regularly, it reduces the amount of work to do for each iteration.
Would you consider another volunteer from NVIDIA and AMD? That would be greatly appreciated.
Big thanks for helping out.
You can select your preferred time here: https://github.com/onnx/onnx-mlir/wiki/LLVM-Update-Schedule

@AlexandreEichenberger I could do another bump in the week of 2023-05-01.

@chenchongsong @tungld I saw in PR #2252 you bumped the LLVM commit to a "non standard" commit
I think we need to be cautious about that because it brings us out of sync with torch-mlir, which I understood to be a key motivation for our LLVM updates process
hopefully it doesn't create any problems but in the future please post here in the master issue to build consensus before we diverge from the commits from https://github.com/llvm/torch-mlir/issues/1178

@chenchongsong @tungld I saw in PR #2252 you bumped the LLVM commit to a "non standard" commit
I think we need to be cautious about that because it brings us out of sync with torch-mlir, which I understood to be a key motivation for our LLVM updates process
hopefully it doesn't create any problems but in the future please post here in the master issue to build consensus before we diverge from the commits from llvm/torch-mlir#1178

@chenchongsong We should only be using the green commits mentioned by @ashay to keep things in sync. I actually think the recent issues @cjvolzka and @negiyas are seeing maybe related to this. I am going to revert the LLVM commit to d421f5226048e4a5d88aab157d0f4d434c43f208 to see if this solves the issue. The below issue just started to occur with the recent LLVM bump:
$ ./build/Debug/bin/onnx-mlir -mcpu=z14 --EmitONNXIR  bidaf-9-nocategorymaper-onnxbasic.mlir
onnx-mlir: /home1/negishi/src/dlc.git/llvm-project/llvm/include/llvm/Support/Casting.h:566: decltype(auto) llvm::cast(const From&) [with To = mlir::RankedTensorType; From = mlir::Type]: Assertion `isa<To>(Val) && "cast<Ty>() argument of incompatible type!"' failed.
./compile-bidaf9.sh: line 76: 642957 Aborted                 (core dumped) /home1/negishi/src/dlc.git/onnx-mlir.main/build/Debug/bin/onnx-mlir -mcpu=z14 --EmitONNXIR bidaf-9-nocategorymaper-onnxbasic.mlir


[HUDI-3974] Fix schema projection to skip non-existent preCombine field

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Given we're punting on this fix for 0.11, i think we can avoid making these changes in the light of #5430 following up fairly soon
WDYT?

Agree.  This is more like a bandaid fix for the 0.11.0 release.  Since we don't need this for 0.11.0, we should close this one in favor of #5430 which is a proper fix and improvement.  Closing this PR.


feat: add bria payouts

Closing in favour of an updated version of this branch. Current state also capture in PR #2681


manifest.yaml referenced in quickstart does not exist

Hi,
I'm trying to follow your quickstart tutorial at https://docs.epinio.io/tutorials/quickstart
In the step "Push an application" you tell me to clone
git clone https://github.com/epinio/epinio.git
cd epinio/assets

two lines later, I'm supposed to do
epinio push manifest.yaml

however, there is no manifest.yaml in the whole epino repository.

Hey @domdorn , you need to create your manifest.yaml by following this pattern - https://docs.epinio.io/references/manifests#manifest-format


S3 crt client doesn't pick up the default region

Confirm by changing [ ] to [x] below to ensure that it's a bug:

[ x] I've gone though Developer Guide and API reference
[ x] I've searched for previous similar issues and didn't find any solution

Describe the bug
S3-crt client doesn't automatically get the region unlike the S3 client which automatically fetches region (using the chain of AWS_DEFAULT_REGION -> profile -> instance metadata). The user is forced to provide the correct region when creating the s3-crt client
SDK version number
1.9
Platform/OS/Hardware/Device
EC2 Linux instance
To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code)
Create S3 client without setting region in the client config. It automatically picks up the default region from the profile/instance metadata (This is as expected from version 1.8 as mentioned here - https://aws.amazon.com/blogs/developer/aws-sdk-for-c-version-1-8-developer-preview/)
Create S3-crt client without setting region in the client config. It does not pick the default region as expected.
Expected behavior
S3-crt client should automatically pick up the default region as done by the S3 client

Hi @dhananjays ,
So, it seems like you've figured out the workaround , but for the record this behavior is not expected of the s3-crt default constructor.
The s3-crt default provider chain is reduced to make it faster to go through, and it will only check for the region in the environment variable, the profile in the config file or the one hard coded.
Having said that, this could be a feature request, but I can't make any promises on when we could work on it.

Here is how we back-ported that in our code, since we ran into the same issue: the CRT does not pickup AWS_{,DEFAULT_}REGION:
        Aws::S3Crt::ClientConfiguration config;
        // ...
        config.region = []() -> Aws::String {
            // Return the configured AWS region, using us-east-1 as fallback. This is normally part
            // of Aws::Client::ClientConfiguration, but is not implemented for the S3CrtClient.
            Aws::String region = os::getenv("AWS_DEFAULT_REGION");
            if (!region.empty()) {
                return region;
            }

            region = os::getenv("AWS_REGION");
            if (!region.empty()) {
                return region;
            }

            // The profile may also contain a region value.
            if (Aws::Config::HasCachedCredentialsProfile("default")) {
                region = Aws::Config::GetCachedCredentialsProfile("default").GetRegion();
                if (!region.empty()) {
                    return region;
                }
            }
            return Aws::Region::US_EAST_1;
        }();

The problem is also resolved by #1884.

Merged: https://github.com/aws/aws-sdk-cpp/pull/2098

Thank you.


Reduce time to execute tests by 10 minutes

Do we really need this test?
If yes, what about paralleling it?

yes we need it because we had a bug where actions were not running for the full 5 minutes.

note it doesn't run on travis, only internal jenkins.

Why don't we do this for swift?

we could - iirc i explained this away as python proxy is the same one used for swift, so it was low risk because the bug/issues was from the node proxy.

Expected that answer.
Change is still LGTM. Parallelising this is goodness.

already pg'ed?


WIP: Temporary fix for #4118 in acs-engine v0.24

What this PR does / why we need it:
The October windows image MicrosoftWindowsServer:WindowsServerSemiAnnual:Datacenter-Core-1803-with-Containers-smalldisk:1803.0.20181017 brought in Docker EE-basic 18.03, which has a problem with Kubernetes v1.12 (https://github.com/kubernetes/kubernetes/issues/69996)
This puts in a temporary workaround. The best fix to avoid this problem long term is to enable acs-engine to deploy a specific Docker version so they can be tested before release, and pinned if necessary. That fix is in #4119 but will be in acs-engine v0.25 later.
Which issue this PR fixes
fixes #4118

This doesn't work yet. do not merge

Ok, working now
$ kubectl get node
NAME                    STATUS    ROLES     AGE       VERSION
39001k8s9000            Ready     agent     4m40s     v1.12.1
39001k8s9001            Ready     agent     4m57s     v1.12.1
k8s-master-39001978-0   Ready     master    7m35s     v1.12.1

patrick@plang-h1:~/plang1029$ kubectl get node -o wide
NAME                    STATUS    ROLES     AGE       VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                    KERNEL-VERSION   CONTAINER-RUNTIME
39001k8s9000            Ready     agent     4m57s     v1.12.1   <IP_ADDRESS>   <none>        Windows Server Datacenter   10.0.17134.345
                        docker://18.3.1
39001k8s9001            Ready     agent     5m14s     v1.12.1   <IP_ADDRESS>   <none>    Windows Server Datacenter   10.0.17134.345
                        docker://18.3.1
k8s-master-39001978-0   Ready     master    7m52s     v1.12.1   <IP_ADDRESS>   <none>    Ubuntu 16.04.5 LTS   4.15.0-1023-azure   docker://1.13.1

I have a comment in there not to merge this to master. We'll get the master branch moved up to Docker 18.09 which doesn't need this workaround.

I will be updating this to build on top of #4119 instead


update template

Codecov Report
Base: 96.83% // Head: 96.83% // No change to project coverage :thumbsup:

Coverage data is based on head (c018b44) compared to base (7364b79).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #386   +/-   ##
=======================================
  Coverage   96.83%   96.83%
=======================================
  Files          37       37
  Lines        1993     1993
  Branches      175      175
=======================================
  Hits         1930     1930
  Misses         37       37
  Partials       26       26

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Ability to retry a data provider in case of failures

TestNG Version

Note: only the latest version is supported

7.6.1
Expected behavior
The data provider is retried automatically
Actual behavior
No generic mechanism to retry a data provider without doing it at a per data provider level.
Is the issue reproducible on runner?

[X] Shell
[X] Maven
[X] Gradle
[X] Ant
[X] Eclipse
[X] IntelliJ
[X] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

No testcase, since this is a new requirement. For more details please take a look at this user post https://groups.google.com/g/testng-users/c/7Q40qIPcOLc/m/W7ibgBW2AQAJ
Contribution guidelines
Incase you plan to raise a pull request to fix this issue, please make sure you refer our Contributing section for detailed set of steps.

@krmahadevan thanks for bringing it into GitHub.
Do You have any implementation ideas on how to approach this task?

@krmahadevan thanks for bringing it into GitHub.
Do You have any implementation ideas on how to approach this task?

@baflQA
An working on the PR for this. Should be done in a few hours.
The implementation would be similar to how we use retry analyser for test methods so that one can have different retry implementations for different data providers.

You are amazing @krmahadevan ! Can't wait for the next release.
Thank You for all Your work.


Help with CSS

Could you please tell me what is the CSS property to set to have a nice looking selected day (see image).
Thanks
-- nick

app-datepicker {
    --app-datepicker-selected-date: {
    color: yellow;
  };
}

Actually I don't not need a yellow color :) The computed height is not right : the 2 lines overlaps ("dim. 5" and "juin").

@nocquidant What browser you're on seeing this problem?

On Chrome and FF. Your demo looks good so it is probably one of my style rules...

@nocquidant I thought so. I don't see any issue only current styling. You can try line-height for a little adjustment.
app-datepicker {
  --app-datepicker-selected-date: {
    line-height: 32px;
  };
}

OK it is much better. Thanks
Le mar. 5 juil. 2016 à 13:46, Rong Sen Ng<EMAIL_ADDRESS>a
écrit :

@nocquidant https://github.com/nocquidant I thought so. I don't see any
issue only current styling. You can try line-height for a little
adjustment.
app-datepicker {
--app-datepicker-selected-date: {
line-height: 32px;
};
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/motss/app-datepicker/issues/33#issuecomment-230456683,
or mute the thread
https://github.com/notifications/unsubscribe/AANP3mKHnrxCW9qHBG5L5xxyqi8qoKAcks5qSkQmgaJpZM4JFBLI
.


Fix GitLab CI + small improvements

Minors changes:

test-unit_lpf now requires a high_core tagged runner in order to avoid timeout. Fix in this commit.
Some tests were skipped during the coverage, it was due to the missing CMake DATASET_DIR variable during the build. Fix in this commit.
Compilation of sparseblas.cpp was failing when the reference backend only was enabled. Fix in this commit.
Fix sporadic bug of Coverage with OpenMP. See this gcovr issue. Fix in this commit

Review OK, CIs OK. Will merge

Concept release notes:
This MR fixes the following issues encountered by the internal CI:

the LPF tests could fail on gitlab runners that are not large enough;
some coverage tests were skipped due to the missing CMake DATASET_DIR
compilation of the SparseBLAS was always attempted no matter which backends were enabled
fix sporadic bug of Coverage with OpenMP.

(holding off merge since I got a question on the CI tag)

Review OK, GitHub CI OK, waiting internal CI OK

Internal CI OK, will merge

Last minute detected doc not yet updated with sufficient conditions to reproduce a full successful CI run, now done in latest commit. Will not trigger internal CI OK before merging, since only the doc was changed in this latest commit.


Help about Intersecting searchContextByPaths

I have two folders, docs/myproduct and docs/myproduct/faq.
I want the first index to include the second folder but the second index not to include the first folder. So users can search the faq folder only, while still can search the entire docs.
When I have the following settings,  the 'docs/myproduct/faq' index does include only the docs in docs/myproduct/faq. But the 'docs/myproduct' index does not include the docs in docs/myproduct/faq. Can index a include docs in a/b while a/b is itself a separate index? Thanks!
searchContextByPaths: [ 'docs/myproduct/faq', 'docs/myproduct']

According to the code, only the first matched path in searchContextByPaths will be used.
postBuildFactory.ts#L56
I did a PoC to allow a doc to be added to multiple indexes. Is it OK to support this feature? If so, I'll try to make a PR.


mql4 Expert initialized successfully and Publish_MarketData is True but in terminal: expert lab, it doesn't send bid/ask data!

help wanted

[@integracore2 ]


Exporting the project?

Hello. When I compile the project using C::B (in the debug mode), I get an .exe file on the "Debug" folder in the project but when I try to open that .exe it says that "Couldn't exec because libgcc_s_dw2-1.dll is missing".
So how can I make it to export my project and be able to open it in another computer?
Thanks.

This is a compiler (GCC), not a raylib issue. GCC groups some helper functions into libgcc, e.g. 64-bit division if the host CPU ISA doesn't natively support it.
Add -static-libgcc to the linker flags dialog in Code::Blocks to instruct GCC to include the library with the exe.

Hey @a3f! Thank you very much for the answer! By the way, could you take a look to Travis CI? It seems there is some issue with glfw headers... About examples compilation issue of LoadFontEx(), I'm taking a look.
Closing this issue.

It seems there is some issue with glfw headers...

Ah, I missed that. I've commented on #558, which I suspect to be the culprit.


Add PostAsync to the UserInfoClient

Add PostAsync to the UserInfoClient to send a UserInfo request using an HTTP POST (useful for interacting with IDPs that only support POSTing to their userinfo endpoint)

Thanks!


performance enhance for pstree

do not grap all system table for each app view

https://github.com/laoshanxi/app-mesh/commit/473ac3abdd196d797765f14d03f0c5b3854d04c7


Use UTC DateTimes and Intervals whenever making decisions involving segments.

This should make the time partitioning stuff work even if the user's timezone
is something other than UTC, or if the Timekeeper or Timestamper return
non-UTC times.

+1


Refine custom-application-tab extensibility

Next in priority to https://github.com/vkottler/runtimepy/issues/255 / completed with https://github.com/vkottler/runtimepy/issues/254.
"Bring your own custom UI panel / application" needs to be a first-class configurable thing. This may technically be the case? In any case we should develop using a mechanism like this to ensure it exists and is reasonable to use (do another/final refinement pass on this interface).

Markdown stuff + landing_page app is a good example of how this can be done successfully


Search should retain even after closing popup

Is your feature request related to a problem? Please describe.
The search disappears if we close the popup.
Describe the solution you'd like
The search should be accessible for that session until changed by user.
Additional context
I would like to work on this.

@AmanR28 We tried this during the early development stage. The one problem that occurred was the increased start-up time of the extension. But, since the code has been improved significantly, it might work now.
The obvious solution is to store the search query in the localStorage to persist it across sessions.
Also, not all users might want to have this feature, therefore we can add a tab in the Options page with the title "Other Settings". There we can add a setting to toggle off this feature if the user wants.
I will make a separate issue for this. Just make sure that your implementation takes into account this aspect also.


1.1.0 tags and 1.2.0 tags and commits missing

Hello, I noticed that the latest version is 1.2.0 which was released a few hours ago, but when I look in this repo I do not see tags nor commits for it nor a tag for 1.1.0. Would it be possible to push these changes to the repo? Thanks!

would be nice to have version 2.0.0 as well including the changelog

Agree, especially since 2.0.0 is listed on npm, which it shouldn't since 2.0.0 has no release tag thus cannot be installed


fix: pubsub auth check

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
same change with https://github.com/risingwavelabs/risingwave/pull/13918
and fix format issue

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Can you add Co-authored-by or commit directly to the original author's branch (gh pr checkout 13918)?

let me try cherry pick


Fix typo in user_guide.md

Fix typp 'message' in user_guide.md

It would be better to submit a relevant issue first @liuzc9

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

Project coverage is 42.90%. Comparing base (144b22b) to head (229b08e).

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #8244      +/-   ##
=============================================
- Coverage      42.92%   42.90%   -0.03%
+ Complexity     10383    10381       -2
=============================================
  Files           1271     1271
  Lines          88785    88785
  Branches       11408    11408
=============================================
- Hits           38112    38091      -21
- Misses         45973    45988      +15
- Partials        4700     4706       +6

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

I submitted a new issue with #8245


Change method identifier "writeToStream" to "closeStream".

The method closes a stream, thus the method name "closeStream" should be better than "writetoStream".

All these PRs need a bug in fop jira with replication steps of issue


US975260: Remove HPE references in code

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

CI Build Link:
https://sou-jenkins2.swinfra.net/job/JobService/job/JobService~job-service-client~975260~CI