Importing Wakatime JSON exports

Is there currently a plan to allow for importing JSON exports provided by Wakatime? This would be a beneficial feature for those looking to switch from Wakatime to a self-hosted solution.

Hi @PotatoPlank, thanks for your feature request. Having the ability to import data from Wakatime would indeed be a desirable functionality.
However, a major issue here is the fact that you can only export aggregated data, i.e. summaries, from Wakatime. As far as I know, there is no way to download raw heartbeats, as they're potentially not even persisted on their side anyway.
In Wakapi, heartbeats are the "source of truth", while aggregated summaries are considered volatile and are being derived from heartbeats. Wakapi bases on the assumption that summaries can be dropped and recomputed at any time. We would lose this flexibility if we imported prepared summaries from Wakatime.
What we could to is distinguish between volatile and persistent summaries, whereas such imported from Wakatime would have a flag like persistent: true, indicating that they must not be deleted ever. This would certainly add complexity to out summary computation logic, but enables for a valuable feature on the other hand.
Somebody else interested in this as well?

Hi @muety, makes sense. You're correct that all of the data they provide is just summaries.
I took a brief look at the Wakapi database structure to get an idea how the summaries were being calculated. I personally didn't see how the Wakatime data could be easily imported.
The persistent flag sounds like a good idea. If I think of anything else, I'll add it here.
Thanks for the response!

Duplicate of #87.

Duplicate of #87.


Reverted Maxime's changes for pink theme

This version is based on "Light Theme".
Recent changes for Pink theme has been reverted.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Error when opening settings on windows 10 64bit

failing on this line
icon = Icon.FromHandle(hIconEx[0]);

... when right-clicking the tray icon.

OK, as it seems that there are no reactions for a long time, I have corrected this issue in a forked branch:
https://github.com/MisterY/AudioSwitch/releases/tag/<IP_ADDRESS>

Fixed in latest version


connect to provisioner socket

Describe what this PR does
in current deployment, liveness container is connecting to csi.sock socket which is exposed by node plugin, not the provisioner
is listening on csi-provisioner.sock. the liveness container inside the provisioner pod should connect to the provisioner socket, not the node plugin socket
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:

Kubernetes links that explain why the change is required
CSI spec related changes/catch-up that necessitates this patch
golang related practices that necessitates this change

Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #619
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.

I am assuming the Helm changes will come in through the other PR that @wilmardo is working on.

yes @ShyamsundarR that's the plan, so thats why I have not done any changes to helm chat

@Madhu-1 this should be backported to 1.2.0 , Isnt it ?

@humblec yes this need to be backported once PR is merged will send backport PR

@humblec PTAL

@Madhu-1 PR description has to be updated.

@Madhu-1 PR description has to be updated.

@humblec didnt get what changes i need to make?

@Madhu-1 PR description has to be updated.

@humblec didnt get what changes i need to make?

Is there anything that requires special attention
Do you have any questions?

Is the change backward compatible?

Are there concerns around backward compatibility?

Provide any external context for the change, if any.

For example:

Kubernetes links that explain why the change is required
CSI spec related changes/catch-up that necessitates this patch
golang related practices that necessitates this change
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.

Above can be removed from the PR description @Madhu-1

@humblec done

LGTM. Approved.


Rebuild the project on changes in multiple directories?

What version of Wrangler are you using?
2.0.6
What operating system are you using?
macOS
Describe the Bug
Hi!
In my project, I have two packages: one for the core app, and another for Workers-specific implementation; the latter references the former as a local dependency. Currently, wrangler dev tracks changes and rebuilds the project only when it detects changes—which are relatively rare—in the implementation package.
Is there a way to make wrangler track changes in additional folders?

Currently this is not possible. Related issue https://github.com/cloudflare/wrangler2/issues/703

Ideally, our bundling process should track changes to the dependency.
@yakovmanshin could you provide a real example of the setup that is problematic for you?

Hi @petebacondarwin! Sure!
In my project, one package contains platform-independent code (where most of the work is done), and another is for the Workers-specific implementation (literally a couple of files which rarely change).
/
|
|- core/
|  |- src/
|  |- package.json
|  |- tsconfig.json
|
|- cf/
|  |- src/
|  |- package.json
|  |- tsconfig.json
|  |- wrangler.toml

In cf/package.json, core is linked as a local dependency:
"dependencies": {
    "core": "file:../core"
},

When wrangler dev runs (from within the cf directory), core is built and pulled in cf:
[build]
command = "<…>"
# The build command above:
# (1) installs `core` dependencies
# (2) builds `core`
# (3) installs `cf` dependencies (including `core`)
# (4) builds `cf`

While wrangler dev is running, it’s observing file changes—but only in cf—and rebuilds the entire project (including core) using the build command. So basically it is possible to debug changes in core without relaunching the server; however, wrangler won’t act on them until something changes in cf.

OK, so our bundler knows about the file that is being imported (e.g. ../core/dist/index.js) so if that changes then the cf project will rebuild. But it is not aware of the source files that are used to generate this core distributable.
One workaround, rather than using the custom build rule to bundle the core project, would be to have a separate process watch the core project and rebuild it when it changes. This will cause the core distributable to update and trigger wrangler dev on the cf project to trigger a rebuild.

Here is an example: https://github.com/petebacondarwin/cf-external-dep-demo

I don't think I would recommend having the core library build as part of your cf custom build step since it tightly binds these two, and I would expect the core project to need its own processes anyway.
But we could consider making the watch_dir accept an array or a glob maybe, which I think would resolve this too.

Needed this for the weekend, so I'm sending a quick PR

(We do support globs already btw)


Add Heteroscedastic Gaussian Likelihood

Codecov Report

Merging #17 into master will increase coverage by 1.13%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   62.50%   63.63%   +1.13%
==========================================
  Files           3        3
  Lines           8       11       +3
==========================================
+ Hits            5        7       +2
- Misses          3        4       +1

Impacted Files
Coverage Δ

src/GPLikelihoods.jl
100.00% <ø> (ø)

src/likelihoods/gaussian.jl
57.14% <66.66%> (+7.14%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2b89c26...ccdc777. Read the comment docs.

@devmotion @willtebbutt @theogf Any objections to merge this?

Also, patch bump please :)


Run the no-commit-to-branch check only locally

It does not make sense to run this pre-commit check in pull requests or when merging to the main branch on GitHub.

I got confused by "It does not make sense to run it when merging to main." as almost every PR is aiming to be merged into main. But as gh runs action after it is merged then OK to disable it.
BTW summary and PR doesn't match - this PR disables whole pre-commit, not just one hook, right? Is there a way to disable just this check?

Is there a way to disable just this check?

Hm, don't know if it's possible to only disable a specific check. @thrix, any hint?

BTW summary and PR doesn't match - this PR disables whole pre-commit, not just one hook, right?

Ah, right, will update the title if we keep it as it is.

Interestingly, in the Artemis project, pre-commit runs after merge event, against main, and it reports no problems with main branch... I'm puzzled :/

Interestingly, in the Artemis project, pre-commit runs after merge event, against main, and it reports no problems with main branch... I'm puzzled :/

Hmmm, that's really weird.

@psss An attempt to disable single hook.

Great! Thanks for preparing this. Tried with 8366c74f and confirm it works nicely! Let's approve and merge soon!

Doing a code search. Examples with --branch seem to be using pre-commit-ci. Without it the default is to use master and main, qnd I see it used with the pre-commit action without erroring 🤷♂

Nope, no idea why it works in Artemis and fails here. no-commit-to-banch is apparently executed against main at https://gitlab.com/testing-farm/artemis/-/jobs/6784553461#L435, and it's green and happy. The only idea I have is that it's not checking any new commit, it's running against main that's been already enriched with new commits, it's done and no changes are pending to be committed to main. Is that different than Github actions we saw fail? Running before the actual merge? I suppose in that case this check might start to complain.

Just a quick question - why not add it directly to the workflow env: key?

Yeah, now that the condition was dropped this can be simplified. Updated.

Also updated to the latest versions of actions to get rid of the warnings.


Fix call to logging._level

I just installed your excellent library on an ESP32, and got it working by making this change. I can't say I've read every line of your library and logging.py but it looks like maybe logging._level was removed at some point after you wrote the library?
Anyway I think using self._log.level seems to be the right fix.

An additional fix, to get the logging levels to work (I wanted to disable logging by setting logLevel to WARNING) I had to as make the change in the second commit

Any updates on this? I'm pretty sure it works and you could just merge it.


is it possible to create separated "work" sections?

i would like to create separated work sections - each for different category. Can it be done easily?
Thanks!

I tried it by changing the template logic and the settings in the console, but I see the main problem in Javascript part. I'm not familiar with the (JS) codebase itself nor I'm an expert in JS itself.

@digitalcraftsman thanks!


Finalization logic for foreign field arithmetic and keccak primitive gates

Already have an issue to track this.. so closing.


[FLINK-6747] [table] [docs] Time attributes section added

This documents the Table API's time attributes.
CC @fhueske @alpinegizmo

Thanks for the feedback @alpinegizmo and @fhueske. I hope I addressed all your comments. I will merge it.


T34551 remove system pages from history

https://phabricator.endlessm.com/T34551

@dylanmccall I'm bad with github suggestions UI, but here is a branch with 2 commits on top to fix what I'm seeing in testing: https://github.com/endlessm/kolibri-installer-android/pull/109


[PDI-20145] - Remove version checker from PDI

kettle-version-checker plugin was performing the version check. We have removed the plugin from the pdi assembly

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 24m 2s
Build command:
mvn clean verify -B -e -Daudit -Djs.no.sandbox -pl \
assemblies/plugins,plugins

:exclamation: No tests found!
:information_source:  This is an automatic message


pin nock beta

Maybe fixes https://github.com/replicate/replicate-javascript/issues/237

That didn't work. It's the latest version of Node 20 to blame.


Digital twins architecture

In the technical architecture, IoT digital twins provide the visibility and monitoring of things and related events (e.g., using IoT devices to automatically capture the origin of a product), and blockchain enables the shared single version of the truth as to the state of these things across their life cycles and associated business events.
Robonomics Parachain provides an opportunity to create a model of a digital twin and update its state every 6 seconds, and important today describe the architecture of this.

Probably, it could be fixed by adding documentation into https://github.com/airalab/robonomics/blob/master/robonomics/frame/digital-twin/src/lib.rs#L18

Implemented in pallet-digital-twin


Apply a business created profile to a Codeset

Please fill in the sections below, adding/removing information where applicable:
Description
When attempting to apply a profile (in this case DD4C Profile (Standard)) to a Codeset, the system failed, presenting a failure message "There was a problem getting the selected profile".
Steps to reproduce - please see attached error report which shows screen shots taken whilst producing the error.
error report.docx
Error details
{
  "headers": {
    "normalizedNames": {},
    "lazyUpdate": null
  },
  "status": 404,
  "statusText": "OK",
  "url": "https://modelcatalogue.cs.ox.ac.uk/nhsd-test/api/codeSets/b84af776-c1e3-4736-ad64-c17601517ede/profile/uk.ac.ox.softeng.maurodatamapper.profile.provider/DD4C+Profile+%28Standard%29",
  "ok": false,
  "name": "HttpErrorResponse",
  "message": "Http failure response for https://modelcatalogue.cs.ox.ac.uk/nhsd-test/api/codeSets/b84af776-c1e3-4736-ad64-c17601517ede/profile/uk.ac.ox.softeng.maurodatamapper.profile.provider/DD4C+Profile+%28Standard%29: 404 OK",
  "error": {
    "path": "/api/codeSets/b84af776-c1e3-4736-ad64-c17601517ede/profile/uk.ac.ox.softeng.maurodatamapper.profile.provider/DD4C+Profile+(Standard)",
    "resource": "ProfileProviderService",
    "id": "uk.ac.ox.softeng.maurodatamapper.profile.provider:DD4C+Profile+(Standard)"
  }
}

@alanpnhs can you try renaming the profile without the brackets …. And then try applying it again.
I curious if this is a brackets issue or something else

@olliefreeman I created a new profile, without the use of brackets, this time simply, DD4C Profile Trimmed. This 'almost' worked, in that it took me further on, but when I applied this new profile, whilst it prompted me to complete appropriate values it wont accept what appears to be a valid date.  The data element is Assurer Date, which has a data type of Date - primitive. The UI presents , dd/mm/yyyy but entering several variations of dates (matching that structure) it continues to display the error message "the field must be a valid Date" (screenshot provided below). So it looks like the brackets do seem to be creating an issue. Curious. Let me know if I need to raise a separate issue for the date validation issue (for traceability purposes etc).

OKay, so

i'm gonna move this to mdm-core as its a "Searching" issue in the backend...may or may not be resolvable. @jamesrwelch  We may need to be clear that dynamic profile DMs cannot contain anything other than alphanumeric characters at this point in time
we have an update in the next release which allows customisation at the admin point for date formats for the profile date fields. it shoudl currentlt recognise 'dd/MM/yyyy', 'dd-MM-yyyy', 'MM/dd/yyyy', 'MM-dd-yyyy', 'yyyy/MM/dd', 'yyyy-MM-dd' though with no alterations. Can you raise a ticket pls


Implement statistics collection

Need to collect some sort of stats so that something can be evaluated

This has been fixed however some of the results do not look quite right and should be fixed.

This is corrent, the incorrect looking results were because the same simulation was run again because some of the parameters were missed


[ci:component:github.com/gardener/oidc-webhook-authenticator:v0.24.0->v0.25.0]

Release Notes:
Logging was enhanced to indicate that a handler was removed from store when an `openidconnect` resource was not found.

OWA is now built using go version `1.21.2`.

Administrators can now configure OpenIDConnect objects to retrieve additional claims from the JWT token using the new extraClaims field. The client (kubectl, web application, etc.) is responsible for requesting the scopes that will provide these claims upon authentication.

/hold
I think we should release new version of OWA which will make this PR obsolete

Shouldn't we still merge it in order to deliver the release notes?

The next auto-upgrade PR bumping from 0.24 to 0.26 will deliver them. So, no need to merge this one.

The next auto-upgrade PR bumping from 0.24 to 0.26 will deliver them.

Oh, I didn't know that. Then we can hold this one in favour of the upgrade to 0.26 directly.


Fixed #1273 : Add a battery low mode in settings

Description
Image will not load if battery is low
Related issues and discussion
#1273
Screen-shots, if any
Checklist

Hey @PrajwalM2212,
Your changes looks good to me!


Codespace is broken

ADD ISSUE DESCRIPTION HERE
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0
Embedder: codespaces

Cannot access CS50 extensions in codespace after rebuild

/question please use your CS50 course support channel.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Support Ubuntu 22.04, jammy

Thanks! Nice that now can get rid of many of the special cases/exceptions.

Yes. I hope we don't have to bring some of this code back ...


Secondary part of content

Add information blocks to the cat resume.

Cool. Cat resume is awesome!


Support InternVL 1.5

Strong model with great capabilities:
https://huggingface.co/OpenGVLab/InternVL-Chat-V1-5

with some OCR tests, the best OS that i've tested

Any Plan for support this model?

+1


ISPN-6504 Try to use the index even if the query matches all entries

https://issues.jboss.org/browse/ISPN-6504
https://issues.jboss.org/browse/ISPN-6506

pulling

merged, thanks @anistor


Question about Checkpoints of pretrained models

hi
I got some trouble when I tried to download the checkpoint of pre-trained models.
Files which I downloaded from google drive links cannot be uncompressed or viewed correctly. The error is "tar: This does not look like a tar archive"
I'm wondering did I do it in a wrong way and Is there another download link?
It troubles me a lot, could you please offer some advice.
Thanks!

i also meet this problem, did you solve it ?

I meet the same issue, how do you solve it ?


Container webhook changes when I manually recreate container

Bug description
When we enable a container webhook we get a URL that we can use to recreate container using CURL.
But when we do a manual recreate the URL of a webhook changes
Expected behavior
The URL should be persistent when we do a manual Recreate of a container.
Portainer Logs
N/A
Steps to reproduce the issue:

Go to container details
Enable container webhook
Copy the link
Do a manual Recreate with Pull latest image
The webhook URL changes

Technical details:

Portainer version: 2.14.1
Docker version (managed by Portainer):
Kubernetes version (managed by Portainer):
Platform (windows/linux):
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
Browser:
Use Case (delete as appropriate): Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? No

Additional context
I'm using webhooks in a CI/CD environment, so on every build, I call that webhook to refresh the container and deliver the latest version on dev environment.

Thanks for this - this is something that we're aware of and have an internal issue open around, so I've added your feedback to this.
The reason this happens is because when you recreate a container you're actually deleting the container then creating a new one with the same settings as the original. The new container gets a new webhook URL as part of this. Ideally we'd carry over the existing URL to the new container.

@jamescarppe thank you for confirming the error.
I noticed that the container id changes after recreation, so maybe pair the webhook URL with the container name, it isn't changing when recreating.
Recreating a container via a webhook is different than recreating via an action button because a webhook recreates the container and preserves the webhook url, but recreating via a button changes the url. Why the difference?

@jamescarppe any updates on this?

This is with our engineering team who are looking at fixing it in a future release. I don't have an ETA for it at this stage sorry.

@jamescarppe thank you for the update :)

Any updates? 🙂

I believe this fix is flagged for 2.17. There look to have been some code conflicts that meant it didn't quite make it into 2.16 unfortunately.

@jamescarppe is this fixed in 2.17?

A fix for this was rolled out as part of 2.17.0. Are you able to confirm whether this fixed the problem for you?

This does not seem to be fixed. If I have a webhook on a container and I press "Pull and redeploy" in the stack all containers connected to that stack will lose their webhooks. Basically still the same as reported by @Misiu. The container webhook will be disabled after redeploying the stack.

@fgroenendijk I think the issue is different.
My problem was on the container level. I use Recreate with Pull latest image option checked and the webhook changed (the URL).
Sadly I'm still waiting for the update on my server, so I'm not able to confirm if version 2.17 fixed the issue. @jamescarppe I have this on my TODO list :)
@fgroenendijk maybe create a separate issue for the behavior you have, it's clearly a bug to me.

@Misiu You're right, it's slightly different, I will create a separate issue. I might have been hoping the issue was the same ;)

@Misiu
I wanted to follow up this request.  Have you been able to upgrade and confirm that 2.17 resolved your issue?
Thanks!

@fgroenendijk did you create a separate issue for stacks (webhooks disabled, so when enabling we get a new URL).
I can't find it anywhere and I want to track it.

Manually clicking "Recreate" in portainer dashboard keeps an existing webhook.
Howver, calling docker-compose -f docker-compose.yml up causes a loss of a previously activated webhook.

Manually clicking "Recreate" in portainer dashboard keeps an existing webhook. Howver, calling docker-compose -f docker-compose.yml up causes a loss of a previously activated webhook.

This is because the docker-compose CLI command destroys the stack and creates it as new, whereas when it's done within Portainer we "cheat" a bit and save the webhook and associate it with the new stack. The docker-compose CLI doesn't know anything about Portainer or webhooks so has no way of doing this.

@fgroenendijk did you create a separate issue for stacks (webhooks disabled, so when enabling we get a new URL). I can't find it anywhere and I want to track it.

@jamescarppe Keeping existing webhooks even on stack recreation seems to be a planned feature.

hi - any eta on this feature? without a static webhook it makes redeploying containers via an external call not possible

@fgroenendijk did you create a separate issue for stacks (webhooks disabled, so when enabling we get a new URL). I can't find it anywhere and I want to track it.

@MStumpp @eugene-pattern @Misiu
It looks like someone has opened this as a separate issue now - #8929 - so let's track that there. This issue was specific to this happening on containers, whereas the new issue is on stacks. As the container side of the equation has been fixed, I'm closing this issue. For the stack side, refer to #8929.


Allow template7 page rerendering

Its possible to update template7 pages with new data.

This looks to be of some interest. @valnub ?

@ZanderBrown Yeah, but Vladi knows F7 core rendering functionality better than me, so he'll have to decide if this gets merged.

@valnub sure, i was just going through the older issues/pr's and saw that this seemed to have gone unnoticed.
So @nolimits4web what do you think?

@nolimits4web
Please add this. It's amazing!

:+1:

@nolimits4web
What's up? Please merge it :)

@J05HI you will notice that there are merge conflicts, hence the red label

Yeah then @antono should fix them

I'll fork it and fix the merge conflicts.

@J05HI PR still has merge conflicts that @antono hasn't resolved

@ZanderBrown
You can close this now because of #1391.

Okay closing in favour of #1391


Add support for DMA-based reading from USART

Based on #260. I recommend reviewing/merging that one first.
Close #124.

Rebased, ready for review.
@david-sawatzke: To address your comment on #260, I've pushed a commit that panics, if the buffer is too long. Is that what you had in mind? I don't think a Result makes sense, as this is going to be a programmer error that is not recoverable.


Update to Tricia (alternate approach)

Per some conversation, this cleans up the beta process a bit and would replace PR #360.

This is my preferred approach to adding the beta support

Pretty sure I've always used master to build the images, unless I'm testing a PR. Branching the release usually happens after we've built an image, and got master working against it.


"execSync incompatible with installed nodejs" on 0.3.1

Version 0.3.1 cannot be used on Windows:
Running "shell:check-compass-installation" (shell) task
[Error: %1 is not a valid Win32 application.
...\gruntjs\node_modules\grunt-shell-spawn\node_modules\execSync\win32\v0.10\shell.node]
Warning: execSync incompatible with installed nodejs Use --force to continue.

Aborted due to warnings.
grunt process exited with code 3

The shell.node is not a valid Win32 application.
Works perfectly fine on 0.3.0

This is addressed by #35.


Pseudonyms for user names for other components

Keep Pseudonym on all tables, and all logs.
Keep only one mapping table for real (identifiable) user name vs Pseudonym.
Delete user from the mapping upon user deletion request

We introduced "Privacy Toolkit", which has "Forget-Me" function for RDBMS, Logs, and analytics.
https://github.com/wso2/identity-anonymization-tool
Closing this as this is done in a different mechanism.


Fails in Godot 3.1.aplha.custom

I try to investigate better when return from work.

Add a pull request
https://github.com/OBKF/Fake-Interior-Shader-for-GodotEngine/pull/2


How to restart a new session after the first conversation completion

Rasa Core version:
0.8.0
Python version:
3.5
Operating system (windows, osx, ...):
Windows 64bit
Issue:
It performs perfect as the story template, but after the completion of the last response, a new conversation never start no mater whatever I input.
Content of domain file (if used & relevant):
slots:
  bg:
    type: text
  region:
    type: text
  year:
    type: text
  period:
    type: text
  indicator:
    type: text

intents:
  - greet
  - query_finance
  - inform

entities:
 - year
 - period
 - region
 - indicator

templates:
  utter_greet:
    - "Hi"
  utter_ask_indicator:
    - "What indicator do you want?"
  utter_ask_region:
    - "Which region"
  utter_ask_time:
    - "When"
  utter_resp_indicator:
    - "Indicator queried {year}{period}{region}{indicator}is 1243"
  utter_goodbye:
    - "Bey~"

actions:
  - utter_greet
  - utter_goodbye
  - utter_ask_indicator
  - utter_ask_region
  - utter_ask_time
  - utter_resp_indicator
  - fin_bot.ActionIndicatorSearch

Content of story file (if used & relevant):
* greet
  - utter_greet
  - utter_ask_indicator
* query_finance{"indicator": "Sales"}
  - slot{"indicator": "Sales"}
  - utter_ask_region
* inform{"region": "Asia Pacific"}
  - slot{"region": "Asia Pacific"}
  - utter_ask_time
* inform{"period": "Feb."}
  - slot{"period": "Feb."}
  - action_indicator_search
  - utter_goodbye

What command did you use to train the bot?

@tmbo the issue has been resolved.
  - action_restart

action_restart will start new conversation.
Thanks

@zxsimple -action_restart ..is this built in one or user defined ? How do we use it ?

@poorni19 its built-in action，just put at last of each story.

@zxsimple Thank You !!

hii all I have putted action_restart at the end of each story(as mentioned by @zxsimple ).. now I am unable to figure out how it should putted in domain file?? I have putted under actions in following manner:
- ActionRestart
- actions.action.ActionRestart
- action.ActionRestart

But I am getting following error in every case while training the dialogue model:
ValueError: Action 'action.ActionRestart' doesn't correspond to a template / action. Remember to prefix actions that should utter a template with utter_. Error: No module named action

@zxsimple do we have to declare -action_restart in domain file?

@zxsimple having the same issue...seems as though action_restart is no longer built in?

Not sure what you mean, but action_restart is still part of Rasa Core and has not been removed. Given that this issue is closed, please open separate issues for your problems so we can discuss them in detail there.


Revert "[Feature] Render job views on school and school/vacancy pages"

Reverts dxw/teacher-vacancy-service#542
Trello card url
https://trello.com/c/XJ1NYMi6/536-revert-https-trellocom-c-bnbjjjbi-from-develop-to-ensure-it-is-not-deployed
Screenshotsof UI changes
After

 Bug: "back" link from a job page doesn't persist search query


Ext not working on Vs code Insiders

VSCode:

Version: 1.50.0-insider
Commit: bc38b0accb3c62180317c63dbe7323200977db0f
Date: 2020-09-11T12:27:36.137Z
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 3.10.0-1127.19.1.el7.x86_64

EXT:

Name: Kubernetes
Id: ms-kubernetes-tools.vscode-kubernetes-tools
Description: Develop, deploy and debug Kubernetes applications
Version: 1.2.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.vscode-kubernetes-tools

When launching the extension I get this error even after launching vscode with the cmd switch:
[ms-kubernetes-tools.vscode-kubernetes-tools]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-kubernetes-tools.vscode-kubernetes-tools

Update to vs code fixed the issue.


Email and Text Message is not sent when skipSuccessScreen is provided.

See sum-up payment code below, donationAmount provided through app.  Email address and/or mobile phone number is also provided.
When the skipSuccessScreen is provided the app does not send the receipt to the customer/client.
SumUpPayment payment = SumUpPayment.builder()
// mandatory parameters
.total(new BigDecimal(donationAmount)) // minimum 1.00
.currency(SumUpPayment.Currency.GBP)
// optional: add details
.title("Donation")
.receiptEmail(emailAddress)
.receiptSMS(phoneNumber)
// optional: foreign transaction ID, must be unique!
.foreignTransactionId(UUID.randomUUID().toString()) // can not exceed 128 chars
//.skipSuccessScreen()
.build();

Hi Gary
Correct, the SumUp SDK allows you to pre-fill the success screen for receipt email/SMS sending but the skipsuccessscreen cannot be used. However we will update you if anything changes.  Sorry for the inconvenience.
James


Integrate the mysql / postgres driver to the data and full stack

It should be discussed on the dev mailing list first.

It has been decided to not add it to a distribution, as the distribution system is going to be changed in 3.2.0.


Initial prep for multiple specifications under OAI

Update index page and README to showcase multiple specifications.

Update copyright year to 2024

Changes:


Use macro-like functionality for tutorial branches

In some of our tutorials (like https://github.com/ros2/ros2_documentation/blob/rolling/source/Tutorials/Workspace/Creating-A-Workspace.rst), we instruct the user to checkout repositories at a certain branch.  This is fine, but when we go to branch off a new release, we have to go through these instructions manually and update these branches in multiple places.  It would be better if we used some kind of Sphinx substitution here and just automatically replaced the branches with the name of the distribution.  Note that an important piece here is that the branches have to actually exist on the destination repository.

This has been implemented in #1694 and #1705, so I'll close this issue.


Create a link to new result app

Add link to the result app (http://glug.nith.ac.in/result/) at some suitable place.

Added the link in the projects page.


Why so pedantic?

This comment nicely explains why we have such high standards for drive-by contributions. We should incorporate it into the README.

What frustrates me: there should be automation for all that is possible to automate.
The degree of automation still is relatively low (at least in my perception compared to other projects).
So thank you for this project! I hope it will make it into a bot, soon.

So basically:

We have high standards for drive-by contributions because we have to maintain it afterwards.

It's actually the same as any other open source project.

So basically:

We have high standards for drive-by contributions because we have to maintain it afterwards.

It's actually the same as any other open source project.

Right, I have often seen people to not realize that or keep forgetting that.

Right, I have often seen people to not realize that or keep forgetting that.

Well, since we all enjoy philosophical discussions, let's not forget the all-embracing underlaying fundamental truth that contribution of any sort emanates out of a scarse resource itself.
The fact that there are usually more contributors than maintainers is a systemic skew which should not be misunderstood on the individual level. It is hard not to fall in this perception trap.
It should be always the optimal strategy to lower friction for both sides of this interaction.
The natural leadership here is upon the maintainers.

Well, since we all enjoy philosophical discussions, let's not forget the all-embracing underlaying fundamental truth that contribution of any sort emanates out of a scarse resource itself.
The fact that there are usually more contributors than maintainers is a systemic skew which should not be misunderstood on the individual level. It is hard not to fall in this perception trap.
It should be always the optimal strategy to lower friction for both sides of this interaction.
The natural leadership here is upon the maintainers.


Resizing the page with the card submit modal open hides modal

If you open the card submit modal fullscreen and change the size of the browser to width <768px, the modal will disappear and you have to resize to >=768px to see it again.
Same in reverse <768px to >=768px will cause the same issue.
This is caused by there being two different modals for submitting cards, one for mobile size, one for browser size.
Fix is to consolidate the two into one.

I believe this was fixed a while ago


mac m1 fyne-cross Android

I remember that I previously compiled Android on a Mac M1 using fyne-cross, but now it doesn't work anymore, and I've been trying for a long time without success.

now:

I also forgot how I configured it earlier.

This was fixed 2 versions ago - please make sure you have an up to date fyne-cross

Oh wow - it seems that android was a special case and the fix I referenced did not resolve the M1-android issue. My apologies for the mistake.
Fix inbound


⬆ Update watchify and lodash deps

A transitive dep of watchify 3, glob-parent, has a moderate security advisory, https://npmjs.com/advisories/1751

Watchify 4.x drops support for node <10, but this project already targets 10+

lodash version has a CVE as well, https://npmjs.com/advisories/1673

Which issue does this PR address?
Closes #229

Closing in favor of https://github.com/nikku/karma-browserify/pull/231.
Thanks for your contribution.


Created slider ui components.

I have added different sliders. Please check them out.

@radar101 try taking the color of slider and max value as user input and then use them in slider file.


enhance nrovalidate to compute the podfingerprint of a set of pods

the nrovalidate companion tool should be enhanced to compute the PFP value of a set of pods
details (like input format) TBD and to be discussed in this issue to finalize the design.

after further review, we decided to not pursue this


Modmail does not mark as read after being read

Toolbox is hit-and-miss about marking unread modmail messages as read after being viewed. Many times, after viewing all new modmail messages and navigating away from the page, the icon will remain red in both the userbox at the top (RES) and in the toolbox itself at the bottom. Upon returning to modmail, the same messages will still be marked [new]. Issue is fixable by disabling the extension in Chrome and going to modmail.
OS: Windows 8.1 64-bit
Browser: Chrome v40.0.2214.115 m
Toolbox v3.0.5

reddit is hit-and-miss about marking unread modmail messages as read after being viewed.

ftfy

the icon will remain red in both the userbox at the top (RES)

top bar isn't RES, it's reddit.
This is a reddit issue.

Modmail marks as read perfectly fine when the extension is disabled, only stays unread persistently when the extension is active. Is not a reddit issue.

If you can be more clear about the issue, I'm happy to re-open it.  But as phrased, it's not a TB issue.

I'm unsure of what needs clarifying, but I'll try: When the TB chrome extension is disabled, when I click on a modmail icon that shows unread messages, read the messages, and then leave the page, the modmail icon stays gray until I get new mail. With the extension activated, when I click on a red modmail icon, read the messages and leave the page, the icon either stays red or becomes gray only to return to red without having received new mail later. When I return to modmail with the extension installed, the exact messages that I have already read are still marked [NEW], even messages that I have typed myself. This is usually not fixed by leaving the page and returning additional times, although it does eventually return to gray. Deactivating the extension and returning to modmail reliably marks all messages as read. I have yet to pin down the cause but the issue is TB-side, not reddit-side. Let me know if it still doesn't make sense.


Error when adding a package - Error page seems to be broken too.

When submitting the package
https://github.com/jeremygaul/django-gallery
I get an error on submission, tried in chrome and safari.  Page seems to be partial and has a broken image.

Same here, attached below is .har file of the 500 error:
djangopackages.org.har.zip

I'm just starting again to work with the Django Software Foundation (DSF) to transfer the project to their ownership.
In the meantime, please do not add any more "Me too's" or "Still doesn't work" comments. I know this is the case, and all related tickets will be addressed and closed in due time.


Broken links in docs

Issue: 404 errors from links in several different files.
What I was trying to do:

Follow the links in the next steps in get-started.md
Follow the links (except selfdestruct()) in access-control.md
Follow the links in crowdsales.md
Follow the internal repo links in tokens.md
Follow the links in utilities.md

What happened instead:

404 error due to links missing file extensions
404 errors all due to the links pointing to /docs/api (same with 3, 4, and 5)

Fix:

Add .md to the links in the section
The files that are linked now appear to be located under the /contracts/ directory in the repo.

Thanks for reporting these @SriDraco! In case you didn't know, these files are published at https://docs.openzeppelin.org, where all of these links work correctly.
The ones that are missing file extensions can be fixed for browsing within GitHub. The ones that are pointing to /docs/api can't be fixed, we want to remove them but due to a limitation in solidity-docgen right now we can't.


fix: check if a key is defined before dereferencing it

Due to Perl's autovivification feature, if a key is not defined, dereferencing
it will automaticaly create an empty hash as value for that key. This will be
an issue when checking if the key is defined elsewhere.
This change remove this potential problem for 'DATABASE_FUNCGEN' and 'DATABASE
_VARIATION' keys in species_defs->databases.
Related to ENSEMBL-4611.

I'm slightly worried that you won't end up with massive autoviv happening but there will still be some. Might be better to change statements such as
if($self->hub->species_defs->databases->{'DATABASE_FUNCGEN'}){

To
if( exists $self->hub->species_defs->databases->{'DATABASE_FUNCGEN'}) {

That should stop any autoviv happening and ensures you're testing the existence of the key

@andrewyatz I think checking existence only will also let an existed key that has undef value pass through, e.g. when $self->hub->species_defs->databases->{'DATABASE_FUNCGEN'} = undef. By making sure that this key does have associated value will ignore  such cases and it is consistent with testing conditions found elsewhere.
BTW doing this (if($self->hub->species_defs->databases->{'DATABASE_FUNCGEN'})) will not invoke autovivification. Only dereferencing it will.

That's fair enough 👍


Module is temporary halted.

Development of MM Ruter has halted brain damage (hjerne slag. Tt the moment I dong know if I ever will be any developement of this module. Ive recovered a kittle so I have been able to write this update... :)

Get well!


Add pay with mastercard button

This PR adds the pay with mastercard button. ~[Image]~ [Image]

~The icon was wrapped in a span tag because the font-awesome icon doesn't look good at all and does not follow mastercard's branding guideline. Feel free to tell me what you think :)~
Issue: #1504

Done! @shahednasser


xen-dom-mgmt: Remove pages from physmap when unmapping

When unmapping a region, pages should be removed from the self physmap as well. This is necessary to avoid leaking page references and ensure that domains can be properly destroyed.

I tried it and do not see zombies anymore: Tested-by: Grygorii Strashko<EMAIL_ADDRESS>

have you tried this with CONFIG_XEN_REGIONS=n
@lorc builds and works okay for me


Update SLDS Metadata

Address #7 - this is resolved via metadata update

That's correct. Do you want me to bump the version with this change?

@billyma No lets create another PR for that. Thanks


nuxt

Hi there,
Is there any support for nuxt currently? has anyone managed to get this package running in their nuxt projects?
I am getting "e.ref is not a function", thanks!
The only difference I have from the example code is using nuxts  defineComponent function, as opposed to vues own.

Hi @fyllepo , thanks.
I find that  nuxtjs not release to support vue3 now. see https://github.com/nuxt/nuxt.js/issues/5708
This package is only support for vue3.
Could you provide the nuxtjs version and vue version you used?
Thanks 😃


STA can not get an IP (IDFGH-3810)

Environment
Development Kit: [none]
Kit version: [none]
Module or chip used: [ESP32-PICO-D4]
IDF version: v4.2
Build System: [???]
Compiler version: [???]
Operating System: [Windows]
(Windows only) environment type: [???].
Using an IDE?: [Yes (VSCode + ESP-IDF Extension)]
Power Supply: [external 3.3V]
Problem Description
ESP32 in STA mode can not get an IP.
Expected Behavior

check if ssid and pwd are blank;
1.1. starting STA mode if ssid and pwd are not blank;
1.2. starting AP mode if ssid and pwd are blank;
1.2.1. loading STA wifi config from NVS;
1.2.2. if loaded ssid and pwd are blank -> proceed AP mode
1.2.3. if loaded ssid and pwd are not blank -> switching to STA mode to proceed
if ssid and pwd are not correct when connecting - erasing them and save to NVS
go to p. 0

Actual Behavior
STA hangs when connected to WiFi router and cannot get IP when ssid and pwd are loaded from Wi-Fi NVS configuration. SSID and PWD are correct.
P.S. ESP32 panick'ed when esp_event_loop and mDNS service was not deinitialized / freed.
Steps to reproduce
Code to reproduce this issue
Code: https://gist.github.com/stdenits/38f4b6de4fee9035c99b37bd8c0223c5
Debug Logs
Correct behavior log
I (30) boot: ESP-IDF v4.2-dev-1905-g625bd5eb1 2nd stage bootloader
I (30) boot: compile time 19:30:13
I (30) boot: chip revision: 1
I (34) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (41) boot.esp32: SPI Speed      : 40MHz
I (46) boot.esp32: SPI Mode       : DIO
I (51) boot.esp32: SPI Flash Size : 4MB
I (55) boot: Enabling RNG early entropy source...
I (61) boot: Partition Table:
I (64) boot: ## Label            Usage          Type ST Offset   Length
I (71) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (79) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (86) boot:  2 factory          factory app      00 00 00010000 00100000
I (94) boot:  3 storage          Unknown data     01 82 00110000 000f0000
I (101) boot: End of partition table
I (106) boot_comm: chip revision: 1, min. application chip revision: 0
I (113) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x1d3d4 (119764) map
I (167) esp_image: segment 1: paddr=0x0002d3fc vaddr=0x3ffb0000 size=0x02c1c ( 11292) load
I (172) esp_image: segment 2: paddr=0x00030020 vaddr=0x400d0020 size=0x91910 (596240) map
0x400d0020: _stext at ??:?

I (401) esp_image: segment 3: paddr=0x000c1938 vaddr=0x3ffb2c1c size=0x00ee4 (  3812) load
I (403) esp_image: segment 4: paddr=0x000c2824 vaddr=0x40080000 size=0x00404 (  1028) load
0x40080000: _WindowOverflow4 at C:/Users/User/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

I (408) esp_image: segment 5: paddr=0x000c2c30 vaddr=0x40080404 size=0x16ad4 ( 92884) load
I (457) esp_image: segment 6: paddr=0x000d970c vaddr=0x400c0000 size=0x00064 (   100)
I (457) esp_image: segment 7: paddr=0x000d9778 vaddr=0x50000000 size=0x00064 (   100)
I (475) boot: Loaded app from partition at offset 0x10000
I (476) boot: Disabling RNG early entropy source...
I (477) cpu_start: Pro cpu up.
I (481) cpu_start: Application information:
I (485) cpu_start: Project name:     wifi_softAP
I (491) cpu_start: App version:      1
I (495) cpu_start: Compile time:     Aug 11 2020 20:28:51
I (501) cpu_start: ELF file SHA256:  c63aea6b22bc9c43...
I (507) cpu_start: ESP-IDF:          v4.2-dev-1905-g625bd5eb1-dirty
I (514) cpu_start: Starting app cpu, entry point is 0x400819f0
0x400819f0: call_start_cpu1 at C:/Users/User/esp-idf/components/esp32/cpu_start.c:286

I (0) cpu_start: App cpu up.
I (525) heap_init: Initializing. RAM available for dynamic allocation:
I (531) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (538) heap_init: At 3FFBA1A8 len 00025E58 (151 KiB): DRAM
I (544) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (550) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (557) heap_init: At 40096ED8 len 00009128 (36 KiB): IRAM
I (563) cpu_start: Pro cpu start user code
I (581) spi_flash: detected chip: gd
I (582) spi_flash: flash io: dio
I (582) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (589) ESP32_Server: app_main() runned on core 0

I (629) ESP32_SPI: Initializing SPI
I (629) gpio: GPIO[32]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (629) ESP32_SPIFFS: Initializing SPIFFS
I (729) ESP32_SPIFFS: Partition size: total: 896321, used: 518064
I (729) ESP32_Server: ESP_WIFI_MODE_AP
I (729) ESP32_mDNS: mdns hostname set to: [irsta.local]
I (749) wifi:wifi driver task: 3ffc51e8, prio:23, stack:6656, core=0
I (749) system_api: Base MAC address is not set
I (749) system_api: read default base MAC address from EFUSE
I (779) wifi:wifi firmware version: 0507408
I (779) wifi:wifi certification version: v7.0
I (779) wifi:config NVS flash: enabled
I (779) wifi:config nano formating: disabled
I (779) wifi:Init dynamic tx buffer num: 32
I (779) wifi:Init data frame dynamic rx buffer num: 32
I (789) wifi:Init management frame dynamic rx buffer num: 32
I (789) wifi:Init management short buffer num: 32
I (799) wifi:Init static rx buffer size: 1600
I (799) wifi:Init static rx buffer num: 10
I (809) wifi:Init dynamic rx buffer num: 32
I (809) ESP32_Server: WiFi TEST
I (809) ESP32_Server: PSW TEST
I (849) phy: phy_version: 4182, f1ba940, Jun  4 2020, 19:40:07, 0, 1
I (849) wifi:mode : sta (d8:a0:1d:4a:3c:a0)
I (1579) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:13
I (1579) wifi:state: init -> auth (b0)
I (1589) wifi:state: auth -> assoc (0)
I (1589) wifi:state: assoc -> run (10)
I (1609) wifi:connected with TEST, aid = 3, channel 6, BW20, bssid = 3c:19:7d:af:86:bd
I (1609) wifi:security type: 4, phy: bgn, rssi: -88
I (1619) wifi:pm start, type: 1

I (1669) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (6629) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>

I (6629) ESP32_Server: SYSTEM_EVENT_STA_GOT_IP
I (6629) ESP32_Server: Login Success
I (6639) ESP32_Server: Starting server on port: '80'
I (6649) ESP32_Server: Registering URI handlers
sended <80,2;>
I (6739) ESP32_SPI: Start SPI transactions

Incorrect behavior log
I (29) boot: ESP-IDF v4.2-dev-1905-g625bd5eb1 2nd stage bootloader
I (29) boot: compile time 19:30:13
I (30) boot: chip revision: 1
I (34) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (41) boot.esp32: SPI Speed      : 40MHz
I (46) boot.esp32: SPI Mode       : DIO
I (50) boot.esp32: SPI Flash Size : 4MB
I (55) boot: Enabling RNG early entropy source...
I (60) boot: Partition Table:
I (64) boot: ## Label            Usage          Type ST Offset   Length
I (71) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (86) boot:  2 factory          factory app      00 00 00010000 00100000
I (93) boot:  3 storage          Unknown data     01 82 00110000 000f0000
I (101) boot: End of partition table
I (105) boot_comm: chip revision: 1, min. application chip revision: 0
I (112) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x1d3d4 (119764) map
I (167) esp_image: segment 1: paddr=0x0002d3fc vaddr=0x3ffb0000 size=0x02c1c ( 11292) load
I (172) esp_image: segment 2: paddr=0x00030020 vaddr=0x400d0020 size=0x91918 (596248) map
0x400d0020: _stext at ??:?

I (400) esp_image: segment 3: paddr=0x000c1940 vaddr=0x3ffb2c1c size=0x00ee4 (  3812) load
I (402) esp_image: segment 4: paddr=0x000c282c vaddr=0x40080000 size=0x00404 (  1028) load
0x40080000: _WindowOverflow4 at C:/Users/User/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

I (408) esp_image: segment 5: paddr=0x000c2c38 vaddr=0x40080404 size=0x16ad4 ( 92884) load
I (456) esp_image: segment 6: paddr=0x000d9714 vaddr=0x400c0000 size=0x00064 (   100) load
I (457) esp_image: segment 7: paddr=0x000d9780 vaddr=0x50000000 size=0x00064 (   100) load
I (476) boot: Loaded app from partition at offset 0x10000
I (476) boot: Disabling RNG early entropy source...
I (477) cpu_start: Pro cpu up.
I (481) cpu_start: Application information:
I (486) cpu_start: Project name:     wifi_softAP
I (491) cpu_start: App version:      1
I (495) cpu_start: Compile time:     Aug 11 2020 20:28:51
I (501) cpu_start: ELF file SHA256:  385b136fee05901c...
I (507) cpu_start: ESP-IDF:          v4.2-dev-1905-g625bd5eb1-dirty
I (514) cpu_start: Starting app cpu, entry point is 0x400819f0
0x400819f0: call_start_cpu1 at C:/Users/User/esp-idf/components/esp32/cpu_start.c:286

I (0) cpu_start: App cpu up.
I (525) heap_init: Initializing. RAM available for dynamic allocation:
I (532) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (538) heap_init: At 3FFBA1A8 len 00025E58 (151 KiB): DRAM
I (544) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (550) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (557) heap_init: At 40096ED8 len 00009128 (36 KiB): IRAM
I (563) cpu_start: Pro cpu start user code
I (581) spi_flash: detected chip: gd
I (582) spi_flash: flash io: dio
I (582) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (590) ESP32_Server: app_main() runned on core 0

I (630) ESP32_SPI: Initializing SPI
I (630) gpio: GPIO[32]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (630) ESP32_SPIFFS: Initializing SPIFFS
I (730) ESP32_SPIFFS: Partition size: total: 896321, used: 518064
I (730) ESP32_Server: ESP_WIFI_MODE_AP
I (730) ESP32_mDNS: mdns hostname set to: [irsta.local]
I (750) wifi:wifi driver task: 3ffc51e8, prio:23, stack:6656, core=0
I (750) system_api: Base MAC address is not set
I (750) system_api: read default base MAC address from EFUSE
I (770) wifi:wifi firmware version: 0507408
I (780) wifi:wifi certification version: v7.0
I (780) wifi:config NVS flash: enabled
I (780) wifi:config nano formating: disabled
I (780) wifi:Init dynamic tx buffer num: 32
I (780) wifi:Init data frame dynamic rx buffer num: 32
I (790) wifi:Init management frame dynamic rx buffer num: 32
I (790) wifi:Init management short buffer num: 32
I (800) wifi:Init static rx buffer size: 1600
I (800) wifi:Init static rx buffer num: 10
I (810) wifi:Init dynamic rx buffer num: 32
wifi_config.sta.ssid: TEST
wifi_config.sta.password: TEST
I (820) wifi:Deinit lldesc rx mblock:10
I (830) ESP32_Server: Switched to ESP_WIFI_MODE_STA
I (830) ESP32_mDNS: mdns hostname set to: [irsta.local]
I (850) wifi:wifi driver task: 3ffc29c8, prio:23, stack:6656, core=0
I (870) wifi:wifi firmware version: 0507408
I (870) wifi:wifi certification version: v7.0
I (870) wifi:config NVS flash: enabled
I (870) wifi:config nano formating: disabled
I (870) wifi:Init dynamic tx buffer num: 32
I (870) wifi:Init data frame dynamic rx buffer num: 32
I (880) wifi:Init management frame dynamic rx buffer num: 32
I (890) wifi:Init management short buffer num: 32
I (890) wifi:Init static rx buffer size: 1600
I (890) wifi:Init static rx buffer num: 10
I (900) wifi:Init dynamic rx buffer num: 32
I (900) ESP32_Server: WiFi TEST
I (910) ESP32_Server: PSW TEST
I (1010) phy: phy_version: 4182, f1ba940, Jun  4 2020, 19:40:07, 0, 0
I (1010) wifi:mode : sta (d8:a0:1d:4a:3c:a0)
I (1140) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:13
I (1140) wifi:state: init -> auth (b0)
I (1150) wifi:state: auth -> assoc (0)
I (1160) wifi:state: assoc -> run (10)
I (1240) wifi:connected with TEST, aid = 3, channel 6, BW20, bssid = 3c:19:7d:af:86:bd
I (1240) wifi:security type: 4, phy: bgn, rssi: -89
I (1240) wifi:pm start, type: 1

I (1350) wifi:AP's beacon interval = 102400 us, DTIM period = 1

Other items if possible

Thanks for reporting and letting us know, we will look into.

The same thing on ESP IDF v4.3.
The code based on older version of ESP IDF. I'm interested if i screwed up with modifying the code for the current master branch (v4.*).

Hi @stdenits , the log rssi: -89 indicates that the AP is far away from ESP32 devices, suggest keep AP closer to ESP32.

@liuzfesp
Hello.
Check the log of the correct behavior: the signal strength there is also not very good and it works fine, as expected.

Hi @stdenits, it's a bug about esp_wifi_set_storage(WIFI_STORAGE_RAM), we already have fix for it, but it need sometime for it to be merged into IDF.

it's a bug about esp_wifi_set_storage(WIFI_STORAGE_RAM)
Could you please explain how my situation and this bug are related?

Any way to test the fix?

Hi @stdenits, it's a bug about esp_wifi_set_storage(WIFI_STORAGE_RAM), we already have fix for it, but it need sometime for it to be merged into IDF.

I'm wondering if you have some policy to speed up merging critical fixes into IDF.
Especially for panic issues or this issue which causes connecting AP failure.

Hi @stdenits, it's a bug about esp_wifi_set_storage(WIFI_STORAGE_RAM), we already have fix for it, but it need sometime for it to be merged into IDF.

Can you provide the link to the commit? I don't find such fix in esp32-wifi-lib.
Thanks.

HI @AxelLin, we haven't merge the fix yet, it's still under internal reviewing and we still need some time before it can be merged.

Hi @liuzfesp
I still don't find the fix (from the commit log) in esp32-wifi-lib after waiting for 3 weeks.
Now I'm worry that the fix won't be available in recent esp-idf update.
Can you tell which branches are impacted by this issue?

Hi @AxelLin, since this is a big change for us, we still need some time for it.
The root cause of this issue is that the configuration of AP is NOT store into NVS correctly. As a workaround, you can fix this issue by storing the AP configuration into NVS twice.
To be detailed,

Call esp_wifi_get_config(WIFI_IF_AP, &ap_config) to get WiFi configuration
Fill ap_config with new ssid/password and other info
Increase ap_config.ap.beacon_interval by one: ap_config.ap.beacon_internal +=1
Call esp_wifi_set_config(WIFI_IF_AP, &ap_config)
Recovery original beacon_interval: ap_config.ap.beacon_internal -= 1
Call esp_wifi_set_config(WIFI_IF_AP, &ap_config) again

Hi @liuzfesp
Thanks for the update and I didn't mean to push you.
Look back the discussion on 14 Aug, you said "it's a bug about esp_wifi_set_storage(WIFI_STORAGE_RAM), we already have fix for it".
So I'm surprised that you said "this is a big change" now.
And I don't understand the "bug about esp_wifi_set_storage(WIFI_STORAGE_RAM)" and the relationship of your explain detail.
(Why storing AP configuration twice can work?)
PS.
I understand it's closed source library, I wouldn't ask the implementation detail.
But I would like to know the user visible impact, especially which branches are impacted by this bug.
Is this a new bug (regression)? (If yes, which commit causes the problem?)

Hi @AxelLin
This issue exists in all active IDF release for very long time, all branches are impacted by this bug.
Yes, we already have fix for it for more than one month. When I said it's a big change, here it doesn't mean the fix is related to a lot of code change, it just means we have to merge the fix very carefully because it's about WiFi NVS change. Generally speaking, we should always take WiFi NVS related change carefully in case it may introduce new bug about OTA (OTA bug is much more serious bug for us).  For this kind of code change, we internally need several round of tests before we can finally merge it.
The root cause is because esp_wifi_set_config() returns directly if it finds that the passing configurations are same as the value stored in RAM.  In above workaround, the first esp_wifi_set_config call just modifies a parameter beacon_interval and make sure it's different than the value stored in RAM, the 2nd call change the value back. Beside esp_wifi_set_config(), other WiFi APIs related to NVS storing also have similar issue, we will fix all of them in the fix.
Some background information about the intention of API esp_wifi_set_storage(WIFI_STORAGE_RAM):

In ESP32, originally this API is only used for debug reason even though is not prefixed with esp_wifi_internal_.
We internally have a lot of stress testing, some test involving frequently WiFi NVS writing/reading, e.g. in WiFi mode switching testing, we may switch the mode for more than 1000000 times in one stress test. Each time we do a mode switching, we have to read/write the WiFi NVS, it will impact the lifetime of WiFi NVS (which is flash) for so frequency NVS read/write. So we introduce API esp_wifi_set_storage(WIFI_STORAGE_RAM). During stress test involves a huge number of NVS read/write, we just store the configuration into RAM to avoid impacting the NVS.

Now our customers have innovative way to use esp_wifi_set_storage(WIFI_STORAGE_RAM), we need to fix the bug anyway.

@liuzfesp
Sorry for not answering for so long. I was sick.
How is the AP configuration related to the fact that ESP32 in the STAtion mode cannot connect to the access point? Although it seems to receive the correct username and password.
Also i'm using ESP_ERROR_CHECK(esp_wifi_set_storage(WIFI_STORAGE_FLASH)), not RAM only.

Could anybody give me some tips to find  out the reason?
Tried to connect to the smartphone AP's, new log attached below.
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6908
load:0x40078000,len:14304
load:0x40080400,len:3672
0x40080400: _init at ??:?

entry 0x40080678
I (29) boot: ESP-IDF v4.3-dev-1561-g357a27760 2nd stage bootloader
I (29) boot: compile time 13:45:36
I (30) boot: chip revision: 1
I (34) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (41) boot.esp32: SPI Speed      : 40MHz
I (46) boot.esp32: SPI Mode       : DIO
I (50) boot.esp32: SPI Flash Size : 4MB
I (55) boot: Enabling RNG early entropy source...
I (60) boot: Partition Table:
I (64) boot: ## Label            Usage          Type ST Offset   Length
I (71) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (86) boot:  2 factory          factory app      00 00 00010000 00100000
I (93) boot:  3 storage          Unknown data     01 82 00110000 00100000
I (101) boot: End of partition table
I (105) boot_comm: chip revision: 1, min. application chip revision: 0
I (112) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x1c0c4 (114884) map
I (165) esp_image: segment 1: paddr=0x0002c0ec vaddr=0x3ffb0000 size=0x03f2c ( 16172) load
I (172) esp_image: segment 2: paddr=0x00030020 vaddr=0x400d0020 size=0x929bc (600508) map
0x400d0020: _stext at ??:?

I (401) esp_image: segment 3: paddr=0x000c29e4 vaddr=0x3ffb3f2c size=0x00188 (   392) load
I (401) esp_image: segment 4: paddr=0x000c2b74 vaddr=0x40080000 size=0x00404 (  1028) load
0x40080000: _WindowOverflow4 at C:/Users/User/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

I (408) esp_image: segment 5: paddr=0x000c2f80 vaddr=0x40080404 size=0x1567c ( 87676) load
I (454) esp_image: segment 6: paddr=0x000d8604 vaddr=0x400c0000 size=0x00064 (   100) load
I (455) esp_image: segment 7: paddr=0x000d8670 vaddr=0x50000000 size=0x00064 (   100) load
I (473) boot: Loaded app from partition at offset 0x10000
I (473) boot: Disabling RNG early entropy source...
I (486) cpu_start: Pro cpu up.
I (486) cpu_start: Starting app cpu, entry point is 0x40081294
0x40081294: call_start_cpu1 at C:/Users/User/esp-idf/components/esp_system/port/cpu_start.c:124

I (0) cpu_start: App cpu up.
I (500) cpu_start: Pro cpu start user code
I (501) cpu_start: cpu freq: 160000000
I (501) cpu_start: Application information:
I (505) cpu_start: Project name:     wifi_softAP
I (510) cpu_start: App version:      1
I (515) cpu_start: Compile time:     Oct 27 2020 16:57:48
I (521) cpu_start: ELF file SHA256:  116d077734ed02de...
I (527) cpu_start: ESP-IDF:          v4.3-dev-1561-g357a27760
I (533) heap_init: Initializing. RAM available for dynamic allocation:
I (541) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (547) heap_init: At 3FFB8A28 len 000275D8 (157 KiB): DRAM
I (553) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (559) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (566) heap_init: At 40095A80 len 0000A580 (41 KiB): IRAM
I (573) spi_flash: detected chip: gd
I (576) spi_flash: flash io: dio
I (581) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (591) ESP32_Server: app_main() runned on core 0

I (631) ESP32_SPI: Initializing SPI
I (631) gpio: GPIO[32]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (641) ESP32_SPIFFS: Initializing SPIFFS
I (741) ESP32_SPIFFS: Partition size: total: 956561, used: 926190
I (741) ESP32_Server: ESP_WIFI_MODE_AP
I (741) ESP32_mDNS: mdns hostname set to: [irsta.local]
I (761) wifi:wifi driver task: 3ffc5720, prio:23, stack:6656, core=1
I (761) system_api: Base MAC address is not set
I (761) system_api: read default base MAC address from EFUSE
I (791) wifi:wifi firmware version: a94a000
I (791) wifi:wifi certification version: v7.0
I (791) wifi:config NVS flash: enabled
I (791) wifi:config nano formating: disabled
I (791) wifi:Init data frame dynamic rx buffer num: 32
I (801) wifi:Init management frame dynamic rx buffer num: 32
I (801) wifi:Init management short buffer num: 32
I (811) wifi:Init dynamic tx buffer num: 32
I (811) wifi:Init static rx buffer size: 1600
I (811) wifi:Init static rx buffer num: 10
I (821) wifi:Init dynamic rx buffer num: 32
I (821) wifi_init: rx ba win: 6
I (831) wifi_init: tcpip mbox: 32
I (831) wifi_init: udp mbox: 6
I (831) wifi_init: tcp mbox: 6
I (841) wifi_init: tcp tx win: 5744
I (841) wifi_init: tcp rx win: 5744
I (851) wifi_init: tcp mss: 1440
I (851) wifi_init: WiFi IRAM OP enabled
I (851) wifi_init: WiFi RX IRAM OP enabled
I (861) wifi:Set ps type: 0

wifi_config.sta.ssid: arp_pkg_calc
wifi_config.sta.password: 123456789
I (871) wifi:Deinit lldesc rx mblock:10
I (1881) ESP32_Server: Switched to ESP_WIFI_MODE_STA
I (1881) ESP32_mDNS: mdns hostname set to: [irsta.local]
I (1901) wifi:wifi driver task: 3ffc2e9c, prio:23, stack:6656, core=1
I (1911) wifi:wifi firmware version: a94a000
I (1911) wifi:wifi certification version: v7.0
I (1921) wifi:config NVS flash: enabled
I (1921) wifi:config nano formating: disabled
I (1921) wifi:Init data frame dynamic rx buffer num: 32
I (1921) wifi:Init management frame dynamic rx buffer num: 32
I (1931) wifi:Init management short buffer num: 32
I (1931) wifi:Init dynamic tx buffer num: 32
I (1941) wifi:Init static rx buffer size: 1600
I (1941) wifi:Init static rx buffer num: 10
I (1951) wifi:Init dynamic rx buffer num: 32
I (1951) wifi_init: rx ba win: 6
I (1951) wifi_init: tcpip mbox: 32
I (1961) wifi_init: udp mbox: 6
I (1961) wifi_init: tcp mbox: 6
I (1971) wifi_init: tcp tx win: 5744
I (1971) wifi_init: tcp rx win: 5744
I (1971) wifi_init: tcp mss: 1440
I (1981) wifi_init: WiFi IRAM OP enabled
I (1981) wifi_init: WiFi RX IRAM OP enabled
I (1991) wifi:Set ps type: 0

I (1991) ESP32_Server: WiFi arp_pkg_calc
I (2001) ESP32_Server: PSW 123456789
I (2111) phy: phy_version: 4500, 0cd6843, Sep 17 2020, 15:37:07, 0, 0
I (2111) wifi:mode : sta (d8:a0:1d:4a:3c:a0)
I (2111) wifi:enable tsf
I (3441) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:13
I (5471) wifi:state: init -> auth (b0)
I (5541) wifi:state: auth -> assoc (0)
I (5551) wifi:state: assoc -> run (10)
I (5581) wifi:connected with arp_pkg_calc, aid = 7, channel 11, BW20, bssid = 20:da:22:7b:a4:61
I (5581) wifi:security: WPA2-PSK, phy: bgn, rssi: -41
I (5581) wifi:pm start, type: 0

I (5621) wifi:AP's beacon interval = 102400 us, DTIM period = 2

Hi @stdenits,
Can you provide a wireless packet capture corresponding to the unconnected wifi log?
Or provide the smallest reproduction code and phone model for our local reproduction?
The recommended Macbook's built-in packet capture tool does not require a packet capture card. It can be used to capture 802.11a/b/g/n/ac packets:
https://osxdaily.com/2015/04/23/sniff-packet-capture-packet-trace-mac-os-x-wireless-diagnostics/
Or you can use the tutorial on the official Espressif website to capture packets using Wireshark
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/wireshark-user-guide.html

@HarveyRong-Esp,
Hello.
Thank you for your reply. But i just decided to decline this function and use static STA configuration.
Maybe be later it will work as intended.

Hi @AxelLin
This issue exists in all active IDF release for very long time, all branches are impacted by this bug.

I just notice this issue was closed, which commit fixed this issue?


'Find in Project' returns no results

'Find in Project' returns no results when opened for the first time. Once, opened results appear.
To show results, toggle 'Use RegExp' or any of the other toggles.

Thanks for the report. Yeah, I've seen this too -- it's already mentioned in https://github.com/atom/find-and-replace/issues/373#issuecomment-130194295. If you'd like, please reopen this on the package's issue tracker: https://github.com/atom/find-and-replace/issues/373.


[test] Fix validation-test/IDE/slow/rdar45511835.swift

Update the test to reflect the changes made in #38446

@swift-ci please test

Thank you!


QUAL-16-C: Update to allow CS locations to report MATS Averaging Group qualification codes

RT 74192: ORIS 2727, CS001 received a QUAL-16-C error for adding an HGAVG qualification record at the common stack level.
Per 3/28/2024 weekly support meeting with EPA, update this check to allow CS locations to report MATS Averaging Group qualification codes.
Ticket #6192 will handle the need for additional qualification type codes for other MATS parameters included in averaging groups. This ticket is dependent on these changes.
Short-term: Errors will be suppressed in ECMPS 1.0 on a case-by-case basis. This change will only be included with the rollout of ECMPS 2.0.

Blocked by #6192. If there are new codes, this ticket will need to be updated.


Update to SDK version 2.2.3

There's been an enormous number of improvements and bug fixes between
our current release and 2.2.3

:+1:


Pbx revision

Revision of pourbaix functionality
Adds some things to pourbaix.
TODO (if any)

Stress test on ternaries
updates to pymatpro

I'm able to get a result for ternaries, but unable to verify.  Will look into that tomorrow.  Will test with the pymatpro test system [Fe-Ni-Cr].


Cached nonzero values per entry

Turns out we can speed up the MI-based ranking implementations by caching nonzero values so they're not re-computed. This further speeds up the core algorithm by around 20%.

good point, tried, it seems it does actually
On Wed, 27 Sep 2023, 16:48 Miha Jenko, @.***> wrote:

@.**** commented on this pull request.
In outrank/algorithms/feature_ranking/ranking_mi_numba.py
https://github.com/outbrain/outrank/pull/37#discussion_r1338733394:

index = 0
for c in class_values:

To make the code nicer, use enumerate(class_values). There are two
instances of this.
Not sure if it impacts performance.
—
Reply to this email directly, view it on GitHub
https://github.com/outbrain/outrank/pull/37#pullrequestreview-1646841322,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMSERGGDMRV6IALS5D3NF3X4Q4C7ANCNFSM6AAAAAA5JKGSAI
.
You are receiving this because you authored the thread.Message ID:
@.***>


⚠ Bofrost.be has degraded performance

In 5a1027c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1561 ms

Resolved: Bofrost.be performance has improved in c47e643.


vdk-plugins: add connection hook activity diagram

I was playing around (learning how to write PlantUML activity diagrams) and wrote one about how PEP 249 operations and conneciton hooks work.
In my opinion, a picture is worth a thousand words and the current documentation for connection hooks is a bit too text-heavy without showing enough.
I think this would improve understandability of how connection hooks work

Hint: to review easier markdowns click