Setting the font size of the sets

Hey, great package!
I'm struggeling to set the font size of the names of the sets displayed in the middle of the bars. I manage to access the axis to set the size of x and y label.
How can I access the other text elements to set their size?

Hi! Thanks for your feedback. Hope you tapped that star on top of the page :-)
The supervenn function actually has a dedicated parameter named fontsize, BUT:

I forgot to include it in the docstring
I forgot to pass it to side_plot()

Both are fixed in the latest release 0.3.2, so you can upgrade and enjoy.

Hi! Thanks for your feedback. Hope you tapped that star on top of the page :-)
The supervenn function actually has a dedicated parameter named fontsize, BUT:

I forgot to include it in the docstring
I forgot to pass it to side_plot()

Both are fixed in the latest release 0.3.2, so you can upgrade and enjoy.


Problem with running Genotype QC for PCA

While running "sos run GWAS_QC.ipynb king --cwd output/ --genoFile ZOD14598_AD_GRM_WGS_2021-04-29_chr20.recalibrated_variants.leftnorm.filtered.bed --name test --keep-samples sampleSheetAfterQC.filtered_geno.txt --container /mnt/vast/hpc/csg/containers/bioinfo.sif --walltime 12h  --no-maximize_unrelated" in the login node, error reported as below:
ESC[91mERRORESC[0m: ESC[91m[king_3]: [0]: Executing script in Singularity returns an error (exitcode=13, stderr=ZOD14598_AD_GRM_WGS_2021-04-29_chr22.recalibrated_variants.leftnorm.filtered.h3k9.unrelated.stderr, stdout=ZOD14598_AD_GRM_WGS_2021-04-29_chr22.recalibrated_variants.leftnorm.filtered.h3k9.unrelated.stdout).
The script has been saved to /.sos/2b2fea82ec53aec4.To reproduce the error please run:
ESC[0mESC[32msingularity exec  /mnt/vast/hpc/csg/containers/bioinfo.sif /bin/bash /.sos/2b2fea82ec53aec4/singularity_run_2554.shESC[0mESC[91mESC[0m

The problem is:
PLINK v2.00a2.3LM AVX2 Intel (24 Jan 2020)   [www.cog-genomics.org/plink/2.0/](http://www.cog-genomics.org/plink/2.0/)
(C) 2005-2020 Shaun Purcell, Christopher Chang  GNU General Public License v3
Logging to /mnt/mfs/ctcn/team/lu/Peaks_analysis/QC/output/genotype/xqtl_protocol_data.h3k9ac.related.log.
Options in effect:
 --bfile xqtl_protocol_data
 --keep /mnt/mfs/ctcn/team/lu/Peaks_analysis/QC/output/genotype/xqtl_protocol_data.h3k9ac.related_id
 --make-bed
 --memory 90000.0
 --new-id-max-allele-len 1000
 --out /mnt/mfs/ctcn/team/lu/Peaks_analysis/QC/output/genotype/xqtl_protocol_data.h3k9ac.related
 --set-all-var-ids chr@:#_$r_$a
 --threads 20
Start time: Thu Sep 15 22:21:47 2022
515677 MiB RAM detected; reserving 90000 MiB for main workspace.
Using up to 20 threads (change this with --threads).
4669 samples (0 females, 0 males, 4669 ambiguous; 4669 founders) loaded from
xqtl_protocol_data.fam.
94971302 variants loaded from xqtl_protocol_data.bim.
Note: No phenotype data present.
--keep: 0 samples remaining.
End time: Thu Sep 15 22:22:16 2022

After investigation, the reason for this issue is that, king was done based on the output of plink1, where fid = iid when converting vcf to plink bed.  However, while we moved to plink2, the fid will be set to 0. Which leads to this issue.
In consideration of the potential usage of plink2 to accommodate dosage, I think it is best to modify the related.id output from king.


File upload with metadata

This PR should do the following

Create  POST http://host:port/bzz-file api to upload a file
Create GET http://host:port/bzz-file/{address} to download a file with the filename uploaded

See the user story for more details https://app.zenhub.com/workspaces/swarm-10-5e7c6d9966b97049231c3c0b/issues/ethersphere/bee/274

@janos  @nolash  I have done most of the part except testing upload with multiple files. If you insist i will do that, but since that was not a requirement i am submitting for a review. Also the Coverage report failing looks like a false alarm.

@jmozah could you update this branch with the recent changes from the master? We have update the API router.

@jmozah could you update this branch with the recent changes from the master? We have updated the API router.

@janos Updated and fixed the review comments

part is already read and here cannot be read any further as it reached EOF. The whole content type detection has to be done before any Read call on part. Basically, before storePartData call, the whole code block from line 85 to line 111 has to be moved, with one important difference. If the bufio.Reader is constructed it has to be passed to storePartData, not directly the part variable as part reader already moved its cursor, while the bufio reader did not, it just peeked, so it can read from the start, as part reader has advanced 512 bytes. The best way to do that is to create var reader io.Reader = part before if contentType == "" { line and here to do reader = bufio.NewReader(part) (assign to the variable, not create a new one), and use that reader variable in storePartData fr, err := s.storePartData(ctx, reader, fileSize).

Strange, i dont know how the unit testcase for this worked which also test and check the downloaded data with uploaded data. but i changed it as you said.

It looks to me that contentType == "" block is not tested and it would be good to have that test.

Added arguments in test to cover the scenario where we dont send contentType, and check it on receiving.


fix: implement Denops.interrupted property to AccumulateHelper

Summary by CodeRabbit

New Features

Introduced a new interrupted property to the AccumulateHelper class, enhancing asynchronous operation handling.
Added a new dependency for improved resource management.

Bug Fixes

Enhanced test suite for the denops object, ensuring accurate reflection of the interrupted state and improving test reliability.

Tests

Expanded test coverage with new cases for the denops object and improved state management during tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.27%. Comparing base (1bb647b) to head (ce31655).

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   99.25%   99.27%   +0.01%
==========================================
  Files           1        1
  Lines         135      138       +3
  Branches       18       18
==========================================
+ Hits          134      137       +3
  Misses          1        1

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


Clean up list

[x] Stop using hre.deployer.paths
[ ] Do not use config in any tools - tools should only use primitives that are very intuitive
[ ] Do not copy config.paths into config.deployer.paths
[ ] Do not use config.deployer for anything dynamic, since this is supposed to be just config
[ ] Forbid usage of .previousData in hre.deployer?
[ ] Forbid usage of .file in hre.deployer?
[ ] Is config.deployer.proxyName used?
[ ] Document argument-types.js util
[ ] Split out some functions in contracts util to core-js
[x] Move logger to core-js
[x] Move git and package to core-js
[x] Move prompter to core-js
[x] Move relative-path to core-js
[x] Move string to core-js
[ ] Split deployer utils to internal/external utils: Internal are those that need the hre env, and external are the ones that dont - E.g. transactions.js

for  Is config.deployer.proxyName used?
I can answer: Yes.
And in fact I think we should also add the "Gen" prefix as configurable and defaulted to "Gen" so that the tooling doesn't enforce you to use a particular name for the generated contracts (or any hardcoded name).

Closing this issue. Splitting it up in smaller issues.


What is the function of the learn_sigma in SiT model forward?

if self.learn_sigma:
x, _ = x.chunk(2, dim=1)

I didn't see any loss related to sigma. Am I missing something?

This is a legacy option inherited from DiT (and further back to ADM), and not used at all in SiT.

This is a legacy option inherited from DiT (and further back to ADM), and not used at all in SiT.

Thanks!


exit on bad geometry

When geometry argument received is invalid, prevent wf-recorder from recording rather than setting geometry to default '0,0 0x0' and continue recording.

Maybe have the output message suggest that the geometry might need to be in quotation marks, too?

Maybe have the output message suggest that the geometry might need to be in quotation marks, too?

That is already mentioned in the documentation as well as '--help' text. Adding something like 'see: wf-recorder --help' to the message should suffice.

Maybe wf-recorder --help | grep geometry or even more direct: Bad value of geometry: %s\nDid you forget to wrap it in quotation marks?

Maybe wf-recorder --help | grep geometry or even more direct: Bad value of geometry: %s\nDid you forget to wrap it in quotation marks?

Well, we can't simply assume that the value is wrong only because it is not properly quoted. Maybe the user has given a completely wrong data that doesn't represent any geometry.

The reason I suggest the message suggestion is because 1) the number one reason this happens is because people forget the quotations and 2) a message telling people to look at --help output isn't very useful when it's not clearly spelled out that quotations are needed there. Maybe we could combine the ideas and suggest both --help and ask if the argument is not quoted?


Add setup.py script

Hi there, thanks for the great package!
I forked to add a setup.py script, so I can now install the package via:
pip install git+https://github.com/tim-fan/GazeTracking.git
I'm making this pull request in case you want this change in your repo.
It was the first time I've written a setup.py file, so let me know if you want anything changed, for instance if you don't want your email in the package info, or if you'd like to start the version number at something other than 0.1.
I suppose a next step could be to upload to PyPI, although this is something I've never tried.

Is it working on your system? Just asking. I haven't tried it on my system. Are there any system requirements to install the software?

Yep it works for me. I just tested it on bionic - I was able to run the example as follows:
python3 -m venv venv
source venv/bin/activate
pip install git+https://github.com/tim-fan/GazeTracking.git
wget https://raw.githubusercontent.com/tim-fan/GazeTracking/master/example.py
python example.py

(note it would be nice to include the example script in the package, so it is available at the command line after pip installing)


Add a command palette

For easier access to functions on phones with few hardware buttons, it would be easier to invoke the respective functions with star+number combos, instead of with hotkeys. For example, #83 and #170 would require multiple key control keys.
Also, the hotkey processing is getting more and more complex, which is not the way to go.
To resolve this, add a command palette:

Split TraditionalT9 class in three logical pieces.

TypingHandler extends KeyPadHandler. It contains 0-9, Ok and backspace processing code.
HotkeyHandler extends TypingHandler. It contains the hotkey code
TraditionalT9 is on top and contains tools like getting the context and whatnot

Add a "show commands" hotkey. It will display a numbered list of commands. Default key is: "*".
Pressing a number when the command palette is on invokes the respective command.
Command list: 1. Add word; 2. Show settings
Remove the "Add Word" and "Show Settings" hotkeys.
Make sure the command palette fits well, when the on-screen keyboard is on.
Make the list touchable, so it can be used on a device without a hardware keypad.
Remove Add word and settings handling from KeyPadHandler. Done in another issue.
Make a migration for resetting the hotkeys There is no need to migrate anything. The old hotkeys will simply not exist.

I suggest leaving in the Add Word and Show Settings hotkeys. It just increases the customizability available to people. Some people prefer weird things!

Well, I suppose there is no harm in leaving the hotkeys.

After all, I've decided to reduce the number of hotkeys to minimum to make the code simpler and easier to maintain. I believe the new command palette will be convenient enough to compensate for that.


Document mixins

The mixins are documented pretty well in the partial, but web documentation would be better, with examples.
Note I'm not being critical, this is a great project, just documenting the need. :+1:

@bradjones1 I've added the function and mixin comments found in _typesettings.scss to the web documentation.
http://typesettings.io/#functions
http://typesettings.io/#mixins


how to delete the scaled_XXX.jpg file after compress?

After i compress a image file like this:
List imgBytes = await FlutterImageCompress.compressWithFile("xxx.jpg");
the compress plugin will make a scaled file in the Pictures directory：
the scaled file's path like these:
/storage/emulated/0/Android/data/com.ywj.fd.app.family_doctor_app_resident/files/Pictures/scaled_scaled_scaled_scaled_c57c469a-4afb-40a5-8062-af9ae78dabc64003503382529478024.jpg
/storage/emulated/0/Android/data/com.ywj.fd.app.family_doctor_app_resident/files/Pictures/scaled_scaled_c57c469a-4afb-40a5-8062-af9ae78dabc64003503382529478024.jpg
How to delete them?

This plugin does not create any cache files except the one you specify.
If this file is your image source file, then you can use File(path).delete(); to delete file.

Are you using image_cropper plugin by any chance?
The File that you have mentioned gets created for all images that go through image_cropper in my application.


Encode number of segments in filename

[ ] adapt function save_log
[ ] adapt function read_log
[ ] save_log should create a filename of the following form: sim_log_6s_4p.arrow
[ ] read_log should retrieve the correct number of points from the filename
[ ] add function is_4p(filename)
[ ] update documentation

Not longer needed due to https://github.com/ufechner7/KiteUtils.jl/commit/0ae30d2b113a9f2f3169b12c56c570c6eeccc2f4


warp: change handling existing tmp file

in warp, when tmp folder already exists, at the moment the tool deletes it
proposal: if it exists ask user to delete the tmp folder. y/n
if no the process stops
maybe add silent mode parameter?

fixed in https://github.com/Geodan/terrain/pull/29


--version should include CFParser version

When CFLint doesn't find something that it should, it tends to be because of the wrong CFParser version, not CFLint version.  CFLint should expose the version of CFParser it is using (either in --version output or a separate option).

implemented


Spanner: update samples to follow samples guide -4

This PR contains following Samples:

spanner_batch_client
spanner_cancel_backup_create
spanner_create_client_with_query_options
spanner_delete_data
spanner_get_backup_operations
spanner_get_backups
spanner_get_database_operations
spanner_quickstart
spanner_restore_database
spanner_update_backup
spanner_update_data
spanner_insert_data_with_timestamp_column

Fixes #1173
Towards #1136
Fixes #1065
Fixes #1062

Just for expectations, I'll get to this in early January.

Spanner Tests are failing because of create instance permission issue on CI configured project.

The failures seem to be because of permissions. Checking now.

Rerunning...

@laljikanjareeya :

The issue with permissions has been fixed.
There are failures with a couple of tests now. Please take a look.
Also see #1250. There's a change there to the old sample that you need to include here as well.

@amanda-tarafa Thanks for the review, fix the failures tests PTAL.

@amanda-tarafa it's ready for merge.

I'd like @skuruppu to take a look as well from the Spanner side. Unless Shaniks, you are fine with merging as is. There's no rush on my part.

@skuruppu PTAL.

@amanda-tarafa Test failures seem unrelated to the PR.

Unrelated tests failures:

Storage failure being tracked in #1272.

Force merging now. Thanks @laljikanjareeya .


Unavailable workspace displayed while waiting for API response

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1723133790546149
Action Performed:

signing into accountA in #focus mode that is a member of a room that isn't currently read
sending a message in the room from accountB while accountA is still open in another browser
go offline in accountA
open the room and see what the header shows

Expected Result:
Workspace name and loading skeleton for the content while it loads
Actual Result:
No loading skeleton and unavailable workspace displayed  until response received form Chronos comment
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/c53d236a-ecdd-474b-a934-8d301a265de9

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @srikarparsi

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I think we agreed that fixing issues with Chronos is out of scope for the NewDot Quality project: https://expensify.slack.com/archives/C05LX9D6E07/p1723207265131579

I can see we agreed to fix this one however - here: https://expensify.slack.com/archives/C05LX9D6E07/p1724072534751829?thread_ts=1723133790.546149&cid=C05LX9D6E07

I don't think it's necessarily related to Chronos, just to chats that take a long time to deliver an API response

I'm adding another BZ team members since I'll be OOO through 8/30.

Trying these reproduction steps in the Slack chat:

signing into accountA in #focus mode that is a member of a room that isn't currently read
sending a message in the room from accountB while accountA is still open in another browser
go offline in accountA
open the room and see what the header shows

(accountA<EMAIL_ADDRESS>& accountB<EMAIL_ADDRESS>This seems to happen with Chats and Rooms when offline. Here's a video of both. I think this is the issue? Updated the OP with these testing steps.
https://github.com/user-attachments/assets/100ee6e8-55d6-4614-85c5-a198b6983a1c

Hey @Christinadobrzyn! I’m not sure if I missed it but was there an unavailable workspace subtitle in the video? I’ll also try looking more into what could be causing this tomorrow

Hi @srikarparsi, no- I didn't see the unavailable workspace, but the skeleton showed when first testing. I just tested again and the skeleton doesn't show and I don't see the unavailable workspace either.

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Got it, didn't get time to try to reproduce this today but will try to make time for this tomorrow

I'm still not able to get that error. I wonder if we should just ask QA to retest this again or close until it's more clear how to reproduce it?

@Christinadobrzyn I don't think QA was ever able to reproduce this one.
@quinthar we're having a hard time reproducing the issue. Are you still seeing this issue in your account?

Can we amend the reproduction steps to:

Enable 4G throttling
Send a message to Chronos
Before you get your response from Chronos open a room

heads up - I'm going to be ooo 9/4-9/11.
I tried these steps in browserstack Android and I can't reproduce the error.

heads up - I'm going to be ooo 9/4-9/11.
I tried these steps in browserstack Android and I can't reproduce the error. @muttmuure where are you getting the error in those steps? In the new room or in Chronos?

We weren't able to reproduce this in the thread and I wasn't able to reproduce this locally either. I'm going to keep an eye on the thread to see if it gets reproduced but going to close this out for now.
https://github.com/user-attachments/assets/46123b86-b592-469e-934d-c126b59a08b5


Validate commandline arg values, and unify -help documentation

This resolves #172
Re-works the AllowedArgs class to be instantiable and add methods for building and verifying the set of allowed arguments, values, and associated help message. Creates a child class of AllowedArgs for each executable, and for the config file.
In addition, this change moves several constants from .cpp files into .h files, so they are accessible from the AllowedArgs class. It also adds test cases for invalid argument names and values.

Command-line values are verified by grouping all existing arguments into one of six possible value types:

Optional boolean
Argument values that are accessed using GetBoolArg are verified using the optionalBool function. The allowed values are "0", "1", or "".
Required string
Argument values that are accessed using std::string GetArg(), or that are accessed through mapArgs directly are predominantly verified using the requiredStr function. This allows any value, but must not be empty.
Optional string
This is an uncommon type, but some arguments accept strings while also having valid behavior with no value. These arguments are verified using the optionalStr function, and accept any value (including empty strings). (Currently only -connect, -debug, and -rootcertificates use this type).
Required int
Argument values that are accessed using int64_t GetArg() are predominantly verified using the requiredInt function. This allows any decimal character (0-9), but must not be empty. It also allows a negative sign ('-') as the first character. This is used for int argument values that are not typically valid with a value of 0 (or should be explicit if they want to specify a 0 value).
Optional int
Argument values that are accessed using int64_t GetArg() are sometimes verified using the optionalInt function. This allows the same values as requiredInt, but can also be empty. If the value is empty, it will be converted to 0 by GetArg, so this is used for int argument values that are valid with a value of 0 (-maxconnections and -limitfreerelay). It is also used for bool arguments that also accept an int (-upgradewallet and -zapwallettxes).
Required amount
Argument values that are parsed with ParseMoney are verified using the requiredAmount function. This allows any decimal character (0-9) or a '.' character, but must not be empty.

Some arguments could have more strict checks (e.g., -checklevel only accepting values 0-4). However, the goal of this change is just to have high-level argument types. Specific handling of the values (e.g., confining them to a min/max range) should be handled elsewhere (and all the code already does this, since prior to this change, all values were accepted by the command-line parser).
Note that I considered using regular expressions to validate the argument values, however the std::regex library isn't supported in gcc versions prior to 4.9. Also, the windows executables did not work when using regular expressions. So, although creating custom helper functions for each type is more verbose than simply using a regex, this approach is more portable.

All help message documentation (the text that is output up if you run an executable with the -help flag) is moved into the AllowedArgs class. This ensures that all allowed arguments and their documentation are defined in a single location in the codebase.

The design of the AllowedArgs class is inspired by the Boost.program_options library, which allows for defining the allowed arguments for a program as well as their types and their associated help documentation. However, I was not able to simply use this library directly, because of several requirements that the bitcoin executables have that are incompatible with Boost.program_options:
Most notably, Boost.program_options does not have support for the -help-debug option in bitcoin executables, which allows for a more detailed help message to be shown. Additionally, Boost.program_options expects double-dash arguments (e.g. --options), and it generates its help documentation with double-dashes. Also, Boost.program_options allows spaces to separate argument names with values, whereas bitcoin executables require an '=' character (e.g. --option1 value1 --option2 value2 vs -option1=value1 -option2=value2). While these incompatibilities could potentially be worked around, I believe it was easier and cleaner to simply implement the AllowedArgs class, which tailors its behavior for the bitcoin executables.

On a pure line-count, this change is relatively large. However, the majority of the lines changed are simply moving the help documentation from wherever it was located in the codebase into the AllowedArgs class. In order to ease reviewing, this pull request consists of two git commits (each of which are compilable and have all tests passing):
The first commit modifies the AllowedArgs class, and defines arguments for the bitcoin-tx executable. You can look at this commit alone to understand the AllowedArg class and how it is used.
The second commit adds argument definitions for all the remaining executables (bitcoind, bitcoin-qt and bitcoin-cli). In addition, it moves several constants into .h files so that they can be accessed from the AllowedArgs class.

Note that the AllowedArgs class does not always have access to instances of the CChainParams class (since they are in different compilation units, which aren't always linked together). For this reason, I had to make new constants for DEFAULT_MAINNET_PORT and DEFAULT_TESTNET_PORT.
In addition, the help documentation for -checkblockindex and -acceptnonstdtxn relies on values from CChainParams instances. Since these arguments are -help-debug arguments, I simply hard-coded their default values into the help documentation rather than creating new esoteric constants.

In order to verify that none of the help documentation has been inadvertently modified by this change, I have diffed the output of all the executables' help output. The following command works in bash for comparing the help output of two executables (assuming the .. dir contains the executable prior to this change, and the ./src dir contains this change's executable):
diff <(../bitcoind -?) <(./src/bitcoind -?)
I ran that command for all 4 executables, with and without the -help-debug flag (except no -help-debug flag for bitcoin-tx and bitcoin-cli, which did not support that flag prior to this change).
The help documentation for all executables is the same, with the exception of a few intentional changes:

Creating a new 'Help options' group, and moving -?, -version, and  -help-debug into that group.
Creating a new 'Configuration location options' group, and moving -conf and -datadir into that group.
Modifying chain selection options for bitcoin-tx and bitcoin-cli, so that -regtest only shows on -help-debug.
Renaming the 'Options' group to 'General options'.
Showing all valid argument names on -help-debug (e.g., showing -help and -h as alternatives to -?).
Adding example value (e.g. =<n>) for -bytespersigop, -datacarriersize, and -uiplatform.
Removing help documentation for -nodebug, since the -no* syntax is generically handled for all arguments.

A note on backward compatibility: this change will cause the executables to print an error message and immediately quit if there are any invalid command-line arguments or argument values. This has the potential to break things for users when they upgrade if they launch with invalid command-line options or if they have invalid options in their config file.
For example, a user might launch with -listen=false, which currently works as expected (because atoi("false") converts the value to 0). However, upon upgrading, their node will fail to launch. This is the intended behavior, so that users are alerted to invalid command-line flags as early as possible. E.g. prior to this change, if a user tried the inverse: -listen=true, the listen flag would actually be set to false. This change will reduce the chance of that type of unexpected behavior from occurring.

The Teamcity Continues integration system found some errors.
The basic linux-debian build went fine, the unit tests and rpc tests also finished Ok for that build.
The failed ones are the gitian based ones that do static compilation against a specific set of libraries and versions.
Linux 32-bit and 64-bit compiles gave the same error;
allowed_args.cpp: In function 'void AllowedArgs::addZmqOptions(AllowedArgs::AllowedArgs&)':
allowed_args.cpp:328:9: error: expected unqualified-id before '.' token
ICECC[562] 09:57:52: Compiled on <IP_ADDRESS>
make[2]: *** [libbitcoin_util_a-allowed_args.o] Error 1
make[2]: *** Waiting for unfinished jobs....

MacOs compile (uses clang)
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/clang++ -target x86_64-apple-darwin11 -mmacosx-version-min=10.7 --sysroot /home/builder/TeamCity/work/6ff1207d8200ef46/depends/SDKs/MacOSX10.9.sdk -mlinker-version=241.9 -stdlib=libc++ -std=c++11 -I. -I./include -std=c++0x  -DOS_MACOSX -DLEVELDB_PLATFORM_POSIX -DLEVELDB_ATOMIC_PRESENT -Wstack-protector -fstack-protector-all -fPIE -pipe -O2  -fvisibility=hidden -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -I/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/include/  -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS -DMAC_OSX -D__STDC_LIMIT_MACROS -c helpers/memenv/memenv.cc -o helpers/memenv/memenv.o
  CXX      bitcoin_cli-bitcoin-cli.o
In file included from allowed_args.cpp:5:
In file included from ./allowed_args.h:8:
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/../include/c++/v1/list:589:31: error: static_cast from 'pointer' (aka 'std::__1::__list_node_base<AllowedArgs::HelpComponent, void *> *') to '__node_const_pointer' (aka 'std::__1::__list_node<AllowedArgs::HelpComponent, void *> *'), which are not related by inheritance, is not allowed
        return const_iterator(static_cast<__node_const_pointer>(
                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/../include/c++/v1/list:884:59: note: in instantiation of member function 'std::__1::__list_imp<AllowedArgs::HelpComponent, std::__1::allocator<AllowedArgs::HelpComponent> >::end' requested here
    const_iterator end()    const _NOEXCEPT {return base::end();}
                                                          ^
allowed_args.cpp:107:38: note: in instantiation of member function 'std::__1::list<AllowedArgs::HelpComponent, std::__1::allocator<AllowedArgs::HelpComponent> >::end' requested here
    for (HelpComponent helpComponent : m_helpList)
                                     ^
  CXX      libbitcoin_cli_a-rpcclient.o
3 errors generated.
make[2]: *** [libbitcoin_util_a-allowed_args.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:4140: recipe for target 'libbitcoin_util_a-allowed_args.o' failed
rm -f libmemenv.a
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/x86_64-apple-darwin11-ar -rs libmemenv.a helpers/memenv/memenv.o
x86_64-apple-darwin11-ar: creating archive libmemenv.a
make[3]: Leaving directory '/home/builder/TeamCity/work/6ff1207d8200ef46/src/leveldb'
In file included from util.cpp:10:
In file included from ./util.h:17:
In file included from ./allowed_args.h:8:
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/../include/c++/v1/list:684:30: error: static_cast from 'pointer' (aka 'std::__1::__list_node_base<AllowedArgs::HelpComponent, void *> *') to '__node_pointer' (aka 'std::__1::__list_node<AllowedArgs::HelpComponent, void *> *'), which are not related by inheritance, is not allowed
        __node_pointer __l = static_cast<__node_pointer>(
                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/../include/c++/v1/list:670:5: note: in instantiation of member function 'std::__1::__list_imp<AllowedArgs::HelpComponent, std::__1::allocator<AllowedArgs::HelpComponent> >::clear' requested here
    clear();
    ^
/home/builder/TeamCity/work/6ff1207d8200ef46/depends/x86_64-apple-darwin11/native/bin/../include/c++/v1/list:780:29: note: in instantiation of member function 'std::__1::__list_imp<AllowedArgs::HelpComponent, std::__1::allocator<AllowedArgs::HelpComponent> >::~__list_imp' requested here
class _LIBCPP_TYPE_VIS_ONLY list
                            ^
2 errors generated.
Makefile:4308: recipe for target 'libbitcoin_util_a-util.o' failed
make[2]: *** [libbitcoin_util_a-util.o] Error 1
gcc gen_context.o -o gen_context

Compile on ARM;
allowed_args.cpp: In function 'void AllowedArgs::addZmqOptions(AllowedArgs::AllowedArgs&)':
allowed_args.cpp:328:9: error: expected unqualified-id before '.' token
         .addHeader(_("ZeroMQ notification options:"))

I love the work you did, on first look its very clean code and well designed. Thanks!

It looks like the linux issue was a syntax error in the ZMQ section. And, the MacOs build was just due to a missing #include <string> in allowed_args.h. I have pushed fixes for both issues.

Teamcity says all pass now :)

I didn't really investigate, just did a quick compile and that finished just fine (both 1.2 branch and master branch).


update syntax-documentation

Cleanup-request
Description
Add missing changes to the documentation:

new definition-style for undefined items
new output-style for items of tree-objects

closed, because library is no longer maintained


[FRAMEWORK] Emberjs version bump to 3.4

Bump ember-source and ember-cli to 3.4 [LTS]

@ynnoj

Hey @theenadayalank thanks for your contribution 👍
I have updated the dependencies in this PR https://github.com/mansona/ember-cli-notifications/pull/251#issuecomment-552737340 so hopefully this covers what you're trying to do here. Let me know if I have missed anything and we can get it included in the next release 🎉


HTML Entities

Challenge http://www.freecodecamp.com/challenges/bonfire-convert-html-entities has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
function convert(str) {
   return str.replace(/[&'<>]/gim, function(entity) {
     return '&#'+ entity.charCodeAt(0) + ';';
   });
}

convert('Dolce & Gabbana');

I am able to pass one test but not the other. What am I missing? It is not explained well in the tests.

Which test is it showing you're passing and which is it showing that you are not passing?

GitHub issues are not for support, if you have trouble with your code, please use RSAP and ask in the #help channel on Slack.
From a cursory glance, you're converting to Unicode, not HTML entities like the challenge says.

@LumenTeun I don't think I was using Unicode. Referencing the w3schools site it says: "&	- ampersand - &  &." Is this not so?
Either way I passed the test using something else. Thanks for the passive aggressive tone!

& or &


Update build script to handle projects with non default target list

2 teams confirmed they still have packages which use non default target list say 'net40' only.
This PR handles that, particularly, we no longer error out when the 'portable\unsigned' folder contains nothing. There is another option that we can make the 'fxtargetlist' to be configurable, but that means we will need to configure 4 CI projects to expose this parameter, which is a little complicate to the partner teams.
I am also making similar change to the azure-sdk-for-net-pr repo.

reviewed by hovsep


docs: Add MIT License in wrappid-module

[x] Create a LICENSE file from GitHub WebView in main branch
[x] Choose a license template > MIT License
[x] Click on Review and submit
[x] Click on Commit changes
[x] Change commit message in the dialog Propose changes window

docs: 🔒 license added

added MIT License as requested

Ref #[issue-number]

[x] Change new branch name as WRPD-docs-[issue-number] in the dialog Propose changes window
[x] Open a pull request to development branch

closing


Update for new guide - Insider risk solutions

Update for new guide - Insider risk solutions setup guide

@kelleyvice-msft Please merge this PR. Thanks


feat(s3-stepfunctions and eventbridge-stepfunctions) created new constructs

Issue #286 #287, if available:
Description of changes:

Created s3-stepfunctions and eventbridge-stepfunctions constructs
Updated s3-step-function and events-rule-step-function constructs to wrap new constructs

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 32456f20621d590e77ef7697aea7d464364df4e0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 987a1cc7d2ccf5f6d18c168f18a1d8e2de5f0289
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: d282066c4294641743a746a27876cf1c4b755e9e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Added ShopifyLocalization

Purpose
This will allow to fetch Loaclization object, which will be beneficial to present Language and Currency options to the user.

@imsujan276 Sure, I'll add those in the next commit.

@imsujan276 I'm added the documentation and example. The example is in the shop tab.

Hi, thank you for your time for updating the doc.
But, in the example, I am unable to understand how the fetched data can be used in the app.
like

is it used to fetch localized data from the shopify? If yes, how can one use it ?
is it used to just display the supported countries?

It is used to fetch;

Supported languages, which can be used to display language options to the user.
Supported countries and their supported currencies, which can be used to display currency options to the user.

Without this data, the developer would need to hardcode the supported languages and currencies.


Syntax highlighting

[ ] React component
[ ] Markdown code fences
[ ] Should be themeable

conorhastings/react-syntax-highlighter : Uses Lowlight, powerful, good docs, but requires a bit of configuration to have small file footprint
akiran/react-highlight : uses highlight.js, & also requires extra work to not include every language & skin.  Seems more lightweight, but docs are sparse
Vamche/react-syntax-highlight : also uses highlight.js, decent documentation, but unknown to React community so not many issues/PR/versions.

That first one looks great, thanks!
To clarify the theming bullet point, I'd imagine that the syntax theme could be added to an mdx-deck theme:
// example theme
import { docco } from 'react-syntax-highlighter/styles/hljs'

export default {
  highlight: docco
}

Then automatically added to the syntax highlight component (and fenced code blocks) using the withTheme HOC

Is there anything missing here or can we close this issue?


[en]: Update insight/user-guide/trace/trace

Add images
Update English based on Chinese and UI

see preview: https://deploy-preview-5608--daocloud-docs.netlify.app/en/insight/user-guide/trace/trace


Fix communication over time display issues

Only allow data to be displayed in per second
rates and show correct label on y-axis

Why did you change the data being displayed to total (instead of rate), but then changed the labels from total to rate? Shouldn't the labels have remained the same? Otherwise, the rest of it seems sound.

I didn't change the data being displayed to total, it's still displaying rate, it's just that it's only allowing rates to be shown per second now, not per ms or us as before.

Ah nevermind. What I was seeing was the total that is displayed at the bottom of the screen, not the value on the y-axis.


Comments don't look good after formatting

What Git revision are you using?
https://github.com/aiken-lang/aiken/tree/v1.0.26-alpha
What operating system are you using, and which version?

[x] Linux / Ubuntu
[ ] Linux / Other
[ ] macOS
[ ] Windows

Describe what the problem is?
Sometimes we need to temporarily comment some part of the code like this one
let Output {
  address: own_address,
  // value: own_value,
  ..
} = own_output

but after aiken fmt command it looks like this
let Output { address: own_address, .. } =
  // value: own_value,
  own_output

i.e. the comments are placed outside the block
What should be the expected behavior?
Сomments should not be moved outside the block in this case

thanks for reporting


"during GET unexpected status code was returned: 200" when using Proxy

Hi all,
I'm using pivnet behind a proxy with SSL-Interception. This works for me, since i have added the proxy certificates to the ca-trust of the operating system.
The proxy is using authentication thus i defined
export http_proxy=http://$username:$password@$proxy
export https_proxy=http://$username:$password@$proxy

I can use pivnet for alle actions except downloading products. I get the following error
 0 B / 940.50 MiB [-------------------------------------------------]   0.00% 7s
Downloader.Get: problem while waiting for chunks to download: failed during retryable request: during GET unexpected status code was returned: 200

Using wget on the download url I get an proxy request message as last feedback, before the download successfully starts:
proxy request send, waiting for answer ... 200 OK

I suspect this proxy answer to be an unhandled response in pivnet download-product-files
I verified the issue with pivnet in the versions

2.0.1
1.0.4

I verified that the issue does not exist, when not using a proxy

Does your proxy have caching enabled? Does the 200 response include the full 940.50 MiB?
The downloader makes several requests for partial ranges, so it expects the responses to be HTTP 206 (Partial Content) https://github.com/pivotal-cf/go-pivnet/blob/master/download/downloader.go#L189
A caching proxy may combine ranges and return a full response (https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.8) so we may need to ensure Downloader handles that case.

Does your proxy have caching enabled?
yes, kind of. I am not able to access the proxy and configs (other team), but the proxy works roughly as follows:

it establishes the connection
it downloads the file locally to the proxy. while doing this the client only gets small byte-chunks so the connection is not lost
after finishing the download locally, AV-Scans/security checks are performed
after successfully checking the file, the proxy sends the full file to the client

Does the 200 response include the full 940.50 MiB?
I can guarantee, that this is NOT the case.

following a larger log from wget in debug mode (ips, hostnames, company-data redacted) where you can see the last two 200 codes. I suspect one of them to be unhandled. (I'm sorry for the german in the log, it's a system setting :-( )
wget -d -O "harbor_v${harbor_version}.pivotal2" --header "Authorization: Bearer $access_token" ${harbor_download_link}
Setting --output-document (outputdocument) to harbor_v2.0.3.pivotal2
Setting --header (header) to Authorization: Bearer "<REDACTED>"
DEBUG output created by Wget 1.14 on linux-gnu.

URI encoding = »UTF-8«
URI encoding = »UTF-8«
Converted file name 'download' (UTF-8) -> 'download' (UTF-8)
--2020-10-09 08:58:50--  https://network.pivotal.io/api/v2/products/harbor-container-registry/releases/749813/product_files/797038/download
Auflösen des Hostnamen »<REDACTED>
Caching <REDACTED FQDN> => <REDACTED IPs>
Verbindungsaufbau zu <REDACTED>:80... verbunden.
Created socket 4.
Releasing 0x0000000000f431d0 (new refcount 1).

---request begin---
CONNECT network.pivotal.io:443 HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Proxy-Authorization: Basic <REDACTED>
Host: network.pivotal.io:443

---request end---
proxy responded with: [HTTP/1.0 200 Connection established

]
Initiating SSL handshake.
Handshake successful; connected socket 4 to SSL handle 0x0000000000f60cf0
certificate:
  subject: /CN=network.pivotal.io
  issuer:  <REDACTED>
X509 certificate successfully verified and matches host network.pivotal.io

---request begin---
GET /api/v2/products/harbor-container-registry/releases/749813/product_files/797038/download HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Accept: */*
Host: network.pivotal.io
Connection: Close
Proxy-Connection: Keep-Alive
Authorization: Bearer "<REDACTED>

---request end---
Proxy-Anforderung gesendet, warte auf Antwort...
---response begin---
HTTP/1.1 302 Foun
Date: Fri, 09 Oct 2020 06:57:53 GMT
Vary: Accept-Encoding
Location: https://d13k9s5899twdr.cloudfront.net/partner-product-files/vmware-harbor/034a6270-64ca-4ab7-9cd4-924510d8f2aa?Expires=1602313073&Signature=a9UCikVkPD830x%7Eiu3dwVvvOUqtmqgG-dlV7ZvgqrMd2FeOjjhWOHU0CVSph4RpKCsn0xId47libvyquo1ykNAY%7EybFCZ%7ES-z0FuPPsjhJBYnuM9P7DZLpiCLbKOXlY3E6D3SIvdCQ-%7EoHu38mFDgCJIG5wuxTWxcBc1pZqESzIYIO3XZSNQb-sEDtseKvYtMW0KdJR-J-K-TKVO86uI2ScM-RjsLP4wa8JhJivf2u0QZFQCnybewWcEJRQrrdAKI4AIpZbVzgP66vkjlFo4oasy5DzaBlVnwX2dPlil9VxgJggXGoMQ3KRDc0-bWlmzMg78LIakVA6AMRKN5ViVew__&Key-Pair-Id=APKAIOIREZ2UWYGOZQDA&filename=034a6270-64ca-4ab7-9cd4-924510d8f2aa
X-Runtime: 0.103091
Connection: Keep-Alive
Content-Type: text/html; charset=utf-8
X-Request-Id: 7b6cd395-7dce-414f-8dc5-0acad6fa5af3
Cache-Control: no-cache
Referrer-Policy: strict-origin-when-cross-origin
X-Frame-Options: SAMEORIGIN
X-Xss-Protection: 1; mode=block
Transfer-Encoding: chunked
X-Vcap-Request-Id: c1889f9b-f27b-4c70-4724-d21b11f968ed
X-Download-Options: noopen
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Permitted-Cross-Domain-Policies: none

---response end---
302 Foun
Registered socket 4 for persistent reuse.
URI content encoding = »utf-8«
Platz: https://d13k9s5899twdr.cloudfront.net/partner-product-files/vmware-harbor/034a6270-64ca-4ab7-9cd4-924510d8f2aa?Expires=1602313073&Signature=a9UCikVkPD830x%7Eiu3dwVvvOUqtmqgG-dlV7ZvgqrMd2FeOjjhWOHU0CVSph4RpKCsn0xId47libvyquo1ykNAY%7EybFCZ%7ES-z0FuPPsjhJBYnuM9P7DZLpiCLbKOXlY3E6D3SIvdCQ-%7EoHu38mFDgCJIG5wuxTWxcBc1pZqESzIYIO3XZSNQb-sEDtseKvYtMW0KdJR-J-K-TKVO86uI2ScM-RjsLP4wa8JhJivf2u0QZFQCnybewWcEJRQrrdAKI4AIpZbVzgP66vkjlFo4oasy5DzaBlVnwX2dPlil9VxgJggXGoMQ3KRDc0-bWlmzMg78LIakVA6AMRKN5ViVew__&Key-Pair-Id=APKAIOIREZ2UWYGOZQDA&filename=034a6270-64ca-4ab7-9cd4-924510d8f2aa[folge]
Skipping 512 bytes of body: [You are being <a href="https://d13k9s5899twdr.cloudfront.net/partner-product-files/vmware-harbor/034a6270-64ca-4ab7-9cd4-924510d8f2aa?Expires=1602313073&Signature=a9UCikVkPD830x%7Eiu3dwVvvOUqtmqgG-dlV7ZvgqrMd2FeOjjhWOHU0CVSph4RpKCsn0xId47libvyquo1ykNAY%7EybFCZ%7ES-z0FuPPsjhJBYnuM9P7DZLpiCLbKOXlY3E6D3SIvdCQ-%7EoHu38mFDgCJIG5wuxTWxcBc1pZqESzIYIO3XZSNQb-sEDtseKvYtMW0KdJR-J-K-TKVO86uI2ScM-RjsLP4wa8JhJivf2u0QZFQCnybewWcEJRQrrdAKI4AIpZbVzgP66vkjlFo4oasy5DzaBlVnwX2dPlil9VxgJggXGoMQ3KRDc0-bWlmzMg78LSkipping 137 bytes of body: [IakVA6AMRKN5ViVew__&Key-Pair-Id=APKAIOIREZ2UWYGOZQDA&filename=034a6270-64ca-4ab7-9cd4-924510d8f2aa">redirected.] done.
URI content encoding = None
URI encoding = »UTF-8«
Converted file name 'download' (UTF-8) -> 'download' (UTF-8)
--2020-10-09 08:58:50--  https://d13k9s5899twdr.cloudfront.net/partner-product-files/vmware-harbor/034a6270-64ca-4ab7-9cd4-924510d8f2aa?Expires=1602313073&Signature=a9UCikVkPD830x%7Eiu3dwVvvOUqtmqgG-dlV7ZvgqrMd2FeOjjhWOHU0CVSph4RpKCsn0xId47libvyquo1ykNAY%7EybFCZ%7ES-z0FuPPsjhJBYnuM9P7DZLpiCLbKOXlY3E6D3SIvdCQ-%7EoHu38mFDgCJIG5wuxTWxcBc1pZqESzIYIO3XZSNQb-sEDtseKvYtMW0KdJR-J-K-TKVO86uI2ScM-RjsLP4wa8JhJivf2u0QZFQCnybewWcEJRQrrdAKI4AIpZbVzgP66vkjlFo4oasy5DzaBlVnwX2dPlil9VxgJggXGoMQ3KRDc0-bWlmzMg78LIakVA6AMRKN5ViVew__&Key-Pair-Id=APKAIOIREZ2UWYGOZQDA&filename=034a6270-64ca-4ab7-9cd4-924510d8f2aa
Found <REDACTED> in host_name_addresses_map (0xf431d0)
Verbindungsaufbau zu <REDACTED>:80... verbunden.
Created socket 5.
Releasing 0x0000000000f431d0 (new refcount 1).

---request begin---
CONNECT d13k9s5899twdr.cloudfront.net:443 HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Proxy-Authorization: Basic <REDACTED>
Host: d13k9s5899twdr.cloudfront.net:443

---request end---
proxy responded with: [HTTP/1.0 200 Connection established

]
Initiating SSL handshake.
Handshake successful; connected socket 5 to SSL handle 0x0000000000f737b0
certificate:
  subject: /C=US/ST=Washington/L=Seattle/O=Amazon.com, Inc./CN=d13k9s5899twdr.cloudfront.net
  issuer:  <REDACTED>
X509 certificate successfully verified and matches host d13k9s5899twdr.cloudfront.net

---request begin---
GET /partner-product-files/vmware-harbor/034a6270-64ca-4ab7-9cd4-924510d8f2aa?Expires=1602313073&Signature=a9UCikVkPD830x%7Eiu3dwVvvOUqtmqgG-dlV7ZvgqrMd2FeOjjhWOHU0CVSph4RpKCsn0xId47libvyquo1ykNAY%7EybFCZ%7ES-z0FuPPsjhJBYnuM9P7DZLpiCLbKOXlY3E6D3SIvdCQ-%7EoHu38mFDgCJIG5wuxTWxcBc1pZqESzIYIO3XZSNQb-sEDtseKvYtMW0KdJR-J-K-TKVO86uI2ScM-RjsLP4wa8JhJivf2u0QZFQCnybewWcEJRQrrdAKI4AIpZbVzgP66vkjlFo4oasy5DzaBlVnwX2dPlil9VxgJggXGoMQ3KRDc0-bWlmzMg78LIakVA6AMRKN5ViVew__&Key-Pair-Id=APKAIOIREZ2UWYGOZQDA&filename=034a6270-64ca-4ab7-9cd4-924510d8f2aa HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Accept: */*
Host: d13k9s5899twdr.cloudfront.net
Connection: Close
Proxy-Connection: Keep-Alive
Authorization: Bearer "<REDACTED>"
---request end---
Proxy-Anforderung gesendet, warte auf Antwort...
---response begin---
HTTP/1.0 200 OK
Age: 242935
Via: 1.1 eb1a8c1b1275e33a016e623478052111.cloudfront.net (CloudFront)
Date: Tue, 06 Oct 2020 11:28:59 GMT
ETag: "329ffed5681f5f7a792fe31a5716ca6a-19"
Server: AmazonS3
X-Cache: Hit from cloudfront
Connection: Keep-Alive
X-Amz-Cf-Id: 9DWWLDgH9nmtPsySL-J7CnuzHxcQiRqKoUz7rUiAhU3DA3wz5-jAVg==
X-Amz-Cf-Pop: FRA2-C2
Accept-Ranges: bytes
Last-Modified: Mon, 28 Sep 2020 04:45:02 GMT
Content-Length: 986189754
x-amz-version-id: S6sWlyyLr_hVZ8XmNRpyHnVPJsga.v5Z
Content-Disposition: attachment; filename=harbor-container-registry-2.0.3-build.15.pivotal

---response end---
200 OK
Disabling further reuse of socket 4.
Closed 4/SSL 0x0000000000f60cf0
Registered socket 5 for persistent reuse.
Länge: 986189754 (941M)
In »»harbor_v2.0.3.pivotal2«« speichern.

 0% [                                                                                ] 986.190      138KB/s  ETA 1h 56m ^

Maybe this url needs to be whitelisted? d13k9s5899twdr.cloudfront.net
https://network.pivotal.io/docs/faq#downloading

Hi,
Firewall is open. I can download with wget without problems.
Or do you mean in the proxy for ssl-interception?

Hi,
It seems your proxy changes the status code 206 Partial Content to 200 Ok.
Our downloader relies on 206 to function for multi-chunk download code, and this behaviour is already seen in azure proxies see here.
It can be fixed either by us changing the code for accepting 200 in addition to 206 or you fix your reverse proxy to don't change the status code 206 to 200.
Changing the code on our side won't be easy and we may need a thorough checking for not breaking the normal behaviour.

Thanks for the Response, i'll reach out to my proxy-team to see what they can do.

@sluetze also if your proxy team indicate that we are missing a header in our response (like Accept-Ranges: bytes) we will appreciate if they indicate in which response your proxy expects to see that header.


Ponyc update up to 0.15.0

We are switching to mainline ponyc for Wallaroo (#1482).  These changes begin that work, bringing us up to compatibility with ponyc 0.15.0.
Do not merge yet, as we need to decide how we intend to move these over in concert with pony-kafka.

@dipinhora You don't need to review this.  I put you on so that you could see this in case you were interested (given that I am working on parallel work on pony-kafka)

any code for OSX that uses pony_asio_event_create needs to be updated as part of this. Things like TCPSourceListener.
It's easy to overlook as it would still compile. Rather than having Linux and OSX calls to pony_asio_event, OSX now supports "one shot" so it should be:
      _event = @pony_asio_event_create(this, fd,
        AsioEvent.read_write(), 0, true)

in general (as an example)
and the OSX vs Linux differences for registering/unregistering events should change so that its always what the Linux code was doing.

This looks good except for the things we discussed "offline".

@SeanTAllen Here's what the event code looks like currently:
    ifdef linux then
      _event = @pony_asio_event_create(this, fd,
        AsioEvent.read_write_oneshot(), 0, true, true)
    else
      _event = @pony_asio_event_create(this, fd,
        AsioEvent.read_write(), 0, true, false)
    end

Just to be clear, you're saying that I should be replacing these blocks with:
   _event = @pony_asio_event_create(this, fd,
     AsioEvent.read_write(), 0, true)

@jtfmumm no, the opposite.
you want to favor the linux code, not the non-linux code.
_event = @pony_asio_event_create(this, fd,
        AsioEvent.read_write_oneshot(), 0, true, true)

@SeanTAllen Ok, I misinterpreted what you wrote above.  That makes more sense.

Closing in favor of #1542.


Add Project Access Token related endpoints

Add the endpoints mentioned in https://docs.gitlab.com/ee/api/project_access_tokens.html

Thank you ❤

@NARKOZ Would it be possible to have 5.1.0 cut with the recent changes? Thanks.

Sorry for the wait. Version 5.1.0 has just been released. Please see https://github.com/NARKOZ/gitlab/releases


Uncaught TypeError: Cannot read property 'scopeName' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.0
System: Mac OS X 10.10.3
Thrown From: atom-typescript package, v4.6.9
Stack Trace
Uncaught TypeError: Cannot read property 'scopeName' of undefined
At /Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:130

TypeError: Cannot read property 'scopeName' of undefined
  at TokenizedBuffer.module.exports.TokenizedBuffer.setGrammar (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:130:30)
  at DisplayBuffer.module.exports.DisplayBuffer.setGrammar (/Applications/Atom.app/Contents/Resources/app.asar/src/display-buffer.js:1151:35)
  at TextEditor.module.exports.TextEditor.setGrammar (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2264:33)
  at ts-view.TsView.createdCallback (/Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atom/components/ts-view.js:22:16)
  at Function.jQuery.extend.buildFragment (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:5114:20)
  at Function.jQuery.parseHTML (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:8817:18)
  at LineMessageView.jQuery.fn.init (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:2762:33)
  at LineMessageView.View (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:158:24)
  at LineMessageView.View (/Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atom/views/view.js:10:16)
  at new LineMessageView (/Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atom/views/lineMessageView.js:11:16)
  at /Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atom/views/mainPanelView.js:404:48
  at Array.forEach (native)
  at Object.errorView.setErrors (/Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atom/views/mainPanelView.js:402:47)
  at /Users/ivanvoznyakovsky/.atom/packages/atom-typescript/dist/main/atomts.js:87:82

Commands

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "base16-tomorrow-dark-theme"
    ]
  }
}

Installed Packages
# User
.bin, vundefined
atom-alignment, v0.12.1
atom-typescript, v4.6.9
autocomplete-paths, v1.0.2
color-picker, v2.0.7
editorconfig, v1.0.0
emmet, v2.3.10
file-icons, v1.5.8
highlight-line, v0.11.0
linter, v1.0.9
minimap, v4.10.0
minimap-git-diff, v4.1.3
minimap-highlight-selected, v4.3.0
project-manager, v1.15.10

# Dev
No dev packages

My recent integration of the atom-text-editor into error view seems to have triggered this. I can't reproduce but I've been meaning to disable this integration for errors / build errors anyways, so I'll do that now :rose:


Remove extraneous '}' characters from shell_plus docs

This commit removes some spurious brackets that confused me when
reading the documentation.

Coverage remained the same at 38.172% when pulling cee8e12f700949622bf65dc62a6d83ddb2c26832 on mhl:remove-extraneous-curly-brackets into 0064ed9011cfc462733fa9812322a71ccaa354e7 on django-extensions:master.

Thanks !


Login method

Your login method is a void that doesn't take any arguments, hence an error being thrown: The method login() in the type Skype is not applicable for the arguments (String, String)

die

Please use the maven version (0.08-SNAPSHOT). The new version that you manually compiled hasn't been documented yet.


i18n: translatable compound messages

This allows translatable strings to contain format arguments. It enables compound messages:
translation resources:

"tree-punch": "You punch the {0} tree.",
"tree-species-fir": "fir",
"tree-species-palm": "palm",

application code:
translate("${#tree-punch}", tree.getSpecies())

result:

You punch the palm tree.

(This would be a much more compelling demonstration if I knew how to talk about trees in more than one language.)
For this it uses the MessageFormat class from the Java library. That also lets it support things like locale-aware date and number formatting. (and probably pluralization? but that interface looks messy and I haven't tested it.)
How to test
The game-loading error message from #4004 has a compound message. If you know any other languages, you could provide their .lang files with a translation for load-game-error.
Oh, and check to see that the existing text isn't broken. That's probably the more important thing.
Outstanding before merging

[ ] Merge #4004 (a dependency of this branch)
[ ] Does this break API compatibility? It adds varargs to several interfaces marked as public @API. The changes are source compatible, because it's fine to pass zero varargs, but are they binary compatible?
[ ] does this conflict with #4017 (NUI extraction)?
[ ] unit tests
[ ] Will need developer documentation. We have a mishmash of the standard Java interface and homegrown formats.

reminder: merging #4004 will make it much clearer what's actually in this branch

Oh, this should really be in draft state until it has those tests and docs ready.
With those in place, it wouldn't hurt to merge this. The API being compatible-enough, providing a way to do a little more with only a minor change from the current methods.
but honestly, now that NUI is split out, I think it's worth a closer look at this interface in Terasology's code and how it's split between Terasology and NUI and how internationalizable resources work in NUI. Cuz this looks kludgy, especially after the NUI split, and if there's no rush to get this in it's worth a little more thought.


Broken link fix on dns doc page

Old link gives 404; the one under build/kube-dns is the most relevant I could find, but please point if it should be resolved to anything else.

I signed the CLA

LGTM

Thanks, @alena1108 !


Implement Fallout 76 elements and factions on map

I barely played FO76, and not sure how much even of it is still applicable 200 years later.


PoC of feature/pipe based on feature/stdin

Took feature/stdin as inspiration and rewrote parts of to create a true 'pipe' experience. While here did some UI tweaking and safeguarding against errors.

Aaah, tried to get the checks to run. But because this is a pull request to a branch they will not run.

There were some issues with the code and some changes which were bit ninja changes.
I dropped the functionality of --force, this is a personal preference of course.
In general I change all log to be disabled. I like this behavior because it is more close to what general Linux tools do.
Also fix the progress bar to showing a estimate anymore. It now estimates the total amount of chunks base on the file size.


Can`t realize ap composition

Fantasy Land spec:
v.ap(u.ap(a.map(f => g => x => f(g(x))))) is equivalent to v.ap(u).ap(a) (composition)
Implementation:
const v = Task.of(f => g => x => f(g(x)))
const u = Task.of(x => x * 3)
const a = Task.of(x => x + 3)
v
	.ap(u
		.ap(a
			.map(f => g => x => f(g(x)))))
	.fork(console.error, console.log)
Log: g => x => f(g(x))
v
	.ap(u)
	.ap(a)
	.fork(console.error, console.log)
Log: x => f(g(x))

The composition rule states:
v ap (u ap (a map \f. \g. \x. f (g x)))  <==>  (v ap u) ap a

But this was changed at some point. The old specification (which is what this library implements) instead stated:
((a map \f. \g.  Thus, you need:
const v = Task.of(3);
const u = Task.of(x => x * 3)
const a = Task.of(x => x + 3)

With that, you should have the equivalence:
a.ap(u.ap(v))  <==>  a.map(f => g => x => f(g(x))).ap(u).ap(v)

Here's the relevant discussion about the change: https://github.com/fantasyland/fantasy-land/issues/50
Note that this library is not maintained anymore. The new version implements Fantasy Land 2.x specification (https://folktale.origamitower.com/api/v2.3.0/en/-unknown-module-.folktale.concurrency.future._future.fantasy-land-ap.html)

Hmm. Actual specification: https://github.com/fantasyland/fantasy-land#apply

Yes, that's the version 4 of the Fantasy Land specification.
This library does not implement version 4. It implements version 1. In version 1, the arguments to ap were flipped.


Rename lightSetup, material to lightSetupKey, materialKey in certain places.

Motivation and Context
Since #837 keeps failing the cI test, let us split that PR even further into 2 PRs. See what will happen.

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@jturner65 : Thank you very much for your quick response! I appreciate it!


Webpack upgrade breaks TypeScript interface exports

Bug report
Describe the bug
TypeScript interfaces and type aliases that are exported in an object break the dev and prod build. The build will fail with a Module parse failed: Export 'XYZ' is not defined message.
To clarify what I mean with object export, here is a small example:
interface MyInterface {};
export { MyInterface };

This used to work fine in Next 7. The bug was probably introduced in https://github.com/zeit/next.js/releases/tag/v8.0.0-canary.12. Version v8.0.0-canary.11 does not have this problem.
To Reproduce

Setup https://github.com/zeit/next.js/tree/canary/examples/with-typescript
Make sure it runs correctly
Open any component (e.g. components/List.tsx)
Add export { Props }; to the last line
The build breaks

System information

OS: Windows 10
Version of Next.js: 8.0.3

@timneutkens
I could confirm that it would work by canceling #6114.
How should I fix it ...?


send event when redis machine shutdown

Hi,
i am using ioredis with nuxt.js. i used every event on ioredis (error, close etc) in documentation but couldn't throw error when redis server shutdown.  nothing happening when shutdown redis machine and my app not responding becuse of that.
do you have any suggestion about that problem?

the nodejs application will exit if the connection has error. I am also still trying to catch the error and fail gracefully but still not available yet...

the nodejs application will exit if the connection has error. I am also still trying to catch the error and fail gracefully but still not available yet...

Hi @vskavgaci , there should be events when redis server is down. Namely there should be "error" and "close".
const redis = new Redis(6399);

redis.on("error", console.error.bind(console, "error"));
redis.on("close", console.error.bind(console, "close"));

The above code works for me.
@Aung-Myint-Thein Can you upgrade to the latest version and see if the issue still exists?
Closing this, feel free to reopen if there are still issues.


Add a button to download a PM.

I've wanted the ability to locally archive PMs for a while because the storage space provided in the savebox and inbox are tiny.
Downloading as eml is fairly simple, but plain-text download might be easier and more desirable?
Page mockup (just one button added at the bottom)

Part II: consider applicability & implementation for the WIP PM rewrite.


Converting a $class to a string and also ref $class gives incorrect result

Converting a $class to a string and also ref $class gives incorrect result.  Classes in perl are represented as strings.  In Python we use class objects, but they need to act as strings, so str(class) needs to be the classname, and _ref_scalar(class) needs to be the empty string.

Fixed in v1.021


gnome3.gnome-session: 3.34.1 -> 3.34.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-session/versions.
meta.description for gnome3.gnome-session is: '"GNOME session manager"'.
meta.homepage for gnome3.gnome-session is: '"https://wiki.gnome.org/Projects/SessionManagement"

Checks done (click to expand)

built on NixOS

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

0 of 0 passed binary check by having a zero exit code.

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

found 3.34.2 with grep in /nix/store/9p242jw5k009499ycmvzm5qsxww4zhch-gnome-session-3.34.2

directory tree listing: https://gist.github.com/04deb765103065b949c474854eeb12a3

du listing: https://gist.github.com/257b944a481b86840e46381a31a91e29

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

15 total rebuild path(s)
5 package rebuild(s)
5 x86_64-linux rebuild(s)
5 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
5 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gnome3.gnome-control-center
gnome3.gnome-session
gnome3.gnome_control_center
gnome3.gnome_session
pantheon.elementary-session-settings

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9p242jw5k009499ycmvzm5qsxww4zhch-gnome-session-3.34.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnome3.gnome-session https://github.com/r-ryantm/nixpkgs/archive/b37b684ee413a1da9a659db1c27d6ff883a67e3a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9p242jw5k009499ycmvzm5qsxww4zhch-gnome-session-3.34.2
ls -la /nix/store/9p242jw5k009499ycmvzm5qsxww4zhch-gnome-session-3.34.2/bin

cc @lethalman @jtojnar @hedning @worldofpeace for testing.

Changes: https://download.gnome.org/sources/gnome-session/3.34/gnome-session-3.34.2.news


[improve][HIP] HIP-01: Refactoring AbstractCollect

What's changed?
When I was writing unit tests, I noticed that there was a preCheck validation logic in each collector. Therefore, I suggest implementing this method separately to make the code structure clearer and more conducive to unit testing.
Checklist

[x]  I have read the Contributing Guide
[x]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

@tomsun28 The vote is complete; maybe we can merge this PR.


Add alloys?

I know a lot of addons like using alloys as well as ores, so I think it would be neat if this project contained alloys made with both the ores in the project as well as vanilla ores.
Alloy suggestions:

Steel (iron + coal)
Brass (copper + zinc)
Bronze (copper + tin)
Rose Gold (copper + gold)
Constantan (copper + nickel)
Invar (iron + nickel)

This is a decently long list, so I don’t think all of these need to be added.
Some sort of way of crafting alloys should also be added.

This is something that has been discussed as well. We aren't sure if we want to directly include alloys into the "Unified Ore" creator pack, or perhaps a new pack called "Unified Alloys". Even though we haven't made a decision yet about how to incorporate them, it is something we want to do!


The msvs_version option doesn't work from .npmrc nor from environment variable

I'm using the latest node-gyp.
I've found that msvs_version doesn't actually work from .npmrc nor from environment variables.
Here's what happens.

If you set $env:npm_config_msvs_version=2019; node-gyp configure, what happens is that the gyp.opts contains msvs-version, but not msvs_version. This leads the configure command to assume that the env variable hasn't been set.
If you set npm config set msvs_version 2019 --location project, it also doesn't work, instead nothing is read at all, the gyp.opts does not contain msvs_version at all.
If you set node-gyp configure --msvs_version=2019 then it does work, and it shows up on gyp.opts.

https://github.com/nodejs/node-gyp/pull/2644

This issue has been stale for a long time. If there are no objections, I will close this issue next Mon-Tue. In case something similar happens again please open a new issue.
In addition, https://github.com/nodejs/node-gyp/pull/2644 addresses it.

So what does that mean if it is no longer allowed to set it? Is it now automatic?

https://github.com/nodejs/node-gyp/blob/main/README.md#on-windows


Health status marked as UNKNOWN upon crash instead of DOWN

The /health endpoint returns status "UNKNOWN" at the body and status code 200 when a uncaught exception happen in the application.
The application crashes and the stacktrace is logged correctly, but since the healthcheck still returns something that is not an error, it is never captured by any orchestration.
This became a problem in our cluster. For example, when a Kafka node fails, all threads with partitions that had it as the leader throws an exception and crashes, which brings the whole app down. This is the intended behaviour for Kafka Streams, the application crashes and you can restart it, manually or automatically.
What we expected
The health-check endpoint would mark a crashed application as being unhealthy, Kubernetes would restart the pod and the application would connect to the new leader.
What actually happened
The health-check endpoint changed to unknown and consider that a "OK". Therefore Kubernetes, logically, did nothing.

Is that an intended behaviour? Currently, the only way for us to have applications auto-healing is to inject a bash script to parse the response consider the "UNKNOWN" from the body as unhealthy. To me it seems to defeat the purpose of having a health-check endpoint, if you need to use a bash script you can just check if the process is running.

Hi @Fryuni, thanks for reporting this issue. Which version of Azkarra are you currently running ? I will fix this soon.

We are using v0.5.0. We can try with v0.6.0 if there was any changes that might affect this.

Hi @fhussonnois , do you have an idea of what is the problem and/or an estimate ETA? Just so I know if I can push this down on my sprint or if I should make a more decent script to send to production while you are on it 😄

@Fryuni could you give the version of Apache Kafka and Kafka Streams you are using ? I didn't succeed to reproduce StreamThread failure when a leader election is triggered.
Also, can you confirm to me that the state your Kafka Streams instance is equal to NOT_RUNNING when you observe the behaviour ? A fix should be available this week.

The cause of the crash in my example might be exclusive to our scenario (how we route our connections to kafka), but the same happens with any exception on the code, to reproduce you can create an app that always throw an exception.
We are using Kafka and Kafka Streams version 2.4.0

And yes, on the logs the state goes RUNNING -> PENDING_SHUTDOWN -> NOT_RUNNING right after the exception is logged

This issue has been fix in Azkarra v0.6.1. I strongly recommand to you to upgrade.

Thaaanks @fhussonnois !!


HTTP PUT method

Hey!
Nice Plugin, but why is there no PUT or DELETE HTTP method?
Thank you!
Kirrg

Because the original authors of this plugin didn't need it.
Check these issues and add a comment if you'd like.


[AutoRelease] t2-media-2022-06-22-13648(Do not merge)

https://github.com/Azure/sdk-release-request/issues/2933
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1012
BuildTargetingString
azure-mgmt-media
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/2933


Disabled breakpoint reverts the breakpoint to original location (not where it bound)

@isidorn @weinand
We wanted to check what we are seeing is expected.
If a breakpoint is set on line n, and that breakpoint bound to line m, when the breakpoint is disabled (but the debug session is still running), the glyph goes back to line n.

VS doesn't behave that way: the disabled breakpoint stays on line m until the debugging session is stopped. When the debugging session is stopped, the breakpoint goes back to n.

Any thoughts whether it would make sense for VSCode to remember the line a breakpoint bound to and keep that information until the debugging session finishes?

Yes this is designed behavior - we were inspired by the chrome debugger which behaves that way.
When the breakpoint is disabled making it jump to the original assigned position feels natural to me.
Closing as designed, but I have no strong opinion here so if @edumunoz or @weinand have strong preference I can easily be conviced to go in another direction.

Looping in @jacdavis and @delmyers in case they have a strong preference.

My only concern is the lack of unity between the VS experience and the Vscode experience as we try and unify the design and do things like support VSCode debug adapters inside Visual Studio. I suspect users are unlikely to notice this change in behavior, but if they did, it would appear as a bug in which ever product they were less familiar with.  I suspect Xamerin Studio probably has a third behavior in this case as well.


Install iiif_print into Essi

Summary
Essi is a Hyrax app. This ticket serves two purposes.

[ ] Test generator on a hyrax app
[ ] Install iiif_print into Indiana

Acceptance Criteria

[ ] Indiana should have iiif_print installed.
[ ] ideally iiif_print should be fully functional, but depending on the level of effort for such configurations, this may be separated into its own ticket. Ref: Features List #66

Screenshots or Video
Testing Instructions
Notes

Will they need to upgrade their bulkrax from 1.0.2 to 5.0?

Timebox 4 hours

IIIF Dependencies

Status
Package
Essi
IIIF Print

✅
Fits
1.5.5
1.5.5

⚠
Tesseract
4.1.1
4.1.3

⚠
LibreOffice
<IP_ADDRESS>
<IP_ADDRESS>

✅
GhostScript*
9.53.3
n/a

❌
popper-utils
n/a
21.11.0

❌
ImageMagick
6.9.11-60
7.1.0-57

⚠
libcurl3
7.74.0
7.80.0

⚠
libgbm1**
n/a
n/a

* Does not have but is listed as a dependency
** I could not find the version
UI test
Parent work to child work relation
Seems to be working, you can only see the child work in the UV and not the _items partial.
Errors seen:
convert-im6.q16: attempt to perform an operation not allowed by the security policy PDF' @ error/constitute.c/IsCoderAuthorized/421.`
This likely contributed to why the PDF derivative was not created correctly, file seems malformed and PDF splitting does not work.
Ref: https://github.com/scientist-softserv/iiif_print/blob/main/lib/iiif_print/image_tool.rb#L79
OCR text is not getting picked up.  The txt, json, and xml do get created but with no text.  When running tesseract in the container, it does seem to work though.
Bulkrax test
We tested a Bulkrax import and it looks like at the moment we do not need to upgrade Bulkrax.
***** INCLUDE CSV HERE *****
NOTE
Essi has their own text extraction that saves the output to solr_doc['word_boundary_tsi']
Ref: https://github.com/scientist-softserv/essi/blob/main/app/indexers/essi/file_set_indexer.rb#L13
This instantiates this object https://github.com/scientist-softserv/essi/blob/main/lib/newspaper_works/text_extraction/alto_reader.rb
Which is effectively the same thing as https://github.com/scientist-softserv/iiif_print/blob/main/lib/iiif_print/text_extraction/alto_reader.rb
diff essi/lib/newspaper_works/text_extraction/alto_reader.rb essi/vendor/engines/iiif_print/lib/iiif_print/text_extraction/alto_reader.rb
5c5
< module NewspaperWorks
---
> module IiifPrint
42c42
<           match = attrs.select { |e| e[0].casecmp?('WIDTH') }[0]
---
>           match = attrs.find { |e| e[0].casecmp?('WIDTH') }
115,118c115,119
<         builder = NewspaperWorks::TextExtraction::WordCoordsBuilder.new(words,
<                                                                         @image_width,
<                                                                         @image_height)
<         builder.to_json
---
>         IiifPrint::TextExtraction::WordCoordsBuilder.json_coordinates_for(
>           words: words,
>           width: @image_width,
>           height: @image_height
>         )

Essi has a bunch of NewspaperWorks code (but did not install the gem) sprinkled throughout the codebase, likely because they didn’t need the entire gem and only a few features like Alto OCR.
MISC
Potential bug in, worth a quick look:
Hyrax::Actors::CreateWithFilesOrderedMembersActor.prepend Extensions::Hyrax::Actors::CreateWithFilesOrderedMembersActor::AttachFilesWithMetadata

Ref: https://github.com/IU-Libraries-Joint-Development/essi/blob/eb1c9b652f1b96eda0eb65655d9b70e68bfe5042/app/actors/essi/actors/create_with_remote_files_ordered_members_structure_actor.rb#L1


Complete ties should be broken randomly

It's possible for both the territory and the territory integral of two players to be the same. (Especially when someone is testing versions of their bots locally -- they may behave identically.)
Such ties should be broken randomly (instead of based on player index).
I believe the relevant piece of code is at:
https://github.com/HaliteChallenge/Halite/blob/master/environment/core/Halite.cpp#L347
Which I think could be replaced with something like this, except I'm not a C++ person. Presumably we also need to import some PRNG function and seed it at some point...
// Sort newRankings by last territory count. If it's the same, use the territory integral instead to break that tie.
// But if that's the same, flip a coin.
std::stable_sort(newRankings.begin(), newRankings.end(), [&](const unsigned int & u1, const unsigned int & u2) -> bool {
    if (last_territory_count[u1] != last_territory_count[u2]) {
        return last_territory_count[u1] < last_territory_count[u2];
    }
    if (full_territory_count[u1] != full_territory_count[u2]) {
        return full_territory_count[u1] < full_territory_count[u2];
    }
    return RESULT_OF_SOME_COIN_FLIP;    // Don't know the C++ way to do this.
});

It would be nice if ties were actually treated as ties, but I think it's too late to make such a drastic change. Randomization is a compromise that would help, but from what @Sydriax has said before I'm not sure even that would be accepted at this point since it would change results of old replays using the same seed and competitors?

I think these "complete ties" are already broken randomly, because as you say, they are broken by player index -- and the indices were assigned randomly.  At least I think they are (should be), I haven't checked the code.  If you are using the @smiley1983 halite-match-manager locally, the player indices are certainly assigned randomly (that code I know), so there is no bias in the tiebreak.

Yes, on the competition server this isn't an issue in practice since (except for the seed) the players are listed in a random order.


cannot run roslaunch realsense2_camera rs_camera.launch

I cant get the frames, when I run roslaunch realsense2_camera rs_camera.launch.  I tried it with realsense-viewer, and it was the same. However the realsense-viewer` on win10 can works.
I got the output below:
vtol@vtol:~$ roslaunch realsense2_camera rs_camera.launch
... logging to /home/vtol/.ros/log/f41a4d40-f943-11e8-8473-f8633f4a9bbf/roslaunch-vtol-31294.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
WARNING: disk usage in log directory [/home/vtol/.ros/log] is over 1GB.
It's recommended that you use the 'rosclean' command.

started roslaunch server http://vtol:45511/

SUMMARY
========

PARAMETERS
 * /camera/realsense2_camera/accel_fps: 1000
 * /camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
 * /camera/realsense2_camera/align_depth: False
 * /camera/realsense2_camera/aligned_depth_to_color_frame_id: camera_aligned_de...
 * /camera/realsense2_camera/aligned_depth_to_fisheye_frame_id: camera_aligned_de...
 * /camera/realsense2_camera/aligned_depth_to_infra1_frame_id: camera_aligned_de...
 * /camera/realsense2_camera/aligned_depth_to_infra2_frame_id: camera_aligned_de...
 * /camera/realsense2_camera/base_frame_id: camera_link
 * /camera/realsense2_camera/color_fps: 30
 * /camera/realsense2_camera/color_frame_id: camera_color_frame
 * /camera/realsense2_camera/color_height: 480
 * /camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
 * /camera/realsense2_camera/color_width: 640
 * /camera/realsense2_camera/depth_fps: 30
 * /camera/realsense2_camera/depth_frame_id: camera_depth_frame
 * /camera/realsense2_camera/depth_height: 480
 * /camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
 * /camera/realsense2_camera/depth_width: 640
 * /camera/realsense2_camera/enable_color: True
 * /camera/realsense2_camera/enable_depth: True
 * /camera/realsense2_camera/enable_fisheye: True
 * /camera/realsense2_camera/enable_imu: True
 * /camera/realsense2_camera/enable_infra1: True
 * /camera/realsense2_camera/enable_infra2: True
 * /camera/realsense2_camera/enable_pointcloud: False
 * /camera/realsense2_camera/enable_sync: False
 * /camera/realsense2_camera/filters:
 * /camera/realsense2_camera/fisheye_fps: 30
 * /camera/realsense2_camera/fisheye_height: 480
 * /camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
 * /camera/realsense2_camera/fisheye_width: 640
 * /camera/realsense2_camera/gyro_fps: 1000
 * /camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
 * /camera/realsense2_camera/infra1_fps: 30
 * /camera/realsense2_camera/infra1_frame_id: camera_infra1_frame
 * /camera/realsense2_camera/infra1_height: 480
 * /camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
 * /camera/realsense2_camera/infra1_width: 640
 * /camera/realsense2_camera/infra2_fps: 30
 * /camera/realsense2_camera/infra2_frame_id: camera_infra2_frame
 * /camera/realsense2_camera/infra2_height: 480
 * /camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
 * /camera/realsense2_camera/infra2_width: 640
 * /camera/realsense2_camera/json_file_path:
 * /camera/realsense2_camera/pointcloud_texture_index: 0
 * /camera/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
 * /camera/realsense2_camera/rosbag_filename:
 * /camera/realsense2_camera/serial_no:
 * /rosdistro: kinetic
 * /rosversion: 1.12.14

NODES
  /camera/
    realsense2_camera (nodelet/nodelet)
    realsense2_camera_manager (nodelet/nodelet)

auto-starting new master
process[master]: started with pid [31304]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to f41a4d40-f943-11e8-8473-f8633f4a9bbf
process[rosout-1]: started with pid [31317]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [31334]
process[camera/realsense2_camera-3]: started with pid [31335]
[ INFO] [1544093089.489847818]: Initializing nodelet with 4 worker threads.
[ INFO] [1544093089.534657002]: RealSense ROS v2.1.1
[ INFO] [1544093089.534686809]: Running with LibRealSense v2.16.3
[ INFO] [1544093089.700663846]: getParameters...
[ INFO] [1544093089.740896678]: setupDevice...
[ INFO] [1544093089.740925861]: JSON file is not provided
[ INFO] [1544093089.740954524]: ROS Node Namespace: camera
[ INFO] [1544093089.740980467]: Device Name: Intel RealSense D435
[ INFO] [1544093089.740994057]: Device Serial No:<PHONE_NUMBER>22
[ INFO] [1544093089.741010187]: Device FW version: <IP_ADDRESS>
[ INFO] [1544093089.741024493]: Device Product ID: 0x0B07
[ INFO] [1544093089.741040234]: Enable PointCloud: Off
[ INFO] [1544093089.741061027]: Align Depth: Off
[ INFO] [1544093089.741077263]: Sync Mode: Off
[ INFO] [1544093089.741159945]: Device Sensors:
[ INFO] [1544093089.741193004]: Stereo Module was found.
[ INFO] [1544093089.741214479]: RGB Camera was found.
[ INFO] [1544093089.741253269]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1544093089.741271435]: (Gyro, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1544093089.741288574]: (Accel, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1544093089.741307209]: setupPublishers...
[ INFO] [1544093089.743488527]: Expected frequency for depth = 30.00000
[ INFO] [1544093089.769186932]: Expected frequency for infra1 = 30.00000
[ INFO] [1544093089.792588615]: Expected frequency for infra2 = 30.00000
[ INFO] [1544093089.813684158]: Expected frequency for color = 30.00000
[ INFO] [1544093089.835069448]: setupStreams...
 06/12 18:44:49,836 WARNING [140571855181696] (sensor.cpp:338) Unregistered Media formats : [ UYVY ]; Supported: [ ]
[ INFO] [1544093089.838501282]: depth stream is enabled - width: 640, height: 480, fps: 30
[ INFO] [1544093089.838675021]: infra1 stream is enabled - width: 640, height: 480, fps: 30
[ INFO] [1544093089.838829980]: infra2 stream is enabled - width: 640, height: 480, fps: 30
[ INFO] [1544093089.844470492]: color stream is enabled - width: 640, height: 480, fps: 30
[ INFO] [1544093089.912097527]: num_filters: 0
[ INFO] [1544093089.912134821]: publishStaticTransforms...
[ INFO] [1544093089.912364416]: RealSense Node Is Up!
[ INFO] [1544093089.912393778]: Start updating dynamic parameters...
 06/12 18:44:49,965 WARNING [140571855181696] (types.cpp:57) start_streaming(...) failed. UVC device is already streaming!
 06/12 18:44:49,965 WARNING [140571855181696] (types.cpp:57) start_streaming(...) failed. UVC device is already streaming!
 06/12 18:44:49,965 WARNING [140571855181696] (types.cpp:57) start_streaming(...) failed. UVC device is already streaming!
 06/12 18:44:49,965 WARNING [140571855181696] (types.cpp:57) start_streaming(...) failed. UVC device is already streaming!
[ INFO] [1544093090.143278313]: Done updating dynamic parameters...
 06/12 18:44:54,907 WARNING [140571100301056] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
 06/12 18:44:54,914 WARNING [140571085096704] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
 06/12 18:44:54,919 WARNING [140571074230016] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
 06/12 18:44:59,911 WARNING [140571100301056] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
 06/12 18:44:59,919 WARNING [140571085096704] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
 06/12 18:44:59,921 WARNING [140571074230016] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds
^C[camera/realsense2_camera-3] killing on exit
[camera/realsense2_camera_manager-2] killing on exit
[ INFO] [1544093104.115755736]: Interrupt Signal is received! Terminating RealSense Node...
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

the output of lsusb and lsusb -t for the camera
vtol@vtol:~$ lsusb
Bus 002 Device 004: ID 8086:0b07 Intel Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

vtol@vtol:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 2: Dev 4, If 0, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 4, If 1, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 4, If 2, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 4, If 3, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 4, If 4, Class=Video, Driver=uvcvideo, 5000M

output of uname -a
vtol@vtol:~$ uname -a
Linux vtol 4.15.0-42-generic #45~16.04.1-Ubuntu SMP Mon Nov 19 13:02:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Output of modinfo uvcvideo | grep "version:"
vtol@vtol:~$ modinfo uvcvideo | grep "version:"
version:        1.1.2.realsense-1.3.4
srcversion:     C4FB5E9B212E9C39ED6CD7C

the issue of "Frames didn't arrived within 5 seconds" is known. Currently it usually means that you need to disconnect and reconnect the camera or set the color_fps to half of the infra1_fps (i.e., 15 and 30 fps).
However, since you mention that there is a problem with the realsense_viewer in linux, I would open the issue in the librealsense page: https://github.com/IntelRealSense/librealsense

Thanks
I update the framework, it works now

Update the framework. Refer to https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/Linux-RealSense-D400-DFU-Guide.pdf

Hi all,
Is that means if I update the framework, the issue of "Frames didn't arrived within 5 seconds" will be gone completely?
Best,
Samuel


Kubernetes pods stuck with multiple S3 mount points

Mountpoint for Amazon S3 version
aws-mountpoint-s3-csi-driver-1.3.1
AWS Region
us-east-1
Describe the running environment
Azure Kubernetes Cluster
Mountpoint options
allow-delete
allow-other
region us-east-1
uid

What happened?
Azure Kubernetes Cluster failed to mount multiple S3 mount points, but one S3 mount point can work.
Relevant log output
No response

Found the cause, volume handler cannot be the same, closing


Ensure rimraf 2.4.x doesn't apply globs when moving directories.

Fixes: #16

published as 2.1.1. Thank you very much.


use title case for all placeholder text

fixes #638
provides more consistency to kiln-specific UI elements

Coverage increased (+3.3%) to 77.517% when pulling f7dd1a86279b51ee04bb8b00a7c10700a6583080 on placeholder-titlecase into 2fcb1d698c1fbdd11c9c32a291b788885b261dce on master.


OpenCV upgrade e.g. to 3.4.8

might need Java 12
class file has wrong version 56.0, should be 52.0

see https://trac.macports.org/ticket/60193


feat: handle page streaming from query/4

reuse existing prepare_execute function, which already handles page streaming.
this fixes some issues where xandra would return a paginated result, with exandra throwing an exception

Hi @noaccOS, could you please update your PR? I had to fix the build pipeline.
Thanks!


[stable/airflow] Worker CrashLoopBackOff running chart version 2.8.7

Describe the bug
I was using this chart with version 2.8.6, after i upgrade to 2.8.7, the worker pods can't run, it restarts all the time.
Here's the worker log:
waiting 60s...
executing worker...
[2019-06-06 14:38:41,905] {settings.py:174} INFO - settings.configure_orm(): Using pool settings. pool_size=5, pool_recycle=1800, pid=1
[2019-06-06 14:38:42,444] {__init__.py:51} INFO - Using executor CeleryExecutor

Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Kubernetes:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.6-gke.5", GitCommit:"46b3ddd492a78deae773f24b47c5c564a9b928b1", GitTreeState:"clean", BuildDate:"2019-05-18T01:19:43Z", GoVersion:"go1.11.5b4", Compiler:"gc", Platform:"linux/amd64"}

Which chart: 2.8.7
What happened:
Worker pods restarting
What you expected to happen:
Worker pods running
How to reproduce it (as minimally and precisely as possible):
helm upgrade --install --version 2.8.7 airflow stable/airflow --namespace airflow

Anything else we need to know:

Apparently  a dependency was conflicting with airflow, closing it.

How can this be fixed? I am on the chart version 3.0.0, and with the docker image 1.10.3 I still get this silent crash. If I am on 3.0.0 with 1.10.2 I get this error: https://github.com/puckel/docker-airflow/issues/342
What is the combination of versions that is stable and working currently for Airflow (helm chart)?


Changing Modpack versions

It would be handy, if it was possible to choose between the various versions of modpacks, under the "Change Version" tab of the instance:

Yeah, thats a good idea, I should also add a way to check/show updates as well.

Yeah - preferably a check while the launcher begins, so you realize you need to update, before launching the game.

Its now in.

Thank you, the OneClient is shaping out nicely :D


App crash after tapping search button

Steps to reproduce

Open Neko App
Select Browse tab
Tap Search button

Expected behavior
After tapping search button it should open menu for searching certain comic based on filter
Actual behavior
Sending error message logs and after restarting the app the issue still exist
Crash logs
neko_crash_logs.txt
Neko version
2.16.9
Android version
Android 12
Device
POCO X3 NFC
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

#1861


Bad condition for succeed - bug

Challenge http://www.freecodecamp.com/challenges/waypoint-use-conditional-logic-with-ifelse-statements has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
"Create an if-else statement to return heads if the flip var is zero, or else return tails if it's not."
The condition is exactly opposite. If the flip var is zero, it has to return "tails" for the test to succeed.

It works both ways

@Harpner thanks for posting this issue!
I've just opened a PR which fixes this issue. Thank you for your contribution!

Please review the Guidelines for Contributing, thank you!.


Unhandled Exception - 'Access to the path 'DLSSUpdater.exe' is denied.'

I have been unable to update this application (using the internal updater) for multiple releases now.
I keep getting the following error after pressing "Ok" when the application finds a new software-update during startup.
Encountered an unhandled exception:
  at System.IO.FileSystem.RemoveDirectoryRecursive(String fullPath, WIN32_FIND_DATA& findData, Boolean topLevel)
  at System.IO.FileSystem.RemoveDirectory(String fullPath, Boolean recursive)
  at DlssUpdater.Windows.Splashscreen.Splashscreen.OnContentRendered(EventArgs e)
  at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)
  at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
  at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)```

I have tried running the application ad "Admin", but that doesn't help.

I am running Windows 10, by the way.

Any ideas?

Duplicate of #30


Unable to open /dev/kfd read-write: Cannot allocate memory

As I try:
`rocminfo
ROCk module is loaded
Unable to open /dev/kfd read-write: Cannot allocate memory
igor is member of render group
hsa api call failure at: /src/rocminfo/rocminfo.cc:1142
Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events.
`
look into dmesg:
`sudo dmesg | grep kfd
[    3.548555] kfd kfd: amdgpu: PITCAIRN  not supported in kfd
`
Info:
`uname -r
5.4.0-54-generic
 lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM]
`
I've been using this guidance here: https://github.com/Grench6/RX580-rocM-tensorflow-ubuntu20.4-guide
Thanks in advance for help!

My user needed to be added to both the video and render groups on my machine.  Also need to reboot after setting those permissions.
I was able to test if it worked by running cat /dev/kfd.  Before my permissions were correct, it gave "permission denied" or something like that.  After permissions were fixed, I see "cat: /dev/kfd: Invalid argument" and my ROCm install works.

As I try running cat /dev/kfd I get following message: cat: /dev/kfd: Cannot allocate memory
And if I try to add my user to the video permission group and reboot my PC I still get the same error message as above

I see.  I'm afraid I don't know what's going on for you in this case then; that is different than what I was getting.

 ROCm requires at least gfx8 (Hawaii is the only gfx7 GPU supported, gfx6-and-older aren't supported due to missing HW capabilities) . You can refer to https://rocm.docs.amd.com/en/latest/release/gpu_os_support.html for official ROCm GPU support, but you won't be able to use a Pitcairn card for KFD,


Pressensor data is not displayed/imported in full timeline

Describe the bug
Imported Pressensor CF .csv data only rendered partially, not in full timeline.
To Reproduce
Steps to reproduce the behavior:

Import the Pressensor data (KintamaniFIrstPull.csv)
See in the Visualizer data, it only displayed only first 10sec

Expected behavior
Full timeline of the shot displayed/uploaded. See attached example.

Screenshots

Sample data : click

Hey, thanks for providing a sample csv.
The problem is now fixed, but I have some problems deploying it. Will let you know once it's live!