duplicate error logs into a separate file

What type of enhancement is this?
User experience
What does the enhancement do?
Currently, the runtime log will be output to stdout and file: https://github.com/GreptimeTeam/greptimedb/blob/d0ef3aa9eb4fb5e77a8060dc7f6ca2b55f28a730/src/common/telemetry/src/logging.rs#L97-L101
Both consumers are holding all the logs with valid levels. E.g., if the level is set to INFO, then all the ERROR, WARN and INFO logs will present in stdout and log file.
It would be useful if we could duplicate some important logs separately. Like only placing ERROR level in error.log, and ERROR, WARN and INFO in the normal log file like we have present. tracing provides such functionality with_filter which allows setting per-layer filter. I tried it and successfully separated the ERROR log in the stdout (left), while still keeping the full content in the log file (right).

Implementation challenges
No response

Today on slack, I received a New Year's gift from GreptimeDB community, which is very happy. Rust Hong persuaded me to withdraw an issue before, but I am still learning and do not give up. I want to try to complete this issue, I may encounter many problems, but I will not give up, please assign it to me, thanks!

Hi @azhsmesos, just a friendly ping, do you have any progress or problems to share?

Hi @azhsmesos, just a friendly ping, do you have any progress or problems to share?

Sorry, I am still in the Spring Festival holiday, not yet developed

Wish you a wonderful holiday 🎆  As it has been over a month since assign, we'd release this task and make it up for grabs. Feel free to retake it when you get back to work

Let me take it.


Replication

Setup a postgres cluster automatically, the number of slaves can be scaled.

@ant31 Could you please have a look at this PR ?

@ant31 I just noticed that for the shards it creates a directory named "/etc/k8s/manifests/postgres/etcd-1/postgres-slave-rc.yaml". I don't know where the string "etcd" is inserted.

@Smana be sure to have k8s-common up-to-date.
directory should be {{shard_prefix}}-{{shard_name}}

Tested several times, it works great :)
Let me know if you see any possible improvements.


KAFKA-17011: Fix a bug preventing features from supporting v0

As part of KIP-584, brokers expose a range of supported versions for each feature. For example, metadata.version might be supported from 1 to 21. (Note that feature level ranges are always inclusive, so this would include both level 1 and 21.)
These supported ranges are supposed to be able to include 0. For example, it should be possible for a broker to support a kraft.version between 0 and 1. However, in older software versions, there is an assertion in org.apache.kafka.common.feature.SupportedVersionRange that prevents this. This causes problems when the older software attempts to deserialize an ApiVersionsResponse containing such a range.
In order to resolve this dilemma, this PR bumps the version of ApiVersionsRequest from 3 to 4. Clients which send v4 promise to be able to handle ranges including 0. Clients which send v3 will not be exposed to these ranges -- the feature will simply be omitted from the response. This work is part of KIP-1022.

Did we check the kraft upgrade system tests? I can kick off a job. Looks like there may also be some issue with the build.

It seems simpler to just pass the ApiVersionsResponse version as a parameter to the Supplier (hence making it a Function, I guess)
Updated.

Let's take a look at  testUnsupportedApiVersionsRequestWithVersionProvidedByTheBroker

It looks like the test was checking the ApiVersionsRequest header version against 3. So it needed to be updated to 4

The test failures pass locally.

https://github.com/apache/kafka/pull/16183 will wait for this PR in order to not break tests.

Looks like there are still quite a few failures for ApiVersionsRequestTest and BrokerFeaturesTest

The context here is that we’re adding kraft.version in 3.9. But not in this PR. I did add kraft.version to supportedFeatures, simply so that I could verify that the RPC results looked like what I wanted. This will cause no compatibility problems since there is no way to set kraft.version yet.

Test failures are unrelated. I will merge.


ValueError: Prepared geometries cannot be operated on

Expected behavior and actual behavior.
My script throws a ValueError: Prepared geometries cannot be operated on in a LineString intersects call
This only happens when the following conditions are met:

the method performing the intersects  call is called several (100?) times
the linestrings used in the intersects call are generated using a random function

Steps to reproduce the problem.
See https://gist.github.com/atlefren/d106fb2cc470844d9006fd0e4f580950
Operating system
Windows subsystem Ubuntu 16.04.5 LTS
Shapely version and provenance
1.6.4.post2 installed from PyPI using pip

The exception comes from https://github.com/Toblerity/Shapely/blob/4433a841d379044bdca0a891f8fe79c6eed4e06d/shapely/topology.py#L19-L20. The exception is misleading in your case. I think that if you filter out the objects that aren't geometries (have no type) you can avoid this error.

@sgillies Thanks! That cleared it up somewhat, as I could not understand what prepared geoms had to do with this.
However, if I change the intersetcs call in my sample (line 30), to this:
intersects = True
if hasattr(line_so_far, 'type') and hasattr(new_segment, 'type'):
    intersects = line_so_far.intersects(new_segment)i

I still get the error. It's like the type gets erased somehow between my call to intersetcs and the check in topology.py.
Not sure if this is a Shapely bug or my code. Tried replacing the recursive call with a while-loop, then the type is always set. Does Python do something strange with recursion?


add support for unicode exponents in units

This change allows to use and intermix unicode and ascii exponents in short units.
#11

Sorry for taking a long time and thank you for your contribution.


initial build and test pipeline using actions

Linux/Mac test runs?

Linux/Mac test runs?

yes, I'm adding those now.


Add BuiltWithAppwrite to pages.json

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests / types / typos

Description
Add a new project to list of showcase projects. It's web BuiltWithAppwrite, which uses Qwik and Pink Design.
Use cases and why
x
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] Added new tests to cover the fix / functionality

Hi @Meldiron 👋
Thanks for this submission 🙏  nice page and great (synthetic) [PSI Scores(https://pagespeed.web.dev/analysis/https-builtwith-appwrite-io/mc3t9iya1r?form_factor=mobile)


Unable to configure for self hosted instance.

https://github.com/codecov/codecov-browser-extension/blob/0a395bfb6e35dc0eb958d70ba176c40aed70d54a/src/service.ts#L15
Current auth check logic seems to assume that the github user codecov would exist in the server. But in the case of self hosted that is not the case.
As is the api call will return a 404 and the extension will fail to initialize.
These json blobs are the logs from the actual containers of my instance.
{
    "message": "Not Found: /api/v2/github/codecov",
    "asctime": "2024-01-29 21:25:37,486",
    "name": "django.request",
    "levelname": "WARNING",
    "lineno": 241,
    "pathname": "/usr/local/lib/python3.9/site-packages/django/utils/log.py",
    "funcName": "log_response",
    "threadName": "MainThread",
    "status_code": 404,
    "request": "<WSGIRequest: GET '/api/v2/github/codecov'>",
    "logger.name": "django.request",
    "logger.thread_name": "MainThread",
    "level": "WARNING"
}

{
    "remote_address": "<IP_ADDRESS>",
    "request_time": "[29/Jan/2024:21:25:37 +0000]",
    "request": "GET /api/v2/github/codecov HTTP/1.1",
    "status_code": "404",
    "response_length": "23",
    "referer": "-",
    "useragent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
}

Using that service.ts file as a guide I am able to poke at it with curl to see the body of the reply as well as test it with a different username to confirm what a 200 reply would look like.

looks like just removing the username may be sufficient for testing the auth token provided.


how to manually render between updates?

I'm refactoring my code to replace Engine.run with calling Engine.update a pre-set number of times instead. However, I could not get the rendering to work.
I've created the engine as follows:
engine = Engine.create(document.getElementById('canvas-container'));

and I'm attempting to simulate 1 second of a box falling as follows:
var boxA = Bodies.rectangle(400, 200, 80, 80);
World.add(engine.world, [boxA])
console.log(boxA.position)
var n = 0
while(n < 100) {
  Engine.update(engine, 10.0)
  n = n + 1
}
console.log(boxA.position)

From the log I observe the box has correctly been falling through the updates, but it'll be nice to actually see it as well. How might I render it? I tried calling engine.render.controller.world(engine) after every update, but the result seems buggy. Thanks!!

Try using [Runner.create](http://brm.io/matter-js-docs-master/classes/Runner.html#method_create] and Runner.tick which will update and render etc. but don't use Runner.run.

thanks it did the trick for me. here's what I'm using now.
// animate n key frames with 100 ms delay
function animateN(n) {
  var cur_frame = 0
  function animate() {
    if (cur_frame < n) {
      Runner.tick(runner, engine, 100)
      cur_frame += 1
      setTimeout(animate, 100)
    } else {
    }
  }
  animate()
}


Legal pages

This adds the terms and conditions and cookie pages, ported from the previous app.
Dumping a load of HTML into the locale file doesn't seem ideal, but breaking down each paragraph of legalese would be pointlessly onerous.

LGTM! Rebase?


Added some text

Added some general info.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

While interesting, I don't think this really adds anything to the article. We are marking this PR invalid for Hactoberfest as it does not follow the recommended guidelines below:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove white space / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


Created File.py

Related Issues or bug

Info about Issue or bug

Fixes: #[issue number that will be closed through this PR]
Proposed Changes

Info about changes Goes here

Additional Info

Anything related Issues

Screenshots

Original
Updated

original screenshot
**updated screenshot **

Just testing...


Add ubuntu latest

Thanks @pi-314159 for this PR proving that the delayed docker login works. I had to create #84 though as it contains all components that sub projects beyond boringssl and liboqs need. I did add you as a contributor there: Hope that's OK (and to close this PR then without merge)?!

I'll update BoringSSL next week


Added Edit button

I have added an edit button to the page template allowing for direct edit of given page in GitHub
Unfortunately I see no other way than pulling whole default mdbook index.hbs and editing it inline.
At least it was possible to avoid pulling the book.js also...
This should resolve: https://github.com/brson/rust-cookbook/issues/82 but please note that it is my first time editing javascript so the solution might not be ideal.

Nice! I don't know javascript either so we'll just see whether anyone complains.


feat: replace ngrok for boulder

I will merge this PR for now, so anyone could play with this new structure and maybe could suggest bugfixes and improvements


chore: switch to modules and update RDF/JS packages

Closes #45

LGTM I merged it into the next branch where all breaking changes of the Next milestone are collected. I created a separate Next Features milestone for non-breaking changes, which can be shipped later.


add on_missing argument to EpochsArray

As on_missing's default is set to 'error' on BaseEpochs, EpochsArray will always raise a "ValueError: No matching events found for ..." when epochs are not found in some condition. This is not always desirable, so control on_missing from EpochsArray would be very useful.

Sounds reasonable to me, can you make a PR?

yep, I can!
...as I was super lazy with PR #3965 (I work in my master instead of branching), I will wait for that PR first. I never thought I'd be doing another PR so soon... shame on my 😞


Round robin DNS pooling?

I've been looking at helixdns for a project of mine and was wondering if it supports round robin style pooling of IP addresses. Is this supported?

+1
@mrwilson I'd like to store a list instead of a string so an A query gets multiple A records


Add lowercase property to Button

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
It is specified in the Material design spec that Container Button can be sentence cased: https://material.io/components/buttons/#contained-button
It would be nice to add a sentenceCase property.
Examples 🌈
<Button sentenceCase>My button</Button>

@lcswillems Use customizations for this problem.

This is what I do but why? Customizations are for changing the spec. It doesn't make sense for me to have to implement the spec manually.

I think that it boils down to how frequently would you use it? It opens the door to inconsistencies in your UI. I doubt we need a prop for it.

text-transform

@lcswillems Use customizations for this problem (text-transform).

Hi, How do this?

<Button>
        <Typography textTransform={'lowercase'}>some lower case text</Typography>
</Button>

You can simple do this.


Python Template v2

This PR introduces a new version of the Python Template. The main differences are:

Deprecated Python 2 support.
Provide support for both setuptools and poetry, allowing to select which one to use during the cookiecut process.
When using setuptools, consolidate most of the configuration files under setup.cfg.
Moved the tests directory outside the python product.
Remove all utils code and instead use sdsstools.
Allow to choose between two Sphinx themes for the documentation.
Updated the documentation and the coding style guide.

The documentation has been built here.
The idea would be to merge this to master and make it the default cookiecut template. The previous version would still be available by doing
cookiecutter https://github.com/sdss/python_template.git --checkout python-template-v1

Fixes #15
Fixes #17
Fixes #18
Fixes #19
Fixes #20

I agree overall with looking into other options for logging, and maybe not make the sdsstools log tool a default, but let's explore that for v3.


chore: refactor prisma tx

Title

Changes 👷♀

push all product hub update operations to one prisma transaction

How to test 🧪

- step 1 ...

Merged with #2683


Python module requests for Py2 and Py3

Description
We have to have vendorized requests with dependencies for Python 2 hosts as current version is outdated.
[cuID:OP-2589]

With merging of Kitsu integration, this is now priority as currently we have broken build process.

Crap, I didn't notice that when merging.

Resolved with https://github.com/pypeclub/OpenPype/pull/3305


ProfilingPlugin produces malformed JSON

Bug report

What is the current behavior?
When running webpack with ProfilingPlugin, the resulted JSON is malformed. To be precise, the end of file looks following:
61,97,109,128,131,177,95,126,136,134,122,233,42,132,128,138,210,113,127,160,144,200,67,128,137,100,166,113,139,75,160,86,140,137,160,106,128,193,118,103,172,50,130,204,89,123,142,207,138,209,139,236,26,127,146,115,126,126,180,99,111,125,159,119,158,97,110,151,117,135,125,126,143,110,110,121,132,127,206,58,132,147,132,125,130,166,99,168,156,106,129,103,127,146,387,154,235,163,137,122,139,130,217,54,129,109,132,138,123,162,79,130,125,136,121,140,128,126,126,135]}}}},

So looks like the output just cuts off. the resulting file size over 200 MB in size.
If the current behavior is a bug, please provide the steps to reproduce.

run webpack using dev server (not sure if that's related)
shut down webpack
see the result: not valid JSON.

What is the expected behavior?
Output should be valid JSON that's compatible with Chrome profiler.
Alternative would be to provide enough instructions in documentation on how to run profiler proerly.

Other relevant information:
webpack version:  4.31.0
Node.js version: v10.15.0
Operating System: MacOS 10.14.4
It might be related to what this guy is hitting, i'm also getting the same error (at least when running with devserver): https://github.com/webpack/webpack/issues/6767#issuecomment-384713454

Can you create minimum reproducible test repo?

@evilebottnawi Actually now when I started to work on minified repro and built just one file, it looks like Chrome eats the malformed output just fine and shows profiling info like it should. I'm suspecting that in my case the file size is too large for Chrome profiler in this case.
Are there other ways to profile webpack performance than the plugin?

@villesau effective only this plugin

Ok, thanks! To be honest, I don't know if chrome dev tools are actually expecting malformed JSON. At least the profiler can deal with it so it's not a big problem I think. The actualy problem might be in produced file size. This might be the same issue I'm actually experiencing: https://github.com/webpack/webpack/issues/7689
Another bug I encountered: https://github.com/webpack/webpack/issues/9114

@villesau anyway, can you create minimum reproducible test repo (ensure problem not in webpack)

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!


IR Headers distorted due to plugin

Hi,
If you scroll down in your demo page, you will see headers of IR are distorted. See the attachment.

Thanks
Sunil Bhatia

Dear Sunil,
I tested on Chrome, Firefox, Safari and Opera. I don't see this behaviour.
Regards,
Richard


fix: corrected to appropriate error message

Description

Fix error messages to appropriate ones.
Since this is the part where you get the callee address, I modified the error message as follows.
https://github.com/Finschia/cosmwasm/blob/4f0efc49898794ff9d97071da4683e6b103867f7/contracts/call-number/src/error.rs#L10-L11
Closes #319
Types of changes

[ ] Bug fix (changes which fixes an issue)
[ ] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[x] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] The PR title and commits are followed conventional commit form.

It looks enum's case name StorageError does not need to be changed, and only replacing the error message "Storage does not have the number" with "Storage does not have the address" is enough.

It looks enum's case name StorageError does not need to be changed, and only replacing the error message "Storage does not have the number" with "Storage does not have the address" is enough.

Why?
Since another contract defines an enum with the same name, it does not seem like a good decision to use the same name and change only the error message.
https://github.com/Finschia/cosmwasm/blob/db084956732e1d1c101e7e9f7d0f92a734b6e633/contracts/number/src/error.rs#L10-L11

@loloicci
I will adopt this Storage does not have the address, thank you!


RestFulModelAdmin incompatibility with from django.contrib.admin.ModelAdmin

I realise that RestFulModelAdmin isnt currently supposed to be used like a normal admin.ModelAdmin, however,
a) it is confusing/misleading to explain that people should create these beasts in "admin.py" and have the class ending with ..ModelAdmin
b) it is misleading to even say that django-restful-admin (current) is "Expose Django's admin as a RESTFUL service", or use "admin" in the name, as it doesnt use any part of django.contrib.admin afaics, and were it is asserted was wrong https://github.com/amirasaran/django-restful-admin/pull/8
c) there is a richness within the Django ModelAdmin that django-restful-admin can use to great effect to provide a great REST api, especially all of the Django admin apps which enhance Django Admin, some of which should enhance  django-restful-admin also.  Some of the "Todo" in the README indicate that Django Admin features would be integrated.
So with that in mind, the first step would be to decide whether the restful admin is going to become part of the typical admin class, or be separate with a link to the typical admin class.
This issue is about the former of those options, as I feel that is neater. (There is one significant reason against it, that DRF will instantiate "duplicate" instances because it thinks they are viewsets, but that can be prevented with python magic)  The latter implies a need to create a lot of additional classes which are actually just specialised DRF viewsets, in which case I should just use DRF viewsets and the extremely large collection of helpers that exist for normal DRF viewsets.
So if I define
class MymodelAdmin(admin.ModelAdmin, RestFulModelAdmin):
    ...

admin.site.register(Mymodel, MymodelAdmin)
api_admin.site.register(Mymodel, MymodelAdmin)

And I run drf-spectacular to generate a schema, I get the following error
Traceback (most recent call last):
  File "manage.py", line 52, in <module>
    main()
  File "manage.py", line 48, in main
    execute_from_command_line(sys.argv)
  File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "adhoc_deps/before/django_compat_patcher/fixers/django1_10.py", line 411, in run_from_argv
    original_run_from_argv(self, argv)
  File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 328, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.8/site-packages/django/core/management/base.py", line 369, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python3.8/site-packages/drf_spectacular/management/commands/spectacular.py", line 50, in handle
    schema = generator.get_schema(request=None, public=True)
  File "/usr/lib/python3.8/site-packages/drf_spectacular/generators.py", line 175, in get_schema
    paths=self.parse(request, public),
  File "/usr/lib/python3.8/site-packages/drf_spectacular/generators.py", line 135, in parse
    for path, path_regex, method, view in self._get_paths_and_endpoints(None if public else request):
  File "/usr/lib/python3.8/site-packages/drf_spectacular/generators.py", line 117, in _get_paths_and_endpoints
    view = self.create_view(callback, method, request)
  File "/usr/lib/python3.8/site-packages/drf_spectacular/generators.py", line 84, in create_view
    view = super().create_view(callback, method, request)
  File "/usr/lib/python3.8/site-packages/rest_framework/schemas/generators.py", line 192, in create_view
    view = callback.cls(**getattr(callback, 'initkwargs', {}))
TypeError: __init__() got an unexpected keyword argument 'suffix'

getattr(callback, 'initkwargs', {}) is returning {'suffix': 'List', 'basename': 'mymodel', 'detail': False}
I can work around this by changing the admin class a bit
class MymodelAdmin(RestFulModelAdmin, admin.ModelAdmin):
    def __init__(self, model=Mymodel, site=admin.site, **kwargs):
        RestFulModelAdmin.__init__(self, **kwargs)
        admin.ModelAdmin.__init__(self, model, site)

The could be avoided if RestFulModelAdmin.__init__ understood model and site args, and also understood that it should not pass viewset specific args shouldnt be used when invoking `the super.__init__1

I have been using ViewSet as ModelAdmin because I can do anything that I want with ApiView.
I can customize serializing, add pagination, add filters, and support any things that I want.
You have a Good Idea and if you can do it I'm happy to hear from you. and this repository is open to merging your pull requests.
With the next version, we can implement support Django default admin customization.

If you can get a test suite started (c.f. https://github.com/amirasaran/django-restful-admin/issues/11), I'll make RestFulModelAdmin a normal django.contrib.admin.ModelAdmin subclass, and then you can integrate features from django.contrib.admin.ModelAdmin.

If you can get a test suite started (c.f. #11), I'll make RestFulModelAdmin a normal django.contrib.admin.ModelAdmin subclass, and then you can integrate features from django.contrib.admin.ModelAdmin.

@jayvdb
I suggest you create a mixin class instead of a subclass for more flexibility.

On mixin vs subclass, that is irrelevant.  Re-read my issue.  If django-restful-admin is going to use ModelAdmin features, it needs to be able to be part of the MRO of a ModelAdmin subclass.  A mixin is just a lazy and monkey-ier way of doing that, avoiding the brittle nature of subclassing.  But in this case "brittle" is another way of describing type-safety.


Developer in Play Store appears to be an unknown company?

It seems the developer in the play store has changed to "DoubleApp Xco" and their only other apps are a flashlight app and something about unused Nigerian network & bank codes. This is a rather concerning change.

Yes I didn't have time to maintain the app and it was scheduled to be removed from Play Store few days ago because of some security issue. So instead of having it removed, I sold the app to this company. There will be more ads there, but otherwise it's harmless. Btw the original code is all here, feel free to fork it and build the original version.


On unexpected error log exception message

When an unexcepted error occours the following message below is logged, without further information.
✖ Unexpected error:
With this change the exception thrown message is appended to provide more detailed information.

Thanks for this @desyncr ! I'll merge it in now :)

Awesome thanks!


Fix compatibility with webrtc/adapter.js

I have been running into some compatibility issues with adapter.js and after a lot of debugging I found out that the problem was a compatibility issue with RecordRTC.
adapter.js overwrites the navigator.getUserMedia function and make it work as defined by the webrtc specs for all browsers that have an API implemented.
When I imported RecordRTC after adapter.js, RecordRTC will also overwrite the function and break some shimming functionalities for the constraints.
To fix that, all I had to do is to import adapter.js after RecordRTC. It seems that everything is working nice now.
I don't know if this is expected, but it would be great to have RecordRTC and adapter.js working together since the browsers implementations are very different sometimes and adapter.js makes a very good job shimming al that.

Thanks @muaz-khan! :)


Populate more fields of plugin.cfg

These are shown in the plugins section of the project settings.
The author and description fields can be populated statically, but the version number cannot unless we manually update it for each release. Instead, lean on a feature of git archive where magic placeholders in specified files can be substituted for strings based on the current commit, crucially including the output of git describe which will return a tag name if the current commit is an annotated tag.
v0.2.0 is annotated while v0.1.0 was not.
https://phabricator.endlessm.com/T35503

If you check out the project from Git you will see the following ugly version string in the settings:

Here is the result when I import a snapshot archive of this branch into another project

v0.2.0-5-gc885832 decodes to:

Closest tag is v0.2.0 (as an aside: I dislike the v prefix)
5 indicates that it is 5 commits ahead of that tag
gc885832 indicates that the commit is c885832


Test utilities

choo seems nice and dandy but testing is a bit of a pain.
Where in React you would typically compare JSX with another JSX and have a match, in choo it does not seem so straightforward after for example comparing expected choo/html output with real component output, one needs to make either creative regexes or compare some DOM selector results. That due to comparing ES6 string templating, where spaces make it very inconsistent.
Is there plans for some testing utilities that would make it out of the box?
For example (jasmine):
expect(renderedMain.outerHTML).toEqual(
     html`

Hello

     `.outerHTML
)

Will most of the times fail or be difficult to use due to whitespace inconsistency and stuff. With comparing DOM objects its also not too nice, as it then is much more abstracted away from the HTML markup (in case of differences).

It seems like jest in version 20.0 does a nice job. For all, make sure its not 19.0 - this version doesn't support serialising native DOM.

For UI testing there'd ideally there'd be a DOM string comparison library that could work with tape, similar to spok.
But not all testing is UI testing; I'd argue UI testing has the lowest priority - whereas unit testing logic is a bit more pressing. To do this you can take any function that is passed to .use() and call it with a custom state object + event emitter instead. You can then test the full range of behavior and listen to the events it emits. This should provide a good separation of concerns. :sparkles:
I hope this answers your question!

Thanks.
I meant not so much UI but rather interaction testing; in my experience units rarely do fail on their own, and I what mean unexpectedly - which is the most valuable case for testing.
Although I agree that tape is a nice little thing, for ES6 and DOM is a bit of pain to work with in terms of configuration.  It turns to be a bit time consuming and expensive. Jest seems to work perfectly as of now, especially with automating automatic unit tests and contract changes.


result.compressed not work in 0.18.0

Before 0.18.0, I set "result.compressed = true" in app.conf and works fine to render result. In 0.18.0, the compressed function not work correctly. If set "result.compressed = true" all pages will be downloaded as actionName.gz file, instead of render html page.
Seems the render function did set html header as gzip format correctly.

confirmed results.compressed = true

This should fix the issue

Thanks for the prompt action 👍


async route handlers returning response headers, but no response body

Describe the bug
There are three different arc 'Hello World' examples below. While 1 (a traditional callback handler) works, 2 and 3 fail - they return a response that has headers, but no body. 3 is currently deployed on https://0fi9ete7v3.execute-api.us-west-2.amazonaws.com/staging
            Node 8.12.0
             npm 6.4.0
            .arc 4.0.1

To Reproduce
// 1. Not sure where I got this, but this works
// Is it out of date?
// 'arc' is unused in this code, but will fail if not included
// let arc = require("@architect/functions")
// function route(req, res) {
// 	console.log(JSON.stringify(req, null, 2))
// 	res({ html: `hello world` })
// }
// exports.handler = arc.html.get(route)

// 2. From https://arc.codes/
// Returns headers, but no body
//
// exports.handler = async function http(request) {
// 	return {
// 		type: "text/html",
// 		body: "
Hello World! 🎉
"
// 	}
// }

// 3. From https://arc.codes/guides/http
// Returns headers, but no body
//
// exports.handler = async function http(request) {
// 	return {
// 		status: 201,
// 		type: "text/html; charset=utf8 BUTTSEX",
// 		body: `
//     <!doctype html>
//
//       hello world
//
//    `
// 	}
// }

With 2 and 3, FireFox and Chrome DevTools show response headers, but no response bodies:
Headers:

No bodies:

Expected behavior
Delicious response bodies.
Note I'm deploying from Windows: Microsoft Windows NT 10.0.17763.0

We’ll look right into this! A quick troubleshooting question: do you have a non-Windows machine we can use to see if you have the same issue when using the same arc file and code creating resources from Mac or Linux?
We aim for full Windows support, just want to begin isolating the surface area of the problem.

I just noticed that after updating architect (the hello world was made on architect 3 originally), workflows might still be outdated.
"dependencies": {
"@architect/architect": "^4.0.1",
"@architect/workflows": "^3.5.11"
}
Is workflows out of date? I'm going to recreate the project from scratch on arc 4 and go from there.

Also example 3 had some filth in there (I was testing to see if the headers used in the route were being used in the browser - they're not, setting a weird content type doesn't change anything), I've removed it.

Ah, that's the problem! Workflows is now deprecated as of 4.x, we apparently still need to do that. I'd suggest using npx inventory nuke to blow away your project (or just use another @app name, either works) and remove @architect/workflows from your package.json. That should set you straight!
I feel confident that's the issue, but just for reference, I was unable to using the boilerplate code and the two examples you included as failing: https://he1jnhtrag.execute-api.us-west-2.amazonaws.com/staging


fileinfo: Anomalies in PE files

PE files (or generally other executable files, but let's stick to PE files in this ticket) do not necessarily need to conform to the PE specification in order to be loadable by Windows. There are often many discrepancies  and violations of the specification and the file still remains valid. This is often abused by malware authors in order to make analysis of the file more complicated. These, so called anomalies, can be used as initial indicators that something fishy is going on. They can also be used by another tools which use fileinfo as their source of data in order to focus on things pointed out by these indicators.
The indicators would be presented by fileinfo in form of list. Indicators would also possibly be parameterized if it is necessary. Indicators can also possibly be split into categories by their severity.
I am not going to list here all the possible anomalies that are going to be implemented here because I don't even know them all myself and the list would be infinite. We can start with the detection of unusual values in PE header and work our way from that. This is more of a research than definite task.

Internal note: possible inspiration in Avast cuckoo module static_pe_anomaly.py.

Additional anomalies proposed:

Detection of PDB paths that was purposefully truncated (like in af4db267da79adc536f4fdae30860d92b384a39acb8a7fa6ed1b99ad66310188)


INTEXT-139: Deprecate High Level Consumer Adapter

JIRA: https://jira.spring.io/browse/INTEXT-139

I don't think that we want to remove the tests for the deprecated classes. I think that it's still good to have them around until we remove those components altogether.

Yeah... That was an evening's overhead...
Changed the mind and pushed deprecation instead of removal.

Merged with minor changes: https://github.com/spring-projects/spring-integration-kafka/commit/0ab6eedc528b495da8a8db82de014bf80fe1ab60


👨🏻🔧 Increase Code Coverage

Right now Rugby has the dramatically low code coverage.

It will be great ♥ if you can help and write some new tests here.
Feel free to book some of them in this issue and then open a pull request.
It should be count in upcoming Hacktoberfest.

Hi, I would like to help you with this

Hi, I would like to help you with this

Hello @ameen4455! Feel free to select some tests 👍


CNI and CDI integration

Greetings from the CNI project.
One of the annoying sticking points of the CNI spec is that there isn't a good way for networks to interact with hardware, especially when something needs to be allocated on a per-attachment (i.e. per-container-nic) basis. We have an issue for this without any real progress.
There are really two separate problems here:

CNI networks should be able to say that they need a specific hardware resource
CNI plugins need to know which resource was allocated for them by some external process

So, I've opened this, well, open-ended issue in an attempt to build some bridges and do some brainstorming.
Thoughts? Does the CDI have some kind of "result" type that would be neatly embedded in a CNI ADD request?

@kad  as discussed in the meeting. Please take a look at this.


How to run js method  with params

If in java application, run js method in java, can send some params such as text or code,but i can't find any type to set params in using duktape.evaluate.
For Example
ScriptEngineManager engineManager = new ScriptEngineManager();
ScriptEngine engine = engineManager.getEngineByName("JavaScript");
engine.eval(new java.io.FileReader("test.js"));
Invocable inv = (Invocable)engine;
Object a = inv.invokeFunction("get", text, code);

To pass parameters to a JS method, you can bind a JS object to a Java interface: https://github.com/square/duktape-android#calling-javascript-from-java.


feat: add WebAssembly support

Resolves #78.
This PR:

resolves a few issues that were causing wasm32 builds to fail:

js feature in getrandom needed for WASM to work;
bitvec not behaving well in wasm32 (this PR removes bitvec for good);
crypto-bigint uses u32 in 32-bit mode while ark-ff doesn't care.

adds an example for using starknet-rs in browser with WebPack.

You can now use starknet-rs in browser :)

Should we add support for wasm32 into the CI?

Did you run yarn build before serving the page though?

Yes, I did. How do you serve it then?

$ yarn global add serve
$ serve -p 3000 -s dist/

Cool, that works!


BUG-000102904  The Coordinate Conversion tool of Military Tools for ArcGIS crashes ArcMap when changing the display coordinates after using the Map Point Tool.

Salesforce ID: BUG-000102904
Salesforce Submitter: Kory Kramer
Salesforce Submit Date: 2/14/2017 5:20 AM
Salesforce Bug Type: Crash
Salesforce Severity: Medium
Repro Data: \\esri.com\sf_filestore\PRD\Attachments\Defects\BUG-000102904
Work Around: (n/a)
Product: ArcGIS for Desktop
Functional Category: ArcGIS for Defense
Client Platform: (n/a)
Version Found: 10.3.1
Planned Version Fixed: (n/a)
Comment: This issue will be fixed in the next release. A basemap or layer will be required before the map point tool can be enabled.

Duplicate of #319

Closing since it's a duplicate.


WFLY-4578 Consolidate attribute types in IIOP subsystem

Windows Build 1468 is now running using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3

Linux with security manager Build 1316 is now running using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3

Linux Build 6389 is now running using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3

Linux with security manager Build 1316 outcome was SUCCESS using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3
Summary: Tests passed: 825, ignored: 317 Build time: 0:05:24

Linux Build 6389 outcome was SUCCESS using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3
Summary: Tests passed: 2856, ignored: 373, muted: 1 Build time: 0:46:54

Windows Build 1468 outcome was SUCCESS using a merge of d39ff7b50f1985c1ce673c6ec3b2f3115c9e73f3
Summary: Tests passed: 2857, ignored: 373 Build time: 0:47:49


Switching run_tests.py to Rust tests

See #166
New tests:

[x] arg conflicts with another arg
[x] arg that defined conflict appears before conflicting arg at runtime
[x] arg that defined conflict appears after conflicting arg at runtime
[x] arg conflicts with group

Once a test works in the Rust codebase, I'm good removing it entirely from the run_tests.py instead of just commenting it out ;)

It's just for me, while it is still wip.
I've opened PR for discussion about new tests, maybe anyone have good suggestions, new test ideas, etc

Just saw, this four little test made +4% coverage!

Awesome! That alone gets us near 70% :smile:

New tests for #166:
[x] required argument overridden
[x] conflict overridden by third party argument
And we got 70% :clap:

Nice! Now we can make 70% the passing rate for coverage :smile:

New tests for #166:

[x] arg requires another arg
[x] arg requires group
[x] required arg group
[x] optional arg group

Requirements and Groups blocks finished
And we are on 72%!


feat(react): switch to vite and @azure/msal

create-react-app -> vite
jest -> vitest
@intility/react-auth -> @azure/msal-react
better structure
better comments on template code
remove javascript template

Try the new template by running (creates from branch version)
npx degit intility/templates/react#react-vite intility-vite-app
cd intility-vite-app

npm install
npm start

run the docs by cloning and running
cd docusaurus
npm install
npm start

closes #124

Awesome!
One small thing i noticed is when running the npm run build I got the following message. Not sure what this means tho :)

Awesome!
One small thing i noticed is when running the npm run build I got the following message. Not sure what this means tho :)

I ran source-map-explorer to check it out.

I'll have to look into bifrost and its dependencies, as it seems it can't shake unused components.
Most of it comes from @azure/msal. I have seen issues there mentioning their size, but it would seem a lot of it is needed, and potential improvements won't come until the next major.
Many dependencies could also be code-splitted, depending on each applications needs, but I fear it would be too cluttered with fallbacks etc in the template alone.
250kb isn't optimal, but it's not the worst for internal apps which usually always is behind an authwall.


This does not work in Powershell

PS C:\Users\sanity> curl -Headers Metadata:true "http://<IP_ADDRESS>/metadata/instance?api-version=2017-08-01&fo
text"
Invoke-WebRequest : Cannot bind parameter 'Headers'. Cannot convert the "Metadata:true" value of type "System.Strin
to type "System.Collections.IDictionary".
At line:1 char:15

curl -Headers Metadata:true "http://<IP_ADDRESS>/metadata/instance ...

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

CategoryInfo          : InvalidArgument: (:) [Invoke-WebRequest], ParameterBindingException
FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

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

ID: 0fdce995-5347-32c4-119f-6e8484250859
Version Independent ID: 3dcfe7f4-cbb8-6323-5d93-b7e6b7f74db7
Content: Azure Instance Metadata Service
Content Source: articles/virtual-machines/windows/instance-metadata-service.md
Service: virtual-machines-windows
GitHub Login: @KumariSupriya
Microsoft Alias: sukumari

Thanks for the feedback! We are currently investigating and will update you shortly.

@Sanitys the commands are designed to be ran within the specific VM and in a Bash environment. Not in PowerShell. So the error you see would be expected in most cases.

Can you ping me internally<EMAIL_ADDRESS>I would like to talk
about making this document easier to read.
On Wed, May 22, 2019 at 9:07 AM Micah<EMAIL_ADDRESS>wrote:

@Sanitys https://github.com/Sanitys the commands are designed to be ran
within the specific VM and in a Bash environment. Not in PowerShell. So the
error you see would be expected in most cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/31851?email_source=notifications&email_token=AAXTRV4UK76ZWXVNTVRWHTDPWVVSLA5CNFSM4HOPDTFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7RO5A#issuecomment-494868340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXTRV4RZ7ND77ERH6ZAVZDPWVVSLANCNFSM4HOPDTFA
.

@Sanitys please reach out to the author @KumariSupriya and CC myself and @cynthn :)

#30370


Making channel type a enum

HI!
While i was using PusherSwift and thought if we could improve way of handling channel identifiers.
Main goals:

less error-prone channel type detection

I thought something like this will be useful (at least to replace current calls to isPresence && isPrivate functions)
enum ChannelType {

    private static let privateChannelPrefix = "private-"
    private static let presenceChannelPrefix = "presence-"

    case Global
    case Private
    case Presence

    init(channelName: String) {
        switch channelName {
        case _ where channelName.hasPrefix(ChannelType.privateChannelPrefix):
            self = .Private
        case _ where channelName.hasPrefix(ChannelType.presenceChannelPrefix):
            self = .Presence
        default:
            self = .Global
        }
    }

    func idenitifer(withChannelName name: String) -> String {
        switch self {
        case .Global:
            return name
        case .Private:
            return ChannelType.privateChannelPrefix + name
        case .Presence:
            return ChannelType.presenceChannelPrefix + name
        }
    }
}

Probably with ability to subscribe with struct similar to this one:
struct ChannelName {
    let name: String
    let type: ChannelType

    var channelIdentifier: String {
         return type.identifier(withChannelName: name)
    }
}

Would be glad to hear your thoughts about this and discuss.
Thanks!

Sounds good to me! Feel free to open a PR. You might want to create it based on the split-up-and-document branch, as I think I'm going to try and get that merged soon, when I've got the documentation in place

Great to hear, just didn't open PR because i saw that splitting was coming, will do soon :)
Thanks!

@Austinate the splitting has been merged along with a host of other changes for the 1.0.0 release

This has been added thanks to @Noobish1 as part of #60


WIP -DO NOT MERGE - HOFF-422: Replace hof-rds-api Image (WAIT FOR REGRESSION TESTING)

What?
Fix Vulnerabilities in hof-rds-api Image. These vulnerabilities can be in base Image and Yarn Packages. And Update Image from Branch (dev) to Prod. see ticket
#HOFF-422
Why?
The CVE List is a set of records that describe specific vulnerabilities or exposures. It is maintained by a large community of trusted entities and individuals.
A vulnerability is a flaw in a software, firmware, hardware, or service component that can be exploited to cause a negative impact to the confidentiality, integrity, or availability of an impacted component or components.
An exposure is a code or configuration error that can be exploited to gain indirect and often hard-to-discover access to application data such as customer information.
How?
Used Trivy to Scan Images and as a result Vulnerabilities found in Yarn packages.
Used yarn upgrade to upgrade outdated and vulnerable packages to latest versions
Built a new hof-rds-api image with upgraded yarn packages and no vulnerabilities found with Trivy Scanner
Please refer to below Trivy report,
https://confluence.bics-collaboration.homeoffice.gov.uk/display/FBISC/hoff+-+Trivy+-+hof-rds-api:f72489e134c4e80740cb919602409b61f82ae598
Testing?
Ingress url for Branch : https://ima-hoff-422.internal.branch.sas-notprod.homeoffice.gov.uk/your-details
Pods are healthy in Branch Env:
kubectl --context=acp-notprod_SAS --namespace=sas-ima-branch get pods | grep "hoff-422"
We will need to perform regression testing, and Merge these changes to Master Branch to test the services in QAT

@sulthan-ahmed  Now that we have successfully tested this hof-rds-api image in Branch Env for IMA service as part of the following ticket by Elias.
https://collaboration.homeoffice.gov.uk/jira/browse/HOFF-571
Can we Merge to Master branch So that we have this image available in UAT and then to Prod.
As these are higher environments, We may need to check the capacity of QA testers. So that we can merge and test asap for any issues.
FYI -  @SwathiManikos

yes just resolve the conflicts


Distance never shows

While I love the PirateWeather sensors, it has never showed a value for nearest_storm_distance.  Even with rain outside it still shows as 0.  Is this a sensor that simply no longer exists, or is there a configuration that I am missing?
configuration.yaml
`weather:

platform: darksky
api_key: !secret darksky_api
latitude: !secret homeassistant_latitude
longitude: !secret homeassistant_longitude
mode: "hourly"
`
sensor.yaml

`

platform: darksky
api_key: !secret darksky_api
scan_interval: '00:15:00'
forecast:

0
1
2
3
4
5
6
monitored_conditions:
alerts
apparent_temperature
apparent_temperature_high
apparent_temperature_low
cloud_cover
daily_summary
dew_point
hourly_summary
humidity
icon
minutely_summary
moon_phase
nearest_storm_bearing
nearest_storm_distance
ozone
precip_accumulation
precip_intensity
precip_intensity_max
precip_probability
precip_type
pressure
summary
sunrise_time
sunset_time
temperaturee
temperature_high
temperature_low
uv_index
visibility
wind_bearing
wind_gust
wind_speed
`

This issue was brought up in a separate repository and the answer from the developer is that particular parameter doesn't actually work currently. The developer gave some ideas on how he could implement but he has gotten busy and hasn't had a chance to implement anything for this.
I believe that these parameters are the only ones which do not work currently:

nearestStormDistance
nearestStormBearing
nearest-station (PW doesn't actually use any station data currently)

Thank you very much for this!  I didn’t realize there was another repository.  I’ll watch that one for any future updates.  Thanks again!

 That other repository is for the main PW website and is for general API issues not related to HA.
It could also be that the dev was going to look into it and then just forgot about it and this issue and/or commenting on that other one will serve as a reminder to look into it after the new HA flow is complete.

Thanks @cloneofghosts for responding to this! Your answer here is exactly correct, they're not working at the moment, but are on the list of things to improve at some point.
Thanks again for using this API, and let me know if you notice any other issues or have an idea!


feat: add switchContainer and ff for new search screen

This PR resolves FX-4562
Description

Adds ff AREnableESOnlySearch to switch between old and new search
creates boilerplate code to support the new search screen

PR Checklist

[x] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[x] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

add switchContainer and ff for new search screen - gkartalis

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

pushed some changes that might fix this, might need to test the deeplinking though


Guidance on synchronizing across browser tabs

Here's how I use the second argument of the writable creator to make the store update with storage events only as long as it has at least one subscriber:
https://github.com/babichjacob/svelte-localstorage/blob/fb04f7cdfeabb1f42e566b0cebca610893f5cc27/projects/svelte-localstorage/base.js#L13-L26
Let me know if you have any questions.

that's exactly what's needed!
Thanks Jacob :clap:
I will open a PR

It's been merged. Published in v.0.2.0.
Thanks again for providing the solution. :raised_hands:


Imran Turganov project

It would have been better to report the error as soon as it happened.
% cabal run
Enter the size of the Board:
8 200 200
Enter the screen Width:
200
Enter the screen Height:
200
Error: Invalid input detected.

Also, the ability to close the window, and basic validation that the field is even going to fit the window would be nice.

You have an exorbitant amount of code duplication, which should be fixed.


Fixing wrong method documentation for SetAlgebra

Spot the error:
/// Return true iff `self.intersect(other).isEmpty`.
@warn_unused_result
func subtract(other: Self) -> Self

…

/// Return true iff `self.intersect(other).isEmpty`.
@warn_unused_result
func isDisjointWith(other: Self) -> Bool

:wink:
I had reported a bug on this on Aug 4th 2015 (rdar://22031133).
Radar screening staff however deemed it not even worthy reading, apparently.

This issue behaves as intended based on the following:
Your suggested rewrite is isn’t accurate—‘subtract’ doesn’t return a Boolean at all.
We are now closing this bug report.

It does indeed not return a boolean. That was the whole point of my radar. Sigh.
 You made my day with this release! :bow:
Your attitude of friendliness and openness really makes a difference at Apple!

Damn! Color me impressed. :open_mouth:
Man, I'm already in love with this Apple! :heart_eyes: :bow:


Failures in syntax_test_rust.rs

https://gist.github.com/Jayflux/0e660fd525fee1beca638f53876b4916
@dten is this something you know about?

Think they came from your tweaks between taking the file from SublimePackages and adding it here. I think...
I'm going to do a different branch that improves the syntax stuff without going against the sublime future soon

@dten you  think it would be possible to run the syntax checks on PR somewhere?
May need to chat to you on irc or something about it

@wbond is it possible to automate the syntax tests? PackageControl doesn't seem to

Not currently, no. The syntax highlighting engine is used for the tests, and it is not available outside of the Sublime Text executable. Mostly this is due to the work it would take to extract it into a standalone executable. It has been requested by a couple of users, but for now the tests have to be run by hand.

thanks for the confirmation. we'll just have to be diligent

In the case of default packages, the tests are run as part of building Sublime Text, so we definitely catch anything before a new build goes out. That obviously doesn't help for third-party packages, however.

Sorry, I commented on the closed PR before, should have gone here.
At https://github.com/sublimehq/Packages/commit/b69477be90811ad2b248bd5e36b4774aea8ae892 I ported the new tests that were added. Currently all of the tests pass there.
I'm planning on brining the scopes more in line with http://www.sublimetext.com/docs/3/scope_naming.html in the near future. The Rust syntax was somewhat early in the process of me getting familiar with the existing landscape of scope names, so some of them deviate from what we've now established as guidelines.

I've just checked these tests agaiun and they're passing now. I think its because we changed the name of the package and it was testing against the wrong file!
When i change the top line to // SYNTAX TEST "Packages/sublime-rust/RustEnhanced.sublime-syntax" i now get Success: 2565 assertions in 1 files passed


Forbidden should not swallow the underlying error

Consumers have no idea why it was forbidden without including the error.

LGTM


Bump TibberLink stable to 1.6.1

1.6.1 isn't old enough, but a functional regression has been discovered in 1.5.0 - so I want to replace it earlier. Usage count of 1.6.0 and 1.6.1 could be added, cause there are no functional changes.

1.6.1 created 26.11.2023
63 user


Fix ES6 linting

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX
Haha, so this is a bit awkward. I had seen this pop up multiple times (or so I thought), so I decided to just start working on it. Then I checked when creating the PR, and I couldn't find an open issue on this 😅 I'm not the only one that thought there was an issue about it: #12693 😄

Description
So with ES6 syntax, the linter was complaining that you had to use the esversion: 6 option. This PR makes sure we use that option. The linter no longer complains now 🙌

LGTM! :1st_place_medal:


Hugo Themes that use deprecated variables

This issue records the 60 themes currently in the Hugo Themes showcase that have not been updated and currently use deprecated variables in their templates that will be removed from Hugo at some point in the future.
These themes throw console warnings in the deploy logs of the Hugo Themes showcase.
@bep I am notifying you with this issue about the need to apply the removal of the various deprecated variables gradually (whenever you deem necessary) and not all at once. As you know the Build Script allows for 50 broken theme demos, beyond this number we won't be able to update the Themes Site, until we have removed these themes.
cc: @digitalcraftsman

hugo-goa
.RSSLink

hugo-sustain
Page's .Hugo

onetwothree
Page's .URL

hugo-stellar-theme
Page's .Hugo

manis-hugo-theme
Page's .Hugo

hugo-material-blog
.RSSLink

LeaveIt

.RSSLink
Page's .URL

anybodyhome
.RSSLink

infinity-hugo
Page's .Hugo

gohugo-theme-ananke
gohugo-theme-ananke

hugo-lodi-theme
Page's .URL

hugo-nederburg-theme
.RSSLink

detox
Page's .Hugo

kube

Page's .Hugo
.RSSLink

artists
Page's .Hugo

onepress
Page's .Hugo

hugo-theme-yuki

Page's .Hugo
Page's .URL

Midnight
Page's .URL

bootie-docs
Page's .URL

hugo-theme-winning

Page's .Hugo
.RSSLink

hugo-w3-simple
Page's .RSSLink

hugo-theme-cactus-plus

Page's .Hugo
Page's .URL

freelancer
Page's .Hugo

hugo-identity-theme
Page's .Hugo

hugo-theme-revealjs
Page's .URL

hugograyscale
Page's .Hugo

hugo-fabric

.RSSLink
Page's .URL

strange-case

Page's .Hugo
.RSSLink

hugo-theme-cleanwhite

Page's .URL
Page's .UniqueID
Page's .Dir

simplicity

Page's .Hugo
Page's .LanguagePrefix
.RSSLink

hestia-pure
Page's .Hugo

hugo-now
.RSSLink

hugo-blog-jeffprod
.RSSLink

hugo-starter

Page's .Hugo
.RSSLink
Page's .URL

BeyondNothing

Page's .Hugo

hugo-theme-dopetrope
Page's .Hugo

hugrid
Page's .Hugo

future-imperfect

Page's .Hugo
.RSSLink

grid-side

.RSSLink
Page's .Hugo

hugo-theme-hamburg

Page's .URL
.RSSLink

classless-hugo
Page's .Hugo

highlights
Page's .Hugo

bulma

Page's .Hugo
.RSSLink

hugo-universal-theme
Page's .Hugo

hugo-theme-techdoc

Page's .Hugo
Page's .URL
Page's .UniqueID

vienna

Page's .URL
.RSSLink

hpstr-hugo-theme

.RSSLink
Page's .Hugo

osprey

.RSSLink
Page's .Hugo

hugo-pacman-theme

Page's .URL
.RSSLink

slim
.RSSLink

hugo-changelog-theme
Page's .Hugo

hugo-conference
Page's .Hugo

allegiant
Page's .URL

hugo-theme-sky
Page's .Hugo

dot-hugo-documentation-theme
Page's .URL

story
Page's .Hugo

nofancy
Page's .Hugo

hugo-resume
Page's .Hugo

creative
Page's .Hugo

hugo-theme-vec

Page's .Hugo
.RSSLink

This issue has been fixed in Midnight -develop as of this commit and should appear in -master and the next release by the time this pull request gets included in a Hugo release.
Issue #682 has also been fixed in Midnight as of this other commit


redis session count more than visitor count

i used redisson in tomcat8 to mange session.and i have a problem that: site real visitor count only 100,but redis save session count is 1700.i don't understand the reason.

I am not sure where you have obtained the site real visitor count from. You have to understand a site user can have more than one sessions under certain scenarios.


Call For Contribution

Hi dear community!
Since a while, i have less and less time to maintain this cookbook. For a lot of good reasons :)
At my job, i do less and less code... More and more management!
And at home, 2 children and 1 wife keep me occupied.
If you feel you wanna help me, i will let you manage the repository! Please write me in PM.
Thx to everybody!

Hey @sinfomicien - there doesn't seem to be a way to PM in github anymore. I can't promise a lot of time to help manage things, but could be another pair of eyes to review PRs and issues.

Seems like you guys really need some help with this. I'm (for better or worse) getting more involved with mysql (specifically the mariadb variant) and I've been a chef user for 5+ years. I cant promise limitless cycles to work on this but I'd be more than happy to help out.

Dear jwmarshall, you've been added as a collaborator for both the repository, and for the cookbook on supermarket! We need help, you're welcome if you want to ! :)
Thx a lot

@sinfomicien I don't seem to have the ability to merge pull requests.

Chef needs an actively maintained MariaDB cookbook. Per a point @jcotton1123 made to me today, Puppet has a single MySQL module that works for MySQL, MariaDB, and (I assume) Percona.
But back in 2013, @sethvargo wrote on this ticket (https://tickets.opscode.com/browse/COOK-3487):

...while you are right that there are similarities between MariaDB and MySQL, they are not the same product. The inclusion of the Percona recipes are also of question, but the past is the past .
Given the existing bloat in the MySQL cookbook, we think it is in the best interest for a community member who uses MariaDB to create and maintain an alternative community cookbook.

His points are valid.
I'm assuming this cookbook was that alternative community cookbook, and @sinfomicien, you've done a great job with this. There are currently 20 open issues and 19 open pull requests on this cookbook. We're using it for at least one customer, so I'm happy to request collaborator access (as would @jcotton1123, who recently opened a PR).
Does anyone have any thoughts on a solution to this issue? Should we all put effort into continuing to maintain this cookbook or are others finding alternatives I'm missing?

Dear Matt & Jesse... You're welcome on the project :)
You've been invited as collaborator on the repo... And as collaborator on the supermarket!

@sinfomicien sounds like you've had the same idea we had. If there's anything https://github.com/chef-brigade/ can do to help, let us know. Especially happy to help with admin overhead, and we've got folks who are got excited about contributing.

@josephholsten : I always need help! To start, i give you access to the repo ! Will try to give you access to supermarket tomorrow... What's your preferred way of communication to go further ? Slack/Hangout, Skype, mail, other ? :)

I must admit I've also fallen behind in helping. Unfortunately I have some (rather insane) deadlines approaching. I should be back in the swing of things mid-December though.
I think putting together a Slack team or something would be great for coordinating our efforts and discussing where we want to take the development of this cookbook.

@jwmarshall Agreed. Or to @josephholsten's point, might make sense to put this cookbook under the management of chef-brigade? They already manage related cookbooks, like MongoDB and PostgreSQL. I'm happy to help maintain it either way.

Im not familiar with those guys, and I don't believe I use any of their cookbooks, but I'm certainly not opposed. If they already have a communication stream as well maybe we should all join forces?

@jwmarshall I am not familiar either; however, there seems to be some energy there. @sinfomicien, what would you prefer?

I wish there was a better way to communicate then this...
We, the maintainers, need to be careful about versioning. I was looking at releasing a new 0.3.x version of the cookbook however master contains at least one set of breaking changes - adding a priority to the config file names (ex: innodb.cnf becomes 20-innodb.cnf). What is currently in master likely needs to be released as 1.x. I am going to cut a 0.3.x branch from the last 0.3.1 release and cherry-pick a few changes into it.

FYI: chef-brigade has been renamed to sous-chefs, and lives at https://github.com/sous-chefs
Currently we're working to put together some standards (just recommendations, really) and tooling to help. We're also about to start building some test infra for people to run test-kitchen on.
But don't feel like you're got to relinquish anything, we're happy to help no matter where the cookbook lives. Feel free to poke us in https://chefcommunity.slack.com/messages/sous-chefs/

Anyone else have any thoughts?

We use this cookbook a fair amount internally and it would be a shame if it wasn't kept up to date. It looks like a few people have already put their hands up to help, but if still looking for someone I am happy to assist.

@sinfomicien I've gotten a request to fork this cookbook into sous-chefs so more people can have commit access. I'd really like to avoid that. Do you think you can get another person or two to have commit access? Or would you be okay with transferring this cookbook to sous-chefs?
I'm watching this thread, and would be happy to chat in the chef community slack or in chef IRC.

@sinfomicien sous-chefs have had a chat and put together this process for if we have to create a hard fork: https://github.com/sous-chefs/meta/blob/master/docs/forking.md
So we're going to wait until 2017-03-10 before letting anyone create a hard fork. I really hope to hear from you before then so we can avoid that.
To anyone wanting help getting their PRs tested, we've created a soft fork at https://github.com/sous-chefs/mariadb. We'd still like to see everything merged into the official mariadb cookbook, but we can work on integrating patches over there in the mean time.

well, I feel like a total jerk. apparently /I/ have a commit bit. Honestly, I don't know what I'm doing with this cookbook, so I'm going to be trusting @shoekstra to review things that aren't obvious.
The offer to transfer to sous-chefs is still on the table, but we absolutely will not hard fork while someone with a commit bit is still around.

I’m happy to pitch in with reviews as well. I haven’t had a chance to work on resolving outstanding issues, but I also have a commit bit, and hope to have more time soon.

 Honestly, I don't know what I'm doing with this cookbook, so I'm going to be trusting @shoekstra to review things that aren't obvious.
The offer to transfer to sous-chefs is still on the table, but we absolutely will not hard fork while someone with a commit bit is still around.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@mjuszczak well I realized that I don't actually have perms to release the cookbook to supermarket, but I think you do. Hopefully @shoekstra and I can knock down some of the backlog to make it worth releasing soon.

OK! I will try to pitch in some cycles soon, too.

On Mar 1, 2017, at 7:21 PM, Joseph Anthony Pasquale Holsten<EMAIL_ADDRESS>wrote:
@mjuszczak well I realized that I don't actually have perms to release the cookbook to supermarket, but I think you do. Hopefully @shoekstra and I can knock down some of the backlog to make it worth releasing soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Issue has been open over a year and now there is more active development happening.  No reason to keep this open longer.


ComponentClass prop should be able to accept an actual component class

Currently propTypes only allows a string for the ComponentClass prop:
https://github.com/azmenak/react-stripe-checkout/blob/c351801381677dbee08bbca3861136dbd78a553f/StripeCheckout.js#L46
It should be able to accept an actual component class (or function), to avoid the extra span DOM node:
import StripeCheckout from 'react-stripe-checkout'

const Button = ({ children, ...props }) => (
  <button {...props}>{children}</button>
)

class TakeMoney extends Component {
  onToken = token => console.log(token)

  render() {
    return (
      <StripeCheckout
        stripeKey={process.env.STRIPE_KEY}
        token={this.onToken}
        ComponentClass={Button}
      >
        New payment source
      </StripeCheckout>
    )
  }
}

The above works, but triggers a propTypes warning in a dev environment.

What about this issue?

Any progress on this?


Empty response in fetchConfirmations

$confirmations = $steam->mobileAuth()->confirmations()->fetchConfirmations();
return empty array
Any help will be appreciated. Can't understand how to make this thing work. Thanks.

/closed
Wrote down from scratch by myself.


Skype Ads on Windows PC app

Starting to see these crop up today. Anyone know how to block these babies out again?

Switch to signal a well known end to end encrypted messenger and phone program. And help spread democracy and freedom to the people

Send high-quality group, text, voice, video, document, and picture messages anywhere in the world without SMS or MMS fees.

Signal messages and calls are always end-to-end encrypted and painstakingly engineered to keep your communication safe. We can't read your messages or see your calls, and no one else can either.

Starting to see these crop up today. Anyone know how to block these babies out again?

I am seeing those too before, also in their Android app.
Though it is not appearing on my devices anymore.
I am using a custom list so I can't pinpoint the exact domain.

I'm going to close this now because nothing actionable arises.


backup exit code not captured

Hi,
I noticed some of my failed backups are being marked as COMPLETED when it shouldn't be, example:
...
Uploaded chunk 4442 size 13353236, 299KB/s 1 day 08:43:07 38.8%
[0] Maximum number of retries reached (backoff: 64, attempts: 15)
Failed to upload the chunk 32a5c7b52d67130c1a5c32c0b5dcbc211cfebze5f59b6214a32ebf8c0921c470: googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded
Backup COMPLETED, duration 21:15:32

The issue appears to be due to the way duplicacy is called in /apps/backup.sh :
duplicacy $GLOBAL_OPTIONS backup $BACKUP_OPTIONS | tee -a $log_file
exitcode=$?

Since tee is being called you are measuring the exitcode by tee's response code and not of duplicacy.
ie. you are doing this:
$ exit 1 | tee ; echo $?
0

When you can capture the exit code of what is before the pipe with $PIPESTATUS[0] like this:
$ exit 1 | tee ; echo ${PIPESTATUS[0]}
1

And to get the tee exit code simply:
$ exit 1 | tee ; echo ${PIPESTATUS[1]}
0

prune.sh appears like it will suffer from the same issue but might be a bit more complicated due to 'sh -c' being called as well...

Thanks!


vulkan: Update SensorEvents API to use GVRPickedObject

Same as #1256, refactored for vulkan. Dependent on #1360 because of updates to picking functions.

GearVRf-DCO-1.0-Signed-off-by: Jonathan Reynolds<EMAIL_ADDRESS>

I see now that these changes are identical to #1256, so those commits can be cherry-picked.

Please consider this for merging.  I will try to cherry-pick https://github.com/Samsung/GearVRf/pull/1257 from master afterwards.


generate warp page

how can I generate pages like this? thanks, for your help.

use blender for it.

create a plan.
draw verticle lines in plan.
move those line to form that kind of shap.
apply Subdivision Surface Modeling.
add texture to plan.
place camera from where you want to capture this page.
render a image.
done.


fix: reduce CDN size by tree shaking

Summary
These changes reduce the size of cwr.js from ~230KB to 148KB. The problem is that we are including unused dependencies because our tree shaking is broken. From webpack documentation: https://webpack.js.org/guides/tree-shaking/

Ensure no compilers transform your ES2015 module syntax into CommonJS modules (this is the default behavior of the popular Babel preset @babel/preset-env - see the documentation for more details).

This PR restores treeshaking by compiling to native ES5 modules instead of CommonJS.

However, this only fixes the CDN build and does not impact the NPM build in any way. While the CDN build is compiled by webpack and outputs to build/assets/cwr.js, the NPM build is managed by tsc and outputs to the dist directory.
Example
We have a dependency on UUID's v4 function that is currently taking 15 kb. However, nearly all of that is stuff that we do not need, such as v1, md5, etc.

After tree shaking, we now only import v4 and drop everything else, reducing the stat size from 24 kb to 3 kb, and the parsed size is much lower.

Backwards compatibility
We can reduce package size even further by specifying browser targets. I've used the default targets from documentation, which look good against a quick check of which browsers people actually use.

https://babeljs.io/docs/options#targets
https://www.stetic.com/market-share/browser/

In general, we can trade backwards compatibility for package size by setting browser targets to earlier versions. By default, the TerserPlugin for Webpack attempts to provide the broadest support possible.
Risk
Before deploying, we should do some manual testing and run the smoke tests for backward compatibility since we are switching the CDN build from CommonJS to ES15.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This CR restores treeshaking by compiling to native ES5 modules instead of CommonJS.

Question for my understanding since I have limited understanding of this - Will this lead to issues with folks with CJS applications to be able to use the package?

Question for my understanding since I have limited understanding of this - Will this lead to issues with folks with CJS applications to be able to use the package?

Ultimately, no because this package is for the Browser runtime, whereas CommonJS is Node.js and meant for servers. However, we may see issues in some dev environments, similar to what happened with the web vital attributions imports.
I can add additional integ tests for cwr.js and npm builds to give us more confidence, as well as attach evidence of manual e2e testing.

Update: I have updated the configuration to target the default browser targets. This reduces the build size to the following:

As a follow up, I am working on improving support for older targets by adding polyfills via corejs; however that is still a WIP. While the polyfills work on all browsers on unix/macos, none of them work on windows yet. Those polyfills will cost us 5-20 kb, so up for discussion as well once I raise another PR.

Follow up action is being tracked here: https://github.com/aws-observability/aws-rum-web/pull/567

Browsers list defaults
These are the browsers now supported.

0.5%, last 2 versions, Firefox ESR, not dead


Low contrast in the lateral nav arrows.

Bump!
#BBB IMO

cool!

Since we're changing the contrast on these buttons, shouldn't the cancel-buttons also be updated? Since we already unified #2222 these styles previously I figured we perhaps should do it this time too

+1


merging

i am still trying to comit

Please I am sorry for all the trouble we have caused you but count it all joy. Your PR is about to be merged and you will be able to see your name on this url.
To enable me to do this, READ the README again carefully, update your code with the latest and push the update. I am here for you for the next 6 hours before I close the PR so you can initiate a fresh PR which will be easier to merge.

Hi Maryann!
Please open a new PR! Remember to make a branch as you work on your changes!
We look forward to merging your next PR! :partying_face:


support django 2

Maybe the python2 compatibility got lost.

@SteinRobert we need it soon, django 1.11 LTS end is coming.

I guess there is an issue within the collapsable tab structure...


A typo in A2 English for Developer - Learning greetings in your first day at the office.

Describe the Issue
Jake is explaining the purpose of his visit to Sarah. He's there to hand over something that Sarah needs, which will permit him (should be her) access to certain areas.
Affected Page
https://www.freecodecamp.org/learn/a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/task-154
Your code

Expected behavior
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Next step has similar error.
https://www.freecodecamp.org/learn/a2-english-for-developers/learn-greetings-in-your-first-day-at-the-office/task-155

What is Sarah referring to with it in his question Is it contactless?

Should be

What is Sarah referring to with it in her question Is it contactless?

Hii @Neonnati @huyenltnguyen @gikf  excellent catch. Solved it locally, will be raising a PR soon. This my first valid pull request, pls assign me if possible

Hii @huyenltnguyen @gikf @Neonnati fixed the typos in both the task (154 & 155)

Hope it clear all the test and get merged


feat(locators): add by.exactRepeater

Modified version of https://github.com/angular/protractor/pull/1662

Looks good after comments.

Merged in at https://github.com/angular/protractor/commit/324f69d6aa7c23ad77f1d50e26e0a56bade40132


Replace disk occurrences with storage

name: Pull Request
about: Submit a pull request
title: ''
labels: ''
assignees: '@boz @gosuri'

Description
Replaces all the disk: instances with storage:
Motivation and Context
Fixes #518
How Has This Been Tested?

Types of changes

[x] 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)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@boz Should be fixed now


Design system - Select dropdown component

Create a generic Leather-themed Radix dropdown component, where each slot component is exported from @app/componet/dropdown.

@fbwoolf These are the base to the selector component

@markmhendrickson in Radix, a dropdown and a select component are two different things. The issue and location should be renamed to match the designs for a Select component?

@mica000 might be best to answer

Yes, makes sense to rename to selector

Yes, makes sense to rename to selector

@mica000 is the interactions that it drops down below the trigger, or does it popup over what is selected? Ref the playground to see the difference here. I need to know what we want bc they are two different Radix components to start from. cc @kyranjamie
https://www.radix-ui.com/themes/playground#select
https://www.radix-ui.com/themes/playground#dropdown-menu

I believe we want a dropdown, but it is labeled in Figma as a select?

Also a bit confused here on the file location, we currently have a components folder, is that what you mean in description? Or, should I start a new folder singular? Maybe we want something completely separate, like ui so those can be pulled out to share if needed later?
@app/ui/components/dropdown?

Guess Select has a position prop...

https://www.radix-ui.com/themes/playground#select

This is what I was thinking too @fbwoolf . They are really two different components. The radix select component looks good for more basic types of select but I think we want to have more complexly styled rows so we want to create a dropdown that we can use as both a dropdown menu and custom select
What we should can do is have a dropdown component for both of them but with different triggers

for the Settings menu, the trigger is a button
for the Select the trigger is a button that is styled to look like a select option

Inside of the menu itself we would then have child components for each row like

asset row
receive row
settings menu row

Doing things that way and we can share a lot of code between UI implementations and also do more cool stuff in the select like hot keys etc.
So it would be like this:
// @app/ui/components/menu
<DropdownMenu.Root>
  <DropdownMenu.Trigger>
    <!--  Icon button for Settings menu -->
    <!--  Full width button for Select menu - like we have in swaps-->
  </DropdownMenu.Trigger>
  <DropdownMenu.Content>
    <DropdownMenu.Item shortcut="⌘ E">Some settings menu item</DropdownMenu.Item>
    <DropdownMenu.Separator />
    <DropdownMenu.Item shortcut="⌘ N">
     {assets.map(asset => <AssetRow variant='receive' asset={asset} >)}
     </DropdownMenu.Item>
</DropdownMenu.Root>

I don't mind what we call it but I think it is a good idea to put it in a subfolder like @app/ui/ or @app/components/ui/. Then we can start adding all our bespoke radix components there.
We can even have wrapper components for the two variants then so we would have:

@app/ui/components/menu - base bespoke radix dropdown
@app/ui/components/select  - imports and builds on menu to make it behave more like a select - for swaps etc.
@app/ui/components/dropdown  - imports and builds on menu to make it behave more like a dropdown - for select menu

We may even be over-thinking this a bit. I know of only one place where we need the dropdown-menu - for settings. We may use the select in more places - for swap, send etc.

@pete-watters thanks for the reply. It appears we are on the same page here. 👍

I feel like this issue is a duplicate of newer issues so I'm going to close it and start those instead.


Why cant I set Default group to do volume.

When I go on permission txt and grant people to that group but some reason they cant to !volume and I try adding volume in the commandwhitelist and when I get back on discord and do !perms it show all of command_whitelist: {'search', 'id', 'skip', 'clean', 'help', 'perms', 'queue', 'np', 'play'} That's it and I try different ways still wont work can some one please help me?

As is hinted to in the name, [Default] is the group that is used by default. You shouldn't be adding users or roles to it.
To add a command to the whitelist, add it with a space.
CommandWhitelist = search id skip clean help perms queue np play volume

You need to restart the bot after saving permissions.txt.

I did restart the bot when adding the volume with space and still people can't change the bot volume it keep saying it's not enable for this group (default)

You've misconfigured your permissions. We'll be able to help you more with this if you join our help server on Discord: http://discord.me/rhinohelp


Fix Chinese translation

We usually use 切换 instead of 检出 in Chinese. Anyway, in the most other translations, it uses properly.

Thanks for the fix!


Fix refcounting in sys_common

PR w/ @kapkic that fixes refcounting in many of the system calls that were translated last summer.
Also fixes an off by one error in waitpid that was causing it to fail early.

Resolved the issues except sel_ldr.c


How to load self-made vocab.txt

As the title, is there already a function that I can call to load my personal vocab? I find the code in pretrained and found that the vocabfilepath has been fixed?
Do you have the function that receives the path of new vocab and returns the tokenizer loaded from this path?

@lierik ,
I am not sure what type of tokenizer model you are after but BERT, you can load as in the example/basic example:
https://github.com/sugarme/tokenizer/blob/c9b250ce72455d4dc86c6e28c623e0c511be91ed/example/basic/bert.go#L29
Hope that helps.

@lierik ,
Late response. The tokenizer built to deal with multiple languages including chinese. Please see test cases in test files.
So if theres something not as expected, please create a simple example so we can have a look. Thanks.

Close for now as now response.


fix(ANR): Moves saveRequestForLater from main thread. Adds synchroniz…

fix(ANR): Moves saveRequestForLater from the main thread. Adds synchronized to init method at LeanplumEventDataManager.
E2-1091, E2-1092
Fixes #
Fixes possible ANR when saveRequestForLater called from the main thread.
Proposed Changes

Move saveRequestForLater for a separate thread.
Adds synchronized to init method at LeanplumEventDataManager to be sure that we will have only one LeanplumDataBaseManager.

test this please

test this please

test this please


Have (i) for each of items in create market

Have information popups / mouse overs for headers in the create market forms.
outcome
Resolution Source
Designated Reporter
Expiration Date
no show bond
validity bond
Settlement Fee
Initial Liquidity
...
...
This is a good idea, but punting it to Peccary for now to minimize scope creep...
...
:thumbsup:  Totally agree!
-sharkcrayon
...
@serena I'd like to get design for tooltip or description of the create market fields.
-bthaile

Should do this for trading

@matt-bullock @cillianhunter0 @Chwy5 -- Do you believe the new market creation designs approach the problem of communicating whats happening enough that this ticket is closable?

I believe it does, there might be 1 or 2 random spots that need an (i) but we can close this ticket

Is this done for trading?

I believe so... @matt-bullock please confirm
only thing i think still needs to be completed with them is changing eth to dai for Total amount escrowed in the order ticket and Total Cost (shares) in Open Orders


Sort out front end

Front end currently not fully ported

@griff-rees pretty sure an earlier version of this was the theme I scavenged: https://colorlib.com/wp/template/courses/

@annakrystalli The tarball containing that theme also references but doesn't contain slider-img-1.jpg (Issue #45)

Here's a rough look at the png with a lot of references to the img path
(but some to image):
style.css
              [0/7561
]1231:  background-image: url(../images/reprohack_banner0.png);
1235:  background-image: url(../images/reprohack_banner0.png);
1248:.slider_area .single_slider .illastrator_png {
1255:  .slider_area .single_slider .illastrator_png {
1262:  .slider_area .single_slider .illastrator_png {
1269:  .slider_area .single_slider .illastrator_png {
1276:  .slider_area .single_slider .illastrator_png {
1282:.slider_area .single_slider .illastrator_png img {
1654:  background-image: url(../images/reprohack_footer0.png);
1894:  background-image: url(../images/reprohack_banner_short0.png);
1899:  background-image: url(../images/bradcam2.png);
2724:  background-image: url(../img/team/overlay.png);
2829:  background-image: url(../img/team/img.png);
2936:  background-image: url(../images/bradcam2.png);
3234:  background-image: url(../img/testmonial/testmonial.png);
4634:  background: url(../img/elements/primary-check.png) no-repeat center
center/cover;
4676:  background: url(../img/elements/success-check.png) no-repeat center
center/cover;
4724:  background: url(../img/elements/disabled-check.png) no-repeat center
center/cover;
4766:  background: url(../img/elements/primary-radio.png) no-repeat center
center/cover;
4808:  background: url(../img/elements/success-radio.png) no-repeat center
center/cover;
4856:  background: url(../img/elements/disabled-radio.png) no-repeat center
center/cover;

On Thu, 1 Oct 2020 at 15:33, Will Furnass<EMAIL_ADDRESS>wrote:

@annakrystalli https://github.com/annakrystalli The tarball containing
that theme also references but doesn't contain slider-img-1.jpg (Issue #45
https://github.com/reprohack/reprohack_site/issues/45)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reprohack/reprohack_site/issues/37#issuecomment-702177562,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOLEZ3MVSVVX7KPGZKPDTXDSISHLLANCNFSM4RVNAP7A
.

--
Dr Griffith Rees (he/his)
Research Associate
Sheffield Methods Institute
https://www.sheffield.ac.uk/smi/people/academic/griffith-rees
CABDyN Complexity Centre
http://www.cabdyn.ox.ac.uk/
http://www.cabdyn.ox.ac.uk/people_pages/complexity_people_rees.asp

I'm tempted to say we can safely get rid of any reference to assets and styling in img/?


⚠ AGEG website (prod) has degraded performance

In 08564da, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 7345 ms

Resolved: AGEG website (prod) performance has improved in bf47a35.


Add dates/deadlines for breakouts/lightning talks etc.

Deadline for submission of breakouts/lightning talks: March 28th
Notice of acceptance: March 30th

Added in #71


[DO NOT MERGE] Release 1.0.0

This is to release OpenWhisk core 1.0.0 and fix tags from the nightly to a fixed tag.
Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[ ] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

This PR would not be merged.
This is a branch in the Apache repo and would preserve a snapshot for the 1.0.0 version.

Reference: https://github.com/apache/openwhisk-release/blob/master/docs/release_instructions.md#preparing-to-make-a-release

I will see if I can manage to convince the Jenkins job to build the right core Docker images from the 1.0.0 branch.  Might not have time until later tonight.

Codecov Report

Merging #4998 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4998   +/-   ##
=======================================
  Coverage   83.75%   83.75%
=======================================
  Files         202      202
  Lines        9786     9786
  Branches      409      409
=======================================
  Hits         8196     8196
  Misses       1590     1590

Impacted Files
Coverage Δ

.../org/apache/openwhisk/core/connector/Message.scala
79.36% <0.00%> (ø)

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 a1ba987...1b4cadc. Read the comment docs.

Now, this branch includes these two new commits.

And I think it is finally ready to be released.

closing as the 1.0.0 version is released.


Very nice example! Would you mind adding a GAE example too?

My use-case would be this one:

having a shared typescript lib between an app / cloud function / an expressjs API server running on Google App Engine
having the isolate command allowing to package each of those for deployment

I am not planning to add all kinds of different deployments to this example, because the list would become endless. The isolation process is independent of the platform you deploy to.
I don't currently use GAE so I don't know the details, but once you run npx isolate in the package you want to deploy you have a directory that should be no different from any other nodejs application that is not coming from a monorepo. You can a system can install and execute the entry point.
Note that for a web app you probably do not need to run isolate. A platform like nextjs deployed on vercel already supports monorepo setups, as will most other platforms I think.

Thanks!


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg d569db3...d4505c6:
  > d4505c6 Source validation fixes (# 2251)
  > fb7ee28 when testing downstream use the correct release branch (# 2265)
  > bfab3c8 Add back inadvertedly deleted call to ObserveKind (# 2282)

/lgtm
/approve


Add CodePen and GeneralObserver features

Description
Adds full features of CodePen's embed, plus adds improvements to GeneralObserver
GeneralObserver will now load when the component is 400px off-screen. This gives the benefits of lazy loading without impacting the user's experience with a blank space as the component loads in.
GeneralObserver also takes a height prop to keep the space it will take up on load. The CodePen component is passing its height prop for it to use. Other components can do the same.
Related Issues
Addresses #21

@a-trost Hey Alex, thanks so much for the PR. I'll add a review now!


Add configuration for authentication strategy

We want to be able to use other authentication strategies in forms-admin. This PR refactors the application controller to allow configuration of the strategy using the settings files or environment variable.
We also deprecate the old way of selecting the basic authentication strategy, and move the basic authentication strategy out the application controller and into a Warden strategy.

I've renamed things a bit, I decided that it would be better to be consistent in our configuration interface with what we save in our db, so I've changed the name of the configuration variable to auth_provider.


Fill in git username to the generated gem's contributing section of README.md

This Pull Request changes the GitHub URL in the Contributing section of README.md from generated gem (e.g. bundle gem foo).
Why:
I found myself change [USERNAME] to my git username so many times and I also help some people fix this.
So I think this should be filled when new gem is generated. When git username not set, falls back to [USERNAME].
I don't really know how to make tests DRY, please advise, thank you.

@indirect r?

@homu r+

:pushpin: Commit 7f29df5 has been approved by segiddins

:hourglass: Testing commit 7f29df5 with merge 92aa19d...

:sunny: Test successful - status


Suppress a warning when using clang (clang does not have the  flag).

Codecov Report

Merging #276 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #276   +/-   ##
=======================================
  Coverage   94.82%   94.82%
=======================================
  Files          53       53
  Lines        2940     2940
=======================================
  Hits         2788     2788
  Misses        152      152

Impacted Files
Coverage Δ

packages/Interface/test/tstC_API.c
97.49% <ø> (ø)
: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 b73ff2a...73cf892. Read the comment docs.

See compiler warnings analysis on Jenkins here

Forgot Wall on my gcc built :/


WebSockets samples for Java

Adding doc samples for WebSocket and session affinity support beta release.

ping

Ping again

Closing this as this needs to be re-done and re-tested. The team will re-submit this later. Thanks!


Problem with Minigame

I am fishing with:

Iron Fishing Rod
Long Cast Reel
Heavy Bobber
Shiny Hook

When I am in the minigame, I will have the tension bar over the fish and it is actively reeling in the fish. Suddenly, I get kicked out of the minigame without any indicator telling me why. The distance text colour is green but still kicks me out. It will use up my bait but not my durability. This is not a problem with fish less than 90m away. I've been trying to catch a whale but I am not sure why I keep getting kicked out despite other people being able to catch a whale with the same fishing set up.

The long cast reel is slow, and that combined with whales being slow to reel in means its likely taking too long to reel in, however that is supposed to give a popup message on screen when a fish gets away.

Otherwise, if the bobber entity is being killed somehow, like being knocked onto land or something similar, that could also cause the fishing to stop without a message.

Yes, I'm on a server. We are using the RLCraft package and added [1.12.2] Gravestone Mod 1.10.1. There is no pop up on the screen, I just get kicked out of the minigame. Also I was only reeling for about 10 seconds before it kicks me out. I'm fishing in the middle of the ocean so I don't think its the bobber entity being killed.

Either the server or client being installed incorrectly can cause it to desync the fishing and stopping without a message, that or server performance mods if added, some can cause issues as well.
It only taking 10 seconds before kicking you out of fishing almost sounds like the server either removed the FMB mod, or didnt install any of its configs, I'd recommend reinstalling using the server pack and making sure all the proper configs and mods are there.

Hey! We've redownlaoded all the files and checked the config but are still running into the problem. We also removed the gravestone mod as well. We decided to just turn off the minigame so I can catch the whale as it started kicking me out of the minigame even with other fish :)

Could you upload the latest.log file when this happens, from both the client and server if possible?