Incorporate Stripe timezones in reporting

Are you a current Fivetran customer?

Dylan, Fivetran
What change(s) does this PR introduce?

This PR aims to bring this package closer in line with reporting metrics that can be seen in the Stripe UI. The issue is that when aggregating to day, week, month or quarter, Stripe converts the timestamps from UTC to whatever timezone the user prefers. This PR makes the same transformations.
Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No  (please provide explanation how the change is non breaking below.)
New functionality only comes into play when a new variable is set. Otherwise, nothing should change.

Is this PR in response to a previously created Issue

[x] Yes, Issue [#12]
[ ] No

How did you test the PR changes?

[x] CircleCi
[ ] Other (please provide additional testing details below)

@fivetran-joemarkiewicz Got a first draft of this for your review.
My personal view is that we should only incorporate the timezone when we are 'date_trunc'-ing to something that is not a timestamp. I feel we should leave timestamps as UTC, and let BI tools (or users) do the final mile there if they prefer.
Therefore, I have (1) created a new macro that takes timezones into account and (2) replaced column references in that macro wherever we were converting a timestamp to a date, month, quarter, week, etc.
Example config looks like:
vars:
    stripe_timezone: 'America/New_York'

TODOs:

[ ] Make this cross database compatible
[ ] Change CI to test with timezone


MUI Date Picker Component - Time Picker UI Issue

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I have used Date Picker for my Application
it is working as expected in android chrome browser but safari is showing some UI issues. can anyone please solve this

<LocalizationProvider dateAdapter={AdapterMoment}>
            <DateTimePicker
                renderInput={(props) => (
                    <CustomTextfield
                        {...props}
                        {...InputProps}
                        id={props.id}
                        name={props.name}
                        placeholder={props.placeholder}
                        error={props.error}
                        helperText={props.helperText}
                    />
                )}
                label={props.label}
                value={props.value}
                onChange={props.onChange}
                {...props}
            />
        </LocalizationProvider>

this is giving me in safari browser as
Any solution for solving this ?
Expected behavior 🤔
There should not be any visible boxes around the hours
Steps to reproduce 🕹
Steps:

Use Date Picker component
try that in iOS Safari browser for iPhone

Context 🔦
UI Issue
I pasted the Image of UI issue
Your environment 🌎

`npx @mui/envinfo`
Safari in iPhone 12 pro
```
  System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
  Binaries:
    Node: 14.15.4 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.10 - /usr/local/bin/npm
  Browsers:
    Chrome: 96.0.4664.45
    Firefox: 94.0
  npmPackages:
    @emotion/react: ^11.5.0 => 11.5.0
    @emotion/styled: ^11.3.0 => 11.3.0
    @mui/core:  5.0.0-alpha.53
    @mui/icons-material: ^5.0.4 => 5.0.5
    @mui/lab: ^5.0.0-alpha.51 => 5.0.0-alpha.53
    @mui/material: ^5.0.4 => 5.0.6
    @mui/private-theming:  5.0.1
    @mui/styled-engine:  5.0.2
    @mui/styles: ^5.0.1 => 5.0.2
    @mui/system:  5.0.6
    @mui/types:  7.0.0
    @mui/utils:  5.0.1
    @types/react:  17.0.33
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    styled-components:  5.3.3
```

@Venkateshwar-AINQA Your example is incomplete. Please provide us with a codesandbox that demonstrates the problem.

@Janpot In Normal Browsers like chrome, firefox it is working fine as expected
but in mobile browsers for safari alone it is throwing a UI issue [showing blue box around the numbers in clock ] which I give it as a screenshot
here is the link you have asked for - https://codesandbox.io/s/materialuipickers-material-demo-forked-wg1so

Duplicate of https://github.com/mui-org/material-ui/issues/26664


Moved argmin_testfunctions into argmin repo

Codecov Report
Attention: 27 lines in your changes are missing coverage. Please review.

Comparison is base (370c76d) 90.26% compared to head (39cdff5) 90.38%.

:exclamation: Current head 39cdff5 differs from pull request most recent head 949031d. Consider uploading reports for the commit 949031d to get more accurate results

Files
Patch %
Lines

tools/testfunctions/src/rosenbrock.rs
67.21%
20 Missing :warning:

tools/testfunctions/src/sphere.rs
66.66%
4 Missing :warning:

tools/testfunctions/src/zero.rs
70.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #409      +/-   ##
==========================================
+ Coverage   90.26%   90.38%   +0.11%
==========================================
  Files         141      162      +21
  Lines       19936    20463     +527
==========================================
+ Hits        17995    18495     +500
- Misses       1941     1968      +27

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


Checks don't work for modules

Some of the NPM modules utilise new feature of Node.js that is called modules, that is declared as:
{
  ...
  "type": "module,
  ...
}

in package.json file. And the current implementation of checks, like:
node -e 'require("/nix/store/4dj4m2yanj5z1182ji9y47vir6w723bk-formdata-polyfill-4.0.10/lib")

doesn't work with that new module type.
I found that for the packages of the module type, this check would work:
node --input-type=module -e 'import  "/nix/store/4dj4m2yanj5z1182ji9y47vir6w723bk-formdata-polyfill-4.0.10/lib/formdata.min.js"'

that is, the check needs to add --input-type=module option and specify the file explicitly.

As a workaround for the projects that face this check issue:
let
  env = pkgs.js2nix {
    package-json = ./package.json;
    yarn-lock = ./yarn.lock;
    overlays = [
      (self: super: {
        # TODO: remove once this https://github.com/canva-public/js2nix/issues/20 is resolved
        buildNodeModule = pkgs.${system}.lib.makeOverridable
          (args: (super.buildNodeModule args).override { doCheck = false; });
      })
    ];
  };
in env.nodeModules


Optional physics features

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

Currently, all features used by the physics system are required to load a physics engine. In the interest of supporting multiple physics engines with different sets of features, the physics system can be refactored so that some features are optional. Optional features are just skipped if not supported by a physics engine, while required features prevent the engine from being loaded.
Pull request #573 started work on this but couldn't be merged in time for GitHub migration. We'll reopen the PR there.

@mxgrey made a comment on the pull request after the freeze which didn't make it into the back up, so I'll copy it here for it not to get lost:

Michael Grey commented on pull request #573:
Optional physics features
I’m not 100% clear on why an additional RequestFeatures would be needed, but the runtime cost of it should be unnoticeable if the casted entities are being cached. Either way, this  is probably a premature optimization concern. I’d say whenever there’s a  need in the future to audit the compilation times, this would be a  prime candidate to look at.

I can respond properly once we're done with the migration.

I’m not 100% clear on why an additional RequestFeatures would be needed

We need DetachableJointFeatureList for 2 entities: the child link and the detachable joint. The joint is created from the childLink->AttachFixedJoint call, so it inherits all features from the link. After it's created, we need to call some "core" joint features, and also store the joint in the global joint map. For those, MinimumFeatureList is necessary. If DetachableJointFeatureList doesn't include MinimumFeatureList, we need to make a RequestFeatures call to cast it.

Either way, this is probably a premature optimization concern. I’d say whenever there’s a need in the future to audit the compilation times, this would be a prime candidate to look at.

+1

Now that #62 has been merged, all that's missing is to add support for TPE. There's initial work on the chapulina/tpe branch which needs to be cleaned up.


Support for WebpackJsonp

Hello, it would be fantastic to have support for files in the form of
(window.webpackJsonp = window.webpackJsonp || []).push(/* ... */);
Any way of making this work, please? 🙏🏻

Added.
Run retidy with the flag -t webpack-jsonp specified.


31_Depth_Charge/ruby

Simple stuff for ruby, and an editor config file.  Those are useful ;)

looks great, thank you! 🎁


Adding a column (and updating view) is not reversible

Assume the following:
visible_users_v01.sql:
select * from users where deleted_at is not null

class CreateViewForVisibleUsers < ActiveRecord::Migration[5.2]
  def change
    create_view :visible_user
  end
end

that will bake the current fields into the view. So now when I want to add a field:
class AddStuffToSupplierOrder < ActiveRecord::Migration[5.2]
  def change
    add_column :users, :stuff, :string
    update_view :visible_users, version: 1, revert_to_version: 1
  end
end

That works as well.
The problem arises when I want to rollback the migration:
cannot drop table users column stuff because other objects depend on it
DETAIL:  view visible_users depends on table users column stuff

Is it possible to make this reversible?

This is the danger of using * in a database view. The simplest workaround is:
def up
  drop_view :visible_users
  add_column :users, :stuff, :string
  create_view :visible_users
end

def down
  drop_view :visible_users
  remove_column :users, :stuff, :string
  create_view :visible_users
end


mean_squared_error with ignore_nan option

[x] fix test to chainer-chemistry style
[x] add double backward tests
[x] add documents

Codecov Report

Merging #190 into master will increase coverage by 0.14%.
The diff coverage is 82.14%.

@@            Coverage Diff             @@
##           master     #190      +/-   ##
==========================================
+ Coverage   76.64%   76.79%   +0.14%
==========================================
  Files          87       89       +2
  Lines        3712     3852     +140
==========================================
+ Hits         2845     2958     +113
- Misses        867      894      +27


Our .csv files lack columns whose first rows contain empty values

Describe the bug
It appears the BQ csv export function drops any columns whose row1 value is empty (or null)
To Reproduce
Steps to reproduce the behavior:

go to "Downloads and Methodology"
scroll down and click "download" for BJS of KFF Vaccinations
download RACE at STATE

downloaded BJS csv is missing race_contains_ethnicity and jail_per_100k
downloaded KFF vaccination csv is missing vaccinated_pct, population_pct and others
Expected behavior
Columns would remain despite some of the row values (including the first) being null
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Known issue? https://stackoverflow.com/questions/69660855/how-to-export-a-null-field-on-bigquery

It's hacky, but what about using -1 to indicate null? That way we'd ensure all columns are exported. I was thinking we could just sort the so "All" was first row but there are some (like KFF) where we had two columns that can only have a value in one of the other. In this case, one of those columns would always be lost due to this weird bug


Update build-release-run.md

"est accessible en écriture uniquement" is not a good translate for "are an append-only ledger". "append" imply the idea of write but only for add. "est accessible en écriture incrémentale uniquement" is more appropriate to include the idea of "add only".

Thanks


Makes border radius adjustable from lib/variables.less

Added a set of new variables which control the pixel size of
border-radius for varius box models. The variables are defined as:
@borderRadiusForms:   3px;
@borderRadiusTables:  4px;
@borderRadiusBoxes:   6px;
@borderRadiusLabels:  3px;
@borderRadiusMedia:   4px;
@borderRadiusButtons: 4px;
This is a proof of concept implementation of adjustable border radius. If you like the idea let me know what has to be changed in order to make the merge.

Cool, but not the level of control we need for rounded corners me thinks. That said, this is a good call to make things a bit more standard perhaps. I'll revisit some of the rounded corners' values in 2.0-wip.

Yep, I think it would be a good idea to just use one or two sizes, controllable from lib/variables.less, and then just have special cases if needed. It would ensure more consistency across the styles.
Thanks for the feedback and having a look.  S.

This is something I'd be interested to see in a future version of Bootstrap. Is this still under consideration?


correct typo in envoyproxy_io_proxy_http3_downstream.yaml

Thank you so mush for great project! I fixed a simple typo.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Fixing DCO or DCO: Sign your work

Thanks for all. Anyone can fix the typo.


Docker start error

Use the latest(now is 2023-10-29) version of TCG, there is error logs when start container.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/app/tabby_connection_gateway/cli.py", line 7, in <module>
    from .admin_server import AdminServer
  File "/app/tabby_connection_gateway/admin_server.py", line 2, in <module>
    from tabby_connection_gateway.gateway_server import GatewayServer
  File "/app/tabby_connection_gateway/gateway_server.py", line 5, in <module>
    import websockets
  File "/usr/local/lib/python3.7/site-packages/websockets-12.0-py3.7.egg/websockets/__init__.py", line 6, in <module>
    from .version import version as __version__  # noqa: F401
  File "/usr/local/lib/python3.7/site-packages/websockets-12.0-py3.7.egg/websockets/version.py", line 3, in <module>
    import importlib.metadata
ModuleNotFoundError: No module named 'importlib.metadata'

+1

Confirmed. :(


Get parameter failed; Retrying in background

Hi.
I tried to install in my Home Assistant 2023.8.0 via local and I get error:
Config entry 'local - xxxxxxxxxx' for fujitsu_airstage integration not ready yet: Get parameter failed; Retrying in background
Logger: homeassistant.config_entries Source: config_entries.py:1250
Tried with two different units and with same result.

Hi,
Thank you for letting me know.
I assume you have the correct IP address for your unit.
I'll add some more debugging information in the logs in the next update, so we can figure out which parameter failed.
If you want you could add this to configuration.yaml for more debug info:
logger:
  default: info
  logs:
    fujitsu_airstage: debug
    pyairstage: debug

Thanks!
I'll see if I can make any improvements tonight!

I found the problem, I got the device_id (mac address) from my router and it was lowercase, but the device expects all uppercase.
Once I entered with uppercase it is working as expected.

Ah, good catch! I'll add that to the config flow! Thank you!


Update index.js

The element in plugins array in not a plugin object. It's an array!

Hey @cainiaokan, thanks for the PR, but I'm actually working on this right now. It's an array in babel 6, and an object in babel 7. I got it fixed to work with both but there are several other differences mostly dealing with the template function that I'm trying to fix now.

@detrohutt Glad to hear you are working on it right now. Please keep up on this good work. I got stuck in here at this moment.


Move anno files that affect the db model out of respective UI app fol…

…ders

Hi @MN-public , this changes moves those annotation files that affect the base model out of the UI app folders.
Can you please check whether the tools still work with this setup?

Hi @MN-public , thanks for the hint. I have now moved the PresentationVariant to the file with the ValueList annotations, too.


OptionItem, ProductImage Summary Fields

Option Item - added Available as a summary field
ProductImage - added CMSThumbnail as summary field

I'll double check the failure on this. It may be how I have the test written as it's the PGSQL database instance.

Just realized I published this to dynamic/foxystripe, not my account. Once we merge this I'll zap the remote branch on dynamic

hold off on a merge for now, found another bug or two that I'll wrap up in here

Looks good, merging.

Just realized we'll need to specify a minimum requirement for GridFieldBulkEditingTool as the new function is for newer versions of that module.


Monitoring chart custom range only lets you increase/decrease minutes in 5 min intervals

Version: master 2.2 (12/14/18)
What kind of request is this (question/bug/enhancement/feature request):
Enhancement Request
Request:
Notice when you set a custom time range on monitoring charts that when you increase or decrease minutes and seconds with the up and down arrows built-in to the UI you can only go up or down in intervals of 5. Would like to request that we go up or down in intervals of 1 instead.

Version: master 2.2 (12/20/18)
Confirmed fixed. We can now increase any time (hours:mins:secs) in intervals of 1. I noticed some other oddities and will enter one or more bugs as necessary as I test further.


--device need to handle dirs

In the new Docker 1.2.0 release announcement it is stated:
"Previously, you could use devices inside your containers by bind mounting them ( with -v)   in a --privileged container. In this release, we introduce the --device flag to docker run which lets you use a device without requiring a --privileged container."
But when I change my start command for my docker container from:
docker run -i -t --rm \
    -e DISPLAY=unix$DISPLAY \
    -u chbr \
    -v /tmp/.X11-unix:/tmp/.X11-unix:ro \
    -v /home/chb/grid:/home/chbr/grid \
    -v /home/chb/files/Daten:/home/chbr/Daten \
    -v /home/chb/uni:/home/chbr/uni \
    --name="rdev" ubuntu-r:v1

to
docker run -i -t --rm \
    -e DISPLAY=unix$DISPLAY \
    -u chbr \
    --device=/tmp/.X11-unix:/tmp/.X11-unix \
    -v /home/chb/grid:/home/chbr/grid \
    -v /home/chb/files/Daten:/home/chbr/Daten \
    -v /home/chb/uni:/home/chbr/uni \
    --name="rdev" ubuntu-r:v1

I will get the following cryptic (error?) message:
2014/08/24 10:05:40 Post http:///var/run/docker.sock/v1.14/containers/1c92e198d279d782f76722e8f3a1b318013e072b3342c21ea92fa96ebb27b2a5/start: EOF
The command before using the --device flag will work with no problem; I'm also part of the docker group so that should also not be a problem. Does someone know what is happening?

also this was added by https://github.com/docker/docker/pull/10745#event-271179342


Convert sample code in tutorials to Python 3

@econchick  This is what I thought you meant by "python 3 support." Please correct me if I'm wrong.

[ ] Begin/Setup
[ ] Data Visualization
[ ] API
[ ] Web Scraping
[ ] IRC Bot
[ ] GUI

This can be broken down into separate issues based on who volunteers to do what.

Is there any progress on this?


Question about calculating the overlapping regions of source cloud and target cloud

Your work is great, I've recently been debugging your code to compare algorithms, but I've noticed that there seems to be an ambiguity. In pointcloud.py, when you calculate the overlap region between the source and target point clouds, you first fill tgt_corr, src_corr with a value of -1, and then calculate the correspondence: src_corr_is_mutual = np.logical_and(tgt_corr[src_corr] == np.arange(len(src_corr)), src_corr > 0). Shouldn't "src_corr > 0" be adjusted to "src_corr >= 0", because the index value starts from 0, and it's correct if for a point in the source point cloud, it has to be indexed to 0 for the target point.

Hi, I took a quick look, and seems like you are right.
I don’t think it affects the result much, but I will fix this once I verify
it more closely. Thanks for pointing this out!
On Wed, 26 Jun 2024 at 2:46 PM, CorgiBoyG @.***> wrote:

Your work is great, I've recently been debugging your code to compare
algorithms, but I've noticed that there seems to be an ambiguity. In
pointcloud.py, when you calculate the overlap region between the source and
target point clouds, you first fill tgt_corr, src_corr with a value
of -1, and then calculate the correspondence: src_corr_is_mutual =
np.logical_and(tgt_corr[src_corr] == np.arange(len(src_corr)), src_corr >
0). Shouldn't "src_corr > 0" be adjusted to "src_corr >= 0", because
the index value starts from 0, and it's correct if for a point in the
source point cloud, it has to be indexed to 0 for the target point.
—
Reply to this email directly, view it on GitHub
https://github.com/yewzijian/RegTR/issues/27, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIBP6Y35TFHKXAOEYPCG73ZJJPTFAVCNFSM6AAAAABJ5G4RYKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TINBZGMYDONQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, I took a quick look, and seems like you are right. I don’t think it affects the result much, but I will fix this once I verify it more closely. Thanks for pointing this out!
…
On Wed, 26 Jun 2024 at 2:46 PM, CorgiBoyG @.> wrote: Your work is great, I've recently been debugging your code to compare algorithms, but I've noticed that there seems to be an ambiguity. In pointcloud.py, when you calculate the overlap region between the source and target point clouds, you first fill tgt_corr, src_corr with a value of -1, and then calculate the correspondence: src_corr_is_mutual = np.logical_and(tgt_corr[src_corr] == np.arange(len(src_corr)), src_corr > 0). Shouldn't "src_corr > 0" be adjusted to "src_corr >= 0", because the index value starts from 0, and it's correct if for a point in the source point cloud, it has to be indexed to 0 for the target point. — Reply to this email directly, view it on GitHub <#27>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIBP6Y35TFHKXAOEYPCG73ZJJPTFAVCNFSM6AAAAABJ5G4RYKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TINBZGMYDONQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

Excuse me, thank you for your response and thank you again for the outstanding work you do. The network you designed for point cloud registration is very powerful and inspiring.


BUG: Timer doesn't reset on timer completion

"Time left to vote" remains at 00:00:00 after cycle completion, although the next cycle number is updated.

This was fixed by #184. But I will leave it open until we merge fa2-transfers branch to develop, so that if another member sees this bug on the staging site, it won't be re-reported


Update manifests to use RH-built Etcd image

Motivation
Use RH-based Etcd container
Modifications
Update image pointer to modh etcd repo
Result

/retest

You would need to change these lines to reflect modelmesh-serving based on the cloned repo name in tests/Dockerfile
https://github.com/opendatahub-io/modelmesh-serving/blob/master/tests/scripts/install.sh#L31
https://github.com/opendatahub-io/modelmesh-serving/blob/master/tests/scripts/install.sh#L46

/retest

/retest

/retest

/retest

/lgtm


Call to a member function getId() on null

I am creating the billing app with usage-based charge and I have followed this https://github.com/osiset/laravel-shopify/wiki/Creating-a-Billable-App
Expected Behavior
Successfully create the usage-based charges.
Current Behavior
Currently, it's giving Call to a member function getId() on null error
Failure Information

Steps to Reproduce

Create Usage-Based charges:

Redirect to usage-based charges URL:

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Package Version: v17.1.0
Laravel Version: v8.55.0
PHP Version: 7.4.26
Using a toolset (Docker, Laradock, Vagrant, etc.): ngrok

Failure Logs
Please include any relevant log snippets or files here.

Duplicate of #1002


.type should be .keyboard.type

the .type method comes from the Puppeteer.Keyboard class so await page.type(...) should really be await page.keyboard.type(...)

Thank you Kevin. Looks good to me.
The latest Puppeteer APIs have these breaking changes.


Side-by-side diff view

@steven9463912 what do you expect here. Please explain a little bit more.

:+

Any news on this topic, maybe an estimated release?

This is a big feature, currently we are not able to set a target release for it

Is any work-around it? like configuring an external diff (like kdif3) with easy access?

@alainm you can use an external diff, just right click on a file an external diff

This feature I am missing most. :heart:

Mind the details.

Just found out this program exists because I was looking for a git client for Linux.
The current unified diff and staging is so comfortable to use. kudos for all involved. 🥇. I believe it'll definitely will be even better with side-by-side diff.


Move the Test.Hspec.Extra module to cardano-wallet-test-utils

Overview
Move the Test.Hspec.Extra module to the cardano-wallet-test-utils package. This is a better place for it.
(I was tempted to merge the core-integration package into cardano-wallet-jormungandr... But it will need to be separate again when we add another backend.)

bors r+


Update generateClient.ts with new link to moved reserved_model_names.rs

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


Added //fn to the help command

Haven't found it anywhere inside of the mod yet, so I thought why not add it.
Also added missing > and . inside of it.
(plz ignore the typo fix in the comment, no idea how to remove the commit)
Edit:
Okay so github just added the other commit to this pr, so I guess it's included in here now??
Well the third commit basically adds color to the runs in here:

0 runs = red
1-9 runs = yellow
10+ runs = green
I've also noticed that the "," are bugged out and not showing in the whole thing, and Health, defense & mana are not working

Its not tested yet (because I have no friends!), but I'll try to test it in the next couple of hours

Alright looks good!


Suggest of Warship filtering

Hi,
Is it possible to add some filter in Warship page? It looks not cool as expected.
Suggesting fiter:

By numbers of combat
By winning rate
By all the other major meta data

It will be appreciated if it could be done. Thank you!

Yes, I actually did it before but it was not ideal. I am currently redesigning the filter system.

Hi there, it has been a while.
I will be working on warship filter really soon and it is now possible to advance warship filtering. An update will come soon.

Hello again, this feature has been implemented now. Best testing is gonna come soon and the update will be available on the 1st April.
I will close this issue for now.


Consider renaming repo to us-nicknames

existing name is quite verbose. Then it would match the python package name. I think all existing links should be redirected.

I think this sounds like a reasonable idea.  Can anyone think of a reason not to rename it?

Tagging everyone who's contributed in the last 2 years, in case anyone wants to weigh in. Feel free to ignore, and sorry for the spam!
@KenLewis @f0rk @c0bra @gpilgrim2670 @cwag03 @CalvinWu4 @louking @danielleevandenbosch @ITernovtsiy @lockster99

👍🏻 from me

I think "nicknames" would be better as it's not just US names. They are English country names.
My only concern about changing the name would be the Google search results for years of it being the current name. That's how I found this great repo. If you rename it, I suggest creating a new repo with the old name that just has a readme that points to the new one.
Just my two cents.

I'm with @KenLewis: be bold and go for "nicknames" with the idea that this covers all English language nicknames.
Conceivably at the data level one could add files like names-uk.csv someday if they ever wanted to differentiate nicknames that were only in common use somewhere else. But I speculate this would be more trouble than it's worth for most folks.
Likewise, keeping or re-creating "nickname-and-diminutive-names-lookup" just for search purposes is a great idea.

Not a contributor, but here's a user's perspective. My use case is to find nicknames in a pool of people whose nationality isn't known. I think the database could potentially support non-English names/nicknames. So why limit it via the repo name?
I.e., I support use of 'nicknames' if that's not already used.
Uh, oops -- looks like 'us-nicknames' has already been published: https://pypi.org/project/us-nicknames/

OK, removing the us- prefix sounds fine to me. I was hesitant to claim the name of just nicknames on PyPI, that seemed like such a desirable and general name that I wanted to leave it available. Think I'm being silly there, should we just claim it?
Or should we be more precise, and mention that this is a hand-curated list? I think this might differentiate us from other projects. Could do

nickname-list
nickname-roundup
nickname-compendium
nickname-anthology

I think nicknames or nickname-roundup (🤠 lol) are my top choices.

Uh, oops -- looks like 'us-nicknames' has already been published: https://pypi.org/project/us-nicknames/

Not a big deal the PyPI package is published already, it's version 0.1.0 so we can remove it. Probably should do it pretty soon though.

If I had a vote (I don't think I do), I would name it simply "nicknames" or "nickname-lookup". Sorry I don't like "-roundup" as I guess I don't know what it means in this context.

Sounds like everyone is good with nicknames.  Sounds good to me.  Should we go ahead and make the name change before we update the pipeline with Pypi API token @NickCrews ?

Ok, I made the change and it looks like the links automatically forward from the old repo to the new repo.  Doing a search on Google for nicknames github and clicking on the old repo result automatically forwards to the new repo.  If that's the case, I think creating a repo with the old name that points to the new repo may actually hurt us more than help us.  Thoughts?

Sweet thanks! I vote no on creating a new repo, Google is smart and they'll figure it out that they are the same.


Group by exact hout

Checklist

[x] I am running the latest version of the card
[x] I checked if there isn't another feature request opened with the same request
[x] I checked that the feature is not already available in the dev branch

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
group by exact hour e.g. 11-12, 12-13, 13-14 instead of by current e.g. 11.42-12.42, 12.42-13.42 ...

That is already possible if you make your graph end at the hour/start at the hour
span:
  end: hour

Thanks!


Improve travis setup

@ueberauth/developers I am still working on it.

@yordis I'm open to dropping the other versions for Travis.  @hassox thoughts?

Always down for dropping old versions personally ;)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8df179e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #494   +/-   ##
========================================
  Coverage          ?   85.4%
========================================
  Files             ?      17
  Lines             ?     418
  Branches          ?       0
========================================
  Hits              ?     357
  Misses            ?      61
  Partials          ?       0

Impacted Files
Coverage Δ

lib/guardian/token/jwt.ex
85.36% <ø> (ø)

lib/guardian/plug/keys.ex
83.33% <ø> (ø)

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 8df179e...44ba7d6. Read the comment docs.

@ueberauth/core yeah I wouldn't train the folks that it is fine for them to do not do their job upgrading their platform and by so we carry on their responsibilities

@ueberauth/core done!


Run unit tests in the browser

Not just in Node.  Need to be able to run tests with both a traditional script tag / global variable initialization, and also with AMD module loading.

Ideally also hook up the browser tests into a CI build.


[BEAM-14405] Fix NPE when ProjectID is not specified in a template execution

PR #16547 added handling for null ProjectIDs on command line execution,
but did not handle the possibility of null ProjectIDs in template
execution. PR #17094 added nullness checks in MonitoringInfoMetricNames,
which then triggered NPEs if the ProjectID was not specified during a
template execution.
This corrects this by checking for a null ValueProvider, a null value in the ValueProvider, and an empty String in the ValueProvider.

GitHub Actions Tests Status (on master branch)

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

Can one of the admins verify this patch?

Can one of the admins verify this patch?

R: @lukecwik

Run Java PreCommit

Would be great to follow up by removing the suppressions that made NPE possible in the first place, or we should presume there are others lurking.

@SuppressWarnings("nullness") is what I mean by suppressions.

We use checkerframework, which is a full type system (not heuristic) that prevents NPEs wherever it is not disabled.

Should this be mentioned in the release notes for 2.38.0 as a known issue?

Currently Beam release notes seems to be a list of auto generated JIRAs created at release time. For example, https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12351169
Is there a better place to record known issues found after that fact ?

There's CHANGES.md and the blog post and the affected versions field in the Jira. I don't know if we point users to these very much.

CHANGES.md seems to be the best candidate. Sent https://github.com/apache/beam/pull/17631 to update it on this and other recent issues.


Operators help page requires internet access

The help in the operators page is not integral to the page, but goes off to some on the web typescript developer documentation. This means that this help is not cached or running locally, and thus will not be accessible when there is no internet connection.
Please can you provide all PXT help as static pages within the PXT system itself, so that PXT can be cached or run locally and therefore used successfully without an internet connection.

The same is true of the statements page - it goes off to developer documentation elsewhere on the web, it will not work when there is no internet connection.

Documentations won't work when it is not live. We don't want to download all the documentation and keep it just for offline.

Current solution won't scale for offline. We will work on a solution where teachers will have to download separately the documentation

Won't fix from our end

Ok, thanks. Screen dump above shows that the UX of this is pretty abrupt if there is no internet connectivity - the functionality of the application appears degraded when internet disappears.

i.e. normal users will not know the difference between what is part of the editor, and what is not part of the editor. So as far as they are concerned, it's broken (this is what users tell me).
When you get a longer term story on this, could you refer to this github ticket, as I have references to this particular ticket in our support system and I will need a way of updating the users that reported this issue and this is my only point of reference at the moment. Thanks. (Just refer to this ticket in any new ticket that you create, and I will get notified and can then follow up with the appropriate users).


"Become Avatar" usefulUtility and JAT's script

JAT's script has been "QA'd". The "Become Avatar" script hasn't - a quick pass on that would be nice! Use any FST model, then attach the script.

I have the click me script staged on some avatars now, that looks good.
Question though, could we set this up to have the avatar list be part of the config.json instead of hard coded in the script? or would that be to heavy of a lift? Because then we are a stones throw away from my dream for this sort of app showing my favorite avatars as a clickable avatar entity that i only see. (i know that second is a larger ask, but i feel like doing the groundwork now would not be a crazy ask? or would it?)

@AndySeattle:

could we set this up to have the avatar list be part of the config.json instead of hard coded in the script?

Could you please explain what this means? I don't understand. It feels like this might be a separate feature request, but I don't yet understand the request.

@AndySeattle:

could we set this up to have the avatar list be part of the config.json instead of hard coded in the script?

Could you please explain what this means? I don't understand. It feels like this might be a separate feature request, but I don't yet understand the request.

Nevermind you are already doing what i want it to do, the other is indeed a feature request, well actually a separate thing altogether. (A way to visualize your avatars in a 3d space.) I just reviewed the files for the avatar selector and the blank config file, did not fully read the readme for the JAT script :) what you are doing is what i wanted you to do :) So i am gold. about to rig this with some of my avatars and give it a go.
my BIG question however looking at the code, could we reference the avatar locations in the config file instead of hard coding them? That would make this much more malleable. (as we are already pulling the avatar FST files from a reference in the config.json, could we also not pull the locations? I feel like having them hardcoded in the script, but the avatars not hardcoded in the script is disjoint of the data pertaining to them. )

Thank you for QAing this! And I appreciate your comments. What you're asking for (which is a great suggestion) belongs in a separate (small) project rather than in James Arnold Taylor's script specifically.


x/tools/cmd/goimports: adds flag control to delete extra blank lines before grouping

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

$ go version
go version go1.15.2 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/chenglong/Library/Caches/go-build"
GOENV="/Users/chenglong/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/chenglong/go/pkg/mod"
GONOPROXY="tkestack.io,k8s.io,git.code.oa.com"
GONOSUMDB="tkestack.io,k8s.io,git.code.oa.com"
GOOS="darwin"
GOPATH="/Users/chenglong/go"
GOPRIVATE="tkestack.io,k8s.io,git.code.oa.com"
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/local/Cellar/go/1.15.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/20/n4jpmhjs0hd9hjxg80yr2nww0000gn/T/go-build993050189=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

use goimports to format file.
current:

What did you expect to see?
Blank lines cause incorrect grouping. These blank lines are automatically generated by IDE.
What did you see instead?
Delete extra blank lines and regroup:

Any clue for this issue?

Two and a half years later and still not even looked into.


portal: Only derive key if needed

This allows for searches that find nothing or number of items
operations to complete without deriving the key.
I think with this one I wouldn't need the unstable feature anymore.

Not really finished but wanted to have an opinion first

See if https://github.com/bilelmoussaoui/oo7/pull/19 helps with the deadlocks.


Fixes the window title label option

Fixes the label option so it actually hides the label when toggled off
Adds a side effect to the label and icon toggles so one of them is always active

:heart:


How to place MarketOrder?

HI,
I tried to use it. It is working well with Limit Order, but how to place the market order??

Hi
Techically Market Order is a IoC (immediate-or-cancel) Limit Order with some unreachable limit price (like 1 for SELL, or Long.MAX_VALUE for BUY).

Hi
Techically Market Order is a IoC (immediate-or-cancel) Limit Order with some unreachable limit price (like 1 for SELL, or Long.MAX_VALUE for BUY).

How to limit the total amount of purchases？


Add links to Metabase on GIS import pages

As an analyst
I want the GIS import pages to have a link to the Metabase GIS analysis dashboard
So that I can see the GIS analysis for all projects
Acceptance Criteria:
Input page

Wireframe

[ ] Add card for GIS Metabase link
https://ccbc-metabase.apps.silver.devops.gov.bc.ca/dashboard/87-gis-analyses

background: #FFFFFF;
border: 1px solid #D6D6D6;
box-shadow: 0px 4px 4px rgba(0, 0, 0, 0.25);
border-radius: 8px;

[ ] Convert upload label & description to card

GIS Import Success Page

Wireframe

[ ] Add card to GIS import success page
https://ccbc-metabase.apps.silver.devops.gov.bc.ca/dashboard/87-gis-analyses

Implementation Details

DB:

.
.

Middleware:

.
.

Frontend:

.
.

Tests:

.
.

Documentation:

.
.

@VB-at-Bis  can all the acceptance criteria be checked off?


Is there a way to use cake and Cocoapods at the same time?

Is there a way to use cake and Cocoapods at the same time? This way we can use Cocoapods for dependencies like 3rd party libraries and use Cake to modularize our code.

Yes, but the Batter (currently) cannot use CocoaPods since it cannot see the Pod libraries.
We can probably make this automatic, if we detect the Pods directory we could its Pods target as a dependency of the Batter.

I can start work on this, can you guide me where to look in the code?

The XcakeProject is where we generate the Cake.xcodeproj, in there we will need to detect if the prefix is a Pods project, depend on the external target in the Pods xcodeproj and (maybe) add some link/include paths.

The scenario in my mind is to use cocoapods for 3rd party libraries and Cake to modularize my code. So for start, it is enough if the project builds with Cocoapods and Cake at the same time.

Yeah, so your modules (the Batter) will need that the Pods build first (the target dependency) and that they can see the Pods (so add search paths). Then it should work.

I have a sample project here: https://github.com/abbasmousavi/CakePods
It has some pods and is integrated with Cake and it builds successfully.
@mxcl I am trying to add required dependency and search paths manually, in order to understand what should be added to it to work.
I have tried adding Pod.framework as a dependency to Batter and adding search paths to it, but it does not work. also, we need to have access to pods from all modules inside Batter, so maybe we should add dependency and search paths to all modules in Batter?
Would you please take a look at this? what should be added to this project in order to have access from inside Bar module to Alamofire?

we need to have access to pods from all modules inside Batter, so maybe we should add dependency and search paths to all modules in Batter?

Yes, all batter modules will need this. We have a loop or two already in there for Batter modules, so you can add the dependency there.

I have tried adding Pod.framework as a dependency to Batter and adding search paths to it, but it does not work.

What's the error?

Would you please take a look at this? what should be added to this project in order to have access from inside Bar module to Alamofire?

K, so you mean the link you provided?

This works: https://github.com/mxcl/CakePods
I had to:

Add the Pods project to the Cake project
Add the Pod xcconfig files to the Cake project
Make the project settings use the xcconfig files

Note when opening it don’t have Cake.app running or it will regenerate Cake.xcodeproj and the changes will be lost.

Sorry for the delay, thank you for fixing the project, now it builds. I am trying to implement the steps that you have done on the project in the code.

LMK if I can help, I found figuring out how to make xcodeprojs quite tricky.
We use tuist/xcodeproj, but I made a facade wrapper (module: XcodeProject) that should be capable of all the above (I believe).

@mxcl please take a look at https://github.com/mxcl/Cake/pull/52. I am not familiar with tuist/xcodeproj, I have tried to follow the patterns in the code and I have tested the result on a simple cocoapods project and it worked. please let me know if it needs anything to be added or changed.


bootstrap css problem

if i add navbar-brand,

navbar-brand will display like this
.......................
this is i want

BTW
mobile first but off canvas less

You'll need to override things as you start to customize the navbar—we require a specific markup structure for that component. As you change that, expect to have to make style changes as well.

You'll need to override things as you start to customize the navbar—we require a specific markup structure for that component. As you change that, expect to have to make style changes as well.


Grafana Status Panel

I can't solve how to use the Status Panel plugin to indicate the state of the machines, assuming every query calls for an asset and its property status.
Nothing works, do you have any examples, docs anything that will tell me how to transform the SiteWise Asset data?
https://status.mimi.marmonim.com/plugins/vonage-status-panel?page=overview
Thanks

Hi @misiek303, is this the plugin you mean: https://grafana.com/grafana/plugins/vonage-status-panel/?
It would help if you could give us some info on what you've tried already that didn't work, the query types you're using (with any sensitive data removed)
I assume you've already tried using grafana transforms to get the data you need?


Cover case when file with the name, that we already have in our clients HashMap was sent

Just fixed itself, idk


feat: fixbug for 'WalletProvider' cannot be used as a JSX component

Summary
fixbug for 'WalletProvider' cannot be used as a JSX component

Closes #issue

https://github.com/rooch-network/rooch/issues/1339

@wow-sven help review


Cannot find reset function with functionName collector

Hi! Thank you for the library.
It seems that
        -   name: reset
            collectors:
                -   type: functionName
                    regex: ^reset$

cannot find a reset function.
Am I doing smth wrong?

Don't quote me on this, but I think I remember that we do not have support default PHP functions yet.

Yes, we only search for function definitions available to us. Maybe using something like JetBrains/phpstorm-stubs could be used to provide them.

Looked into it and we don't even support internal PHP classes either based on the code. The only thing we do is ignore them when they are the target of dependency. But they cannot be collected by a collector either.

I think a reasonable solution would be something like a PHPInternalCollector. WDYT?

@patrickkusebauch, Thank you!


Correction for raw affiliation CNRS & IHRIM (UMR 5317)

Correction needed for raw affiliation CNRS & IHRIM (UMR 5317)
raw_affiliation_name: CNRS & IHRIM (UMR 5317)
new_rors: ;02wmc6m46
previous_rors:
works_examples: W2771775599
contact: a6e65acc4e0d4723b81d5a1f65c3facd:bd6851a8cf727cb0cb0a0759c65d @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Change img reference

closes https://github.com/OpenBCI/OpenEXP/issues/40.
@andyh616, I tried this and worked locally. is this what you meant? or did you want change the base href such that we could just say images/blue.jpg?

hmm, I must've had something else wrong with the path because that's what I was trying to do and the images were not showing up.  this looks good to me!


Reloading page on Chrome, Next button stops working.

Describe the bug
The Next button wont move me forward to the next step. Maybe it has something to do with code validation?
To Reproduce
Steps to reproduce the behavior:

Go to 'holiday bow battle' on google chrome
Try doing a step incorrectly to trigger the validation
Refresh the page
Now the Next button doesn't move you forward. You can still move backwards but not forward.

Expected behavior
Should be showing me a code validation dialogue, or move me forward because I already completed earlier steps
Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Chrome
Version: arcade version:  [1.12.11]; Microsoft MakeCode version:  [8.5.14]

Here is an error I saw:

Stack trace:
Uncaught (in promise) TypeError: t.execute is not a function
    at K (main.js:1:563743)
    at setTutorialStep (main.js:1:565066)
    at onClick (main.js:1:570739)
    at Object.assign.onClick (main.js:1:2435)
    at Object.Ge (main.js:1:2432326)
    at Ye (main.js:1:2432480)
    at main.js:1:2450648
    at Tr (main.js:1:2450742)
    at kr (main.js:1:2451156)
    at main.js:1:2456794

Stack trace from non-minified code:
Uncaught (in promise) TypeError: validator.execute is not a function
at validateTutorialStep (TutorialContainer.js:95:1)
at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
at invokeGuardedCallback (react-dom.development.js:4056:1)
at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:4070:1)
at executeDispatch (react-dom.development.js:8243:1)
at processDispatchQueueItemsInOrder (react-dom.development.js:8275:1)
at processDispatchQueue (react-dom.development.js:8288:1)
at dispatchEventsForPlugins (react-dom.development.js:8299:1)
at react-dom.development.js:8508:1


Topshelf executable doesn't start when service is installed with powershell new-service command

We have a bunch of legacy service that we converted to use topshelf.
Our build system uses the new-service powershell command to configure windows services on the target server and topshelf services deployed in this way do not start.  (the exe executes correctly from shell)
Is there a way for topshelf services to start after using the new-service command to install?
It will not be trivial to convert our build system to use topshelf.exe intall method.
Regards
Thomas

NVM,
You can use new-service powershell command if you specify service name as command line parameters.
new-service -Name Stuff -BinaryPathName "service.exe  -displayname Stuff -servicename Stuff


Add support for creating zip files

Basic zip files can be created (or appended to) by supplying the path to a zip file and either paths to existing files or NSData objects along with filenames.

You even added tests! Thanks so much! I'll take a look soon and get this merged. Thanks again!

Thanks so much! I really appreciate it!


Apollo Gradle plugin -- add okbuck support

For OkBuck to work with gradle plugins, you must offer some configuration at plugin evaluation. For example, SQLDelight:
  project.plugins.whenPluginAdded { plugin ->
   ...redacted...
    else if (plugin.class.simpleName == "SqlDelightPlugin") {
        applySqlDelightConfig()
      }
    }
  }

 private void applySqlDelightConfig() {
    project.android.libraryVariants.all {
      Task okbuckTask = project.rootProject.tasks.getByName("okbuck")
      Task sqlDelightTask = project.tasks.getByName(
          "generate${it.name.capitalize()}SqlDelightInterface")
      okbuckTask.dependsOn(sqlDelightTask)
      project.android.sourceSets."${it.name}".java.srcDirs += [sqlDelightTask.outputs.files[0] as String]
    }
  }

This does not work with apollo because there are no apollo tasks on project.tasks when plugins are configured.
I believe this is because we register after project evaluation?:
private void applyApolloPlugin() {
....
project.afterEvaluate {
     project.tasks.create(ApolloCodeGenInstallTask.NAME, ApolloCodeGenInstallTask.class)
     addApolloTasks()
   }
}

whereas sqldelight does it sooner? https://github.com/square/sqldelight/blob/master/sqldelight-gradle-plugin/src/main/kotlin/com/squareup/sqldelight/gradle/SqlDelightPlugin.kt

@marwanad Would you be able to help me with this?

Yeah, the tasks will not be there at the whenPluginAdded check. Since we don't really do any configuration that happens after project evaluation, I moved them outside of the block in #475.
The tasks ':generateApolloClasses', ':generateApolloIR', ':installApolloCodegen' should now be available.

@kageiit you mentioned you knew how this should work, want to chime in?

@BenSchwab You can do it in project.afterEvaluate instead of project.plugins.whenPluginAdded and both the tasks should be created by that point

What @kageiit said and https://github.com/apollographql/apollo-android/pull/475 works for me now. Thanks!


Use gcr.io/distroless/static as base image

          Could we use distroless static `gcr.io/distroless/static` as base image?

Originally posted by @aramase in https://github.com/Azure/rg-cleanup/pull/14#discussion_r1212352619

@marosset tried to do this in #14  but the container group failed to become ready


Document various steps

bots@server1:~/ImagesOfNetwork$ python3 subreddit_setup_and_copy.py
/r/ImagesOfEgypt, skipping creation
imagesofplaces
adding to multireddit
Traceback (most recent call last):
  File "subreddit_setup_and_copy.py", line 114, in main
    ret = whipslaves(reddit_session, base_settings, do_mods, base_mods)
  File "subreddit_setup_and_copy.py", line 43, in whipslaves
    add_to_multi.add_subreddit(subreddit)
  File "<decorator-gen-302>", line 2, in add_subreddit
  File "/usr/local/lib/python3.4/dist-packages/praw/decorators.py", line 271, in wrap
    return function(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/objects.py", line 1669, in add_subreddit
    *args, **kwargs)
  File "<decorator-gen-7>", line 2, in request
  File "/usr/local/lib/python3.4/dist-packages/praw/decorators.py", line 116, in raise_api_exceptions
    return_value = function(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 601, in request
    retry_on_error=retry_on_error, method=method)
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 451, in _request
    response = handle_redirect()
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 432, in handle_redirect
    verify=self.http.validate_certs, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 134, in wrapped
    return function(cls, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 56, in wrapped
    return function(cls, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 102, in request
    allow_redirects=False, verify=verify)
  File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 576, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/requests/adapters.py", line 376, in send
    timeout=timeout
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 559, in urlopen
    body=body, headers=headers)
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 353, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1088, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1121, in _send_request
    self.putheader(hdr, value)
  File "/usr/lib/python3.4/http/client.py", line 1067, in putheader
    value = b'\r\n\t'.join(values)
TypeError: sequence item 0: expected a bytes-like object, NoneType found
subreddit_setup_and_copy.py:121: ResourceWarning: unclosed <ssl.SSLSocket fd=5, family=AddressFamily.AF_INET, type=2049, proto=6, laddr=('<IP_ADDRESS>', 60186), raddr=('<IP_ADDRESS>', 443)>
  traceback.print_exc()
adding to multireddit
Traceback (most recent call last):
  File "subreddit_setup_and_copy.py", line 114, in main
    ret = whipslaves(reddit_session, base_settings, do_mods, base_mods)
  File "subreddit_setup_and_copy.py", line 43, in whipslaves
    add_to_multi.add_subreddit(subreddit)
  File "<decorator-gen-302>", line 2, in add_subreddit
  File "/usr/local/lib/python3.4/dist-packages/praw/decorators.py", line 271, in wrap
    return function(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/objects.py", line 1669, in add_subreddit
    *args, **kwargs)
  File "<decorator-gen-7>", line 2, in request
  File "/usr/local/lib/python3.4/dist-packages/praw/decorators.py", line 116, in raise_api_exceptions
    return_value = function(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 601, in request
    retry_on_error=retry_on_error, method=method)
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 451, in _request
    response = handle_redirect()
  File "/usr/local/lib/python3.4/dist-packages/praw/__init__.py", line 432, in handle_redirect
    verify=self.http.validate_certs, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 134, in wrapped
    return function(cls, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 56, in wrapped
    return function(cls, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/praw/handlers.py", line 102, in request
    allow_redirects=False, verify=verify)
  File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 576, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/requests/adapters.py", line 376, in send
    timeout=timeout
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 559, in urlopen
    body=body, headers=headers)
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 353, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1088, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1121, in _send_request
    self.putheader(hdr, value)
  File "/usr/lib/python3.4/http/client.py", line 1067, in putheader
    value = b'\r\n\t'.join(values)
TypeError: sequence item 0: expected a bytes-like object, NoneType found
subreddit_setup_and_copy.py:121: ResourceWarning: unclosed <ssl.SSLSocket fd=5, family=AddressFamily.AF_INET, type=2049, proto=6, laddr=(snipped), raddr=('snipped')>
  traceback.print_exc()


How to quickly load a SQLite "dump" file?

Original issue: https://github.com/rqlite/rqlite/issues/1016
A rqlite user has reported it takes a long time to load a ~19MB SQL text file, generated by the .dump command. On my machine it takes 13 mins. Most of the time seems to be preparing the statements, detecting the first SQL statement in the SQL dump, and making the rest of the text the "tail", as per here:
https://github.com/mattn/go-sqlite3/blob/master/sqlite3.go#L850
and so on.
rqlite calls this code via ExecContext:
https://github.com/rqlite/rqlite/blob/master/db/db.go#L437
So I suspect all this moving around of memory and text is just slow. Is there a faster way to load a valid SQL file? It takes a couple of seconds if one loads the file directly into a SQLite database.
$ time sqlite3 test.db < av_autoprovisionvalues.sql

real	0m1.931s
user	0m1.773s
sys	0m0.048s

Is there a way to use the go-sqlite3 API for shorter load times? To get the same (or closer) performance as the SQLite command itself?

Can you provide part of the queries? If it contains INSERT statement, it will be heavily. (So you can use begin transaction)

Yes, it has thousands of INSERTs. And because it's generated by SQLite the file starts like so:
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE....

and ends with:
COMMIT;

I think it's the prepare and tail loop in https://github.com/mattn/go-sqlite3/blob/master/sqlite3.go#L850 that takes all the time.

Another possibility is to use the actual SQLite database for this operation, rather than a dump file. Then you can leverage SQLite's backup/restore API, which should be faster.

I could totally do that, would be easy enough to add. Let me try that -- thanks.

Loading the SQLite file directly works great -- load times for this case went from minutes to seconds. Thanks for the suggestion.
https://github.com/rqlite/rqlite/pull/1017


Add Optional --wait argument to promote subcommand

It would be helpful to add an optional --wait argument to the CLI to wait for the promote subcommand so that you don't have to create your own automated logic and looping for waiting for the promotion to have been activated for the specified environment.

This is added.  You can now do a -w or  --wait-for-activate option with promote and on check-promotion-status


Update Contribution Guide

Update the CONTRIBUTE file with details about how one can contribute to this project. I don't need to have it fully done, but it should be enough to point others in the right direction.

Content contribution is the most important one to finish for now, as the other sections can be added later with more feedback. I will split this into 4 separate issues and close this one.

This issue can be closed as it has been superseded with issues: #29, #33, #34, and #35.


esy bootstrap: error: unknown flag `r'

I'm having problems building oni on ubuntu 20.04:
leon@polly:~/src/oni2$ git log |head
commit 40d0d2c11a96b6434fa92bf65f57cfb5b49c3d12
Author: Bryan Phelps<EMAIL_ADDRESS>Date:   Mon Apr 12 12:36:34 2021 -0700

    fix(code-action): Fix a couple bugs around lightbulb+quickfixes (#3396)

    Fix a couple of bugs with the lightbulb showing up when 'quick fixes' are available:

    1) The light bulb would be rendered across all open editors. Scope to just the active editor.
    2) The light bulb would only show up if the fix had associated diagnostics, which some providers don't give. Scope to the current position, in that case.

leon@polly:~/src/oni2$ git s
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

leon@polly:~/src/oni2$ esy bootstrap
error: unknown flag `r'

esy-output.txt

It looks like one ot the build steps is failing somewhere, but its not at all obvious where...
If you run with the verbose flag (-v) then perhaps we will get some more information, though I expect you will be spammed by info with that on.


Added back to home button on contact us page

@PriyaGhosal @samarth-6 please review and merge it give gssoc tag with level 2

@PriyaGhosal please review it

@AsifQamar This has been already resolved .Find another issue or feature to contribute to. Thank you!

@AsifQamar Closed PR by project admin, so no points


space-age: missing type upon exercise download

There is a small bug in the exercise Space Age. When one downloads the problem and tries to test the solution. There is an error:
./cases_test.go:9:14: undefined: Planet
FAIL	space [build failed]

The file cases_test.go shows the following :
package space

// Source: exercism/problem-specifications
// Commit: 28b3dac0 space-age: restrict seconds to fit within 32-bit int range
// Problem Specifications Version: 1.2.0

var testCases = []struct {
	description string
	planet      Planet
	seconds     float64
	expected    float64
}{
	{
		description: "age on Earth",
		planet:      "Earth",
		seconds:<PHONE_NUMBER>,
		expected:    31.69,
	},
	{
		description: "age on Mercury",
		planet:      "Mercury",
		seconds:<PHONE_NUMBER>,
		expected:    280.88,
	},
	{
		description: "age on Venus",
		planet:      "Venus",
		seconds:     189839836,
		expected:    9.78,
	},
	{
		description: "age on Mars",
		planet:      "Mars",
		seconds:<PHONE_NUMBER>,
		expected:    35.88,
	},
	{
		description: "age on Jupiter",
		planet:      "Jupiter",
		seconds:     901876382,
		expected:    2.41,
	},
	{
		description: "age on Saturn",
		planet:      "Saturn",
		seconds:<PHONE_NUMBER>,
		expected:    2.15,
	},
	{
		description: "age on Uranus",
		planet:      "Uranus",
		seconds:<PHONE_NUMBER>,
		expected:    0.46,
	},
	{
		description: "age on Neptune",
		planet:      "Neptune",
		seconds:<PHONE_NUMBER>,
		expected:    0.35,
	},
}

The planet datatype should be string and not Planet. There is no such custom data-type defined.

As for my opinion we shouldn't change planet datatype to string, but simply move 'Planet' type definition to space_age.go file. When one downloads the problem, he also downloads space_age.go with preset type definition, and it will prevent error, mentioned by You

@LDODen converting to string is the most simplest of the solutions. Yes, we can move the definition of Planet type to space_age.go but the I don't think there is anything else to be added to that data-type instead of just a Name identifier.
Either way, this bug is very easy to fix, but not sure, if exercism are actively monitoring this repo. as I pointed this out more than 2 months ago and there has been almost no response/action.

Yes, this is seems as simpliest way, but in this way we should also refactor  example.go, which contains a solution based on Planet type

@LDODen see this line : https://github.com/exercism/go/blob/c545db854be41530ec3f70b29ce3823a08c73000/exercises/space-age/example.go#L4
They've already declared Planet as type string

Sorry, for the late reply here. Maintainers were away, should be more timely responses from now on.
Here, planet type was added, just to make the exercise more difficult. That's why changing type back to string would be moving backwards.
My suggestion is similar to @LDODen but instead of moving, we should copy. Then, while testing stub file is ignored and we have a working implementation to satisfy tests but also users won't see this error message either.
How does it sound? Would you like to send a PR?

Sure. I'll send a PR in a bit.

It will be one type declared twice in one package.

Yes, but while testing stub is ignored. When downloaded, example is ignored so users see only one of them at a time.

While checking https://github.com/exercism/go/pull/1299, saw meetup exercise has also similar issue but it has a comment at least.

resolved by https://github.com/exercism/go/pull/1301


[PolicyRecordingBot] Getting meeting ID

I want to get meeting information by using Get onlineMeeting Graph API  from PolicyRecodingBot.
It seems possible by leveraging OnlineMeetingHelper.cs which is already used by another sample here.
However, I cannot figure out how I may retrieve meeting ID with PoilcyRecordingBot. The other example retrieved from joinCallBody, but PolicyRecordingBot does not use it. CallsOnIncoming handler receives the collection of ICall, but ICall.Call.Resource.MeetingInfo does not have ID field.
Can anyone guide me where I may get meeting ID?

@hohno-panopto did you find an answer on this? I am facing the same issue...

Unfortunately, no.
On Mon, Feb 22, 2021 at 11:21 PM Vassilis Salis<EMAIL_ADDRESS>wrote:

@hohno-panopto https://github.com/hohno-panopto did you find an answer
on this? I am facing the same issue...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/206#issuecomment-783968591,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7QRI6LHYBWATPL46JCH3TTANJO7ANCNFSM4MFFHBVA
.

@zhengni-msft @zihzhan ?

Well, I tried a workaround:

Used GetCallRecord passing the CallChainId, which is available via this.Call.Resource.CallChainId
This returns the JoinWebUrl property
using Graph Beta for GetOnlineMeeting that accepts JoinWebUrl as an argument

Problems are:

That you need to have more permissions (CallRecords.Read.All),
That the CallRecord is available after the bot leaves the meeting - which means that you might need another "background service" to make the actual call and have available data.
Using a beta API

Still looking for a better solution on this...

Hey Vasalis - nice to see you here :)
I have a similar challenge. I'm thinking it's a challenge problem, with bots added by policy especially. They can sit there & record, kick-out/mute people but that's it. It's not "their" meeting so basically can't do much to the meeting itself. I couldn't even get the callRecord with the chain ID because that's only a thing once the call is over.
Anyway, my plans are to have the bot actually create the meeting & invite whoever to it, so we have the same setup but this time not by policy. Meaning they can also chat, they'll have alread the meeting details, and send audio too. That way the bot drives the meeting from the start & also isn't forced into literally every call with anyone in the policy too (which wasn't needed).
It's not particually well explained IMO what the point & limitations of policy bots are. I have similar issues where I need to also do things in the meeting the bot's in, so I'm taking this new approach.
Cheers,
Sam


Support for additional URL formats in object_store for Azure blob

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
In azure storage blobs can be referred to with a URL format like: https://<account>.blob.core.windows.net/<container>/...
Describe the solution you'd like
I would like to be able to use the from_url method on MicrosoftAzureBuilder to construct a MicrosoftAzure instance including the container name directly from a URL in this format.
Describe alternatives you've considered
I currently have built a parser that will do this as an extra layer in my application.
Additional context
None?

label_issue.py automatically added labels {'object-store'} from #5371


Remove Reader::scrach_buffer field + resulting breaking API changes.

PTAL?
This mostly follows what we've discussed in https://github.com/image-rs/image-png/issues/417.
If we merge this, then some coordination may be required for releasing a new version of the png crate and then updating the image crate:

I am happy to volunteer to update the image crate after a new version of the png crate is released.  OTOH, I am not sure how to get notified when this happens?
I am not sure when exactly it would be desirable to release a new version of the png crate.  It may be worth waiting until some additional changes get merged:

additional performance-related improvements (e.g. PRs that stem from the "copy avoidance series of commits")
additional performance-related breaking-changes (e.g. I think that Read => BufRead is on the table - I want to try measuring this after flushing out other changes from the "copy avoidance series of commits")

Hmmm... after having already submitted the PR, I now started to wonder:

Maybe the remaining API should just be called next_row (rather than next_interlaced_row)

Maybe I should simplify the description in CHANGES.md to something like:
  ```
  * Breaking API changes:
     - Removing the `Row` and `InterlacedRow` structs
     - Removing the `Reader::next_interlaced_row` method
     - Changing the signature of the `Reader::next_row` method
  ```

I would like to eventually make this API change, but for now I wonder if it would be simpler to make next_frame call self.next_pass() and self.next_interlaced_row_impl() directly. The scratch buffer variable would still exist, but it would only be allocated/used if the user specifically requested rows one-by-one.

One motivation for the changes in this PR is to improve the performance of image::codecs::png::PngReader which calls into next_row.  Changes to next_frame wouldn't help with that.
It seems that sometimes decoding row-by-row (or at least smaller-than-frame-chunk-by-chunk) may be desirable if pixels needs some kind of post-processing (e.g. applying gamma, alpha premultiplication, etc.) and the user of the png crate wants to do such post-processing while the image data is in L1 cache.  image::codecs::png::PngReader is compatible with that idea, but next_frame would add a considerably larger L1 cache pressure.  ("seems" because I don't have hard data and/or benchmarks to confirm this.  But it does seem like a valid idea. I think.)

Is the main concern the desire to avoid breaking changes?
One way to address this concern may be to instead add a new API (next_row2?) and the (#[deprecated])[https://doc.rust-lang.org/beta/reference/attributes/diagnostics.html#the-deprecated-attribute] attribute to the old APIs (structs and methods).
OTOH, IMO some breaking API changes may be required for performance one way or another.  So maybe another way to proceed is to wait until those other breaking changes have PRs with measurements that show their impact for the noncompressed benches and then land all the breaking changes around the same time.  (For example, I plan to send the Read => BufRead changes after first flushing out 2 less controversial PRs - so, in a week or two maybe, depending on how the other PRs are received :-))

The goal is to bundle all the breaking changes we'd like to make into a single 0.18 release, rather than have a couple breaking releases in rapid succession. But that means that breaking changes will take longer to land than non-breaking changes. So if there are pieces that can be split out, it likely makes sense to merge those first.

The goal is to bundle all the breaking changes we'd like to make into a single 0.18 release, rather than have a couple breaking releases in rapid succession.
...
These changes generally look good to me though, so I'm fine with letting them linger until we're ready to do a breaking release

Ack.  That sounds good and is totally reasonable.
Just as an FYI, let me point out that currently I think that I may want to make the following 3 breaking changes:

This PR (Reader::next_row taking &mut [u8] instead of returning &[u8])
Requiring that the reader passed to the png crate is already BufRead and not just Read (this is in the spirit of copy avoidance but wasn't explicitly covered in my recent measurements).  Like this PR, that other PR will probably also require follow-up changes in the image crate.
Changing ZlibStream::decompress (and ZlibStream::finish_compressed_chunks) so it takes &mut [u8] instead of taking and appending to &mut Vec<u8>.  This has been a part of the copy-avoidance-series-of-commits and has been covered by my recent measurements.  This is technically a breaking API change, but this is a fairly low-level API that I think/hope shouldn't see that much usage (or at least should see less usage than the other changes above).

I think that it's probably desirable to first flush out 3-4 other PRs with non-breaking changes (starting with the noncompressed benchmarks).  Flushing those out will help to highlight/magnify the relative improvement from the breaking changes (at least from the last 2;  the current PR isn't directly covered by the benchmarks in the png crate and I am hesitant to expand the scope/shape of the benchmarks just to justify the PR).

Status update:

I've made the small tweaks that I've listed in https://github.com/image-rs/image-png/pull/421#issuecomment-1789923399
I've put together a PR for another breaking API change (BufRead): https://github.com/image-rs/image-png/pull/427
I am no longer sure if it is desirable to pursue "changing ZlibStream::decompress [...] so it takes &mut [u8] instead of [...] &mut Vec<u8>." (mentioned in https://github.com/image-rs/image-png/pull/421#issuecomment-1792962177 above).  In particular, https://github.com/image-rs/image-png/pull/422#issuecomment-1796868872 shows that avoiding copying of prev can be achieved without this breaking API change.  There may be additional desirable tweaks of ZlibStream, but hopefully they won't require a breaking API change.

@fintelia, can you PTAL again?
Process notes
I see that this PR has been rebased on top of https://github.com/image-rs/image-png/tree/next, but this branch is 24 commits behind https://github.com/image-rs/image-png/tree/master and this makes GitHub is quite confused.  In particular, it is not quite correct that in this PR “anforowicz wants to merge 26 commits” (as GitHub says at the top) - I just want to merge the 2 commits here: https://github.com/image-rs/image-png/compare/master...anforowicz:image-png:scratch-buffer-removal: https://github.com/image-rs/image-png/commit/b7d0c0641c5fb379af265a49b33516da3e08a4dc and https://github.com/image-rs/image-png/commit/29e90cc4ec83ddbbe2286967b12224935c742771. So, maybe you want to rebase on top of the master branch again?
I am also not sure what the right process is for landing breaking API changes.  I went ahead and bumped up the version to 0.18.0 in CHANGE.md and Cargo.toml but please shout if I shouldn’t be doing that just yet.
Performance Impact
Performance of next_row matters mostly in scenarios that require some post-processing (e.g. doing a gamma correction or rgba8=>bgra8 conversion).  Reasons for post-processing after decoding each row (rather than after decoding the whole image) include 1) incremental/progressive/partial decoding scenarios (this matters both for interlaced and non-interlaced images) and 2) desire to do the post-processing while the row pixels are still in L1 cache.  The performance gains are mostly limited to scenarios where post-processing can happen in-place (otherwise, the memory copy would still happen as part of the post-processing) - assuming that rgba8 images can be post-processed in place this covers around 54% (rgba8 images) to 89% (rgba8 + indexed images) of scenarios involving web images (percentages are based on the data here).
This PR adds a benchmark that covers next_row of a generated, non-compressed image (i.e. focusing on parsing and memory copies instead of decompression overhead).  The PR improves the benchmark results by 8-17% (see the commit description for more details).
In theory the changes in this PR can also result in a small performance gain in some non-incremental decoding scenarios in next_frame - avoiding an extra copy of 7th-pass pixels of interlaced images (decoding these pixels directly into the target buffer instead of calling adam7::expand_pass).  I haven’t implemented these changes, because interlaced images seem to only happen in 1-2% of web images (see the data here).
Breaking Changes
At this point this PR is the only breaking change that I plan to do (given that the BufReader-related changes don’t give clear performance gains as discussed elsewhere).  I think this means that the earlier comment “to bundle all the breaking changes” doesn’t apply anymore.
I note that a bit ago the image crate stopped calling the next_row function (see the commit here).  This reduces the impact / scope of the proposed breaking changes (although image is just one crate).
If the breaking API changes are nevertheless concerning, then we can also keep the old APIs (maybe marking them as #[deprecated]) and introduce a separate new API.  If we want to do that, then we’d have to decide what to call the new API:

The old APIs are pub fn next_row(&mut self) -> Result<Option<Row<'_>>, DecodingError> and pub fn next_interlaced_row ….
Maybe the new API can look like pub fn read_row(&mut self, row: &mut [u8]) -> Result<Option<InterlaceInfo>, DecodingError> (i.e. naming it read_row instead of next_row).  I don’t quite like the asymmetry between next_frame and read_row, but this should work.

I'm supportive of this PR, but I'm too burned out right now to review everything and manage a major release. As far as the BufRead changes, the last image crate release did add a BufRead bound for decoders so at least that aspect no longer applies.

I'm supportive of this PR, but I'm too burned out right now to review everything and manage a major release. As far as the BufRead changes, the last image crate release did add a BufRead bound for decoders so at least that aspect no longer applies.

Ack.  I am gradually evolving toward keeping Reader.read_row for now:

This avoids a breaking change.  And even if we wanted to take the breaking changes, it probably would be desirable to initially mark read_row as #[deprecated] and only later (maybe after another major release?) remove it.
Reader.read_row has reasonable performance if the caller unconditionally post-processes and copies (because in this case no memory copy is saved).  And in such a scenario having Reader.read_row is a nice convenience.

So, now I am leaning toward abandoning the current PR and introducing a separate, new API instead in
https://github.com/image-rs/image-png/pull/493.
WDYT?


Permission driven database access

CATEGORY
Choose one

[ ] Bug Fix
[X ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
By default, database list is not permission driven. It shows all databases to all users. This filter allows us to restrict that view. After applying this filter, user will only see the databases that they have
datasource_access permission.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
Tested that the database access is controlled by permission
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

can someone please restart the following build:
https://travis-ci.org/apache/incubator-superset/jobs/529580023

Just did, building...

A similar PR adding this functionality has been merged already.


Feature/allow resource allocation

Proposed changes
Problem: When using autoscaling kubernetes clusters based on resource requests (like Karpenter implemenations or fargate kind of setups), pods will get evicted when the request 0 cpu and memory whilst the node it landed on is strapped for one of those resources, this change will give use the capability to set resource requests & limits in a way users see fit.
Solution: Allow use to set resource values (https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#resource-requests-and-limits-of-pod-and-container)
Testing: Tested by overriding the default clusters and checking in k8s if resource settings where taken over.
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[x] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

 Add capability to set resource requests and limits on nginx-gateway deployment

@anwbtom can you run make generate-helm-docs and commit the changes? That should fix the pipeline

Thanks for the tip @kate-osborn, just ran the command and it only made a change in the readme of the chart.
Hopefully that fixes stuff & things :)


Testing accuracy on the fly during training

Hi @yjxiong
Since I am re-implementing TSN, could you provide the testing accuracy on the fly during training or your training log? So it is much more easier to compare training performance with your original model without evaluating it at last. Thanks a lot!

I suggest you instead compare the final evaluation results to check whether your implementation is correct. The on-the-fly validation only serves for monitoring and they are not run on the exact entire validation set each time.
We have tried implementing TSN with several libraries and the final performance is stable.

@yjxiong Thanks for your reply and your suggestion.  I understand your meaning. However, since I do not achieve your final results, I want to check which part (the training part or the final 10-crop evaluation) may have some bugs in my implementation.
Could you provide a rough number of the accuracy of the on-the-fly validation (1-crop of 3 segments)? Thus I could know about how much can the final 10-crop of 25 segments predict improve over the validation results during training. Thanks a lot!

For RGB with segment number 3 using the bundled Caffe, the on-the-fly number can be between 83% to 85%. For flow, it can also be something between 83-85.
And as I said, this number is highly versatile, which means in different frameworks we observe different ones due to the validation settings. However, the video-level testing performance is quite stable across frameworks.

@yjxiong Thanks a lot for your reply. It helps me a lot. I have another question about the pre-trained model. In order to be the same as your setting, I want to use the same original Inception-BN model which was pre-trained on ImageNet. Did you use the public Inception-BN re-implemented model? If so, could you provide the link? Many thanks for your help!

As we know, there is no public implementation of BN-inception that matches the originally reported performance. The one we released as the RGB initialization model is our own implementation which achieves the reported accuracy. You can use it as you will.

Thanks for your reply. @yjxiong


AND | OR rule in adjust -> when parameter

I am trying to ensure the test will be running only for relevant distros with the help of the following config.
summary: check-custom-repo
tag+:
  - centos7
  - centos8
  - oracle7
  - oracle8
  - check-custom-repo
adjust:
  enabled: false
  when: >
    distro != centos-7 or
    distro != centos-8 or
    distro != oracle-7 or
    distro != oracle-8

However, this definition is not working as expected and the test is filtered out all the time. i was looking to https://fmf.readthedocs.io/en/latest/context.html#syntax and from my point of view the syntax complies. However, if I run the following command:
tmt --context distro=centos-7 run plan --name /plans/integration/check-custom-repo/vm_centos8/good -vvvddd

no tests selected

You should be using AND imho. For your context (--context distro=centos-7) first matching expression is distro != centos-8 so whole when is True and as such enabled: False is applied.

@lukaszachy you are right, than kyou


Specify a pip version for travis.

I am merging this since travis can successfully install the required packages through peep.


[POC] react navigation ios

Description
This PR is a demonstration of the steps needed to consolidate the navigation infrastructure across iOS and Android.
This gets it about 90% of the way there, there's some tricky infra issues to overcome:

if we use createNativeStackNavigator (i.e. react-native-screens) for the outer modal stack, then we run into a couple of serious issues:

touches don't work on full screen modals (they do if you set the modal type to 'transparent full screen' but that's not an option on iOS 12). I debugged this for a while but failed to pinpoint where the touches were being lost.
safe area insets were a bit glitchy.

Meanwhile, using the regular createStackNavigator for the outer modal stack (as I left it in this PR) has a couple of issues

safe area insets are not propagated to native view controllers embedded in the modal (e.g. as needed by live auctions)
there is no 'page sheet' style modal, so all modals would be full screen.

Also I just noticed that this PR fails to retain the scrollToTop functionality, but that should be easy enough to reinstate.

Closing PR for inactivity - please feel free to reopen it if needed 👌 Thanks David and Brian for working on this


Pasting is very slow with big clipboards

nano is a workaround, in case cannot use xclip -se c -o due to SSH for instance, as far as I remember.
Steps to reproduce
Not read.
Expected behaviour
Not read.
Version of Vim
Not read.
Environment
Not read.
Logs and stack traces
No response

I have in mind 322,411 bytes according to wc -c.


AssertionError when .sass-lint.yml or package.json missing

I would expect sass-lint to work by just running:
$ sass-lint

Or at least it should provide a helpful error message describing which required options I'm missing. Instead it crashes:
assert.js:89
  throw new assert.AssertionError({
  ^
AssertionError: missing path
    at Module.require (module.js:364:3)
    at require (module.js:385:17)
    at module.exports (/usr/local/lib/node_modules/sass-lint/lib/config.js:73:12)
    at Function.sassLint.getConfig (/usr/local/lib/node_modules/sass-lint/index.js:25:10)
    at Function.sassLint.lintFiles (/usr/local/lib/node_modules/sass-lint/index.js:166:18)
    at detectPattern (/usr/local/lib/node_modules/sass-lint/bin/sass-lint.js:16:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/sass-lint/bin/sass-lint.js:87:3)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)

So I follow the manual and create .sass-lint.yml and run it again:
$ sass-lint

Again it crashes with the same stack trace as before.
So I go and look at this config.js file at line 73. Turns out it tries to read in package.json. Apparently that's a hidden feature implemented in #47, but documented nowhere.
So I create an empty package.json file consisting of just {} to please sass-lint.
Now finally I'm able to run it:
$ sass-lint

But I see no errors, it appears to lint just fine, although I purposefully created a very buggy SCSS file. OK, I'll try to introduce a syntax error. I'll run the linter again, and it crashes:
/usr/local/lib/node_modules/sass-lint/index.js:250
    throw new Error(errorCount.count + ' errors were detected in \n- ' + errorCount.files.join('\n- '));
    ^

Error: 1 errors were detected in
- test.scss
    at Function.sassLint.failOnError (/usr/local/lib/node_modules/sass-lint/index.js:250:11)
    at detectPattern (/usr/local/lib/node_modules/sass-lint/bin/sass-lint.js:27:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/sass-lint/bin/sass-lint.js:87:3)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:134:18)
    at node.js:961:3

That error doesn't really help me either. I search through the issues in this repository, and find #500, from where I finally learn that I need to run:
$ sass-lint --no-exit --verbose

The CLI docs don't explain any of this. There's no way I would have guessed that I need to use --verbose option. Issue #500 mentions that there are plans to improve this in 2.0, but I really suggest documenting the current behavior.
Using sass-lint 1.5.1

Hi @nene I completely agree with you. The CLI and sass-lint itself had grown at a very quick pace and the amount of usage it was getting so early on kind of took us by surprise, in our efforts to get as much functionality and usability into the tool as soon as possible when we started this I think we kind of neglected some of the documentation and at the same time maybe took some decisions regarding the implementation which we now would change.
The CLI itself is due an overhaul for sass-lint v2 but in the meantime I've updated our README in PR #586  to provide a little more information straight off the bat about how to use the CLI.
I've also put PR #588 in to fix the assertion error you see if not specifying a config file. Both of these we've known about for a while but you know time is one of those things we struggle to find recently!
Anyway, hopefully the changes should see issues like yours become less frustrating from a user point of view and with the added test for this missing config error im sure we shouldn't see that raise its head again.
Thanks

Thumbs up for all the effort. Looking forward to using sass-lint when new release with all the fixes from gonzales gets out.

I'm going to close this as the bugs have now been fixed and the README has hopefully improved the way this is documented, when version 2 comes into sight though then this will form part of our thinking.


Rep001 1 (rez-test improvements)

This updates rez-test behaviour wrt https://github.com/nerdvegas/rez/issues/665.
Not all of the REP is addressed here. This PR includes:

addition of run_on tests field (however this is not fully acted on yet - pre_release does nothing atm)
Addition of --inplace option, to run a test in the current env (if necessary requirements are present)
Better handling of variant iteration (there was none previously), and a new on_variants tests field to give granular control over this.
Updated wiki docs wrt tests package attrib.

Note: It would also make sense to have tests for the PackageTestRunner class. However I'd like to hold off until we port to pytest - I think it's going to be significantly simpler to do something like have a fixture for installing a set of packages into a fake fs. The way packages are built and tested on currently is haphazard and I'd rather not increase our technical debt for the sake of this fairly non-critical part of the code. https://github.com/nerdvegas/rez/issues/808.

"""Should we add support for doing rez-test . or rez-test /path/to/package (can be useful for CI) in this PR?"""
I wanted to keep that as a separate PR because I think there are some outstanding questions that need to be answered, so I wanted to wait til we get consensus. See https://github.com/nerdvegas/rez/pull/759
"""Are you planning to add a variant selection flag to the CLI?"""
Yes. I didn't want this PR to be too large, so was leaving this for next. Will also add the --interactive flag in this PR.

Issues addressed in https://github.com/nerdvegas/rez/pull/811 (fixing them here will just cause conflicts).
If we're reasonably happy with what's here, I'd like to merge and roll further reviewing into #811
.

I'll reply to your comments when I get at home (so 2 hours).

Ok, I think after I make these changes we're on the same page. It's gonna be a lot simpler to do this over in https://github.com/nerdvegas/rez/pull/811. Let's take the convo over there, and when that's ready, I'll do both merges into the same release.

I also think we are now on the same page. So if you feel like it's going to be easier to do the changes in #811, I'm fine with that.

Sounds good. I should have these changes in #811 within the next 24 hours.
A
On Wed, Dec 4, 2019 at 3:50 PM Jean-Christophe Morin <
<EMAIL_ADDRESS>wrote:

I also think we are now on the same page. So if you feel like it's going
to be easier to do the changes in #811
https://github.com/nerdvegas/rez/pull/811, I'm fine with that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/pull/807?email_source=notifications&email_token=AAMOUSUN2SMXW26X4LD32QTQW4ZKZA5CNFSM4JP4E56KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF3XBCY#issuecomment-561475723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSQ3ZNWKASPVFRZCOWLQW4ZKZANCNFSM4JP4E56A
.


remove nested parallel, run multi-thread without omp env

current nested loop needs a OMP_NESTED=true environment variable, this patch tries to get rid of it.
Basically removed the nested omp parallel, which I believe can improve readability as well.
I used the std::thread to create monitoring job.
partly solved https://github.com/wangtzh/pibench/issues/8

no measurable performance change based on my experiments

Also moved the  auto value_ptr = value_generator_.next(); to the places they're really used.

Relevant changes already merged.


musllinux wheel

Would you consider shipping a musllinux wheel? This is possible since PEP 656.
It would be great to have the wheel on PyPI for Docker containers running Alpine, which some people use in their CI/CD.
Thank you!

With 0.21.2, wheels are now provided for musllinux.

Merci!


SEO

Good morning,
can we just agree to Krzysztof’s idea regarding the issue with the pull request and implement SEO changes on to the site?
Kind regards
Filip Kopijer
Digital Marketing Manager
@.***
Przedsiębiorstwo Farmaceutyczne LEK-AM Sp. z o.o.
Biuro Handlowe
Al. Jana Pawła II 80, 00-175 Warszawa
<EMAIL_ADDRESS>Kom: +48728432939

From: Krzysztof Hankiewicz @.>
Sent: Wednesday, June 7, 2023 9:44 PM
To: kjhank/zatogrip @.>
Cc: Filip Kopijer @.>; Comment @.>
Subject: Re: [kjhank/zatogrip] SEO (PR #42)
Nie otrzymujesz często wiadomości e-mail z adresu<EMAIL_ADDRESS>Dowiedz się, dlaczego jest to ważnehttps://aka.ms/LearnAboutSenderIdentification
@kjhank commented on this pull request.

In src/components/CookiesAlert/CookiesAlert.jshttps://github.com/kjhank/zatogrip/pull/42#discussion_r1222080057:

@@ -20,9 +18,9 @@ export const CookiesAlert = ({

content, confirmCookies, isVisible,
}) => (

Sure, when the code is on the client's repo, they'll have a say in regards to code quality. Until then - DRYhttps://en.wikipedia.org/wiki/Don't_repeat_yourself.
—
Reply to this email directly, view it on GitHubhttps://github.com/kjhank/zatogrip/pull/42#discussion_r1222080057, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAMM4L3FPVXEYJVAIGUXNRLXKDKY5ANCNFSM6AAAAAAY52FAIY.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>


Add travis CI to the repo

This repo should contain a CI which would be helpful to see if the tests are passing.
ref: https://github.com/retr0h/git-url-parse/pull/4#issuecomment-379267967

Good suggestion.


"Directory" resource schema: needed to enable the CRUD of folders and subfolders of resources [Placeholder]

This is a placeholder until I can write more about this.  This is not a EDV Kernel capability. It can wait.

This raises the question; are EDV's filesystems or databases?

I believe EDVs will become a fundamental component of the Trusted Digital Web and that there should not be any unnecessary restrictions.
That is, like TCP-IP, the spec needs to be compatible with the #OpenToInnovation principle: https://hyperonomy.com/2019/03/12/internet-protocols-and-standards-not-only-need-to-be-open-but-more-importantly-open-to-innovation/
The short answer is both or what you want them to be.