fix(eventListener): use the correct WTF issue array to iterate on

It seems that zone.js iterates on the wrong array while considering WTF issue. This results in a lot of unnecessary iterations and object creations. Although it seems that the main functionality is not affected.

@jahtalab , thank you for the fix, this my typo, LGTM.

@jahtalab, could you rebase your PR, the CI failed because your .travis.yml still using nodejs 6.

@jahtalab, sorry this PR takes so long, the PR doesn't been merged because it need rebase, now zone.js has been moved to angular/angular https://github.com/angular/angular/tree/master/packages/zone.js, could you re-create this PR there?
Thanks.

https://github.com/angular/angular/pull/31208


Add Table File Replication Factor Property to the Accumulo-store properties

The accumulo-store properties should enable a user to set a replication factor to be used on table creation for file replication in HDFS instead of just using the accumulo default setting.

Merged into develop.


disable default metrics scraping in dependency charts

pod annotations changes like formatting and removal of default /metrics path annotations
use metrics/internal instead of metrics/general in otelCollector config

Signed-off-by: Prashant Shahi<EMAIL_ADDRESS>

I understand why you are disabling this. With this change in place, How are the collector metrics for each custom collected?

How are the collector metrics for each custom collected?

They will still be collected as the same way it is.
Since, we have only removed it from dependency chart itself but overridden at SigNoz main chart values.yaml.


Login Issue

i have a login issue i have just installed it for the first time but keep getting a error every time i try to login it keeps saying Company disabled due to payment can someone please help i have had a read through the issues to see if there was any fixes and i cannot find the billing_date in table settings so please can someone advise thanks in advance

Same problem.

I have also hit in the same problem

expire_date
it this the correct way? pleae tell us

expire_date` datetime NOT NULL '3018-01-01 00:00:00',

I am closing the issue as @yamcell pointed out the solution to this problem.


halt() methods force handlers to return Object

Maybe more of a question; in the project I'm working on I noticed several handler methods that returned Object while actually they should return String (JSON payloads).
On closer inspection this is because internally they were calling halt() to signal a server error or 404 Not Found in certain situations.
Since the methods called halt instead of doing throw halt() the compiler forces a return statement, and since it's either returning a String or an exception (which is thrown but never returned anyway) the return type had to be Object.
I've made a fork and changed the return to void, and the build still works with all tests passing.
Is there any particular reason for the signature of the static halt() methods?

the signature of the halt() methods are very old and the forcing of return is purely from limitations in Java. I'm not on a device with an IDE but wouldn't:
`return halt(404, "not found"); work?

Probably not, since that method still as a return type of HaltException where to me it seems it should be void (the method is a one-liner which throws an exception, so it's guaranteed to never return anything).
For clarification see this commit, after this the project build still completes without errors:
https://github.com/tonvanbart/spark/commit/7218618d823882151acbcdd55898647c86642409

@perwendel Hi, any update on this, or is there no time/priority?

I usually throw halt instead of return halt


Add a binary search algorithm implementation

Hello!  Here is my version of the binary search algorithm.
If you have any suggestions or spot any bugs, please let me know!
Thank you ^_^
Viva la Hacktoberfest!

Thank you for contributing to Algorithms/Python, your pr got merged! ✨


Configuration of outgoing RTX streams

Makes RTCRtpSender capable of configuring RTX streams.
Incoming RTX streams are already handled at the SDP/SDES layer and then processed by RTCRtpReceiver::receive_for_rtx. This means interceptors can bind to remote RTX streams. This PR aims to do the same for local streams. This is related to, but not a full fix for https://github.com/webrtc-rs/webrtc/issues/295 since it doesn't implement the retransmission, but it allows the separate RTX SSRCs to be configured, negotiated, and then bound to interceptors that can do the rest.
First, a field is added to StreamInfo to pass information about associated streams from the SDP to the interceptor chain. This is populated for both senders and receivers. Typically the interceptor can check if the MIME type is */rtx and know that the associated stream is the original stream, but this concept can also used for other RTP extensions.
The main commit adds support for establishing RTX streams in RTCRtpSender. Since it's easy to unknowingly have */rtx codecs configured, this feature is gated behind a new enable_sender_rtx setting (this can be removed if it's thought safe to always enable). Whenever an encoding is added, the sender checks if the media engine contains a suitable RTX codec. If so, a SSRC is allocated, a flow identification ssrc-group is added to the SDP, and interceptors are bound for the RTX streams on start().
The last commit fixes an issue where repair_ssrc is only populated if the a=ssrc-group:FID line appears before the a=ssid: lines.
Let me know what you think about the approach!

Do you think the new setting is necessary? If so I'm open to suggestions on how to get the setting into RTCRtpSender without tripping clippy parameter count lint. Maybe a new RTCRtpSenderInit struct?


Use Symfony constants for return value

Now 0 and 1 are used for command return values.
Symfony provides nice constants.
https://symfony.com/doc/current/console.html#creating-a-command

Changed. #119

Thank you.


Blazegraph setup instructions

As an extension to the @origin_trail v6 data layer, we are introducing support for Blazegraph! Blazegraph is the second out of many triple stores to be integrated and supported by OriginTrail v6, after the initial integration with Ontotext GraphDB.
Following the OriginTrail development principle of #neutrality, this opens up doors for further integrations with the likes of Amazon Neptune, Stardog and other great graph solutions out there.
If you want your nodes to automatically start using Blazegraph from the new release (beta 1.23), you should follow these instructions.
Installation
Download Blazegraph on Ubuntu machine:
wget https://github.com/blazegraph/database/releases/download/BLAZEGRAPH_2_1_6_RC/blazegraph.deb

Install Blazegraph:
dpkg -i blazegraph.deb

Start Blazegraph:
systemctl start blazegraph

To verify that Blazegraph is running you can use next command:
systemctl status blazegraph

Testing
Now that you have running Blazegraph you can test it out to and if everything works fine, you OT-Node v6 will automatically connect to Blazegraph after beta 1.23.
Create a testTriples.nq file and place these triples in it:
<did:dkg:95b5b8929e92859f40d1d8d3729080a3eb9721537e0e18bc64758b0bc972c473> <http://schema.org/hasKeyword> "default" .
<did:dkg:95b5b8929e92859f40d1d8d3729080a3eb9721537e0e18bc64758b0bc972c473> <http://schema.org/hasKeyword> "scientist" .
<did:dkg:95b5b8929e92859f40d1d8d3729080a3eb9721537e0e18bc64758b0bc972c473> <http://schema.org/hasRootHash> "74f701ee49af0976f58c7cf9cc690f7a456b25b21e81761f70f290c8ee85bafc" .
<did:dkg:95b5b8929e92859f40d1d8d3729080a3eb9721537e0e18bc64758b0bc972c473> <http://schema.org/hasBlockchain> "polygon::testnet" .

Upload the file to Blazegraph:
curl -X POST -H 'Content-Type:text/x-nquads' --data-binary<EMAIL_ADDRESS>http://localhost:9999/blazegraph/sparql

Query the Blazegraph to see uploaded triples:
curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 4' -H 'Accept:application/rdf'

Final step, to get you OT-Node v6 ready to automatically switch to Blazegraph, you need to add lines with parameters for implementation name and url of graph database (in this case Blazegraph) to your .origintrail_noderc file :
"implementation": "Blazegraph",
"url": "http://localhost:9999/blazegraph",

At the end your .origintrail_noderc will be similar to this one:
{
  "blockchain":[
    {
      "blockchainTitle": "Polygon",
      "networkId": "polygon::testnet",
      "rpcEndpoints": ["https://rpc-mumbai.maticvigil.com/"],
      "publicKey": "...",
      "privateKey": "..."
    }
  ],
  "graphDatabase": {
    "implementation": "Blazegraph",
    "url": "http://localhost:9999/blazegraph",
    "username": "admin",
    "password": ""
  },
  "logLevel": "trace",
  "rpcPort": 8900,
  "network": {
  },
  "ipWhitelist": [
  "::1",
    "<IP_ADDRESS>"
  ]
}

Your Blazegraph is ready and OT-Node v6 will start using it after the new 1.23 release!
#TraceOn

DKG v6 beta.1.23 is now live on the network. If you want your node to switch to Blazegraph, after performing steps above, run next command to restart your node:
systemctl restart otnode

Alternatively, for non-Debian-based Linux distros, you can run:
wget https://github.com/blazegraph/database/releases/download/BLAZEGRAPH_2_1_6_RC/blazegraph.jar
and start the following service:
#/lib/systemd/system/blazegraph.service
[Unit]
Description=blazegraph - OriginTrail V6 Stage 1 Beta Node
Documentation=https://github.com/OriginTrail/ot-node
After=network.target
[Service]
Type=simple
User=root
WorkingDirectory=/root/
ExecStart=/bin/java -server -Xmx4g -jar /root/blazegraph.jar
Restart=on-failure
[Install]
WantedBy=multi-user.target


Vcenter automatic_vlan_id does not work

Author Name: Sergio Semedi (Sergio Semedi)
Original Redmine Issue: 5418, https://dev.opennebula.org/issues/5418
Original Date: 2017-09-28
Original Assignee: Sergio Semedi

None

Original Redmine Comment
Author Name: OpenNebula Systems Support Team (OpenNebula Systems Support Team)
Original Date: 2017-10-06T16:26:00Z

Needs testing


Allow joining over FlaggedStorage in parallel

Problem
We cannot join over a FlaggedStorage as usual because it does not fulfill the DistinctStorage guarantee (since it pushes events when accessed).
Potential solution
We can push the events prior or after the actual access and keep it out of any parallel logic. This seems to be the technically most reasonable solution, but might be very hard to get right, especially with the API we have.

cc @Moxinilian Would you be interested in taking a look?

I think the easiest solution would be to extend the parallel iteration process to call a storage-specific method prior to parallel iteration. This method would pass the joined mask bitset to the storages. We could push all the edit events at that time.
I think the best way to implement this is by extending the Join trait with a pre-process method (breaking change should be avoidable by defaulting it to a no-op). The FlaggedStorage would implement that method by doing the event push logic (and forwarding the call to the wrapped storage).
The Join trait would therefore get a new safe method fn prepare(&mut self, mask: T::Mask) to which the iteration bitset is passed. This method would be implemented for joinable tuples as a call to all prepare of the joinables with the mask. The default implementation should be a no-op. As this is statically determined, LLVM should be able to truncate those no-op calls, ensuring this is zero-cost for non-flagged storages.
The FlaggedStorage wrapper type would do the flagging of entities there using the mask (this could even make flagging more efficient considering it will be an optimizable bitset AND, maybe?). It would implement Join and ParJoin manually. In the immutable implementation of Join, the prepare method will only forward it to the wrapped storage, but in the mutable iteration, it will first register the masked entities as dirty, then forward it to the wrapped storage.
This prepare method would be called here for serial and here for parallel.
Notice that this has the drawback of being inefficient, as the final mutable iteration might have filtered out some of the entities. It seems like the current FlaggedStorage doesn't do it either, so at least for now I believe it is acceptable.
Do you think this would be a reasonable fix?

I realize this might come off as flippant but serious question has anyone ever seriously used a parallel join?

Yes, in the simulation I'm making for my finals.

Nope nope nope

Another nope.  ^.^

This should probably use a non-stale label or whatever it was called?

Still relevant.


Add checks to button command

Add checks to  commands with button

Marked as duplicated and assigned it to you hahayes


TimedSupervisorTask : task supervisor rejected the task (eureka-client 1.10.17)

We have an issue with one of the pods in cluster became unreachable due to the fact that Eureka client did not update the service registry cache. Initially this pod started to log WARNs that the thread pool is full:
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@3201d694[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@7ae6c02f[Wrapped task = com.netflix.discovery.DiscoveryClient$CacheRefreshThread@6c874d5e]] rejected from java.util.concurrent.ThreadPoolExecutor@60790f93[Running, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 20397]
	at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2055)
	at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
	at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355)
	at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
	at com.netflix.discovery.TimedSupervisorTask.run(TimedSupervisorTask.java:66)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

Then after 4 days, the dependent service was redeployed, which caused hosts to change, however the affected pod failed to get the updated list of hosts, and started to fail all the requests, since the dependent service is used in every request.
I/O exception (java.net.NoRouteToHostException) caught when processing request to ->http://<IP_ADDRESS>:8080: No route to host (Host unreachable)

This caused a temporary outage on production system until we noticed the pod under issue and rebooted it.
All other pods of the same system did not have this issue and were stable.
After some investigation, it seems that this issue was reproducible couple of times on different versions of eureka-client:
For reference: https://github.com/Netflix/eureka/issues/907
The version of eureka-client is at the moment: 1.10.17
Spring Cloud version: 3.1.2
Also we noticed that eureka-client was updated only in major release of Spring Cloud:
https://mvnrepository.com/artifact/org.springframework.cloud/spring-cloud-starter-netflix-eureka-client/4.0.0

the same got with
eureka-client version 1.10.17
Spring Cloud version: 3.1.7

same error in our production environment with
eureka-client version 2.0.1
Spring Cloud version: 2023.0.0
Spring Boot: 3.2.4
logger_name com.netflix.discovery.TimedSupervisorTask
java.util.concurrent.TimeoutException: null
	at java.base/java.util.concurrent.FutureTask.get(Unknown Source)
	at com.netflix.discovery.TimedSupervisorTask.run(TimedSupervisorTask.java:68)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)


[Bug] doris1.1.3版本BRPC通信问题

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Release 1.1.3
What's Wrong?
BRPC之间的通信问题8060端口
部分日志：
load_id=805cebf2efe2446a-900e944fec59fc95, txn_id=1257276, node=:8060, NodeChannel[10791-10004], load_id=805cebf2efe2446a-900e944fec59fc95, txn_id=1257276, node=:8060, open failed, err: failed to open tablet writer, error=RPC call is timed out, error_text=[E1008]Reached timeout=60000ms @:8060, host:
What You Expected?
解决BRPC之间的通信问题，服务能够正常运行
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

timeout when waiting for send fragments RPC. Wait(sec): 5,
telnet端口是通的

服务已正常。我的总结是：

kafka是两个节点，其中一个节点挂了，日志显示routine load频繁的去请求坏了的broker，在十几二十分钟内请求一直是失败状态（日志显示 data_consumer.h 94行打印的），然后在某个时间BRPC就突然通信不上了。是因为把请求频繁把线程挤掉了？

plan_fragment_executor.cpp的
完整的流程是 open-> exec -> close
失败的流程就是 open -> cancel (timeout)


Migrate to IIncrementalGenerator

I think this should be made into an incremental source generator so that it cannot possibly tank performance in Visual Studio 2022.

This would have to be migrated to SyntaxProvider: https://github.com/Elskom/IDisposableGenerator/blob/source-generate-attributes/src/IDisposableGenerator/SyntaxReceiver.cs

Unfortunately the migration of SyntaxReceiver to SyntaxProvider proves to be too complex currently.


Client side Blazor: UseCors not supported by IComponentsApplicationBuilder

There is no support for UseCors in client side blazor apps.
I'v created a client side blazor app but I can't get CORS running. IComponentsApplicationBuilder does not support an UseCors extension method.
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Components.Builder;
using Microsoft.Extensions.DependencyInjection;

namespace TestApp
{
  public class Startup
  {
    public void ConfigureServices(IServiceCollection services)
    {
      services.AddLogging();
      services.AddCors(options =>
      {
        options.AddDefaultPolicy(builder =>
        {
          builder.WithOrigins("http://adifferentserver:8080");
        });
      });
    }

    public void Configure(IComponentsApplicationBuilder app)
    {
      app.UseCors();  // <-- Error
      app.AddComponent<App>("app");
    }
  }
}

Hi @NCC1701M,
Enabling CORS is a server concern, not a client-side concern, so it needs to be done in the Startup class in the server project. Instead of calling UseCors in your client project, you should add it to the Startup class in the server project when using the "Blazor (ASP.NET Core hosted)" template.

Hi @danroth27
If I call the Azure function from the Blazor client-side app, an error occurs.
Access to fetch at 'http://webrecording.azurewebsites.net/api/RecordMasterEntities?userid=admin&code=PTXZS0NGYzqYjyNUNWFJrPLEnkAQU6iE==' from origin 'http://localhost:2399' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Q1. Do I have to add CORS to fix this?
By the way, if I look at the comments, it looks like Blazor client-side app can not use CORS.
Q2. If I want to use CORS, do I create and use it as a Blazor (ASP.NET Core hosted) project template?

Hi @kaki104,
If you want to make a cross origin request from a Blazor WebAssembly App, then, yes, the endpoint you are calling does need to support CORS. To enable CORS for an Azure Function see https://docs.microsoft.com/en-us/azure/azure-functions/functions-how-to-use-azure-function-app-settings#cors. For more details on making HTTP requests from a Blazor app see https://docs.microsoft.com/aspnet/core/blazor/call-web-api


Cannot run gpg successfully

Right after logging in to the client on Linux, either gpg option gives me this error:

There was an error provisioning
Unknown error: Unhandled incoming RPC 138 keybase.1.gpgUi.selectKey

Here's a screenshot!

Cc: @chrisnojima, this issue might come up if there are multiple keys that can be used to provision...

Thanks, we'll investigate this shortly

Oh yeah, I have multiple secret keys, some of which are attached to expired public keys.

Good news is a fix has been checked in (https://github.com/keybase/client/pull/4460). Bad news is that this isn't supported in the gui directly in the short term. You can use the terminal to handle this though.
Thanks!

Huh. I didn't have any trouble from the terminal to begin with.
On 09/30/2016 08:13 AM, chrisnojima wrote:

Good news is a fix has been checked in (#4460
https://github.com/keybase/client/pull/4460). Bad news is that this
isn't supported in the gui directly in the short term. You can use the
terminal to handle this though.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/4429#issuecomment-250770879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKw0bugo4wUsbssVixbUlOxaXxRyqflks5qvSc3gaJpZM4KG7sU.

--
Erik L. Arneson<EMAIL_ADDRESS>:: +1<PHONE_NUMBER>
https://twitter.com/pymander


dependabot's tracking for 'nuget' is failing

Describe the bug
dependabot's tracking for the nuget package-ecosystem is unable to locate a *.(cs|vb|fs)proj file.
I've seen this on Alan's fork as well, so this does not seem to be fork specific.  Is this a known issue or something we need take up with the dependabot folks if we really need this?
OS information
No response
Steps taken to reproduce bug

Enable dependabot for the forked repo via 'github->Security->Dependabot'.  (This option is available only on forked repos).
Select the 'Dependabot' tab @ 'github->Insights->Dependency Graph'.
(OPTIONAL) - Trigger a dependabot scan for nuget (by clicking 'last checked xxx -> 'Check for updates' link)

Expected behavior
Expected result:

No errors should be reported (No 'red triangle' preceding the 'last checked xxx...' message-link for the nuget entry).

Actual outcome

Notice the error 'red triangle' preceding the 'last checked xxx...' message-link for the nuget entry.
Click the 'last checked xxx' message-link to see the message re. a missing *.(cs|vb|fs)proj file.

Additional details
Error message:
Dependabot couldn't find a .(cs|vb|fs)proj
Dependabot couldn't find a .(cs|vb|fs)proj.
Dependabot requires a .(cs|vb|fs)proj to evaluate your .NET dependencies. It had expected to find one at the path: /.(cs|vb|fs)proj.
If this isn't a .NET project, you may wish to disable updates for it in the .github/dependabot.yml config file in this repo.

Blocked on this dependabot ticket

Have a workaround, so not blocked on GH's fix


[SPARK-11053] Remove use of KVIterator in SortBasedAggregationIterator

SortBasedAggregationIterator uses a KVIterator interface in order to process input rows as key-value pairs, but this use of KVIterator is unnecessary, slightly complicates the code, and might hurt performance. This patch refactors this code to remove the use of this extra layer of iterator wrapping and simplifies other parts of the code in the process.

Merged build triggered.

Merged build started.

Test build #43535 has started for   PR 9066 at commit 2b8bf94.

Test build #43535 has finished for   PR 9066 at commit 2b8bf94.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43535/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

/cc @yhuai @rxin for review.

Looks ok to me. I will leave it to @yhuai for the detailed review.

Merged build started.

Test build #43538 has started for   PR 9066 at commit 2b8bf94.

Test build #43538 has finished for   PR 9066 at commit 2b8bf94.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43538/
Test FAILed.

jenkins retest this please

Merged build triggered.

Looks good.

Merged build triggered.

Merged build started.

Merged build started.

Test build #43551 has started for   PR 9066 at commit ef53862.

Test build #43548 has started for   PR 9066 at commit 2b8bf94.

Test build #43551 has finished for   PR 9066 at commit ef53862.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43551/
Test PASSed.

Merged build finished. Test PASSed.

Test build #43548 has finished for   PR 9066 at commit 2b8bf94.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43548/
Test PASSed.

@yhuai thanks for reviewing. I've addressed your comment by removing the unnecessary copy() calls and the tests are still passing, so I'm going to merge this now.


Add Support for Additional State Session Backends

Right now the state session backend feature only supports memory. Memory is not the best choice most of the time.
Completed:

File (DONE)
GCP Firestore (has free tier) (DONE)

Next up:

SQLAlchemy (Postgres, SQlite, etc, GCP Cloud Cloud SQL)

Other considerations if there is interest:

Redis (Valkey fork of Redis, GCP Memorystore)
Memcached (GCP Memorystore)
GCP Cloud Storage
Other popular key/value store?

Ref: https://google.github.io/mesop/api/config/#mesop_state_session_backend

@richard-to I think we need some kind of guide. Technically all the information is in https://google.github.io/mesop/api/config/ but it's not obvious to look there. I think having some kind of "Performance" guide would be very helpful.
Something like:

How do I diagnose my performance problem? e.g. is it because state is too large or some other reason
If state is a problem, how do I pick which state session backend is suitable?

Going to close this for now. We can create new issues for additional backends if there is interest.


Documentation tool

Closes #73

Integrates typedoc to generate docs from inline code documentation
The generated json file can then be used with react-docs to display it (here how it looks like https://trustlines-network.github.io/clientlib-docs/)
Changes also some destructured function arguments because react-docs could not parse it

~NOTE: Based on PR #78. So waiting for it to be merged.~

Sorry for mixing refactoring and documentation... I will collect the refactoring related comments and open issues for them @berndbohmeier and address them in new PRs. As @jensneuber suggested I will only fix documentation and typos in this PR.


Final Developer Portal Design Review

Bugs from the various parallel workstreams to check on at the end.

[ ] The mobile view menu icon has disappeared. It is still there as I can click on it, but I cannot see it anymore.
[ ] Sometimes the close mobile menu icon is disappearing. Example in #40 on the new /docs page it disappears
[ ] Footer bar at top of footer should not be 100%
[ ] Double check that the developer portal button should have the active state
[ ] Double check font sizes
[x] Footer is not centered
[x] Footer links to Terms of Conditions which is not a thing or a page.

Moved to #57


Iterations create blank lines

When there's an iterator in the liquid template, the parser introduces a carriage return at the beginning of each iteration, and another one at the end, leaving a blank line between each iteration.
This does appear to be known, since it's accounted for in template_spec.cr:
  it "should render for loop with loop variable" do
    tpl = Parser.parse("{% for x in 0..2 %}
    Iteration n°{{ forloop.index }}
    {% endfor %}")
    tpl.render(Context.new(:strict)).should eq "\n    Iteration n°1\n    \n    Iteration n°2\n    \n    Iteration n°3\n    "
  end

However, this isn't desirable behaviour to me, and I'm wondering if anyone else agrees that we should change this, or if it's preferred to leave it as is.

This behavior matches with the Ruby version of LiquidTemplate, and this is desired.
2.7.6 :004"> Liquid::Template.parse("{% for x in (0..2) %}
2.7.6 :005">   Iteration n°{{ forloop.index }}
2.7.6 :006 >   {% endfor %}").render
 => "\n  Iteration n°1\n  \n  Iteration n°2\n  \n  Iteration n°3\n  "

Note that ruby version requires the parenthesis in the range, Crystal version not.


documentation: upskilling javascript and vue knowledge

upskilling Javascript and Vue knowledge for contributing to the front-end team
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Documentation (update or new)

How Has This Been Tested?
Passed all the checks in the Github
Testing Checklist:

[ ] Tested in latest Chrome
[ ] Tested in latest Safari
[ ] Tested in latest Firefox

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have requested a review from ... on the Pull Request

Closing PR, no review.


Can't specify will delay on CONNECT packet with auth_on_publish_m5 hook enabled

Environment

VerneMQ Version: 1.12.5
OS: Alpine Linux v3.15
Erlang/OTP version (if building from source): <IP_ADDRESS>-alpine
Cluster size/standalone: standalone

Expected behaviour
Not much here, when I send a CONNECT packet with a will message that includes a delay, I expect it to just work as outlined on the MQTT v5 spec.  Sadly, it is not working for me now.
Actual behaviour
When I send a CONNECT packet with a will message that includes a delay, I receive a CONNACK packet with a reason code of 'not_authorized'. I traced the call to the auth_on_publish_m5 hook using vmq-admin, see output below:
2022-06-07T18:17:22Z <8526.2958.3> Calling auth_on_publish_m5(undefined,{[],
<<"{CLIENT-ID_REDACTED}">>},0,test/sampleTopicef3d88ba-5c6b-41f0-bb2c-11547b8ebefe,false) with payload:
testPayload
with properties: #{p_message_expiry_interval => 3600,
p_will_delay_interval => 2}
2022-06-07T18:17:29Z <8526.2958.3> Hook returned {error,error}
2022-06-07T18:17:29Z <8526.2958.3> MQTT SEND: CID: "CLIENT-ID_REDACTED" CONNACK(sp: 0, rc: not_authorized(135))
I am running VerneMQ on my development machine, and I set it up to call localhost endpoints for its webhooks. The modifiers response from the auth_on_publish_m5 hook has the p_will_delay_interval on it, as I copy the request properties into the modifiers properties. The will delay interval comes in the request to auth_on_publish_m5 . If I null the p_will_delay_interval property on the response, then I get a successful CONNACK packet, but the will delay is not respected. I think I am getting the 'not_authorized' response because P_WILL_DELAY_INTERVAL is not on vmq_plugin_util.erl at modifiers(auth_on_publish_m5).  Overriding that list of modifiable fields seems to do the trick.

Please include minimal steps to reproduce the issue, if possible.

Spin up vernemq with an auth_on_publish_m5 hook
Send a CONNECT packet with a will message and a will delay
See the response CONNACK packet with the 'not_authorized' reason code

Sure, it is:
2022-06-10 17:19:27.556 [error] <0.1965.0>@vmq_mqtt5_fsm:auth_on_publish:1173 can't auth publish [undefined,{[],<<"CLIENT_ID_REDACTED">>},0,[<<"test">>,<<"sampleTopicd0115ff5-e96b-4348-8a87-e8fdac0afad1">>],<<"testPayload">>,false,#{p_message_expiry_interval => 604800,p_will_delay_interval => 2}] due to error
2022-06-10 17:25:09.785 [error] <0.2550.0>@vmq_plugin_util:val_properties:187 property not allowed p_will_delay_interval 2

@aj9411 Thanks, coming back to this to see whether we need to actually fix something.
Note that there should never be a will delay property in a PUBLISH packet (auth_on_publish hook must be triggered by a PUBLISH packet not a CONNECT packet). Currently I think you might be doing something unexpected by included those properties in the PUBLISH packet.
Can you confirm that understanding?

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Right, a will delay property should never be present on a PUBLISH packet. But I opened this issue regarding a CONNECT packet, I don't have any problems with PUBLISH packets. Shouldn't the auth_on_publish_m5 hook be called on CONNECT packets including a WILL? By including a will, I am asking as a client to publish something at a later time, correct? So, doesn't it make sense that the auth_on_publish_m5 hook is called in this case so that the topic can be modified and what not?
Can I provide some other logs or evidence to prove that I am not doing something unexpected myself?

I think an exact client command would help me (with mosquitto_sub or a similar client).
Note that auth_on_publish will be called on that last will message, but at session termination, not at connect time.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Hello @ioolkos : I have a similar (but different issue):

auth_on_publish_m5 gets the p_will_delay interval as property. As far as I understand @aj9411 tries to return that as a modifer which is not allowed. Of course, one could argue if that property could be filtered beforhand.

my issue is:
Similar to @aj9411 the auth_on_publish_m5 is called immediately and not when the last will message is actually published. To reproduce:
mosquitto_pub -t test -m 123 --will-topic test2 --will-payload gone --will-qos 1 -V 5 -D will will-delay-interval 20 -u joe -P secret --repeat 100 --repeat-delay 100 -x 5
will cause the following
hook: auth_on_register_m5
  data:  {'peer_addr': '<IP_ADDRESS>', 'peer_port': 59564, 'mountpoint': '', 'client_id': 'anon-Pg4URyvMwXxFT7SKJ79egt4egNNd', 'username': 'joe', 'password': 'secret', 'clean_start': True, 'properties': {'p_receive_max': 20, 'p_session_expiry_interval': 5}}
<IP_ADDRESS>:59014 - - [14/Apr/2023 09:23:20] "HTTP/1.1 POST /myendpoints" - 200 OK
hook: auth_on_publish_m5
  data:  {'username': 'joe', 'mountpoint': '', 'client_id': 'anon-Pg4URyvMwXxFT7SKJ79egt4egNNd', 'qos': 1, 'topic': 'test2', 'payload': 'Z29uZQ==', 'retain': False, 'properties': {'p_will_delay_interval': 20}}
<IP_ADDRESS>:59014 - - [14/Apr/2023 09:23:20] "HTTP/1.1 POST /myendpoints" - 200 OK
hook: auth_on_publish_m5
  data:  {'username': 'joe', 'mountpoint': '', 'client_id': 'anon-Pg4URyvMwXxFT7SKJ79egt4egNNd', 'qos': 0, 'topic': 'test', 'payload': 'MTIz', 'retain': False, 'properties': {}}

as you can see auth_on_publish_m5 is called immediately after register (topic test2), before the auth of the actual payload happens (test).
Question:
What is the correct behaviour? I can see arguments for both. The will comes with the connect packet. So it feels right to also check the authorization at that point. On the other hand, it might be published years later, so it also feels right to check it (maybe again?) on publish...

@mths1 @aj9411 my information about the last will publish being checked at session termination was obviously wrong then. I apologise for that!
The authorization context is this: the LW will be published by the broker on a topic that is chosen by the client. Who is allowed what and when then.
Technically, it's simpler to check the last will publish authorization at CONNECT.
It's probably not mandatory in the spec to authorize a last will topic in the server. But we do it; and then the question is: how to tell the client about this. Instead of disconnecting, we should probably use Connect Response Code 144. ("Topic Name Invalid")
Weirdly enough, the description to that code reads:

The Will Topic Name is not malformed, but is not accepted by this Server.

Also, we should fix the opening issue, I guess. Modifying the last will delay should be possible in a plugin.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.


Build successful, but I'm having reference issues

I keep getting these errors
An error occurred during the compilation of a resource required to process this request. Please review the following specific error details and modify your source code appropriately.
Generated Code
One or more compilation references are missing. Ensure that your project is referencing 'Microsoft.NET.Sdk.Web' and the 'PreserveCompilationContext' property is not set to false.
The type or namespace name 'Hosting' does not exist in the namespace 'Microsoft.AspNetCore.Razor' (are you missing an assembly reference?)
+
[assembly: global::Microsoft.AspNetCore.Razor.Hosting.RazorCompiledItemAttribute(typeof(RazorPagesMovie.Pages.Index_Page), @"mvc.1.0.razor-page", @"/Pages/Index.cshtml")]
The type or namespace name 'Hosting' does not exist in the namespace 'Microsoft.AspNetCore.Razor' (are you missing an assembly reference?)
+
[global::Microsoft.AspNetCore.Razor.Hosting.RazorSourceChecksumAttribute(@"SHA1", @"472eba6082c4cfd9087bb1b0a55099908614d006", @"/Pages/Index.cshtml")]
The type or namespace name 'Hosting' does not exist in the namespace 'Microsoft.AspNetCore.Razor' (are you missing an assembly reference?)
+
[global::Microsoft.AspNetCore.Razor.Hosting.RazorSourceChecksumAttribute(@"SHA1", @"5bffd98f02597e6a09295a2131188dc64093be78", @"/Pages/_ViewImports.cshtml")]

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

ID: 2aa70bd9-d52a-8b71-4f56-abf4b53c5ca1
Version Independent ID: 99c9a3fe-747c-160e-0a57-421426202506
Content: Add a model to an ASP.NET Core Razor Pages app with Visual Studio for Mac
Content Source: aspnetcore/tutorials/razor-pages-mac/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@khozanai What's the output when you execute ...
dotnet --version

... at a command prompt?

@khozanai What's the output when you execute ...
dotnet --version

... at a command prompt?
You may need to get the latest SDK 👉 https://www.microsoft.com/net/download (Download .NET Core SDK under the macOS tab)

when I run dotnet --version, I get this version: 2.1.4

You might want to go ahead and get 2.1.403 on there and see if that resolves the errors.
Unfortunately, I'm buried in a topic right now or else I'd get on my Mac and see what's what.
If you haven't figured out the problem by later this afternoon, I'll get on the Mac and see if I can repro your errors here.

I just ran the app again after the updated SDK, and got the same errors, twice. Here is a screenshot of the errors.

I'll try to repro that here in a few hours when I'm free. It's a slightly older 2.0-era app; so if I get the same result you're getting, the first thing I'll try to do is update the app to 2.1. I'll get back to you later today or this evening. Otherwise, @Rick-Anderson might recognize what's going wrong and let us know. He sees dev feedback on this set of topics and may have encountered this happening earlier.

Thank you for all your efforts in assisting to resolve this

For a quick check to see if upgrading the app will help, try using the following project file (RazorPagesMovie.csproj) and see what happens. It might still :boom: for other reasons, but it also might improve the situation ...
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.1.5" />
  </ItemGroup>

</Project>

Yup changing to 2.1, that made the app run, and its working fine now.
Thanks for the help
`

netcoreapp2.1

`

I think this sample is slated for update on the sample update tracking issue #5495. We'll get to it as soon as we can.


Using json-bigint instead of native JSON to fix long integer id's.

This is to address this specific issue: https://github.com/node-strava/node-strava-v3/issues/125

Thanks. Can you say more about this change works in testing? Is completely backwards compatible? Does it convert these big numbers into strings?
What can users of this module expect when they upgrade to a version with this change?

It should be backward compatible yes. The difference is that long ID's will be converted to bigInt class (which support long ID) instead of native javascript integer and their toString() when using it will spit out the proper long integer string representative.
Basically, this change replace the JSON.parse() by the JSONbig.parse() function.

I'll try to get this released this week. Did you see the issue affecting more than Segment Effort IDs in the wild?

I did not see anything else other than Segment Effort ID's at this point of time but anything that would be using long ID's will have the same issue.


Error in installing excel-import 1.0 with Grails 2.0

Hi,
I have tried to install excel-import 1.0 with Grails 2.0 and get the following error due to the falcone-util 1.0 which excel-import depends on.  Any suggestion ?
Thx.
Regards,
Thum
grails> run-app
| Compiling 184 source files.
| Error Compilation error: startup failed:
Compile error during compilation with javac.
C:\Users\ckthum.grails\2.0.0\projects\iTCM-std\plugins\falcone-util-1.0\src\jav
a\util\TreeKey.java:3: warning: sun.misc.ASCIICaseInsensitiveComparator is Sun p
roprietary API and may be removed in a future release
import sun.misc.ASCIICaseInsensitiveComparator;
^
C:\Users\ckthum.grails\2.0.0\projects\iTCM-std\plugins\falcone-util-1.0\src\jav
a\com\infusion\util\domain\event\hibernate\InterceptableSession.java:31: com.inf
usion.util.domain.event.hibernate.InterceptableSession is not abstract and does
not override abstract method getLoadQueryInfluencers() in org.hibernate.engine.S
essionImplementor
public class InterceptableSession implements EventSource, Session {
^
C:\Users\ckthum.grails\2.0.0\projects\iTCM-std\plugins\falcone-util-1.0\src\jav
a\com\infusion\util\domain\event\hibernate\InterceptableSessionFactory.java:40:
com.infusion.util.domain.event.hibernate.InterceptableSessionFactory is not abst
ract and does not override abstract method getTypeHelper() in org.hibernate.Sess
ionFactory
public class InterceptableSessionFactory implements SessionFactory , SessionFact
oryImplementor{
^
C:\Users\ckthum.grails\2.0.0\projects\iTCM-std\plugins\falcone-util-1.0\src\jav
a\util\TreeKey.java:18: warning: sun.misc.ASCIICaseInsensitiveComparator is Sun
proprietary API and may be removed in a future release
private static final Comparator STRING_COMPARATOR = new ASCIICaseInsensitive
Comparator();
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
2 warnings
1 error
| Error Error running script run-app: org.codehaus.groovy.grails.cli.ScriptExitE
xception (Use --stacktrace to see the full trace)

Hmm, excel-import does not depend on falcone-util plugin.  I am not sure why you think it does - let me know if I can reproduce this error with a small project.

Sorry, my fault.  It is other plugin that has dependency on falcone-util plugin.  Thanks for the excellent plugin


Resource overlay remained "on" and then factorio crash

The mod YARM - Resource Monitor (0.10.14) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event YARM::on_tick (ID 0)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
[C]: in function '__index'
YARM/resmon.lua:453: in function 'scan_current_site'
YARM/resmon.lua:1676: in function 'update_players'
YARM/resmon.lua:1733: in function 'on_tick_internal'
YARM/resmon.lua:1767: in function <YARM/resmon.lua:1762>

I am using the dangOreous mod. Normally, on the occasion when I slip and 'select' some minerals, it'll grow that site. until it seems to be satisfied. This time, I was walking back to my base when the crash happened. I'll be glad to provide more details.

Probably fixed by #180

Also, with dangOreus, please make sure you have configured a maximum site size in the mod settings; the default is -1, meaning infinite, and while I'm pretty sure YARM won't generate more ore patch, it will also likely not generate useful sites either. Also check #111 for a future feature to limit a site to exactly selected entities.


assets-webpack-plugin v3.9.12 uses a vulnerable lodash version

🐛 Bug report
Current Behavior
We recently integrated snyk into our builds and it told us that it needed to patch razzle because the locked assets-webpack-plugin v3.9.12 is locked on a security vulnerable version of<EMAIL_ADDRESS>Expected behavior
To have razzle not lock things that have security vulnerabilities.
Reproducible example
N/A
Suggested solution(s)
Please ensure that Razzle v4.x does not include vulnerable software. Not sure how reasonable it is for the project to integrate with something like snyk
Additional context

Your environment

Software
Version(s)

Razzle
3.3.13

Razzle Plugins

Node

Browser

npm/Yarn

Operating System

TypeScript

React

Razzle 3.x will not receive security updates. Just bugfixes.

But 4.x will, right? Just waiting for it :)

Yup, my precious gets everything ;)


Fix uncaught exception

Fixes: https://github.com/feross/webtorrent/issues/1100
Fixes: https://github.com/feross/webtorrent/issues/1101

0.98.17


Prev month not working

Hi.
First of all, thanks for the great datepicker.
I have once issue where the prev month goes to the next month.
Here my conf
$('#datepicker_lg').datepicker({
format: 'yyyymmdd',
startDate: "today",
endDate: "+7d",
weekStart:1
});
So I only allow selection for the next 7 days. At the end of the month the next month become available and the arrow next to the month shows up. Clicking next month actually goes to the next month and then prev month arrow shows up. However clicking that goes to the next month rather the prev.

Thanks
Phillip

B.t.w I have tested this in 1.5.1 and the latest 1.6.0 alpha

@phillip-kruger can you provide a jsfiddle that has the problem? As I can't seem to reproduce this issue here http://jsfiddle.net/zcvq0yhh/22/
Thanks!

OK I see now it's working with the latest alpha. I must have tested the
wrong one. I get it in a prev version. But I'll just upgrade ! Thanks !!
On Mon, Jan 25, 2016 at 9:31 AM, Jeroen Thora<EMAIL_ADDRESS>wrote:

@phillip-kruger https://github.com/phillip-kruger can you provide a
jsfiddle that has the problem? As I can't seem to reproduce this issue here
http://jsfiddle.net/zcvq0yhh/22/
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/eternicode/bootstrap-datepicker/issues/1769#issuecomment-174425815
.

Ah great! Should have worked in the alpha as we had a specific fix for that issue! Stable should be out by the end of the month (or around the end)

Thanks !!
On Mon, Jan 25, 2016 at 9:57 AM, Jeroen Thora<EMAIL_ADDRESS>wrote:

Ah great! Should have worked in the alpha as we had a specific fix for
that issue! Stable should be out by the end of the month (or around the end)
—
Reply to this email directly or view it on GitHub
https://github.com/eternicode/bootstrap-datepicker/issues/1769#issuecomment-174430913
.


Mention the Vcpkg package in README

Following ArchLinux, meshoptimizer is now also available in Vcpkg (https://github.com/microsoft/vcpkg/pull/12211).

Thanks!


fix: 'URL bucket doesn't match' error appears if to create an unpublish request for some conversations #463

/deploy-review


Custom active camera

Hi,
I added an UIBarButtonItem with a camera icon on footer using "imagePickerControllerFooterView".
How can I active the camera when click on that bar button, and can I remove the camera cell from the the picker
Thanks in advance.

Same here! :( we need custom camera

can I remove the camera cell from the the picker

pickerController.sourceType = .photo

How can I active the camera when click on that bar button

In 3.8.0, you can call the presentCamera function to present a camera.


spire: 1.4.1 -> 1.5.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.4.4"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.4 in filename of file in /nix/store/0npkm5mf7jxyi9c03r4m1yxr7dy0am6d-spire-1.4.4

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0npkm5mf7jxyi9c03r4m1yxr7dy0am6d-spire-1.4.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/20e02e85f5fc2eccf1c30043f89a19d4dc04a980.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0npkm5mf7jxyi9c03r4m1yxr7dy0am6d-spire-1.4.4
ls -la /nix/store/0npkm5mf7jxyi9c03r4m1yxr7dy0am6d-spire-1.4.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.4.5"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.5 in filename of file in /nix/store/7x2kdxj82g1h8himaq5ywai637i3jljq-spire-1.4.5

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7x2kdxj82g1h8himaq5ywai637i3jljq-spire-1.4.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/e016e791a09ac04002a5894a95bbb83a6a132259.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7x2kdxj82g1h8himaq5ywai637i3jljq-spire-1.4.5
ls -la /nix/store/7x2kdxj82g1h8himaq5ywai637i3jljq-spire-1.4.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.5.0"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.0 in filename of file in /nix/store/4d52hwqdal9chqs64y7i4pps8s54iaqk-spire-1.5.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4d52hwqdal9chqs64y7i4pps8s54iaqk-spire-1.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/0bb3f52ecc2ba92c1576a49df0509405f1fb6bf2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4d52hwqdal9chqs64y7i4pps8s54iaqk-spire-1.5.0
ls -la /nix/store/4d52hwqdal9chqs64y7i4pps8s54iaqk-spire-1.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.5.1"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.1 in filename of file in /nix/store/687sdnhj4hcxfn0d9qk3djhxphzaq6j3-spire-1.5.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/687sdnhj4hcxfn0d9qk3djhxphzaq6j3-spire-1.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/758344e7ad773e00f6a34f51c62a6902d0b43553.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/687sdnhj4hcxfn0d9qk3djhxphzaq6j3-spire-1.5.1
ls -la /nix/store/687sdnhj4hcxfn0d9qk3djhxphzaq6j3-spire-1.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.5.2"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.2 in filename of file in /nix/store/bli0v5vbfpflrvan7qgn6vjmjzi21x1n-spire-1.5.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bli0v5vbfpflrvan7qgn6vjmjzi21x1n-spire-1.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/86663873324ef789bfef8c3108423582c416381e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bli0v5vbfpflrvan7qgn6vjmjzi21x1n-spire-1.5.2
ls -la /nix/store/bli0v5vbfpflrvan7qgn6vjmjzi21x1n-spire-1.5.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: "The SPIFFE Runtime Environment"
meta.homepage for spire is: "https://github.com/spiffe/spire"
meta.changelog for spire is: "https://github.com/spiffe/spire/releases/tag/v1.5.3"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.3 in filename of file in /nix/store/0s6j087n9w44bm5h5p62gzx5hlfnig82-spire-1.5.3

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0s6j087n9w44bm5h5p62gzx5hlfnig82-spire-1.5.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/848e5d39b1740bb6f09e7bde924c05cc4ed62c23.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0s6j087n9w44bm5h5p62gzx5hlfnig82-spire-1.5.3
ls -la /nix/store/0s6j087n9w44bm5h5p62gzx5hlfnig82-spire-1.5.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spiffe/spire/releases.
meta.description for spire is: The SPIFFE Runtime Environment
meta.homepage for spire is: https://github.com/spiffe/spire
meta.changelog for spire is: https://github.com/spiffe/spire/releases/tag/v1.5.4
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.4 in filename of file in /nix/store/xff0pawvx3v3yi1p6dpfrjcnjklcwb1f-spire-1.5.4

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
spire
spire-agent
spire-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xff0pawvx3v3yi1p6dpfrjcnjklcwb1f-spire-1.5.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A spire https://github.com/r-ryantm/nixpkgs/archive/f5bde9dca0e2d194dc2b4ebfbc7f2ea20a7d36bf.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xff0pawvx3v3yi1p6dpfrjcnjklcwb1f-spire-1.5.4
ls -la /nix/store/xff0pawvx3v3yi1p6dpfrjcnjklcwb1f-spire-1.5.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

spire
spire-agent
spire-server

Maintainer pings
cc @jonringer @fkautz for testing.

@ofborg build spire spire-agent spire-server


demo password is wrong

In case you experience issues with docker image provided by linuxserver.io/papermerge, please open bug report in their repository.
Description
A clear and concise description of what the bug is.
Expected
A clear and concise description of what you expected to happen.
Actual
What actually happens
Info:

OS: [e.g. Windows 10, Ubuntu 20.04 LTS]
Browser [e.g. chrome, safari]
Database [SQLite, PostgreSQL 12.1]
Papermerge Version [e.g. 1.4.3]

Credentials for demo account are:
username: guest
password: password77a
They are correctly listed on github page and on official webpage.

Oops, veeeery sorry. I typed demo for username. My bad, thanks.


fix: tracing on request level

closes https://github.com/n0-computer/iroh/issues/74

looks okay, but hard to tell for me if does what you want it to do 😅

Yeah, is a bit ugly. The layers and funky stuff are the result of just reading a ton of docs. There's some logic to the layering and how it's structured.
The end result is that we have a "unified" interface for erroring out & traceIDs you get from requests are now simply better/capture more.


Extract StateMachineLoop component

What this PR changes/adds:
Extracts a component called StateMachineLoop that handles the execution of the loop that takes care of the state transitions in the TransferProcess/ConsumerContractNegotiation/ProviderContractNegotiation
Why it does that
Principally to avoid duplication since this pattern was used 3 times in different places, but with this we'll gain some other advantages:

Fully tested component that will permit to handling eventually new features introduction more easily
Graceful shutdown, that would wait for some time for letting processe before shutting down everything.
Better readability for the *Manager classes.

Further notes
I put this component in the common folder inside a -lib module because seemed like the right position.
I remember a discussion about this in #695 but there wasn't an official statement.
Linked Issue(s)
Relates mainly to #549 , does not resolve any issue but it will help with further developments on this topic.
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?

Codecov Report

Merging #787 (f215149) into main (4abdc10) will increase coverage by 0.09%.
The diff coverage is 76.37%.

@@             Coverage Diff              @@
##               main     #787      +/-   ##
============================================
+ Coverage     56.78%   56.88%   +0.09%
- Complexity     2158     2162       +4
============================================
  Files           599      602       +3
  Lines         13265    13267       +2
  Branches        948      944       -4
============================================
+ Hits           7533     7547      +14
+ Misses         5308     5296      -12
  Partials        424      424

Impacted Files
Coverage Δ

...dataspaceconnector/common/collection/LruCache.java
80.00% <0.00%> (-20.00%)
:arrow_down:

...dataspaceconnector/core/CoreServicesExtension.java
0.00% <0.00%> (ø)

...onnector/iam/did/spi/hub/message/CommitHeader.java
100.00% <ø> (ø)

...samples/identity/did/InMemoryDidDocumentStore.java
72.72% <0.00%> (-12.99%)
:arrow_down:

...spaceconnector/ion/spi/request/InputValidator.java
0.00% <ø> (ø)

...econnector/spi/system/ExecutorInstrumentation.java
0.00% <0.00%> (ø)

...r/iam/did/hub/memory/InMemoryIdentityHubStore.java
84.84% <25.00%> (ø)

...taspaceconnector/extension/jetty/JettyService.java
77.77% <85.71%> (+4.80%)
:arrow_up:

...onnector/common/statemachine/StateMachineLoop.java
88.00% <88.00%> (ø)

...iation/ProviderContractNegotiationManagerImpl.java
65.06% <90.90%> (+0.63%)
:arrow_up:

... and 8 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 3b07d9c...f215149. Read the comment docs.

Looping in @algattik here as well because we had a discussion about leveraging state machines for certain data sink implementations in the DPF. This is really good stuff and I think putting it in a library is the right way to do it since it will allow sharing regardless of the runtime (e.g. Connector, DPF, etc.)

@jimmarino ready to go


Multiple call policies do not work with session keys

Having multiple call policies for a session key does not work.
I can get the session key to work end-to-end for each individual policy below when it is the only policy in the array. When more than one policy is in the array, I get a 400 response status with the following detail: UserOperation reverted during simulation with reason: 0x.
I also tried including the permissions associated with each policy below in the permissions array of a single call policy, but that resulted in UserOperation reverted during simulation with reason: duplicate permissionHash.
const permissionPlugin = await toPermissionValidator(publicClient, {
        entryPoint,
        signer: emptySessionKeySigner,
        policies: [
            callPolicy1,
            callPolicy2,
            callPolicy3,
            callPolicy4,
        ],
    });

const sessionKeyAccount = await createKernelAccount(publicClient, {
        entryPoint,
        plugins: {
            sudo: ecdsaValidator,
            regular: permissionPlugin,
        },
    });

I'm also running into issues when using zeroAddress as the target. Passing an actual address works, but when passing zeroAddress, I get a 400 response status with the following detail UserOperation reverted during simulation with reason: 0x.
const getErc20Policy = (toAddress) =>
    toCallPolicy({
        permissions: [
            {
                target: SEPOLIA_USDC_CONTRACT,
                valueLimit: BigInt(0),
                abi: erc20Abi,
                functionName: "transfer",
                args: [
                    {
                        condition: ParamCondition.EQUAL,
                        value: toAddress,
                    },
                    null,
                ],
            },
        ],
    });

The sessionKeyAgentERC20AndEth.js script in this repo is what I was using to test.

Doing the following got me to a point where only the first permission in the policy works. The overarching question is:
how do I create a policy where an agent can send any ERC-20 tokens and ETH to a limited amount of addresses (not just one)?
Neither the SDK docs or examples show any of this, and it becomes a guessing game to figure out what will work.
Additionally, using an individual ERC-20 token address as the target works, but using zeroAddress to indicate all ERC-20 tokens does not work, as the docs indicate.
toCallPolicy(
		{
			permissions: [
				{
					target: SEPOLIA_USDC_CONTRACT,
					valueLimit: BigInt(0),
					abi: erc20Abi,
					functionName: "transfer",
					args: [
						{
							condition: ParamCondition.EQUAL,
							value: TEST_ADDRESS_1,  // <------ sending USDC to this works
						},
						null,
					],
				},
			],
		},
		{
			permissions: [
				{
					target: SEPOLIA_USDC_CONTRACT,
					valueLimit: BigInt(0),
					abi: erc20Abi,
					functionName: "transfer",
					args: [
						{
							condition: ParamCondition.EQUAL,
							value: TEST_ADDRESS_2, // <------ sending USDC to this does not work
						},
						null,
					],
				},
			],
		},
		{
			permissions: [
				{
					target: TEST_ADDRESS_1, // <------ sending ETH to this does not work
					valueLimit: maxInt256,
				},
			],
		},
		{
			permissions: [
				{
					target: TEST_ADDRESS_2, // <------ sending ETH to this does not work
					valueLimit: maxInt256,
				},
			],
		}
	);

Hey @0xernesto, sorry for the late reply.
First, if you want to set multiple permissions on the call policy, you can set like this:
Note that for now, using different multiple permissions emits type error message, but you can ignore it. This will be fixed in the next version.
const callPolicy = await toCallPolicy({
                permissions: [
                    {
                        abi: erc20Abi,
                        target: SEPOLIA_USDC_CONTRACT,
                        functionName: "transfer",
                        args: [
                            {
                                condition: ParamCondition.EQUAL,
                                value: TEST_ADDRESS_1
                            },
                            null
                        ]
                    },
                    {
                       // This will emit type error but you can just ignore it.
                        abi: vaultAbi,
                        target: VAULT_CONTRACT,
                        functionName: "deposit",
                        args: [
                            {
                                condition: ParamCondition.EQUAL,
                                value: DEPOSIT_AMOUNT
                            },
                            null
                        ]
                    }
                ]
            })

In your cases, you basically want to set OR condition for the same contract function. Like give permisson to transfer to TEST_ADDRESS_1 or TEST_ADDRESS_2. Unfortunately, using this kind of OR condition in permission is not supported now.
{
	target: SEPOLIA_USDC_CONTRACT,
	valueLimit: BigInt(0),
	abi: erc20Abi,
	functionName: "transfer",
	args: [
		{
			condition: ParamCondition.EQUAL,
			value: TEST_ADDRESS_1,  // <------ sending USDC to this works
		},
		null,
	],
},
{
	target: SEPOLIA_USDC_CONTRACT,
	valueLimit: BigInt(0),
	abi: erc20Abi,
	functionName: "transfer",
	args: [
		{
			condition: ParamCondition.EQUAL,
			value: TEST_ADDRESS_2, // <------ sending USDC to this does not work
		},
		null,
	],
},

Regarding native token transfers, I could reproduce the error message when trying to set permissions for the native token transfers. The user op reverted during the simulation. I'm currently investigating the issue and will let you know as soon as it is resolved.


Allow measurement of edge "capacity", average pixel intensity over length

The current approach allows measurement of pixel intensity as a height, but not as an independent value. For some applications (Breuer et al, in press), this is insufficient.

Closed by #28


Set-AzureADApplication: can't change RequiredResourceAccess for app when allowPublicClient = true

If we set allowPublicClient to true for AAD app:

and then will try to add more permissions e.g. to Graph API:
$tokensApp = Get-AzureADApplication | Where-Object { $_.AppId -eq "..." }
$requiredResourceAccess = $tokensApp.RequiredResourceAccess
$graphPermissions = $requiredResourceAccess | Where-Object { $_.ResourceAppId -eq "00000003-0000-0000-c000-000000000000" }
# add Sites.Read.All delegated permission
$perm = New-Object -TypeName "Microsoft.Open.AzureAD.Model.ResourceAccess"-ArgumentList "205e70e5-aba6-4c52-a976-6d2d46c48043","Scope"
$graphPermissions.ResourceAccess.Add($perm)

Set-AzureADApplication -ObjectId $tokensApp.ObjectId -RequiredResourceAccess $requiredResourceAccess

Then Set-AzureADApplication will throw the following error:

Set-AzureADApplication : Error occurred while executing SetApplication
Code: Request_BadRequest
Message: Property requiredResourceAccess.resourceAccess is invalid.
Details: PropertyName  - requiredResourceAccess.resourceAccess, PropertyErrorCode  - GenericError
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At line:1 char:1

Set-AzureADApplication -ObjectId $tokensApp.ObjectId -RequiredResourc ...

  + CategoryInfo          : NotSpecified: (:) [Set-AzureADApplication], ApiException
  + FullyQualifiedErrorId : Microsoft.Open.AzureAD16.Client.ApiException,Microsoft.Open.AzureAD16.PowerShell.SetApplication

When allowPublicClient is set to false this code works properly and successfully changes configured permissions list.

Hi,
I'm having similar issues. Once I set the publicClient=True, I'm not able to add Graph application permissions. I've tried to hack it, by creating the app as Public=True, to have the correct Authentication Platform created, then changing the IsPublic to false and set the Application permissions. The problem with this hack is, that changing the PublicClient value will change the Auth Platform as well.
It is really saddening, that there are PS commands to manage the apps, but are allowing only one case ...
Any suggestion here?
Thanks,
Attila

Hi @sadomovalex
Thank you for your issue submission.  Unfortunately, this appears to be a problem with the cmdlt and a support issue.  Issues in this repo are for documentation issues.  You can try one of the following links for additional help.
Microsoft Support:  https://support.microsoft.com/
Azure AD forums: https://social.technet.microsoft.com/Forums/en-US/home?forum=windowsazureaditpro
Stackoverflow: https://stackoverflow.com/

As always Microsoft is extremly helpful with problems that occur because there stuff is not working as it should. Almost one year until a response is posted and then it is a copy/paste template saying to get help from somewhere else. Thank you very much.
Oh and yes, I do have the same problem as the other people who were posting on this thread.

I echo @srudin 's sentiment. Adding my 2 cents here with a different error i found. Almost certain this will not be worked up on by Microsoft considering its been closed and not fixed yet.
I am using a slightly "funky" identifier URI but can observe the same code posted by op not working when switching public client off and on.
$tokensApp = Get-AzureADApplication -ObjectId "b1b0de21-add0-4ee2-badc-d1024275de54"
$tokensApp.IdentifierUris
>> urn:tst:service-name:portal

I get the below error,
Set-AzureADApplication : Error occurred while executing SetApplication
Code: Request_BadRequest
Message: Property identifierUris is invalid.
RequestId: e7c317ac-4b9f-436e-ac1d-4bfa92ec44cd
DateTimeStamp: Mon, 25 Jan 2021 09:00:01 GMT
Details: PropertyName  - identifierUris, PropertyErrorCode  - GenericError
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At line:1 char:1
+ Set-AzureADApplication -ObjectId $tokensApp.ObjectId -RequiredResourc ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-AzureADApplication], ApiException
    + FullyQualifiedErrorId : Microsoft.Open.AzureAD16.Client.ApiException,Microsoft.Open.AzureAD16.PowerShell.SetAppl
   ication

I echo @srudin 's sentiment. Adding my 2 cents here with a different error i found. Almost certain this will not be worked up on by Microsoft considering its been closed and not fixed yet.
I am using a slightly "funky" identifier URI but can observe the same code posted by op not working when switching public client off and on.
$tokensApp = Get-AzureADApplication -ObjectId "b1b0de21-add0-4ee2-badc-d1024275de54"
$tokensApp.IdentifierUris
>> urn:tst:service-name:portal

I get the below error,
Set-AzureADApplication : Error occurred while executing SetApplication
Code: Request_BadRequest
Message: Property identifierUris is invalid.
RequestId: e7c317ac-4b9f-436e-ac1d-4bfa92ec44cd
DateTimeStamp: Mon, 25 Jan 2021 09:00:01 GMT
Details: PropertyName  - identifierUris, PropertyErrorCode  - GenericError
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
At line:1 char:1
+ Set-AzureADApplication -ObjectId $tokensApp.ObjectId -RequiredResourc ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-AzureADApplication], ApiException
    + FullyQualifiedErrorId : Microsoft.Open.AzureAD16.Client.ApiException,Microsoft.Open.AzureAD16.PowerShell.SetAppl
   ication

for those who is interested: for original problem we found the following workaround using 2 another cmdlets Get-AzureADMSApplication and Set-AzureADMSApplication:
$azureAdMsApps = Get-AzureADMSApplication
$azureAdMsApp = $azureAdMsApps | Where-Object { $_.AppId -eq $appId }
Set-AzureADMSApplication -ObjectId $azureAdMsApp.Id -IsFallbackPublicClient $value | Out-Null


Different behaviours in update with native serialization

Hello again, I found an issue in the update behaviour using native serialization.
Please check the test class below
data class TestDTO(val id: UUID, val name: String)

class UpdateTest() : MongoBaseTestWithUUIDRepr<TestDTO>() {

    @Test
    fun testFailing() {
        val id = UUID.randomUUID()
        val test = TestDTO(id, "name")
        col.save(test)
        val result = col.updateOneById(id, TestDTO::name setTo "new name")
        if (result.modifiedCount != 1L) {
            entityNotFound<TestDTO>(id)
        }
    }

    @Test
    fun testOk() {
        val id = UUID.randomUUID()
        val test = TestDTO(id, "name")
        col.save(test)
        val result = col.updateOne(ClubDTO::id eq id, TestDTO::name setTo "new name")
        if (result.modifiedCount != 1L) {
            entityNotFound<TestDTO>(id)
        }
    }
}

MongoBaseTestWithUUIDRepr it is just a base test class initializing the mongo client (with uuid representation set), database and collection.
As far I can understand the two test should implement the same update in Mongo, but the first one is failing with the following error on the col.updateOneById(id, TestDTO::name setTo "new name") call:
org.bson.codecs.configuration.CodecConfigurationException: An exception occurred when encoding using the AutomaticPojoCodec.
Encoding a SetTo: 'SetTo(property=val com.octawizard.repository.club.TestDTO.name: kotlin.String, value=new name)' failed with the following exception:

SetTo contains generic types that have not been specialised.
Top level classes with generic types are not supported by the PojoCodec.

A custom Codec or PojoCodec may need to be explicitly configured and registered to handle this type.

The updateOneById expect an instance of the collection:
val result = col.updateOneById(id, TestDTO(id, "new name"))
The update parameter of updateOneById ( see https://litote.org/kmongo/dokka/kmongo/org.litote.kmongo/com.mongodb.client.-mongo-collection/update-one-by-id.html ) is of type any because you can use an other class:
data class Update(val name:String)

val result = col.updateOneById(id, Update("new name")) //this works too

I agree it would be useful to add a documentation sample

It's clear now, thank you! I thought updateOneById could be used also for partial updates.
Maybe it could be useful to add this in the future even though that can be achieved with updateOne .


Can’t return to timeline when full screen for articles is enabled

Don’t know, maybe it’s a feature but previously it worked well. Now swiping from the edge doesn’t return to timeline, instead it just switches to previous article.

Wow. It looks like the 13.4 update broke this. I’ll see what I can do.

I've got a fix in for this.  We'll get it out as soon as possible with the 5.0.1 release.


Specify top-level filtering

Hi  -- the new changes in the latest release that enable resource embedding have been working great, thanks again!
I had one request though.  It seems that by default, the postgrest-csharp library is adding top-level row filtering by inserting !inner in the query a la https://postgrest.org/en/stable/api.html#embedding-with-top-level-filtering.  This ignores any top level rows for which there are no nested resources.  It would be great to have more fine grained control over this.  In my use case I would like all top level rows returned even if the nested resources contains no rows.   Is there currently a way to control this, and if not could it be added?

@bdcodestuff can you look at the PR? Would that do what you're expecting?

Yes, that looks perfect!  Thanks for the quick reply.

@bdcodestuff happy to! I changed it to a boolean value instead of an enum (see pull). But it's available in version 2.1.1!


Enhancement: Added Docker Container Support

This PR is to resolve issue #3 by adding Docker container support to the application and adding the image container to the github container registry.

See my fork's container here: jimbrig/shinymde - Package shinymde (github.com) for the resulting container.

See the added docker.yml GitHub action and also two development scripts docker.ps1 and docker.sh.

@Nelson-Gon let me know if you have any further questions.

Approving as the failing checks are unrelated with the PR, thanks again @jimbrig

@Nelson-Gon Happy to help


Change MaxUint32 to MaxInt32 in scroll.go

This change addresses the following compile error, reported by raspberry-pi golang compiler v1.12:
/home/pi/go/pkg/mod/github.com/mum4k/termdash@v0.9.0/widgets/text/scroll.go:119:29: constant<PHONE_NUMBER> overflows int

Pull Request Test Coverage Report for Build 1183

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.498%

Totals

Change from base Build 1176:
0.0%

Covered Lines:
7151

Relevant Lines:
7731

💛  - Coveralls


package.json: Add repository config

So that https://www.npmjs.com/package/license-to-fail will link to github

@hzoo, ping?

Getting tired of seeing this on my list of open PRs, closing :)


Calls to stream methods removeListener and cancel being ignored

The current DevToolsStreamInterceptor implementation doesn't support calls to the stream's methods removeListener and cancel as calling these methods on the interceptor just does nothing. This leads to streams not being cancelled while the devtools are open.

It looks like I stubbed these out deliberately, but can't recall why. -1 to myself for not leaving a comment.

I do recall at the time the implementation for streaming wasn't fully baked. It's possible those calls caused problems back then that have since been resolved. I'd like to have a peek at the grpc library to see what's changed and if there are any obvious gotchas. Have you tested it out? Thanks!

Thanks for your reply! Yes, we have a version of the devtools with this fix running in our team and it has fixed our imminent issue of cancel calls not going through. I'm not sure about removeListener though. If I should have a look at that or test anything else, let me know!

Was the issue that if the cancel call does not propagate the stream won't cancel properly? Mainly I just want to look through the implementation of grpc to see if there's an obvious reason I omitted those calls. It's possible I just missed it.

Yes exactly, we register a callback using stream.on('data', response => {...}) and after eventually calling stream.cancel() are continuing to receive calls to that callback as the stream isn't cancelled.


Implement date picker UI

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.
[X] I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
[X] I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description
Addition of UI elements to allow the use of a date picked when picking due, scheduled and start date
✔ Solution
Button or pop up of a calander type date picker UI element to use and an alternative to typed text or date
❓ Alternatives
No response
📝 Additional Context
No response

Ohm there is #308 too.

So sorry I didn’t spot 1161 which is exactly what I would love. Such a great plug-in thanks for all your efforts.

So sorry I didn’t spot 1161 which is exactly what I would love. Such a great plug-in thanks for all your efforts.

Fabulous. Don't worry, there are so many requests it's hard to see the wood for the trees...

I've just released Tasks 7.13.0 with a date picker in the Edit Task modal...


Massive indecipherable warning message

Describe the bug
I've gotten this error message from vite, but don't know how to fix it. It's a pretty bizarre error message because it just tells me a bunch of files where the classes aren't used. But where are they imported?

"Sprite" and "CubeTexture" are imported from external module "three" but never used in "node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+core@7.3.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threejs-kit+instanced-sprite-mesh@2.4.7_@types+three@0.165.0_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/troika-three-utils<EMAIL_ADDRESS>"node_modules/.pnpm/troika-three-text<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-perf<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/three-mesh-bvh<EMAIL_ADDRESS>"node_modules/.pnpm/@threlte+extras@8.11.2_@types+three@0.165.0_svelte@4.2.18_three<EMAIL_ADDRESS>"node_modules/.pnpm/troika-three-utils<EMAIL_ADDRESS>"node_modules/.pnpm/troika-three-text<EMAIL_ADDRESS>"node_modules/.pnpm/three-perf<EMAIL_ADDRESS>and "node_modules/.pnpm/three-perf<EMAIL_ADDRESS>
Reproduction
https://github.com/benmccann/vite-warning-bug
Steps to reproduce
pnpm install
pnpm build

System Info
command is hanging on my machine. maybe because it's a pnpm project?
vite 5.3.1
rollup 4.18.0

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

looks like this warning is coming from rollup:

https://github.com/rollup/rollup/blob/c8082814fd1d518aadeb950fc7e8aa4e5e55bddb/src/utils/logs.ts#L1082
https://github.com/rollup/rollup/blob/c8082814fd1d518aadeb950fc7e8aa4e5e55bddb/cli/run/batchWarnings.ts#L252

Sigh. I guess I partially have myself to blame for this one: https://github.com/rollup/rollup/pull/4194. Lol
To be fair, putting a huge list of files where you have to guess which one contains the error is slightly better than the old version, which told you nothing

I've seen this happen more often since a couple months ago, but I'm not sure it's related to Vite either. Perhaps it should be reported to Rollup instead? Maybe also worth testing downgrading Rollup versions.

I was going to close this and file an issue with Rollup, but I can't reproduce it with Rollup alone: https://stackblitz.com/edit/rollup-repro-imroal
I'm guessing that there's something in Vite's TypeScript transformation that is triggering this or something along those lines