/usr/bin/sort: No such file or directory

hi
updatedb has error and locate show no results
[parsibox@localhost VSCode-linux-x64]$ updatedb
/home/parsibox/.linuxbrew/Cellar/findutils/4.6.0/libexec/bin/updatedb: line 323: /usr/bin/sort: No such file or directory
[parsibox@localhost VSCode-linux-x64]$ which sort
~/.linuxbrew/bin/sort

The sort program appears to be controlled by an autoconf variable for findutils, so we could probably make findutils depend on coreutils and rebuild the bottle.
Can you run brew config and paste the output here please? /usr/bin/sort is provided by coreutils on Debian/Ubuntu, and presumably by a similar package other systems. While coreutils isn't strictly speaking a dependency of Linuxbrew, other stuff could likely break if it's not available.

This issue was moved to Linuxbrew/homebrew-core#2263


Updated unlock to allow for mutiple unlocks and unlock nesting

Previously, the unlock function did not support multiple unlocks with different configs within a program. Additionally, you could not nest unlock decorators if you wanted to combine multiple configs into one config object. With this change, the unlock function can now do both.
If a user has two functions, each with a different @unlock call, and each pointing to a different config, they can do that. Each Config object created will only have the keys from the YAML file specified in the unlock. These keys can be overwritten from the command line as usual. However, this means that a user can now specify arbitrary keys from the command line without causing an error. These keys go unparsed, and if a user tries to access these unparsed keys that do not exist in a YAML file, they will get an attribute error indicating that they did specify this key from the command line, but they need it to be in the YAML config. Because I am storing the unparsed keys in the config object as a private variable, I created a "to_dict" method for the Config class that controls how the config object is converted to a dictionary, which means that this private attribute is excluded in the conversion. This "to_dict" method was used in place of using the 'vars' function within the instantiate function family so that they do not attempt to add private attributes from the config class into the object the function is attempting to instantiate. Additionally, if a user tries to specify a config from the command line when there are multiple unlocks, they are given a warning that tells them that all the configs have been overwritten with this config. In the future, this can be changed to potentially only overwriting the config from the first call of unlock or some other behavior.
Additionally, I changed the unlock function in a way that allows nesting. This means that a user can add multiple unlock decorators to a single function. The keys from the last decorator applied will overwrite any matching keys from the previous unlock.
Future additions may include allowing a user to specify a prefix in an unlock, meaning that they can nest unlocks with the same key names without having them overwritten. Additionally, with the prefix, it would potentially allow for separate unlocks to be changed via the command line (i.e., the prefix is an unlock identifier). Also, the unlock can be changed so that the user can specify skeleton key keywords like "keyring."
Overall, I think this expands the use cases for skeleton key, allowing for more complex behavior.

This is amazing


Migration Mhz19b and documentation update

Description
Migrated Mhz19b source to devices.

Updated readme with appropriate information.
Updated sample project with latest packages.
Added fritzing example.
Added expected output from sample.

Motivation and Context

Closes nanoFramework/Home#NNNN

How Has This Been Tested?
Ran example on hardware shown in fritzing diagram. Showed example of output.
Screenshots:
See expected output in readme.
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (work on Unit Tests, has no impact on code or features)
[x] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

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

Saw that build failed due to missing nuspec. Will add.

Nuspec failed due to missing dependencies. Will fix.

@Spottigus thanks a lot for this addition!


Wrapper for shap.TreeExplainer for SurvSHAP

[ ] implement shap.TreeExplainer for local explanations (PredictSurvSHAP)
[ ] implement shap.TreeExplainer for global explanations (ModelSurvSHAP)
[ ] check the other explainer types from shap library

implementation can be based on #15


Login-Bitbucket command always fails

OSX 10.15.3
Powershell 7.0.4
Atlassian.Bitbucket 0.24.1
Get this error every time I run Login-Bitbucket.
Confirmed I'm using the correct password.
Exception: /Users/bauman/.local/share/powershell/Modules/Atlassian.Bitbucket/0.24.1/Classes/Atlassian.Bitbucket.Auth.psm1:77
Line |
  77 |              throw 'Login Failed - credentials are invalid.  Use Login …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Login Failed - credentials are invalid.  Use Login-Bitbucket to re-authenticate.

OAuth login works ok.

Hi @aaronbauman,
What were you using for the password in this scenario?  Were you using an app password or a regular password?  If you are using an a regular password can you try creating an app password and see if that works?
I was using the module today without issue, but I always use app passwords.
Thanks,
Mark


ENV Variables in request highlighting

Is your feature request related to a problem? Please describe.
Trying to use environment variables is pretty difficult, and we never know if a variable is successfully attached to the request
Describe the solution you'd like
If there was some kind of checking with underline or changing text color it would be much easier to identify wrong env. variables
Describe alternatives you've considered
Insomnia Rest does smth like this, as shown in the screenshot
Additional context
Attached Screenshots

I totally agree, in Insomnia it hardly took any time to figure out how env variables work but in postwoman, it is a bit difficult.
I have created an env with few variables but still not able to figure out how to make any env active.

Got it. Since envs are used inline inside an input box (URL field), it's quite hard to list / highlight registered envs from input. I tried to parse URL input with some regex to show registered envs in  a tooltip but had no luck with it. Will try another method. Let me know if there's any UI wise implementation that could tackle this. May be like auto-complete for envs?

That's great input. Visually, this is something I'd in mind. Let me dig deep into this approach. Will ping you in need of any help ;)

Umm, I am actually working on the implementation of this. Along with a overhaul of the URL parsing system. Just that all new feature work is paused for a while to work on tests and improving the stability and reliability until the Teams feature has rolled out.

Update: Environment variable highlighting is now implemented in the URL field as an Experiment. You can enable the experiment in the settings page. It is not stable yet, but it is on track to be stable soon.
Closing this issue meanwhile.

I feel a bit dumb for having to ask this, but what is the syntax for using environment variables in your URLs?
I have an environment with variable base_url in it, but I can't get my requests to work with it... I couldn't find any examples showcasing this feature, so I had to guess how it should work. I read the discussion in #147 which suggested that Hoppscotch would, like Postman, support nunchucks syntax for environment variables. I've tried different variations, but without success.
Example:
GET {{ environment.base_url }}/companies
GET {{ variables.base_url }}/companies
GET {{ base_url }}/companies

Ex: <<variable_name>>
Use environment variables enclosed in double angular brackets (<<>>) anywhere in request section.

Thanks for the quick reply! And the awesome work you guys are doing :D


hyprland/workspaces: Improve the workspaces persistency logic

Fixes #2945
Split the config and rule persistency in 2 attributes, one storing the persistency as set in Waybar's config, the other one storing the persistency as set in Hyprland.
It fixes some conflicts between the persistency state of a workspace as set in Waybar's config and its dynamic state in Hyprland.
It allows to remove a persistent workspace in Waybar if this workspace is removed from Hyprland and if the workspace is not set as persistent in Waybar's config.

CC @zjeffer

Thanks for the review!

LGTM, thanks guys!


Add DestroyMode to provide context to destroyObject activations. Fixe…

…s POOL-387, needed by DBCP-567.

Coverage decreased (-0.2%) to 84.257% when pulling e2b1a8132ce59a9d6e6b4310f80ca81fb2a4b595 on psteitz:master into 2360671b114894d91b61c893a3299e61d033d946 on apache:master.

@psteitz
LGTM & TY. I will merge in the AM with fresh eyes. The only item I will modify after a merge, or you can do here, it is to add Javadoc since tags for all new public methods, and since we have new APIs, the since will be for 2.9.0 instead of 2.8.2.


Can't set foreground colour of mpd repeat single icon

Describe the issue
When I use the line icon-single-foreground = ${colors.foreground-alt} to try and set the colour of the icon-single element, it does not change the colour. It is working for all the other icons that I am using though (prev, seekb, stop, play, pause, seekf, next).
Expected behavior:
icon-single-foreground should set the colour of icon-single
Actual behavior:
icon-single-foreground does not change the colour of icon-single
Was it working before?
I've only just started using the mpd module so I can't say if it was working before.
To Reproduce
[colors]
foreground-alt = #666

[bar/bottom]
monitor = ${env:MONITOR:eDP-1-1}
bottom = true
width = 100%
height = 32
fixed-center = false

module-margin-left = 1
module-margin-right = 2

modules-center = mpd

[module/mpd]
type = internal/mpd
format-online = <label-song>   <icon-single>  <icon-prev> <icon-next>
format-stopped =

icon-single = SINGLE
icon-prev = PREV
icon-next = NEXT
icon-single-foreground = ${colors.foreground-alt}
icon-prev-foreground = ${colors.foreground-alt}
icon-next-foreground = ${colors.foreground-alt}

Polybar Log
❯ polybar bottom
warn: No fonts specified, using fallback font "fixed"
warn: Termination signal received, shutting down...

Screenshots

Environment:

WM: i3
Distro: Arch
Output of polybar -vvv:

polybar 3.3.0-1-gdec801a1

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) -render -damage -sync +composite +xkb +xrm +xcursor

Build type: RelWithDebInfo
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wall -Wextra -Werror -Wno-noexcept-type -pedantic -pedantic-errors
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

The keys icon-[random|repeat|repeatone|single]-foreground are not used by polybar.
You must use these keys to change the colors of these icons:
toggle-on-foreground toggle-off-foreground

Ah, thanks that works. This behaviour does feel a bit unintuitive though. What's the reason that it's implemented this way?

What's the reason that it's implemented this way?

Don't know, the behavior is like that since more than 3 years.
Moreover, it prevents the usage of different colors for the icons [random|repeat|repeatone|single] :/

I'd be happy to change this and put in a PR if others agree that this option design is weird

@JonnyHaystack how would you imagine the new options should look like?
I think it was probably designed this way because most people want the same on and off colors for all icons.

It doesn't even apply to all icons though, it only applies to the repeat icons. I would've just kept the option naming scheme the same as it is in the rest of polybar, so that it's easy and intuitive to deduce the name of the option to change the colour or font of any element.
It would be nice if there were maybe some ways to colour related groups of elements the same, but it should be consistent instead of an outlier like this. And the naming scheme should be intuitive, e.g. colour all icons in the module with icon-color perhaps. Although we would also have to add things like icon-font so the other options still work the same as the color options.

I'm not aware of any modules that also has toggleable icons like mpd has, so I don't know what naming scheme you are refering to.
We only change the foreground color of icon-single and the other toggleable icons, you should still be able to set icon-single-font or icon-single-background.

It would be nice if there were maybe some ways to colour related groups of elements the same

I agree with this. Not just in mpd but everywhere. The main blocker for this is that we don't have a way to easily say that a label should inherit from another label (same for formats, ramps, progressbars etc). I have actually created a refactoring task for this quite some time ago, but never did any work on it...

I mean the regular scheme where you use <element-name>-foreground
E.g. icon-seekb-foreground
I guess it just feels a bit weird that we have this grouping which we don't have anything else similar to. I get that it is a unique case in polybar though. I can see how it does make sense to have this grouping as an option, but in my opinion you should definitely be able to set the foreground colours for them individually as well.
Maybe a naming scheme like icon-[single|repeat|random]-[on|off]-foreground, which overrides the values in toggle-[on|off]-foreground

I see, so with this we could make the icon states fully customizable (different text for on and off etc.)
This would then require that icon-[...]-[on|off]-* inherits from icon-[...]-* and that it inherits foreground from toggle-[on|off]. The question would be what foreground do you use when both icon-[...]-foreground and toggle-[on|off]-foreground are set.
If you want to open a PR to implement this, we'd appreciate it :)

I think inheriting from icon[...]-foreground makes the most sense in that situation because you'd write it specifically with that icon in mind. It would directly conflict with toggle-[on|off]-foreground so I think going with the one that is more specific (in terms of how many items it applies to) makes more sense and it will almost always be the user's intention. Can't think why you'd want to set icon-[...]-foreground but have the toggle-[on|off]-foreground apply to it


MINOR: Store metrics scope, total metrics

Rename metrics scope of rocksDB window and session stores; also modify the store metrics accordingly with guidance on its correlations to metricsScope.

Add the missing total metrics for per-thread, per-task, per-node and per-store sensors.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

One thing yet to be added is in the upgrade section, I will wait and see if RC0 2.0 made it or not: if RC0 succeeds, I will add it to 2.1 upgrade section. Otherwise I'll do it in piggybacked 2.0 branch.
@mjsax @vvcephei @bbejeck

LGTM! I suppose we'll mention in the release notes that we changed the rocksdb store metric names?

yes, that's my plan as commented above.


[bugfix] Remove legacy hack for fees of Decred / Qtum / Viacoin

📝 Description
Until now a hack was required on Live side to get around an issue with the /fees endpoint of the Bitcoin explorer, only for Decred, Qtum and Viacoin.
It appears the /fees endpoint has been fixed at some point and the hack is now redundant, causing the issue in the linked tickets.
Removing the hack solves the issue.
❓ Context

Impacted projects: LLC
Linked resource(s):

https://ledgerhq.atlassian.net/browse/LIVE-9497
https://ledgerhq.atlassian.net/browse/LIVE-9500

✅ Checklist

[ ] Test coverage :x: depending on correctness of backend-provided data, which we don't validate at the moment
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach

On hold until further notice, as we need to clarify the migration plan with backend.
As a quick fix backend team are reverting to their previous (buggy) implem to unlock users, then we'll need to plan a proper, seamless migration on both backend and LL side.

Following discussions with backend they provided a fix on staging -- this PR can be validated using https://explorers.api-01.live.ledger-stg.com
:warning: HOWEVER the PR cannot be merged unless the fix on backend side is compatible with both before and after this fix...
Proper migration plan can only be one of:

backend implements the fix on a new endpoint, different from /network
we implement some temporary hack to support both, instead of just removing the legacy logic


Inconsistent Layer Node Naming

The problem
Describe the bug
The naming of a new style on its nodes in the scene hierarchy is inconsistent.

This has been implemented.


fix: Allow file fields to be non translatable

Description
This addresses the issue where setting the translatable(false) method on a file field does not affect the field (i.e. Always translated) by adding a new disableTranslate() method on the file field.
Usage:
Files::make()
    ->name('single_file')
    ->label(twillTrans('Single file'))
    ->disableTranslate();

Related Issues
Fixes #1712

Why create a new disableTranslate when there is already translatable(false)?

Let me clarify this. We can agree this is not pretty, but it is temporary to avoid a breaking change.
In https://github.com/area17/twill/pull/2525 I asked @zeezo887 to add a new option to work around the current situation with the translate prop on medias field that isn't working because of the global configuration option. Similarly, the files field currently forces translations without any ability to control it globally or at the field level.
To avoid breaking changes in Twill 3 while enabling the missing functionality we introduce these temporary methods. In a future breaking release we will fix the behavior of the translate prop and translatable method, remove the global configuration option for medias fields, as well as these unnecessary methods.


request to get access to "oneLineAboveText" property in "vscode.onEnterRules"

C/C++ extension need to get access to "oneLineAboveText" property in "vscode.onEnterRules" to fix this bug: https://github.com/microsoft/vscode-cpptools/issues/5733 .
I can see this property is being used here: https://github.com/microsoft/vscode/blob/e5ceb315da2462b0fea70716e79cc82ce708b438/extensions/typescript-language-features/src/features/languageConfiguration.ts#L21
but it is missing from the vscode extension API:
https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L4677

Let's track in #58440

Let's track in #58440


OAuth2FeignRequestInterceptor is thread safe?

Hi all,
I have one question.
I would like to use OAuth2FeignRequestInterceptor for my feign client together with DefaultOAuth2ClientContext which is not thread safe.
My interceptor can be fired from multiple threads, not from request. In this case the  DefaultOAuth2ClientContext is not session scoped as in spring framework.
What in that case when 10 threads try to concurrently get token via interceptor. I think the last thread wins and rewrite token in  DefaultOAuth2ClientContext objects and in the worst case the token will be acqruired ten times.
Am I right?
My configuration class is here:
@Configuration
public class FeignClientConfiguration {

    @Bean
    public RequestInterceptor requestInterceptor(ApplicationContext ctx)
    {
        return new OAuth2FeignRequestInterceptor(new DefaultOAuth2ClientContext(), clientCredentialsResourceDetails(ctx));
    }

    private static ClientCredentialsResourceDetails clientCredentialsResourceDetails(ApplicationContext ctx) {
        ClientCredentialsResourceDetails details = new ClientCredentialsResourceDetails();
        details.setAccessTokenUri(ctx.getEnvironment().getProperty("tokenUrl"));
        details.setClientId(ctx.getEnvironment().getProperty("clientId"));
        details.setClientSecret(ctx.getEnvironment().getProperty("clientId"));

        return details;
    }
}

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.

sorry for late answer.
If I understood your anwer, interceptor is thread safe right? Can you tell me which part implement such synchronization or something else?
thanks

There is no specific synchronization.


client library info

Adding details and pointing to examples of how to use swagger to
generate client libraries for access to RackHD APIs

@RackHD/corecommitters <-- PR for docs to match @jlongever recent update to making python client library

+1


feat(ar-io cli): init CLI setup PE-5854

this PR inits the ar.io CLI
ar.io CLI
Test Locally
yarn build:esm
node lib/esm/cli/cli.js

out example:
> ar.io
Usage: cli [options] [command]

Options:
  -h, --help                              display help for command

Commands:
  ar.io [options]                         AR.IO Network CLI
  info [options]                          Get network info
  token-supply [options]                  Get the total token supply
  get-registration-fees [options]         Get registration fees
  get-demand-factor [options]             Get demand factor
  get-gateway [options]                   Get the gateway of an address
  list-gateways [options]                 List the gateways of the network
  get-gateway-delegates [options]         Get the delegates of a gateway
  get-delegations [options]               Get all stake delegated to gateways from this address
  get-allowed-delegates [options]         Get the allow list of a gateway delegate
  get-arns-record [options]               Get an ArNS record by name
  list-arns-records [options]             List all ArNS records
  get-arns-reserved-name [options]        Get a reserved ArNS name
  list-arns-reserved-names [options]      Get all reserved ArNS names
  get-arns-auction [options]              Get an ArNS auction by name
  list-arns-auctions [options]            Get all ArNS auctions
  get-arns-auction-prices [options]       Get ArNS auction prices
  get-epoch [options]                     Get epoch data
  get-current-epoch [options]             Get current epoch data
  get-prescribed-observers [options]      Get prescribed observers for an epoch
  get-prescribed-names [options]          Get prescribed names for an epoch
  get-observations [options]              Get observations for an epoch
  get-distributions [options]             Get distributions for an epoch
  get-token-cost [options]                Get token cost
  list-vaults [options]                   Get all wallet vaults
  get-primary-name-request [options]      Get primary name request
  list-primary-name-requests [options]    Get primary name requests
  get-primary-name [options]              Get primary name
  list-primary-names [options]            Get primary names
  balance [options]                       Get the balance of an address
  list-balances [options]                 List all balances
  get-redelegation-fee [options]          Get redelegation fee
  get-vault [options]                     Get the vault of provided address and vault ID
  get-gateway-vaults [options]            Get the vaults of a gateway
  transfer [options]                      Transfer IO to another address
  join-network [options]                  Join a gateway to the AR.IO network
  leave-network [options]                 Leave a gateway from the AR.IO network
  update-gateway-settings [options]       Update AR.IO gateway settings
  increase-operator-stake [options]       Increase operator stake
  decrease-operator-stake [options]       Decrease operator stake
  instant-withdrawal [options]            Instantly withdraw stake from a vault
  cancel-withdrawal [options]             Cancel a pending withdrawal
  delegate-stake [options]                Delegate stake to a gateway
  decrease-delegate-stake [options]       Decrease delegated stake
  redelegate-stake [options]              Redelegate stake to another gateway
  buy-record [options]                    Buy a record
  upgrade-record [options]                Upgrade the lease of a record to a permabuy
  extend-lease [options]                  Extend the lease of a record
  increase-undername-limit [options]      Increase the limit of a name
  submit-auction-bid [options]            Submit a bid to an auction
  request-primary-name [options]          Request a primary name
  spawn-ant [options]                     Spawn an ANT process
  get-ant-state [options]                 Get the state of an ANT process
  get-ant-info [options]                  Get the info of an ANT process
  get-ant-record [options]                Get a record of an ANT process
  list-ant-records [options]              Get the records of an ANT process
  get-ant-owner [options]                 Get the owner of an ANT process
  list-ant-controllers [options]          List the controllers of an ANT process
  get-ant-name [options]                  Get the name of an ANT process
  get-ant-ticker [options]                Get the ticker of an ANT process
  get-ant-balance [options]               Get the balance of an ANT process
  list-ant-balances [options]             Get the balances of an ANT process
  transfer-ant-ownership [options]        Transfer ownership of an ANT process
  add-ant-controller [options]            Add a controller to an ANT process
  remove-ant-controller [options]         Remove a controller from an ANT process
  set-ant-record [options]                Set a record of an ANT process
  remove-ant-record [options]             Remove a record from an ANT process
  set-ant-ticker [options]                Set the ticker of an ANT process
  set-ant-name [options]                  Set the name of an ANT process
  set-ant-description [options]           Set the description of an ANT process
  set-ant-keywords [options]              Set the keywords of an ANT process
  set-ant-logo [options]                  Set the logo of an ANT process
  release-name [options]                  Release the name of an ANT process
  reassign-name [options]                 Reassign the name of an ANT process to another ANT process
  approve-primary-name-request [options]  Approve a primary name request
  remove-primary-names [options]          Remove primary names
  help [command]                          display help for command

Use --dev  and --debug for verbose output
> node lib/esm/cli/cli.js list-gateways --dev --debug --limit 2 --sort-by totalDelegatedStake
{"level":"debug","message":"Evaluating read interaction on contract","name":"ar-io-sdk","tags":[{"name":"Action","value":"Paginated-Gateways"},{"name":"Limit","value":"2"},{"name":"Sort-By","value":"totalDelegatedStake"}],"timestamp":"2024-11-27T17:20:31.196Z","version":"2.5.3-alpha.2"}
{"level":"debug","message":"Read interaction result","name":"ar-io-sdk","result":{"Assignments":[],"GasUsed":2765758034,"Messages":[{"Anchor":"00000000000000000000000000003113","Data":"{\"sortOrder\":\"desc\",\"hasMore\":true,\"totalItems\":16,\"limit\":2,\"sortBy\":\"totalDelegatedStake\",\"items\":[{\"startTimestamp\":1719295200000,\"totalDelegatedStake\":9937949693,\"weights\":{\"compositeWeight\":0.1444099720516666685,\"gatewayRewardRatioWeight\":1,\"tenureWeight\":0.86111111111111116045,\"observerRewardRatioWeight\":0.006451612903225806446,\"normalizedCompositeWeight\":0.02186951638311611032,\"stakeWeight\":25.993794969300001441},\"operatorStake\":250000000000,\"status\":\"joined\",\"observerAddress\":\"QGWqtJdLLgm2ehFWiiPzMaoFLD50CnGuzZIPEdoDRGQ\",\"stats\":{\"failedEpochCount\":0,\"failedConsecutiveEpochs\":0,\"passedEpochCount\":154,\"totalEpochCount\":154,\"observedEpochCount\":0,\"prescribedEpochCount\":154,\"passedConsecutiveEpochs\":154},\"gatewayAddress\":\"QGWqtJdLLgm2ehFWiiPzMaoFLD50CnGuzZIPEdoDRGQ\",\"settings\":{\"delegateRewardShareRatio\":10,\"protocol\":\"https\",\"minDelegatedStake\":500000000,\"note\":\"Test Gateway operated by PDS for the AR.IO ecosystem.\",\"allowedDelegatesLookup\":{\"31LPFYoow2G7j-eSSsrIh8OlNaARZ84-80J-8ba68d8\":true},\"port\":443,\"allowDelegatedStaking\":true,\"properties\":\"raJgvbFU-YAnku-WsupIdbTsqqGLQiYpGzoqk9SCVgY\",\"fqdn\":\"ar-io.dev\",\"label\":\"AR.IO Test\",\"autoStake\":false},\"endTimestamp\":0},{\"startTimestamp\":1719295200000,\"totalDelegatedStake\":3553726285,\"weights\":{\"compositeWeight\":0.10797346774098785793,\"gatewayRewardRatioWeight\":0.83974358974358975782,\"tenureWeight\":0.86111111111111116045,\"observerRewardRatioWeight\":0.006410256410256410034,\"normalizedCompositeWeight\":0.016351554453999633809,\"stakeWeight\":23.293554098499999583},\"operatorStake\":229381814700,\"status\":\"joined\",\"observerAddress\":\"M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4\",\"stats\":{\"failedEpochCount\":25,\"failedConsecutiveEpochs\":0,\"passedEpochCount\":130,\"totalEpochCount\":155,\"passedConsecutiveEpochs\":3,\"prescribedEpochCount\":155,\"observedEpochCount\":0},\"gatewayAddress\":\"M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4\",\"settings\":{\"allowDelegatedStaking\":true,\"protocol\":\"https\",\"minDelegatedStake\":500000000,\"note\":\"Primarily just a test server for L1 indexing.\",\"port\":443,\"delegateRewardShareRatio\":20,\"properties\":\"FH1aVetOoulPGqgYukj0VE0wIhDy90WiQoV3U2PeY44\",\"fqdn\":\"permaweb.name\",\"label\":\"Permaweb Name\",\"autoStake\":true},\"endTimestamp\":0}],\"nextCursor\":\"M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4\"}","Tags":[{"name":"Data-Protocol","value":"ao"},{"name":"Variant","value":"ao.TN.1"},{"name":"Type","value":"Message"},{"name":"Reference","value":"3113"},{"name":"Action","value":"Gateways-Notice"},{"name":"X-Origin","value":""},{"name":"X-Reference","value":""}],"Target":"1234"}],"Output":{"data":"Pruning state at timestamp:<PHONE_NUMBER>539\n{\"Type\":\"Message\",\"Timestamp\":1732727641539,\"Variant\":\"ao.TN.1\",\"Limit\":\"2\",\"Cast\":false,\"Cron\":false,\"From\":\"1234\",\"Action\":\"Paginated-Gateways\",\"Pruned-Requests-Count\":0,\"_e\":1,\"From-Formatted\":\"1234\",\"Sort-By\":\"totalDelegatedStake\",\"Epoch-Index\":155,\"Data-Protocol\":\"ao\",\"Message-Id\":\"1234\"}\n{\"Type\":\"Message\",\"Timestamp\":1732727641539,\"Variant\":\"ao.TN.1\",\"Limit\":\"2\",\"Cast\":false,\"Cron\":false,\"From\":\"1234\",\"Action\":\"Paginated-Gateways\",\"Pruned-Requests-Count\":0,\"_e\":1,\"From-Formatted\":\"1234\",\"Sort-By\":\"totalDelegatedStake\",\"Epoch-Index\":155,\"Data-Protocol\":\"ao\",\"Message-Id\":\"1234\"}","print":true,"prompt":"\u001b[32mDevnet IO\u001b[90m@\u001b[34maos-2.0.1\u001b[90m[Inbox:\u001b[31m265\u001b[90m]\u001b[0m> "},"Spawns":[]},"timestamp":"2024-11-27T17:20:32.710Z","version":"2.5.3-alpha.2"}
{
  "sortOrder": "desc",
  "hasMore": true,
  "totalItems": 16,
  "limit": 2,
  "sortBy": "totalDelegatedStake",
  "items": [
    {
      "startTimestamp":<PHONE_NUMBER>000,
      "totalDelegatedStake":<PHONE_NUMBER>,
      "weights": {
        "compositeWeight": 0.14440997205166667,
        "gatewayRewardRatioWeight": 1,
        "tenureWeight": 0.8611111111111112,
        "observerRewardRatioWeight": 0.0064516129032258064,
        "normalizedCompositeWeight": 0.02186951638311611,
        "stakeWeight": 25.9937949693
      },
      "operatorStake":<PHONE_NUMBER>00,
      "status": "joined",
      "observerAddress": "QGWqtJdLLgm2ehFWiiPzMaoFLD50CnGuzZIPEdoDRGQ",
      "stats": {
        "failedEpochCount": 0,
        "failedConsecutiveEpochs": 0,
        "passedEpochCount": 154,
        "totalEpochCount": 154,
        "observedEpochCount": 0,
        "prescribedEpochCount": 154,
        "passedConsecutiveEpochs": 154
      },
      "gatewayAddress": "QGWqtJdLLgm2ehFWiiPzMaoFLD50CnGuzZIPEdoDRGQ",
      "settings": {
        "delegateRewardShareRatio": 10,
        "protocol": "https",
        "minDelegatedStake": 500000000,
        "note": "Test Gateway operated by PDS for the AR.IO ecosystem.",
        "allowedDelegatesLookup": {
          "31LPFYoow2G7j-eSSsrIh8OlNaARZ84-80J-8ba68d8": true
        },
        "port": 443,
        "allowDelegatedStaking": true,
        "properties": "raJgvbFU-YAnku-WsupIdbTsqqGLQiYpGzoqk9SCVgY",
        "fqdn": "ar-io.dev",
        "label": "AR.IO Test",
        "autoStake": false
      },
      "endTimestamp": 0
    },
    {
      "startTimestamp":<PHONE_NUMBER>000,
      "totalDelegatedStake":<PHONE_NUMBER>,
      "weights": {
        "compositeWeight": 0.10797346774098786,
        "gatewayRewardRatioWeight": 0.8397435897435898,
        "tenureWeight": 0.8611111111111112,
        "observerRewardRatioWeight": 0.00641025641025641,
        "normalizedCompositeWeight": 0.016351554453999634,
        "stakeWeight": 23.2935540985
      },
      "operatorStake":<PHONE_NUMBER>00,
      "status": "joined",
      "observerAddress": "M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4",
      "stats": {
        "failedEpochCount": 25,
        "failedConsecutiveEpochs": 0,
        "passedEpochCount": 130,
        "totalEpochCount": 155,
        "passedConsecutiveEpochs": 3,
        "prescribedEpochCount": 155,
        "observedEpochCount": 0
      },
      "gatewayAddress": "M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4",
      "settings": {
        "allowDelegatedStaking": true,
        "protocol": "https",
        "minDelegatedStake": 500000000,
        "note": "Primarily just a test server for L1 indexing.",
        "port": 443,
        "delegateRewardShareRatio": 20,
        "properties": "FH1aVetOoulPGqgYukj0VE0wIhDy90WiQoV3U2PeY44",
        "fqdn": "permaweb.name",
        "label": "Permaweb Name",
        "autoStake": true
      },
      "endTimestamp": 0
    }
  ],
  "nextCursor": "M0WP8KSzCvKpzC-HPF1WcddLgGaL9J4DGi76iMnhrN4"
}

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hooking UIViewController method

i'm trying to hook this method ( using ) fakelogo.h but it keep crashing
CRASH
Feb 24 02:27:44 iMokhless-iPad WhatsApp[865] <Warning>: ZKSwizzle: incompatible type encoding for _presentViewController:withAnimationController:completion:. (expected v40@0:8@16@24@?32, got v40@0:8@16@24@32)
Feb 24 02:27:44 iMokhless-iPad WhatsApp[865] <Error>: +[UIViewController _ZK_unconditionallySwizzle]: unrecognized selector sent to class 0x1a210c458
Feb 24 02:27:44 iMokhless-iPad WhatsApp[865] <Error>: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[UIViewController _ZK_unconditionallySwizzle]: unrecognized selector sent to class 0x1a210c458'
	*** First throw call stack:
	(0x1847e9900 0x183e57f80 0x1847f0514 0x1847ed5b8 0x1846f168c 0x10262e930 0x183e5a0cc 0x183e5ae30 0x1200ddd3c 0x1200ec960 0x1200ebb20 0x1200ebbd4 0x1200de08c 0x1200e20fc 0x1200dd044)

CODE I USE
hook(UIViewController)
- (void)_presentViewController:(id)arg1 withAnimationController:(id)arg2 completion:(id /* block */)arg3 {
_orig(void, arg1, arg2, arg3);
}
endhook

any idea ?

<Warning>: ZKSwizzle: incompatible type encoding for _presentViewController:withAnimationController:completion:. (expected v40@0:8@16@24@?32, got v40@0:8@16@24@32)

This is a significant error message in your log. The method you are trying to hook has a type encoding v40@0:8@16@24@?32 but you are giving it a method with the encoding v40@0:8@16@24@32.

YES after searching on the internet i found it's because the block argument, but i hooked public method
got the same issue ?
it say also incompatible type encoding for -------
- (void)presentViewController:(UIViewController *)viewControllerToPresent animated: (BOOL)flag completion:(void (^ __nullable)(void))completion {
_orig(void, viewControllerToPresent, flag, completion);
}

What are this fakelogo.h and these hook() macros you are using?

this one
https://github.com/mstg/fakelogos

If it still says incompatible type encoding then it will keep doing so until you fiddle with the arguments until they match.

mmmmmm great i will try hope it works ( thanks )


Fixed driver initialization within modules

The drivers needed to be initialized in the modules.

This change looks like the last one to eliminate the regressions!  Testing is looking good through CLI and VDs.

Hi @clintonskitson,
Thanks. I merged this then rolled it back as a soft reset into the original PR. However, I didn't want you to think I didn't take this commit. I also replicated the work into the remote volume driver as well.


Cannot get ("app", "Root") session on 2019 server VM

Hello,
we are trying to run automated tests using Appium Driver for a desktop application on a remote machine that is on Windows 2019.
We are using this solution to start the application, and it works on the VM I am writing tests,
But when run on the 2019 server machine the "DesktopSession" is returning null.
We have developer mode enabled on the machine and also we are using AppiumServceBuilder to automatically start the winApp driver.
Sample of the code which is returning a null on the Win 2019 Server:
            var appiumServiceBuilder = new AppiumServiceBuilder().UsingPort(4723).Build();
            appiumServiceBuilder.Start();
            var appiumOptions = new AppiumOptions();
            appiumOptions.AddAdditionalCapability("app", "Root");
            var desktopSession = new WindowsDriver<WindowsElement>(appiumServiceBuilder, appiumOptions);
            Assert.NotNull(desktopSession);

This is working properly on the Win 10 VM.
I was wondering if it is possible that the 2019 server machine is missing some rights and that is why it does not have access to "find" the desktopSession.
Any advice would be greatly appreciated!
Regards

As per the FAQ its supported on Windows server 2016. Will it be possible for you to check on Windows Server 2016.

Hello, currently cannot test on a 2016 server, I saw in the documentation 2019 should be supported and is the recommended one compared to 2016. We've already requested a Win 10 VM as we tested with a Win 10 agent and it worked properly.
Some more details:
The WinAppDriver is starting the application on the 2019 Server VM, but cannot find any Window Sessions.
Regards

I have been running tests on both Windows Server 2019 and Microsoft host agent 2019 without any issues, if you post your WinAppDriver logs maybe I can help. Here is my code (Java) to connect:
try {
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("app", "Root");
capabilities.setCapability("platformName", "Windows");
capabilities.setCapability("deviceName","WindowsPC");
capabilities.setCapability("ms:experimental-webdriver", false);
driver = new WindowsDriver(new URL("http://<IP_ADDRESS>:4723"), capabilities);
sleep(3);
WebElement session = driver.findElementByName("My app name");
String hex = session.getAttribute("NativeWindowHandle");
int handle = Integer.parseInt(hex);
String windowHandle = Integer.toHexString(handle);
windowHandle = "0x"+windowHandle;
DesiredCapabilities caps = new DesiredCapabilities();
caps.setCapability("appTopLevelWindow", windowHandle);
caps.setCapability("platformName", "Windows");
caps.setCapability("deviceName","WindowsPC");
capabilities.setCapability("ms:experimental-webdriver", false);
driver = new WindowsDriver(new URL("http://<IP_ADDRESS>:4723"), caps);
} catch (MalformedURLException | InterruptedException e) {
e.printStackTrace();
}

I have been running tests on both Windows Server 2019 and Microsoft host agent 2019 without any issues, if you post your WinAppDriver logs maybe I can help. Here is my code (Java) to connect:
try { DesiredCapabilities capabilities = new DesiredCapabilities(); capabilities.setCapability("app", "Root"); capabilities.setCapability("platformName", "Windows"); capabilities.setCapability("deviceName","WindowsPC"); capabilities.setCapability("ms:experimental-webdriver", false); driver = new WindowsDriver(new URL("http://<IP_ADDRESS>:4723"), capabilities); sleep(3); WebElement session = driver.findElementByName("My app name"); String hex = session.getAttribute("NativeWindowHandle"); int handle = Integer.parseInt(hex); String windowHandle = Integer.toHexString(handle); windowHandle = "0x"+windowHandle; DesiredCapabilities caps = new DesiredCapabilities(); caps.setCapability("appTopLevelWindow", windowHandle); caps.setCapability("platformName", "Windows"); caps.setCapability("deviceName","WindowsPC"); capabilities.setCapability("ms:experimental-webdriver", false); driver = new WindowsDriver(new URL("http://<IP_ADDRESS>:4723"), caps); } catch (MalformedURLException | InterruptedException e) { e.printStackTrace(); }

I have the same problem. Can you help me to see it，the testcode run on  my pc is ok,but run on VM,desktopSession is null.


typo: teh -> the

@nschonni - This change has been implemented, regardless of the status of this PR.  Thanks for the update!


Use http.NewRequestWithContext

Specifically to support tracing we need to pass the existing context into the downstream http requests

TestIntegrationQueryContextCancellation is failing with these changes so I'll have to look into that next week. I'm fairly new to go contexts though so if someone has any helpful hints for failures here I'd appreciate it

@devinsba my attempt is in #95. I figured out that when cancelling the query by sending a DELETE request, we need to "uncancel" the parent context using context.WithoutCancel().


Smooth rendering of parameter changes

Rationale:
There are many use-cases where one or more frequently changing parameter/dimension for a WMTS source are used. One such example is issue #2827 and in our SCALGO Live products we also have several different  types of WMTS layers where a continuous dimension made available in the UI through a slider. An example of this is the [sea-level flooding] (http://scalgo.com/live/global?center=-10546029.2%2C3387094.1&zoom=5&tool=zoom&lrs=basic%2Cglobal%2Fhydrosheds%3Adem%2Cglobal%2Fhydrosheds%3Asea-levels&flooding=10) layer, and there is a similar interaction for flow accumulation. In the former, the sea-level rise is set via a dimension/parameter to the GetTile request, and when the user drags the slider around, the sea level changes (the WMTS server delivers tiles with the appropriate sea level). In stock openlayers, this is not well supported as no tiles are rendered until the new tiles are ready, resulting in heavy flickering.
This non-trivial patch changes the image tile renderer to keep rendering old tiles while the new tiles are being loaded, this significantly improves the use cases where such rapid changes in a dimension are being performed. We have created an example, supplementing the one in issue #2827, that clearly illustrates the use case. You can see the regular WMTS mode on the left, and the new on the right. Use the sea-level slider to change the sea level and notice how the regular WMTS layer flickers significantly, especially when you slowly drag the slider (which is a very common use case). This patch does not change the semantics of existing WMTS layers, the smooth mode has to be explicitly requested by designating which dimensions  should be treated this way.  We have already been running this patch in production for several months (and it's used in the links above) with no issues for both regular WMTS layers and WMTS layers with a smooth dimension.
Details:
First, the patch tells WTMS sources to ignore certain dimensions when building tile cache keys. That way, when these parameters change, the existing tiles are not immediately discarded (or ignored) from the cache. Instead, the old tiles are still rendered. Without any other changes to the code, just this change would cause the ignored dimensions to have no effect on rendering at all.
When the ignored dimensions do change, we added a new method that, when called, explicitly reloads all the currently-visible tiles, and purges all the not visible tiles.
Tile reloading for this method uses a mechanism we called "out-of-band" in the code. Essentially, we turned each tile in the cache into a linked list of tiles. The head of the list is the current tile, and the second node (if any) is a tile waiting to be loaded. If there's a third node in the linked list (which is less common), that means the second node tile is in a loading state, but yet another tile has been requested. If a linked list gets flooded with load requests (which often happens for e.g. slider inputs), the linked list builder drops tile nodes that it knows will never be rendered. This load shedding generally keeps the length of the linked list to at most three.
This tile loading mechanism uses the ol3 tile load queue, so it still takes advantage of all the nice work scheduling for image loading that the ol3 engine uses.
We also made a small change to the image tile renderer to check the state of the linked list for each tile to decide which one to render for that frame.
The patch passes the Travis CI test and is rebased on top of current ol3 master. We have split the patch into one commit for the base functionality (I am not sure it's necessary to further subdivide that commit) and a separate commit for the example. I have filled out the corporate contributor license agreement and can send that in when it becomes relevant.
We appreciate your comments.

I am not entirely sure what the expect.js called gets moody all too quickly from Travis CI is about, it doesn't happen on my system. I am not sure it has anything to do with this patch?

This is a very well put together contribution and much appreciated (the code is generally very clean and your description is great).  We've just had a short discussion about the nature of this change on our weekly dev call.  We want to make sure the change is appropriately general (nothing tied to WMTS) and will handle multiple use cases.  I imagine we'll have some back and forth as people find time to review and potentially suggest some alternatives.
So, nothing more substantive from me right now.  But I wanted to at least express appreciation and say that the results look great.

@tschaub thanks for your review, I'm happy you appreciate the contribution.
It certainly makes sense to get more eyeballs on the patch. The WMTS-specific changes are limited to simply managing the dimensions, and I am hopeful the underlying design will work for a larger set of sources. We have not worked much with WMS layers, someone else might want to confirm that the idea carries over.
Thank you for your line-by-line comments as well, I guess we should hold off with incorporating the detailed comments until there's consensus on the fundamental design?

I am interested in reviewing this, and eventually merge this work, possibly with changes. I'll spend some time on it tomorrow. Thanks for the contribution.

Excellent! I have a rebased it to master (as of a few days ago) in a branch in my own repo, I can update the pull request with that version, that might make things a little more convenient for you - I had to change a few things to adapt to the tilegrid coordinate scheme changes.

Yes please!

I have rebased to current master and updated the pull request. Thanks for the review!.

Thanks again for your code and the details provided in the issue description.
I've been thinking about the whole problem, and I've come up the same design as you: organize tiles in a linked list.
Here are more comments:
The application code shouldn't need to call reloadVisibleTilesOutOfBand to load tiles. The loading of tiles should be done by the library.
Your patch adds a lot of code to ol/imagetile.js and ol/source/tileimagesource.js, and I've wondering if we could do simpler.
So I've been experimenting in my own branch (dynamic-params). My code uses a similar design to yours, but it includes fewer changes to both ol/imagetile.js and ol/source/tileimagesource.js. The new logic is basically in the ol.source.TileImage#getTile function.
But my code is not as complete as yours.
In particular, the length of tile linked lists is not handled. So linked lists may end up with lots of tiles, based on the number of possible dimension values. That is a problem, and, at this point, I don't quite understand how you addressed that issue.
Another problem is the disposal of tiles in the cache. Only the head of the linked list is a candidate for expiration. I am not sure your code handles that problem either. But in your case the problem is mitigated by the fact that you control the length of linked lists.
So, to conclude this comment, I'd like to come up with a patch that is simpler than yours but more complete that mine. It would be good if you could have a look at my patch, to tell me if it makes sense to you.

Excellent! Your new implementation is cleaner and smaller than ours (which we were also trying to make mostly additive for easier porting to new releases), and although our patch worked - I am sure we're better off with a patch by someone more familiar with the ol infrastructure. I am happy you got rid of the explicit reloadVisibleTilesOutOfBand call, that always seemed iffy.
I tested your patch out on my system and it appears to work reasonably well for the example, crucially, there is no flickering and tiles are simply updated with newer data as it becomes available. However, it does seem to have a significant responsiveness regression compared to our patch. When you drag the slider multiple times back and forth rather quickly, the map rendering lacks behind the current value of the slider, and it takes a while to "catch up". This is probably caused by the length of the linked list getting too long as you also point out, assuming the network and not rendering is the bottleneck here.
As for pruning the request, the idea is that if we know a request would never get loaded we can throw it away. I.e. if you have 2 requests queued up, and you're loading no 1, but not no 2, and then request no 3 comes in, you can just drop no 2 without ever loading it and skip straight to no 3.  This happens e.g.
https://github.com/openlayers/ol3/compare/master...thomasmoelhave:smoothparams_clean#diff-d4d79f1d362fadde99dd6ee2af0a76d8R97
and the hack in
https://github.com/openlayers/ol3/compare/master...thomasmoelhave:smoothparams_clean#diff-c4373b774a597750cb202cf726c7303fR240
This has worked out well in practice in our non-trivial application, but a more sophisticated pruning algorithm might be desired down the line for use cases we maybe didn't consider - at the very least we probably should get rid of the timeout thing. We have also not tested this extensively if the dynamic parameter space has more than one dimension.
Good point about tile disposal from the cache, I'm honestly not entirely sure what this implication of this is in practice, but I don't think we explicitly handle that problem, as you also pointed out.
Causes many requests to get dropped, although doing it with a timeout is not ideal as @tschaub also pointed out.
In conclusion, I think your patch is architecturally more sound, but some form of load shedding probably needs to be put in place.

Thanks for your comments. Very useful. Starting Friday I am on vacation for three weeks. I'll see if I can spend more time on this work before my vacation. Otherwise it will have to wait until I return. I you want to help feel free to suggest changes/commits based on my branch.

I am glad you found the comments useful. I am also going on vacation starting Friday, so I am not sure much will happen until a few weeks from now :).
Have a nice summer!

Hi @elemoine, I hope you had  a nice vacation.
I did some more performance testing of you branch, and looked on the length of the linked list here:
https://github.com/openlayers/ol3/compare/master...elemoine:dynamic-params#diff-c4373b774a597750cb202cf726c7303fR133
It does not seem to behave the way I imagined, in particular it appears the list is never cleared or reduced. After dragging the slider around a  little bit, I easily got a list of length > 70 for every tile in my viewport. Is that the intended behavior?

It does not seem to behave the way I imagined, in particular it appears the list is never cleared or reduced. After dragging the slider around a little bit, I easily got a list of length > 70 for every tile in my viewport. Is that the intended behavior?

No. This is what I wrote in my previous comment:

In particular, the length of tile linked lists is not handled. So linked lists may end up with lots of tiles, based on the number of possible dimension values. That is a problem, and, at this point, I don't quite understand how you addressed that issue.

Oh right, sorry about that. My memory was foggy after the vacation and I should have re-read your notes. I'll take a closer look at this later this week.

@elemoine, I have added a number of notes to the commit. I hope they help you understand how we managed the length of the lists. I am not sure how to incorporate these ideas into your patch, but maybe you can take a look? If I didn't actually address your question, let me know and I'll try again :).

@elemoine any news on this pull request?

@elemoine Please take another look at this pull request. @thomasmoelhave deserves some feedback I think. If you don't have time, at least summarize your thoughts, so someone else can take over from here.

I am sure about the lack of activity on this. I do want to get back to this, but I haven't found the time up to now.

@thomasmoelhave, I've rebased my dynamic-params branch onto the current master. I've also made changes based on your comments.
With these changes the list length never exceeds 2. I hope this will make address the performance problems that you observed. I still need to make sure that my code is compatible with the "tile reprojection" code (I don't think it is at the moment).
Do you have time to test my branch again?

That is excellent! I am very interested in testing your code, but I might not be able to find the time for it until the week of the 16th. Does that work for you?

That is excellent! I am very interested in testing your code, but I might not be able to find the time for it until the week of the 16th. Does that work for you?

I created a new PR based on my branch. I'll try to spend more time on it next week.

Fixed with #4389

Hello,
not sure if I ask in the right place, but do you plan to support this feature for TileWMS source on updateParams calls ?
I use TileWMS layer with time parameter, and it would be great if the smooth transition could be used in this case too.
Thanks

@skalp See: https://github.com/openlayers/ol3/pull/4527

Great ! Thanks !


Add dark mode

Dark mode!
Two alternatives I'd be okay with here:
a. Always default to the user's browser theme preference
b. Default to light mode, when the user changes it save their preference to local storage

👋 hey, I want to work on this. But I can't figure out a good-looking color palette for dark mode.

ah yeah. maybe @noelsner can provide some advice? he did the original styles

I agree, the dark mode color palette is tough 😬
I would go with a dark-gray background color like this and then the yellow, green, and gray colors might be able to stay the same (I think those colors are in HSL formats so you could play with lightness percentages to see if darker versions of those colors look better)


Fix recommendedHealth

Had local health bar anomalies. Suspect caching.

The cache seemed to be setting maxHealth lower.
Tested using proxy and everything worked.
Worked locally after clearing cache.

Bug: Only clamped health if level type was course. Most have type hero. The fix injects additional data into the level data object to inform when to clamp.

As discussed removing try from names, replacing clamp with constrain.

@differentmatt Fixed. Will merge when travis checks done.

@differentmatt Do you mean like so:
return unless level.constrainHeroHealth
    hero = _.find @thangs, id: 'Hero Placeholder'
    if hero?
       # ... more code ...


Apply todos from code review to Viewer app

Todos from the code review on March 29:

[ ] Flatten file structure (no need to use folders if filenames are already clear)
[ ] Use of $log vs console.log
[ ] Put space between icons and text in buttons in a stylesheet
[ ] Split up index.html into smaller templates via Makefile
[ ] Split up viewer.app.js
[ ] Remove hardcoded rbk link in viewer.spec.js
[ ] Mock things properly in viewer.spec.js... possibly look at Shuai's code
[ ] Where noted via TODO comment reminders, check for the assertion first instead of stuffing everything inside the if block
[ ] In viewer.app.js, refactor the functions where you fetch entities from vocab tables
[ ] Internationalize the toTitleCase filter
[ ] Abstract away the code to authenticate the user via Globus

This is no longer relevant as the viewer app is now changing.


SSL not able to connect, keep getting SSL Error

Im getting SSL error when using SSL mentioned in this page this the SSL cert - https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem.
Error i get when using the provided cert:
failed: SSL error: certificate verify failed

We're running the Azure Database for PostgreSQL on version 11. Could it be another cert?, I hope you can list out all the related certs that working.
Exploring deeper I found this cert: https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem , which is from the MySQL document not from PostgreSQL and the cert is working - here the cert

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

ID: c4e9deb2-fb0e-9a91-4f07-c65ffc6a1ac1
Version Independent ID: c52bc1e8-2571-1d51-37f1-6b72f236491d
Content: SSL/TLS - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/single-server/concepts-ssl-connection-security.md
Service: postgresql
Sub-service: single-server
GitHub Login: @niklarin
Microsoft Alias: nlarin

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

@qeba
Thank you for bringing this to our attention.
I've delegated this to content author @niklarin, who will review it and offer their insightful opinions.

@niklarin
Please review it, update document as appropriate.

After careful consideration, we have decided to discontinue further updates to single-server content.
This decision was not made lightly. Our team is committed to delivering the best possible experience, and focusing our efforts on Flexible Server will benefit you more in the long run.
#please-close


Send confirmation when email address changed

Currently on PyPI, if a user changes their contact email address, there is no notification to the old email address, meaning account compromise can go unnoticed.
This means that an attacker can silently prevent other important security notifications (eg #997) from being sent to the real owner.

Thanks for another great suggestion, @edmorley, and sorry for the slow response!
This would be a very useful security feature, and now that #2898 is written and merged, it's far easier to add this feature.
Today in our development meeting we discussed where this should go on our development roadmap.
Since this feature isn't something that legacy PyPI has, I've moved the issue to a future milestone. But that doesn't have to stop a volunteer from working on it now; if someone wants to write up a pull request for it, go ahead!
Thanks and sorry again for the wait.

I think we should send an email whenever an

email is added
email is deleted
email has been changed to primary email

@brainwane I'm looking into this and will soon put up a PR.

@waseem18 We already send an email when a new address is added (the "verification" email). I don't think deleting an email should require a notification, most likely the address will be unused/invalid anyways, and a "primary change" action is the one with real security implications, so I think this issue is good. Thanks for your work!

Your welcome @di :)


ENYO-5703: Fix Marquee component to render font based on locale correctly

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Make Marquee as a styled component.
Resolution
Fix Marquee to use moon-font() mixin.
Additional Considerations
Some of moonstone components are using Marquee and handling font styling by themselves.
To minimize impact of change, I modified them to use MarqueeDecorator('div') instead of Marquee.
Here is the list of those components

moonstone/GridListImageItem
moonstone/LabeledItem
moonstone/Spinner
moonstone/VideoPlayer/MediaTitle
moonstone/internal/Picker/PickerItem

Also note that moonstone/MediaOverlay  is using Marquee but has no font styling for it.
I leave it as-is to be fixed by styled Marquee.
Links
ENYO-5703
Comments
Enact-DCO-1.0-Signed-off-by: Yeram Choi<EMAIL_ADDRESS>

This seems to be very likely to cause regressions for applications.  Is there a narrower approach we could apply?

IMO, it's a most narrow approach on framework side.
To fix it by application side, framework provides generic less mixin or new styled Marquee component and applications use it case by case.

The framework does provide a styled Marquee, it's called Item.

Closing in favor of #2007


#11 - Filter works in the first page only

In the current code, after apply de filter has a function to keep current page
but after apply the filters is more common to leave user to the first page, because a data length is changed, current page may no longer exist (Ex, filter return empty queryset, nos has second page).
for this reasson i commend this code
if (page != 0) { // this main current page
    // params = 'p=' + page + '&' + params;
}

Approved


Setting: Close tray icon on quit

Implements this feature request: #263
Adds a new setting under "tray" category

Turning this setting on will make the tray close when you close the window.
Toggling the window with the tray icon works the same.
Possible changes:

Needs translations for the new setting.
Wording can be changed if someone comes up with a better way to describe this feature.
Only show this setting if the tray icon is enabled.

I'm not sure if I'll pull this PR, I think if I maybe just remove the disable tray functionality in favour of this. But I'll probably work on something like this on my own.

I'm not sure if I'll pull this PR, I think if I maybe just remove the disable tray functionality in favour of this. But I'll probably work on something like this on my own.

I wouldn't remove the option to disable the tray icon - I think some people like having that option even if this is functionally similar.
I agree there's probably smoother ways to implement it though - maybe a dropdown with three options instead of two checkboxes.

I wouldn't remove the option to disable the tray icon - I think some people like having that option even if this is functionally similar.

I'm not so sure on that, in fact I'm not quite sure if there's any application supporting both of these options (especially if Discord is doing that on their own).
Anyway, there's also a problem with the right notifications, since when the app is not running in the background, you might not receive any notifications via Discord. There's a lot to discuss about the WebCord implementation with the tray disabled or the window closed.
In general, the option to disable the tray has its origins in times where the users reported that the tray won't display to them and thus they can't really quit from the app properly. Disabling the tray was meant to mitigate this, but it wasn't designed to make WebCord function properly.

(…) I think some people like having that option even if this is functionally similar.

@JulianHeuser going with the workflow breaking, here's an XKCD about that :wink::

I think I'll just replace the disable tray with this new option, changing a bit the localization files and where it is going to be categorised and if there will be a huge enough movement of the community against this change, I'll just re-add the old option.

I think I'll just replace the disable tray with this new option, changing a bit the localization files and where it is going to be categorised and if there will be a huge enough movement of the community against this change, I'll just re-add the old option.

If you think that's the best option I won't argue. I could work on updating this PR to work that way this weekend but I get it if you want to do it yourself.

@JulianHeuser I've actually decided I won't remove the existing tray option. I've also implemented it a bit differently than you did, it's placed under different category (as it affects the main window) and there's no like two if statements: https://github.com/SpacingBat3/WebCord/commit/95b94185d5a97485625b44dc21484fb868d49e16.
Because of this, I'll close this PR. The commit https://github.com/SpacingBat3/WebCord/commit/95b94185d5a97485625b44dc21484fb868d49e16 makes it obsolete.


Fix naming to remove pricing connotations

This hasn't published yet and PM wants to remove billing connotations.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] 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 information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

This will again create breaking changes as the name of the enum is changed. However, all these changes would be gobbled up in one go, so things should be fine.

 https://github.com/Azure/azure-sdk-for-python/pull/945

 https://github.com/Azure/azure-sdk-for-node/pull/2021

 https://github.com/Azure/azure-sdk-for-ruby/pull/641


Issue With Barco PDS Code

When using the Barco PDS code to try and program buttons for the input selection on all the variants it is set up for the wrong number of inputs and also is missing inputs. there should be inputs 1-4 as vga and 5-8 are dvi and there is also a SDI and black/Logo input that should be available. in the current code there are 4-vga and 2 dvi and black/logo as being available input selections.
I have tried all the available variants. the pds701, pds901, and pds902 and all show the same issues as showing wrong input.

@thunderbirdboy transferred your issue to the PDS module.

Hi there!
What version of Companion are you running?
In the 1.4 stable are still some issues, but bitfocus is focusing on the 2.0 release.

i have both 1.4 and 2.0 and its not in the companion software its self. its
with the code for the PDS module. the coding is missing the proper inputs.
On Sat, Jan 4, 2020 at 5:51 AM Marc<EMAIL_ADDRESS>wrote:

Hi there!
What version of Companion are you running?
In the 1.4 stable are still some issues, but bitfocus is focusing on the
2.0 release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-pds/issues/9?email_source=notifications&email_token=AOFGBT3XCK4ETBBIANRHLXLQ4BS25A5CNFSM4KCLSQEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICVO3Q#issuecomment-570775406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFGBT7ITGRUIWEZG2GVANDQ4BS25ANCNFSM4KCLSQEA
.

Oké thanks for the reply.

Can you also provide me with the full version number? (So 1.4.0 (build xxxx, 2.0.0 (build xxx), these can be found in the top bar.
Have you tried to reapply the config values, checking the ip and set the correct pds variant?
Also does disabling and enabling the module fix the missing inputs?

2.0 is (8c349cb)
1.4 is (backport-b402e70-1559)
now i have tried all of the things you listed as far as ip goes and trying
the different variants. but i do not have the PDS infront of me now. when i
load companion and go into the PDS module to try and program or assign
buttons no matter what i do i cannot access all the inputs to assign
buttons. the option in the PDS module just does not have them listed as
inputs. they are missing and unavailable. and its that way with all the
variants. if you look up the equipment models from barco you can see that
they are all basically the same inputs on all model variants. the
difference with all the PDS Models is on the output side.
On Tue, Jan 7, 2020 at 5:32 PM Marc<EMAIL_ADDRESS>wrote:

Oké thanks for the reply.

Can you also provide me with the full version number? (So 1.4.0 (build
xxxx, 2.0.0 (build xxx), these can be found in the top bar.
Have you tried to reapply the config values, checking the ip and set the
correct pds variant?
Also does disabling and enabling the module fix the missing inputs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-pds/issues/9?email_source=notifications&email_token=AOFGBT67ITHKPNMDD25O5L3Q4T7IBA5CNFSM4KCLSQEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIKQRWI#issuecomment-571803865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFGBT4VO5J36XTY3KUFYB3Q4T7IBANCNFSM4KCLSQEA
.

Prefect thanks for you reply!
I know the different pds have different inputs with the different models.
What you described is clear and should not be the case. Why this is happening is not yet clear to me and I will look into it.
I will keep you updated

So it seems that the config update was broken and therefore not working properly not populating the right inputs.
I have updated the module and asked the devs if there is a possibility to get this still in 1.4 (i doubt it)
For the 2.0 i have been working a redesign of the module with more features, this will also be available soon.
Thank for you're report :)

Thank you for looking at that. We use the 902 often and I have been hoping
for use to be able to tie into the current setup and have an actual remote
control panel. I really appreciate the effort you have dedicated to this. I
will look for the update. Thank you again for keeping in touch.
On Tue, Jan 14, 2020, 5:36 PM Marc<EMAIL_ADDRESS>wrote:

So it seems that the config update was broken and therefore not working
properly not populating the right inputs.
I have updated the module and asked the devs if there is a possibility to
get this still in 1.4 (i doubt it)
For the 2.0 i have been working a redesign of the module with more
features, this will also be available soon.
Thank for you're report :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-pds/issues/9?email_source=notifications&email_token=AOFGBT2DIZYQGHCINF2KJ4DQ5Y46FA5CNFSM4KCLSQEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6MAJA#issuecomment-574406692,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFGBT7LQ5EIJ3M7PKRHCYTQ5Y46FANCNFSM4KCLSQEA
.


[Wiki] - example of docker-compose.yml

Can you make available a docker-compose.yml example file in the wiki, for integrating this image with others like redis, mariadb, etc?
Thanks.

Yep.. I also need this


Adding conan for dependency management

I had some troubles building related to libraries which often end with 'libxcb-...-'
Had to install the following packages using apt before I got things working on my version (Ubuntu 22.04 Jammy Jelllyfish)
libx11-xcb-dev
libxaw7-dev
libfontenc-dev
libxcomposite-dev
libxdamage-dev
libxkbfile-dev
libxmuu-dev
libxres-dev
libxtst-dev
libxvmc-dev
libxcb-render0-dev
libxcb-render-util0-dev
libxcb-xkb-dev
libxcb-icccm4-dev
libxcb-image0-dev
libxcb-keysyms1-dev
libxcb-randr0-dev
libxcb-shape0-dev
libxcb-sync-dev
libxcb-xfixes0-dev
libxcb-xinerama0-dev
libxcb-dri3-dev
libxcb-util-dev
libxcb-util0-dev
Any idea why we need these now according to conan but not before?
Also, just a warning for others; first time running conan gives quite long build times (beware...). It seems like it's building QT5 for me separately again, even though I have it installed? My PC actually crashed running conan for the first time...

Ok, seems to build/run fine for me now

Nvm, I still have issues building roboteam_robothub.
There are some failing tests, in roboteam_ai, but it seems that this is not due to conan.
I also get the following warnings with QT, although the QT applications run:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Fontconfig error: Cannot load default config file: No such file: (null)
And the fonts indeed look a bit scuffed.

Font issues are fixed by adding 'FONTCONFIG_PATH=/etc/fonts/' to my environmental variables in CLion

Didnt' have any issues running, didn't run tests, kinda assumed they ran in CI.
Wondering if you're on xorg or wayland?

I had issues building roboteam_robothub because of proto stuff, what are the issues you have?

I'm on wayland. When trying to build roboteam_robothub, I get the following. It seems the proto compiler is trying to run on files which do not exist?
[60/104] Running cpp protocol buffer compiler on /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_control.proto
FAILED: roboteam_robothub/simulation_proto/proto/ssl_simulation_control.pb.h roboteam_robothub/simulation_proto/proto/ssl_simulation_control.pb.cc /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_control.pb.h /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_control.pb.cc
cd /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto && /usr/local/bin/protoc --cpp_out :/home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto -I /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_control.proto
ssl_gc_common.proto: File not found.
ssl_simulation_config.proto: File not found.
ssl_simulation_error.proto: File not found.
proto/ssl_simulation_control.proto:6:1: Import "ssl_gc_common.proto" was not found or had errors.
proto/ssl_simulation_control.proto:7:1: Import "ssl_simulation_config.proto" was not found or had errors.
proto/ssl_simulation_control.proto:8:1: Import "ssl_simulation_error.proto" was not found or had errors.
proto/ssl_simulation_control.proto:42:14: "RobotId" is not defined.
proto/ssl_simulation_control.proto:85:14: "SimulatorConfig" is not defined.
proto/ssl_simulation_control.proto:91:14: "SimulatorError" is not defined.
[61/104] Running cpp protocol buffer compiler on /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_config.proto
FAILED: roboteam_robothub/simulation_proto/proto/ssl_simulation_config.pb.h roboteam_robothub/simulation_proto/proto/ssl_simulation_config.pb.cc /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_config.pb.h /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_config.pb.cc
cd /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto && /usr/local/bin/protoc --cpp_out :/home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto -I /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_config.proto
ssl_gc_common.proto: File not found.
ssl_vision_geometry.proto: File not found.
proto/ssl_simulation_config.proto:6:1: Import "ssl_gc_common.proto" was not found or had errors.
proto/ssl_simulation_config.proto:7:1: Import "ssl_vision_geometry.proto" was not found or had errors.
proto/ssl_simulation_config.proto:43:14: "RobotId" is not defined.
proto/ssl_simulation_config.proto:72:14: "SSL_GeometryData" is not defined.
[62/104] Running cpp protocol buffer compiler on /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.proto
FAILED: roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.pb.h roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.pb.cc /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.pb.h /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.pb.cc
cd /home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto && /usr/local/bin/protoc --cpp_out :/home/rolf/roboteam/roboteam/cmake-build-debug/roboteam_robothub/simulation_proto -I /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto /home/rolf/roboteam/roboteam/roboteam_robothub/simulation_proto/proto/ssl_simulation_robot_feedback.proto
ssl_simulation_error.proto: File not found.
proto/ssl_simulation_robot_feedback.proto:6:1: Import "ssl_simulation_error.proto" was not found or had errors.
proto/ssl_simulation_robot_feedback.proto:22:14: "SimulatorError" is not defined.
[66/104] Building CXX object roboteam_networking/proto/CMakeFiles/roboteam_networking_proto.dir/messages_robocup_ssl_game_event.pb.cc.o
ninja: build stopped: subcommand failed.

@Yuhanun Check if the changes I did fixed it for you; It did fix for me, at least.

So what is the status of this branch? Can we merge it, or does conan still not work?

So what is the status of this branch? Can we merge it, or does conan still not work?

Haven't been able to work on it for a while due to a new job. I'll try take a look soon but can't promise anything.


Option to hide all warnings in the console

Reporter
Francis
Is your feature request related to a problem? Please describe.
Sometimes it can be the case that there are too many warnings that clutter the console overview.
Describe the solution you'd like
I'd like to have an option to hide or fold/minimize the warnings so you have a quicker access to the configurations and adapters.

Already fixed

Already fixed


becomeMaster vs tabPromoted vs tabUpdated

I notice that the becomeMaster event doesn't seem to work as expected, it doesn't necessarily fire when a tab becomes master.
I also notice that your sample crosstab\samples\index.html doesn't use the becomeMaster event, instead it looks at the tabPromoted and tabUpdated events and updates the state of the UI (after a setTimeout) to the new state.
I would have thought the becomeMaster event would be the only event I would need to subscribe to for knowledge of who the master is (unless I specifically wanted to know when a tab was updated).

becomeMaster only fires on the tab that is now turning into the master. tabPromoted is the event that's fired on every tab when a tab is promoted to master.
if you're trying to do some kind of resource setup, then becomeMaster is the right event to use.

OK, cheers.  I am trying to have one persistent connection to the server for realtime (signalr).  Still need to check the initial state on page load as to whether the page is master or not as no becomeMaster will fire in that scenario right?

becomeMaster event should always fire, but it's potentially possible that it's firing before you bind something to it.


Add jfree, jfreechart, swingx libraries into Gralde build script

This commit enables jfree, jfreechart, swingx libraries to be imported automatically by Gradle build script, and deletes related unused files.

Including concrete .jar, .zip files as libraries is not good practice as @claudejin knows.
Starting from this PR, all libraries must be described in gradle script as @claudejin does because it violates de-facto standard and open source license.
Good work.
P.S. this commit will be merged by current active member.


Instructions give bad advice re: installing libraries

From https://github.com/Protonerd/FX-SaberOS/wiki/Setting-up-Arduino:

Step 5: Navigate to the folder you unzipped the Arduino IDE and go to the libraries folder.
...
you must copy all folders located in libraries folder of the lightsaber software ZIP file to this folder.

You should never install libraries to the Arduino IDE installation folder. The reason is they will all be lost whenever you update to a new version of the Arduino IDE. Instead, you should always install libraries to the sketchbook folder (reference: https://www.arduino.cc/en/guide/libraries#toc5).

@jbkuma why did you close this? The same bad installation instructions are still given.


[CARBONDATA-3394]Clean files command optimization

Problem
Clean files is taking of lot of time to finish, even though there are no segments to delete
Tested for 5000 segments, and clean files takes 15 minutes time to finish
Root cause and Solution

Lot of table status read operations are were happening during clean files
lot of listing operations are happening, even though they are not required.

Read and list operations are reduced to reduce overall time for clean files.
After changes, for the same store, it takes  35 seconds in same 3 node cluster.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NA

[x] Any backward compatibility impacted?
NA

[x] Document update required?
NA

[x] Testing done
tested on three node cluster
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3302/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3505/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11569/

@ravipesala please review

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3534/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11599/

@kumarvishal09 please review

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3334/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3535/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11601/

LGTM


Create Project Details page

Create the Project details page as seen in the Figma design.
With the help of already created components such as

Top Navigation,
Bottom Navigation bar,

seen in closed issues here, create the Project details page.

@PetraAG   I wish to work on this page


📌 Upgrade Analytical Platform Compute EKS to 1.30

This pull request:

Upgrades EKS to 1.30

https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-eks-distro-kubernetes-version-1-30/
https://kubernetes.io/blog/2024/04/17/kubernetes-v1-30-release/

Notes:

apply fails because no version is returned from AWS API when requesting versions for aws-guardduty-agent for EKS 1.30, I have raised this with enterprise support. It doesn't affect clusters upgrading, but would affect new clusters

Signed-off-by: Jacob Woffenden<EMAIL_ADDRESS>

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@jacobwoffenden Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance


Remove redundant code

Just removing a lot of redundant code + minor code improvements & typos fixes.
Test plan

CI passes
plugin can be built and run

No new code = no new bugs, right..? Right?

No new code = no new bugs, right..? Right?

less code less bugs 😄


added text-diff tool

Type of Pull Request

[ ] Bug fix
[x] Enhancement

Related Issue #s or links (if any):
Description of Changes

@AnkitaMalik22 Please check the deploy log for errors, I think you just need to run npm run lint to auto-fix some linting errors.
https://app.netlify.com/sites/developertools-tech/deploys/633e840b3a748b00080bc41b

@AnkitaMalik22 great job on this! We need to address a few things before we can merge.
The two text fields seem to change when the page is reloaded, the keys on useLocalState need to be different so they are saved separately.
Also, the test file is empty, I am happy to help with that if needed?
One last thing, the two input fields should wrap on mobile, they get too narrow to be very usable when they are side by side.

I'm sorry I've never worked on test files before.

@AnkitaMalik22 I will take some time to figure out whats going on here and give you some advice, ok?

@AnkitaMalik22 I've rebased your branch onto the dev branch here - https://github.com/developertools-tech/developertools.tech/tree/text-diff-rebase
You can force push it to your fork like this:
git remote add devtoolstech https://github.com/developertools-tech/developertools.tech
git fetch devtoolstech
git checkout text-diff-rebase
git branch -D text-diff
git checkout -b text-diff
git push -f -u origin text-diff

That should hopefully get all the tests passing so I can do a review.
Let me know if you have any questions :-)


Version 4 changes

Add eslint to peerDependencies
Bump peerDependencies versions
Add flowtype/require-valid-file-annotation rule

@JamesLefrere would you mind to give your blessing?


Question about the protocol

Hi,
I found your repo and i am trying to interact with the heater using ESPHome and i had few questions which i was hoping you could answer :
After Connect i have to write to the characteristic and then i can read the value, i tried it on the LightBlue app for iOS and i did got a response. Now to get values each time the heater has a new value i would like to subscribe so i can get notify but i am not sure i understand. If i subscribe and i get notified of a change i guess i need to do a read of the characteristic again or do i again have to write each time before i read ?
Do you know if the heater will send a notification when things changes like power on/off, temperature, level, etc ?
Essentially what i am trying to do is to run the heater with a separete thermostat so i can control as the way it works today it way to unreliable in terms of temperature, you set it to 27C and the room is 19C.
/donnib

Hi @donnib, I don't have access to the heater anymore so I can't check.
From what I remember, the notifications are a one-off. That is, you send your request and subscribe to the notifications, and get a single response back as the notification. In order to get updates, you need to poll the unit using the readonly get status command.

@donnib have you made any progress on this?


README: tweak intro and include concrete use-cases

This is based on our recent HackerNews Post and the description on our website.

I think this is better than what we have now. We can iterate further over the next week. For now this is an improvement, so I'll merge.


hookable functions in Shopware_Controllers_Widgets_Emotion

Shopware_Controllers_Widgets_Emotion doesnt allow modification of eg getBlogEntry, because of a private functions. in our use case we want to extend core blog widget with a category filter, but we are not able to reuse core because of missing hookable possibility. just make them protected resolves this.

Dear Contributor,
Thank you for your contribution to Shopware. We value your engagement.
Unfortunately we have to close all existing Pull Requests.
This is due to the new Shopware 5 Major Release and a restructuring of the branch names.
If your contribution is still relevant for Shopware 5, a new pull request is highly appreciated.
We are very sorry for this inconvenience.
Greetings from the Shopware Team.


Spanish

Added Spanish translation from Transifex.
@josek5494, thank you for your contributions! Please review the test fixtures in this PR for any edge cases that may need to be overridden. Incidentally, it looks like we got very lucky in that we only ended up needing feminine ordinals (for destina and salida).
/cc @MallorcaRedes

Also, if any strings need to differ from country to country (such as Spain versus Colombia), please let me know and I’ll be happy to add the appropriate languages to the Transifex project.

Please don't forget to remove Spanish code replacement in frontend's itinerary_builder.js code after all.

Oh, interesting. @freenerd, what’s the story behind that special case? Do we need to remove special cases anywhere else in the frontend?

@1ec5 my guess is that the frontend relies on existing i18n in Leaflet Routing Machine for languages that are not yet in osrm-text-instructions.

But my guess is easier - frontend has its own Spanish translation block - this automatically enables Spanish 'Change language' option - so to prevent 'Missing language' error from osrm-text-instructions, this lang code is temporary replaced :wink:

@yuryleb and @perliedman are correct. Ticketed in https://github.com/Project-OSRM/osrm-frontend/issues/232


Query: Skip formatting strings if debug logging is disabled

After upgrading from v0.34.1 to v0.36.0, I see some queriers using about 10 times more CPU than before. These queriers only receive ~16 instant http q/s and have over 20 endpoints.
A pprof profile showed that the GC is using most of the CPU, so I ran a pprof heap alloc_space, and the problem seems to be fmt.Sprintf used in the debug message in the store proxy, even if debug logging is disabled.

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
I added a validation to skip the string formatting if debug logging is disabled.
Verification
I deployed a patch with this change and it definitely fixed the CPU usage. This graph is avg CPU usage after removing the formatting in matchingStores and then after removing it in storeMatches and storeMatchDebugMetadata.

Do we actually need those debugging messages at all?


Status of Merlin Falcon

On the website Merlin Falcon status appears as:
AMD Merlin/Falcon Embedded System is also not currently supported by the public Repo.
Is there a way to get access to the "private repo"/preview?
We (qtec) already have NDA with AMD.

This is supported out of our embedded team

@gstoner  This means that ROCM already supports Merlin Falcon, or that I need to ping the Embedded Team. And where? Thansk!


Update highcharts to 8.1

This is a minor update and should be safe to take as a drop-in, but there were some upgrade notes in https://www.highcharts.com/blog/changelog/ and HC is important/complex enough it warrants a careful look.

Changelog didn't contain anything too scary. Banged on our charts in toolbox, looked ok so far. Will discuss with Colin as well

https://github.com/xh/hoist-react/tree/updateHighcharts


feat(quest): include completions and points fields

Same idea as #174 but for quest notifier

Is there any concern for people misinterpreting %POINTS%/questPoints as the incremental points earned from the given quest?


[BUG] Management cluster VM is constantly above 100% memory pressure

Describe the bug
Management cluster VM is constantly above 100% memory pressure. Perhaps a different memory configuration should be used?
To Reproduce
Steps to reproduce the behavior:

Deploy AKS service on an HCI cluster

Expected behavior
Memory pressure should be under 100%
Screenshots

Environment (please complete the following information):

AKS-HCI Version <IP_ADDRESS>
Kubernetes Version 1.18.14

Collect log files
https://1drv.ms/u/s!Aq86yCB_tZaGoZYFq72eJBf6r2oLHg?e=Dw3kPK

Actually this is not related with performance and it can be safely ignored. We have document it here, https://docs.microsoft.com/en-us/azure-stack/aks-hci/known-issues#hyper-v-manager-shows-high-cpu-andor-memory-demands-for-the-management-cluster


target: zephyr: Update to Zephyr 1.6 API.

Zephyr 1.6 switched to "unified kernel API". Old API is supported, but
deprecated and leads to warnings.
JerryScript-DCO-1.0-Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

Zephyr 1.6 is at RC3 now, the release is expected next week. Note that this breaks compatibility with the current latest release, 1.5, so one approach for this patch is to merge it next week. OTOH, JerryScript 1.0 release supports Zephyr 1.5 release, and the master is for development.
@poussa, @sergioamr : Please suggest on the best timing to merge this.

LGTM

LGTM
Lets merge it now since Zephyr 1.6 will be released soon.


Make transition shader material configurable

As a game developer using Escoria I'd like to configure how the scene transition is played. I may even want to change that dynamically.
The transition is using a shader in the color rect of transition.tscn. This shader is using a grayscale gradient which is configured as a texture in the shader params. This texture should be configurable in the project settings and changeable using code.

(breakout issue of #314)


Show correct artifact run node details on artifact side drawer panel

JIRA: https://issues.redhat.com/browse/RHOAIENG-7544
Description

Updated the way we search for the artifact details for a specific node. Also, I removed the status for the artifact node because an artifact node shouldn't have status. (I checked that in KF UI)

How Has This Been Tested?

Import the pipeline listed in the JIRA ticket
Create a run using that pipeline
Compare the artifact details with the KF UI to make sure the info is correct

Test Impact

N/A, it's topology side panel details change, hard to write test.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@DaoDaoNoCode I think Yan wants artifact nodes to be green if they exist and then grey otherwise
see this mock: https://www.figma.com/design/etbN0ccCcZR1qKCpJXQNAg/Pipeline-phase-2?node-id=1585-97434&t=BZENynAkmHo29x6Z-0

@Gkrumbach07 Updated PR based on the mockup

This looks good. we just need one more reviewer to merge
/lgtm