Update beta.kubernetes.io/os nodeSelector to kubernetes.io/os

As per https://v1-14.docs.kubernetes.io/docs/setup/release/notes/ beta.kubernetes.io/os has been deprecated and will be completely removed in k8s 1.18. That said, please update beta.kubernetes.io/os nodeSelector to kubernetes.io/os in the antrea yml file.

Hi all, I would like to complete this issue!
Thanks, Dilan

@dilan-js do you still intend to take a stab at this? Thanks.

No update, so re-assigning the issue to myself to make sure it gets taken care of in time for the 0.5.0 release.


PointerExited event not always fired (when pointer captured)

If I mouse over a control (so PointerEntered is fired), press, then drag outside the control, the PointerExited event does not fire in at least some cases. I didn't spend a long time testing but it definitely occurs when ManipulationStarted is triggered (and maybe even if not - I didn't test it). It would be useful if we could guarantee the PointerExited event fires. This is important because, for example, we might change the cursor or control style when the pointer is over a specific elements etc, and without this event firing the change is permanent. (It would also be useful if controls had IsPointerOver and IsPointerPressed properties, but that's another issue). The PointerExited event should probably fire when the pointer is released outside the control and also if the control is unloaded before the pointer leaves the control. I assume all built-in controls use the PointerEntered/Exited events for transitioning to/from the PointerOver visual state, so this bug potentially effects that as well.
Also, it would be nice if PointerReleased was always called after PointerPressed, rather than having to listen to PointerReleased, PointerCanceled and PointerCaptureLost (I think all 3 are necessary currently), but maybe that's necessary due to the design of pointer capture and manipulation.
I've put together the following workaround which provides the desired behaviour (if you listen to its IsPointerOverChanged event), but it would be good if I didn't need this workaround - https://github.com/Pictureflect/pictureflect-parital-source/blob/master/PictureflectPartialSource/PointerOverManager.cs.

PointerExited should always fire if PointerEntered did, if it doesn't that's a bug.

Starting with Windows 8.1, PointerExited is fired for any case where the pointer had at one time fired a PointerEntered event, but some UI state change happens where the pointer is no longer within that element. This includes cases where the whole element disappears. And if the pointer is now over a different element because a previous element disappeared, that element fires PointerEntered, even if the pointer never moves. Elements that set their Visibility to Collapsed programmatically is one way that elements might disappear from UI, and the Windows 8.1 behavior accounts for this and will fire PointerExited for the Collapsed element and PointerEntered for the newly revealed element.

https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.uielement.pointerexited

@benstevens48 definitely a bug if these events aren't paired. Can you give more detail on your specific configuration for this? I'm unable to reproduce this so far.
To reproduce I tried setting up something like this:
    <StackPanel Padding="100" HorizontalAlignment="Center">
        <Button Height="200" Width="200" PointerEntered="IncrementPointerEntered" PointerExited="IncrementPointerExited"/>
        <TextBlock x:Name="EnteredCount"></TextBlock>
        <TextBlock x:Name="ExitedCount"></TextBlock>
    </StackPanel>

        private int _entered = 0;
        private int _exited = 0;

        private void IncrementPointerEntered(object sender, PointerRoutedEventArgs e)
        {
            _entered++;
            EnteredCount.Text = "PointerEntered: " + _entered.ToString();
        }

        private void IncrementPointerExited(object sender, PointerRoutedEventArgs e)
        {
            _exited++;
            ExitedCount.Text = "PointerExited: " + _exited.ToString();
        }

I can never get the event counts to drift apart. Can you clarify what more is essential for the repro?

@chrisglein - it actually seems to be related to pointer capture. Try this instead.
<Grid Height="200" Width="200" Background="Beige" PointerEntered="IncrementPointerEntered" PointerExited="IncrementPointerExited">
                <Border Width="100" Height="100" Background="Red" PointerPressed="Border_PointerPressed" PointerReleased="Border_PointerReleased"></Border>
            </Grid>

        private int _entered = 0;
        private int _exited = 0;

        private void IncrementPointerEntered(object sender, PointerRoutedEventArgs e) {
            _entered++;
            EnteredCount.Text = "PointerEntered: " + _entered.ToString();
        }

        private void IncrementPointerExited(object sender, PointerRoutedEventArgs e) {
            _exited++;
            ExitedCount.Text = "PointerExited: " + _exited.ToString();
        }

        private void Border_PointerPressed(object sender, PointerRoutedEventArgs e) {
            System.Diagnostics.Debug.WriteLine("pressed");
            var button = sender as UIElement;
            button.CapturePointer(e.Pointer);
        }

        private void Border_PointerReleased(object sender, PointerRoutedEventArgs e) {
            System.Diagnostics.Debug.WriteLine("released");
            var button = sender as UIElement;
            button.ReleasePointerCapture(e.Pointer);
        }

Click on the red square then drag outside the beige container and release. This is presumably due to the way pointer capture works. In my opinion the PointerExited event still needs to fire at some point though. Either when the pointer leaves the grid or when the pointer capture is released outside the grid (but in that case it would differ from the behavior of adding all the events to the containing grid itself so I'm not sure which is best - possibly you could change the behavior of PointerExited not to fire until pointer capture is lost even on the element that has pointer capture, because in a sense the pointer is still inside the element until then).

Gotcha. Thanks for the details on that @benstevens48, much appreciated!
Will require WinUI3 to complete (this code is not in WinUI2), tagging as such.

@chrisglein - it turns out there are other scenarios when the PointerExited event does not fire. I have discovered this while trying to implement a drag and drop. Suppose we have a FrameworkElement A that undergoes the follow events:  PointerEntered, PointerPressed, pointer capture is taken by some other FrameworkElement B outside element A, then the pointer is moved outside element A, then the pointer is released. The pointer exited event for element A is never fired. it should probably be fired at the point pointer capture is taken by element B.
I would also like to confirm that in the previous scenario where a sub-element captures the pointer, it would make most sense for PointerExited not to fire when the pointer moves outside the sub-element if the element has pointer capture. The PointerExited event for the sub-element should fire on pointer capture lost instead (if the pointer is not over the sub-element at that point), This it because PointerMoved events still fire for the sub-element (which is essential for e.g. dragging), and one would expect PointerExited to fire after any PointerMoved events.
Finally, I would like to mention that there are serious problems with the built-in drag and drop functionality regarding events like pointer released etc. It seems that at the time when dragstarting occurs, pointer capture is taken away from the app entirely. So even if you add pointer pressed and pointer released event handlers to the core window, you will not see a pointer released event when the drag completes (and possibly this includes when the dragstarting is canceled - I can't remember). In my opinion, it ought to be possible to determine when the pointer is released. I struggled for a very long time working out the sequence of events and what is being given pointer capture (if you add CanDrag to an element then it will be given pointer capture on PointerPressed or something which will then be taken away on dragstarting), and which events fire and which events are missed out, and along with trying to deal with this bug #1540, which occurs if you set CanDrag to false between PointerPressed and DragStarting, it ended up taking my entire day and was somewhat frustrating! At the very least it would be nice if the sequence of pointer events that occur when doing drag and drop could be documented.

Also, this doesn't just apply to mouse (I don't know if the 'area-Mouse' label added to this issue includes touch as well), because the PointerEntered and Exited events will fire for touch too (when in contact).

Suppose we have a FrameworkElement A that undergoes the follow events: PointerEntered, PointerPressed, pointer capture is taken by some other FrameworkElement B outside element A, then the pointer is moved outside element A, then the pointer is released. The pointer exited event for element A is never fired.

This behavior is called out in the docs:

If another element has captured the pointer, PointerExited won't fire even if the captured pointer leaves an element's bounds. For more info on pointer capture, see CapturePointer or Mouse interactions.

@Felix-Dev OK, but we need an event that is guaranteed to fire after pointer entered else how are we supposed to do things like set a different cursor or visual state on hover? If pointer exited never fires then the cursor or visual state will be changed permanently.
The quote you mentioned seems to be in contradiction to the following quote lower down the page.

Starting with Windows 8.1, PointerExited is fired for any case where the pointer had at one time fired a PointerEntered event, but some UI state change happens where the pointer is no longer within that element. This includes cases where the whole element disappears. And if the pointer is now over a different element because a previous element disappeared, that element fires PointerEntered, even if the pointer never moves. Elements that set their Visibility to Collapsed programmatically is one way that elements might disappear from UI, and the Windows 8.1 behavior accounts for this and will fire PointerExited for the Collapsed element and PointerEntered for the newly revealed element.

I don't think there is a contradiction here:

Starting with Windows 8.1, PointerExited is fired for any case where the pointer had at one time fired a PointerEntered event, but some UI state change happens where the pointer is no longer within that element.

The case mentioned in the docs above is about another element capturing the pointer, and not one of the UI state changes listed in the paragraph you are quoting from.

Ok, well regardless of what it says in the docs there needs to be a reliable way of changing visual state and cursor on hover without the change being permanent.

Is this going to be fixed in WinUI 3? This is a serious flaw regardless what docs say.

I can confirm this happens (PointerExited event not fired), even when the mouse is NOT captured.
I have a grid on the left and a grid on the right.

I capture PointerExited on the left. It's sent probably 5% of the time. The workaround for me is to capture PointerEntered for the right pane. It's quite sad.

Need to check this has been fixed in WinUI3. Would also be good if it was fixed in system XAML.


Allow node type with different name than Connection type

Hello, we have following connection types defined in our GraphQL schema:

type Member { ... }

type EntityOwnerEdge {
    cursor: String!
    node: Member
}

type EntityOwnerConnection {
    edges: [EntityOwnerEdge!]!
    pageInfo: PageInfo!
}

these conforms to the Relay Cursor Connections specification. However, using this schema with Spring GraphQL results in following error, produced by SchemaMappingInspector:
No node type for EntityOwnerConnection.
Upon inspecting the code it is obvious, that the inspector expects every connection type FooConnection to have edge types with  node field of type Foo. But the Relay Connection spec doesn't say anything about the names of the node types (nor edge types), only about the name of connection types. Imho it can be merely considered a good practice, but it shouldn't be something that is enforced through hard assert. This expectation also isn't explictly stated anywhere in Spring GraphQL documentation. Am I missing something?

Hello @njuro, thanks for reaching out.
You are pointing at the schema inspector feature, which checks for the presence/absence of type definitions and corresponding data fetchers.
Is your application manually registering such types and data fetchers? Your code snippet is showing the schema part, but I'm wondering what's actually done by the application for this. As far as I remember, our ConnectionTypeDefinitionConfigurer will only automatically register infrastructure for connection types that follow this convention, so in that sense maybe the warning is correct because the relevant data fetchers are not registered?
Ideally, a minimal sample application should help us discuss this issue. Can you provide one?

Hi @bclozel thanks for the swift reply!
We are actually using Netflix DGS framework and right now are trying to migrato to the new starter (com.netflix.graphql.dgs:graphql-dgs-spring-graphql-starter) which integrates with Spring GraphQL. The DGS calls the schema inspector here. Are you suggesting the problem may be with the way DGS is using the inspector? Should I open an issue with them?

From what I can see, DGS is also following the type+connection/edge/node convention. So, back to my question: how are those types supported in the first place in your application?

We are writing the schema manually and then generating the objects with dgs-codegen plugin. However, we are not using the @connection directive, we define the connection, edge and node types by hand. It wasn't a problem until now and from what I can see, the DGS docs also don't indicate that you have to follow this naming convention, it just provides a tool to autogenerate these types for you if you want.

If typed and data fetchers are present in the graphql engine at the time of schema introspection, then this should not be raised as a warning.
I'm probably missing something though. Could you share a minimal sample application so E can have a look, please?

I think I see the problem. At the moment, the schema inspection derives the paginated type from the ~Connection type name and expects those to be aligned, which in this case they are not. We can improve this by getting the actual type name of the node field in the ~Edge type.

Thank you @rstoyanchev, that's exactly the problem! Sorry I didn't make myself clear at first.


Resolve conflict with Simulink

Please can you resolve a blocking conflict with Simulink.
Steps:
Unpack attached zip (though essentially the same as either metrics example)
Open Docker, then in folder: docker-compose up -d
Open 23b & install toolbox 1.7.0.
Run myExample.m (or either metrics example) -> should be fine
Then open Simulink -> should throw error
Restart 23b
Open Simulink -> should be fine
The run myExample.m (or either metrics example) -> should throw error
untitled1.zip

This seems to be caused by a conflict of different versions of abseil_dll.dll


Epochs

Epochs are defined as being the bounds between an event being fired, and all subsequent events, db updates, subscriptions, and renders being run. This is inherently a little bit of a fuzzy concept, as there may be events added to the re-frame event queue by async network activity which becomes part of the epoch, even though it is logically separate. For developing and debugging purposes to show the separation of events this is good enough.
How do we know when we are in a new epoch? How do we know when it is finished? Just based on events? Should there be something fired at the end of the render?
We also want to show in the trace view the bounds of each epoch.

I am really interested in tackling this issue, because surfacing the most important information and collapsing everything else would really change the whole debugging experience.
Is there some people who might be familiar with the internals of re-frame that you could suggest I reach out to to have a discussion about this with?


Host example pages on gh-pages

To get better user experience (for repo users) I recommend to host example directory on gh-pages.
I think that way increase users of this package/repo

Something like this https://vanng822.github.io/pagination/ @shavidzet

Something like this https://vanng822.github.io/pagination/ @shavidzet

Looks good, but I'm talking about host static files, html files in example/ dir, it would have demo purpose.

Ah, ok maybe someone or you can contribute. I don't really have time for this now and also that I "abandoned" nodejs since 4 years ago.

It needs your account permissions to change gh-pages configuration for your personal repo.
Also, contributors can host files on https://netlify.com, but the first step is to import repo from their panel, it needs also your account permissions too 😃


Re-write Application Metric Documentation

Overview
Connects to https://github.com/ministryofjustice/cloud-platform/issues/844
This document will follow an example to expose an application endpoint to Prometheus.
Why
It was decided that the previous documentation was out of date and required an uplift.

This look great, @jasonBirchall I just spotted one tiny typo, and then I think it's good to go.


Replace old Camunda BPMN repository

[x] Add Github workflow to build image based on this repository
[x] Archive old repository available here
[ ] Add first release comprising new engine
[ ] Update documentation (?)

Can we add the history scripts maybe as a git submodule ? To enable fetching latest changes in an easy way?

In principle yes, however, Camunda changed the plugin mechanism between version 7.14 and 7.15 (as far as I remember) and I had some trouble integrating the latest version of the scripts. But would be a nice improvement, so feel free to try it out :-)


Add tags to articles

Unfortunately, there seems be no way to add tags to the article: https://developer.hatena.ne.jp/ja/documents/blog/apis/atom


Add better instructions on configuring deno fmt

https://docs.deno.com/runtime/fundamentals/linting_and_formatting/#available-options
This page needs some example code and better instructions

Also mentioned in https://github.com/denoland/docs/issues/1143

I've updated the copy and included a link to the configuration file that shows the settings options for the fmt tool in https://github.com/denoland/docs/pull/1165


Problem running on Windows

Getting an error "Windows cannot find 'jre/bin/java'" when running the v2 tika-gui.bat. The Linux version runs correctly. Java is installed, and the Release version runs.

Is this v1.0.0-ALPHA4?  If so, do you see that there is, in fact, a java at jre/bin/java relative to the .bat file?

tika-gui-v2-main, I just downloaded the Zip from GitHub. There is no java near the .bat file (which I put in Downloads). I was looking for a .jar file in the download somewhere to run directly, but no luck.

This Zip?

Yes.

If so, that's just the source code.  You'd have to build it and run the release locally to get all of the java stuff and jars where they belong.
The release zips for the latest release are here: https://github.com/tballison/tika-gui-v2/releases/tag/v1.0.0-ALPHA4 One per OS supported.

If there's enough new stuff for another release, I can make dependency upgrades and then push the release.
I was hoping to fix the sqlite stuff and the race condition in the UI before then.

Shoot, I knew that. My bad. I've previously used the releases but when I saw the version 2 tag I got excited. No worries about a new version if the changes don't warrant it.


[CT-1261] Have a "FROM SOURCES" SQL query

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
I often query views created in DBT, but when I encounter an issue it is hard to share the SQL with external colleagues to troubleshoot the problem. This is mainly because some teams that don't have access to the DBT managed views themselves (or the data vendors for the raw data), so there is no single SQL statement they can run to reproduce the issue.
I'm looking for a version of the "Compiled SQL" that goes all the way back to the sources. I envision this as a recursive replacement of the dbt tables/views until you get to only referencing sources.
For example; if you have model:
-- dbtTable1.sql
SELECT * FROM {{ source('dbo', 'sourceX') }}

and
-- dbtTable2.sql
SELECT * FROM {{ref('dbtTable1')}}

I'd like to be able to see dbtTable2's compiled sql as
SELECT * FROM dbo.sourceX

Note: Obviously this is more valuable with more complex queries.
Describe alternatives you've considered
No response
Who will this benefit?
Teams working with data vendors and/or collaboration between DBT users and non-dbt users.
Are you interested in contributing this feature?
No
Anything else?
No response

hi @mkleinbort-ic, are you aware of the compiled code in the target directory? when you run dbt compile or several other commands (run, build at least) your code is "compiled", which is then shipped off to the warehouse for execution.
that code ends up (by default) somewhere like `target/compiled//models//.<sql|py>
let us know if you're looking for something else or this isn't sufficient!

Yes, and it is very helpful, but not enough to address the ask.
When I have DBT models on DBT models the compiled SQL references tables/views that are not available to the data vendors / external partners (ie. not the raw data). I'd have to send 10+ (compiled) SQL files to external colleagues and they'd have to run each of these (in a given order) to create the tables/views - and then they can see what I'm seeing.
To illustrate the point, consider the following:
layer1.sql
SELECT * FROM {{ source('dbo', 'raw_transactions') }} WHERE transactionStatus != 'cancelled'

layer2.sql
SELECT storeId, SUM(sales) AS storeSales FROM {{ ref('layer1') }} GROUP BY storeId

This roughly gets compiled to:
layer1.sql
SELECT * FROM SOURCE_DATABASE.SOURCE_SCHEMA.raw_transactions WHERE transactionStatus != 'cancelled'

And
layer2.sql
SELECT storeId, SUM(sales) AS storeSales FROM TARGET_DATABASE.TARGET_SCHEMA.layer1 GROUP BY storeId

However, if I see an error in the results of layer2 (the view) I need people to have access to the layer1 view to help me troubleshoot it.
A naive solution would be to recursively replace dbt's views with CTEs. Something like:
layer2_from_source.sql
WITH layer1 AS (
    SELECT * FROM SOURCE_DATABASE.SOURCE_SCHEMA.raw_transactions WHERE transactionStatus != 'cancelled'
)

SELECT storeId, SUM(sales) as storeSales FROM layer1 GROUP BY storeId

But it is unlikely a CTE solution would always result in valid SQL.
(as before, this has much more value the "deeper" the DBT dag becomes)

A naive solution would be to recursively replace dbt's views with CTEs.

You could actually get this, by changing all the model materializations to ephemeral!
Here's what I get in the example above, with dbt compile -s layer2:
with __dbt__cte__layer1 as (
SELECT * FROM "jerco"."dbo"."raw_transactions" WHERE transactionStatus != 'cancelled'
)SELECT storeId, SUM(sales) AS storeSales FROM __dbt__cte__layer1 GROUP BY storeId

The spacing could be prettier, but that's effectively what you're after.
One cool trick to override the configuration of all models in your project: Install it as a package in another project. Any config you set in your root-level project's dbt_project.yml takes precedence over all config set in packages.
# packages.yml
local: path/to/actual/project

# dbt_project.yml
name: 'wrapper_project'
...
models:
  actual_project_name:  # installed here as a package
    +materialized: ephemeral

Now, in order to rewrite that SQL — to simplify it down — dbt would need an actual validating SQL parser / transpiler. That's something we've discussed wanting for other reasons (#4454, #4458), and we might want it for this reason, too — probably by integrating with other SQL parsers / transpilers! That would be a way to "simplify" the SQL above to something like:
SELECT storeId, SUM(sales) AS storeSales
FROM "jerco"."dbo"."raw_transactions"
WHERE transactionStatus != 'cancelled'
GROUP BY storeId

I'm going to close this issue in the meantime, as something that's already made possible by the ephemeral materialization. Rewriting/simplifying SQL would be a much bigger lift, but I'm not saying never.

No need for the SQL simplification - your answer solves my problem!


use: add new method

Allows declaring multiple hooks through store.use(hooks). All hooks will now be executed on every call. Useful to register multiple handlers and stuff ✌
const barracks = require('barracks')
const log = require('choo-log')

const store = barracks()
store.use(log())

const createSend = store.start()

Oh, to clarify: no breaking changes. Minor version

Coverage increased (+0.5%) to 95.172% when pulling 6bc9b11c893c5f5f247bc1a708ab784a7e872bc1 on use into b381a971ec72102caf6570756bb3d63a8e6f885e on master.

This is cool with me if we don't mind the arrays part?  (We could always Array.isArray is if we really wanted to prevent it)

@toddself yeah, I'm not too fussed about it - feel like the assert() calls we got is to prevent people from making lil accidental mistakes - nothing too strict - most common use case I can imagine that would occur is that they'd forget to initialize a function, so it doesn't return an object and we'd catch that and warn :sparkles:

Coverage decreased (-84.2%) to 10.49% when pulling 3e05b1bb644659682a656fd5180b892cb697809d on use into b381a971ec72102caf6570756bb3d63a8e6f885e on master.

Coverage increased (+0.5%) to 95.238% when pulling e20ff726c8dbd17c61348977a8f263163b779f4d on use into b381a971ec72102caf6570756bb3d63a8e6f885e on master.

Welp, think this is good to merge then :sparkles:

released as v8.1.0 :grin:


python312Packages.django-stubs-ext: 5.0.4 -> 5.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.django-stubs-ext is: Extensions and monkey-patching for django-stubs
meta.homepage for python312Packages.django-stubs-ext is: https://github.com/typeddjango/django-stubs
meta.changelog for python312Packages.django-stubs-ext is: https://github.com/typeddjango/django-stubs/releases/tag/5.1.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.0 with grep in /nix/store/qqbdg4g3v8q45hy6d9acr2cwc8rqf4i0-python3.12-django-stubs-ext-5.1.0
found 5.1.0 in filename of file in /nix/store/qqbdg4g3v8q45hy6d9acr2cwc8rqf4i0-python3.12-django-stubs-ext-5.1.0

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

12 total rebuild path(s)

12 package rebuild(s)

First fifty rebuilds by attrpath

healthchecks
python311Packages.django-modeltranslation
python311Packages.django-stubs
python311Packages.django-stubs-ext
python311Packages.djangorestframework-stubs
python311Packages.pyngo
python312Packages.django-modeltranslation
python312Packages.django-stubs
python312Packages.django-stubs-ext
python312Packages.djangorestframework-stubs
python312Packages.pyngo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qqbdg4g3v8q45hy6d9acr2cwc8rqf4i0-python3.12-django-stubs-ext-5.1.0 \
  --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 python312Packages.django-stubs-ext https://github.com/r-ryantm/nixpkgs/archive/babb4b38199c8a6932cf2f08ca25108777cac9dd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/babb4b38199c8a6932cf2f08ca25108777cac9dd#python312Packages.django-stubs-ext

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qqbdg4g3v8q45hy6d9acr2cwc8rqf4i0-python3.12-django-stubs-ext-5.1.0
ls -la /nix/store/qqbdg4g3v8q45hy6d9acr2cwc8rqf4i0-python3.12-django-stubs-ext-5.1.0/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

21 packages built:

healthchecks
python311Packages.django-modeltranslation
python311Packages.django-modeltranslation.dist
python311Packages.django-stubs
python311Packages.django-stubs-ext
python311Packages.django-stubs-ext.dist
python311Packages.django-stubs.dist
python311Packages.djangorestframework-stubs
python311Packages.djangorestframework-stubs.dist
python311Packages.pyngo
python311Packages.pyngo.dist
python312Packages.django-modeltranslation
python312Packages.django-modeltranslation.dist
python312Packages.django-stubs
python312Packages.django-stubs-ext
python312Packages.django-stubs-ext.dist
python312Packages.django-stubs.dist
python312Packages.djangorestframework-stubs
python312Packages.djangorestframework-stubs.dist
python312Packages.pyngo
python312Packages.pyngo.dist

Maintainer pings
cc @elohmeier for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

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

21 packages built:

healthchecks
python311Packages.django-modeltranslation
python311Packages.django-modeltranslation.dist
python311Packages.django-stubs
python311Packages.django-stubs-ext
python311Packages.django-stubs-ext.dist
python311Packages.django-stubs.dist
python311Packages.djangorestframework-stubs
python311Packages.djangorestframework-stubs.dist
python311Packages.pyngo
python311Packages.pyngo.dist
python312Packages.django-modeltranslation
python312Packages.django-modeltranslation.dist
python312Packages.django-stubs
python312Packages.django-stubs-ext
python312Packages.django-stubs-ext.dist
python312Packages.django-stubs.dist
python312Packages.djangorestframework-stubs
python312Packages.djangorestframework-stubs.dist
python312Packages.pyngo
python312Packages.pyngo.dist


⚠ Processors has degraded performance

In ddcb533, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 48 ms

Resolved: Processors performance has improved in d822630.


Add some important events to batch & staking to ensure ease of analysis

Allow events from batched items to be separated. Also ensure the validator stash and era index from which the rewards are derived is always recorded. Also rename the events which do not respect the past-participle naming convention.

bot merge

bot merge

bot merge

Need a rebenchmark?

Looks good modulo I don't understand the justification for the ItemCompleted event and

Also include the era index in the Rewarded event

The code doesn't have it included, but maybe you meant too since it was added to the Rewarded event doc comment?
For users tracking events this could be a breaking change, heres a tl;dr:
EraPayout => EraPaid
Reward => Rewarded
Slash => Slashed
StakingElection => StakersElected
Also not sure if this affects @jacogr

@emostov indeed this is a breaking change, so we will adapt Fearless Wallet for it, thank you.
Most likely Subscan team should be notified as well, I will reach them out


Add option to do offload copying automatically

How do I change the option programatically in Python?
I have verified this branch from Python using the previous python driver I was using.  First data using resnet50 bs=64:
= this branch: 74.544 ms, 859 images/sec
= last measurements (Oct 21): 73.299, 873 images/sec
The previous measurements were based on older version of MIGraphX, so want to use the option to compare using the same MIGraphX build.


test: Docstrings module tests

This PR is part of Issue #15

refactors the 3 methods in docstrings.py that use 3rd party docstring_parser.parse function to instead of checking for None, handle the ParseError exception.
adjusts the tests to mock the exception raised. I don't think we ever get this exception because we call docstring_parser.parse with Auto style, we always get a Docstring object back, albeit a Docstring object with empty params.
add more tests to increase docstring test coverage:

Thanks @aluu317!
I think I'm just a bit lost on what's going on here though:

refactors the 3 methods in docstrings.py that use 3rd party docstring_parser.parse function to instead of checking for None, handle the ParseError exception.

Is there a case where we don't get a ParseError exception back but we do get a None back? I know the test coverage was pretty bad before, but I would want to make sure that we still get visible logging and correct handling when that case happens.

adjusts the tests to mock the exception raised.

I think this may answer my question from above, does this mean that the Docstring object with empty params is the case that was previously checked for by if not docstring instead of catching the parser error?

To clarify my Description above (I did a bad job explaining):
3rd party docstring_parser.parse function does not return None. This line here tells me that if there's no Docstring parsed, a ParseError had occurred and the exception was raised. So in our docstrings.py code, instead of checking for None, I chose to handle the ParseError instead.


Added wing 3d to downloadable design software in readme.md

Added wing 3d to downloadable design software in readme.md

Looks like a duplicated of #1269
Closing


[Bug]: wrong links of legacy version

Describe the bug
In README.md there are two mention of legacy version, but both of them have incorrect link.

AdashimaaTube-Legacy is suitable for legacy browser. You can install it from here.

If you still prefer to use an old browser, we also have AdashimaaTube-Legacy available.

As I understand, links need to be https://github.com/sapondanaisriwan/AdashimaaTube/raw/master/userstyles/AdashimaaTube%20Legacy.user.css
Screenshots
Not needed
What browser are you using?
Cent Browser 102.0.5005.167
What version of AdashimaaTube are you using?

Thank you for telling me


add flash algorithm for MultiTech xDot (STM32L151CC)

@sg- @c1728p9 This PR has been open for nearly 6 months. Any problems or can it be merged?

should be good to merge. Just need a conflict resolved


Add link to install cf

To use deploy.sh, you need to have installed cf.

a note was added since there's a choice of using cf or bluemix/bx as CLIs


bug 1837881: remove humorous help from dev focused command

Eventually we should probably find a way to auto-update these.  A someday project

/lgtm

/bugzilla rerfresh
/lgtm

/bugzilla refresh


[CSL-781] Move almost all executables to cardano-sl-tools

The main reason I am doing it is that currently every time one wants to change
something in tests, they have to wait until all executables are preprocessed.
It can be partially solved by --for-install flag, but:
• it's easier to forget to pass this flag than to pass the proper target;
• there still were about 5 exeuctables needed for installer.

One appveyor build failed with a strange error, but pr build passed and branch build is not required to pass, so I think it's fine to leave it as is.

Since macOS is disabled, this introduced a regression in osx, leaving one for-installer flag condition around


Medium:Weak Cipher Suites - ROBOT Attack : Vulnerable cipher suites are supported by the server

Stratos Version

4.4.0
Frontend Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] npm run start
[ ] Other (please specify below)

Backend (Jet Stream) Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] Other (please specify below)

Expected behaviour
AppScan DAST scan should not report Weak Cipher Suites - ROBOT Attack : Vulnerable cipher suites are supported by the server vulnerability
Actual behaviour
AppScan DAST scan reports Weak Cipher Suites - ROBOT Attack : Vulnerable cipher suites are supported by the server vulnerability
Steps to reproduce the behavior
AppScan DAST scans for Stratos URL https://ui.<IP_ADDRESS>.nip.io/api/v1/auth/verify.
The test result seems to indicate a vulnerability because AppScan determined that the site uses weak cipher suites by successfully creating SSL connections using each of the weak cipher suites listed here.
The following weak cipher suites are supported by the server:
Id Name SSL Version
47 TLS_RSA_WITH_AES_128_CBC_SHA TLS 1.2
53 TLS_RSA_WITH_AES_256_CBC_SHA TLS 1.2
60 TLS_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
61 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
65 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.2
132 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.2
156 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
157 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
186 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 TLS 1.2
192 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 TLS 1.2
49232 TLS_RSA_WITH_ARIA_128_GCM_SHA256 TLS 1.2
49233 TLS_RSA_WITH_ARIA_256_GCM_SHA384 TLS 1.2
49308 TLS_RSA_WITH_AES_128_CCM TLS 1.2
49309 TLS_RSA_WITH_AES_256_CCM TLS 1.2
49312 TLS_RSA_WITH_AES_128_CCM_8 TLS 1.2
49313 TLS_RSA_WITH_AES_256_CCM_8 TLS 1.2
Log output covering before error and any error statements
Insert log hereCopy

Detailed Description

Context

Possible Implementation

Change server's supported ciphersuites

@manojtyagi2021 What server??
Please be careful when creating issues using automated tools to first read what it produces and then apply some context.

No response, closing.


Case study: Content box seems smaller than PL

See https://iatistandard.org/en/about/case-studies/raw-html-case-study-example/ vs http://iati.surge.sh/page-templates/01-2-1-case-study

The example page no longer exists and was likely caused by the raw HTML template used. Closing issue.


fetch vs superagent with turned on withCredentials

Superagent code:
superagent
      .post(this.apiUrl + '/login')
      .send(data)
      .set('Accept', 'application/json')
      .set('Content-Type', 'application/json')
      .withCredentials()
      .end((err, result) => {
        console.log(err)
        console.log(result)
      })

Fetch code:
return fetch(this.apiUrl + '/login', {
      method: 'POST',
      headers: this.postJsonHeaders(),
      body: JSON.stringify(data),
      mode: 'cors',
      credentials: 'include'
    })

Response header contain Set-Cookie:token=c06a3daba059e32529d2a25ab4be45bd; path=/; HttpOnly
If I using fetch, I see cookies in Chrome console.

But if I using superagent, cookies is clear

why topic is closed? I can confirm this. Cannot set cookie from server

@romanlex I'm using fetch now

I can also confirm this bug.

Wow, just installed the fresh version 8.0.0 and seems like the bug has been fixed.


K8s software-update: RabbitMQ and REDIS

Redis updated to 7.0.2
Rejson updated to 2.0.9
RMQ updated to 3.10.5
Added tcpKeepAlive for rmq

Backport to 3.5.0  branch


Microsoft.Framework.ConfigurationModel stuck on beta 5?

Hi there,
I don't seem to be able to update my Microsoft.Framework.ConfigurationModel reference to beta 7, is this now under a different name or something?  I need it for the Configuration class.
Nick.

It's been moved to another package: Microsoft.Framework.OptionsModel.

@henkmollema not quite. It was renamed to Microsoft.Framework.Configuration

@npateman Follow https://github.com/aspnet/Announcements/issues for breaking changes like these

Great thanks!

Oh duh, copied the wrong package name haha. :dizzy_face:

Can anyone share , how to read config file  in Beta7

@shreedevishete you can see an example in the MusicStore sample app
https://github.com/aspnet/MusicStore/blob/dev/src/MusicStore/Startup.cs#L24-L33


Create insert journal headline at point

I have a project where I would like to use journal style headlines outside a journal file. This small adjustment enables the option to insert journal style headlines at point. I thought it might be useful sometimes for other user too. If you think the extra command is too "exclusive" to be added by default then it is no problem if you remove it. But then it would still be nice to keep the optional insert-at-point argument.

I like it! Let's see what @cslux will say.

On a second thought, and a more thorough look at your code, I feel that this behavior does not fit well into org-journal. Reading through org-journal's code, it is not clear how this functionality is related to org-journal's behavior.
I think I would advise you to maintain a fork or a derivative project for this functionality.
That said, I would have no problem with adding an optional argument or configuration variable here and there for enabling your fork.

Okay thanks, that is fine also. On the other hand, all arguments I've added are optional, and should not break anything.
The only parts that could break something would be

moving the TODO in front of the time in the headline (in #338), but as I wrote in that PR (with a link to org's documentation), that is required for org to handle the HEADLINE as a todo.
adding the time within the time-stamp (but that was merged already by cslux, he (or me) just had to update a single test)
inserting the scheduled keyword when creating a scheduled entry

I would say these are nice little "improvements/corrections" (if indeed they do not break the functionality), but they are not essential at all of course. Anyway, no problem for me to maintain a fork.

I saw that all the arguments are optional. My concern is more with the maintenance surface. Optional arguments only make sense if the code itself is actually using them--otherwise, how would you decide whether to delete some apparently unused piece of code?
Therefore, such affordances for third parties must be kept to a minimum, and rigorously documented (and tested, if possible). In case of the insert-at-point arguments, I felt that they needed to be introduced in a few too many places for comfort. Perhaps there is a way of refactoring org-journal's internals such that insertion and location are handled separately, and can be reused by your code more easily (just thinking out loud here). That would be a preferred solution to me.
As for the order of date and TODO, as well as the scheduled keyword, I am all in favor of those.
All of that said, I am not really the maintainer of org-journal any longer. If @cslux later decides that this pull request is acceptable after all, I am entirely ok with that, too.


[LastPass Credentials Search] Error message showing full credentials (security issue bug?)

Extension
https://www.raycast.com/alex-popov-tech/lastpass
Description
I belive I've been signed out or something in the lastpass cli, and when I now tried to do a search I was able to see my master password and email, everything was shown.
Steps To Reproduce
I'm not quite sure how it happend, but it looked like this:

I'm not sure if this is a error message by the lastpass cli or not, but if it is i would assume a possible fix could be to have a regex to remove the password. The place where the password is mentioned looked like this:
&& echo "......" | LPASS_DISABLE_PINENTRY=1
so a regeg looking for echo " and " | LPASS_DISABLE_PINENTRY could maybe work?
Current Behaviour
The master password and email is being showed. (guess the email is ok)
Expected Behaviour
Expected the masterpassword atleast to not be shown.

Hello, @jjmss !
Password is there for debugging purposes, so if you put incorrect password, you will be able to see it there, in error message.
As for your error, can you please check is there email confirmation of usage your credentials from LastPass ? If so, please approve it and try load extension again

I logged in again using lpass login and it worked again.. even if the password is there for debugging, it would be nice to either toggle debugging or something so "again" for people sitting in public or doing live meetings screensharing (as the search worked fine yesterday, so it came as a suprise for me)

okay, makes sense, i will take into it

@jjmss Hello! I've created pr addressing your issue #7841


Client Allocation Request for: Huddle01

Client Allocation Questions
Core Information

Name: Huddle01
Website / Social Media: www.huddle01.com
Region: Asia excl. Greater China
DataCap Requested: 500TiB
Addresses to be Notarized: f1f66jgglnxcdtdkfgppqt4r72x6oifrkcfnrec5q
Notary Requested: andrewxhill

@ranjan3118 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hi @ranjan3118! As part of the onboarding process, would you mind answering the following:

Can you introduce yourself? Where can I find you online? Examples include Github, Twitter, LinkedIn, WeChat, etc., and more than one is encouraged.
If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
In which region(s) do you intend to use the DataCap?
What is your use case for the DataCap being requested?
How many miners do you plan on allocating the DataCap? Please specify if you have a specific miner(s) you would like to allocate the DataCap.
Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing? If so, how will you plan to report it?
Will your organization be responsible for allocating the full DataCap? Examples where this might not be the case, include app builders where the application end-users may have access to storage backed by the DataCap. Please read our full proposal for details on this approach. Unfortunately, our proposed multisig enabled DataCap provider is not ready today, but when it is, we will provider further documentation.

Could you also confirm that the address you listed isn't one hosted on Textile infrastructure? If it is, I'll ask a second notary to 👍 this application before I confirm.
Thanks!

Hi @andrewxhill

I am Ayush Ranjan, co-founder & ceo of Huddle01. Along with my cofounder @susmit, I am building a video conferencing platform and SDK powered by web3 and blockchain technology.
Link to my Twitter - https://twitter.com/ranjan3118
Link to my LinkedIn - https://www.linkedin.com/in/ranjan18/
I am the co-founder of Huddle01 - www.huddle01.com , Graphene 01 is the name of the company under which we have launched the product Huddle01. Graphene 01, Inc is registered in Delaware and was incorporated in October 2020. Ayush Ranjan and Susmit are the named officers of the organization.
We intend to use the datacap in Asian region in majority of the cases.
Huddle01 has clients in Web2 and Web3 space in sectors like education, telemedicine, gaming and more. Huddle01 intends for the clients to use Filecoin instead of S3 buckets or Glacier to store their recordings of 1:1, 1:few, 1:many video & audio calls. It also plans to progressively make Filecoin a de-facto for storage of educational content for Cohort Based Courses (CBCs), uploading assignments, notes and more.
The 500 TiB, we tentatively plan on distributing to 4 miners from Asia with 100 TiB each and one miner from west with 100 TiB. Regarding the details of which miners, we haven't zeroed in yet.
Yes, the details of datacap allocation and its utilisation, we plan to make it publicly available in the form of CSV’s or excel sheets or tables on any of our publicly hosted platforms. In case of excessive/unfair self-dealing we would be immediately reporting the same. We have demonstrated something similar during Filecoin Slingshot 2.4 where all the details could be seen publicly.
Filecoin Slingshot dashboard by Huddle01 - http://filecoin-proofs.huddle01.com/
Filecoin Slingshot competition 2.4 - https://slingshot.filecoin.io/project/60d8b0d81295158ebdb2db47?phase=2.4
Yes, the applications developers would not have access to this datacap but would be given access to the monthly 32 GiB publicly available datacap.
Yes, I confirm that address listed above isn't one hosted on Textile infrastructure.

Hey @ranjan3118 sorry for the delay here. There are a few dimensions in my rubric that withhold datacap a bit from first time applications (e.g. public history of past datacap). I can grant you 1TiB immediately. If you start using that though, I'd be happy to do a follow-up with you before your datacap is depleted for a higher amount. Sound okay? If so, can you confirm once again that the above FIL address is the right one?

Hey @andrewxhill understood. yes that sounds good.
yes, the above FIL address is the correct one. Thanks.

Sorry, this was completed some days ago. You are good to go!


If WMS "Additional WMS Params (as JSON object)" does not have wrapping {}, add them.

The two scenarios to test are

A blank input box should result in {} which is a valid entry
Comma separated fields should look like var: 12, num: 8 -> {var: 12, num: 8}

no problem with the first one, we can use the sanitizer logic.
for the second one it's a tricky thing, we can sanitize it in the same function but we can't use keys without double quotes (the current validator wants them). we can use a complex function to creare a valid json from "var: 12, num: 8" like this:
{${url.split(",").filter(v => v !== "").map(v => v.split(":")).map(([k, v]) => "${k.replace(/[ "']/g, "")}": ${v}).join(",")}}

That sounds good so far.  You can create regex patterns to test against to know how to sanitize the data.

Use
sanitizer: json => `{${json
                    .trim()
                    .replace(/[{}]/g, "")
                    .split(",")
                    .filter(u => u !== "")
                    .map(u => {
                        const [k, v] = u.split(":");
                        return v && `"${k.replace(/[ "']/g, "")}": "${v.replace(/[ "']/g, "")}"`;
                    })
                    .join(",")}}"`,


Static pages support broken?

I know that buster doesn't support static pages. I did the trick mentioned in https://github.com/axitkhurana/buster/issues/7 and it generates the page, but without the index.html string. When I try to open the page in the browser it doesn't work.

+1 same problem as @tomvo and @WillemWijnans .
I sort of "automated" the procedure by adding an npm task:
"rename": "mv static/about static/about.html"`` so I can run multiple npm tasks with &&` to wrap buster tasks (i.e. generate and deploy) in one npm command.

Although @apandichi fix solved the issue once and for all.
See d9cdde755b39a74c3ea99cd8bffbbd7be94b24cd


Allow users to specify search params on route path

What is this Contribution About?
Allow users to specify search params on route path to be used by URLPattern.
URLPattern already support search params, we are not using it so far, but we have now included. Users needs to specify following URLPattern documentation.
Example usecase in the linked issue.
Issue Link
Please link to the relevant issue that this pull request addresses:

Issue: #823

Additional: https://github.com/deco-cx/deco/pull/826/files


Implement support for diagnostic requests on server

The LanguageServer trait is missing the following requests:

[ ] textDocument/diagnostic
[ ] workspace/diagnostic

The Client struct is also missing the following requests:

[ ] workspace/diagnostic/refresh

These request types were added in LSP 3.17.0, but lsp-types unfortunately doesn't support them. This should have landed in lsp-types 0.94.0, but was missed in https://github.com/gluon-lang/lsp-types/pull/255. I've opened https://github.com/gluon-lang/lsp-types/pull/258 to address this omission.

Unassigning myself as this ticket is blocked on https://github.com/gluon-lang/lsp-types/pull/258 currently.

does there exist any branch of tower-lsp with implementation utilizing https://github.com/gluon-lang/lsp-types/pull/258?

@meetmangukiya Not at the moment, sadly. It should be pretty trivial to add after the PR is merged, though!

Upstream PR was only just merged! :tada: A maintenance release of tower-lsp containing the changes should come shortly.

@meetmangukiya Alright, tower-lsp 0.20.0 and tower-lsp-macros 0.9.0 have been released to crates.io. This release includes full support for diagnostic requests. :rocket:

nice, thanks!


Kysely and Deno & MySQL Driver

Anybody already written a MySQL driver to work with Kysely in Deno ? Or is that even needed anymore ? Sry my programming skills are bad  and I can't write it for myself :)

I managed to create one with the help of chatgpt :) for anybody who needs something like this here it goes. I don't know how good it is, but it's working for me :
`import { Client, ClientConfig } from "mysql";
import {
CompiledQuery,
DatabaseConnection,
Driver,
QueryResult,
TransactionSettings,
} from "kysely";
type QueryArguments = unknown[];
export class MySQLDriver implements Driver {
readonly #connectionMutex = new ConnectionMutex();
#client?: Client;
#connection?: DatabaseConnection;
db_conn_info: ClientConfig; // MySQL connection info
constructor(conn_info: ClientConfig) {
this.db_conn_info = conn_info;
}
async init(): Promise {
this.#client = await new Client().connect(this.db_conn_info);
this.#connection = new MySQLConnection(this.#client);
}
async acquireConnection(): Promise {
await this.#connectionMutex.lock();
return this.#connection!;
}
async beginTransaction(
connection: DatabaseConnection,
_settings: TransactionSettings,
): Promise {
await connection.executeQuery(CompiledQuery.raw("start transaction"));
}
async commitTransaction(connection: DatabaseConnection): Promise {
await connection.executeQuery(CompiledQuery.raw("commit"));
}
async rollbackTransaction(connection: DatabaseConnection): Promise {
await connection.executeQuery(CompiledQuery.raw("rollback"));
}
releaseConnection(): Promise {
this.#connectionMutex.unlock();
return Promise.resolve();
}
destroy(): Promise {
this.#client?.close();
return Promise.resolve();
}
}
class MySQLConnection implements DatabaseConnection {
readonly #db: Client;
constructor(c: Client) {
this.#db = c;
}
async executeQuery(compiledQuery: CompiledQuery): Promise<QueryResult> {
const { sql, parameters } = compiledQuery;
const rows = await this.#db.query(sql, parameters as QueryArguments);

return Promise.resolve({
  rows: rows as [],
});

}
async *streamQuery(
_compiledQuery: CompiledQuery,
_chunkSize?: number,
): AsyncIterableIterator<QueryResult> {
// Streaming queries are not yet supported by the deno_mysql library.
throw new Error("Streaming queries are not supported with MySQL driver.");
}
}
class ConnectionMutex {
#promise?: Promise;
#resolve?: () => void;
async lock(): Promise {
while (this.#promise) {
await this.#promise;
}
this.#promise = new Promise((resolve) => {
  this.#resolve = resolve;
});

}
unlock(): void {
const resolve = this.#resolve;
this.#promise = undefined;
this.#resolve = undefined;

resolve?.();

}
}
`

That seems to be created from the SQLite driver, which has a single connection. Having the mutex there forces your MySQL driver to only have one connection, which will lead to bad performance once you have more than one concurrent request running.

thanks for the info, I will try to remove it.

I managed to modify it to use a connection pool, that currently has 10 max connections, but you can modify the maxConnections: number = 10 value according to your needs and server capacity.
https://pastecode.io/s/jwfpktky
Is this one better @koskimas ?

thanks for looking into it @y12studio but I prefer my method more, seems more cleaner.

I'd also like to add that npm specifiers are not yet supported on deno deploy so the npm packages will not work there unless using cdns or esm.sh. So custom adapters/dialects for deno are the way to go for now for both mysql and postgres.

I would love if I could just use kysely's query builder, target a particular dialect and then get a string. I want to pass the string to the database interface myself.

@alexgleason https://kysely.dev/docs/recipes/splitting-build-compile-and-execute-code


CMSIS-NN Conv kernel writes outside of allocated memory when num_channels > 256

@tensorflow/micro
System information

Host OS Platform and Distribution (e.g., Linux Ubuntu 16.04): N/A
TensorFlow installed from (source or binary): source
Tensorflow version (commit SHA if source): b36436b087bd8e8701ef51718179037cccdfc26e
Target platform (e.g. Arm Mbed OS, Arduino Nano 33 etc.): ST IoT Discovery Kit

Describe the problem
The CMSIS-NN convolutional and depthwise convolutional layers write in uninitialized memory in CalculateOpData when num_channels is higher than 256 (kMaxChannels). There are no boundary checks for this function, and thus no error is thrown when this happens.  Non CMSIS-NN kernels have no problem.
I can get around this by switching the structure to use dynamic memory:
void* per_channel_output_multiplier;
context->AllocatePersistentBuffer(context, sizeof(int32_t) * num_channels, &per_channel_output_multiplier);
data->per_channel_output_multiplier = (int32_t*)per_channel_output_multiplier;

But this is a temporary object, so I assume I should use the scratch buffer instead. However, I have no idea how to clear the object again from the scratch buffer.
Please provide the exact sequence of commands/steps when you ran into the problem
The problem shows in the following tflite model. In one of the final layers it has 1280 channels. ei-plants-vs-lamps-transfer-learning-tensorflow-lite-int8-quantized-model.lite.zip
/cc @kwagyeman This could be the same issue as you're facing with CMSIS-NN. It shows on our image models.

Awesome find Jan. If this is fixed then CMSIS-NN will work for images finally.

@kwagyeman Seems like it. I've written a patch and now have CMSIS-NN working with MobileNetV2, will open up a PR after the weekend.

@janjongboom Are there any other parts in the code where they allocate static buffers like this? It's kinda down right absurd in production code by ARM employees...

Conv.cc and depthwiseconv.cc both have the issue. You need to fix both.

Hello @kwagyeman @janjongboom!
I represent Arm. Some background; kMaxChannels is there for historical reasons - that's how the reference kernels used to be implemented as well. Some months back, the AllocatePersistentBuffer API was introduced in favor of the static buffers. Hence the ref kernels was updated to use that API. Our intention is to 'up-merge' changes, such as this one, to our CMSIS-NN kernels on a regular basis. However, we had to revert that change since we discovered an issue with the AllocatePersistentBuffer API, see https://github.com/tensorflow/tensorflow/pull/41121 for details. We're worked with the TFLu team to resolve this issue and it looks like this was fixed this(!) friday by https://github.com/tensorflow/tensorflow/commit/59d177d9acabe8e70bc33e554a364d2620bc6999#diff-7aab15c6eb5282359c2b928998bab743.
In the meanwhile, the quick fix is to bump kMaxChannels to the size it needs to be on your local fork.
I hope this gives some clarity to the issue.
@janjongboom thanks for the PR (https://github.com/tensorflow/tensorflow/pull/42770)! Let continue the technical discussion there.
Cheers!
Fredrik

@freddan80 Thanks for the update. I ran into the same issue on our 2.3.0 fork, and replaced the scratch buffer with a persistent one to get around that.

In the meanwhile, the quick fix is to bump kMaxChannels to the size it needs to be on your local fork.

This adds 10K of RAM per convolutional layer, which won't fit on our targets.

@janjongboom thanks for the updated PR!

This adds 10K of RAM per convolutional layer, which won't fit on our targets.

Make sense. Then your PR is the preferred solution.
However, allocating the memory using AllocatePersistentBuffer API will only move the memory claim from the BSS to the memory arena (which may well be located in BSS as well). It actually won't save memory, it's just putting it in a different part of the SRAM.
Cheers!

The tensor arena is dynamically allocated and freed so memory can be used for other things until when it’s needed for TF lite. Having it be dynamically allocated is a must.
I don’t wish to be mean here, but, I have been consistently disappointed with ARMs lack of effort in support for these faster kernels... I would like to ask that future code released has more effort put into making it useful for a wider audience. Hard coded static buffers in code with max sizes without range checks is not production code.
Anyway, glad to see this getting fixed so we can enable it on the OpenMV Cam finally.

@kwagyeman I believe there is some misunderstanding here. The TFLu feature to handle interleaved persistent memory request and arena scratch buffer requests, is only possible since the 28th of Aug 2020 (see 59d177d9acabe). We've been working with Google towards getting this TFLu feature so that it improves the usage of CMSIS-NN for wider audience like you.
Sorry that you feel that it wasn't given attention. Hope PR #42770 helps the case now and please reach out by a Github ticket, such as this one, for unsupported features or bugs, either in the TFLu or the CMSIS-NN repo. That way the issue is seen and known by a wider audience and thereby gain traction and leverage support from the entire community.
Cheers!

However, allocating the memory using AllocatePersistentBuffer API will only move the memory claim from the BSS to the memory arena (which may well be located in BSS as well). It actually won't save memory, it's just putting it in a different part of the SRAM.

Yep, but I only have one very large convolutional layer and a lot of smaller ones, so dynamically allocating it saves me a lot of memory. But great to see PRs being landed to mainline these types of issues.
@freddan80 Q though (we can take this offline if you prefer): are there currently CI/CD pipelines set up for the CMSIS-NN kernels? E.g. we found this issue & https://github.com/tensorflow/tensorflow/issues/41816 through our own CI (and a bunch of debugging :-)), and we have currently automated tests for a wide variety of development boards that we run on real hardware for releases, both with the micro allocator and custom allocators, and with and without CMSIS-NN. But we don't follow mainline TensorFlow so we only find these issues once we upgrade. Perhaps it would be beneficial to share that with Arm?

@freddan80 Q though (we can take this offline if you prefer): are there currently CI/CD pipelines set up for the CMSIS-NN kernels? E.g. we found this issue & #41816 through our own CI (and a bunch of debugging :-)), and we have currently automated tests for a wide variety of development boards that we run on real hardware for releases, both with the micro allocator and custom allocators, and with and without CMSIS-NN. But we don't follow mainline TensorFlow so we only find these issues once we upgrade. Perhaps it would be beneficial to share that with Arm?

We have our internal CI, that tests TFLu-CMSIS-NN usecases on FPGAs and HW models with Cortex-M4 up to Cortex-M55 reference systems. We usually find issues related to CMSIS-NN quite soon. Unfortunately the networks we use did not have a reshape before FC as you encountered in #41816, or it would have been caught. Usually we create a kernel unit test case - in fully_connected_test.cc in this case - when we find issues such as the one in #41816, and then contribute that to avoid the same issue in the future. For the issue reported in this ticket, we’ve been waiting for 59d177d to make a permanent fix (thanks again for you PR!). We had actually bumped kMaxChannels to 2048 in our internal tests (not being aware of the missing range check), but didn’t want to deliver that since it increases the memory footprint unnecessarily for smaller network usecases.
That’s some words about our internal CI. In parallel, we're working with the TFLu team to enable CMSIS-NN regression directly in the Tensorflow Github project, using Renode as target emulator (see test_stm32f4_binary.sh) to prevent breaking PR’s being merged. It’s work ongoing and may take some time since there's an issue running this using Docker. However, I believe CMSIS-NN is tested using at least one of the targets in the internal TFLu tests, so there is some level of protection.
It’s awesome to hear that you have CMSIS-NN tests in you CI tests as well! I’d love to hear more about that. Perhaps some of your work can be upstreamed to the Tensorflow Github repo?
Cheers!
Fredrik

I can provide some additional context from the TF Micro side:
As you probably already know, the conv and depthwise_conv kernels use per-channel scale and zero-point quantization parameters. From the scale and zero points values, we calculate a multiplier and shift during the Prepare stage, which involves some computationally expensive double precision math as well as exponent calculations. Applying the multiplier and shift is a relatively cheap operation which occurs during the Eval stage. The storage required for these multipliers and shifts correlates to the number of channels along the quantized dimension (see the TFLite quantization spec for more info).
Since we pre-calcualate shifts and multipliers during Prepare, we need to store the resulting values in persistent buffers, which means the memory cannot be re-used between kernel invocations (and the buffers must be allocated via context->AllocatePersistentBuffer). This is the price we pay for avoiding the large runtime overhead of calculating the multiplier and shift on-the-fly. Before we had a way to allocate persistent buffers in TF Micro, we implemented the conv and depthwise_conv kernels with a fixed-length buffer with 256 values. This issue seen here results from that previous implementation, and the fact not all of our kernels  have been updated to use dynamic allocation.
On a side note, it seems that there is increasing evidence that allowing models to use per-tensor quantization instead of per-channel for conv and depthwise_conv may be better for some TF Micro usecases. This is something we are aware of and discussing internally.


sap.(ui.core|m).routing.Targets: public method to add targets

The Router got the addRoute method to add new routes at runtime, but the Targets#_createTarget method is "private" (well, not really, ..its js) so there is no "official" way to add new targets to a router at runtime.
It would be nice to be able to add new routes and targets for example when loading additional components/modules etc.
But I guess this could be low priority since we could use _createTarget and _addParentTo.

Hi,
thank you for the message. We will add a public method to enable the adding of target to Targets.
Internal incident is created to track the issue<PHONE_NUMBER>.
Best regards,
Jiawei

Hi,
we added the method "addTarget" to sap.ui.core.routing.Targets. It will be available from version 1.34.
Best regards,
Jiawei


Custom tag export does not work

Describe the bug
It seems that the new added custom_tags do not work.
When I launch an export I do not have the custom tag
unknown resource dynatrace_custom_tags
To Reproduce
Steps to reproduce the behavior:

Launch .\terraform-provider-dynatrace_v1.18.1.exe -export dynatrace_custom_tags
Error displayed: unknown resource dynatrace_custom_tags

Expected behavior
List of custom tags

Hello @MaudVandevelde ,
You're right the resource dynatrace_custom_tags is not getting exported at the moment.
But there's a reason for that. Contrary to other endpoints of the Dynatrace REST API you're able to specify an entitySelector here. Essentially this means that a resource export would have to produce a .tf file for every single entity available within Dynatrace - every Service, every Host, every Process Group, ...
What the REST endpoint current does NOT offer is a way to query for the entities which's tags have been affected using said endpoint. For full coverage that would mean to iterate of 100k+ entities and check whether the list of tags is non-empty.
In other words, that resource is among the few that doesn't represent static "configuration settings". It offers to dynamically add or remove tags from entities.


Uglify now outputs error in Browserify/Uglify/Sourcemap recipe

Added error output for Uglify, so that it doesn't just fail silently.

This addresses: https://github.com/gulpjs/gulp/issues/990

Updated! Thanks @callumacrae silly oversight on my part.

You may also be interested in linking to Combining streams to handle errors for it's suggestion for handling errors.

@terinjokes I've added the note to the recipe.
Thanks @bhough!


Feature/toxic log removal

In this PR I removed the toxic logs from staging and production applications
 No stream match for pointcloud chosen texture Process - Color

What do you think about this new implementation @charlielito ?


fix: make CollectionHeader container slightly bigger

This PR resolves []
Description

Makes CollectionHeader container slightly bigger
Screenshots

Before
After

smaller devices
smaller devices

bigger devices
bigger devices

PR Checklist

[x] I tested my changes on iOS / Android.
[x] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

add some bottom header padding in collections page onboarding - gkartalis

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Thanks for the fix @gkartalis! One followup question: could we use margin/padding here? I didn't think of it at the time, but seems like it would make more sense instead of hardcoding a height.
I looked at the docs for ImageBackground and am frankly mostly confused by them - they mention

Note that you must specify some width and height style attributes.

but their code examples don't include either. They also say that style is ViewStyle props passed to the containing View, and in the docs for those props, they don't mention margin or padding...but those ARE included in their examples.
So...I think we could use margin/padding without issue?

@mdole you are right! Just tried it out and it works without the fixed height, will open a pr later today to update this


You attempted to update _value on TrackedStorageImpl, but it had already been used previously in the same computation.

I suspect this isn't actually a bug, but any help that could be given to help me track this down would be greatly appreciated!

I figured it out. The message didn't help a ton though :)

Note that the message is an internal auto-tracking message, not specific to this library. The stack trace came from wherever you set during a read (normally: when setting tracked state during construction or in a getter), but it would be equally likely to happen in any construction of tracked state. Worth flagging up to think about whether and how we could make that error message better in Glimmer. If we could port back in some of the work @wycats has done on Starbeam debugging tools into the Glimmer auto-tracking system, that might be a good first step.


Add permissions requirements for SDK repo when generating SDKS

Before users start working on the SDKs (.NET management plane, and all languages in data plane), the app should have a check to ask people to have:

Write permissions to the repository
Beign a public member of the Microsofr and Azure GitHub org.

@jsquire the write permission is only once. Not per language repo, right?

They'll need write permissions for every repo that they own code in - but we generally handle that via GitHub team membership so it should be a one-step process.   @weshaggard would be able to confirm.

We could add a check in the Prerequisites section of the SDK Release apps to ensure the neccesary people have permissions:

Like another step that says Request access and have 2 checks:
Text: Ensure every memeber of your team that is going to contribute to the Azure SDKs requests:

Access to Azure SDK team: link to https://aka.ms/azsdk/access
Access to SDK repositories: link to https://eng.ms/docs/products/azure-developer-experience/onboard/access?tabs=write-access

FYI @ladonnaq

After receiving more feedback that @catalinaperalta gathered from our service partner teams, we agreed to add this to each language step inside the "Generate SDK" task so the individual developer awknowledges they have permissions.
Currently this will happen for every release

Added to March cycle


Fun coincidence, we use the same disclaimer!

"malware ahead (..)"
Have a nice day!
Just thought it was nice To see such a coincidence, I admire those who make such a clear and concise disclaimer.
Over n out!

umm u got me i saw that disclaimer from you :) it was really clear

Oh it's okay! :D no worries, just happy someone else is using clear disclaimers, respect!
Have a really Nice day! :D


Side effect of notch_approximation_law.stress

Describe the bug
After call to notch_approximation_law.stress(value), the value object is sometimes changed. This is an unwanted side effect of this function.
To Reproduce
Hard to reproduce, it was observed in _compute_hcm_RAM where we have:
extended_neuber = pylife.materiallaws.notch_approximation_law.ExtendedNeuber(E, K_prime, n_prime, K_p)
extended_neuber_binned = pylife.materiallaws.notch_approximation_law.Binned(
        extended_neuber, maximum_absolute_load, 100)

This calls materiallaws.notch_approximation_law.Binned._create_bins_single_assessment_point where self._lut_primary_branch.load is changed during
self._lut_primary_branch.stress \
            = self._notch_approximation_law.stress(self._lut_primary_branch.load)

Expected result
self._notch_approximation_law.stress does not change the argument, self._lut_primary_branch.load in this case.
Environment (please complete the following information):

OS: Windows 11
How installed: pip
Version: develop branch

Additional context
The problem was tracked back and it seems scipy.optimize.newton(func, x0) changes x0 if it is an object like a pd.Series.

Using the fix with copy(x0) will make it work also for numpy 2 (at least in the cases in my setup)

Closed as of #139

I can confirm that the issue is now fixed with #139 (using np.asarray instead of copy(x0))


Run JS tests in Continuous Integration

We have a bunch of tests written in JavaScript in the repository. We need to find a way to run these automatically on Continuous Integration bots.

Maybe should try Selenium.

The tests are run via Selenium now.


Figure out recommended strategy on managing secrets in production

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2047
Originally created by @DouweM on 2020-05-19 20:43:29

Spun out of https://gitlab.com/meltano/meltano/-/issues/2023

View 10 previous comments from the original issue on GitLab


[CORE-610] Cherry-pick Snowflake VARIANT support

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.9 out of 10 committers have signed the CLA.:white_check_mark: molinamelendezj:white_check_mark: nadegepepin:white_check_mark: albscui:white_check_mark: robert-uhl:white_check_mark: chainlink:white_check_mark: bbonenfant:white_check_mark: jrockway:white_check_mark: PFedak:white_check_mark: acohen4:x: armaanvYou have signed the CLA already but the status is still pending? Let us recheck it.


Updated Catppuccin gtk theme version from v0.4.1 -> v0.5.0

Description of changes

Updated catppuccin-gtk to v0.5.0
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.05 Release Notes (or backporting 22.11 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.

I think you forgot to change the sha256 hash to sha256-tVkB9R3Z4lApCIveWPweTnB/JlwbiVAHREGq+xRINkM=

A simple version bump is not enough. Something changed in the build scripts that broke theme generation. Instead, we get the Colloid themes in the result directory instead.
$ l result/share/themes/
dr-xr-xr-x - root  1 Jan  1970  Colloid-Dark
dr-xr-xr-x - root  1 Jan  1970  Colloid-Dark-hdpi
dr-xr-xr-x - root  1 Jan  1970  Colloid-Dark-xhdpi

I noticed this too. I also noticed my overlay didn't fix the control center overlapping the Gnome 44 added dropdown menus. Glad I'm not going crazy!


chore: move vscode extension package.json to client

The generation of the vsix file is based on the package.json, this is now the client package.json.
The client takes the server as a workspace dependency. The bundling operates within client on the server package through node_modules.

Codecov Report

:exclamation: No coverage uploaded for pull request base (development@1b5d874). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 7b8b569 differs from pull request most recent head 5eda804. Consider uploading reports for the commit 5eda804 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@              Coverage Diff               @@
##             development     #396   +/-   ##
==============================================
  Coverage               ?   55.70%
==============================================
  Files                  ?      175
  Lines                  ?     4463
  Branches               ?      735
==============================================
  Hits                   ?     2486
  Misses                 ?     1744
  Partials               ?      233

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Allow the agent and channel to not exist at first

Checking if the agent and channel exists creates a chicken/egg condition where the agent and channel creation cannot be relayed for the first time.

Checking if the agent and channel exists creates a chicken/egg condition where the agent and channel creation cannot be relayed for the first time.

Hey Clara. Not sure maybe I miss something you discussed before. I would assume the agent/channel of bridgeHub is an built-in config when deploy the contracts.  For other sibling chains they need to customize the runtime to allow send xcm to create agent/channel(as we do for the template chain) through the channel of bridgeHub. After that they send other messages through their own channel.
So there is no problem but correct me if I'm wrong.

Checking if the agent and channel exists creates a chicken/egg condition where the agent and channel creation cannot be relayed for the first time.

Hey Clara. Not sure if I fully understand the context. Maybe miss something important you and team discussed?
I would assume the agent/channel of bridgeHub is an built-in config when deploy the contracts. For other sibling chains they need to customize the runtime to allow sending xcm to create agent/channel through the channel of bridgeHub(as we do for the template chain). After that they send other messages through their own channels.
So there is no problem but correct me if I'm wrong.

Hey @yrong! If you run start-services.sh, you'll see that the template parachain execution and parachain relayer keeps restarting. If you run the create agent test, you'll see the create agent message is sent to the outbound queue but it doesn't get relayed. So perhaps this is another bug - the bridge hub relayer isn't picking up the message as it should.

you'll see the create agent message is sent to the outbound queue but it doesn't get relayed.

Just tested seems create_agent and create_channel work as expected.
cargo test --test create_agent
...
Event found at ethereum block 278
test create_agent ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 87.78s
...

cargo test --test create_channel
test create_channel ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 126.06s

you'll see that the template parachain execution and parachain relayer keeps restarting.

Yes, it's as expected and the log will be fine after we create agent/channel for template parachain.

Let me retest. 😄

I have confirmed the create agent and create channel tests pass, thanks! I think it might have been related to some of the changes I have in-flight on https://github.com/Snowfork/snowbridge/pull/972.


Turn off desktop notifications by default for new users.

Previously, it was a really unpleasant to join an active Zulip realm, because the moment you joined, you were bombarded with dozens of desktop notifications for new messages to every stream you were subscribed to by default. This isn't a theoretical concern: We've on-boarded hundreds of Zulip users at the Recurse Center, and since we have an active realm and lots of default streams, we have to have extra instructions to tell every new user to turn these two settings off as soon as they first log in.

Automated message from Dropbox CLA bot
@nicholasbs, it looks like you've already signed the Dropbox CLA. Thanks!

Personally I agree that we need to do something to change these settings because they're definitely wrong for an established realm and it's annoying for one of your first things to do to be changing the notifications settings, but I think we should be thoughtful here, because IIRC these defaults were set that way to address an issue with newly created realms where users weren't noticing that other people were sending messages.
I'd be interested in other folks' thoughts on how to solve the problem for new teams effectively here; e.g. maybe we should flag notification settings as material we more strongly encourage users to read or see (e.g. making it its own page in the gear menu separate from the rest of "settings")
(@nicholasbs you should linewrap your commit message content to match the zulip commit message style)

Yeah in general I think this is the right move. We switched to this default but IMO experience shows that tons of people have found this quite annoying.

I can see how these notifications make sure people don't miss messages early on, but default notifications for everything seems like the wrong way to fix this problem, even for new realms.  Having this on by default encourages a pattern that (I assume) very few Zulip users actually follow once they understand the product (though you'd know better than me; I can only speak for RC's community, and perhaps we're an outlier).
A better approach might be more aggressive email notifications early on, a better tutorial/on-boarding, or even one-time desktop notifications for new users (e.g., to let them know there's a new message and point them towards the notification settings). But I think these are all largely orthogonal to this change.
That said, assuming you disagree with the above, either of the following would solve the current problem for RC:

A realm-level setting to set the default value for these two settings.

The ability to set these settings when you invite new users (e.g., two checkboxes in the dialog that comes up after you select, "Invite coworkers" from the gear menu).

Yeah honestly I'd be happy to just merge this and think about how to advertise the notification settings better in a new issue about adjusting the onboarding emails.  I'll let this sit a day for further commentary though since it is a significant shift.
I think we should put a note about this into a new changelog.md file that can be used to track major changes that folks might want to read about when upgrading.
@nicholasbs I assume you've tested this change?

I guess it's probably worth including in this at least a small change to templates/zerver/emails/followup/day1.text item 3 explaining briefly something about how by default @-mentions and PMs result in desktop notifications, sounds, and "missed message" emails but that you can adjust these settings either for individual streams on that stream's settings page or for the new stream default on the overall settings page's notifications section.

I tested this manually by creating a new user via manage.py and verifying that those two checkboxes were unchecked by default for that user in their settings. Is there any additional testing I should do? I couldn't think of a meaningful automated test to write.
I'm happy to take a pass at updating the followup email templates (I assume the HTML one would need to be updated as well) and add a changelog, though I'm busy tonight and traveling the next few days, so that likely won't happen until early next week.

You should probably create a new user via the actual signup flow and do the
same checkbox test, since it is a different codepath.
If you haven't done this before in the dev VM, the confirmation emails just
get printed out to the manage.py console.
I think early next week is a fine timeline for addressing the rest.
    -Tim Abbott

On Wed, Oct 7, 2015 at 7:22 PM, Nicholas Bergson-Shilcock <
<EMAIL_ADDRESS>wrote:

I tested this manually by creating a new user via manage.py and verifying
that those two checkboxes were unchecked by default for that user in their
settings. Is there any additional testing I should do? I couldn't think of
a meaningful automated test to write.
I'm happy to take a pass at updating the followup email templates (I
assume the HTML one would need to be updated as well) and add a changelog,
though I'm busy tonight and traveling the next few days, so that likely
won't happen until early next week.
—
Reply to this email directly or view it on GitHub
https://github.com/zulip/zulip/pull/141#issuecomment-146363307.

@timabbott Ok, I think this is all set:

I've created a new user (by clicking "Register" and then using the activation link printed to the console) and verified that the two checkboxes under settings were unchecked.
I've added a changelog.md.
I've added some copy to day1.html and day1.text.
I fixed the line-wrap on my commit message (and squashed my commits).

Please let me know if anything looks amiss!

OK, awesome, merged!
I'd definitely be happy to hear any suggestions for further things we can do to improve the experience and onboarding around notifications now that we've done this.

Maybe use heuristics to detect new users who aren't yet in the habit of checking Zulip, and show them (only) more notifications. You could also batch. Wait till a few messages come in, then be like: "See 5 unread messages in 'code > desktop notifications'". Once people are checking back often, stop sending them notifications of this type.


documentation glitch: timepicker doesn't work with type="date"

The example in the docs shows using a timepicker like this:
<input type="date" class="timepicker">

    $( document ).ready(function() {
      $('.timepicker').pickatime();
    });

Expected Behavior
I'd expect this usage to work like in the example. 😃
Current Behavior
A date input is rendered with a placeholder of tt.mm.jjjj (OS language is set to German, it's probably dd/mm/yyyy on English systems).

The picker itself works. But if you pick a time, the value is not inserted because the value doesn't match any date format. A warning is raised in the console: The specified value "12:00PM" does not conform to the required format, "yyyy-MM-dd".
Possible Solution
Change the docs to use an input of type="text" instead, which is already used in the sample on the page itself. 😃
Steps to Reproduce (for bugs)
Codepen: https://codepen.io/anon/pen/mwKXry
Context
This is just an inconvenience, nothing groundbreaking.
Your Environment

Version used: v0.99.0
Browser Name and version: Chrome 59
Operating System and version (desktop or mobile): Windows 10 desktop

https://github.com/Dogfalo/materialize/pull/4868

Oh great, that happens when I search issues but not PRs.. 😂
Sorry..


Test the possibility to upload zktypes to crates.io

This crate may be built only with rslang fork of the Rust. Is it possible to upload crate, which is not compiling with the original rustc to crates.io?
This should be tested and if not, we would stick with the "GitHub link" way of specifying dependency for this crate.

[x] #9

Uploading crate is possible.
Still there is an issue with team access to the crate. We should check if the team access is really working fine: all the members of the team must be able to update crate and yank versions.


Merge identity/1.10.2-rel back to main

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Comprehensive reference and guide

Brief

Update README file

Activities

This PR sets to provide documentation for the deroll project and its router and wallet functionalities

I configured typedoc myself, using the monorepo guidelines described at https://typedoc.org/api/#md:monorepos--workspaces. I even tried the upcoming beta version, which improves support for monorepos, among other things.
Documentation is generated ok, but I don't like the result very much.
I'll try next week to follow another strategy, which is using VitePress for a docs website, and generating markdown from JSDoc into a VitePress website.
If that doesn't work well either, I'll reevaluate the options.

Documentation already published at https://deroll.dev


Bug Report: Databricks typo in policy definition for private endpoints

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform:
azure provider:
module:
Description
Describe the bug

Minor typo in policy definition referring to "Databrics" instead of "Databricks".
Steps to Reproduce

Screenshots

Additional context

@juanandmsft thanks for raising this. PR in progress, just needs testing before merge.

This is now merged to the policy refresh branch, and will go live with the next major refresh release. Closing as no further action required.


how to use many to many relationships

Hello thk for your generator.
how to use many to many relationships ?

Hi,
At this moment is not possible. Maybe in the next version.
Thank you.


Go Router state.uri.queryParameters are null

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Install Go Router version 12.0.1
Setup a Path and in the builder GoRouterState log state.uri.queryParameters
Notice that state.uri.queryParameters is null

Expected results
state.uri.queryParameters should not be null if there are query parameters present int the url
Actual results
state.uri.queryParameters returns null
Code sample
Code sample
 GoRoute(
                  path: Routes.reset_password_screen,
                  name: Routes.reset_password_screen,
                  builder: (BuildContext context, GoRouterState state) {
                    RouteStream.routeStream.add(state.name);
                    final String? code = state.uri.queryParameters["oobCode"];
                    if (code == null) {
                      return const NotFound();
                    }
                    return ResetPasswordScreen(
                      code: code,
                    );
                  }),

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
 Flutter (Channel stable, 3.13.9, on macOS 13.4.1 22F770820d darwin-x64, locale en-US)
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d211f42860 (4 days ago), 2023-10-25 13:42:25 -0700
    • Engine revision 0545f8705d
    • Dart version 3.1.5
    • DevTools version 2.25.0

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/la.jamessaulsberry/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 231.9161.14

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/la.jamessaulsberry/Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • Alcatel 5004R (mobile) • QOFYWSINAMZHJZEM • android-arm    • Android 10 (API 29)
    • macOS (desktop)        • macos            • darwin-x64     • macOS 13.4.1 22F770820d darwin-x64
    • Chrome (web)           • chrome           • web-javascript • Google Chrome 118.0.5993.117

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Closing this as a duplicate of https://github.com/flutter/flutter/issues/137513. Please follow up on it for updates.


Lidar point cloud accuracy

The point cloud data of vehicles got from Carla is not presenting its real shape. All vehicles are considered as box like objects which is quite from real world data. This issue have been existing since when lidar has been introduced. And also sensor noise could be considered to add into the sensor data. (e.g. the floor should not be exact flat)
Another issue is that when enabled lidar processing, the server is running much lower sometimes.

Duplicated of #423.


Route aliases please!

It would be great to be able to alias routes, since sometimes it makes sense to nest routes based on which layout they use, but I don't want to show that in the URL
/basic/home, /basic/article/ and /minimal/some-other-thing
I want to just be able to use /home and /article but still use the nested views.
Can almost do this using route.redirect, but the route changes in that case

I tried implementing this by copying a few chunks of code from router.redirect, and turns out that doesn't work for nested routes with multiple route-variables. I wonder if it's related to #44 and would be fixed if that's fixed
E.g. router.alias({'/c/a/:foo/b/:bar': '/a/:foo/b/:bar'}) blank page

Thanks, fixed the test case.

Yup that works!
Here's what I have: https://github.com/vuejs/vue-router/compare/master...cheapsteak:alias?expand=1
I'm not really happy with the amount of code duplication I have though, pretty much copied everything related to redirect so lots of dupe code.
Also not sure if there needs to be a separate recognizer for redirects and aliases
Let me know if you'd prefer to write your own implementation or if I should make a PR.

I've merged your implementation and reduced the code duplication in https://github.com/vuejs/vue-router/commit/94159f51aa6788faf4f75432f76696a35b3aa6d3 :)

Thanks so much :D