GcloudFile DelegationError

Thanks for a great gem.
When remote files are not present, some GcloudFile methods that are delegated to the file fail...
Module::DelegationError: CarrierWave::Storage::GcloudFile#size delegated to file.size, but file is nil:

Suggest allowing nil in the delegation in gcloud_file.rb line 11
delegate :content_disposition, :content_type, :size, to: :file, allow_nil: true

Would you suggest that we handle the exception in our application rather than allow nil on the delegation?   I am happy to offer a PR if you would accept the allow_nil: true option.

This was merged as part of https://github.com/metaware/carrierwave-google-storage/pull/32 Closing.


Required CuPy version specification in the stable version looks incomplete

Current minor versions of Chainer requires CuPy (if installed) older than the unseen next minor version. For example, the recent release of Chainer v3.2.0 requires CuPy <2.3. I think it should be fixed so that 1) it does not allow too old CuPy, and 2) it allows any newer version of CuPy at the same major version.

How about this?
For stable branch:
  v4.0.0: `>=4.0.0, <5.0.0`
  v4.1.0: `>=4.1.0, <5.0.0`
  ...
For master branch:
  v5.0.0a1: `==5.0.0a1`
  v5.0.0b1: `==5.0.0b1`
  ...

PR raised: #4830
(I found the spec has unexpectedly changed in #4640)

Fixed via #4830


feat: add arrow function support

fixes https://github.com/bluetech/ng-annotate-patched/issues/12
Got most of the features working. Except the IIFE support. Annotated the not supported IIFE lines with NOT IMPLEMENTED FOR ARROW FUNCTIONS. So it's still in the test and validated that the code isn't touched.
The tests are a copy of tests/original.js, but most of the functions converted into arrow functions.

sadly it's not that easy. E.g. angular.module('foo').service(($location) => 1) throws in angular anyway, as angularjs does new on the function, and in es6, new and an arrow function throw a TypeError 😭

Buuuuuut, it enables some annotations. Our project runs fine with this branch.

Thank you! I'll try to review this sometime this week.

added commits that cover the code review

Ok, added to commits that should resolve the two comments of yours.
Thank you for taking the time :)

This is now published as v1.10.0.


Add app section for Anaconda Navigator

Checklist

[X] Used a fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@aganders3 if you're wondering, this is for a new install method I'm working on that I'm starting to prefer over packaging as a standalone application. This lets GPI show up as a package in Anaconda Navigator:


Client UI v0.0.2-alpha

Working on formal client UI

formal UI rework - WIP

Concurrent Actor Framework ref: https://en.wikipedia.org/wiki/Actor_model

@restevens402 are you good to review?


Tag asserts

Description
Tag asserts for client minor release
Reviewer Guidance
The review process is outlined on this wiki page.

https://github.com/microsoft/FluidFramework/pull/17769 should fix the failing tests,


Rename EVP_CIPHER_CTX_get_iv and EVP_CIPHER_CTX_get_iv_state for clarity

To clarify the purpose of these two calls rename them to
EVP_CIPHER_CTX_get_original_iv and EVP_CIPHER_CTX_get_updated_iv.
Also rename the OSSL_CIPHER_PARAM_IV_STATE to OSSL_CIPHER_PARAM_UPDATED_IV
to better align with the function name.
Fixes #13411
Checklist

[x] documentation is added or updated
[x] tests are added or updated

ping?

ping?

This pull request is ready to merge

This pull request is ready to merge

Merged to master.

Merged to master.


Unable to use UUID's as permanent ids

DualStorage uses UUIDs as the temporary id generator.  And detects the id being a temporary id as one that looks like a UUID.  This means that it's impossible to use DualStorage out of the box if the server also uses UUIDs as the permanent id.  I can see this being a very common use case.  What ends up happening is that DualStorage never issues "remote" server commands when inserting/updating/deleting items.   You should change it to use temporary ids that are something more unique instead of using a standard for real ids.
In order to get this to work, I had to override the temporary id generation and check.  I just prepended a "t" to a UUID so it was a different length than a normal UUID.
	Backbone.Model.prototype.hasTempId = function() {
		 return _.isString(this.id) && this.id.length === 37;
	};
	window.Store.prototype.generateId = function() {
		 return "t" + uuid.v4();
	}

Released in v1.4.0.


ParseError: syntax error, unexpected 'EnvironmentInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)

Laravel Version: 8.6
PHP Version:8,7.4
Database Driver & Version:

Description:
we are using php version 7.4 on the production server but on my local server I updated to php 8. Now I am facing this error on production server
ParseError: syntax error, unexpected 'EnvironmentInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)

How I can solve this issue?

Use the same PHP version on both servers. Otherwise you risk pulling in package versions that are compatible with one version but not the other.
Also, are you sure your production server is actually running 7.4? Looks like whatever PHP version you're using doesn't support typed properties - so it can't be 7.4.

Thanks @AegirLeet


Adding Support for Single Template with Multiple Parameter Files

Overview/Summary
This PR adds support for single template with multiple parameter file associations resulting in multiple deployments and closes #831.
The parameter file association allows for many-to-one relationships between parameter file and template and each relationship represents a unique deployment.
scope/
├── template.x1.bicepparam
├── template.x2.bicepparam
├── template.x3.parameters.json
└── template.bicep

This behavior's is controlled with two new settings Core.AllowMultipleTemplateParameterFiles and
Core.MultipleTemplateParameterFileSuffix read more in the wiki or head over to faq.
This feature is disabled by default, to enable this feature set Core.AllowMultipleTemplateParameterFiles to true.
It is optional to change Core.MultipleTemplateParameterFileSuffix, if you want a different filename identifier than x update this setting as well.
This PR fixes/adds/changes/removes

Changes Frequently-Asked-Questions.md
Changes Settings.md
Changes Initialize-AzOpsEnvironment.ps1
Changes Invoke-AzOpsPush.ps1
Changes Core.ps1
Changes ConvertFrom-AzOpsBicepTemplate.ps1
Changes New-AzOpsDeployment.ps1
Changes Set-AzOpsWhatIfOutput.ps1
Changes Strings.psd1
Changes Repository.Tests.ps1
Adds rtmultibase.bicep
Adds rtmultibase.x123.parameters.json
Adds rtmultibase.xabc.bicepparam

Breaking Changes

N/A

Testing Evidence
Automated testing included in PR and in additon to that manual testing has been performed with custom .bicep, .json, .parameters.json and .bicepparam files in conjunjtion with different Azure Policy deployments.
As part of this Pull Request I have

[x] Checked for duplicate Pull Requests
[x] Associated it with relevant issues, for tracking and closure.
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated relevant and associated documentation.

🚀


Removing Optionals from method/constructor parameters

The original discussion is here. It would be better to make those parameters nullable or handle empty parameters in a different way.

I think we can prohibit Optional in fields as well.
There is an "Optional used as field or parameter type" inspection in IntelliJ. We can make it error-level.


cmd/dev-cmd: improve handling of invalid input

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Raises errors in more cases of missing or invalid input for various commands. Includes improvements for wording and help text.

Fantastic work as usual @EricFromCanada!


[Maintenance] Update to Vue 3.4 and introduce defineModel #175

Description

updated dependency
replaced props and emits of modelValue with defineModel
removed two-way binding of dialog instead of replacing it with defineModel

Issues #175

Updates to various dependencies were made in https://github.com/it-at-m/refarch-templates/pull/212. Please check if you can implement your feature with the new dependencies now or if additional bumps are required.

Can only be merged once https://github.com/it-at-m/refarch-templates/issues/290 has been done.


Strange catchError behavior inside of concat

RxJS version: 6.2.0
Code to reproduce:
Try it out on this Stackblitz
import { Observable, of, concat, throwError } from 'rxjs';
import { map, catchError } from 'rxjs/operators';

concat(
  new Observable<string>(o => {
    o.next('first item');
    throw 'lol error';
  }).pipe(
    catchError(err => {
      console.log('caught', err);
      return of('blah');
    })
  ),
  of('this should be played'),
)
.subscribe({
  next(x) { console.log(x); },
  error(err) { console.log(err); },
})

Expected behavior:
Logs
first item
caught
blah
this should be played

Actual behavior:
Logs
first item
lol error

Additional information:
Appears to have to do with the difference in behaviors between when an Observable is lifted, vs when it's not WRT syncErrorThrowable.

Thanks, @hansl for pointing this one out.

Isn't this the same as - or very closely related to - #3561?

This seems related to #3560. See this comment.

I've had a quick look at this. It seems to be related to the syncErrorThrowable property and the internal SafeSubscriber in Subscriber.
In Observable.prototype.subscribe, _trySubscribe is called depends upon  whether there is a source and the value of syncErrorThrowable.
The problem is that those conditions are met only for the subscribe call that's made to the outermost observable - the observable returned from the concat call.
It works like this:

concat is implemented by applying the concatAll operator to an of observable.
concatAll is implemented using mergeMap (with a concurrency of one) and mergeMap has an InnerSubscriber.
InnerSubscriber does not copy its parent's syncErrorThrowable value.
Essentially, that means that when mergeMap subscribes to the observable returned by catchError, to does so by calling _subscribe - and not _trySubscribe.
The means when an error is thrown in the new Observable, the stack unwinds to the _trySubscribe call that's made in the of observable and the catchError implementation doesn't even get a look in.

Note that the of('this should be played') only matters because without it, concat is short-circuited to return the of observable - which sees the catchError operator returned and subscribed to directly - which means catchError gets a SafeSubscriber, etc.
A possible fix - which fixes the repro - could be something like this, but it needs more thought:
export class InnerSubscriber<T, R> extends Subscriber<R> {
  private index = 0;

  constructor(private parent: OuterSubscriber<T, R>, public outerValue: T, public outerIndex: number) {
    super();
    this.syncErrorThrowable = parent.syncErrorThrowable;
  }

  // ...
}

@cartant, at first blush, that seems like the correct solution. The only thing is we'd need to make sure that the InnerSubscriber's syncErrorThrowable property was updated at the appropriate time to be set back to false (meaning it would need to be linked to the parent's syncErrorThrowable property). So perhaps a getter propertly on the InnerSubscriber that was backed by parent.syncErrorThrowable would be better?
(I haven't verified any of this, just thinking this might be the better way to approach this)

Yeah, using a getter would be the way to go.
I'm pretty sure that syncErrorThrowable is only assigned to during or immediately after the subscriber's construction, but "pretty sure" isn't really good enough. Using a getter would be less rash.

Actually, I suppose it should really have getters for each of the syncError-related properties in the parent:
/** @internal */ syncErrorValue: any = null;
/** @internal */ syncErrorThrown: boolean = false;
/** @internal */ syncErrorThrowable: boolean = false;

Need to think about this.

As evident in the previous stream-of-consciousness comment, I've been messing with the above-mentioned fix.
I'm inclined to change my mind about it, as it's really only related to the deprecated sync-error handling and that doesn't even work with the fix applied.
If the inner subscriber's syncErrorThrowable is assigned the value of the parent's property, it still fails, as the error will be rethrown - see #3560. That is, the catchError operator will catch lol error and will emit blah into the stream, but it then re-throws the error which is passed to the outermost error callback and then re-thrown again.
Given that this behaviour is still broken and that #3560 was closed, I think a better fix might be to use a different test for deciding between a _subscribe call and a _trySubscribe call.
Instead of this:
sink.add(this.source || !sink.syncErrorThrowable ? this._subscribe(sink) : this._trySubscribe(sink));

It could be something like this:
const noTry = config.useDeprecatedSynchronousErrorHandling ?
  this.source || !sink.syncErrorThrowable :
  this.source;
sink.add(noTry ? this._subscribe(sink) : this._trySubscribe(sink));

This solves the problem - for non-deprecated usage - in a less complicated way.


Why are we still using char feild to store latlng,

Change charfield
We should be using an extra field store them as two floats or polyfield because to find nearest people through Django queries. other wise it has to be processed in frontend

+1 to this. Can we outline the work involved to do this? As I see it:

add dependencies required for GeoDjango
Add a PointField column to the Request model
write a management command / script to parse existing lat-lngs and where parseable, populate the PointField for existing Requests.
switch to saving to this PointField in the Request form submission
switch out all APIs to return JSON of the geometry from the PointField

If setting up dependencies for geodjango is not something we want to do, even two float fields for lat and lng would suffice as @vmwsree suggests - steps above would be similar.
@vmwsree am sanjayb on the slack - feel free to ping me and we can try and see how to make this happen. There seems to be interest in this from a few people.

Backward compatibility

Backward compatibility

This would be for data consumers, right? So the lat-lngs should be returned the same way as they currently are - this is on the /data end-point .. anywhere else?

For the data which is already present in the database, there will be corrupted or non standard records in var char field. It is to be cleaned up before changing the field type, otherwise data will be lost

any performance impact due to incorrect data type ?

It is to be cleaned up before changing the field type, otherwise data will be lost.

This will need some manual cleaning. Also, I would recommend keeping the existing field so the data can be extracted if needed.

any performance impact due to incorrect data type ?

So the reason to do this as I see it is to enable proximity / bounding box filtering for the map view. This will allow optimizations on the map page that would allow it to avoid having to fetch ALL data like it currently does. So, it's not an immediate impact - and refactoring to use spatial queries on the frontend would also likely be a bunch of work, but changing the data type will make that optimization possible.
The problem is that as the data grows, the request at /data is just going to get too big, regardless of any server-side caching, and the most obvious way to fix would be to do some sort of spatial queries -- like fetch very coarse data if the user is zoomed out and fetched more detailed data only at a higher zoom level or some such.
So, in short - this is only needed if we want to be able to spatial proximity queries, and  otherwise is probably not a priority.

So, in short - this is only needed if we want to be able to spatial proximity queries, and otherwise is probably not a priority.

+1


result page encoding

All my files are in UTF-8, so I added -e utf8 to jsdoc, but no meta tag is generated in the resulted index.html, like this one :
<meta http-equiv="content-type" content="text/html; charset=utf-8">

Am I missing something ?

The -e switch works for JSDoc but is not supported here.


wiki requires me to paste images here

I have to paste images into this thread or I'll need to host them off-site as the wiki editor doesn't seem to be the same as the editor for issues.


De-emphasise and reduce the usage of /_synapse endpoints

This is something I noticed while working on conduit support (#513), where it seems that complement currently requires or emphasizes the usage of /_synapse endpoints.
Specifically, it uses them like so:

Under "Image Requirements" in README.md, it asks for /_synapse/admin/v1/register to be supported for "admin" registrations.

This is then used in RegisterUser where isAdmin is true, which is used by the following tests:

TestCanRegisterAdmin
TestServerNotices

TestRegistration, under some t.Runs

From a puritan perspective, these should not exist within complement, as they test Synapse-specific behaviour that other servers have to then copy uncritically, and without blessing or formalisation from the spec.
From such a perspective, the concept of "admins" is also dubious, as the spec (explicitly) makes no serious note of them, leaving server administration as an implementation detail. (See MSC3593 for some context reading on an attempt to broach/formalise this as well.)

For all of complement's current usage of this endpoint, there is one problem with a suggestion of removing all of them altogether; Server Notices are defined in the spec, and so the absence of a formal mechanism which empowers servers/users to send server notices is unfortunate, but this means complement has no "closed system" way of implementing this.
To make the rejection of a /_synapse specific API explicit, and to develop a better way of testing server notices, I'm suggesting to introduce a /_complement API space, which servers should enable only in their corresponding complement images, and (for now) be only used for sending server notices (exact API forthcoming), not to elevate individual users as a "server admin", as this concept does not properly exist from a matrix specification standpoint.
This API space should only perform individual elevated actions, such as sending a single server notice via a POST API.
Hopefully, this way, we can avoid biasing to a certain implementation, and help make complement more pure or agnostic when testing conformity.

One additional note: When I was converting sytests, I had to reject a bunch of them (some of them found in sytest.ignored.list) because they were testing synapse-specific behaviour such as this, would it be possible to still write them, but place them in a subdirectory of matrix-org/synapse?
This way, it is explicit that these tests are for synapse-specific behaviour, but yet they'd be using the complement framework to test them, which could become an interesting development.


Add basic bash completion script and framework for others

This is a good feature. I only have some goofball nitpicks and I don't think they're worth blocking on.

I can fix those issues up real quick. Also realized I should reject completion if cur starts with a - since this doesn't support flags/options yet.

Fixed up noted issues and a couple other little things.

Oh, I think I just need to add the extras folder to the list of files in the gemspec.

OK, extras/completions should now actually be included in the .gem :)

Can confirm:
mckern@flexor vmfloaty (git:add_bash_completion) $ (set -x; floaty completion)
+ floaty completion
/usr/local/var/rbenv/versions/2.3.4/lib/ruby/gems/2.3.0/gems/vmfloaty-0.7.8/extras/completions/floaty.bash

Ping @briancain; when this is in and a release is cut, I'll update my homebrew tap.

❤  Thanks for all the feedback @mckern !

@scotje woot thanks for the contribution! I'll check this out later this morning and try it :)

Thanks for the contribution @scotje and @mckern for feedback!

Updated with better --help output and an error message.

ping @briancain
Thanks for taking a look and have a nice weekend!

Thanks @scotje ! Your changes are now in 0.7.9 which I just released (cc @mckern). It should be there if you do a gem update, or however you have it installed!

Thanks Brian! ❤


Attach does not work as expected

When rendering the example from Typst documentation, Wypst seems to treat t as tr and b as br. Moreover, nothing else is rendered.
Typst:
attach(
  Pi, t: alpha, b: beta,
  tl: 1, tr: 2+3, bl: 4+5, br: 6,
)

LaTeX:
\underset{\beta}{\overset{\alpha}{\prescript{1}{4+5}{\Pi}^{2+3}_{6}}}

Outputs:

Hello! As of now, wypst only support b and t. I plan to expand on this on the near future; for now the idea was to implement a minimal working setup for Attach that works in most simple cases.

By the way, this on my top list of TODO things, so maybe this week or the next I'll have it fixed.

It seems prescript doesn't work in KaTeX; it's probably not possible to fix this without some arcane syntax.

It seems prescript doesn't work in KaTeX; it's probably not possible to fix this without some arcane syntax.


Token Command

This patch introduces the new rexray token command for creating and decoding authentication tokens. This issue is related to codedellemc/libstorage#501.

Codecov Report

Merging #803 into master will decrease coverage by 0.35%.
The diff coverage is 0.68%.

@@            Coverage Diff            @@
##           master    #803      +/-   ##
=========================================
- Coverage    7.41%   7.06%   -0.36%
=========================================
  Files          21      22       +1
  Lines        2588    2733     +145
=========================================
+ Hits          192     193       +1
- Misses       2379    2522     +143
- Partials       17      18       +1

Impacted Files
Coverage Δ

cli/cli/cli.go
1.08% <ø> (ø)
:arrow_up:

cli/cli/cli_formatter.go
53.21% <0%> (-0.96%)
:arrow_down:

cli/cli/cmds_60_token.go
0.7% <0.7%> (ø)

Continue to review full report at Codecov.

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


bii simple layout incompatible with eclipse

OS: Ubuntu 14.10
Biicode: 3.0
Steps to reproduce:
$ git clone git@github.com:smessmer/cryfs.git
$ cd cryfs
$ bii init -l
$ bii cpp:configure -G "Eclipse CDT4 - Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug

Then try to import the project into eclipse (Version: Luna Service Release 1 (4.4.1) Build id: 20140925-1800) under File -> Import -> Existing Projects Into Workspace
I get the following error:
Error processing changed links in project description file.
  Cannot create a link to '[homedir]/cryfs/bii' because it overlaps the location of the project that contains the linked resource.

Got the same problem for following the getting started guide: http://docs.biicode.com/c++/gettingstarted.html#create-your-first-project
Used bii configure -G "Eclipse CDT4 - Unix Makefiles"
And having this error when importing into eclipse:
Error processing changed links in project description file.
  Cannot create a link to '/home/benny/Development/cpp/learn/unit_test/bii' because it overlaps the location of the project that contains the linked resource.


[WIP] Track RVs in dictionaries and Inference simplification

Simplifies Inference Context and tracks RVs in context with names.
Needs to be rebased and fixed up after this one is merged https://github.com/pymc-devs/pymc4/pull/111

I close this PR due to new design choice


Documentation: Add fish shell completion to MAC completion options.

Proposed changes
I noticed there are more shell completions supported than documented. So I added the other one that works on OSX.
Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 875835f97569992a6173a2bba5091946bbb62f8d
https://deploy-preview-8895--docsdocker.netlify.com


Origins acting weird to missing origin IDs and Replace don't working on the first go

Unsure how this works but it seems to involve missing ID's of origins. The issue is that the player some times when they load in and the ID of the origin is missing, they get to pick the origin like normal, but for some reason, I had a few cases where the powers still remained of the origin that is now missing from the datapack, they picked all the missing layers fine, and have the powers of selected origins, but also have the previous powers of the now "missing" origin. Also at times I had issues where it just wouldn't allow to load in a single-player world and displayed "invalid player data" error message and unsure how I fixed it a couple of times.
It would also seem like I'm unable to get the "replace" field in origin_layers to replace default origins with custom ones, they just act as if "replace" was set to false unless I fiddle around somehow (needs more testing and only shows up to worlds that transition from 1.16.5 to 1.17.1)

Upon more testing, I managed to fix the "invalid player data" by removing all the players powers, and setting all layers back to "origins:empty"


Support Newer Versions of the redis Gem

What This Fixes
Newer versions of the redis gem include bug fixes, and will likely include clustering support in the near future. (4.1.0.beta1 includes this support.) The cb2 gem uses get, set, del, zremrangebyscore, zadd, zcard and flushdb methods. As these methods have not changed in newer versions of the redis gem, the only change necessary is to update the cb2 gemspec.
This change also adds a require for 'securerandom' to rolling_window.rb. Without it, the reference to SecureRandom is undefined, at least on Ruby 2.3.7.
Finally, added a development dependency for minitest to the gemspec. It appears that this library was included in older versions of Ruby, but is now provided as a separate gem.
Testing

Ran unit tests.
We are using this in production (recent version of redis-rb master with cb2).

Seems like maintainer isn't doing anything with this project any more. Can re-open this pull request if someone takes over the project or Pedro becomes active again.


Clean up Dagon API a bit.

Introduce Cache analog to HCache
Rename ExpressionDag to Dag
Move DependantGraph to tests, rename to SimpleDag
A bit of other code clean up
Some extra docs

Codecov Report

Merging #7 into master will decrease coverage by 2.43%.
The diff coverage is 72.22%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   86.38%   83.95%   -2.44%
==========================================
  Files          12       12
  Lines         191      187       -4
  Branches       14       14
==========================================
- Hits          165      157       -8
- Misses         26       30       +4

Impacted Files
Coverage Δ

core/src/main/scala/com/stripe/dagon/Id.scala
100% <ø> (ø)
:arrow_up:

.../src/main/scala/com/stripe/dagon/PartialRule.scala
100% <ø> (ø)
:arrow_up:

core/src/main/scala/com/stripe/dagon/Dag.scala
93.93% <100%> (ø)

core/src/main/scala/com/stripe/dagon/Memoize.scala
100% <100%> (ø)
:arrow_up:

core/src/main/scala/com/stripe/dagon/HCache.scala
57.14% <25%> (-9.53%)
:arrow_down:

core/src/main/scala/com/stripe/dagon/Cache.scala
57.14% <57.14%> (ø)

core/src/main/scala/com/stripe/dagon/HMap.scala
71.42% <60%> (-6.35%)
:arrow_down:

core/src/main/scala/com/stripe/dagon/Rule.scala
75% <71.42%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Remove duplicates strings in auth/src/main/res/values/strings.xml

To make the live of translators easier, I would recommend to remove duplicates from the strings.xml:
Next (2x)
Sign In (5x)
Password (2x)
Ok -> replace with android.R.string.ok
Is it ok to add translations to other languages already?

@peterhav which languages were you considering adding translations for?  This is something we'd have to coordinate across platforms.
However a PR to reduce duplication in string resources would be welcome if you'd like to submit it.

The PR has been created. I would be able to add Dutch translations for the auth lib strings.xml

Thanks for the PR!  As for the dutch translation, let's hold off for now.  I think we have some plans to get all translations done at once for this library (and the iOS version) and I don't want to have you put in the effort now only to see it deleted later.  We do appreciate the offer though :+1:

The PR has been merged so I consider this issue fixed.  Thanks again!


fixed:pagespeed加速导致的二维码无法展示

Codecov Report

Merging #59 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #59      +/-   ##
============================================
+ Coverage     17.43%   17.45%   +0.01%
+ Complexity      800      799       -1
============================================
  Files           173      173
  Lines          2851     2848       -3
============================================
  Hits            497      497
+ Misses         2354     2351       -3

Impacted Files
Coverage Δ
Complexity Δ

app/Http/Controllers/Frontend/IndexController.php
90% <ø> (+20.76%)
2 <0> (-1)
:arrow_down:

Continue to review full report at Codecov.

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


Bump the Mermaid version

Hi,
Thanks for your contribution. I could notice that Mermaid 9.1.2 is being used and it would be nice if this is bumped to the latest version (9.1.6).
Thanks again.

Where do you see that? This is the only reference to Mermaid I can see in Markdig.

Markdig does not use or reference any mermaid library. You might redirect your request to the repository where Markdig is used and you noticed this reference.


Update apptest-countries-and-translations.md

Moving 'November 2022' mark to Available

Learn Build status updates of commit 7092daa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dev-itpro/compliance/apptest-countries-and-translations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Missing images in documentation - "No puml file found!"

The documentation page User guide for 4.x currently misses two images in the section Dealing with a Stream-based Transport. They are currently replaced with a template image saying "No puml file found!".
Here are the two screenshots demonstrating the problem:

please post the images directly in github so we don't have to follow external links

@Scottmitch fixed that, couldn't find any "attach" button at first

@scadgek - Can you try again? I just cleared the cache [1] and it worked for me.
[1] https://help.github.com/articles/why-do-my-images-have-strange-urls/#removing-an-image-from-camos-cache

@scadgek - Also clear your browser cache before you try (or use a "incognito"/"private browsing mode")

Oh, now they appear. I didn't even clear the cache.
I thinks now this issue may be closed.

seems like the missing images issue is happening again?

@ChuntaoLu Not for me - just checked and they're all there.

The issue is happening again.

https://camo.githubusercontent.com/24ed1176ecca468dfb2b8b017bb927a8715a16f2/687474703a2f2f756d6c2e6d766e7365617263682e6f72672f676973742f3832653366626530653264346466323833323262

https://camo.githubusercontent.com/5b595baf5071bf669f81d08b7554064f4142cc69/687474703a2f2f756d6c2e6d766e7365617263682e6f72672f676973742f6233316330626437626266633639666438326436
https://camo.githubusercontent.com/24ed1176ecca468dfb2b8b017bb927a8715a16f2/687474703a2f2f756d6c2e6d766e7365617263682e6f72672f676973742f3832653366626530653264346466323833323262

#7374


Download an exe?

I'm having issues with quick sync causing red glitches in videos. One page mentions using the media sdk as there seems no way to disable quick sync. Is there a simple way to install it?

Hi @EddieOne,
Quick Sync is HW technology that offloads video coding computation to the Intel(R) Processor Graphics. Media SDK is programming API to access Quick Sync.
It looks like you're using some application that uses Quick Sync. Which application do you use?
Best wishes,
Anna

Hi @avbelova,
If I render any 4k footage on adobe cs6 slightly older Intel chips, I get Quick Sync crashes that show in the render as solid color glitches, red or green. Not sure if buying new software is the only option or if new hardware will also fix it?
Thanks, Eddie

@EddieOne ,
Which concrete Intel chip do you use, and which video decoder (AVC, HEVC,..)?
Best wishes,
Anna

It's the i7-4790k and it happens with the h264 codec. I use another application that offers gpu quick sync and I can render down to 1440p. It's then possible to render those via Intel inside Adobe.

@EddieOne , on the QuickSync/Media SDK side we don't have limitations with 4K AVC decode. We advice you to address the issue to Adobe.
Best wishes,
Anna


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 4b0f287, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 9441 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in c6a431a after 23 minutes.


operator uma-operator (2023.9.5)

/test skip check_pruned_graph

/ok-to-test

/ok-to-test

@mn660971: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

/ok-to-test

/ok-to-test

/ok-to-test


zynaddsubfx: use zyn-fusion as default gui module

Added guiModule option that accepts "fltk", "ntk", "zest", or "off"

Split FLTK dependencies from NTK dependencies

Added support for building the FLTK gui

Added support for building the Zyn-Fusion (zest) gui

Added new derivation for the Zest UI framework (local to zynaddsubfx)
It's not yet designed to be used outside of zynaddsubfx, but it
may be in the future

Added flags for all optional features

Added & disabled dssiSupport by default

Disabled lashSupport by default
Slows down startup looking for LASH server if not running

Added & enabled portaudioSupport by default
Cross platform audio library that uses ALSA/JACK on Linux.
Supports multiple audio streams without needing JACK.

Enabled tests

Removes nico202 as maintainer, as requested in code review

Motivation for this change
Closes #90698
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
222.5M -> 223.1M
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Formatted with nixpkgs-fmt

I get
[INFO:Zyn] setup_pugl()
libGL error: MESA-LOADER: failed to open radeonsi (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: radeonsi
Jack info message: Jack: JackClient::ClientNotify ref = 6 name = zynaddsubfx notify = 18
Jack info message: Jack: JackClient::ClientNotify ref = 6 name = zynaddsubfx notify = 18
libGL error: MESA-LOADER: failed to open radeonsi (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  55
  Current serial number in output stream:  54

I have  services.xserver.videoDrivers = [ "amdgpu" ];
Not sure if this is related to packaging.

I was having issues running this with the zest ui under Ardour. The issue is that when using the zest ui, the ZynAddSubFx plugin does a dlopen to libzest.so. The standalone binary works around this with some LD_LIBRARY_PATH trickery, but Ardour falls flat trying to load the plugin, since the dlopen fails.
I was able to resolve the issue by forcing libzest.so into the rpath of the plugin shared objects with something similar to the snippet below (VST untested, although I'd assume it needs the same fix), although I'm not sure if this is the best way to resolve this issue:
postFixup = ''
  rp=$(patchelf --print-rpath $out/lib/lv2/ZynAddSubFX.lv2/ZynAddSubFX_ui.so)
  patchelf --set-rpath ${mruby-zest}:$rp $out/lib/lv2/ZynAddSubFX.lv2/ZynAddSubFX_ui.so

  rp=$(patchelf --print-rpath $out/lib/vst/ZynAddSubFX.so)
  patchelf --set-rpath ${mruby-zest}:$rp $out/lib/vst/ZynAddSubFX.so
'';

Using this PR, when loading ZynAddSubFx as a plugin in a different application and trying to open the GUI, it will complain that libzest.so cannot be found and shows a blank screen. I've tried patching the Zyn*.so object files in lib/vst using patchelf, but they're actually all statically linked, so I'm not quite sure where the issue is.
When I add the directory of libzest.so to LD_LIBRARY_PATH the plugin and UI works, so it seems these statically linked objects are still doing some dynamic loading.

@Sorixelle & @Beskhue Hmm, that's strange. It dynamically links to libzest here: https://github.com/zynaddsubfx/zynaddsubfx/blob/3.0.5/src/Plugin/ZynAddSubFX/ZynAddSubFX-UI-Zest.cpp#L68-L72.
But when ZynFusionDir is specified in the build, it should automatically set up LD_LIBRARY_PATH before starting the UI: https://github.com/zynaddsubfx/zynaddsubfx/blob/3.0.5/src/main.cpp#L705-L740.
I will try it out in Ardour to try to reproduce it.

Ardour doesn't use the standalone binary, it just goes straight to the LV2 plugin. The LD_LIBRARY_PATH setup is only in the standalone binary.

@Sorixelle Oh, right thanks I misread your comment. I think patching the rpath would be the best approach then.

@Sorixelle I get:
thomas@argo /nix/store/0m3nr7s3yac9zm9nm4darm7ifwg72217-zynaddsubfx-3.0.5/lib/vst
 % file *.so
ZynAddSubFX.so:      ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynAlienWah.so:      ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynChorus.so:        ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynDistortion.so:    ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynDynamicFilter.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynEcho.so:          ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynPhaser.so:        ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped
ZynReverb.so:        ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), statically linked, not stripped

@Beskhue I think that file is printing that because there are no load-time dynamically linked dependencies, but libzest.so is linked at runtime.

@MetaDark You're right. @Sorixelle's patch works, and the GUI loads without setting LD_LIBRARY_PATH. The error from patchelf I got previously was due to mistaken use of the --set-interpreter option.

Ok I'll submit the patch. I was trying to remove ZynFusionDir by wrapping $out/bin/zynaddsubfx with zest in the PATH, but it doesn't seem to properly find the zest executable, so I'll just leave it in.

Thank you @Sorixelle & @Beskhue. Now it should properly load libzest.so when using the lv2 & vst plugins.

Builds and works wonderfully, both the standalone and the lv2.

I've been using this to make some songs in Ardour, and I just love it.
It would be wonderful to have this in nixpkgs.
Thanks a lot @MetaDark!
Could the people in this thread have another look and see if it works for them now?
@Sohalt @Sorixelle @Beskhue
Maybe the maintainers could also have a look?
@cillianderoiste @nico202

Nice! I always wanted to try zyn-fusion, but unfortunately I'm not using nix on a desktop anymore, so I cannot test this patch.  Could you remove me from the maintainers?
Thanks

@nico202 Just submitted an update that removes you as a maintainer

@magnetophon It's working great for me.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/386

@magnetophon Sorry for the late reply. It works perfectly for me as well.

It's working well for me as well. It'd be nice to get this merged. @SuperSandro2000 can you have a look?

It's working well for me as well. It'd be nice to get this merged. @SuperSandro2000 can you have a look?

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 91674 run on x86_64-linux 1

3 packages built:

zyn-fusion (zynaddsubfx)
zynaddsubfx-fltk
zynaddsubfx-ntk

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 91674 run on x86_64-linux 1

3 packages built:

zyn-fusion (zynaddsubfx)
zynaddsubfx-fltk
zynaddsubfx-ntk

@SuperSandro2000 Thanks for reviewing this! I didn't resolve all of you're comments, but does this look ok now?

@SuperSandro2000 Thanks for reviewing this! I didn't resolve all of you're comments, but does this look ok now?

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 91674 run on x86_64-linux 1

3 packages built:

zyn-fusion (zynaddsubfx)
zynaddsubfx-fltk
zynaddsubfx-ntk

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 91674 run on x86_64-linux 1

3 packages built:

zyn-fusion (zynaddsubfx)
zynaddsubfx-fltk
zynaddsubfx-ntk

Thank you @SuperSandro2000! I really appreciate the review :heart:

Thank you @SuperSandro2000! I really appreciate the review :heart:


[WIP] test-e2e/cip: Remove checkEqual() function

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
(testing this for https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/285)
test-e2e/cip: Remove checkEqual() function
Signed-off-by: Stephen Augustus<EMAIL_ADDRESS>Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/lgtm


how workerman is faster than swoole itself ?

Hello, I saw benchmark on https://www.techempower.com/benchmarks/#section=data-r19&hw=ph&test=plaintext
workerman: 25%
swoole: 15%
I dont believe it so I wrote a script (below) to test it myself:
<?php

use Workerman\Worker;

require_once __DIR__ . '/vendor/autoload.php';

// #### http worker ####
$http_worker = new Worker('http://<IP_ADDRESS>:2345');

// 4 processes
$http_worker->count = 4;

// Emitted when data received
$http_worker->onMessage = function ($connection, $request) {
    //$request->get();
    //$request->post();
    //$request->header();
    //$request->cookie();
    //$request->session();
    //$request->uri();
    //$request->path();
    //$request->method();

    // Send data to client
    $connection->send("Hello World");
};

// Run all workers
Worker::runAll();

<?php
use Swoole\Http\Server;
use Swoole\Http\Request;
use Swoole\Http\Response;

$server = new Swoole\HTTP\Server("<IP_ADDRESS>", 9501);
$server->set(['worker_num' => 4]);

$server->on("start", function (Server $server) {
    echo "Swoole http server is started at http://<IP_ADDRESS>:9501\n";
});

$server->on("request", function (Request $request, Response $response) {
    $response->end("Hello World\n");
});

$server->start();

Result
Running 5s test @ http://<IP_ADDRESS>:9501
  4 threads and 4 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    83.34us  274.08us  11.56ms   99.18%
    Req/Sec    14.84k     4.04k   18.97k    58.33%
  301141 requests in 5.10s, 47.39MB read
Requests/sec:  59050.57
Transfer/sec:      9.29MB

Running 5s test @ http://<IP_ADDRESS>:2345
  4 threads and 4 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    80.86us  378.40us   9.77ms   97.93%
    Req/Sec    25.65k     2.17k   28.28k    71.50%
  510596 requests in 5.01s, 64.28MB read
Requests/sec: 102014.51
Transfer/sec:     12.84MB

It is true - but how :smiley: ?
You are using swoole under the hood - so how is this possible ?

You are using swoole under the hood - so how is this possible ?

Although workerman supports swoole as the underlying driver, but the above benchmark workerman did not use swoole.
I don't know why workerman performs better than swoole. It may be that swoole's internal implementation is more complex, which affects its performance.

You are testing Swoole only for http requests/ response, without using co-routines to multiplex other I/O like Database, Redis, System Process/ Commands.
Plus, after frameworks achieves performance of a certain level, we seek a better trade-off between Performance and Featrues offered by a platform. Swoole certainily has all modern features required to program IoT, Real-time Network Communication, In-memory / Memory-first Architecture, Games and other Micro-services based on Communicating Sequential Process (CSP) model of Concurrent Programming.


step-ca: 0.15.15 -> 0.16.0

Motivation for this change
Reasoning for backporting: v0.* and no specified support for older versions. Also never saw updates to older versions.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 131821 run on x86_64-linux 1

1 package failed to build:

nixos-install-tools

1 package built:

step-ca

@dguibert Sorry but I realized that this package is not reproducible and tried to fix it. This should really not break it as the buildid is just a value in an elf section but feel free to quickly check again.

Result of nixpkgs-review pr 131821 at 5f645dd5 run on aarch64-linux 1

2 packages built successfully:

nixos-install-tools
step-ca

I don't think that's sufficient justification for backporting. Firstly many projects don't hit 1.0 for many many years, and by this logic anyone using a 0.x version of something should expect it to be switched out from under their feet at any moment (I guarantee that you depend on the stability of a 0.x package somewhere in your stack). Furthermore a package not having stated support for a version doesn't mean we can't/shouldn't distribute it. If there is a grave bug or security issue, then we can worry about that when the time comes on a case-by-case basis. FWIW most projects don't have any stated support for any version (possibly not even the latest), which would mean we should be just continually bumping 90% of packages. And then stable would be the same thing as unstable.


Implement Navbar in the Dashboard

Implement Navbar in the Dashboard
Description
A left-side navigation bar (navbar) needs to be created for the dashboard. This navbar should facilitate easy navigation between different sections of the dashboard.
Requirements

Responsive Design: The navbar must adapt to various screen sizes.
Included:

Dashboard /dashboard
Your Money /dashboard/money
Payment links /dashboard/links
Sales /dashboard/sales
Settings /dashboard/settings

Interactivity: It should include visual effects to indicate the active link.
Accessibility: Ensure that the navbar complies with accessibility guidelines.

Technical Considerations

Use TailwindCSS for styling and layout.
Implement components using shadcn/ui and Radix UI to ensure a good user experience.
Use Lucide/icons

Tasks

Design structure and necessary components.
Leave a empty section on the right for the other components
Style the navbar using TailwindCSS classes.
Implement logic to highlight the active element using Class Variance Authority.

Figma Reference
You can use the Figma design linked here as a reference, but feel free to use the previously mentioned components as a guide.

Hello I'm a frontend developer in web3 I have contributed in previous OD Hacks  i have made over 70+ contribution in past OD Hacks I intend in solving this issue with the following approach :

Can I take care of this issue?

Is this issue still available?

I’d like toHello I'm a frontend developer in web3 I have contributed in previous OD Hacks  i have made over 70+ contribution in past OD Hacks I intend in solving this issue with the following approach :
Step 1: Structuring the Navbar
First, I'll create the layout for the navbar. I'll make sure it sits on the left-hand side of the dashboard and leaves an empty section to the right for other components, as specified. Using a flexbox layout will help me achieve this cleanly. I'll set up placeholders for the links (Dashboard, Your Money, Payment Links, Sales, and Settings) and use a responsive design approach from the start.
Step 2: Styling with TailwindCSS
Since TailwindCSS is my tool of choice for styling, I'll ensure the navbar has a modern and sleek look:
I'll use Tailwind utility classes for spacing, colors, and responsive adjustments.
For the active link, I'll use hover effects and dynamic classes to ensure it's visually distinct.
I'll also ensure it's responsive so it works seamlessly across devices, using Tailwind's sm, md, and lg breakpoints.
Step 3: Adding Interactivity
For interactivity, I'll use Class Variance Authority (CVA) to manage the styles for active and inactive links dynamically. I’ll also set up logic to detect the current route so that the active link is highlighted. I'll rely on useLocation (React Router) or usePathname (Next.js) to handle this smoothly.
Icons will make the navbar more intuitive, so I'll integrate Lucide icons to match each link’s purpose. For example:
HomeIcon for the dashboard.
DollarSignIcon for "Your Money."
LinkIcon for "Payment Links."
Step 4: Ensuring Accessibility
Accessibility is critical, so I’ll:
Make sure all links are keyboard accessible using tabindex and provide meaningful aria-labels.
Style focus states using Tailwind to meet WCAG guidelines.
Test with screen readers to confirm the navbar works well for all users.
Step 5: Polishing with Components
I’ll use shadcn/ui and Radix UI to create reusable components for the navbar links. These libraries will help me deliver a polished user experience while keeping the code modular and clean.
work on this.

Hello @MPSxDev, I'm Wheval a  frontend developer with multiple experiences working with React, Tailwindcss, Nextjs and Shadcn. I am also a good contributor on Onlydust. Can i work on this?
Here's how I would do this,
I would go through the current codebase to understand how it's structured.
I would then implement a side navbar component using Shadcn and the linked figma file, the sidebar would contain all the links you listed above. I would ensure the sidebar is responsive on all screen sizes.
I would also implement interactivity so a user can know when a link is active or clicked using Class Variaince authority.
Please assign, Thank you.
ETA is 1 day.

My Background and How It Can Be Leveraged
Hello, my name is Derian Rodríguez. I am a passionate software engineer with over one year of experience. I am part of the Dojo Coding Community and have been actively contributing to open-source projects through OnlyDust. I have experience in frontend development using JavaScript/TypeScript, React, and Next.js. I would love to continue contributing and supporting the development of this project.
How I Plan on Tackling This Issue
I will create the navbar using shadcn/ui and Radix UI, making sure to include the specified sections (Dashboard, Your Money, Payment Links, Sales, Settings), following the Figma design.
I will style the navbar with TailwindCSS to make it responsive and highlight the active link using Class Variance Authority.
I will add Lucide/icons.
I will test the functionality to ensure everything works correctly.

I would like to work on this issue

Can I take care of this issue?
i'm a frontend dev and a blockchain dev please kindly assign :)

Hi @MPSxDev, I'm a software developer with 2+ years of experience and I have worked with backend technologies such as Cairo, Java, C# and frontend with React, NextJS, JS/TS. Also, I'm a member of the Dojo Coding community here in CR and I have made contributions in Cairo VM Go, Cairo VM TS, Cairo Lints etc. Likewise, I’m a Cairo developer working in ByteBuildersLabs creating on-chain games using the Dojo framework.
This is my approach:

I will review the contributor guide and any existing components to ensure the navbar follows the project’s structure and styling conventions.
I’m going to create a reusable Navbar component, ensuring it matches the design provided.
I’ll make sure the component is responsive and can be easily integrated into all routes.
Finally, I will test the component across different routes to verify that it works as intended visually.

ET: 3 days.

I'd be happy to do this.

Could I try solving this?

Hello @MPSxDev My name is Kevin Latino, and I'm a Frontend Developer and active open-source contributor. I'm a member of Dojo Coding ⛩, a thriving Web3 community in Costa Rica. I have experience with React, Next.js, and TypeScript, also I have experience in data fetching and API integrations and I recently won the LATAM Hackathon hosted by Base. I've also contributed to projects in ecosystems like Starknet and Stellar.
I'll implement a responsive left-side navbar for the dashboard using TailwindCSS. The navbar will include links for "Dashboard," "Your Money," "Payment Links," "Sales," and "Settings," each linking to their respective routes. It will feature interactive visual effects to highlight the active link using Class Variance Authority and ensure compliance with accessibility guidelines. I'll integrate Lucide icons for each section and use shadcn/ui and Radix UI for consistent components. The right side will remain empty for other components, and I'll refer to the Figma design for alignment with the overall UI.
Here is an example of a Frontend Project that I have made:
https://buildmyevent.xyz/

May I handle this issue? I am an experienced frontend developer.

This is my first time contributing to this ecosystem and I would love to be given the opportunity. I am a blockchain developer, and my experience includes html, css, react, javaScript, typescript, solidity and cairo.
To solve this issue I’ll take the following steps:
1. I’ll create a Navbar component that includes navigation links for sections like /dashboard, /dashboard/money, /dashboard/links, /dashboard/sales, and /dashboard/settings. Then I’ll use React Router () to handle routing between different dashboard sections.
2. Then I’ll use TailwindCSS for styling, with responsive classes (e.g., lg:flex, lg:hidden) to adapt the navbar for both desktop and mobile views.
3. I’ll highlight the active link by comparing the current route (window.location.pathname) with the target link. Use CVA (Class Variance Authority) pattern (or classnames) to dynamically apply styles based on the active state
4. I’ll use TailwindCSS utility classes for layout (flex, items-center, space-x-3) and conditional styling (e.g., bg-gray-700 for active links). I’ll also add hover effect.
5. I’ll ensure semantic HTML (, , ) and include aria-current="page" on active links for better screen reader support.
Please assign me I’m ready to work.

I'd love to handle this task

I am a front-end developer specializing in responsive web design,
device-compatible email templates, 3D web integration,
and technical writing on programming topics. I also contribute
to open-source documentation and help build documentation sites.
i will create a responsive sidebar that have a toggle and it is responsive for all device and make sure i leave a blank sidebar on the right for other components using the design as a references .
glad to work on this
Thanks

Hi! I'm Alvaro Lazarus, a developer from Dojo Coding ⛩ with experience in both front-end and back-end development, and I would love to tackle this issue. With my proficiency in TypeScript, React, NextJS and experience working on the front-end aspects of my last few hackathons, I'm confident that I can contribute to this project efficiently.
My workflow:

Create a responsive left-side navbar with the specified dashboard links
Use TailwindCSS, shadcn/ui, Radix UI, and Lucide/icons for styling and
components
Implement visual effects to highlight the active link using Class Variance Authority
Ensure accessibility compliance and leave an empty right section for other components

ETA: 48 hrs

Hi, i am Chiboka Emmanuel  a full-stack web developer who enjoys creating solutions and applications that look great and work smoothly. I would really love to be assigned this issue and work on this project.

I'd be happy to do this.
Hello, I'm Deon a  Full-Stack developer with high expertise in making crisp & responsive UI designs
How i hope to handle this task:

Structuring a responsive left-side navigation bar with links to all sections.
Adding interactivity using Class Variance Authority for active state highlights.
Styling with TailwindCSS and enhancing usability with shadcn/ui, Radix UI, and Lucide icons.
Leaving a placeholder section on the right for additional components.

ETA: 48 hours.

I’d like to work on this,
and make sure it meets the requirements

I'm Pablo Madrigal.
I'm a Fullstack Developer and also part of Dojo Coding 🔥
Problem
Implement a Navbar in the Dashboard
Solution
Create a reusable Navbar component for navigation through the application
I would create a responsive component that could adapt to the different screen resolutions
The navbar is going to be able to adapt to different needs in the future
Also, I would recommend modifying the current layout component to implement the navigation and changes between logged users and public view, this could be implemented at the same time
Estimated time
I'm going to have everything ready in less than 48 hours from the bug assignation

hey sir I'd like to handle this task.
i'm a frontend developer with experience
i would really love to contribute to your project
kindly assign :)

May I be assigned to this?

Mind if I take this issue?
i'm new and would love to work on this
please assign me


support for Odroid C1

Hello has odroid c1 been supported.  I thought it could be quite easier.
It's like the hypriotos guys have added it to their supported platforms.
Meanwhile thumbs up luxas,  and when are we seeing the release with the new dashboard and heapster.

I'm 2nding the anticipation of new dashboard and heapster

Well even though I haven't promised support for heapster I did cross-compile it yesterday. So that's fortunate.
Feel free to install HypriotOS on your Odroid C1 and install the .deb package on it. @zimme is also working on Arch support: #46

So just to clarify: I have both heapster and dashboard working on my Pi, but it will take some time before I release something, 'cause I'm preparing PRs to the main projects first

is there a way to indicate which docker images are ARM?  methinks this should maybe something that should be incorporated into docker itself.  i.e.  docker pull debian should detect that you are on ARM and pull the appropriate images.  I know this is 'pie in the sky' kind of stuff, but it seems that maybe with the 'cavium' stuff coming mainstream soon this should be possible.

I was thinking it would be better to release the version for some guys to be testing and reporting before it meets k8 mainstream.

Here's an alpha version of dashboard:
mkdir -p /etc/kubernetes/source/addons/dashboard
curl -sSL https://raw.githubusercontent.com/luxas/kubernetes-on-arm/dev/addons/dashboard/dashboard-rc.yaml > /etc/kubernetes/source/addons/dashboard/dashboard-rc.yaml
curl -sSL https://raw.githubusercontent.com/luxas/kubernetes-on-arm/dev/addons/dashboard/dashboard-svc.yaml > /etc/kubernetes/source/addons/dashboard/dashboard-svc.yaml
kube-config enable-addon dashboard


chore: remove maintainer

Description

to remove a maintainer from package.xml
Tests performed

Not applicable.
Effects on system behavior

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

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

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

[ ] The PR follows the pull request guidelines.

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

[ ] There are no open discussions or they are tracked via tickets.

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

:cry:

:sob:

:sob:

🥺


Account for fields mapped by rules when checking for missed fields

Fixup for #4 and https://github.com/ros2/ros1_bridge/pull/382 applied on top of mojin-devel
The code after the early return mentioned in the previous commit assumed all fields would match by name, which was of course true. But not anymore, so the missing check now only fails when the missing fields are also not already accounted for via a mapping
To test:
Put
  - topic: /test_id
    type: unique_identifier_msgs/msg/UUID
    queue_size: 1
  - topic: /gazebo_stuff
    type: gazebo_msgs/msg/ODEJointProperties
    queue_size: 1

in eg. amr_config/robots/common/ros1_ros2_bridge.yaml
and start source_amr_ros_bridge && ROBOT=mrl-2 start_amr_ros_bridge
Then run
source_amr_ros2 && ros2 topic pub /test_id unique_identifier_msgs/msg/UUID "uuid: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 2, 2, 2, 2]"

source_amr_ros1 && rostopic echo /test_id

source_amr_ros1 && rostopic pub /test_id uuid_msgs/UniqueID "uuid: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1]" -r1

source_amr_ros2 && ros2 topic echo /test_id

source_amr_ros2 && ros2 topic pub /gazebo_stuff gazebo_msgs/msg/ODEJointProperties "damping: []
hi_stop: [10]
lo_stop: [11]
erp: [12]
cfm: [13]
stop_erp: [14]
stop_cfm: [15]
fudge_factor: [16]
fmax: [17]
vel: [18]" -r 1

source_amr_ros1 && rostopic echo /gazebo_stuff

source_amr_ros1 && rostopic pub /gazebo_stuff gazebo_msgs/ODEJointProperties "damping: [1]
hiStop: [2]
loStop: [3]
erp: [4]
cfm: [5]
stop_erp: [6]
stop_cfm: [7]
fudge_factor: [8]
fmax: [9]
vel: [10]"  -r 1

source_amr_ros2 && ros2 topic echo /gazebo_stuff gazebo_msgs/msg/ODEJointProperties

Well shit, this one is not super trivial: the action mapping code raises a plain Exception, which needs to be caught. To squelch the formatting error, I need to introduce a new custom Exception type I think. Hmm

Heh, the code styles don't agree it seems.
Locally:
Code style divergence in file 'include/ros1_bridge/action_factory.hpp':

--- include/ros1_bridge/action_factory.hpp
+++ include/ros1_bridge/action_factory.hpp.uncrustify
@@ -397 +397 @@
-    return std::hash<rclcpp_action::GoalUUID>{}(uuid);
+    return std::hash<rclcpp_action::GoalUUID>{} (uuid);

1 files with code style divergence

which is the opposite of the above. I specifically looked at the include ordering myself (and remember because it was annoying to figure out what was correct) so I think the style changed for rolling. Not sure how to continue, besides disabling rolling.

ok, I'll disable rolling

as this has been going back and forth, I want to give this a proper review next week


Adds ResourcesList widget

All updates made and merged in the last PR (#76) in this nested chain of collection execution PRs


Navbar with dropdown is not working properly

Issue description
How to use NavDropdown along with Navbar, due to having two collapse states, this is not working properly, sorry I am new to React.

version #Latest
components: Navbar, Nav

Steps to reproduce issue
Navbar component along with NavDropdown

...

This question may be best for stackoverflow. Without seeing your code I cannot tell you what is happening.


verbose output for cilium status command

Proposal / RFE
Is your feature request related to a problem?
no
Describe the solution you'd like
The current cilium status will only display some basic status from k8s perspective.  I hope if we have cilium status --verbose we can grab the cilium status from the cilium agent pod
Here is the example of the cilium status from the pod
KVStore:                Ok   Disabled
Kubernetes:             Ok   1.26 (v1.26.3) [linux/arm64]
Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
KubeProxyReplacement:   Disabled
Host firewall:          Disabled
CNI Chaining:           none
CNI Config file:        CNI configuration file management disabled
Cilium:                 Ok   1.13.4 (v1.13.4-4061cdfc)
NodeMonitor:            Disabled
IPAM:                   IPv4: 2/254 allocated from <IP_ADDRESS>/24,
IPv6 BIG TCP:           Disabled
BandwidthManager:       Disabled
Host Routing:           Legacy
Masquerading:           IPTables [IPv4: Enabled, IPv6: Disabled]
Controller Status:      11/12 healthy
  Name                    Last success   Last error   Count   Message
  ipcache-inject-labels   never          4s ago       3       k8s cache not fully synced
Proxy Status:                     OK, ip <IP_ADDRESS>, 0 redirects active on ports 10000-20000
Global Identity Range:            min 256, max 65535
Hubble:                           Warning Server not initialized
Encryption:                       IPsec
Cluster health:                   0/2 reachable   (2023-08-18T03:15:59Z)
  Name                            IP              Node          Endpoints
  minikube/minikube (localhost)   <IP_ADDRESS>    reachable     unreachable
  minikube/minikube-m02           <IP_ADDRESS>    unreachable   reachable

We have had some complaints that cilium status already takes too long to execute for large clusters. This seems potentially quite useful, but we would have to keep performance in mind.

Let me try to understand the performance you are referring to here.
If cilium status takes too long because of the cilium itself for some pods. I can only think of we can run cilium status in parallel in different goroutines and come back to the client with a fixed timeout and disregard the one takes too long.
thanks for the reminder

Imposing a cutoff time for the response from all agents is a great idea.

I personally think about this again. If the goal is to understand the overall status of the cilium, we can just pick one pod to run cilium status and return it.
I doubt the value of returning all of pods' output to the stdout...


Bug Invalid date/datetime to NULL

Proposed changes
Issue Number: close #11429 #9861
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

please rebase to pass workflow

closed.


Problem Items Disappears .

Hi ,
Sorry To Disturb you ,
When I Work with The V2 , The Console Work But My Last Section in the Html Domcument which is Contact Form Disappears in The Preview untill I Get focus on it by Clicking her link in the navbar .
This is link of the Preview Screen of what Happened : (https://imgur.com/3q9vDqH) .
This Is link of the preview when i get focus on it : (https://imgur.com/tfcCcjZ) .

That's how i worked with it : https://codepen.io/abcari/pen/MOYdGZ

No problem. Unfortunately, I don't think that this has anything to do with MixItUp. I would need to see a real link to your project to confirm.

okéy i'll code it in CodePen And Put It Here For you To See , and I Hope you help Me Out Of this , really I Need To Work with It .

Hello ,
Sorry , i feel So Shy of you friend For This pro oPrblem , But really I need your help For This Plugin .
here is the Preview Of the template which has the problem : http://chairman-helen-16074.bitballoon.com/ .
So friend here in the preview when you get into it try to reach the contact us section which is the last section , if it appears try to press on arrow up or down or refresh the page and you'll see the problem that the last section can't display .
and here the code on codepen : (https://codepen.io/abcari/pen/QOjbBa) .
i put the code on codepen but the whole template is working on bitbaloon so try to get look , and please help me out . Thank You Very Much .

Hi, i'm not sure but based on V3 you need to add the class "controls" on your ul list.
Basic:

            <button type="button" class="control" data-filter="all">All</button>
            <button type="button" class="control" data-filter=".green">Green</button>
            <button type="button" class="control" data-filter=".blue">Blue</button>
            <button type="button" class="control" data-filter=".pink">Pink</button>
            <button type="button" class="control" data-filter="none">None</button>

            <button type="button" class="control" data-sort="default:asc">Asc</button>
            <button type="button" class="control" data-sort="default:desc">Desc</button>

And you can find here some selectors configurations: https://www.kunkalabs.com/mixitup/docs/configuration-object/
Cheers Chris

Thanks for Your help Chris ,
I tried To Work With V3 but i Face A problem which is My Console didn't work anymore .

You can test:
V3
var mixer = mixitup('#mixit', {
selectors: {
target: '.mix',
control: '.filter'
}
});
V2
$('#mixit').mixItUp({
selectors: {
target: '.mix',
control: '.filter'
}
});

Thanks for your help @in-session.
Hi @patreck-developer, thanks for the additional links.
I've looked at your template, but it appears to be working fine for me. I can't reproduce any sort of problem where the contact form disappears like in your screenshot.
Can you give me some steps to follow to reproduce the bug?

hello ,
try the enter to the Preview i sent it to you and try to scroll down to contact form , and after try to refresh the page one time and if the contact form stays try to click on the array up or down and the contact form will disappears .

thank @in-session  for your help but i tried to do it in js file but the problem still happening .

@patreck-developer I belive this is a problem of jquery.nicescroll.min.js, nicescroll cuts the last section

Hello, I managed to recreate the issue. It is not caused by MixItUp, but my a jQuery scrolling problem that is on your page.

hello , Thank you Very Much For Your Help , Really I didn't Realize That , But I'm Really Sorry for Disturbing you . Thanks you Very Much And Sorry Again .


Mutual recursion sample for F# record types.

The example code for creating mutually recursive record types, does not actually feature any mutual recursion.

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

ID: fe1bc735-dea5-eaf1-8adf-6fa03a43a88e
Version Independent ID: 76d64ebf-a460-3e86-898f-c31c6c70e354
Content: Records - F#
Content Source: docs/fsharp/language-reference/records.md
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

Thanks @davidn-sytelco, I updated the sample.


A new service is created a new window is opened. It's feature or bug?

please complete the following information:

OS version: macOS Mojave
Editor version: v1.48.1
Programming language: js
TabNine extension version: v2.9.2

Issue Details:
My computer memory is overwhelmed when I have two windows open, it's possible to merge the services into one?

It creates TabNine process each time new VS Code window is opened, because it spawns child and attaches to the process so it could communicate with it (stdin/stdout). I had some ideas to fix this issue.
Imagine we have 2 windows, A and B.

If user changes from A window to B window. Active window now is B, it runs timer and if after N time for e.g. 5 minutes window A is inactive it kills process and keeps only process in active window B. This approach fixes the issue and it keeps only 1 process active which means you could spawn as much windows as you want, but it will have only 1 process at the time. It could also kill it instantly you switch to another window. BUT the main problem with TabNine is, it's not persistent and doesn't contain any cache which means it again scans all your project, etc. if project is small no problem, but if it's big it can cause problems and it takes some time to initialize everything on TabNine side.

I like this approach more, I don't know how it would work from TabNine side. It spawns only 1 process using TCP or UDP instead of IPC. Which means we can communicate through network card using HTTP calls and keep only 1 active process for N VS Code windows. We will not have problem mentioned above, because we don't kill process so it doesn't have to initialize every time. But the main question how TabNine will handle this I don't know, because the same process will be in charge of different projects.

While this is currently the expected behavior of TabNine, we are aware that it is problematic and we are working on a fix that should be out in a little while.
In this fix, we will still have a tabnine process for each open window. However most of the memory in the tabnine process is consumed by our local deep model. Once the fix is out, those two processes will share the same deep model, which will run in its own process, thus alleviating much of the pain you describe.
In the meantime, you can consider disabling tabnine deep local option, or moving from deep local to the deep cloud (a paid option).

Is there no way to share the process between multiple windows? loopback tcp / unix domain socket maybe? or have a PID file?
Recently upgraded to deep cloud, so I expect it to be a bit less taxing on my poor 2-core laptop, but I'm glad its being looked at for the Deep Local use-case

@amircodota good news! This will improve TabNine a lot, especially working with several windows opened.

@amircodota  thx. this will save my poor memory 👍

Bumping the issue just to let you all know that @amircodota has made huge progress on this and it we are currently dog fooding on the implementation! Expect this fixed soon enough 🥳

Good news!


HC-522: Remove installing docker at the hysds_dev container level

This PR removes installation of docker at the hysds_dev container level. This is not needed since docker is already being installed at the hysds/base container level.
See related PRs:

https://github.com/hysds/puppet-hysds_base/pull/19

Still need to remove kludges before merging in

@pymonger kludges have been removed


Move lf13 to a103 on tuesday

please file a pull request

fixed by https://github.com/MarcelCoding/bszet-mind/commit/59556130d6dc8cecbc79a75eb33297fe8f6c7fb0


Still seeing "Component has already been discovered" when using with Home Assistant

Describe the bug
Home Assistant log is hit with "Component has already been discovered" for every sensor with each update.
To Reproduce
% sudo pip install ecowitt2mqtt
% /usr/local/bin/ecowitt2mqtt --mqtt-broker=xx --mqtt-username=yy --mqtt-password=zz --mqtt-topic=ecowitt2mqtt/myinstall --input-data-format=ecowitt --hass-discovery
Expected behavior
Quiet log after startup.
Additional context
Although this appears to have been a previously squashed bug,  I'm still seeing it with ecqwitt2mqtt installed via pip run on an pi 3B+.

What version are you running?

$ pip show ecowitt2mqtt
Name: ecowitt2mqtt
Version: 2023.8.0
Summary: A small web server to send data from Ecowitt devices to an MQTT Broker
Home-page: https://github.com/bachya/ecowitt2mqtt
Author: Aaron Bach
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/srp/.local/lib/python3.9/site-packages
Requires: ruamel.yaml, colorlog, python-multipart, uvloop, meteocalc, voluptuous, fastapi, rapidfuzz, certifi, aiohttp, uvicorn, aiomqtt

You have a very old version of the library—specifically, since you're using Python 3.9, you're using the last version of the library that supported 3.9. You'll need to upgrade to at least Python 3.10 in order to get the latest library (at which point, this error will no longer appear).

Got  it - upgraded and it's working correctly, thanks for your help.


Exposes mounter configuration item.

Partial closure of: https://bugs.launchpad.net/charm-kubernetes-master/+bug/1895428

LGTM. Will merge this after https://github.com/charmed-kubernetes/cdk-addons/pull/196.

Found an issue with this that I missed in review. Follow-up PR: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/124


[DOCU-2989] Upgrade guidance + sessions parameter cleanup

Re-opened following accidental early merge.
Description
Upgrade guide:

Added all the breaking changes from the changelog
Tables and upgrade guidance for the sessions library upgrade
The upgrade table sort of combined 3.1 and 3.2 paths, so I split those out into their own tables
Used variables for versions whenever possible

Other topics:

Searched through all of our docs for any mention of the deprecated parameters and updated them to the new ones

https://konghq.atlassian.net/browse/DOCU-2989
Testing instructions
Main changes: https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/upgrade/
Some of the updated topics with new params:
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/install/kubernetes/helm-quickstart/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/install/kubernetes/openshift/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-enterprise/dev-portal/authentication/basic-auth/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-enterprise/dev-portal/authentication/sessions/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-manager/auth/basic/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-manager/auth/sessions/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-manager/auth/oidc/configure/
https://deploy-preview-5183--kongdocs.netlify.app/gateway/latest/kong-manager/auth/ldap/configure/
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

The new sessions are not compatible with the old ones, which means existing sessions are invalidated on upgrade and users will have to reauthenticate, etc, but the session library is compatible with the old configuration.

I don't quite understand this. The new sessions are incompatible, but the session lib is? So - on upgrade, everyone that was logged in will be logged out, and they have to reauthenticate. That's the whole thing.
According to the library's release notes, it is not backwards compatible: https://github.com/bungle/lua-resty-session/blob/master/Changes.md#400---2023-02-01 - that seems to contradict what you're saying here.
I do think that we should document these changed parameters as "recommended" still. Ie, sure, your config will still work, but we never recommend using anything deprecated.

@lena-larionova

According to the library's release notes, it is not backwards compatible: https://github.com/bungle/lua-resty-session/blob/master/Changes.md#400---2023-02-01 - that seems to contradict what you're saying here.

Right. The explanation is that the session library is never configured directly by users: it is rather accessed through plugins on the gateway. The plugins on Kong gateway add the compatibility layer between old and new configurations, so the library is indeed not backwards compatible, but the session, oidc and saml plugins are, because they take the old parameters and translate them into the new ones when necessary (aliasing). As a result the session configurations on Kong Manager and portal are backwards compatible.

I do think that we should document these changed parameters as "recommended"

Agree

deprecated params: recommended to remove? they will work for now, correct?

This might actually need to be fixed, the parameters that say "deprecated" on oidc and saml are actually removed, i.e. they are now ineffective if configured.

Though reading through the upgrade doc again, maybe not for this PR, but I feel like the Upgrade page is getting to be a bit long. Maybe we could split the upgrade paths + instructions into one page and the upgrade considerations/breaking changes into another page? There's a lot of good considerations, and I almost wish they were included a little bit in the upgrade steps (with a link to the section for more information about that particular breaking change, etc.).

Agree that this is not for this PR. I like the idea though - maybe we can do a follow-up ticket post-3.2 release.


No longer use , or ; for multiple inputs.

If extra inputs required use html parameters instead.
Implement min, max and step as html parameters on the number and slider variables.
Implement items parameter on dropdown. The items parameter takes a python list which just needs to be valid code for a python list. Therefore it can be static or it can be a custom list based on python variables.
Implement the relevant html parameters and then add a deprecation notice for the previous API for version 0.4.1.
Remove the ability to use , or ; to separate values in version 0.6.0.

Implemented usage of both , and ; in version 0.4.0. Will remove usage of , in version 0.6.0

Complete. Now just need to leave the deprecation notices up for a set time.


Utiliser les prefix git flow

Base configuration should be the git flow prefix :

feature
hotfix
release
develop

You can also keep your own prefix, because they can be useful.
Good job guy !

I add selector in settings
GIT Flow
Angular
SemanticCommitMessage
If more to add, please open an issue 😃
Have a nice day and be happy

So i search for documentation about it but everything is speaking about name in branch
like following :

bugfix
config
feature
hotfix
init
release
support
version

Are you sure it's about commit prefix ?
If Yes, I commit with the full selection of prefix, if  not, i don't commit it 😉
source: https://github.com/petervanderdoes/gitflow-avh/wiki#reference

With settings if needed you can add your own prefix 😃

I forgot documentation for prefix selector, I add it on next release


care doc fix

Fairly minor change, documenting existing behaviour.
Also a minor wording fix in exception text (discrete -> continuous).

Coverage remained the same at 79.15% when pulling 065b2cf9cd55db2c7ed7a1c656c7ed20706fd695 on roryyorke:care-doc-fix into 38d71254c483020c56be9f31972a7f958928c772 on python-control:master.

Coverage remained the same at 79.15% when pulling 065b2cf9cd55db2c7ed7a1c656c7ed20706fd695 on roryyorke:care-doc-fix into 38d71254c483020c56be9f31972a7f958928c772 on python-control:master.


invokeMethod arguments confusing (needs better documentation)

Currently invokeMethod has the signature
Future<dynamic> invokeMethod(String method, [dynamic arguments]) async {
Which is great, however on Android its not clear how to fetch the arguments. You can either call getArguments() on MethodCall (in Android) which I assume returns the array of arguments, or there is also a method called getArgument(key). Investigation into the java source for getArguments(key) reveals that it does something like
   public <T> T argument(String key) {
        if(this.arguments == null) {
            return null;
        } else if(this.arguments instanceof Map) {
            return ((Map)this.arguments).get(key);
        } else if(this.arguments instanceof JSONObject) {
            return ((JSONObject)this.arguments).opt(key);
        } else {
            throw new ClassCastException();
        }
    }

This basically means if I pass in a Map into invokeMethod I can fetch the key and values.
This is great but it's not documented anywhere as far as I can tell.

cc @mravn-google

The Android side is documented here. The MethodChannel can be used with any MethodCodec, which is really the right place for documenting which argument values are accepted, or what they translate into on the target platform. I'll add a link to the standard codec.


STM32 I2S Driver Clock Configuration

Discussed in https://github.com/zephyrproject-rtos/zephyr/discussions/77480

Originally posted by rriveramcrus August 23, 2024
	if (cfg->pclk_len > 1) {
		if (clock_control_get_rate(DEVICE_DT_GET(STM32_CLOCK_CONTROL_NODE),
					   (clock_control_subsys_t)&cfg->pclken[1],
					   &freq_in) < 0) {
			LOG_ERR("Failed call clock_control_get_rate(pclken[1])");
			return -EIO;
		}
	}
	/*
	 * The ratio between input clock (I2SxClk) and output
	 * clock on the pad (I2S_CK) is obtained using the
	 * following formula:
	 *   (i2s_div * 2) + i2s_odd
	 */
	i2s_div = div_round_closest(freq_in, bit_clk_freq);
	i2s_odd = (i2s_div & 0x1) ? 1 : 0;
	i2s_div >>= 1;

Hello, I am a bit confused by this code snippet in the i2s_ll_stm32.c driver. This snippet comes from the i2s_stm32_set_clock function. I don't expect pclk_len to ever be greater than 1, so freq_in is never set. Am I missing something in my understanding of the I2S and clocking drivers?
For context I am trying to run the i2s output sample application on an STM32 Nucelo F401RE to verify a sine wave output. My overlay and clock configuration are here: https://github.com/zephyrproject-rtos/zephyr/commit/8c9c638e092b5fc1cb699c039f9cd654d876ccc9

Fixed by https://github.com/zephyrproject-rtos/zephyr/pull/77655, but V3.70 backport PR expects an issue.


Update dependencies in lock file

Codecov Report

Merging #170 (1a971d8) into main (9ac9b6e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #170   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          687       687
=========================================
  Hits           687       687

Continue to review full report at Codecov.

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


Update source prerequisite behavior

Updates the behavior of multiple source fields. Now, a Source i will be visible if source:i-1 has a non-empty value, or if any source tag with index > i has a non-empty value.
This will ensure all Source fields from 1 to 3 to be visible if source:3 has a non-empty value

@1ec5 I assume based on your comment that this is not ready to merge?

I've been working on tests for this behavior for a while, more specifically for the id.uiSectionPresetFields() section, but haven't been able to get them working just yet.


[MB-4208] Adds testdatagen function for MTOAgent.

Description
Adds testdatagen functions for MTOAgent -  MakeMTOAgent and MakeDefaultMTOAgent.
Reviewer Notes
Inline comments.
Setup
Run new unit test to ensure nothing breaks.
mylaptop ~ %: cd /mymove
mylaptop ~ %: make server_run
mylaptop ~ %: go test ./pkg/models --testify.m "TestMTOAgentTestdataGen" -v

Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story MB-4208 for this change

Messages

:book:
:link: MB-4208

  Generated by :no_entry_sign: dangerJS against fb3501463fc05a0d68383ef89fbb756379828921


Wallet Not Syncing

i have downloaded a wallet and it just does not sync to the network.

The seed server was offline at that point in time. This has been fixed.


tx_initialize_low_level.s:33: undefined reference to `systick_cycles' collect2.exe: error: ld returned 1 exit status

Hi! I'm new to Azure RTOS and just started playing with NXP's MCUExpresso IDE. After installing everything I create a new project using only "Azure RTOS" (no driver or anything) and the project fails to build with the following error:
E:\Nxp\IDE-Workspace\Test\Debug/../azure-rtos/threadx/ports/cortex_m7/mcux/src/tx_initialize_low_level.s:33: undefined reference to `systick_cycles'
Please advise,
Thanks!

Sounds like NXP messed something up, because all of our ports (https://github.com/azure-rtos/threadx/tree/master/ports/cortex_m7) have SYSTICK_CYCLES defined.

Closing this issue. Feel free to re-open if you have more questions.


Typo "Github"→"GitHub"

https://docs.microsoft.com/en-us/cli/azure/containerapp/github-action?view=azure-cli-latest

#PingMSFTDocs

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

ID: 0816bb7a-1e85-c4a9-f77f-e2ebef587fa1
Version Independent ID: 7bde93ab-9a2b-5d5a-b23f-202b78acb844
Content: az containerapp github-action
Content Source: latest/docs-ref-autogen/containerapp/github-action.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to CXP team

@hyoshioka0128 Creating a PR to fix this.

@yonzhan @RakeshMohanMSFT  @zhoxing-ms  - Thanks!


Support binary logical attributes in PathLayer and SolidPolygonLayer

For #3758
Change List

Support binary input to PathTesselator and PolygonTesselator
Unit tests
Render tests

Coverage increased (+2.7%) to 83.744% when pulling a9dbdb3c95124d183bed1da2c00d6956f3ef114b on x/binary-path-attributes into 5328f38e0aec05dab36d477f52fd2eaca6f9e7c0 on master.


Terminix has been renamed to Tilix due to trademark issue

More information at https://github.com/gnunn1/tilix/issues/815

Thanks, I'm aware of this since I've been part of the discussion for the new name and there's also already PR #13.
Haven't got the time to update the project and all assets yet. I think I'll also implement a migration function for the install.sh script.

Sorry I had not seen #13 .
Keep your great work with nord .

🚢 Shipped in release version 🏷 0.3.0.


dnstap logging not recovering after dnstap process restarts (regression in 1.11)

With unbound 1.11 being first release that switched away from libfstrm (#164, #264), we observe number of regressions with dnstap logging over unix socket.
This one is pretty obvious and relatively easy to reproduce:
* unbound running with dnstap logging enabled over unix socket, under some measurable load (few thousands+ requests per minute)
* dnstap process consuming the logs is restarted.

with 1.9.6, dnstap can reconnect to socket and process samples continuously
with 1.11.0, dnstap can reconnect to socket but receives only 99 samples, all stamped with ~time dnstap process was restarted. Next restart gets another 99 samples, and so on.

Restarting the unbound while leaving dnstap process to run mitigates the problem, until the next time dnstap is restarted.
Unbound's performance seems unaffected.
Doesn't happen when unbound is idle/lightly used.
We observe this on all our Unbound instances with 1.11, never happened on 1.9.6 or earlier versions we used before.

Thanks for reporting! This should be fixed by commit https://github.com/NLnetLabs/unbound/commit/00fe4b03062c2e9adacb95ade9418b759c1238ca


dotnet-format failed

partial log:
2020-11-29T08:43:21.8135623Z ##[group]Run dotnet format
2020-11-29T08:43:21.8136143Z [36;1mdotnet format [0m
2020-11-29T08:43:21.8200889Z shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
2020-11-29T08:43:21.8201413Z ##[endgroup]
2020-11-29T08:43:22.7229480Z   Could not find a MSBuild project file or solution file in 'D:\a\HandyControl\HandyControl'. Specify which to use with the --workspace option.
2020-11-29T08:43:22.9104666Z ##[error]Process completed with exit code 1.

@lindexi can you take a look at it sometime


Search broken

INFO[2023/01/10 22:48:43] [smtp] starting on <IP_ADDRESS>:1025
INFO[2023/01/10 22:48:43] [http] starting server on http://<IP_ADDRESS>:8025/
ERRO[2023/01/10 22:52:10] sql: Scan error on column index 5, name "FromJSON": converting NULL to string is unsupported

go version go1.19.4 freebsd/amd64
mailpit version: 47a556d05e68f4ce59548ea423b11dcad9ea2830

Thanks for the report.
This was briefly an issue before v1.2.8 which should have been fixed in early November last year.
Could you please provide me some more information @yonas ...
Do you currently have old emails in your database what may have been capture before v1.2.8?
If some of your captured mail was from < v1.2.8 then there isn't anything I can do about it unfortunately as the data was stored as a null when there was no From address, rather than an empty JSON object (this breaks the SQL JSON search which is the error you are seeing) :-( If it was captured in v1.3.5 recently, can you please provide me with a copy of the full email (even if you change the values) so I can test please - assuming you can work out which one it is?

Hi @axllent

Do you currently have old emails in your database what may have been capture before v1.2.8?

No, this is a fresh install.

@yonas Do you happen to know what email is causing this, and if so, are you able to provide me a copy of the raw email itself?

Thanks for the feedback! From what I can tell, all emails should contain a From: header - however the RFC documentation is very difficult to read and isn't crystal clear (to me) as to what exactly it should contain. Anyway, I was able to replicate the issue on my end following your instructions and have just pushed a fix for it to correctly index a missing From header. You'll find the fix in the latest release (v1.3.6).

Thanks @axllent , it works! :partying_face:


[Misc. Devops] Don't run the build step twice

Purpose
This PR stops the compose build step being run as a precursor to the run_infrastructure.py script, saving about ~1min from the CI process.

The unsafe checks are currently broken due to an issue with the BigQuery secrets, that shouldn't be a blocker to merging this PR, since the unsafe checks aren't effected here.

Nice @seanpreston, the speed improvements here were definitely noticeable, thanks.


A lot of resources aren't shown in Resource view of deployments and probably others

Describe the problem/challenge you have
Under resource viewer, I don't currently see config maps, pvcs/pvs etc
Describe the solution you'd like
Under the resource view of say a Deployment or Service I would expect to see resources such as PVCs/PVs, configmaps etc. Everything required for that resource, similar to doing a kubectl describe
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Octant version (use octant version):  Version:  0.16.1
Git commit:  8aebb34922f83894fb02ad393740e96ee1b3d8fe
Built:  2020-10-07T23:36:32Z
Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.11", GitCommit:"3a3612132641768edd7f7e73d07772225817f630", GitTreeState:"clean", BuildDate:"2020-09-02T06:46:33Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Windows 10

Gonna look into this
/assign


Troubles with preservative rerendering when components are used with same props

Just to track that in an issue.
var cellContent = $$(CellContentClass, {
  // HACK: having trouble with preservative rerendering
  // when Components are used with the same props
  // this hack forces a rerender
  hack: Date.now(),
  node: cell
});

This should be fixed now.


Misc fixes

backport  (using /etc/TZ as alternative to /etc/localtime) from stable-1.1 (commit 605d0a85183d2f9d5b0da5629cbadf01173bbb2f)
fix spelling

+1 for the fixes, but the timezone patch collides with #3151

@hardening it's a one line I guess we will manager to update one of the conflicting pulls ;)

@bmiklautz you think so? well, then lets merge ;)