force matplotlib backend to Agg in unSupervisedLearning

Issue Description
What did you expect to see happen?
when we run the test test_dataMiningHierarchical.xml in tests/framework/PostProcessors/DataMiningPostProcessor/Clustering
we get the following (highlighted in red the suspicious parts) and a final seg fault (see attached file).
This issue may related to #702
What did you see instead?
(    0.07 sec) STEP SINGLERUN           : Message         -> ***       Beginning run       ***
(    0.07 sec) SCIPY                    : Warning         ->  The ground truth labels are not known a priori
WARNING: QApplication was not created in the main() thread.
(    1.68 sec) PointSet                 : DEBUG           -> Printing data from "DataSets" to CSV: "dummy.csv"
(    1.71 sec) STEP SINGLERUN           : Message         -> ***       Run finished        ***
(    1.71 sec) STEP SINGLERUN           : Message         -> ***     Closing the step      ***
(    1.71 sec) STEP SINGLERUN           : Message         -> ***        Step closed        ***
(    1.71 sec) SIMULATION               : Message         -> -- End step Hierarchical of type: PostProcess                  --

(    1.71 sec) SIMULATION               : Message         -> -- Beginning step output of type: IOStep                            --
(    1.71 sec) STEP IOCOMBINED          : Message         -> ***  Beginning initialization ***
(    1.71 sec) STEP IOCOMBINED          : DEBUG           -> jobHandler initialized
(    1.74 sec) STEP IOCOMBINED          : DEBUG           -> for the role Output the item of class OutStreamPlot   and name PlotHierarchical has been initialized
(    1.74 sec) STEP IOCOMBINED          : Message         -> ***    Initialization done    ***
(    1.74 sec) STEP IOCOMBINED          : Message         -> ***       Beginning run       ***
(    1.74 sec) OUTSTREAM PLOT           : DEBUG           -> creating plotPlotHierarchical
/Users/alfoa/miniconda2/envs/raven_libraries/lib/python3.7/site-packages/matplotlib/axes/_axes.py:4204: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  (isinstance(c, collections.Iterable) and
QObject::startTimer: Timers can only be used with threads started with QThread
(    1.98 sec) STEP IOCOMBINED          : Message         -> ***       Run finished        ***
(    1.98 sec) STEP IOCOMBINED          : Message         -> ***     Closing the step      ***
(    1.98 sec) STEP IOCOMBINED          : Message         -> ***        Step closed        ***
(    1.98 sec) SIMULATION               : Message         -> -- End step output of type: IOStep                             --

--------------------------------------------------
There were 1 warnings during the simulation run:
(1 time)  The ground truth labels are not known a priori
--------------------------------------------------
(    1.98 sec) SIMULATION               : Message         -> Run complete!
../../../../../../raven/raven_framework: line 72: 53706 Segmentation fault: 11  $PYTHON_COMMAND -O $RAVEN_DIR/framework/Driver.py "${ARGS[@]}"

Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

It will cause the run crash, not wrong results.  No email is needed to be sent to the users.


[Create New Issue]:  Add Area Calculator

Calculator Functions
I want to add area calculator which will take respective inputs and it will calculate area.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I want to work on this.

/assign

i want to work on this.

/assign

/assign

@Anjalih11   create your own pr!
in case of any queries feel free to reach out to us on discord !

please assign this issue o me


Remove remaining $ref statements

Change-type: patch
Signed-off-by: Lucian Buzzo<EMAIL_ADDRESS>

@balena-ci I self-certify!


Create 3D models

Use https://spline.design/ for interactivity and design

If someone can provide ideas for designs I will do them


keeping contract dependencies up to date and adding events to contracts

I updated all the instances of libraries that had been changed, like BasicMathLib.
Also added events from libraries to the contracts that use them

Codecov Report

Merging #81 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #81   +/-   ##
=======================================
  Coverage   98.92%   98.92%
=======================================
  Files          26       26
  Lines        2412     2412
  Branches      365      365
=======================================
  Hits         2386     2386
  Partials       26       26

Impacted Files
Coverage Δ

...okenLib/truffle/contracts/TokenLibTestContract.sol
100% <ø> (ø)
:arrow_up:

TokenLib/truffle/contracts/BasicMathLib.sol
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Manual build

It would be nice to trigger a manual test/build/deploy after setting up a repository.

This will most likely be part of the next release. At least triggering the full test / build / deploy process, I am not sure if single tasks against branches will be supported with the next release or one of the following.

added to the todo list https://trello.com/c/IQjYmpXf - in consideration for the next release


Expose judgment timestamp as a timeline facet

We currently offer a "Judgment action timestamp" facet which gives the timestamp of the action which last set the judgment on each cell:

Because these are time values, as a user I would expect this to be a time range facet instead.
Proposed solution
Change the GREL formula defining this facet to convert the timestamps to dates and use the time range facet instead. This requires being able to do this conversion in GREL itself, which is not supported yet (#608). It can be done in other expression languages but it would be better not to rely on extensions to implement this core functionality.
Alternatives considered
Since the time range facet is not always very usable (just like the numeric facet, the binning is not configurable #2329 #215), it might actually become less usable. Perhaps improving the time range facet is a prerequisite.
Additional context
Brought up by @allanaaa in a documentation meeting.

@wetneb are you sure about that link to issue 2684 ? seems like that's a PR that only changes CSS padding

Thanks, it was probably introduced by GitHub's annoying auto-complete feature.

What are the units? ECMAScript Time Values (ie msec), seconds since the Unix epoch, or something else?


Cannot reference WindowsAppSdk and a WPF library in the same project: There was no runtime pack available for win10-arm

Describe the bug
I'm trying to build a class library that references both another class library (with useWPF set to true), and Microsoft.WindowsAppSdk. The combination of these two references in this one project seems to be incompatible, as I immediately start seeing these errors, and so far, nothing I've tried has resolved it.
There was no runtime pack for Microsoft.WindowsDesktop.App.WPF available for the specified RuntimeIdentifier 'win10-arm'.		C:\Program Files\dotnet\sdk\7.0.102\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets	448
There was no runtime pack for Microsoft.WindowsDesktop.App.WPF available for the specified RuntimeIdentifier 'win10-arm-aot'.		C:\Program Files\dotnet\sdk\7.0.102\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets	448

Even after making sure I have the latest .NET SDKs and Visual Studio 2022 updates, this occurs. I'm not specifically targeting ARM64 in any way; my build configuration is set to "Any CPU".
I originally posted a bug report about this to dotnet/sdk, as there was an earlier bug report there that had a similar error message, but after some thought, I figured this might be a slightly better place to post it.
Steps to reproduce the bug
I created a minimum reproduction of the issue I'm facing here: https://github.com/JaykeBird/RuntimePackErrorRepro
To create this on your own:

In a new solution, create a WPF class library.
In this library's csproj file, reference multiple .NET runtimes in the <TargetFrameworks>, such as net6.0-windows;net7.0-windows. I don't think referencing multiple runtimes is actually necessary, but I've done it as it reflects my larger library where I first encountered my issue. Also make sure the line <UseWPF>true</UseWPF> is present.
In this same solution, create another WPF class library.
In this second library's csproj file, set the <TargetFramework> to net6.0-windows10.0.19041.0.
Also with this second library, add a project reference to the first library and also add Microsoft.WindowsAppSdk.
Try building the second project.

Expected behavior
I expect the library to build without this error occurring.
Screenshots
No response
NuGet package version
Windows App SDK 1.2.2: 1.2.221209.1
Packaging type
Unpackaged
Windows version
Windows 11 version 22H2 (22621, 2022 Update)
IDE
Visual Studio 2022
Additional context

Using Visual Studio 2022 17.4.4 (I also have Visual Studio 2019 installed, but I'm not using it in this scenario)
Output of dotnet --info (I know there's a lot of runtimes, I can't seem to figure out how to remove the older ones):

C:\Users\jacob>dotnet --info
.NET SDK:
 Version:   7.0.102
 Commit:    4bbdd14480

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.102\

Host:
  Version:      7.0.2
  Architecture: x64
  Commit:       d037e070eb

.NET SDKs installed:
  3.1.426 [C:\Program Files\dotnet\sdk]
  5.0.103 [C:\Program Files\dotnet\sdk]
  5.0.408 [C:\Program Files\dotnet\sdk]
  5.0.416 [C:\Program Files\dotnet\sdk]
  6.0.202 [C:\Program Files\dotnet\sdk]
  6.0.405 [C:\Program Files\dotnet\sdk]
  7.0.102 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.21 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  arm64 [C:\Program Files\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\arm64\InstallLocation]
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

WinAppSDK does not support Arm32 like WPF. Marking as documentation so we can add this limitation to our docs.
We recommend editing your VS proj to not include Arm32:
<Platforms>x86;x64;ARM64</Platforms>

I've been building for AnyCPU thus far, so I'll try the platforms line and will report back.
A more actionable error message or some way to detect this issue would be nice, but I'm suspecting there's some form of limitation that makes that not possible.

Okay. I actually wasn't aware that WPF supported Arm32. I've been building for AnyCPU thus far, so I'll put in that platforms line and report back.

I added that Platforms line to both the base WPF project and the referencing project (in my repro project https://github.com/JaykeBird/RuntimePackErrorRepro ), I still get the same result.

I'm open to admitting there might be something on my computer that needs to be reset/reinstalled/cleaned out, but I've made sure I'm on the latest stable version available of .NET 7, Visual Studio 2022, and Windows. Trying to clean the solution (either via Visual Studio or dotnet cli) fails with the same error, and deleting the .vs folder in the solution doesn't make a difference.

Okay, I've figured it out!
It's not the Platforms line that was needed. Instead, it was the RuntimeIdentifiers line.
<RuntimeIdentifiers>win10-x64;win10-x86;win10-arm64</RuntimeIdentifiers>


Internal Triton PTX codegen error

When I try to run the tutorial on RTX3080, it occurred:
Exception has occurred: BackendCompilerFailed
compiler raised RuntimeError: Internal Triton PTX codegen error:
ptxas fatal   : Value 'sm_86' is not defined for option 'gpu-name'

You can suppress this exception and fall back to eager by setting:
    torchdynamo.config.raise_on_backend_error = False
  File "<string>", line 21, in _layer_norm_fwd_fused_single_pass

During handling of the above exception, another exception occurred:

  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/model_optimization.py", line 46, in compiler
    return cuda_graphs_wrapper(gm, example_inputs, pool=pool)
  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/implementations/cuda_graph.py", line 40, in cuda_graphs_wrapper
    model(*inputs)
  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/optimizer/layer_norm.py", line 29, in layer_norm_wrapper
    return layer_norm(v, layernorm.weight, layernorm.bias, layernorm.eps)
  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/implementations/layer_norm.py", line 319, in layer_norm
    return LayerNorm.apply(x, weight, bias, eps, implementation, use_rms_norm)
  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/implementations/layer_norm.py", line 290, in forward
    implementation[(M,)](
  File "<string>", line 42, in _layer_norm_fwd_fused_single_pass

The above exception was the direct cause of the following exception:

  File "/home/zonlin/kernl/openclip-kernl/kernl/src/kernl/model_optimization.py", line 50, in run
    return original_model.forward2(*args, **kwargs)

All envs are set: python3.9, torch=1.12.1...

Which tuto is it?

@pommedeterresautee  yes, I used other models. But I think this error has no relation to what model I use.

@pommedeterresautee  Hello, any solutions?

can you retry with last version (based on PyTorch nightly, etc.)
tbh, never saw this kind of error. Let's see if this happens again...

Tried. But still the same error.

Can you provide a short script giving this error ?


RFC: use codepush for PR QA and faster releases

codepush

This is an exciting opportunity. Reviewing PRs would be a nice-to-have, but the ability to ship hot-fixes or save days of release time (and so start to release more often) would be huge. I tend to agree that the slowness and irreversibility of the current process makes us very cautious.
Of course, the devil will be in the details. And adding another dimension (of which release and bundle someone's on) to the already confusing mix of beta/store, staging/production, simulator/device, and feature flag considerations could create even more confusion when it comes to tracing errors.

the most confusing parts right now are not the actual releases, since they are just 2 scripts that work very easily. and codepush would add another script. that part is fine.
the harder part is the scheduling/QAing, which I'm trying to ease with this rfc. so my plan is to not complicate the release docs much more besides the js vs native code, and to uncomplicate by having an easy release/hotfix when we need it.

Love it ❤

whoa. this sounds like the future, TBH. would be huge if we can just release whenever we want and QA much more easily.
One thing we should get a sense for before committing: how much will it cost? In the pricing section, I see 240 build minutes per month and then $40 per month per "build concurrency" and $99 per month per "device concurrency"...I have no clue what that means. Do you understand it @pvinis ?

@mdole for pricing, it would be free, as we don't need to build with them. my plan is to build in circle, and just deliver it to appcenter only for the OTA part.
I'll verify it's actually free and possible again, but that's how I've used it before.

I'm very excited about the DX possibilities of Codepush: being able to run arbitrary branches on a device by just selecting a bundle from a dropdown seems like a small miracle to me.
But I'm sceptical about going full CD, partly for the reason that I mentioned in my comment above. This is a good article about trying out Codepush with a complex app, and how in the end they decided not to use it:
https://www.matthewsessions.com/blog/code-push/
There are a lot of subtle payoffs that we would need to think about before committing to a new set of processes.
 I just think we need to be realistic about what we're likely to gain from it.

A little update here.
I want to make this RFC mostly about PR testing first.
I see some people are not too familiar with how things work on codepush, and I see that we definitely need to try out some things first until we are all comfortable with how the whole system works and what control we have over it. So I would like to slightly pivot this RFC for just the PR testing before merging first, and once we are done with that, we can evaluate how/if we want to move further with codepush and use it for hotfixes, and even later if/how we want to use it for releases.

So Mounir said Apple "may not like." we need to make sure that whatever we do is within the bounds of the developer agreement we sign, or there is the problem that we could be removed from the store.

2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. ...

Certainly we can't add features or change functionality.

I don't know about that.

3.3.2 Except as set forth in the next paragraph, an Application may not download or install executable code. Interpreted code may only be used in an Application if all scripts, code and interpreters are packaged in the Application and not downloaded. The only exceptions to the foregoing are scripts and code downloaded and run by Apple's built-in WebKit framework or JavascriptCore, provided that such scripts and code do not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store.

it mentions not changing the "primary purpose" of the app, and the "intended and advertised purpose". Which in my mind we have not changed since I joined artsy. The app allows users to buy and sell art. 🤔

The only exceptions to the foregoing are scripts and code downloaded and run by Apple's built-in WebKit framework or JavascriptCore

This is the phrasing they added a while ago to explicitly allow code push; the "or JavascriptCore" part didn't used to be there (see for example this blog post that quotes an earlier version of this paragraph, without the JSC allowance) (remember when Meteor was the future?!). I wonder whether they'll change it soon, now that Hermes is the default runtime instead of JSC?
Anyway, there are plenty of examples of apps that use code push on the app store, so I don't think we should be too worried about that. But I'm still not convinced about the gains we would get from using it for updates, so I agree that we should start by trying it out for PR testing.

I think we should be looking at the spirit - which is that they want to review what's on the store, and they don't want you changing it after the fact so much. In addition, I think there's an aspect of user consent here. I consent to changing the software on my phone when I download things from the App Store. I personally don't want random bits of software installing itself without my awareness. Obviously for ease of use I don't want to be manually updating everything. However, we shouldn't think that we own the container on everyone's devices. The user owns their device not us. They should choose what goes on it.
For PRs though I think this is effing cool. We should all be able to test what colleagues are adding easily.

I know all that and it's a matter of when the updates happen - Apple asks me if I want to have it automatically. I don't put google maps on my device so they don't track me. Financial apps mostly put up a forced app update flag to download updates from the store. And to be clear having a client server approach where we can change the server after the fact is adding new functionality. It's just that the user should control when software is installed. Otherwise we are close to malware. Even if we will never ever in 100 million years do something janky with our software, the behavior looks similar. Nobody should trust anyone ever with software. I certainly don't trust WhatsApp or TikTok, for instance, and I long ago deinstalled the Facebook app. Maybe I overindex on threat modeling, but better safe than sorry, especially as we become more of a marketplace.

I'm on board with this!

Thanks for writing this up!
I am on board with trying out codepush for PRs + hot fixes. Not on board with replacing our existing release process with code push.
There are anecdotal issues quoting App Store rejections explicitly calling out code push all of them after 3.3.2 was updated: https://github.com/microsoft/react-native-code-push/issues/1898, https://github.com/microsoft/react-native-code-push/issues/1297.
And I agree with Kathy the spirit of the law is Apple's wants to review your code when you add significant functionality.
The quoted guidelines interpretation is coming from Microsoft who owns codepush so it is important to take it with a grain of salt. It sounds from 3.3.2 that code push is allowed with the callout for JSCore, ...but it also sounds like it is contradicted by 2.5.2. How it is applied is up to Apple and I don't like the idea of banking our continued release of the app on that. Worth mentioning previous companies that provided hot code push functionality assured people that they were in compliance with App Store review guidelines, then one day all those apps started getting rejected: https://news.ycombinator.com/item?id=13817557 The mechanism was different and more risky (Obj-C runtime magic vs js updates) but I worry the risk remains without some specific assurances from Apple.

Resolution
We decided to do it as a PR List. Everyone agrees that using codepush as a way to test a PR with no native code before merging to main is the best gain for us.
Most people are not into using/replacing our existing release ways. Something to be looked at again in the future.
Level of Support
1: Overwhelming positive feedback. (for the PR List part.)
Next Steps

[ ] I make a tech plan (that I have started) for how we set up the PR list.
[ ] Get the tech plan approved, and further work continues from there.
[ ] Implement PR list.

Exceptions
N/A

As mentioned in Slack, perhaps we can give this a try with Folio to get some experience and then reevaluate in terms of Eigen? A trial run.


Keep Prometheus 1.8.x around on download page for a while

I think we should keep Prometheus 1.8.x on the download page for a few months, as it's needed to access data from 1.x installations and it may take a few releases for 2.0 to fully stabilize.

We never got to do this, and by now it doesn't make sense to advertise 1.8 anymore.


Identity Verification Providers text overflowing in Management Console

Describe the issue:
In the Management Console, the text "Identity Verification Providers" found at Main > Identity > Identity Verification Providers is overflowing.

How to reproduce:

Login to the Management Console
See Main > Identity > Identity Verification Providers

Expected behavior:
The gray header area should cover the entire text.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-7.0.0-rc1-SNAPSHOT
OS: Mac

Reducing severity and priority as the issue is related to the management console

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


apiv2: depsolve and build should be 2 jobs and therefore 2 different endpoints

Actually splitting these jobs up will be handled by depsolving in the workers.
/compose: should depsolve (should we rename the endpoint to something more obvious?)
/build: build the job which was previously depsolved in /compose
As a first iteration this can be a purely cosmetic change, where everything happens in /compose, once the job is split up in the background /build can do the actual build job.
This is useful to for instance call /compose (depsolve) on the review screen in image-builder-crc; so we can verify the validity of a request before trying to build it.

What's open still is what exactly the requests should look like. If /compose just does a depsolve, what exactly does it need, it probably will not need the upload targets.

Question: should builds nest under composes, or reference them?

Question: should builds nest under composes, or reference them?

Either could work; but /composes/${id}/build as a POST makes sense yea, I think I prefer that even.


Before flag in restore

Output of restic version
restic 0.9.5 compiled with go1.12.4 on linux/amd64

What should restic do differently? Which functionality do you think we should add?
It would be nice to have a before (and maybe after) date flag in the restore command.
What are you trying to do?
Use case is that you know when bad files/bugs appear and you want the latest snapshot before a specific date, instead of just the latest.
Did restic help you or made you happy in any way?
Very :D

Since restore command requires a snapshot ID, how is it possible to obtain programmatically ID of a snapshot made at given date?

@giskou Can't you just 1) snapshots, 2) in the list of snapshots, locate the last one before the date you are concerned about, 3) restore that snapshot? It's just one extra command to run.

@rawtaz If restic should be used from a script / pipeline, which is given restore date as a parameter, what is recommended way to do 2) programmatically?

@eprigorodov In the list of snapshots you have the dates and the snapshots ID. There's many different ways to do it, here's one using awk:
bash-3.2$ cat apa.txt
e953e6fb  2020-05-11 04:29:58  foo.local                /what/ever

746f1121  2020-05-12 04:01:01  foo.local                /what/ever

98d3115e  2020-05-13 03:02:19  foo.local                /what/ever

4ca4fdcd  2020-05-14 03:24:39  foo.local                /what/ever

6d25cfbd  2020-05-18 00:33:02  foo.local                /what/ever

bash-3.2$ cat apa.txt | awk '/^\s*$/{next;} $2=="2020-05-14"{print line}{line=$1}'
98d3115e

bash-3.2$

There are probably cleaner ways, but this one is simple enough that you can use it in a script if you want (obviously while handling the case where you don't get any snapshot ID out of it).
I think this use case is rather rare. Most people restore manually, and those that have it scripted somehow either have some input from a user after showing them a list or offering them some search that can yield a snapshot ID in another way.

Since restore command requires a snapshot ID, how is it possible to obtain programmatically ID of a snapshot made at given date?

@eprigorodov that's my main issue. Such a feature will not require an id. It's more or less the same as latest but with a specific date.

In the list of snapshots you have the dates and the snapshots ID. There's many different ways to do it, here's one using awk:

@rawtaz Of course something like this is possible, but it can get complicated very fast.

There are probably cleaner ways, but this one is simple enough that you can use it in a script if you want (obviously while handling the case where you don't get any snapshot ID out of it).

The cleanest way would be that restic deals with this internally, so every run, on every shell version, with no extra tools (awk,sed,grep) will give you exactly the same results.

I think this use case is rather rare. Most people restore manually, and those that have it scripted somehow either have some input from a user after showing them a list or offering them some search that can yield a snapshot ID in another way.

Fair enough. I still think that such a feature will not be that hard to implement and will benefit at least some.

EDIT: The above grabs the last snapshot ID before the date you provided. If you just want the snapshot ID for a given date, that's even simpler. Also note that it won't work if there's multiple lines of paths for the snapshot you want, it will have to be adjusted for that. This is just a basic example.

As you can see such an approach has a few "gotchas"

I think you are overcomplicating it and that restic shouldn't cater to every single use case. It, if anything, would become too complex. Do few things and do it well. But that's just my opinion. FWIW I don't think the proposed solution is very complex at all, it's literally one single command to get you 99% of the way. If you add a couple more lines you're done. And having to adjust and run different commands on different platforms is already something you have to do anyway, even if you were to use a built-in feature like this in restic, so you already crossed that boundary.

@rawtaz Point-in-time restore is a primary use case for keeping multiple backup snapshots in general. If all restore operations only used the "latest" snapshot then there would be no need in the whole restic machinery.
And manual restore is only feasible while the data to be restored is simple as single directory. Consider repeating the "awk" approach for related snapshots from several hosts. Think of restore scenarios that have further steps after extracting files, like database import. Automation becomes necessary in any infrastructure larger than personal space and/or when multiple operators are involved.
Compare the snipped above with the following possible way:
restic restore latest --before 2020-01-01 --target ...

Would you say that this feature is not needed at all or just that it has low priority?

Technically, this change should be simple: just handling a new --before command line filter in addition to existing --tag, --host, --path,
and then changing a single line in snapshot_find.go/FindLatestSnapshot():
		if snapshot.Time.Before(latest) || !snapshot.Time.Before(before) {
			return nil
		}

Sorry for the late reply, been busy.

Would you say that this feature is not needed at all or just that it has low priority?

Needed or not isn't something that can be answered as the concept of needed is relative and individual. I think it's a nice to have rather than need to have, if that answers your question. People restoring manually don't need this, and those that automate/integrate their restores will have written scripts/integrations already, and will have absolutely no problem to grab the list of snapshots and pick the one they're interested in (or as I think I mentioned before, will already have a UI for it anyway). It's a pretty specific use case.
Regarding priority, it's currently not realistic that a core developer will write it (as there's a lot of other more important things to focus that time on), that's pretty certainly not going to happen in the foreseeable future. Possibly a PR would be considered though, if written properly :)

Tested a workaround with helper script, as suggested in the comment above: Python script gist. Usage:
restic snapshots --json | python3 find_snapshot.py <before|after> YYYY-MM-DD.HH:MM+HH:MM

Some details can make the task too complex for an inline awk program: semantics of input date and time zones.

As mentioned in the same comment, the requested restore date can be interpreted in several ways:

latest snapshot taken before the given date,
snapshot taken exactly on the given date,
earlest snapshot taken after the given date.

At least our ops were not able to tell if preferred mode would be "latest before" or "earliest after", they need both. The case with exact date might be rare due to backup retention.

Backup and restore may take place in different time zones.

To the credit of restic, it saves snapshot timestamps with time zone information.
When restoring, operator can /and most often will/ enter desired restore date without indicating any time zone. In that case the only reasonable assumption is the current local time zone. Even in the same location, the time zone of requested date may differ from the time zone of snapshot (due to DST).
The helper script should consider these details when comparing points in time.


RaspberryMatic <IP_ADDRESS>00621 reports running low on disk space for /media/usb1 while creating a backup

Describe the bug
While creating a backup (automated via cronjob or manual via WebGUI), low disk space for /media/usb1 is being reported.
System has been working stable and correctly before.
No external SD memory card is installed!
To Reproduce
Steps to reproduce the behavior:
Backup via cronjob or manual system backup via WebGUI.
Tests showed diskspace runs low when the sbk file is being created and the tmp file still exists.
Expected behavior
Correct backup created.
Screenshots
None.
System information (please complete the following information):

Version : RaspberryMatic <IP_ADDRESS>00621
Hardware : TinkerboardS

Additional context
I am also having troubles with existing HMIP devices not communicating correctly, though no error is being reported.

Sorry, but if your system is running low on disk space while you are trying to create a backup, then you should switch to a larger USB stick or lower the amount of data that is required to be backed up. I can currently not see any way of fixing here something that is related to not enough disk space being available on your device.

In the meantime I've found the root cause of the problem. The backup script (started via the cronjob) tried also to backup the former backups stored under /usr/local/backup as well though it should have been excluded in the createBackup.sh . This caused an exponential increase of the backup files after a few days. I have no idea why this is suddenly happening. The problem happens when the /media/local/backup/ path is being used. After writing /usr/local/backup/ into the CronBackupPath file in /etc/config the problem disappeared.

@tnick61 Where does this /usr/local/backup folder come from? AFAIR this is not a directory path RaspberryMatic creates/uses itself.

@jens-maus Interesting. I installed RaspberryMatic on a TickerboardS with no additional SD card installed. The problem with the memory size started after upgrading RaspberryMatic to the latest release <IP_ADDRESS>00621. Using the df command from the root directory it shows that /dev/mmcblk2p3 is mounted twice ether to /media/usb1 and to /usr/local. Funny, they point both to the same directory! Meaning cd to /media/usb1 or cd to /usr/local end up in the same directory with the backup directory in it. usb0 is symlinked to usb1 as it should be.


Swift 4 - 'range(at:)' has been renamed to 'rangeAt(_:)'

I'm using your lib with the version 1.1.0
I got this error message for the file Match.swift.
The following are the affected lines:
117: let stringRange = try? match.range(at: i).asRange(ofString: source)
133: return try? match.range(at: index).asRange(ofString: source)
145: return try? match.range(at: groupIndex).asRange(ofString: source)

i had the following snippet in my podfile which caused the error:
post_install do |installer|
  installer.pods_project.targets.each do |target|
	target.build_configurations.each do |config|
	  config.build_settings['SWIFT_VERSION'] = '3.0'
	end

	puts "#{target.name}"
  end
end


Touch issue with GTK+3 applications in Rootston

For at least some touch devices, touch input doesn't work as expected with GTK+3 applications when using Rootston.
The same applications are running as expected in Weston.
Observed behaviour (Rootston): For GTK+3 UI elements (tested with Gtk.Button), there are signals emitted to the wrong GTK UI object and some expected signals missing at all.
Test application: The issue has been tested with a small GTK+3 app written in Vala: buttonbox.vala. The app has 3 GTK buttons, each connected to the following signals: clicked, pressed, released, enter, leave.
Test case:
Tapping button 1, button 2, button 2, button1 in this order. Tested with Rootston and Weston with WAYLAND_DEBUG=client. Logs with the signals emitted in each case are attached.
Test configuration:

Golden Delicious GTA04 board, TSC2007 touchscreen, kernel 4.19.12-letux+ armv7l, Debian Buster, GTK+ 3.24.2-3
Raspberry Pi 3B+, ADS7846 touchscreen, kernel 4.14.86-v8-rpi aarch64, PureOS, GTK+ 3.24.2-3 (only short test without logs so far)

Notes:

This problem doesn't seem to be present in all environments with touchscreens.
Trying wlroots touch demo doesn't show any unexpected behaviour
No problems with touch using X11 as well

Logs:
rootston-buttonbox-debug-log.txt
weston-buttonbox-debug-log.txt
Source code:
buttonbox.vala

Is it maybe fixed by https://github.com/swaywm/wlroots/commit/4f4d3cf2a25f7af022e51b861ef04f7c4a94b768?

Closing because this is a rootston bug. rootston ahs been removed from the wlroots tree.


Add support for json_decode($data, true)

The entire library right now only works if the calling code passes in both the schema and the data as it has been returned from json_decode($data).  It would be helpful for projects to be able to pass in the data and/or schema if it comes from a json_decode($data, true) call.
I'm thinking the simplest fix for this is to claim the mostly defunct Validator::CHECK_MODE_* constants and either use CHECK_MODE_TYPE_CAST or a new constant to allow the calling code to indicate which format the data is coming in.
It would be fairly trivial to then convert the data to the expected types for validation so not much of the actual validation code has to change.

I have application code which decodes JSON in the array style, but have to decode it again to validate against the schema. I'm in a situation where I have to either decode twice or rewrite the app code to use object style.
Is this a compelling enough case for adding this feature? Consider that the JSON structures can potentially be quite large and rewriting application code can be costly.


Delete .tmp files

If files are downloaded after having done one or more retries, the original .tmp files that did not result in a successful file download are not deleted.

I am closing this issue as it is fixed in the latest version.


Feature: Theming packages for autoform

I am still new to autoform and haven't used it that much (using mostly angular-meteor), but I was thinking, instead of defining html elements seperately and adding things like bootstrap-datepicker, would it not be nice to have theming packages?
e.g. have a default package aldeed:autoform and then install twbs:bootstrap-autoform which depends on aldeed:autoform and then overwrites some of the code to generate a standard bootstrap form with all the classes such as  btn success, form-input, form-group, row and col-md-4 etc.
Then if you got a project that uses bootstrap and you want to migrate it to some new trend, e.g material-design, you would simply go and install this new package autoform:material-design or whatever it might be called and without changing any html files or any code in the project, all forms magically update to material design.
Like I said at the top, I am still new to autoform and I don't know if it is practically possible to have packages that overwrite the autoform functionality and still stay up to day with versioning, but I figured it would be a good idea to look into it and it will help with the lifespan of autoform to live in production as opposed to the current usage of prototyping (and some admin routes where styling doesnt matter).
Right now, css can only do so much without the actual html content changing.
Just my 2 cents. Use it, don't use it :)

This is pretty much how it already works, except that the bootstrap theme package is currently included with the core package. Pulling that out into its own package is near the top of my to do list. Anyone can already create a theme package for any other framework.
Theme packages are currently primarily for overall form layout and default HTML field types. There isn't really a way to swap custom components just by swapping the theme package. One idea might be to document a standard component naming convention. For example, various autoform theme packages would all define advanced components with identical type names, so you could do type="DateTimePicker" for your form field and then simply swap theme packages to get variations of a date time picker. It seems like a good idea in theory, but in practice I suspect it won't work that well since many components would require additional packages. I don't know if it is worth the coordination effort.


Apply called with wrong number of arguments

apply is called with four arguments (here), but the contract expects three arguments (here).
This meant that all calls to apply would fail for the TCR that I deployed.
If I remove the listingID argument from the call to apply and update the contract ABI's to match (e.g. 0xafbbefb788e478d30f2aca7c8fc8b8271a9603a2), then the calls to apply succeed (see this commit)
Is this UI repo designed to work against an older version of the contracts? Am I missing something? I'm totally happy to submit a PR fixing this, if it is indeed a bug 🙂

ah, just saw more of that commit: https://github.com/humansTCR/tcr-ui/commit/da484c6ff39c5e03cf923a2374dd14f87e4f9695. looks good to me!

OK clear. Thanks for the detailed answer!


[Feature Request] Add a JwtClaim public property of type string to TokenAcquirerOptions for Pop advanced protocols

Why?
ATPop requires more than the Key
What?
Add a JwtClaim public property of type string to TokenAcquirerOptions

Released in 2.1.0.


Publish to Open VSX

Dear extension author,
Please publish this extension to the Open VSX marketplace.
Context
Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.
What is Open VSX? Why does it exist?
Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.
You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.
How can you publish to Open VSX?
The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

Done.
https://open-vsx.org/extension/adamraichu/font-viewer

That was fast, thank you!


Creating a test file

I assume this is also a test pull request? I'm closing since I don't think it's intended for merging :smile:.


Build failure: qpdfview

Steps To Reproduce
Steps to reproduce the behavior: try to build qpdfview.
Full build log on Hydra: https://hydra.nixos.org/build/272025147
Additional context
I attempted to git bisect the issue and ended up with:
1bcca7d66b0a052b703d029c4593434b84136455 is the first bad commit
commit 1bcca7d66b0a052b703d029c4593434b84136455
Author: Wolfgang Walther<EMAIL_ADDRESS>Date:   Wed Jun 12 18:31:45 2024 +0200

    qt: support structuredAttrs in qmake hook

    Tested qbs with and without __structuredAttrs.

 pkgs/development/libraries/qt-5/hooks/qmake-hook.sh         | 36 ++++++++++++++++--------------------
 pkgs/development/libraries/qt-5/hooks/qttools-setup-hook.sh |  2 +-
 pkgs/development/libraries/qt-6/hooks/qmake-hook.sh         | 28 ++++++++++++----------------
 3 files changed, 29 insertions(+), 37 deletions(-)

Looking at the log it looks like the qmakeFlags are not set/used properly, e.g. PLUGIN_INSTALL_PATH below:

make[1]: Entering directory '/build/qpdfview-0.5' g++ -c -pipe -O2 -std=gnu++11 -Wall -Wextra -D_REENTRANT -fPIC -DAPPLICATION_VERSION=\"0.5.0\" -DWITH_SVG -DWITH_SQL -DWITH_DBUS -DPLUGIN_INSTALL_PATH=\"/usr/lib/qpdfview\" -DWITH_PDF -DPOPPLER_VERSION=\"24.02.0\" -DPDF_PLUGIN_NAME=\"libqpdfview_pdf.so\" -DWITH_PS -DLIBSPECTRE_VERSION=\"0.2.12\" -DPS_PLUGIN_NAME=\"libqpdfview_ps.so\" -DWITH_DJVU -DDJVULIBRE_VERSION=\"3.5.28\" -DDJVU_PLUGIN_NAME=\"libqpdfview_djvu.so\" -DWITH_IMAGE -DIMAGE_PLUGIN_NAME=\"libqpdfview_image.so\" -DWITH_CUPS -DCUPS_VERSION=\"2.4.10\" -DWITH_SYNCTEX -DHAS_SYNCTEX_2 -DWITH_SIGNALS -DDATA_INSTALL_PATH=\"/usr/share/qpdfview\" -DAPP_DIR_DATA_PATH=\"data\" -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Isynctex -Iicons -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtPrintSupport -I/nix/store/b76svm0rpryy2vc70mcs8al73x9d2kb2-qtsvg-5.15.14-dev/include/QtSvg -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtWidgets -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtGui -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtConcurrent -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtSql -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtDBus -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/include/QtCore -Imoc -I/nix/store/0nifpiwvav0p4nh67w5vzy3xfdy2m50g-libglvnd-1.7.0-dev/include -I/nix/store/4xk5njji85yszys9hg8v2mml7wp4y8k1-qtbase-5.15.14-dev/mkspecs/linux-g++ -o objects/settings.o sources/settings.cpp

Notify maintainers

@raskin @wolfgangwalther
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.10.10, NixOS, 24.11 (Vicuna), 24.11.20240914.c60562f`
 - multi-user?: `yes

Add a :+1: reaction to issues you find important.

Hm. My commit is already on master and I can build qpdfview fine there. What am I missing?

Really not sure, I get the exact failure as on Hydra, also using nixpkgs master.


[[FEAT]] Add logout support

Exposes a new method in the strategy to redirect to the Telefonica Accounts logout endpoint
Closes #15

It should go in v1.1.0 when landed

Coverage increased (+0.7%) to 97.143% when pulling e9b263696806de6ae35289d2d93a4661bc6dc7d2 on issues/15 into 99fa0df74b8aaaab6d7ab41301a19aa3fb6e01af on master.

LGTM


New Evaluation: Legal

We would like to find or create an eval dataset that tests legal knowledge. Note that the LSAT exams do not actually test any legal knowledge.

[ ] Data processing code implemented
[ ] Evaluation implemented

This should be modeled after the BoolQ task in lm_eval/tasks/suerglue.py

This dataset is a good place to start for this issue.

This dataset is a good place to start for this issue.

https://arxiv.org/pdf/2009.03300.pdf has approximately 2000 US multistate bar exam questions.

https://arxiv.org/pdf/2009.03300.pdf has approximately 2000 US multistate bar exam questions.

Excellent! I look forward to it.

Excellent! I look forward to it.


How Do I use "onDrag" in version 0.6.0?

In 0.6.0, instead of using the closures willMoveToStickyPoint, didMoveToStickyPoint andonDrag you should override the methods  override func pullUpControllerWillMove(to stickyPoint: CGFloat) pullUpControllerDidMove(to stickyPoint: CGFloat) and pullUpControllerDidDrag(to point: CGFloat)
For more informations you can check this commit https://github.com/MarioIannotta/PullUpController/commit/4ceffcae014b24dfb0b04ca2749ee4676ad41b1e


The use of ${random-word} creates a new route with every 'cf push'

If I have a manifest.yml with the following entry:
host: cloud-services-test-${random-word}

Every time I push the application (cf push), it creates a new route, instead of reusing the one that is already bound to the application.
Observed this regression (about a week or two back, cf exhibited the right behavior with the same manifest.yml) with cf version 6.1.2-6a013ca as well as today's master build 6.1.2-91a805a.

Please re-open this one. It's a regression and it's going to drive people nuts.


Support list gist commits and list gist forks endpoints

Added support for list gist commits and list gist forks endpoints, including tests.
I was looking for a Go project to contribute to (as I'm still not very comfortable with Go) and I found that these two end points are missing (and no one has started working on them yet). Please let me know if I missed something in the guidelines :-)

Hey @beshrkayali, thanks a lot for your contribution, it is really appreciated!
This PR is off to a great start! I've left a few comments for style issues I've spotted, most of them are really minor and easy to fix. I've linked to sources so you can see where these style guidelines are coming from.
Thanks again, and I hope you enjoy learning more about Go and using it/making contributions! 💯

@shurcooL Thank for your feedback Dmitri! I've committed the necessary fixes.

A few minor comments, otherwise LGTM 👍

Thanks for the feedback @gmlewis, issues resolved.

Thanks, @beshrkayali!
Awaiting one more LGTM and then I will merge your changes.

Edit: One tiny issue to note is that the last few endpoints are actually implemented but not reflected in the google doc as Done.

What google doc? I'm not familiar with one.

@shurcooL ah, it's a spreadsheet actually not a doc. It's highlighted in the roadmap section of the README.

@shurcooL ah, it's a spreadsheet actually not a doc. It's highlighted in the roadmap section of the README.

just fyi, edit access to that doc should be open to anyone in the go-github Google group.

LGTM.
Huge thanks @beshrkayali! 🎉

Incorporated in https://github.com/google/go-github/commit/e4b1c2870fd8416f2193ab449a4c889a9134b036.
Thank you, @beshrkayali!

Thanks @shurcooL + @gmlewis 👍


Add DigitalOcean exporter

Prometheus exporter for various metrics about your DigitalOcean droplets, volumes, snapshots & networks and much more, written in Go.

Thanks!
Both of your status metrics are a bit weird. Usually you either use 1/0 to indicate the account is active OR have a 1 on the current status as a label. A mix of both is going to be difficult to deal with.

Thanks for that valuable feedback. I will look into that, just like I will look into the transmission-exporter comments you gave me. :+1:

I changed digitalocean_account_status{status="active"} 1 to digitalocean_account_active 1. If there was another metric, didn't find know you were talking about, please let me know. Thanks! :)


vite run dev error

The browser throws
vue-json-editor.vue:17
   Uncaught (in promise) SyntaxError: The requested module '/node_modules/vue-json-editor/assets/jsoneditor.js' does not provide an export named 'default'

version is @1.4.3

I guess is not support the vue3. My project is vue 3+.Thank you for support the vue3 by the npm package version 1.5.0 ~


cleanup + use unicode symbols

@wkchuang tagging you for fun here. Julia supports using a lot of characters outside the normal text ones, e.g. µ.  I am especially proud of my ℞X to check input X (℞ is the medical prescription symbol; so this is likely giving a prescription to a pharmacist lol I have no idea why I thought this was a good idea)


Add builder config implementation

Summary
A reference implementation of the RFC at https://github.com/paketo-buildpacks/rfcs/pull/241
Use Cases

As explained in the RFC.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

I'm going to mark this as a draft since the related RFC is also marked as a draft. Both seem dormant right now.

The RFC that this was a reference implementation for has been closed. Closing this.


Can you share the preprocessing steps of ShapeNetPart Dataset?

Hi, I have been able to train PointNeXt BasePartSeg model on ShapeNetPart however I would like to extend it to another dataset with a different number of classes and parts. When I run the evaluation, I get poor results. This leads me to believe the datasets have different augmentations and transforms.
I found the ShapeNetPart dataset from https://drive.google.com/uc?id=1W3SEE-dY1sxvlECcOwWSDYemwHEUbJIS and used it directly to get results. The website no longer has the ShapeNetPart dataset. Can you give me the preprocessing steps of the data in the link, so that I can compare with my dataset?

I do not think we used any preprocessing. We use the original dataset


clear OpenSSL thread error queue each time, might help with certain f…

…ailure cases.
It wasn't clear if this is absolutely necessary but it does follow the spec:
6d0835759b131748582cfccb694d16f59205bfe6
And apparently some people have run into problems if they don't do it this way:
https://github.com/nodejs/node-v0.x-archive/issues/1719
I think if you call it more than once it's supposed to give "more detailed" error messages with each invocation or something along those lines.

Could you try setup a spec for this?
I think messages should be joined by a line break. And please write to an IO instead of concatenation.

please write to an IO instead of concatenation.

I think the point here is that having multiple errors is extremely unlikely (which is why things work at all as they are). So this would likely make the average slower.

Are there specs somewhere else I can see as an example of mocking out LibCrypto?  Is that possible?  Do you still want an IO? (Yes it's very rare AFAIK).

I think the point here is that having multiple errors is extremely unlikely (which is why things work at all as they are). So this would likely make the average slower.

In that case, there is still a concatenation because message is initialized to "". Concatenating to an empty string might be optimized, though...

Yes, that should be fixed. Perhaps there's a way to combine 2 different desired properties: "no concatenation by default" and "add newlines". Something like this:
if !error
  error = get_error()
else
  error += "\n" + get_error()
end

Concatenating to an empty string might be optimized, though...

It is! It returns the non-empty string :-)

You'd like an exception whose message contains newlines?  Might that mess up logging and loggers or some odd?

I had hoped this would fix this bug: https://github.com/crystal-lang/crystal/issues/8108 but it turned out it didn't.  It might be worth pursuing sometime for "better OpenSSL error messages" but I lack the expertise to finish it at this point, love for anybody else to finish it, cheers!

After some further research, it appears that it's too dangerous to "trust yourself" to having cleared it perfectly before, and the safest option is to insert a call to ERR_clear_error before any OpenSSL call:
https://stackoverflow.com/questions/18179128/how-to-manage-the-error-queue-in-openssl-ssl-get-error-and-err-get-error
This PR is marginally useful for reporting purposes if anybody wants to finish it off, as well :)

So do we need a new issue to track this?

Yeah.


Define and document the ibm.com Library contribution model

The ibm.com Library is open source.  We would like to provide processes and possibly tools the support this model.  The DDS role will be to provide consulting to adopters and review/approve the contributions before they are merged into the code base.

Work finished.  Closing


Demo script not working on OAK-D

Using windows 11.
Python=3.11
depthai <IP_ADDRESS>
depthai-sdk 1.9.4
The following error is observed.
Using depthai module from:  C:\Users\Kukil\AppData\Roaming\Python\Python311\site-packages\depthai.cp311-win_amd64.pyd
Depthai version installed:  <IP_ADDRESS>
Setting up demo...
Available devices:
[0] 14442C10B1E393D000 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.SUPER
[14442C10B1E393D000] [2.2.3] [1.161] [StereoDepth(9)] [error] RGB camera calibration missing, aligning to RGB won't work
F: [global] [         0] [ThreadN] dispatcherResponseServe:925  no request for this response: XLINK_WRITE_RESP 1

Stopping demo...
=== TOTAL FPS ===
[color]: 29.3
[left]: 0.0
[right]: 0.0
  File "C:\Users\Kukil\Desktop\depthai\depthai_demo.py", line 656, in run
    self.instance.run_all(self.conf)
  File "C:\Users\Kukil\Desktop\depthai\depthai_demo.py", line 133, in run_all
    self.run()
  File "C:\Users\Kukil\Desktop\depthai\depthai_demo.py", line 317, in run
    self.loop()
  File "C:\Users\Kukil\Desktop\depthai\depthai_demo.py", line 373, in loop
    self._pv.prepareFrames(callback=self.onNewFrame)
  File "C:\Users\Kukil\AppData\Roaming\Python\Python311\site-packages\depthai_sdk\managers\preview_manager.py", line 148, in prepareFrames
    packet = queue.tryGet()
             ^^^^^^^^^^^^^^
RuntimeError: Communication exception - possible device error/misconfiguration. Original message 'Couldn't read data from stream: 'color' (X_LINK_ERROR)'

Please help.

Hi @kXborg , it seems like you have quite an old device, which doesn't have RGB calibration. Could you try recalibrating the device?

Hi @Erol444,
Thanks, it is working after calibration. There were a few hiccups, I am noting them down here in case someone faces the issue.

Submodules were not getting cloned (had to clone them individually) depthai_calibration and resources/depthai_boards.
Using the laptop screen for displaying ChAruco board is not a good idea. Good luck orienting that.
Minimum size of one square should be 2.2 cm. If your iPad / tablet is big enough, it might work. Mine is just 10.4 inch (squares were 1.4 cm). Got away with a chopping board and an A4 sheet finally.
It took me 29 captures for complete calibration.


Client - Getting warning of not enough balance when order is filled when using binance_papertrade

Describe the bug
For tracking purpose
While using binance_papertrade, we noticed that there are instances of the bot not recording the filled trades and getting a warning of hummingbot.core.network_iterator - WARNING - Not enough USDT balance to fill limit buy order on ETH-USDT. 6.2735640 USDT needed vs. 1000 USDT available. while the balance paper has more than enough to use.
Tested using different markets getting the same warning when getting a filled event and no data is recorded.
https://user-images.githubusercontent.com/73840223/168779387-de173d51-9d3f-4fc6-9c8f-a098042eb0d4.mp4
Steps To Reproduce

Setup Pure market making or Avellaneda using binance_papertrade
Set spreads tight enough to execute trades
Start the bot and monitor filled order events

Release version
development branch dev-1.5
Attachments
logs_pmm-binance-paper.zip

I have the same issue, in development 1.4.0

I am getting the same error as well.
The paper trade is important as it helps to fine tune strategies before deployment.
Downgrading to previous version using docker is not possible as well since there is no image for version 1.2.0 available for non-arm based systems(https://hub.docker.com/r/coinalpha/hummingbot/tags?page=1&ordering=last_updated)

Fixed


Add repeat (Eder Lomba of Rainmain 9b)

Eder Lomba makes second ascent of Rainman (9b)
source: https://www.ukclimbing.com/news/2022/05/eder_lomba_makes_second_ascent_of_rainman_9b-73054
source: https://www.instagram.com/p/CdnEuVmD5Ec/

Thanks a lot :)


Don't follow include! expansion to origin

include! errors are special in the sense that caller side is not useful for reporting all the syntax / type errors originating in included file (as you're getting tons of messages pointing to the same line where include!(...) occurs).
This change adds special case that keeps errors bound to their original location if it was include!d.
Before:

After:

Hello @RReverser,
I need to check it before I can merge it.
Thank you for this.

@KalitaAlexey Sure, let me know if you find anything.

Could you provide an example?
I have no time now for imaging it itself.

Well just any include!("somefile.rs") where somefile.rs is garbage (has syntax errors on various lines).

@RReverser,
I checked it twice.
First time
build.rs:
use std::env;
use std::fs::File;
use std::io::Write;
use std::path::Path;

fn main() {
    let out_dir = env::var("OUT_DIR").unwrap();
    let dest_path = Path::new(&out_dir).join("hello.rs");
    let mut f = File::create(&dest_path).unwrap();

    f.write_all(b"
        pub dfn message() -> &'static str {
            \"Hello, World!\"
        }
    ").unwrap();
}

main.rs:
include!(concat!(env!("OUT_DIR"), "/hello.rs"));

fn main() {
    let x = 5;
    let y = 6;
    let u = 7;
}

It showed errors in hello.rs.
Second time
main.rs:
include!("f.rs");

fn main() {
    let x = 5;
    let y = 6;
    let u = 7;
}

f.rs:
s

It showed errors in f.rs.

So I don't know what problem you have.

Oh right, syntax errors originate in correct place because otherwise include! can't even parse that file, it's type checker and other errors that don't.

Example with multiple errors

@RReverser,
I will check it.
Thanks.

Sorry.
I forgot about you.
I'll check it now.


Unexpected Exceptions

If you use EvalEx with user input you will get a lot of unexpected exceptions.
I expect ExpressionException, but, a lot of other exceptions are thrown as well.
Making it very hard to handle safely when you're implementing EvalEx.
Here are some test cases to showcase some of the examples:
import com.udojava.evalex.Expression;
import org.junit.Test;

public class ExpressionExceptionTest {

	@Test
	public void testNullPointerException() {
		Expression expression = new Expression("\"");
		expression.eval();
	}

	@Test
	public void testStringIndexOutOfBoundsException() {
		Expression expression = new Expression("100\"");
		expression.eval();
	}

	@Test
	public void testArithmeticException() {
		Expression expression = new Expression("100/0");
		expression.eval();
	}

	@Test
	public void testNumberFormatException() {
		Expression expression = new Expression("1.0.");
		expression.eval();
	}

	@Test
	public void testExpressionException() {
		Expression expression = new Expression("");
		expression.eval();
	}

}

My suggestion would be to wrap those exceptions in ExpressionException exceptions, ensuring easy exception handling.
It may even be viable to change ExpressionException from a RuntimeException (unchecked exception) to an Exception (checked exception), declaring what methods can throw it.

Obsolete with version 3, there should be only 2 exceptions now. ParseException an EvaluationException, each with detailed information.


⚠ Bofrost.de has degraded performance

In 385339b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1239 ms

Resolved: Bofrost.de performance has improved in 5b4ce73.


Saved dashboard not available under list of dashboards

Steps to reproduce
I have saved a dashboard and refreshed the page. The dashboard doesn't show up under the dashboard list and can only be accessed from the Recently opened.
Is this the expected behavior?

Environment

atoti: 0.5.1
Operating System: win32

Hi Hui Fang,
The "Dashboards" section displays a list of folders when expanded. To see the list of dashboards in the root folder, you need to click on this "Dashboards" item.

Hi Hui Fang,
The "Dashboards" section displays a list of folders when expanded. To see the list of dashboards in the root folder, you need to click on this "Dashboards" item.

Tracking this internally in this ticket.

Tracking this internally in this ticket.

Closing this since the layout has changed in the latest release :


Bump min torch version to 2.3.0

[x] Wait for Composer release with torch 2.3 support
[x] Rebase this PR on to main (which uses the latest composer release)
[x] Update regression tests to use torch 2.3 image
[x] Run regression tests on this branch

Lgtm, can't approve my own pr even though Milo took it over, so will just force merge when ci passes


Release number to match the vendored version of Tailwind

I’d like to make a proposal that going forward the gem version matches the release of Tailwind vendored in the assets directory.
Doing so would make it far easier for users to determine what version of Tailwind they are using in the gem, and make bundle updates a breeze.
The gem is currently on version 0.3.3 and that vendors 2.0.2 of Tailwind.
Could we release 2.2.4 using this convention?
Huge fan Tailwind, thank you for all your work in making it so easy to use with the asset pipeline 😄

I don't think we can make that work, since it would make it impossible to do new releases outside of TW releases. Which we may well need in order to fix bugs or add features.
But I do like the idea of being very clear, perhaps in the README, about which TW is included.


[PLAT-9816] Improved reliability of obtaining memory metadata on iOS 13+

Goal
Improved reliability of obtaining memory metadata on iOS 13+
Testing
E2E Tests

Did you see the warning about BSGRunContext.h above?

Can you confirm that the e2e tests pass on a device in the range iOS 15.0-15.3 on BitBar? Just a brief comment in the PR description is fine, I don’t need hard proof. I’ve set up some extra device groups, so you can use of the groups from --device=IOS_15_0 to --device=IOS_15_3 for that (choosing just one of them is fine I think).

Here is a link to a Bitbar test results for 15.1. It used to fail previously: https://cloud.bitbar.com/#testing/projects/207188123/209297604

Did you see the warning about BSGRunContext.h above?

I fixed the issue


WIP: Make matplotlib an optional dependency

Starting work on #286 .

@gdmcbain can you make a quick review at this point? Comments on the overall structure would be appreciated and if you have any ideas or alternative implementation strategies.
I'll continue with fixing rest of the examples after you think this is the right way to go forwards.

Another thought for the further future: Thus far the visualization is based on the skfem.Mesh class hierarchy but it also partially implies ElementLineP1 for MeshLine, ElementTriP1 for MeshTri, etc., or sometimes P0, Q0, etc., I think.  Some visualization backends (Gmsh, ParaView?, ...) might support higher order elements.  Does eventually supporting higher order visualization imply anything about the structure of the skfem.visualization package?  Should the functions take bases rather than meshes?  (Noting that an skfem.assembly.GlobalBasis has a .mesh attribute anyway.)

Fantastic suggestions, as usual. Here is a notebook I used during development.
plotting.pdf
I'm going to implement also the possibility of drawing through InteriorBasis since I removed the plotting of piecewise-constant and DG functions and refinterp should be used instead. I was thinking syntax like this:
plot(interior_basis, solution)

and the call is the passed to interior_basis.refinterp and, e.g., plot(m: MeshTri, ...).

Next I start fixing the examples. It might take a while.

Starting by running the Makefile under docs/examples and fixing all errors. Later fixing the docs.

Starting to be ready for review. Fixes #286 .

Am I missing some examples?


Interactive / notebook without workspace

Bug: Notebook Editor, Interactive Window, Editor cells
I have encountered an unforeseen bug and would like to also offer the fix. I would be willing to submit a PR and would like to discuss the potential solutions to this.

Steps to cause the bug to occur

Launch VSCode from Applications or Spotlight (similar procedures for Windows and Linux)
Open a Python file or Jupyter notebook (not a folder or workspace)
Attempt to execute notebook or start interactive window

Actual behavior
The interactive window does not load and an error is produced indicating that the file Untitled.ipynb cannot be written.
https://drive.google.com/file/d/1iKjhv9brRfclk8VDBy1yl80umoo8Lp28/view?usp=sharing
Expected behavior
Start a new interactive window. I'm personally not concerned where the notebook-dir is set to.
I have done some debugging on my own and determined that the expandWorkingDir function is used to set notebook-dir to / at https://github.com/microsoft/vscode-python/blob/1370b6de25c9e04c7d67d8b9c8069e601e16e8c8/src/client/datascience/jupyter/jupyterUtils.ts#L42.
I would like to propose that a check of write permissions be performed on process.cwd() before returning for use in notebook-dir. In the case where process.cwd() is not writable would a location in global storage be appropriate?
I'm happy to work on a PR for this use case.

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local
Extension version: v2020.9.114305
VS Code version: 1.50.0
Setting python.jediEnabled: false
Setting python.languageServer: Microsoft
Python and/or Anaconda version: 3.7.7
OS:  Mac
Virtual environment: conda

Jupyter Output
Starting Jupyter from ~/Applications/miniconda3/envs/plot/bin/python with command line --no-browser --notebook-dir="/" --config=/var/folders/lk/s__7f9fx15x_zrw6q5xkmm500000gp/T/71650752-3c70-4d3a-9de5-9394c1362fed/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
[I 20:24:19.146 NotebookApp] Serving notebooks from local directory: /
[I 20:24:19.147 NotebookApp] The Jupyter Notebook is running at:
[I 20:24:19.147 NotebookApp] http://localhost:8888/?token=5933e1200de371df96c0b76eb2f7d8dcf2bd3b8a94f0273f
[I 20:24:19.147 NotebookApp]  or http://<IP_ADDRESS>:8888/?token=5933e1200de371df96c0b76eb2f7d8dcf2bd3b8a94f0273f
[I 20:24:19.147 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 20:24:19.153 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///Users/adefusco/Library/Jupyter/runtime/nbserver-48334-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=5933e1200de371df96c0b76eb2f7d8dcf2bd3b8a94f0273f
     or http://<IP_ADDRESS>:8888/?token=5933e1200de371df96c0b76eb2f7d8dcf2bd3b8a94f0273f
[I 20:24:19.694 NotebookApp] Creating new notebook in /
[W 20:24:19.709 NotebookApp] 403 POST /api/contents/?1602635059680 (<IP_ADDRESS>): Permission denied: Untitled.ipynb
[W 20:24:19.709 NotebookApp] Permission denied: Untitled.ipynb
[W 20:24:19.710 NotebookApp] 403 POST /api/contents/?1602635059680 (<IP_ADDRESS>) 24.64ms referer=None
[I 20:24:19.733 NotebookApp] Creating new notebook in /
[W 20:24:19.735 NotebookApp] 403 POST /api/contents/?1602635059716 (<IP_ADDRESS>): Permission denied: Untitled.ipynb
[W 20:24:19.736 NotebookApp] Permission denied: Untitled.ipynb
[W 20:24:19.736 NotebookApp] 403 POST /api/contents/?1602635059716 (<IP_ADDRESS>) 4.54ms referer=None
Starting Jupyter from ~/Applications/miniconda3/envs/plot/bin/python with command line --no-browser --notebook-dir="/" --config=/var/folders/lk/s__7f9fx15x_zrw6q5xkmm500000gp/T/59c368c0-7073-467f-856f-b80caed3061c/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
[I 20:24:20.389 NotebookApp] Serving notebooks from local directory: /
[I 20:24:20.389 NotebookApp] The Jupyter Notebook is running at:
[I 20:24:20.389 NotebookApp] http://localhost:8888/?token=01f1a456d96ccff26eb8c1da220332717fb4559c72eea253
[I 20:24:20.389 NotebookApp]  or http://<IP_ADDRESS>:8888/?token=01f1a456d96ccff26eb8c1da220332717fb4559c72eea253
[I 20:24:20.389 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 20:24:20.392 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///Users/adefusco/Library/Jupyter/runtime/nbserver-48353-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=01f1a456d96ccff26eb8c1da220332717fb4559c72eea253
     or http://<IP_ADDRESS>:8888/?token=01f1a456d96ccff26eb8c1da220332717fb4559c72eea253
[I 20:24:20.407 NotebookApp] Creating new notebook in /
[W 20:24:20.411 NotebookApp] 403 POST /api/contents/?1602635060396 (<IP_ADDRESS>): Permission denied: Untitled.ipynb
[W 20:24:20.412 NotebookApp] Permission denied: Untitled.ipynb
[W 20:24:20.412 NotebookApp] 403 POST /api/contents/?1602635060396 (<IP_ADDRESS>) 12.52ms referer=None
[I 20:24:20.418 NotebookApp] Creating new notebook in /
[W 20:24:20.420 NotebookApp] 403 POST /api/contents/?1602635060412 (<IP_ADDRESS>): Permission denied: Untitled.ipynb
[W 20:24:20.420 NotebookApp] Permission denied: Untitled.ipynb
[W 20:24:20.420 NotebookApp] 403 POST /api/contents/?1602635060412 (<IP_ADDRESS>) 3.43ms referer=None

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

Thanks @AlbertDeFusco . We've actually had this bug from somebody else (same circumstances where it was using the root folder)
If process.cwd isn't writable, I'd suspect the os.tmpdir() would be good or if that also doesn't have write permissions, then the VS code extension global path.
We'd love a PR if you want to give it a try.

I've got a start on it, but I have encountered some oddities while debugging the extension. There are times during the screencapture steps I recorded above when the expandWorkingDir()function has a definedlaunchingFileand sometimes it isundefined`.
Could this be related to the fact that every time I launch VSCode the Python extension is loaded even if a py/ipynb file is not open or a workspace/folder is not open. Is that expected behavior? I have enabled pytest, could that (or some other setting) force the extension to launch?

Oh, it's Python test explorer that was causing the launch after startup.
https://github.com/kondratyev-nv/vscode-python-test-adapter/blob/fb202ddc017fc1077e3aea52c4a6861fdbd72dd0/package.json#L107

I've submitted https://github.com/microsoft/vscode-python/pull/14454 to kick this off. I was not able yet to determine globalStoragePath from within the expandWorkingDir function.


No router instance found when using redirectToDefaultLang

When using redirectToDefaultLang and getting redirected from logging in on Auth0 back to my page I get the following error:
Error: No router instance found. you should only use "next/router" inside the client side of your app. https://err.sh/zeit/next.js/no-router-instance

on this line:  router.replace(/es/${router.query.path.join('/')}) in [...path.js]
Maybe it would work when using getInitialProps here with something like:
  if (isServer) {
      appContext.ctx.res.writeHead(302, {
        Location: `/es/${router.query.path.join('/')}`,
      })

      appContext.ctx.res.end()
    } else {
      appContext.router.push(`/es/${router.query.path.join('/')}`)
    }

I guess that is the same issue reported on https://github.com/vinissimus/next-translate/issues/150. This will be fixed on 0.16.0. Can you confirm that  in0.16.0-canary.5 is working fine?
By the way, redirectToDefaultLang in >0.16.0 will be deprecated (but with backwards compatibility) https://github.com/vinissimus/next-translate/pull/162. Is recommended to change to defaultLangRedirect (after 0.16.0).

redirectToDefaultLang=true -> Same as defaultLangRedirect='lang-path'
redirectToDefaultLang=false -> Same as defaultLangRedirect=undefined (default one)
New one -> defaultLangRedirect='root' -> /en/example redirects to /example

I'll try to release 0.16.0 this week. If you can confirm that it is working fine what you reported here would be very useful! Thanks.

@aralroca okay, going to try it out.
So in my config I would have:  "defaultLangRedirect": "es", ?
Doesnt-work for me

@aralroca okay, I used "defaultLangRedirect":"lang-path" and this fixed the problem.
Good job :)

Cool! I'm going to release 0.16.0 soon! I need time to update the docs. I hope tomorrow! I'm going to close this issue then!

No, worries I am just going to use the canary version for now

@aralroca I just noticed, that on the canary some of my translations do not get included. I think there is a problem with the regex pattern.

mmmm... Is it not loading the full namespace, or only some translations of this namespace?
We have tests covering the part of loading the correct namespace from regex...

https://github.com/vinissimus/next-translate/blob/master/__tests__/getPageNamespaces.test.js#L31

Can you tell more details? I would like to reproduce it in order to fix it before 0.16.0 lands.


toml/json: Localization support for error messages

as usual: simple-to-use solution based on ResourceBundle & MessageFormat

done.


remove mac travis tests

Summary
This removes Mac travis CI tests.
Motivation
They're a pain and often fail.
r? @scottjab-stripe
cc? @stripe/storage

:shipit:
🔴 PRs are best PRs


Enable localizations of UI

A user would have the option of changing the language of the game's UI through a dropdown with available languages.

@djwhitt The names of the units should be localized when shown in the unit picker, right? They aren't currently in the dict.

As I mentioned earlier, I'm using a dropdown for the user to select the language. It's currently in the upper right hand corner. (ALL CAPS is my test dict.)

Would you prefer it be put somewhere else?
And should I replace it with a modal?

I have since implemented the modal and it definitely makes more sense. I'm thinking of labeling the link "Settings" instead of whatever the current language is, so other settings, like whether or not to show the "You still have turns left" modal, can go there too.


Add explanation on calculating 30% rewards

This PR adds an explanation on how 30% rewards can be calculated for simple function calls using data from NEAR Explorer. It also helps understand gas fees a little better by outlining the difference between receipt creation and execution cost.

@bucanero what do you think?


[markdown]

[x] List syntax is required.

You can nest lists below, too!

[x] This item is completed.
[ ] This item is not complete.

Communities


Build process fails on NixOS

Let me know if you want more details about the case.

Can you update again? There's been an xdph update in the meantime.

@fufexan I still have the same error:

https://github.com/luisnquin/nixos-config/blob/main/flake.nix#L45 this seems to be your problem. Is your nixpkgs up to date? (newer than 2-3 weeks ago)

Okay, I'll try with a newer version of nixpkgs.

Yup, that worked! Thanks @fufexan!


Enable better BrowserStack test naming

Enable various Buildkite environment variables to be passed through to maze-runner which will help with linking particular Buildkite jobs to BrowserStack runs.
In this case, only the app-automate service will have the new names, which is currently only utilised by the Expo maze tests.

Can you point this at next please? That should have been the default branch.

Going to close this off as it's quite stale now.


a11y: implement new SemanticsAction "showOnScreen"

This action is triggered when the user swipes (in accessibility mode) to the last visible item of a scrollable list to bring that item fully on screen.
This requires engine rolled to https://github.com/flutter/engine/pull/3856.
I am in the process of adding tests, but I'd like to get early feedback to see if this approach is OK.

@Hixie I am closing this PR. Please take a look at my second attempt: https://github.com/flutter/flutter/pull/11156


Added repr to Moran I

While the memory address returned is highly informative....I thought that it would be nicer to see a better representation of the class.  Perhaps this is a template for other classes?
Here is an example, generated on a network using GeoDaNet Crimes data and counts per edge.
#Moran's I
res = ps.esda.moran.Moran(y, ntw.w, permutations=99)
print res

        Moran's I: 0.00519268749608

        Normality Assumption
        --------------------
        Expected Value: -0.00331125827815
        Variance of I: 0.001848680825
        Standard Dev. of I: 0.0429962885026
        Z-Value: 0.197783252239
        P-Value: 0.843214650106

        Randomization Assumption
        ------------------------
        Variance of I: 0.00184235970473
        Standard Dev. of I: 0.0429227178162
        Z-Value: 0.198122258023
        P-Value: 0.842949410612

        Permutation Results
        -------------------
        Number of Permutations: 99
        Average Expected Value: -0.00471588766906
        Variance of I: 0.000802558883639
        Standard Dev. of I: 0.0283294702322
        Standardized I: 0.349762105818
        P-Value: 0.363258620035

@jlaura is this available in your branches? I was thinking about trying to push on this, maybe also adding special pretty printing for IPython notebook environments.

It looks like I axed the branch, but the commit lives on in an old PR:
https://github.com/pysal/pysal/commit/c0037459ba295eefa8311fb520a84a4d1434ad83
Also checkout how pandas manages the to_* methods.  I think that this
approach, and the awesome formatting we see in the statsmodels project give
us a a pretty good roadmap.  Thoughts?
https://github.com/pydata/pandas/blob/355b4623d842633746b29b6e7f1724af4cd87dae/pandas/core/format.py
https://github.com/statsmodels/statsmodels/blob/4b55fa4871cf3f1dbd2e30bfe00d80df87d4b340/statsmodels/tsa/vector_ar/output.py#L27
(I think this is the correct class, checkout the make method.
On Thu, Jul 30, 2015 at 11:53 AM, Levi John Wolf<EMAIL_ADDRESS>wrote:

@jlaura https://github.com/jlaura is this available in your branches? I
was thinking about trying to push on this, maybe also adding special pretty
printing for IPython notebook environments.
—
Reply to this email directly or view it on GitHub
https://github.com/pysal/pysal/pull/527#issuecomment-126437103.

oh woah, didn't realize these changes got merged in a different PR. Should this get closed?
Yes on the outputting stuff. Taking inspiration from how they design their interfaces is smart, I think.  This could go into stuff like an spreg SUMMARY.* call and add to the repr as well as the summaries.

I hadn't realized that this was merged either....
What I can do is manually back it out (just that commit)?  This must have
have snuck in with another PR due to some sloppy git work on my side.
On Thu, Jul 30, 2015 at 1:06 PM, Levi John Wolf<EMAIL_ADDRESS>wrote:

oh woah, didn't realize these changes got merged in a different PR. Should
this get closed?
Yes on the outputting stuff. Taking inspiration from how they design their
interfaces is smart, I think. This could go into stuff like an spreg
SUMMARY.* call and add to the repr as well as the summaries.
—
Reply to this email directly or view it on GitHub
https://github.com/pysal/pysal/pull/527#issuecomment-126464716.

git revert c00374 could be pretty scary, but might work. I can't remember any changes made to Moran that have that commit as a parent.
There's probably a tool to visualize the git graph somewhere. That'd show what would cascade.

Since the change in that commit is just the repr addition, I would
likely just manually remove it and then PR that back in.  To avoid a nasty
cascade.
Are we better leave it, knowing that someone is looking at adding repr
and other writing items or remove and start fresh?
On Thu, Jul 30, 2015 at 1:43 PM, Levi John Wolf<EMAIL_ADDRESS>wrote:

git revert c00374 could be pretty scary, but might work. I can't remember
any changes made to Moran that have that commit as a parent.
There's probably a tool to visualize the git graph somewhere. That'd show
what would cascade.
—
Reply to this email directly or view it on GitHub
https://github.com/pysal/pysal/pull/527#issuecomment-126480023.

I don't think this got merged into master? At least moran.py doesn't look to have the new __repr__

+1
https://github.com/pysal/pysal/search?utf8=✓&q=__repr__
No need for a roll back.
On Thu, Jul 30, 2015 at 2:16 PM, Sergio Rey<EMAIL_ADDRESS>wrote:

I don't think this got merged into master? At least moran.py
https://github.com/pysal/pysal/blob/master/pysal/esda/moran.py doesn't
look to have the new repr
—
Reply to this email directly or view it on GitHub
https://github.com/pysal/pysal/pull/527#issuecomment-126491052.

I think it got pulled in and out over the course of #601.
That said, this PR is weird and should probably get refreshed since we can't add to it if the source is deleted. Apparently github copies the source into a hidden branch in the target so that the PR can still get merged if the source is deleted.
However, I'm not sure whether you can just reopen the source with the same branch name...

Revisit at Scipy 2106 to assign modules to implement this for.


[WIP] Check if item has corresponding inventory record before including in …

…cart
We were seeing an issue where there's a mismatch between the cart total number and the items that appear on the cart page. We only render cart item if they have product details (i.e. a correspondingInventoryRecord), but we calculate the number of cart items without doing the same check. This updates our itemSelector to only return items that have a corresponding InventoryRecord so everywhere we use cart items we have the same data
STR:

Add some items to your cart
Go to the Inventory table in the Airtable and delete the row for one of the items you've added to your cart
Refresh your cart and verify that that item no longer appears in your cart, and your cart quantity matches your item list

Setting this to WIP, seems create-order is still using a deleted item


Scanning malicious files before upload

"this commit fixes #6 "

@shubhamj99 There is a small issue in the PR
TypeError: expected str, bytes or os.PathLike object, not UploadedFile
Traceback:
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/streamlit/script_runner.py", line 351, in _run_script
    self._session_state.call_callbacks()
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/streamlit/state/session_state.py", line 490, in call_callbacks
    self._new_widget_state.call_callback(wid)
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/streamlit/state/session_state.py", line 220, in call_callback
    callback(*args, **kwargs)
File "/home/gauransh/Code/chithi/src/app.py", line 116, in mail
    mailer.send_mail(to=recipients, cc=cc, bcc=bcc, subject=subject,
File "/home/gauransh/Code/chithi/src/mailer.py", line 73, in send_mail
    api_response = api_instance.scan_file(files)
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/cloudmersive_virus_api_client/api/scan_api.py", line 55, in scan_file
    (data) = self.scan_file_with_http_info(input_file, **kwargs)  # noqa: E501
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/cloudmersive_virus_api_client/api/scan_api.py", line 119, in scan_file_with_http_info
    return self.api_client.call_api(
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/cloudmersive_virus_api_client/api_client.py", line 325, in call_api
    return self.__call_api(resource_path, method,
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/cloudmersive_virus_api_client/api_client.py", line 141, in __call_api
    post_params = self.prepare_post_parameters(post_params, files)
File "/home/gauransh/Code/chithi/lib/python3.9/site-packages/cloudmersive_virus_api_client/api_client.py", line 451, in prepare_post_parameters
    with open(n, 'rb') as f:

The possible solution to this could be not reading the files as binary rather sending the FIleObject as it is or as a byte stream.
For further reference please have a look at the streamlit Documentation here

Also, Is this key in the commit belongs to you, if yes then please don't share it in public and use a secure way to use it maybe by exporting the key as an Environment Variable and using it via os.getenv(key)

Ok I'll look into this, I didn't get that error before. Thanks for the feedback.

Sure 👍🏼


[Bug]: deprecated items

Describe the Bug
When loading the module this appears in the console

Steps to Replicate
Enableling the module in the setup window

Desired Outcome
Update to use the latest data structures
Actual Outcome
outdated data structure
Screenshots

Foundry Version
v10.286
System and Version
DND5e
Module Profiles Version
v1.0.6
What browser did you see this on?
Chrome
What OS were you using?
Windows
Installed Modules + Additional Info

Module Profiles v1.0.0

Closed by 7fe2b23dd275700c5637486cdb08f1ad159b25cb

nice!  Thanks for the update


Desktop Voice Assistant

Aim
To be able to perform basic functions on our desktop using our voice
Details

What the features will your script have
Will be able to perform basic functions like:

Sending email
Opening google
opening some app
or any other

@sayantani11 go ahead, assigned to you

@sayantani11 updates on this?

@kaustubhgupta I am stuck at a point where I am unable to install PyAudio..... I will fix it today with @santushtisharma10

did you found any alternative for PyAudio?

Yes....I guess I will be able to push the code within a day or two
@kaustubhgupta


#378 explictly set charset for jsonify()

https://webhint.io/docs/user-guide/hints/hint-content-type/ reference for best practice
Without this Microsoft Edge devtools post a warning
https://github.com/pallets/flask/issues/378 appears to be the first report (but was also possibly caused by bad payload).

fixes #378

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[ ] Run pre-commit hooks and fix any issues.
[ ] Run pytest and tox, no tests failed.

Opening as a place holder. I don't have time to setup a dev environment and create a new test for this.

If you need this, you can set app.json.mimetype.


consierge

Does this occur consistently?
Repro steps:

Action: staticWebApps.createStaticWebApp
Error type: 500
Error Message: An error has occurred.
Version: 0.5.0
OS: win32
OS Release: 10.0.19041
Product: Visual Studio Code
Product Version: 1.55.0
Language: en

Call Stack
new RestError extension.bundle.js:48:64839
extension.bundle.js:48:1490514extension.bundle.js:48:1490514
processTicksAndRejections task_queues.js:97:5

Possibly related to https://github.com/microsoft/vscode-azurestaticwebapps/issues/305
Please make sure that you have admin access to the repository that you are using to create a SWA.

Please provide repro steps.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Update Foodcritic from 4.0.0 to 7.0.1

Foodcritic >= 7.0 removed support for Ruby 2.0
Foodcritic >= 5.0 removed support for Ruby 1.9.3
Do we still need to support the EOL'd versions?  This would mean dropping support for Chef <12

Do we still need to support the EOL'd versions? This would mean dropping support for Chef <12

nevermind, saw your comment on https://github.com/mthssdrbrg/kafka-cookbook/issues/105
I will remove the version bump but still keep the FC rule fixes so they will not be an issue when the version is bumped

Updated the Travis setup so foodcritic isn't run for Ruby 1.9.3 and merged the first commit of this PR in 492dff8e5190df6d2e62f12ca9ded3090acdf3a8. Thanks :)

that works :)
Travis should probably still run foodcritic though (under ruby 2.1+) to verify that no violations appear.
Adding section to the travis matrix and only running foodcritic would probably suffice

Yeah, Travis still runs foodcritic for the "default" Ruby version (it's included in bundle exec rake test) :).

Ah! missed that, cool :)


build: Add Stylelint

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#10  👈
#9
#8
#7
#6
#5
#4
#3
#2
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MikeRatcliffe and the rest of your teammates on  Graphite