[PE-D][Tester B] UG: Name field: Unable to accept "," symbols

Steps to recreate: input a valid add command with all valid parameters, except the name parameter which includes a comma in the name.
Expected: Name should be accepted as there is a significant enough number of people with the "," symbol in their name (eg. Tan Kian Hoo, John).
Actual: An error message is thrown.

Labels: severity.Medium type.FeatureFlaw
original: Arren11111/ped#14

close, same as #253


Update README.md before archival

I am merging this as an Admin without waiting for approvals since there are no other approvers that can do it.


Unconditional generation

Hello thanks for the great repository!
I'm wondering how the unconditional video generation results from the paper can be reproduced.
In the runner.video_gen() function there seems to be an assert that only allows conditional generation.
Is there an example for sampling unconditionally elsewhere?

Thanks for the quick response, I managed to get it working I believe.
The results were all very gray at first, but started to look better after they had drifted for enough frames.
Are there any settings during training that might help improve the performance specifically on unconditional generation?
Also is it possible to run video_gen() and only do the unconditional generation step?
I tried to puzzle out all the if statements but was just left confused.
I added an uncond_gen() function to the runner but that just ended up deleting my log folder, there goes a week and a half of training ;_;

This grey effect seems very weird, id make sure that your data has the correct format [-1,1] and that you use sampling.clip_before=True and model.version=DDPM during sampling.
The easy hacky way to do it would be to do use data.num_frames_cond=1 with data.prob_mask_cond=1 during training, this way it always mask the single conditional frame and its always just unconditional. vid-gen will still do video prediction conditional, but you can just ignore it. If you want to remove conditional generation, here's a suggestion: In https://github.com/voletiv/mcvd-pytorch/blob/master/runners/ncsn_runner.py, remove lines 1508 to 1571 and then change the if statement in line 1573 so it activates this one to prevent fvd/ssim/etc calculation.
.

hi, thanks for your great work.

Hi! Thanks for your great work.
I am wondering what is the exact data resolution of the unconditional generation on UCF-101?
I have seen the paper report the FVD metrics in table 6 (Unconditional generation of UCF-101 video frames.) in the main paper, however, I am confused about the data resolution.


Improve :: replace step translation to mongo

We have to support multiple replacements at once.
API:
{
   name: 'replace',
   search_column: "COUNTRY",
   new_column: "REGION"
   to_replace:
     'France': 'Europe',
     'USA': 'North America',
}

Closes https://github.com/ToucanToco/vue-query-builder/issues/115

Codecov Report

Merging #119 into master will increase coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   86.03%   86.14%   +0.11%
==========================================
  Files          13       13
  Lines         358      361       +3
  Branches       40       40
==========================================
+ Hits          308      311       +3
  Misses         42       42
  Partials        8        8

Impacted Files
Coverage Δ

src/lib/translators/mongo.ts
96.85% <100%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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


Faild save file in vscode

I have a problem with not saving the code in VS Code
I have Windows 10 operating system and have ESET
And when I want to save the code with an error
Failed to save file: Insufficient permissions. Select 'Retry as Admin' to retry as administrator
How can I fix the problem?

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!

:sob:


Checkbox flattening sets value to 0 when it should be 1

When specifying chebox variables, the packacke gives the boxes filled value 0 when ISEE expect 1 during flattening.

Rounding error


Internal technical Documentation created/updated (Create ADR)

Example usecase:

Further questions:

Will replication always only work on the latest or on all in spec (SemVer of Component status)?
Should a successful replication automatically result in creation of a component and resource CRs?
How many replication attempts do you want to keep in replication CR status?

More to follow up on:

extend config type transport.ocm.config.ocm.software to support more options of ocm transfer componentversions?
is it Ok that the when replication the component is re-downloaded from the source registry?

Hello @frewilhelm
I have a question about the above diagram.    In SAC we are hoping to move to OCM-Controller+Flux for deployment and we are anticipating that the deployment controllers would only be on MCP.
However the diagram above appears to show things not working as we hoped.    Or perhaps it it not related to our case?

Hi @dee0, the diagram only shows one possible setup. The setup you are describing is another use-case that will work as well using the kubeconfig fields in Flux to remotely deploy into the runtime clusters.

We now move to the review phase as most ADRs are initially created and in phase of constant feedback. We plan to slowly move ahead with the merge after incorporating feedback.


Latest version in stackage

Hi there, it's me again,
Do you think it would be possible to include the latest version of the package in the current Stackage snapshot? I'm not sure what the way forward is, but I'm willing to contribute if I can.
Thanks a lot,

Closing this issue as new version <IP_ADDRESS> is now in lts-11.0 snapshot. Thanks!


Readme: wrong link to the lpac fork

https://github.com/stich86/lpac-libmbim-wrapper/blob/d467bd83c0f28843d7d191652e8f16e11d2b22e0/README.md?plain=1#L142
The link points to this repo and not to the lpac (or whatever) fork, appears to be wrong.

Also, could you elaborate (maybe in the Readme) on why MbedTLS doesn't suit?
Maybe create an issue upstream to not maintain the fork, then?
Thanks.

Problem was related to cipher suite used by remote server.
When I first tested lpac had problems with mbedtls. Switched to OpenSSL resolved the issue.

Fixed the link to my repo link

When I first tested lpac had problems with mbedtls.

@stich86 Could you provide the error in the Readme?
Thanks.

Sorry don't have a time.
Build by yourself and run a simple profile add and check with a tcpdump the error


docs: typo fix for INSTALLATION.md

1.Describe what this PR did
Fix typo found in the installation guide
2.Does this pull request fix one issue?

3.Describe how you did it
4.Describe how to verify it
5.Special notes for reviews

LGTM, thanks a lot for your contribution. Merging...


Maven SNAPSHOT artifacts still dont work.

The website explicitly states availability of snapshots: https://duckdb.org/docs/installation/?version=main&environment=java&download_method=package_manager
However, the org.duckdb:duckdb_jdbc:0.10.4-SNAPSHOT can't be found.
Execution failed for task ':JSQLTranspiler:compileTestJava'.
> Could not resolve all files for configuration ':JSQLTranspiler:testCompileClasspath'.
   > Could not find org.duckdb:duckdb_jdbc:0.10.4-SNAPSHOT.
     Searched in the following locations:
       - file:/home/are/.m2/repository/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/maven-metadata.xml
       - file:/home/are/.m2/repository/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/duckdb_jdbc-0.10.4-SNAPSHOT.pom
       - https://repo.maven.apache.org/maven2/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/maven-metadata.xml
       - https://repo.maven.apache.org/maven2/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/duckdb_jdbc-0.10.4-SNAPSHOT.pom
       - https://oss.sonatype.org/content/repositories/snapshots/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/maven-metadata.xml
       - https://oss.sonatype.org/content/repositories/snapshots/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/duckdb_jdbc-0.10.4-SNAPSHOT.pom
       - https://s01.oss.sonatype.org/content/repositories/snapshots/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/maven-metadata.xml
       - https://s01.oss.sonatype.org/content/repositories/snapshots/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/duckdb_jdbc-0.10.4-SNAPSHOT.pom
       - https://oss.sonatype.org/content/groups/public/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/maven-metadata.xml
       - https://oss.sonatype.org/content/groups/public/org/duckdb/duckdb_jdbc/0.10.4-SNAPSHOT/duckdb_jdbc-0.10.4-SNAPSHOT.pom
     Required by:
         project :JSQLTranspiler

I am publishing SNAPSHOTS to all of my projects, so how can I help best to make this work for Java DuckDB too?

Even the Binary Blob seems to be outdated:

We've fixed the snapshot version number on the website, thanks for that. And yes, you're correct, presently only the java portion of the jdbc driver is nightly, now that we've moved to a standalone repo. We're hopefully going to add support break, but it may take time.
Feel free to raise a seperate issue for that if it's important to you


[Home] Update home tab switching method

Based off @ashfurrow's comment, using the Page prop is indeed cautioned against.
Originally we went for this, as changing tab through just the initialPage prop wasn't working, however we are now switching to the recommended goToPage function. (thanks @ashfurrow!)
🎉

Yeah, OK, this makes sense 👍

I can't wait for "merge on green" functionality 💕

It's about to happen: https://github.com/artsy/peril-settings/pull/59


0.9.0 broke positional argument passing

I haven't had time to investigate this too much yet, but updating from 0.8.0 to 0.9.0 broke RasterizeXCAssets, even though my understanding was that the only breaking change should be requiring a more recent version of Swift?
When positional arguments is missing, it correctly prints that it's missing those arguments. But when they are given it prints an "Unknown Arguments" error:
$ swift run rasterizexcassets
[0/0] Build complete!
An error occurred: Missing value for `source`

$ swift run rasterizexcassets a
[0/0] Build complete!
An error occurred: Missing value for `output`

$ swift run rasterizexcassets a b
[0/0] Build complete!
Unknown Arguments: a b

Here is the code used to set up the command:
func main(source: String, output: String, size: Size) throws {
    // ...
}

command(
    Argument<String>("source", description: "Source SVG file"),
    Argument<String>("output", description: "Output path for resulting asset"),
    Option<Size>("size", default: Size(width: 64, height: 64), description: "Size (in points) of the output asset (e.g. 120x120)"),
    main
).run()

I'm not able to reproduce what you are seeing. Could you please compare against a test project. I've included a tarball in https://flr.li/F1cZ7x .
$ curl -s https://flr.li/F1cZ7x | tar xv
Package.resolved
Package.swift
Sources/
Sources/test/
Sources/test/main.swift

$ cat Sources/test/main.swift
import Commander

func main(source: String, output: String, size: String) throws {
    // ...
    print("Source \(source)")
    print("Output \(output)")
    print("Size \(size)")
}

command(
    Argument<String>("source", description: "Source SVG file"),
    Argument<String>("output", description: "Output path for resulting asset"),
    Option<String>("size", default: "64x64", description: "Size (in points) of the output asset (e.g. 120x120)"),
    main
).run()

$ swift run test
...
Creating working copy for https://github.com/kylef/Commander
Working copy of https://github.com/kylef/Commander resolved at 0.9.2
[19/19] Build complete!
An error occurred: Missing value for `source`

$ swift run test a
[0/0] Build complete!
An error occurred: Missing value for `output`

$ swift run test a b
[0/0] Build complete!
Source a
Output b
Size 64x64

$ swift run test a b --size 128x128
[0/0] Build complete!
Source a
Output b
Size 128x128

Sorry for not getting to this, I will investigate further to se what the problem is, will reopen if I run into more problems. Thank you for taking time on this!


rails_blob_path always renders with only_path: true

Does that actually work for files on an external host? E.g. S3 / CloudFront, Google Cloud Storage

Not sure. Don't have app that uses S3. I talked to somebody who does, and it seems that it works fine if storage is configured to use cloud hosts. For local storage it doesn't cram full though. Please confirm though.

Closing this for now and will re-open if there are any issues


feat: Allow per-image configuration of pull secrets

Is your feature request related to a problem? Please describe.
Currently, image pull secrets can only be specified on a per-registry basis. That means you'd need one credential that has access to all images from this registry, which might not be possible in some scenarios.
Describe the solution you'd like
It should be possible to define Image pull secrets on a per image (or per repository) basis, using an annotation on the application resource. Depending on further design decisions (like, access to remote clusters), it could also be viable to use the imagePullSecret property of existing workloads to figure out what pull secret to use.

Implemented by #52


A benchmark isn't a benchmark w/out something to compare against

If users post their results, we'll all have something to compare against.  Here is one from me to get it started.

Benchmark

math
1.652

string
2.239

loops
0.072

ifelse
0.133

connect
0.001

select_db
0.001

query_version
0.001

query_benchmark
10.707

total
14.803

Tested on a mac mini with Debian installed:

@odan I love the simplicity of this and the way you have written it. I saw this issue by @jrogers512 and saw what he was trying to accomplish by starting this thread, but this still isn't really a decent way to compare results.
On first glance though, while I’m sure you have plenty to do, I can see a relatively easy way to accomplish a REAL benchmark/comparison, without effecting your scripts performance. Would just take a bit of your time to write. This could be a great way to see just how many people are using your script, as well as something to actually compare results to. FYI, this is the first result when you search google for "php mysql benchmark", so it probably gets some use.
My idea is, add a form to your output html with hidden inputs. and pre-populate those inputs using the test results. Name the submit button "Compare Results", and have the form post data to another php file on your own website.,
the php on your website will add the data to an sql database, and you could query it based on the platform, and mysql/php version. You could then average the columns, and present the user with a visual representation (css/js?) of their performance, in comparison to others using the same software.
I guess you'd want perform some data validation to prevent bogus data from being posted and ending up in your tables, be it with malicious intent or just by someone who modified the code and broke it. You could also store a separate table for posts with the client ip and server time, so you could limit posts per IP per day, and avoid any individual abusing resources.
Anyway, just an idea. I'm very new to PHP and mysql, so there's probably far better ways of doing it. that’s just what came to mind and what i thought of when i saw this thread

Hi @geelongmicrosoldering

but this still isn't really a decent way to compare results.

The original idea of this script was to compare only its own servers.

this is the first result when you search google for "php mysql benchmark"

Cool :-)

representation ... in comparison to others using the same software.

Comparison with foreign servers was never the main goal, but it's sounds interessting.
If there are more people who like this idea, I might implement something.
Thanks for your feedback :+1:

The Idea is intresting, and yeah having something to compare would be great to know how good or ugly one's values are.
for example on netcup webhosting the calc total is about 0,4 sec but MySQL is like 8,4, which obviously looks crazily high but as I said without knowing how demanding the bench is (e.g. by seeing how others compare), well I guess you get my point.

Dev Server
1 core ( VirtualBox - Ryzen 7 1700 @ 3.00GHz )

Main Production Server
2 core (Xeon Gold 6136 @ 3.00GHz)

While this benchmark shows better performance out of the dev server, in real life, PHP scripts run much faster on the production server. For example, the production server can load the WordPress admin in about 140ms while my dev server averages about 400ms; but I suspect some of that has to do with the virtualized environment I am running.

@joshrowland Make sure that xdebug is not enabled (on your dev server).

@odan, I did get a notice about that when I first ran benchmark-php and disabled it for these tests. Thanks for mentioning that!

Does anyone knows how to make the string test after?

SiteGround, server stats unknown

Serverless mysql amazon setup

000webhost free site


Issues 15 - DSL for Wiremock verify API

Codecov Report

Merging #23 (a177cf1) into master (843bfaf) will increase coverage by 2.17%.
The diff coverage is 98.78%.

@@             Coverage Diff              @@
##             master      #23      +/-   ##
============================================
+ Coverage     92.41%   94.58%   +2.17%
- Complexity       58       74      +16
============================================
  Files            10       13       +3
  Lines           290      351      +61
  Branches         23       29       +6
============================================
+ Hits            268      332      +64
+ Misses           19       17       -2
+ Partials          3        2       -1

Impacted Files
Coverage Δ

...om/marcinziolo/kotlin/wiremock/WireMockInstance.kt
84.21% <85.71%> (+10.87%)
:arrow_up:

...otlin/com/marcinziolo/kotlin/wiremock/CountStep.kt
100.00% <100.00%> (ø)

...arcinziolo/kotlin/wiremock/RequestSpecification.kt
98.43% <100.00%> (+0.93%)
:arrow_up:

...marcinziolo/kotlin/wiremock/VerifySpecification.kt
100.00% <100.00%> (ø)

...main/kotlin/com/marcinziolo/kotlin/wiremock/api.kt
86.40% <100.00%> (+2.03%)
:arrow_up:

...lin/com/marcinziolo/kotlin/wiremock/dslAdapters.kt
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


arangodump corrupts unloaded collections

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[X] 3.3

Mode:

[X] Single-Server

Storage-Engine:

[X] mmfiles

On this operating system:

[X] Linux

[X] Debian .deb

Problem description:
Command arangodump corrupts collections which are in "unloaded" state when command is issued.
These are the steps to reproduce:

open linux terminal (ssh to server)

run command "arangodump --output-directory /tmp/arangodump --server.database somedb --server.username someuser --server.password somepass"

dump crashes on the first "unloaded" collection with error "2018-02-20T09:20:28Z [4365] ERROR got error from server: HTTP 404 (Not Found): ArangoError 1203: collection not found"

affected collection changes its state from "unloaded" to "corrupted"

Version:
3.3.3
architecture: 64bit
arm: false
asan: false
asm-crc32: true
assertions: false
boost-version: 1.62.0
build-date: 2018-01-25 20:21:22
build-repository: tags/v3.3.3-0-g5819c24e24
compiler: gcc [5.4.0]
cplusplus: 201103
debug: false
endianness: little
failure-tests: false
fd-client-event-handler: poll
fd-setsize: 1024
full-version-string: ArangoDB 3.3.3 [linux] 64bit, using jemalloc, VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.0.1t  3 May 2016
icu-version: 58.1
jemalloc: true
maintainer-mode: false
openssl-version: OpenSSL 1.0.1t  3 May 2016
platform: linux
reactor-type: epoll
rocksdb-version: 5.6.0
server-version: 3.3.3
sizeof int: 4
sizeof void*: 8
sse42: false
unaligned-access: true
v8-version: 5.7.492.77
vpack-version: 0.1.30
zlib-version: 1.2.11

Hi @zpolisensky,
i tried to reproduce it with the current version 3.3.3 using Ubuntu 17.04 and a custom user/database but arangodump worked for me. Collections, that are unloaded before executing arangodump, are loaded when it is finished. Is there anything else to consider? Does this error only occur when using a non-root user and not the _system database?

Hi @maxkernbach ,
I did more testing and found out that it does not happen if Arango was upgraded from any previous version so it must be clean installation (it fine just to purge it from the system: sudo apt purge arangodb3). My OS is Debian 8.0. I'm using non-root, read-only user on not the _system DB.

Could you please provide further information on your collection size and count? This would be helpful to reproduce your issue. Thanks!

Hi Max,
here is more information:

dump works fine if authentication is disabled "authentication = false"
dump work fine if user used for it has "Administrative" access
dump fails if user has only "Access" level of permissions
So it looks that user with "Access" permissions do not have ability to load collection as it works earlier versions of Arango.
Good news are that collection switch to corrupted state are OK after Arango restart.

OK, I found how to make it work for every user:
Everything is done in User menu on user configuration level:

Add user "Access" level privileges on database
Click on database name to drop down to collections level
Do down to "*" (Default access level for collections) and set also "Access" level
Dumb now works

Hi,
I'm trying to reproduce this but failed.
I've used collections in the _system database and the test database;
Cutting two screenhots from the permissions of the user to one:

The user needs access to the test database, else dumping fails from the start:
2018-03-01T13:09:04Z [3445] ERROR Could not connect to endpoint 'tcp://<IP_ADDRESS>:8529', database: 'test', username: 'test'
2018-03-01T13:09:04Z [3445] FATAL Error message: 'got error from server: HTTP 401 (Unauthorized)'

can you pin in my screenshot which permission I should change so this happenes?

ah, hang on - just a second to early - got it reproduced.

will be addressed with https://github.com/arangodb/arangodb/pull/4725

Hi @zpolisensky ,
Thanks for reporting this bug
We have released 3.3.4, and it includes a fix for it
I am closing this ticket now. Please feel free to reopen if the problem persists


Doc fix

fixes #44

Codecov Report

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

@@           Coverage Diff           @@
##           master     #129   +/-   ##
=======================================
  Coverage   99.35%   99.35%
=======================================
  Files          19       19
  Lines        2029     2029
=======================================
  Hits         2016     2016
  Misses         13       13

Impacted Files
Coverage Δ

lib/google/gax/settings.rb
99.01% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Support for Babelfish v4.0.0

Description
Support for Babelfish v4.0.0
Issues Resolved
Support for Babelfish v4.0.0
Check List

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

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thank you!
Rob Verschoor
AWS | Principal Database Engineer, RDS
<EMAIL_ADDRESS>|  T +31-655-772131 | twitter: @rob_verschoor
From: Hong @.>
Sent: Friday, February 16, 2024 19:21
To: babelfish-for-postgresql/babelfish_compass @.>
Cc: Verschoor, Rob @.>; Author @.>
Subject: Re: [babelfish-for-postgresql/babelfish_compass] Support for Babelfish v4.0.0 (PR #121)
@hong-yuan approved this pull request.
LGTM.
—
Reply to this email directly, view it on GitHubhttps://github.com/babelfish-for-postgresql/babelfish_compass/pull/121#pullrequestreview-1885744905, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVYPZMH5QIHVTTZRLOHXEZTYT6PPBAVCNFSM6AAAAABDMND566VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOBVG42DIOJQGU.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>Amazon Development Center (Netherlands) B.V., Johanna Westerdijkplein 1, NL-2521 EN The Hague, Registration No. Chamber of Commerce 56869649, VAT: NL 852339859B01


Gets stuck at Step 12 on AWS

I'm trying to set up a HOT wallet claimer via AWS and after inputting the seed phrase it gets stuck at Step 12:

"Attempting to click the storage link"
In one of my many attempts it went a little further, claiming that an error occurred while trying to clear overlays:

I think it bricks my EC2 instance because restarting the ShellNGN window gives me a "connection closed" timeout error and I have to reboot the instance via AWS panel.

Alright, after about an hour of stepping away it suggests it timed out trying to find an iframe:

I started everything from scratch step by step and it got stuck nonetheless, now at step 5:

Hi,
The setup process should only take a couple of minutes—I recently recreated over 60 accounts in about an hour.
What server specifications are you using? It sounds like you might be running out of RAM.
You can check your memory usage with the following command:
free -m

As mentioned in some of the closed issues, if you’re on a limited RAM AWS account, consider using an ARM64 server. This setup is tied to an older version of Chrome, which tends to use less memory.

I followed the video setting up an Amazon VPS 1:1 with a default instance type t3.micro.
I'll try ARM64 for sure.

At the time of recording the video, the setup was successfully hosting 8 or 9 accounts using that method. Unfortunately, since then, the baseline RAM requirements of the third-party software seem to have increased, impacting its ability to run on a 1 GB server.

Right, so would I have to go with an instance of at least 2gb of memory? Is there any clue as to how much it would cost per month running say 10 HOT accounts given that the free tier is limited to micro with 1gb of memory?

Hi,
The costs can vary depending on the data center hosting the script, but there’s an option that might work well for testing:
When creating an instance, search for:
Minimal Ubuntu 22.04 LTS - Jammy

I set up a test instance on an AMD-64 bit, t2.micro instance (free-tier eligible), and was able to create six accounts with some RAM to spare.
If the free tier doesn’t quite cover the number of accounts you want, it might be worth moving to a different provider after testing. Many offer servers with 2 GB RAM for around $2-3 per month, which could be a good alternative.

Awesome, I got it working finally. Are there any particular providers at that cost that I could check out?

Well, while I managed to add the processes successfully after upgrading an instance to x64 ARM and bigger RAM, it still fails:

Error encountered: expected string or bytes-like object, got 'bool' right after it attempts to locate storage.

Hi,
You need to follow the troubleshooting guide: https://github.com/thebrumby/HotWalletClaimer/issues/166

Enable verbose 3
Enable debugging and look at the screenshots from the virtual browser

Alright well, it didn't get to the storage step this time:

I just re-ran the exact same thing again and no chrome crash happened.

Despite the log saying "Was successfully able to enter the seed phrase", based on the screenshots it doesn't do anything:

All the rest of the screenshots for the consequent steps are just staring at the import wallet starting screen on the app.
However, there is one account that I claimed manually just a short while ago, and the debug screenshots show that it does enter the seed and access the wallet:

I don't know what to make of any of this. The other handful of accounts that I run from my PC work fine.

For the accounts that don't get stuck on the entry screen. I set up the forced claim in settings but judging from screenshots it's stuck because of the "check news" button.


support multiline responses from tor to applications

this requires https://github.com/Yawning/bulb/pull/4

looks good to me but we cannot merge it until the upstream bulb changes are merge or your change the import statements to point to your fork of bulb.


"npm init -y influx-node-app" Not found

I follow the first step of the instruction but receive error from npm:
$ npm -v
10.8.2
$ npm init -y influx-node-app
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/create-influx-node-app - Not found
npm error 404
npm error 404  'create-influx-node-app@*' is not in this registry.

Relevant URLs

https://docs.influxdata.com/influxdb/cloud/api-guide/client-libraries/nodejs/install/

Thanks for pointing this out. npm init -y <new-package-name> no longer works the same way.
The command npm init -y <new-package-name> is incorrect and causes npm to search for a package named create- in the npm registry, which results in a 404 error if such a package does not exist.
Correct Usage
Creating a New Directory for the Package
If you want to create a new directory for your package and initialize it there, you should first create the directory and then run npm init inside it. If you want to use package defaults, include the -y  flag:
mkdir influx-node-app
cd influx-node-app
npm init -y

You can also do something like the following to configure the package:
npm init -y; npm pkg set type="module"


Remove unneeded credentials

For read access to the GitHub container registry, we do not need any credentials like the CR_PAT secret which I think stands for "container registry personal access token".
This pull request removes the unneeded credentials from the android-release.yml workflow.

This still leaves me a little curious. Why do we not need any credentials to access Github container registry?

It is public for read access

You can run docker run --rm -it ghcr.io/maplibre/android-ndk-r21b  on your local machine and it will take you into the container.

Only when you want to write to the github docker registry, e.g. in
https://github.com/maplibre/maplibre-gl-native/blob/2478d54261908711cbea89de4d4212917e021f9f/.github/workflows/android-docker-ndk-r21b.yml#L16-L29
you will need the credentials...


Feature request: make it a a standalone app

The new settings and welcome even for those who are not using nwg-shell. It would be great to be able to install it as a standalone application. instead of lxappearence.

LOL, what stops you from doing so? I know some people who use nwg-look with X11.

I must have been tired yesterday, I don't know how I missed this is AUR. :facepalm:
aur/nwg-look 0.1.4-1 (+6 1.45)
    GTK3 settings editor adapted to work in sway/wlroots environment
aur/nwg-look-bin 0.1.4-1 (+7 1.34)
    GTK3 settings editor adapted to work in the sway/wlroots environment (binary package)

Thanks for the answer. I'm closing the issue.
BTW, awesome project!

Thank you!


Issue 139

Closes #139

Codecov Report

Merging #140 into develop will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #140      +/-   ##
===========================================
+ Coverage    96.56%   96.59%   +0.03%
===========================================
  Files           14       14
  Lines         2944     2970      +26
  Branches       445      447       +2
===========================================
+ Hits          2843     2869      +26
  Misses          50       50
  Partials        51       51

Impacted Files
Coverage Δ

rflx/expression.py
93.7% <100%> (+0.2%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix docs layout on big screen

The white container should be aligned to the left. This happens on big screens (width 1600+px)

Me! Let me fix this issue.
This will be my first open source contribution if I can fix this issue! :)

Fixed in 0.0.19


Lettuce can't connect to Redis Cluster + SSL but can connect to same Redis server + SSL if treated as Standalone node.

Bug Report
Current Behavior
I've an Azure Cache for Redis - Premium and Cluster enabled. I've been trying to connect to that Redis using spring-boot-starter-data-redis (spring boot version: 2.3.4.RELEASE, Java version: 11) and using lettuce client but Lettuce is throwing SSL exception when I am treating my Redis as a Redis Cluster but connects just fine when using it as a Standalone Redis server.

Stack trace
java.lang.IllegalStateException: Failed to execute CommandLineRunner
    at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:798) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
    ...
Caused by: org.springframework.data.redis.RedisConnectionFailureException: Redis connection failed; nested exception is io.lettuce.core.RedisConnectionException: Unable to connect to [RedisURI [host='<redacted>.redis.cache.windows.net', port=6380]]
    at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:66) ~[spring-data-redis-2.3.4.RELEASE.jar:2.3.4.RELEASE]
    ...
Caused by: io.lettuce.core.RedisConnectionException: Unable to connect to [RedisURI [host='<redacted>.redis.cache.windows.net', port=6380]]
    at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78) ~[lettuce-core-5.3.4.RELEASE.jar:5.3.4.RELEASE]
    ...
Caused by: javax.net.ssl.SSLHandshakeException: No subject alternative names matching IP address <redacted> found
    ...
Caused by: java.security.cert.CertificateException: No subject alternative names matching IP address <redacted> found
    at java.base/sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:165) ~[na:na]
    ...

Input Code

Input Code
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.autoconfigure.data.redis.RedisProperties;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.redis.connection.*;
import org.springframework.data.redis.connection.lettuce.LettuceClientConfiguration;
import org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory;
import org.springframework.data.redis.core.StringRedisTemplate;

@Configuration
class LettuceConfig {

    @Bean
    StringRedisTemplate getStringRedisTemplate(final RedisProperties redisProperties) {
        return new StringRedisTemplate(getRedisConnectionFactory(redisProperties));
    }

    @Bean
    RedisConnectionFactory getRedisConnectionFactory(final RedisProperties redisProperties) {

        final RedisNode redisNode = RedisNode.newRedisNode()
                .listeningAt(redisProperties.getHost(), redisProperties.getPort())
                .build();

        // Connecting as a Redis Cluster
        final RedisClusterConfiguration redisClusterConfiguration = new RedisClusterConfiguration();
        redisClusterConfiguration.addClusterNode(redisNode);
        redisClusterConfiguration.setPassword(RedisPassword.of(redisProperties.getPassword()));

        // Connecting as a Standalone Redis server
        final RedisStandaloneConfiguration redisStandaloneConfiguration = new RedisStandaloneConfiguration();
        redisStandaloneConfiguration.setHostName(redisProperties.getHost());
        redisStandaloneConfiguration.setPort(redisProperties.getPort());
        redisStandaloneConfiguration.setPassword(RedisPassword.of(redisProperties.getPassword()));

        final LettuceClientConfiguration.LettuceClientConfigurationBuilder lettuceClientConfigurationBuilder =
                LettuceClientConfiguration.builder()
                .clientName(redisProperties.getClientName())
                .commandTimeout(redisProperties.getTimeout());

        if (redisProperties.isSsl()) {
            lettuceClientConfigurationBuilder.useSsl();
        }

        final LettuceClientConfiguration lettuceClientConfiguration = lettuceClientConfigurationBuilder.build();

        return new LettuceConnectionFactory(redisClusterConfiguration, lettuceClientConfiguration);
    }
}

@SpringBootApplication
public class LettuceClusterApplication implements CommandLineRunner {

    private final StringRedisTemplate stringRedisTemplate;

    @Autowired
    public LettuceClusterApplication(final StringRedisTemplate stringRedisTemplate) {
        this.stringRedisTemplate = stringRedisTemplate;
    }

    public static void main(String[] args) {
        SpringApplication.run(LettuceClusterApplication.class, args);
    }

    @Override
    public void run(String... args) throws Exception {
        System.out.println(stringRedisTemplate.hasKey("abc"));
    }
}

pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.3.4.RELEASE</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>
	<groupId>com.example</groupId>
	<artifactId>lettuce-cluster-connect</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>lettuce-cluster-connect</name>
	<description>Demo project for Spring Boot</description>

	<properties>
		<java.version>11</java.version>
	</properties>

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-data-redis</artifactId>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
			<exclusions>
				<exclusion>
					<groupId>org.junit.vintage</groupId>
					<artifactId>junit-vintage-engine</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
	</dependencies>

	<build>
		<plugins>
			<plugin>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-maven-plugin</artifactId>
			</plugin>
		</plugins>
	</build>

</project>

My application.properties file:
spring.redis.host = <redacted>.redis.cache.windows.net
spring.redis.port = 6380
spring.redis.password = <redacted>
spring.redis.ssl = true
spring.redis.clientName = ${HOSTNAME}
spring.redis.timeout = 100000

Expected behavior/code
Lettuce should've been able to connect to Redis Cluster just fine and run the command just like it did when treating it as a standalone Redis node.
Environment

Lettuce version(s): 5.3.4.RELEASE (bundled under spring-boot-starter-data-redis)
Redis version: 4.0.14

Additional context
Found a similar GitHub issue: https://github.com/lettuce-io/lettuce-core/issues/246
and the documentation link: https://lettuce.io/core/release/reference/#ssl which both basically states that this issue is fixed with Lettuce version > 4.2. Quoting the relevant part of the documentation:

Lettuce supports SSL connections since version 3.1 on Redis Standalone connections and since version 4.2 on Redis Cluster.

Link to StackOverflow question: https://stackoverflow.com/q/64287424/3160529

The linked ticket #246 and #209 are about general SSL support for Redis Cluster.
This report is related to the fact that the Redis certificate doesn't contain Redis cluster IP addresses. The Redis cluster topology is based on IP addresses, not hostnames (see https://redis.io/commands/cluster-nodes). Enabling SSL also enables SSL certificate validation. No subject alternative names matching IP address basically means that the supplied SSL certificate doesn't list the target IP address.
There are a couple of things you can do about:

If the Redis IP addresses can be mapped onto a hostname, then please configure a MappingSocketAddressResolver through ClientResources to map IP addresses into hostnames that are listed in the SSL certificate
Reach out to the Azure support team so that they fix the SSL certificates and include all cluster IP addresses
(least favorable option) Disable SSL certificate validation. That can be done with RedisURI.setVerifyPeer(false) when using Lettuce directly. For Spring, you should be able to register a LettuceClientConfigurationBuilder customizer to invoke LettuceSslClientConfigurationBuilder.disablePeerVerification().

@mp911de Thanks for the response. We're currently using the 3rd option to continue our operations but are also planning on discussing with Azure team as well for this. Will update this issue as I get more information on this.

FTR, with #1460 we want to improve on TLS verification options

@mp911de on Azure Redis, the cluster node addresses are always on the same IP that the DNS (cacheName.redis.cache.windows.net) points towards.
With this in mind, can we possibly change the default SocketAddressResolver to an implementation that verifies/provides a default mapping if the IPs can be mapped/resolved to one of the initialURIs with a DNS hostname?
This will definitely be a lot more secure since most people right now might be defaulting to the 3rd and the least favorable option simply because it is the easiest to do.

For reference, I also had a look how StackExchange.Redis does the host verification and it seems that they infer the hostname from the initial config rather than try using the IP endpoints directly which does not also seem like a bad idea.
https://github.com/StackExchange/StackExchange.Redis/blob/main/src/StackExchange.Redis/ConfigurationOptions.cs#L807

Since there isn't anything actionable on this ticket, I'm going to close it. If you would like us to look at this issue, please provide additional information and we will re-open the issue.

Thanks @mp911de . I'm not up on the details but I think @aravindyeduvaka provided an actionable suggestion to change the default SocketAddressResolver? Alternatively, could an example be provided for suggestion 1 with a MappingSocketAddressResolver that handles this? I took a look at this and wasn't able to easily figure out how to do this. I suspect suggestion 2 is unlikely to get traction and I'm unwilling to go with suggestion 3. Thanks for the great work you do.

We're not going to change SocketAddressResolver for a functionality that isn't reflecting any operational defaults but something that introduces complexity caused by Azure.
Note this is a community project, that isn't sponsored by Microsoft or anyone else, and our maintainers are the ones who are left with trying to figure out way how to cope with quirks of AWS, RedisLabs, Azure,... you name it. Hence we're reluctant to introducing provider-specific quirks.
You can find an example of how to solve the issue via MappingSocketAddressResolver at https://github.com/lettuce-io/lettuce-core/blob/1e334f68aaa3cbd6a021e0b699c85a450551f42d/src/test/java/io/lettuce/core/resource/MappingSocketAddressResolverUnitTests.java#L69-L70

This is a ticket for Azure feedback to possibly resolve this from their side
https://feedback.azure.com/forums/169382-cache/suggestions/42831483-the-certificate-of-azure-redis-in-cluster-mode-sho

I found these docs from azure on "Lettuce best practices": https://github.com/Azure/AzureCacheForRedis/blob/main/Lettuce Best Practices.md
They recommend basically the same (copying the code from that link):
    Function<HostAndPort, HostAndPort> mappingFunction = new Function<HostAndPort, HostAndPort>() {
        @Override
        public HostAndPort apply(HostAndPort hostAndPort) {
            InetAddress[] addresses = new InetAddress[0];
            try {
                addresses = DnsResolvers.JVM_DEFAULT.resolve(host);
            } catch (UnknownHostException e) {
                e.printStackTrace();
            }
            String cacheIP = addresses[0].getHostAddress();
            HostAndPort finalAddress = hostAndPort;

            if (hostAndPort.hostText.equals(cacheIP))
                finalAddress = HostAndPort.of(host, hostAndPort.getPort());
            return finalAddress;
        }
    };

    MappingSocketAddressResolver resolver = MappingSocketAddressResolver.create(DnsResolvers.JVM_DEFAULT,mappingFunction);

    ClientResources res =  DefaultClientResources.builder()
            .socketAddressResolver(resolver).build();


Refactor EXIF stripping for images

Context for change: I got really annoyed with the trouble involved in installing one of the pygobject subdependencies, so I spitefully refactored the code it was used in to do away with pygobject and use pillow, which was already in the requirements list. That happened to be the function that strips EXIF data from images.
Test steps

Upload test image containing verified EXIF data to dev server
Check EXIF data in image saved in /stor
Verify that image served by dev site is browsable and also contains no EXIF data when downloaded

Thanks for the PR! Didn't knew PIL could strip EXIF data

AFAIK it's because PIL doesn't actually know how to handle EXIF data that this works.


Refactor - Home page

[x] merge Skill Page, something like "Setup" or "Uses"

72044bafac8862954e3e6484771e7072dc070605


Add a real time raid guide.

For newer players and hard raids like UBHL, Akasha, and the promised focus on new HL content this year.
Displays info on triggers and notes on gameplay based on current raid status.

The idea is to create a very simple data set with name, general advice/reminders (short), triggers & ougis, their activation requirements (HP, OD/N, (de)buffs maybe), and specific notes.
Then display relevant data in a new UI panel, updating as required.
For the extra mile; some form of colour warnings for (de)buffs and particularly bad triggers could be fun.
A simple block data structure should suffice but none in particular is yet set.

any news on this I was planning on requesting the same Idea but instead just pull out the Raid page that I'm currently running.

I'm having a busy time and am not actively playing anymore either so development is slow at best for now. A few bits and pieces are already in the code, but I've not sat down to think about the details. I don't think it should be too hard for anyone interested to complete this however.


FR: Set entry assets' creation date on import

When importing an entry which contains an asset field, I'd like to be able to set that asset's creation date to be the entry's publish date. Currently I'm just importing that date as a separate field for the asset, but it would be a bit cleaner to be able to set the asset creation date from import.

I don't believe we're able to alter the dateCreated attribute on any element, as thats strictly handled by Craft. For Assets, this would be the time of upload of that Asset, not the Entry associated with it.
I'll look into this, but I'm fairly certain its not going to be possible. A separate date field would be the way to go.

Closing, this simply isn't possible with Craft (Craft overrides element creation/update times).


Fix failing tests

There is still one test failing which tests the Cerebral error catching.
It seems that  Jest is not able to not catch the error or fail.
With AVA thows I am able to test this.
Needs further investigation.


MountVolume.SetUp failed for volume "docker-sock" on OKE

Summary
I have a k8s cluster on Oracle kubernetes engine (OKE) with Argo setup on it. Now i upgraded the kubernetes version of the cluster from v1.19.12 to v1.20.8.
Try to deploy the basic hello-world.yaml example in the cluster:
argo submit -n argo --watch https://raw.githubusercontent.com/argoproj/argo-workflows/master/examples/hello-world.yaml -n opstesting

After that, argo workflows are not running properly as the pods cannot be started by giving the error:
MountVolume.SetUp failed for volume "docker-sock" : hostPath type check failed: /var/run/docker.sock is not a socket file

Diagnostics
What Kubernetes provider are you using?
Oracle kubernetes engine (OKE) v1.20.8
$ kubectl version

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.8", GitCommit:"50317190d44dbdb51ae7ff430917b32ba96188b5", GitTreeState:"clean", BuildDate:"2021-06-30T14:20:31Z", GoVersion:"go1.15.13 BoringCrypto", Compiler:"gc", Platform:"linux/amd64"}

What version of Argo Workflows are you running?
$ argo version
argo: v2.11.0
  BuildDate: 2020-09-17T21:01:53Z
  GitCommit: f8e750de5ebab6f3c494c972889b31ef24c73c9b
  GitTreeState: clean
  GitTag: v2.11.0
  GoVersion: go1.13.15
  Compiler: gc
  Platform: linux/amd64

Did this work in a previous version?
Yes, it worked in the previous kubernetes version v1.19.12 .
( It works even when the control-plane version is v1.20.8 and worker nodes version is v1.19.12 In OKE provider.)
Other debugging information (if applicable):
Workflow pod description:
$ kubectl describe pod hello-world-tp4jv -n opstesting

Name:           hello-world-tp4jv
Namespace:      opstesting
Priority:       0
Node:           <IP_ADDRESS>/<IP_ADDRESS>
Start Time:     Tue, 27 Jul 2021 13:24:18 +0530
Labels:         workflows.argoproj.io/completed=false
                workflows.argoproj.io/workflow=hello-world-tp4jv
Annotations:    workflows.argoproj.io/node-name: hello-world-tp4jv
                workflows.argoproj.io/template:
                  {"name":"whalesay","arguments":{},"inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"docker/whalesay:latest","command"...
Status:         Pending
IP:
IPs:            <none>
Controlled By:  Workflow/hello-world-tp4jv
Containers:
  wait:
    Container ID:
    Image:         argoproj/argoexec:v2.11.0
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      wait
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  hello-world-tp4jv (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /var/run/docker.sock from docker-sock (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-fpdmk (ro)
  main:
    Container ID:
    Image:         docker/whalesay:latest
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      cowsay
    Args:
      hello world
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-fpdmk (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  podmetadata:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.annotations -> annotations
  docker-sock:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:  Socket
  default-token-fpdmk:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-fpdmk
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason       Age                   From     Message
  ----     ------       ----                  ----     -------
  Warning  FailedMount  7m26s (x259 over 8h)  kubelet  MountVolume.SetUp failed for volume "docker-sock" : hostPath type check failed: /var/run/docker.sock is not a socket file
  Warning  FailedMount  89s (x139 over 8h)    kubelet  Unable to attach or mount volumes: unmounted volumes=[docker-sock], unattached volumes=[podmetadata docker-sock default-token-fpdmk]: timed out waiting for the condition

Please try with PNS executor instead of Docker

@AnjanaAK

I think we can close this. Re-open if not fixed.

@alexec Could you please re-open this issue? It was not fixed.

Please try with PNS executor instead of Docker

I tried modifying the workflow-controller configuration to use pns executor instead of docker, by editing the configmap :
kubectl edit configmap workflow-controller-configmap -n argo

Added this entry: containerRuntimeExecutor: pns
But now sometimes, some of my workflows are failing with error:
failed to save outputs: Failed to determine pid for containerID e5e38509993337278095fe65: container may have exited too quickly


Add Psalm

This PR wants to introduce psalm to the list of code analyzing tools for deptrac. For now on Level 3 this can be increased later on, if wanted.
Unfortunately i needed to add a baseline because of the graph api. It seems to be inconsistent in the 0.9.1 release.
On the master branch the createVertex method completely changed. So i think the should go for the baseline for now and update as soon a new release got cut for graph and graphiz.

Can the issue with the graph api suppressed? I already did this for phpstan.

Thank you @DanielBadura!


test: blob sizes that are too large

Part of https://github.com/celestiaorg/celestia-app/issues/2156

Codecov Report

Merging #2187 (3b86900) into main (6c72c6d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2187   +/-   ##
=======================================
  Coverage   24.93%   24.93%
=======================================
  Files         127      127
  Lines       14309    14309
=======================================
  Hits         3568     3568
  Misses      10374    10374
  Partials      367      367

It might be better to use a constant and test around that constant

I thought about introducing a constant for the max blob size b/c currently one isn't enforced but I think that requires further discussion.
Since the largest supported blob size isn't a constant now, it has to be calculated based on a few other parameters (max square size, max block bytes) which requires access to state.


Update mongodb-org package for Debian to 3.2

I confirm that Rocket chat works on MongoDB 3.2.

LGTM!

Just successfully tested the installaiton of RocketChat on a DigitalOcean Debian 8.5 droplet.
One little thing, as I tried to initialize the Mongo replication (rs.initiate()), I did run into the following error:
{
    "info2" : "no configuration explicitly specified -- making one",
    "me" : "<IP_ADDRESS>:27017",
    "errmsg" : "couldn't initiate : can't find self in the replset config",
    "ok" : 0
}

Workaround for this, is to comment out the bindip option in /etc/mongod.conf:
net:
  port: 27017
#  bindIp: <IP_ADDRESS>

@unixfox Can you please check if you had to do this as well?

@Sing-Li If I remember correctly you said something yesterday about 3.2 doesn't work yet. What exactly doesn't work? Can't find any issues right now.

@frdmn I don't have any problem with the default configuration (I just added smallfiles):
# mongod.conf
# for documentation of all options, see:
#   http://docs.mongodb.org/manual/reference/configuration-options/
# Where and how to store data.
storage:
  dbPath: /var/lib/mongodb
  journal:
    enabled: true
#  engine:
  mmapv1:
    smallFiles: true
#  wiredTiger:
# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log
# network interfaces
net:
  port: 27017
  bindIp: <IP_ADDRESS>
#processManagement:
#security:
#operationProfiling:
#replication:
#sharding:
## Enterprise-Only Options:
#auditLog:
#snmp:

We are based on Meteor 1.2.1 -  so the potential problems are documented on these two tickets.
https://github.com/meteor/meteor/issues/5809
https://github.com/meteor/meteor/issues/6957
I'm reluctant to recommend 3.2 usage at this time.  We should be upgrading to Meteor 1.4 in a little while - at that time we will "catch up" with the latest mongo.
We can merge this down after our upgrade to Meteor 1.4, thanks.


router: remove optional http filters because it's hcm dependent

Commit Message: router: remove optional http filters because it's hcm dependent
Additional Description:
The ConfigImpl (route table) created by the rds may shared by multiple listeners/hcm. It means that the ConfigImpl should be  hcm independent.
However, in the current codebase, the optional http filters is extracted from the HCM and used for the ConfigImpl creation.
Because the xds cache, the first hcm's http filters list will be used.
This typically a bug or potential error becasue different HCMs may have complete different http filters list and optional configuration.
Risk Level: mid.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.
[Optional Runtime guard:] n/a.

cc @markdroth because you concern #15025

There is a quesion about the PR self:

should a runtime flag to be added? although i think this is a bug. But it was introduced at two years ago. May be some users depend on current behavior?  cc @envoyproxy/runtime-guard-changes cc @mattklein123

There is a quesion about the PR self:

should a runtime flag to be added? although i think this is a bug. But it was introduced at two years ago. May be some users depend on current behavior?  cc @envoyproxy/runtime-guard-changes cc @mattklein123

As my understanding the usecase of is_optional is primary for the case of update, then new optional filter won't break the old envoy. I guess for this case, this new filter will be marked as optional at all HCMs' config, it doesn't make sense in some HCMs are optional and some HCMs aren't optional. I guess this is why this bug won't be found until now. If we directly remove this feature, I guess this will break some users depending on this.
I quickly search the code. maybe we can add the optional config into the hash of the provider
https://github.com/envoyproxy/envoy/blob/7657d0b252e698e04d836c4481e71503d792e9c1/source/common/rds/route_config_provider_manager.cc#L82
Then we can get different provider instances for different optional config
Not sure whether this can be an acceptable temporary fix. if yes, then you can have a better fix later and won't take the risk break some users.

cc @soulxu See https://github.com/envoyproxy/envoy/pull/26097 and related discussion. I think it's similar to your new idea.

@mattklein123 I think I need some more input from the community first.
Will the suggestion from @soulxu be a possible better way to solve this problem?
This is related to rds, so I want consider it more carefully and take various options into account.

I think this is the right behavior, but I suggest combining this PR with #27210.  That way, any user that runs into a problem will be able to solve it with the is_optional mechanism.
I don't entirely understand @soulxu's suggestion, but I think the behavior we want here is:

When we receive the RDS resource, we iterate through the filter configs, checking the type_url for each one to see if that filter impl is supported.
If the filter impl is not supported, the default behavior is to NACK the RDS resource.
If the filter impl is not supported but the entry is marked as is_optional, then we ignore the entry instead of NACKing.

Note that this behavior has already been agreed upon and has been implemented by gRPC.  I don't think we want Envoy to do something different.

When we receive the RDS resource, we iterate through the filter configs, checking the type_url for each one to see if that filter impl is supported.
If the filter impl is not supported, the default behavior is to NACK the RDS resource.
If the filter impl is not supported but the entry is marked as is_optional, then we ignore the entry instead of NACKing.

Do we want the HCM's is_optional apply to the pre-route/vh filter config when is_optional isn't specified in the pre-route/vh filter config?

I don't entirely understand @soulxu's suggestion, but I think the behavior we want here is:

It basically like #26097. We we shared same rds resource and proto config in multiple HCMs. But we may have different config providers based on the optional filters list. Rds resource will be accepted if all config providers validated it.
But this way are more complicate and not sure if has other potential problem.

Of course we can fix current error directly like this PR did. But this error was exist for two years. I worry about the back compatiability. If some users depend on this 'error', orz.
Not sure if a runtime guard enough.

yea, the trouble is we documented this behavior in API doc https://github.com/envoyproxy/envoy/blob/bedd2b6cc19958eb5c57715722ccaf55b1fc7f87/api/envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#L1143-L1144
That is declared behavior, so in theory, removing it isn't right. except we consider this behavior is fully not working, then it is fine to delete it directly. But it work some case, not sure whether have people depend on it.

I don't think that will work, because the set of HCM configs can change over time. Consider the case where we initially have 3 HCM configs that point to the same RDS resource, we ACK that RDS resource, and then later we get a new HCM config that does not work with the RDS resource. At that point, the RDS resource would suddenly be considered invalid, but it's too late to NACK it.

@markdroth yeah, I think you are right. I didn't thought this point in the past. Thanks.

Then, I think there no other choice. I will add a runtime guard and update doc. And also the test.

cc @alyssawilk for runtime guard.

@mattklein123 ready for a formal review

re runtime guard, f it's high risk, or if it's a behavioral change (even if it's a bug fix) please runtime guard.

cc @adisuissa @markdroth for API review, thanks.
cc @snowp for code review, thanks.

/lgtm api

Please also update the PR title and description to reflect the addition of the is_optional field in typed_per_filter_config.  Thanks!

It seems to me that the API allows overriding a config of some filter-type-A with a different filter-type-B, which is why the HCM's is_optional and the FilterConfig's is_optional may have different values. I think this use-case is only implied here, and maybe explaining that in the comments will help.

No, that's not at all the intent.  It's not okay to have the same filter instance name with configs for two different filter types, and is_optional is not intended to change that.
Consider the following example:
// In HCM config, in LDS resource:
http_filters {
  name: "foo"
  typed_config {
    [types.googleapis.com/envoy.extensions.filters.http.rbac.v3.RBAC] {
      // ...
    }
  }
}

// In RDS resource:
typed_per_filter_config {
  key: "foo"
  value {
    [types.googleapis.com/envoy.extensions.filters.http.fault.v3.HTTPFault] {
      // ...
    }
  }
}

Note that both of these resources are valid and will be ACKed, because the client supports both the RBAC and HTTPFault filters.  The config is invalid only when the client attempts to put those two resources together, because the "foo" filter is actually an RBAC filter, and the RBAC filter doesn't understand the HTTPFault config.  The data plane needs to decide how to handle that: it can either fail requests at L7, or it can just ignore typed_per_filter_config entries whose configs are of the wrong type.
Note that we cannot NACK the RDS resource in this case, because when we're validating and caching the RDS resource, we have no way of knowing which set of HCM instances that RDS resource may be used in -- and that set may change over time, even after it's already too late to NACK the RDS resource.  The resource cache in the xDS transport protocol layer requires that each resource be validated independently of any other, which means that you cannot send a NACK based on a problem that is visible only when looking at a combination of more than one resource.
The is_optional field does not change any of the above.  The only purpose of is_optional is to allow new filter types to be configured by the control plane without breaking older clients that don't yet support them.  Its effect is to tell the client that if the filter type is unknown, then it can ignore the filter instead of NACKing the resource.  So, in the above example, if the is_optional field was set in both the LDS and RDS resource, the behavior would be:

If the client supports the RBAC filter, the is_optional field in the LDS resource is a no-op.
If the client does not support the RBAC filter, the filter entry would be ignored instead of causing the LDS resource to be NACKed.
If the client supports the HTTPFault filter, the is_optional field in the RDS resource is a no-op.
If the client does not support the HTTPFault filter, the filter entry would be ignored instead of causing the RDS resource to be NACKed.
If the client supports the RBAC filter but not the HTTPFault filter, then it will configure the RBAC filter in the LDS resource, but it will not use the HTTPFault entry in the RDS resource, so there will be no conflict when putting the two resources together.
If the client supports the HTTPFault filter but does not support the RBAC filter, then it will ignore the RBAC filter entry in the LDS resource, so there will be no filter instance with the name "foo".  It will see the HTTPFault filter in the RDS resource, but that will be a no-op, because there will not be a top-level filter under the name "foo" that could use that override config.

friendly ping @snowp @adisuissa

/assign-from @envoyproxy/envoy-maintainers

/assign-from @envoyproxy/envoy-maintainers

/assign-from @envoyproxy/senior-maintainers

I can do second pass but first can @adisuissa and @markdroth make sure to tag resolved conversation as resolved?  It's a bit hard to read at least parts of diffs with all the comments, and I don't want to resolve anything still in progress

I don't have permission to resolve or unresolve comment threads.  But I commented on the one thread that @alyssawilk resolved that I think is still open.

Hi, @markdroth @adisuissa, could you give a stamp about this PR if it ready for a second pass? Then we can push this to the next phase. 😄

/retest

Tests were fixed and a new test to cover the new exception thowing was added.
Could you giva a new stamp? cc @alyssawilk Thanks.

close #15025


Encoder Bootstrapping

Hi @yuval-alaluf,
Thanks for your awesome project! I have a small question about the encoder bootstrapping.
I have a pre-trained StyleGAN2 model trained on FFHQ with 256x256 output resolution and fine-tuned on an anime dataset. Now, I am trying to train a ReStyle model from scratch using this model and I also used a FFHQ dataset with 256x256 resolution images for training and testing. Am I doing everything right, no anime dataset is needed for the training, only the pre-trained model and a dataset with real images?
Looking forward to your soonest answer!

Hi @gchilingaryan
You are correct. You need to train a model that is able to translate real face images to anime face images. Doing so would be best if you had paired data of real and anime, but as this is probably not the case, you can try training the encoder using only real images (similar to what I did with the toonify). Now, I can't say in advance if what I used to train the toonify task will work for you out of the box, so you may need to play around with it a bit.
However, once you have the real-to-anime model, you can pair it with the ffhq encoder and perform the bootstrapping technique

The thing is when training the ReStyle model, the average anime image is note changing that much during the training (only the background of the image, the hair color and skin tone is changing depending on the input image, but the image is overall the same throughout the training). Is this a normal behaviour, did you have the same results when training the Toonify model?

You should see changes beyond just changes to hair color and skin tone. You may need to play around with the losses.
As I also mentioned, what worked for toonify may not work for anime. You may need to go beyond what was done for toonify, but the idea should be similar.

Alright! Thanks for your insights, I will try playing with the losses as you suggested.


feat: Add support for background colours

Cava has a feature in it config to set the background of the visualiser. This improves things for users working with the SDL2 renderer as the window does not have a background colour set by the terminal.

Superceded by #10, sorry for overwriting it and thanks for the PR!


Allow user to define multiple policies

This PR allows policy server to load multiple policies. Each policy has also its own settings, which tune how they behave.
The policies configuration file is a yml file like the following one:
valid:
  url: file:///home/flavio/hacking/kubernetes/chimera/policy-server/namespace-validate-policy.wasm
  settings:
    valid_namespace: valid
flavio:
  url: file:///home/flavio/hacking/kubernetes/chimera/policy-server/namespace-validate-policy.wasm
  settings:
    valid_namespace: flavio
empty:
  url: file:///home/flavio/hacking/kubernetes/chimera/policy-server/namespace-validate-policy.wasm
  settings:
    foo: bar
nothing:
  url: file:///home/flavio/hacking/kubernetes/chimera/policy-server/namespace-validate-policy.wasm

Each policy is identified by a unique ID (valid, flavio, empty, nothing in the example above), this ID is used to build the endpoint of the policy. All the policies are exposed by the web API under the /validate/<policyID> endpoint.
Given the previous example, the policy server would reply to POST requests sent to:

/validate/valid
/validate/flavio
/validate/empty
/validate/empty

Finally, as you can see the same policy can be loaded several times, each time with a different set of settings.

Thanks @cmurphy!
Tomorrow I'll squash some of the commits and merge it


Remove Buffers type

cc @dragonnn @MathiasKoch
If this gets merged, then #189, when aligned, can follow.

@rmja Could you fix the CI?

Sorry for the delay, I think it is ready now.


Fix mismatched ImGui::Alloc/Free

The socket was being allocated with ImGui::MemAlloc but being freed with delete. When overriding the ImGui allocators, this mismatch causes a crash during disconnection.

The socket is allocated using ImGui::MemAlloc inside a placement new. The fix is missing manually calling the destructor of SocketInfo and then Imgui::MemFree.

Good point, I was focused on the memory and forgot about the destructor. Replacing with your standard way of doing it sounds great, thanks.


Remove tqdm from base requirements

This PR will close  #406.
If tqdm module exist, use it to show progress.
If it doesn't, do not show progress, just show "Done." when the download finished.

Coverage decreased (-0.2%) to 90.935% when pulling 5b833073faf5e646af4ebab9c27f624579f01c16 on rm-default-tqdm into 9c6ecd728469d4b5a12389e49b606306f490f914 on dev.

Hello @bact! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/test_benchmarks.py:

Line 66:80: E501 line too long (90 > 79 characters)


feat(deps): upgrade esbuild to v0.15.4

Latest esbuild bring support for yarn pnp: see https://github.com/evanw/esbuild/releases/tag/v0.15.0.
I'm not sure of implications on other packages. Just run a local test.
Is it something that need more thoughts ?

I believe this is just for the Build API. tsx uses the Transform API, which doesn't do any import resolution. It delegates it to Node.js instead.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Kuhn Poker] Simplify the implementation

Hey, multiple implementations of Kuhn Poker out there (open_spiel for instance) use only two actions (pass, bet) instead of the four considered in pgx (call, bet, check, fold). In fact we can group bet/call and check/fold without ambiguity for this game.
Would you be interested by this simplification? I would be happy to open a PR if you are!

Hi, thank you for your comment! 🙏
I'm positive for this change.
There are only five scenarios. Four actions are redundant.
If you kindly submit a PR, we'll receive it.
We also really appreciate if you can list up some implementations or papers which use two actions to support this change (in addition to open spiel)


Add logging for API calls

Right now, all caught errors are ignored.

You mean logging on client?

We have Sentry now.


Strange error if I add file with same syntax content as previous one

/home/yolo/yolo_rpi_server/mock/server/utils.js added to sources

undefined:1786
throw new JS_Parse_Error(message, filename, line, col, pos);
^
Error
at new JS_Parse_Error (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :1778:18)
at js_error (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :1786:11)
at croak (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2299:9)
at token_error (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2307:9)
at unexpected (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2313:9)
at block_ (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2708:28)
at function_body (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2682:21)
at function (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2636:20)
at expr_atom (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :2968:24)
at maybe_unary (eval at (/home/yolo/yolo_rpi_server/mock/server/node_modules/uglify-js-harmony/tools/node.js:22:1), :3303:19)

I'm getting this error too, but I'm presently unable to diagnose the issue. Previously had to remove a cyclic dependency.
processing main file: /.../api/app.js
/.../api/app.js added to sources
/.../api/config/config.js added to sources
/.../api/routes/index.js added to sources
/.../api/routes/users.js added to sources
/.../api/models/user.js added to sources
/.../api/models/company.js added to sources
/.../api/config/database.js added to sources
/.../api/routes/companies.js added to sources
/.../api/routes/folders.js added to sources
/.../api/config/log.js added to sources
/.../api/routes/files.js added to sources
/.../api/import/importfile.js added to sources
/.../api/routes/views.js added to sources
/.../api/routes/nodes.js added to sources
/.../api/routes/links.js added to sources
/.../api/config/passport.js added to sources

undefined:1786
    throw new JS_Parse_Error(message, filename, line, col, pos);
    ^
Error
    at new JS_Parse_Error (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:1778:18)
    at js_error (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:1786:11)
    at croak (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2299:9)
    at token_error (eval at <anonymous> (/.../wise/api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2307:9)
    at unexpected (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2313:9)
    at block_ (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2708:28)
    at _function_body (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2682:21)
    at function_ (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2636:20)
    at expr_atom (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:2968:24)
    at maybe_unary (eval at <anonymous> (/.../api/node_modules/uglify-js-harmony/tools/node.js:22:1), <anonymous>:3303:19)

same error


Document mixins

Signed-off-by: Andrew Meyer<EMAIL_ADDRESS>Signed-off-by: Javier Romero<EMAIL_ADDRESS>

Are mixins implemented?

Are mixins implemented?

@jkutner The documented rules are now enforced on master :)


cast metadata field values that are ints or floats, to binary

Addresses #8
I used 253 because that is the highest precision we will be able to preserve in the conversion according to http://erlang.org/doc/man/erlang.html#float_to_binary-2
Looking forward to your feedback.

Codecov Report

Merging #9 into master will increase coverage by 1.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
+ Coverage    67.9%   69.04%   +1.14%
==========================================
  Files           2        2
  Lines          81       84       +3
==========================================
+ Hits           55       58       +3
  Misses         26       26

Impacted Files
Coverage Δ

src/oc_reporter_datadog.erl
64.58% <100%> (+2.36%)
:arrow_up:

Continue to review full report at Codecov.

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


Re-design Indices lowering

Previously the indices lowering stage is not flexible not not supporting indices that are not sparse itervars and one sparse itervar can only be attached to a single sparse buffer, also multiple sparse-blocks is not supported, which is not reasonable in the practical case.
These limitations hinders non-zero elements inference and more examples such as sparse softmax. This PR fix the issue by re-designing the indices lowering algorithm.
More specifically, this PR completely removes analyzer (that collects dependency information), but use a sparse block context stack to store the sparse block local information used for rewriting, also, a sparse iter var is no longer attached to a sparse buffer.
Support indices more complicated than sparse itervars is supported by a visitor that recursively transforms var nodes.
UPD: unittests passed.
TODOs:

[ ] Docstring not ready.
[ ] Decompress offset for sparse axis from coordinates not finished yet (but it won't affect unittest).
[ ] More tests involves dense iterator viewed in sparse axis.

These TODOs will be implemented in following PRs.

@MasterJH5574 Let's sync after Dec 15th.
@junrushao1994 any code-wise suggestions?

Thanks, code revised according to suggestions.


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:55:11)
CompassView.initialize (/Users/jasper/git/noblejasper/dotfiles/macosx/atom/packages/compass/lib/compass-view.coffee:10:9)

Thanks for the heads up. Should be fixed.


Nginx web server failing in Media Microservice application

I have deployed the Media microservice on aws using kubernetes. The Nginx web server pod is failing to mount the persistent volume. I got the following events from the nginx pod:

Hi! I encountered the same problem, did you solve it?

Hi! I encountered the same problem, did you solve it?

I think the issue is that the application requires a NFS persistent storage and requires us to change pv and pvc yaml files. I think AWS EFS is the way to go for this.

Did you succeed? I didn't deployed it on aws, but I used NFS Share on my Kubernetes and it didn't work.

Did you succeed? I didn't deployed it on aws, but I used NFS Share on my Kubernetes and it didn't work.

I am still learning how to do it. Meanwhile, can you tell me how to setup NFS share on k8. Any links to refer, etc....

Got the issue. Need to create configmaps for nginx config files (nginx-k8s.conf)


the value of traefik_tls_crt

Hi nemonik, thanks your book, it's very helpful.
I tried to make my domain certificate, but the firefox show "Warning: Potential Security Risk Ahead"
the wildcard domain keys, fullchain.pem and privkey.pem:
/etc/letsencrypt/live/example.com/fullchain.pem
-----BEGIN CERTIFICATE-----
1xxxxxx
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
2xxxxxx
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
3xxxxxx
-----END CERTIFICATE-----

/etc/letsencrypt/live/example.com/privkey.pem
-----BEGIN CERTIFICATE-----
4xxxxxx
-----END CERTIFICATE-----

I made the vault file and got a traefik-cert-secrets.yaml:
...
data:
  tls.crt: |
    1xxxxxx
  tls.key: |
    4xxxxxx

There are 3 keys in fullchain.pem, I don't known the content of tls.crt should be (just wrotre the first 1xxxxxx in tls.crt).
Thanks for any opinions :)

I need to document this section.
I will write up something today and place in the README.md file.

Updated README.md with the first stab at Let's Encrypt documentation.

i'll continue to tweak the text... i should be using the domain variable throughout the IaC lemme know if not pls...

Can I close? Are things working for you?


Refactors store to reduce duplication and make it more readable.

@JyotinderSingh
I appreciate the effort to reduce duplication; that's a great goal. However, in my opinion, the current approach impacts readability. You might find this reference helpful: Happy Path

@kushal0511-not Though I agree with what you are saying and I adopt the same style of having guards to prevent multiple conditional statements, it may not be the case in this PR. The conditional levels are <= 2 and is not impacting readability to a huge extent as the block sizes within the conditional statements are not very large.

Thanks for the reviews @kushal0511-not @gauravsarma1992, I have migrated all instances of store locks to use this pattern. Tried to structure it in a way that it becomes easier to add more lock variants into this approach.


Database issue

All of my data stored in the database has a password. But when I try to access data by using PPMA'm having trouble with blank lines.
This is a databese: https://yadi.sk/d/SEkdsKTuYmgAt
This is a PPMA interface: https://yadi.sk/d/QUd7hEeNYmgfU
There are too many passwords. There is only one reserve. Produce your solution!

For reference to my issue above, this was caused by (for some reason) the encryption key being NULL.
As we're a UK company I've just added in a check if the decrypted password can be parsed by htmlentities, and if not, to then try the NULL encryption key as below:
    public function decrypt($text)
    {

            $item = Yii::app()->securityManager->decrypt($text, $this->encryptionKey);
            if(htmlentities($item)) { return $item; }
            else { return $item = Yii::app()->securityManager->decrypt($text, NULL); }
    }

Obviously this does remove some level of security for us, but until we can pin down the original issue (why was the password encrypted with NULL?) this works for us.
Thanks to @cicero44bc for his help on this.


[Docs]: Execution failed with status 5000

This happens when I try to run two queries in parallel to a Redshfit server simultaneously.  in Backend it seems this error is related: - Looks like the connection is stale. Retrying with a fresh context. (Add all the scenarios)

@danciaclara - Could you please add relevant links or additional information to this ticket?

I think we will have to check with BE to understand the different scenarios where this error occurs for, eg: Unknown host, connection timed out, etc ..... we need to understand what the possible scenarios are where this error is flagged to the user and how they can solve them. @sribalajig @rohan-arthur sorry for pinging you both, as I'm not sure which pod could help us with this.
few support links below
https://github.com/appsmithorg/appsmith/issues/14585
https://community.appsmith.com/t/execution-failed-with-status-5000/947
https://discord.com/channels/725602949748752515/760761686549463060/918537502309101649
@jnikhila Until we get an idea about these scenarios, I think we should park this issue and pick up something else.


touchend is equal to touchstart

Hi,

I have multiple controls
I start selection hover one control
I end selection hover another control

If i'm using mouse events it works fine. In mousedown I get the first control and in mouseup I get the second control.
But if i'm using touch events i'm getting only the first control. In touchstart I get the first control (it's correct) but in touchend I was expecting the second control - but get first control again.
I'm using version 4.1.0 with angular 5.2.2 and the relevant code is:
<ng-template ngFor let-item let-i="index" [ngForOf]="locals.Locals">
      <svg:g (down)="activate($event, item)" (up)="deactivate($event, item)" class="container small"

Thanks.

Hi @jftsaraiva,
I'm really sorry, I must have somehow totally missed this issue.
Apparently this is not a bug but indeed a feature for touch events:

The event's target is the same element that received the touchstart event corresponding to the touch point, even if the touch point has moved outside that element.

Source: https://developer.mozilla.org/de/docs/Web/API/TouchEvent
Did you manage to find a way around your problem?
All this library does for the up/down/move events is mapping them to their mouse, touch, and pointer counterparts. For more sophisticated touch logic, I would suggest something like HammerJS


Adds to onboarding: general artsy/README callout, Engineer Workflow doc

I found the Engineer Workflow doc very helpful for better understanding how we use GitHub and other services. Also noticed that there were a lot of links to artsy/README docs, but no general link to artsy/README itself - thought it worth calling out.

👍


Preinitialize texture data for the user

Creating a texture without data property and then calling subimage raises a warning in FF:
let txt = regl.texture({
  channels: 1,
  width: 1,
  height: 1
})

txt.subimage({
  data: dashData,
  width: 1,
  height: 1
}, 0, 0)

To fix that, a blank array should be passed:
let txt = regl.texture({
  data: new Uint8Array(1),
  channels: 1,
  width: 1,
  height: 1
})

Would that be polite to create data for the user, if that is not passed, in order to avoid warning?

Fixed by #479


React.createElement: type should not be null, undefined, boolean, or number

Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of `t`.

I get this error message with the example and only white page ...
React 15.4.0
Ps.:

With<EMAIL_ADDRESS>it's looks better, but still not smooth ...


[API][Controllers] Exhibition ReadAll Controller

Done.

This route shouldn't return all the data about the exhibitions, same for the other "get all" routes. It should return an id, a name, and the first 100 characters of the description for example. For the web application it should be okay with these 3 informations, but you need to ask for the android app too!


excessively long lines complicates CI based format validation

(Disclaimer: I'm not actually implementing CI validation at the moment as I'm mostly learning rust, so it's a hypothetical. But it's one of the first things I'd do if Rust were to be adopted where I work, for example, and I'm intending on doing so with Travis on my personal stuff as well.)
I ran into the impossibility case:
Rustfmt failed at /Users/scode/..../tunytools/src/bin/numstats.rs:94: line exceeded maximum length (maximum: 100, found: 110) (sorry)

This is because I have a comment with a long URL in it:
https://github.com/scode/tunytools/blob/master/src/bin/numstats.rs#L94
If I want to implement a CI check that ensures code is formatted, I would use the diffing mode to get a user friendly diff along with looking for exit code 4:
    4 = Formatted code differs from existing code (write-mode diff only)

However since the case of impossible-to-format has an exit code of 3, and it takes precedence, I now cannot, by exit code, differentiate between "the file is otherwise fine, but there's an impossible-to-format case in it" and "the file would have been changed". The only way I see to do this would be to look at what goes to stdout, rather than pay attention to the exit code.
Because it seems reasonable to have a maximum line length policy that is allowed to be violated in certain cases such as including a link without breaking it up (though reasonable people can disagree), it seems like it would be preferable to allow this through. I can think of a few options:

Provide a flag that says to not treat impossible-to-format as errors. I'm not sure what unintended consequences this has for other cases that are in this class.
Provide a mechanism to allow leniency in certain cases (e.g. "line length violation is okay, if it's impossible to format otherwise").
Provide an additional exit code that represents the combination of 3+4; i.e., there is a diff and it's impossible to format correctly (validation code would then require a 3 for success if it wants to allow impossible to format code).
Document that it is valid to interpret an empty stdout as an indication that the file did not need to be changed, if the exit code is 3 specifically.

Additionally:

Document that when exiting with code 3, formatting that is possible has still been done (basic testing indicates to me that this is the case, but I feel uncertain whether this is the contract and generally true).

Would disabling error_on_line_overflow in rustfmt.toml help?

That would seem to work around this particular case. I'm not sure whether or not it's a general answer though. The documentation of the exit codes suggests that the 'impossible to format' case is general in nature:
    3 = Code is valid, but it is impossible to format it properly

I'm not sure it the intent is for such cases to be a formatting policy violation or not. If that is indeed the case, then yeah - for anything that one would like to let through despite it not being possible to format, turning off the appropriate option seems reasonable.
I took a look at https://github.com/rust-lang-nursery/rustfmt/blob/74f5a515ef025ed629cf3cf1c04ed783c9a371c6/src/lib.rs#L446 and surrounding code, and I'm not yet sure how to, or whether, those cases are differentiated. The comment (https://github.com/rust-lang-nursery/rustfmt/blob/74f5a515ef025ed629cf3cf1c04ed783c9a371c6/src/lib.rs#L627) suggests that error is used only when it cannot be corrected, but yet I see nothing different about the application of TraillingWhitespace (https://github.com/rust-lang-nursery/rustfmt/blob/74f5a515ef025ed629cf3cf1c04ed783c9a371c6/src/lib.rs#L662) which presumably can always be corrected. Basically I was considering whether the error message here should tell the user about the switch being available, but I don't know the rustfmt code base yet.
My overall motivation is for cargo fmt to "just work", including for someone just sticking a line into their travis config without a lot of research and effort. The goal is to incentivize adoption and promote consistency like gofmt has done in the Go world.
I am new to rustfmt and of course defer to others, but my current thoughts are:

If you are running cargo fmt, it should never fail unless there's a bug in the formatter.
If you are running cargo fmt -- --write-mode=diff (maybe in the future this will be cargo fmt --test or similar?), it should only fail if (a) there's a bug in the formatter or (b) a diff was produced.

Modes of operation which cause failures for other reasons seem best left as opt-in behaviors in order to promote painless widespread adoption.
Thoughts?

A possible solution is discussed in https://github.com/rust-lang-nursery/rustfmt/issues/1977#issuecomment-372167773  Closing this issue in favour of #1977


Cannot checkout the repo due to invalid path

Hi All ,
It appears that we cannot clone the repo
https://github.com/ARM-software/ML-zoo.git
$ git clone https://github.com/ARM-software/ML-zoo.git
Cloning into 'ML-zoo'...
remote: Enumerating objects: 1320, done.
remote: Counting objects: 100% (66/66), done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 1320 (delta 27), reused 22 (delta 22), pack-reused 1254
Receiving objects: 100% (1320/1320), 413.77 KiB | 721.00 KiB/s, done.
Resolving deltas: 100% (480/480), done.
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:1/0.npy'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
The path that git checks is  models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:1/
But the actual path seems to be,
/models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_input/normalized_input_image_tensor/
#git checkout master
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:1/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:2/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:3/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_int8/testing_output/TFLite_Detection_PostProcess:01/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_int8/testing_output/TFLite_Detection_PostProcess:02/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_int8/testing_output/TFLite_Detection_PostProcess:03/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_int8/testing_output/TFLite_Detection_PostProcess:04/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_uint8/testing_output/TFLite_Detection_PostProcess:1/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_uint8/testing_output/TFLite_Detection_PostProcess:2/0.npy'
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_uint8/testing_output/TFLite_Detection_PostProcess:3/0.npy'
Thanks,

As per your post on the community forum (but adding here as well for others to see)
There is an error due to non-Windows compatible paths (works fine on OSX/Linux). The team are fixing the repo to have Windows compatible paths and will get back when they have fixed the problem.

As per your post on the community forum (but adding here as well for others to see) There is an error due to non-Windows compatible paths (works fine on OSX/Linux). The team are fixing the repo to have Windows compatible paths and will get back when they have fixed the problem.

Though it works in Linux, The issue still exists in Windows.
$ git clone https://github.com/ARM-software/ML-zoo.git
Cloning into 'ML-zoo'...
remote: Enumerating objects: 1345, done.
remote: Counting objects: 100% (91/91), done.
remote: Compressing objects: 100% (67/67), done.
remote: Total 1345 (delta 28), reused 45 (delta 24), pack-reused 1254
Receiving objects: 100% (1345/1345), 62.53 MiB | 6.60 MiB/s, done.
Resolving deltas: 100% (481/481), done.
error: invalid path 'models/object_detection/ssd_mobilenet_v1/tflite_fp32/testing_output/TFLite_Detection_PostProcess:1/0.npy'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'


Don't not show flags if there are no switches.

:+1:
Unrelated, but I think those functions should return Option[String] so that the display doesn't print out a whole bunch of empty lines (not in this PR though)