Think about disputing unfunded channels

It is currently possible to dispute channels that were never funded. This could be used to inflate the on-chain state.
Im not sure if it is really a problem but it seems weird since the on-chian state should be minimal.

I don't think it's a mature problem currently. We can reopen later if required.


wrong argument type nil (expected String) when string begins with "www."

I've been using Rinku for several months, and just recently, a problem popped up that I had not seen before.  I'm using Rinku on a particular text field which may or may not contain a URL.  All this time, the URLs have always started with http://, but recently, a user of this particular web application entered www.hostname.tld, and Rinku.auto_link started throwing exceptions:
wrong argument type nil (expected String)
  vendor/bundle/ruby/1.9.1/gems/rinku-1.5.1/lib/rails_rinku.rb:16:in `auto_link'

When I modified the string to start with http:// or removed www., the problem went away.

I still get this error either with https:// or www.
TypeError: wrong argument type nil (expected String)
	from (irb):21:in `auto_link'
	from (irb):21

This is what I'm trying to do,
Rinku.auto_link(text, mode=:all, link_attr=nil, skip_tags=nil) { |link| puts link }

Reproducible with Rinku v2.0.0:
>> gem "rinku", "2.0.0"
=> true
>> require "rinku"
=> true
>> Rinku.auto_link("google.com") { |link| puts link }
=> "google.com"
>> Rinku.auto_link("www.google.com") { |link| puts link }
www.google.com
TypeError: wrong argument type nil (expected String)
	from (irb):4:in `auto_link'
	from (irb):4
	from /Users/bquorning/.rubies/ruby-2.3.1/bin/irb:11:in `<main>'

I can reproduce this too; looking into the cause.

Ah, this is actually the expected behaviour. From the README:

&block is an optional block argument. If a block is passed, it will be yielded for each found link in the text, and its return value will be used instead of the name of the link. E.g.

auto_link('Check it out at http://www.pokemon.com') do |url|
"THE POKEMAN WEBSITEZ"
end
=> 'Check it out at THE POKEMAN WEBSITEZ'

The block is never called in the `"google.com"` example because no autolinking has taken place. It's called in the `"www.google.com"` example, `puts` does its thing, then returns `nil` to Rinku, which is wanting a String.

If you want to use it this way (and ignore the result), you could return an empty string from the block:

Rinku.auto_link("www.google.com") { |link| puts link; "" }; nil
www.google.com
=> nil


[Component Request] Dialogs

Dialog to show information to user, alerts requesing an action.
https://www.google.com/design/spec/components/dialogs.html#dialogs-confirmation-dialogs
When the application needs a confirmation to delete a element "Are you sure to delete? | Yes or No"

Issue #781


.meta files of deleted .pdb files in the upm package

Thanks a lot for this wonderful piece of software. This is a total life saver for me.
Just one tiny thing is, version 2.0.1 for unity includes .meta files for .pdb files. Since unity considers upm packages from remote repositories as read-only, per each .meta file of a .pdb, they report two errors: one for the existence of it, and another for not being able to delete a read-only file.
While deletion of these .meta files may already make our lives even better than now, in the next release, if possible, I would like to have .pdb files as an option. For example, while I was yesterday having a trouble importing this package due to libwebrtc killing the process when there is an invalid audio input (or no permission for the microphone), it was hard to figure out the issue due to the lack of accessibility to the details of the error. I totally agree with your decision to not have the 100 megabytes includes in the package by default, but would like to see them somewhere if possible.
Again, thanks a lot for all this amazing work! While trying to debug the above bug yesterday and going through libwebrtc, I was really about to give up making my application work outside our lab.

Hi @hanseuljun,
Why was this issue closed? Is the .meta file issue happening or not?

It is happening. I just closed this thinking it was too trivial.

i also get them. The warnings get fired everytime the editor gains focus. They don't break anything and you can hide all warnings, however it makes finding other warnings hard.

Yes I agree this needs to be fixed.

Fixed in 2.0.2, just published.


[1pt] PR: Develop Python script to convert ras2fim rating curves to Inundation Mapping calibration format

This PR introduces a new tool for the ras2fim that cycles through the ras2fim outputs and compiles the stream segment midpoints and rating curve tables. The purpose of this tool is to facilitate the use of ras2fim outputs in the FIM calibration workflow.
Additions

src/compile_ras_rating_curves.py: New file. Processes ras2fim outputs into correct format for FIM calibration.

Testing

HUC 07080103

Optional arguments were tested individually and within a variety of usage combinations
Modifed to test for instances where the rating curve is missing, units are mismatched (and unknown)

HUC 12090301

Tested and ran sucessfully after code was adjusted to accommodate multiple rasters in one directory

Output Files

reformat_ras_rating_curve_points.gpkg (point location geopackage)
reformat_ras_rating_curve_table.csv (rating curve CSV)
reformat_ras_rating_curve_log.txt (output log textfile, only saved if '-l' argument is used)
intermediate_outputs/ (rating curve, geospatial, and output logs for each directory, only saved if '-k' argument is used)

Usage

Required input files from ras2fim output:

/02_shapes_from_conflation/_no_match_nwm_lines.shp
/02_shapes_from_conflation/_nwm_streams_ln.shp
/03_terrain/<numerical_id>.tif
/06_ras2rem/rating_curve.csv

Required arguments: -i "input path", -o "output path"

Optional arguments:

use the -l tag to save the output log
use the -v tag to run in a verbose setting
use the -j flag followed by the number to specify number of workers
use the -k flag to keep intermediate files once the script has run
use the -ov flag to overwrite any existing intermediate files
use the -so flag to input a value for the "source" output column (i.e. "ras2fim", "ras2fim v2.1")
use the -lt flag to input a value for the "location_type" output column (i.e. "USGS", "IFC")
use the -ac flag to input a value for the "active" column ("True" or "False")

Recommended parameters:
python ras2fim/src/reformat_ras_rating_curve.py -i 'C:\ras2fim_data\output_ras2fim_models' -o 'C:\ras2fim_data\output_ras2fim_srcs' -v -l -ov

Minimalist run (only uses required arguments):
python ras2fim/src/reformat_ras_rating_curve.py -i 'C:\ras2fim_data\output_ras2fim_models' -o 'C:\ras2fim_data\output_ras2fim_srcs'

Maximalist run (uses all optional arguments):
python ras2fim/src/reformat_ras_rating_curve.py -i 'C:\ras2fim_data\output_ras2fim_models' -o 'C:\ras2fim_data\output_ras2fim_srcs' -v -l -j 6 -k -ov -so "ras2fim" -lt "USGS" -ac "True"

Keep intermediates, save output log, and run quietly (no verbose tag):
python ras2fim/src/reformat_ras_rating_curve.py -i 'C:\ras2fim_data\output_ras2fim_models' -o 'C:\ras2fim_data\output_ras2fim_srcs' -k -l

Input the data source, location type, and active information using the -so, -lt, and -ac flags:
python ras2fim/src/reformat_ras_rating_curve.py -i 'C:\ras2fim_data\output_ras2fim_models' -o 'C:\ras2fim_data\output_ras2fim_srcs' -v -so "ras2fim" -lt "USGS" -ac "True"

Checklist
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>
[x] Links are provided if this PR resolves an issue, or depends on another other PR
[x] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g.: dev-revise-levee-masking)
[x] Changes are limited to a single goal (no scope creep)
[ ] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[x] Changes adhere to PEP-8 Style Guidelines
[x] Any change in functionality is tested
[ ] Passes all unit tests locally (inside interactive Docker container, at /foss_fim/, run: pytest unit_tests/)
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (CHANGELOG and/or README)
[x] Reviewers requested

Also.. where to you envision the new script being called in the overall ras2fim workflow. I can help with that as I am making minor changes to where the initial rating curve is being created.

@RobHanna-NOAA This script would be part of post-processing.

ok. we might have to talk about what is "post processing".  The plan is that when we are done processing a huc that it includes it's own post processing. Then, when we bundle to ras2release (to HV), that script will simply pull in the file's it needs and packages them up.  Or do you see this as a "catfim" type post processing where it brings in multiple hucs into one rating curve?

The script suggests it is part of the full ras2fim process flow, like ras2rem and ras2catchemnts.

I see this as occurring at the HUC-level. One rating curve per HUC.

Did not mean to close. Reopening.

ok cool. That is the way I see it too, so we talk about it shortly
getting it into the ras2fim.py flow.
On Mon, Jun 12, 2023 at 10:34 AM Brad @.***> wrote:

Did not mean to close. Reopening.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/ras2fim/pull/73#issuecomment-1587675489, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVVFLIVYLEW5PSA5SATFC3TXK5AIHANCNFSM6AAAAAAY73EQPE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Rob Hanna
@.***
NOAA Affiliate, Lynker

@EmilyDeardorff Please wrap filenames and arg flags in tick marks in your description. It helps with readability. Thanks.

@RyanSpies-NOAA Have you had a chance to review Emily's latest outputs? I'm fine to merge as long as the files look good to you.

Can you check that the points gpkg includes a CRS? It appears as undefined when viewing the metadata in QGIS and geopandas also throws an error (I have a workaround that assigns the crs to the dataframe).

I am assuming that this is ready to merge. We will include it in today's build.


DEPLOY-569:Stable ActiveMQ Chart (used by ACS 6.1)

Update chart version of Activiti-Cloud-Events-Adapter.

@cristina-sirbu where did the .tgz in this PR come from? Was it built from https://github.com/Activiti/activiti-cloud-charts/tree/5d80d1af8e3d36efe0f3f772656daa7503fd36ee/activiti-cloud-events-adapter ? Because I don't see any changes in that directory other than the chart version.

ok didn't realise there were other PRs


White oval circle appears on clicking the data points in the confusion matrix

Module: Create a Language Understanding App
Lab/Demo: AI-102 Lab 9
Task: Perform batch testing
Step: 5
Description of issue
On clicking the different data points in the confusion matrix several times we observe that an white oval circle appears which overlaps on the data points
Repro steps:
1.Create a Language Understanding app
2.Add Intents, Entities and train the app
3.Perform Batch testing and click on the "see results"
4. In the confusion matrix that appears , click on the different data points
Observe that after some time the oval circle appears , which overlaps on the data points.

Added a note explaining this issue


"ctrl+/" insert "//"  instead of ""

When using with node Js, express et handlebars in Visual Code.
Adding comment to hbs files doesn't work as normal without this extension.
Should add  " "  but it add "//" instead

Hey @nicgravel, I don't know exactly how to do that, so if you do, a PR would be really appreciated.

Its fixed on v. 0.1.0
Sorry for the delay..

I thought the block comment syntax for handlebars should be {{!-- --}}? I don't think regular html comments prevent handlebars from rendering.

@davidpmccormick  you're right, I've just published v0.1.2 with this fix. Thanks

Nice – thanks!


feat: use @rollup/plugin-replace to replace define variables

Description

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Current dependencies on/for this PR:

feat_migrate_optimizer_to_rollup

PR #3

PR #4

PR #5

PR #6

PR #7

PR #8

PR #9   👈

PR #10

This stack of pull requests is managed by Graphite.

Current dependencies on/for this PR:

feat_migrate_optimizer_to_rollup

PR #3

PR #4

PR #5

PR #6

PR #7

PR #8

PR #9   👈

PR #10

This stack of pull requests is managed by Graphite.


[WIP] Service bus session id and partition key sample

Add service bus session id and partition key sample.

Closing this PR, because there it's not active for a long time.


Trigger code once login successful or canceled

Hi all,
Flutter 3.7.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 32fb2f948e (22 hours ago) • 2023-02-08 07:30:10 -0800
Engine • revision f40b73f8a4
Tools • Dart 2.19.2 • DevTools 2.20.1
Platform • Android
using flutter_azure_b2c: ^0.0.9
I have been able to run the sample but now I am wondering how to catch the the user gets redirected back to the app once the login has been successful or canceled.

Found:

    AzureB2C.registerCallback(B2COperationSource.POLICY_TRIGGER_INTERACTIVE,
        (result) async {
      if (result.reason == B2COperationState.SUCCESS) {
        await checkLogin();
      }
    });


Building Interactive Web Applications with WebSockets

In the evolving landscape of web development, the need for real-time, interactive web applications is more prominent than ever. Users expect dynamic experiences with instant updates—be it in chat applications, live sports scores, or stock market feeds. Several CSC301 partners demonstrate needs for dynamic experiences within their products.
This is where WebSockets come into play, offering a powerful solution for bi-directional communication between a client and a server over a single, long-lived connection. I propose adding a new heading, "Building Interactive Web Applications with WebSockets" under the bigger section Tech Stacks to the wiki.
I intend to shed light on this by addressing the following topics -

Introduction - Briefly introduce WebSockets and identify relevance to CSC301 curriculum.
Understanding - This will include a technical overview
WebSockets vs HTTP - Comparing these two to underscore WebSockets' advantages.
Advantages and Disadvantages - Talk about benefits and cover some challenges and considerations.
Setting up - Outline the basic setup requirements for a WebSocket project.
Real-World Use Cases - Describe several applications of WebSockets in the real world
Conclusion - Summarize the key ideas and include further readings.

This proposal addresses a crucial aspect of modern web development and aligns well with the evolving needs of CSC301 partners and the broader industry landscape. WebSockets offer a powerful solution for real-time, interactive web applications, and providing an overview of their usage, advantages, and setup will be immensely beneficial for CSC301 students. Looking forward to seeing this content added to the wiki and exploring real-world use cases of WebSockets. Great initiative!

This is an excellent topic to delve into. While WebSockets may seem sophisticated and not commonly utilized in beginner projects, they are integral to larger software solutions. Therefore, understanding these concepts can greatly benefit CSC301 students, while giving them the ability to implement these solutions effectively.

Completed


Having trouble replicating training process from README

Hello,
Firstly, thanks very much for the work that has gone into this, its a really interesting approach and I am keen to investigate it further.
I have been trying to replicate the work here but am currently struggling to fill in the gaps between the instructions to prepare the OAS dataset and the instructions to train a model. Looking at the hydra configs there are some undocumented steps around preparing a training dataset and validation dataset?
Could you consider updating the readme to facilitate replication please?

Thanks for the note, Justin!
I've updated the processing script and added a script for creating splits. I've also added the splits that I used in my experiments in the "data" directory. Note that you'll have to modify the hydra arguments to match the below, as I had to break the train csv into pieces in order to add to the repo.
data_dir: ./data
train_fn: train_*.csv

Hello.
I have also attempted to follow the instructions provided in the README.md file. But I encountered some runtime errors.
First, I executed the following command for training the generative head.
CUDA_VISIBLE_DEVICES=1 PYTHONPATH="." python scripts/train_seq_model.py model=mlm model.optimizer.lr=0.0005 data_dir=/home/ryota-nakano/workspace/NOS-temp/data train_fn=train_*.csv val_fn=val_iid.csv vocab_file=/home/ryota-nakano/workspace/NOS-temp/vocab.txt log_dir=/home/ryota-nakano/workspace/NOS-temp/out

Upon executing this command, an error was thrown after the fourth epoch. The specific detail of the error is as follows:
Traceback (most recent call last):
  File "/home/ryota-nakano/workspace/NOS-temp/scripts/train_seq_model.py", line 45, in main
    trainer.fit(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 531, in fit
    call._call_and_handle_interrupt(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 41, in _call_and_h
andle_interrupt
    return trainer.strategy.launcher.launch(trainer_fn, *args, trainer=trainer, **kwargs)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/strategies/launchers/subprocess_script.py
", line 91, in launch
    return function(*args, **kwargs)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 570, in _fit_im
pl
    self._run(model, ckpt_path=ckpt_path)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 975, in _run
    results = self._run_stage()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 1018, in _run_s
tage
    self.fit_loop.run()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/fit_loop.py", line 201, in run
    self.advance()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/fit_loop.py", line 354, in advance
    self.epoch_loop.run(self._data_fetcher)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 134,
in run
    self.on_advance_end()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 248,
in on_advance_end
    self.val_loop.run()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/utilities.py", line 177, in _decora
tor
    return loop_run(self, *args, **kwargs)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/evaluation_loop.py", line 122, in r
un
    return self.on_run_end()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/evaluation_loop.py", line 244, in o
n_run_end
    self._on_evaluation_epoch_end()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/loops/evaluation_loop.py", line 325, in _
on_evaluation_epoch_end
    call._call_callback_hooks(trainer, hook_name)
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 189, in _call_call
back_hooks
    fn(trainer, trainer.lightning_module, *args, **kwargs)
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/trainer.py", line 100, in on_validation_epoch_end
    _, log = sample_model(
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/sample.py", line 151, in sample_model
    seed_log, seed_wandb_log = metrics.evaluate_samples(
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/metrics.py", line 215, in evaluate_samples
    samp_df = labeler.label_seqs(s_for_labels)
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/metrics.py", line 98, in label_seqs
    return pd.DataFrame([self.label_seq(s) for s in seqs])
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/metrics.py", line 98, in <listcomp>
    return pd.DataFrame([self.label_seq(s) for s in seqs])
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/metrics.py", line 78, in label_seq
    ss_frac = X.secondary_structure_fraction()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/Bio/SeqUtils/ProtParam.py", line 324, in secondary_structur
e_fraction
    aa_percentages = self.get_amino_acids_percent()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/Bio/SeqUtils/ProtParam.py", line 112, in get_amino_acids_pe
rcent
    percentages = {aa: count / self.length for aa, count in aa_counts.items()}
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/Bio/SeqUtils/ProtParam.py", line 112, in <dictcomp>
    percentages = {aa: count / self.length for aa, count in aa_counts.items()}
ZeroDivisionError: division by zero

On debugging, I found that modifying line 371 of the mlm_diffusion.py file to samples = traj[-1] did not resolve the issue completely. Instead, it prolonged the occurrence of the same error until epoch 356.
Subsequently, I executed the following command, according to the instructions provided for “vanilla infilling experiments,” using the checkpoint from epoch 303. Since the file “poas_seeds.csv” was not available, I used the “poas_seeds.txt” file located in the root directory as a substitute.
CUDA_VISIBLE_DEVICES=1 PYTHONPATH="." python scripts/infill/run_diffusion.py model=mlm ckpt_path="/home/ryota-nakano/workspace/NOS-temp/out/ar_mlm_test/models/best_by_train/epoch\=303-step\=216144.ckpt" +seeds_fn=/home/ryota-nakano/workspace/NOS-temp/poas_seeds.txt +results_dir=infill/ data_dir=/home/ryota-nakano/workspace/NOS-temp/data vocab_file=/home/ryota-nakano/workspace/NOS-temp/vocab.txt log_dir=/home/ryota-nakano/workspace/NOS-temp/infill_out

However, the following error happened. It seems that the poas_seeds.txt file is not the correct one. It appears that there are missing files required for replication. Please verify and provide the necessary files for replication.
Traceback (most recent call last):
  File "/home/ryota-nakano/workspace/NOS-temp/scripts/infill/run_diffusion.py", line 71, in <module>
    main()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/main.py", line 94, in decorated_main
    _run_hydra(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
    raise ex
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
    return func()
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/home/ryota-nakano/miniconda3/envs/nos/lib/python3.10/site-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/home/ryota-nakano/workspace/NOS-temp/scripts/infill/run_diffusion.py", line 59, in main
    sample_outer_loop(
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/sample.py", line 337, in sample_outer_loop
    make_sampling_csv(
  File "/home/ryota-nakano/workspace/NOS-temp/seq_models/sample.py", line 65, in make_sampling_csv
    for vh, vl in seeds:
ValueError: not enough values to unpack (expected 2, got 1)

Apologies in being so slow to reply! I've added the missing csv file here: https://github.com/ngruver/NOS/blob/main/poas_seeds.csv
The csv has should be correctly broken into vh and vl and therefore not lead to the ValueError you included above.
Please let me know if you run into any other issues!
Nate


Add ZernikeWFE.getOPD

Add hook to get OPD from ZernikeWFE before it's applied. If this proves to be useful, it could be pushed down to ParameterizedWFE or similar.

Ah, yes. I've thought about adding exactly this functionality before. More generally this idea is potentially applicable to any optical element. It would be a large refactoring to make all the AnalyticOpticalElements have a getOPD, and then getPhasor would become some small wrapper to that for the complex exponential. That's a longer term change but we should sketch out what a good API might look like.

@mperrin, yes! getting the OPD in meters for the any optic would be incredibly useful, I was wishing, not for the first time, that I had that functionality just last week.

Does this API look good to you @douglase? Any other related "nice to have"s?

That looks good to me.

Well, except in general an optic is defined by two 2D real quantities: an amplitude transmission/throughput and an OPD. If we have a getOPD then should there also be a get_transmission?
One could imagine defining in AnalyticOpticalElement as follows:
    def get_OPD(self, wave, units='meters'):
        return 0

    def get_transmission(self, wave):
        return 1

    def getPhasor(self, wave):
        opd_as_phase = 2 * np.pi * self.get_OPD(wave, units='meters')  / wave.wavelength
        phasor = self.get_transmission(wave) * np.exp(1.j * opd_as_phase)
        return phasor

Then subclasses could define their own get_OPD and get_transmission instead of getPhasor as currently.  Would that be a worthwhile approach? On the other hand this might lead to some repetition of code between the get_OPD and get_transmission functions, for instance setting up coordinate systems.  The other approach would be something like:
    def get_OPD_and_transmission(self, wave, units='meters'):
        return 0, 1

    def getPhasor(self, wave):
        opd, transmission = self.get_OPD_and_transmission(wave, units='meters')
        opd_as_phase = 2 * np.pi * opd  / wave.wavelength
        phasor = transmission * np.exp(1.j * opd_as_phase)
        return phasor

Oh and incidentally when adding new functions, should we strive for PEP8 compliance with underscores? That isn't something I kept in mind when starting this code base 5 years ago but we can be more mindful now perhaps.

I was trying to go with the 'house style' for now, and planning to do a Big Renaming Pull Request for 0.4. I just want to land the WFIRST stuff first, so right now there are a bunch of smallish PRs for POPPY that perhaps point the way to more refactoring once that has gotten released.

I like factoring out get_phasor into get_opd and get_transmission (where most subclasses won't have to touch get_phasor itself). Any non-trivial duplicated code there could be factored out into a private method, I think.

Whoops, I killed it. Thought I could resurrect Travis by merging the code that skips that one test, but git had other ideas.


Release Binary Crash on win10, debug compiled point at pipeline creation fail: No message at all

in ShadowRaytracer.cpp: 187

GPU is nvidia 1070
other sample like gtlf sample 1.4 works, both binary and locally compiled
it works on nvidia 2080 so must be a DXR limitation

Might be related, I had a similar issue where m_pClassifyPso[0] failed to compile, had to update Windows from 1909 to 20H2.

We've triaged the failure on Pascal-based GPUs and will have a fix in the next update to allow it to fail gracefully.


[loc][Query] Context for "Quick picker color for grouping labels."

For string below community member is asking about the context, can you please check? Thanks!
Original comments
BG ISSUE - What is a 'quick picker color'?
by lyubomirv, 5 months ago
Context
src/vs/platform/theme/common/colorRegistry:English (en):plaintext:pickerGroupForeground
Resource
vs_platform
String Hash
22622b86f29794ad75012e01854e037d
String text
Quick picker color for grouping labels.

@josefhosek see this example:

A quick picker provides fast access to a list of items. Multiple items can be grouped together and separated. The quick pick group color is the blue color for grou plabels on the right.


Fix Lint warnings in api-metrics, context-zone-peer-dep, and context-async-hooks

related to #1093,
Which problem is this PR solving?

This PR fixes lint warnings in api-metrics, context-zone-peer-dep, and context-async-hooks packages.

Short description of the changes

Fix lint warnings

I removed the last commit because I realized someone else created a PR for that.


Media Query in Functions

Is it possible to use this in functions?
ie
screenSize () {
   <MediaQuery maxWidth={350}>
      return { screenSize: 'Mobile }
   </MediaQuery>

   <MediaQuery minWidth={351}>
      return { screenSize: 'Desktop }
   </MediaQuery>
}

something like that?

@tonywong625 No you can't use react components like that. You can use the matchmediaquery module directly for this.

ok thanks


Build Vector Library

Provide Vector and Matrix objects and the following functions:
Add, Subtract, Multiply, Dot product, Division, Length, Direction

This is for CPU derivations for input to shader libraries if necessary


Version support policy

Is there a policy regarding which jupyterlab-vim/JupyterLab versions we're "supporting", either within the repo or within the organization? I understand that JL itself has a policy of maintaining the two latest major versions, but this repo doesn't seem to be keeping any branches for maintenance of jupyterlab-vim 0.x for JL 3.x.
I'm asking this partly in reference to #71, which seems to be resolved if we're only maintaining 4.x. On the other hand, if we're planning to accept PRs for JL 3.x users, it seems like we should split off a 0.x branch. Since the number of JL 3.x users may still be substantial for some time, this may come up for other issues as well.
@ianhi @krassowski

I think there is no policy as of now (happy to be corrected though!).
With other extensions in the past my approach was "support the previous major version of JupyterLab as long as it is being developed", this is once we transitioned to JupyterLab 3.0 I would still fix issues for JupyterLab 2-compatible version for as long as there were minor releases (e.g. JupyterLab 2.3) and otherwise only backport security fixes. But it is not clear if there will be JupyterLab 3.7.
If you are asking if it is fine to close the issue my answer would be yes. If you are asking is someone is going to help with a release if you yourself need to support older version the answer is likely yes. If you are asking if other maintainers are going to actively fix bugs in older versions the answer is likely no.

Thanks for your response, @krassowski! It sounds like we can basically say that issues that exist exclusively in 0.x will be "won't fix" then, unless another contributor comes along to maintain that version.

Closing as I believe we're in agreement here


Session and SqlServerCache does not share session keys across multiple servers

I'm using the following project https://github.com/mw007/SessionSample to reproduce this on ASP.NET Core 1.0
As mentioned in the title, I'm using SqlServerCache to manage session state. What I've noticed	is that when running in a multi-server environment, a different session key is generated for requests coming through different servers. I'd like this key to be shared so that session state is shared between servers.
I've looked at the following docs:

https://docs.asp.net/en/latest/fundamentals/app-state.html
https://docs.asp.net/en/latest/performance/caching/distributed.html

In the second doc, I see the following under the What is a Distributed Cache section.

A distributed cache is shared by multiple app servers (see Caching Basics). The information in the cache is not stored in the memory of individual web servers, and the cached data is available to all of the app’s servers. This provides several advantages:

Cached data is coherent on all web servers. Users don’t see different results depending on which web server handles their request

The way I've set this up is by using NGINX to proxy between both servers. Here is the proxy configuration from my nginx.conf file:
upstream backend {
	server localhost:5000;
	server <IP_ADDRESS>:5000 backup;
}

server {
	listen       80;
	server_name  localhost;

	location / {
		proxy_pass http://backend;
		proxy_redirect off;
		proxy_set_header Host $host;
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded_for $remote_addr;
}

If I remove the "backup" option from the second server listed in the upstream configuration, a new session key is created for each request. This makes it so the session is basically not used.
Are there options I need to enable before sharing session between app servers will work?

The session cookie is also protected so you need to share your DataProtection configuration across the machines: https://docs.asp.net/en/latest/security/data-protection/configuration/overview.html

Thank you so much! This fixed the issue I was having.


Added an article to Philosophy & Concepts

chore: Added the article, Decentralized Identity — Owning It! (https://medium.com/p/94987f97649f#1cec) to the Philosophy & Concepts.

https://medium.com/p/94987f97649f#1cec

That URL, because of the '#1cec' suffix sends the viewer down to a point three quarters of the way through the article, to the heading "Time for some Action!".
Pretty sure that wasn't what was intended ?

Thank you for pointing that out. The comment has a different URL from the actual commit, the commit has the URL starting from the beginning.

Good one, I had only read the comment. Looks like an interesting read so thanks for adding it.


ESL is not prevented lock all accounts from spray password attack

ESL is good, but it does not prevent the lock of all accounts of the company

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

ID: d8634165-2ff5-9b01-e3fc-17827360a5f3
Version Independent ID: a5a91921-3193-93ad-df22-d486e65b19f8
Content: Configure AD FS Extranet Lockout Protection
Content Source: WindowsServerDocs/identity/ad-fs/operations/Configure-AD-FS-Extranet-Smart-Lockout-Protection.md
Product: windows-server-threshold
Technology: identity-adfs
GitHub Login: @billmath
Microsoft Alias: billmath

Yep.  Disable the usernamemixed endpoints on the ADFS web application proxies to stop that.  At least for now.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


feat(decorators): add DateOnly and DateTime

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feature[next]: ITIR Inline lift pass extension

Blocked by #1455 (contained in this PR)
Still a draft. While refactoring I found a less complex way for this transformation.

please re-open if still relevant


sqlc volume 1

Note: ignore any changes in the admin directory; we don't use the admin UI atm and I just commented/deleted stuff to get unit tests working
What's new?
The main goal of this PR is to start moving us toward using sqlc instead of inline string-based SQL queries. I'm taking an incremental approach; this PR moves the AdmireRepository and GalleryRepository types over to sqlc, but also includes some groundwork for this and future sqlc PRs. When converting a repository, I've been copying the existing SQL statements verbatim where possible. I'm not trying to change any functionality; just trying to execute the existing queries via sqlc. If an existing SQL statement isn't actually used, or is only used by dead code, I've removed the dead code instead of converting the statement to sqlc.
I've also been prefixing the converted statements with the repository name so it's obvious where the statement came from (e.g. GalleryRepoCheckOwnCollections). New code shouldn't use these statements; in a future pass, I'll either get rid of them or rename them.
Groundwork

Worth noting: the vast majority of changes in this PR come from these groundwork changes, and are mostly just trivial renames or type changes
Removed persist.Repository interfaces

Everything uses postgres.Repository implementations directly now

Added wildcards to sqlc.yaml for common types: *.ids, *._ids, *._address, *.action, etc
Started passing a queries parameter to all Repository types

GalleryRepository

Dropped the backups table instead of converting backup-related SQL statements

In the absence of the backups table, I've improved some logging and fixed a bug in the query scrubbing middleware to ensure we have good visibility into user activity

Got rid of cache-related functions because we haven't used caching since we switched to GraphQL
Removed a lot of dead code
Added a new query to get preview images for the membership page instead of converting the legacy "fully hydrated persist.Gallery" query to sqlc

AdmireRepository

Nothing too notable here

Would it be worthwhile to add it to the email field and for the input used to verify an email?

Good question! Hadn't considered scrubbing email addresses, but that's probably a good call from a PII perspective. Email verification stuff sounds like a good case for scrubbing, too.


Do not display duplicated volumes in Swarm mode

When the UI points to a Swarm cluster, the global volumes are listed for each node in the cluster (Docker Swarm standard behaviour).
It would be clearer to not display duplicates volumes.

This was already added in the internal version: https://github.com/cloud-inovasi/cloudinovasi-ui/commit/b997b787c48e97cb7b9462d14be8e1526107969d#diff-ed8d7e26f2efa506e3bed0f3d60ab057R92


clp-package: Fix several bugs in query worker scripts

Description
This PR fixes two bugs in query worker scripts, introduced by https://github.com/y-scope/clp/pull/460

Fixes a bug where the search results are written to task_id collection. They should be written to job_id collection
Fixes a bug where an int is converted to string before joined as part of the command

Validation performed
Tested with log viewer.

Lgtm. How about changing the PR title to "clp-package: Fix type conversions in query worker scripts."?

hmm, it's not only type conversion. the change also updated the result collection to use job_id instead of task_id.

Lgtm. How about changing the PR title to "clp-package: Fix type conversions in query worker scripts."?

hmm, it's not only type conversion. the change also updated the result collection to use job_id instead of task_id.

Right, sorry for the oversight. How about: clp-package: Fix issues with command generation and search results write destination in query worker scripts.

Quote reply
Reference in new issue
Edit
Hide
Delete

Lgtm. How about changing the PR title to "clp-package: Fix type conversions in query worker scripts."?

hmm, it's not only type conversion. the change also updated the result collection to use job_id instead of task_id.

Right, sorry for the oversight. How about: clp-package: Fix issues with command generation and search results write destination in query worker scripts.

@kirkrodrigues any suggestions?

How about:
clp-package: Fix bugs introduced in #460:

Write search results to collection named job_id rather than task_id.
Convert int to str in IR extraction command generation.

Ordinarily, I'd make these two separate PRs so the commit message is easier to write, but above is how I'd write it so that it makes sense why we're fixing both bugs in one PR.


chromium: add useOzone and 'chromiumOzone' variant

Motivation for this change
Since I did this, apparently talked about it on HN, and someone asked in IRC, I figured I'd send this.
This adds a new chromium variant that enables Ozone and builds relevant ozone backends.
Last time I built it, it wasn't really usable due to where upstream is at with Wayland support. Furthermore, the HiDPI handling is pretty completely broken still.
NOTE: I could use some advice on how to instruct Hydra to not build this.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@colemickens This is a replacement for #50486?

@gnidorah yes.

I've not pushed this yet, it's still too buggy to use, but here's a screenshot, it finally is usable on hidpi now (make sure you don't use the gtk theme):

To disable the hydra build, one need to set meta.hydraPlatforms = [].

Mhm. I think broke evaluation with my merge:
attribute 'useVaapi' at /home/joerg/.cache/nix-review/pr-61008/nixpkgs/pkgs/applications/networking/browsers/chromium/default.nix:39:14 already defined at /home/joerg/.cache/nix-review/pr-61008/nixpkgs/pkgs/applications/networking/browsers/chromium/default.nix:39:14

cc @zimbatm as a wayland user.

$ nix-env -f /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs -qaP --xml --out-path --show-trace --meta
error: while evaluating 'callPackageWith' at /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/lib/customisation.nix:108:35, called from /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/pkgs/top-level/all-packages.nix:17701:14:
while evaluating 'makeOverridable' at /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/lib/customisation.nix:67:24, called from /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/lib/customisation.nix:112:8:
attribute 'useVaapi' at /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/pkgs/applications/networking/browsers/chromium/default.nix:39:14 already defined at /home/zimbatm/.cache/nix-review/pr-61008/nixpkgs/pkgs/applications/networking/browsers/chromium/default.nix:39:14

I rebased. It starts building, but I don't have CPU available right now to build. I didn't fix the hydra building part yet.

Actually, since the Ozone build uses the dev channel, it's already excluded from hydra. Should be okay to review again.

Dropping this as I don't plan to pursue it. For now I plan to build my own chromium in nixpkgs-wayland using volth's chromium-git PR.

@colemickens Is the ozone build somewhat usable? Would you mind pointing me to how I can get a nixpkgs-wayland setup working?


mux to mp4 Dosnt work

there is any way to save live dash to mp4 file while its recording ?
command i have used RE "Manifest_link.mpd" --live-real-time-merge --live-pipe-mux -M format=mp4
still getting .ts file

Actually, the -M option doesn't work when recording live streams. It only kicks in for VOD content.

Actually, the -M option doesn't work when recording live streams. It only kicks in for VOD content.

When download is done I’m just running
ffmpeg -I video.ts -c copy output.mp4
There is any way to do it when download the file or run it automatically when finish?
Thanks.


New release?

Would it be possible to cut a new release? There's been a number of new commits to master since the last release over 7 months ago which I'd love to be able to use without building locally. Let me know if I can help in any way!

@erichoracek since you contributed to repo before I can give you access to make releases, are you on newest OSX? if so you could cut release following our process from https://github.com/krzysztofzablocki/Sourcery/blob/master/RELEASING.md
I don't have newest osx installed and so I couldn't cut release

@krzysztofzablocki Yes—I'm on Catalina (10.15.4). I'd be happy to take on cutting a new release.

@erichoracek awesome :) invite sent

@krzysztofzablocki Great, thanks—accepted. Can I grab trunk access on CocoaPods trunk as well?
pod trunk add-owner Sourcery<EMAIL_ADDRESS>

In preparation for cutting the release I've updated the docs and the circle CI Xcode/Ruby version

#824
#825

And then here's a draft PR for bumping the version to 0.18.0 once we've merged the prep PRs #826

@erichoracek added you to trunk

Looks like we're good!

Release https://github.com/krzysztofzablocki/Sourcery/releases/tag/0.18.0
Homebrew PR https://github.com/Homebrew/homebrew-core/pull/53896
Trunk Podspec https://github.com/CocoaPods/Specs/blob/master/Specs/9/2/2/Sourcery/0.18.0/Sourcery.podspec.json


As a content editor, I want existing content pages migrated from mezzanine to wagtail so that I can manage them in the new system.

testing notes
see the fyi section on #180 before testing this, if you haven't read it yet.
as part of the v3.0 upgrade, we are using a script to convert all of the old pages (the ones in /admin) into their new counterparts (the ones at /pages URLs, which are editable in /cms). we're calling this process the "exodus", because it isn't quite a migration. this issue (and others like it) are for testing that certain kinds of pages were "exodized" correctly - that the new versions got created and work just like the old ones (or better!)
for this issue, we need to check that three types of pages were correctly "exodized" and are available under /pages:

the homepage (/pages/)
all the landing pages (/pages/people, /pages/research, /pages/projects/about, /pages/engage)
all the content pages (too many to list here)

notice that /events and /updates are not landing pages; they're special and will be tested on #252 and #250 respectively. also, /projects/about is special - we wanted /projects/ to just be a list of projects, so the actual landing page is at /projects/about. make sure you go to pages/projects/about to test it.

for the homepage and landing pages, load up the current site (cdh.princeton.edu) and just do a quick comparison to make sure nothing looks out of place in the new counterpart.
for the content pages, you can explore the pages tree in wagtail and just pick a few to examine; anything under /engage is a safe bet. stay away from /projects, /events, /people, and /updates – most of those special pages haven't been "exodized" yet, so you'll see a lot of blank pages. we'll be testing them later.
make sure to also test the two embedded forms /pages/events/cosponsor and /pages/engage/consult; these are sorta "special" but we made them part of this issue, so they should work.

dev notes
depends on #180
this will be a script that can be run by a manage command that uses the tools prototyped in #243 to query for all the existing content page (content page, landing page, homepage) and create their new wagtail versions from #180.
likely order is homepage first, then landing pages, then content pages. probably we will have logic like "if this page's parent hasn't been migrated, do that first, then create it as a child of the parent". maybe we can do something clever and request a flattened page tree from mezzanine so that we do it in top-down order.

[x] migrate homepage
[x] migrate landing pages
[x] migrate content pages (recursively)
[x] ensure page visibility status (draft/published) is migrated
[x] generate simple report of pages with keywords so data is not lost (but do not migrate)
[x] ensure embedded forms are preserved (consult, cosponsor)

Investigating keyword usage on current content:

2 of 57 content pages use keywords
14 of 208 blog posts use keywords

 Page.objects.exclude(keywords_string='')
<SearchableQuerySet [<Page: Engage / Graduate Students / Graduate Fellowships>, <Page: Engage / Graduate Students / Graduate Travel Grants>]>
>>> Page.objects.exclude(keywords_string='').values_list('keywords_string', flat=True)
<SearchableQuerySet ['graduate students grad grants graduate students fellowships', 'grants graduate students travel']>
>>> BlogPost.objects.exclude(keywords_string='')
<BlogPostQuerySet [<BlogPost: Still Speaking in Code>, <BlogPost: Best Practices?>, <BlogPost: Lessons learned from building “Derrida’s Margins”>, <BlogPost: Designing for Jacques Derrida>, <BlogPost: Princeton Prosody Archive: Rebuilding the Collection and User Interface>, <BlogPost: Bridging Digital Humanities Internal And Open Source Software Projects Through Reusable Building Blocks>, <BlogPost: The CDH at DH2018>, <BlogPost: CDH Web 2.0 is live!>, <BlogPost: Why and How We Test Software>, <BlogPost: Fall Visiting Speaker: Deb Verhoeven>, <BlogPost: The One Where There Are Two New Post Docs at the CDH>, <BlogPost: Meet Our (New) Graduate Students!>, <BlogPost: So Long, and Thanks for All the Muffins>, <BlogPost: Project Managers and Designers - Meet up at DH 2017!>]>
>>> BlogPost.objects.exclude(keywords_string='').count()
14
>>> BlogPost.objects.count()
208
>>> BlogPost.objects.exclude(keywords_string='').values_list('keywords_string', flat=True)
<BlogPostQuerySet ['origin story', 'software development projects fallibility process', 'software development lessons learned mistakes process', 'design', 'DH2018', 'software development DH2018', 'DH2018', 'software development', 'testing software development fallibility', 'Workshop lecture visiting speaker', 'postdocs CDH community Workshop projects', 'graduate students CDH projects grad caucus collaboratories', 'DH2017 meetup projectmanagement projectdesign community storify', 'DH2017 meetup projectmanagement projectdesign community']>

Let's not worry about migrating them to wagtail, but generate a quick report of url + keywords so we have the data.

Report on pages with keywords:
graduate-fellowships | Graduate Fellowships | graduate students grad grants graduate students fellowships
engage/graduate-students/graduate-travel | Graduate Travel Grants | grants graduate students travel
blog pages with keywords:
still-speaking-code | Still Speaking in Code | origin story
best-practices | Best Practices? | software development;projects;fallibility;process
lessons-learned-building-derridas-margins | Lessons learned from building “Derrida’s Margins” | software development;lessons learned;mistakes;process
designing-jacques-derrida | Designing for Jacques Derrida | design
princeton-prosody-archive-rebuilding-collection-and-user-interface | Princeton Prosody Archive: Rebuilding the Collection and User Interface | DH2018
dh2018-reusable-software | Bridging Digital Humanities Internal And Open Source Software Projects Through Reusable Building Blocks | software development;DH2018
cdh-dh2018 | The CDH at DH2018 | DH2018
cdh-web-20-live | CDH Web 2.0 is live! | software development
why-and-how-we-test-software | Why and How We Test Software | testing;software development;fallibility
fall-visiting-speaker-deb-verhoeven | Fall Visiting Speaker: Deb Verhoeven | Workshop;lecture;visiting;speaker
the-one-where-there-are-two-new-post-docs-at-the-cdh | The One Where There Are Two New Post Docs at the CDH | postdocs;CDH;community;Workshop;projects
meet-our-new-graduate-students | Meet Our (New) Graduate Students! | graduate;students;CDH;projects;grad;caucus;collaboratories
so-long-and-thanks-for-all-the-muffins | So Long, and Thanks for All the Muffins | DH2017;meetup;projectmanagement;projectdesign;community;storify
project-managers-and-designers-meet-up-at-dh-2017 | Project Managers and Designers - Meet up at DH 2017! | DH2017;meetup;projectmanagement;projectdesign;community

@thatbudakguy These look good!
Just reminding you about the url inconsistency:
On the live site (cdh.princeton.edu), the "grants page" and all its subpages (e.g. research partnerships) do not have "engage" in the URL, even though they are underneath "engage."
On the test site with "pages", urls based on live site don't work (that is, /pages/grants give you an error). Rather, you need: /pages/engage/grants to get it to work. Thus, the research partnership "pages" page is pages/engage/grants/cdh-research-partnerships, NOT pages/grants/cdh-research-partnerships

@thatbudakguy These look good!
Just reminding you about the url inconsistency:
On the live site (cdh.princeton.edu), the "grants page" and all its subpages (e.g. research partnerships) do not have "engage" in the URL, even though they are underneath "engage."
On the test site with "pages", urls based on live site don't work (that is, /pages/grants give you an error). Rather, you need: /pages/engage/grants to get it to work. Thus, the research partnership "pages" page is pages/engage/grants/cdh-research-partnerships, NOT pages/grants/cdh-research-partnerships

@cvansant thanks for flagging the url mismatch! We're thinking we can address/resolve when we tackle the menus so we can properly handle the mismatch between site hierarchy and navigation / menus.

@cvansant thanks for flagging the url mismatch! We're thinking we can address/resolve when we tackle the menus so we can properly handle the mismatch between site hierarchy and navigation / menus.


test fdo packages

This PR includes:

Install FDO packages and start FDO servers in ostree-simplified-installer.sh

For FDO container test, will test it and make another pr

/test-rhel-9-2-simplified

/test-rhel-9-2-simplified

Failed due to bug https://bugzilla.redhat.com/show_bug.cgi?id=2170903

@yih-redhat Could you please make main rebase? I fixed some issues in PR https://github.com/virt-s1/rhel-edge/pull/2132, https://github.com/virt-s1/rhel-edge/pull/2135, and https://github.com/virt-s1/rhel-edge/pull/2124. Thanks!
And the bug has a work around https://bugzilla.redhat.com/show_bug.cgi?id=2170903#c1

@yih-redhat Could you please make main rebase? I fixed some issues in PR #2132, #2135, and #2124. Thanks! And the bug has a work around https://bugzilla.redhat.com/show_bug.cgi?id=2170903#c1

sure, I may need to add one more test "onboarding user", and I will make a rebase and push later.


Arbitrage tx mempool filter

Closes: #723
Description
This PR adds a mempool filter for arbitrage txs. When its hit, it charges a separate gas price, as specified in the full nodes application config.  This defaults to 0 uosmo if not set in the app.toml, but the app.toml defaults to .005uosmo/gas.
The detection algorithm for arbitrage txs does have some false positives, and likely many false negatives. The false positives are described in the code comments, and I think are pretty miniscule. (Only thing I can see hitting it is a service that batches many users swap / LP positions together. Such a batching service seems like it can maintain connections to folks with lower fees though)

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #741 (bb58c10) into main (bc65a83) will decrease coverage by 0.00%.
The diff coverage is 23.07%.

@@            Coverage Diff             @@
##             main     #741      +/-   ##
==========================================
- Coverage   18.73%   18.72%   -0.01%
==========================================
  Files         172      174       +2
  Lines       23908    23931      +23
==========================================
+ Hits         4478     4481       +3
- Misses      18655    18674      +19
- Partials      775      776       +1

Impacted Files
Coverage Δ

x/gamm/types/msg_lp.go
0.00% <0.00%> (ø)

x/gamm/types/msg_swap.go
0.00% <0.00%> (ø)

x/txfees/keeper/feedecorator.go
72.09% <75.00%> (-1.60%)
:arrow_down:

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 bc65a83...bb58c10. Read the comment docs.


How to use another pypi source when install packages

How to use another pypi source when install packages just like "pip install -i" do.

uv pip install -i ?
 -i, --index-url <INDEX_URL>                (Deprecated: use `--default-index` instead) The URL of the Python package index (by default:
                                             <https://pypi.org/simple>) [env: UV_INDEX_URL=]

@FishAlchemist Thank you. That's make sense.


Add custom packages and generators for Python, R and  Node.js

See git commits for more details.

Thanks! :christmas_tree: :gift: :santa:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MacOS not working?

Hi, I tried air-drawing on a MacBook Pro 13 M1 however it seems that neither pose is recognized. The lighting should be ok.
Could it be, that the webcam is not good enough to detect the hand pose?
Did anyone test this on a MacBook already?

I haven't tried it on macbook, but even with a bad webcam it should still make some rough handpose prediction, so I'd say it's a compatibility issue. Do you have any error message in the console (right click -> inspect -> console) when you load the page ?

Ha, this shows an error. It seems that mediapipe is not available for the M1 yet.
Thanks for pointing me to the right direction.


[Question] In Dev branch，When run  ApiApplicationServer#main，the Application will be blocking。Can you help me to solve it?

I was run in my PC，The IDEA console print：
Connected to the target VM, address: '<IP_ADDRESS>:59176', transport: 'socket'

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::       (v2.1.17.RELEASE)

 _ _   |_  _ _|_. ___ _ |    _
| | |\/|_)(_| | |_\  |_)||_|_\
     /               |
                        3.2.0

Just print this logo.
Help me， thank you！

Sorry, it is not blocking,That's the problem with logback-api.xml,Someone commented <appender-ref ref="STDOUT"/> in 58 lines。can you change it？

Sorry, it is not blocking,That's the problem with logback-api.xml,Someone commented <appender-ref ref="STDOUT"/> in 58 lines。can you change it？

You can find the log content in logs/dolphinscheduler-api.log, this is the default behavior.
If you want to print the log on the console, you can replace the appender-ref in the logback-api.xml like below
<root level="INFO">
        <appender-ref ref="STDOUT"/>
</root>

Thank you for your reply，I have started and enjoy it.


Update Packaging_Instructions_Windows.md

@ryanleung were you able to make these same changes in your other PRs?
Otherwise, please do so so that I may close this PR
thanks!


Problems with DSM 6 . can't open parameters or directories

Hi,
I was using subliminal from several years on my nas synology but after a crash, i upgraded it from DSM5 to DSM 6.
And now I can't write anything in parameters . I found a workaround (I hope) in editing config.ini and it seems to work but I don't know how to edit directories to be scanned. Indeed, when I click on Directories and Add , I can't browse any directory.
Can someone help me ?
Best regards,
Fabrice

Please report to spksrc

Désolé , je ne savais pas où poster ...
J'ai donc posté au bon endroit désormais .

Le 2 avr. 2016 à 20:52, Antoine Bertin<EMAIL_ADDRESS>a écrit :
Closed #607.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


chore: promote origins-cms to version 0.0.24

chore: promote origins-cms to version 0.0.24
this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign dnmahendra
You can assign the PR to them by writing /assign @dnmahendra in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


composer install

why composer install , not add cmd  php artisan key:generate?

Because you really don't want that.

That would break all apps every time you deployed them.

You should never run composer update to update a production app - you should do that first, check it works, commit the new lock file, then run composer install on prod.


Stored XSS in Project Name

Version
~ 1.3.22
Problem
~ Stored XSS in Project Name
如何复现此问题

Register a account in the demo domain http://yapi.demo.qunar.com/
Then new a project:

Insert the paload xss"><img src=1 onerror=alert(/xss/)> in project name  and set the project as public.
Then put the project to as public group ,such as test2, so every one can view the project

When the someone including the managers & administrators views the operation dynamics of the project,  malicious js code will execute.

什么浏览器
~ chrome
什么系统（Linux, Windows, macOS）
~ Linux

感谢建议

Please confirm it or not.

@gaoxiaomumu Does the issue have been fixed ? If it does, please show me the commit.Thanks


[Docs | Issue while accessing webchat] Directline app service extension | Webchat mentions azurewebsites.net

[Enter feedback here]
This article mentions in the webchat that the domain needs to be "https://<your_app_service>.azurewebsites.net/.bot/v3/directline"
Where in the endpoint which is created with ASE azure bot will be "https://.appserviceenvironment.net/api/messages
So should we use "azurewebsites.net" or " appserviceenvironment.net" while making a call to ASE azure web app bot with directline extension keys? If this needs to be " appserviceenvironment.net", kindly make the changes in the document :)
Also, when we are using both, we get below error in browser :

Please help with this request

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

ID: 1e3a6ed6-7d29-d82e-c86f-8f405ab12fe3
Version Independent ID: 6a4ba6ea-51df-929f-e307-38c4a1f9b889
Content: Use Web Chat with the direct line app service extension - Bot Service
Content Source: articles/bot-service-channel-directline-extension-webchat-client.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

@MeenakshiBalekar The domain is where the bot is hosted.  For example, in Azure is  https://<bot_name>.azurewebsites.net/' as described in the example. The updated documentation will be in the next available release.

The updated documentation will be in the upcoming release.


Snappi changes sync

place holder
need to test the code

* `_get_property_param_string`

Andy had changed the logic, which would suffice the fix, I had added in snappi generator
if property["type"] in ["number", "integer", "boolean"]:
val = "=%s" % default if default == "None" else "=%s" % default
else:
val = "=%s" % default if default == "None" else "='%s'" % default


[webview_flutter] : eliminated underscore in Javascript channel

Description
The existing behaviour was that the Javascript channel name could only have underscore as a starting character. I changed the regular expression to allow underscore anywhere.
Related Issues
The PR solves issue flutter/flutter#35011
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Closing in favor of https://github.com/flutter/plugins/pull/1996


Add travis-ci continuous builds of firmware

Places to take inspiration from;

Original HDMI2USB firmware - https://github.com/timvideos/HDMI2USB/wiki/Continuous-Integration
Atriq - https://github.com/m-labs/artiq/blob/master/.travis.yml

Things to investigate;

Binstar / Conda
strace - https://github.com/m-labs/migen/blob/master/tools/strace_tailor.sh
Joel's fuse system - http://logs.timvideos.us/%23timvideos/%23timvideos.2014-06-03.log.html#t2014-06-03T14:47:55

Started some stuff here -> https://github.com/timvideos/HDMI2USB-misoc-firmware/pull/43


R2DBC - Oracle Database Support

I found R2DBC when I was searching reactive relational database drivers, but I couldn't see any driver for Oracle DB. Does anyone have any information on whether to provide support?

This issue was moved to r2dbc's SPI for referential purposes.


Enable ACH in Batch Gift Entry

Critical Changes
Changes
We enabled ACH in Batch Gift Entry
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

Tracking W-11831824


Add instructions on how to use the theme as hugo module

What problem does this PR solve?
This PR adds instructions on how to use the theme as hugo module.
It also renames config.toml to hugo.toml in various places.
PR Checklist

[x] I have verified that the code works as described/as intended.
[x] This change does not include any external library/resources.
[x] This change does not include any unrelated scripts (e.g. bash and python scripts).
[x] I have enabled maintainer edits for this PR.

Rebased the PR and resolved merge conflicts.
I realised that preview of my PR is fine with hugo 0.122.0, but fails with hugo 0.123.7.
I doubt that 9f042a81f72ce4d2045ec4eb89948523297feccc was a complete fix for the issue addressed in #170.

Just to mention it here as well - the go.sum still points at release v1.13.0 that doesn't contain the fix yet. When a new release has been created, it can be used as a go module and will resolve the issue.

the go.sum still points at release v1.13.0 that doesn't contain the fix yet.

You are right. I just changed go.sum to point to HEADof repo and everything is fine now 😄.
Sorry for the noise!


Issue/timechodb 841

Fix various issues with removing data-nodes.

Not being able to remove a data-node by it's id
When using an rpc-port of <IP_ADDRESS>:{somePort}, it's impossible to only remove one node.

That's the reason why It's still in WIP and not marked as finished ... my current changes fully address the issues in the JIRA, but have to find out how to sensibly write a unit-test for this (Doing everything with ITs isn't a good idea in my oppinion)


Do not panic on outdated inline snapshots

The code assumed that inline snapshots do not linger around for too long. This caused panics if the files were changed between when the inline snapshot was created and it was applied. Now this case is silently ignored.
Fixes #220

Thanks a lot @mitsuhiko !


Bug: Autosuggest throws an exception when value is 'number'

For my form I need to pre-fill the value from server which end up as Integers.
But when I try to pass that to Autosuggest it fails, It does not have issues with String. Those work just fine
https://codepen.io/anon/pen/QQaxeP
Uncaught TypeError: (intermediate value)(intermediate value)(intermediate value).trim is not a function
    at Autosuggest.getQuery (Autosuggest.js:280)
    at Autosuggest.render (Autosuggest.js:497)
    at finishClassComponent (react-dom.development.js:7873)
    at updateClassComponent (react-dom.development.js:7850)
    at beginWork (react-dom.development.js:8225)
    at performUnitOfWork (react-dom.development.js:10224)
    at workLoop (react-dom.development.js:10288)
    at HTMLUnknownElement.callCallback (react-dom.development.js:542)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:581)
    at invokeGuardedCallback (react-dom.development.js:438)
    at renderRoot (react-dom.development.js:10366)
    at performWorkOnRoot (react-dom.development.js:11014)
    at performWork (react-dom.development.js:10967)
    at batchedUpdates (react-dom.development.js:11086)
    at batchedUpdates (react-dom.development.js:2330)
    at dispatchEvent (react-dom.development.js:3421)

Yup, I encountered the same issue.

@kavink @NicoleRauch Did either of you guys end up finding a way around this bug?

1

Seems like, the value parameter expects a string. Converting the value to a string using toString resolved the problem for me.

I have the same problem trying to work with Objects, I found a solution hacking the method GetQuery from the module:
` //Overide original method for internal use with object
Autosuggest = function getQuery() {
var inputProps = this.props.inputProps;
var value = inputProps.value;
var valueBeforeUpDown = this.state.valueBeforeUpDown;
return value}`

I basically need to override this method and it works. My problem is how

So @mirkourrunanos  did you figure it out how handle that?

@matheuspoleza
I got the same error and finally found out where I made an error :
My onChange function (passed via the inputProps attribute) didn't destruct the newValue from the object :
onChange = (event, { newValue }) => {...}

instead of
onChange = (event, newValue) => {...}

By setting an object (containing the newValue attribute) instead of the string, it's impossible for AutoSuggest to call the trim method on it.
Hope that helped !

@matheuspoleza
I got the same error and finally found out where I made an error :
My onChange function (passed via the inputProps attribute) didn't destruct the newValue from the object :
onChange = (event, { newValue }) => {...}

instead of
onChange = (event, newValue) => {...}

By setting an object (containing the newValue attribute) instead of the string, it's impossible for AutoSuggest to call the trim method on it.
Hope that helped !

In the onChange handler, I was using event.target.value to update my value. When I used the de-structured value of the second parameter (event, { newValue }), it worked. Thanks for this.


feature: add QUIC transport support

http://www.chromium.org/quic

Wrong layer of the stack.  What libuv does is at level 4 of the OSI model, what you are proposing is level 5 or higher.  You can implement QUIC on top of libuv but it has no business in libuv itself.


Update build scripts

The HTML markup in Material Design Guidelines has changed, so I updated build scripts.

Thank you very much!


don't store value in attribute

Store value internally instead of value attribute.
In addition, it fixes error when value attribute removed.

The repo doesn't provide tools to minify the code, so code-input.min.js was not updated.


WyzeAccessory.js  - improve device compatibility

Improving compatibility with Wyze devices by removing some productModel checks.
Plug may have new productModel strings but they are compatible with WLPP1 so check removed.
OutdoorPlug case is duplicated, one with model check and one without, so deleted case with check.
Removed model check from Camera case to enable Pan and Pro models, Outdoor v1/v2, etc...
Accessory toggles privacy mode vs. power on some cameras (Pan v3 for example) but should be functional.

Since all camers dont act the same, its better not to remove this function. It might be improved.


[1207] Fix Manage Courses UI course page link

Context
The link from the vacancies edit page in this app to Manage Course UI doesn't work.
Changes proposed in this pull request

fix the 'Cancel changes' link
fix the course page URL
re-cut helper responsibility

Guidance to review
Alternative to #121 with some more code tidy-up. Best reviewed commit-by-commit.

 Deep-link from vacancies to the course page


LED Colours dont match Colours chosen on Hyperion Remote

Hi,
I am currently using Hyperion to run some Arduino driven WS2812B that i use as mood lighting in my living room. Everything works fine apart from the fact that when i select a colour on my Remote (currently Hyperion Remote for Android, but all apps have the same problem) the LED colour doesn't match what i've chosen. Red comes out as blue, blue as red and yellow as turquoise.
is this likely something i've got wrong in the code for the Arduino? i have two sets of 51 leds.
i've pasted the Arduino code here: http://pastebin.com/wYHf17dp
Thanks,
Adam

I also use WS2812B via Arduino.
Here is the sketch I have adapted (Also uses FastLED like yours) http://pastebin.com/Z0aJYEZ4
Set the following values to your config
#define NUM_LEDS
#define DATA_PIN
#define serialRate
I've added the variables from your setup into my Sketch. Just copy and paste this one below and upload to your arduino
http://pastebin.com/Ny5qVUSV
The arduino Handles the Changeover to GRB make sure your hyperion.json.conf has
"colorOrder" : "rgb"

Hey, Many thanks for that, I think I tried this Sketch otiginally, but it didn't work but i'll try again when i get home.

Only just got round to uploading this. it worked perfectly. Thanks a lot mate.. :)


Markdown! What is it?

Heading level 1
Heading level 2
Heading level 3

list item
list item

....
.....

<xml>

          <heading>Hi there</heading>

 </xml>

[ ] Do your homework, by 11:15am.
[ ] Work on project.
[ ] Play a game.

See the  M with down-arrow in bottom right when you edit? That's GitHub's Markdown tutorial--click on it and you go here:
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax


Bounding box for this dataset

Hi, how can I access the bounding box for this one?

There isn't any.


prometheus-apcupsd-exporter: 0.2.0 -> 0.3.0

Signed-off-by: Matt Layher<EMAIL_ADDRESS>Description of changes
New release of apcupsd_exporter. Adds new metrics regarding UPS temperature and status, and fixes timestamp bugs.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Builds and runs:
16:04 $ ./result/bin/apcupsd_exporter -h
Usage of ./result/bin/apcupsd_exporter:
  -apcupsd.addr string
        address of apcupsd Network Information Server (NIS) (default ":3551")
  -apcupsd.network string
        network of apcupsd Network Information Server (NIS): typically "tcp", "tcp4", or "tcp6" (default "tcp")
  -telemetry.addr string
        address for apcupsd exporter (default ":9162")
  -telemetry.path string
        URL path for surfacing collected metrics (default "/metrics")

/cc @Ma27 @WilliButz

/marvin opt-in

/marvin status needs_reviewer

@GrahamcOfBorg test prometheus-exporters.apcupsd

/status needs_reviewer

@GrahamcOfBorg test prometheus-exporters.apcupsd


Strange style behavior

Hello,
I'm not sure is this a problem from CSS, Node-red or whatever.
I observe a strange behavior of style properties if I automatically format.
For example: I want to set the colors of numbers in a gauge.
<style> /* Zahlen */ #{{'gauge_'+$id}} .g-num:nth-child(n+0) {color: #dc080899;} #{{'gauge_'+$id}} .g-num:nth-child(n+4) {color: #101ed499;} #{{'gauge_'+$id}} .g-num:nth-child(n+6) {color: #1f940099;} #{{'gauge_'+$id}} .g-num:nth-child(n+9) {color: #101ed499;} #{{'gauge_'+$id}} .g-num:nth-child(n+11) {color: #dc080899;} </style>

If I format the code (or copy it to another gauge) the code looks like this
``
and the gauge like this. ???

Any idea what do I wrong.
Best regards
Detlef

``
Sorry
the working code looks like this without empty lines.


Update TestServer limitation

Let's add a comment about this limitation of TestServer: https://github.com/dotnet/aspnetcore/issues/33780

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

ID: 9421feee-5207-e379-00fb-847cc880014c
Version Independent ID: 8415adee-793e-2ba7-b97b-672b493ba42b
Content: Test ASP.NET Core middleware
Content Source: aspnetcore/test/middleware.md
Product: aspnet-core
Technology: aspnetcore-test
GitHub Login: @Tratcher
Microsoft Alias: riande

@wade, look at dotnet/aspnetcore#33780 and add a comment to this article.


Fix application gateway, ssl profile, ssl policy

1710
PR Checklist

[ ] I have added example(s) inside the [./examples/] folder
[ ] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[x] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description

Does this introduce a breaking change

[ ] YES
[x] NO

Testing

Run terraform apply for the example: https://github.com/aztfmod/terraform-azurerm-caf/tree/main/examples/app_gateway/210-agw-with-keyvault. Note configuration for ssl_policy: https://github.com/aztfmod/terraform-azurerm-caf/blob/f0e5018023d998a82e00862c239d3c2a4d1e9a58/examples/app_gateway/210-agw-with-keyvault/application_gateways.tfvars#L29
Verify that the ssl_policy is generated correctly

Thanks for your PR @wubini. Can you please help with the example also, I'm running example 210 and getting :
╷
│ Error: creating Application Gateway: (Name "lsvg-agw-app_gateway_example" / Resource Group "lsvg-rg-example-app-gateway-re1"): network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="ApplicationGatewaySslPolicyMisMatch" Message="The newer and older SSL policies can't be used together for SSLPolicy and listener-specific SSLProfile. Your configuration's sslProfile SecureTLS conflicts with the global sslPolicy AppGwSslPolicy20150501 set for this Application Gateway. Know more about the SSL policies. https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-ssl-policy-overview#usage-and-version-details" Details=[]
│
│   with module.example.module.application_gateways["agw1_az1"].azurerm_application_gateway.agw,
│   on ../modules/networking/application_gateway/application_gateway.tf line 29, in resource "azurerm_application_gateway" "agw":
│   29: resource "azurerm_application_gateway" "agw" {
│
╵

>The newer and older SSL policies can't be used together for SSLPolicy and listener-specific SSLProfile. Your configuration's sslProfile SecureTLS conflicts with the global sslPolicy AppGwSslPolicy20150501 set for this Application Gateway. Know more about the SSL policies. https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-ssl-policy-overview#usage-and-version-details

Thanks @arnaudlh. Could this error be coming from an Azure policy? (I don't think it's an issue with the example.)

Hi @arnaudlh , in my Azure environment I am able to run example 210 and do terraform apply with no errors.

>The newer and older SSL policies can't be used together for SSLPolicy and listener-specific SSLProfile. Your configuration's sslProfile SecureTLS conflicts with the global sslPolicy AppGwSslPolicy20150501 set for this Application Gateway. Know more about the SSL policies. https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-ssl-policy-overview#usage-and-version-details

Thanks @arnaudlh. Could this error be coming from an Azure policy? (I don't think it's an issue with the example.)

I dont think so, probably more a conflict in the policy modes for app-gateway.

https://github.com/hashicorp/terraform-provider-azurerm/issues/22669


Error: Missing information for API call to answerPreCheckoutQuery

Here's my code:
    bot.on('pre_checkout_query', async (ctx) => {
      const query = ctx.update.pre_checkout_query;

      // some validation logic here...

      return await ctx.answerPreCheckoutQuery(true);
    });

I see the following error in the logs:
Error: Missing information for API call to answerPreCheckoutQuery

The interesting part is that regardless of the error everything works fine, the bot receives the successful payment message after this one.
Why do I get this error? Is this a bug in the library or am I doing something wrong?

Can you reproduce the error if you call ctx.api.answerPreCheckoutQuery manually and specify the right value for pre_checkout_query_id?

Yep, it's the same when I use
bot.on('pre_checkout_query', async (ctx) => {
  const query = ctx.update.pre_checkout_query;

  // some validation logic here...

  return await ctx.api.answerPreCheckoutQuery(query.id, true);
});

I'm sorry. The issue occurred because I accidentally put return await ctx.answerPreCheckoutQuery(true); at the end of the next handler - message:successful_payment. That's why everything worked well but the log appeared.
Thanks for your attention anyway, @KnorpelSenf


luject master xmake failed

xmake version :
xmake v2.7.9+20230515, A cross-platform build utility based on Lua

issue print to terminal
[ 25%]: cache compiling.release src/lni/main.cpp
/usr/bin/gcc -c -m64 -fvisibility=hidden -fvisibility-inlines-hidden -O3 -std=c++14 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -isystem /home/jiachengy/.xmake/packages/l/libxmake/v2.7.1/e20dade54e864035be295e18a062200d/include -isystem /home/jiachengy/.xmake/packages/l/libxmake/v2.7.1/e20dade54e864035be295e18a062200d/include/lua -isystem /home/jiachengy/.xmake/packages/l/lief/0.11.5/5fd114f41ff6445fb276c359a1d679ec/include -DNDEBUG -o build/.objs/luject/linux/x86_64/release/src/lni/main.cpp.o src/lni/main.cpp
error: src/lni/main.cpp: In function ‘tb_int_t lni_pe_add_libraries(lua_State*)’:
src/lni/main.cpp:44:23: error: ‘lua_objlen’ was not declared in this scope; did you mean ‘lua_len’?
   44 |         tb_size_t n = lua_objlen(lua, 3);
      |                       ^~~~~~~~~~
      |                       lua_len
src/lni/main.cpp: In function ‘tb_int_t lni_elf_add_libraries(lua_State*)’:
src/lni/main.cpp:86:23: error: ‘lua_objlen’ was not declared in this scope; did you mean ‘lua_len’?
   86 |         tb_size_t n = lua_objlen(lua, 3);
      |                       ^~~~~~~~~~
      |                       lua_len
src/lni/main.cpp: In function ‘tb_int_t lni_macho_add_libraries(lua_State*)’:
src/lni/main.cpp:161:23: error: ‘lua_objlen’ was not declared in this scope; did you mean ‘lua_len’?
  161 |         tb_size_t n = lua_objlen(lua, 3);
      |                       ^~~~~~~~~~
      |                       lua_len
src/lni/main.cpp: In function ‘tb_int_t main(tb_int_t, tb_char_t**)’:
src/lni/main.cpp:223:30: warning: ISO C++ forbids converting a string constant to ‘tb_char_t*’ {aka ‘char*’} [-Wwrite-strings]
  223 |     tb_char_t* taskargv[] = {"lua", "-D", "lua.main", tb_null};
      |                              ^~~~~
src/lni/main.cpp:223:37: warning: ISO C++ forbids converting a string constant to ‘tb_char_t*’ {aka ‘char*’} [-Wwrite-strings]
  223 |     tb_char_t* taskargv[] = {"lua", "-D", "lua.main", tb_null};
      |                                     ^~~~
src/lni/main.cpp:223:43: warning: ISO C++ forbids converting a string constant to ‘tb_char_t*’ {aka ‘char*’} [-Wwrite-strings]
  223 |     tb_char_t* taskargv[] = {"lua", "-D", "lua.main", tb_null};
      |                                           ^~~~~~~~~~

#10

try it again.
xrepo update-repo
xrepo remove --all -y libxmake
xmake f -c
xmake

tks


Config: datetime format

gaaqoo.config.DATETIME_FORMAT
DATETIME_FORMAT = r'(\d{4}):(\d{2}):(\d{2}) (\d{2}):(\d{2}):(\d{2})'

done!


Can i set the language to spanish?

I need to set the plugin to spanish, can i do this?

Locales are managed by momentjs http://momentjs.com/.
To set spanish, you need to set lang to es.
Like this
$('#picker').bootstrapMaterialDatePicker({ format : 'DD/MM/YYYY HH:mm', lang : 'es', weekStart : 1 });

Thanks!!

How change the plugin UI colour?

You can do it by editing css file


Office 365 Groups External Access & SharePoint Online External Sharing Levels

It looks as though the Office 365 Group setting for not permitting external access does not overrule SharePoint Online's External sharing level anymore. Was this a recent change? The Message Center does not show an announcement of this effect. I believe it'd be worth outlining the impact on this page.

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

ID: 40a570bb-2567-565c-e9ff-bf1ccbf38d0e
Version Independent ID: 3d342dea-9dd3-008c-20c6-902452302e95
Content: Manage sharing in OneDrive and SharePoint
Content Source: OneDrive/manage-sharing.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@ferrety2006 Thank you for this feedback
I am not sure if this is a recent change or a possible bug. Support can handle this to resolution.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

We have the same problem. We are going to open a ticket.

There is a solution.
Go to SharePoint Administration Portal. Select the office 365 group. At right panel you can see the options of that site. The last option is about shared use. External Access is not allowed by default.

Hi @ferrety2006 , @jmvelo , thank you for your feedback.
I don't know if this was updated or not but there were updates recently on these docs and SharePoint admin portal. You can see some information about this:
"If you disable external access, or limit external access to a more restrictive form, external users will typically lose access within one hour of the change. If you disable external access, access to resources will also be blocked to guests in Office 365 Groups."
"By default, guests can access group files and the group OneNote notebook. To turn off guess access, you need to turn off the SharePoint external sharing setting at the organization level. For the steps, see Turn external sharing on or off for SharePoint Online, "Manage external sharing for Office 365 Group site collections."
However, even if the SharePoint external sharing setting is turned off, the files from SharePoint sites can still be shared with new guest users based on SharePoint settings. To learn more, see Manage external sharing for your SharePoint Online environment."
From:
https://docs.microsoft.com/en-us/office365/admin/create-groups/manage-guest-access-in-groups
https://docs.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off


Feature Request: Enable JSON serialization in Request and JSON parsing in Response separately

Summary
Note: This is a Feature Request. I'm willing to discuss the 2 solutions I suggest, and already implemented both of them with success; I will submit the PR as soon as discussion on this Feature Request is able to settle on one of the 2 solutions
I think that it would be useful to be able to enable separately the JSON serialization of a Request's data, and the JSON parsing of the Response's data. Currently, both of this parts are handled by the same json param which makes it a pain for people who might want one and not the other.
Simplest Example to Reproduce
This example will be based on https://hellojson.horgix.eu is the most simple API of the world and will just answer this with application/json Content-Type wether you GET or POST on / :
{
    "hello": "world"
}

So, let's send a simple POST to it:
$ cat test.js
var request = require("request");
request(
        {
          method: 'POST',
          url: 'https://hellojson.horgix.eu',
          body: '"feature request"',
          json: true
        },
        function(err, httpResponse, body){
          console.log(body)
          console.log('hello' in body)
        }
)

and the result:
$ node test.js
{ hello: 'world' }
true

This is fine. Now just switch the json: true to json: false in order to not encode the request body ("feature request") in JSON, and we get this:
$ node test.js
{
  "hello": "world"
}

./test.js:12
          console.log('hello' in body)
                              ^

TypeError: Cannot use 'in' operator to search for 'hello' in {
  "hello": "world"
}

    at Request._callback (./test.js:12:31)
    at Request.self.callback (./node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request.<anonymous> (./node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage.<anonymous> (./node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:91:20)

And this is what I want to talk about.
Current Behavior
This request lib exposes the json parameter for requests, allowing the user to enable a set of things:
From https://github.com/request/request#requestoptions-callback :

body - entity body for PATCH, POST and PUT requests. Must be a Buffer,
String or ReadStream. If json is true, then body must be a
JSON-serializable object.
[...]
json - sets body to JSON representation of value and adds Content-type: application/json header. Additionally, parses the response body as JSON.

The usecase that I'm concerned with is the case where we need to do a request that is not a JSON request, but where the expected response is a JSON response, so where we want to be able to use the "Additionally, parses the response body as JSON"  part despite this json param being set to false.
Actually, as told in the documentation quoted some lines ago, the JSON parsing of the response is only enabled if the request itself is declared as json:
From https://github.com/request/request/blob/master/request.js#L1152 :
if (self._json) {
  try {
    response.body = JSON.parse(response.body, self._jsonReviver)

Expected Behavior
I'm feeling like it would make sense to be able to enable this response parsing without depending on the json parameter; this is actually a need that I find myself with, and which is described in details below.
Possible Solution
I see 2 possibles solutions:

Add a json_response parameter that enables response parsing even if json is set to false

Advantages: quite simple, just implies adding a new parameter and documenting it
Disadvantages: it would have to be clear what the default behavior is in case it's not defined

Add something a bit smarter, which parses the JSON in the Response body if the Response comes with application/json as Content-Type, which would totally make sense

Advantages: cleaner, imho
Disadvantages: might be a breaking change for people who are relying on response not being parsed right now

Context
I'm using chakram (site, github) to test a REST API. This is just an extension for chai (site, github) that uses request for requests, and which is run by mocha (site, github).
Among my tests, I would like to test the edge case where I POST an invalid JSON to the API on purpose, but with a Content-Type set correctly to application/json; the goal being to ensure that my API correctly detects the invalid JSON data and handles it propertly by sending back an  HTTP 400 error.
Concretely, this result in the following test: https://gist.github.com/Horgix/6a612f2a86c7507663012f530ed66c59#file-test_invalid_json-js
The "json": false is here to disable the JSON serialization of my data by request lib (it is automatically enabled by chakram), and the manual definition of the Content-Type header is here due to the fact that this is usually done by the json param, which I just explicitely set to false.
My API returns an error looking like this:
HTTP/1.0 400 BAD REQUEST
Content-Type: application/json

{
  "error": "400 Bad Request: Failed to decode JSON object: Unterminated string starting at: line 1 column 9 (char 8)"
}

Until this point, everything is fine.
Except that, as explained in the Current Behavior part, I'm setting the json param to false (since I explicitely want to avoid my request's body from being serialized into JSON), so I don't benefit from the "Additionally, parses the response body as JSON." part, despite the fact that I really want to use it since I'm going to verify this response against a JSON schema (see test linked above). This is actually on this part that my test fails, since the response body is no longer parsed and is only a plain string, which obviously doesn't match whatever JSON schema that expects a dict (which would be got from parsing the reponse body).
That's at this point that I took a look at how this json think is handled and that I felt the need of this Feature Request.
Of course I could parse the response afterward by myself in a single line, but this is something I would expect request being able to do.
Your Environment
Not really relevant. Anyway I'm using nodejs v7.10.0 with request v2.81.0.

5 days ago already?
https://www.youtube.com/watch?v=BLUkgRAy_Vo
Hope you'll get some support and replies from the community!

Is this project still maintained?

Well, guess it isn't maintained anymore, which is weird and scary for the second most depended upon library on npm

Ping ? 🙂

+1 For this request. My use case is when dealing with big integers in the response from the API as the default JSON parser built in Node will not deal with them correctly, so I have to set all the JSON stuff (headers, encoding) manually in the request so it doesn't auto-parse in the response.
I believe those options should indeed be split as you mentioned.