parserOptions.schema error for require-id-when-available rule

Describe the bug
Trying to validate queries in apollo client under gql tag results in  following error
Error while loading rule '@graphql-eslint/require-id-when-available': Rule 'require-id-when-available' requires 'parserOptions.schema' to be set and schema to be loaded
use the following eslintrc.json file
{   "root": true,   "ignorePatterns": ["**/*"],   "plugins": ["@nrwl/nx"],   "overrides": [     {        "files": ["*.ts"],       "processor": "@graphql-eslint/graphql"   },     {       "files": [         "*.ts"       ],       "parser": "@graphql-eslint/eslint-plugin",             "parserOptions": {                 "schema": "./apps/customer-api-federated/src/profile.graphql"       },       "plugins": [         "@graphql-eslint"       ],               "rules": {           "@graphql-eslint/require-id-when-available": "error",           "@graphql-eslint/no-anonymous-operations": "error"         }               }   ] }
Environment:

OS: windows
@graphql-eslint/...:3.9.0
NodeJS: 14.16.1

Hi @sujithgowda, to help you I need a reproduction repo or some debug information of your configuration.
Please install<EMAIL_ADDRESS>alpha version that includes debugging printing.
After installation run DEBUG=graphql-eslint:* eslint . and show your output.

I close this issue as I didn't receive a response


Tutorial harmonic oscillator configuration space

PR precedent #8
For #9
Added

tutorials for HO:

Why is this a separate PR, instead of being identical to the one of HO?

Why is this a separate PR, instead of being identical to the one of HO?

The first PR has too many files.


Add github action to install dependencies

Description
I noticed some issues running the install script again, so figured this could be useful. At the very least for me to check if it happens in a clean env.
I only see one other github action in the project so let me know if there isn't any interest in adding more.
Checklist

[x] The base branch of this PR is preview, rather than main

Ah just realized I need approval for the workflow to run. You can see the current install failure in my fork. happens locally as well.
https://github.com/djgould/continue/actions/runs/9021010813/job/24787377254

Hm yeah the approval is something we'll keep around for security reasons. Given this, I'm not sure it's super helpful to have the action here in the repo. Thoughts on a script instead to "remove-all-dependencies"? I don't disagree that the fresh start would be nice, and maybe we can just make it easy to do so locally. The other option is a local clone

As for the issue, it seems like a matter of explicitly declaring the dependency? My plan was to move to pnpm anyway, so in the process of doing that I'm sure we'll solve this

Given this, I'm not sure it's super helpful to have the action here in the repo

cool i'll close this then

Thoughts on a script instead to "remove-all-dependencies"

That would be great!

As for the issue, it seems like a matter of explicitly declaring the dependency? My plan was to move to pnpm anyway, so in the process of doing that I'm sure we'll solve this

Yeah I think it was just a missing dependency. Not sure how it slipped in. +1 for switching to pnpm

totally! commit incoming for the switch to pnpm


A bug in blog.cpp

In the blob.cpp: reshape function,we should allocate shape.sizesizeof(int) instead of KMaxBlobAxessizeof(int).
Is that right ?

cache the shape data memory so that we don't need to realloc the memory when shape changes.

Could I have your WeiChat so that I can consult with you ?

But if the size after reshped  bigger than KMaxBlobAxes, it will realloc or not ?I print the KMaxBlobAxes and the result is 32 .In my thought,if I reshape a bigger size like (1,1,1,33),there should be a core dump.I try it but there is no mistake about memory.What's the matter ??Thank you in advanced.

kMaxBlobAxes is the maximum number of shape dimension


Update Driver dialog is not clickable until Driver settings dialog is opened

Description
Update Driver dialog is not clickable until Driver settings dialog is opened

DBeaver Version
22.2.2
Operating System
win10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

verified


Youtube Clone

Project title
Youtube Clone
Project Description
I have made a youtube ui clone using HTML, CSS, Vanilla JS.
Stack:

[x] Html
[x] CSS
[x] JavaScript
[] ReactJS

/assign


Question: Is there any reason not to merge .bowerrc into bower.json ?

What is the reason for the separation of options into .bowerrc and bower.json and are there reasons against .bowerrc being merged into bower.json.
Thanks

oops, just found https://github.com/bower/bower/issues/1986


Upgrade Firebase to 9..

Follow this upgrade guide to upgrade Firebase to version 9: https://firebase.google.com/docs/web/modular-upgrade

I would like to work on this request. kindly assign this to me. thanks

Hi, I would love to contribute and work on this issue. Kindly assign this to me. Thanks

Hi, update is now complete. should i do a pull request. I did see there is already a pull request for eslint. should i wait for that pull request to finish.

Hi @mfix22 could I get assigned to this? Thanks!

Hi @mfix22 could I get assigned to this? Thanks!

Sure, but please don't feel the need to get assigned in order to submit PRs to fix issues. Anyone is allowed to submit a PR, even without assignment.


scene deformation

Is there a way to avoid scene deformation while typing on mobile devices?
The input text is unreadable.

Personally I use the keyboard open/close bindings to either block or allow reflowing of the game


feat: support streaming of responses

tough nut and still not happy with this implementation - feedback welcome
https://github.com/user-attachments/assets/c88c5bc2-0c93-401f-b95f-a659ebb35035

on hold for refactoring of Message, Response and Document refactoring.

def not happy with the direction of Response obj as well, but would rather continue to add feature and shift refactoring to later with more implementations and knowledge


Feature Request - Single Crafting upgrade

What it says - upgrade that when multiples of an item are requested the system waits for one to complete before attempting the next. An example use would be with Botania's rune crafting. If 500 of a rune is requested it would supply items for one then wait for that to be returned to the system before supplying items for the second.
Another use case would be with tiered items such as vibrant alloy from EnderIO. Request 64 vibrant alloy. One energetic alloy is smelted then one vibrant alloy is started. Second energetic alloy is not started until the first vibrant is in the system. This would supply a smaller number of items back to user even though the full craft might take longer.

already in 1.11 might get backported to 1.10


Post release automated changes for machinelearningexperimentation releases

Post release automated changes for azure-arm-machinelearningexperimentation

@praveenkuttappan why this PR fails ? It is auto generated by bot right ?


Improvement Request: allow browsing of the  "Music Folder" in Material Skin

As per the title, the ability to browse the music folder is not available in LMS Material, while it is in the normal LMS interface.
The improvement request is to make such access available in Material Skin.
Thanks!
Francesco - Rome

All modes are supported. This is a duplicate of #452 - please look for existing issues, even closed ones, before creating new ones.


package name collision with cpapi / OpenMaya

Hello,
There is another package with the same name already published to pypi (https://pypi.org/project/cpapi/), so if someone accidentally type "pip install cpapi" after seeing a message "No module named 'cpapi'" he gets this OpenMaya package (why is it called cpapi - I don't know, I hope it's not malicious but it would be possible to use it as such).
It is kind of annoying that your package is not available via pypi, as it is hard to use it in another packages as dependency, also installing from git is not always an option; would it be possible to give the package unique name and publish it to pypi ?

Hi,
A while back we couldn't publish it due to organization policy. I'll check again and update you if things have changed.
In the meantime, you can use: pip install git+https://github.com/CheckPointSW/cp_mgmt_api_python_sdk
If you don't have git, you can:
Download the SDK by using the ‘Download ZIP’ button
unzip it.
Navigate to .../cp_mgmt_api_python_sdk/ directory and run: pip install .

Hi,
The package is now available in PyPI as cp-mgmt-api-sdk:
https://pypi.org/project/cp-mgmt-api-sdk/
Regards,
Eden

Wow, great!!! thank you very much!


ValueError: All shapes must be fully defined.

Hi,
I am trying to create a TFRecord file where each picture is saved by its dimensions, label and image content.
Since every picture has different dimensions, so it is necessary to read the info from the file and reshape them. When I did something as the following:
features = tf.parse_single_example(
serialized_example,
dense_keys=['image_raw', 'label', 'height', 'width', 'depth'],
# Defaults are not specified since both keys are required.
dense_types=[tf.string, tf.int64, tf.int64, tf.int64, tf.int64])
image = tf.decode_raw(features['image_raw'], tf.uint8)
height = tf.cast(features['height'], tf.int32)
width = tf.cast(features['width'], tf.int32)
depth = tf.cast(features['depth'], tf.int32)
im_shape = tf.pack([height, width, depth])
new_image = tf.reshape(image, im_shape)
I got the error "ValueError: All shapes must be fully defined." Is this because I used the tensors representing dimensions instead of specific numbers? I have searched through the internet, all the tutorials and discussions are about reading fixed sized images. I do think reading various sized images is important. Any solutions to this issue? I would really appreciate it.

That is my post. Because it did not solve the problem, so I came here for help.


Bug/target subscription

#56

@Plork thanks a bunch, these look good. I will merge now, test with some other updates, and hope to have a new release by next week.


JAMES-3963 Sort From To Cc on display name first

TODO

[ ] backport on tmail...

13:26:04,446 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:check (check-style) on project apache-james-mailbox-opensearch: You have 1 Checkstyle violation. -> [Help 1]


Bump VERSION to "v0.4.1-mercari.1"

WHAT
This pull request bump VERSION to v0.4.1-mercari.1.
WHY
To release https://github.com/mercari/kritis/pull/21

Thank you for the review! I'm going to merge it 💪


sysinfo crate is marked "not a library", but it's wrong

As you can see when going on https://docs.rs/crate/sysinfo/0.10.0, you have a big message saying "sysinfo-0.10.0 is not a library", which is wrong.

Duplicate of https://github.com/rust-lang/docs.rs/issues/503. Should be fixed by https://github.com/rust-lang/docs.rs/pull/508.


Made release &mut self to reflect its internal use

I noticed that release was internally changing the read and write_in_progress fields, made the method take &mut self to reflect this.
Maybe there is a reason for the &self that I missed?

I believe this is now superseded by #37. Please let me know if you disagree.


CIF Input gathering for Amendments/Revisions workflows

Describe the task
Gaps between the front-end business logic and the back-end technical logic have been identified and discussed with the developers as outcome of #1365. However, the workflow design have diverged into 2 main different directions:

When viewing/editing a revision record, other forms from the tasklist always show the current status of the project, i.e. always show the latest committed information

View Revision Record (Updated)
New Revision Record (Updated)
Edit Revision Record (Updated)

When viewing/editing a revision record, other forms from the tasklist are accessible and show a past status of the project, i.e. show information at the time of the revision record

Alternative Workflow

We need to choose one of the direction to move forward. To make informed decision, CIF's input is required as suggested by the developers. This ticket is to discover and discuss confusions the CIF team may have with the updated interactive prototypes, and make design decisions based on them.
Acceptance Criteria

[x] Write agenda and meeting invite for the input gathering session with CIF
[x] Schedule the input gathering session with CIF
[x] Draft test scripts and draft
[x] Conduct the usability test / input gathering session with CIF
[ ] Compile and document design decisions based on the input with the team
[ ] Update the prototypes to reflect the design decisions we agree upon and remove older versions to avoid confusions

Helpful comments in #1275.

Questions copied over from Teams:
If the decision is to go with the new flow, then answers to the following should help unblock some of the work. Numbers 1 and 2 were just points that were causing confusion and final decisions weren't made at the dev/design sync. Number three is a bigger issue that in my opinion needs feedback from the users.

Are we keeping the task list on the page with the holistic change log? There was confusion around this at the last dev/design sync, and no official decision was made.

Are we keeping the link to the change log in the task list, removing it, or separating it from the other items with a gap to indicate that it isn’t tied to a specific revision?

With General revisions and Minor revisions (a.k.a. routinely updated fields) being able to update the same set of fields, we’ve introduced the possibility of a non-linear history, which to date we’ve placed a lot of emphasis on maintaining. This is best understood with an example:

I start a General revision on a project, and one of the changes I make is setting the project status to “Under Technical Review”. I’m waiting to hear back from the proponent about something so I leave the revision pending.
Now you go in and change change the status to “Technical Review Complete” via a routinely updated field. The next day, I hear back from the client and finally submit my General revision. Your change is overwritten and the project status is now “Under Technical Review”.  Alternatively, when you hit submit on your routinely updated field, the status in my general revision is changed to “Technical Review Complete”, and now something has changed in my revision that wasn’t my doing. In this specific scenario, the latter is fine. There are others where the opposite is true. It’s a case by case basis which would be correct.
We all agree the likelihood of this happening is quite low, but not impossible, and we should avoid introducing the potential for it.
Do we need to give them two different ways to update the same set of fields? If so, I think a meeting with the ops team will be necessary because while there are ways to handle this, they are a little bit unintuitive and we need to make sure that any conflicts are handled the way the team expect them to be.
If however the CIF team feel that just one way to update that set of fields is no loss to them, then eliminating either General or Minor revisions, then we bypass the problem entirely. I lean towards General getting the axe if this is the route we take, as without them, our existing flow would need very little tweaking to accommodate for having Minor and amendments as the two types of revision.

@LindsayMacfarlane's feedback:
1. Are we keeping the task list on the page with the holistic change log? There was confusion around this at the last dev/design sync, and no official decision was made.
For clarification, this is reference to when a user is viewing a revision? If so, then I would recommend removing the task list when a user is just looking at a previous revision. Allowing them to jump around is confusing and adds unnecessary complexity.
2. Are we keeping the link to the change log in the task list, removing it, or separating it from the other items with a gap to indicate that it isn’t tied to a specific revision?
I feel I need to see an image. I would say keep the link in the task list. To me it already seems intuitive that you would select the amendments change log from the task list to see all amendments/revisions related to a particular project.
3. With General revisions and Minor revisions (a.k.a. routinely updated fields) being able to update the same set of fields, we’ve introduced the possibility of a non-linear history, which to date we’ve placed a lot of emphasis on maintaining.
Is part of the confusion here that we have general and minor revisions? Is this  adding in some of the complexity? Can we nudge the team into just two categories - Amendments and Revisions? This probably doesn't answer your specific question. Wouldn't the change that was 'committed' first be the first in this linear scenario? I always appreciate the team looking at all the what if scenarios, but in this context can we address at a later date if there is an issue or the scenario arises?

Updates for @LindsayMacfarlane:

Usability testing and input gathering session was held with Amanda, Lindsay (CIF), @mikevespi, @BCerki, @suhafa, and @Dianadec on Thu, Feb 16.
Prototypes of both the refined workflow and the alternative workflow was walked through by Amanda completing key user tasks: view/create/update Amendments/Revisions.
Very helpful input was gathered. Questions from the developers were answered. We are in a good place to agree on design decisions to unblock associated development tickets. Key take-aways below:

After clicking on a form from the task list, user always expects to see the current status (latest committed information) of a project. (With only one exception, see the next point below.)
When creating a new Amendment, user expects to use the task list to navigate among forms to make edits.
The users see little value of keeping General Revision, given the technical complexity of avoiding potential duplications/conflicts.
As suggested, we'll only keep Amendment (created from the holistic change log table page) and Minor Revision (routinely updated fields).
As suggested, the "New Revision" button on the holistic change log table page should be relabeled as "New Amendment".

A 45-minute briefing session is scheduled on Fri, Feb 17 afternoon for the attendees to sync-up on notes, confirm and document the agreed solutions to make sure the development tickets are all unblocked.

Hi @LindsayMacfarlane - FYI, key design decisions compiled and agreed upon with @mikevespi, @BCerki, @suhafa, and @Dianadec are listed below:

After clicking on a form from the task list, the user always expects to see the CURRENT status (latest committed information) of a project. (With only one exception, see the next point below.)
When creating a new Amendment or editing an open Amendment, the user expects to use the task list to navigate among forms to make edits.
The users see little value in the current workflow of creating a General/Minor Revision, given the technical complexity of avoiding potential duplications/conflicts.
As suggested, we will only keep the workflow of creating an Amendment from the holistic change log table page, and use the current workflow of updating routinely updated fields to create General Revisions.
There will be no more Minor Revisions.
Rename the "New Revision" button on the holistic change log table page to "New Amendment".
For an open Amendment, we will add more clarity to the “Forms updated” section so that the user is aware that by clicking the form title, they can navigate to it to make further edits.
Nice to have (low priority) - A “View History” button from the “Projects” page that brings the user directly to the holistic change log table page of a project.
With the page title, e.g. “Amendment 4”, “General Revision 2”, there will be no more “Revision type” section.

Next steps:

Update the spreadsheet to reflect the new grouping of fields as discussed.
Refine the tickets for Amendments/Revisions accordingly to unblock implementation
Update the prototypes to reflect the design decisions. (Not a blocker of the implementation but can provide additional guidance according to Brianna.)
Update the business workflow charts to reflect the design decisions. (May or may not be needed, based on the upcoming updates from Mike)

Hi @LindsayMacfarlane - As discussed with @mikevespi, this ticket is ready for you to review and can be closed with updates summarized below:

CIF perspectives and preferences have be documented above and brought back to the team
After additional technical discussions (Feb 22nd Backlog Refinements), the design decisions and next steps agreed upon and documented above are NOT relevant any more
Based on the CIF input, @mikevespi, @dleard, and the team agree to follow up on white boarding sessions to come up with technical design solutions, which may have impacts on the workflows
The implementation of Amendments/Revisions is currently on hold until technical design decisions coming out of the white boarding session.

Thank you @nanyangpro! I appreciate how much work this has been to bring the team and program staff to a common understanding of how this feature can be implemented. I look forward to seeing the next steps.


Why  Toturial Notebook run always wrong !!!

Environment (please complete the following information):

OS: [e.g. mac / window]
Python Version [e.g. 3.6]

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

What is wrong? And you can try to use source code .


[MM-37052] Payment information test scripts for system console

Summary
Payment information scenario's after subscription
Ticket Link
https://mattermost.atlassian.net/browse/MM-37052

Release Note
NONE

Hello @vinod-demansol,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


[INLONG-3201] [TubeMQ] Improve the cluster query function

Title Name: [INLONG-XYZ][component] Title of the pull request
where XYZ should be replaced by the actual issue number.
Fixes https://github.com/apache/incubator-inlong/issues/3201
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Fixed by https://github.com/apache/incubator-inlong/pull/3273.


rootDir should default to the tsconfig.json directory

Otherwise it crashes when calling from another working directory.

Did you specify root dir in your tsconfig.json?

Fixed in 793211e


section:pre-data, exit status 1

import Postgres databases with monolith but error while executing pg_restore, section:pre-data, exit status 1
cloudnative-pg:15
postgresql:11

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: pgsql-cluster
spec:
  instances: 1
  superuserSecret:
    name: pgsql-cluster-superuser
  imageName: ghcr.io/cloudnative-pg/postgresql:11
  bootstrap:
    initdb:
      import:
        type: monolith
        databases:
          - "*"
        roles:
          - "*"
        source:
          externalCluster: machine-pg
  externalClusters:
    - name: machine-pg
      connectionParameters:
        host: x.x.x.x
        user: postgres
        dbname: postgres
        sslmode: disable
      password:
        name: machine-pg-superuser
        key: password

There's too little information to help here. Just noting that "CloudNativePG" 15 does not exist.
I can only speculate, but it might depend on the extensions you have installed in the source database.

This issue doesn't look right at all @Evolt0 , please, open an issue with all the information and the proper information, just adding an error and the cluster spec doesn't make it an issue.


Update supported MeiliSearch verison in README

Codecov Report

Merging #93 (b86e308) into meilisearch-v0.24.0 (500e2fd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head b86e308 differs from pull request most recent head d6ebb71. Consider uploading reports for the commit d6ebb71 to get more accurate results

@@                  Coverage Diff                  @@
##           meilisearch-v0.24.0       #93   +/-   ##
=====================================================
  Coverage               100.00%   100.00%
=====================================================
  Files                       15        15
  Lines                      820       820
=====================================================
  Hits                       820       820

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 500e2fd...d6ebb71. Read the comment docs.


Bump buggy renovate detection on helm-setup

Description
Renovate is not bumping this, let's see after updating manually

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.37%. Comparing base (c424179) to head (22f1e99).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3106   +/-   ##
=======================================
  Coverage   59.37%   59.37%
=======================================
  Files         319      319
  Lines       17443    17443
=======================================
  Hits        10356    10356
  Misses       5922     5922
  Partials     1165     1165

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


FMU / IO drivers: Move param definition of MAIN / AUX params to drivers

This ensures param pruning works correctly on a per-driver level. This also adds the missing AUX params for FMUv5 which has 8 instead of previously 6 AUX ports.
@PX4/testflights Please test on Pixracer and Pixhawk 4.

These all need to go somewhere central (maybe something like a pwm output module interface) and then we need to do a pass to check usage across all modules.
The root cause of #9859 is that px4fmu is directly accessing PWM_AUX_REV and PWM_AUX_TRIM parameters https://github.com/PX4/Firmware/blob/master/src/drivers/px4fmu/fmu.cpp#L925-L942) even when it's configured as the primary pwm output (MAIN).

Followup https://github.com/PX4/Firmware/pull/9925

flashed on a pixracer (V4)
ESC's do not initialize

@santiago3dr I presume you flashed this branch and not the follow-up PR from Daniel?

correct, i flashed this branch, git hash: 023c905

Flashed on a pixhawk 4 (V5)
https://review.px4.io/plot_app?log=ef0ce562-cb3a-4c8f-921d-3d4e4a852481
The ESC initialize and working well.

tried again, same results, esc's do not initialize
here is a log from boot:
https://logs.px4.io/plot_app?log=b5e87ef0-ad99-42cb-a460-025e2fd44f7b


Add documentation for GRPC_ environment variables

This is really useful -- thanks for putting it together!

test this please

test this please

No idea. This is documentation by grep.
On Fri, Sep 16, 2016, 2:17 AM Jan Tattermusch<EMAIL_ADDRESS>wrote:

@jtattermusch commented on this pull request.
In doc/environment_variables.md
https://github.com/grpc/grpc/pull/8050#pullrequestreview-318504:

@@ -0,0 +1,64 @@
+gRPC environment variables
+--------------------------

+gRPC C core based implementations (those contained in this repository) expose
+some configuration as environment variables that can be set.
+
+* GRPC_ABORT_ON_LEAKS

A debugging aid to cause a call to abort() when gRPC objects are leaked past
grpc_shutdown(). Set to 1 to cause the abort, if unset or 0 it does not
abort the process.

+* GRPC_GOOGLE_CREDENTIALS_ENV_VAR
Did we change the name?
It used to be GOOGLE_APPLICATION_CREDENTIALS or sth in that sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/8050#pullrequestreview-318504, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpudejEOlCpP_PwRvUMDEtIY6LNtSTLks5qql6-gaJpZM4J5L2M
.

test this please

test this please


Proposed Cache path in documentation

In the documentation of Skeets one example shows how to specify the cache path.
//set the cache directory. Only have to do this once since `sharedManager` is a singleton
let paths = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true)
ImageManager.sharedManager.cache.diskDirectory = "\(paths[0])/ImageCache"

My understanding until now was, that the Document Directory (and its subdirectories) is NOT the right choice to store cache data, it even leads to failing the app review process, due to the fact, that the Document Directory gets backed up to the iCloud and cache data is nothing, which we really want to back up in the cloud.
Unless of course we exclude the Directory, which we specified, from the iCloud backup explicitly.
I thought the NSSearchPathDirectory.CachesDirectory would be the appropriate location to store cache data?

Agreed, the documentation should probably be updated. That isn't an ideal example, was just something I used for testing and forgot to change. I just updated it to use the CachesDirectory. Thanks!


Error at windows sturt up

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
GitHub, PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
Start up windows
✔ Expected Behavior
No errors
❌ Actual Behavior
Error:

Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 22.04.2024 11:42:01
Exception:
System.Collections.Generic.KeyNotFoundException: The given key 'D:\Library\Games\Escape From Tarkov SPT AKI 3.7.6\EscapeFromTarkov_Data\StreamingAssets\Windows\assets\content\items\mods\pistol grips\pistolgrip_m3_benelli_telescopic_stock_handle.bundle' was not present in the dictionary.
   at System.Collections.Concurrent.ConcurrentDictionary`2.ThrowKeyNotFoundException(TKey key)
   at Wox.Infrastructure.Image.ImageCache.get_Item(String path)
   at Wox.Infrastructure.Image.ImageLoader.LoadAsync(String path, Boolean generateThumbnailsFromFiles, Boolean loadFullImage)
   at Wox.Infrastructure.Image.ImageLoader.<>c.<<Initialize>b__16_1>d.MoveNext()
--- End of stack trace from previous location ---
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
   at System.Threading.QueueUserWorkItemCallback.Execute()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

Other Software
No response

@dec04
Please update to the latest version of PowerToys. It should be fixed there.
/needinfo


Colorful taxonomy

This is an enhancement or feature.

Summary
I think that making categories and tags on posts colorful is more beautiful, and it can attract readers to click them. The color of each taxonomy is calculated by the polynomial rolling hash value of its text.

Colored taxonomy links doesn't fit in with my vision for the theme as I find it quite distracting visually.
This is a perfect example of customizing the theme to suit your needs instead of something I'd natively add support to. Closing for this reason.


accessiBe trial

accessiBe is a software that assesses 508 compliance and ensures our website is accessible to all.

This change is

After discussing this with Mike, we decided not to pursue accessiBe at this time.


unwanted sharing and a new oneShot RULE for await?

I was studying the difficulties about sharing, CSE and 'full-laziness' which @edsko was advancing in a blogpost here - but also in reddit discussions here and here, and in the ghc tracker here .  It occurred to me to try a rewrite rule
 ; "await >>= f" forall f . await >>= f = Request () (oneShot f)

You can see it in situ in this branch.
This use of oneShot should in principle make every user-defined Pipe or Consumer unshared after the first use of await. This gist gives a separate implementation of the patch.  You can toggle between using the patched oneShot await' and regular await and see the accumulation either in a Pipe or Consumer version.
Pathological sharing of Pipes and Consumers frequently fails to arise even where in principle it might with full-laziness, because of the way pipes writes Pipes and because of its battery of rewrite rules. But it is pretty easy to construct cases.  I was thinking this patch was maybe too clever, and I had tested it only on stylized examples like those in the gist, and figured one should await word from the issue on the ghc tracker so I delayed raising an issue. ... But then there came up this trouble with pipes-text, also on reddit . Here the user was cleverly redeploying the same Pipe , called processor, on many different threads working with separate files. I suggested maybe trying this patched version and they reported success calming the problem down, so this emboldens me to recommend the patch. The solution seems surprisingly strong, though I haven't tried a million examples.
The same solution should by the way work for conduit sinks and intermediate conduits.
The difficulties would remain for the Producer case, which doesn't admit a solution like this as far as I can see. The compiler's behavior in pathological producer cases is however much more intelligible in my view - it is like making several references to numbers = [1..] in the same program. In any case, a program does not tend to read the same file again again, but raw reusable no-argument pipes p >-> myPipe >-> c are pretty common in practice.
Anyway I can produce a proper patch if the branch I mentioned looks good.

I may be getting a counter-indication and will close this for the moment.

@michaelt I'm curious, what was the counter-indication? Just difficulties in getting the rule to fire reliably,  or a more fundamental problem with the idea itself?

No, there isn't any problem I have found. I just haven't tested it enough.  What got me excited enough to raise the issue was the independently devised pipes-text program linked above from Reddit.  At first s/he said it was improved, but the program had other problems and later they said it didn't make a difference, if I understood.  That is, I just lost confidence that it contained a sharing problem like the ones you discussed. (It seemed like an interesting case for pathology since he was using the same named, user defined top level pipe on several concurrent threads. I take it that that could be really ugly if there were the kind of sharing you describe, maybe I should try to devise s case.)
As I said, the device does seems to survive a lot of compositions. I think it is also clear that it can do no harm, e.g. oneShot isn't itself expensive if I understand. (?) So I think it is certainly a good patch but would like to comprehend the problem better and have a few gruesome natural programs it cures.

Yup, I agree. I'm planning on further research as well :)


INCLUDE switch directory option for demo generator

It looks like demogenerator takes a default directory from https://aex.dev.azure.com/, which does not make it easy when needing to change it:

Open private browser
go to https://aex.dev.azure.com/ and select the new directory
Open demo generator and sign in

It should include something similar to Azure DevOps portal to swith the related Azure AD easier:

Implemented the feature to switch between directories. Please click on the profile icon to see the option.

it looks like we still need to clean cache before opening demogenerator again with another active directory, if we dont, it open demogenerator with the first directory

maybe we can choose the directory when signing in?

we have tested the feature, looks like it is working fine, as we are reading all the tokens from the new/changed active directory.

In my case I need to click on switch directory, change it in https://aex.dev.azure.com/ and open a clean browser in incognito. It does not work if the other directory is on cache or so :( It would amazing to be able to change the directory on the same demogenerator website (as Azure Devops does)


Version bump to v7.16.2

https://www.elastic.co/guide/en/elasticsearch/reference/current/release-notes-7.16.2.html
Need version bump in order to use plugin.
Edit:
Open PR: https://github.com/vvanholl/elasticsearch-prometheus-exporter/pull/329

https://github.com/vvanholl/elasticsearch-prometheus-exporter/pull/329


[Runtime] Make Swift errors bridged to NSError and cloned round-trippable

When a Swift error is bridged to NSError, it maintains enough information
to round-trip back to Swift. However, if the NSError is then cloned—e.g.,
a new NSError is created with the same domain/code/user-info dictionary,
the identity of the Swift type is lost.
When we initially form the user-info dictionary for a Swift-defined
error that is not explicitly bridgeable back from an NSError instance,
add a new key to the user-info dictionary containing a wrapped copy of the
original error. When trying to bridge from NSError, look for that key in
the user-info dictionary and cast to its value.
Fixes rdar://problem/29882046.

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 6221d0e7f22fc83418538e829d01d9c7cd457f6b

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Add to admin visibility whether there is a scheduler running

Is your feature request related to a problem? Please describe.
Currently there is no way to know whether there is a worker with a scheduler.
Describe the solution you'd like
Add a check whether there is a worker with a scheduler and make it visible in the admin view.

@cunla I was checking and apparently, that is possible, by querying directly to redis. Would you entertain me going this path?
Also, the best place for this check would be django-rq, where a column cold be for each queue to say if a scheduler (/worker-scheduler, it's the same) is attached to each queue.

Since this package is a wrapper on top of django-rq (which is on top of rq) - I recommend not going this path on django-rq-scheduler. If they choose to change implementation it will break.
But generally speaking, in rq you can see redis commands.


Add admiral_file_tag job

https://github.com/Shippable/pm/issues/10930

this is done, closing

reopening to fix bug

this is done, closing


rails-transporter:open-model ignores non-namespaced models

rails-transporter:open-model looks for models under the same namespace as the view or controller. It does not find models that are not in the same namespace as the controller or view.
For example, I have a controller app/controllers/admin/members_controller.rb. My model is in app/models/member.rb. Launching rails-transporter:open-model does not find the model, but instead brings up a dialog like the following:

@mysmallidea Sorry for the delay in fixing, latest version of this pacekage's open-model now supports to open non-namespaced models from controller.
Thanks.

Thanks!  This just got 10x more useful in my heavily namespaced project!

:satisfied:


[wifi_info_flutter] Initial commit for wifi_info_flutter plugin and platform interface

Description
This PR is from the generated code when running the lines below. Only small changes were made to get tests passing.
flutter create --platforms=android,ios -t plugin --org="io.flutter.plugins" -a java -i objc --project-name=wifi_info_flutter .
flutter create -t package --project-name=wifi_info_flutter_platform_interface .
Beginning a larger effort to separate wifi related methods from the connectivity plugin. See https://github.com/flutter/flutter/issues/40418
Related Issues
https://github.com/flutter/flutter/issues/40418
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@amirh This PR was only supposed to be code generated from flutter create and small changes to get tests passing. Ideally, this makes it easier to review and the following PRs will have non-generated code.

Ok! let's just add the license files before submitting.


Fix mix includes for flatten

Submission Checklist

[X] Run unit tests: ./runTests.py src/test/unit
[X] Run cpplint: make cpplint
[X] Declare copyright holder and open-source license: see below

Summary
The flattening of mix happening in https://github.com/stan-dev/math/pull/1584 replaces stan/math/mix/mat.hpp with stan/math/mix.hpp, so this is required alongside those changes.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Marco Colombo
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

@rok-cesnovar do you know how to make travis point to a specific branch? I couldn't find instructions.

Perhaps it's not necessary, as I can see we can actually merge. I'll leave it up to you for when the time is right.

I am not sure how to do that on Travis, but I think its fine regardless as these are really simple include fixes.


Add support for minimum datapoints per update

Sorry for the PR spam, need to recreate this one again after a merge conflict (my git fu is just terribad). Deprecates the work in #437 which in turn replaced #231. I'd like to find a better var than mdpu, looking for suggestions.

There's something broken with this change. Caches are neither able to create new files or write to existing ones. I'll try to look into this closer as time permits but I've removed it from the 1.0.0 milestone for now.

@pratX I know it's been a long time coming but if you have time to look at this it would be greatly appreciated.

I will look into this.

Looked briefly at this because I want something similar. The idea is interesting but it looks like the implementation could use some love

Did this feature make it to production?

@Exocomp - unfortunately not. I rebased it in #692 but not sure is it worth inclusion.
If you interested in this change - please test how it works.
Please also check timesorted writing strategy - it's a bit different, but maybe it's better fix then MDPU.

Closed in favor of #692

@deniszh would the idea be to use MIN_TIMESTAMP_LAG with timesorted strategy ?

@Exocomp - I'm not sure what's problem are you trying to solve, probably MIN_TIMESTAMP_LAG is a solution, probably not. What are you trying to achieve?

@deniszh basically to put a delay in writing so you get the effect of "batch" writes.  I like the idea of minimum data point per update but I do see how timesorted with MIN_TIMESTAMP_LAG can help - would be good if we had both (if I'm thinking about it right).

@deniszh I should add that I'm working with a system where the disk is not able to keep up with the small writes, it is basically killing all its throughput.

@Exocomp : TBH I do not really understand how you can have both - for now I just exclude MDPU from timesorted strategy.
How do we need to combine it - would we

select metrics which have more than MIN_DATAPOINTS_PER_UPDATE datapoints in cache AND already MIN_TIMESTAMP_LAG seconds
or
select metrics which have more than MIN_DATAPOINTS_PER_UPDATE datapoints in cache OR already MIN_TIMESTAMP_LAG seconds ?

Or maybe it's better to implement MPDU only in separate strategy, and not for all strategies? I'm worried a bit that MPDU trying to change the default behavior of all strategies now...

@deniszh

select metrics which have more than MIN_DATAPOINTS_PER_UPDATE datapoints in cache OR already MIN_TIMESTAMP_LAG seconds

I like this greedy method.

@Exocomp : OK, added that grredy logic to timesorted strategi in #692. Completely not tested, though - any feedback appreciated.

Sweet!

Well, current implementation should be fixed - with default MIN_DATAPOINTS_PER_UPDATE == 1 it's effectively turns timesorted strategy to sorted. I'm still thinking about implementing MDPU only for selected strategies, e.g. Max and Timesorted.


Playing with layers

Check out this flow !
Is it possible to implement such things? to toggle / hide / show layers

maybe next time, today i am implenting the multi flow

That is very nice. I would actually use that for displaying a datacenter room (cooling, ventilation, power, rackspace, temperature, cable trays) Sooo many things one can do with draw.io.

Awesome :heart_eyes:

A little demo of current dev

If I understand correctly, this is for selecting the drawing to display. Not for changing it on the fly during normal operations?

It's only the first step, next time,link can open sub flows and shape take
the hightiest color
Le sam. 13 juin 2020 à 22:40, xkilian<EMAIL_ADDRESS>a écrit :

If I understand correctly, this is for selecting the drawing to display.
Not for changing it on the fly during normal operations?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/algenty/grafana-flowcharting/issues/182#issuecomment-643675558,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALGVW5JYENXTOBVST7T7HTLRWPP4XANCNFSM4N3RI4NQ
.

--
Arnaud GENTY
Responsable et Ingénieur de production IT (SAP/J2EE).
Tel : (+33)<IP_ADDRESS>.14
Email<EMAIL_ADDRESS>

How is this coming, along? Are you still planning on supporting draw.io layers or mutiple draw.io diagrams? How much effort is still required to support layers?


More flexibility with Cells

... would be possible using code like this:
from ipylab import JupyterFrontEnd

        app = JupyterFrontEnd()
        app.commands.execute("notebook:insert-cell-below")
        app.commands.execute("notebook:replace-selection", {"text": result})

Source: https://github.com/kolibril13/jupyter-tldraw/blob/b4af7d98c86ec24c026e80ec927b6ef270d42d49/src/tldraw/init.py#L142

This doesn't work in colab and pycharm.

#134
#139


proposal: cacheable time layouts

What version of Go are you using (go version)?
N/A
Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (go env)?
N/A
What did you do?
Profile code using time.Format or time.Parse.
What did you expect to see?
Efficiency.
What did you see instead?
So. Many. Allocations.
... So here's my thought: Ideally, I'd love a way to pre-parse a time format. And I thought "yes, but you can't do that without changing the API". But... You sort of can. Imagine, if you will, a convenient trivial binary representation of a fully-parsed time format, represented as a series of bytes-or-runes.
layout = time.ParseFormat("2006-01-02")
fmt.Println(time.Now().Format(layout)

If layout were set to a suitable intermediate representation, this could be done without all the current parsing logic and overhead that goes into parsing strings. The only trick is that layout has to be instantly identifiable as not a valid time format. I suspect that little to no real-world code has time format strings that include literal control characters, though, so that's probably doable.
An intermediate representation might be something like 0xNN bytes to indicate specific time fields, plus a special value which indicates a length-prefixed literal byte string. No fancy parsing, no allocation, etc.; as long as you're comfortable with the assumption that no real formats start with \x01, it's probably fine?
I don't know. This is probably not the right design, but I think the real-world cost of the Format and Parse operations having to reparse those strings all the time is observably high, and people work around it a lot.

CC @rsc for time

Adding new API seems premature. If the current code needs to be faster, the first thing to do would be to make it faster without new API. Brad says he tried putting in a cached compiled form at one point (https://golang.org/cl/6255052), but it was rejected as adding too much complexity. I think we could probably make the scanner much faster even without a cache. But the report does not say what speedup is needed or why (beyond "observably high").
Note also that this could be done outside the standard library as a separate package that was simply compatible with package time.

Huh, I hadn't thought of duplicating stdlib for it.
I don't have detailed breakdowns, but I think we have a log-adjacent thing which ends up spending about 25% of runtime on time calls, and it looks like a lot of that is in the parser. Since I can't separate the parsing-of-time-formats from the formatting/parsing of the actual times, I can't easily measure it without adding additional hooks.


[#313] Setup Rubocop for Ruby

Closes https://github.com/Terrastories/terrastories/issues/313

@rgenchev I wasn't sure about the readme either. You can update readme like this in this PR -> https://github.com/Terrastories/terrastories/pull/338/files#diff-550856cf67eb7260aaeb883550043af8R143-R149

@rgenchev Thanks for the contribution!! Rubocop seems like it could be helpful. Can you describe more about what rules you're adding and what benefits you think they would bring? I'm wary to add too many rules that would block other people!

@rgenchev Thanks for the contribution!! Rubocop seems like it could be helpful. Can you describe more about what rules you're adding and what benefits you think they would bring? I'm wary to add too many rules that would block other people!

@mirandawang, sure. :)
I used what was discussed here: https://github.com/Terrastories/terrastories/issues/313#issuecomment-543311629
We use the default Rubocop configuration. We'll later work on 2 other PRs.

@rgenchev  hi is this still being worked on? we just did a refactor that will require rebasing (moving the Rails app to a Rails directory)

Closing for now due to rebasing needs, can be reopened with those changes.


[FR]: Pass func_kwargs to _evaluate_custom

Proposal Summary
Hello,
It would be nice if we could pass func_kwargs to evaluate_func, in the same fashion than for dataloader_func. Or maybe it is already possible but I've missed how?
Many thanks
What component(s) does this request affect?

[ ] OliveModels
[ ] OliveSystems
[X] OliveEvaluator
[ ] Metrics
[ ] Engine
[ ] Passes
[ ] Other

It actually already exists - my bad.


Make sure manuscript deploys on github pages

Right now it does not deploy at all (I did it once manually). Something is this line keeps it from not pushing the updated HTML manuscript to the gh-pages branch.
@hrshdhgd can you take a look of what is happening? If you cant find a solution within 15 minutes, say it here and abandon the task.

It's because these tokens do not exist
https://github.com/monarch-initiative/gpt-mapping-manuscript/blob/0cd7cf64a8b4cacc09f17cd4400dd352f35b4ae0/.github/workflows/manubot.yaml#L101-L102

Thank you! Do you understand how it is able to push to the "output" branch? That seems to get updated every time.

https://github.com/monarch-initiative/gpt-mapping-manuscript/blob/0cd7cf64a8b4cacc09f17cd4400dd352f35b4ae0/ci/deploy.sh#L79-L84
I haven't worked with this a whole lot.


Create reusable editor component

Objective
Create an editor component that is very similar to micro text editor. But it must live in the tui layout engine:

Meaning that it can be fit in different shaped boxes in the main terminal window.
We can't assume that it will take up 100% height & width of the terminal since there are other UI components on the same "screen" / terminal window.

Timeline & features

Editor component that can fit in a TWBox and is implemented as a Component. Example of a Component column_render_component.rs.
Supports editing but not saving.
Supports focus management, so there may be multiple editor components in a single TWApp.
Support unicode grapheme clusters (cursor navigation).
Rudimentary support for syntax highlighting (using an extensible backend to implement support for various languages / file formats).

Timeline is about 6 weeks.
Milestones

Start building an example in r3bl-cmdr repo for editor component.
Create an app that has a 2 column layout, w/ a different editor component in each column.
Get the code solid in the example. Then migrate the code w/ tests into the tui module of r3bl_rs_utils repo.

Illustrations
TODO: add some illustrations of what the editor might look like
Resources
This is a great series of videos on syntax highlighting & unicode support in editors:

https://www.youtube.com/playlist?list=PLP2yfE2-FXdQw0I6O4YdIX_mzBeF5TDdv
There are a lot of videos here, but they're organized by topic
Topics include: unicode handling, text wrapping, and syntax highlighting engines

Here are a few resources related to editors, and syntax highlighting:

https://github.com/ndd7xv/heh
https://docs.rs/syntect/latest/syntect/
https://github.com/zee-editor/zee
https://github.com/helix-editor/helix

Here are some other TUI frameworks:

https://dioxuslabs.com/
https://github.com/veeso/tui-realm/blob/main/docs/en/get-started.md

Add lolcat to EditorBuffer here 3bc1d2dfc67bc4cbfa0807dae8e1383d491b37ab

Handling cursors
There are two ways of showing cursors which are quite different (each w/ very different constraints).

Use the terminal's cursor show / hide. Both termion::cursor and crossterm::cursor support this.

The downside is that there is one global cursor for any given terminal window. And this cursor is constantly moved around in order to paint anything (eg: MoveTo(col, row), SetColor, PaintText(...) sequence).
So it must be guaranteed by TWCommandQueue via TWCommand::ShowCaretAtPosition???To(...). The downside here too is that there's a chance that different components and render functions will clobber this value that's already been set. There's currently a weak warning that's displayed after the 1st time this value is set which isn't robust either.
This is what that code looks like:// Approach 1 - using cursor show / hide.
tw_command_queue! {
  queue push
  TWCommand::ShowCaretAtPositionRelTo(box_origin_pos, editor_buffer.caret)
};

Paint the character at the cursor w/ the colors inverted (reversed) giving the effect of a cursor.

This has the benefit that we can display multiple cursors in the app, since this is not global, rather it is component specific. For the use case requiring google docs style multi user editing where multiple cursors need to be shown, this approach can be used in order to implement that.
The downside is that it isn't possible to blink the cursor or have all the other "standard" cursor features that are provided by the actual global cursor (discussed above).


coordinates double at intermediate resolutions

Seems like coordinates are not being scaled appropriately for intermediate resolutions (or any res less than the highest res?)


No Input Sources for Knees and Elbows

You have InputSources for feet and even shoulders, which is cool - but how about elbows and knees?
I'm actually much more likely to attach trackers to my knees and/or elbows than to my shoulders. What I'll probably do in Holodance for now, is (ab)use Left Shoulder and Right Shoulder for either knees or elbows depending on where they are located during calibration.
But it would be much better if we could properly assign those two four joints. I believe with head, left hand, right hand, left foot, right foot, waist, left elbow, right elbow, left knee, right knee, chest, you have everything covered (in that order of importance). Left/Right Shoulder is nice to have (IMHO), so keep it.

This is old, but probably also outside the scope of this github. Thanks for the suggestion


Unable to build alacritty after #593

After #593 had been merged, I am unable to build alacritty without errors. I get the following error message:
error: struct field shorthands are unstable (see issue #37340)
   --> src/renderer/mod.rs:188:43
    |
188 |                 font::Style::Description {slant, weight}
    |                                           ^^^^^

error: struct field shorthands are unstable (see issue #37340)
   --> src/renderer/mod.rs:188:50
    |
188 |                 font::Style::Description {slant, weight}
    |                                                  ^^^^^^

error: aborting due to 2 previous errors

error: Could not compile `alacritty`.

OS: Gentoo linux
Rust version: 1.16.0

Oh, shoot. You can upgrade your Rust compiler to work around this.
@algesten can we remove the named field shorthand usage?

@jwilm Sadly 1.16.0 is the latest one available in the official gentoo package repo.
I suppose I could bump it up myself to 1.17.0. If you want alacritty to depend on newer rust versions, that is.

I fix imminently.

So #596 should address this.

@algesten Yes, that has fixed it for me atleast! Thanks! :)

I'll close this because the fix is now in master.


WIP: Refresh CA mine first, then the rest

After publishing the ca.crt into the mine, we need to make sure that
the mine.update happens first on the ca, so we know that it syncs
this information with the master first, then we can proceed to run
mine.update on all nodes, so they again sync with the master and
find the information the ca minion published on it.
Fixes: bsc#1049137
Fixes: bsc#1048548

Adding reviewers despite of being marked as WIP. It's flagged as WIP because we need to verify this fixes the issue completely in a fresh cluster under the same conditions the error was 100% reproducible.
We should be able to verify this fix tomorrow, and possibly get this into 1.0 if at all possible.

Bootstrap passed on XEN-PV with this fix

This working is just a coincidence. Reading salt's source code, mine.send will asynchronously send an event with the new information, and wait a fixed 0.5 seconds (https://github.com/saltstack/salt/blob/42bb1a64caa65bbf0649c50800a0e62897ba654c/salt/modules/mine.py#L60-L66).
We are adding more operations between the mine.send action and the real usage in etcd_proxy_setup, so it's more likely for the information to be there, but is not a real fix for the original issue.
This means that sometimes this mine information is there and sometimes not, depending on different factors.
I'm currently checking if there's a way to do an active wait for the mine information to be there (check contents, not wait for a fixed amount of time).


[Snackbar] Is it possible to disable the transition?

Is it possible to disable the transition for the Snackbar?
TransitionComponent is a prop that I assume wraps the component, but passing null and a generic div wrapper don't seem to work.
Maybe there is something in TransitionProps, but I expect that's just to tweak the transition, not turn it off.
Use case: I am rendering a Snackbar via SSR. I want to show a notification that javascript is disabled so in this case I'm rendering Snackbar via SSR with javascript disabled. The DOM is added, but the snackbar never animates in because the javascript is disabled.
Is there any way to achieve this?
Thanks

Does this work?
const Transition = props => props.children

Oh, reading your use case now. Wrong answer.

Tip: check the props of react-transition-group, you will find what you are looking for in it.

Based on https://reactcommunity.org/react-transition-group/transition#Transition-props there is the enter prop which is supposed to disable enter transitions, but it doesn't seem to work.
<Snackbar
      TransitionProps={{
        enter: false,
      }}
/>

The Snackbar still animates in.
I can take my question to StackOverflow, though maybe this common case could also be added to the docs. I can send a PR if desired and I figure it out.

Did you try appear?

Yes, but it looks like it still requires javascript for it to appear. appear makes the Snackbar appear instantly, but with JS disabled (and SSR) it still doesn't pop in.

I remember making sure appear={false} was working correctly a while ago. I would expect it work work correctly on the first SSR pass.

Doing the following seems to work:
<Snackbar
      TransitionProps={{
        appear: false,
      }}
/>
  <SnackbarContent
      style={{
        opacity: 1,
        transform: 'none',
      }}
  />
</Snackbar>

Overwriting the styles on the SnackbarContent seems the only way to get it to work.

Hum, there is something to dig here. I don't expect any extra style to be provided.

Ok, I had a look, it seems alright. The following is displayed during in the initial SSR output:
      <Snackbar
        TransitionProps={{
          in: true,
          appear: false,
        }}

Great, I'll try that tomorrow. Thanks so much, Olivier.

That indeed works. I thought I tried that specifically before, but somehow missed it. Thanks again!

Doing the following seems to work:
<Snackbar
  ContentProps={{
    style: {
      opacity: 1,
      transform: 'none',
    },
  }}
  TransitionProps={{
    appear: false,
  }}
/>

EDIT: modified to a better version
Overwriting the styles on the SnackbarContent seems the only way to get it to work.

Won't work if you use tricks like this: https://codesandbox.io/s/mui-snack-stack-jnrnwq


Added SAML signed requests support

Added saml settings to server, as support for signed SAML request is already in the lib.

Codecov Report

Merging #311 (0b16768) into 2021.9.x (23a2446) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           2021.9.x     #311      +/-   ##
============================================
- Coverage     42.37%   42.37%   -0.01%
============================================
  Files           781      781
  Lines         73456    73456
============================================
- Hits          31126    31124       -2
- Misses        37931    37932       +1
- Partials       4399     4400       +1

Impacted Files
Coverage Δ

system/types/app_settings.go
53.52% <ø> (ø)

pkg/wfexec/session.go
58.52% <0.00%> (-0.51%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 23a2446...0b16768. Read the comment docs.


Features not working

The only thing that appears to change is the volume bar always showing, none of the other features appear.

Yeah there was a big update to the Twitch player and it broke most features. Will fix soon!

Should all be fixed and working now.

@ehsankia For me, on linux Developer Edition Firefox + BTTV I only get always-on volume bar and I don't have no quality selection anywhere.
That's step back, not forward towards one-button-per-quality dream of mine :laughing:

Sorry the extension broke again, I'll fix it soon!

@a13ph should be fixed now.


logger configuration is incompatible with Rails.logger (not really)

The type checking seems redundant.

Quack quack thanks.


🐛

Environment information

OS: Ubuntu 24.04.1 LTS
C++: CMake 3.28.3
Python: v3.12.4
mqt.core: main

Description
I am trying to build the mqt package as a development package for testing, and CMake fails to find a suitable python version.
Attached is the error log
errorlog.txt
Expected behavior
No response
How to Reproduce
Get the package via git.
Attempt to install via pip pip install -ve .

Hey 👋🏻
Thanks for raising this issue!
Typically, these errors indicate that the Python installation on your system is not complete. Do you have python3.12-dev installed? (sudo apt-get install python3.12-dev)
Truly annoying how hard it is to properly set up Python even these days...

python3-dev is installed, but there seems to be some kind of issue:
❯ sudo apt install python3-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpython3.12-dev : Depends: libpython3.12-stdlib (= 3.12.3-1ubuntu0.2) but 3.12.4-1+jammy1 is to be installed
                     Depends: libpython3.12t64 (= 3.12.3-1ubuntu0.2) but it is not going to be installed
 python3.12-dev : Depends: python3.12 (= 3.12.3-1ubuntu0.2) but 3.12.4-1+jammy1 is to be installed
                  Depends: libpython3.12t64 (= 3.12.3-1ubuntu0.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Yeah. Unfortunately, your Python installation seems broken.
It's definitely not the first time that I have seen this...
IIRC, I personally fixed this at some point by doing a complete reinstall of all Python-related system packages.
We do run CI on default Ubuntu images in GitHub actions and everything seems to "just work" there as well as locally on multiple development setups.
You could give uv (https://docs.astral.sh/uv/) a try:
curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv --python 3.12
uv pip install -e.

You can tell uv to explicitly set up Python for you and not use the system Python via
uv venv --python 3.12 --python-preference only-managed

aptitude managed to resolve some version conflicts between different parts of python which mutually blocked each other from updating.


exhaustruct doesn't detect properties not defined in slice expressions

This:

type user struct {
    Name string
    Age  int
}

func test() {
    _ = []user{
        {
        	Name: "",
        },
    }
}

Does not trigger exhaustruct.

Same goes for map elements like:
_ = map[string]user{
    "a": {
        Name: "",
    },
}


Authenticate with Facebook

I created my Tidal account with the "Sign in with facebook" option. Anyway to sign in to the cli-client?

I'll try do allow Facebook login. Thanks for your patience :)

There is currently no option for Facrbook authenticated login, but you can login like normal. On the other device you should set up you Tidal password and you can now login like to the normal account.