EBADF (Bad file descriptor)

Download video mp4 file throw Bad file description on my Realme C1 and Xperia Z1 with release build, work well with debug build.
Android 9
The video url is: https://v.pinimg.com/videos/mc/720p/29/8b/e4/298be43b0ab83f7608767ae5bc767071.mp4
The file uri to save (permission has been granted): content://com.android.providers.downloads.documents/tree/raw%3A%2Fstorage%2Femulated%2F0%2FDownload%2FMusic/document/raw%3A%2Fstorage%2Femulated%2F0%2FDownload%2FMusic%2F298be43b0ab83f7608767ae5bc767071.mp4
Here is the exception log:
libcore.io.Linux.writeBytes (Linux.java)
libcore.io.Linux.write (Linux.java:288)
libcore.io.BlockGuardOs.write (BlockGuardOs.java:348)
libcore.io.IoBridge.write (IoBridge.java:526)
java.io.FileOutputStream.write (FileOutputStream.java:381)
com.tonyodev.fetch2core.StorageResolverHelper$getOutputResourceWrapper$1.write (StorageResolverHelper.java:37)
com.tonyodev.fetch2.downloader.SequentialFileDownloaderImpl.writeToOutput (SequentialFileDownloaderImpl.java:232)
com.tonyodev.fetch2.downloader.SequentialFileDownloaderImpl.run (SequentialFileDownloaderImpl.java:124)
com.tonyodev.fetch2.downloader.DownloadManagerImpl$start$$inlined$synchronized$lambda$1.run.     (DownloadManagerImpl.java:103)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)

When I set minifyEnabled false and shrinkResources false in release build, it works well.
If I turn those things on, I set proguard as following, it still not works, the error Bad file descriptor is still there.
-keep class com.tonyodev.fetch2.** { *; }
-keep class com.squareup.okhttp3.** { *; }

It's all about the contentResolver.openFileDescriptor(fileUri, "w") in the class StorageResolverHelper.kt.
When using with Storage Access Framework the file path is a Document uri, if the download is paused and then resumed, the file will be cleared to 0 byte and continued append the new bytes on Android version <= 9 (Realme C1 and Xperia Z1).
The fix is: contentResolver.openFileDescriptor(fileUri, "rw")
Everything works well again.
It took me a month to find this problem :))

Thanks @andj207, your patch https://github.com/andj207/Fetch/commit/49ca46e10d548f1bd7a94ba2cf4fef7ff5b233f7 fixes file corruption issues some of my users were facing (xperia, asus phones). I couldn't reproduce the bug myself but after  testing the patch with affected users, they reported file corruptions have stopped.
/cc @tonyofrancis

Also, this may be a diplicate of #454 where I got the proguard rules from.


Build from source fails due to function mismatch in MPIServer code

Context:
Trying to build from source, master branch as of 12/06/2018 T 06.00 UTC+2.
Configured to build with MPI support, using OpenMPI 3 (compiled from source and already tried and tested, including with older versions of TF, such as the TF master branch from a week ago).
The error occurs during compilation, preventing it to conclude successfully. Disabling MPI from configure leads to successful build.
Error messages (relevant parts):
ERROR: [...]/tensorflow/tensorflow/contrib/mpi/BUILD:83:1: C++ compilation of rule '//tensorflow/contrib/mpi:mpi_server_lib' failed (Exit 1)
tensorflow/contrib/mpi/mpi_server_lib.cc: In member function 'tensorflow::Status tensorflow::MPIServer::Init(tensorflow::ServiceInitFunction, tensorflow::RendezvousMgrCreationFunction)':
tensorflow/contrib/mpi/mpi_server_lib.cc:57:64: error: no matching function for call to 'tensorflow::MPIServer::Init(tensorflow::ServiceInitFunction&, tensorflow::RendezvousMgrCreationFunction&)'
   Status s = GrpcServer::Init(service_func, rendezvous_mgr_func);
                                                                ^

Debugging steps tried so far:
I am not familiar with the codebase, but it seems that the recently introduced feature Collective Ops (commits in Part 8) does add an argument place to non-empty GrpcServer::Init calls in tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc, which is then called in tensorflow/contrib/mpi/mpi_server_lib.cc with a number of arguments not matching any definition.
System information (if needed, anyway)

Have I written custom code: Yes, but probably unrelated (this and this patches to fix a GCC 8.1-related problem with MPI's streamexecutor);
OS Platform and Distribution: Manjaro Linux (ArchLinux);
TensorFlow installed from: Source, master branch;
TensorFlow version: 1.9-RC0
Python version: 3.6.3 (IntelPython)
Bazel version (if compiling from source): 0.14.1- (@non-git)
GCC/Compiler version (if compiling from source): 8.1.1; 7.x for CUDA
CUDA/cuDNN version: 9.2/7.1
GPU model and memory: Quadro Mobile M1000M (compute capability: 5)
Exact command to reproduce: Building from source (/bin/bazel build --config=opt --config=cuda --config=mkl --copt="-DEIGEN_USE_VML" //tensorflow/tools/pip_package:build_pip_package after having configured to use MPI)

Fixed by #19942. I'm closing the issue.


Allow installing as non-admin on Windows

Fixes a minor typo and passes the type parameter to fs.symlinkSync (which is used only on Windows and ignored on others) to remove the need to run as admin.

Do I need to add a changeset to the PR? I do not see it in the instructions in the README, so I hope it's not blocking this PR.

@aabounegm thank you so much for submitting this PR 🌼! It looks good to me.
@PhilippeduPreez can you please quickly test if it works? If so, I'll update some related parts of our docs and we can merge!
@aabounegm As for the changesets file - no, I don't think we need to add one for such a minor change. For future reference, here is the docs page with some helpful information for contributors - https://flowershow.app/docs/contributors. If anything is not clear or some information you're looking for is missing, please do let us know! Thanks again!

Thanks for the positive comment 😁. I did check the page, but I thought this fix was too small to open an issue for it before, so I got worried when the PR took a few days to be reviewed 😅. I tried to follow your commit messages style, though. Hope I didn't do it badly 😄.

@PhilippeduPreez any thoughts?

@aabounegm thank you so much for the contribution! We'll have a shout-out to you in our next release update!


Update nextjs.page.server.mdx: Add 'Other concerns' section + upd. table

Add table rows on Bundler and Caching.

Made some minor changes here as well. Let me know if you object with any of it, otherwise I'll merge.
Thanks, your PRs are very help and will have a significant impact on Vike's adoption.

Should be ready to merge now, if it looks good to you!

I made the Vike description a little more precise and more fair towards Next.js. Let me know if this looks good to you (and commits welcome to polish my English).

Merged 🎉
Thanks a lot @redbar0n.


IAsyncOperation breaks IntelliSense

About the problem
I noticed that when you put either co_await or co_return in the body of IAsyncOperation<TResult>, the IntelliSense stops working completely within the file that contains the function. The syntax is no longer highlighted and no suggestions are given. Restarting Visual Studio or rebuilding the solution doesn't help. The only way to bring IntelliSense back to work is to remove all co_await and co_return keywords.

How to reproduce

Launch Visual Studio 2019 (the version I'm using - v16.10.2).
Create a Windows Console Application (C++/WinRT).
Write a simple function, which return type is IAsyncOperation<hstring>. The TResult doesn't have to be  hstring.
Use either co_await or co_return within the function body.
Notice that the IntelliSense no longer works within the entire file until you manually remove all occurrences of co_await and co_return from that function.

The function I wrote:
IAsyncOperation<hstring> SomeRandomOperation()
{
    HttpClient client;
    Uri uri{ L"https://example.com" };

    hstring result = co_await client.GetStringAsync(uri);

    // IntelliSense stops working just after typing the "co_await" keyword.
    // The syntax is no longer highlighted and no suggestions are given.

    int32_t someRandomVariable = 123;

    return result;
}

Software details
OS version:  10.0.19043
Visual Studio 2019 version: 16.10.2
Extension version: 2.0.210505.3
NuGet package version: 2.0.210621.3
Closing
I am not exactly sure if this is a C++/WinRT issue or if there is something wrong with my environment. Anyway, I tried everything from simply rebuilding the solution to reinstalling the entire Visual Studio. Any help would be greatly appreciated.

I've successfully reproduced the issue on a newly created virtual machine.

Thanks for the report, however the Visual Studio team requests that you use their feedback tool for issues with tooling:
https://developercommunity.visualstudio.com/search?space=62

https://developercommunity.visualstudio.com/t/IntelliSense-stops-working-when-inside-a/1407261


Add no_std support

This adds no_std support to Rhai. The dependant crates are responsible for making sure the alloc crate is enabled. I've used https://github.com/rust-embedded/alloc-cortex-m for this.
The reason I chose for a feature called no_std, instead of adding a default feature std, is because we need to import several crates when we're not compiling from std. In most cases we have less dependencies.

HashBrown. HashMap is not available in alloc, because it uses an OS-based hasher by default: https://github.com/rust-lang/rust/issues/56192
core-error. Rhai uses std::error::Error, which is locked to std because of methods that are now deprecated. Core-error aims to be a replacement crate.
libm. core does not have support for floating point mathematics by default, and there are 2 places where f64::pow and f64::powi are called. Libm provides those functions on different platforms.

Two new features are added in this PR:

no_std: this enables #![no_std] and switches all imports to use core and alloc.
default_buildins: This enables all the methods in src/builtin.rs. This feature is enabled by default. If users of this crate (including myself) are limited for space on their target platform, disabling this feature saves a nice 80KB (out of 155KB).

Closes #19

I got Rhai working on an stm32f103 with 64KB of FLASH. With this change the library was barely too big (77KB), however after temporarily removing some language features (who needs functions, variables and if-statements?) I managed to get Rhai down to 37KB.
https://twitter.com/victorkoenders/status/1235247234356310016

I got Rhai working on an stm32f103 with 64KB of FLASH. With this change the library was barely too big (77KB), however after temporarily removing some language features (who needs functions, variables and if-statements?) I managed to get Rhai down to 37KB.

@VictorKoenders   I have been thinking.  Why does cutting off functions, variables and if-statements cut down on code size?  AFAIK those features are quite simple to implement, and adds little code to the code base.  The significant elephant features are arrays, resolving array indexing, and custom types (with dot getters/setters chain).
I'd imagine that simply by cutting off custom types, you'd probably cut down 1/4 of the code size. Another probably 1/4 if you cut arrays.
However, maybe you need custom types to expose features in your embedded system... but those can easily be flattened into a bunch of function-based API instead.  So if it were for me, I'd be dropping custom types but keeping functions, because function definitions mostly use code that are common for evaluation function calls...

Sorry my week's been busy. I'll finish the code before the end of the week.

Why does cutting off functions, variables and if-statements cut down on code size?

The large space saver is that the code ignores more tokens and has less complexity. The embedded version simply panics if it encounters a token it does not recognize. Because in my case all I had was a loop and 2 external fn calls, I didn't need to account for other language tokens.
From what I can tell, a large part of the rhai binary rhai is because of text-to-AST parsing. If that could be offloaded somewhere else, and have the AST send over and executed on the microcontroller, rhai would easily fit on a 64KB chip. In the future I can look into exporting and importing AST so this could be possible.

I'd imagine that simply by cutting off custom types, you'd probably cut down 1/4 of the code size.

This is probably true. Disabling builtins already saved almost 50%. I think in my experiment I removed all variable assignment so rustc was probably able to optimize away most variables and types.

OK, I did some experiments with the examples.  These program sizes are for standard release builds for x64 with standard library:

Build
Size
Decrease

standard
830K

unchecked
780K
50K

unchecked + no_index
680K
150K

Therefore:

checked arithmetic is 50K of code
indexing feature is 100K of code

OK, I did some experiments with the examples.  These program sizes are for standard release builds for x64 with standard library:

Build
Size
Decrease

standard
830K

unchecked
780K
50K

unchecked + no_index
680K
150K

unchecked + no_index + no_stdlib
560K
270K

Therefore:

checked arithmetic is 50K of code
indexing feature is 100K of code
the standard library is 120K of code

So the major reduction ones are: arrays/indexing (as predicted), and floating-point support.
Your milage may vary because no-std doesn't have floating point in the first place.

As expected, removing functions does not make the code size any smaller.

I realize that by doing lto=fat and not setting opt-level=z, I have been optimizing for speed instead of size.
Rebuilding for size in 32-bits on a Windows system:

Build
Size
Decrease
Feature

standard
492K

unchecked
464K
28K
unchecked = 28K

unchecked + no_index
408K
82K
no_index = 56K

unchecked + no_index + no_float
323K
169K
no_float = 87K

unchecked + no_index + no_float + only_i32
268K
224K
only_i32 = 55K

unchecked + no_index + no_float + only_i32 + no_stdlib
238K
254K
no_stdlib = 30K

unchecked + no_index + no_float + only_i32 + no_stdlib + no_function
233K
259K
no_function = 5K

@schungx I've re-applied all the changes. I also moved all the imports to stdlib.rs which matches the no_stdlib feature you introduced.
With all the stuff going on in the world I'm not able to test this on a microcontroller any time soon. However seeing as this compiles and with the size optimalizations you've done, I'm certain it works fine. The codebase itself already worked and if people want to reduce the file size they can work it out.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101576

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101962

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103387

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105209

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105331

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110687


Visibility/obstruction charts

We have very nice pass plots. However, they assume that there's 100% horizon visibility without any obstructions. We could implement some sort of visibility information. Trickle planner for GPS planning had a cool feature like that. We could come up with something similar.
For now, this could be for information purposes only. But in the future, we could use that for observation planning. No need to listen to a sat if it's behind a building.

I think that we can also implement obstacle map in planning process. Now we have a possibility for set minimal AOS elevation. But more powerful will be 360 degrees mask.
For example as you know our antenna is covered by wall from one side. It will allow us to avoid recording when satellites are hidden when flight from that side.

We can inherit the LocationPredictor class and overload the iter_passes function. It will call the original implementation to get the pass iterator.
Next, we will crop the passes in these places where obstacles occur.
The new class will accept the obstacle mask in the constructor. This mask will be a CSV file with azimuth degree and obstacle elevation at a specific angle. Users will be able to provide as accurate data as they want. The elevations for missing angles will be interpolated (we can implement linear or polynomial interpolation to choose by user).
The predictor will accept the standard parameters as aos_at, los_at, max_elevation_degrees. Additionally, it may accept maximal duration of signal override to avoid unnecessary reception interruption.

The LocationPredictor inheritance makes sense.
I'm not sure if the CSV format will be enough. I think there are several aspects here:

some obstructions are soft, i.e. there's a building that blocks path, but we can point antenna there. If there's no better path, antenna can pass through this, just the reception will be poor.
some obstructions are hard, i.e. there's a wall, roof, or whatever that physically prevents antenna from moving in that direction. If we try to move it there, equipment damage will occur and we should never do this.
for some antenna/rotor configuration, I had a conflict with a roof over my balcony. For directions az=0-40 degrees, antenna could move horizontally when it was pointing relatively low (el=0-30 degrees), it would hit the roof for mid-elevations (el=30-60 degreees) and was moving ok if way pointed up (el=60-90 degrees).
ultimately we should address several use cases:

fixed omni antenna that is obscured in some directions
fixed directional antenna that is pointed in some specific direction. It has some selectivity and there's no point in listening when sat is outside of its primary beam.
moving directional antenna that can move freely everywhere, but is obscured in some directions
moving directional antenna that has its movements restricted in some directions

It's complicated. We can support all of them, but it's fine if choose to focus on some of them for now,

I think that there are two separate use cases:

Rotor controlling
Pass planning

The "obstacle" meaning is different in both cases.
In rotor controlling, you need to define a path to avoid collision with obstacles. We need to analyze only blocks near the antenna (in rotation radius). These obstacles sometimes have a small height and width - it means that in some cases, you can move below or above the obstruction. Additionally, an object that is an "obstacle" for the rotor may be "transparent" for receiving the signal.
The obstacles can be far from the antenna (e.g., buildings). In this case, you can assume that the obstacles are filled - you cannot receive the signal only above the block.
In summary - I think that we should have separate obstacle models for controlling and for planning. My above proposal was about pass planning.
I agree with you that we need the elevation range for controlling the rotor, but in pass planning, we can use only the maximum elevation on a specific azimuth.
I will try to implement the obstacle model generic to re-use this component in the rotor controller. But rotor-related design should be discussed in the svarog-ctl repository.

That's a fair assessment with the planning and rotor control. It more or less maps to my concept of soft and hard limits.
Reusing the code for obstacle model sounds great!


generate crd api docs

Closes #1248
Closes #671
Signed-off-by: Benedikt Bongartz<EMAIL_ADDRESS>

rebased and regenerated docs


Document 'optional' argument supported in AzureML component YAML v2

I was looking for a way to make uri_file inputs optional and spotted in the YAML v2 specification that there is in fact an optional attribute supported (https://azuremlschemas.azureedge.net/latest/commandComponent.schema.json - in the InputPortSchema).
I tried it out, then received an error "In command "xxx", optional input yyy must be placed in nested argument: []." when submitting the job. I guessed the syntax, and now it works as we required. Is this deliberately undocumented, or just not documented?
For reference:

inputs:
  dsm_input_file:
    type: uri_file
  orthophoto_input_file:
    optional: true
    type: uri_file

command: >-
  python3 main.py
      --output_folder ${{outputs.output_folder}}
      --dsm_input_file ${{inputs.dsm_input_file}}
      [--orthophoto_input_file ${{inputs.orthophoto_input_file}}]

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

ID: c5f00a7b-6459-9082-edd6-2ceda2e5a8c2
Version Independent ID: 64a0194e-ad23-5cd2-fb84-8fc92d045fd2
Content: CLI (v2) command component YAML schema - Azure Machine Learning
Content Source: articles/machine-learning/reference-yaml-component-command.md
Service: machine-learning
Sub-service: core
GitHub Login: @s-polly
Microsoft Alias: scottpolly

@jamescrowley
Thanks for your feedback! We will investigate and update as appropriate.

@jamescrowley ,
For your requested The Docs itself mentioned the page please looking to this if needful, Below updated for your reference

For examples
https://github.com/Azure/azureml-examples/blob/main/cli/jobs/pipelines-with-components/rai_pipeline_adult_analyse/components/component_gather_rai_insights.yaml

I’m so sorry @RamanathanChinnappan-MSFT  I have no idea how I missed that 🙈 Many thanks for the example


Foundry 0.7.5 Compatibility

Have there been any reports on Foundry 0.7.5 compatibility yet? Would be good to update moduledb.json if compatibility is confirmed.

I haven't had any issues on 0.76


[CLOSED] Extend init method to support a mode flag

 Issue by hvolos
Wednesday Aug 31, 2016 at 19:26 GMT
Originally opened as https://github.com/hkimura/libnvwal/issues/3

Supported mode flags: L_CREAT, L_TRUNC, L_EXCL
0: attempts to restart existing log and fails if log doesn't exist. Doesn't create anything if log files do not exist.
L_CREAT : If log exists, then it attempts to restart. If there is no log remnant to restart from, then it creates a new. Otherwise, if there is a log remnant that couldn't restart from, it returns error.
L_CREAT | L_TRUNC: discards existing logs, and recreates a fresh log.
Alternatively can be done through the configuration object.

 Comment by hkimura
Thursday Sep 15, 2016 at 23:59 GMT

I guess this item is done


skinchanger

the skin name show “？” when game language is chinese

The skin changer doesnt recognize the character thats why

It doesn't recognize the character

套壳的傻逼弟弟

Yeah, you translated Osiris into Chinese and sold it, right?

Yeah, you translated Osiris into Chinese and sold it, right?

中午界面配置皮肤看不到名字，只能到英文去配置，切换回中文后配置又会乱而已，别张口就来好吧

Yeah, you translated Osiris into Chinese and sold it, right?

中午界面配置皮肤看不到名字，只能到英文去配置，切换回中文后配置又会乱而已，别张口就来好吧

我是说， 你想汉化了卖钱吧  @GhostNoc

Yeah, you translated Osiris into Chinese and sold it, right?

中午界面配置皮肤看不到名字，只能到英文去配置，切换回中文后配置又会乱而已，别张口就来好吧

我是说， 你想汉化了卖钱吧 @GhostNoc

我只是自己玩玩而已

English please xd

有这功夫去学学imgui 而不是在这issue

English please xd

:P I just chatting with him

You need to add Chinese Unicode ranges to https://github.com/danielkrupinski/Osiris/blob/d432198196da9ce83451ef90ea8af5d503d8eb5c/Osiris/GUI.cpp#L37 .

You need to add Chinese Unicode ranges to
https://github.com/danielkrupinski/Osiris/blob/d432198196da9ce83451ef90ea8af5d503d8eb5c/Osiris/GUI.cpp#L37
.

I added the range
io.Fonts->AddFontFromFileTTF(strcat(buffer, "/Fonts/Tahoma.ttf"), 16.0f, nullptr, io.Fonts->GetGlyphRangesChineseFull());
but it's not working, still display '?'

Maybe you need Chinese font file, see https://github.com/ocornut/imgui/issues/1434

xswl


general: use pre-built images for speed of development

pwd, l2, github.com/play-with-go/gitea/cmd/gitea, controller and github.com/play-with-go/preguide/cmd/preguide all rely to some extent on running a version of "self" in a container. Put another way, when running PWG we end up compiling linux/amd64 versions of these programs in order to run them inside a Docker container.
When not developing any of the above, this is a potentially significant cost in terms of CPU time (consider CI instances which are much smaller), especially when not developing on a linux/amd64 platform.
A better approach therefore might be to offer pre-built Docker images for each of the above, tagged according to the version of the module to which they correspond.
This requires some sort of tip and tag-based CI workflows to automatically build and push docker containers corresponding to the pseudo-version/tag. This is doable, and in some respects correctly shifts the burden of building these programs to us, rather than the end user (the person creating guides).
This also somewhat suggests that we should move cmd/controller out to be a dependency of its own (because otherwise cmd/controller is part of the main module and not versioned)
If we did implement this then we would be able to drop the _scripts/{gitea,preguide}.sh scripts.

This cost has largely been amortised by the use of buildkit with a shared and persisted build and module cache. We can re-open a more specific issue if there are any other improvements that jump out at us.


Replace usage of secrets.SUPPORT_TOKEN PAT with standard github.token

Pull request template

Motivation and context
Full context of this change on https://searchbroker.atlassian.net/browse/OPS-8556
I've replaced the usage of secrets.SUPPORT_TOKEN with the standard github.token where possible, with the exception of the edocs workflows since those target a separate private repository, where the workflow wouldn't have proper permissions since permissions of the github.token are scoped to the current repository so, in that case, a Personal Access Token (PAT) is still necessary. We might revisit that trigger in the future.
Also removed the github_token input when calling the ad-m/github-push-action action as ${{ github.token }} it's already the default
Type of change

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that causes existing functionality to not work as expected)
[ ] Change requires a documentation update

What is the destination branch of this PR?

[x] Main
[ ] Other. Specify:

@Roberdvs we have the main branch write protected, so every change must be done through a PR. However, the Lerna's release process generates a new commit that needs to be push to main from the CI. Currently we use the SUPPORT_TOKEN to bypass the write protection for this use case. Is the github.token able to do that? Last time I checked I think was not possible but maybe we can change the default permissions.

You're right, seems that still isn't an option:

https://github.com/orgs/community/discussions/25305
https://github.com/orgs/community/discussions/13836

And the workaround is to either use a PAT or use custom GitHub app, which can be configured to bypass branch protections (See here & here).
I'll rollback the change for now on the publish-release.yml workflow and we'll come back to this later.


Update T000032.md

Included math type for T_2.5

Strange, https://topology.jdabbs.com/theorems/T000032
still shows "(where Comp. Haus means T_Parse error: {2.5}).", which this was supposed to fix?


[Alarms & Timers] Fix #1735

Fix issue introduced with #1722.
I open a new PR because the old one (#1729) contains other stuff also.

Fix #1735

Thanks!


Null Cheater Model

Model merge of Null Pointer #34111 and Cheater #34119

I am new to contributing to openpilot, does anyone know a good way to include the supercombo.onnx model in my PR?

This (a merge of two models trained in two different simulators) is not something we plan to upstream.
Our strategy is to get rid of the old sim completely.
You're very welcome to maintain a fork of openpilot and give these models a try though! You could try other merging approaches or other models, and post about them in #topic-custom-models or #custom-forks in our discord!
Have fun!


Add vm.bitcast ops for i32<->f32 and i64<->f64.

Working towards https://github.com/google/iree/issues/6629
Also included a conversion for standard bitcast -> vm.bitcast.* ops.
See also https://reviews.llvm.org/D105376 for std.bitcast, which has more details about endianness and includes some fold/canonicalization patterns. We have a more restrictive set of types to support here.

Presubmit passed but GitHub service degradation swallowed the completion signal. Merging manually.


Intel HAXM installation failed, For more details, please check the installation log: C:\Users\HP\AppData\Local\Temp\haxm_install-20220801_0909.log

ersion: 7.6.5
Output folder: C:\Program Files\Intel\HAXM
Extract: checktool.exe... 100%
Execute: C:\Program Files\Intel\HAXM\checktool.exe --verbose
CPU vendor          *  GenuineIntel
Intel64 supported   *  Yes
VMX supported       *  Yes
VMX enabled         -  No
EPT supported       *  Yes
NX supported        *  Yes
NX enabled          *  Yes
Hyper-V disabled    *  Yes
OS version          *  Windows 10.0.22000
OS architecture     *  x86_64
Guest unoccupied    *  Yes. 0 guest(s)
The system requirements are not satisfied.

Seems like you did not enable VMX, please try to enable VMX before installing HAXM

i have the same problem

VMX enable

how to enable VMX

same issue i am facing how to enable


Saleor 3093 variant selection attributes

I want to merge this change because...
This is a followup with futher changes from https://github.com/mirumee/saleor-dashboard/pull/1458 . Can't push directly onto it since I don't have necessary permissions

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://master.staging.saleor.cloud/graphql/

Task linked: SALEOR-3093 Variant selection attributes

 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.0 out of 2 committers have signed the CLA.:x: Bonifacy1:x: golota60You have signed the CLA already but the status is still pending? Let us recheck it.


If LoadBalancerClientFilter NotFoundException set status to 404

This kinda falls between two stools. It's a question but I feel it's also an issue tho happy to be corrected.
In the LoadBalancerClientFilter class it throws a NotFoundException exception if it can't find the load balanced endpoint defined in a route but when this is returned to the browser it is returned as a HTTP 500, example response below.
{
    "timestamp": "2018-07-05T09:19:43.749+0000",
    "path": "/xyz/get/request",
    "status": 500,
    "error": "Internal Server Error",
    "message": "Unable to find instance for xyz-service"
}

Normal HTTP protocol would suggest we should be returning a 404 here as the thrown NotFoundException would also suggest. Something back up the filter chain is catching the exception and converting to internal server error which I believe to be the wrong behaviour.
Is this a bug or intentional? Could someone suggest a way we could 'intercept' the error and return a valid 404?
Thanks, Andy.

See https://github.com/cloudfoundry/gorouter/issues/135
Should likely default to 404 and be configurable as 503.

Same 500 error in zuul in spring cloud netflix, so at least we have parity :stuck_out_tongue_winking_eye:

the problem with a 404 is that by default, the retry filter won't retry a 404, a 503 it would.

@spencergibb makes sense for it to be retried on a 503 I guess, would be good if there were a way to have the final status correct on the response before finally sending it back tho.

Yeah, it's more involved than even just that after a little exploring

@spencergibb if it was easy it wouldn't be any fun 😉

Let's default to 503, configurable to 404.

@andye2004 were you working on a PR for this?

@ryanjbaxter Sorry, I wasn't no. We're currently just living with it. Happy to have a look if you need someone to do it but would probably need a little guidance from @spencergibb or others re the configurability of it.


Assess and document Windows OS compatibility

CytoTable currently is tested against Linux and MacOS environments. This issue highlights a need to assess and document Windows OS compatibility as a proactive step towards user support.
Possibly related / involved: Parsl/parsl#1878

It's possible WSL1 or 2 may be required to run CytoTable within Windows environments. To this effect, GitHub Actions may need special considerations. See the following links for more information:

https://github.com/actions/runner-images/issues/5920
https://github.com/Vampire/setup-wsl

Have we already had requests for native Windows support? I'm a Windows user, but long before I started using devcontainers for everything I only ever ran code/cli tools in WSL. That meant I was always looking at the Linux/Ubuntu documentation section for tools anyways.
I've done some work on Github Actions in a  repo that supports windows natively and ut was a pretty big headache. The testing matrix was very complicated and there were multiple versions of jobs that were required for the different platforms.

Thanks @kenibrewer ! It does seem like this might be a challenge on multiple fronts. I raised this issue in anticipation of users coming from Windows as part of investigating IN Carta for #136 . Reading through the documentation found here it seems that IN Carta is a Windows-only software, meaning that there's likely a chance we will need to support Windows somehow (even if through WSL). I'm under the assumption that https://github.com/Parsl/parsl/issues/1878 could take time to address and WSL1 or 2  (as opposed to native Windows) would be advisable to any Windows users of CytoTable. I feel that WSL, like MacOS, is different enough from Debian Linux to warrant a distinct test for observing behaviors.
This issue I think could be addressed with:

[ ] a specialized test for Windows over WSL1 (because WSL2 is not yet supported on the default GitHub Actions images)
[ ] documentation on installing / using WSL with CytoTable

Doing these could help us prepare for IN Carta users through prior awareness of technical issues and a focus on documentation (guidance on WSL usage if the users are not yet aware, etc). All that said, there are some possible "unknowns" here (deeper than the Parsl fork error we face now on Windows).


NEXT-36826 - Fix the selected customer when creating a new order

1. Why is this change necessary?
If you are in the customer's orders view and want to create a new order for the customer from there, the customer object has so far been transferred as a route parameter. This behavior has worked in some scenarios but has been advised against as it's an anti-pattern in routing for many reasons, one of them being reloading the page lose the params. Fixing vuejs #1497, required getting rid of unused params and therefore it breaks this long standing anti-pattern usage. You can read more about it here. As a result, the transfer of the customer no longer worked and the customer had to be searched for and selected again in the create-order view.
2. What does this change do, exactly?
Now the sw-customer-detail-order component passes the customer ID as a query parameter instead of passing the customer object as a route param and the sw-order-create-initial component loads the customer object by this ID instead of reading the customer object from route params.
3. Describe each step to reproduce the issue or behaviour.

Go to Customers -> Overview
Select a customer
Click on Tab "Orders"
Create a manually order with the "Add Order" Button
In the "New order" modal view the customer is not preselected and you have to search it again

4. Please link to the relevant issues (if any).
Issue: https://github.com/shopware/shopware/issues/4376
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

Having never written JS tests before, I didn't know whether to write JEST or Cypress tests for this change. If tests still need to be added here, I would be pleased if you could tell me what I should use to write the tests and what should be roughly tested.

Having never written JS tests before, I didn't know whether to write JEST or Cypress tests for this change. If tests still need to be added here, I would be pleased if you could tell me what I should use to write the tests and what should be roughly tested.

@momocode-de It would be nice if you could add a jest test for the sw-order-create-initial component. It should consist of four test cases:

"should be a Vue.js component" (like in any jest test)
with no customerId in query, no repository and state call are made
with nothing returned from the repository, no state should be set
with something returned from the repository, the state should be set

@cyl3x Thanks for your test instructions!
I have implemented and pushed 3 out of 4 tests. Can you give me some feedback on this?

with no customerId in the query, no repository and state calls are made

Should I check whether the “get” function of the customerRepositories has been called? If so, what is the best way to do this? Unfortunately, I have not found a similar case in the existing tests where it is checked whether a repository function has been called. Or is it sufficient to check whether a customer object is in the state, as in the 3rd test?

Thanks for your contribution @momocode-de, you did a great job :blue_heart: :tada:


Fixes #1569 - Split http_endpoints parameter

This change is inspired on code from MarathonConf. I'm still a scala newbie, so don't be afraid to bash me ;-).

:100: Very nice!


Unable to scroll at all in files

Description
Unable to scroll using the trackpad on my laptop in any area of files. Tried with a mouse and the problem persists
Steps To Reproduce
Try to scroll.
Steps to fix
unfixed at the moment
Files Version
Stable <IP_ADDRESS>
Windows Version
22621.675
Relevant Assets/Logs
debug.log

Is this issue in the setting dialog as well?

For me this is everywhere.  In settings section as well.
debug.log

Seems to be an issue with WinAppSdk, can you report it on their repository?

Do I need to install any of the SDK's ?  I don't have Visual Studio installed.

You can make the issue here https://github.com/microsoft/WindowsAppSDK/issues


try/catch autocomplete

Like the rest of Visual Studio, when editing in a razor file's @code section, I would like autocomplete to work for things like try/catch (tabbing twice after typing try)

Duplicate of https://github.com/dotnet/razor-tooling/issues/4322

Similar to 4322, but hardly a duplicate.

Noooo, you are describing snippet behaviour, that doesn't work. https://github.com/dotnet/razor-tooling/issues/4322 describes the same problem, but with an example of other snippet.

I agree with @DoctorKrolic's synopsis, @pmarangoni why do you feel this is not the same as #4322?

#4322 was in the markup, and mine was in the @code section.  That's why I said similar, but not a duplicate.

#4322 was in the markup, and mine was in the @code section. That's why I said similar, but not a duplicate.

Oh thanks for confirming, we're using #4322 to also track doing snippet expansion in @code blocks as well. No worries!
I'll close this as duplicate for now.


Which version of COCO for calibration?

Just to clarify, from which version of COCO are these calibration images?
https://github.com/mlperf/inference/blob/master/calibration/COCO/coco_cal_images_list.txt
I could not find them in val2017, but val2017 is what is referenced here:
https://github.com/mlperf/inference/tree/master/others/cloud/single_stage_detector/pytorch

We use val2017. The calibration might come from train2017.

I've found similar image filenames in val2014 and val2017, and so far they are the same files (example hash match below for the last image in the list).  It would be nice to add clarity here though.
$ md5sum val2014/COCO_val2014_000000511117.jpg
cd81784d6252c106a8857e595b4b409b  val2014/COCO_val2014_000000511117.jpg
$ md5sum train2017/000000511117.jpg
cd81784d6252c106a8857e595b4b409b  train2017/000000511117.jpg
What do you mean by "we use val2017"?  The provided calibration image list(s) are not the required images to use for calibration?

In general we use coco 2017 for everything.

I can confirm that all the images from coco_cal_images_list.txt are in both val2014 and train1027.
The confusion mainly came from COCO's calibration images are then from its training set while ImageNet calibration images are from its validation set.  Maybe calibration images should always come from the training set?

Its a perfectly valid issue. For some reason we have been specific with imagenet (like imagenet2012) everywhere but not with coco ... we should update the README's to say coco 2017

IIRC, the WG decided that downloading the whole ImageNet training set just for a hundred  calibration images would be impractical hence using the validation set. For COCO, however, this was fine.


Creation handler to accept different kinds of model

Can the creation handler used with another model other than Item?

The creation handler just takes an action like the other handlers, in this case, CreateAction type, the action inside has the metadata to do what we need to do, in this case with CreateItemAction we have the metadata to build an item that will be stored.
Does this solve your question? if not, could you explain a bit more?

Closing it since it seems the answer was enough.


Documents component is installed but when I change item it show me the documents of previous item

Documents component is installed and working but when I change item it show me the documents of previous item.
if I leave the app and come back it shows me the correct documents.

got the same problem
Open Account 1 -> View Account 1
Open Account 2 -> Still Account 1 (FolderPane & Title), shown Files are from Account 2
Reload -> Account 2 is fine, Account 3 shows Account 2 Data

The issue should be solved now.

The issue should be solved now.


Training of WnAn

I noticed an update to the BNN-PYNQ library adding support for WnAn.
Can you please give a pointer as to what quantization scheme are you using, and what framework?
From the finnthesizer, it does not look like you are using DoReFa-Net like you used in QNN-MO-PYNQ.

We're planning to release the training scripts by the end of this week - I hope this will answer all of your questions.

Can you link a research paper, if you have implemented that?

What does the s0.5 and s0.25 imply in the given .npz names?

There is actually no (relevant) meaning to those. It's related to the topological description of CNV & LFC - these values are simply hardcoded into the cnv/lfc.py files respectively.
Apologies again for the delay, we plan to upload the training scripts for these this week.

Thanks, I was able to train a 2 bit and a 4 bit network using the -.5,.5 and equidistant thresholds respectively.


Added getSearchCount that returns the number of results found by search

DevOps requested a way to see the active n-cube count for a given ApplicationID, which will allow them to automate the verification of an n-cube release.
I decided to piggyback off of search and default cubeNamePattern, content and active to make the call easier for them, but also allow for a more robust search count if necessary.

I had a couple different names locally, so I'm cool with whatever makes the most sense. At first I did getAppCubeCount, until I realized it could be a count based on some search parameters. Then I changed to getSearchCount since it's really just telling you how many results you got back, but getCubeCount might be more generic.


Method not found after update to MongoDB.Driver 2.19+ where Skip, Limit become Int64

Is there an existing issue for this?

[X] I have searched the existing issues

Product
Hot Chocolate
Describe the bug
There is an runtime error after update from MongoDB.Driver 2.18 to MongoDB.Driver 2.19 due to a signature of the methods Skip(), Limit() was changed:
Skip(int skip) => Skip(long skip)
Limit(int limit) => Limit(long limit)

see jira.mongodb CSHARP-4445: Support 64-bit values for Skip and Limit/Take:
Steps to reproduce

Query with pagination

    [UsePaging]
    public IExecutable<DataModel> GetData()

Update to MongoDB.Driver 2.19
Runtime error when calling GetData() query

Relevant log output
"message": "Method not found: 'MongoDB.Driver.IAggregateFluent`1<System.__Canon> MongoDB.Driver.IAggregateFluent`1.Limit(Int32)'.",

Additional Context?
No response
Version
12.18.0

That is a breaking change in the contract ... not really a bug on our side... We will create a new package version for 13.1

@michaelstaib, is there any chance to backport the Mongo Driver version bump to 12.x?

This is now fixed


Fix: Remove unnecessary nested function in authorizationHeaders() and rename it to getAuthHeaders()

The third part from https://github.com/pilcrowOnPaper/lucia/pull/508, and I also renamed it to getAuthHeaders() because it seems more convenient and shorter.

I think authorizationHeaders() is a better name, the header name is literally Authorization.


Messages are posted where most of my friends are

When I post a message, it will go to the community where I have most of my friends. Perhaps there is a count of friends returned so the React client can make a decision.

I am starting to rethink this. Perhaps they must choose. Curious about your thoughts.
For nkw let's just choose one. If you have already written code that is ok. We may use it anyhow.


gene_mean_with_sig function missing!

Hi, thanks for such a nice tool.
I think the gene_mean_with_sig function can not be found in the pp script.
Best,
Daniel

obs_mean_with_sig as well.
Best,
Daniel


Add profile dell-os10

What does this PR do?

See title
Motivation

https://datadoghq.atlassian.net/browse/NDM-2002
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

There was also an empty MIB: line, I fixed that.


fix: make pull request getter more resilient

GitHub randomly not send the body...
Depends-On: #527

This pull request is part of a stack:

refactor: check API response globally (#511)
chore: use a more reliable solution to get changes (#512)
feat: allow to pass author (#520)
feat: add stack checkout (#523)
feat: add stack github-action-auto-rebase command (#527)
fix: make pull request getter more resilient (#528) 👈


Remove reference to the preemptible_rollup branch of the googlegenomics fork.

The code needed for using preemptible VMs is now in the master.

LGTM, nice to have that rolled into master


GTK3 implementation should check xft.dpi settings, not just scaling factor

My dpi settings under gnome and i3 seem to be ignored.  There's another github issue (which now I'm having trouble finding again) indicating Avalonia currently only uses the gdk window scale factor setting.
It's an int, 1 is not scaled, and 2 or more makes everything huge so i'm not sure why anyone would actually set this.
I think Avalonia should be checking this: https://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings--gtk-xft-dpi.
More details here:
https://bugs.chromium.org/p/chromium/issues/detail?id=723931 (see comment 13)

@jameswalmsley did you have a similar issue before?

Fixed by switching to X11 backend. For configuring per-monitor DPI see https://github.com/AvaloniaUI/Avalonia/wiki/Configuring-X11-per-monitor-DPI

From what I can tell, this line is where you are getting scale factor (from Avalonia.Gtk3/WindowBaseImpl.cs):
        public double Scaling => LastKnownScaleFactor = (int) (Native.GtkWidgetGetScaleFactor?.Invoke(GtkWidget) ?? 1);
According to this StackOverflow answer, you can get the DPI from the (poorly-named) gdk_screen_get_resolution.  A gdk screen instance can be retrieved from gtk_widget_get_screen.
Unless I'm missing something, seems like the GTK backend should be doing this.

@davex25 Gtk backend is being removed, you should switch to using X11 backend.

Doesn't this mean requiring users to configure yet another thing?

It should detect your DPI automatically from EDID. If it does, see https://github.com/AvaloniaUI/Avalonia/wiki/Configuring-X11-per-monitor-DPI

Ok.


Made ConjunctionSpans class public and intersect method public

Should these also be merged to fs/branch_9x in our lucene fork and potentially also done as upstream tickets?


I would like to add simulator screenshots functionality for failed tests - few questions

Hi,
I would like to add new functionality to Bluepill which would take simulator screenshot whenever ui test fails and output those as a result together with test results.
For now from what I've seen in bluepill implementation and private headers there is something like that (already implemented screenshot functionality, like simctl screenshot) inside DVTDevice.h header. But knowing this I can't somehow link this information to SimDevice.h used across bluepill (or SimServiceContext.h).
Is this even correct approach to do this? Any suggestions / directions would be very appreciated.

This is possible but not trivial, I didn't really look into that because we take screenshot in the UI test framework side. I suggest you take a look at FBSimulatorControl if you are interested in implementing this feature.

Thanks for the hint. After spending more time with it (Bluepill and FBSimulatorControl) this seems like pretty straight forward feature to implement. So stay tuned, I will create something soon :)

Awesome! Looking forward to that @adamszeremeta


variables included in Instructions parameter of manual intervention task could not be recognised in the alert email

In this document, "You can use built-in and custom variables to generate portions of your instructions."
But the variables in Instructions did not be replaced by its value in my email.
There is the related thread:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/1a2f815a-1b6e-4b02-a33b-9a81258d39da/release-variables-are-not-being-expanded-in-email?forum=tfsbuild

Hi, TFS2017U1 does not have this feature (variable expand support in MI instructions). 2017u2 has this feature. In above message release definition name and environment names only expanded. $(Agent.Name) not expand because server phase does not contain agent. $(Release.Artifacts.{webredirect}.DefinitionName) not expand because this is not in variable format. If you try same variable in powershell, you will get error.


DefaultSearchPlatform

How to do  defaultplatform to search, everytime  it search ytsearch, im disabled youtube search in lavalink but im idk how to disable it bot side.

make defaultPlatform: "scsearch"

and when you search track use spotify or scsearch

make defaultPlatform: "scsearch"

Can y can write code example to do that please?

Im maked Poru options defaultPlatform: "scsearch". But it searching yt and don't find any song because I disabled youtube search in lava link...

Solved that, thanks.


How to use LoRa

Could you please tell me how to integrate ControlNet、LORA? Also, could you show me the workflow?

Heya. for LoRA loading, please refer to normal comfyui guides, but in practice, you'd place a Lora Loader node after the Checkpoint loader, and route your clip and unet (model) through it, and into the original nodes in the workflow (text encoding, sampling.). For ControlNet with deforum, you'd want to use a (deforum) Load Video node, which returns a single frame on each execution, or use logic nodes to control other video loader nodes to return the relevant frames desired for your animation, then route that into a ControlNetApply node which normally sits before the sampler, after the text encoder, as the information get's embedded with the conditioning each time.
https://www.runcomfy.com/comfyui-nodes/deforum-comfy-nodes/DeforumControlNetApply
https://www.runcomfy.com/comfyui-nodes/deforum-comfy-nodes


Limit account import/creation to only two tabs and fix language and add tooltips

[x] Remove mnemonic and key pair tabs from Add an Account screen.
[x] Rename "Import Fundraiser" tab to "Import Fundraiser Wallet"
[x] Change Import fundraiser instructional text to "Please refer to the PDF document that you created during the Fundraiser."
[x] Use proper field labels: 15 Word Secret Key, Fundraiser Password, Fundraiser Email Address, KYC/AML Activation Code.
[x] Add tooltips to Fundraiser Password, Fundraiser Email Address, and KYC/AML Activation Code. (text provided below)

Fundraiser Password Tooltip:
This is the password that you used when generating a Tezos paper wallet to participate in the Fundraiser.
Email Tooltip:
This is the email address that you used when generating a Tezos paper wallet to participate in the Fundraiser.
KYC/AML Activation Code Tooltip:
This is the activation code that you received after completing the KYC/AML process. An activation code corresponds to a public key hash and is required if you participated in the Fundraiser. You may complete the process at verification.tezos.com if you have not done so already.
Designs:
https://zpl.io/blpj4o0
https://zpl.io/2ZJDxYE

It still says “Add an Address” instead of “Add an Account” - please see the design
When entering the seed phrase when the phrase uses longer words it doesn’t all fit in and gets cut off, there is no way to scroll inside the input field to see the beginning of your seed phrase.
When entering an email that is too long it shows up under the question mark icon instead of being pushed back like the seed phrase. Text should not be appearing under that icon. We should treat it as if the input field is shorter.
Activation code field can be a little bit narrower to give email field more space
The website (verification.tezos.com) mentioned in the KYC/AML activation code tooltip should be linked.

@mikaScalac

[ ] When I switch between "Import Fundraiser Wallet and "Create New Account" tabs it clears my Fundraiser secret key.
[ ] The fields right now are not aligned and displayed in diagonal zig-zag fashion. Please make the pkh field the same width as Activation Code for now. We'll fix this layout later with another ticket.

[ ] Activation Code label reverted back to "KYC/AML Activation Code". Please remove "KYC/AML" part of the label.

In fix layout ready to merge


Parallelize iterators

Overview
This pull request adds parallel execution of aggregate SELECT statements. Iterators within each shard  are split using the NewParallelMergeIterator() function which processes iterator batches based on the number of logical cores on the system.
/cc @jwilder @toddboom
Results
On an AWS c4.8xlarge machine, performance of a simple COUNT() query over 1B points and 100K series drops from 1m57s to 16.8s. The execution of the count itself is significantly improved, however, the bottleneck on the query is now in the single-threaded planning phase for the 100K series. Parallelizing the planning phase should improve performance significantly for large numbers of series.
TODO

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

👍


Replace a dom element other than body?

Would it be possible to add an option to replace something other than the <body>?
I've built many site where the header / footer needed to stick around and only the content inbetween needs to be replaced. I've tried using data-turbolinks-permanent in beta 3 but it doesn't seem to have the same effect.
I'm thinking something like this:
<head>
  ...
  <meta name="turbolinks-container" content="#main">
</head>

Hi Wayne,
Part of what makes Turbolinks so simple is that it "just" swaps the <body>. I don't think we should deviate from that.
I'm curious why permanent elements aren't working for you. Could you elaborate?

Thanks for responding @packagethief. I love the default zero-configuration behaviour of swapping the contents of the body, it's amazing!
I've been trying to use permanent elements to persist dom created by 3rd party javascript, which I have no control over unfortunately. That hasn't been working for me. I think it might be because turbolinks is looking for data-turbolinks-permanent once, on initialisation and I'm trying to dynamically add the attribute later on?

I think it might be because turbolinks is looking for data-turbolinks-permanent once, on initialisation and I'm trying to dynamically add the attribute later on?

That sounds like the problem. Permanent elements must match between pages. If you add one with JavaScript that isn't present on the next page rendered from the server, it won't be carried over.
What about creating a permanent container element that you do render on the server, and placing your 3rd party DOM inside it?

That's the thing though @packagethief, I'm currently facing a scenario where I can't tell the javascript where to render it's dom :(

@packagethief I got a similar problem using the toastr plugin
the idea was bump a toastr after the model was successfully created, so on create.js.erb I just triggered and everything should work fine.
My case was similar to @wayneashleyberry one, once I don't have control about the rendering, then my solution was
$( document ).one( "page:load", function() {
  toastr.success("message", "title", {timeOut: '5000', closeButton: true, progressBar: true});
});
Turbolinks.visit('/path/to/models');

@packagethief is it possible to stop the body swapping somehow in turbolinks:before-render? If so, people could use event.data.newBody to replace some elements themselves. This would allow advanced usage for those who need it while still keeping the easy-to-use default way of replacing the entire body.

I'm currently facing a scenario where I can't tell the javascript where to render it's dom

@wayneashleyberry oh the tangled webs we weave! I'm sure there's a solution, but it's hard to say without seeing your code. Feel free to email me at<EMAIL_ADDRESS>with details and I'll be happy to help.
I'm going to close this issue because I think specifying an alternative replacement element is off the table.

is it possible to stop the body swapping somehow in turbolinks:before-render? If so, people could use event.data.newBody to replace some elements themselves.

That's an interesting idea @MSchmidt. However, I'd rather we didn't encourage people to pick and choose elements to replace. The beauty of just replacing the <body> is that you don't need to worry about specific elements or fiddle with the DOM.
Of course, you can always modify event.data.newBody in turbolinks:before-render and perform any custom replacement you wish. I just wouldn't recommend getting carried away ;-)

A lot of third party plugins would just work of this was an option

FYI Workaround to not re-send static elements
<%= permanent :header do %>
  <%= render 'layouts/header' %>
<% end %>
... dynamic things go here ...
<%= permanent :footer do %>
  <%= render 'layouts/footer' %>
<% end %>

  # do not re-render and re-send permanent page content when navigating via turbolink
  # data-turbolinks-permanent tags only stay around if they are exactly the same, so we fill them with javascript
  def turbolink_permanent(id, &block)
    anchor = content_tag(:div, "permanent #{id}", "data-turbolinks-permanent": true, id: id)
    return anchor if request.env["HTTP_TURBOLINKS_REFERRER"]
    html = capture(&block)
    anchor << content_tag(:script, "document.getElementById('#{id}').innerHTML = #{html.inspect};")
  end

My use case is that I'd like to keep iframes dynamically attached inside the body laying around. For example, GTM preview and debug, LivePerson, etc. Often times some tools that set all this up do not have public JavaScript interfaces in order to recreate them. Also, you can not detach and move iframes around using the before-cache and before-render events because moving iframes around like that is just not a thing, even all the hacks are out of data, Chrome & Safari. So instead, I'd like to explore swapping the only child we have in the body, a page wrapper.

For anyone interested, my app was on v5.1.0 tag and this was my diff below. I just did a build with this change and added the built dist file to my app's vendor/assets/javascripts folder. I'm not going to use this in production, but I can say it is WONDERFUL to have the GTM Preview & Debug iframe now hanging around on each Turbolinks visit.
--- a/src/turbolinks/snapshot_renderer.coffee
+++ b/src/turbolinks/snapshot_renderer.coffee
@@ -61,7 +61,9 @@ class Turbolinks.SnapshotRenderer extends Turbolinks.Renderer
       replaceableElement.parentNode.replaceChild(element, replaceableElement)

   assignNewBody: ->
-    document.body = @newBody
+    docRoot = @getRootElement document.body
+    newRoot = @getRootElement @newBody
+    docRoot.replaceWith(newRoot)

   focusFirstAutofocusableElement: ->
     @findFirstAutofocusableElement()?.focus()
@@ -89,3 +91,6 @@ class Turbolinks.SnapshotRenderer extends Turbolinks.Renderer

   findFirstAutofocusableElement: ->
     document.body.querySelector("[autofocus]")
+
+  getRootElement: (node) ->
+     node?.querySelector '.my-PageWrapper'

@metaskills, did you have success with your patch?  Were there any unforeseen issues with this approach?

I totally did. No issues for me either. Just know I only used it in local development and our staging servers. Never had a need to ship the patched version to prod but it did work like a champ.

Hi everyone,
my $0.02: instead of patching the Turbolinks build, I suggest overriding the prototype for assignNewBody function. Patching the Turbolinks build will prevent you from updating Turbolinks itself whereas overriding the function lives in your codebase and worst case will stop working in future releases (in case there's a method rename or a refactoring for example).
The code:
Turbolinks.SnapshotRenderer.prototype.assignNewBody = function () {
  var newBody = this.newBody;
  var currentBody = document.body;

  // Custom logic to replace DOM Elements here...
  // ...
};

Turbolinks.start();
....

I have a use case for targetting an element other than body:  I have some CSS animations on a container element which kick in when its class changes, but these get bypassed when the whole body gets swapped out.  Being able to only swap the #main element, which is a child of the container, would avoid the CSS animations on the container being interrupted/reset.


"Not a valid data type or _FillValue type mismatch" when using NC_BYTE

Hi, when I used ncmpi_def_var(..,NC_BYTE,...) and ncmpi_put_vara_all(...,MPI_BYTE), it will throw a error "NetCDF: Not a valid data type or _FillValue type mismatch". And when I change the datatype "BYTE" to other datatype like "INT", the error is gone. How can I fix it if i want to use "BYTE" datatype? Thanks.

I think you want to take this to the parallel-netcdf team. The ncmpi_ functions are not from netCDF, they are from parallel-netcdf. (https://trac.mcs.anl.gov/projects/parallel-netcdf)
And I also have noticed that the 1-byte types don't work in pnetcdf. So please do report that bug and I hope they get it fixed.

Thanks for the reply. I have figure it out that starting from PnetCDF 1.7.0, MPI_BYTE does not correspond to any internal data type used in NetCDF/PnetCDF APIs. And changing MPI_BYTE to MPI_SIGNED_CHAR or just use ncmpi_put_vara_schar() can fix this problem.


[Disaster Dashboard] Binning histogram to latest year

This PR:

Adds a server endpoint that filters observation series to data for a specific year.
Use that endpoint to have histogram tiles only show data from 2022.

This allows us to pre-bin the data used in the histogram tile to a specific year, as a quick workaround to the rendering issues seen when trying to show histograms for long historical timeseries.
Allowing for multiple types of binning (by decade, year, month) and either allowing this to be set in a config or dynamically chosen based on the data can come in a future PR.
Current:

Proposed:

Merging for now to see results on autopush, will address comments in followup PR


Append missing optional parameters documentation to README.md

This PR appends missing optional parameters documentation to the main README file, so that the folks who are new to this dbt package is aware of them. Currently you have to click on the title of of each one to see what they are. Addresses #76 .
For future:

This doc is getting to be a pretty long list, so it may be helpful to divide them up for easier maintainability and readability.
It may be beneficial to look into docs generating library rather than manually editing the README if this package grows significantly.

@clausherther I'm open to suggestions on a better way to document sigma_threshold_upper and ...lower. Anyway, please review the rest of the changes and let me know if you have any feedback. Thanks!


Add GPU support for RNN/LSTM models

RNN models can now be run with both the NervanaGPU backend (fp32 and fp16 support), Cudanet backend (fp32) and CPU backend (fp32 and fp64).


Get version by 'func --version'

fix #150

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@dd2cb89). Click here to learn what that means.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##             develop     #153   +/-   ##
==========================================
  Coverage           ?   60.53%
==========================================
  Files              ?       50
  Lines              ?     1566
  Branches           ?      171
==========================================
  Hits               ?      948
  Misses             ?      558
  Partials           ?       60

Impacted Files
Coverage Δ

...re/maven/function/handlers/CommandHandlerImpl.java
68.42% <50%> (ø)

...unction/handlers/FunctionCoreToolsHandlerImpl.java
85.71% <77.77%> (ø)

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 dd2cb89...4c9f267. Read the comment docs.


ob run loses GHC warnings

ob run does not show GHC warnings. Even if it did, the running app may produce logging output that could quickly hide them in the terminal window. This may indicate we need a different command that focuses on error reporting over running the app. Or we need something more advanced.

ob run should handle these situations.

the running app may produce logging output that could quickly hide them in the terminal window.

This is a general inconvenience with using ghcid and nothing specific to obelisk per se. I think obelisk could handle it better though; for example, ob run could capture the standard output (of frontend and backend libraries) and display them somehow ensuring (not sure yet how) that it doesn't scroll out the ghcid output.

Yep.  This isn't a top priority, but it's well within the scope of ob run.

Note that by default ghcid doesn't run the --test if there are warnings. This must be enabled with -W. A very simple (and also not very satisfactory) solution would be to remove that (see https://github.com/obsidiansystems/obelisk/blob/8dca44efd8b8b5d638b178c1be4ced9b3e3fd16c/lib/command/src/Obelisk/Command/Run.hs#L121) and/or provide an option for ob run that decides.

#86 is a better title. ;)


Unable to import github repo due to auto_init

Expected Behavior
Should be able to import an already created github repo and then run terraform apply without it wanting to recreate the repo.
Actual Behavior
In our terraform, we set the argument auto_init = true. Recently, there was a commit which changed the behavior. Before I was able to import an already created github repo into terraform state and then run apply, but now, it wants to recreate it, due to the ForceNew, which has been added. So, I can't safely import a repo.
auto_init:          "" => "true" (forces new resource)

For now, I have pinned to v1.1.0 and then was able to proceed and had the expected behavior.  It just wanted to modify the single argument.
auto_init: "" => "true"

References
https://github.com/terraform-providers/terraform-provider-github/pull/135
Version
Terraform v0.11.7
Affected Resource(s)
github_repository

Hi @gabrielsyapse
the behaviour you described is (unfortunately) expected since you're importing an existing repository and the GitHub API doesn't tell us whether the repository was auto-initialized, so we have no way of knowing whether to set auto_init to true or false when importing that resource.
We have discussed some long-term plans on improving the (currently limited) important functionality, but I'm afraid there isn't much better solution other than setting auto_init = false in your config after importing that resource for now.
Prior to the 1.2 that field appeared updatable, but was in fact ignored, which may have caused some confusions and bugs. So the previous behaviour was actually wrong and now is fixed.
I'm going to leave this open for reference, but it needs to be addressed at higher level (helper schema / core) and there's a lot of work currently underway related to 0.12, so I wouldn't expect this to be implemented before shipping that version later this year.

@radeksimko Can you be more specific regarding the workaround? I've tried several options and the only one that avoided the recreate is to remove the flag from my module. But then I don't know how to accomplish an auto_init. What are the steps to auto_init on create and also avoid subsequent recreations?

Our decision was to add a lifecycle of ignore_changes to auto_init.

My sincere apologies to everyone! 😑I drew conclusions before trying to reproduce it as it looked very similar to some other bugs I saw in the wild in the past.
Basically I was under the impression that we just set auto_init to false by default on import/read, but that's apparently not happening. There's currently no workaround except what @sstarcher mentioned.
I will raise a PR with patch and aim to get it shipped in 1.3.1.
Bear with me, please.

Sorry again for the overlook from my side.
Just a quick update: PR to fix this was just raised in https://github.com/terraform-providers/terraform-provider-github/pull/154
Also I just realized (while testing my PR) that there is, in fact a workaround, and that is to omit the auto_init argument completely from the config:
provider "github" {
  organization = "terraform-providers"
}

resource "github_repository" "github_repository" {
  name               = "terraform-provider-github"
  description        = "Terraform GitHub provider"
  homepage_url       = "https://www.terraform.io/docs/providers/github/"
  topics = ["terraform-provider", "github", "terraform"]
  private            = false
  has_issues         = true
  has_wiki           = false
  has_downloads = true
  allow_merge_commit = true
  allow_squash_merge = true
  allow_rebase_merge = true
  default_branch     = "master"
  archived           = false
}

$ terraform init

Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "github" (1.3.0)...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.github: version = "~> 1.3"

Terraform has been successfully initialized!

$ terraform import github_repository.github_repository terraform-provider-github
github_repository.github_repository: Importing from ID "terraform-provider-github"...
github_repository.github_repository: Import complete!
  Imported github_repository (ID: terraform-provider-github)
github_repository.github_repository: Refreshing state... (ID: terraform-provider-github)

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

github_repository.github_repository: Refreshing state... (ID: terraform-provider-github)

------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.


bug fix:Can't get field comment

If I want to get the comment of a Edge I failed because the Comment field not defined in the Descriptor. I fix it in https://github.com/facebookincubator/ent/pull/244.
I'm not sure if we need such an operation,please review it.Thanks!

And I found the same problem in Field package, fixd in https://github.com/facebookincubator/ent/pull/247

Hey, thanks for raising up this issue.
It's not a bug.  The Comment exists for historical reasons, and it's not used by entc (ent codegen) - no need to export it in the Descriptor.

Hey, thanks for raising up this issue.
It's not a bug. The Comment exists for historical reasons, and it's not used by entc (ent codegen) - no need to export it in the Descriptor.

Got it! Thanks!


Crashing on Android after trying to create new Signature

Hello! I'm using liboqs-java on Android. I have compiled liboqs.so and libjni.so for Android x86_64 successfully and the modules are loaded successfully by Android. I copied the CMakeLists.txt made by Hatzen.
However, after my main activity loads, I try to call the example code from examples/SigExamples.java the app crashes on this line:
Signature signer = new Signature("DEFAULT");
Here's the logcat from Android (click here to see full crash log):
2021-01-28 11:14:44.807 2263-2263/io.trustwave.polarisclientapp A/olarisclientap: java_vm_ext.cc:577] JNI DETECTED ERROR IN APPLICATION: use of invalid jobject 0x7efd45de09d0
    java_vm_ext.cc:577]     from org.openquantumsafe.Signature$SignatureDetails org.openquantumsafe.Signature.get_sig_details()
2021-01-28 11:14:44.946 2263-2263/io.trustwave.polarisclientapp A/olarisclientap: runtime.cc:655] Runtime aborting...

Is this an issue with Android, the way I compiled liboqs, the Android version or an issue with the liboqs-java wrapper?
Thanks - Taimoor

Thanks for your investigations and trials. Just for clarification my code and the whole repository is not working as well. So this error is probably a duplicate of https://github.com/open-quantum-safe/liboqs-java/issues/11

Closing in favour of #11.


Implement pydocstyle rules

It's possible that we could collect the docstrings on the Rust side, then call out to pydocstyle. Or we could just re-implement the logic ourselves in Rust. The goal would be to enable adopting ruff for users of flake8-docstring.
See: https://github.com/PyCQA/pydocstyle

Starting: #394, #395.

Wow you blitzed through these! The rules section of the README.md should be updated to reflect the latest coverage

Ah yeah, they're enumerated in that huge table (look for the DXXX codes), but the whole thing needs to be redone. Maybe for now I'll split that table into sections to make the rule sets clearer?

Oh, no that's my bad! I thought the check mark meant "implemented" and the DXXX codes needed a check.

As a follow-up though, is the best way to activate pycodestyle to manually enable those error codes? Or is there an "on-switch" for the plugin as a whole?

Oh that's great feedback... If the check mark confused you, then it's my bad, not yours :) Will think on that.

Yeah, the best way to activate (for now) is to manually enable the error code. I'm going to improve this.
Here's an example from Polars that I was (coincidentally) just writing up: https://github.com/pola-rs/polars/pull/5151#issuecomment-1279765121


fix(franka_hw): include cstdint in franka_hw/resource_helpers

franka_hw wouldn't build for me because it couldn't find type uint8_t, this fixes it.
cc: https://github.com/lopsided98/nix-ros-overlay/issues/382

I think this should go in resource_helpers.h instead


Possibility to add input groups?

I am using input groups for stylizing and was wondering if/how hard it would be to implement them into this.
Excellent work so far!

Well they were never implemented because of email support for input elements. I am curious your use case? Are you trying to make an element look like an input or something?

Yes, just for easily transitioning between input and view forms for the user. Simply styling preferences. Makes sense to not be included if it bugs out the email program.

After some more browsing it seems there's some trickery available to display rounded corners in Outlook.
https://gist.github.com/elidickinson/9424116
If I knew how to implement these things I would definitely help you out but for now I'm just stuck researching and using.


Client Allocation Request for: Starry sky in Yunnan

Client Allocation Questions
Core Information

Name: Starry sky in Yunnan
Website / Social Media: https://ah22192341-1.icoc.vc/
DataCap Requested: 5TiB
Addresses to be Notarized: f3roqgq2iyh5rrzkfdipcw4vpn7pj5b2vx4m2vxbi6t7rj7aodaccuglaeaersukth34clwwknbkgez6eah4da
Notary Requested: Rin-huang

Client Allocation Questions
Core Information

Name: Starry sky in Yunnan
Website / Social Media: https://ah22192341-1.icoc.vc/
DataCap Requested: 5TiB
Addresses to be Notarized: f3roqgq2iyh5rrzkfdipcw4vpn7pj5b2vx4m2vxbi6t7rj7aodaccuglaeaersukth34clwwknbkgez6eah4da
Notary Requested: Rin-huang
请问能否提供一下贵公司Filecoin +项目负责人的联系信息？ 邮箱或者微信都可以，谢谢！
Can you provide the contact information of the person in charge of your company's Filecoin + project? Email or WeChat is fine, thank you!

hey @1am5UP3RasM4R10
<EMAIL_ADDRESS>WeChat:13169628872

This user’s identity has been verified through filplus.storage


Code from external modules not correctly transpiled

Eg on the client side async/await from kCore remains in app code, could be linked to:

https://github.com/babel/babel-loader/issues/293
https://github.com/babel/babel-loader/issues/149
https://github.com/webpack/webpack/issues/1643

Replacing all async/await is not sufficient, then we get errorslike:Uncaught SyntaxError: Use of const in strict mode.

Different things have been tested without success:

use include to add our module paths to the webpack config of babel-loader

using relative or absolute path without symlinks using fs.realpathSync

use include to add our module paths to the webpack config of vue-loader
similar as above
remove our modules from the exclude pattern like /.*node_modules((?!kCore).)*$/
process everything with babel-loader in project including node_modules

raises some issues on leaflet plugins

set option resolve.symlinks: false

The sole solution that seems to work is to integrate module files into app files so that babel correctly transpiles it.


fix(curriculum) Split Cat App Step 12 into two parts

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

This is the non-controversial half of #47149

Sorry for the noise, I was editing via the web editor.
This seems to work when I test it via Gitpod.

Note that when you build the site, even on gitpod, there is a challenge editor that makes this much easier. See at: https://contribute.freecodecamp.org/#/how-to-work-on-practice-projects?id=using-the-challenge-editor
I've restarted the tests

Do we care if they delete the "cat photos" link below the p element? I can definitely see them "moving" the link by thinking they need to delete it even though we aren't telling them to. And then if they do delete it in this step and it reappears in the next step is that a problem we need to be concerned about?

Honestly? I'm not sure. I think that users who look at the forum for old hint may try to do it all in one step. I could go either way here.

I've helped a couple people on the forums on this step specifically, and I've noticed something else about this step that seems to be confusing some people. Up until this point, they've been nesting one thing entirely inside another, like:

CatPhotoApp

And that nesting has been the same for their text. Each sentence has been contained entirely within one set of tags. This step is the first time they need to wrap one specific part of the sentence in tags, instead of the entire thing. What I was noticing is that it seemed like not everyone understood that some tags can just go in the middle of text, to only apply to specific words of that text. I feel like if we change the way the directions are phrased, we'd be able to communicate this at least a little more efficiently.
Rather than describing it like:
' by adding a new anchor element.'
It could be described as:
' by starting a new anchor tag just before the word "cat" and placing the closing tag after the word "photos" and before the period.'
I know that's a little verbose, but anything that describes it more as wrapping the already existing words in an element, rather than just adding a new element inside the 'p' element, should help the people running into this.

That is way, way too verbose in my opinion.

@jeremylt Is this ready for review?

It's been ready for review for a while. I'm not sure why staff removed the ready for review tag.

Yes, it blocks the builds, but we are pretty quick - at this time only three languages have the responsive web design new enabled

Sorry for the delay here @jeremylt - I'm not sure I actually got the answer I was looking for. I was told...

Wait for the translations to be added to the new challenge - the PR will sync daily and the action will stop failing when translations catch up

Which seems to imply that the translations will be added to this PR. But I'm not sure how that works - I dunno, maybe they will. @ieahleen, can you shed some light on this for me? Do we want to wait for something like that or merge this with just the English and block deploys?

@moT01 the new files can't be imported in crowdin until this is merged. Once it is merged, it will be imported into crowdin.
The crowdin PR will fail initially, and sync daily on its own, until the translation is complete, and the translated files are downloaded into the crowdin PR, which then can be merged.
Naomi has created the scripts, and we have everything documented, for more info.

您好：    双换感谢您的来信，收到信后我会第一时间回复您，如需紧急处理请致电15809253357，谢谢！


Get reference/location of Subscription

It would be great of there was a function that given a Subscription returns the reference/location it points to.

Ok, this would be possible, but it would necessitate to keep the subscriptions table (on the Javascript side) forever. Unsubscribed entries could not be deleted because otherwise functions on the returned reference wouldn't be pure anymore.
Do you have a certain use case in mind?

Thinking a bit more about a possible implementation of such such a function: The mentioned problem about keeping old data around could be handled.
Nevertheless, I don't see the need of such a function, so I close this issue. If a good use is emerging I will reopen it.


test_user_prayer_status_change_answer.py:82: Исправить...

The puzzle 1206-3300b41b from #1206 has to be resolved:
https://github.com/blablatdinov/tg-quranbot/blob/0c942f98da8005c7401cc1a099b16201546ae240/src/tests/it/handlers/test_user_prayer_status_change_answer.py#L82-L82
The puzzle was created by Ilaletdinov Almaz on 02-Sep-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1206-3300b41b has disappeared from the source code, that's why I closed this issue.


Add namespace attribute on IngressRouteTCP service

What does this PR do?
Add a namespace attribute on IngressRouteTCP service.
Motivation
Allow to specify a namespace to reference a Kubernetes service from IngressRouteTCP.
More

[x] Added/updated tests
[x] Added/updated documentation

Cross namespace referencing is discouraged due to fishing, and security/accountability reasons.
Is there a use case where an IngressRouteTCP could not be created in the target namespace?
Also, this does not take into account that the target namespace may not be watched/allowed via RBAC, and the informers may not be up to date with the endpoints...

There is a long dicussion in Kubernetes tracker about this if you want to deep dive the subject: https://github.com/kubernetes/kubernetes/issues/17088 .
Nginx usage for solving this is interesting though: they have the concept of "merged Ingress": https://github.com/nginxinc/kubernetes-ingress/tree/master/examples-of-custom-resources/cross-namespace-configuration .

I think that if this was enabled by a feature flag, it would be fine.
--provider.kubernetescrd.crossnamespacereferences=true with a default of false would be enough.
It would keep the current behavior, and allow the defaults to be secure, and allow users to allow references if required.
This could be implemented to the ingressRoute and ingressRouteTCP crds IMO if that feature flag were implemented.

The namespace is already available for the services in IngressRoute, so we cannot introduce the option with the expected behavior without breaking.

LGTM after formatting fix.


Toolbar gets smaller

Firefox 63.0.1
OS: Windows 10
Basically in this version, when you apply shadowfox the toolbar (or whatever it's called) gets smaller.
I haven't looked at the code yet so i haven't seen any bugs.
Anyways, the screenshot of my current toolbar is this:
https://gyazo.com/97684062db89e928dee59af81914d1a3
while it clearly should be this:
https://gyazo.com/36f3c5f45b1025c36c615205f08aad5c]

Hi there @zCri -
Your second link is broken, but I assume this is just the density setting of Firefox.
See #213.
Feel free to re-open if not, but there's no css styling to shrink the toolbar in ShadowFox


env  compile failed  caused by  <immintrin.h>

Proposed changes
Issue Number: close #xxx

run buildall

run p0

could u update desc to explain which pr intro this issue?


alex's xml-fixes branch on upstream + update .gitignore

@alexrass @dustismo added tests in web to verify that dynmap.toXMLString uses the passed in XmlFormatter (EscapeFormatter). A jar was built with this change and uploaded to artifactory but the pull request was never merged. I'm going to merge this change unless any objections.


How to add custom menu buttons

Version
3.4.0
Development Environment
Windows 10
Current Behavior
All menu buttons are predefined menu: ['crop', 'flip', 'rotate', 'draw', 'shape', 'text', 'filter'],
Question
How can I add custom menu buttons? For example 'save'?

This is not a proper solution but you can do with JQuery or Javascript  by replacing HTML on load. For example:
 $('.tui-image-editor-header-buttons .tui-image-editor-download-btn').
replaceWith('<button class="tui-image-editor-save-btn" >Save</button>')

Replace Download button into Save and then attach event with addEventListener
document.querySelector('.tui-image-editor-header-buttons .tui-image-editor-save-btn').
addEventListener('click', this.prcoessSaveImage)

fucntion prcoessSaveImage(){
//your code
}

@arifhussain353
虽然你这种侵入性的方法很龊，更新以后的新版本，可能就不兼容了。
但是目前要想解决问题，还不得不这么做。
看不懂，你自己去翻译吧。

Yeah It should be able at least to rename standard buttons. Add a new one.

The download button opes a new tab . i don't want that new tab how to stop that ?

@GEMI
Currently adding menu button or something functional into TOAST UI Image-Editor UI via Image-Editor constructor's options parameter or certain API is not available.
If you have to create save button and add that button among TOAST UI Image-Editor's menu buttons, you should extend TOAST UI Image-Editor src/ui/template/controls.js or just add a button into after Image-Editor rendered.

Can you show the example?

Hi! I want to use the custom function on the download button  is it possible and how can I do that

I want to remove "Load" and "Download" Button  and the header text
Please have a look on the marked area of the below image

I want to remove "Load" and "Download" Button and the header text
Please have a look on the marked area of the below image

I removed the header all together by overriding the following CSS properties in my Vue project:
.tui-image-editor-header {   display: none; } .tui-image-editor-container .tui-image-editor-main {   top: 0; }

I want to remove "Load" and "Download" Button and the header text
Please have a look on the marked area of the below image

Seems slightly cleaner solution
const myTheme = {     "header.display": "none" }; var instance = new ImageEditor(document.querySelector('#tui-image-editor'), {      includeUI: {          ...          theme: myTheme,          ...      },     ... });

Hi. I want to save the edited image (without downloading it to the local system) in a storage system (maybe S3) and then save the image URL in database. How can I do that?

Hi. I want to save the edited image (without downloading it to the local system) in a storage system (maybe S3) and then save the image URL in database. How can I do that?

Hi. I want to save the edited image (without downloading it to the local system) in a storage system (maybe S3) and then save the image URL in database. How can I do that?

@singhkirtii  I'm looking for this solution as well. Could you figure it out?

Yes. You can fetch the image data using the editor's toDataURL() function. This data can also be converted into blob, if needed. Once you have the image data, you can send it to the server and then upload the dataURI/blob directly to S3.

Thanks mate. Understood

how do i can add 1 or more menu?

How to add one more menu item inti list with submenus

@eriksetiadi-pro  @vijaykuamrparelli
just add them in the menu
export default function App() {   const props = {     includeUI: {       menu: [**"shape", "filter", "text","crop","draw","rotate","flip","icon","mask"**],       initMenu: "filter",       uiSize: {         width: "1000px",         height: "700px"       },       menuBarPosition: "bottom"     },     cssMaxWidth: 700,     cssMaxHeight: 500,     selectionStyle: {       cornerSize: 20,       rotatingPointOffset: 70     }   };

I want to remove "Load" and "Download" Button and the header text
Please have a look on the marked area of the below image

Seems slightly cleaner solution
const myTheme = {
    "header.display": "none"
};
var instance = new ImageEditor(document.querySelector('#tui-image-editor'), {
     includeUI: {
         ...
         theme: myTheme,
         ...
     },
    ...
});

How can I remove only the title and keep up the buttons

Any suggestions on a React equivalent of this?

@Shane-Geary
There is no way to add a menu yet. We will decide after a discussion with the team.

How can i use this theme using html

@PrashantNandanvar
Menubar Position Top does not have a separate theme.
You can set the option by setting it to includeUI.menuBarPosition.top = 'top'.

@yuban00018
Would you like to use file-saver?

const logImageContent = () => {
const instance = refImage.current.imageEditorInst;
let dataUrl = instance.toDataURL();
console.log(dataUrl)
};
and add button  save and give the onClick ={logImageContent} you will get  bs64 data of image    and use it

@Shane-Geary There is no way to add a menu yet. We will decide after a discussion with the team.

Hi,
Is there any solution?


It is recommended to update SpringBoot and SpringCloud to the latest version

spring boot  → 2.3.0.RELEASE
spring cloud → Hoxton.SR5
I hope to update in the next release as the spring community progresses

we are working for it.


[Gssoc'21] Imporve the footer

Is your feature request related to a problem? Please describe.
I want to improve the ui/ux of footer as it is currently very dull.

@rupeshmohanty kindly review my PR


Bug in importing custom class

I tried example of Third-Party library file given on https://code.askimed.com/nf-test/assertions/libraries/
Getting below error:
groovy.lang.MissingMethodException: No signature of method: static MyWordUtils.capitalize() is applicable for argument types: (String) values: [world]
  Possible solutions: capitalize(java.lang.String)

Hi!
There was a typo in the documentation in the MyWordUtils.groovy example. The method capitalize was not defined as static. I updated the documentation as following:
class MyWordUtils {

    def static capitalize(String word){
      return word.toUpperCase();
    }

}

Moreover, we extended the example by the following process capitalizer.nf to provide a running example:
#!/usr/bin/env nextflow
nextflow.enable.dsl=2

process CAPITALIZER {
    input:
        val cheers
    output:
        stdout emit: output
    script:
       println "$cheers".toUpperCase()
    """
    """

}

The test file capitalizer.nf.test remains the same:
nextflow_process {

    name "Test Process CAPITALIZER"
    script "capitalizer.nf"
    process "CAPITALIZER"

    test("Should run without failures") {

        when {
            process {
                """
                input[0] = "world"
                """
            }
        }

        then {
            assert process.success
            assert process.stdout.contains(MyWordUtils.capitalize('world'))
        }

    }

}

Hi @lukfor , I have double-checked if everything works as expected per documentation, and it seems that it works as expected. I opened a minor PR with bits of documentation updates which I think should conclude this issue.

Thanks Iwo!


Apply end with new line and remove trailing spaces

About this change - What it does
Applies spotless to check for trailing whitespaces or absence a new line in the end of file. In case this check finds something it fails the build.
It also includes functionality for autofixing all the things, just make ./mvnw spotless:apply or mvn spotless:apply from project root folder.
The whole changeset except pom.xml is a result of mvn spotless:apply
The configuration itself is done in pom.xml at https://github.com/aiven/klaw/blob/f43e26c8548f2bfe179f4e96abad53c2b870e97d/pom.xml#L305-L322
// cc @programmiri , @SmuliS since I remember you mentioned similar issue

@snuyanzin closing this PR, as mentioned before FE is being written in react, and being on safe side for these source files.


Add functions to check ABI of eBPF collection

It's useful to do some basic checks on a Collection if there is a user space component. Basically,
let the user specific a list of MapSpec and make sure that they are present in the collection and have the right types. The same goes for ProgramSpec.
Open question: how to do this for pinned collections? In that case we do not have *Spec to work with.

Let's get some unsupported errors going for some of these syscalls.

@nathanjsweet I see these options, my preferred solution last:

Add another feature test for the object info syscall, return ErrNotSupported from LoadPinned* if they don't work. Kind of involved, another feature test.
Look at err, and decorate it if it is EINVAL. We can't know for sure that means the syscall isn't supported, since there are other things that might return this code.
Document on LoadPinned* that kernel 4.13 is required (I think this is already the case) and that EINVAL can mean that your kernel is too old.

Thoughts?