Add native facebook "quick_reply" support as "facebook_quick_reply"

I've noticed that the quick_reply is perceived as a "message_received" event, where as the "facebook_postback" is a native event type. This is confusing for initial users unless time is spent reading through issues or the source code (#1224 + including myself).
This pull request adds "quick_reply" as a native facebook event. I've also assigned the quick_reply.payload to message.text as this would make it easier for creating proper listeners when combined with RegEx versus the quick_reply button text.

I would suggest implementing this as a plugin middleware that is separate from Botkit Core.
Can I ask, why do you want it to be a special event?

@benbrown
That's a good question. I suppose I've wrongfully viewed quick replies as a in-between offering to text and buttons (postbacks) due to the custom payload similar to a postback. Thus the complexity arises when a quick reply label (which is considered message.text) may have different utterances with identical payloads, or my payloads have identical labels with slightly different payloads (suggest:<user>, suggest:<business>, etc).
However, it seems this is a common confusion among users (#1244 , #1013, #992), so perhaps at a minimum an example general middleware in the docs would greatly benefit users as well as prevent breaking changes.
It seems there was a similar PR to this #992 (my apologize for duplication) suggesting a backward compatible solution triggering both events, but it would probably make sense to treat specific quick_reply event using the quick_replies.payload as the message.text, and maintain the default  message_received behavior as the quick_reply.text as the message.text to prevent duplication in triggered events and maximum compatibility.

We are currently not going to change the way quick replies are handled.


[DOC] how to work with existing react router v6 data router

Documentation issue
data router I mean createBrowserRouter, instead
Describe the thing to improve
Add doc using createBrowserRouter
Describe the solution (optional)
No response

Hello @wenerme could you elaborate more on your request? It's not clear what you are asking for.


Gmaps refactor to lat and lng

Issue
Issue number - #192
PR type
Location images show should have red marker and support all location

Pull Request Test Coverage Report for Build 430

0 of 0   changed or added relevant lines in 0 files are covered.
74 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.01%) to 43.242%

Files with Coverage Reduction
New Missed Lines
%

file:/home/travis/build/AY1920S1-CS2103T-T10-4/main/src/main/java/seedu/address/logic/internal/gmaps/ProcessVenues.java
2
94.29%

file:/home/travis/build/AY1920S1-CS2103T-T10-4/main/src/main/java/seedu/address/model/GmapsModelManager.java
3
77.78%

file:/home/travis/build/AY1920S1-CS2103T-T10-4/main/src/main/java/seedu/address/websocket/GmapsApi.java
7
50.0%

file:/home/travis/build/AY1920S1-CS2103T-T10-4/main/src/main/java/seedu/address/model/display/detailwindow/ClosestCommonLocationData.java
16
76.06%

file:/home/travis/build/AY1920S1-CS2103T-T10-4/main/src/main/java/seedu/address/websocket/Cache.java
46
49.24%

Totals

Change from base Build 427:
-0.01%

Covered Lines:
3036

Relevant Lines:
7021

💛  - Coveralls


jcenter issues

Latest version of this library uses Ktor 1.3.2 which it's getting from jcenter (with all the associated issues that's causing these days).  I realise this isn't being maintained but just in case anyone is planning on updating dependencies?

Go for it, PRs are welcome!

I think https://github.com/nielsfalk/ktor-swagger/pull/59 should go a long way towards this.


Wanted: accurate preview

You can go for a long time as an advanced LabVIEW user without realizing that while the LabVIEW Icon Editor is 24-bit, LabVIEW icons are 8-bit (the web-safe colors, to be precise, along with some extra grays). For instance, these gradients:

are crushed into:

And you have no feedback in the Icon Editor that this is about to happen, until you click OK. (Fortunately, the Icon Editor data model is also 24-bit, so you can open it back up to fix any issues that arise.)
The most annoying situation for this sort of thing is when you want to apply a slight tint to white, or perhaps some shade of gray. You're only going to be specifically doing that (and caring about the result) with an area fill. And that's precisely where any color differences will be most notable. Perhaps the worst-case scenario is in the light violets, with significantly more blue than red, in order to maximize the misalignment with the 6x6x6 color cube of the web-safe palette: #f7efff is crushed to white, while the only slightly-darker #f2e5ff goes off in a completely-different-yet-equally-unacceptable direction.

This can also lead to trouble when you want to apply some sort of overlay with a light alpha: at the high transparency settings you tend to want, only some of the pixels will actually be any different.
Ways to potentially solve this:

The icon preview in the Icon Editor should render the icon the same way LabVIEW would, including the color depth conversion.
Ask NI to add 32-bit icon support.
(Maybe) some better dither support, but I don't know how I feel about this, my experience with dither has been generally negative

An alternative way would be to limit the color pallette in the Icon editor to the websafe colors. This would be less intrusive to the LabVIEW VI Format, until the VI Format supports 24bit Icons.
I have cursed this feature multiple times because I was drawing some iconography for VIs using the TestStand green, which then was compressed into another green, that did not look anything like the amount of work I had put in for finding the right green.

It would also be useful to have a viewer that shows what the icon will look like when it is on a block diagram, including size (not zoomed in)

Besides this preview box

Good catch.  That's what I get for not double checking before making a post...


Task 185-188: conll2002 dataset

@Mirzyaaliii, wondering if you can help review these tasks.

General Comments -

Include dataset link and paper (if there is any) in the source field, for reference check tasks 166 and 313 here.
In the README, write the tasks in order.
Correct grammar and typos in the definition from all the tasks (few suggestions are provided below also.).
In the file name, keep all letters small.

Task - 185

Please check Task-345 here and change your whole task accordingly.
Also, check 312 on the same link and add the following things:

  "Input_language": "",
  "Output_language": "",
  "instruction_language": ""

Apply this change to all 4 tasks.

Task - 186

In the definition, it is mentioned as LOC and in the example, it is written as LOCN; correct it.
In the definition, correct this line
You should respond with the valid NET tags.

Task - 187

There are some special characters (e.g. \u00e9) in some examples and instances, remove that.
Apply this change to 188 as well.
Elaborate definition by explaining that how to generate output (write about B and I tag, PER, etc.).
Apply this change to 188 as well.
In the 3rd positive example, there is no word Bode in the input then how does it come into output. (Correct it or explain it.)
Also mention in the definition that there can be instance exist which has 0 Name Entity in the input. (if this is the case,)
Apply this change to 188 as well.

General comments -

Source and Category should be list not string (In all the tasks).
In the definition and explanation write . after each sentence and end (In all the tasks).
Delete the old file of Task -185.
Mention category at end of the filename (in all the tasks), for example,
task185_conll2002_pos_tagging_answer_generation
task187_conll2002_person_name_extraction_answer_generation
Change category of task 186 to Answer Generation.
In Task - 186 & 187, the output is in Dutch and English both languages, mention that in Output_language in the list.
In Task - 186 & 187, return output as None, if there is no name or location entity presents in the input. That makes more sense, compared to an empty string.

All things look good to me, can you please just make this one change:
In Task 186-188, separate entity and entity name by : as below
Marktrock: B-MISC, Leuven: B-LOC

One last change -
Change the definition (for Tasks 186-188)
from
There can be the instances with no ... name entities.
to
There can be instances with no ... name entity then return \*None\*.

@swarooprm All tasks look to me now. Proceed further.

@Mani9333, please fix the test failures and your HW2 will be complete.

Your HW2 is complete now.
Would you like to submit the same tasks to our big project repo https://github.com/allenai/natural-instructions-expansion/pulls? You just need to fork that repo, rename tasks starting from the latest number in the repo and create PR there. This way, you can be part of our research on "learning from instructions instead of learning from examples (conventional machine learning)". This is purely optional and your HW2 grade does not depend on this @Mani9333

@Mani9333, Just a reminder that, if you plan to submit these tasks to the main Github repo and join our research project, Monday (27th Sept) is the deadline. Again, this is optional and independent of your HW2 grade.


Ok, this is the important step to hare the server.

The French instance https://acesttoi.fr has been hardened in this way from the beginning, and it was necessary .
To use cmdeploy probably, using of ~/.ssh/conifg seams to be sensfull, and using ssh with key not with password is recommended.

this is not a complete PR -- did you manually install those files after you ran "cmdeploy run"?

I won't change cmddeploy.
There are some changes, that should be make during the installationen. At
least the change of the ssh-port is very important.
This change can be done by 'tee' or something else over the command - line.
The path should usualy be: /etc/ssh/sshd_config. If dropbear is used and
installed correctly, the changes in this file should be produced, too.
But there is - still - the problem with the use of ssh by cmddeploy. After
the the change, the new port is to give on every connection by using the
parameter -p 220XX with ssh.
As I don't want to delitate into cmddeploy, I only pushed the sshd_config
with in the changes to the original. So the change-protokol is more
important then the file itself.
holger krekel @.***> schrieb am Sa., 11. Mai 2024,
22:52:

this is not a complete PR -- did you manually install those files after
you ran "cmdeploy run"?
—
Reply to this email directly, view it on GitHub
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106028961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK35VR6NY37TMN3KA6W7S2TZB2AKNAVCNFSM6AAAAABHKHEPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAZDQOJWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't understand how you suggest to merge this, sorry.
This repo aims to make things automatically be setup via "cmdeploy" commands.
We try to keep the "out of cmdeploy" tasks to a minimum --
currently the DNS settings and adapting the web page.
So if we want to harden ssh in some way,
i am afraid we need to think how to integrate it.
On Sat, May 11, 2024 at 21:30 -0700, Dorfzwockel wrote:

I won't change cmddeploy.
There are some changes, that should be make during the installationen. At
least the change of the ssh-port is very important.
This change can be done by 'tee' or something else over the command - line.
The path should usualy be: /etc/ssh/sshd_config. If dropbear is used and
installed correctly, the changes in this file should be produced, too.
But there is - still - the problem with the use of ssh by cmddeploy. After
the the change, the new port is to give on every connection by using the
parameter -p 220XX with ssh.
As I don't want to delitate into cmddeploy, I only pushed the sshd_config
with in the changes to the original. So the change-protokol is more
important then the file itself.
holger krekel @.***> schrieb am Sa., 11. Mai 2024,
22:52:

this is not a complete PR -- did you manually install those files after
you ran "cmdeploy run"?
—
Reply to this email directly, view it on GitHub
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106028961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK35VR6NY37TMN3KA6W7S2TZB2AKNAVCNFSM6AAAAABHKHEPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAZDQOJWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Reply to this email directly or view it on GitHub:
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106114815
You are receiving this because you commented.
Message ID: @.***>

Ok, I am not so fit in find and replace by command line, but will try to
add a new command to cmdeploy which calls "harden" to do theses things
additionally if they are wanted.
holger krekel @.***> schrieb am So., 12. Mai 2024,
18:22:

I don't understand how you suggest to merge this, sorry.
This repo aims to make things automatically be setup via "cmdeploy"
commands.
We try to keep the "out of cmdeploy" tasks to a minimum --
currently the DNS settings and adapting the web page.
So if we want to harden ssh in some way,
i am afraid we need to think how to integrate it.
On Sat, May 11, 2024 at 21:30 -0700, Dorfzwockel wrote:

I won't change cmddeploy.
There are some changes, that should be make during the installationen. At
least the change of the ssh-port is very important.
This change can be done by 'tee' or something else over the command -
line.
The path should usualy be: /etc/ssh/sshd_config. If dropbear is used and
installed correctly, the changes in this file should be produced, too.
But there is - still - the problem with the use of ssh by cmddeploy.
After
the the change, the new port is to give on every connection by using the
parameter -p 220XX with ssh.
As I don't want to delitate into cmddeploy, I only pushed the sshd_config
with in the changes to the original. So the change-protokol is more
important then the file itself.
holger krekel @.***> schrieb am Sa., 11. Mai 2024,
22:52:

this is not a complete PR -- did you manually install those files after
you ran "cmdeploy run"?
—
Reply to this email directly, view it on GitHub
<
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106028961>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AK35VR6NY37TMN3KA6W7S2TZB2AKNAVCNFSM6AAAAABHKHEPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAZDQOJWGE

.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Reply to this email directly or view it on GitHub:
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106114815
You are receiving this because you commented.
Message ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/deltachat/chatmail/pull/289#issuecomment-2106305565,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK35VR5Z6XRZXPBOSHRQHVDZB6JLVAVCNFSM6AAAAABHKHEPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGMYDKNJWGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


[REPOSITORY] Egeria Notebooks

Name
egeria-jupyter-notebooks
Owner
planetf1, mandy_chessell
Deliverable
Provides Jupyter notebooks used for Egeria tutorials
Build, test and CI-CD process
The notebooks are currently in open-metadata-resources/open-metadata-labs.
They would be moved over (and later removed from core egeria).
We will no longer build a container with these notebooks, but rather access directly from github (copied into jupyter under control of our helm charts)
That copy will use either a specific SHA to refer to a consistent version as tested for a release, or we may implement a tagging or release process

SHA - lightweight, no build work needed
Tag - still fairly lightweight, clearer identity
release - clearer still, easier to download a bundle
branch & release - can maintain a service stream

Therefore there is no ci/cd process (automated test/verification is a future option)
https://github.com/odpi/egeria-jupyter-notebooks/issues/4 will track the specific migration of the code, removal from old repository, changes to charts, containers etc
Dependencies
Affects

egeria (source for the notebooks, jupyter container image)
egeria-charts (the lab chart requires these notebooks)

Justification
Continue splitting out egeria assets into logical units to make them easier to work with - by creators & consumers.
Assumptions
yes - true
Additional Information
No response
Work Plan
Before creating the repo

[x] review overall request & get clarifications
[x] get approval on developer/TSC call from maintainers

Creating the repo

[x] Create the repo under the odpi organization (default gitignore, license, readme)
[x] Setup branch protection rules
[x] Set pull request options (allow merge, squash, rebase, suggest updating, allow automerge, do not delete head)
[x] Update security settings in repo (policy, advisories, alerts)
[ ] set up permissions

First steps

[x] Initial code-drop (author)

Getting CI/CD started & refining settings

[x] Add initial build script for PR (including gradle wrapper if required)
[x] Add initial build script for merge

Further Refinement

[ ] Add link in egeria docs to new repo describing purpose ( https://github.com/odpi/egeria-docs/blob/main/site/docs/education/tutorials/git-and-git-hub-tutorial/egeria-git-repositories.md )
[ ] Add to connector catalog, if new repo is for connector ( https://github.com/odpi/egeria-docs/blob/main/site/docs/connectors/index.md )
[ ] Add to release process docs ( https://github.com/odpi/egeria-docs/blob/main/site/docs/guides/contributor/release-process/index.md )
[x] Add required credentials for publishing to container repos, maven central etc
[x] Add artifact signing if needed
[x] Add dependabot config
[x] Add CodeQL
[ ] Add to LFX ( https://projectadmin.lfx.linuxfoundation.org/project/a092M00001IV4JtQAL  ) for

[ ] LFXSecurity
[ ] LFAnalytics

[x] Add check for stale defects
[x] Add any required issue tags

Release

[x] Add release pipeline

remaining work is documentation so moving there


fixed app id

Thanks for submitting this PR.  It applies to a previous version of the skill, so closing.  The current version uses a different mechanism to verify the skill is being invoked by the correct skill, so this issue is resolved.


Push to more than 100 devices

Describe the solution you'd like
Be able to send push notification to more than 100 devices
Describe alternatives you've considered
I'm considering to split requests but didn't test it yet.
Is it possible to split push notification request (with more than 100 devices) in several requests ? (eg : a notification has to be sent to 350 devices, then 4 requests will be created and sent to appcenter server)

@ricavir11 yes, that's how you have to do it.


add more tests

This adds tests for StripeProvider and some more tests for the edge case paths of injectStripe.

Great!
I think some of these were covered in index.test.js -- worth delurking that, if all of the surface area is covered?

Good call. I removed the ones that are really just duplicates, but I left most of the other ones, because the test more complete integrations instead of stubbing out most parts.
The new tests are mostly to cover every possible edge case per component.

:+1:


Not grading correctly.

There is a problem with the grading system. It runs perfectly in python but it's giving a grade of less than 50%.
Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/question please use your course support channel.


Ignore certain actions

Maybe interesting feature could be to ignore certain actions from logging?
Cheers

I see predicate option


[Bug] Autoplay stop on resize window

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.5.0.

Platform/Target and Browser Versions: Debian 9 - Firefox Quantum 60.7.1-ESR

Live Link or JSFiddle/Codepen or website with isssue: https://jsfiddle.net/1rytecaw/

What you did
When auto play is active and browser window size was change it stop and does not working.
Expected Behavior
Auto play working like before...
Actual Behavior
Auto play stop
Note : This bug was reported before but won't fixed and closed with out date reason.

Hi @nolimits4web , Can you please tell me the reason of closing this issue?

Because it was fixed


Cannot bazel build tensorflow pip package from source (/usr/bin/env: 'python': No such file or directory)

System information

OS Platform and Distribution: Linux Ubuntu 16.04
CUDA Toolkit v8.0
cuDNN 5
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Bazel 0.5.0 (from repo)
Anaconda Python 3.6

francesco@gpu-box:~/tensorflow$ python
Python 3.6.0 |Anaconda custom (64-bit)| (default, Dec 23 2016, 12:22:00)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

Hello,
I am trying to build tensor flow pip package from source. I can install and use tensorflow with GPU using a precompiled binary just fine. However, in this case, I need to build from source.
Here is the following steps I take:

git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow
./configure

francesco@gpu-box:~/tensorflow$ ./configure
Please specify the location of python. [Default is /home/francesco/anaconda3/bin/python]:
Found possible Python library paths:
  /home/francesco/anaconda3/lib/python3.6/site-packages/
  /home/francesco/anaconda3/lib/python3.6/site-packages
Please input the desired Python library path to use.  Default is [/home/francesco/anaconda3/lib/python3.6/site-packages/]

Using python library path: /home/francesco/anaconda3/lib/python3.6/site-packages/
Do you wish to build TensorFlow with MKL support? [y/N] n
No MKL support will be enabled for TensorFlow
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]:
Do you wish to use jemalloc as the malloc implementation? [Y/n] y
jemalloc enabled
Do you wish to build TensorFlow with Google Cloud Platform support? [y/N] n
No Google Cloud Platform support will be enabled for TensorFlow
Do you wish to build TensorFlow with Hadoop File System support? [y/N] n
No Hadoop File System support will be enabled for TensorFlow
Do you wish to build TensorFlow with the XLA just-in-time compiler (experimental)? [y/N] n
No XLA JIT support will be enabled for TensorFlow
Do you wish to build TensorFlow with VERBS support? [y/N] n
No VERBS support will be enabled for TensorFlow
Do you wish to build TensorFlow with OpenCL support? [y/N] n
No OpenCL support will be enabled for TensorFlow
Do you wish to build TensorFlow with CUDA support? [y/N] y
CUDA support will be enabled for TensorFlow
Do you want to use clang as CUDA compiler? [y/N] n
nvcc will be used as CUDA compiler
Please specify the CUDA SDK version you want to use, e.g. 7.0. [Leave empty to use system default]: 8.0
Please specify the location where CUDA 8.0 toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify which gcc should be used by nvcc as the host compiler. [Default is /usr/bin/gcc]:
Please specify the cuDNN version you want to use. [Leave empty to use system default]: 5
Please specify the location where cuDNN 5 library is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify a list of comma-separated Cuda compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size.
[Default is: "3.5,5.2"]: 6.1
Do you wish to build TensorFlow with MPI support? [y/N] n
MPI support will not be enabled for TensorFlow
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
Configuration finished

Unfortunately, when I then build with bazel, it runs into an error. It seems like it cannot find python?
francesco@gpu-box:~/tensorflow$ bazel build -c opt --verbose_failures --config=cuda //tensorflow/tools/pip_package:build_pip_package
WARNING: /home/francesco/tensorflow/tensorflow/contrib/learn/BUILD:15:1: in py_library rule //tensorflow/contrib/learn:learn: target '//tensorflow/contrib/learn:learn' depends on deprecated target '//tensorflow/contrib/session_bundle:exporter': Use SavedModel Builder instead.
WARNING: /home/francesco/tensorflow/tensorflow/contrib/learn/BUILD:15:1: in py_library rule //tensorflow/contrib/learn:learn: target '//tensorflow/contrib/learn:learn' depends on deprecated target '//tensorflow/contrib/session_bundle:gc': Use SavedModel instead.
INFO: Found 1 target...
INFO: From Compiling external/snappy/snappy-sinksource.cc [for host]:
cc1plus: warning: command line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++
cc1plus: warning: unrecognized command line option '-Wno-shift-negative-value'
INFO: From Compiling external/snappy/snappy-c.cc [for host]:
cc1plus: warning: command line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++
cc1plus: warning: unrecognized command line option '-Wno-shift-negative-value'
INFO: From Compiling external/snappy/snappy-stubs-internal.cc [for host]:
cc1plus: warning: command line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++
cc1plus: warning: unrecognized command line option '-Wno-shift-negative-value'
INFO: From Compiling external/snappy/snappy.cc [for host]:
cc1plus: warning: command line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++
external/snappy/snappy.cc: In member function 'void snappy::SnappySinkAllocator::Flush(size_t)':
external/snappy/snappy.cc:1403:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     for (int i = 0; i < blocks_.size(); ++i) {
                       ^
In file included from external/snappy/snappy-internal.h:34:0,
                 from external/snappy/snappy.cc:30:
external/snappy/snappy.cc: In instantiation of 'bool snappy::SnappyScatteredWriter<Allocator>::AppendFromSelf(size_t, size_t) [with Allocator = snappy::SnappySinkAllocator; size_t = long unsigned int]':
external/snappy/snappy.cc:715:13:   required from 'void snappy::SnappyDecompressor::DecompressAllTags(Writer*) [with Writer = snappy::SnappyScatteredWriter<snappy::SnappySinkAllocator>]'
external/snappy/snappy.cc:799:3:   required from 'bool snappy::InternalUncompressAllTags(snappy::SnappyDecompressor*, Writer*, snappy::uint32) [with Writer = snappy::SnappyScatteredWriter<snappy::SnappySinkAllocator>; snappy::uint32 = unsigned int]'
external/snappy/snappy.cc:1460:78:   required from here
external/snappy/snappy.cc:1316:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (PREDICT_TRUE(offset - 1u < op_ptr_ - op_base_ && op_end <= op_limit_)) {
                                  ^
external/snappy/snappy-stubs-internal.h:80:25: note: in definition of macro 'PREDICT_TRUE'
 #define PREDICT_TRUE(x) x
                         ^
At global scope:
cc1plus: warning: unrecognized command line option '-Wno-shift-negative-value'
ERROR: /home/francesco/.cache/bazel/_bazel_francesco/7b3bdb053a374c3fec955b526c0e6446/external/highwayhash/BUILD.bazel:8:1: C++ compilation of rule '@highwayhash//:sip_hash' failed: crosstool_wrapper_driver_is_not_gcc failed: error executing command
  (cd /home/francesco/.cache/bazel/_bazel_francesco/7b3bdb053a374c3fec955b526c0e6446/execroot/tensorflow && \
  exec env - \
    CUDA_TOOLKIT_PATH=/usr/local/cuda \
    CUDNN_INSTALL_PATH=/usr/local/cuda-8.0 \
    GCC_HOST_COMPILER_PATH=/usr/bin/gcc \
    PWD=/proc/self/cwd \
    PYTHON_BIN_PATH=/home/francesco/anaconda3/bin/python \
    PYTHON_LIB_PATH=/home/francesco/anaconda3/lib/python3.6/site-packages/ \
    TF_CUDA_CLANG=0 \
    TF_CUDA_COMPUTE_CAPABILITIES=6.1 \
    TF_CUDA_VERSION=8.0 \
    TF_CUDNN_VERSION=5 \
    TF_NEED_CUDA=1 \
    TF_NEED_OPENCL=0 \
  external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -DNDEBUG -ffunction-sections -fdata-sections '-std=c++11' -MD -MF bazel-out/local_linux-py3-opt/bin/external/highwayhash/_objs/sip_hash/external/highwayhash/highwayhash/sip_hash.pic.d '-frandom-seed=bazel-out/local_linux-py3-opt/bin/external/highwayhash/_objs/sip_hash/external/highwayhash/highwayhash/sip_hash.pic.o' -fPIC -iquote external/highwayhash -iquote bazel-out/local_linux-py3-opt/genfiles/external/highwayhash -iquote external/bazel_tools -iquote bazel-out/local_linux-py3-opt/genfiles/external/bazel_tools -isystem external/bazel_tools/tools/cpp/gcc3 -no-canonical-prefixes -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fno-canonical-system-headers -c external/highwayhash/highwayhash/sip_hash.cc -o bazel-out/local_linux-py3-opt/bin/external/highwayhash/_objs/sip_hash/external/highwayhash/highwayhash/sip_hash.pic.o): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 127.
/usr/bin/env: 'python': No such file or directory
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 44.289s, Critical Path: 5.54s

Both my python_bin_path and python_lib_path are correct, so I do not understand.
Any advice?
Regards

I am pretty certain the cause is using anaconda python, instead of ubuntu python.
Is your python bin path included in your "path" environment variable?

francesco@gpu-box:~$ env
SHELL=/bin/bash
LD_LIBRARY_PATH=/usr/local/cuda-8.0/lib64
PATH=/home/francesco/anaconda3/bin:/usr/local/cuda-8.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
PWD=/home/francesco
HOME=/home/francesco
_=/usr/bin/env

Yes it's included, AFAIK

@damienmg Could you help look into this?
highwayhash//:siphash seems to be a cc rule, but I am not sure why we see the failure here.
maybe there is some backwards incompatible change with bazel 0.5?

Can you try with --action_env PATH?

Nope.
Tried variations like --action_env PATH, --action_env=PATH, --action_env=$PATH to no avail.

--action_env PATH="$PATH"?

Hi,
That worked!
At global scope:
cc1plus: warning: unrecognized command line option '-Wno-self-assign'
Target //tensorflow/tools/pip_package:build_pip_package up-to-date:
  bazel-bin/tensorflow/tools/pip_package/build_pip_package
INFO: Elapsed time: 1238.673s, Critical Path: 133.18s

However, I then build a wheel (still fine)
francesco@gpu-box:~/tensorflow$ bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg
mer 31 mag 2017, 18.48.47, CEST : === Using tmpdir: /tmp/tmp.D9nGwyy56D
~/tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package.runfiles ~/tensorflow
~/tensorflow
/tmp/tmp.D9nGwyy56D ~/tensorflow
mer 31 mag 2017, 18.48.48, CEST : === Building wheel
warning: no files found matching '*.dll' under directory '*'
warning: no files found matching '*.lib' under directory '*'
~/tensorflow
mer 31 mag 2017, 18.48.58, CEST : === Output wheel file is in: /tmp/tensorflow_pkg

I install the wheel tensorflow-1.2.0rc0-cp36-cp36m-linux_x86_64.whl
francesco@gpu-box:~/tensorflow$ pip install /tmp/tensorflow_pkg/tensorflow-1.2.0rc0-cp36-cp36m-linux_x86_64.whl
Processing /tmp/tensorflow_pkg/tensorflow-1.2.0rc0-cp36-cp36m-linux_x86_64.whl
Requirement already satisfied: six>=1.10.0 in /home/francesco/anaconda3/lib/python3.6/site-packages (from tensorflow==1.2.0rc0)
Collecting bleach==1.5.0 (from tensorflow==1.2.0rc0)
  Using cached bleach-1.5.0-py2.py3-none-any.whl
Requirement already satisfied: wheel>=0.26 in /home/francesco/anaconda3/lib/python3.6/site-packages (from tensorflow==1.2.0rc0)
Collecting markdown==2.2.0 (from tensorflow==1.2.0rc0)
  Downloading Markdown-2.2.0.tar.gz (236kB)
    100% |████████████████████████████████| 245kB 1.8MB/s
Requirement already satisfied: werkzeug>=0.11.10 in /home/francesco/anaconda3/lib/python3.6/site-packages (from tensorflow==1.2.0rc0)
Requirement already satisfied: protobuf>=3.2.0 in /home/francesco/anaconda3/lib/python3.6/site-packages (from tensorflow==1.2.0rc0)
Requirement already satisfied: numpy>=1.11.0 in /home/francesco/anaconda3/lib/python3.6/site-packages (from tensorflow==1.2.0rc0)
Collecting html5lib==0.9999999 (from tensorflow==1.2.0rc0)
  Using cached html5lib-0.9999999.tar.gz
Requirement already satisfied: setuptools in /home/francesco/anaconda3/lib/python3.6/site-packages/setuptools-27.2.0-py3.6.egg (from protobuf>=3.2.0->tensorflow==1.2.0rc0)
Building wheels for collected packages: markdown, html5lib
  Running setup.py bdist_wheel for markdown ... done
  Stored in directory: /home/francesco/.cache/pip/wheels/b9/4f/6c/f4c1c5207c1d0eeaaf7005f7f736620c6ded6617c9d9b94096
  Running setup.py bdist_wheel for html5lib ... done
  Stored in directory: /home/francesco/.cache/pip/wheels/6f/85/6c/56b8e1292c6214c4eb73b9dda50f53e8e977bf65989373c962
Successfully built markdown html5lib
Installing collected packages: html5lib, bleach, markdown, tensorflow
Successfully installed bleach-1.5.0 html5lib-0.9999999 markdown-2.2.0 tensorflow-1.2.0rc0

but when I try to import tensorflow, it fails :(
francesco@gpu-box:~/tensorflow$ python
Python 3.6.0 |Anaconda custom (64-bit)| (default, Dec 23 2016, 12:22:00)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow
Traceback (most recent call last):
  File "/home/francesco/tensorflow/tensorflow/python/pywrap_tensorflow.py", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
ModuleNotFoundError: No module named 'tensorflow.python.pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/francesco/tensorflow/tensorflow/__init__.py", line 24, in <module>
    from tensorflow.python import *
  File "/home/francesco/tensorflow/tensorflow/python/__init__.py", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "/home/francesco/tensorflow/tensorflow/python/pywrap_tensorflow.py", line 52, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "/home/francesco/tensorflow/tensorflow/python/pywrap_tensorflow.py", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
ModuleNotFoundError: No module named 'tensorflow.python.pywrap_tensorflow_internal'

Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/install_sources#common_installation_problems

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Is it an issue with the building process, or making the wheel, or installing the wheel?

Hi,
That worked. Ran into another issue ModuleNotFoundError: No module named 'tensorflow.python.pywrap_tensorflow_internal'when importing the tensorflow in python, but that's only because I was running the shell in the git directory :)
Will close the issue.

Got snagged by this too. Anaconda is very common, recommend adding a side-note of this flag in the installation instructions

I used bazel 0.21 for TF 1.13.1, and I had to add --noincompatible_strict_action_env as well.

@hsgkim , Thanks! Compiled TF with this command:
bazel build --config=opt --config=cuda --noincompatible_strict_action_env //tensorflow/tools/pip_package:build_pip_package

Ubuntu 20.04.
It's work for me
sudo ln -s /usr/bin/python3 /usr/bin/python

Ubuntu 20.04.
It's work for me
sudo ln -s /usr/bin/python3 /usr/bin/python

Thank you @deslum
the command worked for me too.
ubuntu 21.04


Add text label for airplay active state

Show AirPlay is active label for AirPlay active state. Hide label if content controls are shown.

I prefer having design similar to the native iOS player. This looks not good. Probably we should contact  Sigma designer to improve this.

@BogdanBilonog Update screenshots in PR.


[x-plane] Update to 3.0.3

Describe the pull request

What does your PR fix?
Updated x-plane package to latest (3.0.3) & changed macOS lib deployment to include .framework directories as it is in the original package.

Which triplets are supported/not supported? Have you updated the CI baseline?
Package is header & precompiled lib only

Does your PR follow the maintainer guide?
Yes

Hi @siavee
Thanks for your PR.
Could you please help check the build status on arm, uwp and linux for the new version?
If they have passed, please remove these codes from ci.baseline.txt.
x-plane:arm64-windows=fail
x-plane:arm-uwp=fail
x-plane:x64-linux=fail
x-plane:x86-windows=fail

x-plane:x86-windows=fail can be removed now since you have added Supports: !x86 in vcpkg.json.

Hi @NancyLi1013 thanks for the review, the SDK is x64 only so arm is definitely unsupported. I've tested x64-linux to be working find. I'll update the requested files in a bit.

Please help update the test result on Linux, thanks.

Roger, in a bit

Working fine in Linux.

LGTM now, thanks for your PR @siavee.

Thanks for the review too @NancyLi1013 :)

Thank you!

And thank you to you too!


Fix visibility for this repo

I notice the repo has no description or topics used on the main page:
https://github.com/sfackler/cargo-tree
this really hurts visbility, as people searching GitHub for dependency
or dependencies arent going to find this repo.
They would only find it with tree or dependency in:readme, which introduces a lot of noise.

Looks like this is now built into Rust


Don't send " skipped the night" to players in beds if they are the only ones sleeping

fixed in https://github.com/globau/ClodMC/commit/6fcb1d806b15da1e7130fc438508b6cb900315f4


added "back to top button"

Implements "Back to Top" Button
This pull request adds a new "Back to Top" button to the user interface. The button is positioned in the bottom right corner and remains visible even when the user scrolls down the page (pinned behavior). Clicking the button smoothly scrolls the user back to the top of the page.
Benefits:
Improves user experience by providing a convenient way to navigate back to the top of the page.
Enhances accessibility by offering an alternative scrolling option for users.

There is some conflicting issue in style.css
Check it & then create PR agaim


correction of icons and improvement of footer section #23

updated the logo of footer icons

@subhadipbhowmik sir why there is so may conflict coming in my code.


Use "u" and "d" for half page

Matches Less and Moar

I'm sorry, please customize it.
Changes to the default key bindings will not be accepted by pull requests.


Build fails when using OLLAMA_SKIP_CPU_GENERATE=1 on aarch64 Linux

What is the issue?
When using the OLLAMA_SKIP_CPU_GENERATE=1 flag for compiling the binary, the Ollama binary fails to compile with the error:
In file included from gpu_info_nvml.h:4,
                 from gpu_info_nvml.c:5:
gpu_info_nvml.c: In function ‘nvml_check_vram’:
gpu_info_nvml.c:158:20: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘long long unsigned int’ [-Wformat=]
  158 |     LOG(h.verbose, "[%d] CUDA totalMem %ld\n", i, memInfo.total);
      |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~     ~~~~~~~~~~~~~
      |                                                          |
      |                                                          long long unsigned int
gpu_info.h:33:23: note: in definition of macro ‘LOG’
   33 |       fprintf(stderr, __VA_ARGS__); \
      |                       ^~~~~~~~~~~
gpu_info_nvml.c:158:42: note: format string is defined here
  158 |     LOG(h.verbose, "[%d] CUDA totalMem %ld\n", i, memInfo.total);
      |                                        ~~^
      |                                          |
      |                                          long int
      |                                        %lld
In file included from gpu_info_nvml.h:4,
                 from gpu_info_nvml.c:5:
gpu_info_nvml.c:159:20: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘long long unsigned int’ [-Wformat=]
  159 |     LOG(h.verbose, "[%d] CUDA freeMem %ld\n", i, memInfo.free);
      |                    ^~~~~~~~~~~~~~~~~~~~~~~~~     ~~~~~~~~~~~~
      |                                                         |
      |                                                         long long unsigned int
gpu_info.h:33:23: note: in definition of macro ‘LOG’
   33 |       fprintf(stderr, __VA_ARGS__); \
      |                       ^~~~~~~~~~~
gpu_info_nvml.c:159:41: note: format string is defined here
  159 |     LOG(h.verbose, "[%d] CUDA freeMem %ld\n", i, memInfo.free);
      |                                       ~~^
      |                                         |
      |                                         long int
      |                                       %lld
# github.com/ollama/ollama
<EMAIL_ADDRESS>running gcc failed: exit status 1
gcc: error: /home/tegra/ok3d/ollama-container/dev/ollama/llm/build/linux/arm64_static/libllama.a: No such file or directory

What did you expect to see?
It appears code to build a required static library folder was added inside of the optional flag OLLAMA_SKIP_CPU_GENERATE on line 62. Not sure if the intent was to build the _static folder to include in every build or to only include it when building for CPU.
Additionally, although I enjoy saving time by adding the OLLAMA_SKIP_CPU_GENERATE flag, should the LCD_CPU build be created regardless of the skip flag as a fallback for GPU OOM?
Steps to reproduce
Set OLLAMA_SKIP_CPU_GENERATE=1 as an environment variable for compiling the binary.
Are there any recent changes that introduced the issue?
In file llm/generate/gen_linux.sh, the following code snippet exists starting on line 62:
if [ -z "${OLLAMA_SKIP_CPU_GENERATE}" ]; then

    if [ -z "${OLLAMA_CPU_TARGET}" -o "${OLLAMA_CPU_TARGET}" = "static" ]; then
        # Static build for linking into the Go binary
        init_vars
        CMAKE_TARGETS="--target llama --target ggml"
        CMAKE_DEFS="-DBUILD_SHARED_LIBS=off -DLLAMA_NATIVE=off -DLLAMA_AVX=off -DLLAMA_AVX2=off -DLLAMA_AVX512=off -DLLAMA_FMA=off -DLLAMA_F16C=off ${CMAKE_DEFS}"
        BUILD_DIR="../build/linux/${ARCH}_static"
        echo "Building static library"
        build
    fi

OS
Linux
Architecture
arm64
Platform
No response
Ollama version
0.1.30
GPU
Nvidia
GPU info
NVidia Jetson Orin Nano 8Gb (Tegra ARM64v8 SOC)
CPU
Other
Other software
No response

We've been shuffling things around a bit with the new subprocess based model.  We're building a static link version of the library to link to ollama via cgo so we can access some low-level routines.  In our Dockerfile, we build the CPU variants in other build targets and then stitch the results together.  Largely this is meant as a mechanism to be able to parallelize more parts of the build process to speed it up.
I'm not sure what your objective is, so I'm not sure how we want to adjust these settings.  Ultimately we do need to generate llm/build/linux/arm64_static/libllama.a to be able to compile.

The logic to build libllama.a (mandatory piece) is held within an optional flag (the skip cpu gen flag), I figured just move libllama.a to build every time? I skip the cou generate on the Jetson so it only builds cuda

Got it.  This might be getting into diminishing returns, but splitting those out for the x86 and arm build shaves off 30-60 seconds of wall-clock time for the build.  ROCm is by far the slowest part of the build (x86 only) but we're trying to keep things as efficient and parallelizable as possible given the volume of llama.cpp variants we're building.  I'm expecting more variants will come over time.
Feel free to land a PR to refine this, as long as we can retain the parallel logic here and here and not build the libllama.a multiple times.

Okay, so I was thinking we could either add a flag to skip static generation like:
if [ -z "${OLLAMA_SKIP_STATIC_GENERATE}" ]; then <build llm/build/linux/${ARCH}_static/libllama.a>
If the llm/build directory is shared between builds, can instead just check if it's already built with:
if [ -z llm/build/linux/${ARCH}_static/libllama.a ]; then <build llm/build/linux/${ARCH}_static/libllama.a>.
Would either of these work for you? I know adding the skip flag would add an additional ARG line per container build, which I think should be avoided when possible but I'm not seeing a lot of viable options for programmatically skipping a portion of the build while making it happen by default.

In the containerized build, the filesystem isn't shared as they're all running in parallel on their own overlay filesystem, so I don't think the second option will work.  Flags are probably the best option and set it up so a simple go generate ./... gets all the bits and pieces, but the containerized build can set flags to optimize the parallelism.

@dhiltgen Do you include a RUN OLLAMA_CPU_TARGET="static" <generate> line in every build that requires one? I'm asking because if so, I'd change the Dockerfile to blanket OLLAMA_SKIP_STATIC_GENERATE, and set OLLAMA_CPU_TARGET="static" to override the skip when you want to build it. It would still build the static by default.
init_vars
if [ -z "${OLLAMA_SKIP_STATIC_GENERATE}" -o "${OLLAMA_CPU_TARGET}" = "static" ]; then
    # Builds by default, allows skipping, forces build if OLLAMA_CPU_TARGET="static"
    # Enables optimized Dockerfile builds using a blanket skip and targeted overrides
    # Static build for linking into the Go binary
    init_vars
    CMAKE_TARGETS="--target llama --target ggml"
    CMAKE_DEFS="-DBUILD_SHARED_LIBS=off -DLLAMA_NATIVE=off -DLLAMA_AVX=off -DLLAMA_AVX2=off -DLLAMA_AVX512=off -DLLAMA_FMA=off -DLLAMA_F16C=off ${CMAKE_DEFS}"
    BUILD_DIR="../build/linux/${ARCH}_static"
    echo "Building static library"
    build
fi

If not, how do you want to handle the cascading if statements? I guess I could just leave it like this and you can further adjust it later.
init_vars
if [ -z "${OLLAMA_SKIP_STATIC_GENERATE}" ]; then
    if [ -z "${OLLAMA_CPU_TARGET}" -o "${OLLAMA_CPU_TARGET}" = "static" ]; then
        init_vars
        CMAKE_TARGETS="--target llama --target ggml"
        CMAKE_DEFS="-DBUILD_SHARED_LIBS=off -DLLAMA_NATIVE=off -DLLAMA_AVX=off -DLLAMA_AVX2=off -DLLAMA_AVX512=off -DLLAMA_FMA=off -DLLAMA_F16C=off ${CMAKE_DEFS}"
        BUILD_DIR="../build/linux/${ARCH}_static"
        echo "Building static library"
        build
    fi
fi

#3708 Submitted


added lunas

edit: whoops, forgot to leave a comment
lunas is an Uxntal assembler I made that's written in Lua, with better error reporting than uxnasm

whoops, forgot to leave a comment.
lunas is an Uxntal assembler I made that's written in Lua, with better error reporting than uxnasm

Very cool :D Added!

yippee


Add new API bindParameters() for simple parameter bindings

It implements the feature mentioned in PR #111

I have to mention that the output of the parameter list has changed!
Previously we only get the out & in_out parameters output.
But now the new API can not distinguish them, so all the parameters will be in the output.
For example, the most famous procedure -- call QXMLSERV.iPLUG512K(?,?,?,?)
Its parameter list is --
        [ipc, IN, CHAR],
        [ctl, IN, CHAR],
        [xmlIn, IN, CLOB],
        [xmlOut, OUT, CLOB],

When we run execute() against it.
Previously the output array has 1 element - the last output parameter xmlOut.
Now all the 4 parameters will be in the output array!


Explore: How to implement DSS with classical snap

Why it needs to get done
We plan to use classi snap for DSS because it needs to install other snaps like Microk8s, juju and juju-wait.
What needs to get done
Research:

how are classic snaps written
how to install, upgrade, delete other snaps with classic snap
examples of other classic snaps
how to run python cli in classic snap

When is the task considered done
We will understand how to write proper classic snap.

At the end we decided to go with 2 snaps setup where we don't need classical snap. 1 snap will be for Microk8s and one for DSS.


DRILL-6575: Add store.hive.conf.properties option to allow set Hive properties at session level

Details in DRILL-6575.

@vdiravka could you please review.

@vdiravka thanks for the code review. Addressed code review comments.


Move inline JS

TODO:

[ ] inline GA tracking events

I move GA track events too, but I'm not sure it's right or if it even works.

+1, what I was thinking


workflowgenerator.load should add steps to the steps_library

Instead of replacing them.

And warn if there is a step with a duplicate name.


feature: add a /showcase url

The /showcase url on tailcall takes a config query parameter.
curl https://tailcall.run/showcase/graphql?config=http://abc.com/tc.graphql

The config parameter takes a link to the GraphQL file and runs a GraphQL server in that context.
Technical Requirements

Similar code is written cloudflare/handle remove it from there.
Ensure unit tests are added.
All error messages while validating should be returned as a JSON response.
Add a feature flag in @server(showcase: Boolean) to configure the feature enablement.

/bounty 200$

may I try?

Can I get assigned this ?

should it merge configs or keep it standalone?

I would like to work on this 👀

I'm also interested.

would like to work on this


Bot is not releasing duplicates

Expected Behavior
Bot releases duplicates of pokemon caught with lower CP
Actual Behavior
Bot keeps all pokemon
Steps to Reproduce
Catch 2 of the same pokemon and see if it transfers
Other Information
OS: Ubuntu 16.-04
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here) 18f232bffb8df487654e6c52ff3eea859a120925
{
    "max_steps": 5,
    "mode": "all",
    "walk": 4.16,
    "debug": false,
    "test": false,
    "initial_transfer": false,
    "location_cache": true,
    "distance_unit": "km",
    "reconnecting_timeout": 15,
    "item_filter": {
      "1": { "keep" : 100 },
      "101": { "keep" : 10 },
      "102": { "keep" : 30 },
      "103": { "keep" : 30 },
      "201": { "keep" : 30 },
      "701": { "keep" : 100 }
    },
    "evolve_all": "NONE",
    "cp_min": 300,
    "use_lucky_egg": false,
    "evolve_captured": false,
    "catch": {
      "any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
      "// Example of always catching Rattata:": {},
      "// Rattata": { "always_catch" : true }
    },
    "release": {
      "any": {"release_below_cp": 0, "release_below_iv": 0, "logic": "or"},
      "// Example of always releasing Rattata:": {},
      "// Rattata": { "always_release" : true }
    }
}

Why do you expect it to release duplicates? Currently, it releases pokemon based on the release block

if I recall correctly, this bot released duplicates previously
On Wed, 27 Jul 2016, 8:35 PM Victor<EMAIL_ADDRESS>wrote:

Why do you expect it to release duplicates? Currently, it releases pokemon
based on the release block
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PokemonGoF/PokemonGo-Bot/issues/1181#issuecomment-235571560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIC5J9HRBgfPxJ-FePdTcu77bZpy_P0cks5qZ1CQgaJpZM4JWF3p
.

Please upgrade to the latest dev branch. The bot should release pokemons inside the "release" parameter.
/closed

@TheGoldenXY  I wish for it to release ALL duplicates not just teh ones i specify, i don't want to make 150 entries.

@Snorflake https://github.com/PokemonGoF/PokemonGo-Bot/pull/1302


Added levels in the game

What does this PR do?
This pull request introduces significant updates to the game mechanics, specifically focusing on the wave system for alien spawns. The main changes are as follows:
Wave System Implementation:
The game now consists of three distinct waves:
Wave 1: Introduces 10 aliens.
Wave 2: Follows after a message indicating "Wave 2 Incoming!" and introduces 20 aliens.
Final Wave: Displays a message for the "Final Wave Incoming!" and activates an infinite spawn of aliens.
Message Display:
Added stylized message boxes that appear during wave transitions, providing clear visual feedback to the player about upcoming waves.
Gameplay Enhancements:
Introduced a delay before the next wave starts, allowing players to prepare for the upcoming challenge.
Adjusted the spawning mechanism to handle both fixed and infinite waves effectively.
And high score is updating
Fixes #207

before:
https://github.com/user-attachments/assets/525a05c8-dc37-4370-bf32-42bbbd45c527
after:
https://github.com/user-attachments/assets/1562cca1-f408-471e-8662-c3f0225ad720
Type of change

Bug fix (non-breaking change which fixes an issue)
Chore (refactoring code, technical debt, workflow improvements)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How should this be tested?

[ ] Test A
[ ] Test B

Mandatory Tasks

[ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Can u add the labels which were assigned in the #207
i had worked very hard to do this can u give me lvl 3 as i kept levels in the game

can u check this pr


asyncapi.components().messages() is undefined when message ref'ed is in other file

I have in a template as follows:
{%- for messageName, message in asyncapi.components().messages() -%}
{{-messageName|log-}}
{%- endfor -%}

When executed on the following localref.yaml file:
asyncapi: '2.0.0-rc2'
id: 'urn:hello_world_publisher'
info:
  title: Hello world publisher application
  version: '0.1.0'
channels:
  hello:
    publish:
      message:
        $ref: '#/components/messages/hello-msg'
    x-protocolInfo:
      nats:
        pubSub:
components:
  messages:
    hello-msg:
      name: helloMsg
      payload:
        type: string
        pattern: '^hello .+$'

the output is:
hello-msg

But when executed on a globalref.yaml file, that references a message defined in another file, I get an error.
Content of the globalref.yaml file is:
asyncapi: '2.0.0-rc2'
id: 'urn:hello_world_publisher'
info:
  title: Hello world publisher application
  version: '0.1.0'
channels:
  hello:
    publish:
      message:
        $ref: './common.yaml#/components/messages/hello-msg'

Content of the common.yaml file is:
components:
  messages:
    hello-msg:
      name: helloMsg
      payload:
        type: string
        pattern: '^hello .+$'

The error shown is:
Something went wrong:
Template render error: (unknown path) [Line 3, Column 35]
  Error: Unable to call `the return value of (asyncapi["components"])["messages"]`, which is undefined or falsey
    at Object._prettifyError (/usr/lib/node_modules/asyncapi-generator/node_modules/nunjucks/src/lib.js:36:11)

I would expect the asyncapi.components().messages() to contain all messages, whether they are defined in the same file or in a different file.
There is a similar issue with asyncapi.components().schemas().
Using ag v0.16.0

The behavior is correct. You are iterating on components().messages():
{%- for messageName, message in asyncapi.components().messages() -%}

And your globalref.yaml file doesn't have a components section. When you call components() it returns only what's defined in the components section.
Maybe you want a method that will list all the messages your document is using? Is that what you're looking for?

Thanks for the clarification.
A list of all messages would be nice, though one can quite easily get the messages used from the defined channels.
A list of all used schemas is actually more stringent, as getting this list is somewhat complex when multiple levels of nested schemas are being used.
In both cases, the availability of such lists would mean less code in the template files.
I was actually expecting the asyncapi.components().messages() and asyncapi.components().schemas() to reflect all messages and schemas used. Whether the components are defined in the main yaml file or in a ref'ed file, should not matter.
We have e.g. separate files describing components for different functional domains, to be used by the a2s file defining the communication interfaces of an application. Usually the a2s file for the application does not define components of it's own, as it uses components from the functional domains.

I see. Let me just clarify one thing:

I was actually expecting the asyncapi.components().messages() and asyncapi.components().schemas() to reflect all messages and schemas used. Whether the components are defined in the main yaml file or in a ref'ed file, should not matter.

It should matter because the external file doesn't have to be an AsyncAPI file. It can be just a simple YAML/JSON file. Actually, this resolving mechanism is part of JSON Schema and not something AsyncAPI specific, so when we parse AsyncAPI, all the $refs have already been dereferenced. For instance:
something:
  $ref: 'somewhere.com#/components/messages/myMessage'

becomes:
something:
  description: This is the definition of myMessage
  ...

As you might have noticed, we don't have any context of where the message is coming from. And that's intenteded to work like this. This way pieces become more reusable between different specs.

I get your point.
I have solved this by defining some arrays that collect the messages and schemas in use, as I loop through the channels.

That could be done with the parser, I agree. Something like .allMessages().


Small Refactor

I realized that some parts could be written a bit better.

@avelis that was fast :+1:

@tselepakis Thanks again for the refactor! I appreciate the effort. I really need to make a release soon. :-)

@tselepakis If possible, could you update the README docs on how to use the class mixin constants?

@avelis no problem but I would like your insight on that. This pr does not introduce anything new, at least user wised. The constants are meant to be used for development purposes, in order this to be more clear we could move them outside of the class.
On the other hand, we could make them available to the users. The user will be able to define his CLEANED_SUBSTITUTE (something that is not possible for now) and set his SENSITIVE_FIELDS (something that is partially supported now, you can only extend the predefined set of sensitive fields).
In that case, CLEANED_SUBSTITUTE and SENSITIVE_FIELDS are not going to be so constant.
There is also sensitive_fields which let you extend SENSITIVE_FIELDS. If we go with that option the it would be better to drop the extend functionality (breaking change).
Thoughts?

Regarding the 'CLEANED_SUBSTITUTE' I didn't gave the possibility to the user to change it because it doesn't really matter I think, the point here is to change the value to not have it in the DB without encoding.
About the 'SENSITIVE_FIELDS' the point was to let the user extend it but not remove it (security issue appears if you do it).
I don't mind about the 'CLEANED_SUBSTITUTE' if you prefer to have '+++' instead of '*****' but I would keep the way 'SENSITIVE_FIELDS' works right now.


New button to quit ludusavi

What's your idea?
On Steam Deck one can add ludusavi as a non-steam game.  If started as such, it will be displayed without any window decorations (no frame, no maximize / minimize / close button) and can only be quit by "killing" the process.
Is it possible to have a "quit" button?

It sounds like you can hold Steam + B to exit. Are there any problems with using that?

Not at all, but I somehow feel a bit uncomfortable stopping programs like that since it is somewhat a last resort (feels like using the task manager to end a program).  But that might just be my gut feeling.  Please close if this is not an issue for you.

Gotcha. Steam+B/alt+F4/etc won't cause any trouble unless you're right in the middle of a backup/restore, so no need to worry.

Hi! I was about to create a similar issue before finding this one. Actually there is a problem with force closing games / apps on the Steam Deck: if you have two running games / apps at the same time, both are force closed (see https://github.com/ValveSoftware/SteamOS/issues/897).
I'm actually using that scenario regularly because I tend to keep my games running and just send the SD to sleep. But in that case, the saves are not synced with the cloud. For non Steam games, there is no cloud sync at all, so no backup. That's why I usually start Ludusavi before I put the SD down, make a backup, quit Ludusavi and turn of the SD. But when I do that using the Steam menu, my game is also force closed.
Of course I could just keep Ludusavi running, but on a system as limited as the SD, I'd rather free up as many resources as possible. Therefore, having a simple "Quit" button would be very nice!

I set it up so the button should only appear on Steam Deck installations (specifically, if /home/deck exists). Here's a preview with it temporarily enabled on Windows:

Wow, that was really fast! Thanks a lot @mtkennerly! Unfortunately, that didn't solve the problem described above, i. e. the game is also force closed when I quit Ludusavi with the new button. But now at least it's clear that it's not caused by the force close function from the Steam menu. I've update https://github.com/ValveSoftware/SteamOS/issues/897 accordingly. Let's see if I'll ever get a response...
Thanks again and keep up the great work! I've used other savegame managers in the past, but Ludusavi works best :rocket:


2-css_IgorFromUA - used grid

added a picture to about , a header with a logo. added a page with cards and a header. used grid.

hi @IgorFromUA I suggested several small improvements to your code. You have done a good job!

rolled back the commit and created new commits


_BV macro missing in unit test

Issue Summary
problem occurred in a unit test where I used the _BV() macro which is normally supported in Arduino sketches.
Replacing the test code with a normal shift (1UL << (x))  solved the issue.
However people might expect to be able to use the same code constructs as in the sketches / libraries,
just after #include "Arduino.h"

Is this the use of a documented or undocumented Arduino API?  My search suggests that it's not universal:
via avrfreaks.net

as far as I'm aware, _BV is only defined in the avr-libc headers. Extracted from avr/sfr_defs.h in avr-libc:
#define _BV(bit) (1 << (bit))

I'm pretty sure that _BV is not documented Arduino API. As you mentioned, it is made available by avr-libc, and also used by the AVR Arduino core, so it is de facto exposed by Arduino.h on AVR, but not guaranteed on other platforms (some might define it, but you can't really rely on this). I would even say that code should not rely on Arduino.h exposing _BV, even on AVR, and they should just include avr/sfr_defs.h or some other header that includes that directly, but I guess there's too much code that already assumes that the macro is available on AVR.
I would suggest to add an avr/sfr_defs.h in Arduino-ci with this macro, and include that from Arduino.h on AVR only, for compatibility with AVR-specific sketches.

My sense is to only prioritize this if there is some "official" (Arduino-hosted) documentation explaining it, since there are still a bunch of official functions that need implementation.

low priority indeed, as workaround is simple.
Thoughts

maybe get usage out of core Arduino code?
check how often it is used?

Is the other option here to put it behind some kind of #ifdef?  Maybe some more use cases here would sharpen the boundaries of this issue

As this issue has no reactions for 2 yrs the priority is low.  For me I try not to use the macro (as macros can have side effects).
That said, I searched the Arduino Libraries section (1.8.19) and the BV macro is used in multiple libs incl  SPI and SWSerial.
Maybe that is still a point of attention?


Ignore escaped quotes in string literals

I've merged this PR in a new repo we plan to maintain - https://github.com/thesis/vim-solidity - thanks @attente!


Additional keybindings

Bind C-l to recenter, C-v and M-v to move a page's worth of matches forward or backward.

Currently we do have an implementation of C-l, but the binding does not correctly take effect. Furthermore, the function as written does not conform to the usual behavior of C-l, which varies between successive calls.


Code Sample in JAVA?

Thanks for the lib!
Is there a code sample on how to implement mosby with conductor in java?

Not yet ...
@sirvonthomas<EMAIL_ADDRESS>schrieb am Mo., 8. Aug. 2016,
10:27:

Thanks for the lib!
Is there a code sample on how to implement mosby with conductor in java?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sockeqwe/mosby-conductor/issues/6, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjnrqHSP8laVA9-g_tmCieAsjQJS0Meks5qduh6gaJpZM4Jez_A
.

But you can have a look at code samples from Mosby repository. There are
plenty written in java, and there is no difference between using i.e. a
fragment or conductor controller. Mosby offers the same api for both
Hannes Dorfmann<EMAIL_ADDRESS>schrieb am Mo., 8. Aug. 2016,
16:47:

Not yet ...
@sirvonthomas<EMAIL_ADDRESS>schrieb am Mo., 8. Aug. 2016,
10:27:

Thanks for the lib!
Is there a code sample on how to implement mosby with conductor in java?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sockeqwe/mosby-conductor/issues/6, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAjnrqHSP8laVA9-g_tmCieAsjQJS0Meks5qduh6gaJpZM4Jez_A
.

and that said it all...a fragment is equivalent to a conductor controller! thanks!


Proposal: Stay lean, focus on iOS and Android (drop Windows and DOM support)

Me and @CHaNGeTe were discussing the future of this amazing project. We want to reconsider the multi platform support and focus on the majority, iOS and Android. This means dropping support for DOM and Windows (or extracting to separate repos). It would also be nice to drop support for Android MediaPlayer and only focus on ExoPlayer.
The main reason for this is to make the project leaner, more stable and be able to move faster.
There are a lot of people depending on this library, but just a few maintaining it. Please let us know your thoughts on this. Ideally we create a new version where we drop the support, so people can decide to stay or move towards the future of video playback! 🚀

I suggest adding audio playback to the discussion

What do you feel we gain by dropping support for these other platforms? The approach I had taken was to not put any effort into new development for the other platforms but if people submitted PRs, I'd take them. Is the main concern the example projects?
There are a fair number of people that didn't ever switch over to ExoPlayer for whatever reason, so that code needs to continue to be available in some capacity or another. No idea if there are people using it on Windows, I'm sure there are a few.
As far as audio goes, I'd love to see that dropped. I have no idea why people are using this lib for audio rather than a dedicated audio lib like react-native-track-player. The main support issue I've seen is background audio. I'm not sure if that has any video use cases, the only thing I could think of might be Picture in Picture, but probably not. Definitely don't put in any support for new audio features. I guess you could completely eliminate audio only support and tell people to switch to a dedicated audio lib.
With all this stuff, just realize that dropping support will create some headaches for people especially if they have an app that's already out there and they're not putting a lot of work into maintaining it. Suddenly they see that MediaPlayer or Windows is gone and they aren't sure what to do. Not to say don't do it, but do consider the impact it will have.

I think one of the reason that React ecosystem works is because it foucs on small targets. Focusing on android + ios + windows + exoplayer + android mediaplayer + audio having not a lot of maintainers can be an issue
In my point of view, I think it is better to freeze the project as it is right now and focus on what most people is using. Then, if some people is using it for web (the are multiple players already focusing to web) or android mediaplyer, they can create a fork of this component and from the fork a new library focusing only on android mediaplayer or web.
So, in our case (as we use it in a company project), exoplayer + IOS + Android as @jenshandersson proposed would be perfect

@cobarx I feel that if a library supports multiple platforms then they should have feature parity. Right now the library feels a bit all over the place, features are added to one platform but not others.
I agree with dropping audio only support. But background audio support is required for background video support, and I feel this is a key feature.
One way forward could be keeping the support but officially only maintaining ExoPlayer and iOS. But that wouldn't be my preferred way forward.
Proposal
Start working on a 5.0.0 version where we remove DOM, Windows, Android MediaPlayer, Audio only playback. We focus on delivering a great experience on ExoPlayer and iOS. This will allow us to easier clean up the code and repo (hopefully closing the 500+ issues). We keep a consistent interface between the platforms.
Freeze 4.x and allow people to keep using it. This way people who use Windows and DOM can keep using the lib. (We could consider releasing new versions for bug fixes etc?)
Thoughts? (or just leave a 👍if you like this proposal)

@jenshandersson wait, what? don't drop the audio only playback

@gazedash this is just a discussion right now :) Can you please explain why you'd use a video library for audio playback? Instead of eg react-native-track-player like @cobarx suggested above.
Since we still need background audio for background video, maybe we might as well keep the audio only playback? (ping @cobarx @CHaNGeTe )

Here's my recommendation:
react-native-dom
React out to Vincent Remier over at react-native-dom and see if he'd like to fork the repo and maintain a copy of the video player for DOM uses as something like react-native-video-dom. There's probably very few people using this (I built it for a project that we didn't end up taking to production) so I doubt it will be missed.
Android MediaPlayer
Because there are a fair number of people using this, there needs to be some kind path where people can keep their app the way it is or gradually migrate over. Fork this into react-native-video-legacy and let someone who wants to maintain it take it over. Actively work to address issues where MediaPlayer has advantages over ExoPlayer so that code branch can fade into obsolescence.
Windows
It would be pretty nice to be able to support all of the major React Native platforms. React out to someone at Microsoft and see if they have anyone on their team who would be interested in helping to maintain this. I can talk to people within our org and see if we have any connections over at Microsoft or Windows dev who might want this role. If nobody steps up, fork it off.
Note:
I think there is a lot of value in supporting tvOS and Android TV, so those should still be officially supported platforms. Many of the apps I've worked on would love to have TV support. To get large corporate & Silicon Valley apps to adopt react-native-video this needs to be there.

Just got a notification from this thread which reminded me that some people have issues with expoplayer and fall back to the Mediaplayer.
https://github.com/react-native-community/react-native-video/issues/1628
Stuff like this should get addressed before removing Mediaplayer.

@n1ru4l you linked this same issue

I meant https://github.com/react-native-community/react-native-video/issues/1318 sorry.

This project is impressive, and important. He must not die and continue to evolve.
But currently this project is completely overwhelmed by bug reports.
Any proposal that will bring stability and accelerate progress is welcome.
Some bugs are more than 10 months old and are quite relevant. Where a solution could have been proposed during the week, the delay is abnormally high and blocks many javascript developers (they can't contribute if they are not native experts). Unfortunately, and hopefully, the community has nothing as good as this component and therefore remains blocked when their issues are not resolved in month.
I fully understand that an open source library is developed by people on their free time. And I also understand all the difficulties involved in having to satisfy an open source community on a project as central as it is necessary.
So I completely agree with this proposal and I hope that it will be able to attract new contributors at the same time as it will make this library stable.
I'm not a native English speaker, if some of my sentences are rude, it's not on purpose. Sorry in advance if it's the case.

Android MediaPlayer does seem like it falls into the legacy category and it'd make a lot of sense to deprecate with the next major version.
It'd be nice to keep windows support active but without an active maintainer, it does seem like it could slow down the rapid evolution of the core platforms.
Regarding ios and android support, I agree with what others have said it'd be great to continue supporting advanced features like audio only, background playback, etc. I've been thinking about a plugin/extension system that could make such features optional. This could also help with some of the less popular platforms where only "core" would be supported but only some of the extensions would be implemented.

As far as audio goes, I'd love to see that dropped. I have no idea why people are using this lib for audio rather than a dedicated audio lib like react-native-track-player. The main support issue I've seen is background audio. I'm not sure if that has any video use cases, the only thing I could think of might be Picture in Picture, but probably not. Definitely don't put in any support for new audio features. I guess you could completely eliminate audio only support and tell people to switch to a dedicated audio lib.

Our app relies on react-native-video for audio only, video and background playback and can switch from audio only to video. Using the same library to power all these experiences is a major win.

So, there's ny final decision about this topic? I think it is, probably, one of the most important topics to discuss about and find a proper solution ^_^

I vote for keeping it simple supporting only iOS and Android and only video related stuff.
We are using this library for playing video streams, have to use another one for YouTube videos and another for video controls and its overhelming.
However you could keep this focused and suitable for all video playing cases with great performance, stability and so on.
P.S. When you type "react-native video player" you always get here. And semantically when people type "react-native" they are looking for mobile specifics ;-)

Hey guys, what do you think on autolinking exoplayer version for RN > 60.
I think it makes more sense than android
https://github.com/react-native-community/react-native-video/issues/1747

This issue has received a lot of feedback now so I'd like to propose a few concrete next steps:

Aggressively triage old issues and PRs. For PRs, close duplicates and ask the developer if they'd like to bring the PR up to date with master.
Start merging PRs for minor bugs and feature improvements. Release every change to 5.1-alpha.
Target a 5.1 release within ~1 month, say by end of October. Peloton will be committing dev time during work hours so this should be more than achievable. 5.1 will be the last release with windows, dom and android MediaPlayer support. If there's support for it, we can continue releasing critical bug fixes for those platforms on 5.1.x.
Remove support for windows, dom and android MediaPlayer from the repo, release 6.0.

Unless there's any major pushback, we'll start working on 1. and 2. next week :).

I am placing PRs (merging them, but not releasing them) to master, by now Changelog entries are set to next

+1 for not removing audio only. Lots of blogs linked me here and I tried other packages and none were as easy to get up and running

With regards to autlinking
".. Hey guys, what do you think on autolinking exoplayer version for RN > 60.
I think it makes more sense than android .."
I find that autolinking in both react-native-community/cli and
in react-native-unimodules   is completely broken for non-trivial monorepo projects
In monorepo projects location of package.json is not just ../../   compared to the android app location.
Instead it can be at a parent or sibling directory, and there are more than one node_modules (some times).  There is also not a 'standard' MainApplication.java where the list of packages can be 'injected'.
These two projects ( react-native-community/cli and react-native-unimodules ) made some efforts to accomodate monorepo projects, but enough enough to make support working. Instead builds break right away, require days of troubleshooting, and then at the end packages under autolink 'spell' cannot be used.
So if anything, the autolinking thing  would be a step back.
Truth is, probably, that  automatic discovery and linking that works for RN universally, require a formalized build system like 'webpack' or metro in level of complexity, and it is simply unattainable with the effort that one or two package maintainers can put into it.

I'd like to argue against deprecating MediaPlayer support on Android.
There remain several issues with the newer ExoPlayer, particularly with older Android devices, most of which are probably issues with this project's implementation rather than ExoPlayer itself.

As @n1ru4l mentioned, ExoPlayer straight up doesn't work in some cases (#1318)
Exoplayer doesn't always pick up the correct orientation on older Android devices (#1213, #842, #808). This seems to be an issue with Android itself, as you see a lot of StackOverflow issues on this subject
The current implementation of android-exoplayer doesn't support returning the video's real dimensions (#1530). Currently the naturalSize reported by onLoad is just pulled from the on-screen React container's dimensions, in contrast with the MediaPlayer approach where it is sourced from the actual video. ExoPlayer does support pulling the dimensions from the video, but it's a bit more complicated. This matters in particular because on older Android devices, the system media APIs can returns incorrect dimensions, and the EXIF information can be unreliable. @react-native-community/cameraroll and expo-media-library both have this issue

It's worth noting that ~10% of Android users are still on Android 4.4 or earlier. When you scope to people in the West using apps like Peloton, of course that number will be much smaller. But for a lot of people in the developing world, React Native's ability to support older Android devices is crucial. If react-native-video stopped being viable for the developing world it would be a huge hit for the React Native ecosystem as a whole.

When analyzing an AAB I saw some files related to shaka-player from the DOM version that get bundled in Android app, probably iOS as well, didn't check yet.

👋 Hello from the React Native team here at Microsoft! We have been actively working with Facebook to make Windows a "1st class citizen" alongside Android and iOS. This is obviously a work-in-progress, but one that we're committed to with our friends at Facebook.
To that end, we have updated the RN for Windows platform to leverage high-performance C++ ("RNW vNext"). Now that the RNW vNext supports native modules as a platform, we have identified several key native modules to add Windows support for (including react-native-video) to help validate that the platform has the right set of capabilities and to bootstrap the community of modules that target Windows.
To that end, we have developer resources here at Microsoft to update react-native-video's Windows implementation to the latest version of React Native for Windows. We're also tracking this work here: https://github.com/microsoft/react-native-windows/issues/2095
Our hope is that Windows support is not removed from react-native-video, as this module is very important for React Native developers including those that target Windows.

if there's resourcing to actively support the package I see no reason to drop windows support. Especially since we've failed to execute on a lot of the idea described earlier in this thread. The more active developers, the better at this stage :).

In android media player support should be dropped and only exoplayer should be focused for. Windows support should be there but moved to seperate branch and added only if required. A lean video playback will DRM, custom ui and quality improvements to keep it updated with latest version of the player is most important.

What is the status on this proposal?

At the time of writing this proposal I was very excited to fix this project, but unfortunately there wasn't great support in streamlining it. Best way forward might be creating a streamlined fork of this library, focusing on the core video experience. Will close this issue as I'm not the person to lead this, but if there's interest in helping manage/maintain this just re-open.


Dyson eye 360 cleaning map not shown / empty

Core
2023.11.2
Supervisor
2023.11.3
Operating System
11.1
Frontend
20231030
Dyson add on latest

Hmm, interesting. This is an area of the integration that doesn't get a lot of attention these days.. Could you enable debug logging for the integration and share the logs here?

I saw something similar with the 'other' Dyson integration - it seems someone managed to work it out:
https://github.com/shenxn/ha-dyson-cloud/issues/2

Interesting! I'll reach out to @condor872 and see if we can integrate his solution here. Thanks @iMiMx!

Update: @condor872 has replied on https://github.com/shenxn/ha-dyson-cloud/issues/2, we may have a working solution for this soon. :crossed_fingers:.

Can't wait for this to be implemented. does this also include the ability to send the vacuum to only clean the selected zone(s)?


Outliers management

Sometimes it looks like sensor picks up only outliers. There was a print there instead of a logging statement, so it didn't leave any trace, but here's what I assume to be the chain of events:

Sensor starts freaking out, values are ignored
PID value stays the same for a while, keeping the temp increasing or decreasing
Sensor comes back to normal, but values are now all outliers and ignored

This is supported by the fact that, when temp is going too hot, venting steam and running water will usually get the temperature to catch up to where it was when the sensor started acting out. Normal operation then resumes.
For now we'll accept outlier values, but stop the machine if we get 50 of them. Unsure whether that will ever happen since it'll update the average, but at worst it should act out temporarily and log what happened, at best everything will be roses and sunshine.

Changed definition of outlier to a temperature under 0 or over 200. Will accept values otherwise. This'll permit the program to pick back up where it left whatever the current temperature is when the probe amplifier starts freaking out. Still want to shut off heating during such events. Turning it back on will have to be manual with the toggle button.
New sensor ordered. Will try to split temperature up into a temp part and a sensor part.


GitHub display ordering

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Is your feature request related to a problem? Please describe.
When the directories are submitted, they would be ordered on GitHub by the string ordering rather than natural ordering. For example, this is the order that we see:

Describe the solution you'd like
Perhaps it could instead be written with prepending 0's, such that it would go:

0001-two-sum
0002-add-two-numbers

etc.
Describe alternatives you've considered
If the numbering doesn't matter, then maybe it could be removed overall and a table of number to problem could be created/updated in the README.md
Additional context
Add any other context or screenshots about the feature request here.

duplicate of #229


Ambiguity not evident in nearley-test output

I have a grammar producing multiple parsings of an input, implying ambiguity, but when I run nearley-test on the input, it outputs two identical parse trees. That doesn't seem correct to me; shouldn't the parsings differ if there's more than one way to parse the input? Thanks!

Not necessarily — if you are using empty "null" rules, then all sorts of bad things can happen. As a simple example,
a -> null "a" | "a" null

is ambiguous with input "a", as shown:
$ nearley-test -i a <(nearleyc <(echo 'a -> null "a" | "a" null'))
Table length: 2
Number of parses: 2
Parse Charts
Chart: 0
0: {a →  ● "a"}, from: 0
1: {a →  ● "a"}, from: 0

Chart: 1
0: {a → "a" ● }, from: 0
1: {a → "a" ● }, from: 0

Parse results:
[ [ 'a' ], [ 'a' ] ]

Another possibility is that you are using postprocessors to map different "raw" trees to the same output. You can compile grammars with the --nojs option to disable them and see these "raw" trees, which should differ.

Of course, the nulls! Thanks for the clear and quick answer. I don't have any explicit nulls in my grammar but they're implicit in lots of ? and * rules.
I had already deleted the postprocessor logic to make sure that it wasn't obscuring the answer (the nojs flag throws away my lexer so I can't use that).
Some way to see which rule exactly is where the parse "forked" would be extremely helpful.

Of course, the nulls! Thanks for the clear and quick answer.

Glad I could help. :-)

Some way to see which rule exactly is where the parse "forked" would be extremely helpful.

We think so too! I'm not sure if it's captured in an issue anywhere, but this is definitely something @Hardmath123 and I are thinking about.


Fix pgen

Change short name for --enable-clock to avoid collisions with other arguments (certificates).
Fixes crash when running pgen aka generate-policy

Nothing seems to call pgen with short arguments.
I haven't run the tests, will wait for the CI.

This is failing due to openssl-sys updating earlier today and bumping the MSRV.  You will need to wait until #266 is merged.


too many citations for GRaF R package

Apparently this package of mine has picked up four citations for a 90's spectrograph (that I never knew existed): http://depsy.org/package/r/GRaF

whoops!  Thanks for letting us know :)  Will work to fix it.


Update trace4cats-exporter-common, ... to 0.12.0-RC1+191-347e4fc7

Updates

io.janstenpickle:trace4cats-exporter-common
io.janstenpickle:trace4cats-model
io.janstenpickle:trace4cats-testkit

from 0.12.0-RC1+156-7ea07b63 to 0.12.0-RC1+191-347e4fc7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.janstenpickle" } ]

labels: library-update, semver-build-metadata

Superseded by #10.