Update CUDA Array Interface to v3 - Part 2

Follow up of #4357 and #4322. This PR should not be backported.
Now that we support PTDS (#4322), we should detect if it's in use before exporting (context: https://github.com/cupy/cupy/pull/4357#issuecomment-735852102). The test suite is updated accordingly. One of the main focus is to ensure the tests pass regardless of the value of the env var CUPY_CUDA_PER_THREAD_DEFAULT_STREAM (verified locally).
This PR also adds an extra safe for HIP following #4651: On HIP, CUPY_CUDA_PER_THREAD_DEFAULT_STREAM should be ignored as PTDS is not supported.
cc: @pentschev

Jenkins, test this please

Jenkins CI test (for commit b35f3f83cd3dc10c76803097a5fa26c10765e360, target branch master) failed with status FAILURE.

Looks like the failure will be fixed in #4648.

Thanks @pentschev! No worries, this was on my todo list anyway. Was just waiting for PTDS to go in.

Jenkins, test this please

Jenkins CI test (for commit b35f3f83cd3dc10c76803097a5fa26c10765e360, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit b35f3f83cd3dc10c76803097a5fa26c10765e360, target branch master) succeeded!

@emcastillo PTAL.
Jenkins, test this please

Jenkins CI test (for commit 7a938a84c8d18f8dae580d4b4345bcb3bb718f34, target branch master) succeeded!

Much cleaner, Thanks!!


Reduce line length of Fira Mono

4 Month later and I just realized the line length is off. :hankey:
This PR will increase the padding to reduce the characters per line to around 60.

Thanks!


Can't add Intl (icu) support to nodejs.

Issue description
I tried to build nodejs with Intl/icu support.
I tried to let it download icu during the configure phase which failed. I suppose network requests are being blocked because they are side effects.
I also tried importing icu and using this one in configure, but that also failed because of weird configure flags that where generated (shared-icu)
Steps to reproduce
Download ICU
Use this commit. This branch
System ICU
Use this commit. This branch.
Technical details

System: 16.09pre89269.8512747 (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: "16.09pre89269.8512747"

Sorry that there was no answer. Were you able to solve your problem?

Nope, I gave up and did it in a docker container instead, and eventually I went to another OS :/
Feel free to close this or leave it open if ICU is something you want to have added to the node package :)

Thanks for the quick response. NixOS got a lot cooler in the meantime, maybe it’s worth a second try? :)

I'll look into it :)


switching to using findup-sync to find local node_modules

it works in more contexts, it finds the closest node_modules directory up the directory tree.
When integrating meta with microsvc, it was failing to find the installed plugins otherwise.

published!

curious what the directory structure looked like. if the system directory is the meta repo, I would imagine it should all be fine. if the system is a child directory of the meta repo and you want to be able to execute commands from within a child dir, perhaps that would be a prob.

I'd installed it as a dependency to microsvc and was running it as exec(__dirname + '/node_modules/.bin/meta init', ...)


Add a pre-push hook

⚠ This PR depends on changes that will get introduced with #1298

Add a pre-push hook to run the unit test before pushing stuff to origin.

mesosphere-ci retest this please

Looks great, I am OK with this, but it takes an awfully long time on every push.
My concern is that sooner or later, people will start using skip validation...

@orlandohohmeier can we close this PR now?

@MatApple I'm fine with closing it, but would vote to merge it and risk that people will start skipping the validation (--no-verify) as running it every now and then is already better than never.
We also have the commitment to improve the test performance which will improve the pre-push performance as well...

I'm with you on that @orlandohohmeier - thought since https://github.com/dcos/dcos-ui/issues/1340 merged we are good. But I think it's good to have this as too. We can at least trial it to see if it isn't too disruptive.

@MatApple @wavesoft There is a rather hacky way to get the base branch which we then could us to only test "changed" files..
base_branch=$(git show-branch | sed "s/].*//" | grep "\*" |
  grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -n1 | sed "s/^.*\[//")

Works for me! Hacky is Ok here :)

@orlandohohmeier let's rebase and merge it!

Rebased, tested and labelled!


Order Columns by relational JSON data field

Summary of problem or feature request
First of all this datatables plugin is amazing. I love the service approach. But I ran into a problem with relational data and ordering. I have a JSON field in a relational table I'm trying to get the English title from. Everything works fine, but it's not possible to order the table, because the orderColumn method only searches in fields of the parent table. I'll give you a quick example.
Code snippet of problem
$query = Rating::with(['company' => function($query) {
            $query->select(['id', 'title']);
        }])->select(['ratings.id', 'ratings.company_id']);

$this->datatables
            ->eloquent($query)
            ->orderColumn('company.title', 'company.title->"$.en" $1')
            ->make(true);

This results in Unknown column 'company.title' in 'order clause' because of the select from `ratings` order by company.title->"$.de" In my option the order query should query the relational table(s), too.
@yajra Any idea how to solve this?
System details

Operating System: OSX (Laravel Valet)
PHP Version: 7.0
Laravel Version: v5.3.21
Laravel-Datatables Version: v6.21.1

FYI: I figured out how to solve this! It's pretty simple and doesn't need a orderColumn() method call. Simply adapt the column definition like this:
['data' => 'company.title', 'name' => 'company.title->en', 'title' => 'Company'],
...

And change the eager loading query like this:
$query->select(['id', 'title->en as title']);

And that's it!


Add the js.special package with delete, debugger and globalThis.

Spawned from https://github.com/scala-js/scala-js/pull/2934#discussion_r118822237, backported to 0.6.x so that it is possible to write codebases cross-compiling between 0.6.x and 1.x.
The js.special._ name can still be debated ;)

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4004/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5304/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4005/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5305/
Test PASSed.


implement microtransactions

each part of the brower (tabs, bookmarks, history, etc) should cost $5 USD

*each

Make it a loot box by paying $5 to have a wheel spin and whatever it lands in is what you unlock, make sure it just misses the item you want

make it so you also have to pay to buy the microtransctions

PissandshittEAum

5$ per new Tab sounds like an infinitemoney-glitch


Add command-line switch to enable asserts in release mode

building with scons --assert ... will not define NDEBUG. This enables asserts.
@HowardHinnant @ximinez

Current coverage is 68.15%

Merging #1608 into develop will not affect coverage as of f078540

@@            develop   #1608   diff @@
=======================================
  Files           908     908
  Stmts         67295   67295
  Branches          0       0
  Methods           0       0
=======================================
+ Hit           45862   45868     +6
  Partial           0       0
+ Missed        21433   21427     -6

Review entire Coverage Diff as of f078540

Powered by Codecov. Updated on successful CI builds.

Looks good to me.  :+1:  Though I can't explain the travis failure.  Not sure if it is spurious or not.

Observation: a failed assert in release mode in Windows prints the same "Assertion failed" message to the console, but does not pop up the abort/retry/ignore dialog - it just fails. This is almost preferable. :)
Changes look good, and may help me optimize my local testing. :+1:


chore(main): release 2.1.2

:robot: I have created a release beep boop
2.1.2 (2024-11-10)
Bug Fixes

Convert tailwind config to ES module (#42) (550e79b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aimeerivers/watchthis-home-service/releases/tag/v2.1.2 :sunflower:


Don't use GetComponents if firmware doesn't support it

Related to https://github.com/home-assistant/core/issues/123440

It's not ready yet, I'll test the change with the old firmware in the evening.


Changelog

It's hard to see the what's changed from the commit log. I saw again there is a new major version. Is there any BC? The supported versions for browsers changed?

it was due to a getStats change, see https://groups.google.com/forum/#!topic/discuss-webrtc/OXqm0tjg8hs


areas of developer interests

Regarding our recent conversation here https://github.com/joemasilotti/railsdevs.com/issues/45 I suggested to implement something like limited badges, that developers can choose
Additionally, I think it might be useful to add some preferences between the two options, it can help to better understand developer preferences.
For example:
ruby - other backend languages
rails way - dry-rb
I don't know maybe developer can set some percentage proportion 30/70 or 50/50 or something like this
It can helps employees to choose developers that better match their project conditions. For example, it's good for big projects that currently rewriting their existing monoliths to microservices with golang backend language, that your future ruby developer has some interest in golang. And vice versa for startups it's not valuable if the developer starts to push founders to try any other technology only because he has an interest in it.

Oh, interesting idea! I've never seen a sliding scale like that for preferences.
In theory, this could be a lot of fun. But in practice, I worry that a developer might be limiting themselves too much by sliding that scale too far. For example, I strongly prefer minitest over RSpec, so I would set it to 100%. But if a potential client was using RSpec I wouldn't say no, you know?
Instead, I'd rather we add a set list of tags/interests/expertise. Then, each developer can show 3 (maybe 5?) of these on their profile. That limits a developer to choosing the ones that make the most sense for them. Some examples can include React, Hotwire, TDD, minitest, Heroku, AWS, Tailwind CSS, etc.

I think it makes sense to add a hint with the explanation that this is not an overall developer opinion, but the willingness to work with technology where 0 - I will never work with that technology for any money, 100 - I'll very like(want to try technology) and ready to start work asap. For me, personally, it will be interesting to see this combats stats, I think results can be an argument in many of holly wars 😄
Interests in technologies is cool too, but this idea is not so fresh, as I know linkedin has something like this, and I think it will be interesting only in limited size and maybe it should be not technologies, but more common things as directions for career growth like ui/ux/frontend, infrastructure/devops, oss, management, high load

Hey @briu, if you're still interested in this can you please open an Ideas discussion?
I'm trying to keep Issues for bug reports and work-in-progress tracking. Thanks!


Creating a window causes blanking of Firefox and KDE taskbar resize

Hi!
I have this weird bug with neovide, which I have reduced to happen on Skulpin window creation. A minimized repro is available at https://github.com/lf-/skulpin-repro
The source is reproduced below, run with the master version of Skulpin, with the skulpin_sdl2 feature.
use skulpin::sdl2;
use std::thread::sleep;
use std::time::Duration;

fn main() {
    let context = sdl2::init().expect("Failed to initialize sdl2");
    let video_subsystem = context
        .video()
        .expect("Failed to create sdl video subsystem");

    let mut sdl_window = video_subsystem
        .window("Neovide", 300, 300)
        .build()
        .expect("Failed to create window");
    sleep(Duration::from_secs(20));
    return;
}

Environment infos:
dev/neovide - [main] » pacman -Q linux nvidia xorg-server firefox
linux 5.10.10.arch1-1
nvidia 460.39-1
xorg-server 1.20.10-3
firefox 85.0-1

I am on KDE in X11 mode on Arch Linux. Nothing in dmesg/Xorg logs of interest. GPU is a GTX 1060 6GB.
Here's a video of this strangeness, with neovide, but it also happens with the repro above:
https://user-images.githubusercontent.com/6652840/106874983-0a0c5600-668b-11eb-8c64-bed27f920010.mp4
Please let me know if there is anything I can do to help debug this.

Sorry for bothering you! This is in fact an SDL bug reproducible with a simple C program even. I'm going to see if I can find it upstream.


Label JS property crashes when switching from value to JS

Steps to reproduce the behavior:

Drag and drop a buttonGroup onto your form
Click on 'buttonGroup' and navigate to the properties panel
Scroll down to and click on 'Customize Button Group'
Click on 'Add Group' or 'Add New Item'
Afterwards, click on 'Label' JS option either on group or new item option
Actual Results: The component crashes

NB: This should be fixed globally where the button group is utilised
Expected behavior
The JS should switch successfully without crashing the component

We'll use this card to list all the properties that are crashing

Tab pane title
Wizard Step title
ButtonGroup Label (group and item)

With the current changes, the entire page crashes after clicking the JS option on the components mentioned above. Here's a URL: https://github.com/shesha-io/shesha-framework/issues/1652


Add support for sending to threads

Here is a PR to add support for sending a stream of output to a threaded message.
It makes use of the --comment option for the initial message (or "Slackcat Stream Output" if comment is not specified)
For #84

merged; thanks @ArcticSnowman !


Set-SPProjectPermissionMode : A parameter cannot be found that matches parameter name 'AdministratorAccount'.

Examples show using -AdministratorAccount, but this is not a valid parameter, confirmed by testing the command with this parameter on SharePoint 2016 farm with Project Server Service App. Please correct the document by removing -AdministratorAccount parameter from the examples.

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

ID: 04a0d8f1-c420-9cb6-6e2a-6a55338028d1
Version Independent ID: 35bad0fb-a392-8b48-7b23-ffcb3298b46c
Content: Set-SPProjectPermissionMode (sharepoint-server)
Content Source: sharepoint/sharepoint-ps/sharepoint-server/Set-SPProjectPermissionMode.md
Product: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

@yogkumgit in 2016/2019 (do not have 2013 to test with), the parameter -AdministratorAccount contoso\John.Woods does not exist, it can be removed from the example.

Hello @SharePointBlackBelt Vincent 👍 Thanks for noticing this. Created a pull request to correct the examples.

@get-itips  Thank you very much for the contribution and updating the documentation with PR. @SharePointBlackBelt Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Midnight trains

It seems that after or around midnight, all trains appear as not having left their station. I need to look into this.

I might have found the issue, which is the use of second past midnight when calculating timestamps. This could be resolved by exposing the timestamps as UTC timestamps


Chrome plugin mode not support

My index.html  is:

{{name}}

new Vue({
 el: '#app',
 data: {
   name: "hxh"
 }
})

I can run this directly in browser.
Now I am developing a chrome plugin,and I use it:
"chrome_url_overrides": {
  "newtab": "index.html"
}

but this not work,just show:

So, is vue.js use some feature that not supported in chrome plugin mode?

Are you using CSP version?

See above - you need to use the CSP build for Chrome apps.

Thanks


Tuya app Closes when scanning QR code

Description
No matter what i do after i put my user code in and scan qr code with tuya app. Tuya app on phone immediately crashes. Keep in mind i have already added 21 devices using the exact same procedure.
Steps to reproduce

Go to tuya local.
Add device
input user code
scan qr code.

Expected behaviour
I expect the tuya app to scan qr code and add devices i have synced to app.
Additional context
No response
Confirmation

[X] I am sure this is a bug or improvement, that is well enough described that it can be implemented.

[ ] If this is for a specific device, the device config is mentioned above, or diagnostics are included.

[ ] Log messages or diagnostics relevant to the issue are included.

[X] This is not requesting addition of a new device.

I am not responsible for the Tuya app.


[HUDI-4952] Fixing reading from metadata table when there are no inflight commits

Change Logs
When metadata table is just getting initialized, but first commit is not yet fully complete(or lets say metadata initialization failed mid-way), reading from metadata table could fail w/ the stacktrace posted in the linked jira. Fixing the read of hudi table to fallback to FS based listing if FILES partition in metadata table if not yet ready to serve data.
Also, if user sets "hoodie.metadata.enable" = true while querying, even if metadata table is not available, we try to fetch from metadata table. Have fixed the same in this patch as well.
Impact
Users should not see any failures or data loss while reading from hudi table if metadata table initialization is happening or if it fails mid-way.
**Risk level: low **
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

addressed all comments. will merge it in once CI is green


Fetch stream should return Event wrapper objects

#291
Renamed Body to Data to better reflect mt_events column name.
Also fixed storyteller tests.

Got it w/ a rebase.


Actually logs LogMessage request from plugins

Found while trying to debug plugins. Will help with that significantly if we can have the logs.
Signed-off-by: Hanif Ariffin<EMAIL_ADDRESS>
[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

this should include plugin in target

No idea what that means :3?


add initial checkbox for point rendering

Work for PR #123 , PR #122 .

Create a checkbox to indicate whether to render the points or not. When user checks to not display the points, the query to fetch the 100,000 points will not be sent to the server (#123)
In display mode, when there are more than 100,000 points to be rendered, do not render the points anymore (#122)

Merge for continuous development


stringArray not respected in influx v1 auth create

Steps to reproduce:

create buckets
use influx v1 auth create command to add permissions to these buckets (note that multiple buckets were added so stringArray for --write-bucket and --read-bucket should be respected)

Expected behavior:
User should have access to all buckets
Actual behavior:
User have access only to last bucket on list
Environment info:

System info: Linux 5.4.0-1059-aws x86_64
InfluxDB version: Influx CLI 2.2.1 (git: 31ac783) build_date: 2021-11-09T21:24:22Z

Config:
Copy any non-default config values here or attach the full config as a gist or file.

Logs:
user@host:~$ influx v1 auth create \

--write-bucket 18339452dd466af8
--write-bucket fe5e0d6e35b07081
--read-bucket 18339452dd466af8
--read-bucket fe5e0d6e35b07081
--org=org --username=username --password=password
ID			Description	Username	v2 User Name	v2 User ID		Permissions
08873a54a5fae000			username		admin		078161444a0e3000	[read:orgs/c3dba96725d43fe4/buckets/fe5e0d6e35b07081 read:orgs/c3dba96725d43fe4/buckets/fe5e0d6e35b07081 write:orgs/c3dba96725d43fe4/buckets/fe5e0d6e35b07081 write:orgs/c3dba96725d43fe4/buckets/fe5e0d6e35b07081]
user@host:~$

Duplicate https://github.com/influxdata/influx-cli/issues/327, fixed in https://github.com/influxdata/influx-cli/pull/328/


Difference between 'ludwig predict' and 'ludwig serve'

Description of the bug
Hello,
I find an issue with the contribution serve.py.
I tried to use 'ludwig serve' with a python client to send data to a trained model but I notice a difference if I send a csv file to 'ludwig predict' again sending file to 'ludwig serve' through python client.
After investigation, I deduce that the problem is due to a wrong managing of null input field.
Basically, 'Ludwig Serve' requiered all input features (function convert_input from serve.py) , so you need to define all input features inside the client.
But convert_input() not allow to retrieve None data (None / "" / '').
Is it possible to manage empty data into convert_input ? Or to add a new feature in serve.py in order to enable to request the REST API directly with a json ? ( Maybe we could protect the input data with a serializer construct with pydentic build by using input_features )
To Reproduce

Load your model:
ludwig serve --model_path ../../ --port 5000

Request the server with a client:

Python client which send text data to ludwig serve
import requests
file={
'some input parameters': (None, 'some text data'),
'some none imput parameters': (None, ''),
'some none imput parameters': (None, None), # Raise an error on client side
'some none imput parameters': None, # Raise an error on client side
}
r = requests.post(url, files=file)
print(r.json())
Environment

OS: Windows 10 Pro
Python version: 3.6.8
Ludwig version: 0.2.1 & <IP_ADDRESS>

#Additional context
In addition, find below my json request.body json parser:
Initial function
@app.post('/predict')
async def predict(request: Request):
form = await request.form()
files, entry = convert_input(form)
I test to add a new function to serve.py which retrieve json directly from body request (Json allow safely to initialize None field)
This different approach produce the same results as 'ludwig predict'
import json
@app.post('/predict_json')
async def predict_json(request: Request):
entry = await request.body()
entry = json.loads(entry.decode())

@myzarak thanksfor posting this, let me try to undesrand better the problem.
First of all, why do you want to send None?
Second, what is the difference in terms of outputs from the server and by running predict? Can you provide a specific example that I can reproduce?
In general, all lists associated with all input fields must contain the same number of values, so your example
 'some none imput parameters': None, # Raise an error on client side

is wrong, but in the other cases, where the length is correct, I understand that there is a problem with those too if they contain None, is this correct?
Again a completely reproducible example will enable me to look into this. Please provide code / data/ command / yaml / pretrained model for me to test. If the data or the model cannot be shares, you can use the script in `data/dataset_synthesizer.py to generate synthetic data.

@w4nderlust
Thank you for the answer.
Your right, due to my company policy I couldn't share data. I will try to send you fastly synthetic data and model to reproduce.
To respond to your questions:
When you train a model which have to process text, the text data is provide to ludwig inside a csv file. If one cell of the csv file is empty, the dataframe generate by ludwig return NaN value (equivalent to None) for the empty cells. That's not a problem, it's just the behavior.
But, with the REST Api, i don't want to lose time to put my input data vector inside a binary csv which one should be save temporarly by ludwig and process after to construct a dataframe. So, I try to send directly my input data. In that specific case, on the client side, it's seems to be not possible to send empty data (like None), I could only send blank (like ""). But, if I display the dataframe build by ludwig, I notice that the only difference between the two methods is  the  NaN/Blank cells.
So, my first approach should be to try to find a solution which allow the client to send 1 None field (Field is define with None value) without success ( I spare a very lot's of time on this question without finding a solution ).
My second approach should be to write another ludwig REST Api input (called predic_json) which received not a files, but a json ( which allow to send None data. ) and this function returned to me exactly the same result like a standard predict with the csv file.
In terms of results:
ludwig predict with csv:
{'tag_predictions': 'CLASS_1', 'tag_probability': 0.532364}
ludwig serve with manual input data:
{'tag_predictions': 'undefined', 'tag_probability': 0.5043553113937378}
ludwig serve with custom json function:
{'tag_predictions': 'CLASS_1', 'tag_probability': 0.532364}

Thanks for the additional details, we'll look into it!
@johnwahba maybe you can help on this?

@myzarak if you can provide a synthetic model, a curl that repros, and what you want it to provide, that'll be ideal. :)

@myzarak do you have any update for us? can you provide a reproducible example? Even a manually defined 2 lines csv would suffice, but without being able to reproduce the issue we won't be able to solve it.

I also improved the test of the server to make sure that the outputs from it are the same you obtain from a local model: https://github.com/uber/ludwig/commit/e576bcaf331ce34d8569197ad9fc7c0eab4a7d0f
I would be happy to include tests for corner cases with None inside but I need an example of that.

Closing due to staleness. I believe the recent changes for v0.3 solved the issue, but if not please post again here and i will be happy to fix any issue.


connection and cursor in a with block

I wanted to use a pymapd connection in a python with block, but found that __enter__ opens a cursor.  It would be useful if it returned self.  That way, I could write:
with pymap.connect(...) as c:
    print(type(c))
    print(c.get_tables())

The above fails because c is a cursor so doesn't have get_tables.
This also fails because Cursor.__enter__ does pass instead of return self.
with pymap.connect(...).cursor() as c:
    print(type(c))
    print(c.execute('select count(*) from flights').fetchall())

https://github.com/omnisci/pymapd/blob/0ffc1afd42aa4aa13550580a5065f0baa86ad372/pymapd/connection.py#L217
https://github.com/omnisci/pymapd/blob/0ffc1afd42aa4aa13550580a5065f0baa86ad372/pymapd/cursor.py#L26
Let me know if you agree and I'll submit a patch.

I believe the standard for context managers specifies that it's a cursor, so I'm not sure we can change this and still be DBI compliant. Let me search a bit.

PEP 343 is the best reference I can find so far: https://docs.python.org/2.5/whatsnew/pep-343.html

The enter() method is pretty easy, having only to start a new transaction. For this application the resulting cursor object would be a useful result, so the method will return it. The user can then add as cursor to their 'with' statement to bind the cursor to a variable name.
class DatabaseConnection:
...
def enter (self):
# Code to start a new transaction
cursor = self.cursor()
return cursor

I get the feeling that either DBI or SQLAlchemy expects that __enter__() into a Connection returns a Cursor, since the pattern would be running some statements and committing them if they are successful.
Perhaps the best thing would be to try to change this to the behavior you want, then see if you can do the following:
from pymapd import connect
import pandas as pd

conn = connect(...)
df = pd.read_sql("select * from table", conn)

If that pandas code still works, then I'd be okay with changing the behavior (though, we should ask Quansight as well to understand what Ibis looks for)

Closed by #237


Remove a specific tag from many | Enhancement

I have lots of images of people in crowded places but with lot of false positives. Is it possible to remove specific rectangles by clicking the cross button on top right corner ? or right click then select remove ?
I would be able to retrain my model by remove them from the dataset.
Thanks !

@AlexeyAB
If you can find time to implement this one feature. I would be able to increase accuracy by 10 folds.

@dexception

I added this feature. Select any bbox by moving cursor inside the bbox. Then press r button - to delete it.
Also you can move any bbox by usinr Right mouse button.


check wl not empty

Forget why i wrote this issue. Closing unless I remember or someone else brings this up.


Added timeout to Jenkins user input

Otherwise it will hang until the pipeline timeout
Why is this PR needed?
If someone who's not a collaborator submits a pull request the pipeline will be paused until it's approved in Jenkins. This will eventually block other runs until the job times out.
Fixes #
What does this PR do?
Adds a timeout to the input
Anything else a reviewer needs to know?
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

I'm not sure how useful is to have a timeout of 5 minutes. I was looking around and found that an alternative approach using "agent none" for input stage as described in this post However, depending on where in the pipeline we put this input, ensuring all stages run in the same node may result more complex.

How about a timeout of 1 minute for the short term, and if blocking becomes an issue later look into "agent none"?

@stefsuse I would actually propose to increase the timeout to 15 o 30 minutes to give time to actually go to the ci and approve the PR. If this becomes a problem, then look into the alternative as you propose.

I don't see the benefit of a long timeout holding resources up.  If it fails fast, someone will eventually notice that it failed and come back to restart the job - which is really the only way this will be encountered 90% of the time.  They'll see the prompt essentially interactively at that time, and approve.  Given that workflow, I think the wiggle room left by a 5-minute timeout is probably about right.  One minute seems a little short to me, but either way.
I'd approve of this as-is, but it'd be nice to see a decision on the suggestion raised in @pablochacin 's agent none link before that. :)


Raise error on non-resolution of function

This PR fixes #573

There's two paths to take here:

if we want to bind functions in planner, then this is OK, however then https://github.com/tursodatabase/limbo/pull/567 needs to follow suit accordingly.

if we do the binding ad-hoc in the bytecode emission phase per function invocation, then the best way forward here is to treat unresolved functions the same way as resolved ones:

                                    Ok(_) => {
                                        let contains_aggregates =
                                            resolve_aggregates(&expr, &mut aggregate_expressions);
                                        plan.result_columns.push(ResultSetColumn {
                                            expr: expr.clone(),
                                            contains_aggregates,
                                        });
                                    }

The biggest problem with 2, i.e. not binding in the planning stage, is that then we have no idea whether the extension-defined function (which presents itself as "any unrecognized function" to the planner) is itself an aggregate function. This will result in incorrect behavior, since we never invoke aggregate functions inside the main query loop: for example, we don't call SUM(x) for every row of the loop -- we evaluate x for every row and then call SUM after the loop:
https://github.com/tursodatabase/limbo/blob/main/core/translate/emitter.rs#L1057-L1071
https://github.com/tursodatabase/limbo/blob/main/core/translate/expr.rs#L2147
cc @penberg

We decided to merge #567 as is, so this PR should be changed to ignore the error from resolving the function - effectively do option 2 above.
We will cross the bridge of handling externally defined aggregate functions when that becomes relevant.


Crash on an attempt to close  mpv fullscreen window

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
Yes
System Info and Version
 System/Version info
Hyprland 0.45.0 built from branch main at commit 6d7544458d0fafcae410c1978a0cabce2fb4a346  (cleanup: use doLater instead of adding idle event handlers (8624)).
Date: Sun Dec 1 22:14:35 2024
Tag: v0.45.0-74-g6d754445, commits: 5507
built against aquamarine 0.5.0

flags set:
debug

System Information:
System name: Linux
Node name: archbtw
Release: 6.12.1-zen1-1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Fri, 22 Nov 2024 16:04:23 +0000

GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module  565.57.01  Thu Oct 10 12:29:05 UTC 2024

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Description
Hyprland crashes during an attempt to close fullscreened mpv window.
How to reproduce
Open a videofile with mpv, fullscreen it with an mpv keybind (f), try to close it (q)
Crash reports, logs, images, videos
hyprlandCrashReport1347.txt
hyprlandCrashReport18776.txt

it's probably caused by latest commit, will fix later today

it's probably caused by latest commit, will fix later today

Also, I don't know whether it's related - but an attempt to exit hyprand session via loginctl terminate-user $USER, when there's a fullscreen window (fullscreen, 0) causes crash before actually exiting the compositor. Happens with any gui app 100% chance, and a terminal window 50%. Here are the logs for when firefox was on fullscreen
hyprlandCrashReport38134.txt
and foot terminal window
hyprlandCrashReport39201.txt

UPD: Looks like it's not just fullscreened windows. Here's the crash upon exiting via loginctl command, when a foot window (not fullscreened) was focused. Visually, the compositor crashed in the middle of closing window animation.
hyprlandCrashReport41459.txt
Worth to mention, that closing non-mpv windows (fullscreen or not) with hyprland killactive keybind does not cause the crash

try this patch.txt

try this patch.txt

loginctl terminate-session and exiting mpv don't crash the compositor for me

I would also like to add that aside from the crashes (mine happens with looking glass), I also see way longer startup time for my session in general until I reverted back to d26439a0fe5594fb26d5a3c01571f9490a9a2d2c. Things like my second monitor activating, AGS bar loading, etc were significantly slower on that build.

git fix


Running video detection model on Android

Is there an example app running inference using SlowFast detection model trained on AVA dataset ?

This tutorial can handle both Slow and SlowFast models. Please refer to the comments in the tutorial for more information.


handle commas better

Codecov Report

Merging #7 (8d06a92) into main (36432b2) will increase coverage by 9.70%.
The diff coverage is 77.77%.

:exclamation: Current head 8d06a92 differs from pull request most recent head d491ee8. Consider uploading reports for the commit d491ee8 to get more accurate results

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   45.11%   54.81%   +9.70%
==========================================
  Files           4        4
  Lines         133      135       +2
  Branches       21       20       -1
==========================================
+ Hits           60       74      +14
+ Misses         65       57       -8
+ Partials        8        4       -4

Flag
Coverage Δ

frontend
48.00% <77.77%> (+17.86%)
:arrow_up:

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

Impacted Files
Coverage Δ

web/static/js/calculator.js
48.00% <77.77%> (+17.86%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Spark and Polaris DesignOps playbook

[x] Review and detect what's missing @Bibisirius
[ ] To refine and add missing information
[ ] Add screens
[ ] Share and valid

Figma : url

Moving this task to Jira


Crash if the description exceeds 251 characters

Prerequisites

[x] Using npm
[x] Using an up-to-date main branch
[x] Using latest version of devtools. Check the docs for how to update
[x] Tried solutions mentioned in #400
[x] For issue in production release, add devtools output of DEBUG_PROD=true npm run build && npm start

Expected Behavior
You should be able to enter a lengthy prompt, for example:

powerful dark matter mancer, dark soul 3, Extra-Wide Angle, 3d zbrush, trend on ArtStation, Realistic Lighting, Volumetric Lighting, dramatic, 8k, cinematic, super detailed, vfx, symmetrical face and body, full body portrait, cinematic lighting, hyperdetailed, detailed realistic symmetrical eyes, cinematic lighting, hyperdetailed, cgsociety, 8k, high resolution, noah bradley, Billelis, masamune shirow, katsuhiro Otomo, insanely detailed and intricate, dark, dramatic, powerful, poster, cinematic Lighting through volume, Style=render, highly detail render with octane, octane render, color black and gold, photorealistic

and have the image generate.

Current Behavior
Currently, the filename is saved as the description, with spaces replaced with dashes, and .png added to the suffix. If this filename exceeds 255 characters, the following error is thrown and the program halts:
OSError: [Errno 63] File name too long: '<filename here>[25502] Failed to execute script 'txt2img' due to unhandled exception!

Steps to Reproduce

Enter a description greater than 251 characters
Generate

Thanks! will fix this

Fixed in latest!


[WIP] Create UuidFields value object

Don't merge, this is a work in progress

Coverage decreased (-1.1%) to 95.782% when pulling 86eb45f814309ee7ff321b2a40c94bf4f82f1ded on nicwortel:create-fields-value-object into ec940bfc2fdaf06a6cd289e8706f6bbd7049f99c on ramsey:4.x.

Coverage increased (+0.1%) to 97.043% when pulling 8bd7e3ede35f67bc7d40fa645d9a78bceffd7bdf on nicwortel:create-fields-value-object into ec940bfc2fdaf06a6cd289e8706f6bbd7049f99c on ramsey:4.x.

Coverage increased (+0.1%) to 97.043% when pulling 8bd7e3ede35f67bc7d40fa645d9a78bceffd7bdf on nicwortel:create-fields-value-object into ec940bfc2fdaf06a6cd289e8706f6bbd7049f99c on ramsey:4.x.

Coverage increased (+0.2%) to 97.074% when pulling 725e17575a148b004118101a1e4cdd5545750291 on nicwortel:create-fields-value-object into ec940bfc2fdaf06a6cd289e8706f6bbd7049f99c on ramsey:4.x.

Coverage increased (+0.2%) to 97.074% when pulling bfd5504b421a15fa6ca8c6d3cf0e4a51c446a71b on nicwortel:create-fields-value-object into ec940bfc2fdaf06a6cd289e8706f6bbd7049f99c on ramsey:4.x.

Coverage increased (+0.2%) to 97.074% when pulling 57fd14f7c04801f5ac9da2cdffcf8b047ad2842c on nicwortel:create-fields-value-object into 6b6e85cbf5258f534a3db9b582bdef7a4b6ce8b3 on ramsey:4.x.

Your work in progress looks nice, but I'm a bit worried about the performance impact of all those assertions in the constructor of UuidFields.
Do you mind providing a benchmark to compare performance before and after your changes ?

Checking in on your work in progress. How's this coming?

Changes Unknown when pulling aac264d752af8b980280512de418dfae91f55457 on nicwortel:create-fields-value-object into ** on ramsey:4.x**.

Hi, sorry for the delay, I couldn't find the time to finish the PR. I think it's finished now, although I'll have to do some more exploratory testing to be sure everything works.

Changes Unknown when pulling f80e955f00ce7951495c440c08cac21fa7da65ce on nicwortel:create-fields-value-object into ** on ramsey:4.x**.

@aztech-dev I've created the following file: benchmark.php
<?php

require 'vendor/autoload.php';

for ($i = 0; $i < 1000; $i++) {
    $uuid = \Ramsey\Uuid\Uuid::uuid4();
}

Then I execute the following command:
time php benchmark.php

On the 4.x branch this gives the following result:
real	0m0.048s
user	0m0.040s
sys	0m0.008s

On my branch this is the result:
real	0m0.089s
user	0m0.080s
sys	0m0.008s

On what version of PHP did you run that benchmark?

Sorry for the delay. On holiday now; I'll review late next week.

No problem, enjoy :+1:

I'm still giving some thought to this. I have some ideas about the future structure, and I've been thinking about your suggestion at DPC (I think it was you who suggested this) to introduce separate objects for Uuid1, Uuid4, etc.
Just wanted to let you know this is still on the table. :-)


minify URLs

I'd like to shorten background:url('http://website.com/images/bg.png') to background:url('images/bg.png').
I've been looking through rebase, relativeTo, root & target. They serve their own intended purpose, and I can't hack it to do URL minification. For starters, it bails out as soon as it sees an absolute URL.
If there is already an existing option to do this, please let me know.

@alexlamsl there's currently no way of doing that. That would require specifying a root option as URL. May I know how your CSS ended up having absolute URLs?

@jakubpawlowicz I'd confess I find that odd as well, but I was handling https://github.com/kangax/html-minifier/issues/535 and mistakenly thought clean-css can minify absolute URLs.

That's not the case at the moment, but I can see it was addressed in html minifier itself. I'll close it for now.

Yeah I've made a PR that handles the inline CSS for now. Separate .css files aren't handled by html-minifier, but then ball's in your court. :ghost:


versions: Bump golang

Bump to go 1.20.12 to resolve https://pkg.go.dev/vuln/GO-2023-2382

@stevenhorsman have you used hack/update-go-container.sh to bump the version?

Yes - that's where all the checksums automatically were gen'd by

And next you will send a PR to update Dockerfile?

Sorry, which Dockerfile? Did I miss something?

@bpradipt - sorry Pradipta, I think you left a comment, rather than approval, so it still needs a second green tick. Thanks!

Yeah sorry about it.

Adding hold label until I understand from Wainer what I've missed

Adding hold label until I understand from Wainer what I've missed

I was talking about https://github.com/confidential-containers/cloud-api-adaptor/blob/main/Dockerfile#L2 .

I was talking about https://github.com/confidential-containers/cloud-api-adaptor/blob/main/Dockerfile#L2 .

Okay, so something that has to be done as follow up and the image won't be build yet. Understood and thanks for the reminder (that it looks like we've forgotten the last few times).

I was talking about https://github.com/confidential-containers/cloud-api-adaptor/blob/main/Dockerfile#L2 .

Okay, so something that has to be done as follow up and the image won't be build yet. Understood and thanks for the reminder (that it looks like we've forgotten the last few times).

Now the base image has been built and pushed to quay.io - I've created https://github.com/confidential-containers/cloud-api-adaptor/pull/1621 to use it


Non-technical Mitigation Strategies

Hi!
Great stuff!
WDYT about the following non-technical strategies to address cognitive load when faced with unfamiliar code:

While trying to understand a piece of code:
a. Take notes of micro-understandings - this can serve as an external persistent memory, extended cognition
b. Even better: encode your micro-understandings into the code with micro-refactorings, comments, docstrings, renames, etc.
This can combat loss of context when interupted for example.

Chunking:
Assuming we can hold only four chunks in mind at a time. Chunks can differ greatly in cognitive value. I beleive that through delberate practice, we can chunk together smaller chunks into larger ones, allowing us to tackle a larger range of cognitive tasks. See @jbrains writing and talks about this.

Shared burden through Teaming
Maybe a team has more cognitive power than a single person?

More?
Thanks!

Three more come to mind:
4. Work in tiny steps see GeePaw's MMMSS, Arlo's Read by Refactoring and Naming as a Process, etc.
5. Offload cognitive load to AI, let it do (some of) the thinking
6. Offload to automation and tools

Hi there, @nitsanavni! Thank you for your feedback and such insightful thoughts!
Reading your points, as well as the links you provided, triggered a few thoughts, so I'll write them down in raw.
That chunking thing resonates a lot of with my own experience. Even when it comes to non-technical stuff. It seems like it is closely related to bird's eye overview, and writers from non-technical field seem to practice this idea a lot. You take a sneak peak at the article's headline or a few intro lines - and you can immediately chunk the whole article in just one idea. You can read a few headlines and you get the basic idea of what's happening in some domain, it might be a totally wrong and subjective picture, but that's not the point here. You get overarching view of the system (chunking?), and you can dive into the details if needed.
I had a rather different experience when reading technical proposal and the code itself. You open a technical proposal, you read a few lines, and one question appears in your head. "What is that for? What problem does it solve? How does that fit into overall system?". And usually you have to dig deep in order to for this chunking to happen.
Whenever I face a new framework, orchestration system like K8S or any system in particular, I want this chunking to happen as quick as possible. And with the current learning mediums it's a rather tedious, slow experience. Taking notes helps a lot, I completely agree with you about this point about micro-understandings! With such approach I can come back years after and load those mental models from the notes directly into my head.
The way programmers love to learn new systems is to take some working simple example that they understand, and hack&run it until a more complex solution emerges.  We start with a naive view of the system - we see only few interacting overarching chunks, and we hack&run until we get a finer realistic picture. Sadly, current mediums throw at you all the details at once, and you have to go through that taxing chunking process all on your own.
That's not a structured response to your points, just a train of thoughts.


MOTD for quest scanning

Hello,
I've got users that never visits discord when I post that there will be rescan of quest. I was thinking maybe adding some logic that is device SE1 is assigned to instance Quests1 users will get MOTD "Quest scanning in progress". I know that people might have different instances for example per town, so it would be best to include that logic too zone restriction rights. I hope more or less it is clear what I mean hehe

Maybe instead of by device, we look at instances? For example, in the config, you could have an array of quest instances that you want to alert users about (or an option for all). If any of those instances are active, with a set interval that's checking the device/instance DB, a MotD template could be generated saying X instances are currently being scanned for quests?

Yeah that sound good, would be less strain on the DB I think.

But what if I use separate device (not mons related) to scan more quests or so? MOTD would be kinda pointless then. I'd rather go with this solution: https://github.com/WatWowMap/ReactMap/issues/464 ;)

What do you mean? This wouldn't be device dependent, just if any specified quest instances are active.

I think that he means, that he switch to mons but leave like for example 1 device to continue scanning quests?

What do you mean? This wouldn't be device dependent, just if any specified quest instances are active.

Lets say I scan mon instance with 10 devices that during the night do quests but I scanned 90% of pokestops and during the day I'd like to scan other 10% with additional device when these 10 devices are still scanning mons. MOTD about quest scans in that case is pointless

I use rdmass to schedule quest scans and that's why I think issue 464 would be the best option cause rdmass sends notification to announcements channel

But what if I use separate device (not mons related) to scan more quests or so? MOTD would be kinda pointless then. I'd rather go with this solution: #464 ;)

That #464 dosn't look back but I would rather have something automatic. When I use rdmass I sometimes don't have time to post it on discord. Plus you got telegram and in house login.

But what if I use separate device (not mons related) to scan more quests or so? MOTD would be kinda pointless then. I'd rather go with this solution: #464 ;)

That #464 dosn't look back but I would rather have something automatic. When I use rdmass I sometimes don't have time to post it on discord. Plus you got telegram and in house login.

rdmass posts info by itself ;) just configure it

What do you mean? This wouldn't be device dependent, just if any specified quest instances are active.

Lets say I scan mon instance with 10 devices that during the night do quests but I scanned 90% of pokestops and during the day I'd like to scan other 10% with additional device when these 10 devices are still scanning mons. MOTD about quest scans in that case is pointless

So you could just exclude that instance from being checked on/reported in a motd?

What do you mean? This wouldn't be device dependent, just if any specified quest instances are active.

Lets say I scan mon instance with 10 devices that during the night do quests but I scanned 90% of pokestops and during the day I'd like to scan other 10% with additional device when these 10 devices are still scanning mons. MOTD about quest scans in that case is pointless

So you could just exclude that instance from being checked on/reported in a motd?

But it would be scanned each day at night anyway

But what if I use separate device (not mons related) to scan more quests or so? MOTD would be kinda pointless then. I'd rather go with this solution: #464 ;)

That #464 dosn't look back but I would rather have something automatic. When I use rdmass I sometimes don't have time to post it on discord. Plus you got telegram and in house login.

rdmass posts info by itself ;) just configure it

Okay I will try that, but another question will be for #464 how do you clear it MOTD? How long will you want to stay there? I rather don't bother premium users to close MOTD every time they log in as I know for experience it is annoying. Best would be to display once per user. Anyways it is up to @TurtIeSocks what way he wants to go hehe

Going to close this for now. I think RM is perhaps not the correct tool to alert users automatically of quest rescans


Compress in-memory slices with Zstd

In a repeated test with 8'557'668 ingested Suricata events enabling the compression had a negligible effect on import speed (under 0.5%), but reduced the size of the archive and also the in-memory size of the loaded slices by roughly the same amount.
Here are the sizes of the database for three scenarios: Uncompressed, Zstd with the default compression level, and Zstd with the max compression level (50% slower on import, so irrelevant in the grand scheme of things).
❯ du -csh vast.db.uncompressed/{index,archive}
667M	vast.db.uncompressed/index
1.8G	vast.db.uncompressed/archive
2.5G	total

❯ du -csh vast.db.zstd.default/{index,archive}
668M	vast.db.zstd.default/index
426M	vast.db.zstd.default/archive
1.1G	total

❯ du -csh vast.db.zstd.max/{index,archive}
675M	vast.db.zstd.max/index
361M	vast.db.zstd.max/archive
1.0G	total

:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Discuss whether we want to enable this by default, or make this an option, or just not do it at all. After that comes testing and a changelog entry.

Out of curiosity, trying to understand the entropy: can you zstd-compress the index (on the filesystem) as well and report on the sizes?

667M to 229M when doing it per-file.

667M to 229M when doing it per-file.

So down to ~34% of the original size.

I guess it would be an easy win if this could be made configurable. There seem to be people out there using a compressed file system with VAST, and for those scenarios the additional compression might become a performance degradation, as there would be two layers attempting to compress this.

Very nice! I would like to measure the export performance and RSS as well.

There seem to be people out there using a compressed file system with VAST, and for those scenarios the additional compression might become a performance degradation, as there would be two layers attempting to compress the data.

Probably not even necessary, at least btrfs opts out of compression very quickly if it doesn't manage to compress the first few kB itself. This should also be much more effective than compressing individual filesystem blocks.

Out of curiosity, trying to understand the entropy: can you zstd-compress the index (on the filesystem) as well and report on the sizes?

667M to 229M when doing it per-file.

That is promising, but we should probably do it a per-value-index basis instead of the whole file.

I guess it would be an easy win if this could be made configurable.

Yes, I think so. Even with Parquet stores coming up this is still valuable to reduce the memory usage.

Very nice! I would like to measure the export performance and RSS as well.

Will do and report back!

Out of curiosity, trying to understand the entropy: can you zstd-compress the index (on the filesystem) as well and report on the sizes?

667M to 229M when doing it per-file.

That is promising, but we should probably do it a per-value-index basis instead of the whole file.

I think that's for a separate story, let's keep this focussed on the table slices only for now.

I think that's for a separate story, let's keep this focussed on the table slices only for now.

Definitely.

Very nice! I would like to measure the export performance

No noticeable difference for Zstd with default compression. Unpacking is probably slightly more expensive, but sending things over the wire is much cheaper. The higher compression level is especially bad when selecting subsets of table slices, because that requires re-compressing the results before sending them over with the current approach. But from this point of view alone I don't see why we'd not just always enable Zstd with default compression.

and RSS as well.

For the Zstd default during export:
Maximum resident set size (kbytes): 2186784
Socket messages sent: 2818
Socket messages received: 584

For the uncompressed version:
Maximum resident set size (kbytes): 2406112
Socket messages sent: 19274
Socket messages received: 574

I've extended this PR with the tuned defaults following my extensive measurements on our testbed server.


Type check user provided arguments against expected types

For example, using the function =markets_region_orders(10000065,sell,true) results in the ESI requests to be like: https://esi.evetech.net/v1/markets/10000065/orders/?order_type=#NAME?&type_id=true, which causes some unexpected behavior.
We could probably easily prevent this by using https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof on the input arguments and ensuring they match what ESI's arguments are expecting, otherwise throw an error.

So as it turns out, the value of order_type is actually "#NAME?". As such typeof won't really help in this context. But I can still catch it and throw some error. Then can also use typeof to handle type differences.


chore(*) import acme

As a result of an effort to improve external plugins maintainership, we are importing currently-bundled plugins into Kong's main tree. The acme plugin used to live in [1].
Additionally to importing plugin contents, this PR also preserves the Git history. History was amended to correct commit scopes - including acme in commit messages scope.
[1] https://github.com/Kong/kong-plugin-acme/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: samnela:x: herlon214:x: okanozdemirYou have signed the CLA already but the status is still pending? Let us recheck it.

@herlon214, @okanozdemir, @samnela My apologies to bug you all, but would you mind re-signing the CLA, so we can incorporate this plugin into Kong's tree? It was already signed in the acme repository, but as it's a separate repo, it doesn't show up here.

@gszr, it is done.

Hey @herlon214, sorry to bug again - could you sign the CLA so we can proceed with this PR? Thanks!

Hey @herlon214, sorry to bug again - could you sign the CLA so we can proceed with this PR? Thanks!

Sorry for the delay, just signed :rocket:


Per connection local rate limiting

Commit Message:
This is a PR for scoping token buckets in the local rate limiting flow on a per connection basis as opposed to scoping it on the entire envoy instance. More details in #15637
Additional Description:
Risk Level: Low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

cc @mattklein123 @rgs1

@gokulnair mind addressing the format error:
trailing whitespace: source/extensions/filters/http/local_ratelimit/local_ratelimit.h

I'll review the rest in the meanwhile, thanks!

Did a first pass, let's also add docs and tests. Thanks!

Thanks for taking a look! I've moved it out of draft and added docs and tests as well. Let me know if this is good to go.

Ugh! I might've messed up this dev branch by fetching & rebasing from upstream and resolving conflicts rather than resolving it directly via github 🤦♂Not sure if there's an easier way to restore this branch other than closing this PR and reopening a new one?

FWIW I don't know of a situation where it's appropriate to rebase in the Envoy github flow. Just merge main and resolve conflicts that way.

Thanks for the reviews! Let me know if there's anything else that's needed to get this going.

Oops, I'm sorry about review lag - Matt would usually take the lead here but his leave got unexpectedly extended. I'll pick it up instead!

Thanks @alyssawilk!

Looks good, just some minor comments / nits.

Thanks!

I've addressed all comments/nits. Will take a look at adding the integration test shortly.

/restest

/retest

LGTM
Could you please update the PR description with the appropriate fields (testing: unit tests, docs: inline etc) and then I'll let @antoniovicente merge when he's set.

I don't have remaining comments.  The remaining question is wherever or not integration tests are in the work as part of this PR or a followup.  A followup makes the most sense to me at this point, we should go ahead and merge.

LGTM
Could you please update the PR description with the appropriate fields (testing: unit tests, docs: inline etc) and then I'll let @antoniovicente merge when he's set.

I don't have remaining comments. The remaining question is wherever or not integration tests are in the work as part of this PR or a followup. A followup makes the most sense to me at this point, we should go ahead and merge.

Thanks! I do agree that a follow task makes the most sense at this time (I do have a draft up but its still WIP)
Also, I've updated the PR description with more details. Looks like we should be good to go for the merge, let me know if there's anything else that's needed from my end 👍

/lgtm api

@htuch Mind approving the api change once again, please? (we updated a doc in the proto file)
Thanks!


Fix/jeb snowflake source quoting

Fixes #1317
Fixes the other bug described in #1326
HEAD also includes the PR for #1332 , with merge conflicts resolved and the snowflake docs generate tests fixed
let's see if windows works?

the new error message looks great -- let's let the tests run then ship this in the AM!


Pull configuration from Rails credentials

Suggested by @garrettdimon, we should set defaults coming from Rails' credentials in addition to ENV.
https://guides.rubyonrails.org/security.html#custom-credentials

Fixed in #782


🐛 Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.Rebuild Packages Package Settings

I'm a big fan of this package, but since the last update this bug keeps returning.. 🐛
I hope you can fix it, info is in the img 🔽🔽

Did you try rebuild the package? Uninstall re-install?

@daverickdunn I did, as it says. It's just keeps saying after every reload or restart. That's why I made an issue out of it.

Which version of Atom are you running?

@daverickdunn 1.20.0 x64 MacOS 10.12.6 (Sierra)

1.21.1 or 1.22.0-beta1 are the latest versions of Atom, please try either as the last patch was tested for both of those. Since Atom changed some CSS class names it may not work correctly for older versions.

uninstall & install work fine for me.


disabled stage

Ran Plan for project: non-prod_us-east-2 dir: non-prod/us-east-2 workspace: default
Show Output
time=2022-04-30T16:41:09-05:00 level=info msg=The stack at /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2 will be processed in the following order for command plan:
Group 1
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster

time=2022-04-30T16:41:09-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql]
time=2022-04-30T16:41:09-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster]
time=2022-04-30T16:41:09-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql]
time=2022-04-30T16:41:09-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster]

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...
- Installing hashicorp/aws v3.7.0...
- Installing hashicorp/aws v3.7.0...
- Installing hashicorp/aws v3.7.0...
- Installing hashicorp/aws v3.7.0...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
Releasing state lock. This may take a few moments...
aws_security_group_rule.elb_allow_all_outbound: Refreshing state... [id=sgrule-3199863889]
aws_security_group_rule.asg_allow_http_inbound: Refreshing state... [id=sgrule-2456877539]
aws_security_group_rule.elb_allow_http_inbound: Refreshing state... [id=sgrule-2974374769]
aws_security_group.asg: Refreshing state... [id=sg-0139520714f7ad776]
aws_launch_configuration.webserver_example: Refreshing state... [id=terraform-20220430212525261900000001]
aws_security_group.elb: Refreshing state... [id=sg-0136aec550f832fea]
aws_autoscaling_group.webserver_example: Refreshing state... [id=tf-asg-20220430212529316200000002]
aws_elb.webserver_example: Refreshing state... [id=webserver-example-stage]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # aws_autoscaling_group.webserver_example will be destroyed
  # (because aws_autoscaling_group.webserver_example is not in configuration)
  - resource "aws_autoscaling_group" "webserver_example" {
      - arn                       = "arn:aws:autoscaling:us-east-2:270463201375:autoScalingGroup:3f84a4b4-ec28-41d0-8adf-eca11793b92f:autoScalingGroupName/tf-asg-20220430212529316200000002" -> null
      - availability_zones        = [
          - "us-east-2a",
          - "us-east-2b",
          - "us-east-2c",
        ] -> null
      - default_cooldown          = 300 -> null
      - desired_capacity          = 2 -> null
      - enabled_metrics           = [] -> null
      - force_delete              = false -> null
      - health_check_grace_period = 300 -> null
      - health_check_type         = "ELB" -> null
      - id                        = "tf-asg-20220430212529316200000002" -> null
      - launch_configuration      = "terraform-20220430212525261900000001" -> null
      - load_balancers            = [
          - "webserver-example-stage",
        ] -> null
      - max_instance_lifetime     = 0 -> null
      - max_size                  = 2 -> null
      - metrics_granularity       = "1Minute" -> null
      - min_size                  = 2 -> null
      - name                      = "tf-asg-20220430212529316200000002" -> null
      - protect_from_scale_in     = false -> null
      - service_linked_role_arn   = "arn:aws:iam::270463201375:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling" -> null
      - suspended_processes       = [] -> null
      - target_group_arns         = [] -> null
      - termination_policies      = [] -> null
      - vpc_zone_identifier       = [
          - "subnet-06539adae1deb3596",
          - "subnet-08d1816ef938a42f5",
          - "subnet-095ff506b3a724ab8",
        ] -> null
      - wait_for_capacity_timeout = "10m" -> null

      - tag {
          - key                 = "Name" -> null
          - propagate_at_launch = true -> null
          - value               = "webserver-example-stage" -> null
        }
    }

  # aws_elb.webserver_example will be destroyed
  # (because aws_elb.webserver_example is not in configuration)
  - resource "aws_elb" "webserver_example" {
      - arn                         = "arn:aws:elasticloadbalancing:us-east-2:270463201375:loadbalancer/webserver-example-stage" -> null
      - availability_zones          = [
          - "us-east-2a",
          - "us-east-2b",
          - "us-east-2c",
        ] -> null
      - connection_draining         = false -> null
      - connection_draining_timeout = 300 -> null
      - cross_zone_load_balancing   = true -> null
      - dns_name                    = "webserver-example-stage-1824628323.us-east-2.elb.amazonaws.com" -> null
      - id                          = "webserver-example-stage" -> null
      - idle_timeout                = 60 -> null
      - instances                   = [
          - "i-02afabca315aa1fd0",
          - "i-04e1ee3f8f53a5757",
        ] -> null
      - internal                    = false -> null
      - name                        = "webserver-example-stage" -> null
      - security_groups             = [
          - "sg-0136aec550f832fea",
        ] -> null
      - source_security_group       = "270463201375/webserver-example-stage-elb" -> null
      - source_security_group_id    = "sg-0136aec550f832fea" -> null
      - subnets                     = [
          - "subnet-06539adae1deb3596",
          - "subnet-08d1816ef938a42f5",
          - "subnet-095ff506b3a724ab8",
        ] -> null
      - tags                        = {} -> null
      - zone_id                     = "Z3AADJGX6KTTL2" -> null

      - health_check {
          - healthy_threshold   = 2 -> null
          - interval            = 30 -> null
          - target              = "HTTP:8080/" -> null
          - timeout             = 3 -> null
          - unhealthy_threshold = 2 -> null
        }

      - listener {
          - instance_port     = 8080 -> null
          - instance_protocol = "http" -> null
          - lb_port           = 80 -> null
          - lb_protocol       = "http" -> null
        }
    }

  # aws_launch_configuration.webserver_example will be destroyed
  # (because aws_launch_configuration.webserver_example is not in configuration)
  - resource "aws_launch_configuration" "webserver_example" {
      - arn                              = "arn:aws:autoscaling:us-east-2:270463201375:launchConfiguration:b5e53209-c749-46d7-a261-a87c7ede414e:launchConfigurationName/terraform-20220430212525261900000001" -> null
      - associate_public_ip_address      = false -> null
      - ebs_optimized                    = false -> null
      - enable_monitoring                = true -> null
      - id                               = "terraform-20220430212525261900000001" -> null
      - image_id                         = "ami-05803413c51f242b7" -> null
      - instance_type                    = "t2.micro" -> null
      - name                             = "terraform-20220430212525261900000001" -> null
      - security_groups                  = [
          - "sg-0139520714f7ad776",
        ] -> null
      - user_data                        = "4430fd6498339061effa6d27ccf341a1e94569d7" -> null
      - vpc_classic_link_security_groups = [] -> null
    }

  # aws_security_group.asg will be destroyed
  # (because aws_security_group.asg is not in configuration)
  - resource "aws_security_group" "asg" {
      - arn                    = "arn:aws:ec2:us-east-2:270463201375:security-group/sg-0139520714f7ad776" -> null
      - description            = "Managed by Terraform" -> null
      - egress                 = [] -> null
      - id                     = "sg-0139520714f7ad776" -> null
      - ingress                = [
          - {
              - cidr_blocks      = [
                  - "<IP_ADDRESS>/0",
                ]
              - description      = ""
              - from_port        = 8080
              - ipv6_cidr_blocks = []
              - prefix_list_ids  = []
              - protocol         = "tcp"
              - security_groups  = []
              - self             = false
              - to_port          = 8080
            },
        ] -> null
      - name                   = "webserver-example-stage-asg" -> null
      - owner_id               = "270463201375" -> null
      - revoke_rules_on_delete = false -> null
      - tags                   = {} -> null
      - vpc_id                 = "vpc-0675eacc2e2bb79bb" -> null
    }

  # aws_security_group.elb will be destroyed
  # (because aws_security_group.elb is not in configuration)
  - resource "aws_security_group" "elb" {
      - arn                    = "arn:aws:ec2:us-east-2:270463201375:security-group/sg-0136aec550f832fea" -> null
      - description            = "Managed by Terraform" -> null
      - egress                 = [
          - {
              - cidr_blocks      = [
                  - "<IP_ADDRESS>/0",
                ]
              - description      = ""
              - from_port        = 0
              - ipv6_cidr_blocks = []
              - prefix_list_ids  = []
              - protocol         = "-1"
              - security_groups  = []
              - self             = false
              - to_port          = 0
            },
        ] -> null
      - id                     = "sg-0136aec550f832fea" -> null
      - ingress                = [
          - {
              - cidr_blocks      = [
                  - "<IP_ADDRESS>/0",
                ]
              - description      = ""
              - from_port        = 80
              - ipv6_cidr_blocks = []
              - prefix_list_ids  = []
              - protocol         = "tcp"
              - security_groups  = []
              - self             = false
              - to_port          = 80
            },
        ] -> null
      - name                   = "webserver-example-stage-elb" -> null
      - owner_id               = "270463201375" -> null
      - revoke_rules_on_delete = false -> null
      - tags                   = {} -> null
      - vpc_id                 = "vpc-0675eacc2e2bb79bb" -> null
    }

  # aws_security_group_rule.asg_allow_http_inbound will be destroyed
  # (because aws_security_group_rule.asg_allow_http_inbound is not in configuration)
  - resource "aws_security_group_rule" "asg_allow_http_inbound" {
      - cidr_blocks       = [
          - "<IP_ADDRESS>/0",
        ] -> null
      - from_port         = 8080 -> null
      - id                = "sgrule-2456877539" -> null
      - ipv6_cidr_blocks  = [] -> null
      - prefix_list_ids   = [] -> null
      - protocol          = "tcp" -> null
      - security_group_id = "sg-0139520714f7ad776" -> null
      - self              = false -> null
      - to_port           = 8080 -> null
      - type              = "ingress" -> null
    }

  # aws_security_group_rule.elb_allow_all_outbound will be destroyed
  # (because aws_security_group_rule.elb_allow_all_outbound is not in configuration)
  - resource "aws_security_group_rule" "elb_allow_all_outbound" {
      - cidr_blocks       = [
          - "<IP_ADDRESS>/0",
        ] -> null
      - from_port         = 0 -> null
      - id                = "sgrule-3199863889" -> null
      - ipv6_cidr_blocks  = [] -> null
      - prefix_list_ids   = [] -> null
      - protocol          = "-1" -> null
      - security_group_id = "sg-0136aec550f832fea" -> null
      - self              = false -> null
      - to_port           = 0 -> null
      - type              = "egress" -> null
    }

  # aws_security_group_rule.elb_allow_http_inbound will be destroyed
  # (because aws_security_group_rule.elb_allow_http_inbound is not in configuration)
  - resource "aws_security_group_rule" "elb_allow_http_inbound" {
      - cidr_blocks       = [
          - "<IP_ADDRESS>/0",
        ] -> null
      - from_port         = 80 -> null
      - id                = "sgrule-2974374769" -> null
      - ipv6_cidr_blocks  = [] -> null
      - prefix_list_ids   = [] -> null
      - protocol          = "tcp" -> null
      - security_group_id = "sg-0136aec550f832fea" -> null
      - self              = false -> null
      - to_port           = 80 -> null
      - type              = "ingress" -> null
    }

Plan: 0 to add, 0 to change, 8 to destroy.

Changes to Outputs:
  - asg_name              = "tf-asg-20220430212529316200000002" -> null
  - asg_security_group_id = "sg-0139520714f7ad776" -> null
  - elb_dns_name          = "webserver-example-stage-1824628323.us-east-2.elb.amazonaws.com" -> null
  - elb_security_group_id = "sg-0136aec550f832fea" -> null
  - url                   = "http://webserver-example-stage-1824628323.us-east-2.elb.amazonaws.com:80" -> null

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: plan.out

To perform exactly these actions, run the following command to apply:
    terraform apply "plan.out"
Releasing state lock. This may take a few moments...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
Releasing state lock. This may take a few moments...
Releasing state lock. This may take a few moments...
time=2022-04-30T16:41:36-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...
- Installing hashicorp/aws v3.7.0...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-30T16:41:36-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...
- Installing hashicorp/aws v3.7.0...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-30T16:41:36-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...
- Installing hashicorp/aws v3.7.0...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

time=2022-04-30T16:41:36-05:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching "3.7.0"...
- Installing hashicorp/aws v3.7.0...
- Installed hashicorp/aws v3.7.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

:arrow_forward: To apply this plan, comment:

atlantis apply -p non-prod_us-east-2

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p non-prod_us-east-2

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply -p non-prod/us-east-2

Apply Error
no project with name "non-prod/us-east-2" is defined in atlantis.yaml

atlantis apply -p non-prod_us-east-2

Ran Apply for project: non-prod_us-east-2 dir: non-prod/us-east-2 workspace: default
Show Output
time=2022-04-30T16:43:42-05:00 level=info msg=The stack at /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2 will be processed in the following order for command apply:
Group 1
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql
- Module /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster

time=2022-04-30T16:43:42-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/webserver-cluster]
time=2022-04-30T16:43:42-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/stage/mysql]
time=2022-04-30T16:43:42-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/mysql]
time=2022-04-30T16:43:42-05:00 level=warning msg=No double-slash (//) found in source URL /var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/empty.tf. Relative paths in downloaded Terraform code may not work. prefix=[/var/home/chris/.atlantis/repos/jackmonty/terragrunt-infrastructure-live-example/63/default/NZXW4LLQOJXWIL3VOMWWKYLTOQWTE===/non-prod/us-east-2/qa/webserver-cluster]
Releasing state lock. This may take a few moments...

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Releasing state lock. This may take a few moments...
Releasing state lock. This may take a few moments...

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Apply complete!  This may take a few moments...

Apply complete! Resources: 0 added, 0 changed, 8 destroyed.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: non-prod/us-east-2 workspace: default


Add typecasts for lambdas for eclipse compiler

This adds explicit type casts for lambdas in engine-test. See #1771 for details.
It also formats the expressions in engine a little and adds a short comment to it.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/144/
Hooray Jenkins reported success with all tests good!


ZEPPELIN-3527. Use log4j v2

What is this PR for?
ZEPPELIN-3527
Draft for using log4j v2 jars instead of log4j v1
What type of PR is it?
Improvement -- Security
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?

Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the license files need to update?
Is there breaking changes for older versions?
Does this needs documentation?

I know it's related to log4j's security issue but I wonder if it's possible to replace all with log4j2 because we might have some log4j1-specific code. Let's keep on eye on the CI first.

zeppelin no longer seems to have any log4j v1 internal logging - but does still use slf4j-log4j12
My next aim is to try to get rid of slf4j-log4j12


feat(react-query): add re-export tanstack query functions

Overview

https://github.com/toss/suspensive/issues/1096

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 75.46%. Comparing base (8449980) to head (5693dc1).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1138      +/-   ##
==========================================
- Coverage   75.72%   75.46%   -0.26%
==========================================
  Files          57       58       +1
  Lines         585      587       +2
  Branches      115      116       +1
==========================================
  Hits          443      443
- Misses        132      134       +2
  Partials       10       10

Components
Coverage Δ

@suspensive/utils
47.16% <ø> (ø)

@suspensive/react
95.74% <ø> (ø)

@suspensive/react-query
67.66% <ø> (ø)

@suspensive/react-query-4
0.00% <ø> (ø)

@suspensive/react-query-5
0.00% <0.00%> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/cache
98.16% <ø> (ø)

@suspensive/react-image
80.39% <ø> (ø)

@manudeli Are you planning to add the migration explanation to the Docs? If you do, I would also like to add @sse to the JSDoc.

@manudeli Are you planning to add the migration explanation to the Docs? If you do, I would also like to add @see to the JSDoc.

How about next version after this, first make docs and then re-think whether it is permanent link or temporary link. if permanent link it is, at that time, could you add @see jsdoc please?

I agree. Let's proceed step by step.


Update Readme

I Tested in my Browser Microsoft Edge on my Lumia 950XL with Build Windows 10 Insider Preview, and this work, but front camera!!

Deploy preview for qrcode-4951b7 ready!
Built with commit 2672eee4561c4c35602991ae4b57b01f93045898
https://deploy-preview-54--qrcode-4951b7.netlify.com


Gnome

Linux GUI Desktop environment:
https://www.gnome.org/wp-content/themes/gnome-grass/images/gnome-logo.svg

Added in 028450df5370ab04535e3d1b0f5e343232d94d2d
Thanks


P2P not getting INV message

Hi,
we're using your bitcore-p2p module, to get INV messages.
Our p2p pool is getting INV messages fine, but after some time stops getting them without any error.
We have tried to save connection of our pool and bitcoin network using ping and pong messages, but it haven't take any effect.
Code example:
var pool = new Pool({
    network: Networks.livenet,
    maxSize: 150,
    dnsSeed: false,
    addrs: hosts
});

pool.connect();

pool.on('peerinv', function (peer, message) {

                   var Invs = message.inventory;
                    async.eachLimit(Invs, 20, function (inv, cb) {
                        var invHash = lib.util.buffer.bufferToHex(lib.util.buffer.reverse(inv.hash));
                        //console.log(invHash);
                        cb();
                    }, function (err) {
                        assert.equal(null, err);
                    })

                    peer.sendMessage(messages.Ping());
                    peer.on('ping', function (message) {
                        console.log(message.nonce);
                        peer._sendPong(message.nonce);
                    });

                    peer.on('ready', function() {
                        console.log("ready",pool.inspect());
                        peer.sendMessage(messages.GetAddresses());
                    });

                    peer.on('addr', function(message) {
                        message.addresses.forEach(function(addr) {
                            console.log(addr);
                            pool._connectPeer(addr);
                            console.log(pool.inspect());
                        });
                    });
})

Sorry, the issue was MongoDb related and has been resolved.
So I'm closing it.


ACER Chromebook - Crouton fails to complete installation if a single package fails

I am trying to install linux kali (kali-roling) to my cromebook acer CB3-111 I have downloaded
https://github.com/dnschneid/crouton
https://goo.gl/fd3zc
when installing with the code "sudo sh crouton -r kali-rolling -t xfce,extension,xiwi" for the first time all wne well exept untill what I think was the end of the instalation process when it gave the text
Package xbindkeys is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'xbindkeys' has no installation candidate
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
now then I try installing again it just says
/usr/local/chroots/kali-rolling already has stuff in it!
Either delete it, specify a different name (-n), or specify -u to update it.
I have deleted it and I dont know how to successfully install linux kali, Any help would be nice.

I see you left a comment in the "tutorials are broken" issue saying you were new, which is understandable; that being said, please don't create another issue with your exact same problem simply because no one responded to it the first time. no one's obligated to help you, and duplicate issues only clutter and complicate things. as such, I will address your original issue (#4171).

@thatonetechdude,
See if this helps:
https://github.com/dnschneid/crouton/issues/4153#issuecomment-560190450

@DennisLfromGA Can this be closed? It is a duplicate of https://github.com/dnschneid/crouton/issues/4171.

@JL2210,
Yes, definitely, I missed that earlier one.
Closing, duped to https://github.com/dnschneid/crouton/issues/4171.
-DennisLfromGA

Thank you so much for the help! Sorry for the duplicate.