Laravel file manager doesn't show uploaded images in file manager

Please check the following instructions before submitting a bug :

Make sure you are using the latest version.
Make sure you read installation, integration, and upgrade document.

And provide the followings :

Operating system : Ubuntu 18.08
Laravel version : 6.0
Package version :2.2.0
Steps to reproduce your issue :

Install laravel
Install package
Config with Tinymce
Upload image from tinymce image button

Screenshots of browser console :

I have the same issue
Ubuntu 20.04
PHP8
Laravel 8
Package 2.2.0

Try running php artisan storage:link.

Yes, I did it while installation didn't solved the proble,

same issue, on shared hosting namecheap

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

if UniSharp laravel-filemanager adding '/storage' to you files, and its dont preview because path to file incorrect, use in filesystems.php config
'mediafiles' => [
'driver' => 'local',
'root' => public_path(),
'visibility' => 'public',
'url' => '', // url without any path
],
my files in public/mediafiles path, and this config help

how fix?

how fix?

Check routes; be sure that you have storage:link
it works for me

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

thank you so much....the problem "Invalid Proses Upload" is SOLVED...

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

Thank you so much. It was really helpful

Thank you so much. It was really helpful

Thank you so much. It was really helpful

Thank you so much. It was really helpful

it says links already created.
it was showing until recently but after the last delete image, the new image uploads stop showing

Change your env APP_URL configuration with same port of serve or your own domain.
Add storage:link too
I Solve my issues in my TinyMCE

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

This is working fine. Thanks

thanks

if UniSharp laravel-filemanager adding '/storage' to you files, and its dont preview because path to file incorrect, use in filesystems.php config 'mediafiles' => [ 'driver' => 'local', 'root' => public_path(), 'visibility' => 'public', 'url' => '', // url without any path ],
my files in public/mediafiles path, and this config help

👍

same issue on host, any suggestion?

Thank you so much

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

Thank you so much man

nếu UniSharp laravel-filemanager thêm '/storage' vào tệp của bạn và nó không xem trước vì đường dẫn đến tệp không chính xác, hãy sử dụng trong filesystems.php config 'mediafiles' => [ 'driver' => 'local', 'root' => public_path(), 'visibility' => 'public', 'url' => '' , // url không có đường dẫn ],
các tệp của tôi trong đường dẫn tệp công khai/tệp đa phương tiện và trợ giúp về cấu hình này

👍

nếu UniSharp laravel-filemanager thêm '/storage' vào tệp của bạn và nó không xem trước vì đường dẫn đến tệp không chính xác, hãy sử dụng trong filesystems.php config 'mediafiles' => [ 'driver' => 'local', 'root' => public_path(), 'visibility' => 'public', 'url' => '' , // url không có đường dẫn ],
các tệp của tôi trong đường dẫn tệp công khai/tệp đa phương tiện và trợ giúp về cấu hình này

👍

if UniSharp laravel-filemanager adding '/storage' to you files, and its dont preview because path to file incorrect, use in filesystems.php config 'mediafiles' => [ 'driver' => 'local', 'root' => public_path(), 'visibility' => 'public', 'url' => '', // url without any path ],
my files in public/mediafiles path, and this config help

👍

In laravel 7 how to fix the above error?

Issue: Uploaded Images Not Showing Preview in Laravel File Manager
If you're facing the problem of uploaded images not showing a preview or thumbnail in Laravel File Manager, it might be due to an incorrect image URL being generated. This can often be resolved by making a simple adjustment in your application's configuration.
Solution: Update the Filesystems Configuration

Locate the filesystems.php configuration file in your Laravel project. You can find it in the config directory.
Inside the filesystems.php file, look for an entry named 'public'.
In the 'public' entry, you'll find a 'url' setting that might look something like this:

'url' => env('APP_URL') . '/storage',
4. To fix the image preview issue, you can modify this setting as follows:
'url' => '/storage',
You're essentially removing env('APP_URL') . from the URL.
Final Steps: Clear Cache and Routes (If require)
After making this configuration change, it's a good idea to perform these two commands to ensure that your changes take effect:

Clear the cache:
php artisan cache:clear
Clear the routes:
php artisan route:clear
These steps should resolve the issue of uploaded images not showing previews in Laravel File Manager. Your images should now be displayed correctly.

Please note that modifying configuration files should be done with caution, and it's always a good practice to back up your files before making changes. This solution should help you improve the image preview experience within Laravel File Manager.

Change your env APP_URL configuration with same port of serve or your own domain. Add storage:link too I Solve my issues in my TinyMCE

I already had the storage:link set but APP_URL in my .ENV was wrong, as suggested above. Changing that to what was actually my site URL fixed the issue for me.

fixed it by just deleting the storage folder in public, and rerun : php artisan storage:link

This works for me.
Thanks :)

Can Unisharp handle logic like this? For example, I have 2 file choose options: one for choosing a background file and the other for choosing an author file. When the background file is selected, the file manager opens, and the user is directed to the background folder


Fix fake minimum capacity

Fixes two issues, one where the endpoint mailbox had an invalid capacity, data handles are just pointers to a the file, so its fine for them to be unlimited. The series mailbox isnt a big deal since most of the time you want a batchsize greater than 64 (internally the default of the actor buffer). Adding the optaschan removes the buffer and enforces the strong capacity.

JFYI I tested it locally (starting Alloy, disabling internet, waiting for some time, restarting Alloy, enabling internet back) and it works as expected, so this seems to fix what I have been facing.


With 2FA disabled, user should be able to remove last OTP token

Currently we don't allow user to remove the last token on the account.  If 2FA is disabled and the user wants to remove all tokens, they should be able to.

Current testing shows this not to be a problem.  Will reopen if I can replicate the issue at a later time


Init translation for redux lib

Summary
Use init function in redux to store a reference for translation
Ticket Link
MM-10331
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Has redux changes (https://github.com/mattermost/mattermost-redux/pull/475)
[x] Has UI changes

@enahum If it gets merged wouldn't it work from master?. Could I just force push to get redux from master for build?

You need to update it in package.json to point to the commit and also update package-lock.json if i’m not mistaken

Ya @enahum It does not work with force push. I didn't realise we point to commit in webapp and not to master makes sense though.

Removed redux update as master contains the commit now.


Handle provider error

Return the error from the provider to the UI so it can be displayed on the screen.  This is mostly for the new hardware wallets but will also work for the injected provider.
Resolves #106
hardware wallets
Ledger, trying to connect to RSK testnet using the RSK Ledger app. The error is set from the provider.

injected provider
The injected provider will always throw "User Rejected." because of this line in web3modal. This is pulled by a few files before it gets to the provider controller. I don't know if it makes sense to fix this in this pr.

Should say in the provider error that the user needs rsk app for mainnet and ethereum app for testnet?

@ilanolkies

Yes, customising the error would be good. This is the responsibility of the provider and put this ticket in: https://github.com/rsksmart/rLogin-providers/issues/19
I think a back button would be the best since there could be different reasons the provider failed. This gives the user the option to click the provider again or try a different one. I'll add it.

After rebasing, I have added a call to action (CTA) region to the errorComponent. When the provider throws an error, a button with "Start Over" is added allowing the user to start over.

This node can also be used with the server if it errors. The datavaut already has a way to retry when it fails. I don't want to clutter this PR, so I put in this ticket here: https://github.com/rsksmart/rLogin/issues/170


[Feature Request] Translate menu option

Add option to the Edit menu dropdown to translate all selected elements. This would bring up a dialog box to translate the x and y positions of the selected elements. Hitting ok would then apply the translations, adding or subtracting the x and y values from each element's x and y position
This would allow you to shift selected sections by a certain amount while preserving their relative positions to each other

Sure that makes sense. A more precise move than just multi-selecting elements and dragging them. 👍

New "Move" button added to the Layout Control (by scale, resize, and the others): https://github.com/nhmkdev/cardmaker/releases/tag/v.<IP_ADDRESS>-unstable.v.a5 (though that version needs a lot more testing!).


unable to install on ubuntu 16.04

SerialPort Version:  1.7.4

NodeJS Version: v8.9.3

Operating System and Hardware Platform: Ubuntu server 16.04 on x64

Have you checked the right version of the api docs?:  yes

Are you having trouble installing and you checked the Installation Special Cases docs?  yes

Are you using Electron and have you checked the Electron Docs?: not using electron

Summary of Problem
Error when trying to install serialport.
Steps and Code to Reproduce the Issue
Run npm install --unsafe-perm serialport as root.
I always run as root on this server (no lectures please).  I have been using serialport in this environment for years with no problem.  But I rebuilt the server from scratch using newer node version and I can't get past this error ...
><EMAIL_ADDRESS>install /archive/dev/apps/hvac2/node_modules/serialport
> node-pre-gyp install --fallback-to-build

node-pre-gyp info it worked if it ends with ok
node-pre-gyp verb cli [ '/root/.nvm/versions/node/v8.9.3/bin/node',
node-pre-gyp verb cli   '/archive/dev/apps/hvac2/node_modules/serialport/node_modules/.bin/node-pre-gyp',
node-pre-gyp verb cli   'install',
node-pre-gyp verb cli   '--fallback-to-build' ]
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| linux | x64
node-pre-gyp verb command install []
node-pre-gyp info check checked for "/archive/dev/apps/hvac2/node_modules/serialport/build/serialport/v1.7.4/Release/node-v57-linux-x64/serialport.node" (not found)
node-pre-gyp http GET https://node-serialport.s3.amazonaws.com/serialport/v1.7.4/Release/node-v57-linux-x64.tar.gz
node-pre-gyp ERR! UNCAUGHT EXCEPTION
node-pre-gyp ERR! stack Error: Cannot find module 'internal/util/types'
node-pre-gyp ERR! stack     at Function.Module._resolveFilename (module.js:536:15)
node-pre-gyp ERR! stack     at Function.Module._load (module.js:466:25)
node-pre-gyp ERR! stack     at Module.require (module.js:579:17)
node-pre-gyp ERR! stack     at require (internal/module.js:11:18)
node-pre-gyp ERR! stack     at evalmachine.<anonymous>:31:26
node-pre-gyp ERR! stack     at Object.<anonymous> (/archive/dev/apps/hvac2/node_modules/serialport/node_modules/node-pre-gyp/node_modules/tar/node_modules/fstream/node_modules/graceful-fs/fs.js:11:1)
node-pre-gyp ERR! stack     at Module._compile (module.js:635:30)
node-pre-gyp ERR! stack     at Object.Module._extensions..js (module.js:646:10)
node-pre-gyp ERR! stack     at Module.load (module.js:554:32)
node-pre-gyp ERR! stack     at tryModuleLoad (module.js:497:12)
node-pre-gyp ERR! System Linux 4.4.0-87-generic
node-pre-gyp ERR! command "/root/.nvm/versions/node/v8.9.3/bin/node" "/archive/dev/apps/hvac2/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /archive/dev/apps/hvac2/node_modules/serialport
node-pre-gyp ERR! node -v v8.9.3
node-pre-gyp ERR! node-pre-gyp -v v0.6.7
node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>
npm ERR! code ELIFECYCLE
npm ERR! errno 7
npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-12-11T08_24_31_217Z-debug.log

srv(~/dev/apps/hvac2/node_mod

Closing this for now because I think I am missing some gyp dependencies.

I just created a fresh directory and ran npm install serialport --unsafe-perm.  It installed serialport using a prebuilt binary.  So the problem has something to do with my npm module dependencies in my particular project.
I just deleted my node-modules/serialport directory and did a global install and everything works fine now.


ci: add integration tests for k8s 1.25

Fixes no issue
Description

add integration tests for kubernetes version 1.25 to ensure compatibility

Checklist

[x] PR is rebased to/aimed at branch develop
[x] PR follows Contributing Guide
[x] Added tests (if necessary)
[x] Extended README/Documentation (if necessary)
[x] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

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

Coverage data is based on head (54fff5a) compared to base (88407a9).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #786   +/-   ##
========================================
  Coverage    96.81%   96.81%
========================================
  Files           22       22
  Lines         1226     1226
========================================
  Hits          1187     1187
  Misses          39       39

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

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


New version: CloudFoundry.CLI.v8 version 8.7.2

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-01-27T06:45:47.4996335Z ##[error] Manifest Error: DisplayVersion declared in the manifest has overlap with existing DisplayVersion range in the index. Existing DisplayVersion range in index:  [ [VERSION, VERSION]]

(Automated response - build 669.)


Update swift tools version of Package.swift

When using this package via SPM, we encountered the error 'bringSubviewToFront' has been renamed to 'bringSubview(toFront:)' which we think is related to swift versions. Updating the swift version used in Package.swift to 5 as in the project, solves this problem.

Can this be merged in please


Ok so

Describe your problem here.
Ok so, does anyone know how to make that like when you lose, a random sound plays?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

function onGameOver()
playSound(sound:String, volume:Float = 1, ?tag:String)
end

Do you want it to be in conjunction with the default death sound or do you want to replace the death sound entirely?

function onGameOver() playSound(sound 1, tag) end
Replace sound with where the sound is placed in the files and tag with a name for the sound (it's just used for pausing the sound so it doesn't really matter).

Yes i know that, but what i want to do is that when you die, a random sound appears

Do you want it to be in conjunction with the default death sound or do you want to replace the death sound entirely?

No, i dont want to replace the death sound, i want to play a random sound when you die

local myTable = { 'sounda', 'soundb', 'soundc', 'soundd' }
function onGameOver()
playSound( myTable[ math.random( 0, #myTable - 1 ) ], 1, tag )
end
Didn't test so idk if it works

local myTable = { 'sounda', 'soundb', 'soundc', 'soundd' }
function onGameOver() playSound( myTable[ math.random( 0, #myTable - 1 ) ], 1, tag ) end
Didn't test so idk if it works

do i change the tag on the function thing?

local myTable = { 'sounda', 'soundb', 'soundc', 'soundd' } setPropertyFromClass('GameOverSubstate','deathSoundName',myTable[getRandomInt(1,#myTable)])

setPropertyFromClass('GameOverSubstate','deathSoundName',myTable[getRandomInt(1,#myTable)])

do i have to put that on the function game over?

setPropertyFromClass('GameOverSubstate','deathSoundName',myTable[getRandomInt(1,#myTable)])

do i have to put that on the function game over?

You can use in all the functions of preference I recommend put it in onCreate()

setPropertyFromClass('GameOverSubstate','deathSoundName',myTable[getRandomInt(1,#myTable)])

do i have to put that on the function game over?

You can use in all the functions of preference I recommend put it in onCreate()

ok ill try it out


Editor doesn't forward --rendering-driver option to child process when running project

Godot version
Godot Engine v4.0.beta1.official.20d667284
System information
Linux 5.18.6-arch1-1; OpenGL Renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
Issue description
I'm using ssh, X forwarding and VirtualGL to run Godot remotely. Vulkan is unavailable in this situation, but using OpenGL works quite well.
I'm running the editor as godot4 -e --rendering-driver opengl3
Running the project thru the editor fails, as --rendering-driver opengl3 is not passed to the child process.
Changing the render driver in the project settings will allow the project to run, but that makes a undesired change to the project, and I only want to use the OpenGL renderer while working remotely.
Should the editor pass arguments to child project processes? Are there other arguments that should be forwarded? Should Godot fallback to OpenGL automatically when Vulkan fails to initialize? Is there some other intended workflow for specifying render drivers I haven't found?
Steps to reproduce
Run the editor with --rendering-driver opengl3 arguments.
Run the project from the editor.
The running project will not use the same render driver as the editor.
Minimal reproduction project
No response

See https://github.com/godotengine/godot/pull/64874, which is supposed to have fixed this.

Related to https://github.com/godotengine/godot/pull/64874 (which is only about project manager → editor argument passing).
Passing CLI arguments from editor to running project can be risky in some cases, so it should only be done for select arguments such as --rendering-driver and --audio-driver.

Yes, you can change the rendering driver in the project settings. Make sure the Advanced toggle is enabled so you can see the setting in question.

I don't want to save this to the project file and commit it to version control. While it will be fine as a temporary solution, a better option would be nice.


Update upgrade.md

Add language to specifically call out network firewall changes necessary before upgrade.

Thanks for trying to make our users' lives easier!
Even though I understand the intention of this change, I don't agree with it.
We use semantic versioning in UCP and DTR to signal to users that:

The version is not compatible with older releases
There might be breaking changes
There might be different requirements

Given that the system requirements doc already lists all the minimum requirements to a version, we should not duplicate that information anywhere else.
This means the first step of the upgrade docs should be "make sure your cluster complies with the new system requirements (here's the link to check that out)".
There are two reasons for that:

Keeping information in two places makes things harder to maintain, and information becomes inconsistent over time
RAM and ports are only a subset of system requirements. There are a ton of other requirements users need to comply with like OS versions, clock synchronization, ...

I know that the current version of the docs already talks about checking RAM and disk space, so it might seem that firewall ports are only an extension to this information.
The information about RAM should not be there to begin with, so let's not continue expanding that section.
@n00tz are you willing to update this PR to clean up the whole section and make clear to users that they should check the system requirements?

@joaofnfernandes I've updated the section to more closely match the existing documentation with specific call out for port openings.

Thanks for addressing the feedback! Let's ship it.


Set variables in tasks without showing them

Take this sample task:
- [ ] (location:supermarket) buy the milk

In this case, the displayed result is something like:
[ ] supermarket buy the milk

where supermarket has a light-grey background.
I'd like to set the variable to the task, without showing it.
Is it possible?

Could you explain what the output would look like?

The desired output is:
[ ] by the milk

Ah so you want to completely hide the metadata. This could probably be done with a bit of DVJS where you modify the display text to strip out metadata.
The plugin is effectively in maintenance mode as the author is working on a successor plugin so this likely won't be picked up.

Ok thank you for your answer.

You could hide the inline metadata in comments.
- [ ] %%(location:supermarket)%% buy the milk
See forum post: https://forum.obsidian.md/t/hide-tasks-metadata/53255


How to choose HAWQ version

Hello, i want to reproduce results from HAWQV1, V2 and V3 versions. How can i understand which HAWQ version i'm using

Hello, i want to reproduce results from HAWQV1, V2 and V3 versions. How can i understand which HAWQ version i'm using

hello, i am a new comer in this field. did you find the solution?


Any chance this could work with fzf-lua in Neovim?

https://github.com/ibhagwan/fzf-lua

Fantastic! Very happy with the result. This is what I ended up with (using lazy.nvim):
{
  'nanotee/zoxide.vim',
  cmd = { 'Z', 'Zi' },
  keys = {
    { '<leader>fz', ':Zi<CR>', desc = '[F]ZF [Z]oxide CD' },
  },
  init = function()
    vim.g.zoxide_use_select = 1

    -- If no args are given to Neovim,
    -- open `Zi` on launch.
    if vim.fn.argc() == 0 then
      vim.defer_fn(function()
        vim.cmd 'Zi'
      end, 0)
    end
  end,
}

Sincere thanks!

hi,
If I understand correctly, the above configuration should work bith just zoxide.nvim and fzf-lua right? I am trying to use with Nvim 0.10.3 and I am getting error messages like these:
Error executing vim.schedule lua callback: vim/_editor.lua:0: nvim_exec2(): Vim:Error executing Lua callback: .../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:48: nvim_exec2()..function zoxide#zi, line 1: Vim(echoerr):The fzf.vim plugin must be installed
stack traceback:
	[C]: in function 'cmd'
	.../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:48: in function <.../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:16>
	[C]: in function 'nvim_exec2'

Would be great to have this working with fzf-lua...
thanks!

Just tried this with a minimal config, it should work if vim.g.zoxide_use_select = 1 is set correctly

so sorry! My bad, totally forgot to set that variable...
It works wonderful!
thanks


move Atan, Acosh, Asinh, Atanh to datafusion-function

Which issue does this PR close?

Relates #9285
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Marking as draft as I think this PR is no longer waiting on feedback. Please mark it as ready for review when it is ready for another look

merging this quickly to keep the train going and minimize potential conflicts


0.12 reports invalid cert where 0.11 succeeded

Bug Report
After upgrading tonic from 0.11.0 to 0.12.2, gRPC connections fail with InvalidCertificate(UnknownIssuer) for the exact same server endpoint.
Platform
Windows
Crates
tonic
Description
A very trivial repro, comprising just this:
use tonic::transport::{Channel, ClientTlsConfig, Uri};

#[tokio::main]
async fn main() -> Result<(), tonic::transport::Error> {
    let uri = "https://zec.rocks:443/".parse::<Uri>().unwrap();
    let tls = ClientTlsConfig::new().domain_name(uri.host().unwrap());
    let channel = Channel::builder(uri.clone())
        .tls_config(tls)?
        .connect()
        .await?;

    println!("Hello, world!");
    Ok(())
}

Succeeds when using tonic 0.11, but fails on 0.12.x.
I have the minimal repro ready to cargo run at this repo: https://github.com/aarnott/tonic_fail_repro (main branch works, broken branch doesn't). The only difference between them is the tonic version.
Expected (0.11 behavior)
Hello, world!

Actual (0.12.x behavior)
Error: tonic::transport::Error(Transport, ConnectError(Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) }))
error: process didn't exit successfully: `target\debug\gRpcTest.exe` (exit code: 1)

In the original project that led to this report, I was getting transport error instead of InvalidCertificate. But in both cases, just upgrading tonic as described above is the only thing that causes it to fail.

I expect this is the same issue I ran into with this upgrade, specifically this entry in the 0.12.0 changelog:

BREAKING CHANGES

Removed implicit configuration of client TLS roots setup (#1731)

This was originally undocumented in the 0.12.0 release notes; the line was added later in #1781.

The fix is to use one of these methods:

ClientTlsConfig::with_native_roots
ClientTlsConfig::with_webpki_roots
ClientTlsConfig::with_enabled_roots (newly added in 0.12.2 by #1866, as a side-effect of fixing breakage caused by #1731)

Confirmed. Thank you!


--version doesn't show the version

This is just a minor annoyance :)
% gitu --version
gitu 32fde9c

While this is pretty good from a developer perspective, a user who wants to check if there's an update, needs to check git commits. I'd suggest something like this:
% gitu --version
gitu v0.26.0 (32fde9c)

That's peculiar, It's supposed to print either a version:
gitu on  master ❯ gitu --version
gitu v0.26.0

or if built from master, it should try describe the version
gitu on  master ❯ gitu --version
gitu v0.26.0-4-g93c3857

Where did you install it from?

Where did you install it from?

I installed a pre-compiled binary from the releases page.

Damn
Thought I had fixed it and released a v0.27.0
Turns out it fails to describe latest tag when running CI...
./gitu --version
gitu v0.26.0-8-g8300bd6

:facepalm:
This was after adding:
https://github.com/altsem/gitu/blob/8300bd605ff9acdc6ed6962f2c728a8c79815b4f/.github/workflows/release.yml#L98-L99

After downloading commit 8300bd60, clearly release 0.27.0, I got something different on ubuntu 22.04 than experienced by @TLINDEN :
$ gitu --version
gitu v0.26.0-8-g8300bd6

... got a version number, but it looks like to wasn't incremented.  So, it looks fine to me with a reasonable oversight on the numbering,


Push notification not received in iOS.

I implemented all the steps given in plugin. And Testing Notification from Firebase Console. Receiving Notification On Android but not in iOS. Permission is granted for push notification.

@devduttnetsutra
Please provide flutter doctor -v, iOS version. Can you also check if onLaunch and onResume are getting called while running on iOS ?
Thanks.


Book card - link behavior

when rollover the cover thumbnail, the title will turn into it's rollover stage, so people know that it will lead to the book's page when clicking on the cover or title
click on the author will open a filtered library page of that author's books

click on the author will open a filtered library page of that author's books
has not been fixed

@xinyil We have a separate issue now for author link - see #89. That functionality requires Solr functionality, which hasn't been implemented yet in this branch.  Please test and accept this one independent of that.

@rlskoeser Thanks for the update!
Also note that titles and images are not aligned.

We have to be careful with conversions and limit it to 6 decimal places because certain browsers show no difference between 2-5.d.p. Browsers also have different default styles that can affect the calculation of fonts and percentages. In some cases the same percentages will display differently in different browsers.
We are using ems, as Px have accessibility issues, so I am hesitant to simply use px for everything even though it would be easier to adapt exact measurements. I can use the converter, but just be aware that there could still be some variation on the calculated style.

As far as I understand, browser default to 16px = 1em.
If someone changed the conversion in browser to a larger px scale, it should be enlarged, and this is exactly why we use ems!

@kevinglover is there anything still to be done on this one?  I can't tell from the conversation; the one item previously needed has been handled as a separate issue.


Upgrade the C++ client to 3.5.0 for some bug fixes

Fixes https://github.com/apache/pulsar-client-python/issues/199
Fixes https://github.com/apache/pulsar-client-python/issues/193
Upgraded the pulsar-client-cpp dependency to 3.5.0, which has the fixes for them. Then add relevant unit tests.

@merlimat @shibd @RobertIndie Could you take a look?


Change [ PersonCard & PersonListPanel ] to [ PatientCard & PatientListPanel ]

Refractor the existing AB4 classes (PersonCard, PersonListPanel, etc) to new classes PatientCard, PatientListPanel.

Closed due to refactoring discussion as at milestone v1.2.


Accesion based mapper fails with OutOfMemoryError

Out of memory error occurs.
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
	at java.lang.Class.getInterfaces(Class.java:856)
	at java.lang.Class.getGenericInterfaces(Class.java:913)
	at java.util.HashMap.comparableClassFor(HashMap.java:351)
	at java.util.HashMap$TreeNode.find(HashMap.java:1874)
	at java.util.HashMap$TreeNode.getTreeNode(HashMap.java:1889)
	at java.util.HashMap.getNode(HashMap.java:576)
	at java.util.HashMap.get(HashMap.java:557)
	at net.sourceforge.ondex.core.memory.MemoryONDEXGraph.storeRelation(MemoryONDEXGraph.java:400)
	at net.sourceforge.ondex.core.base.AbstractONDEXGraph.createRelation(AbstractONDEXGraph.java:191)
	at net.sourceforge.ondex.core.EntityFactory.createRelation(EntityFactory.java:242)
	at net.sourceforge.ondex.mapping.lowmemoryaccessionbased.Mapping.createRelation(Mapping.java:503)
	at net.sourceforge.ondex.mapping.lowmemoryaccessionbased.Mapping.createRelationsOnResults(Mapping.java:395)
	at net.sourceforge.ondex.mapping.lowmemoryaccessionbased.Mapping.start(Mapping.java:250)
	at net.sourceforge.ondex.workflow.engine.Engine.runMapping(Engine.java:396)
	at net.sourceforge.ondex.workflow.engine.PluginProcessor$4.run(PluginProcessor.java:128)
	at net.sourceforge.ondex.workflow.engine.PluginProcessor$4.run(PluginProcessor.java:126)
	at net.sourceforge.ondex.workflow.engine.PluginProcessor.execute(PluginProcessor.java:83)
	at net.sourceforge.ondex.workflow.engine.BasicJobImpl.run(BasicJobImpl.java:110)
	at net.sourceforge.ondex.WorkflowMain.main(WorkflowMain.java:216)
	at net.sourceforge.ondex.OndexMiniMain.main(OndexMiniMain.java:7)

Test workflow and data available under knetminer/test/mapping_bug/git_issue_30/
The input OMA data might have malformed accession datasources or ids.

@josephhearnshaw, some paths have changed:
FASTA and GFF3: 2#2 The argument is invalid -- The file /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_pep_all.fa does not exist and is required to do so for Fasta File. Absolute path: /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_pep_all.fa Absolute path to a FASTA input file with protein secuences
FASTA and GFF3: 2#2 The argument is invalid -- The file /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_gene_protein_mapping.txt does not exist and is required to do so for Mapping File. Absolute path: /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_gene_protein_mapping.txt Absolute path to a mapping input file which provides mapping relationsship between the GFF and the FASTA file. It should contain two columns: 2) gene id and 4) protein id
FASTA and GFF3: 2#2 The argument is invalid -- The file /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_genes.gff3 does not exist and is required to do so for GFF3 File. Absolute path: /home/data/knetminer/species/fungi/fusarium_2020/fungi/organisms/fusarium_culmorum/ensembl/fusarium_culmorum_genes.gff3 Absolute path to a GFF3 input file with 9 columns. It uses 1)chromosome id, 4)start, 5)end and 9)gene id and gene description i.e. "ID=PGSC0003DMG400030251;Name=""Conserved gene of unknown function"""

I cannot find those files, please fix their paths (new launching script is basePath).

With the new launching script and without the FASTA parsing step, it completed without errors, the only strange thing is it took almost an hour to produce a small 1.4Mb OXL. I'm attaching the output here, for future reference.
git_issue_30-out.zip


Implementing pagination to UserBlock

Feature description

This is the implenmentation proposal of UserBlock feature at #448
Now for each user there is an array of userblock that is saved in KVStore
"UsersBlocksStoreKey" -> []UserBlock
It should be split to a relationship associated to only one key so that query.FilteredPaginate can be used when querying.
Implementation proposal

KVStore relationship should change from one to all to one to one/one to few , that is
"UsersBlocksStoreKey-1" -> UserBlock-1
"UsersBlocksStoreKey-2 -> UserBlock-2
Show what UserBlockStoreKey would be
UsersBlocksStorePrefix + Blocker +  Subspace  -> [] blocked Users
So that user can query not only base on the blocker, but also subspace the user block.
However I am not sure if it is enough or we should add more store key to make that one on one. I have trouble comming up more possible key.

@HarleyAppleChoi In my opinion, It should be one to one relationship for paginating UserBlock. In the way you proposed is paginated by subspace, but not by  blocked user.
What I think it is better to use UsersBlocksStorePrefix  + Blocker + Subspace + BlockedUser.
This allows:

Query all user block objects by iterating over UsersBlocksStorePrefix
Query all user block objects created by a blocker by iterating over UsersBlocksStorePrefix + Blocker
Query all user block objects created by a blocker inside a specific subspace by iterating over UsersBlocksStorePrefix + Blocker + Subspace
Check if a user block exists or not easily and fast with O(1) time complexity.

@dadamu

Check if a user block exists easily and fast with O(1) time complexity.

It is O(1) only if blocker ,subspace and blockedUser are all provided. If subspace isn't provided, it would have O(n) time. Not bad...

@HarleyAppleChoi Yes, you are right. It assumes that blocker, subspace and blockedUser are all provided. I think there is only a case to check the user block exists or not when storing a new user block. Are there any other cases I lost?

I think you pointed all of them out @dadamu

@HarleyAppleChoi would you like to tackle this and implement it?
Usually what we do to introduce a new feature/improvement is

Checkout on master branch
Create a new branch with the following name convention:
your-name/the-feature-name  e.g apple/user-block-pagination-impl
Start your implementation
Open a PR when you've finished
After all the checks passed, you can request a review to any of us: me, Paul, Ricky

Feel free to ask anything to us, and take your time to explore, study and try out the code!


Fix rendering

Not using DynamicFlags::IS_VISIBLE flag on drawing masks.

Also fixed the shader compilation error on macOS.
layout (location = 0) in vec2 out_tex_coords; // consumes `out_tex_coords` from a vertex shader.
...
    vec4 color = texture(us_tex0, out_tex_coords); // uses texture instead of texture2D (deprecated)

I don't know if this works on Windows.

Ah ye, didn't notice I was using a deprecated function there. The name of the input variable doesn't matter though since i've linked them with the layout (location = 0) attribute from what I know.

Even though the layout is specified, the shader compiler on macOS warns (and panics) saying that “out_**” was not used. I don’t know why.

Huh interesting, well it doesn't really matter anyways.


filter collection with "groupBy" when keys can be null / undefined.

https://github.com/a8m/angular-filter/blob/91ae1bfe75a4e747c2c52eab2065565aeb39c97e/src/_filter/collection/group-by.js#L36-L43
Because of memoization, special values such as null or undefined converted to their string equivalent 'null' and 'undefined'.
e.g. I am trying to have an accordion-group whose heading is the name of the group, however I cannot test for null or undefined explicitly.
<accordion-group is-open="group.open" ng-repeat="(groupKey, groupData) in originalData | groupBy:radioButtonGroupBy">
  <accordion-heading>

  </accordion-heading>
...something with groupData...

Can you provide some fiddle/jsbin @dnozay ?
Thx.

will do.

http://jsfiddle.net/unn62n16/1/

Any changes with that issue?

Can you please add a conditional to       if(!isObject(collection) || isUndefined(property)) {
to test for property !== 'null' or undefined


v3: Update TUF to latest version

Signed-off-by: Asra Ali<EMAIL_ADDRESS>
Summary

Now that https://github.com/theupdateframework/go-tuf/pull/175 is merged (YAY!) I'm going to start merging in the v3 changes, starting with a light bump on the TUF version.
Can we open up a separate branch on this repo so we can keep the existing state until all the changes are merged and we can manually test everything? I propose a new branch, something likev3
Ticket Link

Fixes
Release Note

Thanks @ethan-lowman-dd, the delegation PR was really critical to getting these next PRs merged!

Looks good! I assume we've checked that all instances of data.Key have been changed?

I've compiled both binaries (which is also in CI), and also manually searched so I think so! Also a good push to have this merge to a separate branch. Mind if I create a v3-staging branch @dlorenc ?

Go for it!

Great, changed base!


Messaging behind assertResult should be used for tests built using Matchers

Distinguishing between the actual and expected results appears to be the point of assertResult. However, when a test is built using the DSL, these nicer messages are not returned.
"Error message consistency" - {
  val error1 = intercept[org.scalatest.exceptions.TestFailedException] {
    assertResult(3) { 2 }
  }

  val error2 = intercept[org.scalatest.exceptions.TestFailedException] {
    2 should be (3)   // No ambiguity here which is the expected result
  }

  "The idea behind assertResult should carry through to tests expressed using `should`" in {
    error1.message.get should equal(error2.message.get) // :(
  }
}

That is actually the intended design because it is hard for users to remember whether the left side or right side is actual or expected in the case of matchers or assert with === or ==. In the case of assertResult, it is it more obvious because you can think of assertResult(3) { 1 + 1 } as assert that the result is 3 when you evaluate { 1 + 1 }. Originally the name of that was expect(3) { 1 + 1 }, so it was even more obvious than it is now.
So instead of picking one side to be expected and the other to be actual, we just say left did not equal right, so you can always figure out which value was the left expression and which value was the right expression. This was discusesd here:
http://www.artima.com/weblogs/viewpost.jsp?thread=223156

I understand the difference between assert and assertResult. The issue here is that when a test is composed using the DSL, is it not evident which side represents the expected result?

Well, Yoda does use ScalaTest, and the opposite opinion would he express. Of course he might also have the opinion that your tests fail because you don't believe they could pass.
I do see your point that it is more natural to think "expected should be actual," but I don't think users always think that way. Not all users are native English speakers, for example. What I did therefore was try and use an error message where anyone could figure out which side each reported value was on, and that was to always place the values in the error message in the same order the variables or expressions appeared in the source code.
Note that this rule of the variables/expressions always appearing in the same order also holds for assertResult:
scala> assertResult(3) { 1 + 1 }
org.scalatest.exceptions.TestFailedException: Expected 3, but got 2

But it would not hold if the following were to produce Expected 3, but got 2:
scala> { 1 + 1 } should be (3)
org.scalatest.exceptions.TestFailedException: 2 was not equal to 3
....

Even in diagrammed assertions the values show up in the same order as they appear in the source:
scala> val x = 1
x: Int = 1

scala> val sum = 3
sum: Int = 3

scala> assert(x + x == sum)
org.scalatest.exceptions.TestFailedException:

assert(x + x == sum)
       | | | |  |
       1 2 1 |  3
             false

...

So that's the reasoning behind he design.

Excellent explanation, thanks for making the effort.
I take your point about the results being in the same order as they are in code. So I suppose I would have expected something like:
scala> { 1 + 1 } should be (3)
org.scalatest.exceptions.TestFailedException: The result was 2; 3 was expected

but this pre-supposes that the expected result is always on the right. Pleased with this, Yoda would not be.


Support anything in nested data structures

Would it be possible to extend anything support so it can be used in maps nested within a sequence?
We often have to check a function that returns a sequence of maps (e.g. JDBC queries that return a sequence of map rows). In many cases, we don't care about the exact value of some map value, such as autogenerated SERIAL IDs.
This test passes:
(fact "this passes"   {:x 1, :y 1} => (just {:x anything, :y anything}))

But this version, where the map is wrapped in a vector, fails:
(fact "this fails"   [{:x 1, :y 1}] => (just [{:x anything, :y anything}]))

An engineer at my company developed custom Midje checker that does exactly this and a bit more, including what you suggested in https://github.com/marick/Midje/pull/403#issuecomment-333672673.
We've are a bit reluctant to release it into the midje code-base as is; there are some minor rough edges to clean up. He is currently on vacation, but I've asked him for the go-ahead to post a gist with the checker code so you can reuse it. I'll keep you posted
Looking forward, we have hopes to clean up the checker implementation and add it to the core midje code.

May not be relevant, but I originally developed https://github.com/marick/structural-typing with the idea it would replace much of Midje's checking infrastructure. It was partly based on my years-too-late belief that testing frameworks erred by starting with equality as the fundamental operation. Instead, for maintainable tests of non-trivial data, the fundamental operation is applying a predicate to the actual value. Midje does that by letting => take a predicate as the right-hand side, but that produces crummy error messages.
The structural-typing library was an attempt to provide predicates that both produce truth values and also provide explanations -- good explanations -- when something goes wrong. It got the wind taken out of its sails when clojure.spec was unveiled, and then I exited the Clojure ecosystem. But I still think replacing Midje's ad-hoc extended-equality with something based on this library would at worst be a useful experiment.

@marick I'm sorry to hear you've exited the Clojure ecosystem. Does this mean that Midje is dead and we should not use it for new projects?

There are some people from Brazil who are supporting Midje, honestly with more company support than I had. It might be time for them to say Midje is now their project.
That's not advice about new projects. But I'd say Midje is safer to rely on than it was during the last two years of my involvement. It's probably safe to rely on it continuing to work.
For new projects, the decision comes down to this:

It seems clojure.test will continue to be a pretty minimal test framework, but...
... with increasingly more third-party tools and built-in support from tools like Leiningen.

Then we could ask:

how long will it take the clojure.test ecosystem to include the things you value about Midje?
will the clojure.test ecosystem will outstrip Midje in what it allows?

My personal opinion is:

the clojure.test ecosystem is hampered because core clojure people neither appreciate nor understand modern testing. So I doubt clojure.test is the route to really great testing.

Midje's stability as Clojure versions change shouldn't be a major worry. Midje was first written for Clojure 1.2. Clojure version changes since then required very few Midje changes. Given Hickey's emphasis on backwards compatibility, I expect that will continue to be true.

But there are important secondary issues. For example, Midje is weak at describing clearly how a big expected value differs from an actual value. I wanted to improve that. It was a big part of the reason I wrote the structural typing library. My goal was to integrate it into Midje's failure reporting. I gave up on it because clojure.spec, despite having much less of an emphasis on error messages, was the variant everyone would use.

Getting rid of Midje's deficiencies will probably require community involvement. The question of "should we keep using Midje" might turn into "do we value the Midje approach enough to add to it?"

Hey @pjlegato, as @marick mentioned, a few engineers at Nubank (including myself) have taken over supporting Midje. The test infrastructure for our 100+ engineering team is powered by Midje, so we are keen to see that it continues to run smoothly.
We don't currently have plans for any grand new features, but have invested time fixing a few bugs and making Midje more user-friendly where possible. We've published a few alpha releases that we've been using internally, and are hoping to cut a normal release in the coming weeks.
Looking forward I hope to invest some time profiling Midje to see if startup times can be improved. My colleague @rafaeldff has been playing around with better checkers for nested structures and built-in generative testing constructs; hopefully we can get these released in the future too. That said, it would be great to hear other peoples ideas!
Lastly, thanks Marick for continuing to offer background context and insights on PRs and issues; it has proven very valuable as we continue to improve Midje

To follow up on this, we've released a new library for checking nested data-structures that attempts to solve the problem described here: https://github.com/nubank/matcher-combinators
@pjlegato as you mentioned, the following doesn't work with midje checkers:
(fact "this fails"   [{:x 1, :y 1}] => (just [{:x anything, :y anything}]))

With matcher-combinators this can be solved:
(require '[midje.sweet :refer :all]
         '[matcher-combinators.matchers :refer [equals embeds]]
         '[matcher-combinators.midje :refer [match]])
(fact "the nested map can have extra keys we don't ignore during matching"
  [{:x 1, :y 1, :extra :ignore-me}] => (match [{:x anything, :y anything}]))
(fact "the nested map must have exactly the keys specified"
  [{:x 1, :y 1}] => (match [(equals {:x anything, :y anything})]))

In the example above still need to wrap the nested map with the strict equals matcher if you want to check the map exactly because the default matcher for maps is a looser embeds (similar to midje's contains)
matcher-combinators also give you nice diff messages when there are mismatches in results just like you asked about in https://github.com/marick/Midje/pull/403#issuecomment-333672673


AST: support availability on Windows

Enable Windows specific availability annotations in Swift.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @benrimmington

@swift-ci please test Windows platform

Build failed
Swift Test Linux Platform
Git Sha - 2214d7f54e365daabf3c48ff95eed9b8c02b2a2d

@swift-ci please test

@swift-ci please test

What happens when a version number is used?
The parser/runtime might allow:

#available(Windows 10, *) is always false on Windows.
@available(Windows 10, *)
@available(Windows, introduced: 10, deprecated: 11, obsoleted: 12)

I can add the additional test cases, however, I'm not sure that the versions make too much sense.  Microsoft has announced that Windows 10 is the last version.  Do we really want to have build version numbers here?  I think that can get confusing and unwieldy.  You would be looking at something like:
@available(Windows, introduced: 10.0.107763,1, deprecated: 10.0.19140.2)

I was just wondering what happens when someone tries using version numbers on Windows. Does the compiler crash? Or is there an error or warning? Or are version numbers allowed at compile-time, but ignored at run-time?

Parser::parseNewDeclAttribute

Parser::parseAvailabilitySpecList

Parser::parseExtendedAvailabilitySpecList

https://github.com/apple/swift/blob/c10064a698d2b6424353a83b216514855d668f41/stdlib/public/core/Availability.swift#L39-L42

Ah, okay.  I'll certainly add those test cases.  It shouldn't crash the compiler, merely fail (warning/error).  The version numbers aren't supported.

@swift-ci please test

This seems to cause some problems for SK-LSP.  I want to get the reviews taken care of for the change, but leave the merging to until after the SourceKit-LSP issues have been worked out.

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test

@swift-ci please test Windows platform

The additional tests have been added, I think that all the review comments have been addressed and SK-LSP has been updated, so optimistically merging this for now.


Add support for Offcanvas sizes (like offcanvas-size-lg, offcanvas-size-xl)

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
The Offcanvas component has a "fixed" width of 400px (adjustable via $offcanvas-horizontal-width) for any breakpoint.
It would be very useful to have different size options similar as Modal also has optional sizes.
Like:
offcanvas-size-sm (default 300px)
offcanvas (default 400px)
offcanvas-size-lg: 500px
offcanvas-size-xl: 600px
offcanvas-size-xxl: 700px
Proposed withs are just an example.
Motivation and context
This especially useful as screens tend to get wider and wider but one still wants to use a Offcanvas to hide some content by default; like an advanced filtering pane.

You appear to be making an effort to support the creation of the Offcanvas component inside the Bootstrap open source project. In the problem you brought up, it is suggested that support be added for several Offcanvas sizes, such "offcanvas-size-sm," "offcanvas-size-lg," "offcanvas-size-xl," etc.
The existing Offcanvas code could be changed to support these new size classes and the Offcanvas width could be adjusted as a result. To support the "offcanvas-size-lg" class, you might edit the Offcanvas code as shown in the following example:
.offcanvas-size-lg {
width: 500px; /* Change the width to 500px */
}
.offcanvas.show.offcanvas-size-lg {
 transform: translateX(0); /* Reset the transform property */
}
For the other size classes, you can also apply equivalent CSS rules. The JavaScript code for the Offcanvas must also be changed in order to handle these new size classes and toggle the proper class when the Offcanvas is opened.
Before sending a pull request, don't forget to test your changes properly and make sure they work on all popular browsers and gadgets.

No plans to change the width here ourselves—feel free to address this in your own overrides :).


Detect early and abnormal dcrd process shutdown

Avoids waiting for a 10m timeout in go test, that ultimately results in the test being killed without any debug information available read from stdout or stderr.

This helped me determine that dcrd was being called with --appdata set to a read-only directory, and dying before writing anything to the ipc pipe (or even closing it wtf).


Simplify cycleway crossings

NVDB maps cycleway crossings with roads as short way segments rather than just a node at the crossing. This is also legal in OSM and this is currently translated by the script. However, it's not a common way to map in OSM, and it does make cycleways inside cities very fragmented and thus leading to more work merging.
Maybe look into simplify this type of geometry and just node crossings instead.

I have seen both methods used for mapping in OSM. Some users take care to tag the short crossing ways as highway=footway + footway=crossing (or similar for cycleway), while most users do not tag the crossing segment in any special way. I think your proposal is ok and in line with majority of mappers, i.e. no footway/cycleway=crossing on the way.
I would only add a node at the intersection with highway=crossing if it is included from NVDB. Otherwise we would just be guessing what kind of crossing it is (markings etc). And it is not strictly necessary to add a crossing node each time a footway or cycleway crosses a (motor vehicle) highway.

This has now been implemented.


Fatal Exception: java.lang.UnsatisfiedLinkError

I am getting below crash for some devices like Gionee M7 power and Xiaomi Redmi 4a.
Fatal Exception: java.lang.UnsatisfiedLinkError
dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/mypackage.myapp-2/base.apk", zip file "/data/app/mypackage.myapp-2/split_config.arm64_v8a.apk", zip file "/data/app/mypackage.myapp-2/split_config.xhdpi.apk"],nativeLibraryDirectories=[/data/app/mypackage.myapp-2/lib/arm64, /vendor/lib64, /system/lib64]]] couldn't find "libsecrets.so"
       at java.lang.Runtime.loadLibrary(Runtime.java:367)
       at java.lang.System.loadLibrary(System.java:1076)
       at air.com.religare.iPhone.Secrets.<clinit>(Secrets.java:10)

Let me know if you need more information.
Please help

Hello @Sonampasi ,
it is working well for other devices ? What did you try to solve this issue ?
Thanks

Hi @ben-j69,
Thanks for the quick response.
Yes, it's working fine for other devices.
I am using abiFilters of the issue but still it's not working.
build.gradle(app)
android {
     defaultConfig {
          ndk {
                 abiFilters 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a'
           }
      }
}

Hello @Sonampasi ,
I don't think this filter will change anything because you are filtering but with the list of all abis so it should have no effect. In more restricting architectures will not allow it to work on some devices.
We apparently have no issue with this devices in our production app using Hidden Secret v0.1.2.
Do you have 100% of crash on these devices or it just occur sometimes ? It could be just an installation issue or something like this.

Hello @Sonampasi
I am having the same problems. Did you find a solution?
Fatal Exception: java.lang.UnsatisfiedLinkError dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.flirt.dating-m03hAqtxJtGEp-FQIe2dBg==/base.apk"],nativeLibraryDirectories=[/data/app/com.flirt.dating-m03hAqtxJtGEp-FQIe2dBg==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libsecrets.so"

Hello @iremalbayrak can I see your gradle file please ?

Hello @Sonampasi ,
I don't think this filter will change anything because you are filtering but with the list of all abis so it should have no effect. In more restricting architectures will not allow it to work on some devices.
We apparently have no issue with this devices in our production app using Hidden Secret v0.1.2.
Do you have 100% of crash on these devices or it just occur sometimes ? It could be just an installation issue or something like this.

It happens sometimes on these devices.
Now I am having this issue in more devices, mostly in android 6.0.1 (98%).
Xioami - Redmi 3S, Redmi 4 Pro
Samsung - Galaxy On7 Pro
LeMobile - Le 2
GIONEE - M7 Power

Hello @Sonampasi
I am having the same problems. Did you find a solution?
Fatal Exception: java.lang.UnsatisfiedLinkError dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.flirt.dating-m03hAqtxJtGEp-FQIe2dBg==/base.apk"],nativeLibraryDirectories=[/data/app/com.flirt.dating-m03hAqtxJtGEp-FQIe2dBg==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libsecrets.so"

No, not yet.

I checked on M1 and for me libsecrets.so can't be generated at all. Any suggestions why it can be? Other .so libraries used in project successfully built.

Currently having this trouble for Pixel 3 XL. any idea how to solve this?

I checked on M1 and for me libsecrets.so can't be generated at all. Any suggestions why it can be? Other .so libraries used in project successfully built.

There is a PR about M1, feel free to review it : https://github.com/klaxit/hidden-secrets-gradle-plugin/pull/46

Hello, I'm getting the same crash while using classpath "com.klaxit.hiddensecrets:HiddenSecretsPlugin:0.1.5"
Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.my.application-k3NGrJChpymO2ia7c4Gl_w==/base.apk"],nativeLibraryDirectories=[/data/app/com.my.application-k3NGrJChpymO2ia7c4Gl_w==/lib/arm, /data/app/com.my.application-k3NGrJChpymO2ia7c4Gl_w==/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]] couldn't find "libsecrets.so"
       at java.lang.Runtime.loadLibrary0(Runtime.java:1011)
       at java.lang.System.loadLibrary(System.java:1661)
       at com.my.application.Secrets.<clinit>(Secrets.kt:10)
       at com.my.application.MainViewModel.<init>(MainViewModel.kt:36)
       at java.lang.Class.newInstance(Class.java)
       at androidx.lifecycle.ViewModelProvider$NewInstanceFactory.create(ViewModelProvider.java:219)
       at androidx.lifecycle.ViewModelProvider$AndroidViewModelFactory.create(ViewModelProvider.java:278)
       at androidx.lifecycle.SavedStateViewModelFactory.create(SavedStateViewModelFactory.java:112)
       at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.java:185)
       at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.java:150)
       at com.my.application.MainActivity$viewModel$2.invoke(MainActivity.kt:42)
       at com.my.application.MainActivity$viewModel$2.invoke(MainActivity.kt:41)
       at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
       at com.my.application.MainActivity.getViewModel(MainActivity.kt:41)
       at com.my.application.MainActivity.initLanguageAndCountry(MainActivity.kt:184)
       at com.my.application.MainActivity.onCreate(MainActivity.kt:54)
       at android.app.Activity.performCreate(Activity.java:7110)
       at android.app.Activity.performCreate(Activity.java:7101)
       at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1214)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2922)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3047)
       at android.app.ActivityThread.-wrap11(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1777)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:166)
       at android.app.ActivityThread.main(ActivityThread.java:6861)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:450)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Any idea?

I got the same crash on my application on some devices.  99% of them are in the background.
@ben-j69 do we have any update on this issue?

@Sonampasi do you found any solution for this issue?

I'm having same issue:
Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/io.quarkux.drugindexplus-Ottf6qqwM4kTbogQ099KKQ==/base.apk"],nativeLibraryDirectories=[/data/app/io.quarkux.drugindexplus-Ottf6qqwM4kTbogQ099KKQ==/lib/arm64, /system/lib64, /system/vendor/lib64]]] couldn't find "libsecrets.so"

plugins {
    id "com.klaxit.hiddensecrets" version "0.2.1"
}

0% background, is there a solution or a clarification ?
thanks.

problem solved (I think) by adding this in build.gradle:
android{
  ...
  defaultConfig{
    ndk {
            abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
  }
}

apparently the problem occurred only in arm64 devices /lib/arm64, /system/lib64, /system/vendor/lib64.
sources:
https://medium.com/mobiwise-blog/unsatisfiedlinkerror-problem-on-some-android-devices-b77f2f83837d
https://developer.android.com/reference/tools/gradle-api/7.1/com/android/build/api/dsl/Ndk#abifilters
https://developer.android.com/ndk/guides/abis.html#sa

my answer might help you with R8


Major refactor of getting-started (w/readfiles)

Opening this to show how readfile would work instead of shortcode alone.

Will close #3 in favor of this approach based on discussion with @dcwangmit01

Fixed all comments. Okay to merge?


1.13.0 rc1: pachctl update pipeline Doesn't Enforce Parallelism Limits

What happened?:
I had an existing pipeline running with no parallelism spec set. I edited the JSON file for the pipeline and added a parallelism_spec with constant = 200. I then ran pachctl update pipeline and was able to successfully update the pipeline to that level of parallelism, despite not having an Enterprise token.
What you expected to happen?:
I expected to receive an error message informing me that parallelism greater than 8 requires an Enterprise token.
How to reproduce it (as minimally and precisely as possible)?:
Do what I did above. :)  Create a pipeline with parallelism < 8, then update the spec to have paralelism > 8 and run pachctl update pipeline
Anything else we need to know?:
Nope. :)
Environment?:

Kubernetes version (use kubectl version): 1.18.6
Pachyderm CLI and pachd server version (use pachctl version): 1.13.0-rc.1
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): AWS
OS (e.g. from /etc/os-release):
Others:

I just learned that update pipeline will also create the pipeline if it doesn't already exist. So I tested that scenario, and in that case update pipeline does fail with the expected error message.  Which isn't too surprising since it's likely directing to the create pipeline code path under the hood.

Fixed in #5923


Sql Vulnerability Assessment - role changes

Hi,
When running the assessment and setting baseline based on database principals and roles, I would like to verify that change to role of a principal will trigger a new notification and not be considered as part of the baseline.
As an example to what I mean, in the image below, the principal test1 will change to db_datareader, will a new notification be raised.

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

ID: 02495b5c-f888-b3fc-82e0-37350af6ae81
Version Independent ID: ff0899fe-800e-328a-1690-f0d911331837
Content: SQL Vulnerability Assessment - Azure SQL Database & SQL Managed Instance & Azure Synapse Analytics
Content Source: articles/azure-sql/database/sql-vulnerability-assessment.md
Service: sql-db-mi
Sub-service: security
GitHub Login: @barmichal
Microsoft Alias: mibar

@assaf-grth Thank you for the feedback. We are actively investigating and will get back to you soon.

@assaf-grth Thank you for the feedback. We are actively investigating and will get back to you soon.

@femi-msft @BharathNimmala-MSFT Can you please provide insight with this issue.

@femi-msft @BharathNimmala-MSFT Can you please provide insight with this issue.

@assaf-grth Sorry for the delayed response. Could you please clarify that by notification do you mean to say if we change the role of member principal from db_ddladmin to db_datareader, will it still show in scan of the vulnerability results? If thats the query, it depends on roles that we configure on the principal, and not all roles will have this failure. ddl_datareader is just a select on existing objects and hence could behave differently as compared to say db_ddladmin.
Please let us know if thee question is something else and we can discuss further accordingly.

@assaf-grth Sorry for the delayed response. Could you please clarify that by notification do you mean to say if we change the role of member principal from db_ddladmin to db_datareader, will it still show in scan of the vulnerability results? If thats the query, it depends on roles that we configure on the principal, and not all roles will have this failure. ddl_datareader is just a select on existing objects and hence could behave differently as compared to say db_ddladmin.
Please let us know if thee question is something else and we can discuss further accordingly.

In my case I have a principal with db_datareader role saved as basedline
If the role will change to db_datawriter or db_ddladmin, will future scans raise this change as a difference from the current baseline?

In my case I have a principal with db_datareader role saved as basedline
If the role will change to db_datawriter or db_ddladmin, will future scans raise this change as a difference from the current baseline?

@assaf-grth Yes the scans will raise this change if we change the roles as mentioned by you as they are differ from the baseline. Again we can approve these changes as baseline. Also we can set up periodic scan as per the same article and it will detect any vulnerability in the database on weekly basis.
Please let me know if this helps.

@assaf-grth Yes the scans will raise this change if we change the roles as mentioned by you as they are differ from the baseline. Again we can approve these changes as baseline. Also we can set up periodic scan as per the same article and it will detect any vulnerability in the database on weekly basis.
Please let me know if this helps.

Thanks for the update

Thanks for the update