Better exception message when throwing MalformedResponse

It is very hard to find where is the malformed part of a response when dealing with a big JSON.
Would be nice if a more specific message was shown, like "Could not find "key" in the JSON".
And also, I couldn't find a way to get the raw text response and print it to help me debug.
Thanks for the library. I really wish I could be of more help, but I'm learning Swift.

The malformed error means different things depending on which Deserializer you are using (the old JSON or the Swift4 Codable way for JSON).
Can you post some sample code?

As for getting the raw Data object:
do {
    let response = try result.value()
    // ...
} catch NetworkingError.malformedResponse(let data) {
    print("Error performing GET, malformed data response: \(data!)")
}

The data variable will be of type Data? which represents the raw bytes received. In a future RestEssentials release, it will not be an optional, but just a Data object. For now, you can safely force unwrap it (only for malformedResponse errors).  It is not safe to force unwrap the data object for ANY other type of error.

First of all, thanks for such a quick answer!
Now at least I can actually see the received JSON and send reports of failure to the API I'm using.
Thanks a lot!
About the Deserializer, I'm using only Swift 4's Codable for now. Some example:
    //Usage in my ViewController
    ServerClient.fetchStartupData(){ startupdata, httpResponse in
            if let data = startupdata{
                //Handle received data
            }else{
                print("Nope, Connection Error")
            }
        }

    //Expected response
    public struct StartupDataResult: Codable {
        public let name: String
        public let photo: String
        public let active_orders: [ActiveOrder]
        public let notifications: [Notification]?
    }

    //Global function that can be accessed in my whole project
    public static func fetchStartupData(callback: @escaping (StartupDataResult?, HTTPURLResponse?) -> ()) {
        let name = "buscaDadosDeStartup"
        let dados = Server.getBasicInfo() //Codable with API Token and more basic info, nothing much
        Server.client(callName: name).post(dados, responseType: StartupDataResult.self) { result, httpResponse in
            handleDefaultConnection(callback, result, httpResponse)
        }
    }

    //Some connections only require "Data or No Data", so I created this handler
    static func handleDefaultConnection<T>(_ callback: (T?, HTTPURLResponse?) -> (), _ result: Result<T>, _ response: HTTPURLResponse?) {
        do {
            print("Response = \(response)")
            let response = try result.value()
            callback(response, response)
        } catch {
            print("Error receiving fetchStartupData = \(error)") //I will modify this go get the raw data now
            callback(nil, response)
        }
    }

Probably there is a better way to do what I'm doing, but I'm already very happy for now.
Is there any way to get an exception that indicates what key is missing in the JSON response, or something like that, that narrows my search for API misbehavior?

It should already be logging the error that comes straight from the Swift API.  If you look at the. DecodableDeserializer in Deserializer.swift you can see the error from the native JSONDecoder should be logged out:
print("Error decoding to JSON object \(error.localizedDescription)")

I am not sure how detailed the built-in decoder's errors are, but take a look there (you can breakpoint in there and see if there are different details in the error that isn't being logged out.  If you find something else that I should log out, let me know.

@vitorhugods can this be closed?

@vitorhugods Take a look at the last commit: https://github.com/sean7512/RestEssentials/commit/43b15f21f61fd3db05c912ef7263a4e6daae2b54
I changed the Deserializers so they no longer swallow error, but instead pass them back up.  Now when you try to get the result.value() you will get the original error back in the failure case.  So you should now be getting the JSONDecoder errors that you linked to.  This will be in the next release (4.0.2) and I will release it once you confirm it looks good.
Thanks!

Seems really good to me. Really liked it. =)
Also, I've been thinking here about debugging and reports.
In Android I normally use Firebase/Crashlytics to send reports of connection, failures or edge-case.
It would be very nice to access the raw response data even successful cases as well.
Is this an issue-material?

Ok, I'll start getting 4.0.2 released soon.
As for Firebase/Crashyltics, that would be integrated at the app level, not in the library.
Thanks for the suggestion on the error improvements!

I'm not saying it should not be in the app level. But so far, the way to get the raw response body in order to log or report, without deserializing is when an serializing error occurs, as seen here. Or is there any other way to get that?

4.0.2 has been released and contains better error handling for Deserializers and it also removes the optional on the Data parameter for a malformedResponse error.  I have also updated the Readme to include information on Error Handling.
As of now, there is no way to get the raw data back in a success case.  There are some memory constraints with doing this. Imagine using an Image Deserializer on very large raw images, you would be using twice as much memory, which is probably not desirable.  Or worse yet, maybe you used a Movie Deserializer.
If you use the built-in JSON type (instead of Codable), we do keep the raw response (it isn't accessible right now, it is private), but if there was a strong argument for it, I could expose it.  The issue with exposing it is mutability and how that may break the json parsing.  I guess it could be immutable getter only.  Either way, feels awkward for only 1 of the deserializers to provide that functionality.

Understood. I've never though of images and videos.
I've worked in projects that some operations were really sensitive, complexes and cost big money. To the if any error was reported customer-wise, admins should be able to look logs back and see exactly what the app requested, and what it received from the API, so It would be fixed ASAP.
It never came to the point that a costumer reported something, mostly because even when in beta testing, these reports helped to correct mistakes.

@vitorhugods going to close now that the 4.0.2 release include much better error handling.  Thanks a ton for bringing the issue to my attention.


Fix MSRV issue on Windows

Fixes #2436

@bors try

@bors try

:hourglass: Trying commit ba6e50a9e93e9f16ab8b159e86332701a7e422b0 with merge 46ff687ec0e5b6c0aa32763c62c3e133ea721234...

@bors try

@bors r+

:pushpin: Commit 6ea2c7100f20f2f6a0c8079044585c3fb8ee51f3 has been approved by JohnTitor

:hourglass: Testing commit 6ea2c7100f20f2f6a0c8079044585c3fb8ee51f3 with merge c768286cfed305e68103886f57fc2127b6f453b8...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing c768286cfed305e68103886f57fc2127b6f453b8 to master...


Paulyuk/hello world refactor

Description
This addresses the proposal to refactor ./hello-world quickstart into node and python subfolders.  This is closer to what other quickstarts do, to what real life code looks like, and it enables downstream Devops benefits like having seperate Dockerfiles or builds.
The following changes were made:

refactored all Node.js code and assets for nodeapp into ./hello-world/node
refactored all Python code and assets for pythonapp into ./hello-world/python
added working Dockerfile for each language/application
updated makefile to  enable make build make all and make build_containers
enabled tye run to easily start both services
updated README to match new paths and optional tye run step at the very end.

Issue reference
Fixes #477
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary

I do not believe the goals of this PR are correct

Dapr does not requires docker to host the applications and this implies it requires this. It is important the developer understand that Dapr runs executables, not code in containers. This quickstart should not have docker file added, since this is about using Dapr to launch exes.
The Hello-World K8s example (which has to have containers) is where the docker files for these apps are including these instructions https://github.com/dapr/quickstarts/tree/master/hello-kubernetes#deploying-your-code
Even if we were to add dockerfiles, these files are different from the  Hello-World K8s example, and should be the same.
Adding Tye to this quickstart which is a .NET/MS centric prototype tool confuses people and should be separated out. This is best placed as a documentation example in the IDE section of the docs and is the best place for people to learn about Tye, not from a quickstart. For example I would not include Bridge for K8s into the Hello-World K8s example and the VS Code extension in not include currently, which is also in preview. (and specifically the Tye build make file instructions target Linux and instructions on using Windows machines should be included, presumably saying this requires WSL2)

Dapr does not requires docker to host the applications and this implies it requires this. It is important the developer understand that Dapr runs executables, not code in containers. This quickstart should not have docker file added, since this is about using Dapr to launch exes.
The Hello-World K8s example (which has to have containers) is where the docker files for these apps are including these instructions https://github.com/dapr/quickstarts/tree/master/hello-kubernetes#deploying-your-code
Even if we were to add dockerfiles, these files are different from the  Hello-World K8s example, and should be the same.
Adding Tye to this quickstart should be separated out. This is best placed as a documentation example in the IDE section of the docs and is the best place for people to learn about Tye, not from a quickstart. For example I would not include Bridge for K8s into the Hello-World K8s example and the VS Code extension in not include currently, which is also in preview. (and specifically the Tye build make file instructions target Linux and instructions on using Windows machines should be included, presumably saying this requires WSL2)

Hey @msfussell, thank you for the feedback.  Ok we can keep this clean and focused on inner loop, and break build and deploy into separate steps.  Tye is an open source tool that is really handy for all languages we use in Dapr, but let's also keep that separate.  I haven't written new docs for these, so we'll leave that to a future PR.
Now this PR is about:

refactored nodeapp and pythonapp code and dependencies into their own folders
updated readme with paths.

That's it. Better?

I noticed that you've moved both hello-world/sample.http and hello-world/sample.json into the hello-world/python directory. While that makes sense for the structure of the source code since the python app initiates the orders, I actually think these sample "orders" should be kept in the hello-world/node directory instead. Since the user of this quickstart will use the sample.* files to test their node deployment, we should house these files in the node directory for easier access immediately following their node dapr app deployment. Thoughts?

Hi Will! thank you for the review and feedback.  Good catch.
How about this:
sample.http moves to \node folder because it's the documented way to test the nodeapp service from any REST client, curl etc. Note that a sample data is self-contained in this file so you don't need second sample.json.
sample.json is really a hard dependency of pythonapp client. I'm a bit of a stickler about data being co-located with its microservice, and not leaking out. how about we keep this one in \pythonapp?

I noticed that you've moved both hello-world/sample.http and hello-world/sample.json into the hello-world/python directory. While that makes sense for the structure of the source code since the python app initiates the orders, I actually think these sample "orders" should be kept in the hello-world/node directory instead. Since the user of this quickstart will use the sample.* files to test their node deployment, we should house these files in the node directory for easier access immediately following their node dapr app deployment. Thoughts?

Hi Will! thank you for the review and feedback. Good catch. It's interesting that sample data is a hard requirement for pythonapp, but it's also a soft dependency of nodeapp since we guide folks to call the invoke CLI command with it. Let's call on some creativity then..
How about this:
sample.http MOVES to \node folder because it's the documented way to test the nodeapp service from any REST client, curl etc. Note that a sample data is self-contained in this file so you don't need second sample.json.
sample.json is COPIED (yes there will be two copies) since is really a hard dependency of pythonapp client, but also a soft dependency of the doc for nodeapp. I'm a bit of a stickler about data being co-located with its microservice, and not leaking out. The only other alternative I can see is moving sample.json and sample.http up to the root of hello-world, and change docs to say ../samples.json as path. That seems less ideal to me.

@paulyuk - I agree with this approach. While having two copies of sample.json is redundant, I think it's necessary for the sake of convenience in the quickstart steps (i.e. no need to cd back and forth between /node and /python). Plus, I don't expect the data model to be changed much for these simple apps, so I think this is acceptable.

Did you intend to go to the hello-world/K8s quickstart and "improve" the container Dockerfile with your suggestions? Also these folder changes are simply to make it consistent with the K8s/Hello World example I presume?

@msfussell Yes I plan to do that k8s dockerfile work separately in another PR focused on deployment options including dockerized ones.  These folder changes simply add consistency, but also mirror what a node or python developer is used to, as well as what you'd want to see out of tiny autonomous microservices.


Standalone map: Add marker specific legend

The standalone map currently has a single legend component, which works will with donut and barplot markers. But, once we add bubble markers, we will need to introduce marker-specific legends.

to add a bit more detail to this, bubbles will have two parts to their legend. the first will indicate size and likely be a set of concentric circles, the second will indicate color and at least for whats been discussed so far will require a gradient legend.

see https://github.com/VEuPathDB/web-monorepo/issues/249

I propose we introduce MapTypePlugin, which will include a component to render the configuration panel, and a component to render a "map layer" (which will include a legend, markers, floating vizs, etc).
This approach will make it possible to have non-marker map types (such as animation, time-based view, etc).
The map itself would continue to be rendered independently.
@bobular I would love you feedback on this proposal.

I'm going to rename this issue and move it back to "TODO". I also don't think it's needed for NIAID QO

Just thinking if we want to be really flexible and future proof, then rendering the base map itself might be the purview of the 'map type'.

Just thinking if we want to be really flexible and future proof, then rendering the base map itself might be the purview of the 'map type'.

I had a similar thought. I'm not opposed to that. Can you think of use cases? Maybe if a map type wants to use a different base layer?

I was thinking of choropleth and cartograms, etc

Cool, makes sense. I'm going to leave this here for future reference: https://leafletjs.com/examples/choropleth/

Even though this isn't urgent any more I like the idea of future proofing. Dave's proposal looks good!
Choropleths still go on top of a regular map, so I don't think the base layers need to be part of the plugin scheme.

Closed by #399


Leave non-dated issues for last when sorting by by nearest due date

"Sort by nearest due date" should leave the ones without due date for last. For example:
Currently:
#_2324          (no due date)
#_2626          (no due date)
#_1234    Oct 3 (past due)
#_1432    Nov 7 (due Today)
#_5232    Nov 8 (due Tomorrow)

Expected:
#_1234    Oct 3 (past due)
#_1432    Nov 7 (due Today)
#_5232    Nov 8 (due Tomorrow)
#_2324          (no due date)
#_2626          (no due date)

This PR fixes that.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c15d371). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #8871   +/-   ##
=========================================
  Coverage          ?   41.21%
=========================================
  Files             ?      544
  Lines             ?    70096
  Branches          ?        0
=========================================
  Hits              ?    28890
  Misses            ?    37505
  Partials          ?     3701

Impacted Files
Coverage Δ

models/issue.go
51.2% <0%> (ø)

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 c15d371...ec865ba. Read the comment docs.


[DO NOT MERGE] Testing CI [skip ci]

DO NOT MERGE
This is a test PR to trigger CI

rerun tests

rerun tests


many to many?

This is a great tool for learning data modelling, thanks!
BUT why is there no many to many relationship? And what is a zero to one relationship?

This tool is a physical database modeling tool.
N:M relationships are modeled as follows.

The relationship names like "zero one" refer to the states of the PK and the FK it's pointing to, not the PK state itself.

Thanks so much! This tool forced me to figure out good practices.


chore(main): release 0.19.0

:robot: I have created a release beep boop
0.19.0 (2023-03-04)
Features

. (e38cc1c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/samuele-cozzi/obsidian-marp-slides/releases/tag/v0.19.0 :sunflower:


I'm Japanese! Atom-beautify not woking!

First of all, I'm Japanese and my English is not really good.
Description
Atom beatify is working with no errors and
no results.
l installed "Atom beatify" and "php-cs-fixer" in Atom.
And I also instaled "php-cs-fixer"
at
https://github.com/FriendsOfPHP/PHP-CS-Fixer#installation
which is in my pc.
The file name of it is "php-cs-fixer-v2.phar" which of course is
in my pc(c:¥xampp¥php¥php-cs-fixer-v2.phar)
And in Atom
my path is "c:¥xampp¥php¥php-cs-fixer-v2.phar".(Excuatbles▶PHP-CS-Fixer)
the other path is "c:¥xampp¥php.exe".
(Excuatbles▶PHP)
l don't why it's not working.
l geuss setting is no problem becuse
"linter-php" is working.

This is my fist time doing this. This is all I can do now.
I aiso don't know how to post pictures and debug from Atom.
I've been so in trouble.
Please help me!

From the given paths I asume you are working on a windows pc.
Here are some things you can check:

have you restartet Atom after the settings where made?
What is the extension of the file you are trying to beautify? (should be .php)
have you tried the developer tools? Are there any messages if you perform ctrl+alt+b in your file?

You should also give more detail on your setup and on the failing action you are trying to perform.

@YutaNakai can you run the debug command?  There is likely an error somewhere, it's just not shown in the UI.  Open the file you are trying to format and go to Packages -> Atom Beautify -> Debug.  Follow the prompts and when it opens a tab with text, copy and paste that text into a GitHub gist and make a comment here with the link to the gist.

Thank you! I really appreciate responding.
Yes l did run debug.
But l don't know how to upload here.
@szeck87
How can l put pictures here?
@JAFteach
Yeas l restarted.
The file name is "bbs.php".
You mean run debug?

@YutaNakai Don't take a picture of it, copy and paste the text and create a gist (https://gist.github.com/) and comment here with a link to the gist.

Thank you!
Please forgive me for not being used to this.
l've been the link before and pasted.
How about after that?
Add file button?

No, Create public gist.

l'm sorry l'm late.
I hope I did.
https://gist.github.com/YutaNakai/d17fa7e3d81b7eea52a0e36f4070f442#file-atom

And I also know how I can upload pictures.
l think it's very helping

It looks like it's running properly, but there isn't anything for it to change.  Try creating a .php_cs.dist in the same directory with contents something like:
<?php

return PhpCsFixer\Config::create()
    ->setRules([
        'indentation_type' => true
    ])
    ->setIndent("\t")
    ->setFinder(
        PhpCsFixer\Finder::create()
        ->exclude('vendor')
        ->in(__DIR__)
    )
;

Thank you.
Do you mean l make file?
l'm sorry l'm not really good at PC.

Yes, create/make a new file.

Thank you.
But l really make sure l'm correct.
Can l ask you again how l put pictures here.
l'm so sorry. l really want you to help me out here.

l'm sorry.
Could you please help me?

@YutaNakai you can simply drag & drop pictures in the box you write your comments. You can also copy & paste them from your clipboard.
How to attach files is also described under the dashed line in the commentbox.

Okay. Thank you.
@szeck87 said this
It looks like it's running properly, but there isn't anything for it to change. Try creating a .php_cs.dist in the same directory with contents something like:
And it turns out I have to make a file.
l don't know what is the next.


Create warning when time stamp is missing leading zero

When ActivityStartTime, ActivityEndTime, or AnalysisStartTime are missing a leading zero in the 00:00:00 format, warning message is not being generated.

I wrote a unit test for this, it passes as expected. We can retest on the next schema deployment.


Allow use of new behaviour for --no-default-features and --features without changing resolver

Problem
I would like the command line options --no-default-features and --features to apply to all members of the workspace. Currently, this only appears to work for resolver = "2". However, I am unable to change the resolver due to MSRV restrictions.
This problem is occurring for the object crate. The object crate is the root of the workspace, and object-examples is another member. With resolver = "2" I get:
$ cargo tree --no-default-features --features read_core -e features -i object-examples
object-examples v0.0.0 (/home/philipc/code/rust/object/crates/examples)

and with resolver = "1" I get:
$ cargo tree --no-default-features --features read_core -e features -i object-examples
object-examples v0.0.0 (/home/philipc/code/rust/object/crates/examples)
├── object-examples feature "default" (command-line)
└── object-examples feature "read"
    └── object-examples feature "default" (command-line)

As shown, --no-default-features is not applied to object-examples.
Alternatively, if I change the default features of object_examples to [], then I would like the following to also enable object-examples/read but it does not:
$ cargo tree --features read -e features -i object-examples
object-examples v0.0.0 (/home/philipc/code/rust/object/crates/examples)
└── object-examples feature "default" (command-line)

Proposed Solution
I don't have any great ideas for how this might be solved. The only possibility I can think of is adding a new workspace setting in Cargo.toml, but I expect that's not very palatable, and this is a problem that will eventually disappear when the MSRV is increased.
Notes
No response

Yea, I don't think we are likely to add another flag to opt-in to this behavior.  Hopefully the wait to make 1.51 your minimum version won't be too bothersome.


ra-multiselect form boxes always empty on mobile safari

i.e. on iPad. Work fine on desktop safari and chrome.

It is counter-intuitive, yet 100% functional :D
You need to click left form (populate it first with a search if needed), select the options you want to add, click the right arrow between two selects to push options to the right select and you are down.
Pro-tip, you can even sort right options :D
I can't take your patch, because it won't work with AJAX populating the form.


Base version for applying change

Hello Roman, this is less an issue but more a question.

Do you create and update something like DATABASECHANGELOG collection with already applied patches to prevent failures or damages by accidentially repeating of not idempotent changesets?
Is it possible to declare the base state (version/timestamp from the above DATABASECHANGELOG), for what a patch/changeset may be applied?

Regards, Gena

Hi Gena,
Sorry for delay, I'm on vacations right now :)

Yes, correct - there is a collection named mongol_migrations_3710611845fe4161b74d2ec5eafe9124. It contains list of changes applied + hash of that change.
This tool relies on a sequence of changes, declared in changelog-file - if there is a change (migration) inserted in the middle between already applied migration, it will fail with corresponding message (format: Applied changeSet-set with ID %v after not-applied changes).
So, directly answering your question - no, right now here is no ability to reference/declare a dependency on another migration or make some kind of tag/versioning.
Actually, it seems to be a good idea for, at least, removing "old" migrations, ie flattening list of migrations + it will add an extra check for DB integrity before applying migrations.


genericize warning text for 'inferredNotNull'

I'm not sure if this warning is just an experiment or will stay (there was no issue?), but, the warning text contains "Java":

not null type inferred from Java reference (explicitly specify the type)

and the warning appears when using interop in the Dart backend as well.
I suppose I could s/Java/Dart in the Dart compiler as a post processing step, but a solution that is less of a hack would be nice if possible.

I did not realize you had uncheckedNulls in the Dart model loader.

Fixed.

Thanks!


[reggen] Prefer explicit utf-8 encoding

This fixes the chip level nightly breakage.
Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

Does it mean that one of the Hjson files had non-ascii content?

Yep:
$ git ls-files '*.hjson' | env LC_ALL=C xargs grep -lP '[^\0-\x7f]'
hw/ip/sysrst_ctrl/data/sysrst_ctrl.hjson

This turns out to be some "smart quotes". Fixed with #6349. I'll try to knock together a CI check for this later: I think we've agreed to avoid non-ASCII characters in source code.

Thank @rswarbrick for addressing this.


BIOS Update

Did anyone try updating their bios above version 0075?
Current up to date version is 0081 which has a lot of great fixes, but after 0077 you cannot downgrade to 0075 anymore.
So if anyone on version 0081 or below could comment if you had any issues after upgrading I would much appreciate it.

I’m on 0081 with no issues.
On Aug 3, 2020, 12:18 AM -0500, Dawid Bialek<EMAIL_ADDRESS>wrote:

Did anyone try updating their bios above version 0075?
Current up to date version is 0081 which has a lot of great fixes, but after 0077 you cannot downgrade to 0075 anymore.
So if anyone on version 0081 or below could comment if you had any issues after upgrading I would much appreciate it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@Beajar Thank you!


The track in a jukebox continues to play even though there is technically no music disc in it

Describe the Bug
If a music disk is removed from a jukebox by a Create machine while it is still playing (only possible with Mechanical Arm and Chute, Funnels and Smart chutes are blocked by the jukebox's redstone signal), you can still hear the track. However, the jukebox no longer emits a redstone signal and the jukebox is also empty in Jade.
Reproduction Steps

Put a music disc in a jukebox
Remove the music disk with a chute or mechanical arm.

Expected Result
The song stops as if you were pulling out the Muaic disk by hand.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.1f
Minecraft Version
1.20.1
Other Mods
No response
Additional Context
I took advantage of this and this is what I got. Just put a music disc on the depot and listen to the wonderful music :)
broken_pigstep.zip
There is a schematic in the zip file

update FAPI

Fabric API is already installed (version 0.92.1)

cant reproduce with fapi 0.92.1+1.20.1

I only tested the bug with Create Fabric and Fabric API, Fabric 0.15.10 and it was still there.

Build a tower of chutes and jukeboxes, always alternating. Maybe you can hear several pieces on top of each other.

I have found out something more precise: When a Chute takes an item from a Jukebox, the Music Disk is removed from the Jukebox inventory, but the song is not stopped. A Mechanical Arm stops the song properly. However, there are problems if a second Mechanical wants to pick up the Music Disc from the jukebox at the same time. Then the song is not stopped.
Maybe this is related to game ticks. If the mechanical arm only searches for a target every second tick, maybe the latter bug is also fixed.

This is, again, a fabric API issue. https://github.com/FabricMC/fabric/issues/4220


[FEATURE] - Binary selection for block nodes

Your Info
Superlist
User Behavior
Currently the selection of block nodes (e.g. images or horizontal rules) is implemented as UpstreamDownstreamNodeSelection, which allows to place the selection at one of the ends of the node (upstream or downstream). For block nodes it feels more natural to have binary selection, where the node is either selected or not.
Although BinarySelection and BinaryNodePosition exists in code it is not used anywhere, but it seems like SuperEditor supported binary selection or at least was planned to.

@angelosilvestre why don't you take a stab at integrating binary selection. If you get stuck, let me know.
@miguelcmedeiros can you clarify where you'd like to see this used? Do you expect that all non-text components should be able to understand both UpstreamDownstreamSelections and BinarySelections? Or should there be two sets of components? Or just certain components should be replicated to use BinarySelection?

@matthew-carroll it's difficult to say what would be the approach, since that might bound to the current APIs and by how much of a breaking change this would be.
Probably @angelosilvestre will have some insights about this once he dives into it and figures out what's possible.

@miguelcmedeiros - I'm not sure that he will. As the issue is currently written, we seem to lack both a clear motivating UI/UX, and also any suggestion for what should change.
You've mentioned in the issue that we have a selection type that's not used, and you've mentioned in general that the unused selection type would make more sense when editing with blocks. The first part is definitely true, the second part might be true in some situations, but certainly isn't true in all situations.
So I do think we need a bit more guidance as to what the output from this ticket should be. If Superlist wants/needs binary selection for certain components, which ones are those? And what would be the most convenient change for Superlist? I think those are important guiding answers for @angelosilvestre's investigation.

@miguelcmedeiros can you provide more guidance on this?


Grammar issue with rest parameter of nillable type

Description:

$title
I think this is due to introducing ?. to access optional values of records.
Steps to reproduce:
public function main() {
  foo(1,2,3);
}

function foo(int?... nums) {
    io:println("bar");
}

Error invalid token '?.'
But the following works
public function main() {
  foo(1,2,3);
}

function foo((int?)... nums) {
    io:println("bar");
}

@SupunS can you please have a look?


Steal from crates

So players can spam right click tools in the crates  then they can use the tools but it won’t stay if they try to pick it up inside there inventory.

Sounds like its a client site visual bug unless there is an error in console when it happens. If there is no error then it might be a visual bug so have the user relog when this happens and see if when they rejoin they still have it.

It is gone after a tp or relog or even picking it up, but the problem is, players can ah them and scam other people. Can you add the option so if they click on an item in the gui, it closes it. That would fix the issue.


Add perfectly_balance option to C++ interface for kaffpa

Proposal to implement https://github.com/KaHIP/KaHIP/pull/60 as new interface function.

[ ] Test

Thanks!


Cake Pay BTC payments temporarily disabled

We have reports that BTC payments are not being processed correctly. Our team is reviewing the issue.

This is resolved. Please contact support if you have issues.


Want to change default delimiter to other

Hello,
This plugin seems to work great.
But I have few queries, It would be great if you help me, overcoming those.

I want to change default delimiter comma to other symbol like "|" or  "/"
As I have suggestions that has comma in it. And this makes it breaking a single term into multiple.

Want to customize the dropdown suggestions view by supporting html in it.
So that I can be able to add css classes to it.
Have a look on attachment to get it clear.

Thanks.
Sneha

You can change the default delimiter by passing  - delimiter: '|' or an array ['|', ','],
Example -
$('#ajey').tokenfield(
{
createTokensOnBlur: true,
delimiter: ['|', ','],
typeahead: [
{
minLength: 1,
highlight:true
},
{
source: engine.ttAdapter(),
templates: {
}
}
]
}
);

Thanks, This works.

@Ajeey  and @sneha27  tab is not working after selecting an element even not enter. can you please tell me how can i do this?

@omar-faruk-sust  Please create a jsfiddle with your problem and paste it here so that I can help you out.

@Ajeey can you see the #244 this issue please, here i give the details.

@omar-faruk-sust I think its better you create a fiddle and post it. Becomes a lot easier to debug


Implement Trans component

📜 Description
This PR adds a new feature to the project: the Trans component. The Trans component is a custom translation component that can interpolate variables and parse HTML elements.
The Trans component takes three props:

children - The translation string to be rendered.
values - An object containing values to be interpolated in the translation string.
components - An object containing custom React components or HTML tags to be parsed and rendered.

This PR also includes an updated version of package.json.
🧪 How to test this?
To test this PR, follow these steps:

Clone the repository.
Checkout the trans-component branch.
Install dependencies with yarn install.
Run tests with yarn test.
Link littera package with yarn link while in the root directory.
Set up an example React app with npx create-react-app ./PlaygroundApp --template=typescript
Link littera with the example app and complete basic setup. Link with yarn link @assembless/react-littera while in the apps root directory.
Run the app and navigate to http://localhost:3000 to see the Trans component in action.

🚀 Examples
Here are a few examples of how to use the Trans component:
import React from 'react';
import { Trans, useLittera } from '@assembless/react-littera';

const translations = {
  welcome: {
    en_US: "Welcome {name}!",
    de_DE: "Willkommen {name}!",
    pl_PL: "Witaj {name}!",
  },
};

function App() {
  const translated = useLittera(translations);

  return (
    <Trans values={{ name: "Jack" }}>
      {translated.welcome}
    </Trans>
  );
}

import React from 'react';
import { Trans, useLittera } from '@assembless/react-littera';

const translations = {
  about: {
    en_US: "This is the about page.",
    de_DE: "Dies ist die Über uns-Seite.",
    pl_PL: "To jest strona o nas.",
  },
};

function AboutPage() {
  const translated = useLittera(translations);

  return (
    <Trans components={{ a: "Link" }}>
      {translated.about}
    </Trans>
  );
}

We have pushed a nightly release that includes the Trans component.
<EMAIL_ADDRESS>To update run: yarn upgrade @assembless/react-littera@nightly

/reviewpad summarize


Crash on illumos due to different passwd struct definition

Describe the bug
Hi there, and thanks for maintaining this library!
I'm trying to use a project that depends on whoami, on illumos, and I'm seeing memory corruption occur due to this.
This appears to be because the passwd struct is different on illumos than on other Unixes -- so the getpwuid_r call corrupts memory.
On illumos, the passwd struct is listed here (search for "passwd Structure"):
struct passwd {
    char *pw_name;      /* user's login name */
    char *pw_passwd;    /* no longer used */
    uid_t pw_uid;       /* user's uid */
    gid_t pw_gid;       /* user's gid */
    char *pw_age;       /* not used */
    char *pw_comment;   /* not used */
    char *pw_gecos;     /* typically user's full name */
    char *pw_dir;       /* user's home dir */
    char *pw_shell;     /* user's login shell */
};

But what whoami uses on illumos is defined here:
#[repr(C)]
struct PassWd {
    pw_name: *const c_void,
    pw_passwd: *const c_void,
    pw_uid: u32,
    pw_gid: u32,
    pw_gecos: *const c_void,
    pw_dir: *const c_void,
    pw_shell: *const c_void,
}

To Reproduce
On an illumos system, run:
#[test]
fn test_names() {
    println!("{:?}", whoami::username());
}

Then, run cargo test --release -- --nocapture.
This fails with:
     Running tests/basic.rs (target/release/deps/basic-3cc3589bf34767da)

running 1 test
"unknown"
error: test failed, to rerun pass `--test basic`

Caused by:
  process didn't exit successfully: `/home/rain/dev/whoami/target/release/deps/basic-3cc3589bf34767da --nocapture` (signal: 6, SIGABRT: process abort signal)

Expected behavior
No crash occurs.
Additional context
It looks like the nix library implements this call safely, using the passwd definition in libc here.
Would it be okay to switch the Unix impl of this library to using nix rather than doing this call by hand? That would make it so that whoami would work on any platforms supported by nix and libc (which is roughly all of them).
I'm happy to do the work here if you're okay with it. Thanks!

@sunshowers Thanks for opening this issue!
Unfortunately, nix has an MSRV of Rust 1.69, which would break whoami's MSRV of Rust 1.40, so it is not an option for this project.
I'd be happy to review and merge a PR if you wanted to do the work fix it.

Thanks for the response. Would you be open to changing the MSRV policy at all? The general ecosystem consensus is that changing the MSRV can be done with a minor version bump (so as part of 1.5.0 in whoami's case).
Thee advantage of that would be that this crate has less unsafe code, instead relying on the already-audited unsafe code in nix. To my mind, that advantage far outweighs MSRV considerations, especially against ancient versions of Rust.
This comment on Zulip may be helpful. Assuming that whoami's usage follows the general patterns of overall crate usage, an MSRV of 1.69 would result in well over 90% of overall fetches being satisfied. And it's quite likely that whoami's largest dependencies have a much more modern MSRV. I briefly looked through the top couple of reverse dependencies and found that they don't actually have an MSRV policy at all, meaning they're only guaranteed to build on the latest version of stable Rust.
I've written a series of patches at https://github.com/oxidecomputer/whoami which switches whoami to using nix. This works very well, and massively reduces the amount of unsafe in whoami.

Another option is to use the libc crate. Currently, libc 0.2 has a fixed MSRV of 1.13. The MSRV policy for the next version of libc, 1.0, is actively being discussed here.
However, while that would fix the immediate issue, it still results in this crate containing a great deal of unsafe code.

In any case, once this issue is addressed we will likely need to put out a RUSTSEC advisory, since this is a stack buffer overflow. I'm happy to work with you on that!

Thanks for the response. Would you be open to changing the MSRV policy at all? The general ecosystem consensus is that changing the MSRV can be done with a minor version bump (so as part of 1.5.0 in whoami's case).

Considering that I have advertized whoami 1.0 to not break MSRV without a major version bump, any MSRV policy changes would have to be accompanied with the 2.0 release.  When whoami 1.0 was released, there was not a general ecosystem consensus on when to change MSRV, as advertizing and supporting an MSRV was just becoming popular.

Thee advantage of that would be that this crate has less unsafe code, instead relying on the already-audited unsafe code in nix. To my mind, that advantage far outweighs MSRV considerations, especially against ancient versions of Rust.
This comment on Zulip may be helpful. Assuming that whoami's usage follows the general patterns of overall crate usage, an MSRV of 1.69 would result in well over 90% of overall fetches being satisfied. And it's quite likely that whoami's largest dependencies have a much more modern MSRV. I briefly looked through the top couple of reverse dependencies and found that they don't actually have an MSRV policy at all, meaning they're only guaranteed to build on the latest version of stable Rust.
I've written a series of patches at https://github.com/oxidecomputer/whoami which switches whoami to using nix. This works very well, and massively reduces the amount of unsafe in whoami.

Makes sense to me.  I think it's time to create the v2 branch, and if you open a PR I'll review it for inclusion there.

Another option is to use the libc crate. Currently, libc 0.2 has a fixed MSRV of 1.13. The MSRV policy for the next version of libc, 1.0, is actively being discussed here.
However, while that would fix the immediate issue, it still results in this crate containing a great deal of unsafe code.

I think this could be an option for whoami 1.0 release track, depending on what the policy ends up being.

In any case, once this issue is addressed we will likely need to put out a RUSTSEC advisory, since this is a stack buffer overflow. I'm happy to work with you on that!

Help would be appreciated on that, thank you!

Considering that I have advertized whoami 1.0 to not break MSRV without a major version bump, any MSRV policy changes would have to be accompanied with the 2.0 release. When whoami 1.0 was released, there was not a general ecosystem consensus on when to change MSRV, as advertizing and supporting an MSRV was just becoming popular.

Sounds good. Happy to put up a PR once the v2 branch is out. (I'd also have a few other suggestions for that branch, such as making the fallible methods the default ones, and maybe removing the infallible ones while providing an easy way to get defaults like unknown).
It would also be great to figure out an MSRV policy as part of the v2 release. What do you think of something like:

best effort, but will occasionally bump if dependencies change
a minimum of 6 months of support -- this would easily cross the 90% threshold, based on the data in the Zulip comment. (Rust 1.69 was released on 2023-04-20, so if we bump to that we'll get 10+ months of support.)
minor version number must be bumped

And once again, thank you for maintaining this crate. As I was telling my coworker, whoami does something nothing else does -- provide a cross-platform wrapper to data that's generally pretty useful!

Created different issues for follow-up work based on the discussion here.  Closing the issue, since it's fixed on the v1 branch.  Release will be tracked at https://github.com/ardaku/whoami/issues/87

whoami 1.5.0 just released to crates.io with this fix.


How to I uninstall

Sorry to ask this here, but how do I uninstall this add-in. I can't see in my account or Outlook add-ins

If you don't see an add-in in you individual list it's possible your admin installed it tenant wide

I installed it manually via this link - https://appsource.microsoft.com/en-us/product/office/WA104005406


Linux issues

After trying it on Linux, there are a few more issues.
The MessageBox doesn't show up centered to the parent. That's an issue with Avalonia; but as for right-now, here's the fix.
We can close the dialog with Esc or Enter; but not Space. We have to do Tab,Tab,Space to close it. Should set the initial focus to the default button.
Min/Max buttons are displayed. Not being able to hide them is a Avalonia problem. On Linux, pressing Min flickers then does nothing. Pressing Max hides the window border/title and centers the window. Just some weird behavior.

I think centering correctly should be handled by Avalonia itself. Do you know if there is already an issue related to that there?

There are discussions about it, but no release date for a fix. Some stuff will wait until Wayland renderer release before getting fixed.


Rename parameter "bool" to "wait_for_kernel_finish" to solve issue #262.

This message was generated by git-bob (version: 0.9.0, model: gpt-4o-2024-08-06), an experimental AI-based assistant. It can make mistakes and has limitations. Check its messages carefully.
The changes made to address issue #262 involve updating the parameter name in the set_wait_for_kernel_finish function within the pyclesperanto/_interroperability.py file. Specifically, the parameter name was changed from bool to wait_for_kernel_finish to avoid using a type name as a parameter. This parameter is utilized to call the wait_for_kernel_to_finish function with the updated name, and the existing deprecation warning informs users to consider using wait_for_kernel_to_finish() directly. View the modified file.
closes #262

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 87.91%. Comparing base (a2dd16c) to head (cec6e06).

Files with missing lines
Patch %
Lines

pyclesperanto/_interroperability.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #263   +/-   ##
=======================================
  Coverage   87.91%   87.91%
=======================================
  Files          20       20
  Lines        1646     1646
=======================================
  Hits         1447     1447
  Misses        199      199

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

We should also update the parameter name in the core.py file:
https://github.com/clEsperanto/pyclesperanto/blob/a2dd16cb3fe9947000a40f6a8432e7d1d6f915b1/pyclesperanto/_core.py#L129-L146

We should also update the parameter name "flag" of the "wait_for_kernel_to_finish" function in the core.py file. It should be named "wait".

This message was generated by git-bob (version: 0.9.0, model: gpt-4o-2024-08-06), an experimental AI-based assistant. It can make mistakes and has limitations. Check its messages carefully.
In the recent updates, modifications were made to the pyclesperanto repository. Specifically, the function parameter bool was renamed to wait_for_kernel_finish in the set_wait_for_kernel_finish function within the newly created file pyclesperanto/_interroperability.py. Additionally, in the wait_for_kernel_to_finish function, the parameter "flag" was renamed to "wait" in another new file pyclesperanto/_core.py.

Also in _interroperability.py let's call the parameter "wait" and not "wait_for_kernel_finish".

This message was generated by git-bob (version: 0.9.0, model: gpt-4o-2024-08-06), an experimental AI-based assistant. It can make mistakes and has limitations. Check its messages carefully.
In the recent changes, there have been modifications to rename parameters in two functions for improved clarity. In the file pyclesperanto/_interroperability.py, the parameter "bool" was renamed to "wait" in the set_wait_for_kernel_finish function. Similarly, in the file pyclesperanto/_core.py, the "flag" parameter was renamed to "wait" in the wait_for_kernel_to_finish function. With these changes, both files have been created or updated to reflect these parameter name adjustments.


how to install with PHP7 in centos 7?

I git clone it, and cd the folder, run ./install .it's not working.
env：Linux localhost.localdomain 3.10.0-327.13.1.el7.x86_64
PHP：PHP 7.0.6 (cli) (built: May  5 2016 18:26:00) ( NTS )

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

it's ok,libtool version made this wrong, close it.


Enable NuGet packaging of OutlookService sample

Enable Microsoft.OData.ProxyExtensions to be used in projects targetting WP8
Enable nuget packaging of OutlookServices sample

LGTM modulo Bcl.Build version dependency.


Aquatic Forms causing major lag when a large amount are in water (again)

ok guess im not the only one with this issue


feat: memcached instrumentation

Which problem is this PR solving?
Adds auto-instrumentation for memcached.
Short description of the changes
We're monkey-pathing an public generic command function all methods use internally.

in general lgtm, I'm missing just one thing to be able to verify this easily, a working example so that I can generate spans myself, can you please add the example ?

in general lgtm, I'm missing just one thing to be able to verify this easily, a working example so that I can generate spans myself, can you please add the example ?

Added an example!

@Rauno56 Should be good to merge after fixing the CI


Add latest signatures

Description
Updated procedures signatures to match the latest Memgraph.
Pull request type
Please delete options that are not relevant.

[x] Bugfix

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

######################################
Reviewer checklist (the reviewer checks this part)

[ ] Core feature implementation
[ ] Tests
[ ] Code documentation
[ ] Documentation on gqlalchemy/docs

######################################

Added new signatures, but tests kept failing. I spoke shortly with @Josipmrden and the decision is to skip the test for now. This is not as important and it's blocking other features from being merged.
TODO: check fail on constraints test.

@antepusic @as51340 @Josipmrden I will just need approval so I can merge after all tests pass


contos6.9 Compilation error

Describe the bug
{ "@swc/core": "^1.3.4" } Compilation error ;
yarn dev:h5;
yarn run v1.22.17
$ cross-env BUILD_ENV=dev taro build --type h5
?? Taro v3.5.10
thread '' panicked at 'attempt to divide by zero', library/std/src/sys/unix/thread.rs:552:70
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
locking version "resolutions": { "@swc/core": "1.3.3" } normal;
Input code
No response
Config
No response
Playground link
No response
Expected behavior
Normal compilation
Actual behavior
No response
Version
^1.3.4
Additional context
No response

what is taro build? please provide reproducible codes, without other external tools to confirm if this is swc/core issue or not.


ref: Rename component modules to lower case (ruff N999)

Rename component modules to lower case (ruff N999)

@ogabrielluiz The Playwright tests pass and I did some manual testing.
Do you see other tests that should be done ?


Feature US6761-allow_notifier_with_notifiers

Add notifier object back in for backwards-compatibility.
@fractalis Can you review, please?

Looks good; did notice that we still have a reference to notifiers in the RSpec for the EmailNotifier (https://github.com/cloudvox/adhearsion-reporter/pull/2/files#diff-1336e2d9aa7a7bdc6eb5452f4246578dR127) - believe that sould be the only line that needs to be changed for the EmailNotifier tests.

I made the change to the test locally, and it seems that the multiple notifiers tests are now not passing. I'll have to look into this some more.

You might need to add this before line 181 in the RSpecs (https://github.com/cloudvox/adhearsion-reporter/pull/2/files#diff-1336e2d9aa7a7bdc6eb5452f4246578dL181)
Adhearsion::Events.clear_handlers(:exception)

The exception handlers are kept between each of the RSpec contexts, so we try to notify with the EmailNotifier again but don't have all the set-up to allow the test to pass that was necessary in its specific context.

Good question, Ben. I don't see any reason for the index. I've quickly changed the code leave it out, and unit tests aren't broken, but I wonder if I should do more "real" tests.

Thanks Rachel; the original use of index was an arbitrary decision on my part but I think using the reference to the notifier is a better approach, especially considering I was already using it to call #init.

Thanks both of you. Changes are made according to comments.
@fractalis Do you want to have another look?

@fractalis Is this okay to merge now?

Yep, looks solid to me. @ajayanty Good to merge when you have a chance, thanks!

@ajayanty Can you merge when you get a chance?


Docs include broken links that reference the Pulumi Service API

These links are then hit by the broken link checker, which triggers 5xx responses from the API server. We should see about skipping these specific links somehow.

We should just exclude all links to https://app.pulumi.com


test if saving/loading work with interactive learning approach (esp the online learning part)

in previous experiments, i noticed that they weren't working because the predicate classifiers weren't being saved correctly. need to dig into this

it's weird though, because _learn_nsrts() saves pickled NSRTs, which should include the predicate objects in them, so things should work already


Perl build with make

Create a static library of the core C code using the Makefile generated by charmonizer and link the result with the compiled XS code. This makes it possible to speed up the build of the Perl runtime by running make jobs in parallel. It also centralizes the selection of C source files which becomes important when building multiple binaries.

I came to the conclusion that this needs more work.


Clarifies audience for L&L's.

I was talking with a non-engineering colleague in the PDDE org and they mentioned how unclear they are about who L&L's are for. I talked this over with @orta and we both agreed that we want to continue L&L's as we have done (sometimes deeply technical topics, sometimes topics for a general audience). Instead, let's address the concerns of our colleagues directly by changing how we communicate L&L's internally.
This pull request changes our L&L documentation to provide clarity around:

how L&L's generally have an ill-defined audience, but...
individual L&L's should have their audience defined within Artsy staff newsletters and calendar invitations.

It also cleans the docs up a little bit.
This is a WIP until I can get some feedback from colleagues in PDDE.

Okay, this is ready for review. I'll mention it in standup this morning.

This feels right to me 👍
I do like being more explicit on the audience. Also being mindful of when we send out an invite to everyone vs just engineering or product.


Not finding nested modules/all imports failing

Greetings everyone!
I apologize if the questions seems a bit too stack-overflowy but I'm having issues with the module imports being resolved.
For some reason nested imports are not being respected at all. I have no trouble running index.js and rendering stuff - works awesome!
But when I try to import a custom router which handles what gets shown (just for example) - it doesn't wish to resolve or import the module -
import Router from 'components/layout/Router/Router';
(the components directory is inside pages so it is as follows:
Root
-pages
--index.js
--components
---layout
----Router
-----Router.jsx
)
And it's failing with the following error:
These modules were not found:

* components/layout/Router/Router in ./pages?entry

Same goes for me trying to include a css file or any other components that are nested. Am I missing something very obvious here?
Sorry if the question/issue seems bafoonish, I've only used webpack before in a client-side type of bundling so I'm pretty new to universal javascript - I just used rules, tests and loaders to make sure the js I need is being included and is "importable" so to speak.

try ./components/layout/Router/Router notice the ./ at the beginning.

@tkh44 Hey, thanks for the quick response, but it doesn't seem to be picking it up.
Tried the following:
import Router from './components/layout/Router/Router';
import Router from '/components/layout/Router/Router';
import Router from 'components/layout/Router/Router';
import Router from '~/components/layout/Router/Router';
Last one was with module resolver setup.

Okay guys I was being bad at reading the docs - turns out the .jsx imports were failing - as they should be.
.js rename worked like a charm!


OnPrime Flyte Binary Values file Link not found (404 Error)

curl -sL https://raw.githubusercontent.com/davidmirror-ops/flyte-the-hard-way/main/docs/on-premises/single-node/manifests/onprem-flyte-binary/values.yaml > onprem-flyte-binary-values.yaml
This link given in single node on-prem installation of flyte-binary didn't work

Thanks for reporting
It has been fixed. Please check and report any other problem


TWILIO

Explore SMPTLIB module to send hassle free texts to phone

SMTPLIB using the below would be a nice alternative to Twilio:
AT&T<EMAIL_ADDRESS>Sprint<EMAIL_ADDRESS>or<EMAIL_ADDRESS>T-Mobile<EMAIL_ADDRESS>Verizon<EMAIL_ADDRESS>Boost Mobile<EMAIL_ADDRESS>Cricket<EMAIL_ADDRESS>Metro PCS<EMAIL_ADDRESS>Tracfone<EMAIL_ADDRESS>U.S. Cellular<EMAIL_ADDRESS>Virgin Mobile<EMAIL_ADDRESS>

Thanks for adding that I am about to add that


Make it possible to define the full path in copyLibraries

Library Affected:
workbox-cli, (workbox-build)
Browser & Platform:
all browsers
Issue:
I am using workbox for precaching in a business web application with React and AngularJS. We have many customers for our software, that run it via intranet, so I have to serve the workbox libraries from local files.
I use workbox-build with injectManifest to create the service-worker in our Gulp-build-process. The workbox-library files are generated during the build-process by using copyLibraries from workbox-cli.
The problem is, that the output folder of copyLibraries mandatorily contains the version number of workbox, e.g. “workbox-v4.3.1”. Which means, I can’t reference the workbox-folder in the modulePathPrefix-configuration of my service-worker without committing to a specific version number, that has to be manually changed when upgrading to a new version of workbox.
Currently we use a workaround for this issue is by copying the files with two Gulp-tasks.

Execute the command “workbox copyLibraries build/“ to copy the workbox-files to a temporary folder, that is deleted at the end of the build-process. This copies the workbox-files to “build/workbox-v4.3.1”.

Copy the files from “build/workbox-v4.3.1” to the final folder “dist/app/workbox”.

gulp
.src('build/workbox-*/*')
.pipe(flatten()) // extracts the files from the folder "workbox-v4.3.1"
.pipe(gulp.dest('dist/app/workbox'))

Possible Solution: To avoid this workaround, it would be great, if there was an option to define the full path for the copyLibraries-command of workbox-cli, instead of just the path where the “workbox-vX.Y.Z”-folder will be copied to.
For example, there could be an additional flag that can be set in the command, that specifies that you are defining the full path, that points directly to the library-files.
Example: “workbox copyLibraries build/workbox/ --fullpath”.
This will copy the library-files directly into the folder “build/workbox”.
Is there already some easy solution to achieve this behaviour, that I somehow missed or is it intended to bind developers stronger to a certain version of workbox?

The problem is based in:
[https://github.com/GoogleChrome/workbox/blob/ecb987fedeb90954012f17791afe6829b1989d10/packages/workbox-build/src/lib/copy-workbox-libraries.js#L39]
module.exports = async (destDirectory) => {   const thisPkg = require('../../package.json');   // Use the version string from workbox-build in the name of the parent   // directory. This should be safe, because lerna will bump workbox-build's   // pkg.version whenever one of the dependent libraries gets bumped, and we   // care about versioning the dependent libraries.   const workboxDirectoryName = workbox-v${thisPkg.version};   const workboxDirectoryPath = upath.join(destDirectory, workboxDirectoryName);   await fse.ensureDir(workboxDirectoryPath); ...
by replacing the section with:
module.exports = async (workboxDirectoryPath) => {   await fse.ensureDir(workboxDirectoryPath); ...
the issue could be solved.

The underlying reason for this was that, until very recently, not all browsers would check importScripts() resources for updates and trigger the service worker update flow. (Chrome didn't until last month with Chrome 78.) So if the URL that you used with importScripts() didn't contain any versioning info that would be bumped each time you upgraded your Workbox deployment, users of your service worker would be stuck on older versions of Workbox indefinitely.
So I really would not attempt to work around the versioning info in the importScripts() URL.
That being said, if you update to Workbox v5 (currently in release candidate), the default behavior in generateSW mode is to create custom, local bundles of the Workbox (and those bundles contain hashes as part of their URLs for versioning info). If you use it in importScripts mode it's up to you to create your own local bundles, but you can do that by bundling the JavaScript/TypeScript modules directly using Rollup/webpack/etc.
Local bundles are the direction we're going with moving forward, so there's not going to be any changes to the copyLibraries flow in the v4 branch.


Failover and load testing for V3 endpoints

We need to do proper failover and load testing for v3 scenarios against v3 endpoints.

V3 blobs are exposed by CDN, and search service has a failover scenario. Closing since this is no longer required.


auro-carousel: callback after panes are fully loaded

Is your feature request related to a problem? Please describe.
At the moment we are implementing a shoulder svelte component for our search microsite. I am facing some issues while implementing the a center pane on the selected pane due to not have a way to know when the panes have fully loaded.
Project Link: https://github.com/Alaska-ECommerce/flightsearch-lem-svelte
Workaround: https://github.com/Alaska-ECommerce/flightsearch-lem-svelte/blob/main/src/lib/results/ShoulderDates.svelte#L27
At the moment, I played with lifecycle methods in order to wait until the panes are fully loaded. In addition, I also tried to put a setTimout to wait 1 sec for the panes to load. This 2 solutions seem to me hacky and not ideal.
Describe the solution you'd like

I would like to get some sort of callback or return that tells me that the panes are fully loaded with the data so I can use my handleCenter() function to center the carousel to the middle of the screen.
A Center carousel on the selected one. we pass the selected pane which is the one that gets darken, it would be ideal if the carousel also centers to the selected one.

Describe alternatives you've considered

Set 1 second timeout in order to wait for the panes to load.
Use lifecycle methods to sort of re-render once the variable that I hold the selected pane changes.

Issue is being tracked by: https://github.com/AlaskaAirlines/auro-carousel/issues/19


Update administration-center-api_environment_settings.md

Updated wording from Key to Connection String.

Learn Build status updates of commit 29004c0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dev-itpro/administration/administration-center-api_environments.md
:warning:Warning

Details

dev-itpro/administration/administration-center-api_environment_settings.md
:white_check_mark:Succeeded

dev-itpro/administration/administration-center-api_environments.md

Line 679, Column 156: [Warning: bookmark-not-found] Cannot find bookmark '#put-appinsights-key' in 'administration/administration-center-api_environment_settings.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Acronym between two letters breaks mapping

- (void)testEdgeCase
{
    NSString *localKey = @"userIDFirst";
    NSString *remoteKey = @"user_id_first";

    XCTAssert([remoteKey isEqualToString:[localKey remoteString]], @"[%@ isEqualToString:%@", remoteKey, [localKey remoteString]);
}

Expected result:
[@"userIDFirst" remoteString] => user_id_first
Current result:
[@"userIDFirst" remoteString] => user_idfirst

Fixed on NSString-HYPNetworking 0.3.0
https://github.com/hyperoslo/NSString-HYPNetworking/releases/tag/0.3.0
Thanks @RamonGilabert  !!!


nsc-events-nextjs_8_427_edit-dialog-arrows

Resolves #427
This PR changes the edit dialog box on the Event Detail page to be less wider. Drop shadow has been added to the arrow icons so they stand out better from the background.
Before

After

Before

After

This PR works as explain and looks good. Event dialog window is minimize a little and the edit box is shaded in grey.

This PR looks good on my end!

Hey team,
I checked out the pull request for the Event Detail page changes. The update to the edit dialog box and arrow icons look awesome! Making the edit dialog box narrower definitely helps it look cleaner and easier to navigate. Adding the drop shadows to the arrow icons really makes them pop against different backgrounds, which is a nice touch since it gives it a contrast with the rest of the UI.
Looking at the file changes, I noticed you applied the drop shadow to both the back and forward arrow icons, and the dialog box adjustments seem good. The updated edit dialog box looks much better with these additions. One suggestion would be to make sure the shadows are consistent across all pages and screen resolutions to keep the UI looking cutting edge.
I found a helpful guide on improving UI with shadows and depth:
https://bootcamp.uxdesign.cc/designing-in-the-shadows-how-to-use-shadows-to-enhance-your-ui-72cda79aa878
Thanks!

I can see that in my end, it looks wonderful.


Create Lexington Christian Academy domain

@ScienceMind11 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

School URL
450 W. Reynolds Road
Lexington, KY 40503
High School Course Guide (STEM pathway shown on page 6)
I'm happy to provide number four, I just don't quite understand what sort of proof you want.

@ScienceMind11 Please provide us with any of the following as the proof confirming that 365.lexca.org belongs to the school:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

Thank you for your cooperation!

This is a screenshot of an email sent to me by the LCA administration regarding email addresses and their formats (black boxes represent personal information that I'd rather not share openly). If this isn't enough, please let me know and I'll see what more proof I can find.

@ScienceMind11 Thank you for the clarification and your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Panic when using nested dynamic arrays

Aim
fn main(mut array: [Field; 2], i: u32) {
    array[i] = 2;

    let array2 = [array, array];
    println(array2[i][i]);
}

Expected Behavior
The value of arra2[i][i] to be printed
Bug
The application panicked (crashed).
Message:  internal error: entered unreachable code: Dynamic array should already be initialized
Location: compiler/noirc_evaluator/src/ssa/acir_gen/acir_ir/acir_variable.rs:1966

This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at
https://github.com/noir-lang/noir/issues/.
If there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml

To Reproduce

Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
No response
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

I was experimenting with an optimization to optimize array merges across if conditions using [array1, array2][cond as u32] but this bug prevents that.


Add custom headers names

Allows to setup the headers names using configuration
closes #7

I'm closing this PR because I hadn't have the time to make the requested changes and the related issue is already closed by #13


update typescript to 3.4.x

Angular is going to support typescript 3.4.x in version 8. So we need to update the same.

Would you want to open a PR with this?

Yes will open the PR.


warning: Model myModel has auth with authStrategy public of which is not yet supported in DataStore.

hi
my graphql has an entity like this:
type myModel @model @auth(rules: [
    { allow: public, operations: [read] }

]) {
  id: ID!
  aaa: String!
  bbb: Float!
  ccc: AWSJSON
  ddd: AWSDateTime
}

I get this message when I try to save something on the server side (I see nothing on server , in admin.amplifyapp.com/)

warning: Model myModel has auth with authStrategy public of which is not yet supported in DataStore.

my understanding, is I have to add login/password for my users in other to save on amplify for iOS ? I don't want to do this, I just want to let users use the app without logins at first with the possibility to save on server.
is this correct? if yes, is it planed soon to add support for app to "use of api without having user to login"?
thank you in advance for your support

Dupe of https://github.com/aws-amplify/amplify-ios/discussions/1221, let's continue the conversation there


Updated the accounting Namespace

Added allowed edge contains from CompanyEntity to CompanySpecificCategorization
Added new entity CompanySpecificCategorization.
Please check and verify the new entity definition for validation.

test


Feature/112 initial solution

closes #112

implement for subduction as well

recreating this with the correct commits


Add missing properties to Error property on ServerError

Add Phase and Grouped to Error property on ServerError
Example:
{
  "error" : {
    "root_cause" : [
      {
        "type" : "parse_exception",
        "reason" : "failed to parse date field [-1m] with format [strict_date_optional_time||epoch_millis]"
      }
    ],
    "type" : "search_phase_execution_exception",
    "reason" : "all shards failed",
    "phase" : "query",
    "grouped" : true,
    "failed_shards" : [
      {
        "shard" : 0,
        "index" : "project",
        "node" : "Uo6PBln_QrmD8Y9o1NKdQw",
        "reason" : {
          "type" : "parse_exception",
          "reason" : "failed to parse date field [-1m] with format [strict_date_optional_time||epoch_millis]",
          "caused_by" : {
            "type" : "illegal_argument_exception",
            "reason" : "Parse failure at index [2] of [-1m]"
          }
        }
      }
    ],
    "caused_by" : {
      "type" : "parse_exception",
      "reason" : "failed to parse date field [-1m] with format [strict_date_optional_time||epoch_millis]",
      "caused_by" : {
        "type" : "illegal_argument_exception",
        "reason" : "Parse failure at index [2] of [-1m]"
      }
    }
  },
  "status" : 400
}

Add Line and Col
Example:
{
  "error" : {
    "root_cause" : [
      {
        "type" : "parsing_exception",
        "reason" : "[terms] unknown token [END_ARRAY] after [numberOfCommits]",
        "line" : 9,
        "col" : 7
      }
    ],
    "type" : "parsing_exception",
    "reason" : "[terms] unknown token [END_ARRAY] after [numberOfCommits]",
    "line" : 9,
    "col" : 7
  },
  "status" : 400
}

I think I found another case where it would be nice to have ServerError populated. I accidentally set a field to use fvh highlighter without correct settings, and the error was returned like below. I had to read the response from DebugInformation to find the error source. Using NEST 5.3.0
    "took": 47,
    "timed_out": false,
    "_shards": {
        "total": 5,
        "successful": 0,
        "failed": 5,
        "failures": [{
            "shard": 0,
            "index": "udf__2017.04.19_11.08",
            "node": "eNK9OdfmSyyruECF3GaHFw",
            "reason": {
                "type": "illegal_argument_exception",
                "reason": "the field [name.nor_lemmas] should be indexed with term vector with position offsets to be used with fast vector highlighter"
            }
        }]
    },```

#2929 deals with this, additional documents will appear in Metadata on Error starting with 6.x

This has now been merged


Meeting #6 - Oct 8, 2022

Meeting Time: 8 PM
Meeting Agenda:

[ ] SRS Peer Review
[ ] Hazard Analysis
[ ] POC Breakdown

Related Issues:

#119

Peer Review

You state "Bluetooth wireless connective capabilities" is out of your scope, however your product/app will be using Bluetooth to connect to the lock. This is a bit confusing and sounds conflicting.
Should GPS signal be an input in the System Context?
The problem statement mentions how current locking system may not lock the seat, however your product does not mention being able to do this.

Verifiable Requirements
This is not a good NFR as it is very difficult to verify. The state method of verification is not a good to verify this. Also it is a bit ambiguous as there are multiple ways to "use" the app.
NFR1: Can be used by people of any language.
Verification: App will be verified by test users who do not know english.
Verifiable Requirements
This NFR is not an easily verifiable requirement. The idea of using test users will always be subject to biases.
NFR4: The design must be visual appealing.
Rationale: Our lock must be visual appealing for it to be a desirable product.
Verification: Design willbe verified with test users who will rank visual how appealing the lock is.
Complete, Correct and Unambiguous
There is very little description of the iOS App. Hard to tell how exactly this app will work and be structured.
Complete, Correct and Unambiguous
In your scope, you state that it will be waterproof, but you also assume that the lock will be weatherproof (A3)
What not How (Abstract)
Throughout the SRS and in the requirements, it is mentioned that this is an iOS app, however this should have been stated with rational within the constraints (rational was in requirements section).
LO_Impact / Focus on Users
Missing stakeholder (e.g., society) and Health/Safety/Cultural factors
- No mention of safety measure to prevent injuries during use to the user (e.g., do no camp down on the user's finger, will not use be moving a speed or force that can use injuries)


Improved code coverage for issueSolution app

Worked ontop of pull: #124 since I fixed a lot of annoying bugs in it.

Pull Request Test Coverage Report for Build 25

333 of 336 (99.11%)  changed or added relevant lines in 12 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+27.6%) to 73.73%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

project/issueSolution/views.py
8
9
88.89%

project/teams/models.py
13
14
92.86%

project/teams/views.py
44
45
97.78%

Files with Coverage Reduction
New Missed Lines
%

nspmessage/tests.py
1
90.91%

nsp/tests.py
2
85.71%

Totals

Change from base Build 21:
27.6%

Covered Lines:
929

Relevant Lines:
1260

💛  - Coveralls


Sylvania LIGHTIFY Motion and Temperature Sensor showing double entries after 0.85.0 upgrade

Home Assistant release with the issue:
0.85.0

Last working Home Assistant release (if known):
0.84.6
Operating environment (Hass.io/Docker/Windows/etc.):
Hass

Component/platform:
ZHA

Description of problem:
Sylvania Smart Home E21266 72923 Sylvania LIGHTIFY Motion and Temperature Sensor showing double entries.  Previous release had single entry. There are now two after 0.85.0 upgrade.
0.84.6:

binary_sensor.centralite_motion_sensora_0e057eed_1_1280     person icon

0.85.0

binary_sensor.centralite_motion_sensor_a_0e057eed_2_1030    house icon
binary_sensor.centralite_motion_sensora_0e057eed_1_1280     person icon

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

@damusmf your issue will be fixed in the next beta

@WedHumpDay I plan on addressing this in the next round of changes after this cycle completes.

@dmulcahey  Great news.. Thanks.


TabError: inconsistent use of tabs and spaces in indentation

Description
What steps will reproduce the problem?

I prefer Sypder over a larger IDE to have a lighter tool to try some code.
So I am copy-pasting a lot of code from external source, add something, ...
Too often I get the error message "TabError: inconsistent use of tabs and spaces in indentation", likely because some code uses spaces other tabs. Manual fixing this is quite cumbersome.
The function "fix identation" does help here either.
On top of that when I actually give up and replace tabs with spaces, delete the tab, insert spaces, the "tool tips" pop up for no reason ... and if I press the wrong button, I also suddenly have some code in there which I did not want.
Makes this version of Spyder almost unusable ....

I guess you mean here "does not help". But why not? What's the problem? Please be more specific.

On top of that when I actually give up and replace tabs with spaces, delete the tab, insert spaces, the "tool tips" pop up for no reason ... and if I press the wrong button, I also suddenly have some code in there which I did not want.

I don't understand very well what you mean here. Please create a simple video and post it here to clarify.

this error is so annoying, im not sure why it happens, everytime it happens i have to fix it by opening the code in sublime text-->view-->identation-->convert identation to tabs

this error is so annoying

But what is the error? Please post the error so we can understand how to fix it.

As I described in the initial post:
"So I am copy-pasting a lot of code from external source, add something, ..."
Likely there is some code with used tabs for indentation others spaces, so you end up with mixture of both and get said error message.
In the meantime I discovered the option to display spaces and tabs, so in that case you could spot the problem, but still you would need to (manually?) change every ident.

I haven't found a function in Spyder to change idents from/to spaces/tabs
not manually, not (semi)automatically
other iDEs (ie Pycharm) provide conversion options and silently, automatically any copy-pasted text to fit the current ident style so that such error never pops up

@SvenMeyer, please upload a file with mixed tabs and spaces for which "Fix indentation" is not working, to see if we can reproduce the error in our side.

fyi it is hard to provide an example here.
why? because by copying and pasting it here it can mix the hiden info that cause that error to happens

You can attach a file @isalirezag or provide us with an error traceback

@isalirezag, you can upload a file directly here instead of pasting its contents.

@SvenMeyer, @isalirezag, we're still waiting for a file from you guys.

@ccordoba12 I cannot upload the .py file here. how should i do that?

Great, thanks!

This bug still exists in spyder 4.1.1
I'm using ubuntu 16.04
Python 3.6.6 64-bit | Qt 5.9.6 | PyQt5 5.9.2 | Linux 4.15.0-91-generic

just clear the indentation and then again give identation by tab. It works in my case in spyder4

@nishant2k  how to clear the indentation? it does not work for me

Temporary solution is to change the indentation characters to 4 spaces in Tools>Preferences>Editor>Advanced settings.

same issue here: Ubuntu 18.04 Spyder 4.1.4


Build error

I cloned the repository first, and then when I executed the command make all-via-docker, I encountered the following error message:
ethan@EthanT14s:~/projects/cryptape/ckb-auth$ make all-via-docker
docker run --rm -v `pwd`:/code nervos/ckb-riscv-gnu-toolchain@sha256:d3f649ef8079395eb25a21ceaeb15674f47eaa2d8cc23adc8bcdae3d5abce6ec bash -c "cd /code && make"
make: /bin/sh: Operation not permitted
make: *** [Makefile:37: deps/secp256k1-20210801/src/ecmult_static_pre_context.h] Error 127
cd deps/secp256k1-20210801 && \
        ./autogen.sh && \
        CC=riscv64-unknown-linux-gnu-gcc LD=riscv64-unknown-linux-gnu-gcc ./configure --with-bignum=no --enable-ecmult-static-precomputation --enable-endomorphism --enable-module-recovery --host=riscv64-unknown-linux-gnu && \
        make src/ecmult_static_pre_context.h src/ecmult_static_context.h
make: *** [Makefile:21: all-via-docker] Error 2

My system parameters are as follows:
ethan@EthanT14s:~/projects/cryptape/ckb-auth$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"

Is there any solution to the problem?

make sure run

git submodule update --init

check permission of local files

make sure run

git submodule update --init

check permission of local files

I performed the following steps:

git submodule update --init
chmod -R a+rw .
make clean

However, I'm still encountering the same error. It seems that the error message indicates insufficient permissions, possibly within Docker?

Are you still encountering the same error when you build it from scratch by removing the old one?


Support for SQL filters

The documentation doesn't specify the quota on the SQL filters per namespace. Are SQL filters supported?

This would be really useful,

@SeanFeldman SQL Filters & Actions are not supported in initial release. We will be updating the documentation to reflect same.
Tagging @Saglodha for further comments.

That's a bummer 🙁 Is there any roadmap / eta for when they will be available? I have 2 projects where i could benefit form the emulator but both make use of sql filters...

We don't have an ETA as of yet however we'll keep this issue open for tracking and I would share progress updates here. @razvangoga

We also need this really badly, please consider prioritizing

Ditto, and reinforce need this :-(  Would be great to have it

I noticed that the schema includes a SQL filter type in the enum, but unfortunately, it is not currently supported. This feature is essential for our needs, and we strongly recommend its implementation.

It does feel like the SQL filters have become an integral part of using service bus, so without them the emulator is not bringing much value atm.


add conda-store image to upgrade docs

Related to https://github.com/Quansight/qhub/issues/842

Closing in favor of https://github.com/Quansight/qhub/pull/843


⚠ Bofrost.si has degraded performance

In ce9540d, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 1717 ms

Resolved: Bofrost.si performance has improved in 53ad00e after 7 minutes.


The Command hub not working well.

Describe the bug
A clear and concise description of what the bug is.
The command hub is not working well. I made one recently and I put a engine on it like it asked me to. After that I made 6 of those solar panels which I tried to connect to the same command hub. But I noticed that the menu of the command hub was broken. I could only connect 1 solar pannel and I could grab the glass panes and every item which you should not be able to grab from the menu.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error
Get a command hub, command hub engine and a solar panel.
Place them next to each other and right click on the command hub.
You notice that you can only link 1 solar pannel and that you can grab the glass panes from the command hub gui.

Expected behavior
A clear and concise description of what you expected to happen.
After I made tue command hub and command hub engine I expected that I could link as many solar panels to it as I wanted.
Screenshots
If applicable, add screenshots to help explain your problem.
Dont have any
Desktop (please complete the following information):

Slimefun Version [ e.g. DEV 1081]:
Server Version [e.g. Paper 1.18.2]:
AdvancedTech Version [e.g. DEV 10]:
We have the most recent slime fun versions.
Additional context
Add any other context about the problem here.

same issue, here is callstack:
java.lang.NullPointerException: Cannot invoke "org.bukkit.inventory.ItemStack.hasItemMeta()" because the return value of "org.bukkit.inventory.Inventory.getItem(int)" is null
        at me.pranavverma.advancedtech.general.items.commanders.command_hub.command_hub.onInventoryDrag(command_hub.java:286) ~[SlimefunAdvancedTech.jar:?]
        at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor2885.execute(Unknown Source) ~[?:?]
        at org.bukkit.plugin.EventExecutor$2.execute(EventExecutor.java:77) ~[purpur-api-1.20.1-R0.1-SNAPSHOT.jar:?]
        at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:77) ~[purpur-api-1.20.1-R0.1-SNAPSHOT.jar:git-Purpur-2023]
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[purpur-api-1.20.1-R0.1-SNAPSHOT.jar:?]
        at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:54) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:126) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:617) ~[purpur-api-1.20.1-R0.1-SNAPSHOT.jar:?]
        at net.minecraft.world.inventory.AbstractContainerMenu.doClick(AbstractContainerMenu.java:480) ~[?:?]
        at net.minecraft.world.inventory.AbstractContainerMenu.clicked(AbstractContainerMenu.java:383) ~[?:?]
        at net.minecraft.server.network.ServerGamePacketListenerImpl.handleContainerClick(ServerGamePacketListenerImpl.java:3252) ~[?:?]
        at net.minecraft.network.protocol.game.ServerboundContainerClickPacket.handle(ServerboundContainerClickPacket.java:58) ~[?:?]
        at net.minecraft.network.protocol.game.ServerboundContainerClickPacket.handle(ServerboundContainerClickPacket.java:23) ~[?:?]
        at net.minecraft.network.protocol.PacketUtils.lambda$ensureRunningOnSameThread$0(PacketUtils.java:51) ~[?:?]
        at net.minecraft.server.TickTask.run(TickTask.java:18) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.util.thread.BlockableEventLoop.doRunTask(BlockableEventLoop.java:153) ~[?:?]
        at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(ReentrantBlockableEventLoop.java:24) ~[?:?]
        at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:1366) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:197) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:126) ~[?:?]
        at net.minecraft.server.MinecraftServer.pollTaskInternal(MinecraftServer.java:1343) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.server.MinecraftServer.pollTask(MinecraftServer.java:1336) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.util.thread.BlockableEventLoop.managedBlock(BlockableEventLoop.java:136) ~[?:?]
        at net.minecraft.server.MinecraftServer.waitUntilNextTick(MinecraftServer.java:1314) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1202) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:323) ~[purpur-1.20.1.jar:git-Purpur-2023]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]```

known bug, working on fixing this.


Migrate to {{ stdlib("c") }}

The sysroot* syntax is getting phased out (conda-forge/conda-forge.github.io#2102).
The recommendation is to move to {{ stdlib("c") }}.
Ref https://github.com/rapidsai/build-planning/issues/39

Thanks @hcho3 for working on this. I haven't followed current progress, is this expected to be working immediately or are there changes elsewhere required before this works properly? I'm asking it because CI is currently failing with an error due to this change:
conda_build.exceptions.DependencyNeedsBuildingError: Unsatisfiable dependencies for platform linux-64: {MatchSpec("c_linux-64")}

I will investigate this further shortly.


[red-knot] store child scopes using a Range instead of a Vec

(idea from Micha)
Instead of Scope::children being a vec of scope IDs, it could just be a Range of descendants (because descendant scopes of a given scope should all be interned contiguously). This would mean that finding direct children would require filtering on the descendants' parent scope ID, but it would avoid allocating (and deallocating) all those vectors.

I did this in the salsa refactor


habitat: pin core/jq-static/1.6

This is to be reverted when we've dealt with core/jq-static/1.10.
I believe that if we get this merged, and then pull the erroneous version 1.10 off bldr (or make it private, whatever), we can revert this: core/jq-static will then resolve to 1.6, and everything will build OK.

we don't need this 💣


[fix] Fix documentation and add job name to stdout

Current dependencies on/for this PR:

main

PR #4   👈

This comment was auto-generated by Graphite.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/tkoft/job-queue?version=dev:6bc9a5bc2a50a9caf31ea4d73362301ca17a289f


Encoding problem

I am on Win7 SP1 x64 with python 3.5.0 x64.
I get error: File "D:\bin\sdat2img.py", line 2 SyntaxError: encoding problem: utf8
I replaced second line: # -*- coding: utf-8 -*- and no more error!

fixed.


Proposal for renaming (npm ready)

I would be happy if you could install your package via npm. Therefore, I propose the following name changes.
@hyperapp/middlewares -> hyperapp-v2-middlewares

There are several reasons for this proposal:

According to Jorge Bucaran, naming the package for hyperapp is better in the hyperapp-xxx format than in the @hyperapp/xxx format.
(ref: https://github.com/jorgebucaran/hyperapp/pull/867#issuecomment-518046892)
The name "hyperapp-middlewares" makes it very difficult to distinguish okwolf's packages.
https://github.com/okwolf/hyperapp-middleware
This is my opinion, but hyperapp V1 and V2 are not compatible and are actually close to another library, so by including "v2" in the package name, this package is for V2 Makes it easier to distinguish.

If you agree, I would be happy if you changed the naming and made it public on npm.

I'm sorry, this suggestion didn't match Jorge Bucaran's claim, so I'll close it.
See the thread below for details.
https://hyperapp.slack.com/archives/C41ECC0V6/p1568503156011300


Simpler support for custom worker class

Currently, in order to create a custom exception handler, you need to create a subclass of QC::Worker and override the #handle_failure method. In addition, you also have to create a custom Rake task to trap INT and TERM and call out to an instance of your custom worker.
The first step makes a lot of sense, but the second step seems unnecessary. It would be simpler for users if there were an API like this:
# lib/my_worker.rb
class MyWorker < QC::Worker
  def handle_failure(job, e)
    # ...
  end
end

QC.worker_class = MyWorker

This is based on the unfounded assumption that it's much more common to change how exceptions are handled than how signals are handled, so it would be valuable to make the first case simpler.
I'm happy to contribute a PR if this is a feature that you guys want.

@bclennox would #241 suffice for your needs?

That is literally exactly what I want! I just didn't see it while searching issues.
Thanks!

:blush: thanks for the quick response.

@senny Do you know when this will make it into an official release? I didn't see it on the list for 3.2 in #250, and it's not on the 3-1-stable branch yet.

@bclennox it will be part of 3.2


Please add "distroless" images to simplify distribution of Swift apps

Current images contain all the development libraries, headers and compilers. This is not a good base to distribute Swift applications.
Please add the image variant that can be used as a base image to run applications, that will have only necessary runtime dependencies. "Distroless" concept seem to be the most effective for that:
https://github.com/GoogleContainerTools/distroless

Current images contain all the development libraries, headers and compilers. This is not a good base to distribute Swift applications.

Agreed, but the images are not intended to be a base for distributing Swift applications. They are a "shop front" for Swift, aimed at newcomers to the language who want to explore building apps and running the REPL.

Please add the image variant that can be used as a base image to run applications, that will have only necessary runtime dependencies. "Distroless" concept seem to be the most effective for that:
https://github.com/GoogleContainerTools/distroless

I agree that it would be great to have a "runtime" image, but I think Swift's runtime requirements are currently quite considerable, unfortunately. I doubt that https://github.com/GoogleContainerTools/distroless/blob/master/base/README.md would be sufficient.
More likely in the short term is an Ubuntu-based runtime image. Even a "Hello world" Swift program links 63 shared libraries: https://forums.swift.org/t/which-clang-package-should-we-install/20542/8?u=ianpartridge

Thanx for the fast reponse!

Agreed, but the images are not intended to be a base for distributing Swift applications. They are a "shop front" for Swift, aimed at newcomers to the language who want to explore building apps and running the REPL.

And that is not something on TODO list to provide runtime base images? I would imagine that Swift Server development would definitely benefit from it.
And thanx for the link! Might help me build my own minimal image 😆

Yes it's definitely on the TODO list 🙂
I would also like images based on Debian (rather than Ubuntu).

Going for distroless-style images, from personal experience it is much easier to use rpm-based distros, because unlike deb they are easier to relocate, to create rootfs with all the dependencies, for example openSUSE:
zypper --non-interactive --root /swift-root install --no-recommends coreutils ...

Then in Dockerfile it will be as easy as
FROM scratch
COPY --from=build /swift-root /
CMD ["appname"]

So that might be a good enough solution at least in short term.

Interesting! I'm not familiar with zypper. Can I suggest you start a discussion on the Docker section of the Swift forums? https://forums.swift.org/c/server/docker

Ok, I will try to come up with something to actually show and not only talk 😆

It seems like there are no quality RPM packages available for Swift, so this might take much longer than I expected.
I did a different experiment, seems like 18.04 version of ubuntu container is supposed to be the smallest one. It is still nearing 250MB with all the deps and Swift runtime libs, but cannot compare it to 700MB of full image:
https://github.com/TheIndifferent/timestampname-swift/blob/master/Dockerfile

Yes I think this is the approach to take with the Swift 5 images.

Closing this because true distroless images are not feasible in the short term. We're working on slim/runtime images at the moment though.


Exposing UDP port

Hi,
does the plugin support exposing UDP ports?
I see just 'void exposePort(Integer port)'.
Thanks.

Yes, in master branch (not released in any published version).
Then one can use void exposePort(String port) to expose udp ports.

Thanks.
So do you have any plans for publishing a new version?.
if not, how can I use master version in my project?

There are plans, but no specifics yet. For local development you can publish the master version into your local m2 repository using the gradle task publishToMavenLocal, and then reference 1.3-SNAPSHOT as version in your project.
Aware of the issues with this...