[mlflow] Upgrade mlflow to version 2.4.2

What this PR does / why we need it:
Upgrades MLFlow to version 2.4.2. Container image still needs to be pushed to registry.
Which issue this PR fixes
Special notes for your reviewer:
Just duplicated the changes from the last version bump.
Checklist

[ x] DCO signed
[ x] Chart Version bumped
[x ] Chart artifacthub.io/changes field updated (if exists)
[ x] Title of the PR starts with chart name (e.g. [mlflow])
[ ] Unit tests written
[ ] values.yaml file fields documented
[ x] README.md file updated

Also opened a PR to upgrade the container image.
https://github.com/burakince/mlflow/pull/112


added custom callback for fileopen()

Hi,
this pull request adds a FPPTAG to submit is custom fileopen function.
Reason: this is useful for integration into any engine that rolls its own filesystem (where fopen does not work) or for embedding into environments where there are no local files (e.g. asm.js/webassembly).
Cheers.

cpp3.c:277:24: warning: assignment from incompatible pointer type [-Wincompatible-pointer-types]
       global->openfile = (FILE* (*)(char *,char *))tags->data;


Add <LinkButton> to Radiance ✨

Adds the LinkButton component to the Radiance package.

React Router support
You can now pass in React Router's Link/NavLink as a prop.
import { Link } from 'react-router';

<LinkButton to="/somepath" renderedTag={Link}>
  Click me!
</LinkButton>

 Convert Button component


SAM crashes after loading large library

When launching a library of over 5000 games, SAM crashes without error after loading 100% of the library. I'm able to interact with SAM as it's loading and click a game before the crash, but the main window crashes without error the majority of the time.
After attempting to open it several times I've finally been able to generate an error:
SAM (1465860) 2024-07-28 10:50:47,506 ERROR SteamStatsManager [8] - An error occurred handling stats retrieval. Specified argument was out of the range of valid values. (Parameter 'stat') System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'stat')    at SAM.Stats.SteamStatisticFactory.CreateStat(Client client, StatInfoBase stat) in D:\a\SteamAchievementManager\SteamAchievementManager\src\SAM\Stats\Factories\SteamStatisticFactory.cs:line 57    at SAM.Stats.SteamStatsManager.GetStatistics() in D:\a\SteamAchievementManager\SteamAchievementManager\src\SAM\Stats\SteamStatsManager.cs:line 279    at SAM.Stats.SteamStatsManager.OnUserStatsReceived(UserStatsResponse param) in D:\a\SteamAchievementManager\SteamAchievementManager\src\SAM\Stats\SteamStatsManager.cs:line 144
I've noticed the original branch of SAM functions normally as well as SAM Auto, so I'm unsure if it's a matter of how large libraries being considered outside of the range of valid values.

Upon further review, I believe it's do to the inability to translate certain Unicode characters some examples:
🔴 Circles
🕌魔塔与6⃣勇者  (Six Braves)
I've tested a change on my own fork and it seems to have resolved the issue.

why close the issue? it's not solved here as far as i can tell

Upon further review, I believe it's do to the inability to translate certain Unicode characters some examples: 🔴 Circles 🕌魔塔与6⃣勇者 (Six Braves)
I've tested a change on my own fork and it seems to have resolved the issue.

Heyo, I just now saw this because you closed it too fast, I can make the change here for the unicode fix or if you wanted to make a PR that would be cool too.


Add VLASS as a database option

VLASS is a useful point source catalog of radio sources:
https://cirada.ca/vlasscatalogueql0
Can be loaded as, for example:
    df = pd.read_csv(catalog_file)
    df = df[df["Duplicate_flag"] < 2]
    df = df[df["Quality_flag"] == 0]
    df = df[df["Total_flux"] >= 1]
    df = df[df["Total_flux"]/df["E_Total_flux"] >= 5]

See https://github.com/dmitryduev/kowalski/blob/master/tools/ingest_ztf_source_features.py for reference.

This and the test_ingester.py script looks like good examples. Do you also have an example somewhere of the script you used for some other catalog?

See here: https://github.com/dmitryduev/kowalski/tree/master/tools
There are scripts for Gaia and PS1 STRM.


Line breaks don't cause exception

Line breaks will be removed from strings now to avoid exceptions being thrown. We could add support for multiple lines at a later time.

Looks good.


gltfio: fix crash when custom attributes used

Thanks, this makes sense to me. Do you have a glTF file that uses custom attributes we can use to verify?

robot.zip
This is glTF file with custom attributes as follows:

NOTE: on linux or android, load this glTF will not make app to crash sometimes, seems caused by "undefined behaviour"; but on mac or iOS, app will crash by SIGABRT always.


[move] type layout generation from modules

Motivation
This is the clone of #8968 just because I don't know how to commandar that PR :(

Add code in the move-binary-format crate to create a MoveTypeLayout from a CompiledModule
In the cli, add new generate struct-layout command that leverages this functionality to dump layouts in YAML format
The eventual goal is to have the CLI spit out YAML that can be used directly by serde-generate to create typed struct bindings in any language supported by serde-generate
Added the error propagation comparing to #8968.

/land


Cannot find colorscheme 'base16-stylix'

Hey, love the project pretty much everything worked straight out of the box for me, but I came across this one issue.
I have 2 machines running the same configuration, but on 1 of the machines i get the following error when opening neovim:
Error detected while processing /home/user/.config/nvim/init.lua:
E5113: Error while calling lua chunk: vim/_editor.lua:0: /home/user/.config/nvim/init.lua..nvim_exec2() called at /home/user/.config/nvim/init.lua:0../nix/store/ccv39rvxf4swj4qnspkzk9k0np384z88-nvim
-init-home-manager.vim, line 2: Vim(colorscheme):E185: Cannot find color scheme 'base16-stylix'
stack traceback:
        [C]: in function 'nvim_exec2'
        vim/_editor.lua: in function 'cmd'
        /home/user/.config/nvim/init.lua:1: in main chunk

I have already verified that all the files are present, there is a /nix/store/.../colors/base16-stylix.nix, etc.
The files also look identical accross devices
I am not using nixvim
For now i have disabled the nvim module, but i would prefer for it to work like my other machine
Does anyone know what could be going on here?

I'm not sure what the issue was, but seems it solved itself.
I can't reproduce it anymore, so I'm closing this issue

I had same issue. I think it happes because some shell. I use tcsh and had same issue, but after rehash this issue disappears.


C++ compatibility and fix compiler warnings

Add extern "C" when compiling from C++
Sprinkle some NK_UNUSED macros on unused variables
Declare a few functions only present under NK_IMPLEMENTATION as static instead of NK_API (-Wmissing-prototypes)

Thanks so much. I've been wanting to put more work into this project....

Merging nuklear_gamepad into nuklear_console
Clean up the memory allocation system to use the context's allocator
Possibly having multiple windows... somehow

If you have any other ideas, lemme know!


Inliner panic

def Main = Many { Match1 'a'; Match1 'b'; Match1 'c' }

The problem seems to be with inlineBlocks


Ensure that our TypeScript and/or JSDoc checking is configured properly

In a recent PR it became apparent that we weren't catching some obvious TypeScript/JSDoc issues. In this case it was a @readonly tag on a getter, which isn't valid as getters are always readonly.
Node.js version: Any
Impacted package(s): All
Steps to reproduce
To show the error occurring:

Install<EMAIL_ADDRESS>in n-membership-sdk
Use the HttpError somewhere (just import and add new HttpError({}))
Run the build to see the error

To see our build passing:

Check out the commit before James' PR
Run npm run lint, there will be no errors reported

Expected behaviour
We expect the linter to complain in the same way as n-membership-sdk does.

We've started publishing type definitions since we created this ticket.


Begin using meson build system

Currently GStreamer 1.16 is being built, which supports both meson and automake, however in master and for the next 1.18 release, automake has been removed completely in support of meson. Some feedstock that have moved to meson include atk and gdk-pixbuf.
I'll take a stab at doing this, and submit a PR if successful

@joshdoe , You probably saw this already, but gobject-introspection-feedstock  has a recipe that uses meson.

I just went to atk-feedstock and saw that recipe uses meson too.
Never mind.

What's the status of this?

 Once it works well there, then I was going to revisit this. However I'm trying to port to meson plus Windows at the same time, should probably just do it on Linux first.


Add Azure Content Safety java

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run prepare-pipelines

/azp run java - contentsafety - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-contentsafety

/azp run java - contentsafety - ci

/azp run prepare-pipelines

/azp run java - contentsafety - ci

/azp run java - contentsafety - ci

/azp run java - contentsafety - ci

/azp run java - contentsafety - ci

/azp run java - contentsafety - ci

/azp run java - contentsafety - ci


Migrate SystemController to v2.0

Currently only ran the system controller example projects for the SJOne and MSP432 boards. Unable run the the clock configuration example projects for the other boards since I don't have them.

I'll take a look at this tomorrow on Sunday. This is a big change and will take some time for me to go over.


getting blank sets when accessing v2/_catalog using riak-cs(2.0.1) backend

The registry is accessing the riak-cs without specifying delimiter, causing riak-cs to crash.  The crash log points to a function where it tries to search for the delimiter'<<>>' in the file path.  We have to use s3-goamz driver because the riak-cs doesn't support v4auth yet.

@Charles546 have you tried using the v2 signing with the s3-aws driver?

@dmcgowan I don't see an option to use v2 signing with s3-aws driver.

See comment on #2227


Network Mocking

Hello.
Is there any way to test an application using Maestro with network mocking?
Thanks.

You could prepare a mock flavor/version of your application and run maestro on that app variant

Thanks for the answer @AKJAW .
It seems there is also now an Experimental section on Network Mocking!
https://maestro.mobile.dev/advanced/experimental/network-mocking
I'll give those a try.


NGX-Admin ghost button not w

Ghost Button etc. not working!
I was developing a project on this ngx-admin theme. But yesterday, I ran command 'npm install' to install the package for some newly added components.
But as soon as it got installed, the project stopped working.
I rectified all the issues, it took me a couple of hours and maximum things are sorted as of now.
But now, the ghost button and the ghost dropdown are not working as they were, earlier.
I am attaching the screenshot of a nb-card to have an idea of the problem.
While running the application with 'ng serve', it runs like earlier but there is a warning of Deprecation for @import rule in CSS files. I don't know if this is anywhere related to this issue.
Kindly help.

hi @himanshuaum !
Could you tell me please about these components? Are they from Bootstrap or Nebular?


std::tm timestamp problem with DST

In timezone with the 'daylight savings time' (e.g. Europe/Prague), it's not possible to read 31.3. 2:00:00 from database (e.g. postgresql: timestamp without timezone), because mktime() will always change it to 3:00:00
TEST_CASE("Time DST", "[postgresql][dst-time]") {
	// hack: set Europe/Prague time zone
	setenv("TZ", "Europe/Prague", 1);

	soci::session sql(backEnd, connectString);

	sql << "drop table if exists soci_test;";
	sql << "create table soci_test(id integer, ts timestamp)";

	// winter summer time shifts from 2:00 -> 3:00
	// but we use the database for UTC values
	sql << "insert into soci_test values (1,'2019-03-31 02:00:00'),(2,'2019-03-31 03:00:00')";

	std::tm t1 {};
	std::tm t2 {};

	sql << "select ts from soci_test where id=1", into(t1);
	sql << "select ts from soci_test where id=2", into(t2);

	// it is not possible to determine if original DB value was 2:00 or 3:00
	// because t1 == t2
	bool t1_equals_t2 =
		t1.tm_mday == t2.tm_mday &&
		t1.tm_mon == t2.tm_mon &&
		t1.tm_year == t2.tm_year &&
		t1.tm_hour == t2.tm_hour &&
		t1.tm_min == t2.tm_min &&
		t1.tm_sec == t2.tm_sec &&
		t1.tm_isdst == t2.tm_isdst &&
		t1.tm_gmtoff == t2.tm_gmtoff;

	// fails
	CHECK_FALSE(t1_equals_t2);
}

So do I have to change time zone of whole program, to be able to read '2019-03-31 02:00:00' from the database?

The string with timestamp is parsed here
https://github.com/SOCI/soci/blob/95e4633a5f00b2f75cd7d79a5266476181bc316d/src/backends/postgresql/standard-into-type.cpp#L108-L111
Possibly, the parser needs to be improved
https://github.com/SOCI/soci/blob/56bc9f9c5e1f12c43217f4949cf70489d91ed4c9/src/core/common.cpp#L45-L93
PRs welcome!

I dont think it Postgresql only problem.
soci::details::parse_std_tm parses 31.3.2019 2:00:00 with is_dst=-1 and tm_gmtoff=0
But then mktime_from_ymdhms is called:
inline
void
mktime_from_ymdhms(tm& t,
                   int year, int month, int day,
                   int hour, int minute, int second)
{
    t.tm_isdst = -1;
    t.tm_year = year - 1900;
    t.tm_mon  = month - 1;
    t.tm_mday = day;
    t.tm_hour = hour;
    t.tm_min  = minute;
    t.tm_sec  = second;

    mktime(&t);
}

and mktime changes it from 2:00:00 to 3:00:00
It is just not possible to store 31.3.2019 2:00:00 in the std::tm, when it does not exist in current time zone. Because time skips from 1:59 to 3:00 then anything between 31.3. 2:00 and 31.3. 2:59 cannot be returned as std::tm after the mktime call.
Any plans for replacing std::tm with another data type?

I have analysed this issue in relation to my team's project and it potentially affects every SOCI user (regardless of database) running on a system with Daylight Saving Time enabled (most people I'd guess). There are specific hours that will not be read correctly from the database and will be inaccurate by 1 hour.
Writing to the database via soci::use() is affected also. If a std::tm with a specific date/time is passed to soci::use(), the library will (quite unexpectedly!) change the value of the input variable by 1 hour. However, the original value will be written correctly to the database. If the input variable is const, an "Attempted modification of const use element" error will occur.
Our application uses SOCI with Oracle on a standard UK timezone (with DST) on Windows 10 and I experience this problem. It affects PostgreSQL also but is not a PostgreSQL-specific issue so could we lose the PostgreSQL label?
As Saring pointed out, this is due to mktime() altering the input std::tm time as part of its normalisation function.  In UK timezone with DST enabled, an input date/time that falls within the hour where clocks go forward (e.g. 31 March 2019 01:00) will be moved forwards or backwards 1 hour depending on the value of tm_isdst.  Presumably this is because mktime() expects to operate on local time and in UK+DST the aforementioned time does not exist.  However, in our application date/times are UTC where it would be legitmate.
You can write a test app to examine mktime() behaviour for your timezone by looping through every hour of the year, calling mktime() and checking whether mktime has modified the input. Changing tm_isdst affects whether the input time is moved forwards or backwards but there is no value that prevents modification in my timezone.
The reason this issue affects SOCI is because mktime() is used in mktime_from_ymdhms() to normalise a std::tm that has been read from database client libs.  When reading a date/time from the database, a std::tm is created from the internal db format and mktime() is used to normalise that value.  When writing to the database, after the write has been performed, the input value (in internal db format) is read back again (to allow for in/out parameters) and converted to std::tm which is validated by mktime().  Interestingly, mktime() normalisation is not applied to the value before it is written to the database.
My thoughts are that any std::tm passing through the SOCI API should be written to/read from the database verbatim with no localisation. To my knowledge, SOCI does not handle database types that include timezone information and therefore all times are naive/unaware of timezone. SOCI would need a different type to hold a timezone-aware date/time since members tm_zone/tm_gmtoff are unsupported on many platforms (e.g. Windows).
POTENTIAL SOCI SOLUTIONS

In mktime_from_ymdhms(), replace the call to mktime() with a call to _mkgmtime() on Windows or timegm() on Linux/BSD. This works like mktime() but always assumes GMT/UTC so does not adjust times for local timezone. We have implemented this temporarily in our local build and it works OK.

Unfortunately these are not standard C/C++ functions. SOCI could define timegm() as _mkgmtime() on Windows builds but are there other platforms for which this might be a problem?

Remove the mktime() call from mktime_from_ymdhms() altogether. Just poke the parameters into the std::tm and return it with tm_isdst=0 (or perhaps -1), tm_wday=-1, tm_yday=-1.

I question whether normalising via a call to mktime() is necessary. Historically, std::tm has often been considered to represent local time but there have always been exceptions to this.  It seems to me that SOCI API is just using std::tm as a convenient DTO for y,m,d,h,m,s since tm_isdst, tm_wday, tm_yday are ignored when converting to internal db formats. If it is just a DTO with no implied localisation semantics, does it need normalising?
Currently, mktime() normalisation is only applied to values being read back from database client libs.  Is it likely that the database would produce an output that requires normalisation? Is it necessary to calculate tm_wday, tm_yday? If so, perhaps it should be the responsibility of the client application to call mktime()/_mkgmtime()/timegm() as they see fit?  Given that the database time value is zoneless I don't think we should assume it bears any relation to the client machine timezone so should avoid making calls that bring localisation into play.

Implement one of the above choices with a build option that allows the SOCI user to choose if they wish to preserve the current behaviour or adopt one of the above.

Any thoughts on this?  I'm happy to implement a fix but could use a steer on the desired approach

Thanks for looking at this! It's clearly a bad bug and I just didn't have the courage to dive into it as I know that everything DST-related always takes more time than foreseen.
Ideal, I think, would be to have some SOCI-specific type representing the time(stamp) with TZ info, but this is probably going to require a lot of work, so I agree that just passing the contents of struct tm transparently to/from the database is the best we can realistically do right now.
If we can just do (2), I don't see any reason to do anything else. I think we can trust database libraries to return valid dates (unless somebody knows of an example disproving this) and we can make having a valid date a precondition in the other direction. If we find some example showing that we really need to call timegm() (which is more or less universally available IME), we could do (1), but (2) seems preferable. Finally, I strongly dislike (3) because I don't see any reason why we should burden SOCI users with having to make any choices there -- this should just work correctly.
One last thing: we really need to have a (currently failing) test checking for this, to ensure that not only this (difficult to notice in normal use) bug is fixed, but that it remains fixed in the future.
Thanks again for looking at this!

Great, thanks - yes, the analysis has been fairly time-consuming but I think I have a decent handle on the issues now.
I'll have a look at doing (2) + test.

Was hoping to have got to this by now but have been diverted by other tasks.  This is still on my TODO list and hopefully I'll fit it in next week.


Add pull/pull_all/push, etc for screenboards.

Match the same style as we do with dog dash but use something like dog screen.

Issue is fixed in datadogpy. Closing.


add fix used by the vis editor for long perl patterns

The perl lexer used in the vis editor has a fix to deal with a regex pattern longer than a screen as introduced by the following commit
To be able to bring the lexers back in sync it would be great if this fix could be merged.

This should not happen anymore since lexer.delimited_range() was replaced by lexer.range(). The former function requires an ending delimiter in some specific cases1 that meet the Perl lexer criteria, and the latter2 does not.


hop-node: TransferRootsDb: Add timestamped keys sublevel db

Ready for review but I don't want to merge this in yet until the latest updates have been running in production for a while.

Changes LGTM 👍

would it be possible to DRY this up with the similar logic in ..

Should be possible, will think about it/implement it


Update password-policy-recommendations.md

Updated the minimum to 8 characters as to encourage users to think about a unique password, MIcrosoft recommends keeping a reasonable 8-character minimum length requirement.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7941

@kwekuako Please merge this Pr. Thanks


Cargo run command error in Windows 10

Command: cargo run --release
My changes:

cargo.toml

Before
[dependencies.amethyst]
version = "0.15.0"
default-features = false
features = ["json", "animation"]

[features]
default = ["metal"]
metal = ["amethyst/metal"]
vulkan = ["amethyst/vulkan"]

After
[dependencies.amethyst]
version = "0.15.0"
default-features = false
features = ["json", "animation", "no-slow-safety-checks"]

[features]
default = ["vulkan"]
empty = ["amethyst/empty"]
metal = ["amethyst/metal"]
vulkan = ["amethyst/vulkan"]

Log:
warning: unused import: GenericBox

src\entities\flier.rs:15:28
|
15 |         Directions, Flier, GenericBox, Motion,
|                            ^^^^^^^^^^
|
= note: #[warn(unused_imports)] on by default

warning: 1 warning emitted
Finished release [optimized] target(s) in 4m 03s
 Running `target\release\space-menace.exe`

[INFO][amethyst::app] Initializing Amethyst...
 DescriptorPool { size: 64, free: 62, freed: 0 }
[ERROR][rendy_descriptor::allocator] Not all descriptor sets were deallocated
[ERROR][rendy_descriptor::allocator] Descriptor pool is still in use during allocator disposal. DescriptorPool { size: 64, free: 63, freed: 0 }
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
[ERROR][rendy_resource::escape] Escape was dropped after a Terminal?
error: process didn't exit successfully: target\release\space-menace.exe (exit code: 101)
Note:
It opens the game window, but then it closes, and I tested it without the flag --release the error persisted
Version OS: Windows 10 20H2 19042.804

I have the same issue. It looks like it's similar to this issue here in theta-wave, which fixed it in its develop branch:
https://github.com/amethyst/theta-wave/issues/100

I had a similar problem with windows 10.
This looks like a dependency problem (just guessing).
I did the following to make it work:

Changed the cargo.TOML:
`
[dependencies.amethyst]
version = "0.15.3"
default-features = false
features = ["json", "animation", "no-slow-safety-checks"]

[features]
default = ["vulkan"]
metal = ["amethyst/metal"]
vulkan = ["amethyst/vulkan"]
`

Deleted the "Cargo.lock" file.
This allows to select newer crates.

Adjusted the resolution in resources\display_config.ron

Run it from with "cargo run" otherwise the programm will not find its resource and asset folder.


Not working with Recycler and Support Design 23.3

Hey!
The recycler is not working anymore when using the new support library 23.3:
compile 'com.android.support:design:23.3.0'
compile 'com.android.support:recyclerview-v7:23.3.0'
compile 'com.bignerdranch.android:expandablerecyclerview:2.1.1'

But using this it works:
compile 'com.android.support:design:23.2.0'
compile 'com.android.support:recyclerview-v7:23.2.0'
compile 'com.bignerdranch.android:expandablerecyclerview:2.1.1'

The problem is that when using 23.3 the recycler shows nothing. It gets entirely blank.
I don't know what is causing this.
Best regards and thanks for such nice library!

Hi @shinayser I haven't been able to reproduce this with our samples, any chance you could test it out there and see if you get the same results? otherwise maybe it's specific with your project.

I found a way to fix it on my case.
My recyclerview was set to "wrap_content" and working fine on 23.2.
After updating to 23.3 (and the new 23.4) the recycler was not wraping its content. I saw it because my recyelr had a padding of 2dp and when turning the develop option "Show layout bounds" (on the Developer  Options on my Android device) I could see the recycler with its 2dp padding (a small 4dp height line).
So, this is what I've done: I changed the recyclerview height from "wrap_content" to 2000dp (Any large number, 1024 probably will be more than enough).
Thanks again for such nice library.

Hey @shinayser, you may also want to try setting your RecyclerView's layout height to match_parent. Using an arbitrarily large size like 2000dp may put you at risk for not seeing all of the content in your RecyclerView on the screen.
Thanks for the kind words!


LMU3030 Protocol Error

I download the Traccar server and send a package of LMU3030 tracker, then i discover the IMEI and add in system. After that, the server report the error below:
2016-04-11 21:43:55 DEBUG: [52AD1666: 5082 > <IP_ADDRESS>] HEX: 020103be020000000000
2016-04-11 21:43:55  WARN: [52AD1666] error - Not enough readable bytes - Need 4, maximum is 0 - IndexOutOfBoundsException (... < CalAmpProtocolDecoder:132 < *:198 < ExtendedObjectDecoder:39 < ...)

Could you help me, please?
Thanks. All the best.

It doesn't looks like a valid CalAmp message.


jjb: switch to storage_method parameter

This fixes jobs, that still used want_ceph instead of the new storage_method parameter.
want_swift and want_ceph are deprecated for the Jenkins job.
the storage preference is passed via the storage_method parameter.

+1

so we don't want to support deploying ceph and swift?

@dirkmueller
the code that supports the storage_method variable and sets/unsets the want_{ceph,swift} variables for the mkcloud run is now in the openstack-mkcloud job definition since 10 months (Nov. 2015)  - so nobody missed that feature.
But I can add another option to the storage_method parameter like "ceph+swift" if that is wanted.

also we would need to teach the proposals to not grab all nodes and disks, so that some are left for the other storage service.


Question: How can I set up a custom environment?

Hello,
I came across this repository and was wondering what the steps and requirements would be to set up a custom environment and utilize the algorithm. Specifically, for example, a gym environment will require which functions?
Thanks

Greetings,
We have prepared documentation on how to customize environments and algorithms within the LightZero framework, which can be accessed through the following links:

Customize Environments Documentation
Customize Algorithms Documentation

Although these documents provide fundamental guidance, they may not encompass all details. Should you encounter any issues or have queries during the customization process, please do not hesitate to reach out to us. We are eager to assist you in ensuring a smooth customization experience.
Best wishes!

Thanks for getting back to me!
I appreciate the fast response and clear instructions. Another question I had, taking a loom at the documentation suggest two modes, board game and non board game atari based. Would it be possible to implement an environment that is two players but allows all actions as legal? I suppose I could simply pass all moves as legal. Adding onto this, could I encode a no-move as a 0 embedded plane? Do you have any suggestions for algorithms that are self-play but less data hungry?
I understand my questions are more beginner, and am asking for your instruction.
Thank you for the clarifiaction!

Certainly, an environment that allows two players to make any legal moves can be created. In the field of Multi-Agent Reinforcement Learning (MARL), such types of environments are quite common. For example, the PettingZoo library provides many examples of such environments. You can browse PettingZoo's GitHub repository for more related information. In the LightZero project, we have some ongoing pull requests, such as PR#149, PR#153, and PR#171. You can follow the updates on these pull requests, or contribute your own insights.
Regarding the encoding of "no action" as an embedding vector with a value of 0, this is technically feasible. However, this requires that the design of the environment explicitly clarifies how to interpret this condition and how to enable agents to recognize and learn a "no action" strategy.
For self-play algorithms seeking data efficiency, you might refer to research papers that focus on data-efficient reinforcement learning. For instance, data utilization can be enhanced through methods like model-based reinforcement learning, representation learning, and so on. Relevant resources can be found on awesome-model-based-RL.


haskellPackages.gogol{,*}: unbreak

The gogol packages have not been updates on hackage in a long time. Locally I use them by overriding the sources with latest master.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@sternenseemann can you take a look?

This override business is very unfortunate. Is there an explanation why there are no hackage releases? Can we please nudge upstream to do them? Maybe we can also add an assert that this override can be removed when a new release happens?
Besides that I don’t see any problems with this PR. Thank you for the contribution.


Document VolumeGroupSnapshots

This is a Feature Request
What would you like to be added
Update the volume snapshot page to explain VolumeGroupSnapshots
Why is this needed
VolumeGroupSnapshots are beta and we barely document them.
Comments
See https://github.com/kubernetes/enhancements/issues/3476
Linking to the CSI documentation is not enough (but we should to that too).
/sig storage

/language en
/triage accepted
/priority backlog

Some useful links to help with this task:

v1.32 Feature Blog on Volume Group Snapshots Moving To Beta: https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/
CSI Volume Group Snapshot documentation: https://kubernetes-csi.github.io/docs/group-snapshot-restore-feature.html


Cannot read property 'remember_me' of undefined

I just test this strategy and it wont work. When i go to any route it show the error message:
Cannot read property 'remember_me' of undefined
I followed exactly as the Usage in README.md

+1

Hi. I had this problem too. Turns out I had forgotten to use cookie-parser.

i had the same problem .. how to solve this?

@bryantobing12 see @Kudos5 comment.

Yeah i see. I forgot that cookie parser no longer bundled in express. Just Install cookie-parser and add cookieparser() to your middleware. Thank you


Address Issue #91

Fixes this.

Got caught up with other things.  This addresses the issue and will be closed.  Thanks Daniel.


Markdown Images are not rendered in pypi

Describe the bug
Images are not rendered in pypi from README.md file
Package link: https://pypi.org/project/shconfparser
Image Size:
sh_cdp_neighbour.png - 184 KB
sh_run.png - 855 KB
Expected behavior
Images need to be rendered, as shown in the following link
Github link: https://github.com/kirankotari/shconfparser
To Reproduce
Image from a link:
![show run to tree structure](https://github.com/kirankotari/shconfparser/blob/master/asserts/img/sh_run.png)
Testing using image from package path:
![show run to tree structure](/asserts/img/sh_run.png)
My Platform
Checked in Chrome 71 and IE 11
Additional context
The warehouse image link says Not Found

Thanks @ewdurbin

Hello, we have some problem with rendering GitHub status badges - https://pypi.org/project/pytorch-lightning/1.0.8/
so we tried to download all badges locally and add then to the package distribution on the fly (when the package is created) but this approach does not work as readme cannot take local images from the package - https://stackoverflow.com/a/46875147/4521646
so is there a way or suggestion on how to upload the images/badges to a public domain and later refer in the readme? Moreover, are these referred imaged downloaded by PyPI or what happens if the image changes over time or it is removed?

Hi @Borda - many users upload images to GitHub or another image hosting service (like imgur) or host the images on their own domain. PyPI will link directly to the image, so if the hosted image is changed or removed, it will change on PyPI as well.


fix(emitter): filter out api versions not specified by api-version

Description

add logic to filter out api versions newer than specified api-version
add unit tests
regen

fix #4775
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

Since we'll get available API versions from TCGC probably SdkPackage, I resolved the commentd by applying the suggested changes.


App/1235 remove offset and buy carbon tabs

Description

[x] Removes Offset and buy carbon tabs from app (Draft)
[x] Fixes a bug with server and client renders did not match

Related Ticket

Resolves #1235

Checklist

[x] I have run npm run build-all without errors
[x] I have formatted JS and TS files with npm run format-all

@biwano I still see all this padding on this container? Can the height match what you have on the Offset page?

Sorry I missed this comment. can you check again?


fix typo in kg

Two small fixes for the kg task

add hit10 metric
fix typo of feature description


Find parameters for disparity2depth

Hi,
I see that the function disparity2depth() has 2 parameters baseline and focal.
Do you know how to find these two parameters?
Since I use only a single 360 camera with Lidar to capture depths, there is no baseline between the two cameras.
Could you please suggest some approach to determine the baseline and focal?

You can use the default values provided by the function (baseline=1 and focal=1), which computes depth as inverse disparity.
Please note that the depth has an arbitrary scale. If you need a different scale, you can scale it however you like.


hmrOnInit is executed after component's ngOnInit

As you can see in the screenshot below, when my components are initialized the state isn't restored yet. Is this the wanted behavior? Perhaps could I hold the application bootstrap somehow until the state is restored?!
PS: I'm already using your latest modifications made on hmr and in the starter pack
PS2: On the log messages: "APP INITIALIZED" is at app module constructor and "COMPONENT INITIALIZED" at component ngOnInit

For now I am working around this by setting on localStorage a "wait" flag when hmrOnDestroy is fired and providing async getters for on my store service.
Suggestions for better solutions are welcome... :pensive:

use the constructor and check for module.hot.data

Thanks! Much better now...
But still no way to hold up the full app initialization until the data is restored? If not, fell free to close this issue, thanks Patrick!

so are you're saying you want to have data before bootstrapping? like for creating certain providers or something?

I might have a wrong idea of how the application lifecycle goes with HMR, but I tough that what I'm trying to achieve was already the default behavior. I believe that after the replacement occurs this should be the order:

All injectables are instantiated (so they can be provided in the module decorator)
App module is instantiated
App state is restored on store service (hmrOnInit)
Continue remaining bootstrapping process (root component initialization, etc)
Child component is initialized and already has it's cache restored (so it doesn't fire a http request to fetch data)

For me step 3 happens only after step 5, and that's my problem...

What is the resolution for this one? @cvsguimaraes I am seeing the same, how did you resolved this?

hmrOnInit is ran after ngOnInit by design but I can change it to happen before bootstrap and introduce hmrAfterBootstrap. If you need something to happen before bootstrap you can use the constructor as I mentioned

Thanks @gdi2290, which component lifecycle hook is called after hmrOnInit so we can be sure APP_STORE is already set?

hmrOnInit is called right after bootstrap is done

So ngAfterContentInit() will do. Thanks.
ngAfterContentInit() | Respond after Angular projects external content into the component's view.Called once after the first ngDoCheck().

Hello, I integrated the hmr with ngrx.  Since its in a ngOnInit, the store is populated -> triggers all the actions of load success before the hmrInit is injected.
Which is dumb considering the data is already in the store (not injected yet). Is there a way (example)  to inject the store before the onInit is called on components?
I tried in the constructor of the appmodule, but the module.hot.data is empty. I also tried ngAfterContentInit() its still being called before the hmrInit.
Tnx

Any response would be greatly appreciated.

this was my solution instead of hooked it after the bootstrap
`export class AppRootModule {
constructor(
public appRef: ApplicationRef,
private _m: NgModuleRef,
private _store: Store
) {
if (environment.hmr && module['hot']) {
module['hot']'accept';
if (module['hot']) {
if (module['hot']['data']) {
this.hmrOnInit(module['hot']['data']);
}
module['hot']['dispose'](store => {
this.hmrOnDestroy(store);
_m.destroy();
this.hmrAfterDestroy(store);
});
}
}
}
hmrOnInit(store) {
Log.info('------- HMR init');
if (!store || !store.rootState) return;
Log.info('HMR store', store.rootState);
// restore state by dispatch a SET_ROOT_STATE action
if (store.rootState) {
this._store.dispatch({
type: 'SET_ROOT_STATE',
payload: store.rootState,
});
}
if ('restoreInputValues' in store) {
store.restoreInputValues();
}
// this.appRef.tick();
Object.keys(store).forEach(prop => delete store[prop]);
}
hmrOnDestroy(store) {
	Log.info('------- HMR OnDestroy');
	this._store.take(1).subscribe(s => (store.rootState = { ...s, hmr: true }));
	const cmpLocation = this.appRef.components.map(
		cmp => cmp.location.nativeElement
	);
	store.disposeOldHosts = createNewHosts(cmpLocation);
	store.restoreInputValues = createInputTransfer();
	removeNgStyles();
}
hmrAfterDestroy(store) {
	Log.info('------- HMR AfterDestroy');
	store.disposeOldHosts();
	delete store.disposeOldHosts;
}

}`


Make Lynch Vote only work in Mafia Game Chat

see title.

Added in https://github.com/dylanpiera/Mafia-Quickplay-DiscordBot/commit/3b12a76f4367f662f43644fa12539d17807df5ad


RHEL workflows updated.

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   78.78%   78.78%
=======================================
  Files          22       22
  Lines        1499     1499
=======================================
  Hits         1181     1181
  Misses        244      244
  Partials       74       74

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 c965577...cfaccd9. Read the comment docs.


Make debug log outputs neater

While debug feature is helpful for debugging, there left some boring jobs like:
use erg_common::color::*;
log!("{GREEN}[DEBUG] msg {RESET}");

Currently, debug outputs look like:

Once we forget to end with "msg {RESET}", output are painted in all green and it is a little bit difficult to see.
Also, handwritten [DEBUG] is not aligned due to different length of file/line info.
Thus, I introduced these fix in log! macro
Changes proposed in this PR:

Inserting [DEBUG] in front of file/line information to log in default.
Forcing color reset for every log!
Adding directives in log! to switch colors we like.
Shorthand for green output(info) and red output(err)(for debugging, maybe warn is not necessary)
(- documentation for log! directives above)

With these utilities, we can easily write neat logs with:
log!(info "compiler reached {}", fn_name!());
log!(err "error occured in {}!", fn_name!());

and outputs look like:

@mtshiba

Pretty good! Thank you!


Adding ConditionalTask support in agent.

If RunMode of a TaskInstance is specified be 'Custom', the task will only run if the conditions evaluate to true.
Retained back-compatibility by falling back to the old properties if RunMode is 'Undefined'.

@patrickcarnahan please review

@patrickcarnahan Please review this PR

@ericsciple can review

what does the UI look like?

Attached are the proposed UI screenshots

have you considered the server only sending down conditions instead of runmode + conditions?
for example, $(agent.jobstatus) contains the current job status. so "Default" could be represented by something like $(agent.jobstatus) != failed.
otherwise it seems like we are setting ourselves with a limitation. e.g. consider a request for rollback + condition.

Github seems to be facing some issues (HTTP500 response). So responding via email.
Yes, the ConditionEvaluator works on the latest updated recursively expanded set of variables available at every step.
Regards,
Sandeep.
From: ericsciple<EMAIL_ADDRESS>Sent: Wednesday, December 7, 2016 1:39 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Sandeep Venkata<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Adding ConditionalTask support in agent. (#711)
@ericsciple commented on this pull request.

In src/Agent.Worker/StepsRunner.cshttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fpull%2F711%23pullrequestreview-11670707&data=02|01|savenkat%40microsoft.com|ce35fe2288da46a3581a08d41e13c805|72f988bf86f141af91ab2d7cd011db47|1|0|636166517685817415&sdata=3kHd5KUj0ci0ZHP9ZiZ4p4T7CEFL%2Fo%2FBk16sjoVpfy4%3D&reserved=0:

               return step.Finally || ShouldRunStepBasedOnRunMode(step, stepFailed, criticalStepFailed);

       }

   }

   private static bool ShouldRunStepBasedOnRunMode(IStep step, bool stepFailed, bool criticalStepFailed)

   {

       switch(step.RunMode)

       {

           case RunMode.Default:

               return !stepFailed;

           case RunMode.Always:

               return !criticalStepFailed;

           case RunMode.Rollback:

               return stepFailed && !criticalStepFailed;

           case RunMode.Custom:

               return !stepFailed && TaskConditionsEvaluator.AreConditionsSatisfied(step.Conditions, step.ExecutionContext.Variables, step.ExecutionContext);

the agent supports recursive variable expansion. the agent stores the original variables and re-evaluates expansion between steps. does this use the expanded variables?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fpull%2F711%23pullrequestreview-11670707&data=02|01|savenkat%40microsoft.com|ce35fe2288da46a3581a08d41e13c805|72f988bf86f141af91ab2d7cd011db47|1|0|636166517685817415&sdata=3kHd5KUj0ci0ZHP9ZiZ4p4T7CEFL%2Fo%2FBk16sjoVpfy4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXMOtJFRBaaoYhXLlo37gTdQyvfzjhDQks5rFcD1gaJpZM4LFUHb&data=02|01|savenkat%40microsoft.com|ce35fe2288da46a3581a08d41e13c805|72f988bf86f141af91ab2d7cd011db47|1|0|636166517685817415&sdata=qZw2Ceos1nV2nrYXskL3q3f%2FO7Zv%2BEX7QVcIbOb72ns%3D&reserved=0.

Github seems to be facing some issues (HTTP500 response). So responding via email.
The idea is that Conditions are supported only when RunMode is set to ‘Custom’.
Any other RunMode doesn’t allow you to set Conditions. There are checks in place for this on the server side
Regards,
Sandeep.
From: ericsciple<EMAIL_ADDRESS>Sent: Wednesday, December 7, 2016 1:33 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Sandeep Venkata<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Adding ConditionalTask support in agent. (#711)
have you considered the server only sending down conditions instead of runmode + conditions?
for example, $(agent.jobstatus) contains the current job status. so "Default" could be represented by something like $(agent.jobstatus) != failed.
otherwise it seems like we are setting ourselves with a limitation. e.g. consider a request for rollback + condition.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fpull%2F711%23issuecomment-265257334&data=02|01|savenkat%40microsoft.com|61440d4d61fc4e511d4708d41e12dc0b|72f988bf86f141af91ab2d7cd011db47|1|0|636166513722474328&sdata=PQZwpkY6%2BoiylisXkcHZbM3z%2FXGOzs%2FpO61TAwICuoM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXMOtGwdFcriwhupj4yFsPOnEco2Z5wzks5rFb9mgaJpZM4LFUHb&data=02|01|savenkat%40microsoft.com|61440d4d61fc4e511d4708d41e12dc0b|72f988bf86f141af91ab2d7cd011db47|1|0|636166513722474328&sdata=PHxJYz9KcRmzVSO6lzMOCNpffm5mUPZ8GTvD%2F9w2Pp4%3D&reserved=0.

i think we're saying different things. i'm saying have you considered eliminating the RunMode enum altogether and having a design that always sends down a list of conditions - regardless whether it is custom conditions or well-defined conditions
otherwise it seems like you are designing a limitation. e.g. consider a user attempting to do rollback + custom condition - not supported with the design you currently have.

There's a few issues from the experience and the implementation.
In both cases, we don't want to paint ourselves into a corner where we can't innovate on it.  On other words, let's make sure it's the right subset that we can augment.
From the experience, the defined experience (which gets persisted to def json so need to consider going forward) is a bit limiting.  For example, you can't put conditions on onError tasks (I don't like rollback since that's a deployment term - not generic step term).  So, we're going back and forth with Chris on a few options.  Either have success, always, onFailed in dropdown (no custom condition) and don't show conditions if always .... OR, have the UX simply gen conditions on drop down option so you can augment.  We will iterate on experience.
Implementation wise, we need to make sure an expression string is persisted.  Consider yaml.  Consider showing the def json.  The UX is simply a UX generator.  We need the option to extend the expressive capabilities later.  We also need to share that expression engine with demands code.  The other area we need more expressive capabilities.
So we need to take a minor reset.  Let's start with the experience then code after that.  Taking offline.

... we also need to discuss what it means for the web UI to show expressions but still have an older agent.  Compat.  Demands?
For that reason, always run needs to stay a bool checkbox.  Does the server demand a minimum agent of 2.111 if expressions beyond always run are used?


Return user agent string for remote logging

Return User Agent string while remote logging, which can be used for statistic / debugging purposes.

Added via pr https://github.com/i-break-codes/logerr/pull/18


New version: Bruno.Bruno version 1.7.1

Pull request has been created with komac v2.0.2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Duplicate of https://github.com/microsoft/winget-pkgs/pull/137183


Revenue per content

Nice code! Just some comments

I'm merging it due to a presentation on Interledger Summit 2023 - Costa Rica.
All my comments will be transformed into issues that must be handled soon.


CMake: forbid building for target architectures other than x86_64

Resolves https://github.com/ethereum/evmjit/issues/17.
Supports https://github.com/ethereum/webthree-umbrella/issues/626.

LTGM.
@chfast ASIDE - Are you using both CircleCI and TravisCI for much the same thing?     I gave up on CircleCI myself a few weeks back, because the automated Git caching was always screwing up for me.

Yep. I just left circle for no reason.
On Mon, Jul 11, 2016, 19:12 Bob Summerwill<EMAIL_ADDRESS>wrote:

LTGM.
@chfast https://github.com/chfast ASIDE - Are you using both CircleCI
and TravisCI for much the same thing? I gave up on CircleCI myself a few
weeks back, because the automated Git caching was always screwing up for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/evmjit/pull/68#issuecomment-231800184, or mute
the thread
https://github.com/notifications/unsubscribe/AAi_xGoticAiwbaBf99WtCgNBlNu8dJiks5qUnl3gaJpZM4JJFcc
.


add ci and tags for releases

what

what

I meant to do so as I can just grab your jar file directly on GitHub releases tab on your repo without going through CurseForge.
You don't have to build the jar file and upload it to GitHub yet again, as there are automation tasks that you can use in GitHub Actions, so that everytime you tag a release it would just build the files for you.
I might be able to whip up a PR for this, but for now I want to hear your opinion on this.

I don't want to deal with maintaining a CI pipeline on github for this (or any) of the projects.  CF is the only supported distribution center.


I don’t understand the  query results

What does the null  column mean here

Maybe Nullable?

@Amber1990Zhang It is recommended to use MySQL firstly.


Mac Installer creates directories with incorrect permissions

When installing Elm on a freshly installed MacOS Sierra 10.12.2, the Elm Mac Installer for Elm 0.18 will create the directory /usr/local/bin/ with the permissions drwx------. This means the elm executables will not be found on the PATH when running in user mode:
HackbookPro:~ alex$ elm --version
-bash: elm: command not found
HackbookPro:~ alex$ ls -la /usr/local/
total 0
drwxr-xr-x   3 root  wheel  102  5 Feb 23:27 .
drwxr-xr-x@ 10 root  wheel  340  5 Feb 23:27 ..
drwx------   7 root  wheel  238  5 Feb 23:30 bin
HackbookPro:~ alex$ ls -la /usr/local/bin
ls: bin: Permission denied
HackbookPro:~ alex$ sudo ls -la /usr/local/bin
Password:
total 85536
drwx------  7 root  wheel       238  5 Feb 23:30 .
drwxr-xr-x  3 root  wheel       102  5 Feb 23:27 ..
-rwxr-xr-x  1 root  wheel   2055692 11 Nov 02:46 elm
-rwxr-xr-x  1 root  wheel  15449760 11 Nov 02:46 elm-make
-rwxr-xr-x  1 root  wheel  11310156 11 Nov 02:46 elm-package
-rwxr-xr-x  1 root  wheel   7592372 11 Nov 02:46 elm-reactor
-rwxr-xr-x  1 root  wheel   7378676 11 Nov 02:46 elm-repl
HackbookPro:~ alex$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
HackbookPro:~ alex$ sudo elm --version
0.18.0

This directory should be created with the permissions 'drwxr-xr-x'. This will allow users to find the executables on their path.

Interesting! I wonder if a lot of people aren't affected by this because npm installer does the same thing for global installs, and people have already fixed it for that directory?

I think I am in a similar position. I did a clean install on a new OSSierra build. brew doctor returns no errors. When I try to install a package:
elm package install
-bash: /usr/local/bin/elm: Permission denied

Can anyone suggest a workaround?

This should be an issue open over at https://github.com/elm-lang/elm-platform, not here in the compiler repo. @alexspurling, move it over?

I agree with @jvoigtlaender. Apple changed the permissions of that directory with one of the new OSes and it is not 100% clear what the alternative location should be. In any case, this is def an elm-platform thing, which is where all the installers live.


Post-transfer updates

Codecov Report

Merging #31 (0f2d8ff) into main (232ec00) will decrease coverage by 2.66%.
The diff coverage is n/a.

:exclamation: Current head 0f2d8ff differs from pull request most recent head 0c92a1c. Consider uploading reports for the commit 0c92a1c to get more accurate results

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
- Coverage   75.75%   73.09%   -2.66%
==========================================
  Files           3        3
  Lines         165      171       +6
==========================================
  Hits          125      125
- Misses         40       46       +6

Impacted Files
Coverage Δ

src/Language/Haskell/TH/TestUtils.hs
78.37% <ø> (-3.32%)
:arrow_down:

src/Language/Haskell/TH/TestUtils/QState.hs
29.41% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


cmd/go: 'go mod vendor' does not fail on case-insensitive import collision

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
During the investigation of #38342, I discovered the following ux quirk:
On a case insensitive filesystem: (I am using vfat)
package main

import (
	_ "example.com/Foo"
	_ "example.com/foo"
)

func main() {}
-- go.mod --
module play.ground

go 1.14

require (
	example.com/foo v0.1.0
	example.com/Foo v0.1.0
)

replace (
	example.com/foo => ./foo
	example.com/Foo => ./!foo
)
-- foo/go.mod --
module example.com/foo
-- foo/foo.go --
package foo
-- !foo/go.mod --
module example.com/Foo
-- !foo/foo.go --
package Foo

go mod vendor

What did you expect to see?
main.go:5:2: case-insensitive import collision: "example.com/foo" and "example.com/FOO"

What did you see instead?
go mod vendor succeeds, but go build fails, and one must flush vendor to fix things:
go build

main.go:5:2: case-insensitive import collision: "example.com/foo" and "example.com/FOO"

I will work on this

@jayconrod any chance to get a review? :worried:

@justplesh I think @bcmills would be a better reviewer for this. I haven't read through the full discussion in #38342 or thought about all the implications.

@bcmills would appreciate


Build script changes

Added "clean" and  "makeZWFSFriendly" scripts
makeZWFSFriendly is named so there are never any questions later as to why/what it does

https://github.com/julianharty/testing-heuristics/issues/19


[NP-515] DocuSign Integration

Currently this is in a state of partial completion. This is reflected in the documentation and there is a note for contributors.
What works:

OAuth2 flow for DocuSign
Storing DocuSign session keys
Generating sanitized documents in DocuSign "HTML"
Sending envelope requests for embedded signing flow
(to the user in context, from a designated user)

What's missing

Sending documents from context user to another user on the system
DocuSign Connect handler to verify signing has completed
Scheduled task for refreshing DocuSignSession tokens
Allow user to switch from their default DocuSign account

Oh, almost forgot to mention, this also adds alias support to PropertyParser.

Closing until needed.


Include in Readme how to Pass Custom Arguments to llama_cpp.server in Docker

Title:
Issue with Passing Custom Arguments to llama_cpp.server in Docker
Issue Description:
Hello abetlen,
I've been trying to use your Docker image ghcr.io/abetlen/llama-cpp-python:v0.2.24 for llama_cpp.server, and I encountered some difficulties when attempting to pass custom arguments (--n_gpu_layers 81, --chat_format chatml, --use_mlock False) to the server through Docker.
Steps to Reproduce:

Pull the Docker image: docker pull ghcr.io/abetlen/llama-cpp-python:v0.2.24

Run the container with custom arguments:
docker run --rm -it -p 8000:8000 \
  -v /home/jaredquek/text-generation-webui/models:/models \
  -e MODEL=/models/tulu-2-dpo-70b.Q5_K_M.gguf \
  --entrypoint uvicorn \
  ghcr.io/abetlen/llama-cpp-python:v0.2.24 \
  --factory llama_cpp.server.app:create_app --host <IP_ADDRESS> --port 8000 --n_gpu_layers 81 --chat_format chatml --use_mlock False

This results in an error: Error: No such option: --n_gpu_layers.

Expected Behavior:
I expected to be able to pass these arguments to the llama_cpp.server application inside the Docker container.
Actual Behavior:
The uvicorn command does not recognize these arguments as it's designed for the ASGI server, not the llama_cpp.server application.
Potential Solutions:

Modify the Dockerfile or application configuration to accept these arguments.
Provide guidance in Readme on how to correctly pass additional arguments or configure the server with these settings.

I would appreciate any assistance or guidance you could provide on this issue.
Thank you for your time and for maintaining this project.
Best regards.

you could try my container:
https://hub.docker.com/r/3x3cut0r/llama-cpp-python
i implemented all supported options to an env variable.
tell me what do you think and please tell me any bugs.

Thanks for ur attention. So I tried the Docker but the GPU isn't being activated even though the uvicorn server starting. This is my Docker run:
    --name llama-cpp-python \
    --cap-add SYS_RESOURCE \
    -v /home/jaredquek/text-generation-webui/models:/models \
    -p 8000:8000/tcp \
    3x3cut0r/llama-cpp-python:latest \
    --model /models/tulu-2-dpo-70b.Q5_K_M.gguf \
    --n_gpu_layers 81 \
    --chat_format chatml \
    --use_mlock False
``` Does the Docker image run Cuda acceleration by default or I have to do some other thing? Thanks!

Unfortunately, this alpine based image is built with these CMAKE_ARGS="-DLLAMA_BLAS=ON -DLLAMA_BLAS_VENDOR=OpenBLAS -DLLAMA_AVX=OFF -DLLAMA_AVX2=OFF -DLLAMA_F16C=OFF -DLLAMA_FMA=OFF".
This means it is optimized for older CPUs and GPU support is deactivated.
An image optimized for GPUs with cuda would need a different base image anyway. Unfortunately I don't have an Nvidia GPU myself and therefore can't test or deploy anything. But maybe i can have a look activating gpu support (without cuda). But then llama-cpp-python needs to be recompiled after image creation. or i could deploy i on another tag. need to think about that.
I have also not yet dealt with your question about parallel requests. But I would also be very interested into that too.
Sorry

Thanks! Perhaps that's true with abetlen's original image too - not for Cuda? Have to look deeply. I have managed to get the non Docker version of the server working already. However I still hope to find out about the parallel requests.

@jaredquekjz there are two options really

Use environment variables instead of cli args. This is the slightly more idiomatic solution for containers and every cli argument has a corresponding environment variable, so --n_gpu_layers is equivalent to N_GPU_LAYERS.
Change your entrypoint to python in the docker command and run with -m llama_cpp.server followed by the cli args, this should allow you to pass either cli or environment variable arguments.

The benefit to using the default entrypoint and environment variables with the official image is that it includes a compiler and will rebuild the image for any cpu architecture you deploy it to ensuring that it's going to be as fast as or faster than pre-built binaries.

@jaredquekjz there are two options really

Use environment variables instead of cli args. This is the slightly more idiomatic solution for containers and every cli argument has a corresponding environment variable, so --n_gpu_layers is equivalent to N_GPU_LAYERS.
Change your entrypoint to python in the docker command and run with -m llama_cpp.server followed by the cli args, this should allow you to pass either cli or environment variable arguments.

The benefit to using the default entrypoint and environment variables with the official image is that it includes a compiler and will rebuild the image for any cpu architecture you deploy it to ensuring that it's going to be as fast as or faster than pre-built binaries.

this is pretty cool, are all the server arguments can be set via ENV variable? (all capitalized?)


Readme / Dev setup instructions missing details

[ ] Detail which of Android Studio and SDK to install

[ ] what API level is currently supported

[ ] What JxCore -jxv level is currently supported.

[ ] what is the right path for env vars: eg: export ANDROID_HOME=/<installation location>/Android/sdk doesn't exist

[ ] Update: Ensure npm v3.x+ is NOT installed on Ubuntu

Required packages on Ubuntu:
sudo apt-get install lib32stdc++6
sudo apt-get install lib32z1

Install latest Android Studio or android-sdk
For Mac: brew install android-sdk
It also sets your ANDROID_HOME correctly

Current target level is android-21

It's better to install latest version of jxcore (currently it is 3.1.2b)
For Mac it can be dowloaded from here

If you have already installed android-sdk the correct ANDROID_HOME sets automaticaly
Otherwise set ANDROID_HOME to /<installation location>/android-sdk and PATH to ${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools
E.g. on my machine it is
export ANDROID_HOME=/usr/local/Cellar/android-sdk/24.4.1_1/
export PATH=${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools


[Docs]: Uncomment instructions for --server-side

Is there an existing issue already for your request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new documentation enhancement to be evaluated.

What problem in the existing documentation this issue aims to solve?
We do not explain what to do when updating to 1.22.2 and 1.21.4 due to future Kubernetes 1.29 support.
Describe what additions need to be done to the documentation
We need to add info about server-side apply of manifests and K8s 1.29 supported in 1.22
Describe what pages need to change in the documentation, if any

https://cloudnative-pg.io/documentation/current/installation_upgrade/
https://cloudnative-pg.io/documentation/current/supported_releases/

Describe what pages need to be removed from the documentation, if any
No response
Additional context
No response
Backport?
Yes
Code of Conduct

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

This was already fixed on #4114


Merge PR if no bundle is added and ci.yaml is updated

Due to a Tekton limitation, we can't execute a merge task if any previous tasks have been skipped. This usually happens when no bundle is added and ci.yaml file is updated. Until Tekton enables this workflow I am temporarily moving the merge task into finally section.
The issue has been created in Tekton upstream to fix this issue https://github.com/tektoncd/pipeline/issues/7680
JIRA: ISV-4476

Are we sure this won't lead to unintended merging? If some of the previous tasks fail (e.g. validation or preflight), shouldn't the PR not be merged? But with this change all PR will be merged as long as the ci.yaml has merge set to true.

Are we sure this won't lead to unintended merging? If some of the previous tasks fail (e.g. validation or preflight), shouldn't the PR not be merged? But with this change all PR will be merged as long as the ci.yaml has merge set to true.

Of course you are right and than you for catching it!! I added one more condition to merge it only when pipeline passed.


Basemap selector

This PR adds a toggle between default and satellite map.
One thing to note is that when switching to the default style the satellite layer is removed. When the same behaviour was implemented toggling it's visibility things started going weird: the map flickers, the tiles load again... I remove it for these reason.

Also, it seems like the design changed a bit: https://www.figma.com/file/WxYMmJrUZAgV6f0Csmt8fK/LG-Tool---Work-in-progress?node-id=1724%3A40086

Also, it seems like the design changed a bit: https://www.figma.com/file/WxYMmJrUZAgV6f0Csmt8fK/LG-Tool---Work-in-progress?node-id=1724%3A40086

That explains why I couldn't find the design 🥲

There is an issue with the tooltips (see screenshots).


Add transfermarkt-datasets to projects section

Closes #78

I find especially exciting to get a dedicated public dataset collection which could take form of :

Public Kaggle dataset
Public Motherduck

what's your opinion about that @davidgasquez ?

Seems to become a pattern indeed! I think I'd keep it as they are for now. If there are a couple of datasets more, we could think about doing a "DuckDB Compatible Datasets"! :sweat_smile:


Update Best Practices and FAQ.md

@rnystrom Per recent internal discussions 😄

@jessesquires you're lightning speed. I was going to suggest doing this 😆


probes: refactor bpftool feature macros generation

The first commit removes code from the ProbeManager that shells out to bpftool and replaces it with a pure Go API using the cilium/ebpf features package and go templates.
The second commit removes the no longer needed bpf_features.h file.
Fixes: #20743

/test

/test

Rebased onto master to pick up the recent changes to cilium-cni installation. The following error occurred on 4.9:
2022-10-28T13:45:36.370192057Z Removing active Cilium CNI configurations from /host/etc/cni/net.d})...
2022-10-28T13:45:36.370209112Z find: '/host/etc/cni/net.d': No such file or directory

/test

k8s-1.23-kernel-5.4 and k8s-1.16-kernel-4.9 are both hitting #21735

/test

4.19 failure should be fixed by https://github.com/cilium/cilium/pull/21981. Marking ready.


feat: allow to use a non-root S3 bucket location

This allows to direct cratery to use a 'subdirectory' to store its data on S3.  This is useful to not have to dedicate a bucket to cratery (which may or may not be appropriate). E.g. instead of using my-cratery-bucket/ we can now use my-multipurpose-bucket/cratery/.

Thanks for this project! While evaluating it, came across a few things that would make life easier for me, so here is the first one :)


[fpga] Multiple top_pkg modules cause FPGA build to pick up Ibex UVM parameters

In the process of integrating a new FPGA board, I started experimenting with the FLASH_PAGES_PER_BANK parameter as suggested in #2171.
I found that the top_pkg.sv picked up by the FPGA build lives in:
hw/vendor/lowrisc_ibex/dv/uvm/icache/dv/top_pkg.sv
The expected path is:
hw/top_earlgrey/rtl/top_pkg.sv

Is there a way to exclude the uvm folders from the FPGA build?
Looking at the dependencies hw/ip/rv_core_ibex/rtl/deps.f points to the following dependencies:

-f ${PRJ_DIR}/hw/vendor/lowrisc_ibex/rtl/ibex.f
-f ${PRJ_DIR}/hw/vendor/lowrisc_ibex/rtl/deps.f

However the hw/vendor/lowrisc_ibex/rtl/ folder only has ibex_core.f.  Are ibex.f and deps.f expected to be generated dynamically?

I fixed that yesterday in https://github.com/lowRISC/opentitan/pull/2511 (I think), do you have an up-to-date version of OT?

Verified #2511 fix. Thanks @imphil!


Use a message bus driven architecture

I have an issue with the Reflux event handling architecture.
None of these problems are necessary and can be solved in Reflux by adopting a message bus driven architecture and allowing the user to customize event behavior like order of execution and synchronicity themselves, with the only breaking change that Reflux.setEventEmitter will be deprecated.
What we need to change is to interface with a single application wide message bus instance instead of a unique event emitter per action.
Example: createAction.js
var PublisherMethods = require('./PublisherMethods');
var MessageBus = require('./MessageBus.js');
// Note: Let users customize the message bus instance via
// Reflux.setMessageBus, instead of a type with setEventEmitter

function createAction (name) {
    var functor = function () {
        // Let the bus completely decide how emitting is performed.
        // For even better control, we pass in the whole functor as context data.
        return MessageBus.emit(functor, arguments);
    };
    functor.name = name;  // Store event name as context data
    extend(functor, PublisherMethods);  // PublisherMethods also interfaces with MessageBus
    return functor;
}

module.exports = createAction;

Note that we must update publisher/listener methods to interface with the message bus too.

The message bus now owns all the event logic, enabling any users like myself control the order of execution and synchronicity without modifying Reflux.

We can easily implement a message bus that maintains the event logic Reflux currently have.

What is a message bus?
A message bus basically provides the same interface as an event emitter, with the one exception that it's an instance and not a type to be instantiated per action (although I would personally vouch for a subscription based interface over a listener interface). This way the bus may store state if it so wishes, controlling things like order of execution or synchronicity.

For instance, we could implement a message bus that works like facebooks Dispatcher, for those you wants to further align with the Flux architecture.

Also, instead of emitting only an event name, we may extend the contract by passing in a context hash (the action functor) to the event emitting function of the message bus, where the name is just a property among many others. This gives the message bus even more control and flexibility. For instance, the Reflux specific "sync" property can be handled so that synchronicity can be controlled per action by customization. Or a channel property could be added, for those who want such an architecture.
Please let me know what you think about this!

I believe @LongLiveCHIEF is working on something like this in 0.3.x. So I'm culling this issue.


RoboVM 1.2.0

Google Analytics library is broken in RoboVM 1.2.0
libgoogleanalytics.a
16:03:20.799 [DEBUG] [org.gradle.api.Task]     -force_load /Users/appsure/Documents/Apps/app/ios/build/libs/ios/libObjectAL.a -framework MobileCoreServices
16:03:23.128 [ERROR] [org.gradle.api.Task] Undefined symbols for architecture armv7:
16:03:23.128 [ERROR] [org.gradle.api.Task]   "_inflate", referenced from:
16:03:23.131 [ERROR] [org.gradle.api.Task]       +[GAICompressionUtil gai_dataByInflatingBytes:length:isRawData:] in libgoogleanalytics.a(GAICompressionUtil.o)
16:03:23.303 [ERROR] [org.gradle.api.Task]      (maybe you meant: _str_inflater_20_3D_3D_20null_00_ptr, _str_inflater_20_3D_3D_20null_00 , _[j]str_inflater_20_3D_3D_20null_00[ldcstring] , _str_inflateImpl_00 , _Java_java_util_zip_Inflater_inflateImpl___3BIIJ , _str_inflate_00 , _Java_java_util_zip_Inflater_inflateImpl )
16:03:23.304 [ERROR] [org.gradle.api.Task]   "_deflate", referenced from:
16:03:23.306 [ERROR] [org.gradle.api.Task]       +[GAICompressionUtil gai_dataByCompressingBytes:length:compressionLevel:mode:] i

I'm having the same issue. Have you made any progress on this?

Unfortunately not, having this issue with a few bindings. Maybe they forgot an essencial lib?

I was having problem when trying to run any iOS project after upgrading RoboVM 1.2.0 but I postponed debugging it until I was ready to submit an update to the App Store. Maybe this was the culprit? If so this worries me a lot, as I cant update any app without Analytics, so maybe we have to downgrade to RoboVM 1.1?
Best

On May 13, 2015, at 10:52, voidstarfire<EMAIL_ADDRESS>wrote:
Unfortunately not, having this issue with a few bindings. Maybe they forgot an essencial lib?
—

Original issue:
“
Google Analytics library is broken in RoboVM 1.2.0
libgoogleanalytics.a
16:03:20.799 [DEBUG] [org.gradle.api.Task] -force_load /Users/appsure/Documents/Apps/app/ios/build/libs/ios/libObjectAL.a -framework MobileCoreServices
"

It's a real shame no one is keeping the bindings updated, it's going to kill RoboVM.

I fixed all the breaking changes in LibGDX 1.6.0 which would appear to not work with RoboVM 1.1.0 so it doesn't look like I can roll back.

Are you saying the bindings now work with 1.2.0?

I'm not using Google Analytics in my projects but what you're describing may be a libGDX Gradle configuration problem as currently libGDX will automatically delete any 3rd party .a library from the robovm.xml descriptor when building the project via Gradle.
Have a look at https://github.com/libgdx/libgdx/issues/3027 and try the workaround see if that fixes your issue.

Yes I got around that by doing this in iOS gradle:
//For analytics //Can be done with for loop *.a
task copyStaticLib(type: Copy) {
from 'libs/libgoogleanalytics.a'
into 'build/libs/ios/'
}

Check out this:
https://github.com/libgdx/libgdx/issues/3063

Still doesn't resolve the issue with static libraries not working in version 1.2.0

I'm using 2 static libraries with RoboVM 1.2.0 with no issues. Have you tried the workaround on the referred JIRA?

Did you try BlueRiver analytics? It's not a problem with the library being overridden it's a problem with RoboVM (me thinks) or the library being out of date hmm.

I have almost not tried/used 1.2.0 yet, but I’ve had an issue in the past with the bindings being outdated, so I had to update the RoboVM version on the build.gradle of the bindings (outside Eclipse, on the root folder of the bindings) and then Gradle-Refresh All on the project of the bindings so it started using the correct versions of the dependencies.
On that occasion there was no crash/problem due to this issue, but when building the final .IPA it would add 2 versions of the same libraries (the one referenced by the lib, and the one referenced by my game).
Best

On May 13, 2015, at 11:31, voidstarfire<EMAIL_ADDRESS>wrote:
Did you try BlueRiver analytics? It's not a problem with the library being overridden it's a problem with RoboVM (me thinks) or the library being out of date hmm.
—
Reply to this email directly or view it on GitHub https://github.com/BlueRiverInteractive/robovm-ios-bindings/issues/174#issuecomment-101687154.

I'm not using Google Analytics. I use BlueRiver's binding classes but I always download the native libraries from the original sources. Sorry not to be able to help you.

Ah the Google Analytics library for BlueRiver is out of date. The new one even has a different name. Thanks Rotter, not sure what you mean. I've updated all that needs to be updated, ./gradlew clean and deleted the RoboVM cache. Seems it's on 1.2.0; just fails; Are you using Google Analytics?

See this thread:
http://www.badlogicgames.com/forum/viewtopic.php?t=19318&p=81107
axl had recompiled the analytics jar with the missing lib. I've just tried it and it fixes the problem.

I can confirm that it now compiles but now I have the following error:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[GAITrackerImpl send:]: unrecognized selector sent to instance 0x1897ba20'

Please add z to your robovm.xml libs node for the time being.
Google Analytics is subject to be released as RoboPod shortly. Please check the https://github.com/robovm/robovm-robopods issue tracker for more.
BTW essentially all of the bindings here will be deprecated soon and removed in favor of the updated RoboPods. Facebook has already been released as a robopod.


Launch Party UI - External links

[x]  Link to the Twitter whitelisting request
[x] What pre-filled message do we want?
[x]  Link to UbiquiStick open seas NFT page
[x]  Link to buy/sell the liquidity pool tokens
[x]  Link to buy/sell the uAR-ETH pool

@pavlovcik what do you think about a Twitter pre-filled message for when the user is not whitelisted?
Right now it's like: "@UbiquityDAO I want to be whitelisted for the  launch party https://uad.ubq.fi/launch-party"

[ ]   Link to the Twitter whitelisting request
[ ]  What pre-filled message do we want?

https://docs.google.com/document/d/1beWQE4fu0akWtpB3XbRLdD66vKIb0bgyOAgAUQyYMxk/edit
For now you can imagine that we will use "Tweeting to be eligible for the #ubiquistick NFT whitelist @UbiquityDAO"

[ ]   Link to UbiquiStick open seas NFT page

https://opensea.io/collection/the-ubiquistick-v3 temporary link not sure why its V3 but you can get a preview anyways

[ ]   Link to buy/sell the liquidity pool tokens

We will call this bonding because thats what OHM calls it.

[ ]   Link to buy/sell the uAR-ETH pool

@pavlovcik what do you think about a Twitter pre-filled message for when the user is not whitelisted?
Right now it's like: "@UbiquityDAO I want to be whitelisted for the launch party https://uad.ubq.fi/launch-party"

Prefilled message dope idea. Want to use this domain: https://uar.farm

If we end up deciding to create a custom domain let's create another issue to update the links; I'm closing this for now.


fix: non-ledger wallets unable to import accounts

Description
Fixes non-ledger wallets (e.g native) unable to load any accounts in "import accounts" in account management.
Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
closes #6906
Risk

High Risk PRs Require 2 approvals

Low risk.

What protocols, transaction types or contract interactions might be affected by this PR?

Testing
Check non-ledger wallets can load accounts in import accounts drawer in account management (metamask excluded)
Engineering

Operations

Screenshots (if applicable)
https://github.com/shapeshift/web/assets/125113430/26670856-1690-44ca-a7b7-7464f4982ec0

TY ser, I've broken out this feedback into a new ticket so we can keep things moving forwards:
https://github.com/shapeshift/web/issues/6918


wanted: jmillikin/rules_{bison, m4, flex}

We are currently transitioning our (now deprecated) bazel-eomii-registry to become a fork of the bazel-central-registry. We want to upstream the modules that are not reliant on our rules_ll to this repo, since I believe they would be useful for more users.
The repos rules_m4, rules_flex and rules_bison are essentially always used together, so I'm tracking progress for all three here. I intend to first add some proper testing that our original module files lacked. Then I'll submit the patched variants to this repo and then upstream the patches to the original repos.
The repos in question are for instance used by carbon and will in general likely be used by Bazel projects implementing programming languages. We also have a module for Carbon itself (very experimental, here), but testing that will likely not be straightforward and Carbon is IMO too unstable to become a module for now.

@meteorcloudy this issue can be closed now I think - the 3 modules are now in the registry.


New Release

There have been 80 commits to master since the last release of 1.0.4 which primarily seem to have come from docs PRs and from #109 I think it would be nice to release these changes as there have been some issues popping up that are solved on the master branch but are not yet released.
This would at the very least deserve a bump to 1.1.0, possibly a major version as well as some niches parts of #109 may be backwards incompatible.
@marimeireles I don't know how permissions on pypi/npm work for quantstack projects, but if you're able to add me to those projects I'd be happy to do the release.

Sorry I missed it @ianhi.
I'm always trying to merge all the PRs before making a release but lately it's been hard. That's why I dragged it for so long :(
I'll try to give you permissions for that :)
We can talk on private. Will make a new release right now.
Thanks for the reminder.

Done :)
New release out in pypi and you're invited as a maintainer.
To upload to pypi, create an account, I think you have to install sdist and twine. And the do the following:
git clean -fdx
python setup.py sdist
python setup.py bdist_wheel
twine upload dist/ipycytoscape*

After that the bot will pick up your changes on conda feedstock and you can merge the PR. Takes about an hour for that to happen, you can also do it manually by changing the hash of the file.
You're also invited for conda feedstock :)
Lemme know if you have any questions


Respect initial aspect ratio while resizing with shift pressed

Part of https://github.com/excalidraw/excalidraw/issues/690.
Missing:

[ ] Adjust rollbackShiftElement while resizing in aspect ratio mode so when you release the key the changes are applied to it.
[ ] All handlers should respect aspect ratio.
[ ] Aspect ratio while creating ? (maybe another PR ?).

This should mirror the shape when going to the negative. Currently, it first stops at 0px height, and then doesn't remember the scale vector on the other side.

I'm thinking if we shouldn't wait for @GasimGasimzada, where he potentially wanted to implement scale vector for all shapes, not just for arrows (https://github.com/excalidraw/excalidraw/pull/759)
Second, related point: the shape should remember its dimensions when you release shift and press it again, as long as you don't release mousedown.

It was not my intention to fix the whole issue, just to provide a way to keep initial aspect ratio as a low hanging fruit. That's why I wrote "Part of #690" and not "Closes #690" 😁
I indeed didn't go as far as mirroring + recording initial state as I wrote in the issue. I had some minutes to kill, so I wrote some fix. Feel free to do whatever you want with the PR 👍

Yep, I'm aware that you didn't want to fix the whole issue, but wasn't sure what part of it it was fixing. Either way, as it stands now it's a regression against current production, so I wouldn't merge it in this state, but we can keep working on this PR.

What's the status here? Does anyone wants to pick it up?

@lipis I said on Monday via the Twitter group that I could finish this up, but we need to align on the expected behaviour.

As Sketch does it :)

Not sure how Sketch does it, but Keynote handles shift+side handle like this:

Let's copy someone's functionality.. but from a single source.. I mentioned Sketch as more popular, or we can do what Figma does as more open and free.

Figma is the same as Keynote. Is Sketch any different?

As per orig issue, we wanted to align with Figma.

So let's do Figma style..! @enzoferey are you up for it?

Sure thing ! 👍 I should be done by the end of the weekend.

@enzoferey a friendly ping :) 🍰

Hey @lipis, as I wrote on the Twitter group I was waiting for the rotation to land in order to avoid conflicts. I'm also quite busy rebuilding a whole platform from scratch at the moment, but I think I will manage to close this in the upcoming days 👍

Would be great.. whenever you have time, no rush.. was just wandering what's the status.

The code is not super clean but it works fine, but it would almost be the same thing for all other handlers as well (right now only "SE" works).
There are two things that concern me:

The handlers being outside the element: Figma's one are inside, so the patterns works better I feel.
I was not able to think of an implementation matching Figma's one that doesn't require adding 2 new element references in the app state (one for keeping aspect ratio, one for fallback when unpressing shift). Plus, the fallback unshift element needs to be updated as well while resizing with shift pressed.

Let me know if this is fine for you or if you have any better idea.

I'm not sure if I understand the Figma behavior, but I'm pretty sure what to be stored in the app state is the position&size (element.x, element.y, element.width, element.height and element.angle) of the element at the start of dragging. It should be common with #1024/#1225.
Note: #1296 is going to be a big rewrite. Check out the dependency graph in https://github.com/excalidraw/excalidraw/issues/1298#issue-595798631

Pinging @dwelle and @dai-shi here. So what's up ? Does this implementation work for you guys ?
If you want me to finish this, I need clear indications of what you expect. The maths for "SE" corner are there working, it should be trivial to adapt for the other handlers. Adjusting rollbackShiftElement while resizing in aspect ratio mode so when you release the key the changes are applied to it is not implemented but could be tackled in another PR as well as the creation aspect ratio.
I think you have a better vision on the interdependencies of these many resize features and it will be easier for you to merge this logic than it is for me. But waiting for your comments 👍

#1296 is merged, which no longer uses deltas. So, this needs to follow that. Sorry about this big change, but the UI is much better and the logic is much cleaner now.
Also, as we discuss now in https://github.com/excalidraw/excalidraw/pull/1225#issuecomment-612407129, the original ratio can be stored in local variables not in app state.

Also, as we discuss now in #1225 (comment), the original ratio can be stored in local variables not in app state.

That was my initial suggestion in chat. I forgot to follow up again because there was too much chaos going on.

I'm not sure how you want to implement shift unpress with local variables. Would you be exporting those so the App.tsx can use them ? For reference shift unpress handler.
I still think it will take you less time to finish this up now that you have just changed the resize logic as it's pretty much rewriting this PR from scratch.

Handle all of it inside the pointerMove handler nested in pointerDown. Set up a local variable isShiftResizing: boolean that you'll toggle on/off when you get to https://github.com/excalidraw/excalidraw/pull/768/files#diff-c8a101915dc6871f1f3d7ad2208d8655R1071. Using that you'll be able to figure out if you need to reset to orig x/y (when you go from true → false).
It's best not to add new state variables for things like these when we absolutely don't need to.

Pinging @jquintozamora here to see if he'd be interested taking this in the future.

Just a note: As a commit in #1467 showed, keeping ratio is basically one line of code. The real issue is handling key up/down events #1340 which is not well implemented currently. There's an unconfirmed suggestion in https://github.com/excalidraw/excalidraw/pull/1225#issuecomment-617168284.

This should be simpler now that I added the PointerDownState, which is where the ratio can live.
https://github.com/excalidraw/excalidraw/blob/4ab4fce9981afb1d6ee6d61a1e5f22a026f0fd5d/src/components/App.tsx#L1990-L1992

I'm gonna close this. We'd have to resolve the conflicts and from what I gather this PR needs a rewrite anyway. @enzoferey feel free to reopen  if I'm wrong.


Create file on shutdown to indicate that data prepper is shutdown

Description
This change creates a file named Is-Shutdown.log when data prepper is shutdown. This can be used as an alternative method to check if a data prepper container has shutdown.
This was tested with a Docker volume to ensure this file was created successfully.
Check List

[x] New functionality includes testing.
[ ] New functionality has a documentation issue. Please link to it in this PR.

[ ] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing in favor of https://github.com/opensearch-project/data-prepper/pull/4189 based on @dlvenable's comments


Script Hex and Script Decoded are always the same; OP_RETURN doesn't show in UTF-8

https://explorer.e.cash/tx/29c72138eaceabc5d2e7d127f6dcd500f7b77db0e6ca81ea1e7886a177981abd
https://explorer.bitcoinabc.org/tx/29c72138eaceabc5d2e7d127f6dcd500f7b77db0e6ca81ea1e7886a177981abd (see how the OP_RETURN shows).
I'm prett sure 'Script Decoded' should be the UTF-8 result that we have showing in the old explorer.

https://reviews.bitcoinabc.org/T2909


华为手机生成不了图片.

Please make sure you are testing with the latest release of html2canvas.
Old versions are not supported and issues reported for them will be closed.
Please follow the general troubleshooting steps first:

[ ] You are using the latest version
[x] You are testing using the non-minified version of html2canvas and checked any potential issues reported in the console

Bug reports:
Please replace this line with a brief summary of your issue AND if possible an example on jsfiddle.
Specifications:

html2canvas version tested with: 所有版本..
Browser & version:  自带浏览器, 微信浏览器.
Operating system: 安卓手机, 荣耀10以及荣耀系列,  最新的华为p30,p40

您好 解决了吗 这个问题？目前我也遇到了这个问题，但是在用华为的手机自带浏览器打开就可以绘图成功。

一直没解决.. 华为个别型号一片白...