[2.3.2] Always unauthorized using sessionToken from user (request.user)

Issue Description
My instance of Parse Server always error out with error "ParseError { code: undefined, message: 'unauthorized' }" when using find({sessionToken: }). The session token is retrieved with "request.user.getSessionToken()".
Steps to reproduce
var token = request.user.getSessionToken(); // it is not null
var query = new Parse.Query(MyTable);
query.find({sessionToken: token}).then(function(results) {
...
});

Expected Results
No error
Actual Outcome
ParseError { code: undefined, message: 'unauthorized' }
Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : 2.3.2
Operating System:    Ubuntu 14.04 LTS
Hardware:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                6
On-line CPU(s) list:   0-5
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             6
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 63
Stepping:              2
CPU MHz:               2499.980
BogoMIPS:              5001.29
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              4096K
NUMA node0 CPU(s):     0-5
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Linode

Database

MongoDB version:  3.0.8
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): Local to the same machine

@contervis do you have any CLP (Class Level Permissions) configured to this class?

@NatanRolnik The specific class involved in the issue has public READ and WRITE access level.

I have the same problem since I attempted to upgrade yesterday. Last known good version for me (using sessionToken) was 2.2.23.

Also having the same problem after upgrading this morning.

Can you provide the logs when runnjngn with VERBOSE=1?

We are also having this issue. We get the same error when running Parse.User.logInWith('facebook', {authData})
It seems to be an issue introduced in 2.3.0. We were previously on 2.2.22

as much as I would like to help, can you please provide the logs when running the server with VERBOSE=1 please? Without it, there isn't much to be done.

Yes, of course, sorry. This is the output when running Parse.User.logInWith('facebook', {authData}):
  express:router dispatching POST /parse/users +6s
  express:router query  : /parse/users +3ms
  express:router expressInit  : /parse/users +2ms
  express:router trim prefix (/parse) from url /parse/users +1ms
  express:router mounted_app /parse : /parse/users +0ms
  express:router dispatching POST /users +6s
  express:router query  : /parse/users +1ms
  express:router expressInit  : /parse/users +0ms
  express:router allowCrossDomain  : /parse/users +1ms
  express:router router  : /parse/users +0ms
  express:router dispatching POST /users +1ms
  express:router urlencodedParser  : /parse/users +0ms
  body-parser:urlencoded content-type "text/plain" +0ms
  body-parser:urlencoded skip parsing +2ms
  express:router router  : /parse/users +2ms
  express:router dispatching POST /users +1ms
  express:router router  : /parse/users +0ms
  express:router dispatching POST /users +0ms
  express:router jsonParser  : /parse/users +1ms
  body-parser:json content-type "text/plain" +2ms
  body-parser:json content-encoding "identity" +1ms
  body-parser:json read body +0ms
  body-parser:json parse body +14ms
  body-parser:json parse json +0ms
  express:router allowCrossDomain  : /parse/users +15ms
  express:router allowMethodOverride  : /parse/users +1ms
  express:router handleParseHeaders  : /parse/users +0ms

Please let me know if you need anything else.
Appreciate the help!

This is now solved!
Saw this issue https://github.com/ParsePlatform/parse-server/issues/3577, and I had done something similar. Previously I had configured my cloud code with 'unused' as the JAVASCRIPT_KEY, but this does not work anymore. So now I supply the configured JAVASCRIPT_KEY in my cloud code. I thought I could leave it empty or null, but that does not seem to work.

so @johanarnor everything works for you?

@flovilmart yes!

That's great to hear!
@contervis, I'M not sure if you jumped between 2.2.23 and 2.3.4, but can you try it out?

I can confirm that this does seem to be an error with the logic introduced in e788d49
When I upgrade my project from 2.2.23 to 2.2.24, some cloud code using user.login() and a subsequent user.getSessionToken() breaks and throws the following error: error: Error generating response. ParseError { code: 141, message: '{"message":"unauthorized"}' } code=141, message={"message":"unauthorized"}.
javascriptKey was never configured previously, but when I include it in the new ParseServer() initialization, everything starts working as before the 2.2.24 upgrade.
As far as I know the javascriptKey argument is intended to be optional so this seems to be a bug @flovilmart .
Thanks a ton @johanarnor @contervis and @oliverchoy et all, this was annoying to debug and you guys helped a lot!

javascriptKey is not optional if you are using javascript, e.g. cloud code. It should be safe to omit if you are just connecting to parse-server to perform queries from a REST or .Net client for example.
The change in 2.2.24 is to enforce key security correctly. Previously if any key was omitted then none were checked, which removed the point of having keys and which led to an undesirable workaround of having to specify unused keys if you wanted key security.
You should be able to remove all client keys from config if you want to disable key security, although I've not tried how this works with cloud code.
This change does seem to cause a lot of issues so perhaps the documentation needs an update?

Yeah, I think we should just update the documentation if that's the case, so people are aware that they'll need javascriptKey configured if they plan to use cloud code.

So my understanding at this point is
If you want to use cloud code, you can either:
a: use no client keys
or
b: configure javascriptKey if any client keys are in use
You cannot use any client keys without configuring javascriptKey if you want to use cloud code.
Does that sound right?

Yes, that sounds right.

Yes.
And can confirm @johanarnor final point: values for keys that are not configured in the constructor are also ignored.

Let me understand, in this scenario can I continue use the same code just by adding the javascriptKey?


Hello I wanted to get in touch, before I do something ..

I am looking for an opportunity to start contributing to an open source project and I chose you project, because I like it, I understand it and there might be something to help out on. As a first task, I decided to remove the print statement: there is one in your code, that I think is not supposed to be there. I forked the repo and deleted the statement in a new branch, I will send you a pull request, if you do not mind and I would also don't mind to put the docu into Spinx for you as a next try to contribute something.
This is the print statement in your code:
def validate_required():
def required_validator(field, data):
print('checking', field.name, 'with', data, 'and', field.value)
if not field.value:
raise ValidationError('required')
return required_validator
I am sure you can easily fix this yourself, but would you mind, if I send you my pull request? I feel like a newbie to open source and hope I am doing things right to get started, otherwise, please tell me.

Hi! Thanks for the message. Please do feel free to send a pull request if you'd like. That print statement was in there for debugging purposes.

Closed by #2


I want to be able to use ClusterConfigTemplates in Delivery

Description of problem
As per the RFC, a config is a useful input type which means we need to support ClusterConfigTemplates in the Delivery CRD

@sclevine In the RFC we see mention of config[], source[] -> <something> which is why I took it as implied that we need to support ClusterConfigTemplates.
Was that your intention?

returning to pre-ipm until we hear from @sclevine


Sntiches aren't refreshed while in vehicles

Needs further testing, players moving in a vehicle trigger the same code as players walking into fields

is the player position updated while moving in a vehicle? iirc while in certain vehicles the player position stays at where they entered the vehicle, and only the vehicle entity position is updated; only when the player exits the vehicle is the player position updated to the exit location. if this is still true, a fix would be to special-case players in vehicles and using the vehicle location instead of the player location for checking snitch ranges.

See: https://github.com/CivClassic/JukeAlert/issues/53. Original issue by KaloHG claiming boating did not refresh their snitches. Metriximor theorized it may be because vehicles have a different entry event.
Definitely needs testing as it is very possible KaloHG was mistaken. At one point /jalist was not updating live and so a refreshed snitch did not show as refreshed until the next day, so that could have been the cause.

Requesting someone to actually reproduce this, looking at the code I'm relatively sure it should work. Metriximor's analysis in the original issue is wrong, he's looking at the wrong place.

Issue was created before a ton of performance improvements and optimizations to JA by Orinnari, plus no replication of issue


Add support for HTTP status code: 423 Locked

Add support for HTTP status code: 423 Locked

@nasaabg @fstech/sell-billing I can not add you to Reviewers in this repo. Can you take a look and you can give me an approval using a comment :)


llvmPackages_16: 16.0.1 -> 16.0.5

Description of changes

Bumped the default.nix version to the latest point release.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

@alyssais nothing in particular, I've just never had a PR on llvm before and didn't want to jump the gun before someone looked at it!

Separately, @RaitoBezarius, based on #235216, looks like keeping emscripten up to date will occasionally require more backports from LLVM tip to stable. This PR won't get 3.1.40 working, but hopefully the next point release will.

@RaitoBezarius as noted in #235216, I spoke too soon -- while 3.1.39 built fine already, further attempts to use it and build other things on staging ran into some LLVM issues. I think the backports from 17 to 16 will be necessary to stabilize that for staging, and those are themselves dependent on this landing, so I think this is ready to go now.
For whatever it's worth, emscripten's policy is only to target tip-of-tree LLVM. Keeping llvm_git perpetually up to date just for emscripten strikes me as more challenging than occasional backports. I tried to note that these particular patches are for emscripten -- once the new version stabilizes and emscripten moves on, I think they can be removed. I did submit a backport request which might land in LLVM 16.0.5, but the emscripten maintainers did note that they're skeptical that LLVM will want to include new flag functionality in an old stable branch.

@OfBorg build llvmPackages_16

Bumping to 16.0.5, which was just released and will be the final point release on the 16 branch. This will unblock #235216 once landed.
Also, retargeting to staging-next to try to catch the #235556 train. Could also retarget to master, but it'd be good to unbreak what's a little broken with emscripten 3.1.39 on staging-next.

Uh, I was too trusting.  It won't apply patches, let alone build and work.

Reverted for now.  Changes like this can go directly to master, by the way, but they should get at least some basic testing before merging.

Apologies — I didn’t do a full rebuild on staging but I can say that this did build locally for me when testing on top of master, at least for Darwin. Will figure out what broke and submit a new PR with fixed patches.

I don't expect the branch changed that, but this amount of rebuilds is small enough to merge directly to master and avoid such complications.

New version of this on #235624 to address the need for revert.


MaterialDesignExtensions 3.3.0 has a resource with the locale 'Ru'

Severity	Code	Description	Project	File	Line	Suppression State
Warning	NETSDK1187	Package MaterialDesignExtensions 3.3.0 has a resource with the locale 'Ru'. This locale has been normalized to the standard format 'ru' to prevent casing issues in the build. Consider notifying the package author about this casing issue.	Jem.WpfCommonLibrary22	C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets	267

Same here:

warning NETSDK1187: Package MaterialDesignExtensions 3.3.0 has a resource with the locale 'ru-ru'. This locale has been normalized to the standard format 'ru-RU' to prevent casing issues in the build. Consider notifying the package author about this casing issue.

Hi, just created a PR for this as it's been bothering me as well for a long time...


Update Django compatibility to 4.1 - 5.1

This PR won't pass until the django-hawk package has a deployed version that supports Django 5.1
https://github.com/uktrade/django-hawk/pull/18/files

It looks like Django 5.1 is failing for this package at the moment


Query the database at job execution time vs job queue time when updating attributes on Asset Manager assets

Currently all the ServiceListeners::AttachmentXxxxUpdater classes queue up jobs using the AssetManagerUpdateAssetWorker which accepts a Hash of attributes which are determined at the time the job is queued up.
If we're going to re-use the logic in these updaters to update the attributes of all existing Whitehall attachment assets in Asset Manager, I think we're going to want to determine the attributes at job execution time. This is because we might be queueing up millions of jobs and it might be a long time before the ones at the back of the queue are executed.

The attachment listeners/workers have been updated so that we only store an AttachmentData.id on the queue and look up the attributes at the time the job is processed:

Move AttachmentAccessLimitedUpdater logic to a worker
Move AttachmentDraftStatusUpdater logic to worker
Inline attachment link header updater logic into worker
Extract AttachmentRedirectUrlUpdater logic into worker
AttachmentReplacementIdUpdater queries required data when job is executed
Delete assets in Asset Manager when attachments are deleted

I'm not sure it's easy/possible to really validate this is working as expected in production given that it's an internal change. So I'm going to close this issue.
@chrislo / @floehopper: Feel free to re-open it if there's more testing you want to do.


[BUG] URL bug when compressing video (both platform)

Hello, thank you for great library. I'm trying to compress video from my phone, and it stucks with this issue showed in Xcode, and it seems a similar problem on Android as well. Here is my url: "file:///private/var/mobile/Containers/Data/Application/4C481244-1158-49F8-8C2E-63820626912E/tmp/react-native-image-crop-picker/DBEA92DF-CF1A-424C-BD55-479DAE1F7A5C.mp4"
https://imgur.com/a/7mTWe0W
Any ideas guys ?

Hi @dangkhoa2708 ,
Please specify versions that you're using and the issue that you faced with.

I'm using the lastest version, here the error I got from Xcode, sorry just posted the wrong one


:bug: Handle editable pip installs

What kind of change does this PR introduce?
Handle editable pip installs in Pinned-Dependencies check.
Description
When performing pip install -e <pkg>, the install can be considered secure if the package and it's dependencies are hash-pinned. The package can come from a local or remote source (VCS install). If the package is local, it is considered secure. If the package is remote, it needs to pinned by commit hash to be secure. We have no way to identify if the dependencies installed from requirements are hash-pinned. The flag --require-hashes does not work with -e flag. To guarantee we are not installing malicious dependencies, we can use --no-deps flag to not install the dependencies. That way the install can be considered secure.
Examples

secure
pip install --no-deps -e git+https://github.com/username/repo.git@0123456789abcdef0123456789abcdef01234567#egg=package"

secure
pip install --no-deps -e .

not secure
pip install -e git+https://github.com/username/repo.git@0123456789abcdef0123456789abcdef01234567#egg=package"

not secure
pip install --no-deps -e git+https://github.com/username/repo.git#egg=package"

References

pip install syntax: https://pip.pypa.io/en/stable/cli/pip_install/#pip-install
secure pip install: https://pip.pypa.io/en/stable/topics/secure-installs/#do-not-use-setuptools-directly
what is editable pip install: https://setuptools.pypa.io/en/latest/userguide/development_mode.html
pip VCS install syntax: https://pip.pypa.io/en/latest/topics/vcs-support/#vcs-support
https://github.com/pypa/pip/issues/4995

(Is it a bug fix, feature, docs update, something else?)

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
Currently, we don't handle editable pip installs. We suggest using --require-hashes as remediation but it's not possible.
What is the new behavior (if this is a feature change)?**

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
Closes https://github.com/ossf/scorecard/issues/2228
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

Accept pip installs with `-e` flag along with `--no-deps` flag in Pinned-Dependencies check. Editable pip installs will be accepted if coming from a local source or a remote Git source pinned by hash, as long as it's not installing dependencies.

Please rebase and we'll be able to merge.


[TemplateFlip]  -> [HTML & CSS Templates]

Hi,
I found this resource useful for   all community members. Regards
https://templateflip.com/templates/

Hi Alaev,
I found this resource also useful for all community members. Regards
https://www.bootstrapdash.com/product-category/free-bootstrap-admin-templates/

Why did you removed the templateflip link?

Hi Stefan, sorry for the confusion. In fact, I had two additions. No removal.. First one is Templateflip, the second one is Bootstrapdash.

Ok, please add the other resource and remove table of content link.

@cetinogut

Closing.
Not 100% free.


Decimal negative zero coefficient/exponent fixes

Addresses the following issues related to Decimal coefficients and exponents with value -0:

third-party BigInteger.sign is supposed to be true for negative numbers, but sign is false for BigInteger(-0) and BigInteger('-0');  constructing BigInteger(0) and calling negate() achieves the desired behavior
BinaryWriter.writeDecimal() was producing an unnecessary byte when the coefficient is (+)0
BinaryWriter.writeDecimal() special case for 0d0 was also (incorrectly) catching decimals with a 0 coefficient but non-zero exponent
Decimal.stringValue() wasn't including - for negative coefficients and exponents

Resolves #289
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@zslayton It is considered bad style/bad practice to extend native types:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Inheritance_and_the_prototype_chain#Bad_practice_Extension_of_native_prototypes
@pbcornell The impl that wins with Number.sign() is the last one that is defined. Change the order of the definitions and you'll change the impl of Number.sign().


Unnecessary conversions between [UInt8] and ByteBuffer

Describe the bug
When decoding a multipart buffer using FormDataDecoder you generally start with a ByteBuffer. FormDataDecoder forces you to convert this to [UInt8] which then it converts back to a ByteBuffer internally inside MultipartParser.execute. This is causing unnecessary data copying.
Expected behavior
Add
FormDataDecoder .decode<D: Decodable>(_ decodable: D.Type, from data: ByteBuffer, boundary: String) throws -> D

which uses ByteBuffer version of MultipartParser.execute.
Set other versions of FormDataDecoder.decode to use this new version

I can do a PR for this if you want

@adam-fowler that would be great thanks!


Critical rule 1 still doing too much damage

In the example I am firing a +1 shortbow with 14 dex, I should be doing 1d6+6+3 but instead I am doing 2d6+6+3.
The mod version is <IP_ADDRESS>

Tried another fix. In dev


Create data API for adding listbox widget to select

something like select2, but Im not sure. What shell we use?

Select2 was used...


fix: Support parameter that contains semicolon(":")

May I ask why you've added hour12: false to the getErrorMessage method?

May I ask why you've added hour12: false to the getErrorMessage method?

Hi @mattkingshott , when I ran the test locally, one of the test cases failed and I found out that it was caused by inconsistent date formats.

I see. I'm not sure if that would be a breaking change given that people might be performing assertions based on the output of the error message. It should probably be a major version bump.

Released in version 5.0


[AST] Move getEffectiveAccess calls into SIL.

@swift-ci Please smoke test.

This will conflict with https://github.com/apple/swift/pull/10380, can you wait until @swiftix checks that in? Also I think isConformanceSerialized() is a better name than isConformanceFixedLayout().

@swift-ci Please smoke test.

@swift-ci Please smoke test and merge.

@swift-ci Please smoke test.

@swift-ci Please smoke test


spiderfied event not firing

I am using following code to create a markerClusterGroup and then trying to bind to its spiderfied event,
let markerClusterGroup = L.markerClusterGroup({
                        showCoverageOnHover: false,
                        chunkedLoading: true,
                        zoomToBoundsOnClick: true,
                        iconCreateFunction: (cluster) => {
                            return L.divIcon({
                                html: '<span style="background-color:yellow">' +
                                    cluster.getChildCount() + '<span>',
                                className: 'cluster-icon',
                                iconSize: L.point(120, 120)
                            });
                        }
                    });

                    markerClusterGroup.on('clusterspiderfied', (cluster, cMarkers) => {
                        console.log('spiderfied'); //This statement not executing
                        console.log('Cluster markers', cMarkers); //This statement not executing
                    });

The event 'clusterspiderfied' is not firing at all.
So I wanted to ask if anything I am missing or doing wrong. Please help.
Thanks.

Leaflet version I'm using: 1.2.0
Leaflet.MarkerCluster version I'm using: 1.3.0
Browser (with version) I'm using: Firefox 61.0
OS/Platform (with version) I'm using: Windows 10

https://github.com/Leaflet/Leaflet.markercluster#additional-markerclustergroup-events
that isn't the event name


iModel Upload,outdated file

@Josh-Schifter

I am a novice. I have some problems when I register the project. Can you teach me，Thanks

The upload only supports the iModel 2.0 format.  The error suggests you are using an older format.  See this page for instructions on how to create iModel 2.0.

@maoyankandanteng if you have any follow up questions/issues, please open a new issue.


#EXT-X-DISCONTINUITY not being looked for when parsing file

It looks like when parsing an m3u8 file the check for the #EXT-X-DISCONTINUITY line is missing.
I'll create a pull request if this turns out to be the case.
Apart from this issue it's been working perfectly for us so thanks!
Our related issue: https://github.com/LA1TV/M3U8-Parser/issues/1

Closed by #13. Thanks!


Improve readability of WASM testsuite definition

Changes:

Use sorted XML list in POM for cleaner diffs
Rename parameters for clarity on wast file vs test
Enforce that all wast files are explicitly included or excluded

This will ensure that we aren't missing any tests by accident.

If you want to merge yours first, this is easy for me to rebase. Up to you. This change should make future conflicts easier to deal with.

If you want to merge yours first, this is easy for me to rebase.

Thanks, if it doesn't take too long to have the approvals I'll try to go down this path.

@electrum please rebase and we move on with this one too, sorry for asking you to resolve the conflicts this time and thanks for your patience.

@andreaTP no problem, I rebased it


SD1.5 - mm v2 and v3 models very noisy

For some reason, it seems that the mm_sd_v15 seems to work ok, yet the mm_sd_v15_v2 and v3_sd_mm just produce a lot of noise. I´ve tried a lot of settings and models and boiled things down to the simplest possible thing: just generating one image and it still doesn´t seem to work.
Am I missing something?
https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved/assets/937467/03c849df-6f2d-4a4f-a53e-c25814cbaff0

AnimateDiff's sweetspot is 16 latents at a time. It worked by sampling all the latents at once - stray too far from the sweetspot, and you get noise (your v1 model results are also noisy due to this). Wherever you are creating/loading the latents to be passed into the Ksampler, make them 16 if not using any Context Options, or at least 16 if using Context Options.

Thanks


Drop-down are not the correct size

Some of the drop-downs are smaller then other drop-down and all the other fields:
Examples:
On deployment create, in the container tab:  Pull Policy is the only drop-down that is corecct.  All the other drop-downs are 2 or 3 pixels to short:  Here are some examples:

Comments:
This seems to be happening all over the Cluster Explorer and the other apps I install.

Fixed


MoodBot does not respond to my slack messages

Rasa Core version: '0.8.2'
Python version: 3.6
Operating system (windows, osx, ...):windows 10
Issue:
I installed the starter-pack and followed the instructions here:
https://core.rasa.com/tutorial_basics.html#tutorial-basics
to set up the rasa moodbot
I also configured slack using the ngrok https webhook.
I am not getting any response from the moodbot in slack.
So I test this:
curl -XGET <IP_ADDRESS>:5002/webhook -d '{"text":"bye"}'
This is also not giving me any response from the mood bot. However, I see
<IP_ADDRESS> - - [2018-06-12 22:10:17] "GET /webhook HTTP/1.1" 200 115 0.001003
where I run the command:
python -m rasa_core.run -d models/current/dialogue -u models/current/nlu --port 5002 --connector slack --credentials slack_credentials.yml
I also tried:
curl -XPOST http://b928f88d.ngrok.io/webhook -d '{"text":"bye"}'
I don't see anything happening at my server end.
How do I get my moodbot to respond to "hi" or "bye" from slack??
Content of domain file (if used & relevant):
intents:
  - greet
  - goodbye
  - mood_affirm
  - mood_deny
  - mood_great
  - mood_unhappy

actions:
- utter_greet
- utter_cheer_up
- utter_did_that_help
- utter_happy
- utter_goodbye

templates:
  utter_greet:
  - text: "Hey! How are you?"
    buttons:
    - title: "great"
      payload: "great"
    - title: "super sad"
      payload: "super sad"

  utter_cheer_up:
  - text: "Here is something to cheer you up:"
    image: "https://i.imgur.com/nGF1K8f.jpg"

  utter_did_that_help:
  - text: "Did that help you?"

  utter_happy:
  - text: "Great carry on!"

  utter_goodbye:
  - text: "Bye"

This is the documentation for version 0.13.7
Python version: 3.6
Operating system (windows, osx, ...):windows 10
Issue:
I installed the starter-pack and followed the instructions here:
https://core.rasa.com/tutorial_basics.html#tutorial-basics
to set up the rasa moodbot
I also configured slack using the ngrok https webhook.
I am not getting any response from the moodbot in slack.
credential.yml
slack:
slack_token: "xoxb-604774568887-613958177573-QDxG7R7y5Mp7rwICKAVFUoKI"
slack_channel: "@moodbot1"
@moodbot1 -is my app name
(rasa_stack) C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2>python -m rasa_nlu.train -c config.yml --data nlu.md -o models --fixed_model_name nlu --project current --verbose
2019-04-20 13:12:16 INFO     rasa_nlu.utils.spacy_utils  - Trying to load spacy model with name 'en'
2019-04-20 13:12:28 INFO     rasa_nlu.components  - Added 'nlp_spacy' to component cache. Key 'nlp_spacy-en'.
2019-04-20 13:12:28 INFO     rasa_nlu.training_data.loading  - Training data format of nlu.md is md
2019-04-20 13:12:28 INFO     rasa_nlu.training_data.training_data  - Training data stats:
- intent examples: 63 (6 distinct intents)
- Found intents: 'greet', 'mood_deny', 'goodbye', 'mood_affirm', 'mood_great', 'mood_unhappy'
- entity examples: 0 (0 distinct entities)
- found entities:
2019-04-20 13:12:28 INFO     rasa_nlu.model  - Starting to train component nlp_spacy
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component tokenizer_spacy
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component intent_featurizer_spacy
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component intent_entity_featurizer_regex
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component ner_crf
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component ner_synonyms
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Starting to train component intent_classifier_sklearn
Fitting 2 folds for each of 6 candidates, totalling 12 fits
[Parallel(n_jobs=1)]: Using backend SequentialBackend with 1 concurrent workers.
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
C:\Users\uttam.patra.kumar\AppData\Local\Continuum\anaconda3\envs\rasa_stack\lib\site-packages\sklearn\metrics\classification.py:1143: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
[Parallel(n_jobs=1)]: Done  12 out of  12 | elapsed:    0.0s finished
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Finished training component.
2019-04-20 13:12:29 INFO     rasa_nlu.model  - Successfully saved model into 'C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2\models\current\nlu'
2019-04-20 13:12:29 INFO     main  - Finished training
(rasa_stack) C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2>python -m rasa_core.train -d domain.yml -s stories.md -o models/dialogue
Processed Story Blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:00<00:00, 2004.93it/s, # trackers=1]
Processed Story Blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:00<00:00, 2006.36it/s, # trackers=4]
Processed Story Blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:00<00:00, 668.49it/s, # trackers=12]
Processed Story Blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:00<00:00, 573.36it/s, # trackers=12]
2019-04-20 13:13:03.204177: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2

Layer (type)                 Output Shape              Param #
masking (Masking)            (None, 5, 18)             0

lstm (LSTM)                  (None, 32)                6528

dense (Dense)                (None, 12)                396

activation (Activation)      (None, 12)                0
Total params: 6,924
Trainable params: 6,924
Non-trainable params: 0

2019-04-20 13:13:03 INFO     rasa_core.policies.keras_policy  - Fitting model with 62 total samples and a validation split of 0.1
Epoch 1/100
62/62 [==============================] - 1s 14ms/step - loss: 2.5008 - acc: 0.0806
Epoch 2/100
62/62 [==============================] - 0s 129us/step - loss: 2.4493 - acc: 0.3065
Epoch 3/100
62/62 [==============================] - 0s 289us/step - loss: 2.4181 - acc: 0.4032
Epoch 4/100
62/62 [==============================] - 0s 273us/step - loss: 2.3841 - acc: 0.4194
Epoch 5/100
62/62 [==============================] - 0s 177us/step - loss: 2.3576 - acc: 0.4194
Epoch 6/100
62/62 [==============================] - 0s 209us/step - loss: 2.3322 - acc: 0.4194
Epoch 7/100
62/62 [==============================] - 0s 257us/step - loss: 2.2871 - acc: 0.4355
Epoch 8/100
62/62 [==============================] - 0s 193us/step - loss: 2.2596 - acc: 0.4355
Epoch 9/100
62/62 [==============================] - 0s 225us/step - loss: 2.2132 - acc: 0.4355
Epoch 10/100
62/62 [==============================] - 0s 258us/step - loss: 2.1982 - acc: 0.4355
Epoch 11/100
62/62 [==============================] - 0s 241us/step - loss: 2.1527 - acc: 0.4355
Epoch 12/100
62/62 [==============================] - 0s 290us/step - loss: 2.1158 - acc: 0.4355
Epoch 13/100
62/62 [==============================] - 0s 273us/step - loss: 2.0766 - acc: 0.4355
Epoch 14/100
62/62 [==============================] - 0s 273us/step - loss: 2.0413 - acc: 0.4355
Epoch 15/100
62/62 [==============================] - 0s 242us/step - loss: 1.9894 - acc: 0.4355
Epoch 16/100
62/62 [==============================] - 0s 250us/step - loss: 1.9412 - acc: 0.4355
Epoch 17/100
62/62 [==============================] - 0s 274us/step - loss: 1.9368 - acc: 0.4355
Epoch 18/100
62/62 [==============================] - 0s 225us/step - loss: 1.8967 - acc: 0.4355
Epoch 19/100
62/62 [==============================] - 0s 210us/step - loss: 1.8716 - acc: 0.4355
Epoch 20/100
62/62 [==============================] - 0s 210us/step - loss: 1.8120 - acc: 0.4355
Epoch 21/100
62/62 [==============================] - 0s 193us/step - loss: 1.7951 - acc: 0.4355
Epoch 22/100
62/62 [==============================] - 0s 129us/step - loss: 1.8051 - acc: 0.4355
Epoch 23/100
62/62 [==============================] - 0s 193us/step - loss: 1.7520 - acc: 0.4355
Epoch 24/100
62/62 [==============================] - 0s 161us/step - loss: 1.7291 - acc: 0.4355
Epoch 25/100
62/62 [==============================] - 0s 225us/step - loss: 1.7271 - acc: 0.4355
Epoch 26/100
62/62 [==============================] - 0s 161us/step - loss: 1.7192 - acc: 0.4355
Epoch 27/100
62/62 [==============================] - 0s 225us/step - loss: 1.6874 - acc: 0.4355
Epoch 28/100
62/62 [==============================] - 0s 257us/step - loss: 1.6790 - acc: 0.4355
Epoch 29/100
62/62 [==============================] - 0s 306us/step - loss: 1.6591 - acc: 0.4355
Epoch 30/100
62/62 [==============================] - 0s 290us/step - loss: 1.6333 - acc: 0.4355
Epoch 31/100
62/62 [==============================] - 0s 225us/step - loss: 1.6304 - acc: 0.4355
Epoch 32/100
62/62 [==============================] - 0s 259us/step - loss: 1.5914 - acc: 0.4355
Epoch 33/100
62/62 [==============================] - 0s 257us/step - loss: 1.5951 - acc: 0.4355
Epoch 34/100
62/62 [==============================] - 0s 241us/step - loss: 1.6245 - acc: 0.4355
Epoch 35/100
62/62 [==============================] - 0s 306us/step - loss: 1.6044 - acc: 0.4355
Epoch 36/100
62/62 [==============================] - 0s 129us/step - loss: 1.5855 - acc: 0.4355
Epoch 37/100
62/62 [==============================] - 0s 211us/step - loss: 1.5611 - acc: 0.4355
Epoch 38/100
62/62 [==============================] - 0s 193us/step - loss: 1.5506 - acc: 0.4355
Epoch 39/100
62/62 [==============================] - 0s 178us/step - loss: 1.5717 - acc: 0.4355
Epoch 40/100
62/62 [==============================] - 0s 209us/step - loss: 1.5319 - acc: 0.4355
Epoch 41/100
62/62 [==============================] - 0s 145us/step - loss: 1.5119 - acc: 0.4355
Epoch 42/100
62/62 [==============================] - 0s 241us/step - loss: 1.5333 - acc: 0.4355
Epoch 43/100
62/62 [==============================] - 0s 241us/step - loss: 1.5044 - acc: 0.4355
Epoch 44/100
62/62 [==============================] - 0s 257us/step - loss: 1.4928 - acc: 0.4355
Epoch 45/100
62/62 [==============================] - 0s 451us/step - loss: 1.4884 - acc: 0.4355
Epoch 46/100
62/62 [==============================] - 0s 257us/step - loss: 1.4566 - acc: 0.4355
Epoch 47/100
62/62 [==============================] - 0s 322us/step - loss: 1.4746 - acc: 0.4355
Epoch 48/100
62/62 [==============================] - 0s 145us/step - loss: 1.4670 - acc: 0.4355
Epoch 49/100
62/62 [==============================] - 0s 229us/step - loss: 1.4587 - acc: 0.4355
Epoch 50/100
62/62 [==============================] - 0s 161us/step - loss: 1.4504 - acc: 0.4355
Epoch 51/100
62/62 [==============================] - 0s 145us/step - loss: 1.4605 - acc: 0.4355
Epoch 52/100
62/62 [==============================] - 0s 322us/step - loss: 1.4396 - acc: 0.4355
Epoch 53/100
62/62 [==============================] - 0s 209us/step - loss: 1.4181 - acc: 0.4355
Epoch 54/100
62/62 [==============================] - 0s 161us/step - loss: 1.4209 - acc: 0.4355
Epoch 55/100
62/62 [==============================] - 0s 241us/step - loss: 1.4031 - acc: 0.4355
Epoch 56/100
62/62 [==============================] - 0s 338us/step - loss: 1.3861 - acc: 0.4355
Epoch 57/100
62/62 [==============================] - 0s 322us/step - loss: 1.3801 - acc: 0.4677
Epoch 58/100
62/62 [==============================] - 0s 209us/step - loss: 1.3749 - acc: 0.4516
Epoch 59/100
62/62 [==============================] - 0s 370us/step - loss: 1.3564 - acc: 0.4677
Epoch 60/100
62/62 [==============================] - 0s 370us/step - loss: 1.3787 - acc: 0.4516
Epoch 61/100
62/62 [==============================] - 0s 338us/step - loss: 1.3256 - acc: 0.4677
Epoch 62/100
62/62 [==============================] - 0s 322us/step - loss: 1.2826 - acc: 0.4839
Epoch 63/100
62/62 [==============================] - 0s 225us/step - loss: 1.3070 - acc: 0.5000
Epoch 64/100
62/62 [==============================] - 0s 322us/step - loss: 1.2929 - acc: 0.4677
Epoch 65/100
62/62 [==============================] - 0s 225us/step - loss: 1.2875 - acc: 0.4839
Epoch 66/100
62/62 [==============================] - 0s 370us/step - loss: 1.2828 - acc: 0.5000
Epoch 67/100
62/62 [==============================] - 0s 338us/step - loss: 1.2434 - acc: 0.4839
Epoch 68/100
62/62 [==============================] - 0s 338us/step - loss: 1.2918 - acc: 0.5000
Epoch 69/100
62/62 [==============================] - 0s 274us/step - loss: 1.2323 - acc: 0.5161
Epoch 70/100
62/62 [==============================] - 0s 289us/step - loss: 1.2554 - acc: 0.5323
Epoch 71/100
62/62 [==============================] - 0s 209us/step - loss: 1.2169 - acc: 0.5161
Epoch 72/100
62/62 [==============================] - 0s 322us/step - loss: 1.2238 - acc: 0.5000
Epoch 73/100
62/62 [==============================] - 0s 289us/step - loss: 1.1908 - acc: 0.5323
Epoch 74/100
62/62 [==============================] - 0s 322us/step - loss: 1.1655 - acc: 0.5484
Epoch 75/100
62/62 [==============================] - 0s 306us/step - loss: 1.1733 - acc: 0.5645
Epoch 76/100
62/62 [==============================] - 0s 418us/step - loss: 1.1590 - acc: 0.5645
Epoch 77/100
62/62 [==============================] - 0s 370us/step - loss: 1.1296 - acc: 0.5806
Epoch 78/100
62/62 [==============================] - 0s 306us/step - loss: 1.1589 - acc: 0.5000
Epoch 79/100
62/62 [==============================] - 0s 354us/step - loss: 1.1261 - acc: 0.5323
Epoch 80/100
62/62 [==============================] - 0s 306us/step - loss: 1.1338 - acc: 0.5806
Epoch 81/100
62/62 [==============================] - 0s 290us/step - loss: 1.1304 - acc: 0.5484
Epoch 82/100
62/62 [==============================] - 0s 338us/step - loss: 1.1075 - acc: 0.5806
Epoch 83/100
62/62 [==============================] - 0s 305us/step - loss: 1.0809 - acc: 0.5968
Epoch 84/100
62/62 [==============================] - 0s 370us/step - loss: 1.0686 - acc: 0.6129
Epoch 85/100
62/62 [==============================] - 0s 418us/step - loss: 1.0825 - acc: 0.5968
Epoch 86/100
62/62 [==============================] - 0s 322us/step - loss: 1.0537 - acc: 0.6290
Epoch 87/100
62/62 [==============================] - 0s 257us/step - loss: 1.0613 - acc: 0.5645
Epoch 88/100
62/62 [==============================] - 0s 515us/step - loss: 1.0333 - acc: 0.6129
Epoch 89/100
62/62 [==============================] - 0s 289us/step - loss: 1.0496 - acc: 0.5484
Epoch 90/100
62/62 [==============================] - 0s 306us/step - loss: 1.0121 - acc: 0.6290
Epoch 91/100
62/62 [==============================] - 0s 322us/step - loss: 1.0155 - acc: 0.5806
Epoch 92/100
62/62 [==============================] - 0s 273us/step - loss: 0.9699 - acc: 0.6452
Epoch 93/100
62/62 [==============================] - 0s 402us/step - loss: 1.0084 - acc: 0.6452
Epoch 94/100
62/62 [==============================] - 0s 289us/step - loss: 0.9807 - acc: 0.6452
Epoch 95/100
62/62 [==============================] - 0s 306us/step - loss: 0.9734 - acc: 0.6290
Epoch 96/100
62/62 [==============================] - 0s 322us/step - loss: 0.9701 - acc: 0.6290
Epoch 97/100
62/62 [==============================] - 0s 257us/step - loss: 0.9480 - acc: 0.6129
Epoch 98/100
62/62 [==============================] - 0s 547us/step - loss: 0.9665 - acc: 0.6290
Epoch 99/100
62/62 [==============================] - 0s 257us/step - loss: 0.9434 - acc: 0.6290
Epoch 100/100
62/62 [==============================] - 0s 322us/step - loss: 0.9844 - acc: 0.6613
2019-04-20 13:13:07 INFO     rasa_core.policies.keras_policy  - Done fitting keras policy model
Processed actions: 62it [00:00, 3656.25it/s, # examples=62]
2019-04-20 13:13:07 INFO     rasa_core.agent  - Model directory models/dialogue exists and contains old model files. All files will be overwritten.
2019-04-20 13:13:08 INFO     rasa_core.agent  - Persisted model to 'C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2\models\dialogue'
(rasa_stack) C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2>python -m rasa_core.run -d models/dialogue -u models/current/nlu
2019-04-20 13:18:57 INFO     root  - Rasa process starting
2019-04-20 13:19:09 INFO     rasa_nlu.components  - Added 'nlp_spacy' to component cache. Key 'nlp_spacy-en'.
2019-04-20 13:19:20.738352: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2019-04-20 13:19:21 INFO     root  - Rasa Core server is up and running on http://localhost:5005
Bot loaded. Type a message and press enter (use '/stop' to exit):
Your input ->  Hello
<IP_ADDRESS> - - [2019-04-20 13:19:29] "POST /webhooks/rest/webhook?stream=true&token= HTTP/1.1" 200 286 0.125641
Hey! How are you?
Buttons:
1: great (great)
2: super sad (super sad)
Your input ->  super sad
Here is something to cheer you up:
Image: https://i.imgur.com/nGF1K8f.jpg
Did that help you?<IP_ADDRESS> - - [2019-04-20 13:19:35] "POST /webhooks/rest/webhook?stream=true&token= HTTP/1.1" 200 344 0.018948
Your input ->  yes
Great carry on!<IP_ADDRESS> - - [2019-04-20 13:19:40] "POST /webhooks/rest/webhook?stream=true&token= HTTP/1.1" 200 183 0.020146
Your input ->  bye
Bye<IP_ADDRESS> - - [2019-04-20 13:19:45] "POST /webhooks/rest/webhook?stream=true&token= HTTP/1.1" 200 171 0.017488
Your input ->  /stop
(rasa_stack) C:\Uttam\ChatBot\RASA\RasaCore\rasa_core-master\examples\moodbot2>python -m rasa_core.run -d models/dialogue -u models/nlu/current -p 5002 -c slack --credentials credentials.yml --debug
2019-04-20 13:20:17 INFO     root  - Rasa process starting
2019-04-20 13:20:29 INFO     rasa_nlu.components  - Added 'nlp_spacy' to component cache. Key 'nlp_spacy-en'.
2019-04-20 13:20:42.081691: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2019-04-20 13:20:43 DEBUG    rasa_core.utils  - Available web server routes:
static                                             OPTIONS, GET, HEAD             /static/[filename]
slack_webhook.health                               OPTIONS, GET, HEAD             /webhooks/slack/
slack_webhook.webhook                              OPTIONS, GET, POST, HEAD       /webhooks/slack/webhook
2019-04-20 13:20:43 INFO     root  - Rasa Core server is up and running on http://localhost:5002
<IP_ADDRESS> - - [2019-04-20 13:23:29] "POST /webhooks/slack/webhook HTTP/1.1" 200 200 0.000996
2019-04-20 13:28:57 DEBUG    rasa_core.tracker_store  - Creating a new tracker for id 'UHGTEB1QR'.
2019-04-20 13:28:57 DEBUG    rasa_core.processor  - Received user message 'Hello' with intent '{'name': 'greet', 'confidence': 0.5550509971084321}' and entities '[]'
2019-04-20 13:28:57 DEBUG    rasa_core.processor  - Logged UserUtterance - tracker now has 2 events
2019-04-20 13:28:57 DEBUG    rasa_core.processor  - Current slot values:
2019-04-20 13:28:58 DEBUG    rasa_core.policies.memoization  - Current tracker state [None, None, None, {}, {'intent_greet': 1.0, 'prev_action_listen': 1.0}]
2019-04-20 13:28:58 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '7'
2019-04-20 13:28:58 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:28:58 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:28:58 DEBUG    rasa_core.processor  - Predicted next action 'utter_greet' with prob 1.00.
2019-04-20 13:29:00 DEBUG    rasa_core.processor  - Action 'utter_greet' ended with events '[]'
2019-04-20 13:29:00 DEBUG    rasa_core.processor  - Bot utterance 'BotUttered(text: Hey! How are you?, data: {
"elements": null,
"buttons": [
{
"payload": "great",
"title": "great"
},
{
"payload": "super sad",
"title": "super sad"
}
],
"attachment": null
})'
2019-04-20 13:29:00 DEBUG    rasa_core.policies.memoization  - Current tracker state [None, None, {}, {'intent_greet': 1.0, 'prev_action_listen': 1.0}, {'intent_greet': 1.0, 'prev_utter_greet': 1.0}]
2019-04-20 13:29:00 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '0'
2019-04-20 13:29:00 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:29:00 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:29:00 DEBUG    rasa_core.processor  - Predicted next action 'action_listen' with prob 1.00.
2019-04-20 13:29:00 DEBUG    rasa_core.processor  - Action 'action_listen' ended with events '[]'
<IP_ADDRESS> - - [2019-04-20 13:29:00] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 2.194233
2019-04-20 13:29:00 WARNING  rasa_core.channels.slack  - Received retry #1 request from slack due to http_timeout
<IP_ADDRESS> - - [2019-04-20 13:29:00] "POST /webhooks/slack/webhook HTTP/1.1" 201 141 0.002990
<IP_ADDRESS> - - [2019-04-20 13:29:01] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 0.000000
2019-04-20 13:32:39 DEBUG    rasa_core.tracker_store  - Recreating tracker for id 'UHGTEB1QR'
2019-04-20 13:32:39 DEBUG    rasa_core.processor  - Received user message 'sad' with intent '{'name': 'mood_unhappy', 'confidence': 0.9264257325961566}' and entities '[]'
2019-04-20 13:32:39 DEBUG    rasa_core.processor  - Logged UserUtterance - tracker now has 6 events
2019-04-20 13:32:39 DEBUG    rasa_core.processor  - Current slot values:
2019-04-20 13:32:39 DEBUG    rasa_core.policies.memoization  - Current tracker state [None, {}, {'intent_greet': 1.0, 'prev_action_listen': 1.0}, {'intent_greet': 1.0, 'prev_utter_greet': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}]
2019-04-20 13:32:39 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '8'
2019-04-20 13:32:39 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:32:39 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:32:39 DEBUG    rasa_core.processor  - Predicted next action 'utter_cheer_up' with prob 1.00.
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Action 'utter_cheer_up' ended with events '[]'
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Bot utterance 'BotUttered(text: Here is something to cheer you up:, data: {
"elements": null,
"buttons": null,
"attachment": "https://i.imgur.com/nGF1K8f.jpg"
})'
2019-04-20 13:32:40 DEBUG    rasa_core.policies.memoization  - Current tracker state [{}, {'intent_greet': 1.0, 'prev_action_listen': 1.0}, {'intent_greet': 1.0, 'prev_utter_greet': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}]
2019-04-20 13:32:40 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '9'
2019-04-20 13:32:40 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:32:40 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Predicted next action 'utter_did_that_help' with prob 1.00.
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Action 'utter_did_that_help' ended with events '[]'
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Bot utterance 'BotUttered(text: Did that help you?, data: {
"elements": null,
"buttons": null,
"attachment": null
})'
2019-04-20 13:32:40 DEBUG    rasa_core.policies.memoization  - Current tracker state [{'intent_greet': 1.0, 'prev_action_listen': 1.0}, {'intent_greet': 1.0, 'prev_utter_greet': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_utter_did_that_help': 1.0}]
2019-04-20 13:32:40 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '0'
2019-04-20 13:32:40 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:32:40 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Predicted next action 'action_listen' with prob 1.00.
2019-04-20 13:32:40 DEBUG    rasa_core.processor  - Action 'action_listen' ended with events '[]'
<IP_ADDRESS> - - [2019-04-20 13:32:40] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 1.223328
<IP_ADDRESS> - - [2019-04-20 13:32:40] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 0.000998
<IP_ADDRESS> - - [2019-04-20 13:32:40] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 0.000997
<IP_ADDRESS> - - [2019-04-20 13:32:41] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 0.000000
2019-04-20 13:33:27 DEBUG    rasa_core.tracker_store  - Recreating tracker for id 'UHGTEB1QR'
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Received user message 'super sad' with intent '{'name': 'mood_unhappy', 'confidence': 0.7067781916293838}' and entities '[]'
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Logged UserUtterance - tracker now has 12 events
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Current slot values:
2019-04-20 13:33:27 DEBUG    rasa_core.policies.memoization  - Current tracker state [{'intent_greet': 1.0, 'prev_utter_greet': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_utter_did_that_help': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}]
2019-04-20 13:33:27 DEBUG    rasa_core.policies.memoization  - There is no memorised next action
2019-04-20 13:33:27 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:33:27 DEBUG    rasa_core.policies.ensemble  - Action 'action_listen' was predicted after a user message using policy_0_KerasPolicy. Predicting fallback action: action_default_fallback
2019-04-20 13:33:27 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_1_FallbackPolicy
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Predicted next action 'action_default_fallback' with prob 1.00.
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Action 'action_default_fallback' ended with events '['UserUtteranceReverted()']'
2019-04-20 13:33:27 DEBUG    rasa_core.policies.memoization  - Current tracker state [{'intent_greet': 1.0, 'prev_action_listen': 1.0}, {'intent_greet': 1.0, 'prev_utter_greet': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'intent_mood_unhappy': 1.0, 'prev_utter_did_that_help': 1.0}]
2019-04-20 13:33:27 DEBUG    rasa_core.policies.memoization  - There is a memorised next action '0'
2019-04-20 13:33:27 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-04-20 13:33:27 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_2_MemoizationPolicy
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Predicted next action 'action_listen' with prob 1.00.
2019-04-20 13:33:27 DEBUG    rasa_core.processor  - Action 'action_listen' ended with events '[]'
<IP_ADDRESS> - - [2019-04-20 13:33:27] "POST /webhooks/slack/webhook HTTP/1.1" 200 115 0.104020
ngrok by @inconshreveable                                                                                (Ctrl+C to quit)
Session Status                online
Session Expires               7 hours, 33 minutes
Version                       2.3.25
Region                        United States (us)
Web Interface                 http://<IP_ADDRESS>:4040
Forwarding                    http://e0016011.ngrok.io -> http://localhost:5002
Forwarding                    https://e0016011.ngrok.io -> http://localhost:5002
Connections                   ttl     opn     rt1     rt5     p50     p90
9       0       0.00    0.00    0.72    3.01
HTTP Requests
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   201 CREATED
POST /webhooks/slack/webhook   200 OK
POST /webhooks/slack/webhook   200 OK

I am the same issue with my bot. I execute the commands in the following order:

rasa run (by default this goes to 5005)
ngrok http 5005
copy the first link in my endpoints file (http:-ngroklink-:5055/webook
rasa run on port 5002
ngrok http 5002
copy that link in event subscriptions
URL gets validated

When I try talking to my bot the terminal shows that the intents have been predicted without any errors but the bot response is not shown in the slack window.
Please can anyone help me.
Please view the following link: https://forum.rasa.com/t/rasa-bot-not-responding-on-slack/13704/13
My id is zaidalvi and have pictures and a detailed explanation of my problem there as well.
PLEASE I NEED HELP!

@Uttam1982 any ideas on how can solve this problem?


Document RPA functionality

Issue #2788 added support for RPA but there's no time to document the functionality in the User Guide before RF 3.1 alpha 1. Because the User Guide is not generated with preview releases, this doesn't matter much, but this issue acts as a reminder to do it after the alpha.
Documentation to add include:

[ ] New section about the RPA functionality in general:

[ ] Using *** Tasks *** header instead of *** Test Cases ***
[ ] Using --rpa both with Robot and Rebot
[ ] Using --task instead of --test
[ ] Using Set Task Variable instead of Set Test Variable

[ ] Note to section about creating tests about possibility to using *** Tasks ***
[ ] Note to section about test data tables about the Task table.
[ ] List --rpa and --task in the appendix about all command line options

coming late to the party, and read the discussion in #2788, but I still don't understand what is the difference between a "Task" and a "Test". Is it just a name difference because the goal is different (automating anything versus automating a test)? If so, then a "Task" would be written and executed the same way as a test, right? (failing if there is a failing keyword).

Yeah, this is just terminology. No real functional difference.


[tcb / consensus] Hardening

This issue covers the remainder of tasks necessary for completion of SafetyRules

[ ] LEC issues should not cause consensus to panic
[ ] Logging of all events, both positive and negative
[x] Moving consensus_state logging into safety rules
[ ] Network errors do not affect consensus
[ ] Consensus handling a key is missing
[ ] Consensus handling not being involved in an epoch
[ ] Consensus handling a request to perform an outdated action (construct_and_sign_vote, sign_timeout, sign_proposal)
[ ] Consensus handling an unconfigured SafetyRules in the middle of an epoch / Consensus safely restarts an epoch if SafetyRules goes offline
[x] Consensus losing a vote and re-requesting for the same round
[x] The waypoint is more than 100 epochs behind the current state (currently the framework only retrieves 100
[x] SafetyRules idempotent behavior to initialize with the same value without restart
[ ] Metrics for all public persistent store data and failures
[ ] Logging error where appropriate
[ ] Implement a write-through cache for persistent storage
[ ] Remove explicit dependency on anyhow from interfaces
[x] SafetyRules config
[x] SafetyRules supports dns

Discussion
Issue) Consensus handling a key is missing
David) Ideally, SafetyRules would keep checking and logging errors so the admin would respond. Consensus would fail operations but could still participate in storing and committing blocks.
Issue) Consensus handling not being involved in an epoch
David) Should consensus disable itself and rely on state sync? Should it exhibit the same behavior as if the key is missing? Does it even bother calling into SafetyRules? I'd say if we want to enter consensus the behavior should be the same, but SafetyRules only logs debugging info but still errors.
Issue) Consensus handling a request to perform an outdated action (construct_and_sign_vote, sign_timeout, sign_proposal)
David) Simply log and wait for the next event.
Issue) Consensus losing a vote and re-requesting for the same round
David) Opinion, this is an optimization to increase liveness and avoid cases where consensus is stuck because only 2f + 1 nodes remain and 1 has a failure of this nature. This does not seem like a V1 critical area and can be added without breaking changes.
Issue) The waypoint is more than 100 epochs behind the current state (currently the framework only retrieves 100,
David) This should be optional, the waypoint should probably be updated in the case it is this far behind.

Hey folks, I think this summarizes all of the outstanding concerns we have around SafetyRules / Consensus engagement.

Thanks for putting this together!

agree with missing key and different epoch, consensus can continue operating without the ability to vote. (still able to add block/sync)
I think we should handle  Consensus losing a vote and re-requesting for the same round, since this requires a code change to fix.
Manually update waypoint seems fine.
looks to me consensus can safely ignore all the errors from LSR?

Actually my preference was kind of to do nothing and have consensus not participate, but since we need to handle errors anyway, this is probably more uniform.
Why? This is something that we could update our code without impacting anything in the future. I personally see this as a nice to have. And we should also evaluate the performance overhead.
Closing out the waypoint issue
Yup!

Consensus handling a request to perform an outdated action (construct_and_sign_vote, sign_timeout, sign_proposal) is already handled by these events being logged by consensus -- @zekun000 do you feel we should have explicit tests for these?

@lightmark, I suspect there was some interesting condition wherein LEC wasn't capturing network errors in remote_service client -- likely wrapping them as anyhow::Error. At any rate, I hope that is the only LEC issue, so I'm going to close check that off too.

@davidiw what interesting condition are you referring to?


🐞 Highlighting slowly disappears as user scrolls down

Description
CodeEdit app isn't highlighting all lines of code. It's highlighting about 85% of lines displayed in the window. To fix this I need to scroll down all the file.(after scrolling all file the highlighting remains).
BUT: there is a scenario when scrolling doesn't help: if last few lines of file are not empty, then the'll not be highlighted. To fix this I need to add some empty lines at the end of file.
To Reproduce

Open a file with an implemented highlighting(i.e .py file). The file must be longer than the CodeEdit app height.

Expected behavior
All the file is highlighted
Version information
CodeEdit: [e.g. 1.0 (1)]
macOS: [e.g. 13.1.0]
Xcode: [e.g. 14.2]
Additional context
No response

Is this still an issue with the most up to date build? I can't reproduce this.

Yes, it's. Issue is in the first img:

Version information
CodeEdit:  0.0.1-alpha (25)
macOS: 13.1.2
Xcode: 14.2

This should be fixed in the next release. If it is not please comment/reopen.


First iteration of simulate validation (user operation)

This adds first checks for simulate validation - forbidden opcodes. It also removes sanity_check_results and rertieves the stake info at the start (alongside JS trace).

I am curious what stuffs left to be resolved

You mean in general or in the simulation? For simulation, there are still several things: storage access, limitations on CALL opcodes ... I will continue with these things.


Publish new versions to pub.dev

Describe the bug
The most recent patches to riverpod_lint (#3706) failed to release.
To Reproduce
https://pub.dev/packages/riverpod_lint
Expected behavior
It didn't display an analysis issue warning.
PS: Thanks for Riverpod! It's why Dart's my favorite language—it has Riverpod! 🙃

My bad. Forgot to press one button.
Done


Update basic-concepts.md

Highlighted that do blocks need enclosing parens.

These are transitional copies of the Motoko generated docs and should not be edited. I'll fix the sources instead and then close this PR.

Fixed in motoko doc branch here https://github.com/dfinity/motoko/commit/5c99f088131338854d413cecbf072ba4479cb426

I agree that this might be not the best place to explain nested
expressions.
However, I don’t think regular developers will read the grammar definition.
Maybe we can find another place to explain the details of “do” blocks.
On Wed, Jun 15, 2022 at 3:10 AM Claudio Russo @.***>
wrote:

@.**** requested changes on this pull request.
Thanks for the PR, but I don't think this improves the doc.
The original example was syntactically correct, and your new example,
meant to illustrate the need to parenthesize nested do expressions,
doesn't build on the previous example in the same way and is ill-typed.
I think at this point in the doc, it doesn't really make sense to describe
precise details of the grammar, which you can find here:
https://internetcomputer.org/docs/current/developer-docs/build/languages/motoko/motoko-grammar/
I would just close this PR.
—
Reply to this email directly, view it on GitHub
https://github.com/dfinity/portal/pull/244#pullrequestreview-1007234473,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYV4Y4EHBIRFOIQIV4233I3VPGTZZANCNFSM5YZJNYEA
.
You are receiving this because you were mentioned.Message ID:
@.***>


White screen after loading PDF anly API 21

v.0.4.1
I download pdf via url, everything works fine.
But only on API 21 after loading a white screen remains and that's it
I attach screenshots of the code, logs and screen.
Sorry for the quality, I take pictures from my work laptop.

Hi @Vasilisk7
please download example project
and run it to check if it has the same issue

I downloaded the example and checked it on API 21, the problem persists, I attach a video
https://user-images.githubusercontent.com/35864378/146187310-18718e79-98e3-44a2-ae49-e4cf8feaae3f.mp4
https://user-images.githubusercontent.com/35864378/146187318-8e4a66f5-7cb1-4f23-905d-02c7f83c3071.mp4

please tell me what is the flutter version you use
 flutter --version
are you find the same issue with the real devices?

Flutter 2.8.0
Dart 2.15.0
On a real device API 21 there is no way to check (no device).
On API 29-30 on a real device everything works.

Having the same issue with version 0.4.1

Ok seems like I was messing up with URL and that is why the widget was rendering blank, my issue is solved

My problem is still not solved :(

I downloaded the demo project and ran it without changing anything. The problem persists, this is all I described above.

Having the same issue with version 0.4.1 On Android 11 API 30

I have same problem, how can I solve ?
Android 11 API 30

same issue, It worked in debug mode, but in release didn't. I included the proguard configuration but don't work

I downloaded the demo project and ran it without changing anything. The problem persists, this is all I described above.

same issue,have you solved? It seems cann't use in API 21

+1


iter time as high as 9000ms

for falcon-7b, adapter tuning, I have high iter times, around 9000ms.
Looks like the contributors have as low as 200ms.
I'm using an NVIDIA RTX A6000, if that matters.
is there any way I could figure out what the bottleneck is?

Your best bet would be using the PyTorch profiler. Here's a video that shows you how https://www.youtube.com/watch?v=qRZrVNNe3gQ


docker server certificate -- requires exact ip match?

Let's say I have two machines: my desktop machine running docker in Virtual Box, and my laptop where I want to run the docker client.
I created a Virtual Box docker server named "docker" on my desktop with:
docker-machine create --driver=virtualbox --virtualbox-memory=9000 --virtualbox-disk-size=50000 docker

I'm trying to access that docker server from my laptop (OSX).
I'm running this ssh tunnel between my laptop and my desktop, exposing the docker server port on my laptop's localhost port 12376. This requires me to be able to ssh from my laptop to my desktop, but seems secure.
ssh -nNT -L 12376:<IP_ADDRESS>:2376 MYDESKTOP
I already copied the docker server's certs, i.e. copied /var/lib/boot2docker/tls ca.pem cert.pem key.pem to my laptop's ~/.docker-tls.
But docker only wants to talk to a specific ip:
$ export DOCKER_CERT_PATH=~/.docker-tls
$ export DOCKER_TLS_VERIFY=1
$ export DOCKER_HOST=tcp://localhost:12376
$ docker ps
FATA[0000] An error occurred trying to connect: Get https://<IP_ADDRESS>:12376/v1.17/containers/json: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>

Is there any way to tell docker client to trust the certificate and ignore its hostname/ip? Or is there a better way to tunnel a docker server port?

I see certs.go newCertificate() sets the Subject Name "Organization" to the docker-machine name.
https://github.com/docker/machine/blob/344c7d771afd681322d543891df948db8749cb7b/utils/certs.go
func newCertificate(org string) (*x509.Certificate, error) {
...
	return &x509.Certificate{
		SerialNumber: serialNumber,
		Subject: pkix.Name{
			Organization: []string{org},
		},

Maybe it should set the "Common Name" to that too too? Then as long as I access the server by that hostname (eg. add "<IP_ADDRESS> docker" to my /etc/hosts and set DOCKER_HOST=tcp://docker:12376), the docker client would validate the cert.
Or, allow a series of alternative hostnames or ip's to be passed down, currently the array only contains a single ip:
https://github.com/docker/machine/blob/339267198840eefa6508c1de509b13af3c77884f/libmachine/provision/utils.go
func ConfigureAuth(p Provisioner, authOptions auth.AuthOptions) error {
...
        err = utils.GenerateCert(
		[]string{ip},

Yup, setting "CommonName" allows docker client on my laptop to validate the cert, even through an ssh tunnel to the docker server running in a Virtual Box on my desktop. Code diff below.
Had some trouble figuring out which cert files I needed on my laptop. I assumed all the .pem files I need are in /var/lib/boot2docker/tls, but ./docker-machine_darwin-amd64 regenerate-certs docker did not seem to update that directory, and cert.pem isn't even in the file system.
Got it working by copying some of the .pem's from my desktop:
ssh MYDESTOP tar -cf - -C .docker/machine/machines/docker/ ca.pem cert.pem key.pem | tar -xvf - -C ~/.docker-tls
ssh -nNT -L 12376:<IP_ADDRESS>:2376 MYDESKTOP  # tunnel to docker on docker vm
ssh -nNT -L 12022:localhost:57040 MYDESKTOP   # tunnel to ssh on docker vm
export DOCKER_CERT_PATH=~/.docker-tls
export DOCKER_TLS_VERIFY=1
export DOCKER_HOST=tcp://docker:12376  # my /etc/hosts has "<IP_ADDRESS>  docker"
docker ps   # yay, able to securely use by desktop's virtual box docker-machine

diff --git a/utils/certs.go b/utils/certs.go
index 84361f7..4341a21 100644
--- a/utils/certs.go
+++ b/utils/certs.go
@@ -51,6 +51,7 @@ func newCertificate(org string) (*x509.Certificate, error) {
SerialNumber: serialNumber,
Subject: pkix.Name{
Organization: []string{org},

                  CommonName: org,
          },
          NotBefore: notBefore,
          NotAfter:  notAfter,

I get almost exactly the same error when using Kitematic (which bundles docker-machine) + a hostname (also defined in /etc/hosts) for the active docker machine instead of an IP address.
As previously found, this is most likely happening because CN is not being set yet. This would need to be fixed before this setup can actually work.

Result of using DOCKER_HOST with IP address:
$ env DOCKER_HOST=tcp://<IP_ADDRESS>:2376 docker info
Containers: 52
...[it works]...

Result of using it with the active docker-machine name:
$ env DOCKER_HOST=tcp://dev:2376 docker info
FATA[0000] An error occurred trying to connect: Get https://dev:2376/v1.18/info: x509: certificate is valid for , not dev

Content of /etc/hosts file:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
<IP_ADDRESS>	localhost
<IP_ADDRESS>	broadcasthost
::1             localhost

# Docker host
<IP_ADDRESS>  dev

System:

OS X 10.10.3
Docker version 1.6.2, build 7c8fca2
docker-machine version 0.2.0 (8b9eaf2)

Correct.  This is how the TLS config works.  It currently uses the IP SAN for communication.  There is a PR open to allow more SANs during creation (#1228).

@jamshid Maybe you could make some specific propsals for features, including how they would be integrated with the Machine CLI, to follow up on this?  There's a couple different threads in this issue.

I think being able to specify multiple --tls-san when creating machine or regenerating certs covers my use case, so I think https://github.com/docker/machine/pull/1228 resolves this.


Stubs remove, offsite tuts list add

Stubs remove, offsite tuts list add
I imagine it is a bit scary for curators to see a complete change-out of statics.json, instead of seeing a list of edits to the old one.
But, I did the build at home, using the new statics.json, and with all the stub files removed, and with the list installed in generals... and it was error free and looked fine.
I have good confidence in my new statics.json.  I think it's fine.  :)  (I'm still scared, though)

So I can see that you removed stubs but I cannot see the new page

Yep, I screwed up.  I put "creating a convincing world" stub into
generals/general, instead of offsite_tutorials_list.md
Reject the PR, I'll fix and new PR.  Sorry.
Darn.
On 9/14/2016 9:58 AM, David Catuhe wrote:

So I can see that you removed stubs but I cannot see the new page
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Documentation/pull/224#issuecomment-247041206,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGn1aCgrrB-OT3T4mQ0dBKm3nRIn1G6dks5qqAt4gaJpZM4J8Xlm.

Fixed here... I think.  Not sure if I can add them to my PR, or what happens now.

If you want me to cancel first PR and re-PR, tell me so.  I kept it open.  Perhaps the fixes are automatically included.  (scared)

yep this is fine. I'll merge and start a build to see the result live

Yay, build might have worked!
Notice that our title underscores got shortened, so we lost the widened column.  hmm.
Thanks for your help/work/tolerance, DK.

Table is not centered in screen, either.  hmm.

Ping @temechon


Documentation for classes

Add docstring for classes as well as functions

Docstring for classes and functions
Jupyter notebook with an interactive demo of the classes
Consider readthedocs or sphinx for hosting documentation


Redis: propagate redis query syntax though "filter"

The purpose of this proposal is to allow the user to propagate redis query syntax through then filter option in the query end-point.
A noteboook demonstrating the query syntax is provided in:
examples/providers/redis/semantic-search-and-filter.ipynb

Don't escape the wildcard * from the TAG fields.

Rationale: Suppose the user has multiple corpus of documents and they want to differentiate query then independently. E.g. "test_123", "test_xyz", this can be filtered using | or prefix matching with *,
{"source_id" :  "test*"}
With the change:
This matches "test_123", "test_xyz"
Without the change:
doesn't match anything.

Don't escape the TEXT field:

This idea is to support queries like this involving wild cards: "author": "Elvis*Jr.|Vape".
We've also removed the _escape altogether:
As an example, suppose we have authors Elvis Tusk Jr. and Vape Jordan,
With the change:
"author": "Elvis Tusk Jr.|Vape" - matches Elvis Tusk Jr. or Vape Jordan
"author": "Elvis*Jr.|Vape~" - causes 500 internal server error because of the ~.
Without the change:
"author": "Elvis Tusk" - doesn't match anything
We might intercept the server error and make some helpful suggestions to the user instead but allow the additional flexibility of the query.

logging.info(f"Gathering {len(queries)} query results", flush=True)

This was causing an error for me, it's not related to the other changes.

Thank you! @isafulf this is good from my perspective.


Implement a digital forest

This idea was triggered by @Sakrecoer comments on https://github.com/bonfirelink/websites/pull/50#issuecomment-988645061, inspired by conversations with @WilhelminaWelsch about digital gardens and motivated by my desire to give more visibility to subjective perspectives on the website.
Quoting my reply on https://github.com/bonfirelink/websites/pull/50#issuecomment-990377383:

Your idea of inviting to self-reflection in more explicit ways is something that I resonate a lot with. I imagine these questions and many others (e.g. What is a Tuesday for you?) being seeds for people to write their subjective perspective publicly. I believe that, these short essays would come to reflect more faithfully what the collective (un)conscious may be over time.
A format that I imagine for this is the digital garden or, even better, the digital forest. The landing page and main sections of the website, in practice, is representing the most institutional aspects of the collective, where content and aesthetics are curated and polished. The digital forest, on the other hand, would give a space for more extitutional expression, where a labyrinth of unindexed content and diverse aesthetics grow by multiple authors.

Reposting @Sakrecoer ideas from https://github.com/bonfirelink/websites/pull/50#issuecomment-988645061:

I would maybe list a few useful questions to ask oneself, and questions that might arise, to give a little ground for the less poetically inclined users without leaving the metaphysical realm.
What would it feel like to be at the receiving end of harassment, discrimination or bullying?
What would you think of a place where you get scammed, spammed or bombarded with irrelevant information?
What do you think of people scamming, spamming and bombarding irrelevant or nonfactual information?
What do you feel when someone is impatient or impolite to you?
Is it a good idea to post private information to a group with people that are potentially total strangers?
What do you think when a product is being thrown at your face?
How does it feel to be deceived by someone pretending to be something or someone they are not?
What is your reaction to unsolicited DMs from unknown members?
How do you navigate off-topic conversation?
What is it that you would expect from interacting with your peers?


chore: refactor nasty async edge cases with type parsing enabled

This refactor how we parse async edge cases with types on. I tried to optimize and tweak this, but it's hard so I was forced to do some speculative parsing.
It's performs 80% better than Babels current WIP solution on the same issues

@aladdin-add I'm aware there are still space for optimizations and there exist some duplicate code. I'm working on it :)

@aladdin-add I merge this as it is and will do a follow up PR to clean up the messy code :)


fixed minor bugs in dark-theme

fixed code-copied pop-up color in dark mode

Bugs have been fixed.


the edges of display are black on rotation

hi.
it seems there is effect that rotation if faster then rendering itself and as result during rotation of head we get black edges. is this possible to address this ?
it is not really a high priority for me but would make it much closed to other commercial headsets.
perhaps render a bit wider area so it can be used when rotating head?
g

We may get picture of wider area, how we put the texture for headset (Oculus Mobile SDK)?
I think we need to implement ATW like algorithm to properly slide the texture for SDK.
It is very hard work and takes very long time.
Reducing latency is also effective for this problem. ALVR work in following steps.

(Headset) Get and send tracking data
(Server) Receive tracking data and produce VSync event
(Server) Wait for game to render texture.
(Server) Compose texture and encode and send to headset
(Headset) Receive texture and decode and render

I think we can more tune around step 2.

ok. thanks for clarification.
i am not opting to do hard work on it. very happy with how it works now :)

one solution for this could be to predict a little rotation of headset and display content for displayed rotation.


Add default docs to this repo

Take a look at https://opensource.guide/starting-a-project/#launching-your-own-open-source-project for guidance on default documentation that an open source project should have. You have inherited the Code of Conduct from the organization, and the .github repo contains some good boilerplates.  What I see missing from here, specifically:

Open source license
README
Contributing guidelines

What do all the files in here do? Do they generate some webpage? Where is the webpage? How do I contribute to this effort?
Check out the links above for more information on what each of those files should contain. LMK if you need help with this.

thanks for sharing! I will make sure to check.

Currently combine the contributing into README. A readme is added through #23

We should discuss the license for all repos in our next meeting! I am currently thinking of using GPLv3 which allow the open source to continues if any of the code is being used somewhere else. However, we should probably also think about when would be a good time to put the license on. Should we wait till the repos are more established or now is actually a good time.

Looping in @ocefpaf for advice RE: which license to choose. The OpenSource Guide provides a lot of good context from which to make an educated decision.
Timing of adding a license: ASAP. According to GitHub's guidance on licenses:

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

Which does not jive with what we're trying to do here.
I'm trying to look for NOAA guidance on software licensing. But, I think as an initial step, MIT is a good one to start with.

MIT is a good one to start with.

I try to avoid MIT b/c it has a loophole for plagiarism. BSD-3-Clause is virtually identical and without the text that allows for copy without credits.
The problem with MIT is the second paragraph:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.

What means substantial in code? How much of a library can someone copy without the need to include the original license and acknowledge?

Thanks! @ocefpaf . I was originally thinking about GPLv3. Is the reason of BSD3 "more free" for the user? In other words, it allow the user to have the choice of choosing their derivative on their own license or also allow the derivative to be not open sourced?  (GPLv3 requires the derivative to also be under GPLv3 and has to stay open sourced).

The virality of copy left licenses may affect the project adoption. In a perfect world we all would use GPL only code. In reality, if we do that, we will restrict the code use. I don't know what this project is and what are its goals, so maybe GPL may be fine here. Still, I would avoid it.

@ocefpaf thanks for the suggestions!


Frontend Masters lineman install issue

Hello,
I'm just following along on your course on FEM and I have just run into an issue. When doing an npm install from the lineman directory I get this nasty looking error

<EMAIL_ADDRESS>install /Users/name/Development/tutorial-machine/build/js-testing/real-world-testing-video/lineman/node_modules/png
node-gyp rebuild
/bin/sh: pkg-config: command not found
gyp: Call to 'pkg-config libpng --libs' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/name/.nvm/versions/node/v6.5.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 15.6.0
gyp ERR! command "/Users/name/.nvm/versions/node/v6.5.0/bin/node" "/Users/name/.nvm/versions/node/v6.5.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/name/Development/tutorial-machine/build/js-testing/real-world-testing-video/lineman/node_modules/png
gyp ERR! node -v v6.5.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS><EMAIL_ADDRESS>install: node-gyp rebuild
npm WARN<EMAIL_ADDRESS>Exit status 1
<EMAIL_ADDRESS>/Users/name/Development/tutorial-machine/build/js-testing/real-world-testing-video/lineman
└── (empty)
npm ERR! code 1

Looking into the issue it looks like one of the PNG dependencies is broken, but after the issue was raised there's no fix https://github.com/pkrumins/node-png/issues/50.
Is this something you have come across or could verify if it is an issue for you too. I'm on OSX 10.11.6.
Great course by the way!

First, thanks for the kind words about the course.
Second, yes I see this too:
><EMAIL_ADDRESS>install /Users/justin/code/testdouble/real-world-testing/lineman/node_modules/png
> node-gyp rebuild

Package libpng was not found in the pkg-config search path.
Perhaps you should add the directory containing `libpng.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libpng' found
gyp: Call to 'pkg-config libpng --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/justin/.nodenv/versions/6.3.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Darwin 16.0.0
gyp ERR! command "/Users/justin/.nodenv/versions/6.3.0/bin/node" "/Users/justin/.nodenv/versions/6.3.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/justin/code/testdouble/real-world-testing/lineman/node_modules/png
gyp ERR! node -v v6.3.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS><EMAIL_ADDRESS>install: `node-gyp rebuild`
npm WARN<EMAIL_ADDRESS>Exit status 1

><EMAIL_ADDRESS>install /Users/justin/code/testdouble/real-world-testing/lineman/node_modules/webdriver-http-sync
> node-gyp rebuild

  CXX(target) Release/obj.target/curllib/curllib.o
  SOLINK_MODULE(target) Release/curllib.node
clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9

I don't really have a great answer for you 😦  -- @davemo, thoughts?

I was able to continue with the FEM course by globally installing lineman


openrouter/openai/o1-preview is not known?!

openrouter/openai/o1-preview is changed to gpt-4o-mini?!
command aider '--map-tokens=0' --gitignore --no-dirty-commits --vim --no-suggest-shell-commands --model openrouter/openai/o1-preview --editor-model openrouter/deepseek/deepseek-coder --edit-format whole --no-auto-commits MAI.lisp
─────────────────────────────────────────────────────────────────────────────────────
Add .aider*, .env to .gitignore (recommended)? (Y)es/(N)o [Yes]:
Added .aider*, .env to .gitignore
Warning for openrouter/openai/gpt-4o-mini: Unknown context window size and costs,
using sane defaults.
Did you mean one of these?
- openrouter/openai/gpt-4
- openrouter/openai/gpt-4o
- openrouter/openai/o1-mini
For more info, see: https://aider.chat/docs/llms/warnings.html
You can skip this check with --no-show-model-warnings

Thanks for trying aider and filing this issue.
The fix is available in the main branch. You can get it by installing the latest version from github:
aider --install-main-branch

# or...

python -m pip install --upgrade --upgrade-strategy only-if-needed git+https://github.com/Aider-AI/aider.git

If you have a chance to try it, let me know if it works better for you. I'm going to close this issue for now, but feel free to add a comment here and I will re-open. Or feel free to file a new issue any time.


New option to apply device tree overlays at runtime.

Description of changes
NixOS can apply device tree overlays by means of the hardware.deviceTree.overlays option. However, it is very useful to be able to apply pre-built overlays in runtime, without recompiling the whole device tree. This PR introduces a new option hardware.deviceTree.runtimeOverlays you can use to specify the overlays you want to apply at runtime. The list of overlays is handled by the extlinux config generator and ends up in the FDTOVERLAYS option. This option is understood by u-boot, which applies the requested overlays to the device tree.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3652


[TB] Implement dark mode

Problem/Concern
Dark mode is not fully implemented for all molecules/components.
Proposed Solution
Add css rules for .darkmode on existing classes as needed to implement the molecules and components.

Group buttons & lists are still in progress.


[Do not merge] Code review

Pull request will all tsmean code - just for Github UI purposes.

hm, i guess refactoring to “app-bla" would be “best practice”? what I thought is e.g. have the user module components prefixed with user, the animal module components prefixed with animal etc.
that way it’s easier to make a library out of parts of the application. but refactoring is also fine for me… you can decide.
About the rule, if it’s possible to have multiple prefixes we could do that, or if not kick the rule out.

On 13 Feb 2018, at 18:16 , Michał Lytek<EMAIL_ADDRESS>wrote:
@19majkel94 commented on this pull request.
In frontend/tslint.json https://github.com/tsmean/tsmean/pull/3#discussion_r167936673:

"variable-name": false,

"whitespace": [

 true,

 "check-branch",

 "check-decl",

 "check-operator",

 "check-separator",

 "check-type"

],
"directive-selector": [

 true,

 "attribute",

 "app",

 "camelCase"

],
"component-selector": [
What do you mean? We can refactor all components to app-something or disable that rule.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/tsmean/tsmean/pull/3#discussion_r167936673, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ34pdPzJI_BKkVwHtfkfU3kSDvk93c0ks5tUcNzgaJpZM4SCGti.

Okay good. I don’t know NEST well yet, so I didn’t understand that this was needed, but now i get it, thanks.

On 13 Feb 2018, at 18:20 , Michał Lytek<EMAIL_ADDRESS>wrote:
@19majkel94 commented on this pull request.
In backend/src/animal/animal.controller.ts https://github.com/tsmean/tsmean/pull/3#discussion_r167937987:

   });

 })

 .catch(err => {

   if (err.message === 'Animal already exists') {

     res.statusMessage = err.message;

     res.status(403).send();

   } else {

     res.statusMessage = err.message;

     res.status(500).send(err.message);

   }

 });

}

@Get()
async find(options?: FindManyOptions): Promise<Animal[]> {
const defaultOptions = {
Yes, we should use @Query decorator to allow GET /animals?skip=100&take=25

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/tsmean/tsmean/pull/3#discussion_r167937987, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ34pcuM06iFcVUuY3j1xafeih8dkBOcks5tUcRvgaJpZM4SCGti.

(even though the controller doesn’t really do anything with the query params yet)

On 13 Feb 2018, at 18:23 , Daniel Niederberger<EMAIL_ADDRESS>wrote:
Okay good. I don’t know NEST well yet, so I didn’t understand that this was needed, but now i get it, thanks.

On 13 Feb 2018, at 18:20 , Michał Lytek<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
@19majkel94 commented on this pull request.
In backend/src/animal/animal.controller.ts https://github.com/tsmean/tsmean/pull/3#discussion_r167937987:

   });

 })

 .catch(err => {

   if (err.message === 'Animal already exists') {

     res.statusMessage = err.message;

     res.status(403).send();

   } else {

     res.statusMessage = err.message;

     res.status(500).send(err.message);

   }

 });

}

@Get()
async find(options?: FindManyOptions): Promise<Animal[]> {
const defaultOptions = {
Yes, we should use @Query decorator to allow GET /animals?skip=100&take=25

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/tsmean/tsmean/pull/3#discussion_r167937987, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ34pcuM06iFcVUuY3j1xafeih8dkBOcks5tUcRvgaJpZM4SCGti.


chained tagged_with throws ActiveRecord::StatementInvalid: Mysql2::Error: Not unique table/alias error

Activity Load (1.0ms)  SELECT `activities`.* FROM `activities` JOIN taggings activities_taggings_531c2fd  ON activities_taggings_531c2fd.taggable_id = activities.id AND activities_taggings_531c2fd.taggable_type = 'Activity' AND activities_taggings_531c2fd.tag_id = 33 AND activities_taggings_531c2fd.context = 'skills' JOIN taggings activities_taggings_a841373  ON activities_taggings_a841373.taggable_id = activities.id AND activities_taggings_a841373.taggable_type = 'Activity' AND activities_taggings_a841373.tag_id = 37 AND activities_taggings_a841373.context = 'skills' JOIN taggings activities_taggings_531c2fd  ON activities_taggings_531c2fd.taggable_id = activities.id AND activities_taggings_531c2fd.taggable_type = 'Activity' AND activities_taggings_531c2fd.tag_id = 33 AND activities_taggings_531c2fd.context = 'skills'

ActiveRecord::StatementInvalid: Mysql2::Error: Not unique table/alias: 'activities_taggings_531c2fd': SELECT `activities`.* FROM `activities` JOIN taggings activities_taggings_531c2fd  ON activities_taggings_531c2fd.taggable_id = activities.id AND activities_taggings_531c2fd.taggable_type = 'Activity' AND activities_taggings_531c2fd.tag_id = 33 AND activities_taggings_531c2fd.context = 'skills' JOIN taggings activities_taggings_a841373  ON activities_taggings_a841373.taggable_id = activities.id AND activities_taggings_a841373.taggable_type = 'Activity' AND activities_taggings_a841373.tag_id = 37 AND activities_taggings_a841373.context = 'skills' JOIN taggings activities_taggings_531c2fd  ON activities_taggings_531c2fd.taggable_id = activities.id AND activities_taggings_531c2fd.taggable_type = 'Activity' AND activities_taggings_531c2fd.tag_id = 33 AND activities_taggings_531c2fd.context = 'skills'

This occurs when chaining tagged_with and tagged_with the same tag again-- for ex:
Activity.tagged_with(["problem solving", "critical thinking"], on: :skills).tagged_with("problem solving", on: :skills)
The use case is when you have a list of items already filtered by a tag and you want a count of a certain tag within that filtered group. In the use case above, you have a list of activities with the skill.
The error is recent and only started happening when we upgraded to rails 4.2x
Our solution while not optimal, has been to re-grab the records with the original tagged with and then run tagged with again on it.

I also have this same issue.

Just curious, did you have this when you were using match_all?  I had this issue when I was using match_all: false and changing it to any: true made the issue disappear.