mesa: Don't fail to build when d3d isn't built

Motivation for this change
d3d.pc isn't necessarily there depending on how you build mesa. The postFixup script depends on it
being there since https://github.com/NixOS/nixpkgs/commit/acbfd3f7c09e4df7300261d85edf586c8a5028af.
Things done
I changed the script to check for existence of the files, or not err when something fails.

[ ] 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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

But the point is that it might be missing. It's missing with the settings I use.
---元のメッセージ---
　 2021年4月30日 1:48, Sandroに が送信

@SuperSandro2000 commented on this pull request.

In pkgs/development/libraries/mesa/default.nix:

 # remove pkgconfig files for GL/EGL; they are provided by libGL.
 rm -f $dev/lib/pkgconfig/{gl,egl}.pc

 # Move development files for libraries in $drivers to $driversdev
 mkdir -p $driversdev/include

mv $dev/include/xa_* $dev/include/d3d* $driversdev/include

mv $dev/include/xa_* $dev/include/d3d* -t $driversdev/include || true

I think using a condition here would be better otherwise we might miss if $dev/include/xa_* is missing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm going to merge this as it fixes a "regression" from https://github.com/NixOS/nixpkgs/commit/acbfd3f7c09e4df7300261d85edf586c8a5028af and it's out of scope of this PR to fix/refactor our post{Install,Fixup} mess.


Enhancement : Force Directed Map Layouts

Force Directed maps are a (relatively) simple way to provide an automatic layout for maps that avoid overlaps etc.
Something like getspringy ...  http://getspringy.com/

Seems that jsPlumb implements a Force Directed layout as well ... https://jsplumbtoolkit.com/docs/toolkit/demo-spring.html#adding

Yeah this is from the "Tookit Edition" which costs about $2500,.... https://jsplumbtoolkit.com/download
I use the "Community Edition" (free) with some custom plugins.
We could use the "magnetize" feature for this (with some modifications). I have implemented this  for testing (some month ago) and can be activated on the "maps menu".
This is not a "top priority" feature request, more a "nice to have" feature....

Can I add a vote for this. Coming from another mapping tool (eve-wspace) it is surprising how being able to freely place the systems adds confusion. Turning on magnetising helps a bit with the initial placement but it would be nice to force a rows and columns system in some way.

I wrote an algorithm for jsplumb that forces a treeview layout if you would like to modify it, let me know and I can throw it into a gist. It isn't perfect, but it is pretty decent for what it does.


duplicate class names crash the build

@paulodamaso/z please, pay attention to this issue

@rultor release, tag is 0.30.3

@rultor release, tag is 0.30.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.30.3

@yegor256 Oops, I failed. You can see the full log here (spent 2hr)
13 XML reports created in 36s
13 XML reports created in 36s
BUILD org.jpeek.App: Matrix generated with 13 metrics
Matrix generated with 13 metrics
Matrix generated with 13 metrics
BUILD org.jpeek.DefaultBase: Found 512 files in .
BUILD org.jpeek.skeleton.Classes: 64 classes found and parsed via Javassist in 153ms
BUILD org.jpeek.skeleton.Skeleton: 4 classes parsed via ASM in 381ms
BUILD org.jpeek.skeleton.Skeleton: 64 bytecode classes parsed in 1s (21ms per class)
BUILD org.jpeek.App: Constructors will be ignored
BUILD org.jpeek.App: Static methods will be ignored
BUILD org.jpeek.App: Private methods will be ignored
BUILD org.jpeek.Report: LCOM2.xml generated in 4s
LCOM2.xml generated in 4s
LCOM2.xml generated in 4s
BUILD org.jpeek.Report: MWE.xml generated in 4s
MWE.xml generated in 4s
MWE.xml generated in 4s
BUILD org.jpeek.Report: TCC.xml generated in 5s
TCC.xml generated in 5s
TCC.xml generated in 5s
BUILD org.jpeek.Report: CCM.xml generated in 5s
CCM.xml generated in 5s
CCM.xml generated in 5s
BUILD org.jpeek.Report: LCOM3.xml generated in 5s
LCOM3.xml generated in 5s
LCOM3.xml generated in 5s
BUILD org.jpeek.Report: LCC.xml generated in 5s
LCC.xml generated in 5s
LCC.xml generated in 5s
BUILD org.jpeek.Report: SCOM.xml generated in 5s
SCOM.xml generated in 5s
SCOM.xml generated in 5s
BUILD org.jpeek.Report: OCC.xml generated in 5s
OCC.xml generated in 5s
OCC.xml generated in 5s
BUILD org.jpeek.Report: PCC.xml generated in 5s
PCC.xml generated in 5s
PCC.xml generated in 5s
BUILD org.jpeek.Report: NHD.xml generated in 5s
NHD.xml generated in 5s
NHD.xml generated in 5s
BUILD org.jpeek.Report: LCOM.xml generated in 5s
LCOM.xml generated in 5s
LCOM.xml generated in 5s
BUILD org.jpeek.Report: MMAC.xml generated in 5s
MMAC.xml generated in 5s
MMAC.xml generated in 5s
BUILD org.jpeek.Report: LCOM5.xml generated in 5s
LCOM5.xml generated in 5s
LCOM5.xml generated in 5s
BUILD org.jpeek.App: 13 XML reports created in 37s
13 XML reports created in 37s
13 XML reports created in 37s
BUILD org.jpeek.App: Matrix generated with 13 metrics
Matrix generated with 13 metrics
Matrix generated with 13 metrics
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.505 sec - in org.jpeek.IndexTest
cdada9ea23a49cc7d18c75ca3237da0aef368ac1ef08275a6827664606cf09b8
'pid' file is absent, something was broken

@rultor release, tag is 0.30.3

@rultor release, tag is 0.30.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.30.3

@yegor256 Oops, I failed. You can see the full log here (spent 16min)
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.30.3/jpeek-0.30.3-javadoc.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.30.3/jpeek-0.30.3.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.30.3/jpeek-0.30.3-sources.jar'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.30.3/jpeek-0.30.3.pom'
[ERROR]     * Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/org/jpeek/jpeek/0.30.3/jpeek-0.30.3-jar-with-dependencies.jar'
[ERROR]
[ERROR]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:43 min
[INFO] Finished at: 2019-12-07T18:36:56+00:00
[INFO] Final Memory: 114M/689M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:release (jcabi-deploy-to-sonatype) on project jpeek: Could not perform action: there are failing staging rules! Staging rules failure! -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:release (jcabi-deploy-to-sonatype) on project jpeek: Could not perform action: there are failing staging rules!
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not perform action: there are failing staging rules!
	at org.sonatype.nexus.maven.staging.workflow.AbstractStagingActionMojo.execute(AbstractStagingActionMojo.java:65)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 20 more
Caused by: com.sonatype.nexus.staging.client.StagingRuleFailuresException: Staging rules failure!
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV3ServiceImpl.monitorRepositoryTransition(StagingWorkflowV3ServiceImpl.java:272)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl.monitorRepositoryTransition(StagingWorkflowV2ServiceImpl.java:407)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl$10.perform(StagingWorkflowV2ServiceImpl.java:281)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl$10.perform(StagingWorkflowV2ServiceImpl.java:276)
	at com.sonatype.nexus.staging.client.internal.ExceptionConverter.runAndReturn(ExceptionConverter.java:38)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV2ServiceImpl.releaseStagingRepositories(StagingWorkflowV2ServiceImpl.java:275)
	at com.sonatype.nexus.staging.client.internal.StagingWorkflowV3ServiceImpl.releaseStagingRepositories(StagingWorkflowV3ServiceImpl.java:91)
	at org.sonatype.nexus.maven.staging.workflow.ReleaseStageRepositoryMojo.doExecute(ReleaseStageRepositoryMojo.java:55)
	at org.sonatype.nexus.maven.staging.workflow.AbstractStagingActionMojo.execute(AbstractStagingActionMojo.java:55)
	... 22 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
container de8c6e8aa1dc2b8f718b232c0610be4b23bbcd6c0dce5f50a7c57e546d7822a1 is dead
Sat Dec  7 19:37:14 CET 2019

@rultor release, tag is 0.30.4

@rultor release, tag is 0.30.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.30.4

@yegor256 Done! FYI, the full log is here (took me 23min)

Job gh:yegor256/jpeek#362 is not assigned, can't get performer

This job is not in scope


[tests] Install node+npm on CI build machines

This is needed for Aspire.Hosting.Tests.Node.NodeFunctionalTests.VerifyNodeAppWorks, which started running with https://github.com/dotnet/aspire/pull/4500/ .
fail: Aspire.Hosting.Dcp.dcpctrl.ExecutableReconciler[0]
      failed to start a process	{"Executable": {"name":"npmapp_598acd4d"}, "Reconciliation": 3, "error": "exec: \"npm\": executable file not found in $PATH"}
fail: Aspire.Hosting.Dcp.dcpctrl.ExecutableReconciler[0]
      failed to start Executable	{"Executable": {"name":"npmapp_598acd4d"}, "Reconciliation": 3, "error": "exec: \"npm\": executable file not found in $PATH"}

Linux: npm is missing
Windows: npm, and node are missing
cc @RussKie @joperezr

@ReubenBond In such tests we should detect when node/npm did not start and fail the test with a corresponding error. What would be needed for that?

Opened https://github.com/dotnet/dnceng/issues/3091 .


Selecting and Moving a group of Tiles erases the Selection both in the origin and the destination

Godot version
v4.0.rc2.official [d2699dc7a]
System information
Windows 10
Issue description
Instead of moving a selection of tiles, both the tiles in the destination (When you release the selection while moving it) and the tiles you had selected dissapear, making it look like it's an erasing selection despite not having the Eraser enabled.
https://user-images.githubusercontent.com/25066388/219513252-9a255bf2-f8a4-4eb0-aac7-f8416201355c.mp4
What I expect it to do is to place the original selection of tiles in the destination.
Steps to reproduce

Create a Tilemap Node.
Add a new Tileset in its Inspector.
Drop a Tileset on the TileSet tab.
Go back to the TileMap tab.
Paint some tiles.
Select some tiles.
Move the Selection over other tiles.
Both the selection and the other tiles are gone.

https://user-images.githubusercontent.com/25066388/219514953-eb841048-25f6-4456-952a-c42bef4745e0.mp4
Minimal reproduction project
I'm attaching it with a free tileset since the one shown in the videos is licensed but the behavior is the same.
tile_map.zip

I'm having exactly the same issue.
I want to add that trying to create a Pattern by Drag/Drop this way also crashes Godot. No log is created.


Sync unregistered nodes on vsphere with kubernetes nodes

Currently the getNodes method in vsphere manager fetch VM IDs from the tag resource (looks like vm-206), this needs to be fixed to pull VM UUIDs somehow, which are reflected in each Node providerID spec.
By fixing this, the autoscaler would be able to sync unregistered nodes because the VM IDs fetched through Nodes() int NodeGroup (which internally calls vsphere manager's getNodes) will be the same.
Ref: https://github.com/jk8s/autoscaler/blob/vsphere-cloudprovider/cluster-autoscaler/cloudprovider/vsphere/vsphere_manager.go#L128

fixed in: https://github.com/jk8s/autoscaler/commit/65113ed7b833ae24a445f0d906ebcf601bd65f3e


Whoops - you're missing the repositories table. See this section of step 2: https://www.carbondesignsystem.com/tutorial/react-step-2#build-repo-page

No updates in 90 days. Closing.


Adding "-n " at the start of the pasted line

Hi!
After I do V y p or dd p the plugin inserts "-n " at the start of the pasted line when copy_sync is enabled.

Hi,
ty for the heads up. I will look into it asap. Probably in the next 2-3 days. Have to finish an article first. Thus, please bear with me :D
Kind regards
Alexander

I was using neovim 0.6.0. After installing 0.5.0 it is working properly!

No problem Alex! Take your time :}

Should work now. Plz give me a heads up, if you get any trouble.
Kind regards


When Kyma resource is under deletion let module's CR know about that

Description
This is an additional feature for modules being deleted by the Lifecycle Manager. The LM should mark module CR with the label before calling the delete operation.
Reason
Some modules could want to act like "force-delete" when de-provisioning comes from Kyma deletion. For example, BTP Manager will delete all instances and bindings in such a scenario.
This is an optional functionality for module owners. The module does not need to react to that.
Proposal

Mark all modules with the standard known label, or

Allow the module owner to define a label name for LM that will be used then

AC

[ ] 1) Document and implement the above feature

We have internally analysed the issue and come to the following conclusions / recommendations based on the use case:
We assume that we wait for all modules to be removed and block the kyma deletion with a finaliser until the (optionally given) timeout is reached. This will not change.
It assumes triggering a Delete of the kyma with kubectl delete kyma NAME --cascade='foreground' and blocking. Alternatively, one can use kubectl delete kyma NAMand we will usebackground` cascading policy, which will require a regular check of the resource for it being already deleted. If it is gone, the deletion was successful.
After the timeout is reached (via kubectl through --timeout=30s), if not all resources are removed, one has to either manually check the Manifest Custom Resource and then decide wether finaliser removal is acceptable or not: if finaliser removal is acceptable, one can force-remove the finaliser which triggers an immediate removal of the Module from the Tracking.
In any case, as soon as the Kyma resource is triggered for deletion, modules will be notified by having their deletionTimestamp set as well, to which controllers can react. The default behaviour here MUST block by not removing a finaliser until all dependencies created by the CustomResource are removed without exception to comply with Kubernetes standards.
If the module should not wait for dependencies (e.g. to keep externally created instances), we recommend to rethink your strategy. Usually this should be done only if triggered with a deletionPropagationPolicy of orphan. Every other value should be respected as is.
For your concrete use case we recommend to

Always remove all services / instances created through the CR by blocking with a finaliser and listening for the deletionTimestamp
Document scenarios in which the finaliser can get stuck and how to deal with these scenarios
Do not introduce specific logic for deletion cases, instead implement only this strategy that removes all dependant objects.
If the cluster is completely uninstalled (kyma CR is triggered for deletion), act as if it were a normal deletion of the module and cleanup all instances created by your CR.
If you have a use case where you want to keep your third-party resources after the CR that triggered their creation was deleted, introduce your own .spec policy for this, e.g. CleanupPolicy with values Orphan and Foreground to map it to the correct Kubernetes primitive. This is strongly discouraged if not absolutely necessary. Instruct your users on how to use this Policy for non-default behaviour. Initialise the Policy in the default data for the Module if necessary.

If the module needs to be aware of when the Kyma resource cleans up the entire cluster (e.g. for different code paths), lifecycle manager should not introduce a custom label on our controller as it makes it implementation specific how controllers can react.

@jakobmoellersap Just to make sure I understand it correctly.
You mean that:

if Kyma CR is under deletion, or
user removed the module from Kyma CR

Then LM will act the same, which means adding deletionTimestamp to module CR, right? If yes, I think it doesn't help.
What we want to achieve is the following, (two scenarios):

User disables btp opertor module in the kyma resource, then btp manager will check if any ServiceInstance(SI), ServiceBindings(SB) CRs exists. If yes, the user must delete them. When no single SI/SB then module CR is gone.
KEB calls deletion on Kyma resource. Then in this scenario btp manager removes ServiceInstance(SI), ServiceBindings(SB) on its own. It always will result in no SI/SB and then module CR is gone.

Please let me know how from your conclusions / recommendations we can implement that.

@jakobmoellersap We need a way to free up resources quickly when when user decides to dispose cluster by deleting Kyma service instance through KEB.  Unfortunately, if we do not clean up resources from the cluster shoot deletion will stuck (see: https://github.com/gardener/gardener/issues/3110). It is not acceptable to charge user for the cluster  that cannot be used therefore it is our cost. The issue is not about rsources created by module operators. It is about resources created by users using CRDs introduced by modules. These resources should not be deleted by the operator (user should delete them). The problem is that user instead of deleting all these resources decided to dispose entire cluster (or even deleted subaccount where cluster is created) and expects that all the resources created there will be soon gone.
@PK85 proposed the strategy where you delegate such clean up to modules. But maybe it doesn't make sense as user can install some resources that are not related to any module and deletion can stuck anyway. So probably it would be better to activate forceful clean up anyway (after some timeout).

We've decided to introduce another controller in the LM to force-remove all the resources and their finalizers from the cluster upon deletion (with a set timeout). It should be later moved to the Infrastructure Operators.
As for the modules we should still decide on the implementation, the options are Kubernetes-native way with orphan finalizers deletion or some sort of custom label-based logic.
Suggestion: modules should by default use the cascade delete, for the ones that would need to keep their children some sort of field/label could be introduced to prevent the user-created resources from being removed.
There would be two options for modules:

force delete off: default in the KCP scenario, keep the resources and block the deletion until the customer removes all the children resources
force delete on: remove all the children resources instantly

Issues to be created:

Implementation of the controller in the LM
E2E test for the deletion scenario
Introduce the modes for the module deletion
Moving to the Infrastructure Operator

Closing this issue in favour of the ones mentioned above


feat(#162): final recipes for composing found metadata into final CSV

In this pull I've implemented final recipe, that composes all found repositories metadata into final CSV file.
closes #162
History:

feat(#162): final
feat(#162): passes

PR-Codex overview
This PR introduces a new task for composing metadata into a final CSV file, updates the workflow for handling outputs, and adds tests for the new functionality.
Detailed summary

Added final task in pyproject.toml for composing metadata.
Updated .github/workflows/collect.yml to save outputs in a structured folder.
Implemented main function in sr_data/steps/final.py to process CSV files.
Added unit tests for the main function in test_final.py.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here.

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 10min).


Another name for the @UriRef annotation

And yet another name I'm not fully happy with. The @UriRef annotation can be used to assign a symbolic id to the URI template of a controller method. Originally there was some discussion if this annotation should actually be provided by JAX-RS, but this never happened.
Just thinking out loudly: Is @UriRef a good fit for the name of the annotation? Actually this annotation is used to define a simple ID, which can be used to reference the URI template later. On the other side we could consider this annotation to define a symbolic reference to the URI template, which may also be correct.
One alternative would be @UriId, although I'm not sure if this is much better.
I don't know. I'm a bit unsure about what the best name could be and whether my doubts make any sense. Please let me know your thoughts. If you don't see any problem with the current name, I'll immediately shut up. :laughing:

Regarding rel: I agree that rel isn't a good fit. It is usually not a unique identifier but some kind of symbolic reference relative to the current resource (like self, next, etc).
I also don't like @UriId very much. I guess @UriRef is the best name we have. I was just wondering if everybody comes up with a better idea. Naming is hard. ;-)

Closing this one now. Feel free to reopen if you come up with a better name.


add glow to esp

this is a external cheat as far as im aware you need an internal cheat to do that


[Request] Add default font Cascadia-Mono to the Windows Terminal manifest

Since updating to the latest version of Windows Terminal; 1.6.10571.0, I noticed I get an error every startup unless I install its new default fonts, fonts which are being hosted separately here: https://github.com/microsoft/cascadia-code
Is it possible to include this in the Windows Terminal manifest since it's now a dependency in practice, in order to avoid any errors and run the software as intended?
Thank you for your time.

Note: The fonts seem to require Admin privileges to install

I'm currently running an installation of the required fonts separately through the following json: https://github.com/kkzzhizhou/scoop-apps/blob/master/bucket/cascadia-code-pl.json
It does require sudo on uninstallation, but not on installation.
Don't know if that complicates things or not.

Interesting...I installed using https://github.com/microsoft/cascadia-code/wiki/Installing-Cascadia-Code#installation-via-scoop-unofficial-by-sbatten which requires admin on both install and removal.


Mac what am I doing wrong?

Sorry to bother you Jaku but maybe you can help me figure out what i'm doing wrong. I downloaded the cert file then changed it to always trust and finally I copy pasted the code into my terminal. When i open the app everything is still blank but oddly enough i can access some of my filters that i saved in favorites although i have to randomly guess which ones they are because they all look like blanks.
Thanks for your time and concern Jaku
sincerely, a computer noob :(

Did you completely close Snap Camera and reopen it? A reboot to be sure.
When you first close the app, it still hangs around in the Menu Bar at the top of the screen near the clock.

i copy pasted it into the terminal and it did not show me the IP nor the studio-app.snapchat.com entry

I put the command in quotes. Please try again without the quotes.

here is the result of taking the quotes out

@CalebWalz411 looks like your /etc/hosts file is not properly pointing to the right location.
On your first screenshot, after you pasted the command on Terminal and hit enter, you need to type your local password and hit enter so that the file gets properly edited.

And I'm facing a similar issue even though I have the certificate applied and the /etc/hosts file edited:

(It's in Portuguese, but it does say "Always Trust" lol.

Hello Luizpdlh thanks for your advice I tried to re-enter the command then put my local password and push enter and this was the result

You're mistaking what they asked.
Go back to the guide and run that command like before. In the first screenshot you sent you will see it asked for your password. When you type it it won't show.
So go back and run the command, when it prompts type your password and press enter. It should then make the entry in your hosts file.

woohoo success :) thanks for you patience Jaku and help and thank you @luizpdlh for your help.


Refactor and move functions

Change make_Hlabel to gen_label, which will generate a hierarchical or global label depending on the sheet of each part with the label
Moved part rotation logic to part.py
Created inner function for sorting parts into hierarchies

Thanks!


UART not found

When trying "uart_echo" sample Micropython gives an error "ImportError: cannot import name UART".
I looked into machine-module and it indeed does not have UART in it.
What seems to be the problem?

What model of XBee are you using? Per the Digi MicroPython Programming Guide, only XBee Cellular and XBee 3 Cellular support machine.UART at this time: https://www.digi.com/resources/documentation/digidocs/90002219/default.htm#reference/r_features.htm%3FTocPath%3D_____2

I see. I use the zigbee variant. I did not know what secondary uart meant but it seemed to me like a basic thing that would be available in all devices right from the start :(


[FLINK-36935][state/forst] Implement fast link for ForStFileSystem

What is the purpose of the change
This pr implements fast link for ForStFileSystem.
Brief change log

Introduce FileMappingManager to manager the file mapping in ForStFileSystem.
Adapt ForStFileSystem to FileMappingManager

Verifying this change
This change added tests and can be verified as follows:

FileMappingManagerTest

This change is already covered by existing tests:

ForStStateBackendV2Test#testAsyncStateBackendScaleUp
ForStStateBackendV2Test#testAsyncStateBackendScaleDown

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Please can you describe in the jira what the purpose of this change is. I am not sure what fast link is and it is not described in the Flip, Jira or the PR comments or code..

Please can you describe in the jira what the purpose of this change is. I am not sure what fast link is and it is not described in the Flip, Jira or the PR comments or code.

Sure, I edited the description and added some clarification for Fast Link.

As discussed offline, it is better to use a file mapping to manage all the soft link, including the remote -> remote ones as well as those remote -> local ones. We use link to implement the rename to reduce file copy AMAP. Let's see how it goes.


Add operationId properties to endpoints

This enables client SDK generators to create nicer names for the functions
Otherwise auto generated names are used, which are mostly suboptimal

This would generally make it easier to use SDK generation tools such as OpenAPI Generator to generate client SDKs for the HTTP API.
This PR only contains a change to the OpenAPI spec, and it only adds operationId properties. These are typically not show in e.g. SwaggerUI or ReDoc output, but can be leveraged by e.g. above-mentioned tools.
Names/operation IDs are of course up for discussion; I picked some which looked as if they would make sense.
Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

 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.

Thanks for submitting this PR, we'll give it a review as soon as possible

@tabergma What's the state here?

Ready to be merged. Sorry.


[Snyk] Upgrade @vscode/vsce from 2.21.1 to 2.22.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @vscode/vsce from 2.21.1 to 2.22.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 3 months ago, on 2023-10-28.

Release notes

Package name: @vscode/vsce

2.22.0 - 2023-10-28remove win32-ia32 (#908)

2.21.1 - 2023-09-29

use execFile instead of exec

fix for windows

    from @vscode/vsce GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

merging with dependabot/npm_and_yarn/vscode/webview-ui-toolkit-1.4.0


The signature of transaction is not shown

The signature of transaction is not shown, or cc_id is the signature?

What version of marbles are you running? Can you post a screen shot of what you do see and explain what you expected to see?

closing due to inactivity.


AnimationTree repeats the methods and properties that trigger the last frame of the acyclic animation

Godot version
3.x Latest
System information
windows 10
Issue description
AnimationTree repeats the methods and properties that trigger the last frame of the acyclic animation.
I only pressed the button once.
As shown in the figure, I don't know whether it is a bug or a feature?
How can I keep the last frame of the current animation instead of switching to the next animation to solve this problem?
AnimationTree 会重复触发非循环动画的最后一帧的方法和属性.
我只按了一次Button.
如图所示,不我知道是BUG还是特性?
如何可以保持当前动画的最后一帧,而不是切换到下一个动画来解决这个问题?

See also: #51576

After testing #51576, it is feasible.
经过测试#51576,可行.


Adding keyword-named properties to functions generates invalid declarations

TypeScript Version: 4.0.0-dev.20200522

Search Terms:
Code
function foo() {}
foo.null = true;

Expected behavior:
Any syntactically valid output. Since namespaces can't hold keyword names one option is generating an object type with call signature:
declare var foo: {
    (): void;
    null: boolean;
}

This change would also allow to generate declarations for statically-analyzable dynamic property access expressions (i.e. foo["foo bar"] = true), which are currently omitted from declarations, resulting different behavior between in-project and out-of-project values.
Actual behavior:
declare function foo(): void;
declare namespace foo {
    var null: boolean;
    //        ^^^^^^^ TS2693: 'boolean' only refers to a type, but is being used as a value here.
    //  ^^^^^ TS1134: Variable declaration expected.
}

Playground Link: https://www.typescriptlang.org/play?ts=4.0.0-dev.20200522#code/GYVwdgxgLglg9mABMOcAUBKRBvAvgKBTgDowQAbcxAXkSgCcQBTAbiA
Related Issues:

We can generate a temp name and re-export with the right name.
declare function foo(): void;
declare namespace foo {
    var _null: boolean;
    export { _null as null };
}

Just make sure that everything else is still exported (i.e. yadda is accessible in the generated .d.ts file for the following).
function foo() {}
foo.yadda = 100;
foo.null = true;


Escape control characters in CSV log file

Description
This patch escapes new line and carriage return characters when writing and unescapes them when reading those CSV log files.
Motivation and Context
As reported in #5770 and on the users mailing list, we currently do not escape new line characters when writing the CSV log file.
How Has This Been Tested?
Tested on a local test plan and add JUnit tests.
Types of changes

Bug fix (non-breaking change which fixes an issue)
But could also be seen as a new feature or even breaking change.

Checklist:

[x] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

I think the escaping of \r and \n should not be done according to the RFC: https://github.com/apache/jmeter/issues/5770#issuecomment-1554402532


Mismatch Fig. 3.46

In Fig. 3.46, there is a slight difference for the sopc variable. Its corresponding plot should exhibit a higher peak around 1980.
The issue persists when changing the solver.

Closed by #108 .


Can't start VMs using UTM on aarch64-darwin

Describe the bug
When trying to start a VM on mac, it just fails
Steps To Reproduce
Steps to reproduce the behavior:

Install utm using home-manager (might also have the same
open UTM
Create a new linux VM with 4096 memory,
Attach ubuntu 18.04 x86_64 ISO
Start VM

Expected behavior
The VM should boot up.
Screenshots
Config

Error

Additional context
Add any other context about the problem here.
Notify maintainers
@rrbutani
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"aarch64-darwin"`
- host os: `Darwin 22.5.0, macOS 13.4`
- multi-user?: `yes`
- sandbox: `no`
- version: `nix-env (Nix) 2.16.1`
- channels(root): `"nixpkgs"`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

I fixed it by adding write permissions for the current user to efi_vars.fd. Something like:
chmod +uw ~/Library/Containers/com.utmapp.UTM/Data/Documents/[VM NAME].utm/Data/efi_vars.fd


Add new action for Watson Retrieve and Rank

@csantanapr commented on Tue Jun 07 2016
Add new action for Watson Retrieve and Rank
Related to #365
http://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/retrieve-rank.html

@markusthoemmes commented on Fri Mar 10 2017
@csantanapr move to catalog?

Any new Watson packages, they need to be created outside Apache in a repo that IBM Watson team maintains, and deploy themselves.
cc @sjfink


SAK-47462 Rubrics: Don't set weight for criterion groups

When switching a rubric to weighted the weight for the first criterion get’s set to 100%. If there is a criterion group before other criteria, the criterion group get’s the weight value instead (hidden). The weight should only be set for “real” criteria.
This also fixes console errors when changing to weighted for a rubric without criteria.

@mpellicer Can you take a look please? :)


grid3_client ts version typescript problems

@polkadot/util-crypto has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.14     node_modules/@polkadot/keyring/node_modules/@polkadot/util-crypto/cjs
        cjs 10.1.14     node_modules/grid3_client/node_modules/@polkadot/util-crypto/cjs
@polkadot/util-crypto has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.14     node_modules/@polkadot/keyring/node_modules/@polkadot/util-crypto/cjs
        cjs 10.1.14     node_modules/grid3_client/node_modules/@polkadot/util-crypto/cjs
        cjs 10.1.14     node_modules/@polkadot/types/node_modules/@polkadot/util-crypto/cjs
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.14     node_modules/@polkadot/util/cjs
        cjs 9.7.2       node_modules/ts-rmb-http-client/node_modules/@polkadot/util/cjs
@polkadot/keyring has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.14     node_modules/@polkadot/keyring/cjs
        cjs 9.7.2       node_modules/ts-rmb-http-client/node_modules/@polkadot/keyring/cjs
@polkadot/util-crypto has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.14     node_modules/@polkadot/keyring/node_modules/@polkadot/util-crypto/cjs
        cjs 10.1.14     node_modules/grid3_client/node_modules/@polkadot/util-crypto/cjs
        cjs 10.1.14     node_modules/@polkadot/types/node_modules/@polkadot/util-crypto/cjs
        cjs 9.7.2       node_modules/ts-rmb-http-client/node_modules/@polkadot/util-crypto/cjs
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/node' is not defined by "exports" in /home/jimber/Documents/Threefold/tf-deployer/node_modules/grid3_client/package.json
    at new NodeError (node:internal/errors:387:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:464:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:748:3)
    at resolveExports (node:internal/modules/cjs/loader:493:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:533:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:942:27)
    at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/home/jimber/Documents/Threefold/tf-deployer/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

this is my package.json:
{
  "scripts": {
    "deploy:qsfs": "ts-node qsfs/qsfs.deploy.ts",
    "deploy": "ts-node deploy/vm.deploy.ts",
    "delete-gateways": "ts-node delete/gateway.delete.ts",
    "delete-contracts": "ts-node delete/contract.delete.ts"
  },
  "main": "deploy/vm.deploy.ts",
  "dependencies": {
    "@polkadot/wasm-crypto": "^6.3.1",
    "dotenv": "^16.0.2",
    "grid3_client": "1.4.2",
    "tfgrid-api-client": "^1.12.1",
    "ts-node": "^10.9.1",
    "typescript": "^4.8.2"
  }
}

issue linked to correct repo: https://github.com/threefoldtech/grid3_client_ts/issues/464

in this line
you need to remove /dist/node and just be grid3_client
so the line should be :
import { BackendStorageType, GridClient, KeypairType } from "grid3_client";

Verified.
I changed line as in @0oM4R comment, and the error gone, and code started validating user variables.

in this line you need to remove /dist/node and just be grid3_client so the line should be : import { BackendStorageType, GridClient, KeypairType } from "grid3_client";


Bug Report: Error in compiling, I can't fix this.

When I try to compile for windows, it gives me this error:

I know, I know there's a lot of other reports with this same error, but I still get this error after following all the steps other people give.
When I use lime rebuild extension-webm windows, this error appears:

Actuate is already installed.
And yes, I already used "haxelib git extension-webm https://github.com/GrowtopiaFli/openfl-haxeflixel-video-code.git".
Please help me.

I could fix it. I don't know what I did, but I fixed it.


Investigate using actors for thread-safe services

Swift now has a thread-safe Actor type, which is like a class, but enforces safety against data-races between different threads and tasks.
Currently we use DispatchQueue.sync to enforce thread-safety for certain services. We could investigate using actors instead. They are more ergonomic, and integrated with Swift's async features.
https://www.swiftbysundell.com/articles/swift-actors/

We've started using actors as of https://github.com/subconsciousnetwork/subconscious/pull/501


Fix normalization of playbook/playbooks keys of ansible plugin

Pull Request Checklist

[x] implement the feature

Hm, copr builds failed because of:
!! Copr timeout => sending INT
Copr build error: Build failed

Seems like some infra issue, let's try again.

/packit test


bug(toLazySignal): leaks subscription

More info:
https://github.com/angular/angular/issues/55337#issuecomment-2059206188
cc @e-oz

No, don’t worry :)
https://github.com/angular/angular/issues/55337#issuecomment-2059418668


[REVIEW]

Twitter profile link
https://twitter.com/jamesspurin

Thanks, the feedback was brilliant


Test-UnifiSiteKnownSetting

Building list of Unifi site settings...
Processing [Redacted SiteName]...
Found new site setting: super_fwupdate. Please inform module maintainer.
available_controller_channels : {release}
available_firmware_channels   : {release}
controller_channel            : release
firmware_channel              : release
key                           : super_fwupdate
sso_enabled                   : False
_id                           : [REDACTED just incase]
Controller Version: Version 6.2.25. Linux
in GUI, New GUI, I BELIEVE this is referring to System > Maintenance > "Top Section (not named)" > Advanced > Release Channel Settings

I just checked your closed issues, this is a duplicate.  Closing.


Issue with Lazy loading

HI,
I tried normal lazy loading approach but that process doesn't meet my custom requirement.
First I'll explain my scenario and add  necessary files now.
Requirement
I need to load 6 to 7 different tree view's in a page So initially call the api(Service) function through ajax then i iterate the each item which has the children properties(Implemented Approach) bind to the different tree view
I faced below problems with lazy loading approach(As suggested)

If i modify this process as per your suggestion or doc then i need to fetch the all roots in each and every time of tree view binding .It will be duplicate call's to api function(Service call)

I need to modify the json data after coming from api call(service) so i used DataFilter in normal suggested approach.In this approach i couldn't find the first call response or lazy load call response.

Avoid these problems i added mouse down event.In this situation drag and drop option didn't work.
Please Check this customized requirement and necessary attached docs.
Please suggest me how to proceed further.

In first api call i got the list tree's collection.I think as per normal lazy load approach doesn't meet my requirement and if i use that approach api(Service) call's will be duplicated

Use core.data as a function - you have full control then - you can fetch the resource once and feed it to all trees. Having a function as core.data gives you full control and maximum flexibility - you can fetch / cache data however you need.
If you absolutely want to go the hard way and do things manually - try not to break existing event handlers and you should be fine. If you are preventing the mousedown event from bubbling - that will break the DND functionality.

HI,
please suggest any reference links to help my scenario so that i can get full idea.


Child loggers

What's the proper way to append a child logger? I'd like to append a trace id to all requests, using ctx.state to carry it.
Somehow do this:
app.use(correlationIdMiddleware)
app.use((ctx) => {
  logger({
   level: 'debug',
   name: 'askas-facade'
  }).logger.child({correlationId: ctx.state.correlationId })
  }
)

Never mind, I solved it with a middleware added before the logger:
const uuid = require('uuid/v4')
const validate = require('uuid-validate')

const correlationIdMiddleware = async (ctx, next) => {
  const requestCorrelationId = ctx.request.header['x-correlation-id']
  const correlationId = validate(requestCorrelationId)
    ? requestCorrelationId
    : uuid()

  ctx.reg.id = correlationId
  ctx.set('X-Correlation-ID', correlationId)

  await next()
}

module.exports = correlationIdMiddleware

You can check out this alternative koa-logging.


flutter-download download uri maybe wrong

I just found that we might have downloaded flutter-engine from the wrong url on beta.
This url is current used,
https://storage.flutter-io.cn/flutter_infra/flutter/52c7a1e849a170be4b2b2fe34142ca2c0a6fea1f/linux-x64/linux-x64-flutter.zip
But as I found, this zip does not contain flutter_embeder.h. I think this binary contains embeder, glfw and other stuff and might be google's final desktop runner.
According to google's wiki, we might use for only embedder, like this one:
https://storage.flutter-io.cn/flutter_infra/flutter/52c7a1e849a170be4b2b2fe34142ca2c0a6fea1f/linux-x64/linux-x64-embedder

The new download contains both the desktop shell and the embedder API. Sadly there is no download that contains both the new and the old headers, so for now I've opted to download the new library and headers and manually added the old headers.

I mean the Old downloads are still available and contain the Old header only. We can continue to use them. New package are probably for Google desktop  implementation. We probably dont need them.

I've fixed the download url in https://github.com/gliheng/flutter-rs/commit/e58866f12aaeb5bff5f01e0068a8c64500468eab    Is it working for you?

Okay, works fine as well. I'll close this :)


⚠ Bofrost.be has degraded performance

In dbddafd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1076 ms

Resolved: Bofrost.be performance has improved in ba14d39.


feat(nfs-server): provision nfs server resource in user provided namespace

Why is this PR required? What issue does it fix?:
As of now, nfs-provisioner creates nfs-server resources in default 'openebs' namespace. This resource can be isolated from operator namespace.
What this PR does?:
This PR fixes the above issue. With these PR changes, nfs-provisioner will create the nfs-server resources in the namespace mentioned in OPENEBS_IO_NFS_SERVER_NS env variable in nfs-provisioner deployment. If OPENEBS_IO_NFS_SERVER_NS is not mentioned or is having empty value then nfs-server resources will be created in the operator namespace which is openebs.
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[x] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #58 (7e2700a) into develop (0e0a870) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #58   +/-   ##
========================================
  Coverage    48.37%   48.37%
========================================
  Files           18       18
  Lines         1598     1598
========================================
  Hits           773      773
  Misses         781      781
  Partials        44       44

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 0e0a870...7e2700a. Read the comment docs.

Hi @kmova @mittachaitu
I've updated the PR as per review comments. PTAL.
Thanks


Add daily maintenance rake task

This will run daily through a cronjob pod, and will purge old checks so the database doesn't grow unnecessarily with stale data.

@tmckernan Precisely because of that, we would want to remove those checks early, as the data would be incomplete and not very useful for analytics, but still a few days is valuable to detect where users might be dropping out of the journey, or kickout (exit) pages. 7 days is a reasonable time period. Happy to go with any other (short) period.
Similarly for completed checks, and given there is no personal data in this service, we can go with a longer period, to be able to analyse the data and have enough checks to find patterns and/or iterate those checks that are most common, etc.
In the C100 we maintain these 30 days, but for this service we can go much longer.

Fine lets go with these time frames for now


Final project: Parallel Ecosystem

Implement / test / benchmark a parallelized version of the Ecosystem which would be based on multiple phases of an agent step:

create a list of all potential interactions (e.g.: "wolf eats sheep", "sheep eats grass", ...)
find collisions like "sheep1 eats grass1" / "sheep2 eats grass1" and resolve them
execute interactions
remove / spawn agents

@pevnak @smidl do you think we should add this one to the projects page?


Jupyter Notebook isn't where it usually is

Hello!
when I try to start Imswitch, I get this error and I'm sure thatr Jupyter notebook is installed. Any suggestions?

Thanks. What do the logs in the console look like? What happens if you click ok?

If you click ok, the message pops up again. I solved the issue by installing python 3.10.0 as mine was 3.9 and the installed miniforge was for python 3.10. So I guess this was the issue.

Now I ran into one more issue. Failed to load module APDRED when I selected the imcontrol_setup file: sted.json. I face this error of failing to load module so many times and It remains the same even when I restart the software and I'm not able to select another file or remove the error. So what should I do? uninstall the software and install it again or what?

If you click ok, the message pops up again. I solved the issue by installing python 3.10.0 as mine was 3.9 and the installed miniforge was for python 3.10. So I guess this was the issue.

Can you briefly explain the steps to reproduce? Did you use the installer? What did you do afterwards?

Now I ran into one more issue. Failed to load module APDRED when I selected the imcontrol_setup file: sted.json. I face this error of failing to load module so many times and It remains the same even when I restart the software and I'm not able to select another file or remove the error. So what should I do? uninstall the software and install it again or what?

This is caused by a wrong config file. Can you visit this page and check how to change the config file? You want to use example_uc2.json. I'll delete the sted example from the uc2 code-base.

If you click ok, the message pops up again. I solved the issue by installing python 3.10.0 as mine was 3.9 and the installed miniforge was for python 3.10. So I guess this was the issue.

Can you briefly explain the steps to reproduce? Did you use the installer? What did you do afterwards?

I installed the software again after installing python 3.10 and deleting all the old dependencies and packages. And it worked fine.

Now I ran into one more issue. Failed to load module APDRED when I selected the imcontrol_setup file: sted.json. I face this error of failing to load module so many times and It remains the same even when I restart the software and I'm not able to select another file or remove the error. So what should I do? uninstall the software and install it again or what?

This is caused by a wrong config file. Can you visit this page and check how to change the config file? You want to use example_uc2.json. I'll delete the sted example from the uc2 code-base.

which page do I need to visit to see how to change the config file? can you share the link?

oh snap, I forgot the link: https://github.com/openUC2/imswitchconfig?tab=readme-ov-file#setting-up-this-repository

What I see on this page is just a description of the existing files in the ImSwitchConfig, but I can't find any related explanation about how to change a specific config file. Can you explain the process, please?

Okay It worked. Just copied the config files into ImSwitchConfig and everything is fine.

What exactly are you trying to do. The config file should represent your hardware configuration further described here: https://imswitch.readthedocs.io/en/stable/use-cases.html?highlight=config
You can try using the following config to have the virtual microscope running
{
    "positioners": {
        "VirtualStage": {
          "managerName": "VirtualStageManager",
          "managerProperties": {
            "rs232device": "VirtualMicroscope",
            "isEnable": true,
            "enableauto": false,
            "isDualaxis": 0,
            "stepsizeX": 1,
            "stepsizeY": 1,
            "stepsizeZ": 1,
            "stepsizeA": 1,
            "homeSpeedX": 15000,
            "homeSpeedY": 15000,
            "homeSpeedZ": 15000,
            "homeSpeedA": 15000,
            "homeDirectionX": 1,
            "homeDirectionY": 1,
            "homeDirectionZ": -1,
            "initialSpeed": {"X": 15000, "Y":  15000,"Z": 15000, "A": 15000}
          },
          "axes": [
            "X",
            "Y",
            "Z",
            "A"
          ],
          "forScanning": true,
          "forPositioning": true
        }
      },
    "rs232devices": {
    "VirtualMicroscope": {
      "managerName": "VirtualMicroscopeManager",
      "managerProperties": {
      }
    }
  },
 "lasers": {
    "LED": {
      "analogChannel": null,
      "digitalLine": null,
      "managerName": "VirtualLaserManager",
      "managerProperties": {
        "rs232device": "VirtualMicroscope",
        "channel_index": 1
      },
      "wavelength": 635,
      "valueRangeMin": 0,
      "valueRangeMax": 1023
    }
  },
  "detectors": {
    "WidefieldCamera": {
        "analogChannel": null,
        "digitalLine": null,
        "managerName": "VirtualCameraManager",
        "managerProperties": {
            "isRGB": 0,
            "cameraListIndex": 0,
            "cameraEffPixelsize": 0.2257,
            "virtcam": {
                "exposure": 0,
                "gain": 0,
                "blacklevel": 100,
                "image_width": 1000,
                "image_height": 1000
            }
        },
        "forAcquisition": true,
        "forFocusLock": true
    }
    },
  "rois": {
    "Full chip": {
      "x": 600,
      "y": 600,
      "w": 1200,
      "h": 1200
    }
  },
  "fovLock": {
    "camera": "WidefieldCamera",
    "positioner": "VirtualStage",
    "updateFreq": 1,
    "piKp":1,
    "piKi":1
    },
    "sim": {
      "monitorIdx": 2,
      "width": 1080,
      "height": 1920,
      "wavelength": 0,
      "pixelSize": 0,
      "angleMount": 0,
      "patternsDirWin": "C:\\Users\\wanghaoran\\Documents\\ImSwitchConfig\\imcontrol_slm\\488\\",
      "patternsDir": "/users/bene/ImSwitchConfig/imcontrol_sim/488"
    },
    "dpc": {
      "wavelength": 0.53,
      "pixelsize": 0.2,
      "NA": 0.3,
      "NAi": 0.3,
      "n": 1.0,
      "rotations": [0, 180, 90, 270]
    },
  "PixelCalibration": {},
  "availableWidgets": [
    "Settings",
    "View",
    "Recording",
    "Image",
    "Laser",
    "Positioner",
    "Autofocus",
    "MCT",
    "ROIScan",
    "HistoScan",
    "Hypha"
  ],
  "nonAvailableWidgets":[
    "FocusLock",
    "SIM",
    "DPC",
    "FOVLock",
    "Temperature",
    "HistoScan",
    "PixelCalibration",
    "Lightsheet",
    "WebRTC",
    "Flatfield",
    "STORMRecon",
    "DPC",
    "ImSwitchServer",
    "PixelCalibration",
    "FocusLock"]
}

It can very well be that there is some thread waiting for a hardware response e.g. from USB and hence it's crashing. Unclear.

Hello @Farghal1 It seems that we are currently working on similar projects and have run into similar problems from the issues we have reported. I would love to get in contact with you to ask you how you solved some of these issues and I might be able to answer some questions of yours. Please email me at<EMAIL_ADDRESS>if you are available to discuss these things in more detail. Thanks in advance!

We recently introduced a forum under openUC2.discourse.group for
like-minded optics enthusiasts. Feel free to use this for open discussions
or questions :)
Tag me and I try to answer a soon as possible
On Thu, Jun 27, 2024, 23:58 jsmithe2 @.***> wrote:

Hello @Farghal1 https://github.com/Farghal1 It seems that we are
currently working on similar projects and have run into similar problems
from the issues we have reported. I would love to get in contact with you
to ask you how you solved some of these issues and I might be able to
answer some questions of yours. Please email me at @.*** if
you are available to discuss these things in more detail. Thanks in advance!
—
Reply to this email directly, view it on GitHub
https://github.com/openUC2/ImSwitchInstaller/issues/10#issuecomment-2195726923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBE5ODWWNSP4NCZ72PAEMDZJSDH5AVCNFSM6AAAAABHIVPZBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVG4ZDMOJSGM
.
You are receiving this because you commented.Message ID:
@.***>


Add ability to specify job name and have it show in the job listing page in the UI

Which issue does this PR close?

Closes https://github.com/apache/arrow-ballista/issues/277
Rationale for this change

Easier to find my jobs now:

What changes are included in this PR?

Users can set the ballista.job.name config in their context and that name appears in UI.
Are there any user-facing changes?

Thanks for the review @avantgardnerio


Update build.yml and aside.go

Updated build.yml with new go-version variable with values including 1.21 and 1.22 to the matrix
and
Added an option to ClientOption to use Lua scripts for acquiring locks, enhancing compatibility with older Redis versions that do not support the SET NX GET command.

Do I have to do something in order to get this test cases passed or is it normal?


Add support for network visualiser when connected to shared instance

This PR adds support for parent/child interface visualization when connected to a shared RNS instance, and removes dependency on manually getting certain interface-specific characteristics such as hash and name, since these were added natively in RNS 42319a092db0d593e35f07478d1eece907f3bb88.
Also fixes a bug where the network visualizer would fail if a probe responder was active on the transport node.

Tested on one of my well-connected testnet hubs with ~120 interfaces. Much spring, but works nicely!

Holy moly! That's a fair few interfaces!
Thanks for the PR and for adding those extra infos natively :)
I'll get this merged in once RNS has a release available to pull in.

Thanks for the merge! It would be quite nice if you can also add custom display names to the network visualiser, so that if a custom name is set on a conversation, it will use that in the visualiser too. I tried messing around with it a bit today, but I am completely unfamiliar with Vue, and figured I'd likely just break something, or implement it wrong, so I'd rather leave it to you :) Just a humble request, but man would it be nice :)

Done :) Added in 000b51544215e3719f808abd56d6781ec4b37658 and 1c1d820bb27ef893a92aedd50b8535bafc624916

AWESOME!

Question: Does this generalize out to being able to look at "parent_interface_name/hash" on any shared Reticulum instance for identifying which interface an announce came in on?


Storm control with port-channels - wrong CLI syntax  for unknown-unicast

Issue Type

[x ] EOS Configuration rendering error

Summary

rendering edge port configuration with port-profile including storm-control configuration is working well for single ethernet ports but showing a CLI syntax issue on port-channels for unknown-unicast. It  generates "unknown_unicast" instead of "unknown-unicast"
Component Name
eos_l3ls_evpn
ansible-avd/ansible_collections/arista/avd/roles/eos_l3ls_evpn/templates/edge_ports/leaf-server-port-channels.j2
Steps to reproduce

port_profiles:
  Tenant_DC_ESX:
    mode: trunk
    native_vlan: '1000'
    vlans: 1000-1200
    spanning_tree_bpdufilter: false
    spanning_tree_portfast: edge
    storm_control:
      broadcast:
        level: 1
        unit: percent
      multicast:
        level: 1
        unit: percent
      unknown_unicast:
        level: 1
        unit: percent

servers:
  server10:
    adapters:
    - profile: Tenant_DC_ESX
      server_ports:
      - Eth0
      - Eth1
      switch_ports:
      - Ethernet9
      - Ethernet9
      switches:
      - leaf-2A
      - leaf-2B
      type: nic
      port_channel:
        description: PortChannelTest
        mode: active
    rack: 2E5

  Host-21-13:
    adapters:
    - profile: Tenant_DC_ESX
      server_ports:
      - Eth0
      switch_ports:
      - Ethernet10
      switches:
      - leaf-2A
      type: nic
    rack: 2E5

Expected results

$
interface Port-Channel9
   description server10_PortChannelTest
   no shutdown
   switchport
   switchport trunk allowed vlan 1000-1200
   switchport trunk native vlan 1000
   switchport mode trunk
   mlag 9
   spanning-tree portfast
   storm-control broadcast level 1
   storm-control multicast level 1
   storm-control unknown-unicast level 1

interface Ethernet10
   description Host-21-13_Eth0
   no shutdown
   switchport
   switchport trunk allowed vlan 1000-1200
   switchport trunk native vlan 1000
   switchport mode trunk
   spanning-tree portfast
   storm-control broadcast level 1
   storm-control multicast level 1
   storm-control unknown-unicast level 1

Actual results

interface Port-Channel9
   description server10_PortChannelTest
   no shutdown
   switchport
   switchport trunk allowed vlan 1000-1200
   switchport trunk native vlan 1000
   switchport mode trunk
   mlag 9
   spanning-tree portfast
   storm-control broadcast level 1
   storm-control multicast level 1
   storm-control unknown_unicast level 1

Could you try typing unknown-unicast instead of unknown_unicast. I have this working in my case.

Could you try typing unknown-unicast instead of unknown_unicast. I have this working in my case.

Hi... tested it: it is working with unknown-unicast instead of unknown_unicastin the DC_SERVERS.yml file for ethernet port and port-channel.
Seems to be a documentation error.

Hi... tested it: it is working with unknown-unicast instead of unknown_unicastin the DC_SERVERS.yml file for ethernet port and port-channel.
Seems to be a documentation error.

Since storm-control for ethernet_interfaces is based on unknown_unicast, I will replicate same behavior to get consistency in YAML configuration.
PR is in progress.

Since storm-control for ethernet_interfaces is based on unknown_unicast, I will replicate same behavior to get consistency in YAML configuration.
PR is in progress.


Refactoring of deployments and env

This is last bits on refactoring deployments. It includes:

move deploying logic from envs to deployments
remove model field from deployment, now you should provide it every time you run deployment
changes to mlem deployment run similar to those in #363
(WIP) add used declaration to state to detect changes (eg change in heroku app name). For now we should just forbid changes (ie just create new deployment and remove old one). In future we can allow changing some of the fields (scaling factor, for example)
(WIP) add used model info to state. For now it will be only path and project (if used explicitly). In future we should also add rev for git-tracked models (commit sha, not branch/tag) to link deployment state with repo "state". Also a good idea will be to have an option to forbid deploying not tracked models (ie changed after last commit) or at least warn about it. This will allow users to enforce this linking and have exactly the same version of model in commit and in deployment

Some examples of how deployments cli can be used:
# declare everything separately
mlem declare env heroku --api_key lol prod.mlem
mlem declare deployment heroku --env prod.mlem --app_name myapp service.mlem
mlem deployment run --load service.mlem --model mdoel
# ----
# declare deployment with embedded env
mlem declare deployment heroku --env.api_key lol --app_name myapp service.mlem
mlem deployment run --load service.mlem --model mdoel
# ----
# declare env only
mlem declare env heroku --api_key lol prod.mlem
mlem deployment run heroku service.mlem --model model --app_name myapp --env prod.mlem
# ---
# provide all parameters to `run
mlem deployment run heroku service.mlem --model model --app_name myapp --env.api_key lol
# error on args mismatch

move deploying logic from envs to deployments

Had a quick look, this is basically reversing the roles of envs and deployments.
But I think tests have to be changed right now? to accommodate this reversal of roles.

remove model field from deployment, now you should provide it every time you run deployment

I guess this only applies to mlem deployment run, what about other sub-commands such as mlem deployment apply? They shouldn't be affected right? or --model has to be used with each sub-command as well?
Also, just to confirm, if I understand correctly, I guess the commands will change in such a manner right?:
BEFORE:
mlem deployment run testsk --model sk-model --env kubernetes

AFTER:
mlem deployment run kubernetes testsk.mlem --model sk-model

But I think tests have to be changed right now?

They are.
Every command except run works with already existing deployment so you do not need to provide model option.
Now you can either create new deployment with mlem deployment run <type> <path> [options]
or run existing with mlem deployment run --load <path>


Bug:

Self Checks

[x] I'm using the latest lualine.
[ ] I didn't find the issue in existing issues or PRs.

How to reproduce the problem

Today, Barbar and lualine packages have some of the icons as question marks with rectangle box around them. Barbar shows the close button as above symbols. Lualine shows the language server warning/issues/errors as above symbols.
Expected behaviour
Actual behaviour
Minimal config to reproduce the issue

Additional information
I am currently using mononoski nerd font mono. My Nvim-Tree works okay. And the icons are only partially broken. I tried use packer to remove both barbar and lualine. And reisntalled one of them at a time. The issue persist. The terminal I am using right now is iTerm2. I barely have any modification on the lualine.lua configuration. Its in my repo here:
lua/lualine-config/init.lua
https://github.com/Roboticyang/Nvim_lua_config.git

I am facing the same problem after updating the nerd fonts today

https://github.com/ryanoasis/nerd-fonts/releases/tag/v3.0.0
It's because there was a breaking change in Nerd Fonts.

@tgw314 Thanks alot on the information. I guess, because I used brew to install the font on my macOS, and installed differently on my ubuntu device. I don't have any issue on my ubuntu device so far.

great tool to deal with obsolete symbols:
https://github.com/loichyan/nerdfix
waiting for lualine update to fix the issues with outdated symbols

@moshiur-raj barbar.nvim has fixed the close button issue already.

@yujingyuz Cool! I will keep an eye on the new updated with Nvim packer.


message list: Scrollbar moves underneath the top navigation bar.

This reproduces on Chrome 70, Safari 12, and Firefox 73; this is the scroll bar for the entire window that moves with the message view:

@zulipbot add "area: message view" "area: general UI" "bug"

After PR  #10885  , this should fix it :
body {
    overflow-y: scroll;
}
.app {
   // overflow-y: scroll;
}

@zulipbot claim

Closing as duplicate of #9911.


Gettr api has upgraded to v2.  This library no longer works.

@milesmcc do you have any plans to maintain this repo?

@apilover12321 I would gladly accept a PR that adds support for the V2 API.


Leave skipped tests out of the report

If skipped integration tests are present in the machine.log from flutter test --machine, they are marked as follows:
{"test":{"id":37,"name":"Test title","suiteID":0,"groupIDs":[2,32],"metadata":{"skip":true,"skipReason":null},"line":159,"column":5,"url":"package:flutter_test/src/widget_tester.dart"},"type":"testStart","time":554187}
{"testID":37,"result":"success","skipped":true,"hidden":false,"type":"testDone","time":554187}

They should be omitted from the resulting JUnit test report

Closed as I opened this one https://github.com/TOPdesk/dart-testreport/pull/4


Add two more Mastodon accounts (and a matrix id)

cause who wouldn't want to profit from https://mstdn.science/@gtn/110628391201479353 :-)

@hrhotz you're also welcome to join in

Thanks for the heads-up
I will add my accounts within the next few days

done, see: https://github.com/galaxyproject/training-material/pull/4256


Better type casting of BIT values

see similar discussion in https://github.com/sidorares/node-mysql2/issues/1597
Currently BIT fields are always returned as single byte Buffer:
https://github.com/mysqljs/mysql/blob/dc9c152a87ec51a1f647447268917243d2eab1fd/lib/protocol/packets/RowDataPacket.js#L107
I think this should be returned as a number. Might be good to coordinate both changes here in mysql2, this is potentially a breaking backwards incompatible change

Good idea. Need to make sure we don't run in to Javascript number issues. The BIT field is up to 64 bits wide and of course a plain javascript number can only be 53 bits wide. Perhaps it would just always return a BigInt?

Oh, for some reason I assumed it's always just one byte. Not so sure about this change now, really depends on what's the most common use case in real life. If it's actually used as a "bit field" a Buffer might be a good container for it

Gotcha. Yes, I don't personally use the field, so not sure all the uses folks have for it. The field itself comes back as a length-encoded string field over the text protocol and the BIT type in the database can be between 1 and 64 bits. The string contents is just the binary data of the bits, not really much different from like a BINARY field, just that the length is defined in bits instead of bytes. I guess there is probably some kind of storage optimization possible for this but 🤷


JSON API gives different results depending on HTTP client

After updating my package in production on legacy PyPI, the warehouse package shows the current version, but the PyPI JSON API seems to return stale results depending on which HTTP client queries it.
*When I use urlopen() (Py3) to access https://pypi.io/package/json, the JSON reports the results for the previous version rather than latest.
*When I use curl to access the JSON page, it also reports the old version.
*Unexpectedly, when I access https://pypi.io/package/json in my web browser, it reports the latest version. Therefore, it appears that pypi.io only responds with the latest version when more detailed HTTP headers are provided.
I have not found any documentation that what this header should be.
This behavior has broken some of my build scripts that worked about a month ago. (I can check exact dates if this is useful for bisection.) My Travis CI build process and my local box both exhibit the behavior, so it is quite unlikely that it is a local machine cache issue on my end.
To reproduce:
-use twine to upload a new version of a test package, targeting legacy PyPI
-wait for warehouse's rich HTML to reflect that the new package is available
-check the same JSON page in a web browser, and it shows the current package, as expected
-curl https://pypi.io/package/json and it incorrectly reports the old package

About 24 hours later, curl reports the correct (new) package.

I'm pretty sure that this is just going to be down to the Vary header and caching in Fastly. Uploading to legacy PyPI doesn't purge Warehouse so you have to wait for stuff to fall out of the cache "naturally" in that case. Uploading to Warehouse purges both Warehouse and Legacy.
I'm going to go ahead and close this, we're unlikely to solve this since it'll go away once Legacy upload goes away.

@dstufft Do you recommend uploading to Warehouse at this point?

@jbarlow83 Yes, and both twine and Python default to it in their latest version if you haven't overridden it in your ~/.pypirc. You can upload to https://upload.pypi.org/legacy/ for production Warehouse and https://test.pypi.org/legacy/ for TestPyPI.


Refactor AMIP experiments

Purpose

Refactors the experiments directory to contain only the currently maintained code, and ordered similarly to the CIME setup

addresses #232

To-do

[x] new components dir with model setup files
[x] test the same results are obtained as before this PR - Buildkite output checked for both slabplanet and AMIP
[x] clean up

[x] I have read and checked the items on the review checklist.

bors r+


simply quick fix for import type missing typeof

Fixes #24172 #24192

@mhegazy
sorry about this,
i have do these change and i forget to commit it


attach conversation data to chat activity notifications CORE-4401

The point of this patch is the following:
1.) Refactor all the Gregor handling code into the chat package.
2.) Refactor the Badger into the badges package.
3.) Change the behavior of the NewMessage, ReadMessage, and SetStatus handlers to include a ConversationLocal object on them so that the frontend can use that to update itself.

cc @chrisnojima

CI looks like it is still running, I think the red X came from your change req.


adding normalization

@aarmey here's the normalization code

After adding the subset by replicates change, the emcee trace was breaking more often. It would typically break for me the first time I ran it and work properly afterwards.

Think this is working. Merging!


std::is_pod is deprecated in C++20

Newest msvc preview version already implements warning for this case. While it's not urgent in any way, it might be nice to replace it with either std::is_standard_layout or std::is_trivial to avoid warnings during compilation with newer standard support.
Here you can find more details on its deprecation:
https://stackoverflow.com/questions/48225673/why-is-stdis-pod-deprecated-in-c20

I created a branch for this: https://github.com/nlohmann/json/tree/feature/issue1913

@stale This issue should be pinned.
@nlohmann, hello.
Is there any new progress? It seems that this issue will be closed by bad bot.

I have a branch for this an will finish this after my vacation.


Exclude more tests from ASan test configuration.

See https://github.com/iree-org/iree/issues/5716. I just excluded all lit tests from here: https://github.com/iree-org/iree/blob/db6b68773e4daab4da2de1e835c16c4323b583ec/tests/e2e/models/CMakeLists.txt#L13-L24
As there are other tests in that file using runners other than lit that have not crashed (that I'm aware of), I did not exclude the entire directory.
Most recent failure: https://github.com/iree-org/iree/runs/8146877750?check_suite_focus=true
1030/1030 Test   #46: iree/tests/e2e/models/resnet50_fake_weights.mlir.test ....................................................................***Failed   63.16 sec
-- Testing: 1 tests, 1 workers --
FAIL: IREE :: e2e/models/resnet50_fake_weights.mlir (1 of 1)
******************** TEST 'IREE :: e2e/models/resnet50_fake_weights.mlir' FAILED ********************
Script:
--
: 'RUN: at line 4';   iree-run-mlir --iree-input-type=mhlo --iree-hal-target-backends=llvm-cpu /home/runner/actions-runner/_work/iree/iree/tests/e2e/models/resnet50_fake_weights.mlir --function_input=1x224x224x3xf32 | FileCheck /home/runner/actions-runner/_work/iree/iree/tests/e2e/models/resnet50_fake_weights.mlir
: 'RUN: at line 5';   [[ $IREE_VULKAN_DISABLE == 1 ]] || (iree-run-mlir --iree-input-type=mhlo --iree-hal-target-backends=vulkan-spirv /home/runner/actions-runner/_work/iree/iree/tests/e2e/models/resnet50_fake_weights.mlir --function_input=1x224x224x3xf32 | FileCheck /home/runner/actions-runner/_work/iree/iree/tests/e2e/models/resnet50_fake_weights.mlir)
--
Exit Code: 1

Command Output (stderr):
--
Tracer caught signal 11: addr=0x0 pc=0x61dbf9 sp=0x7f63edb65d30
==53069==LeakSanitizer has encountered a fatal error.
==53069==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
==53069==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)

It's unfortunate that this also drops asan coverage for non-vulkan things here, but I guess that's an issue with using lit as the runner instead of cmake (which it's still useful to have at least some things running like this to ensure the tools work, so I think that's fine, but we may also want to have cmake runners for these models)

It's unfortunate that this also drops asan coverage for non-vulkan things here, but I guess that's an issue with using lit as the runner instead of cmake (which it's still useful to have at least some things running like this to ensure the tools work, so I think that's fine, but we may also want to have cmake runners for these models)

Agreed :/. I've seen enough flakes (and confusion about whether those are issues in infra / llvm integrates / PRs themselves) in the past few weeks that I want to at least patch which tests are ran in this way. When I last looked at the actual failure (LeakSanitizer has encountered a fatal error), I wasn't really hopeful about For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1, but that might help us narrow this down.

Ping? Still seeing a few of these tests flake.


Support for ASUS TinkerBoard GPIO

Support for ASUS TinkerBoard GPIO TESTING
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
switchs.yaml
  - platform: tinker_gpio     ports:       12: TinkerFan                                # GPIO PIN number     invert_logic: true
Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

You need to include the component as well, not only the sensor.

@plutosherry, this PR is still incomplete.


How to mock IP address for testing?

I need to test blocking certain ip addresses. I tried to implement a test middleware to mock IP addresses but it seems I cannot overwrite the req.connection.remoteAddress value.
Example:
const ipMocker = (req, res, next) => {
  req.connection.remoteAddress = '<IP_ADDRESS>'
  // this value reverts to original
  next()
}

I do not want to test using the 'trust proxy' method.

The req.connection.remoteAddress is from Node.js code and is what is reverting the assignment. If you need to override that property, you may need to open an issue with Node.js core, as we wouldn't e able to change how it works.
How does your code get the ip to look it up on the whitelist?

The req.connection.remoteAddress is from Node.js code and is what is reverting the assignment. If you need to override that property, you may need to open an issue with Node.js core, as we wouldn't e able to change how it works.
How does your code get the ip to look it up on the whitelist?

This is my ip validator middleware, I'm open to changing it if it can solve my problem, I'd rather not have to do something like if (mockIp) do x. I'd rather not have any mocking code in my production app.
const ipValidator = (req, res, next) => {
  let ip = req.connection.remoteAddress

  if (isUsIp(ip)) {
    next()
    return
  }

  res.end()
}

So, i see. If you are reading from that prop and node.js does not allow changing the value, the only next step is open a ticket with node.js issue tracker.
Alternatively you can use a different property to get around this like maybe have your validator read req.remoteIp and add a middleware before it that does req.remoteIp = req.connection.remoteAddress. Then you can mock req.remoteIp

So if I understand correctly, none of the default req values can be overwritten, only the ones you have added yourself.

Express does not add req.connection.remoteAddress, it comes from node.js. You need to open and issue on thier issue tracker if you have questions regarding it.

Express does not add req.connection.remoteAddress, it comes from node.js. You need to open and issue on thier issue tracker if you have questions regarding it.

Yeah I get that, what about using req.ip? Is there a way to mock it?

Yes, there are several ways, but the main method you explicitly said you didn't want to use which is why i suggested to make your own property.

Otherwise you can redefine how req.ip works:
Object.defineProperty(app.request, 'ip', {
    configurable: true,
    enumerable: true,
    get: () => { /* what you want to do */ }
  })

Yes, there are several ways, but the main method you explicitly said you didn't want to use which is why i suggested to make your own property.

Well making my own property is the same as adding mocking code that's only purpose is for mocking in my production app, so it would not be what I want. My optimal method would injecting a test middleware that does req.iq = 'my mock ip', but I just tried and that does not seem to overwrite.

Using trust proxy adds no mocking code to your app, though.

that's true but it doesn't feel right. I'd be testing my app with a different flag on then I'd use in production. I'd rather my mocks be something I made myself and know what they do exactly. Probably makes no difference but doesn't feel right.

All of these options have that issue. If example if you reassign req.ip how do you know that your tests aren't just working because you assigned an ip there and in reality req.ip is undefined in production?
If you want to overrite req.ip: https://github.com/expressjs/express/issues/3908#issuecomment-473566585

If you want to overrite req.ip: [#3908 (comment)]

thanks I hadn't seen that.

So I'm going to close this for now due to inactivity. Let me know if you're still having problems or other questions and I can help answer or even reopen the issue.

If I overwrite req.ip, the req.ip cannot be recover and the test after defineProperty  will get mock ip.
How should I get original function?


The library  support Vue??

I`m using it in my vue project.
You could use it like this
 EXIF.getData( this.$refs['img'][index], function() {
   var Orientation = EXIF.getTag(this, 'Orientation')
   console.log(this,Orientation)
})

And you should note that the getData callback looks like only run success when the img tag is visible,not just loaded.


Hold your Ground

This Crusader Passive should cap dodge at 0% as it make's dodging impossible however with the Gogok of Swiftness gem it still gains dodge.

Fixed.


feat/starknet_getBlockWithTxHashes

Issue: Implement starknet_getBlockWithTxHashes RPC Call
Description:
The starknet_getBlockWithTxHashes RPC call has been implemented but requires further testing and verification against the entire state. This RPC call retrieves block information with transaction hashes given the block id.
Parameters:

block_id: The hash of the requested block, or number (height) of the requested block, or a block tag. This parameter is required.

Expected Result:
The resulting block information with transaction hashes. The result can be of two types:

Block with transaction hashes
Pending block with transaction hashes

Potential Errors:

BLOCK_NOT_FOUND: The block requested could not be found.

Testing:
Initial testings can be found here. However, these should not be considered complete and improvements are welcome.
Resources:

Alchemy RPC API Endpoint Documentation
Starknet API OpenRPC Spec

Comments:
Please comment below for coordination.

tests:

[x] non existing block
[x] existing block
[ ] latest block
[ ] pending block


CI/CD: You have attempted to create more buckets than allowed

The Chore
https://github.com/vegaprotocol/frontend-monorepo/actions/runs/9173247634/job/25221866965?pr=6426 failed while creating a deploy preview with the following error:
An error occurred (TooManyBuckets) when calling the CreateBucket operation: You have attempted to create more buckets than allowed

Tasks

[ ] Get rid of some buckets I suppose?
[ ] Didn't we have an action that culled old buckets?

Valentin has fixed this


render: Scroll games list when needed

Needs testing but I believe the logic could work.

Confirmed working on my 1.0!


Bump icedfrisby and icedfrisby-nock

This fixes a bug in icedfrisby that emerged with nock beta.15. I'm not sure if this will allow updating to nock beta.20, though it's worth merging regardless.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 6cbb860bce4e37014083547b5146bcd75ad18898

Only a handful of service tests failed when running all of them, and all those failures were timeouts or spurious/unrelated
👍


build(deps): bump Terraform from 1.5.6 to 1.6.1

Release notes
https://github.com/hashicorp/terraform/releases/tag/v1.5.7
https://github.com/hashicorp/terraform/releases/tag/v1.5.7

The legal state of this dependency is still unclear but hopefully you'll be able to provide an update soon

Thank you for providing updates to Terraform @yeikel! Our team is somewhat underfunded at the moment, but I hope we can prioritize keeping ecosystems up-to-date.
I'll follow up on this by merging https://github.com/dependabot/dependabot-core/pull/8175 next. Please let me know if you are aware of other ecosystems that are outdated.

Thank you for merging these @Nishnha
FYI, we have been squashing these changes as intermediate commits rarely mean anything


Update mainnet-beta.json

New token ticker

do I close the pull request now, this is my first time?


crash on system missing snap

On an Ubuntu derivative without snap, we get the following crash:
tuffix 0.1.0

usage:

    tuffix <command> [argument...]

where <command> and [argument...] match one of the following:

Traceback (most recent call last):
  File "/usr/bin/tuffix", line 14, in <module>
    print_usage(DEFAULT_BUILD_CONFIG)
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Driver.py", line 30, in print_usage
    commands = all_commands(build_config)
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Commands.py", line 502, in all_commands
    return [AddCommand(build_config),
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Commands.py", line 250, in __init__
    self.mark = AddRemoveHelper(build_config, self.name)
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Commands.py", line 90, in __init__
    self.container = KeywordContainer(build_config)
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Keywords.py", line 713, in __init__
    C481Keyword(build_config),
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Keywords.py", line 492, in __init__
    self.Eclipse = EclipseKeyword(self.build_config)
  File "/usr/local/lib/python3.8/dist-packages/Tuffix/Editors.py", line 212, in __init__
    raise EnvironmentError(f'could not find snap')
OSError: could not find snap

It seems like the only place we are using snaps are to install Eclipse. Could we either cut Eclipse, or install it from tarball?

In previous builds of Tuffix, I attempted to alleviate this issue by installing from a tar ball too. Since installing a tar ball does not leave any real way of uninstalling it, I decided to try and make a class that could construct Debian packages of a tar ball. That sort of worked but was more of a case by case basis. I don't know the legality of putting pre-made Debian installers on our PPA. We could just cut the Eclipse editor for the initial launch and we can make a Debian installer but make it "hidden" from average users until we figure out the logistics of that?

Also, it seems that 481 might be in need of it based on previous requirements (not sure why AI needs it but hey), and since there are a lot of different options available, I'd say we could let students figure out how to install it themselves if they really want it?

Closing this issue and making a new issue labeled help wanted in regards to eclipse


use rem instead of em for HiDPI support

Updated style sheets with rem for #19
Unable to test this as I don't have a HiDPI screen however.

To simulated a higher dpi by setting layout.css.devPixelsPerPx to 1.5 in firefox about:config.
The layout does seem to fit on screen better with these changes, so I'm happy to merge it.


GPUImageFramebufferCache cannot release hash string after using  "- (NSString *)hashForSize:(CGSize)size textureOptions:(GPUTextureOptions)textureOptions onlyTexture:(BOOL)onlyTexture;"

Hi @BradLarson ,
I met this memory problem with Xcode profile for watching memory allocate size, and I found this function  for producing a temporary string value for a new frame.
So I try to using @autoreleasepool{//nsstring produced codes here};
it was better than before, but hash string memory was still increasing .
So can you had some idea for resolve this memory increasing problem?
Thx from EK

Hi @BradLarson ,
I thought and understand the reason what you do like this, but you can try using a max number for replacing the hash string to find the right frame. it will be better for heap and VM allocated every frame when producing lookupHash string.


Issues Packaging vSRX

Hi @carlmontanari
Thanks for posting this wonderful project. This is something we would love use for packaging a vSRX image into a docker container for some automated testing and validation.
I am running into an issue when trying to package a vSRX image in qcow2 format. Is there something I am doing wrong that is causing the error below?
boxen package --disk junos-media-vsrx-x86-64-vmdisk-20.3R3.8.qcow2
      info<PHONE_NUMBER> package requested for disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.qcow2'
  critical<PHONE_NUMBER> failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.qcow2'
  critical<PHONE_NUMBER> error allocating disks for packaging: inspectionError: failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.qcow2'
        🆘 finished unsuccessfully in 0 seconds
inspectionError: failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.qcow2'

I also tried ova format, bu that did not work either.
boxen package --disk junos-media-vsrx-x86-64-vmdisk-20.3R3.8.ide.ova
      info<PHONE_NUMBER> package requested for disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.ide.ova'
  critical<PHONE_NUMBER> failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.ide.ova'
  critical<PHONE_NUMBER> error allocating disks for packaging: inspectionError: failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.ide.ova'
        🆘 finished unsuccessfully in 0 seconds
inspectionError: failed gleaning source data from disk 'junos-media-vsrx-x86-64-vmdisk-20.3R3.8.ide.ova'

Actuall looks like this line may be to blame. https://github.com/carlmontanari/boxen/blob/98a32ca384635b77bbccaaeb0a4b99460022fc91/boxen/platforms/util.go#L16
May need to improve the regex matching string to follow the pattern of files downloaded for juniper in recent versions.

Hey @tagur87 yeah the patterns are not super broad and really just match the things I had available. Do you know if all the more recent disk images follow the same pattern as that qcow you have in the output above? if so I can prolly get that updated and pushed up later today/tonight, and can release 0.0.1 later this week.
Thanks for raising this!
Carl

Yea from what I can see, the most recent vSRX images follow this pattern junos-media-vsrx-x86-64-vmdisk-20.3R1.8.qcow2

Hey @tagur87
How does this pattern look to ya: (?:junos-)?media-vsrx-(?:x86-64-)?vmdisk.*.qcow2 should match the older 17.x one I have to test with and this new disk. I'll plan to add the capability to explicitly pass the target vendor/platform as well (overriding the auto-selection thing) at some point but probably won't get to that till the weekend.
Thanks for the help on this!
Carl

Simpler pattern in linked pr, lemme know what ya think!

Yea that pattern looks good and matches the file I downloaded from juniper the other day! Thanks for your efforts on this!

hola! found this and see the change in regex was merged but i seem to be hitting the issue as well:
# boxen package --disk ~/disks/junos-media-vsrx-x86-64-vmdisk-21.2R2-S1.5.qcow2
      info<PHONE_NUMBER> package requested for disk '/root/disks/junos-media-vsrx-x86-64-vmdisk-21.2R2-S1.5.qcow2'
  critical<PHONE_NUMBER> failed gleaning source data from disk '/root/disks/junos-media-vsrx-x86-64-vmdisk-21.2R2-S1.5.qcow2'
  critical<PHONE_NUMBER> error allocating disks for packaging: inspectionError: failed gleaning source data from disk '/root/disks/junos-media-vsrx-x86-64-vmdisk-21.2R2-S1.5.qcow2'
	🆘 finished unsuccessfully in 0 seconds
inspectionError: failed gleaning source data from disk '/root/disks/junos-media-vsrx-x86-64-vmdisk-21.2R2-S1.5.qcow2'

i've tried renaming the file but the regex should be matching it so unsure whats happening here. running 0.0.1, but also tried the 0.0.1-alpha to be safe and same thing.
# boxen --version 	version: 0.0.1 	source: https://github.com/carlmontanari/boxen

Hey @jsakofsky juniper version numbers make me sad (to be fair, most vendors version numbers make me sad!). Looks like the vendor -> platform regex works, but the regex to glean the disk version is missing the - in the number-y part. At some point I swear I will add tests for this stuff... but ya know, time and all that :) Anyway, will push something that should match to main here in a bit and update this comment so you can try to build from there.
PS- I dont think you'll need to do this because the only time we do the version parsing stuff is in the "outer" boxen (the part you run on your machine, not int he container), but if im forgetting that the stuff in the container does any of this regex checking you can use this to include the locally built boxen in the container instead of yanking from GitHub releases.

@carlmontanari isn't user-defined platform flag the answer to that?

Haha just was about to add another comment -- yeah... what @hellt said -- should also work with passing the --vendor --platform and --version flags to package. If memory serves you have to pass all three as we basically explicitly ignore the auto finding stuff! Good call Roman!

excellent, the flags did the needful. thanks so much all, all around.

awesome, thanks for confirming @jsakofsky and thanks @hellt for chiming in!


Issue Refreshing: fix it

There's actually a bunch of fixes here all detailed in the commit
messages:

Use bluebird promises in one last place
Use correct octokit api for fetching issues
Re-add the accidentally rate limit
Add logging by default to the Dockerfile
Template rendering: turn off useless debug mode

Thanks! This looks really good!

CR 👍
A couple comments, one about deprecation of that getFromRepo function and the other about leaving debugTools configurable.

CR 👍

CR :zap:


added is highly available and listing nodes on cluster response

Returning nodes when retrieving a cluster and return highly available flag

Current dependencies on/for this PR:

main

PR #7   👈

This comment was auto-generated by Graphite.