Application fails to load levels

I don't know what I'm doing wrong, but Drizzle refuses to load anything.
I've tried every conceivable type of .txt in the rainworld world/*_levels directory, the RWLE sampler levels, and the arena settings. The app crashes every time.
I assumed that this just meant it used it's own format and just... didn't label it as such, but the application has no "New file" option nor a new file keybind (I assume; ctrl+N does nothing) so that's not possible to test.
Because it's a total crash I can't get the console output very easily as it just closes immediately after, but I eventually got this:

I'm on a underpowered Windows 11 laptop, and here's the contents of Drizzle's "about":

I would chalk this up to windows 10/11 incompatibility but I've never had a problem with that before, and I can run applications that are older than me on here just fine.
I already tried to follow the "run" instructions but since Drizzle.Tanspiler doesn't exist I had to assume that's not applicable to Git Releases.

I am having the same problem on my brand new Windows 11 Laptop, not sure what's going on.

it loads the levels that come with the editor just fine. (the ones in Data\LevelEditorProjects)
my fault was me being a dumbass and loading one of the output text files, not one of the level editor files.

oh wow that makes a lot of sense and it actually works


Update packages

The packages have been updated

@OlhaPeculiar Cold you please check on https://fortify-tools.vercel.app/ Thanks.

Everything is displayed correctly

Everything is displayed correctly

Thank you @OlhaPeculiar

@OleksandrSPV Maybe we could also remove dependencies duplications. I ran the command and saw a lot of changes.

@OleksandrSPV Maybe we could also remove dependencies duplications. I ran the command and saw a lot of changes.

Done here https://github.com/PeculiarVentures/fortify-tools/pull/215/commits/0cd44ae4cacdec63fe1b0be15797a8fdcff6ce90 @donskov


Host Error

The inject node with "/red/worldmap" as payload should be only "/worldmap" since that is the url where the map is.
Same thing apply in the function node before the worldmap node in the following line of the json object (url field) ->
msg.payload={lat:lat, lon:lon, name:"Mike", icon:"male", url:"<a href="/ui/#/1">IBM link"};
It should be without the "/red" part but I didnt fix it because I dont understand the purporse of it, since it would be a infinite loop of links.

thanks will have a look - the default on Bluemix is to use /red - but yes it should be more generalisable and work for both if possible.

Closing as finally fixed by using more relative paths so should work in more places.
see commit 5f3812a3686527f7b576e3c63503e3cd595abeb1


Fix/scrolling contents

Update to pull request https://github.com/wagoodman/dive/pull/473
This should fix the static-analysis failures in the pipeline.
I am not good at re-base, so opted to merge main into this branch to check if @mark2185's fix plays well with the current version of dive. Tested to work locally.

Hi, this fix does solve the scrolling error, but introduces a new problem:
The UI is now fixed to the initial size - Resizing the window leaves the stored amount of layers the same
Video


Exceptions/errors in Win32 application

Hi,
While maintaining an old Win32 application, I started noticing the following errors in the debugger's output window:
onecore\com\combase\objact\objact.cxx(836)\combase.dll!00007FFA56273BB7: (caller: 00007FFA56272A3C) ReturnHr(1) tid(e3c) 800401F0 CoInitialize has not been called.
onecore\com\combase\objact\objact.cxx(836)\combase.dll!00007FFA56273BB7: (caller: 00007FFA56272A3C) ReturnHr(2) tid(e3c) 800401F0 CoInitialize has not been called.
onecore\com\combase\objact\objact.cxx(836)\combase.dll!00007FFA56273BB7: (caller: 00007FFA56272A3C) ReturnHr(3) tid(e3c) 800401F0 CoInitialize has not been called.

Which was puzzling, because I was calling CoInitialize( nullptr ) at the top of WinMain.
A quick google suggested I should be calling CoInitializeEx( nullptr, COINIT_MULTITHREADED ) instead.  So I changed the code to call that.
Now I'm seeing a bunch of different errors:
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {00BB2761-6A77-11D0-A535-00C04FD7D062}.'.
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: 0x40080202: WinRT transform error (parameters: 0x0000000080040155, 0x0000000080004002, 0x000000000000001D, 0x000000000014EBC0).
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {EAC04BC0-3791-11D2-BB95-0060977B464C}.'.
onecore\com\combase\dcomrem\marshal.cxx(1111)\combase.dll!00007FFA56291094: (caller: 00007FFA562922FC) ReturnHr(1) tid(83bc) 80040155 Interface not registered
    Msg:[Failed to marshal with IID={EAC04BC0-3791-11D2-BB95-0060977B464C}]
onecore\com\combase\dcomrem\marshal.cxx(1032)\combase.dll!00007FFA56292329: (caller: 00007FFA56285E8D) LogHr(1) tid(83bc) 80040155 Interface not registered
onecore\com\combase\dcomrem\marshal.cxx(972)\combase.dll!00007FFA56285FFD: (caller: 00007FFA562851E8) ReturnHr(2) tid(83bc) 80040155 Interface not registered
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {00BB2761-6A77-11D0-A535-00C04FD7D062}.'.
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: 0x40080202: WinRT transform error (parameters: 0x0000000080040155, 0x0000000080004002, 0x000000000000001D, 0x000000000014EBC0).
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {EAC04BC0-3791-11D2-BB95-0060977B464C}.'.
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {00BB2761-6A77-11D0-A535-00C04FD7D062}.'.
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: 0x40080202: WinRT transform error (parameters: 0x0000000080040155, 0x0000000080004002, 0x000000000000001D, 0x000000000014EBC0).
onecore\com\combase\dcomrem\marshal.cxx(1111)\combase.dll!00007FFA56291094: (caller: 00007FFA562922FC) ReturnHr(3) tid(83bc) 80040155 Interface not registered
    Msg:[Failed to marshal with IID={EAC04BC0-3791-11D2-BB95-0060977B464C}]
onecore\com\combase\dcomrem\marshal.cxx(1032)\combase.dll!00007FFA56292329: (caller: 00007FFA56285E8D) LogHr(2) tid(83bc) 80040155 Interface not registered
onecore\com\combase\dcomrem\marshal.cxx(972)\combase.dll!00007FFA56285FFD: (caller: 00007FFA562851E8) ReturnHr(4) tid(83bc) 80040155 Interface not registered
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {EAC04BC0-3791-11D2-BB95-0060977B464C}.'.
onecore\com\combase\dcomrem\marshal.cxx(1111)\combase.dll!00007FFA56291094: (caller: 00007FFA562922FC) ReturnHr(5) tid(83bc) 80040155 Interface not registered
    Msg:[Failed to marshal with IID={EAC04BC0-3791-11D2-BB95-0060977B464C}]
onecore\com\combase\dcomrem\marshal.cxx(1032)\combase.dll!00007FFA56292329: (caller: 00007FFA56285E8D) LogHr(3) tid(83bc) 80040155 Interface not registered
onecore\com\combase\dcomrem\marshal.cxx(972)\combase.dll!00007FFA56285FFD: (caller: 00007FFA562851E8) ReturnHr(6) tid(83bc) 80040155 Interface not registered

I'm not using WinRT.  (At least not directly.)
They appear to be originating from a few calls I make to SHAutoComplete while handling the WM_INITDIALOG message in a dialog box.
Is this due to something I've screwed up, or have you screwed up?  :)

It's hard to say without a minimal self-contained repro. As this question is not specifically about C++/WinRT (or even WinRT) I think you'll have better luck sharing such a repro on https://stackoverflow.com/

If errors coming from WinRT aren't related to WinRT, what are they related to?
Here's a repo case:  Win32 C++ desktop application:
int WINAPI WinMain( HINSTANCE instance, HINSTANCE, LPSTR, int show )
{
	CoInitializeEx( nullptr, COINIT_MULTITHREADED );
	SHAutoComplete( nullptr, 0 );
}

Debugger output window contains:
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {00BB2761-6A77-11D0-A535-00C04FD7D062}.'.
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: 0x40080202: WinRT transform error (parameters: 0x0000000080040155, 0x0000000080004002, 0x000000000000001D, 0x000000000014F5D0).
Exception thrown at 0x00007FFA55D7A799 (KernelBase.dll) in OsoXMLMergeD.exe: WinRT originate error - 0x80040155 : 'Failed to find proxy registration for IID: {EAC04BC0-3791-11D2-BB95-0060977B464C}.'.
onecore\com\combase\dcomrem\marshal.cxx(1111)\combase.dll!00007FFA56291094: (caller: 00007FFA562922FC) ReturnHr(1) tid(3bf8) 80040155 Interface not registered
    Msg:[Failed to marshal with IID={EAC04BC0-3791-11D2-BB95-0060977B464C}]
onecore\com\combase\dcomrem\marshal.cxx(1032)\combase.dll!00007FFA56292329: (caller: 00007FFA56285E8D) LogHr(1) tid(3bf8) 80040155 Interface not registered
onecore\com\combase\dcomrem\marshal.cxx(972)\combase.dll!00007FFA56285FFD: (caller: 00007FFA562851E8) ReturnHr(2) tid(3bf8) 80040155 Interface not registered

These are C-style COM and Shell APIs, not WinRT APIs. Under the hood, much of the OS is built with WinRT and it happens to have a great error reporting capability that many subsystems use. That's why you tend to see WinRT in traces.
In this case, you're creating an MTA and then calling a shell API that is probably designed for an STA and lacks marshaling proxies. It fails because COM attempts to marshal some single-threaded internals on the MTA calling thread. SHAutoComplete bubbles up this failure by returning E_NOINTERFACE. If you instead create an STA with COINIT_APARTMENTTHREADED then SHAutoComplete seems to get further but returns E_INVALIDARG, presumably because it expects an HWND.
Anyway, this has nothing to do with the original error you cited - "CoInitialize has not been called". That indicates that CoInitialize/CoInitializeEx was not actually called at all (on the thread). Perhaps you're doing something slightly different in production.
I hope that helps, but again I'm not familiar with the Shell APIs and you'd probably do better on https://stackoverflow.com/.

Ah, ok.  That makes sense, I guess.
It appears SHAutoComplete is just completely broken now.  Calling CoInitializeEx( nullptr, COINIT_APARTMENTTHREADED ) results in an error claiming CoInitialize hasn't been called.  Calling CoInitializeEx( nullptr, COINIT_MULTITHREADED ) results in the above errors.  (All of this is happening on the main thread.)
I guess that'll never be fixed.
Anyway, thanks for the info.  :)

Did you try using CoCreateInstance with CLSID_AutoComplete instead of calling the API?


Reply-To parameter missing

Hi there, love this API, but seems to be extremely limited as to what you can do with it. The example only shows basic to, from, subject, and body parameters. I need to set a Reply-To value in the header, and there seems to not be a way to do this. Could someone confirm if this is missing or if I am just dumb and can't find it? If it is not an option, consider this a feature request. Thanks!

Hey @edgarwideman, I will get the example updated.
You can set the reply to by passing a reply_to body parameter. Like so:
    $resend->emails->send([
        'from' => 'Acme<EMAIL_ADDRESS>        'to' =><EMAIL_ADDRESS>        'reply_to' =><EMAIL_ADDRESS>        'subject' => 'Hello world',
        'html' => 'It works!',
    ]);

Awesome! You're the best! Thanks a ton. 🎉


Test the generated binaries

Check if the binaries that are created in CI actually work.
Basically download them and run them to see if they work!

on macOS we need notarization, otherwise the user has to bypass the security things

Can you make another issue @wolfv ?


Enable Screen Space Reflections (HDRP)

Ocean currently does not work with SSR in HD render pipeline.
Here's a screenshot with a ship and Crest, SSR enabled and no reflections.

Here's the same setup, just added a reflective quad underneath the ocean surface to capture the reflection.

Unfortunately I believe it is a hdrp limitation - no SSR on transparent materials.
https://forum.unity.com/threads/ssrr-on-a-transparent-or-translucent-object.408206/

@huwb It looks like they added it in HDRP 10. According to the changelog:

Added of Screen Space Reflections for Transparent materials

Ha thanks. Hopefull it will work then (when testing, definitely worth trying flat/calm water first). Can reopen this until one of us gets the chance to try it out.

I up this one, a tutorial/vid on SSR and Crest for HDRP would be a good start.

Closing this one as it is a duplicate of issue #613. Oops

Closing this one as it is a duplicate of issue #613. Oops


Add MixinExtras annotations to MixinsTranslator and MixinsDummy

MixinExtras is on its way to become a standard within Mixin circles, and it would be handy if people coming to ClassTransform from Mixin could use the MixinExtras annotations they feel comfortable with (for example @Local would become @CLocalVariable).
Relevant PRs:

Fabric: https://github.com/FabricMC/fabric-loader/pull/854
NeoForge: https://github.com/neoforged/NeoForge/pull/303

I have planned to add MixinExtras annotations to the translator.
I'm currently working on a @Share implementation for ClassTransform. I'm not sure which other annotations from MixinExtras I will implement since most of them can just be a @CRedirect or @CInject without any issues


Some video info not showing.

what info? @AdityaMishra135

This is normal. The video info is first fetched from the system media database, some of which may not have been recorded. In this case the app will try fetching the info via MediaMetadataRetriever then record them into the db once for all.  But if the info is failed to fetch, default data will be displayed for the lacked info of a video. This is not so important that we can retry with more approaches despite the performance influcence unless we have a better choice instead of MediaMetadataRetriever.

Whats better instead of media metadat


unrecognized template parameter 'logAnalyticsRetentionInDays'.

logAnalyticsRetentionInDays needs to be removed from the example ADO document
its not supported AND not used in the two other example files

hmm, nevermind. still getting the eror message
Current working directory: /home/vsts/work/1/s/landingzones/lz-platform-logging

Deploying main.bicep using create operation...
ERROR: unrecognized template parameter 'logAnalyticsRetentionInDays'. Allowed parameters: logAnalyticsAutomationAccountName, logAnalyticsResourceGroupName, logAnalyticsWorkspaceName, resourceTags, securityCenter, serviceHealthAlerts, subscriptionBudget, subscriptionRoleAssignments, subscriptionTags
##[error]Caller: 5 /home/vsts/work/_temp/azureclitaskscript1635994635337.sh, LineNo: 1, Command: az deployment sub create --location canadacentral --subscription 88358fdf-3ca9-4b73-b561-38f4934ab400 --template-file main.bicep --parameters serviceHealthAlerts='{
    "resourceGroup

removing theline from the template, seems to have resolved the issue

Looks like issue is related to #44

@KingBain can you check if you have the latest code?  We added this parameter in #44 and it's reflected in  https://github.com/Azure/CanadaPubSecALZ/blob/main/landingzones/lz-platform-logging/main.bicep#L185

updating the source code resolved the issue thanks.


add data attribute (data-key) for better testability

Hi,
there is no possibility to touch a search-parameter without using the 'param.name' if you use this for different languages in testing.
So I decided to use the 'param.key' which works perfectly and is unattached to the name.

Hi,
thanks for your contribution. Could you please explain a bit more why this change is needed? I don't know the data-key attribute.

The HTML-Code is too generic. You can't handle a click-point on testing.

Yes, you are right! Sorry for the inconvenience.

I have the same problem. The generated HTML is too generic and therefore I cannot create a JQuery selector that will trigger the test event action.

@wtczk BTW I think its better if you use one way bindings in the expressions, AFAICS the keys are unlikely to change their text when they are set.

On a second thought, 2 ways binding is fine, since the filters may change. So the commit seems fine.


how to change wiper menu right to left?

how to change wiper menu right to left?

At the moment we do not have this option, but a great idea dovandu, iriei add in the backlog for implementation.

available in version 1.1.0


React version

React version
Support of usage in list view
New "button class" property

In widget.config.xml, it doesn't read data from package.json. For example, widgetFriendlyName and description. Please read webpack.dev.js and webpack.prod.js.

Fixed that.


Import sqlite dependency got errors at gf v2.0.4

1. What version of Go and system type/arch are you using?
go version go1.17.8 windows/amd64
2. What version of GoFrame are you using?
v2.0.4
3. Can this issue be re-produced with the latest release?
yes
4. What did you do?
When i import the sqlite dependency by doc, it's
_ "github.com/gogf/gf/contrib/drivers/sqlite/v2"
then compile and got below errors
github.com/gogf/gf/contrib/drivers/sqlite/v2
C:\Users\yililong\go\pkg\mod\github.com\gogf\gf\contrib\drivers\sqlite\v2@v2.0.0-20220319145450-d1f76f3834e1\sqlite.go:109:17: d.DoSelect undefined (type *Driver has no field or method DoSelect)
C:\Users\yililong\go\pkg\mod\github.com\gogf\gf\contrib\drivers\sqlite\v2@v2.0.0-20220319145450-d1f76f3834e1\sqlite.go:144:19: d.DoSelect undefined (type *Driver has no field or method DoSelect)
Compilation finished with exit code 2
that because gf frame changed the fun name in the latest branch
Now, question is, i am using v2.0.4 , and how to import the matched sqlite version.
Thanks.

try go get -u github.com/gogf/gf/contrib/drivers/sqlite/v2@6ffdff70950eacc74cd91a3a00d8d385018437de

Yes, it works as you suggestion, tks
At last, I suggest that the contrib libs also should be released as the gf with same version, otherwise we will be confused.


[test] Rename moveonly{,wrapper}_to_copyable.sil.

Just a more specific test name since we are going to start doing actual move only stuff.
NFC.

@swift-ci smoke test and merge


Laravel 8 Sail Redis not assuming the default cache driver

Laravel Version: 8.38.0
PHP Version: 8.0.3
Database Driver & Version: N/A
Environment: Sail (Docker)

Description:
Laravel 8 and the dev environment is Sail - including Redis. The .env file:
 CACHE_DRIVER=redis .. REDIS_HOST=redis REDIS_PASSWORD=null REDIS_PORT=6379
Using the Redis facade functions, like
Redis::set( 'bar', 'The hole of the moon' );
using redis-cli is possible to find the value stored in cache
but using
Cache::put('bar2', 'baz', 100);
or even
Cache::store('redis')->put('bar3', 'Awesome', 100);
the values cannot be seen using the redis console.
Please note:
dd(env('CACHE_DRIVER'));
shows "redis" .
Steps To Reproduce:
In terminal
docker exec -it laravel_sail-app_redis_1 redis-cli
(after: sail up)
This machine has no local Redis installation, not even MySQL, only PHP- this is a fresh Ubuntu installation . The app is served by Sail / Docker.
Everything stored with Redis facade - replicants of Redis commands - works well.

Thanks @driesvints  good to know: there is no bug!!
It will be worth trying with a fresh app.
I've already post on Laracasts Forum and StackOverflow...

I have the same issue

@adellinocasas, @piterog

First, laravel uses different bases for Redis and Cache facades.
See config/database.php redis.default and redis.cache

Second, Laravel uses a prefix for Redis keys.
See config/database.php redis.options.prefix
Thirdly, the Cache facade uses a prefix for the key. Concatenate database.redis.options.prefix and cache.prefix
See config/cache.php prefix

Finally
To view cache values change database and find keys:
<IP_ADDRESS>:6379[1]> SELECT 1;
<IP_ADDRESS>:6379[1]> KEYS *bar*
1) "laravel_database_laravel_cache:bar2"
2) "laravel_database_laravel_cache:bar3"

laravel_database_ is database.redis.options.prefix
laravel_cache: is cache.prefix
bar2 your key


Consider switching to absolute imports for all collection paths

Our project files currently import collections using two import styles, relative and absolute, depending on the context. Generally, the imports are done as such:

relative imports for collections within the same module as the importing file
absolute imports for collections in a separate module from the importing file

Lets discuss the tradeoffs of other possible importing rules, make a decision, and change all of our imports to match up with the decision.

This issue was moved to apinf/platform#2058


The information placed is not displayed within "My Team"

Nice to greet you Stuar, I have the following problem: I have several users where, when filling in the location of where they will be in the week, it is not displayed in the "My Team" tab. I attached a reference image, hoping you can guide me to a solution.
Thank you very much and greetings.

That's very strange.  Is it just when you select Home/Casa?
Can other people see your presence in My Team?

If I grab the user and drop them into my pinned list, I see their selection with no problem. But within "My team" some selections are not displayed as I show you in the photo. I've already checked some things with the user but I can't find the problem.

If you refresh the app does it show?

Not yet, we currently have version <IP_ADDRESS>, if we do the update do you think it will correct the error?

There is a pre-release available at https://github.com/stuartridout/teamlink/releases/tag/v1.27-prerelease along with some other feature enhancements.   This is pre-release so be sure to try in a test environment.


Fix for rgw_support_bundle integration with cortx_support_bundle

Signed-off-by: Palak Garg<EMAIL_ADDRESS>Problem Statement

cortx_support_bundle not generating rgw support bundle

Design

Added rgw support.yaml

Coding
Checklist for Author

[ ] Coding conventions are followed and code is consistent

Testing
Checklist for Author

[ ] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[x] Testing was performed with RPM

Impact Analysis
Checklist for Author/Reviewer/GateKeeper

[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)

Review Checklist
Checklist for Author

[x] JIRA number/GitHub Issue added to PR
[x] PR is self reviewed
[x] Jira and state/status is updated and JIRA is updated with PR link
[x] Check if the description is clear and explained

Documentation
Checklist for Author

[ ] Changes done to WIKI / Confluence page / Quick Start Guide

/opt/seagate/cortx/utils/bin/cortx_support_bundle generate  -c yaml:///etc/cortx/cluster.conf -t file:///var/log/cortx/support_bundle -b SBag9s2g01 -m "Testing" --modules "rgw,utils"

[root@ssc-vm-g4-rhev4-0860 SBag9s2g01]# tar -xvf SBag9s2g01_e884506cadb150157e923ad8e4873ac4.tar.gz
SBag9s2g01/
SBag9s2g01/common/
SBag9s2g01/common/common.tar.gz
SBag9s2g01/summary.yaml
SBag9s2g01/rgw/
SBag9s2g01/rgw/rgw_SBag9s2g01_e884506cadb150157e923ad8e4873ac4_rgw.tar.gz
SBag9s2g01/utils/
SBag9s2g01/utils/SBag9s2g01_e884506cadb150157e923ad8e4873ac4_utils.tar.gz


Skip unit tests if docker executable not found

This matches the work we did in the vagrant provisioner.
Fixes: #314

👍


feat(path-filter): Filter blockdevice using custom udev rules

Signed-off-by: Abhishek Agarwal<EMAIL_ADDRESS>Why is this PR required? What issue does it fix?:
This PR fixes the issue - https://github.com/openebs/openebs/issues/3491
What this PR does?:
This PR adds extra dev links(apart from by-id and by-path) info which we get from the udev` probe.
Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::

Added custom udev rules for a disk: KERNEL=="sdb1",SYMLINK+="openebs_storage_02"
Relead the udev db using the command: udevadm control --reload
The new symlink is available in the udev output now:

P: /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1
N: sdb1
L: 0
S: disk/by-uuid/E48D-9C94
S: disk/by-path/pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0-part1
S: disk/by-label/ABHISHEK
S: disk/by-id/usb-JetFlash_Transcend_8GB_OWXSZQ7L-0:0-part1
S: openebs_storage_02
S: disk/by-partuuid/02a28704-01
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1
E: DEVNAME=/dev/sdb1
E: DEVTYPE=partition
E: DEVLINKS=/dev/disk/by-uuid/E48D-9C94 /dev/disk/by-path/pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0-part1 /dev/disk/by-label/ABHISHEK /dev/disk/by-id/usb-JetFlash_Transcend_8GB_OWXSZQ7L-0:0-part1 /dev/openebs_storage_02 /dev/disk/by-partuuid/02a28704-01
E: TAGS=:systemd:

Install ndm operator
Update the ndm config:
a. Exclude the disk with symlink: /dev/openebs_storage_02 using exclude path filter:- key: path-filter
  name: path filter
  state: true
  include: ""
  exclude: "/dev/loop,/dev/openebs_storage_02,/dev/fd0,/dev/sr0,/dev/ram,/dev/md,/dev/dm-,/dev/rbd,/dev/zd"

OUTPUT: Listing bds with kubectl get bd -n openebs doesn't list the above disk.
b. Include the disk with symlink: /dev/openebs_storage_02 using include path filter:- key: path-filter
  name: path filter
  state: true
  include: "/dev/openebs_storage_02"
  exclude: "/dev/loop,/dev/fd0,/dev/sr0,/dev/ram,/dev/md,/dev/dm-,/dev/rbd,/dev/zd"

OUTPUT: Listing bds with kubectl get bd -n openebs does list the above disk.
The bds are listed is it should have been:abhishek@abhishek-Mayadata:~$ kubectl get bd -n openebs
NAME                                           NODENAME            SIZE         CLAIMSTATE   STATUS   AGE
blockdevice-0db0a0b21ddbc52266b551d2d1c53791   abhishek-mayadata<PHONE_NUMBER>   Unclaimed    Active   4s
blockdevice-14065e0e32469367655092a3333cfe99   abhishek-mayadata   1024         Unclaimed    Active   102s
blockdevice-2345c8576f192616c18b8f9f19f2497e   abhishek-mayadata   536870912    Unclaimed    Active   102s

blockdevice-0db0a0b21ddbc52266b551d2d1c53791   abhishek-mayadata<PHONE_NUMBER>   Unclaimed    Active   4s is the one having the custom udev rule

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[x] Fixes - https://github.com/openebs/openebs/issues/3491
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #670 (80ee461) into develop (9f40337) will increase coverage by 0.13%.
The diff coverage is 73.91%.

:exclamation: Current head 80ee461 differs from pull request most recent head f9d1304. Consider uploading reports for the commit f9d1304 to get more accurate results

@@             Coverage Diff             @@
##           develop     #670      +/-   ##
===========================================
+ Coverage    44.83%   44.97%   +0.13%
===========================================
  Files           79       79
  Lines         3970     3991      +21
===========================================
+ Hits          1780     1795      +15
- Misses        2023     2029       +6
  Partials       167      167

Impacted Files
Coverage Δ

cmd/ndm_daemonset/filter/pathfilter.go
69.38% <50.00%> (-7.54%)
:arrow_down:

cmd/ndm_daemonset/probe/udevprobe.go
47.67% <100.00%> (+1.03%)
:arrow_up:

pkg/udev/common.go
88.23% <100.00%> (+0.93%)
:arrow_up:

pkg/udev/mockdata.go
67.12% <100.00%> (+0.45%)
:arrow_up:

pkg/udev/udev.go
90.00% <0.00%> (ø)

pkg/udev/device.go
100.00% <0.00%> (ø)

pkg/udev/monitor.go
80.00% <0.00%> (ø)

pkg/udev/enumerate.go
58.33% <0.00%> (ø)

pkg/udev/listentry.go
0.00% <0.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

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

@akhilerm could you review this PR?


4 add simple aggregations

Percentile ranks was not included yet because in order to get meaningful results we must have some idea of the range of the data being ranked.
We can perhaps build and request a basic percentile_ranks query after retrieving results for extended_stats which have min, max, avg and other stats.


Use ModelAdmin's Queryset for Searching

Thank you for this project. It works great so far!
In one of my projects, we are using a lot of customized base querysets (ie. overriding get_queryset) in the ModelAdmins. Eg. for filtering the objects based on permissions.
It would be very useful, if the queryset for searching would not be hardcoded to objects.all() but instead uses the ModelAdmin get_queryset method.
I would offer to create an according PR :)
Thanks!

Hi! Glad you like the project 🙌
Thanks for raising the issue - the hardcoded objects.all() is quite rigid. To keep it as customisable as possible, my instinct is to add a self.get_model_queryset(self, request, model_class, model_admin) method. Then, overriding that to use the admin's get_queryset, or whatever else, should be easy enough.
Feel free to raise a PR, otherwise I'll look to get something out asap 🙏

@ahmedaljawahiry I see you already created a PR. Thank you!
I wanted to prepare a PR a few days ago but had a hard time getting the tests running locally. It would probably make sense to write a section about that in the readme, if you want others to contribute :)

Thanks @maqnius - indeed lacking a "development" section in the readme, I'll look at getting this added.
I've merged that PR, and the get_model_queryset(...) method should be available in 1.1.0: https://github.com/ahmedaljawahiry/django-admin-site-search/releases/tag/1.1.0
To use the ModelAdmin's method, I'd do something like:
class CustomAdminSite(AdminSiteSearchView, admin.AdminSite):
    """Adds the AdminSiteSearchView to the default AdminSite"""

    def get_model_queryset(
        self, request: HttpRequest, model_class: Model, model_admin: Optional[ModelAdmin],
    ) -> QuerySet:
        if model_admin:
            return model_admin.get_queryset(request)

        return super().get_model_queryset(request, model_class, model_admin)

Let me know if there's any issues 🙏


"az pipelines runs artifact download" fail for containers that need to be downloaded as a zip file.

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Extension name (the extension in question)
az pipelines runs artifact download
Description of issue (in as much detail as possible)
I need to be able to download the "containers" from the build run artifacts as a zip file (the same as I can from the web UI).
However the above command fails with error "Artifact with name 'Android' was found, but is of type 'Container'".  I've tried mapping into the container to download an individual file, but that also fail with a can't find file error.  I have also tried adding on "Android&$format=zip" that the rest api uses in it's download URI, but this also fails.
I've also posted this issue to Stock Overflow.
https://stackoverflow.com/questions/60942336/az-pipelines-runs-artifact-download-fails-with-error-artifact-was-found-but

pipelines

@BrianMouncer - I have raised the same issue on our repo azure/azure-devops-cli-extension. I am closing this issue and you can track the issue - https://github.com/Azure/azure-devops-cli-extension/issues/982 on our repo for further updates.

Yes, we are using the Publish Build Artifacts task, and after several attempts, I am still unable to get "az pipelines runs artifact download --run-id" to work with any files that are in a "container".
I did a quick experiment today, and if I switch our build system to use PublishPipelineArtifact@1 task, then the AZ Clie command will work and download the files, though no longer as a zip file, but as an uncompressed set of files on disk.
I could adapts our scripts to this easy enought, but the blocking issue is that PublishPipelineArtifact@1 does not seem to be able to upload files from multiple agents to the same artifact name.
Our build system is distributed, so our windows binaries all builds on different agents.
e..g one agent will builds X64, while others builds arm and x86 binaries.
in the current system, each uploads a folder to an atrifact names "Windows", which later gets pulled down as a whole, and used to create our SDKs multi-platform nuget package.
The documentation on PublishPipelineArtifact@1 is a bit light.
Can you tell me how to configure PublishPipelineArtifact so that it can upload multiple parts to the same artifact name?
without hitting the "##[error]Artifact XYZ already exists for build ####" errors?
thanks...

@geverghe, @BrianMouncer had a fair point could we clarify this, reopen?
az pipelines runs artifact download --artifact-name $name --path ~/Downloads --run-id $run_id
gives back a Artifact with name 'mock-name' was found, but is of type 'Container'.
I know that moving forward one should use pipeline-artifacts instead of build-artifacts, but would be great to be able to download old artifacts from the command line too.


fix(compiler): do not force module kind if piping babel

Closes #767

Pull Request Test Coverage Report for Build 1913

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 91.491%

Totals

Change from base Build 1907:
0.03%

Covered Lines:
1026

Relevant Lines:
1073

💛  - Coveralls


Upgrade to actix-web 1.0

At the moment it's in Beta, but it might be a good idea to start testing now.

Done in #62


Broken documentation links to Publish

Hello,
We are just investigating bringing MediatR into our project, and I noticed some broken links around the notification publish strategies. https://github.com/jbogard/MediatR/wiki#publish-strategies. It looks like the samples/examples have been removed from the repo?

What a co-incident, I'm in the same situation and would be happy to explore samples  as well.

A recent change broke all of the samples, so I'm in the process of getting them added back.

Thank you, @jbogard.


[FEATURE] Configure ruff for backend.

Summary
NA
Description
NA
Use Case
No response
Alternatives
No response
Affected Area
Backend

To be done after #206 .

we should also adopt to UV for package management.

we should also adopt to UV for package management.

Create an issue maybe? so that we can have discussion on its pros and cons.


build_library: add extract_docs()

Related https://github.com/coreos/coreos-overlay/pull/1055

Updated.

One lat nit and then LGTM


WIP - use istanbul-require-hook

This is just another exploratory PR.
Trying to figure out the best way to accommodate custom preprocessors.
istanbul-require-hook was mentioned here: https://github.com/bcoe/nyc/issues/70.
I think it shoes great promise. Especially if altered to include hook combining/chaining with something similar to what was done here https://github.com/bcoe/nyc/pull/65
I think we are nearing a real solution. Until a clear winner emerges from the solutions proposed in  https://github.com/bcoe/nyc/issues/70, I think I will fork istanbul-require-hook with some changes specific to what we need.

Two things:

It's called istanbul-lib-hook, not istanbul-require-hook, FYI
I think that it would be worthwhile to use pirates instead, as istanbul-lib-hook will (hopefully) soon just be a wrapper around pirates.

@ariporad - yep, this was an exploratory thing I did when that whole discussion kicked off.
I am going to be opposed to integrating pirates in any projects until https://github.com/ariporad/pirates/issues/5 is resolved.

@jamestalmage: Fair. I've just posted an update in that issue, in the interest of now flooding this one.


Runelite command/highscore kc bug

Type
Incorrect behavior
Operating System
Windows
OS Version
11
Bug description
When I type !kc lunar chest, it shows that I have less kc than on the highscores, this is the problem for almost 1 week.
Screenshots or videos

RuneLite version
Newest
Logs
No response

Go do one more KC or use a ring of wealth to check the boss log.

Did you open 2 chests on a non-RuneLite client, such as on mobile? !kc only updates based on seeing your kc change, it doesn't fetch from the hiscores.

Did you open 2 chests on a non-RuneLite client, such as on mobile? !kc only updates based on seeing your kc change, it doesn't fetch from the hiscores.

Yes i did some kills on mobile. But that was more than only 2 kills.

But that was more than only 2 kills.

It's not that it only counts kills done on RuneLite, just that it can only update the count when you do a kill on RuneLite. So like I said, if you go do one more kc on RuneLite it should be accurate again for you.

But that was more than only 2 kills.

It's not that it only counts kills done on RuneLite, just that it can only update the count when you do a kill on RuneLite. So like I said, if you go do one more kc on RuneLite it should be accurate again for you.

Ah I understand now, the last time I did some kills were on mobile so that should be it! Thanks!


Please, remove source map url from CDN version

Please, remove this: //# sourceMappingURL=./dist/svg-injector.map.js from the<EMAIL_ADDRESS>version … or add the map.

The map is actually there it's just the path that's wrong. Should be //# sourceMappingURL=./svg-injector.map.js


Create an issue template similar to what is used in the grails-data-mapping plugin

This will be great for prompting users to supply the information required to reproduce and fix the issue.
Example issue template: https://github.com/grails/grails-data-mapping/blob/master/ISSUE_TEMPLATE.md

Code has been reviewed and merged.
Marking as 'Done' and closing.


Refactor of Talk Rating

This PR does a few things:

Create a TalkRating base class which has some standard functionality like saving the new rating.
Create a TalkRatingContext, which defines what strategy to use
Create a Provider which calls the TalkRatingContext
Override some standard Illuminate functionality in relation to created at and updated at functions.

Follows #503 .

Thanks @BackEndTea


Server api

Please review and approve, thx.

Once your PR is merged, I'll cover @KocaMio to finish the client side.

What is PR?

PR stands for pull request.


error/warning on singleton BND

if both ends of a BND are not present in the VCF sent for genotyping, svtyper will silently ignore the one that is present. It would be nice if this at least printed a warning message.

Totally agree. I have not had much time for development work lately, but this will make it in.


MM-19674: use respondXXX in http handlers

Summary
There was some funky error handling in http functions, streamlined it, should now consistently use respondErr when returning errors in http handlers.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-19674

@DHaussermann there is not too much you can test here other than for general regressions. Most of the changes affect the error paths, but technically most of the http endpoints are affected.

Regression tested some server side error cases:

Regression tested some server-side error cases

Summary length
Description length
User permission revoked
Jira instance unavailable
Project has become un-available

@levb In some cases when validating the length, there are extra characters appearing in the validation text. I'm not entirely sure it was introduced by this PR. Should this be a separate issue?

@DHaussermann fixed

Codecov Report

Merging #500 into master will increase coverage by 0.34%.
The diff coverage is 17.13%.

@@            Coverage Diff             @@
##           master     #500      +/-   ##
==========================================
+ Coverage   33.62%   33.97%   +0.34%
==========================================
  Files          37       37
  Lines        4535     4501      -34
==========================================
+ Hits         1525     1529       +4
+ Misses       2863     2823      -40
- Partials      147      149       +2

Impacted Files
Coverage Δ

server/atlassian_connect.go
0.00% <0.00%> (ø)

server/instance.go
57.14% <0.00%> (ø)

server/instance_cloud.go
8.16% <0.00%> (ø)

server/instance_server.go
10.11% <0.00%> (ø)

server/issue.go
12.52% <0.00%> (+0.82%)
:arrow_up:

server/stats.go
11.76% <0.00%> (-0.09%)
:arrow_down:

server/user.go
21.00% <0.00%> (+0.80%)
:arrow_up:

server/user_cloud.go
0.00% <0.00%> (ø)

server/user_server.go
6.36% <0.00%> (ø)

server/http.go
12.79% <39.28%> (+0.95%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

@levb @jfrerich Heads up that this PR has broken master: https://app.circleci.com/pipelines/github/mattermost/mattermost-plugin-jira/1723/workflows/0c43ee0a-750a-4a3b-8f76-afdc2ca0f799/jobs/5371

Yes.  I am workin on that fix right now :)


implement improved node spacing zooming

base on #88
closes #86 and closes #85
when changing the node size change the center of the map to the scaled old center. (either center of the map or the position under the mouse)

the shift could be because of some numeric rounding errors and if you don't hit the center perfectly the error adds up

Thanks for looking into it, and for giving me a tour of the code.
David Manthey is away from the office right now, so let's just merge this and fix the mouse interaction later.


cbor_encode: Fix encoding data length

Change fixes encoding data length and adds support for big endian byte ordering. According to specification, data length can be encoded either on 1, 2, 4 or 8 bytes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The CONFIG_BIG_ENDIAN was used a few lines above in the same file. Still, maybe we should consider defining this in an other way,

Thanks a lot! I started looking into this, and discovered another related bug. I ended up refactoring a bit and solving both bugs in another way: #80. Closing this, in favor of #80


[Docs Bug 🐞 report]: Fix typos in add-server.md

Describe the bug you found in AsyncAPI Docs.
There's a couple of typos in the Server reusability page.
The code reads:
servers:
  kafka-test:
    $ref: '#/components/servers/kafka-test
  mqtt-test:
    $ref: '#/components/servers/mqtt-test
components
  servers:
    kafka-test:
      host: my.kafka.pl
      protocol: kafka-secure
      description: Test Kafka server
    mqtt-test:
      host: test.mosquitto.org
      protocol: mqtt
      description: Test MQTT server

but it should be:
servers:
  kafka-test:
    $ref: '#/components/servers/kafka-test'
  mqtt-test:
    $ref: '#/components/servers/mqtt-test'
components:
  servers:
    kafka-test:
      host: my.kafka.pl
      protocol: kafka-secure
      description: Test Kafka server
    mqtt-test:
      host: test.mosquitto.org
      protocol: mqtt
      description: Test MQTT server

Attach any resources that can help us understand the issue.
Code is at URL: add-server#server-reusability
Image of the rendered typos:

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Spotted while working locally, fixed and submitted a PR: https://github.com/asyncapi/website/pull/3171


Dependency Bug: PostCSS line return parsing error

Describe the bug
Dependabot alert: https://github.com/radius-project/docs/security/dependabot/128
Steps to reproduce
Check out the vulnerability section of the repo: https://github.com/radius-project/docs/security/dependabot
Expected behavior
No vulnerability
Screenshots
N/A
Additional context
N/A
AB#11621

Close not fix, we don't accept non PR changes to Docs


Doc: updates following Rust compilation

This is a follow on to #212 with a few extra tweaks to the documentation.

Just stopping by to say I approve of the level of grammatical pedantry on both sides!  If you want one more, I don't like "Note that" because it's redundant.
And yes please on the citation nudge.


Strict-Mode Unencoding Entities

This is aimed at unencoding entities that may be safely unencoded when used with escape in strict mode.

FYI: I'm testing the new code and I am finding problems. I'm working on characterizing them, but the upshot is that this branch definitely IS NOT production quality yet.

Problems:
Contrary to RFC 3986 §3.3, which does not allow any control characters to appear unescaped in the path segment of a URL, unescaped newline characters do not get normalized to %0A in strict mode as they should.
Contrary to §3.4, which lists / an an allowed character in the query string of a URL, unescaped / characters get turned into %2F sequences. Because / is a member of the GEN-DELIMS set it is also part of the RESERVED set, thus per §2.2 the URL has been changed into a non-equivalent one with this translation. Also, the query section of the URL has the same problem with unescaped newlines that the path section does (and per §3.4 all such characters must be escaped as %0A).

Reupped -- fixed bugs about 1) encoding newlines in URLs and 2) allowing / in queries.

I'm pretty sure that nobody legitimately includes unescaped newline characters in their URLs. Almost all URL parsers consider whitespace as terminating the URL itself. In particular, assuming you are parsing a URL from an href attribute, an unescaped newline character should probably not be included as part of the URL itself. In almost all cases where I've seen this happen, it's been due to broken HTML with either a missing close quote mark or that includes arbitrary javascript (maybe as string interpolation) into the href attribute.
Specifically from Appendix C:

In practice, URIs are delimited in a variety of ways, but usually
within double-quotes "http://example.com/", angle brackets
http://example.com/, or just by using whitespace:
http://example.com/
These wrappers do not form part of the URI.
In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) may
have to be added to break a long URI across lines.  The whitespace
should be ignored when the URI is extracted.
In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) may
have to be added to break a long URI across lines.  The whitespace
should be ignored when the URI is extracted.

Also, section 1.2.1 talks about Transcription whereby someone copies a URL onto a napkin. Whitespace is never meaningful in such a context, and this is considered a general design criteria for URLs. In general, I think treating unescaped whitespace as part of a URL is a very bad idea.


clear text from ng4-geoautocomplete

Hi,
I need to clear the text from ng4-geoautocomplete textbox when I click on submit button.
Please help me on how can I achieve this.
Thanks,
suresh

+1

Please provide the solution for the same, as I want to clear searched text.

You can clear the input field manually in the below way
`this.userSettings: any = {
inputText: ''
}
this.userSettings = Object.assign({},this.userSettings) //Very Important Line to add after modifying settings.
`


centos-6: Disable obsolete mirrorlist for yum

CI isn't prepared for it because CentOS 6 is already EOL.
I confirmed that it can build the package on my local environment.


Login window

In windows, it is difficult that I edit config.json because of Character encoding.
So please make login window.

Looks good point. Thank you for reporting that.
For now, please install your favorite editor on your Windows machine and associate it to .json file extension.
I'll consider how it should be done but it may not be feasible with reasonable effort.  I think I could create simple small login window with two forms.
However, after all, changing app configuration later needs to edit JSON file.


UV doesn't crash if there is operation timeout and error

I was trying to execute uv pip install requirements on latest version of uv. If there was a operation timeout error , uv didn't crash and instead just printed the error like below and said all is successful

Shouldn't it have crashed and asked user to re execute the install command here?

That's surprising. Hm. You might be seeing an error that was retried? Maybe it was a pre-fetch that we didn't need? It seems weird that we could fail a request and not propagate the error into a failure unless the request didn't matter for some reason.

I am not entirely sure, also I see this randomly obviously for some timeout reasons. If possible i will try to get you more verbose logs when it happens

That'd be really helpful. You can set RUST_LOG=uv=trace (or RUST_LOG=trace) to increase verbosity.


Remove the old PhalDock organisation and repository

The organisation PhalDock (https://github.com/PhalDock) with its repository phaldock (https://github.com/PhalDock/phaldock) should be removed since this is the official repository.

Done.


Generalize for Linux and possibly OSX

It would be great, if this extension could be generalized so it runs also under Linux and possibly OSX.
The capabilites of TortoiseSVN should be available under Linux/OSX, if any SVN package is installed, so the binary to call would be probably /usr/bin/svn.

As this is noted as a change in the release list for 1.1 - shouldn't this issue be closed?

@s-martin I think it is reasonable to now remove "Tortoise-" from the extension name+displayName (the repo-name could stay as is, only its description should be adjusted to something like "Using SVN in VS Code (formerly only TortoiseSVN)" with using the same in the displayName) as it should work with any SVN client in PATH, won't it?
I suggest the simple "SVN for VS Code" as extension name and could do a PR for this. Opinions?


NF036: Add logic for awardCriteria when testing with Ecuador

Right now, the indicator just ignores what the awardCriteria is, entirely.
We could add an option to the prepare command to set awardCriteria to 'priceOnly' if the lowest valid bid is awarded.

This indicator makes most sense when the criteria is price only, to identify if the lowest bid was disqualified, so thats the preferred option.  If we decide to input the awardCriteria to price only when the lowest value is awarded, wouldn't we be missing actually on the flagged procedures (lowest bid disqualified)?
To test with Ecuador, I would suggest to ask SERCOP if they use priceOnly award criteria for specific procurement methods instead and input the value based on that.

wouldn't we be missing actually on the flagged procedures (lowest bid disqualified)?

If the condition is that the lowest valid bid is awarded, then it could still be the case that there are lower disqualified bids.

Noting that we removed this indicator from Ecuador SERCOP per the "Questions and feedback" document, so moving to Post-MVP.


enet_projection in dictionary update: hack or not hack ?

The code from lines 604 to 622 of dict_fact.py  is really weird. Are we formally computing the projection of the atom onto the elastic-net unit ball of radius 1 or is it some kind of hack ? For example, the call to enet_projection has radius=self.comp_norm_[k].
In any case, a detailed comment explaining what is being done would help for future maintenance / extension.

It's the right form : see the dictionary update section of https://arxiv.org/abs/1701.05363


Compilation error under TS v<IP_ADDRESS>

Hi!
I just have installed package and installed it for my project and have two errors in collection.ts file:
Type 'LinkedList<{}>' is not assignable to type 'LinkedList'.  Type '{}' is not assignable to type 'T'.
and
Type '{}' is not assignable to type 'BSTreeNode'.  Property 'element' is missing in type '{}'.
Apart that issues whole project is great :)
Thanks!
Aggie

Same problem when I enable "Redirect JavaScript output to directory" in the project TypeScript Build settings.

I just opened the repo right now, I see no errors. Can I have a screenshot?

Hi Basarat,

Got the package from nuget. It was easy to fix - just added some generic args in a couple of places.

Are those errors pointing it our file or other files in the project?

Yes, collections.ts. Is it the latest version in the nuget?

Yes, collections.ts. Is it the latest version in the nuget?

Wasn't. Thanks. Pushed the latest :rose: : https://www.nuget.org/packages/typescript.collections/


No json or ndjson files created

Looking for some help.
I can run my cucumber features successfully with Cypress 10.3
.cypress-cucumber-preprocessorrc.json
{
  "json": {
    "enabled": true,
    "formatter": "node",
    "args": [
      "report-formatter.js"
    ]
  },
  "messages": {
    "enabled": true,
    "output": "./messages.ndjson"
  }
}

report-formatter.js
const Formatter = require('cucumber-json-report-formatter').Formatter;

const formatter = new Formatter();
const sourceFile = "./messages.ndjson"
const outputFile = "./cucumber-report.json"

await formatter.parseCucumberJson(sourceFile, outputFile);

After running single scenario, no files are generated
I tried putting the configuration w/in thepackage.json file too but nothing worked.

Doh!  my bad.  Works when "run" no "open"


Add support for function keys

Is your feature request related to a problem? Please describe.

It would be very useful if egui had support for function keys F1, F2, etc as they are great to bind for special purposes.
Describe the solution you'd like

Support for Fn keys in Key enum and handling on at least desktop platforms.  Compile time feature if necessary.
Describe alternatives you've considered

I don't know of any alternative solutions other than choosing other key bindings.  However a user may expect F1 to bring up help, and might appreciate function keys for other application functions.
Additional context

Just go ahead and add them if you want them! Just make sure to test them on web too!

Looks like this was implemented in PR #1665, so closing.


dark get_color_frame()

| Camera Model                       | D415 |
| Operating System & Version |   Ubuntu 18 , Jetpack 4.4 [ L4T 32.4.3]   |
| Platform                                 | NVIDIA Jetson Nano  |
| Language                               |  python |
Issue Description
I use simple example from distance_to_object.ipynb (https://github.com/IntelRealSense/librealsense/blob/jupyter/notebooks), but something is wrong with frameset.get_color_frame() data. It is very dark. Also i noticed that the camera used IR Projector to produce photo.

Hi @linukc  I downloaded the **object_detection bag file from the link below so that I could check it in the RealSense Viewer.
http://realsense-hw-public.s3.amazonaws.com/rs-tests/TestData/object_detection.bag
I cannot see any problems with dark RGB in the file.  And because it is recorded data instead of live camera input, it would only respond to changes in the post-processing filter settings and filters are not applied in the distance_to_object example.
Could you download the bag file from the link above and drag and drop it into the center window of the RealSense Viewer please to confirm whether the color renders correctly when the bag is played in the Viewer, please?

@MartyG-RealSense

I didn't notice problem with live color stream at another programs (for example jetson example).

Having a camera connected at the same time as playing the bag should not make a difference to the bag's playback, as it is using recorded data and so the current status of the projector should not make a difference to the bag image.
If you are using that bag file when the camera disconnects, I experienced instability with it myself whilst testing it in the Viewer, such as frequent crash-exits of the Viewer.  Do you still experience camera disconnection if the bag is not being accessed?

I was able to help myself. I increased Auto-Exposure time to adjust (for x in range(15):
pipe.wait_for_frames() instead for x in range(5): pipe.wait_for_frames() [The API, line 8]) and color stream works perfect.

  We're here to help, and you learned something from it too.  Glad you found a solution!

@MartyG-RealSense, about disconnect - it not a very big problem, i rarely use Viewer, but i can create another issue and give more details about this strange.

Okay, please do make a new issue and I will take a look at it on Friday.


Workers not identified

When I start workers on an LSF cluster the jobs are started but the client does not acknowledge the workers. If I submit tasks to the cluster they are never executed because there are no workers to perform the execution. I know the jobs are indeed starting because I can see them on my system with the bjobs command.
This just started happening. Everything was running fine for a few months.
cluster = LSFCluster(queue='short', processes=4, walltime='2:00', ncpus=4, mem=2024, cores=4, memory='2 GB')
client = Client(cluster)
cluster.scale(8)
cluster

Output
LSFCluster(cores=0, memory=0 B, workers=0/8, jobs=0/2)
This does not change even after the jobs start running.

Weird, especiallly the "this just started happening" since nothing has changed on the dask-jobqueue side (last dask-jobqueue release was in October 2018).
What you are seeing seems to indicate that the LSF jobs start but that the dask workers do not manage to connect to the scheduler.
The few things I would suggest:

make sure that you are using the same conda/virtualenv environment where you run the snippet above and in your workers. Sometimes a good sanity check is to create a new conda/virtualenv environment from scratch and see whether the problem is still here.
have a look at https://jobqueue.dask.org/en/latest/debug.html to troubleshoot your problem. In particular, I would look at your LSF logs stdout/stderr logs to see whether there is any indication of where the problem might be and also increase the logging verbosity.

Thank you for your suggestions. Things are working as expected today. Not sure what happened, it is likely something to do with the cluster. I will close this issue for now.


python2Packages.pylatexenc: 2.1 -> 2.2

Motivation for this change
Version bump hit last night. https://github.com/phfaist/pylatexenc/releases/tag/v2.2
Cleans up some meta/test too.
Things done

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

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

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

@GrahamcOfBorg build python27Packages.pylatexenc python37Packages.pylatexenc python38Packages.pylatexenc
downstream packages like python3Packages.qiskit-terra currently fail due to #83888 merge causing scipy failures (see https://github.com/NixOS/nixpkgs/pull/84943#issuecomment-617154731), so nixpkgs-review pr 85676 doesn't run cleanly.

@GrahamcOfBorg build python27Packages.pylatexenc python37Packages.pylatexenc python38Packages.pylatexenc

unfortunately, this causes rebuilds of scipy and a few other heavy weight packages. But I am building it. Also, I should have my 3990X server up soon, which should be able to to build these very quickly.

Maybe if I rebase it onto master, the build would go easier? Scipy
shouldn't have to rebuild based on this, it does need to rebuild after the
Blas merge referenced above.
On Tue, Apr 21, 2020, 7:24 PM Jon<EMAIL_ADDRESS>wrote:

unfortunately, this causes rebuilds of scipy and a few other heavy weight
packages. But I am building it. Also, I should have my 3990X server up
soon, which should be able to to build these very quickly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/85676#issuecomment-617462563, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNZYI2W2ZCDQQUIIUWJH6TRNYTLRANCNFSM4MNIZGVA
.


After update to 1.0.0 detects are incorrect

After the update from 0.5 some feature detects are incorrect, for example with a project in 0.5 the feature detect "eventlistener" returns true on the latest version of Chrome, with 1.0.0 it returns false.

Hey @amorino, thanks for reporting this bug. Could you please provide us with some more information about your webpack and modernizr configuration? This would be helpful, thanks!

@flootr I have anther issue using v1.0.0. I'm chaining yaml-loader and modernizr-loader to write the config file in yaml. Here's my .modernizerrc
minify: false

options:
  - setClasses
  # - testAllProps
  # - mq

feature-detects:
  # - svg
  # - video

After starting webpack-dev-server, I got this error:
ERROR in ./.modernizrrc
Module build failed: /Users/jude/sites/devcore2017/.modernizrrc:2
	"minify": false,
	        ^
SyntaxError: Unexpected token :
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.exec (/Users/jude/sites/devcore2017/node_modules/webpack-core/lib/NormalModuleMixin.js:88:7)
    at Object.module.exports (/Users/jude/sites/devcore2017/node_modules/modernizr-loader/index.js:20:26)
 @ ./client/index.coffee 5:0-20
webpack: bundle is now VALID.
^C

I have tried the same setup with v0.0.5, everything worked great.

@judewang you could try to pass in the json-loader before moving stuff from the yaml-loader to the modernizr-loader. Like so: modernizr!json!yaml.

@flootr It worked! I haven't notice that new version needs json-loader, thanks.

Sorry to pile-on a somewhat unrelated issue, but it might not be a bad idea to make a note about upgrade path:

Install json-loader when using JSON config.
Add !json to loader chain in Webpack config.
Properly import Modernizr where previously you'd been relying on a global.

I seem to be up and running again, thanks for your work!

@synapticism good point! I updated the CHANGELOG accordingly.

I believe this bug is caused by #23. In the built Modernizr file, window will be an empty object now, so tests such as "addEventListener" in window return false.

I took a closer look and it seems I'm also experiencing the same problem as the OP: multiple tests are failing where the global window object is referenced in the Modernizr test.

I created a PR #25 which should resolve the issue.

Can we merge that pull request? Works properly.

@clessg thanks for your PR 👍
I somehow want to have this tested though. I'm going to set up a local test project to see how we can improve on this.

@flootr when can we merge this PR, getting the same issue as some modernizr tests are failing. Thanks


Fix: Unknown Match in CustomerGroupRelationManager

Not sure this is a correct way to fix or no. But, happened an exception/issue during installation and testing when attach a customer group to product in availability section:
Here is the exception;

After this, it will look like this.

Thanks @tuvshinjargal Do you know what the state was if it wasn't 0 or 1 ?

This was 0 (false) on the table

Thanks @tuvshinjargal I don't think this solution is correct, I'm going to close but if possible could you raise as an issue instead with more details on how to reproduce so we can approach this a different way :)


rootDir and path mapping does not work for paths outside rootDir

TypeScript Version:  2.6.2

Search Terms: rootDir, rootDir and path mapping, path mapping, path map rootdir, etc.
Code
Clone cra-workspaces.

Run yarn install at root
cd packages/package-b
yarn build

Expected behavior:
TS compiler should compile without errors.
Actual behavior:
The compiler throws:
yarn run v1.3.2
warning package.json: No license field
$ tsc
error TS6059: File '/Users/agroza/Projects/cra-workspaces/packages/package-a/src/foo.ts' is not under 'rootDir' '/Users/agroza/Projects/cra-workspaces/packages/package-b/src'. 'rootDir' is expected to contain all source files.
error TS6059: File '/Users/agroza/Projects/cra-workspaces/packages/package-a/src/index.ts' is not under 'rootDir' '/Users/agroza/Projects/cra-workspaces/packages/package-b/src'. 'rootDir' is expected to contain all source files.
error Command failed with exit code 2.
i

I understand that this happens because I set rootDir and that the paths are outside, but I need the rootDir to generate a proper folder structure after compilation (everything that's inside of packages/package-b/src should end up compiled in packages/package-b/out-tsc/lib-es2015/ with the exact structure of the contents of packages/package-b/src).
Playground Link:
Related Issues:

package-b is depending directly on the .ts files in package-a. Since these are .ts files we expect to emit them somewhere. It might be better to depend on the public interface of package-a from its generated declaration files, so that nothing gets emitted for package-a when compiling package-b.

@andy-ms I understand. Ideally, the compiler should somehow know that it should only emit the js for the ts files that are in "rootDir": "src" (and keep the folder tree structure) of package-a even though it also needs some from package-b.
I'm not sure I follow what you're saying.
I use tsc in two ways:
First:

cd to package-b
tsc --watch
Edit some files in package-a and expect tsc to see the change and rerun the compilation of package-b

Second:

cd to package-b
tsc and expect the package to be compiled into js
cd to package-a
tsc and expect the package to be compiled into js

First case it's useful during development. It works the same for tests (with jest), rerun when there are changes in either package.
Second case it's a single run task that's supposed to compile the ts files to js and a subsequent step that takes the result and generates UMD and FESM modules (using Rollup). That's why it's essential to keep the same folder structure, otherwise I'd need to make a different script for each package that knows where the compiler outputs the files and how the folder structure looks like (even though this is trivial, it's easy to forget this when you add new packages or remove them and the output tree changes).

First:
cd to package-b
tsc --watch
Edit some files in package-a and expect tsc to see the change and rerun the compilation of package-b

That wouldn''t work at runtime if the compiled output of package-a isn't also updated -- you would need to --watch both packages.
You may be interested in #17611.

@andy-ms are you sure about that? Because that's not what I'm seeing.
Just cd packages/package-b and run yarn start. Ignore the errors I described and go to package-a and change some .ts files. You will see that the TS compiler picks up on that and will rerun.

Yes, because it sees the files in package-a as part of its compilation. But what you were asking for was for it to only update the emitted files for package-b -- then you would end up with a broken program because the compiled output of package-a wouldn't be up to date. #17611 would allow you to compile everything together so this doesn't happen.

Ok. I've already been subscribed to that issue. So what you're also saying that currently there's no way to have the rootDir and path mappings that point outside of the root dir scope and there's no plan to support this?

Quick question, could I use the programmatic API to find out how the folder structure emitted by the compiler would look like?

Ok, I resorted to simply searching for a file that I know will be at the root of the emitted folder that I'm interested in. Not ideal, but it works.
If there are no plans to support a rootDir when path mappings are outside of the root dir path, then I guess this issue can be closed.


UI Improvements

Currently every part of the font viewer are editable text fields, which feels a bit weird.
It would be best to lock all text fields and create another text field with placeholder "Type here to preview", so that users can type anything and the viewer will change the sample text to input string.

I did that on purpose, as a graphic designer I use it all the time, this was one of the main reasons I made this plugin.

Still, I think a separated text field is somehow certainly better and less buggy. And the "buggy" includes: pressing [Enter] in text fields will simply open the font file instead of adding a line break, and the copyright line is not rendered using the font but still editable.
Perhaps we can somehow freeze the title area, and fix the [Enter] bug in main text field?


Bugfix config tab process

Bugfix for
https://github.com/maykar/custom-header/issues/75

I'd still want to support cases of 5to6, so a regex to detect numbers on either side would be better.


//eventuals/grpc breaks cc_binary targets built with linkshared = True

Given a minimal sample-binary.cc that defines an empty main function:
int main() {
  return 0;
}

These two binaries build:

cc_binary(
    name = "sample-eventuals-grpc-binary-default-link",
    srcs = ["sample-binary.cc"],
    copts = copts(),
    # Use default linking.
    deps = ["//eventuals/grpc"],
)

cc_binary(
    name = "sample-eventuals-grpc-binary-static-link",
    srcs = ["sample-binary.cc"],
    copts = copts(),
    # Use static linking (build libraries as `.a` files).
    linkstatic = True,
    deps = ["//eventuals/grpc"],
)

But this binary does not:
cc_binary(
    name = "sample-eventuals-grpc-binary-shared-link",
    srcs = ["sample-binary.cc"],
    copts = copts(),
    # Use dynamic linking (build libraries as `.so` files).
    linkshared = True,
    deps = ["//eventuals/grpc"],
)

The error is reproducible without //eventuals/grpc by depending on both @com_github_grpc_grpc//:grpc++ @com_github_jemalloc_jemalloc//:jemalloc together:
cc_binary(
    name = "sample-grpc-and-jemalloc-binary-shared-link",
    srcs = ["sample-binary.cc"],
    copts = copts(),
    linkshared = True,
    deps = [
        "@com_github_grpc_grpc//:grpc++",
        "@com_github_jemalloc_jemalloc//:jemalloc",
    ],
)

The error is about invalid relocations given the compiler's flags:
 /workspaces/respect/submodules/eventuals/test/BUILD.bazel:118:10: Linking test/libsample-grpc-and-eventuals-binary-shared-link.so failed: (Exit 1): clang failed: error executing command
  (cd /home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/63/execroot/com_github_3rdparty_eventuals && \
  exec env - \
    PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
    PWD=/proc/self/cwd \
  /usr/lib/llvm-14/bin/clang @bazel-out/k8-fastbuild/bin/test/libsample-grpc-and-eventuals-binary-shared-link.so-2.params)
# Configuration: b74a02822c949d313fa6fb43644395877f96df5af4a497bac0102267e6c72476
# Execution platform: @local_config_platform//:host

Use --sandbox_debug to see verbose messages from the sandbox
ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'malloc_conf'; recompile with -fPIC
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(jemalloc.o)
>>> referenced by jemalloc.c:955 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/jemalloc.c:955)
>>>               jemalloc.o:(malloc_conf_init_helper) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'malloc_message'; recompile with -fPIC
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(malloc_io.o)
>>> referenced by malloc_io.c:84 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/malloc_io.c:84)
>>>               malloc_io.o:(je_malloc_write) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'malloc_message'; recompile with -fPIC
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(malloc_io.o)
>>> referenced by malloc_io.c:627 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/malloc_io.c:627)
>>>               malloc_io.o:(je_malloc_vcprintf) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'malloc_message'; recompile with -fPIC
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(malloc_io.o)
>>> referenced by malloc_io.c:627 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/malloc_io.c:627)
>>>               malloc_io.o:(je_malloc_cprintf) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'malloc_message'; recompile with -fPIC
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(malloc_io.o)
>>> referenced by malloc_io.c:627 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/malloc_io.c:627)
>>>               malloc_io.o:(je_malloc_printf) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:51 (include/jemalloc/internal/tsd_tls.h:51)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:52 (include/jemalloc/internal/tsd_tls.h:52)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:54 (include/jemalloc/internal/tsd_tls.h:54)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:0 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:0)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:0 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:0)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:0 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:0)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:0 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:0)
>>>               tsd.o:(je_tsd_fetch_slow) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:51 (include/jemalloc/internal/tsd_tls.h:51)
>>>               tsd.o:(je_tsd_cleanup) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:52 (include/jemalloc/internal/tsd_tls.h:52)
>>>               tsd.o:(je_tsd_cleanup) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd_tls.h:54 (include/jemalloc/internal/tsd_tls.h:54)
>>>               tsd.o:(je_tsd_cleanup) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.h:353 (include/jemalloc/internal/tsd.h:353)
>>>               tsd.o:(je_malloc_tsd_boot0) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:430 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:430)
>>>               tsd.o:(je_malloc_tsd_boot0) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.c:430 (/home/vscode/.cache/dazel/eventuals/sandbox/processwrapper-sandbox/11/execroot/com_github_3rdparty_eventuals/bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_.build_tmpdir/src/tsd.c:430)
>>>               tsd.o:(je_malloc_tsd_boot0) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.h:354 (include/jemalloc/internal/tsd.h:354)
>>>               tsd.o:(je_malloc_tsd_boot0) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: relocation R_X86_64_TPOFF32 against je_tsd_tls cannot be used with -shared
>>> defined in bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a(tsd.o)
>>> referenced by tsd.h:353 (include/jemalloc/internal/tsd.h:353)
>>>               tsd.o:(je_malloc_tsd_boot1) in archive bazel-out/k8-fastbuild-ST-dd44be474a39/bin/external/com_github_jemalloc_jemalloc/jemalloc_preinstalled_make_/lib/libjemalloc.a

ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Target //test:sample-grpc-and-eventuals-binary-shared-link failed to build
INFO: Elapsed time: 0.837s, Critical Path: 0.52s
INFO: 5 processes: 4 internal, 1 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

I discovered this when trying to use pybind11 (via https://github.com/pybind/pybind11_bazel#bazel-extensions-for-pybind11 ) to call C++ code from Python. This builds the wrapped C++ libraries as shared libraries, as can be seen in this example: https://github.com/cdleary/bazel_pybind_sample/blob/master/BUILD#L10
Sample PR that configures these binaries: https://github.com/3rdparty/eventuals/pull/469
The break can be reproduced by running these commands on the xander.shared-wont-build branch:
dazel build //test:sample-eventuals-grpc-binary-shared-link

or:
dazel build //test:sample-grpc-and-jemalloc-binary-shared-link

Modifying our code in https://github.com/3rdparty/bazel-rules-jemalloc/blob/main/BUILD.bazel that defines @com_github_jemalloc_jemalloc//:jemalloc seems to affect this error: more on that in another comment!

I can get the linkshared = True build to succeed if I comment out this out_static_libs property: https://github.com/3rdparty/bazel-rules-jemalloc/blob/c82c0c3856f07d53c1b76e89beeb8abab8c2d0ad/BUILD.bazel#L29-L34
And replace it with an out_shared_libs property:
    out_shared_libs = select({
        "@bazel_tools//src/conditions:windows": [
            "libjemalloc_so.lib",
        ],
        "//conditions:default": ["libjemalloc.so"],
    }),
    # out_static_libs = select({
    #     "@bazel_tools//src/conditions:windows": [
    #         "libjemalloc_a.lib",
    #     ],
    #     "//conditions:default": ["libjemalloc.a"],
    # }),

Simply adding the out_shared_libs property without commenting out the out_static_libs does not resolve the issue or change the produced error.
This change appears to make all 3 binaries build, and it passes eventuals tests. I don't know if it breaks anything because I don't know how to check whether jemalloc is correctly used.
Overall, this build issue makes me think that:
a) We should document why we're using any non-standard malloc replacement.
b) We should consider using tcmalloc instead of jemalloc, since tcmalloc supports being built by bazel out of the box: https://github.com/google/tcmalloc/blob/master/docs/quickstart.md#creating-your-build-file so we don't have to hand-roll bazel support (which the jemalloc team didn't want to add because it would be too hard to do correctly if https://github.com/cockroachdb/cockroach/issues/57976#issuecomment-746899504 is correct)
c) We should consider replacing malloc at a binary level, not at a library level, so we're not trying to conflict with other malloc replacements (which gRPC might be doing)
I'm going to send out a PR to do something like switch to out_shared_libs.


Code workflow

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: psmadasu sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.