[Bug]: Eufy Floodlight 2 pro stream

What happened?
I have a problem with my eufy floodlight pro 2. it is clearly visible in homekit but the stream does not start and after waiting 10s I get a message telling me that the camera cannot be reached. Also changing state doesn't work.
Device Type
Floodlight (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[10/17/2022, 5:24:28 PM] [EufySecurity-2.1.0] INFO:  Arrière-cour is set to handle snapshots with cloud images. Snapshots might be older than they appear.
[10/17/2022, 5:24:28 PM] [EufySecurity-2.1.0] INFO:  Adding new accessory: Arrière-cour
[10/17/2022, 5:25:00 PM] [EufySecurity-2.1.0] INFO:  Looking for old cached accessories that seem to be outdated...
[10/17/2022, 5:25:00 PM] [EufySecurity-2.1.0] INFO:  Removing cached accessory 110b3678-4445-44de-a988-f7a232fa523c Garage
[10/17/2022, 5:25:00 PM] [EufySecurity-2.1.0] INFO:  Removed 1 cached accessories
[10/17/2022, 5:25:06 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour Local livestream didn't start in time. Abort livestream request.
[10/17/2022, 5:25:06 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour Unable to start the livestream: no started livestream found
[10/17/2022, 5:36:11 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour handleSecuritySystemCurrentStateGet Wrong return value
[10/17/2022, 5:36:11 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour handleSecuritySystemTargetStateGet Wrong return value
[10/17/2022, 5:36:15 PM] [EufySecurity-2.1.0] WARN:  Push Closed!
[10/17/2022, 5:36:15 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour handleSecuritySystemCurrentStateGet Wrong return value
[10/17/2022, 5:36:15 PM] [EufySecurity-2.1.0] ERROR: Arrière-cour handleSecuritySystemTargetStateGet Wrong return value

config
{
    "platform": "EufySecurity",
    "ignoreStations": [
        "T8030P232233084D",
        "T8423N1022120701"
    ],
    "ignoreDevices": [
        "T8114P0121091290",
        "T8210P0020260D61",
        "T8410P2020284928"
    ],
    "cleanCache": true,
    "username": "",
    "password": "",
    "country": "FR",
    "stations": [
        {
            "serialNumber": "T8030P232233084D",
            "manualTriggerModes": [
                0,
                1,
                2,
                3
            ]
        },
        {
            "serialNumber": "T8410P2020284928",
            "manualTriggerModes": [
                0,
                1,
                2,
                3
            ]
        },
        {
            "serialNumber": "T8423N1022120701",
            "manualTriggerModes": [
                0,
                3,
                2,
                1
            ]
        }
    ],
    "cameras": [
        {
            "serialNumber": "T8114P0121091290",
            "enableCamera": "true",
            "videoConfig": {
                "audio": true,
                "audioSampleRate": 0
            },
            "talkback": true
        },
        {
            "serialNumber": "T8423N1022120701",
            "enableCamera": "true",
            "videoConfig": {
                "audio": true,
                "audioSampleRate": 0
            },
            "talkback": false,
            "useCachedLocalLivestream": false
        },
        {
            "serialNumber": "T8210P0020260D61",
            "rtsp": false,
            "enableCamera": true,
            "videoConfig": {
                "audio": true,
                "audioSampleRate": 0
            },
            "talkback": true
        },
        {
            "serialNumber": "T8410P2020284928",
            "enableCamera": "true",
            "videoConfig": {
                "audio": true,
                "audioSampleRate": 0
            },
            "talkback": true
        }
    ],
    "CameraMaxLivestreamDuration": 120
}

I saw, that in your json config the same serial numbers are under "ignored stations" and configured below. Maybe thats the problem?

I saw, that in your json config the same serial numbers are listed under "ignored stations" and even configured below. Maybe thats the problem?

Hello,
Even turning them on doesn't work.

Is this still an issue?

@schliemann with the last beta no, but with the curent version yes.


Prevent cycle sending

Stop sending activation message to QueueManager itself again but recover MemoryQueue instead when cycle happens
Description

Related issue and scope

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

My changes affect the following components

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

Types of changes

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

Checklist:

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

I have an issue where the namespaceContainer metric still emits containers for a namespace even after no activations are being run in a long time for that namespace. The value just remains constant forever until I restart the scheduler in which it then correctly goes to 0 not emit for that namespace. My thought was something getting stuck in memory with the memory queue even after it should have been shut down since the metric is reported from that actor. And it's weird that it would still report that there are containers even if there are none in etcd for the namespace even if the memory queue wasn't properly shut down as I assume it would get updated with the correct value when still emitting unless it's stuck in a zombie state or something. Do you think this could be the same issue?

Codecov Report

Merging #5251 (b5f7aaf) into master (1a6c99d) will decrease coverage by 7.44%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #5251      +/-   ##
==========================================
- Coverage   70.59%   63.14%   -7.45%
==========================================
  Files         238      238
  Lines       14009    14047      +38
  Branches      567      569       +2
==========================================
- Hits         9889     8870    -1019
- Misses       4120     5177    +1057

Impacted Files
Coverage Δ

...in/scala/org/apache/openwhisk/common/Logging.scala
68.58% <0.00%> (-10.09%)
:arrow_down:

.../openwhisk/core/scheduler/queue/QueueManager.scala
7.05% <0.00%> (-0.95%)
:arrow_down:

...che/openwhisk/core/invoker/LogStoreCollector.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/RxObservableImplicits.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedConsumer.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0.00% <0.00%> (-95.85%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0.00% <0.00%> (-93.90%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0.00% <0.00%> (-92.31%)
:arrow_down:

...a/org/apache/openwhisk/http/BasicHttpService.scala
3.17% <0.00%> (-87.31%)
:arrow_down:

... and 42 more

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 1a6c99d...b5f7aaf. Read the comment docs.

LGTM


The nice Fibonacci series

A nice Fibonacci series written in C++, with a bit of madness

You can follow me on github


Flutter doesn't detect existing Gradle dist

Flutter doesn't use existing Gradle distribution that we use on our development machines. We use Gradle-4.6 as our standard. As soon as we do a flutter run, flutter tries to download a new version of Gradle.
Meta

Flutter version: 1.2.1

The initial title of the issue, was wrong due to an issue with our application which we use for GitHub

Hi, just want to check if this is still a problem for you.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Python3 support.

Hello,
Is there any plan of expediting this PR? I am migrating some projects  to python 3 under a tight schedule and this would could be my only hope. The work could easily miss a very critical deadline if I moved  to the official django UUIDField.


Switch method to POST rather than GET

I wasn't sure where to open this issue, it doesn't directly concern the SDK but the overall implementation of JustAuthMe.
Using GET parameters is less secure than using POST method.
A simple example: parameters are displayed in access logs...
Having the possibility to choose the method used would be a plus, I think...
And make POST as default, like ReCaptcha use it.

Hi,
There is the "docs" repo for thid kind of issue, but you can open it here as well, we will see it anyway :)
POST over GET isn't semantically correct, as the API request does not post or create anything on the server-side, it is a proper get of an already crafted response.
But you made a point on access logs, we will consider updating the API to accept secrets via request headers.

Sorry about that...
Do you want I open repost the issue on the doc repository?
I've got a potential other security point that could be tricky.
I'm opening a way out on the right project this time !

No, here is fine :)
The callback URL in the SDK is usefull in order to, in the future, allow multiple callback URLs. If the security point that concerns you is the spoofing of the callback URL, no worries, we won't redirect the user to an unknown callback.


Load PairRM ranker without Internet access failed

Hi, and thank you for your outstanding work!
I recently attempted to execute the PairRM project on a development machine without internet access. Despite pre-downloading the hf model to a local directory, I encountered an issue during the load_ranker process where the model still attempts to download microsoft/deberta-v3-large. Could you please advise on how to bypass this automatic download? Or is it necessary for me to also download this specific model locally?
Thank you for your assistance!

Hi Kai!
Thanks for the question! @jdf-prog  and I will look into this and see if we can make it an option when loading the model.
For now, maybe it is possible to manually change the source code here
This huggingface doc may be useful: https://huggingface.co/docs/huggingface_hub/guides/download#download-files-to-local-folder
Thanks!

Hi @kai01ai , I have updated the llm-blender codebase and modify the downloading strategies. Now loading pairrm with first check if the local dir checkpoints exists, and will only try downloading if that folder does not exist. I think now you can work with PairRM withour internet access well by downloading the checkpoint in advance!
Thanks for the issue!

Hi @jdf-prog thx for the quickly fix.
After updated the codebase, load_ranker still meet the following error
OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like microsoft/deberta-v3-large is not the path to a directory containing a file named config.json.

I found the microsoft/deberta-v3-large is the model_name which defined in ranker_config.json

It worked after setting model_name in ranker_config.json to local deberta-v3-large model path


Update ThriftScanner to use nanotime

Update ThriftScanner to use nano time to be consistent with elapsed time tracking in other locations. Also, convert timeOut to be a Duration to prevent future errors. This value was being converted to seconds from millis which is error prone as there was not a good indication the unit was in seconds.
This is a follow on to #4864
As a side note, there are plenty of other timeout related properties that are part of the scanner code. I started to convert those as well to Duration but it cascaded and started touching a lot of classes which i didn't think was a good idea for 2.1. However, I was thinking as part of 3.1 and 4.0 we may want to update some more fields in classes from a long to a Duration (assuming no performance concerns). Here are some examples I found but I am sure there are more spots:
TimeoutTabletLocator (in 3.1 only)
ScannerOptions
TabletServerBatchReaderIterator
ScanState in ThriftScanner

The MiniAccumulo tests were hanging on this and I took a look at logs and found the following:
2024-09-12T10:20:28,962 [threads.AccumuloUncaughtExceptionHandler] ERROR: Caught an Exception in Thread[accumulo.pool
.metadata.tablet.assignment-Worker-10,5,main]. Thread is dead.
java.lang.RuntimeException: java.lang.ArithmeticException: long overflow
        at org.apache.accumulo.tserver.AssignmentHandler.run(AssignmentHandler.java:142) ~[accumulo-tserver-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]
        at org.apache.accumulo.tserver.ActiveAssignmentRunnable.run(ActiveAssignmentRunnable.java:63) ~[accumulo-tserver-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]
        at org.apache.accumulo.core.trace.TraceWrappedRunnable.run(TraceWrappedRunnable.java:52) ~[accumulo-core-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
        at org.apache.accumulo.core.trace.TraceWrappedRunnable.run(TraceWrappedRunnable.java:52) ~[accumulo-core-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]
        at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.lang.ArithmeticException: long overflow
        at java.base/java.lang.Math.multiplyExact(Math.java:1004) ~[?:?]
        at java.base/java.time.Duration.toNanos(Duration.java:1250) ~[?:?]
        at org.apache.accumulo.core.util.Timer.hasElapsed(Timer.java:62) ~[accumulo-core-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]
        at org.apache.accumulo.core.clientImpl.ThriftScanner.scan(ThriftScanner.java:344) ~[accumulo-core-2.1.4-SNAPSHOT.jar:2.1.4-SNAPSHOT]


validated vnsLDevCtx with context=""

Validation Type
[x] - Config
The empty context for vnsLDevCtx  are not supported and can cause unexpected forwarding issues.
What needs to be validated
if vnsLDevCtx.context=="", raise the alert before upgrading.
Why it needs to be validated
To prevent svg outage post upgrade
Additional context
Add any other context about the feature request here.

https://github.com/datacenter/ACI-Pre-Upgrade-Validation-Script/tree/welkin-issue-78

Would you mind sharing a little bit more details on this? For instance whether this is specific to upgrade, a bug, etc.

@welkin-he any more detail/bug you can provide for this specific check?

No further details shared, closing this one out


Fix the local integration test docker-compose file

What changed?
Moved updates to the docker-compose file used in the CI to the local
docker-compose.

Why?
This enables us to run the integration tests locally in docker

How did you test it?
Local tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018df3b0-7004-4cc1-9aee-181011e7265f
Details

0 of 0   changed or added relevant lines in 0 files are covered.
44 unchanged lines in 9 files lost coverage.
Overall coverage decreased (-0.009%) to 62.892%

Files with Coverage Reduction
New Missed Lines
%

common/task/fifo_task_scheduler.go
2
87.63%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

common/util.go
2
91.69%

service/matching/taskReader.go
2
84.88%

common/persistence/statsComputer.go
3
93.57%

service/matching/taskListManager.go
3
80.71%

tools/cli/admin_db_decode_thrift.go
3
68.83%

service/history/execution/mutable_state_task_refresher.go
7
67.09%

common/persistence/sql/workflowStateMaps.go
20
81.25%

Totals

Change from base Build 018df01c-3fd6-4c29-b1b5-1dbf8f49a043:
-0.009%

Covered Lines:
92958

Relevant Lines:
147805

💛  - Coveralls


fabric-ccenv-sgx image creating fails

make prep fails when applying patches.
patching file /tmp/linux-sgx/linux/installer/common/psw/install.sh
patching file /tmp/linux-sgx/linux/installer/bin/install-sgx-psw.bin.tmpl
Hunk #1 FAILED at 30.

Quick fix would be to pin commit 08c2457.

Longterm solution: We create and maintain our own dockerfile and thereby reduce the dependency.


Fix storage sample notebook, and a few regressions that crept in from

merge conflicts when merging federated table support.

LGTM


Wish

The wish meteor animation is failed to load why plss help

If you are in the iOS ecosystem, some functions may not work properly. I'm still working on finding a solution to this problem.

Ok tysm its really making me a lil upset cuz idk if its a 5 star or 4 star so thank youu

And yes im on ios

By the way do you have another wish simulator website? That i can play on that has a wish or any other wish simulator while waiting for the meteor fix

Have you tried this https://gi-wish-simulator.uzairashraf.dev/ ?
I don't know much about other simulator sites, but I think there are already many similar apps that you can find if you search for them.

Thank you

Hello are u trying to fix it cuz its really bugging me

Hi when do you think this will get fixed:/

Sorry, I still have no clue.
But, can you tell me about your experience while pulling from these sites?

https://gi-wish-simulator.uzairashraf.dev/
https://primoprod.vercel.app/
https://bluestixs.github.io/WishSim/
https://genshin-wish-simulator-khaki.vercel.app/

Do the meteor animations show up or not?
I'll try to use the same code from the site that works well.

I think you should use the primoprod one its a lil better

I have played them but its so lagyy

Can You Fix It Almost?!

I've made a small change. How does it look now?

Sorry Still Not Working.

Is this alert still appearing, or are you experiencing a different issue?

Yes!

Thats Exactly Whats Happening

Okay.. I'm still trying..
I've tested this on BrowserStack and LambdaTest, and it seems to be working now. However, I still don't know about the real experience since I don't have access to an iOS device.
Sorry, I hope you can be patient with this problem.

ITS FIXED!

THANK YOU!

Oh, really?
Well, in that case, I think I can close this issue. Thank you for your patience all this time.


Build #104 broken

Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: module 'matplotlib.font_manager' has no attribute '_rebuild'
Error: Process completed with exit code 1.

Fixed in 6bd5a2644fe2a97a8c695cf02093a8d6e369615f


Support for Stoch Wt Avg (SWA) closes #321

Stochastic Weight Averaging (SWA) is (quoting/paraphrasing from their page):

a simple procedure that improves generalization in deep learning over Stochastic Gradient Descent (SGD) at no additional cost, and can be used as a drop-in replacement for any other optimizer in PyTorch. SWA has a wide range of applications and features, [...] including [...] improve the stability of training as well as the final average rewards of policy-gradient methods in deep reinforcement learning.

See the PyTorch SWA page for more.
Description

Relatively simple change in exp_manager.py. It allows an additional key "swa" to be included in policy_kwargs, e.g.
hyperparams["policy_kwargs"]["swa"] = {
   "swa_start": 5,
   "swa_freq: 3,
   "swa_lr": 0.05
}

Motivation and Context

SWA might help improve stability and reduce sensitivity to random seeds in some DRL applications.

Closes #321

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

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (update in the documentation)

Checklist:

[x] I've read the CONTRIBUTION guide (required)
[ ] I have updated the changelog accordingly (required).
[x] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.
[ ] I have reformatted the code using make format (required)
[ ] I have checked the codestyle using make check-codestyle and make lint (required)
[ ] I have ensured make pytest and make type both pass. (required)

Note: we are using a maximum length of 127 characters per line

I realized we need to do opt.swap_swa_sgd() at the end of training, and some further thought is needed, to see how this impacts computation of validation metrics  by EvalCallback etc

I added opt.swap_swa_sgd() after model.learn.
We also need to do this before and after each evaluate_policy() call in EvalCallback (which is in the original sb3 repo), so that validation metrics are evaluated with the SWA-averaged model weights. We could potentially subclass EvalCallback to accomplish this.


Add/done tasks from widget itself

Could you please add the "Add" button which simulates add a button for adding new tasks( if it's was possible to do from a message box, not from opening the app, could be much better) and a "Done" button for tasks?

Unfortunately, RemoteViews do not support CheckBoxes but I will find a way to enable this feature in the widgets.

Unfortunately, RemoteViews do not support CheckBoxes but I will find a way to enable this feature in the widgets.

:)


Update azure_regulatory_compliance_report.pt

Changed the ignore_status to 404 (was previously a typo with 400).
Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          2 Errors

:no_entry_sign:
Please add a CHANGELOG.md file

:no_entry_sign:
Please add labels to this Pull Request

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger

          2 Errors

:no_entry_sign:
Please add a CHANGELOG.md file

:no_entry_sign:
Please add labels to this Pull Request

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


fixed label in config_flow and new service Draw Custom Image

Fixed label for ip in config_flow by adding translation for DE and EN
added new service draw custom image

Thank you for your contribution


Seek for Audio

Implementing seek in the much simpler case of audio. Need to do more testing to make sure this behaves appropriately, but putting the PR up now under WIP status since this has the main idea implemented.
Uses the chunk metadata to create a dummy iterator of the same shape as the true iterator and keeps track of the shard id and the row index reached during the resume process. Then, initializes the actual iterator from the location reached during the dummy iteration.

this is obviated by the big cache changes i made


Add Travis secrets for snapshot deployment.

Closes #5.

Bonus: we get to see if the hackjob of a .travis.yml I made works...

LGTM, assuming Travis is happy.

One build timed out installing the test APK. Is there a "kill me" emoji?

:hocho: :scream:


[18.0.0-proposed] Bump lib-common due to antiaffinity weight change

https://github.com/openstack-k8s-operators/lib-common/pull/543
Related: https://issues.redhat.com/browse/OSPRH-8870

/retest

/test manila-operator-build-deploy-kuttl


Update manifest file

As @fekad pointed out we include docs and tests directory in our wheel file. This should not be the case.
This PR updates the MANIFEST.in file to explicitly include only the correct folder and files.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage remained the same at 77.768%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/dataconverter/convert.py
1
74.86%

pynxtools/nexus/nxdl_utils.py
2
73.07%

pynxtools/dataconverter/helpers.py
2
90.68%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2599

Relevant Lines:
3342

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage remained the same at 77.768%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/dataconverter/convert.py
1
74.86%

pynxtools/nexus/nxdl_utils.py
2
73.07%

pynxtools/dataconverter/helpers.py
2
90.68%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2599

Relevant Lines:
3342

💛  - Coveralls


add sha256sum of image as a label

This will allow us to short circuit the CircleCI workflow by immediately checking if the image needs to be rebuilt and bailing out (halting) if not.
Look up sha256sum of flavor in index.json, compare to label on remote image, halt if matching.

IIRC this is an un-recoverable chicken/egg scenario.
We cannot know the image sha until the image is fully built, once we know the image sha, if we add that as a label to the image, the image sha will change as a result.

Sorry @usrbinkat I didn't make this clear enough. I want to short circuit based on the sha256sum of the qcow2 disk image. I spent some time thinking about this morning and I have yet to figure out a way to stick a unique label on the image(s) (in the case arm64 and amd64 will have different sums).

Ah, we can create a ${QCOW2_FILE}.sha256 file here and then add the shasum file path to persist_to_workspace here.
From there we can read in the sum and create a label for each child qcow2 arch image.

closing this issue, I'm taking a different approach to halt the jobs.


Clean dependencies

Closes #60
CI coverage will decrease a little, but it is unavoidable (as some heavy packages were loaded for just one or two tests)

It shouldn't be the case.


[BUG] Unable to extends Card component

The code
import React from 'react';
import PropTypes from 'prop-types';
import styled, { css } from 'react-emotion';
import { Button, Card, CardHeader, Heading, Text } from 'circuit-ui';

const ThankYouContainer = styled(Card)`
  ${() => css`
    background-image: url('https://static.sumup.com/assets/images/dashboard/package.jpg');
    background-repeat: no-repeat;
    background-size: 100% auto;
    height: 350px;
    width: 75%;
    margin: auto;
  `};
`;

function GuestThankyou({ ...props }) {
  return (
    <ThankYouContainer>
      <CardHeader>Thank you</CardHeader>
      dasdasd
    </ThankYouContainer>
  );
}
export default GuestThankyou;

The error:
1282:42 Uncaught TypeError: shadowOptions[shadow] is not a function
    at shadowStyles (1282:42)
    at Styled.handleInterpolation (981:283)
    at Styled.eval (981:355)
    at Array.forEach (<anonymous>)
    at Styled.createStyles (981:354)
    at Styled.css (981:392)
    at Styled._render [as render] (986:158)
    at finishClassComponent (792:8377)
    at updateClassComponent (792:8345)
    at beginWork (792:8966)
shadowStyles @ 1282:42
handleInterpolation @ 981:283
(anonymous) @ 981:355
createStyles @ 981:354
css @ 981:392
...
792:9627 The above error occurred in the <ThankYouContainer> component:
    in ThankYouContainer (created by GuestThankyou)
    in GuestThankyou (created by TemporaryGuestShop)
    in TemporaryGuestShop
    in Unknown (created by pure(Component))
    in pure(Component) (created by getContext(pure(Component)))
    in getContext(pure(Component)) (created by getContext(getContext(pure(Component))))
    in getContext(getContext(pure(Component)))
    in div
    in Unknown
    in Unknown (created by I18nEnhancedComponent)
    in I18nEnhancedComponent
    in div (created by ModalProvider)
    in ModalProvider
    in ScrollSpyProvider
    in I18nextProvider
    in ThemeProvider
...

The possible problematic line:
https://github.com/sumup/circuit-ui/blob/c6b262ae1a7b1c86ae074a12179203628c509a9c/src/components/Card/Card.js#L32

This happens because the current version of emotion does not forward the defaultProps to the styled custom component. The shadow prop ends up being undefined, leading to this error.
Upgrading emotion in Circuit UI should solve this issue.

A workaround, for now, is to explicitly set the shadow property.
function GuestThankyou({ ...props }) {
  return (
    <ThankYouContainer>
      <CardHeader shadow={Card.SINGLE}>Thank you</CardHeader>
      dasdasd
    </ThankYouContainer>
  );
}

This is fixed in emotion v.9.2.0+. Circuit UI uses v9.2.6, so this should bug should be resolved.


add a new menu based CLI test tools - tpmtest

Jimmy, can you please rebase this to the latest on master?

Done.


Percy anywhere doesn't seem to work with RSpec

When using bundle exec rspec as in the readme, Percy runs just fine w/o errors, but doesn't upload anything. Removing rspec fixes it. Example, see https://github.com/joscha/example-percy-react-storybook
references https://github.com/joscha/example-percy-react-storybook/issues/2

Whoops that's supposed to be bundle exec ruby snapshots.rb — fixing now.

@fotinakis This would only "fix" this example of using percy anywhere though (by not using rspec) - the issue still remains, Percy Anywhere and RSpec don't seem to work together - if you check out  https://github.com/joscha/example-percy-react-storybook/ you can see it failing.


Looks like "setLeftAccessoryView" works only after notification is shown

Hello again!
I'm trying to get rid of left accessory view (i.e. setLeftAccessoryView to nil). I'm doing that before I show notification, but it works only on touch block.
            self.notification.setLeftAccessoryView(nil, animated: false)
        })
        view.addSubview(notification)
        notification.show()```

^^^ this works and left accessory view is removed upon touching the notification

notification = JFMinimalNotification(style: .StyleInfo, title: "Som etit;e'", subTitle: "Subtitle", dismissalDelay: 5.0, touchHandler: { () -> Void in
        })
        view.addSubview(notification)
        self.notification.setLeftAccessoryView(nil, animated: false)
        notification.show()

^^^ this doesn't work :( left accessory is still there.

Hey!
I've not tested this but give this a try...
self.notification = JFMinimalNotification(style: .StyleInfo, title: "Som title'", subTitle: "Subtitle", dismissalDelay: 5.0, touchHandler: { () -> Void in
})
view.addSubview(notification)
self.notification.setLeftAccessoryView(nil, animated: false)
self.notification.layoutIfNeeded() // <- adding this. Again, I'm not sure if this will fix it or not but give it a shot and let me know
notification.show()

Didn't work :(

OK, gonna have to create a new swift project and try it out myself. give me a bit and I'll get back to you.

Looks like
- (void)setStyle:(JFMinimalNotificationStytle)style animated:(BOOL)animated
is called after I call
self.notification.setLeftAccessoryView(nil, animated: false)
as if I comment out
[self setLeftAccessoryView:self.accessoryView animated:animated];
in that method, everything works well.

OK coo, probably a mucked up order of operations then. Thanks for the tip. I'll dig in and get a fix for this.

Thank you!

@backmeupplz JFMinimalNotifications v0.0.5 has been published to CocoaPods https://cocoapods.org/pods/JFMinimalNotifications

Closed accidentally. Re-opened.

Hi @backmeupplz,
I was able to fix the problem by using a delegate:
extension ViewController: JFMinimalNotificationDelegate {

  func minimalNotificationWillShowNotification(notification: JFMinimalNotification!) {
    minimalNotification.setLeftAccessoryView(nil, animated: false)
    minimalNotification.layoutIfNeeded()
  }
}

Seems like it works almost for all required cases.

@valzevul
It's work

@valzevul It doesn't work sometime

@backmeupplz @valzevul @bawn
I just release v0.0.7 to CocoaPods https://cocoapods.org/pods/JFMinimalNotifications
It's also available in the Releases tab here https://github.com/atljeremy/JFMinimalNotifications/releases/tag/0.0.7
With this release there are 3 new styles, they are...
/**
 * @return Used to get a title and subtitle, no accessory views, and white bg with black label text. Use the .bakgroundColor property on the notification to set the desired background color and .textColor property on the titleLabel and subTitleLabel UILabel's to change text color.
 */
JFMinimalNotificationStyleCustom,

/**
 * @return A dark blur with vibrancy effect in the bakground with black label text.
 */
JFMinimalNotificationStyleBlurDark,

/**
 * @return A light blur with vibrancy effect in the bakground with black label text.
 */
JFMinimalNotificationStyleBlurLight

Each of these new styles doesn't show a left or right accessory view by default. So if you want a notification without left or right accessory views you can do something like this...
self.minimalNotification = [JFMinimalNotification notificationWithStyle:JFMinimalNotificationStyleCustom title:self.titleLabelTextField.text subTitle:self.subTitleLabelTextField.text dismissalDelay:0.0 touchHandler:^{
    [self.minimalNotification dismiss];
}];

// Set a custom backgroundColor, default for JFMinimalNotificationStyleCustom is white
self.minimalNotification.background = [UIColor purpleColor];

// Set title and subtitle label text color, default for JFMinimalNotificationStyleCustom is black
self.minimalNotification.titleLabel.textColor = [UIColor whiteColor];
self.minimalNotification.subTitleLabel.textColor = [UIColor whiteColor];

With this new update I'm going to close this issue. Setting the left accessoryView to nil before showing it isn't the way to show a notification without any accessory views. Use one of the new styles listed above to do so. Thanks!

@atljeremy awesome man, thank you very much!

@atljeremy Thanks


[5.9] [SymbolGraphGen] allow cursor symbol graphs from function params

Cherry-pick of https://github.com/apple/swift/pull/67267

Explanation: Updates SymbolGraphGen to support ParamDecl symbols, to support function and closure parameters.
Scope: Allows SourceKit to generate cursor-info symbol graphs for these symbols.
Issue: rdar://105516823
Risk: Low. The change is targeted to symbols that ordinarily wouldn't appear in whole-module symbol graphs, and only allows more symbols to have single-decl symbol graphs via SourceKit.
Testing: A test has been added to ensure the expected behavior.
Reviewer: @bnbarham

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test


Extra linebreak and inconsistent whitespace when columnifying html attributes.

With emmet as the only extension to brackets 1.0, I create an emtpy html-document and expand "!", place the cursor in the body and expand "div.stuff" or enter the  manually.
Place the cursor at the start of "class" and hit enter. I expect the class attribute to go one line down and get indented by one tab relative to the opening tag "<" character or indented to one space to the right of the opening "div" or some other consistent indentation that makes sense.
What I get is one line of whitespace and the class alligning with the "<" character of the opening div. In short I hit enter once, but I get two linebreaks. The behaviour is the same regardless of my tab-scheme; "Tab Size: 4" or "Spaces: 2".
After fiddling around a bit with different html, the behaviour does not appear to be consistent. For some other html I don't get an extra line of space when trying to linebreak on attributes. The indentation is not consistent either. Sometimes I get the attribute aligning with the "<" character, as above, but sometimes I get one space in addition.
Why is this important? Because sometimes, especially when writing AngularJS code I need many attributes and to make my templates more readable it helps to allign the attributes in a column rather than to flow them on a single line.
For reference, when not using any addons, the default behaviour is that the class moves one line straight down with no change to the char-count meaning 1 newline and enough whitespace to place the "class" at the same column as it had before hitting enter.
Thanks for a great tool! ;)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5794153-extra-linebreak-and-inconsistent-whitespace-when-columnifying-html-attributes?utm_campaign=plugin&utm_content=tracker%2F311111&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F311111&utm_medium=issues&utm_source=github).

+1, I'm seeing the same behavior, and so is this guy:
http://stackoverflow.com/questions/27251080/fixing-brackets-indentation-new-line-indentation-off-by-one-space-or-tab
Sometimes I'll enter down and the char count for tabs is off by one (as shown in the gif that the above StackOverflow question has).
I've confirmed that this is an Emmet issue because reloading Brackets without extensions fixes the problem, and the only other extensions I have are for the file tree and handlebars syntax highlighting.


[topgen] Fix flake8 lint errors

This needs a rebase onto the newest changes in master...

sorry looks like i forgot to check on my last merge. I'll try to remember going forward.

sorry looks like i forgot to check on my last merge. I'll try to remember going forward.

Don't worry. :) Anyway you can add flake8 to your pre-commit hook to prevent flake8 error from merging to the master.

Can someone approve this? :)


Introduce tests for a few Byzantine faulty cases

This pull request is trying to add test code for a few simple Byzantine faulty cases. As discussed in #127, we could have a hybrid approach of the complementary two approaches:

(1) tests whole network's behavior by mimicking all replicas individually, and
(2) tests one tested replica by mimicking surrounding network including the all other replicas.

This PR make a step on approach (1), and some of the simplest cases will be covered. Please see individual patches for more details.
One thing I'd like to discuss is that I don't think that inserting some hook into main logic like below is clean and optimal.
https://github.com/Naoya-Horiguchi/minbft/blob/94dfc5059779f71c2df58efaa411d597139beb94/core/message-handling.go#L256-L268
One possible better way to me is to convert package method startPeerConnections into instance method  of replica struct, then it's overwritable by introducing another variant struct like replicaBftTest struct which embeds the original replica struct. This approach seems better in the way that we can clearly separate the test logic from the main logic, and in another way that we could generalize the approach to other functions components in minbft package. One downside is that the code need to be changed in design level and the cost of the change might not be small.
I'm glad if I can hear about any ideas.

Just for your information, I'd like to share how the PBFT implementation in Fabric v0.6.1 is tested. It has a parameter in a configuration file as we do, to cause byzantine behavior; a peer will not send a broadcast message to one of peers with 1/3 possibility. This code is written in a production file (not a test file).
https://github.com/hyperledger/fabric/blob/e728c5c22160620e189e85be6becb7cbf75d87dc/consensus/pbft/pbft-core.go#L1286

One possible better way to me is to convert package method startPeerConnections into instance method of replica struct, then it's overwritable by introducing another variant struct like replicaBftTest struct which embeds the original replica struct. This approach seems better in the way that we can clearly separate the test logic from the main logic, and in another way that we could generalize the approach to other functions components in minbft package. One downside is that the code need to be changed in design level and the cost of the change might not be small.

The first way in looks good for me but I am not sure it is the best design in Go. As you mentioned, the way needs many changes and I think we can proceed with the current design because there is only one paremeter at now.

Just for your information, I'd like to share how the PBFT implementation in Fabric v0.6.1 is tested. It has a parameter in a configuration file as we do, to cause byzantine behavior; a peer will not send a broadcast message to one of peers with 1/3 possibility. This code is written in a production file (not a test file).
https://github.com/hyperledger/fabric/blob/e728c5c22160620e189e85be6becb7cbf75d87dc/consensus/pbft/pbft-core.go#L1286

Thanks for sharing/checking, Namiki-san. So such a faulty case seems possible way to go. In order to test other Byzantine cases in more systematic manner, I think that we have to understand what kind of Byzantine faults we can have. What I think of now are categorized as below:

selective ignorance: a Byzantine faulty replica refuses to send only to a set of other replicas. "Intentionally delay message" case may be included into this category.
inconsistent response: a Byzantine faulty replica responds to a set of replicas as the protocol specifies, but responds inconsisted (or manipulated) messages to the other replicas.
unexpected message: a Byzantine faulty replica sends random messages to one or more replicas at random.
(we could have better categorization...)

"selective ignorance" is relatively easy to test, but other types are protocol specific and maybe hard to test in current approach.

I am really sorry for such late feedback...

One thing I'd like to discuss is that I don't think that inserting some hook into main logic [...] is clean and optimal.

I believe even the core logic of correct behavior alone is already substantially complex, so inserting hooks for Byzantine behavior would clutter the code and make it even harder to follow, as well as introduce some additional performance overhead.

One possible better way to me is to convert package method startPeerConnections into instance method of replica struct, then it's overwritable by introducing another variant struct like replicaBftTest struct which embeds the original replica struct. This approach seems better in the way that we can clearly separate the test logic from the main logic, and in another way that we could generalize the approach to other functions components in minbft package.

Maybe we could convert parts of connectivity-related code (it's not much) into dependency-injection style, similar to the core protocol logic which is constructed from smaller components, mostly using function closure technique. It would help if we make defaultIncomingMessageHandler function more modular. That would allow us to reuse existing components for correct behavior and construct Byzantine replica instances by replacing individual components, clearly separating normal and testing logic.
Another approach would be to describe Byzantine replica behavior in specific test scenarios. This would require some testing framework to imitate Byzantine replica by merely executing/interpreting the scenario, which is basically generating and sending messages. The same approach would help us to test individual replicas by imitating the surrounding network.
As a side note, formal verification could be another possibility, but as far as I know, this is not really an option with imperative languages like Go.

[...] In order to test other Byzantine cases in more systematic manner, I think that we have to understand what kind of Byzantine faults we can have. What I think of now are categorized as below:

selective ignorance: a Byzantine faulty replica refuses to send only to a set of other replicas. "Intentionally delay message" case may be included into this category.

inconsistent response: a Byzantine faulty replica responds to a set of replicas as the protocol specifies, but responds inconsistent (or manipulated) messages to the other replicas.

unexpected message: a Byzantine faulty replica sends random messages to one or more replicas at random.

Forged message or "internally inconsistent" messages (e.g. Prepare from backup replica) would fall under "unexpected message" category, right?

"selective ignorance" is relatively easy to test, but other types are protocol specific and maybe hard to test in current approach.

In fact, "selective" ignorance can be simulated in a specifically crafted implementation of ReplicaConnector, completely separated from the core, but other types of failure would require somewhat more powerful mechanisms...

I believe even the core logic of correct behavior alone is already substantially complex, so inserting hooks for Byzantine behavior would clutter the code and make it even harder to follow, as well as introduce some additional performance overhead.

Yes, so we would want some way to avoid this.

Maybe we could convert parts of connectivity-related code (it's not much) into dependency-injection style, similar to the core protocol logic which is constructed from smaller components, mostly using function closure technique. It would help if we make defaultIncomingMessageHandler function more modular. That would allow us to reuse existing components for correct behavior and construct Byzantine replica instances by replacing individual components, clearly separating normal and testing logic.

OK, so this approach seem to be promising.

As a side note, formal verification could be another possibility, but as far as I know, this is not really an option with imperative languages like Go.

[...] In order to test other Byzantine cases in more systematic manner, I think that we have to understand what kind of Byzantine faults we can have. What I think of now are categorized as below:

selective ignorance: a Byzantine faulty replica refuses to send only to a set of other replicas. "Intentionally delay message" case may be included into this category.
inconsistent response: a Byzantine faulty replica responds to a set of replicas as the protocol specifies, but responds inconsistent (or manipulated) messages to the other replicas.
unexpected message: a Byzantine faulty replica sends random messages to one or more replicas at random.

Forged message or "internally inconsistent" messages (e.g. Prepare from backup replica) would fall under "unexpected message" category, right?

In my opinion, Byzantine behavior in "inconsistent response" category is something predictable and maybe it could be simulated by introducing a variant with some small changes from the normal core logic.  On the other hand, I assumed in "unexpected message" category that a testing replica receives messages in somehow unpredictable manner (meaning very far from our protocol).  The latter ones are by nature harder to define but maybe the above-mentioned scenario based approach is suitable for simulation.

"selective ignorance" is relatively easy to test, but other types are protocol specific and maybe hard to test in current approach.

In fact, "selective" ignorance can be simulated in a specifically crafted implementation of ReplicaConnector, completely separated from the core, but other types of failure would require somewhat more powerful mechanisms...

Sure, I first thought of adding another ReplicaConnector implementation for testing, but I felt difficulty (I don't remember details of it, sorry) and didn't make it.

Please check my feedback in #169 (comment). Besides that, I think we might already like to apply changes from 4b09c01, in a separate PR.

OK, I'll submit it later.

I'm implementing the same problem with another approach in #196. I think that it completely includes the testcases covered by this PR, so I no longer have to push this PR for merging. I close this issue.


Update local_directory WorkerType argument. Removes deprecation warning.

The WorkerType keyword argument has been changed from local_dir to local_directory. This removes a depreciation warning when launching workers.

I'm going to merge this and deal with the GHA issues in another PR.

Thanks for the contribution @kjgoodrick!


Create forum landing page for unauthenticated users

Closing this issue as not planned for now!

Reopening this issue to address this comment by @majorsylvie on #414 requesting a forum landing page for unauthenticated users.


New aka.ms link

Aka.ms link name
securitybestpractices
Category (Optional. Select None to auto-select)
None

Thank you for submitting aka.ms/securitybestpractices. Your link already exists at akaSearch.net. 🙏✅


Ptero egg

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
An egg ready for pterodactyl panel use
✔ Solution
An egg being made
❓ Alternatives
No response
📝 Additional Context
Pterodactyl panel is an easy was to host apps in a docker like environment

I have just had a quick look at the projects website. It seems to be based around hosting games with a nice frontend.
I have a couple of questions about this.
How would the egg be distributed? It doesn't seem as if there is a way to export the entire thing as a single file as it is very UI based.
Would users be able to use the standard docker file? It seems from the docs that a custom docker file based on alpine Linux is used, something that I think would be difficult to support long term, especially since the current alpine Linux docker file got depreciated as too much work to maintain.

So the egg is used to create server using the admin panel you can import the egg (uses a docker image) and then it builds a server from the image

So the egg is used to create server using the admin panel you can import the egg (uses a docker image) and then it builds a server from the image
https://github.com/parkervcp/eggs/blob/master/bots/discord/nodemon.js/egg-nodemon.json
This is an example of an egg

Ok, it's good that it is actually a single file. That would make it easier to share.
Can the default docker image be used or would a custom one be required?

I believe you current docker image should be fine you just have to add it to an egg

That is good.
I am not sure where this should go in terms of repositories. To me, it doesn't feel like it fits in the main repository. The root would start getting very cluttered if config files are added for every platform. Perhaps it should go somewhere in the wiki but I am not entirely sure on that or perhaps a third-party repo.

Hi, Just happen to see this maybe its useful info maybe not.
Ptero eggs are mainly maintained over here  This saves you having it in your repo.
If you want to contribute the config  i'd recommend to read the  CONTRIBUTING.md

Can the default docker image be used or would a custom one be required?
They want you to use the stock images. And Self-hosted or third-party images won't be accepted for security reasons.
If you need something in an image, open a PR in parkervcp yolks repo. This is the guy that maintains these images.

When will this be done?

I am really waiting for it since 2 months
@Computroniks

I am really waiting for it since 2 months @Computroniks

Amature.
Been waiting since nov 15, 22, 5months

@Shriy1556k @duckytutorials I do not have any experience with ptero eggs. There was some debate on where to store the config files as we don't want the root to become cluttered. I don't know where this is up to but if someone who has some experience with this sort of thing it could be worth looking into where to store the config files.

I might be able to create one later today. As I understand how they work now

@Computroniks @duckytutorials
I have already made this egg

I might be able to create one later today. As I understand how they work now

Just asking, did you do this?

@Computroniks @duckytutorials I have already made this egg

Hows that working for you?

I might be able to create one later today. As I understand how they work now

Just asking, did you do this?

Yes

I've made an egg for Uptime Kuma. You can download it here.

Does someone have this egg?

Does someone have this egg?

https://gist.github.com/meFqulted/b33d38af8c6fc56f3b96eb267260f1c3

@Viiiinx


Fix JVP rule for lax.pow()

Fixes #12033

I double-checked against the analog of the code in https://github.com/HIPS/autograd/issues/116, which inspired the introduction of this select statement. I get the same result before and after the change in this PR:
import jax
import jax.numpy as jnp

def fun(x):
    return jnp.exp(-(x*x))
d1 = jax.grad(fun)
d2 = jax.grad(d1)
d3 = jax.grad(d2)
d4 = jax.grad(d3)
print(d1(0.), d2(0.), d3(0.), d4(0.))
# -0.0 -2.0 0.0 12.0

def fun(x):
    return jnp.exp(-(x**2))
d1 = jax.grad(fun)
d2 = jax.grad(d1)
d3 = jax.grad(d2)
d4 = jax.grad(d3)
print(d1(0.), d2(0.), d3(0.), d4(0.))
# -0.0 -2.0 0.0 12.0

So, it turns out there is one (untested) case that this PR changes:
jax.grad(jax.lax.pow, 0)(0.0, 0.0)

On main, this returns 0.0; with this PR, it returns NaN.
Chatting offline with @mattjj, we realized this is similar in spirit to the sinc zero issue in (#5054); the resolution there was to do a custom JVP rule using the maclaurin series (#5077), and I think the most rigorously-correct solution here will probably be similar.


EXCEPTION: Invalid return character or leading space in header: User-Agent

I'm getting an EXCEPTION: Invalid return character or leading space in header: User-Agent and then the code runs and then errors on Waiting...
[•] URL: https://url.cloud | PAYLOAD: ${jndi:ldap://url.cloud.
/bbvurkv}
EXCEPTION: Invalid return character or leading space in header: User-Agent
[•] Payloads sent to all URLs. Waiting for DNS OOB callbacks.
[•] Waiting...
Traceback (most recent call last):
File "log4j-scan.py", line 336, in
main()
File "log4j-scan.py", line 325, in main
records = dns_callback.pull_logs()
File "log4j-scan.py", line 150, in pull_logs
return req.json()
File "/usr/lib/python3/dist-packages/requests/models.py", line 897, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python3/dist-packages/simplejson/init.py", line 518, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 370, in decode
obj, end = self.raw_decode(s)
File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 400, in raw_decode
return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

It seems that you network is injecting data into the HTTP response that breaks the JSON body of the response.


Why use two containers to run integration tests?

For the integration tests in the build pipeline, you use two containers. One that has integration tests and another for the database.
This introduces complexity where you have to:

copy source files from the agent to the docker image
configure containers to talk to each other
copy test results created in the container to the agent so they can be displayed in the pipeline

Question: Why not create one container for the database and run tests directly on the agent/host machine?

Hi @lamelyan,
We've done it long ago, and never bothered to change it. We'll accept PRs improving the test infrastructure.

I was just about to create a pipeline for a different solution, and I got reminded of this issue. @ardalis do you remember why we didn't set a single container (only for the database)? Is it just so we can wait for the database to be up and ready? And to do that, we had to run the tests in the container too, right?

Yeah, it was a long time ago and I think the reason was mainly ignorance on my part. There were docs and samples showing how to get a SQL docker image, and there were docs/samples on how to get a dotnet image, and it was easy enough to use docker-compose or whatever to make the two talk. I wasn't aware of a stock docker image that had both (if there is one), nor did I want to figure out how to configure a container with both, so here we are...

No, I think the question was more about why not just run the mssql-ubuntu image, and then run the tests from the agent (just connect to db). And I think the issue is that once the db container is up and running, the build task is considered done and moves to the next one, the testing one. But, at that stage even though the container is up, not necessarilly the db is up and ready.
So, you need some mechanism to wait for the db to be ready. Either you will have some bash script that loops until the db connection is ready, or use the approach in this project.
Here I found a nice article that describes both approaches https://alex-klaus.com/dotnet-sql-tests/
Anyhow, I don't see a huge benefit of changing the approach in this project. I'm closing the issue.


JSON Native Support

Coming out of Spawnfest 2022, json_native is an extension of :jason which adds a sprinkle of NIFs to make operations like Jason.encode! almost 1.5x faster for most inputs (and up to 8x faster than :jason for long strings).
It's very simple to adopt now as an optional dependency ({:jason_native, "~> 0.1.0"}) in the mix.exs file, it just needs{:jason, "~> 1.5.0-alpha.1"}.

closing and we can open up a PR when jason 1.5 is ready


test: add e2es for new pod affinity fields

Fixes #N/A
Description
Adds e2e test for the new pod affinity fields made beta in k8s 1.31.
How was this change tested?

Tested in a 1.31 k8s cluster, won't be able to test via /karpenter snapshot until EKS 1.31 is released.

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.025%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
5512

Relevant Lines:
6639

💛  - Coveralls


Fixed small typo in ES spanish translation.

Please make sure your PR is ready to be merged !

[x] You added the changes in CHANGELOG.md
[ ] You choose the right repository branch to make the PR
[ ] You described the PR as below

Changes :

Fixed small typo in ES spanish translation.

Related to (put here the others PR in other repositories)

Hi and thank you for you pull request.
To manage the ES translation we are using poeditor.
Can you please do your modification directly on spanish page of this project ?
https://poeditor.com/join/project/hEp5Khj4Ck
We'll import it in ES once done.

@rockaddicted Done!

great thank you @svera


change get_backend_name to accept multi-context

Description

change get_backend_name to return the right type even when the dev_id is not 0. e.g. 'cpu:1' was used to return 'interpreter' because of the dev_id is not 0.
uses backend_key instead of backend_name for the key of the unordered map. e.g. 'cpu:0'
needs to follow up on the Backend::create(backend_name) for transformers

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

TESTNOW


Mailers

Hi,
I came across this repo accidentally. Nice to see good code.
Thank you for making this open-source to learn some DDD.
But there seems some of the stuffs got changed recently. Eg : https://github.com/BenGorUser/User/blob/85628a911ea53205e5c250975100aef4dca778bb/docs/mailers.md mentions about installing swiftmailer.
But it should go for composer require bengor-user/swift-mailer-bridge and other one mailgun seems missing. There is another repo https://github.com/flint/Stampie , https://github.com/stof/StampieExtra ( if you have not came across ) that have different implementation other than mailgun.
I hope I can look into more details in the coming days and send a few PR to fix some of the inconsisteny.
Is there any roadmap or some other place where you guys discuss about the same ?
Thank you for your time reading.

Hi,
Thanks for your comment.
Those mailer docs are based in 0.5 versión and need a revision before we tag v0.6.
In v0.5 mailers were located in the infrastructure folder but in v0.6 we moved those implementations to separate packages leaving in this package just basic code.
UserMailer definition will not be changed for v0.6 and will be the same as noted in the docs.
The stampie integration should be developed as a separate package where UserMailer is implemented on top of the library you suggest. We do it in that way to keep our library as independent as we can from 3rd party libraries.
Our roadmap is to write some docs to let other devs play with the whole package ecosystem and once done that we will tag v0.6. If no big issues appear regarding the architecture of this package 1.0 will be tagged
Hope this answers all your questions. More questions are nore than welcome.

@harikt Our plan is to tag the new release today. You are very active in BenGorUser ecosystem so, we want to ask if you see finel for tagging or it is something wrong/missing before to publish new release.

@benatespina my policy is release often. So please do go with tagging new releases. We can always make new releases / fixes as soon as they are available.
Thank you so much for asking me my opinion though I have not contributed more into this.


Add documentation for flatpickr-mobile

Documentation for the feature which displays different inputfield for mobile devices would be great.

https://chmln.github.io/flatpickr/mobile-support/


HTC Vive: Document state of Linux OpenVR

https://www.reddit.com/r/Vive/wiki/linux

Per https://hacks.mozilla.org/2017/08/firefox-55-supports-webvr/#comment-21575

@kearwoodgilbert: what's the official status + notes I can provide for folks wondering about timeline/dependent bugs for Linux support?

The main bug to follow would be https://bugzilla.mozilla.org/show_bug.cgi?id=1310663
Someone told me that it allegedly once worked so I made https://bugzilla.mozilla.org/show_bug.cgi?id=1389339 but I don't really believe that it ever actually worked with OpenVR on Linux.
The only change in firefox has been a short period where OpenVR support on Linux had been disabled in the code, but later it was enabled again. Other than that it has been in this dysfunctional state since February, so don't get your hopes up for a quick resolution.
I mean I don't blame kip, he's a very busy guy, but Mozilla as a whole doesn't seem to care enough about libre platforms anymore to actually make someone work on it.

The status is actually documented in the source code of the website, it is just not actually shown anywhere, probably because there is no support from any browser.
Before anyone toggles this on (in case there is interest to do that), the description is not always right. The Linux entries are done like

"linux": "headset_unsupported",

which expands to the title/tooltip

Unsupported OS by headset maker

https://github.com/immersive-web/webvrrocks/blob/1e333c5a5ffba9ea3513dfdee8dfa0d1523f5e19/public/_helpers.html#L151-L154
That is wrong for the Vive. SteamVR and the Vive have been supported on Linux for over a year. It is the browsers that are lacking support.

thanks for digging in and clarifying, ChristophHaag - on it!


Custom classes

Hi,
Is there a possibility to use custom classes during generation? I have a separate package which defines classes for my project. Can I somehow use them?
Thanks in advance!

Nope, not at the moment.


support for simulator recorder

Adds a "recorder" button that allows to record animated gifs of the simulator.
TODO:

[ ] 3rd party notice
[ ] add logo
[ ] support for FF
[ ] trap all UI updates

simulator sends XML snapshots after updating state
rendered in UI thread
assembed into gif using gifjs

Is this tested on IE11 & Edge & mobile browsers?

@microsoftsam the simulator CSS does not seem to be complete anymore. Do we have dependencies on sim.css?

We got asked about this feature again recently, is it 'coming back'?

We already have various way to share which are under utilized.

Download screenshot
Download Hex
Share the link
Embed
I am not sure adding to the list will help the broader set of audience. We are still evaluating. This is unlikely to make it to V0.


system_gateways font-awesome convert

https://forum.pfsense.org/index.php?topic=101343.15

Merged. Thanks.


Xrs + mtls support for interoperator broker & cis quota app

Pull Request Test Coverage Report for Build 5809

19 of 91 (20.88%)  changed or added relevant lines in 5 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.5%) to 87.912%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

broker/data-access-layer/quota/src/QuotaAPIMtlsAuthClient.js
0
1
0.0%

broker/core/utils/src/HttpClient.js
4
8
50.0%

broker/core/express-commons/src/middleware/BrokerMtlsAPIClient.js
5
10
50.0%

broker/core/express-commons/src/middleware/index.js
7
69
10.14%

Files with Coverage Reduction
New Missed Lines
%

broker/core/express-commons/src/middleware/index.js
1
60.23%

broker/data-access-layer/cf/src/TokenIssuer.js
1
98.55%

Totals

Change from base Build 5793:
-0.5%

Covered Lines:
9753

Relevant Lines:
10705

💛  - Coveralls

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n+n+n is succeeded.

Validation on k8s cluster: n failed.

Validation on k8s cluster: n failed.

Validation on k8s cluster: n failed.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n+n+n is succeeded.

Validation on k8s cluster: n failed.

Validation on k8s cluster: n failed.

Validation on k8s cluster: n failed.


IERS A table workaround

Here's one solution to our troubles with the IERS Bulletin A table. I'll try to summarize what this is all about before describing the PR, and hopefully a discussion can emerge from @astroplanners/astroplanners-contributors about whether or not this is an OK fix. I acknowledge the inevitable gripe that this PR should really be to astropy, but for the sake of getting astroplan done before the summer is over, I'm keeping my work in astroplan.
Background
Earth orientation data is necessary to precisely calculate alt/az positions. The Earth orientation data used by astropy comes from IERS, and they post it in two forms. The IERS Bulletin B (denoted throughout astropy as "IERS B" or the "IERS B table") contains the orientation data for the recent past, based only on observations. The IERS Bulletin A has the data in Bulletin B and also extrapolations into the past and future. Leap seconds get factored into the future extrapolations in the IERS A table, making them necessary for precision O(seconds) in the near future. This table gets updated once a week.

See this blog post that I wrote up a few weeks ago for details on how to make those plots with astropy.
In the current version of astropy, the IERS Bulletin B is included in the package, but IERS Bulletin A is not. If you try doing a calculation with a time in the near future, you get:
IndexError: (some) times are outside of range covered by IERS table.

In astroplan so far, we've been running a script to download/cache the IERS Bulletin A (~3 MB) every time the user runs astroplan. This hasn't been a big deal because (1) we're connected to the internet, (2) after the first time you download it, you don't notice it's happening.
Since we want the tests to run without internet access, and we want users to be able to do these calculations without the internet, a workaround is needed that gives users access to IERS Bulletin A without an internet connection.
This PR
The solution here is to include IERS Bulletin A in the astroplan package data/ dir, stored as a text file. When the user accesses astroplan/core.py, a new function get_recent_IERS_A_table in the utils module is called that manages IERS Bulletin A. Here's what it does:

It first opens data/iers_bulletin_a.txt and looks to find the date when the observed Earth orientation data runs out and the predictions begin (which is flagged within the table). This tells you when the file was last updated
If the table has observations <7 days old, that table is returned and used for calculations.
If the table has no observations <7 days old, it tries to download a new copy of the table and store it in the same place as the old one (data/iers_bulletin_a.txt)
If the table has no observations <7 days old and the internet is not accessible, it uses the old (and only available) table and raises a warning like this:

WARNING: OldEarthRotationDataWarning: Your local copy of the IERS Bulletin A
table is 8.2 days old, and the internet can not be accessed to download the latest
copy. Earth rotation calculations will not be as precise as possible until you
reconnect to the internet and attempt to access the IERS Bulletin A table again.
[astroplan.utils]

Thanks for the context and background!
I'm still against including a copy of the table in astroplan because then the file is tied to the release schedule of astroplan. Imagine that releases only happen every 6 months. Then a typical user will install astroplan and have a ~3 month old version of the file. Based on the criteria you outline above for when to grab a new version of the file, all users will have to download a new version of the file anyways...?

RE @adrn :

Then a typical user will install astroplan and have a ~3 month old version of the file.

That's not how this PR works, actually. If the user has internet access, any table more than one week old will get refreshed. If the user does not have internet access, we simply can't do better than using an old table.
It's true though that we have update the astroplan version of the file every so often to ensure that people downloading the package for the first time get a reasonably recent version of the table to fall back on if they don't have consistent internet access.

Sorry, I guess I wasn't clear.
What I mean is this: if the release schedule is every 6 months, and a user installs astroplan 3 months after a release, then their IERS table will be 3 months old. So whenever they use astroplan and have an internet connection, a download will be triggered to get the new version anyways (as it happens now, right?). All I'm saying is that maybe there is a better solution than packaging a perpetually-old version of the table in to astroplan, especially since it is a few MB. For example, there may be a way to include an external file download in setup.py? I'm not sure, but @eteq might know.

So whenever they use astroplan and have an internet connection, a download will be triggered to get the new version anyways (as it happens now, right?).

In the PR, whenever a download is done it gets saved and replaces the data/iers_bulletin_a.txt file. The download only has to happen once a week to be perfectly up-to-date – the download does not happen every time, it just checks whether the present table is up-to-date each time.
Before this PR, the download happens once and gets cached (similar to in this PR, except that it's saved in the astropy cache).
Important Aside
Let's remind ourselves of the precision we're quibbling about. We can only calculate rise/set times to an accuracy of a few seconds right now anyways. For the average user, a few second offset of UTC-UT1 is a negligible difference, and even if the user doesn't connect to the internet for a year, the offset is likely still <3 seconds.

@adrn / @eteq: The current build has an error that looks like weird quantities behavior. In almost all contexts I've been able to compute an inequality for a Quantity that's a time duration (days, minutes) and a TimeDelta, but it's giving an error on some of the builds (but not all), see one here.

I understand that the file is cached now, and I understand the offsets are small. My point is just that even if we include a version of the file in astroplan, most users will still have to download an updated version of the file. I'm not arguing/quibbling about precision, I just don't think we should package the file in astroplan! If most users will need to download a more recent version of the file anyways because the packaged version is out of date, then we should just find a solution that grabs the newest version of the IERS file available on install. Again, I don't know how to do this, but I figure there must be a way!

I think the whole problem that @cdeil was trying to avoid was that users should be able to install/test without downloading anything.

And my point is that -- even with this PR -- the typical user will install astroplan, then immediately try to use it. Meaning it will immediately trigger a download to get the latest version of the file because the packaged version of the file is old. So I'm proposing we look for a solution that does the download on install rather than on first usage of the code. Then we don't have to package the IERS file with astroplan.

(and if that solution I suggest doesn't exist then fine, I give in)

Ok, now I understand.
I'm not disagreeing with you (yet), but is there a significant difference between doing it on install rather than on first use? Astroplan builds a lot of stuff at first use, rather than doing it on install.

In this case, the difference is just not packaging an out of date, 4 MB data file with astroplan that we then have to deal with. I know it doesn't seem like a hassle, but (a) even though it's only MB's, git doesn't like MBs and (b) I'm only making a fuss if there is an easy alternative solution, and this is the kind of something that @eteq will know immediately :)

Got it. Waiting on @eteq!

@bmorris3 – Thanks for implementing a possible solution for this issue! (Apart from https://travis-ci.org/astroplanners/astroplan/jobs/77017285#L555 which needs to be resolved.)
@adrn – I don't think we have to find and implement the long-term solution for this issue when to download or update the IERS table here. Download on install instead of first import has pretty much the same issues, i.e. install and travis-ci tests can fail if the site that hosts the IERS table is not available.
@olebole as Astropy Debian packager – Any advice on when the IERS A table should be downloaded / updated by Astropy (or astroplan for now) so that it would work e.g. for Astropy in Debian?
@bmorris3 – It seems that @adrn's main concern here is with bundling these few MB in the code repo. (And I share this concern a bit, it's not a great solution.)
Can you come up with a different solution that makes the IERS A table completely optional for astroplan? Maybe fall back to the IERS B table only? Or if that is not possible for some reason (the IndexError in Astropy), then fake a IERS A table using the IERS B table as input and adding one entry in the far past and future that does linear interpolation? I think that would be acceptable if a warning is emitted. Not super-high precision results are better than refusing to produce any results!

@eteq – Assigning this PR to you for the final decision.

@cdeil Would you suggest also revising all of the tests to use dates that exist in the IERS B table? Otherwise they'll break.

I think you should still test for dates in the the past and future.
But it's OK if those tests are low precision, at a level that corresponds to 'linear interpolation' of the always-available IERS B table (whatever that means exactly).
There can still be high-recision tests that require the IERS A table, but those should be marked @remote_data if IERS A isn't bundled.

No strong opinion here because this seems like trying to pick the "least bad" thing to do, but given a choice between requiring a download at installation vs. first use I would prefer at installation time.  If the cache freshness period is 7 days then at least tests should succeed without requiring a subsequent download.
What about at least providing a separate option in setup.py to download the table?  Then at least the travis builds can run that step before running tests.  I like the idea of the tests giving a warning that the table is out of date (and maybe should suggest the command to run to refresh the table).

@cdeil I still do not understand the whole context yet (it is the first time I heared about astroplanner :-) ), but I would put the data file into /var/cache/.... If it is used by more than one independent package (so, if astroplanner does not depend on astropy), I would create an extra package for that and  let the others depend on it.
About the update process:  Debian wants that the user keeps control the remote activities like downloads, so an automated download needs to be switched on somehow -- I will find out.

@bmorris3 @adrn - I left some inline suggestions on this (including an important but probably fairly easy-to-implement bit about location of the files).  But I'd also like to give an opinion on the at-install vs as-import question (and hopefully we can resolve this in the telecon later today):
I'm generally in favor of @adrn's idea of downloading at build-time if possible (more on how to do that below).  But I have one question for @bmorris3: do you need the IERS A file for some of this to work at all?  That is, is there functionality that works with even a horribly out-of-date IERS A that won't work with just IERS B?  If yes, then I'd say we have to include one with each release (updated, if possible, immediately before release), because that accounts for the user who gets the package and then later tries to install it without internet access.  So in that case I'm in favor of this PR plus what @adrn is suggesting.
As for the mechanics of downloading at-install: I think this isn't going to be that hard to implement if we follow my second in-line comment above about having the "preferred" IERS A file be in the astropy cache directory.  If that's what we want, all you have to do is do the download into that same location at the end of the install procedure.  Adding a final step to the install isn't too hard because we can just add in a custom install build command that runs a function to do this.  It should be only ~10 lines of code to do that (although it does require a bit of modification to the base level setup.py).

Closing in favor of #71, after conversation over Hangout and Slack.


Is it synchronous?

I see that the retrieved values are passed to callbacks. Is it because this library works asynchronously? If yes, why? Can't memory reading/writing be done synchronously?

Memcache is a distributed cache and is not in your local memory so you really do want these operations async.

@nmaves  makes sense, thanks!


Support for width/height and style attributes to media and image files

This commit adds the possibility to add inline style attributes to Medium objects and width and height attributes to ImageMedium objects. Usage is like shown below:
![Example](myimg.png?style=float:left)
![Example](myimg.png?width=200&height=400)
![Example](myimg.png?resize=100,200&width=100&height=200)  # match the resized dimensions
![Example](myimg.png?width=auto&height=auto) # use image's native dimensions
![Example](myimg.png?width&height)    # same as above, just more brief
{{ page.media['myimg.png'].width().height().html }}   # use image's native dimensions
{{ page.media['myimg.png'].resize(100,200).width(100).height(200).html }}

Going to hold off on reviewing this until next RC release is out.

Great addition.  Thanks!  I will need to remember to update the media docs after next release.


NIFI-2289: Directly ask ZooKeeper which node is cluster coordinator a…

…nd add watches on the ZNode rather than relying on Node Status Updates over the cluster protocol because cluster protocol may get the events out-of-order

Reviewing...


Fix accuracy mode

Closes https://github.com/mlcommons/mobile_app_open/issues/274

While investigating this I tried using the test dataset but it didn't work.
In our current tasks file test datasets has groundtruth files specified so I thought it would be suitable for accuracy mode testing. But apparently those groungtruth files don't match inputs of test datasets so accuracy is zero when using them.


wandb & tensorboard

visualize the loss

@ZhikangNiu Nice work! I want to reproduce your training. Can you share the training tensorboard for reference? Thx.

Sorry.It has been a long time here and I couldn’t found this log. So sad, feel free to ask questions 发自我的 iPhone在 2024年10月23日，20:10，xhq11 @.***> 写道：
@ZhikangNiu Nice work! I want to reproduce your training. Can you share the training tensorboard for reference? Thx.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@ZhikangNiu Do you still keep your original training config file and running command?

actually, I couldn’t find it :(发自我的 iPhone在 2024年10月24日，16:19，xhq11 @.***> 写道：
@ZhikangNiu Do you still keep your original training config file and running command?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Clean up mocha eslint errors

We've moved to<EMAIL_ADDRESS>which includes eslint-plugin-mocha.
A number of the mocha linting rules are quite valuable for keeping tests performant and readable but were turned off in Ghost because they caused a lot of noise with our existing codebase. It would be great to resolve the issues so that we can turn the rules back on.
You can find the list of rules that were turned off here https://github.com/TryGhost/Ghost/blob/master/core/test/.eslintrc.json#L24-L27
For anyone picking this issue up, a separate PR for each rule would be the preferred approach, please comment on this issue if you make a start to avoid duplicate work 🙂
General approach:

Choose a rule and check the rule's docs to make sure you understand what it's checking for and how to fix reported problems
Remove the line from core/test/.eslintrc.json that corresponds with the rule that you are enabling
Run yarn lint:test
Work through the reported problems - make a change to the code then run yarn lint:test again to make sure the problem disappears. If you have eslint configured in your editor you should be able to get some immediate feedback too
Periodically run grunt test:unit to make sure there haven't been any non-linting problems introduced by the code changes

starting on rule:
camelcase

working on rule ghost/mocha/no-identical-title

Hi,
created PR #11140
for max-top-level-suites
Thanks!

I'm going to start on the next available one:
no-setup-in-describe

I also reviewed nip10's PR and refactored the two pieces of code he was stuck on.
Once they are fixed it should be ready to be merged.

completed no-setup-in-describe
#11154
I still need to merge these PR with the updates that were completed over the last few days.

Hi,
I did a git pull push origin on my local repo.
Completed refactor changes and resubmitted PR
which is now #11164
Please let me know if any changes need to be made!

I am picking ghost/mocha/no-sibling-hooks

Hello! are all the rules fixed? can I pick one?

Hi, I believe they've all been claimed @dsuarezlogans

Hi,
@gargol
Updated PR #11154 after I accidentally pulled in some additional code into this commit.
passes
npm run test
npm run lint

Please let me know if anything else needs to be changed!

👋 Hello! Saw this was marked as stale, and the work done previously got outdated. Opened https://github.com/TryGhost/Ghost/pull/19720 to handle both ghost/mocha/no-identical-title and ghost/mocha/max-top-level-suites. I plan to finish the remaining ones in separate PRs!
In any case, it was a good opportunity to learn more about the codebase 🙌
cc @kevinansfield


filters: autosuggest filter values

related to #3 - #3 is about when you have to consult an fkey table for the label, this is about when the raw value is present
https://global-power-plants.datasettes.com/global-power-plants/global-power-plants?_sort=rowid&primary_fuel__exact=Solar&country_long__in=Canada%2C+United+States+of+America
When typing in the filter box, it'd be nice if it auto-suggested options
This might require some storage in order to remember candidate values (running SELECT DISTINCT xxx FROM table is likely slow)

see also https://github.com/simonw/datasette/issues/1890, which I think I broke by making facets lazy.

That feature is only available in the 1.0 alpha series, I think. You can see it working here: https://dux-demo.fly.dev/cooking/badges?_sort=id&_dux_show_filters=1&_dux_show_filters=1&_dux_show_filters=1&_dux_show_filters=1

Hmmmm, that's a lot of _dux_show_filters. Maybe now that we set _dux_show_filters=1, we don't need the hidden input?

The datalist autosuggest is something, gonna close this. If we do anything, it'll be in the omnibox.


Added null_resource to untaggable resources

the example01/aws/tags.feature was failing when I had a null_resource (which doesn't support tags). Seems pretty trivial, please be kind :)

Nevermind :) I created an issue about that and fix it within today.
Thanks a lot for the PR!

fixed.


[API DESIGN REVIEW] Recurrent Attention Layer(s)

I've laid out an API suggestion for application of attention mechanisms in a recurrent setting.
Full design review doc: https://docs.google.com/document/d/1psFXnmMlSTg5JapgZKz26ag-zBu3ERrxkKoEzNpzl4w/edit?usp=sharing
There is a proof-of-concept implementation of the API in my (play-ground) add-on library extkeras as well as an example of its use in model training.
There is still a lot of work needed, but if you think it's a good general direction I'm happy to take lead in completing the implementation.
Happy for all feedback at any level!

+1
On Sun, Aug 13, 2017 at 1:29 PM, andhus<EMAIL_ADDRESS>wrote:

I've laid out an API suggestion for application of attention mechanisms in
a recurrent setting.
Full design review doc: https://docs.google.com/document/d/
1psFXnmMlSTg5JapgZKz26ag-zBu3ERrxkKoEzNpzl4w/edit?usp=sharing
There is a proof-of-concept implementation of the API in my (play-ground)
add-on library extkeras
https://github.com/andhus/extkeras/blob/master/extkeras/layers/attention.py
as well as an example
https://github.com/andhus/extkeras/blob/master/examples/attention/graves_sequence_attention.py
of its use in model training.
There is still a lot of work needed, but if you think it's a good general
direction I'm happy to take lead in completing the implementation.
Happy for all feedback at any level!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/7633, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWGWKeajqfYEYKV6BFYAYLzAPsVncwPks5sX1yYgaJpZM4O1yfi
.

+1

This is important. Attention mechanisms is often used in various capacities in new papers. It would be highly beneficial to have a standard way to apply attention to general RNNs / LSTM / GRU.

I fully agree that we need built-in support for RNN attention in Keras, and I think this is a solid first proposal. What would be some alternative proposals? If none, we will go with this one.

As discussed in comments of the API Review doc, the introduction of standalone RNN Cells (https://github.com/fchollet/keras/pull/7943) will simplify and make addition of Recurrent Attention more modular. I'll adapt the API suggestion accordingly asap.

@fchollet The API doc is now updated, see the PR:s above which covers most crucial parts. Let me know if you think it's on the right track and I'll continue with step 3 and 4 according document. The concept of standalone cells really makes these things more modular and neat :D

@andhus I need a help . I've researched a lot but I'm stuck on something . I need to extract the attention weights . But couldn't find an tutorial or blog on how to do that . Just consider IMDB dataset , and after training , I will input a test data . Then I want to know which words in the test data are most important . I only know keras well . Is there any way ? For a better understanding I want something like deepmoji.mit.edu but it's simpler than that . Any kind of help by anyone is appreciated

Closing this issue in favor of #11172 for organization purposes. This issue can be reopened later on if necessary.


[Feature][linkis-engineconn-plugins/presto] Adapt Presto version 0.255

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Problem Description
At present, Presto plug-in only supports version 0.244 and below. It is recommended to adapt Presto version 0.255
Description
At present, Presto plug-in only supports version 0.244 and below. It is recommended to adapt Presto version 0.255
Use case
No response
solutions
No response
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

提供最新版DataSphereStudio全家桶安装服务。
包括（DataSphereStudio, Linkis, Exchangeis(Datax, Sqoop), Scriptis, Streamis(Flink), Visualis, DolphinScheduler)

另外包含 元数据，数据安全，数据质量，数据血缘。（这些都是DataSphereStudio不自带的服务）
包含hadoop集群搭建（hive, spark, flink, kafak, kylin）
提供上述所有系统二次定制开发服务
提供系统搭建运维疑难问题解决

添加备注，DSS大数据
持续为DataSphereStudio开源贡献力量


feat: tree hook for persisting blocks

Closes: #9235

also added logic to remove blocks from memory after successfully persisted


Provide a Vulkan surface view base implementation

Provides a base implementation of the Vulkan surface view (VkSurfaceView.kt) and its accompanying components.
The implementation is meant to be extended and updated in order to integrate it with the existing Godot java codebase.
The native layer is a stub at the moment, and is also meant to be extended and updated (based on @RandomShaper work) in order to provide the actual logic to setup and drive vulkan rendering.
The implementation is done in Kotlin, who's use in the engine (for Android) was recently green-lit!

Needs a rebase after #36798.

@akien-mga the PR was rebased.

Thanks!


[Feat] Adding Toast rather than simple alerts

Description
Currently for telling success and displaying message dureing signup and login we are seeing alerts which stops execution, instead i wanted to implement toast functionality for displaying messages
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

please assign this issue to me

Hey @Sourabh782, can you please share a demo video of the type of alert you want to contribute?

Star our repository ⭐

@mdazfar2 can I share ss?

Sure @Sourabh782

Sure @Sourabh782

like this, its currently toastify-js

And also, like you guys are changing project to next, may i know how can i contribute if i wanted to help?

Hey @Sourabh782, sorry for the late reply. I’ve been a little busy due to my health condition. We have converted the entire code to Next.js and Tailwind CSS for better backend integration. You raised a good issue, but it was based on the old HTML and CSS version. We’ve moved everything to Next.js and Tailwind CSS. Please look into that, and don’t forget to join our Discord Serverfor the latest website announcements and features.

And also please give Star us ⭐

Please don't be discouraged. I will close the issue for now, but you can raise a new one that is truly needed for our website. Thank you.


Added Switch

Preview 👁👁
https://github.com/user-attachments/assets/286a6dbe-cfcb-4115-a064-4e402899aec2

LGTM;


Why output_label=0 in datasets generation for Masked LM

In dataset.py, function 'random_word', line90, why the output_label of  85% data(no masking) is set to 0 ， output_label.append(0)？

So you mean only 15%  of all data are used to train MLM？

@jiqiujia @codertimo thanks, guys.


library not published

not able to sync.. Isn't available on jcentre either. https://jcenter.bintray.com/com/afollestad/

https://github.com/afollestad/easy-video-player/issues/7


[stable/reloader] Update ClusterRole and ClusterRoleBinding to use full name

Signed-off-by: James Ritter<EMAIL_ADDRESS>What this PR does / why we need it:
Updates ClusterRole and ClusterRoleBinding to use the chart full name in their names, so the chart can be deployed multiple times
Which issue this PR fixes

fixes #15759

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @kahootali

/assign faizanahmad055  you helped with my PR last time

@GreenKnight15 Approving this PR, but you should make changes to Reloader's official repo for any further changes, we will be deprecating this

/ok-to-test

/ok-to-test

/lgtm


Release floating IP address upon shelving an instance.

Our quota for floating IP address is less than the quota for our number of instances. As per discussion and request from JS2 admins, revise the shelving action to release the ip address back to the pool. IP addresses are scarce resources and most of our instances stay shelved.
This should no impact on the user, since now we are sending a new credential email to the users each time they are unshelving an instance, which should provide the new IP address.
@julianpistorius does this address the concern?

Yes, that would be ideal. Thank you!

Ditto. I will release the IP when shelving and re-associate one upon unshelving.


NullPointerException in AssemblyAnalyzer.analyzeDependency()

We are getting NullPointerException in assemblies in our project
The problem occurs using version 5.1.1 of the cli. It looks similar to #2025, but this one happens in a different line of code. Also, #2025 used to fail for many assemblies and most errors have disappeared in 5.1.1... just this one remains.
See below the error message and stack trace, thanks.
[WARN] An unexpected error occurred during analysis of 'MyAssembly.dll' (Assembly Analyzer): null
[ERROR]
java.lang.NullPointerException: null
        at org.owasp.dependencycheck.analyzer.AssemblyAnalyzer.analyzeDependency(AssemblyAnalyzer.java:234)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Sorry about that.  I need to build up a better set of .net assemblies to analyze as part of my test cases.

No problem... the one that ran into this issue is actually in nuget: https://www.nuget.org/packages/chilkat-win32/<IP_ADDRESS>. The assembly is \lib\net20\ChilkatDotNet2.dll.