Remove remove unstable-azure provider

Now that the 5.1.8 release of Sourcegraph has experimental support for azure-openai as an autocomplete provider, this unstable provider that connects directly to azure is no longer needed.  To use azure for autocomplete a user should choose the unstable-openai provider and connect to a sg instance that is configured to use azure's openai apis.
Test plan
pnpm --filter cody-ai run start:dev:desktop ensure autocomplete still works.

Should we defer removing this? In case we run into a customer that needs this but can't upgrade quickly/easily?

Should we defer removing this? In case we run into a customer that needs this but can't upgrade quickly/easily?

I debated that, but I think with needing the keys in the extension it's pretty much unusable by customers, and it causes confusion around which one to use for azure openai.  There is always the ability to install a specific VS Code extension version.


Google drive links?

Could you please provide Google Drive links for the checkpoints, logs, etc., in addition to the Baidu links?
I'm unable to access the baidu storage.
Thank you!

Me too...


Add deriveSafePrivateKey

Add deriveSafePrivateKey and documentation about it.
Source: https://8gwifi.org/docs/window-crypto-pbkdf.jsp

lgtm


AssetManager ArrayIndexOutOfBoundsException on finishLoading

Issue details
From time to time I see this crash reported on my live wallpaper apps. It is impossible for me to reproduce.
Version of LibGDX and/or relevant dependencies
1.9.10
Stacktrace
Fatal Exception: com.badlogic.gdx.utils.i: java.lang.ArrayIndexOutOfBoundsException: src.length=28 srcPos=0 dst.length=49 dstPos=0 length=29
       at com.badlogic.gdx.assets.AssetManager.handleTaskError(AssetManager.java:638)
       at com.badlogic.gdx.assets.AssetManager.update(AssetManager.java:412)
       at com.badlogic.gdx.assets.AssetManager.finishLoading(AssetManager.java:439)
       at com.myapp.getSprite(LwLauncher.java:244)
       at com.myapp.setQuantities(LwLauncher.java:137)
       at com.myapp.run(LwLauncher.java:284)
       at com.myapp.render(LwLauncher.java:262)
       at com.badlogic.gdx.backends.android.AndroidGraphicsLiveWallpaper.onDrawFrame(AndroidGraphicsLiveWallpaper.java:217)
       at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1575)
       at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1271)

Caused by java.lang.ArrayIndexOutOfBoundsException: src.length=28 srcPos=0 dst.length=49 dstPos=0 length=29
       at java.lang.System.arraycopy(System.java)
       at com.badlogic.gdx.utils.Array.resize(Array.java:410)
       at com.badlogic.gdx.utils.Array.add(Array.java:101)
       at com.badlogic.gdx.graphics.Texture.addManagedTexture(Texture.java:233)
       at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:148)
       at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:142)
       at com.badlogic.gdx.assets.loaders.TextureLoader.loadSync(TextureLoader.java:77)
       at com.badlogic.gdx.assets.loaders.TextureLoader.loadSync(TextureLoader.java:35)
       at com.badlogic.gdx.assets.AssetLoadingTask.handleAsyncLoader(AssetLoadingTask.java:125)
       at com.badlogic.gdx.assets.AssetLoadingTask.update(AssetLoadingTask.java:90)
       at com.badlogic.gdx.assets.AssetManager.updateTask(AssetManager.java:563)
       at com.badlogic.gdx.assets.AssetManager.update(AssetManager.java:410)
       at com.badlogic.gdx.assets.AssetManager.finishLoading(AssetManager.java:439)
       at com.myapp.getSprite(LwLauncher.java:244)
       at com.myapp.setQuantities(LwLauncher.java:137)
       at com.myapp.run(LwLauncher.java:284)
       at com.myapp.render(LwLauncher.java:262)
       at com.badlogic.gdx.backends.android.AndroidGraphicsLiveWallpaper.onDrawFrame(AndroidGraphicsLiveWallpaper.java:217)
       at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1575)
       at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1271)

It looks like the problem resides in this line where for the System.arraycopy to work as it should, the result of the function Math.min(size, newItems.length)  must be <= items.length (in my case it looks like "size" is 29 while items.length is 28, thus giving the ArrayIndexOutOfBoundsException) - But I can be wrong. This happens rarely and I don't know why.
Thanks for your support.
Please select the affected platforms

[x ] Android

It looks like Texture managedTextures is accessed OR modified by multiple threads. It should only ever be accessed and modified by the OpenGL thread (the "sync" part of loading an asset). You could add checks that make sure everywhere Texture managedTextures is referenced Thread.currentThread() is in the same as the thread that eg called create on your app listener.

Thanks for your suggestion. Probably you are right.
My situation is that I'm showing a small window of the live wallpaper and under it, I put a button that starts the system full-screen live wallpaper preview. I think that if the user presses the button fast enough, the small preview and the full-screen preview will start almost at the same time thus accessing  managedTextures by multiple threads. I think I just have to wait for the small preview to finish loading and then make the button clickable.
Thank you so much NathanSweet. You really helped me.

Cheers! Likely you just need to use Gdx.app.postRunnable to ensure your code is run on the libgdx OpenGL thread (but I've never done wallpaper stuff, so maybe things aren't initialized yet).

I'm already using Gdx.app.postRunnable in many situations, but a re-check never hurt. Thanks again


Tap-to-dismiss in the backdrop view not enabled by default

Description
Tap-to-dismiss in the backdrop view not enabled by default.
Expected behavior
To be activated by default or to have a setting to activate or deactivate
Actual behavior
Tap on dismiss in the backfrop view is by default not enabled.
From code:
// Set tap-to-dismiss in the backdrop view
let tapGesture = UITapGestureRecognizer(target: self, action: #selector(handleBackdrop(tapGesture:)))
tapGesture.isEnabled = false

Hi, you can enable it like this.

Hi, you can enable it like this!
https://github.com/scenee/FloatingPanel/blob/43c7e8c2a05a32d8b1e3018e341ba3fab8285d14/Examples/Samples/Sources/UseCaseController.swift#L73

backdropView.dismissalTapGestureRecognizer.isEnabled = true is conflict with isRemovalInteractionEnabled = true

There is no conflict between them 🤔

Thanks @scenee , it works!
Indeed isRemovalInteractionEnabled is a different thing, it is for dismissing by swiping to the edge.


Tests

Coverage decreased (-0.9%) to 95.268% when pulling 2ad89783bc140a944a24a579b949e2c2f9385d64 on flatiron-school:tests into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.


PHP Warning from cron job

For a few days now, I have been receiving the following error message from the cron job I have set up:
PHP Warning:  Undefined array key "current" in /var/www/vhosts/httpdocs/megane/index.php on line 308 PHP Warning:  Trying to access array offset on value of type null in /var/www/vhosts/httpdocs/megane/index.php on line 308 PHP Warning:  Undefined array key "current" in /var/www/vhosts/httpdocs/megane/index.php on line 309 PHP Warning:  Trying to access array offset on value of type null in /var/www/vhosts/httpdocs/megane/index.php on line 309 PHP Warning:  Trying to access array offset on value of type null in /var/www/vhosts/httpdocs/megane/index.php on line 309 PHP Warning:  Trying to access array offset on value of type null in /var/www/vhosts/httpdocs/megane/index.php on line 309
There is another process running on the server for a Zoe that is not reporting any errors. Installed is the latest version with the customized api-keys.php.
Megane
PHP-Version: 8.2.6
cron: */1 * * * *
Zoe
PHP-Version: 8.2.6
Folder: /var/www/vhosts/httpdocs/zoe/index.php
cron: */5 * * * *
I suspect that the error lies with me. Maybe someone knows the problem. At least the correct values seem to be transmitted.
Thanks for your help!

This indicates a problem with getting data from the openweathermap API.
Did you changed the config.php? There is the API key for openweathermap defined.

Closed because no answer to my question.


Create comprehensive tests to check the logic of the entire extension

Currently storage.ts isn't well tested. It is not trivial to test the logic here since a lot of the work gets delegated to chrome.storage.
We should introduce dependency injection to solve this issue by passing something that wraps chrome.storage or whatever other storage provider we decide to use in the future. We can also introduce an interface type for this storage provider.

Here's a great video on DI: https://www.youtube.com/watch?v=J1f5b4vcxCQ

In tests, we can then pass a fixture for the storage provider that we can use to verify our tests.

We could use browser.storage.sync instead of the Chrome storage API. It works similarly, except it supports Chrome, Firefox, and Edge. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage/sync

@superbahbi This refactor makes it possible to totally abstract any browser implementation details using DI: https://github.com/r3bl-org/shortlink/blob/main/src/storage/storage_provider_api.ts
This opens the doors for writing comprehensive tests and supporting other browsers and electron environments, etc.


Port to 1.20.6

This is a port to 1.20.6
1.20.6 split the load function into loadFromResource and loadFromNetwork (in net.minecraft.registry.RegistryLoader)
I've changed the mixin to inject into the net.minecraft.registry.RegistryLoader.parseAndAdd function since both of the two methods use it.
On another note, it looks like 2.1.2 was released, but gradle.properties still says 2.1.1?

Thank you for this PR, I'll look into it today!

Well looks good to me, thank you, I'll upload it asap!


Y24-098 Tube Rack Banking Purpose

User story
As PSD, we would like to support Limber plate purpose configuration using the versioned Tube Rack model proposed in Reuse of TubeRacks document.
Who are the primary contacts for this story
Abdullah, Katy, Andrew
Who is the nominated tester for UAT
TBD
Acceptance criteria

[ ] LRC Bank Seq and LRC Bank Spare tube racks are configured in purpose config (they are tube purposes in DPL-811)
[ ] Tube racks are displayed and linked to on the Limber Pipeline Work In Progress page

Dependencies
This story is blocked by the following dependencies:

#1482

References
This story has a non-blocking relationship with:

#1314

Additional context
The versioned tube rack model is researched in DPL-1011 Re-use of tube racks and the model is summarised in the Google Document https://docs.google.com/document/d/1rvPXeCk5rBEf72VkchHCD2FRmWANboke2pln_Lt_j5U/edit?usp=sharing
This story is part of re-implementation of DPL-811 Transfer PBMC isolations into FluidX tube racks (Banking) using the versioned tube rack model. https://github.com/sanger/limber/issues/1314

One more user facing acceptance criteria?:

[ ] Tube racks are displayed and linked to on the Limber Pipeline Work In Progress page

If we display TubeRacks in Work In Progress page, what happens?
For example, in the following page: https://uat.limber.psd.sanger.ac.uk/pipeline_work_in_progress/scRNA Core Cell Extraction
At the moment we are showing LRC Bank Seq  and LRC Bank Spare tubes in the last two column individually. We would instead show a single Tube Rack entry for its LRC Bank Seq tubes and similarly a single Tube Rack entry for its LRC Bank Spare tubes, which would take us to their TubeRack views similar to a Plate views.
I think modifying Work In Progress view would deserve a separate story but I can still add it here for now.

I think it would be handy if you mentioned in your acceptance criteria which are existing already.
e.g. a tube rack can already have a purpose, so you could put:

Tube Rack can have a purpose (already implemented)

Or, just leave it out altogether?
What actually needs to be done here? Is the main thing "Pipeline configuration can specify relationships using tube racks"?

I have added Purpose config and pipeline config criteria similar to DPL-811 in order to group Seq and Spare tubes under the tube racks with the same purpose.

Move criterion "Tube racks are displayed and linked to on the Limber Pipeline Work In Progress page" to another story.

I have moved the "Tube racks are displayed and linked to on the Limber Pipeline Work In Progress page" to a new story: Y24-112 Display Banking Tube Racks for scRNA Core Cell Extraction in Limber Pipeline Work in Progress #1714
I have made a top level story for the Banking part to link the banking stories together: Y24-088 Implement DPL-811 Transfer PBMC Isolations into FluidX tube racks using the versioned TubeRack model #1713


[Proposal] support periodic backups

I already seen a bunch of ask about how to schedule periodic backup.
The current design will not support that, and suggest to use CronJob to create backup CR periodically (Only creation can trigger the actual backup handling function).
Here are some cons of this methods.

CronJob is scheduled by k8s scheduler. For clusters has 100s etcd-operators, it will be a big load on the scheduler. (It is not the option for me at Azure) @khenidak on more thoughts.
For users seeking backup operator, they are looking into a solution. Backup scheduling always comes with Backup itself
It is not very intuitive to create a CronJob with access to k8s api-server. It involves secret handling.

So, i propose to have backupPolicy option.

If backupPolicy not provided, it will not do periodic backup. It will be the same of existing behavior, which does one-time backup.
For backupIntervalInSecond

unit in Sec
>0 means interval. Of course, we will have the minimal interval limit.
=0 means explicit disable interval backup, it will just do one time backup.
<0 not allowed, failed validation
It doesn't need to strictly refer to the interval. For any reason the backup operator get restarted, we can just ignore the last backup time

For maxBackups

specify how many backups we want to keep
maxBackups == 0 => unlimited backup

Related Issues: #1787

Based on above proposal,
When user specify in backup CR
spec:
  backupPolicy:
    maxBackups: 4
    backupIntervalInSecond: 30
  s3:
     path: "mybucket/mycluster_backup"
  ...

We will have "mybucket/mycluster_backup_v{revision}_{date}"
And for each revision, we keep up to 4 revisions.
The same logic apply to restore operator as well.

@rjtsdl kindly ping on this one.

@xiang90 , I am currently not having cycle anytime soon. If someone want to pick it up, I am totally good with it.

currently, there is a default backup timeout of 60s which is not configurable which can cause problem for slow machine that can't finish backup under 60s as seen in https://github.com/coreos/etcd-operator/issues/1903.
I also propose to include a configurable backup timeout in backupPolicy.

Do you have plan to support periodic backups in near future?


Add some handy options to Multisearchable

Had this sitting in a fork, and wanted to PR upstream for feedback and consideration for a merge. (Although it might need some refactoring first? Certainly needs docs.)
This adds two pieces of functionality:
1. Conditionally update pg_search_documents
Specify an :update_if parameter:
  multisearchable(
    against: [:body],
    update_if: :body_changed?
  )

I think this is a good way to solve https://github.com/Casecommons/pg_search/issues/217.
2. Specify additional attributes to be saved on the pg_search_documents table
Imagine each multisearchable Model has an associated project_id. You can add a column, and then:
  multisearchable(
    against: [:body],
    additional_attributes: -> (record) { { project_id: record.project_id } }
  )

EDIT: There might be a related issue for this, but I can't seem to find it now.
Let me know what y'all think!

This looks great. I've tried to avoid adding too many methods to the modules that get mixed into ActiveRecord::Base subclasses, but I think you have good reasons for each one here.
I'm going to go ahead and merge, but we should add some documentation to the README about these new features before we push out a new gem version.


"Valea Iașului", "Bădila" are listed in the drop-down menu

Description:
When user writes "Valea Iașului" and "Bădila" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Valea Iașului"

Expected results
The location appears in the drop-down menu as "Sat Valea Iașului, ARGEȘ (Valea Iașului)"


Retrieve the block results that include the event with the exact attributes in query

Closes: #2867
Closes: #2868

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

I think also fixes #2868

What do you think about untangling this PR to separate the changes related to issue 2868 apart from issue 2867?
Context:

I think we can merge the changes related to https://github.com/informalsystems/hermes/issues/2868 ASAP. They look solid.
As for https://github.com/informalsystems/hermes/issues/2867 this is more complex.

Jasmina proposed a Tendermint-level fix in this PR https://github.com/tendermint/tendermint/pull/9759
With these changes in place we can query from Hermes using the new match.events flag.
This requires tendermint-rs changes, so it will be a bit more work to push that through, but it's a long term fix.
In order to unblock the Tendermint team, it would be good if we give them feedback on their PR.

Summary:

We can fix #2868 by trimming down the present PR (or a new PR with the right changes)
We can open a new PR to test E2E if the changes in Tendermint (https://github.com/tendermint/tendermint/pull/9759) are sufficient to fix #2867.

If yes, we give the feedback to TM team and go with that
If no, we retain the solution in this PR

I'll take a look at the tendermint PR and run a custom hermes version that uses that. But it seems that we still need to temp fix hermes with the PR here until all chains move to the new tendermint version.


Missing argument when building lookahead

With latest master I get the following error when building the lookahead:
[  0%] Built target file_xc7_archs_artix7_devices_rr_graph_xc7a50t_test.rr_graph.real.xml
[  0%] Generating rr_graph_xc7a50t_test.rr_graph.real.xml.cache, rr_graph_xc7a50t_test.lookahead.bin, rr_graph_xc7a50t_test.place_delay.bin
VPR FPGA Placement and Routing.
Version: 8.0.0-rc1+a7964ea8d
Revision: v8.0.0-rc1-1170-ga7964ea8d
Compiled: 2019-11-28T13:36:35
Compiler: GNU 7.4.0 on Linux-4.15.0-65-generic x86_64
Build Info: release IPO VTR_ASSERT_LEVEL=2 debug_logging

University of Toronto
verilogtorouting.org
<EMAIL_ADDRESS>This is free open source code under MIT license.

Missing expected argument for --router_lookahead

usage: vpr architecture circuit [--pack] [--place] [--route] [--analysis]
       [--disp {on, off}] [--save_graphics {on, off}] [-h] [--version]
       [--device DEVICE_NAME] [-j NUM_WORKERS] [--timing_analysis {on, off}]
       [--disable_errors DISABLE_ERRORS] [--suppress_warnings SUPPRESS_WARNINGS]
       [--route_chan_width CHANNEL_WIDTH] [OTHER_OPTIONS ...]
xc7/archs/artix7/devices/CMakeFiles/file_xc7_archs_artix7_devices_rr_graph_xc7a50t_test.lookahead.bin.dir/build.make:65: recipe for target 'xc7/archs/artix7/devices/rr_graph_xc7a50t_test.rr_graph.real.xml.cache' failed
make[3]: *** [xc7/archs/artix7/devices/rr_graph_xc7a50t_test.rr_graph.real.xml.cache] Error 1
CMakeFiles/Makefile2:89474: recipe for target 'xc7/archs/artix7/devices/CMakeFiles/file_xc7_archs_artix7_devices_rr_graph_xc7a50t_test.lookahead.bin.dir/all' failed
make[2]: *** [xc7/archs/artix7/devices/CMakeFiles/file_xc7_archs_artix7_devices_rr_graph_xc7a50t_test.lookahead.bin.dir/all] Error 2
CMakeFiles/Makefile2:215596: recipe for target 'xc7/tests/serdes/CMakeFiles/all_oserdes_test.dir/rule' failed
make[1]: *** [xc7/tests/serdes/CMakeFiles/all_oserdes_test.dir/rule] Error 2
Makefile:1763: recipe for target 'xc7/tests/serdes/CMakeFiles/all_oserdes_test.dir/rule' failed
make: *** [xc7/tests/serdes/CMakeFiles/all_oserdes_test.dir/rule] Error 2

Nevermind, I realized I was using a wrong VtR version


🪲[Bug]: Navbar logo hovering effect .

Describe the bug
In the navbar logo while hovering the logo going out of the navbar.
@akshitagupta15june
Dear PA,
If you think this is a bug, then please assign this to me under gssoc'24. And if this is not then, please consider it and assign me.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
video -
https://github.com/akshitagupta15june/PetMe/assets/136844498/d661ee6c-f092-4b62-969e-1a4a185acad4
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Please assign this issue to me


Create Back End project (API)

I have created and published my first HttpServlet API, please check below links:
http://alessfirstproject.appspot.com/test?num1=1&num2=2
http://alessfirstproject.appspot.com/hello

Below is my solution:
https://github.com/AlessHo/Httpservlet-API


Java realtime transcription function contains insecure version of Log4J

Disclaimer: I am not a Java dev, this is the best description of the problem and solution I can create based off my research, I may be wrong about some details, or its completely possible I am totally off base on multiple aspects. My hope is that the information below is at least somewhat useful in fixing this issue as quickly as possible.
Problem
No doubt the maintainers of this project are at this point aware of CVE-2021-44228, AKA the Log4j vulnerability. The most recent version of this package makes use of slf4j-log4j12 version 1.7.24 uses an insecure version of log4j as a downstream dependency. Notably, the dependency 'amazon-kinesis-video-streams-parser-library' is also outdated (v1.0.15) and the version in use also contains slf4j bindings and an outdated version of log4j. This causes the function to log:
SLF4J: Class path contains multiple SLF4J bindings.

when run.
This vulnerability could theoretically allow arbitrary Java code execution within the Lambda function and in turn lead to an attacker accessing other resources in the AWS environment that the function has access to. As far as I can see it's unlikely that an attacker could devise a way to exploit this vulnerability over an Amazon Connect IVR. As far as I'm aware the only instance where the function logs user input is when it logs the real time transcript, which would be be quite difficult to use for an exploit, if exploited however it represents a significant security risk so this needs to be patched as quickly as possible.
Solution

Upgrade to the latest version of the 'amazon-kinesis-video-streams-parser-library'.
Exclude log4j and the slf4j bindings from downstream dependencies of 'amazon-kinesis-video-streams-parser-library'. Maven instructions specific to slf4j. Gradle Instructions. Or if switching to a different logging provider use 'log4j-over-slf4j' instead..
Force the use of the latest version of log4j as a downstream dependency, or switch to a different logging provider and use different slf4j bindings.

As the official repo still uses v1 .  We would be inclined to stick with the official version rather than branching off on our own.  Otherwise when AWS changes it to add a new feature we will be stuck with a merging job or stuck with the old version

This has been addressed by PR https://github.com/amazon-connect/amazon-connect-realtime-transcription/pull/66
Please build and deploy the project again. Let us know how it goes.

Please note that, at the time of writing this comment, v1.1.0 of amazon-kinesis-video-streams-parser-library was still not available on Maven, hence you would need to clone https://github.com/aws/amazon-kinesis-video-streams-parser-library first, and run mvn clean install to build v1.1.0 of amazon-kinesis-video-streams-parser-library. Once completed, run the build.

Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.8.1/commons-lang3-3.8.1.jar (502 kB at 913 kB/s)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:15 min
[INFO] Finished at: 2021-12-21T13:34:34+11:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.projectlombok:lombok-maven-plugin:<IP_ADDRESS>:delombok (delombok) on project amazon-kinesis-video-streams-parser-library: Execution delombok of goal org.projectlombok:lombok-maven-plugin:<IP_ADDRESS>:delombok failed: An API incompatibility was encountered while executing org.projectlombok:lombok-maven-plugin:<IP_ADDRESS>:delombok: java.lang.IllegalAccessError: class lombok.delombok.Delombok (in unnamed module @0x75120e58) cannot access class com.sun.tools.javac.tree.JCTree$JCCompilationUnit (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.tree to unnamed module @0x75120e58
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.projectlombok:lombok-maven-plugin:<IP_ADDRESS>
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/Users/jingjinli/.m2/repository/org/projectlombok/lombok-maven-plugin/<IP_ADDRESS>/lombok-maven-plugin-<IP_ADDRESS>.jar
[ERROR] urls[1] = file:/Users/jingjinli/.m2/repository/org/apache/commons/commons-lang3/3.8.1/commons-lang3-3.8.1.jar
[ERROR] urls[2] = file:/Users/jingjinli/.m2/repository/org/projectlombok/lombok/1.18.16/lombok-1.18.16.jar
[ERROR] urls[3] = file:/Users/jingjinli/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.7/plexus-build-api-0.0.7.jar
[ERROR] urls[4] = file:/Users/jingjinli/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.8/plexus-utils-1.5.8.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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/PluginContainerException
just saying after mvn clean install, got these error after donwloading lombok-maven-plugin:<IP_ADDRESS>:delombok

@angieyu can you help to review the error above and provide solution to fix it?
we are trying to run mvn clean install to build v1.1.0 of amazon-kinesis-video-streams-parser-library, but get this error and cannot move futher. thanks.

The release is available in Maven, please try getting the dependency from there: https://mvnrepository.com/artifact/com.amazonaws/amazon-kinesis-video-streams-parser-library/1.1.0

Hi, I have discovered that if I install Java version 12 from brew, I can run mvn clean install successfully. These were the steps I took.
brew tap AdoptOpenJDK/openjdk
brew install adoptopenjdk12 --cask
/usr/libexec/java_home -V (to get Java version for the next step)
export JAVA_HOME=`/usr/libexec/java_home -v 12.0.2`
java -version
mvn clean install

Java version 16 also worked for my coworker.

@angieyu Hi Angela, thanks for your quick response. the mvn error is fixed followed your commands.
However, i got a error when running gradle build to build amazon-connect-realtime-transcription:
_amazon-connect-realtime-transcription [master] gradle build
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details
FAILURE: Build failed with an exception.

Where:
Build file '/Users/jingjinli/Documents/temp/Genie/amazon-connect-realtime-transcription/build.gradle' line: 13

What went wrong:
A problem occurred evaluating root project 'amazon-connect-realtime-transcription'.

Could not find method compile() for arguments [directory 'jars'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 4s_
I got the same error when building in our customized repo(i pasted the new version 1.1.0 jar files into jars folder ) and the demo repo https://github.com/amazon-connect/amazon-connect-realtime-transcription. Could you please help to advise which step i did wrong?

can you let me know what version of gradle you are using, please?

Hi @angieyu  thanks for your reply, with your commands, mvn clean install successfully.
and later run gradle build but need to install gradle v6, with latest gradle will get error.

In my lambda I have this kvsTranscriber function, which I need to update to fix the log4j insecure version, how can I get a newer version without re-compile the whole project, as it is in production today thank you

I was able to get the build to work by changing compile to implementation in the gradle.build file.  Any issues or concerns with that method?

@sidbenac you would need to build the KVS Transcriber project and then deploy Lambda function with .zip file archive as described here.

The source code is patched with the following versions of affected dependencies.
amazon-kinesis-video-streams-parser-library version to 1.1.0
org.slf4j:slf4j-api to 1.7.32
org.slf4j:slf4j-log4j12 to 1.7.32


Load messages after the given day

Following up with the UX problems mentioned in https://github.com/matrix-org/matrix-public-archive/pull/71, it would be really nice to be able to load messages after the given day:

UX problems
We can't show messages after the selected day
With /messages, we can only pick an event and paginate backwards because paginating forwards does not work properly with /backfill. And /context doesn't /backfill at all.
Because we can't get messages after the selected day, if the day doesn't have enough messages to fill up the screen, the URL will immediately change to a day before and there is no way to scroll low enough to select the day again except for the calendar.
-- https://github.com/matrix-org/matrix-public-archive/pull/71

Todo

[x] Create MSC for being able to /backfill forwards -> MSC4000
[ ] Maybe update /context/{eventId} to backfill and with the MSC, we can backfill both forwards and backwards from the given eventId. We can then use /context instead of /messages.

Given how the archive now works by showing the end of the date/time specified in the URL looking backward up to the limit, it's less clear that we actually want to do this.
The original "want" and desire for this was to be able to render the top of the date/time specified looking forwards but that just doesn't work right now because it never backfills over federation. And because we were rendering from the top, our scroll would be nicely just at the top of timeline (no monkey business to scroll to the bottom) and the date header would be visible regardless of whether we made it sticky.


refactor: remove redundant else clauses

This PR removes redundant else clauses where if statements return.

LGTM, less code is less code 👍


You are using the default TMDB api key

I have created a config.yml file and pasted in
tmdb:
  api_key: xxxxxxxxxxx

But I still get the error. Or is this expected?
 you are using the default TMDB api key; TMDB requests will be limited to 1 per second; to remove this warning please configure a personal TMDB api key

Hi @warmwhisky , I've double checked and this works for me, which suggests your config.yml is in neither one of:

the current working directory from which you're running BM
the XDG app config directory for bitmagnet on your platform

If all else fails you could set it as an environment variable TMDB_API_KEY instead...

Hi @mgdigital I have bitmagnet store in C:/bitmagnet with the following direcctory structure
C:/bitmagnet
    data (directory)
    .env
    config.yml
    docker-compose.yml

I have also tried using the .env file with the following in it too but I get the same error
TMDB_API_KEY=xxxxxxxxxxx \

I guess I am not mounting the coinfig file? Do I have to add the config to the  docker-compose.yml file?

Yes, either that or set the env var in docker-compose.yml

Unfortunelty I do not know how that is done. I guess this is why I cannot get it to work. The docs assume we know this part?

The docs are already very clear on how to do this.

I respectfully hold a different viewpoint, which is why I took the initiative to open an issue.

Jeez, either:

look again at my instructions above
look again at the docs more carefully
LOOK in your docker-compose file and see the example of how to do exactly this is already there
Google it

This isn't the Docker support hotline (their docs are also very detailed and clear) - if you can't set an environment variable (or take the initiative to find out for yourself how to do this) you probably shouldn't be using this app.
I'm sorry I bothered....

Jeez, either:
look again at my instructions above
look again at the docs more carefully
LOOK in your docker-compose file and see the example of how to do exactly this is already there
Google it
This isn't the Docker support hotline (their docs are also very detailed and clear) - if you can't set an environment variable (or take the initiative to find out for yourself how to do this) you probably shouldn't be using this app.
I'm sorry I bothered....

I think you are right. I should not be using this app.


Bug when when model properties file exists

Describe the bug
I have a dbt models directory structure like so:
Model files:

models/dir1/sub_dir1/model_a.sql,
models/dir1/sub_dir1/model_b.sql,
models/dir1/sub_dir1/model_c.sql

Model properties file: models/dir1/sub_dir1/models_schema.yml looks like this:
version: 2
models:
  - name: model_a
    description: "Something something a"

  - name: model_b
    description: "Something something b"

  - name: model_c
    description: "Something something c"

When I run this command
pre-commit run check-model-has-meta-keys --files models/dir1/sub_dir1/model_a.sql

And I get this error:
Check the model has keys in the meta part................................Failed
- hook id: check-model-has-meta-keys
- exit code: 1

Traceback (most recent call last):
  File "/Users/xxx/.cache/pre-commit/repo4nh1q0_n/py_env-python3.10/bin/check-model-has-meta-keys", line 8, in <module>
    sys.exit(main())
  File "/Users/xxx/.cache/pre-commit/repo4nh1q0_n/py_env-python3.10/lib/python3.10/site-packages/pre_commit_dbt/check_model_has_meta_keys.py", line 99, in main
    return has_meta_key(
  File "/Users/xxx/.cache/pre-commit/repo4nh1q0_n/py_env-python3.10/lib/python3.10/site-packages/pre_commit_dbt/check_model_has_meta_keys.py", line 53, in has_meta_key
    in_schemas = {
  File "/Users/xxx/.cache/pre-commit/repo4nh1q0_n/py_env-python3.10/lib/python3.10/site-packages/pre_commit_dbt/check_model_has_meta_keys.py", line 53, in <setcomp>
    in_schemas = {
  File "/Users/xxx/.cache/pre-commit/repo4nh1q0_n/py_env-python3.10/lib/python3.10/site-packages/pre_commit_dbt/utils.py", line 199, in get_model_schemas
    with open(yml_file, "r") as file:
FileNotFoundError: [Errno 2] No such file or directory: 'project-name/models/dir1/sub_dir1/models_schema.yml'

But I do have that file with the structure as seen above. What am I doing wrong?
If I either remove or comment out the models a, b, c from the properties file, then it works and passes the check-model-has-meta-keys check.
To Reproduce
Steps to reproduce the behavior:

Create project with structure above
Set pre-commit-config.yml to something like this:

repos:
  - repo: https://github.com/dbt-checkpoint/dbt-checkpoint
    rev: dd74d50dfa32617b1ddaa8f745c3dbd0d05c13e4
    hooks:
      - id: check-model-has-meta-keys
        args:
          [
            "--allow-extra-keys",
            "--meta-keys",
            "a",
            "b",
            "c",
            "d",
            "--",
          ]

dbt run --select @project-name.dir1.sub_dir1
pre-commit run check-model-has-meta-keys --files models/dir1/sub_dir1/model_a.sql

Expected behavior
I expected it to succeed or fail based on the meta keys and not crash.
Version:
commit: dd74d50dfa32617b1ddaa8f745c3dbd0d05c13e4
Additional context
I believe it's failing on this line specifically of the check_model_has_meta_keys.py
    schemas = get_model_schemas(list(ymls.values()), filenames)

which in turn calls:
def get_model_schemas(
    yml_files: Sequence[Path], filenames: Set[str], all_schemas: bool = False
) -> Generator[ModelSchema, None, None]:
    for yml_file in yml_files:
        with open(yml_file, "r") as file:
            schema = yaml.safe_load(file)
            for model in schema.get("models", []):
                if isinstance(model, dict) and model.get("name"):
                    model_name = model.get("name", "")  # pragma: no mutate
                    if model_name in filenames or all_schemas:
                        yield ModelSchema(
                            model_name=model_name,
                            file=yml_file,
                            filename=yml_file.stem,
                            schema=model,
                        )

But the problem here is that yml only has the a relative posix path but not the full path and that's causing the file not found issue:
{'models_schema': PosixPath(project-name/models/dir1/sub_dir1/models_schema.yml')}

But when I print the sql file paths I get this:
{'model_a': PosixPath('models/dir1/sub_dir1/model_a.sql')}

Why the difference? Why does one have the project-name in the path and one doesn't?
Let me know if this helps?

cc @tomsej @ssassi @BAntonellini Could you please advise? Is there any quick fix that I can do to help?

This PR #99 should fix the issue. @tomsej @BAntonellini @ssassi Do you see any issues with this?


Add instructions on setting Akri Instance OwnerReference when requesting Akri Resources

Instead of using the Akri Controller, Akri users can deploy their own Kubernetes Objects (Pods, Deployments, DaemonSets, etc) to use the Kubernetes resources created by Akri. This is explained in the Requesting Akri Resources documentation. However, if a device goes offline and an Instance is deleted, the workload will remain. A way to avoid this is to add OwnerReferences like the Akri Controller does by default. This ensures that the Pod/Deployment/Job only runs so long as the device exists:
apiVersion: v1
kind: Pod
metadata:
  name: akri-broker
  ownerReferences:
  - apiVersion: akri.sh/v0
    blockOwnerDeletion: true
    controller: true
    kind: Instance
    name: akri-udev-video-985ff9
    uid: be3363ce-c84a-4c2e-8b68-d5186d48fb7b
spec:
  containers:
  - name: akri-broker
    image: nginx:latest
    resources:
      limits:
        akri.sh/akri-udev-video-985ff9: "1"
      requests:
        akri.sh/akri-udev-video-985ff9: "1"

The uid can be obtained by running kubectl get akrii --output=json | jq ".items[].metadata.uid"
We should provide a script -- maybe a series of jqueries -- for generating the OwnerReference that can be added to a PodSpec.

We need to confirm that this does not interfere with the Controller's owner references.

@diconico07 checked. This does not interfere with the Controller's owner refs. This issue is available for anyone to pick up who wants to contribute to docs


Create Profile for Malish James

/#
/## Name
Malish James
Profile Image

/
Country
/
Uganda
Region
West Nile
Organisation
Afri-Youth Network
Languages
English (Fluently), Kakwa (Native), Juba Arabic (Very Good)
Skill 1
Media & Art
Qualifications for Skill 1

Certificate in Photography, Filmmaking, and Social Media handling.
Certificate in Digital Story Telling

Skill 2
Community & Moderation
Qualifications for Skill 2

Exactive Director Afri-Youth Network

Skill 3
None
Qualifications for Skill 3
No response
Skill 4
None
Qualifications for Skill 4
No response
describe yourself
Malish James is a highly skilled and dedicated professional with a diverse educational background and a passion for making a positive impact in the lives of others. He holds a Certificate in Videography, Digital Story Telling and Content Creation.
E-Mail
<EMAIL_ADDRESS>Phone
+256776771995
WhatsApp
+256776771995
Website
No response
Telegram
No response
GitHub
No response
LinkedIn
No response
Twitter
No response
Facebook
malishjames5
Instagram
milah104
Mastodon
No response
WikiFab
No response
Other
No response

profile created


Update loggers levels

Hello. I've tried to update the levels in the loggers (in accordance with what I stated in the previous discussion).
The level are mostly set "by feeling", though I tried to be coherent; feel free to change it according to your own feeling !

@lgeo3 could you merge this so we can bring the discussion back to https://github.com/InseeFrLab/pynsee/pull/129? I don't think it's good to have discussions in multiple places ;)


PowerShell Cmdlet - Remove-CaasVlan

Hi Guys,
I am looking to a Cmdlet Remove-CaasVlan, like Remove-CaasNetwork to use against a MCP 2.0.
Thank you
Job.

Thanks Job, adding Remove-CaasVlan and Remove-CaasNetworkDomain soon.


Add support of merging classes in withStyles

Hello,
we just migrated to tss-react in MUIv4 based project and we found a small difference in how withStyles work in MUI and here.
The difference is in maybe a special case. Here's a small example:
import InputBase from '@material-ui/core/InputBase';
import { withStyles } from 'common-ui/styles';

export const CustomInputBase = withStyles(
  InputBase,
  (theme) =>
    ({
      input: {
        backgroundColor: theme.palette.grey[50],
      },
    } as const)
);

const StyledInput = withStyles(CustomInputBase, () => ({
  input: {
     backgroundColor: 'red'
  },
}));

The problem is that StyledInput won't get red color as one would expect. The reason is that withStyles currently doesn't merge classes passed in props of the wrapping component.
I tried to add it by using mergeClasses function where I noticed another small issue. The problem is when classes doesn't contain all the keys; then the key present on classesOv would be missing in the output classes object.

Hi, thank you very much for that PR.
Sorry I didn't manage to make time to test it yet although it looks good!
I published a beta version incorporating your changes so you are not blocked until it make it to main.
3.3.2-beta.0.

@garronej Thanks for the quick reaction, I just upgraded to the beta version and it seems to work for our use-case.

I'm testing the changes right now.
I happy you're choosing to use TSS not just only out of necessity to upgrade to MUIv5. 😄

Hi @synaptiko,
Good catch on this bug, it was a pretty big one.
I got confused at first because the sniped you provided works as expected (if it's not the case for you, you might have a problem with your configuration).
Anyway I wrote another test and polished a little bit your PR that was otherwise very good.
Thanks for your contribution,

I got confused at first because the sniped you provided works as expected

I extracted it from our code and simplified it for this PR but I think I did a mistake there.
Thanks for the test, I wanted to provide it too but wasn't sure what's the right process.

No problem, you submitted a clean PR when you could just have opened an issue.


Remove Metamask from docs

It’s Luis’ wish to remove Metamask as a must-have in the docs when Frame is ready for prime time.  Could we make the docs agnostic?

Close in #99


[HOLD for payment 2024-03-22] [$500] [MEDIUM] Approved expense preview does not show GBR when submitter needs to add a bank account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @anmurali
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704819780539799
Action Performed:
Create a money request and submit it to a Collect workspace. Approve and pay as the workspace admin.
Expected Result:
After an expense is approved, the submitting user should see a GBR in the expense preview which prompts them to add a bank account by clicking in to reveal the Add bank account CTA.
Actual Result:
After an expense is approved, the submitting does not see a GBR in the expense preview, and there is no indicator that they must click in to find the Add bank account CTA.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e7910dca0f3c5b57
Upwork Job ID:<PHONE_NUMBER>600576000
Last Price Increase: 2024-01-23
Automatic offers:

cubuspl42 | Reviewer | 28131009
tienifr | Contributor | 28131010

Hey @m-natarajan were you able to reproduce this, or should we add the Needs Reproduction label?

Hello. I want to work on the issue but I'm unable to do  initial npm install.
I've got such error

As I understand from error messages project's version of react is 18 and @storybook package wants a version not higher than 17.
Please, help me resolve this issue properly. Thanks.

@happy-man
Welcome to Expensify! Please ensure to read the contributing guidelines and check out a few other issues with other contributors' proposals to get a feeling of how the Expensify process works. If you have any general questions unrelated to this issue, ask them on #expensify-open-source Slack channel.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01ecd21cecad2f34a0

@happy-man
Welcome to Expensify! Please ensure to read the contributing guidelines and check out a few other issues with other contributors' proposals to get a feeling of how the Expensify process works. If you have any general questions unrelated to this issue, ask them on #expensify-open-source Slack channel.

Hello! Thanks. How can I be added to slack channel?

@happy-man please read the contributing guidelines, this instructions for getting added to Slack are included there.

To request an invite to Slack, email<EMAIL_ADDRESS>with the subject Slack Channel Invites. We'll send you an invite!

@happy-man
Hi again!
Please ensure to read the contributing guidelines. Have you read the contributing guidelines? If you have some questions, you can also check the contributing guidelines. Sometimes, I feel that people don't read the contributing guidelines, but then I realize that it's unlikely, because two bots and four people ask them to read the contributing guidelines.

@tienifr

This is new feature, we never had it implemented.

Does this chat log clarify anything?

From https://github.com/Expensify/App/issues/34278#issuecomment-1898153759, it's mentioned that the "specifically the description" is supposed to be in the preview. But the OP in this GH issue doesn't mention about description, it's just about GBR and CTA

I think we want the submitter's expense preview (which is shown in screenshot 2) to reflect the same expense details and CTA that are shown in the approved expense preview (which is shown in screenshot 1). So for this example, that would be:

Cash > Approved

$35
Ride for BDO conference

Then when clicked, it would show the green Add bank account button (as shown in screenshot 2)
@anmurali can you confirm the above?

https://github.com/Expensify/App/issues/34278#issuecomment-1898153759 also doesn't mention anything about GBR, CTA when confirming it's a regression, so a bug so I'm not sure whether it's included in this issue's scope. Are the GBR, CTA issue mentioned in the OP a regression? Or are they new features we want to implement here.

This is reported to be a regression, and the scope of the issue is to: 1) update the expense preview to show the relevant details,  and 2) show the green Add bank account button when the expense preview is clicked. Maybe I am missing something here, but do we need to drill into whether this is 100% regression in order to solve it?

Chatted with @anmurali and it seems like this issue somehow got conflated with another issue.
For this issue, we're basically just adding a GBR to the expense preview so that the submitter knows to click in to find the existingAdd bank Account CTA.  (which already exists in the Detail view). The detailed view is in fact out of scope, as the CTA already exists.
I've updated the issue body, I think it's much more clear now but LMK if we need to drill into it further! cc'ing @tienifr since I gave you some wildly conflicting info earlier 😅 (sorry bout that!)

Makes sense, I agree that there's not much to add. Let's figure out the details in the PR.
I approve the proposal by @tienifr
C+ reviewed 🎀 👀 🎀

PR is under review

Seems like this is held up on some clarifying questions asked in the PR, I bumped that in Slack in case it was missed within the PR: https://expensify.slack.com/archives/C01GTK53T8Q/p1707427263037779

As per the PR status, the most important feedback was this thread. I bumped @tienifr.

PR is being actively reviewed.

PR is still under active review!

@stephanieelliott We're having problems with reproducing the context of this issue. It's partially my fault, as I should've caught this earlier.
Slack thread: https://expensify.slack.com/archives/C01GTK53T8Q/p1708946657174689?thread_ts=1708772104.743519&cid=C01GTK53T8Q

This is on me now, I'll do the checklist today 👍

Looks like we are working through testing on the PR

Yeah, sorry for the delay! Some things apparently changed under our feet because of the work from other PRs; we want to ensure everything is working as expected.

The PR that introduced the bug has been identified. Link to the PR:

Essentially it's a new feature fixing a "UX bug"

The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

N/A

A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

No need for additional discussion

Determine if we should create a regression test for this bug.

No

If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

N/A

All paid! Summarizing payment on this issue:

Contributor: @tienifr $500 PAID via Upwork
Contributor+: @cubuspl42 $500 PAID via Upwork

Upwork job is here: https://www.upwork.com/jobs/~01e7910dca0f3c5b57


Make the docs embeddable

Replace outdated and unmaintained help tabs on Codewars.
When ?embedded=true, add html[data-embedded="true"] as early as possible, so we can style differently.
/* Hide navigation components when embedded. */
html[data-embedded="true"] {
  & .navbar,
  & .pagination-nav,
  & .footer,
  & div[class^="docSidebarContainer"],
  & div[class^="tableOfContents"] {
    display: none;
  }
}

(can also variant embedded and use embedded:hidden)
Also, allow overriding the theme with query parameter ?theme=dark|light to match the user's setting on Codewars. This should simply change html[data-theme].

BTW cold you provide places where "Help" tab is presented, what is its topic, and eventually what are the info tooltips there? Some of them might be outdated, but all of them present some kind of information which is needed to users, and it would be worthwhile to make sure that there's corresponding information in new docs. I think that many topics from help tabs are still not present in current docs, and there will be nothing to replace them with.

Kata editor:

Kumite editor:

We can add one in the trainer.

I can also show something to let users read the tutorial before creating a kata. Probably better to provide a link to open a new tab is better for this. There's only a brief tour of the kata editor at the moment.


Add a utility to track processes liveness and basic stats

Signed-off-by: Radu Andries<EMAIL_ADDRESS>What type of PR is this?
/kind feature
*Any specific area of the project related to this PR?
/area debug-utilities

What this PR does / why we need it:
This adds a new debug utility to track process stats (from proc)
Special notes for your reviewer:
This is part of a debug image in debug-bridge and allows you to log process memory usage, CPU usage and pid

@admiral0: The label(s) area/debug-utilities cannot be applied, because the repository doesn't have them

In response to this:

Signed-off-by: Radu Andries<EMAIL_ADDRESS>What type of PR is this?
/kind feature
*Any specific area of the project related to this PR?
/area debug-utilities
What this PR does / why we need it:
This adds a new debug utility to track process stats (from proc)
Special notes for your reviewer:
This is part of a debug image in debug-bridge and allows you to log process memory usage, CPU usage and pid

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign admiral0 after the PR has been reviewed.
You can assign the PR to them by writing /assign @admiral0 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 84dd5e0d6d5b95ef6f5b5b314505221cb8320266


Issue in mbt npm install

Hi,
I am tryibg to build a mta project which has CAP and UI5 modules.
When the UI5 app is being built the system unable to reach mbt module.As in the below screenshot.

logs file
Will be helpful if anyone faced the issue and has a fix.
Thanks.
With Regards,
Joseph.
Error Log.txt

Try deleting the package-lock.json and rerun npm install.

@JOSEPHSASIKANTHREDDY Is this issue fixed for you? If so, Could you please let me know how you did it?


Turbosnap fails to upload the Storybook build

Hey, I have started using your plugin to turn on my project's turbosnap feature of chromatic. Unfortunately, after running chromatic in CI it produces this error:
Chromatic CLI v7.5.0
https://www.chromatic.com/docs/cli

Authenticating with Chromatic
    → Connecting to https://index.chromatic.com
Authenticated with Chromatic
    → Using project token '********************'
Retrieving git information
Found 3 changed files:
  .github/workflows/chromatic.yml
  packages/frontend/package.json
  packages/frontend/src/components/Tabs.tsx
Retrieved git information
    → Commit 'f0f5545' on branch 'bring-back-viz-reg'; found 1 parent build and 3 changed files
Collecting Storybook metadata
Collected Storybook metadata
    → ; no supported addons found
Initializing build
Initialized build
    → Build 44 initialized
Building your Storybook
    → Running command: yarn run storybook:build --output-dir /tmp/chromatic--2038-Bmbz7mRY2y1C --webpack-stats-json /tmp/chromatic--2038-Bmbz7mRY2y1C
    → [*                   ]
    → [ *                  ]
    → [  *                 ]
    → [   *                ]
    → [    *               ]
    → [     *              ]
    → [      *             ]
    → [       *            ]
    → [        *           ]
Storybook built in 1 minute 28 seconds
    → View build log at /home/runner/work/l2beat/l2beat/packages/frontend/build-storybook.log
Publish your built Storybook
    → Validating Storybook files
Retrieving story files affected by recent changes
    → Traversing dependencies for 3 files that changed since the last build
Could not retrieve dependency changes from lockfiles; checking package.json
Failed to retrieve dependent story files
    → Could not retrieve dependent story files.
a.map is not a function
✖ Failed to publish your built Storybook

Could not retrieve dependent story files.
a.map is not a function
→ View the full stacktrace below

If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at<EMAIL_ADDRESS>if chat is not an option.

Please provide us with the above CLI output and the following info:
{
  "timestamp": "2023-10-25T20:26:09.439Z",
  "sessionId": "814664a5-199c-402d-a9ba-f6cda197113c",
  "gitVersion": "2.42.0",
  "nodePlatform": "linux",
  "nodeVersion": "16.20.2",
  "packageManager": "yarn",
  "packageManagerVersion": "1.22.19",
  "packageName": "chromatic",
  "packageVersion": "7.5.0",
  "storybook": {
    "configDir": "",
    "staticDir": ""
  },
  "flags": {
    "allowConsoleErrors": false,
    "buildScriptName": "storybook:build",
    "exitOnceUploaded": true,
    "exitZeroOnChanges": true,
    "interactive": false,
    "onlyChanged": true,
    "projectToken": "***",
    "uploadMetadata": false,
    "zip": false,
    "junitReport": false
  },
  "configuration": {},
  "buildScript": "(cd ../.. && wsrun -p @l2beat/{shared-pure,config} -recsm build --module es6) && storybook build",
  "buildCommand": "yarn run storybook:build --output-dir /tmp/chromatic--2038-Bmbz7mRY2y1C --webpack-stats-json /tmp/chromatic--2038-Bmbz7mRY2y1C",
  "exitCode": 0,
  "exitCodeKey": "OK",
  "errorType": "TypeError",
  "errorMessage": "✖ Failed to publish your built Storybook",
  "build": {
    "id": "6539789cd23f4cb6c8e9e150",
    "number": 43
  }
}

TypeError: ✖ Failed to publish your built Storybook
Could not retrieve dependent story files.
a.map is not a function
    at GIt (/home/runner/work/_actions/chromaui/action/v1/action/register.js:999:583)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async zbi (/home/runner/work/_actions/chromaui/action/v1/action/register.js:1285:[48](https://github.com/l2beat/l2beat/actions/runs/6645749380/job/18057736321?pr=2095#step:4:49)9)
    at async FZ.task (/home/runner/work/_actions/chromaui/action/v1/action/register.js:293:12[71](https://github.com/l2beat/l2beat/actions/runs/6645749380/job/18057736321?pr=2095#step:4:72)7)
Error: non-zero exit code

I have read some GitHub issues regarding the same error but these ones claim that Webpack is a problem so I thought you may have some advice on how to solve the problem.

Can you try building your storybook separately, then providing the built files to Chromatic using --storybook-build-dir?

Can you try building your storybook separately, then providing the built files to Chromatic using --storybook-build-dir?
Sure, will do that in a minute.

Did this only start happening once you added this plugin? Can you share your .storybook/main.ts?
Well, I assumed that if I am using the vite with storybook then I need to use your plugin as without it I would not have the json file needed for Turbosnap to work.
There is a link to the commit that started messing up the upload: commit. You can check other commits but there is a mess cuz I was trying to solve it 😅

Can you try building your storybook separately, then providing the built files to Chromatic using --storybook-build-dir?

Okay, I have just locally done what you suggested and everything works. So I decided to enable the CI and it turns out it failed. The only difference I can see is that I run chromatic command inside packages/frontend directory and the CI runs it from the root folder.

Update:
I have made it work. I stopped using @chromaui/action and instead, I am doing the build and publishing manually. So, probably it is the action issue and this plugin is working correctly. You can see the change here. I thought that maybe I made some typo in @chromaui/action configuration but have not found anything like that.

Great, thanks for sharing!


Customer/sachams metadata add

Are you a current Fivetran customer?

Fivetran created PR
What change(s) does this PR introduce?

This PR introduces the ability for users to pivot out the metadata field within the respective staging models for the following source tables: charge, invoice, payment_intent, payment_method, payout, plan, refund, and subscription. To configure the metadata fields to be pivoted out a user may configure the following variables:
# dbt_project.yml

vars:
    stripe__charge_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__invoice_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__payment_intent_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__payment_method_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__payout_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__plan_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__refund_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON
    stripe__subscription_metadata: ['the', 'list', 'of', 'property', 'fields'] # Note: this is case-SENSITIVE and must match the casing of the property as it appears in the JSON

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[X] No  (please provide explanation how the change is non breaking below.)

This metadata pivot will be disabled by default and will not introduce a breaking change for existing stripe users.
Is this PR in response to a previously created Issue

[X] Yes, Issue #18
[ ] No

How did you test the PR changes?

[X] CircleCi
[ ] Other (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

[X] BigQuery
[X] Redshift
[X] Snowflake
[ ] Postgres
[ ] Databricks
[ ] Other (provide details below)

Provide an emoji that best describes your current mood

🤘
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

@sachams and @mnahkies for visibility.


first jab at writing the loadflow.md page

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

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

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs
What is the current behavior? (You can also link to an open issue here)
A link to a todo page on the https://www.powsybl.org/docs/functional-documentation.html page
What is the new behavior (if this is a feature change)?
No todo page

This is the same explanation as found in other places in the docs. We will fix them all together in another PR


Keys API - POST support

Add tests for validation and access around POSTing to create keys.
existing tests now use new POST API instead of chef-server-ctl

ping @chef/lob

:+1:


Handshake failed and timeouts

Expected Behavior
Connect to peer and be able to get responses from the API
...
Actual Behavior
The connection timeout or sends an empty response
...
Steps to Reproduce the Problem

I use base dir /opt/epoch
Once you have created your generated_keys (key and key.pub) and your keys (peer_key peer_key.pub sign_key and sign_key.pub)
Create docker container docker run -d --cpus=1 --name epoch -p 3013:3013 -p 3014:3014 -p 3015:3015 -p <IP_ADDRESS>:3113:3113 -v /opt/epoch/generated_keys:/home/epoch/node/generated_keys -v /opt/epoch/myepoch.yaml:/home/epoch/myepoch.yaml -v /opt/epoch/db:/home/epoch/node/data/mnesia -v /opt/epoch/keys:/home/epoch/node/keys -e EPOCH_CONFIG=/home/epoch/myepoch.yaml aeternity/epoch
Start it and watch it fail
optionally try curling /internal/v2/account/pub-key on any port and it timeout

Logs, error output, etc.
`08:58:37.846 [info] Synced blocks 412 - 454
08:58:54.348 [info] Synced blocks 455 - 460
08:59:04.038 [info] Connection handshake failed - timeout was from <<"<IP_ADDRESS>">>
08:59:32.162 [info] Peer "pp_2ZhkUus...Ktzxeev" - ignoring peer address changed from <IP_ADDRESS>:3115 to <IP_ADDRESS>:3015 by <IP_ADDRESS>
09:00:36.439 [info] Connection handshake failed - timeout was from <<"<IP_ADDRESS>">>
09:00:39.354 [info] Synced blocks 461 - 500
09:00:39.450 [info] Synced blocks 501 - 501
09:00:39.945 [info] Synced blocks 502 - 505
09:00:41.446 [info] Synced blocks 506 - 516
09:00:42.048 [info] Synced blocks 517 - 520
09:00:50.646 [info] Synced blocks 521 - 587
09:00:52.248 [info] Synced blocks 588 - 600
09:00:53.547 [info] Synced blocks 601 - 611
09:01:02.148 [info] Peer "pp_vJciDRY...eRCusVn" - ignoring peer address changed from <IP_ADDRESS>:3015 to <IP_ADDRESS>:3015 by <IP_ADDRESS>
09:01:02.153 [info] Peer "pp_ZoYtaYr...2qQBDM3" - ignoring peer address changed from <IP_ADDRESS>:3015 to <IP_ADDRESS>:3015 by <IP_ADDRESS>
09:01:04.749 [info] Synced blocks 612 - 700
09:15:12.868 [info] Peer "pp_ZoYtaYr...2qQBDM3" - ignoring peer address changed from <IP_ADDRESS>:3015 to <IP_ADDRESS>:3015 by <IP_ADDRESS>
09:15:12.938 [info] Connection accept failed - timeout was from <<"<IP_ADDRESS>">>
09:15:12.946 [info] Peer "pp_2ZhkUus...Ktzxeev" - ignoring peer address changed from <IP_ADDRESS>:3115 to <IP_ADDRESS>:3015 by <IP_ADDRESS>
`
yaml
sync:
port: 3015
external_port: 3015
listen_address: <IP_ADDRESS>
keys:
dir: keys
password: "XXXXXXXXXXXXXXXXXXXXXXXXX"
http:
external:
port: 3013
listen_address: <IP_ADDRESS>
internal:
port: 3113
listen_address: <IP_ADDRESS>
websocket:
channel:
port: 3014
listen_address: <IP_ADDRESS>
mining:
beneficiary: "ak_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
autostart: true
chain:
persist: true
db_path: /home/epoch/node/data/
Specifications

Virtualization: version 18.06.1-ce, build e68fc7a
Hardware specs:

RAM: 4gb
CPU: 2.4GHz 2xCores

OS: Centos 7
Node Version: aeternity/epoch:latest (36c969d29950) 0.24

Found a reference to https://github.com/aeternity/epoch/issues/1244 but that one has no clear solution and I don't want to revive a dead thread.

I am not sure if this is closely related to #1642 but fixing the mining part seems to have solved this issue as well


Alerting items cannot be isolated by tenant.

Describe the bug
There is a bug in the Alerting feature of the OpenSearch Plugin: Although users can be granted the ability to view items on the Alerting monitor or alert pages by assigning them the alerting_read_access_new role (a new role copied from alerting_read_access), the Alerting Items cannot be isolated by Tenant. This means that as long as a user’s role includes alerting_read_access_new, they can see all Alerting Items across the entire system, even if I have added a tenant specific to this user in alerting_read_access_new.
Expected behavior
I hope this bug can be fixed in the next version so that user roles can isolate alerting items by tenant.
OpenSearch Version
2.15.0
Dashboards Version
2.15.0
Plugins
Alerting
Reporting
Host/Environment (please complete the following information):

OS: Rocky Linux release 8 (x86_64)

[Catch All Triage - 1, 2, 3, 4]


Added db user and password in the connection string.

Resolves: #3217 , #2802
Relates: #3321
Relates: https://github.com/forseti-security/terraform-google-forseti/pull/291

@gkowalski-google Yeah, let's tackle that in another issue (or 2).

Terraform - Pass the user and password variables to the on_gke submodule.
Helm - Update the templates to utilize a username and password variable.

@gkowalski-google Yeah, let's tackle that in another issue (or 2).

Terraform - Pass the user and password variables to the on_gke submodule.
Helm - Update the templates to utilize a username and password variable.

New issue: https://github.com/forseti-security/forseti-security/issues/3294

@kevensen updated docker entry point, PTAL
@gkowalski-google I have done some investigation, using KMS here doesn't seem to provide any security benefits as if users can ssh to the VM, they can run gcloud command with the VM's elevated privilege to decrypt the password

@kevensen updated docker entry point, PTAL
@gkowalski-google I have done some investigation, using KMS here doesn't seem to provide any security benefits as if users can ssh to the VM, they can run gcloud command with the VM's elevated privilege to decrypt the password

Thanks for evaluating that!

Attempt to reopen


Recharge

Test Plan (Steps to test):
Things to test, in no particular order:

All data displayed as expected
Update selected variant for the subscription
Update quantity
Skip and unskip
Make a one time purchase
Change next charge date
Change delivery frequency
Change address
Cancellation

Checklist:

[x] Create a Test Plan
[x] Changes Communicated (in commits or above)
[ ] Docs Updated
[x] Storybook Updated

This subscription is yours, not mine, appearing in my list:

Update product options from overview triggers an error:

From: Mesh Gym Shorts, Black, Small, Quantity 1
To: Mesh Gym Shorts, White, Medium, Quantity 2

Unhandled shipping status style:

Update next charge date not mutating subscription data. 9/28 -> 9/29 but still seeing 9/28 on the Manage screen. After a full refresh the Manage screen updates.

Delivery frequency current value not selected.

Updating delivery frequency does not update the parent subscription.

Updating address leads to TypeError: Cannot read properties of undefined (reading 'payment_details'). Subs are now borked, so I can't test further.

Report Issue button not showing for past orders. All orders past the status where they can be skipped should show this button.

Also, oddly, images aren't loading for orders? They are for a different subscription, so something else might be amiss here.

Order Now text, current text below:

Instead it should reflect the current one-time nature:
Screen 1:
Order the same product to be processed immediately using this subscription's payment method.

This will not affect your upcoming delivery on DATE and it will not receive your standard subscription discounts.

Screen 2:
Your one-time order is being processed.

Also, I'm not seeing any indication the one-time orders are processing. Can you verify they are making their way into Recharge?

Loading and reloading behavior needs work. The loading screen looks like this:

I think a better look would be to use a skeleton, similar to purchases, and end with the No Active Subscriptions screen if nothing loads.
Also, the re-fetch behavior should be improved. Every time a switch away from the tab it reloads. This might be a separate story though. I'll file one.

I'm now seeing changes to the parent subscription data reflected, however the delay after the modal closes is odd. Can we somehow tie the isSubmitSuccessful event to the subscription object update being executed? Maybe there's another approach?

Odd behaviors with skipping orders. For instance, I skipped a Sept 12 order, with no other displayed, and suddenly I had a December 11th order then the skipped Sept 12th order.
The top / upcoming orders shown should remain consistent, their sort should stay the same, and they should only change their status when skipping / unskipping.
Also, top / upcoming orders are an ascending chronological sort that starts with the most recent order in the past and continues into the future. I believe there's a limit to how many future orders Recharge will return — 2 or 3...
Past Orders is all orders that are in the past except the most recent, and it is a reverse chronological sort.

Cancel Subscription does not work:
{
    "errors": [
        {
            "message": "Status Code: 415 Response Body: {\"error\":\"Bad Request\",\"message\":\"The server has refused to accept the request because the payload format is in an unsupported format\"}\n",
            "locations": [
                {
                    "line": 110,
                    "column": 3
                }
            ],
            "path": [
                "subscription"
            ],
            "type": "GraphQLError"
        }
    ],
    "data": {
        "subscription": null
    }
}

We will need some cancelled subs to review the Past Subscriptions features.

All amounts are off, which you already know.
The approach I would have take here is to use the transforms to process the data and create a subscription object that consistently has all calculations made — e.g., amount would be calculated once, and subscription.amount (e.g.) would be read and displayed in the various components.
I haven't dug into the code yet, so I'm not sure what your approach was, just a suggestion.

Past subscriptions need the loading skeleton treatment:

Update product no longer does anything. I've changed color / size / quantity and no changes are reflected. Not even after a full refresh.

Update payment method changes are not reflected on the subscription. They show up after a full refresh.

Skip next order button appears to act twice. First it skips the next available order, then it gives another message saying it has skipped the order after that — e.g., I skip Dec 12th, and I see two confirmation screens one after the other, saying Skipped Dec 12th, Skipped March 11th. March 11th isn't actually skipped.

Order now text has placeholder DATE in it.

Order now doesn't seem to do anything. No record of an order in Recharge or in Shopify. Am I looking in the wrong place? Maybe the onetime endpoint doesn't work?

Update delivery frequency does not seem to do anything. I changed from 90 -> 30 days and the change is not reflected. I am able to do this update in the Recharge portal.
Here's the request in the Recharge portal.
POST /subscriptions/271016815
delivery_option: 30
order_interval_frequency: 30
charge_interval_frequency: 30
order_interval_unit: day

Changing the address leads to an error like before, when the payment method wasn't associated.
I'm using this build (the most recent on the PR) https://penny-git-sc-9488-featureintegrate-recharge-wi-9dfeb3-takeshape.vercel.app/account/subscriptions. Is this correct? I'm surprised to see all these errors resurface.


Updates from the Spring 2015 semester at ELTE

Here are the pack of changes that were made during the introductory Agda course at ELTE.  It only covers the first part of the curriculum as we have only reached the section on Sigma.  Those changes are mostly about style and grammar fixes (at least I hope so) and add some more text about certain topics.  Though, I have also had to shuffle the exercises around to create some unified format.  But it requires some further hacking around Pandoc and PandocAgda make them look nice (and highlighted) as before.

Thanks, that's pretty impressive! I'll do a quick review now.

Looks great! I'll merge and set up a pull req for some further suggested changes.


Automated Package Upgrade

:tada: This PR is included in version 5.0.520 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Send timestamp inside database seed field

Here's needed follow-up change to tests https://github.com/chiselstrike/tursotest/pull/22


Payment request table and detail page

[ ] Style payment request table edit link
[ ] Style payment request detail page

All acceptance criteria visible and functional during test. Thanks! 💥


Make public static fields final

This reduces the possibility of accidents or malicious code changes vulnerability, especially as most of these fields are in the encryption-related util class.

These fields are provided to users to change the mode on purpose.

That's fine, I am not making them private, just final, so people don't change the value of AES_Algorithm class variable for example from AES to Caesar.

I chang the field of DES_Algorithm is private static final. The field of DES_Transformation is public static. If it's final, user can't change DES_Transformation to DES/ECB/PKCS5Padding.


[RFC / WIP]: Rework bundling

Some notable things:

Add code splitting
Allow multiple entrypoints which can share code.
Remove build:light for JS and move it to an environment variable (happy to change the ENV var)

@gazayas Can you double check that theme ejection still works after this?


Refactor home controller

The main motivation is to use more standard approach to handling the questions, rather than generating dynamic actions in a single controller. Further PRs (ie. the almost ready submission one) will remove summary and confirmation actions too.
The idea was to utilise the current models as much as possible and also the views. The change to all the views is very superficial even though it looks like they all changed.
I think steps we could/should take further:

Introduce context to allow accessing previously answered questions
Standardise the names of the attributes and question forms, because they don't match the ones we use in the staff application
HomeController should be just for the homepage, or renamed
move all the form models to their own Forms namespace (for example)

But this is a subject of review and agreement. Maybe we should not merge this at all.

Looks fine.  Merge when ready...

Should we turn off the codeclimate fixme check, before we merge to master and make this permanently red?


Muti-Zone and Schedule support

@acd or @Will1604 Just joined the Infinitive's team a year ago and since then I always wondered if there was a way to add multi-zone support as well as support for handling Schedules.
I currently have a 2 Zones setup so if I can send you any data so this can be added, please let me know as this would be more versatile for those who don't have the Touch Thermostat.

Heya, if you're still interested I'm definitely curious to see what a two zone setup looks like. We may be able to grok what's different by observing data coming across the bus. If you can capture traffic for 10-15 seconds and share it that'd be a good start.

@acd I completely missed your response. I'm still interested for sure. How would you like me to capture the data ?

@acd If you'd like, I could test the release for you since I have 2 zones prior you make it available for everyone (if you need to)


Add RECOVER_KEY_SAFE protocol feature

Change Description

Implement EEP-9.
Change Type
Select ONE:

[ ] Documentation

[ ] Stability bug fix

[x] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[ ] New Tests

[x] Existing Tests

[ ] Test Framework

[ ] CI System

[ ] Other

Consensus Changes

[x] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

@heifner
Thank you for the review. What do you think of recovering uncompressed public key for recovery ID from 27 to 30?

@heifner Thank you for the review. What do you think of recovering uncompressed public key for recovery ID from 27 to 30?

Sorry for the slow response. At this time we would like the uncompressed public key (if added) to come in under a different PR to keep this particular change focused on just having a recover key that does not assert.


Unify linux/windows randint with NumPy

Alternative to #4802

Wow this works?!

I hope so

Jenkins, test this please

Jenkins CI test (for commit c3dfe24c17336494527cb916566fa06cf40cbef4, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit c3dfe24c17336494527cb916566fa06cf40cbef4, target branch master) succeeded!

Windows failure is fixed! I think this should be backported.

Jenkins, test this please.

Jenkins CI test (for commit c3dfe24c17336494527cb916566fa06cf40cbef4, target branch master) succeeded!

LGTM.


fix: stop using npx for git commands

What does this PR do?
Stop relying on npx for executing git commands
What issues does this PR fix or reference?
[skip-validate-pr]

These changes look good. Have we been able to verify this fixes the problem? Is git installed so it doesn't require npx to run?

@WillieRuemmele Yes, I was able to reproduce the problem locally on node 17 and verified that this fixes it. Circle includes git on their images so we should be good


ARM build linker error since absl bump

When building in the docker container for ARM, I could not finish compilation as I got a linker error regarding the absl library.
This is fixed once I reverted this commit.
I'll add more information about the setup and the actual linker error tomorrow.

I recently faced an build error related to absl, too. I noted down: ld.lld: error: undefined symbol: absl::lts_20211102::Mutex::Lock(). In case you get the same error, you don't need to revert commit 8874b4ce0395015c0b2b3a500da8f3311dcd15d9 that switched to a newer version of absl. The problem can be fixed by rebuilding the dependency that requires absl (if I remember correctly, that was grpc). To rebuild grpc, either (a) do ./build.sh --cleanAll (maybe --cleanDeps is enough) and ./build.sh, or (b) (hacky solution that is quicker) remove thirdparty/flags/grpc_v1.38.0.install.v1.success and do ./build.sh.
Background: When we increase the version number of a dependency in software-package-versions.txt, the next run of ./build.sh downloads and builds the new version of the dependency, which also triggers a rebuild of the affected parts of DAPHNE. With absl, the problem is that it is not a direct dependency of DAPHNE, but a dependency of grpc. We download and build absl separately, because we need to apply some patch to it for some reason (*). As a consequence, ./build.sh builds the new version of absl, but doesn't rebuild grpc, since there is still the install.v1.success flag file present for grpc. I think one might have prevented this problem in 8874b4ce0395015c0b2b3a500da8f3311dcd15d9 by increasing the v1 to v2 in build.sh for grpc.
I wanted to write up this problem and its solution as an issue, but hadn't found the time yet...

(*) Since 8874b4ce0395015c0b2b3a500da8f3311dcd15d9, that patch isn't applied anymore, so maybe we should not download and build absl separately anymore, but rely on the build of grpc for that again.

Didn't think about rebuilding grpc. That's exactly the problem I had, thanks @pdamme.


Initialize Autopot thread only when there is a key configured

@afonsocdaniel  should have at least one key to start thread? or HP and SPKey must be setted?


[rv32] Expand arith.mulsi_extended before going to LLVM

This enables tosa.apply_scale to be vectorized, and thus fixes a code size regression.
Fixes: https://github.com/iree-org/iree/issues/12239

I need to write some tests


Custom babel configuration

Description
I have this in my package.json (tried the inherit way as well). But when I run ava (version 0.13.0) I get a SyntaxError: Unexpected token import.
  "ava": {
    "babel": {
      "presets": [
        "es2015",
        "stage-0"
      ]
    }
  },
  "babel": {
    "presets": [
      "es2015",
      "stage-0"
    ]
  },

In the test file itself, the import seems to work fine import server from '../index';, because the error is being reported from within the ../index.js file, so it's strange.
Environment
Node.js v5.5.0
linux 4.4.1-2-ARCH

@rightaway, add "require": ["babel-register"] to your AVA config:
  "ava": {
    "babel": {
      "presets": [
        "es2015",
        "stage-0"
      ]
    },
    "require": ["babel-register"]
  },
  "babel": {
    "presets": [
      "es2015",
      "stage-0"
    ]
  },

AVA currently only supports transpiling your test files for you. Not your source files. This is why you need to use babel-register. Note that we do intend to add the source transpilation feature at some point, so be sure to watch release notes when upgrading versions.

Now it looks like this and has resolved that problem. But I'm getting ReferenceError: regeneratorRuntime is not defined. Seems like I need babel-polyfill to solve this? But where should I define this in package.json or elsewhere?
  "ava": {
    "babel": "inherit",
    "require": ["babel-register"]
  },
  "babel": {
    "presets": [
      "es2015",
      "stage-0"
    ]
  },

Hmm. That's weird. Try npm install babel-runtime

Have just tried it but I get the same error. Any other ideas?

Can you create a project with a minimal reproduction and upload to github? It will be easier for us to troubleshoot that way.

Just require babel-polyfill also:
  "ava": {
    "babel": "inherit",
    "require": ["babel-register", "babel-polyfill"]
  },

@spudly works, thank you. Just out of curiosity, it seems like babel-register and babel-polyfill were already in my node_modules folder (probably as dependencies of other babel stuff). Is it good practice to explicitly declare both of these under devDependencies in package.json, or should I just leave it as is?

@rightaway, I would definitely add it as an explicit dev dependency.


fix: pagination page size of the property card list

Proposed Changes
Allow to change the page size of the property card list.

Implementation

Use onShowSizeChange to change the perPage
The initial value of pageSize is defautlPageSize with perPage set to

I'll check soon!

Thank you for your good changes and solid codes! I'll merge this!


Development

Changed all the documentation to sphinx-compatible .rst
Scan objects can also now be queried to allow for flexible compound querying

@monkeyman192 I observing your progress here. Just a suggestion, you should not commit in master any generated files. These can be big, will change a lot and will make the repo large. You should use gh-pages branch to have website that contains the generated doc.
my 2c

@agramfort I assume you are talking about the files in docs/generated/? They are only small .rst files. All the files that are actually generated by sphinx are indeed in the gh-pages branch. There shouldn't be any generated documentation on the master branch, only the source.
I am somewhat following the mne-bids repo as inspiration on how to do it.

what is in a folder called generated should be generated hence not be part
of the master branch.
also if you follow the mne-bids / python way of doing things your file
names should be snake_case
with not capitalized letter. Some file systems are still not case sensitive.

Ah ok, upon looking at the mne-bids repo I see that it isn't actually included in the repo.
I hadn't used sphinx before for documentation so I was trying to figure it out as I went, so thanks for the advice!
And ok, thanks, I think I meant to change to that a little while back but forgot about it :/


.ba domains

Problem
There's no whois server registered to the IANA Route Database Zone for all .ba domains.
Conclusion
That makes all .ba domains fails.

Please report to http://www.nic.ba/stream/whois/ for whois lookup


chore(main): release 3.5.0

:robot: I have created a release beep boop
3.5.0 (2024-08-26)
Features

Implement mark handler (e24b1f5)
More highlights in cursorline (0f4836a)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.5.0
:sunflower:


Fix Build Warnings (part 5): Add XML comments and remove unused variables in Csharp code

Add XML comments and remove unused variables in DefaultLoggerService.cs， ILoggerService.cs， Log4NetLoggerService.cs， LoggerServiceFactory.cs， Column.cs， EventPublisher.cs

Current coverage is 75.49%

Merging #371 into master will not affect coverage as of 0d31984

@@            master    #371   diff @@
======================================
  Files           45      45
  Stmts         4681    4681
  Branches       419     419
  Methods
======================================
  Hit           3534    3534
  Partial        179     179
  Missed         968     968

Review entire Coverage Diff as of 0d31984

Powered by Codecov. Updated on successful CI builds.

LGTM


payment steps

Why is payment separated as so many steps?
Firstly prepare payment, then submit payment, lastly confirm it.
Why not is just one step?

Check out: https://ripple.com/build/reliable-transaction-submission/#ripple-rest-submitting-and-verifying-payments

Applications should persist a record of a transaction before submitting it, in order to recover from a catastrophic failure such as a power outage


Add node options

This PR adds some functionality back into the Node type. It adds a flags and options struct to NodeIO that is accessible to all nodes.
Also added some helpful flags to publishers and subscribers for checking status.
Added a printstatus method for printing a summary of a nodes, publisher, or subscriber
The task for a subscriber is now stored inside SubscribedMessage so that it can directly access the state of the subscription task

Closes #6

https://github.com/RoboticExplorationLab/Mercury.jl/blob/a4c2ddb605c1b98c2f9b0401adf251bf1235339e/src/subscribers/zmq_subscriber.jl#L41
Should this be included in SubscriberFlags?


OSX Version

I added OSX target for version 0.1.18 (Swift 1.2):

https://github.com/ricardopereira/SwiftWebSocket/tree/rp-osx-v0.1.18

Do you want a PR?
If so, create a branch for that fix.
OSX target it's missing for the current version.

Perfect. I just merged in your update to v0.1.20. Should be Cocoapod compat.

Let me know if the merge worked for you. I did a reverse merge into a new branch and made some minor updates and tagged it. Apparently this doesn't count in the Github world as adding you to the Contributor count. I should have just let you create the PR....

Oh, no problem :+1:
You can delete the branch. I use the tagged one with carthage.
Thank you.


Disabled query is run when useQuery is nested within a usePrefetchQuery

Describe the bug
import React from "react";
import { usePrefetchQuery, useQuery } from "@tanstack/react-query";

function getTimeoutQuery() {
  return {
    queryKey: ["timeoutQuery"],
    queryFn: () =>
      new Promise((resolve) => {
        console.log("we should not be seeing this log");
        setTimeout(() => resolve("done"), 3000);
      }),
    enabled: false,
  };
}

export default function Home() {
  usePrefetchQuery(getTimeoutQuery());

  return <HomeInner />;
}

function HomeInner() {
  const timeoutQuery = useQuery(getTimeoutQuery());

  return <>{timeoutQuery.status}</>;
}

when using both usePrefetchQuery and useQuery, the query function is ran even though both queries have enabled set to false.
Your minimal, reproducible example
https://glitch.com/edit/#!/mighty-ebony-skink
Steps to reproduce

Go to the glitch.me or copy/paste the code shared above
Run the react app

Expected Behavior:

timeoutQuery.status is idle and the queryFn is not run

Actual Behavior:

timeoutQuery.status goes from pending -> success and the queryFn is run even though enabled is set to false

Expected behavior
As a user, I expected timeoutQuery.status to always be idle since the query is not enabled
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: MacOS
Browser: Arc (also saw this in jest)
Version: 1.57.2 (53036) / Chromium Engine Version 128.0.6613.85

Tanstack Query adapter
None
TanStack Query version
v5.52.2
TypeScript version
No response
Additional context
Totally recognize I could be misunderstanding usePrefetchQuery - but I was not able to find details to build a mental model of how this should work in the docs for usePrefetchQuery or for using the enabled flag

usePrefetchQuery doesn't allow for an enabled field. It's for unconditional prefetching of queries.


Signing in to wrong character

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10 Pro
Bug description
I logged into my main I log into everyday, I was taken to tutorial island like I never made an account, I logged out, tried again, then I was a completely different character in the new pvp arena, I immediately logged out again , tried on mobile and It finally logged me back into the correct account, and now Runelite signs me into the correct account.
Screenshots or videos
No response
RuneLite version
1.8.26
2.1.7
Logs
client.log
launcher.log

The issue tracker is not a support forum. Please join the Discord for questions or support.

Wasnt asking for support was attempting to report a bug. Thanks.

This doesn't sound like a bug. What exactly did RuneLite do wrong in this case that would be a bug? Sounds to me like you may have logged in to a world with a different game mode, hence appearing on tutorial island. If you launched the client after the game update, but before our client update today, the Deafult World plugin would not have been active hence you could have had some other default world selected.


Patched "render" function

Test if there is data for the current metric before trying to render the graphic.

Thanks @linuxitux - merged as 834150e (updated commit message to suit).
Pete


Convert verlet rope example to Godot 4.1

Upgrade verlet rope to Godot 4.1.
Add mouse follow behavior.
Little bit of code cleanup in string.gd.

Example of the mouse follow behavior


chore(ci): Timeout cache restoration after 2 minutes

Description

Problem*

Resolves
Summary*

On the macos-latest-xl runner, I was seeing some cache timeouts that just hung the cache step, so I'm experimenting with timeouts and continue-on-error for the step.
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Very weirdly, I've not been able to get this PR to timeout on cache download.