Feature: Bring to foreground

Summary
Working very well.
PR Checklist

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #14730
[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Lanuch the app
Bring another window (not Files) to foreground
Activate with Win+E
See the window will be brought to foreground

Screenshots
None

Can we revert the changes in #13588?

Can we revert the changes in #13588?

Done

This bring also when the app lanches for the first time.
So when user bring Chrome for example right after the lanuch, the app will be brought to the foreground. Should I limit to run this code to activation?

So when user bring Chrome for example right after the lanuch, the app will be brought to the foreground. Should I limit to run this code to activation?

I think so, otherwise we can end up with the app being unexpectedly focused.

Done


Status icons not colored

Seen this a few times, especially on a cold launch. Refreshing fixes it.

Bug Report Dump (Auto-generated)

Version 1.19.0<PHONE_NUMBER>)
Device: iPhone X (iOS 11.3)
TestFlight: true

Models are probably cached before the status fetch finishes or something? Great issue for someone to pitch in!
Sent with GitHawk

I haven't seen this issue and it's going to be hard to reproduce, but I think I know how the issue might be caused.
Perform Fetch
githubClient.client.send(V3RepositoryNotificationRequest(all: all, owner: repo.owner, repo: repo.name)) { ...

On Fetch Success
Create view models
CreateNotificationViewModels(
    width: width,
    contentSizeCategory: contentSizeCategory,
    v3notifications: response.data
) { [weak self] in
    self?.fetchStates(for: $0, page: response.next, completion: completion)
}

During ViewModels Create
Set state to .pending
state: .pending, // fetched later

On Create Completion
Fetch States. If case .failure overwrite cache (with view models in initial state .pending).
githubClient.client.send(ManualGraphQLRequest(query: query)) { result in
            let processedNotifications: [NotificationViewModel]
            switch result {
            case .success(let json):
                var updatedNotifications = [NotificationViewModel]()
                for notification in notifications {
                    if let alias = notification.stateAlias,
                        let result = json.data[alias.key] as? [String: Any],
                        let issueOrPullRequest = result["issueOrPullRequest"] as? [String: Any],
                        let stateString = issueOrPullRequest["state"] as? String,
                        let state = NotificationViewModel.State(rawValue: stateString),
                        let commentsJSON = issueOrPullRequest["comments"] as? [String: Any],
                        let commentCount = commentsJSON["totalCount"] as? Int {
                        var newNotification = notification
                        newNotification.state = state
                        newNotification.comments = commentCount
                        updatedNotifications.append(newNotification)
                    } else {
                        updatedNotifications.append(notification)
                    }
                }
                processedNotifications = updatedNotifications
            case .failure:
                processedNotifications = notifications
            }
            cache.set(values: processedNotifications)

I was thinking of maybe adding a conditional check upfront to ensure we pull a view model out of the cache or create if it doesn’t. Would happen in fetch closure.
At the moment the fetch closure is creating an empty view model every time, expecting it to be populated by new data.

I'm not up to speed with the project so I'm kinda reverse engineering as I go 😅
I can see you have a cache with a get func like so
func get<T: Cachable>(id: String) -> T?

So it looks like the view model must first be created and populated with an ID because it conforms to Cachable. Got it!
Ok, so fetch > create view model > assignID > consult cache for any existing data
if data exists then pass that cached data along to be updated.
What you think?

@rob-nash yup! Exactly

Ok, I'll give this a go this morning.
@rnystrom would you mind giving this one a once over please?


No music found

Mac app on Mavericks shows 1 connected
Enabled SimonRemote in System Prefs for accessibility (assistive apps)
Verified the Pebble App on iPhone 6 Plus is in the foreground
App on Pebble shows "No music found."
Tried doing a refresh on the Pebble app.
Suggestions?

Fixing soon.

dup of #1

Try these steps.
Right click on SimonRemote.app and click View Package Contents.
Go into Contents->Resources and double click on iTunes-info. Run that Script when iTunes is running.
Does it print out valid information at the bottom?


grandpa: report metrics on prevotes and precommits cast

This adds a new prometheus and telemetry metric for every prevote/precommit that is cast by the local GRANDPA voter.
cc @mattrutherford

@ddorgan This is another metric that might be useful to track on validators that are elected, e.g. if the number of prevotes / precommits doesn't increase for > 1 minute then we should alert.

@andresilva looks great, have it deployed on two westend nodes since the end of last week. Would be great to have this in the next release.

@mxinden is this good to merge with the two changes you suggested committed?


build: Streamline mocha config

Adds support for native mocha config support - now we can use npx mocha without passing additional args/config

Additional note/context: Mocha merges the config file (.mocharc - owned by owl-bot/synthtool) and package.json#mocha (owned by us): https://mochajs.org/#merging


graph.query wont escape params

Hi,
From my experience, query bindings capabilities escape the data before it is being saved to the database. for security reasons and data integrity reasons...
await graph.query("CREATE (n:Person { name: $name })", {name: 'test"abc'});
This will throw an error:
ReplyError: errMsg: Invalid input 'a': expected ';', a statement option, a query hint, a clause or a schema command line: 1, column: 1, offset: 0 errCtx: abc"  CREATE (n:Person { name: $name }) errCtxOffset: 0
    at parseError (/usr/src/app/node_modules/redis-parser/lib/parser.js:179:12)

I think it must be escaped by the framework...
Thanks

@avifatal
please verify so I can close this issue

@DvirDukhan Thanks for the fast reply. I was a little bit off. will have a soon. thanks

Verified

@DvirDukhan Hi,
When are you going to release it here https://www.npmjs.com/package/redisgraph.js ?
Thanks

@avifatal
this week

@avifatal published

Toda!

Bevakasha
I think you should wait for 2.2.1
https://github.com/RedisGraph/redisgraph.js/pull/56
I missed an edge case


Ability to upgrade stopped stack for catalog

v0.44.0
Steps to Reproduce:

Create an older version of a catalog entry.
Click on upgrade button in UI

Result: Unable to upgrade the services.

We should also support upgrade for stack having mix of active/inactive services

Some better steps written by @tfiduccia
Steps;

Add Elasticsearch Stack with older version of rancher
Click on upgrade before you start any services
Try to finish upgrade

Results:
It gets stuck trying to upgrade.
Expected:
Should not get stuck.

@sangeethah you can test this fix using the UI only. Could you file a separate bug to enable rancher-compose support?

Tested with build from master - dec 3

Add Elasticsearch Stack with older version of rancher. Choose not to start the service.
Click on upgrade before you start any services

kpof service tries to get upgraded but gets stuck in "activating" state since the containers get constantly restarted . All other services in the stack continue to remain in "Inactive" state.
Following exception seen in kpof container logs:
12/3/2015 7:29:51 PM2015/12/04 03:29:51 [emerg] 1#1: host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:29:51 PMnginx: [emerg] host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:30:19 PM2015/12/04 03:30:19 [emerg] 1#1: host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25
12/3/2015 7:30:19 PMnginx: [emerg] host not found in upstream "es-clients:9200" in /etc/nginx/nginx.conf:25

hm, looks like a compose bug. When upgrade stack, we should call upgrade for every service in order defined by links (similar how we start the services when stack.activate is called). Otherwise master service can get upgraded before service we depend on, even created. @ibuildthecloud ^^

@alena1108 I believe that is how it works today.

Verified with v0.51.0 that this is still a bug in rancher-compose v0.7.0.
Steps to Reproduce:

Start ElasticSearch catalog item using old version (uncheck start services after creation)
After creation, click on upgrade available and select new one.

kopf service gets stuck in activating as per @sangeethah's comments.

Would it be related if I am unable to stop a "Finish upgrade" when there is a port conflict that can only be stopped by deleting the service in the stack

@asciifaceman What state is your service in? Is it still trying to Uprgrade? This issue is specifically about having inactive stack and trying to upgrade the stack.

Ah, it's not a match then. My situation was clicking "Finish upgrade" on an
active service with a port conflict puts it in an infinite loop that can
only be stopped by deleting it entirely.
On Tue, Mar 22, 2016 at 3:38 PM, Denise<EMAIL_ADDRESS>wrote:

@asciifaceman https://github.com/asciifaceman What state is your
service in? Is it still trying to Uprgrade? This issue is specifically
about having inactive stack and trying to upgrade the stack.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/2650#issuecomment-200063862

--
Charles P. Corbett

Tested on 1.0.0-rc5 and can't reproduce.

Verified with v1.0.0-rc6.


Exmaples for Online Bandit Alogirhtms with Replay Method

I add a quickstart notebook and an example script for OPE with online bandit algorithms using Replay Method (RM).
To calculate ground-truth policy values for online bandit algorithms, I implemented SyntehticBanditDataset.sample_reward and simulator.calc_ground_truth_policy_value.
I added test code for SyntehticBanditDataset.sample_reward but not for simulator.calc_ground_truth_policy_value because test_simulator.py does not exist. If you want me to create test_simulator.py, I will do it.

@Kurorororo Thanks! Can you address the following points?
[nits]

You use distribution of rewards several times in several files. It is correct, but I think reward distribution is better as it is meaningful and also simple.

In the quickstart example, you use evaluation_policy_epsilon_greedy, evaluation_policy_lin_ucb, and evaluation_policy_lin_ts to define the (online) evaluation policies. I think just epsilon_greedy, lin_ucb, and lin_ts are sufficient here.

When calculating the ground-truth policy values, can you reveal the arguments of calc_ground_truth_policy_value? This will make it easier for users to learn how to use the function.
I mean, I recoomend

policy_value_epsilon_greedy = calc_ground_truth_policy_value(
    bandit_feedback=bandit_feedback,
    reward_sampler=dataset.sample_reward, # p(r|x,a)
    policy=evaluation_policy_epsilon_greedy,
    n_sim=3 # the number of simulations
)

I think :math:r \sim p(r \\mid x, a) is more understandable than just :math:p(r \\mid x, a).
https://github.com/Kurorororo/zr-obp/blob/04813d9938f3be3db49c4919c7d9fc49783318cf/obp/dataset/synthetic.py#L213

There is a typo in the titile Bndit -> Bandit
https://github.com/Kurorororo/zr-obp/tree/04813d9938f3be3db49c4919c7d9fc49783318cf/examples/online

[ask]

Why did you implement sample_reward and sample_reward_given_expected_reward separately?
https://github.com/Kurorororo/zr-obp/blob/04813d9938f3be3db49c4919c7d9fc49783318cf/obp/dataset/synthetic.py#L245

Thank you for the review.

You use distribution of rewards several times in several files. It is correct, but I think reward distribution is better as it is meaningful and also simple.
In the quickstart example, you use evaluation_policy_epsilon_greedy, evaluation_policy_lin_ucb, and evaluation_policy_lin_ts to define the (online) evaluation policies. I think just epsilon_greedy, lin_ucb, and lin_ts are sufficient here.
When calculating the ground-truth policy values, can you reveal the arguments of calc_ground_truth_policy_value? This will make it easier for users to learn how to use the function.
I think :math:r \sim p(r \mid x, a) is more understandable than just :math:p(r \mid x, a).
There is a typo in the titile Bndit -> Bandit

I addressed these comments in the latest commit.

Why did you implement sample_reward and sample_reward_given_expected_reward separately?

This is because obtain_batch_bandit_feedback needs expected_reward when the reward type is 'continuous'.
I implemented two functions to extract expected_reward here.
https://github.com/st-tech/zr-obp/blob/44bec59ba7c33043d08a1e13beca15aeccb40049/obp/dataset/synthetic.py#L290-L300

@Kurorororo Thanks! LGTM!


Support for kotlinx.serialization

I'm not 100% sure how in-scope this is, but it'd be great to bundle a simple default kx.ser serializer, just for convenience's sake. A simple primitive one over Strings would be great!

Hi @gdude2002 ,
Thank you for reaching out, I've created a PR that adds built-in serializers, is there anything else that you'd like to see included? Here's the PR: https://github.com/z4kn4fein/kotlin-semver/pull/3
Thanks!

Looks good to me - thanks for that!

It seems I have conflicts with the kotlinx.serialization package in terms of supported targets; I think it might be better to create a separate package for the serializers.
What do you think?

Hmm, that's difficult - I know it's possible to do default serializers multi-platform, but to be entirely honest I just use Kotlin/JVM, so I have no clue.
I'll ask around and see if I know anyone that might have any ideas.

It works fine where kotlinx.serialization is supported, but my package has +N targets that are not supported by kotlinx.serialization by default.
I see two options here, degrade the number of supported targets to match exactly with kotlinx.serialization's supported targets, or publish a new package with matching targets and leave this library untouched.
I prefer the second option, but I can't add the @Serializable annotation to the Version class.
Or, if possible (I'm not sure), just put the annotation there for the matching targets, but I have to research that's it even possible.

In the end, I just released a new version with the serializers (1.3.0) for those platforms that supports kotlinx.serialization. Please let me know if you have any feedback!

Looks good to me - thanks for your work!


Added Builder class to build rules

Fixes #7

I like it. Will have to play with it.

I played with the idea of refactoring Rule to StringRule or something like that, but it would break the existing API.

I played with the idea of refactoring Rule to StringRule or something like that, but it would break the existing API.

I'm OK with that, but I think I would prefer

not having a BaseRule; call that Rule
Rule (currently BaseRule)'s constructor being internal
Rule having a static method FromString

When adding breaking changes, do you mind also refactoring all Rule classes into their own namespace (PasswordSharpRules.Rules)?

When adding breaking changes, do you mind also refactoring all Rule classes into their own namespace (PasswordSharpRules.Rules)?

Yeah, sounds good.
(Tokenizer should probably also be internal, and maybe move to a new namespace PasswordSharpRules.Rules.Parsing?)

I wouldn't want to touch the tokenizer, as it seems OOS for this PR

I wouldn't want to touch the tokenizer, as it seems out of scope for this PR

c9e3732c6af01c2618c9da7cd10c978fca26236a

@chucker Done

The only thing left that I would change is to make IncompleteRule internal too.

The only thing left that I would change is to make IncompleteRule internal too.

agreed


Full Output pushes content/sections to the right in live-log scenarios

Seems to happen after a console-line-clearing happens (e.g. "collecting...").
html_report.html.txt

Still occuring in 1.9+. Worth some investigation.


fix(#patch); aave v2 forks; fix lendingConfig issues

Addressing QA #773
issues:

The reserveFactor is not being properly updated in the amm markets in some cases.

Fix:

make the lendingPoolConfiguration handlers/templates less verbose and hardcode it in instead of tracking the proxy upgrades as a template
remove LendingPool template since it is more verbose and prone to error than just tracking the proxy listed here: https://docs.aave.com/developers/v/2.0/deployed-contracts/amm-market
add getOrCreateMarket() since reserve factor is being set on markets before they are initialized in order to capture these changes

Testing:

https://okgraph.xyz/?q=dmelotik%2Faave-v2-ethereum-amm

@jaimehgb

What were the benefits of tracking proxy upgrades via templates? What do we potentially lose from ignoring them?

I am not sure there are any benefits. This is what aave did in their official subgraph and when we initially made aave v2 we copied that, and i didn't pay much mind to it bc it worked. It is possible that this is what needed to be done in an old version in graph-cli. but I would say this is not good practice anymore, it is too verbose and makes a simple thing harder to understand.

Does the contract API change in a relevant way in any of those upgrades?

Not from what I am aware of, we would probably have issues if that was the case. Because tracking the new proxy every time does not give you the new ABIs. When an ABI is changed in a proxy upgrade we would need that new ABI in the mappings in order to utilize the events/functions.


[Bellesa] add new extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

As this doesn't have a linked site support request issue, please complete the site support request template: you can paste it here.

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://www.bellesa.co/videos/6698/quaranteened-pent-up

Description

WRITE DESCRIPTION HERE

The website features nsfw content btw. Dunno if that's important to note.

So I gathered. Thanks for your work, anyway.
Please

add # coding: utf-8 as the first line
use 'single quoted strings' rather than "double"
explain or comment what the block if "VideoCard" not in webpage: is for.

Then I'll review in more detail.

I applied your suggestions. If there's anything else that needs adjustments, just let me know.


Alignment of line numbers is too low/high

Here it is using the different fonts it lists on my setup.

Unfortunately the line numbers are drawn entirely differently than the hex text, and so to properly fix this it would need to be refactored to use the same text renderer, but that text renderer is meant for fixed-width drawing, and the line numbers are drawn as normal text, so it's a tricky fix..

Should be fixed with<PHONE_NUMBER>1048aeb6df84561cb37c108760e867 and 7f251f4c790fa2c309bdea1e3ff6c06631d8d113
The line numbers were being drawn centered, but were off by one point for some reason. However the hex/plain text were not centered, although sometimes it looks like it was. Resolving both of these fixes the issue.
Happy New Year! 🎉


Unfollowing does not remove notes from follows feed

Running Astral on what I think is effectively current master HEAD, I see messages of unfollowed accounts in my "follows" feed.
This problem persists for days, with many reloads and tab close and re-opens.
I unfollowed jb as can be seen on the "following" list, yet I see many of their notes.

While some "in reply" ones were in reply to my notes, so those should probably stick around, the screenshot also contains one that is not "in reply".

yeah currently the only way to remove is to remove all data and then resync which is a huge pain. I am working on db stuff now so going to fix this at the same time (don't really want to do a short term fix for this)

this is fixed now, closing.


Authentication error when deploy

Describe the bug
Since yesterday I can't deploy my bots, I have tried on different machines and OSs, I  can login into the azure portal and manage all the resources but when I try to deploy I get the error below(screenshots section):
Version
1.3.0
Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[x] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Open my project, to the publish tab, select the bots to publish, click on "Publish selected bots", a new popup comes up to enter my credentials and after entering my email and password I get the error below.
Expected behavior
I should be able to publish my bot.
Screenshots

Additional context
By mistake my AD account was deleted a couple of days back, the sysadmin recreated my account yesterday so I am not sure if it's related. I can login into any other service that uses my domain account (Azure, Outlook, etc)

@pedro-ramirez-suarez the context looks related:

By mistake my AD account was deleted a couple of days back, the sysadmin recreated my account yesterday so I am not sure if it's related. I can login into any other service that uses my domain account (Azure, Outlook, etc)

Can you make sure you have your account and subscriptions properly set up?

Hi @cwhitten,
I can login into Azure without any issues and even manage all the bots that I already deployed, I can see my subscriptions, the only thing that I can't do is deploy from composer. Do you have any idea of what settings could be wrong that prevents me to deploy?

Hi @pedro-ramirez-suarez Let me check some things and get back to you.

Hi @pedro-ramirez-suarez I tested by trying to do the same thing (creating an account that I then removed and re-added), but was unable to reproduce this.
Are you able to create a new bot and new publishing profile and log in successfully with that?
If so, can you try creating a new publishing profile on the existing bot and try?

I can't either create new a publish profile or publish to an existing profile, maybe the problem is on the authentication service not in composer?

It might be. If you have the az cli tools (or can install them), are you able to log in with the same creds?
az login
And to clarify; this is a Work/School account, not a personal MSA, correct?

Closed due to inactivity.


delimiter '|' is not allowed

I tried readcsv("c:/data/some.csv"; delim = '|') and it gives error delimiter '|' is not allowed. Why not?

This is fixed by c12dfd06fc62302cf6f9ce384c1e590289cdb166.


Add Benchmarks

This PR add benchmark tests and results comparison in to CI.
Comparison of two similar benchmarks
NOTE: % differs by < 2%
 $ go tool pprof -top -diff_base=bench.out -normalize -show="github.com/socketplane/libovsdb.*" -hide="github.com/socketplane/libovsdb\.[bB]ench.*" bench1.out
File: libovsdb.test
Type: cpu
Time: Apr 14, 2021 at 12:02pm (BST)
Duration: 2.94mins, Total samples = 97.83s (55.44%)
Active filters:
   hide=github.com/socketplane/libovsdb\.[bB]ench.*
   show=github.com/socketplane/libovsdb.*
Showing nodes accounting for -0.14s, 0.15% of 97.83s total
      flat  flat%   sum%        cum   cum%
     1.59s  1.63%  1.63%      1.59s  1.63%  github.com/socketplane/libovsdb.OvsSet.MarshalJSON
    -0.92s  0.94%  0.69%     -0.92s  0.94%  github.com/socketplane/libovsdb.OvsMap.MarshalJSON
    -0.63s  0.65% 0.044%     -0.63s  0.65%  github.com/socketplane/libovsdb.(*OvsMap).UnmarshalJSON
    -0.08s 0.084%  0.04%     -0.18s  0.18%  github.com/socketplane/libovsdb.(*OvsSet).UnmarshalJSON
    -0.05s 0.054% 0.094%     -0.09s 0.097%  github.com/socketplane/libovsdb.(*OvsSet).UnmarshalJSON.func1 (inline)
    -0.04s 0.043%  0.14%     -0.04s 0.043%  github.com/socketplane/libovsdb.ovsSliceToGoNotation
    -0.01s  0.01%  0.15%     -0.01s  0.01%  github.com/socketplane/libovsdb.setify

Comparison of tow dissimilar benchmarks
NOTE: % differs by > 20% where a 1 second sleep was added in the OvsSet.UnmarshalJSON function
$ go tool pprof -top -diff_base=bench.out -normalize -show="github.com/socketplane/libovsdb.*" -hide="github.com/socketplane/libovsdb\.[bB]ench.*" bench2.out
File: libovsdb.test
Type: cpu
Time: Apr 14, 2021 at 11:32am (BST)
Duration: 2.75mins, Total samples = 97.83s (59.35%)
Active filters:
   hide=github.com/socketplane/libovsdb\.[bB]ench.*
   show=github.com/socketplane/libovsdb.*
Showing nodes accounting for -3.41s, 3.49% of 97.83s total
Dropped 1 node (cum <= 0.49s)
      flat  flat%   sum%        cum   cum%
   -21.69s 22.17% 22.17%    -24.89s 25.44%  github.com/socketplane/libovsdb.(*OvsSet).UnmarshalJSON
    14.21s 14.52%  7.65%     14.21s 14.52%  github.com/socketplane/libovsdb.OvsSet.MarshalJSON
     4.13s  4.22%  3.43%      4.13s  4.22%  github.com/socketplane/libovsdb.(*OvsMap).UnmarshalJSON
     3.14s  3.21%  0.22%      3.14s  3.21%  github.com/socketplane/libovsdb.OvsMap.MarshalJSON
    -3.06s  3.13%  3.35%     -3.20s  3.27%  github.com/socketplane/libovsdb.(*OvsSet).UnmarshalJSON.func1 (inline)
    -0.14s  0.14%  3.49%     -0.14s  0.14%  github.com/socketplane/libovsdb.ovsSliceToGoNotation

I'm expecting this to fail CI on the download-artifact step, since no artifacts have been generated yet...
Closes: #80

Coverage remained the same at 76.932% when pulling 020656b138f4eedc99cbd9159930871b0c843a0f on dave-tucker:bench into 0c231867ccfd3308c8f263d26c0358c2fd8fba35 on socketplane:main.


infinite downloading 100% in download new mods

Geode Issue

[X] I confirm that this bug is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
SDK commit
No response
Geode Version
v2.0.0-beta.18
Mods Installed
GD mega overlay v2.4.6
Expected Behavior
I expected to download mods in GD
Actual Behavior

Steps to Reproduce
idk because after I download mod. it happens again and again
Additional Information
No response

did you solve the problem?

what did you do to fix it? i have the same poblem


Channel tests failing for variant=release with GCC

Following addition of variant=debug,release to Travis CI in #50, the GCC 5.4.1 build job is failing due to failing channel tests, see https://travis-ci.org/boostorg/gil/jobs/355009262
testing.capture-output bin.v2/libs/gil/test/channel.test/gcc-5.4.1/release/channel.run
====== BEGIN OUTPUT ======
std::exception
EXIT STATUS: 1
====== END OUTPUT ======

Interestingly, the same tests built with clang 4.2.1 are passing without any failures, see https://travis-ci.org/boostorg/gil/jobs/355009263
I confirmed this issue locally, on Ubuntu with GCC 5.4.0
b2 variant=debug,release cxxflags="-Wno-unused-local-typedefs" test
...
testing.capture-output ../../bin.v2/libs/gil/test/channel.test/gcc-5.4.0/debug/channel.run
**passed** ../../bin.v2/libs/gil/test/channel.test/gcc-5.4.0/debug/channel.test
...
testing.capture-output ../../bin.v2/libs/gil/test/channel.test/gcc-5.4.0/release/channel.run
====== BEGIN OUTPUT ======
std::exception

EXIT STATUS: 1
====== END OUTPUT ======

References
Yet another issue revealed by variant=release build configuration.
Previous one was the image checksum tests, see #49

More info related to this bug in https://github.com/boostorg/gil/pull/50#issuecomment-376719681

The error occurs when compiling the channel.cpp test with g++ -O3.
A noteworthy observation: Using -Wall yields these warnings, which may be related:
../../boost/gil/channel.hpp: In function ‘void test_packed_channel_reference()’:
../../boost/gil/channel.hpp:441:79: warning: ‘*((void*)&<anonymous> +16)’ is used uninitialized in this function [-Wuninitialized]
     void set_unsafe(integer_t value) const { this->set_data((this->get_data() & ~channel_mask) | (( static_cast< BitField >( value )<<FirstBit))); }
                                                             ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
../../boost/gil/channel.hpp:441:79: warning: ‘*((void*)&<anonymous> +16)’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     void set_unsafe(integer_t value) const { this->set_data((this->get_data() & ~channel_mask) | (( static_cast< BitField >( value )<<FirstBit))); }
                                                             ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
../../boost/gil/channel.hpp:441:79: warning: ‘*((void*)&<anonymous> +16)’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     void set_unsafe(integer_t value) const { this->set_data((this->get_data() & ~channel_mask) | (( static_cast< BitField >( value )<<FirstBit))); }
                                                             ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
../../boost/gil/channel.hpp: In function ‘void test_packed_dynamic_channel_reference()’:
../../boost/gil/channel.hpp:563:42: warning: ‘*((void*)&<anonymous> +32)’ is used uninitialized in this function [-Wuninitialized]
         this->set_data((this->get_data() & ~channel_mask) | value<<_first_bit);
                        ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~

which confuses me. I don't even understand which of the referenced variables / values the compiler believes to be uninitialized...

Indeed. It might be worthwhile trying to compile with g++ -fno-strict-aliasing -O3 to see whether that works around the failure seen with g++ -O3.

Can someone please provide a minimal reproducible code sample?

Great!
Are you using any fancy compiler switches like the ones @stefanseefeld mentioned?

You call '-O3' fancy ??? :-)
On Fri, Apr 13, 2018, 18:49 chhenning<EMAIL_ADDRESS>wrote:

Great!
Are you using any fancy compiler switches like the ones @stefanseefeld
https://github.com/stefanseefeld mentioned?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boostorg/gil/issues/51#issuecomment-381278596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABL411CN7mDM_ss89k9LNG71ulrCVY0sks5toSt2gaJpZM4SvOrc
.

@chhenning during local testing I tried all sorts of switches, optimisation levels, with and without strict aliasing etc.
On CircleCI all builds are using the same switches as defined in our root Jamfile https://github.com/boostorg/gil/blob/develop/Jamfile
And there are two build variants: debug (those run first) and release with optimisation=speed (those run if corresponding debug pass, hence you see two walls of builds).

:-)
This one I call fancy: -fno-strict-aliasing

@mloskot you are correct. What about the other bug?

No news yet on the checksum bug from me. Got busy with the bitsN refactoring and other things.

Not sure how relevant this issue is today, but the warning seems to indicate exactly what it says: a pixel value is used uninitialized. The tests seems to have been reorganized though so it's not easy to track now.


Asking for extra results

Thank you for your great work!
I feel that the online training procedure is quite independent to the loss L_Epr. Have you tried to combine the online training procedure with other losses?
If it is convenient for you, can you provide some results on those combinations?
And also I cannot find the supplementary file anywhere, can you release it?

Thanks for reading!
You're right that the online label estimation framework could be combined with different losses, and I agree that it would be interesting to try some different approaches. Due to other commitments, I probably won't be able to do too many of those experiments myself in the near future.
Regarding the supplementary material, I'm still finalizing a thing or two - sorry for the delay!

Hi @elijahcole how about the supplementary material? Thank you :-)


apiVersion information is out of date

The enumeration in the field list shows an old 2018 date, while the example shows 2021-07-01.  Please provide a listing of valid apiVersion values.
Also, 2021-07-01 doesn't appear to work ( and neither does '2021-07-01' nor "2021-07-01" )
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d76dd9b1-b82f-0f68-0f82-dac7275885a6
Version Independent ID: 13450a08-6624-cd01-fa9d-c86e0da5a2d0
Content: YAML reference for container group - Azure Container Instances
Content Source: articles/container-instances/container-instances-reference-yaml.md
Service: container-instances
GitHub Login: @macolso
Microsoft Alias: macolso

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Hi @Foozinator. Thanks for the feedback! I've updated the YAML reference to include all valid values for the apiVersion enum. The changes should go live tomorrow. #please-close


psst: unstable-2024-01-28 -> unstable-2024-02-25

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for psst is: Fast and multi-platform Spotify client with native GUI
meta.homepage for psst is: https://github.com/jpochyla/psst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-03 in filename of file in /nix/store/jp6zr2nkg4zayxfk38p20ksgm185grbn-psst-unstable-2024-02-03

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
psst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jp6zr2nkg4zayxfk38p20ksgm185grbn-psst-unstable-2024-02-03 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A psst https://github.com/r-ryantm/nixpkgs/archive/ae4c71b6eddf232bc687d1496d7d502b7e73da43.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ae4c71b6eddf232bc687d1496d7d502b7e73da43#psst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jp6zr2nkg4zayxfk38p20ksgm185grbn-psst-unstable-2024-02-03
ls -la /nix/store/jp6zr2nkg4zayxfk38p20ksgm185grbn-psst-unstable-2024-02-03/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

psst

Maintainer pings
cc @vbrandl @peterhoeg for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for psst is: Fast and multi-platform Spotify client with native GUI
meta.homepage for psst is: https://github.com/jpochyla/psst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-10 in filename of file in /nix/store/0yc6yvk8hwxaz6jy50k4d94g516gqs28-psst-unstable-2024-02-10

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
psst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0yc6yvk8hwxaz6jy50k4d94g516gqs28-psst-unstable-2024-02-10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A psst https://github.com/r-ryantm/nixpkgs/archive/f35250ab2484081fab8ebde77ebc911202645b27.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f35250ab2484081fab8ebde77ebc911202645b27#psst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0yc6yvk8hwxaz6jy50k4d94g516gqs28-psst-unstable-2024-02-10
ls -la /nix/store/0yc6yvk8hwxaz6jy50k4d94g516gqs28-psst-unstable-2024-02-10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

psst

Maintainer pings
cc @vbrandl @peterhoeg for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for psst is: Fast and multi-platform Spotify client with native GUI
meta.homepage for psst is: https://github.com/jpochyla/psst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-17 in filename of file in /nix/store/v3q15330a4scjvfd0y275i5m5xp3zhd1-psst-unstable-2024-02-17

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
psst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v3q15330a4scjvfd0y275i5m5xp3zhd1-psst-unstable-2024-02-17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A psst https://github.com/r-ryantm/nixpkgs/archive/aa01b79dcb775081f0d43e378545a4276674f98d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/aa01b79dcb775081f0d43e378545a4276674f98d#psst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v3q15330a4scjvfd0y275i5m5xp3zhd1-psst-unstable-2024-02-17
ls -la /nix/store/v3q15330a4scjvfd0y275i5m5xp3zhd1-psst-unstable-2024-02-17/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

psst

Maintainer pings
cc @vbrandl @peterhoeg for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for psst is: Fast and multi-platform Spotify client with native GUI
meta.homepage for psst is: https://github.com/jpochyla/psst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-21 in filename of file in /nix/store/imyl7vlzi86444dnd6kgbn44w499wybz-psst-unstable-2024-02-21

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
psst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/imyl7vlzi86444dnd6kgbn44w499wybz-psst-unstable-2024-02-21 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A psst https://github.com/r-ryantm/nixpkgs/archive/d7100dff4692e51159125c90b74a96dbf3d472d4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d7100dff4692e51159125c90b74a96dbf3d472d4#psst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/imyl7vlzi86444dnd6kgbn44w499wybz-psst-unstable-2024-02-21
ls -la /nix/store/imyl7vlzi86444dnd6kgbn44w499wybz-psst-unstable-2024-02-21/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

psst

Maintainer pings
cc @vbrandl @peterhoeg for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for psst is: Fast and multi-platform Spotify client with native GUI
meta.homepage for psst is: https://github.com/jpochyla/psst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-25 in filename of file in /nix/store/mypsklzbda141h56dp5cnw5agidx0r2g-psst-unstable-2024-02-25

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
psst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mypsklzbda141h56dp5cnw5agidx0r2g-psst-unstable-2024-02-25 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A psst https://github.com/r-ryantm/nixpkgs/archive/b111587067d52a360685419d671e78171c3dcacf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b111587067d52a360685419d671e78171c3dcacf#psst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mypsklzbda141h56dp5cnw5agidx0r2g-psst-unstable-2024-02-25
ls -la /nix/store/mypsklzbda141h56dp5cnw5agidx0r2g-psst-unstable-2024-02-25/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

psst

Maintainer pings
cc @vbrandl @peterhoeg for testing.

Already on master.


Cheat

need

Hi @Troreen, thanks! It seems like there is a problem with the CLA. Can you follow the instructions above and let me know once you have signed the CLA?

Can I double-check that you intended to submit this as a pull request to add to OpenSpiel?

Can you take a look at the instructions for adding a new game, here: https://github.com/deepmind/open_spiel/blob/master/docs/developer_guide.md#adding-a-game
Specifically, can you do steps 5 (add the game to pyspiel_test) and 9 (add a playthrough)?
You also need to add cheat_test to the games/CMakeFiles.txt

It was a mistake i did not intend to create a pull request.
On Fri, Sep 9, 2022, 23:03 lanctot @.***> wrote:

Can I double-check that you intended to submit this as a pull request to
add to OpenSpiel?
—
Reply to this email directly, view it on GitHub
https://github.com/deepmind/open_spiel/pull/930#issuecomment-1242469149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF27KK4Q6QXPZF3462Q5TPTV5OQ2XANCNFSM6AAAAAAQI5BUYU
.
You are receiving this because you were mentioned.Message ID:
@.***>

It was a mistake i did not intend to create a pull request.

No problem! I will close this for now then, but it would be a good game to contribute to the library if you are ever interested in doing that :)


Add filename pattern to cli

Motivation and context

Add ability to create task with filename_pattern by cli.
How has this been tested?

Manually
cvat-cli --server-port 3000 create "task with filtered cloud storage data" --labels '[{"name": "car"}]' --use_cache --cloud_storage_id 1 --filename_pattern "test_images/*.jpeg" share manifest.jsonl

Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes
- [ ] I have linked related issues (read github docs)
- [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@Marishka17 , need to add a line into CHANGELOG.md

@zhiltsov-max , could you please look?


More PD 500 info.

Travis tests have failed
Hey @bakert,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
TravisBuddy Request Identifier: b10f1290-eb1f-11ea-95c6-05b7905ca42d


chore(docs): update Notification Manager Service documentation

chore(docs): update Notification Manager Service documentation

We fixed the build issue, the doc is ready to merge.

@pmarchini @fredmaggiowski can we merge it?


aws_cloudfront_distribution - forwarded_values validation needs to account for the cache_policy_id value

Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[x] IDE version (IntelliJ IDEA 2021.1.3 (Ultimate Edition) Build #IU-211.7628.21, built on June 30, 2021)
[x] intellij-hcl plugin version (0.7.10)
[x] Terraform version (0.13.5)

Terraform Configuration Files
resource "aws_cloudfront_distribution" "example" {
  ...
  default_cache_behavior {
    allowed_methods  = ["GET","HEAD"]
    cached_methods   = ["GET", "HEAD"]
    target_origin_id = "anS3Bucket"
    cache_policy_id = data.aws_cloudfront_cache_policy.CachingOptimized.id

    viewer_protocol_policy = "redirect-to-https"
  }
  ...
}

Exception
Missing required properties: forwarded_values
Expected Behavior
when cache_policy_id field is configured under the default_cache_behavior, the forwarded_values block is not required by AWS
Actual Behavior
a warning is shown on the IDE
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

add cache_policy_id without the forwarded_values block

Fixed in 0.7.12


No contributing.md file

I noticed that there is not any contributing. md and link added in the README.md also shows an error.

So please assign me this issue and add label gssoc-extd and hactoberfest

@BamaCharanChhandogi  please assign me this issue

@MadhurimaNayak  I created the pull request for this: #47

@MadhurimaNayak  I created the pull request for this: #47


Unit testing for TypeScript/JavaScript code

Tests are supposed to written in TypeScript, so  webpack was configured to work with TypeScript as well.

Coverage remained the same at 64.759% when pulling 1492a44006b3d2b42a43d348e39959dccdd7e9e5 on OlehKSS:olehkss/unittests into 8603a47aff4531df69ace44efdcf6b85d6e51e51 on maartenbreddels:master.

Just letting you know I'm on vacation. Will take a look as soon as I can!

Sorry for disturbing you:)

Sorry for not getting back to you sooner! Doing my best, but it is a busy
period
(from mobile phone)
On Fri, 22 Jun 2018, 23:20 Oleh Kozynets<EMAIL_ADDRESS>wrote:

Sorry for disturbing you:)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/maartenbreddels/ipyvolume/pull/146#issuecomment-399585280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABryPQkcArbyKknE-FZo3rzeFDSfmRerks5t_V-KgaJpZM4UwKAF
.

Great work, we should be adding some unittests, especially the transitions are complex, wouldn't hurt to have tests for those so refactoring will be easier


one more slash was added on S3 prefix when using iceberg.tables.auto-create-enabled option

When I using the connector with iceberg.tables.auto-create-enabled option, one more slash was added on S3 prefix like below
if) default db LOCATION of temp_beta database : s3://test_bucket/temp_beta

expected S3 path: s3://test_bucket/temp_beta/test_table/
auto-generated S3 path:  s3://test_bucket/temp_beta//test_table/

I think it's not intended result unlike https://github.com/tabular-io/iceberg-kafka-connect/issues/118

By the way, is iceberg.tables.evolve-schema-enabled option working well..?
If so, how about updating Tabular medium blog for this connector..?
(on Future enhancements phrase, it say there is no table schema evolution feature as yet)
https://tabular.medium.com/intro-to-the-iceberg-kafka-connect-sink-f0f86eae2937

I believe this is an issue with Iceberg itself, you may want to raise an issue there. Schema evolution is working and we are currently working on a series of follow-up blog posts to detail some of the new features, so stay tuned.

Thanks for pointing out the outdated docs, I'll update the future enhancements section.

This PR updates the design doc: https://github.com/tabular-io/iceberg-kafka-connect/pull/131

Thank you @bryanck  !

By the way, there will be a PR in the Iceberg repo shortly, to fix the extra slash issue when using the Glue catalog, in case you want to follow along. Thanks for reporting that.


Improved ecma_utf8_string_to_number function

This patch extends the infinity and zero parsing of the convertible number by comparing it to Number.MAX_VALUE or Number.MIN_VALUE which makes it even faster than before.
In addition added a test case for it based on #1973.
JerryScript-DCO-1.0-Signed-off-by: Robert Fancsik<EMAIL_ADDRESS>

@akosthekiss I've updated this PR according to your remarks.

@akosthekiss I've updated this PR, please review.

@akosthekiss I've updated this PR, please review.

@akosthekiss I've updated this PR with an other solution which not uses any FP arithmetic.

I've missclicked and I closed this PR by accident. Sorry, let's continue.

@akosthekiss This patch is reworked and rebased.

First of all as we previously discussed, there was a huge memory gain problem in crypto-aes.js test. I've used valgrind to see where this memory gain came from and the results are really strange for me.
Without this patch:

crypto-aes.js: Peak: 32.8Kb (33659b) Total: 1.4Mb (1538831b)
ecma_new_ecma_string_from_utf8 () : Peak: 5.6Kb (5755b)  Total: 37.8Kb (38757b)

With this patch:

crypto-aes.js: Peak: 39.2Kb (40222b)  Total: 1.4Mb (1544890b)
ecma_new_ecma_string_from_utf8 () : Peak: 5.6Kb (5775b)  Total: 38.6Kb (39613b)

The patch modifies only ecma_new_ecma_string_from_utf8 () and the numbers doesn't show big
different in it. I'm not sure but maybe the GC's work causes this gain.
Secondly, let's talk about the runtime. In overall this patch increased the runtime about 0.3%. That seems acceptable for me because we always calculate e_check and compare it most of the two times to pre-defined values if the convertible number has exponent part. In addition, I've used callgrind to check how much the the execution spend in the new code part, and most of the time it doesn't reaches this part at all.
What do you think these @akosthekiss ?

@rerobika Don't bother with crypto-aes; according to my experiences, it is notoriously unstable memory consumption wise (haven't been able to track down the reason, yet). But what are those results reported for "ecma_new_ecma_string_from_utf8" (Peak and Total)? Have you measured memory consumption for that single function only? (How?) As for running time, I'm still interested in the results on the originally reported test case (hang.js: 777E7777777777-----00,');, if I'm not mistaken), before and after the patch. (Before should be 1min+, but what is the number for after?)

Memory
I've used valgrind-freya's output to get these results. The full log is available in:
Without patch: https://gist.github.com/rerobika/852c9d4a92cf3d9a9eb46568385c8665
With patch: https://gist.github.com/rerobika/405d727ae8cef2ab091ea070c6cf729f
For measure I've used the latest jerry master and build command was: tools/build.py --debug --valgrind-freya ON
Runtime
The originally reported test case without this patch:

real	0m15.712s
user	0m15.704s
sys	0m0.004s

The originally reported test case with this patch:

real	0m0.001s
user	0m0.000s
sys	0m0.000s

For measure I've used the latest jerry master and build command was: tools/build.py

@LaszloLango Do you have any more suggestions?


Add RPC and Blockexplorer endpoints for TX-Builder

What it solves
Resolves #230
How this PR fixes it
Add RPC and Blockexplorer configuration for Avalanche chain
How to test it
Load the TX-Builder in Avalanche chain Safe. Check that normal operation is possible

All good from my end, was able to create and execute transactions via tx builder on avalanche network ;)


gurl: update googleurl tar

Signed-off-by: Dan Zhang<EMAIL_ADDRESS>Update to commit 6dafefa72cba2ab2ba4922d17a30618e9617c7cf which avoids having both build/ and BUILD under root directory.
Risk Level: low, no behavior change
Testing: no need to test
Fixes #11671

/assign @htuch

/azp run envoy-presubmit


build(deps): bump docker/bake-action from 2 to 4

carry and closes #4233
This handles provenance for built artifacts and disable provenance when generating docs.
See https://github.com/distribution/distribution/actions/runs/7501643046/job/20422754661?pr=4253#step:9:40

LGTM, but can u squash? PTAL @thaJeztah

You mean squashing dependabot commit? I think we should keep it as this is just carried over.

Nope, just your two commits into a single one


Documentation organization

Need to think how to organize documentation and generate documentation site

Mkdocs does the job...you can take example here:
Config:
https://github.com/tiangolo/fastapi/blob/master/docs/en/mkdocs.yml
Example:
https://fastapi.tiangolo.com/

Mkdocs does the job...you can take example here:
Config:
https://github.com/tiangolo/fastapi/blob/master/docs/en/mkdocs.yml
Example: https://fastapi.tiangolo.com/

@theArtechnology Thank you for the idea, will look at it!


Link to the SS manual in README.md is broken

As of July 7th, 2023 in the README.md file under "How can I learn how to use Stock Synthesis?" the link to 'Stock Synthesis user manual' is broken.

Thanks @John-R-Wallace-NOAA, we'll get it fixed.
@e-gugliotti-NOAA, the page that redirects from that old link to the working one seems to have gotten removed in this commit: https://github.com/nmfs-stock-synthesis/doc/commit/84647d7d3e91cfddae74b3acbfba69636c267899. Was that intended or by accident?

That was a mistake on my part thinking that it was the same as the duplicate user manual html that used to be written to docs. I've added it back in. @iantaylor-NOAA Can you check that the redirect works now?

@e-gugliotti-NOAA
status of this?

This has been rectified.


Fix TaskProcessorFactory#getTaskProcessor get common processor is not thread safe

Purpose of the pull request
Close #10470, maybe we need to remove the variable in processor, then we don't need to create it in each task, or we can use threadlocal to store the variable.
Brief change log

Don't cache the CommonTaskProcessor in TaskProcessorFactory
Add some log

Verify this pull request
Trigger multiple process instance, then see all process instance can run successful.

Codecov Report

Merging #10479 (4015a2c) into dev (f512e3c) will decrease coverage by 0.04%.
The diff coverage is 21.12%.

@@             Coverage Diff              @@
##                dev   #10479      +/-   ##
============================================
- Coverage     40.90%   40.85%   -0.05%
+ Complexity     4853     4843      -10
============================================
  Files           883      885       +2
  Lines         35972    35974       +2
  Branches       3991     3993       +2
============================================
- Hits          14715    14698      -17
- Misses        19802    19820      +18
- Partials       1455     1456       +1

Impacted Files
Coverage Δ

...pache/dolphinscheduler/common/utils/FileUtils.java
52.94% <0.00%> (-3.31%)
:arrow_down:

...e/dolphinscheduler/dao/entity/ProcessInstance.java
65.56% <0.00%> (-0.44%)
:arrow_down:

...ver/master/consumer/TaskPriorityQueueConsumer.java
0.00% <0.00%> (ø)

...ler/server/master/dispatch/ExecutorDispatcher.java
0.00% <ø> (ø)

...duler/server/master/processor/queue/TaskEvent.java
50.00% <0.00%> (-17.95%)
:arrow_down:

.../master/processor/queue/TaskExecuteThreadPool.java
2.17% <0.00%> (-0.10%)
:arrow_down:

.../server/master/runner/WorkflowExecuteRunnable.java
7.74% <0.00%> (-0.01%)
:arrow_down:

...erver/master/runner/WorkflowExecuteThreadPool.java
1.40% <ø> (ø)

...server/master/runner/task/CommonTaskProcessor.java
4.10% <0.00%> (ø)

...inscheduler/server/worker/config/WorkerConfig.java
76.47% <ø> (ø)

... and 18 more

Continue to review full report at Codecov.

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


<ARKit/ARKit.h> file not found.

How can I fix this?
I create a new React Native project and install react-native-arkit and link.
When build using xcode - > <ARKit/ARKit.h> file not found.

Try updating to the latest BETA release for iOS and xcode

oke. thanks bro!


feat: update recognizer UI in form

Description
update recognizer UI in form.
Task Item
close #7935
Screenshots

Coverage increased (+0.02%) to 50.377% when pulling 50183ca41d48b57d22d8554fd4a5374b1dbc1a30 on wenyluo/newUI into 56801686c41a21630be2955a54b992dd59d8f91a on main.

@VanyLaw , Can you adjust the UX to make sure we follow Vivek's design, for example:

remove the "recognizer" in titles.
add "." at the end of the sentence.
the size of the modal.

@VanyLaw , Can you adjust the UX to make sure we follow Vivek's design, for example:

remove the "recognizer" in titles.
add "." at the end of the sentence.
the size of the modal.

updated.

@hatpick, could you help take another look at this PR.


Master

fixing time and adding isinstance compliancy

aargh, sooorry I screwed the formatting of transcrypt/development/automated_tests/transcrypt/classes/init.py :-(((
thought isinstance is not worth an own test, so added into yours but the tab -> spaces -> edit -> tabs workflow did fail somehow. Btw: You don't happen to have a vim config for your tab indented sources ?
I was replacing all tabs with four spaces then back but it failed.
PS: daylight saving should work but its crazy. ... (quote pydoc: DST is Daylight Saving Time, an adjustment of the timezone by (usually) one hour during part of the year. DST rules are magic (determined by local law) and can change from year to year. )

ok, think I fixed it. It was not an editor problem but a git problem, git ammend did not do what I thought ( as a mercurial guy git for me is still pita )

ok, conflict now with your builtins commit. Let me know if you want seperate PRs or you merge manually.

Which files did you modify / create?

hi, created none, changed:
transcrypt/development/automated_tests/transcrypt/classes/init.py
transcrypt/development/automated_tests/time/testlet0.py
transcrypt/modules/time/init.py
transcrypt/development/automated_tests/hello/README.md
transcrypt/run_transcrypt (chmod)
and last but not least:
transcrypt/modules/org/transcrypt/javascript/builtin.mod.js

Still behind your computer...
Glad I'm not the only one...

the interruption free part of the day just started ;-)
So I send you seperated PRs and we forget about this one, or can you handle?

Connected google analytics to the site today.
Also uploaded a very simple movie of the mondrian turtle graphics to youtube.
And added some SEO info to the site.
For Python + Javascript on page one.
For Python + Browser on page three.

and... I am INFRONT of my computer. GRRRRR ;-)

If it's not too much work, I'd like to try separate PR's.
Will handle them tomorrow, however, not enough concentration anymore, will make mistakes now.
Alright, so you're actually facing your screen then.
I use a mirror...

ok, I create 4 PRs

regarding youtube: This one really hit me yesterday, thats what the ruby guys built on top of their Transcypt - with which they have massive trouble with the native js access, since the syntax is so different, thats why yours does have actually so much more potential!
https://www.youtube.com/watch?v=KbFtIt7-ge8

Nice video. He doesn't hesitate while talking and operating his computer. Rather hard to do (from experience). By the way, have you seen the conversation at issue #150? I'd like your (and dabo's) opinion on that, since the 'in' operator was made suitable for objects on your request. Should it stay like it is to cover your use cases, or being changed as proposed in #150? Original motivatioin was I believe that it's handy to have Python's 'in' behave like JS 'in' on (JS) objects, so also iterate through attribs that were inherited from prototype. What's your preference on this?

argh it does not work, when I sent one PR and then, after that send another this GitHub gui just appends the second to the first PR.
I continue now and manually merge the builtins stuff from me , so that you don't have to merge. I have a lot of tests so I'm positive the isinstance improvements you can accept as is and merge all automatically. Or maybe with your permissions you can merge also the single commits of this new PR... sorry for that, have no Idea how I could create 4 isolated PRs w/o you accepting them intermediatelly.

I'll look into 150

If you have done a manual merge, there will be no conflicts anymore, right?
So even if it's one PR, I could merge automatically, and then just do a QC/review diff?
In that case one PR is fine.
I will suspend any commits on builtins for now to keep the target steady.


convert winevent ingester over the the structured logging format

winevent needs a logger and we need to get rid of the infoout, errorout nonsense.

done and done


Support CTE/JOIN usage for PIVOT operator (PG15)

Description
This commit fixed an issue that CTE and JOIN cannot be used with pivot operator.
We added 1 field (Node *context) in FuncExpr Struct to store pivot additional information. FuncExpr will carry the pivot information to ExecMakeTableFunctionResult. In this function, we pass the pivot information into two newly added FunctionCallInfo that we can retrieve at bbf_pivot function.
Issues Resolved
Task: BABEL-4713, BABEL-4714, BABEL-4795
Test Scenarios Covered
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

41 of 44 (93.18%)  changed or added relevant lines in 3 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 72.964%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/hooks.c
28
29
96.55%

contrib/babelfishpg_tsql/runtime/functions.c
12
14
85.71%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tsql/runtime/functions.c
1
82.86%

contrib/babelfishpg_tsql/src/pl_exec.c
2
44.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
41251

Relevant Lines:
56536

💛  - Coveralls


fix filterManager destroy

Just looked inside, saw a bug. Lets test it!
#4418 #4420

ok, fixed.

Yeah, we should make a unit test for this. Welcome a PR for that!

@bigtimebuddy #4431


HIJACK_LOGOUT_REDIRECT_URL not working

django-hijack v3.0.0
django-hijack-admin v2.1.10
I'm using the Django admin integration app so I can hijack users from the admin interface.
When I release a user, Django reloads the last hijacked page instead of loading what I set in my settings:
HIJACK_LOGOUT_REDIRECT_URL = '/django-admin/auth/user/'

In fact, if I don't set HIJACK_LOGOUT_REDIRECT_URL, the default behavior (loading LOGIN_REDIRECT_URL) doesn't work neither.

django-hijack v3.0 is completely rewritten and does not require django-hijack-admin. The administrator interface is now included in django-hijack.
Please follow our docs for v3 here https://github.com/django-hijack/django-hijack#docs
Also we use LOGOUT_REDIRECT_URL to redirect on logout https://github.com/django-hijack/django-hijack/blob/ab80da9e108316f1fef98e593fc4cbea84a30c63/docs/customization.md#notification-layout

django-hijack v3.0 is completely rewritten and does not require django-hijack-admin. The administrator interface is now included in django-hijack.

OK, thanks, I will remove the now obsolete django-hijack-admin from my project.

Also we use LOGOUT_REDIRECT_URL to redirect on logout https://github.com/django-hijack/django-hijack/blob/ab80da9e108316f1fef98e593fc4cbea84a30c63/docs/customization.md#notification-layout

I guess the notification template is an "example to be customised", because it seems to default to the last requested page URL instead of LOGIN_REDIRECT_URL:
<input type="hidden" name="next" value="{{ request.path }}">

and that's the reason it is ignoring my LOGIN_REDIRECT_URL.
Thanks for your answer and an awesome job!

Thanks! I'll look into the PR and this issue over the weekend.

I double-checked the documentation. It correctly reflects the current implementation.


Applied fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Coverage remained the same at 97.0% when pulling 59e1a4a3a41a347f15ba653e8a3941fda8e38325 on analysis-zGG3eA into 917ef427eb189eb3d8bd7cc0f9387e7616f29400 on develop.


Windows build failed.

C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\dxgi.h(1,1): error C2220: the following warning is treated as an error [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\audiotags\audiotags_plugin.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\dxgi.h(1,1): warning C4821: Unable to determine Unicode encoding type, please save the file with signature (BOM) [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\audiotags\audiotags_plugin.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\winapifamily.h(1,1): warning C4821: Unable to determine Unicode encoding type, please save the file with signature (BOM) [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\audiotags\audiotags_plugin.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\sdkddkver.h(1,1): warning C4821: Unable to determine Unicode encoding type, please save the file with signature (BOM) [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\audiotags\audiotags_plugin.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\um\windows.h(32,28): warning C4067: unexpected tokens following preprocessor directive - expected a newline [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\audiotags\audiotags_plugin.vcxproj]
C:\Users\sani\Documents\GitHub\simple_music_player\windows\flutter\ephemeral\flutter_windows.h(121,5): error C2061: syntax error: identifier 'HWND'
...
...
C:\Users\sani\Documents\GitHub\simple_music_player\windows\flutter\ephemeral\cpp_client_wrapper\include\flutter/plugin_registrar_windows.h(96,9): error C2451: a conditional expression of type 'std::optional' is not valid [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\simple_audio\simple_audio_plugin.vcxproj]
C:\Users\sani\Documents\GitHub\simple_music_player\windows\flutter\ephemeral\cpp_client_wrapper\include\flutter/plugin_registrar_windows.h(97,8): error C2065: 'result': undeclared identifier [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\plugins\simple_audio\simple_audio_plugin.vcxproj]
Building Windows application...
Exception: Build process failed.

I will take a look at this when I have the time.

Hello.
I am able to build and run the example app with no errors. Maybe try flutter clean?

@erikas-taroza not sure if its this packages fault but got this error after upgrading to audoitags 1.1.1.
lib/main.dart(16,7): error GC9768DF9: Undefined name 'NotificationActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/main.dart(17,7): error GC9768DF9: Undefined name 'NotificationActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/main.dart(14,5): error GC6690633: No named parameter with the name 'androidCompactPlaybackActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/utils/utils.dart(34,30): error G75B77105: Member not found: 'Icon'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/utils/utils.dart(35,24): error G75B77105: Member not found: 'Png'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): error MSB8066: Custom build for 'C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\CMakeFiles\346ec51341759c40164bbd4237fd13ff\flutter_windows.dll.rule;C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\CMakeFiles\b16c681d098d89377f86e7eb3427e6e6\flutter_assemble.rule' exited with code 1. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
Building Windows application...
Exception: Build process failed.

@erikas-taroza not sure if its this packages fault but got this error after upgrading to audoitags 1.1.1 (previously using 1.1.0).
lib/main.dart(16,7): error GC9768DF9: Undefined name 'NotificationActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/main.dart(17,7): error GC9768DF9: Undefined name 'NotificationActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/main.dart(14,5): error GC6690633: No named parameter with the name 'androidCompactPlaybackActions'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/utils/utils.dart(34,30): error G75B77105: Member not found: 'Icon'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
lib/utils/utils.dart(35,24): error G75B77105: Member not found: 'Png'. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): error MSB8066: Custom build for 'C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\CMakeFiles\346ec51341759c40164bbd4237fd13ff\flutter_windows.dll.rule;C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\CMakeFiles\b16c681d098d89377f86e7eb3427e6e6\flutter_assemble.rule' exited with code 1. [C:\Users\sani\Documents\GitHub\simple_music_player\build\windows\flutter\flutter_assemble.vcxproj]
Building Windows application...
Exception: Build process failed.

Please read the changelog. Breaking changes were added.

@erikas-taroza please follow semver rule 0.[breaking change].[bug fix]
Sorry, it was my fault to not check my code beforehand.

@erikas-taroza please follow semver rule 0.[breaking change].[bug fix]

Ah sorry. I will keep in mind :)

@erikas-taroza didn't really solve the problem, I'm trying it in brand-new instance in a vm. do I have to do any setup beforehand?

@erikas-taroza didn't really solve the problem, I'm trying it in brand-new instance in a vm. do I have to do any setup beforehand?

Should work OOTB. Maybe you need to update the Windows SDK via Visual Studio?


Names of people in hangouts overlap the dots in top right

Hangouts with a lot of participants causes the names to run into the three vertical dots in the top right.
Running v1.4.1 on macOS 10.12.1

if you can, please, attach a screenshot

Here it is, although i've blurred out the names.


Nativescript: crash at launch of iOS Application in device

After update Xcode to 10 version and iOS 12 in device, i have a problem with ios app generate by Nativescript:

with the emulator, the app run correctly;
with the device, the build is ok, but the app crash without error when the app is opening at splash screen. The same if i use Xcode;
when i archive the app with Xcode, upload to TestFlight correctly.

The trid to change certificates, but I have the same problem. I use 4.2.3 version of Nativescript (i tried 5.0.0 -next-).

Closing as duplicate to https://github.com/NativeScript/nativescript-cli/issues/4002


MatOfT dispose problem

Hi.
When we creat Mat<TElem, TInherit> fom anothe Mat and then dispose one - memory dealoceted two times:
1 - when disposing  Mat<TElem, TInherit> class
2 - when disposing sourceMat (when GC working)

you are right
here is the case:
        Mat newm = img;                   //work well
        newm.Release();
        img.Release();

        //Mat newm = img.Clone();             //work well
        //img.Release();
        //newm.Release();

        //Mat newm = new Mat(img);          //throw exception when return

        //Mat newm = new Mat(img.Clone());  //throw exception when return

        return;

It is anothe case
var sourceMat = new Mat(10, 20, MatType.CV_64FC1);
var doubleMat = new MatOfDouble(sourceMat);
sourceMat = null;
doubleMat.Dispose(); // after it when GC will working program broken

Thanks :+1: This is fixed by https://github.com/shimat/opencvsharp/pull/380/commits/fe3b036c40cbfe8d2df4aff9d2fe25cbd8a09e02


Add real numbers in Result.Vue

"Showing 15 out of 196 results" should not be static.

maybe do this from backend and sending it in the get route. To do it with sequilize and mongoose and fulfill the course requirement

sequelize.fn('COUNT',...


Remove incorrect validations

Hi!
As mentioned in #176 & #209, the validation done by foundation-datepicker is incorrect since there's no guarantee that the length of the format string will match the actual length of a date. Moreover, this validation has been biting us in combination with the https://github.com/sgruhier/foundation_rails_helper gem. If a submitted form has errors in the date field, this gem will generate form input with "foundation friendly errors". However, this piece of JS will actually remove part of them making them look weird.
Also, in my opinion, users wanting to perform client side validations should use foundation-abide which is more powerful anyways.
So because of all of the above reasons, I think we should remove these incorrect validations from the library.
Fixes #176 & #209.

I committed to package-lock.json file since it helps a bit with ensuring all contributors get the same environment, and it prevents source control untracked files from being generated while development. Let me know it you want that removed.

I moved the package-lock.json addition to a separate PR to make reviewing this easier.

@najlepsiwebdesigner Any news here? We'd prefer to not fork the library and have some valuable feedback from you :)

Hi! I'm sorry for late answer, I am currently finishing my PhD so I'm "little bit" busy. I plan to review all the changes proposed in PRs and issues during August. Thank you for understanding ;)

He @najlepsiwebdesigner, just a ping since it's september now. I hope you finished your PhD successfully and you're doing great! :)

Any news?


Create Hello Cody Vue file

Acceptance criteria:

[x] plugin installation
[x] create file to display quotes
[x] put accepted vue file inside plugin repository

Repo: https://github.com/elkmod/SwagHelloCody

I have created PR --> https://github.com/elkmod/SwagHelloCody/pull/4


then to than

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Good spot @eben-roux. Thanks for creating this PR. This ASCIIDOC is actually generated from a file (src/Tests/Tests/ClientConcepts/HighLevel/Inference/FieldInference.doc.cs) which is where this fix would need to be made. Once that's done, the docs can be re-generated. If you fancy it, would you mind making the change in that file? I can handle the re-gen once it's merged. Alternatively, I can port this and close this PR.

I'd be happy to make the change in the source file :)
I'll submit a new PR for that change.


Tplink MR200 (Archer AC 750) router , it is an LTE router

logged in, the page is basic settings status tab
pressed advanced settings , status tab
pressed advanced settings ,wireless tab , statistics
pressed logout
again logged in with password
pressed reboot
after reboot logged in again

You forgot to attach the captured data

Unfortunately, all request are encrypted and I cannot parse them without having this router
Would be great if you could add support for your router by creating PR with new class that extends https://github.com/AlexandrErohin/TP-Link-Archer-C6U/blob/main/tplinkrouterc6u/client.py#L16
To solve encryption I found this for your router https://github.com/0xf15h/tp_link_gdpr

Ok I'll try that and let you know.
Thanks 😊

@raviteja9494 Archer MR200 v5.3 support was added. It is also LTE router. Please new version of the integration

@AlexandrErohin   it is working, thankyou, thankyou very much 😊
I am still going through the base to understand how to add support to my router, but you did it .. thankyou very much 😊..
I'll try to understand and if possible I'll try to add the entities for LTE signal details also ..
Thanks 😊

@raviteja9494 could you me tell please what is the hardware version of your router?

@raviteja9494 Thank you!
P.S. Dont forget please to give a star to the repo :)


Monitoring design changes

Features that have this component/card after you activate/turn on the feature:
Monitoring Overview
Istio Overview
Longhorn Overview (still WIP)

note to self

as of right now I can't get istio to install

This is validated in master-head ec04f7878 with the latest UI
note that the panels for CRDs are removed in the new design https://github.com/rancher/dashboard/issues/1260


Delay ledger close when network stalled (RIPD-1628)

When a node is not advancing the fully validated ledger, this change will delay closing the next ledger as part of consensus to give more time for the node to reconnect with the network. This limits the number of intermediary ledgers the node generates while not in sync with enough of its peers.

Jenkins Build Summary
Built from this commit
Built at 20180518 - 13:54:49
Test Results

Build Type
Log
Result
Status

docs
logfile
1 cases, 0 failed, t: 2s
PASS :white_check_mark:

clang.debug.unity
logfile
1030 cases, 0 failed, t: 248s
PASS :white_check_mark:

coverage
logfile
1030 cases, 0 failed, t: 618s
PASS :white_check_mark:

clang.debug.unity, PARALLEL_TESTS=false
logfile
1030 cases, 0 failed, t: 484s
PASS :white_check_mark:

gcc.debug.unity
logfile
1030 cases, 0 failed, t: 237s
PASS :white_check_mark:

gcc.debug.nounity
logfile
1028 cases, 0 failed, t: 104s
PASS :white_check_mark:

clang.debug.nounity
logfile
1028 cases, 0 failed, t: 654s
PASS :white_check_mark:

msvc.debug
logfile
1026 cases, 0 failed, t: 565s
PASS :white_check_mark:

clang.release.unity
logfile
1029 cases, 0 failed, t: 332s
PASS :white_check_mark:

gcc.release.unity
logfile
1029 cases, 0 failed, t: 347s
PASS :white_check_mark:

gcc.debug.unity -Dstatic=true
logfile
1030 cases, 0 failed, t: 239s
PASS :white_check_mark:

msvc.debug, PROJECT_NAME=rippled_classic
logfile
1026 cases, 0 failed, t: 1243s
PASS :white_check_mark:

msvc.release
logfile
1025 cases, 0 failed, t: 513s
PASS :white_check_mark:

Codecov Report

Merging #2548 into develop will increase coverage by <.01%.
The diff coverage is 76.08%.

@@             Coverage Diff             @@
##           develop    #2548      +/-   ##
===========================================
+ Coverage    70.78%   70.78%   +<.01%
===========================================
  Files          703      703
  Lines        54626    54655      +29
===========================================
+ Hits         38665    38690      +25
- Misses       15961    15965       +4

Impacted Files
Coverage Δ

src/ripple/app/consensus/RCLConsensus.h
80% <ø> (ø)
:arrow_up:

src/ripple/app/consensus/RCLConsensus.cpp
64.67% <0%> (-0.38%)
:arrow_down:

src/ripple/consensus/Consensus.h
89.67% <100%> (+0.66%)
:arrow_up:

src/ripple/consensus/ConsensusParms.h
100% <100%> (ø)
:arrow_up:

src/ripple/consensus/Consensus.cpp
73.52% <62.5%> (-9.17%)
:arrow_down:

src/ripple/app/misc/SHAMapStoreImp.cpp
75.29% <0%> (+0.23%)
:arrow_up:

src/ripple/protocol/impl/Serializer.cpp
70.5% <0%> (+0.33%)
:arrow_up:

src/ripple/basics/DecayingSample.h
86.11% <0%> (+8.33%)
:arrow_up:

Continue to review full report at Codecov.

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

Closing while I followup on @wilsonianb's good comments. I think using the preferred ledger sequence number over the last fully validated one would improve things. I'll open a new PR after working on that change.


Docs for workload identity / assume role for dedicated clusters

Fixes DOC-6414, DOC-6415

Added sections to the Cloud Storage Authentication page for workload identity/assume role steps for dedicated clusters. This has included reworking some of the structure to make use of the existing docs workflow for self-hosted clusters.
Made the procedural step based for clarity.
Corrected a duplicated screenshot.
Added a section that was missing (in error) from the current workload identity docs for GCP.
Reworked the note on implicit auth so that CockroachDB Cloud users are aware that it is possible with ASSUME_ROLE auth.

Preview
Amazon S3 https://deploy-preview-15963--cockroachdb-docs.netlify.app/docs/stable/cloud-storage-authentication.html#amazon-s3-workload-identity
Google Cloud Storage https://deploy-preview-15963--cockroachdb-docs.netlify.app/docs/stable/cloud-storage-authentication.html?filters=gcs#google-cloud-storage-workload-identity

@andf-crl requesting your docs review on this one! Thanks!

TFTRs!


Deprecate celer.datasets.fetch_libsvm in favor of libsvmdata package

Codecov Report

Merging #163 into master will increase coverage by 3.88%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #163      +/-   ##
==========================================
+ Coverage   80.47%   84.35%   +3.88%
==========================================
  Files          12       12
  Lines        1019      959      -60
  Branches      147      136      -11
==========================================
- Hits          820      809      -11
+ Misses        158      109      -49
  Partials       41       41

Impacted Files
Coverage Δ

celer/datasets/libsvm.py
50.00% <40.00%> (+28.78%)
:arrow_up:

celer/datasets/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[Tour of Beam] Learning content for "Splittable DoFn" module

#22529
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM, thanks

@AnandInguva done


Have a bot holiday

It would be great if the bots went on holiday for a while to reduce the pressure on people. Imagine going from being stuck in a noisy traffic jam with cars honking to an serene secluded beach that no one else knows about. That would be what a bot holiday is like.

Unfortunately I don't think this would be feasible, some of the bot actions require quick turnaround.
We have a triage owner rotation to try and reduce the load, spreading it across a few people. Your team is currently excluded, so you are not reaping the benefits of that yet.

I'm talking about the actions that don't need quick turn around. Those could easily be skipped for a while.


asyncio rawsocket clients crash on WELCOME message

Asyncio rawsocket clients crash when receiving a WELCOME message.
WARNING  root:rawsocket.py:87 Instantiate autobahn component
WARNING  root:rawsocket.py:92 Start component
WARNING  root:rawsocket.py:96 Wait for the compoenent to be connected
WARNING  autobahn.asyncio.component.Component:aio.py:162 trying transport 0 ("None") using connect delay 0
ERROR    autobahn.asyncio.wamp.Session:aio.py:162 Session.onUserError(): "While firing onWelcome"
Traceback (most recent call last):
  File "/.../txaio/aio.py", line 489, in done
    callback(res)
  File "/.../autobahn/wamp/protocol.py", line 605, in success
    transport=self._transport.transport_details,
AttributeError: 'WampRawSocketClientProtocol' object has no attribute 'transport_details'

Indeed compared to autobahn.twisted.rawsocket.WampRawSocketProtocol, the transport_details property is missing from autobahn.asyncio.rawsocket.PrefixProtocol and the framing type is not updated once the transport details are created.

fixed via https://github.com/crossbario/autobahn-python/pull/1593


Feat : Improving contact form UI

Improving contact form UI with latest styling design (keeping in mind the color scheme of website),
I would like to work on it, as part of gssoc'21

@WaderManasi Make sure you only make changes to the UI.

Sure @harshita2216


Added missing square bracket

Added a missing square bracket to the headers section in the request options page.

Thanks @j92