#Perf: Tutorial: How a page gets populated with content

New Documentation
Title: Populating the page
Summary: An HTTP request is made and, hopefully, a few seconds later, the site appears. Displaying the content involves executing JavaScript, possibly modifying the DOM, calculating styles, calculating layout, and finally rendering the content, which involves painting and compositing, and can involve GPU acceleration on a separate thread.
Linked to from https://developer.mozilla.org/en-US/docs/Web/Performance

Created:
https://developer.mozilla.org/en-US/docs/Glossary/Packet


Improve integration tests

Don't merge this PR until integration test on jenkins passes.

Ping @vmarmol @rjnagal. Integration tests are finally working. Time to get this merged. I want this in before other PRs.

@rjnagal @vmarmol Addressed comments. PTAL

LGTM, waiting on @rjnagal

@rjnagal: Jenkins is flaky when it comes to multiple commits per PR. Ignore the jenkins run for this PR and go ahead with the merge. I tested it manually.

ok :) LGTM


mobile: track network state (wlan/wwan/unreachable) changes when using c++ engine builder.

Title: [One line description](mobile: track network state (wlan/wwan/unreachable) changes when using c++ engine builder.)
Description:
As it is now, only Swift/obj-c and Kotlin/Java engines builder set up network monitors which inform Envoy about network state changes such as wlan->wwan and wwan->wlan transitions which allows the library to refresh its DNS entries and/or recreate connections as needed.
iOS logic for setting up network monitor:
https://github.com/envoyproxy/envoy/blob/cea17494ef49969b888368a5fe1709e347acea2e/mobile/library/objective-c/EnvoyEngineImpl.mm#L440-L444
Android logic for setting up network monitor:
https://github.com/envoyproxy/envoy/blob/cea17494ef49969b888368a5fe1709e347acea2e/mobile/library/java/io/envoyproxy/envoymobile/engine/AndroidEngineImpl.java#L26

FYI @alyssawilk @RyanTheOptimist


Getting error: Uncaught SyntaxError: Unexpected token & after upgrading to 0.5.0

I upgraded from version 0.4.1 to 0.5.0 after npm started complaining about it failing the audit, but I get this error Uncaught SyntaxError: Unexpected token &  in the console. The error seems to be occurring on this line. Which the previous version outputted to script.src = '/' + name.slice(1); but the broken version outputs to script.src = '/' + name.slice(1).
Could it be due to something else in my build configuration? I'm using nodemon and the --experimental-modules flag. Although, I don't think I'm doing anything else out of the ordinary that would cause apostrophes to become escaped.
Sorry I can't provide any more information. Let me know if you're not able to reproduce it, or if any other information could be useful.

I'm having this issue too. It looks like 0.5.0 has switched to using ejs for the loader template and it's escaping the single quotes used when publicPath is set.
The more worrying part of this is that the code for 0.5.0 doesn't seem to be pushed to this repo. This is a great way to backdoors to sneak into build tools.

You are right I did switch to ejs and apparently forgot to push. Apologies!
I’ll fix that and then take a look at the escaping issue :)

master and v0.5.0 tag is pushed. Apologies for failing to do that.

Added a test for publicPath usage and fixe the ejs template.
v0.5.1 should work for you! Please re-open if not.

Thank you!


R Package (k)pcalg/RCIT is not available. RCIT has to be installed from https://github.com/Diviyan-Kalainathan/RCIT

When I am running this code
`
import cdt
import pcalg
#import kpcalg
import networkx as nx
from cdt.causality.graph import PC
from cdt.data import load_dataset
import matplotlib.pyplot as plt
data, graph = load_dataset("sachs")
cdt.SETTINGS.rpath = 'C:/Program Files/R/R-4.1.0/bin/Rscript'
obj = PC()
output = obj.predict(data)
nx.draw_networkx(output, font_size=8)
plt.show()
`
I am getting this error
"R Package (k)pcalg/RCIT is not available. RCIT has to be installed from https://github.com/Diviyan-Kalainathan/RCIT". I have already installed the necessary packages. I need your help on this.
Thanks
PFA

Thank you so much for your response. I am very new to R environment. Can you please tell me where to run the above line? I will check and update you.

Hello ! This command has to be ran in the Windows command line
otherwise, just go to the path and execute the R executable and try to execute library('pcalg')

Error: package or namespace load failed for 'pcalg' in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]):
there is no package called 'graph'
In addition: Warning message:
package 'pcalg' was built under R version 4.1.3
Execution halted

Hello do you tackle this issue? I am facing the same condition as yours

+1 same issue. I need this to work directly off windows. Here are my installed packages.
reqp <- c("pcalg", "kpcalg", "bnlearn", "D2C", "SID", "CAM", "RCIT")
intersect(sort(.packages(all.available = T)), reqp)
[1] "bnlearn" "kpcalg"  "pcalg"   "RCIT"    "SID"

Yet cdt is unable to identify pcalg
cdt.RPackages
['init: False', 'pcalg: False', 'kpcalg: True', 'bnlearn: True', 'sparsebn: False', 'D2C: False', 'SID: True', 'CAM: False', 'RCIT: True']

Is there a way to force cdt to use the pcalg located in my R installation? cdt is already pointing to the right R installation where pcalg is located so unsure what to do or ways to further test.


How to change the UI of adaptive cards

I am using Bot Framework Composer (v2.0.0).
After publishing the bot to Azure, I am using direct line token to integrate the published bot into react app. Is there any way I can change the UI of adaptive cards or manipulate the CSS of adaptive cards through ReactWebChat component of react?

Hello @poojarkpatel i m working in a project like your "chat bot with directline using a react " i have a question for you, do you use the authentication in your bot ? if yes can you please show me this part of authentication because it s not working for me thks

@nahlaGit We are not using any authentication as for now for our Bot. If we come across any such requirement and if we were able to implement it, we will reach out to you. And in meanwhile if you find any solution please let us know.

@poojarkpatel, please look over this answer I provided on Stack Overflow that demonstrates how this can be done.

The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github collection of repos are the preferred platforms for information on submitting bug fixes and feature requests.


gen: Introduce generic import mapping

This introduces actual support for doing import mapping natively in cuetsy.
It's a little awkward and definitely needs some tests, but the new cue.Value.Buildinstance() method introduced in a recent release of CUE makes all the difference here. Knowing that there is hugely helpful.
This will end up allowing us to have imports with core kinds - which i'd swear we had an issue for, but i can't find it now.

@spinillos this should be quite useful, and is in support of a larger goal scenes folks have for schemas

We can put all of this logic inside a new import_mapper.go file and we can start to split a few things.

not sure what this failure with max.MaxInt is about, but haven't investigated deeply

glad we're passing, but definitely need some tests on this first.
there are weird cases to be checked here depending on whether/how the input is unified, and properties of the root instance being looked up


Brushing gets stuck if the user scrolls while holding alt

Sometimes after pressing alt the paintbrush remains selected and its not possible to deselect it. Im not sure what causes this. Otherwise it works very well.

I figured out how to replicate this, if you scroll while holding alt (Im not sure if you also need to be currently actively brushing) the brush will get stuck (at least on my machine).

Thanks! Nice work =)
I'm probably just missing the button release event because the window is losing focus or something. It shouldn't be too hard to fix =)

I was only disabling the brushing mode on the keyup event, which could be missed if the users released the alt key while the window was out of focus. I'm being a bit more aggressive with the disabling of the brushing mode now, and I can't seem to reproduce it anymore, so I'll mark this as fixed and we can reopen it if we find another case where it's still happening.

great!


Unnecessary (non-dev)dependency on babel-plugin-transform-runtime

It looks like the "babel-plugin-transform-runtime" dependency could be a devDependency instead.

same problem


MediaObject: Button for navigate audio(next, previous) in Google Home Hub is disable

I follow the instruction in the article:
https://medium.com/google-developers/two-minute-actions-long-running-audio-c2ed9507493a.
When I test the actions on Google Home Hub, although I can say next and previous for another audio, the next and previous button of media player are disabled. How can I enable them?
I have posted on stackoverflow too so you can view code and image there:
https://stackoverflow.com/questions/56721059/how-to-enable-next-button-of-music-actions-in-google-home-hub
I will appreciate any help. Thanks

I got the answer from stackoverflow at that time there is no way for developer to develop a third-party application that has enable next and previous button.
You can see it here
https://stackoverflow.com/questions/56721059/how-to-enable-next-button-of-music-actions-in-google-home-hub?noredirect=1#comment100076548_56721059

Note that spoken commands sometimes work, but see #310 for some known issues with that.


fixed 401 error on quotes and fundamentals

to solve auth requirement described here:
https://github.com/Jamonek/Robinhood/issues/167

When update to the provided code, I get the following error.
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.robinhood.com/orders/


Reorganized SOlution

Moved the web site to a sub folder and created a top level solution.
Added a Azure Functions project for feeding to ADT

Just need to get the Docker build working again before merge.


🚀 Feature: Use words/phrases with hyperlink in response according to their reference in docs

🔖 Feature description
Documents like HTML, MD, PDF, and DOCX can include hyperlinked words or phrases. When a response is generated that contains those words/phrases it is nice to bring the URL under those hyperlinks.
🎤 Why is this feature needed ?
For ease of reading the response from document chat. For example, source doc includes this:
To generate the workflow follow this [example](http://path.to.example) file.
Currently it seems the URL part is not considered when reading and training the doc.
So when asking about "how to generate workflow", the chat refers to that "example" without providing the link.
✌ How do you aim to achieve this?
Keep track of hyperlinks from source doc and insert them in the response.
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
Yes I am willing to submit a PR!

Important PR! thank you!

Should work for remote ingestion


i18n with next-intl fails to register routes

I tried using next-intl with next-on-pages, but I'm getting the message below:
⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡ The following functions were not configured to run with the Edge Runtime:
⚡
⚡  - de
⚡  - en

Seems like the dynamic routes don't get picked up

@Hades32 have you found any workarounds?

I stopped using this repo. It misses a lot of features. I now use preact

@Hades32 Does your Preact support SEO well?
Vercel still builds well NextJs projects, but it runs edge functions slower much than CF Workers.
For Website frontend only, I use CF Application plan (CDN, proxy..) routing to Vercel.
For backend, I buy a CF Workers plan.

I still use built-in i18n and have this solution, pls try:
(i) Keep next.config.js
i18n: {
    locales: ['vi',  'en'],
    defaultLocale: 'vi',
    localeDetection: false,
  },

(ii) Add this line to public/_redirects file
/ /vi 301

All build runs well, and I never face any issue. The default locale "vi" also removed on URL after first time render home page from / or /vi

I believe that we may have identified a way that we can support the i18n option from the next.config.js, now that we have the new routing system. I'll be looking into a way to introduce proper support.


Add Yofri to Contributors list

Hey @Yofri: can you reopen this pull request so that I can merge it to this project?


Use UTF-8 encoding in events (fixes #181)

Cf #181
I've also added non-ASCII characters in the unit test.

Thanks so much @gaelrenoux ! Scheduling. @gaelrenoux has signed the CLA.


Problems in NodeJS environment.

I have a problem in testing via mounting enzyme component.
Problem line, for example (from extra/material.js):
if ('CustomEvent' in window && typeof window.CustomEvent === 'function') {
        ev = new CustomEvent('mdl-componentupgraded', {

This will fail in NodeJS, because CustomEvent is not defined in global scope, however window.CustomEvent is OK. Currently, I'm fixing this as doing
require('react-mdl/extra/material');
global.Element = global.window.Element;
global.CustomEvent = global.window.CustomEvent;
global.Event = global.window.Event;
global.NodeList = global.window.NodeList;
global.Node = global.window.Node;

However I don't feel this is right, it's preferable for me to not have this chunk of code at all, by changing problem line to
ev = new window.CustomEvent('mdl-componentupgraded', {

I believe you might be able to skip the use of react-mdl/extra-material inside a nodejs env.
Have you tried it?


Update licensing-service-plan-reference.md

Added missing service plans to ENTERPRISE MOBILITY + SECURITY E5

@Nicholak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#Sign-off

@Nicholak-MS: I'm sorry - only the author of this article, @daveba, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @Nicholak-MS - This pull request was opened in the public repo. (It's easy to do.) Would you make this content update in the private repo instead? You can sign off there. Thank you. We'll close this PR.

Apologies, I will open a new PR in the private repo.


Feat/api

Added Ky http client.
Created apiService and apiRoutes ts files.
Added apiService logic to fetch from given endpoints.
Added types for http request responses.
Merged develop into feat/api and resolve merge conflicts.

Noted, will be added back into linter.


Invalid Syntax: def expect(self, pattern, timeout=-1, searchwindowsize=-1, async=False):

Python 3.7.5
Install from github.
$python demo.py
Traceback (most recent call last):
File "demo.py", line 2, in
from pandasgui import show
File "/home/steph/Projects/pandasgui/pandasgui/init.py", line 1, in
from pandasgui.gui import show
File "/home/steph/Projects/pandasgui/pandasgui/gui.py", line 10, in
from pandasgui.widgets import PivotDialog, ScatterDialog
File "/home/steph/Projects/pandasgui/pandasgui/widgets/init.py", line 8, in
from pandasgui.widgets.plotly_viewer import PlotlyViewer
File "/home/steph/Projects/pandasgui/pandasgui/widgets/plotly_viewer.py", line 5, in
import plotly
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/plotly/init.py", line 30, in
from plotly import (
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/plotly/graph_objs/init.py", line 98268, in
import ipywidgets
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/ipywidgets/init.py", line 23, in
from IPython import get_ipython
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/init.py", line 55, in
from .core.application import Application
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/core/crashhandler.py", line 27, in
from IPython.core import ultratb
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/core/ultratb.py", line 119, in
from IPython.utils import path as util_path
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/utils/path.py", line 17, in
from IPython.utils.process import system
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/utils/process.py", line 19, in
from ._process_posix import system, getoutput, arg_split, check_pid
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/IPython/utils/_process_posix.py", line 23, in
import pexpect
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/pexpect/init.py", line 75, in
from .pty_spawn import spawn, spawnu
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/pexpect/pty_spawn.py", line 14, in
from .spawnbase import SpawnBase
File "/home/steph/anaconda3/envs/bert/lib/python3.7/site-packages/pexpect/spawnbase.py", line 224
def expect(self, pattern, timeout=-1, searchwindowsize=-1, async=False):
^
SyntaxError: invalid syntax

Solved one issue:
sudo apt-get remove python-pexpect python3-pexpect
pip install --upgrade pexpect

sudo apt-get remove python-pexpect python3-pexpect
pip install --upgrade pexpect


Apollo6.0 With dreamview not work

My apollo version is 6.0 (Actually I don't know why even if I have cloned the newest Apollo version, the ./dev_start.sh would direct to 6.0).   And when I build the apollo and enter the dreamview, the page says the lidar and GPS are not activated. Interestingly, this error is missing in the official apollo.

We recommend using the following steps to see if the system can be restored.

Go to the apollo directory and run ./docker/scripts/dev_start.sh
Run 'bash docker/scripts/ dev_int.sh' to access the container
Delete the compilation cache and recompile by executing './ Apolo.sh clean -a '  and then  './ apolo.sh build_gpu '

Looking forward to your feedback. It is also recommended to upgrade to apollo7.0.

@JasonBourne1998 We recommend using the following steps to see if the system can be restored.

Go to the apollo directory and run ./docker/scripts/dev_start.sh
Run 'bash docker/scripts/ dev_int.sh' to access the container
Delete the compilation cache and recompile by executing './ Apolo.sh clean -a '  and then  './ apolo.sh build_gpu '

Looking forward to your feedback. It is also recommended to upgrade to apollo7.0.

Actually, I am confused about how to upgrade to 7.0. Since I already clone your apollo package at https://github.com/guardstrikelab/apollo, it ought to be 7.0.

@JasonBourne1998 We recommend using the following steps to see if the system can be restored.

Go to the apollo directory and run ./docker/scripts/dev_start.sh
Run 'bash docker/scripts/ dev_int.sh' to access the container
Delete the compilation cache and recompile by executing './ Apolo.sh clean -a '  and then  './ apolo.sh build_gpu '

Looking forward to your feedback. It is also recommended to upgrade to apollo7.0.

I have recompiled and it still does not work. I guess the error was caused by the mismatch version between dreamview(7.0) and Apollo(6.0). @daohu527 sorry to bother you, but could you plz explain why my apollo version couldn't switch to 7.0?

Hi guys, sorry about the delay from our support team. Almost all of our team members got hit by covid during the past two weeks. We expect to resume our work this week, and will get back to you all soon.

Hi @JasonBourne1998,
Just because the Apollo Development Docker was tagged with "-20210914_1336" doesn't mean you're running Apollo-6.0. It is just a development environment. dev_start.sh will mount $APOLLO_ROOT_DIR (which is the apollo code repo you cloned from us, with version > 7.0) as /apollo within the container.
If you follow our instructions in the readme you will get an Apollo vehicle running in Carla.
Could you let us know what you're trying to achieve?

This issue will be closed if there are no more activity, thanks for your attention.

It looks like this issue hasn’t been active in longer than a few weeks. In the absence of more information, we will close it, If you find that this is still a problem, please feel free to reopen it.


Add feature so a user knows their download is coming and they should not to hit the button more than once

Is your feature request related to a problem? Please describe.
When a user clicks "Download Working Dataset" or "Download Final Dataset" the application does not do anything right away. It can take over a minute for the file to download.
Describe the solution you'd like
It would be helpful if there was a pop up to let the user know it is running and that they should not hit the button again. It could be the same as the pop up we use for the flag page to let a user know they are running:

Additional context

Need to disable buttons (possibly) and set a block on the window.  The disable button is a 20 minute fix.  The progress screen is an 1 hour fix since I need to figure out how to do it in a 'standardized' fashion.

I have the spinner modal and disable-button working. I can't get the file to download though.  I'll come back to it.

Additionally - the download buttons are active by default.  They should be inactive until there is data loaded - I think it is tadat$data or something similar.
There is a bigger problem.  The TADA_summary panel is supposed to be hidden until there is data.  But instead it is displayed always.  It has something to do with setting tadat$raw = NULL - which makes req(tadat$raw) == TRUE

I figured out how to disable the button once it is clicked.  The part that is not shown on the googles, is that the id for elements in this panel have 2 parts - the id of the panel ('TADA_summary_1') and the id of the button 'download_button').  So the code for disabling and enabling reads
output$download_working <- shiny::downloadHandler(
      filename = function() {
        paste0(tadat$default_outfile, "_working.zip")
      },
      content = function(fname) {
        shinyjs::disable("TADA_summary_1-download_working")
        on.exit(shinyjs::enable("TADA_summary_1-download_working"))
....


🐛 BUG: Can't create a worker from a github repository

What version of Wrangler are you using?
2.1.13
What operating system are you using?
Windows
Describe the Bug
Can't create a worker from a github repository. This error always occurs while creating the worker.

Hi @ambit741235WHJR thanks for reporting this - could you confirm which command you're running?
I just tried the following and it worked:
wrangler generate projectname2 https://github.com/stripe-samples/stripe-node-cloudflare-worker-template

 ⛅ wrangler 2.1.13
--------------------
Creating a worker in projectname2 from https://github.com/stripe-samples/stripe-node-cloudflare-worker-template
✨ Success!

Hi @rozenmd, I used the following command to create the worker but still not working.
wrangler generate stripe-worker https://github.com/stripe-samples/stripe-node-cloudflare-worker-template

Even when I tried to execute the command you executed, it still throws the same error.
❯ wrangler generate projectname2 https://github.com/stripe-samples/stripe-node-cloudflare-worker-template
 ⛅ wrangler 2.1.13
--------------------
Creating a worker in projectname2 from https://github.com/stripe-samples/stripe-node-cloudflare-worker-template

✘ [ERROR] Failed to find "undefined" in https://github.com/stripe-samples/stripe-node-cloudflare-worker-template.git

If you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new/choose

That's strange, how about git -v?

That's strange, how about git -v?

@rozenmd
git version 2.35.1.windows.2

I’m having the same issue on Mac with wrangler 2.1.13 and git 2.23.0 when trying to use the official worker-typescript-template repo.


Jgonzalesxx patch 1

Replace the following text with your own catchy marketing slogan for ACME.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


Newsletter 224: Add german translation

Also contains minor fixes to the German style guide.

@Xekyo : Would you be so kind to do the usual review? Thank you in advance. :bow:

@Xekyo, @bitschmidty : Könntet ihr auf die Ausgabe einen Blick werfen? Vielen Dank!

@tschweg can you take a look at @Xekyo 's comments?

@bitschmidty : Absolutely. Sorry for the delay, I was rather swamped the last 2 weeks. I'll have the corrections in within the next 1-2 days.

Yeah, I feel you. It also took me forever to finish reviewing the PR. It would be nice if we had a couple more people look at it with us.

So much for 1-2 days :sweat_smile: But we should be good now with the changes. Could I trouble you for a final review agian, @Xekyo

I only read the changes again, but they looked good to me. About to merge :)

Rebased on master

Thanks for the long wind!


Typo in a name

Just a quick typo correction, since it's on a package name

Thanks @alesvaupotic good catch. My bad.


Write own include preprocessor

For the shaders using string manipulation i should be able to include the contents of other shaders, simply concatenating sources of other shaders with the one containing the include
Will be usefully for adding multiple lights to the scene

Closed due to the discontinuity of the project


Svg stacking

https://hofmannsven.com/2013/laboratory/svg-stacking/

This is also called fragment identifiers: http://caniuse.com/#search=svg fragment

Oh, you're right.


Documentation should explain how to use DevKitMQTTClient

In API Reference on IoT DevKit Docs  developer should have an explanation how to use DevKitMQTTClient.
For example, how to use these functions and what's really mean each one function(based on IoT Hub documentation)
DevKitMQTTClient_SetSendConfirmationCallback(sendConfirmationCallback);
DevKitMQTTClient_SetMessageCallback(messageCallback);
DevKitMQTTClient_SetDeviceTwinCallback(deviceTwinCallback);
DevKitMQTTClient_SetDeviceMethodCallback(deviceMethodCallback);

What's the status on that issue? Where can the API documentation be found?

@ericbrunner As I know, at this moment API documentation doesn't exists. You can read my article about this(just snippet) to figure out how to use MQTT in AZ3166.

Will have reference doc for these APIs, thanks @Xeinaemm and @ericbrunner


No token renewal on OS update

When Android is upgraded, Google offers no guarantee the GCM token will keep working, and we saw some cases where GCM would stop working after an upgrade to Android 5.1.
EasyGCM should probably listen to system boot and renew the GCM token if needed:
<uses-permission
    android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
...
<receiver android:name=".BootReceiver">
    <intent-filter>
        <action android:name="android.intent.action.BOOT_COMPLETED" />
    </intent-filter>
</receiver>

Waiting a few seconds for the network to be available, or even better, some exponential backoff, could be a good idea.

This would require adding a new permission (RECEIVE_BOOT_COMPLETED) - which I would like to avoid. I think we could do this as an optional feature of the library - you would specify the permission in your application manifest and the library would then handle it. I will have to think about this. Or maybe if someone can submit a pull request.

@DanielNovak do you have any news about this?
If you want a PR, what would be some code design guidelines you'd have in mind?

@adrien-aubel Sorry - no news yet, but I have it in my backlog. I haven't thought about it in detail yet - so now specific code guidelines :-(. I can't promise an ETA, but I would like to at least start this weekend on this.

Ping @DanielNovak :)

@adrien-aubel do not worry about code guidelines, regular Android style is fine. Just make a PR, that's where we can discuss :-)

This could be fixed in version 1.5.0 as we started using com.google.android.gms.iid.InstanceID intent filter to renew the registration ID. This should be called also when device information is changed, which is probably also this case. More info here: https://developers.google.com/instance-id/guides/android-implementation
Probably needs testing, before we can close this issue


Theming

In flexx, layout is mostly determined by choice of widgets and their configuration. Styling however is "open for interpretation". Since styling a webpage is very much an interactive process, it would be nice to have a resource available for editing that can reload upon page refresh, instead of restarting the server.
A static CSS stylesheet that is served independently is one option for such functionality. Determining global style, like background color, font family and size, and so on, could go in there.
Default styling for widgets like ui.TabPanel is nice when you want to prototype things, but doesn't lend itself very much to styling a production application. Perhaps the docs could include a section that explain how you can apply a custom "theme" to the flexx-provided widgets? This is probably also easiest to implement using static stylesheets. Related to #139, I think.

I agree that Flexx needs first class support for theming.
Though for shorter term. You can still collect all CSS in one place and then set it as the CSS attribute of a single class. The CSS of all class is simply collected and put together in one CSS file by Flexx, so you could put any style there.
Another option could be to create a static .css file and make Flexx load it as a resource similar to howe we load additional .js resources.
The fact that the TabPanel is so hard to style is I think mainly because its implemented via Phosphor which has its own CSS prefix etc. This is sometithing that can also possibly be improved.

It would be nice to break the CSS that is currently in Flexx into flexx.css and flexx.theme.default.css, so that you can easily add your own theme. As far as I can see, flexx.app.assets already supports serving custom stylesheets, so this shouldn't be a difficult change.

Another question that I have: how likely is it that HTML structure or classes will change from one release of Flexx to the next? Is it possible that it will break stylesheets?

That's a good question. For simple widgets it should not change much. Some more complex widgets could, e.g. Canvas changed along the way to allow better positioning. Anything based on Phosphor (i.e. all layout widgets) I have not much control over. Phosphor is turning into 1.0 but I am not sure if this means that the underlying HTML structure will never change.
BTW: CSS theming migh be an issue that is also relevant to the Phosphor project.

Some updates:
In the form.py example I added a few lines illustrating how theming can be done via CSS. In this case the CSS is added to the application widget, but you can also write an actual css file and add it as an asset.
Flexx is no longer based on Phosphor, so the dom structure should be pretty stable from here on.
Work that remains would be to factor out the theme-specific CSS into a separate file and add that as a default asset, which can easily be used as starting point for custom themes.


Add more elaborate block breaking

Blocks shouldn't break instantly, have various hardness levels, and there should be appropriate tools to break them.
What blocks yield upon breaking should also be dependent on the tool used to break them.
These values should be configurable via a config file such as .toml so they can be edited without recompiling

[x] 1. Figure out a good format for the config
[x] 2. Implement deserialization into a Bevy Resource
[ ] 3. Implement breaking with hardness
[ ] 4. Implement looting (blocked by #12)

Current format choice
#![enable(implicit_some)]
BlockBreaking({
    Default: {
        Stone: ( hardness: 7, drops: Rock, min: 4, max: 6 ),
        Limestone: ( hardness: 5.5, drops: Lime, min: 1, max: 2 ),
        Log: ( hardness: 5, drops: Stick, min: 2, max: 3 ),
        // will fallback on 'log' family for the other info
        Acacialog: ( hardness: 6 ),
        // if no drop quantity is specified it defaults to 1
        Soil: ( hardness: 3, drops: Self ),
        Sand: ( hardness: 1.5 ),
    },
    Shovel: {
        Soil: ( hardness: 1.5 ),
        Sand: ( hardness: 0.75 ),
    },
    Pickaxe: {
        Stone: ( hardness: 2.5, drops: Self ),
        Glass: ( hardness: 1 ),
    },
    Axe: {
        // you get the idea
    },
})

Limitations:

this syntax only allows blocks to drop 1 type of stuff, but it can be extended
keyword "self" used to express that a block drops itself

see discussion below (with myself 🤪) for other ideas and pros/cons

Some blocs will have the same hardness/yield properties (like wood types), or will have the same preferred tool (like rocks) so having a way to group blocs into families to write the config files would be really useful.

Ok here's a first draft (with example data):
# blocks are allowed to be in 0, 1 or more families !
[block_family]
stone = ["cobblestone", "stone", "limestone"]
soil = ["dirt", "sand", "mud", "snow"]
log = ["oaklog", "birchlog", "sequoialog"]
leaves = ["oakleaves", "birchleaves", "sequoialeaves"]
glass = ["glass", "ice"]

# unspecified hardness will make the block unbreakable (eg bedrock)
[hardness]
# block hardness when no tool is used (also fallback values if the tool did not specify the hardness for a block)
# both block families and block can be specified (the block will take precedence over the block family)
default = {
  stone = 7, limestone = 5.5,
  log = 5, acacialog = 6,
  soil = 3, sand = 1.5
}

shovel = { soil = 1.5, sand = 0.75 }

# limestone is specified directly in 'default' and only 'stone' is specified here but hardness 2.5 will be chosen if the player breaks a limestone with a pickaxe (tool takes precedence)
pickaxe = { stone = 2.5, glass = 1. }

# we could image the pebble being a tool, prompting the player to look for one at the beginning
pebble = { stone = 4, limestone = 3, log = 3 }

# unspecified loot means the block will loot nothing upon breaking
[loot]
default = {
  stone = [4, 6, "pebble"],
  limestone = [1, 2, "lime"],
  log = [1, 2, "stick"]
}

# really not sure about this syntax, how should we specify that a bloc will drop itself ?
pickaxe = { stone = [1, "self"] }

It's probably very flawed, so feedback is welcome :)

I think this is good enough to start implementing, so I'm marking the first to-do as done :p

I just learned that TOML doesn't support nested dict the way I wrote it (I would need to flatten it with a pickaxe.stone =  syntax) so I'm switching to RON format instead because it's still somewhat simple to write than JSON and it was made to deserialize into Rust objects.
I'm updating the format to reflect this :)

I ended up hardcoding the block families because it was way more convenient in the code and I don't expect block families to change that often, I also added tool families (pickaxe, axe, etc.) for the same reason.

There has been a plot twist, turns out Ron does not play well with untagged enum (which I need to keep the config file less verbose) so it was deserializing total nonsense. So I need to try another file format such as JSON (but I kinda dislike the "quotes" everywhere, so maybe I'll look for another alternative)
Still, I wrote some code to make all the fallbacks and default value logic for tool/block families work, that will be useful no matter the file format 👍

urgh turns out some of the enum I use can't really be untagged it seems https://github.com/serde-rs/serde/issues/1740
So I'll have to find a workaround

Ok we're so back, thanks to this https://github.com/serde-rs/serde/issues/1560#issuecomment-1666846833
I have to use JSON5 instead of Ron though because Ron simply wouldn't work, but that's almost the same syntax, spare for a few more quotes inside the drop info.

Note for myself of what should reset the breaking action:

change of target
change of selected hotbar slot

other case that we don't care about now but might be relevant later:

block gets moved by a piston (kinda counts as change of target but harder to deal with)

First version done !


Don't expose all errors to the client

for example, https://github.com/graphcool-examples/functions/blob/master/authentication/email-user-management/functions/authenticate/authenticate.js#L51 shouldn't be returned to the user.

fixed in #72


[WIP] Enable testing charts with test values

What this PR does / why we need it:
Enables testing charts with test values.

The first commit refactors changed.sh. I ran Shellcheck across it and applied fixes. Some variable were upper, some were lower case. I made that consistent: lower case for script variables, upper case for environment variables.
The second commit updates changed.sh such that the script installs and tests the chart for any *-values.yaml found in the ci folder within the chart's directory.

I added stable/testdummy for testing this which will be removed before merging.
Which issue this PR fixes:
Fixes #3943

The chart included for testing has two different values files for
/retest

I cleaned these up manually but it doesn't look like cleanup is happening.

You can see in the log that clean-up happens. I bet these are leftovers from my tests when clean-up failed in some cases.

/lgtm


auth_basic() doesnt work

I have a setup route function in my python code. I can't use @route and @auth_basic. I use like this:
>def setupRoutes():
>      auth_basic(auth, text = 'auth Error')
>      route('/in', 'ANY', self.inputPage)
but in it, auth_basic() doesn't work and just open inputPage. how can I use it in a project?

Is this what you required?
https://stackoverflow.com/questions/52461587/basic-auth-authentication-in-bottle


Disable bluefin step template updater for 3.12 and above

As its natively built into Octopus as of 3.12.0

Feel free to squash the commits on this one :)


Ensure request method accepts UPDATE, PATCH & DELETE verbs

This will be hard to test sadly without mocking or sending requests to a non-realtime server, but we should do our best to confirm request support these verbs.
See https://github.com/ably/docs/pull/493
┆Issue is synchronized with this Jira Story by Unito

@maratal should this issue be closed if this has already been implemented?


MerkleTrie root in BlockchainTree

Describe the feature
Add marketization of substate inside blockchain tree
Additional context
No response

Is this because in chain.rs we only call validate_and_execute w/o any further verification?
https://github.com/paradigmxyz/reth/blob/c5f197dd957255e9999e39a3d6c365d2f0ef15a6/crates/executor/src/blockchain_tree/chain.rs#L180-L198


Respect original formatting/whitespace

Describe the bug
(This might be too hard and out of scope depending on the implementation. If so, feel free to close)
The repair removes whitespace, so that if the LLM responds with:
{
  "foo": "bar"
}

repair "corrects" it to
{"foo":"bar"}

This makes it hard to detect if an actual repair was made.
To Reproduce
repair JSON with whitespace
Expected behavior
whitespace is preserved

This is an interesting issue because the library isn't stripping whitespaces if not trailing ones, the behavior is the one of json.dumps().
One could argue that I shouldn't "redump" a valid json but that would cause an issue when return_objects=True on a valid json. I could fix this by redumping only on return_objects=True but you see that it gets kinda complicated :)


[ Idea ] Preprocessor Selector

A nice feature for this node suite, would be a dedicated preprocessor selector.
Now I can connect the [ AIO Aux Preprocessor ] node to a primitive.
But primitives have limitations.
For instance, Anything Everywhere? does not work with primitives.
The rgthree suite has a similar selector, but for KSampler configuration.
This allows me to use the same sampler and sheduler, throughout the workflow, via AE nodes.
Now, I can also use AE nodes to set the ControlNet model, throughout the workflow.
Because the "vanilla" [ Load ControlNet Model ] node also works with AE.
It would be great to do the same with the ControlNet Preprocessor !

This was already added to the Preprocessor node suite.
https://github.com/Fannovel16/comfyui_controlnet_aux/pull/291


feat(wallet): implement drep registration tracker

Context
We need to add an observable to the wallet to follow drep registrations / de-registrations;
it will be used by Lace web-extension, so it must be added to the ObservableWallet interface, and in observableWalletProperties: RemoteApiProperties.

Great work, @vetalcore !
Please retarget the merge on master branch. Lace uses SDK versions generated from master. conway-era is for back-end only changes.
You might have to split it in two PRs:

DRep tracker -> master
master -> conway-era
Update e2e test in conway-era to use drep tracker.

Great work, @vetalcore ! Please retarget the merge on master branch. Lace uses SDK versions generated from master. conway-era is for back-end only changes. You might have to split it in 3 PRs:

DRep tracker -> master
master -> conway-era
Update e2e test to use drep tracker -> conway-era.

@mirceahasegan retargeted on master.
Would cover other two once this one is merged.


Allow client to take a screenshot

Would it be possible to add a command-line argument to allow the client to take a screenshot? I am writing a short script to capture the screen, but it's latency-sensitive, and the default way of using screencap takes two full seconds just to encode to JPG. Anything cutting down on that would be very welcome.

Would it be possible to add a command-line argument to allow the client to take a screenshot?

A command-line argument? So it would take a screenshot and exit?
Or a shortcut, to save the current frame to a file somewhere?

As I need to control it programmatically, it would be most convenient for me if it could take a screenshot and exit, yes. Right now I am looking into whether I can write a small client to speak the protocol and connect to the device to grab a single frame, any information you may have would be of great help.

That would probably not be faster than screencap:
adb exec-out screencap -p > screenshot.png

Starting the java application through app_process is already about 800ms, then the screen would be captured, encoded, transmitted, and saved on the client. If this is faster than screencap, then screencap must be fixed :)

Ah, I thought the server would already be running. Yes, you may be right. screencap takes 250ms or so to capture, but 2 sec to convert to png, so it's pretty slow. Feel free to close this ticket, thank you!

I didn't know about exec-out so I was doing a save-then-pull, exec-out only takes a few ms, thank you!

I thought the server would already be running.

Ah ok :)
To be faster, scrcpy could be running, and receive (from whatever channel) a request to take a screenshot, it already has the frame, so it would encode/save it locally (on the computer, which is probably faster than the device to encode a png).
Too specific though.

Yeah, too specific and screencap is already fast enough with the exec-out trick.
Thanks for the help and for a fantastic project!

@skorokithakis   but  I need 2 second

To be faster, scrcpy could be running, and receive (from whatever channel) a request to take a screenshot, it already has the frame, so it would encode/save it locally (on the computer, which is probably faster than the device to encode a png).

Any hint how could I achieve this? I am interested in to develop such a feature.
I am already saving a bitmap from the SDL window, but the picture quality is not that great, have H.264 artifacts.
What you described on that comment would improve picture quality?
Thanks Romain

@dedosmedia see #684

I thought the server would already be running.

Ah ok :)
To be faster, scrcpy could be running, and receive (from whatever channel) a request to take a screenshot, it already has the frame, so it would encode/save it locally (on the computer, which is probably faster than the device to encode a png).
Too specific though.

Dear @rom1v, thank you for your workaround suggestion. Now I managed to write a simple bash script to automatically execute scrcpy, request screenshot in ubuntu using gnome-screenshot (no window), save it, & close the scrcpy window. The problem is the captured image resolution is not correct as my device (an Android TV) has a 2k resolution. This is because my PC monitor aspect ratio is 16:10 while the TV itself aspect ratio is 16:9. (Already using ctrl + G shortcut). However, the tool I'm developing has a requirement to preserve the original device resolution. Any idea how to solve this? adb screencap doesn't always reliable because it can't capture some screens (especially 3rd party apps i.e., YouTube main screen), which will return an empty png file.


Handle NaNs in ndimage.shift

I tried to use scipy.ndimage.interpolation.shift on a combined Hubble image, but because the edges of my input image were NaNs where there were no valid data points, the output image had all pixels set to NaN. I had to put a line in my code to set all NaNs in my input image to 0 before running the shift task.
It would help the users if this task could handle NaNs somewhere in the image without setting all values in the output image to NaN.
The code simply read in an image with fits.open, ran shift, and saved the output image, which displayed as all NaNs.
There was no error printed to screen, so no traceback message to show here, just the behavior of the task.
Scipy/Numpy/Python version information:
<<Output from 'import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)'>>

print(scipy.version, numpy.version, sys.version_info)
1.1.0 1.14.3 sys.version_info(major=3, minor=5, micro=5, releaselevel='final', serial=0)

By setting the NaNs to 0 in my input image, I was able to get the task to work to my satisfaction, but it would be a serious improvement if the code could properly handle NaNs without needing a work-around.

this is by design - NaN's in your input usually indicate something went wrong. this isn't actionable and not specific to ndimage.shift (many functions work like this), so closing.

Many astronomical images have a few NaNs in locations of bad pixels or edge effects. Those few pixels are considered bad and do not need to be treated. However, the remainder of the image consists of good pixels, and those good pixels should not be set to NaN in the output image. A few bad NaN pixels do not mean the entire image is bad. If marking the entire image bad due to a handful of NaN pixels is by design, then this is basically useless for astronomy.


Changes to add density following adjoint feature

What changes does this PR introduce?
This PR adds the changes needed to introduce a density following adjoint feature.
What is the current behaviour?
#483 - this issue explains how the new feature is intended to work.
Does this PR introduce a breaking change?
No
Other information:
Suggested addition to tag-index
(To avoid unnecessary merge conflicts, please don't update tag-index. One of the admins will do that when merging your pull request.)

@ciarapimm
I tried this with your https://github.com/ciarapimm/verification_other/tree/cp_testcase/global_oce_cs32 and there are extensive recomputation warnings associated with: The responsible variables are : ac2d,as2d,aw2d,pc,ps,pw
and main_do_loop is called again within a second loop over ilev_1 (which is the innermost checkout loop counter). Also (probably follow on) do_oceanic_phys is called again from forward_step_ad, which we would like to avoid. Do you see that too?

Thank you @mjlosch for your very helpful comment.
Could you please clarify to me in a bit more detail where you find these warnings, as I am not sure when this is happening?

After make adtaf (part of make adall) to generate the AD-code, you'll get a taf_ad.log file that contains a lot of information about the code generation. Particularly interesting are these RECOMPUTATION warnings. Some of the are "benign" and we tend to ignore them, but some are (very) expensive, especially when they appear in the_main_loop.f. You will also see in the AD-code, that for each inner loop round there are ilev_1 additional calls of main_do_loop (basically the entire model time step). So you call the model (N!) times too often (if N=nchkptlev_1) in each of the nhkptlev_2*nckptlev_3 loop rounds.
Compare the structure of the_main_loop_ad and forward_step_ad (and the taf_ad.log files) between upstream/master and this PR, you'll see the difference immediately. "testreport" now counts, how often do_oceanic_phys (dop) and load_fields_driver (led) are called. Both should be 1 only. Again, compare between upstream/master and this PR.

For the record, this is what I did to download and compile this branch and the test experiment:
git remote add ciarapimm https://github.com/ciarapimm/MITgcm.git
git fetch ciarapimm
git checkout --track ciarapimm/cp_issue483
git clone -b cp_testcase git@github.com:ciarapimm/verification_other.git

cd verification_other
../verification/testreport -adm -ncad -devel -t global_oce_cs32

The run will fail because I did not download any forcing files etc., but I am only interested in the compilation at this point. This leads to a taf_ad.log that contains at least 9 new recomputations warnings, all in the_main_loop, here's the first one:
TAF RECOMPUTATION LOOP WARNING DOLOOP_STMT the_main_loop.for:3114 in the_main_loop
extensive recomputations are required.
The responsible variables are : ac2d,as2d,aw2d,pc,ps,pw

I think one way forward is to find places where the fields ac2d,as2d,aw2d,pc,ps,pw are already stored and adjust the corresponding cpp-flags.
The next question is why these fields need storing after your changes: They are the matrix coefficients and preconditioner coefficients of the 2D barotropic pressure solver (cg2d.F) and are already stored with NONLIN_FRSURF defined (which is the case in the global_oce_cs-experiment). It's not clear why your relatively simple changes have such a large effect on the recomputation/flow analysis. Maybe you can try to precompute a 2D density field per player before computing the mask?

@ciarapimm after unsuccessfully fiddling with your code for quite some time, I took a leap (in German "Flucht nach vorn"= something like "running away towards the enemy lines") and merged the upstream/master into this branch. This fixed all recomputation problem that I had. I don't want to push this merge to your PR, because I had some issue during the merge related to ecco.h, which has changed to upper case ECCO.h, a difference that my MacOS computer does not appreciate. So could you please try and merge the upstream master into your branch and push it? Instructions are at the end of the quickstart guide section in the manual. During the merge, you'll have to carry over your changes to ecco.h into ECCO.h, otherwise they will be lost.

Thanks @mjlosch! When we tested this ourselves using https://github.com/ciarapimm/verification_other/tree/cp_testcase/global_oce_cs32 , I would run two short tests one with gencost_useDensityMask(1) = .TRUE., and one with gencost_useDensityMask(1) = .FALSE.,. in data.ecco. If you set the density range to be very large in data.ecco, then the cases with the density following feature on and off will give approximately the same results. This is so the density following feature makes sure to keep all of the depths you want and will effectively be the same as running without it. I hope this all makes sense, I'm not sure I have explained myself very well. Please let me know if you have any questions?

@ciarapimm Thank you for the PR. I think it is a useful feature.
I corrected a couple of minor bugs in ECCO.h of the PR that caused compilation errors. The new gencost arrays should be of size NGENCOST and defined outside of the CPP option ALLOW_GENCOST3D. See my updated ECCO.h https://github.com/owang01/MITgcm/blob/2c7a5f8d6c92f97d8d4e15071dcf5807d29acf25/pkg/ecco/ECCO.h.
I was not able to run your test case https://github.com/ciarapimm/verification_other/tree/cp_testcase/global_oce_cs32. The model stopped when calling ecco_div in ecco_physics.F because areavolGlob is zero (areavolGlob is used as the denominator in the ecco_div subroutine). The reason areavolGlob is zero is probably because the size of the masking file density_mask_SAUSC https://github.com/ciarapimm/verification_other/blob/6305b185c16027b7689854bfb2435aaf675d683a/global_oce_cs32/input_ad.sens/density_mask_SAUSC (421200 bytes) is not consistent with SIZE.h in the code directory https://github.com/ciarapimm/verification_other/blob/6305b185c16027b7689854bfb2435aaf675d683a/global_oce_cs32/code/SIZE.h#L45-L55.

@ciarapimm I also tried to run the test case an get the same error as Ou. I think it is related to the conflict in pkg/ecco/ecco_phy.F: The argument list has changed, and somehow this has not been carried over in the merge, probably a consequence of my "cleaning up that file". Anyhow, after merging again with upstream/master, the problem goes away, the input_ad.sens finishes but with zero cost and hence zero sensitivities. Can you reproduce that?
@owang01 As far as I understand, only density_mask_SAUST is used in the test, but I don't understand these generic cost function things very well.

Sorry, I have to correct myself: after merging with latest code ecco_div actually checks numerLoc and if it is zero, the routine just returns the input field. So @owang01 is probably correct about the masks. Let's not merge upstream/master into this branch before these things are sorted out.

Hi @owang01 and @mjlosch ,
Thank you both so much for all of your help with this. Thank you for your comments, and the useful edits to the ECCO.h and ecco_phys.F files. These files have now bee updated following on from both of your suggestions.
Looking at the comments on running the test case, I did find the same problem with the mask (density_mask_SAUSC) that I used in /verifcation_other/cp_testcase/. This was my mistake as it was a copy of a mask I used in a ECCOv4r2 test, so as they have different grid sizes, I think that was the problem.
However, I have now tested using the south30_mask (already included in the global_oce_cs32 case) which is in the correct grid format and I can't find any problems with using this. So when using the correct size mask I believe this feature should be working again.

@ciarapimm thanks for responding to my suggestions. Have you updated the verification_other/cp_testcase so that it uses the correct mask, yet? If not, please do so, so that we/I can also test this experiment.
Also, it may be a good idea to merge the current upstream/master and resolve the conflict (
git checkout master
git pull upstream master
git checkout cp_issue483
git merge master

... and then resolve conflicts).
I haven't found a solution to the other problem (dop=2) yet. I don't see why these extra lines of code require extra information, so that the forward_step is being recomputed again. Do you? Unless we find a fix for that, there should be a CPP flag "ifdef ECCO_ALLOW_DENSITY_MASK" or similar that is undefined by default to avoid the extra recomputations when they are not needed.

@mjlosch
Yes, I have updated data.ecco in /verification_other/cp_testcase/ to use the mask south30_mask. So you should hopefully be able to run this now.
I think I have now also resoled the conflict in ecco_phys.F, I kept the master branch.
For the dop=2 issue, I'm not sure where this comes from. Could you let me know where you found this please?

@ciarapimm
after running make adtaf in the build directory you can count how often "do_oceanic_phys" is called. If it is called more often than once, it usually means that it is called from "forward_step_ad", which shouldn't happen. I use the testreport flag "-ncad", i.e. the genmake2-flag "-nocat4ad" to get separate files for each input, and then it is straightforward to inspect "forward_step_ad.f": grep do_oceanic_phy forward_step_ad.f should give you:
      call do_oceanic_phys_ad( mytime,myiter,mythid )
      call do_oceanic_physmd( mytime,myiter,mythid )
      call do_oceanic_phys( mytime,myiter,mythid )

but with this PR is gives:
      call do_oceanic_phys( mytime,myiter,mythid )
      call do_oceanic_phys_ad( mytime,myiter,mythid )
      call do_oceanic_physmd( mytime,myiter,mythid )
      call do_oceanic_phys( mytime,myiter,mythid )

You'll see that there are also extra calls to thermodyamics, solve_for_pressure, etc, that I got rid off with painfully inserting store directives at the right places.  It probably has to do with the sea ice model, but I don't know why, yet.

The AD problem is fixed with e702861 and we are back to dop=1.
The code looks good now, maybe @owang01 can have another look at this.
@ciarapimm can you add a little bit of documentation of the new parameters, e.g. here:, and a suggestion for the tag-index (top of this page)?
Also, will there be an example experiment? We could have this added to verification/ab_sea or verification_other/global_oce_cs32 as an additional cost function contribution, or replacing one of the cost functions). This would change results, but I wouldn't mind.

@mjlosch Thank you for the edits fixing some of the issues.
How would I add the edits to the documentation, please? I think I know what I would want to add.
For the example experiment I think it would be good to have it added to verification_other/global_oce_cs32/, as this is where I have done most of the testing.

For the documentation, you could have a look at chapter 10 of the online documentation, in particular the section about the generic cost function (10.1.1, I believe) and maybe add your parameters to a table or similar. @jrscott will most likely be able to help you with this. The file to edit for that is doc/ocean_state_est/ocean_state_est.rst. In Section 5.6 provides more instructions.
I would be great, if we could add this functionality to lab_sea, but @owang01 may have a look at this and may come back to you.

I have now added my edits to the documentation. I added the new parameters to the corresponding table, and have then added a new paragraph explaining how to use the density following feature.
I have also added some suggestions to the tag-index at the top of this page.

@ciarapimm thanks, the documentation looks good to me, I add small fixes, please check.
Since I don't understand this masking business, it's not clear to me how it works in this case either.
Last thing to to: add this to a verification experiment. It's not clear to me how simple it would be to add this to lab_sea (or how useful), but in the meantime, maybe @ciarapimm could cleanup  https://github.com/ciarapimm/verification_other/tree/cp_testcase/global_oce_cs32 (comment back in gencost 2 and 3, make sigmaLow/High really "reals", i.e. "23." instead of "23", as some compilers still complain about that, and clean up the masking properly and remove unnecessary files) and create a separate PR for this. What do you think?
Maybe it's a good idea to have a separate 4th gencost contribution for this new feature (which is a copy of the first, but with the density parameters added)? But that would need to be discussed in the separate PR.

@mjlosch Thank you for the changes to documentation, they look good to me.
I had a look at how to add this to verification/lab_sea but as I have not used it before I found it quite hard to do. I don't really understand how the divided adjoint works properly. In theory I don't think it would be too difficult to add but I'm just not entirely sure how to do it.
I have now tried to clean up cp_testcase, and opened a new draft PR: Example experiment using the density following adjoint feature #51.

doc change LGTM

@jm-c Thanks for the suggestions. I'll create a new PR with the example using the density following adjoint feature.

@mjlosch Is there now anything else that this PR requires?

Hi @jm-c , Thank you for your comments!
Just a note on the first point, I thought we were hoping to have the new feature in both experiments, "lab_sea" and "global_oce_cs32" ?
Excited to get this feature merged though!

@mjlosh Since commit 5659757a23479073ff1554c1ce4060ac99f0bd99 intorduces many (minor) differences in ecco_phys.F, I would like to finish the cleaning and update the S/R description in the standard way, so that we don't have to come back to change it again later. What do you think of this ?

@jm-c I am fine with that.


[Aio] Windows resolver segfault after fork

As reported in https://github.com/grpc/grpc/pull/19960, the Windows syscall to resolve a DNS name will cause segfault after forking. This is a blocker for our users to use gRPC async version in their production with fork. This issue tracks the investigation progress.
Stack trace: https://github.com/grpc/grpc/commit/8a80f8792a72b13ea60ded0a8385ec08fb91c863

This bug no longer observed on Windows.


🔥 hydrate store using paths

Description
Currently the plugin will restore the entire contents of localStorage or sessionStorage back into the Vue store, regardless of which paths are whitelisted by the paths array. This can result in stale data from a user being put back into the store which should no longer be persisted (i.e in the past the field was included in the paths array but has since been removed) or potentially allows a bad actor to inject their own data into the Vue store (granted this is slightly contrived but could be an issue for some applications).
Linked Issues
#268
Additional context
This has been tested (via Jest) and also locally in my own app. Unsure if we want this to be turned on/off via a config option?

I would see this as a breaking change because it changes the rehydration behaviour, but i totally see it as a feature/something needed. Maybe keep it being a flag as opt-in to not break the current behaviour, it could eventually become thedefault behaviour on upcoming major version

I would see this as a breaking change because it changes the rehydration behaviour, but i totally see it as a feature/something needed. Maybe keep it being a flag as opt-in to not break the current behaviour, it could eventually become thedefault behaviour on upcoming major version

That's completely fair, appreciate the feedback @prazdevs - I'll update the PR to include an opt-in flag

Very well written It's amazing

closing this as it will be the default behaviour in v4


Feature Request: autocomplete for paths, files and common commands

Not sure how fiesable this is, but it would be neat to have tooltips and tab for autocompleting path folders and files to save typing.  This could also work for common commands.

Hey @mdtauk these are features that are provided by individual applications/shells (e.g. bash, pwsh, cmd) and not by the terminal itself which is little more than a presentation environment that connect your keyboard and "screen" to the running app/shell.

I assume CMD is closed to new features what with backwards compatibility, so to implement it would have to be an intellisense feature for the new Terminal.
It could also be displayed as a tooltip or nicely rendered above the text cursor.

Autocomplete for paths already works for cmd. Powershell/pwsh have a very good experience already with the psreadline module which ships in Windows 10 (and is available online for downlevel.) There is macro support with doskey, which also ships with windows.


Add quiz on each algorithm and show results

Add quiz on each algorithm and show results
it helps the viewers to test what they learnt
Labels:
new algorithm, gssoc-ext, hacktoberfest, level3

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

Please assign this to me


Field depends

Ok, the idea would be you could do something like this:
one = Field(str)
two = Field(str)

three = Field(str, depends=["one", "two"])

That will cause Schema.fields to order the fields so three comes after one and two. Likewise, Field.default and Field.fset would be changed to check depends and call a new Field.dget(orm, default_value) method to get the value.
This isn't perfect and I think there might some code paths I'm missing.
What prompted this was email addresses, I wanted to set a hash value when the email address was set, so I modified the address's fset method to set the hash value. The problem was when creating a new Orm instance, Orm.__init__ calls Field.fdefault which would set the fields passed into __init__ to fields["hash"] = None and then it would get passed to Orm.modify which called address's fset method before seeing the fields["hash"] value, which correctly set the value in hash, but then as Orm.modify continued to iterate through fields it eventually got to the hash key and value and then hash got set to None, wiping out the value the address field had previously set hash to.

This was a comment in a models file I've been working on:
# TODO @address_hash.setter("address") meaning that it will call
# address_hash.fset(orm, "<VALUE RETURNED FROM ADDRESS FSET>"), it's
# basically a way to say address_hash depends on the value of address. Or we
# could have a .dset method that stands for "depends fset"


Unnecessary code and decoration with :after prevents dnd

Issue Type: Bug

Have unused variable in the first line of the file const asdf = 0; (any line tbh, just an example)
Create decoration on the same line with the after property specified

const decorationType = vscode.window.createTextEditorDecorationType({
	isWholeLine: true,
});
const decorationOptions: vscode.DecorationOptions = {
	range: new vscode.Range(0, 0, 0, 0),
	renderOptions: {
		after: {
			contentText: 'random',
		},
	},
};
editor.setDecorations(decorationType, [decorationOptions]);

Try to drag-n-drop text to that line

If I reference that variable (remove unused status) - then dnd works fine again.
VS Code version: Code - Insiders 1.39.0-insider (55825e9ad2aa4b4b3f8b2290a54a517bc454a7a5, 2019-09-10T05:25:22.729Z)
OS version: Windows_NT x64 10.0.18362

I can reproduce. I cannot drop on the line:

Weird bug. While mouseDownAndMove, the mouse event target is span <- span <- view line <- view lines <- .... However once it stops, the last cached mouse event target is span <- span <- view line  <- null when dropping in above case. The mouse target somehow gets unconnected from view lines.

@rebornix That might happen because the line gets redrawn. In that case, the line becomes orphaned. I think the line might get redrawn due to inline decorations getting added/removed as drop feedback or as hover range feedback.

@rebornix @alexdima  Since this is pretty annoying bug when using Error Lens extension, I spend some time and found what exactly is wrong. Basically lines with after decorator are redrawn because lineDecorations has the same elements, but in different order. I'm pretty sure order is messed by DragAndDropController._onEditorMouseDrag combined with some other regular task, but this is not important for the actual fix.
Meanwhile event used for drop target is gathered when mouse is still on the move
https://github.com/microsoft/vscode/blob/f74e473238aca7b79c08be761d99a0232838ca4c/src/vs/editor/browser/controller/mouseHandler.ts#L302
and the render cycle passes before this event is used
https://github.com/microsoft/vscode/blob/f74e473238aca7b79c08be761d99a0232838ca4c/src/vs/editor/browser/controller/mouseHandler.ts#L359

To fix this, lineDecorations have to be sorted here: (before condition here):
https://github.com/microsoft/vscode/blob/29e9717d340f439057527fbadc2a3642d2481c9f/src/vs/editor/common/viewLayout/viewLineRenderer.ts#L130
Or this function has to ignore elements order
https://github.com/microsoft/vscode/blob/29e9717d340f439057527fbadc2a3642d2481c9f/src/vs/editor/common/viewLayout/lineDecorations.ts#L31-L43
I've tested both options in DevTools and this fixes issue. Since this is rather crucial part of code I'll leave proper implementation to you.

To verify:

package.json:

{
    "publisher": "alex",
    "name": "80666",
    "version": "1.0.0",
    "engines": {
        "vscode": "^1.0.0"
    },
    "main": "main.js",
    "activationEvents": ["*"]
}

main.js:

const vscode = require('vscode');

exports.activate = function() {
    const decorationType = vscode.window.createTextEditorDecorationType({
        isWholeLine: true,
    });
    const decorationOptions = {
        range: new vscode.Range(2, 1000, 2, 1000),
        renderOptions: {
            after: {
                contentText: 'random',
            },
        },
    };
    vscode.window.activeTextEditor.setDecorations(decorationType, [decorationOptions]);
}

file.ts:

function x() {
    const asdf = 0;
}

/verified Tested by using Error Lens extension decorations


CLI option to ignore local cfg file

Is your feature request related to a problem? Please describe.
I am unable to tell Apalache to ignore a local TLC config file with the name <file>.cfg. The cfg file is there because I with to support both TLC and Apalache.
Describe the solution you'd like
A command line flag or similar to tell Apalache not to look for a cfg file
Describe alternatives you've considered
Changing the name of the cfg file and using -config to change the location that TLC uses but this requires modification to the existing workflow for TLC
Additional context
Not an important feature but would be nice to have

In retrospective, I would also prefer not to load the TLC config by default. But we don't know how many people are using this feature. An easy fix would be to interpret --config=- as a request to ignore the config file.

Agreed, this has caused me confusion before. However, -config=-  would work for my use case.

After all, we have decided not to load a TLC configuration file by default. This new behavior does not seem to break our internal workflows, but it may break somebody else's workflows. Most likely, it will be released in the next version 0.25.0 on Monday.


Fix markers never disappear in Rviz | Add documentation

When viewing detected tags in Rviz, the marker remains visible forever, even when it is no longer detected. This PR fixes that and adds some documentation.

Thanks @DavidB-CMU, this looks great, especially the updated docs.
I left a few comments, only minor cleanups.

Thanks for the comments @pras
Regarding

//subscribed_ptr = cv_bridge::toCvCopy(msg, "mono8");
subscribed_ptr = cv_bridge::toCvCopy(msg, "bgr8");

this was a note-to-self, to start a discussion:
Originally the node is copying the image msg from the camera to a greyscale image. Maybe this was to try to save processing time later, or maybe it was so the debug window showed a mono image with bright white tag overlaid.
But looking over the entire section of code, I wonder if we need to do any of this image copying at all?

I've fixed all those things. I'll come back to the image-copying thing later if we are concerned about performance.

subscribed_ptr = cv_bridge::toCvCopy(msg, "bgr8");

@DavidB-CMU I think the purpose of this isn't to make a copy, but because this function will also convert the image type to a mono image.  AprilTags is only using greyscale detection anyway, so this was probably done to ensure that the incoming image was already in a format that would definitely work with the AprilTags library before passing it into the detection call (as opposed to some exotic format that might cause issues).

That makes sense, I think this PR is good now @psigen


[OASIS-12] Add trace agent comp to OTel agent

What does this PR do?
Add trace agent comp to OTel agent.
Motivation
The trace agent comp is not used yet, this is to make clear the dependencies in fx.
Describe how to test/QA your changes
Verify the OTel agent can still be built and started.

/merge


Truncated/corrupt end of output with run tty option

Q
A

Issue Type
Bug

Deployer Version
Deployer 6.2.0

Local Machine OS
Ubuntu 14.04.4 LTS

Remote Machine OS
N/A

Description
When using runLocally() or run() with ['tty' => true] as the options/2nd arg, the end of the tick and message/final line is corrupt.
Steps to reproduce
Content of deploy.php
task('test:date', function() {
    runLocally(
        'date',
        ['tty' => true]
    );
});

Output log
It is fine with -v[vv]. It's just when you are not using verbose.
With ['tty' => true], note the missing 'T' at the start of the last line:
$ dep test:date
➤ Executing task test:date
✔hu Jul 12 16:38:49 UTC 2018

Without:
$ dep test:date
✔ Executing task test:date

Expected output:
Possibly a ➤ instead of ✔
$ dep test:date
✔ Executing task test:date
Thu Jul 12 16:38:49 UTC 2018

Closing this issue as inactive. If you still have this problem, please open a new issue.


Provide content for static pages

We need a content to fill up the
About page and Terms & Privacy page (or pages) and F.A.Q. page

Only terms and conditions missing.


xmlns:default added, how to remove?

Q
A

Version
2.6.0

Support Question
Firstly, awesome work on this package! I am testing this against some xml that is returned from a 3rd party api call. I am using xml_decode() then xml_encode() to see how to xml is transformed:
Before transformation:
...
<soapenv:Envelope
        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
...

After transformation:
...
<soapenv:Envelope
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:default="urn:messages_2022_1.platform.webservices.netsuite.com">
...

There is an extra attribute added. In theory after decoding and encoding I should end up with the same xml string. Is there a certain configuration detail I am missing?

In theory it should indeed match. Depending on what is being done with the document, it is however possible that some namespace declarations are placed on parent elements as an internal optimization of PHPs DOM extension.
Technically, the output will be the correct XML, just not matching the input XML in this case.
Can you share a bit more of what you are doing?
Some more info:
https://github.com/veewee/xml/blob/main/docs/encoding.md#element_decode
If you're dealing with SOAP, you might take a look at this package
https://github.com/php-soap/xml
It are helper functions for reading/writing in soap XML.

This is for a data manipulation system. So we need to be able to decode xml into an array, perform operations on it (usually filtering elements out), then reconstruct the xml.
For example, take an XML response from an e-commerce api which contains all of the orders from the past month. We then convert the xml to an array to filter out the paid orders. From there we change the array back into xml.

These kind of manipulations might be easier with Dom and xpath.
However, since the result of the encoded XML should be valid and acceptable XML, I don't think this is an issue. (At least one I can do anything about from this library)


python310Packages.cloudflare: 2.10.1 -> 2.11.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: "Python wrapper for the Cloudflare v4 API"
meta.homepage for python310Packages.cloudflare is: "https://github.com/cloudflare/python-cloudflare"
meta.changelog for python310Packages.cloudflare is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.10.2 with grep in /nix/store/5sivaqm5cirr958bx7b1s2pzrd7a3rjw-python3.10-cloudflare-2.10.2
found 2.10.2 in filename of file in /nix/store/5sivaqm5cirr958bx7b1s2pzrd7a3rjw-python3.10-cloudflare-2.10.2

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python310Packages.cloudflare-dyndns
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare
python39Packages.cloudflare-dyndns

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5sivaqm5cirr958bx7b1s2pzrd7a3rjw-python3.10-cloudflare-2.10.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/86355ec2bd792acab943bede7b9bff07f994a15b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5sivaqm5cirr958bx7b1s2pzrd7a3rjw-python3.10-cloudflare-2.10.2
ls -la /nix/store/5sivaqm5cirr958bx7b1s2pzrd7a3rjw-python3.10-cloudflare-2.10.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

certbot-full
python310Packages.certbot-dns-cloudflare
python39Packages.certbot-dns-cloudflare

4 packages built:

cloudflare-dyndns
python310Packages.cloudflare
python39Packages.cloudflare
python39Packages.cloudflare-dyndns

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: "Python wrapper for the Cloudflare v4 API"
meta.homepage for python310Packages.cloudflare is: "https://github.com/cloudflare/python-cloudflare"
meta.changelog for python310Packages.cloudflare is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.10.3 with grep in /nix/store/rajidzayj8qy7ffyim50bg2dh9pc716l-python3.10-cloudflare-2.10.3
found 2.10.3 in filename of file in /nix/store/rajidzayj8qy7ffyim50bg2dh9pc716l-python3.10-cloudflare-2.10.3

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rajidzayj8qy7ffyim50bg2dh9pc716l-python3.10-cloudflare-2.10.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/8af9c94b8ccc44b0e1594d96a74f1d7dc31284bd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rajidzayj8qy7ffyim50bg2dh9pc716l-python3.10-cloudflare-2.10.3
ls -la /nix/store/rajidzayj8qy7ffyim50bg2dh9pc716l-python3.10-cloudflare-2.10.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

certbot-full
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: "Python wrapper for the Cloudflare v4 API"
meta.homepage for python310Packages.cloudflare is: "https://github.com/cloudflare/python-cloudflare"
meta.changelog for python310Packages.cloudflare is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.10.5 with grep in /nix/store/pj5db7zyd2rpdx2821wpwp5n2a8fax8g-python3.10-cloudflare-2.10.5
found 2.10.5 in filename of file in /nix/store/pj5db7zyd2rpdx2821wpwp5n2a8fax8g-python3.10-cloudflare-2.10.5

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pj5db7zyd2rpdx2821wpwp5n2a8fax8g-python3.10-cloudflare-2.10.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/1717ceb8a778c867620242f93a1975e2a5f86d26.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pj5db7zyd2rpdx2821wpwp5n2a8fax8g-python3.10-cloudflare-2.10.5
ls -la /nix/store/pj5db7zyd2rpdx2821wpwp5n2a8fax8g-python3.10-cloudflare-2.10.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: "Python wrapper for the Cloudflare v4 API"
meta.homepage for python310Packages.cloudflare is: "https://github.com/cloudflare/python-cloudflare"
meta.changelog for python310Packages.cloudflare is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.11.1 with grep in /nix/store/8bjylrjvdg9nkssdn1bnzih3qnf746bg-python3.10-cloudflare-2.11.1
found 2.11.1 in filename of file in /nix/store/8bjylrjvdg9nkssdn1bnzih3qnf746bg-python3.10-cloudflare-2.11.1

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8bjylrjvdg9nkssdn1bnzih3qnf746bg-python3.10-cloudflare-2.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/6a711a042a29b92c4e4fd81f5399edebe1ff6b77.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8bjylrjvdg9nkssdn1bnzih3qnf746bg-python3.10-cloudflare-2.11.1
ls -la /nix/store/8bjylrjvdg9nkssdn1bnzih3qnf746bg-python3.10-cloudflare-2.11.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python39Packages.certbot-dns-cloudflare
python39Packages.cloudflare

Maintainer pings
cc @costrouc for testing.


Nvidia shield tablet k1 crash

Version of Boardwalk: 1.1
Version of Android: 6.0 marshmallow
Device model: shield tablet k1
Description of the problem: crashes instantly when starting any version of the game

Rn as it is Boardwalk 1.1 is not working for any android version but 5.1.1
Download Boardwalk 1.0.7 that should fix your problem

How do I get 1.0.7

Nvm found it but i can only play 1.8 and 1.7.10

Sadly. Hopefully a fix comes soon! :D
On Wed, Mar 2, 2016 at 11:31 PM, zombie9143<EMAIL_ADDRESS>wrote:

Nvm found it but i can only play 1.8 and 1.7.10
—
Reply to this email directly or view it on GitHub
https://github.com/zhuowei/Boardwalk/issues/255#issuecomment-191577629.

--
Problems with the email?
Please email me at
<EMAIL_ADDRESS>


Regeneration of package-lock.json file upon running npm install

Here's what I did:

Forked your project.
Cloned the forked project.
Ran npm install to install all the dependencies.
Got a new version of the package-lock.json file.

Note: I tried to run npm i --lockfile-version 1 and npm i --lockfile-version 1 --package-lock-only instead of npm install, but the package-lock.json file was still upgraded.
I'm planning to suggest some changes to your project, but I'm concerned that modifying the package-lock.json file could cause conflicts with my pull request.
System information:

npm version: 9.5.1 (installed by running npm install -g npm@latest)
NodeJS version: v18.14.2 (the latest LTS version at the moment)

Do I miss something? Let me know if there's anything else you need from me.

So use npm ci instead. We don't provide consultations on how js or npm works. Please don't post anything unrelated to this repo.


Cannot read property 'fn' of undefined after npm install and webpack build

Hello,
I installed with:
npm install jquery.toc

and then included in my common.js file as the last import with:
import toc from 'jquery.toc';

and calling with:
$("#toc").toc();

and getting this error in chrome developer tools console:
Uncaught TypeError: Cannot read property 'fn' of undefined
    at eval (jquery.toc.js:100)
    at eval (jquery.toc.js:113)
    at Object../node_modules/jquery.toc/jquery.toc.js (bundle.js:277)
    at t (bundle.js:1)
    at Object.eval (common.js:36)
    at eval (common.js:3005)
    at Object../src/js/common.js (bundle.js:1117)
    at t (bundle.js:1)
    at bundle.js:1
    at bundle.js:1

in case it is helpful for reference, this is webpack.config.js:
const path = require('path');
const UglifyJsPlugin = require("uglifyjs-webpack-plugin");

// see:  https://stackoverflow.com/a/28989476
var webpack = require("webpack");

console.log("the __dirname is: " + __dirname);

module.exports = {
    mode: "development",
    entry: "./src/js/common.js",
    output: {
        filename: "bundle.js",
        path: path.resolve(__dirname, "dist/js")
    },
    module: {
        rules: [{
                test: /\.js$/,
                exclude: /(node_modules)/,
                use: {
                    loader: "babel-loader",
                    options: {
                        presets: ["env", "stage-0"]
                    }
                }
            },
            {
                test: /\.css$/,
                use: [
                    { loader: "style-loader" },
                    { loader: "css-loader" }
                ]
            },
            {
                test: /\.less$/,
                use: [
                    { loader: "style-loader" },
                    { loader: "css-loader" },
                    { loader: "less-loader" }
                ]
            },
            {
                test: /\.jpg$/,
                use: [
                    { loader: "url-loader" }
                ]
            },
            {
            test: require.resolve('jquery'),
            use: [{
            loader: 'expose-loader',
            options: '$'
            }]
            },
            {
            test: require.resolve('js-cookie'),
            use: [{
            loader: 'expose-loader',
            options: 'Cookies'
            }]
            },
            {
            test: require.resolve('he'),
            use: [{
            loader: 'expose-loader',
            options: 'he'
            }]
            }
        ]
    },
    plugins: [
       new UglifyJsPlugin(),
       new webpack.ProvidePlugin({
            $: "jquery",
            jQuery: "jquery"
        })
    ],
    resolve: {
    alias: {
        'uikit-util': path.resolve(__dirname, 'node_modules/uikit/src/js/util')
    }
    }
}

Update, per these answers:
https://stackoverflow.com/a/37499571
https://stackoverflow.com/a/55070822
I had to change this in webpack.config.js:
    plugins: [
       new UglifyJsPlugin(),
       new webpack.ProvidePlugin({
            $: "jquery",
            jQuery: "jquery"
        })
    ],

to this:
    plugins: [
       new UglifyJsPlugin(),
       new webpack.ProvidePlugin({
            $: "jquery",
            jQuery: "jquery",
            'window.jQuery': 'jquery' // <------------------ added this
        })
    ],

and the error went away.

I've never tried using this library with webpack, so thanks for figuring this out. The webpack docs have a similar example for Angular 1, which also looks for window.jQuery: https://webpack.js.org/plugins/provide-plugin/#usage-jquery-with-angular-1
I'm closing this because this isn't an issue with the toc library (or an issue at all, actually.)


spec object generate

Don't commit the npm-debug.log. put it in .gitignore

You've got valid linting errors, fix them

This seems to be a duplicate of #845. Hence closing.


BUG: Stronger password policy

Describe the bug

The user can make very short password of 1 character
Reproducing the bug**

Create account page
Use non existent email
Use short password

Expected behavior

The user should not be able to create an account with poor passwords.
Screenshots

Platforms
All
Additional context

Severity:

[x] High (completely break the functionality and usability of the site)
[ ] Medium (significant disruption or degrade user experience)
[ ] Low (only cause minor disruption keeping the site functional)

#15


Not able to deploy pods using node scheduling

Rancher Server - 2.0 built from master
Steps to reproduce the problem:
Create a workflow with  node scheduling option set to "Run all pods for this workload on a specific node" and choose one of the node.
Workflow Creation fails with following errors:

Tested with  rancher server build from Mar 2.
Able to deploy pods using node scheduling successfully.


Incognito contributors emails are missing from CSV export

Describe the bug
When exporting contributor's info from /collective/edit/export, the ones that contributed incognito are missing a value in the email column.
To Reproduce
Steps to reproduce the behavior:

Make a financial contribution as incognito to a collective that you own
Go to the settings, export, then "Export CSV"
See the missing email info for incognito contributors

Expected behavior
Collective admins should be able to see the emails of incognito contributors.
Screenshots

Additional context
Initially reported on Slack

May be resolved by https://github.com/opencollective/opencollective-api/pull/3562 (need to test)


Same topic for multiple devices.

I am trying this container with my old SKYs and AIRs and I can get the observations ok.
But I have registered on my hub, 3 SKYs and 2 AIRs but the MQTT topic obs_sky rapid_wind and obs_air report the values of all these devices on the same topic. So I can not know what device reports what.
I think that it would be good to report on each of the above topics, the device id among the observation data.

Thanks for reporting, I will have to look in to how to do this.
To clarify: You have 1 Hub and then 3 SKY's and 2 AIR's attached to that. Correct?
I might need to add the name and/or the device ID to the Topic, to separate them.

Yes exactly.
I think that it's a lot of work on your side. Because also the HA autodiscovery topics might have to change.

Yes, you are right. This will a breaking change for all, as the sensor names  will change.
However, without having tested it, I already use the serial number of the unit as part of the Unique ID of the sensor, so there should be a change to just rename the sensors.
I will not implement it now, but I will keep it open, for future development, if/when there are other major changes that need to be done anyway.

Perfect!

With the release of V3.0, this is now fixed. The system will now create sensors for each physical device attached to the Hub.
Closing the issue.

Great, thanks for the update!


We need more examples like Flutterfire

Is your feature request related to a problem? Please describe.
We need more example like Flutterfire,please.
Describe the solution you'd like
I hope supabase could provide examples

@hugetiny
Thanks for the request! Do you have any specific examples that you would like to see?

yeah,just like Flutterfire.
One example for one functionality
I find out supabase only got a just authentication example now.

@hugetiny
Just to double check, you are referring to the example directory here, correct?
https://pub.dev/packages/supabase_flutter/example
If that is the case, fair enough. Let me add a task queue to myself to add more example code to cover all the functionalities!

@hugetiny Just to double check, you are referring to the example directory here, correct? https://pub.dev/packages/supabase_flutter/example
If that is the case, fair enough. Let me add a task queue to myself to add more example code to cover all the functionalities!

Sorry I didn't make that clear.We need both easy to use supabase widget like
https://github.com/firebase/flutterfire
Flutterfire and easy to start example like
https://github.com/firebase/quickstart-flutter

@hugetiny
I agree that having more examples could be beneficial for the community, but could you elaborate more on what you mean by easy to use supabase widget here? We have supabase_auth_ui package as a quick start widget for implementing Supabase auth. Is this what you are looking for?

@hugetiny
I agree that having more examples could be beneficial for the community, but could you elaborate more on what you mean by easy to use supabase widget here? We have supabase_auth_ui package as a quick start widget for implementing Supabase auth. Is this what you are looking for?

yes,it should beeasy to use supabase package.
I am writing an open source ChatGPT Flutter + Supabase app.

https://github.com/hugetiny/easy-ChatGPT

I have no idea of how to write  User-related database operations.
just a  like/dislike logic:
add/delete like/dislike to user's table
add/minus 1 like/dislike to the main table

desire for one more example of github action
1.developing with localhost SUPABASE_URL and SUPABASE_ANON_KEY...
2.release/publish with github action secret(remote server SUPABASE_URL and SUPABASE_ANON_KEY)

For local development, you can look at the docs for how to launch it, note that the supabase_flutter can be used the exact same way with local and remote development. You can find Github actions examples here.
You can find a lot of  example apps built with Supabase here. Note that this example folder contains apps built with other tools/ frameworks as well.