feat: allow to set initialSearchTerm

Based on discussion on this other PR https://github.com/MrBartusek/gif-picker-react/pull/32 I decided to send a suggestion to have a better UX + fixing some typos.
Behavior:

Placeholder will still show Search Tenor.
Initial search term will be the default and initial search to already show relevant/context gifs to the user.
Categories won't show up because of the initialSearchTerm, added this note to the README docs.

initialSearchTerm is just a duplicate of #32 at this point. But I would gladly merge these typo fixes. Please remove initialSearchTerm implementation from here but keep other fixes.

it still has a different behavior related to have input value empty + still search relevant gifs, you can see the storybook, would you rather the other behavior?

initialSearchTerm is just a duplicate of #32 at this point. But I would gladly merge these typo fixes. Please remove initialSearchTerm implementation from here but keep other fixes.

it still has a different behavior related to have input value empty + still search relevant gifs, you can see the storybook, would you rather the other behavior?

Oh, I overlooked that. In that case, it's just a questionable UX choice. A user can see that nothing is being searched for and then they see a search result. I would prefer #32 implementation rather than this one
Can you please tell me, does #32 fit your use case?

@MrBartusek  Technically so so, it has a worst UX, our common tag used w/ creators is the name of the product, which would make no sense (or irrelevant) to show to the user as a term, they will need to remove the entire term to search something else, whereas this one will friendly change behavior based on users' interaction

Hey! I've just merged #32 and the implementation for the initialSearchTerm as in this PR doesn't work for this project. I would be happy to merge a PR with these typo changes you have made, and we can discuss a fix for your use case later.
This may be tricky to update this PR specifically since I've implemented new listing rules and caused conflicts in every single file. So I would suggest you either make a new PR with the typo fixed or try to change this one.

@MrBartusek thank you, I'll take a look, lets close this one.


Using Node & OpenAI Embedding Question

The openai.createEmbedding returns an Array object for the embedding. How do I insert those into my database to later use with vss0? Convert to bytes? Also made a request on their project but maybe the question is more specific to here?

https://github.com/openai/openai-node/issues/39

Yes JSON.stringify() will probaby be the easiest way.
I have a WIP docs site here, with a section about working with vectors in Node, but they're still incomplete https://alexgarcia.xyz/sqlite-vss/nodejs.html

Thanks! I'll close this out.
Do you have any advice on how to query? I'm there now and working thru it...

The SQL should be similar to something like this:
select rowid, distance
from vss_articles
where vss_search(headline_embedding, ?)
limit 100;

Where ? is a parameter you bind that's either a JSON string of a vector, or the "raw bytes" representation of a vector (using Float32Array like in those docs).
That'll just get you the rowids and distances of the 100 nearest vectors to your query vector, you'll probably want to JOIN that query against other tables in your DB. If you want the raw values of the original vectors, you can also return them, which should be vectors in "raw bytes" as of v0.1.1


feat: created the OG image for repository pages

Description
Implements the open graph (OG) image for repository pages.
Related Tickets & Documents
Closes #3098
Mobile & Desktop Screenshots/Recordings

Steps to QA

Go to e.g. https://deploy-preview-3117--oss-insights.netlify.app/s/kubernetes/kubernetes
The repository page loads.
In Slack or some social network, paste that URL.
When the post or message is published, an OG image appears.

Tier (staff will fill in)

[ ] Tier 1
[x] Tier 2
[ ] Tier 3
[ ] Tier 4

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Looking good on imessage. Title does get cut off though.

Looking good on imessage. Title does get cut off though.

@isabensusan should we reduced the font size or is the avatar and just the name not org better?

For reference, GitHub wraps the name

Yeah, chatted with @isabensusan, and that's what I'm going to do.

So with a short and long name.


Integrate PropertyField support

Implement a Property handling strategy

Support Environment variables
Support Java System properties
Support Atlas Mapping defined properties
Support runtime properties
Support a default processing order: Env, Sys, Mapping, Runtime

Last "wins"

Support a way to configure the processing order and/or disable certain property bags

PR #34 integrated w/ 83.3% unit test coverage of the property strategy class


Default Cryptographic Secrets Stored in Source Code

Description:
Cryptographic secrets were found within the corpora-data-portal application source code. As this is an open source repository, any attacker or malicious insider would have access to these secrets. This may enable them to attack the cryptographic systems used by the application.
The assessment team found that the Flask secret key defaulted to a hard-coded secret of “OpenSesame” if a secrets file is not found (lines 39-48 of corpora-data-portal-main/backend/chalice/api_server/app.py, shown below).

The Flask secret key was used to sign session cookies, so anyone with access to this key would be able to impersonate other users and escalate privileges to a user with higher permissions.
While this currently has no impact on the production application when the auth_secret is successfully loaded, it is recommended practice not to set a default value for a secret. Ensuring that the testing environment loads secrets in the same manner as the production environment would lessen the chance of future code refactors or bad deployments causing the hard-coded secret to be used in production.
Recommended Remediation:
The assessment team recommends that the secrets for the testing environment are loaded in the same manner as for the production environment. If this is deemed impractical, then the application initialization code should only use the hardcoded variable when the testing environment is explicitly set, and fail to start the server otherwise.

This is a very low risk issue. Closing for this reason.


Typo

Theres a typo at the beginning of the following sentence:
> 1 If your SharePoint databases are scaled across multiple servers, you cannot use the Scheduled Backups feature to back them up.

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

ID: 4d2b336e-6b64-615b-ac24-416772d184c7
Version Independent ID: 33e3cb7c-581c-1f82-581e-ec210fa80b6e
Content: Understand TFS databases, deployment topologies, and backup - Azure DevOps Server & Team Foundation Server
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/tfs-docs-pr?path=%2fdocs%2fserver%2fadmin%2fbackup%2fbackup-db-architecture.md&version=GBlive&_a=contents
Product: devops-server
Git Login: elbatk
Microsoft Alias: elbatk

@pascalberger Thanks for letting us know, I'm getting it fixed and it should be live soon.


002 Package Strucure and Code Organization

Proposal for package structure and code organization. Relates to direct-state-transfer/dst-go#38

@manoranjith, I guess 53a099f slipped into this PR by mistake, didn't it?

Yes, commit 53a099f slipped in by mistake. I have removed it now.

Hi @choeppler,
I have squashed the commits and updated the pull request.
I have also changed the status to accept and added source file for the diagram.
Can you please review it again.


Clean loggers

Coverage decreased (-0.05%) to 7.425% when pulling f9209037a6a7a478df458286f52e4c533426b8f4 on clean-loggers into 5b68e1c4852c335dac1365cf94c06b053b789c41 on master.

Coverage decreased (-0.1%) to 25.445% when pulling 9f1efbbc78f0754abe69eececad00fa1c07ff6ee on clean-loggers into c0c311ddb62d73553b4333471f7b8bd0f2cd32e8 on master.

Coverage decreased (-0.1%) to 25.445% when pulling d695ebea2d2644e3f292714c007a7d7f75498d02 on clean-loggers into c0c311ddb62d73553b4333471f7b8bd0f2cd32e8 on master.

Changes Unknown when pulling f7cbcf1c829007e496c2fe651e96ec337ecc0071 on clean-loggers into ** on master**.


gRPC throws "Did not read entire message" for unknown reason

What version of gRPC and what language are you using?
v1.24.3, C++, Python
What operating system (Linux, Windows,...) and version?
Linux, Ubuntu 18.04, x64
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc --version
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.

python3 --version
Python 3.6.8

What did you do?
We use gRPC in our product (thank you for it). Our testers reported a bug that one of the APIs didn't work.
What did you expect to see?
Working rpc.
What did you see instead?
"Did not read entire message","grpc_status":13"

For no reason we faced the error ^^ above. I did some investigations and figured out that the issue could be fixed simply by the variables re-ordering in that particular message.
Sample application
I've written a sample application to confirm the bug https://github.com/AntonQubecinema/grpc-issue. Please refer to README for the details.
If you need any help, feel free to contact me here.

Esun, can you take a look?

@yashykt is there any hope that this will be resolved?

This should not have been closed, sorry for that!
@veblush ping

I decided to take a look myself since it seemed interesting.
I was unable to replicate the build instructions exactly, so I had to copy over the content to my existing setup.
Looking at the example, I was first suspicious of the name 'option' being used. I would expect protobuf to treat that as a keyword and give an error on compilation, but surprisingly it did not.
On running the example with grpc_cli, the RPC succeeded with both TestFailed and TestPassed.

@yashykt thanks for your response!
Please let me know if you have any questions.

My above response does use grpc_cli so it does not seem to be reproducible with a C++ client (grpc_cli).
I tried creating a Python client too and this time TestFailed did fail with the following log -
_open_source_grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.INTERNAL
	details = ""
	debug_error_string = "{"created":"@1597740539.550490995","description":"Error received from peer ipv4:<IP_ADDRESS>:1234","file":"third_party/grpc/src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"","grpc_status":13}"

I did suspect that the field name 'option' might be causing an issue but that turned out to not be the case, since TestFailed still failed even after changing the field name to 'optiona'.
Based on this, I do acknowledge that this is weird behavior and should be investigated though this bug might potentially lie in protobuf territory. I doubt gRPC Python is doing anything special for serializing the protos, but I will ask the Python folks @lidizheng  @gnossen for their opinion.

(Lidi, Richard: I've got an internal setup ready for reproducing the bug if the steps provided by @AntonQubecinema do not work for you either)

After running the example, I can reproduce the error. However, I find Python client serializes the TestFailedRequest successfully and the StatusCode.INTERNAL was returned by Core as an event.

Unfortunately, this doesn't seem like a gRPC Python issue but an issue between ProtoBuf and Core. gRPC Python client's behavior looks legit but peer returned internal error.
@AntonQubecinema Can you help to provide the tracing log for both the Python client and the C++ server? To turn on tracing, set environment variable GRPC_TRACE=all and GRPC_VERBOSITY=debug. See https://github.com/grpc/grpc/blob/master/doc/environment_variables.md for more details.

@lidizheng did the internal repro not work for you?

@yashykt It works (is reproducible). But I still can't get the tracing log with debug build.

@AntonQubecinema Can you help to provide the tracing log for both the Python client and the C++ server? To turn on tracing, set environment variable GRPC_TRACE=all and GRPC_VERBOSITY=debug. See https://github.com/grpc/grpc/blob/master/doc/environment_variables.md for more details.

Please see the attached files, @yashykt , @lidizheng
client.log
server.log

From the tracing log, the binary message was sent out of client, but it is still unclear why the server directly set status code to 13 (INTERNAL).

@lidizheng is there a difference when compared to a C++ client?

I haven't got time to produce the tracing log and compare the actual bytes yet.

@yashykt @lidizheng
Me added C++ client to the demo
Both tests passed for C++ client. See the tracing logs attached.
cpp-client.log
cpp-server.log

Thank you for providing the trace log for both languages.
For server side, unfortunately, there isn't any interesting log about why the method decided to return a status code 13.
For client side, the only difference I found is the encoded protobuf message:
C++ Client:    DATA: 00 00 00 03 00 00 00 00 0f 0a 0d 0a 06 62 6c 61 62 6c 61 10 f4 03 18 '.............blabla....'
Python Client: DATA: 00 00 00 03 00 00 00 00 0d 0a 06 62 6c 61 62 6c 61 10 f4 03 18 01 00 '...........blabla......'

So, I checked the encoded message for these two client. There are 2 bytes difference:
C++ Encoded Message:    0A 0D 0A 06 62 6C 61 62 6C 61 10 F4 03 18 01
Python Encoded Message:       0A 06 62 6C 61 62 6C 61 10 F4 03 18 01

This is definitely something wrong, and I created an issue https://github.com/protocolbuffers/protobuf/issues/7863 to their repo.

@AntonQubecinema Awkwardly, a ProtoBuf maintainer pointed out that the Python client is creating the sub message TestFailedMsg https://github.com/AntonQubecinema/grpc-issue/blob/master/client/manual/test_client.py#L24. While C++ client is creating legitimate TestFailedRequest.
Why the malformed Python client passes the first unit test is still unclear to me. It could be those two different messages accidentally have the same serialized output.

whoops, this turned out to be a wild-goose chase

@lidizheng @yashykt thanks for your time, guys!


OSQuery integration

Hola All,
Has there been any progress on OSQuery?
Ref: https://medium.com/netflix-techblog/introducing-netflix-stethoscope-5f3c392368e3
Cheers!

Hi Andrew,
Thanks for your interest. Unfortunately, progress on OSQuery is stalled for a few reasons, including our workload.
Further, the technical problem of integrating OSQuery has turned out to be bigger than I initially thought. One reason is the many different configurations for OSQuery (i.e., which "packs" are in use). A second reason is that OSQuery has no default or canonical storage method for the data it collects. We're still brainstorming around how to provide an OSQuery plugin that works for us and for the majority of potential users.
I'll leave this issue open to track progress over time.

@andrewmwhite do you presently have any update w.r.t OSQuery integration, is this on any roadmap for implementation this year or is this request presently still upon a "wishlist"?
Thanks!

A generic osquery integration is still basically on the "wishlist"; that said, the issues I mentioned above make that technically infeasible.
It's more likely that someone would integrate Stethoscope with one of the packaged osquery providers (like Uptycs), but we have no plans to do that ourselves at this point.

Perhaps relevant: https://github.com/mwielgoszewski/doorman (A FOSS fleet manager for OSQuery)

also consider as relevant Fleet by Kolide https://github.com/kolide/fleet (they have nice APIs) and Zentral https://github.com/zentralopensource/zentral (django based + elastic stack build in).
it's mostly what functionality should be linked here:
i.e. Stethoscope webhooks + serial number could enable multiple integrations to all such projects.

@headmin Would you elaborate a little on what you mean here?

it's mostly what functionality should be linked here:
i.e. Stethoscope webhooks + serial number could enable multiple integrations to all such projects.

sure. sorry I just sketch this briefly.
i.e. if a outgoing webhook from a osquery TLS system (Doorman, Kolide, Zentral alike) will contain a payload with serial number of device, and Stethoscope can receive and filter such incoming webhook -> this could be used to indicate a "status" or severity for a device (identified by serial number).

Got it. We may end up implementing a datastore specific to Stethoscope
itself, at which point would be possible to provide API endpoints for
receiving device data. Still in the wishlist stage, as well, though.
On Tue, Mar 13, 2018 at 12:26 PM headmin<EMAIL_ADDRESS>wrote:

sure. sorry I just sketch this briefly.
i.e. if a outgoing webhook from a osquery TLS system (Doorman, Kolide,
Zentral alike) will contain a payload with serial number of device, and
Stethoscope can receive and filter such incoming webhook -> this could be
used to indicate a "status" or severity for a device (identified by serial
number).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/stethoscope/issues/28#issuecomment-372788844,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQudkh2aY0qBv4DUecAQZyOaBfxGMygks5teB1QgaJpZM4NbPJY
.

Also jumping in on this, we're using Kolide Fleet as or osquery manager, basic incoming data from workstations is available in JSON format; while the technical problem would be what keys and dicts to select, another method could be getting all the key names that are available and presenting that to the administrator to use in policy creation.
Currently, we have this terraformed on AWS and logging to S3 with Athena analysis (and streaming to ElasticSearch), for us it makes it relatively easy to add this (if we can get the spare resources to do this), a problem could be that it is nearly impossible to make it generic, as osquery itself doesn't want to be responsible for any logging, streaming, events etc. Even osqueryd is bare-bones to the point where you need a process manager to manage it's lifecycle. Not a bad design per-se, but it does make integration for bare osquery somewhat hard.
I propose that getting specific osquery wrappers to work with stethoscope instead of generic osquery is a much more feasible way forward.

Oh we also landed on Kollide to manager our OSQuery stuff. (perhaps its becoming the defacto mechanism to do this?)


Unable to add a third head node to VM cluster

I am seeing following errors when I add third head node to the cluster with BCPC-Hadoop-Head role assigned to it.
================================================================================
    Error executing action `run` on resource 'ruby_block[setup-jn-data]'
    ================================================================================

    NoMethodError
    -------------
    undefined method `bash' for Chef::Resource::RubyBlock

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/bcpc-hadoop/recipes/journalnode.rb:52:in `block (2 levels) in from_file'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/bcpc-hadoop/recipes/journalnode.rb

and
Recipe: <Dynamically Defined Resource>
    * directory[/disk/1/dfs/jn/] action create (up to date)
    * directory[/disk/1/dfs/jn/Test-Laptop] action create (up to date)
    * file[/var/chef/cache/jn_fmt.tgz] action create (up to date)

    ================================================================================
    Error executing action `run` on resource 'ruby_block[setup-jn-data]'
    ================================================================================

    NoMethodError
    -------------
    undefined method `resolve_notification_resources' for Chef::Resource::RubyBlock

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/bcpc-hadoop/recipes/journalnode.rb:65:in `block (2 levels) in from_file'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/bcpc-hadoop/recipes/journalnode.rb

Fixed in PR #772

Resolved when #772 was merged.


Nishit/springboot auth setup

Completed Auth setup with Login, Registration and Logout functionalities.
User data is dynamic now.
Made a few changes to the UI
Spring boot skeleton is now set with various examples

Will require docker setup in everybody's systems as database is being used out of docker.
Steps to configure:

Install Docker Desktop
add a .wslconfig file to your C:\Users{user} directory with the following text:

[wsl2]
memory=4GB
processors=2

while trying to run everything together, in the root directory of the project run the following command: "docker-compose up --build", it will take some time to create containers of everything and the application will be running inside containers on localhost.


metanorma/metanorma-build-scripts#18 add ruby 2.6 to CI matrix

@CAMOBAP795 please update the Nokogiri dependency here for this PR. Thanks!

@CAMOBAP795 can you relax the Nokogiri dependency here so that we can merge? Thanks.

@ronaldtse done

Thanks, @CAMOBAP795 feel free to merge when all passing.

@CAMOBAP795 which gems do we have that lock Nokogiri dependencies? We should hopefully only have 1 or max 2 gems that have this requirement. I can't imagine other gems needing to lock Nokogiri.

@ronaldtse I purpose to keep version here https://github.com/metanorma/relaton-bib/blob/master/relaton-bib.gemspec I have just removed it from https://github.com/metanorma/iso-bib-item/pull/11/files too


[Bug Fix] - fixed bug in discovery layout Toolbar

What

fixed bug in discovery layout by wrapping the toolbar and tabs in a linear layout

Issue

The toolbar wasn't responding to clicks due to the CollapsingToolbarLayout not having one direct child.

Tested On

Galaxy S7 (Aaliyah 7.0)
Galaxy S3 (Enya 4.4.2)
HTC One (Cher 4.4.2)

 Toolbar Bug Fix


[Fix] Same branches for inconsistent build check

Inconsistent build configuration was checked regardless of ENABLE_ASSERTS.
It looks like an error, and dropping it helps with header only use.

This is here on purpose.  The logic of the check doesn't work if you remove that code.  Right, this would allow someone to build object files with asserts enabled and then later build other object files against headers with asserts disabled.  That would be an ODR violation.

I do realize this is irritating for things that would otherwise work header only.  But before I added these checks I would constantly get posts from users who messed up their build systems and created ODR violations.  There isn't anything I can do to stop users from doing that.  Like they would setup some broken build system, and they happen to also be using dlib and so they complain to me about it.  But it's got nothing to do with dlib.
I'm open to suggestions for how to make this less annoying.  But I don't really want to remove the error checking.  Maybe there could be some option that disables this, like #define DLIB_HEADER_ONLY or something.  Needing that is also sort of irritating though and it wouldn't surprise me if I then start getting messages from users like "I'm using #define DLIB_HEADER_ONLY and I then went and built the dlib .cpp files into my program anyway and created ODR violations!".   Or people would get one of these "you are making an ODR violation, fix your build system!" errors.  And their solution is go to stick #define DLIB_HEADER_ONLY at the top of their .cpp files to make it go away.

No problem there. I thought it was a mistake because it's the same two lines in two branches. Maybe just remove #ifdef ENABLE_ASSERTS altogether then?

Na, those are different lines.

Oh. One tiny underscore. Didn't notice. Still, maybe at least a change in the FAQ?

What change would you suggest?

So, for this question, I suggest something like that:

If you absolutely sure you have to use dlib as headless library (strongly discouraged), e.g. to use pipe, you should comment out macroses ENABLE_ASSERTS and DLIB_CHECK_FOR_VERSION_MISMATCH  in config.h and this line:
    const int USER_ERROR__inconsistent_build_configuration__see_dlib_faq_1_ = 0;

in one (and only one) of your cpp file.
Before you do that, make sure you actually need this. If you don't wand to use dlib as a shared library, you can simply add source.cpp to a list of *.cpp files.

This definitely worked for pipe header-only use. Of course, then I thought these "identical" lines is a bug, and "fixed" that. As for why I didn't just include source.cpp myself, it was a fix of another project with five Studio projects, one xcode project and one Makefile. At that point, just adding one line to an existing file, and then removing two from another one feels less of a hassle.

It honestly sounds like you are talking about creating an actual ODR violation though.  Like if you are using dlib::pipe then you need to be building the threading .cpp files or it won't work.  It's not header only.  And if you are doing that and getting errors from things like USER_ERROR__inconsistent_build_configuration__see_dlib_faq_1_ then it's because you have done something in your build setup to violate ODR.

An yet it works: https://github.com/topin89/dlib_pipe_is_headless/
Looks like none of the function in threading .cpps are actually used, and unused function declarations are allowed. Luck, I guess, but it works anyway.
Still, as I understand it, headless use is unsupported, or at least limited to a few libs. Maybe this should work for the FAQ:

Maybe you're trying to use dlib as a headless library. This is not supported <or supported only for ...> and you're on your own, so don't ask for help if something is not working as expected.

Ah, yeah, turns out the dlib::pipe does work with just the header.  Header only use is fine and something I expect people to be able to do for some things.  If you want to do it you can just delete the contents of dlib/test_for_odr_violations.h.  Nothing bad should happen for actually header only use.  The problem happens when people then go build in dlib/all/source.cpp with different settings or do some other ODR violating thing.
But if you really aren't building any dlib .cpp files into your application then you can't get into any ODR violation situations.

Header only use is fine and something I expect people to be able to do for some things. If you want to do it you can just delete the contents of dlib/test_for_odr_violations.h

Cool! It is worth mentioning in FAQ, I think. Or maybe another approach:
Another macro, ENABLE_HEADLESS. So, if enabled, test_for_odr_violations.h is skipped entirely, but another header, e.g. test_header_only.h, with something like
#ifdef ENABLE_HEADLESS
extern const int USER_ERROR__source_cpp_is_compiled_despite_using_headless;
#endif

included in source.cpp.

Yeah, an ENABLE_HEADER_ONLY macro could be ok.  That seems kinda funny too though.  I'm more happy to just let someone who knows what they are doing delete the contents of test_for_odr_violations.h.  I'm hesitant to put that in the FAQ though, because lots of users will cargo cult that into their programs without understanding and I'll be right back to the original problem.


[BEAM-9443] update document about direct_num_workers = 0 for FnApi

R: @pabloem

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Can you please add a more clear title/commit message

Can you please add a more clear title/commit message

Both title and commit message were updated with clear contents.

LGTM. Feel free to merge.

LGTM. Feel free to merge.

Thanks Pablo!


It is recommended to provide datazoom function for Bar and Line

When there are many X-axis data, some X-axis data will not be displayed

Duplicate of #1251


add errant_ttl python script

to detect and repair db records with ttl = null or greater than 3 days.
Please review but DO NOT MERGE.  We will recreate a PR and merge to master after enums-feature is merged to master.
Once I received the +1 I'll package and deploy just the python script to prod to run analysis and repairs as needed.
Usage of script:
usage: errant_ttl.py [-h] {show,repair} ...

show and repair cassandra records with errant ttl, e.g. null

positional arguments:
  {show,repair}  commands
    show         get all records in a table with errant ttl
    repair       repair all records in a table with errant ttl

usage: errant_ttl.py show [-h] [-e {localhost}] -cf COLUMNFAMILY [-l LIMIT]
                          [-ttl TTLINSECONDS] [-v]

optional arguments:
  -h, --help            show this help message and exit
  -e {localhost}, --env {localhost}
                        Environment we are pointing to
  -cf COLUMNFAMILY, --columnFamily COLUMNFAMILY
                        name of column family (table) to retrieve rows from
  -l LIMIT, --limit LIMIT
                        limit number of records to retrieve at a time for
                        analyzing; default to 500, use 0 for no limit;
  -ttl TTLINSECONDS, --ttlInSeconds TTLINSECONDS
                        the ttl threshold in seconds to compare against,
                        default to 157680000 seconds (5 years)
  -v, --verbose

usage: errant_ttl.py repair [-h] [-e {localhost}] -cf COLUMNFAMILY [-l LIMIT]
                            [-ttl TTLINSECONDS] [-v] [--dryrun]

optional arguments:
  -h, --help            show this help message and exit
  -e {localhost}, --env {localhost}
                        Environment we are pointing to
  -cf COLUMNFAMILY, --columnFamily COLUMNFAMILY
                        name of column family (table) to retrieve rows from
  -l LIMIT, --limit LIMIT
                        limit number of records to retrieve at a time for
                        analyzing; default to 500, use 0 for no limit;
  -ttl TTLINSECONDS, --ttlInSeconds TTLINSECONDS
                        the ttl threshold in seconds to compare against,
                        default to 157680000 seconds (5 years)
  -v, --verbose
  --dryrun

optional arguments:
  -h, --help     show this help message and exit

Can we update all rows to TTL of 3 days, let say to full resolution CF? What problems would this cause? If some rows have TTL of 1 day remaining, in worst case they will live for couple more days. This probably is a ridiculous idea, I am just trying to understand at this point.

@ChandraAddala re: updating the TTLs of all rows of a table... I am not sure why you would want that accomplished instead of just updating the ones that actually need fixing.   What is your reasoning?

If there are too many rows which need an update, it would be easier to update all of them.

@ChandraAddala "update all of them" concept does not exists for cassandra >.<

neither does delete all of them for that matter.
However, you can delete (truncate) the entire table!  but that's something we do NOT want.

@VinnyQ  - has all this work been completed?  should we merge?

no longer relevant.  this script is timing out in prod db and we found a different solution (directly deleting sstables files older than yymmdd date).


prepuller is fine on nublado, updating int

going to self-merge.  It ran fine overnight at nublado.lsst.codes.


clarify about concurrency / safety

Per #11.

LGTM.
@slimsag did you want to see anything else?

LGTM.
We will also want to have this be a part of the Go package docs at (https://godoc.org/github.com/opentracing/api-golang/opentracing) but this can be done as a follow-up. I'll see if I can send a PR for this tomorrow.

@slimsag makes sense re the godocs. We need a package-level comment there; hopefully it can point to the main opentracing.github.io site for general background.


Modernize build

See https://github.com/dwavesystems/dwave-greedy/pull/16.
At the very least, define build system via pyproject.toml according to PEP-517/PEP-518.
Blocker for https://github.com/dwavesystems/dwave-ocean-sdk/issues/144.

Resolved with #196.


Add JDownloader

This proved to be a bit tricky to implement in scoop, and I'm not sure if my approach is the most viable one.
Due to self-installer that by itself is dependent on java, it ended up being more complex that I would have liked.
With my approach, scoop will wait until jdownloader downloads icon file in pre_install phase, then it proceeds with installation, creates dummy shortcut (so that scoop can track and remove in case of uninstall), and then manually modify icon and target of the shortcut in post_install phase.
Given the nature of this manifest, whether you want to merge this or not, is up for your consideration. I just thought I'd share my manifests that I built over the past few months, maybe some folks using brilliant scoop would find this handy.

Web installer version contains adware. Downloading .jar and letting it download through their update servers is cleanest way to get only the software you want. Second reason, it installs embedded JRE, taking up additional space as well as taking away control on version of JRE you want to run (when I already have JRE installed anyway).

So this file which is at their download page (Other platform) is containing adware? On official page?

Downloading .jar and letting it download through their update servers is cleanest way to get only the software you want

Thats exactly what that other platform do. Its single file which after executing as javaw.exe -Xmx192m -jar .\JDownloader.jar will lead to downloading from their servers.

pre_install could be converted for "installer" :{"script": ""}. It would be much cleaner

Looks better now, thanks @Ash258 . Only downside is that due to shortcut being .bat it now flashes a new cmd line window quickly. But that's a nitpick, and users can of course create their own shortcuts with direct targets.
If shortcuts parameters could evoke commands (much like pre_install for example can) it would be much easier to do shortcut properly without relying on .bat.

Or try using a powershell script instead of cmd: https://github.com/lukesampson/scoop/blob/master/bucket/neofetch.json

Make it Start-Process javaw.exe -ArgumentList "-jar", ".\JDownloader.jar" -wait It will be waiting until process exit (No need for while)

Looking much better now than first commit. Thank you for suggestions.
One more thing I would like to add would be autoupdate/checkver. but sadly it seems developers don't publish changelog for this file, they simply just update JDownloader.jar. This file seem to be updated only occasionally (current version was first submitted to VirusTotal on 2018-03-24). Hopefully it wouldn't cause too much manual maintenance over time, with updating hashes when the files change.
Alternative would be to omit hash, but then users see warning that there are no hashes. 🤷♂


Upgrade to nom 1.0

Hi!
nom 1.0 is here, and comes with a few breaking changes. To help the transition, and to test the beta version before release, I took the liberty to test and upgrade (if needed) your code to the 1.0 version. It should work right away, but if there are still issues, or if the code needs to be updated to your latest master, please let me know!
If you want an explanation of the changes, please take a look at the upgrading documentation.
By the way, could you go to one (or all) of those links and write a few kind words about your experience writing parsers in Rust? It would really help me!

nom 1.0 release blogpost
Reddit post
Hacker News post

Thank you for using nom!

Thanks a lot for all this information ! As soon as this parser is done, I'll spread the name of "nom". ^^


disconnecting client as steam ticket authentication failed with error 4

i have this error during connecting to server every time. What i should do to repair it?

guys, i get it. ypu should just put 480 instead here instead other

Piracy is not supported.


resources not processed [v 4.0.0-next.415]

i could be doing something wrong (again) but am following the docs for bundling assets.
import * as file  from './abc.png'

based on the docs: https://github.com/fuse-box/fuse-box/blob/master/docs/resource_links.md
it seems that these types of resources should be handled without additional configuration.
have also added the resource path in fuse.ts:
resources: {
    resourceFolder: resourcePath,
  },

i don't see the files being copied to my output (dist/) folder
is there any examples i can look to? i saw this one: https://github.com/fuse-box/react-example which had assets to be bundled

Have you cleared the cache? It might be related. Otherwise, here is the code for reference. It follows the configuration. Unless something is broken on the way.

tried clearing the cache -- no luck.
the code links helped. i don't see the callback invoked (plugin_link.ts):
 return (ctx: Context) => {
    ctx.ict.on('bundle_resolve_module', props => {
      if (!props.module.captured) {
        // filter out options

i added the following as well to fuse.ts:
  plugins: [pluginSass('app.scss', { asModule: {} }), pluginLink(/\.png/, { useDefault: true })],

not sure if its needed given that png resource types are handed without extra configuration

So is it working now ? If not please reproduce it

its still not working, even with adding the link plugin... as for reproducing:

i have a simple react (typescript) app building with fuse-box

watcher/HMR are working for react components, sass compilation and HMR for styles is working

when i add a png resource in the src/ folder its not getting picked up. it looks like the pluginLinkHandler is not getting called or more specifically the callback to the 'bundle_resolve_module' event set in the pluginLink() method.
is there a test case i can run in an environment for resources such as a .png? just to confirm is a code issue or a config setup issue

@fiftymissioncap there is really weird. I've just tried it myself
import logo from './logo.png';

No configuration set whatsoever, it's being correctly copied:

Which OS are you using? Mac/Windows/Linux
DIsable cache and try again.

@fiftymissioncap it just occurred to me:
If the import is unused it will not be bundled.
import abc  from './abc.png'
console.log(abc);

if you remove console.log the statement will be removed.

just added the log statement ... bingo! ... its working
i thought i had tried that before but probably doing too many other things.
anyway, thanks for the help. really enjoying using this package/tool.

You are welcome :)


Readme.md out of date

The example deployment-config.json file in Readme.md says "user": but the default deployment-config.json file (created through Packages menu -> FTP/SFTP -> Map to Remote...) comes with "username":
Not sure which other settings are incorrect.

Hi @sylistine,
It's an error in the documentation, I have merged a PR for this.
Thank you for your feedback.


Add a way to figure out that a notebook document was closed

For text documents we have TextDocument#isClosed and we should have the same for notebooks. It will allow to inspect a notebook for being closed (when you missed the onDidClose-event)

To verify make sure that there is vscode.notebook.NotebookDocument#isClosed


Inlining resized images

I am currently inlining pretty much all the images on my website since that causes next to prefetch them making navigation appear instantaneous. Still, I figured out it might be a good idea to resize the thumbnail images on my blog in case someone accesses the page directly. It would appear to me that resizing and inlining is not possible, though. I tried stuff like
<img src={require("../static/img/blog/crowd.jpg?inline?resize&size=100")}/>
but no matter what I try, the image is either resized or inlined, but never both. Is what I am trying possible?

Hi @Juhannuspukki
Since we just pass everything to the resize webpack loader when ?resize is in the query param, I think it is correct right now that this doesn't work since the resize webpack loader doesn't support inlining images.
But your use-case makes definitely sense and I'll try to implement this later this week.

In my case, I manually resized the image so I could inline it.
Funny story, the image was about 6k, 1500x500. I needed to resize it to 150x50 but when webpack did it, I ended up with a 6k image (with smaller dimensions). Why? My original was using a 2bit palette but the webpack resize set it back to full color.


Add multi cpt tests and refactoring

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

22 of 22 (100.0%)  changed or added relevant lines in 1 file are covered.
24 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 94.175%

Files with Coverage Reduction
New Missed Lines
%

src/pypilecore/input/grouper_properties.py
24
16.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1536

Relevant Lines:
1631

💛  - Coveralls


Incorrect mask

Incorrect mask is applied to aeDeleteFileEvent inside writeToClient, which causes the server to get into endless loop and crash after client closed the connection.

Thx you for PR 👍


Added Traditional Chinese language file.

New language file: Traditional Chinese.

@fabriciodisalvo the zh_TW.json file you're providing isn't in a valid json format. You're using invalid characters.
Also you seem to be missing an update on l10n/supported.js.
Please test your contribution before PRing; we won't accept broken collaborations.
Also, please update your PR name to something more accurate.

Both files updated. PR name changed.
Hope it complies...

Awesome! You're just missing one little thing: add the settings.locale.zh_TW key to en.json, es.json and zh_TW.json to provide a label for the settings language drop-down. If not, this is how it looks:

Got it. So, should i add that label to every language file?

Only if you feel confident enough in every language :)
Translations fall back to the english language file so it shouldn't be an issue if it's available in en.json
Sent from my iWordPress
On Wed, Jul 1, 2015 at 12:55 PM, fabriciodisalvo<EMAIL_ADDRESS>wrote:

Got it. So, should i add that label to every language file?
Reply to this email directly or view it on GitHub:
https://github.com/DemocracyOS/app/pull/956#issuecomment-117724935

Third time's a charm? I think we are good to go now....

An (un)related question:
Shouldnt every  settings.locale.lang line refer to every language in that language?
I saw that en.json has an entry for  "Deutsche" instead of  "German" and that made sense...

It's a fairly good point; I guess it's understandable. Keys would still fall back to english if missing in the selected language file.
Would you mind opening an issue for that? I'll label it as a discussion.

@fabriciodisalvo ok, code looks good and works. There's just one more thing you need to do. Edit the PR so you submit it to the development branch. We don't merge into master since only released versions are under master

Sorry for that, haven't realized... Can I edit this PR or do I need a new one? I'm confused... Thanks in advance.

Yea; just edit your PR. I can't do it :(
Sent from my iWordPress
On Wed, Jul 1, 2015 at 4:17 PM, fabriciodisalvo<EMAIL_ADDRESS>wrote:

Sorry for that, haven't realized... Can I edit this PR or do I need a new one? I'm confused... Thanks in advance.
Reply to this email directly or view it on GitHub:
https://github.com/DemocracyOS/app/pull/956#issuecomment-117799239


Import Data.Generic.Rep from prelude

Description of the change
We merged generics-rep into prelude and renamed the Data.Generic.Rep.* modules to Data.*.Generic in https://github.com/purescript/purescript-prelude/pull/235.

The build fails because newtype doesn’t depend on safe-coerce in the package set but it compiles with the rc5 branch of my fork:
let upstream =
      https://raw.githubusercontent.com/kl0tl/package-sets/rc5/src/packages.dhall

in  upstream


Only allow uploaded videos to be seen on certain domain names

I am not sure where to put this issue since it is a feature for odysee. There does not seem to be a github page just for odysee.
Only allow uploaded videos to be seen on certain domain names when the uploaded videos are embedded into the website that has that domain name. Configure the uploaded video to not be seen on odysee publicly, but instead can only be seen on a certain domain name when embedded.
Vimeo does this. It would be great if odysee could do it as well.
If this issue does not belong here, please place it in the proper location so that it gets added.

Thanks for the suggestion. This is not possible on an open and decentralized network as everyone will have access to the same content.

@tzarebczan Good point thanks for the response.

@tzarebczan PeerTube recently added this feature that is the same as what I requested here. PeerTube is also decentralized.
https://github.com/Chocobozzz/PeerTube/issues/3773
Maybe you could do the same exact thing by using the Referer request header?


AuReiNAND A9LH - If NTR Isn't working with a firmware.bin

Hello,
I just wanted to mention something that wasn't very specific with the new update of ARN:
(x ) Autoboot SysNAND
(x ) Use SysNAND FIRM as default (A9LH-only) * This needs to be enabled so that it reads the Firmware.bin file in aurei folder*
(x ) Force A9LH detection
( ) Use second EmuNAND as default
(x ) Enable region/language emulation
( ) Use developer UNITINFO
(x ) Show current NAND in System Settings
(x ) Show GBA boot screen in patched AGB_FIRM
( ) Enable splash screen with no screen-init

Issue Tracker is not a forum, please stop flooding with useless information.


add memory to rag and chat applications

Both chat_langchain and rag_langchain do not have memory components. Meaning, that you cannot ask follow up questions during a chat session.
We should add the a chat memory component that allows for asking follow up questions. It should also gracefully handle the case in which the chat history exceeds the models context window.

Closing this issue as it was resolved in #127.


M1 macbook module not found "Cython"

When I was installing the application for m1 macbook, i got an error when i reached the step where i was pip installing the required modules. I was thrown this Error
ERROR: Command errored out with exit status 1:
     command<EMAIL_ADDRESS>-c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/rc/3jyrny5531s7kxgxp83xn0940000gn/T/pip-install-mmpe8zg_/recordclass/setup.py'"'"'; __file__='"'"'/private/var/folders/rc/3jyrny5531s7kxgxp83xn0940000gn/T/pip-install-mmpe8zg_/recordclass/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/rc/3jyrny5531s7kxgxp83xn0940000gn/T/pip-pip-egg-info-_o4jiu_x
         cwd: /private/var/folders/rc/3jyrny5531s7kxgxp83xn0940000gn/T/pip-install-mmpe8zg_/recordclass/
    Complete output (5 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/rc/3jyrny5531s7kxgxp83xn0940000gn/T/pip-install-mmpe8zg_/recordclass/setup.py", line 38, in <module>
        from Cython.Distutils import Extension, build_ext
    ModuleNotFoundError: No module named 'Cython'
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

I'm wondering if this is an issue with m1, python3 (i was using pip3 for installations) or something else.

try python3.7 to avoid rebuilding some libraries

I tried 3.7 but that didn't change the error, I ended up installing Cython manually and that seemed to fix it


runtime: TestLldbPython failing with 'no intvar'

During all.bash, I 100% reproducibly get:
--- FAIL: TestLldbPython (7.82s)
    runtime-lldb_test.go:187: Unexpected lldb output:
        Created target
        Created breakpoint
        Process launched
        Hit breakpoint
        Stopped at main.go:10
        no intvar
FAIL
FAIL	runtime	35.143s

On macOS.
$ lldb --version
lldb-1<IP_ADDRESS>
  Swift-5.0

The builders aren't failing because of https://github.com/golang/go/issues/31123.
cc @heschik @aarzilli @thanm @dr2chase

I have LLDB on my laptop and it passes.
$ go test -v -run=Lldb runtime
=== RUN   TestLldbPython
--- PASS: TestLldbPython (6.96s)
PASS
ok  	runtime	7.014s

My LLDB is older though.
$ lldb --version
lldb-1<IP_ADDRESS>
  Swift-4.2

Fails quite nicely for me, with the matching lldb version.
Just trying to use lldb by hand, it fails horribly with some sort of Python nonsense.
Using delve, the generated binary seems fine.
I assume this has something to do with updates to macOS.
Does anyone actually use lldb with Go?
It's never been anything other than incredibly frustrating for me.

Don't try this with MacPorts Python:
python
Python 2.7.16 (default, Mar  9 2019, 03:43:10)
[GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path.append("/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python")
>>> import lldb
Fatal Python error: PyThreadState_Get: no current thread
Abort trap: 6

Does anyone actually use lldb with Go?

I do, because of frustrations with gdb and codesigning. But I may be the only one.

Gdb worked for me last week, but not this week. Seriously.
I even code-signed it just now, but for some reason that didn't work.
Presumably security was enhanced in some way when I upgraded to Mojave.

But I may be the only one.

I sometimes do as well. But my use case doesn't really involve the python part (or even nicely formatted variables, etc.).

dwarfdump -verify is very whiny.
But it's whiny back to at least go-1.11.5
I don't know if this is the problem or not.

@andybons I’ve changed the milestone to 1.13, if for no other reason than it causes all.bash to fail. If we want to punt indefinitely, we should add a t.Skip to the test. I’ll defer to @dr2chase as to whether we want to fix soon or skip soon.

@josharian sounds good to me. No objection on my end.

It's not good that it causes all.bash to fail for Mojave users.
"Fix soon" assumes that "soon" is an actual option for "fix".

This may be related to whatever is going on in #29244, which causes a somewhat different failure on some Linux machines with the right (or wrong) combination of lldb and kernel versions.

It looks, though not quite proven, like this is a newish enhancement to a bug in lldb.  The accompanying dwarf dumping tools fail to properly recognize "base address selection entries" (DWARF 4, section 2.6.2, page 30) and instead decodes them as beginning and ending address offsets, in turn mis-interpreting the actual beginning and ending offsets that follow.
Apparently lldb has historically failed to properly process base address selection entries and we hacked around it for Darwin, but now their mere presence causes failure.  The string "base address ent" appears nowhere in the lldb sources.

It's reading the section start to finish rather than actually using the references? Great.
Unfortunately a base address selector is shorter than a location list entry -- it doesn't have a location expression length -- so a simple strategy of just zeroing them out won't work.
When I wrote this, I was uncomfortable actually changing the size of the .debug_loc section for fear of breaking subsequent link steps. We do have some precedent for that now, though, since DWARF compression does it. So it might be possible to actually strip the base address entries rather than leaving them around as junk data.

@heschik we're already changing DWARF section sizes in the object file reader, e.g. patchDWARFName.

That's changing the size of symbols on their way in to the linker, which should be pretty harmless. I'm pretty sure that removeDwarfAddrListBaseAddress used to run after sections had been laid out and relocations had been processed, so changing symbol sizes would have changed section sizes and layouts. But if that was ever true, it's not now, because https://golang.org/cl/111237 moved all this work before section layout is done. So it should be totally fine to just remove the base address entries entirely.

To be clear, I am benchmarking a CL that removes the base address entries entirely, and though that made dwarfdump happy (and gnu objdump and delve remained happy), it did not fix the lldb test failure.

On Mojave, it looks like your option for debugging Go is Delve, even with the Go binaries fixed to make dwarfdump happy.  The binaries on Macos were in fact technically incorrect because there were no references to the BAS entries in .debug_loc.  Objdump (from macports, gobjdump) would diagnose this problem correctly, dwarfdump would get completely confused.
Gdb from homebrew or from macports does not work, even with updated codesigning, even with with a properly configured .gdbinit (must contain set startup-with-shell off), even with proper python support (port install gdb +python27).

Also, just to be clear, I'm going to work on other problems.  I cannot see recommending anything but Delve to Go users on Macos, because so far attempting to use the other debuggers merely wastes time.

By-the-way, this is looking more like someone enhanced the bejeezus out of the LLVM Dwarf library concurrent with the Mojave-related XCode upgrade ; all sorts of stuff is broken, and it's not the Go side that's broken.  This hasn't been proven in this case yet, but given how the last few weeks have been spent it looks like a good bet.
Just for example, if you want to debug with lldb, you'll need to turn off compressed dwarf, because the splitdwarf trick no longer works.


Works with Meritsun

Hy,
The Project works also with a MeritSun LFP 200 - 48V (Rebranded by i-finity (company in Austria)).
Only had to Activate the Modbus via pbmstool.exe
@syssi if you want, you could add this to your Readme.
Thank's for the great Project :)
Greetings from Austria.
Mike

Cool! I'm happy about every contribution. Please extend the README.

See https://github.com/syssi/esphome-pace-bms/pull/30


I18n and clean url's

Is it normal that Directory Indexes doesn't works when I18n is enabled?

Unfortunately, you have to activate directory_indexes AFTER i18n in v3.

Thanks for the quick-response. Could be something for the documentation.

It's resolved in the v4 betas... but yeah, you're probably right.


Updating the wof:name of Delhi caused multiple properties to be edited

https://github.com/whosonfirst-data/whosonfirst-data-admin-in/pull/31/files
The only edit I made was to change the wof:name to "Delhi1", but as you can see, many properties were updated.

Oops, that's not good! Let's dig into this before general release of v1.

It looks like the data.whosonfirst.org version is really old. It's this one, which is from July.

Looks like we can crutch off WOF.org for which repo, but we should always read from repo.
And when new feature ask for which repo or full url?

On Feb 6, 2020, at 17:45, Ian Dees<EMAIL_ADDRESS>wrote:

It looks like the data.whosonfirst.org version is really old. It's this one, which is from July.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ahh.. the data.whosonfirst.org site can be out of sync, the Github page will have the most up-to-date version of each record.

Ok, I am making a request to data.whosonfirst.org to get the wof:repo property and then making a request to GitHub to get the actual data from the repo's master branch to display for editing.
I also added an endpoint to do this same thing so others can use it if they want: https://93ctehyu4h.execute-api.us-east-1.amazonaws.com/dev/place/85977539/metadata
I made a PR for Delhi after these changes (https://github.com/whosonfirst-data/whosonfirst-data-admin-in/pull/33) and it looks better.

I made a second PR for Delhi, which looks much cleaner: https://github.com/whosonfirst-data/whosonfirst-data-admin-in/pull/34/files
Note that the name:eng_x_colloquial property currently exists as an empty string (it should be removed), and because it is empty, the wof-editor strips the record of this property. Probably not a blocker because the property doesn't need to be present, but something that caught my eye.

Agree that empty property should be stripped out.
@iandees what happens when data.whosonfirst.org doesn't have that file? Does it error hard or prompt for a URL &/or repo?

For an example: https://93ctehyu4h.execute-api.us-east-1.amazonaws.com/dev/place/512891029831/edit
Gives:

Hit send too soon, but the idea is that on that initial page would be a box to enter the URL or the GitHub repo + ID.


Source data is inconsistent

I'm not sure how do you input new data, but it looks like some of mongo documents have very different properties within same collection. It is important to know what to expect in the results form the api user perspective.
I started a branch to add more assertions for results https://github.com/Srokap/SpaceX-API/tree/more_assertions and noticed that ie. dragon capsule and falcon rockets data differs wildly. The launches data has single launch with missing UTC timestamp.
So main question is about approach to take to make api useful for it's users that need to make assumptions about what to expect in results. We could track it in tests, or we could validate data when being put into db. In this use case, making extensive input tools might be not worth the effort, so we might run travis on master on schedule instead (don't remember if Travis allows to run tests on demand).

TODO:

[ ] Set Travis tests on daily schedule
[ ] Make vehicle data consistent for easier testing  #54
[ ] Add data validation to tests for each collection

I think the capsule data shouldn't be with the other rocket data, so all the rockets can have the same schema. I'll create a new collection and endpoint for capsule data at some point this week 👍

The schema changes are live now, all rockets should have exactly the same structure, solving the inconsistency issue. Dragon data is now on its own collection and endpoint as well.


can not excute this script

import shownfile#i have named this script
Enter a file name: r'c:\python27\showfile.py'
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\showfile.py", line 18, in
file_stats = os.stat(file_name)
WindowsError: [Error 123] : "r'c:\python27\showfile.py'"

Can you post the contents of shownfile? You might not need r in the beginning of your input.

No need for mentioning r in the start. Simply do this 'c:\python27\showfile.py'.
For more info on this method hit here: os.stat()


Test-Please don't Review it

Test Pull request.Please don't review it.

Hi

Hii

Test comment

Test Comment

Test Comment


Wont build under Delphi 11.2 (Trial)

[dcc64 Fatal Error] Vcl.PythonGUIInputOutput.pas(53): E2213 Bad packaged unit format: C:\Users\Public\Documents\Embarcadero\Studio\22.0\Dcp\Python.dcp.PythonEngine - Expected version: 35.0, Windows Unicode(x64) Found version: 35.0, Windows Unicode(x86)
Works fine in 11.1 Trial + 10.4.2 CE

You're targeting the wrong dcp. Check out your lib path.

This was using a freshly installed copy of Delphi 11.2 Trial - I guess they could have screwed the trial up... I'll go check the paths for 11.1 (which works) and compare to 11.2 (which don't)

Compile P4D for both Win32 and Win64. Make sure your lib path are set to the desired platform folder.

Just checking now. Got 10.4.2 as main install. Just copied all lib settings from 11.1 in VM, now installing 11.2 to check if anything is different - more infor when 11.2 in installed

Mine appears to have a wrong entry via the installer
What should be
$(BDSCOMMONDIR)\Dcp$(Platform)
is
$(BDSCOMMONDIR)\Dcp
That explains why it's finding the 32 bit library - Delphi Trial set it to that value

Win32 is $(BDSCOMMONDIR)\Dcp only. You must add the $(platform) variable for Win64.

Cool - that compiles properly now
What version of 11.x you using? I'm wondering if just Trial is wrong (probably) - I'll mention it in the Tutorial anyway

This issue is present in 11.x.

Not in 11.1 Trial - it was by comparing 10.4.2 to 11.1 Trial to 11.2 Trial that I found the solution- I expected this was the problem.
Did you have to change your 11.?? non-trial version then? If so this definitely needs mentioning in the Tutorial and bugging with Embarcadero

This problem is present in 11.2 trial or not.

OK - defo mention this in Tutorial

This will also be fixed by the settings config discovered today


Enable rolling deployment for non major upgrades

Describe the issue
As of the recent upgrades of RHSSO, the deployment strategy has been set to recreate. This force all small changes to result in service downtime.
Additional context

ocp template: https://github.com/bcgov/ocp-sso/blob/master/openshift/sso74-x509.yaml#L126
pipeline re-enforcement: https://github.com/bcgov/ocp-sso/blob/master/.pipeline/lib/deploy.js#L135-L138

Definition of done

update template to use rolling with proper configs
test in sandbox instance

https://github.com/bcgov/ocp-sso/pull/121


[BUG]: Workflows Scanner using SP Modernization Scanner Tool throwing error

SharePoint Modernization Scanner tool is throwing error while running.
Issue :
We have approx. 4000 teams sites. Among them we have successfully ran all the sites but there are 8 sites which is causing problem. whenever we are running these sites its throwing error. also not able to attached the screenshot here.
Error:
Index was outside of the bounds of the array.
Please note: we have downloaded and used the latest modernization tool.

@itk975 : the screenshot is not visible here, can you paste it again. Can you also ensure that you're only running the Workflow scan option (so not a full scan) to verify the issue is related to the workflow component of the scan.

Hi Bert,
Thanks for replying back.
Here is what I was trying
[image: image.png]
[image: image.png]
Thanks,
Abhishek
On Mon, Dec 7, 2020 at 10:05 AM Bert Jansen<EMAIL_ADDRESS>wrote:

@itk975
https://urldefense.com/v3/__https://github.com/itk975__;!!EFVe01R3CjU!PCcsk6AXKuxxjo8oC1XEBNseVFnkpeeOHTNMEUe24wUBOrovW2Z-estjR5bNB5LZKLQXjzw$
: the screenshot is not visible here, can you paste it again. Can you also
ensure that you're only running the Workflow scan option (so not a full
scan) to verify the issue is related to the workflow component of the scan.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/pnp/sp-dev-modernization/issues/559*issuecomment-739974638__;Iw!!EFVe01R3CjU!PCcsk6AXKuxxjo8oC1XEBNseVFnkpeeOHTNMEUe24wUBOrovW2Z-estjR5bNB5LZ-iRn2qQ$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ASA7PLTIBW2JWQLIYXQSFK3STTVJVANCNFSM4UQSO57Q__;!!EFVe01R3CjU!PCcsk6AXKuxxjo8oC1XEBNseVFnkpeeOHTNMEUe24wUBOrovW2Z-estjR5bNB5LZMf_OE0c$
.

--
Thanks & Regards,
Abhishek Nundy

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

@itk975 : Please add the screenshot in the GitHub UI...via mail you can't add screenshots

Hi Bert,
Not able to upload a screenshot. What file type is required?
Thanks,
Abhishek
On Mon, Dec 7, 2020 at 2:30 PM Bert Jansen<EMAIL_ADDRESS>wrote:

@itk975
https://urldefense.com/v3/__https://github.com/itk975__;!!EFVe01R3CjU!ITYdaOJMezJekEBSLGi5z5K7Cp6iNXs6lHKsboddAv8Byp7qREaaprOSu1EtVVrGeb0igbg$
: Please add the screenshot in the GitHub UI...via mail you can't add
screenshots
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/pnp/sp-dev-modernization/issues/559*issuecomment-740130939__;Iw!!EFVe01R3CjU!ITYdaOJMezJekEBSLGi5z5K7Cp6iNXs6lHKsboddAv8Byp7qREaaprOSu1EtVVrGcQEgI2k$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ASA7PLVXYRMBD7AUTPKPYCTSTUUNLANCNFSM4UQSO57Q__;!!EFVe01R3CjU!ITYdaOJMezJekEBSLGi5z5K7Cp6iNXs6lHKsboddAv8Byp7qREaaprOSu1EtVVrGOMo4qVk$
.

--
Thanks & Regards,
Abhishek Nundy

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

Every time it is saying Something went wrong and we cant process that file

Sens the screenshot to<EMAIL_ADDRESS>

Closing as we're following this one up via email

Hello,
Could someone tell me what was the fix for this, as I'm experiencing the same error message "Index was outside of the bounds of the array" when using a .csv file.  If i enter the URL of the SharePoint site, no error and is processed. I'm also seeing the same problem when using the newer "Microsoft 365 Assessment" tool, hence why i reverted to using the SharePoint Modernization scanner for evaluating my SharePoint environment's 2013 SharePoint workflows and Infopath forms.
Any help would be great.
Thank you,
Cindy


CLI payload decoding

We support custom en/decoders now, so this line which enforces payloads to be in JSON format, is wrong. That block should be moved to some helper function, which extracts the payload based on clap matches. The helper function should support multiple encodings (based on the encodings supported by the operation) and return the struct needed for the body.

This is blocking #22


Fix dependencies

Types of changes

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

Motivation and Context / Related issue

Koncept and Lpips are made optional
How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CLA).
[x] All tests passed, and additional code has been covered with new tests.

Feel free to add your thoughts and anything that might help. Any help is heavily appreciated!
It's my first time contributing to an open source project, looking forward to improve Nevergrad!

I also have one concern, that the tests run in my pc with pytest could not reproduce the outputs of the same tests in CircleCI. I do not know exactly why.


XML file without style

Hi,
The link news, in navbar class, returns a XML file without style.

This XML file does not appear to have any style information associated with it. The document tree is shown below.

Fortran Newsletter

2021-02-02T22:08:53+00:00
/news

Hi @aslozada, is there any part of the website that doesn't seem to work correctly? I can't find it. How do I reproduce the issue?

In the navbar, the link news, https://fortran-lang.org/news.xml, returns a XML file without style.

Hi @aslozada, are you referring to the RSS feed link?

Yes. In the "button" of RSS.

Ah okay, the xml file that it links to is intended to be read by an RSS reader and hence it will not display properly in a Web browser.

I'll close this issue as resolved.


rustup

@bors r+

:pushpin: Commit 4f5fe49cd8ceec9a4c0bfd93d47c3fa264ec33fc has been approved by oli-obk
It is now in the queue for this repository.

:hourglass: Testing commit 4f5fe49cd8ceec9a4c0bfd93d47c3fa264ec33fc with merge 8f939dbeaee67bd80cf8a13440825343d349cee1...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing 8f939dbeaee67bd80cf8a13440825343d349cee1 to master...


fix(utils): handle Markdown links with spaces to route correctly

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[x] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Fixes #8867
Links to Markdown files with spaces are routed to the original filename (i.e. they also keep the original file extension).
The problem is that existing regex for Markdown links doesn't match filenames that contain whitespaces and wrapped with <> .
Thus, here are changes I applied to the regex:

match links wrapped with <>
match spaces in filename

replaceMarkdownLinks method already replaces spaces with %20 in a link, therefore we are good to go here.
Test Plan

This issue can be tested using examples provided in #8867.
I have also added unit tests.
Test links

Deploy preview: https://deploy-preview-8874--docusaurus-2.netlify.app/
Related issues/PRs

#8867

LGTM thanks 👍
Note to self: it looks bad to me that we process links from string/regexp, we should probably handle that in a remark plugin instead. It's been like that for years.


Fix set dns to VIP in GCP

Codecov Report

Merging #625 (5825632) into master (c3f6023) will increase coverage by 0.00%.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##           master     #625   +/-   ##
=======================================
  Coverage   42.28%   42.28%
=======================================
  Files         321      321
  Lines       23122    23124    +2
=======================================
+ Hits         9778     9779    +1
- Misses      13344    13345    +1

Flag
Coverage Δ

unittests
42.28% <50.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

dbaas/workflow/steps/util/vip_provider.py
40.63% <50.00%> (+0.03%)
:arrow_up:

Continue to review full report at Codecov.

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


[yarac] Drive letter considered as namespace

Passing absolute paths on windows causes yara to omit the drive letter from the path and use it as a namespace, which could also result in using a wrong path:

Possible solution could be to restrict namespace length to a minimum of 2 letters and check that whenever a colon is found.

Fixed in 632a6ab2411ab9e296ce05224199f1e3927f487a


Possible tiny optimization for Python 3.9+

I noticed the call helpers use the public API Py_EnterRecursiveCall and Py_LeaveRecursiveCall but those are no longer macros/inline functions in Py3.9+. Assuming using the internal API is fair game (IIRC you use it already), you could use _Py_EnterRecursiveCall  and _Py_LeaveRecursiveCall instead.

This is deceipful code, but Nuitka does this:
#ifndef _NUITKA_FULL_COMPAT
// Remove useless recursion control guards, we have no need for them or we
// are achieving deeper recursion anyway.
#undef Py_EnterRecursiveCall
#define Py_EnterRecursiveCall(arg) (0)
#undef Py_LeaveRecursiveCall
#define Py_LeaveRecursiveCall()
#endif

So unless --full-compat is specified, it's not done, which is only happening when running Nuitka tests. This can in fact be improved however, my CI might like it.

Thanks for the explanation, and sorry for the noise. I thought this would be required for module mode (but not  for standalone).

It is still valid information, slowing down my CI is not a good thing either. It is just not generally all relevant outside of the CPython test suites, etc.
My hunt for API functions is on hold while I finish 3.11 compatibility now, but I will surely resume, and this made me aware to also consider --full-compat as a valid use case.

Ah, these macros want a tstate. But Nuitka is not yet good at passing it around sufficiently. I guess that means we would have to do our own variant there, but will then make this part of a bigger change that allows e.g. call code to have it passed by the raiser, such that e.g. Nuitka_CheckFunctionResult and others will have it more often. I need to convince myself of the cost that comes with PyThreadState_GET() and its use of _Py_atomic_load_relaxed vs. the cost of passing the pointer, I guess, in the general case without inlining chances, it has to be avoided. I will put this to delayed until I draw the line for exception handling specifically, and if e.g. framed code, would get and store this pointer where there is no chance of switching threads (i.e. outside of generators, coroutines, asyncgen). Then this will be solvable easily.

The macros are themselves creating a tstate, doing the check there, only the error itself is reported via an API call, which would be fine. In the new code, rather than a macro, an inline function is used, which is acceptable, same effect as a macros. The fact that no tstate is passed, doesn't appear to be much of an issue, no caller seems to close to having it.
I do not believe that there should be a considerable slowdown from this. I will check out --full-compat specifically when I try to look at API calls next time. But I do not believe there is this issue. For 3.11 I do not think I did it yet that tracing, so probably I can combine that.
But generally, I do not think this is a real optimization improvement.


DbtRuntimeError.init() missing 1 required positional argument: 'msg'

Describe the bug
I am having this error message when trying to build both materialized tables and incremental tables. The funny thing is that sometimes I am able to build the tables and sometimes I get this error message.
DbtRuntimeError.__init__() missing 1 required positional argument: 'msg'

    > in macro materialization_table_clickhouse (macros/materializations/table.sql)
    > called by model stg_transaction_event_card (models/prd/staging/stg_transaction_event_card.sql)

When successful, the table is build with all the data. But when it fails, an empty table is created in my database.
Steps to reproduce
For materialized tables

profiles.yaml

local_clickhouse:
      type: clickhouse
      schema: warehouse_dev
      user: "{{ env_var('CLICKHOUSE_USER') }}"
      password: "{{ env_var('CLICKHOUSE_PASS') }}"
      port: 9000
      host: localhost
      cluster: default
      retries: 1
      connect_timeout: 10
      send_receive_timeout: 3600 # 1hr

stg_transaction_event_card.sql example code:

{{
    config(
        materialized = "table",
        engine = "ReplicatedMergeTree",
        unique_key = "transaction_id",
        pre_hook = "TRUNCATE TABLE IF EXISTS {{ this }} ON CLUSTER default",
        indexes=[
          {'columns': ['transaction_id'], 'type': 'btree', 'unique': True },
          {'columns': ['last_mod'], 'type': 'btree'}
        ]
    )
}}

WITH txns_events AS (
    SELECT
        col1,
        col2,
        col3
    FROM postgresql('host:port', 'db_name', 'table_name', 'db_user', 'db_password', 'schema')
)

SELECT
    col1,
    col2,
    col3
FROM txns_events

For incremental tables

profiles.yaml

local_clickhouse:
      type: clickhouse
      schema: warehouse_dev
      user: "{{ env_var('CLICKHOUSE_USER') }}"
      password: "{{ env_var('CLICKHOUSE_PASS') }}"
      port: 9000
      host: localhost
      cluster: default
      retries: 1
      connect_timeout: 10
      send_receive_timeout: 3600 # 1hr
      use_lw_deletes: true

stg_transaction_event_card.sql example code:

{{
    config(
        materialized = "incremental",
        unique_key = "transaction_id",
        indexes=[
          {'columns': ['transaction_id'], 'type': 'btree', 'unique': True },
          {'columns': ['last_mod'], 'type': 'btree'}
        ]
    )
}}

WITH txns_events AS (
    SELECT
        col1,
        col2,
        col3
    FROM postgresql('host:port', 'db_name', 'table_name', 'db_user', 'db_password', 'schema')

    {% if is_incremental() %}

         AND (last_mod > (SELECT max(last_mod) FROM {{ this }}))

    {% endif %}
)

SELECT
    col1,
    col2,
    col3
FROM txns_events

Configuration
Environment

dbt version: dbt-core=1.4.6
dbt-clickhouse version: dbt-clickhouse=1.4.2
Python version: Python=3.11.4
Operating system: M1 Mac

It looks like there's a bug in error message handling/logging that keeps you from seeing the underlying ClickHouse exception  I've pushed a fix for that in the new release 1.4.4.  My guess is that's hiding the real error message which might be related to some Postgres issue.  If you can try the 1.4.4 dbt-clickhouse version that might point to the root cause.
You might also check your ClickHouse server logs for related errors.

That looks like a network error in the underlying HTTP request from dbt to your ClickHouse server.  How long does this select usually take?  Where is the Clickhouse server you are connecting to?

Oh, you're doing this on localhost, so it's probably an error between your localhost and the Postgres server?

The query takes around 20 - 25min for materialized=table. For incremental it takes 1min and 30seconds approx. But I don't understand why there is an error between my localhost and Postgres when using WITH statements specifically. @genzgd

It could just be a coincidence.  Unfortunately the error still doesn't provide much information once it's been processed through several DBT layers.   You could try running the same query using just the underlying python client (clickhouse-driver if you are using native protocol over port 9000, clickhouse-connect if you are using http over port 8123).  The error is currently coming directly from the clickhouse-driver query so you should see the same thing with hopefully more information.
Does the DBT debug log show anything in addition to that error message?

Found my issue!

So, basically it wasn't an error on the network, it was a memory issue. Scaling my memory did the work!
Other people also suggested updating send and receive timeout as well as max_insert_threads.

Found my issue!

So, basically it wasn't an error on the network, it was a memory issue. Scaling my memory did the work!
Other people also suggested updating send and receive timeout as well as max_insert_threads.
In addition, something I discovered is that, it doesn't matter if my CTE has filters (such as date >= 'YYYY-MM-DD'), clickhouse will load all the data. Hopefully this is useful for someone to check if they are also running out of memory.


DOI for ANTsR

We could get a DOI for ANTsR and make the whole software citable. Objections?
Step by step guide:
https://guides.github.com/activities/citable-code/

Not sure if we should do this or go for a proper publication in JSS or
similar.  Brian--do you have thoughts?
On 11 February 2015 at 09:44, Arman Eshaghi<EMAIL_ADDRESS>wrote:

We could get a DOI for ANTsR and make the whole software citable
https://zenodo.org. Objections?
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11.

i would prefer to try http://www.jstatsoft.org/
brian
On Wed, Feb 11, 2015 at 9:50 AM, bkandel<EMAIL_ADDRESS>wrote:

Not sure if we should do this or go for a proper publication in JSS or
similar. Brian--do you have thoughts?
On 11 February 2015 at 09:44, Arman Eshaghi<EMAIL_ADDRESS>wrote:

We could get a DOI for ANTsR and make the whole software citable
https://zenodo.org. Objections?
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11.

—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73892903.

That would be excellent...

Just to add that jss can take a while if you want something in the interim I have used zenodo.org.
Sent from my iPad

On 11 Feb 2015, at 06:44, Arman Eshaghi<EMAIL_ADDRESS>wrote:
We could get a DOI for ANTsR and make the whole software citable. Objections?
—
Reply to this email directly or view it on GitHub.

interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/

another fantastic reference:   http://www.sciencedirect.com/science/article/pii/S0167947308001606

My inclination is that it's worth it to do it "properly" and get it up to
JSS standards, and then have one unambiguous place to cite, even if it
takes a few months more to get out.  We've invested enough time in this
package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava<EMAIL_ADDRESS>wrote:

interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.

agreed ... and it's good to know, now, what the "beyond cran" standards of
jss are ....
brian
On Wed, Feb 11, 2015 at 4:04 PM, bkandel<EMAIL_ADDRESS>wrote:

My inclination is that it's worth it to do it "properly" and get it up to
JSS standards, and then have one unambiguous place to cite, even if it
takes a few months more to get out. We've invested enough time in this
package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava<EMAIL_ADDRESS>wrote:

interesting comments here:
http://robjhyndman.com/hyndsight/jss-rpackages/
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.

—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73964460.

nice blog post for JSS standards, definitely worth the time, I'm sure we
will all be learning lots of things in the process (as I have already
learned a lot). Am happy to work on this even if it takes a year or so
On Thu, Feb 12, 2015 at 12:34 AM, bkandel<EMAIL_ADDRESS>wrote:

My inclination is that it's worth it to do it "properly" and get it up to
JSS standards, and then have one unambiguous place to cite, even if it
takes a few months more to get out. We've invested enough time in this
package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava<EMAIL_ADDRESS>wrote:

interesting comments here:
http://robjhyndman.com/hyndsight/jss-rpackages/
--
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.

--
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/issues/11#issuecomment-73964460.


Add testing and CI infrastructure

From @mosheBelostotsky
Here is how to connect any NPM project to use our pipeline (I will also document this in KB and sharepoint)
This is based on current pipeline functionality without any change

Copy Jenkinsfile from hubot-enterprise into your project root
Edit package package.json

devDependencies:

add jenkins-mocha and jshint to  devDependencies

add to scripts (assuming project not using coffeescript):

“coffeelint”: “return 0” (or anything else that does not throw an error)
“jslint”: "jshint --exclude-path .gitignore --reporter=jslint .> js-lint.xml || true" (add flags for es6 support, if needed: https://www.npmjs.com/package/jslint)
"test": "ARTIFACTS_DIR='./' COVERAGE_DIR='./' TEST_DIR='./test/' jenkins --check-leaks --no-coverage test/**/*.js || true"

Docker autobuild-

follow instructions in wiki: https://github.com/eedevops/hubot-enterprise/wiki/jenkins#dockerhub-autobuild
If autobuild already exists: change only “build settings” according to the wiki above

Done.


doc: update readme.md

Resolve #17
Signed-off-by: Yi Zha<EMAIL_ADDRESS>

@toddysm @iamsamirzon @FeynmanZhou I have resolved your comments, please review this PR again. Thanks.


Queue not created as durable despite "Durable?" checkbox being selected

Hello,
I have tested with the "Durable?" checkbox either being selected or not, and the queue is not ever being created as "Durable".  If the checkbox is selected, the queue is created as "excl" (Exclusive).
Graylog version 2.4.3
RabbitMQ version 3.6.11

You are setting the "Durable" parameter in the wrong spot
From the RabbitMQ docs https://rabbitmq.github.io/rabbitmq-java-client/api/4.x.x/com/rabbitmq/client/impl/recovery/AutorecoveringChannel.html#queueDeclare(java.lang.String,boolean,boolean,boolean,java.util.Map)
public AMQP.Queue.DeclareOk queueDeclare(String queue, boolean durable, boolean exclusive, boolean autoDelete, Map<String,Object> arguments) throws IOException
You can see here that the "durable" boolean is the 2nd parameter.
From your code:  https://github.com/nexylan/graylog-rabbitmq/blob/master/src/main/java/net/nexylan/graylog/rabbitmq/senders/RabbitMQSender.java
Line 93:
this.channel.queueDeclare(this.queue, false, this.durable, false, null);
You can see here that "Durable" (the 2nd parameter) is always being set to false, and instead of setting "Durable" you are setting "Exclusive" using the " this.durable" boolean value.

Hello,
Well done ! I will give a look this week to publish a bugfix,
Happy new Year ! :)
Best regards,


Lumen compatibility

I understand the readme states this is for Laravel 5, but the service provider has a conditional for Lumen applications. This might just be an artifact from a boilerplate service provider you use for new packages but I thought I should point out that it will not work with Lumen applications.
The first issue Lumen runs into is on line 63 where it attempts to call registerLocker with the application parameter being an instance of Laravel\Lumen\Application instead of the expected Illuminate\Contracts\Foundation\Application. Lumen also runs the same type-hinting problem with setupConfig after the previous issue is resolved.
While Laravel's application class (Illuminate\Foundation\Application) does implement Illuminate\Contracts\Foundation\Application (what this package type-hints), Lumen's application class (Laravel\Lumen\Application) does not. They do, however, both extend Illuminate\Container\Container - though I don't think type-hinting that would be correct given the methods being called on it are not from that class.
If you plan to support Lumen in the future, you might want to make a separate service provider just for Lumen. Additionally, if Lumen becomes supported, it might be worth mentioning in the readme that illuminate/redis is a required dependency (Lumen does not include this out of the box) and that you need to have the database config loaded ($app->make('db') will do this, though that's overkill if you don't need Eloquent) prior to Illuminate\Redis\RedisServiceProvider being ran.

Having redis missing is NOT an issue. You MUST install that yourself if you want it.
In terms of the application typehints, I'm going to fix them on ~40 packages including this one at the weekend.

Good point on illuminate/redis. I didn't see that it was just a Predis client instance that was required.


Support relative toolchain filepath

forwarding absolute path from CMAKE_TOOLCHAIN_FILE since hunter build directory isn't the same as user's

Okey I remove the changes on these two files

Have you actually test it? Doesn't seem to work, I think HunterGate should be updated too.

nop
I'm testing now with modified HunterGate

with modified HunterGate

You should open pull request to HunterGate too. This change make no sense without HunterGate update.

just editing the HunterGate seems to fix our build, I created a PR : https://github.com/hunter-packages/gate/pull/15

I created a PR : hunter-packages/gate#15

Merged

just editing the HunterGate seems to fix our build

Same for me. Closing?


tests: improve coverage

Codecov Report

Merging #171 (5f57b86) into main (4159cfb) will increase coverage by 1.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #171      +/-   ##
==========================================
+ Coverage   79.14%   80.25%   +1.11%
==========================================
  Files          20       20
  Lines        2474     2472       -2
==========================================
+ Hits         1958     1984      +26
+ Misses        516      488      -28

Impacted Files
Coverage Δ

taos/cinterface.py
79.15% <100.00%> (+2.70%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add authentication system for the water level dashboard users

Is your feature request related to a problem? Please describe.
Preventing anonymous users see the water level
Describe the solution I'd like
I want to add an user authentication system (Email Password login , reset password ) using google firebase
alternatives I've considered
Alternatively can be done with php, Mysql
Please assign me in this i can do this

@vinitshahdeo
@ShreyaAnand
please respond

@ayan-biswas0412 Hey, are you a participant of GSSoC?

Yes I am a Participant

@ayan-biswas0412 please start working on this issue. It's now assigned to you.

Thank you i will surely do that

If you have made a PR for this issue, please refer it to this issue.

If you have made a PR for this issue, please refer it to this issue.
I have already mentioned this issue

Can i move forward with this issue? i can authenticate it with express server including SIgn-up  and Log-in feature.

@vinitshahdeo please respond

@kishankr7979  Yes, you can.
Assigning you to the issue.

Hey can I contribute in the issue under SWOC ?

Hey can I contribute in the issue under SWOC ?

@kishankr7979 Are u working on this?

@kishankr7979 Are u working on this?

@nandikajain Already requested a PR

@nandikajain Already requested a PR

With a Authentication code and description

With a Authentication code and description


Get the foss-eda-tools.googlesource.com mirror happening

Seems to be working at https://foss-eda-tools.googlesource.com/globalfoundries-pdk/libs/gf180mcu_fd_sc_mcu7t5v0/


Show audio muted OSD image when audio volume value is 0

Currently, if you reduce the volume to zero, the OSD image is still the non-muted audio speaker, even though the volume is muted.
This change will set the OSD image to the muted audio speaker if the volume becomes zero.

I'd like to wait for this one for #245 as they will inevitably conflict.

Made a small change to clean up duplicated logic from #245 in the conflicting code, encapsulated in last commit in this branch. Feel free to blow that commit away if it should be in a separate PR - the change to show the audio muted image is code-complete in the first commit.

@JoniVR: Were there any more changes I needed to make before this gets merged? Been open a little while now.

Code looks good to me, I just haven't had the time to test it yet. I'll try to find some time to review some PRs when I can soon, sorry about that.
Thanks for all the work you've been putting in though 😃


Correct function name for HipChat APIv1 response check.

checkResponseCodeForRoom -> check_response_code
Using HipChat API v1 would cause any fastlane execution to throw an error when attempting to send a HipChat message due to checkResponseCodeForRoom being undefined. Updated function call to the defined function name.

Thanks! Will be in the next release :+1:


Add LICENSE file

The MIT requires full license text to be present (fixes #66)
@naterkane @sokra Particular license terms matter (citing from https://github.com/babel/babel/pull/7308#issuecomment-367686736):

legally, it is not satisfactory to have the license name alone in the package.

This is also explicitly required by some licenses in order for it to take effect, such as ICS, Apache 2.0, all GNU licenses and MIT.

The MIT license requires that "the above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." By including the license in the source file, you have met this obligation.

Not specifying the license text in each package restrictedly means that no one may reproduce, distribute, or create derivative works from your work. The name of the license alone does not "apply" the license, hence it retains the default license instead.

without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.

@sokra I just stumbled upon this one and it seems like it is a similar case as https://github.com/webpack/loader-runner/pull/27#issuecomment-417679141 😞

Thanks

@sokra thank you very much.  Any plan for release date ?


Refactor react context

At the moment we are accessing the react context via two methods: consumer and hooks,
Generally we should be using one method for consistency (probably hooks),
We are also exposing the context at the top most app level, we may wish to restrict this to certain components,

fixed by #21