Backlit of my custom keyboard is not working even after the command

Regression?
Yes
System Info and Version
https://justpaste.it/fh1qf
Description
My backlit used to work when I uninstalled hyprland months ago. Today, i installed hyprland and everything works fine but backlit is not wokring.
My backlit blinks for a second if i write this command but it only blinks sudo sh -c 'echo 1 > /sys/class/leds/input24::scrolllock/brightness'
How to reproduce

Opens terminal and write both command - xset led on && sudo sh -c 'echo 1 > /sys/class/leds/input24::scrolllock/brightness'
backlit blinks for a second and stops
again type command then it blinks and stops

Crash reports, logs, images, videos
No response

excuse me but why is your keyboard's backlight the scroll lock LED?

@vaxerski It's a custom embed setting from the keyboard. In Windows, it starts with the Fn key + Scroll Lock. Even on Arch Linux, I can enable it through xset led on, but on Hyprland, I cannot enable it using xset led on or by running sudo sh -c 'echo 1 > /sys/class/leds/input24::scrolllock/brightness'.

xset is for X. It won't work on wayland.
ATM, there is no mechanism to forcefully lock LED states in hyprland. You could patch hyprland yourself for that though

@vaxerski okay but can you tell me why sudo sh -c 'echo 1 > /sys/class/leds/input24::scrolllock/brightness'  not working because I used this command couple month ago in my previous hyprland setup and it was turning my LED on but now its not, why?

hyprland takes full control of your LEDs, if scroll lock is not enabled in hyprland, the LED will be disabled next time hyprland updates the LED states.

@vaxerski So there is no way to get LED enabled ? What do i have to do to patch my hyprland for my LED problem

IKeyboard.cpp@290
you need to find your numlock LED index and make the value val | (1 << idx)
updateLEDs(leds.value() | (1 << numlockLedIndex));

Okay, Thanks

because hyprland controls your leds


[engsys] upgrade dev-dependency @types/mock-fs

I believe this has been solved in https://github.com/Azure/azure-sdk-for-js/pull/18707

closing. we now have bot-created issues tracking dep upgrades.


Stark: Update docs

TITLE
Description
Description of the pull request changes and motivation.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #611 (c43c3c5) into main (a1f2fa7) will increase coverage by 0.37%.
Report is 3 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #611      +/-   ##
==========================================
+ Coverage   96.74%   97.11%   +0.37%
==========================================
  Files         115      114       -1
  Lines       26675    26540     -135
==========================================
- Hits        25807    25775      -32
+ Misses        868      765     -103

see 10 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Via cannot detect my ergodash

I flashed the firmware in this repo for both sides. Then I connect the keyboard into my computer and start Via. But it keeps searching for devices...
BTW, I see some posted that Ergodash is supported in via but cannot find the firmware in the official document here

You need to sideload the JSON file found in the firmware zip
https://github.com/omkbd/ErgoDash/tree/master/Firmware
One you do this it will show up (note that you will need to do this every time you open via, I have not found a way to make the sideload json permanent. Same with Vial)


Expose LibCrypt PKCS5_PBKDF2_HMAC

Solves issue #6973
Replaces pull request #5021

I declared a new enum named DigestAlgorithm.
I declared a new enume DigestAlgorithm
I'm not sure about the following:

Location (should I declare this inside the module?)
Casing (for acronims in enum members)
Enum naming (is the name DigestAlgorithm a good name?)

IMO just Digest is fine, like https://crystal-lang.org/api/master/OpenSSL/Digest.html. You can also drop the , after each enum element. For the location, it's in the right place.

Added a version check that enables the feature only when OpenSSL >= 1.0.0
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Added a version check that enables the feature only when OpenSSL >= 1.0.0
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Added a version check that enables the feature only when OpenSSL >= 1.0.0
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Added a version check that enables the feature only when OpenSSL >= 1.0.0
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Made the chanes you suggested.
Also added a version check that enables the feature only when OpenSSL >= 1.0.0 (when the underlying method became available).
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Made the chanes you suggested.
Also added a version check that enables the feature only when OpenSSL >= 1.0.0 (when the underlying method became available).
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Made the chanes you suggested.
Also added a version check that enables the feature only when OpenSSL >= 1.0.0 (when the underlying method became available).
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Made the chanes you suggested.
Also added a version check that enables the feature only when OpenSSL >= 1.0.0 (when the underlying method became available).
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Made the chanes you suggested.
Also added a version check that enables the feature only when OpenSSL >= 1.0.0 (when the underlying method became available).
Suggestion made in https://github.com/crystal-lang/crystal/pull/5021#issuecomment-334394154

Sorry for the mess, Im a total newbie

I feel that I'm close...

done

just waiting for another review

You'll be able to compile with a macro condition at compile time. What if you think the function won't be used but it does in a particular situation? This is a case that could be dealed before runtime, and your application will be more robust because this error won't exist.

Shit, this was a breaking change, so this needs a revert and resubmit and wait until 0.28.0
Or we could just say that it's been so long since 0.27.0 that we can have the next release be 0.28.0.

This change does indeed break any code that deals with OpenSSL Ciphers.
@RX14 Will it be reverted and wait until 0.28.0 will the 0.27.1 release just never happen? I think it's fine either way (from my perspective), there should just be some clarity on which it will be so I can update my libraries accordingly.

It will be reverted.

@asterite Given the amount of changes wouldn't be better to tag next release as 0.28?

@mniak please resubmit this PR! It's my mistake merging it too early, but it needs to wait until 0.28.0 so it's been reverted in master.

@Sija We discussed this option in the core team and agreed that it is be better to stick to the plan. Reverting this PR is cheap and doesn't cause any disturbance. We can proceed to prepare for 0.27.1 as the next release and 0.28.0 after that.

@RX14 Do I do it simply by creating a new PR with these changes?


Issues with DtcNumberObdCommand and TroubleCodesObdCommand

Hello,
While working with your API, I've had great success in general so I have to thank you for that first. Everything seems to work well in general and I haven't had issues with most of the commands.
It's when I get to DtcNumberObdCommand and TroubleCodesObdCommand that issues start to occur.
In the case of DtcNumberObdCommand, after running it it throws the following error:
E/AndroidRuntime(11826): FATAL EXCEPTION: Thread-410
E/AndroidRuntime(11826): Process: com.vuzix.networker, PID: 11826
E/AndroidRuntime(11826): pt.lighthouselabs.obd.exceptions.NonNumericResponseException: Error reading response: 1:06410100040000
E/AndroidRuntime(11826):        at pt.lighthouselabs.obd.commands.ObdCommand.fillBuffer(ObdCommand.java:155)
E/AndroidRuntime(11826):        at pt.lighthouselabs.obd.commands.ObdCommand.readResult(ObdCommand.java:138)
E/AndroidRuntime(11826):        at pt.lighthouselabs.obd.commands.ObdCommand.run(ObdCommand.java:84)
In the case of TroubleCodesObdCommand, the issue I get is the following:
E/AndroidRuntime(12254): FATAL EXCEPTION: Thread-416
E/AndroidRuntime(12254): Process: com.vuzix.networker, PID: 12254
E/AndroidRuntime(12254): java.lang.StringIndexOutOfBoundsException: length=16; index=16
E/AndroidRuntime(12254):        at java.lang.String.indexAndLength(String.java:500)
E/AndroidRuntime(12254):        at java.lang.String.charAt(String.java:494)
E/AndroidRuntime(12254):        at pt.lighthouselabs.obd.commands.control.TroubleCodesObdCommand.performCalculations(TroubleCodesObdCommand.java:82)
E/AndroidRuntime(12254):        at pt.lighthouselabs.obd.commands.ObdCommand.readResult(ObdCommand.java:139)
E/AndroidRuntime(12254):        at pt.lighthouselabs.obd.commands.ObdCommand.run(ObdCommand.java:84)
You may already know of what's going on, but I couldn't say for sure myself since this is really my first step into working with OBDII to any significance.
The last bit of information I can provide is that the vehicle I was testing on was a 2011 Chevrolet Cobalt. This may or may not have some relation to the issue. I am not sure personally. If there's any other way I can help you pinpoint the issues (more information, more testing, ect) just let me know.
Thanks!

pt.lighthouselabs.obd.commands.control.TroubleCodesObdCommand.performCalculations(TroubleCodesObdCommand.java:82) throws java.lang.StringIndexOutOfBoundsException: length=16; index=16, so that's the issue. Will try to fix tomorrow.

Haven't got the time to fix this. @nomwerp care to give a try?

sorry can't make much sense of it without the data, would it be possible to look into the value of workingData ?        could it possibly be another case of junk data?  in android-obd-reading we are having to strip out some of the junk before performCalculations() is called
https://github.com/pires/android-obd-reader/blob/master/src/main/java/pt/lighthouselabs/obd/reader/activity/TroubleCodesActivity.java
  public class ModifiedTroubleCodesObdCommand extends TroubleCodesObdCommand {
      @Override
      public String getResult() {
          // remove unwanted response from output since this results in erroneous error codes
      return rawData.replace("SEARCHING...", "");
      }
  }

we should probable add this to obd-java-api instead so that other projects also can benefit from it

@nomwerp workingData in case of error is here
performCalculations workingData﹕ "41006000"
java.lang.StringIndexOutOfBoundsException: length=8; regionStart=7; regionLength=3


[SPARK-49264][SQL][TESTS] Add collation support unit tests for Contains, StartsWith, and EndsWith

What changes were proposed in this pull request?
Add collation support unit tests for:

Contains
StartsWith
EndsWith

This PR contains test-only changes, providing additional test coverage for cases such as:

case and accent variation
one-to-many case mapping
conditional case mapping
surrogate pairs
etc.

Why are the changes needed?
Improve collation support testing.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New unit tests in CollationSupportSuite.
Was this patch authored or co-authored using generative AI tooling?
Yes.

+1, LGTM. Merging to master.
Thank you, @uros-db.


Update Bookstack form BookStack v23.12.2 to BookStack v24.02.3

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hi,
i want to Update my Instance. But i get an Error:
apt update
apt upgrade
cd /var/www/bookstack
sudo composer self-update
git pull origin release
Aktualisiere 9441e32c..606f9d92
Fehler: Ihre lokalen Änderungen in den folgenden Dateien würden durch den Merge
überschrieben werden:...
He cannot carry out the update, otherwise the data will be overwritten.
Source:
https://www.bookstackapp.com/docs/admin/updates/
Thanks for your help!
Exact BookStack Version
BookStack v23.12.2
Log Content
Von https://github.com/BookStackApp/BookStack

branch              release    -> FETCH_HEAD
Aktualisiere 9441e32c..606f9d92
Fehler: Ihre lokalen Änderungen in den folgenden Dateien würden durch den Merge
überschrieben werden:
.github/translators.txt
app/Access/Oidc/OidcOAuthProvider.php
app/Access/Oidc/OidcService.php
app/Access/RegistrationService.php
app/Activity/ActivityQueries.php
app/Activity/CommentRepo.php
app/Activity/Controllers/CommentController.php
app/Activity/Controllers/FavouriteController.php
app/Activity/Models/Comment.php
app/Activity/Tools/CommentTree.php
app/Api/ApiDocsGenerator.php
app/App/HomeController.php
app/App/Providers/ThemeServiceProvider.php
app/App/PwaManifestBuilder.php
app/Config/clockwork.php
app/Config/filesystems.php
app/Console/Commands/CopyShelfPermissionsCommand.php
app/Console/Commands/RegenerateCommentContentCommand.php
app/Entities/Controllers/BookApiController.php
app/Entities/Controllers/BookController.php
app/Entities/Controllers/BookExportApiController.php
app/Entities/Controllers/BookExportController.php
app/Entities/Controllers/BookSortController.php
app/Entities/Controllers/BookshelfApiController.php
app/Entities/Controllers/BookshelfController.php
app/Entities/Controllers/ChapterApiController.php
app/Entities/Controllers/ChapterController.php
app/Entities/Controllers/ChapterExportApiController.php
app/Entities/Controllers/ChapterExportController.php
app/Entities/Controllers/PageApiController.php
app/Entities/Controllers/PageController.php
app/Entities/Controllers/PageExportApiController.php
app/Entities/Controllers/PageExportController.php
app/Entities/Controllers/PageRevisionController.php
app/Entities/Controllers/PageTemplateController.php
app/Entities/Controllers/RecycleBinController.php
app/Entities/Models/Book.php
app/Entities/Models/BookChild.php
app/Entities/Models/Chapter.php
app/Entities/Models/Page.php
app/Entities/Queries/EntityQuery.php
app/Entities/Queries/Popular.php
app/Entities/Queries/RecentlyViewed.php
app/Entities/Queries/TopFavourites.php
app/Entities/Repos/BaseRepo.php
app/Entities/Repos/BookRepo.php
app/Entities/Repos/BookshelfRepo.php
app/Entities/Repos/ChapterRepo.php
app/Entities/Repos/PageRepo.php
app/Entities/Repos/RevisionRepo.php
app/Entities/Tools/BookContents.php
app/Entities/Tools/Cloner.php
app/Entities/Tools/MixedEntityListLoader.php
app/Entities/Tools/PageContent.php
app/Entities/Tools/PageEditorData.php
app/Entities/Tools/ShelfContext.php
app/Entities/Tools/SiblingFetcher.php
app/Entities/Tools/TrashCan.php
app/Http/DownloadResponseFactory.php
app/Http/Kernel.php
app/Permissions/JointPermissionBuilder.php
app/Permissions/PermissionsController.php
app/References/CrossLinkParser.php
app/References/ModelResolvers/BookLinkModelResolver.php
app/References/ModelResolvers/BookshelfLinkModelResolver.php
app/References/ModelResolvers/ChapterLinkModelResolver.php
app/References/ModelResolvers/PageLinkModelResolver.php
app/References/ModelResolvers/PagePermalinkModelResolver.php
app/References/ReferenceController.php
app/References/ReferenceFetcher.php
app/Search/SearchController.php
app/Search/SearchRunner.php
app/Settings/MaintenanceController.php
app/Theming/ThemeEvents.php
app/Translation/LocaleManager.php
app/Uploads/Attachment.php
app/Uploads/AttachmentService.php
app/Uploads/Controllers/AttachmentApiController.php
app/Uploads/Controllers/AttachmentController.php
app/Uploads/Controllers/GalleryImageController.php
app/Uploads/Controllers/ImageGalleryApiController.php
app/Uploads/ImageRepo.php
app/Uploads/ImageService.php
app/Users/Controllers/UserProfileController.php
app/Users/Queries/UserContentCounts.php
app/Users/Queries/UserRecentlyCreatedContent.php
app/Util/HtmlDescriptionFilter.php
composer.lock
database/factories/Activity/Models/CommentFactory.php
dev/api/requests/chapters-create.json
dev/api/requests/chapters-update.json
dev/api/responses/chapters-create.json
dev/api/responses/chapters-read.json
dev/api/responses/chapters-update.json
lang/ar/activities.php
lang/ar/common.php
lang/ar/editor.php
lang/ar/entities.php
lang/ar/errors.php
lang/ar/settings.php

Hosting Environment
PHP 8.2
Debian 12
Apache 2.4
MariaDB 10.11.6-MariaDB-0+deb12u1 Debian 12

Hi @Tutnich,
Please can you:

Run git config core.fileMode false then confirm the output of git status.
Confirm if you've made any intentional changes to BookStack source/app files?

Thanks Dan.
That solved my Problem.

Good to hear! Will therefore close this off.


BarrierBeforeFinalMeasurement should be removed from transpiled circuit

Environment

Qiskit Terra version: 0.42.1
Python version: 3.9
Operating system: MacOS

What is happening?
When the transpiler does its routing pass, in some cases it inserts a barrier before final measurement. This barrier is not necessarily in the input circuit, and in cases where it is, it is expanded to span the full width of hte device rather than only the qubits of the input qubit.
If this barrier is not in the input circuit it should be removed from the transpiled circuit. If it is in the input circuit it should be only on the appropriately mapped qubits in the output circuit.
How can we reproduce the issue?
Example Circuit 1
First example is for a circuit with no barriers:
from qiskit import QuantumCircuit, transpile

qc = QuantumCircuit(2, 2)
qc.cx(0, 1)
qc.measure(range(2), range(2))

          ┌─┐
q_0: ──■──┤M├───
     ┌─┴─┐└╥┘┌─┐
q_1: ┤ X ├─╫─┤M├
     └───┘ ║ └╥┘
c: 2/══════╩══╩═
           0  1

Example Circuit 2
If I use measure_all which inserts a barrier, it gets expanded to all ancilla qubits:
              ░ ┌─┐
   q_0: ──■───░─┤M├───
        ┌─┴─┐ ░ └╥┘┌─┐
   q_1: ┤ X ├─░──╫─┤M├
        └───┘ ░  ║ └╥┘
meas: 2/═════════╩══╩═
                 0  1

Transpiled Circuits
If i force some complicated layout, in both cases the transpiled circuit has a full width barrier in it
transpile(qc, initial_layout=[1, 4], coupling_map=[[1, 2], [2, 3], [3, 4]]).draw()

                        ░
ancilla_0 -> 0 ─────────░───────
                        ░
      q_0 -> 1 ─X───────░───────
                │       ░ ┌─┐
ancilla_1 -> 2 ─X───■───░─┤M├───
                  ┌─┴─┐ ░ └╥┘┌─┐
ancilla_2 -> 3 ─X─┤ X ├─░──╫─┤M├
                │ └───┘ ░  ║ └╥┘
      q_1 -> 4 ─X───────░──╫──╫─
                        ░  ║  ║
       meas: 2/════════════╩══╩═
                           0  1

What should happen?
Expected transpiled circuit 1

ancilla_0 -> 0 ────────────────

      q_0 -> 1 ─X──────────────
                │        ┌─┐
ancilla_1 -> 2 ─X───■────┤M├───
                  ┌─┴─┐  └╥┘┌─┐
ancilla_2 -> 3 ─X─┤ X ├───╫─┤M├
                │ └───┘   ║ └╥┘
      q_1 -> 4 ─X─────────╫──╫─
                          ║  ║
       meas: 2/═══════════╩══╩═
                           0  1

Expected transpiled circuit 2

ancilla_0 -> 0 ────────────────

      q_0 -> 1 ─X──────────────
                │       ░ ┌─┐
ancilla_1 -> 2 ─X───■───░─┤M├───
                  ┌─┴─┐ ░ └╥┘┌─┐
ancilla_2 -> 3 ─X─┤ X ├─░──╫─┤M├
                │ └───┘ ░  ║ └╥┘
      q_1 -> 4 ─X──────────╫──╫─
                           ║  ║
       meas: 2/════════════╩══╩═
                           0  1

Any suggestions?
Add another transpiler pass to the generate_routing_passmanager that removes the barrier inserted by BarrierBeforeFinalMeasurement, and in the case where the original circuit has a barrier, preserve that barrier mapped to the appropriate qubits in the transpiled circuit.

Yeah I think ideally we should have an option to label the barrier BarrierBeforeFinalMeasurement inserts and later remove the labeled barriers before optimization. The barriers are only inserted for routing purposes so there isn't a reason for them to persist outside of the transpiler. This shouldn't be too hard to implement.

Are these barriers still necessary for routing? I don't believe they are needed for the backends anymore, so maybe BarrierBeforeFinalMeasurement can be removed from the default levels.

Yeah, they are still needed for routing. Without it sabre will potentially route past a measurement so we still rely on the inserted barrier for routing to work.

I think they're not needed for backends, but a mid-circuit measurement (which these measurements become if swaps appear after them) have different error rates and performance characteristics than final measurements, so it's probably not ideal to be routing gates after them.  It's also better for parallelisation of readout on basically any hardware architecture that can parallelise readout, I think?
Fwiw, I want to update Sabre with more context about every operation as a stepping stone to getting it to support mirror-gate synthesis and optimising the final circuit construction in Python space, and that would naturally tie into this as well.


not_to not negating redirect_to and render_template

Hi I have a some RSpec tests that follow the following format:
expect(response).not_to render_template(:index)
expect(response).not_to redirect_to posts_url

In both cases despite the subject of the test functioning as expected, the tests fail. The reason looks like it is a result of the assertions not being negated when using not_to.
For example when I run:
expect(response).not_to redirect_to posts_url

I get:
Expected response to be a <redirect>, but was <200>.

When I run :
expect(response).not_to render_template(:index)

I get:
expecting <"index"> but rendering with <["applications/foobar", "layouts/application"]>

I am running Ruby 2.1.7 with the following dependencies:

rails (4.0.13)
rspec (3.3.0)
rspec-collection_matchers (1.1.2)
rspec-core (3.3.1)
rspec-expectations (3.3.0)
rspec-mocks (3.3.1)
rspec-rails (3.3.2)
rspec-support (3.3.0)

FYI: I'm not using shoulda-matchers, so this closed issue looks different.
Thanks.

It's possible those matchers don't negate properly, but I'm surprised we've never received a bug report before if thats the case! In the mean time try this:
RSpec::Matchers.define_negated_matcher :avoid_rendering_template, :render_template
RSpec::Matchers.define_negated_matcher :avoid_redirect_to, :redirect_to

specify { expect(response).to avoid_rendering_template(:index) }
specify { expect(response).to avoid_redirect_to posts_url }

/cc @samphippen @cupakromer

Hi @JonRowe,
Thanks for the suggested workaround. However this also gives me unexpected results.
Having defined the negated matchers as you suggest, I still have failing tests, with similar output:
When I run:
expect(response).to avoid_rendering_template(:index)

I get:
expecting <"index"> but rendering with <["error/errors", "layouts/foobar"]>.

Stacktrace:
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:55:in `block in assert_block'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:1627:in `call'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:1627:in `_wrap_assertion'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:53:in `assert_block'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:163:in `block in assert'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:1632:in `call'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:1632:in `_wrap_assertion'
#../ruby/2.1.0/gems/test-unit-3.1.2/lib/test/unit/assertions.rb:130:in `assert'
#../ruby/2.1.0/gems/rspec-rails-3.3.2/lib/rspec/rails/adapters.rb:210:in `block (2 levels) in define_assertion_delegato
rs'
#../ruby/2.1.0/gems/actionpack-4.0.13/lib/action_controller/test_case.rb:118:in `assert_template'
#../ruby/2.1.0/gems/rspec-rails-3.3.2/lib/rspec/rails/matchers/have_rendered.rb:17:in `block in matches?'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/built_in/base_matcher.rb:47:in `match_unless_raises'
#../ruby/2.1.0/gems/rspec-rails-3.3.2/lib/rspec/rails/matchers/have_rendered.rb:16:in `matches?'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/matcher_delegator.rb:17:in `method_missing'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/aliased_matcher.rb:25:in `method_missing'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/aliased_matcher.rb:78:in `matches?'

Not sure if the following is what you would expect, but as the stacktrace shows AliasedNegatedMatcher determines that the @base_matcher (have_rendered) doesn't respond to a does_not_match? method, and the matching logic gets handled up the inheritance tree by MatcherDelegator, who calls matches? on the base_matcher (have_rendered).
The avoid_redirect_to negated matcher produces very similar results to avoid_rendering_template. With the test result being:
Expected response to be a <redirect>, but was <500>.

Stacktrace:
#../ruby/2.1.0/gems/actionpack-4.0.13/lib/action_dispatch/testing/assertions/response.rb:27:in `assert_response'
#../ruby/2.1.0/gems/actionpack-4.0.13/lib/action_dispatch/testing/assertions/response.rb:53:in `assert_redirected_to'
#../ruby/2.1.0/gems/rspec-rails-3.3.2/lib/rspec/rails/matchers/redirect_to.rb:15:in `block in matches?'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/built_in/base_matcher.rb:47:in `match_unless_raises'
#../ruby/2.1.0/gems/rspec-rails-3.3.2/lib/rspec/rails/matchers/redirect_to.rb:14:in `matches?'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/matcher_delegator.rb:17:in `method_missing'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/aliased_matcher.rb:25:in `method_missing'
#../ruby/2.1.0/gems/rspec-expectations-3.3.0/lib/rspec/matchers/aliased_matcher.rb:78:in `matches?'

Not sure if this sheds any further light?
Thanks.

Ok so I've tested this myself and I can't replicate it, I've opened a PR showing negated examples working correctly (we already had specs for them) (on Rails 4.2, but the PR will test against all our supported versions of Rails) so if that passes we'll need more information to try to fix this...

The negated examples are all passing for us on Travis so there has to be something else at play here, whats generating response here?

Hi @JonRowe,
Thanks for confirming that this was not a rspec-rails issue. Your findings highlighted that this was probably a configuration issue with our app. Long story short, I discovered that the test-unit gem was also being included in the Gemfile, and that this was the culprit; interfering with these specific matchers when negated. Once this dependency was removed the relevant tests passed.
So looks like this issue can be closed :)
Really appreciate your efforts investigating this.
Thanks,
Matt


Enabling the rebelinblue/deployer plugin

Hi, I want to try using rebelinblue/deployer as describe in https://github.com/Block8/PHPCI/wiki/Deployer.
Installed the plugin via composer but somewhow I get this when running a build:

RUNNING PLUGIN: deployer
Plugin does not exist: deployer
PLUGIN: FAILED

What was the process you took in order to install the plugin?
Also what version of PHPCI are you running?

PHPCI Version 1.6.0
I install the plugin through the Plugins page.

Search the package
Install
composer update

Can you run the following at the root of your PHPCI folder and post the relevant section?
./console phpci:rebuild -vvv
I don't personally have a clue on your situation but I've found running these commands manually will assist in debug / troubleshooting.

Someone else had this problem before, can you try running composer dump-autoload?
Are you using cronjobs to run builds? If you are using the daemon or the queue listener can you restart them to make sure it has picked up the plugin file?

Sorry for the late reply. Was away for a while. Anyway, I started from scratch:

remove the plugin
composer update
install the plugin via the plugin page. choosed 0.0.33
composer update

and get this result:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1

Installation request for rebelinblue/deployer 0.0.33 -> satisfiable by rebelinblue/deployer[0.0.33].
rebelinblue/deployer 0.0.33 requires andywer/js-localization dev-laravel-5 -> satisfiable by andywer/js-localization[dev-laravel-5] but these conflict with your requirements or minimum-stability

PHPCI version 0.60

Ah, there seems to be some confusion here. https://github.com/REBELinBLUE/deployer is a completely separate app I work on, it isn't a plugin for PHPCI.
PHPCI has a plugin, included already https://github.com/Block8/PHPCI/blob/master/PHPCI/Plugin/Deployer.php which can call the webhook feature in Deployer to trigger a deployment on a successful build.

I see. My mistake then.
That said, without installing the packages. I still getting same error at my first post. Plugin does not exist: deployer
Copy paste the command from wiki.. using my own url off course.

https://github.com/Block8/PHPCI/tree/1.6.0/PHPCI/Plugin Version 1.6.0 doesn't appear to include the plugin
Added in the 1.7.0 betas by the looks of it
https://github.com/Block8/PHPCI/tree/1.7.0-beta1/PHPCI/Plugin
https://github.com/Block8/PHPCI/tree/1.7.0-beta2/PHPCI/Plugin

Ah yes.. why didn't I check that first? facepalm
I'll wait for the official release.. Thank you


Creating register method for controller not working.

I created my own post register method yet it still use the old post register. I modify it into redirect to login, and also var_dump the validator with a commented return, still not works, it still redirect to route site.com/customer/register not site.com/customer/login
/app/Http/Controllers/Customer/Auth/RegisterController.php
public function postRegistrationForm(Request $request)
{
    // return $request->all();
    var_dump($this->validator($request->all())->validate());

    return redirect()->route('login')
        ->with(['success' => 'Congratulations! your account is registered, you will shortly receive an email to activate your account.']);
}

and on my routes\customer.php
Route::group(['namespace' => 'Customer'], function() {
...
    Route::get('login', 'Auth\LoginController@showLoginForm')->name('customer.login');
    Route::post('login', 'Auth\LoginController@login');
    Route::post('register', 'Auth\RegisterController@postRegistrationForm'); // <--------
...
});

It can run the route but it has different result. I can't get the var_dump($this->validator($request->all())->validate());

Originally posted by @jeraldpunx in https://github.com/bitfumes/laravel-multiauth/issues/45#issuecomment-443209464

    public function postRegistrationForm(Request $request)
    {
        $this->validator($request->all())->validate();

        return "aw";
    }

Even I do this on /app/Http/Controllers/Customer/Auth/RegisterController.php
It still doesn't return "aw" when correct, but when I failed the input, it redirect to Route::get('register', 'Auth\RegisterController@showRegistrationForm')->name('customer.register');


"SSL: CERTIFICATE_VERIFY_FAILED" should show cert at least with --debug

When connecting to a site with a broken TLS certificate, httpie only displays the one-liner Python error message.
It would be nice, if it would print the certificate chain in human readable form, maybe even with a hint that e.g. the intermediate certificate is no longer valid, the common name does not match or the certificate is self signed.

I'd like to take this issue.

@darthbeep go for it 👍

Would you be ok with importing sockets and cryptography? I'm not sure it's possible to do without them.

#954

@lathspell would you mind sharing an example website that we can use to reproduce this problem?


Redis Streams support

Are there a plans to implement streams?
Redka Streams would be perfect replacement for Redis Streams in many Kafka use cases where disk storage is required and/or memory is restricted.

No current plans. Would you personally use Redka in this use case?

Yes, definitely.
Support for full streams API would allow me to switch from Kafka to Redka Streams for dev/ci/testing environments. Using Redis Streams currently doesn't have much sense to me, because of high requirements for a memory which is way more expensive than disk in a cloud. My use cases usually require long data retention but are fine with reduced performance.

If you only use Kafka in production (and Redis/Redka in dev/test), doesn't that mean that Kafka-related features don't get tested at all? Is that wise?

I'm using te same protocol on all environments. Currently it's Kafka.
I could switch to Redis/Redka streams everywhere, if Redka supports streams. Then I could use Redka for dev/testing and some managed Redis solution for production.

I see, thanks for the explanation! I will look into streams after the 1.0 release.
I'll leave the issue open to see if anyone else is interested in this feature.


NIFI-3851 Add expression language support to AWS Endpoint Override UR…

NIFI-3851 Add expression language support to AWS Endpoint Override URL property

Reviewing...

@tequalsme Thanks for putting this together.  The commit passes the full build, and manually running it with an S3 processor worked great.
But I would prefer not to add runner.setValidateExpressionUsage(false) to the unit tests for DyanmoDB, Kinesis, etc.  They might use EL validation in the future, and I don't think it should be necessary based on precedents like ACCESS_KEY or PROXY_HOST that also use EL.
The problem appears to be a mismatch between those processors not configured to use the ENDPOINT_OVERRIDE property descriptor, but are nonetheless evaluating it when they call AbstractAWSProcessor::initializeRegionAndEndpoint.  That situation predates your change, but adding EL causes the exception for those tests.
Instead, what would you think about the treatment given to REGION in that same method (AbstractAWSProcessor.java, ~line 210)?
protected void initializeRegionAndEndpoint(ProcessContext context) {
    // if the processor supports REGION, get the configured region.
    if (getSupportedPropertyDescriptors().contains(REGION)) {
        final String region = context.getProperty(REGION).getValue();
        if (region != null) {
            this.region = Region.getRegion(Regions.fromName(region));
            client.setRegion(this.region);
        } else {
            this.region = null;
        }
    }

    // if the endpoint override has been configured, set the endpoint.
    // (per Amazon docs this should only be configured at client creation)
    final String urlstr = StringUtils.trimToEmpty(context.getProperty(ENDPOINT_OVERRIDE).evaluateAttributeExpressions().getValue());
    if (!urlstr.isEmpty()) {
        this.client.setEndpoint(urlstr);
    }

}

The client is only modified when REGION is explicitly included on the concrete processor class.  We could add a second if (getSupportedPropertyDescriptors().contains(ENDPOINT_OVERRIDE)) {... protecting the expression language from being evaluated for ENDPOINT_OVERRIDE.  There is a similar, but different, approach used for PROXY_HOST on line 193 if (context.getProperty(PROXY_HOST).isSet()) {....
Now that I've made it this far, I'm not sure why there isn't such an if statement even without the expression language, like REGION.  Maybe I'm missing something?  Is this already familiar to you?

@jvwing Your suggestion sounds reasonable, I don't like all of the unrelated runner.setValidateExpressionUsage(false) either! I will update.

Thanks again, @tequalsme.  This has been merged to master.


Experiment to compile to 2.12 and cross to 2.11, drop 2.10.

removed all the straight deprecations
added access to sun.misc.Unsafe in Util - removed in 2.12
might be useful if anyone wants to update the library for 2.12
there are many other macro code deprecations that would take time to remove

Compiles except for benchmark and tests. If the build (project/Util.scala) is changed to 2.11.8 only, everything compiles and the tests run so clearly there are some differences when using 2.12.1 that don't work. I suspect that there is still a reference to scala.concurrent.util.Unsafe.instance. This would work in 2.11 but not 2.12.
Note: I used whitebox macros.

This is the sign of scala.concurrent.util
[info]     val pickle = data.pickle
[info]                       ^
[info] /Users/eric/workspace/pickling/benchmark/SparkLR.scala:32: genPickler is not a valid implicit value for scala.pickling.Pickler[spark.util.Vector] because:
[info] hasMatchingSymbol reported error: object util is not a member of package concurrent

You have a typo with "picking" instead of "pickling" in the second commit. It compiles afterwards.

Thanks for the tip, compiles now with 3 test failures.

The following 3 tests fail probably due to 2.12 lambda encoding differences.

[ ] AnonfunBinaryTest
[ ] AnonfunJsonTest
[ ] Transient2SparkTest


doppelgreener: Blacklist Coupon4all.com

doppelgreener requests the blacklist of the website Coupon4all.com. See the Metasmoke search here

!!/approve


enhancement cancel loading tasks directly without retrying when timeout exceeded

Proposed changes
As title.

run buildall

run buildall

run buildall

run buildall


Fix list termination in FAQ error_log

This PR resolves issue https://github.com/corona-warn-app/cwa-website/issues/3229 "Wrongly terminated list in FAQ #error_log"
In the first unordered list (<ul>) in

https://www.coronawarn.app/en/faq/results/#error_log and
https://www.coronawarn.app/de/faq/results/#error_log

the order of the closing tags is corrected to be </li></ul>.

The checks are failing due to a network error:
npm ERR! URL: https://download.cypress.io/desktop/10.11.0?platform=linux&arch=x64
npm ERR! Error: Failed downloading the Cypress binary.
npm ERR! Response code: 524

The checks are failing due to a network error:
npm ERR! URL: https://download.cypress.io/desktop/10.11.0?platform=linux&arch=x64
npm ERR! Error: Failed downloading the Cypress binary.
npm ERR! Response code: 524

Huh.. that is weird. Error 5XX are usually not on our end. I will try again in a bit.


Expose paths constants in API

From mail, from Erich:

A nit, it currently only works in the stable product:
privateextensionsPath: string= path.join(os.homedir(), '.vscode', 'extensions');
we should provide some API/constants for the product specific paths so that extensions do not have
to do path-math and getting it wrong.

a workaround would be to use extensionPath https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts#L2672

Plan is to encourage using extensionPath

Instead of adding another API constant for this special case, I proposed to use the extensionPath to figure out the install location: https://github.com/webstp/extension-manager/issues/5


RDKTV-13125: WPEFramework timeout during shutdown

Reason for change:Due to maintenance running the task seems to be
blocked.
Test Procedure:Refer Ticket.
Risks: Low

Developer Testing in progress. Do not merge.

Created https://github.com/rdkcentral/rdkservices/pull/2077


Address clippy warnings

I couldn't figure out how to remove the extern crate with the rename here. I read https://doc.rust-lang.org/nightly/edition-guide/rust-2018/module-system/path-clarity.html#renaming-crates, but couldn't get it working. Possibly it's because I needed to edit alot more files, but didn't feel I should have to do that. So I also tried https://doc.rust-lang.org/1.28.0/cargo/reference/unstable.html#rename-dependency, but couldn't get it working either. So I just turned off the lint in one spot ...
Also the config_toml_parser could be broken out a bit but didn't seem like a big deal to just disable the lint for now.

You may also want to add:
#![warn(rust_2018_idioms)]

...to the top of lib.rs

You may also want to add:

I'm using cargo clippy --all --all-targets -- -Dwarnings -Drust-2018-idioms which is what's being run in CircleCI, which presumably achieves the same result?


How many epochs

Hello，i‘m trying to run the training code ,but i find that the max_epochs: is setted to -1。it will be grateful if you can tell me how many epoches did you set and how many images did you use each epoch .thanks !!

Hey, buddy. I can read your training script. There was a mistake when I was getting ready for training.


JPA tests and native-image build changes

Added small set of JPA integration tests to verify MP and native image.
Found 3 issues with loading entity beans and session initialization. Those were fixed so tests pass with native image too.

@romain-grecourt This PR was not ready for review so many things were made just to work somehow. I'm doing final cleanup now. Will let you know when it's ready for final review. :)

Think it's time to review this PR.

No need to squash manually, GitHub can do that for you automatically with the "Squash and merge" option.

Resolves #2054


Running npm start does not generate the build

Hello, I ran into a weird issue while trying the generator. When i run gulp through npm, it doesn't generate the build folder. However if I run gulp directly, everything works as expected. I was wondering if it was an issue with my  config or if it was like this for everyone.
Here's how to reproduce the issue :

mkdir something; cd something;
yo angular2
rm -r build
npm start

It launches the browser and the browser say "Cannot GET / "

you need to run gulp serve or better yet gulp dev

So if I understand properly, npm prevents gulp from messing with the file system? Interesting!

Apologies for no response on this, will be taking a look over the weekend to shore up some of these issues.


How does rand work?

I'm trying to generate random integers, but they are always the same each time I run the program. For instance, if I have the one-line program (that I called rand.nit)
print(1000.rand)

then, on my computer, I always get 483:
 [graphs] blondin_al [~/Applications/nit/lib/graphs]
 $ nit rand.nit
483

 [graphs] blondin_al [~/Applications/nit/lib/graphs]
 $ nit rand.nit
483

 [graphs] blondin_al [~/Applications/nit/lib/graphs]
 $ nit rand.nit
483

 [graphs] blondin_al [~/Applications/nit/lib/graphs]
 $ nit rand.nit
483

Even if I add the srand command before running the program, I still always get 483.
What am I doing wrong?

Hi,
If you do call srand (which should not be necessary since it is automatically called since PR #916), you should indeed get different values, which do seem to work on my machine
$ ./rand
657

$ ./rand
509

The only difference I can spot is that you're using the interpreter, and well, he might very well be broken.
Though, on my machine there seems to be no such problem:
$ nit rand.nit
12

$ nit rand.nit
369

$ nit rand.nit
229

So, I'm not sure, if I recall correctly, you work on OSX right ? This would surprise me but this could be an environment-related issue.
If someone could test this too on a mac, we'd be sure (ping @Tagachi)

Yes, I'm on Mac OS 10.10.3 (Yosemite).
But even when I dot nitc rand.nit && ./rand, I still get the same numbers.

It looks like srand is marked as obsolete on OS X. They recommend to use arc4random instead for rand, but it cannot be seeded and won't produce the same result. Still there is no reason it doesn't work, it must be a bug in the OS, searching for srand broken on OS X yields a lot of results.
@ablondin It's an ugly workaround but you can define locally a method to access arc4random:
fun arc4random: Int `{ return arc4random(); `}

Linking with #1388.

Or easier
redef fun rand: Int do return 9

http://dilbert.com/strip/2001-10-25


Fix hash changing

If a route doesn't have a hash and the next route does (and the paths are identical), then that should be considered a hash change. Or if a route has a hash but the next route _does not (and the paths are identical) then that should be considered a hash change.
Specifically this fixes an issue where if you're on /some/path and click an anchor link to /some/path#some-anchor the anchor wouldn't be jumped to, although the route would appropriately change. Subsequent changes to the anchor like from /some/path#some-anchor to /some/path#some-other-anchor would still work since there's an anchor in both cases.

@neilff mind giving this some 👀 ?


No Time No Wait

💥 Proposal
This  proposal is like
Only x hours are left for the March Long Challenge and Chef is only left with the last problem unsolved. However, he is sure that he cannot solve the problem in the remaining time. From experience, he figures out that he needs exactly H hours to solve the problem.
Now Chef finally decides to use his special power which he has gained through years of intense yoga. He can travel back in time when he concentrates. Specifically, his power allows him to travel to N different time zones, which are T1,T2,…,TN hours respectively behind his current time.
Find out whether Chef can use one of the available time zones to solve the problem and submit it before the contest ends.
Input
The first line of the input contains three space-separated integers N, H and x.
The second line contains N space-separated integers T1,T2,…,TN.
Output
Print a single line containing the string "YES" if Chef can solve the problem on time or "NO" if he cannot.
You may print each character of each string in uppercase or lowercase (for example, the strings "yEs", "yes", "Yes" and "YES" will all be treated as identical).
Constraints
1≤N≤100
1≤x<H≤100
1≤Ti≤100 for each valid i
Have you read the Contributing Guidelines on Pull Requests?
Yes
i am a gssoc'21 participant can you please assign this problem to me @bhav09
i will do this problem in c++ language

/assign


fix: Add specific error handling around git repo input

Adds error handling to return specific eval errors for known errors encountered with git repos and models missing.
This fix (with a new release of eval) must go in before: https://github.com/instructlab/instructlab/pull/1616

Note this PR is best reviewed ignoring whitespace: https://github.com/instructlab/eval/pull/52/files?w=1

Related to #36

Please resolve conflicts

Done, thanks!


onTokenRefresh() is triggered every time the app is opened

Describe the bug
If my understanding is correct, onTokenRefresh() should only be called when a new token is generated. However, while testing on iOS, this method observable is being called every time I close and reopen the application. It doesnt run the token method if I go from App -> Home Screen -> App. But if I go App -> Swipe to close app -> Reopen application then it runs (but it's still the same token instance). I thought this method should only run if the instance token actually needs to be changed?
I've confirmed that the token is not updating by comparing the token instance ID that is printed to XCode console to the one that is currently saved in my database.
To Reproduce
Steps to reproduce the behavior:
In my app.component.ts I subscribe to an auth method from firebase that returns a user object
this.auth.user$.subscribe(
        (user) => {
          if (user) {
            this.fcm.getToken(user)
          }
      })

in my fcm.service I then subscribe to the onTokenRefresh():
import { Firebase } from '@ionic-native/firebase/ngx';
constructor(public firebaseNative: Firebase) { }

  async getToken(user) {
    this.firebaseNative.onTokenRefresh().subscribe((instanceToken) => {
      alert('Token has been refreshed')
    })
    ...
  }

And every time I open my application, the Token has been refreshed text is printed to the alert.
Here's a video, every time I close out the app and reopen, the token is printed as an alert notice how the token is the exact same on each one but for some reason even though it's the same token that onTokenRefresh is being called..:
https://streamable.com/xawbe
Expected behavior
Token refresh method should only be triggered when a new token instance is generated. Such as when I'm deleting and reinstalling my app.
Screenshots
token instance shown in Xcode console:

token instance in my database:

Plugin Version
Run cordova plugin list to find out what version of cordova-plugin-firebase you are running with
cordova-plugin-firebase 2.0.5 "Google Firebase Plugin"
Desktop (please complete the following information):

OS: OSX
Browser [e.g. chrome, safari]
Version Mojave

Smartphone (please complete the following information):

Device: iPhone XR
OS: iOS 12.0.1

I am facing same issue. Please help!


Ignore VSCode files from git commit

Coverage remained the same at 93.137% when pulling 3ed4f398853d882c2290f2b6c768dd8e2ce5963c on aleung:master into d6dd9c350b391bde7ecc9c0ba14660ccbf394ce6 on vpulim:master.

Can you also remove the vscode files?

@jsdevel Which files do you refer to? There is no vscode file inside git repo at present. I send this PR because I'm using VSCode and I want to avoid VSCode auto generated files being added into my upcoming PRs. I believe it benefits other contributors who use VSCode as well.

I see.  I thought some were checked in.  Thanks!


Trace query service routes

TODO:

[ ] upgrade to released version of jaeger-client (currently using SHA from https://github.com/uber/jaeger-client-go/pull/117)

Coverage remained the same at 100.0% when pulling 0bed4586d9344dfed1d0b131f2a531e488c18191 on trace-query-service into 1465fd513cdcc24d2259fe0177488aa6bf061435 on master.


Beginnings of heatmaps

Purpose:
Adds heatmaps to ScottPlot 5
int width = 100;
int height = 100;

double[,] intensities = new double[width, height];

for (int x = 0; x < width; x++)
    for (int y = 0; y < height; y++)
        intensities[x, y] = (Math.Sin(x * .2) + Math.Cos(y * .2)) * 100;

WpfPlot.Plot.Plottables.AddHeatmap(intensities);

They now support transparency (using double.NaN):
double[,] intensities = new double[width, height];

for (int x = 0; x < width; x++)
    for (int y = 0; y < height; y++)
    {
        intensities[x, y] = (Math.Sin(x * .2) + Math.Cos(y * .2)) * 100;

        if (Math.Abs(x - y) < 5)
        {
            intensities[x, y] = double.NaN;
        }
    }

Still to do:

[ ] Customizable extent
[ ] Cell Alignment
[ ] Flip vertically
[ ] Customize interpolation mode
[ ] ClippingPoints? Is this API needed?
[ ] Colorbar (perhaps this is a separate plottable/renderable/somethingelseable?)

I've added a ColormapBase class to handle repeated logic within the colormaps.
I'm also unsure about how we handle updating, currently the user has to manually call Update() to update the cached image. With the current implementation (and likely any future implementation) getting rid of the cache is pretty unperformant.
We could use setters to update the cache automatically, in an earlier implementation of this class I used this to update the cache when the Intensities array changed. However, there are a lot of properties that could impact rendering:

Colormap
CellAlignment
Extent
FlipVertically
Smooth
Intensities

More perniciously however, modifying an element in the Intensities array without reassigning it will not call the setter. So what we probably need to do is create a data class which alerts us when the array is modified in place. I didn't want to start on this without checking in first, because in v4 we were happy to just make the user call Update

getting rid of the cache is pretty unperforming.

in v4 we were happy to just make the user call Update

Cashing is more performant, but it's not what the rest of the plottables do... For most plot types, users expect to be able to change the data they pass in and have the changes reflected on the plot automatically.
Not caching data would be more in-line with the principle of least astonishment. Maybe caching could be an optional opt-in feature for users who actually need/want the performance enhancement?

Tying-up a couple loose ends,

ClippingPoints? Is this API needed?

It seems okay without it

Colorbar (perhaps this is a separate plottable/renderable/somethingelseable?)

Let's do this a lot later... I'm still deeply changing how plot layouts work (e.g., #2058) so I definitely want to push this off.


Extract Load/SaveTree/JSONUnpacked from repository

What does this PR change? What problem does it solve?
This PR splits the following functions from the repository:
SaveJSONUnpacked(context.Context, FileType, interface{}) (ID, error)
LoadJSONUnpacked(ctx context.Context, t FileType, id ID, dest interface{}) error
LoadTree(context.Context, ID) (*Tree, error)
SaveTree(context.Context, *Tree) (ID, error)

Especially for the tree blobs, but also for snapshots the repository has no knowledge of what data they contain. This is not surprising as these blobs are part of the snapshot data model, whereas the repository is just responsible for managing pack files.
For consistency also convert all other data types to provide load and save methods.
Was the change previously discussed in an issue or on the forum?
No.
Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[x] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM!

Then let's merge this.


Write longer wait voice statements to overcome wait time / latency

See also

#22

Seems that the wait file is played and just after that STT is performed, so it just informs the user and does not bridge waiting time. Have to do more debugging.


Add preference for changing the details panel's side

Hi @mrvladus,
Thanks for maintaining this great project! I think that the details panel to the right feels more natural than the current design (#129), so I've implemented it and updated the two screenshots.
EDIT: I've added a new section in the preferences for toggling between the left and right details panel, read here.

@mrvladus I found this comment in #113 so I started implementing the UI for switching the details panel side:
Video
I guess the only thing that's missing are live updates for the task lists in the view stack (the toggle button should change its icon and position in the toolbar).
What do you think about it so far?

Hi! It looks very good but it needs a few tweaks. I'll write them now.

We can have two toggle buttons in headerbars and bind their visibility to gsettings

Ah yes, thanks! So then I'll look into updating the toggle buttons.

Nice job!


Failed to upload when using from Work Zone

Failed to upload files.
Relevant to double slash // between serviceUrl and path?
Sometimes GET contentType takes some time. Is it relevant?

Changed code 07b7907476665c45b39d661abb91557879fae216 and resolved issue now. Not sure this change is root cause.


Add a Google Tables example Pack

Wanted to have a sample Pack that demonstrated how to do two-way sync with a dynamic sync table. Got a bit more involved than could easily fit in a single file, so adding it to this repo.
When reviewing, make sure to load the diff in convert.ts.

Ping @chris-codaio.


inheritdoc normal tag

In https://docs.phpdoc.org/guides/inheritance.html#the-inheritdoc-tag it is said

we are working to include a new (normal) tag in the PHPDoc Standard @inheritDoc that will serve that purpose.

Seems no issue has been submitted following https://github.com/phpDocumentor/phpDocumentor2/pull/1612#issuecomment-305889652 so here I go.
Could it be added to v3?

Inheritdoc is under discussion in psr-5. We are aware of the unclear specs of the interitance of docblocks and their tags.
First of all the current behavior of phpdoc v3 and v2 need to checked. To see how inheritdoc works at this moment. In the past years we have seen several misinterpreted usecases in the wild. Adding another tag wouldn't make it much clearer.
I cannot state that we will implement a new tag for this purpose at the moment.

I cannot state that we will implement a new tag for this purpose at the moment.

In that case as {@inheritdoc} seems to be widely used as a block tag will it be considered as valid?

Yes, we will keep support for {@inheritdoc} but at this moment it is unclear which tags will be included in the inheritance. But when things are changing that won't be done without a release of PRS-5 :-D so you are safe to use {@inheritdoc}


Add --no-ssl-verify to bbs2gh commands

Fixes #864

[x] Did you write/update appropriate tests
[x] Release notes updated (if appropriate)
[x] Appropriate logging output
[x] Issue linked
[x] Docs updated (or issue created)
[x] New package licenses are added to ThirdPartyNotices.txt (if applicable)

Description
This PR adds --no-ssl-verify option to migrate-repo and generate-script commands for bbs2gh to support migrating form servers that use self-singed SSL certificates.

Looks great! Think we could add a warning to the log output about skipping SSL?
For what it's worth, a lot of companies roll their own internal CA, and as long as the CA's chain of trust is present in the user's trusted certificates, the server certificate should validate. Self-signed CAs will also cause SSL validation issues, but these are not as common for most companies that I've witnessed 🙂

Not a bad idea, but since gei doesn't spit out a warning I guess for consistency bbs2gh needs to do the same.I guess ppl who use this flag know the risks too.


Update Ember-CLI to 0.2.7

No issue

updates Ember-CLI to 0.2.7

@jaswilli @rwjblue I started the update process on this and ran into a couple of issues.
I first tried updating to 0.2.7 directly, and got this error when running grunt init:
ENOENT, no such file or directory './dist/assets'

(this was during the ember build script)
So I decided to try upgrading incrementally, going by each Ember version. The update to 0.2.3 went perfectly fine, no issues. Then I tried upgrading to 0.2.4, and got the same error as I did upgrading to 0.2.7 directly.
I tried grunt clean to remove dependencies and re-installed everything. Still giving me the same issue. I only made the changes suggested by the ember init command, which included mostly updating bower & npm dependencies.
Any ideas?

This sounds like what @halfdan was talking about when we were discussing grunt dev being a bit broken, which I wrote up in #5322

Newer versions of ember-cli won't recreate dist/ for you.  The easiest thing to do is adjust the glob path for the clean:built task in Gruntfile.js to be 'core/client/dist/*' instead of 'core/client/dist/** so that the dist folder itself isn't removed.

@jaswilli I just tried that, and it also removes the /dist/assets/ folder, which causes the issues

it still removes the /dist/assets/

'!core/client/dist/assets',
'core/client/dist/assets/*'

There's still some deprecation errors being thrown, but as far as I can tell, none of them are within the Ghost ember application.
The biggest one so far is with Simple-Auth: https://github.com/simplabs/ember-simple-auth/issues/517

This PR seems to have a genuine test failure.

Yeah I'm trying to figure out exactly what it is

@ErisDS I'm not sure what specifically was causing the test error, but I think the ember unit tests were doing something weird with the build, causing casper tests afterwards to fail. I switched the order of the casper tests and the ember tests, which seemed to fix it locally.

If someone can restart the one Travis failing build I think this one's good to go

I switched the order of the casper tests and the ember tests, which seemed to fix it locally.

It's good that you figured out a way to make the tests run to completion but we're going to have to figure out why these changes caused the tests to fail that way.  We can't just move some things around and hide the problem--that's just asking for trouble down the road.

@jaswilli I figured out the error.
As it turns out, in core/client/config/environment.js, the ghost css file was (unecessarily) set to be minified during ember unit testing, resulting in a ghost.min.css file being outputted to the built directory. Because the development server used during the Casper tests looks for just ghost.css, the server would fail to start, thus causing the casper tests to fail.

So switching the test order does the trick, and it is because the `shell:ember:test

shell:ember:test command modifies the ember environment, changing the rootElement, baseDir, locationType, etc. These changes persist even after the ember build has completed, resulting in issues with the Casper tests.

So why isn't this an issue on master right now?
We can't just hide the problem by moving the order of the tests around.  Either the root cause of the problem has to be identified (i.e., why is it manifesting on this PR but not on master?), or safeguards have to be put into place (like rebuilding the ember app as a part of the functional test tasks) before this can be merged.

I'm almost certain this is related to the issue with the postBuild order hook, or more accurately, the changes to the asset delivery add-on that were made. In the previous version, the old files weren't deleted from the built directory when shell:ember:test was called, there was just a new file ghost.min.css that was outputted along with the files built by grunt init.
I'll add a call to shell:ember:dev before the functional tests are run. IMO that is the best way so that one can run npm start immediately after grunt validate, should the need arise.

@ErisDS @jaswilli Just rebased this. Per the comment above ^ I added a call to shell:ember:dev before the casperjs tests in order to counteract whatever changes are made by shell:ember:test.

What happened with the stuff about ghost.min.css being generated during an ember test build?  It seems like that should still probably be removed?

@jaswilli It could be, but that wasn't the only issue. The other testing variables, such as rootElement, also modify the environment, resulting in failure of casperjs tests afterwards, so the ember rebuild is still necessary. I'm pretty sure the minified css speeds up the testing too.


bump sigs.k8s.io/karpenter

Fixes #N/A
Description
bump sigs.k8s.io/karpenter
How was this change tested?
NA
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 78.676%

Totals

Change from base Build<PHONE_NUMBER>4:
0.03%

Covered Lines:
5977

Relevant Lines:
7597

💛  - Coveralls


Youtube channels

All youtube channels links in the bottom of readme document does not work, Please check them out!

okay, thanks for your report. The issue is resolved.


⚠ ClamAV has degraded performance

In 6f7e91c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 175 ms

Resolved: ClamAV performance has improved in 39bd42e.


#2241 Event Details (Admin) - Hide Create New Task button when Event …

…in Past

@redware are you able to make this small adjustment so that we can merge?

Looks like this got implemented in #2305


Stack acquiring ownership over foreign resources (f.e. s3 bucket)

Found what seems to be a critical bug in creating s3 buckets (although not sure yet if it only happens on s3 buckets). When creating a bucket that already exists (was created manually or created by a different pulumi stack) pulumi will show 'created' and the stack will now reference that already existing bucket. Meaning we can have the same s3 bucket managed by different stacks.
Expected behaviour:
Pulumi should fail creating an already existing bucket (that is not managed by this stack).
Steps to reproduce:
Create 2 stacks with the same s3 bucket:
new aws.s3.Bucket('test', { bucket: 'some-unique-name' })
Run the first. Run the second. See stack resources are pointing to the same bucket.
Pulumi CLI version: 1.3.1, Pulumi SDK (Node) version: 1.2.0, Pulumi AWS version: 1.5.0

This appears to be due to https://github.com/terraform-providers/terraform-provider-aws/issues/3307, which is ultimately due to a backward compatibility setting in only the us-east-1 region of AWS.  I confirmed that this does not repro in other regions.

The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except us-east-1 (N. Virginia). For legacy compatibility, if you re-create an existing bucket that you already own in us-east-1, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).

It's theoretically possible this could be fixed in the upstream provider via the issue linked above - but may be that this cannot be fixed correctly without a breaking change to the AWS API.


State should not be Abstract

Allow States to be instantiated without subclassing by removing their Abstract status. Inline initialization or property assignment can be used where behavior needs to be specified.
Essentially State is a POCO with no state management logic itself. This will be easy to accomplish thanks to #8
This is an effort to make it easy to create bespoke states without requiring a class to be written for each.
Projects already working around this:
public class InlineState : State
    {
        public Action StartState { get; set; } = () => {};
        public Action EndState { get; set; } = () => { };
        public Action UpdateLogic { get; set; } = () => { };

        public override void Start() => StartState();
        public override void End() => EndState();
        protected override void UpdateState() => UpdateLogic();
    }

Alongside converting the State into a concrete class, it is possible to initialize the state event logic through the constructor.
It would be nice to have a version that doesn't rely on constructor parameters and more readable as a result, though at least labeling constructor arguments is an option:
            var state = new State(                 start: () => {},                 update: () => {},                 end; () => {}             );


How to render video?

Hi folks,
Thanks for this awesome work. I'm wondering how to render the "spiral" videos demonstrated in the project page?
Any reply would be appreciated!
Best,
Peihao

Hi, you can interpolate between the data cameras to get a new pose sequence, and then render each pose to get the final video.


How to run

Hey there! I am new to Java, how do I run the app?

Hello, as far as I remember it is only as module to your bot
Пт, 31 мая 2024 г. в 02:55, Carlos Veryan @.***>:

Hey there! I am new to Java, how do I run the app?
—
Reply to this email directly, view it on GitHub
https://github.com/EvgeniiSiniuk/tg-inline-calendar/issues/4, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BASAIUW3XIGJEL4MWLFGLLDZE635NAVCNFSM6AAAAABIR2G4HWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDMNZSG4YDKOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


ChangeRecord behavior right after deletion

Remark: record is of type ChangeRecord.
Current behavior:
record.new might be nil even though record.old is nil too.
This will happen if you spawn and then despawn entity right away in the same frame.
Presumable behavior:
record.new will be populated, record.old will be populated.
Maybe even better to run for once queryChanged with new, and then with old data.
My thoughts:
I'm not sure whether it's intended, but from my P.O.V it's not intuitive behavior.
However I do understand that it might become even more confusing if you change current behavior, but at least documentation of current behavior would be great.

This is intended behavior and it's documented with ChangeRecord. If both are nil that indicates that since queryChanged last ran it was both created and destroyed. It would be incorrect to populate either field in that scenario; the last time you saw the state of the world it wasn't there, and in the current state of the world it's not there.


calculate stats on real data

check that nothing broke after changing total, panel, and genotyped.

https://github.com/agladstein/SimPrily/commit/335a5925b33fa61c577ddd38273651bdd814235b


Add DiffFile#added_lines

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Ensure all commits include DCO sign-off.
[ ] Ensure that your contributions pass unit testing.
[ ] Ensure that your contributions contain documentation if applicable.

Description
DiffFile#added_lines returns the source lines added and their respective line numbers.
My use case involves adding Danger warnings to PRs based on inserted lines.
Wanted to get some feedback before putting more work into it (tests, etc).

I think the idea of this PR looks fine.  I'd like to generalize it to return both added and deleted lines which seems simple enough.
Should we introduce a new abstraction to represent a 'difference line' to encapsulate the line, line number, and maybe if the line was added or deleted?
I added other comments inline.

Sure, I had considered that too, although I thought it had some further-reaching consequences I was avoiding:

Ideally in the long run, the diff-parsing of my private DiffFile methods and process_full_diff would be consolidated, as they conceptually share a single responsibility.
It looks like there was an intention to refactor process_full_diff?
If I were to implement DiffLine without touching process_full_diff, I'd likely be adding a decent amount of tech debt, and every line in the diff would also end up getting unnecessarily parsed twice.

Your thoughts? Btw, I don't see any comments inline.

@Kache sorry, I didn't submit the conversation entries I had made -- they are there now.
I agree about consolidating the parsing is probably the way to go. Would be nice if people who did not need access to individual lines of diff did not have to pay the price of parsing them.

Hi @jcouball, I've updated this PR in accordance everything's that's been discussed so far.
The most sizable part is the parsing refactor, which I've grouped together with a non-ff merge:

Let me know if you'd prefer it as a separate PR that merges first. Note that it's not a perfect/pure refactor, there are a few minor changes that may warrant evaluation.
In any case, I've organized the changes as atomic commits for ease of review. All tests should pass at every commit.

Update: I'm going to try an alternative -- rather than having both #added_lines and #deleted_lines, to have a single #each_diff_line (aliased by #each) that returns both as interleaved DiffLine objects.


Server Crash / Freeze with latest Terrain Control

https://hastebin.com/putazomihi.md
Terrain Control Dev build from 12th April 2017
Server Crash with latest Terrain Control (it's the only plugin I have updated today, so assuming this must be terrain control). This crash never happened before.

It's just that terrain generation is taking too long, and the server times out. You can increase the timeout time using the setting timeout-time in the spigot.yml file.


Implement read/write reserved state and query_commit_path in RawRepository

sorry for the miscommunication.
can you update according to #196 please?


uptdate to last google/brotli?

Can you please update to last google/brotli?

That sounds like a good first pull request :+1:


add detail on T205

Searches to satisfy:

[x] https://topology.pi-base.org/spaces?q=Pseudoradial%2B~Radial
[ ] https://topology.pi-base.org/spaces?q=Pseudoradial%2B~Sequential
[ ] https://topology.pi-base.org/spaces?q=Radial%2B~Fréchet Urysohn

Regarding S36 ($\omega_1+1$), it's fine to assert that P163 (card. at most continuum).  Do you think it might be worth adding "card. = $\omega_1$" as a pi-base property at some point?

Added T216: LOTS ==> radial.  I could not find a reference with a fully spelt out proof, but it's simple enough, so I picked the article that introduced radial spaces, which mentions the result.  Please see how it looks.
That allows to automatically deduce that $\omega_1+1$ is radial.

Some comments about T210 and T211 (countable + radial ==> Frechet-Urysohn).  It could be more subtle than it looks, as it's not true that "every transfinite sequence is a countable sequence", due to repetitions.  I think the following would do it, but maybe you have a shorter argument.
So assume there is a point $p\in\overline A\setminus A$ and a transfinite sequence $(x_\alpha)_{\alpha<\lambda}$ in $A$ that converges to $p$.  We have to show that there is an ordinary sequence that converges to $p$.  Wlog we can assume that $\lambda$ is infinite and of smallest cardinality possible, so in particular it's a regular cardinal.
If one of the $x_\alpha=a\in A$ is repeated cofinally many times, then extracting the subsequence of all the elements with value $a$ gives a constant (transfinite) sequence that converges to $p$.  Then every nbhd of $p$ contains $a$ and the ordinary sequence $(y_n)_{n<\omega}$ with each $y_n=a$ also converges to $p$.
Otherwise, for each $a\in A$ the set of indices $I_a=\{\alpha<\lambda: x_\alpha = a\}$ is not cofinal in $\lambda$, that is, $I_a$ has cardinality smaller than $\lambda$.  But there are only countably many values $a\in A$.  So we get a partition of $\lambda$ into countably many sets, each of cardinality smaller than $\lambda$.  If $\lambda$ were uncountable, that would contradict the fact that $\lambda$ is a regular cardinal.  So necessarily $\lambda=\omega$ and our original sequence was an ordinary sequence.
Note: The same argument works if we replace countable with locally countable.

Regarding S36 (ω1+1), it's fine to assert that P163 (card. at most continuum). Do you think it might be worth adding "card. = ω1" as a pi-base property at some point?

Yes, along with a theorem card = omega_1 => card <= mathfrak c.

Some comments about T210 and T211 (countable + radial ==> Frechet-Urysohn). It could be more subtle than it looks, as it's not true that "every transfinite sequence is a countable sequence", due to repetitions. I think the following would do it, but maybe you have a shorter argument.
So assume there is a point p∈A―∖A and a transfinite sequence (xα)α<λ in A that converges to p. We have to show that there is an ordinary sequence that converges to p. Wlog we can assume that λ is infinite and of smallest cardinality possible, so in particular it's a regular cardinal.
If one of the xα=a∈A is repeated cofinally many times, then extracting the subsequence of all the elements with value a gives a constant (transfinite) sequence that converges to p. Then every nbhd of p contains a and the ordinary sequence (yn)n<ω with each yn=a also converges to p.
Otherwise, for each a∈A the set of indices Ia={α<λ:xα=a} is not cofinal in λ, that is, Ia has cardinality smaller than λ. But there are only countably many values a∈A. So we get a partition of λ into countably many sets, each of cardinality smaller than λ. If λ were uncountable, that would contradict the fact that λ is a regular cardinal. So necessarily λ=ω and our original sequence was an ordinary sequence.
Note: The same argument works if we replace countable with locally countable.

I like replacing countable with locally countable.
I think my hand-waving should be recoverable, but since it's not obvious to me how to do it at the moment, I'll incorporate your arguments into an update.

Actually let me know if you'll let me get away with b75ef7dd5faabd938abdf20def03ea032ee469d1

Actually let me know if you'll let me get away with b75ef7d

Hmm, I don't think that really works.  Can you ask a general question on mathse and I'll answer it, and then we can make reference to that?  Maybe something along the following lines: Suppose $X$ is a countable topological space and $A\subseteq X$. Suppose a point $p\in X$ that is the limit of a transfinite sequence $(x_\alpha)_{\alpha<\lambda}$ of points of $A$, where $\lambda$ blah blah ... blah blah. Is there an ordinary sequence of points of $A$ that also converges to $p$?

Yeah, given there's been this much discussion, airing out on math.SE feels correct: https://math.stackexchange.com/questions/4785088/

I updated the list of searches above.
The last one: ample of space that is both radial and sequential, but not Frechet-Urysohn may not be easy to find.  The Encyclopedia of General Topology chapter mentions that [compact + radial + sequential ==> Frechet-Urysohn] without giving any reference.  We'll have to find more about it.  But that seems to imply that without compact there could be counterexamples.

I added the MathSE reference at 4679c8d but note that I did keep the claim that transfinite sequences contain countable subsequences, as I think that's still correct: take the tail end of the sequence in the countable neighborhood, then either it has countable cofinality and use any countable subsequence, or it must be eventually constant and use a constant sequence.

I suggest adding compact + radial + sequential ==> Frechet-Urysohn and a (presumed) counterexample to radial + sequential ==> Frechet-Urysohn in a future PR.

I added the MathSE reference at 4679c8d but note that I did keep the claim that transfinite sequences contain countable subsequences, as I think that's still correct: take the tail end of the sequence in the countable neighborhood, then either it has countable cofinality and use any countable subsequence, or it must be eventually constant and use a constant sequence.

It's good you added the reference.
But I think the current text: By {P93}, every converging transfinite sequence contains a converging countable subsequence. needs to be changed.
What I am objecting to is the language in terms of subsequence.  Writing sequence for"transfinite sequence" here, to me the notion of subsequence  means a "cofinal subsequence".  That is we have a sequence indexed by some limit ordinal $I=\lambda$, and then we pick of cofinal subset of the ordinal (i.e., pick an index set $J\subseteq I$, but $J$ itself has the order type of some ordinal $\mu\ge \mathrm{cof} \lambda$) and that gives our subsequence.  But if $J$ is not cofinal in $I$, that does not qualify as a subsequence.  So now going back to the theorem, if we have a transfinite sequence indexed by an uncountable regular cardinal $\lambda$ for example, there is no such thing as a "countable subsequence" of it, as $\lambda$ has no countable cofinal subset.
Now I know what it's trying to say.  But in your comment above: or it must be eventually constant and use a constant sequence, that constant (ordinary) sequence is what we want, but is not a "subsequence" of the original transfinite sequence (so the current text of the theorem is not valid for that case).  Also it's not the case that the original sequence needs to be eventually constant.
We could still say something along the lines of your comment above.  How about the following maybe?
Given a transfinite sequence with values in a set $A$ and converging to a point $p\in X$, first replace it by a tail end belonging to a countable neighborhood of $p$ by {P93}.  Then if the sequence has countable cofinality, extract a countable subsequence converging to $p$.  Otherwise, some value in the sequence repeats cofinally, which implies that value belongs to all neighborhoods of $p$. In this case, $p$ is the limit of an (ordinary) constant sequence with that value.  In both cases we get a countable sequence in $A$ that converges to $p$.  See {{mathse:4785088}} for details.

Actually, we could shorten this quite a bit, as long as we don't use the word "subsequence".  Like the following for example:
Given a transfinite sequence with values in a set $A$ and converging to a point $p\in X$, first replace it by a tail end belonging to a countable neighborhood of $p$ by {P93}. So we can assume without loss of generality that $A$ is countable.  Then, as explained in {{mathse:4785088}}, there exists a countable sequence of points of $A$ converging to $p$.

I like your suggestion for wording. (Of course, I meant to imply that a subsequence can be any restriction of the domain of the transfinite sequence, but this does not preserve limits, so I understand the disagreement.)


Build Failure: Error while running OPI from version 0.4.1 or main

Hello, I'm encountering an issue while trying to run OPI from version 0.4.1 or the main branch. The problem arises during the build process when attempting to build ord. Specifically, I'm receiving the following error:
cd ord; cargo build --release;  returns on 0.4.1 and main branches
   Compiling time v0.3.31
error[E0282]: type annotations needed for `Box<_>`
  --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.31/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
help: consider giving `items` an explicit type, where the placeholders `_` are specified
   |
83 |     let items: Box<_> = format_items
   |              ++++++++

For more information about this error, try `rustc --explain E0282`.

Seems like an issue with the time package, try this for now:
cargo update -p time
It builds with time v0.3.36.

Thanks, it fixed the build.


Ocaml packages fix build on darwin

Description of changes

While testing https://github.com/NixOS/nixpkgs/pull/197367 I saw that many other package was broken with the same kind of error so I did a pass to fix the same error in multiple packages.
build log before this PR:
error: builder for '/nix/store/vihic2dgbd98lrl0sas2c647c6fz7dsz-ocaml-libvirt-<IP_ADDRESS>.drv' failed with exit code 2;
       last 10 log lines:
       > like 'CDEFLMPSUVYZX', is deprecated.
       > Use the equivalent signed form: +C+D+E+F+L+M+P+S+U+V+Y+Z+X-3.
       > Hint: Enabling or disabling a warning by its mnemonic name requires a + or - prefix.
       > Hint: Did you make a spelling mistake when using a mnemonic name?
       > ocamlmklib -o mllibvirt libvirt_c.o libvirt.cmo libvirt_version.cmo -L/nix/store/nv200j8plka6f5knmnsx8wqx7736pq43-libvirt-8.10.0/lib -lvirt
       > ld: file not found: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation for architecture x86_64
       > clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
       > make[1]: *** [Makefile:68: mllibvirt.cma] Error 2
       > make[1]: Leaving directory '/private/tmp/nix-build-ocaml-libvirt-<IP_ADDRESS>.drv-0/source/libvirt'
       > make: *** [Makefile:31: all] Error 1
       For full logs, run 'nix log /nix/store/vihic2dgbd98lrl0sas2c647c6fz7dsz-ocaml-libvirt-<IP_ADDRESS>.drv'.

Things done

copied from what is done with cairo2
For reviewer:
nix build .#ocamlPackages.bjack .#ocamlPackages.ffmpeg .#ocamlPackages.ffmpeg-av .#ocamlPackages.ffmpeg-avcodec .#ocamlPackages.ffmpeg-avdevice .#ocamlPackages.ffmpeg-avfilter .#ocamlPackages.ffmpeg-avutil .#ocamlPackages.ffmpeg-swresample .#ocamlPackages.ffmpeg-swscale .#ocamlPackages.gstreamer .#ocamlPackages.labltk .#ocamlPackages.ocaml_libvirt

(might be quicker than nixpkgs-review)

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build ocamlPackages.ocaml_libvirt ocamlPackages.labltk ocamlPackages.gstreamer ocamlPackages.ffmpeg-avutil ocamlPackages.bjack ocamlPackages.ffmpeg-avcodec ocamlPackages.ffmpeg-avfilter ocamlPackages.ffmpeg-swscale ocamlPackages.ffmpeg-av ocamlPackages.ffmpeg-avdevice ocamlPackages.ffmpeg-swresample

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/794


docs: MAINTAINERS file and LGTM configuration

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

LGTM (ping @tiborsimko)

LGTM

LGTM


Create Sydney.json

Welcome @thomaseizinger , have a good one! :tada:

Thanks a lot! I am excited :)


earthengine authenticate

Error Logs:
Traceback (most recent call last):
File "~/anaconda/bin/earthengine", line 11, in
sys.exit(main())
File "~/anaconda/lib/python3.5/site-packages/ee/cli/eecli.py", line 63, in main
dispatcher.run(args, config)
File "~/anaconda/lib/python3.5/site-packages/ee/cli/commands.py", line 226, in run
self.command_dict[vars(args)[self.dest]].run(args, config)
File "~/anaconda/lib/python3.5/site-packages/ee/cli/commands.py", line 252, in run
token = ee.oauth.request_token(auth_code)
File "~/anaconda/lib/python3.5/site-packages/ee/oauth.py", line 56, in request_token
urllib.parse.urlencode(request_args)).read()
File "~/anaconda/lib/python3.5/urllib/request.py", line 163, in urlopen
return opener.open(url, data, timeout)
File "~/anaconda/lib/python3.5/urllib/request.py", line 464, in open
req = meth(req)
File "~/anaconda/lib/python3.5/urllib/request.py", line 1183, in do_request_
raise TypeError(msg)
TypeError: POST data should be bytes or an iterable of bytes. It cannot be of type str.
How I resolved it : I had to explicitly encode data parameter(urllib.parse.urlencode(request_args) ) for urllib.request.urlopen() from str to bytes and then had to again decode response variable from byte to str for refresh_token.

Can I see the code you're using here?

I made below changes in my code in oauth.py:
try: #Line 54
parm=str.encode(urllib.parse.urlencode(request_args))
response = urllib.request.urlopen('https://accounts.google.com/o/oauth2/token',parm).read()
response=bytes.decode(response)
refresh_token = json.loads(response)['refresh_token']
@jonparrott Does this help? Please let me know if you need any other input.

Oh, okay, I understand. This is not the API client you're using. You should report this issue over at https://github.com/google/earthengine-api.


test error

TypeError: unsupported operand type(s) for *: ‘NoneType’ and ‘float’ when I reason with pre-trained weights, what should I do about this?

Hi, I also encountered the same problem, have you solved it?


options.maxMatchLen should be camelCased

Closes #21

Hi @stevemao. Thanks for this! Have merged and published as 4.0.0. I've also added you as a committer and on the contributor list as part of our OPEN Open Source contribution policy.
Cheers!

Thanks @eugeneware

We should add a test for this option, too.


xds: Ignore HTTP filters if LDS resource is v2.

Also add a missing test from the fault injection PR, addressing a previously added TODO.

The "Interop ALTS Tests" failure looks like a transient failure fetching external dependencies.
The "Basic Tests ObjC Examples" failure is an infrastructure timeout.
Known issues: #25660


Add plugin create functionality.

- What I did
Add plugin create functionality.
- How I did it
Given a rootfs and a plugin manifest.json, create a plugin.
- How to verify it
Use docker plugin create to create the plugin. Once successfully create, you can enable it and use it. You can also docker plugin push to registry.
Signed-off-by: Anusha Ragunathan<EMAIL_ADDRESS>

How about using an image instead of a raw rootfs directory?
e.g.
$ git clone https://github.com/vieux/docker-volume-sshfs
$ cd docker-volume-sshfs
$ docker build -t vieux/docker-volume-sshfs-image .
$ docker plugin create vieux/docker-volume-sshfs --manifest /somewhere/manifest.json vieux/docker-volume-sshfs-image

@AkihiroSuda we discussed this already, we think it's a good idea, it's coming soon (in a separate PR)

LGTM ping @tiborvass

Apart from small optional nit, LGTM

ping @thaJeztah

LGTM

Any chance we could also update api/swagger.yaml with the new endpoint?

@bfirsh : Updated swagger.yaml and confirmed that yamllint is happy.

@bfirsh @thaJeztah : Updated with review comments on API. PTAL

@bfirsh @thaJeztah  : updated

swagger.yaml LGTM!

Do not merge until https://github.com/docker/docker/pull/27967 is merged
moving back to docs review to prevent trigger-happy's


export ReactChartJs

exports ReactChartJs rather than react-chartjs so we can simply call ReactChartJs rather than window['react-chartjs']

This seems like a small enough improvement one could submit a PR for. Would one change this file? https://github.com/reactjs/react-chartjs/blob/master/index.js

Hi Everyone, I believe this is specified in webpack and not in the source code itself. I am happy to take PRs.
That being said, my only concern with this request is that it may break other people's projects using window['react-chartjs'] if we change it. Unfortunately, I am a little hesitant with this change.
Please see:

Webpack Config
Compiled Source

Helpful resource:
Webpack >2.0 Doc


Add pre-release/dry-run mode for all workflows

Updated to specify that we want it for all workflows, noticing that the Rust/csharp workflows do not have dry-runs
Previous comment regarding Java: This would ideally just call Jreleaser which has a dry-run feature


Feature Request: Support Project Through GitHub Sponsors

I'd like the ability to donate some money to help support this project. It might only be enough for a cup of coffee or a cool brew, but I'd like to show my appreciation for your work here. Perhaps you can turn on GitHub Sponsors.

Hi @KenKodz,
Thank you very much for considering donating for my contributions! The request for GitHub Sponsors is currently awaiting approval :wink:

The request has been approved! :tada:


PyObjectProtocol::get_type_ptr()

This is a getter for ob_type, without instantiating a PyType.

What is the expected usage of this method?

It allows a user to optimize checking that two instances are the exact same type.

Thank you!


Outline can't find symbols, if asserts are present

Outline OK:

### Latest launches
GET /launches/latest

Outline broken:

### Latest launches
GET /launches/latest

?? status == 200

Environment:
VS Code 1.82.0
httpYac v6.6.4

already fixed with https://github.com/AnWeber/httpyac/pull/542. but I need to release it


Redo "Do not render in handleDownEvent"

Redo #4581 and implement something where renderers can get notified of hint changes without forcing a render.

It may not actually make sense to "notify" the renderer without rendering - since the hints are meant to be used during a render.  But it would be worth looking at how the information flows around and make sure we aren't abusing map.render().

Closing due to lack of activity.


SPIKE: Check rate/burst limit for Parse JS SDK on server side

The Parse Server seems to have a rate/burst limit for client request. As the Parse JS SDK is also being used on the server side, we should check whether we can surpass it (e.g. usage of master key, check for requests from localhost, ...) or if is already handled by Parse server.

No indication found for a rate/burst limit found in parse server code. The client SDK has a prop REQUEST_ATTEMPT_LIMIT which limits the number retries on failed requests for API calls to 5 in the default setting.
Rate limiting can therefore be implemented in a proxy / load-balancer in front of the application without effecting the server code.


Different service call results depending on where the service is called.

I'm trying to determine the start of the lowest price interval, based on the epex_spot.get_lowest_price_interval service call.
If I use this service call in the Developers tools:
service: epex_spot.get_lowest_price_interval
data:
  duration:
    hours: 3
  earliest_start: "07:00:00"
  latest_end: "16:00:00"

I get this response:
start: "2024-03-29T12:00:00+01:00"
end: "2024-03-29T15:00:00+01:00"
price_eur_per_mwh: 12.09
price_ct_per_kwh: 1.209
net_price_ct_per_kwh: 1.209

12:00 in localized time is correct!
But when I use the service call like this, in the config-file:
  - trigger:
      - platform: time
        at: 00:00:01
    action:
      - service: epex_spot.get_lowest_price_interval
        data:
          duration:
            hours: 2
          earliest_start: "07:00:00"
          latest_end: "16:00:00"
        response_variable: resp
    sensor:
      - name: start_laagste_prijs
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

Then the sensor.start_laagste_prijs gets a different value, that is wrong.

2 observations:

You have a duration of 3h in the developer tools and 2h in the config file.
2024-03-29T12:00:00+01:00 represents the same point in time as 2024-03-29T11:00:00+00:00. The first is timestamp includes a timezone offset of 1h which causes the difference.

HA displays timestamps in the entity status view with UTC timestamp (= timezone offset 0). But the timestamp is correct and if you display the sensor value in Lovelace (e.g. an entity card), it will also use your local timezone.

Any feedback on this?

I changed my Apex data generator as follows. This now seems to render the right result:
data_generator: >
      return entity.attributes.data.map((entry, index) => { return [new
      Date(entry.start_time).getTime(), ((0.2040 + entry.price_ct_per_kwh) *
      1.06  ) + (1.582+4.71756+0.20417+5.03288)]; }).slice(new
      Date(hass.states['sensor.start_laagste_prijs'].state).getHours(),new
      Date(hass.states['sensor.start_laagste_prijs'].state).getHours()+3);


Update HiFi4 nnlib to v2.5.0 from v2.4.1

Download HiFi4 nnlib from v2.5.0 instead of v2.4.1.
Minor code change is necessary due to an API change. Patches from https://github.com/tensorflow/tflite-micro/pull/711 was also re-generated.
BUG=#758
TESTED=
docker run --rm -v "$(pwd)":/opt/tflite-micro ghcr.io/tflm-bot/xtensa:0.1 /opt/tflite-micro/tensorflow/lite/micro/tools/ci_build/test_xtensa_hifi3z.sh

Tagging @cad-audio


Updating documentation for 'Submission summary statistics plus metadata'

Updated table rows with new SSF fields.

Agreed, but those changes had actually already been made - I did several commits in a row, so I hope you were checking the latest version. I can see all my changes here: https://github.com/EBISPOT/gwas-ui/pull/268/files


Remove pai-fs

Remove pai-fs.

Coverage increased (+35.4%) to 83.771% when pulling e5f5728e3d2519f41ab04ed3f8aac5b43adb220a on xiongyf/remove-pai-fs into 14cd30972ee19141c439dab933f4e0dad0ea477d on master.

Coverage increased (+35.4%) to 83.771% when pulling e5f5728e3d2519f41ab04ed3f8aac5b43adb220a on xiongyf/remove-pai-fs into 14cd30972ee19141c439dab933f4e0dad0ea477d on master.

Coverage increased (+35.4%) to 83.771% when pulling e5f5728e3d2519f41ab04ed3f8aac5b43adb220a on xiongyf/remove-pai-fs into 14cd30972ee19141c439dab933f4e0dad0ea477d on master.


Sidebar Slide-along keeping pusher content centered

I am trying to create a sidebar with animation Slide Along.
When the sidebar is hidden, the pusher content is centered with respect to the width. But when the sidebar is visible, the width of the pusher remains the same and there is an additional width from the visible sidebar. Hence the pusher content, which is still centered looks skewed to the right.
Here is an example. Initial Codepen
This is what I tried. My Attempt.
I am trying to keep the pusher content centered at all times.
Thanks.

The user will have to look at two different places in the browser or may be scroll horizontally depending upon the visibility of the sidebar.
invisible => pusher is in the center
visible => pusher is in the right
I just want to avoid this.

Maybe there should be another class which pushes the content but not off the canvas.