Multiple trees

Closes #22
I had to wrap the ReactSortableTree so that I could make it a dropTarget dynamically. This is necessary, because the drop type needs to be generated dynamically before calling dropTarget.
Because of the ESLint configuration, this forced me to push the ReacSortableTree into a new file because we can only have one class per file.
I checked that everything works both in the example app, as well as in my own.
Let me know if this will be published to NPM soon. I was hoping to push what we made with this library to production, but we cannot do that until this fix is merged and published.

Thank you for bringing this up, and putting time into making it work.
I think one of the reasons it was so difficult to replace the react-dnd item types was because I was using a funky solution for scrolling on drag. I had to fix that first, and then I implemented a prop called dndType to do the same thing your treeName did.
However, I also implemented a reasonable dndType default value, fixing the issue you were having without having to assign a name explicitly. Because most users will never have to use it, I'm keeping the dndType prop out of the README.
The fix is now available in v0.1.6, which is already on npm now. Thanks for bringing this to my attention.

@ncphillips @fritz-c any specific example of this working available, as I am in need of a solution to have a dndType be dragged and dropped into a sortable tree.


don't know how to run the code examples

I have an experience with cpp but not cmake i have spend the last 2 days trying to configure the libraries to work in my system but i couldn't !
i really want help
what i do is the following:

tried to install them with something called conan but in vain 90% of them didn't exists in conan
read about cmake and learned how to install them i tried to do it with pytorch first because i alread know how to work with it but get a lot of error tried to figure out how to solve them like cudnn version is not exist ..etc but there is something wrong.
i asked help from a lot  of people and communities but there is no useful help yet.
the last thing i tried to do is i downloaded the code sample for the book and go to the folder build scripts then i run it but get a lot of errors again. i know that in the LIBS_DIR is sould give pass to configuration but i don't know what is configuration he is talking about
i want to read this book and take this challenge i spend a lot of time and didn't want to stop now! is there any other ways to run the code vm ,docker what i really missing why it's really hard to add just a thrid-library in cpp world i do it easly with conda in python and cargo in Rust ..javascript!!!!
please any help!

Hello @abdelkareemkobo, please follow the official instruction to create the Docker development environment. Current books samples are based on outdated 3rd parties so it can be very tricky to setup every thinning for recent version of Ubuntu. Please read the README in the env_scripts folder.


Kotlin

Add Kotlin support with decoders and extension functions for the builder and gestalt.

Add Kotlin support with decoders and extension functions for the builder and gestalt.


Add new desert models

Summary by CodeRabbit

New Features

Added new biome entries: Bare, Temperate Deciduous Forest, Grassland, Ocean, and Outline.
Updated model paths for Temperate Desert and Deep Ocean.
Restored entries for Snow, Tundra, and Tropical Rain Forest.

Bug Fixes

Corrected the model path for Deep Ocean to ensure accurate rendering.

lgtm


With spring-cloud-gcp-starter-secretmanager Spring Boot Fails to start with Could not find TLS ALPN provider; no working netty-tcnative

With spring-cloud-gcp-starter-secretmanager Spring Boot Fails to start with Exception : Could not find TLS ALPN provider; no working netty-tcnative
Exception from start Logs:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'secretManagerClient' defined in class path resource [org/springframework/cloud/gcp/autoconfigure/secretmanager/GcpSecretManagerBootstrapConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.google.cloud.secretmanager.v1beta1.SecretManagerServiceClient]: Factory method 'secretManagerClient' threw exception; nested exception is java.lang.IllegalStateException: Could not find TLS ALPN provider; no working netty-tcnative, Conscrypt, or Jetty NPN/ALPN available

Could you share your pom.xml file?
Note that this error means that the grpc-netty-shaded dependency is not on your classpath, usually it refers to a project configuration problem.


nbio.write_all and nbio.send_all

This is usually what you actually want to do, should be builtin

Done in #31


Feat/router path handling migrations

This is an extension of #5292 which also includes an automatic migration feature.
Recommended to review commit-by-commit.

This needs a rebase on top of #5292, please don't merge before 5292 is reviewed and merged.

Closing in favor of #5360


Make a decision about exchange integration

If CCXT:
implement
else
?

Selected CCXT. Need help with wrapper.


✨ Nested JSON ✨ (Working Demo!)

yo @benborgers
not sure if you're interested or not, but referencing #15, 1.5 years later... I did it!
(let me know if you want me to submit a PR, if not all good)
Nested JSON
This new feature let's you create nested.json.using.dot.notation in the header. The flat json still works as well.
fork: https://github.com/oneezy/opensheet
sheet: https://docs.google.com/spreadsheets/d/1hFt4kkXoAx-LFZvfhsN8JITb5zuAufqhkvs0ZKTjxac/edit#gid=0
json: https://opensheet.justinoneill2007.workers.dev/1hFt4kkXoAx-LFZvfhsN8JITb5zuAufqhkvs0ZKTjxac/nested

Ahh this makes so much sense seeing it built out!
I think unfortunately I haven’t seen a lot of demand for this, so I’m hesitant to add it to the core instance. (It would also technically be a breaking change I believe.)
I’m glad you forked and hosted your own version though! Having that fork separate might be the best path forward.

Ahh this makes so much sense seeing it built out!
I think unfortunately I haven’t seen a lot of demand for this, so I’m hesitant to add it to the core instance. (It would also technically be a breaking change I believe.)
I’m glad you forked and hosted your own version though! Having that fork separate might be the best path forward.

It's actually backwards compatible so i think it'd just be a be feature bump
Flat Demo
sheet: https://docs.google.com/spreadsheets/d/1hFt4kkXoAx-LFZvfhsN8JITb5zuAufqhkvs0ZKTjxac/edit#gid=0
json: https://opensheet.justinoneill2007.workers.dev/1hFt4kkXoAx-LFZvfhsN8JITb5zuAufqhkvs0ZKTjxac/flat

I think it'd technically be a breaking change for columns with a dot in them already. But yeah, mostly I'm trying to keep the core project as simple as possible — it gets a lot of traffic so I'm hesitant to complicate it too much.

Ooo duh! I totally didn't think of that 😂
Makes sense


feat(testing-library): enable prefer-find-by rule

Suggest using findBy* methods instead of the waitFor + getBy queries.
BREAKING CHANGE: You may need to run eslint --fix if you were violating this rule.

This will work after a new release (required dependency update is still in develop branch), or if you manually remove the eslint-plugin-testing-library entry from yarn.lock in the consuming project.

:tada: This PR is included in version 7.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Show module hint when auto-importing

Probably a duplicate of #2604. That issue was closed with the conclusion that it was a problem in VSCode UX, but other extensions have this feature already so that's not it.
Usually, I need to use typing.cast, but VSC shows 2 functions called cast, and I have no way to know which one is it.

also the first one always ends up being wrong, even though I've already imported something from typing

I'm asking for something like what the Typescript extension does, it shows a hint besides the identifier with the name of the library.

rust-analyzer also does this, and probably many others but those 2 are the ones that I tested.
Hopefully it's easy to implement! Good luck!

A module hint is provided, but you need to ask VS Code to display expanded information for the suggestion. This is true for other language servers as well, not something that's unique to Pylance.
To show the expanded information, move your mouse pointer over the suggestion, and you'll see a > icon. Click it, and you'll see a separate window to the right of the primary completion list window. Once you toggle this, it will appear every time you invoke completion suggestions, so you need to do this only once.

Yes I know, but I learned about it in that other issue, so I'm not sure if it's really discoverable.
Something like this mockup should be better IMO

and instead of showing the import statement in that popup, show information about the function

That's how the Typescript extension works basically, which I think it's a very good example and I hope you agree

Actually, Pylance is consistent with how TypeScript and other language servers work in this regard. Here's a screen shot that shows an auto-import in TypeScript.

I think you make a good point about discoverability.

Weird?... This is how it looks for me (VSCode 1.67.1)

And btw, thank you for the really quick feedback!

Yeah, you're right. I see that for some TypeScript auto-imports but not for all. We'll need to dig into it further to understand what's going on here.
Thanks for the feedback.

This issue has been fixed in version 2022.6.10, which we've just released. You can find the changelog here: CHANGELOG.md


Cherry pick Remove unneeded rc feature of serde to active_release

Automatic cherry-pick of 771b248

Originally appeared in https://github.com/apache/arrow-rs/pull/990: Remove unneeded rc feature of serde

Codecov Report

Merging #1016 (81951af) into active_release (a92672e) will increase coverage by 0.00%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           active_release    #1016   +/-   ##
===============================================
  Coverage           82.37%   82.38%
===============================================
  Files                 168      168
  Lines               49133    49133
===============================================
+ Hits                40474    40476    +2
+ Misses               8659     8657    -2

Impacted Files
Coverage Δ

arrow/src/array/transform/mod.rs
85.47% <0.00%> (+0.13%)
:arrow_up:

parquet/src/encodings/encoding.rs
93.71% <0.00%> (+0.19%)
: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 a92672e...81951af. Read the comment docs.

SIMD checks are failing due to some error in the nightly rust compiler


memutil.cc: always use tolower() in memcasecmp() for better branch prediction

We need the CLA before we can consider contributions.
This is essentially proposing reverting a recent change that claimed to show an improvement:
https://github.com/abseil/abseil-cpp/commit/6c8338c252116e429307361ff4fdc1fd0532902d
We would need real data to convince us to revert https://github.com/abseil/abseil-cpp/commit/6c8338c252116e429307361ff4fdc1fd0532902d.
I also highly recommend https://abseil.io/fast/39, particularly the part about how small microbenchmarks can mislead about actual performance in large programs which cache pressure is high. That is the most important thing to consider here. Macrobenchmarks in large programs are what really matter.


Use DXT1 when compressing PNGs with RGB format

Fixes: https://github.com/godotengine/godot/issues/58012
This now roughly matches the behaviour of Godot 3. We switched to DXT5 for RGB textures in https://github.com/godotengine/godot/pull/47370 and it's not clear why the change was made. My guess is it was just a typo.
This PR only changes the RGB format. R format is left as DXT5. Originally it used FORMAT_RGTC_R. Since I'm not sure why and I'm not sure what the tradeoffs involved are, I'd prefer to leave this PR as just fixing up the obviously broken case of RGB texture imports.
There is a quality difference between DXT5 and DXT1. Notably the DXT5 option appears slightly smoother, but comes nowhere close to the quality of BPTC with the same file size
Before

After

BPTC for reference

Original for reference

Are we trying to optimize disk size or gpu memory size? Reducing GPU memory size is better I think.

VRAM compression optimizes both for disk size and GPU memory size. The gains are the same for both

This PR only changes the RGB format. R format is left as DXT5. Originally it used FORMAT_RGTC_R. Since I'm not sure why and I'm not sure what the tradeoffs involved are, I'd prefer to leave this PR as just fixing up the obviously broken case of RGB texture imports.

Ideally, the BC4 format should be used: https://learn.microsoft.com/en-us/windows/win32/direct3d10/d3d10-graphics-programming-guide-resources-block-compression#bc4
If we can't use BC4, then BC1 (DXT1) should be used instead. We don't need green/blue/alpha channels at all, and the red channel's precision remains the same (but with 1:6 compression ratio instead of 1:4).

This PR only changes the RGB format. R format is left as DXT5. Originally it used FORMAT_RGTC_R. Since I'm not sure why and I'm not sure what the tradeoffs involved are, I'd prefer to leave this PR as just fixing up the obviously broken case of RGB texture imports.

Ideally, the BC4 format should be used: https://learn.microsoft.com/en-us/windows/win32/direct3d10/d3d10-graphics-programming-guide-resources-block-compression#bc4
If we can't use BC4, then BC1 (DXT1) should be used instead. We don't need green/blue/alpha channels at all, and the red channel's precision remains the same (but with 1:6 compression ratio instead of 1:4).

Looks like FORMAT_RGTC_R does use BC4. The problem appears to be that ETCPAC doesn't have a pathway to compress to FORMAT_RGTC_R. So I guess we are stuck with DXT5 unless someone wants to add support for RGTC_R (its supported in the renderers already). The problem with falling back to DXT1 is that it will impact the green and blue channels. A luminance texture returns the same grayscale value for r, g, and b, while a RED texture returns a grayscale value in the r channel, but 0 in the green and blue channel

Does it have a lose on quality in the after result?

Does it have a lose on quality in the after result?

Yes DXT1 is lower quality than DXT5, see the comparison in the top post in this PR

The analysis suggest we don't merge this.

The analysis suggest we don't merge this.

What analysis is that?

The quality difference is hardly noticeable – it's unlikely to be something you'll pick on during gameplay, especially with higher-resolution textures.
Remember that pixel art textures should not use VRAM compression in general, since they're already low-resolution.

Thanks!

Googling does suggest that the quality for RGB should be similar for DXT1 and DXT5 (perhaps identical, as articles suggest conversion is lossless), and they both use 4 bits per pixel for color (with DXT5 having extra 4 bits for alpha):
http://blog.wolfire.com/2009/01/dxtc-texture-compression/
I did a diff on clay's posted two versions and increased the levels and there does appear to be a slight difference (assuming that these PNGs are lossless):

Maybe this is down to the compressor rather than the format?

Cherry-picked for 4.0.3.


[Docs] update Sphinx config

This is part of refactoring the doc system to realign the different layouts found in different packages and make them consistent.
Small change to the overall config, plus updates to several of the single-page modules as test cases.

Also adding qu2cu pages to the docs structure; that package had been missing previously and, from conversations, that seemed to be an unintentional gap.

@anthrotype If you don't object, I'd like to merge in the Doc/-only bits and get on to staging other things that might warrant a little real-human review.

LGTM.


Allow generic-typed class methods/variables in abstract classes

I ran into this limitation when attempting to define an abstract base class which accepted a generic type. While I somewhat understand the compiler needing to infer the type of the generic in order to generate appropriate code, however abstract classes should be treated as non-instantiatable code which sub-classes inherit from and implement the missing bits to make instantiatable. What struck me as odd about the error message, is it's coming from the scope of Foo (where the type of generic T should be known), but not Base (where the class variable @@foo is defined via the class_getter macro and given the type T?).
Example
abstract class Base(T)

  class_getter(foo : T?) { T.new(0) }

end

class Foo < Base(Int32)
end

p Foo.foo

Compiler Output
Showing last frame. Use --error-trace for full trace.

There was a problem expanding macro 'class_getter'

Code in test.cr:3:3

 3 | class_getter(foo : T?) { T.new(0) }
     ^
Called macro defined in macro 'macro_140569709955712'

 1052 | macro class_getter(*names, &block)

Which expanded to:

 >  8 |
 >  9 |           def self.foo
 > 10 |             if (value = @@foo).nil?
                                ^
Error: can't infer the type of class variable '@@foo' of Foo

The type of a class variable, if not declared explicitly with
`@@foo : Type`, is inferred from assignments to it across
the whole program.

The assignments must look like this:

  1. `@@foo = 1` (or other literals), inferred to the literal's type
  2. `@@foo = Type.new`, type is inferred to be Type
  3. `@@foo = Type.method`, where `method` has a return type
     annotation, type is inferred from it
  4. `@@foo = arg`, with 'arg' being a method argument with a
     type restriction 'Type', type is inferred to be Type
  5. `@@foo = arg`, with 'arg' being a method argument with a
     default value, type is inferred using rules 1, 2 and 3 from it
  6. `@@foo = uninitialized Type`, type is inferred to be Type
  7. `@@foo = LibSome.func`, and `LibSome` is a `lib`, type
     is inferred from that fun.
  8. `LibSome.func(out @@foo)`, and `LibSome` is a `lib`, type
     is inferred from that fun argument.

Other assignments have no effect on its type.

can't infer the type of class variable '@@foo' of Foo

Generic types can't have generic class variables. I think there's a separate issue for that already.

I couldn't find it either but essentially
Todays current behavior is
class Bar(T)
  class_property x : Int32 = 0
end

Bar.x = 1
Bar(Int32).x = 2
Bar(String).x = 3

pp! Bar.x         # => 3
pp! Bar(Int32).x  # => 3
pp! Bar(String).x # => 3

Instead of
pp! Bar.x         # => 1
pp! Bar(Int32).x  # => 2
pp! Bar(String).x # => 3

I think this is the same issue that I'm experiencing. I'm trying to create a generic class variable.
Without Generics
What I'm trying to accomplish is to get around the fact that class variables do not persist between sub-classes.
So let's say for example that I have an Entity class with some internal counters. If I create an AnimalEntity sub-class, I have a new list of counters.
The solution is to use a singleton for the internal counter
class EntityCounter
  @@counter = 0
  # class methods for managing counter...
end

class Entity
  def dostuff
    EntityCounter.increment
    # do stuff
  end
end

Now the counter is the same for Entity and AnimalEntity.
With Generics
Here is a more complex example where I want to create a pool of resources by type. Each resource in the pool has a reference counter (sort of like a file reference count), so resources can be garbage collected once they have no more references.
I have several different types of resources that need different pools. Say for example a Texture, Model, and Shader.
Again, I'd like to be able to subclass any of those types, but still maintain the same resource pool for each.
Here is what I'd like to do:
class Reference(T)
  # instance vars and methods for managing reference
end
class ReferencePool(T)
  @@references  = Hash(String, Reference(T)).new
  # class methods for managing pool
end
class Texture
  def dostuff
     ReferencePool(Texture).use("texture-key")
  end
end
# etc...

Assuming the above code worked, I could easily create new types with their own pool of references. However, the compiler just complains that it can't infer the type for T.

I think it's a good use case.
For the record, C# can do it.
using System;
using System.Collections.Generic;

class C<T>
{
  static Dictionary<String, T> stuff = new Dictionary<String, T>();

  public static int foo() {
    return stuff.Count;
  }
}

class Application
{
  static void Main()
  {
    C<int>.foo();
  }
}

I would also prefer if class variables are scoped to instantiated generic class.
That also pushes class methods to be on instantiated generic class.
It is more powerful. If there is a need for shared class variables across all instances, there can be a helper non-generic class created for that end.
But we might need to wait. I doubt it will change soon.

I looked at the code and this might not be hard to implement... but I don't have the time right now.


Does echart4 support chord with ribbon?

One-line summary [问题简述]
As checked the demo/echarts-examples for echart3/echart4, there is no any demo of ribbon chord.
I found echart2 has demo on supporting ribbon chord.  But the demo code from echart2 cannot work in echart3/echart4.
So I got question on whether echart4 can support the ribbon chord diagram? If yes, could you please help to provide a demo to demonstrate it? Thank you so much!
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

I've got the same question. Chords are very commonly used chart, so having it in ECharts will be very helpful!

This may be what you're looking for: https://echarts.apache.org/examples/en/editor.html?c=graph-circular-layout

I've got the same question, I had a solution to support ribbon chord.
you could import chord after import echarts:
import * as echarts from 'echarts'; import 'echarts/lib/chart/chord'
but there is anther question I met, the tooltips was gone.

Any updates on chords for version 5?
I see that issue https://github.com/apache/echarts/issues/10098 is requesting the same...


Scaling function for regularization

In the old ACE package, there is a scaling function used in ACESchrodinger:

which the current package don't have.

I will get to this eventually, but if you are in a rush, here is what this does, maybe this can help you implement it:
The scaling function specifies how to regularize each parameter. It's best to think of it as follows: the parameter for the envelope has not natural scaling and maybe shouldn't be regularized at all -> hence the 0.
But the parameters associated with the linear ACE are associated to basis functions and those basis functions have a natural regularity attached to them. In the context of the 1d models each basis function Bi can be thought of as a symmetrized tensor product P_k1 ... P_kN where the kt are the degrees. The scaling attached to this basis function is morally speaking something like the H^p norm. For simplicity we just use
   k1^p + ... + kN^p

The p here is the 2 in scaling(ace, 2)
So to implement this one would need to recover the specification of each basis function and one can then reconstruct this scaling very easily.

@cortner I think I have done this. Maybe we can close this issue?

This should be done. Shall we close this issue?
CC @cortner

you know best, please close it if you think this has been taken care of.


Uncomment lines about android demo in builder

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Add to whitelist


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2023-02-20)
Features

docker: include db migrations in container (363e2e9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/bdronneau/memoriesbox/releases/tag/v1.1.0 :sunflower:


0.1.1 Changes

Yo; few changes, so have a read if you're interested. Otherwise, install and have fun!

🚀 Performance fixes; updated playback system to use HTML Canvas instead of SVG DOM Elements for faster and smoother animations.
💧Fixed memory leak; discovered memory leak in the playback that would draw 80,000 extra nodes than required, and would continue to build up overtime until the browser crashed (my bad; too little sleep I suppose... no one reads these right?).
😪 Project changes; restructured projects so I could start sharing components between private and public instances of Raid Review (coming soon tm).
🗺 Playback interface: slight changes to the UI, and better exposure of the positional/heatmap toggle.
🧠 Added caching: utilising client side caching for positional and heatmap data, should help with load times.
🐞 Bug fixes; other various bug fixes and changes.
Other changes...

Thanks for reading ✌

No work on 3.9.0 yet, sorry!


[TACHYON-424] S3 client

https://tachyon.atlassian.net/projects/TACHYON/issues/TACHYON-424
This PR implements an S3 Client using the jets3t library.
A new s3 submodule under /underfs contains the logic for the client. The user may enable this client as their s3 client by removing the s3n:// prefix from the hadoop prefixes in their configuration.
The implementation conforms to our UnderFileSystem interface and unit tests. It also passes all applicable core tests when using the S3UnderFileSystemCluster. Since the S3UnderFileSystem is implemented as a real S3 backend, the tests are disabled by default.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/3142/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/3151/Failed Tests: 1org.tachyonproject:tachyon-underfs-hdfs: 1tachyon.master.MasterFaultToleranceTest.faultTest
Test FAILed.

NIT: use git push --force YOUR_REMOTE YOUR_BRANCH to avoid having duplicated commits after rebasing

Sorry , I was on the wrong thread. discard my post :)


A confusion between the formula and the code

Hello, I am trying to understand your excellent work
But as far as I am concerned, according to the formula in the paper as below
$h_i^{k+1}=\text{arg}\min||F_q(\hat{z_t}^{k+1})-F_{h_i^k}(z_t)||$
Is the code here should be
https://github.com/Yujun-Shi/DragDiffusion/blob/3a88d93e97cbb1863d73a98b577b639bd4020b8a/drag_utils.py#L31C33-L31C33
f0 = F0[:, :, int(pi[0]), int(pi[1])] instead of f0 = F0[:, :, int(pi0[0]), int(pi0[1])]?
I wonder if it is my wrong understanding, hope for your answer

Hello, thanks for your interests in our work!
Actually, this is a typo in our report. The code is the correct implementation.
Thanks again for pointing out the typo in our report. We will revise this in our later version.


Wire up font subsetting for all platforms

The tool has new assets to subset icon fonts, and new functionality is being added to the assets build target to use these tools to remove unneded icons from fonts.
Each platform needs to be wired in to use this - some are easy and will be done in the same pull request that adds functionality to the assets target, but others are blocked or in flux at the moment.

[x] iOS (blocked by making iOS use assemble completely - https://github.com/flutter/flutter/pull/49842) (fixed in #50224)
[x] Android (#49737)
[x] macOS (#49737)
[ ] Linux
[x] Windows
[ ] Fuchsia
[x] Web (does not emit a kernel file at present)

This is done for windows now by way of windows AOT support. Removing fuchsia from the list since we don't yet know how we will build fuchsia.

Err, that is "we should" remove fuchsia from the list.

Don't we already build for Fucshia?  e.g. flutter run with a Fuchsia device attached?

there is no "distribution" of fuchsia applications though, so it doesn't really make sense to wire up release only features yet

Ahhh ok, that makes sense.

This is completed, by way of AOT support for Linux


sequenceArray_

And countless other variants.
flow(T.sequenceArray, T.map(constVoid))

https://github.com/samhh/fp-ts-std/commit/706e2959be838494450b5463034f5a66499bda45 and the previous two. Added for IO, Task, and TaskEither. Can be expanded to other monadic or foldable structures as needed/requested.


substrate --dev

Fatal error: Client(Execution(Wasmi(Function("Module doesn't have export BabeApi_configuration"))))

Please run cargo run -- purge-chain --dev -y


Possible to use ESP8266 ?

Is it possible to use an ESP8266 instead of a ESP32 or do you need the extra processing power that the ESP32 has ?

In theory it should work also for the ESP8266 as all the connections needed are there, but unfortunately I've never tried it. In any case, I don't think that the processing power needed is too high to handle for the ESP8266.
If you succeed in using it with an ESP8266, please tell me so I can update the read.me file

I've added a new code specific for ESP8266 (just a slight modification of the original file). You can find it as peopleCounterESP8266.ino in the main folder


Attach commit as package.json#gitHead in prerelease versions

:warn: I didn't do any extensive testing - this PR should be verified by somebody who actually understands how this script is used and how this might affect other things.
Why?
I've recognized a regression between nightly builds of TS (well, when you were releasing nightlies for 3.8). I have the exact version in which the valid error has stopped being reported by TS but I cannot easily check from which commit this build was prepared. This helps with that.
Note that I don't care where this commit would be written - it could be in a root .json, in the README, or somewhere else. It's just that per semver spec attaching such metadata in the version is allowed and this shouldn't affect any semver-aware algorithms for matching versions, dependency ranges etc. This is described here: https://semver.org/#spec-item-10
While this is a very little-known "feature", I've seen this being used "in the wild".

#36960

@DanielRosenwasser I have no opinion on the change itself, but this would be a breaking change for the pipeline that syncs versions across to the ADO repo, so we'll have to make a corresponding change. Let's just make sure that's handled before we merge.

Note - I don't mind using some other solution for this, I only care about the commit being available somewhere in the published artifact. It made sense for me to include it here as it is some well-defined sport where such a thing can be put, any other place I would have to "figure out" by myself/pick at random and I didn't know what would be the preference of the team.
In a sense, this PR is more of a conversation starter than something that has to land ASAP.

I think that my main concern is that if the commit metadata lands in the package version, it becomes harder (maybe not easily possible?) to get a version of TypeScript on a specific date, which is often how we offhandedly bisect. For example, I'll try installing<EMAIL_ADDRESS>to get the most recent version, but I don't think I could write that without knowing the exact commit that was published on that nightly.

That's actually not true - this build metadata is completely ignored when it comes to matching semver ranges etc. You could install this just fine.

Could you elaborate? If I try installing a partial date suffix, it will fail.
> npm install<EMAIL_ADDRESS>npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR!      [UserPath]\AppData\Local\npm-cache\_logs\2022-03-06T22_16_28_756Z-debug.log

If I give a full published version (e.g. typescript@4.7.0-dev.20220304), it seems to succeed.

@DanielRosenwasser The build metadata is not part of the actual version number. It makes no difference whether you install<EMAIL_ADDRESS>or<EMAIL_ADDRESS>

Yea, and actually - that build metadata is completely ignored when installing. This particular package and version doesn't have any build metadata and it gets installed successfully:
yarn add<EMAIL_ADDRESS>
We can also test a package (@react-aria/utils) that has some build metadata in its version field set to 3.0.0-nightly.1460+2c25922e2 in one of its nightlies~:
yarn add<EMAIL_ADDRESS>
This one installs just fine as well.

I agree with all the build metadata / semver discussion, but it might just be simpler to put this on a new field in the package json

What do you think about package.json#gitHead? This is a field added by some tools (like Lerna) when packing packages.

switched this one to use package.json#gitHead, cc @jakebailey

Many thanks!

Okay, what? How did this pass CI?
npx hereby scripts
Using ~/work/TypeScript/Herebyfile.mjs to run scripts
Starting scripts
scripts/configurePrerelease.mjs:55:22 - error TS2339: Property 'gitHead' does not exist on type 'PackageJson'.

55     packageJsonValue.gitHead = execFileSync("git", ["rev-parse", "HEAD"], { encoding: "utf8" }).trim();
                        ~~~~~~~

Found 1 error.

Error in scripts in 3.2s
Error: Process exited with code: 1
Completed scripts with errors in 3.2s

We test this in CI so I don't know how this happened...

This property displays as any in my IDE, I assumed that PackageJson type has an index signature ;p

Right, but it's only any because it's actually an error... The type is defined at the top of the file. I don't get what's happening here. It's failing over on #53134 now, but not in main?

Note that I dont see an error at this location in the IDE


Add open.oneplus.net

See: https://www.chrisdcmoore.co.uk/post/oneplus-analytics/

Thank you @nikeee !


Fix Something related to the #1

Fix the doc issue of 9 not 12

@Clivern Just what the title mentions

Thanks @TommyPujol06


MaterialApp should support unconstrained environments

If an Overlay widget finds itself in an unconstrained environment (e.g. because the View is allowed to pick a dynamic size, see https://github.com/flutter/flutter/issues/134501), it throws. This means, MaterialApp (which introduces an Overlay as part of the Navigator) cannot be placed in an unconstrained view. We somehow need to allow that. I suspect, it means limiting the available options to position things inside the overlay...

FYI @ditman

This is actually more complicated. It's not just the overlay that blows up in unconstraint environments. Things like Scaffold (and anything else that uses a CustomMultiChildLayout amongst other things) also cannot live in unconstraint environments. So, just fixing Overlay is not gonna be enough in the long term.
cc @yjbanov @ditman Do you have an idea of what kind of UIs need to work in unconstrained environments so we can prioritize those? I am afraid that just fixing the Overlay doesn't get us all that far...

@ditman Do you have an idea of what kind of UIs need to work in unconstrained environments so we can prioritize those?

Now that the constraints for the root view can be set from the embedder, potentially any app can end up in an unconstrained view.
One simple example that I couldn't get to work, is adding a SelectionArea to your "yellow box with text inside" reflow sample, because SelectionArea ends up needing an Overlay (that's the first bug I've noticed regarding this, there's maybe others)

I've been looking into getting the counter app (the app you get when you do flutter create) to work in an unconstrained view. It uses some of the problematic widgets like Overlay and Scaffold.

(PS: Do we need to re-think how views are able to resize from the framework, or would we end up in a similar situation anyways?)

I believe the issue is inherent to the problem we are trying to solve. We want to size the view based on its content. However, currently some widgets (Overlay, Scaffold, to name some) are unable to size themselves based on their content. They rely on the parent telling them what size they should be (but of course if the size should be based on content the parent doesn't know what size to give the child).
Some of this is due to history. There was never a reason for some of these widgets to size themselves based on content because they could just rely on the fact that they will be used in a fixed size view that needs to be filled out. For some of these widgets this problem is straight-forward to fix:
If the Overlay finds itself in an unconstraint environment, it could pick a child that determines its size (e.g. the topmost child that wants to fill the entire view is a good candidate). I've implemented this in https://github.com/flutter/flutter/pull/139513.
For other widgets, this is a lot harder to fix. The Scaffold is a good example. For simplicity, lets assume our Scaffold just has an app bar and a body. They are obviously expected to have the same width, but in order to figure out what width that should be in an unconstrained environment we would need to lay out both, measure their individual widths, pick the larger one and lay them both out again at that desired overall width. We are in intrinsics sizing territory here, which comes with performance penalties due the additional layout passes required. Other widgets based on CustomMultiChildLayout and CustomSingleChildLayout face the same problem.
If we want to make this work, we likely will not get around the fact that this may require intrinsics calculations. One thought I had to make this work: Instead of fixing up each individual widget (as illustrated above for the Scaffold), can we just wrap the entire widget tree in IntrinsicsWidth/IntrinsicsHeight widgets? In theory, this should work. In practice we face the problem that widgets based on CustomMultiChildLayout don't implement the intrinsics protocol properly (see TODO), likely again because they never had to work in these kind of environments before. So, as before we'd be back to fixing up the intrinsics of the individual widgets.
Furthermore, even if we fix up intrinsics for these widgets we still have the fundamental limitation that intrinsics do not work for LayoutBuilder-type widgets (and until https://github.com/flutter/flutter/pull/138369 is fixed it also doesn't work for anything that requires baseline calculations). So, those types of widgets couldn't be used inside an unconstrained view (unless they have a parent widget that gives them constrained constraints).
Long story short: I don't think we will ever be able to allow any kind of widget inside an unconstrained view. Even getting a reasonable generic subset to work is gonna require a heavy lift of fixing up assumptions/bugs in our existing widgets. For a specific UI where the number of widgets that need to be fixed is clear, this may be possible, but likely in the short term not for generic "unknown" UIs. 🫤


Runtime Error when using timetrace start

If I use timetrace start with omitting the <PROJECT KEY> I get an panic: runtime error: index out of range [0] with length 0 error.
Timetrace v0.14.0

Thanks for reporting this! Indeed, there should be a human-readable error message instead.


Uncaught Error: Missing: SyncTestZoneSpec

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Mac El capitan

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.2.2
os: darwin x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
I created this app using the webpack 2 version.  Since rc6 was released I upgraded to rc6 and modified all the tests to match the new way of doing them with TestBed instead of addProviders.

The log given by the failure. Normally this include a stack trace and some
more information.
Chrome 52.0.2743 (Mac OS X 10.11.6) ERROR
Uncaught Error: Missing: SyncTestZoneSpec
at /Users/porteraz/workspace/travel/travel-client/src/test.ts:59883 <- webpack:///Users/porteraz/workspace/travel/travel-client/~/zone.js/dist/jasmine-patch.js:66:0

Chrome 52.0.2743 (Mac OS X 10.11.6) ERROR
Uncaught Error: Missing: SyncTestZoneSpec
at /Users/porteraz/workspace/travel/travel-client/src/test.ts:59883 <- webpack:///Users/porteraz/workspace/travel/travel-client/~/zone.js/dist/jasmine-patch.js:66:0

Mention any other details that might be useful.

According to this github issue in zone.js:
https://github.com/angular/zone.js/issues/404
We need to add the following to the config/karma-test-shim.js (or config/spec-bundle.js):
require('zone.js/dist/proxy'); // since zone.js 0.6.15
require('zone.js/dist/jasmine-patch'); // put here since zone.js 0.6.14
But I can't find a karma-test-shim.js to update.

Thanks! We'll be in touch soon.

I have the same problem with Ubuntu 16.04 LTS after changing from<EMAIL_ADDRESS>to the angular-cli@webpack.
angular-cli: git master
node: 6.2.1
os: Ubuntu 16.04 LTS 64 Bit
@zackporter92 The official instruction for the change says that some file not needed anymore. One of this file is karma-test-shim.js.

As far as I can see I found the problem. I took a look into angular-cli template file and ended at test.ts (1) file. This file has one import more than my test.ts file and the order of the imports were different.
(1) https://github.com/angular/angular-cli/blob/master/addon/ng2/blueprints/ng2/files/path/test.ts#L3-L8
Now I'm getting an other error which says that a provider for a component can't be found. I think this indicates that the original problem is solved.

This is currently added in beta.14, under src/test.ts.

The location of that file has been changed: https://github.com/angular/angular-cli/blob/master/packages/%40angular/cli/blueprints/ng2/files/path/test.ts

Location changed again:
<EMAIL_ADDRESS>

Thanks for the person who deleted the blueprints directory :rage: :rage: :rage:


Projectiondefaults, width slider direct save

The projection default as a root rest element is removed. This reduces the complexity on the client a lot.

Hm. Why do you added views to delete projection defaults or to create new ones?

Ping?

You are right. I also disallowed update and partial updates, becuase they are not needed. See #4644 .


has / contains

https://github.com/kitsuyui/python-richset/pull/18
https://github.com/kitsuyui/python-richset/releases/tag/v0.1.7


Migrate source packages to separate repo

NuGet packages for source-embedding (MoreLinq.Source.MoreEnumerable.*.nuspec) scenarios should be moved to another repo to separate their maintenance from the core library and packages.

[x] Import to new repo
[ ] Delete from core repo

Imported into morelinq/srcpkg@086a97395b38a5d8da8694cfecb716933148404a


Add mouse grab example

Fixes #4094

Awesome. Once I have a second approval I'm ready to merge this :)

bors r+


XLPagerTabStrip update indicator image

Hello. I use ButtonBarPagerTabStripViewController. How do I update indicator image? I need to update the image when I receive notification

Hey @Metman !
I think this issue is related to #325, can you confirm that ? That issue is addressed in #368 & will soon be merged into the master branch
Cheers

Closing due to lack of response.


Create ADR describing sequencerless pessimistic mode

This is simply a based rollup mode that will be supported post https://github.com/rollkit/rollkit/issues/1649


Add tgl reports flag to show end times

Add a new flag to change ([time ago] at [start]) to ([start] to [end])
Maybe -E, or -T


add LXD_UNPRIVILEGED_ONLY to disallow privileged containers.

Signed-off-by: Jingkui Wang<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

jenkins: test this please

jenkins: test this please

jenkins: test this please

jenkins: test this please

jenkins: test this please

@brauner looks good, but I don't get why you're making that huge change to the testsuite.
Wouldn't it be simpler to just have the test set the env variable before calling spawn_lxd and then unset it immediately afterwards?

On Fri, Apr 20, 2018, 00:53 Stéphane Graber<EMAIL_ADDRESS>wrote:

@brauner https://github.com/brauner looks good, but I don't get why
you're making that huge change to the testsuite.
Wouldn't it be simpler to just have the test set the env variable before
calling spawn_lxd and then unset it immediately afterwards?

That's what I did first but it didn't work as LXD didn't pick it up on
start. Note that we do the same for LXD_DIR. If you are convinced that it
works the other way you could do a reset on the branch and just add that
piece. But I didn't get it to work. But that might just be oversight on my
part. :)
—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/pull/4473#issuecomment-382904770, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHA05U6eFy3jObgstc1lx3eXY82pDzbVks5tqRVtgaJpZM4TbB1f
.

@brauner yeah, doing that now, the big diff in tests/ bothers me :)

jenkins: test this please

@brauner please review my changes and merge if you're happy with them, I'm fine with yours :)

@brauner good to go


Why is a RPC node needed for constructing a new Wallet?

I can see from Wallet.ts:
constructor(rpc: RPCInterface, seed: string, index: number = 0, work_function?: WorkFunction) {
and
static gen_random_wallet(rpc: RPCInterface): Wallet {
    let random_bytes = new Uint8Array(32);
    crypto.getRandomValues(random_bytes);
    const random_seed = util.uint8array_to_hex(random_bytes);
    return new Wallet(rpc, random_seed);
  }

that you use an rpc, that incudes a URL, to generate a new wallet. Why? Wouldn't it be (& look/feel) safer to have network related tasks & fields separate from the seed & private keys?

Well, the private key / seed are never sent to the RPC, the library handles the signing on the device, so it would give any safety improvements. You can just omit the parameter if you don't need to interact with a RPC, iirc it will not error in Javascript. In Typescript you can just make a dummy RPC with a random URL if you will not need to interact with a RPC.
The reason why a RPC is "required" to make a wallet is because wallets need to send, receive, change rep, etc. Those typically involve making RPC requests to for example get the current balance and frontier hash. And obviously, the signed transaction needs to be broadcast somewhere. I guess the rpc could be a required parameter for all the send, receive, account history, etc functions, but I don't really see the point. Could you elaborate on why you think it would be safer to not require a RPC to create a Wallet?
If your usecase does not involve network access (cold wallet signing...?), look in util.ts for block signing functions and whatnot, you probably don't want to use a Wallet.


Improve Search experience

Search is now always visible.
Search removes any empty dates, they are unnecessary clusters.
Pressing back now closes the search, before closing the app.
Account action moved to the right side of the top bar.

@joreilly + @martinbonnin I'm not sure how much I like the new search compared with the previous one (and there is no animation now), but it will make it easier to include a filter action in the future (on the right side of the account).
Let me know what you think, I can drop the changes on the "Improve Search UI" commit.

I have reverted the search UX, for now - we can discuss it separately.


lack of antialiasing

I have tried both the picture-entity card, and your custom webrtc as well, the result is the same. The card shows the camera stream correctly, but it is very very pixelated, I can barely read out the timestamp. I tried this both in Firefox and Chrome. I have 4MP Hikvision cameras, I use RTSP protocol. Is there some setting I haven't enabled? I guess it is not intended behavior.

What resolution of your camera in pixels? What OS you using?

@AlexxIT this is a 4MP stream, the os is windows 11.

Pixels please

Oh, ok. The 4MP one is 2560 × 1440, and I have a 5MP, which is 2560 × 1920.

Both streams has same problem?

Yes, the distortion looks exactly the same on both streams. Should I try lowering the resolution or anything else, for debugging purposes?

I can confirm this problem on Windows Edge. Don't have problem on Mac. Don't know how to fix it in near future.


Implementing Frontend Pagination in React

This fixes #4679

Plagiarism check done ✅

@M0nicah, any feedback?

@M0nicah, I checked my article again in Grammarly and there are no grammar mistakes.
Everything is okay 🚀

Jumping on this one

Overall nice work 👍


Exclude a path from applying postcss rules on it

Problem
Not able to apply postcss on a specific path
Description
Im using React and<EMAIL_ADDRESS>in postcssOptions I use postcss-rtlcss plugin which makes styles rtl. I'm using a template which I dont want to to apply postcss-rtlcss on it. but I couldn't find a way to exclude a path in postcss, craco or postcss-rtlcss configs. any idea?
My craco config
const postCssRtl = require("postcss-rtlcss");

module.exports = {
    reactScriptsVersion: "react-scripts",
    style: {
        postcss: {
            loaderOptions: {
                postcssOptions: {
                    plugins: [postCssRtl()],
                },
            },
        },
    },
};

Try using postcss-exclude-files to get this behavior. You can configure webpack within your craco config. I'll close this issue but feel free to leave a comment if you're still having this problem.


Working Slow

I am currently using onnx version but even with 32 core cpu also It's taking almost 14 seconds to compile image, So I tested some AWS GPU servers with normal model Which takes 29-35 seconds which is too much, I have tested with T4, k80 A10G, All 3 which is provided by AWS but results are same.
SO can you please let me know how can I make it fast or any GPU recommadation I should use for this which can process it within 2-5 seconds.

Please make sure that you are using CUDA backend for pytorch. It only took a few seconds to process.

Do you have any specific section of code where and how to implement this, It would be helpfull

It is already implemented for both command-line tool and python API. Please check if your machine works with CUDA backend for pytorch.
import torch

torch.cuda.is_available()

If it returns false, you need to setup your environment properly. I would recommend re-install pytorch by following the official instruction.


Params.to_map behaviour for missing fields.

Both to_map and data have the behaviour that it's not possible to see if nil was submitted for a field or if that field was not submitted at all.
It makes sense that data behaves that way, since it returns a struct. But with to_map, I would expect it to use the schema as whitelist and not add extra fields unless default is used.
Maybe this should be a different function than to_map?
My usecase is an API endpoint that can update a resource. Something like this:
defmodule MyAPIEndpoint do
  defmodule MyParams do
    use Params.Schema, %{
      id!: :integer,
      name: string,
      owner_id: :integer
    }
  end

  def call(params) do
    changeset = MyParams.from(params)
    if changeset.valid? do
      attributes = Params.to_map(changeset)
      MyRepo.update_attributes(attributes)
    end
  end
end

So I want to update only the submitted keys. In this case it should be possible to update owner_id to the value nil.
Again, I will be happy to help with the implementation. Just wanted your oppinion before getting started ;)

Hey @lasseebert,
Definitely your use case seems valid to me, there should be a way to determine if some value was given on the request or completely missed. And as you mention I think the behaviour of to_map has to change, having nil values only if the user explicitly sent nil for that field or if the developer specified a default nil value for it.  Please go ahead implementing it.
I've just added you as collaborator so you can directly merge things or send PR if you want some code review. Also merged ecto-2.x branch into master as I think we'll be adding more features on it and ecto-1.x branch will be kept behind.
Thanks again! :)

Oh, just to make it clear, I don't think we need a separate method besides to_map, so feel free to change it as you said.

Thanks for making me a collaborator :)
I'll make the changes to to_map as discussed above.


Header score impl

HTTP Header Score Implemented
Fix for #5

@maruthi-adithya would be nice to have tests for the Header score functions as well, if possible

@Shriram-Balaji  Test Cases are Added for the changes


Uncaught TypeError: Cannot read property '_unhandledEvent' of undefined with Ember Data 1.0.0-beta.19

When upgrading Ember Data to 1.0.0-beta.19, this error appears (from ember-data.model-fragments.js:98):
Uncaught TypeError: Cannot read property '_unhandledEvent' of undefined

And Ember Data Model Fragments fails to load, which causes other errors to be thrown.
See jsbin: http://emberjs.jsbin.com/hafaso/1/edit?html,js,console. Change Ember Data from beta.19 to beta.18 (HTML tab line 12) and the error goes away.

I'm aware of the issue; this is unfortunately just the tip of the iceberg. The beta.19 release shifted around internal APIs in preparation for 1.0, and it will take a considerable amount of effort to maintain compatibility.
I'm currently in the process of a near-full rewrite to provide support for 1.0, so it's possible that MF will never support beta.19 due to my limited bandwidth.

Are there any plans for support for beta 19? Or will the next version just support Ember Data 1.0?

I'm currently working against the 1.13 release series, although it's possible that the update to that version will be compatible with beta-19.

Ember Data 1.13 is fine too, I will just upgrade from beta-18 tot 1.13. No problem!

Is there an ETA for next version?

We are moving with our app to the new ember and ember data and need this update very much... Is there any way we could help You?

Sorry for the delay all, recent changes have made the upgrade difficult. Unfortunately I don't think there's any way to help @herczyn, thanks for the offer.

Any progress? :smile_cat:

Thanks for your patience everyone, I was able to get tests passing this weekend in #109. This update was very invasive, and so I would appreciate if anyone waiting on an upgrade could test against that PR. I've published the distribution files to the tmp-dist branch, so you can install the package directly without having to clone and build:
$ bower install ember-data.model-fragments#tmp-dist

Very exciting @slindberg :beers:

Indeed! I'm still on ember-data beta 15 for the moment, but it's great to know this will be available when I can slot it in time to upgrade.

Gonna update to Ember, Ember Data and Ember cli 1.13 + using the tmp-distData Fragment. Hope everything will work out fine. Thanks for the update @slindberg!
Btw, wouldn't it be better to give your next release also v1.13 to stay in sync with al other Ember projects (I know this is not a core project, but it's a project that's likely to change every time when Ember got a new version)?

I know my opinion on this wont matter much here, but I hate the fact that projects other than Ember and Ember Data are adopting this versioning pattern. It's not semver compliant and only allows packages other than Ember to update their patch version. I think it adds more confusion than it helps. Is<EMAIL_ADDRESS>compatible with<EMAIL_ADDRESS>Who knows unless you read a single blog post on emberjs.com...

@devinus You should always be on the latest patch version, since those are bug fixes, and semver guarantees (as much as humanly possible) that the changes in the patch are fixes and not something that will make one version incompatible.
The real value is in the major.minor version numbers, since then Ember Data can say yes we use the new computed property syntax because Ember 1.13 does.

@knownasilya Except that a library can now never have a major or minor version change to signify what they are supposed to signify according to semver. They can only ever bump the patch version. It's not semver.

Yes that is true, they have to wait till the next minor version to add new features. I think that's the idea, if you buy into this as a library author (I'm not, because I want the flexibility to not wait for Ember).


bootstrap-treeview.js file issue

downloaded js file form this site but facing error
TypeError: this.$element.off is not a function
Please suggest

Not enough information


Unable to run clean command because plugin was not found.

I ran the command
docker run -it --rm --name my-project -v "$PWD":/data andreptb/maven:3.2.5-jdk6 mvn clean
Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:
maven-clean-plugin:jar:2.5: Could not transfer artifact org.apache.maven.plugins:
maven-clean-plugin:pom:2.5 from/to central (https://repo.maven.apache.org/maven2):
Received fatal alert: protocol_version -> [Help 1]

What's the problem?

@rhuanpacto ,
I couldn't reproduce this problem. Can you try the same command with library/maven image?
Maybe i'ts a problem in your docker environment.

@rhuanpacto ,
I was able to reproduce the problem now. It seems the current SSL version used in maven central repo (TLS 1.2) is not supported by jdk 1.6, hence the failure fetching any dependencies from there.
You don't need to use maven with jdk 1.6 to build your projects. You can use a newer jdk/maven but configure to be compatible with source code for java 6. Check maven-compiler-plugin documentation.
I'm affraid there's nothing more we can do regarding this issue.


Update to SVGInjector2?

Since the Waybury team stopped supporting SVGI a long time ago, any thoughts on updating this or creating a new version with the newer supported version of SVGI2?
https://github.com/flobacher/SVGInjector2

Hey @simpson, this has come up before in #16 but to be honest I haven't given it much more thought, since this library at the moment is working and stable.
When I can carve out some time I'll take a closer look, but what sort of things are you thinking would be advantageous to have from SVGInjector2?

Closing due to no activity...


"Message is currently being processed"

We have changed a few IPs around and updated the pools, although we have one message that seems to be just stuck (12+ hours in that status).
Have tried a few of the earlier comments for stuck messages with no joy on this one and the usual steps have not worked.
Has anyone come across this and managed to unstick the message?

does the database tell you if that particular message is locked by anything or did you already clear that bit?
does the UI page for it have any resend or re queue links?

Ah, perfect. I did check in the DB but didn't spot that.
Set the lock values to NULL and it pretty much vanished.
The buttons to resend/queue were not there, most likely due to being stuck.


p2p: fix connecting to bootnodes

Motivation
There was loop variable capture that had some chance to make go-sm only try to connect to a subset of required bootnodes, and alo messed up logging
Description
Fix loop variable capture

... appears to be no longer an issue for go v1.22 (default capture behaviour changed), so closing


Load dependent service providers and aliases

add dependencies in composer.json for laravelcollective/html
load dependent service providers and aliases of laravelcollective in service provider

Fixed in release 0.2.34


(fix) - return value of functional components

fixes: https://github.com/FormidableLabs/urql/issues/335
Normally one would use the exported type React.FC for these but since this isn't possible with generics I followed this line from the React types to come to this conclusion.
type SFC<P> = StatelessComponent<P>;
interface StatelessComponent<P> {
 (props: P & { children?: ReactNode }, context?: any): ReactElement<any>;
}

Sorry about the notification spam, I missclicked on assignees there :/

Looks good to me!
I'd go as far as to say we shouldn't be explicitly stating function return types unless absolutely necessary. This can sometimes lead to upcasting and in the case of these components, an error will be thrown through implicit inference when used as a component and the return type is not ReactElement | null.


Code action to open namespace inserts declaration at wrong location when no other opens present

Describe the bug
When using a code action to add a missing open declaration to a source file that does not yet contain any open statements (including Microsoft.Quantum.Intrinsic), the new open declaration is included at the wrong location.
To Reproduce
Start with the following source file:
namespace Microsoft.Quantum.Arrays {

    /// # Summary
    function All<'T> (predicate : ('T -> Bool), array : 'T[]) : Bool {
       return Fold(And, true, Mapped(predicate, array));
    }

}

Select the available code action at And to obtain:
namespace Microsoft.Quantum.Arrays {

    /// # Summary
    open Microsoft.Quantum.Logical;

    function All<'T> (predicate : ('T -> Bool), array : 'T[]) : Bool {
       return Fold(And, true, Mapped(predicate, array));
    }

}

Expected behavior
namespace Microsoft.Quantum.Arrays {
    open Microsoft.Quantum.Logical;

    /// # Summary
    function All<'T> (predicate : ('T -> Bool), array : 'T[]) : Bool {
       return Fold(And, true, Mapped(predicate, array));
    }

}

System information

Version of the NuGet package or extension for which the problem occurs: 0.11.2003.2506
Your operating system and .NET Core version: Windows 10, .NET Core SDK 5.0.100-preview.1.20155.7
For issues with extensions, the version of the IDE for which the problem occurs: VS Code 1.43.2.

That's a good candidate for a bug bash...

Hey guys,
I'm HAckermango as the name implies, a white hat hacker. Would like to

to CREATE AN ONLINE VIDEO AND ANIMATION EDITOR like Powtoon. Check out
www.powtoon.com to have a better understanding. This project would comprise
of professional programmers, developer, animation guru and lots more.
You all should have a good look on the website and amaze me with your

comments.TOGETHER WE STAND. Thanks
Best Regards,
Hackermango


Is it updated ?

Is it in sync with tellform repo? if not can you please guide me on how to do that?

@saurabhPV not it is not currently in sync with the tellform repo. However it would be pretty easy to extract the form logic from tellform as it's completely seperated. You just need to copy public/form_modules as well as public/form_application.js and public/form_config.js

ok thanks! I will try that!

@saurabhPV you also need to include the bower dependencies in bower.json

1.I cloned the main repo deleted everything except public folder and bower.json.
2.Then I copied grunt file.js, package.json,config, css, demo and publish.js.
3. ran command bower install.
4.ran command npm install grunt --save-dev (failed saying browserify-shim not found)
5.ran command npm install browserify browserify-shim
6.ran grunt
It generates bundle.js , form.css ,form.js ,template.js in dist folder but not the lib folder.
I don't  remember exactly how but I was able to generate the lib in angular-tellform repo.

@saurabhPV you have to run bower install. Bower installation was removed from the npm script to maintain compatibility with the Heroku Button.

Thanks!
But I end up using main Tellform repo instead.

Can you help me with the bundle.js if using directly the main repo? When I ran bower install in the tellform-repo and copied its libraries here I was getting some missing files errors

@ianubhav Applogies for the delayed response.
I just checked my old repo I don't see any config changes I had done to run this. But I see I had added few new component and few fixes. Unfortunately I don't remember what changes we did to build, If you haven't fixed it let me know I will try to dig into the code and can find out what needs to be done.


This allows the user to set their own lock table name

Point me to where I neeed to change docs, if this is accepted.

@krainboltgreene change looks good, what is missing is the documentation to index.html and test case to make sure that feature really works.

@elhigu Any chance you could write the test or at least point me to a recent pull request that deals with this area and has a test?

@krainboltgreene You can start looking to tests here: https://github.com/tgriesser/knex/blob/master/test/integration/suite.js
Thats where migration tests are getting their configuration and knex instance is passed to here: https://github.com/tgriesser/knex/blob/master/test/integration/migrate/index.js
Where you should be able to add tests case for changing the migration lock table name.
Even better would be if you can find somewhere a test where changing name of the migration table is tested it would be pretty perfect example. I'm just not sure if that has been tested at all :(
Hope that these pointers gets you started.

@elhigu Would this change be still good to go if I added test and documentation?

Yep, it would be

why was this deleted? it just missed tests

I don't care anymore.


Cohen's d calculation (paired samples) result doesn't match underlying formula

Hey Joses,
Thanks a lot for the great package and the great work!
By using dabestr I realised a potential bug in the cohen's d calculation for paired samples: the outcome of dabestr doesn't match the outcome of the standard formula of Cohen's d (paired samples). As an example: please see formula nr. 6: https://www.frontiersin.org/articles/10.3389/fpsyg.2013.00863/full
To make it easier for you to verify my report, I have used your example of dummy data from the respective vignette: please see the R code in the txt-file attached below:

Cohen's d based on dabestr: 0.689
Cohen's d based on the standard formula (e.g. see the mentioned reference above): 0.495

In case I can help in any way, please get in touch! Thank you!
testing_dabestr.txt

Hey @josesho! Thanks a lot for your clarifying and very helpful response! Your examples and the reference make perfect sense - and in particular you are right that both definitions of Cohen's d exist in parallel. This resolves my question. Thanks again & all the best! GG
P.S: Maybe this is useful for other readers: The two formula outputs based an your vignette dummy data (formula nr. 10 is realsized in dabestr):

cohens_d_result_formula_6 <-
mean(my.data_set$Measurement[41:80] - my.data_set$Measurement[1:40]) /
sd(my.data_set$Measurement[41:80] - my.data_set$Measurement[1:40])'

cohens_d_result_formula_10 <-
mean(my.data_set$Measurement[41:80] - my.data_set$Measurement[1:40]) /
((sd(my.data_set$Measurement[41:80]) + sd(my.data_set$Measurement[1:40]))/2)


Update diagnostic-services.md

Update diagnostic-services.md to add more detals about metrics

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

Hi @ShichaoQiu
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
For more information, see Should I work in a private or a public repo?
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
Would you create a pull request in the private repo to make these updates? We'll close this PR. Thank you.


12 feature creating an appsettingsjson for configuration

Problem
Currently, our application has configurations hardcoded in multiple locations, making it difficult to manage and maintain. This can lead to issues when deploying the application to different environments or when sharing the project with other contributors.
Solution
This pull request introduces an appsettings.json file that centralizes all application configurations. The new configuration system makes it easier to manage and maintain settings, ensuring consistency across the application.
Changes in this PR include:

Added an appsettings.json file to store all application configurations.
Modified the code to read settings from the appsettings.json file instead of hardcoded values.
Updated relevant classes to use dependency injection for accessing configurations, making it more flexible and testable.

It should fail, i didn't changed the Unit test. That is what I'm now working on, but you can have a look @xXDaniel1109Xx

Everything looks good, will rebase and merge


Feature Request: Display preview of themes inline in the theme-installation window

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
At the moment, I have to resort to a browser tab to hunt down an Atom theme that I like - the "Install Themes" window is fairly useless until I already know which theme I want.
Thus, I'd like to suggest that that window display a row of four or five tiny, rendered, code-editors below each theme in the list; each of which displays an example of syntax-highlighting with a different language / snippet.
(If that's too architecturally complex, then perhaps simply inlining the first image found on the project's GitHub README is a better solution?)
tl;dr I think the theme-browser can be made more useful! (=

Thanks for the suggestion!
Enhancement requests for the settings view should go in https://github.com/atom/settings-view -
I searched around there and found that this is a duplicate of https://github.com/atom/settings-view/issues/106 so you can subscribe there if you'd like.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


update for conda-build 3

@conda-forge-admin, please update for conda-build 3

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I updated the recipe for conda-build 3 in conda-forge/sk-video-feedstock#6.


[BUG] ECS connect container unhealthy during new deployments to ECS EC2

Summary
ECS service connect random unhealthy during new deployment
Description
I have several ECS tasks running on EC2 using ECS service connect for internal communication. Sometimes, during new deployments, the ECS service connect container linked to these tasks becomes unhealthy, preventing the deployment from succeeding. This issue doesn't occur with every deployment.
These ECS tasks are GPU-based and take some time to start. I don't have any health check configured for the task definitions.
Capacity provider with auto scaling is configured to manage the EC2 instances.
Environment Details
docker info:
Client:
 Version:    25.0.5
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.0.0+unknown
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx

Server:
 Containers: 26  Running: 26
  Paused: 0
  Stopped: 0
 Images: 5
 Server Version: 25.0.6
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2 nvidia
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
 runc version: 58aa9203c123022138b22cf96540c284876a7910
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 4.14.352-267.564.amzn2.x86_64
 Operating System: Amazon Linux 2
 OSType: linux
 Architecture: x86_64
 CPUs: 192
 Total Memory: 1.457TiB
 Name: ip-10-0-2-132.us-west-2.compute.internal
 ID: 15f20bda-0351-45ab-ad53-c8d80dd58902
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

curl http://localhost:51678/v1/metadata:
{"Cluster":"my-ecs-cluster","ContainerInstanceArn":"arn:aws:ecs:us-east-2:0000000000:container-instance/my-ecs-cluster/cd84e75764231289b1bkd206fi72m258","Version":"Amazon ECSAgent - v1.86.3 (*78a2bf0c)"}[

df -h:
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        747G     0  747G   0% /dev
tmpfs           747G  192K  747G   1% /dev/shm
tmpfs           747G  4.1M  747G   1% /run
tmpfs           747G     0  747G   0% /sys/fs/cgroup
/dev/nvme0n1p1  2.0T  180G  1.8T   9% /
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/75908095d9049666eeb194f2acdebed201a37464d6b736451988d9b7788c7e7f/merged
shm              64M     0   64M   0% /var/lib/docker/containers/d051c2ff3b372b802f8345415f44c9cb854dea42fdb117242eddf1b4cf28d131/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/13354169b95381eb57886c3f57b66c3bdd7378d5e88674fe6c93be5df0341eae/merged
shm              64M     0   64M   0% /var/lib/docker/containers/c3cfb4a8e7c7ed26a7fe06cd07be006814a1a6754816554edc82ebfb4b964b70/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/adba0c57bef371f0b59333d991fcd9ec03259cf66316a6f0a7840e271859573d/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/0a55bbb1de653ba266bef399838e16d419e53cc3959e349196c24a40e5bd93fb/merged
shm              64M     0   64M   0% /var/lib/docker/containers/8cd6dc2f806ab1b28a7abaa7faffcf192c64fadcbd20a4bcd38cd782cf447323/mounts/shm
shm              64M     0   64M   0% /var/lib/docker/containers/b2b805eaa6b03557ab51e8718e0e358a80899472b7fa1ea25696260fdf1bae28/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/106e197ff6f8bca3186ffe79500f9d39118fe631a73227db4e9d9feda0c430fe/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/51ea09b880f730bd8401a02ba7e1ddcb1355e3a07217813678c9c6ab1d9b3916/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/3981bb1d5cd3cc3ceb9d93e7b8bac5ff3cd48a9a3dc5fe5111c6d0d9ddcb8c35/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/f0ff09d07dc268742c5cf822f25b4e2e808e927f970367bcd8891cfcf9edf845/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/205d2733fe0eaebefad382923d87724a7d030d3d4a97db462e3d5b43971c54b7/merged
shm              64M     0   64M   0% /var/lib/docker/containers/1b4c28b1c3c027f6b23257b079fc32502d8d7a5e9ad8a750b1c4b8d30fe2d359/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/804329014a4e65d8fde5434bbe45524871bb85e680e3858eab410d0803fbfe55/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/58d54b86009dc496217d00c6ad6868af3fb7b6a94d8d91b0f8a7a3f133d45524/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/96023af81fb1c64109215f8b72dd502d36cbf833caeb8eff5daf4ab211711a84/merged
shm              64M     0   64M   0% /var/lib/docker/containers/594a961052567e09a1fb5045753a084b4694393c83f04093a51d70673adb8af7/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/37fa80b308db379ef1c5f856ad7c3acd638723e8043a983b3cfd0cc783df4a48/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/ccca21342476e7748f59bc01ac62eb80ac240a3551af17acb8da5e8efb715b92/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/11929964a105c2563fc43162b8c533e38e380a7aaf4f246eb219c22ceed2aad7/merged
shm              64M     0   64M   0% /var/lib/docker/containers/615338fb533f8e6e5fcbd31faa28e9d214dec1d577ee194f30067c78bee928f4/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/037114f77c35a836c3a404d0afa119fd60bbb17e7928bd76808a98d40af90838/merged
shm              64M     0   64M   0% /var/lib/docker/containers/b08883992f0c40a6b0a26cf3ea778979fab30de3129e569200e4b0b09ef268e1/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/11158010fd59709c33f8aa3737f9b2bed99d88a8e71ccf1bff8572f13462994a/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/096723829a6e9422512296ec229c8390ac0be538240259cf73978d84342a9e1f/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/bc56d64d85f094938f9ece7484a06d9daae7ee95f39c61f16faf1a39bed6fc5a/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/28ab86ad867dc6f181b8470a500a8a131475902306b8e2845166724340b27cca/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/a5c164d50643790c9cf19bcf0c7f1a27ff6f446945ec8bc8ae0d8b6a65b6b0c8/merged
shm              64M     0   64M   0% /var/lib/docker/containers/2389eb4c023889900be4401b3386e64464354c71d220f8b38a32585777d43937/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/be3a5bf1df6251f1738d322f483a8459d7bbfde8e8253037bbfc99bd5e4bd4e3/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/d4113d8f1f4850f5ff2ebf02832b2ad0a9108282ce1f55a07bd5598accc5eb3d/merged
shm              64M     0   64M   0% /var/lib/docker/containers/bf73f5d1f0a289b6c2b006d7e2c75324985773159ba1e1456925c60fb0176c36/mounts/shm
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/7a7896e24a77ff4cb9cec2043182c542ec740eec762f4cd92ec8ceda36b1c34c/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/4772f3fcda060c06dc89b20e5d56ccd8346577530a3a300a2609ab52df77618f/merged
overlay         2.0T  180G  1.8T   9% /var/lib/docker/overlay2/0b127fa447b2bca958b0f01cfa6cb5782bd2798466d7aef5c800d5fe45161ed7/merged
tmpfs           150G     0  150G   0% /run/user/0

Hi. Do you have any logs we can refer to?

I suspect this is a duplicate of #41


Names of first week tracks disappeared

Found strange detail about Story Mode menu. There are no names of first songs in a week. I don't know why. I rebuilt the game from zero and this is still here. Is this my problem or Kade Engine one?

Bug in the original Funkin source that cuts off the last song.

Will this thing will be somehow fixed in future? Cause I saw that many mods which used Kade don't have such an error.

It will be fixed. There's already a fix in Funkin's PRs

This is already fixed.

budget how-to-fix-this-bug method if you lazy to redownload source code

Oh,  I see, I redownloaded source code and get plenty of new things, including this fix. Thanks!