what's this method's rank in tianchi, compare with original EAST?

Hi, what's this method's rank in tianchi, compare with original EAST?

maybe ranked 3rd or 4th

maybe ranked 3rd or 4th

Excuse me, how can you know?

@scut-salmon check this:
https://gitlab.com/lufo/AdvancedEAST
https://tianchi.aliyun.com/home/science/scienceDetail?userId=910860123
just a guess, maybe they use another Method.


Add docs for UseIdentityServerEfTokenCleanup

Could not find any documentation on this extensions method.
public static IApplicationBuilder UseIdentityServerEfTokenCleanup(this IApplicationBuilder app, IApplicationLifetime applicationLifetime);
What does it actually do if I add it as bellow
           app.UseIdentityServer();             app.UseIdentityServerEfTokenCleanup(appLifetime);
Version used : 1.5.3

I guess not. It would be here: http://docs.identityserver.io/en/release/reference/ef.html
I'll leave this open as a docs issue.

What does it actually do if I add it as bellow

Registers TokenCleanup.Start and .Stop to the respective starting and stopping callbacks of the given app lifetime. I.e. starts up the cleanup schedule on app startup and stops it when it's shutting down.


"npx codeceptjs run-rerun --steps" writes step multiple times

What are you trying to achieve?
Combine "re-run" with "--steps"
Expected: I see each step printed out once
What do you get instead?
Actual: I see each step printed out x times depending on iteration of re-run.

Provide console output if related. Use --verbose mode for more details.

$ npx codeceptjs run-rerun --steps

CodeceptJS v2.6.5
Using test root "/Users/grafn/projects/demp"

demo --
  test something
    I am on page "/"
  ✔ OK in 2321ms

  OK  | 1 passed   // 3s

Process run 1 of max 5, success runs 1/5

CodeceptJS v2.6.5
Using test root "/Users/grafn/projects/demp"

demo --
  test something
    I am on page "/"
    I am on page "/"
  ✔ OK in 1797ms

  OK  | 1 passed   // 3s

Process run 2 of max 5, success runs 2/5

CodeceptJS v2.6.5
Using test root "/Users/grafn/projects/demp"

demo --
  test something
    I am on page "/"
    I am on page "/"
    I am on page "/"
  ✔ OK in 1818ms

Details

CodeceptJS version: 2.6.5
NodeJS Version: 12.6
Operating System: MacOS
Configuration file:

const { setHeadlessWhen } = require('@codeceptjs/configure');

// turn on headless mode when running with HEADLESS=true environment variable
// HEADLESS=true npx codecept run
setHeadlessWhen(process.env.HEADLESS);

exports.config = {
  rerun: {
    // run all tests must pass exactly 5 times
    minSuccess: 3,
    maxReruns: 3,
  },
  tests: './*_test.js',
  output: './output',
  helpers: {
    WebDriver: {
      url: 'https://www.codecept.io',
      browser: 'chrome'
    }
  },
  include: {
    I: './steps_file.js'
  },
  bootstrap: null,
  mocha: {},
  name: 'demp',
  plugins: {
    retryFailedStep: {
      enabled: true
    },
    screenshotOnFail: {
      enabled: true
    }
  }
}

I think impact is rather low, this combination is not used that often. Maybe this is the reason I did not find any open issue.

I see this issue also

run-rerun was removed in 3.0

Fair enough 👍


[partitioning][state] Flexible partitioning and state preservation

If I understood correctly states is tightly bound to the number of the partitions.
Currently wallaroo requires to define partition function and the number of partitions only once during initialization of the cluster.
Resizing the number of partitions is not possible as previous states won't match the new scheme.
It would be better to decouple partition and state and have possibility to have multiple state per partition.
Otherwise the state objects will grow in size which would lead to high I/O and memory consumption.

Hi @niamster I believe that https://github.com/WallarooLabs/wallaroo/issues/751 addresses your concern.
In Wallaroo a state object, which are defined by the user, are the unit of transactionality, and parallelization. But because you currently have to define them ahead of time, you have to do something like:
Rather than having a state object per customer (where the number of customers might change over time), you have to define you state objects as a collection of customers and hash your unique customer identifier over the number of partitions established. In this way, Wallaroo is currently similiar to Apache Storm's fields grouping.
When #751 is addressed, you would have a state object per customer. You wouldn't need to articificially couple the partitions and the state objects.


Blackened and ruffed

@coderabbitai: ignore

Summary by CodeRabbit

Refactor: Improved code readability and maintainability across multiple modules by reordering imports, renaming variables, and updating function signatures.
Bug Fix: Enhanced error handling in the frames function in aeon/io/video.py to include more detailed information in error messages.
Documentation: Updated and clarified docstrings for several functions across different modules.
Style: Standardized string literals and import statements across the codebase for consistency.
New Feature: Modified the chunk and load functions in aeon/io/api.py to handle both single values and series of timestamps.
Test: Updated test cases in tests/io/test_api.py to reflect changes in the main codebase.

Note: revert changes to all files within 'aeon/dj_pipeline' - these will be appropriately reformatted in a separate PR


Emoji spacing in nwg-wrapper

First of all, very nice job on wttr.in; I rely on it every day! I am currently using nwg-wrapper and ansifilter to display v1 and v2 forecast, and was wondering if you could give me some tips on character spacing with emoji fonts, as it is rather important for v2 layout to appear legible.
My current issue is that whenever emoji symbols appear, line height and character width is slightly larger than a standard monospace character. This in turn throws things off alignment, and causes an overflow in the right. In addition, I do not really understand why but sometimes a monospace font symbol is used instead of emoji. Both of these symptoms can be seen for instance on the weather symbols line or moon phases line in the following screenshot:

The picture above was generated using the following script:
curl -s "https://v2.wttr.in/$city" | grep -v "^$" | ansifilter -c -M -F "Terminus" -s 11 --art-tundra

As a monospace font, I am using Terminus but I verified that the same result can be reproduced using any other monospace font. My emoji font is Joypixels. My ~/.config/fontconfig/fonts.conf file looks like this:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <alias>
    <family>monospace</family>
    <prefer>
      <family>xos4 Terminus</family> <!-- Your preferred monospace font -->
      <family>JoyPixels</family> <!-- Your preferred emoji font -->
     </prefer>
  </alias>
</fontconfig>

I read the part of the README re: URXVT, specifically the URxvt.letterSpace: 0 setting and the symbola font workaround. I was wondering if you are aware of an equivalent setting for pango, or something similar that could help me squeeze those emojis into their bounding box, so that the table does not spill over. Thank you for any ideas you can share!

Anyone here?

@chubin Hello?


@ts2doc/json - If file not found, no errors or logs, just empty array

Should do something

fix on 0.2.1


Error during postprocess - NZBGet to CP

Hi
I seem to be having a problem. I wasnt getting this error until recently after reinstalling Ubuntu Server.

Waiting for 65.0 seconds to allow CPS to process newly extracted files

NZBGet sits on this for 65 seconds and then while I am tailing nzbget.log I see this:
Sat Sep 17 00:46:52 2016	INFO	NZBGetPostProcess: 2016-09-17 00:46:52 - autoprocess.autoProcessMovie - INFO - Waiting for 65.0 seconds to allow CPS to process newly extracted files. Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess: 2016-09-17 00:47:58 - autoprocess.autoProcessMovie - INFO - Opening URL: http://localhost:5050/api/2f33a07423134ea186cc8a0c9931f448=/renamer.scan. Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess: Traceback (most recent call last): Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/opt/nzbget/scripts/NZBGetPostProcess.py", line 185, in <module> Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     autoProcessMovie.process(path, settings, nzb, status) Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/mnt/md0/nzbget/automator/autoprocess/autoProcessMovie.py", line 93, in process Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     rstate = r.json() Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 826, in json Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     return complexjson.loads(self.text, **kwargs) Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/usr/lib/python2.7/json/__init__.py", line 339, in loads Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     return _default_decoder.decode(s) Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/usr/lib/python2.7/json/decoder.py", line 364, in decode Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     obj, end = self.raw_decode(s, idx=_w(s, 0).end()) Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:   File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess:     raise ValueError("No JSON object could be decoded") Sat Sep 17 00:47:58 2016	INFO	NZBGetPostProcess: ValueError: No JSON object could be decoded
CP subsequently never processes the file.
I have double checked my API key.
When converting from Sonarr all goes well.
I can only imagine this is maybe a permissions issue? Although I dont see any permissions errors anywhere.
Ive restarted all services as well.
Any ideas at all would be appreciated. If you need any other information please let me know.

Something is going on with talking to CP. Either the API key or the server address or port is wrong. Or an HTTPS vs HTTP issue. Either way it's failing to connect to the CP API like it should.
Sent from my iPhone

On Sep 17, 2016, at 01:55, martylavender<EMAIL_ADDRESS>wrote:
Hi
I seem to be having a problem. I wasnt getting this error until recently after reinstalling Ubuntu Server.
Waiting for 65.0 seconds to allow CPS to process newly extracted files
NZBGet sits on this for 65 seconds and then while I am tailing nzbget.log I see this:
Sat Sep 17 00:46:52 2016 INFO NZBGetPostProcess: 2016-09-17 00:46:52 - autoprocess.autoProcessMovie - INFO - Waiting for 65.0 seconds to allow CPS to process newly extracted files.
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: 2016-09-17 00:47:58 - autoprocess.autoProcessMovie - INFO - Opening URL: http://localhost:5050/api/2f33a07423134ea186cc8a0c9931f448=/renamer.scan.
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: Traceback (most recent call last):
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/opt/nzbget/scripts/NZBGetPostProcess.py", line 185, in
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: autoProcessMovie.process(path, settings, nzb, status)
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/mnt/md0/nzbget/automator/autoprocess/autoProcessMovie.py", line 93, in process
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: rstate = r.json()
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 826, in json
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: return complexjson.loads(self.text, **kwargs)
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/usr/lib/python2.7/json/init.py", line 339, in loads
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: return _default_decoder.decode(s)
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: raise ValueError("No JSON object could be decoded")
Sat Sep 17 00:47:58 2016 INFO NZBGetPostProcess: ValueError: No JSON object could be decoded
CP subsequently never processes the file.
I have double checked my API key.
When converting from Sonarr all goes well.
I can only imagine this is maybe a permissions issue? Although I dont see any permissions errors anywhere.
Ive restarted all services as well.
Any ideas at all would be appreciated. If you need any other information please let me know.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Let me see what I can figure out . I was thinking the same thing as I was having issues getting PlexRequests to talk to CP as well.

Ok so actually it looks like Sonarr isnt working either. I end up with Sonarr responding that its queueing files. Something is def not working correctly.
Im not even sure where to start at this point.

Alright
I got my detective on and this is what I figured out.
I was totally confused this evening as I added a new series to Sonarr and had several episodes downloaded. They downloaded, converted, and imported into Sonarr / Plex / etc., without any issues. This baffled me.
I went and enabled Trace logging in Sonarr. I should have done this from the beginning.
sonarr.trace.txt:16-9-18 23:15:41.6|Debug|UnverifiedSceneNumberingSpecification|This file uses unverified scene numbers, will not auto-import until numbering is confirmed on TheXEM. Skipping /mnt/md0/nzbget/completed/tv/.mp4
I hoped over to TheXEM and sure enough....the series listings are alll kinds of jacked for this show. I remember that when Sonarr would search, the episode listings were always wacky. This was even more proven when I manually downloaded the episode by adding the NZB myself to NZBGet....once it downloaded and Plex updated the TV library, the show was displays as the same series but a different version of it altogether. Upon playing the show however, it was in fact the correct show. Soooooooo
Not an issue with your script.
I also noticed quite a few movies downloaded processed just fine as well.
I think we can close this one out.

Ok
I am still getting the JSON error for some reason:
Tue Sep 20 04:47:23 2016        INFO    NZBGetPostProcess: Starting conversion. Tue Sep 20 04:50:36 2016        INFO    NZBGetPostProcess: /mnt/md0/nzbget/completed/movies/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.cp(tt0096119)/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.mp4 created. Tue Sep 20 04:50:36 2016        INFO    NZBGetPostProcess: Successfully processed /mnt/md0/nzbget/completed/movies/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.cp(tt0096119)/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.mkv. Tue Sep 20 04:50:36 2016        INFO    NZBGetPostProcess: Successfully processed /mnt/md0/nzbget/completed/movies/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.cp(tt0096119)/Sleepaway.Camp.III.Teenage.Wasteland.1989.720p.BluRay.x264-SADPANDA.mp4. Tue Sep 20 04:50:36 2016        INFO    NZBGetPostProcess: 2016-09-20 04:50:36 - autoprocess.autoProcessMovie - INFO - Waiting for 65.0 seconds to allow CPS to process newly extracted files. Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess: 2016-09-20 04:51:41 - autoprocess.autoProcessMovie - INFO - Opening URL: http://localhost:5050/api/2f33a07423134ea186cc8a0c9931f448=/renamer.scan. Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess: Traceback (most recent call last): Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/opt/nzbget/scripts/NZBGetPostProcess.py", line 185, in <module> Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     autoProcessMovie.process(path, settings, nzb, status) Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/mnt/md0/nzbget/automator/autoprocess/autoProcessMovie.py", line 93, in process Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     rstate = r.json() Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 826, in json Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     return complexjson.loads(self.text, **kwargs) Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/usr/lib/python2.7/json/__init__.py", line 339, in loads Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     return _default_decoder.decode(s) Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/usr/lib/python2.7/json/decoder.py", line 364, in decode Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     obj, end = self.raw_decode(s, idx=_w(s, 0).end()) Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:   File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess:     raise ValueError("No JSON object could be decoded") Tue Sep 20 04:51:41 2016        INFO    NZBGetPostProcess: ValueError: No JSON object could be decoded

I'm not sure what to tell you, try accessing your CouchPotato API via a web browser and see if you get the expected JSON output


Test Adjust test_hive_write_partitions regression test to resolve special characters issue with git on windows.

Proposed changes
[Test] (hive-writer) Adjust test_hive_write_partitions regression test to resolve special characters issue with git on windows.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run external

run external

run buildall

run buildall

run buildall


I can'i search it form docker hub

I need to run it on my Ubuntu 22.04，  I can't find it when I was used "docker search ghcr.io/ika-rwth-aachen/mqtt_client:ros"

The Docker image is not published on DockerHub, but in GitHub's container registry, see here. docker search only searches DockerHub.
If you run it like docker run ghcr.io/ika-rwth-aachen/mqtt_client:ros, it will automatically pull the image from the GitHub container registry.

Thank you very much for your help!


Hub related documentation

we may have to link "via the Hub" to the Hub category or even to a guide. Not something that needs to be addressed right now but maybe we could create a task to track it? We will need to do it not only here, but it just occurred to me, that we should assume that some devs might now know what "via the Hub" means, or how to do it, when they are reading the docs of other categories.
Originally posted by @drochetti in https://github.com/aws-amplify/amplify-ios/pull/93

This is still a relevant issue and needs to be triaged and prioritized.

JS has hub docs: https://docs.amplify.aws/lib/utilities/hub/q/platform/js#listening-for-messages

this comment was from the category API doc comment at https://github.com/aws-amplify/amplify-ios/pull/93/files/4745ae542f4fc3caa241aaef0bc8a0bd1b88fc05#diff-a6e16f7d518ba3f3535817d6749ba4e746e922ca12c821d40372eb2223dd3600
/// Perform a GraphQL subscribe operation against a previously configured API. This operation
    /// will be asychronous, with the callback accessible both locally and via the Hub.

As mentioned in the comment thread, discuss a "How it works" in the API documentation and point to Hub documentation, similarly use JS has a reference for a Hub documentation structure


Latest docker image "500 Internal Server Error"

Just pulled the latest docker image and I'm getting a "500 Internal Server Error" when I try to schedule a post. going to roll back for the time being
not too sure going about saying what all version the image is an all, but portainer gives me a checksum
sha256:0279b1ccdb9095a0f83cca1dcc40d19045d2db2451ac9286f47284185aa4e9d0
for the current image I'm using

okay figured out how to find it image version. the image I'm currently using is 1.3.3, which is borked for trying to schedule posts

<IP_ADDRESS> - - [16/Oct/2023:01:32:36 +0000] "GET /post/create HTTP/1.1" 500 1353 "http://unas.hanlan:8074/post/list" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"
<IP_ADDRESS> - - [16/Oct/2023:01:32:35 +0000] "GET /post/list HTTP/1.1" 200 4279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"
[Mon Oct 16 01:32:36.772882 2023] [php:notice] [pid 45] [client <IP_ADDRESS>:3122] [critical] Uncaught PHP Exception Twig\\Error\\RuntimeError: "An exception has been thrown during the rendering of a template ("Unable to generate a URL for the named route "app.post.ajax.title_expression" as such route does not exist.")." at /var/www/html/templates/post/create.html.twig line 10, referer: http://unas.hanlan:8074/post/list
<IP_ADDRESS> - - [16/Oct/2023:01:32:35 +0000] "GET /build/fonts/fa-solid-900.1551f4f6.woff2 HTTP/1.1" 200 78557 "http://unas.hanlan:8074/build/app.195b04ee.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"
<IP_ADDRESS> - - [16/Oct/2023:01:32:35 +0000] "GET /build/app.195b04ee.css HTTP/1.1" 200 57083 "http://unas.hanlan:8074/post/list" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"
<IP_ADDRESS> - - [16/Oct/2023:01:32:35 +0000] "GET /build/app.2fd1a0c3.js HTTP/1.1" 200 9253 "http://unas.hanlan:8074/post/list" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"

so rolling the docker image back does not resolve the not being able to schedule issue. other than that scheduled posts seem to still be posting an all.

k, figured out there's something in my cache that isn't playing nice since updating to 1.3.3. if I nuke my cache it resolves this issue. however this isn't ideal at the moment because I have several days of posts lined up. once my posts finish posting I'm just going to nuke the cache.
let me know if you want the backup of the cache I made to poke at.

Can you send the cache?
There should be a directory called pools, this is the one that contains your data and should be preserved, can you try deleting the others (keep a backup of the whole directory, though)?

copy of my cache
cache.zip

deleting everything but the pools folder works

I'm failing to reproduce the issue, was it perhaps caused by the stale cache?

Closing the issue, feel free to reopen if the issue still persists.

I'm having the same problem with a fresh installation.
The problem seems to only happen with recurring weekly posts. I can change the time without problem, but if I try to change the day of the week, I get the pop-up error.
I was able to schedule a weekly post on Monday, because Monday is filled in by default and there's no error if you don't change it.

Closing the issue, feel free to reopen if the issue still persists.

The issue is entirely unrelated. It's been fixed in #20.


add nix support

[X] packages
[TODO] Modules

Adding the environment variable of git_hash can be easily solved.

@blaggacao
At present, I am exploring nix-driver related things. I  think the graph based on petri-nets is enough for use. Maybe we can examine the way for funflow in the future. For std flow implementations, I'd instead put them in the backend than wait in a tty for an indeterminate amount of time. Whether it's a c4 model or a jobs dag, it's sufficiently to analyze the data by json.

@blaggacao you can find the example of the config files here https://github.com/sphenlee/waterwheel/blob/main/sample/jobs/complex-dag.yml
At present, I am exploring nix-driver(worker side) related things. I think the diagram based on petrinets is enough for use. Maybe we can examine the way for funflow in the future. For std flow expectation, I'd instead put them in the backend than wait in a tty for an indeterminate amount of time. Whether it's a c4 model or a jobs dag, it's sufficiently to analyze the data by json.

Regrading Add std flow divnix/std#49,  Maybe we just need to add a watcher for flow in justfile.
std workflow,  waterwheel would help us to achieve this motivation.

Do you know about funflow? you might be interested this project. I would like to add a notebook for the waterwheel to research the seeable and logical structure of the job, even DC field.

this looks awsome.

The nix PR works well for now. @sphenlee. Next, I'm going to talk about other features which need to be implemented.


⚠ Bofrost.fr has degraded performance

In 338c43d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1028 ms

Resolved: Bofrost.fr performance has improved in 1ae07c3.


Need more information about seasonal SVR

Hi,
First, it is a great article for a beginner like me.
I have an interest in time series forecasting using SVR.
And your code help me a lot to learn SVR.
I have question about your code, about "Convert observations into the seasonal learning data".
Can you give more information about that code ?
Regards

Hello @kusumy
We need to transform a timeseries into a number of s-dimentional vectors that represent the seasonally grouped data points. If you have a question about how the grouping of points in a time-series has been done, carefully read the build_seasonal_learning_sequences function's implementation. If you have problems with understanding the code, probably it is useful to learn more about NumPy (https://numpy.org/doc/stable/)
If you wonder why we actually need to "group" data from a season together, check the slides (particularly the slide "How to build a model" in the SVR section) and the usage of the SVR in sckit-learn
best,
Andrii


Feature Request: Enable half-closed with CloseWrite

I'm writing a TCP reverse proxy over Websocket and I'm trying to use this library.
However, it provides no way to close the write side only. That's needed to indicate end of stream (EOF), which gets mapped to a FIN on the TCP connection to the origin.
Looking at the code, I see that Close() runs the full handhsake. Perhaps CloseWrite could just send the close message with the normal status, but not wait for the response. And the code should not close the connection when receiving the close message. It should only do that on the explicit Close() or CloseWrite() call by the application code.

Hi, @fortuna.
Interesting use-case. From what you describe it sounds like it's somewhat in conflict with RFC 6455: 5.5.1:

If an endpoint receives a Close frame and did not previously send a
Close frame, the endpoint MUST send a Close frame in response.  (When
sending a Close frame in response, the endpoint typically echos the
status code it received.)  It SHOULD do so as soon as practical.

Essentially this states that the close handshake should happen, i.e. we can't send off a close-frame without receiving one back. Although the receiving side could delay the close for the current message.

An endpoint MAY delay sending a Close frame until its current message is
sent (for instance, if the majority of a fragmented message is
already sent, an endpoint MAY send the remaining fragments before
sending a Close frame).  However, there is no guarantee that the
endpoint that has already sent a Close frame will continue to process
data.

But with regards to closing the underlying TCP connection, the spec is pretty clear:

After both sending and receiving a Close message, an endpoint
considers the WebSocket connection closed and MUST close the
underlying TCP connection.  The server MUST close the underlying TCP
connection immediately; the client SHOULD wait for the server to
close the connection but MAY close the connection at any time after
sending and receiving a Close message, e.g., if it has not received a
TCP Close from the server in a reasonable time period.

In the clients case, we could probably change the behavior a bit, but I'm not sure if that would be helpful for your use-case? Given the above, does it sound like what you want to achieve is possible? If yes I'm probably not fully grokking what you're looking to do and would appreciate some more details.

Unfortunately the RFC text is a bit limiting, but not completely.
For the "MUST send a Close frame in response", we will always send a Close, but later. The "as soon as practical" is a SHOULD, so we would not be in violation of that.
They say that the client MAY delay the Close until its current message is sent. But it doesn't say it MUST be sent right after the message, or that sending it after future messages is forbidden. That's where the RFC text is lacking. Sending it later is not in violation of the text, but the text doesn't make it clear it's safe, unfortunately.
As for closing the TCP connection, that's fine, because the client will send a TCP FIN when it sends the Websocket Close, and receive a FIN when it receives the Websocket Close, ensuring TCP is fully closed when Websocket is.
In my case, I control both the client and the server, so I could ensure that is working. However, that will certainly tie my implementation, and I'm not sure what other reverse proxies will do along the way. I intend to put my reverse proxy behind CDNs like Cloudflare, who may have a different interpretation of the RFC.
I'm still debating what's the best way to proceed:

Modify the library to support the half-close I mention in this issue
Implement an application-layer protocol on top of Websocket for TCP streams. That effectively introduces an new protocol, which I'd rather avoid.
Perhaps use boundless messages instead. I'm trying to figure out how that works. But if possible, I'll make the entire TCP stream be one message. That way it's clear the stream is done.

@mafredri does this implementation support unlimited messages?


Fga bug report

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1855
Describe the bug
I think it cant scan the screen properly. I try to choose the map for it and it scan the support set up like normal but do nothing. I try to turn on and off ignor notch too but it wont work either
Video
Link to the video  https://youtu.be/M7mcaGD3izM
Device model
Redmi 9T
Android version
10
Screen size
6,53 inches
RAM
4GB

Disable and re-enable accessibility services and check out this site

Disable and re-enable accessibility services and check out this site

I have done like you said and it still wont work. What should i do next ?

The screen detection is not the problem, clicks aren't triggered.
Can you try restarting your phone after disabling the battery optimizations?

The screen detection is not the problem, clicks aren't triggered.
Can you try restarting your phone after disabling the battery optimizations?

Thx you so much, it work normal now


exclude_from_localizations won't exclude files containing a front matter

Since the fix of issue #70, only static files are being excluded using exclude_from_localizations.
Files that include a front matter, which are treated by Jekyll as a page are not being excluded, this includes sass and js files which can contain an empty front matter and are processed as pages.

Any workaround to exclude files with front matter?

I would like to exclude a html file and I'm experiencing this problem now. Is there anything new about the fix?


Test

@vishalops87 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


We need az-core module to put common code

azkaban-common sub module today is too common. The original authors put too much burden in this place. Any other module relied on  azkaban-common can not call code there, so it causes problems. We need to create az-core module, which should be the baseline foundation class for all other az modules. For instance, Metrics Registry class should be there, and all other modules can call it to register monitoring.

#1461


branch dev build error

Hi All, I'm trying to build the DEV branch, but I get the follwing error, any idea ? the clarity image is trying to use a proxy called proxy.vmware.com ....
make install -e GOBUILDIMAGE=golang:1.7.3 COMPILETAG=compile_golangimage -e CLARITYIMAGE=danieljt/harbor-clarity-base:0.8.3
➜ Better to upgrade golang package to 1.6.0+ or use golang docker image build binary.
Note: docker version: 1.10.3
Note: docker-compose version: 1.8.0
compiling binary for clarity ui...
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info attempt registry request try #1 at 10:28:36 PM
npm http request GET https://registry.npmjs.org/fs
npm info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy.vmware.com proxy.vmware.com:3128
npm info attempt registry request try #2 at 10:28:46 PM
npm http request GET https://registry.npmjs.org/fs
npm info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy.vmware.com proxy.vmware.com:3128
npm info attempt registry request try #3 at 10:29:47 PM
npm http request GET https://registry.npmjs.org/fs
npm ERR! Linux 3.13.0-54-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.5.0
npm ERR! npm  v4.1.2
npm ERR! code ECONNRESET
npm ERR! network tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy.vmware.com proxy.vmware.com:3128
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR!     /clarity-seed/npm-debug.log
make: *** [compile_clarity] Error 1
Thanks.

roldancer, thanks for pointing this. The 0.8.3 is now an internal used image for Harbor development, we will provide an clean image soon without npm proxy.

@roldancer the clarity image has been upgraded to 0.8.4 which doesn't contain the proxy info. We have closed this issue, if you still encounter any error, feel free to reopen it.


Improving existing translations

I have built a system that helps to improve the translations of (open source) programs: https://btranslator.net/ It allows users to suggest improvements to existing translations.
I think that it can be customized and adopted for the Quran and its translations. We can have a site like qtranslate.org or translate.quran.com with all the verses and their translations. Then, when somebody wants to suggest a fix or a better translation on quran.com, they click on it (or an icon next to it) and are redirected to the translation site (similar to this example: https://btranslator.net/translation-context). Their suggestion is reviewed by the moderators (at least one for each language) and they decide to accept it and make it official (and transfer it to quran.com).
I can start by trying it first with just English and Albanian languages, and later we can add other languages. But I will need the data for these two languages first (and the Arabic text of the Quran). Anyway, for a month or two I will be busy with some other things, but this should not stop us from discussing and planing it right now.

Some other issues related to fixing/improving translations:

https://github.com/quran/quran.com-frontend/issues/145
https://github.com/quran/quran.com-frontend/issues/37
https://github.com/quran/quran.com-frontend/issues/38

i like this issue, i'm :+1: on it

@dashohoxha I am a fan of this too. It's something we wanted to build previously but no time. I almost see it to be much like stackoverflow; answers and upvotes.

Yes, it is somewhat similar to stackoverflow, but not so much.
Forget about building it yourself, it is much more complex than it seems to be. It is easier to start with an existing application and to customize it.
However it is also separated into a back-end (database) and a front-end (UI), which communicate through an API. So, if you don't like the interface, it is quite possible (and maybe quite easy) to build another UI (for example with React). For example, vocabulary (http://v.btranslator.org/) is a simple javascript app that uses this API.

i like this also @dashohoxha

I have started this: https://github.com/Q-Translate
which is basically a clone of this: https://github.com/B-Translator
(with some renaming).
It still needs some work to make it run properly.
Then, maybe it will need some customizations, since it is a bit different from translating programs.
When done, we should have a translating server and API like this: https://btranslator.org/
and also a translating web interface like this: https://btranslator.net/

I have installed it here: https://qtranslate.org/ and https://qtranslate.net/
Of course it does not do yet what it is supposed to do.

I have made some progress:

https://qtranslate.net/qtr/
http://info.qtranslate.org/api/
But there is still lots of things to done and to be fixed.
Anybody would like to help, or at least to encourage me by subscribing (watching the project on github)?

I have some problems displaying correctly the Arabic text (verses of the Quran).
For example look at this: https://qtranslate.net/qtr/en/2/3 I see there some empty boxes.
The same here: http://info.qtranslate.org/api-examples-js/#translations/get.js
I also see the same thing on phpMyAdmin when I look at the content of the DB.
And this is very common, not just a single isolated case, for example see this:
https://qtranslate.net/qtr/search?words=unseen&lng=en
I use utf8 as character encoding and the mysql DB is of type utf8-general-ci.
Does anybody know what may be wrong and how to fix it?
P.S. Maybe this is not the propper place to ask for help on this, but I don't know any better place.

For your information, the text of the Quran needs the font me_quran to be rendered correctly (like this: https://github.com/Q-Translate/qtrclient/commit/508e2c7b520c35ea0010c03312c9c5f2835a60ab)

This feature (correcting or improving existing translations) can be implemented simply by adding a link to the corresponding verse on qtranslate.net
For example, to correct the English translation of (2,3), the link should be: https://qtranslate.net/qtr/en/2/3

Would be better to have this internally and then admin should look through if people submitted valid responses (such as typos etc.) then when he accepts them, they should update a revision nr, and that should be passed in API as well, as well as new feed.  There are multiple english translations and other languages... Other languages will be added to quran.com in the future, so it should use an unique identifier, to connect to the correct translation. (i.e. the shuyukh here are working on a Danish translation, so that should be added at some point when released... I got 3 indexed danish quran translations that are popular here, but they are all translated by some doubtfull individuuals and have some mistakes in them...).
I think it is too early to close this "issue" at its current state

@ATouhou  The aim of the site https://qtranslate.net is precisely to double check translations, fix any mistakes or typos, and encourage people to think and discuss about the right translation of the Quran verses. (I also think that this is a useful mental excercise that may help people to understand better the real meaning of the Quran.)
This may include Danish translations as well, if there are people interested about them.
For the time being https://qtranslate.net is on the testing phase and there are also a few things still to be done, before it becomes fully functional. If anybody is interested, we can continue the discussion here: https://github.com/Q-Translate/qtr_server/issues (testing, finding and fixing bugs, improvements, etc.)
If you wish, we can add the Danish translation for testing.
However, related to quran.com, it can just add a link to https://qtranslate.net, in case that somebody wants to correct a translation. This is why I closed the issue. Do you think we should reopen it?

Yes.
Most people aren't qualified to translate any verse, so their changes should not be activated right away. I was refering to typos or mixups in quran translations, which there are some dousin reports in the quran-android repo.
However if the purpose was for adding benefitial tafseer / quotes, / examples to ponder,   i.e. any fawaaid really from any verse,  that would then also be double checked by admin with correct aqeedah and knowledge, before posting, then that would be great :-)
This way, there would lot's of info about each verse.
Reason of revealing (azbaal ul nuzol),  commentary from sahaba, any beneficial tafseer and relation to other verses,  if is mansookh or not ,  the miracle of the elequoence of the ayah,  anathing beneficial,  that would be great...
So maybe the qtranslate.org should  pivot into this model and the correcting / report error/mistake  should be implemented directly into quran.com :-)   What do you think ?

Before I can understand your speech, you have to explain me what is: tafseer, fawaaid, aqeedah, mansookh, etc. Sorry, I still belong to the domain of the ignorants, not to the people with high knowledge.

So maybe the qtranslate.org should pivot into this model and the correcting / report error/mistake should be implemented directly into quran.com :-) What do you think ?

I am glad to leave that model to quran.com for implementing, and to stick to the humble goal of fixing translations only.

Very bad translations below:
Tafseer: explanation.
Fawaaid: Benefits.
Aqeedah: Matters of belief.
Mansookh: Quranic verses that has been replaced by new verse.
It's good to fix the translations, like in a danish translation somebody just found a typo which made the ayah "hide the truth, while you know" as "hide falsehood, while you know"
and as you see in these 2 github repos (quranandroid and this)  , there are several typos etc. in many of the popular translations.
However I do not think anything should be replaced without it being looked upon by an admin.
There are many sects and many wish to replace ayat such as "istawa 3la l-arsh" to something other than it's real meaning etc.
So for fixing translations, this should be internal where they just click an "report error / improvement", and it will ask them for details.
Sunnah.com already has this:

could work as an email, or as an automated system, that when admin edits/updates it will update api and increase revision nr etc, :-)

However I do not think anything should be replaced without it being looked upon by an admin.

In qtranslate.net, it is not a matter of replacing a translation, it is like adding another, alternative, translation. Then it is the community which decides which translation is the most correct and the best one.
But in the end, still it is a qualified/authorized person (you may call him admin), who decides which translations should be transferred to tanzil.net.
I don't understand that thing with revision numbers and api, that you are trying to explain. Why don't you try to understand how qtranslate.net works?

I do understand how it works brother.
However there are 2 things to be aware of with community driven sites.
Sufi and shiaa will try to edit whatever they don't like.
Allah scorns the majority, multiple places in the Quran and we can't make decisions based on the majority, this concept in itself is flawed.
The version numbers are so that people that had local copies, can do automated system update from API, with new version - or just keep track on fixes.

I do understand how it works brother.

Maybe. But I feel that there are a few important details that you have missed. You can fully understand it only if you try it.

Sufi and shiaa will try to edit whatever they don't like.

We cannot force our understanding to them, and they cannot force their understanding to us. There is no compulsion in religion. The program can accomodate the views of everybody. Wherever we agree it renforces the agreement, wherever we disagree it allows the diversity.

Allah scorns the majority, multiple places in the Quran and we can't make decisions based on the majority, this concept in itself is flawed.

The question is: the majority of what? I agree that in questions of personal believes and personal understanding the majority plays little role, although it may be quite useful in other cases.
Anyway, the program can accomodate the views of minorities as well, so there is no need to "fight" about who is right and who is wrong.

The version numbers are so that people that had local copies, can do automated system update from API, with new version - or just keep track on fixes.

I still think that this is not relevant to qtranslate.net. It leaves versioning up to tanzil.net, as a central authority for translations. Because after being corrected, translations can be exported and re-submitted back to tanzil.net.
However there are means of keeping track of what is going on, what has been changed recently. One of them is RSS feeds.

I have made the first release of Q-Translate and some testing is needed:

https://github.com/Q-Translate/Q-Translate.github.io/issues/1
https://github.com/Q-Translate/Q-Translate.github.io/issues/2

Anybody can help?


updated link for the community edition of docker

The install instructions pointed to an outdated link for the community edition of docker. I have updated the link to point to https://docs.docker.com/install/.

Thanks! And welcome to the ever growing list of people who have contributed to repo2docker :)


Add react-native-svg to whitelist

This PR adds https://github.com/react-native-community/react-native-svg to whitelist in order to use it's typings in react-native-svg-charts.
Related PRs:

https://github.com/DefinitelyTyped/DefinitelyTyped/pull/25880
https://github.com/JesperLekland/react-native-svg-charts/pull/142

@andy-ms PTAL


Add support for border properties to be blacklisted

Follow up of #16

Adds all border size properties to black list
Updates README

thanks for the pull request! @lutien
will check

Discussed in #16, that there is no need for this


No 'UTXO diagram' specification.

When producing UTXO transition diagrams, we should abide to a standard format. This standard format needs to be documented in a file in docs/meta. This will be useful for new specs writers and serve as a 'legend' for those looking at UTXO diagrams in the specs. Wherever a UTXO diagram appears in the specs, a hyperlink to the schema should be included.

Closing this. We'll use draw.io where it's useful due to the relatively decent integration with Notion.


[stable/prometheus-operator] grafana login specified in config not valid

Describe the bug
I've set a password in the values file, using the password specified along with the admin user does not work as expected. I've verified the secret used by the deployment is populated with the correct password.
Version of Helm and Kubernetes:
Helm: 2.14.3 (client & server)
K8s: 1.11.9
Which chart:
stable/prometheus-operator
What happened:
Grafana login is telling me "Invalid Username or Password".
What you expected to happen:
Grafana login to succeed with the password I provided in my values file.
How to reproduce it (as minimally and precisely as possible):
Install prometheus operator, specify a customer adminPassword for grafana.
Anything else we need to know:
This is the values file I'm using:
coreDns:
  enabled: false

kubeDns:
  enabled: true

alertmanager:
  alertmanagerSpec:
    resources:
      requests:
        cpu: 100m
        memory: 250Mi
      limits:
        cpu: 100m
        memory: 250Mi
    storage:
      volumeClaimTemplate:
        spec:
          accessModes: ["ReadWriteOnce"]
          resources:
            requests:
              storage: 10Gi

prometheus:
  prometheusSpec:
    resources:
      requests:
        cpu: 1
        memory: 2Gi
      limits:
        cpu: 2
        memory: 2Gi
    storageSpec:
      volumeClaimTemplate:
        spec:
          accessModes: ["ReadWriteOnce"]
          resources:
            requests:
              storage: 50Gi

grafana:
  adminPassword: "REDACTED"
  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.class: nginx
      kubernetes.io/tls-acme: "true"
    hosts:
      - grafana.example.com
    tls:
      - secretName: example-k8s-dns
        hosts:
          - "*.example.com"
  persistence:
    enabled: true
    accessModes: ["ReadWriteOnce"]
    size: 10Gi

I was able to address the issue by deleting the PVC for grafana. Not sure what could have happened here.


[Dashboard] Adding widget to dashboard is buggy in firefox

Description:
In firefox, when you try to "drag" a widget from the top right onto the dashboard there is a poor user experience where fire fox initially prevents you from dragging the widget, and instead grabs the image of the icon you clicked initially.
Reproduce:

Open dashboard in firefox
Click on line chart, and drag onto dashboard

Expect behavior to behave in the same manner as chrome
Observed behavior is the widget fails to drag
Acceptance critera:

User experience of dragging a widget onto the dashboard in firefox matches chrome.

resolved in https://github.com/awslabs/iot-app-kit/pull/2085


App should not suppress iOS predictive keyboard

In recent versions of iOS predictive keyboard has been introduced. However it is for some reason not possible to use the app with this. (No third party keyboard here, I'm just using the built in default.)
This results in a lot of typos. :(

Tracking this issue in Jira: https://mattermost.atlassian.net/browse/PLT-98


Extend AwsService:getAuthorizationHeader() / AwsV4Signature:getAuthorizationHeader()

In order to allow the caller to pass the arbitrary host name for signer to calculate the hash with.
In order to enable the caller to obtain the payload sha256 hash which is used to calculate the signature and must be passed to the endpoint along with the other signed headers.

These changes are essential to use S3 API.

I am currently using the following patch with 1.7.0 to allow generating signatures for s3 AWS4 using proxy_pass in openresty:
diff --git a/src/lua/api-gateway/aws/AwsV4Signature.lua b/src/lua/api-gateway/aws/AwsV4Signature.lua
index 3936937..8f9af85 100644
--- a/src/lua/api-gateway/aws/AwsV4Signature.lua
+++ b/src/lua/api-gateway/aws/AwsV4Signature.lua
@@ -28,6 +28,8 @@ function HmacAuthV4Handler:new(o)
         -- services that want to suppress this, they should set it to false.
         self.doubleUrlEncode = o.doubleUrlEncode or true
     end
+    local divider = self.aws_service == "s3" and "-" or "."
+    self.aws_endpoint = self.aws_service .. divider .. self.aws_region .. ".amazonaws.com"
     -- set amazon formatted dates
     local utc = ngx.utctime()
     self.aws_date_short = string.gsub(string.sub(utc, 1, 10),"-","")
@@ -153,12 +155,11 @@ end

 function HmacAuthV4Handler:getSignature(http_method, request_uri, uri_arg_table, request_payload )
     local uri_args = self:formatQueryString(uri_arg_table)
-    local utc = ngx.utctime()
     local date1 = self.aws_date_short
     local date2 = self.aws_date

     local headers = {}
-    headers.host = self.aws_service .. "." .. self.aws_region .. ".amazonaws.com"
+    headers.host = self.aws_endpoint
     headers["x-amz-date"] = date2

     local encoded_request_uri = request_uri

As noted by @jlapier the distinction of s3-region.amazonaws.com vs. s3.region.amazonaws.com doesn't really seem to be needed and could be fixed in my case by using the dot seperator when defining the endpoint mapping in the nginx config.
For local testing though I really need to be able to pass in the endpoint, so I can use this with minio.
I'm not really familiar with lua, so not sure if my changes are the right way to do it.


Return object from set method

Just a small change to return the object from the set method. I find it convenient in some cases, and it does not add any significant overhead.
Feel free to merge if this makes sense to you. Tests and readme are updated accordingly.

I find it convenient in some cases

Do you have an example of that? I'm trying to think of when it would be useful.

@sindresorhus As an example, I have a function that takes a value, does something to it, and returns it at a path in a new object. (The path is provided at run-time, so regular JS object notation is not an option.)
When set does not return the object, I have to write:
const object = {}
set(object, path, value)
return object

With this PR I could simply write:
return set({}, path, value)

It's not a big issue – just for convenience. :)

Makes sense. Can you use something like that in the readme example too? const foo = obj => dotProp.set(obj, 'unicorn', '🦄'); Makes it easier to understand the use-case of it.

Sure. I had an example of the return value, but it wasn't clear enough. Changed the input to an empty object, so it is clearer what the point of it is.
Sorry I didn't return a unicorn.


Feature/linear spectral unmixing

@jdrisdelle @akferoz please take a look.  My fork includes the latest commits from this repo's master, but really the only true contribution from my end should be the addition of functions/LinearSpectralUnmixing.py.  If we need to revisit how things were handled on my fork before we accept this PR, please let me know.  Thanks!

@jdrisdelle, @jwasil: PR merged with LinearUnmixing branch (off master, here: https://github.com/Esri/raster-functions/tree/LinearUnmixing).
I'll merge changes to master after the few remaining issues with ArcGIS 10.3.1 and Pro are resolved. @jwasil, you can continue making changes (if needed) on your fork as well. I'll pull at least once more before merging with master.

@akferoz this sounds good, thanks.
What do you think about the default value for input param 2, at https://github.com/Esri/raster-functions/blob/LinearUnmixing/functions/LinearSpectralUnmixing.py#L25 ?
This default value was convenient for me when testing endmember signature means for my specific Landsat testing scene, but I was thinking that it should be clear to the end-user that the input here needs to be changed.  However, it also serves to show how it should be formatted going in.  There are also some limitations on the total number of endmembers that can be supplied to the function.  Just trying to brainstorm on ways to convey this info clearly.

:+1:

Thanks @jwasil!

My pleasure, @scw! If you end up using it and have any ?'s, feel free to let me know.


doubled namespace in input id

If I have namespace attribute set on form, all inputs ids include that id twice. E.g
semantic_form_for  ... namespace: "foo"
<input id="foo_foo_user_name" />

I'm using formtastic 2.0.2 and rails 3.2.1.
Gemfile.lock (https://gist.github.com/1717300)

Please bundle from master branch or use formtastic gem with at least version 2.1.0.pre1 for rails 3.2 support

Sorry about that. Thanks!


Is there any chance to use this with Nuxt?

Describe what you want:
It's working like a charm in Vue, but running the same code in Nuxt results in "ReferenceError: window is not defined".
Is there any workaround?
Thank you"

Nevermind, it's working out of the box. If anyone else has trouble configuring it to run with Nuxt, here is the solution:

if not exists, create a 'plugins' directory in project folder
create file 'vue2-scrollspy.js'
add code:
import Vue from 'vue' import Scrollspy, { Easing } from 'vue2-scrollspy' Vue.use(Scrollspy, {   easing: Easing.Cubic.InOut })
extend your 'nuxt.config.js' file:
module.exports = {   plugins: [{ src: '~/plugins/vue2-scrollspy', ssr: false }] }

that's it :)

Anyway using this module is sh...


Update readme.md

add dwm to support list. Been using with dwm on multiple machines inc FreeBSD

Just came out of the grave. Thanks for your contribution :)


Test fails on evals/requires

Although we should simply abort evaluation of submissions with potential malicious  code instead of making test fail, the proposed approach in this PR is better than nothing.

@faloi Please comment


Removing unused ttf-dejavu package

The package ttf-dejavu adds 17MB to the alpine images (and probably similar for Ubuntu). I unable to identify through source history why the package was added in the first place. Being a server environment, fonts are not typically applicable.

:+1:


chore: bdd-nh-1586105701 to 0.0.1

chore: Promote bdd-nh-1586105701 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


"Star"ratings should be rendered as stars, not as "4 *"

So we always want to see 5 stars, but in case of a 3-star rating, three of them should be saturated/blue, and two should be light-gray.


Issues integrating with Sapper

Hi there! First off I wanna thank you and Alex for these great projects. Performance is absolutely fantastic for a node.js server, easily beating Express 5x.
While integrating with Sapper (to perform server-side rendering) I ran into a number of issues I believe are bugs. Sapper uses an express middleware to run all the routing etc.

req.originalUrl is unimplemented - https://expressjs.com/en/api.html
req.baseUrl also appears to be unimplemented but this wasn't a problem for me, just something to look out for?
Setting res.statusCode caused the request to hang, with error 'Text and data can only be passed by String, ArrayBuffer or TypedArray.' (this originates from uWebSockets.js) even though res.end sent a string. I was able to fix this temporarily with Object.defineProperty: Object.defineProperty(res, 'statusCode', {     set: val => (res.rawStatusCode = val),   });. res.status didn't work either and caused the same issue as setting res.statusCode. I'm not sure whether rawStatusCode actually does anything though. I couldn't find any good examples on setting the status code other than skimming https://github.com/dalisoft/nanoexpress/blob/master/src/proto/http/polyfill-chunks/status.js.
Normally you're meant to do app.use(sapper.middleware()), but I had to do app.any(sapper.middleware()) with nanoexpress, as the app.use didn't fire at all. Additionally, when using app.any any app.uses would still not fire: app.use((req, res, next) => console.log(req, res) || next()); before the app.any wouldn't cause anything to log.

I also found app.setErrorHandler and app.setNotFoundHandler a bit strange. It's nice and convenient but I can imagine it throwing express veterans off, especially given that app.use doesn't seem to work.
I've been able to fix all of these in my application code, but it was time consuming to figure out what was going wrong. Given that these are all minor issues I figured it would be better to make a single issue. If you need any help with a test case let me know.

Hello and big thanks for report and using nanoexpress.
I am firstly express user, then transited to fastify, so i am forgot polyfill a lot of methods and properties and i am very happy to see this library helpful to someone than me.
I am would be happy to fix these bugs, make tests to these issues. Are you able to test when fix.
Also, i am uses different solution for middleware than using like router for performance and better error handle reason.
Middleware will call if any of route was defined and calling. If no one defined, you can fix this by app.any(‘*’, () => {}). Express-like solution is best, that solution performance differs by 2x on medium-scale apps and reduces hosting cost by from 2 up to 25 times depending on your application code which is huge for startup projects and even for huge applications. I hope you understand why i used different solution than express.
About other like status or polyfill properties i will look tomorrow, today bit busy.
Thanks again

Yup, I will be able to test. That makes sense; it would be helpful to document it though. Thank you for your time!

I also just found one more issue that is particularly annoying as it doesn't appear to have a good workaround. req.method is set to ANY when using app.any(...). The d.t.s says you should use req.getMethod() from uWebsockets.js for this method, however trying to use this method in app.any(...) will always hang because req is deallocated by then (Using uWS.HttpRequest past its request handler return is forbidden (it is stack allocated).) because there is an await inbetween calling the user handler.
Sapper uses req.method to determine which module method (get, post, etc.) to call. When it's set to ANY all server routes fail.
I've done req.method = "GET" for now but this obviously won't work for post methods.

Hi @caresx
Please, can you test, issue is fixed in v0.12.15 or still available?

@caresx
I am also added status change example

Hi! A number of issues still exist, but req.originalUrl is fixed now. Setting res.statusCode (= 200 for example) still breaks the app with the same message but res.status works now. req.method is still ANY for app.any routes and req.getMethod() still crashes inside app.any. The fix applied for req.baseUrl is also not correct and I've had to set it to '' for now. req.baseUrl is supposed to be used for subrouters however it's not very useful and I think always setting it to '' is fine (note that setting it to '/' caused mime errors for all my static .js files, so it really needs to be an empty string). Thanks for your time!

Hi @caresx
Can you test now?
Also i am did polyfill which should atomically call app.any() even if you not define app.any() after using app.use() (can you test this functionality too?)
Thank you for your test and time :)

Yup, every single issue is resolved! Behaves exactly like express. Thank you very much for your time! Very excited to try out websocket support too, very promising

Thanks for report, test and help.
Happy to see users able to use this library


Line chart ignores beginAtZero if no y-values are present

In ChartJS 2.1.0 a line chart ignores the beginAtZero option, if no y-values are present. This was also mentioned in https://github.com/chartjs/Chart.js/pull/1581#issuecomment-151992967 . I want to avoid having negative values.
Config:
                type: 'line',
                options: {
                    scales: {
                        yAxes: [{
                            ticks: {
                                beginAtZero: true
                            }
                        }],
                        xAxes: [{
                            gridLines: {
                                display: false
                            }
                        }]
                    },
                    responsive: true,
                    maintainAspectRatio: false
                }

Screenshot:

Works as expected in 2.1.2. Thanks for the quick fix.


Code coverage on errors and schema_helper

What is the context of this PR?

Added new functions to check whether there are any duplicate aliases
Removed unused code

How to review

Check to see tests work correct

Check that code was definitely unused

Still some left to do on errors.py, not in for next two days, didn't want to leave as is.

@jonnyshaw89 happy with this PR now?


Update documentation about HTML Report

In HTML Report section of the current README.md, it shows
await checkA11y(
      page,
      'form',
      {
        axeOptions: {
          runOnly: {
            type: 'tag',
            values: ['wcag2a'],
          },
        },
      },
      true, 'default',
      {
        outputDirPath: 'results',
        outputDir: 'accessibility',
        reportFileName: 'accessibility-audit.html'
      }
    )

However, when I tried creating the HTML report based on this example, 'default' as a value of reporter parameter did not work, and this function call did not create a report file. Instead, I had to use 'html' option for this value.
I am not sure if this code snippet is an actual working example, but it would be great if this can be updated to avoid confusion.

@torimori-k would you mind raising a PR for the same?

I couldn't link my PR to this issue, so I will leave the link here: https://github.com/abhinaba-ghosh/axe-playwright/pull/220

https://github.com/abhinaba-ghosh/axe-playwright/pull/220 This change has been merged. Closing this issue.


Broken icons for Copr/Koji builds in pipeline view

How to reproduce:

lower width of view than full HD; by slowly narrowing the view it is possible to see the shrinking in progress

Doesn't happen with regular icons (can be seen on SRPM status on the screenshot), suspected bug on upstream.
Example:

Probably could be fixed via min-width == width == max-width


Allow to process search results. Refs #75.

@emmenko please review

Will adapt to asSearch as extra method.

@emmenko please check again.

Add a test and squash your commits then before merging, thanks


Overhaul UI

(NOTE: Based on #31; the only changes are in search.html)

Update: separated the dataset-specific queries into a new tab


What about mibBuilder.loadTexts?

I'm wonder about how to use in the right way all that stuff in ModuleIdentity class as well as setStatus func while mibBuilder.loadTexts is False by default?
Should I set it to True manually?

This loadTexts is off by default to save on runtime memory. If you plan to use these SMI objects, you should remove all your previously compiled MIBs (~.pysnmp/mibs) and flip loadTexts to True. Once it's done, all subsequently compiled MIBs will have these objects in Python.
Alternatively, if you take the latest (not yet released) pysmi from master, with it you could come up with  a perhaps superimposed Jinja2 template for Python code generation that would include whatever SMI objects you want.


replace atob package to be compatible with web worker

Fixes #2260
Description
package atob does not work correctly in web worker environment, replace it with package atob-lite

Pull Request Test Coverage Report for Build 132846

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.359%

Totals

Change from base Build 132840:
0.0%

Covered Lines:
12700

Relevant Lines:
15092

💛  - Coveralls

hi, @Stevenic  can you help check this one, we need this to fix for composer's scenario, which move all parser into web worker that don't work with previous "atob" package.


Update flags for Table 1.3.14

currently flagged LGV all, but should be Non-Electric, I also looked to see if this would change with year as electric fleet size increases, and it doesn't implying initial assumption this is non-electric is correct

Fixed in linked commit - closing

Processing should run fine now but not tested, only conceivable thing I can think of that wouldn't work is difference in capitalisation. Currently looking to match against 'Non-Electric'


implement sampled functions based on the PDF spec (part 2)

@pdfjsbot test

@pdfjsbot makeref
Looks good tried a few corp report pdfs too.


Suppress the results of nc

#11 0.442 Detected: running on Linux.
#11 0.446 Connection to <IP_ADDRESS> 53 port [tcp/domain] succeeded!
#11 0.642 Connection to bitcoincore.org (<IP_ADDRESS>) 443 port [tcp/https] succeeded!
#11 0.643 Performing a system upgrade... ok.

From https://github.com/bitcoin-tools/nodebuilder/actions/runs/8227383300/job/22495207301?pr=382

Closing as duplicate of #385


[BEAM-14072] Revert "[BEAM-13993] [BEAM-10039] Import beam plugins before starting SdkHarness"

Reverts apache/beam#16998

Testing a revert to fund the culprit for following test suite breakages.
https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJavaSQL_Dataflow/
https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJavaSQL_Dataflow/

Run XVR_PythonUsingJava_Dataflow PostCommit

R: @rahuliyer95 @robertwb

Hi, Thanks for triaging this! Would it be possible for you to link the failed CI job run and Dataflow job logs from the failed run? I would like to see which plugin import is causing the failure and maybe we can make it work without having to revert the change completely.

Seems like build jogs do not contain Dataflow job IDs unfortunately: https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJava_Dataflow/144/consoleText
Lemme try running a separate x-lang job from HEAD.

I couldn't reproduce by running a single job but you should be able to reproduce by triggering the test suite.
https://issues.apache.org/jira/browse/BEAM-14072?focusedCommentId=17503837&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17503837
Could we proceed with the revert since this could result in other other critical bugs creeping into the repo ?

R: @tvalentyn
BTW one suspicion is that this might be broken for certain Python versions.
Both these test suites are run for multiple Python versions: https://github.com/apache/beam/blob/b07840e925b910fffee85d3bcdb67468965b7770/.test-infra/jenkins/PythonTestProperties.groovy#L37

LGTM.
s.apache.org/beam-python-dev-wiki has some pointers on running individual intergration tests that may be helpful

Thanks Valentyn. @rahuliyer95 I'll merge this to make the test suites green again but lemme know if you need help running x-lang tests. (also added some info to the Jira)


colab is not working on video

i am not a coder but its not working i guess can someone give me fix
this is showing
cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
frame=  242 fps= 42 q=2.0 Lsize=N/A time=00:00:07.36 bitrate=N/A speed=1.29x
video:47948kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
python demo/track.py video.source=demo_out/videos/images/breakdancing video.output_dir=demo_out/videos/phalp_out/breakdancing overwrite=False detect_shots=True video.extract_video=False render.enable=False
[05/13 07:43:11] INFO     No OpenGL_accelerate module loaded: No module

@rokonezoko55555555
Did you solve the problem ?

We are aware that there is an issue with video demo in the Colab notebook. Please try the video demo in a local or remote machine, and we will try to fix the issue with Colab.

Any updates on the video demo for Colab?


Establish a testing workflow, with unit tests and integration tests placed in the /tests folder for both backend and frontend. Ensure test scripts are functional and share consistent configurations across the monorepo.

Task Overview:
Create a comprehensive testing workflow that includes both unit tests and integration tests for the backend (Node.js) and frontend (Vite) applications. Tests should be placed in their respective /tests folders, and the testing configuration should be shared and consistent across the monorepo to ensure uniformity.

SMART Criteria
Specific 🎯:
Establish a consistent testing framework by:

Creating a /tests folder in both the /server and /client directories for backend and frontend tests.
Adding unit tests for isolated functionality testing, and integration tests for cross-module or feature-level validation.
Ensuring test scripts (e.g., test, test:unit, test:integration) are functional and use shared configurations (e.g., Jest, Mocha, or similar frameworks).

Measurable 📏:
Success will be measured by:

Both backend and frontend projects having at least 3 unit tests and 2 integration tests each.
Test scripts running consistently and passing across both backend and frontend with no configuration conflicts.
90% code coverage for critical components in both backend and frontend.

Achievable 🚀:
This task is achievable by leveraging testing frameworks like Jest or Mocha for unit and integration tests, along with shared configuration files that simplify setup for both projects.
Relevant 🎯:
Setting up a consistent testing workflow is critical to ensure the codebase's stability and quality, enabling both backend and frontend teams to catch issues early in development.
Time-bound ⏳:
This task should be completed in 1 week, giving time for setup, testing, and ensuring consistency across the monorepo.

Subtasks 📝

[ ] Create /tests folders in both /server and /client directories for test files.
[ ] Set up unit tests for both backend and frontend, ensuring coverage of key functionality.
[ ] Set up integration tests to validate interactions between different parts of the system.
[ ] Configure shared testing scripts (e.g., test, test:unit, test:integration) in the root package.json and respective package.json files for server and client.
[ ] Ensure that test frameworks (e.g., Jest, Mocha) are working consistently across the monorepo, with no configuration conflicts between projects.
[ ] Validate the workflow by running tests on both backend and frontend projects and ensuring successful execution with consistent test results.

Acceptance Criteria ✅

[ ] Both backend and frontend have at least 3 unit tests and 2 integration tests.
[ ] Test scripts run successfully across backend and frontend projects without configuration issues.
[ ] Code coverage reaches 90% for critical components, ensuring comprehensive test coverage.
[ ] Developers confirm that the testing workflow is easy to use and consistent across the monorepo.

Additional Notes 🗒
Ensure the test setup is scalable, allowing for easy addition of future tests and projects. Use code coverage reports to track test coverage over time.

@girl-loves-coding what tests should we write? :D there is like 6 packages. i think this need more info? or it has to be completed after other OKR's are completed given there is almost no code to test right now ^^

@girl-loves-coding what tests should we write? :D there is like 6 packages. i think this need more info? or it has to be completed after other OKR's are completed given there is almost no code to test right now ^^

agree, we should do it as the last task of OKR. Regarding the tests, I would just write a few basic tests to ensure the set up is correct.

done we will skip tests for now


Convert to typescript

Do we actually care to do this? If so, do we need to evaluate this vs. Flow vs any other options? Closing for now until someone has stronger feelings about leveraging static type-checking


Update Documentation

config.js moved to example/ (since Raneto is now NPM-installable)
The ./bin directory is no longer needed
Heroku deployment tutorial update, to show the new NPM usage of Raneto

I am not sure if the documentation needs an update or what but I cannot get heroku to work right following the directions.

Ok, updating now

@rdbrdd , Updated. Please let me know here if you have any more issues.
http://docs.raneto.com/tutorials/deploying-raneto-to-heroku

The new directions worked.  It seems like the issue was the inclusion of the "Procfile" that was causing it to fail for me.  Thank you.

Awesome, great to hear!
Yes, you're right. The Procfile had an outdated script in it that we forgot to update.
We'll look through the documentation and update it, and move most of the ReadMe contents to the Raneto docs to prevent split-brain from happening again.
Let us know how else we can be helpful

Sorry, I may miss some basics in node and npm usage but how am I supposed to make Raneto start from a directory other than example? Should I upgrade package.js file?
the example dir Is hardcoded in bin/raneto exectuable also.
I admit I am confused!

yes you should update package.json and change the lines 27 and 28 regarding to your needs.

The repo is currently confusing, so it's not something you're missing.
I'll dedicate time this weekend to cleaning things up and get it started back on track
In the meantime, you may find this repository helpful to deploy (Ubuntu v14.04 only, DigitalOcean recommended)
@stickgrinder @mohammadrafigh Please contact me directly in the meantime if you have pressing issues. Email address is in profile

Forgot the repo. here it is
https://github.com/ryanlelek/raneto-devops

Linking this to the megathread of Documentation updates and the Roadmap.
Please see above links.
Closing this issue.
Join us in the discussion on the Roadmap/Docs or re-open this issue with questions


Terrain, triplanar and forward rendering

The docs warn against this for performance reasons: https://alloy.rustltd.com/documentation/shader/terrain
However - for VR anything other than forward isn't really an option. Is there any way around this conundrum?

Not really, no. For our own VR project we've also been forced to use the forward renderer because we need MSAA. So when it comes to our splat-based shader materials we have been managing the cost by aggressively disabling the normal and packed maps .
Please note, this channel should be used for Alloy development questions. Usage questions should be directed to our Unity forums thread:
https://forum.unity.com/threads/alloy-physical-shader-framework-version-3-for-unity-5.305178/


Why not use enhancer API?

I noticed you're providing your own createStore function. Why not use export an enhancer instead? (Like Redux DevTools does.)

Thanks for your feedback! Released as 2.0.0!


Gitcoin bounty for enhancement of the JavaScript driver size by < 1MB

Hi there!
Thank you for dropping by. BigchainDB is open source project that has many moving parts. We try to allocate time to each issue and feature request but sometimes we run out of time or the problem is out of our maintainers expertise reach. To combat this problem we add bounties to issues / features. this is our way of saying Thanks for your contribution to our cause.
If you do not have any gas (Gwei) to pay transaction fee for work submission, we will be happy to send Gwei to you :)
We will try to help you help us getting this issue closed. But, if for some reason you would not be able to work on this bounty, please see our Gitcoin profile for our other open bounties. We would also encourage you to watch this repo as we are planning more upcoming bounties and we would love to have your contributions.
How can you help?
We are looking for some help to minimize the size of our javascript driver to < 1MB. We investigated the cause of size bloating for this driver and found that one of the dependencies crypto-conditions takes up quite some size. Bad thing is we only use a fraction of its code base. So, one of the optimisation strategy, we believe would be to somehow bundle only the used code. This may either be achieved by updating configurations in webpack 4 or feel free to be creative and propose alternate solutions. Our end goal is to optimise the size of the driver to less than 1 MB and you are free to use other means to optimise the size without breaking the build and tests.
What needs to be done?

Refactor code base to reduce the size of the driver to less than 1MB

We are very happy when -

[ ] size of driver package with refactored code results in passing all tests and size of package less than 1MB.
[ ] refactored code is merged into master branch in https://github.com/bigchaindb/js-bigchaindb-driver repo.

Seen this problem before ?
Any help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.
Questions & Reviews
Pull requests will be reviewed by one of maintainers or long term contributors. In case of any additional questions feel free to ask in this thread (preferred) or message me personally on Gitter (username - innoprenuer) and we will do our best to add the missing info :)

Thanks for accepting my proposal! I took a look at the builds and it seems like the actual source code compiles to around 600k. The extra bloat on top is the inline source map. My proposal is to eliminate the source mapping for vendor modules by altering the webpack config for the development environment. I aim to have a functional PR within the next several days.

Thank you, makes sense. If you would like sharing any progress update feel free to post here. Looking forward.

Apologies for the delay on that. This was my first time doing this type of configuration with Webpack 4 so it took me a good bit to get fully up to speed. I wound up configuring webpack to split out the vendor and main source files. From there I was able to exclude the compiled vendor asset from source mapping. A plugin ties it together by merging the vendor and main assets back into one file with inline source mapping for the first line (all of the non-vendor code) and nothing else.
Production still works the same way, providing a separate source map file for the combined vendor and non-vendor source code.

Thanks @dmvt for helping us with this. We would like to help us with other upcoming issues and bounties. It would be nice if you could join our gitter channels -
https://gitter.im/bigchaindb/bigchaindb
https://gitter.im/bigchaindb/js-bigchaindb-driver
We will be releasing bounty reward to you soon :)


Feature/pxweb2 213

Show scrolls when needed separatly on variablebox and table.

@KentMossback is this change still valid?

This has been implemented in another pr


[AutoRelease] t2-storagecache-2023-02-15-84525(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3790
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=842
BuildTargetingString
azure-mgmt-storagecache
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3790


feat(reform): support jsx v4

Moved here https://github.com/rescriptbr/reform/pull/249/commits/284ee39fbd4989a802139d8b7061ddf41514c69c thanks


pip install conversational-sentence-encoder error

pip install conversational-sentence-encoder
Collecting conversational-sentence-encoder
Could not find a version that satisfies the requirement conversational-sentence-encoder (from versions: )
No matching distribution found for conversational-sentence-encoder
Hi, do you know how to solve the above issue? I actually successfully installed the package before, however, today, there is the above mentioned error.
Thanks in advance!

Hello @lytum,
Thank you for reporting! Recently I noticed that some dependencies of conversational-sentence-encoder are not compatible with the latest python versions. Since the stability of this package is tested for python 3.6 only (works perfectly in google colab), I limited the options to python 3.6.* when installing via pip.
Please let me know if it works fine in python 3.6. Also, if you are willing to do some testing, please try to install the package from source code for your current python distribution and let me know your python version if it works, so that I will include it to supported python versions of the package.

In my another project, I installed this library with Python 3.7.6 previously, now it works well.
Could you include python3.7.6 to the supported python version?
Thanks a lot!

Good to know!
I did some tests and found that it is possible to install the package with python versions up to 3.7.10, so I will include this version. Unfortunately, the package will not support python>=3.8, since python 3.8 support requires TensorFlow 2.2 or later, but the package requires TensorFlow 1.14.


Breaks when used with ionic tabs template

First, thanks for creating this awesome project!
I got an error after upgrading to the latest version, after some investigation it seem to break when used in a project which uses the standard ionic tabs on the root page.
Any super-tabs version on a clean root page without ionic tabs
-> Works
super-tabs <= v 2.1.0 on a root page with ionic tabs
-> Works
super-tabs >= 2.2.0 on a root page with ionic tabs
-> Throws error below
content.js:799` Uncaught TypeError: this._tabs.setTabbarPosition is not a function
   at Content._writeDimensions (content.js:799)
    at content.js:214
    at SafeSubscriber.schedulerFn [as _next] (core.es5.js:3840)
    at SafeSubscriber.__tryOrUnsub (Subscriber.js:236)
    at SafeSubscriber.next (Subscriber.js:185)
    at Subscriber._next (Subscriber.js:125)
    at Subscriber.next (Subscriber.js:89)
    at EventEmitter.Subject.next (Subject.js:55)
    at EventEmitter.emit (core.es5.js:3814)
    at Array.<anonymous> (page-transition.js:34)
    at IOSTransition.Animation._fireBeforeWriteFunc (animation.js:838)
    at IOSTransition.Animation._beforeAnimation (animation.js:749)
    at IOSTransition.Animation._playDomInspect (animation.js:411)

Here is a repo to reproduce the error
repo

ionic2-starter-tabs template
Added supertabs on homepage with the contact page & about page as tabs pages
Currently on supertabs 2.2.0 and throws error
Downgrade to 2.1.0 and it works

Hey there,
Can you please upgrade to<EMAIL_ADDRESS>and let me know if this issue has been solved?

Works! Thanks for fixing this so quick!
I noticed another problem with the content area, will create another issue with a description.


support PATCH in crdclient

Part of this is already in #27761 tested and working. For now, only supporting regular RFC 6902 json patch, not strategic merge or any of the other k8s patch types.
As far as the auto-registration code is concerned, this simple patch helps a lot to avoid conflicts when writers have completely separate concerns.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
1dc819e60bef6052e791c7c988cc39a37e797169
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
1dc819e60bef6052e791c7c988cc39a37e797169
link
/test gencheck_istio

lint_istio
1dc819e60bef6052e791c7c988cc39a37e797169
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Context please ? Who'll use the patch method ?
My concern is on maintaining support for non-k8s environments - is this something that can be supported ?

rest LGTM

@costinm This will be useful for VM auto-registration and health-checking. We probably don't want a lot of things trying to PUT WorkloadEntry just to update unrelated fields.
As far as supporting non-k8s.. I'm not sure how we would be able to write to other places. Write's outside of k8s and in-memory just return "not supported" errors. This would be a good goal down the line, but if we want to utilize features like managed fields it will be hard to expose this in a generic way.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ba6e65d825712a14212114f6dca28dfe13967323
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

health-checking

This will use status, can status be PATCHed? Seems like no based on https://github.com/kubernetes/kubernetes/issues/67455.
What are we patching for auto registration? Should it also be in status?

this simple patch helps a lot to avoid conflicts when writers have completely separate concerns.

What are we trying to avoid here? Two istiod's conflict? Istiod and human? istiod and some other tool?
It seems like we would only have one istiod instance touching a given workload entry. Maybe in some edge cases we would have a few conflicts, but it seems like an edge case not a common one - is that accurate?
BTW - https://godoc.org/k8s.io/client-go/util/retry#RetryOnConflict is useful.

It seems like we would only have one istiod instance touching a given workload entry.

In auto-registration, if we have a disconnect/reconnect scenario, they'll both be setting "controller name" and "(dis)connect timestamp". In the testing I've done so far this happens often whether it's the same istiod or the proxy switches istiod.
I'd imagine we'll have even more contention if health checking is enabled.

I think we should be able to patch status.. it has to be treated as a separate resource though and not a part of the main resource.

Yeah one concern I would have with status is that I think it's a list of conditions (matches how all of almost all native types work, as far as I know? or I'd at least now recommended practice). I would guess this essentially makes patching impossible (?). We should probably see what k8s does here, I'd they just have retry loops for conflicts or patch or something else

Granted the two fields for registration are not in the conditions list (not sure if that's recommended or not, need to check the latest k8s recommendation since they updated a couple months ago) so that concern may not apply here

question.. if using managed fields, is patch necessary?

@rshriram yes, you have to use a specific patch type to get the benefits. Update will just overwrite

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ba6e65d825712a14212114f6dca28dfe13967323
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ba6e65d825712a14212114f6dca28dfe13967323
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Windows fails with version 0.46 / 4.3

We reached the number of public methods that the Windows linker can consume.
We were very close to the limit, but now we no longer can do very much about it.
In the short term, a band aid would be to not generate code for a handful of rarely used classes (things like XR), just to get the Windows build going again.
A better version would be to rationally split SwiftGodot in multiple libraries, in themes.
Now, to keep our lookupObject working as-is and not require registration, we could keep all the class definitions in SwiftGodot, but the actual methods would be provided as extensions on the new libraries.
So "Window" might be defined in SwiftGodot, but the methods would be in "SwiftGodot.Windows".

Ok, I deployed a band aid for now.   Compile SwiftGodot and the extension as static libraries.
But we should still find a way of splitting SwiftGodot in chunks.


fix(ci): fix a typo in rustup update

This looks like a possible typo; it was introduced in #297. Fixes a parse error I ran into when cargo initing from a fresh repo using this prerelease version.

!#$%? i swear i fixed this in #336 but it vanished


Add face detection

Whops, didn't mean to open a PR to the main repo. My mistake :-)

The code is working though, could use a clean up. Let me know if interested.


SVG Image Upload to Stored Cross-site scripting

Issue Summary
Ghost platform is vulnerable to Stored Cross-site scripting via SVG file uploads.
Scalable Vector Graphics (SVG) can be used to define vector-based graphics within a webpage. SVG can be mixed with HTML content, as well as XML namespaces. SVG can be used to create interactivity within a webpage and perform animations.
It should be noted that even though the MIME type for an SVG image is image/svg+xml. It is possible to store JavaScript code within an SVG document and execute it if viewed directly within a web browser. An example proof on concept for this can be seen below
<svg version="1.1" baseProfile="full" xmlns="http://www.w3.org/2000/svg">
    <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red" />
   <script type="text/javascript">
      alert(document.domain);
      alert(document.location);
   </script>
</svg>

To Reproduce

Create a new post within you Ghost blog
Instead of uploading a jpeg file, upload the above SVG document as a .svg file and then publish the new post
Once published, go to your post and copy the image location of rendered SVG file

Cross Site Scripting (XSS) allows clients to inject arbitrary scripting code into aapplication and have the server return the script to the client in the response. This occurs because the application is taking untrusted data (in this example, as form of a SVG file) and storing it without performing any validation or encoding.

This isn't the correct method to report security vulnerabilities. Please take a look at the security documentation

If you can, please edit the issue to hide the vulnerability, and remove the edit Github stores

thanks for this issue i know the vuln 👍 haha


Fix typo (spreadsheet => stylesheet)

Fixes obvious typos.

i was just about to make this PR after being briefly confused while reading the docs on the new react-dom <style> element API. this is perfect and should be merged ✅!


Uncaught SyntaxError: Identifier 'Buffer' has already been declared

I'm having an issue when using this lib. It complains about the Buffer class. Can this be named something else?

fixed in latest version. note than bp_statemachine should be updated


Custom select

We don't want to use native select inside entity editor. We want to use custom dropdown like we do with multi-select input.

Codecov Report

Merging #636 into metadata-editor will decrease coverage by 0.05%.
The diff coverage is 0%.

@@                 Coverage Diff                 @@
##           metadata-editor     #636      +/-   ##
===================================================
- Coverage            52.94%   52.88%   -0.06%
===================================================
  Files                  258      258
  Lines                 7106     7114       +8
===================================================
  Hits                  3762     3762
- Misses                3344     3352       +8

Impacted Files
Coverage Δ

src/article/metadata/SelectInput.js
0% <0%> (ø)
: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 13c0a30...7afd232. Read the comment docs.


ADDED SCROLL BAR AND DARK-LIGHT THEME SWITCH

Hello @GarimaSingh0109
As you requested, I have implemented the switch using the specified colors. I've also added the scroll bar functionality at the top of the navigation bar. Please take a look!

@STDYGIT resolve the conflict

dii

Mam Conflicts got resolved you can pull the code now


added dock command that starts docker containers only without services

Coverage decreased (-0.5%) to 20.054% when pulling 3557f23d5e9cc7867ef967953ef8fa8bf082a76c on new-cmd-dock into 8ec485bb04644e92c320fe5a92df7529af804a39 on master.


Fixed #29

Adds Grid Component with same usage API as https://github.com/GeekyAnts/react-native-easy-grid

left a few minor styling comments. Will try the grid layout soon and implement it in the hackathon-starter project as a demo.
Also @binoy14, could you kindly change the base branch as v0.9.0. Thanks.

@binoy14 there is an outstanding PR on the react-native-easy-grid repo that I think would be a great addition. Check this out: https://github.com/GeekyAnts/react-native-easy-grid/pull/21
What are your thoughts on adding the onPress feature to this PR?

@Monte9 What's the advantage/purpose of adding an onPress? I don't mind adding it, just trying to understand how will it be useful.

@binoy14 Although the onPress does not directly improve the functionality of the grid layout itself, I think having it will give the user some flexibility in case they need to use it. One use case I can think of is.. Using flex to position an image but then having to wrap it in a TouchableHighlight to make it clickable. In this case, if I am using the grid layout, I don't have to wrap the image and I can directly use the onPress of the Col/Row. Does that make sense?
Also I just tried the Grid layout from this PR and I really like it. Good job!

@Monte9 I added onPress event for all three elements.
I have set default activeOpacity to 1. It made sense to have default of one and give option to change it by the consumer. If you would like me to change that let me know.

@binoy14 @Monte9 is this PR ready to merge?

@dabit3 from my side yes


Wrong start page on self hosted version

The README.md says the site can be reached on http://localhost:7331/web/ but when i access i got a 404.
After browsing the site developer.google.com I just noticed the fundamentals area is under web/fundamentals so i changed the url to http://localhost:7331/web/fundamentals and it worked.
I think the README.md should be updated to avoid headaches.

Just added a pull request to solve the issue
https://github.com/google/WebFundamentals/pull/3288