Use taylorbot instead of default github-action identity

This PR replace the default identity used by all our github actions with taylorbot.
Problem
Actual github action are never run on release PR. So we usually need to create an empty commit in order to actually trigger github actions.
Example:
Note the absence of check mark next to the commit created by github-action.

source: https://github.com/giantswarm/github/pull/826
This is due to a limitation in github itself
if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

source: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow
Solution
The workaround proposed here make use of a different identity, our beloved taylorbot, to actually execute github actions like commit, push and create release.
Test:
Note the presence of check mark next to the commit create by taylorbot, bonus we get our logo everywhere :)

source: https://github.com/giantswarm/theo-test/pull/9
In order to get this working I also: (I need to document this)

created a github token (with repo and read:org permissions) under taylorbot account https://github.com/settings/tokens/1146048704

added a new TAYLORBOT_GITHUB_ACTION secret available to all repositories in our organization https://github.com/organizations/giantswarm/settings/secrets/actions

TODOs
Checklist

[x] Update changelog in CHANGELOG.md.

This would also allow us to get rid of this overrides which is left unmaintained https://github.com/giantswarm/github/blob/7e9c04d352d3c54912a92be5a38a4bb449a76dca/repositories/override/github/.github/workflows/zz_generated.create_release.yaml#L191-L194

cc/ @QuantumEnigmaa as will enable us to run the inhibition-tests script on release PRs


Vulnerability found on latest version of eslint-plugin-import (2.27.5)

There is vulnerability found on latest version of eslint-plugin-import (2.27.5) due to minimist.

This isn't an actual vulnerability, and tsconfig-paths depends on json5 with ^, and json5 has a v1 and a v2 both that don't have the vulnerability anyways.


[1.12.2] Not compatible with Mixin 0.8.3+

MixinLoader breaks with Mixin 0.8.3+, as MixinProcessor became package-private, leading to
java.lang.IllegalAccessError: tried to access class org.spongepowered.asm.mixin.transformer.MixinProcessor from class net.minecraftforge.fml.common.Loader
    at net.minecraftforge.fml.common.Loader.handler$zza000$beforeConstructingMods(Loader.java:1141)

MixinBooter fixed this here, perhaps you could implement something similar.

look into this with JEID (Just Enough IDs) I possibly can fix it later for VanillaFix

Is there any update on this?


"Multiselect" DropDown does not work in SUI

Hi guys.
The "multiselect" options for DropDown list does not work in SUI. I cannot select multiple values for this type of element form SUI but can do it from classic ui:
Screen frim Classic UI:

Screen from SUI:

Whattup @ITD27M01 !  ok so off the bat, from where are you accessing the multiselect dropdown?
this matters because it might be an issue better suited for https://github.com/ManageIQ/ui-components

Hi @AllenBW I'm trying to set up a dynamic dialog for the service. One of the elements of such a dialog is a drop-down list with multiselect parameter.

Hello @ITD27M01,
Where are you accessing the multiselect dropdown?

@chriskacerguis
From SUI during Service Request. Service have dynamic dialog with dropdown element with "multiselect" option:

Yeah, I think this needs to go to https://github.com/ManageIQ/ui-components


Quick Tips Animated Transitions

Description
When changing tips in help center there should be a "swipe" move in animation for fluidity
Acceptance criteria
(Try to get early buy in on this from Tad)
Applies to clicking a tip in main menu and navigation in tip view (go to main menu, previous, next)
Still to find out

Are entrance/exit animations index dependent for direction? or do they always swipe out to the left and in from the right?

Current scope

Adds utility for exit animation
Adds custom layout to animate bg to new heights of different views
Adds "swipe" animation on view transitions with panel animating to new height
Adds open/close anim when opening or closing help center modal

Taking off the estimate cus this could be more or less work depending on mockups.
With "Swipe in/out", There's some complexity I still need clarification on:

Different tips are different heights. Would the popup need to animate height between tips?
Would items need to animate out before they unmount?
Would animations be directional depending on order of tips?

All these factors are doable, but would add significant complexity to the logic & layout for this feature. They are also more foundational and harder to add after the feature is already built out.
Having a mockup would answer a lot of questions here. There's not really any animations currently being used in the editor UI besides the animation panel, so we don't really have any existing motion language to pull from.
I want to avoid adding complexity to the codebase unless it's an explicit requirement. Let me know where this stacks up as a priority for y'all & what your thoughts are. Until then, gonna add a "UX needed" flag on this.
@tmagalhaes-huge @angelapgUX

Taking off the estimate cus this could be more or less work depending on mockups.
With "Swipe in/out", There's some complexity I still need clarification on:

Different tips are different heights. Would the popup need to animate height between tips?
Would items need to animate out before they unmount?
Would animations be directional depending on order of tips?

All these factors are doable, but would add significant complexity to the logic & layout for this feature. They are also more foundational and harder to add after the feature is already built out.
Having a mockup would answer a lot of questions here. There's not really any animations currently being used in the editor UI besides the animation panel, so we don't really have any existing motion language to pull from.
I want to avoid adding complexity to the codebase unless it's an explicit requirement. Let me know where this stacks up as a priority for y'all & what your thoughts are. Until then, gonna add a "UX needed" flag on this.
@tmagalhaes-huge @angelapgUX

Hi @littlemilkstudio ,
Thanks for the detailed feedback and clarification. We are discussing them with the team to get back to you ASAP.
Q.q Could you please elaborate a bit more on the second question? We are not quite sure we understand it.
Thank you!

Hi @littlemilkstudio ,
Thanks for the detailed feedback and clarification. We are discussing them with the team to get back to you ASAP.
Q.q Could you please elaborate a bit more on the second question? We are not quite sure we understand it.
Thank you!

Awesome @aaecheverria Thanks!

Q.q Could you please elaborate a bit more on the second question? We are not quite sure we understand it.

Yea absolutely.
Say you were on a tip and you pressed the next button to view the next tip. Would the tip you're on animate out? or just disappear while the next tip animated in?
I only ask cus animating out would require some extra engineering effort. Still obtainable, just relevant to estimating work

Awesome @aaecheverria Thanks!

Q.q Could you please elaborate a bit more on the second question? We are not quite sure we understand it.

Yea absolutely.
Say you were on a tip and you pressed the next button to view the next tip. Would the tip you're on animate out? or just disappear while the next tip animated in?
I only ask cus animating out would require some extra engineering effort. Still obtainable, just relevant to estimating work

@littlemilkstudio I see, thanks for clarifying. We were hoping the tips would have a swipe motion left and right (within the panel) as the user clicks next or previous, to indicate continuity. As if the tips were all in a row, in a carousel. If that's not doable, please let us know. If we need to keep the panel sizes consistent in order to make that happen, we can explore that option too.

@littlemilkstudio I see, thanks for clarifying. We were hoping the tips would have a swipe motion left and right (within the panel) as the user clicks next or previous, to indicate continuity. As if the tips were all in a row, in a carousel. If that's not doable, please let us know. If we need to keep the panel sizes consistent in order to make that happen, we can explore that option too.

@tmagalhaes-huge Awesome! Definitely doable, just wanted to verify it's what y'all were asking for. I can make the height of the panel animate too. would you prefer that or would you like the height just to be static?

@tmagalhaes-huge Awesome! Definitely doable, just wanted to verify it's what y'all were asking for. I can make the height of the panel animate too. would you prefer that or would you like the height just to be static?

@littlemilkstudio Ideally the height would animate to avoid lots of empty areas on some of the tips. Since the next/previous buttons stay in the same place, that should be ok. Thank you!

@littlemilkstudio Ideally the height would animate to avoid lots of empty areas on some of the tips. Since the next/previous buttons stay in the same place, that should be ok. Thank you!


[6.0] Sema: Fix @retroactive does not apply diags for same-package conformance

SE-0364 was amended to allow same-package conformances to be considered non-retroactive. The logic for that ammendment was implemented in Swift 6.0, but the diagnostics were not updated.
Resolves rdar://133423931.

@swift-ci please test

@swift-ci please test

Fixes https://github.com/swiftlang/swift/issues/75412 and https://github.com/swiftlang/swift/issues/76724.


Ket element

Ket-viewer has all elements centered, looks better and will be useful for QG.

@KlemKlem I merge ket. Since you didn't base the changes on the master, it will be harder to merge.

Ok, what should I do?


Update custom response header collection

This PR is to update the response header collection interface

Related to #45 #38


Docs around kustomization overlay - regression

https://github.com/fluxcd/terraform-provider-flux/pull/217

Seems to have made some docs changes that remove an explanation about how kustomization.yaml is used, we are not sure if this patch has made a regression in the docs.
If the proposed alternative doesn't allow updating the kustomization override, then it seems it's not a total replacement for kustomization.yaml and we should return this section to the docs:
https://github.com/fluxcd/terraform-provider-flux/pull/217/files#diff-c5fd63d104ff4c57163b958295311e8e4a3831eac0df51ccf7f9a880ea191d21L12-L16

cc: @darkowlzz

I found the same thing as I was trying to follow best practices for multi-tenancy. However I found this simple trick which works fine. The trick is at the content part of the kustomize github file.
locals {
  patches = {
    deployments = file("${path.module}/fluxcd/templates/deployments.yaml")
  }
  base = file("${path.module}/fluxcd/templates/kustomization-base.yaml")

data "flux_sync" "this" {
  target_path = "clusters/${var.cluster_id}"
  patch_names = keys(local.patches)
}

resource "github_repository_file" "kustomize" {
  repository          = data.github_repository.cluster.name
  file                = data.flux_sync.this.kustomize_path
  content             = "${data.flux_sync.this.kustomize_content} ${local.base}"
}

kustomization-base.yaml:
#https://fluxcd.io/docs/installation/#multi-tenancy-lockdown
patches:
  - patch: |
      - op: add
        path: /spec/template/spec/containers/0/args/0
        value: --no-cross-namespace-refs=true
    target:
      kind: Deployment
      name: "(kustomize-controller|helm-controller|image-reflector-controller|image-automation-controller)"
  - patch: |
      - op: add
        path: /spec/template/spec/containers/0/args/0
        value: --default-service-account=flux
    target:
      kind: Deployment
      name: "(kustomize-controller|helm-controller)"
  - patch: |
      - op: add
        path: /spec/serviceAccountName
        value: kustomize-controller
    target:
      kind: Kustomization
      name: "flux-system"

cc @rtjfarrimond


Manually poll an UdpSocket is not working, but used to – regression?

Hi,
I need to manually poll an UdpSocket to drive it from a poll_next method.
I've read #636, where @stjepang suggests to just recreate the future on each poll. I've set up an example here:
https://github.com/Frando/async-std-udp-test/blob/main/src/main.rs
When pinning async_std to =1.6.2 this works as it should. When changing the async_std version to 1.9, the example fails: The reading side is not woken after a first read_from returns Poll::Pending.
Is there something I'm missing, or is this a regression?
I'll try to track down from which version it fails (the 1.6.2 comes from another crate that depended on this version, from where I started debugging why things don't work anymore).

OK, I pinned down where the regression occurs: It works fine with 1.6.3 but not with 1.6.4. So maybe related to #853 which was part of 1.6.4?

This "worked" previously because we used a hack, which was later on removed. Imagine there are 1000 tasks concurrently polling read_from on the same UdpSocket. We'd have to store all those wakers somewhere and then wake them all up at once when the UdpSocket becomes readable. That's an extreme and contrived example, but you see how inefficient it could be in theory. The hack we used before was to store a bounded number of wakers (a few dozen of them) and immediately wake all wakers when the limit is reached. But now, when a read_from future is dropped, it removes its registered waker because we assume that the read_from operation was canceled.
What you should do instead is store the future inside UdpStream struct. Take a look at this for inspiration: https://docs.rs/async-net/1.5.0/src/async_net/tcp.rs.html#257-259

Thank you for the explanation! Storing the future was actually what I tried first, but ran into lifetime issues and then found that comment of yours. I'll try again storing the future then.

OK, I found a way to circumvent the lifetime issues. I don't think its super elegant, but it works: I'm moving both the socket and the buffer into the future, getting it back when the future is ready.
https://github.com/Frando/async-std-udp-test/commit/4b0dc438c417d5df84096df5f3086d9934425b0d
It works and will do for now I hope. Still have to see if I can make that compatible with sending over the buffer at the same time (or making it appear as such from the outside). Would prefer a way where I can store just the future without moving the socket in. I think that's doable as well, but not sure if it's possible without unsafe, and so far I never dealt with unsave future and pinning things. If there's an example somewhere I'd be interested.

I found a more elegant way to store and poll the future than in the example linked above, see https://github.com/Frando/async-osc/blob/72ec4cc7aac65891a241daab9d180b2ace636c70/src/udp.rs if interested.
Closing this, thanks for the help :slightly_smiling_face:


Hardcode username and password for standalone deployment

Hi again,
thanks for the standalone capabilities!
I think there are many cases in which a dashboard is basically read-only for a very large audience. In that case, it would be very useful to hardcode a user and password into the config file for standalone deployment. Would you consider such a use case in future? Not necessary bestest of practice everywhere of course but I think the option would still be helpful to many people.
Best

I think this will be helpful, but I'm also aware of the potentially big security issue here.
The app is currently designed to pick up the "environment variables" (those in config.json) at runtime. This also means that config.json is visible for everyone, example:
https://neodash.graphapp.io/config.json
Perhaps this can be a 'hidden feature' that is not visible by default, but appears in the developer documentation (with a ton of warnings). In other words, the standalonePassword/standaloneUsername passwords are not in config.jsonby default, but adding them will automatically fill in the credentials on user connect anyways. Thoughts?
This reminds me that I need to put some time into writing up a project wiki where all of these things are documented beyond the short description in the README. Will look into that one!

Yes, that sounds like a good idea. If it is prominently documented in a wiki, developers should be aware of the risks. Auto filling is exactly what is needed. Experience tells me that as soon as "user login" appears somewhere in big corporations, controlling and data privacy departments unfortunately have to intervene even if they do not wish to themselves. Default read-only users help to circumvent such hassle. Thanks for your quick response!

As of neodash 2.0.12, this functionality is implemented. Thank you! Closing the issue now.


Validation errors return an HTTP 500 Error

In User model, I changed  username attribute to unique and required.
// user-model.js - A mongoose model
//
// See http://mongoosejs.com/docs/models.html
// for more of what you can do here.

import mongoose from 'mongoose';
const Schema = mongoose.Schema;

let userSchema = new Schema({
  username: {type: String, required: true, unique: true, index: true},
  password: {type: String, required: true},
  createdAt: {type: Date, 'default': Date.now},
  updatedAt: {type: Date, 'default': Date.now}
});

let userModel = mongoose.model('user', userSchema);

export default userModel;

When I try to send a POST request to http://localhost:3030/users with empty body parameters, I get a 500 Internal Server Error.

However, I see in the console:
error: (400) Route: /users - user validation failed
info: BadRequest: user validation failed
    at Object.construct (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/core-js/modules/es6.reflect.construct.js:22:24)
    at BadRequest.ExtendableBuiltin (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/feathers-errors/lib/index.js:27:28)
    at BadRequest.FeathersError (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/feathers-errors/lib/index.js:105:87)
    at new BadRequest (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/feathers-errors/lib/index.js:145:79)
    at errorHandler (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/feathers-mongoose/lib/error-handler.js:23:25)
    at run (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/core-js/modules/es6.promise.js:104:47)
    at /Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/core-js/modules/es6.promise.js:115:28
    at flush (/Users/kulakowka/Documents/node.js/sandbox/feathers-chat/node_modules/core-js/modules/$.microtask.js:19:5)
    at nextTickCallbackWith0Args (node.js:452:9)
    at process._tickCallback (node.js:381:13)

In documents written that I'll get a nice error handling out of the box. But this is not the case.
Maybe I'm doing something wrong?
How to check the uniqueness of user name in another way?

I think I understand.
I removed the error handling from /src/middleware/index.js and added simple error handler to the end of file:
import path from 'path';
import notFound from './not-found-handler';
import { handler as error } from 'feathers-errors';
import logger from './logger';

export default function() {
  const app = this;

  // Add your custom middleware here. Remember, that
  // just like Express the order matters, so error
  // handling middleware should go last.
  app.use(notFound())
    .use(logger(app))
    // .use(error());

  // This simple error handler was added
  app.use(function(error, req, res, next){
    res.json(error);
  });
}

Now the error displayed in the proper format:

It works, but I'm not sure I did it right.

You need to set the Accept header in your request to application/json otherwise the default error handler thinks you want HTML.
The error page should probably show a better message though. You get a 400 code but it shows up as a 500 error page. It should probably just say something like "General error".

Thank you @daffl. I forgot about this header! :)


Possible bugs in message command when saving to DB

What steps will reproduce the problem?
First part - Set up messages and make them save to DB
https://www.yiiframework.com/doc/api/2.0/yii-i18n-dbmessagesource
common/config/messages.php
<?php

return [
	...
    'languages' => array_keys([
		'es' => 'Español',
		'ca' => 'Català',
		'en' => 'English',
	]),
    'removeUnused' => true,
    'markUnused' => true,
    ...
    // 'db' output format is for saving messages to database.
    'format' => 'db',
    ...
];

Also make sure you create the required tables by running the migration as instructed in API link.
Now add some translations inside some php files in your application:

<?php echo Yii::t('app', 'This is my first translation string'); ?>

Then run the messages command with your configuration file:
yii message common/config/messages.php

Until here, everything should have worked as expected and the translations are also working fine.
If you look into the DB you have both the source messages and the translation messages (NULL) rows inserted. You just have to edit the translations rows and add your translations.
Second part
This is where the bugs occur.
Add a new language into your configuration file:
<?php

return [
	...
    'languages' => array_keys([
		'es' => 'Español',
		'ca' => 'Català',
		'en' => 'English',
                'af' => 'Afrikaans', // <-- new language here
	]),
    ...
];

And also add a new translation string somewhere inside your application:

<?php echo Yii::t('app', 'This is a new translation string'); ?>

Now run the messages command again:
yii message common/config/messages.php

What is the expected result?

I expect the command to insert the new string in the source table
I expect the command to insert the NULL translation into the message table
I expect the command to not break
I expect the command, if run at a later time, to check and rebuild all the missing rows if the data is incomplete
I expect the command to consider obsolete the translations of a language that is no longer used and mark/delete them

What do you get instead?

The command inserts the new source message
The command inserts the NULL translation ONCE
The command then tries to insert another NULL translation for the same key (id-lang) because it considers the new added language as a missing language
I get a MySQL FK error and the remaining queries get cancelled and never get the chance to run so the messages table becomes incomplete
Also if I remove a language and run the command, the rows in the messages table are not removed

2023-07-31 12:43:37 [-][-][-][error][yii\db\IntegrityException] PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '366-af' for key 'PRIMARY' in /var/>
Stack trace:
#0 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/db/Command.php(1302): PDOStatement->execute()
#1 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/db/Command.php(1102): yii\db\Command->internalExecute()
#2 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/console/controllers/MessageController.php(421): yii\db\Command->execute()
#3 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/console/controllers/MessageController.php(331): yii\console\controllers\MessageController->saveMessagesToDb()
#4 [internal function]: yii\console\controllers\MessageController->actionExtract()
#5 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array()
#6 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/base/Controller.php(178): yii\base\InlineAction->runWithParams()
#7 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/console/Controller.php(180): yii\base\Controller->runAction()
#8 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/base/Module.php(552): yii\console\Controller->runAction()
#9 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/console/Application.php(180): yii\base\Module->runAction()
#10 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/console/Application.php(147): yii\console\Application->runAction()
#11 /var/www/vhosts/example.com/httpdocs/vendor/yiisoft/yii2/base/Application.php(384): yii\console\Application->handleRequest()
#12 /var/www/vhosts/example.com/httpdocs/yii(23): yii\base\Application->run()
#13 {main}

Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
8.1.19

Operating system
Windows 11

Do you have a fix for it?

@samdark yes I have created this PR https://github.com/yiisoft/yii2/pull/19934
Let me know what you think, the code has been reorganized into a different structure but keeping "the good" and adapting to fix the bugs and be more flexible.

Hi @atrandafir ,
it seems it's the same bug as I started here #17532
I haven't balls to fix it, it seems you have. Thank you.
Is it going to be merged?
I looked through your new code, I understand it and it seems right to me, but I'm not confident enough saying that there isn't any hidden bug.
I also tested it on my broken translations and it worked
UPDATING DB

SOURCE MESSAGE TABLE

Inserting new messages...1 saved.
Updating obsoleted messages...1 updated.

MESSAGE TABLE

Generating missing rows...1 for cs, 3 for sk, 2 for en, 1 for de, 2 for pl, 2 for it, 2 for es, 2 for sv.
Dropping unused languages...Nothing to do.

Hi @OndrejVasicek indeed it is the same bug as your issue.
And indeed the code block was a bit hairy to understand and fix, and also the logic involved.
But I think the way it works right now should be good and we shouldn't get any surprise.
I tried to think of most of the use cases so hopefully we should have everything covered.
But maybe in the future if this is ever rewritten, listing all the use cases and maybe do some testing would be a good idea in order make sure no new bugs appear.


Clean up code related to Graphics\5_Game\5_Background\0\Background.png

Can you write a one-sentence description of your request?
It appears that Graphics\5_Game\5_Background\0\Background.png has gone unused in the codebase but still exists in TextureLoader and SimpleStyle and should be cleaned out.

I have confirmed that this couldn't have worked anyway, even it attempting to use it, and it has likely been generating filesystem related errors in the application log, since the code specifying the texture path was bugged.


Show incorrect Minumum active value on the Network detail screen

Describe the bug
Show incorrect Minumum active value on the Network detail screen
To reproduce the behavior
Steps:

Go to the add to bond screen
Click on (!) button to go to the network detail screen then observe the minimum active value
Back to Add to bond screen then select any collator
Back to the Network detail and check minimum active value is displayed

Actual: Show incorrect Minumum active value on the Network detail screen

Minimum active = Max (MinStakeChain, MinStakeCollator)
Expect: Show correct information
Minimum active on the network detail = MinStakeChain

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1775-build-1.1.7-0-2023-08-10T04-35-33UTC.zip
Validation passed.


Add command to upgrade/downgrade litmusctl binary

We can add an upgrade/downgrade command for litmusctl binary, it can look at the matrix of versions in a file and upgrade/downgrade according to the user's choice.
example

litmusctl upgrade v0.5.0
litmusctl downgrade v0.4.0

Hey, I would like to work on this!
Can you please help me how to approach this?
Thank you.

Hi @imrajdas, is this done or yet to be done?

@imrajdas I'm trying to set the env variable by using this code os.Setenv("CLIVersion", CLIVersion) in some test file, but if I try to reaccess the same env variable in some other file say version.go, I'm not getting the updated value. On further digging, I found out that the environment variables are bound to the process in which they are set. If this is the case, how can I tackle this? What should I do to make it accessible everywhere?
This is the directory structure

Setting the env in test.go and trying to access the same in version.go.


Add readme for NPM

The dcql folder does not have a readme, resulting in no description being present on the NPM package page

done. For now I just copied the Readme


Update camel-core, camel-reactive-streams to 3.20.5

About this PR
📦 Updates

org.apache.camel:camel-core
org.apache.camel:camel-reactive-streams

from 3.20.2 to 3.20.5
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.camel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.camel" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #602.


Updating the deferred recovery logic

I observed that in most cases there was a "begin" message, but never a corresponding
"end" message surrounding the various sync loops that occur.  It appears that this was
caused by the deferal of the recover() method followed, immediately, by a panic(nil).
I have updated the offending logic to only issue the panic() call when an error is
returned from the recover() logic.

/assign @smarterclayton


Update System.Security.Cryptography.Pkcs from 5.0.0 to 9.0.0

What are you trying to accomplish?

Update System.Security.Cryptography.Pkcs from 5.0.0 to 9.0.0
Anything you want to highlight for special attention from reviewers?

This manual update is required, because Dependabot currently fails with the error^1:
updater | Starting analysis of System.Security.Cryptography.Pkcs...
  Determining multi-dependency property.
  Finding updated version.
The package System.Security.Cryptography.Pkcs.5.0.0 is not compatible. Incompatible project frameworks: net9.0
  Finding updated peer dependencies.
dotnet build in GetAllPackageDependenciesAsync failed. STDOUT:   Determining projects to restore...
/tmp/package-dependency-resolution_IISvDN/Project.csproj : error NU1102: Unable to find package System.Security.Cryptography.Cng with version (= 9.0.0)
/tmp/package-dependency-resolution_IISvDN/Project.csproj : error NU1102:   - Found 47 version(s) in nuget.org [ Nearest version: 6.0.0-preview.4.21253.7 ]
  Failed to restore /tmp/package-dependency-resolution_IISvDN/Project.csproj (in 513 ms).

This is because version 5.0.0 of System.Security.Cryptography.Pkcs has a dependency on System.Security.Cryptography.Cng^2. However, version 9.0.0 of System.Security.Cryptography.Pkcs no longer has this dependency^3.
Side note: @brettfo why do we have two Directory.Packages.props with the same packages? It appears that Dependabot is only updating one of them (nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Packages.props).
How will you know you've accomplished your goal?

Build completes, tests pass, and Dependabot is able to resume automatic updates.
Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

This is interesting.  *.Pkcs/9.0.0 does depend on .Cng, but it's expecting version 5.0.0 and not 9.0.0 so we're incorrectly passing through the 9.0.0 version.
As for the duplicate Directory.Packages.props, they can and should be combined.  I'll look into that.


Update local-universe resource rewriting to not include empty .images property as it will break on DC/OS 1.7 or older

/cc @tamarrow @jsancio @pyronicide

Customer ran into this issue today when a generated local universe had an empty .images in the mysql package
{ "assets": {"container": {"docker": {"mysql-docker": "master.mesos:5000/mysql:5.7.12"}}, "uris": {}}}

Related to #618


marko Test : Can't able run browser test in other browsers except chrome

<EMAIL_ADDRESS>Details
Trying to run browser test on firefox using marko-cli. Tried below both configs
markoCli.config.wdioOptions = {
        capabilities: [{
            browserName: 'firefox',
            // 'moz:firefoxOptions':
            //     {
            //         args:
            //             ['no-sandbox',
            //                 'disable-dev-shm-usage',
            //                 'disable-setuid-sandbox',
            //                 'headless',
            //                 'disable-gpu']
            //     }
        }]
    }

markoCli.config.wdioOptions = {
        capabilities: [{
            browserName: 'Firefox',
            platformName: 'Windows',
            os_version: '10'
        }]
    }

Expected Behavior
It runs only on chrome
Actual Behavior
Browser test should run on firefox
Steps to Reproduce

Include the above code in marko-cli.js
Run the browser test
Test run on chrome

Possible Fix

Additional Info
I suspect it's getting overwritten during the merge
https://github.com/marko-js/cli/blob/b3dd6912cb813d75c0417d74fabf3251736d0f97/packages/test/src/util/browser-tests-runner/index.js#L1

This isn’t documented well, but local headless testing is only possible with chrome at the moment (the chrome driver comes pre installed). For testing with other browser you can run the cli with the --debug flag and copy the url to the browser you wish to test. Not ideal, but it works for now.
You can also use BrowserStack or other selenium services to test against browsers in the cloud which works out of the box.

@DylanPiercey  Ohh okay cool. Thanks for clarifying. Maybe we need to document it. I will close this issue then.


SyntaxError: invalid syntax: reset = Reset(1, active=0, async=True)

python-37 prints this error:
/usr/local/bin/python3.7 /tmp/tmpdhipfzyy.py
  File "/usr/local/lib/python3.7/site-packages/pyfda/fixpoint_widgets/iir_df1.py", line 234
    reset = Reset(1, active=0, async=True)
                                   ^
SyntaxError: invalid syntax

removing /tmp/tmpdhipfzyy.py

FreeBSD 12.2

This file shouldn't be there, sorry. Please delete it if you can, it is a remainder of previous fixpoint implementations. But I don't quite understand why you're getting this error, the file shouldn't be used or imported anywhere. Are you running pyfda from the pyInstaller executable for Linux?

This code is called autiomatically from setup.py install.

I guess most people use pip install ... , that's why the error hasn't been noticed earlier. Thanks for reporting, I'll make a new release in the next few days that fixes the bug. I've pushed the change to the master branch already, if you install directly from the latest git master branch everything should be fine.


How to run the tests?

Hello, we have done some additions to this library and would like to give back the contributions. The thing is that we weren't able to run the test suite for the artifactory-client module.
We managed to pass the tests for the ning-client using a docker artifactory, but we didn't have the same luck with the artifactory-client-api tests.
I made a gist with the log: https://gist.github.com/amanya/f6bbc0c5b6c9a4c8970d
I was wondering if do you have some guidelines on how to run the testsuite.
Thanks!

I have the same problem. I've used the docker oss version of artifactory but almost all tests fail.

@vincentfree and @amanya,
The tests are currently testing all Artifactory features, including non-OSS ones.
As a workaround, you can probably comment out the test methods that use those features. I think it would be good to add a system property that will run OSS tests only. What do you think?
If one of guys would like to contribute that to the project, it will be greatly appreciated.


fixed isWithinBar() crash when there were less than 2 items in pathSegList

@adufilie Please see my comment on #1551. Thanks!

Edit: Never mind the tests; just could you give me an example case when this occurs? Thanks!

Closing in favor of #1550 (rebased on master)


(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

All the dates are being saved as UTC in the database but shows up in PST on the screen. Screen shot for reference :


Make ajax more successful

Status codes other than 200 are successful. Update to reflect the correct range.

I am ok with any 2xx status but not 3xx, they are not really success. They are mostly for browser or direct  request coding on server-side. For example, if you go to http://www.idangero.us/framework7/kitchen-sink/ and type in console (CORS in browser should be enabled):
$$.get('http://idangero.us', function (data){console.log(data)})

In network inspector you will see actually 2 requests:

one to http://idangero.us with 301 status (moved permanently)
and then browser will do the second request/redirect to http://www.idangero.us and respond with data and 200 status

So in this case we even can't catch the 3xx status. So i think it should be removed from "success" check, as it can produce unwanted results

With xhr (not network inspector), the 3xx status codes will be automatically dealt with, you will never see a 301 status code for example, it will perform the redirect internally and return the next status code :)

Right, so why we need to deal with it in XHR logic?) So can we keep it as xhr.status >= 200 && xhr.status < 300? At least, i will feel safe with it

< 300 is OK also, updated. My main concern was getting failures for 201 etc, which was causing me issues

Merged, thanks


Remove special characters such as * in paths and filenames

Its nearly impossible for Windows users to git clone this repository since it has special characters such as * in paths and filenames. Please remove them.
Please refer this like to get the list of characters to be replaced.

For reference, a full log of the error that appears
$ git clone https://github.com/maaz93/Algorithms_Example.git
Cloning into 'Algorithms_Example'...
remote: Counting objects: 1512, done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 1512 (delta 22), reused 36 (delta 8), pack-reused 1462
Receiving objects: 100% (1512/1512), 326.30 KiB | 447.00 KiB/s, done.
Resolving deltas: 100% (552/552), done.
**fatal: cannot create directory at 'A*Search': Invalid argument**
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'

@IshamMohamed @maaz93 Thank you. I will remove those.

After looking through the repo, I think only Dijkstra's  is an invalid folder name. Note that it has an extra space at the end of the name and that is causing the problem.
Also, as per @IshamMohamed 's link, the following characters are invalid

< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

Right now, only the space in Dijkstra's  is causing the problem.

@maaz93 Thank you. I will remove the space.


Validate dbt resource identifier to see if it is a valid airflow task id during conversion from dbt to Airflow

While parsing the dbt project, we should confirm if the node names we'll use to define Airflow task IDs are valid.
If they are not valid, we should at least raise a warning (probably an error message) explaining the issue to users.
We can accomplish this by using airflow.utils.helpers.validate_key.
This task is related to #636, but they are not duplicates and should not conflict.
This improvement came from a conversation with @MrBones757 , regarding Cosmos 1.2.2. More details:
When we create dbtNode objects in https://github.com/astronomer/astronomer-cosmos/blob/main/cosmos/dbt/graph.py#L367
We set the nodeName == alias, with a fallback to name if it doesn't exist.
We then create the airflow graph with that value here: https://github.com/astronomer/astronomer-cosmos/blob/main/cosmos/airflow/graph.py#L125
The issue: dbt doesn't impose limitations on node names, but airflow does as such. When we go to render the airflow dag in the UI, we get:
The key 'my$cool_alias' has to be made of alphanumeric characters, dashes, dots and underscores exclusively

For some reason, I'm not being able to assign this issue to @MrBones757 in the Github UI, but he is planning to work on this!

Before implementing this, i will wait on #636 to ensure there are no clashing changes.

@MrBones757  #662 has a first level of "validation" (conversion from dots to underscore)


reshard output mismatch

There's a pcc mismatch on reshard with row major tensors. To reproduce run pytest -svv "tests/ttnn/unit_tests/operations/test_core.py::test_reshard[input_height=512-input_width=1280-input_memory_layout=Layout.ROW_MAJOR-input_sharded_memory_config_args={'core_grid': ttnn.CoreGrid(x=8, y=4), 'strategy': <ShardStrategy .BLOCK: 3>}-output_sharded_memory_config_args={'core_grid': ttnn.CoreGrid(x=8, y=8), 'strategy': <ShardStrategy.BLOCK: 3>}-input_override=None-output_override=None]"
on aknezevic/reshard_pcc

will be tracked with subsequent reshard sweep .


Enhancing Superkit with Optimal Tools and Practices

Hi @anthdm,
As we progress with the Superkit project, which aims to build high-performance web applications swiftly using minimal team resources in Go, I’d like to open a discussion about the frameworks, tools, and libraries we should adopt to ensure we achieve our goals effectively.
Key Points for Discussion:
1. Database Choices:
Currently, we are using SQLite3. While this is suitable for development, we suggest allowing users to select other relational databases like PostgreSQL. What do you think about making the database choice configurable? (When I review the code database configurations part is adaptable for this.)
2. Testing and QA:
What testing frameworks and tools should we adopt for unit, integration, and end-to-end testing in Go? (e.g., Testify, GoConvey, Selenium)
What best practices should we follow to maintain high code quality and performance benchmarks?
3. Security Considerations:
What security best practices and tools should we incorporate to ensure our applications are secure from the outset? (e.g., security linters, vulnerability scanners)
4. Other Tools and Libraries:
Are there any additional tools, libraries, or resources you believe would be beneficial for the Superkit project? (e.g., Redis for high performance and caching)
Please share your thoughts, experiences, and any resources that you think would help us make well-informed decisions. Your input will be crucial in shaping the direction of our project and ensuring we build a high-performance, maintainable, and scalable application.
Right now I want to draw the architecture of the project and then work on it for todos.
Thank you for your contributions!

This seems to be a LLM generated text. Closing this for now.

No, this is the template I created for the discussion but a few list items were created by LLM. I'll update this discussion for clarity. I'm just working on Redis for DB links and caching on superkit. The other thing that the design drawing could be useful for the future, I just wanted to create a discussion for what could be for the future?
Thank You!


Azure CLI soft requirement for tutorial

There is a soft requirement of having Azure CLI (or being able to set it up) when going through this tutorial.
The code samples are great and helpful, but without the azure CLI, you have to hunt around for various keys/compatible paths a lot more. I'm currently a bit stuck but I don't have subscription access to set up the store for CLI which slows my progress.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 666d1390-a995-fb5f-e1ee-49e28c50e901
Version Independent ID: d699e566-83d8-5af9-56a5-4baa56ae0455
Content: Send telemetry to Azure IoT Hub quickstart (C#)
Content Source: articles/iot-hub/quickstart-send-telemetry-dotnet.md
Service: iot-hub
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@JonathanPalmerGD An option to the portal CLI is to run CLI locally please read: Install Azure CLI on Windows

Thanks for the detailed feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@JonathanPalmerGD - what type of Azure subscription are you using - I see you mentioned that you couldn't set up the Azure cloud shell - can you provide more detail? The Quickstart specifically uses the Azure cloud shell to minimize the setup required on your local machine. Thanks!

I don't exactly know the details of the subscription. I wasn't the one who set it up or manages it.
It gives a 'Storage Creation failed, Error 403 - code: RequestDisallowedByPolicy, etc'
It's possible it's a MSoft thing due to specific org policies?
I could connect you to an individual who would have more info than myself if desired.

@JonathanPalmerGD - it sounds as if your subscription was set up in a non-standard way. We would expect someone doing the Quickstart to have set up (or have access to) a standard subscription: https://azure.microsoft.com/free/?WT.mc_id=A261C142F
If you want to follow up on creating a Cloud Shell with your subscription, can you open an issue on https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart
To keep the Quickstart brief, we opted to use the Azure CLI to retrieve the various configuration values needed to avoid having lots of clicking around in the portal. I know that in the portal you can find a connection string for the Event Hub compatible endpoint, but I still think it's easier to run a script to retrieve three values to paste into code.
We will take your comments into account when we next review these articles - and thanks for your detailed feedback.

I'm going to request that this issue is closed, but feel free to reopen it with any follow up questions. Thanks!
#please-close


Check if _array_cast should be before or after the multiplication with the exponential factor

The current way of doing it (_array_cast before multiplication) is faster.


add support to .jenkinsfile files

icon request pls

v0.0.8 has support for jenkins files (via https://github.com/miguelsolorio/vscode-symbols/pull/54)


amqp

event-hub support amqp?

Hello 👋 Is this question related to any specific piece of documentation?


Initial test around stampy.ts

This PR uses the miniflare jest env (https://miniflare.dev/testing/jest) to run a test on code that has a dependency on CF workers, in this case server-utils/stampy.ts.
The new test, in stampy.spect.ts, relies on a data which is stored in the repository in the mocks directory.
The data can be refreshed manually by running npm run refresh-test-data.
The only app code change (other than new exports) a cut-paste of Coda URL generation  from stampy.ts to a separate file. Other wise, compilation of the refresh coda data script fails due to missing CF vars (e.g. CODA_TOKEN).
TODO:

[x] ensure that latest code is being tested (as it seems to be the built CF worker file that is executed)
[x] add script for generating test data
[x] write README on how to use the script
[x] parameterize the test to run for each result of the mock data
[x] share the same question ids between the script and the test (was too challenging to get the compilation to work)
[x] use questionId 0 for test
[x] manually run app to do basic sanity test (e.g. can app still get question details from Coda)

Relates to issue #191

Thanks for the review @Aprillion . I will make the suggested changes and then mark as Ready for Review again

@Aprillion I think all of the comments from your first review have been addressed. Please give the PR another review when you have the opportunity (no rush at all 😄  ).

@Aprillion The PR is ready for review again when you have time. No rush.

Hey @Aprillion, no rush, but just checking in here. What would you say the next steps for this PR would be? Are there additional reviews or changes required?
If it is indeed ready and it is a good time to merge, could you please do so when you have capacity? I don't currently have write access to the repo, so I can't merge it myself.

oh, GH actions needed some extra approval, not just PR approval.. the merge button should get enabled after the checks run I hope..

@jrhender one of the tests failed in https://github.com/StampyAI/stampy-ui/actions/runs/6245510948/job/17457463802?pr=276#step:3:139 FAIL app/server-utils/stampy.spec.ts -> loadQuestionDetail › can load question 0, can you please check?

@Aprillion could you approval the workflow again when you have a moment please?
I think the issue was that the feature branch (miniflare-jest-env) didn't have the last changes so it was trying to make a request to Coda that probably wasn't available due to some change in Coda. I thought about merging in master before posting my earlier message but I was too lazy to do so 😓  .
At any rate, the CI is now passing on my GH fork (https://github.com/jrhender/stampy-ui/actions/runs/6435300979/job/17476259392?pr=2), so I'm pretty sure it will pass now in this PR.

Whoops, sorry, I guess it needs to be reviewed again as well as I updated the cached coda data in the last commit: https://github.com/StampyAI/stampy-ui/pull/276/commits/30845a9c1ec090df88adefe44606facb7a60a4c8

ok, the test passed for PR #337 => https://github.com/StampyAI/stampy-ui/actions/runs/6439654334/job/17487581099?pr=337
😌


Remote with data notification not displaying badge number

everything works fine with custom, remote notification.
also local & schedule notification. But remote with data failed.
RN version : 5.0
RN-FCM: ^11.0
im doing something like this.

Cheers Thanks

@jaysmoodge - is it possible to share your custom notification payload? thanks..

sure.. il make a sample later.
On Feb 20, 2018 2:29 PM, "shekharskamble"<EMAIL_ADDRESS>wrote:

@jaysmoodge https://github.com/jaysmoodge - is it possible to share
your custom notification payload? thanks..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/evollu/react-native-fcm/issues/729#issuecomment-366879610,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhdfjcPVGG_fCdPLbymjsRXQAHc1WRoDks5tWmZmgaJpZM4RUTOx
.

@shekharskamble
something like this
"data":{custom_notification": {
"title": "Simple FCM Client",
"body": "Click me to go to detail",
"sound": "default",
"priority": "high",
}
}.
you can try the working example.
to change badge u can try something like.
FCM.setBadge( badege => {
FCM.getBadge()+=1;
}).
im not in my PC im just using my phone.
Hope it helps.

@ctrlspcmac Thank you for the example to change the badge app needs to be running am I right?

@shekharskamble not neccesarily, when the FCM works fine in your app.  when notif triggers the FCM.on(event.notif)....{
//change badge
FCM.setBadge( badege => {
FCM.getBadge()+=1;
}).
}

u mean through payload? i think its possible , check the sample working
code. =)
On Fri, Mar 2, 2018 at 4:21 PM, shekharskamble<EMAIL_ADDRESS>wrote:

@ctrlspcmac https://github.com/ctrlspcmac can we run the FCM.On or
FCM.setbadge in lets say cloud function?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/evollu/react-native-fcm/issues/729#issuecomment-369853534,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALwBfrV_gbo7TJ5qVv2n4x6FVho1dQgWks5taQEigaJpZM4RUTOx
.


Remove defaults for AIX and Solaris as we can't verify/maintain these

Since all settings in the params class are now defaults for class parameters I'll remove the defaults for AIX and Solaris as we have no way to verify their correctness.
AIX and Solaris users can still use the module by providing their own parameters.
Builds on #99

Since the fail() for unsupported os/os-versions is removed I think it's fair to drop those defaults


Bug: ESC panel isn't working properly

The ESCs I'm using require a throttle signal of 40Hz-490Hz. The DroneCAN ESC panel sends throttle messages at 10Hz (0.10 sec). Changing the broadcast interval down to 0.01 sec doesn't increase the frequency of uavcan.equipment.esc.RawCommand packets. Note: I'm using DroneCAN GUI Tool v1.2.25 on windows.

I then test using UAVCAN GUI Tool V1.0.0 on windows. I open the ESC panel and set the broadcast interval to 0.01 sec (100Hz). Then I go to the Bus Monitor, and I see that the frequency is 100Hz

In summary, DroneCAN GUI Tool doesn't spin my motors, but UAVCAN GUI Tool works great.
If PX4 and ArduPilot firmware send RawCommand at 50Hz, why isn't 50Hz the default in the ESC Management Panel?

fixed in #60


Expose module.proxy.lambda_edge_arn in tf_next outputs

It would be nice to add outputs into the outputs.tf for:

target_origin_id
lambda_arn

for tf_next so that it is then accessible for custom ordered_cache_behavior blocks in your own main.tf for customizing the CloudFront distro.  As an example use case, consider requests to /api that you do not want to cache at all.  I think the current recommendation would be to do something like this:
  ordered_cache_behavior {
    path_pattern = "/api/*"
    allowed_methods = ["GET", "HEAD", "OPTIONS", "PUT", "PATCH", "POST", "DELETE"]
    cached_methods = ["GET", "HEAD", "OPTIONS"]
    target_origin_id = "tf-next-s3-static-content" # must be hard-coded

    compress = false
    viewer_protocol_policy = "redirect-to-https"

    origin_request_policy_id = data.aws_cloudfront_origin_request_policy.all_viewer.id
    cache_policy_id = data.aws_cloudfront_cache_policy.caching_disabled.id

    lambda_function_association {
      event_type = "origin-request"
      lambda_arn = module.tf_next. ... # this is completely inaccessible
      include_body = false
    }

which is ugly and incomplete.  The alternative is to edit the default_cache_behavior to customize the policies there hwich is how I am currently going to do this, but I would rather not hack into TF Next's defaults.

I could also go at this using dynamic but that is also going to lead to some really hacked code that depends on TF Next not changing its underlying resources rather than exposing them for consumption.

You should be able to use the cloudfront_default_cache_behavior for this use-case.
A default cache behavior in CloudFront has the same properties as an ordered cache behavior besides the path_pattern property.
Not tested, but I think something like this should work:
module "tf_next" {
  source = "dealmore/next-js/aws"
  ...
}

locals {
  # Create a new ordered cache behavior from the default cache behavior by adding the path_pattern property
  api_cache_behavior = merge(module.tf_next.cloudfront_default_cache_behavior, {
    path_pattern = "/api/*"
  })
}

resource "aws_cloudfront_distribution" "distribution" {
  ...

  dynamic "ordered_cache_behavior" {
    for_each = [local.api_cache_behavior]

    content {
      path_pattern     = ordered_cache_behavior.value["path_pattern"]
      allowed_methods  = ordered_cache_behavior.value["allowed_methods"]
      cached_methods   = ordered_cache_behavior.value["cached_methods"]
      target_origin_id = ordered_cache_behavior.value["target_origin_id"]

      compress               = ordered_cache_behavior.value["compress"]
      viewer_protocol_policy = ordered_cache_behavior.value["viewer_protocol_policy"]

      origin_request_policy_id = ordered_cache_behavior.value["origin_request_policy_id"]
      cache_policy_id          = ordered_cache_behavior.value["cache_policy_id"]
    }
  }
}

Ah, got it.  That's a really smart use of merge() with locals for overriding as the latter source of input for the merge.  I will give that shot.  Maybe this is worth putting in the docs somewhere in https://github.com/dealmore/terraform-aws-next-js/tree/main/examples/with-existing-cloudfront.  Thank you for the prompt reply!

I had to go one level deeper accessing the default behavior like:
locals {
  api_cache_behavior = merge(module.tf_next.cloudfront_default_cache_behavior.default_behavior, {
    path_pattern = "/api/*"
    ...
  })
}

but then everything worked as suggested for merging in overrides.  I sincerely appreciate the recommendation and think this would be great to have in the docs.  Thank you!

Ah yes, forgot that we put the actual behavior in a sub-property so that it could directly consumed by a dynamic block. Glad you found out by yourself 👍
I really like the idea of adding common use cases from the issues to the docs.
Behind the scenes I already started working on a dedicated website for this project and I plan to put guides on it that cover advanced customization of the module.
This way we can ensure that the examples stay simple and understandable and can also provide resources for working with the module.
Stay tuned for more, happy I could help 😊


Fix whats-new

Oops. I used "Github Codespaces" to edit whats-new, but it turns if you commit in there, it just commits to main!
This fixes the pre-commit error.

Wait what version are we on right now?? :sweat_smile: Are you in middle of issuing a release? The whats-new in main doesn't match what's actually been released atm

Sorry  for the confusion. Releasing 2023.02.0 now. I  meant to create a PR with the whats-new updates, but committed to main by mistake.

Thanks @dcherian!


Fixed #24227 -- Replaced isinstance checks by field properties

Tests failures seem unrelated to the patch.

Buildbot, test this please.

Probably caused by a forced push after the Jenkins job started.

No, I didn't force push this patch yet (and I always wait for test finishing before force-pushing).

Really odd then :/ I thought it could be a forced-push because of the Jenkin failure FATAL: Could not checkout e578d57cc9417dcea28d6be458b80aa246421d18 which is similar.

+1

@loic, any objection to this?

I'm +1 on the principle, but if we do this we should also do it for the reverse fields.

Would it make sense to have a patch with only the ManyToMany changed (which might sometimes lead to field.many_to_many or isinstance(field, ForeignKey), at least until we do the ForeignKey part)?

#6265 is a version with only the ManyToMany occurrences changed.

Since we had some trouble with a similar change in the past in relation with django-taggit I think we should keep an eye on this when we go forward.

What's your thinking about changing isinstance(..., models.ManyToOneRel) as Loic mentioned?
contrib/admin/templatetags/admin_list.py:                if isinstance(f.remote_field, models.ManyToOneRel):
contrib/admin/views/main.py:                if isinstance(field.remote_field, models.ManyToOneRel):
core/serializers/xml_serializer.py:            elif field.remote_field and isinstance(field.remote_field, models.ManyToOneRel):
core/serializers/python.py:            elif field.remote_field and isinstance(field.remote_field, models.ManyToOneRel):

I'll surely address the ManyToOneRel issue, in a separate commit.

Not changed in this commit, but noticed in docs/ref/checks.txt`, * fields.E311: <model> must set unique=True because it is referenced by a ForeignKey." should be "foreign key".

I guess the commit message could be a bit more specific as I revised, otherwise, LGTM. Do you want to use "Refs" in the commit message if there is still more work to do for the ticket?

Claude, I'm not sure what the status is here.

I'm not feel very confident going forward with this. Sorry, anyone can continue from where I left it.


  If you took the time to read ANYTHING in here, you would see that it is being worked on.  You are free to NOT use the software if it causes you that kind of pain that you must try to lash out at someone for no reason other than you do not have any patience nor take ANY time to see what is going on before making accusatory remarks.

You were right Mr. Rozwood, people don't listen. I've explained this to
others as you have and they keep writing back "it doesn't WORK"...and now
this guy is swearing at you!.
On Tue, Jul 26, 2016 at 10:35 AM, Daniel Rozwood<EMAIL_ADDRESS>wrote:

Do you really think swearing is going to get you anything any faster? If
you took the time to read ANYTHING in here, you would see that it is being
worked on. You are free to NOT use the software if it causes you that kind
of pain that you must try to lash out at someone for no reason other than
you do not have any patience nor take ANY time to see what is going on
before making accusatory remarks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zhuowei/MCPELauncher/issues/1357#issuecomment-235344586,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATqRplKKXUylBGQsXMGQMuwUw389NH2Dks5qZkVXgaJpZM4JVZT1
.

LMAOO

I could respond to the OP, but then I'd probably start swearing etc... This is hilarious tho, xD

Changed my mind about not responding...
Tell me, why do you think @zhuowei hasn't updated BlockLauncher yet? Hm? Well, maybe you could've considered that he might be BUSY? You forget that this app is something he VOLUNTARILY made for the community and it is HIS choice to update it. In my opinion I think the reason he's not updated the app is because people like you are getting impatient and cussing at him and being overall disgusting. Don't you think he'd be put off if he saw constant people demanding him to update it and swearing? Wouldn't you? Have some patience and maybe, just maybe, you can look at the 11 PAGES OF THE SAME ISSUE BEFORE YOU MAKE ANOTHER? Next time you're about to complain, maybe think about not insulting them? Oh, sorry I forgot! This ISSUE TRACKER is an insult submitter! That makes sense!
Have a good day. I don't want to see you on this issue tracker again unless you have a valid thing to report.

Well said...
On Tue, Jul 26, 2016 at 11:38 AM, Black-DeathPE<EMAIL_ADDRESS>wrote:

Changed my mind about not responding...
Tell me, why do you think @zhuowei https://github.com/zhuowei hasn't
updated BlockLauncher yet? Hm? Well, maybe you could've considered that he
might be BUSY? You forget that this app is something he VOLUNTARILY made
for the community and it is HIS choice to update it. In my opinion I think
the reason he's not updated the app is because people like you are getting
impatient and cussing at him and being overall disgusting. Don't you think
he'd be put off if he saw constant people demanding him to update it and
swearing? Wouldn't you? Have some patience and maybe, just maybe, you can
look at the 11 PAGES OF THE SAME ISSUE BEFORE YOU MAKE ANOTHER? Next time
you're about to complain, maybe think about not insulting them? Oh, sorry I
forgot! This ISSUE TRACKER is an insult submitter! That makes sense!
Have a good day. I don't want to see you on this issue tracker again
unless you have a valid thing to report.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zhuowei/MCPELauncher/issues/1357#issuecomment-235364173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATqRpkm7CSSR0c59iEg-frJDRmcmdLW-ks5qZlQ6gaJpZM4JVZT1
.

I've spent a month and 20 days doing what can be done in a week. In the meantime even Toolbox has updated twice.
I know I'm the worst developer in the world. I know this. You don't have to tell me.

'-' ;-;

All in favor of swatting uskaz say I.
jk dont take this seriously

I


homedir(): add special case for Haiku

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

I'm not sure if this is really the best way to implement this, but Haiku generally avoids dotfiles in the user's home directory, and should be placed in the settings folder without a leading dot.

I think this may be best suited for https://github.com/rust-lang/rfcs/pull/1615 perhaps? I'd be hesitant to merge this before that RFC is decided on

Ah yes, I was considering using one of the XDG environment variables, as these point to correct locations on Haiku.

Ok in light of that I'm going to close this for now, but hopefully it's easy to resubmit once the RFC is decided on!


Runelite Overriding normal game features. Or breaking them.. Not sure

Please check if your issue is not a duplicate by searching existing issues
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'XP ORB toggle, Normal runescape function, Right beside hp Orb'
Click on 'Right click and click setup'
Scroll down to 'Change Position to Middle or Left'
Does not change position to left or middle...

When doing this, the xp drop moves to the middle or left, BUT the experience tracker box, stays to the right. Normal runescape allows this to be moved left, middle or right. This is really pissing me off because i want it in the middle, Works as it should on normal runescape client, osb and konduit, Just not runelite -,-
Expected behavior
When changing to middle or left, the xp tracker box should move left or middle
Screenshots
This is how its meant to behave > https://gyazo.com/95b3e2086e8a2483d93bdd8374e0ef17
This is how it behaves on runelite > https://gyazo.com/32ecef9244f1f918e0cd6e0c8aa7c0a1
Excuse the writing on the picture, i was asking my clannies.
Environment (please complete the following information):

OS: Windows 8.1 Pro
RuneLite version: 1.4.23
Launcher version: 1.5.2

Additional context
Add any other context about the problem here, e.g. logs. Your client logs can usually be found in
C:\Users\<your_user_name>\.runelite\logs on Windows and ~/.runelite/logs on Linux and macOS.

Move the box by holding alt

lol how would i have known a normal feature was changed like that? Is there a page i can read normal feature changes? please? im trying to switch from konduit to runelite, but some stuff is odd for me, i wouldnt of made a report if i knew it was that simple :D

the wiki


bug when loading a scan report

After doing a clean build of Perseus I get the following error from _create_source_schema_by_scan_report:
(full stack below)
init() got multiple values for argument 'schema'
Looking at this
https://stackoverflow.com/questions/75282511/df-to-table-throw-error-typeerror-init-got-multiple-values-for-argument
suggests that the issue could have to do with pandas version mismatches. I'll also attach a pip freeze.

Has anybody else encountered this?
The version of pandas is quite old, many of the libraries are several years old (namely Angular) and this creates a number of landmines when debugging/dev'ing. Are there any prospects for getting the libs up to date. I suspect this would be a prerequisite for most new work.

[2023-04-14 02:35:28,397] ERROR: http://localhost/backend/api/create_source_schema_by_scan_report request returned error: init() got multiple values for argument 'schema'
backend                   |   File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1516, in full_dispatch_request
backend                   |     rv = self.dispatch_request()
backend                   |   File "/usr/local/lib/python3.7/site-packages/flask/app.py", line 1502, in dispatch_request
backend                   |     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
backend                   |   File "/app/utils/username_header.py", line 12, in decorator
backend                   |     return f(current_user, *args, **kwargs)
backend                   |   File "/app/perseus_api.py", line 82, in create_source_schema_by_scan_report
backend                   |     raise error
backend                   |   File "/app/perseus_api.py", line 78, in create_source_schema_by_scan_report
backend                   |     .create_source_schema_by_scan_report(current_user, etl_mapping.id, etl_mapping.scan_report_name)
backend                   |   File "/app/services/source_schema_service.py", line 32, in create_source_schema_by_scan_report
backend                   |     return _create_source_schema_by_scan_report(username, etl_mapping_id, scan_report_path)
backend                   |   File "/app/services/source_schema_service.py", line 92, in _create_source_schema_by_scan_report
backend                   |     raise e
backend                   |   File "/app/services/source_schema_service.py", line 55, in _create_source_schema_by_scan_report
backend                   |     from overview group by table;""")
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandasql/sqldf.py", line 156, in sqldf
backend                   |     return PandaSQL(db_uri)(query, env)
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandasql/sqldf.py", line 58, in call
backend                   |     write_table(env[table_name], table_name, conn)
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandasql/sqldf.py", line 121, in write_table
backend                   |     index=not any(name is None for name in df.index.names))  # load index into db if all levels are named
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandas/io/sql.py", line 440, in to_sql
backend                   |     pandas_sql = pandasSQL_builder(con, schema=schema)
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandas/io/sql.py", line 508, in pandasSQL_builder
backend                   |     return SQLDatabase(con, schema=schema, meta=meta)
backend                   |   File "/usr/local/lib/python3.7/site-packages/pandas/io/sql.py", line 940, in init
backend                   |     meta = MetaData(self.connectable, schema=schema)
APScheduler==3.9.1
azure-common==1.1.28
azure-core==1.26.4
azure-identity==1.10.0
azure-keyvault-secrets==4.4.0
backports.zoneinfo==0.2.1
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
click==8.1.3
cryptography==40.0.1
Flask==2.0.3
Flask-Cors==3.0.10
greenlet==2.0.2
idna==3.4
importlib-metadata==6.3.0
isodate==0.6.1
itsdangerous==2.1.2
Jinja2==3.1.2
MarkupSafe==2.1.2
msal==1.21.0
msal-extensions==1.0.0
msrest==0.7.1
numpy==1.21.6
oauthlib==3.2.2
pandas==0.23.4
pandasql==0.7.3
peewee==3.16.0
portalocker==2.7.0
psycopg2-binary==2.9.6
py-postgresql==1.2.2
pycparser==2.21
PyJWT==2.6.0
python-dateutil==2.8.2
pytz==2023.3
pytz-deprecation-shim==0.1.0.post0
requests==2.28.2
requests-oauthlib==1.3.1
six==1.16.0
SQLAlchemy==2.0.9
typing_extensions==4.5.0
tzdata==2023.3
tzlocal==4.3
urllib3==1.26.15
waitress==2.1.2
Werkzeug==2.2.3
xlrd==1.2.0
zipp==3.15.0

this bug is reproducible in the images new images from docker #31

@bradanton please investigate the issue asap

Seeing the same error as well
(Failed to load report: __init__() got multiple values for argument 'schema')

the issue was fixed, should work now.


Feature/restore password screen

Let's use common naming for PR. And would be good to link issues to PR.


CHR-22: This PR has an issue in the title from the get go

Github action should not create an issue or update the title

closing


Temporary PR

Temporary PR

Temporary PR as suggested by @bodhish .
Fixes #8302

Purpose
This PR is a temporary solution to provide visibility while work is in progress. Final improvements and refactoring will follow.

I am deleting this PR and going to draft another one with suggestions


Wip multimaster

Note: Sentinal tests currently failing, and cluster tests are crashing.  Standard tests pass.


Ratelimit

The rate limit info is exposed as a hidden property on the user object.

@millette friendly ping :)

Sorry, been overwhelmed, back early next week. PS: Got Konami code? http://www.rollodeqc.com/ and the Deep Web documentary now has French subs :-)

Closing for lack of activity. Happy to reopen if you ever want to finish this ;)


TIM-215 Announcement item on feed

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#126  👈
#125
#124
#122
#121
#120
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tamrivera05 and the rest of your teammates on  Graphite


Upgrade github.com/lestrrat-go/jwx to 1.2.12

Hi,
I am the author of github.com/lestrrat-go/jwx. During a routine search I noticed that this project uses a rather antiquated version of that library.
After reviewing I realized that you probably have not upgraded the module because jwt.Set has been turned into an interface during the v0.9.x to v1.x transition. You probably needed to allow private parameters in the jwk.Set deserialization. I have tentatively implemented it in the main branch for github.com/lestrrat-go/jwx, and applied the changes I think are required to make things work on your end. Currently the PR uses an unreleased version of github.com/lestrrat-go/jwx. If these changes actually work for you, I should probably release 1.2.12 first, and then have this PR merged.
Please note that I have only verified that make unit mostly works -- I did not run the TestRemapConfig and its related tests, and did not verify trafficcontrol running in any other form.
Also, I reviewed your PR template, but didn't think this particular PR really fits into your regular type of PR. I especially have no clue how trafficcontrol works, and just changed the minimal code so that it works with the new version of jwx. And to that extent, I made the judgement call to set aside your templates, as I do not believe I can really respond to your PR template.  I feel bad for ignoring the rules, but I hope you understand my position.

Please note that I have only verified that make unit mostly works -- I did not run the TestRemapConfig and its related tests, and did not verify trafficcontrol running in any other form.

Mostly we rely on automated testing these days, at least for changes like this. So don't worry about it, all the checks we want to run are being run.

Also, I reviewed your PR template, but didn't think this particular PR really fits into your regular type of PR. I especially have no clue how trafficcontrol works, and just changed the minimal code so that it works with the new version of jwx. And to that extent, I made the judgement call to set aside your templates, as I do not believe I can really respond to your PR template. I feel bad for ignoring the rules, but I hope you understand my position.

That's fine. By the way, "trafficcontrol" sort of implies that this project is one main program, but actually it's more accurate to say that Traffic Control is a collection of software, rather than a single binary you run on its own. FYI.
Anyway, as of right now we have three failing checks. First, it looks like the dependency on your old 0.9 version is still in there, so it needs a go mod tidy. Then, go vet is showing some things it would like changed. Idk if you want to bother with that though, because more importantly it seems like these changes break the API. It's actually pretty remarkable that you've managed to make those changes with no understanding of how ATC works and not break the stable APIs at all. But our unstable APIv4 needs client changes to support the server changes, and it's probably gonna need to be one of us that makes that change. I nominate @zrhoffman who first noticed our version of jwx was causing some issues in #6354.

Thanks, I fixed one of the failing tests, but the other one will need additional fixes in my part -- currently jwk.Set does not allow setting private parameters, but you programmatically create a jwk.Set in one of the tests. I'll com back around to it sometime later today.

Fixed in  a3adfe9. I couldn't remove the indirect dep to github.com/lestrrat/go-jwx (the old one) ATM, I wasn't sure where it was being used.
Please let me know if I can help you with anything else.

I have a PR open against this branch at lestrrat/trafficcontrol#1 that fixes the license and go module issues

I believe I addressed the issues. PTAL again.


Fill in missing source endpoint

Sets the source endpoint if it is missing from the submitted message. This will prevent extraction errors. Since the jurisdiction had to authenticate and can only submit to their endpoint, this is not a security risk to set the endpoint for them from a look up table.
This PR is dependent on branch 471 getting merged into the vrdr-dotnet library so it can look up the endpoint by jurisdiction ID.

remove auto-population
id, destination endpoint, source endpoint, are all required, return a 400 if any of those required fields aren't populated


I'm wondering if the current validation system is overly complicated

Why have a Valid<Email> type, when you could just have an Email type with a failable initializer?
I'm guessing it's not because of the magic "example@domain.com".validated() method, because you could just as easily do that with the Email type if you'd let that conform to some protocol called Validator.
I'm guessing it's also not because of how easily you can compose validators in the current system:
class Name: ValidationSuite {
    static func validate(input value: String) throws {
        let evaluation = OnlyAlphanumeric.self
            && Count.min(5)
            && Count.max(20)

        try evaluation.validate(input: value)
    }
}

Because you could just as easily do this:
struct Name: Validator {
    let value: String

    required init?(_ value: String) {
        guard value.isOnlyAlphanumeric()
            && value.hasMin(count:  5)
            && value.hasMax(count: 20) else {
            return nil
        }

        self.value = value
    }
}

And of course methods like isOnlyAlphanumeric() would need to be defined somewhere else, but so would the other validation suites like OnlyAlphanumeric. The only difference is that in my model those methods are simply extensions of for example String.
Can anyone explain to me the significant benefits of the current system? Because if the benefits are not significant then I propose to ditch that system. I believe having a simpler system with the fewest demands on how to shape your types is always better, because it gives more freedom to the developer.

The system I have in mind would be much simpler. We could have a very simple protocol to allow for the .validated() method:
protocol Validator {
    associatedtype ValueType
    init?(_: ValueType) throws

So that we can write stuff like:
protocol Validatable {
    func validated<T: Validator where T.ValueType == self>() throws -> T
}

extension Validatable {
    func validated<T: Validator where T.ValueType == self>() throws -> T {
        guard let validated = try T(self) else {
            // throw some general error
        }

        return validated
    }
}

extension String: Validatable

But that's not very different from what we have. I just wanted to show that we wouldn't lose any features per se. Things just get simpler, like our model would look something like:
class Person: Model {
    var id: Value?
    var name: Name
    var email: Email
    var age: Age
}

extension Person {
    struct Age: Validator {
        let value: Int

        init?(_ number: Int) {
            guard 18...120 ~= number else {
                return nil // not a valid adult human age
            }

            value = number
        }
    }
}

This also happens to give Age a nice namespace Person.Age, which can come in handy since the age of other things might not have the same limits (a tree for example).

@Evertt Thanks for another great proposal! We put a lot of time and thought into the current validation system, so I think this warrants a bit of extra discussion time so we can way all the pros and cons effectively.
I'll try and dig in a bit deeper in the next couple days personally, I'm looking forward to seeing some of the feedback on this 👍


No analog audio support in 2.91

There has been a breaking change in 2.91 that prevents using analog audio out (headphone jack).
In earlier versions (i.e. 2.88.5) default configuration provides /dev/snd/by-path/platform-bcm2835_audio
alsa show one soundcard with many outputs:
bash-5.1# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 7/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
However in newest version multiple cards for both hdmi ports are visible (I believe this is change from upstream kernel), but there is no analog audio card by default.
ls /dev/snd/by-path/platform-fef0
platform-fef00700.hdmi  platform-fef05700.hdmi
Furthermore kernel module snd_bcm2835 is not loaded at all by default. I tried to load with various module parameters but with no luck. BTW pulseaudio does not see any cards on 2.91
What's possible to do to get analog sound in newer images, if it's not on in default?

So the problem with newest release is that if we are using vc4-kms-v3d overlay, we are having just two hdmi sound devices in /dev/snd/by-path/. If we do not load this overlay or load vc4-fkms-v3d , we have /dev/snd/by-path/platform-bcm2835_audio . I think this is breaking change that wasn't present in earlier versions.
How do we use sound  via headphone jack when loading vc4-kms-v3d overlay?

I found this interesning information:
<...> I figured something out that I have not seen pointed out anywhere that I recall. But if you use dtparam=audio=on in your config.txt, it does different things based on its relative position to dtoverlay=vc4-kms-v3d-pi4.
If it follows the dtoverlay=vc4-kms-v3d-pi4 and before another dtoverlay command, it becomes a parameter to the dtoverlay, and acts to turn on digital audio. Even if you set dtoverlay=vc4-kms-v3d-pi4,noaudio=on (which turns digital audio off).
However, if dtparam=audio=on is placed before dtoverlay=vc4-kms-v3d-pi4 it turns on analog audio via bcm2835.
So I turn on analog audio and turn off digital audio:
dtparam=audio=on
dtoverlay=vc4-kms-v3d-pi4,noaudio=on
I can confirm that those parameters in opposite order doesn't fix analog audio issue.

Hi, what device is this for? Is it an image from the dashboard or one built by yourself?
config.txt elemens are appended by https://github.com/balena-os/balena-raspberrypi/blob/master/layers/meta-balena-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend on top of the upstream recipe https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-bsp/bootfiles/rpi-config_git.bb

I'm talking about vanilla images from the balena-cloud dashboard.  Raspberry Pi4 64bit

I see, thanks for clarifying. In v2.88.5 vc4-kms-v3d was not getting loaded, because in upstream the overlay-map was modified to load vc4-kms-v3d-pi4.dtbo instead of vc4-kms-v3d.dtbo and the v2.88.5 image did not include this newer overlay. So the overlay was not getting loaded at all and analog audio worked. The v2.91.1 image uses the upstream raspberrypi linux version 5.10.83 and includes both vc4-kms-v3d-pi4.dtbo and vc4-fkms-v3d-pi4.
I suggest trying to reproduce the issue with the latest RaspberryPi OS. If it isn't reproducible and the kernel is newer than 5.10.83 we update to that version, otherwise it needs to be reported in upstream.


Can't import from database

The docs state:

Besides adding static import paths, it’s also possible to add custom import functions. This allows you to load paths from a database, or HTTP, or using files that SCSS would otherwise not process (such as vanilla CSS imports).

The addImportPath() method permits specifying a custom function, however that function still has to return a path on the file system.
Compiler.php L3181 always loads from a file:
$code   = file_get_contents($path);

How can I load an import path with code from a database?

At the moment, indirectly. Your callback would fetch the scss code from your database, save it locally to a temp file, and return the oath of the temp file

Typo. "path" (not oath)


Changed supported deployment target and added support for negative scroll.

anyone?

I'm really really sorry for not answering this, @942v. I completely missed it.


error found in the code

Is there an existing issue outlining your problem?

[X] I am using the latest version of the provided userstyle.
[X] I have searched the existing issues and they do not solve my problem.

What userstyles are you seeing the problem on?
lbl:mastodon
Describe your problem.
when opening the theme in stylus, it points out an error at line 29 and the theme doesn't load on mastodon
Attach screenshots.

What browser(s) are you seeing the problem on?
G-Chrome 127.0.6533.100 (Official Build) (64-bit) (cohort: Stable)
Any additional comments?
i don't know to fix tbh

The latest version of the theme loads fine for me. The "unknown word" issue does not block the loading of the userstyle and isn't fixable on our end unless we want to rename the theme...


Rename UseRpcServices to UseRpcRouting

This change will make it clearer which routing option is being used.

this has been implemented


Maximize Split Pane

At iTerm2 you have a feature to maximize split panels, with cmd+shift+return.
I would love to have it here too, i thought about doing a plugin for that but wanted to check here first as i think it makes sense to be a core feature.

I kept looking and i found https://hyper.is/plugins/hyper-pane which does that in case someone is also looking for this. :+1:

We try to keep as much features out of the core as possible, moving functionallity to plugins. As you found a plugin that helps you with this, I'm closing this here. Thanks for reporting and posting the plugin for others to find! ❤


WSL Instance shuts down after not using it for a while

Environment
Windows build number: 20185
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 1

Steps to reproduce
Start a WSL instance
Close the terminal and do something else for a while
a ) Try to access a WSL file from the explorer sidebar or //wsl$/Ubuntu
OR
b) Start a new WSL instance in Windows terminal
Expected behavior
a) Since WSL was booted up once and I hadn't typed wsl --shutdown, the instance should be online and I should be able to access my files
OR
b) WSL should start a terminal instance without starting the distro again because it was started once and not shut down.
Actual behavior
a) Trying to access //wsl/Ubuntu (Linux section in Explorer sidebar) or //wsl$/Ubuntu tells me file or resource was not found
OR
b) WSL starts the distro again, starting at /mnt/c/Users/Blacklight instead of ~ respecting startingDirectory attribute I set in terminal (I have made an issue about it at microsoft/terminal#7272).
This is the exact opposite of microsoft/WSL2-Linux-Kernel/#111, which suggests to add this feature as an option in WSL but this is what I have as default in my system and I don't have an option to turn it off :(

IIRC this is intended behavior as to prevent unnecessary usage for portable devices.

Oh, that makes sense because my device is a laptop. In that case is there any way to turn it off?

//wsl$/Ubuntu tells me file or resource was not found

WSL does shut itself down by-design to conserve resources, but that doesn't (ie: shouldn't) prevent WSL from being fired back up on-demand when you access \\wsl$\Ubuntu. Your described behavior described does not reproduce here. There is some variable causing your "file or resource was not found" error, but no off-cuff guesses what.
Please collect networking logs and post to feeback hub.

Here's the link of the Feedback Hub report: https://aka.ms/AA9at0w
While I was collecting the reports, I noticed that the delay for the //wsl$/Ubuntu path being inactive after closing WSL varies each time. In this instance it wasn't working immediately after I closed the tab, but I tried it once afterwards and it was active for a while more.


example for EEG has spaces in the json field for hardware filters

@sappelhoff
There are spaces in the EEG example for the hardware filters. This should be CamelCase. Can I change this?

What exactly do you want to change?
https://github.com/bids-standard/bids-starter-kit/blob/2711f87260851a2d2da2b1829cb847883b220d5e/templates/sub-01/ses-01/eeg/sub-01_ses-01_task-FilterExample_eeg.json#L1-L9
generally, it should be fine - but I don't know whether it is necessary. As far as I know, only the top level keys must be camel case. Or should all keys always be camelCase?

I would prefer something like this, for consistency, and add a note that frequencies SHOULD be expressed in Hz, so no need to specify that in the json:
{
"HardwareFilters": {
"HighpassRCfilter": {
"HalfAmplitudeCutoff": 0.0159,
"Rolloff": "6dB/Octave"
}
},
"SoftwareFilters": "n/a"
}

Okay, that would be fine by me. What is your general view on this way to define filters? So far, I didn't get a lot of feedback

I think it is helpful, but potentially a little much to be required (as per comment on the BIDS-iEEG extension) and we had another question from @voytek about how to specify DC removal

another question from @voytek about how to specify DC removal

mh we could either have a new key for it e.g.,
{
    DCOffset: "The DC Offset was removed through ... "
}

Or we could somehow integrate this information with HardwareFilters, but that'd better be discussed in the specification.

I think it is helpful, but potentially a little much to be required

mmmh okay let's wait for good alternatives in the spec then. I'll adjust this example once we converge on a solution.
In the meantime, feel free to adjust the camelCase if you like.

Ok, I changed this to CamesCase and will close this issue. I will add comments on DC Offset and HardwareFilters in the spec.


OCPBUGS-1417: AWS: build temp credentials file from AWS key and secret

If file credentials cannot be found then build a temp file from aws_access_key_id and aws_secret_access_key.
Other operators build AWS credentials from aws_access_key_id and aws_secret_access_key without the need to have an explicit credentials file. This is not a problem for environments where the cloud-credential-operator injects the correct data. However, in manual credentials mode, users seem to expect to only provide the key_id and access_key.
Reported-at: https://issues.redhat.com/browse/OCPBUGS-1417
Signed-off-by: Andreas Karis<EMAIL_ADDRESS>

/retest-required

/lgtm

/retest


Josh fix doc typo

Might be confusing for a user who scans the docs and tries setting the directive to On when the module expects on.

:+1:

In production, we definitely use On, not 'on' - what makes you say this is what the module expects? (i'm pretty sure it's case insensitive actually) Maybe there's another bug somewhere?
jib@beacon-a101:/etc/apache2$ grep -nri QS2Cookie .
./sites-enabled/entrypoints/event.gif.entrypoint:122:           QS2Cookie On

K, I'll update the other way. There's both On and on in the documentation.

Should it be On|Off in the docs?

This just makes the DOCUMENTATION file consistent on using On v. on. I think you're right about it being case insensitive, just figured we should stick to one.

good catch, thanks.


Simplify ITF collection representation

If #2258 gets implemented, we can drop the single #-prefixed object wrapper, as types will then be able to guide reconstruction from a json array.
E.g. instead of
"mapVariable": {
  "#map": [ [k1, v1], ..., [kn, vn] ]
}

we could just have
"mapVariable": [ [k1, v1], ..., [kn, vn] ]

because the "vars" field would already contain { ... "mapVariable": "a -> b" }.

Having an option to switch between these formats would be nice.
Is it possible to encode types in JSON rather than a simple string?

For example, {"Fun": {"inputs": ["a"], "output": "b"}} instead of "a -> b".

Having an option to switch between these formats would be nice.

I don't think so, especially since the "ITF-with-types" variant contains strictly more information than the normal one. If you don't need types, just ignore them.

Is it possible to encode types in JSON rather than a simple string?

Yes, but {"inputs": ["a"], "output": "b"} is not a representation of any valid TlaType1 type. Having e.g.
"type": {
  "kind": "FunT1"
  "args": {
    "from": "StrT1"
    "to": "IntT1"
  }
}

is the alternative, because both that and the string version can be parsed into a TT1 type from within Apalache. Any homebrew json representation of a type is useless to us.

I'm not opposed per se, but I still don't see the value in having this intermediate wrapper.

It is mainly for back compatibility.

is not a representation of any valid TlaType1 type

Mine was an example. I am okay with your example.

I agree with you. Human readability will be improved for sure. But this adds extra overhead at machine parsing.
Nonetheless, adding type info (#2258) would be helpful for Atomkraft's reactor generation !

Human readability will be improved for sure

To be clear, I think human readability with NOT improve: I think it will get worse :) This is because, looking a state {"v" : [1, 2], "x" : [2,1]} humans will have no way of knowing whether or not "v" should equal "x", because they won't know whether these are sets or sequences without consulting the types for the variables stored in a different key. This problem could occur any number of times in more complex cases.
I agree #2258 should go forward regardless! :)

Alright, since the consensus seems to be "keep #-tags" I'll close this issue, and just implement #2258.


fix(xacro): replace load_yaml with xacro.load_yaml

Description
From humble, load_yaml should be replaced with xacro.load_yaml to suppress warnings.
Related links

https://github.com/autowarefoundation/autoware/issues/3322
https://github.com/autowarefoundation/autoware.universe/issues/2977
https://github.com/autowarefoundation/autoware_individual_params/pull/42

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[X] The PR follows the pull request guidelines.
[X] The PR has been properly tested.
[X] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[X] There are no open discussions or they are tracked via tickets.
[X] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@shmpwk can you merge this PR ? Or do I need to fix the ci ?

One CI is failing but we ignore it because of EOF galactic.
build-and-test-differential / build-and-test-differential (galactic) (pull_request) Failing
Run package_paths=$(colcon list -p --packages-above-and-dependencies awsim_sensor_kit_description --base-paths . dependency_ws)
Warning: running 'rosdep update' as root is not recommended.
reading in sources list data from /etc/ros/rosdep/sources.list.d
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml
Skip end-of-life distro "ardent"
Skip end-of-life distro "bouncy"
Skip end-of-life distro "crystal"
Skip end-of-life distro "dashing"
Skip end-of-life distro "eloquent"
Add distro "foxy"
Skip end-of-life distro "galactic"
Skip end-of-life distro "groovy"
Add distro "humble"
Skip end-of-life distro "hydro"
Skip end-of-life distro "indigo"
Skip end-of-life distro "jade"
Skip end-of-life distro "kinetic"
Skip end-of-life distro "lunar"
Add distro "melodic"
Add distro "noetic"
Add distro "rolling"
updated cache in /github/home/.ros/rosdep/sources.cache
  You should run 'sudo rosdep fix-permissions' and invoke 'rosdep update' again without sudo.
WARNING: ROS_PYTHON_VERSION is unset. Defaulting to 3
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
awsim_sensor_kit_description: Cannot locate rosdep definition for [ament_cmake_auto]
velodyne_description: Cannot locate rosdep definition for [ament_cmake]
Error: Process completed with exit code 1.