[monitor-opentelemetry] Update Monitor README

Packages impacted by this PR

@azure/monitor-opentelemetry

Issues associated with this PR

#26754

Describe the problem that is addressed by this PR
Updates the README with a cast to the proper type.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

/check-enforcer override


Feature Broken: Drag and Drop of scripts in Scene.

Release Type: Official Release
Version: <IP_ADDRESS>4
Platform(s): Windows
Describe the bug
For some reason you cannot drag and drop scripts to the code directly anymore, even tho they still conserve the old icons it used to have when you add them like that, the scripts added to the scene at least still works (if they are correctly coded of course).
Both scripts were StartupScript if that's relevant, but i tried to do it with other types too and it doesn't work either.
To Reproduce
Steps to reproduce the behavior:

Drag a script from your asset folder to the scene.
See the error message than appeard there.

Expected behavior
Should be possible to drag scripts from your asset folder to the scene and, after doing that, it should create an entity with a special icon with the script in there.
Screenshots
In this pictures, the project at the left is new, the project at the right is old, from before the feature was broken (i.e. before the updates start)

Cannot reproduce this - In <IP_ADDRESS>2 dragging scripts in both Viewport and object list seem to work fine.


[prototype] The new Transforms API should support different fill values for Segmentation masks than Images

🚀 The feature
While migrating the reference scripts for Segmentation to the latest API, @pmeier noticed that one of the transforms uses a different fill value for Images vs Segmentation masks:
https://github.com/pytorch/vision/blob/d367a01a18a3ae6bee13d8be3b63fd6a581ea46f/references/segmentation/transforms.py#L59-L60
The 255 value is used to encode values that the loss should ignore:
https://github.com/pytorch/vision/blob/d367a01a18a3ae6bee13d8be3b63fd6a581ea46f/references/segmentation/train.py#L39
This means that we should have different fill values for Images and Segmentation masks. Other libraries such as fvcore already do this by adding separate fill pad_value and seg_pad_value parameters.
It's worth noting that a parameter behaving similarly is interpolation only that in the case of masks it's fixed to nearest and thus it's not necessary to have 2 of them.
Motivation, pitch
Here is what needs to be done:

[ ] All eligible kernels (affine, rotate, pad, perspective, elastic, etc) that could receive a fill parameter should receive it for for SegmentationMask
[ ] Make it possible for all related Transforms (Pad, RandomZoomOut, RandomRotation, RandomAffine, ElasticTransform, FixedSizeCrop, etc) to receive different parameters for Image and Masks.
[ ] Update the tests.

Alternatives
No response
Additional context
No response
cc @vfdev-5 @bjuncek @pmeier

Done in https://github.com/pytorch/vision/pull/6599 and https://github.com/pytorch/vision/pull/6586


Add earthworm extension

Description

Quick play with Earthworm.
Earthworm is Learning English through the method of constructing sentences with conjunctions.
source code | home page
Commands

Earthworm quick to home page
Home quick to home page
Code quick to source code page
Issues quick to issues page
Pulls quick to Pulls page

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Everything in this extension could simply be quicklinks; perhaps it makes more sense to just use quicklinks?

Quicklinks is Good Idea.
But “Quicklink” can only be a single one.
It would be nice to create a collection of “Quicklink”. He should make more sense that.

Then, in the near future I'm considering making the core gameplay of our site. Offered in this extension, at the moment, he really only has a few “QuickLinks”, so it's also possible to re-request a review when I'm done!

It would make sense to add more since it just opens links, also right now two of the commands opens the same link 🙂

It would make sense to add more since it just opens links, also right now two of the commands opens the same link 🙂

I'll add more since, for now let's set it up as a draft😋


typesystem.Integer default

class testVal (typesystem.Integer):
    minimum = 1
    maximum = 8
    default = 1

The default does not work

Can you give some code about how you use testVal ?


remove en-us

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnetcore/data/ef-mvc/update-related-data.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Error in homepage. "roles" request - 404

We launched the egeria ui master project with mocks. We go to the main page, an error falls on the API request for roles and the application state does not exit "Loading"

We looked for a method for requesting "/api/users/roles", in a project with mocks, this method does not exist, so all actions in the ui project lead to 403 errors

@BaronSergo hi, i fixed the missing API Endpoint in this PR [0], thank you for the issue.
[0] - https://github.com/odpi/egeria-api-mocks/pull/9

@BaronSergo we are trying to keep odpi/egeria-api-mocks as up to date as possible with the real APIs, you might find other API endpoints that fail or are missing, you can open a PR in the https://github.com/odpi/egeria-api-mocks or a new issue here in egeria-ui or in egeria-api-mocks.


Added batch write support to overlay replicated log.

Also, modified overlay master recovery so that the state of recovery
can be inferred from the replicated log store rather than by maintain
explicit state variables, which was error prone.

Ready for review !!

Can we get review from someone on the mesos core / C++ team for the code changes here?

🚢 . Talked offline, has been reviewed by Jie.


bug: file leak in object store cache

What type of bug is this?
Other
What subsystems are affected?
Datanode
What happened?
We already implemented an object store cache in #928 , but it has a potential issue.
The LruCachePolicy keeps all active cached items in memory, and if we restart the datanode, those items are lost.We don't recover the cached items from disk when initializing the LRU cache. The cache will be reconstructed by file accessing.
So if a file is not accessed after that at all, the file is leaked on disk forever and may consume too much disk consumption.
What operating system did you use?
All os systems.
Relevant log output and stack trace
No response
How can we reproduce the bug?

Enable the object store caching by setting cache_path in storage config when using s3 or OSS.
Write and read some data.
Restart the datanode(or standalone node).
The files in cache_path may leak.

@e1ijah1  The object store cache is already an LRU cache with a maximum capacity. But the LRU cache doesn't recover the cached items from the disk when it's initialized. So the previous cached items may leak in file systems because the LRU cache doesn't manage them.
I am working on this issue at https://github.com/GreptimeTeam/greptimedb/pull/1482


Issue with correct consumer/source configuration for production

Hi,
I have a simple service (Record ingester service) where I need to consume messages present on apache pulsar to
elastic store and for that I am using com.sksamuel.pulsar4s.akka.
Messages on pulsar is produced by another service which is Record pump service.
Both these services are to be deployed separately, in production.
Here is my source:
`private val source = committableSource(consumerFn)`

This code works fine and its able to consume message from pulsar and write to ES.
However, I am not sure if we should be using MessageId.earliest when creating source
private val source = committableSource(consumerFn, Some(MessageId.earliest))
While testing, I found pros and cons of both that is without using MessageId.earliest
and with using MessageId.earliest, but none of them are suitable for production (as per my opinion).

Without using MessageId.earliest:

a. This adds a constraint that this Record ingester service has to be up before
we put start Record pump service.
b. If my record ingester service goes down (due to an issue or due to maintenance), the messages
produced on pulsar by record pump service will not get consumed after the ingester service is back up.
These messages are lost and never gets consumed.
So, I think the logic is that only those messages will be consumed which will be put on pulsar
AFTER the consumer has subscribed to that topic.
But, I don't think its acceptable in production for the reason mentioned in point a and point b.

With MessageId.earliest:
a. When we use this, any time my record ingester service comes back up (after downtime or maintenance),
it starts consuming all message since the very beginning.
I have the logic that records with same id gets overwritten at ES side, so it really doesn't do any harm
but still I don't think this is the thing - as there would be millions of messages on that topic
and it will first consume the ones that are already consumed (which is a waste).

This also to me is unacceptable in production.
Can anyone please help me out in what configuration to use which solves both cases.
I tried various configurations such as using  subscriptionInitialPosition = Some(SubscriptionInitialPosition.Earliest)
but no luck.
Complete code:
//consumer
private val consumerFn = () =>
  pulsarClient.consumer(
    ConsumerConfig(
      subscriptionName = Subscription.generate,
      topics = Seq(statementTopic),
      subscriptionType = Some(SubscriptionType.Shared)
    )
  )

  //create source
  private val source = committableSource(consumerFn)

  //create intermediate flow
  private val intermediateFlow = Flow[CommittableMessage[Array[Byte]]].map {
  committableSourceMessage =>
    val message                     = committableSourceMessage.message
    val obj: MyObject = MyObject.parseFrom(message.value)
    WriteMessage.createIndexMessage(obj.id, JsonUtil.toJson(obj))
}.via(
  ElasticsearchFlow.create(
    indexName = "myindex",
    typeName = "_doc",
    settings = ElasticsearchWriteSettings.Default,
    StringMessageWriter
  )
)

  source.via(intermediateFlow).run()

Thanks

@msg4ashish I don't believe your problem is with this library, and this tracker is really meant for bugs in this library, not general advice. You might consider joining the Pulsar slack community if you're looking to discuss your problem more generally.
My guess is you probably want to use a subscription with SubscriptionInitialPosition.Earliest and no seeking.

This adds a constraint that this Record ingester service has to be up before
we put start Record pump service.

That problem is solved using SubscriptionInitialPosition.Earliest in your ConsumerConfig.

If my record ingester service goes down (due to an issue or due to maintenance), the messages
produced on pulsar by record pump service will not get consumed after the ingester service is back up.
These messages are lost and never gets consumed.

That should not be true as long as your consumer attaches to the same subscription when the ingestion service comes back up. In your example you're using Subscription.generate directly when creating your consumer, which is probably not what you'd want in a production service. Pulsar uses the subscription to keep track of which messages have been consumed, which seems like something that'd be useful in your use case.

@gmethvin ,
Thanks for your suggestion. I did try SubscriptionInitialPosition.Earliest without any seeking and that didn't solve the issue. But let me try out taking help on slack community as you suggested.
Thanks again for your time.


Destroy PathContext

After new Path set to Flow, the contexts in the old path may be destroyed.
Why only the tail of the old path will be destroyed rather than all contexts which are not in the new path?
The commented in the following code is what I wants to do.
  /** Finds the tail of this path which is not in the given path, and destroys it. */
  public void destroyNotIn(PathContext path, PathContextFactory factory) {
    Iterator<Path> aElements = this.path.elements().iterator();
    Iterator<Path> bElements = path.path.elements().iterator();
    while (aElements.hasNext() && bElements.hasNext()) {
      Path aElement = aElements.next();
      Path bElement = bElements.next();
      if (!aElement.equals(bElement)) {
        factory.tearDownContext(contexts.get(aElement));
        break;
      }
    }
   /**
    while (aElements.hasNext()) {
      factory.tearDownContext(contexts.get(aElements.next()));
    }
  **/
  }

You are correct, I referred to this problem here as well:
https://github.com/square/flow/issues/116

PathContext is dead, and this should be fixed via KeyManager (on master now)


How to generate 33, 61, 77 files

%chk=CH4.chk
%mem=20GB
%nprocshared=12
#p opt freq b3lyp def2svp emp=gd3 scf=xqc pop=nboread
CH4
0 1
C                  0.24027460    2.82036609    0.00000000
H                  0.59692903    1.81155609    0.00000000
H                  0.59694744    3.32476428    0.87365150
H                  0.59694744    3.32476428   -0.87365150
H                 -0.82972540    2.82037927    0.00000000
$nbo FILENAME=CH4 AONAO=W33 FNAO=W61 DMNAO=W71 $end
hello，this is my input file. I use the g09 in the linux, but i can't find a 33,61,and 77 files. How do I generate the appropriate file? thanks！

Sorry I just see your issue. I'm not very active on GitHub. Has your issue been resolved? Your input file seems perfectly fine and works on my computer. If your issue is persistent, send an email to<EMAIL_ADDRESS>


[5.5] IRGen: Private opaque result types from another TU are not ABI accessible

Fix a compiler error when using a struct with a private field that has
an opaque result type in another file.
% cat A.swift
public protocol P { }
extension Int : P {}
struct Container {
  private let mem : some P = 5
}

% cat B.swift
public func doIt() {
  var x = Container()
  var y = x
}

Risk: Low. If the condition matches we will access containing struct's
metadata instead of the fields metadata.
Testing: Swift test added
Reviewed-by: Slava Pestov
Original PR #38873
rdar://76416817

@swift-ci Please test


wasmi::Module does not need to be wrapped in Arc, or does it?

Wasmi's Module already internally is an Arc, so wrapping it in an Arc has no real benefits, or am I overlooking something?
https://docs.rs/wasmi/0.39.1/src/wasmi/module/mod.rs.html#53-55
Concerning: https://docs.rs/wasmi_runtime_layer/0.39.0/wasmi_runtime_layer/struct.Module.html
Given that wasmtime_runtime_layer::Module is not an Arc wrapper:
https://docs.rs/wasmtime_runtime_layer/26.0.0/wasmtime_runtime_layer/struct.Module.html

You are correct - the Arc wrapper is left over from earlier versions of wasmi, where the Module structure was not itself Clone. I have pushed a fix to main - it will be included in the next version of wasmi_runtime_layer. Thanks!


CORS does not work with found endpoints

What version of Hono are you using?
4.6.3
What runtime/platform is your app running on?
Bun
What steps can reproduce the bug?
Creating a GET endpoint and adding cors as middleware to all endpoints
What is the expected behavior?
A header Access-Control-Allow-Origin on all endpoints
What do you see instead?
It shows a header on a non-working endpoint, but not on a found one
Additional information
No response

Middlewares should be registered before the route. Can you provide a code example?


[SPARK-49461][SS][TESTS][FOLLOWUP] Move related resource files to correct place

What changes were proposed in this pull request?

I created a new resource location sql/core/src/test/{scala/org/apache/spark/sql/streaming/resources before, moving it to the correct structured-streaming resource folder.
Why are the changes needed?

Better code structure
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test
Was this patch authored or co-authored using generative AI tooling?

No

@WweiL Shall we rerun the CI? Looks like the relevant module had failed. I guess it's not relevant, but since it's timed out and some tests may not even run...

@HeartSaVioR The tests now pass : )

Thanks! Merging to master.


playerProfile keeps the same data for every user.

Hello. Me and my friend are trying to do a simple app that would take all the steam64ids from mysql and then use the id in playerProfileRequest.
`var j = schedule.scheduleJob('*/5 * * * * *', function(){
var array = [];
con.query("SELECT * FROM counterStrikeGlobalOffensive", function (err, rows) {
	for (var i = 0; i < rows.length; i++) {
		console.log(rows[i].steam64ID);
		CSGOCli.playerProfileRequest(CSGOCli.ToAccountID(rows[i].steam64ID));
		CSGOCli.on("playerProfile", function(profile) {
			console.log(profile.account_profiles[0].ranking.rank_id);
			return;
		});
	}
});

return;
});`
This is where my problem begins. When I do console.log(rows[i].steam64ID, it returns all of the ids that are in the mysql. Then I put the id in playerProfileRequest and then when I do console.log(profile), it keeps repeating the same data for each steamid.

Don't spam the GC.

Should I set like timeout?

Wait until you get a playerProfile, then call playerProfileRequest again.

Don't use timeouts, use something like https://caolan.github.io/async/docs.html#series

Could you give me an example of I could do this? I was trying with some of my friends but we're all new to node js so we didn't get anywhere.

Something like this. I haven't tested this code, so your mileage may vary. It's not even the best way to go about it, but it should work. I specifically don't like adding a new callback every time it iterates, but I don't have any time to debug it or make it more efficient. This should help out a bit, though. The idea is that it's similar to forEach on an array, but because we have asynchronous callbacks, just using forEach will iterate over the entire array and disregard the asynchronous operations. By using the async package and the eachSeries, we don't iterate until callback() is called from within our last asynchronous operation.

One more question, how could I put all the steamids in an array like this const steamIDs = ["", "", ""];

Nvm I did it, but
CSGOCli.on("playerProfile", function(profile) { 		var rank = profile.account_profiles[0].ranking.rank_id; 		var wins = profile.account_profiles[0].ranking.wins; 		var vac = profile.account_profiles[0].vac_banned; 		sqlsss = 'UPDATE counterStrikeGlobalOffensive SET clientRank= "'+ rank +'",wins="'+ wins +'", isVACBanned="'+ vac +'" WHERE steamID  = "'+ steamID +'"'; 		console.log(sqlsss); });
it keeps printing the sqlsss + 1 every time. So like it will print once, then twice, thrice, and so on.

        const steamIDs = ["xxxxxxx", "xxxxxxxxxxx"];
        async.eachSeries(steamIDs, (steamID, callback) => {
            CSGOCli.playerProfileRequest(CSGOCli.ToAccountID(steamID));
            CSGOCli.on("playerProfile", function(profile) {
		console.log("Player Rank: " + CSGOCli.Rank.getString(profile.account_profiles[0].ranking.rank_id))

                callback();
        }   );
        }, (err) => {
            // If an error was thrown, err will be set; otherwise, we're done.
        });

I keep getting the same info for some reason :/


Make use of request queue UI

Switches the tool over to use the request queues stored in the database, rather than the queues stored in configuration files
Fixes #602 #603

This is deployed to https://accounts-dev.wmflabs.org/demo/internal.php


How do we handle nixos releases in future?

Just now we only target nixos-unstable. I am leaning into having release branches to avoid having to put conditionals in the code whenever module options changes.

Same. It depends on what is the most practical.

By the way, flakes using srvos should probably follow srvos.inputs.nixpkgs

Maybe we should also run the NixOS VM tests

By the way, flakes using srvos should probably follow srvos.inputs.nixpkgs

Not quite sure what you mean with that.

{
  inputs.srvos.url = "github:numtide/srvos";
  // somehow follow the nixpkgs version pinned by srvos
  inputs.nixpkgs.follows = "srvos.nixpkgs";
}

You would rather need access nixpkgs like that srvos.inputs.nixpkgs in your flake. I don't think there is a reverse .follows. However I often see myself in the position where I have to temporary or permanent fork nixpkgs in order to use certain fixes and changes so it might be not practically to require this.

Maybe the srvos flake could be exposed as a fake nixpkgs, like we do in nixpkgs-unfree.
inputs.nixpkgs.url = "github:numtide/srvos";

Seems a bit hacky. For nixpkgs-unfree this is fine but fore srvos it would be more transparent to use srvos.inputs.nixpkgs. Otherwise the code would need a comment or it looks like a bug.

Just a heads up that per https://github.com/numtide/srvos/commit/52fb159b7da3082859cba5faf65f4594947a96d7 the modules are no longer compatible with the nixos-23.05 channel.

I think I actually care now about 23.05 compatibility.

https://github.com/numtide/srvos/pull/191

Same. It's time to have CI test against both channels.

Based on my experience with nixos hardware, it's usually not so hard to support two channels for small code bases. It makes it easier for us since we don't need to backport and easier for the user because they don't have to pick the right branch.


Improve watch mode to reduce recompilation

Implementation for #318 and #340

Not 100% ready. Needs some cleaning up and testing.
Also, I can't figure out why, but additional builds in watch mode seem to ignore the string extraction.

additional builds in watch mode seem to ignore the string extraction.

It seems some "phantom templ generate" is also running in the background and it overwrites the file.
I am not sure what invokes it, but it seems to use some existing templ because it ignores things like adding a custom comment at the end of each line.

but it seems to use some existing templ

This was the issue. I had a running templ generate --watch that wasn't killed properly. The PR works great 👌🏾

The PR is now ready to be reviewed @a-h
Side note: I also modified writeText to use WriteLiteralString

Waiting on a review 🙏🏾 @a-h

Apologies. I want to have a good sit down and really understand it. With the holidays, I've just been picking up small stuff.
I will get on it though, I'm excited about the change. Think it will be a big improvement to dev performance.

Ready for another review @a-h

Brilliant work, thanks a lot. I think it's worth a blog post to explain the improvement, and how it's a potential game changer for development experience with templ. If you want to write it, go ahead, if not, I will - just let me know.
The next thing to deal with is to switch out the very basic "walk the directory every second" with a filesystem watcher implementation. I couldn't get fsnotify to work properly on my Mac, but maybe I was using it wrong.

Brilliant work, thanks a lot. I think it's worth a blog post to explain the improvement, and how it's a potential game changer for development experience with templ. If you want to write it, go ahead, if not, I will - just let me know.
The next thing to deal with is to switch out the very basic "walk the directory every second" with a filesystem watcher implementation. I couldn't get fsnotify to work properly on my Mac, but maybe I was using it wrong.
With that in place, the reload time will be incredible...

Hi @a-h what was the problems you encountered with fsnotify ?

Brilliant work, thanks a lot. I think it's worth a blog post to explain the improvement, and how it's a potential game changer for development experience with templ. If you want to write it, go ahead, if not, I will - just let me know.

I will write something about this. It's been too long since I wrote a blog post and this definitely deserves one.

@philippefuentes the issue I had was inconsistent notifications. Sometimes it would work, sometimes not.

Basically, the watch implementation needs some automated integration tests, including one that can be ran for extended periods to identify issues that crop up over time.


Tasks 960-967

Thanks for the PR!
Several minor suggestions, plus a concern: for the sentence completion tasks (sentence completion, missing words) I am concerned whether the task is well-defined or not. In some (many?) there are many possible responses, but the instance has listed only one possible output.

Several minor suggestions, plus a concern: for the sentence completion tasks (sentence completion, missing words) I am concerned whether the task is well-defined or not. In some (many?) there are many possible responses, but the instance has listed only one possible output. - For the sentence completion and missing words, we can derive multiple instances from a single data-point but I though by doing them we will be repeating (at least subset) input sentences in the instances. So, I would like your input on this. @aarunku5

@ssingulu, can you address the reviewer comments?


Oni2 struggles with a simple stress test

I did a simple stress test in Oni2. I start with a blank buffer. I write Hello on the first line. Then I yank the line and paste it 3 million times using 3000000p. This crashes Oni2.
I can do the same with neovim with no issues. The lines are pasted instantly. In fact, I can paste an incredible amount of lines. Neovim will accept 20 million lines without any issues.

Thanks @Apostolique ! This will be a good test case for us.
Planning on doing some stability / perf work in June prior to dropping releases. We need to build up an infra to run these sorts of tests.

A couple other stress test cases I'm interested in:

Open buffer, repeatedly (for small, medium, large files)
Switch between buffers, repeatedly
Repetitive text edits (the case you called out is a good start)

A good test might also be to define a macro and execute it a lot of times. I've noticed that in some editors emulating vim that macro's can be excruciating slow.

Yeah, Fatal error: exception Stack overflow for me, although 100k lines pastes instantly for me

Thanks for trying it out @somebody1234 ! If you run with the ONI2_DEBUG environment variable set to true - we should get a stack trace as well (which might give some clues on where in the pipeline things are failing).

The error you get on pasting is as follows:
Fatal error: exception Stack overflow
Raised by primitive operation at file "src/editor/Neovim/NeovimApi.re", line 55, characters 2-17
Called from file "list.ml", line 106, characters 12-15
Called from file "list.ml", line 106, characters 12-15
Called from file "list.ml", line 106, characters 12-15
Called from file "src/Core/Tick.re", line 33, characters 8-25
Called from file "list.ml", line 88, characters 20-23
Called from file "src/Core/Tick.re", line 39, characters 22-50
Called from file "src/Core/App.re", line 62, characters 4-23
Called from file "src/glfw.re", line 192, characters 19-31
Called from file "src/editor/bin/Oni2.re", line 166, characters 0-1

The first line is unlocking a mutex, then most of it goes into revery code by the looks of it.

Thanks @CrossR ! Looks like there is a bug somewhere in one of our handlers for messages in NeovimApi: https://github.com/onivim/oni2/blob/master/src/editor/Neovim/NeovimApi.re
(At least, one of the places where we are calling withMutex 🤔  - likely due to a large volume of notifications).

We must be using a List operation somewhere in processing these notifications that isn't tail recursive (using constant stack space).

Stack trace is pointing to a use of  List.iter: https://github.com/ocaml/ocaml/blob/20d2b67a39750ef334dad3aab13766646c523569/stdlib/list.ml#L106. But it's interesting - thought that should be tail recursive.

I've given this a try out with the latest master, and can confirm that with a libvim build I was able to past 3 + 6 million lines with no trouble. Undoing that took a moment and hung the editor until the undo completed, but I think that the terminal versions also have a hiccup on an undo that big. Scrolling after this was slower, but not very slow.
Pasting 20 million also worked, with a slight delay on paste, and very slow scrolling after.
Undoing that managed to cause the editor to hang and not respond, but I also don't know how realistic a 20 million line edit is to test with.

Nice, thanks for testing this out @CrossR ! Seems like we're improved from where we were.
It'd be nice to get the undo case working (I suspect that either libvim is sending a lot of events in that case, or we're doing something in response to a large buffer update that is problematic).
I'd also like to add some benchmark / stress tests to reason-libvim - just having some of those tests in place at that layer can help us isolate where we need to focus on performance. For example - if reason-libvim on its own, without UI, undos 20mil lines without a hiccup, we know the problem is like in the Onivim 2 layer.


Trouble executing STARTUP_SQL

I'm having some issues with my mysql instance not executing the script in the STARTUP_SQL environment variable.  Here's what I'm doing.
docker run -d --volumes-from db_vol -v /Users/me/Desktop:/tmp/sql -p 3306:3306 -e MYSQL_PASS="randompass" -e STARTUP_SQL="/tmp/sql/init_database.sql" --name mysql_box tutum/mysql
Where db_vol is a volume created per the default example in the README.  You can see I've set up a volume mapping between my desktop and the /tmp/sql directory.  I have verified that (with nsenter) that init_database.sql is indeed in /tmp/sql/init_database.sql .  From my shell into the mysql_box, I can execute the init_database.sql script by hand -- but the STARTUP_SQL variable seems to be ignored.  Is this change live on dockerhub?
Thank you!

Doesn't work for me either. I'm guessing it's because of this:
if [[ ! -d $VOLUME_HOME/mysql ]]; then
    echo "=> An empty or uninitialized MySQL volume is detected in $VOLUME_HOME"
    echo "=> Installing MySQL ..."
    if [ ! -f /usr/share/mysql/my-default.cnf ] ; then
        cp /etc/mysql/my.cnf /usr/share/mysql/my-default.cnf
    fi
    mysql_install_db > /dev/null 2>&1
    echo "=> Done!"
    echo "=> Creating admin user ..."
    CreateMySQLUser

    if [ -n "${STARTUP_SQL}" ]; then
        echo "=> Initializing DB with ${STARTUP_SQL}"
        ImportSql
    fi
else
    echo "=> Using an existing volume of MySQL"
fi

$VOLUME_HOME/mysql was already created, so it never gets to ImportSql()
https://github.com/tutumcloud/tutum-docker-mysql/blob/master/5.6/run.sh

Just checked the code, it is a PR from a user who need it for testing in development test.
https://github.com/tutumcloud/tutum-docker-mysql/pull/40
But yes, I think it is possible to put the invoke of Importsql outside the volume check statement. I will modify it soon.


support if statement in expression mapper

What kind of change does this PR introduce? (check one with "x")
[] Bugfix
[] Feature
[] Code style update (formatting, local variables)
[] Refactoring (no functional changes, no api changes)
[*] Other... Please describe: Enhancement to support if statement in the expression mapper

Fixes: #254
What is the current behavior?
Today there is no way to add if statement in expression mapping to support
What is the new behavior?
Support if statement , the if statement also supports nesting.
if string.equals("FLOGO", "FLOGO") {
     if string.equals("if", "if") {
             "Hello FLOGO IF expression"
     }
}else {
    if string.equals("TIBCO", "TIBCO") {
            "Hello TIBCO"
    }
}

The body of the if statement can be any data type.
You can take a look the if test cases which covered most of case. https://github.com/TIBCOSoftware/flogo-lib/blob/iff-expr/core/mapper/exprmapper/expression/iff_test.go

I'm concerned about this, this is no longer a simple expression language... this seems more like a general script.  Can we model this with a ternary expression?

@fm-tibco Thinking about multiple levels nested ternary expression which will be very hard to read and write.  The if/else make things more clear,  easier to maintain and read. We can think if/else just a logic function of the expression.
We had a customer POC last week, the customer wants to do a mapping base on several conditions, it invokes to have a nested if/else way.

I tend to agree with @fm-tibco. I don't think we should support essentially, scripting in an expression. We should look at another mechanism.

See comments of #254.  we'd rather to support a scripting activity than add if/else in expression mapper.


CI: Only run dependency review for upstream

This workflow fails when running on forks, which by default have it disabled.

Run actions/dependency-review-action@v3
Error: Dependency review is not supported on this repository. Please ensure that Dependency graph is enabled along with GitHub Advanced Security on private repositories, see https://github.com/hugovk/coveragepy/settings/security_analysis

https://github.com/hugovk/coveragepy/actions/runs/7418996024

This is one of those GitHub-suggested actions.  I guess you could enable it in your fork, but no one would of course, so we should disable it to prevent the failure.
TBH, I'm not exactly sure what this action is doing for me.  Looking at a recent run of it, I'm not sure it's checking any dependencies because I use quirky dependency management.  But also, coverage.py has no run-time dependencies, so, whatever?

I don't think I've seen this used anywhere else either.


Cannot get object's keys stored in state from component before render

Vue.js version
2.1.10
Reproduction
Module called users inside a Vuex store. Object data maps user ids to users, and it begins empty.
state: { data: {} }, mutations: {   setUser(state, user) {     Vue.set(state.data, user._id, user);   }, }, actions: {   fetchUser({ commit }, id) {     userService.find({ _id: id }).then((response) => {       commit('setUser', response.data[0]);     });   }
Message component with a passed property called authorId. This message will use the id try to get the author's email by searching the data object in the store. If it doesn't find it, it will dispatch an action that will fetch the user from the server and commit a mutation to add the id and user to the data object in the store. Note that for now every message has the same authorId and that the server fetching logic works as expected. A parent component fetches from server and renders multiple instances of this component.
`

{{author.email}}: {{text}}

`
What is Expected?
The expected behavior would be to see just one setUser mutation because the first message component instance will fetch and populate the store, and the next instances would use that stored value.
What is actually happening?
I see one mutation per message meaning that the call to this.author in created() or mounted() is always undefined, maybe I would expect this in the first message but not in the next ones as the store is already populated.
Doing console.log(Object.keys(this.$store.state.users.data)) in every created() or mounted() of each message instance reveals the data object is empty but I can see it has one key (authorId) and the user value in the vue dev-tools and also if I console.log(this.$store.state.users.data).
Moreover, if in the template I render {{this.user}} it will print the data correctly on every message. Also if I re-save any file, hot reloading will now print all the console.log(Object.keys(this.$store.state.users.data)) I did before again but now showing the key and value I expect instead of showing an empty object.
This also happens when returning a promise from the action and waiting for it to finish.
It seems like the state won't be ready before all message instances are rendered. If I create a new message after all have being rendered, it works.

Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or Github repository containing a set of reproducible steps that can lead to the behaviour you described. Make sure to boil down the problem as much as possible. Thanks!


PhotoView.setImageURI doesn't show and PhotoView.setImageDrawable can't be zooming, help..

PhotoView.setImageURI doesn't work and PhotoView.setImageDrawable can't be zooming,
BUT in PhotoView.setImageResource ,use local picture is normal , WHY???

Do not use setImageURI, please use a library like Picasso or Glide instead. setImageURI does not give you a callback in which you refresh the attacher. See the sample for an example with Picasso


Allow space application supporter to access specific task endpoints.

Issue
Allow space application supporter to access specific task endpoints.
Context
We are introducing a new role and we want to make sure it has the right access.
Expected result
A space application support should be able access the following endpoints:
GET /v3/tasks
PATCH /v3/tasks/:guid
POST /v3/tasks/:guid/actions/cancel
Acceptance
A space application supporter would see the same info as a space developer assigned to the same space for these and only these task endpoints.
Documentation
When I browse to any of these endpoints on v3 docs I can see the Space Application Supporter role in the list of permitted roles with an indication that this role is not fully implemented and the permissions will be changing.

duplicate issue.


V3 upgrade guide and v2 documentation

Have we got V3 upgrade guide / breaking changes and V2 documentation somewhere?
Thank you.

Hello, unfortunately not. I did not have enough time to write it :(

Thanks man no problem, I appreciate all your efforts.


Greenfield Terraform modules

Modules to include AVD Insights, Scaling Plan reformatted to modules

Great changes, thanks for the contribution


Generate timelines if flash message was not set.

Previously this code was not re-generating Policy timelines when Policy timelines options were changed on the screen. This issue does not exist on upstream or EUWE, it was addressed with PF timeline upgrade changes
https://bugzilla.redhat.com/show_bug.cgi?id=1398276
@dclarizio please review this is a Darga only fix.
before:

after:

@chessbyte change looks good, should include in darga once checks are green.


Create ar.json

Added Arabic translation

There is an error in Profile Translate Apple ID verification as well

If there something else will let you know. Thanks

Ok. Thank's

Hi
On Wed, 5 Jan. 2022, 6:11 pm Surya Hadinata, @.***>
wrote:

Ok. Thank's
—
Reply to this email directly, view it on GitHub
https://github.com/pi-apps/pi-explorer/pull/17#issuecomment-1005672665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW7Z62X6KA666SQCJALK4H3UUQ7OZANCNFSM5LE42NTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi
…
On Wed, 5 Jan. 2022, 6:11 pm Surya Hadinata, @.> wrote: Ok. Thank's — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AW7Z62X6KA666SQCJALK4H3UUQ7OZANCNFSM5LE42NTQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.Message ID: @.>

Hi

The language name is: العربية

Ok

Apple ID verification

Hello, sorry I did not understand your point, what is the profile page? In general, did the Arabic language added to the Apple ID verification? Thanks.

Hi , yes they add the Apple ID verification

Ok


how to scan time.Time?

cannot scan redis.result 2022-11-25 16:05:00.5789249 +0900 JST m=+0.000944801 into struct field Account.CreatedAt of type time.Time, error-redis.Scan(unsupported time.Time)

scan without time.Time support makes nonsense. bro time matters, especially for something like a database.

fixed #2317


ci: Add test for elemental-iso-build on PR

Now that we can modify where the artifacts are obtained from in the
script, we can tests under a PR context the validity of the script.
Also moves the script under the .github dir as it should not be on a
public facing place. Releases will be used to generate a script with the
proper tag embedded so it uses the proper tag to obtain the artifacts

Also added a comment and changed the name of the main script to make it more clear that the test is done from a external point of view, only accessing the script directly, no other interaction with the repo needed.


Automate RBAC test cases for Secrets

Automate RBAC tests for secrets

Completed.
https://github.com/rancher/rancher/pull/25171


Service assumes installation in user home

Service is looking for file in user home directory:
/home/miner/venv/bin/hermes

Because the power management needs root permission I have to run hermes as root. Therefore I don't need to assume a home dir, I have changed hermes to install into '/etc/hermes' and the service is pointing to that location as well.


Unable to register multiple codecs after 1st successful negotiation

Your environment.

Version: v3.1.24 (can be reproduced on latest master)
Browser: NA
Other Information - Created test case #2262 to reproduce the below steps

What did you do?
I saw that i'm not able to subscribe multiple tracks of different codecs if the codecs are registered on the fly (just before the transceiver has to be created). E.g. Initialise MediaEngine with 0 codecs. Steps,

say for PeerConnection offererinitialised withMediaEnginehaving no codecs registered initially and otherPeerConnection answerer` on client side with H264 and VP8 codecs registered
Some chrome based client (say 'chrome') publishes track-A with codec H264
register codec to MediaEngine of offerer pc and add this track to offerer's transceiver
do the offer/answer sdp negotiation b/w offerer and answerer pc --  ✅ Success with H264 registered in MediaEngine of offerer
'chrome' publishes another track track-B with codec VP8 ->
register codec to MediaEngine of offerer pc and add this track to offerer's transceiver
redo the offer/answer sdp negotiation b/w offerer and answerer pc --  ❌ offerer.SetRemoteDescription(answer) Fails because VP8 was not pushed to MediaEngine.negotiatedCodecs

What did you expect?
Expected SetRemoteDescription to finish without any errors
What happened?
SetRemoteDescription raised ErrUnsupportedCodec even when me.RegisterCodec(VP8) was successful.
What happens internally I saw is that the second time we call SetRemoteDescription -> updateFromRemoteDescription does not register the new codec because negotiatedVideo was set to true when the first negotiation was successful.
In ion-sfu/mediaengine.go as the subscriber pc does not have any codecs and each codec is registered when a new DownTrack is added.  This creates problem when a new track with different codec is added.

Hi @adityaa30 sorry for the late response to this. This is working as intended, you can see some of the discussion thoughts in c8b7aa38

In earlier versions of Pion it was possible to share a copy of the MediaEngine between multiple PeerConnections. This would fail when shared between multiple types of remote agents (FireFox/Chrome use different PayloadTypes etc...)
For the application you have described here I think the 'right' thing to do here is create a MediaEngine with VP8 and H264. Then if you want to force the remote to use a specific codec use SetCodecPreference on each individual transceiver.

I am going to work hard on getting tickets down to 0 this month! Sorry that I have accumulated such a backlog.


Cross-domain Canvas limitations: add try/catch and document it

Note that Canvas does have cross-domain issues much as does AJAX. Loading tiles from a remote origin will not work properly unless CORS headers are set.

Add try/catch to PixelFilter.js at that getImageData() around line 99, so it gives a more useful error message
Document this in the README so it's pretty clear, cuz folks likely don't know offhand

This round of commits greatly improves the cross-origin situation:

Documented it and gave links to other places to learn about CORS
Extended the _createTile() function to add the .crossDomain="Anonymous" attribute, so the tile is "CORS ready" if headers are available.
Added exception handling around getImageData() so that if it does fail, a more useful error message is given.


⚠ Blutopia has degraded performance

In 5c93cbe, Blutopia ($BLU) experienced degraded performance:

HTTP code: 200
Response time: 1025 ms

Resolved: Blutopia performance has improved in 95c7405 after 8 minutes.


Instagram4Android.login() -> Status "fail"

I'm setting everything up exactly as mentioned in the readme - on some devices however the login does not work. There is no Challenge-Required message and there is no suspicious Login Attempt when I log into my Instagram Account with a Desktop PC. I added a bit of output into the login() function where it checks for the status - It just says "fail".
In the Applikation there aren't even any errors... The Setup() works, the Login() works but when it comes to reading some data (e.g. the posts of a user) an Exception is thrown saying "You need to login first".
Any Ideas? Thanks in advance.

Looks like you uses another object for requests to server. You need place Instagram4Android object to Application class, then use this object for all project. I did this:
public class App extends Application {

    private static Instagram4Android sApiInstagram;

    public static void buildInstagramApi(String username, String password) {
        sApiInstagram = Instagram4Android.builder()
                .username(username)
                .password(password)
                .build();
    }

    public static Instagram4Android getApiInstagram() {
        return sApiInstagram;
    }
}

Then you need log in
apiInstagram = App.getApiInstagram();
apiInstagram.setup();
apiInstagram.login;

Then when me need make some requests I do this:
apiInstagram = App.getApiInstagram();
apiInstagram.sendRequest(...


ci: use node image for docker staging

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[feat] Support path expression for Key annotation

Support the path expression for @Key annotation like the picture above.

How about introducing a new annotation called @Path. It wouldn't inherit the parent's definition, but just query the value from the given path.
interface A {
	B some();
	interface B {
		@Path("settings.dimension.filter-null-value")
		boolean filterNullGrouping();
	}
}


Support for next js 13 server side components

The old getServerSideProps api is deprecated, and you no longer have access to the request and response objects. Instead you get access to headers and cookies.
It would be nice to have a new helper function like withIronSessionSsr for accessing the session in server side components.

This is blocking my Next.js 13 upgrade path, would love to see a resolution for this, cheers!

The issue is very urgent and critical for my project!

I still use iron-session with Next 13 to handle auth/session. My solutions is like this:
// lib/getRequestCookie.ts
import { SessionUser } from "@/api/user";
import { unsealData } from "iron-session";
import { ReadonlyRequestCookies } from "next/dist/server/app-render";

/**
 * Can be called in page/layout server component.
 * @param cookies ReadonlyRequestCookies
 * @returns SessionUser or null
 */
export async function getRequestCookie(
  cookies: ReadonlyRequestCookies
): Promise<SessionUser | null> {
  const cookieName = process.env.SESSION_COOKIE_NAME as string;
  const found = cookies.get(cookieName);

  if (!found) return null;

  const { user } = await unsealData(found.value, {
    password: process.env.SESSION_COOKIE_PASSWORD as string,
  });

  return user as unknown as SessionUser;
}

And then, in protected layout or page (preferably layout), I do:
import { cookies } from "next/headers";
import { redirect } from "next/navigation";
import { getRequestCookie } from "@/lib/getRequestCookie";

export default async function TenantLayout({
  children,
}: {
  children: React.ReactNode;
}) {
  console.log("Entering TenantLayout boundary");
  const user = await getRequestCookie(cookies());

  // Prevent non logged user to acces all pages in the tenant layout tree
  if (!user) {
    redirect("/login");
  }

  return (
    <>
      // header component
      {children}
      // footer component
    </>
  );
}

So far it works perfectly well.

Thank you @poltang! I was able to use iron-session successfully on Next.js 13 using that sample code

Thanks for sharing this @poltang. Would be great to see this added to iron-session as a one-liner like withIronSessionSsr

I agrre with you @ajsharp that it

Would be great to see this added to iron-session as a one-liner like withIronSessionSsr

But for me it's a matter of preference. Writing-wise I prefer this new approach since we don't need to write separate ssr logic like this example:
export default function SsrProfile({
  user,
}: InferGetServerSidePropsType<typeof getServerSideProps>) {
  return (
    <Layout>
      {/* Page content goes here */}
    </Layout>
  )
}

export const getServerSideProps = withIronSessionSsr(async function ({ req, res }) {
  const user = req.session.user;

  if (user === undefined) {
    res.setHeader("location", "/login");
    res.statusCode = 302;
    res.end();
    return {
      props: {
        user: { isLoggedIn: false, login: "", avatarUrl: "" } as User,
      },
    };
  }

  return {
    props: { user: req.session.user },
  };
},
sessionOptions);

With new approach this logic goes into page body with simpler code and no need to create props:
export default async function Page() {
  const user = await getRequestCookie(cookies());

  if (!user) {
    redirect("/login");
  }

  return (
    <>
      {/* Page content goes here */}
    </>
  );
}

And again, as we now have layout, we can colocate this to it and then IF we have hundreds of pages we will be grateful not to call withIronSessionSsr on every single page. And preference-wise I can change all of my pages to be ssr-ed and only use useUser() on child components deep in page tree.

Thanks for this solution @poltang, it was very useful. One thing that was still missing to me was a way to query the api passing the auth cookie. I was not really able to use the withSessionSsr, so I came up with this:
import { cookies } from 'next/headers'
async function getUser() {
    const sessionCookie = cookies().get(
        process.env.SESSION_COOKIE_NAME as string
    )
    if (sessionCookie) {
        const Cookie = `${sessionCookie.name}=${sessionCookie.value}`
        const res = await fetch(`${apiDomainAndProtocol}/api/user`, {
            headers: {
                Cookie,
            },
        })
       ...

Would you have another suggestion?

@brunoreis I'm afraid I don't understand with what you mean by query the api passing the auth cookie. All my protected APIs now share the same shape like this:
async function handler(req: NextApiRequest, res: NextApiResponse) {
  const user = req.session.user;

  if (!user) {
    return res.status(401).json( ERROR_401 );
  }

  // do some stuff
  return res.json( ERROR_404 );
}

export default withIronSessionApiRoute(handler, sessionOptions)

Add next.js-13-typescript example pls

@poltang, I think I'm still a little bit confused in this SSR world logic.
I do have an /user route that I use in frontend to access the user data and I'm hitting that api route from the ssr in order to grab the same data when rendering in the server.
In fact I don't need to grab my data through an api call, right? I'm already in the server.
:-)
Although it feels like a good thing to access data from the server and from the frontend in the exact same way.
Specially because I'm intending to write a graphql schema for data. And also because that makes it possible to transform a backend component in a client component and vice versa with no extra effort.

I also wish I could create my login, logout and signup routes in the /app directory using the new route handlers. It seems to me that withIronSessionApiRoute only works for endpoints in the pages/api directory

Is Poltang's example still the standard implementation method for using iron-session cookies with the current Next 13 app router? Or has there been anything new to newly use since the app router stable release in May?

I still use iron-session with Next 13 to handle auth/session. My solutions is like this:
// lib/getRequestCookie.ts
import { SessionUser } from "@/api/user";
import { unsealData } from "iron-session";
import { ReadonlyRequestCookies } from "next/dist/server/app-render";

/**
 * Can be called in page/layout server component.
 * @param cookies ReadonlyRequestCookies
 * @returns SessionUser or null
 */
export async function getRequestCookie(
  cookies: ReadonlyRequestCookies
): Promise<SessionUser | null> {
  const cookieName = process.env.SESSION_COOKIE_NAME as string;
  const found = cookies.get(cookieName);

  if (!found) return null;

  const { user } = await unsealData(found.value, {
    password: process.env.SESSION_COOKIE_PASSWORD as string,
  });

  return user as unknown as SessionUser;
}

And then, in protected layout or page (preferably layout), I do:
import { cookies } from "next/headers";
import { redirect } from "next/navigation";
import { getRequestCookie } from "@/lib/getRequestCookie";

export default async function TenantLayout({
  children,
}: {
  children: React.ReactNode;
}) {
  console.log("Entering TenantLayout boundary");
  const user = await getRequestCookie(cookies());

  // Prevent non logged user to acces all pages in the tenant layout tree
  if (!user) {
    redirect("/login");
  }

  return (
    <>
      // header component
      {children}
      // footer component
    </>
  );
}

So far it works perfectly well.

how to set the cookie? poltang

great solution! however, i always get undefined when using it on server component. any advice or ide?
thanks

How do we initially set cookies to the header securely with Iron Session? The code examples above are for when the cookie has been already set

i want something like iron-session that can be use in nextjs 13, i love the way iron-session ecrypt the cookie and easily get the cookie with the actual value, is there any reference?

I'm using this as of recently, which is working quite well
const ironSessionWrapper = (handler: RouteHandlerWithSession): RouteHandler => {
  return async (request, routeSegment) => {
    const cookieResponse = new Response();
    const session = await getIronSession(
      request,
      cookieResponse,
      sessionOptions
    );

    const sessionRequest = Object.assign(request, { session });
    const response = await handler(sessionRequest, routeSegment);

    const setCookie = cookieResponse.headers.get("set-cookie");
    if (setCookie) {
      response.headers.set("set-cookie", setCookie);
    }

    return response;
  };
};

I'm using this as of recently, which is working quite well
Edit: It's for Route Handlers, it might be adapted for Server Components?
export type DynamicSegments = {
  params: { slug: string } | undefined;
};

export type RouteHandler = (
  request: Request,
  routeSegment: DynamicSegments
) => Promise<Response>;

export type RouteHandlerWithSession = (
  request: Request & { session: IronSession },
  routeSegment: DynamicSegments
) => Promise<Response>;

const ironSessionWrapper = (handler: RouteHandlerWithSession): RouteHandler => {
  return async (request, routeSegment) => {
    const cookieResponse = new Response();
    const session = await getIronSession(
      request,
      cookieResponse,
      sessionOptions
    );

    const sessionRequest = Object.assign(request, { session });
    const response = await handler(sessionRequest, routeSegment);

    const setCookie = cookieResponse.headers.get("set-cookie");
    if (setCookie) {
      response.headers.set("set-cookie", setCookie);
    }

    return response;
  };
};

And using it like this:
const POST: RouteHandlerWithSession = ironSessionWrapper(async (request) => {
  request.session.destroy();
  return NextResponse.json({});
});

it work perfectly thanks erwanvivien, but i still waitting till the iron-session maintainer release the official trick or docs

Hey everyone 👋
I have Iron Session now fully working with support for NextJS App Router and Server Actions. It works without the need for wrappers and handlers.
The feature update is provided with documentation and a working example application. Please refer to my comment under the Roadmap v8 issue thread for it, being available as a pull request.
I would love your support in getting this PR approved so that we can complete the V8 branch to be pushed into the main branch to have Iron Session with NextJS 13 Server Side Components available for everyone to use.


Entering a space too much is interpreted as a word

Empty spaces should be ignored.

More annoyingly it seems entering a single word followed by a space adds an empty word to the seed phrase.


build(package.json): include chokidar dependency required by nunjucks

Include chokidar dependency required by nunjucks, this is causing issues when running the  application in
Azure.
2022-06-22T17:03:11.348461362Z /opt/app/node_modules/nunjucks/src/node-loaders.js:49
2022-06-22T17:03:11.348537763Z         throw new Error('watch requires chokidar to be installed');

Also revert previous npm and node version limits as this did not fix the issue.

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


TEST ISSUE

Description
This is a test issue.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-7.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/index.md
Document ID
1668c8fb-024c-c86d-d4d5-e22e3355c04b
Article author
guardrex

Leave open for a bit ... still working out the GH CLI command to add it to the project


use es2022 instead of es2020

closes #8980
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

We don't need to worry about this being breaking for anyone? All Cloudflare projects are continuously updated to the latest version of their JS engine? There's no setting in their dashboard for this, and projects don't default to staying on the then-latest version when they were originally created?

Am basing this on https://github.com/cloudflare/workers-sdk/pull/2720. The runtime is kept up to date for all workers. If somehow this did cause a problem for somewhere (and I'm not sure how it could, given what we know) the worker would fail to deploy — it wouldn't cause failures in production

I read that doc as "set a compatibility date in your config and workers will not upgrade beyond that", which means changing the build target likely affects some people.

Cloudflare regularly updates the Workers runtime. These updates apply to all Workers globally

They update the runtime, but they preserve old bugs

Mhm ok I read it as "runtime is part of the thing you pin", not "code on top of the runtime is what you pin", but maybe that's just me.

When it comes to syntax, it's the engine that matters, rather than the runtime, and IIUC workers always run on a recent version of V8 (because of security, and because of the economies of scale from being able to run many workers in a single process regardless of when they were first created). I'm pretty confident this change is safe. If not, we'll find out very soon!


getting activity list or any elements list fails (unicode error)

def get_elements(self, tag_name, attribute):
"""
Return elements in xml files which match with the tag name and the specific attribute
        :param tag_name: a string which specify the tag name
        :param attribute: a string which specify the attribute
    """
    l = []
    for i in self.xml:
        for item in self.xml[i].getElementsByTagName(tag_name):
            value = item.getAttributeNS(NS_ANDROID_URI, attribute)
            value = self.format_value(value).encode('ascii', 'ignore') <-- this line should be added
            l.append(str(value))
    return l

test 'callsign android app' , https://play.google.com/store/apps/details?id=com.callsign.android.app
error is
File "lib/androguard/core/bytecodes/apk.py", line 647, in get_activities
return self.get_elements("activity", "name")
File "lib/androguard/core/bytecodes/apk.py", line 569, in get_elements
value = self.format_value(value).decode('ascii', 'ignore')
UnicodeEncodeError: 'ascii' codec can't encode character u'\u0493' in position 2: ordinal not in range(128)

I have the same error when using API get_services(). Of course, get_elements() is called.
Traceback (most recent call last):
    File "test.py", line 53, in <module>
        for s in a.get_services():

    File "build/bdist.linux-x86_64/egg/androguard/core/bytecodes/apk.py", line 510, in get_services
    File "build/bdist.linux-x86_64/egg/androguard/core/bytecodes/apk.py", line 436, in get_elements
UnicodeEncodeError: 'ascii' codec can't encode characters in position 2-3: ordinal not in range(128)

Not sure which version of the code you are using. I know that master is broken as many report, but it contains a my pull request merged, where I have fixed a big mess in the encoding when reading string blocks from packed files. Try patching your version with this https://github.com/leonid-s-usov/androguard/commit/ab2fbac1b11002581a454048417a3930c7d88b32

Thanks for your answer, I'm using the last stable version. I have almost the same issue with this patch:
Traceback (most recent call last):
  File "test.py", line 53, in <module>
    for s in a.get_services():
  File "build/bdist.linux-x86_64/egg/androguard/core/bytecodes/apk.py", line 572, in get_services
  File "build/bdist.linux-x86_64/egg/androguard/core/bytecodes/apk.py", line 488, in get_elements
UnicodeEncodeError: 'ascii' codec can't encode character u'\u02ce' in position 2: ordinal not in range(128)

OK,
we don't have line matching version, but I suspect the the problematic line is
l.append(str(value))
please change str() to unicode() and try again, still having my patch applied

Thank you it's working. The encoding is in fact a mess, I'll wait your patch in the next release :).

Good to know.
I suspect that the unicode() fix will remove the crash also if the patch is not applied, but it may return a corrupt string without the patch. Would appreciate if you could confirm this.
Cheers!

Thanks for you reply,
Yes the unicode() fix removes the crash but sometimes it returns a corrupt string without the patch.

Would be great if one of you created a pull request with replacing str() to unicode() in all places, given that you possess the appropriate APKs to test on.

Indeed, it works with the unicode() without the patch (In my case).

created a pull request for the change. Please check
https://github.com/androguard/androguard/pull/159

@ranjeetDT @leonid-s-usov Can you check if this one is still an issue? I think the unicode errors are gone now?

@reox : This seems to be fixed. You can close it.


BackdropFilter has bad performance

I use BackdropFilter to has a blur filter effect, but found this widget has bad performance. The root cause is that BackdropFilterLayer has no RasterCache:
https://github.com/flutter/engine/blob/master/flow/layers/backdrop_filter_layer.cc#L23
And ImageFilterLayer has RasterCache:
https://github.com/flutter/engine/blob/master/flow/layers/image_filter_layer.cc#L68

@liyuqian Please take a look at this issue

Hi @zljj0818
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

Hi @zljj0818
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
I recommend you to use Discord channel (you can find it in https://flutter.dev/community) for asking questions like this.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

I have change the title and description. It's a performance issue of BackdropFilter. Please reopen this issue

Hi @zljj0818
Thanks for the update.
Can you please share how are you measuring the performance?

@zljj0818 is there a reason you can't use ImageFiltered in your app instead of BackdropFilter?

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


chore (setup.cfg): update request to  2.32.1

Related Issue
#1597

Newer versions of Requests have an issue with the way we pass our custom SSL context. That needs to be fixed before we can upgrade.
See https://github.com/httpie/cli/issues/1583 https://github.com/httpie/cli/issues/1581
Example:
$ https google.com

https: error: SSLError: HTTPSConnectionPool(host='google.com', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)'))) while doing a GET request to URL: https://google.com/

Fixed in v3.2.4 via #1596


[FEATURE] Add mirage-factory and mirage-fixture blueprints

This PR adds blueprints for mirage-factory and mirage-fixture as described in #51
I don't have any tests for them yet, would you like me to add the blueprint testing helpers so they can be tested?

I have a few things I'd like to add to this before it's ready. I'm going to add a description as well as the ability to pass params to generate factory properties.
It would also be possible to add to the config when adding a fixture, similar to how the route blueprint generation adds your route to the router.js (thanks to @abuiles).

That sounds awesome! Definitely give it a shot if you're up for it

What about m-fixture and m-factory as aliases? (other ideas?) I know programmers hate to type...

I'd be fine with fixture and factory personally. How about tests? I don't want to drag all that setup code in for testing without your okay first.

I actually don't know how tests work for blueprints, you're saying to make sure they actually generate the files? I'm ok without them for now.

Yeah, they run in mocha, generating an ember app, then running the generate command to verify the contents. Not very important for simple blueprints, but when the blueprint modifies exisiting content (like the route blueprint), or has complex rules to generate content (like the model blueprint), it's probably good to have.
I've actually got some more pressing things to work on right now, so I'm thinking I'll take the additional functionality I've listed above and break it into another issue to implement later. Then we can take the time to add the additional support for the tests.

gotcha - so I can go ahead and merge this, and we'll track the other features in a different issue?

Actually let me change the blueprint names to fixture and factory first.

I went with factory and fixture. I looked through and there was only one other project using a fixture blueprint and it's not likely the two projects would be used together.
This is ready to go :+1:

thanks mate!


Why are images needed?

Hi,
I'm trying to run inference on manually collected data that does not include images and I keep on getting assertion errors where the code is checking for images. I can't find anything in defualt.yml for disabling this behavior either.
Are the images actually needed? Based on the paper the only input should be pointcloud.
Thanks!

the images are used for filter the pointcloud

So is there a possibility to only use the pointcloud without images?

the images are used for filter the pointcloud

I want to use olny lidar of 32 lines collected by us， the network can work？

the images are used for filter the pointcloud

How to use images to filter point clouds？Is it to filter out the point cloud outside the image range?

Any findings on this thread? I too want to use only point cloud for training the network


agreementDetails validation and set frameworkAgreementVersion automatically

Added JSON schema validation for agreementDetails which only allows
signerName, signerRole, signerUserId, frameworkAgreementVersion fields, along with the required validation for each of those fields. In time agreementDetails will soon be used for storing countersigning fields as well but that is not in our story scope at the moment and so those fields have not yet been added to the schema. This schema validation is then used in our API endpoint.

agreementDetails will only be set if the relevant framework has a frameworkAgreementVersion. This will allow the previous signing process to run as normal.

The user process for adding fields to agreementDetails will not see all required fields set at the same time due to a multipage form / multistep process. Therefore we introduce validate_agreement_details_data function which allows us to override which fields are required (if not all as set in the JSON schema). This is a similar pattern that has been used in other apps. Example usage will allow us to set signerName and signerRole without having to set uploaderUserID until the next step.

If agreementReturned is set for a supplier framework then we will set agreementDetails.frameworkAgreementVersion to that of the relevant framework's agreement version.

If agreementReturned is unset then we will also unset agreementDetails.

The endpoint will allow agreementDetails.frameworkAgreementVersion to be updated but only in the case when the agreement is already marked as returned. It is anticipated that this behaviour will not actually be needed but does allow us the ability just in case.

Note, we used a slightly roundabout way of assigning interest_record.agreement_details due to SQLAlchemy not picking up internal changes to agreementDetails. (It may be possible to rewrite this in a more straightforward way if one of @risicle's two propsed pull requests are accepted.)

We store the uploaderUserId. Later on in our apps we will use this data to show information related to the uploaderUser, such as their name and email address. So this can happen easily we have added to SupplierFramework.serialize() to include uploaderUserName and uploaderUserEmail in agreementDetails if there is a uploaderUserId.

Tidying up of test code to move from using assert_* functions to use the assert keyword plainly i.e. using assert a == b rather than assert_equal(a,b).

Some older tests have had their method names updated so they reflect clearly what they are doing e.g. test_pass_fail_update_creates_audit_event to test_changing_on_framework_to_passed_creates_audit_event

minor nitpick, but I think this is good now :+1:


SCRD-5562 remove componentWillReceiveProps hook

Removes deprecated componentWillReceiveProps life cycle callback.

@guglo @GarySmith  do either of you remember what the firstValidate logic was added for to begin with? I'm trying to find a scenario where it actually triggers... I'm not seeing validation until a value is added/changed

@jeremy-moffitt It looks like firstValidate was added in this PR

@GarySmith I should've phrased that differently, I'm trying to understand why we need the logic that was in the componentwillmount in the first place... though I ran into some other issues anyway

I think that the componentWillReceiveProps was used because for whatever reason the yaml and j2 editors update their props late not on instantiation like this PR requires right now.

Using componentWIllReceiveProps is a hack to support an anti-pattern. Here's the gist of it. If you have a component that you always instantiate in the render function of the parent, but use some alternate mechanism like a show property to selectively hide it when you don't want it shown, then the component will only be instantiated once ever.  The only kind of components that should have such a hide/show component are those with content that never changes, like maybe our loading mask. If a component needs to render differently based on properties that are passed in (i.e. nearly every react component) and it uses this crummy hide/show flag, then you have to use componentWIllReceiveProps to grab those new properties and forceably re-render.
That is exactly the opposite of how react is designed to work.

The yml files work fine, but I'm still seeing issues with the .j2 editor on the validation page, the j2 files are coming up empty for me, are you seeing differently?

LGTM still, and this time I actually tried the j2 editor


Automated cherry pick of #9778: fix(region): avoid auzre request timeout

Cherry pick of #9778 on release/3.7.
#9778: fix(region): avoid auzre request timeout

Codecov Report

Merging #9779 (d3a5317) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9779       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/keystone/tokens/payloads.go

... and 662 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9779 (d3a5317) into release/3.7 (56d583e) will increase coverage by 2.06%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.7   #9779       +/-   ##
===============================================
+ Coverage         6.00%   8.06%    +2.06%
===============================================
  Files              845     107      -738
  Lines           131245   12978   -118267
===============================================
- Hits              7879    1047     -6832
+ Misses          122665   11811   -110854
+ Partials           701     120      -581

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/host.go
0.77% <0.00%> (ø)

pkg/multicloud/esxi/image.go
0.00% <ø> (ø)

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/snapshot.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storage.go
0.00% <ø> (ø)

pkg/multicloud/esxi/storagecache.go
0.00% <ø> (ø)

pkg/multicloud/esxi/template.go
0.00% <ø> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <ø> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/keystone/tokens/payloads.go

... and 662 more

Continue to review full report at Codecov.

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


Functionality broken in Sublime Text 4

Functionality is broken in Sublime Text 4.  They changed some APIs, and it uses Python 3.9 now, although I'm unsure of the exact details.
Is this project still being maintained?  Any chance of getting an updated version that works with ST4?

As a workaround, if you unzip the sublime-package (you can find the path in the console window when it errors), you can change the version in the  .python-version file from 3.4.3 to 3.8 (or 3.3) and it appears to work correctly. There's PR already open.

I'm also still having this issue.
This was also mentioned in issue #47, but the creator of that thread closed it...

Looks like merge #48 fixes the issue. The owners of the repo just need to test it and merge it.

Sublime Text has two built-in python interpreter versions, namely 3.3 and 3.x, of which 3.3 will not change, and 3.x will change with version updates.
The ST plug-in uses version 3.3 by default when it does not specify an interpreter.
But sublime_docblockr_python uses .python_version to specify an interpreter version 3.4.3 that has been used and is now invalid, causing the plug-in to not work properly.
Now this repository is no longer updated. It is not recommended to use this .python-version file anymore, just delete it and it will be normal.

Now this repository is no longer updated. It is not recommended to use this .python-version file anymore, just delete it and it will be normal.

How to do that if there is only the DocBlockr_Python.sublime-package file in ST4 config folder?

How to do that if there is only the DocBlockr_Python.sublime-package file in ST4 config folder?

DocBlockr_Python.sublime-package is essentially a compressed file, you can rename it to DocBlockr_Python.zip, then unzip it, and delete the .python-version file.
Then you should recompress it to a zip file, and rename it to DocBlockr_Python.sublime-package.
Finally, copy or move the new DocBlockr_Python.sublime-package to the Installed Packages directory.

I ended up personally just switching to this, and it's been quite a nice replacement for this old package
https://packagecontrol.io/packages/AutoDocstring

Try it: https://github.com/thep0y/python-docblockr/releases/tag/v1.8.0


Update README.md

Add description of vibrate props to README, and point out the npm packeage isn't the latest version.

@dankerri wouldn't it be better to update the module to account for the updated package?

Could I ask when do you plan to update the package? Maybe we should keep this until you finish it.

I'm currently only contributing essential fixes to this repo, and won't be able to take on implementing the additional scope in the short term. Will accept PRs updating the package.

Closing this due to lack of activity, please reopen if still relevant


[Enhancement] Enhance dubbo common logger

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Our common logger is a logging facade just like SLF4J.
We can enhance it to support parametrized logging
We have many places like this:
if (logger.isInfoEnabled()) {
                logger.info("aaa" + "bbb" + "ccc");
}

We are using logging guard to avoid unnecessary string concatenate.
With the support of parametrized logging, this can be simplified just like:
logger.debug("Hello world {} {} and {}", a, b, c);

Similar feature discribed in SLF4j:
https://www.slf4j.org/faq.html#logging_performance
Question: Any other points can be enhanced?

After some similar discuss in #3438
I'll close this for now.


Add support for AWS GovCloud regions to the ALB Provider

Hey, I just made a Pull Request!

Addresses #24020 by adding support for AWS GovCloud (US) regions to the AWS ALB provider.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@cftad I pulled your changes locally into our deployment and I was able to confirm these updates resolve the issue. Not sure if there is any way I can provide screenshots for evidence though as it's all happening on the backend.
Thanks for working this with such a quick turnaround! Looking forward to getting this change merged in officially

@Rugvip - Possible to get your 👀 on this PR so we can get it into the upcoming release? 😊


removed android:required="false" from androids "uses-permission" tag

"uses-permission" tag has no "required" attribute (https://developer.android.com/guide/topics/manifest/uses-permission-element).
see also: https://github.com/bitpay/cordova-plugin-qrscanner/issues/111

YES :) Please integrate this PR ... it's super annoying to handle projects with multiple camera permissions, you have to fix the permissions always manually

Could you integrate this, please :) ? This would help a lot


Fix/#716

Description:
To avoid NoSuchVar error, we put the orig variable in the export_type function
To avoid TypeUsedAsVar error, I add in_export_named var in ctx, because if we use named export, the export type is alias

BREAKING CHANGE:

Related issue (if exists):
fix #716

Can you rebase this PR? I think both of these patches are required

Thanks, I rebased


Definitions

What is the "developer key" mentioned in the explanation of vary-by-developer?
It doesn't seem to be the API keys from a subscription since from what I understand those do not vary by developer.
Similarly, what "user role" is referred to in vary-by-developer-group?

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

ID: 181c69b0-e136-426b-02f5-4a1a8f0f419d
Version Independent ID: 2e57c2f1-fc01-17c9-cd94-920b582e6aa2
Content: Azure API Management caching policies
Content Source: articles/api-management/api-management-caching-policies.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

Hello @dcbrown16
Thank you for your feedback! We will investigate and get back to you with our findings.

Hi @dcbrown16 Pretty sure "developer key" refers to subscription keys and "user role" refers to a group that the user is associated with.
@vladvino any thoughts on this?

@vladvino Can you confirm please. Happy to create the PR :-)

@mike-urnun-msft you are correct!

Hey @dcbrown16 We've updated the doc to ensure consistency:

"developer key" is updated to read "subscription key" and links to its respective doc
"user role" is updated to read "user group" and links to its respective doc

Thanks again for your contribution & helping us drive improvements towards MS Docs! We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Choose first account from accounts by default

When I open up an app, it asks me permission to read my accounts but will not choose an address in the login field
expected behaviour would be to select first address by default

@yangwao I'll try to do this

It had some bug afaik 👀

Closing in favour https://github.com/kodadot/nft-gallery/issues/837


how to delete previous version?

Hi, sorry for late reply, away on holidays.
About deleting old files and folders, where do they sit? I download new version in download folder and run the app file from there. But where does that old version app folder/file sit?
Is there any step by step guideline?
How do i know that the most recent version is running? Does it show version label anyehere?
Thanks

The same Way all other Files and Folder can be deleted on a Windows PC
https://github.com/Fragtality/Fenix2GSX/issues/28#issuecomment-1686222471


Any way to make the Proxy Class Generator tool skip certain folders?

Is your feature request related to a problem? Please describe.
I have a _nodeploy folder in my root IPS folder that contains several old css files, themes, cms pages, etc. that I keep for tracking changes and other things. When I run the Proxy Class Generator tool it also picks up all the files in that folder and throws errors because they are not properly formatted like a normal/proper IPS file.
Describe the solution you'd like
Either make tool search only inside the default IPS folders (admin, applications, dev, etc.) or maybe add a setting to exclude specific folders by path/name?
Describe alternatives you've considered
It took me quite a while to track down what the issue was since, at first, I thought it was a new bug with the 4.6 version that wasn't fixed yet. For now the simple solution I've come up with is to temporarily move the _nodeploy folder outside of where the IPS suite files are, run the tool, and then move back the folder. While I don't run the tool that often, it's still an annoying step.

yes in toolbox/sources/Proxy/Proxyclass/Proxyclass.php, go to method "excludeDir" (currently on line 641 of the latest), and you can add the folder name or the relative path, and the generator should skip that directory.  you can also do the same thing for files, in the excludedFiles method for files.

in the latest commit, if in your IPS root directory (where conf_global.php can be found) if you added a file called "excluded.php" and include 2 arrays like this:
`<?php
$excludeFolders = [
'Foo'
];
$excludeFiles = [
'Foo.php'
];`
proxyclass generator will check if this file exists, include it and merge the results with excludeDirs and excludeFiles methods in proxyclass.


Include in Scope - no complex url handled

Hello, I started using this automation few days ago.
When I try to add url in scope like: https://example.com/ the scan is correctly performed and burp returns issues.
But if I try to add a url like https://example.com:443/ no issues are returned.
The expected behaviour is which a url with port is handled as advanced scope management.
What I'm missing? Or there is a bug?
Regards, Arcangelo.

This issue should be fixed in master. It would be great if you could compile the extension from master and do a bit of testing. Thanks!


Garo Assilian - UI/UX - Challenge 1 - Karaoke Needs Words

Starting up

After pulling project, cd into ui/ux/challenge1
run npm install or yarn.
run npm start
url is in : localhost:3000

Features

Takes the name of any artist and return top 10 songs from artist.
Able to sort by track name, number of lyrics in song, and by artist name by clicking on appropriate row header.
Re-clicking on same header will change sort order between ascending and descending.
Can fetch 10 more results by clicking on the Get more results on the bottom of the track list. This will fetch another 10 songs.
Clicking on any song will display the lyrics for that song. Clicking on same song again will hide lyrics.
Making an empty search will return 10 random songs.

Process
I wanted to use React to develop this project, so I've used create-react-app to start it up. This allowed me to dive right into the development.
I've used axios in order to make the ajax calls to the MusixMatch API. Axios allows me to create a custom instance and define a base URL with header.
Generally, I would have the apikey hidden in a dotenv file, however I decided to forgo this step in order to make pulling and starting up the project easier.
Pursuant to the in-person tech interview, I decided to use async await for the calls to be API as I wanted to learn more about them.
For the CSS framework, I decided to go with Bootstrap and reactstrap as it offers great components to use for a React app such as this one.
All important files are found within the src folder. The Components folder contains all the React components and the services folder contains the API calls and the AxiosInstance.
In order to get the information I need whilst minimizing the API calls, I decided to use the track.search endpoint, and then use the track.lyrics.get endpoint. This allowed me to fetch all the required information for the project all at once. I only make more calls when the user wants to fetch more tracks to sing to. I also added a filter to get the most popular songs from an artist.
Note
This PR isn't actually 10K + lines long. Length is due to the yarn.lock file.

Hi @GaroAssilian ,
tx for taking the time for this challenge. You rock!
Can I ask a little bit more?

There are several warning messages on the console. Can you fix them?
ReactJS has a "new way" of creating components with state without the use of classes. Can you follow the same pattern they have here: https://reactjs.org/docs/hooks-intro.html. Instead of using regular functions, use arrow functions.
At byond we use jss instead of css. Can you try using that instead? https://cssinjs.org/react-jss/?v=v10.0.0-alpha.22
Can you also trigger the search when the user hit enter?

Oh, can you also add a few tests?

@tveronezi Hey!
Thank you for taking the time to review the challenge and for the feedback! I had fun building it and would love to improve upon it.
I was able to take a look at the React Hooks as well as JSS and am very excited to dive into them and integrate them into the project, they both look very interesting to use. I'll be making all of the other improvements as well.
Regarding a timeframe, I can have it done by the end of the day this Friday. Is this acceptable?

@tveronezi Hi,
I've just finished making all of the requested changes! Here are some notes about what was done and as well as some improvements I can make in the future:
Changes

Enter button will now trigger search. As long as the search is being made, user cannot make another search.
All react components are now functions and use the useState React hook.
Integrated JSS into project. npm currently only have version 8.6.1 so I have decided to work with this stable version. Pursuant to this, moved all styles to the styles.js file and deleted the .css file.
Removed duplicate key console errors -- problem was that the Get More Results and Search button did not behave in the same way.
Wrote tests for all components. They can be found in the Tests folder under src. I used AirBnB's enzyme in order to write my tests. All tests can be run by running npm test within the challenge-1 folder.

NOTES / IMPROVEMENTS

Due to components now being functions and using the new React Hooks for the state, the tests were a little tricky to get right since Enzyme could no longer access the state. After some research, what I did to resolve this issue was to mock the useState hook within the tests and then check to see if the setState method had been called with the correct values.
I wanted to test the axios calls as well using axios-mock-adapter, however I was having a bit of trouble with it.
I looked at other testing frameworks such as react-testing-library (https://github.com/testing-library/react-testing-library). I wanted however to dig deeper using enzyme to figure out how I can make it work with the React Hooks.

Hi again!
I had forgotten to mention to run yarn or npm install prior to starting up the project as I have added new dependencies.

tx!


H3 support

How difficult would adding h3 cell support be given that deck.gl already supports it?  Would it be possible to quickly list the steps that are required to add another feature layer type?

The steps required for a new layer type are:

Add JavaScript support for the layer type to https://github.com/geoarrow/deck.gl-layers, ensuring that you're using deck.gl's support for binary attributes. For an example you can see the PR for the GeoArrowTextLayer.
Add a new layer model in the JavaScript bindings of lonboard to sync layer state from Python and pass it into @geoarrow/deck.gl-layers. E.g. https://github.com/developmentseed/lonboard/blob/cc40061e63a93b0ce736fbd14cd55b2cbab53a01/src/model/layer.ts#L576-L662
Add a new Python class in the Python part of lonboard to pass data from Python into JavaScript. E.g. https://github.com/developmentseed/lonboard/blob/cc40061e63a93b0ce736fbd14cd55b2cbab53a01/lonboard/_layer.py#L409-L599
Add a page to the API documentation: https://github.com/developmentseed/lonboard/blob/main/docs/api/layers/scatterplot-layer.md

In the case of H3 support specifically, deck.gl has an H3ClusterLayer which clusters points into H3 cells on the frontend and an H3HexagonLayer which renders hexagons from h3 cell id input. I assume in this case you're referring to the latter one. I already added GeoArrowH3HexagonLayer to @geoarrow/deck.gl-layers, so in this case we only need steps 2-4.


Use an in-memory Knex database in unit tests

Is your feature request related to a problem? Please describe.
Some of the Knex related unit tests are creating a SQLite database file and cleaning it up after each test runs. This marginally impacts test completion time, and sometimes the files do not successfully get removed if tests are stopped early, which can make them susceptible to being committed to source control.
Describe the solution you'd like
Where possible we should use the in-memory database available when using Knex.js.
This solution may not be appropriate for all test suites, they need to be assessed on an individual basis.

Automatically generated comment to notify maintainers
/cc @machi1990, @wtrocki

I'd like to work on this. Can you please tell me which tests are being referred here?

Hi @RinkiyaKeDad, doing a .sqlite search on the project will reveal which test files using the file for storage. There is still a couple of them. I'll take one example file for further clarification.
Le'ts take the file:
https://github.com/aerogear/graphback/blob/master/packages/graphback-runtime-knex/tests/service/DefaultCRUDService.test.ts
You can see that, Knex is configured to use sqlite database with a connection to a file system:
https://github.com/aerogear/graphback/blob/master/packages/graphback-runtime-knex/tests/service/DefaultCRUDService.test.ts#L36
The idea here will be to use an in memory database like: https://github.com/aerogear/graphback/blob/master/packages/graphback-runtime-knex/tests/knexQueryMapper.test.ts#L12
To improve test speed and also make sure that we do not have to worry about the database file being left around.
https://github.com/aerogear/graphback/blob/master/packages/graphback-runtime-knex/tests/service/DefaultCRUDService.test.ts#L15-L19
The patch needs to be applied to all occurrences where a connection to a file system is used to setup the database. Thanks.

I actually think now that this will not work at all - the problem is that migrateDB does not accept a database, just a config which it uses to create a connection. This creates two separate in-memory databases (one during migrations) and another in the tests but this one does not have the migration history.


android: add support for registering a platform KV store

Description: This PR allows platform implementations of a generic (and potentially persistent) key-value store to be registered with the Engine. Internal components can look up these implementations by name. The internal implementation and wiring in this PR is platform agnostic, but this PR adds a public API for Java/Kotlin only, initially. iOS and other public APIs to follow in upcoming PRs.
Part of #2077.
Risk Level: Low
Testing: New Unit + Integration Coverage
Signed-off-by: Mike Schore<EMAIL_ADDRESS>

Nice! A few small comments. I think it would also be nice to flesh out the PR description to explain a bit more the details of what's going on.

👍

Can you please add a changelog entry for the user-facing change?


nextjs - getPresignedUrl returns 404 / File not found

This only happens on page reload if initialNhostSession={nhostSession} is set in NhostProvider. The authorization header is missing in the request when it fails.

Just updated all nhost packages to the latest version and it's working now 👍