auto Rule reloading no longer works in development

In previous version (0.5.3), the auth rules config would be reloaded with each request in development mode allowing for tweaking of the rules file without restarting the server..  However with 0.5.5 this no longer happens.  It seems to be caused by commit fb37826 on lines 274/275 (self.initialize) (current master line 283).  Basically the "or in development" check was removed.   Is there a better way of implementing this now?  Or was this an accidental removal?
Ideally I would like it to ONLY reload the files in AUTH_DSL_FILES if they have changed instead of every request.

I did not intend to change the behavior here.  How would you want to improve the check whether a reload is necessary?  Through a file timestamp check?

A basic quick and dirty would be cache the newest timestamp of the files listed in AUTH_DSL_FILES.  I'm curious as to how rails 3.2 is implementing this functionality for the regular class loading.   I can play around with it some later today as I'll be working with Auth rules on a project I'm building.

Muwhahaha..   I convert you to a PULL request!.
Ok.. seriously now.  I've put a patch here to add in the lazy reloading of rule files in development mode.


child visible property toggles from true to false without re-render

In my test project: https://github.com/MichaelRando/preact-rollup-bootstrap
pressing button 'Test Dialog' displays a test dialog, by virtue of setting the state variable to true and the Dialog's visible property is set to said state. Clicking off or closing the dialog is expected to hide the dialog's view.
When using react & react-dom, the dialog appears and disappears as many times as the user could want, successfully.
When using preact & preact-compat, the dialog appears successfully, but closing / setting the visible state false has no effect. The Dialog component is not re-rendering as React compatibility would expect.
This is a super basic test; not sure why this is happening.

It is re-rendering, just it's not closing the dialog.  this seems to be an incompatibility with rc-dialog / css-transition-group.  I understand your frustration, but bear in mind that while the demo code might be basic, it's relying on a fairly large external library.  The complexity/intricacy is hidden.
I've been debugging so far and haven't found much, I'll post back here when I do.

Weird. I assumed it was vdom issue because I wasn't getting breakpoints (update/render) in the child upon parent state change. But I'm not surprised it's a tip of iceberg, otherwise nothing would work...

this seems to be an incompatibility with css animation, when modify animation-duration to 0s, the rc-dialog is not re-rendering.
https://github.com/ant-design/ant-design-mobile/blob/master/components/style/anim.less#L4

I use chrome-devtools debug it, the cause is the className of animation is removed before remove the div element, so may be this is not preact bug.

I found why remove element have delay, when remove setTimeout in the following code, the dialog is not re-rendering. @developit
// render-queue.js:10
(options.debounceRendering || setTimeout)(rerender);

Yes. We need to switch back to Promise.then for denouncing.

Yes. need to revert https://github.com/developit/preact/commit/78014124593997d749e50ea1291a3c18731f1fe4

https://github.com/developit/preact/commit/576dda310a8e31e524fa2ecc803d6d406597c41e


In VGT，how to generate a png image into a pkl format Grid image？？？

I would like to ask, in VGT, how to infer your own document images, that is, how to generate a png image into a pkl format Grid image

https://github.com/AlibabaResearch/AdvancedLiterateMachinery/issues/75

I also need to know  how to generate a png image into apkl format Grid.

I also need to know  how to generate a png image into apkl format Grid.

I read the Refer#75. there is a template for grid to generate a pkl file.is it correct？Is it mean i can make a ocr for image and populate the OCR results into this template to make pkl file
        dict_for_grid = {             'input_ids': [],             'bbox_subword_list': [],             'texts': [],             'bbox_texts_list': [],         }

The pr currently only handles creating grid from a machine readable pdf. For png most probably, you'd need to use a ocr to populate the fields in dict_for_grid


wall anchor is flakey in simulator

Half of the time it won't work for me. (beta 8)
Not to blame you @tracyhenry : P but I was curious if you had the same experience?
Best regards!

In my case I have never seen "Think difference" image. (beta 8 also)

same here. Running Version 15.0 beta 8 too. I can't produce the "think different" image nor the generated art unfortunately, I am developing on an m1 Macbook pro, base model. When running, I get the following console logs:

nw_socket_copy_info [C1:2] getsockopt TCP_INFO failed 102
nw_socket_copy_info getsockopt TCP_INFO failed 102
Class for component AccessibilityComponent already registered
Class for component ImageBasedLightComponent already registered
Component Shadow already registered
Component Shadow already registered
AddInstanceForFactory: No factory registered for id <CFUUID 0x60000026a800> F8BB1C28-BAE8-11D6-9C31-00039315CD46
HALC_ProxyObjectMap.cpp:153  HALC_ProxyObjectMap::_CopyObjectByObjectID: failed to create the local object
HALC_ShellDevice.cpp:2,609  HALC_ShellDevice::RebuildControlList: couldn't find the control object

this helped me! Hopefully, more environments will support surfaces in the future.


user name mention notifications happen when user name is mentioned without any qualifying prefix/suffix

Describe the bug
My Matrix user name is simply be, which is a common English word. Element triggers a notification anyone uses my user name, which is almost always not actually trying to send a message to me. This makes notifications from Matrix clients basically unusable. User name mentions should only trigger a notification with an appropriate prefix such as @ or a suffix such as :.
To Reproduce
Steps to reproduce the behavior:

Use a common word as a user name
Be annoyed by a bunch of irrelevant notifications

Expected behavior
I should only be notified by messages specifically directed at me.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Fedora 33
Browser: Firefox
Version: 84.0.2

Additional context
I reported this first on the Element Web tracker and they directed me here.

FYI, in Element, you can turn off notifications for "Messages containing my display name" and "Messages containing my username".  This will stop notifications when someone just writes "be", but will still notify you when someone writes your full Matrix ID.

@uhoreg I have tested this. Like you explained switchting it off disables all notifications including the "@" ones. This isn't an option for me because then I am missing "@" mentions.
In many highly acitve rooms I have disabled notifications except "mentions & keywords".

related: https://github.com/matrix-org/matrix-doc/issues/1549

I think being notified when a message contains "be" is expected behaviour if your username is "be" and you have "messages containing my username" enabled. The fact that you then aren't pinged by @mentions is covered by #1549.
Certainly this stuff is a total mess, and it pains me that we've not had the time to rework it.


Add Montfort College Rotslaar

School in Belgium, can be referred to as MCR
edit: extra info for easier verification:
Main website: https://www.montfort.be
We use Office365 for email addresses and only the admin can create them.

@MaxTechnics Pull request merged. Thank you!


Update auth, dynamodb, s3, sqs to 2.17.238

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.193 to 2.17.238.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #936.


feat(config): support regexes for commit triggers

Signed-off-by: Matej Focko<EMAIL_ADDRESS>TODO:

[ ] Write new tests or update the old ones to cover new functionality.
[ ] Update doc-strings where appropriate.
[ ] Update or write new documentation in packit/packit.dev.
[ ] ‹fill in›

Fixes
Related to
Merge before/after

RELEASE NOTES BEGIN
￼
RELEASE NOTES END

document this also in packit.dev please

@TomasTomecek I'm actually not sure if I want to document it before I test it in action :D

document this also in packit.dev please

@TomasTomecek I'm actually not sure if I want to document it before I test it in action :D

yes, absolutely! just pointing out that once we make sure it works, we should document it :)


Add plans to queue with an excel file

Can you add PR description describing the adding functionality and design considerations?


Delete LICENSE.md

MIT license is the best option for such project, at least for the original repository. I'm closing it for now.
PS: Just in case you wanted to make these changes in your own version, feel free to send this PR to your fork instead of original repo.


Implement UI changes for Exploring Objects fields

We need to consider carefully how the UI will display additional API endpoint data. This issue will track that discussion and development.

V3 will combine and simplify data and visualizations, negating this explicit implementation.


fix: add logo-clicking to tests

Description
Some e2e tests are still failing (LGPage and NotificationPage) because Cypress can't click on elements it thinks are covered. Moving the mouse around (by clicking something non-interactive) might fix this.
Task Item
#minor

Looks good. @beyackle can you fix conflicts?


Fix running actions on a user resource

Resolves #3062
What is being addressed
Fix the route for running actions on a user resource

/test-extended

/test-extended


chore(app): improve the app info page a bit

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 18 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 3.57%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/pages/App.jsx
0
18
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/pages/App.jsx
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.002%

Covered Lines:
514

Relevant Lines:
16257

💛  - Coveralls


Not rendering ticket numbers correctly

When entering another ticket number into a comment field of a ticket the ticket number is not rendering correctly and not turning into a link either.
An example is I type in DB-4 into a ticket and it renders as DBnull-4.

Has anyone else experienced this before?

Hi - sorry I haven't replied earlier.
To be honest it's not something I have tested. When I get a chance I will give it a go.
Gary

Thanks for the reply Gary. I know this is something that is annoying a few
of my users.  I don't know if it has to do with the config change we made to
allow numbers and only two characters for project keys.  Just to let you
know.

Jon

On Wed, Oct 19, 2011 at 4:42 PM, Gary Hodgson <
<EMAIL_ADDRESS>
Hi - sorry I haven't replied earlier.
To be honest it's not something I have tested. When I get a chance I will
give it a go.
Gary
--
Reply to this email directly or view it on GitHub:
https://github.com/garyhodgson/tinymce-renderer-plugin/issues/25#issuecomment-2462880

Hi,
I finally got around to testing this and sadly on my setup everything works as expected. I even changed the project key to be two alphanumeric characters.
Could you tell me what regular expression you use for your project key, and whether there is anything weid in the html generated by the editor (using the "html" button in the TinyMCE editor itself)
Cheers


Getting permission issue while running flutter app to real device

Steps to Reproduce

...Creating new app
...Trying to run in Read device

Logs
Exception: null. The flutter tool cannot access the file.
Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the current user.

Logs

[✓] Flutter (Channel stable, 1.22.6, on Linux, locale en_IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Android Studio (version 4.0)
[!] VS Code (version 1.52.1)
✗ Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[!] Connected device
! No devices available
! Doctor found issues in 2 categories.

@jayaVassar
can you provide your flutter doctor -v, your flutter run -v and a minimal reproducible code sample

Hi @iapicca
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you


merge: stage to master

:tada: This PR is included in version 0.62.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


added docker support

Codecov Report

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

@@           Coverage Diff           @@
##           master     #119   +/-   ##
=======================================
  Coverage   91.03%   91.03%
=======================================
  Files           1        1
  Lines         145      145
=======================================
  Hits          132      132
  Misses         13       13

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 8512c38...2d92126. Read the comment docs.


Support for proxies in requests

It would be nice to be able to configure proxies for the HTTP requests.
Using https://requests.readthedocs.io/en/latest/user/advanced/?highlight=proxies#proxies it could be introduced on the requests.session object https://github.com/dell/PyU4V/blob/master/PyU4V/rest_requests.py#L69

I've contributed a modification for the 9.2 branch since this is where my primary need comes from. Do you want the equivalent pull request for the 10.0 branch ? or on master ?

PR 155 adds this support on 10.0.18


Missing Information - Android App - SDK Privacy Report.csv

ADmob SDK
Platform: Android
Name (as on the CSV file): Android App - SDK Privacy Report.csv
On the official page https://developers.google.com/admob/android/play-data-disclosure of the admob documentation it is informed "The Google Mobile Ads SDK collects and shares the following data types automatically for advertising, analytics, and fraud prevention purposes ."
On the Google Play console form there is the option to select "collects or/and shares".
However in the spreadsheet "Android App - SDK Privacy Report.csv" there is only the answer for the option "Shared".
Could you explain better if it's a mistake or is it deliberate?
Thank´s

@123dma - If you look at column two, it is Data Types Collected. We additionally give information if it is shared, Purposes, Required/Optional etc. So basically all the data types mentioned against a SDK are collected.

@123dma - let me know if this solves the issue. Will close it accordingly.

Hi @vaibhavantil1 , thank you. Yes, you can close the issue. If all data is to be checked as "Collected" the form on the Google Play console should be more intuitive.

Yes. In fact we are reporting for only the data which is being collected by the SDK because then only it can be shared and have a purpose. Read this for more information by Google on definition of data collected:
Libraries and SDKs: This includes user data transmitted off device from your app by libraries and/or SDKs used in your app, irrespective of whether data is transmitted to you or a third party server.


Add an "airdrop" feature at start of Anvil network

Component
Anvil
Describe the feature you would like
anvil --accounts 10 --balance 10 --mnemonic-random --airdrop=[0x...., 0x....]

This would allow me to use my test wallet instead of creating new wallets every time. A genesis file similar to the one available in Cosmos will be great too. Wondering if there is something similar available.
Additional context
Since Anvil "knows" the private key at start of network, it can use one of the private keys to send the tokens to a mentioned address via Alloy or Ethers.

You can initialize anvil with a genesis.json file, see the general options: https://book.getfoundry.sh/reference/anvil/?highlight=genesis#general-options
for an example of a genesis.json file, see https://github.com/foundry-rs/foundry/blob/5f8579b3fefc5b3e3b76cecf827c7361866fbd36/crates/anvil/tests/it/genesis.rs#L12-L37 , you probably want to see the alloc section. This is geth's genesis.json format (see https://geth.ethereum.org/docs/fundamentals/private-network#ethash-example)

My bad, thank you!


Floating value literals without postfix should be parsed as decimal

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to  the what)
Related to #4024, #4071.
A literal like 0.06 is parsed as double in DataFusion. It causes some counter-intuitive result as 0.06 - 0.01 = 0.049999999, 0.06 + 0.01 = 0.069999999 in DataFusion. This result is correct, though. (If you ask Spark to treat them as double (i.e., 0.06f), you will get same result).
Such literals are parsed as decimal in Spark. I think for floating literals without postfix, we should parse them as decimal in DataFusion
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks @viirya I had forgotten about this ... this is the relevant code in sql/planner.rs, for reference
// Parse number in sql string, convert to Expr::Literal
fn parse_sql_number(n: &str) -> Result<Expr> {
    // parse first as i64
    n.parse::<i64>()
        .map(lit)
        // if parsing as i64 fails try f64
        .or_else(|_| n.parse::<f64>().map(lit))
        .map_err(|_| {
            DataFusionError::from(ParserError(format!(
                "Cannot parse {} as i64 or f64",
                n
            )))
        })
}

Yes, I played this a bit yesterday. With some tweak, I can make it parsed as decimal and get 0.06 - 0.01 = 0.05 correctly.

Here is the spec for SQL numeric literals:
<signed numeric literal> ::=
[ <sign> ] <unsigned numeric literal>

<unsigned numeric literal> ::=
<exact numeric literal>
| <approximate numeric literal>

<exact numeric literal> ::=
<unsigned integer> [ <period> [ <unsigned integer> ] ]
| <period> <unsigned integer>

<sign> ::=
<plus sign>
| <minus sign>

<approximate numeric literal> ::=
<mantissa> E <exponent>

<mantissa> ::=
<exact numeric literal>

<exponent> ::=
<signed integer>

<signed integer> ::=
[ <sign> ] <unsigned integer>

<unsigned integer> ::=
<digit>...


can dlib dnn tooling use half precision weights?

Greetings
I just bought an new PC with an RTX 2080 graphics card.
I tried to find out by googling if dlib can do dnn training and inference in half precision/fp16 mode, but could not find anything.
So I'd like to know if there are any plans to add half precision training and inference to dlib.

No plans at the moment.  Right now it's all in fp32.


I-JEPA layers

PR Type
Feature
Short Description
This PR introduces added two modules for the I-JEPA layers, specifically the attention.py and transformer_block.py modules.
Tests Added
N/A

@vahid0001 Reminder to run pre-commit run --all-files and fix the reported errors.

@vahid0001 Reminder to run pre-commit run --all-files and fix the reported errors.

Fixed!


Don't hardcode edgedriver version

Clear and concise description of the problem
Currently we hardcode edgedriver because of this bug: https://github.com/webdriverio-community/node-edgedriver/issues/239
Suggested solution
Don't hardcode it after the issue is resolved
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@sheremet-va I started working on https://github.com/webdriverio-community/node-edgedriver/issues/239


added to the code

made two dice roller and also an option for getting the sum of two outputs of the dice rollers .

Good Job 🚀 🌋 👍 keep it up


vpcagent: fend off non-onecloud-vpc guest nics

这个 PR 实现什么功能/修复什么问题:
vpcagent: fend off non-onecloud-vpc guest nics

是否需要 backport 到之前的 release 分支:

release/3.2

/area vpcagent
/cc @swordqiu @zexi @wanyaoqi

Codecov Report

Merging #6022 into master will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6022   +/-   ##
=======================================
  Coverage    7.02%    7.02%
=======================================
  Files         644      644
  Lines      110405   110405
=======================================
+ Hits         7754     7756    +2
+ Misses     102051   102050    -1
+ Partials      600      599    -1

Flag
Coverage Δ

#aFlag
7.02% <ø> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/appsrv/response.go
70.58% <0.00%> (+2.94%)
: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 74eef22...6f2178e. Read the comment docs.

/hold 一起解决一起合


Provide a way to preload color emoji on web

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
On web, we can add useColorEmoji: true to use Noto Color emoji.
But before it gets loaded, all emojis are displayed as a block with a question mark in it.
I tried something like this in my loading screen before rendering any emojis:
await GoogleFonts.pendingFonts([
    GoogleFonts.notoColorEmoji(),
])

Which does nothing except make the loading time of my app 10s longer.
Proposal
Can we have something like WebColorEmoji.precache() to let us load the NotoColorEmoji font before we actually render it?

Thanks for the report @crizant
Can you take a look at this issue and check if it resembles your case or not ?

Thanks for the report @crizant Can you take a look at this issue and check if it resembles your case or not ?

No. They are totally different.

I think this is a duplicate/similar to:

https://github.com/flutter/flutter/issues/78422


New completed-docs "tags" property doesn't work

Bug Report

TSLint version: 5.8.0
TypeScript version: 2.5.3
Running TSLint via: CLI

TypeScript code being linted
...
/** @see Class */
export const balls: string = 'balls';
...
    /** @inheritDoc */
    public async doSomething () : Promise<string> {
        return balls;
    }
...

with tslint.json configuration:
...
"completed-docs": [true, {
	"classes": {"visibilities": ["exported"]},
	"enums": {"visibilities": ["exported"]},
	"functions": {"visibilities": ["exported"]},
	"interfaces": {"visibilities": ["exported"]},
	"methods": {"privacies": ["protected", "public"]},
	"namespaces": {"visibilities": ["exported"]},
	"properties": {"privacies": ["protected", "public"]},
	"types": {"visibilities": ["exported"]},
	"variables": {"visibilities": ["exported"]},
	"tags": {
		"content": {"see": [".*"]},
		"exists": ["inheritDoc"]
	}
}],
...

(Also tested with tags copied and pasted as a nested property of all of its sibling properties.)
Actual behavior
...
ERROR: /path/to/file.ts[12, 14]: Documentation must exist for exported variables.
ERROR: /path/to/file.ts[43, 2]: Documentation must exist for public,async methods.
...

Expected behavior
No errors.

Can you try without the curly braces:
"content": {"see": ".*"},

Looks like an issue with the docs and examples

(Also tested with tags copied and pasted as a nested property of all of its sibling properties.)

That seems to be the way it works. At least that's how it's done in the tests.

Thanks for the quick reply! Just tested with the configuration below and reproduced the same issue:
...
"completed-docs": [true, {
	"classes": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"enums": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"functions": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"interfaces": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"methods": {"privacies": ["protected", "public"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"namespaces": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"properties": {"privacies": ["protected", "public"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"types": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}},
	"variables": {"visibilities": ["exported"], "tags": {"content": {"see": ".*"}, "exists": ["inheritDoc"]}}
}],
...

Testing the rule revealed, that the new tags logic doesn't handle singleline JSDoc.
If you make it multiline, everything should work as expected.

Interesting, thanks! I'll wait for that to be resolved then before re-enabling this rule.

This was fixed by #3841 while waiting for #3557. 🎉


Upload then immediately delete?

I'm getting situations where files are uploaded, then immediately deleted. The files are already pretty big (they appear to carry other backups which were performed, so each backup makes the backed up file bigger for the next), which perhaps needs to be a seperate issue I'll post.
Also, once it has deleted the files, it then goes to reupload them, even though it is outside of allowed times.
My logs are attached and config below. Do you need any other information?
de91e161_hassio_onedrive_backup_2023-01-18T11-08-59.284Z.log

recovery_mode: false
local_backup_num_to_keep: 10
onedrive_backup_num_to_keep: 5
backup_interval_days: 2
backup_name: hass_backup
hass_api_timeout_minutes: 30
notify_on_error: true
exclude_media_folder: true
exclude_ssl_folder: true
exclude_share_folder: true
exclude_local_addons_folder: false
sync_paths: []
sync_interval_hours: 4
backup_passwd: redacted
backup_allowed_hours: 0-4, 23

Regarding uploads happening outside of allowed hours. You are right this is a bug. Backups won't be created but if it finds local backups that were not uploaded yet it will still do them. I will add a fix for this.
I think I understand what's happening here. Can you confirm you have 5 newer backups that exist both locally and in OneDrive and the ones being uploaded and then deleted are the 5 older backups you still have locally ?

Yes, I meant while it's uploading those backups you should be going over the 5 limit on OneDrive, then it will reach 10 and delete the 5 older backups it just pushed..

I am seeing the same issue. It continually tries to upload the 6th newest backup (I have set to have 5 in OneDrive, 10 locally), then immediately deletes it from OneDrive. 5 minutes later the process repeats:
01/20/2023 07:13:21 Info: Backup interval configured to every 24 hours
01/20/2023 07:13:21 Info: Backups / Syncs will only run during these hours: 0,1
01/20/2023 07:13:24 Info: Checking backups
01/20/2023 07:13:24 Info: Retrieving existing local backups...
01/20/2023 07:13:25 Info: Retrieving existing online backups...
01/20/2023 07:13:25 Info: Last local backup Date: 01/20/2023 00:21:22
01/20/2023 07:13:25 Info: Last online backup Date: 01/20/2023 00:21:22
01/20/2023 07:13:25 Info: Found 1 backups to upload.
01/20/2023 07:13:25 Info: Uploading hass_backup_2023-01-15-00-02 (01/15/2023 00:02:51)
01/20/2023 07:13:25 Info: Fetching Local Backup (Slug:c68d1016)
01/20/2023 07:13:27 Info: Backup (c68d1016) fetched successfully
01/20/2023 07:13:28 Info: Starting file upload. (Size:1376737280 bytes.  (Size:1376737280 bytes. Attempt: 1/3)
01/20/2023 07:26:24 Info: Uploaded 10%
01/20/2023 07:27:07 Info: Uploaded 20%
01/20/2023 07:27:48 Info: Uploaded 30%
01/20/2023 07:28:33 Info: Uploaded 40%
01/20/2023 07:29:13 Info: Uploaded 50%
01/20/2023 07:29:55 Info: Uploaded 60%
01/20/2023 07:30:39 Info: Uploaded 70%
01/20/2023 07:31:21 Info: Uploaded 80%
01/20/2023 07:32:04 Info: Uploaded 90%
01/20/2023 07:32:47 Info: Uploaded 100%
01/20/2023 07:32:49 Info: Upload completed successfully
01/20/2023 07:32:51 Info: Found 1 backups to delete from OneDrive.
01/20/2023 07:32:51 Info: Deleting file: hass_backup_2023-01-15-00-02.xxxxxx.tar
01/20/2023 07:32:52 Info: Backup Interval Completed.

Config:
recovery_mode: false
local_backup_num_to_keep: 10
onedrive_backup_num_to_keep: 5
backup_interval_days: 1
backup_name: hass_backup
hass_api_timeout_minutes: 60
notify_on_error: true
exclude_media_folder: true
exclude_ssl_folder: false
exclude_share_folder: false
exclude_local_addons_folder: false
sync_paths: []
backup_passwd: xxxxxx
backup_allowed_hours: 0-1
backup_instance_name: xxxxxx

As mentioned above, I believe I pinpointed the issue. Fix will be included in the next release.
In the meantime, this shouldn't happen if you have the OneDrive backup number above or equals to the local backup number.

Should be resolved now in version 1.41


build(ci): Fix build metrics report

Changes to finding GTest caused the build metrics job to fail as we don't have GTest in the image yet. See #11837

@assignUser The Generate and Upload build metric job seems to have skipped :| , can you update the yml to force it to run and then revert ?

Ah it skipped because this is a form pr. Let me reopen from a Velox branch.


org.scalastyle.scalariform.SpacesAfterPlusChecker produces spurious detection for covariant types.

subject says it all !
eg:
abstract class CompletionIterator[ +A, +I <: Iterator[A]](sub: I) extends Iterator[A] {

the +A and +I will be reported as violation of SpacesAfterPlusChecker rule.

Looks like it is fixed.


Error: Cannot read property 'branch-config' of undefined

I began integrating Branch.io into my Cordova project and ran across this build error. My config.xml file definitely has a widget element, but it seems like widget is resolving as undefined inside of hooks/lib/configXmlParser.js line 35:
var ulXmlPreferences = configXml.widget['branch-config'];

I've tried this with the config.xml file inside of testbed/config.xml instead of my own as well and still had this error.
Cordova:

Version: 6.5.0
Installed platforms:

android: 5.2.2
ios: 4.2.1

Closing this ticket, handling this issue in<EMAIL_ADDRESS>


The samples are missing bootstrap and jquery CSS and Libraries.

The sample repos are referring to the following css/js files which are missing in the repos. Please add them.
I was testing "quickstart/aspnet-core/ContosoTeamStats/" project, but they may be missing in other projects too..
/lib/bootstrap/css/bootstrap.min.css
/lib/bootstrap/js/bootstrap.bundle.min.js
/lib/jquery/query.min.js

Note to the Azure Cache for Redis team
If I recall correctly, I think this was intentional. I think maybe one of the NuGet packages was intended to add these files to the working directory when it was restored? If possible, it would be good to avoid having to manually manage and update version updates for these external dependencies as individual files outside of the package dependencies system.

If that's the case, then please update the documentation to install those artifacts before running the sample apps, thanks.


0.8.0

Upgrading dprint-core to 0.42.0 to avoid multiple versions in https://github.com/denoland/deno/pull/10867

There is a bit of a change to the API in dprint-core. I can upgrade it right now in this PR because I'm familiar with the change.

There is a bit of a change to the API in dprint-core. I can upgrade it right now in this PR because I'm familiar with the change.

That's be helpful, thanks!


wip: add error fields to opentracing spans

Checklist

[X] I have read the coding guide.

Description
Closes: #3795

@acha-bill please, have a followup regarding this please to see where we are


[High] Column type select broken

if I select a type in the new column side panel, most of the types disappear
https://user-images.githubusercontent.com/458736/123362745-bcde4180-d5a3-11eb-8711-4988ab52b675.mov

already fixed by @phamhieu waiting for deploy


kubernetes: 1.21.1 -> 1.21.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases.
meta.description for kubernetes is: "Production-Grade Container Scheduling and Management"
meta.homepage for kubernetes is: "https://kubernetes.io"
meta.changelog for kubernetes is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kubeadm passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kubectl passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kubelet passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-apiserver passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-controller-manager passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-proxy passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-scheduler passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/e2e.test passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-addons passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/.kube-addons-wrapped passed the binary check.

/nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/bin/kube-addons-lib.sh passed the binary check.

9 of 11 passed binary check by having a zero exit code.

3 of 11 passed binary check by having the new version present in output.

found 1.21.2 with grep in /nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2

found 1.21.2 in filename of file in /nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2

directory tree listing: https://gist.github.com/1c4dcabefaa1c279d2ba90421fcdca21

du listing: https://gist.github.com/46724df2c036c18b26d288fee69d9ca5

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

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
kubectl
kubernetes

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2 \
  --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 kubernetes https://github.com/r-ryantm/nixpkgs/archive/9fb4ba960ac374df9ba278bc2304a2cb6356d84d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2
ls -la /nix/store/z4x7gx0a6xy5nycdkfimadqn76hw24lj-kubernetes-1.21.2/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

2 packages built:

kubectl
kubernetes

Maintainer pings
cc @johanot @offlinehacker @saschagrunert for testing.

Result of nixpkgs-review pr 127321 at 9fb4ba96 run on aarch64-linux 1

2 packages built successfully:

kubectl
kubernetes

2 suggestions:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/applications/networking/cluster/kubernetes/default.nix:36:15:
   |
36 |   patches = [ ./fixup-addonmanager-lib-path.patch ];
   |               ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/networking/cluster/kubernetes/default.nix:61:3:
   |
61 |   installPhase = ''
   |   ^


Build failed on RHEL 9.2.

Hi,
I can't  build it on RHEL9.2.
Steps:

dnf install git cmake gcc-c++
git clone https://github.com/opcm/pcm.git
cd pcm
mkdir build
cd build
cmake ..
cmake --build .

This is my log:
[root@localhost build]# cmake ..
-- System: Linux-5.14.0-284.11.1.el9_2.x86_64
-- Build type: Release
-- initial CMAKE_CXX_FLAGS:
-- initial CMAKE_C_FLAGS:
-- Set LINUX_SYSTEMD=TRUE for a systemd unit file.
-- CMAKE_CXX_FLAGS:  -Wno-unknown-pragmas -fPIC -Wextra -DPCM_USE_PERF -Wl,-z,now
-- CMAKE_C_FLAGS:  -Wno-unknown-pragmas -fPIC -Wextra -DPCM_USE_PERF -Wl,-z,now
-- AddressSanitizer is enabled
-- To disable AddressSanitizer, use -DNO_ASAN=1 option
-- CMAKE_CXX_FLAGS_RELEASE: -Wall -O3 -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- CMAKE_CXX_FLAGS_DEBUG: -Wall -O0 -g -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- CMAKE_CXX_FLAGS_RELWITHDEBINFO: -Wall -O3 -g -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- Detected Linux distribution: rhel
-- Using static libasan
-- To use dynamic libasan, use -DNO_STATIC_LIBASAN=1 option (required for CentOS)
-- Local SIMDJSON exists: /root/pcm/src/simdjson/singleheader/simdjson.h
-- Compiling with SSL support, requires libssl-dev or openssl-devel or libopenssl-devel or libopenssl-dev package installed
-- To disable SSL support, use -DNO_SSL=1 option
-- OpenSSL version 3.0.7 >= 1.1.1, OpenSSL support enabled
-- Install directory: /usr/local
-- CPACK_GENERATOR is RPM
-- Configuring done (0.0s)
-- Generating done (0.0s)
-- Build files have been written to: /root/pcm/build
[root@localhost build]# cmake --build .
[ 18%] Built target PCM_STATIC
[ 37%] Built target PCM_STATIC_SILENT
[ 40%] Built target PCM_SHARED
[ 41%] Linking CXX executable ../bin/pcm
/usr/bin/ld: cannot find -lasan
collect2: error: ld returned 1 exit status
gmake[2]: *** [src/CMakeFiles/pcm.dir/build.make:98: bin/pcm] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:260: src/CMakeFiles/pcm.dir/all] Error 2
gmake: *** [Makefile:156: all] Error 2
[root@localhost build]# rpm -qa | grep -i asan
libasan-11.4.1-3.el9.x86_64
[root@localhost build]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.2 (Plow)

Hi,
could you please install libasan-static and try again?
dnf install libasan-static
does it help?

Hi,
No libasan-static on RHEL9 or RockyLinux9.
I also install the epel-release.
[root@RockyLinux9 build]# dnf search asan
Last metadata expiration check: 0:00:22 ago on Tue 16 Jul 2024 09:23:48 AM CST.
=========================================================================================== Name Matched: asan ===========================================================================================
gcc-toolset-12-libasan-devel.i686 : The Address Sanitizer static library
gcc-toolset-12-libasan-devel.x86_64 : The Address Sanitizer static library
gcc-toolset-13-libasan-devel.x86_64 : The Address Sanitizer static library
gcc-toolset-13-libasan-devel.i686 : The Address Sanitizer static library
libasan.x86_64 : The Address Sanitizer runtime library
libasan.i686 : The Address Sanitizer runtime library
libasan8.i686 : The Address Sanitizer runtime library from GCC 12
libasan8.x86_64 : The Address Sanitizer runtime library from GCC 12
rust-libsqlite3-sys+with-asan-devel.noarch : Native bindings to the libsqlite3 library
rust-libsqlite3-sys0.25+with-asan-devel.noarch : Native bindings to the libsqlite3 library
rust-rusqlite+with-asan-devel.noarch : Ergonomic wrapper for SQLite
rust-rusqlite0.28+with-asan-devel.noarch : Ergonomic wrapper for SQLite
========================================================================================= Summary Matched: asan ==========================================================================================
rust-quick-error+default-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error1+default-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error1-devel.noarch : Macro which makes error types pleasant to write

Hi,
thank you for checking. Perhaps installing one of the "The Address Sanitizer static library" packages can help. Too bad the packages are named so differently on various Linux distributions..
Also a workaround is possible: compiling with dynamic asan instead. For that please use the option suggested in the PCM compilation log from above: -DNO_STATIC_LIBASAN=1
git clone https://github.com/opcm/pcm.git
cd pcm
mkdir build
cd build
cmake -DNO_STATIC_LIBASAN=1 ..
cmake --build .

Let me know if either solutions worked for you.

Hi,
Thanks for your help.
It's worked.


Remove Travis CI configuration

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

During this period of limited Jenkins service, reducing our Travis needs until they can be effectively served.

Coverage decreased (-0.003%) to 69.83% when pulling f1dc6fe3ec6495ab260ac69fc4a1854527617846 on kennknowles:travis into b82cd2446fa681576f83bae0fc2bdd1f03be5e7e on apache:master.

R: @davorbonaci

Pulling out the error:
Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default)
on project beam-sdks-parent:
Failed during checkstyle execution:
Unable to find suppressions file at location: beam/suppressions.xml:
Could not find resource 'beam/suppressions.xml'. -> [Help 1]

To be honest, it seems wrong that it ever works, since the actually invalid relative path is resolved sort of randomly to a place that the pom.xml in question doesn't even own but is pulled in by the dependency set up. But best would be to just fix it for Travis (if we care; Jenkins is back) rather than spend time on it.
Side note: we should probably also fully qualify our resources, so org/apache/beam/suppressions.xml.

Possibly maven version? We could apt-get it if so.

This is likely a versioning issue. The thing is that after we solve this one, there are more issues coming up, unfortunately. Overall, I don't think this is worth the time right now. I'd prefer just to disable Travis.

Let's disable it then. It has obscured our signal for months. Infra needs to flip this switch? I'll wipe out the file here.

Yes, Infra has to disable the switch. @jasonkuster

This will be best handled by an infra ticket -- I've filed https://issues.apache.org/jira/browse/INFRA-14027 to track.

Well, we could make travis vacuous to get signal but I suppose it will not matter for long.

I predict this will be the first green PR in months :-)

Changes Unknown when pulling ab21076f6748315c6bc283a987452c3fc17621a9 on kennknowles:travis into ** on apache:master**.

Coverage decreased (-0.1%) to 69.687% when pulling ab21076f6748315c6bc283a987452c3fc17621a9 on kennknowles:travis into 14a90d7c5196d96de66e897687d28202d790439f on apache:master.

Infra has removed the travis webhook, so we're good to go on that front.

There is still value Travis CI provides for python as that is the only way we can test installation on mac. Is it possible to just keep the Python tests around and remove all things related to Java.
cc @aaltay

I agree with @sb2nov. Python tests in Travis is green, and it is providing an especially valuable signal with macos tests. Until we can have macos coverage in other forms, I am in favor of keeping python tests in Travis.

It's not so simple as that. Travis could possibly be used to test "a little" -- this feature or that feature of the project, but it cannot test the project. How could we justify testing one component and not the other?
Then, Travis is not nearly as configurable as Jenkins, and really doesn't align with the future growth of the project.
MacOS signal, indeed, is valuable, but that's the only pro -- everything else are cons that are really hard to justify.

I don't understand that argument completely though. It is not like Travis is stopping us from running tests for other parts on Jenkins.
The main reason we faced issues with Travis was that our tests took longer than an hour in contrast python tests finish in about 10 mins have generally been pretty stable on Travis as well. So if it can help with development in certain parts of the project I fail to see the rational that we shouldn't use it.

I think one way to think about it could be that we don't have a CI system, we just have a suite of CI systems where we prefer Jenkins whenever possible but shouldn't discard others if they can provide some value.

Nearly every component we have finishes tests within the 10 minute mark when executed alone. The thing is that we have so many components. How could we justify testing one component and not the other?
"Some value" is not enough, because there's a cost involved too. All contributors will have to wait for the signal to come back, someone has to maintain the infrastructure around it, cognitive load, etc.

I don't think the technical portrayal of Travis is accurate here. We did hit some actual issues (a bit improved now with auto cancelation) but we were trying to use a wrench to hammer a nail. It is easy to use Travis in a way so that you have ~zero cost for a little benefit. It doesn't need to scale if you don't try to do everything. I view our failure to benefit from Travis as almost entirely our fault.
This discussion and decision about whether and how we choose to utilize the tool do not belong on a PR. I started this PR just to mitigate the Jenkins outage; now we don't have that option without flipping it back on anyhow so I am just going to close the PR.

In particular, "failure to benefit from Travis" doesn't at all hold from Python's perspective, especially with the recent (ongoing? looks like the most recent build was 4 hours ago) Jenkins outages.
At the very least, it can provide a smoke signal while jenkins is down and/or slow. Say, testing Python + Java Core.
FWIW, I looked for an on-list discussion of this decision to remove travis, and didn't see one.

The community had a discussion looong ago -- with Jenkins being our preferred solution and Travis-CI being a temporary patch. In fact, folks have been working on unification for a while now. With the aggregate Travis signal being broken for months now and nobody stepping in to fix it, it certainly seems like the right kind of clean up.


Recurse over arrays for watch notices

Currently the elements of arrays inside watch notices aren't converted
to intances of RecursiveOpenStruct, they are converted to instances of Hash
instead. This mean that accessing certain fields works differently for
objects retrieved directly than for objects received in a notice. For
example, to extract the internal IP address of a node retrieved directly
the code is like this:
ip = node.status.addresses.detect { |x| x.type == 'InternalIP' }.address

But for a notice it is like this:
ip = node.status.addresses.detect { |x| x['type'] == 'InternalIP' }['address']

This complicates code that needs to treat objects in the same way,
regardless of how they have been retrieved.
To avoid that this patch changes the WatchNotice class so that the
constructor adds the RecursiveOpenStruct :recurse_over_arrays option.

@abonas @simon3z @masayag please review.

@moolitayer @cben can you review?

:+1: good catch, recurse_over_arrays is desired and consistent with rest of kubeclient.
Is there any backward-compatibility concern?
I think not as a RecursiveOpenStruct is nearly drop-in compatible with a hash.

Look good, one nit. Agree with @cben this can be considered backward compatible

Maybe we cab add a simple test for the array access compat?
Silly really since we all know it works but I would add one anyway

Thanks for your review @cben and @moolitayer. I have added the backwards compatibility test as you suggested.

@simon3z thanks for merging this. One can we expect a new release of the gem containing the fix?

@simon3z thanks for merging this. When can we expect a new release of the gem containing the fix?

@jhernand you're welcome, the PR was reviewed and approved by @cben and @moolitayer so merging was just bookkeeping.
@abonas @bazulay any plans around the gem release?

@abonas @bazulay any plans around the gem release?

no plans from my side, I am not focusing at this gem development at the moment

@abonas who is currently responsible for doing releases of the gem?

@jhernand I suggest asking @simon3z and @bazulay


Fix parsing of hidden comments

The hidden comment from the web site
//-title there is no title

is actually processed as
<//-title>there is no title<///-title>

because there is no whitespace between - and t. Jade treats //-title
as a hidden comment.
This PR fixes the parsing problem. I moved all the comment handling
code into one place, too.

Looks good, thanks!


Issue 20

https://github.com/Hireology/erlen/issues/20

Coverage decreased (-1.0%) to 94.609% when pulling e903fb23b6fa5077ea7d89f2003239558d9f10ce on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.

Coverage decreased (-1.0%) to 94.609% when pulling e903fb23b6fa5077ea7d89f2003239558d9f10ce on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.

Coverage decreased (-1.7%) to 93.85% when pulling d314cc6a43056e0694a3911b1e0993b67c40400b on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.

Coverage decreased (-1.2%) to 94.385% when pulling 73912c983bbf9edd65defa239ecbc9e94e11386e on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.

Coverage decreased (-0.4%) to 95.187% when pulling 2b00f9c2ed8ba2b782afd89847ce6cabb611c91a on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.

Coverage increased (+0.7%) to 96.257% when pulling 9cf8314a3e2fad0d36fff34445597204493cf413 on issue-20 into ae31f02079df847c6ecf0827b08d04f06f650912 on master.


MOV files are reported as 0 size in iOS7 & iOS8 w/ multiple attribute present

I was able to reproduce with this jsfiddle: http://jsfiddle.net/zrKQD/3/.
The issue is only reproducible if the multiple attribute is present on a . With this attribute set, all browsers on iOS7 report the File size attribute as "0". Removing this attribute results in as-expected size determination by the browser, but, of course, you can only select one file at a time.
I have filed a bug with Apple and am waiting for updates.  A workaround will likely be provided until this is fixed.
See #989, where this was discovered.

I just upgraded from custom.fineuploader-4.4.0.js to azure.fine-uploader.js and tested it on iPhone 5s and found same bug.....    wondering if anyone else has seen this issue / bug?

What version are you using?

/*! 2015-04-21 */

@mikewebaphorism This is a Chrome-specific issue. so everyone is likely seeing this. There is also a similar issue, #1401.

@mikewebaphorism "2015-04-21" isn't a version. Regardless, this is a Chrome issue. You can follow the status of this by looking at the chromium bug I filed, linked to a few messages back.

Thank You

I just wanted to say i really love you for creating this 'issue'.  I've been trying to track down this chrome ios bug for WAAAAAAY too long.  You are my hero.


[Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

AndroLabServer/requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:  39.0.1 -> 65.5.1
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Checkmarx AST – Scan Summary & Details – 62c939a4-98b4-4e00-a3d4-d10f026c4bf9
New Issues

Severity
Issue
File / Package
Scan Engine

MEDIUM
Cleartext_Submission_of_Sensitive_Information
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/DoLogin.java: 128
CxSAST

MEDIUM
Cleartext_Submission_of_Sensitive_Information
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/DoTransfer.java: 152, 287
CxSAST

MEDIUM
Input_Path_Not_Canonicalized
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/ViewStatement.java: 27
CxSAST

MEDIUM
Privacy_Violation
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/MyBroadCastReceiver.java: 37
CxSAST

MEDIUM
Privacy_Violation
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/ChangePassword.java: 214
CxSAST

MEDIUM
Privacy_Violation
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/LoginActivity.java: 147
CxSAST

MEDIUM
SSRF
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/ChangePassword.java: 138
CxSAST

MEDIUM
SSRF
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/DoTransfer.java: 156, 157, 158
CxSAST

MEDIUM
Use_of_Hard_coded_Cryptographic_Key
/InsecureBankv2/app/src/main/java/com/android/insecurebankv2/CryptoClass.java: 25
CxSAST


Adapt csv files for release version 1.3.1

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.34%. Comparing base (69dec59) to head (5179600).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##           release-1.3    #3927   +/-   ##
============================================
  Coverage        64.34%   64.34%
============================================
  Files              353      353
  Lines            19013    19013
============================================
  Hits             12234    12234
  Misses            5526     5526
  Partials          1253     1253

Flag
Coverage Δ

unittests
64.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Search spec

I'm looking into migrating our current search from tire to elasticsearch-ruby as per #7. So far I've bundled all the search-related methods and indexing found in Person into a Searchable concern. Not a big fan of rails concerns, but right now it's a good enough step getting the search-related stuff into a single place, and we can look into perhaps turning it into a decorator, to be applied on Person in search-specific contexts, later.
(Using this post as a guide to the switch.)
There isn't much existing test coverage for current search functionality, aside from some controller tests checking that something is returned by search#index.
I don't think it's worth adding coverage to the current functionality before the switch, but it'd be great to have a couple of good acceptance and unit tests for the new expected one.
@cromulus, if you could write something up in the form of user story scenarios fleshing out the desired functionality, that'd be awesome. If you don't have enough time before tomorrow's weekly meeting, we can also do it together.

I'll then turn those into acceptance specs and run them as I do the switch. Once things are wired in and running minimally, I'll work on changing the indexing and result sets.

Sent by @cromulus over email:

Primary Goal of Search: To identify groups of people who share common demographic or ‘experience’ characteristics. Currently this is simply a matter of sorting through columns of an excel sheet. Here are a few examples of past searches:

People who do shift work and do not have a bank account
Mothers under the age of 40
People who have had a severe maintenance issue in their apartment, live in Queens
Parents who have at least part-time employment and access to a desktop computer

These searches would primarily be achieved through searching through tags. We would use tags for concrete characteristics: motherhood, maintenance issues, etc. And then other fields like those mentioned below for computer type, location, etc.

Secondary Goal: The secondary goal of search is to find a certain individual. This is definitely needed/helpful because we try not to leave DIG members’ contact information floating around, so being able to go back and access someone’s phone number or email address is important.

Primary Fields:
Name
Phone
Email
Age
Location (zip? neighborhood?). Perhaps a “within N miles of zip code”
Tags

Full text search of notes and comments, currently, isn’t part of our features, but we could foresee a time when that would be valuable, just not at the outset. Once we start to build a database, full text search is something we’d probably add on.


Question: Remote publisher-subscriber

Hi,
I'm trying to understand how to setup a remote publisher-subscriber pair communication msgs over UDP. Tried to search for examples and documents could'nt find something for quick start. Is there any links that is available which would help?
Thanks.

You have documentation here. Also you have an example here. I hope this help you.

@richiware  Thanks for the links. But, I'm trying to setup a remote pub-sub model. i.e nodes running on two different machines. Could you point me to the respective docs or links?

You don't need any special action to setup a remote pub-sub model. The example referenced will work when run on two machines on the same local network

Thanks. It worked.

You're welcome


install-flynn script issues

I've come across a couple of potential issues with the install-flynn script.
Firstly if you use the documented instructions here: https://flynn.io/docs/installation#ubuntu-14.04-amd64 i.e.
$ sudo bash < <(curl -fsSL https://dl.flynn.io/install-flynn)

and any of the packages has an interactive update then you won't be able to put any input in the interactive update. The script needs export DEBIAN_FRONTEND=noninteractive somewhere to work properly.
Additionally the script seems out of sync with the packer scripts. From a standard Trusty Cloud Image ( http://cloud-images.ubuntu.com/trusty/current/ ) I have to run:
DEBIAN_FRONTEND=noninteractive apt-get ${apt_options} install --install-recommends language-pack-en linux-generic-lts-vivid
DEBIAN_FRONTEND=noninteractive apt-get ${apt_options} autoremove
DEBIAN_FRONTEND=noninteractive apt-get ${apt_options} dist-upgrade

before running the install script to get to the same place as the packer output.

Thanks for this analysis! We should definitely add the noninteractive environment variable.
We don't upgrade the kernel in the install script because there are no known bugs that affect us so far in the older kernels and it requires a reboot.


New package: BranchAndPrune v0.1.0

Registering package: BranchAndPrune
Repository: https://github.com/Kolaru/BranchAndPrune.jl
Created by: @Kolaru
Version: v0.1.0
Commit: 9fdad011240f1fdb2befa9874d5714fec70d11a2
Git reference: master

Please add (at least)
[compat]
julia = "1"

to your project file and retrigger the bot.


remove Stage.setTheme

should be handled at GUI level, stage could just have a method set the background color

done dd508901a31d11e17b003c5757f51461cca8d094


Parametrizable router: add the ability to specify a max-length for routes

Part of #1722

Closed as part of route-and-execute


Colors of TransformControls' Axes Not Rendering Correctly After Mouse Hover

three version: 0.128.0
@react-three/fiber version: 6.0.19
@react-three/drei version: 4.3.3
node version: 15.10.0
npm version: 7.5.3

Problem description:
Colors of TransformControls' axes become white after mouse hover.
Their original color (red, green, and blue) are gone, which differs from the example shows in the official Three.js documentation.
Before mouse hover:

After mouse hover:

Relevant code:
Not sure what causes this bug, but you can find it here

Running into the same problem...

So I tried to track down the cause of this one was it's affecting a project where I'm trying to use TransformControls from pmndrs/drei. It seems like it was introduced in cc079be

I think I have found the root cause of this issue. I have looked at the original implementation of the transform control in the threejs library and tried to replicate the visual feedback.
I netted out with something like this :

Cause
So what seems to be wrong in the TransfromControl.js is the state management when the pointer is not hovering on a gizmo axis.  The error is probably in the following code block; here is my TransformControl.js from my node_modules folder. You can find the block here at line 1273
       // Hide disabled axes

        //@ts-ignore

        handle.material.opacity = handle.material.opacity || handle.material.opacity; //@ts-ignore

        handle.material.color = handle.material.color || handle.material.color.clone(); //@ts-ignore

        handle.material.color.copy(handle.material.color); //@ts-ignore

        handle.material.opacity = handle.material.opacity;

        if (!this.enabled) {
          //@ts-ignore
          handle.material.opacity *= 0.5; //@ts-ignore

          handle.material.color.lerp(new Color(1, 1, 1), 0.5);
        } else if (this.axis) {
          if (handle.name === this.axis) {
            //@ts-ignore
            handle.material.opacity = 1.0; //@ts-ignore

            handle.material.color.lerp(new Color(1, 1, 1), 0.5);
          } else if (this.axis.split('').some(function (a) {
            return handle.name === a;
          })) {
            //@ts-ignore
            handle.material.opacity = 1.0; //@ts-ignore

            handle.material.color.lerp(new Color(1, 1, 1), 0.5);
          } else {
            //@ts-ignore
            handle.material.opacity *= 0.25; //@ts-ignore

            handle.material.color.lerp(new Color(1, 1, 1), 0.5);
          }
        }

Broken code
This block of code doesn't make sense to me
       // Hide disabled axes

        //@ts-ignore

        handle.material.opacity = handle.material.opacity || handle.material.opacity; //@ts-ignore

        handle.material.color = handle.material.color || handle.material.color.clone(); //@ts-ignore

        handle.material.color.copy(handle.material.color); //@ts-ignore

        handle.material.opacity = handle.material.opacity;

I suppose that it was used to cache the axis colour in a previous revision, but as @Amaranthos mentioned cc079be commenting this block of code doesn't seem to do anything.
Maybe @joshuaellis, this could be the key to solve that problem, but I couldn't make sense of it.
Axes dissappearing
At the end of that code block
  } else {
            //@ts-ignore
            handle.material.opacity *= 0.25; //@ts-ignore

            handle.material.color.lerp(new Color(1, 1, 1), 0.5);
          }

This called as soon as the component is enabled, for me resulting in the axes disappearing entirely before the first hover when dynamically attaching TransfromControl to an object, the *= is the culprit here.
Managing the end of the hover state
Looking at the pointerHover event, the axis property is set to null when the user not hovering on top transform gizmo. So we can use that to reset the opacity of the gizmo. The following code created the gif that I shared at the top.
         if (!this.enabled) {  //component is not enabled. Hide the axes

           handle.material.opacity = 0;

        } else if (this.axis) {
          if (handle.name === this.axis) { // pointer hover an axis, set opacity of this.axis to 1

            handle.material.opacity = 1.0;

          } else if (this.axis.split('').some(function (a) {  //don't understand this bit
            return handle.name === a;
          })) {

            handle.material.opacity = 1.0;

          } else {  //set all other axis to 0.25

            handle.material.opacity = 0.25;

          }
        }else{   //when this.axis is null set all axis to maximum opacity expect the planar ones
          handle.material.opacity = handle.name==='XY'||handle.name==='YZ'||handle.name==='XZ'? 0.5 : 1;
        }

Please, @joshuaellis let me know the best course of action. Do you want me to create a PR with the following changes?
I think it would be ideal for the @react/three-drei TransfromControl component to follow the original three js behaviour.

The solution was in the end pretty simple!  See the PR.


Tor Browser launcher error

I am getting a “signature verification failed” error when I try to launch the tor browser launcher in subgraph. Is there a way of fixing that?
Steve

I am getting the exact same error.

Has this been resolved?

Has this been resolved?

No. Tor Browser is the only way of accessing the internet on this system, and until it works there is no way of getting net access to fix anything

gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir" --refresh-keys --keyserver keyserver.ubuntu.com

Guys, I was having the same issue, then I decided to turn off my firewall (GUFW) and try to launch Tor Browser again. It worked! Then, I turned on the firewall again and now everything's working normally. I really don't know if the issue was really caused by the firewall, but that was the one and only thing I did and it worked. I hope this is useful somehow.

Hi,
I'm having similar issues with installing Tor Browser (and launcher) on Ubuntu 18.04.
When I first tried the installation I was able to download the software and install it but I was getting an error:
“SIGNATURE VERIFICATION FAILED”. The error code is GENERIC_VERIFY_FAIL.
After updating these keys several times the problem persisted. Now I can not even start the launcher, even after multiple uninstall/reinstalls/restarts.
After doing some digging I came across this article regarding attacks on GPG keyrings that may be causing the issue:
https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f
There is also a problem with the directory when trying to update the keyrings. I've just read I need to stop trying to update keywrings as many of them maybe corrupt. Hence, I can't recall the exact directory error message but it was something to do with it not being large enough to store the updates (I may be wrong there though).
I can't find a fix for this anywhere.
Thanks

Same problem here on Thinkpad running Ubuntu 18.04.2 LTS - time and again the same issue...

Same isssue with new install of Mint 19.2


[code-completion] Fix assertion hit in getTypeOfReference via code completion

enum QuxEnum : Int {
  case Qux1 = 10
  case Qux2 = 20
}

func foo(x: QuxEnum) {
  _ = x == .Qux1 || x == ./* code complete here */Qux2
}

Code completion is re-typechecking the assignment in func foo above. On the first pass the UnresolvedMemberExprs corresponding to the enum elements are transformed into DotSyntaxCallExprs. When it later re-typechecks via typeCheckUnresolvedExpr with the assignment as the parent, the type checker ends up in getTypeOfReference where references to EnumElementDecls are assumed to not occur.  It looks like typeCheckUnresolvedExpr calls an overload of solve() that bypasses the SanitizeExpr ASTWalker, which cleans up ASTs for the constraint-based type checker. Adding that along this path seems to resolve the issue.

Resolves Resolves rdar://problem/38144409.

@swift-ci please smoke test

@swift-ci please smoke test

The previous fix caused a regression for CompletionKind::PostfixExpr caught by a local run of the stress tester. Added the test case and changed the fix to focus on unresolved members specifically (InferUnresolvedMemberConstraintGenerator is only used when completing unresolved members from what I can tell).
Does this look ok @benlangmuir ?

Build failed
Swift Test Linux Platform
Git Sha - 870915dee65f8a9e782f9b9b93f82f0e1ba7da4b

@nathawes Yes, that looks great!

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 781539c5c3d67ee625324dba9e9743bf39798bea

Build failed
Swift Test Linux Platform
Git Sha - 781539c5c3d67ee625324dba9e9743bf39798bea

Failures seem unrelated
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - a0cf755528000f45f3d15d51d8c0ab9581cefd7b

@swift-ci smoke test OSX

@swift-ci smoke test OSX

@swift-ci please smoke test OS X


Support arbitrary user defined partition column in ListingTable (rather than assuming they are always Dictionary encoded)

Which issue does this PR close?
-
Rationale for this change
Let the user decide if they may want to encode partition values for file-based data sources. Dictionary encoding makes sense for string values but is probably pointless or even counterproductive for integer types.
What changes are included in this PR?

the data type specified partition_columns is now the actual output type
SQL mapping has been changed to follow that EXCEPT the default for unspecified types which I kept at Dict(u16, utf8)
I kept the "buffer reuse" logic that was in there but extended it more dictionary types. I use a type-safe approach here because Arrow buffers may become typed at some point w/ the arrow2 merger

Are these changes tested?
Adjusted existing tests.
Are there any user-facing changes?
BREAKING: Types for partition columns in file-based sources are no longer dictionary encoded by default. The user MUST choose a dictionary type if they want to achieve this.

Breaking Change
Before
let file_scan_config = FileScanConfig {
    table_partition_cols: vec![
        (
            "group".to_owned(),
            DataType::Utf8,
        ),
        ...
    ],
    ...
};
let partitioned_file = PartitionedFile {
    partition_values: vec![
        ScalarValue::Utf8(Some("foo".to_owned())),
        ...
    ],
    ...
 };

After (exact)
If you want an exact conversion:
let file_scan_config = FileScanConfig {
    table_partition_cols: vec![
        (
            "group".to_owned(),
            DataType::Dictionary(
                Box::new(DataType::UInt16),
                Box::new(DataType::Utf8),
            ),
        ),
        ...
    ],
    ...
};
let partitioned_file = PartitionedFile {
    partition_values: vec![
        ScalarValue::Dictionary(
            Box::new(DataType::UInt16),
            Box::new(ScalarValue::Utf8(Some("foo".to_owned()))),
        ),
        ...
    ],
    ...
 };

After (alternative)
You may just decide that you don't to dictionary-encode at all:
let file_scan_config = FileScanConfig {
    table_partition_cols: vec![
        (
            "group".to_owned(),
            DataType::Utf8,
        ),
        ...
    ],
    ...
};
let partitioned_file = PartitionedFile {
    partition_values: vec![
        ScalarValue::Utf8(Some("foo".to_owned())),
        ...
    ],
    ...
 };

or that you want a different dictionary key type:
let file_scan_config = FileScanConfig {
    table_partition_cols: vec![
        (
            "group".to_owned(),
            DataType::Dictionary(
                Box::new(DataType::Int8),
                Box::new(DataType::Utf8),
            ),
        ),
        ...
    ],
    ...
};
let partitioned_file = PartitionedFile {
    partition_values: vec![
        ScalarValue::Dictionary(
            Box::new(DataType::Int8),
            Box::new(ScalarValue::Utf8(Some("foo".to_owned()))),
        ),
        ...
    ],
    ...
 };

Note that in all cases, the types in FileScanConfig::table_partition_cols and PartitionedFile::partition_values MUST be in-sync (strictly speaking that hasn't changed, before this PR both had been converted to UInt16 dictionary types).

(BTW I can find time to work on the API in the next day or two if needed)

Added docs here https://github.com/apache/arrow-datafusion/pull/5576

to something like (to force the API to change) ... Field

Field contains other information that is irrelevant here like nullability. We could assert on the correct value though (i.e. not nullable). Also this only concerns on of the two API changes, the other one (PartitionedFile) is still silently breaking. To avoid that we would need to rename partition_values to something else. However I'm not sure if a rename would trigger people to not only follow the rename but also change the types correctly.

And then add some a method and docs to help the upgrade

Since the user needs to adjust their code anyways, I'm not sure if such a random method helps. It's hard to find and because the uint16 dict type is so arbitrary, I'm not sure it should exist in the long run.

Field contains other information that is irrelevant here like nullability. We could assert on the correct value though (i.e. not nullable). Also this only concerns on of the two API changes, the other one (PartitionedFile) is still silently breaking. To avoid that we would need to rename partition_values to something else. However I'm not sure if a rename would trigger people to not only follow the rename but also change the types correctly.

Good point re Field and non relevant columns
What about a type that made the dictionary encoding explict, something like
struct PartitionedColumn {
  name: String,
  data_type: DataType,
  dictionary_index_type: Option<DataType>
}

And then have a new function that defaults to Dictionary 🤔  But that is kind of ugly as well and now what happens if the data_type was a dictionary in the first place ...

now what happens if the data_type was a dictionary in the first place ...

You get a double-encoded dictionary? I don't know, but IMHO data_type+dictionary_index_type screams "just use DataType instead of inventing yet another type".

You get a double-encoded dictionary? I don't know, but IMHO data_type+dictionary_index_type screams "just use DataType instead of inventing yet another type"

Yes I agree -- that is what probably should have been done in the first place, but it was not. So now we need to figure out a reasonable way to help avoid subtle regressions.
Maybe we can handle it by updating the docs / making it easy to do the right thing (use dictionary) 🤔

I've made the following changes:

partition_type_wrap and partition_value_wrap helper methods are now public
docs mention these helpers
there's a transition auto-fix that adds the dictionary wrapping to the value if the type demands it but spits out a warning. this is also tested

This PR had a merge conflict so I took the liberty of fixing that and pushing

Got here as a downstream user who is affected by this change. Thinking through this, I wouldn't totally write off dictionary encoding integers as useless, since there still are benefits to dictionary arrays besides space savings. They essentially mark columns as having low cardinality and provide the set of unique values. Any scalar compute functions run on these columns can be applied to the dictionary while leaving the indices buffer untouched. That is an easy to way to achieve what I would expect out of a "smart" compute engine: when projecting partition columns, project the distinct values rather than the expanded/materialized array. It's possible DataFusion already handles this in a smart way I'm unaware of though.
I'd also note that the ideal partition column types are probably run-end encoded arrays (RunArray), once they are implemented.

@wjones127 you can still dictionary-encode integers by specifying the column type in FileScanConfig as DataType::Dictionary(Box::new(DataType::Int64), Box::new(DataType::UInt8)) (for example), see https://github.com/apache/arrow-datafusion/pull/5545#issuecomment-1465873451

@wjones127 you can still dictionary-encode integers by specifying the column type in FileScanConfig as DataType::Dictionary(Box::new(DataType::Int64), Box::new(DataType::UInt8)) (for example), see https://github.com/apache/arrow-datafusion/pull/5545#issuecomment-1465873451

Noted 👍 I'm not objecting to this change. Just wanted to provide information to any other developers who end up reading this PR and are thinking about how they will adapt their code.


Updated build doc in guide.md

cargo build now outputs to /target/debug, changed doc to reflect that.
steve suggested to add description for cargo build --release
autogenerates to guide.html. Used pre and code tags instead of ``` by following previous examples.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

lgtm

@bors r+

 @bors r=huonw 2ff5f92

:hourglass: Testing commit 2ff5f92 with merge 57a95dc...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


Style/disabled filter chips

Description
Changed styles of disabled filters to differentiate it from enabled filter.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Could you provide instructions so we can reproduce them? Please also
list any relevant details for your test configuration
Before:

After:

[ ] Test A
[ ] Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] The commit message/PR follows our guidelines

Other information:

Is there ticket for these changes?

Yes we have a ticket - UIUX-497.


Cross compiling fails with cmake for CORTEXA53 since 0.3.19

The optimizations introduced in 0.3.19 with 302f226 are leading to the following cross compilation error if cmake build is used:

/build/openblas/kernel/CMakeFiles/dgemm_kernel.c:8:10: fatal error: /src/openblas/kernel/arm64/dgemm_kernel_8x4_cortexa53.c: No such file or directory
8 | #include "/src/openblas/kernel/arm64/dgemm_kernel_8x4_cortexa53.c"

I nailed it down to the fact that while in cross compile the prebuild.cmake becomes involved to apply the architecture specific settings, subsequently setting the DGEMM_UNROLL_M to the wrong/old value. It seems that the cross compile case wasn't covered by 302f226 for the CORTEXA53 yet...
A propper fix would be to apply the DGEM_UNROLL_M/N also TCORE specific in prebuild.cmake:889 for the CORTEXA53:
if ("${TCORE}" STREQUAL "CORTEXA53")
    set(DGEMM_UNROLL_M 4)
    set(DGEMM_UNROLL_N 4)
else ()
    set(DGEMM_UNROLL_M 8)
    set(DGEMM_UNROLL_N 4)
endif ()

fix_DGEMM_UNROLL_MN_for_cortexa53.patch

Oh right, sorry that happened. Guessing it would probably make sense to replace that long and ungainly table with a proper parser for  param.h at some point to prevent this from happening again.

Hi @martin-frbg , I encounter the same build issue with v0.3.24:
src/kernel/arm64/dgemm_kernel_8x4_cortexa53.c: No such file or directory
I build with DYNAMIC_ARCH=true, do you think it is related ?

Strange, the fix in prebuild.cmake is still in place and the same code path should be taken by DYNAMIC_ARCH builds. Are you also cross-compiling ?

Yes I am also cross compiling


Update NoTargets Sdk.targets to fix typo

_CopyFilesMarkedCopyLocal target is disabled when SkipCopyFilesMarkedCopyLocal is set to true

/azp run


vector query - return points instead of polys at low zoom

[ ] activities as points at low zoom in query (to avoid vector rollup)

#3258


.Chart object empty in sub-chart

Output of helm version:
version.BuildInfo{Version:"v3.3.1", GitCommit:"249e5215cde0c3fa72e27eb7a30e8d55c9696144", GitTreeState:"clean", GoVersion:"go1.14.7"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.6", GitCommit:"d32e40e20d167e103faf894261614c5b45c44198", GitTreeState:"clean", BuildDate:"2020-05-20T13:16:24Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T18:46:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform: EKS
I suspect I'm doing something stupid.. but let me explain:
I have a parent chart that installs a subchart:
parent Chart.yaml
apiVersion: v2
name: my-parent-chart
description: A Helm chart for Kubernetes
type: application
version: 1.0.0
appVersion: 10.5.1

dependencies:
  - name: my-sub-chart
    version: 1.1.0
    repository: "https://my-helm-repo.com/helm"
    tags:
      - my-sub-chart

subchart Chart.yaml:
apiVersion: v2
name: my-sub-chart
description: A Helm chart for Kubernetes
appVersion: 10.5.1
version: 1.1.0

The installation fails like so (I know its a lint command, but the error is the same)
helm lint -f ../../tenants/common-secrets.yaml.dec -f ../../tenants/tenant-a-test-values.yaml -f ../../tenants/tenant-a-test-secrets.yaml.dec
==> Linting .
[INFO] Chart.yaml: icon is recommended
[ERROR] templates/: template: my-parent-chart/charts/my-sub-chart/templates/secrets.yaml:101:3: executing "my-parent-chart/charts/my-sub-chart/templates/secrets.yaml" at <include "my-sub-chart.labels" .>: error calling include: template: my-parent-chart/charts/my-sub-chart/templates/_helpers.tpl:20:27: executing "my-sub-chart.labels" at <include "my-sub-chart.name" .>: error calling include: template: my-parent-chart/charts/my-sub-chart/templates/_helpers.tpl:6:18: executing "my-sub-chart.name" at <.Chart.Name>: nil pointer evaluating interface {}.Name

Suffice to say that the ../../tenants/tenant-a-test-values.yaml contains
tags:
  my-sub-chart: true
  my-other-sub-chart: false

# sub-chart configuration
my-sub-chart:
  some:
    config: "values"

As you can see above, the subchart Chart.yaml does contain a name, and so does the parent Chart.yaml..
I did some playing around and it's of course not just .Chart.Name that's nil, but all fields of the .Chart object. Same for the .Release object.. it's just the first thing helm picks up per order of operation its trying to create a secret first, which includes a bunch of templated lables which includes the .Chart.Name:
from the offending tpl:
{{- define "my-sub-chart.name" -}}
{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" -}}
{{- end -}}

[...]
{{- define "my-sub-chart.labels" -}}
app.kubernetes.io/name: {{ include "my-sub-chart.name" . }}
helm.sh/chart: {{ include "my-sub-chart.chart" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
{{- if .Chart.AppVersion }}
app.kubernetes.io/version: {{ .Chart.AppVersion | quote }}
{{- end }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
app.kubernetes.io/deployed-version: {{ default .Chart.AppVersion .Values.deployedVersion | replace "/" "_" | trunc 63 | quote }}
app.kubernetes.io/deployed-by: {{ default "Helm" .Values.deployedBy | replace "/" "_" | trunc 63 | quote }}
{{- end -}}

Any idea what I'm doing wrong here?
Thanks!

nil pointer evaluating interface {}.Name

Looks like you're passing a nil value to the template. Check and make sure that the values being passed to an include are the correct values.
https://helm.sh/docs/howto/charts_tips_and_tricks/#using-the-include-function

Hi @bacongobbler
Could you share an example?
I'm also getting the same error, but I'm using a bit different. For example, the .Release.Name and .Chart.Name it works only on metadata.namespace (I'm not going to use in there) and I get the error when I set as a label or under the affinity.
File -> templates/deployment.yaml
...
kind: Deployment
spec:
metadata:
  name: {{ include "test.fullname" . }}
  namespace: {{ include .Values.namespace . }}
  labels:
    {{- toYaml .Values.labels | nindent 4 }}
...
  template:
...
    spec:
      {{- if .Values.affinity }}
      affinity:
        {{ toYaml .Values.affinity | indent 8 }}
      {{- end }}
...

File -> values.yaml
labels:
  test: {{ .Chart.Name }}

namespace: {{ .Release.Name }}-{{ .Chart.Version }}

affinity:
  podAntiAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      - topologyKey: kubernetes.io/hostname
        labelSelector:
          matchLabels:
            app.kubernetes.io/instance: {{ .Release.Name }}

Thanks

@LozanoMatheus - you can't use templateing in values.yaml - see here for discussion and workarounds: https://github.com/helm/helm/issues/2133
@bacongobbler - it's this line:
app.kubernetes.io/name: {{ include "my-sub-chart.name" . }} where I'm passing the context into the my-sub-chart.name tpl function - that context seems to be empty, or at least it appears that way when it's trying to access the .Chart object from it.
I don't know if it makes a difference, but I should probably mention that I'm able to install my-sub-chart quite happily on its own.
I was modifying the scope around the secret that was causing the issue, using {{ with .. }} - and as the documentation clearly states, it modifies the scope of . - so that things like .Release or .Chart are no longer available.

same solution like @reschex  . scope is changed because i entered a loop with the function range.
You just need to :

replace any .Values.x by $.Values.x
same for include, replace

    {{- include "argo-app.labels" . | nindent 4 }}

by
    {{- include "argo-app.labels" $ | nindent 4 }}

same solution like @reschex  . scope is changed because i entered a loop with the function range.
You just need to :

replace any .Values.x by $.Values.x
same for include, replace

    {{- include "argo-app.labels" . | nindent 4 }}

by
    {{- include "argo-app.labels" $ | nindent 4 }}


Proposed 0.60.0-rc4

Codecov Report

Merging #2051 into develop will increase coverage by 0.03%.
The diff coverage is 93.33%.

@@             Coverage Diff             @@
##           develop    #2051      +/-   ##
===========================================
+ Coverage    67.67%   67.71%   +0.03%
===========================================
  Files          680      680
  Lines        49204    49219      +15
===========================================
+ Hits         33299    33327      +28
+ Misses       15905    15892      -13

Impacted Files
Coverage Δ

src/ripple/protocol/impl/BuildInfo.cpp
82.6% <ø> (ø)
:white_check_mark:

src/ripple/ledger/View.h
100% <ø> (ø)
:white_check_mark:

src/ripple/ledger/impl/View.cpp
89.36% <100%> (+1.37%)
:white_check_mark:

src/ripple/app/paths/impl/BookStep.cpp
85.76% <90.9%> (+0.2%)
:white_check_mark:

src/ripple/beast/core/WaitableEvent.cpp
87.75% <0%> (-4.09%)
:x:

src/ripple/server/impl/BaseWSPeer.h
77.5% <0%> (-3.34%)
:x:

src/ripple/core/impl/Stoppable.cpp
92.55% <0%> (-3.2%)
:x:

src/ripple/beast/asio/io_latency_probe.h
97.01% <0%> (-1.5%)
:x:

src/ripple/beast/clock/chrono_util.h
91.3% <0%> (ø)
:white_check_mark:

... and 4 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 6cea5d0...e27a389. Read the comment docs.


An option to keep already existed content

I'm using several build scripts for several site parts. It will be nice to have an option only to overwrite existed keys in Manifest file & not to clear all content in already existed file.

use the seed options for that: https://github.com/danethurber/webpack-manifest-plugin#optionsseed


Steam Client doesn't properly reconnect when account has SteamGuard enabled

Description
Our Steam Client defined in a ProtectedAccount instance doesn't properly reconnect after asking for the 2FA code from either E-Mail or SteamGuard mobile app. This causes accounts w/ enabled SteamGuard to not function correctly with Titan.
This issue can be worked around by using a already generated sentry file, as it skips the reconnect progress. This does not include Shared Secret accounts (#51, seems to be the same issue).
Reproduction Steps

Setup Steam Guard protected account
Connect to Steam network using it
Get kicked off for not providing a auth code
Get asked for the auth code
-- At this point, we're not properly reconnecting with the submitted auth code.

Errors
Note that these are custom debug messages I implemented.
12:31:52 [Main] INFORMATION GC - marc3842h (Protected) - Disconnected from Steam. Retrying in 2 seconds... (1/5)
12:31:52 [Main] INFORMATION TwoFactorAuthForm - Successfully closed 2FA code form.
12:31:54 [Main] DEBUG GC - marc3842h (Protected) - Reconnecting to Steam and starting watchdog for steam connection.
12:31:56 [Main] DEBUG GC - marc3842h (Protected) - Steam Client connected after 2 sec: False

System Information
Operating System:
$ uname -romi && lsb_release -a
4.13.12-1-ARCH x86_64 unknown GNU/Linux
LSB Version:	1.4
Distributor ID:	Arch
Description:	Arch Linux
Release:	rolling
Codename:	n/a

Titan version: ^HEAD - local changes, 2 commits ahead of origin/master.

Closing this issue as it no longer persists.


Magento 2.3

We have installed the module in our system which has magento 2.3 properly. We're facing the payment. During the test, the bank withdraws money. But the process does not appear successful page and again we receive a return to the cargo information page.

Hi @ozanyeni , I am from the iyzico developer team. Thank you for your feedback.
For solution, our team of<EMAIL_ADDRESS>has contacted you.


fix versionsort chunk split on non-ASCII numerics

Description
Fixes a bug with 2024 Edition versionsort, where a string chunk will split on all numeric characters. For example, this would cause imports containing non-ASCII numeric characters to be incorrectly sorted.
Unformatted (Playground link):
use std::cmp::Ordering;
use print๙msg::print as first_print;
use print0msg::print as second_print;
use printémsg::print as third_print;

fn main() {
    first_print();
    second_print();
    third_print();

    assert_eq!("print๙msg".cmp("printémsg"), Ordering::Greater);
}

/// '๙' = 0E59;THAI DIGIT NINE;Nd;
mod print๙msg {
    pub fn print() {
        println!("Non-ASCII Decimal_Number")
    }
}

/// '0' = 0030;DIGIT ZERO;Nd;
mod print0msg {
    pub fn print() {
        println!("ASCII Decimal_Number")
    }
}

/// 'é' = 00E9;LATIN SMALL LETTER E WITH ACUTE;Ll;
mod printémsg {
    pub fn print() {
        println!("Lowercase_Letter")
    }
}

Formatted imports (nightly 2024-11-29, Playground link):
use print0msg::print as second_print;
use print๙msg::print as first_print;
use printémsg::print as third_print;
use std::cmp::Ordering;

Here, printémsg should be sorted before print๙msg, but since ๙ is a non-ASCII numeric, that import is split into two short string chunks, which will sort before the one longer chunk.
Changes & Notes

Replaces a char::is_numeric() check with the correct char::is_ascii_digit() call in VersionChunkIter::parse_str_chunk().
I also ran the updated rustfmt against the repo and found no changes, so there isn't a separate commit for that.
Related to tracking issue rust-lang/rust#123800

I think we're good to go here, but just want to do a quick sanity check by running the updated rustfmt on some larger rust codebases. Here's a link to the diff check job.


Fix .embedded in Scala from being cut off

This PR removes the opacity from .embedded in Scala and darkens the color instead. This fixes italic text from being cut off. Note the $f in the screenshot:
Before

After

Fixes #44

:+1:


Apple Reminders: Initial version.

Description
Search and manage all your Apple reminders in one convenient place, without switching between apps. Save time and increase your productivity with the ability to easily search and mark reminders as completed.
Currently supports:

Search apple remiders
Get reminders by list
Render priority icons
Present note body
Show due date in human readable form
Mark reminder as done

Technical Details

Uses AppleScript JS(JXA) to interface with apple reminders
Apple's local APIs are slow, so polling slices of data is required, to avoid throttling (i.e Reminder[] => Name[])
Caching each request and uses optimistic updates to avoid unnecessary waiting time and improve overall UX

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Just out of curiosity; what's the difference between this and My Reminders in Raycast?

@pernielsentikaer Hi there! Could you please elaborate? I wan not able to find a reminders app

It wasn't disabled, just couldn't find it on the search.
Maybe because it was called "My Reminders"?
Or maybe because it was built-in and I assumed it would be in the store?
And I developed it because other people couldn't find it.
This sucks..

I'm sorry that you didn't find it; simply searching for Reminder should find it, can you confirm that?

It didn't, but now it does 😅 Added an alias

I will close this since it's a standard feature in Raycast. Sorry for the inconvenience


Analyzer crash: Concurrent modification during iteration

Analyzer Feedback from IntelliJ
Version information

IDEA IU-181.4203.550
2.0.0-dev.62.0
IU-181.4203.550, JRE 1.8.0_152-release-1136-b20x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.13.5 unknown, screens 1440x900  Retina

Exception
Please append the contents of:
file:///private/var/folders/zr/lnfchxms55s5d2_1xc5f47_w00d63q/T/report.txt
Dart analysis server, SDK version 2.0.0-dev.62.0, server version 1.20.3, error: Failed to send analysis.implemented notification.
Concurrent modification during iteration: Instance of '_CompactLinkedHashSet<String>'.
#0      _CompactIterator.moveNext (dart:collection-patch/dart:collection/compact_hash.dart:438)
#1      Search.subtypes (package:analyzer/src/dart/analysis/search.dart:383)
<asynchronous suspension>
#2      SearchEngineImpl.membersOfSubtypes.addMembers (package:analysis_server/src/services/search/search_engine_internal.dart:40)
<asynchronous suspension>
#3      SearchEngineImpl.membersOfSubtypes (package:analysis_server/src/services/search/search_engine_internal.dart:51)
<asynchronous suspension>
#4      ImplementedComputer.compute (package:analysis_server/src/domains/analysis/implemented_dart.dart:34)
<asynchronous suspension>
#5      scheduleImplementedNotification (package:analysis_server/src/operation/operation_analysis.dart:36)
<asynchronous suspension>
#6      AnalysisServer._scheduleAnalysisImplementedNotification (package:analysis_server/src/analysis_server.dart:1149)
<asynchronous suspension>
#7      AnalysisServer.sendStatusNotificationNew (package:analysis_server/src/analysis_server.dart:883)
#8      _rootRunUnary (dart:async/zone.dart:1134)
#9      _CustomZone.runUnary (dart:async/zone.dart:1031)
#10     _CustomZone.runUnaryGuarded (dart:async/zone.dart:933)
#11     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336)

@scheglov

https://github.com/dart-lang/sdk/issues/33412


!price (bug)

hello, I have two graybanns lenses, I use the command, !price graybanns and it only tells me that I don't have any, when they sold me two. It can be a bug or a fault of mine, because when I use it in other cosmetics it works.

Please follow the bug guidelines, create a new one here

You can try removing and adding it back.
!remove sku=30104;6 and;
!add sku=30104;6&max=2
Then try to check the price again
!price Graybanns

i changed sku=30104;6 to name=Graybanns and works