Restructure order of user module load/use and setting executable paths

As brought up in this issue #379 regarding payu being able to find the path to spack built executables. A potential solution, as suggested by @micaeljtoliveira here, was to add the following in config.yaml:
exe: $SPACK_ACCESS_OM3_ROOT/bin/access-om3-MOM6-CICE6

modules:
  use:
      - /g/data/ik11/spack/0.20.1/modules/access-om3/0.3.0/linux-rocky8-cascadelake
  load:
      - access-om3

Where SPACK_ACCESS_OM3_ROOT is set by the access-om3 module.
However currently payu runs module load/use during payu run (Experiment.run()). The paths to the executable are set earlier in the experiment initialisation and if exe is not an absolute path, it prepends the path to the laboratory bin path. The executable paths are checked and added to the manifest during setup in the model driver.
The minimum to get the above solution working, would require moving use/load user modules to Experiment.setup before any Model.setup() is run. It will also require any environment variables to be expanded in the exec_path before the path is checked and added to the manifest. To bypass the absolute path check in initialisation, the exe path will need to start with a forward slash.
I think it could be worth restructuring the Model.exec_path initialisation and setup, so executable paths are set later in Model.setup (vs at payu Experiment initialisation). This means there is no need to ensure there's a starting forward slash in exe as the path will be fully expanded to an absolute path.
As spoke about in the #379, it may be worth adding a check that user module versions are specified. At minimum, it could just be emit a warning if it is using default version.

Closed by https://github.com/payu-org/payu/pull/439


Add 'course_config' feature

can use a config data class with yaml file config for the class to make grading more reproducible


Losing data after prometheus restart

I seem to lose most historical data whenever I restart my Prometheus server.
I'm running both Prometheus and the Postgres Adapter as a docker container, so I assume it has something to do with local cached data vs. when Prometheus will actually use the remote read through the Postgres Adapter.
Is this behaviour observed before, and is there some more docs/insights on how to setup Prometheus with the Postgres Adapter (other than just the write/read urls) ?
I'm not sure where to start debugging this as I don't know if this is either a Prometheus problem, a Postgres Adapter problem, or even a TimescaleDB problem.

Hi @momania,
since docker containers are ephemeral you need to mount a local host volume to a container so all the data will be save on you local machine https://docs.docker.com/storage/volumes/
There is a tutorial that shows basic steps on how to get started
http://docs.timescale.com/v0.10/tutorials/prometheus-adapter

You're welcome. There is a blog post I've published recently on how you integrate Prometheus with PostgreSQL/TimescaleDB:  https://blog.timescale.com/sql-nosql-data-storage-for-prometheus-devops-monitoring-postgresql-timescaledb-time-series-3cde27fd1e07

Have the same issue.. After restarting prometheus I have gaps in the graphs:
https://upload.wiuwiu.de/share.php/566e520d-aa03-45b3-b956-7ed4d502a70e/Screenshot from 2019-02-09 16-59-13.png

Same problem. After restarting server lost last ~2 hours of logs (no problem with older logs). Nothing important it's testing machine for prometheus. Typical basic prometheus.yml file from tutorials.
root@lcx:~/promo# uname -a
Linux lcx 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
root@lcx:~/promo# ./prometheus --version
prometheus, version 2.8.1 (branch: HEAD, revision: 4d60eb36dcbed725fcac5b27018574118f12fffb)
build user:       root@bfdd6a22a683
build date:       20190328-18:04:08
go version:       go1.11.6
Getting warnings:
Fist restart:
level=warn ts=2019-04-04T10:50:46.677339638Z caller=head.go:450 component=tsdb msg="unknown series references" count=1821739
Second restart:
level=warn ts=2019-04-04T10:54:32.894463993Z caller=head.go:450 component=tsdb msg="unknown series references" count=1858139


Update create_csv.py

Conform format of CR_COU_TITLE to OER Commons formatting (Creative Commons Attribution Non Commercial Share Alike 4.0 to cc-by-nc-sa)
What are the relevant tickets?

Addresses part of #100

Description (What does it do?)

Changes output of CR_COU_TITLE from full length of CC license to the format compatible with OER Commons (abbreviated version)
How can this be tested?
Weekly release CR_COU_TITLE output should be "cc-by-nc-sa" for all entries
Additional Context

Completed in https://github.com/mitodl/ocw_oer_export/pull/112


introduce interactive tutorial in DOM breakpoints section

Hey hey @petele I'm piloting interactive tutorials in the DevTools docs. Pretty excited about that. Did I use framebox correctly here? Also, I added a little styling to make inline images display more nicely. I'd like to add this as a general rule but I believe I'm blocked on that (you can ping me if you don't know what I'm talking about).
cc @jpmedley in case you want to writer's review
Notes for posterity:

I'm also testing out using less screenshots and more emphasis on UI labels / small inline images of relevant UI icons. If the docs are still usable like this, then this will aid doc longevity.

✔ Renamed .inline to .devtools-inline


Fix and improve the build system

Fix automatic architecture detection
Fix compiling with MinGW on Linux

MinGW on Windows is still not working though

Default to Clang on macOS
Remove redundant use_custom_api_file option
Format SConstruct using Flake8

Please test extensively on all platforms; I've done basic testing on Windows, macOS and Linux but I may not have caught edge cases.
This closes #245.

Let's try it, we've got the 3.1 branch so lets see how this goes :)


Some question about the inference

Thanks for your nice work~ but I met some questions when I used this model in the customer dataset.
I trained a nice model that achieved satisfying mAP in the validation dataset and the first test dataset (A).  But in the second test dataset(B),  the trained VfNet performed poorly.  And I found that test results were different via many tests. for example, the output json file of the first test was 15MB, the output json file of the second test was 20MB, and so on. I still don't know what caused that. I guessed that may be the multi-scale test?
That's my config:
model = dict(
    type='VFNet',
    pretrained='open-mmlab://res2net101_v1d_26w_4s',
    backbone=dict(
        type='Res2Net',
        depth=101,
        num_stages=4,
        out_indices=(0, 1, 2, 3),
        frozen_stages=1,
        norm_cfg=dict(type='BN', requires_grad=True),
        norm_eval=True,
        style='pytorch',
        dcn=dict(type='DCNv2', deform_groups=1, fallback_on_stride=False),
        stage_with_dcn=(False, True, True, True),
        plugins=[dict(cfg=dict(type='ContextBlock', ratio=1. / 4),
                      stages=(False, True, True, True),
                      position='after_conv3')]
    ),
    neck=dict(
        type='FPN',
        in_channels=[256, 512, 1024, 2048],
        out_channels=256,
        start_level=1,
        add_extra_convs=True,
        extra_convs_on_inputs=False,  # use P5
        num_outs=5,
        relu_before_extra_convs=True),
    bbox_head=dict(
        type='VFNetHead',
        num_classes=num_classes,
        in_channels=256,
        stacked_convs=3,
        feat_channels=256,
        strides=[8, 16, 32, 64, 128],
        center_sampling=False,
        dcn_on_last_conv=True,
        use_atss=True,
        use_vfl=True,
        loss_cls=dict(
            type='VarifocalLoss',
            use_sigmoid=True,
            alpha=0.75,
            gamma=2.0,
            iou_weighted=True,
            loss_weight=1.0),
        loss_bbox=dict(type='GIoULoss', loss_weight=1.5),
        loss_bbox_refine=dict(type='GIoULoss', loss_weight=2.0)),
    # training and testing settings
    train_cfg=dict(
        assigner=dict(type='ATSSAssigner', topk=9),
        allowed_border=-1,
        pos_weight=-1,
        debug=False),
    test_cfg=dict(
        nms_pre=1000,
        min_bbox_size=0,
        score_thr=0.05,
        nms=dict(type='soft_nms', iou_threshold=0.5),
        max_per_img=150))  # 150

img_norm_cfg = dict(mean=[123.675, 116.28, 103.53], std=[58.395, 57.12, 57.375], to_rgb=True)

albu_train_transforms = [
    dict(
        type='OneOf',
        transforms=[
            dict(type='IAAAdditiveGaussianNoise', p=0.5),
            dict(type='CLAHE'),
            dict(type='IAASharpen'),
            dict(type='IAAEmboss'),
            dict(type='RandomBrightnessContrast')], p=0.5),
]

train_pipeline = [
    dict(type='LoadImageFromFile'),
    dict(type='LoadAnnotations', with_bbox=True),
    dict(type='Mosaic', prob=0.5, img_dir='data/train/image',
         json_path='data/annotation/train2.json'),
    dict(type='Resize', img_scale=[(4096, 600), (4096, 1000)], multiscale_mode='range', keep_ratio=True),
    dict(type='RandomFlip', flip_ratio=0.5),

    dict(type='Albu',
         transforms=albu_train_transforms,
         bbox_params=dict(type='BboxParams',
                          format='pascal_voc',
                          label_fields=['gt_labels'],
                          min_visibility=0.0,
                          filter_lost_elements=True),
         keymap={'img': 'image', 'gt_bboxes': 'bboxes'},
         update_pad_shape=False,
         skip_img_without_anno=True),

    dict(type='Normalize', **img_norm_cfg),
    dict(type='GridMask', use_h=True, use_w=True, rotate=1, offset=False, ratio=0.5, mode=1, prob=0.8),
    dict(type='Pad', size_divisor=32),
    dict(type='DefaultFormatBundle'),
    dict(type='Collect', keys=['img', 'gt_bboxes', 'gt_labels']),
]
test_pipeline = [
    dict(type='LoadImageFromFile'),
    dict(
        type='MultiScaleFlipAug',
        img_scale=[(4096, 600), (4096, 800), (4096, 1000)],
        flip=False,
        transforms=[
            dict(type='Resize', keep_ratio=True),
            dict(type='RandomFlip'),
            dict(type='Normalize', **img_norm_cfg),
            dict(type='Pad', size_divisor=32),
            dict(type='DefaultFormatBundle'),
            dict(type='Collect', keys=['img']),
        ])
]

data = dict(
    samples_per_gpu=2,
    workers_per_gpu=2,
    train=dict(
        type=dataset_type,
        classes=classes,
        ann_file=train_ann_file,
        img_prefix=image_dir,
        pipeline=train_pipeline),
    val=dict(
        type=dataset_type,
        classes=classes,
        ann_file=val_ann_file,
        img_prefix=image_dir,
        pipeline=test_pipeline),
    test=dict(
        type=dataset_type,
        classes=classes,
        ann_file=test_ann_file,
        img_prefix=test_image_dir,
        pipeline=test_pipeline))

optimizer = dict(lr=0.01, paramwise_cfg=dict(bias_lr_mult=2., bias_decay_mult=0.))

optimizer_config = dict(grad_clip=None)

lr_config = dict(
    policy='step',
    warmup='linear',
    warmup_iters=500,
    warmup_ratio=0.1,
    step=[36, 40])

log_config = dict(interval=50,
                  hooks=[
                      dict(type='TextLoggerHook'),
                      # dict(type='TensorboardLoggerHook')
                      ])

workflow = [('train', 1)]

runner = dict(type='EpochBasedRunner', max_epochs=41)

swa_optimizer = dict(type='SGD', lr=0.01, momentum=0.9, weight_decay=0.0001)
swa_lr_config = dict(
    policy='cyclic',
    target_ratio=(1, 0.01),
    cyclic_times=12,
    step_ratio_up=0.0)
swa_runner = dict(type='EpochBasedRunner', max_epochs=18)

load_from = 'checkpoints/vfnet_r2_101_dcn_ms_2x_51.1.pth'

Looking for your reply, Thanks!

Hi, you may change nms=dict(type='soft_nms', iou_threshold=0.5) to nms=dict(type='nms', iou_threshold=0.65) when doing multi-scale testing, and then see the test results. From my experience, soft_nms only brings 0.1 mAP gain when using a huge backbone.

Hi, you may change nms=dict(type='soft_nms', iou_threshold=0.5) to nms=dict(type='nms', iou_threshold=0.65) when doing multi-scale testing, and then see the test results. From my experience, soft_nms only brings 0.1 mAP gain when using a huge backbone.

Thanks for your quick reply. I think that the 'soft nms' or the 'nms' may not cause a big gap but it is possible.  The trained model in the first test dataset(A) obtained  58% mAP , but only obtained 52% mAP in the second test dataset(B). And I used the same model to test the second test dataset(B) again, only 41% mAP.
And I would like to know if there are dropped mAP cases randomly in your experiments.
Thanks!

It's a bit weird to see the random drop in performance. I never experienced this in my experiments. But I saw the performance drop when I used soft-nms in multi-scale testing if the iou_threshold was not appropriately set.

It's a bit weird to see the random drop in performance. I never experienced this in my experiments. But I saw the performance drop when I used soft-nms in multi-scale testing if the iou_threshold was not appropriately set.

Thanks for your reply, and thanks for your nice work again. I will conduct some experiments later.


Fix build system issues for LLVM 7

The first commit allows to build against LLVM 7.1; LLVM 7.1 is fixing an ABI compatibility issue that does not affect this project, so it can be used without any issue.
The second commit is fixing an issue that prevents the project from building when only libtirpc is available as SunRPC implementation. It fixes builds on Fedora 29, but further testing is advisable.

Great.


Fix fetchRegistryImageIds (which is only used for "docker push" no-op) to no longer return members of an index/manifest list

This isn't the cause of https://github.com/docker-library/python/issues/888, but it sure is making it hard to fix (because the image that needs to be pushed to that tag is claiming to already be pushed since it's a member of the pushed image already even though it should be pushed).

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

Comparison is base (ff6b5f2) 73.10% compared to head (9a271ea) 73.10%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #88   +/-   ##
=======================================
  Coverage   73.10%   73.10%
=======================================
  Files           7        7
  Lines         714      714
=======================================
  Hits          522      522
  Misses        162      162
  Partials       30       30

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


Add new shards

Hi @veelenga
Added to Development tools section:

kemal-watcher - Kemal plugin to watch files and live-reload the browser
sentry-run - Reload code changes using Sentry.run
watchbird - Monitors directories and files, runs tasks automatically
watcher - Watch file changes using File.stat

Added to Funny stuff section

fast_sleep - Blazing fast (funny) implementation of sleep for Crystal

Nice :) Thanks a lot.


Unable to import AuditComponents(Governance)

Receiving the error
There are missing dependencies. Install the following solutions before installing this one: "msdyn_FlowApprovalsCore (<IP_ADDRESS>)".
Governance Solution Version: 1.50
Core Solution Version: 2.0.10

Please follow step 1 in our documentation to initialize Approvals in the environment: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-governance-components#initialize-flow-approval-tables-in-your-environment


Update module-development.md

@pieandcakes : Thanks for your contribution! The author, @kgremban, has been notified to review your proposed change.

Merging style fixes


Oh my god

That's great! I even found Wenyan in there!
And I'm going to develop an useless assembly-like language called FakeAssembly.
I've done with output.
here is the hello world in FA:
@; By 27Onion
@;
dliteral Hello
dchar ' '
dliteral World

@onion108 this needs to be be but in pull request form, have the issue closed and have  link to the compiler.

OK. I'm gonna upload my compiler(actually, interpreter).
And... could you tell me how to upload a folder(directory) to the github repository please? thanks.

@onion108 sorry I’m not understanding are you trying to upload the interpreter to one of your GitHub repository’s or this one? (I can give an explanation after this question is answered.)

@onion108 this also should be renamed to a more explanatory title.

@onion108 this should also be renamed to a more explanatory title.

Help me to  rename (lol because i'm not good at creating titles.)
And, I mean , I want to know how to upload a folder to the github repository. Any repository can be an example. I usually will add folders manually, but I found that it's not a good way when the structure of the project is too complex.
(Well, I'm not very good at English's grammar. So hope you can understand ;P)

@onion108 this should also be renamed to a more explanatory title.

Help me to  rename (lol because i'm not good at creating titles.)
And, I mean , I want to know how to upload a folder to the github repository. Any repository can be an example. I usually will add folders manually, but I found that it's not a good way when the structure of the project is too complex.
(Well, I'm not very good at English's grammar. So hope you can understand ;P)

@onion108 sorry I’m not understanding are you trying to upload the interpreter to one of your GitHub repository’s or this one? (I can give an explanation after this question is answered.)

Yeah, I'm going to create a repository for the interpreter but I want to know how to upload a folder first and then I'll create the repository and upload my interpreter(Written in Swift) to that repo.

After creating a repository, git clone it locally, add the folder and then git commit and git push


feat(clone) ability to clone SHAs

Seems a bit wasteful to download the whole repo and this comes back to the previous idea of using git worktrees https://github.com/Kong/kong-gojira/pull/83 but as we saw there it came with some gotchas that we are not ready to explore yet. So, this nice

yup. It's not used that often, so I guess the amortized cost is fine.
(We needed it while bisecting a regression after/before a commit that changed deps)


Can I disable swipe when there is only one image

Can I disable swipe when there is only one image?

i see what u say//. there is a no support for that now..

Actually this is feature request.
Feel free to close this issue if you have no plan for it.

@floating-cat fixed


Refactor documentation

Updates on MAPS structure coming soon...

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

In the file clinicadl/clinicadl/__init__.py:

Line 19:1: E402 module level import not at top of file

In the file clinicadl/clinicadl/cli.py:

Line 1119:86: W291 trailing whitespace

In the file clinicadl/clinicadl/utils/maps_manager/__init__.py:

Line 9:1: W391 blank line at end of file


Maya Error Load Render Settings

Error when loading the rendersetupBasic from the Library Loader :
(on the turntable asset)

It can be linked to the error :


Create a Python Package for the Chimoney's API

Create a Python Package for ChiConnect, the new Chimoney API

Should be installable from a package manager like PIP
Should have some tests
Should implement the endpoints outlined at chimoney.readme.io/reference/introduction

Resources

About ChiConnect chimoney.io/chiconnect
Reference chimoney.readme.io/reference/introduction
Swagger Docs api.chimoney.io/api-docs

Start here api.chimoney.io

Hi,
I Handled this and I've made a PR Containing the project and Documention(Remains Deployment to pip and any minor issue which I haven't discovered yet.)


Yaml file not generated - GCST90315948

The yaml file was not automatically generated for GCST90315948, submission id '65c0bc4fe6cd8200012ae294'.
Please investigate and generate.

I've regenerated the metadata yaml and md5sum files and uploaded them to the public FTP. Please review them at: http://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90315001-GCST90316000/GCST90315948/

Looks good to me, ticket can be closed, thank you


Switch to DifferentiationInterface

Switch from AbstractDifferentiation to DifferentiationInterface.

Failures on nightly should disappear once https://github.com/JuliaRegistries/General/pull/108523 is registered. Or at least they won't be my fault anymore


output extension

Any option to jave output files as .mjs instead of .js?

The browser doesn't care about file extensions, so this shouldn't have any affect other than cosmetic (if I'm mistaken, lmk!)
I'm not against the idea of providing this as a config option but don't have the time to contribute it myself.

It's not mandatory but it's recommended by Google Chrome: see here

Then, the contrary would be better. mjs -> js. Because lots of services doesn't give us access to the config file of the server: the default is .js. In addition, as frontend developers, we don't care about this technical/bad choice from nodejs in browsers.

Closing since even Node has walked this back a bit (no longer needed for their most recent planned ESM support) and there aren't any benefits that I know of other than ideological. Will keep an eye out in the future though if that changes.

@FredKSchott There certainly is the argument of the more directly clear and correct semantics and syntax.
https://v8.dev/features/modules#mjs

@FredKSchott The Azure Functions environment only respects esm imports if there is a '.mjs' extension. This would be a really useful feature for Snowpack to allow this configuration. Without it, I'm not able to use Snowpack with Azure Functions.


Cache static endpoints

Coverage decreased (-0.2%) to 82.048% when pulling be52e3ad62774b77dcb9c532875776b4865fdfcf on eatonphil:cache-static-endpoints into ff0c4633c62e3cfadbecba2e3ae3cf5d9ea20641 on linode:master.

Should we add a mechanism to force clearing of the cache, should we need to deploy updates that are coupled to db changes?
30 minutes is pretty short, but you could still create a break for the user without clearing, in which case even 1 minute of broken is too long
perhaps this could be done by always forcing clear of major semver change.
thoughts?

Coverage decreased (-0.2%) to 82.08% when pulling 90c30a1114b0157e42b10b2533766e9ab2332573 on eatonphil:cache-static-endpoints into ff0c4633c62e3cfadbecba2e3ae3cf5d9ea20641 on linode:master.

@eatonphil want to mark DO NOT MERGE for now?


Switch to package references

This is a second attempt at it (see #454 for the first). It now creates the VSIX, and uses the pack target for nuget package creation.

@conniey  Since this now uses the pack target for nuget package creation, I'll probably need to update the build scripts. It requires msbuild to build right now - do we need to support dotnet cli?

@conniey I got the windows builds to work, but can't figure out why the *nix ones are failing. Any ideas?

@twsouthwick It appears when it is trying to run the tests, it tries to do a dotnet restore on the root directory, and as a result, the ApiPort.VisualStudio projects are restored.  Unfortunately, the VSSDK is not installed on *nix systems, so it fails.
It appears you have to alter this line: https://github.com/Microsoft/dotnet-apiport/blob/master/build.sh#L66, by either adding dotnet restore <Path to full csproj> or doing a pushd/popd.

do we need to support dotnet cli?

We need to support it for building on non-Windows systems... We've had a couple of customers issue bugs because they were unable to build/run ApiPort on their Linux machine.

@twsouthwick
Running build.cmd seems to result in an error as well... I can see it in the CI builds but it doesn't appear to be flagged as a build failure. (Possibly because there are still *.trx files to output?)
Testing ApiPortVS.Tests.csproj. Output: ApiPortVS.Tests.2017-09-13.04_44_11.trx
D:\git\conniey\dotnet-apiport\src\ApiPort.VisualStudio\ApiPort.VisualStudio.csproj(186,3): error MSB4019: The imported project "C:\Program Files\dotnet\sdk\2.0.2-vspre-006949\Microsoft\VisualStudio\v15.0\VSSDK\Microsoft.VsSDK.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
Test run for D:\git\conniey\dotnet-apiport\bin\Release\ApiPortVS.Tests\net46\ApiPortVS.Tests.dll(.NETFramework,Version=v4.6)
Microsoft (R) Test Execution Command Line Tool Version 15.3.0-preview-20170628-02
Copyright (c) Microsoft Corporation.  All rights reserved.

The test source file "D:\git\conniey\dotnet-apiport\bin\Release\ApiPortVS.Tests\net46\ApiPortVS.Tests.dll" provided was not found.

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please


Redundant Code Path Inside IF ELSE bLock

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version<EMAIL_ADDRESS>node version:14.17.5
OS version(s):Win32
Steps to reproduce:

Just open the  source code file and see. ( … /node_modules/@slack/bolt/dist/App.js:404)

Expected result:
Take a different code path, i.e. call a different function if ELSE block executed
Actual result:

Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

@TEMHITHORPHE Thanks for taking the time to report this!
The TypeScript code has a slight difference but it does not make any runtime benefit:  https://github.com/slackapi/bolt-js/blob/%40slack/bolt%403.8.1/src/App.ts#L784-L790
Indeed, the lines of code are just redundant. We can simplify the code in future versions.

Okay, but I sure hope "redundant" is only what it is, cause I had to dig into source when I was getting a funny "slack_bot_authorization_error" on a recent(and first) AWS Lambda deployment days ago, brought the entire project to a standstill, and am currently just starting again from scratch, following the steps from https://slack.dev/bolt-js/deployments/aws-lambda like a baby, in case I missed any steps during my previous deployment. Needless to say that too just hit a snag, because for whatever reason I don't understand, "serverless-offline" is not responding to SLACK 's Event API's challenge, but that's an "issue" for another day.


Career pages of - DisneyIndia, WarnerBros & BARC (Broadcasting-Audience-Research-Council)

Hey @Kaustubh-Natuskar ,    " Assign "    me this issue ,
I want to add following company name and their career page in this awesome repository .
Disney India, Warner Bros & BARC (Broadcasting-Audience-Research-Council) .

PR no. #176


Make is.js compatible with 'use strict'

The library is not using 'use strict' at the moment. As a consequence it breaks when concatenated with strict mode code. It could be nice to make it compatible, they are not many triggered errors (1)
line 28
    var root = this || global; // global is undefined

should become something like:
    var root = (typeof global !== 'undefined' && (typeof window === 'undefined' || window === global.window)) ? global : window;

There is a reliable way to get the global object: https://gist.github.com/rauschma/1bff02da66472f555c75 It works even in workers.

Your concatenation process shouldn't enforce modes on code it doesn't own. is.js is in its own IIFE so should otherwise be fine for concatenation.


Aseg Atlas - caudate is missing

Hi @lzehl,
For the Aseg Atlas I miss the region 'Aseg-caudate', respectively cannot find it under parcellation entity.
Would you mind adding it?
Many thanks!

@AnnaHilverling I'll check. this issue should in principle currently go to openMINDS_SANDS (https://github.com/HumanBrainProject/openMINDS_SANDS) where atlases are defined at the moment


fix stringio issue in py3.5.2

this is a fix due to upload_template() breaking. it seems that put no longer works with stringio?

please re-review

This looks to me like it might be a bytes/str issue. Can you provide a piece of code that triggers the error?

@guyromm Can you please rebase on the current master, which includes some travis updates and test fixes so they pass with py3.
I'm still hoping for a showcase that triggers the error ;-)

Since there still is no testcase for this, closing this PR.


Read RFC 9293 vs RFC 793

The beginning of the tcp.rs file states:
Heads up! Before working on this file you should read, at least, RFC 793
But this rfc has been obsoleted by rfc 9293. Any reason why we should still refer to the older rfc?

No reason, other than that code was written before RFC 9293 existed :)

Ahhh ok haha


remove the need to explicitly call (*ircevent.Connection).Loop()

We inherited the following API from upstream:

Client calls (*Connection).Connect(), which returns an error
If err != nil, the connection failed and there are no resources to release
If err == nil, the connection succeeded and the client must call (*Connection).Loop() to maintain the connection

This API does not really make sense given that a successful Connect() already spawns various other goroutines, cleanup of which is managed internally by (*Connection). We should remove the need to call Loop() explicitly; instead, Connect() should spin off the relevant goroutine itself on success, alongside writeLoop and pingLoop. Some possibilities:

Remove it altogether in favor of a Wait() that blocks until the connection is actually finished at the application level, e.g. because of Quit()
Keep it as an alias for Wait()

I looked at this and it seems like it would add more implementation complexity than is really worthwhile. Right now, Loop() calls back into Connect() (to do reconnections), so implementing this would involve separate logic for invocations of Connect() that come from outside (in which case Loop() would need to be autostarted) and those that come from Loop() (in which case it would be incorrect to start an additional Loop()).


[Snyk] Upgrade io.swagger.core.v3:swagger-models from 2.2.12 to 2.2.14

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade io.swagger.core.v3:swagger-models from 2.2.12 to 2.2.14.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released a month ago, on 2023-06-26.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Needs to be done together with https://github.com/vaadin/hilla/pull/1121


Request: Support for self-hosted Jira software servers.

@ASAPHAANING It would be great if you type two words on marketplace reviews - https://marketplace.atlassian.com/plugins/com.web-pal.jira.plugins.chronos/cloud/reviews
something like good or bad will be enought, also github star :star: will help us too. Thank you. :pray: :metal:


Receives UnhandledPromiseRejectionWarning message during bot SSO

Versions
What package version of the SDK are you using. 4.11.1
What nodejs version are you using  10
What browser version are you using  Microsoft Edge 90.0.818.38
What os are you using  Windows
Describe the bug
We're building a Teams bot app with SSO enabled. According to bot SSO flow https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-concept-sso?view=azure-bot-service-4.0 , the bot application should return 412 if token exchange failed. But we observed following UnhandledPromiseRejectionWarning message in console when returning 412:

The SSO functionality is working well, the bug is about unexpected output in console.
Expected behavior
There's no UnhandledPromiseRejectionWarning message in console during bot SSO flow.
Additional context
This seems related to following source code: https://github.com/microsoft/botbuilder-js/blob/main/libraries/botbuilder/src/botFrameworkAdapter.ts#L1244

The reason why this is logged as an unhandled rejection is your call to adapter.processActivity does not have an await with a try/catch or a call to .catch(...). The 412 response, as you mentioned, is normal during the OAuth flow. If you want to ignore it you can add logic to the code that catches the error.


bazel: update googleurl patch with missing header

Upstream fix: https://quiche-review.googlesource.com/c/googleurl/+/11260
Signed-off-by: Keith Smiley<EMAIL_ADDRESS>

/retest

/lgtm deps


chore(master): release 1.1.244

:robot: I have created a release beep boop
1.1.244 (2023-11-16)
Miscellaneous

deps: update dependency @commitlint/cli to v18.4.2 (8e8cdba)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.244 :sunflower:


aarch/freebsd support

I think you can close this too - using the same trick/hack as in #72 and using pre-built zig:
$ tree -Fap zig
zig
└── [drwxr-xr-x]  zig-freebsd-aarch64-0.7.1/
    ├── [lrwxr-xr-x]  lib -> /usr/local/lib/
    └── [lrwxr-xr-x]  zig -> /usr/local/bin/zig*

$ mix test --trace -stale
...
ZiglerTest.Integration.Strategies.YieldingNifTest
  * test yielding nifs can have a void return and parameters (0.1ms)
  * test if you pass an incorrect value in you get fce (0.07ms)
  * test yielding nifs can have an string input (0.01ms)
  * test yielding nifs can have an slice input (0.06ms)
  * test killing the other process lets you cancel the nif (219.8ms)
  * test yielding nifs don't have to suspend (0.03ms)
  * test yielding nifs can sleep for a while (1121.1ms)

  1) test yielding nifs can sleep for a while (ZiglerTest.Integration.Strategies.YieldingNifTest)
     test/integration/strategies/yielding_nif_test.exs:41
     Assertion with >= failed
     code:  assert elapsed >= 2
     left:  1
     right: 2
     stacktrace:
       test/integration/strategies/yielding_nif_test.exs:45: (test)

ZiglerTest.Include.ZiglerIncludeAltNameTest
  * test single include works from zigler preamble (0.01ms)

ZiglerTest.Integration.ZigTest
  * test this module has the code (0.07ms)
  * zigtest forty seven returns forty seven (0.01ms)
  * zigtest system has access to beam test env (0.00ms)
  * test a test can fail, with the correct line number (8788.6ms)

Finished in 214.5 seconds
294 tests, 2 zigtests, 1 failure

Not sure what's happening with the yielding NIF test yet, what os/distro/version are you using for this? I get same issue on amd64 & aarch64 FreeBSD.

yeah the yielding NIF test works both on my machine and on CI.  There should literally be no way for it to quit early unless there's something strange with nanosleep on zig/freebsd

@ityonemo you can close this :rocket: fixed yielding NIF in https://github.com/ityonemo/zigler/pull/234

@ityonemo you can close this :rocket: fixed yielding NIF in https://github.com/ityonemo/zigler/pull/234


update

Hi @azarshab-saeed , Thanks for the PR. These changes look good, but they seem to reflect your own testing rather than address any of the many deficiencies of the project. There are many things that are extremely out of date for this project that could be updated:

multistage Dockerfile
updated usage of compose within the docker command

And I'm sure there are other improvements.
I'm going to close this PR, but feel free to explore some of these other issues.


Merge in new getters: get_snmp_information, get_users, get_network_instances

Merge in new getters: get_snmp_information, get_users, get_network_instances from develop to master

Coverage increased (+0.4%) to 96.505% when pulling 5e30baa712632ad6840df38ba7986b1d544f921a on develop into 6beac260c919f5676540735606be054f8e81f49b on master.


Time-based breaks

Is your feature request related to a problem? Please describe
There's legislation around when drivers need to take a break. This typically depends on the (travel) duration of route. Such breaks are then had along the route, and can be planned. See for example Kok et al. (2009) for a reasonable overview of the problem under EU legislation.
Describe the solution you'd like
Support for at least basic EU break legislation, that is, a 45min break after every 4.5h of driving time.
There are additional restrictions at the daily and weekly level, but those are not that important to support yet, I think. We can always add those later. Additionally, there are several optional aspects we might implement later. A particular case is that the 45min break may be split into one 15min and one 30min break, rather than one 45min break. But that's also for later, I think.
Describe alternatives you have considered
N/A
Additional context
Related to #352, which also discusses some break aspects.

Further: what does this look like in other legislations?

Is the setting of Kok et al. (2009) still up to date with current EU legislation?

I checked some of this, and yes, it seems like it is. There have been updates and revisions, but the core still seems to be 4.5h driving time, 45min break. This break may optionally be split into a 15min and 30min break - see the paper by Goel (2010) above for details.

The US setting is investigated by Goel and Kok (2011).

This paper is super relevant: Goal and Vidal (2013).

I've added a small literature review to the first comment. I think we now have enough good ideas to start working on an implementation, when we're ready to do so. I'll remove the "research" label for now, since the review above should cover most of the big ideas that are out there in the academic literature.

OR-Tools has something built in for breaks, here. Might be relevant.


Added bower.json.

Specified "main" so bower knows which file to use.
Specified "ignore" so bower doesn't download entire repo.
The other properties are just meta.
Consider doing tagged releases on repo https://github.com/bower/bower.json-spec#version

+1
Note that this one seems to be already in the bower repo (although it is outdated).


Wink Garage Doors not migrated to Cover

Home Assistant release (hass --version):
0.27.2
Python release (python3 --version):
3.4.2
Component/platform:
Wink
Cover
Garage_door
Description of problem:
Wink Garage Doors show up as garage_door entities and expose garage_door services
These also generate errors in the log about garage_door being deprecated and needs to be migrated to cover
Expected:
These should be created as cover. entities instead of garage_door entities and services.
Problem-relevant configuration.yaml entries and steps to reproduce:

Configure Wink integration
Have a Wink Garage Door (GoControl Z-wave for my setup)
See the entity list and error in the log

Problem is here. Note that rollershutter should also be moved over.

Closed by #3205


Recent changes

Added new APv2 fixes to the list

Crash Bash (SCUS-94570)
Crash Bandicoot Carnival (SCPS-10140, Original) (PCPX-96202, Taikenban)
Kore Hore! Pukka (SCPS-10133)
Love Hina: Ai wa Kotoba no Naka ni (SLPM-86652)
Love Hina 2: Kotoba wa Konayuki no You ni (SLPM-86677)

Changed all instances of 'my code' to 'alex-free's code'.
Indented some lines of code.
Made slight tweaks to the debug strings.

Replaced country strings to use shorter names as opposed to longer names (e.g. Japan > JPN).
Shortened some of the game titles.

Re-arranged the order of APv2 games slightly.

Note: This did not compile (missing a bracket) so I re-did the commit.

Okay. Thanks.

Okay. Thanks.

Crash Bash did trigger AP on my stock SCPH-1001 using v1.1.2 so I'm not sure why you couldn't reproduce.

I don't know either. No modchips were installed - used both FreePSXBoot, cheat cartridge ROM and boot CD and it doesn't seem to occur.

The same can be also said for my physical copy of the Japanese version.

The same can be also said for my physical copy of the Japanese version.

Maybe possibly the fact that your console is PAL has something to do with it? I don't see any other difference. I have a ton of Japanese and American PS1/PS2s but no PAL ones to verify that though.

I might at one point try and get a PS1 of another region or another model to test this much further.


Color Bleed Effect?

Describe your problem here.
How do I add a color bleed effect like cuphead from indiecross?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

nvm I asked this already


include bug

toJSON has different implementations giving expanded include (correct) and non expanded include (not correct)

json[attr] = (0, _encode2['default'])(attrs[attr], false, true);
(https://parse.com/docs/downloads  -- also the version i think is working in parse hosting)

means that pointers are not expanded, but NPM version of parse is

json[attr] = (0, _encode2['default'])(attrs[attr], false, false);
(https://github.com/ParsePlatform/Parse-SDK-JS)

above works in local debug but on cloud it breaks....
key: 'toJSON',
value: function toJSON() {
var json = {};
var attrs = this.attributes;
for (var attr in attrs) {
if ((attr === 'createdAt' || attr === 'updatedAt') && attrs[attr].toJSON) {
json[attr] = attrs[attr].toJSON();
} else {
json[attr] = (0, _encode2['default'])(attrs[attr], false, true);
}
}
var pending = this._getPendingOps();
for (var attr in pending[0]) {
json[attr] = pending[0][attr].toJSON();
}
            if (this.id) {
                json.objectId = this.id;
            }
            return json;
        }

This was a temporary bug that was fixed in 1.6.6, which is the current version on the repo. We only just finished this, and it takes some time to deploy to our downloads page and the cloud code environment. Please follow issue #32, where we'll be posting when 1.6.6 has been rolled out to the cloud code fleet.


RqHeaders returns List / Set instead of Iterable

RqHeaders now has following methods:
List<String> header(CharSequence key);
Set<String> names();

It makes working with it more convenient.
Fixes #490

@aliceice Thanks, I will ask someone to do a code review here, thanks for your pull request

@dmzaytsev it's yours, please review

@aliceice
@yegor256 mention

let's use Set and List in header() and names() respectively.

you use List in header() and Set in names()

@dmzaytsev it's my mistake. should be List header() and Set names()

@yegor256 got it, thanks

@aliceice @yegor256 another question
we removed VerboseIterable from header()
and some diagnostic messages been lost
should header() return something like VerboseLIst now?

@dmzaytsev I think, yes, we need something like VerboseList

@aliceice please add a decorator VerboseList for List like VerboseIterator

@dmzaytsev Do I understand this right, that I need to implement the VerboseList?
I think this should be a separate task. How should I proceed here?

@aliceice yes , you're right
we need to implement VerboseList but you can add a puzzle for another developer for the implementation VerboseList and its tests, for the replacement List header() to VerboseLIst header()
Also mention in the puzzle a link to deleted lines 101-116 to save diagnostic messages

@dmzaytsev I updated the PR with the puzzles.

@dmzaytsev Okay I don't know how to structure my puzzle comments to let qulice succeed without checkstyle errors..

@dmzaytsev Fixed builds :)

@aliceice thank you!

@rultor merge

@rultor merge

@dmzaytsev Thanks for your request. @yegor256 Please confirm this.

@rultor merge

@dmzaytsev I'm sorry, I don't understand you :( Check this page and try again please

@rultor try to merge

@rultor try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor try to merge

@yegor256 Done! FYI, the full log is here (took me 13min)

@elenavolokhova please, check this issue for QA compliance, as per par.24

@rultor deploy pls

@rultor deploy pls

@davvd OK, I'll try to deploy now. You can check the progress here

@rultor deploy pls

@davvd Done! FYI, the full log is here (took me 11min)

@davvd Looks good!

@davvd Looks good!

@elenavolokhova thanks, got it, great to see high-quality tickets here

@dmzaytsev added 10 mins to @elenavolokhova, for QA review, payment code is 74515550... Many thanks! 26 mins were added to your account in Transaction ID 74515562 (task took 66 hours and 13 mins)... review comments (c=11) added as a bonus... +26 to your rating, your total score is +1707


compatible with isort 5.0+

Hi,
For isort 5.0+, there is a new option extra_standard_library. Currently the seed-isort-config only filtered out modules at field starts with known.
Do we have a plan to support isort 5.0.0?

do you mean known_standard_library which starts with known?

and no, this tool I believe is unnecessary in 5.0

Got it. Thanks!


Enhance docs: specify interval unit

Gentle ping

Looks like simple doc update. @kelseyhightower +1 from me.

Ping @kelseyhightower


fix getting correct mingw-w64 version

When checking mingw-w64 version, at least on debian, the regex being used returned 86 because the name of the binary in debian starts with x86_64-w64 so we use the dumpversion option that gcc has. This fixes not compiling because gcc versions < 7 don't have some checks like shadow-local

Thanks!


Weapons on 2E Character sheet

Describe the bug
I cannot drag weapons from the compendium onto the new 2E character sheets or starship sheets.  1E character sheets work fine.
To Reproduce
Steps to reproduce the behavior:

Open a 2e character sheet
Open 2e Compendium
Select Personal weapons
Drag a weapon onto the 2E version of the character sheet under belongings.  It does not appear.  However, when you switch back to the 1E sheet, the weapon is there.  The same happens with ships.

Note: the feature does work when dragging personal equipment, talents, values, and focuses onto the 2e sheet.
Expected behavior
Weapon should be added to the 2e sheet
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Winows
Browser: Chrome
Current version

This is on Forge

I think you may be adding the 1e weapons by mistake. The "personal weapons" compendium is in the 1st edition folder, you can find the 2e weapons in "equipment (crew)" under the 2nd edition folder.

You are correct sir, user error. Things look good. Sorry to bother you,
appreciate the help. Continue the great work on the module!
On Sat, Oct 5, 2024, 13:54 CalinStar @.***> wrote:

I think you may be adding the 1e weapons by mistake. The "personal
weapons" compendium is in the 1st edition folder, you can find the 2e
weapons in "equipment (crew)" under the 2nd edition folder.
—
Reply to this email directly, view it on GitHub
https://github.com/mkscho63/sta/issues/159#issuecomment-2395132568, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BL3GCG3RE7SZ2LRFHDEIFZLZ2ARWDAVCNFSM6AAAAABPNJRUF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGEZTENJWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Clear out obsolete builds from Demo Apps (a99fd4-tools) environment

Clean up the BCs (and images) in the Demo Apps (a99fd4-tools) environments, and clear out the obsolete ones.
Builds in this environment are triggered by a combination of webhooks on the repos, and a CronJob setup to trigger the builds on a schedule.
Builds here fall into one or more of the following categories:

Failing

Obsolete - Associated with apps we've scaled down and can now be decommissioned.

Shouldn't exist in this environment.  For example vc-authn and acapy-redis-pq.  Neither vc-authn or redis are deployed in these environments.

Required - Supporting deployed apps.

[x] Review the builds.

[x] Decommission any obsolete builds and the associated app components.  Example, email-verification, and safe-entry demos.

[x] Delete builds the should not exist in this environment after confirming they should not exist. Example,  vc-authn and acapy-redis-pq.

[x] Fix the builds that are supporting deployed apps and are stuck or failing.

The a99fd4 dev, test, and prod environments have been cleaned out.


Feature request: view/edit HTML source code

Maybe?

I don't understand the usage scenarios. Could you tell me more details about this ?

A new Preview extension for preview
see: https://leecason.github.io/element-tiptap/preview


Throwing security error: Outdated "libpng" Library Contains Known Security Flaw

When I am trying to run the app via Android Studio 4.1 its throwing me a security error:
Outdated "libpng" Library Contains Known Security Flaw
When I try to run the app this is what is being printed in console window.
Unable to strip the following libraries, packaging them as they are: libjniPdfium.so, libjniPdfium.so, libmodft2.so, libmodft2.so, libmodpdfium.so, libmodpdfium.so, libmodpng.so, libmodpng.so.
In what update will we have secured libpng version. Thanks.

Hi @gadregit , I am facing the same issue, have you found the solution for this issue?

Looks like this library has a depedency on PDFium, which hasn't been updated in a few years.

Looks like this library has a depedency on PDFium, which hasn't been updated in a few years.

Yes, do you have any work around for this issue?

Hi @barteksc Please update the version of libpng being used in PDFium to 1.6.32 or greater.
Currently libpng which PDFium uses contains a security vulnerability disclosed in CVE-2015-8540. please check here

Hi @nidhi88, have you found any solution for this issue?

Hi @barteksc,
We are using the latest stable version 2.8.2. We are facing some security threats as mentioned by others also. Please update the version of libpng being used in PDFium to 1.6.39 or greater.

Try Adding jcenter() in repositories. because this lib is not moved to mavenCentral() and jcenter() depetrecated in android studio.
repositories {
jcenter()
}


Fixed #30801 -- Improved guidance for making good use of signals.

Ticket
#30801
Doubts I have

In ref/signals the warning sections are located after the sections about the signals the warning is about. I continued to follow this pattern. Should the user be warned ahead of using the signal? Not sure.
In topics/signals the setting_changed usage example repeats a lot of code from the Where should this code live? section further down. I tried to minimise the repetition. But I'm not sure I did a good enough job. Feedback appreciated!

cc @adamchainz

@carltongibson All edits are good, thanks!

I rephrased the model warning one, and moved to the top of that section.

Nice!
I have a question about this:

Signals can make your code harder to maintain. Consider implementing a
helper method on a :ref:custom manager <custom-managers>, to
both update your models and perform additional logic, or else
:ref:overriding model methods <overriding-model-methods> before using
model signals.

I see how overriding model methods is a better (in my opinion) approach. E.g. replacing signal usage with model instance methods is obvious to me. For example overriding save.
~However I do not find it that clear how custom managers would make signal usage redundant. Perhaps because I always see signals used at the "instance" rather than "queryset" level.~
After writing the above part (which I've striked through) I realised you are referring to this example use case: I want to send an email when a customer is activated:
class CustomerManager(models.Manager):

    def activate(self):
        self.get_queryset().update(is_active=True)
        # send "you're account is now active" email to customers in queryset

As opposed to a post_save signal.
So I don't think there is anything else to add. Thanks again 👍 👍

Also, it may be that a manager is a better home for some logic, often when involving multiple instances where there's no clear parent.


Streams in FPDart

I'm just in the middle of a major refactor which involves moving a lot of my Dartz code into FPDart.  While going through your articles I found how amazing the TaskEither.tryCatch() is at cleaning up my code (😙👌) .
But now I've come to my Streams and i'm drawing a bit of a blank on how to tidy them up and wonder if this is something that FPDart has a solution for? I'm currently returning Stream<Either<AlertsFailure, List<Alert>>>> in something like this:
Stream<Either<AlertsFailure, List<Alert>>> watchAlerts() async* {
    final userOption = await _auth.getSignedInUser();
    final user = userOption.getOrElse(() => throw NotAuthenticatedError());

    final alertsRef = _firestore.allUserAlerts(user.uid.getOrCrash());
    yield* alertsRef.snapshots().map((query) {
      if (query.docs.isEmpty) {
        return const Left<AlertsFailure, List<Alert>>(AlertsFailure.noAlerts());
      }
      return Right<AlertsFailure, List<Alert>>(query.docs
          .map(
            (alert) => AlertModel.fromFirestore(alert).toDomain(),
          )
          .toList()
        ..sort((a, b) => b.dateCreated.compareTo(a.dateCreated)));
    }).onErrorReturnWith((e, stack) {
      if (e is FirebaseException && e.code.contains('permission-denied')) {
        return const Left<AlertsFailure, List<Alert>>(
            AlertsFailure.insufficientPermission());
      } else {
        return const Left<AlertsFailure, List<Alert>>(
            AlertsFailure.serverError());
      }
    });
  }

i'm trying to imagine something like TaskEither to wrap the snapshot() but don't know how to handle errors from the stream.  The other idea was that there might be some kind of StreamEither but no searching has brought up any examples.
This could be my FP noobish-ness or maybe this is actually a feature request... or maybe this isn't something FP even deals with and then my Stream is the right solution?

Hi @lloydrichards
Streams are a very interesting (and complex) usecase 😅
There are some patterns used in functional programming to deal with Streams. Adding them to fpdart I think would be interesting but also hard work!
Curious to hear any opinion about this 👀

I would like such a feature 😁 my app uses streams nearly constantly for database reading so being able to abstract my left and right makes it much easier for my application layer to return the correct state.
Currently, I rely on RxDart to add more functionality to the stream such as the .onErrorReturnWith() which gives me the correct effect, but can maybe be packaged a little better

I have been working on a alternative to Stream that is more functional in nature:
https://pub.dev/packages/offset_iterator
I have recently added OffsetIterable.fromStreamEither which might be of interest! You can see it in action in this test case:
https://github.com/tim-smart/offset_iterator/blob/main/packages/offset_iterator/test/offset_iterator_test.dart#L111

@SandroMaglione
It would be interesting to prioritize this part, since Future and Streams are commonly used. As in the case of my application

I think dart_either has a practical implementation.
fp_dart already has TaskEither.tryCatch which is generate ADT from Effect, so TaskEither.tryCatchStream would be have.
https://github.com/hoc081098/dart_either/blob/master/lib/src/dart_either.dart#L349-L384
  /// Transforms data events to [Right]s and error events to [Left]s.
  ///
  /// When the source stream emits a data event, the result stream will emit
  /// a [Right] wrapping that data event.
  ///
  /// When the source stream emits a error event, calling [errorMapper] with that error
  /// and the result stream will emits a [Left] wrapping the result.
  ///
  /// The done events will be forwarded.
  ///
  /// ### Example
  /// ```dart
  /// final Stream<int> s = Stream.fromIterable([1, 2, 3, 4]);
  /// final Stream<Either<Object, int>> eitherStream = Either.catchStreamError((e, s) => e, s);
  ///
  /// eitherStream.listen(print); // prints Either.Right(1), Either.Right(2),
  ///                             // Either.Right(3), Either.Right(4),
  /// ```
  ///
  /// ```dart
  /// final Stream<int> s = Stream.error(Exception());
  /// final Stream<Either<Object, int>> eitherStream = Either.catchStreamError((e, s) => e, s);
  ///
  /// eitherStream.listen(print); // prints Either.Left(Exception)
  /// ```
  static Stream<Either<L, R>> catchStreamError<L, R>(
    ErrorMapper<L> errorMapper,
    Stream<R> stream,
  ) =>
      stream.transform(
        StreamTransformer<R, Either<L, R>>.fromHandlers(
          handleData: (data, sink) => sink.add(Either.right(data)),
          handleError: (e, s, sink) =>
              sink.add(Either.left(errorMapper(e.throwIfFatal(), s))),
        ),
      );

Any update on this?


Fixed wishlist event name

The standard Facebook pixel event is AddToWishlist (https://www.facebook.com/business/help/402791146561655?id=1205376682832142), as it stands gets counted as a custom event.
This fixes the syntax.

Sharp eye! Thanks for the PR! I will add some small changes to yours and publish a new version of this template on the gallery :)


DB engine versions issues

I have a MSSQL deployment with RDS module for SQL.
The Engine Version was set to:
engine_version              = "14.00.3035.2.v1"
with the minor autoupgrade option to TRUE.
Now, few months have passed and the RDS instance in AWS has been upgraded automatically to version "14.00.3049.1.v1".
Today I made a change to the terraform code to create an additional instance, and Terraform Plan is returning this change for the DB above:
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ module.-----------
engine_version: "14.00.3049.1.v1" => "~>14.00.3035.2.v1"
Obviously I do not want the db engine to be downgraded.
I haven't found a way to "ignore" the  parameter once the instance was created.
Am I missing something?
Thank you,
Claudio

If you are using autopgrade = true, you should not tie the minor version. Just use 14.00 https://www.terraform.io/docs/providers/aws/r/db_instance.html#engine_version


Blue boxes behind Python domain cross-references

This gives inline code a blue box (with extrastyling disabled):
https://github.com/ionelmc/sphinx-py3doc-enhanced-theme/blob/v2.1.0/src/sphinx_py3doc_enhanced_theme/static/pydoctheme.css_t#L315-L320
But it also gives all Python domain cross references a blue box. I think it might stem from the inherited theme. It looks like Python 3 documentation puts their Python domain cross references in a tt tag instead of a code tag. (<tt (stuff)>(stuff) vs. <code (stuff)>(stuff))
Cross-referencing: http://sphinx-doc.org/domains.html#cross-referencing-python-objects
Python example: https://docs.python.org/3/library/argparse.html

Yes, I think the markup that Sphinx outputs changed (Python 3 docs use older version of Sphinx).

I've added some automated github publishing (from travis), you can see the "bare" version here: http://ionelmc.github.io/sphinx-py3doc-enhanced-theme/bare/
Feel free to make PRs - they are going to be published there (last build overrides everything, don't do anything crazy :grin:)


add support for identifying node and node version

hey there, i added support for identifying node.js and its major version number.

@jdalton there i made use of it

Thanks @soliton4! A PR is a bit of give and take.


update aura/di to 3.0 stable

Can you also update the composer dev dependency please: https://github.com/zendframework/zend-expressive-skeleton/blob/master/composer.json#L38

Closing in favour of https://github.com/zendframework/zend-expressive-skeleton/pull/85


webpack-dev-server could not start

Steps to Reproduce

Error
"webpack-dev-server" �� ���� ����७��� ��� ���譥�
��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.
"webpack-dev-server" �� ���� ����७��� ��� ���譥�
��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.
"webpack-dev-server" �� ���� ����७��� ��� ���譥�
��������, �ᯮ��塞��...
Editor Details
Version: 1.0.0
Mixer User ID: Anonymous

Encrypted Editor State: {"id":"2099f0f08324623d","password":"PtYGRq6fwr6BwKggEdh8GVzu0GjqYWj/jlQvkYy+9EU="}

Hi dont have definitive answer but what I did is recreate the project in CDK in another folder.
For exemple moving project to new folder does not work.
Nick


Error: Type 'AutovalidateMode' not found.

when I run  the example on ipad simulator,the logs show error: Error: Type 'AutovalidateMode' not found.

I solve it by update my flutter version


fix: assertNotInAngularZone should act as a noop

Thank you very much, it fixes the infinite errors we were getting in the console in dev mode, preventing us from testing ours apps with Angular 17+


[Bug]: currentCart object missing in production mode app until refreshing page

Expected Behavior
Clicking Add to Bag on PDP adds product to cart
Actual Behavior
Clicking Add to Bag on PDP yields success message, but when you open cart, cart is empty
Possible Solution
No response
Steps to reproduce

Fresh install of VSF Shopify.

npx @vue-storefront/cli init
cd <new vsf instance directory>
npm install
yarn dev
yarn build
yarn start

Navigate to app homepage.
Click on PLP link.
Click on PDP product.
Click Add to Bag
Notification says successful cart addition, but cart is empty.
Response Payload below.  Notice the GraphQL errors for the currentCart object.

What version of shopify integration are you using?
1.0.18
What version of Node.js are you using?
14.18.1
What browser (and version) are you using?
Chrome 98.0.4758.10
What operating system (and version) are you using?
macOS 12.0.1
Relevant log output
[
    {
        "currentCart": {
            "graphQLErrors": [
                {
                    "message": "Variable $id of type ID! was provided invalid value",
                    "locations": [
                        {
                            "line": 1,
                            "column": 46
                        }
                    ],
                    "extensions": {
                        "value": {},
                        "problems": [
                            {
                                "path": [],
                                "explanation": "Invalid global id `{}`",
                                "message": "Invalid global id `{}`"
                            }
                        ]
                    }
                }
            ],
            "clientErrors": [],
            "networkError": null,
            "message": "Variable $id of type ID! was provided invalid value"
        },
        "product": {
            "__typename": "Product",
            "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0LzUzMjg4NjI1NzY4MDA=",
            "title": "Bag",
            "description": "",
            "descriptionHtml": "",
            "handle": "bag",
            "tags": [
                "Accessories",
                "Sale"
            ],
            "availableForSale": true,
            "totalInventory": 19,
            "vendor": "VSF NEXT PWA",
            "seo": {
                "__typename": "SEO",
                "title": null,
                "description": null
            },
            "variantBySelectedOptions": null,
            "options": [
                {
                    "__typename": "ProductOption",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0T3B0aW9uLzY4MDk5MTk4NDg2MDg=",
                    "name": "Size",
                    "values": [
                        "F"
                    ]
                },
                {
                    "__typename": "ProductOption",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0T3B0aW9uLzY4MDk5MTk4ODEzNzY=",
                    "name": "Color",
                    "values": [
                        "Black"
                    ]
                }
            ],
            "collections": [
                {
                    "__typename": "Collection",
                    "title": "Accessories",
                    "handle": "accessories"
                },
                {
                    "__typename": "Collection",
                    "title": "Sale",
                    "handle": "sale"
                },
                {
                    "__typename": "Collection",
                    "title": "Best Seller",
                    "handle": "best-seller"
                }
            ],
            "images": [
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTI5OTcwMjQ=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465"
                },
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMxMjgwOTY=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p1_1.jpg?v=1593150466",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p1_1.jpg?v=1593150466"
                },
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwOTUzMjg=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p2_1.jpg?v=1593150466",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p2_1.jpg?v=1593150466"
                },
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwNjI1NjA=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p3_1.jpg?v=1593150466",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p3_1.jpg?v=1593150466"
                },
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwMjk3OTI=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p4_1.jpg?v=1593150466",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p4_1.jpg?v=1593150466"
                },
                {
                    "__typename": "Image",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMxNjA4NjQ=",
                    "altText": null,
                    "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p_1.jpg?v=1593150466",
                    "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p_1.jpg?v=1593150466"
                }
            ],
            "variants": [
                {
                    "__typename": "ProductVariant",
                    "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0VmFyaWFudC8zNDgxNzE1MjY4MDA5Ng==",
                    "title": "F / Black",
                    "weight": 0,
                    "availableForSale": true,
                    "sku": "5906878569197",
                    "priceV2": {
                        "__typename": "MoneyV2",
                        "amount": "189.0",
                        "currencyCode": "USD"
                    },
                    "compareAtPriceV2": {
                        "__typename": "MoneyV2",
                        "amount": "0.0",
                        "currencyCode": "USD"
                    },
                    "image": {
                        "__typename": "Image",
                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTI5OTcwMjQ=",
                        "altText": null,
                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465",
                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465"
                    },
                    "selectedOptions": [
                        {
                            "__typename": "SelectedOption",
                            "name": "Size",
                            "value": "F"
                        },
                        {
                            "__typename": "SelectedOption",
                            "name": "Color",
                            "value": "Black"
                        }
                    ],
                    "product": {
                        "__typename": "Product",
                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0LzUzMjg4NjI1NzY4MDA=",
                        "title": "Bag",
                        "availableForSale": true,
                        "handle": "bag",
                        "description": "",
                        "descriptionHtml": "",
                        "images": {
                            "__typename": "ImageConnection",
                            "edges": [
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTI5OTcwMjQ=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465"
                                    }
                                },
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMxMjgwOTY=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p1_1.jpg?v=1593150466",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p1_1.jpg?v=1593150466"
                                    }
                                },
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwOTUzMjg=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p2_1.jpg?v=1593150466",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p2_1.jpg?v=1593150466"
                                    }
                                },
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwNjI1NjA=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p3_1.jpg?v=1593150466",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p3_1.jpg?v=1593150466"
                                    }
                                },
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMwMjk3OTI=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p4_1.jpg?v=1593150466",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p4_1.jpg?v=1593150466"
                                    }
                                },
                                {
                                    "__typename": "ImageEdge",
                                    "node": {
                                        "__typename": "Image",
                                        "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTMxNjA4NjQ=",
                                        "altText": null,
                                        "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p_1.jpg?v=1593150466",
                                        "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p_1.jpg?v=1593150466"
                                    }
                                }
                            ]
                        },
                        "productType": "C",
                        "options": [
                            {
                                "__typename": "ProductOption",
                                "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0T3B0aW9uLzY4MDk5MTk4NDg2MDg=",
                                "name": "Size",
                                "values": [
                                    "F"
                                ]
                            },
                            {
                                "__typename": "ProductOption",
                                "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0T3B0aW9uLzY4MDk5MTk4ODEzNzY=",
                                "name": "Color",
                                "values": [
                                    "Black"
                                ]
                            }
                        ]
                    }
                }
            ],
            "name": "Bag",
            "price": {
                "original": "0.0",
                "current": "189.0"
            },
            "available": true,
            "_id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0LzUzMjg4NjI1NzY4MDA=",
            "variantId": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0VmFyaWFudC8zNDgxNzE1MjY4MDA5Ng==",
            "_description": "",
            "_descriptionHtml": "",
            "_categoriesRef": [],
            "_slug": "bag",
            "_coverImage": {
                "__typename": "Image",
                "id": "Z2lkOi8vc2hvcGlmeS9Qcm9kdWN0SW1hZ2UvMTc1NjA1NTI5OTcwMjQ=",
                "altText": null,
                "originalSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465",
                "transformedSrc": "https://cdn.shopify.com/s/files/1/0407/1902/4288/products/ZA029936_016_p.jpg?v=1593150465"
            },
            "_mainPrice": "189.0"
        },
        "quantity": 1,
        "customQuery": [
            {
                "key": "CustomAttrKey",
                "value": "CustomAttrValue"
            }
        ]
    }
]

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@cavemon Re-install the fresh instance will fix the problem. It was happened due to attributes were missing on the PDP. Thanks for reporting.

@aureate-labs-team

@cavemon Re-install the fresh instance will fix the problem. It was happened due to attributes were missing on the PDP. Thanks for reporting.

I'm still experiencing the issue.  Pulled the latest as instructed and getting this response on the /api/shopify/addToCart XHR:
{
    "graphQLErrors": [
        {
            "message": "Variable $checkoutId of type ID! was provided invalid value",
            "locations": [
                {
                    "line": 1,
                    "column": 54
                }
            ],
            "extensions": {
                "value": null,
                "problems": [
                    {
                        "path": [],
                        "explanation": "Expected value to not be null"
                    }
                ]
            }
        }
    ],
    "clientErrors": [],
    "networkError": null,
    "message": "Variable $checkoutId of type ID! was provided invalid value"
}

Is this issue different?  Seems identical to me.


vCenter Permissions and roles getting an error - pl help

... eport = @()    $authMgr = Get-View AuthorizationManager    $roleHash = @{}    $a ...

               ~~~~~~~~

Unexpected token '$authMgr' in expression or statement.
At C:\Karthik\vCenter permission and roles\PRtestAlan.ps1:1 char:948

... rmissions()    foreach($perm in $perms){      $ret = New-Object PSObject      $e ...

               ~~~~~~~

Unexpected token 'foreach' in expression or statement.
At C:\Karthik\vCenter permission and roles\PRtestAlan.ps1:1 char:1694

... nt($nodeName)  $node.AppendChild($tmp)}function Set-XmlAttribute{  param($node,  ...

               ~~~~~

Unexpected token '$node' in expression or statement.
At C:\Karthik\vCenter permission and roles\PRtestAlan.ps1:1 char:1901

... Inventory =  1 ""# Roles$XMLRoles = ...

               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Unexpected token '""' in expression or statement.
+ CategoryInfo          : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken

This isn't a vCheck script name, what are you trying to run? It also looks like you have some issue with your line endings or character encoding looking at those errors...

No response in almost 4 weeks - closing off issue.


[AIRFLOW-3327] Add support for location in BigQueryHook

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3327

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

The geographic location of the job is required except for US and EU. See details at https://cloud.google.com/bigquery/docs/locations#specifying_your_location.
This PR also cleans some tests
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
All the public functions and the classes in the PR contain docstrings that explain what it does

Code Quality

[x] Passes flake8

cc @fenglu-g

Codecov Report

Merging #4324 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4324      +/-   ##
=========================================
+ Coverage   78.09%   78.1%   +<.01%
=========================================
  Files         201     201
  Lines       16471   16471
=========================================
+ Hits        12863   12864       +1
+ Misses       3608    3607       -1

Impacted Files
Coverage Δ

airflow/models.py
92.35% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

cc @dsdinter


interfaces.php Custom reset text typo

Closing in favour of https://github.com/pfsense/pfsense/pull/1876


SIGBUS/SIGSEGV memory errors when resizing plus converting in some codecs

Describe the bug
Running squoosh with both --resize and --webp produces a SIGBUS (Misaligned address error) on MacOS. I've reproduced this with multiple images and with different options.
With avif, I get SIGSEGV (Address boundary error) or SIGBUS, depending on how my OS if feeling.
However, I can use the resize options with --mozjpeg without any segfaults.
If I run without --resize, avif and webp conversion work. Both commands with resize also do work with about 10% success rate (i.e. 10% chance of no segfaults).
To Reproduce
So far I haven't seen a case where these steps fail:

Open an image in squoosh
Turn on resize and set the resize to less than 100% (resize 100% works without issue)
Set compression to webp
The squoosh webapp shows the result successfully. But copying the npx command & running it fails.

Precise steps to reproduce the behavior:

Download the panda image (open squoosh webapp, open panda example, download the uncompressed image). I've also attached it to this issue: photo
Download squoosh-cli with npm
Run squoosh-cli --resize '{"enabled":true,"width":1000,"height":335,"method":"lanczos3","fitMethod":"stretch","premultiply":true,"linearRGB":true}' --webp '{"quality":70,"target_size":0,"target_PSNR":0,"method":6,"sns_strength":50,"filter_strength":60,"filter_sharpness":0,"filter_type":1,"partitions":0,"segments":4,"pass":1,"show_compressed":0,"preprocessing":0,"autofilter":0,"partition_limit":0,"alpha_compression":1,"alpha_filtering":1,"alpha_quality":100,"lossless":0,"exact":0,"image_hint":0,"emulate_jpeg_size":0,"thread_level":0,"low_memory":0,"near_lossless":100,"use_delta_palette":0,"use_sharp_yuv":0}' photo.jpg
See error

For avif I'm using: squoosh-cli --resize '{"enabled":true,"width":500,"height":500.0,"method":"lanczos3","fitMethod":"stretch"}' --avif '{"cqLevel":13,"speed":2}' photo.jpg
The error
 photo.jpg: 2.66MBfish: Job 1, 'squoosh-cli --resize '{"enabled…' terminated by signal SIGBUS (Misaligned address error)

Version:

OS w/ version: macOS 11.4, arm64
Node version: v16.4.0
npm version: 7.18.1

Here is the crash report if it's any help: node_2021-07-16-014625.crash.txt

Can you do me a favor and re-try on Node v16.5? An important bug fix for Wasm on arm64 landed in the last update that caused seg faults.

Silly me. That fixed it. Thanks!


Bug/mentee intake returns bad request

Description
Bugfix: Submitting the Mentee Intake form returns "400: Bad Request" from the back end server.
Video Link
[Loom Video](Add your loom video link here)
Trello Link
https://trello.com/c/s3ke6ILU/366-bug-mentee-intake-form-submit-returns-bad-request
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have removed unnecessary comments/console logs from my code
[ ] My changes generate no new warnings
[ ] I have checked my code and corrected any misspellings
[ ] No duplicate code left within changed files
[ ] Size of pull request kept to a minimum
[ ] Pull request description clearly describes changes made & motivations for said changes

 Bug: Mentee intake form, submit returns bad request


XBM Setting -> Potential lead to out of memory

Dear author,
I notice that size (xbm setting) for sop dataset is set to dataset size. Will this setting result in out of memory?

Hi,
Storing all the item instances of SOP in a tensor on GPU is quite small, ie 60000x512 which is ~1.4GB.
The authors of XBM explain that this is why this method is memory effective. You only have to compute embeddings and gradients for small batches, as you would do in a typical setting.
Hope this helps :)

I see. Thanks for the explanation.


EO:Bands in the STAC Item properties

Would it make sense to make the EO extension requirements a bit softer? Or that was done on purpose, and the idea behind it was only to use it as a union?
I.e. for the use case when there are items with a significant number of bands (~100), but all assets related to this item have the same band specs; with the current spec it will force the eo:bands duplication across all assets of a particular item.
i.e. to allow smth like that:
{
  "type": "Feature",
  // ...
  "assets": {
    "tiff_0": {
      "href": "http://fancy.tiff",
      "roles": [
        "data"
      ],
      "type": "image/tiff; application=geotiff; profile=cloud-optimized"
    },
    // ...
     "tiff_10": {
      "href": "http://fancy10.tiff",
      "roles": [
        "data"
      ],
      "type": "image/tiff; application=geotiff; profile=cloud-optimized"
    }
  },
  "properties": {
    //...
    "eo:bands": [
      {
        "name": "1",
        "center_wavelength": 0.3659136593
      },
      // ...
      {
        "name": "100",
        "center_wavelength": 0.3659136593
      }
    ]
  }
}

Yes, this was done intentionally, but I'm also not a big fan of the union behavior if all assets have the same bands (which is not the case anymore if you add a thumbnail or metadata asset).

The new RFC for a new "bands" construct will allow this: https://github.com/radiantearth/stac-spec/discussions/1213


Godot doesn't support Mono Output devices

Godot version:
3.2
OS/device including version:
Any mono output device. In this case, specifically the WH1000XM3 bluetooth headphones in "Hands free AG Audio Mode".
Windows 10.
I'm not sure about other OSes.
Issue description:
When opening the Godot engine with a mono device as the default audio device I get the error "WASAPI: Unsupported number of channels: 1". I can see from the audio driver cpp files that this is intentional but I wonder why? If I've got a mono output device then surely other people must too, and wouldn't mono audio be the easiest to support?
If I run the game with this mono device then all audio is distorted to be pitched deeper than it is supposed to be. Presumably because Godot is assuming that the input device has two channels.
Steps to reproduce:
Clone the mic-record project from the Godot Demo Projects github repo and open it in the

"PulseAudio: Unsupported number of channels: 1"

It's weird as the case where you have only one channel is explicitly handled in the Pulseaudio driver, it should not print this warning.
https://github.com/godotengine/godot/blob/b0eca5828ccd3a5c07b77e82e567c45937de9056/drivers/pulseaudio/audio_driver_pulseaudio.cpp#L158-L183
Apart from that yes, support for Mono should be added in the various drivers. The engine (AudioServer) can keep processing audio as stereo, and the AudioDriver can average left and right to generate mono output for mono devices.

Ah, that's my bad.
I've only run my code on Windows so far. I checked the other AudioDriver implementations to check whether they were set up in the same way and it looked like they were but I think I might've been looking at an old commit.
I'll modify the issue.

Confimed by someone on Godot Forums: https://godotforums.org/discussion/25713/wasapi-channel-number-causes-audio-gliches#latest

Can also confirm this for another Sony WH1000XM3, for the Sony WF1000XM3, Sennheiser HD350BT, and the Steelseries Arctic and another Steelseries Arctic Pro. All on Windows 10.
As far as I can tell, this issue basically breaks audio for everyone using a bluetooth headset and voice chat, because bluetooth (at least in pretty much all hardware/stacks available atm) doesn't support stereo playback + microphone, so they require you to switch to a non-stereo setting to use that, or do it automatically. A few of our testers hadn't even realized their headset was set to mono. Might become a bit of a support problem, since that's a lot of people.

I have this warning coming up too for my Sony H.ear too, but only in Hands-Free AG Audio mode, which is basically the mode when using the microphone.

I can confirm this is still the case on Windows 10 with 4.0beta17. Is the "interleave left-right" suggestion in https://github.com/godotengine/godot/issues/39065#issuecomment-634651829 still seen as an acceptable solution? If so, would you prefer a PR based on master for this, or rather a 3.x one?

Is the "interleave left-right" suggestion in https://github.com/godotengine/godot/issues/39065#issuecomment-634651829 still seen as an acceptable solution

Sounds good to me (no pun intended) :slightly_smiling_face:

It seems very closely related to https://github.com/godotengine/godot/issues/25875 at least in my case.
I have reports that both mono devices as well as 7.1 headsets have the same symptoms of severely distorted audio.
In my case it is reproducible by connecting a wireless headset with "Hands-free" capability to Windows machine and trying to play any audio through from the engine. It doesn't even have to be in-game - imported audio files (wav/ogg) are distorted as well.
A common workaround I've seen is to disable "Hands-free" mode and use the headset purel as headphones, but my app features a voice chat so I need both to work on the same device.
Discord and Telegram seem to be handling this just fine, so there's likely something wrong with either WASAPI middleware Godot is using or Audio/AudioServer itself.
For my Godot 3.5.2 project I'm currently working around this by installing 3rd-party software that allows me to remap audio devices and expose them to Godot.
This works, but isn't really user-friendly, especially when said users have other VOIP apps (such as aforementioned Discord and Telegram) working just fine.
Hopefully this message would be helpful, I do not currently posses the knowledge to decipher the way audio works in Godot ^^

Duplicate of https://github.com/godotengine/godot/issues/25875.


AWS extended support pricing for old RDS

Is your feature request related to a problem? Please describe.
AWS increases pricing for RDS when using old mysql or postgreSQL DBs.
Describe the solution you'd like
Find the resources with old RDS in the AWS account and suggest an upgrade.
Describe alternatives you've considered
No real laternative .... finding the RDS yourself
Additional context
Here the issue is discribed: https://medium.com/@totoshko88/prevent-automatic-rds-extended-support-charges-for-unsupported-versions-deed0ba3f51f

Hello @khushboo9024 ,
do you have any questions regarding this issue, please let me know.
Can you give me the status on this or when you are expecting to have this done?
Best
Jo

Hi @joscheuerer, sorry for being silent on this. We will add this to our priority list and let you know if we have any questions about it. We will try to release it as soon as possible.
Thanks!!

Thank you for the update!
Am Mi., 13. März 2024 um 08:12 Uhr schrieb Khushboo <
@.***>:

Hi @joscheuerer https://github.com/joscheuerer, sorry for being silent
on this. We will add this to our priority list and let you know if we have
any questions about it. We will try to release it as soon as possible.
Thanks!!
—
Reply to this email directly, view it on GitHub
https://github.com/turbot/steampipe-mod-aws-thrifty/issues/170#issuecomment-1993704598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVACJVHKJZHQBPGRYHVTYRDYX734BAVCNFSM6AAAAABCMC2RJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTG4YDINJZHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi joscheuerer, we have added a control rds_mysql_postresql_db_no_unsupported_version for this and pushed the changes to the branch. Can you check and let us know if it's good from your side? Thanks!"

Hi Khushboo,
one question regarding the versioning. Is the mysql version that is checked
via the API related to the 'community version' (5.7) or the Aurora mysql
version (2)?
This table shows both:
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html#Aurora.VersionPolicy.MajorVersions
Not sure what you get back from the API , but were you able to test this?
All the best
Jo
Am Di., 19. März 2024 um 08:13 Uhr schrieb Khushboo <
@.***>:

Hi joscheuerer https://github.com/joscheuerer, we have added a control
rds_mysql_postresql_db_no_unsupported_version for this and pushed the
changes to the branch
https://github.com/turbot/steampipe-mod-aws-thrifty/tree/issue-170. Can
you check and let us know if it's good from your side? Thanks!"
—
Reply to this email directly, view it on GitHub
https://github.com/turbot/steampipe-mod-aws-thrifty/issues/170#issuecomment-2006044036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVACJVE2KQXRFLRNJFAIT2DYY7QRZAVCNFSM6AAAAABCMC2RJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBWGA2DIMBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi joscheuerer, we've conducted tests on both the MySQL Community Edition and the Aurora MySQL database instance. The new query verifies both the MySQL Community Edition (version 5.7) and the Aurora MySQL version (2).
Here are the API responses indicating the versions for both database instance types:

MySql community version' (5.7.44 ) - 5.7.44
Aurora MySql version (2) - 5.7.mysql_aurora.2.11.4

Please let us know If any concerns.
Thanks!!

Thank you for the update.
That sounds all great.
Please let me know once it is merged to main.
All the best
Jo
Am Mi., 27. März 2024 um 08:22 Uhr schrieb Khushboo <
@.***>:

Hi joscheuerer https://github.com/joscheuerer, we've conducted tests on
both the MySQL Community Edition and the Aurora MySQL database instance.
The new query verifies both the MySQL Community Edition (version 5.7) and
the Aurora MySQL version (2).
Here are the API responses indicating the versions for both database
instance types:

MySql community version' (5.7.44 ) - 5.7.44
Aurora MySql version (2) - 5.7.mysql_aurora.2.11.4

Please let us know If any concerns.
Thanks!!
—
Reply to this email directly, view it on GitHub
https://github.com/turbot/steampipe-mod-aws-thrifty/issues/170#issuecomment-2022110408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVACJVBLVS3PIDKP3UU7I7DY2JXUDAVCNFSM6AAAAABCMC2RJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRSGEYTANBQHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Model params and flops

📚 Documentation Improvement
Benchmarks only shows inference time on gpu, but the parameters and flops of model really matters.

Agreed.
In the meantime, if you are interested in this information, you can usetorchinfo and get a model summary showing the number of parameters and flops.

I respectfully disagree. Number of parameters and FLOPs actually matters much less than inference time since latency is the absolute measure of how fast model is. And FLOPs is just a proxy for this and number of parameters is even weaker proxy.
As @harpreetsahota204 pointed out you can use torchinfo, since we do not provide mechanism to compute the FLOPS. As for parameters count you can compute it with one line of code:
    model = models.get(Models.YOLO_NAS_S, pretrained_weights="coco")
    trainable_parameters = sum([p.numel() for p in model.parameters() if p.requires_grad])


Add compose() method

Fixes #28

Looks like I need to rebase these for PSR-4 changes.

This one is ready now.

I don't know why Scrutinizer failed...


Abstract dependency and test execution with Makefile

Abstract the runtests script with a makefile, and update travis tests
to use makefile abstraction.
Not sure if the project is friendly towards gmake or not, but if it is
I can re-write the runtests script for make, or leave as is. Or
remove the makefile altogether, I just found it easier and more friendly
to use :)

Test failure is only with Go1.2.2:
go get github.com/urfave/gfmrun/...
# github.com/Sirupsen/logrus
../../Sirupsen/logrus/logger.go:32: undefined: sync.Pool
make: *** [deps] Error 2

It's not you!  https://travis-ci.org/urfave/cli/jobs/154239768
I think this means that, at the very least, we can't run the gfmrun bits on 1.2.x, which I can tackle on master.

Addressing 1.2.x failure via #510

@grubernaut merging/rebasing from master outta do ya! 😻

@meatballhat Updated! <3

@grubernaut one more push?  Looks like that last one didn't make it to Travis 😐

re-kicking through the tubes