[FEATURE] A way to know if an embedded typeform is over quota and "closed"

Hi there! Thanks for much for all the maintenance work on this library 🙌
I've been using the iframe embed SDK. We're now putting the app into sleeper mode after running it actively with a plan. Was hoping to opportunististically show the free plan;s typeform when the monthly quota is still there, and otherwise, skip the intake survey. This doesn't seem to be possible from the app that's embedding the typeform.
Things I've checked:

whether retrieve form endpoint of the Create API changes at all once the quota is hit. It doesn't seem to, neither in settings.is_public or otherwise. E.g., https://api.typeform.com/forms/aYU17R3F
whether any error or extra payload is delivered from a "closed" (overquota) typeform to let the app know that something is up.

Neither of these work. But I think this would support users.
Potential solutions are:

return an error from onStarted or onReady when the form can't be loaded, or
show some indication of over-quota status in the public API for forms.

I know that I'm now wondering whether other form tools are better for the long-tail after our consultation, to keep collecting slow feedback after our main event. I'll be idly looking to other tools in the future if Typeform can't support this.
Thanks for considering this feature request!

Hello @patcon
thank you for the suggestion. I dont know how many customers would be interested in such feature, but I do agree it would be nice to have. Unfortunately I can not promise any timeline, but we will look into it.

I like your suggestion to indicate if the form is open in one of the callbacks. This will mitigate any need for server-side implementation on your side, as API endpoints are not available to be called from browser.
I think the onStarted is not executed for closed forms because, well, they can not be started (I need to double check this). However the onReady payload might be the correct place to put this information.

Thanks for thinking on it! I understand the constraint on commiting :)
I'll keep tabs on this issue for our next consultation. For now, we'll just close typeform after the gig, and disable it from our app.

API endpoints are not available to be called from browser

Small point of clarification: can't we already use the read endpoint of the Create API without auth from the browser? Like I seem to be able to curl this, so I presume my app could use fetch() on it and get a status there, yeah? Would just be a little off-road, and not actually supported by the Embed SDK in an official way
https://api.typeform.com/forms/aYU17R3F

I think the onStarted is not executed for closed forms because, well, they can not be started (I need to double check this). However the onReady payload might be the correct place to put this information.

And just to make sure I understand, the possible states seem to be like so:

unpublished (aka not public)

❓ all forms start this way, but can't re-enter this state via UI. can re-enter this state only via PATCH request to settings.is_public: false with API personal access token.
✅ onReady executes
✅ onStarted executes

published (aka public)

❓ state after clicking the "publish" button in UI, or PATCH to settings.is_public: true with API personal access token
✅ onReady executes
✅ onStarted executes

closed

❓ done through UI, via "access & scheduling" menu, and settings.is_public: true
❌ onReady doesn't execute
❌ onStarted doesn't execute

over-quota (aka "private" in docs), and settings.is_public: true

❓ different than "closed" state
✅ onReady executes
✅ onStarted executes

Does all of the above look right? This was what I was seeing in my testing, but maybe I'll confirm

It looks like you might know more about this aspect of typeforms than I do @patcon . Good job writing this down. Maybe we could use one of the callbacks (onReady seems like a good candidate) and indicate all of the states in the payload. Or should be introduce new callbacks for those state? I will discuss with the team.

heh thanks :) Just wanted to thoroughly explore for my own understanding, and glad if it helps y'all choose more thoughtfully.
All said and done, and additional onReady payload feels like it would accomodate anything I can think of! A status with a value like "open" or "closed" would be a minimum that would seem to align with existing documentation. Another state for "closed (overquota)" might be nice, but wouldn't add anything for my use-case, as I'm happy for the app to treat both as equivalent :)
Thanks you again for thinking on this!

We'd also see a lot of value in having this. Currently, if there is any error creating the widget (e.g. incorrect form ID), then https://www.typeform.com/explore/ would display within our website. Ideally, we'd want to navigate the user somewhere else on error. Although, it's an unlikely scenario it could occur if we are dynamically injecting the formId, when a/b testing for example.

@donovantc I think this is different use case, since there is a difference if the form is closed or there is a 404 error 🤔

@mathio I guess the issue is that none of the existing callbacks fire if the form cannot be found due to incorrect form Id, unless I'm missing something?
Having an onError callback would be ideal in my opinion.
This may be different to the case mentioned above. Happy to file a separate issue if that would be better?

Yes, this is correct. We will need to implement a post message on our side to notify the embed about any errors.

Hi @patcon
I have some good news. We were able to prioritize your feature request and I just opened a PR: https://github.com/Typeform/embed/pull/670
The onReady callback will receive isClosed boolean value to indicate if the form is closed. Forms can be closed manually, based on timestamp or when a response limit is reached (set manually per form, or the limit of your account plan).
Unfortunately we can not implement this callback for forms that are not published or for invalid URLs (form not found) at this time.
I hope this helps your use case.

Thanks @mathio! This def addresses and improves use-cases like mine in the future :)


circt: add shared libs

This changes adds circt's shared libs.
Previous circt only included some binaries related to circt, but with this change it will include shared libs and some files from LLVM used by circt. In the future, it might be nice to split the files into smaller packages (e.g. binaries, libs, llvm stuff, ...) but for now I think this should be all right.
Previous version
$ find -L result | wc -l
10
$ du -shL result
276M	result

New version
$ find -L result | wc -l
5229
$ du -shL result
450M	result

CC: @sequencer
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Ask for review by @SharzyL

The default install contains too many binaries and libraries from LLVM. I am trying multiple outputs.

The default install contains too many binaries and libraries from LLVM. I am trying multiple outputs.

I set outputs = [ "bin" "lib" "dev" "out" ]; but nix complains
error: cycle detected in build of '/nix/store/jhv4qsdi5jm6my2r8lxkmw7lbkdaijh3-circt-1.56.1.drv' in the references of output 'bin' from output 'dev'

Trying to figure out why

any progresses? @SharzyL

After investigation, dev contains lot of reference in $bin$, and bin/llvm-config contains a reference of $dev, thus causing a cycling references. A solution is to remove llvm-config (and other unnecessary binaries).
I would proposes the following changes
diff --git a/pkgs/development/compilers/circt/default.nix b/pkgs/development/compilers/circt/default.nix
index f2939ceb53f0..38bd10575332 100644
--- a/pkgs/development/compilers/circt/default.nix
+++ b/pkgs/development/compilers/circt/default.nix
@@ -61,13 +61,6 @@ stdenv.mkDerivation rec {
     substituteInPlace cmake/modules/GenVersionFile.cmake --replace "unknown git version" "${src.rev}"
   '';

-  installPhase = ''
-    runHook preInstall
-    mkdir -p $out
-    CMAKE_INSTALL_PREFIX=$out cmake --build . --target install --config Release
-    runHook postInstall
-  '';
-
   doCheck = true;
   checkTarget = "check-circt check-circt-integration";

@@ -75,6 +68,17 @@ stdenv.mkDerivation rec {
     rev-prefix = "firtool-";
   };

+  # Only keep circt-related binaries in $bin/bin
+  # Also note that bin/llvm-config may contain $dev string in its content, causing cycle references between $bin and $dev
+  postInstall = ''
+    mkdir bin-backup
+    mv $bin/bin/{fir,hls}tool $bin/bin/circt-* bin-backup/
+    rm $bin/bin/*
+    mv bin-backup/* $bin/bin
+  '';
+
+  outputs = [ "bin" "lib" "dev" "out" ];
+
   meta = {
     description = "Circuit IR compilers and tools";
     homepage = "https://circt.org/";

Now we have
$ du -shL result-*
276M    result-bin
94M     result-dev
81M     result-lib
648M    result-out

(where result-lib contains only CIRCT libs and result-out contains all libs)

Or can we move llvm-config to the dev output? I think the same has been done on llvm.

https://github.com/NixOS/nixpkgs/blob/fccf04b6200b711977dbfe9a59e3356bfe768932/pkgs/development/compilers/llvm/15/llvm/default.nix#L379
Oh that's true. Now we can write postInstall as
mkdir -p $dev/bin bin-backup
mv $bin/bin/{fir,hls}tool $bin/bin/circt-* bin-backup
mv $bin/bin/* $dev/bin
mv bin-backup/* $bin/bin

But it may make $dev much larger, I doubt if circt-dev users need them.

any progress for this PR?

Sorry, I was busy for a while. I'll check and updated this PR tomorrow.

Or can we move llvm-config to the dev output? I think the same has been done on llvm.

But it may make $dev much larger, I doubt if circt-dev users need them.

Before I updated this, I'm checking if I can separate circt and llvm.

Sorry for not making so much progress.
I have worked on this for a while and it seems that splitting the llvm build produces better results.
I will open a new PR for that.


How can I open commisioning window from chip-tool and then commisioning on network on home assistant?

I would like to know it because I have been able to commisionate a device using chip-tool, but as I have home assistant OS in a VM, I can't commisionate the device using bluetooth so by opening the commisioning window with chip-tool and then commisioning it with Home Assistant over the network will allow me to test the matter server.

This should help
https://community.home-assistant.io/t/matter-in-home-assistant-workshop-announcement/426129/132?u=shukkar

I tried, I have been able to commisionate the device using on network pairing with chip-tool (so commisioning on network works), but home assistant can't do the same. From the commisioning logs, I've read that it tries to use ble commisioning, and if it doesn't find a Bluetooth adapter, it fails.
I'm going to change the title of the issue to represent better the problem that exist now.

I have successfully used home-assistant to commission on-network device. BLE error message inb my case was a red-herring - HA add-on also does IP discovery after BLE fails. However, my success rate on pairing was one in five or less - something likely to do with UDP device discovery.  Double check that you are using a manual pairing code when calling matter_experimental.commission , Do not use the one that starts with MT:

Thanks! This workaround (or maybe it isn't a workaround) worked. It works better after restarting the matter server.

The MT: pairing code (QR Code) has a bitfield which says where too look for the device. If you use a QR code which has been generated for Bluetooth commissioning, commissioning won't work.


Fixed redirect_to after successful login

The redirect_to was not working correctly on a successful POST request login. I updated the logic to be consistent with how Django does it. See here as example to how Django handles getting redirect_to from params.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 5ac5581bdd22f5aed3a3a827552be4096dd9d990 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

@Bouke I went ahead and added a test_valid_login_with_custom_post_redirect test case. Let me know if there's any other changes you'd like.

Coverage remained the same at 95.879% when pulling 0c6592282e9a975ddc412f54000108aadb1283f3 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 0c6592282e9a975ddc412f54000108aadb1283f3 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 0c6592282e9a975ddc412f54000108aadb1283f3 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Coverage remained the same at 95.879% when pulling 808f3f3ba4913e36a03f9065d00ecb33ce0d6608 on Tesorio:fix-redirect into 5b671df9604fb18cd89749334f4593068cc7a1e1 on Bouke:master.

Nice work, thank you!

No problem! When will you deploy this to PyPI?

I have not date for it; as a deploy takes quite a bit of my free time.


Adding new images for Getting started with MRTK article

Docs Build status updates of commit 563eef6:
:clock10: Pending: waiting for processors (20 builds ahead of you)
:warning: Docs Build is busy, currently there are 20 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 563eef6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/MRTK_HandJointChaser_Main.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/MRTK_StandardShader.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/MRTK_UX_Slider_Main.jpg
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add support for searching filtering for languages

I'm adding the possibility to search filtering for a specific language

Done with PR #8

closed by PR #8


@conda-forge-admin, please add user @mthh

Additional comment:
Hi !
I am the maintainer of https://github.com/mthh/jenkspy.
If I become a jenkspy-feedstock maintainer I could help to keep the version on conda-forge up to date with the original package.
Thanks.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @mthh in conda-forge/jenkspy-feedstock#22.


NewCantus volpiano treats bar lines and underlay differently from before

Something is different about how NewCantus handles bar lines from OldCantus, e.g compare old and new https://cantusdatabase.org/chant/669059;

A lot of Alleluia chants seem to have been affected by this change e.g. https://cantusdatabase.org/chant/642479

I suppose we could find and fix every one of these, or change whatever it is about the Volpiano rules that makes this show up all weird and misaligned. (Tagging @dchiller since I believe he was looking into other Volpiano rules at some point.)

Thanks! Yes, this should be fixed shortly

Possibly related:
In NewCantus, if a chant does not end with "---" before a gap, the Volpiano displays as only a second treble clef.
If it ends with 6------6 and no final ---, the Volpiano duplicates (!)
Behold (chant has since been corrected, so I won't link to it).

I agree that this is complete in the sense -- these types of chants are well-aligned in NewCantus.


gen-push-lists: Retain existing data

In https://github.com/googlefonts/gftools/blob/main/bin/gftools-gen-push-lists.py I suggest the script read the current values, and retain them.

What Marc suggests is a good idea: if a directory is in one the lists but not in the Traffic Jam project, then it should not be removed and we should have a message about it.

Fixed in #462


TaskOutput not formatted as expected

We're running a crew and want to output the result of each task to a Streamlit UI.
We're using the task_callback parameter with the crew, but there were two issues that tripped us up:

The TaskOutput type is not exported in the __init__ file for tasks, we put it there manually for now and use that to type the expected object coming into the callback handler. (Also helps to know what fields are expected!)

https://github.com/joaomdmoura/crewAI/blob/a3363818498893012be970164a119068b723a402/src/crewai/tasks/task_output.py#L6-L15

The agent name is not being passed in our code, there is no entry as defined in the code above.

I am getting a similar error when running a crew consisting of 4 agents and 5 tasks. It seems that there may be a problem with task.output's format. For reference, this is the exact error I am getting:
\Lib\site-packages\crewai\task.py", line 93, in execute
    context.append(task.output.result)
                   ^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'result'

And the function execute that gets accessed is the following:
def execute(
        self,
        agent: Agent | None = None,
        context: Optional[str] = None,
        tools: Optional[List[Any]] = None,
    ) -> str:
        """Execute the task.

        Returns:
            Output of the task.
        """

        agent = agent or self.agent
        if not agent:
            raise Exception(
                f"The task '{self.description}' has no agent assigned, therefore it can't be executed directly and should be executed in a Crew using a specific process that support that, like hierarchical."
            )

        if self.context:
            context = []
            for task in self.context:
                if task.async_execution:
                    task.thread.join()
                context.append(task.output.result)
            context = "\n".join(context)

        tools = tools or self.tools

        if self.async_execution:
            self.thread = threading.Thread(
                target=self._execute, args=(agent, self, context, tools)
            )
            self.thread.start()
        else:
            result = self._execute(
                task=self,
                agent=agent,
                context=context,
                tools=tools,
            )
            return result```

I would like to ask for some help here. I can provide more information or context, if needed.

If it's a TaskOutput class like what's defined above you'd want task.output.raw_output I believe, but I also don't see where you have the same type of callback set, what I'm describing the issue is when you pass a function to task_callback on the crew configuration.
For the code above, what does task.output look like if you print it? I'd start there to see the object shape then try to find the related class in the crewAI code.


workflows: update to use latest runner images

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The github action workflows are referencing some legacy image runners, which are gonna be fully decommissioned soon, for example, for macos-10.15, it would be removed by March 31 2023.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Just workflow setup changes.
Does this PR introduce a user-facing change?
NONE

@chenrui333 may I ask you to rebase this one?


Cannot get addin to work

When I publish from msbuild in Cake it is working 100%. When publishing from VS it is working 100% using the same credentials.
When I use the plugin I Get an error  using the exact detail:
Microsoft.Web.Deployment.DeploymentException: Source (sitemanifest) and destination (contentPath) are not compatible for the given operation.
The Deploy task in Cake
Task("Deploy")
.IsDependentOn("Build")
.Description("Deploy an example website")
.Does(() =>
{
DeployWebsite(new DeploySettings()
{
SourcePath = "./MyWeb/MyWeb/obj/Release/Package/MyWeb.zip",
SiteName = "TestSite1",
        ComputerName = "iis02",
        Username = "deploy",
        Password = "P@ssw0rd00"
    });
});

I have tried every combination I can think off it simple does not work.
This task in cake is working.
Task("Build")
.Description("Publish the website to a zip package")
.Does(() =>
{
// Build all solutions.
foreach(var solution in solutions)
{
Information("Building {0}", solution);
    //You need to include the 'DeployOnBuild' property to create the publish zip
    MSBuild(solution, settings =>
        settings.SetPlatformTarget(PlatformTarget.MSIL)
            .WithProperty("TreatWarningsAsErrors","true")
            .WithProperty("DeployTarget","MsDeployPublish")
            .WithProperty("DeployOnBuild","true")
            .WithProperty("MSDeployPublishMethod","InProc")
            .WithProperty("MSDeployServiceUrl","https://iis02:8172/MsDeployAgentService")
	.WithProperty("DeployIisAppPath","TestSite1")
            .WithTarget("Build")
            .SetConfiguration(configuration));
}

});

Google's first result for your error message sums it up nicely.

Ive updated the troubleshooting page to include your error message


Rename get_object_2 function.

Is your feature request related to a problem? Please describe.
The MLX90614 package contains two IR sensors, IR1 and IR2.
PyMLX90614 has a function to read the temperature from each of these.
#1 renames the IR1 function, but not IR2. We may need to rename the IR2 function.
Describe the solution you'd like
We need more research and discussion in this area. What is the purpose of two identical IR sensors in the same package?
Based on my understanding, IR2 may be faulty in some/many MLX90614s (binning process). IR1 should always work.
Perhaps rename the IR2 function to get_obj_temp_backup or something along those lines (keeping the current get_obj_temp as get_obj_temp).
Describe alternatives you've considered
No interesting alternatives. I suppose we could remove the second function altogether, but someone may find it useful to be able to use both IR sensors.
Additional context
There is some discussion in #1 about this.

Tested get_object_2 on another MLX90614 - value is constant -273.15.

I have bought a Generic 906 MLX90614 ESF Baa OOO Tu ND Infrared Thermometer IR Sensor from amazon and the get_object_2 returns also -273.15 which is 0K (zero kelvin). I don't have any idea why this value is present though. I'm just providing a little feedback because I questioned myself why is the data even there. Regards


netlink C ext: add PROC_EVENT_SID

Apparently it didn't exist in 2.6.28 but got introduced later. Maybe it
makes sense to just add a default case to be future proof.
Since I fixed that, I wasn't able to reproduce issue #69

I think it makes more sense to ignore all events (current and future) that god doesn't care about, so a default case is probably better than explicitly listing all known events. Can you resubmit this with that change?


MiqPolicies REST API support

Adding CRUD actions to policies API endpoint.
Current api example:
add/update
{
    "action": "add",
    "resource": {
        "description": "sample policy",
        "name": "sample policy",
        "towhat": "ManageIQ::Providers::Redhat::InfraManager",
        "conditions_ids": [
            2,
            3
        ],
        "action_id": 1,
        "event_id": 2
    }
}

The api supports a single action, and event, can extend it if needed.

@miq-bot add_label wip

@miq_bot remove_label wip

@imtayadeway @abellotti please review.

I think all of the comments were issued, please review again @abellotti @imtayadeway
Is there a way to auto expand the actions, conditions, events, to be displayed on all API calls for policies automatically?

Hi @alongoldboim with these being subcollections, this can be requested with the expand parameter. i.e. GET /api/policies?expand=resources,actions,conditions,...

@alongoldboim I had some questions above (editing policies, and required attrs for creates).  Thanks.

@abellotti I changed the api a bit to be more flexible, edits and checking of the needed params is working.

Hi @alongoldboim one additional change to create, also if you could take care of the rubocop warning (line length in spec).  Thanks!!

This LGTM!! Thanks @alongoldboim for this API enhancement.  Will merge then 🍏

@alongoldboim is this euwe/yes or no ?

@miq-bot add_label euwe/no


Add automatic redirect creation V2

(re)implements the 'backend' requirements for https://github.com/wagtail/rfcs/pull/34
Rejigged slightly from the changes in #7761 / #7774 to make the handler enabled by default, and added a test to show the effect of deactivating.

@kaedroho / @gasman This PR is now ready for a second review, having implemented all of the previous feedback. I apologise in advance for the sprawl... I probably could have gotten away without breaking up Page.get_url_parts() and Site.get_site_root_paths() quite so much, but I I hope you'll agree it makes the code easier to digest? On the whole, I think the changes help to dispel some of the 'magic' around how URLs work, and should make it easier for devs.

Closing in favour of #7827


TypeError: __WEBPACK_IMPORTED_MODULE_2_vue_easy_toast

I'm attempting to use the toaster within a single file component, but I am getting the following error:
dcaReports.vue?a5fd:167 Uncaught (in promise) TypeError: __WEBPACK_IMPORTED_MODULE_2_vue_easy_toast___default(...) is not a function
at VueComponent.eval (eval at <anonymous>  (main.js:1273), <anonymous>:173:79)

Here is my setup:
 <script>
import { mapActions } from 'vuex'
import Datepicker from 'vuejs-datepicker'
import toast from 'vue-easy-toast'
   export default { ...
   ...
   ...
       methods: {
          detach: function(match, member){
              this.$http.post('/detachCompany', ids ).then((response) => {
                var data = response.data
                if(data.status == 200){

                    toast('Hi, there!', {
                      id: 'my-toast',
                      className: ['my-toast', 'toast-warning'],
                      horizontalPosition: 'right',
                      verticalPosition: 'top',
                      duration: 3000,
                      mode: 'queue',
                    })

                }

            }, (response) => {
                //gah!! Error

            });
    },

Am I missing something?

hi @retrogradeMT , this is a vue plugin, so you have to "use" it beforehand, usually in your entry.js or index.js
// before start
import Toast from 'vue-easy-toast'
Vue.use(Toast)

Oh well, that's embarrassing.   I'm not why I didn't understand that immediately.    Thank you!


Support multiple references to the same footnote

# Heading

Some text with a footnote.[^1]

Some other text with the same footnote.[^1]

[^1]: The footnote

When rendered, the second paragraph renders the string literal "[^1]" instead of generating a second supertext link to the same footnote.

FYI this plugin does the job: https://github.com/markdown-it/markdown-it-footnote

FYI this plugin does the job: https://github.com/markdown-it/markdown-it-footnote

How exactly would the return link work in this case? Should it add another backlink or just link to the first one? I've circled the backlink, which refers back to the footnote reference 2.


updating the license to 2023

Fixes Issue #2834

Changes proposed

updating the license to 2023

Check List (Check all the applicable boxes)

[x ] My code follows the code style of this project.
[x ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x ] All new and existing tests passed.
[x ] This PR does not contain plagiarized content.
[x ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

@Panquesito7 please review.

@Panquesito7 please review.

Seeing as you created this PR only a few minutes ago, please avoid tagging maintainers as it creates one extra notification that they have to handle. A maintainer will always review and merge your PR as soon as they can :+1:


Add support for pip dependencies

Would fix #100 and probably fix https://github.com/jupyterlite/xeus-python-kernel/issues/48
This is very much experimental for now.
Pip is running with the --no-deps option, meaning that the user would need to install the package dependencies from conda-forge/emscripten-forge/PyPI themselves.
Pip is not made for installing packages in another environment (it is supposed to install packages for the Python version it uses, nothing else), so we have to workaround this by doing some shenanigans to make it work. The --no-deps option is one of those workarounds.
I don't think we should support reading some requirements.txt file for now, at least not before pip packages are more correctly supported, if they ever are.

Building with https://github.com/emscripten-forge/empack/pull/65
Running pip install with --no-deps may be required, because it seems to not look properly into what's already installed in the prefix we install packages.

Local testing is working. Let's release empack.
[LiteBuildApp] WARNING |
            Installing pip dependencies. This is very much experimental so use this feature at your own risks.
            Note that you can only install pure-python packages.
            pip is being run with the --no-deps option to not pull undesired system-specific dependencies, so please
            install your package dependencies from emscripten-forge or conda-forge.

Using pip 23.2 from /home/martinrenou/micromamba/envs/xeus-python-kernel/lib/python3.11/site-packages/pip (python 3.11)
Collecting ipycanvas
  Using cached ipycanvas-0.13.1-py2.py3-none-any.whl (255 kB)
Installing collected packages: ipycanvas
Successfully installed ipycanvas-0.13.1
jupyterlite-xeus-python:xeus:copy:ext:ipycanvas
.  post_build:jupyterlite-xeus-python:xeus:copy:ext:ipycanvas

Working great on RTD

Maybe we can also update the docs to remove this note?

And add a small yaml snippet to show how to install packages from PyPI when they are not available on conda forge?

Yes!

Thanks for the review!

Confirming in ipycanvas that installing a local Python package works nicely:
See https://github.com/jupyter-widgets-contrib/ipycanvas/pull/338
name: ipycanvas
channels:
  - https://repo.mamba.pm/emscripten-forge
  - https://repo.mamba.pm/conda-forge
dependencies:
  - pillow
  - numpy
  - ipywidgets
  - pip:
    - ..

@nthiery You can have a try with this!
The documentation for it is here https://xeus-python-kernel.readthedocs.io/en/latest/configuration.html#pip-packages
For example it is being used here https://github.com/jupyter-widgets-contrib/ipycanvas/pull/338


AttributeError: module 'datetime' has no attribute 'fromtimestamp'

When Running the import all.
I am getting
AttributeError: module 'datetime' has no attribute 'fromtimestamp'
Scanning directory: /Orignals Uploading file: /Orignals/2013/08/20130809_122538_CEA4BDD4.jpg Traceback (most recent call last):   File "/usr/local/bin/photoprism2immich", line 8, in <module>     sys.exit(main())   File "/usr/local/lib/python3.9/site-packages/photoprism2immich/photoprism2immich.py", line 113, in main     upload_files_from_path(args.originals, args.apikey, args.baseapiurl, args.log)   File "/usr/local/lib/python3.9/site-packages/photoprism2immich/photoprism2immich.py", line 73, in upload_files_from_path     upload(file_path, api_key, base_url, log_file)   File "/usr/local/lib/python3.9/site-packages/photoprism2immich/photoprism2immich.py", line 22, in upload     'fileCreatedAt': datetime.fromtimestamp(stats.st_mtime), AttributeError: module 'datetime' has no attribute 'fromtimestamp'

I just had the same error and fixed it locally on my machine, now the Script works fantastically and is currently uploading to my new immich Instance :)
You can fix it yourself too rather easily and quick until we get a proper patch:

Open the file that's mentioned in your log: /usr/local/lib/python3.9/site-packages/photoprism2immich/photoprism2immich.py
Replace the import in Line 5 from import datetime to from datetime import datetime

OR you can change the two lines (22 and 23) that call datetime.fromtimestamp to datetime.datetime.fromtimestamp

Just ran into this problem. Changing "import datetime" to "from datetime import datetime" worked! Thank you!!


Unable to disable touch on mobile

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.5.1

Platform/Target and Browser Versions: macOS X, Android, Chrome/Firefox/Opera/Edge

Live Link or JSFiddle/Codepen or website with isssue: https://lucacattide.dev

What you did
In the above provided URL, by scrolling down a few sections, you'l see a swiper slider set in vertical mode, with 3 different picture slides.
I'm trying to disable touch scrolling on mobile. I've used every option provided by the API - as suggested in many other questions on StackOverflow (which I've already checked) - with no success. Even if combining them in different alternatives, they don't work. On mobile, I'm still able to swipe slides by gestures. Actually, my slider expect the pagination in order to switch the slides and my final goal is to disable all other navigation events except that.
This is the current implementation:
swiperProject = new Swiper('.headline__container', {
    direction: 'vertical',
    autoplay: {
      delay: 5000,
      disableOnInteraction: false,
    },
    speed: 500,
    lazy: true,
    preloadImages: false,
    pagination: {
      el: '.swiper-pagination',
      clickable: true,
    },
    breakpoints: {
      320: {
       // I tried with allowTouchMove: false, allowSlidePrev/next: false too, but nothing
        touchRatio: 0,
        shortSwipes: false,
        longSwipes: false
      },
      992: {
        touchRatio: 1,
        shortSwipes: true,
        longSwipes: true
      }
    }
  });

Expected Behavior
The user shouldn't be able to slide between the pictures by gestures, but with the side pagination instead
Actual Behavior
Nothing of the provided API options for touch events management works.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

Forced a temporary pointer-events: none on mobile in waiting for Swiper API debugging with commit 500f2d2a1088704a5b2a5a15ab2b5f2bec1392ed.

I temporary forced a pointer-events: none on mobile, hoping that API will be fixed in the next future.
Thanks anyway for attention.


UATs for kubeflow 1.8 fail to run with ERROR: Cannot install -r requirements.txt

Bug Description
the UATs from branch track/1.8 are failing to run due a conflict in python dependencies between websockets and juju.
Example failed runs:
AKS
EKS
To Reproduce
run the UATs from branch track/1.8
Environment
juju 3.4/stable
k8s 1.29
Relevant Log Output
kubeflow-remote: install_deps> python -I -m pip install -r requirements.txt
ERROR: Cannot install -r requirements.txt (line 66) and websockets==8.1 because these package versions have conflicting dependencies.
Collecting anyio==4.0.0 (from -r requirements.txt (line 7))
  Downloading anyio-4.0.0-py3-none-any.whl.metadata (4.5 kB)
Collecting asttokens==2.4.1 (from -r requirements.txt (line 9))
  Downloading asttokens-2.4.1-py2.py3-none-any.whl.metadata (5.2 kB)
Collecting backcall==0.2.0 (from -r requirements.txt (line 11))
  Downloading backcall-0.2.0-py2.py3-none-any.whl.metadata (2.0 kB)
Collecting bcrypt==4.0.1 (from -r requirements.txt (line 13))
  Downloading bcrypt-4.0.1-cp36-abi3-manylinux_2_28_x86_64.whl.metadata (9.0 kB)
Collecting cachetools==5.3.2 (from -r requirements.txt (line 15))
  Downloading cachetools-5.3.2-py3-none-any.whl.metadata (5.2 kB)
Collecting certifi==2023.7.22 (from -r requirements.txt (line 17))
  Downloading certifi-2023.7.22-py3-none-any.whl.metadata (2.2 kB)
Collecting cffi==1.16.0 (from -r requirements.txt (line 23))
  Downloading cffi-1.16.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting charset-normalizer==3.3.2 (from -r requirements.txt (line 27))
  Downloading charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting cryptography==41.0.5 (from -r requirements.txt (line 29))
  Downloading cryptography-41.0.5-cp37-abi3-manylinux_2_28_x86_64.whl.metadata (5.2 kB)
Collecting decorator==5.1.1 (from -r requirements.txt (line 31))
  Using cached decorator-5.1.1-py3-none-any.whl.metadata (4.0 kB)
Collecting exceptiongroup==1.1.3 (from -r requirements.txt (line 35))
  Downloading exceptiongroup-1.1.3-py3-none-any.whl.metadata (6.1 kB)
Collecting executing==2.0.1 (from -r requirements.txt (line 39))
  Downloading executing-2.0.1-py2.py3-none-any.whl.metadata (9.0 kB)
Collecting google-auth==2.23.4 (from -r requirements.txt (line 41))
  Downloading google_auth-2.23.4-py2.py3-none-any.whl.metadata (4.7 kB)
Collecting h11==0.14.0 (from -r requirements.txt (line 43))
  Using cached h11-0.14.0-py3-none-any.whl.metadata (8.2 kB)
Collecting httpcore==1.0.2 (from -r requirements.txt (line 45))
  Downloading httpcore-1.0.2-py3-none-any.whl.metadata (20 kB)
Collecting httpx==0.25.1 (from -r requirements.txt (line 47))
  Downloading httpx-0.25.1-py3-none-any.whl.metadata (7.1 kB)
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
Collecting hvac==2.0.0 (from -r requirements.txt (line 49))
  Downloading hvac-2.0.0-py3-none-any.whl.metadata (3.3 kB)
Collecting idna==3.4 (from -r requirements.txt (line 51))
  Downloading idna-3.4-py3-none-any.whl.metadata (9.8 kB)
Collecting iniconfig==2.0.0 (from -r requirements.txt (line 56))
  Using cached iniconfig-2.0.0-py3-none-any.whl.metadata (2.6 kB)
Collecting ipdb==0.13.13 (from -r requirements.txt (line 58))
  Using cached ipdb-0.13.13-py3-none-any.whl.metadata (14 kB)
Collecting ipython==8.12.3 (from -r requirements.txt (line 60))
  Downloading ipython-8.12.3-py3-none-any.whl.metadata (5.7 kB)
Collecting jedi==0.19.1 (from -r requirements.txt (line 62))
  Downloading jedi-0.19.1-py2.py3-none-any.whl.metadata (22 kB)
Collecting jinja2==3.1.2 (from -r requirements.txt (line 64))
  Downloading Jinja2-3.1.2-py3-none-any.whl.metadata (3.5 kB)
Collecting juju==<IP_ADDRESS> (from -r requirements.txt (line 66))
  Downloading juju-<IP_ADDRESS>.tar.gz (582 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 582.0/582.0 kB 15.5 MB/s eta 0:00:00
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
Collecting kubernetes==28.1.0 (from -r requirements.txt (line 70))
  Downloading kubernetes-28.1.0-py2.py3-none-any.whl.metadata (1.5 kB)
Collecting lightkube==0.15.0 (from -r requirements.txt (line 72))
  Downloading lightkube-0.15.0-py3-none-any.whl.metadata (5.3 kB)
Collecting lightkube-models==<IP_ADDRESS> (from -r requirements.txt (line 74))
  Downloading lightkube_models-<IP_ADDRESS>-py3-none-any.whl.metadata (1.1 kB)
Collecting macaroonbakery==1.3.1 (from -r requirements.txt (line 76))
  Downloading macaroonbakery-1.3.1.tar.gz (79 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
Collecting markupsafe==2.1.3 (from -r requirements.txt (line 78))
  Downloading MarkupSafe-2.1.3-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.9 kB)
Collecting matplotlib-inline==0.1.6 (from -r requirements.txt (line 80))
  Downloading matplotlib_inline-0.1.6-py3-none-any.whl.metadata (2.8 kB)
Collecting mypy-extensions==1.0.0 (from -r requirements.txt (line 82))
  Using cached mypy_extensions-1.0.0-py3-none-any.whl.metadata (1.1 kB)
Collecting oauthlib==3.2.2 (from -r requirements.txt (line 84))
  Using cached oauthlib-3.2.2-py3-none-any.whl.metadata (7.5 kB)
Collecting packaging==23.2 (from -r requirements.txt (line 88))
  Downloading packaging-23.2-py3-none-any.whl.metadata (3.2 kB)
Collecting paramiko==2.12.0 (from -r requirements.txt (line 90))
  Downloading paramiko-2.12.0-py2.py3-none-any.whl.metadata (4.6 kB)
Collecting parso==0.8.3 (from -r requirements.txt (line 92))
  Downloading parso-0.8.3-py2.py3-none-any.whl.metadata (7.5 kB)
Collecting pexpect==4.8.0 (from -r requirements.txt (line 94))
  Downloading pexpect-4.8.0-py2.py3-none-any.whl.metadata (2.2 kB)
Collecting pickleshare==0.7.5 (from -r requirements.txt (line 96))
  Downloading pickleshare-0.7.5-py2.py3-none-any.whl.metadata (1.5 kB)
Collecting pluggy==1.3.0 (from -r requirements.txt (line 98))
  Downloading pluggy-1.3.0-py3-none-any.whl.metadata (4.3 kB)
Collecting prompt-toolkit==3.0.41 (from -r requirements.txt (line 100))
  Downloading prompt_toolkit-3.0.41-py3-none-any.whl.metadata (6.5 kB)
Collecting protobuf==3.20.3 (from -r requirements.txt (line 102))
  Downloading protobuf-3.20.3-py2.py3-none-any.whl.metadata (720 bytes)
Collecting ptyprocess==0.7.0 (from -r requirements.txt (line 104))
  Using cached ptyprocess-0.7.0-py2.py3-none-any.whl.metadata (1.3 kB)
Collecting pure-eval==0.2.2 (from -r requirements.txt (line 106))
  Downloading pure_eval-0.2.2-py3-none-any.whl.metadata (6.2 kB)
Collecting pyasn1==0.5.0 (from -r requirements.txt (line 108))
  Downloading pyasn1-0.5.0-py2.py3-none-any.whl.metadata (8.5 kB)
Collecting pyasn1-modules==0.3.0 (from -r requirements.txt (line 113))
  Downloading pyasn1_modules-0.3.0-py2.py3-none-any.whl.metadata (3.6 kB)
Collecting pycparser==2.21 (from -r requirements.txt (line 115))
  Downloading pycparser-2.21-py2.py3-none-any.whl.metadata (1.1 kB)
Collecting pygments==2.16.1 (from -r requirements.txt (line 117))
  Downloading Pygments-2.16.1-py3-none-any.whl.metadata (2.5 kB)
Collecting pymacaroons==0.13.0 (from -r requirements.txt (line 119))
  Using cached pymacaroons-0.13.0-py2.py3-none-any.whl.metadata (1.6 kB)
Collecting pynacl==1.5.0 (from -r requirements.txt (line 121))
  Using cached PyNaCl-1.5.0-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl.metadata (8.6 kB)
Collecting pyrfc3339==1.1 (from -r requirements.txt (line 126))
  Using cached pyRFC3339-1.1-py2.py3-none-any.whl.metadata (2.0 kB)
Collecting pytest==7.4.3 (from -r requirements.txt (line 130))
  Downloading pytest-7.4.3-py3-none-any.whl.metadata (7.9 kB)
Collecting pytest-asyncio==0.21.1 (from -r requirements.txt (line 135))
  Downloading pytest_asyncio-0.21.1-py3-none-any.whl.metadata (4.0 kB)
Collecting pytest-operator==0.31.0 (from -r requirements.txt (line 137))
  Downloading pytest_operator-0.31.0-py3-none-any.whl.metadata (3.5 kB)
Collecting python-dateutil==2.8.2 (from -r requirements.txt (line 139))
  Downloading python_dateutil-2.8.2-py2.py3-none-any.whl.metadata (8.2 kB)
Collecting pytz==2023.3.post1 (from -r requirements.txt (line 141))
  Downloading pytz-2023.3.post1-py2.py3-none-any.whl.metadata (22 kB)
Collecting pyyaml==6.0.1 (from -r requirements.txt (line 143))
  Downloading PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting requests==2.31.0 (from -r requirements.txt (line 149))
  Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting requests-oauthlib==1.3.1 (from -r requirements.txt (line 155))
  Downloading requests_oauthlib-1.3.1-py2.py3-none-any.whl.metadata (10 kB)
Collecting rsa==4.9 (from -r requirements.txt (line 157))
  Using cached rsa-4.9-py3-none-any.whl.metadata (4.2 kB)
Collecting six==1.16.0 (from -r requirements.txt (line 159))
  Downloading six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Collecting sniffio==1.3.0 (from -r requirements.txt (line 167))
  Downloading sniffio-1.3.0-py3-none-any.whl.metadata (3.6 kB)
Collecting stack-data==0.6.3 (from -r requirements.txt (line 171))
  Using cached stack_data-0.6.3-py3-none-any.whl.metadata (18 kB)
Collecting tenacity==8.2.3 (from -r requirements.txt (line 173))
  Downloading tenacity-8.2.3-py3-none-any.whl.metadata (1.0 kB)
Collecting tomli==2.0.1 (from -r requirements.txt (line 175))
  Downloading tomli-2.0.1-py3-none-any.whl.metadata (8.9 kB)
Collecting toposort==1.10 (from -r requirements.txt (line 179))
  Using cached toposort-1.10-py3-none-any.whl.metadata (4.1 kB)
Collecting traitlets==5.13.0 (from -r requirements.txt (line 181))
  Downloading traitlets-5.13.0-py3-none-any.whl.metadata (10 kB)
Collecting typing-extensions==4.8.0 (from -r requirements.txt (line 185))
  Downloading typing_extensions-4.8.0-py3-none-any.whl.metadata (3.0 kB)
Collecting typing-inspect==0.9.0 (from -r requirements.txt (line 189))
  Using cached typing_inspect-0.9.0-py3-none-any.whl.metadata (1.5 kB)
Collecting urllib3==1.26.18 (from -r requirements.txt (line 191))
  Downloading urllib3-1.26.18-py2.py3-none-any.whl.metadata (48 kB)
Collecting wcwidth==0.2.10 (from -r requirements.txt (line 195))
  Downloading wcwidth-0.2.10-py2.py3-none-any.whl.metadata (14 kB)
Collecting websocket-client==1.6.4 (from -r requirements.txt (line 197))
  Downloading websocket_client-1.6.4-py3-none-any.whl.metadata (7.7 kB)
Collecting websockets==8.1 (from -r requirements.txt (line 199))
  Downloading websockets-8.1.tar.gz (58 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
INFO: pip is looking at multiple versions of juju to determine which version is compatible with other requirements. This could take a while.

The conflict is caused by:
    The user requested websockets==8.1
    juju <IP_ADDRESS> depends on websockets>=10.0; python_version > "3.9"

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

kubeflow-remote: exit 1 (9.69 seconds) /home/runner/charmed-kubeflow-uats> python -I -m pip install -r requirements.txt pid=7583
  kubeflow-remote: FAIL code 1 (9.78 seconds)
  evaluation failed :( (9.83 seconds)

Error: Process completed with exit code 1.

Additional Context
No response

I believe the issue here is that some UATs (e.g. for 1.8) are not actually using main, but for instance the track/1.8 that are not up to date with the poetry modification. track/1.8 is still based on the old dependencies (without using poetry) but they are now running in the bundle tests using 24.04 bases, with python 3.12, hence the mismatch and the error.
I suppose we could either:

Run UAT tests for 1.8 against the main branch as well
Backport poetry to track/1.8

Of the two, 1 would be easier (also therefore removing the `track/1.8, limiting the maintainability burned), but I don't know if we can run the tests in main against the 1.8 deployment.


Add demo page

This branch removes the previous wasm example and adds a demo page.
The demo page is already deployed manually. This branch automatically deploys the demo when main branch is updated.

@kampersanda Thank you!
I updated the README without --locked because I think that flag is optional.


Regaining control of project name

Greetings @desandro and anyone else from @bower/registry,
I created angular-schema-form-material and was notified before the project was completed for alpha that my repo was copied with a different name (schemaform-material), but then submitted to Bower under the name of my repo.
I have logged an issue with them https://github.com/nick121212/schemaform-material/issues/2, but have not heard anything back yet so I thought I should raise it here to get a quick resolution.
You can see from the commit history that they are nearly all mine: https://github.com/nick121212/schemaform-material/commits/develop
I am now managing the entire https://github.com/json-schema-form organisation responsible for the project now, which led to some delay, so I suspect it was not malicious, more impatient, but I was hoping someone at Bower could help me please.
Regards,
Marcel

Looks like both schemaform-material and angular-schema-form-material are available to be registered. Has this already been resolved?

I just got a response, I wasn't sure what it meant till now, so I guess it is, yes, thank you!

Actually @desandro I'm not at my computer for another 8 hours as I'm in bed and it's midnight in Australia, any way to stop someone grabbing it overnight however unlikely that is?

Sorry for the intrusion, but I did that for you. :P
Now using node v5.10.1 (npm v3.8.3)
juanmav@juanmav:~$ bower register angular-schema-form-material https://github.com/json-schema-form/angular-schema-form-material.git
bower resolve       https://github.com/json-schema-form/angular-schema-form-material.git#*
bower checkout      angular-schema-form-material#master
bower resolved      https://github.com/json-schema-form/angular-schema-form-material.git#52a3011539
? Registering a package will make it installable via the registry (https://bower? Registering a package will make it installable via the registry (https://bower.herokuapp.com), continue? Yes
bower register      https://github.com/json-schema-form/angular-schema-form-material.git

Package angular-schema-form-material registered successfully!
All valid semver tags on https://github.com/json-schema-form/angular-schema-form-material.git will be available as versions.
To publish a new version, just release a valid semver tag.

Run bower info angular-schema-form-material to list the available versions.

Regards
JM


Blazor web app hangs on RclContext.CreateNode (sudden onset)

I had my Blazor web app working fine, communicating over ROS2 via a node I initialized in the Program.cs (relevant code below).  I then made a trivial change to my Razor file, and the next time I ran it, it would hang at the point where the node is created.  I can create the RclContext but can't do anything with it.
      using Rcl;
      ...
      var ctx = new RclContext();
      var node = ctx.CreateNode("ROS2dotNETwebApp");                                  // Hangs here
      var pub = node.CreatePublisher<Rosidl.Messages.Example.String>("/blazor");
      var sub = node.CreateSubscription<Rosidl.Messages.Example.String>("/blazed");
      builder.Services.AddSingleton(ctx);
      builder.Services.AddSingleton(node);
      builder.Services.AddSingleton(pub);
      builder.Services.AddSingleton(sub);
      var app = builder.Build();

I even created a new Blazor web app and only added these lines (and added to launchSettings.json environmentVariables and installed the RclNet NuGet package), and it still hangs.  I see an empty command window and never a home page.  When I terminate the command window, Visual Studio flashes a message saying "Unable to connect to web server 'https'".  If I run the Release EXE from a command window, it also hangs, and when I hit "Ctrl-C" to terminate, it displays:
[foonathan::memory] Allocator foonathan::memory::heap_allocator (at<PHONE_NUMBER>000000) leaked 36912 bytes.

In case it's relevant, I tried solving it by running the following commands in an admin command window:
dotnet dev-certs https --clean
dotnet dev-certs https --trust

What should I now try first?  Thanks...

UPDATE: I still can't explain how it started happening, but I may have stopped (most of) it.  I reinstalled my Humble but that still didn't fix it; simple commands like ros2 run demo_nodes_cpp talker and ros2 topic list were still hanging.  I discovered that running ros2 run demo_nodes_cpp talker --ros-args --log-level debug DID work, as did normal ros2 run demo_nodes_cpp talker afterward in the same command window, but ros2 topic list still hung.  I found this and on a whim, I entered set RMW_IMPLEMENTATION=rmw_cyclonedds_cpp and then set RMW_IMPLEMENTATION=rmw_fastrtps_cpp, and amazingly, I could run the talker (and listener) normally every time in subsequent command sessions.  Better, once I adjusted my launchSettings.json environmentVariables for the new installation paths, my Blazor web app ran fine again!
Only thing is, I still can't execute something like ros2 topic list without hanging.  Oh well, different issue?...


Add a readiness label for properties or components

Expected Behavior
We need a way to indicate when a component or property is new and either not part of a released version of grommet, or is experimental and the interface has not solidified.
Actual Behavior
When a grommet component is documented, the documentation appears immediately and there's no way to determine if it it's in a released version of grommet.  When a property is added to documentation, there's no indication that it's stable and will not change without a breaking change.
Design suggestions
Use the Grommet Tag at the component level to designate that a component is one of:

experimental - a component or property is in the stable branch and possibly in a released version of grommet, but its interface and capability is not yet finalized.  Changes to visual, behavior, and API are likely for experimental components or properties.  A Change to experimental components and properties will not be considered a breaking change.
pre-release - a component or property is ready for use in the stable branch of grommet, but is not yet available in a released version of grommet.  Minor changes to the component or property are possible without being considered a breaking change.
released - a component or property is ready for use and is available in a released version of grommet.  Changes to the component will be made in a backwards compatible manner or will be made as part of a major version update.  In the case of a breaking change, the change will be documented in the release notes.

Considerations

After writing the above, I'm wondering that maybe we don't need the *released tag as it's implied if neither of the other two are present.
It would be nice to have a small Tag to use for experimental or pre-release properties and the "normal size" tag at the component level.
It would be nice to be able to set the color on tags so we can use different colors for the tags, like the red explicit tag in Apple Music for experimental tags.
We will need a docs page with describing the meaning of the tags similar to the above.

Design investigation underway. Need a dev for help in implementation.


Make data streams truly asynchronous

Describe the bug
The three types of streams in smithy-swift that are used for event and data streaming currently share an implementation of readAsync(upToCount:) that is not truly asynchronous; instead it polls its internal storage continuously to see if it has data and then returns it to its reader.
This caused 100% CPU usage on one core while streaming, since the polling loop ran continuously.  It was documented in #974 and was then partially addressed in https://github.com/awslabs/smithy-swift/pull/552 by reducing the rate of polling with a small (1ms) asynchronous wait.
However, the problem is not completely addressed because the stream still polls for new data and CPU is wasted, even if at a lower rate than before.  This will become an issue when streaming on low-energy devices and/or in situations where the stream stays open for extended periods.  Polling also introduces a small latency where data has arrived but is not being handled until the next poll takes place.
To solve this issue, the data streams should be updated to be fully asynchronous; meaning that they do not resume a suspended read until new data is delivered to them.
Expected Behavior
While streaming and the stream is open but idle, essentially zero CPU should be consumed and the streaming client should not be executing.
Current Behavior
While streaming and the stream is open but idle, streams poll themselves for new data at ~1ms intervals and CPU is consumed at a rate of ~9% of one CPU core.
Reproduction Steps
Run Kinesis integration test under Instruments
Observe test progress vs. CPU consumption
Possible Solution
No response
Additional Information/Context
No response
AWS SWIFT SDK version used
Latest / main branch
Compiler and Version used
Xcode 14.3
Operating System and version
macOS 13.3.1

Related, as part of this we should also fix  BufferedStream.readToEnd. https://github.com/awslabs/smithy-swift/blob/main/Sources/ClientRuntime/Networking/Streaming/BufferedStream.swift#LL75C17-L75C26
Currently, readToEnd is sync and performs a while loop that may hog the CPU. This should be async and call readAsync in its implementation. In-order to make readToEnd async, we'll need to remove equatable conformance of models https://github.com/awslabs/aws-sdk-swift/issues/898.

An asynchronous readToEndAsync() method had been added to the Stream protocol and used where possible.  More work will be required to eliminate all use of the non-async version.

#1020 & #1022 should be perfomed as follow-up to this work.

Shipped in AWS SDK for Swift 0.18.0


Duplicate headers shown when using mod_proxy_fcgi

When using mod_h2, Chrome receives duplicate headers, from everything served via mod_proxy_fcgi (using event MPM).
Double cache-control lines, double expires fields, double strict-transport-security, double x-powered-by etc.
The problem breaks a webpage when content-encoding gzip is added, as Chrome will think the site is double encoded with gzip (ERR_CONTENT_DECODING_FAILED), which is not the case.
Configuration:
<FilesMatch "\.php$">
    SetHandler "proxy:unix:/run/php-fpm.sock|fcgi://localhost/"
</FilesMatch>

Ok, I would like you to try two things:

Enable H2SerializeHeaders on on your server and see if the problem persists
Enable LogLevel h2:trace1on the server and make such a duplicate header request. Please mail me the relevant parts of logs/error_log at icing(at)apache.org (since they might contain sensitive information, better not attache them here...)

Thanks!

H2SerializeHeaders on fixed the problem, thanks. Sent you an e-mail, when logging is on, and serialization is off.

Thanks, I see in the log that a filter of mod_h2 is installed twice where it should only be there once. I setup a php-fpm and tried to reproduce the bug, but no success. Anything else noteworthy in your config? Some other filters configured?

Using Apache 2.4.16. mod_h2 in the config is referenced only once. Using this config:
LoadModule h2_module modules/mod_h2.so
H2Engine on
H2Direct on
H2HackMpmEvent on
Using 0.8.0 of mod_h2, apache and mod_h2 is packed as a Gentoo Linux ebuild. If I will have some time, I'll try with stock apache and stock mod_h2.

Hmm, checking my code. A apache hook seems to be called twice which I have not understood. Can I ask you to send me a log with

LogLevel h2:trace2

again (serialize off)? Thanks!

Sent you the e-mail.

Can you check the v0.8.1 if it fixes the duplicate header problem? Thanks!

Yes, duplicate headers gone with 0.8.1. Thanks!


feat: units of polynomial rings

We proved that a polynomial is a unit if and only if all of its coefficients are nilpotent, except the constant term which is a unit.
Co-authored-by: Cyprien Chauveau<EMAIL_ADDRESS>Co-authored-by: Lucas Pouillart<EMAIL_ADDRESS>
I can backport this to mathlib3 if needed.

Otherwise LGTM.

Thank you!

Is there anything else that I should do concerning this PR?

@semorrison I don't see any reason not to merge this, but I'm not doing a maintainer merge in case you wanted to wait.

Thanks and congratulations for your first PR! :tada:
maintainer merge

bors r+


202307-notebooks Template amends

Added some suggestions on the title structure and on the introduction content. Also added a status check to the Druid initiatlization, and an additional Markdown cell for Kafka. Also added a supplementary section for other bits someone might want in their notebook.

This PR has:

[x] been self-reviewed.
[x] been tested in a test Druid cluster.

@sergioferragut @techdocsmith I added some little bits to the template - like a status check.

I've updated the template with some common suggestions from @vtlim and @writer-jill

I pushed an update with a few changes. I changed the heading "Initialize Python" back to "Initialization" because in my tutorial I'm initializing more than just Python.


scroll to scenarios list

DESCRIPTION
This PR allows scrolling over scenarios list preventing the scroll of the whole sidebar. The "Create a new scenario" button and filters on top should be visible all time.
JIRA
https://vizzuality.atlassian.net/browse/LANDGRIF-155?atlOrigin=eyJpIjoiYWI2OTY1MDRhNmNkNGMyNzk4OTVlYzE3ZjY2ZWRiMjciLCJwIjoiaiJ9
TESTING
https://landgriffon-client-git-landgrif-155-add-scro-7cf1e1-vizzuality1.vercel.app/analysis?collapsed=false&scenario=actual-data&sortBy=updatedAt

Here you can see how it looks in Chrome for Windows. It may need a overflow hidden or something like that

Also, if you can confirm with Andreia how it should be. Because if I'm not wrong the initial idea was to have an infinite scroll, so instead of load everything you have to load first some of them, and when you scroll load more using the pagination in the API.


The confirmation of the registration don't send via smtp.gmail.com

I followed installation from guide on the main site of the project. After installing server I couldn't create account, because I hadn't got confirmation emails. I use smtp.gmail.com. In the logs the servers response was:
[530-5.5.1 Authentication Required. Learn more at 530 5.5.1 http://mail.google.com/support/bin/answer.py?answer=14257 ffa3y7ap9sgytsh1]

After small research I did one small dirty hack: I placed my login and password from smtp in the confimations/models.py:
Before https://github.com/zulip/zulip/blob/master/confirmation/models.py#L95:
        send_mail(subject, body, settings.DEFAULT_FROM_EMAIL, [email_address])

After:
        send_mail(subject, body, settings.DEFAULT_FROM_EMAIL, [email_address],
                auth_user='user_name', auth_password='password')

After my fix sending via smtp.gmail.com works fine.
Offtopic. I had to turn option Allow less secure apps in my google-account to be able to send emails. Maybe this information will be useful to someone:

In https://myaccount.google.com
select Sign-in & security
find "Allow less secure apps: OFF"
turn it on

This is because the EMAIL_HOST_PASSWORD  is actually loaded from the secrets file rather than the settings file (https://github.com/zulip/zulip/blob/master/zproject/settings.py#L915).
Add email_password to the secrets file and it will start working without any hacks.

Oh, it make sense. But it's strange that there is an option for the password in /etc/zulip/settings.py


Barcode.Create width argument doesn't scale actual barcode

The Barcode.Create method doesn't actually scale the barcode if the width is changed, it only changes the width of the bitmap which also results in cropping when a small width is entered with large text.

Hi,
Thank You For your Code. +1:
This has been fixed.


ERROR: -1106, Parameter 'timeInForce' sent when not required

getting  this error when placing binanceordertype  = market
BinaCPP::send_order( "ADAUSDT", "BUY", "MARKET", "GTC", 30 , 0,   " ",0,0, recvWindow, result );

Can you take a look at my issue?


Initialize v0.18

Version bump to start 0.18.0 development.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.71%. Comparing base (c0e97b0) to head (b99b290).
Report is 17 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1775      +/-   ##
==========================================
- Coverage   84.11%   81.71%   -2.41%
==========================================
  Files         198      176      -22
  Lines       22241    12315    -9926
  Branches     4687     3020    -1667
==========================================
- Hits        18709    10063    -8646
+ Misses       2610     1711     -899
+ Partials      922      541     -381

Flag
Coverage Δ

py-unittests
81.71% <ø> (-2.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 66 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


Live-7097: Deflakify Cosmos Tests

📝 Description

Add Cosmos test for Windows tests back in (ran the CI job multiple times with no failures at the previous point of flakiness)
Added types to Staking modal currency objects
Add MOCK mode back in to use consistent mocked API calls, countervalues, etc
Remove unnecessary osmosis accounts
Add Cosmos to mocked on ramp providers

❓ Context

Impacted projects: UI Tests, Staking modal
Linked resource(s): https://ledgerhq.atlassian.net/browse/LIVE-7097

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/generate-screenshots

/generate-screenshots

/generate-screenshots

Yes it's very frustrating, the network fees seem pretty consistently 0.0025 atom on the CI, but sometimes 0.008484 (or something) locally. I'd like to understand why it's happening but as a quick fix this will do (and the network fees are fake so it's not too big a deal to omit for now)


[ACME] Add RFC2136 DNS Provider

What this PR does / why we need it:
In our datacenter we do not use any of the currently supported DNS providers. With this pull request I added  support for the DNS RFC2136 provider. An example configuration is also included.
Special notes for your reviewer:
What do you think of that? Is there anything missing? It would be great if this could be merged.
Release note:

Add RFC2136 DNS Provider

@munnerz anything we can do to help on this?

I've issued a PR to @simonfuhrer which would rebase it and possibly fulfil the previous requirements from the reviewer.

/unassign

Closing in favour of #661


feat:  implement opentelemetry for distributed tracing

What this PR does / why we need it:
This pr implements opentelemetry codes according to this proposal.
Parent context and OTEL endpoint are passed through env(TRACE_PARENT, OTEL_EXPORTER_OTLP_ENDPOINT)
Result is like below

relevant PRs

proposal docs
chaos-runner
chaos-operator

Checklist:

[ ] Fixes #
[ ] PR messages has document related information
[ ] Labelled this PR & related issue with breaking-changes tag
[ ] PR messages has breaking changes related information
[ ] Labelled this PR & related issue with requires-upgrade tag
[ ] PR messages has upgrade related information
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] E2E run Required for the changes

邮件已收到，我会尽快阅读并回复，谢谢

This is a great start however I don't see any place where we are marking span as error in case of failure, do we plan to do this in future iterations?

I will record errors like below
if err != nil {
	span.SetStatus(codes.Error, "operationThatCouldFail failed")
	span.RecordError(err)
}

But we have over 50 chaos faults, so it can be merged in the next PR (it is a time-consuming job)

Based on the experiment context it might be good to explore what span attributes might be relevant.

Does this mean adding a span attribute to help with future queries by attribute?

Lastly to be able to correlate logs with traces can we add traceID to logs?

sure, I will add it

Does this mean adding a span attribute to help with future queries by attribute?

Span Attributes can be useful for queries but also they can serve as additional context when reviewing the spans. Let's take an example, you get an http request, you might wanna log the relevant headers, the request body and the path similarly in context of the experiments it might be helpful to log the parameters for the experiment, maybe the targets and any other data you think that might be helpful when looking at an error trace :)

Thanks for your detailed comments @smitthakkar96 :) I am going to pave the foundation for collaborating with other contributors. Adopting a contrib package is also good idea

I updated contribute/developer-guide folder for using context.Context
context.Context makes context propagation automatically so i fixed all of the functions to add context.Context as a parameter.
Here is a screen shot of distributed tracing. It's a result of pod-delete chaos fault.


Update to Tokio 1.0

Update to Tokio 1.0, required for updating all the other dependencies of Routerify: (stream-pipe, routerify-query, routerify-cors, routerify)

Can you please send the PR to develop branch of async-pipe-rs repo?

Hello, do you think this PR could be merged and released ? The fact that async-pipe is not compatible with tokio v1 is currently blocking me from being able to update stream-body to http-body v0.4, which in turn blocks the update of routerify-websocket to hyper v0.14/tokio v1.

@rousan .. Any reason we can't get this merged. It's blocking a lot of number of upstream projects.


Requests - Several resources

An overview tab of your character sheet like the module tidy5esheet does would be need!
That would also give us the resources part where we can track things such as sorcery points or other stuff.
Another feature I'd like to see is an "always prepared" version of preparing spells for classes that just learn the spells and are not prepared casters.

As well as a quantity tracker for your items :D

As well as a quantity tracker for your items :D

This, along with further automatic resource consumption is planned for the next release 🙂
The resources part can certainly be added, but I have slightly different plans regarding preparation modes. Level Up will soon allow you to have several spell books, and there will be various settings for preparation included as part of that.

Resources are included in the upcoming 1.0.0 release. Automatic resource consumption is also included in that release, so I think this can be closed.


Make it possible to clear/disable templates cache

What problem does this feature solve?
When using <script type="x-template"> for providing template source - it get cached (https://github.com/vuejs/vue/blob/cfd73c2386623341fdbb3ac636c4baf84ea89c2c/src/platforms/web/entry-runtime-with-compiler.js#L12). When using same elements for templates like #order-template on different pages like /orders/1, /orders/2, both components are rendered with first compiled template.
Even when using different template ids, their content is cached which is unnecessary and leads to memory bloat: it caches inner html which is fast to fetch.
Proposed feature will give ability to opt out template caching.
What does the proposed API look like?
Vue.clearAllCaches() or Vue.templateCache = false.

Just wondering, why /orders/1 and /orders/2 have different templates instead of use logic directive in same template?

That's not how templates are intended to be used. The same component should always have the same template, you should use Vue's own logic directives to display different content based on data.

Thank you, I'll try this.
What if I have localized templates (template with same id will have different translations), and want to give ability to switch language without full page reload?

@JounQin some features are available only for premium users, so we want some parts of templates not be visible even in page source.

@yyx990803 what if cached wrapper will take optional cache argument to set cache object explicitly, and in this place Vue.templateCache will be passed? This way template cache will be accessible from user-space and can be cleared manually.

The template cache is something we do not intend to expose to the user, nor should your app logic rely on it. The template self is a language to express dynamic information and you should work within the template, not outside of it.
If you don't want to expose your template source, you should use a pre-compile step, e.g. with vue-loader.

@yyx990803 thank you! I've just checked vue-loader, it seems to work only with webpack.
Can you please advise, how should this be done: server renders vue template into <script id='some-template'> with some translations (eg., action names, labels, etc.). When user changes locale, server renders new content (same markup, different translated phrases) into the same script tag. This way, vue will continue render this template in old locale. The only way i see is to use locale suffix in all template ids, but this will require having global js variable to be used in template: "#some-template-#{window.LOCALE}". This looks dirty to me.

Are you saying when changing locale the page does not reload, but simply fetches new templates via Ajax and updates the <script> nodes?

Maybe you need https://github.com/kazupon/vue-i18n

@yyx990803 yes, we use turbolinks, it replaces body with one fetched via xhr.
@Akryum thank you! If i get i right, it's lib for client-side translations. We are not able to move translation logic to frontend for now, it's out of scope of current tasks.

@yyx990803 one more issue we've faced is rendering old templates after deploying updates: server renders updated vue template but it's not applied until user reloads page.

I want to create more complex widgets/components.
I've describe one of them here: https://forum.vuejs.org/t/how-to-create-reusable-component-with-external-plugin-behavior-logic/28101
I did it with dynamic templates and i've also notice the issue with template cache.
But if on call I change some prop value of this component it works fine...
Is there gonna be some core problem ?

ytetet

I still consider this a bug. When doing "new Vue({template:'#template1'.." and then purposefully load a different page where #template1 has a different content, doing "new Vue({template:'#template1'.." should respect that and not still use the old template content. This is especially weird when using Vue as an on demand tool when extending foreign single page apps.
My workaround for now is using "template: $('#template1').text(),"


Switching from rexie to idb

idb is a lower lever wrapper over the indexeddb, we might want to switch to it rather than use rexie to have more direct control over callbacks and such

rexie doesn't have migrations mechanism


Get-MDEInvestigationPackage playbook retrives SAS URI but returns "expired token"

Describe the bug
A clear and concise description of what the bug is.
This playbook https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Get-MDEInvestigationPackage
Is ran against a Sentinel Incident and it is able to retrieve the get investigation package download URI. However when I navigate to the URL I get a JSON error Message: "Expired token"
To Reproduce
Steps to reproduce the behavior:

Go to 'Sentinel Incident'
Click on 'Run Playbook (Preview)'
Select Get-MDEInvestigationPackage and click "Run"
See error

Expected behavior
A clear and concise description of what you expected to happen.
URL from playbook is supposed to download the investigation package
Screenshots
If applicable, add screenshots to help explain your problem.
See above
Desktop (please complete the following information):

OS: Windows 11
Browser Firefox
Version 104.0.2

Additional context
Add any other context about the problem here.
Permissions as per readme were granted to managed identity.

Hi @kevelife - we are currently investigating why there is error with expired token. in meantime you can utilize HTTP action as a workaround

Update - API token to get investigation package expires couple of minutes after generating, so if you don't click on the link immediately, you will get "token expired" notification.

@BenjiSec - Thaks for the prompt response.
@applefacts - Closing this incident as its by design and please feel free to reopen if you need any further information on this.
Thanks

Update - API token to get investigation package expires couple of minutes after generating by design, so if you don't click on the link immediately, you will get "token expired" notification.

Hi @BenjiSec, I am clicking the package URL immediately and I am not waiting for it to expire.

The token life is definitely too short for this use case - I've managed to download it clicking refresh on the incident page only during the second run (2 minutes); after the first, 5 minutes run, the token was already expired. I can see that the token life is something between 4-5 minutes in total, please correct me if I'm wrong. Anyway, as I said, it is way too short for the production use.


Show your Work for the MTR Map

https://www.mtr.com.hk/archive/en/services/routemap.pdf

Make Perfect for 2020s or 2000s!

GitHub Issues is used for people giving suggestions or provide bugs, not for showing your work!!!


Can't use underscore as part of request path variables

Let's define a new service called FooService:
from venom.rpc import http, Service

class FooService(Service):
    class Meta:
        name = 'foo'

    @http.method('./{obj_id}', auto=True)
    def get_obj(self, obj_id: int) -> int:
        return obj_id

Issue is that whenever I visit an URL corresponding to get_obj view, e.g. http://<IP_ADDRESS>:8000/foo/1234, it always returns 0 instead of the number I put in the URL.
It's because, json_name of obj_id field in auto-generated request class is objId instead of obj_id. But, value of kwargs inside the auto-generated view is {'part_id': '1234'}.
I got following values after putting a breakpoint just before line 45:
>>> method.http_field_locations()
{<HTTPFieldLocation.HEADER: 'header'>: set([]), <HTTPFieldLocation.QUERY: 'query'>: set([]), <HTTPFieldLocation.PATH: 'path'>: set(['obj_id']), <HTTPFieldLocation.BODY: 'body'>: set([])}
>>> http_request_path.field_decoders
{('obj_id', 'objId'): functools.partial(<function URIString._cast at 0x7f7a776361e0>, <class 'int'>)}
>>> kwargs
{'obj_id': '1234'}

Following code also does not work, because json_name becomes objid and field name is objId:
class FooService(Service):
    class Meta:
        name = 'foo'

    @http.method('./{objId}', auto=True)
    def get_obj(self, objId: int) -> int:
        return objId

from venom.rpc import http, Service

So, I'm going to use objid instead of obj_id in my code for the time being, as it works:
from venom.rpc import http, Service

class FooService(Service):
    class Meta:
        name = 'foo'

    @http.method('./{objid}', auto=True)
    def get_obj(self, objid: int) -> int:
        return objid

@lyschoening I tried following solution after @sgalkina's suggestion and it works.
from venom import Message
from venom.rpc import http, Service

class GetObjRequest(Message):
    obj_id = Int32(json_name='obj_id')

class FooService(Service):
    class Meta:
        name = 'foo'

    @http.method('./{obj_id}', Request=GetObjRequest)
    def get_obj(self, obj_id: int) -> int:
        return obj_id

I think we should disable camelCasing of variable names in URL pattern for request path to make life easy.

@psjinx Yes, that workaround works, but I'll fix the original approach too.


add global attributes

attributes attached to the whole model, rather than attributes attached to specific entities
these can be used for many things, e.g. lat long positioning

done


How to use templates

Hi! I would like to know how to use a template-type message in this format.  And how do I change the text inside the pipes?

To use the templates you will need:

The name of the template
The language of the template
The Template class
Any other class to fill the variables (pipes) and the buttons

The code should look somthing like this:
// Ignoring all the setup configurations
const { Types } = require("whatsapp-api-js");
const { Template, BodyComponent, ButtonComponent, Text } = Types;

const message = new Template(
  "the_name_of_the_template",
  "br", // The language of the template, I'm assuming it will be Brazilian
  new BodyComponent(
    new Text("First variable goes here"),
    new Text("Second variable goes here")
    // There are more supported types for the body, such as DateTime
  ),
  new ButtonComponent(
    "quick_reply", // This is the type of the buttons, in your case is quick_reply
    "first_button_id",
    "second_button_id"
  )
);

The button's ids are used to handle the user's reply as follows:
function onMessage(phoneID, phone, message, name) {
  if (message.type === "button") {
    const id = message.button.payload;
    // This id will be the same as the ones we defined before
  }
}

And that's it! Feel free to ask any other question.
Template documentation

Hi friend! Thank you  =)


wire-desktop: add a proper throw

Motivation for this change
cc @toonn. I guess this was the one little detail we forgot https://github.com/NixOS/nixpkgs/commit/854b43404f5c3a62ca1aeafc34a6860980fb3dc1.
Things done

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

[ ] 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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Well, the practical issue was worked around by or "" in the version part already, I believe.

Huh I see @vcunat. Might as well do it like this I guess, also realizing I forgot to do it for version.

👍 Looks much better to me than the workaround. (Sidenote, throwSystem's not documented in the nixpkgs manual.)

+1 Looks much better to me than the workaround. (Sidenote, throwSystem's not documented in the nixpkgs manual.)

throwSystem is something that's defined here and also the electron expression.
But I don't think the detail @vcunat explained at https://github.com/NixOS/nixpkgs/commit/854b43404f5c3a62ca1aeafc34a6860980fb3dc1 and https://github.com/NixOS/nixpkgs/pull/65917#issuecomment-517986419 is.

Hmm, the definition for throwSystem has actually been proliferated throughout nixpkgs. Can we propose it for inclusion in lib or a more appropriate place?


Add missing semicolon

Noticed a missing semicolon when I was converting this file to a format that Flow can understand

Sweet thanks


render all values now stacks values

With the new pipeline, render all values stacks up so everything is illegible:

Previously the text that fell in the next slot was covered by the next box, but now we need to do that artificially.
It looks like there was some code trying to do something like this, but I can't understand it:
https://github.com/NatelEnergy/grafana-discrete-panel/blob/master/src/module.ts#L669

fixed in 0.0.7


Border Bouncy Physics

How to make entities does not bounce from border bcz @Megabyte918 is changing server code so i cant able to make changes
I am sorry for making lot of issues
This is a part of Mobile Physics (if you have time just add this to GamerServer.js)

Do you mean that you want to make a config option for bounce and make a pull request for it, but by the time you finished coding it, there's a new commit and merging isn't possible due to conflicts?

Replace this code with this:
if (!this.config.mobilePhysics) {
    var r = cell1._size / 2;
    if (cell1.position.x < this.border.minx + r || cell1.position.x > this.border.maxx - r)
        cell1.boostDirection.x =- cell1.boostDirection.x;
	if (cell1.position.y < this.border.miny + r || cell1.position.y > this.border.maxy - r)
	    cell1.boostDirection.y =- cell1.boostDirection.y;
}

👍

ok!

@ZfsrGhS953 Code isnt working!

Opsss my mistake the code works thanks @ZfsrGhS953


[fix] cms page sequenced_filename skip_validate_seq_filename

Coverage decreased (-35.3%) to 48.697% when pulling 9cba05fec68de53605fa63489a9070fbb7446a1c on fix-skip-validate-seq-filename into bc9ff65df933f1aa2243e407dadf8cfffea9c824 on master.


mitochondrial inheritance phenotypes PMID:31582398

FYPO:0000906 | abnormal mitochondrion inheritance
need meiotic and mitotic terms
NEW abnormal mitochondrion inheritance during meiosis
synonym mitochondrial mixing during meiosis (author suggestion)
NEW normal mitochondrion inheritance during meiosis
increased mitochondrial segregation during meiosis (author suggestion)

Are these really during meiosis (the nuclear divisions), or during meiotic cell cycle?

Hmm, I thought meiosis because it's to do with what happens to the mitochondria at division. It feels correct to me.

but meiosis is defined as nuclear division, and mitochondria aren't in the nucleus

its what happens to the mitochondria during nuclear division.

you are right though
"during meiotic cell cycle" would be better as we should use the phase terms for during.

included a couple new grouping terms:
abnormal mitochondrion inheritance FYPO:0007274
abnormal mitochondrion inheritance during meiotic cell cycle FYPO:0007275
normal mitochondrion inheritance during meiotic cell cycle FYPO:0007276
normal cellular process during meiotic cell cycle FYPO:0007277
meiotic cell cycle ones have "during meiosis" in related synonyms
edit file: 4595eab9cbfee72ca0a5ff98d8d3c1ee1d1ac872
release: dc0e84f93ec4661e4b482ee0e97f8529ab864359


Make Add-Type open source files with FileAccess.Read explicitly (Fix #7914)

Fix #7914
Omitting the FileAccess attribute when constructing a FileStream with FileMode.Open makes the constructor default to FileAccess.ReadWrite, which is completely unecessary and inappropriate for Add-Type when compiling from source
PR Summary
This PR ensures that Add-Type explicitly opens source code files with only Read access
PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Change is not breaking
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[X] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[X] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@iSazonov done, not sure why the WebListener test fails though


added AbletonLinkDemo example along with AbletonLinkWrapper API

Added a new Examples project:
Examples/iOS/AbletonLinkDemo
Includes:

basic AKSequencer loop
empty AKSequencer extension to add Ableton link functionality
AbletonLinkWrapper API from https://github.com/kvacquier/ABLLinkSwiftWrapper
todo: need to add Ableton Link functionality to AKSequencer and test with loop

You accidentally committed a copy of AudioKit in the new project.  I think in Xcode there's a checkbox for "make copy of files" that you had on while dragging in the framework.


Poetry lock update

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.80%. Comparing base (80a5035) to head (a891a9e).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #219   +/-   ##
=======================================
  Coverage   90.80%   90.80%
=======================================
  Files          70       70
  Lines        2078     2078
=======================================
  Hits         1887     1887
  Misses        191      191

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


2.1: reorganize source code

In preparation for merging many other projects into this repo, this establishes a new source code organization which groups projects together based on subject matter.

src
├── DiagnosticAdapter
│   ├── README.md
│   ├── src
│   └── test
├── ObjectPool
│   ├── perf
│   ├── src
│   └── test
├── Primitives
│   ├── perf
│   ├── src
│   └── test
└── Shared
    ├── src
    ├── test
    └── testassets

Browse the new repo layout: https://github.com/aspnet/Extensions/tree/namc/reorg

:watch: depends on https://github.com/aspnet/BuildTools/pull/837 and https://github.com/aspnet/Extensions/pull/435

is it weird that we have test/Xyz living under src/Xyz as opposed to a parallel test/Xyz/?  Just seems weird to see src/Xyz/src

The thinking for this pattern is described here: https://github.com/aspnet/specs/pull/201. We're borrowing heavily from other dotnet repos which use this pattern in anticipation of 3.0 work, such as the addition of ref assembly projects.

Yeah @HaoK I don't like it either but others do it and the world hasn't ended 😄

Thanks for the sign off. This also depends on https://github.com/aspnet/BuildTools/pull/837. Can you also take a look at that?


Test case Azure Key Vault Linux Extension VM

The following test case validates the Azure Key Vault Linux Extension while creating the following resources:
-A resource group
-A VM
-A Key Vault
-Two certificates in the Key Vault
-Retrieval of the certificate's secrets through SecretClient class from the Azure SDK.
-Installation of the Azure Key Vault Linux Extension on the VM.
-Rotation of the certificates (After KVVM Extension has been installed)
-Asserts after the creation/installation of all of these resources.
All of the resources have been created by using the Azure SDK Python.

put the change in https://github.com/microsoft/lisa/pull/2889 into this PR

@LiliDeng LGTM. Eli has to complete it this week. Let's prioritize this PR.


Add new context argument to _get_responses method

Fixes https://github.com/dbt-labs/dbt-rpc/issues/116 (and https://github.com/dbt-labs/dbt-rpc/issues/113 I believe).
From the linked issue, a recent modification to the json-rpc parent JSONRPCResponseManager https://github.com/pavlov99/json-rpc/pull/122/files#diff-71ff9d558b2e51825f517c97faa2f119ab0aaf26aaff43e36731719017cce06eR75 class adds a new argument that is causing an error in the overridden version in the custom dbt-rpc ResponseManager class.
This PR essentially just adds in the same context argument to the _get_responses method, which is being called from the parent handle_request method.

@anubhavsharma515 Thanks for the fix!! I don't think this would resolve #113 but def resolves #116. I think internally we got over the issue by pinning a previous version of json-rpc. But this def should to be the way longer term.

This makes sense, need to debug the failing unit tests

@anubhavsharma515  Thank you so much for looking into this and update!! Just one last question and I am happy to merge after it is being confirmed!


Cannot save changes

Describe the bug
Cannot save changes when there's "errors".

A clear and concise description of what the bug is. If there's errors it wont let you save any changes to the file which obfuscation prevents this from editing the file.

To Reproduce
Steps to reproduce the behavior:

Open a jar
Have an error because of a obfuscation or make something error
Try saving changes

What do you mean it's "stupid" that you can't save with errors? That doesn't even make sense. Decompilers are great but they're not magic. There are some things that are representable in bytecode form that physically can't be represented in Java source code form making them literally impossible to recompile, and decompilers can't always output recompilable code even in the case that it's valid in both forms. Please read the documentation and learn how to use the assembler.

How am I suppose to edit something when I cant save it when there's errors from obfuscation stopping me from saving it?

https://www.coley.software/Recaf-documentation/use-assembler.html

Theres no other way to edit the code?

This assembler is confusing.

Not easily in it's obfuscated state. To recompile it you would have to fix the errors yourself which is probably easier said than done especially considering other classes and their obfuscated method and field names.

For reused variables stripping debug in the config would be useful.
Or runninf the jar through a deobf program first.

https://github.com/java-deobfuscator/deobfuscator potentially


python310Packages.flask-login: 0.6.2 -> 0.6.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.flask-login is: User session management for Flask
meta.homepage for python310Packages.flask-login is: https://github.com/maxcountryman/flask-login
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 0.6.3 with grep in /nix/store/q7xngc1f57jq477s89nmrklm84306nkm-python3.10-flask-login-0.6.3
found 0.6.3 in filename of file in /nix/store/q7xngc1f57jq477s89nmrklm84306nkm-python3.10-flask-login-0.6.3

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

16 total rebuild path(s)

16 package rebuild(s)

First fifty rebuilds by attrpath
apache-airflow
calibre-web
changedetection-io
flexget
octoprint
pgadmin4
pgadmin4-desktopmode
powerdns-admin
python310Packages.flask-appbuilder
python310Packages.flask-login
python310Packages.flask-security-too
python310Packages.sqlalchemy-continuum
python311Packages.flask-appbuilder
python311Packages.flask-login
python311Packages.flask-security-too
python311Packages.sqlalchemy-continuum

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q7xngc1f57jq477s89nmrklm84306nkm-python3.10-flask-login-0.6.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.flask-login https://github.com/r-ryantm/nixpkgs/archive/a337c356125cd9fd1409d00fd06beaefc5dc0943.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a337c356125cd9fd1409d00fd06beaefc5dc0943#python310Packages.flask-login

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q7xngc1f57jq477s89nmrklm84306nkm-python3.10-flask-login-0.6.3
ls -la /nix/store/q7xngc1f57jq477s89nmrklm84306nkm-python3.10-flask-login-0.6.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

2 packages marked as broken and skipped:

python310Packages.flask-appbuilder
python311Packages.flask-appbuilder

2 packages failed to build:

apache-airflow
powerdns-admin

12 packages built:

calibre-web
changedetection-io
flexget
octoprint
pgadmin4
pgadmin4-desktopmode
python310Packages.flask-login
python310Packages.flask-security-too
python310Packages.sqlalchemy-continuum
python311Packages.flask-login
python311Packages.flask-security-too
python311Packages.sqlalchemy-continuum

Maintainer pings
cc @abbradar for testing.

Result of nixpkgs-review pr 265777 run on x86_64-linux 1

4 packages marked as broken and skipped:

python310Packages.flask-appbuilder
python310Packages.flask-appbuilder.dist
python311Packages.flask-appbuilder
python311Packages.flask-appbuilder.dist

3 packages failed to build:

apache-airflow
apache-airflow.dist
powerdns-admin

24 packages built:

calibre-web
calibre-web.dist
changedetection-io
changedetection-io.dist
flexget
flexget.dist
octoprint
octoprint.dist
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
python310Packages.flask-login
python310Packages.flask-login.dist
python310Packages.flask-security-too
python310Packages.flask-security-too.dist
python310Packages.sqlalchemy-continuum
python310Packages.sqlalchemy-continuum.dist
python311Packages.flask-login
python311Packages.flask-login.dist
python311Packages.flask-security-too
python311Packages.flask-security-too.dist
python311Packages.sqlalchemy-continuum
python311Packages.sqlalchemy-continuum.dist