Investigate why the BQ integration test didn't fail for quoted column name

Describe the bug
We caused #536 (fixed in #537) because of this change which was designed to avoid a similar issue in reverse from Snowflake (that it would have uppercased the column and failed to match in jinja, see #484.
Looking at the Circle logs for the job, it turns out that the table did error, but:

the subsequent dbt test invocation completed with exit code 0 (i.e. only the last step's outcome matters to Circle)
the dbt test invocation succeeded because even though the table failed to build, we don't generate unique schemata for each PR so it would have found an old copy of the table from a prior CI run.
Related: the fact that all PRs share a common schema also means that if two people push up commits at the same time, dbt will stop all over each other's tests and you get weird errors. This also happens if the same person commits back to back, but that's less of an issue IMO (I don't think we need a custom schema for every git commit for example).

Steps to reproduce

Cause a failure in an earlier stage of an invocation, that doesn't impact the final dbt test invocation (see here)

Expected results
CI to fail, because something didn't work
Actual results
No error because dbt test (the final step) still succeeds
Screenshots and log output
Linked above, but in case Circle has thrown away the logs by the time we get to this: utils-bq-logs.txt

This is an awesome investigation into possible solutions here - thank you @dbeatty10!!!
Feels like if we could get this working off of dbt build alone that would be a tremendous win. Two things to think through there on how we might mitigate the downside of it not working with insert-by-period.

In the future of utils  discussion, Joel wrote about moving the insert_by_period materialization into the experimental feature repo. If we were to go ahead and do that then we wouldn't have to worry about tests for insert by period.
You've probably already thought of this but would the insert-by-period tests work on a dbt build --full-refresh?

Those points aside, curious to hear which one you think would be best to move forward on.

I'm interested in pursuing command || exit 1 as our initial response and then queue dbt build, etc as follow-ups.
Rationale:

minimally invasive and straight-forward

only requires adding  || exit 1 suffix to 5 lines of code

solves the immediate problem

already tested it out in my local environment

moving us in the right direction and also completely reversible

it doesn't prevent us from pursuing the other ideas like dbt build, etc as the next logical steps to take

Beautiful - let's do it!


Update README.md

make it easier to find supported smart grammar

Anyone else need to review this?


Optimization and GPU porting of information flow implementation

Project info
Title:
Optimization and GPU porting of information flow implementation
Project lead and collaborators:
Etienne Combrisson & Ruggero Basanisi
Image of the project:

Registered Brainhack Global 2020 Event:
BrainHack Marseille
Project Description:
Frites is a recent pure Python package (https://github.com/brainets/frites) to analyse neurophysiological data within the Information Theoretical framework and to perform group-level statistics on information-based measures. The aim of the software is to extract brain networks that are modulated according to the task (model-based and model free analysis). To this end, Frites contains several CPU-based functions to estimate the directed information flow between brain areas. While those methods estimate the directed connectivity in a reasonable amount of time on small networks, the complexity of larger networks are too demanding for the current CPU implementation. Therefore, the ultimate goal of this project would be to have both a CPU and a GPU implementations of our recent multivariate information flow measure.
Data to use:
No data are needed, Frites includes functions to generate simulated data.
Link to project repository/sources:
GitHub: https://github.com/brainets/frites
Goals for Brainhack Global 2020:
The following points are going to be addressed in this project:

Code a GPU implementation of the conditional mutual-information
Include a switch for the user to specify if a CPU or a GPU implementations are going to be used when computing the univariate information flow
GPU porting of the multivariate information flow measure (which is also going to use the GPU version of scikit-learn)

Skills:
A good knowledge of python is needed. We will mostly use basic libraries used in computer science, especially numpy. No needing about specific knowledge of GPU programming.
Tools/Software/Methods to Use:
Python, Jupyter, GitHub, and Nextjournal or Colab.
Project labels

Type of project:
coding_methods, data_management, documentation, #method_development,
pipeline_development, tutorial_recording, visualization

Project development status:
0_concept_no_content, 1_basic structure, #2_releases_existing

Topic of the projet:
Bayesian_approaches, #causality, connectome, data_visualisation, deep_learning,
diffusion, diversity_inclusivity_equality, EEG_EventRelatedResponseModelling,
EEG_source_modelling, Granger_causality, hypothesis_testing, ICA, #information_theory,
machine_learning, MR_methodologies, neural_decoding, neural_encoding, neural_networks,
PCA, #physiology, reinforcement_learning, reproducible_scientific_methods, single_neuron_models,
statistical_modelling, systems_neuroscience, tractography, #connectivity

Tools used in the project:
AFNI, ANTs, BIDS, Brainstorm, CPAC, Datalad, DIPY, FieldTrip, fMRIPrep, Freesurfer,
FSL, #Jupyter, #MNE, MRtrix, Nipype, NWB, SPM

Tools skill level required to enter the project (more than one possible):
comfortable, #expert, #familiar, no_skills_required

Programming language used in the project:
no_programming_involved, C++, containerization, documentation, Java, Julia, Matlab,
#Python, R, shell_scripting, Unix_command_line, Web, workflows

Modalities involved in the project (if any):
behavioral, DWI, ECG, ECOG, EEG, eye_tracking, fMRI, fNIRS, MEG, MRI, PET, TDCS, TMS

Git skills reuired to enter the project (more than one possible):
0_no_git_skills, #1_commit_push, #2_branches_PRs, 3_continuous_integration

[x] I added all of the labels I want an associate to my project

Project Submission
Submission checklist
Once the issue is submitted, please check items in this list as you add under ‘Additional project info’

[x] Link to your project: could be a code repository, a shared document, etc.
[x] Goals for Brainhack Global 2020: describe what you want to achieve during this brainhack.
[ ] Flesh out at least 2 “good first issues”: those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document.
[x] Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill. Use the issue labels for this purpose.
[ ] Chat channel: A link to a chat channel that will be used during the Brainhack Global 2020 event. This can be an existing channel or a new one. We recommend using the Brainhack space on Mattermost.

Optionally, you can also include information about:

[ ] Number of participants required.
[ ] Twitter-sized summary of your project pitch.
[x] Provide an image of your project for the Brainhack Global 2020 website.

We would like to think about how you will credit and onboard new members to your project. If you’d like to share your thoughts with future project participants, you can include information about:

[ ] Specify how you will acknowledge contributions (e.g. listing members on a contributing page).
[ ] Provide links to onboarding documents if you have some:

Dear @StanSStanman Thank you very much for your project submission and welcome to the Brainhack Global 2020 🎉 I see that you didn't include good first 2 issues to your description. I will merge your project to the website but we always recommend to have those issues listed to guide the participants better on deciding how they can contribute to your project. Please do no hesitate to add when you have time.
Hope you enjoy your participation in Brainhack Global 2020 🚀 🧠

Hi @complexbrains, here's the missing section (or maybe you prefer that we edit the text from @StanSStanman ?) :
Good first issues:

Translate the core functions to be executed on GPU devices
Benchmark those functions against CPU implementations and decide whether it's better in the futur to have two implementations (CPU / GPU) or to have system agnostic functions

Let me know if it's ok for you !

Perfect! Let's add those too! Thank you :hugs:


Howto - installation method similar to setup.py?

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
python3 setup.py install --root=/some/dir/

Description
Would like to package up fastapi by using an installation similar to python3 setup.py install --root=$PKG
fastapi does not provide a setup.py. As a packager/admin, I do not plan to use pip for the installation - rather I plan to create a package and push it out to a number of servers.
Documentation does not describe any method other than pip. I don't use pip to install most things, I package up every python item individually.
Operating System
Linux
Operating System Details
Slackware
FastAPI Version
0.73.0
Python Version
Python 3.9.10
Additional Context
No response

For now I'm exploding (aka unzipping) the wheel from https://pypi.org/project/fastapi/#files and copying into the pkg manually.

Fastapi appears to use flit for building/publishing
It appears flit can produce a setup.py if that is what you want - https://flit.readthedocs.io/en/latest/cmdline.html#flit-build


I'm getting the lowest TF ever while using Osiris.

I've heard about radarhack being detected and also glow which give red trust for both of them? Should i stop using these features even while being on linux?
Thank you.
Oh and before you ask, i don't use aimbot, i don't use anything "obvious", just small backtrack and radarhack.

radarhack, glow, chams, are detected for 6 months

radarhack, glow, chams are detected for 6 months. ur acc may be banned in a while so (:

This is a public source, what did you expect? It has been sigged since ages. And even if not sigged, its not supposed to be updated to stay undetected. You'll have to work on this by yourself, there is many methods.
If the untrusted thingy happens no matter what, it might just be the way the .dll acts. Like those vmthooks waves.
Radarhack/glow/chams are visual, vacnet can't detect them, OW can at some extent, however, nothing is detected as long as you use it properly. Not even wallhacks and such.
Only exploits and so, as well as antiaims can bring on untrusted straight (as well as a high FOV with 0 smooth enabled) but that would be ragehacking so OW again.
If faceit can be cheated on with ESPs, its not VAC that would be able to figure them out. Unless you play on some rootkit anticheats where you DO have to take off anything that is visual cause they take screenshots during games.
So no.

Someone I know plays with Iniuria which has Glow ESP and Radar Hack + ESP Draw on Windows and no red trust factor and no bans. He has level 30+ on Steam.
Osiris must upgrade the spoofing/ hooking to get undetected again.

radarhack, glow, chams are detected for 6 months. ur acc may be banned in a while so (:

7 or + out of 10 games I play, I play vs cheater(s) in Prime. Sometimes when the enemy team has only 1 cheater he goes 39-19 score and never gets banned. They always have wallhacks and sometimes aim and even trigger. If I check the demo of the match, he really looks like having an internal cheat like Osiris, I don't think you can go 39-19 with externals (which just read memory from csgo.exe).

Someone I know plays with Iniuria which has Glow ESP, Skin or Inventory Changer and Radar Hack (not sure if original Radar or a further radar window) + ESP Draw on Windows and no red trust factor and no bans. He has level 30+ on Steam. Osiris must upgrade the spoofing/ hooking to get undetected again. @danielkrupinski

There is no such thing as spoofing however I checked yesterday, it does use vmt hooks, which are known to be detected. Remove them, change them, if you can code, that may be sorted out. Use an alternative or just get rid off it.
And externals not only usually just reads memory, but they only read memory. It doesn't change a thing, an external can still get detected, also, once again, visuals are not meant to be detected. The way you code it however, that's something else.
 Also looking like having an internal or external cannot be told by a demo unless the guy starts spinning and using exploits lmao. What reading and not writing means is, it doesn't inject into the game and therefore only works through the information that the game itself gives, internals on the other side, they do that but they also write in order to change stuffs inside the game itself (like anti aiming and such)
There are however few externals that do write into the game in a subtle manner for functions like backtracking, but that's not my point, both are the same detection rate. And osiris is internal anyway, also, external doesn't mean weaker (hexui is a good example of what you can achieve going full external).
Playing against cheaters, that's the most common thing it has to happen. If you're not happy, go with a paid cheat and try to mm hvh or at least, closet hard enough to not get banned but still win more. Turkish people have plagued the game with closet/ragehacking since years. Literally everytime you'll see a turkish name, you can be sure he ain't legit at 90%. (no racism, just a fact, been up to GE since years and those were the guys that cheated the most, nearly 100% rate)
What you can do if you really want osiris (which is semi-broken like, barely htiting) is fixing the VMT hooks and "spoofing" as you say, aka trying to mutate the signature of the output dll. There are many ways to do that, but, keep in mind, even if a small part of the cheat is sigged, like let's say, the bunnyhop, and that you did not entirely mute it, the bhop will be sufficient. They do not need a full signature, only a portion off it is sufficient, there are tools to compare the signatures, if you really want to go that way I could help.
I've no invite to give for novo sadly and its pricey, but I saw airflow doing good, 5$. I suggest you to pay and not play on your main no matter what, lately, most cheats have been targetted by unknown untrusted detections (worse than vmts) and I can easily tell you ain't a specialist of cheating neither you are a dev/coder, so working on osiris may work just like it may take your time and waste it.
And by, it may work, it'll take your time heavily to understand it and try to "unsig" it enough so you can go with it, but even once done, the cheat will be above average unless you're only looking for legitbot.


Fix link to pms-spec.yaml

Fixes the link in the README from blob/main/pms-spec.yaml to blob/main/src/pms-spec.yaml

Summary by CodeRabbit

Documentation

Updated the path to the main OpenAPI Specification file for clarity.
Rephrased the introduction to the main specification file for improved readability.

@Niggggggo Thanks!


[md mode] bad highlighting with fencedCodeBlocks: true

    fencedCodeBlocks: true,

paste in the following:

```shell
```

*   foo

    *   bar

expected: the bullets are highlighted like bullets (or just text)
actual: the bullets are highlighted like code
compare to how it works in http://spec.commonmark.org/dingus/ for example

Could it be that this was already fixed by 7580a1dc1d7ce1ab? I can reproduce in 5.24.2, but not in master.

Yep, I believe we're good now.


[9.4] ISPN-10220 Create named lambdas to identify which test is running

Backport https://github.com/infinispan/infinispan/pull/6950

Integrated, thanks Diego!


Make the backlayer webview span the full width of the notebook editor

Fixes #117489
With the new markdown renders, we are relying more on the back layer webview. This means that we need to do things like make sure the entire markdown cell inside the webview is draggable.
Currently this is not possible since the webview has a large left margin. This change makes the webview span the entire notebook editor and instead moves the left margin into the individual norebook cells

Merging this for more testing. The main area where this may cause regressions is the output renderers. I think they are working ok, but please let me know if you notice any regressions


investigate predict protein

This tool uses protein embeddings.
Referred to in https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9374478/pdf/baac062.pdf
https://predictprotein.org/about
https://predictprotein.org/
We should evaluate this at some point

This tool predicts quite a lot of features, so I'm not really sure how to evaluate it.
We should probably discuss about the use we would make of it as well.


Use a separate SPECTATOR to listen external view change.

Fix the issue that broker keep processing external view changes and block other listeners.

Codecov Report

Merging #1077 into master will decrease coverage by -0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1077      +/-   ##
==========================================
- Coverage      67%   66.94%   -0.06%
==========================================
  Files         748      748
  Lines       35592    35594       +2
  Branches     4527     4527
==========================================
- Hits        23848    23828      -20
- Misses      10167    10184      +17
- Partials     1577     1582       +5

Impacted Files
Coverage Δ

.../pinot/broker/broker/helix/HelixBrokerStarter.java
70% <100%> (+0.68%)
:white_check_mark:

...m/linkedin/pinot/common/utils/FileUploadUtils.java
47.79% <ø> (-5.15%)
:x:

...altime/impl/dictionary/FloatMutableDictionary.java
58.46% <ø> (-4.62%)
:x:

...mon/utils/retry/ExponentialBackoffRetryPolicy.java
81.81% <ø> (-4.55%)
:x:

...edin/pinot/common/metadata/ZKMetadataProvider.java
69.6% <ø> (-3.93%)
:x:

...manager/realtime/HLRealtimeSegmentDataManager.java
73.33% <ø> (-3.89%)
:x:

...lix/core/realtime/PinotRealtimeSegmentManager.java
75.14% <ø> (-3.47%)
:x:

...m/linkedin/pinot/common/metrics/MetricsHelper.java
72.6% <ø> (-2.74%)
:x:

.../server/starter/helix/SegmentFetcherAndLoader.java
62.22% <ø> (-1.49%)
:x:

.../pinot/core/realtime/impl/RealtimeSegmentImpl.java
70.39% <ø> (-0.33%)
:x:

... and 6 more

Continue to review full report at Codecov.

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


No error log entries for repo 404

Don't have error-level log entries when a non-existent repo is accessed. IMO, this unnecessarily clutters the logs.

Does 404 request is logged somewhere anyway?

@lafriks What do you mean?

Does these 404 requests are still logged in serv.lg/http.log

@lafriks No, but nor are other types of 404 (e.g. non-existent user)

LGTM

LGTM


🐛 Bug Report: Backstage with Dynatrace doesn't work

📜 Description
Adding the Dynatrace Plugin doesn't work and the information in the portal is not clear.
👍 Expected behavior
Problems from the Dynatrace Aplication
👎 Actual Behavior with Screenshots
Return Error 401 or 404
👟 Reproduction steps
https://github.com/backstage/backstage/tree/master/plugins/dynatrace
That document refers all the procedure but doesn't work.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
Development
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Is importan to put both words, to solve this issue Authorization: 'Api-Token ${DYNATRACE_ACCESS_TOKEN}'


Add simple GUI

ModestPy was aimed to serve as a supplementary package for more advanced applications (e.g. Model Predictive Control). However, some users might be interested in using it for offline parameter estimation of standalone models. A simple GUI would be helpful in such cases.

Do not have time for this...


npm run dev fails

Found an issue or bug? Tell me all about!
Describe the issue / bug.
npm run dev fails on fresh install. webpack-dev-server args aren't working.
(Note - I also tried forcing webpack-dev-server == 2.2.0 and also tried removing the --hot option, but then the next arg failed.)
How can I reproduce this problem?
fresh install
vue init simulatedgreg/electron-vue electronvue
If visual, provide a screenshot.
Output with export npm_config_loglevel=verbose
.-(~/dev/tmp/electronvue)-------------------------------------------------------------------------------------------------------------------------------------(rrosen@RossMacbook)-
`--> npm run dev                                                                                [py3]
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb run-script [ 'predev', 'dev', 'postdev' ]
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>dev /Users/rrosen/dev/tmp/electronvue
> node tasks/runner.js

Starting webpack-dev-server...

webpack  fallbackLoader option has been deprecated - replace with "fallback"

webpack  loader option has been deprecated - replace with "use"

webpack  Project is running at http://localhost:9080/

webpack  webpack output is served from /
         Content not from webpack is served from /Users/rrosen/dev/tmp/electronvue/app/dist

webpack

webpack  error: unknown option `--hot'

npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/rrosen/dev/tmp/electronvue/node_modules/.bin:/Users/rrosen/.rvm/gems/ruby-2.1.5/bin:/Users/rrosen/.rvm/gems/ruby-2.1.5@global/bin:/Users/rrosen/.rvm/rubies/ruby-2.1.5/bin:/usr/local/Cellar/pyenv-virtualenv/1.0.0/shims:/Users/rrosen/.pyenv/shims:/Users/rrosen/.pyenv/bin:/Users/rrosen/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/git/bin:/Users/rrosen/.rvm/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /Users/rrosen/dev/tmp/electronvue
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm verb exit [ 0, true ]
npm info ok

Tell me about your development environment.

Node version: 6.9.2
NPM version: 4.0.5
vue-cli version: (if necessary) 2.8.1
Operating System: OSX 10.12.3

@rr326
Sorry for the trouble you are having, but I unfortunately can't reproduce this issue. I've tried multiple node versions and npm versions, including the specifics you provided, and have had no issues. I'm wondering if webpack-dev-server made a release recently that broke with the --hot flag, but has since removed that release. This might be worth investigating on webpack-dev-server's side as this isn't a direct issue with electron-vue.
Currently working with...

<EMAIL_ADDRESS><EMAIL_ADDRESS>macOS 10.12.3

npm ls webpack-dev-server webpack

<EMAIL_ADDRESS>~
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Same here when i do a fresh installation the command npm run dev fails and i get the following error
`Starting webpack-dev-server...
webpack  fallbackLoader option has been deprecated - replace with "fallback"
webpack  loader option has been deprecated - replace with "use"
webpack  Project is running at http://localhost:9080/
webpack output is served from /
webpack  Content not from webpack is served from /home/itachi/Desktop/dev/git/nour/app/dist
webpack  Hash: c66bb46691883ed94c06
Version: webpack 2.2.1
Time: 15109ms
Asset       Size  Chunks                    Chunk Names
imgs/logo.png    61.9 kB          [emitted]
renderer.js    1.15 MB       0  [emitted]  [big]  renderer
index.html  493 bytes          [emitted]
chunk    {0} renderer.js (renderer) 384 kB [entry] [rendered]
[65] (webpack)/hot/emitter.js 77 bytes {0} [built]
[73] ./app/src/renderer/main.js 503 bytes {0} [built]
[74] (webpack)-dev-server/client?http://localhost:9080 4.9 kB {0} [built]
[75] (webpack)/hot/dev-server.js 1.57 kB {0} [built]
[79] ./app/src/renderer/routes.js 143 bytes {0} [built]
[84] ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./app/src/renderer/App.vue 77 bytes {0} [built]
[91] ./~/babel-runtime/helpers/extends.js 544 bytes {0} [built]
[132] ./~/sockjs-client/lib/entry.js 244 bytes {0} [built]
[158] ./~/strip-ansi/index.js 161 bytes {0} [built]
[161] ./app/src/renderer/App.vue 1.53 kB {0} [built]
[171] ./~/vue-loader/~/vue-style-loader!./~/css-loader?sourceMap!./~/vue-loader/lib/style-rewriter.js?id=data-v-017a3761!./~/vue-loader/lib/selector.js?type=styles&index=0!./app/src/renderer/App.vue 1.46 kB {0} [built]
[176] (webpack)-dev-server/client/overlay.js 3.59 kB {0} [built]
[177] (webpack)-dev-server/client/socket.js 856 bytes {0} [built]
[180] (webpack)/hot/log-apply-result.js 1.02 kB {0} [built]
[202] multi (webpack)-dev-server/client?http://localhost:9080 webpack/hot/dev-server ./app/src/renderer/main.js 52 bytes {0} [built]
+ 188 hidden modules
Child html-webpack-plugin for "index.html":
chunk    {0} index.html 541 kB [entry] [rendered]
[0] ./~/lodash/lodash.js 540 kB {0} [built]
[1] (webpack)/buildin/module.js 517 bytes {0} [built]
[2] ./~/html-webpack-plugin/lib/loader.js!./app/index.ejs 1.02 kB {0} [built]
webpack  webpack: Compiled successfully.
Starting electron...
electron  /home/itachi/Desktop/dev/git/nour/node_modules/electron/index.js:9
throw new Error('Electron failed to install correctly, please delete node_modules/' + path.basename(__dirname) + ' and try installing again')
^
      Error: Electron failed to install correctly, please delete node_modules/electron and try installing again
          at Object.<anonymous> (/home/itachi/Desktop/dev/git/nour/node_modules/electron/index.js:9:9)
          at Module._compile (module.js:571:32)
          at Object.Module._extensions..js (module.js:580:10)
          at Module.load (module.js:488:32)
          at tryModuleLoad (module.js:447:12)
          at Function.Module._load (module.js:439:3)
          at Module.require (module.js:498:17)
          at require (internal/module.js:20:19)
          at Object.<anonymous> (/home/itachi/Desktop/dev/git/nour/node_modules/electron/cli.js:3:16)
          at Module._compile (module.js:571:32)

`
I fixed this issue by reinstalling manually...
node: 7.4.0
npm: 4.0.5
vue: 2.8.1
Ubuntu 16.10 64bit

@gimyboya
Your issue is specific to electron trying to run its postinstall to download. As the logs suggests...
Error: Electron failed to install correctly, please delete node_modules/electron and try installing again

have you tried doing so?

As i mentioned i have fixed this error by reinstalling electron again manually i didn't delete anything i just reinstalled electron alone inside my project folder

I tried reinstalling electron and it didn't work. Any ideas what to try next?
rm -rf node_modules/electron
npm install electron
npm run dev
...
webpack  error: unknown option `--hot'

@gimyboya
How did you get the logging? That might help me debug on my end.

@rr326 I don't think that will help you, as your issue is a completely different one from @gimyboya.
It's a weird issue though.

@rr326 in my case i didn't remove electron i just override it with a new installation... you may try again by initializing a new project and overriding electron if you get the same problem

@AkiraLaine
Correct - that did not change anything
@SimulatedGREG
Another clue:
If I add a truly bogus argument to the webpack-dev-server run statement in runner.js I get a different outcome:
runner.js (end)
let command_line = `webpack-dev-server --bogus --hot --colors --config webpack.renderer.config.js --port ${config.port} --content-base app/dist`
console.log('Command: ', command_line)
run(command_line, YELLOW, 'webpack')

Usage: https://webpack.js.org/configuration/dev-server/

         Config options:
... (Big usage help screen)
webpack  Unknown argument: bogus

Then if I start removing args, they all fail (not just --hot).
It's almost like some subsidiary command is getting the command line and expects the previous args to have been popped out.
Command:  webpack-dev-server --hot --colors --config webpack.renderer.config.js --port 9080 --content-base app/dist
webpack  error: unknown option `--hot'

Command:  webpack-dev-server  --colors --config webpack.renderer.config.js --port 9080 --content-base app/dist
webpack  error: unknown option `--colors'

Command:  webpack-dev-server  --content-base app/dist --config webpack.renderer.config.js --port 9080
webpack  error: unknown option `--content-base'

Any ideas how I can debug? I've acked through the entire directory looking for "unknown option" and modified every error / console call with a line number(so I could then trace from there), but I can't find it.  Maybe that is coming from a globally install module or node itself.

@SimulatedGREG
Here's another clue.  I decided to try to build the project.
I get another "unknown option" error.  (This is in a fresh install, and latest Node, npm, webpack)
.-(~/dev/tmp/ev2)---------------------------------------------------------------------------------------------------------------------------------------------(rrosen@RossMacbook)-
`--> node --version                                                                                [py3]
v6.9.5
.-(~/dev/tmp/ev2)---------------------------------------------------------------------------------------------------------------------------------------------(rrosen@RossMacbook)-
`--> npm --version                                                                                [py3]
4.2.0
.-(~/dev/tmp/ev2)---------------------------------------------------------------------------------------------------------------------------------------------(rrosen@RossMacbook)-
`--> npm ls webpack webpack-dev-server                                                                                [py3]
<EMAIL_ADDRESS>/Users/rrosen/dev/tmp/ev2
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
-(~/dev/tmp/ev2)---------------------------------------------------------------------------------------------------------------------------------------------(rrosen@RossMacbook)-
`--> npm run build                                                                                [py3]

><EMAIL_ADDRESS>build /Users/rrosen/dev/tmp/ev2
> npm run pack && build

><EMAIL_ADDRESS>pack /Users/rrosen/dev/tmp/ev2
> npm run pack:main && npm run pack:renderer

><EMAIL_ADDRESS>pack:main /Users/rrosen/dev/tmp/ev2
> cross-env NODE_ENV=production webpack -p --progress --colors --config webpack.main.config.js

Hash: f887bb40c90e6f3d9373
Version: webpack 2.2.1
Time: 927ms
  Asset       Size  Chunks             Chunk Names
main.js  931 bytes       0  [emitted]  main
   [1] ./app/src/main/index.js 745 bytes {0} [built]
    + 1 hidden modules

><EMAIL_ADDRESS>pack:renderer /Users/rrosen/dev/tmp/ev2
> cross-env NODE_ENV=production webpack -p --progress --colors --config webpack.renderer.config.js

fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
 10% building modules 6/8 modules 2 active .../dev/tmp/ev2/app/src/renderer/App.vue
  error: unknown option `-p'

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "pack:renderer"
npm ERR! node v6.9.5
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>pack:renderer: `cross-env NODE_ENV=production webpack -p --progress --colors --config webpack.renderer.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>pack:renderer script 'cross-env NODE_ENV=production webpack -p --progress --colors --config webpack.renderer.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ev2 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production webpack -p --progress --colors --config webpack.renderer.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ev2
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ev2
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rrosen/.npm/_logs/2017-02-13T13_58_34_595Z-debug.log

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>pack script 'npm run pack:main && npm run pack:renderer'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ev2 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run pack:main && npm run pack:renderer
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ev2
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ev2
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rrosen/.npm/_logs/2017-02-13T13_58_34_684Z-debug.log

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.9.5
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `npm run pack && build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'npm run pack && build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ev2 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run pack && build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ev2
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ev2
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rrosen/.npm/_logs/2017-02-13T13_58_34_740Z-debug.log

My bad.
 I had NODE_PATH set in my .zshrc - probably from several years ago when I just started out. I removed that and it all worked.

That sure sounds like a horrible experience. Glad you got everything sorted out!

BTW - I've been using the template. Really great. Thanks so much.


Automatically rescan thumbnail after rotating photo(s)

Is your feature request related to a problem? Please describe.
After rotating a photo, the thumbnail will be stale and the thus have the wrong orientation.
Describe the solution you'd like
Add a auto rescan of the thumbnail photo after the rotation is complete.
Describe alternatives you've considered
I don't think there are any good alternatives.

If i understand correctly, this should already be the case (and it works for me). Could you please provide a video capture of what you're doing? Also please provide a sample image which thumbnail doesn't get refreshed.

Ok I just confirmed this quickly and it is still valid.
If you can't confirm I'll try and send a video but will take a bit more
time.
When looking at a single photo, rotate the photo. Now go back to thumbnail
view and it has the wrong orientation.
On Thu, 11 Jan 2024, 6:19 pm Thibault Deckers, @.***>
wrote:

If i understand correctly, this should already be the case (and it works
for me). Could you please provide a video capture of what you're doing?
Also please provide a sample image which thumbnail doesn't get refreshed.
—
Reply to this email directly, view it on GitHub
https://github.com/deckerst/aves/issues/869#issuecomment-1886595942, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVNKTEJJAWK2CWJHQ3SYCFLYN6OANAVCNFSM6AAAAABBVZZBXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWGU4TKOJUGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, still works for me. Thumbnail is refreshed everywhere.

I must have been having a moment as I went to record a video and couldn't
reproduce :( Sorry for wasting your time.
On Thu, 11 Jan 2024, 11:24 pm Thibault Deckers, @.***>
wrote:

Yes, still works for me. Thumbnail is refreshed everywhere.
—
Reply to this email directly, view it on GitHub
https://github.com/deckerst/aves/issues/869#issuecomment-1887157412, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVNKTENMJZOZ344PCUS7LUTYN7RZ7AVCNFSM6AAAAABBVZZBXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXGE2TONBRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

No worries! Maybe there was a random bug.


Announcement: big_vision is transitioning from jax.pmap to jax.jit.

In the coming 1-2 weeks big_vision is expected to transition from pmap-based parallelism to jit-parallelism. This will enable more flexible parallelisation strategies, including, but not limited to, ZERO* and fully-sharded data-parallel (aka fsdp) training.
This transition may temporarily break project-specific code (or we will just remove such code). If you want to read/run the old code, please see the table at the end of the README for the project-specific commits to sync to.

Transition is done


[Continuous Backup] Implement S3 writer

Implemented draft in https://github.com/ydb-platform/ydb/pull/3152


run build complete handler sync

motivation: when build-complete handler is run async it may never get done siunce the process may exit
changes: run the complete handler sync

@swift-ci please smoke test


Feature/#4 readmeにusageを追加する

Codecov Report

Merging #10 into develop will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #10   +/-   ##
========================================
  Coverage    94.72%   94.72%
========================================
  Files           27       27
  Lines          777      777
========================================
  Hits           736      736
  Misses          41       41

Continue to review full report at Codecov.

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


The User Stories in Beginner Project Dynamic CSS Variables doesn't seem to match the Example Project

Describe the bug

https://github.com/florinpop17/app-ideas/blob/master/Projects/1-Beginner/Dynamic-CSSVar-app.md

The User Stories in Beginner Project Dynamic CSS Variables doesn't seem to match the Example Project.

The user stories to describe a user login experience whereas the example project shows in-app controls to manipulate a box.

Expected behavior

Believe the User Stories are incorrect for the purpose of dynamic CSS variable manipulation for this project.

The example projects might not be 100% accurate. Feel free to create one that is 😊


Guilds and clans icons

Is your feature request related to a problem? If yes, please describe it.
When we're on the Positions page every position related to an area has an image of this area. It negatively affects user experience as area images need to be cut to fit a circular image.
Describe the solution you'd like
Every area should have a distinctive icon that will be used on the Positions page.

Change of mind. We will use tags to specify that position is related to a particular guild/clan


fix: minor formatting updates to glossary

describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

Thanks!


Add fuzz target checker/fuzz/check_project_naive

This PR adds a new fuzz target testing the checker repo. It's not all that helpful at the moment, since it's just detecting todo!() blocks in the code, but it can be useful in the future.
This also sets up the fuzzing_parser and fuzzing_checker CI jobs to replace the fuzzing CI job
/cc @addisoncrump
Fixes https://github.com/kaleidawave/ezno/issues/153

Awesome!
Yeah doing a quick rg, there are ~200 todo! macros (some of those might be behind old commented out code though) in checking APIs. And there are 50 todo!s under the synthesis directory which should all have access to positions and checking_data so should be calling checking_data.raise_unimpement_error instead rather than crashing.
Is there a reason for using naive data, rather than structured?
Also didn't I ask about doing fuzzing for checking last year and heard it wasn't possible?
Also as the fuzzing tests don't run on windows (right?) and the current setup is exit on first error is there a way to do print failed exceptions as it would make fixing them a lot easier. In the current CI setup I have option thing SHORT_CIRCUIT with a modified command recommended by @addisoncrump . But if I remember correctly @addisoncrump a few months ago said it then doesn't run the fuzzing in parallel (and thus covers less cases)? Is there a way to run the most cases while not short-circuiting as I can't run them locally and so rely on back and forth with CI?

Maybe I can shine some light on a few of these points.

Also didn't I ask about doing [mutation-based] fuzzing for checking last year and heard it wasn't possible?

It is possible, but it's not necessarily going to find bugs with complicated pre-conditions. Mutation-based fuzzing works by exploring the program; it mutates a input, and if it sees new coverage, it keeps that input, otherwise discarding. Suppose you have a bug caused by a single block; this strategy finds bugs for which a crash/incorrectness/branch is induced unconditionally (e.g. it just doesn't work) or conditionally on only the last few blocks. As more of the program's state is encoded into bugs/branches which determine whether these blocks get executed, fuzzing becomes less useful without significantly better mutations. This is because you actually want to explore lots of different program states which are less related to the coverage when your targets are more complex.
Concretely, parsers are very good mutation-based fuzz targets because they typically don't encode a lot of state. Typically, each block refers to one particular action (e.g. transforming some tokens to a structure) and that action doesn't have a whole lot of conditions or state attached to it (just the immediate scope).
By comparison, a ton of information is encoded in the state at any given moment in type checkers/compilers, and is used to determine branches and may affect whether a bug is triggered. For this reason, this fuzzer will likely not find deeper bugs in the type checker. Fuzzing compilers is possible, but generally people use generative fuzzers that produce large complex (and generally near-correct!) programs that encode a lot of state, not mutation-based fuzzers like this one. This will find bugs, but it likely won't find so-called "deep bugs".
TL;DR: if you want to find really complicated bugs, you're gonna need a far more specialized fuzzer than naïve or even structured mutation-based fuzzers.

then doesn't run the fuzzing in parallel (and thus covers less cases)? Is there a way to run the most cases while not short-circuiting as I can't run them locally and so rely on back and forth with CI?

It does run in parallel, it just stops all parallel processes at the same time. If you don't want to short-circuit, you can set a max_runs or max_total_time flag to stop it at a given time and put ignore_crashes, ignore_timeouts, ignore_ooms; cargo-fuzz will dump all the crashes after, but they won't be deduplicated by cause (because this is sadly infeasible) and you would need to re-run them to see their stacktraces.

And there are 50 todo!s under the synthesis directory which should all have access to positions and checking_data so should be calling checking_data.raise_unimpement_error instead rather than crashing.

Does this mean that it is in fact finding an issue then? In that I would be able to catch those as ignorable errors for the time being, but right now they panic when they shouldn't?

Yep the unimplement method raises a standard warning (which is better than the program crashing). I don't think I added it in all the places though. Should fix that!
Thanks @addisoncrump! Will act on them later

Hey, sorry have been busy so haven't had a chance to look at it.
Will merge but only after #157 has been merged which clears up obvious todo!s
Also looking at CI times, is the fuzzing build using the cache? It might be just because it is a release build and more dependencies or something but it is taking 90 seconds to build whereas other tasks take 30-45 seconds? Maybe because it is not in the workspace or something (because we don't want it to always be built in development). Not sure?

For fuzzing, the fuzz crates are their own workspace, since there's some weird linking and LLVM flags set. So I don't think it caches?

Now #157 is merged, this additional fuzzing should produce actual errors.
The fuzzing doesn't seem to be compiling though, with an error error[E0463]: can't find crate for core`? Might be because of the recent Rust update.
Once that is fixed then will merge (even if it finds errors as would be useful to have those being highlighted now)

Yeah, that CI error is this again: https://github.com/rust-fuzz/cargo-fuzz/issues/355
Avoid binstall in CI for cargo-fuzz :sweat_smile:

The workflow is running okay so merging now.

Currently is finding an error with the partial syntax system in the parser
thread 'AST parsing' panicked at /home/runner/work/ezno/ezno/parser/src/lib.rs:320:27:
more than 256 markers: TryFromIntError(())
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Might be cyclic recursion or something.
(current parser fuzzing test well formed syntax, so might have not picked it up. Partial syntax wasn't a thing when they were written)

So it begins :grinning:


[Bug] Cursor does not appear on input boxes when sign-in details are picked from saved credentials

Description
When user selects login details from credentials saved on browser and wants to edit details, cursor does not appear at the location where user clicks for input.
Steps to reproduce the behaviour:

Go to appsmith.com login and select from saved credentials on the browser
Click on either email or password expecting for a cursor to appear to indicate where the changes needs to be made - but no cursor appears though user can edit text. During the edit the cursor does however appear.

Important Details

Version: Cloud
OS: Win10
Browser: Chrome
Environment: Production

Hello , I understand the issue. Demo video cleared it all . I would like to take up this issue !

@Yash-Bhange go for it!

thanks , I will start working on it right away !

Hey, I solved the issue !

@Yash-Bhange awesome! Could you link to the issue in the PR? We'll test it and merge it in

@Yash-Bhange awesome! Could you link to the issue in the PR? We'll test it and merge it in

Done ! please check

@Nikhil-Nandagopal  This was my first ever open source contribution. Thanks for the opportunity. The PR is ready to be approved and merged ! Please check


Version 5 release notes

To be added here

New features
New link helpers
The following helpers: #govuk_link_to, #govuk_button_link_to, #govuk_button_to and #govuk_mail_to, plus the class helpers #govuk_link_classes and #govuk_button_classes have been rewritten to use keyword arguments instead of trying to juggle the arguments based on what's passed in, like the old Rails-style ones.
This is a breaking change because the new implementations don't support all the features the Rails ones do,
mainly that govuk_link_to("Peanuts", controller: "snacks", action: "show", id: "peanuts") style invocation won't work. The Rails documentation has advised against using this form of link for many years - pass in the path instead, i.e.,govuk_link_to("Peanuts", snack_path("peanuts"))
The new helpers allow us to easily add extra GOV.UK specific arguments, these include:

new_tab: true - open the page in a new tab, adds rel="noreferrer noopener" and target="_blank" automatically to links #419
visually_hidden_prefix and visually_hidden_suffix - add .govuk-visually-hidden text before or after the link text #465

Another upgrade step for the release notes:
7. Update asset pipeline
If you use Rails’s asset pipeline to import the images and fonts from govuk-frontend, you’ll need to add the dist folder to the path.
Within config/initalizers/assets.rb, change this:
Rails.application.config.assets.paths << Rails.root.join("node_modules/govuk-frontend/govuk/assets/images")
Rails.application.config.assets.paths << Rails.root.join("node_modules/govuk-frontend/govuk/assets/fonts")

to this:
Rails.application.config.assets.paths << Rails.root.join("node_modules/govuk-frontend/dist/govuk/assets/images")
Rails.application.config.assets.paths << Rails.root.join("node_modules/govuk-frontend/dist/gov/assets/fonts")

If you use sprockets to compile javascript or CSS, update the path in the manifest.
Within app/assets/config/manifest.js, change this:
//= link_directory ../../../node_modules/govuk-frontend/govuk/assets/images
//= link_directory ../../../node_modules/govuk-frontend/govuk/assets/fonts

to this:
//= link_directory ../../../node_modules/govuk-frontend/dist/govuk/assets/images
//= link_directory ../../../node_modules/govuk-frontend/dist/govuk/assets/fonts

8.

Another step:
8. Update favicon references in your application layout file
The included icons within govuk-frontend have been updated, with some of the old ones removed.


[WIP] Make UdbBypassSpec part of UdbConfiguration

Move UdbBypassSpec to UdbConfiguration, and get rid of the second argument of UnderDatabase.getTable.

Codecov Report

Merging #13672 (cb938b1) into master (bfd55f5) will decrease coverage by 17.04%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #13672       +/-   ##
=============================================
- Coverage     34.58%   17.54%   -17.05%
+ Complexity     6939     2666     -4273
=============================================
  Files          1382     1384        +2
  Lines         80213    80332      +119
  Branches       9748     9777       +29
=============================================
- Hits          27744    14092    -13652
- Misses        50085    64997    +14912
+ Partials       2384     1243     -1141

Impacted Files
Coverage Δ

...n/java/alluxio/table/common/udb/UdbBypassSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/alluxio/table/common/udb/UdbConfiguration.java
0.00% <0.00%> (-97.06%)
:arrow_down:

...ava/alluxio/master/table/CatalogConfiguration.java
0.00% <0.00%> (ø)

...r/src/main/java/alluxio/master/table/Database.java
0.00% <0.00%> (ø)

...mon/src/main/java/alluxio/shell/CommandReturn.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...mon/src/main/java/alluxio/util/ExceptionUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/wire/AlluxioProxyInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/alluxio/wire/AlluxioMasterInfo.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...src/main/java/alluxio/job/meta/JobIdGenerator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/src/main/java/alluxio/stress/BaseParameters.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 489 more

Continue to review full report at Codecov.

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


Oneview_logical_interconnect_group API 300 Support for Synergy and C7000

Description
Expands support to API 300 for the Oneview_logical_interconnect_group resource
Issues Resolved
#17
Check List

[X] New functionality includes testing.

[X] All tests pass ($ rake test).

[X] New functionality has been documented in the README if applicable.

[X] New functionality has been thoroughly documented in the examples (please include helpful comments).

[ ] Changes are documented in the CHANGELOG.

I suggest waiting for the issue in the oneview-sdk gem #132 get_default_settings in API200 must be used is currently an instance method, when it should be a self method to be fixed before we merge this code.


Methods for setting options are inconsistent

The different way to set options varies widely from option to option.

Some can be set via a flag or environment variable. e.g., --repo/RESTIC_REPOSITORY

Some can be set only via a flag. e.g., --json, --hostname

Some backend options can only be set via --options. e.g., --options connection=10

Some backend options can only be set via environment variables. e.g., GOOGLE_PROJECT_ID

IMO, the options should be consistent. That is, they should all be settable via flags or environment variables.
This is something I can try to clean up and send a PR for when I get a chance.

Just my humble opinion: personally I don't see any problem with this diversity, it seems quite natural, except for the point 4 (if a backend option is settable via an environment variable, it should be settable from the command line). In particular, setting backend options via --options looks like a better approach in comparison with setting them via first-class command line options.
That said, the environment variable for the --hostname command line option looks like a welcome addition.

Agreed, I should have been more clear. I don't think that backend options need to be raised up to full dedicated CLI options, they are fine behind --options. It is the environment variable behavior that should be consistent.

Thanks for raising this issue. I admit that there's a bit of inconsistency, so I'll try to give you some background: There are two places where environment variables are used:

For global options that need to be set for each command: RESTIC_REPOSITORY and RESTIC_PASSWORD, export them once and then run multiple restic commands
For the backend configuration: This was originally added because in the AWS S3 world it's common to have the access credentials in the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, so we just used that. And it seems quite common for other tools too. I agree with you that it's a good idea to have a way to use --option to set this, e.g. with --option s3.access_key_id=foo or so. The extended options (see below) were added quite recently, and not present during initial implementation of the backends.

Then there are the extended options, --option foo=bar, which have been added recently. This is similar to what e.g. ssh or git do, and I expect that we will add many more options in the future that either are not important enough to be promoted to top-level options or are within a specific namespace (e.g. s3.connections=).
However, I disagree that every option should be set via an environment variable. For example, what's the use case of being able to specify the hostname for a new backup via an environment variable instead of the option --hostname? It does not fit into either of the categories mentioned above: It's not relevant to more than one command, and it's not a backend configuration option either.
Is there a use case that I don't see right now?

My use case is for a package I'm writing to control restic. It is cleanest for it to simply set all options the command may need, like hostname, via an environment variable rather than tracking that some must be flags on specific commands.
Doing so is definitely not the end of the world, it just feels inconsistent.

I would like to be able to set b2.connections in the environment - or at least somewhere permanent - so that I don't have to remember to specify it every single time I run a restic command.

I found this confusing as well. I thought I could set the path to the rclone program through an environment variable RESTIC_RCLONE_PROGRAM, but it seems to only be possible through --option rclone.program=/some/path.

Here's a use case for specifying the hostname via an environment variable: using restic via docker-compose. It would allow setting the desired hostname already in the docker-compose.yml, for convenience, overriding the random hostname generated by docker.


Typo in the new hedging API - WithAvailibilityStrategy

Describe the bug
CosmosClientBuilder.WithAvailibilityStrategy contains a typo in the word availability and it is inconsistent with AvailabilityStrategy.
Expected behavior
CosmosClientBuilder.WithAvailabilityStrategy

Thank you @adamnova
Its a real bad mis from our side, thank you for reporting it.
@NaluTripician lets please address it ASAP.


WIP test more Ruby versions on Travis

Not expected to work for a few tries

@rolandwalker What's the status of this pull? Wan't to rebase and merge?

This should be closed, likely, since we now support less ruby versions, and have already removed some of the old ones from various repos.

Yes, this is no longer needed.


remove sed from scripts

most web projects do not have sed in their scripts.  let's try to remove it.

i don't understand the premise, in that a simple google search turns up dockerfile+sed a plenty:
https://www.google.com/search?q=dockerfile+sed&oq=dockerfile+sed&aqs=chrome..69i57.2036j0j1&sourceid=chrome&ie=UTF-8
what is the real concern?
i personally do not feel this is a significant concern.
very open to improvements, i just would like to understand the concrete concerns/objectives.
thoughts?

Just because people are doing it does not mean it is the right thing to do. The concern is docker uses something called aufs which is a write once file system.  Have sed in the script will cause docker to generate a new layer and the more layer there is in the docker image the slower it is and the more file system resource it takes.  Also having sed means you are not make the image completely immutable which is a bad practice as well.

@felixgao Mind creating a pull request with proposed changes to the script(s)? As we had discussed, we own these together as Wasabi committers. If you see areas of improvement, you're empowered to work on the updates to the artifacts and propose them as a PR.

@felixgao do you mind taking a look at https://github.com/intuit/wasabi/pull/78/files#diff-a02022c11f2de6a41f82f8a76f5e0d3cR19 ? It still contains sed in the Dockerfile but much fewer layers around it. Otherwise how should we approach this?