Unable to use collapsible when looping through an object array

I tried looping through collapsible using two methods. when my data is taken from the component as shown in the comment it doesnt work and only yields an expanded list with no collapsible
but when i use an array declared inside the template it works just fine. please help!

                {{i.name}}

filter_dramaFirst

Lorem ipsum dolor sit amet.

@crizzy9 this should work:

{{value}}

{{value}}

values = ["First", "Second", "Third"];

Check out the example code: https://github.com/InfomediaLtd/angular2-materialize/blob/master/app/components/collapsible.ts#L22

Closing. Please let me know if there still are any issues.


Auto-Open URL recognizes but not opens URLs without scheme

Scanning URLs like github.com sends an error that says "Application can't be opened -50".

Thanks @electr1fy0, I've added a simple evristic to handle this 1.5.2


Add a wrapper

imported from https://github.com/NixOS/nixos-weekly/issues/23#issuecomment-251165661
The next level of power would be to wrap it so that it's not necessary to ship styx. For example if it's made part of nixpkgs. Then just need a top-level default.nix and the content of the site are needed. The default.nix would look like:
with import <nixpkgs> {};
stdenv.mkStyxSite {
  name = "my-site-name";
  conf = import ./conf.nix; # or keep it inline
  src = ./.;
  # ...
}

I have played a little with this idea, and I am not sure if this can be implemented.
This require to call nix-build (styx build is just a wrapper around nix-build) during a nix build (mkStyxSite), and Nix dislike it.
It throws the following error:
error: creating directory ‘/nix/var’: Permission denied

But maybe I am just taking a wrong approach?

Took a different approach, so now styx sites can be builded with a simple callPackage call.
Example integration with NixOps.
Note: This require changes in nixpkgs that are not yet commited upstream, but that will be for the 0.4.0 release.
Closed via 163281e0c25d88e5bb3cd91889fa3b8028b98ccb.


Anerdw: Blacklist<PHONE_NUMBER>9

Anerdw requests the blacklist of the number<PHONE_NUMBER>9. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'a good watch, but superseded by a blacklister at https://chat.stackexchange.com/transcript/11540?m=66499828#66499828'


[WIP] OT API using Brave 4

Move to Brave 4 implementation for backing the OpenTracing API layer

[ ] BraveTracer
[ ] BraveSpan
[ ] BraveSpanBuilder
[ ] BraveSpanContext
[ ] JRE 7 compatibility
[ ] brave package space

...

@adriancole I've never used retrolambda, can you look at the config to double check?

for those reading along, eventually this pull request will look like a cleaned up version of this https://github.com/openzipkin/brave/tree/master/brave/src/test/java/brave/features/opentracing

Interesting :)
In which version of brave will this be included? Will OT become the main api for brave?

In which version of brave will this be included? Will OT become the main api for brave?

There's no plan for OT to be the main api for brave, and this wouldn't
make sense to do. This has been discussed in several forums, reasons
including leaky abstraction, lack of engagement, non-goal of interop.
There's also practical reasons like OpenTracing java being 0.X and
also having deprecated methods included (some of which are things
zipkin needs). Note there is also no plan to make Brave's primary
interface HTrace or Finagle's tracer, despite both having large
ecosystem and/or influence with far less marketing.
So, this will not be the main api for brave as it would be a step
backwards and couple compatibility through a leaky and unstable (<1.0)
api.
brave-opentracing is the main effort towards bridging between
various versions of opentracing and would be versioned appropriately
for that. For example, we also have zipkin-finagle, which has the same
bridging goal, and similar to here, since decisions are primarily made
out of the openzipkin org, we have a bridge project to align
appropriately.
Hope this makes sense.

When I originally commended, I thought I was at the /openzipkin/brave repo 😅 . Since then, I rephrased my question. Your response answered it anyway, thx :)

@adriancole Not sure if its needed or not to add this to the brave3 context / thread binder. I know you want to do a thread context API in brave4, should we use brave3's context until that is worked out?

I understand this like: there is X─B3─ParentSpanId but X─B3─TraceId is
missing (or similar combinations).
perhaps.. anyway it is a bit of a bike shed topic
https://github.com/openzipkin/b3-propagation/issues/3

I don't think this PR should use any brave-specific propagation api, as OT does not define propagation at this level of abstraction. Rather, it would using the "global-tracer/active-span" contrib stuff.
In other words, no reason to include brave 3 apis directly, unless it is a part of supporting the OT extension apis

Ok, cool. Then this is close. Just want to look over the tests a bit more for completeness.

Isn't ExtractFailurePolicy.TAG_AND_RESTART redundant? if there is a
standard tag for it, it makes sense, otherwise it would by tracer specific.

I don't know of such a tag, but anyway whether or not to add a tag is a
policy choice.. the goal was to kindof think about this since there's
literally opposing valid view points about how to handle malformed stuff.

It's definitely a good idea :+1: thanks.
Could you please raise it in OT/spec repo as it is your idea :+1: ? Or I can do it.

It's definitely a good idea 👍 thanks.

np

Could you please raise it in OT/spec repo as it is your idea 👍 ? Or I
can do it.

feel free to raise it if you feel it should proceed.
I think the topic is how to address ambiguity in extraction. The motivation
is that nuance limits effectiveness of layered software (as right now they
don't know whether to expect null or catch an exception etc).
possible solutions:

add policy to how a tracer is constructed, so that the tracer's method of
extraction follows rules.
expose the policy w/o indicating how it was set, so that layered
instrumentation know what to expect
punt policy to instrumentation layer who guess on grey areas (ex look for
null, catch exceptions etc)

Honestly I'm not sure what exactly to modify in the current README. The old one is still completely applicable (the magic of using the same interfaces). I guess there might be some context from the discussion in this thread missing though.
@adriancole you have edit permission if you want to take a shot

wrt the README, this is probably not valid "BraveTracer tracer = new
BraveTracer();"
also the status section is completely invalid and can be removed
how about fixing those two things?

ex. for the README
Tracer braveTracer = Tracer.newBuilder().....build();
BraveTracer opentracing = BraveTracer.wrap(brave);
later we can do more, but minimally the above and removing the status
section should be good enough

thanks @devinsba for all the work here!  Thanks also @felixbarny and @pavolloffay for taking a look. will release shortly

going out now as v0.18.0

This is great :+1: :+1: :+1:  thanks!

Agreed, thank you @devinsba and @adriancole!


Transform data before storing in cache

This PR adds a check if the strapi-plugin-transformer plugin is installed. If it is, it should transform the data before storing into the cache provider.
This relates to #25, and seems to solve the issue afaik

Thank you @nystrand1 for your contribution!

Thank you @nystrand1!

Much obliged!


Get persp name from number

every perspective has a number and a name. Is there a good way to get the perspective name when you have the number and vice versa?

This simple function could help you:
(defun isr/persp-select (arg)
  "Switch to perspective number ARG, default to 'main'."
  (interactive "P")
  (let ((new-persp (if arg (nth arg (persp-names)) "main")))
    (when (and new-persp (not (string= (persp-name persp-curr) new-persp)))
      (message "Switching to perspective '%s'" new-persp)
      (persp-switch new-persp))))


Add URLSearchParams article

R: @PaulKinlan  @mikewest @petele @robdodson
I added the card image but the dev server was still giving me 404s. Not sure what gulp command I need to run to get it to show up.
This should be pushed after the demo at https://github.com/GoogleChrome/samples/pull/283 lands.

R: @jpmedley

@ebidel you need to put the image in images/2016/01/urlsearchparams folder <- the url points to that. You have put the image is in images/2016/urlsearchparams.  Just add in an /01/ folder and all will be good.

PTAL

lgtm

Other than a quick comment LGTM.  @jpmedley are you ok with this?


[Question] iBeacon/Eddystone Support

Has anyone tried to fiddle with capturing BT Low Energy packets with this code?  Where would I look to start hacking this in?  I have a Raspberry Pi Zero W and it sniffs the packets great with hcitool, so seems like it could be a nice addition for near real-time proximity detection.  No latency/overhead associated with the regular BT or AP polling.

@regeland This code is compatible with sniffing Bluetooth. There is a CLI utility (https://github.com/schollz/find3-cli-scanner) that allows you to do that and send the results to FIND3.


Snakeyaml vulnerability in OpenSearch 2.2.1

Opensearch 2.2.1 has a dependency on vulnerable Snakeyaml version 1.26.
Dependency Hierarchy:
-> opensearch-2.2.1-SNAPSHOT.jar (Root Library)
-> opensearch-x-content-2.2.1-SNAPSHOT.jar
 -> ❌ snakeyaml-1.26.jar (Vulnerable Library)

Please check details of the WhiteSource scan here
This is a CI blocker in case changes are required in plugin bundled with core 2.2.x.

I think OpenSearch core is not affected by the CVE-2022-1471.
Although snakeyaml library exists in the build artifact of OpenSearch, it's not used directly used by OpenSearch.
The dependency snakeyaml is used by jackson-dataformat-yaml in opensearch-x-content library.
I checked the code repository of jackson-dataformat-yaml, snakeyaml is used for low-level YAML parsing, see here for the code, and the vulnerble SnakeYaml's Constructor() class doesn't occur in the code base.
Currently seems it's not possible to mute the alert from security scanners, because seeing from the CVE description, the mitigation is to use alternative API, instead of upgrading the version.
In addition, Security Analytics plugin may be affected by the vulnerability, which is not part of this code repository, and the fix will go in 2.5.0 release on Jan 17, 2023, see the PR https://github.com/opensearch-project/OpenSearch/issues/5576 for detail.
I will close the issue, please free to reopen if you have further questions.

Update on April 2023:
There are 2 locations OpenSearch use snakeyaml:

Transitive dependency for jackson-dataformat-yaml library
As confirmed from the active contributors of jackson-dataformats-text in the related issues (https://github.com/FasterXML/jackson-dataformats-text/issues?q=is%3Aissue+snakeyaml+cve), jackson-dataformats library is not affected by CVE-2022-1471.
The version of snakeyaml library will be upgraded in the next version release of jackson-dataformats-text .
In class ExtensionManager
snakeyaml usage is introduced in the commit https://github.com/opensearch-project/OpenSearch/commit/c2307fb82005fdd61b9d89bf35e9916ea412155d in January 2023, in OpenSearch 2.5.0. The usage is likely been affected by the CVE.
While in OpenSearch 2.6.0, the venerability has been remediated by the commit https://github.com/opensearch-project/OpenSearch/commit/a5dc22a174e4d2964fb4e6bc84f0b27957d0fddf.
The version of snakeyaml has been upgraded to 2.0 in the commit https://github.com/opensearch-project/OpenSearch/commit/8bda365902ae665bc2082d5b6932b28a1fcb4803, which will be released in OpenSearch 2.7.0 and 3.0. snakeyaml version 2.0 is not affected by the CVE.


Added pokemon uploading, deleting, clone-checking, and visibility settings

Update 2016-03-01: All the other stuff I was working on builds off of changes made in this PR, so I squished it into a general "Pokemon handling" PR.
Notable additions:
POST /uploadpk6: Uploads a pk6 file. The server computes a clone hash and tells the user whether the pokemon is unique.
GET /uploadpk6: Very basic upload form as a proof-of-concept, this should probably be replaced later when we implement the upload button into the client.
GET /pokemon/:id: Gets a pokemon by ID. This takes the visibility and the owner into account.
DELETE /pokemon/:id Deletes a pokemon from the server. Returns a 403 if the request was made by someone other than the owner.

Alright, this should be ready to merge.

:+1: merging


Part of documentation is not working (Account, Comment, Hashtag, Like, Location, Media, Relationship, Thread, ThreadItem, Upload...)

I noticed that you can not open those links:
Account, Comment, Hashtag, Like, Location, Media, Relationship, Thread, ThreadItem, Upload

Is there a way to check it? the usage of those classes?

Yep, in source files u can find names of methods and required arguments.
For example in Like.js
`
Like.create = function(session, mediaId) {
...
}
Like.destroy = function(session, mediaId) {
...
}
`
So if u want to like or unlike:
Client.Like.create/destroy(session, photoID);
Same for other classes.

Thank you for your reply


Very slow Docker builds when oslogin is enabled

Hi, I observed this surprising behavior today:

log into a machine with OS Login enabled

try to build a docker image that uses a non-root user, for example with the following instructions in the Dockerfile:

FROM ubuntu:16.04

RUN adduser --disabled-password --gecos '' --shell /bin/bash user
USER user

[...install programs, move files around, do some regular Dockerfile stuff...]

the resulting build is extremely slow

Using strace on the host's dockerd during the build, I saw many syscalls trying to access files inside the container (I'm not familiar at all with how Docker/OverlayFS handle this). I was able to see that many of those file accesses trigger a request to http://metadata.google.internal/computeMetadata/v1/oslogin/users?uid=1000, which returns a 404 Not Found. This is likely because the OS Login system doesn't know anything about uid 1000, since it's a user created inside of the Docker container.
By using the default "root" user in the container instead of switching to a custom user, the problem disappeared.
I can't really decide if this is a more of an OS Login or Docker issue, but I thought you should be aware of this.

So what seems to be happening here is that you're creating a user within the container that is not known to the VM outside the container. During the build, commands run as this user result in some files being created with the owner set to its UID (default 1000). Separately, some docker processes running outside of the container look at these files and as a result try to look up what name that UID should resolve to. Since it is not a local user on the VM, it tries a lookup to the OS Login service which also indicates this is an unknown user. If you do this a lot in a short time, you can be throttled by the OS Login service, resulting in an overall slowdown for your build process.
Overall this is normal behavior for user lookups and for docker builds, so it isn't a strictly speaking a bug. It's a side effect of the fact that you have a user which only exists inside the container, but whose files are being looked at from outside of the container. Even without OS Login, there would be a lot of these failed UID lookups, just without any slowdown side effect since they'd only need to check the local passwd database.
In the future we are looking at improving the local caching layer for OS Login to also cache missed lookups, which will resolve this kind of issue. In the meantime, there may be some workarounds. You could create a user on your VM with the same UID prior to running docker build, optionally removing it post-build. You could move the USER verb to the end of the dockerfile (and maybe do some retroactive chown if needed). Or you could restrict yourself to only building containers which have embedded users on a non-OS Login VM.

Thanks a lot @hopkiw for the detailed reply ! There are a few workarounds as you mentioned. However I agree that caching missed lookups would be quite nice.


I cant put hexagons in the atom square thingies

I cant put hexagons in squares, i removed the rectangle, and tried

Left clicking
Right clicking
Dragging it in
Trying every possible hexagon thing and dragging it in
Holding shift and dragging it in
Holding ctrl and dragging it in
Holding a cup of water and dragging it in
Looking the other way while dragging it in
Dragging it in 16 times
Dragging it out
Dragging the square in a position that has the hexagon thing in the perfect spot
Dragging the square into the hexagon
Telling the hexagon to drag itself into the square (it wouldnt listen)
Being very gentle and kind to the hexagon
Being very rough and mean to the hexagon
Un hexing the gon

none of these solutions have worked and the hexagon is yet to be put inside the square so I ask help from the gods of cellpond to help me hexagon the square (please)

same for me, no clue what to do. @TodePond may want to look at this

figured it out, it's not the hexagon anymore, it's the triangle


Carousel synchronization

The carousel is looking good, but the 6 mini dots in the bottom section and the carousel is no synchronized properly and an arrow option can be added to toggle back and forth between the carousels.
I  will be very Glad to work upon it

#318 is there


TimestampRange filter accepts 'now' as bound

:question: What
TimestampRange filter accepts "now" as time bound (both start or end)
:white_check_mark: Checklists
This section contains a list of checklists for common uses, please delete the checklists that are useless for your current use case (or add another checklist if your use case isn't covered yet).

[x] Is there unit/integration test coverage for all new and/or changed functionality added in this PR?
[ ] Have the changes in this PR been functionally tested?
[ ] Have new components been added to the related all.go files?
[ ] Have new components been added to the documentation website?
[x] Has make gofmt-write been run on the code?
[x] Has make govet been run on the code? Has the code been fixed accordingly to the output?
[x] Have the changes been added to the CHANGELOG.md file?
[ ] Have the steps in CONTRIBUTING.md been followed to update a Go module?

Codecov Report

Merging #106 (205095b) into main (a556a82) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
+ Coverage   45.68%   45.82%   +0.13%
==========================================
  Files          50       50
  Lines        3642     3651       +9
==========================================
+ Hits         1664     1673       +9
  Misses       1788     1788
  Partials      190      190

Impacted Files
Coverage Δ

filter/timestamp_range.go
78.94% <100.00%> (+6.53%)
: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 a556a82...205095b. Read the comment docs.


Add --compact option to snapshots

With --compact, snapshots doesn't list directories and puts all tags on a single
line. This way each snapshot takes up exactly one line. Fixes #1218.

Codecov Report

Merging #1223 into master will decrease coverage by 5.71%.
The diff coverage is 4.76%.

@@            Coverage Diff             @@
##           master    #1223      +/-   ##
==========================================
- Coverage    52.8%   47.08%   -5.72%
==========================================
  Files         126      126
  Lines       12232    12244      +12
==========================================
- Hits         6459     5765     -694
- Misses       5016     5777     +761
+ Partials      757      702      -55

Impacted Files
Coverage Δ

cmd/restic/cmd_forget.go
33.33% <0%> (ø)
:arrow_up:

cmd/restic/cmd_snapshots.go
33.04% <5.26%> (-2.88%)
:arrow_down:

internal/backend/b2/b2.go
0% <0%> (-79.32%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-73.9%)
:arrow_down:

internal/backend/azure/azure.go
0% <0%> (-61.93%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-59.85%)
:arrow_down:

internal/backend/swift/config.go
34.37% <0%> (-56.25%)
:arrow_down:

internal/archiver/archiver.go
65.47% <0%> (+0.16%)
: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 8e5b1e6...7d5b17a. Read the comment docs.


Function calls are not supported in decorators

I am getting ' Function calls are not supported in decorators but 'ɵmakeDecorator' was called' when I ma running the following command on command prompt:
ng build --prod --aot
Please provide the solution or reason to resolve this issue.
Thank you!

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Build fail

Hello, i am having trouble integrating raix:push to Meteor project. It is difficult for me to follow installation procedure.
I have created new blank Meteor project. Meteor is v1.8.1
These are steps i tried:

meteor create push-test
meteor add-platform android
meteor run android-device
result>APP BUILDS
meteor add raix:push
meteor run android-device
result>ERROR

Where:    Script    /home/borivojeskrbina/Documents/meteor/push-test/.meteor/local/cordova-build/platforms/android/phonegap-plugin-push/yk17zv6fodte-push.gradle    line: 6    What went wrong:    A problem occurred evaluating script.    home/borivojeskrbina/Documents/meteor/push-test/.meteor/local/cordova-build/platforms/android/app/AndroidManifest.xml    (No such file or directory)
Questions:

I see that "phonegap-plugin-push" is already installed (v1.9.0). Does it installs with raix:puh? Documentation say it should be installed separately.

AndroidManifest.xml is located in platforms/android/app/src/main but "phonegap-plugin-push" is trying to find it in platforms/android/app. Should i copy AndroidManifest.xml to app folder? Then i will have 2 AndroidManifest.xml files.

I copied AndroidManifest.xml to app folder and build app:
result>APP BUILDS

meteor add<EMAIL_ADDRESS>

meteor run android-device
result>APP BUILDS

Added<EMAIL_ADDRESS>to cordova-plugins

meteor run android-device
result>ERROR

What went wrong: Execution failed for task ':app:processDebugGoogleServices'. File google-services.json is missing. The Google Services Plugin cannot function without it.

Copied google-services.json to platforms/android/app
meteor run android-device
result>ERROR

What went wrong: Execution failed for task ':app:processDebugGoogleServices'. No matching client found for package name 'com.idh35i361d1pil.yk17zv6fodte'

In mobile-config.js i added

App.info({     id: "com.gvisp.smartshoppinguser", });

meteor run android-device
result>ERROR

 /home/borivojeskrbina/Documents/meteor/push-test/.meteor/local/cordova-build/platforms/android/gradlew: Command failed with exit code 1 Error output: Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. java.lang.IllegalStateException: Dex archives: setting .DEX extension only for .CLASS files
What went wrong: Execution failed for task ':app:transformClassesWithDexBuilderForDebug'. com.android.build.api.transform.TransformException: java.lang.IllegalStateException: Dex archives: setting .DEX extension only for .CLASS files
Can you tell me why build fails? I didn't do any coding yet, just trying to build.
Thanks for help.

@dev8gvisp
Dont copy or move any android manifest files, they are automatically generated
You have to add the google services json file in your ".meteor\local\cordova-build\platforms\android" Folder,
This file you can get from Firebase
Mobile config json
App.info({
id: 'com.gvisp.smartshoppinguser',
});
Download android studio, and open the platforms android folder, you need to download the java libraries with gradle
in build.gradle
configurations.all {
resolutionStrategy {
force 'com.android.support:support-v4:27.1.0'
}
}
configurations {
all*.exclude group: 'com.android.support', module: 'support-v13'
}

The correct gradle file to modify has this line at the begining of the file:
apply plugin: 'com.android.application'
Add this two your dependencies:
classpath 'com.google.gms:google-services:4.1.0' // I added both of these
classpath 'com.google.firebase:firebase-core:11.0.1' // I added both of these
At the end of your build.gradle file add:
apply plugin: 'com.google.gms.google-services'
In case your run into errors with conflicting google libraries add:
configurations.all {
resolutionStrategy {
force 'com.android.support:support-v4:27.1.0'
}
}
configurations {
all*.exclude group: 'com.android.support', module: 'support-v13'
}

This library needs dependencies that do not come bundled with the cordova app.


EntityTag tag in item's tag tag doesn't use the base tag

-- source

:tada: This issue has been resolved in version 1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


User login page

Requirements:

Input field for player name
Login button
Open websocket session

React+Bootstrap UI


Fix no such module 'DOT'

Problem
create cli folder and put this Package.swift
// swift-tools-version:5.1
import PackageDescription

let package = Package(
    name: "Tools",
    dependencies: [
        .package(url: "https://github.com/yonaskolb/XcodeGen", .branch("master"))
    ]
)

and run
swift run --package-path cli xcodegen
cause this error
XcodeGen/Sources/XcodeGenKit/GraphVizGenerator.swift:1:8: error: no such module 'DOT'
import DOT`

Solution
Update GraphViz 0.2.0 to 0.4.0
diff
With this update, we no longer to import Dot.
Changed package to produce a single library named `GraphViz` so that
  `Dot`, `Tools`, and `GraphVizBuilder` need not be imported separately anymore.

Hi, @yanamura, thank you for your contribution! Could you update CHANGELOG.md about your fixing?
Example: https://github.com/yonaskolb/XcodeGen/pull/1064/files#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed
please make Fixed column in Next Version.

It looks like CI didn't run for this PR for some reason. But now we have errors
ld: warning: Could not find or use auto-linked library 'cgraph'
ld: warning: Could not find or use auto-linked library 'gvc'
Undefined symbols for architecture x86_64:
  "_agerrors", referenced from:
      _$s8GraphViz7attempt8throwingxxyXE_tKlF in Error.swift.o
  "_aglasterr", referenced from:
      _$s8GraphViz5ErrorV04lastC7Message026_24C6592C881063ABBFDC7A6D4J5AA881LLSSSgvgZ in Error.swift.o
  "_agmemread", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_SpySo8Agraph_sVGSgSPys4Int8VGKXEfU_AWyXEfU_ in Renderer.swift.o
  "_gvContext", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_ in Renderer.swift.o
  "_gvFreeContext", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_6$deferL_yyF in Renderer.swift.o
  "_gvFreeLayout", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_6$deferL0_yyF in Renderer.swift.o
  "_gvFreeRenderData", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_6$deferL1_yyF in Renderer.swift.o
  "_gvLayout", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_ySPys4Int8VGKXEfU1_s5Int32VyXEfU_ in Renderer.swift.o
  "_gvRenderData", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_ySPys4Int8VGKXEfU2_s5Int32VyXEfU_ in Renderer.swift.o
  "_gvToolTred", referenced from:
      _$s8GraphViz8RendererC6render3dot2to2on10completionySS_AA6FormatOSo17OS_dispatch_queueCys6ResultOy10Foundation4DataVs5Error_pGctFyycfU_AQyKXEfU_s5Int32VyXEfU0_ in Renderer.swift.o
ld: symbol(s) not found for architecture x86_64
<unknown>:0: error: link command failed with exit code 1 (use -v to see invocation)


add php 7.4

This looks good to me. Though a few questions (also aimed at @Nyholm):

Do we win anything by adding the snapshot now and upgrading to release version 7.4 within 2 months? Or are we just as well off waiting 2 months with adding thing?
When 7.4 is released, there is less than a week of planned time until PHP officially stops supporting 7.1. Do we drop 7.1 support at the same time PHP does, or do we keep legacy versions around for this library?
We already do PHP nightly testing, but that is described as PHP 8.0. Is there some way we can test both the PHP 8.0 and the PHP 7.X branch at all times? (Where X will be 5 once 7.4 is released?)

Sorry for the delay.
Thank you for this PR.


Implement Fisheye as a TextureDome

Implement a new texturedome In order to show 360 fisheye videos.
The idea is to dewarp the video provided and project it to a (half) sphere.

Closing as not needed anymore by partner


Manual Installation

CocoaPods and Carthage are awesome tools and make our life really easier, but there are some devs who still don't know how to use them.
It would be cool to add the Manual installation guide in your README.md. You can take a look at my iOS Readme Template to see how you can do it.

Good suggestion @lfarah
I'm on it.


Test alternative rules for falling

Only fall if chunk is loaded

@nsg Please give it a test

@petterarvidsson works, slower. As expected, merge it! :)

I will merge this now, sorry. Think this is the lesser evil consider that the code in master is "a little broken" atm.
Btw, if you do a lot of whitespace changes, try to keep them to a separate commit, hard to tell what has changes, here is the difference for the curious:
$ git diff --ignore-space-change master
diff --git a/src/main.c b/src/main.c
index 5f1668f..3db89e6 100644
--- a/src/main.c
+++ b/src/main.c
@@ -1489,7 +1489,7 @@ void handle_movement(double dt) {
     vy = vy * ut * speed;
     vz = vz * ut * speed;
     for (int i = 0; i < step; i++) {
-        if (g->flying) {
+        if (g->flying || !find_chunk(chunked(s->x), chunked(s->z), chunked(s->y), 0)) {
             dy = 0;
         }
         else {
@@ -1521,22 +1521,6 @@ void parse_blocks(int p, int q, int k, char* blocks, int size, State *s) {
     g->blocks_recv = g->blocks_recv + CHUNK_SIZE * CHUNK_SIZE * CHUNK_SIZE;
     int out_size = inflate_data(blocks + BLOCKS_HEADER_SIZE, size - BLOCKS_HEADER_SIZE,
                                 g->chunk_buffer, g->chunk_buffer_size);
-        int is_empty = 1;
-        for (int x = 0; x < CHUNK_SIZE; x++) {
-            for (int y = 0; y < CHUNK_SIZE; y++) {
-                for (int z = 0; z < CHUNK_SIZE; z++) {
-                    int w = g->chunk_buffer[x+y*CHUNK_SIZE+z*CHUNK_SIZE*CHUNK_SIZE];
-                    if(w != 0) {
-                      is_empty = 0;
-                      /* break all loops */
-                      x = CHUNK_SIZE;
-                      y = CHUNK_SIZE;
-                      z = CHUNK_SIZE;
-                    }
-                }
-            }
-        }
-        if(!is_empty) {
     Chunk *chunk = find_chunk(p, q, k, 1);
     if(chunk) {
         memcpy(chunk->blocks, g->chunk_buffer, CHUNK_SIZE*CHUNK_SIZE*CHUNK_SIZE);
@@ -1557,7 +1541,6 @@ void parse_blocks(int p, int q, int k, char* blocks, int size, State *s) {
             }
         }
     }
-    }
 }

You are free to revert this PR if you think this is the right thing to do.


createAsyncIterator missing return() & throw()

In my interpretation of
https://tc39.github.io/proposal-async-iteration/#sec-async-from-sync-iterator-objects
I believe the return() and throw() methods are required to be an async iterator / "AsyncGenerator".
Thus, createAsyncIterator when creating an iterator for a native type such as Array should include the return() and throw() methods to cause the iteration to cease. Thus would allow it to behave as if it was a real AsyncIterator.
Tested on Chrome 68, for what it is worth.

+1 on this, this is pretty important imo.  Is this repo still being looked at?  I could probably contribute a patch...

Woah, thanks for getting to this.  I hope this helps other people!


Support for newer versions of Keras

Versions of Keras newer than 2.0.6 break my implementation of the mixture of gaussian loss. This occurs because the new version of Keras requires that you supply target values that are the same dimension as the number of outputs your network has, but when we're using a mixture density network we have 3*n outputs where n is the number of mixture components (corresponding to the mean, standard deviation and mixture weight parameters for each component)...

Hi. I tried to modify your codes to the newer version of Keras. One problem I found is that the demand_simulation.py file worked fine on Keras version 2.0.6, but not in the new version.
I got an error of "RuntimeError: It looks like you are subclassing Model and you forgot to call super(YourClass, self).__init__(). Always start with this line" when I ran line 72 of "response_model = Response(some arguments)". Do you have any ideas how does this happen? It doesn't seem to be related with the dimensions of mixture of gaussian. Thank you so much!


ERROR: unsatisfiable constraints: from faas-cli -action build -f ./urlping.yaml

I am following the readme and trying to get my first function running , but hit the below error when trying to build the image
-> sudo faas-cli -action build -f ./urlping.yaml
---> Running in 1075c04bc182
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz: temporary error (try again later)
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz: temporary error (try again later)
ERROR: unsatisfiable constraints:
curl (missing):
required by: world[curl]
The command '/bin/sh -c apk --no-cache add curl     && echo "Pulling watchdog binary from Github."     && curl -sSL https://github.com/alexellis/faas/releases/download/0.5.8-alpha/fwatchdog > /usr/bin/fwatchdog     && chmod +x /usr/bin/fwatchdog     && apk del curl --no-cache' returned a non-zero code: 1

Docker version docker version (e.g. Docker 17.0.05 ):
Docker version 17.06.1-ce, build 874a737

Are you using Docker Swarm or Kubernetes (FaaS-netes)?
Docker Swarm

Operating System and version (e.g. Linux, Windows, MacOS):
Linux Ubuntu 14.04

Link to your project or a code example to reproduce issue:

Hi @tijoytom
Thanks trying OpenFaaS 👍 ! I've just tried this myself again and it works fine, so I suspect this may be an issue with your internet connection. I also haven't run the faas-cli as sudo.
Step 2/15 : RUN apk --no-cache add curl     && echo "Pulling watchdog binary from Github."     && curl -sSL https://github.com/alexellis/faas/releases/download/0.5.8-alpha/fwatchdog > /usr/bin/fwatchdog     && chmod +x /usr/bin/fwatchdog     && apk del curl --no-cache
 ---> Running in 9a426aa71f45
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
(1/3) Installing libssh2 (1.7.0-r0)
(2/3) Installing libcurl (7.55.0-r0)
(3/3) Installing curl (7.55.0-r0)
Executing busybox-1.24.2-r13.trigger
OK: 32 MiB in 35 packages
Pulling watchdog binary from Github.
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
(1/3) Purging curl (7.55.0-r0)
(2/3) Purging libcurl (7.55.0-r0)
(3/3) Purging libssh2 (1.7.0-r0)
Executing busybox-1.24.2-r13.trigger
OK: 31 MiB in 32 packages
 ---> 26694207f995

Here's two things you can try:

Force an update on the base Python image:

$ docker pull python:2.7-alpine

Wipe cache

Use a flag of --no-cache=true on the faas-cli
Please let us know how you get on.

Hi we couldn't reproduce the issue, I'd check your networking and try again. Let us know how it goes and feel free to re-open.

@alexellis Thanks , I was able to get it working on my windows machine , no idea what's wrong with the Ubuntu box..

That's good to hear. I'd suggest trying it again, or maybe provisioning a quick droplet on Digital Ocean?

hi,I got the error,too.
It's the log:
[0] > Building hello-python.
Clearing temporary build folder: ./build/hello-python/
Preparing ./hello-python/ ./build/hello-python/function
Building: hello-python:latest with python template. Please wait..
Sending build context to Docker daemon  8.192kB
Step 1/25 : FROM python:2.7-alpine
---> c98d9ddf345d
Step 2/25 : ARG ADDITIONAL_PACKAGE
---> Running in ac04aa392a84
Removing intermediate container ac04aa392a84
---> e12c355af0d7
Step 3/25 : RUN apk --no-cache add curl ${ADDITIONAL_PACKAGE}     && echo "Pulling watchdog binary from Github."     && curl -sSL https://github.com/openfaas/faas/releases/download/0.9.6/fwatchdog > /usr/bin/fwatchdog     && chmod +x /usr/bin/fwatchdog     && apk del curl --no-cache
---> Running in cefce1ea66f8
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz: temporary error (try again later)
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz: temporary error (try again later)
ERROR: unsatisfiable constraints:
curl (missing):
required by: world[curl]
The command '/bin/sh -c apk --no-cache add curl ${ADDITIONAL_PACKAGE}     && echo "Pulling watchdog binary from Github."     && curl -sSL https://github.com/openfaas/faas/releases/download/0.9.6/fwatchdog > /usr/bin/fwatchdog     && chmod +x /usr/bin/fwatchdog     && apk del curl --no-cache' returned a non-zero code: 1
2018/10/31 17:15:20 ERROR - Could not execute command: [docker build --no-cache -t hello-python:latest .]

This was logged one year ago, do you still have it? We can't reproduce any issue like this so I wondered if you have a restrictive firewall or corporate network?
Alex

Hi @tijoytom
Thanks trying OpenFaaS  ! I've just tried this myself again and it works fine, so I suspect this may be an issue with your internet connection. I also haven't run the faas-cli as sudo.
Step 2/15 : RUN apk --no-cache add curl     && echo "Pulling watchdog binary from Github."     && curl -sSL https://github.com/alexellis/faas/releases/download/0.5.8-alpha/fwatchdog > /usr/bin/fwatchdog     && chmod +x /usr/bin/fwatchdog     && apk del curl --no-cache
 ---> Running in 9a426aa71f45
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
(1/3) Installing libssh2 (1.7.0-r0)
(2/3) Installing libcurl (7.55.0-r0)
(3/3) Installing curl (7.55.0-r0)
Executing busybox-1.24.2-r13.trigger
OK: 32 MiB in 35 packages
Pulling watchdog binary from Github.
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
(1/3) Purging curl (7.55.0-r0)
(2/3) Purging libcurl (7.55.0-r0)
(3/3) Purging libssh2 (1.7.0-r0)
Executing busybox-1.24.2-r13.trigger
OK: 31 MiB in 32 packages
 ---> 26694207f995

Here's two things you can try:

Force an update on the base Python image:

$ docker pull python:2.7-alpine

Wipe cache

Use a flag of --no-cache=true on the faas-cli
Please let us know how you get on.

Just as reference, I ran into this error and I'm under a corporate/firewall network. I ran the command again with the --no-cache=true directive and it did the work. I didn't run the $ docker pull python:2.7-alpine command though. Hope it helps.


pop out player on scroll / Add button to pop out via floating player

We removed the browser based pop-out button cause it would cause confusion between our pop out and the browser one, but now there's no way to force a pop out unless you navigate away.
Other suggestion would be to automatically pop out when scrolling down in comments (in both comment replies and original)

This could be done with an intersection observer
To detect when >X% of the player has passed the top of the viewport, then pop out
(and vice versa, pop in when scrolling back up far enough)

This could be done with an intersection observer
To detect when >X% of the player has passed the top of the viewport, then pop out
(and vice versa, pop in when scrolling back up far enough)

Hello guys, I'll be working on this one.

Hello guys, is this ok?
https://user-images.githubusercontent.com/1719111/107385710-e6556f80-6ad1-11eb-8a50-8e875a044c40.mp4
Regards.

That looks great! I wonder if we should force the pop-out player to the right side so it doesn't take over the comment area? @seanyesmunt thoughts?

I have pushed a WIP branch in the meantime https://github.com/Ruk33/lbry-desktop/tree/issue-4932-floating-player-scroll. Not sure about a few implementation details though...

Hello guys, just following this thread up, any other changes required or is this good? @tzarebczan @seanyesmunt . Regards!


[v2] Add outline buttons demo

I've added the outline buttons to the kitchen sink demo.

Merged, thanks


model serialization / validation schemas leaking into schema

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
As already discussed in https://github.com/tiangolo/fastapi/discussions/10019#discussioncomment-6737227 current pydantic defines different models in the schema when using both modes (validation/serialization) on a model - "{}Input" & "{}Output".
FastAPI started using mode=serialization for response models in 0.101 - bringing this issue up https://github.com/tiangolo/fastapi/discussions/10039 https://github.com/tiangolo/fastapi/discussions/10041.
This breaks all existing clients and invalidates every client code written due to changing the class name.
Current pydantic choose to change the name of the models again - adding a "-" before the Input/Output.
I understand there is a requirement to have different personalities, but the schema should be limited to a single personality - validation.
Example Code
import io

import yaml

from pydantic import BaseModel
from pydantic.json_schema import models_json_schema

class Pet(BaseModel):
    name: str
    weight: int | None
    color: str | None = None

data = models_json_schema([(Pet,"serialization"),(Pet,"validation")])
f = io.StringIO()
for d in data:
    for k,v in d.items():
        print(yaml.dump(v, f, indent=4))
f.seek(0)
print(f.read())

$ref: '#/$defs/PetOutput'
$ref: '#/$defs/PetInput'
PetInput:
    properties:
        color:
            anyOf:
            -   type: string
            -   type: 'null'
            default: null
            title: Color
        name:
            title: Name
            type: string
        weight:
            anyOf:
            -   type: integer
            -   type: 'null'
            title: Weight
    required:
    - name
    - weight
    title: Pet
    type: object
PetOutput:
    properties:
        color:
            anyOf:
            -   type: string
            -   type: 'null'
            default: null
            title: Color
        name:
            title: Name
            type: string
        weight:
            anyOf:
            -   type: integer
            -   type: 'null'
            title: Weight
    required:
    - name
    - weight
    - color
    title: Pet
    type: object

Python, Pydantic & OS Version
pydantic version: 2.2.1
        pydantic-core version: 2.6.1
          pydantic-core build: profile=release pgo=true
                 install path: ~/venv/openapi3/lib/python3.10/site-packages/pydantic
               python version: 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]
                     platform: Linux-6.2.0-26-generic-x86_64-with-glibc2.35
     optional deps. installed: ['email-validator', 'typing-extensions']

Selected Assignee: @adriangb

Would it be sufficient to add input_suffix: str = 'Input', output_suffix: str = 'Output', you could then set them both to an empty string?

@commonism I understand this is frustrating, but when the types are just incompatible for validation and serialization, it may be important to get different behavior. Also, to be clear, pydantic just exposes the ability to specify whether you want to use the output schema or the input schema, and provides automatic conflict resolution.
I'm not convinced that never using the output schema is the best behavior; e.g., for a model with a field of type Json[dict[str, int]], it seems to me unfortunate that if that was in a response field but we generated the JSON schema for validation, you'd get a type error in the generated client.
That said, I think there are a few things we can do to improve this:

Add a model config setting for whether fields with defaults are required in the output schema, and default this to false. This would be the same as the validation behavior, and I believe this is currently the source of the majority of issues where the validation and serialization schemas differ. There is also a reasonable argument to make that you should be able to opt out of having fields with defaults required due to things like exclude_unset when serializing. And I'm suggesting we default this to False because this is a such a common source of issues with FastAPI, and so it won't require any changes.
Add a model config setting that lets you override the schema generation mode even when mode='serialization' or mode='validation' is requested. That would give you the ability to ensure that, if you really want it, the generated schema will always be the 'validation' mode schema. However, I do not think we should do this by default as I think it is better to properly support the case that the input and output schemas are different, and like I said above, I think that changing the default requiredness behavior will eliminate most collisions
I think we can also add the ability to override the input/output suffixes, as Samuel has suggested, but do note that this won't resolve the issues brought up here because you'll just end up with collisions between the two different schemas. While we could perhaps add the ability to have a preferred resolution when there is a conflict, I think it's probably better to just rely on a mode override to prevent that.

So, basically, I'm proposing we add the following settings to the ConfigDict:
json_schema_serialization_defaults_required: bool = False
json_schema_mode_override: Literal['validation', 'serialization', None] = None
json_schema_validation_suffix: str = '-Input'
json_schema_serialization_suffix: str = '-Output'

and @commonism I think the only thing you'd need to change in your models is adding json_schema_mode_override='validation' if you really want to ensure that there is never a discrepancy even for non-idempotent types. (Another option might be to just use json_schema_validation_suffix='', which would at least ensure that if there was a difference, the validation version of the model didn't get renamed.)

If this is an acceptable solution, I don't think it will be very hard to implement.

I'm not frustrated about this, it's more like … surprised about the lack of re/action for ~3 weeks.
It's breaking the whole code stack your loyal fans and customers rely on.
No communication up-front about this breaking change and basically silence afterwards, not even acknowledging the issue.
I know - FastAPI is not your liability, but you've been more concerned/communicative about this.
Another option is - have the  model names static suffixed, using "…Ser" and "…Val", even if they match or serialization is not used, one could $ref the other.
Arguments would always be "…Val", results "…Ser".
Would be easier to work with than having to guess the model name depending on model internals.
Aside - currently the difference in models is having non required fields in validation which are required in serialization?
To clients - this should not matter, as the serialization validation schema will always be a superset of the validation validation schema?

I'm trying to figure a scenario where is there is a requirement to the consumers of the description document to distinguish in serialization and validation for the same model due to optional/nullable properties.
Pet.color - from above - nullable, optional - not required.
If server-side pydantic chooses to serialize (PetOutput schema) Pet.color as None if unset - what does it matter to the validation of the model in a client?
I'd expect the serialization of nullable&optional fields to None (instead of excluding/skipping) to create a superset of the model which is always valid according to the validation schema.
Which would make publishing the serialization schema to the consumers not required?

If server-side pydantic chooses to serialize (PetOutput schema) Pet.color as None if unset - what does it matter to the validation of the model in a client?

Let me try to demonstrate why it can be nice to distinguish between the case where a field is required or not based on the input/output mode in an OpenAPI schema.
Let's say I have an endpoint that looks like this:
class MyModel(BaseModel):
    x: int = 1

@app.post('/')
def increment_my_model(model: MyModel) -> MyModel:
    return MyModel(x=model.x + 1)

Let's say I generate a typescript client based on this schema. We'll get interfaces that look like these:
interface MyModelInput {
    x?: number
}

interface MyModelOutput {
    x: number
}

and some API client method will be generated that will look something like:
function incrementMyModel(input: MyModelInput): MyModelOutput {
  ...
}

In particular, I'd be able to do:
const doubleIncrementedValue = incrementMyModel({}).x + 1

without any type errors, correctly reflecting the actual API.
However, if I use the validation schema for serialization, the code snippet above will result in a type error saying that I can't add a number and undefined, since MyModel.x might be undefined.
More generally, in my experience it can be kind of a hassle if you have to check if a field is undefined everywhere you make an API call just because it has a default value in the server-side model; ultimately I end up just not using default values even if it makes sense because of this.

At any rate, it does sound to me like the suggestion I made above would mostly address your issues. I'll try to open a PR for it  today and if you still have issues we can look into them more thoroughly?

@commonism
This is the generated schema:
from pydantic import BaseModel

class Model(BaseModel):
    x: int = 1

print(Model.model_json_schema(mode='validation'))
#> {'properties': {'x': {'default': 1, 'title': 'X', 'type': 'integer'}}, 'title': 'Model', 'type': 'object'}

The value {} is valid for that schema, but will never be the result of serialization, and thinking it may be will require you to do additional checks that the value is present if you make no assumption about the JSON schema.
The new behavior ensures that you don't have to do this by default, and behaves properly when used with openapi-generator (which I would argue is one of the most important uses of pydantic's generated JSON schemas). I understand if you disagree with this, but I think that using openapi-generator is probably the most common way to generate API clients and, at least in my opinion, this improves the behavior of that generator (and more strictly reflects the generated JSON schema).
At any rate, my proposal here will give the option to control this behavior, and will even have it disabled by default; does that leave you with objections?

Now - take my example of using the Output model as input for e.g. PATCH.
Different classes, this is unsolved.

While this is true, I would argue that when the input and output schemas are different in a way that is incompatible, it probably makes sense to just manually convert data between them if necessary; anything more than that likely requires assumptions that are not strictly guaranteed by the semantics of JSON/OpenAPI schemas. (Again, I am happy to provide features that make it easier for you to work with though.)

{} can be the result of serialization - when excluding default value.
Model({}).x == 1
The limitation in your example is related to the use of typescript interfaces where default values are not possible at compile time. Easy fix, generate code which makes use of default values.
There is code generators which do not understand default values, but I do not see this can/should be resolved here, at least not as a default.
Providing standard workarounds for them keeps them alive & relevant instead of pushing the required changes.
As this degrades the quality of the description document I'd see this as opt-in instead of opt-out, creating awareness of the standards-compatibility issues for those who need it, and not making things worse for those who can do default values properly.
And, of course, having the possibility to change the settings does not help if you do not control the server-side of things.

{} can be the result of serialization - when excluding default value.

I agree, and that's why I think it's reasonable to have it as a configurable option even if you (or others) did agree with my original opinion that it should be the default.

The limitation in your example is related to the use of typescript interfaces where default values are not possible at compile time. Easy fix, generate code which makes use of default values.

This "easy fix" only works if I rework my client to generate types with accessor methods for fields with defaults. While it's admittedly been a while since I looked, I have not seen anyone use this pattern instead of using interfaces and objects, and I'm not aware of tooling (i.e., openapi generator templates) that would do this. (Not to mention the performance consequences.)
If I do want to use interfaces, and I want to make use of the generated interface itself in other parts of my code and still want it type-checked properly, this just fundamentally requires different types to encode guarantees about the presence of the field value.

There is code generators which do not understand default values, but I do not see this can/should be resolved here, at least not as a default.
Providing standard workarounds for them keeps them alive & relevant instead of pushing the required changes.

I am willing to concede that the current default behavior is less practical in some cases and introduces backwards compatibility pain for many, which is why I plan to change it so that fields with default values are not treated as required by default.

... I'd see this as opt-in instead of opt-out

It sounds like we are in agreement. I'll open a PR for this shortly.
That said, I will note that I still believe that when the validation and serialization versions of models have more fundamentally different structure than just default values being present or not (e.g., models with @computed_fields), the two schemas should involve the use of different types. (And would require explicitly opting out if you want it to always use the validation schema.)

This "easy fix" only works if I rework my client to generate types with accessor methods for fields with defaults.

Even when using the spread operator to apply default values?


try harder to figure out what the local DMR address/port is

This just attempts to make a better guess at the local-dmr address and port of the management endpoint.
Since we are running in the same VM we should be able to get the system properties that determine any custom address and port settings for the management endpoint of the local WildFly/EAP.

@jshaughn review this - we can merge once someone else says it looks good.
The idea here is the Java Agent wants to guess what the local DMR endpoint is - if someone overrides the address, port, or port-offset via startup system properties, the agent should be able to detect those and use them rather than rely on the hardcoded defaults (which are <IP_ADDRESS>, 9090, and 0 respectively).

This should help guess better.  It won't detect a change they make by editing the config file itself, but I would hope most people would use the sysprop. LGTM.

This is for HWKAGENT-164


Wiring up a Python project to Kestrel

How would I go about wiring up a Python project to this? For most work we do, we have a Flask or Django app that's using templating and databases.
Come deploy time, we back the project flat with something like django-bakery or frozen-flask. I imagine we'd use git-subtree to create a separate branch for the production application and then deploy it (This approach is similar to how Yeoman suggest you deploy applications).
How do you imagine that working with kestrel?

We use Kestrel for all of our Tarbell based projects by specifying a subdirectory to deploy. I need to add more gifs to the project documentation but here's a quick one.

So this will copy the folder baked-project-dir to 2014/<project-name>.

Here's the docs: https://github.com/mhkeller/kestrel/wiki/Command-line-interface#deploying
It needs flashier, yeoman style prompts and completion to make those sub-dirs easier to type.


Fix for Dark Mode for plots?

Hi,
I have tried using different dark mode options for the plots locally, but because of some hard-coded colors they become a bit hard to read.
Any chance the hard-coded colors could be modified or even removed?
Thank you for your work and your time.

Hi @cfmqm ,
It'd certainly be possible to make those graphic settings dependent on user input.
I won't be able to implement it that soon, if the community has a PR for that I'd gladly accept it. If not I'll try to allocate some time and solve this one. It might take a few weeks though.
Best,
Will

Thank you!


fix: color output in Solarized theme is the same as background

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description

Steps to Reproduce

Install Solarized or just set your terminal colors 8 and 0 to be the same (with the Ubuntu 18.04.2 LTS default terminal emulator go to Edit >> Preferences >> Profiles >> Color and click on the palette colors to modify them).
Run mocha on any local terminal-outputted tests. You should see that you can't read the test descriptions for those that succeed.

Expected behavior: All output is legible against the background (i.e. outputs to a color other than the terminal palette color 8 (which in Solarized, is the same as the background color)).
Actual behavior: Log messages for the success of a test output in terminal palette color 8 which is the same color as the background, making the text illegible.

Reproduces how often: Every time that I run mocha with Solarized as my terminal theme.
Versions

The output of mocha --version and node node_modules/.bin/mocha --version: 6.2.0
The output of node --version: v10.8.0
Your operating system

name and version: Ubuntu 18.04.2
architecture (32 or 64-bit): 64-bit

Your shell (e.g., bash, zsh, PowerShell, cmd): bash
Your browser and version (if running browser tests):
Any third-party Mocha-related modules (and their versions):
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version):

I don't see any reason why we should adapt our colors to Solarized. Just change the color settings in Solarized or use a different color scheme.
As a second option you could create your own Mocha reporter.


Add new exercise: bank account

problem specification | description |  canonical data

I've update the issue with some additional links @brendanmckeown !

@SleeplessByte - with porting this exercise to the JS track, was the intention to include the concurrency/multi-threaded tests?

Good question. Since JavaScript only sorta-kinda-but-no-really has multi-threading here, in this track I don't think it makes sense to have those. I think your PR makes sense :)

Fixed by #888


Enable tags for lb rules

Fixes #679
Use updateLoadBalancerRule instead editLoadBalancerRule
There is no editLoadBalancerRule api
After the fix, im able to see and add tags to lb rules

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/681 (JID-3452)

Thanks @ravening Could you also fix allowing delete tags in the same vue ?

ping @ravening - can you address David's comment? Thanks

ping @ravening - can you address David's comment? Thanks

Didn't get time so far.. will work on it either today or tomorrow

Thanks @ravening

@davidjumani @rhtyd made the change. Please review

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/681 (JID-3488)


Win pypy3.7

Need in https://github.com/conda-forge/aiohttp-feedstock/pull/64

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


WIP: Frontier & HIP support

This branch applies or allows the necessary changes to support compilation with HIP/ROCm, and for MI250x GPUs on Frontier specifically.  It will be merged when it reaches feature parity with kharma-next again.
Currently almost all changes concern leaving the possibility of calling host-only functions from host-device functions, which is a compile-time error in HIP.  This affects the coordinates (which can be fixed as-is) and reductions (which had to be eliminated for now).
Also adds scaling scripts, compile definitions, etc.

After overhauling reductions, Frontier support no longer requires eliminating them.  Build scripts etc are now in the AMR branch


python310Packages.effdet: init at 0.4.1

Description of changes
This will only be working on linux because of a pending dependency fix and my linux machine is stuck right now, so anyone being able to test this is welcome.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

@tjni I don't know if I can abuse your help one more time, this package needs to be tested with linux, but my linux machine is stuck right now. Just in case you have time, no worries at all if you don't.

Thanks for the feedback. I think I've taken care of everything you mentioned.

Result of nixpkgs-review pr 242386 run on aarch64-linux 1

2 packages built:

python310Packages.effdet
python310Packages.effdet.dist

Thanks again for your help here!
I'm going to wait for the ofborg-eval to finish just in case before merging.
Again, if there is ever anything I can do to help back, ping me anytime.


override dependencies installed by git clone

[x] in random places in code
[x] directly in .travis.yml commands

The direct motivation here is ManageIQ whose sub-repos git clone the main repo in a script called from .travis.yml:
https://github.com/ManageIQ/manageiq-providers-kubernetes/blob/gaprindashvili-1/bin/setup#L8
But there are tons of projects doing some kind of git clone of other repos...
I'm looking at 3 approaches:

Search and replace git clone ... in all source files.  This won't work if a git clone command appears directly in .travis.yml.

Add a git shim to PATH.

Set git insteadOf configs!  Local .git/config settings don't seem to affect git clone into a new dir (makes sense), but on Travis we can just config it globally.
POC build: https://travis-ci.org/cben/manageiq-providers-kubernetes/jobs/346289584/config
For a github repo, something like this mostly works:
git config --global --add url.https://github.com/cben/manageiq.insteadOf https://github.com/ManageIQ/manageiq
git config --global --add url.https://github.com/cben/manageiq.insteadOf<EMAIL_ADDRESS>git config --global --add url.https://github.com/cben/manageiq.insteadOf git@github.com:ManageIQ/manageiq

Should also allow for github users/orgs/repos being case insensitive — can't cover all options but just original + all lowercase sounds good enough.
Plus maybe trailing .git permutations.
Plus maybe pushInsteadOf.
Alas, these settings are all for a URL prefix.  If I redirect https://github.com/ManageIQ/manageiq to https://github.com/cben/manageiq, I don't see any way to avoid redirecting https://github.com/ManageIQ/manageiq-providers-scvmm and all longer manageiq-something repo names :-(
(Well, the specific manageiq script clones https://github.com/ManageIQ/manageiq.git, if I require trailing .git I could avoid matching longer repo names, but not everyone uses trailing .git)

Unsolved corners:

[ ] handle git fetch (hard: how to override which branch will later be checked out)
[ ] handle git remote (also hard)
[ ] use existing directory (by symlink / copy / local clone) — will come handy for #3 and maybe #1.

anyway closing for now, these would be separate issues.


Docs Ingestion page refactor

Refactor ingestion into smaller topics. Clean up some style here and there.
Description
This PR breaks down the ingestion landing page topic into smaller topics. Some benefits include:

Ingestion concepts like the Data Model, Rollup, and Partitioning now have smaller more focused topics.
The Ingestion spec reference stands alone as a reference topic.
Should make it easier to add conceptual or example material for a specific concept.

There may be some trade off in topic maintenance. For example if there's an enhancement to rollup, we may need to edit rollup.md and ingestion-spec.md.
This PR has:

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

@sthetland & @vtlim , PTAL

All of my comments are content related so I delegate to your criteria if you want to address them or not. I am fine with the separation of sections. so LGTM.

This PR got out of sync beyond repair. #11576 carries it. cc: @suneet-s , @sthetland


Inconsistent protobuf versions kclvm->python client

Bug Report
I stumbled upon an inconsistency of protobuf versions used and also pinned/validated:
In the python client protobuf is pinned to >=4.25.3 (https://github.com/kcl-lang/lib/blob/main/python/pyproject.toml#L18)
The python client protobuf itself validates against 5.27.0 (https://github.com/kcl-lang/lib/blob/main/python/kcl_lib/api/spec_pb2.py#L14)
And the most relevant part is, that the kclvm/api implements also a different version. If you take the example Python client example you receive class references, which are not implemented in protobuf >= 5.27.0:
import kcl_lib.api as api

exec_args = api.ExecProgram_Args(k_filename_list=["api/tests/schema.k"])
args = api.GetSchemaTypeMapping_Args(exec_args=exec_args)
api = api.API()
result = api.get_schema_type_mapping(args)

assert result.schema_type_mapping.__module__ == "google._upb._message"
assert result.schema_type_mapping.__class__.__name__ == "MessageMapContainer"

If you try to import that class directly from protobuf you get an import error:
from google._upb._message import MessageMapContainer
*** ImportError: cannot import name 'MessageMapContainer' from 'google._upb._message' (/home/olli/code/bm/integration-config/.devenv/state/venv/lib/python3.12/site-packages/google/_upb/_message.abi3.so)

There is an open issue https://github.com/protocolbuffers/protobuf/issues/16935#issuecomment-2135603608 which describes this.
kcl-lib == 0.10.3

@Peefy FYI: when I generate the python stub for https://github.com/kcl-lang/lib/blob/main/spec/spec.proto with https://github.com/kcl-lang/rust-protoc-bin-vendored, The generated python file claims to contain protobuf version 4.25.3:
# -*- coding: utf-8 -*-
# Generated by the protocol buffer compiler.  DO NOT EDIT!
# source: spec.proto
# Protobuf Python Version: 4.25.3
"""Generated protocol buffer code."""
from google.protobuf import descriptor as _descriptor
from google.protobuf import descriptor_pool as _descriptor_pool
from google.protobuf import symbol_database as _symbol_database
from google.protobuf.internal import builder as _builder
# @@protoc_insertion_point(imports)

_sym_db = _symbol_database.Default()
# ...

which was also your pinned version before your version bump.
When I use uv pip install protobuf==4.25.3 I can import from google._upb._message import MessageMapContainer and also test if the result.schema_type_mapping is an instance of it:
(Pdb++) root.__class__
<class 'google._upb._message.MessageMapContainer'>
(Pdb++) from google._upb._message import MessageMapContainer
(Pdb++) isinstance(root, MessageMapContainer)
True

...So I think, the protobuf version of _kcl_lib.cpython-312-x86_64-linux-gnu.so is different than the generated python stub and should all be pinned to 4.25.3, since that seems to be the version you use for kclvm. Even though the newer protobuf python versions seem to work, one cannot type check against e.g. MessageMapContainer.


Replace range-parser

The primary issue with this package is how it throws a TS1259 error how it's currently used.
I suggest deprecating it, as it appears to be unmaintained and has no inbuilt type definitions.
Using packages like this seems to go against the "0-legacy" aim of this package.

do you know any good alternative to it?
also how does it throw an error? it's an internal dependency and shouldn't impact the end developer in any way in theory... maybe you have misconfigured typescript

I have Typescript in strict mode, several of my dependencies require it, this is causing the error to be thrown.
As for alternatives, not aware of any sorry.

@sachaw thanks for quick response, I'll try it out myself with a strict mode
the dumbest solution would be depending on @types/, otherwise idk

omitting @types/range-parser throws a typedef not found like error, depending on it emits the aforementioned TS1259


Use Linebuffering for output

The standard is NoBuffering, which makes the output quite slow.

It looks like this depends on where it is run. Also, stdout seems to be fine after a closer look, but we log on stderr, which has NoBuffering.


Tinkerbell skip power action e2e test for a singlenode cluster

Issue #, if available:
Description of changes:
We cannot run skip power action e2e test because nodes timeout waiting for ipxe if we power it on before cluster creation starts. Thus, to test out skip power action, added a single node e2e test to test out functionality.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.15

/approve


Health endpoint

Atmo should expose a health endpoint that can be used to determine the health of Atmo. This can include whether or not a bundle has been successfully loaded and Atmo is available to serve requests.

@zhangwinning sounds great! This will involve adding a handler to Atmo's router (which is generated by the coordinator - see atmo/coordinator/coordinator.go) that returns a 200ok response, indicating to the caller that Atmo is healthy. That handler should be mounted at the /health path.

~Hi @cohix, I see there are rust examples here, but I’m not familiar with rust, are there any js or ts examples?

@zhangwinning Yes! Atmo supports AssemblyScript (very similar to TypeScript), here's an example: https://github.com/suborbital/atmo/blob/main/example-project/as-graphql/src/lib.ts


Readme documentation config issue

On the documentation page (Readme.md) on the sample app, on the section "Configuring the application", a link to a config.json is present where the file is not there.
Upon starting the sample app, the documentation reads that a config.json file can be drug to the simulator screen, but an error in XCode reveals it is looking for it in the sample directory, even if it is dragged from some place like the desktop.

The config.json link has been fixed.

I believe the issue with dragging the config.json onto the simulator screen has been resolved. It looks like there may have been a bug in a previous version of Xcode.


rerender Issue with useStyle and react-native-keyboard-controller Combination

Description
Hi, I've encountered a problem and hope you can help me.
When I use useStyle and react-native-keyboard-controller together, every time I open and close the keyboard, it causes a rerender. But when I use useStyle alone, as long as I add disableAnimatedInsets: true, rerendering doesn't happen.
If I remove useStyle and use StyleSheet.create along with keyboard-controller, rerendering doesn't happen either.
I tested on Android 14
Steps to reproduce

yarn add react-native-keyboard-controller react-native-reanimated
wrap your app with KeyboardProvider component.
Use useStyle in a component.
Open and close the keyboard multiple times.
Observe the component rerendering.

Snack or a link to a repository (optional)
https://github.com/sssajjad007/unistyleIssue
Unistyles version
2.9.2
React Native version
0.75.2
Platforms
Android
Engine
Hermes
Architecture
Paper (old)

I've encountered the same issue on my Android 8.0 device (HUAWEI P10 Lite)
But the behavior is a little bit different on it.
When I wrap the KeyboardProvider, an extra rerender happens only once. Once I remove the KeyboardProvider only one extra rerender happens when the keyboard gets open.
Hope this information helps you too

Hi,
Any chance we'll get this in v2?

Hey, I'm focusing now on 3.x branch.
Nevertheless I promised monthly updates, and for sure I will cook new release this month with support for RN 0.76.
I will then take a look 🙏🏼

I am experiencing the same issue in the new Architecture too


Add rcon client

This adds a minimal rcon client to allow general script usage.
Additionally there is a players-online.sh script to help with automated updates using watchtower.

I really love the idea, the only thing which prevents me from merging it right away is that I don't like adding the rcon code in this repository directly.
Because its starting to add more and more stuff which is not directly related to docker and factory.
@tripplet Where did you got the rcon.c from? did you wrote it yourself?
I was thinking about moving it a dedicated repository and build binaries there, then load the build binary into this image.
So that everyone who wants to use the binary directly can just use it without loading the whole docker image.

@tripplet Where did you got the rcon.c from? did you wrote it yourself?

Yes I wrote it myself for exactly this purpose. It's mostly the default/generic code to open a tcp socket in linux + some very basic RCON.

So that everyone who wants to use the binary directly can just use it without loading the whole docker image.

Yes that would make sense but I someone is searching for a "fully featured" rcon client they are better of with the many other implementations out there.
If you look very closely it even skips freeing the char* password or the result of combine_args().
But as this is freed up anyway by the OS after exit see I see in this case no point for such a simple "one-shot" binary.
It's really written for this exact purpose.
All required variables are even pulled from the factorio images environment variables, there is no way to set a different host, port or password.
It can be compiled with just the following command, the Makefile is just there to make it cleaner:
gcc main.c -o rcon

The result binary is just 34kB with no external dependencies from the ~200 lines of C code.

Because its starting to add more and more stuff which is not directly related to docker and factory.

Yeah I can understand that, my argument would be to provide a working RCON implementation out of the box with the factorio image to not burden the user of the docker image to then search for: Which RCON client do I use for basic usage.
Also adding it to the image makes it easily possible to use RCON without even exposing the port.
(This could of course also be achieved with compose file and a sidecar container).

I was thinking about moving it a dedicated repository and build binaries there, then load the build binary into this image.

The problem would be that this then would have to mirror the arm64/amd64 compatibility and all the build complexity.
If the C code is just in this repository I there is the need to change something its a simple change to the C file, rebuild the docker image => done.
I think using the multi-stage build in the Dockerfile even avoids complexity because the effect on the result container is only the addition of a single 34kB binary.
I hope I have given some good points for your concern to add this complexity but I can of course understand your approach of keeping this repository minimal.

How about adding LABELs for watchtower using players-online.sh in the Dockerfile or mentioning them in the README?
like LABEL com.centurylinklabs.watchtower.lifecycle.pre-check="/players-online.sh"

How about adding LABELs for watchtower using players-online.sh in the Dockerfile or mentioning them in the README? like LABEL com.centurylinklabs.watchtower.lifecycle.pre-check="/players-online.sh"

Hmm good question, the other option would be to suggestion it in the example compose file and mentioned it in the README rather than in the Dockerfile because I think it's not possible to remove or overwrite a label which is set directly on the container.
(I haven't tested that but the internet seems to suggest that it is no possible to overwrite a label but that's from 2019 so it might no longer be the case)
So it adding it to the Dockerfile would prevent a user from just going yolo I always want the latest container don't care if people are currently playing 😄
Here is for example my current setup extended by the new pre-check. (Not tested yet).
Also it might be better to use pre-update to have watchtower check for update also if players are online but not do the update?
services:
  factorio:
    container_name: factorio
    image: factoriotools/factorio:stable
    restart: unless-stopped
    ports:
      - "34197:34197/udp"
      - "27015:27015/tcp"
    volumes:
      - ./data:/factorio
    environment:
      - CONSOLE_LOG_LOCATION=/factorio/log
      - UPDATE_MODS_ON_START=true
    labels:
      # Allow autoupdate from watchtower only if no players are online
      - com.centurylinklabs.watchtower.enable=true
      - com.centurylinklabs.watchtower.scope=factorio
      - com.centurylinklabs.watchtower.lifecycle.pre-check="/players-online.sh"

  watchtower:
    container_name: watchtower_factorio
    image: containrrr/watchtower
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      # Only update containers which have the option 'watchtower.enable=true' set
      - WATCHTOWER_TIMEOUT=30s
      - WATCHTOWER_LABEL_ENABLE=true
      - WATCHTOWER_POLL_INTERVAL=3600
      - WATCHTOWER_LIFECYCLE_HOOKS=true
    labels:
      - com.centurylinklabs.watchtower.scope=factorio
    env_file:
      # Notification on container update
      # see: https://containrrr.dev/watchtower/notifications/ and https://containrrr.dev/shoutrrr
      - path: ./watchtower_notification.env
        required: false

@tripplet How about adding a docker-compose.yml to the root folder of the respository with watchtower and the labels added but commented out?
So everyone can run the default image and add the version update check if they want to.
This would make a good solution for everyone i guess.
And the docker-compose.yml in the docker folder is for building the image as all other files are too.

while this looks promising, just not for me though. :)
i just want to drop that link:
https://github.com/nekomeowww/factorio-rcon-api

How about adding a docker-compose.yml to the root folder of the respository with watchtower and the labels added but commented out?

Good idea I just pushed add an example file.

this looks promising, just not for me though. :)
i just want to drop that link:...

Ah very cool project thanks for that Im might use that in the future.
Some other off topic:
I also have another project which is not fully ready for release (still some bugs to solve).
It's another side-car container which just watches the log file for login/logouts and is able to send notifications out via Telegram.
I found this helpful for a server used by a small number of friends as a low effort way to play together.
The idea is that you don't have to write in a group every time to say: I want to play does someone want to join?
All involved just receive an automatic notification when someone else joins the server and can decide if they want to join or ignore it.

Just one more, and i think we are ready to go.

Awesome, thanks for merging 😃


[Codegen][GPU] Add pattern to drop lead unit dims of multi_mma ops

Dropping leading unit dims is a useful step that simplifies the process
of lowering to intrinsics by removing the outer iteration space. The
typical lowering flow is to unroll the outer dims to 1 and then apply
this pattern to drop the unit outer dims.
Depends on #17454

Review only the second commit here, the first is from #17454


remove cache logging, add sslproxy_cert_adapt, for generated cert val…

…idity

Some issue with the github action, we can probably do a similar fix as https://github.com/ray-project/ray/issues/7339#issuecomment-663521831, but not sure if that's ideal
@scottrich how did you get this to work before?

This worked fine previously.  Will take a look this weekend.  Maybe a Docker update?

Just for completeness, the problem was that this was the first time we had a PR from a fork.  Turns out that the normal pull_request action does not get access to secrets, but there is a new pull_request_target event that does.  I updated the pipeline to use that, and it seems to be building correctly.  Details on the new feature here: https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/


How to become multiple intelligent agents？

Hello, I really like your work！I have encountered some questions and would like to ask you.
Recently, I hope to transform one intelligent agent into multiple intelligent agents.
I hope these multiple agents adopt the same reinforcement learning strategy and set sim. predict_ method='Inferred'.
I would like to know which code needs to be modified?
Thank you.

Thank you for your kind words! Do you mean to set multiple RL robots just in testing, or in training as well?

I want to set up multiple robots in training.
Thank you!

See https://github.com/Shuijing725/CrowdNav_DSRNN/issues/25 for general comments and https://github.com/Shuijing725/CrowdNav_DSRNN/issues/22 for how to change the gym environments.


Add flexmock, sqlalchemy-utils, pgpy, and py-gfm

Motivation for this change
Trying to build core.sr.ht for NixOS and running into missing packages, figured I would add them upstream. I tested each one with nix-build -A pythonPackages.<pkgname> to make sure they built.
Things done

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

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

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

Lancelot SIX<EMAIL_ADDRESS>writes:

lsix requested changes on this pull request.
Hi,
Thanks for the PR.
Could you add meta attributes for flexmock, PGPy and py-gfm ?

Okay, I added the meta attributes, and added one more package,
'sshpubkeys'. Let me know if you need any more changes :)

worldofpeace<EMAIL_ADDRESS>writes:

meta = with lib; {
homepage = https://github.com/zopieux/py-gfm;
description = "This is an implementation of GitHub-Flavored Markdown written as an extension to the Python Markdown library. It aims for maximal compatibility with GitHub's rendering.";

This description is too long.

Fixed in 9e0430cb919

Robert Schütz<EMAIL_ADDRESS>writes:

dotlambda requested changes on this pull request.
The requested changes should be done for the packages I didn't comment on as well.

Okay, I think I covered all of them. They all have meta, metaintainers, etc.

You might want to read through https://nixos.org/nixpkgs/manual/#python again.

Looking at the contributing guidelines, this is what I see:

Python libraries are called from python-packages.nix and packaged with
buildPythonPackage. The expression of a library should be in
pkgs/development/python-modules//default.nix. Libraries in
pkgs/top-level/python-packages.nix are sorted quasi-alphabetically to
avoid merge conflicts.

Check.

Python applications live outside of python-packages.nix and are packaged
with buildPythonApplication.

None of these are apps.

Make sure libraries build for all Python interpreters.

I think they all succeed. I'll look into testing this thoroughly over
the weekend or next week.

By default we enable tests. Make sure the tests are found and, in the
case of libraries, are passing for all interpreters. If certain tests
fail they can be disabled individually. Try to avoid disabling the tests
altogether. In any case, when you disable tests, leave a comment
explaining why.

Only one package failed to find the tests, and I added a comment
explaining that.

Commit names of Python libraries should reflect that they are Python
libraries, so write for example pythonPackages.numpy: 1.11 -> 1.12.

Check.

Attribute names in python-packages.nix should be normalized according to
PEP 0503. This means that characters should be converted to lowercase
and . and _ should be replaced by a single - (foo-bar-baz instead of
Foo__Bar.baz )

Check.
Okay, anything else I can do?

@dotlambda Anything I can do to help move this along?

@bsima
Could you also fixup these additional commits with an interactive rebase?
It would make reviewing commit by commit possible.

worldofpeace<EMAIL_ADDRESS>writes:

@bsima
Could you also fixup these additional commits with an interactive rebase?
It would make reviewing commit by commit possible.

Yes, I rebased to make things more clear, and updated the meta
info. Thanks for the feedback, and let me know if there is anything else
I can do.


Add ability to filter by status of the projects

Add ability to filter by status of the projects

Add a tabbed view to filter projects by All/Unhealthy
All shows a full list of projects
Unhealthy shows list of failed projects only

Example:

Can I take a stab at this?

Yes @macanrox, go for it.

@macanrox How you getting on with this?

@haroon-sheikh Sorry for the lack of updates. It's been busy on my end.
Check out this update and let me know if there's anything that could be improved on.

So far there's the tabbed view buttons and spaghetti/skeleton code for the Filter component. I'll have a PR either later tonight or tomorrow.

Hey @macanrox, thats looking really good. Exactly, what we're looking for.


Ui improvement

Add hover effect to buttons and changing the color of icons

Hey! Can I work on this issue for hacktoberfest ?


Spellcheck blinking

Hi! A few months ago, an update came out in slate-react that solved the problem of a blinking spellcheck when typing. Are there any plans to move this fix into your project, or perhaps some advice on how I could fix this?

@ilya2204 Thanks for your feedback, I have understood the cause of this problem, I will give ideas as soon as possible.

Hi @ilya2204
I solved this problem by referring to the idea of slate-react, but this solution is a bit sloppy, and the current solution has some problems. The trigger timing of the ngModelChange event has changed. The DOM has been updated when ngModelChange was executed in the past, but now it depends on The browser's default behavior (the default behavior of the beforeinput event is no longer blocked), so the inserted text has not been updated when ngModelChange is executed, this is a difference point, if this is acceptable, you can use this scheme for now. I'm not ready to merge it into the master branch yet, may have to think about it again.
https://github.com/worktile/slate-angular/tree/spellcheck-blinking

Hi @pubuzhixing8
Thanks for solving the problem. I tested and in English spellchecking really doesn't blink anymore. The only thing I found a bug with the fact that some events (moving with the arrows / cutting text through the ctrl+x and maybe others) do not cause a redraw, but this was fixed by adding the line IS_NATIVE_TYPING.set(editor, false) to the beginning of the onDOMKeydown method. Perhaps there are some other handlers to which this fix should be added, but I did not find any other problems.

Hi @ilya2204
I haven't reproduced the problem you mentioned (moving with the arrows / cutting text through the ctrl+x ), but the current way of doing it may indeed be a problem, and the state maintained by IS_NATIVE_TYPING may become dirty. I have submitted a new commit to correct the native typing state, please help to confirm if it can solve your problem.
If it still doesn't match your question, a more detailed exception path can be provided.
https://github.com/worktile/slate-angular/pull/197/files

@pubuzhixing8
Arrow movement really worked. However, there is a bug with the insertion of '\n'. Unfortunately, I didn’t manage to create codesandbox, so in pull request I added an example of inserting '\n' by pressing Enter + Shift into richtext.component.ts, after which strange behavior occurs when typing, you can check (I tested in chrome and firefox)
https://github.com/worktile/slate-angular/pull/198

@ilya2204
Amazing, I found the cause of the problem, a specific rendering template is used when the text ends with \n , so the browser's default rendering behavior cannot be used.

So I added an extra condition to the spellcheck.

@ilya2204
Amazing, I found the cause of the problem, a specific rendering template is used when the text ends with \n , so the browser's default rendering behavior cannot be used.

So I added an extra condition to the spellcheck.

@pubuzhixing8
Thanks a lot. Now everything seems to be working as it should.

And maybe add more complex character input checks.
Instead of /[a-z ]/i.test(event.data) something like event.data.toUpperCase() != event.data.toLowerCase() which works in most languages. Or perhaps add the ability to pass a validation function to the editor's input.

Good suggestion, I am also considering removing the character check, all English input will follow the default behavior of the browser.

And maybe add more complex character input checks. Instead of /[a-z ]/i.test(event.data) something like event.data.toUpperCase() != event.data.toLowerCase() which works in most languages. Or perhaps add the ability to pass a validation function to the editor's input.

Good suggestion, I am also considering removing the character check, all English input will follow the default behavior of the browser.

Hi @pubuzhixing8
Unfortunately I found another bug when after changing the cursor position you enter a character and then delete it (for example, through backspace) strange things happen
https://user-images.githubusercontent.com/52297646/168486909-56a21972-3b24-4ba1-9d6c-989d9f42910d.mp4


adding files and folders

Implemented issue no. 11: Adding Folders and Files
I have added all the folders and files with basic component for the features according to their names in app folder. eg. app/UserProfiles/page.js
Please let me know if it is according to your requirements

Implements #11

adding files and folders -- >
 app/ContentSharing/page.js
 app/Discussions/page.js
 app/InquireAboutCrops/page.js
 app/LearningAndResources/page.js
 app/PersonalAiSupportBot/page.js
 app/SeasonDashboard/page.js
 app/UserProfiles/page.js
 app/WeatherDashboard/page.js

Resolve #11


How to get the dialog reference

Is it possible to get the modal reference from the component where the createConfirmDialog function is used?
something like this:

//CustomDialog.vue

<template>
    // i need this dialog reference
    <Dialog >
</template>

//Any component that use confirmDialog, e.g: App.vue
<template>
  // some code here...
</template>

<script setup>
import CustomDialog from './components/SimpleDialog.vue'
import { createConfirmDialog } from 'vuejs-confirm-dialog'
import { ref } from 'vue'

const dialogReference = ref()

const { reveal, onConfirm } = createConfirmDialog(CustomDialog, { question: 'Are you sure?', ref:dialogReference})

onConfirm(() => {
  // some code...
})

It has occurred to me to do it with props but I don't know if it's possible.
In summary: for example in App.vue I need to save the dialog reference in dialogReference.

Of course, you can pass data from the modal to the component where you call it. Check https://vcd-docs.netlify.app/guide/passing-props-and-data#passing-data

It will not work, even if you pass the ref. Because you need to ignore click outside if the second dialog is open.
This is the solution:
// FirstModal.vue
const { isRevealed } = createConfirmDialog(CustomDialog)

onClickOutside(target, () => {
  if(!isRevealed.value) {
     emit('cancel')
  }
})

I was thinking of doing it with the ref so that from my component hierarchy I can access that dialog with $refs.myConfirmDialog, and so it doesn't matter how nested the component that uses the confirmation box is.
If I do it as you say, it involves me doing emits and watchers to move 'isReveleaded' to its parents.
I'm currently using 'ignoreRefs' with some components with no problem, why won't using the reference in the confirmation box work?

Basicamente tengo algo parecido a esto:
// App.vue
<BaseModal :isOpen=" wtgTypeList.isOpen " :onClose=" wtgTypeList.onClose " :ignore-el-refs=" [wtgTypeFormModal] ">
    <BaseModalHeader>WTG Type List</BaseModalHeader>
    <BaseModalCloseButton />
    <BaseModalBody>
        <ItemList></ItemList>
    </BaseModalBody>
</BaseModal>

//ItemList.vue

import { confirm } from '@/composables/useConfirm';

<Table>
    <TableHeadings>
        <TableItemHeading>Name</TableItemHeading>
    <TableList v-for="item in itemList" :key="item.id">
        <TableItemList>
           {{ item.name }}
        </TableItemList>
        <TableItemList tools>
            <Button @click="async () => {
                await confirm({
                    type: 'ELIMINATION',
                    onConfirm: async () => await removeItem(item.id),
                })
            }" />
        </TableItemList>
    </TableList>
</Table>

If I have to get isRevealed in ItemList, I have to watch it with an emit every time its state changes, then App would have to read that emit and save it to a local ref again.
So I wanted to just get the reference from the confirm modal and pass it to ignore-el-refs

Still, ignoring refs will not work, because you're clicking outside of these refs. But you can still use my solution. Just call useConfirm in App.vue, and pass confirm to ItemList.vue as emit

Also, you should change your confirm function to use it like this:
import { useConfirm } from '@/composables/useConfirm';

const { confirm, isRevealed } = useConfirm()
``

ok, right now I do that and it works for me, if there is no other solution then I will continue using that way, thank you!


Oscillate (swing) should not be added to accessory if not supported

My Mitsubishi air conditioning does not have the swing function, so in that case, and for the HeaterCooler accessory, that property should not be added to the device.
"Device"."SwingFunction": false,

fixed in 0.2.6

Thanks!