app transport security problems on iOS 9

app transport security prevents PFFile.getData() from working on iOS 9
Hi there, I'm using the Parse SDK on iOS 9, and I'm running into issues while downloading PFFiles. This started sometime yesterday, without any code changes. Here is the error log output:
[Error]: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection. (Code: 100, Version: 1.8.2)
2015-12-26 10:25:57.652 ephemera[1238:298230] [Error]: Network connection failed. Making attempt 1 after sleeping for 1.011460 seconds.

It comes in repeatedly, as Parse continues to make more attempts to download the file. Here is a code snippet:
//posts is an array of PFObjects
posts.forEach {
  if let data = $0.getData(), type = $0.postType {
    //omitted
  }
}

here is a URL. Note that it begins with http:// and not https://.

Hey @prehistoricindustries, thanks for the report.
Is there any chance you can try more up-to-date version of our SDK?
We officially support iOS 9, including App Transport Security starting from 1.8.3.
Taking into account that you are running 1.8.2 - I believe purely updating to the latest version is going to resolve this.

Sure, I'll give that a try. However, this did pique my interest a bit. I've been using 1.8.2 for a little while now, and I only started getting problems yesterday. Was this a change in the Parse backend? I'm only asking because I was very impressed with Parse's support for iOS 9 and App Transport Security since day 1. I had never seen this error before.

It is strange, indeed, since you should have been hitting that long before.
Here is a pull request that implements https for files - https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/pull/197
Please note that it's marked with 1.8.3 milestone, meaning that it shouldn't have worked on 1.8.2.
Let me know if it works for you now, or please reopen this issue if it doesn't.

Updated to the new SDK, everything works perfectly. Thank you.


Redis start fails due to 'protected-mode yes'

Apr 21 06:27:15 netbox systemd[1]: Starting redis_6379.service - Advanced key-value store...
Apr 21 06:27:15 netbox redis-server[10661]: *** FATAL CONFIG FILE ERROR ***
Apr 21 06:27:15 netbox redis-server[10661]: Reading the configuration file, at line 7
Apr 21 06:27:15 netbox redis-server[10661]: >>> 'protected-mode yes'
Apr 21 06:27:15 netbox redis-server[10661]: Bad directive or wrong number of arguments
Apr 21 06:27:15 netbox systemd[1]: redis_6379.service: Control process exited, code=exited, status=1/FAILURE
Apr 21 06:27:15 netbox systemd[1]: redis_6379.service: Failed with result 'exit-code'.
Apr 21 06:27:15 netbox systemd[1]: Failed to start redis_6379.service - Advanced key-value store.

Tested using 1.2.11 on Fedora37.
Removing the options allows the service to start.

Did you change the redis_version variable? The default is a very old version not supporting this param.

I do no longer have the playbooks around, but AFAIR I did change the version. I just took the defaults at first, but then tried a newer version and also got that error.
Anyway, updating the default version to something current would be a good idea, wouldn't it?

Issue still persists, looks like the earliest version to support this is 4.0-rc1, the commit is https://github.com/redis/redis/commit/edd4d555df57dc84265fdfb4ef59a4678832f6da
I'll test if 4.0-rc1 still works with this repo.
I would suggest simply updating the default redis version to 4.0-rc1, would this be a viable fix?


[visual-studio-code-recent-projects] Allow reuse-window

Extension
https://www.raycast.com/thomas/visual-studio-code
Description
Currently, when you open a new project from the extension, it opens in a new window. It could be really useful for people working with tabs, to allow to open it in a new tab, or even better, have an option somewhere to change the default open behaviour to new tab instead of new window.
The CLI command to open in tab instead of window is docummented here:
https://code.visualstudio.com/docs/editor/command-line
under the --reuse-window CLI flag
Who will benefit from this feature?
All users that want more customization.
Anything else?
No response

Right now the extension doesn't use the CLI. We could consider bundling the CLI and add an option or secondary option for this behavior.

@vlaraort do you want to contribute to the extension?


Separate distance and duration matrices

Adds support for separate distance and duration matrices. This PR:

[x] Closes #184, closes #60;
[x] Adds and passes relevant tests.
[x] Has well-formatted code and documentation.

Notes:

It is essential that you add a test when making code changes.
This keeps the code coverage level up, and helps ensure the changes work as intended.
When fixing a bug, you must add a test that would produce the bug in the master branch, and then show that it is fixed with the new code.
New code additions must be well formatted. Changes should pass the pre-commit workflow, which you can set up locally using pre-commit.
Docstring additions must render correctly, including escapes and LaTeX.

A bit of a work in progress.

Codecov Report
Patch coverage: 66.66% and project coverage change: -0.05 :warning:

Comparison is base (f9f844f) 93.77% compared to head (ee640e5) 93.73%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #209      +/-   ##
==========================================
- Coverage   93.77%   93.73%   -0.05%
==========================================
  Files          62       62
  Lines        2122     2124       +2
  Branches      181      181
==========================================
+ Hits         1990     1991       +1
- Misses         84       85       +1
  Partials       48       48

Impacted Files
Coverage Δ

pyvrp/cpp/ProblemData.h
100.00% <ø> (ø)

pyvrp/read.py
95.16% <ø> (ø)

pyvrp/cpp/ProblemData.cpp
95.23% <66.66%> (-4.77%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

OK, I think content-wise we're mostly there. I still need to write tests, but I'll do that tomorrow I think.

@wouterkool @leonlan I think this is ready for review. The number of tests is somewhat small, but they do cover the main points. Let me know what you think!

Only comment I have regards naming: compared to dist vs distance, I think dur is less self-explanatory than duration, which was what we previously implemented and discussed about here.

Done. Also resolved several cases where we were already using time, dur for this.

Also, to avoid things like legDuration = duration() would it be an idea to refer to the duration matrix as durationMatrix/durationMat/durMat rather than duration (same for distance matrix?)? It's just a suggestion, I'm fine keeping it as is.

Can't really be helped; duration is a data member of TimeWindowSegment, so we need a different name regardless. I have renamed the dur argument to durationMatrix.


cli: add 'dir' attribute for steps

allow a step to specify the working dir where it should run. For example:
steps:

- uses: docker://alpine:3.11
  dir: /etc/
  args: ['pwd']

and the above should show /etc instead of the default which is /workspace.
Three things that need to be done:

[ ] the YAML spec needs to be updated so a new dir attribute is valid
[ ] a new test for this can be added in the cli/test/test_parser.py.
[ ] document this feature in the Workflow Syntax and the CLI Features sections.

Can I do this issue?

Please go ahead! Let us know if you have any questions
On Sun, Jun 7, 2020, 20:40 Ricardo Holguin<EMAIL_ADDRESS>wrote:

Can I do this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/getpopper/popper/issues/847#issuecomment-640345977,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADTQHKW457M3SYQNIOWWFTRVRMUPANCNFSM4NTA6YAA
.

Hi @ivotron, I already submitted a PR #853 but I should point out that I found an problem in my implementation to solve this issue.
If I define dir as /etc/ and if the container uses a curl, this will throw the following error
curl: (77) error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none

How to recreate this error
Using the following workflow will trigger this error
steps:
- id: download CSV file with data on global CO2 emissions
  uses: docker://byrnedo/alpine-curl:0.1.8
  args: [-LO, https://github.com/datasets/co2-fossil-global/raw/master/global.csv]
  dir: /tmp/

Expected result
A clean download of the csv file that has the url that was passed in the arguments for the step.
Where I could trace this error comes from is from the file runner_host.py in the function run from the DockerRunner class.
I have some idea why this is happening but I don't know for sure and I couldn't be able to fix it.


Catch up with renaming Naming/UncommunicativeMethodParamName to Naming/MethodParameterName

Why?
I happened to fork it, and came accross the Rubocop error.
So, I revised it.
Error was:
Error: The `Naming/UncommunicativeMethodParamName` cop has been renamed to `Naming/MethodParameterName`.
(obsolete configuration found in .rubocop.yml, please update it)

See also:

https://github.com/rubocop-hq/rubocop/commit/3947ce4e913ca1a71f6d7e5effb8042a5f2f9769#diff-3366e6e13a7a00d8b343860e694c13af

Thank you for your review. May I or would you merge this?

Yep. merged.
Thanks your contribution.


update migration guide (en) to include shouldUnregister

I wasn't sure on the ordering so I just put it on the bottom.
Open to any suggestions on verbiage

thank you!


Fixes #11764: Update minor version of java dependency library

https://www.rudder-project.org/redmine/issues/11764

OK, merging this PR


Add floating ip

New How To doc

Can merge at any time
Approved by Casey

Deploy preview for calico ready!
Built with commit 243010eb9d005c8530b94fc5a168e2105486cab0
https://deploy-preview-2773--calico.netlify.com


Add license headers to source files

The text of the Apache license says that to apply it to code, the code should carry a license header. The files in /library don't, so it's unclear what the copyright situation is.

Fixed with https://github.com/tnorbye/kdoc-formatter/commit/b5bff83a647e6198d198dbcf84e9e273a37d8c90

Thanks!


When pop_call_stack=true, call_stack.len() is always equal 1

What command(s) is the bug in?
No response
Describe the bug
https://github.com/scroll-tech/zkevm-circuits/blob/c2c5ecc8d58ac4568dc8365caa8d018a3c2f3135/bus-mapping/src/circuit_input_builder/access.rs#L273C1-L274C1
When pop_call_stack=true, call_stack.len() is always equal 1, so, when pop_call_stack=true, it will keep throwing exceptions? (I am just starting to understand this code. Please ignore if I am mistaken.)
Concrete steps to reproduce the bug. If it's able reproduce via testool, please share test_id from jenkins report
No response

there should be at least one call_stack (to, CodeSource::Address(to)) or (address, CodeSource::Tx).  So it should notpop when there is only one call_stack.


Fix graph conversion service

Add only nodes present in (attrEdge list) when converting to graphML file.  Suggest that this is really a global change.

@willgray: Can you post an example graph?

FYI.
Best,
Will
On Wed, May 27, 2015 at 6:10 PM, Disa Mhembere<EMAIL_ADDRESS>wrote:

@willgray https://github.com/willgray: Can you post an example graph?
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/m2g/issues/66#issuecomment-106094014.

Each vertex is now attributed with a vid attribute that is the vertex id from the incoming attredge graph.


SUGGESTION Skelet-ESP

drawing lines of where the bones are (arms, legs etc)

nice suggestion

I dont know how it will help this in game but anyway.


What is the requirements of the entry_point needed by the mxnet if I want to inference only

As the title mention, this drive me crazy.  What I want to do is

Create an endpoint to predict the image type based on the mxnet
Call the endpoint by lambda function(not sure doable or not)

About entry_point--I cannot find any document mentioned what kind of functions needed by this file, how should I define them,  all I could find are scrap data and use my instinct to do some test.
the entry_point--mxnet_imagenet_classify.py
from __future__ import print_function

import bisect
import json
import logging
import time
import random
import re
from collections import Counter, namedtuple
from itertools import chain, islice

import mxnet as mx
import mxnet.contrib.onnx as onnx_mxnet
import numpy as np
from mxnet import gluon, autograd, nd
from mxnet.io import DataIter, DataBatch, DataDesc
from mxnet.gluon import nn

logging.basicConfig(level=logging.DEBUG)

def model_fn(model_dir):
    """
    Load the onnx model. Called once when hosting service starts.
    :param: model_dir The directory where model files are stored.
    :return: a model
    """
    sym, arg_params, aux_params = onnx_mxnet.import_model('{}/resnet101v1.onnx'.format(model_dir))
    # create module
    mod = mx.mod.Module(symbol=sym, context=mx.cpu(), label_names=None)
    mod.bind(for_training=False, data_shapes=[('data', (1,3,224,224))],
             label_shapes=mod._label_shapes)
    mod.set_params(arg_params, aux_params, allow_missing=True)
    return mod

def transform_fn(mod, data, input_content_type, output_content_type):

    input_data = json.loads(data)
    batch = namedtuple('Batch', ['data'])
    mod.forward(batch([mx.nd.array(input_data)]))

    prob = mod.get_outputs()[0].asnumpy()
    # print the top-5
    prob = np.squeeze(prob)
    a = np.argsort(prob)[::-1]
    result = {}
    for i in a[0:5]:
        result[i] = prob[i]

    return json.dumps(result), output_content_type

Create endpoint
from sagemaker import get_execution_role

role = get_execution_role()

import tarfile
import boto3

from sagemaker.session import Session

with tarfile.open('onnx_model.tar.gz', mode='w:gz') as archive:
    archive.add('resnet101v1.onnx')

bucket_name='sagemaker-gluoncv' # put your s3 bucket name here, and create s3 bucket
role = get_execution_role()
region = boto3.Session().region_name
prefix = 'image_classify'
# customize to your bucket where you have stored the data
bucket_path = 'https://s3-{}.amazonaws.com/{}'.format(region, bucket_name)

def write_to_s3(filename, bucket_name, key):
    content = open(filename, 'rb')
    s3 = boto3.client('s3')
    s3.put_object(
       Bucket=bucket_name,
       Key=key,
       Body=content
    )

write_to_s3('onnx_model.tar.gz', bucket_name, "image_classify/{}".format('onnx_model.tar.gz'))

from sagemaker.mxnet import MXNetModel

mxnet_model = MXNetModel(model_data='s3://sagemaker-gluoncv/image_classify/onnx_model.tar.gz',
                         entry_point='mxnet_imagenet_classify.py',
                         role=role,
                         py_version='py3',
                         framework_version='1.3.0')

%%time

predictor = mxnet_model.deploy(initial_instance_count=1, instance_type='ml.t2.medium')

And then the server always give me error messages:
ValueError: Error hosting endpoint sagemaker-mxnet-2019-06-18-02-01-03-704: Failed Reason: Request to service failed. Please contact customer support.
Very confuse, reading what is docker and try to create a docker container, since I can't find an easy way to make things work

@stereomatchingkiss - You can follow the instructions here - https://sagemaker.readthedocs.io/en/stable/using_mxnet.html#working-with-existing-model-data-and-training-jobs
Here is the instructions on how to construct the entry point file - https://sagemaker.readthedocs.io/en/stable/using_mxnet.html#the-sagemaker-mxnet-model-server

Thanks, I read some posts about sageMaker and ec2.
The conclusions I get are

EC2 is cheaper
SageMaker is run on top of EC2, all it did is help you setup the environment needed by some machine learning task

Is this right? If it was, then SageMaker do not has much benefits for me

@stereomatchingkiss,

Based on the type of instances you are using and the type of services you want to utilize in SageMaker, the prices may vary
SageMaker trains and deploy your models on EC2 instance
SageMaker is a platform that you can easily handle the training, deploying, predicting, transforming etc. of your data and models. So yes, if you know what you need to do with your data, algorithm, models, you don't need SageMaker, but that means you don't use any AWS SageMaker resources.

Thank you


Custom Keyword Feature Offline Usage

Hi,
KWS feature does not require back-end services. Is it enough to have "Speech subscription" to use this feature. Is there any additional license/service fee?
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp#prerequisites
Prerequisites:
The steps in this article require a **Speech subscription**, and the Speech SDK.

https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-keyword-basics?pivots=programming-language-csharp#use-a-keyword-model-with-the-sdk
Note:
The example shown here uses local keyword recognition,
since it does not require a SpeechConfig object for authentication context,
and **does not contact the back-end**. However,
you can run both keyword recognition and verification utilizing a continuous back-end connection.

@webfolderio You need a subscription to create keyword model (.table file). Once you have the keyword model, using Speech SDK's KeywordRecognizer alone does not require subscription/connection to the online service.


[starter-kits] Fix starter kits so npm run serve isn't npm run docs:serve

Context
Currently you cannot serve your component from the starter kit. You always get the generated docs.
 Docs are still available via the nom run docs:serve command.
Currently: npm run serve and npm run docs:serve give you the same output.
Why
Because it's confusing and has resulted in the following efforts to fix:

https://github.com/lit/lit-element-starter-ts/issues/58

In the linked video: https://www.youtube.com/watch?v=86tet76u0uk&ab_channel=MiklosNemeth , they are unable to figure out how to serve their component. This is fixed by this change.

This PR on the original repo: https://github.com/lit/lit-element-starter-ts/pull/57 fixes the serve command explicitly.

Repro bug

Make a new template based on the starter kit.
npm i
npm run build
npm run serve -> get docs page.
Follow instructions in readme and navigate to /dev/index.html and get a 404.

Impact
Fixes serve command so it matches what expectation is set in the readme. Following links in readme, i.e. /dev/index.html return your component instead of 200.

This required a little more work mostly to guide folks in the right direction.
Previous behavior. npm run serve served the docs directory. The result is that you can never get to your /dev/index.html demo. You are instead siloed to docs.
New behavior: npm run serve serves the root directory. This allows for the /dev/index.html route to be available and work. And it correctly shows an incrementor with the slotted content.
However the pitfall of the new behavior is that web/dev-server prompts you to navigate to localhost:8000/ which is a 404. As very light guidance, I've added an html file that links to the demo, rather than having a 404 experience.
@justinfagnani PTAL at new changes. I manually tested all the build rules. Thank you!

Looks good. Still need a changeset though.

Done. Thank you.

Can you please also follow up on the TS and JS issues. There seem to be other issues that seem to be related.

I followed up on all the issues that seem related and will follow up again once this is released into those repos.


Classes removed without major version bump or deprecation notice

While upgrading com.getbouncer:cardscan-ui from 2.1.0020 to 2.1.0023 the build no longer works because of unresolved references:
Unresolved reference: CardScanActivityResult
Unresolved reference: CardScanActivityResultHandler
Unresolved reference: CardScanActivityResultHandler
Unresolved reference: warmUp
Unresolved reference: start
Unresolved reference: isScanResult
Unresolved reference: parseScanResult
'cardScanned' overrides nothing
Unresolved reference: CardScanActivityResult
'analyzerFailure' overrides nothing
'cameraError' overrides nothing
'canceledUnknown' overrides nothing
'enterManually' overrides nothing
'userCanceled' overrides nothing
Unresolved reference: CardScanActivityResult
Unresolved reference: CardScanActivityResult
Unresolved reference: CardScanActivityResult
Unresolved reference: CardScanActivityResult

These classes were removed without bumping the major version (which breaks semantic versioning, and was therefore unexpected https://semver.org/), and there were no deprecation notices in the code for the 2.1.0020 artifact.
Is there any sort of migration guide somewhere?
Thanks!

Apologies @caseykulm ! This code is currently migrating to Stripe infrastructure, and I missed this. You're correct this should have been a major version bump.
I'll update the git readme shortly with an integration example. It should be a relatively small change.
Apologies again!

All good, thanks for the response! Will check it out.

In the mean time, please take a look at the example app in this repo, which uses that interface.
https://github.com/getbouncer/cardscan-android/blob/master/cardscan-demo/src/main/java/com/getbouncer/cardscan/demo/LaunchActivity.java


Changes in ArbitraryGenerator

Description

Used 128 bytes of default buffer size vs 2^24 bytes buffer size earlier.
Used thread_rng to generate random number in each call as compared to using slices from pre-initialized huge buffer
Updated unit tests accordingly to work with new changes.

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[x] Refactor
[ ] New or updated tests
[ ] Dependency Update

Notes to Reviewers
Checklist

[x] I have performed a self-review of my code.
[x] I have commented my code where necessary.
[x] I have updated the documentation if needed.
[x] My changes do not introduce new warnings.
[ ] I have added tests that prove my changes are effective or that my feature works.
[x] New and existing tests pass with my changes.

Related Issues
STR-551

Another thing I just realized we could do is to allocate a large buffer for entropy (like 16M) upfront, but only write to it 1K at a time as requested by the type we're generating.  We'd have to screw around a little bit to make the lifetimes work but it'd be fine and safe.


Possible slow query warnings for meta queries have no whitelist flags

Possible slow query warnings for meta queries have no whitelist flags,
Should these be added?

@barryceelen Do you have a code example?

@barryceelen Historically the sniff only checked for tax queries, so it has the whitelist comment tax-query ok, but that should work for meta queries too.
https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Whitelisting-code-which-flags-errors#slow-taxonomy-queries
I'd like to suggest we deprecate (but still respect) the old whitelist comment and add a new one which better covers the sniff in the next version of WPCS.

@jrfnl I tried the tax-query ok flag, turns out I put it in the wrong place 😐…
Misread the sniff and figured the flag only worked for tax queries.
I’d be happy to create a pull request for a differently named flag. Any naming ideas?
slow query ok seems to imply the query is alway slow so seems a bit on the negative side to me.

slow query ok seems to imply the query is alway slow so seems a bit on the negative side to me.

Actually, if nobody has a better idea, that is actually reasonably consistent with our other sniffs. I mean, we have XSS ok after all. 😃

Yes, this should be added. It's annoing to have that error message.


Reverse displayName helper order to displayName || name

Hey, just a proposal on changing the order that displayName helpers in higher-order choose how to pick what the name of the Component is. Currently is is:
return Component.name || Component.displayName || 'Component';

This is normally fine when you have classes declared with the proper class names. However I'm actually passing an already wrapped class component that wouldn't have the .name set to anything specific, similar to how this is wrapping components. I am however setting the .displayName correctly on the component.
Looking at the mixin implementation of the displayName helper, it doesn't look like it would run into this issue.
Would it be possible to allow a PR or a change to reverse the order when finding the displayName for the new branched component to fix this?

Hello @basicdays. I don't remember exactly why but I think I chose this order initially because otherwise it was causing bugs on earlier versions of react. But I am not sure anymore. So I'll probably accept a PR. If you do so, can you however be sure to also check the mixin to see if something of the kind should also be done?

Awesome, yeah I can do an PR with the change. I'll double check the mixin as well.


Add rubocop

Hey @bensheldon. I think would be nice to add rubocop and tidy up the code. What do you think?

I think Rubocop would be a big improvement to working in the code... but the downside is that it will make finding the meaningful history of a slice of code more difficult.
But I think we may as well do it. What are your thoughts on changing the required Ruby version to a non-EOLed Ruby? (2.6 EOLs in 1 month....2.7 ?).  What kind of release should that get? (is a Minor release ok? It's sorta breaking change, but Bundler will guard against it; I sure hope people aren't still running Ruby 1.x)
https://github.com/assaf/vanity/blob/d61b2e1f8a003174c8c9183350374c9fd3f4de5b/vanity.gemspec#L24

@bensheldon
I think we can set to 2.7 as target version for rubocop.
Which required minimal version we should set do you think? I would suggest set required_ruby_version = ">= 2.5"  and stop supporting 1.9.3

Rubocop's target version needs to be set to the minimum required_ruby_version or else Rubocop may try to correct to a backward-incompatible feature (e.g. a Ruby 2.7-ism that doesn't work on 2.5).
I think required_ruby_version = ">= 2.5" sounds good.

Okay, got it


Add Date Range Selector for Connect Analaytics

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR enhances the ConnectAnalyticsDashboard component by adding a date range selection feature, allowing users to filter analytics data based on predefined or custom date ranges.
Detailed summary

Introduced DatePickerWithRange for date selection.
Added Filters component to manage date range presets.
Replaced useMemo for date calculations with useState for dynamic range updates.
Implemented getLastNDaysRange function to calculate date ranges.
Defined durationPresets for quick selection of date ranges.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4988  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


Merge Job Companies and Reviews REST API

Develop to Main: Merge Job Companies and Reviews REST API
Description:
This pull request merges the develop branch into the main branch, integrating the completed Job Companies and Reviews REST API. This API enables the management of companies, job listings, and reviews with a monolithic architecture. Key functionalities include creating, updating, and deleting companies, jobs, and reviews. The project follows modern development practices for scalability and maintainability.
Key Changes:

Added endpoints for managing companies, job listings, and reviews.
Utilized H2 Database for the database.

Testing:

API endpoints have been manually tested using Postman.

Merging the develop branch into the main branch to integrate the Job Companies and Reviews REST API, including endpoints for managing companies, job listings, and reviews.


Error loading ECLV(ECON) line type from VSDB files

mv_dev.txt
Lines with ECLV(ECON) line type from VSDB files are not in eclv tables.
Count comparison:
line_data_eclv        1339    83
line_data_eclv_pnt 24165  1557
File for testing:
met_data/ens_vsdb/2011070100/sref/sref_20141004.vsdb
line #1101
Expected Behavior
Both databases should have the same count
To Reproduce
Describe the steps to reproduce the behavior:
1. run query on both databases:
select * from line_data_eclv, line_data_eclv_pnt, data_file  where line_data_eclv.line_num=1101 and line_data_eclv.data_file_id=data_file.data_file_id and data_file.filename="sref_20141004.vsdb" and line_data_eclv.line_data_id=line_data_eclv_pnt.line_data_id
2. The result should be similar to the data from the attached file
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)

Projects and Milestone

[ ] Review projects and select relevant Repository and Organization ones
[ ] Select milestone

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdb, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above.
[ ] Fork this repository or create a branch of master_<Version>.
Branch name:  bugfix_<Issue Number>_master_<Version>_<Description>
[ ] Fix the bug and test your changes.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into master_<Version> and link the pull request to this issue.
Pull request: bugfix <Issue Number> master_<Version> <Description>
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the develop branch and link the pull request to this issue.
Branch name:  bugfix_<Issue Number>_develop_<Description>
Pull request: bugfix <Issue Number> develop <Description>
[ ] Close this issue.

This error was caused by having NA values in fcst_lead and obs_lead, which had not been seen before. Added code to convert these NA values to 0.
This revealed the issue that when there is an error in a batch of files, none of the files in that batch are loaded into the database. This is a more complicated issue to solve. Will add another issue for that.


[BUG] Space-evenly and :halign error

Checklist before submitting an issue

[x] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
when space-evenly is set to false in the box widget, the box's children can only align to start, even if children's :halign is set to "end".
Reproducing the issue
this is when space-evenly is set to true
...
(defwidget bar1 []
  (box
    :space-evenly true
    (box :halign "start"
      (workspaces :monitor 1)
    )
    (box :halign "end"
      (time)
    )
  )
)
...

And this is when space-evenly is set to false
...
(defwidget bar1 []
  (box
    :space-evenly false
    (box :halign "start"
      (workspaces :monitor 1)
    )
    (box :halign "end"
      (time)
    )
  )
)

...

Expected behaviour
the widgets should align as it is even if its parent box's space-evenly is set to false

You also can insert a separator, something like (box :hexpand true)
Thank you! :hexpand true solved this problem!
but I still wonder what hexpand do here. The eww doc says it "expand horizontally". I can confirm that it do not expand the size of the widget itself. Does it mean it add more space horizontally?


Fix import issues related to cocoapods.

Still working after modification.

Thanks !

You're welcome !


Adding support for improvement method (draft version)

Description
This PR is to make RL4CO support the improvement method for VRPs. The changes includes:

Add improvement env classes
Add improvement base, encoder, and decoder classes
Add improvement attention classes
Add positional encoding/embedding support
Add a new type of normalization method
ADD the N2S network and policy implementation
Minor changes to re-use the decoding strategy class
[To do] modify the PPO training part

Motivation and Context
This PR is to make RL4CO support the improvement methods.

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Remove all that do not apply:

[x] New feature (non-breaking change which adds core functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (update in the documentation)
[x] Example (update in the folder of examples)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.

Hi @cbhua @fedebotu , thank you so much for the review and great suggestions! I have replied above. Since last time I forgot to perform the pre-commit so I did a forced re-commit of the files. Sorry if it looks a bit hard to track the changes. I will perform new commits for future updates! :)

Hi @LTluttmann, thanks for the review! I have changed the codes in the latest commit!


fix requirement

Hey there! So you want to contribute to a Firebase SDK?
Before you file this pull request, please read these guidelines:
Discussion

Read the contribution guidelines (CONTRIBUTING.md).
If this has been discussed in an issue, make sure to link to the issue here.
If not, go file an issue about this before creating a pull request to discuss.

Testing

Make sure all existing tests in the repository pass after your change.
If you fixed a bug or added a feature, add a new test to cover your code.

API Changes

At this time we cannot accept changes that affect the public API.  If you'd like to help
us make Firebase APIs better, please propose your change in an issue so that we
can discuss it together.

Hi @tomosia-phuongvo, thank you for your contribution. We do not prefer to pin to specific versions of dependencies. Could you elaborate on this change if are running into any issues with the current configuration?


Update stable releases

Coverage decreased (-0.02%) to 36.965% when pulling ae8431ebaf018ae92fa628b64942a4de8546e1b8 on joestringer:submit/bump-1.6.9 into 04edb26b477c2816f7c4e6a29259a253c3f632ce on cilium:master.


Refactor Intro page to be compatible with Simulator Window.

Simulator window now handles changing of pages, as next and back buttons have been elevated to it. Also, the simulator window handles layout of page to be shown. Intro page needs to remove these buttons and be reformatted to be displayed properly.

Merged into seg-doge


[SR-2705][Sema] Always favor non-autoclosure parameter function overload on ranking

Implement a rule on ranking where overload choices that has @autoclosure parameters are disfavored over the ones that aren't to avoid ambiguity in situations like
func f<T>(_: () -> T) {}
func f<T>(_: @autoclosure () -> T) {}

f { } // ok

Resolves SR-2705.

@swift-ci Please smoke test

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test Linux platform

I think CSRanking might be too big of a hammer here, how about we either increment an existing score kind i.e. SK_FunctionConversion or add a new kind to use specifically for situations when closure is an argument for autoclosure coversion?

Thanks, I've updated and that indeed feels like a better solution :)

I think we should add a new ScoreKind at the end of the list though to make sure that it doesn’t interfere in ranking too much since SK_FunctionConversion seems too high of a priority for this...

That makes sense, changes done :)

@swift-ci Please smoke test

@swift-ci please test source compatibility debug

Windows is failing, that may started before that #36107 was merged, let's try again
@swift-ci Please test Windows Platform

Thanks @xedin!


overhauling inference picture to single script

Addresses #277 by making inference a single serial run across all files for a single shift. Includes a function infer which would fit into a more robust inference application down the line by parallelizing across all files and shifts.
Using TimeSeriesDicts for hdf5 I/O for the time being, which breaks with some of our existing infra but I think should simplify things, especially since the integration is wrapped into here anyway. I have also dropped normalization since recent results suggests it doesn't help much but this should be easy to add back in if we'd like to.
(Note that we can still keep an analysis project for re-integrating/normalizing/clustering already computed predictions using novel methods for doing any of those steps, but just not include it in the pinto pipeline).
Remaining questions:

[ ] Since we're doing integration here, do we just want to fit a ClusterDistribution in the callback and then aggregate them all in the main thread? I think this will probably make the most sense.
[ ] How do we fit in injections? Are they done alongside their corresponding background files (would be necessary if we were doing normalization), or do we assume that they will be handled by a separate job?
[ ] No mldatafind integration right now, so could be memory-limited for long segments. Would make the logic for shifting and concatenating batches across chunks more complex, but would probably be worth it longer term.

TODOs

[x] Test on a single shift value with server running ran on 0 lag background using latest production model, all raw and integrated outputs matched those from existing inference/analysis scripts exactly.
[ ] Rewrite tests

Fitting the ClusterDistributions makes sense since we already have all the info they need
Performing and analyzing the injections would fit nicely in infer, but would kill its generality for a larger inference application. The alternative would be to perform the injections in main, and then the fname argument of infer could be generalized to Optional[path, np.ndarray]. We could then either read the data from disk or pass it directly
We can keep what we currently do in the timeslide project, which is chunk segments if they are longer than a specified duration.

Most of the required infra is in there at this point. All that remains is:

[ ] Tests for all the new modules to verify functionality
[ ] events API in analysis library that gets imported here but doesn't exist yet
[ ] Integration with Ethan's condor code

This has become an enormous undertaking, but the pipeline is now working. The structure of the data directory is now:
train/
    background/
        background-<t0>-<duration>.h5
    glitches.h5
    waveforms.h5
test/
    background/
        background-<t0_0>-<duration_0>.h5
        background-<t0_1>-<duration_1>.h5
        ....
    waveforms.h5

Couple things to note:

Waveform generation is bottlenecked by dataloading within each client, and on aggregation of each client's results. This is not the end of the world since you only need to generate a new dataset once in a while (and hopefully we've nailed it such that it's a long while), but worth thinking about optimizing this down the line. Possibly moving all the data generation into a single step so they all run in parallel and the waveform generation can take advantage of a pre-comptued train background PSD (which will be way smaller than the segment needed to compute that PSD on each waveform generation job)
Viz app won't work with this new set up, but hopefully the new bbhnet.analysis.ledger.events API, and the removal of multiple normalizations, should only simplify the vizapp code. Given that we want to make a lot of adjustments to it anyway, maybe this is all better handled in a follow up PR.

I'm going to mark this as ready for review so that folks can begin taking a look and we can see which tests fail. I think the final list of to-dos is:

[ ] The num_injections is getting wildly inflated during event recovery: the number associated with the test waveforms.h5 is correct, but the one that ends up in foreground.h5 at the end of inference is a few orders of magnitude too high.
[ ] There will definitely be tests that I have forgotten to strip out for no-longer-existing modules, calls to tests in no-longer-existing libraries in the CI workflow that need to be removed, and whole projects like analysis that still need to be stripped out (and whose tests will likely fail).
[ ] I have given everything in here reasonably thorough eyeball tests: looking at the distributions of the masses of the test waveform injections, running through inference of a couple test segments and making sure that the data comes out right ( concatenated background matches the standalone file, injection - background comes out to clean waveforms) and that the recovered detection statistics and times and correct, but more extensive unit testing to verify everything will be important. I don't know that we need to be exhaustive before this gets in or before we start using it, but more than what's in there now is probably necessary.

For reviewers, this is enough of a behemoth that it might just be easier to go to the branch itself and peruse the code, since the diffs will be enormous and confusing. Would have been smart to handle this in smaller chunks, but things escalated as they tend to do.

I opened up a PR against your repo to address some issues. I noticed that a few of the ledger test were failing. Not sure If theres a commit or two missing here.


Update README.md

Minor fixes.

Coverage increased (+0.9%) to 67.455% when pulling 20aeb8b345d80a3ec8a3b5b181a0a6770602ada4 on pllim:patch-1 into 06dc2b9a6995cd3d1def407a53e7c2a439ab9328 on astropy:master.

Coverage increased (+0.9%) to 67.455% when pulling bdf273045c4cff9c0d753addf4a7a26dddf4b198 on pllim:patch-1 into 06dc2b9a6995cd3d1def407a53e7c2a439ab9328 on astropy:master.


sync terraform state to TFChain

should use the same format as the typescript client.
this is to be able to list and manage deployments and contracts through the client/weblets

Verified on devnet.
Terrafrom state is now synced with tfchain an the user is now able to check the details of any contract deployed from terraform through the Contracts tab in the grid weblets.
TF Playground (6).webm


Move test_disappearing_class to dedicated output base and disk cache dir

Description
Since test_disappearing_class checks bazel/scala caching I believe it is important to isolate builds from other tasks. Although I don't have a 100% proof but I think test is failing for some PRs because multiple tasks build same targets and write to same output/cache directories. This change fixed build for https://github.com/bazelbuild/rules_scala/pull/1071
Motivation
test_disappearing_class is failing for seemingly unrelated changes.
See PRs https://github.com/bazelbuild/rules_scala/pull/1071 and https://github.com/bazelbuild/rules_scala/pull/1080 as an example. Later one doesn't even touch any scala/starlark code.

Waiting for green checks


runtime and non-runtime testing queries.

Hi,
I  have couple of  questions.

Please explain the difference between runtime and non-runtime testing . can i test all algorithms in both modes ?

I am using openssl-1.0.2l-fips ( Built with openssl-1.0.2l + openssl-2.0.16(FOM)).
We have options:
--with-ssl-dir          location of OpenSSL install folder, defaults to
/usr/local/ssl
--with-fom-dir          Path to FOM install directory
i.  For runtime testing we have only  --with-ssl-dir  option available , if i give openssl-1.0.2l-fips path here  , does app uses openssl-1.0.2l fips  library for testing?  do i need to call FIPS_mode_set(1) in app_main.c to use FOM at runtime?
ii. For non -runtime testing we have both options available --with-ssl-dir  and --with-fom-dir .  For first option if i give openssl-1.0.2l-fips path and for --with-fom-dir  if i give  FOM install dir .  algorithm testing done on which library ?

Regards,
Nagarjun

Hello,
Some algorithms (e.g. DSA) are not able to be tested with the APIs available in openSSL. They need access to internal APIs which would not normally be available or allowed when running software. This is where non-runtime comes in. It links directly to the FOM to allow these algorithms to be tested.
If you use runtime mode, it will only let you test functions that are able to be tested without access to the internal APIs (e.g. SHA, AES). You would need to call FIPS_mode_set to use fips crypto - it will use openSSL crypto by default. Regardless, you will not have access to several algorithms.
Using non-runtime mode (configuring using --with-fom-dir), algorithms will be run using the FOM library crypto, and you will be able to test most of the algorithms libacvp supports. (there are still many algorithms that libacvp supports but openssl/openSSL FOM do not support - these do not appear in acvp_app).
Hope this helps,
Andrew

Hello,
Some algorithms (e.g. DSA) are not able to be tested with the APIs available in openSSL. They need access to internal APIs which would not normally be available or allowed when running software. This is where non-runtime comes in. It links directly to the FOM to allow these algorithms to be tested.
If you use runtime mode, it will only let you test functions that are able to be tested without access to the internal APIs (e.g. SHA, AES). You would need to call FIPS_mode_set to use fips crypto - it will use openSSL crypto by default. Regardless, you will not have access to several algorithms.
Using non-runtime mode (configuring using --with-fom-dir), algorithms will be run using the FOM library crypto, and you will be able to test most of the algorithms libacvp supports. (there are still many algorithms that libacvp supports but openssl/openSSL FOM do not support - these do not appear in acvp_app).
Hope this helps,
Andrew

Can i have list of algorithms can be tested at runtime and non-runtime?
What are internal APIs your are referring to can you give an example ?

The easiest way to locate the non-runtime algorithms is search the app/ and src/ directory for ACVP_NO_RUNTIME.
RSA key generation API requires exposing the random seed as part of the API which should never be done for production runtime code, rsa_generate_key_internal().

Hello,
As it seems the questions have been answered I will be closing this issue for now; please feel free to reopen if you have any more questions specific to this issue. Thanks!
Andrew


Add Label Support on Endpoint

It would be useful to be able to add more metadata to endpoints, like the canary value that's available on LbEndpoint in eds.proto. Kubernetes, DC/OS, and other systems support arbitrary labeling of instances, and making those available via EDS to be used in routing directives opens up a pretty wide range of nice use cases. If metadata were available on the endpoint, the canary attribute could be treated as a well known entry in the metadata map.

Yes I agree we should remove the specific canary flag and replace it with a generic set of labels.

We can have this take the same form as other metadata we tag listeners, filter chains, and routes with, e.g. https://github.com/lyft/envoy-api/blob/master/api/rds.proto#L229.

In this case I'm not sure if we want to use the Metadata struct, since we probably want to have a generic routing rule that would allow the load balancer to narrow load balanced hosts by label. So it might be better served as a list of strings. It's possible we could use the Metadata map and just ignore the opaque payload. Not sure. Needs some thinking.
Also, popping the stack, @mccv is asking for a way to narrow load balanced hosts by label. This is actually a bit different from what we have discussed in the past, which is that the management system would unpack the different "labels" into different clusters. There are pros/cons to both approaches.

Yeah, I think (correct me if I'm wrong) it's the danger of having a potentially huge number of overlapping clusters defined vs. making the routing rules more complex by allowing a route to constrain to a sub-cluster set of instances. That bit would require changes to the RDS for sure.
I think this change is less invasive. Using the existing metadata allows an EDS to inject scoped metadata. This in turn means that if there are well known Envoy labels (e.g. canary) you could define a namespace on the metadata that is reserved for well known fields.

Yeah, I think (correct me if I'm wrong) it's the danger of having a potentially huge number of overlapping clusters defined vs. making the routing rules more complex by allowing a route to constrain to a sub-cluster set of instances

Exactly. I don't want to pollute this issue with the load balancer discussion since there are use cases we know we already need to do with subsetting like forcing the load balancer to choose a canary. This is just a more general case of that. We can sort out the load balancer implementation issues separately.
For this change I think we just need to decide if we want to reuse the existing Metadata message vs. a plain list of label strings. I think the former is probably OK but I don't think the opaque data (values) would be used in the load balancer, just the keys. Which is fine.

I think the former is probably OK but I don't think the opaque data (values) would be used in the load balancer, just the keys. Which is fine.

@mattklein123 we definitely have use-cases where the load balancer would need both key and value for an endpoint label. We could jam {key}={value} in the key for this, but it seems like being able to handle a simple string Metadata message in the loadbalancer might be cleaner.
To give a concrete example, we might have several endpoints, each with version label keys, but with different values, and we'd want to route to a specific version. In this case, routing on the label key is insufficient.
I guess that can be hammered out later, I just want to make sure we don't preclude that use-case in making this change.

Sure sounds good. Let's just use the opaque metadata structure for now.

@htuch is this likely to be on your radar at all in the near term, or would it be helpful for us to put a PR together?

@9len Either way is good. I was planning on making a sweep of smaller API issues later this week to cleanup, so if you want to wait until then I can do it, PRs are welcomed though.

@mccv @mattklein123 Why would you want to cluster instances by label, in the router? For most common cases, you can handle that in the management plane, without the overhead of doing this at every router in the system.

@rshriram that is my general opinion, but I was hoping for a discussion. :)

(This response applies to both #81 and #91)
@rshriram I wouldn't say we feel super strongly about this, it mostly reflects an aesthetic desire to (1) keep the configs relatively compact and readable, and (2) push common complexity lower in the stack.
As @mattklein123 points out in #91, (1) probably matters less and less as configs become more consistently machine-written.
As for (2), If we're expecting to live in a world where there are potentially many implementations of the *DS APIs, my general preference is to reduce the net reinvention of the wheel.
Even if we don't end up routing by these labels per my proposal in #91, it's still useful I think to have this metadata potentially available to filters, for logging, etc.

+1 for having the metadata be available for logging/reporting.

+1 for having the metadata be available for logging/reporting.

Yes, having it at request time makes it much more straightforward to produce stats points dimentionalized by these labels. Otherwise you have to push the log lines through a system that can dereference the instances, which has some obvious race conditions.

@htuch we probably won't get to this in the next week, so happy to fold it into whatever sweep you do. thanks!

I think I'll go with Metadata here for the log/stats reasons above. Metadata is keyed by filter today, so I imagine we'd have a pseudo filter name for the LB, e.g. envoy.lb (and maybe real filter names if/when we have LB filters). Existing stats/logging mechanisms will be adapted to implement Metadata access in the near future, so this will work well there.


Feature/withdraw on chain

Of Note: Still needs to be styled
Description
Adds Withdraw functionality from off-chain defy
How to test
Should work with any staging account with defy.
MagicLink doesn't appear to have log in ability though.

Hey @TheMightyYak1, just a heads up that this project is configured to work with eslint and prettier.
Assuming you are using vscode, you can install and activate those plugins which will help to avoid all the formatting changes

ok I've updated it, should have reverted the formatting changes.
I'm not really sure how to format this part of it, for after the withdrawal. Ideally, both the text and button should be on new lines

ok I've updated it, should have reverted the formatting changes.
I'm not really sure how to format this part of it, for after the withdrawal. Ideally, both the text and button should be on new lines

@TheMightyYak1 - try updating the ModalFooter component to something like this
<ModalFooter flexDirection="column" gap={3}>

Looks to be working


Need to changed "custom loader" instead of "3 dot loader" for "Load on Confirm"

I want to add custom loader instead of 3 dot loader for Load on Confirm.
I mean I want to following loader

Instead of following

Is this possible?

I think you cannot since sweetalert doesn't offer such a customized feature


about the ./hmr2_training_data

Thanks for your excellent work, the download link in this file "https://github.com/shubham-goel/4D-Humans/blob/main/fetch_training_data.sh" can not open, could you please give me the file in ./hmr2_training_data

There is a limit to how many times the training data can be downloaded in a particular time frame. If the link doesn't work, it should be only temporarily.


rr aggregate route

Hello, everybody. When I used Calico bgpPeer, the route I saw for the exchange was:
<IP_ADDRESS>/24
<IP_ADDRESS>/24
<IP_ADDRESS>/24

Can RR be aggregated to <IP_ADDRESS>/16 and sent out?

I think that is not possible, distribution routes are random on Cluster: a Node can receive <IP_ADDRESS>/24 and other Node can receive <IP_ADDRESS>/24, so aggregating route does not work. Thats could be a border router function, summarizing all of then to an external gateway.

Calico will aggregate routes within a particular node, but it cannot control what downstream aggregation occurs at other points in the network.
You can use ip pool nodeSelectors to make sure that certain IP ranges are allocated to certain racks, for example, and then use aggregation at the ToR to represent the entire rack as a single route.
However, I don't think Calico itself can do any further aggregation - you wouldn't want a Calico node advertising a route that included pods that weren't actually running on that node.

Understand, thank you @gunboe


Closes #222 | Create dataset loader for CreoleRC

closes #222
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[x] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

Hi @zwenyu, to make the reviewing tidier, would you like to separate config changes into a different PR? (so you can be attributed for bonus points in introducing new tasks, too)

@sabilmakbar I've removed the config changes in constant.py to a separate PR #502.

@sabilmakbar Thanks for the comments. I've pushed changes addressing the issues. Can you check if they are ok?

@sabilmakbar Thanks for the comments. I've pushed changes addressing the issues. I didn't see error for normalized, using datasets version 2.17.1, but I've added normalized now. Can you check if they are ok?

Initially, I pointed to the missing field of normalized in the SEACrowd Schema of KB under the relations column, which is okay if being filled with an empty list. But since your new changes also fill them with appropriate values, it works (and even better)!


Added masked flag to getClaimChildrenByIdOrLastApproved

Updated table function to return masked LastName if 'masked' parameter is true, will return unedited LastName if flag is set to false
Required for https://github.com/ministryofjustice/apvs-external-web/issues/424

Closing, since the external web needs the ability to retrieve unmasked child details it makes more sense to add the masking to the application logic as it only adds complicity to put it in the DB layer not security.


Dismount on Course Join

Add a check to dismount the player when they join a Parkour course.

Fixed in latest commit.


Update AWS support message

Updating AWS support message reflecting vCPU usage as a limit for regions.

/assign @rira12621

On lines 1048-1049, caseLimitIncreaseBody is appended to caseCommunicationBody, but is no longer necessary.
Also, on line 1053, there is duplicate language in the appended message: "Once this is completed please resolve this case, do not set this case to Pending Customer Action."

/lgtm


How do you locate the MADT?

I am trying to locate the MADT, however it isn't showing up in the R/xSDT. How did you configure QEMU to give you the MADT? As a note, I do find an "APIC" table, but not an MADT.

Sorry, I'm dumb.


Task/aa 2361 link secondary improvements

Reworked in https://github.com/Spendesk/grapes-android/pull/154


Type annotations not working with bs namespace

if bs config contains namespace: true then type annotations are not shown

fix in v0.43


Upgrade Mac OS to Python 3.7, but no command can be found after installation.

As the title, I currently encounter the problem of not finding the command after installation, the installation process did not report an error, the screenshot is as follows：
￼

https://github.com/nbedos/termtosvg/issues/65

Thanks!


Need testing of https://test.pass.library.jhu.edu

We need some people to test the Test environment.  Any user who has an account in Demo should be able to test this as well.
Once this is done and confirmed, we can migrated Demo to the new deployment scheme.

I found an issue, in which the deposit agreement box is empty. NOt sure about the cause. this data comes from the repository object in fcrepo. i looked at the repository object itself, it seems to have the correct value. not sure why it's not showing up here. here's link to the object in fedora https://test.pass.library.jhu.edu/fcrepo/rest/repositories/41/96/0a/92/41960a92-d3f8-4616-86a6-9e9cadc1a269

Hanh,
Can you, maybe, explain briefly how ember gets this data?  Does it literally just contact fedora and grab the data?  Is there access to one of the UI developers who might be able to explain why this might be happening?
On Oct 31, 2018, at 1:50 PM, Hanh Vu <notifications<EMAIL_ADDRESS>wrote:
I found an issue, in which the deposit agreement box is empty. NOt sure about the cause. this data comes from the repository object in fcrepo. i looked at the repository object itself, it seems to have the correct value. not sure why it's not showing up here. here's link to the object in fedora https://test.pass.library.jhu.edu/fcrepo/rest/repositories/41/96/0a/92/41960a92-d3f8-4616-86a6-9e9cadc1a269
[screen shot 2018-10-31 at 1 33 03 pm]https://user-images.githubusercontent.com/11050142/47807167-cc812b80-dd11-11e8-93fb-d9d86dbd7641.png
This behavior does not exist in demo.
I was still able to submit the submission.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/OA-PASS/general-issues/issues/60#issuecomment-434780241, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAOgPSFqbdhWxVTrbPzg03-c7VQJXfvpks5uqeLLgaJpZM4YCrtw.

I’ll look into this with you today.
Hanh Vu
Project Manager, Data Conservancy
Sheridan Library, Johns Hopkins University
On Wed, Oct 31, 2018 at 5:36 PM -0400, "derekbelrose" <notifications<EMAIL_ADDRESS>wrote:
Hanh,
Can you, maybe, explain briefly how ember gets this data? Does it literally just contact fedora and grab the data? Is there access to one of the UI developers who might be able to explain why this might be happening?
On Oct 31, 2018, at 1:50 PM, Hanh Vu <notifications<EMAIL_ADDRESS>wrote:
I found an issue, in which the deposit agreement box is empty. NOt sure about the cause. this data comes from the repository object in fcrepo. i looked at the repository object itself, it seems to have the correct value. not sure why it's not showing up here. here's link to the object in fedora https://test.pass.library.jhu.edu/fcrepo/rest/repositories/41/96/0a/92/41960a92-d3f8-4616-86a6-9e9cadc1a269
[screen shot 2018-10-31 at 1 33 03 pm]https://user-images.githubusercontent.com/11050142/47807167-cc812b80-dd11-11e8-93fb-d9d86dbd7641.png
This behavior does not exist in demo.
I was still able to submit the submission.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/OA-PASS/general-issues/issues/60#issuecomment-434780241, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAOgPSFqbdhWxVTrbPzg03-c7VQJXfvpks5uqeLLgaJpZM4YCrtw.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/OA-PASS/general-issues/issues/60#issuecomment-434856337, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKicnqlmJhd324hffeiwCxrJZfIGPfPlks5uqhe_gaJpZM4YCrtw.

Ok to further complicate this issue,
If you don't use the 'abc' doi and, instead, leave it empty it populates that field in the Ember application.

Thanks @jrmartino.  At this point, I don't know where the ember application gets this deposit agreement. It's also confusing because it works if you don't specify a DOI.  Can we test with a different DOI?  Is that possible?

@derekbelrose i've tested with a variety of DOIs.
Here are a few you can try. any of the format works.
https://doi.org/10.1016/j.polymer.2013.10.051
https://doi.org/10.1016/j.polymer.2014.12.057
10.1039/C7SM01695F

There was a discrepancy between the versions of Ember and FCrepo running on Demo and Test.  I aligned those versions and updated the stack.
Hanh is testing again.

All manual tests seem to have passed.


Use a webframework instead of raw TCP

Looking at the server code, it seems that a big part of it (handling connections, encryption, reading from sockets) could be removed if you would use a web framework (such as rocket or actix).
This could improve code readability (less code, better structured), security/stability (replacing custom implementations with tested ones) and perhaps even performance. Also using a more standard way would make it easier to grasp what's going on and expand the functionalities.
What do you think? Or is there a reason why you chose to not use a web framework?

Initially I started using raw sockets because I've written code in the past using raw sockets.
Eventually we should probably switch to something like actix but right now I don't see a good reason for this switch (because it would require a lot of work). Current networking code is... done. Network messaging is implemented in the 'shared' crate and right now every crate of this project just uses functions like send_message or receive_message and adding new messages is as simple as adding a new entry to an enum.
I had some experience with actix for web servers in the past, should we use something like websockets or something else would be more appropriate here?

For a (relatively) simple performance improvement we could replace std with tokio which is async.
I'd argue that it's better to rewrite it sooner than later, because you have less code to rewrite and you won't write code that will be rewritten later.
But if you don't plan on changing/extending current network code, then this can wait.
Also I was thinking about a HTTP server, especially for reporting (because there you make a single request once in a while). For clients HTTP server should work too, because you don't really have a stream of data. But websockets should be fine too.

I'd argue that it's better to rewrite it sooner than later, because you have less code to rewrite and you won't write code that will be rewritten later.

Agreed, but I don't want to change something that works. Moreover even right now it would require a lot of time to rewrite this (the time that I don't and probably won't have in the future).
As I've said, eventually we should totally do this. But right now we have more important stuff to implement.
So I'm putting this issue on hold, until somebody will start implementing this.

Sure, that's reasonable.

@LoipesMas I got interested in Salvo, do you think this can fit our needs? We can then remove the client application to just have a web interface that the server provides.

So I just gave this a quick though and although I know that there are some great pros for using a web framework but wouldn't it require our users to spend money on SSL certificates? I only know some base information on the web topic so help me out here.
 Our current solution requires almost no effort to set everything up and it will be secured (relatively) enough. I mean this is not some bank management application, bug reports don't hold any sensitive information except maybe for the email addresses (if provided by the reporter).
Don't get me wrong, I would actually like to switch to some library that handles networking but only if it won't require our users to do some complicated setups or spend more money so help me out here.

hey @Flone-dnb
Maybe NATS fits the bill here...   Its tcp, has create rust and golang support. scales like nuts. have built in security if you want it.  It also supports web sockets as maybe thats needed.
tons of game developers use nats to btw.
https://github.com/nats-io/nats-server
golang client: https://github.com/nats-io/nats.go
rust client: https://github.com/nats-io/nats.rs
the NATS server can store the screenshots and data using nats objj store and kv store if you just want to keep things simple.
using the api is really easy i find from rust and golang.

@Flone-dnb with certbot, you can set up free and automatic certificates for your https server. This shouldn't be much harder than setting up the server itself.
But having a certificate wouldn't really be a requirement. As you said, it's not really sensitive information and the requests could be sent over http (without the s).
So considering how simple and standard using https would be, there's not a lot of reasons not to. But on the other hand, it's also not a high-priority thing.

@gedw99 You are right, NATS can actually be one of the solutions. Although I haven't used NATS myself, I know that some C++ game projects from my job use NATS. Unfortunately, I think NATS will be overkill for this project. I already wrote a very simple API for handling encrypted TCP messaging in the shared crate (including file transfer), it works fine and seems to not have any critical issues (although I think our file transfer or the fact that it does not use async will slow us down) now I'm just looking for a proper "battle-tested" simple / lightweight library for handing low-level TCP stuff for me.
@LoipesMas Hey thanks for the info, I didn't knew about certbot.

As you said, it's not really sensitive information and the requests could be sent over http (without the s).

I'm glad you can agree on this, although when I said:

I mean this is not some bank management application, bug reports don't hold any sensitive information

I meant that at least some (poor) encryption is required (we don't need super secured stuff here), moreover, I don't want to just throw away encryption that we currently have. I mean it's not perfect and probably has some security issues, but hey it's better that nothing. Additionally, although reports might not have much sensitive information, client login/passwords do have sensitive information. Imagine you are a developer and you want to check the report list, you connect to the server by sending there your login and password hash - I think this is sensitive information, sending this over HTTP is probably a bad idea.
So I think that we should at least stick with the web framework + certbot solution. Maybe we can detect if the server (built in the release mode) is started in the HTTP mode and just throw an error and don't start at all to prevent the users from shooting themselves in the foot. Yeah, this might work.
So OK, let's say our 2.0 goal is to:

rewrite the server to use salvo (because it seems to be super simple and I wanted to learn it :smile:)
eliminate the client application and just have a web interface that the server provides

Any thumbs up/down on this?

Web framework + certbot sounds good!
Haven't used salvo myself, but it should fit our needs.
Somewhere down the line you could consider selling servers as a service (setting up, maintenance, etc.), for those users who don't want to bother with that, in order to fund further development. But that's just a thought for now.


Add abstracted get initial monitor member function

To get monitor members feature will be reuse serval times in mon.py and osd.py.
Due to this reason, I rewrite the helper function for this feature.
If you have any questions, feel free to let me know.
Thanks!
Signed-off-by: Vicente Cheng<EMAIL_ADDRESS>

Can one of the admins OK this pull request so I can run a build?

ok to test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/ceph-deploy-pull-requests/1536/
Tests passed for this pull request.

@Vicente-Cheng nice work!
Thanks for sticking with this.  I know there were times where I was unresponsive for long periods of time.

@trhoden that's ok!!
I think I have learned much from you.
It's worth for sticking with this!!!!


Allow users to enroll from the product detail page

Depends on #4 and #32
Design (desktop): https://projects.invisionapp.com/d/main/#/console/21535972/455477372/preview
Design (mobile): https://projects.invisionapp.com/d/main/#/console/21535972/455488639/preview
Acceptance Criteria:

If the logged-in user has not enrolled in the upcoming run for the course, clicking "Enroll now" enrolls them in the course in edX and creates a local enrollment record
If the logged-in user has enrolled in the upcoming run for the course, the user is not able to click a button to initiate enrollment

To be decided:

UI for users that have already enrolled in the upcoming run for given course
UI for users that have already enrolled in a past run for given course
UX for success/failure (error messages, where they are displayed, what page to redirect to upon success if any, what alerts/notifications to display upon success if any)

Closed via #93


Fix parameter order of set person home/away methods

The incorrect order or parameters prevented passing in only the home id to set the whole home home/away.
Original HA issue: https://github.com/home-assistant/core/issues/51782

The sourcery refactoring is unrelated in my opinion.


One to One saving of data fails

The below graphql statement fails with error below for a one to one relationship.
savePost(input: {
    description: "hello",
    mediaFile: {type:video, uri: "hello"}
  }) {
    id
  }

CREATE TABLE IF NOT EXISTS mediaFile (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  uri VARCHAR(255) NOT NULL,
  type ENUM('video', 'image') NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
);

CREATE TABLE IF NOT EXISTS posts (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  mediaFileId INT,
  description VARCHAR(100) NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  FOREIGN KEY (mediaFileId) REFERENCES mediaFile(id)
);

Do I need to have both table having reference to each other?

Manage to sort out the issue by swapping the FOREIGN KEY CONSTRAINT
CREATE TABLE IF NOT EXISTS posts (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  description VARCHAR(100) NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
);

CREATE TABLE IF NOT EXISTS mediaFile (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  uri VARCHAR(255) NOT NULL,
  postId INT NOT NULL,
  type ENUM('video', 'image') NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  FOREIGN KEY (postId) REFERENCES posts(id),
  UNIQUE(postId)
);

Manage to sort out the issue by swapping the FOREIGN KEY CONSTRAINT
CREATE TABLE IF NOT EXISTS posts (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  description VARCHAR(100) NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
);

CREATE TABLE IF NOT EXISTS mediaFile (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  uri VARCHAR(255) NOT NULL,
  postId INT NOT NULL,
  type ENUM('video', 'image') NOT NULL,
  createdAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updatedAt TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  FOREIGN KEY (postId) REFERENCES posts(id),
  UNIQUE(postId)
);

Thanks for reporting! This looks like a bug
Just to clarify, the solution was to rename mediaFileId into postId?

What database are you been using?

@mcollina mysql, sorry issue is still there.

@mcollina What i have observed is that the first table being written is Posts table once the ID is returned that ID is passed to mediaFile as postId but mediaFile does not have postId

Discovered that issue was caused by me cause I extended the schema to include mediaFile in the input


useSelector() - changing redux state without useDispatch ???

What is the current behavior?
let data= useSelector((state:State) => state.data);
data = data.filter(/* filter data.... */)

above line actually changes the state. Not sure if it should. State should be change only via useDispatch.
Steps to Reproduce
let data= useSelector((state:State) => state.data);
data = data.filter(/* filter data.... */)

What is the expected behavior?
Redux state should be changed via dispatch actions only (??) If not, then useDispatch seems redundant in redux hooks.
Environment Details
"react-redux": "^7.2.0",
"redux": "^4.0.5",

In this situation actually you are not modify the state of store. the variable ‘data’ only a local variable, data = data.filter(...) only modify the local variable ‘data’ without the ‘data’ point object. so state of store is not be modify.
But in other way, redux cannot prevent user modify the data of production.

I'm not seeing how that particular code would modify anything. The data variable is local and non-referential, so it won't write back to the value in the store object by itself.
I would recommend looking into use Redux Toolkit, as it has an immutability library built-in (Immer) and can prevent these kinds of issues: https://redux-toolkit.js.org/

Yeah. That code shouldn't be causing any mutations as shown.  However, in general, the Redux core does nothing to prevent mutations.  Any reference to state is the actual value kept in the store, and if you mutate it, it's your bug :)  But, Redux Toolkit will throw errors by default if it detects mutations.

Thanks All, yeah I have to figure out what is wrong with my code. :)

Hi!
Could you share your error? I'm experiencing the same behavior.


Templatize E57Simple to support double coordinates

Hi,
The E57Format lib is overloaded to work with several coordinate types, yet the current E57Simple API only supports float coordinates.
Making the E57Simple Data3DPointsData struct a template enables the use of different types, such as double.
In order to keep the current behavior of the API, the default float template was typedefined using the previous Data3DPointsData name.
A new double version Data3DPointsData_d was also typedefined so that it can be used directly as well.
The intent behind this change is that the last official release of the E57Simple API was using double coordinates, and there are still some use-cases where this level of precision is needed.
This is especially the case when working on large scale scenes - such as we do here at Trimble - and this feature should provide more retro-compatibility to the API.
Regards,
Grégoire

Grégoire Jacquemin | Trimble
Software Development Engineer

Thanks! Looks good to me as well. Very nice way to support both float precisions.

Thanks! Looks good to me as well. Very nice way to support both float precisions.

Thanks @ptc-jhoerner.
And thank you @gjacquem for your first contribution! Much appreciated.

Thanks @ptc-jhoerner.
And thank you @gjacquem for your first contribution! Much appreciated.


QT: No matching signal for peer tool buttons

When running avian-qt this always appears in the debug.log:
GUI: QMetaObject::connectSlotsByName: No matching signal for on_addPeer_clicked()
GUI: QMetaObject::connectSlotsByName: No matching signal for on_removePeer_clicked()
GUI: QMetaObject::connectSlotsByName: No matching signal for on_testPeer_clicked()

However the buttons do indeed work without issue. Further testing is required for this.

Fixed in #96


Add Id to ImageResource mapper

fun idToImageResource(id: Int) = ImageResource.Builder()
       .setAndroidResourceByResId(
               AndroidImageResourceByResId.Builder()
                       .setResourceId(id)
                       .build()
       )
       .build()

From here:
https://github.com/joreilly/PeopleInSpace/pull/139/files#diff-4058974ed1ff8fbb817967ab294ee5a8b422543b015c50cf3481cc2fddffbe0cR119-R126
I'm using it for a component audit (in combination with LayoutPreview) but presumably it's handy for the tile renderer too.
Notes:

consider updating the param name to resourceId: String to match the Tiles naming.
I know some folks hate ext funs 😬 but... ImageResource.from(resourceId: String)?

I misread the function, but it's still useful to add (my notes are less useful 😂 )

+1 to DrawableRes.  Also as an extension function on Resources.Builder, it should show up magically inside the Preview blocks and so on.


fix to close call of a freedom manager

Small fix for close arguments of a FreedomModuleFactoryManager.
tested: grunt test

:+1:


New: jsx-curly-newline rule

fixes #1493
This rule is based on eslint core rule function-paren-newline. Its options is similar to that of function-paren-newline, array-bracket-newline,  and object-curly-newline. However there is one new option multiline-lax (default), which is the same as multiline but tolerate cases like
<div>
{
  foo
}
</div>

, that is, single line expressions are allowed to have both newlines.
Separately, since this commit is modified copy of the eslint core rule function-paren-newline.js, I need help on how to deal with the license things.

I forgot to add this rule to the README.

@golopot a followup PR would be great


[Firebase ML Vision] - Face detection and video recording running in parallel

Hi, I was wondering if there is any way to use the ML kit (face detection) in real-time while also running the video recording in parallel? After inspecting the camera module, it seems that it can only do one or the other, as ML kit takes a CameraImage argument inside .startImageStream() and a String path argument inside .startVideoRecording().
It would be helpful if it's possible to do both at the same time. I've been exploring other methods of recording the stream as well, via encoders such as FFmpeg to resolve the conflict of camera controllers but it suffered from performance issues. Any form of assistance would be deeply appreciated.

@ysrarff
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1156. Any further collaboration will be done there.


Wrong type for forceMount prop on DropdownMenu.Content

Bug report
Looks like type for forceMount is given as true  instead of boolean. Which breaks passing condition on this prop. Is this intentional?
<DropdownMenu.Content forceMount={a === b} /> // this give type error `Type 'boolean' is not assignable to type 'true'.`

https://github.com/radix-ui/primitives/blob/main/packages/react/menu/src/Menu.tsx#L238
Current Behavior

Expected behavior

Reproducible example
CodeSandbox Template
Suggested solution

Additional context

Your environment

Software
Name(s)
Version

Radix Package(s)

React
n/a

Browser

Assistive tech

Node
n/a

npm/yarn

Operating System

https://github.com/radix-ui/primitives/pull/1060#issuecomment-1004742028

Got it.


removed starwars from the list

because use the BRUTEforce you must.

Thanks for your help

The force, Brute will learn.

Use the force Brute.

<feeds-the-trolls>
The location is now Passwords/CommonCreds/10-million-password-list-top-10000.txt
...also missed various other ones: Passwords/CommonCreds/10-million-password-list-top-100*
</feeds-the-trolls>
Related troll: #170

I use at least 10000 of the common passwords.. can I remove them? C'mon guys (@cercia01)  ... if we remove all the known passwords this list will be garbage...

Agreed, this was super funny but we don't want to make our lists less effective in the name of humor.
Or at least not often.


Destructo autopromote lmt patch

This should satisfy the LMTs for the time being until they decide what they want.

Why do the LMT Trainers need to be able to add LMTs with a command? Does the normal process through # request-rank not work for them like it is doing for both regular trainers as well as SLRT?

They specifically requested to be removed from the feature, as they have a review board that takes place after the #request-rank messages are approved. This command eliminates the need for a Staff member to add the roles, which will make it easier for the LMT trainers to conduct 1-on-1 trainings, or trainings without Foxy present.

On May 18, 2021, at 15:22, hrolfurgylfa @.***> wrote:

Why do the LMT Trainers need to be able to add LMTs with a command? Does the normal process through # request-rank not work for them like it is doing for both regular trainers as well as SLRT?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.

After discussing it with Foxy, it should be fine to keep them in the feature, they just need some different requirements.
In particular the reviews after trainings only last on average 10-15 minutes, so by having the automatic bot deny time at 1 hour will be fine. Maybe two hours for some extra headroom just in case. This should be fine to be adjusted for everyone, I at least don't see an issue with that being a change for all teams.
After discussing that with her, it seems that it may also be good to add a detector that sees if an X emote is added and remove the request if it detects an X, the X wouldn't necessarily be on the message from the beginning, but that depends on how often a request has to be removed, and we need to talk to more trainers from different teams to get some information on that.
I'm thinking the best way forward is to revert the # request-rank change for now or disable it, and continue looking into it on a separate branch, and then not merge it into main until we show it to leaders of all training teams (LMT, SLRT, ...) and also probably a few extra staff members, just to make completely sure this change is fine, since it changes the # request-rank channel in a fairly big way.

I’ll look into it further this week

On May 18, 2021, at 16:31, hrolfurgylfa @.***> wrote:

After discussing it with Foxy, it should be fine to keep them in the feature, they just need some different requirements.
In particular the reviews after trainings only last on average 10-15 minutes, so by having the automatic bot deny time at 1 hour will be fine. Maybe two hours for some extra headroom just in case. This should be fine to be adjusted for everyone, I at least don't see an issue with that being a change for all teams.
After discussing that with her, it seems that it may also be good to add a detector that sees if an X emote is added and remove the request if it detects an X, the X wouldn't necessarily be on the message from the beginning, but that depends on how often a request has to be removed, and we need to talk to more trainers from different teams to get some information on that.
I'm thinking the best way forward is to revert the # request-rank change for now or disable it, and continue looking into it on a separate branch, and then not merge it into main until we show it to leaders of all training teams (LMT, SLRT, ...) and also probably a few extra staff members, just to make completely sure this change is fine, since it changes the # request-rank channel in a fairly big way.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@hrolfurgylfa Here's the update:

Readded LMTs to requestables
Increased timeout to 2 hours default
Added ❌ reaction hook to delete the message IF the user is a trainer, and the message is in #request-rank

Reopening this pull request, since this branch hasn't been merged yet.

I'm thinking that if we're going this far we should probably switch to the Python logging system

Utilizing the full logging system is a bit overkill to get just a time stamp, however there are other portions of the code that could use it to display messages.

Yeah, I can see that, but this is a pretty big unrelated change though, so go ahead and throw it in a seperate pull request.
-------- Upprunaleg skilaboð --------
Kveikt 5. jún. 2021, 20:59, Daniel Smith skrifaði:

I'm thinking that if we're going this far we should probably switch to the Python logging system

Utilizing the full logging system is a bit overkill to get just a time stamp, however there are other portions of the code that could use it to display messages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Will do

I have moved the commits regarding timestamps into another branch/PR

I'll most likely push reviewing this one until tomorrow morning/noon.


Bugfix/issue 1937 ios base

Submisison Checklist

[ ] Run unit tests: ./runTests.py src/test/unit gtest is broken locally
[ ] Run cpplint: make cpplint python: can't open file '/cpplint.py': [Errno 2] No such file or directory
[ X] Declare copyright holder and open-source license: see below

Summary
Deletes the specialized ios-base::failure exception
Intended Effect
Allow clang++ to compile rstan
How to Verify
R CMD build rstan once the fix makes it into StanHeaders
Side Effects
Exception message is more generic
Documentation
None
Reviewer Suggestions
@bob-carpenter
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Trustees of Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

The one failing Travis run actually says that it passed after 6+ hours

Travis has been acting up lately. I just restarted that one job that failed
-- you should have been able to do so yourself.
I'll take a look at the actual pull request now.
On Tue, Jul 26, 2016 at 9:25 AM, bgoodri<EMAIL_ADDRESS>wrote:

The one failing Travis run actually says that it passed after 6+ hours
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/pull/1977#issuecomment-235266186, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F4qYcG151SHYLianLq7fHKctvNZ4ks5qZgrLgaJpZM4JUmkW
.

btw, what do you mean gtest is broken locally? Can you show me at the meeting?

Looks good to me.

Thanks much.  I mistakenly thought I'd already made this fix for 2.10.


feat(confusing-browser-globals): Add relevant messaging to no-restricted-globals eslint rule

BREAKING CHANGE: export from confusing-browser-globals package changed from String[] to Object[] - no change required if used in eslint no-restricted-globals config
I came across unclear messaging in eslint-config-airbnb today and traced it to this package, which is included in eslint-config-airbnb-base.
If you have code like:
const SomeComponent = () => {
  useEffect(() => {
    const queryString = location.search.substr(1)
    // do something with query string
  }, [])

  // ...
}

Using this package in eslint no-restricted-globals rules will result in the error Unexpected use of 'location'. no-restricted-globals

Which may communicate "don't use location at all" rather than the intended "prefer window.location or a local parameter to avoid unintended effects"
So I've updated this package with clearer messaging, like in this case Unexpected use of 'location'. Use local parameter or window.location instead  no-restricted-globals

And in doing so realised we don't want to recommend using window.<property> everywhere, for example the following code:
const handleEvent = () => {
  doSomethingWith(event.target.value)
}

We'd catch this and suggest using the (missing) local value and not window.event.
So I extended the list with a suggestion between window, document, WorkerGlobalScope*, or none to determine the correct messaging, and added tests covering each scenario.
Since the output of this package changes, it would break anywhere that strictly expects an array of strings to be exported (i.e. not being used in eslint config). It should release as a breaking change and new major version.
* WorkerGlobalScope applies to self included in this list, which made most sense to me but could be removed entirely from the list considering https://developer.mozilla.org/en-US/docs/Web/API/Window/self

Still relevant if anyone's available to review


[FEATURE] add infinite load to mates page

Description
Instead of showing all the users data at a time, show ~20 at first glance and upon scrolling show more. We already have implemented infinite load in the projects page, need to implement for mates page as well. Instead of modifying existing api, i would strongly advice create another api for the infinite load feature in the backend.
let me know if you have any doubts. Thank You :)

can i get assigned this issue?

can i get assigned this issue?

Sure :)

hi @rohitdasu  could you assigned me this feature, hope my contribution will add a value to this project...

@csagar131 sure, thanks for showing your interest :)

Thanks @rohitdasu

Hi @rohitdasu  i am getting below error while seeding the mongo database, i have tried almost everything available on internet to solve this issue, still getting same error,  could you please help me out here.
yarn run v1.22.21
$ /Users/sagarmochi/Desktop/projectmate/node_modules/.bin/prisma db seed
Environment variables loaded from .env
Running seed command ts-node --compiler-options {"module":"CommonJS"} prisma/seed.ts ...
An error occurred while running the seed command:
Error: Command failed with exit code 1: ts-node --compiler-options {"module":"CommonJS"} prisma/seed.ts
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@csagar131 are you on discord group? I can have a look at this problem.


How to sync OnlyOffice Community for 10,000+ LDAP users?

OS : docker Ubuntu:18.04
VERSION : CommunityServer V12.6.0
OPERATION : ldap sync user
ERROR : The maximum number of ldap synchronization users is 10000, report ”The current pricing plan user limit has been reached“

Hello @ivonlee These are our specific restrictions for the server version of Onlyoffice Workspace to ensure maximum performance. The user selector will take a long time to load throughout the portal. You can change this restriction in the tenants_quota table, but we cannot promise stable operation of the user selector and the rest of the portal.

Thanks for your reply. We have modified the value in the database to exceed 10000, but the above information is still prompted to ask if there is any other place for hard coding

Please try restarting the community server site inside the community server container:
systemctl restart monoserve