Missing /nbextensions/widgets/notebook/js/extension.js

Describe the bug
#!javascript results in 404 GET /nbextensions/widgets/notebook/js/extension.js
Please complete the following:
Which version of .NET Interactive are you using?
Version: 1.0.136005+eb038ecb4877981ad1b17a7f6830868c0041aa11
Build date: 2020-07-10T18:53:44.0000000Z

OS

[ ] Windows 10
[ ] macOS
[X ] Linux (Please specify distro) Ubuntu 18.04 LTS
[ ] iOS
[ ] Android

Browser

[X] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[X ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[ ] Visual Studio Code
[ ] Other (please specify)

You are using Jupyter notebook.

The version of the notebook server is: 5.7.8
The server is running on this version of Python:
Python 3.7.3 | packaged by conda-forge | (default, Jul  1 2019, 21:52:21)
[GCC 7.3.0]

Screenshots
If applicable, add screenshots to help explain your problem.

I was able to execute it and use both promsie and async approach

The only difference I have is the js code
#!js

(async () => {
    let output = document.getElementById("output");
    output.innerHTML = await interactive.pwsh.getVariable("hi");
})();

It works for @jonsequitur too. But not for me.
Only reason I can see is the error in the console
[W 21:25:47.058 NotebookApp] 404 GET /notebooks/work/undefinedresources/dotnet-interactive.js (<IP_ADDRESS>): No such file or directory: work/undefinedresources/dotnet-interactive.js
[W 21:25:47.059 NotebookApp] 404 GET /notebooks/work/undefinedresources/dotnet-interactive.js (<IP_ADDRESS>) 2.66ms referer=http://localhost:8888/notebooks/work/Untitled2.ipynb

one last thing to check is that I am on jupyter 6.03 and the error you are seeing is relate to require.js configuration. Is it possible for you to upgrade or that newer version

I've updated to Jupyter 6.0.3

Still no joy.

Same error in the console

Update.
I have it working on Windows. Here is my Windows Jupyter Env

However still no joy using Docker with a Linux Ubuntu 18.04 container. I've gone through and updated everything Jupyter related. Here is that Jupyter Env

Hi, do you have the port mapping working? For that to work .NET Interactive needs to be reachable directly.
Loot at the documentation here to see command line examples

Yes I have Port Mapping working. I've also tried reinstalling the nbextensions.

I was able to reproduce the bug

@darrenjrobinson we have just made a release and I also updated the docker file, your repro steps now seem to work correctly inside a docker container. Could you please test if your scenario is now addressed?

Fantastic, thank you @colombod & @jonsequitur
Success locally with JupyterLab using your sample Dockerfile

However failing locally using Jupyter Notebook with my updated image for Interactive Build 1.0.140402

Different error in the console

Yes, I have incoming ports specified. Same as for what successfully works for Jupyter Lab.

does it work if you retry?

What do you see in chrome dev tools when you execute the cell?
This is a sequence of request that completes with success the kernel's http endpoint discovery

Does it work if you split the powershell code submission from the html and js?

No joy their either.

Maybe missing a dependency.

Some extra tracing showed I needed to update with the following and extend in the inbound ports to start at 1000.
pip install ipywidgets
jupyter nbextension enable --py widgetsnbextension
pip install jupyter-require

not sure, We have no installation of jupyter-require and the only other difference is that we target python 3 explicitly in our docker file.
can you show the docker file you are using ?

AWESOME NEWS.
I took the reference Dockerfile from the updated examples.

Success.
Thanks for all your help @colombod
This particular feature is extremely powerful. 🐱🏍

Thank you for your feedback, glad you have your scenario working.


Published/azure/azure rest api specs pr/dev orbital microsoft.orbital 2021 04 04 preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[x] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This PR has already received breaking change approval here: https://github.com/Azure/azure-rest-api-specs-pr/pull/5419

@thisisdevanshu
For some reason, your commits are showing in this PR even though your commits were already merged last week:
https://github.com/Azure/azure-rest-api-specs/pull/16781

/azp run


Refactor MemoPlaintext to be a fixed-length String

This touches enough of the codebase to deserve its own tracking issue: MemoPlaintext is used in several places but we would be better served by a fixed-length string, though swapping it out may take some thinking about how best to refactor the functions on the implementation.

we would be better served by a fixed-length string

Can someone elaborate on the utility of switching to a string and ditching the struct entirely? I can see that a string would be more pleasant to work with than a vec, but having the methods bundled to the struct for encrypt/decrypt actions strikes me as a pleasant convenience. If anything, I'm biased toward leveraging the impl further: we currently validate that the memo text is less than MEMO_LEN_BYTES in several places, but it might be safer to move that validation logic into a constructor, so that future maintainers don't overlook it when using memos elsewhere.

The intent is to make sure the memo is UTF-8 encoded, so really what we are looking for is a fixed-length UTF-8 string

I can see that a string would be more pleasant to work with than a vec, but having the methods bundled to the struct for encrypt/decrypt actions strikes me as a pleasant convenience.

One point here is that, ideally, users of these APIs won't be calling encrypt/decrypt directly: when creating a transaction, they would construct a TransactionPlan with the Planner API, then call build (which would do encryption internally), and when viewing a transaction, they'd use a TransactionPerspective to create a TransactionView, which provides an already decrypted and "interpreted" view of the transaction.
In either of those cases, an API user will just be operating on the plaintext of the transaction, and at that point, having a String is much more ergonomic.
We also don't necessarily need or want the string to be fixed-length.  For instance, if I create a transaction with the memo field "for pizza", my 9-byte memo will be padded with 0s to get a fixed-length memo ciphertext. But when I look at the transaction later, I don't really want to see "for pizza\0\0\0...(503 zeros)...\0", I just want to see "for pizza".  Or, if I'm reviewing a TransactionPlan before signing, seeing the zero-padded memo plaintext isn't particularly helpful either.
So I think it's simplest just to treat the memo plaintext as an ordinary String.
Now we have two decisions to make:

How do we handle the conversion from variable-length Strings to 512-byte plaintexts when building a transaction?
How do we handle the conversion from 512-byte plaintexts to UTF-8 Strings when decrypting a memo?

On the first question, I think a reasonable answer is to pad an undersized input with 0 bytes, so we have a canonical padding.  For oversized inputs, we could either error or truncate.  Erroring is probably safer, and TransactionPlan::build is already fallible. We'll also want to change the Planner API so that the Planner::memo method is fallible.
The second question relates to @zbuc's point:
It is unsafe to assume the string is UTF-8 when decoding, and the error must be handled gracefully to prevent crashing the view service with malicious transactions.
Not only is it difficult to prove, but also, we don't prove anything about the note or memo plaintexts at all.  The ZK validity checks are only applied to the note commitments, and the NotePayload containing the symmetrically encrypted plaintext is treated as an in-band messaging system between the sender and the receiver. The assumption is that if the sender constructs a malformed plaintext, the receiver simply doesn't agree that a payment happened.

The PR at https://github.com/penumbra-zone/penumbra/pull/1548 is almost ready, and functionally seems sound. I'm going to keep this issue open post-merge to ensure that adequate testing, such as via proptest, is added, possibly after the next testnet.


Switch to GHC 8.0 when it is out.

Currently we use ghc 7.8 for the compilation of slices. There is always quite a lot of fixing required when updating the GHC version used. Using GHC 8.0 should fix #82 and #106 so it is worth it.

Done. The biggest problem was to get the builtin environment right, see utilities-src/create_builtin_environment.hs
Not all modules are exposed in base and integer-gmp. But some entities are defined in non-exposed modules. When we try to import them (in our generated code) from there we get an error.
The workaround is to rewrite the builtin environment as if those entities originated from modules that are exposed.


Moderation Interface

Under features it says:

Review and approve or delete comments through the moderation interface

I don't see any documentation on how to use this moderation interface. Can you provide some?

He @ericuldall! The moderation interface is a part of a rewrite I've been doing for the past few months. The current default branch (v0) will be retired soon. You can follow the development here. We're #movingtogitlab too :)
However, here's a sneak peek into what it looks like:

^ the blue background comments are the new ones; you can approve them or delete them

Is there a docker image built with the latest dev version I can try?

I'm getting the following error (running in kubernetes):
[ERROR] router.go:29 serveRoutes(): cannot start server: listen tcp: address <IP_ADDRESS>:tcp://<IP_ADDRESS>:80: too many colons in address

Sample of my deployment:
---
  apiVersion: extensions/v1beta1
  kind: Deployment
  metadata:
    name: "commento-test"
    namespace: "stage"
  spec:
    progressDeadlineSeconds: 180
    replicas: 1
    strategy:
      rollingUpdate:
        maxUnavailable: 30%
        maxSurge: 50%
    template:
      metadata:
        labels:
          name: "commento"
      spec:
        containers:
          -
            name: "commento"
            image: "registry.gitlab.com/commento/commento-ce"
            env:
              - name: COMMENTO_ORIGIN
                value: http://[REDACTED]
              - name: COMMENTO_POSTGRES
                value: postgres://postgres:postgres@localhost:5432/commento?sslmode=disable
            ports:
              -
                containerPort: 8080
          -
            name: "postgres"
            image: "postgres"
            env:
              - name: POSTGRES_DB
                value: commento
              - name: POSTGRES_USER
                value: postgres
              - name: POSTGRES_PASSWORD
                value: postgres
            ports:
              -
                containerPort: 5432

Very weird. Can you try setting the COMMENTO_PORT env variable to 8080 manually and try again? I have no experience with kubernetes fwiw, but I think I understand the config mostly.

@ericuldall btw, do you mind popping into #commento on freenode IRC so that I can help better? Github is really non-intutive for something like this haha.

Okay, the server is running now. But I'm only seeing the following after embed:

Just to confirm, are you using the latest (from 2 hours ago) image?


GCC and -Werror=alloc-size-larger-than error

Building the latest (c4cfc35) with GCC 10.2.1-6 on Debian Bullseye fails with multiples of this error:
In member function ‘allocate’,
    inlined from ‘meshopt_optimizeOverdraw’ at /home/carl/Work/Native/Obj2Buf/src/overdrawoptimizer.cpp:294:67,
    inlined from ‘main’ at /home/carl/Work/Native/Obj2Buf/src/main.cpp:195:29:
/home/carl/Work/Native/Obj2Buf/inc/meshoptimizer.h:739:48: error: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Werror=alloc-size-larger-than=]
  739 |   T* result = static_cast<T*>(Storage::allocate(size > size_t(-1) / sizeof(T) ? size_t(-1) : size * sizeof(T)));

This is on a Power9 CPU, and size_t is 64-bit as expected.
The fix was to use PTRDIFF_MAX as the upper limit (which matches the signed<PHONE_NUMBER>854775807 maximum object size). Whilst it seems extreme to be limiting to half the size of size_t, even on a 32-bit system this is surely larger that any workable buffer size?
Thoughts? Besides no-one has a Power9 and real men have Power10 these days...

This warning is a little unfortunate. The goal of this code is to pass the size that can't possibly be allocated on any system to convert a numeric overflow during multiplication into an allocation error (and do this in a way that isn't relying on the specifics of the error handling during allocation failure, eg without actually spelling out throw std::bad_alloc in case the allocation handler uses a different strategy).
PTRDIFF_MAX is technically possible to allocate... I doubt any system actually allows this, but still. Let me look into this a little bit since I'm wondering if there's some other way to silence this warning.

Testing your exact command line doesn't produce the error. A little further testing: GCC 10 and 11 error as above, GCC 12 doesn't but creates a new related error:
/home/carl/Work/Native/Obj2Buf/src/overdrawoptimizer.cpp:288:23: error: ‘memcpy’ specified bound between<PHONE_NUMBER>854775808 and<PHONE_NUMBER>3709551612 exceeds maximum object size<PHONE_NUMBER>854775807 [-Werror=stringop-overflow=]
  288 |                 memcpy(indices_copy, indices, index_count * sizeof(unsigned int));
      |

Passing index_count as an unsigned int (or simply casting) keeps the compiler happy.
Clang 11 on the same system is fine.
I will investigate further.

Does the warning for memcpy also get traced to main.cpp and mention inlined functions? I'm wondering if the root of the issue is the calling program, where for example the index/vertex count are signed and GCC thinks they might be negative.

Yes, the error goes back to the inline from here:
In function ‘meshopt_optimizeOverdraw’,
    inlined from ‘process’ at /home/carl/Work/Native/Obj2Buf/src/main.cpp:195:29,
    inlined from ‘main’ at /home/carl/Work/Native/Obj2Buf/src/main.cpp:219:10:
/home/carl/Work/Native/Obj2Buf/src/overdrawoptimizer.cpp:288:23: error: ‘memcpy’ specified size between<PHONE_NUMBER>854775808 and<PHONE_NUMBER>3709551612 exceeds maximum object size<PHONE_NUMBER>854775807 [-Werror=stringop-overflow=]
  288 |                 memcpy(indices_copy, indices, index_count * sizeof(unsigned int));
      |                       ^

The calling line being:
meshopt_optimizeOverdraw(mesh.index.data(), mesh.index.data(), mesh.index.size(), mesh.verts[0].posn, mesh.verts.size(), sizeof(ObjVertex), 1.01f);

And mesh.index being a std::vector<unsigned>.
Now, if I limit how big the index buffer can get, either by only passing in a uint32_t or by limiting the size otherwise, then it works fine.
index.resize(std::max(numIndices, (size_t)UINT32_MAX));

I'll need to look at GCC on Intel to compare whether this is a Power9 particularity or not. The project will be public on GitHub shortly (it's not very interesting, it's just a tool I made to dump out buffers for quick demos), but this part differs little from what your demo/main.cpp is doing, and if I change your code to mirror mine it oddly doesn't fail (as in: the vector resize is done in a single function, which is about the only difference).
I'll come back to this next week with more data when I have more time.

Closing this. It's not reproducible standalone in meshopt, and looks to be over eager static analysis which isn't triggered in newer GCC versions.


docs(tutorial/4 - Directory and File Organization): describe your cha…

…nge...
3 styleguides, sorted alphabetically.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

I would keep john papa's guide as first guide tbh.

I signed it!
On Thu, Feb 16, 2017 at 9:41 AM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/pull/15713#issuecomment-280268219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQrE3Qpc_-1tra-nlvjudIE2Bb5EdD3ks5rdAvDgaJpZM4MCufV
.

Hi Nils. Thanks for your contribution. Unfortunately, recommending multiple guides is confusing for users. I worked with John Papa on his guide and that's the only one the Angular team has been involved with, so that's why we are recommending that one.
As I mentioned, we don't want to recommend multiple style guides and I don't see a reason to change the style guide for AngularJS at this point unless we get a strong signal from the community that a change is needed, which we are not getting.
thanks again.


Use the new mirage-runtime Hooks module to simplify the scheduler.

The main loop is now much simpler, and it calls Lwt_engine directly.
See https://github.com/mirage/mirage/pull/1010

I fixed that patch to keep the sigpipe/Lwt.catch and use the updated hook API.

thanks, merged as part of #15


Renew automatically in info tab URL no longer includes token

Describe the bug
Previous versions included the session token needed to automatically renew the developer mode session within a provided URL box when the "Renew Automatically" modal was opened. The most recent versions (1.7.4, maybe back to 1.7.1) no longer include the sessiontoken at the end of the URL.
To Reproduce
For awareness, I was starting with devices that had already been configured on previous releases.

Choose a device in the upper-left dropdown
Select Info on the menu on the left
Select Renew Automatically within Dev Mode
In modal that opens, see URL is missing session token.

Expected behavior
The URL provided under Renew Automatically -> URL should include the session token for the user to copy.
Screenshots

Additional context

OS: Windows 11

Thanks for the info. It has been fixed in v1.7.9.


mold linker symbol mismatch warning

Hi,
When linking volk using mold linker, I get a ton of warnings (one for each definition) like:
mold: warning: symbol type mismatch: vkGetDeviceQueue2
>>> defined in Submodules/volk/libvolk.a(volk.c.o) as STT_OBJECT
>>> defined in /home/moka/vulkan/<IP_ADDRESS>/x86_64/lib/libvulkan.so as STT_FUNC

I am on arch linux using mold linker 2.0. The warning seems to be added in the 2.0 version of the linker so I am not entirely sure if this issue is with mold or volk at this point.
I am linking volk with cmake via the volk target. Mold is enabled like this: cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_CXX_FLAGS="-fuse-ld=mold" .. . For what it's worth, the same happens if I compile volk into my own c/cpp file.
Any ideas welcome,
Thanks!

You should not be linking libvulkan when using volk.

I am not, at least not on purpose. Could it be that SDL pulls in vulkan somehow?

I put a minimal example to reproduce the issue over here: https://github.com/mokafolio/Volkmold. Build using:
mkdir build
cd build
cmake -GNinja -DCMAKE_CXX_FLAGS="-fuse-ld=mold" ..
ninja

Gonna test this in other platforms than linux in a bit to see if it is a cross platform issue.

Works fine for me:
~/Volkmold/build $ cmake -GNinja -DCMAKE_CXX_FLAGS="-fuse-ld=mold" ..
-- The CXX compiler identification is GNU 12.3.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
 Vulkan as target
-- Configuring done (0.1s)
-- Generating done (0.0s)
-- Build files have been written to: /home/zeux/Volkmold/build
~/Volkmold/build $ ninja
(0.145) [2/2] Linking CXX executable Volkmold

However, I do see libvulkan.so appended in the command line. This should not happen. I think it's happening because of declared dependency on Vulkan::Vulkan via target_link_libraries here:
    if(TARGET volk)
      target_link_libraries(volk PUBLIC Vulkan::Vulkan)
    endif()
    target_link_libraries(volk_headers INTERFACE Vulkan::Vulkan)

These are wrong, but I'd need to go back in CMake history to see why they were added / how to best fix it, as we need an include dependency from Vulkan::Vulkan but not the libraries.

Ok yeah this is due to a dependency on Vulkan::Vulkan, which should not be here. What needs to happen is either that we only depend on Vulkan::Headers, or that we grab the include path from Vulkan::Vulkan and manually add it to volk. I have a patch for the latter that seems to work but I need to look at whether we can just rely on Vulkan::Headers as it's simpler.

Posted a patch that seems to be the most straightforward way to handle this atm. Vulkan::Headers is new as of CMake 3.21, so for now we need to rely on the variables set by FindVulkan.cmake as I understand it.

I just tested your branch and can confirm that it fixes the warnings on mold 2.0. Thanks for the blazingly fast turnaround! Feel free to close the issue once you merge the PR!


build: allow jumping to base class of api class

References #14122

Caretaker note. if you merge this PR, please consider merging https://github.com/angular/material.angular.io/pull/558


Bug since 2022.3.1: couldn't load project

The plugin doesn't show "Load Paddle project" popup notification in PyCharm since 2022.3.1

Fixed in release 0.4.10


onstatechange only works on the first state change

onstatechange only works on the first state change. All subsequent changes to the slider are ignored. Maybe I am doing something wrong. Below is the code I am trying to use. Thanks in advanced for any help with this.
$('.single-slider').jRange({
from: 1,
to: 28,
step: 1,
format: '%s',
width: 375,
showLabels: false,
showScale: false,
onstatechange: function(){
   		if (val = 1) {

		}
		if (val = 2) {

		.....
		}
		if (val = 3) {

		.....
		}
		if (val = 4) {

		.....
		}
	},
});

I don't think it is the case, please see the this http://jsfiddle.net/nitinh/dj8r4q2k/
Looks like you have typo in onstatechange function, there is a parameter missing.

 Thank you for the help. I got it working. I'm still in school learning this stuff. This is an awesome program.


TypeError: described_as() takes at least 2 arguments (0 given)

Don't know what to say. Here is some info:
Test session starts (platform: linux2, Python 2.7.8, pytest 2.8.2, pytest-sugar 0.5.1)
django settings: project.settings (from ini file)
rootdir: /home/l/projects/contextads, inifile: pytest.ini
plugins: describe-0.10.2, sugar-0.5.1, django-2.9.1

../../.virtualenvs/lc/local/lib/python2.7/site-packages/pytest_describe/plugin.py:76: in _getobj
    return self._memoizedcall('_obj', self._importtestmodule)
../../.virtualenvs/lc/local/lib/python2.7/site-packages/_pytest/main.py:317: in _memoizedcall
    res = function()
../../.virtualenvs/lc/local/lib/python2.7/site-packages/pytest_describe/plugin.py:84: in _importtestmodule
    module = make_module_from_function(self.funcobj)
../../.virtualenvs/lc/local/lib/python2.7/site-packages/pytest_describe/plugin.py:29: in make_module_from_function
    module.__dict__.update(trace_function(funcobj))
../../.virtualenvs/lc/local/lib/python2.7/site-packages/pytest_describe/plugin.py:19: in trace_function
    funcobj(*args, **kwargs)
E   TypeError: described_as() takes at least 2 arguments (0 given)

What does your test code look like? It seems like you have a test case named described_as, and the plugin treats it as a new "describe" block. As a workaround, you can try to rename the function to something that doesn't start with 'describe'
There are also some configuration options that might be useful, in case you want to keep the name, but avoid this problem.

E.g. if you set the config option describe_prefixes to ('describe_',) only functions having the underscore will be treated as new blocks.

Oh, thanks, I thought about similar issue, but my code has no similar functions.
But... I use pyhancrest package. I discovered that it has described_as matcher. And my code imports all matchers by * -_-
https://pyhamcrest.readthedocs.org/en/release-1.8/decorator_matchers/#module-hamcrest.core.core.described_as
I'm thinking about the way to detect is it your function or not...

I'm going to close this now, since it's not an issue with the plugin. The plugin just does what it's advertised to do; it takes all functions in your module, that starts with "describe" and calls them a certain way.
For the issue that you're having, there are several things you can do:

Don't use from X import *, use from X import stuff, you, need instead
Don't use from X import, just use import X, and change your code to use X.stuff instead of stuff
Keep your code as it it, but define a __all__ attribute in your module, with a list of functions that you want to be seen by pytest (I haven't actually tried this, but I suppose it should work)

Yea, I know that, fixed it already in my codebase.
Thing, which bothers me is that you blindly took functions by name. This is why I think it could be issue with this plugin. But yea, I'll be fine with that.


Legend hidden when inserted as a child component.

Hi team,

Is it possible to always show the tooltip without a mouseover?
When the same doughnut chart is inserted as a child component, the legends are not visible anymore. Is it a bug?

Steps to Reproduce:

copy the DOUGHNUT chart code sample from LWCC samples.
Paste the same into a component and view the same from a community.
Legends are visible.
Create another component and put the above component as a child cmp.
Legends are no longer visible

Hi @hpmohan , thanks for using the library !
I'm trying to reproduce the error from my side but it seems working fine. If I understood well, your problem could be reproduced with this configuration:
Parent cmp
<template>

Parent Component

		<c-child-chart></c-child-chart>

</template>

Child cmp
<template>

Child component

		<c-chart type="doughnut" responsive="true">
			<c-dataset labels='["OK", "WARNING", "CRITICAL", "UNKNOWN"]'>
				<c-data label="# of Tomatoes" detail="[12, 19, 3, 5]" backgroundcolor='[
					"rgba(14, 110, 206, 1)",
					"rgba(45, 156, 237, 1)",
					"rgba(104, 206, 238, 1)",
					"rgba(150, 242, 238, 1)"]'>
				</c-data>
			</c-dataset>
			<c-title text="Doughnut Chart"></c-title>
			<c-legend position="left"></c-legend>
			<c-arc-configuration bordercolor="rgba(7, 62, 146, 0.7)"></c-arc-configuration>
		</c-chart>

</template>

When I place the parent component in a community page, the chart is displayed with the legend:

Can you please try the code above and let us know please?
Just to double-check: are you using a LWR site?


Setup for local test

Add docker compose and instruction to run a local aggregator for testing purpose

The tests are failing at the moment. This PR is good to merge.


client not foundtoken

Error login: Client not foundtoken

Indeed, and deleting the ini file and updating the app does not change anything.


Error: cannot change profile for the next exec call: No such file or directory

Host is Ubuntu 20.04
I have installed microk8s 1.19 in an lxc container with Ubuntu 20.04 -- worked ok
I have reconfigured the host interface as a bridge so that container can be reached from the local net - worked ok.
I reconfigured the host interface and removed the bridge. That did not work with the same profile as expected.
Then I reconfigured the host interface as a bridge again.
Now the microk8s container does not work anymore:
lxc exec container -- bash then:
root@homekube:~# microk8s.inspect
cannot change profile for the next exec call: No such file or directory

Not sure whether this is a problem with netplan | lxc | microk8s ?
Restoring a formerly saved snapshot of the container does not solve the problem.
Host config

cat /etc/netplan/10-bridge-config-for-lxd-homekube.yaml

network:
    version: 2
    renderer: networkd
    ethernets:
        enp0s10:
            dhcp4: yes
    bridges:
      br0:
        dhcp4: yes
        interfaces: [enp0s10]

ip a s

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 00:26:2d:2d:2f:2f brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:26:2d:2d:2f:2f brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global dynamic br0
       valid_lft 84961sec preferred_lft 84961sec
    inet6 fe80::48af:ecff:fea3:c1ee/64 scope link
       valid_lft forever preferred_lft forever
5: veth8dd99ab0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether ea:c0:ae:f8:a3:2f brd ff:ff:ff:ff:ff:ff link-netnsid 0

lxc list

+----------+---------+---------------------+------+-----------+-----------+
|   NAME   |  STATE  |        IPV4         | IPV6 |   TYPE    | SNAPSHOTS |
+----------+---------+---------------------+------+-----------+-----------+
| homekube | RUNNING | <IP_ADDRESS> (eth0) |      | CONTAINER | 1         |
+----------+---------+---------------------+------+-----------+-----------+
| ubuntu1  | STOPPED |                     |      | CONTAINER | 0         |
+----------+---------+---------------------+------+-----------+-----------+
| ubuntu2  | STOPPED |                     |      | CONTAINER | 0         |
+----------+---------+---------------------+------+-----------+-----------+

lxc profile show microk8s

config:
  boot.autostart: "true"
  linux.kernel_modules: ip_vs,ip_vs_rr,ip_vs_wrr,ip_vs_sh,ip_tables,ip6_tables,netlink_diag,nf_nat,overlay,br_netfilter
  raw.lxc: |
    lxc.apparmor.profile=unconfined
    lxc.mount.auto=proc:rw sys:rw cgroup:rw
    lxc.cgroup.devices.allow=a
    lxc.cap.drop=
  security.nesting: "true"
  security.privileged: "true"
description: ""
devices:
  aadisable:
    path: /sys/module/nf_conntrack/parameters/hashsize
    source: /sys/module/nf_conntrack/parameters/hashsize
    type: disk
  aadisable1:
    path: /sys/module/apparmor/parameters/enabled
    source: /dev/null
    type: disk
  aadisable2:
    path: /dev/kmsg
    source: /dev/kmsg
    type: disk
  eth0:
    name: eth0
    nictype: bridged
    parent: br0
    type: nic
  root:
    path: /
    pool: default
    type: disk
name: microk8s
used_by:
- /1.0/instances/homekube

It seems that this is a problem to somehow missing or incomplete apparmor profile.
https://blog.sleeplessbeastie.eu/2020/07/20/how-to-deal-with-missing-apparmor-profiles-for-microk8s-on-lxd/
This seems to solve this issue however i wonder what could be the root cause why that happened.
It works for me but i do wonder if this is the recommended solution to the problem.


Create MOM-2024-01-23.md

What type of PR is this?

documentation

What this PR does / why we need it:

MoM of 2024/01/23 meeting

Sorry for the delay.
Which issue(s) this PR fixes:

NA

Special notes for reviewers:
Changelog input
Additional documentation

hi @ToshiWakayama-KDDI , I don't see some open points mentioned in the previous meeting 2024-01-09 (Previously mentioned in  Next Steps)

AgeVerification API: we received a request from Olu Omobitan (GSMA) to have the API status because in Drop3 (end of March). I've created an issue with few input, could you create a PR for this API ?
scoring attribute value in Match Response.

Thanks a lot
BR
Gilles

Hi @GillesInnov35,
Thank you for your comments.

AgeVerification API: we received a request from Olu Omobitan (GSMA) to have the API status because in Drop3 (end of March). I've created an issue with few input, could you create a PR for this API ?

Sure.  I will create a PR for this API.  But do you have any initial YAML proposal for the basis of discussion?
BR
Toshi

hi @ToshiWakayama-KDDI , yes I've a yaml proposal to initiate the discussion. Thanks BR Gilles

Thanks, @GillesInnov35 .  So, presumably I shall creat a PR and then you will submit your yaml proposal.
BR.
Toshi

great, thanks a lot @ToshiWakayama-KDDI


IPL-Visualizations

IPL Facts & Visualizations Added

@all-contributors please add @Siddhant-K-code for code

@all-contributors please add @Siddhant-K-code  for code

pls add hacktoberfest-accepted badge, so my PR can eligible for Hacktoberfest, accr. to new guidelines


Client() with srv_domain queries localhost

I created Client with srv_domain:
client = etcd.Client(srv_domain='twindb.com')

However client.machines requests http://<IP_ADDRESS>:4001/v2/machines.
DNS is configured correctly:
$ dig +noall +answer SRV _etcd-client._tcp.twindb.com
_etcd-client._tcp.twindb.com. 300 IN    SRV     0 0 2379 etcd-1e1650524ba511e68a9b12cb523caae1.twindb.com.
_etcd-client._tcp.twindb.com. 300 IN    SRV     0 0 2379 etcd-6794c99e4ba411e68a9b12cb523caae1.twindb.com.
_etcd-client._tcp.twindb.com. 300 IN    SRV     0 0 2379 etcd-c3e9dea04ba411e68a9b12cb523caae1.twindb.com.

@akuzminsky can I see the code snippet of your client initialization? I've used srv domains multiple times and never happened to stumble upon such an issue.

I just ran into this too - looks like python-etcd is querying _etcd instead of _etcd-client when using srv records.

yup, I did that in order to be in sync with what confd is doing.

Why not to be in sync with the official docs?

To help clients discover the etcd cluster, the following DNS SRV records are looked up in the listed order:
_etcd-client._tcp.example.com
_etcd-client-ssl._tcp.example.com


if passed an array object, the first displayed is the last element of json

for example I have this kind of json
	[ {
		"name"        : "reports-observation",
		"version"     : "1.0.0",
		"description" : "",
		"main"        : "server.js",
		"scripts"     : {
			"test"  : "echo \"Error: no test specified\" && exit 1",
			"start" : "node server.js"
		},
		"author"       : "",
		"license"      : "ISC",
		"dependencies" : {
			"csv"          : "^0.4.2",
			"csv-generate" : "0.0.4",
			"exceljs"      : "^0.1.11",
			"express"      : "^4.12.3",
			"fast-csv"     : "^0.6.0",
			"hapi"         : "^8.4.0",
			"should"       : "^6.0.1"
		}
	}, {
		"name"        : "reports-observation",
		"version"     : "1.0.0",
		"description" : "",
		"main"        : "server.js",
		"scripts"     : {
			"test"  : "echo \"Error: no test specified\" && exit 1",
			"start" : "node server.js"
		},
		"author"       : "",
		"license"      : "ISC",
		"dependencies" : {
			"csv"          : "^0.4.2",
			"csv-generate" : "0.0.4",
			"exceljs"      : "^0.1.11",
			"express"      : "^4.12.3",
			"fast-csv"     : "^0.6.0",
			"hapi"         : "^8.4.0",
			"should"       : "^6.0.1"
		}
	} ]

the first displayed is the "dependencies field instead of the "name" field.

p.s. if I want this to create an xls/xlsx file how would I do that?

Hello @xxryan1234 thanks for the feedback!
Can you please try using the option orderHeaders: false?
About the XLS / XLSX currently there is no support for this extension, maybe in the future =)

Thanks for this! It's okay now. XLS / XLSX would surely help! Thanks


Multilanguage Content how to?

I manage to have this theme running with multilanguage. However making a posts a different story altogether, nothing works well at least the recent post appear on the English version. But posts link just doesn't works. I have tried multi variations without such luck. Maybe some help?
You can see my code at https://github.com/tirtadji-com/tirtadji-com.github.io
Need to get more information on the structures.
Also adding id.toml to the list

Manage to fixed the posts and now both languages can start, however, the recent post only shows 1. Unsure why?

Hey @ranrinc, I've downloaded and ran your project

I do see a single post as well. However, looking at your config that's what I would expect

My understanding is that with hugo i18n all posts/content are isolated within their own locales. Let me know if i'm missing something or misunderstanding your issue.

Hey @ranrinc, I've downloaded and ran your project

I do see a single post as well. However, looking at your config that's what I would expect

My understanding is that with hugo i18n all posts/content are isolated within their own locales. Let me know if i'm missing something or misunderstanding your issue.

Hi @alex-bezek thanks for the help.. I actually manage to have both language up and running hahahaha... just need to read hugo document a little bit longer in order to have it working

awesome! glad it worked out for you @ranrinc


Docker can't push to insecure

Is this a request for help?: Yes.

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes: 1.13.1
Which chart: docker-registry
What happened: I was able to deploy the chart, however it seems to run in insecure mode, and when I try to push to it, I get:
╰ 09:33:58 $ docker push registry.hearn.local/nginx
The push refers to repository [registry.hearn.local/nginx]
Get https://registry.hearn.local/v2/: x509: certificate has expired or is not yet valid

Docker clearly wants to push to an HTTPS service.  I do see a TLS option in the "ingress" section of values.yaml, but ingress is disabled, and I'm hoping to just use NodePort (I have an external HAProxy loadbalancer I can use to direct http/https traffic to the nodeport).
What you expected to happen:
I expect to be able to push and pull to my registry.
How to reproduce it (as minimally and precisely as possible):
Edit values.yaml thusly:
# Default values for docker-registry.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 1

updateStrategy:
  # type: RollingUpdate
  # rollingUpdate:
  #   maxSurge: 1
  #   maxUnavailable: 0

podAnnotations: {}

image:
  repository: registry
  tag: 2.6.2
  pullPolicy: IfNotPresent
# imagePullSecrets:
    # - name: docker
service:
  name: registry
  type: NodePort
  # clusterIP:
  port: 5000
  nodePort: 30180
  annotations: {}
  # foo.io/bar: "true"
ingress:
  enabled: false
  path: /
  # Used to create an Ingress record.
  hosts:
    - registry.hearn.local
  annotations:
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  labels: {}
  tls:
    # Secrets must be manually created in the namespace.
    - secretName: registry-cert
      hosts:
        - registry.hearn.local
resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #  cpu: 100m
  #  memory: 128Mi
  # requests:
  #  cpu: 100m
  #  memory: 128Mi
persistence:
  accessMode: 'ReadWriteOnce'
  enabled: false
  size: 10Gi
  storageClass: "gluster-heketi"

# set the type of filesystem to use: filesystem, s3
storage: filesystem

# Set this to name of secret for tls certs
# tlsSecretName: registry.docker.example.com
secrets:
  haSharedSecret: ""
  htpasswd: ""
# Secrets for Azure
#   azure:
#     accountName: ""
#     accountKey: ""
#     container: ""
# Secrets for S3 access and secret keys
#   s3:
#     accessKey: ""
#     secretKey: ""
# Secrets for Swift username and password
#   swift:
#     username: ""
#     password: ""

# Options for s3 storage type:
# s3:
#  region: us-east-1
#  regionEndpoint: s3.us-east-1.amazonaws.com
#  bucket: my-bucket
#  encrypt: false
#  secure: true

# Options for swift storage type:
# swift:
#  authurl: http://swift.example.com/
#  container: my-container

configData:
  version: 0.1
  log:
    fields:
      service: registry
  storage:
    cache:
      blobdescriptor: inmemory
  http:
    addr: :5000
    headers:
      X-Content-Type-Options: [nosniff]
  health:
    storagedriver:
      enabled: true
      interval: 10s
      threshold: 3

securityContext:
  enabled: true
  runAsUser: 1000
  fsGroup: 1000

priorityClassName: ""

nodeSelector: {}

tolerations: []

Run helm install .
Attempt to push to the new registry.
Anything else we need to know:
It may or may not be related, but it doesn't seem like it created a PersistentVolumeClaim either.  I can certainly do that manually, but the persistence config seems to indicate that it wants to do so itself (values.yaml doesn't offer a field for a pre-made PVC name).

If you push directly to the nodePort you will need to add it as an insecure registry in you local docker.

Sorry, I should have mentioned other things I've tried.
I put this in /etc/docker/daemon.json:
{ "insecure-registries":["registry.hearn.local"] }

And I restarted docker after adding it.
"registry.hearn.local" is a CNAME record that points to a shared "keepalived" IP for my HAProxy cluster, which redirects http connections to port 30180 on my K8s worker nodes.  I pulled down an "nginx" image from Docker Hub, and then tagged and tried to push to my new registry:
╭ ✔ mhearn@julep:~/k8s/docker-registry [master L|…1]
╰ 07:48:39 $ docker tag 881bd08c0b08 registry.hearn.local/nginx
╭ ✔ mhearn@julep:~/k8s/docker-registry [master L|…1]
╰ 07:48:41 $ docker push registry.hearn.local/nginx
The push refers to repository [registry.hearn.local/nginx]
3e9eb35b1c23: Preparing
c59b3ca455e3: Preparing
6744ca1b1190: Preparing
error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found\n"

It looks like the registry API is working, though:
╰ 07:48:43 $ curl http://registry.hearn.local/v2/_catalog
{"repositories":[]}

If I bypass the HAProxy setup by adding a worker node and port 30180 to /etc/docker/daemon.json, I can push to it:
╭ ✔ mhearn@julep:~/k8s/docker-registry [master L|…1]
╰ 07:55:24 $ docker push kubenode01.hearn.local:30180/nginx
The push refers to repository [kubenode01.hearn.local:30180/nginx]
3e9eb35b1c23: Pushed
c59b3ca455e3: Pushed
6744ca1b1190: Pushed
latest: digest: sha256:7734a210432278817f8097acf2f72d20e2ccc7402a0509810c44b3a8bfe0094a size: 948

And then API calls to both the node and the load balancer work fine:
╭ ✔ mhearn@julep:~/k8s/docker-registry [master L|…1]
╰ 07:56:16 $ curl http://kubenode01.hearn.local:30180/v2/_catalog
{"repositories":["nginx"]}
╭ ✔ mhearn@julep:~/k8s/docker-registry [master L|…1]
╰ 07:56:27 $ curl http://registry.hearn.local/v2/_catalog
{"repositories":["nginx"]}

So it seems like all calls directly to a worker node work fine; pushes through the HAProxy fail, but API queries (at least for catalog lists) work fine.  Weird.

Another funky thing I noticed when examining the HAProxy logs; it looks like even with the insecure registry settings, docker is still trying to talk to the secure port for push/pull commands.  The first two lines (where HAProxy is forwarding to the https connection for my kubernetes dashboard, the default backend) here are from a "pull" command from my laptop; the http one is a curl command:
Mar 15 08:32:36 haproxy01 haproxy[41551]: <IP_ADDRESS>:58460 [15/Mar/2019:08:32:36.017] https_front dashboard_backs/kubenode02.hearn.local 1/1/9 853 -- 1/1/0/0/0 0/0
Mar 15 08:32:36 haproxy01 haproxy[41551]: <IP_ADDRESS>:58462 [15/Mar/2019:08:32:36.030] https_front dashboard_backs/kubenode03.hearn.local 1/0/9 854 -- 1/1/0/0/0 0/0
Mar 15 08:37:43 haproxy01 haproxy[41551]: <IP_ADDRESS>:49366 [15/Mar/2019:08:37:43.382] http_front registry_back/kubenode01.hearn.local 0/0/0/16/16 200 230 - - ---- 1/1/0/1/0 0/0 "GET /v2/_catalog HTTP/1.1"

I guess I could just manually specify port 80, but was trying to avoid that.  This is probably a question for docker itself, but I wonder if there's a way to configure docker such that when it's talking to an insecure registry it actually uses port 80?


The navbar icons does not have any hover effect at all.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The navbar icons does not have any hover effect at all.
Add Screenshots / Video Clip

What browsers are you seeing the problem on?
No response
Agreements

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSoC contributor
[X] I'm a Hacktoberfest contributor
[X] I want to work on this issue [Optional]
[X] I'm willing to provide further clarification or assistance if needed.

assign me the task under GSSOC AND HACKTOBERFEST .


Change check-lint.sh to invoke flake8 via tox.

Prevents complaints raised by newer versions of flake8/pep8.

LGTM


Page needs review

The advice on this page seems out of date. The import-module command didn't work, it needed to be install-module first and then another error
PS C:\WINDOWS\system32> $Setting = Get-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id
Get-AzureADDirectorySetting : The term 'Get-AzureADDirectorySetting' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ef84a3e0-879e-4312-a89d-7a3bb0cd9a51
Version Independent ID: 43851f8a-b71f-0a0a-8b1f-629e3528972f
Content: Assign sensitivity labels to groups - Azure AD
Content Source: articles/active-directory/enterprise-users/groups-assign-sensitivity-labels.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @curtand
Microsoft Alias: curtand

Hi @jaggersystems, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update the doc as appropriate

Hi @jaggersystems, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update the doc as appropriate

Hi, no problem. I have since realised there is AzureAD and AzureADPreview cmdlets to import. Either way, the import-module command without having the module installed first could confuse others.

Hi, no problem. I have since realised there is AzureAD and AzureADPreview cmdlets to import. Either way, the import-module command without having the module installed first could confuse others.

Hi @jaggersystems
Thanks for your feedback! I added in the PowerShell install step in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/160472
#please-close


Latest version of SealPIR

This version includes significant changes, making SealPIR easier to use and more efficient. It splits up the code into client/server, automatically converts a database of binary data to FV plaintext polynomials, has utilities for generating FHE parameters, etc.

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


Modifications for Digital Input Multiplexers

Description of changes
SEE CLOSED PR #135 (which this one replaces) FOR INFO
This firmware version requires PR #651 of Mobiflight connector (it works flawlessly without that, but Dig.Input Muxes can't be configured without it).
Refers to issue #119.
Includes PR #167; to see specific modifications please refer to individual commits.

Oh no. I did not understand that comment right :(

In the light of the new PR opened, can this one be closed?

implemented by https://github.com/MobiFlight/MobiFlight-FirmwareSource/pull/169


Add ability for the qgb relayer to replay old validator set changes and data commitments

Currently, the relayer only listens for changes from celestia, and then posts those on an evm chain when applicable. It will also need the functionality to replay existing validator set  changes and data commitments, effectively catching the qgb contracts up with the current state of celestia.

Can we change the title to:
Add ability for the qgb relayer to replay old validator set and data commitments changes from celestia to an evm chain

?

sure, left out the "from celestia to an evm chain" as that is reasonably implicit

closing for: https://github.com/celestiaorg/celestia-app/issues/298


Missing documentation and minor error in the icefront package

The code in the icefront package does not agree with the documentation in terms of how the heat and salt transfer coefficients are defined. There's also an issue in the calculation of the melt rate. I'll discuss these issues in turn.
Confusion about turbulent transfer coefficients
Xu et al. (2012, doi:10.3189/2012AoG60A139) is the paper describing the icefront package. It states that the (dimensionless) heat and salt transfer coefficients are γT = 1.1E-3 and γS = 3.1E-5. This is consistent with the recommendation in Table 2 of Jenkins et al. (2010, doi:10.1175/2010JPO4317.1), who use the notation Cd^{1/2} Γ_T and Cd^{1/2} Γ_S.
icefront_thermodynamics.F uses the terms ICEFRONTheatTransCoeff and ICEFRONTsaltTransCoeff to denote dimensional quantities (in m/s). They are effectively defined in that file as
ICEFRONTheatTransCoeff = max(1.0E-2*abs(W)*sqrt(1.5E-3), 1E-4)
ICEFRONTsaltTransCoeff = 5.05E-3*ICEFRONTheatTransCoeff

Some of these values are familiar from Jenkins et al. That is, on page 2308, they mention a dimensional heat transfer coefficient of 1E-4 and a salt transfer coefficient of 5.05E-7 (5.05E-3*1E-4). However, these are not their recommended values in their Table 2. (Edit: the two coefficients are stated in Appendix of Losch 2008, which details the shelfice package). As for the other two numerical values in the code, it is not clear what either 1.0E-2 or sqrt(1.5E-3) correspond to.
The dimensional transfer coefficients should be ICEFRONTheatTransCoeff =Cd^{1/2} Γ_T w = 1.1E-3*abs(W) and ICEFRONTsaltTransCoeff = Cd^{1/2} Γ_S w = 3.1E-5*abs(W)
As for enforcing a minimum velocity, it seems like the best approach would be to follow Slater et al. (2015, doi:10.1002/2014GL062494) and set the minimum velocity to 0.04 m/s.
Mistake in solving for the ice--ocean interfacial salinity
Edit Aug 25, 2020: My statement below and the working in the Mathematica notebooks contains its own sign error. See instead my comment on Aug 25 (and corrected Mathematica notebook), which shows that changing the sign of eps3 solves the problem as pointed out by @mjlosch.
Edit: Sep 11, 2020: The apparent error actually stems from a typo in Equation 2 of Xu et al. (2012) as identified by @owang01. Code in the icefront package was always correct.
Two lines in icefront_thermodynamics.F have sign errors
aqe should equal: a0*(-eps1 - eps3) (i.e., the sign for the second term is wrong)
bqe should equal: -eps1*eps6 + sLoc*a0*eps3 - eps3*eps7 + eps2 (i.e., signs for 2nd and 3rd term are wrong)
The ultimate effect of this change is minimal, since the only real consequence of the change is a minor change in the output for the melt rate. Nevertheless, it is incorrect according to my calculations. Attached to this post are a (zipped) Mathematica notebook detailing the error, and a PDF copy of that notebook.
icefront_calcs.pdf
icefront_calcs.nb.zip

@dngoldberg @mjlosch take a look and let me know if you want me to get involved with making changes to doc here.

OK I confess to mixing up with authors were associated with the various *ICE packages.... but this is an extension of shelfice (for which @mjlosch is a point person)... but a bit confused about the documentation here. pkg icefront is not documented at all in the user manual (so a bit confused about the issue first sentence above to fix doc that's missing?). If you are a user here, @hugke729 would you be willing to submit a start at text/equations doc for users manual?

I had a quick look at pkg/icefront/icefront_thermodynamics.F and the definitions of eps3, aqe, and bqe are not the same as in pkg/shelfice/shelfice_thermodynamics.F, which makes it a little more involved to check. I'll have a closer look, but can't promise anything, because the icefront code is not "mine".
[Note that the appendix in Losch (2008) contains an error, which is corrected in the online documentation of the model, but I never submitted a corrigendum, because the correct form of the equations has been published before.]

@jrscott By missing documentation, I was thinking more about comments within icefront_thermodynamics.F, or at least elswhere within the package files. I'd be willing to write up some documentation for the package since I've got a good handle on how it all works. But there's still the obstacle of figuring out where the 1.0E-2 and sqrt(1.5E-3) values come from. Or, more generally, why the treatment of the turbulent transfer coefficients doesn't match Xu et al. (2012).

Hi Ken (and Jeff, Jean-Michel, Chris, and Ian), I worked on pkg/icefront a long time ago,
but mostly to check-in code that Yun wrote (until she got her own MITgcm account)
and it’s very hazy in my foggy memory.  Would the time history of the code:
http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log
help in any way?
Separately but related, as part of ECCO branch of MITgcm, Ian Fenty has been developing a package
that combines pkg/shelfice and pkg/icefront.  I wonder if this would be good opportunity to bring back Ian’s
version in main MITgcm repository?  I am a little (a lot) out of touch with the particulars of both the ECCO
and main branches of MITgcm but I remember that the last two times that we attempted to carry separate
version of ECCO and main MITgcm code branches, it ended up in a lot of wasted effort and confusion.
I don’t know if it is possible (or even desirable) to re-combine the ECCO and main MITgcm branches
but at the very least it would be nice to have a discussion about this.
Dimitris

On Aug 24, 2020, at 8:20 AM, Ken Hughes<EMAIL_ADDRESS>wrote:
@jrscott https://github.com/jrscott By missing documentation, I was thinking more about comments within icefront_thermodynamics.F, or at least elswhere within the package files. I'd be willing to write up some documentation for the package since I've got a good handle on how it all works. But there's still the obstacle of figuring out where the 1.0E-2 and sqrt(1.5E-3) values come from. Or, more generally, why the treatment of the turbulent transfer coefficients doesn't match Xu et al. (2012).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/MITgcm/MITgcm/issues/363#issuecomment-679192124, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABH7CSJUGG7NIRNSRW6KCPLSCKAMJANCNFSM4QCKYIZQ.

I am running Ian and Ou’s combined package with the latest code. If you need a compatible version I could push it. These are the modified files (it only uses shelfice package):
shelfice_forcing.F       SHELFICE.h              shelfice_init_fixed.F  SHELFICE_OPTIONS.h    shelfice_solve4fluxes.F
shelfice_forcing_surf.F  shelfice_init_depths.F  shelfice_init_varia.F  shelfice_readparms.F  shelfice_thermodynamics.F
Ou has a copy of this too, and it would likely be best if he pushed it since he did much of the development.
(Ou, only changes I haven’t yet fed back to you are renaming diagnostics so that they are all 8 characters.)
Matt

On Aug 24, 2020, at 9:57 AM, Dimitris Menemenlis<EMAIL_ADDRESS>wrote:
Hi Ken (and Jeff, Jean-Michel, Chris, and Ian), I worked on pkg/icefront a long time ago,
but mostly to check-in code that Yun wrote (until she got her own MITgcm account)
and it’s very hazy in my foggy memory. Would the time history of the code:
http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log https://urldefense.com/v3/__http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log__;!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWXv4HeFpA$ http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log https://urldefense.com/v3/__http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm/pkg/icefront/icefront_thermodynamics.F?view=log*3E__;JQ!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWUXVJsZXg$
help in any way?
Separately but related, as part of ECCO branch of MITgcm, Ian Fenty has been developing a package
that combines pkg/shelfice and pkg/icefront. I wonder if this would be good opportunity to bring back Ian’s
version in main MITgcm repository? I am a little (a lot) out of touch with the particulars of both the ECCO
and main branches of MITgcm but I remember that the last two times that we attempted to carry separate
version of ECCO and main MITgcm code branches, it ended up in a lot of wasted effort and confusion.
I don’t know if it is possible (or even desirable) to re-combine the ECCO and main MITgcm branches
but at the very least it would be nice to have a discussion about this.
Dimitris

On Aug 24, 2020, at 8:20 AM, Ken Hughes<EMAIL_ADDRESS>wrote:
@jrscott https://github.com/jrscott https://urldefense.com/v3/__https://github.com/jrscott*3E__;JQ!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWUFFYd3Mw$ By missing documentation, I was thinking more about comments within icefront_thermodynamics.F, or at least elswhere within the package files. I'd be willing to write up some documentation for the package since I've got a good handle on how it all works. But there's still the obstacle of figuring out where the 1.0E-2 and sqrt(1.5E-3) values come from. Or, more generally, why the treatment of the turbulent transfer coefficients doesn't match Xu et al. (2012).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/MITgcm/MITgcm/issues/363#issuecomment-679192124 https://urldefense.com/v3/__https://github.com/MITgcm/MITgcm/issues/363*issuecomment-679192124*3E__;IyU!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWWxfA6tKg$, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABH7CSJUGG7NIRNSRW6KCPLSCKAMJANCNFSM4QCKYIZQ https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABH7CSJUGG7NIRNSRW6KCPLSCKAMJANCNFSM4QCKYIZQ*3E__;JQ!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWUNOl8yuQ$.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/MITgcm/MITgcm/issues/363*issuecomment-679247170__;Iw!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWVKS-VvEQ$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AIEXPOHZMNSAIEXTSZFSKGTSCKLXPANCNFSM4QCKYIZQ__;!!Mih3wA!TExKDfD2DBK9A8CM3pHCQSP68Vx84KB68JxkEr6QyX8Ah87xH4HYCG5HHWVliLa66g$.

@menemenlis Thanks for the code history link. The current treatment of the transfer coefficients was added in revision 1.9 with a comment that they are now functions of the vertical velocity, but unfortunately I still see no details about where the specific formulation for these coefficients comes from.
@mmazloff What is the aim of Ian and Ou's revised shelfice package? I've just started working on my own variant of the icefront package that combines with shelfice to approximate icebergs (stationary, but with thermodynamics) in a high-resolution 3D scenario.

Hi Ken
My understanding is that Ian and Ou simply added a shelf-front component to the shelfice package, so melt happens on both the shelf horizontal and vertical faces. I don’t think there  are any new parameterization added to account for icebergs physics.
They will have to correct me...
Matt

On Aug 24, 2020, at 10:41 AM, Ken Hughes<EMAIL_ADDRESS>wrote:
@menemenlis https://urldefense.com/v3/__https://github.com/menemenlis__;!!Mih3wA!S83Jlvm4-IkDZdwDw03BlR1_0wiR4QvxQGMjsMrq3PE2HXC-JZpm5UYqtWC9ADk-9Q$ Thanks for the code history link. The current treatment of the transfer coefficients was added in revision 1.9 with a comment that they are now functions of the vertical velocity, but unfortunately I still see no details about where the specific formulation for these coefficients comes from.
@mmazloff https://urldefense.com/v3/__https://github.com/mmazloff__;!!Mih3wA!S83Jlvm4-IkDZdwDw03BlR1_0wiR4QvxQGMjsMrq3PE2HXC-JZpm5UYqtWDQldUs1g$ What is the aim of Ian and Ou's revised shelfice package? I've just started working on my own variant of the icefront package that combines with shelfice to approximate icebergs (stationary, but with thermodynamics) in a high-resolution 3D scenario.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/MITgcm/MITgcm/issues/363*issuecomment-679269419__;Iw!!Mih3wA!S83Jlvm4-IkDZdwDw03BlR1_0wiR4QvxQGMjsMrq3PE2HXC-JZpm5UYqtWD1M9bUGA$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AIEXPOBJX2ASPJU4VAKJJGTSCKQ37ANCNFSM4QCKYIZQ__;!!Mih3wA!S83Jlvm4-IkDZdwDw03BlR1_0wiR4QvxQGMjsMrq3PE2HXC-JZpm5UYqtWD9Gk9haQ$.

I can try to push the combined package. The file shelfice_thermodynamics.F is quite different from the one on the main branch. I'll probably have to rename shelfice_thermodynamics.F in the combined package to something else and add a CPP option in do_oceanic_phys.F to call the two different versions of shelfice_thermodynamics.F, similar to seaice_growth.F and seaice_growth_adx.F in the seaice package.

@hugke729 I have gone through the derivation of the shelfice pkg again, and added it to the documentation (see https://github.com/mjlosch/MITgcm/tree/shelfice_documentation/doc), and I think I can agree with you that in the icefront pkg, there's is something wrong with the sign of eps3 (should be -eps3).
@owang01 I think it would be very useful to have this combined package, but can you actually reproduce old (and established) results with this? In principle adding the icefront part should not compromise the basal melting part of pkg/shelfice. I remember discussing that with @ifenty but can remember the result. I would advise against having different versions of almost the same thing, because it is just too confusing. I suggest that you do a pull request and then we can see what has changed and how it is possible to merge the whole stuff.

@mjlosch I concur that the switching the sign of eps3 makes everything correct. Attached to this comment is my working in Mathematica demonstrating this.
So that just leaves the issue of where the values of 1.0E-2 and sqrt(1.5E-3) come from in the formulation of the transfer coefficients.
icefront_calcs_negative_eps3.nb.zip
icefront_calcs_negative_eps3.pdf

@mjlosch When @ifenty and I developed the combined package, we were able to reproduce results generated using the main branch code, based on an idealized configuration.
I made a pull request #368, and you can take a look at what the changes are and advise how to merge it to the main branch. Thanks.

@hugke729 and @mjlosch I believe the sign of eps3 in the icefront package of the main branch is correct. We should not put a minus sign before eps3. However, there is an sign error in equation (2) of Xu et al. (2012). Specifically, the sign before the second term on RHS, the conductive heat flux, should be "minus". The RHS should be −q[Lf - CpI (Tice − TB)], which is the sum of latent heat flux and conductive heat fluxes needed to melt the ice. The colder ice (smaller Tice), the more conductive heat. Note that the sign convention for melt rate q is negative for melting.
Maybe @hugke729 could check in Mathematica if we need to reverse the sign of eps3 with the updated eq. (2) described above.

Good catch @owang01. I never stopped to check that the signs in the paper were correct. I agree with your argument that the conductive heat flux should have a minus sign since the RHS should be the sum of (i) the latent heat of ice and (ii) the sensible heat needed to warm ice from Tice to Tb.
I checked in Mathematica and can confirm that the icefront package does not need changing after all.

@hugke729 Thanks for the confirmation.


Update FFP plugin

Is your feature request related to a problem?
We need to update the ffp (Far Field Pattern) plugin in VisIt visualizing EM patterns. Updated files are attached here avtffp5.tar.gz
This update involves using either the ACM Softwrae Licensed Fortran code 772 or a re-write of that code called stripack.f90 licensed by the individual author (and which we have yet to seek permission to use).
The work here involves the following logistics...

Updating the FFP plugin source code (the easy part)
Ensuring Fortran 77 or Fortran 90 code for stripack feature will compile as shared lib for the FFP plugin
Addressing potential licensing issues by one or more of the following

Making the plugin OFF by default but ensuring it is built with VisIt binary releases
Adding functionality to explicitly build the plugin (--ffp option) to build_visit and then a query to to accept license terms for it
Optionally disabling the stripack feature in the plugin based on either makefile variables that control it or build_visit license question answer.

This was resolved in a previous release


pygmentex: update src

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Does this require a backport?

@Mic92 It stopped building on unstable NixOS with the error message:
unpacking source archive /tmp/nix-build-source.drv-2/pygmentex.zip
suspicious ownership or permission on ‘/nix/store/f7y42xwy0h04xvi2rncnycpd3m7kiv0j-source’; rejecting this build output

I was told on IRC that  there has recently been some security changes within nix, to present exploits based on impure file permissions, and the reported error could be related to it.
I fixed it by tagging pygmentex on the repository and downloading directly from it, instead of CTAN.
If this change on nix is backported to 17.09, this fix should also be.


Fix lint errors with new header standard

Our new header standard has one bad side effect. The problem is that the linter in Visual Studio Code marks files names in RED even when they are valid. We should strive to have no false error reporting in our development tool chain.

Today, there are no files in red in VSC. However I did see a case earlier today where a simple "while" statement had red underlines although it was identical to other similar structures in the same source file.  However when I came back to that file (mqttBroker) there were no underlined parts, and no filenames in red. It's almost as if linter takes a long time to  figure things out.
Willleave this open for a while to see if red filenames return.

It seems that Linter is gong to require us to configure our files so each source file can be independently compiled so that Linter has access to all variables macros and includes when we're editing a single source file. This is disappointing, and I suspect will lead us back to the web of reference interconnections we were trying to fix. Disabling Linter is tempting, but probably not acceptable. I'll start reworking the header file standard.

moved some includes from main.cpp to main.h
put an include main.h in almost all cpp files
compiles OK
/lib file have their own .h file references, and don't follow our new conventions. Best to address this as we convert them from OOP to functional programming


Fix #1431: Sample data ingestion is broken

Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@pmbrull mlmodel ingestion is broken , server is throwing 500 after the recent patch merge. Can you look into it. For now I commented out the ingestion from SampleSource

@pmbrull mlmodel ingestion is broken , server is throwing 500 after the recent patch merge. Can you look into it. For now I commented out the ingestion from SampleSource

will do, sorry for that


added favicon and fixed SignIn issue

Related Issues
added favicon and title and also fixed the sign-in link on the SignUp page
Closes: #70
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

@purnima143 Can you resolve this?

@maw1a  i'll make given  the changes today. My semester exams are going on that's why the delay

@maw1a i'll make given the changes today. My semester exams are going on that's why the delay

Sure, take your time 👍

@maw1a  Please review the changes


How delete with proxy?

I try delete row in my table and get 500 error:
DELETE http://<IP_ADDRESS>:3001/api/disps/92 500 (Internal Server Error)
READ, CREATE, UPDATE works fine
i have proxy
routeRules: {
    '/api/**': { proxy: {to: 'http://localhost:1337/api/**'} },
  },

strapi: {
    url: '/api',
    prefix: '',
    version: 'v4',
    cookie: {},
    cookieName: 'strapi_jwt',
    auth: {
      populate: "*"
    },
  }

just use nginx reverse proxy


Debugging C/C++ WASM code doesn't work

Hi there,
I built a wasm toolchain from the recent LLVM10 release and compile my C code to wasm with command :

clang --target=wasm32 fib.c -nostdlib -Wl,-entry=fib -g -O0 -o fib.wasm

Then debug it with the wasmtime built from the lastest master branch:

lldb -- ./wasmtime/target/release/wasmtime  run fib.wasm --invoke fib 40

The breakpoint to function fib works well, but the local variables in my C code can't be viewed. Maybe I am not doing things in the right way. Could some one please help me? Thanks in advance.

Current executable set to './wasmtime/target/release/wasmtime' (x86_64).                                                                    [0/1836]
(lldb) settings set -- target.run-args  "-g" "fib.wasm" "--invoke" "fib" "40"
(lldb) b fib
Breakpoint 1: no locations (pending).
WARNING:  Unable to resolve breakpoint to any actual locations.
(lldb) r
Process 26871 launched: '/data/home/terry/projects/wasmtime/wasmtime/target/release/wasmtime' (x86_64)
1 location added to breakpoint 1
warning: using --invoke with a function that takes arguments is experimental and may break in the future
Process 26871 stopped

thread #1, name = 'wasmtime', stop reason = breakpoint 1.1
frame #0: 0x00007ffff6209026 JIT(0x555555dccfb0)`fib(n=) at fib.c:2:13
1    int fib(int n) {
-> 2      int i, t, a = 0, b = 1;
3      for (i = 0; i < n; i++) {
4        t = a;
5        a = b;
6        b += t;
7      }
(lldb) n
Process 26871 stopped
thread #1, name = 'wasmtime', stop reason = step over
frame #0: 0x00007ffff6209030 JIT(0x555555dccfb0)`fib(n=) at fib.c:3:10
1    int fib(int n) {
2      int i, t, a = 0, b = 1;
-> 3      for (i = 0; i < n; i++) {
4        t = a;
5        a = b;
6        b += t;
7      }
(lldb) p t
error: Couldn't materialize: couldn't get the value of variable t: Expression stack needs at least 1 item for DW_OP_plus_uconst.
error: errored out in DoExecute, couldn't PrepareToExecuteJITExpression
(lldb)

And my fib C code is as below:
int fib(int n) {
  int i, t, a = 0, b = 1;
  for (i = 0; i < n; i++) {
    t = a;
    a = b;
    b += t;
  }
  return b;
}

CC @yurydelendik

You also need to pass -g to `wasmtime. Otherwise it won't generate debuginfo for the jitted code.

Oh, of course. I wonder if we could warn about this somehow. @yurydelendik could we do something like detect that a debugger is attached and warn if we don't have debug info for the JITted code?

@bjorn3 Sorry that I pasted wrong command line. The -g option doesn't help.

terry@wasm-test01:~/projects/wasmtime$ lldb -- ./wasmtime/target/release/wasmtime -g fib.wasm --invoke fib 40
(lldb) target create "./wasmtime/target/release/wasmtime"
Current executable set to './wasmtime/target/release/wasmtime' (x86_64).
(lldb) settings set -- target.run-args  "-g" "fib.wasm" "--invoke" "fib" "40"
(lldb) b fib
Breakpoint 1: no locations (pending).
WARNING:  Unable to resolve breakpoint to any actual locations.
(lldb) r
Process 5489 launched: '/data/home/terry/projects/wasmtime/wasmtime/target/release/wasmtime' (x86_64)
1 location added to breakpoint 1
warning: using --invoke with a function that takes arguments is experimental and may break in the future
Process 5489 stopped

thread #1, name = 'wasmtime', stop reason = breakpoint 1.1
frame #0: 0x00007ffff7fba026 JIT(0x555555dc5310)`fib(n=) at fib.c:2:13
1    int fib(int n) {
-> 2      int i, t, a = 0, b = 1;
3      for (i = 0; i < n; i++) {
4        t = a;
5        a = b;
6        b += t;
7      }
(lldb) n
Process 5489 stopped
thread #1, name = 'wasmtime', stop reason = step over
frame #0: 0x00007ffff7fba030 JIT(0x555555dc5310)`fib(n=) at fib.c:3:10
1    int fib(int n) {
2      int i, t, a = 0, b = 1;
-> 3      for (i = 0; i < n; i++) {
4        t = a;
5        a = b;
6        b += t;
7      }
(lldb) p t
error: Couldn't materialize: couldn't get the value of variable t: Expression stack needs at least 1 item for DW_OP_plus_uconst.
error: errored out in DoExecute, couldn't PrepareToExecuteJITExpression
(lldb)

2 things might be happening here:

DW_AT_frame_base patch for LLVM came late for v10 release so it might not be included (I'm building fib-wasm.wasm file with clang-11)
There is big refactoring and bug fix at https://github.com/bytecodealliance/wasmtime/pull/1572 -- it might be related here

I think I found something fishy. These lines in expression.rs:
                let wasm_start = local_range.start;
                let wasm_end = local_range.end;

(around line 490) seem bogus. local_range is a Cranelift type ValueLocRange, which most probably don't contain Wasm bytecode offsets, but function-relative machine-code offsets. Then doing translate_ranges with those won't make sense. Instead the machine offset ranges must be  iterated in the FuncTransform based on their gen_start and gen_end.
@yurydelendik can you confirm (some of) this?
I keep working on this.

I think I found something fishy. These lines in expression.rs:
                let wasm_start = local_range.start;
                let wasm_end = local_range.end;

@yurydelendik can you confirm (some of) this?

@ggreif Yes, it is fixed in #1572. Can you review entire PR? ;)

@yurydelendik @ggreif Thanks for your work. I can confirm that the variables in C code can be viewed with the latest llvm trunk and the fix in #1572.

Fixed by #1572.

Quick question @yurydelendik, do you have a link to the DW_AT_frame_base patch so I can confirm I have It because I see the same problem.

do you have a link to the DW_AT_frame_base patch so I can confirm I have It because I see the same problem.

AFAIK DW_AT_frame_base related patch, not my though, landed in LLVM (since version 10?)

Might very well be the case :) I just could Not find any info searching for that.


Recommended Portfolio plugin that plays well with FoundationPress?

Hi all!
A client of mine would like to use a portfolio within their website. What's the best, filterable portfolio plugin that you've come across that integrates well within FoundationPress?
Thank you in advance.

Hi,
if you know how to make a unique theme out of FoundationPress, I would like to suggest you create a custom post type for your portfolio objects, choose your visual approach (jQuery), and create custom, context-aware loops for your portfolio content, which you can then style to your design. You could even use some Foundation components for your portfolio display!
IMHO, forget those wordpress org plugins, they're bad for you and your design.

Hi @Eccola !
I know how to add custom post types through a plugin, how do I create custom, context-aware loops for my portfolio content?
Any help would be appreciated!

FoundationPress is a developers dream, now you really can code premium quality themes for your clients out of it, in no time. You have a working dev environment? Use Grunt?
So, I just finished a portfolio/blog site a couple of weeks ago at http://stormarts.fi and had a great success with Justified Gallery: http://miromannino.github.io/Justified-Gallery/ with Swipebox. Everything here is done on FoundationPress. There is still no image optimization, this is photographers site, and you know they want to crop their images to exotic proportions and usually there's no image compression used before uploading. Kinda heavy image-wise, otherwise very light.
You better get started, so here's a basic loop and a page template for FoundationPress which outputs your portfolio objects into F5 block-grid:
https://gist.github.com/Eccola/05616be9b0b3117c92e8
More: http://foundation.zurb.com/docs/components/block_grid.html
Must read: http://www.billerickson.net/code/wp_query-arguments/
for your object filtering tasks.
Just update/add the arguments to your needs.
Create your custom post type with title, editor, thumbnail, excerpt, whatever to your needs, you can even attach some neat custom fields to them, if you like. Use taxonomies, tag your objects, or categorize them. Create new taxonomies if needed.
Create a page named Portfolio or something and use the portfolio.php template, add some portfolio objects, attach featured images to them and see how they populate the Portfolio page. Now, styling is a breeze with FoundationPress.
If you for some reason want to ditch block-grid, you could easily update the output to your new syntax.
That's the basics of looping, what do you think?
There's more, just ask :)

I share @Eccola 's view of using third-party plugins. Many of the plugins out there are less good in quality, unfortunately. There is however one plugin that I would always recommend. Advanced Custom Fields. Check it out!
@Eccola . Nice work on Storm Arts! Looks great! Would you mind if I add a link to your site from the 'selection of sites using FoundationPress' section on the front-page of the FoundationPress repo?

@jdfweb : I used the Advanced Custom Fields plugin with the Repeater Field add-on for my own portfolio http://olefredrik.com (yeah, I know it's very basic).

@olefredrik , it would be an honor to be added to the selection!

ACF is definitely how I would do it as well.

I'm gonna +1 on ACF as well - it's literally been one of the few plugins that does exactly what I need without bogging down (or worse, conflicting with) any WP install and theme combination that I'm using. This is includes, but isn't limited to, FP. I am not associated with ACF in any way, so when I say that it's really the best one I've used to tie various site components together and not muck up my grid, I really truly mean it.


fix: tag copied cut widgets with layout system type

Description

Adds a tag to copied and exported (partial export) widget data, that contains the layout system type of the source page.
When pasting or importing the above tag is used to verify if the layout system type of the current page and source page matches.
If it doesn't match, a message is shown in a toast notification and the paste/import skips adding widgets.
In the case of partial import, everything else is imported except for widgets, if the layout systems donot match.

Note: Since partial import/export use the paste saga to add widgets to the page, the following have been handled:

The message shown to the user is generic and doesn't specify paste or import.
Both fixes have been added in the same PR.

Fixes #34159
Fixes #34160
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Sounds like a neat idea. I'll do this when looking into separating Anvil copy/cut/paste from Fixed mode. Paste is already separated. I'll deal with the copy and cut flows as well.


Updating content: caching.md to Webpack 4.7.0

Updating content of the caching.md because of the deprecated CommonsChunkPlugin plugin for the sake of using the new : SplitChunksPlugin with optimization fields.
PS : This will probably lead us to update the Code Splitting as well, which will be done in future commit.

@asapach Changes were applied.

@montogeek over the Travis there's : Unexpected end of JSON input is that content problem ?

No, GitHub API restriction

@dhruvdutt this is not being merged because of github api restriction advice to check it.

@houssem-yahiaoui Friendly ping

@montogeek kindly check.

@montogeek reframed and fixed proselint error.

@EugeneHlushko I think this looks good, though some of your comments are valid, @houssem-yahiaoui are you able to address them?

@houssem-yahiaoui Friendly ping

Closing due to inactivity, please ping when back active


Fix/docupdate

Jira Ticket: PXP-xxxx

[ ] Remove this line if you've changed the title to (PXP-xxxx):

New Features
add helm-doc action
Breaking Changes
Bug Fixes
add permissions
Improvements
Add repo
breakout workflow
Dependency updates
Deployment changes

Handled in another PR


Completed Task 776 : Design System > Elements > Enhancements in Toast

Description

Added new properties to match the wireframe
Added 4 stories Default, Download, Chat & Request

ScreenShot

Default (With Header):

Default (Without Header):

Toast with Download (With Header)

Toast with Download (Without Header)

Toast with Chat (With Header)

Toast with Chat (Without Header)

Toast with Request (With Header)

Toast with Request (Without Header)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Code changes related to 'Color variant' should be done after Rahul pushed his changes of 'Color Variant' to development.

Error resolved. Now its working

Color Variants are added for icons also and icon fill control removed as per wireframe

some args are not required, so removed it.

resolved

resolve conflicts


Add deployment to montitor KafkaChannel CM changes

This deployment is useful to monitor and audit ConfigMap
changes for KafkaChannel.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>

/test unit-tests_eventing-kafka-broker_main

/retest

/cherry-pick release-1.5

/cherry-pick release-1.4

/cherry-pick release-1.3

/cherry-pick release-1.2

/retest-required

/retest-required

/test upgrade-tests_eventing-kafka-broker_main


Add link to GitHub Action

Just wanted to share the GitHub Action I wrote to install just. I use just regularly as a command runner in my projects and often want to run it in CI. See extractions/setup-just.

This is awesome!
For the readme, what do you think about:
=== GitHub Actions

link:https://github.com/extractions/setup-just[extractions/setup-just] can be used to install `just` in a GitHub Actions workflow.

Example usage:

```yaml
- uses: extractions/setup-just@v1
  with:
    just-version: 0.8  # optional semver specification, otherwise latest
```

Is "semver specification" the word for a semver requirement specifier, i.e. "^0.5.0"?
I was trying to figure out what people call it  most frequently, but nothing stood out. It seems like, in practice, people don't distinguish between a semantic version, e.g. 0.5.0, and a npm-style semver specifier, i.e ^0.5.0.
In any case, semver specification is fine.

Yes, it is a semver requirement specifier. I'm using this package in the GitHub Action: https://www.npmjs.com/package/semver. This package resolves plain versions slightly differently to Cargo though where 0.5.0 is equivalent to =0.5.0 not ^0.5.0.

Awesome, merged.
You might consider documenting in the action's readme that it's an npm-style semver spec. Just users are pretty varied, but I think a good chunk of them are Rust users, and they might be confused by the difference.
Thanks so much for writing and documenting this, I think it's a really nice addition.


Angular

@shiv19
This PR fixes issue 28. I updated the Angular bindings. One can now use the old or the new interface. I also updated the demo to show how things work. A lot easier to use now and no timing related trouble anymore. I at the same time update the ios podfile to the lates 8 version of the library

Thank you @cjohn001 <3

@cjohn001
can you please rebase your branch with master and push again?

I am not so good with git. How does this rebase work?

Also before we do that,
why is this PR coming to the angular branch?
can you please close this PR and make a PR to master branch instead?
from your local branch, just do
git remote add upstream https://github.com/NativeScript/nativescript-ui-charts.git
then
git rebase upstream master
If any rebase conflicts arise
resolve conflicts if any, track the changes (git add .) and run git rebase --continue
once the rebase is complete, force push to origin,
git push origin angular --force
then make a PR from your angular branch to the master of this repo.
Hope that makes sense.

@shiv19. I have read your comment to late. But thanks for the explantion.  I did it in a similar way now. Did this work as you meant or should I try again?

Already merged and released your new PR :)
Cheers!
Closing this now.


closes #10 and closes #14

This PR should be limited to add and list release branches.
Also includes Graphs based on custom rules.
Work In Progress

lets merge, and move towards https://github.com/sundeep-co-in/transtats/issues/16


add test functions for types

This PR lets you do:
Interfaces.test(Dict)

And it will find all the interfaces Dict implements, and test them.

sorry I didn't find time to review

No worries it wasn't very controversial, just what we have already for Interface types but for the target type