Use clean_title() on title in templates

Articles with
 to manually format titles have
 show up in the browser tabs, as that pulls from the page title. See, e.g., on the development server: http://localhost:8000/five-questions/five-more-questions/
Runing  through clean_title() should fix it.

Commit: a0e1eae943d0eeaea40913d0a6c5b3e138fc7ccf.
Titles within  call article.clean_title now.


Tado device tracker fails if device not at home on Home Assistant startup

Home Assistant release with the issue:
0.90.2
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
FreeNAS
Component/platform:
Tado / Device Tracker
Description of problem:
I have configured Tado as a device tracker as per the documentation. It works well (in fact, it's a very reliable device tracker out of the box) if both my phone and my wife's phone are home when Home Assistant is started.
However, if one or both phones is not home, they are not loaded. I get "entity not available: " in the UI and they are not in the list of entities in the debug tools.
They also never appear in known_devices.yaml (unlike devices tracked by the ios and network device trackers, which seem to populate that file automatically).
The log contains this error:
2019-04-07 00:49:56 ERROR (MainThread) [homeassistant.components.tado.device_tracker] Cannot load Tado data

Looking at the source at https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/tado/device_tracker.py this appears to be a catch-all error handler (which annoyingly swallows the underlying error).
There is a warning log higher up:
                if response.status != 200:
                    _LOGGER.warning(
                        "Error %d on %s.", response.status, self.tadoapiurl)
                    return False

I don't see this in my log, though that may be a logging level issue.

Debugging a bit more, as far as I can tell the error comes in calling the URL templated from:
            self.tadoapiurl = 'https://my.tado.com/api/v2' \
                              '/homes/{home_id}/mobileDevices'
            self.tadoapiurl += '?username={username}&password={password}'

If I call that URL manually, I get a sensible looking response.
I wonder if the problem is a timeout?

Digging into the code I think that error is a red herring, and the behaviour is deliberate:
        # Find devices that have geofencing enabled, and are currently at home.
        for mobile_device in tado_json:
            if mobile_device.get('location'):
                if mobile_device['location']['atHome']:
                    device_id = mobile_device['id']
                    device_name = mobile_device['name']
                    last_results.append(Device(device_id, device_name))

Surely that can’t be right though? It seems very strange to me that the tracker only works if the device is at home each time home assistant is started.

Trying to trace this, I realise that this is how all the device trackers work: the last_results list (or equivalent) only contains "seen" devices. I still don't fully understand the operating principles behind the device tracker, it seems.
However, I believe now the problem is one of:

The Tado device scanner should "see" the device on first startup, even if away. The API returns it. I can't tell how/where in the device scanner API this would happen.

The device is never written to known_devices.yaml. If it were, then it'd work after the device had been seen at home at least once.

I'm looking in components.device_scanner for how that file is updated. I've noticed that the Tado scanner implements async_scan_devices() when most other scanners implement scan_devices(). I'm not sure if this is the problem though.

Did you ever find an answer to this? I've just set up tado as my main device tracker, and yes, if HA is rebooted while either me or my girlfriend are away, then the entity doesn't exist.

I am not 100% sure this was the fix, but I manually added an entry to known_devices.yaml and I think that does it. You need to figure out the device if (something like myname_iphone I think - it should show up in the UI when available automagically) and I don’t think you can change it.
Martin Aspeli

From: theCheek<EMAIL_ADDRESS>Sent: Tuesday, May 28, 2019 6:03 am
To: home-assistant/home-assistant
Cc: Martin Aspeli; Author
Subject: Re: [home-assistant/home-assistant] Tado device tracker fails if device not at home on Home Assistant startup (#22811)
Did you ever find an answer to this? I've just set up tado as my main device tracker, and yes, if HA is rebooted while either me or my girlfriend are away, then the entity doesn't exist.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/22811?email_source=notifications&email_token=AABHJCWMDX5MJDUJ2QQLEF3PXS4JRA5CNFSM4HEB5ZF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWK7CGI#issuecomment-496365849, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AABHJCRQBZDQEDN4UHADLPTPXS4JRANCNFSM4HEB5ZFQ.

Thanks for getting back. known_devices.yaml already contains an entry for my phone. And now for some reason a restart while I am out the house it seems to stick. Didn't change anything. Weird!


[CS2103T-T09-1] StudyTracker

StudyTracker helps NUS Computing students to track great study locations that they have visited. It is optimised for CLI users so that the tracking of study spots can be done easily with commands.

Codecov Report

Merging #42 (1e08e96) into master (ba53b8c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #42   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 ba53b8c...1e08e96. Read the comment docs.


[BUG] MQTT not working with utf8 encoded payload (ex.: from fhem)

Describe the bug
mqtt publish from fhem is not working with the following command:
set myBroker publish /smarthome/sz/tv/cmd {"command":"volume_down"}
I have debugged it, and it seems the payload is utf8 encoded!
So after changing line 338 from:
                message = json.loads(msg.payload)
to:
                message = json.loads(msg.payload.decode('utf-8'))
fixed the issue for me!
I think that change makes no problem with no utf8 encoded strings, but that has to be tried.
Sadly i dont have any other mqtt device to test.
Can you please test this on your side and add this fix?
To Reproduce
see above
Expected behavior
fhem mqtt publish should work with pylips

Have created an PR see #59

Fixed by #59


Calling 'brew --prefix' is slow in the completions module - let's speed it up!

Description

While profiling my prezto config, I noticed that the completions module was taking a bit longer than I felt it should (fractions of seconds, not whole seconds, but still it's slower than I wanted). After profiling, I determined that a subshell call to $(brew --prefix) was the culprit. I'm not the first to notice performance related to brew --prefix: https://github.com/Homebrew/brew/issues/3327
Expected behavior
Since the completions module is one of the core Prezto modules and is enabled by default, I'd like to see it be as speedy as possible.
Actual behavior
It's not speedy.
Steps to Reproduce

On a Mac, install homebrew
Use brew to install curl (brew install curl)
Prezto now slows down because now the completions for curl are in a location managed by homebrew

Versions

Prezto commit: latest (7884fb2271d131bb492fafc4eba1c537a821092b)
ZSH version: zsh 5.8 (x86_64-apple-darwin20.1.0)
OS information: MacOS 12.2

Potential solution
Current code:
# Add completion for keg-only brewed curl when available.
if (( $+commands[brew] )) \
      && [[ -d "${curl_prefix::="$(brew --prefix 2> /dev/null)"/opt/curl}" ]]; then
  fpath=($curl_prefix/share/zsh/site-functions $fpath)
fi
unset curl_prefix

Proposed change (add a cache file):
# Add completion for keg-only brewed curl when available.
if (( $+commands[brew] )); then
  # 'brew --prefix' is slow; cache its output
  cache_file="${XDG_CACHE_HOME:-$HOME/.cache}/prezto/brew-cache.zsh"
  if [[ "${ZDOTDIR:-$HOME}/.zpreztorc" -nt "$cache_file" || ! -s "$cache_file" ]]; then
    mkdir -p "$cache_file:h"
    echo "brew_prefix=$(brew --prefix 2> /dev/null)" >! "$cache_file"
  fi
  source "$cache_file"
  if [[ -d "${curl_site_functions::=$brew_prefix/opt/curl/share/zsh/site-functions}" ]]; then
    fpath=($curl_site_functions $fpath)
  fi
  unset cache_file brew_prefix curl_site_functions
fi

I'm open to discuss other solutions or implementations, but this implementation is similar to what the Perl module does so I modeled off that. I'm currently using it as a .patch file in my personal $ZDOTDIR and this sped up loads by more than 1/10th of a second.

One alternative implementation that doesn't use a cache file would be to check the common homebrew dirs first. This has the disadvantage that there's still a execution path to running brew --prefix during every Zsh init which is what a cache file avoids.
if (( $+commands[brew] )) && {
       [[ -d "${curl_prefix::=/opt/homebrew/opt/curl}" ]] ||
       [[ -d "${curl_prefix::=/usr/local/opt/curl}" ]] ||
       [[ -d "${curl_prefix::="$(brew --prefix 2> /dev/null)"/opt/curl}" ]]
    }
then
  fpath=($curl_prefix/share/zsh/site-functions $fpath)
fi

It's also worth noting that the node module also calls brew --prefix, but since it's not a default module I didn't change it. I'd be open to adding whatever we do in the completions module to the node one if that's helpful.

Bumping this, as I agree it'd be nice to speed up the load time. But I'd like to see it done in a way that is consistent across all our modules, rather than re-patching this in completions-curl, perl, and other places that are affected.
I haven't put a lot of thought into this, and it may need to wait til #1986 is resolved before getting more attention, but it is worth fixing.


Avoid double-quoting of identifiers

ok from me, i will merge this pr and fix black formatting manually. thank you for the contribution!


Status of submission when timeout occurs

If a submission fails because of a timeout in the process run, its status on the webpage doesn't change until the status is clicked. This is because the webpage doesn't poll for submission status, but rather displays it almost immediately. At this point in time, it's not in the contest['attempts'] data structure, and so it get_attempt_status reports on it incorrectly.
One fix would be to poll for a status (as is done for score), but that is extra hits on the server; a better solution would be an AJAX-like one, but that is clearly a significant change.
It might also be worth adding a "Your program used too many resources" case to get_attempt_status, but this requires considering the error code returned by ulimit, which might not be trustworthy; An easy fix would be to say "The program raised an error or used too many resources" in get_attempt_status within judge instead.

My pull request should now handle this case also.


Buying Dracula Pro colorschme without the goodies at a reduced price

Why's there not an option to get the just the Pro colorschemes at a reduced price?
I understand that some people may find the book or the font research useful, but others may just want to try a nice dark colorscheme and don't have 80-100$ to spend.
Not really a software issue, but I wanted to make this comment in a public forum.
Please consider offering a basic package.
Thank you.

Thank you so much for your response @luxonauta! :sparkles:
:x: During these almost two years (one more month and we could be celebrating the second anniversary of this thread, come on) I've had time to pausedly consider the issue at and and have arrived at the conclusion that the price you put for

18 Themes
6 Variants
4 Hand-picked Fonts
1 Productivity E-book
1 Bonus Screencast
Design Files
Wallpapers
Constant updates
Support included
Discord Community
License for 3 computers

is completely absurd.
It strikes me as odd that you're charging people for 18 themes when you've designed one (Dracula).  That would be awkward because there are many more than 18 supported systems in your home page. What I sure do know is that you have not created four fonts! I got Fira Code with ligatures and patched with Nerd Fonts for free! Why should I pay for a font I can pacman in a blink of an eye?
Also, why would anyone in the face of earth to buy a self help book for every three computers they want to use this theme in? Your business model sounds a lot like that of a coercive group, something I've learnt about since december 15th 2020. Anyway. Have fun with your Newtonian colorscheme. I'll keep doing my best without the invaluable learnings from senior professionals. Cheers!


:art: Use a single framework image

With changes to the packages we now generate the proper service files on the fly so we dont need to have those package separated.
We now have 2 framework images, a generic one used for ALL flavors and a fips one, only provided for external consumers as we dont publish any fips enabled artifacts.
We also bring both the systemd and openrc package together as they dont affect each other anymore so we can have a single framework.
This patch also removes the service enablement as its not needed anymore, it done via config files
Reworks the framework jobs to just build and publish the 2 different framework image (generic and fips)

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1896

Do we need to update the docs here https://kairos.io/docs/reference/build-from-scratch/ ?


DATA-1524 - Second round of Data API cleanups

Part 2 of several API cleanup PRs.
Corresponding app PR: https://github.com/viamrobotics/app/pull/1951
Corresponding rdk PR: https://github.com/viamrobotics/rdk/pull/2591

Change Filter org_ids field to organization_ids and CaptureMetadata org_id field to organization_id for consistency with the rest of the Data and Fleet APIs. These are updating in app and RDK. Since these are included in proto APIs that are being used directly, will be notifying users directly about these breaking changes when this PR gets merged.
Update Add/RemoveTags APIs to be ByIDs instead of ByFileIDs for consistency with the rest of the ByID APIs. These are only used in app and updated in the corresponding PR.
Update TabularData.metadata_index and count values to uint32 and uint64 for consistency with the rest of the Data APIs. This is a forwards- and backwards-compatible change.
Change optional fields in GetPackageRequest and ListPackagesRequest to not be optional for consistency with the rest of the Data APIs and improved usability in Go. These are only used in app and RDK and updated in the corresponding PRs.

Order of merges:

Merge this PR and alert customers, mostly about the first bulletpoint
Bump API in RDK and merge RDK
Bump API and RDK in app and merge app

@stuqdog for FYI


Better readout allocation / time handling

(from brilee)
Currently, our self-play and tournament mode both allocate a fixed number of seconds and/or reads.
Both modes suffer from the same problem, which is that they spend their readouts inefficiently. If a response is obvious and has 800 reads compared to its siblings which have 10 reads each, then, there's no point to doing another 600 reads to reach our set point of 1600 reads per move. On the other hand, if the current leading candidate has 800 reads but the second place candidate discovered a new response and is rapidly catching up, we don't give the new candidate enough time to overtake the first place candidate. Ideally, we should truncate search at a point when all moves look sort of equally uninteresting to invest more time into (i.e. they have very similar action score.)
I don't care so much about tournament mode, but self-play could potentially achieve stronger play and using fewer reads, which should speed up the RL feedback loop. That our tournament mode would get stronger is just a nice bonus.

we know a lot more about this and this whole writeup is nonsense.


Added the 'spo term add' command solving #605

Added the 'spo term add' command solving #605

Merged manually


Creating a new View with an invalid name is not handled

Create a new view called 22222
See error

Failed to create '222222.cs'
One or more errors occurred. (Could not compile D:\Repos\TerminalGuiDesigner
\src\bin\Debug\net8.0\222222.Designer.cs:
(14,27): error CS1001: Identifier expected
(14,28): error CS1513: } expected
(16,17): error CS8124: Tuple must contain at least two elements.
(16,19): error CS1022: Type or namespace definition, or end-of-file expected

(19,5): error CS1022: Type or namespace definition, or end-of-file expected
(20,1): error CS1022: Type or namespace definition, or end-of-file expected
(18,27): error CS1001: Identifier expected
(18,50): error CS1513: } expected
[...]

Fixed in b827967


Customizing The Top Bar

This is probably more of a feature request, but is it possible to add a way to customize the top bar that you can pull up to reveal the UIViewController? Maybe have a way to supply a UIView to the component when it is initialized.

Nice feature 👍
I added the feature 😄


1027 fix shortcuts

Closes #1027

Is d770f51 meant to address #1024?

Answer to self: No, issue is still relevant and open with many potential issues (cf. updated issue).

@nikku Ready for review. I've created two seperate issues that I deliberately didn't tackle this time:

Integrate CommandStack#undo and CommandStack#redo when working with the properties panel (https://github.com/camunda/camunda-modeler/issues/1059)
Decide wether to re-implement custom copy/cut/paste behavior in decision table depending on selection range (https://github.com/camunda/camunda-modeler/issues/1060)


document.all is not virtualizable

Spec in question:
https://tc39.es/ecma262/#sec-IsHTMLDDA-internal-slot
A lot more details about this issue here:

https://github.com/caridy/secure-javascript-environment/issues/76
https://github.com/caridy/secure-javascript-environment/pull/79

Yes @Jack-Works we need to explicitly state the limits on the virtualizability we intend to support. We should explicitly state that we will not support emulating document.all. Thanks!

Instead I suggest to remove the magic behavior on document.all. Let it be truthy can solve this problem.

You mean in the main spec?

Yes, I'm mean by delete it in the main spec.
Falsy value of document.all is used to prevent feature detecting on the document.all, but there are better ways to do it. Like the browser can only make it falsy when using the literal to infer to it like what we do on the eval.
e.g.:
ˋˋjs
if (document.all) { // this direct access evaluate to false
}
var x = document.all
if (x) { // this indirect access evaluate to true
}
ˋˋˋ
Make the indirect access to document.all evaluate to truthy, most of the security issues in sandboxies can be resolve (because they never direct access document.all).

It would almost certainly break the web to change that behavior at this point; otherwise we wouldn’t have added the IsHTMLDDA slot to the spec.

Maybe we should try to make it falsy meanwhile less harmful to code that doesn't using document.all

I'm not sure what you mean; the weird part is that it's a falsy object. Making it truthy would break websites; making it not an object would break websites. What change are you suggesting?

I'm suggesting that it still be a falsy object but only when the website is really using it.

IMO, there are 3 things to look at:

how to virtualize this bizarre case when typeof x returns undefined if x uses [[IsHTMLDDA]] internal slot.
how to virtualize the bizarre case when x is falsy even though it is an object if x uses  [[IsHTMLDDA]] internal slot.
Can [[IsHTMLDDA]] case be reformed?

For us, at salesforce, we are virtualizing this by setting document.all to undefined inside the sandbox, that helps with 1, and part of 2, it seems to work for most libraries out there, and will only fail if a piece of code actually attempts to use the HTMLAllCollection object in any meaningful way.

Let the typeof check the isHTMLDDL slot recursively through the Proxy object that can resolve the visualizability.
However, what I really mean is the falsy evaluation is harmful to web security. It's better to disable this behavior on newer websites. (for example in module context or use a "legacy site list")

Let the typeof check the isHTMLDDL slot recursively through the Proxy object that can resolve the visualizability.

I @Jack-Works I do not want to add any complexity to the proxy mechanism to deal with this ugly special case.

However, what I really mean is the falsy evaluation is harmful to web security. It's better to disable this behavior on newer websites. (for example in module context or use a "legacy site list")

I agree it is harmful, and I agree that we should find a way to disable it, or change it to some behavior that can be expressed in JS. I am not familiar with how it is currently used and what the compat issues are in trying to change its behavior. I do encourage you and all of us to continue searching for a way out of the current mess.

if (document.all) {
  // code that uses `document.all`, for ancient browsers
} else if (document.getElementById) {
  // code that uses `document.getElementById`, for “modern” browsers
}

// Internet Explorer
if (document.all) {
    useActiveX()
}
// Netscape Navigator
else {
    useOldButStillWorkingCode()
}

It's the common pattern that why we need document.all falsy.
If we can change the spec like:

If the document.all literal (important) is used to do the ToBoolean operation e.g. if (document.all), Boolean(document.all), or var isIE = !!document.all, it must return a falsy value

If the document.all is not used by literal (or used in an ESModule context?), it must be a normal object (truthy). e.g. const x = document.all; some_lib(!!x)

Then the old code will still be working, and newer code won't be hacked by the document.all (e.g. https://github.com/caridy/secure-javascript-environment/issues/76) because those code doesn't use the document.all literal.
This way is somewhat like eval behavior. I think it's acceptable to have one more literal detect to prevent a more hacky solution.
+function x() {
    let y = 1
    eval('y = 2')
    console.log(y) // logs 2
}()

+function x() {
    let y = 1
    let indirectEval = eval
    indirectEval('y = 2')
    console.log(y) // logs 1
}()

Let the typeof check the isHTMLDDL slot recursively through the Proxy object that can resolve the visualizability.

@Jack-Works unfortunately that does not work in a membrane implementation because the target of the proxy is not the real object/function, but a shadow of it, what we call the shadow target, in order to preserve the language semantics.

See <IP_ADDRESS> step 6 for how direct eval is specced. If you want to do the same thing for document.all, you need to add similar logic in the runtime semantics of:

the typeof operator;
operators based on boolean logic: ||, &&, ? :, !;
operator allowing comparison with null: ==;
statements making use of boolean logic: if, while, do/while, for.
(Fortunately, the newer ?. and ?? operators do not have special treatment of document.all.)

By claudepache https://github.com/tc39/ecma262/pull/673#issuecomment-627219678

The current PR was specifically to sanction what browsers and the HTML spec were already implementing. That is, they felt it was better that the ES spec provided the necessary hook for the HTML spec, rather than the HTML spec monkey-patched the ES spec.

What you are proposing, is modifying the semantics of document.all in a nontrivial way, which implies implementation work and BC concern. If you feel that it is important, it should be a separate issue, and probably indeed a full-fledged proposal.

By claudepache https://github.com/tc39/ecma262/pull/673#issuecomment-627311237
I think it is a good thing to do. Change the meaning of document.all literal to make it Web compatible, and prevent it evaluates to false accidentally, which can improve security.
(See the code example above)
// literal usages
typeof document.all // "undefined"

// non literal usages
function typeof_(x) { return typeof x }
typeof_(document.all) // "object"

I’d be very surprised if that would be web compatible - but itd be worth you making the case to web browsers to gather telemetry about it.

See <IP_ADDRESS> step 6 for how direct eval is specced. If you want to do the same thing for document.all, you need to add similar logic in the runtime semantics of:

the typeof operator;
operators based on boolean logic: ||, &&, ? :, !;
operator allowing comparison with null: ==;
statements making use of boolean logic: if, while, do/while, for.
(Fortunately, the newer ?. and ?? operators do not have special treatment of document.all.)

By claudepache tc39/ecma262#673 (comment)

I correct myself: Copying how direct eval is specified would not work (unless you’re very optimistic about what is needed for web compatibility), because
(somethingThatEvaluatesToFalse || eval)() is not a direct eval (*), while
if (somethingThatEvaluatesToFalse || document.all) should probably test as false.
Another interesting case: should we “support”  if (da = document.all)?

(*) The technical reason is that a || b does not evaluate to a Reference, because it applies GetValue() before returning the result.

browsers to gather telemetry about it

curious about it. do browsers already do that? does the telemetry data for this public or visible in some way?

I think it is a good thing to do. Change the meaning of document.all literal to make it Web compatible, and prevent it evaluates to false accidentally, which can improve security.

FYI, 16 years ago, hacking document.all literal only wasn’t web-compatible, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=259935

function foo() {
    this.ie = document.all;
}
var f = new foo();
if (f.ie) // ...

Damn! It's impossible to do that in the end
Hmm but, does the percent of usage changed now? Just like how we delete other web platform features.

Just to notice, Symbol polyfills rewrite typeof to help functions (so typeof xxx === 'symbol' works), so literals will no longer be literal
Before
if (typeof document.all === 'undefined') {...}

After
function _typeof(val) { /* helper function body... */}

if (_typeof(document.all) === 'undefined') {...}

The code that using a transpiler, won't use document.all IMO

The npm dependencies that use document.all may still be transpiled in some condition. (e.g. some dependency used new syntax that old browser do not support, so they got transpiled all together)

@Jack-Works now that people are sometimes unwisely transpiling node_modules - code they didn't write - that's not necessarily the case.


Issue on page /notebooks/Appendix-MiniProj.html

The Dataset and Model Options
Population Growth
The Question
How well do different mathematical models, e.g., based upon population growth (mechanistic) theory vs. phenomenological ones, fit to functional responses data across species?
Maybe the functional responses data here should be replaced by population growth data ?

Thanks!


Memory leak

🐛 Bug report
Current Behavior
I have an application with multiple forms and I found some memory leaks due to Formik. To be sure Formik is the problem, I created a new app with create-react-app and typescript without adding any other packages like yup, router, etc., only Formik. The I created a Form component with the first example found here https://jaredpalmer.com/formik/docs/overview and a toggle button in App.tsx to mount and unmount the form.
After testing with the performance tab in dev tools and repeating the cicle mount form, call garbage collector, unmount form, call garbage collector a few times, this is the result

As you can see, memory, event listeners and node count are increasing.
This is the result repeating the same mount, unmount, garbage collection process in the memory tab

Gargabe Collector can't reclaim the memory allocated by the objects created by Formik
Your environment

Software
Version(s)

Formik
1.5.7 and 2.0.1-rc.5

React
16.8.6

TypeScript
3.4.5

Browser
74.0.3729.169

npm
6.9.0

Operating System
macOS 10.13.6

Can you create a codesandbox to show how to exactly reproduce this?

https://codesandbox.io/s/formik-codesandbox-template-rhqdj
The behavior is the same when profiling

I'm not certain I can reproduce. Can you investigate the source to figure out areas of interest for a fix?

@jaredpalmer if you raise timeout and toggle during submission memory leak will occur. I just had the same issue in a react native project. If I used isSubmitting from Formik it would cause an error. To fix I had to create my own isSubmitting and isMounted with useEffect cleanup.


Purchasing A new plan

Describe the bug
My account was running out of tokens and I got this notification that said:
"Subscribe to Pro 2 for 3X more usage but I don't see a Pro 2 option among my subscriptions."
Alternatively, just yesterday, I had an option to buy additional 10M tokens which is not viewable anymore.
Link to the Bolt URL that caused the error
https://bolt.new/
Steps to reproduce
Go to any project. Exhaust your tokens. When you check the info just above the chat box, you will see the message with the link to pro 2 which doesn't work.
Expected behavior
A new subscription tier with 3 times more usage.
Screen Recording / Screenshot

Platform

macOS:
Browser: Both Chrome and Safari

Additional context
No response

Same here. Unable to purchase more credits.

@srijan816
Received an update from their team.

They should reactivate soon.


Implement automatic contracts verification

Create a plugin for verifying contracts on Etherscan.
If a user installs this plugin, a new task should be available, which can be used to verify contracts on Etherscan.
An example invocation of the task should be something like npx buidler verify-contract --contract-name EtherToken --address 0x2956356cd2a2bf3202f771f50d3d14a367b48070 --libraries '{"library1": "0x2956356cd2a2bf3202f771f50d3d14a367b48071"}' <constructorArgument1> <constructorArgument2> <constructorArgument3>
This plugin should also add a config field that the user can use to specify their etherscan api key. If no api key was set, the task should ask the user for one.
Desired implementation description:

The plugin should create a new task with the functionality described above. The etherscan API docs is a good place to start.
The plugin should use the flatten task, or one of its internal tasks to get the contracts' code.
The plugin should get the solc version and optimizer settings from the Buidler config.
The plugin should throw a BuidlerPluginError if the contract doesn't exist.
The plugin should throw a BuidlerPluginError if the API key is invalid.
The plugin should throw a BuidlerPluginError if there isn't a contract deployed in the given address.
The plugin should throw a BuidlerPluginError if the libraries hash is invalid for the given contract. Its error message should describe why it is invalid.
The plugin should throw a BuidlerPluginError if the constructor arguments invalid for the given contract. Its error message should describe why they are invalid.
The plugin should throw a BuidlerPluginError if the HTTP request fails (network level error).
The plugin should print an error message if the verification failed. If etherscan provides any reason, show it to the user.
The plugin should print success message if the verification is successful.
The plugin should have unit and/or integration tests. We can provide guidance on how to test each part.
The plugin must be based in the Buidler plugin boilerplate.

@ceresstation this issue is already resolved. @mpetrunic did a great job!
I'll probably merge the PR in another repo, as we are moving to a monorepo, but the work is done.


[bug] Not works with js-ipfs #2564

Describe the bug
refer to Not works with js-ipfs #2564
I created an mini repo.
Reproduction
No response
Expected behavior
No response
Platform and versions
❯ cargo tauri info
Environment
› OS: Mac OS 12.6.0 X64
› Node.js: 16.17.0
› npm: 8.15.0
› pnpm: 7.16.1
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.66.0-nightly
› cargo: 1.66.0-nightly
› Rust toolchain: nightly-x86_64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.0.0-rc.7(outdated, latest: 1.2.0)
› @tauri-apps/api [NPM]: 1.2.0(outdated, latest: 1.2.0)
› tauri [RUST]: 1.1.1,
› tauri-build [RUST]: 1.1.1,
› tao [RUST]: 0.14.0,
› wry [RUST]: 0.21.1,
App
tauri.conf.json error on ``: Additional property '$schema' is not allowed
Stack trace
No response
Additional context
No response

The provided minimal repro https://github.com/moreadgroup/tauri-ipfs, doesn't even compile the front-end due to this vite issue probably https://github.com/vitejs/vite/issues/9062, so we need another minmal repro that actually works.


Fix race condition in System::ClockBuilder

Fix https://github.com/ami-iit/bipedal-locomotion-framework/issues/617 .

Thank you @traversaro


Colab wrong command?

Hi @davidpagnon
I've checked your colab notebook placed here
and i found that it might have some wrong command! (not sure if the openpose is checkedout to specific tag or not)
!sed -i 's/execute_process(COMMAND git checkout master WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}/3rdparty/caffe)/execute_process(COMMAND git checkout f019d0dfe86f49d1140961f8c7dec22130c83154 WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}/3rdparty/caffe)/g' openpose/CMakeLists.txt
This line of code do noting actually!
here is my clone of openpose (today) without checkout, and i can see that openpose/CMakeLists.txt containes lines with git checkout master but all of them are commented out!

either this command is not needed or needs to be modified for replacing the 1807aad with f019d0d for caffe!
Also does it needs to install opencv as a requirement?( i think the openpose > V1.6.0  do not needs the opencv while with the available code on a native ubuntu system, it askes for opencv while making it with the default CMakeList.txt file!
Thanks
Best regards

This is the cmake error

have you check out into specific version of openpose?

If I understand well, you are trying to run the Colab code on a local Ubuntu station?
While both setups are quite similar, a standard Ubuntu installation does not come with as many libraries.
For example, OpenCV is natively installed on Colab and I did not bother install it again. You will likely need to install it on your computer (see the paragraphs coming right after your make error for indications about how to do that).
To be honest, I took most of the code from there and adapted it because it was buggy. I'm not an expert in building project but I'm pretty sure the line of code you're referring to is replacing master with the specific version f019d0dfe86f49d1140961f8c7dec22130c83154 in the CMakeLists.txt file.

I'm pretty sure the line of code you're referring to is replacing master with the specific version f019d0dfe86f49d1140961f8c7dec22130c83154 in the CMakeLists.txt file

This defenately replaces master with f019d0 but as the line including "maste" is commented out, So it does notting! you can ommit this line and test the code!
Thanks for refering to the original code
I've also installed opencv but make -jnproc troughs an error about boost library!
Thats annoying!

Okay I understand what you mean. Did you try replacing 1807aad with the other version? The other version has been tested and works, but apparently it is not needed since it made a change on a commented line.
Concerning the Opencv issue, I am sorry, I don't have a lot of time this week, and I'm not even sure I can help you since I don't have a lot of experience in building with Cmake. I usually just try to change little things until it works, which is definitely not the best way to proceed...
Do you have anyone in your team that could help you? If not, hit me up in a little while (and if so, maybe you could just use the Colab version, which works?)

Hi @p0mad ,
(very) long story short, the colab version should be up now! Don't hesitate to tell me if you face any issues.
I'm closing this for now but if you experience any problems, please reopen the issue.