kitten test file upload returns marshalling error

Following the example code laid out in your upload_test.go I am getting an error posting the kitten photo to a private mediawiki instance.
The post is successfully posting - I see the kitten photo & then manually delete it before rerunning my own test case.
On successful post, upload.Do is returning a marshalling error:
error parsing response: json: cannot unmarshal string into Go struct field .upload.imageinfo.metadata.value of type int
The UploadResponse Printf(%v) is in the attached file.
I have confirmed I get the exact same marshalling error running your upload_test.go test case against my mediawiki instance.
Can you provide any suggestions on how to debug this?

Product
Version

MediaWiki
1.39.3

PHP
7.4.33 (litespeed)

MariaDB
10.3.36-MariaDB-cll-lve

ICU
63.1

Go
1.20.4

mwUploadResponse.txt

Diving into the mediawiki library, it seems the problem is upload.go:82
type UploadUploadImageinfo struct {
...
	Metadata  []struct {
		Name  string `json:"name,omitempty"`
		Value int    `json:"value,omitempty"`
	} `json:"metadata,omitempty"`

It appears the root cause is json upload.imageinfo.metadata.value field is type heterogeneous on return from mediawiki.
I see ints, actual text strings (i.e. not just quoted ints) & arrays in the response for that field.
e.g.
"upload": {
"imageinfo": {
 "metadata": [
      ...
        {
          "name": "Model",
          "value": "SP570UZ                "
        },
        {
          "name": "Orientation",
          "value": 1
        },
        {
          "name": "ComponentsConfiguration",
          "value": [
          ...
            {
              "name": "_type",
              "value": "ol"
            }
``

As a hack I can ignore the error, or change:
UploadUploadImageInfo.Commonmetadata []string -> any
UploadUploadImageInfo.Metadata.Value int -> any
which clears the unmarshal error & allows TestUploadGood() to run clean.
But it is almost certainly not the proper answer.

Hi Eric --
I really appreciate you flexing this code a bit. Keep in mind I wrote this for a little side project, so it's not pretty by any definition (translation: I feel bad that you're having to deal with my gross code).
I think the correct thing to do would to change UploadUploadImageInfo.Metadata.Value to an any type, since it really can contain pretty much anything.
I suspect the same may be true of UploadUploadImageInfo.Commonmetadata (since you found it clearly doesn't comply with a []string contract, but without a robust example of the response I can't say for certain. Should it be an anyor[]any`?
Regardless, if you want to put up a CR, I'll be happy to accept it. If you prefer though, I can just make the changes here when I get the change a little later.

There are several other tests failing because the rendered test JSON isn't identical to the JSON returned by Mediawiki.
I don't know why I thought expecting those to be identical was a good idea. I'm going to get those passing or remove them.

Thanks for the response! I am a relatively new gopher (but not new coder). I have been doing a mediawiki project in go partially as a learning exercise. I was using go-mwclient, but it doesn't support much of the API (and seems unmaintained - I had to fix a bug to get it working & no response to my PR). Yours does support the API I need, so its a win for me. I learned a lot diving into your code.
commonmetadata is the same issue as Metadata. An example is in the attached file on my issue. It is an array of Name/value pairs where the Value can be an int, string or array of dynamic name/value pairs. It could follow the same pattern as Metadata rather than []string.
I tested this by changing Commonmeta to look just like Metadata
	Commonmetadata []struct {
		Name  string `json:"name,omitempty"`
		Value any    `json:"value,omitempty"`
	} `json:"commonmetadata,omitempty"`

upload_test.go TestUploadGood ran clean.
It seems we could refactor the Value any of both into a Value DynamicValue and create a custom marshaler for it. Does sound like the right approach?
Was thinking:
type DynamicValue struct {
	Code   int // type code for what got stored
	Int    int
	String string
	Array  [](*DynamicNameValue)
}

type DynamicNameValue struct {
	Name  string
	Value DynamicValue
}

I didn't find alot written up on handling JSON dynamic typing in go, there may be a better approach.
I plan to use the Protect API next.
Oh, and I bought your book to say thanks!

There are several other tests failing because the rendered test JSON isn't identical to the JSON returned by Mediawiki.
I don't know why I thought expecting those to be identical was a good idea. I'm going to get those passing or remove them.

I did notice this. They all looked like additional params now being returned in the reply that were not in the expect side of the test. It seemed like a small fix.


Values not updated when changed in .env file. Caching bug

There seems to be a bug in the generator. When I change the values in the underlying .env file, delete the env.g.dart file and run the generator, the old values are written to the generated file.
Consider this code:
// lib/env/env.dart

import 'package:envied/envied.dart';

part 'env.g.dart';

@Envied(path: '.env.dev', useConstantCase: true)
final class Env {
  @EnviedField()
  static const String apiBaseUrl = _Env.apiBaseUrl;
}

# .env.dev
API_BASE_URL="dev.example.com"

# .env.prod
API_BASE_URL="prod.example.com"

I am using two .env files: .env.prod and .env.dev.
How to reproduce the bug

Update the value in .env.dev from "dev.example.com" to "devnew.example.com"
Delete env.g.dart
Run the generator

Expected result:
The value in env.g.dart is now "devnew.example.com"
Actual result:
The value is still "dev.example.com"
When it works:

Changing the path from .env.dev to .env.prod and back
Run flutter clean and then generate again with dart run build_runner watch --delete-conflicting-outputs

It looks to me like there is some caching issue going on.
Version: 0.5.3

Sorry, I just found this issue in "Known Issues" in your readme...

I know this is a known issue, but can we do a workaround? I like to have strictly typed ENV files, however, this is actually so critical, that I might need to switch to another approach/library.
@petercinibulk

I know this is a known issue, but can we do a workaround?

Well, for starters, you could suggest one.

might need to switch to another approach/library

What's stopping you?

For anybody else looking for a solution, I've switched to using flutter_dotenv and a similar approach can be achieved using this code:
// lib/env/env.dart

+import 'package:flutter_dotenv/flutter_dotenv.dart';
-import 'package:envied/envied.dart';

-part 'env.g.dart';

-@Envied(path: '.env.dev', useConstantCase: true)
final class Env {
-  @EnviedField()
-  static const String apiBaseUrl = _Env.apiBaseUrl;
+  final String apiBaseUrl = dotenv.maybeGet('API_BASE_URL') ?? 'https://localhost:3000';
}

And to fetch:
-const apiBaseUrl = Env.apiBaseUrl;
+final apiBaseUrl = Env().apiBaseUrl;


the grad calculation takes up a lot of memory

https://github.com/SHI-Labs/Smooth-Diffusion/blob/5522761bb68fcb6ac1cfaee5a5b855d4a56ea33f/train_smooth_diffusion.py#L312
grad, = autograd.grad(
        outputs=(fake_img * noise).sum(), inputs=latents, create_graph=True
    )

The calculation of gradients is memory inefficient and lacks support for flast-attention. Consequently, when training with the reg_loss, it becomes necessary to reduce the batch_size.

Hi, I wander how much the extra memory cost may be? Could you give me a rough number?


Make default volume size configurable

It is desirable to be able to ask Flocker to create volumes other than 100GB in size, for example on EBS where you might not want to pay for lots more storage than you need.
See https://groups.google.com/forum/#!topic/docker-user/Ouq94UGpBwU
The constant at https://github.com/ClusterHQ/flocker-docker-plugin/blob/master/flockerdockerplugin/adapter.py#L18 could be changed to be an optional environment variable, and then the user would be able to configure sizes globally for the plugin at least in the upstart script for the flocker plugin.

Thanks Luke for raising this issue here. It is annoying to see a 100GB volume get created with the use
of flocker plugin. you have rightly mentioned that if somebody like me want to just try out working of flocker plugin in AWS cloud, I have pay for a 100GB volume and thats not fair. I storngly feel this should be configurable for ease of use. May be in the cluster.yml file or other better place.

The default volume size in my testing is 75.00G.   Is it possible to change this default?
is it possible to pass the volume size in the docker run command, for example :

docker run --volume-driver flocker -v volume1:/data -it ubuntu bash

is there any way to add vol size arg to the above command?  (of cause you can create the volume first with specific size, but what happened when the docker run command provision the new volume)
Thanks


Update README_TR.md

Directional suffix is required when translating into advanced Turkish.
"İleri" is Forward.
True Suffix
"İleriye" is Onward.

Evegt doğru.....

The entire translation of the text was done with google translate. Although it contains context, it deserves a better translation.


Autovod doesnt work

Hi,
i installed autovod and configured everything. The sample.mp4 also uploaded correctly to youtube. But now it doesnt upload old vods (or new, if i go live) to youtube.
pm2 status:

What can i do?

Hi @jenslys
Log:
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/init.py", line 19, in
0|ebattleg |     from streamlink.api import streams
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/api.py", line 1, in
0|ebattleg |     from streamlink.session import Streamlink
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/session.py", line 16, in
0|ebattleg |     from streamlink.plugin.api.http_session import HTTPSession
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/plugin/api/init.py", line 1, in
0|ebattleg |     from streamlink.plugin.api.http_session import HTTPSession
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/plugin/api/http_session.py", line 13, in
0|ebattleg |     from streamlink.utils.parse import parse_json, parse_xml
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/utils/init.py", line 1, in
0|ebattleg |     from streamlink.utils.cache import LRUCache
0|ebattleg |   File "/usr/local/lib/python3.6/dist-packages/streamlink/utils/cache.py", line 2, in
0|ebattleg |     from typing import Generic, Optional, OrderedDict as TOrderedDict, TypeVar
0|ebattleg | ImportError: cannot import name 'OrderedDict'

Fixed it!
Needs python 3.7 or higher


Change !+ and !- to emoji

Mafi is lazy; but there is /was a request to change !+ and !- to use emoji
The options discussed where:
👍 / 👎
❤  / 💔
⬆ / ⬇
I don't see an option to link to direct messages, but it's from Aug 18th 2017

There is no facility currently to link to messages, but bots do have the ability to quote/embed other messages. Possibly with the message id I can create links that trigger a search for the original message or something


Enhance failure detection to also recognize failure status of top level resources

MCAD provided a mechanism for encoding conditions of the top level resources that if present would indicate success or failure.  This was used to augment the pod-level status infromation.
We need to design and Implement a similar mechanism for the v1beta2 AppWrapper.

We've discussed further and primarily see value in recognizing when a top level resource has failed.  This would allow us to transition the AppWrapper to failed immediately (without relying on pod-level health).
There seems to be less value in the resource-level success status because we still would have to wait for all pods to reach a Completed state before we could release resources (if we released eagerly, we could cause quota overages).

#163 does this for PyTorchJobs

Closing; we've now implemented for all the supported GVKs that have useful operator-level failure statuses.


Allow NULL callback in uv_async_init

Hi,
Would be very handy to use async to only wakeup the loop.
I use a lot the uv_prepare_t to send/process my datas that came from an other thread witch use the uv_async_send(...) to wakeup the loop and don't do any processing in the callback.
R.

We could indeed do that, which I guess might benefit some like yourself. I'd +1 to a patch.

Isn't that what 1510ce81fde8f07a4f692274de467dfdad33c604 did?

Yep.  It's even documented as such:

A NULL callback is allowed.

I'll go ahead and close this out.

LoL memory, thanks guys!


Support molecule alignment based on a template

It would be very nice to support this out of the box in MoleculeRepresentation https://www.rdkitjs.com/#drawing-molecules-constraints in your implementation.
Specs:

offer a template prop on the MoleculeRepresentation component , which accepts a MolBlock string representing a substructure with 2D alignment coordinates information.
if template is defined and if smiles is passed to MoleculeRepresentation (not smarts), align smiles representation to template coordinates.

@MichelML Sure, we'll add that, thanks for the suggestion

Done in #40, feel free to run storybook to look up the props to pass.


Add support for skipping VIRTUALENVWRAPPER init in modules/python

This branch just changes modules/python/init.zsh so that it will recognize if the user defined a PREZTO_PYTHON_NO_VIRTUALENVWRAPPER var and will not do the virtualenvwrapper setup and sourcing of virtualenvwrapper_lazy.sh in that case.

Bump. Please merge.

I get bitten by this every time I reset local modifications to prezto, and I am unable to open a new terminal window as a result. Normally I just have this line commented out as a local modification.
The problem is that when using pyenv, you must load virtualenvwrapper with pyenv virtualenvwrapper instead of source "$commands[virtualenvwrapper.sh]".
Please merge this so I can configure prezto to skip this step.

If I understand correctly, the problem is caused by the fact that pyenv registers the virtualenvwrapper.sh command through its shims which causes prezto/modules/python to automatically detect it and attempt to source it. As far as I can tell, calling source virtualenvwrapper.sh on my system crashes the shell if pyenv was loaded beforehand. Consequently, isn't the following the easiest solution to the problem?
  if (( $+commands[pyenv] )); then
    pyenv virtualenvwrapper
  else
    source "$commands[virtualenvwrapper.sh]"
  fi

Also, if using pyenv the following enviroment variable should be set:
export PYENV_VIRTUALENVWRAPPER_PREFER_PYVENV="true"

This seems really useful. I'll try to take another look at this later today.

Thanks for your contribution! Sorry it took so long to merge.


DSC in a loop copying vhdx

Trying to deploy the Template into Azure, it fails at the AzSHCIHost001/ConfigureAzSHCIHost.
The error which is returned is:
"statusMessage": "{"status":"Failed","error":{"code":"ResourceOperationFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'ConfigureAsHciHost'. Error message: \"DSC Configuration 'ASHCIHost' completed with error(s). Following are the first few: Exception setting \"TargetPath\": \"Interface not registered\r\n\r\nFailed to find proxy registration for IID: {ADD8BA80-002B-11D0-8F0F-00C04FD7D062}.\" The PowerShell DSC resource '[cShortcut]BuildScript' with SourceInfo 'C:\\Packages\\Plugins\\Microsoft.Powershell.DSC\\<IP_ADDRESS>\\DSCWork\\ashcihost.0\\ashcihost.ps1::106::5::cShortcut' threw one or more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details. The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "}]}}",
Thanks.

I've got the same issue as Dragmarr. Anybody any idea?

I deployed the template again from scratch, works as expected now.

Thanks beckersfa - can confirm that the template deployed as expected for me too this morning. I tried to re-deploy a few times last week but kept failing so happy it working today.


Use Action instead of Kotlin lambda.

Two commits:

First uses Gradle's Action interface for better DSL support.
Adds an initial gradleTest setup for TestKit tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is awesome! Thanks for fixing the Groovy syntax issues with this!
Do we need another Gradle wrapper? Can't we run tasks from the root? : dependency-guard-gradle-plugin ?
If we do need the wrapper can we use symlinks to the root gradlew and other wrapper files?

Will do a proper look over tomorrow after I am back on a computer and not on my phone.
Thanks again!

Failing with an API check (predictably):
> API check failed for project dependency-guard-gradle-plugin.
  --- /home/runner/work/dependency-guard/dependency-guard/dependency-guard-gradle-plugin/api/dependency-guard-gradle-plugin.api
  +++ /home/runner/work/dependency-guard/dependency-guard/dependency-guard-gradle-plugin/build/api/dependency-guard-gradle-plugin.api
  @@ -21,7 +21,7 @@
   public class com/dropbox/gradle/plugins/dependencyguard/DependencyGuardPluginExtension {
   	public fun <init> ()V
   	public final fun configuration (Ljava/lang/String;)V
  -	public final fun configuration (Ljava/lang/String;Lkotlin/jvm/functions/Function1;)V
  +	public final fun configuration (Ljava/lang/String;Lorg/gradle/api/Action;)V
   }

This is awesome! Thanks for fixing the Groovy syntax issues with this!
Do we need another Gradle wrapper? Can't we run tasks from the root? : dependency-guard-gradle-plugin ?
If we do need the wrapper can we use symlinks to the root gradlew and other wrapper files?

I wouldn't recommend symlinks because they won't work on Windows.
I didn't even try to create the wrapper. It just sort of happened. In retrospect, I'm not sure how. Maybe when I imported it into IDEA?
The reason I was running tasks from the plugin directory was because that's where the settings.gradle.kts file was; this is a marker for a root project.

Merging for progress and since this is still a snapshot.  I'll clean up the tests in CI and link to that in a few.

Removed the extra gradle wrapper here: https://github.com/dropbox/dependency-guard/pull/6
Will just push the removal of the comment to main.


Some QR codes do not work

Hello,
first thank you very much for this work. It helps me a lot.
During testing we have found out that some QR codes do not work and we can't find why. We are testing with several mobile bank apps (broken QR codes do not work for none)
We are using version 1.0.7 with qrcode 1.5.0.
For example (working solution):
"Amount": "28",
"BankAccounts": "1",
"CurrencyCode": "EUR",
"IBAN": "SK12345600000000000123456",
"PaymentNote": "Name A",
"PaymentOptions": "1",
"Payments": "1",
"SpecificSymbol": "4129",
"VariableSymbol": "2268824129"
Not working:
"Amount": "74",
"BankAccounts": "1",
"CurrencyCode": "EUR",
"IBAN": "SK12345600000000000123456",
"PaymentNote": "Name B",
"PaymentOptions": "1",
"Payments": "1",
"SpecificSymbol": "4129",
"VariableSymbol": "2268824129"
I am open to testing just let me know. Due to privacy reason I am not sharing whole information.

Thanks @Matej4386 for reporting this issue.
Can you try scanning the QR using the Tatra Banka app? I have not been able to
reproduce the problem using your model example.

Hi @xseman,
thank you for quick response. Model is not the exact one (I cant post the not working model here) - I can sent it to you.

So after testing we found that the non-ASCII characters are invalid, not sure if
any banking app will automatically convert them to basic ASCII, but I wouldn't
count on it. The solution could be for the generate function to remove the
diacritics from PaymentNote as side-effect.

Resolved. Thank you very much

v1.3.2 will convert latin-1 to basic letters. f9932a5bafed18bda9c5abb53730d823f1824d9c


Update standalone doc with NSFS instructions

Explain the changes

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

[ ] Doc added/updated
[ ] Tests added

closing as it's not relevant for now as we will go with no db noobaa.


Poor quality live streaming

Hi,
Thank for all your work on this api, it's really very useful!
I'm having trouble getting a decent quality stream from my gopro hero 4 to facebook. Even if I just display the stream locally, it's quite blury, unlike when I record using the camera normally.
In my gopro_keepalive.py script, I tried adding in:
gopro.streamSettings("4000000", "4"), it doesn't seem to change the quality, though.
For some reason it wouldn't resolve the constants when I tried:
gpCam.streamSettings(constants.Stream.Bitrate.B4Mbps, constants.Stream.WindowSize.R480) #For HERO4
It doesn't look like 480p streaming at all. It looks something more like 240p
In fb_live.sh, I put in:
VBR="4000k"
FPS="30"
QUAL="medium"
When I try to put QUAL = "high", I get
"Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height"
Is there any way you can point me in the right direction?
It also goes kind of pixelated at times. However i'm not too sure what to make of the errors that the gopro_keepalive.py script gives:
[h264 @ 0x1f2f6e0] left block unavailable for requested intra4x4 mode -17kbits/s speed=1.05x
[h264 @ 0x1f2f6e0] error while decoding MB 0 12, bytestream 4295
[h264 @ 0x1f2f6e0] concealing 130 DC, 130 AC, 130 MV errors in P frame
[h264 @ 0x1b4b7f0] concealing 182 DC, 182 AC, 182 MV errors in P frame8.0kbits/s speed=1.05x
[h264 @ 0x1b9d040] concealing 207 DC, 207 AC, 207 MV errors in P frame7.7kbits/s speed=1.05x
[h264 @ 0x1f2f6e0] left block unavailable for requested intra mode=1137.4kbits/s speed=1.05x
[h264 @ 0x1f2f6e0] error while decoding MB 0 8, bytestream 7354
Thanks!

Anyone find the solution?


[WEBHOOKS] No objects to treat webhooks

Would the devs create objects that represents the request's object webhook?

Hi @Odravison
To receive webhooks, you must set the notification preferences. Just it.
The Moip will send webhooks to the registered URL, it'll be based on the status you want to be notified (ex: ORDER.CREATED, PAYMENT.AUTHORIZED, TRANSFER.COMPLETED). Check a notification preferences example here.

⚠ The way that the application will treat the webhook is responsibility of developer.

Thanks @mbnakaya .
Would be nice to has an object to every event of webhook.
Your guys are open to receive PR ?! I will be able to implement this objects very soon.
For now I'm using JSONObject to encapsulate the body of webhooks.
Best regards.

@Odravison
Yes, I agree with you, but for priority reasons we don't put this on our road map, until now.
Sure!! We're totally open to receive contributions, and we appreciate it so much. I only ask you to read the CONTRIBUTING.md.
Best regards.


Improve in editor music scriptracker.js to act like GBT

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Bug fix / feature.

What is the current behavior? (You can also link to an open issue here)
Split of #294 to make merging easier.
Related to #172, #83 and partly #176
The in editor music preview is very inaccurate and will play any mod files without GameBoyTracker limits, leading to confusion and not being useful for previewing common mistakes.

What is the new behavior (if this is a feature change)?
Notes use last set volume instead of the default sample volume.
Channel 4 Noise is forced to note C5.
Instruments are limited to their channels, (no pulse waves on the noise track.)
Forced pan to hard left, both, or hard right.
Tick speed changes the tempo to match in game speeds (tick speeds 4 or faster).
Instrument 28 pitched to better match in game noise.
Hard code Pulse and Wave sample instruments 1-14 as small, accurate samples.
(Catch users with wrong instruments in their mod. Sounds nicer.)
Add persistent Volume sweep for volume envelopes (not in GBT just yet ;)

Other information:
Most cases except odd GBT bugs are now reproduced, (some gbt bugs are being fixed)
It is now useful as a fast preview that reveals common mistakes (volume), without building a game.

That's great, thanks @RichardULZ.
I'm wondering at some point we could maybe split this into a separate git repo scriptracker-gbt that GB Studio could import as a node module. Could be useful for other projects too! Something to think about

Not sure how making it a node module works but sounds neat.
At this stage there's not much more i can do just replicating GBT player bugs (I have a few being fixed in gbt player itself).
The major improvement would be to rip out the Javascript emulators audio code, and get that to work with the script tracker.
A half way point is having it work stand alone just to poke at when playing/making sound effects, seems like the only way to get the right tones, pitch bends, noise sounds, and fades.
Will finish off GBT improvements and volume envelopes first (they're pretty much done), got stuck with pitch bends, they work too, but it would be better if they worked more like a mod tracker for consistency.


Feat:Enhance Navbar Hover Animations, Alignment and Logo Size

Description :
The current navbar could benefit from a few UI enhancements to improve overall aesthetics and user experience. Here’s what I propose :
1) Hover Animations : Add smooth and subtle hover animations to navbar items to make interactions more engaging.
2) Alignment: Improve the alignment of the navbar items to ensure they are evenly spaced and visually balanced.
3) Logo Size : Adjust the logo size to maintain a consistent look, ensuring it complements the rest of the navbar elements without being too large or too small.
Benefits :

Enhances the visual appeal and interactivity of the navbar.
Provides a more polished and professional look, ensuring a better user experience.

Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

go ahead @rohitmore07


[Feat]: Add support for configurable port and host

Port is already configurable

Add support for the following
  #addr: <IP_ADDRESS>
  #proto: udp # udp,udp4,udp6,tcp,tcp4,tcp6,tcp-tls,tcp-tls4,tcp-tls6
  #cert: /etc/void/cert.pem
  #key: /etc/void/key.pem

Applies to #28 as well


Button not showing on tasks in Salesforce integration

Relevant integration (if any): Salesforce
🐛 Describe the bug
toggl button salesforce integration issue - user can see button on some pages (e.g. profile page, attached), but not on the task lists

But it's not showing on the task lists

Screenshot from the wiki showing where it should appear:

Other details or context
conversations/22174259794

case reference


Initial Release

Initial release of the HPDcache TestBench and TestPlan

@MikeOpenHWGroup, @JeanRochCoulon  Can you please review and accept?
@cfuguet For your information


Issue while mapping DependencyScope from maven dependency tree

Method name -> MavenParsingUtilities -> GetMavenComponentStringInfo
On using below dependency with scope -> compile, in Maven Project,
<dependency>
	<groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
	<version>4.8.0</version>
	<scope>compile</scope>
  </dependency>

The SBOM throws an exception
System.InvalidOperationException: Invalid scope ('linux-x86_64') found for 'io.netty:netty-transport-native-epoll:jar:4.1.87.Final:linux-x86_64' found in generated dependency graph
More Info ->
Dependency tree generated using maven dependency CLI command
mvn dependency:tree -B -DoutputFile=bcde.mvndeps -DoutputType=text -f <SampleProjectPath>, contains value linux-x86_64 and osx-x86_64 which further leads to an exception while parsing dependency Scope.
Snapshot of Dependency tree
|  |  +- com.beust:jcommander:jar:1.82:compile
|  |  +- io.netty:netty-buffer:jar:4.1.87.Final:compile
|  |  +- io.netty:netty-codec-http:jar:4.1.87.Final:compile
|  |  |  +- io.netty:netty-codec:jar:4.1.87.Final:compile
|  |  |  \- io.netty:netty-handler:jar:4.1.87.Final:compile
|  |  +- io.netty:netty-common:jar:4.1.87.Final:compile
|  |  +- io.netty:netty-transport-classes-epoll:jar:4.1.87.Final:compile
|  |  +- io.netty:netty-transport-classes-kqueue:jar:4.1.87.Final:compile
|  |  +- io.netty:netty-transport-native-epoll:jar:4.1.87.Final:linux-x86_64
|  |  +- io.netty:netty-transport-native-kqueue:jar:4.1.87.Final:osx-x86_64
|  |  +- io.netty:netty-transport-native-unix-common:jar:4.1.87.Final:compile

AB#2114682

@tarun06
When printing dependency tree on my end, below is the output
[INFO]    +- io.netty:netty-transport-native-epoll:jar:linux-x86_64:4.1.60.Final:compile
[INFO]    |  \- io.netty:netty-transport-native-unix-common:jar:4.1.60.Final:compile
[INFO]    +- io.netty:netty-transport-native-kqueue:jar:osx-x86_64:4.1.60.Final:compile

as you can see there's compile at the end, so total there are six parts seperated by ":" This is handled correctly by maven detector.  I am not able to recreate maven cli output without "Compile" at the end.  Is there any truncation happening when you test ?

upon investigating further, found that maven considers any value as a valid scope and replaces it with default. However, while printing dependency:tree, the invalid scope is preserved as is.
Solution:
We will match CD behavior to maven's where we detect invalid scope as "Compile"


fix deleting data of other mods

complete credit for the fix goes to bennett-zhang

I just implemented the proposed fix by @bennett-zhang, assuming it works. Regular expressions are a closed book to me.

Ah, nvm, forgot to check wheter there was already a pull request wit that fix. There is.


Quick Forge Fill

Is your feature request related to a problem? Please describe.
It's annoying to have to click in 5 items for a forge (especially since some items look the same and cannot be merged).
Describe the solution you'd like
When you click in an item into the forge, it will find all duplicates in your inventory and put in 4.
Describe alternatives you've considered
Juz do it by hand.
Additional context
I can work on this one. It will be a cool learning experience, but if @showierdata9978  want's it, by all means, take it.

👍

There is a texture pack that will change items that share textures (iron ingots, celestial ingots, steel ingots for example)
This is a good alternative to using mods that would be considered abusable for some reason or another.

Yeah, but even for things like rockite where I might have an inventory full, the texture pack won't change it. It just gets really annoying.

DF Rules


Unable to Distribute the App

Hi Team,
Since this morning we are unable to upload and distribute our iOS app to the Distribution groups
Is this due to this issue : App Center is encountering issues with AAD.
Below is the error:-

16-Mar-2021 16:57:27
Release upload failed

16-Mar-2021 16:57:27
/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360

16-Mar-2021 16:57:27
const releaseId = response.release_distinct_id;

16-Mar-2021 16:57:27
^

16-Mar-2021 16:57:27

16-Mar-2021 16:57:27
TypeError: Cannot read property 'release_distinct_id' of undefined

16-Mar-2021 16:57:27
at ReleaseBinaryCommand. (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)

16-Mar-2021 16:57:27
at Generator.throw ()

16-Mar-2021 16:57:27
at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)

16-Mar-2021 16:57:27
at processTicksAndRejections (node:internal/process/task_queues:94:5)

Kindly let me know once this issue will be resolved as our QA's are blocked due to this

+1 any information would be welcomed. this only started last night

also encountering this, getting invalid token today. Changed the token and then getting error with 'undefined'
even manually uploading via web is no go

Spoken to support (I don't use twitter so I didn't know of this) They are aware of the issue. a symptom is either an invalid token or a 403 error. so we just need to sit tight for now. keep an eye on https://twitter.com/AppCenterStatus?ref_src=twsrc^google|twcamp^serp|twgr^author for more info


WIP No more "Terminate Batch Job? (Y/N)"

Bugfix.
On Windows, existing a Rez context with CTRL+C:

Prompts the user with a "Terminate Batch Job? (Y/N)" question that terminates regardless of the answer; this is standard behavior for batch scripts on Windows, but isn't doing us any favours with Rez.
Throws an exception due to the Windows version of CTRL+C not being handled.

Example
$ rez env python-3 -- python -m http.server
Serving HTTP on <IP_ADDRESS> port 8000 (http://<IP_ADDRESS>:8000/) ...

Keyboard interrupt received, exiting.
Terminate batch job (Y/N)? y
Interrupted by user
Traceback (most recent call last):
  File "c:\Python27\Lib\runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "c:\Python27\Lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\Users\manima\Dropbox\dev\anima\github\nerdvegas\rez_install\Scripts\rez\rez.exe\__main__.py", line 2, in <module>
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\cli\_main.py", line 144, in run
    returncode = run_cmd()
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\cli\_main.py", line 136, in run_cmd
    return opts.func(opts, opts.parser, extra_arg_groups)
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\cli\env.py", line 249, in command
    block=True)
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\resolved_context.py", line 871, in _check
    return fn(self, *nargs, **kwargs)
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\resolved_context.py", line 1269, in execute_shell
    stdout, stderr = p.communicate()
  File "c:\Python27\Lib\subprocess.py", line 476, in communicate
    self.wait()
  File "c:\Python27\Lib\subprocess.py", line 689, in wait
    _subprocess.INFINITE)
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\cli\_util.py", line 148, in sigint_handler
    sigbase_handler(signum, frame)
  File "c:\users\manima\dropbox\dev\anima\github\nerdvegas\rez_install\lib\site-packages\rez-2.29.1-py2.7.egg\rez\cli\_util.py", line 137, in sigbase_handler
    os.killpg(os.getpgid(0), signum)
AttributeError: 'module' object has no attribute 'killpg'

This PR solves that.
$ rez env python-3 -- python -m http.server
Serving HTTP on <IP_ADDRESS> port 8000 (http://<IP_ADDRESS>:8000/) ...

Keyboard interrupt received, exiting.
Interrupted by user
^C
$

Solution
Previously, a rez_shell.bat script was dynamically generated when entering rez env, which was then used as a form of startup-script for the sub-shell.
# Example
$ echo "echo Hello" >> rez_shell.bat
$ echo "echo World" > rez_shell.bat
$ cmd /K rez_shell.bat

With this PR, the sub-shell is handed commands via the /K and /C flag instead.
$ cmd /K echo Hello & echo World

The & operator causes the next command to be called regardless of failure of  the prior command, as opposed to && which is only called on success and || which is called on failure.

It's a rather big change to how contexts work on Windows, so I've added a WIP to the title until I'm confident it works.
Edit: Reworded the solution part, not sure what I was smoking when I first typed that!

This PR also appears to quote arguments being passed in like this:
$ rez env some_package -- echo hello
"hello"

That's bad for e.g. argparse which can't decipher what a given '"/path/to/file"' becomes. Not sure why this happens yet.

I've narrowed down the issue to "shlex_join".
Before A
$ rez env -- c:\python27\python -c "print('hello')"
  File "<string>", line 1
    print(""hello"")

After A
$ rez env -- c:\python27\python -c "print('hello')"
hello

Before B
$ echo import argparse;p = argparse.ArgumentParser();p.add_argument("--test");opts = p.parse_args();print(repr(opts.test)) > test.py
$ rez env python-2 -- c:\Python27\python.exe test.py --test hello
'\"c:\Python27\python.exe\"' is not recognized as an internal or external command,
operable program or batch file.

After B
$ echo import argparse;p = argparse.ArgumentParser();p.add_argument("--test");opts = p.parse_args();print(repr(opts.test)) > test.py
$ rez env python-2 -- c:\Python27\python.exe test.py --test hello
hello

Not sure what the original purpose of this call was, earliest mention I can find doesn't mention it explicitly.

https://github.com/nerdvegas/rez/commit/7f454291fccd0f960345447b87047157ae36edce

I'm still having issues with the tests not passing; @nerdvegas can you help me interpret these errors?

https://ci.appveyor.com/project/mottosso/bleeding-rez/builds/24344285/job/ti892wmw7d7s04ha#L12616

Solved by #627!


Update to Swift 4.2

Hello,
Are you plan to update ActionKit to Swift 4.2?

Sure! I'm happy to accept a pull request if ou want to take the initiative, otherwise I'll likely have time to get to this later this week :)

Please update to pod version 2.4.0 to get Swift 4.2 support! For all those who don't yet want Swift 4.2, please keep using the version you're on, or there's also the swift4 branch :)
Thanks for bringing this up @sglushchenko and please do bring up any other issues you might stumble upon!


Change error checking example in README to not loop callbacks

I tried to use error checking after-callbacks as shown in the main README, but using a glGetError() call in the callback caused it to loop back into the callback. Being new the library, I had no idea why my program became completely unresponsive. After some reading, I found using Binding::GetError.directCall() was the correct way to go.
Maybe the example should be changed so other people don't run into the same issue? Or is this possibly a bug?

Nevermind the accidental close -_-

Also in the "Example for logging:" it should be std::cout << call.function->name() << "("; instead of std::cout << call.function.name() << "(";


[Bug]: Types are not exported for namespaced components

Environment
Developement/Production OS: Windows 11
Node version: 20.10
Package manager: npm 10.2.3
Radix Vue version: 1.4.6
Vue version: 3.4.15
Nuxt version: none
CSS framework: none
Client OS: Windows 11
Browser: Chrome latest

Link to minimal reproduction
Nan
Steps to reproduce
Import a component using namespaced method
Describe the bug

Expected behavior
No response
Context & Screenshots (if applicable)
No response

That's weird. I have been using the namespaced components without issues even today.
Make sure you have installed version 1.2.0 or later, since that's when namespaced components where added.

@ChrisGV04 yep, I have "radix-vue": "^1.4.6". I restarted VScode to make sure it's not caused by TS watcher. Still thte same error

@ChrisGV04 it works if I import it from dist:
import {Dialog} from 'radix-vue/dist/namespaced';

Instead of what's specified in the docs:
import {Dialog} from 'radix-vue/namespaced';

I'm not sure why you can't use radix-vue/namespaced. I have been using it exactly as the docs say since I started using Radix Vue.
Here are some suggestions that I can think of:

I use pnpm instead of npm or yarn. I don't know if this makes a difference.
Try to add a .npmrc file to your project directory with this line: shamefully-hoist=true then delete the node_modules and package-lock file and try to run install again.
Try adding "type": "module" to your package.json and reloading VS Code.

I have that my own project using Radix Vue and it works perfectly

@ChrisGV04 it seems radix-vue/namespaced directory is not exported from index or index.d.ts file of the package.
It seems the problem is with the package types.
I have "type": "module" specified. Probably shouldn't create .npmrc just for one package.
It seems pnpm resolves missing types automatically somehow

Just checked the source code and it does export the namespaced types correctly.
If they weren't exported, it wouldn't work for anyone at all. But it works fine in my case.
I use Nuxt 3, so the .npmrc is actually part of the starter template. I also had it on Vite projects, but I'm not sure if it could affect your app. I suggest you give it a try and revert the changes if it breaks something else

The namespaced types are exported in the node_modules/radix-vue/package.json and can be found at node_modules/radix-vue/dist/namespaced/index.d.ts.

@ChrisGV04 could you please take a look at my tsconfig? Is there anything wrong with it?


release notes for 1.1.0-M1

relates to https://github.com/apache/incubator-pekko/issues/945
it would be good if other contributors could check if any important updates have not been listed

Let's wait until merging since https://github.com/apache/incubator-pekko/pull/981 is on the horizon of being completed

Let's wait until merging since #981 is on the horizon of being completed

We don't typically merge these until after the release is approved. We can link this PR in the vote email.

We don't typically merge these until after the release is approved. We can link this PR in the vote email.

Yes I know, just leaving it here as a note so we don't forget it in the notes

The release vote has passed so I need to get the docs updated as part of the release.

I need to get this merged so that I can announce the release.


fatal: no SASL authentication mechanisms

I got the following error inside the docker container:
Jul 10 10:43:18 1b83c6697007 postfix/smtpd[928]: fatal: no SASL authentication mechanisms
solved it by connection to the container and changed user from "docker" to "postfix" as followed:
chown postfix:postfix /var/spool/postfix/private

ok after restart user is docker again and still working... dont know was the problem was -.-


Breaking behavior in latest release (1.0.1)

A change in the latest release of ddt (#22 included in 1.0.1) has seemingly introduced breaking behavior for wrapped tests expecting a dictionary object when receiving test data, as exemplified below:
test_data.json
{
  "test_name": {
    "arg_one": "test1",
    "arg_two": "test2",
    "arg_three": "test3"
  }
}

Original test code:
@ddt.file_data('test_data.json')
def test_something(inputs):
    arg_one = inputs["arg_one"]
    arg_two = inputs["arg_two"]
    arg_three = inputs["arg_three"]
    # Perform tests here
    pass

New test code:
@ddt.file_data('test_data.json')
def test_something(arg_one, arg_two, arg_three):
    # Perform tests here
    pass

Since this behavior appears to be non-configurable and backward-incompatible, this seems more like a major version change rather than a simple patch.  Can this change be reverted at least for the time being?

Thanks for pointing this out. I didn't realise that was breaking existing behaviour.
I will see how to deal with that. In the meantime, pin your dependency to 1.0.0 if that gets you going, as I'm not sure when I can get some time to revert this.

I've pinned it for now, so that should be enough to keep things rolling.
Thanks @txels !

What's the status of this?

@pradyunsg nothing has been done on this yet. Do you want to take a look?

AFAICT, this behavior shouldn't have changed in a patch-version bump. That was a bad mistake.
Since then, another minor version bump has occurred. I recommend the OP to port their tests now, since it's been a while since this change happened. Currently, some people might be using the newer versions (1.0.1+) and it won't be nice to suddenly break their code, intentionally.
It might be easy to write a decorator that handles both cases seamlessly for OP, if the expected number of arguments is 1 then pass a dictionary, if it's more, pass them as keyword arguments.
PS: I am indeed working on parts of this project. Something along the lines of #29, with some other ideas I have in my head. Once that's done, I would like to see all those changes come out as ddt 2.0.0.

I just wrote this decorator... It should work with Py2/3. It's untested though. You can possibly remove the conditionals in the start of the function if you are going to selectively apply only on your ddt  test functions using the old format. Actually, that makes more sense. Because then you would clearly mark which test would need updating.
def adapt_if_needed(func):
    """ Adapt functions expecting ddt's old argument format to run with the newer one.
    """

    argspec = inspect.getargspec(func)

    # If it catches variable arguments, it's probably fine to ignore it
    if argspec.varargs is not None or argspec.keywords is not None:
        return func

    # Count required arguments
    required_args = len(argspec.args)
    if argspec.defaults:
        required_args -= len(argspec.defaults)

    # If it takes more than one argument, it's probably fine.
    if required_args > 1:
        return func

    # adapt for older version.
    @functools.wraps(func)
    def wrapper(**kwargs):
        func(kwargs)

    return wrapper

In all honesty, looking at PR #22 which is what seems to have caused this issue I would really suggest outright reverting #22 and then just telling people to break down the dictionary themselves. There's nothing stopping them from using a dictionary to manage how many entries they have and splitting it out doesn't really add much code to test.
Though if they really want to keep PR #22's functionality, perhaps it shouldn't be part of unpack but it's own unpack_dict to make that kind of functionality explicit.
@pradyunsg sorry...I'm not really seeing benefit to your proposed migration as it seems lacking in matching up arguments especially due to the assumption that a test that previously worked (as @Kuwagata exemplified) would only have 1 parameter, and thinking it through it would seem to me at least not an easy problem to try to determine how many parameters should be able to be matched up. So making the dict unpacking done via its own specific decorator would seem to be the most logical path. Anyone that has come to rely on the new methodology should be able to migrate easily to using a new decorator, which is what you're asking people that have been using the old methodology to do any way. And my guess is that people using the new method are probably fewer in number than people using the new method.

That sounds good too! Having a special decorator ma

Bump. Could @txels make this change?

I think as it is 2018 and whoever is using the lib now is probably using the newer approach anyway. I'm closing this for now.


Missing calls to "registerWith()" in generated dart_plugin_registrant.dart

1.create a plugin by dartPluginClass
2. create a flutter project
3. compile the app by using cross-build's method
4. open the file .dart_tool/flutter_build/dart_plugin_registrant.dart
5. find the symbol of registerWith in libapp.so
In linux-x64,the symbol of registerWith exists in libapp.so, but in linux-arm64,we can't find the registerWith in libapp.so
the plugin's code look like this:
 plugin:       implements: plugin_platform_template_interface       platforms:         macos:           dartPluginClass: FlutterMacPlugin
the dart_plugin_registrant.dart look like this:
 @pragma('vm:entry-point') class _PluginRegistrant {   @pragma('vm:entry-point')   static void register() {     print('zrzrzrzr register function called!!!!');     if (Platform.isAndroid) {       print("zrzrzrzr platform is android");     } else if (Platform.isIOS) {       print("zrzrzrzr platform is ios");     } else if (Platform.isLinux) {       print("zrzrzrzr platform is Linux");       try {         FlutterLinuxPlugin.registerWith();       } catch (err) {         print(           'flutter_linux_plugin` threw an error: $err. '
'The app may not function as expected until you remove this plugin from pubspec.yaml'
);
}
} else if (Platform.isMacOS) {
  print("zrzrzrzr platform is Macos");
  try {
    FlutterMacPlugin.registerWith();
  } catch (err) {
    print(
      '`flutter_mac_plugin` threw an error: $err. '
      'The app may not function as expected until you remove this plugin from pubspec.yaml'
    );
  }

} else if (Platform.isWindows) {
  print('zrzrzrzr platform is Windows');
}

}
}
`

error


Feature/nft

Detailed description:
Adds specific NFT support to composer - a Hedera file is used to store the token properties immutably
Introduces marketplace for token offers

Adds support for Non Fungible Tokens (NFT), using a Hedera file to hold details about the NFT. The file id is used as a symbol for the token and both the file and token are immutable such that no further changes can be made.
Also enabled a "sort of" market place acting as an escrow for token transfers with an offer price in hBar.

Adds support for Non Fungible Tokens (NFT), using a Hedera file to hold details about the NFT. The file id is used as a symbol for the token and both the file and token are immutable such that no further changes can be made.
Also enabled a "sort of" market place acting as an escrow for token transfers with an offer price in hBar.


[chip-test] chip_usb_enumeration

Test point name
chip_usb_enumeration
Host side component
SystemVerilog+Rust
OpenTitanTool infrastructure implemented
No
Contact person
@a-will
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[x] Device-side (C) component developed
[x] Bazel build rules developed
[x] Host-side component developed
[x] HJSON test plan updated with test name (so it shows up in the dashboard)
[x] Test added to dvsim nightly regression (and passing at time of checking)

@alees24 (a new starter at lowRISC) is taking a look at USB device TLT, I've put him in planned assignee for now as he's ramping up currently rather than actively working on any particular test.

Covered by numerous TLTs.


Add Microsoft.CSharp and Microsoft.VisualBasic

Add sources for Microsoft.CSharp and Microsoft.VisualBasic.
Ran Policheck, removed aliases, checked copyright headers. (usual publishing process does not work for VB files)
@rbhanda @richlander @jaredpar

@rbhanda @richlander ? I do not have write access to merge.

BTW @rbhanda as you know, as configured currently, your reference source tool will not update these two folders. I think that's totally fine, but it's important that the next update doesn't remove them either -- I assume that won't happen.


Remove Trajectory.to_state method

Blocked by #325
As part of addressing #321, this refactoring PR removes the last remaining Trajectory method, to_state(), and moves it temporarily to a function _trajectory_to_state in chirho.dynamical.internals._utils.

Base branch should be changed back to staging-dynamic after #325 lands


Add mix2sequences

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

Files
Coverage Δ

src/startorch/timeseries/utils/__init__.py
100.00% <100.00%> (ø)

src/startorch/timeseries/utils/mixed.py
100.00% <100.00%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.


How  to mark variable $filter_published_at  as invalid ?

If there is a way with larastan 2.6 in laravel 10 to mark variable
$filter_published_at
as invalid, but
$filterPublishedAt
as valid ?

you should use phpcs for this kind of rule rather than larastan, as phpcs is more interested in formatting / style:
https://github.com/squizlabs/PHP_CodeSniffer
https://stackoverflow.com/questions/45530721/what-sniff-needs-to-be-used-to-enforce-a-camelcase-variable-naming-convention


Normalisation experiment

What?
Ripper has a lot of ways it can represent method calls. They include:

method_add_arg, for any call with parens
command, for a bare method call without parens
command_call, for dotted method call without parens
call, for a dotted method call without parens or arguments
vcall, for a bare method call without parens or arguments

There are also some very method-call-like things, where the same formatting
rules probably ought to apply. They are:

zsuper, for super with no arguments
super, for super with arguments, or with empty parens
yield
return

This commit normalises these s-expressions into the following structure
before formatting them:
[
  :method_call,
  receiving_object,
  method_name,
  original_used_parens,
  arguments,
]

Where:

receiving_object is an array of expressions, which can be concatenated
to produce the receiving object. This could include operators like .,
&., or ::.

method_name is an expression representing the name of the method.

original_used_parens is a boolean, indicating if the original source
code used parens. This is useful for super calls, where empty parens
change the semantics.

arguments is an array or expressions representing the arguments.

To simplify further, a few other s-expressions are also modified. In the
receiving_object array:

Operators are represented as [:dot, expression_or_symbol]. This fits
neatly with the existing #format_dot method.

Call-like things are represented as [:keyword, keyword], e.g. [:keyword, "return"].

And in the arguments array:

Splats are represented as [:spat, expression] where expression is
the splatted argument.

Blocks passed as params are represented as [:to_proc, expression]
where expression is the block argument.

Now that these cases are all handled consistently, some fixtures have
necessarily changed to make sure they're consistent with each other.
Why?
When a subtle change to the formatting of a method call (e.g. the addition
or parentheses) could change the s-expression representation of the
expression (e.g. from a command to a method_add_arg), and therefore
change the code path followed by rubyfmt, it was easy for differences
between formatting to creep in
There are a couple of reasons this matters:

We want rubyfmt to be idempotent, i.e. running a file through it many
times should produce the same output as running it through once.
Maintaining that property while formatting the same kind of thing in
multiple places would be difficult.

We're likely to go back-and-forth on what the output should look like.
This means a single place to make changes to method calls and other
call-like structures will be beneficial.

Hmm, this breaks the RSpec stress test, so definitely not ready to merge!

how does this work in the case that a call receiver is like
(Foo::Bar::(nil.object_id)).bees(1)

how does this work in the case that a call receiver is like
(Foo::Bar::(nil.object_id)).bees(1)

I'd completely forgotten about the foo::() shorthand. Fixed in abd5d3f.

@georgebrock  please rebase against master, which now has RSpec ci

I was wondering if the normalisation logic doesn’t belong in the Parser class, e.g. by implementing an #on_command method instead of the #normalize_command method? And would that even be possible to implement?

@bquorning Good question! I suspect the code might be less clear if we did it using parser events, for two reasons:

The current separation makes normalisation a clearly separate thing from either parsing or formatting. If it was mixed in with parsing or with formatting, it could be harder to figure out what's what. Currently the custom code we have in the parser is all concerned with getting at information Ripper doesn't provide by default (e.g. unescaped string values).

I think an event-driven approach would mean maintaining more state, which could make it harder to debug the normalisation code because we'd have to consider not only the current event but also the state that previous events have put us in.

I haven't worked with Ripper a whole lot (my commits in this project are it), so I could be making the wrong assumptions.

Green tests!
The failure was coming from this expression: require(path_for(formatter_ref)) ? retry : raise
I'd made “no parens on require” too broad. I think there's a thing to figure out about what the rules for using parens should really be in practice, but at least this no longer changes the semantics of RSpec Core.

Ah, got it. I had misread the code and didn’t see it was a separate step.
Would having e.g. a Formatter and a Normalizer class (or module) make the code clearer? It’s a bit confusing having every method defined without a namespace. (Probably only a Normalizer class would be within the scope of this PR)..

@georgebrock I need to revisit where we should have parens and shouldn't. Could you build an example ala string_literals_stress_test.rb with as many variants as you can think of with md5 puts output based verification?

@georgebrock my intent is to merge this once CI is green.


TOOLPREFIX incorrectly applies to sh

Expected behavior
When building on OSX, using TOOLPREFIX, we should use the system sh binary.
Actual behavior
util/build applied the TOOLPREFIX to sh, and since no x86_64-elf-sh exists the build fails
Steps to reproduce
On OSX:
export TOOLPREFIX=x86_64-elf-
./util/build
2016/05/29 13:49:23 exec: "x86_64-elf-sh": executable file not found in $PATH
QEMU output
N/A
A workaround is to symlink /bin/sh to x86_64-elf-sh somewhere on your path

thanks for the report. If you can manage with this workaround we can limp along until we get the new build tool, hopefully in june, that's much better.

Its already 2017

Yes, but bldy is not ready at all. Sorry for inconvenience.

Isn't this fixed now?

fixed


Let a string analysis input be a dataset

partial overlap with #61

Could this  be related to strings not being displayable through the Visualiation tab anymore?

Strings can now be displayed through the vis tab due to https://github.com/Kitware/tangelohub/pull/146


TUI frames are broken when used in zellij

What system are you running Yazi on?
Windows WSL
What terminal are you running Yazi in?
alacritty 0.13.2
yazi --debug output
Yazi
    Version: 0.3.1 (Nixpkgs 2024-08-18)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.1 (Nixpkgs 2024-08-18)

Emulator
    Emulator.via_env: ("xterm-256color", "")
    Emulator.via_csi: Ok(Unknown([Sixel]))
    Emulator.detect : Unknown([Sixel])

Adapter
    Adapter.matches: Sixel

Desktop
    XDG_SESSION_TYPE: None
    WAYLAND_DISPLAY : Some("wayland-0")
    DISPLAY         : Some(":0")

SSH
    shared.in_ssh_connection: false

WSL
    /proc/sys/fs/binfmt_misc/WSLInterop: true

Variables
    SHELL              : Some("/home/valentin/.nix-profile/bin/zsh")
    EDITOR             : Some("hx")
    VISUAL             : None
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None

Text Opener
    default: Some(Opener { run: "yz-fp \"$0\"", block: false, orphan: false, desc: "Use yazi as file picker within helix", for_: None, spread: false })
    block  : None

Multiplexers
    TMUX               : false
    tmux version       : tmux 3.2a
    ZELLIJ_SESSION_NAME: Some("circular-glockenspiel")
    Zellij version     : 0.40.1

Dependencies
    file             : 5.41
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: No such file or directory (os error 2)
    magick           : No such file or directory (os error 2)
    fzf              : 0.54.3
    fd               : 10.1.0
    rg               : 14.1.0
    chafa            : No such file or directory (os error 2)
    zoxide           : 0.9.4
    7z               : No such file or directory (os error 2)
    7zz              : No such file or directory (os error 2)
    jq               : No such file or directory (os error 2)

--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/home/valentin/.local/state/yazi" directory.

Did you try the latest nightly build to see if the problem got fixed?
Yes, and I updated the debug information above (yazi --debug) to the nightly that I tried
Describe the bug
Frames display is broken when used inside zellij 0.40.1

Minimal reproducer
I'm using the 'JetBrainsMono Nerd Font' font.
$ zellij
$ yazi

Anything else?
No response

This is a rendering error, please submit it to Zellij so their devs can investigate further, as we've received another report similar to this one https://github.com/sxyazi/yazi/issues/1149, although this is actually a terminal emulator bug, not a terminal multiplexer, but they function in the same way.

My bad, it happens also outside of zellij:

To do this, I opened yazi while the terminal window was full-screen, then resized the terminal window down.

Can you re-open @sxyazi ?

Submitted to alacritty https://github.com/alacritty/alacritty/issues/8136

This would point to alacritty being the culprit it seems. Can you confirm?

I found these two issues, and it looks like they might also be related to ConPTY:

https://github.com/alacritty/alacritty/issues/7758
https://github.com/alacritty/alacritty/issues/7914

According to this comment, unlike WezTerm, Alacritty doesn't include the latest conpty.dll with each release but instead uses the system's default. So, you can try downloading and installing WezTerm to see if Alacritty will use the latest DLL to fix the issue, or you could try upgrading your system

I confirm that installing wezterm fixed the issue in alacritty!


Added an animation to fade the gray background in MaterialRippleGestureRecognizer for iOS after 1.5 seconds

Apparently the TapGestureRecognizer for iOS times out if the user holds the tap for an estimated more than 1.5 seconds. When that happens, none of the TouchesEnded, TouchesMoved, TouchesCancelled events are triggered for us to fade the gray background out. So this animation chain will ensure that the background will be faded out.

Hi. There are conflicting files in this PR. I already merged the first PR. Please update you source branch from dev and resolve the conflicts.

Hi,
Not too familiar with the merge and stuff, so I wasn't sure what you meant by updating my source branch 'dev'.
I just manually resolved the conflicts, will that work too?

Yeah, that's what I meant. Anyway, conflicts has been resolved and I can accept this PR now.


yarn run build:production: Hash issues

When running yarn run build:production the resulting files in dist got hashes in their file names.
@icon isn't able to load them anymore because it cannot find the file by its normal file name (without hash).

Added a parse_asset_path helper you can use when defining an asset path to hopefully grab the absolute path of the image from your manifest.

@Log1x: Thank you for this addition! It would be great if there is a some extra documentation about how to add parse_asset_path(...) for making it work with build:production.

Is there a documentation for parse_asset_path() helper how to use it? Thanks!

This would've been very legacy and doesn't exist anymore.
If you're using Sage 10, you will want to use https://github.com/Log1x/sage-svg or https://blade-ui-kit.com/blade-icons

Oh right, yeah, I've been using sage-svg.
I had a similar production issue which I thought was related to hash thing ( and this thread popped up and I didn't double check the library name ) but it turned out my issue was caused by filename case mismatching. Production build hash didn't really matter as it rendered SVGs inline.
Thank you for your reply and reminding!


adds JSON.MSET implementation

adds JSON.MSET implementation

I think we also need to check to all the values using prepareSetValues and the path and the values before setting anyone of them


Allow to search plugin from multiple prefix directory

Allow to search plugin from multiple prefix directory.
Related with issue #1131 (v0.14 doesn't load plugins from directory specified by "-p" option)

With this change, Fluentd seems to load all in_*.rb files from anywhere possible. Is it correct and intentional?
Fluentd should load plugins from directory specified by -p DIR (primal), or gems which have paths like fluent/plugin/in_*.rb.

No. It's not intentional. Thanks for mention it.
It seems to we need two rule of plugin search prefix.

for specified directory (not have paths like fluent/plugin/in_*.rb)
for gems

This is working as we expect. but not looks good to me.
Do you have an idea to improve this?

Current your implementation is breaking code compatibility of Registry class. It might be used by any 3rd party plugins. It can't be merged.

My idea is to add optional keyword argument (like file_prefix or some better name) to be used only for @paths, earlier than @search_prefix.

@tagomoris
Sorry for breaking change. actually, I didn't realize Registry is opened to 3rd party plugins. Thanks for mention it.
How about this one? https://github.com/HatsuneMiku3939/fluentd/commit/d57576af199b3171d190263caa67ef3a3c9c821d

@HatsuneMiku3939 it looks good to me!

@tagomoris
Thanks!

LGTM


junit 5?

Description
https://blog.jetbrains.com/idea/2020/08/migrating-from-junit-4-to-junit-5/ works well enough on a bunch of unit tests
The integration tests are more of pain since they all almost use system rules and system rules is also dead along with powermock.
Review Instructions
Should see an equal number of tests running before and after merge
Issue
https://github.com/dockstore/dockstore/issues/5284
Security
none
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that you pass the basic style checks and unit tests by running mvn clean install
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[ ] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[ ] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[ ] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[ ] Do not serve user-uploaded binary images through the Dockstore API
[ ] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[ ] Do not create cookies, although this may change in the future
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

huh


pymongo.errors.OperationFailure: exception: distinct too big, 16mb cap

Pretty sure https://github.com/gunthercox/ChatterBot/issues/925 will address this but just wanted to give you a heads up.
  File "bot.py", line 87, in <module>
    bot_input = chatterbot.get_response(None)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/chatterbot.py", line 110, in get_response
    statement, response = self.generate_response(input_statement, session_id)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/chatterbot.py", line 130, in generate_response
    response = self.logic.process(input_statement)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/logic/multi_adapter.py", line 52, in process
    output = adapter.process(statement)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/logic/best_match.py", line 54, in process
    closest_match = self.get(input_statement)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/logic/best_match.py", line 16, in get
    statement_list = self.chatbot.storage.get_response_statements()
  File "/home/ubuntu/.local/lib/python2.7/site-packages/chatterbot/storage/mongodb.py", line 275, in get_response_statements
    response_query = self.statements.distinct('in_response_to.text')
  File "/home/ubuntu/.local/lib/python2.7/site-packages/pymongo/collection.py", line 2062, in distinct
    collation=collation)["values"]
  File "/home/ubuntu/.local/lib/python2.7/site-packages/pymongo/collection.py", line 232, in _command
    collation=collation)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/pymongo/pool.py", line 477, in command
    collation=collation)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/pymongo/network.py", line 116, in command
    parse_write_concern_error=parse_write_concern_error)
  File "/home/ubuntu/.local/lib/python2.7/site-packages/pymongo/helpers.py", line 210, in _check_command_response
    raise OperationFailure(msg % errmsg, code, response)
pymongo.errors.OperationFailure: exception: distinct too big, 16mb cap

https://docs.mongodb.com/manual/core/gridfs/


How configure Redis Sentinel

Can you tell me how to configure the Redis Sentinel correctly?
My setting:
sb_redis.yaml
sb_redis:
    clients:
        default:
            $options:    []
            $parameters: ['%env(REDIS_URL)%']
or

sb_redis:
    clients:
        default:
            $options: [replication : sentinel, service : platform-common-develop]
            $parameters: ['%env(REDIS_SENTINEL_URL)%']

.env
REDIS_URL=redis://main-develop-redis:26379?redis_sentinel=platform-main-develop&dbindex=0&replication=sentinel&service=platform-main-develop&database=0

But a have exeption:
    "type": "https://tools.ietf.org/html/rfc2616#section-10",
    "title": "An error occurred",
    "status": 500,
    "detail": "`SELECT` failed: ERR unknown command `SELECT`, with args beginning with: `0`,  [redis://platform-main-develop-redis:26379]",
    "class": "Predis\\Connection\\ConnectionException",

Hi, Yozhef!
See issue https://github.com/nrk/predis/issues/355, I hope this helps you.

@khaperets Sorry but that didn't help me with the problem. I don't understand how to properly transfer configurations from Symfony-bundle to Predis Client. Do you have any idea?

Hi @khaperets.
Does redis sentinel supported?
Due to predis documentation there has to be field $sentinels and no $parameters
$sentinels = ['tcp://<IP_ADDRESS>', 'tcp://<IP_ADDRESS>', 'tcp://<IP_ADDRESS>'];
$options   = ['replication' => 'sentinel', 'service' => 'mymaster'];

$client = new Predis\Client($sentinels, $options);

Thank you all worked it was necessary to add 2 parameters correctly.
sb_redis:
    clients:
        default:
            $options:
                replication: sentinel
                service: platform-common-develop
                parameters:
                    database: 0
            $parameters: ['%env(REDIS_URL)%', '%env(REDIS_URL)%']


IEChooser debugging in VSC

Is your feature request related to a problem? Please describe.
To debug some applications, it is necessary to use IEChooser.exe (%windir%\SysWOW64\F12\IEChooser.exe), which is not as a nice environment to work in as visual studio code
Describe the solution you'd like:
I would like to be able to debug said applications in visual studio code, with all the tools it brings, using this extension (or any that can do this, really)
Describe alternatives you've considered:
Keep using IEChooser, due to a lack of other alternatives that I'm aware of
Additional context:
N/A

Pinging @bwalderman on this issue as I think he can advise on this.
My understanding is that if the app you're debugging needs IEChooser, then that means it's running on the IE browser engine, not the Edge one.
The newer DevTools only work with Edge unfortunately. The APIs that DevTools requires to work simply do not exist in IE, only in Edge. So I don't think what you're asking is technical feasible without a really big adaption project to map the IE APIs to the Edge ones.

To my understanding of this tool (F12, IEChooser), it is Edge in legacy mode, not IE, if it helps

My understanding is that if the app you're debugging needs IEChooser, then that means it's running on the IE browser engine, not the Edge one.

That's correct. If you are debugging an application with IEChooser, then that application is using the IE engine. This is also true if your application is running in Edge in IE Mode. IEChooser continues to be the recommended approach for debugging these apps. VSCode Edge DevTools is fundamentally incompatible with the IE engine.

I understand, thank you for the insight!


Allow searching by date range (since: and until:)

Is your feature request related to a problem? Please describe.
Bluesky doesn't allow searching or filtering posts by date range.
Describe the solution you'd like
Search operators that allow returning results from a date range.
To return all posts containing football since 2 Jan 2023:
football since:2023-01-02

Posts before 2 Jan 2023:
football until:2023-01-02

These operators can be combined to select a date range, and combined with any other search operators to further filter results.
football since:2023-01-02 until:20203-06-02

Describe alternatives you've considered
Can't find any.
Additional context
This is a request for feature parity with other similar social posting services; see also https://github.com/bluesky-social/social-app/issues/1143, https://github.com/bluesky-social/social-app/issues/849, #1522.

This appears to be implemented. I can't pinpoint what implemented it, but I found bluesky-social/indigo/pull/643 and it's documented in a May 2024 blog post: https://bsky.social/about/blog/05-31-2024-search
I can't find any mention of these search operators in the public social app docs.

#4093 proposes a way to document these in-app.


Fix doc links to avoid warning on nightly

Hi there!

one link was just a typo (incorrect ::*)
the other one was a wrong intra-link (which are still unstable)

I converted the wrong intra-link to a normal one for now. Would be awesome if this can be merged, as cargo doc is quite noisy on nightly when you have many dependencies :)

Thanks!
bors r+


Project Page Stable Baselines3

Hello,
nice project =)
We would be interested if you could do a pull request on stable-baselines3 where you add your project to the documentation (project section) ;)

Wow! Thanks for your recognition. That's my great pleasure!

Merci =)


Remove drop-down menus for subheadings, in left panel

They are picking up level 2, 3, etc subheadings. Would rather have no drop-downs here.

Changed my mind - looks ok.