DEPRECATION: Usage of _actions is deprecated, use actions instead.

This line creates a deprecation warning in Ember 2.7.0: https://github.com/thefrontside/ember-impagination/blob/e62c1c70920cad53d0c06189a2b72dcc8b4d7abb/addon/components/impagination-dataset.js#L33

@flexyford could this be fixed and cut a patch release?

Actually that deprecation seems to have been there since 2.1, but I just noticed it now for the first time.

I tried changing it on my own, but it causes two test failures.  I'm not clear if the issue is the tests or the change, all I did was just drop the underscore from _actions in the line cited above:
not ok 26 PhantomJS 2.1 - Integration | Component | ImpaginationDataset observing the dataset firing a setReadOffset Action "before each" hook
    ---
        message: >
            undefined is not an object (evaluating 'this.actions.setReadOffset')
        stack: >
            http://localhost:7357/assets/dummy.js:1954:43
            http://localhost:7357/assets/test-support.js:15696:29
            run@http://localhost:7357/assets/vendor.js:10780:30
            run@http://localhost:7357/assets/vendor.js:30794:32
            http://localhost:7357/assets/test-support.js:15694:27
            invoke@http://localhost:7357/assets/test-support.js:13760:25
            asyncFn@http://localhost:7357/assets/test-support.js:13745:17
            run@http://localhost:7357/assets/test-support.js:6222:19
            next@http://localhost:7357/assets/test-support.js:6548:13
            http://localhost:7357/assets/test-support.js:6569:9
            timeslice@http://localhost:7357/assets/test-support.js:8176:27
        Log: |
    ...
not ok 29 PhantomJS 2.1 - Integration | Component | ImpaginationDataset observing the dataset firing a setReadOffset Action "before each" hook
    ---
        message: >
            undefined is not an object (evaluating 'this.actions.setReadOffset')
        stack: >
            http://localhost:7357/assets/dummy.js:2083:43
            http://localhost:7357/assets/test-support.js:15696:29
            run@http://localhost:7357/assets/vendor.js:10780:30
            run@http://localhost:7357/assets/vendor.js:30794:32
            http://localhost:7357/assets/test-support.js:15694:27
            invoke@http://localhost:7357/assets/test-support.js:13760:25
            asyncFn@http://localhost:7357/assets/test-support.js:13745:17
            run@http://localhost:7357/assets/test-support.js:6222:19
            next@http://localhost:7357/assets/test-support.js:6548:13
            http://localhost:7357/assets/test-support.js:6569:9
            timeslice@http://localhost:7357/assets/test-support.js:8176:27
        Log: |

_actions is no longer used as of v1.0.0-alpha.1


Allow construction of consumer from an existing rationalizer

That is, let multiple Marshal consumers share a single rationalizer.

Isn't this already true? NewMarshaler is the thing that creates/owns all the rationalizers, and NewConsumer just uses those to claim partitions etc.

Haha I thought when we were on the whiteboard we agreed this needed doing, so I didn't actually verify before filing the ticket. :)
It may be that there is nothing to do here, let me see...

The NewMarshaler makes you specify your topic and group id, so it needs to be refactored.

Oh derp, that was the problem. Carry on!
--
Mark Smith
<EMAIL_ADDRESS>On Wed, May 11, 2016, at 09:31 AM, Sean wrote:

The NewMarshaler makes you specify your topic and group id, so it
needs to be refactored.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub[1]

Links:

https://github.com/dropbox/marshal/issues/40#issuecomment-218514680

This was done.


Plans for 1.0.0

Now that the implementation of the glTF 1.0 specification is complete, the next steps are to consolidate the library to a production standard. 1.0.0 will be the version where this condition is met.
Below is an non-exhaustive list of things I would expect from a 1.0.0 release:

[x] Comprehensive documentation
[x] glTF 2.0 support
[ ] Guaranteed backward compatibility for all 1.x.x releases
[ ] KHR_binary_glTF support
[x] Validate implementations for all 2.0 data structures
[ ] Basic wrapper library for the 2.0 implementation
[x] Conversion to and from 1.0 / 2.0 assets (see #14)

In my fork I have altered the API a little, changed few bits so that they take generic Read objects instead of Path so that it's possible to load models from memory and such.  Additionally, I don't think that slice calls in v2 are needed.

N.B. in the upcoming wrapper interface we're planning to take generic Read.

Oh also I don't think there's a reason to load whole resource in memory and then call from_slice on it.  You could do something like this https://github.com/fst3a/gltf/blob/master/src/v1/gltf.rs#L263

Actual loading of data (images, bins and such) and paths should, in my opinion, be delegated to the user

I mostly agree. The idea behind the Source trait is that the user is able to implement their own loader that is called by the importer. This means the importer can make safety guarantees about external data whilst providing a convenient wrapper around the JSON data structures.
Code bloat is a fair concern. Perhaps the library could make the wrapper an opt-out feature.
If all the user wants is to obtain the raw JSON data and validate then that's fine, the appropriate data structures are available in the json module.
I like the code snippet, I haven't seen chain before. That's a nice trick.

I see.

I forgot to mention: The library is moving toward so called 'zero-cost deserialization' of the JSON data structures, which requires from_slice or otherwise to obtain the lifetime of the data. The latest code in the wrapper branch demonstrates this.

In response to @fst3a 's comment, I've added some extra documentation to the import and json modules explaining how the import process may be customised by the user. The relevant from_reader, to_string, etc. functions from serde_json have been re-exported to hopefully alleviate any version mismatch issues.

Once https://github.com/alteous/gltf/issues/34 is closed this issue will enter a 'final discussion phase'.

Final discussion phase
The next version will be 1.0!

Well... looks like the plan to release as 1.0 didn't work out. I anticipate a further minor release (0.11.0) before a 1.0 release. The changes between 0.11 and 1.0 should be minimal.


sgfutils: init at 0.25-unstable-2017-11-27

Description of changes
Adds sgfutils package - someone is writing a book with the help of this.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

note from the PR author: I checked the release notes checkboxes because each implication is vacuously true i.e. this change is just a leaf package, not a major or breaking change, and not a module

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

@ajs124 why did you mark the PR as draft this time?

Because for a split second a thought I cared about not having bad code and commits in nixpkgs, but then I remembered that I don't. Don't ping me again.

requesting a contributor to remove the above inappropriate, toxic comment along with this one. we don't need any of this.

Squashed and rebased on latest master.

The branch this PR will merge in to does not cleanly evaluate, and so this PR cannot be checked.

retriggering eval with a new force push

Thanks @ggPeti. Anyway to keep everyone happy I would suggest we also address this comment https://github.com/NixOS/nixpkgs/pull/271166#discussion_r1414506919
So my suggestion is:

Please move buildInputs following the suggestion
Squash commits in the PR to one again
I think we can merge this

I have a feeling that communication in this PR was not as smooth as I think all parties involved would hope for. This is my suggestion for best resolution.
Once this is done I will be happy to merge PR myself with peace in mind that no one has a reason to feel wronged in the process. I hope this is acceptable to everyone.

[x] Builds locally on linux x86_64
[x] Binaries run
[x] All review requests seems to be resolved


paralax broken and other issues when changing routes

so i was trying to use the parallax thingies in materialize css and i used this ad-don to add it, so i made a few routes and inside this template each had its own parallax thingies, i realized i needed to do some jquery initialization code and since all the initialization code was not included, i added it on the index.html file just to see if it would work,
well when the first browser request occurs, the parallax effect works awesome, when i change the route and go back..BOOM! the thing breaks and the pictures in parallax disappears, I'm left with a white screen, the web app is http://sabekconsulting.com/ its supposed to be an ember app and I'm working on it right now...its supposed to look like that
so my idea is to add all the jquery initialization code in one file  in master so the are added and initialized when the addon is installed...while you make the components just to help before all the components are complete...or a parallax component would be awesome...or maybe I'm doing it wrong..can you help?

How about trying to make a component for parallax that fits your project?  Perhaps get it working locally and contribute it after?  The initializers need to run in the view/component didInsertElement hook.

damn ive tried to get this thing working locally....lol, im realy new to making this stuff...have you tried @rynam0 ...on the parallax component?

No, not yet. I'm still working through the form components. Sadly, that one is pretty low on my list as I'd like to have the more commonly used components available first. After forms I was thinking of looking at dialogs/modals.  If I get a few moments maybe I'll do a quick spike for you.

Here's something to get you going, I hope.
// app/components/simple-parallax.js
import Ember from 'ember';

export default Ember.Component.extend({
  tagName: 'div',
  classNames: ['parallax-container'],
  didInsertElement: function() {
    this.$('.parallax').parallax();
  }
});

// app/templates/components/simple-parallax.hbs

// use it!
{{simple-parallax image="http://i.imgur.com/SrUhhev.png"}}

Yessir!

My really amazing content goes here...

{{simple-parallax image="http://i.imgur.com/bz8XHjr.jpg"}}

That seemed easy enough... guess i'll try to get this in soon.

:-) im still playing with this components stuff its totally awesome...ill have to contribute something soon...
so i gues we can close this...but wait till its into the live-demo  then i try it on my app

It's now live.


:left-space :keep doesn't work for comments

When using zprint-file-str, you can say {:parse {:left-space :keep}} in the options map in order to keep leading spaces in front of top level expressions.  However, at present, this doesn't work for comments, and it should.  The spaces are kept, but when wrapping comments they don't wrap soon enough, and the wrapped part does not have spaces.
(zprint-file-str "\n    (defn thisis [a] test)\n    ;def ghi jkl mno pqr\n" "junk" {:parse {:interpose nil :left-space :keep} :width 10})
"\n    (defn\n      thisis\n      [a]\n      test)\n    ;def ghi\n;jkl mno\n;pqr\n"
zprint.core=> (print *1)

    (defn
      thisis
      [a]
      test)
    ;def ghi
;jkl mno
;pqr

ghi should have wrapped, and ;jkl and ;pqr should have spaces before them.

Fixed in 1.0.0.


Add extra info for when scope is incoming-webhook

Slack just added a new scope that allows easy creation of incoming webhooks on authorization, this changes to the strategy allows it to return the new info slack provides to the client about the created webhook.

@kmrshntr I did a rebase with master to take your latests changes

@gssbzn You found such scope update well!
Thank you for promptly response and sorry for long delay to merge.

@kmrshntr no problem, glad to contribute to this gem. If you need help to maintain it hit me up


Request Error

Does this occur consistently?
Repro steps:

Action: appService.Restart
Error type: ECONNRESET
Error Message: request to https://management.azure.com/subscriptions/2febd4a0-1ac6-4466-85df-16246006a5e7/providers/Microsoft.Web/sites?api-version=2019-08-01 failed, reason: read ECONNRESET
Version: 0.20.0
OS: win32
OS Release: 10.0.21277
Product: Visual Studio Code
Product Version: 1.52.0
Language: en

Call Stack
ClientRequest.<anonymous> extension.js:236:264795
ClientRequest.emit events.js:228:7
TLSSocket.socketErrorListener _http_client.js:406:9
TLSSocket.emit events.js:223:5
emitErrorNT destroy.js:92:8
emitErrorAndCloseNT destroy.js:60:3
processTicksAndRejections task_queues.js:81:21

Please provide detailed repro steps.

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


[ENH] Investigate where mocking can be used in unit tests to improve flakiness, speed up test suite

Context
Currently there are many unit tests which are not very isolated. For example many tests reach out to conda-forge, and are therefore at risk of producing false failures for any number of network-related issues that are unrelated to the code being tested.
This issue is to plan and potentially track the work needed to mock out external dependencies, better isolating the unit tests to the code that we actually want to test.
One suggestion has been to run our own package repository locally, making it unnecessary for conda-store to make requests to conda-forge.
Value and/or benefit
The test suite is currently flaky. This should help reduce flakiness and has the potential to greatly speed up testing, as waiting on external resources takes a lot of time.
Anything else?
No response

Marking as in progress since @peytondmurray  is currently working on this

We've seen significant (>60%) reduction in test times from targeting a few key areas. We can always do better, but the slowness in testing that led to the creation of this issue has largely been resolved. For any flaky tests in the future, let's open a new issue.


MINOR: Code cleanup, subject: log statements.

I'm doing this in my spare time, so don't let reviewing this PR take away actual work time. This is just me going over the code with the Intellij analyzer and implementing the most easily implementable fixes.
This PR is focused only on seemingly erronous log statements.
1: A log statement that has 4 arguments supplied but only 3 {} statements
2: A log statement that checks is debug is enabled, but then logs on info level.

cc @dguy


Flask 2 incompatibility

I'm trying to test this with flask, but running into package compatibility issues.  Using Python 3.9.6, my requirements.txt is:
Flask
graphene
graphql-server[flask]

which ends up giving me:
$pip freeze
aniso8601==9.0.1
click==8.1.3
Flask==1.1.2
graphene==3.1.1
graphql-core==3.2.3
graphql-relay==3.2.0
graphql-server==3.0.0b5
itsdangerous==2.1.2
Jinja2==3.1.2
MarkupSafe==2.1.1
typing_extensions==4.4.0
Werkzeug==2.2.2

Trying to run my flask app results in
ImportError: cannot import name 'escape' from 'jinja2'

Trying to resolve that issue leads me to https://stackoverflow.com/questions/71718167/importerror-cannot-import-name-escape-from-jinja2:
Jinja is a dependency of Flask and Flask V1.X.X uses the escape module from Jinja, however recently support for the escape module was [dropped in newer versions of Jinja](https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-0).

To fix this issue, simply update to the newer version of Flask V2.X.X in your requirements.txt where Flask no longer uses the escape module from Jinja.

Flask==2.1.0
Also, do note that Flask V1.X.X is no longer supported by the team. If you want to continue to use this older version, [this Github issue may help.](https://github.com/pallets/flask/issues/4494)

Setting my requirements to:
Flask>=2.1.0
graphene
graphql-server[flask]

results in
pip freeze
aniso8601==9.0.1
click==8.1.3
Flask==2.2.2
graphene==3.1.1
graphql-core==3.2.3
graphql-relay==3.2.0
graphql-server==3.0.0b4
importlib-metadata==5.1.0
itsdangerous==2.1.2
Jinja2==3.1.2
MarkupSafe==2.1.1
typing-extensions==<IP_ADDRESS>
Werkzeug==2.2.2
zipp==3.11.0

then running my app results in
Traceback (most recent call last):
  File "main.py", line 3, in <module>
    from graphql_server.flask import GraphQLView
  File "env/lib/python3.9/site-packages/graphql_server/__init__.py", line 15, in <module>
    from graphql.error import format_error as format_error_default
ImportError: cannot import name 'format_error' from 'graphql.error'

Trying to resolve this brings me to https://github.com/graphql-python/graphql-server/issues/85, which says to upgrade to graphql-server 3.0.0b5, so I pin my requirements.txt and when I try to install, I get:
pip install -r requirements.txt
Requirement already satisfied: Flask>=2.1.0 in ./env/lib/python3.9/site-packages (from -r requirements.txt (line 1)) (2.2.2)
Requirement already satisfied: graphene in ./env/lib/python3.9/site-packages (from -r requirements.txt (line 2)) (3.1.1)
Collecting graphql-server[flask]==3.0.0b5
  Using cached graphql-server-3.0.0b5.tar.gz (45 kB)
Requirement already satisfied: graphql-core<3.3,>=3.2 in ./env/lib/python3.9/site-packages (from graphql-server[flask]==3.0.0b5->-r requirements.txt (line 3)) (3.2.3)
Collecting typing-extensions<5,>=4
  Using cached typing_extensions-4.4.0-py3-none-any.whl (26 kB)
ERROR: Cannot install Flask>=2.1.0 and graphql-server[flask]==3.0.0b5 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested Flask>=2.1.0
    graphql-server[flask] 3.0.0b5 depends on flask<2 and >=1

What do I do?  graphql-server should be updated to support flask v2 as flask v1 is no longer maintained.

also hitting this


Please consider using NVD for npm packages

If I understand correctly, Dependency Check uses only NSP for checking npm packages. The following command produces a report which refers only to advisories provided by Node Security Project:
${OWASP_DEPENDENCY_CHECK_HOME}/bin/dependency-check.sh --project myproject --out dependency-check --scan package.json
But if NSP analyzer is disabled, then you'll get an empty report:
${OWASP_DEPENDENCY_CHECK_HOME}/bin/dependency-check.sh --project myproject --out dependency-check --scan package.json --disableNSP
NVD contains CVEs reported against npm packages, for example:

https://nvd.nist.gov/vuln/detail/CVE-2018-3728
https://nodesecurity.io/advisories/566

This case is covered by the advisory from Node Security Project. But there may be issues which is not covered by Node Security Project. Furthermore, Node Security Project recently joined nmp, Inc. The advisories are still there, but I am not sure how Node Security Project is going to work in future.
It might make sense to update Dependency Check to be able to use NVD for checking npm packages.

it appears NSP was acquired by NPM, so we're getting a [ERROR] api.nodesecurity.io now in the logs.  Any ideas moving forward on what to use?

The NSP service appears to be working just fine. In fact, NPM (the company) has made no announcement they are changing it, rather incorporating the NSP service into the npm build tool itself. So instead of having to use npm to build and nsp to check, a single tool will do both + will have additional features (like audit) that currently doesn't exist.
Perhaps there's another issue folks are experiencing using NSP. I just tried scanning OWASP NodeGoat with Dependency-Check and ran nsp check and both work fine.

ATM we have no plans to use the NVD to analyze Node projects.  NPM is on top of things.  We have migrated to using the npm audit APIs.


Support for software update in azure iot python sdk

OS and version used: Ubuntu 16.04

Python runtime used: Python 3.8.7

SDK version used:

Description of the issue:

Support for software update in azure iot python sdk
Code sample exhibiting the issue:

Console log of the issue:

Hi Team,
I am working on software update using azure iot. I have found few links which talking about implementing this using azure iot node js sdk and azure iot c sdk as mentioned in below links
"https://github.com/Azure/azure-iot-sdk-c/tree/master/iothub_client/samples/iothub_client_sample_mqtt_dm/pi_device"
"https://docs.microsoft.com/en-us/azure/iot-hub/tutorial-firmware-update"
I havenot used much of C and node js. So I am actually looking for software update using python.
I havent find any link or tutorial which talks about implementing the software update using azure iot python sdk. Please let me know if there is any support/tutorial for software update using azure iot python sdk.

@cgoma there's nothing specially written on that topic using the Python SDK this being said the pattern (using the device twin) remains valid - it's only APIs that change.
The main sample file  shows how to use the device twin APIs.

closing after some inactivity - feel free to reopen if there are any more questions.

@cgoma, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey


Added support for including .css files

Hi. Not sure if you want to include css file support but we want to use your library in our Xerte Online Toolkits project and i've added css support with just minor change to your fantastic library.

Did you try this? Because this seems pretty useful.

The last commit on this repo is from Feb 18th. A while ago I forked/refactored this code to add support for onerror callbacks, CSS files and async:false. If this repo isn't being maintained anymore you're welcome to use my version:
https://github.com/muicss/loadjs

Oh that's neat.
On Thu, Oct 6, 2016, 12:17 AM Andres Morey<EMAIL_ADDRESS>wrote:

The last commit on this repo is from Feb 18th. A while ago I
forked/refactored this code to add support for onerror callbacks, CSS
files and async:false. If this repo isn't being maintained anymore you're
welcome to use my version:
https://github.com/muicss/loadjs
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ded/script.js/pull/97#issuecomment-251723187, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEikcEAxjGKiRR9DFeEKlIsWtwjykNeks5qw82EgaJpZM4IjGxq
.


[BEAM-7277] Add PostCommit test suite for Python 3.7

This is is part of a series of PRs with goal to make Apache Beam PY3 compatible. The proposal with the outlined approach has been documented here: https://s.apache.org/beam-python-3.
This PR adds a PostCommit test suite for Python  3.7.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

@tvalentyn Is this what you need? I am not familiar with gradle.

Run Python PostCommit

Run Python Dataflow ValidatesRunner

Also, we need to trigger these suites in a few places in this file:
https://github.com/apache/beam/blob/cbc2618895622ba5edc2b021b207c600e868871f/build.gradle#L201

Otherwise Jenkins does not trigger these suites, as we can see from current Postcommit test run on this PR.

Postcommit tests failed due to the error:
"09:10:20 root: INFO: 2019-05-13T16:02:15.972Z: JOB_MESSAGE_ERROR: Startup of the worker pool in zone us-central1-a failed to bring up any of the desired 1 workers. QUOTA_EXCEEDED: Quota 'DISKS_TOTAL_GB' exceeded.  Limit: 200000.0 in region us-central1.". This is an environmental issue, and I sent a request to get more quota.

Run Python PostCommit

There is an error:
12:01:44 Could not determine the dependencies of task ':python3PostCommit'.
12:01:44 > Task with path ':beam-sdks-python-test-suites-dataflow-py37:postCommitIT' not found in root project 'beam

Run Python PreCommit

@tvalentyn PTAL

Looks like there is a merge conflict, could you please rebase on top of master?

Once that's completed, please trigger the postcommit suite.

Run Python PostCommit

Run Python PostCommit

I got following error: Project with path ':beam-runners-google-cloud-dataflow-java-fn-api-worker' could not be found in project ':sdks:python:test-suites:dataflow:py37'.

Run Python PostCommit

There is still: ":sdks:python:test-suites:direct:py37:postCommitIT' not found in root project 'beam'."

Also please add the datastore test to the Direct runner suites on 3.6, 3.7. Thanks!

@pabloem could you please help with the merge? Thank you!


(QENG-5106) Add public key for always-be-scheduling

We need to add the public key for ABS to the authorized_keys file to allow puppet to connect to new EC2 instances allocated by ABS.

👍


Fix dispatch_request for Flask 1.1

Continues #50

Codecov Report

Merging #51 (2a98746) into master (12afbbf) will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##            master      #51      +/-   ##
===========================================
- Coverage   100.00%   99.87%   -0.13%
===========================================
  Files           14       14
  Lines          807      807
  Branches       147      147
===========================================
- Hits           807      806       -1
- Misses           0        1       +1

Impacted Files
Coverage Δ

apiflask/app.py
99.69% <0.00%> (-0.31%)
:arrow_down:

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 12afbbf...2a98746. Read the comment docs.


Refined Storage thinks that I have double of everything in my drawers when using two external storages busses

I had one external storage bus connected to a drawer controller from Storage Drawers, and everything worked fine. I connected another external storage bus to the same drawer controller—so that I could get more whitelist slots—but then my Refined Storage system started thinking that I had double of everything in my drawers. Rather than 25 ender lillies, for example, Refined Storage said that I had 50. When I took one ender lilly out, 48 were remaining, so I don’t actually had double of the items; Refined Storage just thought that I did.

Minecraft version: 1.10.2
Refined Storage version: 1.2.25 (latest for 1.10.2)
Storage Drawers version: 3.7.0 (latest for 1.10.2)
Forge version: <IP_ADDRESS>2 (latest for 1.10.2)

Why are you using a whitelist on the external storages? If the ender
lily is whitelisted on only one, it's still showing up as doubled inside
RS? I'd be unsurprised to see things doubled with a couple of
unconfigured external storages.

Why are you using a whitelist on the external storages?

I figured that I didn’t really need to, so I stopped doing that.

If the ender lily is whitelisted on only one, it's still showing up as doubled inside RS?

Yup.

I've found one way around this is to have the external interfaces in separate modes.  eg: interface 1 is in insert-only mode with a whitelist. Interface 2 is in insert-only mode with a separate whitelist.  interface 3 is in extract-only mode, no whitelist.  RS seems to only "see" the items once via the extract-only mode interface.
Also, it's easier to use a drawer key and lock the entire drawer grid.  You can allocate drawer slots by manually inserting an item then the slot becomes available to RS.
When expanding high priority drawer grids myself, I place the drawer on the ground, lock it, use packing tape on it then break it. When reattached to the drawer grid it'll remember the lock state and won't accidentally have items put in it that I didn't intend.

Also, it's easier to use a drawer key and lock the entire drawer grid. You can allocate drawer slots by manually inserting an item then the slot becomes available to RS.

Yeah, that’s what I started doing.

Note to self, this is caused by:

Having multiple of the same storages in the list
Having the detectChanges call in NetworkNodeExternalStorage#update which also calls it, even if it doesn't appear in the list

This is actually intended behavior. It doesn't cause any issues (no dupe bugs).
Also, if you set one of the external storage devices to insert only, the other to extract-only, you get the correct item counts.
It's the only way to get separate import/export priorities for external storage devices.


404 error when Pull to repo with 'pull requests' disabled

Description
When we fork repo - forked repo is created with 'pull request' repo setting enabled. Old repo 'pull request' setting is left untouched. When we trying to create pull request from new repo to old repo we receive 404 'Not found' error if 'pull request' setting is disabled in old repo settings. More informative message is needed, or (more better) only repos with 'pull requests' enabled should shown in 'merge into' drop-down list.
Gitea Version
1.19.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
No response
Operating System
Flatcar
How are you running Gitea?
Kubernetes helm-chart on k3s running on flatcar linux.
Database
PostgreSQL

This may be even better (but I think that fork button should be shown anyway, but either in 'grayed' state - to show end-user that functionality is there but disabled or in 'normal' state with warning that 'you should enable PR on this repo beforehand.

So should we allow repo to be forked if pull request siabled? 🤔

Absolutely not. Not all forks are for the purpose as a sourcs of pull requests, they might become separate projects etc.


Dice Game files

Description 📜
A new project added.
Fixes #296

Type of change 📝
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[X] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[X] Project using only HTML & CSS
[X] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸
Add the screenshot of the changes you have made

@khushi-purwar @meinhoonharsh can you check if anything is needed???


Obfuscate encoded Versions and Timestamps; there are too many 0s in IDs

With the current way that version numbers and timestamps are encoded, there could be a ton of 0s in the ID compared to how many 1s are present since the ID and timestamps are encoded as they are represented in binary.
I have thought about this for a while and have come to the conclusion that it might be best to use an additional Mac instance. This implementation will depend on the utils provided in #7. The procedure will be like so:

MasterKeyGenerator has an additional "static" Mac member (its key never changes).
ID is generated as [Prefix][RandomBytes][empty mac slice]
The first 2 bits of metadata are encoded (the two bools)
Call insert_ints_into_slice(), preserving those two bools, overwriting all remaining space that will be taking up TIMESTAMP_BITS + VERSION_BITS with 0s
Compute the "static" mac
XOR the version with the first 4 bytes of the mac as a u32
XOR the timestamp with the next 8 bytes of the mac as a u64
Call insert_ints_into_slice() to insert these values into the ID

By keeping this MAC's key static, different versions and timestamps will be readable, while this section of the ID will always look different (except for the two bools). The MAC and its key do not need to be super secure, as it is primarily just to have some more random-looking IDs. The only requirement for the MAC is that it must be able to output 12 bytes.

It has been fixed. It uses the KeyGenerator's MAC, and for key and ID generation, a unique version salt is used.


Slider Image width is cut

in slider image is not display full inside the slider ,i think it has not full width of the image

for this issue assigned me @MAVRICK-1

@Varsani2520 it's responsive refresh the page


[Ballerina HATEOAS to OAS] Resolve merge conflicts with restructuring branch

Description:
After recent changes in the response mapper as an effect of restructuring Ballerina to OAS module, there are major merge conflicts with the restructuring branch and the hateoas support branch. In order to resolve these conflicts, logic in the hateoas mapping should be changed..
#1589

Closing this issue since this work has been completed!


feat: upgrade ray -> 2.7

Summary

was testing #713 which upgrades to 2.5. for some reason the head node was constantly restarting. i pulled the branch in my fork and bumped it to 2.7 and tested in an aws cluster. head node is stable, and ran some cursory tests that all worked.
Test Plan

tested on aws cluster

Checklist

[x]  No images hosted from dockerhub
[ ]  Are dashboards present to understand the health of the application.  There must be at least 1 of these

[ ]  all databases should have dashboards
[ ]  ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
[ ]  you can use plural from-grafana to convert a grafana dashboard found via google to our CRD

[ ]  Are scaling runbooks present

[ ]  all databases must have scaling runbooks
[ ]  you can use the charts in pluralsh/module-library to accelerate this

[ ]  do you need to add config overlays?

[ ]  inputing secrets
[ ]  configuring autoscaling

[ ]  If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
[ ]  All major clouds must be supported

[ ]  Azure
[x]  AWS
[ ]  GCP

after more extensive testing, there might some issues. it won't let me make this a draft though

Potential issues after more stringent testing

hey @troyyyang is there a reason this is still a draft PR?  Let us know when it's ready to test on our end and we can get it merged.

hey @troyyyang is there a reason this is still a draft PR? Let us know when it's ready to test on our end and we can get it merged.

let me know what i should do with the appversion, but otherwise all set


Subset from conditional coordinates

Description
Maybe this functionality already exists in some way, but I haven't seen an obvious way to do it.
Frequently I want to retrieve a subset of a dataset where I don't know exactly the index.  For example if I have two coordinates x and y, I want to provide conditions like x< 100 & x>3, y >=2.  Some functions like this exist in the Dplyr package in r using the filter function (e.x. filter(ds, x>= 100 | x <-1). Is such a thing possible using a function in xarray or must I build the boolean index myself using something like  ds[np.meshgrid(ds.x < 100 , ds.y>5)]?
Notice the desired functionality is a lot like xr.where except the conditions are on the coordinates and instead of returning a mask, the function should return a smaller dataframe, if possible.
ds = xr.Dataset({'foo': (('x', 'y'), np.random.rand(4, 4))},
                    coords={'x': [10, 20, 30, 40],
                           'y': [30, 40, 50, 60]})
ds.isel((ds.y>=30) & (ds.y <=50)) #doesn't work, desired functionality

Expected Output
xr.Dataset({'foo': (('x', 'y'), np.random.rand(4, 3))},
                    coords={'x': [10, 20, 30, 40],
                           'y': [30, 40, 50]})

Does the drop argument on the .where() method satisfy your needs? For example,
ds.where((ds.y >= 30) & (ds.y <= 50), drop=True)

reduces the shape of the foo variable to (4, 3), as desired.

Sounds like this is what I’m looking for, I’ll try it out soon thank you! I wasn’t aware that where had a drop option

@jthielen is there a better place to ask these questions in the future?  I like the the package quite a bit, but sometimes I struggle to answer basic questions like this from the documentation alone (ex: this page could maybe use a few words explaining the examples). On the other hand I asked here because I wasn't sure how much traction my question would get on stack exchange.

take a look at https://xarray.pydata.org/en/stable/#get-in-touch where a few options are listed. I'm not a active user of SO / SE so I can't comment on that, but I think it is fine to ask questions like this one using the issue tracker.
Also, thanks for reaching out about the examples. I agree we should have descriptions on what each of them is trying to achieve, and we should also think about linking to the relevant section in the narrative documentation. In this case, that would be https://xarray.pydata.org/en/stable/indexing.html#masking-with-where

we could also add something here: https://xarray.pydata.org/en/stable/howdoi.html

Very helpful resources, thank you all!


Worker error handling

This is a first step in addressing issues like #1035
It tries to formalize worker error handling a bit and move it outside of Strategy for now. The basic idea is that, for efficiency reasons, executors and their provider are polled regularly, based on custom poll intervals, to get the status of all workers managed by the executor. This information is then forwarded to an error handler and, possibly, to the strategy. The error handler checks for problematic situations and informs the executor when such situations are encountered. It is also possible for the executor to implement a custom error handling check.
Part of the solution involves a bit of scaffolding to better keep track of and propagate errors from providers. The exact details of how providers implement error propagation is only addressed for the local provider with a local channel. More work is needed on having all providers properly address errors in the jobs they launch.

Just FYI, I would like to update this PR with a couple of things mentioned by Ben as well as addressing a number of issues raised by mypy. It will not fundamentally change the structure of the solution, so feel free to review this for now.

Well?

One thing I'm not clear of at the moment is how this will capture (or if it is even intended to capture, at the moment) batch jobs failing to launch workers: with unix process launches, there is a useful exit code which is used to set JobStatus.FAILED. With other more asynchronous stuff, I'm less clear what should happen.

One thing I'm not clear of at the moment is how this will capture (or if it is even intended to capture, at the moment) batch jobs failing to launch workers: with unix process launches, there is a useful exit code which is used to set JobStatus.FAILED. With other more asynchronous stuff, I'm less clear what should happen.

Your comment is hard to parse. I have made a comment when I submitted this PR that this is the infrastructure and only local/localchannel implements all the necessary bits. Batch jobs failing when launched from whatnot would need all the whatnots to have some means of propagating errors. This PR has some changes to the bash launcher used by local/localchannel, so there's a little bit of updates in one whatnot.
In other words, there is no magic. The hard work needs to be done. Or not, and we can just let it hang.

@benclifford, do you mind going through conversations and resolving if needed for merging and addressed?

@benclifford, do you mind going through conversations and resolving if needed for merging and addressed?

sure - I've already indicated which pieces should be merged already as separate PRs though.

@benclifford, do you mind going through conversations and resolving if needed for merging and addressed?

sure - I've already indicated which pieces should be merged already as separate PRs though.

I always appreciated the direct nature of your statements. What you are doing here is the opposite. If you think this PR is unmergeable, please state so.

It's got too much going on for me to coherently review without splitting it up, so you're going to have to wait a lot longer for an approving review if you wait for me to split it up.

It's got too much going on for me to coherently review without splitting it up, so you're going to have to wait a lot longer for an approving review if you wait for me to split it up.

Ok, so you mentioned two separate PRs: JobState and ControlNoFlow. You are saying I should manually extract all the changes related to those issues and create two separate branches and PRs. Presumably those would be merged quickly, after which I should manually resolve conflicts in this branch. And that you believe this work would significantly reduce the time it would take you to review the remaining changes. Is this correct?

yes

yes

OK

After banging my head against stuff, it looks like what you suggest would involve significantly more work than mentally separating things and would be quite error prone. It would essentially require rewriting the whole code in this PR such that the above commits end up in a particular order. For example, all executors use JobStatus in methods that have been moved to an abstract class. Going back requires plugging the JobStatus stuff into every executor. It would, if I started entirely from scratch, require more work than I spent on this PR because many of those things got abstracted concurrently, without me changing them first to use the new class.
In addition, both the suggested separate PRs are conceptually trivial and do not make much sense by themselves.
So I would rather not invest significant time into something that is likely to be broken and mostly useless. If you would like, let me know when you have some time and we can skype/etc. and go through each change and discuss. I can than identify for you whether a particular change would have belonged in one of these hypothetical separate PRs.

I think parsl/providers/ad_hoc/ad_hoc.py:AdHocProvider use JobState/JobStatus?

I started unpicking this into a sequence of commits that I'm more happy reviewing with but that ends up with bitwise identical to this source tree. That will probably lead to more review comments as I pay closer attention. I'll push up the commit series to a branch in a day or so when I've made my full first pass.

I think parsl/providers/ad_hoc/ad_hoc.py:AdHocProvider use JobState/JobStatus?

True, true; 95e0159

@hategan How much of the PR is yet to be sliced and merged to master ? Just checking if there's value in keeping this around.

Not all of it is merged. I don't think it matters how much beyond that.


[question] move configuration and data directory for macOS

I'd really like to see the configuration and data directory for macOS moved from ~/Library/Application Support/watson/ to ~/.config/watson/, just as it is in Linux.

This is the default Click behaviour. IMO it's consistent to stick to the system's standard.

This is the default Click behaviour. IMO it's consistent to stick to the system's standard.

I think it would be great if you could specify the data directory because then you would be able to easily push everything to a remote git repo.

I think it would be great if you could specify the data directory because then you would be able to easily push everything to a remote git repo.

The application folder is configurable by defining the $WATSON_DIR environment variable (see https://tailordev.github.io/Watson/user-guide/configuration/#application-folder).

The application folder is configurable by defining the $WATSON_DIR environment variable (see https://tailordev.github.io/Watson/user-guide/configuration/#application-folder).

Thanks, I didn’t know this option existed.

Thanks, I didn’t know this option existed.


Feature Request: addColumn at specific index

Hi i think this can be useful for many reasons. Thanks!!

@risenW Thank you.
I think it would be nice to choose wich columns of the dataframe you want to plot as a table.
Example of desired use:
    let columnsArr =  ["column_name","another_column_name"];
    df.plot("plot_div").table(columnsArr);

If the column param is undefined it will work as always.
I thought maybe this is already possible so also tried doing this but it doesnt works:
    let columnsArr =  ["column_name","another_column_name"];
    let config = {header: { values: columnsArr}}
    df.plot("plot_div").table(config);

If you think it would be usefull or not, i'll be more than honoured to contribute in this project, with this or any other issue.
Just let me know :)


update link for options in README.md

Friendly Ping !!

Ping

Ping again !!

@gnyani change it in .verb.md. All mine, @jonschlinkert and @doowb READMEs are generated by Verb (dev, the dev branch) and using .verb.md as a template files.

No problem will close for now.


Stuck at Writting password... for 2 days

Before submitting a bug report...

[X] This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

[X] The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
tittle, everything was working properly until yesterday
Copy and paste your error
2023-10-23 13:16:56,092 [INFO] Using default request storage
2023-10-23 13:16:56,107 [INFO] Created proxy listening on <IP_ADDRESS>:50356
2023-10-23 13:16:56,108 [INFO] Using undetected_chromedriver
2023-10-23 13:16:56,647 [INFO] patching driver executable C:\Users\green\appdata\roaming\undetected_chromedriver\undetected_chromedriver.exe
2023-10-23 13:16:57,812 [INFO] Screen size: 1431x1180
2023-10-23 13:16:57,812 [INFO] Device size: 1376x1029
2023-10-23 13:16:57,832 [INFO] [LOGIN] Logging-in...
2023-10-23 13:17:00,874 [INFO] [LOGIN] Writing email...
2023-10-23 13:17:02,524 [INFO] [LOGIN] Writing password...
Screenshots

Value of dashboard variable
https://gist.github.com/Greendrift/8a7cebbe61cce4c5b04e54ac4fda5d81

This happens to me sometimes, I just Ctrl-C, kill any remaining chrome processes and then start the script again, usually completes the second time through. Rarely I have to do it again after that.

If you run using "-v" argument, you gonna see "https://login.live.com/" it's not loading. It looks a MS Problem. It's happening now for me

It's also happening off and on to me too days at a time login.live.com will just hang after the writing password or after the logging in stage (does it in normal chrome too)
Other links like login.microsoft.com etc. continue to work, is it possible anyone in the know can modify the bot with alternative login URL's given this seems to be a common issue?

I was able to fix this for myself by making some edits to src/login.py. I noticed that when I ran the script with the -v option it was successfully logging in with my username and password but then stalling when it loaded https://rewards.bing.com/. All I did was change the hostname check on line 73 in src/login.py from
== "account.microsoft.com" to in ("account.microsoft.com", "rewards.bing.com").
This caused the call to self.utils.waitUntilVisible on line 78 to fail but I just replaced it with time.sleep(10) since it times out after 10 seconds anyway. Definitely a quick and dirty fix but it seems to do the job.

I was able to fix this for myself by making some edits to src/login.py. I noticed that when I ran the script with the -v option it was successfully logging in with my username and password but then stalling when it loaded https://rewards.bing.com/. All I did was change the hostname check on line 73 in src/login.py from == "account.microsoft.com" to in ("account.microsoft.com", "rewards.bing.com").
This caused the call to self.utils.waitUntilVisible on line 78 to fail but I just replaced it with time.sleep(10) since it times out after 10 seconds anyway. Definitely a quick and dirty fix but it seems to do the job.

May you share your full code of src/login.py- cant reproduce it at my side. Thanks

I was able to fix this for myself by making some edits to src/login.py. I noticed that when I ran the script with the -v option it was successfully logging in with my username and password but then stalling when it loaded https://rewards.bing.com/. All I did was change the hostname check on line 73 in src/login.py from == "account.microsoft.com" to in ("account.microsoft.com", "rewards.bing.com").
This caused the call to self.utils.waitUntilVisible on line 78 to fail but I just replaced it with time.sleep(10) since it times out after 10 seconds anyway. Definitely a quick and dirty fix but it seems to do the job.

May you share your full code of src/login.py- cant reproduce it at my side. Thanks

yes 2nd that as I'm getting the failed when trying to login at certain runs
please share your login.py file

@Natriumpikant @icescoop12
I created a pull request for klept0's fork: https://github.com/klept0/MS-Rewards-Farmer/pull/42. You can either implement those changes yourself or wait until he confirms them.
If you're still having issues I'd recommend killing chrome and deleting the contents of the session folder before each run.

Mine gets stuck loading after "Stay signed in?". Tried killing chrome and deleting session folder.


fix: use proxy env variables and abort-controller package to prevent hanging behind proxies

What/Why/How?
While working behind proxy,  HTTP_PROXY or HTTPS_PROXY environment variables might be used to detect this and skip  unnecessary http calls.
Also, added abort-controller package to ensure consistent usage throughout different nodeJS versions.
Reference
Related to https://github.com/Redocly/redocly-cli/issues/1146
Testing
IN PROGRESS. Trying to replicate the original issue...
Screenshots (optional)
Check yourself

[x] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[x] All new/updated code is covered with tests

Security

[x] Security impact of change has been considered
[x] Code follows company security practices and guidelines

I'm closing this as we're not actively working on it. If we get more replication cases, we should revisit.


Is there a way to play pandemonium event with this?

sorry if asking this in here is wrong.

Yes you can just add 3 of each key.. to your inventory and kill the bosses  or skip that part completly and just add in the parts you get from doing the keys..
here you have all you need including their value so you can easly import them
1 of each key in cube.. open all 3 portals in same game
3x Key of Destruction (Sk0QAIAAZQAEArc2A4L8EpSBr+A/)
3x Key of Terror (Sk0QAIAAZQAGArcWAwKxk0YMqeA/)
3x Key of Hate (Sk0QAIAAZQAEArcmAwLI3VgNqOA/)
in cube this will get you into uber tristram directly...
1x Mephisto's Brain (Sk0QIKAAZABA0iYmBwI=)
1x Baal's Eye (Sk0QIKAAZAAgIlaWBwI=)
1x Diablo's Horn (Sk0QIKAAZAAAQobmBgI=)


Enable HdfsClientTest

Also the main(): part is not superseded by whatever things we have, in
form of tox and stuff. For instance you can run
export TOX_ENV=hdp; export PYTHONPATH='';
JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64 tox -e $TOX_ENV
test/hdfs_test.py:AtomicHdfsOutputPipeTests.test_atomicity

To run a single test.

Coverage increased (+0.42%) to 76.31% when pulling aaf3260e210d90faf1a423d149775e52afc966be on Tarrasch:enable_HdfsClientTest into d2352682d09f0cc0216520324bfc20b218965a7c on spotify:master.

Coverage increased (+0.57%) to 76.45% when pulling 236001b99839755682250c1cceffa687b7c8701d on Tarrasch:enable_HdfsClientTest into d2352682d09f0cc0216520324bfc20b218965a7c on spotify:master.

Ah now I see what you mean Erik. Yea this PR is really green but shows red because of OTHER pep8 failures.
I'll let you merge if this patch looks sane to you @erikbern

Review please? :)


2x Grid Align left, center, right

Summary
@mjabbink requested we add an option to left align, or center the grid. This sounds like it's helpful in situations in like Gatsby where the max-width is still applied, but the grid is left aligned. Probably need right aligned as well for RTL languages I would imagine.
Might be able to simply remove margin-right, or margin-left on bx-dev--grid. Only issue to keep in mind is the opposite influencer stops working when done this way. We can explore ways to keep them working, or find a new solution though if that's a deal breaker.

Planned for release 2.6.0!

nice work!


ask Testers to provide their spec samples for metacore development

DoD:
collect specifications from companies to explore if different formats might create a road block in using metacore

Has this happened? Was there feedback from the tester are the readers?


[ProxyBridge] Add new Bridge

With this Bridge, you can Read RSS Feeds, cache them for one hour and translate between outputs.
I used #1385 as a template
Preview: https://dhusch.de/rss-bridge/#bridge-Proxy

What is the purpose of this bridge?

For readers that only support Atom for example.
So you can translate from Mrss to Atom
Or to Json, for Applications for example.
Or you can use it as an reader.

I understand. Maybe a better name such as FormatExpanderBridge?

Or maybe BridgeTransformerBridge?

Now that I've looked at it (and renamed it), I have a question: What is the difference to the FilterBridge without filters?
Isn't that doing basically the same? You can insert a feed (filter on it if you want, or not) and then you can use the different formats of the filterbridge to use the feed.
It even also has 1 hour of cache.
Is this bridge still neccessarry with that information @dhuschde ?

Filter bridge can be used for this indeed.


genesis/origin does not have a slot number

pointSlot now has type Point block ->WithOrigin SlotNo. There is no slot for the origin/genesis point.

@mrBliss I've just pushed a commit that makes ouroboros-consensus build and tests pass, but I may have done some dodgy things so please review and change.

Can you do the same thing for BlockNo? Because we need BlockNo 0 for the genesis EBB, so the empty chain should have no BlockNo at all (i.e., Origin).

Giving BlockNo 0 for the empty chain may be right. It's basically the length of the chain, so 0 makes sense. Also, in cardano-sl, the genesis block has BlockNo 0, and every EBB has the same BlockNo as its parent block, so there's precedent.

Can you do the same thing for BlockNo? Because we need BlockNo 0 for the genesis EBB, so the empty chain should have no BlockNo at all (i.e., Origin).

Giving BlockNo 0 for the empty chain may be right. It's basically the length of the chain, so 0 makes sense. Also, in cardano-sl, the genesis block has BlockNo 0, and every EBB has the same BlockNo as its parent block, so there's precedent.

With genesis block, you mean the very first EBB (and thus "thing" on the chain), right? (I call it the genesis EBB)
An argument for WithOrigin BlockNo: during chain selection, we use the BlockNo of the tip of a chain(fragment) as a proxy for the length of the corresponding chain (because we're dealing with fragments, we can't use the fragment length). When we're given the choice between an empty chain (blockNo = Origin) and one containing only the genesis EBB (blockNo = At (BlockNo 0)), we should prefer the latter.

@mrBliss I agree that the empty chain should have no BlockNo. Then chain length can be defined as
chainLength :: HasHeader block => Chain block -> Word64
chainLength = maybe 0 (succ . unBlockNo) . headBlockNo

which corresponds to the actual chain length, for valid chains.
I went ahead and tried to do this but there is too much affected, including the ChainDB, so I gave up. Perhaps you should try?

@mrBliss I agree that the empty chain should have no BlockNo. Then chain length can be defined as
chainLength :: HasHeader block => Chain block -> Word64
chainLength = maybe 0 (succ . unBlockNo) . headBlockNo

which corresponds to the actual chain length, for valid chains.
I went ahead and tried to do this but there is too much affected, including the ChainDB, so I gave up. Perhaps you should try?

I'll give it a try.

@mrBliss I agree that the empty chain should have no BlockNo. Then chain length can be defined as
chainLength :: HasHeader block => Chain block -> Word64
chainLength = maybe 0 (succ . unBlockNo) . headBlockNo

which corresponds to the actual chain length, for valid chains.
I went ahead and tried to do this but there is too much affected, including the ChainDB, so I gave up. Perhaps you should try?

I'll give it a try.

I have a branch for this: https://github.com/input-output-hk/ouroboros-network/tree/mrBliss/point_blockno
But after talking with Duncan and Nick, I'm no longer convinced it is really needed.
The main advantage of WithOrigin BlockNo was the ability to distinguish an empty chain (Origin) from a chain containing just the genesis EBB (At (BlockNo 0)). This is handy because we use the block number as a proxy for the chain length. However, as you say, all other EBBs will have the same BlockNo as the block before them. So this advantage is only true for the single edge case.
And quoting Duncan:

I think we generally don't need to worry too much about block number vs chain length.

When we're doing chain selection when we're syncing from the old part of the chain that has EBBs, then every time we find an EBB we will shortly find another block after it. So even if it means we don't immediately select a chain that has just one more block that is an EBB, we will select it as soon as it has an EBB + 1 block.

bors r+


A Hotel Booking Web Application

This is a basic hotel booking web application created using HTML, Tailwind CSS and JavaScript.

A hotel booking web application.


Cannot find module 'fs-jetpack' with prisma 3.8.0

Bug description
In my jest tests, I run prisma/migrate programmatically to apply migrations at the beginning of each test suite. Since v3.8.0 I get the following error:
Error: Jest: Got error running globalSetup - [...]/tests/setup.ts, reason: Cannot find module 'fs-jetpack'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- [...]/tests/setup.ts
- [...]/node_modules/jest-util/build/requireOrImportModule.js
- [...]/node_modules/jest-util/build/index.js
- [...]/node_modules/jest-config/build/getCacheDirectory.js
- [...]/node_modules/jest-config/build/Defaults.js
- [...]/node_modules/jest-config/build/normalize.js
- [...]/node_modules/jest-config/build/index.js
- [...]/node_modules/jest-cli/build/init/index.js
- [...]/node_modules/jest-cli/build/cli/index.js
- [...]/node_modules/jest-cli/bin/jest.js
- [...]/node_modules/jest/bin/jest.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:941:15)
    at Function.Module._load (node:internal/modules/cjs/loader:774:27)
    at Module.require (node:internal/modules/cjs/loader:1013:19)
    at require (node:internal/modules/cjs/helpers:93:18)
    at Object.<anonymous> ([...]/node_modules/@prisma/sdk/dist/utils/jestContext.js:30:36)
    at Module._compile (node:internal/modules/cjs/loader:1109:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
    at Object.newLoader ([...]/node_modules/pirates/lib/index.js:141:7)
    at Module.load (node:internal/modules/cjs/loader:989:32)
    at Function.Module._load (node:internal/modules/cjs/loader:829:14)

Weird thing is that fs-jetpack doesn't seem to be installed properly...
cat<EMAIL_ADDRESS>| grep "fs-jetpack"
    "fs-jetpack": "4.3.0",

but then
npm ls fs-jetpack
<EMAIL_ADDRESS>[...]
└── (empty)

How to reproduce
import { Migrate } from "@prisma/migrate";

/** RUN MIGRATIONS */
const mig = new Migrate();
await mig.applyMigrations();
mig.stop();

Expected behavior
No response
Prisma information
all prisma packages @ v3.8.0
Environment & setup

OS: mac os, mac M1
Database: PostgreSQL
Node.js version: v16.1.0

Prisma Version
prisma                  : 3.8.0
@prisma/client          : 3.8.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Default Engines Hash    : 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f
Studio                  : 0.452.0
Preview Features        : interactiveTransactions

@janpio FYI the @prisma/sdk package also has a dependency on fs-jetpack which also fails to add it to my dependency tree

Hi @paulrostorp
So the @prisma/migrate is not part of the public API, and it looks like we indeed have this problem with 3.8.0
It's already fixed with https://github.com/prisma/prisma/pull/11111 in our dev package version 3.9.0-dev.6 , though it's not recommended for production use.
The next official release 3.9.0 will contain the fix.
Note: the feature request about a programmatic API is https://github.com/prisma/prisma/issues/4703

ah of course, it was a dev dependency on 3.8. Sounds great, I'll close the issue then

Note, actually a fix was shipped in 3.8.1 about this.


[WIP] fix user specified JSON metadata not updating dashboard on refresh

Issue referenced
This PR aims to fix a bug which prevented a user from overriding chart colors by editing dashboard JSON Metadata. User received an error when clicking Save in the Edit Dashboard screen which prevented users from adding user defined chart colors.

Codecov Report

Merging #7027 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #7027      +/-   ##
==========================================
- Coverage   64.45%   64.45%   -0.01%
==========================================
  Files         421      421
  Lines       20523    20524       +1
  Branches     2245     2245
==========================================
  Hits        13229    13229
- Misses       7167     7168       +1
  Partials      127      127

Impacted Files
Coverage Δ

superset/views/core.py
74.89% <0%> (-0.06%)
:arrow_down:

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 05be866...6bc5120. Read the comment docs.


Reset file input if image-pdf warning appears

If the uploaded PDF is image-only, the file upload box should be cleared.

Ah good catch.
Jeremy B. Merrill
Sent from my mobile device
On May 2, 2015 6:52 PM, "Manuel Aristarán"<EMAIL_ADDRESS>wrote:

[image: screen shot 2015-05-02 at 6 50 56 pm]
https://cloud.githubusercontent.com/assets/27584/7443038/5b8c8d20-f0fc-11e4-94a9-5a2a18ee3d59.png
If the uploaded PDF is image-only, the file upload box should be cleared.
—
Reply to this email directly or view it on GitHub
https://github.com/tabulapdf/tabula/issues/326.

close din a774ebe


Fixed #826

test_blockGenerator should only check if the block is generated within
the slot; in 'IO' use small integers for slot length (in seconds).

bors r+

bors r+


Changes to upload the sticky header library to a local repository

Description
Forked a sticky header view project and made changes to deploy the library to artifactory
/cc @grahamcruse
Risks
Low
References
https://zendesk.atlassian.net/browse/MCA-284

👍


Nest UI and API service at the same path?

Sorry if this is simple, but I'm wondering if it is possible to create an API with the following route structure:
/ => OpenAPI Swagger UI
/whatever => API business logic endpoint(s)
I have a minimal example here.
The behavior in the linked project is that the /info route works, but / is not found.
The desired behavior is that the two routes can co-exist, since none of the paths truly conflict.
I've tried multiple combinations of nest/at, but I can't find a way to get both services to share a root path. I don't want to prepend all my paths with /api or view my UI at /ui.
Thanks!

Ugly, but works. 🙂
  let api_service = OpenApiService::new(Api, "Example API", "1.0");
    let ui = Arc::new(api_service.swagger_ui().map_to_response());

    let api_service_ep = Arc::new(api_service.into_endpoint().map_to_response());
    let handler = poem::endpoint::make(move |req| {
        let ui = ui.clone();
        let api_service_ep = api_service_ep.clone();
        async move {
            if req.uri().path() == "/" && req.method() == Method::GET {
                ui.call(req).await
            } else {
                api_service_ep.call(req).await
            }
        }
    });

    let app = Route::new().nest("/", handler);


Update german flag with the right yellow color

see https://en.wikipedia.org/wiki/Flag_of_Germany

Dankeschön!


Function Role with aws-cli

Hi there,
is there a way to use the role as credentials of the aws-cli?
I'd like to avoid to write secrets in my code. If not, what is the best way to write the .aws/credentials file?
Thanks

Sorry my mistake.


[doc][feat] add docs for broker load balancer

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
Need to add docs for https://github.com/apache/pulsar/issues/16691
What is your suggestion?
See comments below
Any reference?
N/A
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Doc architecture: https://xmind.app/m/4XBe9w
TO-DO tasks:

[ ] Restructure the IA

Consolidate existing docs
Add missing contents

[ ] Add conceptual topics

[x] 1st version - Done by 6/8
[ ] 2nd version - WIP (iterate based on suggestions from @Demogorgon314 and @heesung-sn

[ ] Add reference topics
[ ] Add task topics


Allow building with a user-supplied libssh2

Some projects[1] may want to provide their own libssh2.  This change
allows the project to supply its own libssh2 via a LIBSSH2_DIR
environment variable.
[1] One such project is cargo raze
which provides automation for building cargo dependencies into projects
built with bazel.
Signed-off-by: Chris Frantz<EMAIL_ADDRESS>

Isn't this already implemented with LIBSSH2_SYS_USE_PKG_CONFIG + setting PKG_CONFIG_PATH appropriately to point at your own libssh2?  That worked for me for antioxidant-build-system [1]
[1] https://notabug.org/maximed/cargoless-rust-experiments/

Doesn't println!("cargo:rerun-if-env-changed={}", varname); need to be moved outside the conditional?
In case that previously it isn't set, but later it is?

Isn't this already implemented with LIBSSH2_SYS_USE_PKG_CONFIG + setting PKG_CONFIG_PATH appropriately to point at your own libssh2? That worked for me for antioxidant-build-system [1]

Yes, it is -- a fact I discovered late last week.  I had not gotten around to withdrawing this PR.


Content-type header passed in GET request

The get request coming from the library when I get items from the Kentico Cloud Delivery client is sending a content-type header in GET requests.
Content-type describes the type of the request body. GET requests don't have a body and therefore it shouldn't have a content-type header.
We use the Kentico Cloud delivery client inside a WAF and every get request is triggering an alarm so please remove it from the get requests coming from the library.
Thanks

Hi,
I've just checked this and content-type request header is not actually being send in Delivery API when the request body is empty. The request headers I get when calling items() endpoint are (on the latest beta 6.0.0-beta.10 version)
Host: deliver.kenticocloud.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
Accept: application/json, text/plain, */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
X-KC-SDKID: npmjs.com;kentico-cloud-delivery;6.0.0-beta.10
Origin: null
Connection: keep-alive
Cache-Control: max-age=0

The http client we are using (axios) automatically removes content-type header when the body is empty.
Can you elaborate a bit more on when and where you see the header being sent?

We're seeing this when running it from node. Is that from a browser request?

I've released new beta version for delivery 6.0.0-beta.11 (https://www.npmjs.com/package/kentico-cloud-delivery/v/6.0.0-beta.11) which should no longer send Content-Type headers under node.
Could you please try this version and let me know?

Did you had a chance to test this with the new release?

I'm using version 5.7.2. When I update to version 6.0.0 there are a lot of breaking change (I guess hence the increase in major version number). Is there any chance to get this change in version 5.7.X?
Thanks,
Darren

Unfortunately I can't do a new release for 5.x.y, but if I can I would recommend you to give it a try with the 6.0.0-beta.11 as there are not that many changes yet. If I recall correctly, you could fix majority (if not all) issues by replacing
.getObservable or .getPromise with .toObservable or .toPromise.
There is also a change in linkedItems property so that it is no longer an array, but chances are you are not using this property at all.
There will be quite a lot new changes in the upcoming release though (as you can probably see in commits already)

Unfortunately, the security team in my client will not allow me to use a beta release.
I'll have to wait for the stable release.
I'll add a custom httpService for the time being and remove that default content-type on get requests.
Thanks for your help,
Darren

Ah, okay, thank you for letting me know.
The only reason it is in beta release is that it contains breaking changes and we have to coordinate release with documentation team & update docs across our portals. Otherwise, the beta version I mentioned is more stable, has some bug fixes from v5 and contains more tests.
Our plan is to release v6 around the beginning of August.


What's differences between mustSchedule() and schedule() methods?

mustSchedule()
Attempts to schedule the provided Job, throws an exception if it fails. (ScheduleFailedException)

schedule()
Attempts to schedule the provided Job. Returns one of the (int value) SCHEDULE_RESULT_SUCCESS,
SCHEDULE_RESULT_UNKNOWN_ERROR, SCHEDULE_RESULT_NO_DRIVER_AVAILABLE,
SCHEDULE_RESULT_UNSUPPORTED_TRIGGER, SCHEDULE_RESULT_BAD_SERVICE

Thanks @kaiwalyakhasnis. That's correct. mustSchedule returns void and throws an exception if the schedule request fails, whereas schedule() returns an int status code that indicates whether the request was successful.


Little reusability for arithmetic/logic instructions due to type families

The following PR illustrates this issue: https://github.com/emmanueljs1/lambdaboy/pull/2

Solution: https://github.com/emmanueljs1/lambdaboy/commit/015051cdecd5487af2f9325013a1dc58c738d742
With this commit, register operands are only constrained when they have to be, and it is possible to have these instructions be created with a simple helper function that creates an operand with any register for their second operand.


chore: rewrite agg_pandas to use NamedAgg

Since cuDF have introduced NamedAgg, we can probably refactor the agg_pandas function to use NamedAgg. It may simplify things a bit, and avoid going via duplicate column names
This would just be an internal refactor

That would be really nice!
My concern is that to end up with a dedicated path for modin, wouldn't we?
(I could not find anything documenting modin support for NamedAgg)

looks like they have it
In [13]: import modin.pandas as mpd

In [14]: mpd.NamedAgg
Out[14]: pandas.core.groupby.generic.NamedAgg

Then... I am all in for it 😁🚀


HM Land Registry: Land Charges Bankruptcy Search

Please fill in the following information:
Base URL: https://businessgateway.landregistry.gov.uk/b2b/BGSoapEngine/BankruptcySearchV2_1WebService?wsdl
The URL for the API. For example, https://www.gov.uk/api/content. Please limit this to one URL - if you have sandbox environments or multiple endpoints please add them to the description.
Name: Land Charges Bankruptcy Search
The name of the API. For example, Gov.uk Content.
**Description: Overview

Use this service to find bankruptcy details on the Land Charges Register.

If you’re a software developer

Use this document to integrate data into your system.

Poll Request Service URL for production environment:
https://businessgateway.landregistry.gov.uk/b2b/BGSoapEngine/BankruptcySearchV2_1PollRequestWebService?wsdl
For test environment endpoints replace https://businessgateway.landregistry.gov.uk/b2b/BGSoapEngine with https://bgtest.landregistry.gov.uk/b2b/BGStubService
**
The description of what the API is about. Please make this as detailed as possible to help users search. For example "GOV.UK Content API makes it easy to access the data used to render content on https://www.gov.uk. For any page hosted on GOV.UK you can use the path to access the content and associated metadata for a page."
Documentation URL: https://landregistry.github.io/bgtechdoc/services/land_charges_bankruptcy_search/
The URL for the API documentation. For example https://content-api.publishing.service.gov.uk/
Maintainer<EMAIL_ADDRESS>Contact details for the team who manage the API, and who will be the first point of contact for a user wishing to access the service. Please don't use an individual's email address.
Provider: HM Land Registry
The full name of the department or organisation who provide the API. For example 'Government Digital Service'.
Area Served:
Optional - The geographic area that the API serves. For example: 'Greater London'.
Start Date:
Optional - The date the API comes into service. For example: '2020-07-01'.
End Date:
Optional - The date the API will be retired. For example: '2022-07-01'.
Alternate Name:
Optional - the acronym of the department or organisation. For example: 'GDS'.
Provider URL:
Optional - the canonical URL of the website of the department or organisation. For example: 'https://www.gov.uk/government/organisations/government-digital-service'.
If you have multiple APIs to add, you can use a CSV template with these fields which is available at: https://raw.githubusercontent.com/co-cddo/api-catalogue/HEAD/data/apic-csvtemplate.csv
Optionally, if you have more information you want to share with the API Catalogue community, please add it below.

Thanks Bethan, much appreciated.
From: Bethan Palmer @.>
Sent: 13 February 2023 16:14
To: co-cddo/api-catalogue @.>
Cc: Devey, Simon @.>; Author @.>
Subject: Re: [co-cddo/api-catalogue] HM Land Registry: Land Charges Bankruptcy Search (Issue #584)
Closed #584https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fco-cddo%2Fapi-catalogue%2Fissues%2F584&data=05|01|simon.devey%40landregistry.gov.uk|ee38b54f02104508be2e08db0ddd454c|236309a8284b4e57a7b3fc767736f69d|0|0|638119016215041138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0sK%2BRX2tRBLkx7JXphsEw5hMmWh%2BhPFNItLi3hgYuVU%3D&reserved=0 as completed via #586https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fco-cddo%2Fapi-catalogue%2Fpull%2F586&data=05|01|simon.devey%40landregistry.gov.uk|ee38b54f02104508be2e08db0ddd454c|236309a8284b4e57a7b3fc767736f69d|0|0|638119016215041138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VurxorNxBciS1jXa7G%2BisAHJfijZR7dBzwe8DJqntkA%3D&reserved=0.

Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fco-cddo%2Fapi-catalogue%2Fissues%2F584%23event-8506281316&data=05|01|simon.devey%40landregistry.gov.uk|ee38b54f02104508be2e08db0ddd454c|236309a8284b4e57a7b3fc767736f69d|0|0|638119016215041138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=YLxtygoqQyiNlZbRLiTtuDtwA1fyi8mNT%2FBsWAGDyxc%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA3AYUWCSOYKA4A63YSBF4ODWXJMTHANCNFSM6AAAAAAUXYXDJE&data=05|01|simon.devey%40landregistry.gov.uk|ee38b54f02104508be2e08db0ddd454c|236309a8284b4e57a7b3fc767736f69d|0|0|638119016215041138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=F23u5tYqVT11t%2B6kUn8aFOecqWDDLPHCz1Wb4%2FDMcFc%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>HM Land Registry's purpose is to protect your land ownership and provide services and data that underpin an efficient and informed property market. Our vision is: "A world-leading property market as part of a thriving economy and a sustainable future".
We check all mail and attachments for known viruses. However, you are advised that you open any attachments at your own risk. If you have received this email and it was not intended for you, please let us know, then delete it.
We welcome correspondence in English and Welsh.
To see how HM Land Registry treats your personal information, read our Personal information charter: www.gov.uk/government/organisations/land-registry/about/personal-information-charter.


Remove HttpPlatformHandler port detection.

https://github.com/aspnet/IISIntegration/pull/60
@davidfowl @JunTaoLuo

:shipit:


Android: scroll past last story title when marking stories read on scroll

See https://getsatisfaction.com/newsblur/topics/cannot-scroll-article-list-when-all-content-is-visible
Only show the extra tall footer if mark read on scroll is enabled. I recently added this to iOS.

Will do.  This is 100% untested feature (since I don't use it), so keep the recommendations coming.

included in #1095


Refactor cubos and dispatcher stage system

Refactor the cubos class and dispatcher to the new syntax proposed in #241. The "stages" system has been replaced with the "tags" system, allowing for more flexibility in system configuration.
The refactor is already taking into account multithreading, and is designed already for users to adapt to this paradigm. Systems execution order is now explicit. If no directive is given to a system/tag, their order is undefined. Right now the order is in reverse due to the topology algorithm, so this already gives an hint to developers when they forget to define execution order. When multithreading is introduced, the order will be arbitrary:
/// Before
cubos.addSystem(a, "A").addSystem(b, "B").addSystem(c, "C");
// Systems would implicitely run in order: A -> B -> C

/// Now
cubos.system(a).tagged("A").system(b).tagged("B").system(c).tagged("C");
// Systems will run in reverse due to topological algorithm: C -> B -> A
// With multithreading, this execution order will become further erratic

Further work, such as implementing tag/setting inheritance and adding conditions/threading modes to settings will be done in other PRs as to not clump everything together.

By the way, we hadn't discussed yet and I'm not sure how you are planning to implement it, but I think a possible good solution to the separation of concerts between Cubos and Dispatcher is:

Dispatcher provides exactly the same methods we planned for Cubos (excluding startupSystem of course).
the only job of Cubos is to pass call the methods on the correct Dispatcher and to make sure that no tag is shared between startup and non-startup systems.

By the way, we hadn't discussed this yet and I'm not sure how you are planning to implement it, but I think a possible good solution to the separation of concerns between Cubos and Dispatcher is:
* `Dispatcher` provides exactly the same methods we planned for `Cubos` (excluding `startupSystem` of course).

* the only job of `Cubos` is to call the methods on the correct `Dispatcher` and to make sure that no tag is shared between startup and non-startup systems.

What do you think?

Sure thing, but should the dispatcher handle tag/dependency resolution as well?

Yeah the idea was to move all of the dependency resolution to the dispatcher itself.

The PR is ready for review


Create home brew boilr package

I suggest to create home brew boilr package.

Private Boilr brew: https://github.com/harobed/homebrew-boilr-tap

https://github.com/Homebrew/homebrew-core/pull/25394

@harobed Maybe the formula would be accepted if you rework it to build from source based on the instructions here in the Wiki, rather than maintain your own tap?
Or, maybe you could submit it to homebrew-cask as a Cask instead? As mentioned in https://docs.brew.sh/Acceptable-Formulae.html#we-dont-like-binary-formulae:

Binary-only formulae should go to homebrew/cask.

That would look something like this:
cask 'boilr' do
  version '0.3.0'
  sha256 '81c135073310adbfbfa1b46fabb8467c26e08053340491d604ee9bec886c18d8'

  url "https://github.com/tmrts/boilr/releases/download/#{version}/boilr-#{version}-darwin_amd64.tgz"
  appcast 'https://github.com/tmrts/boilr/releases.atom'
  name 'Boilr'
  homepage 'https://github.com/tmrts/boilr'

  binary 'boilr'

  zap trash: ['~/.config/boilr']
end

this is the way

this is the way


fast-unstake: decouple from nomination pools + staking

The first draft of this pallet was written with the tight coupling approach for the sake of simplicity.

Moving Forward

[ ] We can use StakingInterface as a proxy into a staking pallet.
[x] We won't rely on nomination pools anymore and won't provide the feature to join the pool on the fly.

If we happen to want to still support pool join, we can either:

You provide some opaque: Vec<u8> data to the fast-unstake pallet, which is later on forwarded through some hook to nomination pools, and decoded as pool_id. Still, very very janky.
we wrap the current fast-unstake in a new pallet that does fast-unstake-and-join-pools.

I am going to attempt this.

@Szegoo not recommended, as we're doing a lot of development on this and it might change. I'd recommend sticking to mentor tagged issues.

We can use StakingInterface as a proxy into a staking pallet.

With the way fast-unstake is currently using pallet-staking Storage/Constants/Methods it seems like StakingInterface is not going to be enough to decouple one from another.
What we would need to do for full decoupling:

Remove direct calls to pallet-staking, like: Staking::<T>::chill, Staking::<T>::slashing_spans. For that we'd need to introduce some new methods to the StakingInterface
Remove param/constant getters that reference pallet-staking, like: <T as pallet_staking::Config>::BondingDuration::get()
Remove storage calls: pallet_staking::Ledger::<T>, pallet_staking::ValidatorCount, pallet_staking::ErasStakers

All of the above can reasonably be added to StakingInterface. It is reasonable for a interface to staking to be able to chill or force_unstake stakers, and to report what is its current bodning duration and validator count.
The slashing span thing can be abstracted away and should be dealt with purely on the staking side. We need that value only for weighing anyhow.
I am not saying we should YOLO it and tweak StakingInterface arbitrarily, but all of the above make sense to me to live in the interface, at least at the time being. If you think otherwise, happy to discuss, else I think we can move forward.


How to set the maximum number of faces that can be detected?

Plugin Version or Commit ID
v0.12.0
Unity Version
2021.3.18f1
Your Host OS
macOS Sonoma 14.0
Target Platform
Mac Standalone
Description
Hello,
I'm looking to set the maximum number of faces that can be detected by the Face Detection. I looked at the sources but did not find where to define this value.
Thank you!

Hello @homuler,
would you have some insights on this?
Thank you.

Any solutions to this issue?

I'm sorry, I overlooked this issue.
I believe it can be resolved by using ClipDetectionVectorSizeCalculator.
https://github.com/google/mediapipe/blob/4237b765ce95af0813de4094ed1e21a67bad2a5f/mediapipe/modules/face_landmark/face_landmark_front_cpu.pbtxt#L101-L114
Additionally, in the Task API, there are corresponding parameters available.
https://github.com/homuler/MediaPipeUnityPlugin/blob/84181bf0eebbb625c06112909878ac582dcc4484/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Tasks/Vision/FaceDetector/FaceDetectorOptions.cs#L63-L66


Add subtasks to the enlisted tasks.

SubTasks:

Adding subtasks to the enlisted tasks, could be an option.
The layout isn't thought out yet.

Current thoughts for a layout:

Either a popup when clicked on the To-Do, and further description can be added.
Or an accordion, something like this.

I'd be interested in helping out with this one. :-)

I'd be interested in helping out with this one. :-)

Great. Have you thought of a layout yet?

I was thinking of going more with the accordion proposal -> I'm an avid list maker and definitely prefer the dropdown approach more than the popup when using to-do lists in general. What do you think?

I was thinking of going more with the accordion proposal -> I'm an avid list maker and definitely prefer the dropdown approach more than the popup when using to-do lists in general. What do you think?

Alright! Go ahead!

Hey @ratatatCat
Any updates?

Ah! Sorry, I ended up getting pretty busy with work and got distracted. If it's not too late, I am off next week and could finish it up.

Yeah, no issues. Was just taking updates since it has been quite some time.

If it's not too late, I am off next week and could finish it up.

Yes, go ahead!

Awesome! I'm almost finished and will have a PR ready tomorrow or Tuesday. Thanks!

Awesome! I'm almost finished and will have a PR ready tomorrow or Tuesday. Thanks!


Add inverse header component

This component is a wrapper header to be used on topic and list pages:
https://trello.com/c/g2MMWMQr/110-blue-header

Component Guide Link: https://govuk-publishing-compon-pr-203.herokuapp.com/component-guide/inverse_header

@vanitabarrett I think the publication header component could eventually be replaced with this.
It seems very specific to HTML publications though.
The use case for this header will be in both topic and list pages, they have differing contents, so being able to wrap any content is going to be very useful.

The component as written will go to 100% of whatever it's put inside - I don't know how the topic pages will be structured but if it's at the same level as the global banner it would go full width. If it's put inside a constrained panel I'm not sure how we'd break back out of it without getting a bit hacky.
As for the other component, it might be similar enough to share them, but maybe consolidation is something to look at later? It would have to come into the gem to be used everywhere anyway.

What's the difference between this and http://govuk-static.herokuapp.com/component-guide/title/in_html_publication ?

@maxgds @steventux I've added a story in the backlog here to remind us to revisit Inverse Header vs Publication Headers https://trello.com/c/0pbli2e8/37-replace-publication-header-component-with-inverse-header-component


Fixed (huge) performance issue on belt creation

Hello,
I cannot thank you enough for this great mod. However as my factory grew I had some severe performance issues when creating multiple belts at the same time (like pulling 10 lanes with copy/paste), to a point it became unplayable (3 UPS) for several tens of minutes when placing a blueprint with 10k+ belts and roughly 2k bots. That was even worse in the lab where the game froze completely (all belts built at the same time I guess).
The core of the issue is an iteration over all the belt array on each belt creation in control.lua file, process_fast_replace function (so if like me the array is more than 10k elements and you try to place several hundred belts at the same time....).
For now I changed it to an api call to find_entities_filtered and a way less resource intensive index access. I got nearly native factorio UPS on belt creation back (the same blueprints does not make my UPS drop anymore and is created in the lab in a couple of seconds).
That beeing said I strongly suspect this function has no utility at all. I was totally unable to trigger the condition, be it in the new or the old code by whatever way I could think for a replacement. After checking the events, in every try one of the deconstruction event was trigger before the creation one, and so the table was clean before the creation.
I noticed this particular code comes from the old mod and was written to address an issue for fast replacement more than 4 years ago. It might be there was an API issue were the deconstruction event was not trigger by fast replacement, but it does not seem to be the case anymore. Or it might be a very peculiar case where no event is triggered...
In any case I played for ten hours or so with the function call commented out and still have no orphan entry in the belt array.
Anyways this patch makes the process light enough if you prefer to keep the check the way it is.

I've just created a PR on IThundxr:master to remove this function, but I don't plan on doing any further development on this version of the mod so I'm closing this PR.


Update fill price modeling for stop market orders in FillModel

Description

Updated fill price modeling for stop market orders in FillModel.cs
Updated relevant unit tests to highlight expected behavior

Related Issue
Closes #4545
Motivation and Context
Generate more realistic fill prices for stop market orders when backtesting.
Requires Documentation Change
N/A
How Has This Been Tested?
Updated the relevant unit tests for ImmediateFillModel. I debated breaking the scenarios out into separate tests but I ended up leaving them together to keep it consistent with the rest of the order type tests.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Hi @bhamer interesting PR thank you. I guess a tangible example of this would be a gap down overnight and passing the stop price of the opening bar?

Hi @jaredbroad, the general case is a bar that triggers the stop and where there's a meaningful difference between the open price, close price, and stop price. A gap up/down isn't necessary, but it is a common case.
So using your example of a gap down past the sell stop price, in reality the fill would occur at the open but the current fill model is effectively filling it at the close. This matters when the price has moved meaningfully between the open and close time for that particular bar.

@bhamer, should we not expect the same behavior for limit orders and stop-limit orders?

@AlexCatarino I think limit fills (with or without a stop trigger) can be improved using a similar approach, i.e., utilizing the fact that we know open price came before HLC prices. But I view the limit fills separately since they'll have different logic for determining the fill price than market fills, which is what this is.
It's a good question though, they don't necessarily need to be viewed separately. And you prompted a thought that it could make sense to refactor a bit and break out the fill logic (market, limit) from the trigger logic (stop, MOO, MOC).
Thoughts? If the team agrees with the approach to stop market orders I can put together a more holistic PR that includes the other order types.

Adding to the previous comment -
I think it's more important to update stop-market fills because they're usually filled at an unrealistic price, i.e., it's rare that a stop market order would fill at exactly the stop price (no slippage) or the close price plus slippage of the bar that triggered it. Whereas limit fills are usually filled at the limit price.


[Bug]: "Try another search..." text is not visible in dark mode

Is there an existing issue for this?

[X] I have searched the existing issues

Is there a StackOverflow question about this issue?

[X] I have searched StackOverflow

What happened?
The ClickableText containing the tryAnotherSearchString in the EmptySearchResultBody composable is not visible in dark mode.

Light mode
Dark mode

Default Theme

Android Theme

Relevant logcat output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think this is a duplicate of

#837

Sorry, didn't see that issue was already there as the title was different. Am closing this issue.


AWS::Events::Rule ScheduleExpression: "cron(* 1 * * * *)"

cfn-lint version: (cfn-lint 0.27.5)
Description of issue.
  EventRule:
    Type: "AWS::Events::Rule"
    Properties:
      ScheduleExpression: "cron(* 1 * * * *)"
      State: "ENABLED"
      Targets:
        - Arn: !Ref Foo
          Id: "Foo"
          RoleArn: !GetAtt FooArn.Arn

Check should be probably in:
src/cfnlint/rules/resources/events/RuleScheduleExpression.py
The above ScheduleExpression is invalid (need a value for minute if hour is set). For example cron(0 1 * * ? *)

Schedule Expressions for Rules documentation

@jtheuer I can get * 1 * * ? * to work.  Are you getting an error in this situation?  I'm seeing this in the documentation.
You can't specify the Day-of-month and Day-of-week fields in the same cron expression.
If you specify a value (or a *) in one of the fields, you must use a ? (question mark) in the other.

Which was also corrected in your example and seems like an easy rule we can write.  Thoughts?

Hi @kddejong Yes, * 1 * * ? *is correct. The example from the CF snippet above is invalid but didn't raise an error.  Thanks for tackling this.

main issue for AWS::Events::Rule.ScheduleExpression: https://github.com/aws-cloudformation/cfn-python-lint/issues/816


Subteam-folder not visible

Keybase GUI Version: 3.2.1-20190410001724+61d9000f85
Subteam folder not visible on one PC (this one) but contains files on another PC.

If you do a keybase log send, and post the resulting ID here, I can take a look. Also in the feedback of the log send, please give more info about which folder is not available.

done. af0736685bc962951dc3bc1c

@jokmie it looks like the user logged into that machine isn't a member of the team.  The user is just an "implicit admin" of the team, which means they're an admin of the parent team, but they haven't yet added themselves as an explicit member of the subteam.

Ohh wow. I understand. That was counter-intuitive since I created the group from the same machine and same user.

Yep, it's a little weird, but it makes sense when you consider admins in companies or something that are creating teams on behalf of other groups in the company.  Please let us know if anything else seems wrong.