"Response errors; Validity(InsufficientFeeAmount { expected: 652174, provided: 0 })" })

gm guys, i trying to send some money to my contract address, but the call fails with error  "Response errors; Validity(InsufficientFeeAmount { expected: 652174, provided: 0 })" }), can you help me how to fix that
    let amount = usdc.parse_units(3000_f64) as u64;
    usdc.mint(admin.address().into(), amount).await.unwrap();

    admin
        .force_transfer_to_contract(
            &spark.insurance_fund.contract_id(),
            amount,
            usdc.asset_id,
            TxPolicies::default()
                .with_gas_price(2)
                .with_max_fee(1000000000),
        )
        .await
        .unwrap();

    `fuels = { version = "0.55", features = ["fuel-core-lib"] }`

        Default host: aarch64-apple-darwin
fuelup home: /Users/alexey/.fuelup

installed toolchains
--------------------
beta-5-aarch64-apple-darwin
latest-aarch64-apple-darwin (default)
nightly-2024-01-24-aarch64-apple-darwin
nightly-2024-03-30-aarch64-apple-darwin

active toolchain
----------------
latest-aarch64-apple-darwin (default)
  forc : 0.49.3
    - forc-client
      - forc-deploy : 0.49.3
      - forc-run : 0.49.3
    - forc-crypto : 0.49.3
    - forc-doc : 0.49.3
    - forc-explore : 0.28.1
    - forc-fmt : 0.49.3
    - forc-lsp : 0.49.3
    - forc-tx : 0.49.3
    - forc-wallet : 0.4.3
  fuel-core : 0.22.1
  fuel-core-keygen : 0.22.1

fuels versions
--------------
forc : 0.54.0
forc-wallet : 0.54.0

This should have been solved here. It was released as 0.55.1 so it should be picked up by your cargo.
Make sure you run cargo update just in case your Cargo.lock still points to 0.55.0.
@hal3e fyi.

This should have been solved here. It was released as 0.55.1 so it should be picked up by your cargo.
Make sure you run cargo update just in case your Cargo.lock still points to 0.55.0.
@hal3e fyi.

Unfortunately I do know that it should have been fixed in 0.55.1 and I've checked and re-checked multiple times that we were using the correct version in our matcher. As you can see in the screenshot, we really do. And the issue is still there. Our production env matcher has just encountered this too. The only workaround we have for now is to create a new wallet for this and restart the matcher app.


Seem to be getting double-sized tilemaps

What I am using now is...
local generator = astray.Astray:new( resolutionTilesX/2-1, resolutionTilesY/2-1, 30, 20, 90, astray.RoomGenerator:new(10,1,5,1,5) )
local dungeon = generator:Generate()
local tmp_tilemap = generator:CellToTiles(dungeon, symbols )

Correct. I write a note to the sample code.
Also the size is always uneven. I might can fix this, but i suspect it's a lot of work.


Add hexagonal lattice CouplingMap

Summary
Adds qiskit.transpiler.CouplingMap.from_hexagonal_lattice.
Details and comments
Add qiskit.transpiler.CouplingMap.from_hexagonal_lattice, which generates a hexagonal lattice as a coupling map.

Oh, that's weird - I made the same suggestion inline, but it never showed up in the review.  I must have forgotten to submit the comment...

This code looks correct to me, though do you have a particular use in mind for it? There's a slight mistake in the release notes that are causing the documentation build to fail, but that's nothing major.

I think that it would be a good addition to the coupling maps, but I don't have any specific use in mind for it. :)


Fix AnnotationTest Class Test Case

Fix test cases for modules in querydsl-codegen-utils
@velo
The AnnotationTest test case was not performed properly, so it was changed to run normally.
For test cases Via StringWriter Syntax to check whether a specific string matches an expected string. In particular, w.toString().trim() checks for a match to a certain format in an annotated string.
However, we confirmed that it was not performing normally as shown in the picture and modified the test case.
as-is

to-be

@velo
It seemed to work fine before, but it seems to have failed the test after the Jakarta update.
I downloaded this project yesterday and tested it out first. I think I need to analyze the Maven aspect of this project.

@xeounxzxu found it
https://github.com/OpenFeign/querydsl/pull/487/files#diff-38aa8118c349d8e6bcd8d6fab8d279983ed323ca3ad16ca52835039a531fbf41L66


Improvise  the framework

Thank you for the great work. I understand that you don't want to release the training pipeline for specific detection models but at the least Please provide a simple example of a training pipeline to show how we could train our models with mediapipe.

@Zumbalamambo MediaPipe is mainly an inference framework that supports currently TensorFlow & TFlite. You can create any MediaPipe graph to run any TF or TFlite model. Hence, MediaPipe is independent and not used for model training only inference


KeyPress not working

Hello! I need your help.
Now I have successfully connected to my GoogleTV using PinCode but the KeyPresses(KEYCODE_VOLUME_UP, NETFLIX,...) are not working. I don't know where to check and what else needs to be set up in my xcode project?

Hi, according to the logs, you are sending data of one-byte length, which is incorrect. There is a specific structure - KeyPress, which contains two fields: Key and Direction. You need to initiate this structure and send its binary representation; all the necessary structures have already been implemented. You can refer to the usage example in the demo project.

I tested your "demo project" and it was perfect.
And I have followed as RemoteTVManager class in "demo" unfortunately my send KeyPress commands are not working like that of "demo project". I think my project is missing something.


Detailed parameters of cameras when generating renders results from Objaverse

Hi, thanks for providing the 1.5T rendered views!
As I'm using this dataset for my research, it occurs that only the transformation matrices are provided, while other camera parameters are missing, such as fov, camera_angle_x, rotation, etc (those from BlenderDataset). Since we are using the objects from Objaverse, where GTs are provided, it would be better to skip the calibration step and use the information from the 3D asset. Therefore, I'm wondering if you could provide more data about how each object is rendered.
Thanks!

Hi @ZexinHe , fov is the same thing as camera_angle_x in NeRF's blender dataset, which is 49.1 degree or 0.857 rad as stated in the appendix section of the paper. I might be wrong but I think rotation is not part of the camera intrinsics for NeRF. It describes the rotation angle between two consecutive viewpoints.

Thanks for your timely feedback! I've found the details now. And you are right about rotation, the information is contained in the sequence of transformation matrices.

Hi @ZexinHe ,  So，I want to make sure whether right using the following equations to obtain the intrinsic K for objaverse dataset ?
H, W = imgs[0].shape[:2]
camera_angle_x = float(meta['camera_angle_x'])
f = 1 / np.tan(camera_angle_x / 2) * (W / 2)

Best,
Ying

Hi @yjcaimeow ,
I think you are correct. The above code obtains the focus, which leads to the intrinsic K matrix.
K=[[f,0,W/2], [0,f,H/2], [0,0,1]]
Bests,
Zexin


emergency fix compile error for swift 4.2

Thanks @manuqiao, wanted to do it myself and I saw that you already have done it 😉 Didn't have time to test it, but removing duplicated operators seems like a good fix.
So what happened in Swift 4.2 is a change in Implicitely Unwrapped Optional (IUO). An overview on the changes in Swift 4.1 (where this issue was a warning) and in 4.2 (where this issue is now an error) is in this blog post.
And @JacobKingDev, please don't judge just by the code, sometimes there are different reason for a change and this seems like a good one (at least in my POV).

@sunshinejr My point was more a case of simply removing code will cause issues for users of the library that utilised such code, not to mention potentially causing compiler errors where such methods are used within the library. Also, I noticed builds are failing but on closer inspection I think this is because CI is configured to use an outdated Swift version. If this fix is good, can someone merge it? I'm champing at the bit to use dark mode! 😛

@JacobKingDev sure, it just seemed a bit rude, if you'd write it the way you explained it now, I wouldn't say anything. But no worries, it's all good 👍
About the removals, I think it seems okayish, because these are just redundant (after the changes the method will accept optional either way, no need for unforced unwrapped optional as an argument). I'm not sure for 100%, but it seems reasonable.

Maybe a better/safer solution would be something like
#if swift(>=4.1)
#else
/// Implicitly Unwrapped Optional Object of Raw Representable type
public func <- <T: RawRepresentable>(left: inout T!, right: Map) {
	left <- (right, EnumTransform())
}
#endif

(Sadly swift version check doesn't work fot less than checks)

@talesp Unfortunately this won't work as this is also changed in 3.* version that Xcode 10 ships with. Thus, it won't compile as well.
We would need the compiler directive, but that was just merged yesterday so we would need to wait for next beta probably.

New to me as well. I've heard the news about 4.2 but not 3.*. But it kinda makes sense as they wanted to remove the IUO implementation from the codebase, so.
Tried it yesterday and today just to be sure and it won't compile when you use Swift 3 for the target - still throws an error.

yeah, but breaks compatibility to an already released version :(
So, maybe a xcode-10 branch for now, breaking compatibility with Xcode 9 (that does not have the compiler directive)?

Thanks for the contribution but I already merged another swift 4.2 PR.


A lot of space under listview when try to insert element on the last position

two problems:

a lot of space under list view
very fast scrolling to the bottom (almost immediately)

Code:
<SortableListView
style={{ marginBottom: 44 }}
data={this.state.items}
order={this.state.order}
disableAnimatedScrolling
bounces={false} // tryed to set it to true
onRowMoved={e => replacePositions(e.from, e.to)}
renderRow={row => }
renderSeparator={() => <View style={{ height: 8 }} />}
renderFooter={this.renderAddPicture} />
video with a problem: https://drive.google.com/file/d/1OsJvX-mlvUMVeS_g8X1c2kGL0KiBrR7l/view?usp=sharing

I've found how to solve a problem with space under listview. But it's definitely very bad way (just a hack):
need to change here
(line 244)
const MAX_HEIGHT = Math.max(
          0,
          this.scrollContainerHeight - this.listLayout.height + itemHeight
        )

to this.scrollContainerHeight - this.listLayout.height + itemHeight + 300
and here
(line 303) ```
handleContentSizeChange = (width, height) => {
this.scrollContainerHeight = height
}

to `this.scrollContainerHeight = height - 300`

Thanks for reporting, I'm aware of that too


render_condition_map sometimes has errors

Hi, thank you for your work, when I use render_condition_map for rendering, sometimes the code stops midway because some file error from os.rename(os.path.join(render_path, "depth", f"{0:04d}.png"), depth_path) (depth, normal xxx all possible). I checked and found sometimes 0000.png does not exist, but somehow the if os.path.isfile(os.path.join(render_path, "depth", f"{0:04d}.png")): checks yes. I wonder if you have encountered the problem? I guessed it is about multi-processing but not sure

I encountered the same problem. What was the reason and how could we solve it?


Develop Jupyter Notebook to provide an example preprocessing/resampling of NetCDFs to GeoTiff format

Example:
cd sit_fuse/preprocess
python3 colocate_and_resample.py -y ../config/preprocess/colocate_and_resample/fuse_gk2a.yaml

Update gitbook as you can/see fit - we can work on parameters that are not well documented or easy to understand collectively

Complete


[Fix] Navbar search styling

Task title
Fix navbar search box styling
Task description
There is a weird behavior when the search box of the navbar is being focused, see the image below
Subtasks
Put the subtasks here if any (optional)
Screenshots

This issue has an active pull request and solved


Develop

Update  role style and structure

Nice work. You should check out Molecule: https://github.com/metacloud/molecule/ It'll likely save you a lot of boilerplate when wiring up role tests via vagrant and testinfra.

Any updates on merge here, @achaussier?

Hi @conorsch ,
Sorry for the delay, I had many work on other projects.
I'll review all comments and changes this night.

Some unexpected work occurred, but this night I'll take time to do this :/

@conorsch I've took a look at the Molecule project some months ago, but it have change quickly, I'll take time to re-test it in the next days, and why not replace my current testing method.
Thanks


Ecosystem field unclear for things that are not npm/rust/...

Hi,
I just found out the ecosystem thingy is mandatory to put in affected versions. Is there a reason/need behind that? Because for example, WordPress plugins are in the database, but you can't use the form for them as WordPress is not in the predefined ecosystem fields. The same goes for GHSA-gqhp-5j32-xwmm which is a nodejs issue which doesn't fall into an ecosystem that is predefined. There are probably also plenty of other examples.
I am mainly wondering about the reason why it is mandatory, as I think having typed version ranges alone are also very helpful in case anyone wants to use the database for a tool. However, typed versions seem impossible without the ecosystem at this time.

As an example, this is in my opinion valuable to have but is not possible to get submitted:

Addition: It seems this comes from https://ossf.github.io/osv-schema/#affectedpackage-field however my question still stands as I think packages like nodejs should still be able to have typed versions.

I have been wondering this as well.  For instance the Rust Advisory Database has reports for vulnerabilities in the rust toolchain itself separately from rust crates.  It feels like this should be a separate ECOSYSTEM to crates.io.  I suspect it makes sense to raise an issue about this up on the OSV Schema repo.
cc: @oliverchang

@MTRNord and @westonsteimel thanks so much for chiming in on these. This is indeed an issue we want to eventually address.
The reason that the ecosystem is required is that we have a highly-trained Curation team who is reviewing each PR and we want to make sure they're empowered to make decisions by working on the ecosystems we're familiar with. So at this point, we're only taking contributions on advisories that are part of our 8 formally supported ecosystems. I can see a possible future where we also take community contributions on non-supported ecosystems, but we have a lot of thinking to do on how to structure that.
I'd love to learn more about your use case.
Would either or both of you be interested in chatting with me for 30 minutes in the next month via Zoom? If so, please follow the link below to schedule a time that works best for us both. In recognition of your time, we’ll send you a $60 gift card/cash card/credit for the GitHub Swag store.
https://calendly.com/security-advisories-ux-calls/25min?back=1&month=2021-10

@MTRNord and @westonsteimel thanks so much for chiming in on these. This is indeed an issue we want to eventually address.
The reason that the ecosystem is required is that we have a highly-trained Curation team who is reviewing each PR and we want to make sure they're empowered to make decisions by working on the ecosystems we're familiar with. So at this point, we're only taking contributions on advisories that are part of our 8 formally supported ecosystems. I can see a possible future where we also take community contributions on non-supported ecosystems, but we have a lot of thinking to do on how to structure that.
I'd love to learn more about your use case.
Would either or both of you be interested in chatting with me for 30 minutes in the next month via Zoom? If so, please follow the link below to schedule a time that works best for us both. In recognition of your time, we’ll send you a $60 gift card/cash card/credit for the GitHub Swag store.
https://calendly.com/security-advisories-ux-calls/25min?back=1&month=2021-10

Hi :)
I don't yet have an actual use case here. This mainly came up in the first few minutes of scrolling through the list as I saw the NodeJS and a few WordPress plugin issues. As the NodeJS one had the versions in the text, it was easy to fill the form to give the thing a try :)
The thing with having it "typed"/machine-readable is simply that past taught me that there tend to be plenty of OSS people that tend to make awesome stuffs like statistics out of this kind of data. And having this data flawed just feels kind of sad as there would be plenty of data missing due to this restriction as there seem to be quite a lot of things that don't fall into the existing ecosystems. So this for me is more a thing that would help for future use cases than having an actual use case yet. :)

@MTRNord thanks for the response, this is great feedback and we'll keep an eye on this issue as more feedback comes in.

For Rust, @ev

I have been wondering this as well. For instance the Rust Advisory Database has reports for vulnerabilities in the rust toolchain itself separately from rust crates. It feels like this should be a separate ECOSYSTEM to crates.io. I suspect it makes sense to raise an issue about this up on the OSV Schema repo.
cc: @oliverchang

I believe the Rust advisory database only reports crates vulnerabilities in OSV format. @Shnatsel to comment. Should we also export the toolchain vulnerabilities (and use a separate ecosystem?)"

I believe the Rust advisory database only reports crates vulnerabilities in OSV format.

Yes, that is correct.

Should we also export the toolchain vulnerabilities (and use a separate ecosystem?)

I believe a separate ecosystem is indeed necessary, because Cargo exists both as a crate with its own version (currently 0.60.0) and is also bundled the Rust toolchain with a specific version (currently 1.59.0), and it's the toolchain version that we track in the toolchain advisories. Attempting to match it on the crate version will silently give you incorrect results.
That said, that particular part of the database is currently a preview, for two reasons:

We don't yet have first-party tooling that takes advantage of toolchain vulnerability data, so we have no real-world experience with it.
Right now our format assumes that toolchain vulnerabilities have a CVE IDs assigned; this assumption has been violated already, so a change to our internal format will probably be required. (We did try to become a CNA, but ended up stepping on the toes of Rust Foundation and the process has stalled).

(To be fair, I have not published any Rust crates or NPM packages so if it's enforced at publication time I just haven't seen that)


Could not load dynamic library 'libcusolver.so.10'; dlerror: libcusolver.so.10

Getting this error although the file is there and LD_LIBRARY_PATH is correctly set

This is a bug with CUDA 11.2 and tensorflow
I installed CUDA 11.0 and problem fixed

This is a bug with CUDA 11.2 and tensorflow
I installed CUDA 11.0 and problem fixed

Great ! Let me know if you need any helps to get started with the repository.

Great ! Let me know if you need any helps to get started with the repository.


Stat weight sim for demo lock not calculating mastery

mastery being put to a weight off 0 when simming stat weights for demo lock.

This is working as intended. The reason this happens is that the demonology and affliction mastery total percentage is rounded down, and statweights are calculated by simming +-40 of that stat. So there are many points where adding or removing 40 mastery does literally nothing for your DPS.
We may change how this works in the future if Blizzard confirms they won't fix this mechanic: https://github.com/JamminL/cata-classic-bugs/issues/1256


Improve nuget.org's Markdown support

Since .NET 5.0, you can add a README to your NuGet package. Here are a few Markdown features we should add to nuget.org to make this experience amazing:

[ ] https://github.com/NuGet/NuGetGallery/issues/8503
[ ] https://github.com/NuGet/NuGetGallery/issues/8505
[ ] https://github.com/NuGet/NuGetGallery/issues/8632
[ ] https://github.com/NuGet/NuGetGallery/issues/8644
[ ] https://github.com/NuGet/NuGetGallery/issues/8726
[ ] https://github.com/NuGet/NuGetGallery/issues/8802
[ ] https://github.com/NuGet/NuGetGallery/issues/8833
[ ] https://github.com/NuGet/NuGetGallery/issues/8731

From Loic's README analysis for .NET repos with over 100 stars:

Issue
% impacted

Syntax highlighting
80%

Additional image domains
71%

HTML support
29%

Table rendering
27%

Mailto links
9%

Code snippet copy button

Section links

Blockquote rendering

@loic-sharma could we find out what percentage are impact by the last 3 items?

@chgill-MSFT  Agree,  I think for the HTML we might want to break it down to more specific like header, image, css and so on, how about gather more information/analysis to make it more in details?
Also we could just fix table render, blockquotes since it's small engineering cost with better customer experience.


feat: add Treeview heading (via RSP V3)

Description
Supports TreeView heading aka section.
Comments from designer: https://adobedesign.slack.com/archives/GEFETJ9BR/p1583183591233400?thread_ts=1583183591.233400
RSP@V3
https://reactspectrum.blob.core.windows.net/reactspectrum/c9500ee4a9c5d87b188ddf12c93920da1f72305a/storybook/index.html?path=/story/tree--sections

Section 1

     <svg class="spectrum-Icon spectrum-UIIcon-ChevronRightMedium spectrum-TreeView-indicator" focusable="false" aria-hidden="true">
       <use xlink:href="#spectrum-css-icon-ChevronRightMedium" />
     </svg>
     Group 1

       Layer 2

       Layer 3

How and where has this been tested?
Chrome/Firefox/Safari on MacOS.
IE11/Edge on Windows 10
Screenshots
Before

After

To-do list

[x] If my change impacts other components, I have tested to make sure they don't break.
[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[x] This pull request is ready to merge.

https://spectrum-visual-regression.ci.corp.adobe.com/job/spectrum-css-vr-test-asset/233/artifact/spectrum-css/backstop_data/html_report/index.html

@lazd The 2 props have been removed. If that's the last issue, I'm going to merge it and we can file a new issue for the additional treeview work.


Add TOPS certificates

Follow NASA TOPS resources for open and reproducible science lectures
Add an assignment to require NASA TOPS certificates

Added to lecture 1 and assignments 1 and 3.


⚠ Bofrost.at has degraded performance

In 591ea05, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1397 ms

Resolved: Bofrost.at performance has improved in de3b68b after 6 minutes.


outfox: init at 0.5.0-pre042

Description of changes

Project OutFox is a rhythm game engine forked from StepMania that is performing major refactors of the original code, with a goal of supporting many platforms, input devices, and charts from other rhythm games.
The project is currently closed-source, with plans to release the source under GPL3 at some date in the future when development has stabilized. For now, I've marked the license as unfreeRedistributable.
Things done

Built and tested on x86_64-linux.
Successfully built for i686-linux, armv7l-linux, aarch64-linux with pkgsCross, but was not able to test on those platforms.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Updated to place unpacked files in opt/OutFox/, with a symlink in bin/ pointing to the binary at opt/OutFox/OutFox. Before this force-push all the files and folders distributed alongside the binary were dumped into bin/, which would pollute /run/current-system/sw/bin/~/.nix-profile/bin when installed.
Is this an acceptable location for these files to reside within the derivation, or is a different folder (share?) more idiomatic?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3188

LGTM, just two things to fix:

Many assets in share/OutFox/Appearance are marked executable, please chmod -x them
there is no desktop entry file, meaning OutFox will not show up in the start menu. Please add one

@pbsds I believe I have fixed those last two issues.
The executable bit is now set on only the OutFox executable itself.
There is now a .desktop file which I have tested that successfully launches the program from the start menu (unfortunately without an icon, as one is not included in the source).

Please make sure there is no nix store path in the desktop file. DEs like gnome tend to copy these files to a separate folder to remember them as startup applications, meaning the store path will become outdated.
Your chmod -x is also too aggressive, as several shared object files (.so, kinda like .dll on windows) are marked as non-executable. Please limit the chmod to the previously mentioned path.

Checked it on two systems — appears to be broken after selecting a game mode. Perhaps some resources could not be loaded.

Also, its license is Apache-2.0 https://github.com/TeamRizu/OutFox

Checked it on two systems — appears to be broken after selecting a game mode. Perhaps some resources could not be loaded.

I deleted my ~/.project-outfox folder and I'm now seeing the same thing. I was seeing some strange behavior prior to that which I attributed to that folder being generated by the 0.4.x version, but perhaps it's the 0.5.x version that's having trouble. The most suspicious sign is that the file ~/.project-outfox/Save/Preferences.ini file is not being created.
I'll look into the issue and see if I can figure out a fix.

I'll look into the issue and see if I can figure out a fix.

Looks like this is a bug in OutFox Alpha 5. The game is trying to create settings files inside the program directory, which fails on NixOS, or even on other distros if you unpack the game as root. The latest Alpha 4 version does not have this issue.
I'll try to work with the developers to get this fixed for the next release, but in the meantime here's a workaround to get the game running:

Copy the game out of the Nix store
cp -r $(dirname $(dirname $(realpath $(which OutFox)))) ~/OutFox

Mark this copy as writable
chmod -R +w ~/OutFox

Launch the copied game
~/OutFox/share/OutFox/OutFox

Select a gamemode, then exit the game

Copy over the settings files into your user OutFox folder
cp -r  ~/OutFox/share/OutFox/Save ~/.project-outfox/

Cleanup the copied game folder, it is no longer needed
rm -r ~/OutFox

There still seem to be some issues with persisting settings, but the game works mostly fine otherwise. Scores are saved with no issues.


frontend: improve bitcoin or crypto in translations

In some languages Bitcoin or crypto can have special ending depending
on the context, so translating crypto does not work in all cases.
This is the first step changing keys using bitcoin or crypto
context so that terms like Bitcoin or crypto can be translated
differently.
Added generic buy and receive keys with context, without context
this keys still use a coinCode placeholder. i.e.

Buy Bitcoin
Buy crypto
Buy LTC / Buy {{coinCode}}

Reason to not offer different keys for each token/coin is that it
would required a different key for each coin/token.

/github.com/BitBoxSwiss/bitbox-wallet-app/assets/546900/5688ff64-d9b5-4940-9b4b-7d1a33ff3e90">


Does not work on test_suite

Thanks @fmeum, really enjoying this package so far. I am trying to use it on test_suite as I want to run the "same" tests under different configs.
Given...
_tsc_test_suite, _tsc_test_suite_internal = with_cfg(native.test_suite).set(Label("//tools/ts-project:flag-use-tsc"), True)).build()

and...
_tsc_test_suite(
      name = "aot_test",
      tests = [
        tests_name
     ]
)

This happens:
bazel test //libs/twi-generic:aot_test
ERROR: libs/twi-generic/BUILD:5:13: in _tsc_test_suite_internal rule //libs/twi-generic:aot_test_with_cfg: non-test target '//libs/twi-generic:aot_test_with_cfg' depends on testonly target '//libs/twi-generic:aot_test_/aot_test' and doesn't have testonly attribute set
ERROR: libs/twi-generic/BUILD:5:13: Analysis of target '//libs/twi-generic:aot_test_with_cfg' failed
ERROR: Analysis of target '//libs/twi-generic:aot_test' failed; build aborted: Analysis failed
INFO: Elapsed time: 2.551s, Critical Path: 0.00s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: No test targets were found, yet testing was requested

While I can fix that particular error, I found that a wrapped test_suite no longer runs any tests. This isn't too surprising as test_suite is a deeply magical built-in rule and Bazel doesn't really support targets that depend on tests.
Could you instead try to transition the individual tests?

This may be doable after https://github.com/bazelbuild/bazel/issues/14993.

This can be worked around by transitioning the individual tests instead and wrapping them into a test_suite via a helper macro, see https://github.com/fmeum/with_cfg.bzl/tree/main/examples/java_test_suite_multiple_jdks for an example.

I will close this as "not planned" since I don't think there is anything that can be done without Bazel changes. The test I linked documents the best workaround I'm aware of.


GLPK_MI interface errors

I was going to try to give a minimal test case to reproduce a traceback from CVXPY 1.0.25, GLPK 4.65, and CVXOPT 1.2.3 that ends as follows:
  ...
  File ".../venv/lib/python3.7/site-packages/cvxpy/problems/problem.py", line 289, in solve
    return solve_func(self, *args, **kwargs)
  File ".../venv/lib/python3.7/site-packages/cvxpy/problems/problem.py", line 571, in _solve
    self, data, warm_start, verbose, kwargs)
  File ".../venv/lib/python3.7/site-packages/cvxpy/reductions/solvers/solving_chain.py", line 194, in solve_via_data
    solver_opts, problem._solver_cache)
  File ".../venv/lib/python3.7/site-packages/cvxpy/reductions/solvers/conic_solvers/glpk_mi_conif.py", line 88, in solve_via_data
    status = self.STATUS_MAP[results_dict['status']]
KeyError: 'infeasible problem'

But then I ran into the following, possibly more severe problem.
>>> import cvxpy
>>> x = cvxpy.Variable(1, boolean=True)
>>> p = cvxpy.Problem(cvxpy.Maximize(x), [x == 0, x == 1])
>>> p.solve(solver=cvxpy.GLPK_MI)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../venv/lib/python3.7/site-packages/cvxpy/problems/problem.py", line 289, in solve
    return solve_func(self, *args, **kwargs)
  File ".../venv/lib/python3.7/site-packages/cvxpy/problems/problem.py", line 571, in _solve
    self, data, warm_start, verbose, kwargs)
  File ".../venv/lib/python3.7/site-packages/cvxpy/reductions/solvers/solving_chain.py", line 194, in solve_via_data
    solver_opts, problem._solver_cache)
  File ".../venv/lib/python3.7/site-packages/cvxpy/reductions/solvers/conic_solvers/glpk_mi_conif.py", line 75, in solve_via_data
    set(int(i) for i in data[s.BOOL_IDX]))
TypeError: G must be a 'd' matrix

I'm not sure if there were dedicated unittests for GLPK in the past. There will be from now on, per PR #910. GLPK_MI is currently passing all tests in that PR. The error you see here is because there are no inequality constraints (and the CVXOPT interface to GLPK assumes > 0 inequality constraints). I've also fixed that error in #910.

Does #910 close this?

It fixes your particular test case, and it also has GLPK_MI passing three standard MILP test cases. We can close this issue once #910 is merged, if you'd like. I'm also open to keeping this issue standing until a little longer after the PR (in case you'd like to try additional test-cases).

I won’t be able to do any further testing for several months. Go ahead and close the ticket once merged. If I run into problems again, I’ll either comment on this ticket or open a new one, as appropriate. Thanks for taking care of this!

Sounds good! Thanks for the reply.

Closed by #910


New Exposure System

Rebalance Exposure Protection
Remove Exposure Resistance
Add new "frostbite" status effects that take effect if not wearing armor below certain temps
Add exposure ceiling in certain temps / climates (exposure can't increase above X in Riverwood, so no risk of dying of exposure in those areas, etc)
Refactor Frost Resistance into system
Refactor Wetness into system
Allow Frost Damage and Fire Damage to play a role

Let's get this party started.

Only thing remaining is to add Frostbite effects and hook up a way to deliver them.

Done.


surelog not found

Hi,
I am running the test asic_demo from a Mac (MacOS Big Sur 11.6).
Input:
sc -target asic_demo -remote
I see the following output describing an error with "Executable surelog not found"
Version: 0.10.1

| INFO    | /Users/brucehecht/Documents/zero-asic/siliconcompiler/siliconcompiler/targets/../data/heartbeat.v inferred as rtl/verilog
| INFO    | Command line argument entered: ['option', 'target'] Value: asic_demo
| INFO    | Command line argument entered: ['option', 'remote'] Value: true
| WARNING | job0  | --         | -  | Could not find remote server configuration: defaulting to https://server.siliconcompiler.com
| ERROR   | job0  | import     | 0  | Executable surelog not found
| ERROR   | job0  | import     | 0  | Halting step 'import' index '0' due to errors.

We use Surelog to lint and pickle files before building them, in both local and remote workflows.
If you install SiliconCompiler from PyPi (pip install siliconcompiler), Surelog should be packaged with the wheel file that gets installed. But if you install it from the repository (pip install -e ., python setup.py install, etc.), you will need to make sure that Surelog is built and installed on your system.
Sorry for the confusion.


Setting ArrayLike.length or any index results in TS2450. (TSv2)

TypeScript Version:  2.0.3
Code
var a:ArrayLike<number> = [];
a.length = 10; // TS2450: Left-hand side of assignment expression cannot be a constant or a read-only property.

I'm assuming there are other cases than ArrayLike that this happens?

Only actual arrays have the property that setting their length changes the underlying length in a meaningful way. Example:
function fn() {
  arguments.length = 1;
  console.log(arguments[1]);
}
fn(0, 1, 2); // prints 1, not undefined

What?  You can define what an actual array is yes.  But something that is "ArrayLike" could be anything.
Why are we enforcing "ArrayLike" to be read only?  Make NO SENSE.

So you're telling me because of some weird edge case put into the compiler, I have to write my own ArrayLike?

Ok wow.  I don't know what to say here.
So now I write an identical interface to ArrayLike and the compiler treats it differently.

And you can't extend ArrayLike without incurring the same restriction.

@RyanCavanaugh I saw another issue related to length.  Has by chance this behavior changed?
Please respond to my previous comments above.


NUI editor: additional settings and finishing touches

Contains
Various improvements to the NUI screen/skin editors; see rzats/gsoc-nui-editor#10, rzats/gsoc-nui-editor#13 and rzats/gsoc-nui-editor#14.

Added a 'Preview screen locale' setting - this will change the language of the editor's preview widget (but not the NUI editor or the game itself). Useful for reviewing things such as long UI strings that may break interface rendering!
Added a "Close" button to the editors (as an alternative to ESC & F10/F11) and a "Delete" option to tree view node context menues (as an alternative to DELETE).

How to test
Press F10/F11 in the main menu to run the NUI screen/skin editors, then verify that all of the above work as intended :smile:
Outstanding before merging

[ ] Implement the features from rzats/gsoc-nui-editor#13 (tree view to widget binding).
[x] Review the source code's Javadoc, modify and fill stubs where appropriate.

[x] Also fix Checkstyle warnings where appropriate.

[x] Autosave the asset changes to a temporary JSON file, then add an option to apply the changes to the actual asset file.
[x] Add a popup to warn the user that changes will be lost on asset change.
[x] Automatically edit newly added attributes.

[x] Automatically edit the IDs of newly added widgets.

[x] A "Debug Tools" menu with options to show different dev tools (console, UI editor, skin editor, BT editor).
[ ] When the editor's strings are somewhat finalized, internationalize them all!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

I know there has been a good amount of chat about this one on Slack and there are still two unchecked boxes up top, but is this getting close enough where I can help any with merge testing or anything? :-)
I noticed the issue the top unchecked box leads to has already been closed as well. Feels like this one is close!

@Cervator: the top item is still a WIP. It's mostly a visual extra though, so at this point testing would be really appreciated :smiley:

Played around with it some :-) Probably not as thoroughly as @flo would. Works well for me!
Curious question: should something like alignments where there is a finite set of options be editable via drop-down or other selection of just the valid values? Anything that can be backed by an enum so to say. Maybe still with free-form available.
Should there be a "duplicate" option for some things? Like if you're adding a bunch of similar fields.
I realize those are more future suggestions to probably put in a list somewhere rather than actual feedback on this PR ... :D
I did manage to crash the game at one point by attempting to add a widget of type engine:Port :
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Cannot construct 'engine:Port' - no accessible default constructor

Hooray Jenkins reported success with all tests good!

With the option to save (module assets) with a single click I think we got an very important extra feature added.
You checked "Autosave" above as implemented feature, but it does not seem to be implemented. Although we warn now the user about unsaved changes when he switches the asset which is good.


Fix cuda on cifar

Fix #1224 by adding check_device_limit If the allocated size is bigger than the limit, it creates additional cuda kernels with offset being manually added to the corresponding dimension index using .replace() . Currently only did global[2] which corresponds to grid.z. I want to see if I can reduce the line for those code before adding the check for all grid.x,y,z and block.x,y,z.
Fix #1233 with added .contiguous() in LR to be able to run CIFAR again.
Here are some performance comparison
CUDA=1 BS=256 STEPS=50 python3 examples/hlb_cifar10.py

49  478.41 ms run,    5.42 ms python,  472.98 ms CL,    1.83 loss, 0.000010 LR, 3.82 GB used,   1220.46 GFLOPS
eval 3542/10000 35.42%,    1.86 val_loss STEP=50

GPU=1 BS=256 STEPS=50 python3 examples/hlb_cifar10.py

49  480.70 ms run,    8.91 ms python,  471.79 ms CL,    1.84 loss, 0.000010 LR, 3.82 GB used,   1214.64 GFLOPS
eval 3479/10000 34.79%,    1.86 val_loss STEP=50

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/ops.py                            9               5
tinygrad/runtime/ops_cuda.py              24               3
------------------------------------------------------------
total                                     33               8
------------------------------------------------------------
lines added in the tinygrad folder: 25

In CI both Linters and cuda test has this AttributeError: type object 'Context' has no attribute 'get_device'. Did it confuse cuda.Context which I imported from the library with what's under if getenv("CUDACPU", 0) == 1:?

Is the emulated cuda test using CUDACPU=1?

Also added .contiguous() in LR to fix #1233. What's left is to fix the cuda simulators

Can you do just the #1233 fix first?

After some discussion in the discord, the global dim limit issue would also happen on WebGPU. However, could this potentially be a bug that linearizer did not push everything to the first global dim?
In my example #1235 it was pushed to the third dim.

Was going to reduce some lines in ops_cuda.py but it seems like #1256 is going to directly affect this, since the error was also caused by MemOp. Initially, I was looking into whether its possible to swap gidx0 and gidx2 since the latter corresponds to the first dim which has the biggest size.
UOps.LOOP           :                           []                               ([<gidx0[0-65535]>, <gidx1[0-1]>, <gidx2[0-1]>], 'global')
UOps.LOOP           :                           []                               ([<lidx3[0-31]>], 'local')
UOps.LOAD           : <val1_0>                  []                               MemOp(i=1, idx=<(((gidx0[0-65535]%16)*2)+((gidx0[0-65535]//16)*2048)+(gidx1[0-1]*32)+(lidx3[0-31]*64)+gidx2[0-1])>, valid=<1>)
UOps.LOAD           : <val2_0>                  []                               MemOp(i=2, idx=<(((gidx0[0-65535]//16)*512)+(gidx0[0-65535]%16)+(lidx3[0-31]*16))>, valid=<1>)
UOps.ALU            : <alu0>                    [<val1_0>, <val2_0>]             BinaryOps.CMPEQ
UOps.STORE          :                           [<alu0>]                         MemOp(i=0, idx=<((((gidx0[0-65535]*4)+(gidx1[0-1]*2)+gidx2[0-1])%64)+((gidx0[0-65535]//16)*2048)+(lidx3[0-31]*64))>, valid=<1>)
UOps.ENDLOOP        :                           []                               ([<gidx0[0-65535]>, <gidx1[0-1]>, <gidx2[0-1]>, <lidx3[0-31]>], 'global+local')

Currently it fails when I set BS=1024 but works completely fine with BS=512 or less. Currently the limit check is only applied when the ASTRunner was initialized but not during the kernel execution. There's probably something else that I am missing.
GPU=1 CUDA=1 BS=1024 STEPS=50 python examples/hlb_cifar10.py

0 3597.16 ms run, 3596.93 ms python,    0.23 ms CL,    2.94 loss, 0.003657 LR, 0.10 GB used,    649.21 GFLOPS
  1 1123.78 ms run, 1123.58 ms python,    0.20 ms CL,    2.30 loss, 0.007314 LR, 15.06 GB used,   2078.08 GFLOPS
  2  610.88 ms run,   19.06 ms python,  591.83 ms CL, 154045.27 loss, 0.009944 LR, 15.06 GB used,   3822.83 GFLOPS
  3  611.60 ms run,   14.44 ms python,  597.15 ms CL,<PHONE_NUMBER>6.00 loss, 0.009732 LR, 15.06 GB used,   3818.35 GFLOPS
  4  611.05 ms run,   13.89 ms python,  597.16 ms CL,<PHONE_NUMBER>6.00 loss, 0.009521 LR, 15.06 GB used,   3821.80 GFLOPS
  5  611.39 ms run,   14.95 ms python,  596.45 ms CL,<PHONE_NUMBER>92.00 loss, 0.009310 LR, 15.06 GB used,   3819.63 GFLOPS

Here is the working case for BS=512
CUDA=1 BS=512 STEPS=1000 python examples/hlb_cifar10.py

999  875.59 ms run,  537.66 ms python,  337.93 ms CL,    0.83 loss, 0.000010 LR, 8.85 GB used,   1333.60 GFLOPS
eval 8991/10000 89.91%,    0.41 val_loss STEP=1000

Feel like I am all over the place with this fix but end up decided to redo it from linearizer and cstyle which I believe would be much cleaner.

#1299 is the new fix


HDFS-17546. Follow-up backport from branch3.3

Description of PR
Some minor revisions between the trunk and branch-3.3 changes for HDFS-17546.
So we are backporting the minor changes in the unit test file for javac/linting fixes.
How was this patch tested?
Ran checkstyles + mavent tests
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 51s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
8m  1s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 24s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.txt
hadoop-hdfs in trunk failed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.

-1 :x:
compile
0m 26s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_412-8u412-ga-1~20.04.1-b08.txt
hadoop-hdfs in trunk failed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08.

-0 :warning:
checkstyle
0m 22s
/buildtool-branch-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
The patch fails to run checkstyle in hadoop-hdfs

-1 :x:
mvnsite
0m 16s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in trunk failed.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.txt
hadoop-hdfs in trunk failed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_412-8u412-ga-1~20.04.1-b08.txt
hadoop-hdfs in trunk failed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08.

-1 :x:
spotbugs
0m 26s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in trunk failed.

+1 :green_heart:
shadedclient
2m 20s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 24s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
compile
0m 24s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.txt
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.

-1 :x:
javac
0m 24s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.txt
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.

-1 :x:
compile
0m 32s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_412-8u412-ga-1~20.04.1-b08.txt
hadoop-hdfs in the patch failed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08.

-1 :x:
javac
0m 32s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_412-8u412-ga-1~20.04.1-b08.txt
hadoop-hdfs in the patch failed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
The patch fails to run checkstyle in hadoop-hdfs

-1 :x:
mvnsite
0m 24s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
javadoc
0m 24s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.txt
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2.

-1 :x:
javadoc
0m 24s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_412-8u412-ga-1~20.04.1-b08.txt
hadoop-hdfs in the patch failed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08.

-1 :x:
spotbugs
1m 40s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
shadedclient
5m 56s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
31m 55s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+0 :ok:
asflicense
0m 26s

ASF License check generated no output?

55m 11s

Reason
Tests

Failed junit tests
hadoop.metrics2.sink.TestRollingFileSystemSinkWithHdfs

hadoop.metrics2.sink.TestRollingFileSystemSinkWithSecureHdfs

hadoop.hdfs.server.datanode.TestReadOnlySharedStorage

hadoop.net.TestNetworkTopology

hadoop.hdfs.server.datanode.TestBlockHasMultipleReplicasOnSameDN

hadoop.tools.TestJMXGet

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6908

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7c4d7596914e 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 763342ff1b9bc9f69684e5e59fd04929d315399b

Default Java
Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/1/testReport/

Max. process+thread count
494 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
docker
0m  8s

Docker failed to build run-specific yetus/hadoop:tp-26579}.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6908

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/2/console

versions
git=2.34.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
19m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
55m 18s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
1m 17s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
1m 13s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
1m 12s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
3m 23s

trunk passed

+1 :green_heart:
shadedclient
41m 40s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 14s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
1m 19s

the patch passed

+1 :green_heart:
compile
1m 10s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
1m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  3s

the patch passed

+1 :green_heart:
mvnsite
1m 17s

the patch passed

+1 :green_heart:
javadoc
0m 58s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
1m 42s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
3m 25s

the patch passed

+1 :green_heart:
shadedclient
41m 23s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
263m 44s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

443m 56s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6908

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux cafacf685775 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0b7aaf935f56b28e47601cf1fa22712730b67135

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/3/testReport/

Max. process+thread count
2587 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6908/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Looks good to me! Thank you for the work @NyteKnight


feat: Add the Terraform module

Description
This PR adds the Terraform module for Self Signed Certificates Operator charm.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

@ghislainbourgeois I do not have rights to merge it. If it is fine, could you merge it please ?


Velocity and Position command interfaces don't work when Effort command interface exist

When I add the effort command interface to the test_cart_velocity.xacro.urdf example, the velocity example stops working. I modified the example to reproduce the bug https://github.com/BarisYazici/gz_ros2_control/blob/humble/ign_ros2_control_demos/urdf/test_cart_velocity.xacro.urdf.

This might be a limit of ignition::gazebo::v6::EntityComponentManager.
But why would someone need velocity and effort at the same time? What should the physics engine do then?

They were not claimed by the controller at the same time. Effort interface was just available in the robot itself that triggered the bug.

@BarisYazici I've been stuck on this for a while, I want my simulated robot joints to have both an effort and velocity command interface since that reflects the real robot. Honestly I couldn't solve it so I made different URDFs and I load either one or the other according to how I want to control the joints.

They were not claimed by the controller at the same time. Effort interface was just available in the robot itself that triggered the bug.

Ah I see. This shouldn't be a problem, maybe there is a bug in the logic of the perform_command_mode_switch. Maybe someone here could have a look into this?

@BarisYazici I've been stuck on this for a while, I want my simulated robot joints to have both an effort and velocity command interface since that reflects the real robot. Honestly I couldn't solve it so I made different URDFs and I load either one or the other according to how I want to control the joints.

Our workaround is also basically the same. Could take a look to perform_command_mode_switch when I find time @christophfroehlich


Default Peds

After logging in, making your character, saving them, logging out, and logging back in, at the char select screen, they're just the basic template users. the console is giving an error:
Script:qb-multicharacter SCRIPT ERROR: @qb-multicharacter/client/main/lua:137: No such export setPedAppearance in resource fivem-appearance
Any ideas? I followed the documentation to the letter for the qb-multicharacter, everything is working except this.

what exactly did you do for this because i have the most updated Fivem-Apperance and ive changed the export and all i have is default characters or an invisible character

Make sure you're running the included SQL, and that you're downloading the release version, not the main branch version. As soon as I got the release version, everything was golden.

awesome thanks ill give it a try

just tried i downloaded the full release of fiveM appearance and i update the SQL i still have an invisible character on character selection the empty spots spawn a ped but the already created character does not show no errors in the console is that similar to your issue?

Log into the character, goto a clothing store, save the outfit you're wearing, and see if you get any errors anywhere.


Province codes

since no recoding need to occur for province, most years' code already had the necessary code existing for province.


Apply circuit breaker pattern on external dependencies

e.g. If fb profile images do not load, then trigger circuit breaker and display nothing (or some random images of colorful eggs)

Regarding user images: this is quite difficult to implement, unless we cache or proxy user images, which would require a periodic job to fetch a "fresh" image from facebook. Facebook not loading is also quite unlikely.
Applying circuit pattern is certainly a principle to keep in mind, but as this is not currently an actionable issue, I'm closing it in favor of more specific ones.
See also https://github.com/sic2/isamuni/issues/133


gimx: init at 8.0

This PR adds Gimx project that allows to emulate various input devices for gaming systems.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111416 run on x86_64-linux 1

2 packages built:

gimx
gimx-afterglow

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111416 run on x86_64-linux 1

2 packages built:

gimx
gimx-afterglow


[BLUEPRINT] - Open Telemetry

Add blueprint which demonstrates how to leverage OTEL with external aws observability services.

see https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples/observability


Create Go Related Workflows in Github Actions

Noting we need to commit go.sum file for the lint to pass.
Reasoning https://github.com/golang/go/wiki/Modules#releasing-modules-all-versions


Proposal: Add third source input type, "inline text"

I propose adding a third source input type, "inline text". It just lets you put text into a text box, that would then be read. This text would also be included as part of the JSON or URL.
This would make it easy to create a proof that builds on an existing database and other proofs not in the database, by letting you temporarily add those proofs to what you're working on.

I will implement this. Until then the below workarounds are available.
For local development - create a local text file and append it to the context via "plus" button. If you update content of the file then remove the source with the file via the "trash can" button (in the application header) and add it again. This is required because once content of a source is loaded it is never reloaded again.
For sharing via URL - save the file on GitHub (or any other location which then lets you download this file via HTTP GET without authentication). Add a URL of the file to your settings in the app. Provide an alias for that URL. Alias is not a required attribute but URLs without alias are not appearing in the source selector in the app header. Apply changes to settings and compose the proof you want to share using the file URL as one of the context sources. Then export your proof to URL and share with others. Others will be able to see your proof (if they don't have problems with loading your file). Your URL will not appear in the app settings for other people unless they check "don't ask for this URL" checkbox in the confirmation dialog. But even then your URL will not appear in the source selector for other people because your URL will not have an alias in their settings (aliases are not sharable). So overall this action will not introduce more and more sources in the app header for others. Here is an example of a GitHub URL I added to my settings to speed up loading of set.mm from the web - https://raw.githubusercontent.com/expln/metamath-lamp/master/src/metamath/test/resources/set-no-proofs._mm


chore: fix bug， to avoid crashing the system when passing 0

Brief Description of the PR
Checklist

Demo:
Documentation:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.andy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.andy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Refactor] rename the materialized column API to Generated Column

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 75 / 124 (60.48%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/AlterTableClauseVisitor.java
7
21
33.33%
[286, 312, 323, 401, 405, 429, 440, 458, 459, 462, 491, 523, 549, 560]

:large_blue_circle:
com/starrocks/sql/ast/AddColumnsClause.java
1
3
33.33%
[32, 36]

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
4
11
36.36%
[180, 188, 331, 334, 416, 420, 446]

:large_blue_circle:
com/starrocks/alter/SchemaChangeJobV2.java
7
14
50.00%
[528, 529, 550, 551, 592, 594, 605]

:large_blue_circle:
com/starrocks/load/Load.java
7
13
53.85%
[185, 242, 323, 324, 449, 675]

:large_blue_circle:
com/starrocks/sql/analyzer/UpdateAnalyzer.java
3
5
60.00%
[136, 151]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
5
8
62.50%
[960, 3648, 3651]

:large_blue_circle:
com/starrocks/sql/InsertPlanner.java
4
6
66.67%
[425, 478]

:large_blue_circle:
com/starrocks/sql/ast/ColumnDef.java
5
7
71.43%
[213, 496]

:large_blue_circle:
com/starrocks/catalog/Column.java
11
13
84.62%
[474, 476]

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
12
14
85.71%
[430, 446]

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/UpdatePlanner.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/task/AlterReplicaTask.java
2
2
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 75 / 124 (60.48%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/AlterTableClauseVisitor.java
7
21
33.33%
[286, 312, 323, 401, 405, 429, 440, 458, 459, 462, 491, 523, 549, 560]

:large_blue_circle:
com/starrocks/sql/ast/AddColumnsClause.java
1
3
33.33%
[32, 36]

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
4
11
36.36%
[180, 188, 331, 334, 416, 420, 446]

:large_blue_circle:
com/starrocks/alter/SchemaChangeJobV2.java
7
14
50.00%
[528, 529, 550, 551, 592, 594, 605]

:large_blue_circle:
com/starrocks/load/Load.java
7
13
53.85%
[185, 242, 323, 324, 449, 675]

:large_blue_circle:
com/starrocks/sql/analyzer/UpdateAnalyzer.java
3
5
60.00%
[136, 151]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
5
8
62.50%
[960, 3648, 3651]

:large_blue_circle:
com/starrocks/sql/InsertPlanner.java
4
6
66.67%
[425, 478]

:large_blue_circle:
com/starrocks/sql/ast/ColumnDef.java
5
7
71.43%
[213, 496]

:large_blue_circle:
com/starrocks/catalog/Column.java
11
13
84.62%
[474, 476]

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
12
14
85.71%
[430, 446]

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/UpdatePlanner.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/task/AlterReplicaTask.java
2
2
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 75 / 124 (60.48%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/AlterTableClauseVisitor.java
7
21
33.33%
[286, 312, 323, 401, 405, 429, 440, 458, 459, 462, 491, 523, 549, 560]

:large_blue_circle:
com/starrocks/sql/ast/AddColumnsClause.java
1
3
33.33%
[32, 36]

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
4
11
36.36%
[180, 188, 331, 334, 416, 420, 446]

:large_blue_circle:
com/starrocks/alter/SchemaChangeJobV2.java
7
14
50.00%
[528, 529, 550, 551, 592, 594, 605]

:large_blue_circle:
com/starrocks/load/Load.java
7
13
53.85%
[185, 242, 323, 324, 449, 675]

:large_blue_circle:
com/starrocks/sql/analyzer/UpdateAnalyzer.java
3
5
60.00%
[136, 151]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
5
8
62.50%
[960, 3648, 3651]

:large_blue_circle:
com/starrocks/sql/InsertPlanner.java
4
6
66.67%
[425, 478]

:large_blue_circle:
com/starrocks/sql/ast/ColumnDef.java
5
7
71.43%
[213, 496]

:large_blue_circle:
com/starrocks/catalog/Column.java
11
13
84.62%
[474, 476]

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
12
14
85.71%
[430, 446]

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/UpdatePlanner.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/task/AlterReplicaTask.java
2
2
100.00%
[]

[FE Incremental Coverage Report]
:disappointed: fail : 80 / 152 (52.63%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/dump/DesensitizedSQLBuilder.java
0
2
00.00%
[547, 548]

:large_blue_circle:
com/starrocks/sql/analyzer/AlterTableClauseVisitor.java
10
38
26.32%
[286, 299, 312, 322, 323, 332, 345, 346, 363, 402, 405, 416, 429, 439, 440, 449, 459, 466, 467, 469, 492, 523, 536, 549, 559, 560, 569, 588]

:large_blue_circle:
com/starrocks/sql/ast/AddColumnsClause.java
1
3
33.33%
[32, 36]

:large_blue_circle:
com/starrocks/alter/SchemaChangeJobV2.java
6
18
33.33%
[518, 524, 550, 551, 552, 559, 592, 594, 605, 616, 617, 618]

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
4
11
36.36%
[180, 188, 331, 334, 416, 420, 446]

:large_blue_circle:
com/starrocks/sql/analyzer/UpdateAnalyzer.java
3
5
60.00%
[136, 151]

:large_blue_circle:
com/starrocks/load/Load.java
8
13
61.54%
[185, 242, 324, 449, 675]

:large_blue_circle:
com/starrocks/catalog/Column.java
12
19
63.16%
[458, 476, 479, 509, 619, 685, 706]

:large_blue_circle:
com/starrocks/sql/InsertPlanner.java
4
6
66.67%
[425, 478]

:large_blue_circle:
com/starrocks/sql/ast/ColumnDef.java
5
7
71.43%
[213, 496]

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
14
17
82.35%
[426, 432, 442]

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/UpdatePlanner.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/task/AlterReplicaTask.java
2
2
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 132 / 152 (86.84%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/dump/DesensitizedSQLBuilder.java
0
2
00.00%
[547, 548]

:large_blue_circle:
com/starrocks/load/Load.java
8
13
61.54%
[185, 242, 324, 449, 675]

:large_blue_circle:
com/starrocks/sql/analyzer/UpdateAnalyzer.java
4
5
80.00%
[136]

:large_blue_circle:
com/starrocks/sql/InsertPlanner.java
5
6
83.33%
[478]

:large_blue_circle:
com/starrocks/sql/analyzer/AlterTableClauseVisitor.java
32
38
84.21%
[286, 405, 429, 440, 449, 523]

:large_blue_circle:
com/starrocks/sql/ast/ColumnDef.java
6
7
85.71%
[496]

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
10
11
90.91%
[446]

:large_blue_circle:
com/starrocks/sql/analyzer/CreateTableAnalyzer.java
16
17
94.12%
[432]

:large_blue_circle:
com/starrocks/catalog/Column.java
18
19
94.74%
[458]

:large_blue_circle:
com/starrocks/alter/SchemaChangeJobV2.java
17
18
94.44%
[559]

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/UpdatePlanner.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/task/AlterReplicaTask.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/AddColumnsClause.java
3
3
100.00%
[]


Newest chain.go has incorrect PostageStampStartBlock on goerli

Context
Latest master, commit ee7bef8a
Summary
While adopting the new contract addresses into my monSI monitor, I noticed that the PostageStampStartBlock was not changed.
Expected behavior
Why search blocks before the contract was even deployed?
Actual behavior
A freshly DB Nuked node searches for stamps from far too far back in the past.
Steps to reproduce
Possible solution
Change PostageStampStartBlock to 7951994 matching the contract deployment block.

PS.  Or do stamps migrate when a new contract is deployed?   This is a very personal question to me as I really don't want to lose my large stamp when this new contract finally gets to mainnet.


Upmerge 17 10 2019

Upmerging from zephyr upstream
Do not merge.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: ioannisg:x: de-nordic:x: jimparisYou have signed the CLA already but the status is still pending? Let us recheck it.


DevOps Engineer (Contract)

Job title (DevOps Engineer)
Job level (Intermediate - Senior)
Company name (ACC)
Link to job description: https://accco.taleo.net/careersection/102/jobdetail.ftl?job=21107&tz=GMT%2B13%3A00&tzname=Pacific%2FAuckland
Contact info: A-Bao in Wechat group

closed


Add support for delegation of freezable state

This will allow Frozen models to compute their decisions relative
to the state of a foreign model.

New approach!

:tada: Thanks!


Compatibility with subscribers

Hello, is this compatible with "invite.created" or "user.password_reset" ? :)

Hello,
I've added support for the mentioned events. You can use the event data payload within the email templates for these events.


[MM-26721] show channels across teams in channel switcher modal

Summary
When the user types in the channel switcher, match results across all teams on the server.
If the user has more than 1 team:
The team name would be on the right
The mention badge would be beside the name of the Channel.
If the user has only 1 team:
we have decided to keep the existing layout i.e no changes in the channel switcher list view.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-26721
Related Pull Requests

Has server changes https://github.com/mattermost/mattermost-server/pull/18468

Screenshots

before
after

Release Note
* API: modification in existing API endpoints to meet the Requirements (added new params).
* UI: Behavioral changes in channel switcher if user part of more than 1 team UI will show up with team name.
* Redux: Modification in a couple of redux selectors and added few selectors for selecting all the channels

@agnivade adding you for visibility

/update-branch

@jgilliam17 - Just a quick note that this might need some extra testing which might not be possible via spinwicks. This needs testing with Elasticsearch and Bleve as well. ES is likely not available with spinwicks.
For the basic feature:

Verify that public and private channels from all teams are visible in the switcher, and is navigable.
Verify that channels (from all teams) of which the user is not a member of, is also searchable in the switcher.

For ES and Bleve, you would need to disable database search, and then run the indexing job, and enable search and autocomplete.
Please feel free to let me know if you have any questions. :)

/update-branch

Hey @AshishDhama just checking on this and what are next steps?

@esethna yeah will update this with changes suggested next week, then I guess it would be good to merge

@AshishDhama anything blocking this?

/update-branch

Error trying to update the PR.
Please do it manually.

Hey @AshishDhama, can you provide an update on where this PR is at?

Hey @AshishDhama, can you provide an update on where this PR is at?

@esethna I think we are ready to merge, have implemented all the changes suggested by @hmhealey except the ones which were increasing the scope of this ticket.

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/102943

@Willyfrog @AshishDhama great, can we rally reviews to get this PR merged? It's a massive quality of life enhancement for multi-team users

Ping @hmhealey @koox00 @jgilliam17 for reviews

/update-branch

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/103082

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/103176

Are there still changes outstanding on this? I don't see anything in the web app code about loading channel members for other teams, and we'd need that to show unreads for channels in teams that haven't been loaded yet.

@hmhealey I have updated the branch

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/104289

@koox00 friendly reminder to review :)

@hmhealey if you can please help with review asap as we are trying to merge before feature complete and growth spike

Triggering e2e testing with options:
<nil>

/update-branch

Thank you @AshishDhama
Seeing 2 small theming/alignment issues, otherwise looks and works good.
I will check the  E2E report when the run completes and post here if there are any PR related failures.

Bot tag font theme seems off, only for multi-team user.

Mention badge may need to drop down for a few pixels to be vertically aligned. See above image.

@AshishDhama here is the E2E report
Looks good overall, only two failed tests appear related to the PR changes
MM-T1241
MM-T1225

Thanks @AshishDhama
The mention bag is vertically centered, but the theme is still off
This is what we currently have on master

But on the PR test server theme of the bot tag and mention badge is like below

/update-branch

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/107264

@esethna @matthewbirtch
If nickname or full name is not set - username displays.
If nickname and/or full name is set - username is missing. Is this as designed ?

Currently, we show username on daily, regardless

If nickname and/or full name is set - username is missing. Is this as designed ?

I think username should still be there — assuming we have the room. I think we may need to truncate though if the combination of display name, username and team name cause things to collide.
@AshishDhama I was just playing with keeping the username, and I think there should still be enough space to keep it. Whoever did the original design work must have intentionally removed it but I'm thinking we should keep it if we think there is still space

@AshishDhama one small suggestion
We truncate to soon, there is more room on the modal since for DMs we do not display the team name

@AshishDhama one small suggestion We truncate to soon, there is more room on the modal since for DMs we do not display the team name

@jgilliam17 if we add a guest tag or bot tag, custom status, and mention tag then it will almost make up for the space.

Ah, I was editing my above post after I thought about other items that may display.

Thanks for a reminder @AshishDhama Custom status added

There is still a little bit of room. I downgraded longname user to guest. This is what it looks like. @matthewbirtch thoughts?

I'm fine with the truncation as is. By the time you add all the possible additions, there's not much to play with.

@michelengelen could please review it again.

@AshishDhama looks like reviews are complete and this can be merged?

@AshishDhama Can you help clarify the release note "API: modification in existing API endpoints to meet the Requirements (added new params)." - which API endpoints were modified and why?

@amyblais we have changed following end point ${baseUrl}/api/v4/channels/search?system_console=false we have added additional param to fetch search results across teams.
and have added

${baseUrl}/api/v4/users/me/channels (for fetching all the channel across teams)
${baseUrl}/api/v4/users/${userId/channel_members (for fetching all the channel_members across teams)
@agnivade please correct me If I am wrong.

Yep, those are the ones. The changes are documented in more details here: https://github.com/mattermost/mattermost-api-reference/commit/0c6827642dc286e25c2c9e4c9edcb1b53280b434.

Documented via https://github.com/mattermost/docs/pull/5391


[IOTDB-6048] Refactor RatisClient related code

Use AutoClosable to refactor RatisClient related usages.

Bravo work!

Use AutoClosable to refactor RatisClient related usages.

It is obvious that you can maintain all the modules👀


fix(core): fallback to {asset}.html before index.html, closes #2328

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

It should fall back to {asset}/index.html to follow the standard

It should fall back to {asset}/index.html to follow the standard

yeah good point, should I add another fallback? or do you have something better in mind?

It should fall back to {asset}/index.html to follow the standard

yeah good point, should I add another fallback? or do you have something better in mind?

No, it should replace the {asset}.html as we shouldn't support that. It diverges from the rest of the web, and can break projects unexpectedly that try to output both a Tauri application + a web with the same codebase


Refactor the architecture of the IVisitor hierarchy

Adding a new plugin is much more complex as it should be. Especially the huge and hardly understandable IVisitor hierarchy is responsible for that. The architecture should be simplified drastically. This needs experiments to avoid new pitfalls :-)
The final architecture should be:

1 interface in Robot declaring all visit*-methods for those blocks, that are common to ALL plugins (if, ..., ...) WITHOUT DEFAULTS
1 interface for each plugin declaring the visit*-methods for blocks added in the plugin (sensor, actor, ...) WITHOUT DEFAULTS
all visit* methods in robot and all plugins should be final if possible. Clear Javadoc for each exception rom this rule

goals for the far future:

ValidatorAndCollector and sub classes return BlocklyType instead of Void. The return type is the type
of the blocks result, e.g. "if" -> Void; "max" -> Number; "and" -> Boolean
This will be used later.
in the future we want to switch to a new blockly version. Adding especially sensors/actors should be very easy. All
info about the blockly block, validation, code generation should be ideally at one place: the AST class.
(goal: the refactoring is a prerequisite for that)
In many places the visit-Method in the ValidatorAndCollector-structure (e.g. "visitASTClass(ASTClass x)"
can be removed and done generically. Idea:

the class annotation @NepoOp resp. @NepoPhrase have a flag "validateAndCollect=true or similiar.
in this case the the annotation processor doesn't call "visitASTClass(ASTClass x)",

it executes a "requiredComponentVisited(...)" call for all values
and checks for an optional public method "addHardware(usedHardwareBuilder)". If the method exists,
it is called to update the hardware need of the program.

For simple cases this can be extended LATER to code generation

steps (to be revised when done):

start with all sub-interfaces of IHardwareVisitor

and remove them step by step (as long they don't have defaults, or???)

then remove overrides by the regex:
@Override\NL\ *public ==> public

the result is:

tests should run
forgetting to add visit(...)-method is not visible anymore - only in tests

replace all public visit(...)-methods by visit(...) (really? we can keep the visit* names to avoid overload problems)

problems with tests

but reuse... should run

the relevant changes mentioned above have been done. The "goals for the far future" will probably never implemented.

solved in commits related to "textly"


fix: double slash in url

Describe the changes you have made in this PR
I got an error trying to connect my Umbrel. The error toast currently shows me a URL that contains a double slash: "https://umbrel.local:8080//v1/getinfo". Should be -> https://umbrel.local:8080/v1/getinfo
Might be the case with more connectors?

Other connectors affected by this:

ConnectMyNode
ConnectStart9


Extend db_log event logging

What is the issue, e.g. map voting, you would like to solve?
The db_log plugin is currently not logging every available events from log-parser. When I create database request for player statistics, I often miss data to order players based on playtime or selected role. It would be great, if the db-log plugin would also log player-connected, player-disconnected, player-possess and player-un-possess events. Some server owners might not want to spam their databases with this data, so it should be configurable within the setting.
How would you like us to solve this issue?
As a quick fix, these events could be logged as raw data in a separate table for each event. My preferred solution would be combining player-connected and player-disconnected in a "session" table like:
||  sessionID  || steamID  ||  connected  ||  disconnected  ||  playtime  ||
The "playtime" value would be calculated time between the connect and the disconnect. This would allow dscord bots like SquadStats to also display the time a player played on the server.
For player-possess and player-un-possess it would be already great to just log all the data somewhere to check for which use-cases this values could be useful.
Additional Info
It would be awesome, if the existing tables DBLog_deaths, DBLog_Wounds, DBLog_Revives could include the MatchID. This makes it easier to identify when a specific event happened.

I have already done a similar thing with the plugin 9 days ago, but I wanted to test it properly.
That is why I've added the PLAYER_DISCONNECTED event in my last commit.
Here is what it looks like:

I will commit it soon.

@milutinke that looks really awesome and is exactly what I am looking for.
It will make the insights from the database a lot easier to compare.
O hope that it will find its way to the master branch quickly.

@milutinke that looks really awesome and is exactly what I am looking for.
It will make the insights from the database a lot easier to compare.
I hope that it will find its way to the master branch quickly.

Well, Thomas seems to be busy, so you might wait a little longer.
In the meantime, you can try out my fork and modify it for your needs.


Post to remote service returns "TypeError: Cannot read properties of undefined (reading 'length')"

I have this function in a NodeJS application using @sap/cds version 7.3.0:
static async getEquipmentSet() {
        try {
            const api = await cds.connect.to('sap-odata-service');
            const result = await api.get(`EquipmentSet`);
            return result;
        } catch (error) {
            console.log(error);
        }
}

This previous GET function returned data from the remote service 'sap-odata-service' configured in cdsrc.json file.
But the following POST method returns an error:
    static async postHourmeter(equipmentData, measurementPointId) {
        try {
            const payload = this.getHourmeterPayload(equipmentData, measurementPointId);
            const api = await cds.connect.to('sap-odata-service');
            const result = await api.post(`MeasureDocumentSet`, payload);
            return result;
        } catch (error) {
            console.log(`The error is:`);
            console.log(error);
        }
    }

Errors:

Does anyone know how to fix it?

HI @MiqueiasMaia ,
This questions seems more appropriate to be asked in the community. Or if it's a bug, pls file an incident. More information on how to get support is doucmented here: https://cap.cloud.sap/docs/resources/
In this repository, we only want to solve documentation-related questions and contributions. We do not intend to answer general questions or bug reports. Thanks for your understanding.
All the best René


space-around-operator errors on background shorthand

What version of Sass Lint are you using?
1.13.1
Please include any relevant parts of your configuration
Base configuration, nothing changed
What did you do? Please include the actual source code causing the issue.
background: url(./assets/asset-name.png) center center/contain no-repeat;
What did you expect to happen?
Nothing.
What actually happened? Please include any error messages given to you by Sass Lint.
It triggered a warning for the space-around-operator rule.
warning  Space expected around operator space-around-operator
If you're using a IDE plugin have you tried the CLI too?
Straight up CLI.

I check the docs on MDN and they recommend it without spaces:
https://developer.mozilla.org/en-US/docs/Web/CSS/background


add a more concise YAML file format for 'Apps' thats more like opencompose?

so the opencompose YAML format is nice and concise
https://github.com/redhat-developer/opencompose/blob/master/docs/file-reference.md#opencompose-file-reference-documentation
I wonder if we should support a more concise YAML file format that tries to combine deployment + service to make things a little less complex and nested?
I worry about leaky abstractions though; so wanna make sure its a minor facade really and delegates to the underlying kubernetes model as much as possible:
I've a little spike to experiment with this. for example this app.yml:
---
name: "cheese"
labels:
  app: "cheese"
annotations:
  com.acme: "foo"
replicas: 1
containers:
- image: "foo/bar:123"
  env:
  - name: "MY_ENV"
    value: "CHEESE"
service:
  ports:
  - port: 80
    targetPort: 8080

Generated these resources:
---
apiVersion: "v1"
kind: "List"
items:
- apiVersion: "v1"
  kind: "Service"
  metadata:
    annotations:
      com.acme: "foo"
    finalizers: []
    labels:
      app: "cheese"
    name: "cheese"
    ownerReferences: []
  spec:
    deprecatedPublicIPs: []
    externalIPs: []
    loadBalancerSourceRanges: []
    ports:
    - port: 80
      targetPort: 8080
    selector: {}
- apiVersion: "extensions/v1beta1"
  kind: "Deployment"
  metadata:
    annotations:
      com.acme: "foo"
    finalizers: []
    labels:
      app: "cheese"
    name: "cheese"
    ownerReferences: []
  spec:
    paused: false
    replicas: 1
    template:
      metadata:
        annotations:
          com.acme: "foo"
        finalizers: []
        labels:
          app: "cheese"
        name: "cheese"
        ownerReferences: []
      spec:
        containers:
        - args: []
          command: []
          env:
          - name: "MY_ENV"
            value: "CHEESE"
          image: "foo/bar:123"
          ports: []
          volumeMounts: []
        imagePullSecrets: []
        nodeSelector: {}
        volumes: []

if anyone's interested in noodling here's the code:
https://github.com/jstrachan/fabric8-maven-plugin/tree/app-enricher
so this is the new DTO, App.java which is-a PodSpec with details from the Metadata and DeploymentSpec and an optional ServiceSpec:
https://github.com/jstrachan/fabric8-maven-plugin/blob/app-enricher/enricher/app/src/main/java/io/fabric8/maven/enricher/app/model/App.java
Then here's the current AppGenerator that trivially converts it into the Deployment, Service etc:
https://github.com/jstrachan/fabric8-maven-plugin/blob/app-enricher/enricher/app/src/main/java/io/fabric8/maven/enricher/app/AppGenerator.java#L37

I raised an opencompose issue to ponder this experimental App resource and to see if we could unify this with opencompose in some way down the road: https://github.com/redhat-developer/opencompose/issues/138


Not able to use multi-sig wallet for logging into dApps

My algo connect is not supporting multisig wallets. We have tried logging into multiple NFT market places like AB2 gallery and Algo Gems. We have tried yieldly too. Only individual wallets are showing up.

We have had this issue too. There are also issues with the multisig asset manager not allowing ASA creation or asset config transactions


Fix PHPStan issues

Q
A

Type
task

BC Break
no

Fixed issues

Summary
It's nice to see some ignored errors go :)

Thanks @franmomu!


Theme is not applying, though Theme is attached in configuration

I have attached theme correctly inside theme directory and configuration file
[view] => Array
                (
                    [theme] => Array
                        (
                            [pathMap] => Array
                                (
                                    [@app/views] => @app/themes/advanced/views/
                                    [@app/modules] => @app/themes/advanced/modules
                                    [@app/widgets] => @app/themes/advanced/widgets
                                )

                            [baseUrl] => /themes/advanced
                        )

                )

It is taking default main.php layout from views directory. but it should take main.php layout from theme directory. Please suggest solution what could be the problem for this.
It is giving fatal error
Class 'frontend\assets\AppAsset' not found
in /var/www/cbmp/sitefrontend/views/layouts/main.php at line 12.

Actual asset file located inside
/var/www/cbmp/sitefrontend/themes/advanced/views/layouts/main.php

make sure either frontend\assets\AppAsset exists or that the yii namespace is loaded in your bootstrap.


HTTP Error Response code handling

While you're in there, coding up great error handling with wonderful logging (please 😆 ) I did see Anthropic returning a 529! Not entirely 'standard' but there you go. Thx

Plenty of 429's from Groq. Perhaps introduce a n millisecond delay between calls.


allow to provide custom PatternCompiler

Summary
fix https://github.com/cucumber/cucumber/issues/494
Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

[x] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Looks good! :D

Feel free to merge and make a release. @aslakhellesoy is the release process working?

LGTM! I'll fix the indentation (4 space indent) and make a release. The release process is currently described in CONTRIBUTING_NEW.
The process is still a bit new, so I prefer to do it myself to iron out any kinks.

Awesome!

The release process still needs some work. I'll start by making a pom archetype because I'm tired of cpoy-pasting XML. Give me a few days.


Homepage

Service picture need to be polished.
Perhaps add a cursor to the Subscribe button.
Pictures for items needs to be added.
login page needs to be made.
Perhaps make a forget password page.

All things added/fixed.


HMP2: initial commit

Codecov Report

Merging #2385 into HMP2 will increase coverage by 0.11%.
The diff coverage is 94.83%.

@@            Coverage Diff             @@
##             HMP2    #2385      +/-   ##
==========================================
+ Coverage   93.76%   93.88%   +0.11%
==========================================
  Files         163      161       -2
  Lines       18667    19206     +539
==========================================
+ Hits        17504    18032     +528
- Misses       1163     1174      +11

Impacted Files
Coverage Δ

...dlers/study_handlers/tests/test_sample_template.py
97.5% <ø> (ø)
:arrow_up:

...pet/handlers/study_handlers/tests/test_artifact.py
97.19% <ø> (ø)
:arrow_up:

qiita_pet/handlers/study_handlers/__init__.py
100% <ø> (ø)
:arrow_up:

qiita_pet/handlers/api_proxy/__init__.py
100% <ø> (ø)
:arrow_up:

qiita_pet/handlers/study_handlers/prep_template.py
54% <ø> (-3.41%)
:arrow_down:

...lers/artifact_handlers/tests/test_base_handlers.py
95.29% <ø> (-0.06%)
:arrow_down:

qiita_pet/handlers/api_proxy/tests/test_user.py
78.26% <ø> (ø)
:arrow_up:

qiita_db/metadata_template/constants.py
100% <ø> (ø)
:arrow_up:

...andlers/study_handlers/tests/test_prep_template.py
94.11% <ø> (-3.51%)
:arrow_down:

...iita_pet/handlers/api_proxy/tests/test_artifact.py
98.22% <ø> (ø)
:arrow_up:

... and 44 more

Continue to review full report at Codecov.

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