Multiple Instances crash

I have now multiple instances running and when i upload one instance to S3 the others are crashing:
Error: ENOENT, open '/Users/me/Documents/MeteorProjects/test/.meteor/local/cfs/files/_tempstore/documents-vDpMkJm4ZwBBuEZHp-0.chunk'
any way arround that?

CollectionFS is currently not really suited to run on multiple instance.
Depending on how desperate you are you can use my very experimental branch which is a fork of @rhyslbw branch
https://github.com/planet-training/Meteor-CollectionFS/tree/feature/jc-queue-job-query-restriction
two thinks that are currently required are:

have a NODE_ID environment variable which a name of each of your instances
In addition set this NODE_ID to the FS.JobManager.Config

FS.JobManager.Config.nodeId = process.env.NODE_ID;
FS.JobManager.Config.jobQueryRestriction = {
    'data.sourceId': FS.JobManager.Config.nodeId
};

Don't expect any further work on that branch ;)

allright thanks for the quick update! might give it a go!

same problem when using meteorhacks:cluster, which spawns multiple workers. The environment variable to watch is CLUSTER_WORKER_ID.

@aldeed Would be cool if we could integrate this into the official package. I didn't know that CollectionFS wasn't optimized for multiple instances, we just integrated it because it was a good experience to see how easy file uploads can be.

@rhyslbw Is multi-instance/multi-worker support implemented, then?

@welelay No, but this Github issue is a duplication. Track this to follow along:
https://github.com/CollectionFS/Meteor-CollectionFS/pull/667

@rhyslbw ok good, thanks for the link to the PR.
I've read it through but I have another question :
Is switching the tempstore to gridfs like this:
FS.TempStore.Storage = new FS.Store.GridFS('_tempstore', { internal: true });

without your pull request enough to get away with ENOTFOUND errors when workers try to access chunks already handled by other instances?
In other words, is switching to the gridfs tempstore enough to have multiple apps/instances in production?

@welelay No, the problem is not related to the storage method but the underlying architecture. To better understand this check out https://github.com/CollectionFS/Meteor-CollectionFS/wiki/Insert-process-codebase-walk-through

Got it, thanks :-)


Feature/fastest year to buy apartment

Feature/fastest year to buy apartment

@Hagar-Gomaa @SaraSallah please rename the name of the branch first to follow this example: feature/lowest-taxes-carbonated-drinks


[OpenPulse] Signal Proposal

Expands and flushes out the signal formalism suggested for pulses by @taalexander (https://github.com/Qiskit/openqasm/issues/126).
Some additional considerations are added at the end for specific questions I had, but input would be very useful anywhere!

This PR is being abandoned in favor of the frame approach in https://github.com/stevenheidel/openqasm/pull/2. The proposals are very similar content wise. Will attempt to add niceties and benefits from this proposal into that PR


Autoindex folder's name from apache / error

I cannot fix the problem with 4 folders from apache indexation.

thanks

Hi @tomtoom1978,
Could you share what that same folder looks like when rendered by Apache's autoindex? If those folders are there in what is returned from Apache, then folder.api (which is what player.html uses) will return them as a valid folder.


Update jsdocs

Updated some jsdocs and fixed the linting warning in calendar.js

Codecov Report

Merging #2898 (bd3137a) into develop (4d8fb8c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #2898   +/-   ##
========================================
  Coverage    63.82%   63.82%
========================================
  Files            9        9
  Lines          293      293
========================================
  Hits           187      187
  Misses         106      106

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update Node.js runtime options and depedencies, add handler parameter

Default to Node.js v8.10 runtime
Drop support for Node.js v6.10 runtime
Add support for Node.js v10.x runtime
Upgrade all dependencies
Updates to documentation
Add support for configurable handler option - allowing for custom Lambda handler paths in addition to lambda-cfn's default expectations.

cc @zmully

@zmully just ran a full test with the patrol-cache and mbx name templates, working as expected.

Also, the .travis.yml needs to be updated, but GitHub won't let me comment on it.


Question regarding multi-person videos

Hi Soyong,
Thanks for the great work! I tested the demo and it worked very well. However, when I tried sequences with multiple people, I noticed that the relative positions seemed a bit strange, and all the people appeared to be jammed at the origin in the first frame. Is this the expected behavior?

Best, Tianjian

Hi @tijiang13 ,
Each person's global translation is initialized with 0s, so it's expected that each subject starts from the origin. Furthermore, since WHAM predicts each subject individually, the predicted people may not stay in the same world coordinates. One easy (?) solution is,

Take one representative subject among the people.
Construct the camera frame with respect to the reference subject's motion
Re-map other subjects' motion to the reference subject's world frame using camera un-projection.

Thanks @yohanshin!
I also tried that idea last week, however one problem is that (correct me if I am wrong) when I tried to align one subject's motion (in global coord) with the camera, the alignment of the first frame is decent but it drafts away quickly even when calib is provided -- my thought is that when WHAM predicts the translation (in world coordinate) it did not use the calibration explicit. Do you think that's expected?
Best, Tianjian

Yes, since WHAM does not use the SLAM results explicitly, it suffers from drift. I haven't experimented with, but what you can add some post-processing using SLAM results (update the global orientation using the SLAM results and then refine root velocity accordingly). Since SLAM results will be applied equally across subjects, this might be good solution to tie all people into the same coordinate system.

I was trying that idea too but it appears that the motions (in global coords) become a bit of jittery with further refinement. Perhaps it's just yet another scenario where we need to make trade-off between visual appeal and accuracy. Anyway, thanks @yohanshin for the clarification!


formatDate argument order

Hello,
There seems to be an undocumented change for formatDate's arguments order after version 2.4.8
The docs states that the correct order is (formatStr, dateObj) but as you can see at the jsfiddle below this produces an error and the opposite works.
https://jsfiddle.net/777tzvdc/

@stsourlidakis correct. This still works to retain backwards compatibility and allow users to make the change.
Just haven't gotten around to updating the docs yet.

Should I update the docs and PR?

@stsourlidakis that'd be awesome 👍

https://github.com/chmln/flatpickr/pull/728


drivers: modem: Fix gpio compile errors with modem shell

Compile errors because of missing include file and typos
when accessing variables in the modem_pin struct.
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

We do not seem have a unit test that would have caught the issues. I noticed these when compiling a sample that used modem-shell.


Extract show_email (attempt #2)

Be careful merging, there is a commit here that should be squashed.
We possibly could move the i18n-related commit to the front to simplify the whole series.

I fixed the merge conflict with your other PR and pushed back here.
I'm OK with this stubbing approach; we test the i18n library in its unstubbed form in the i18n node tests, and this seems to not interfere with that.
I'd like to get a quick look at this from Anders in case I'm missing something in how this might effect the ES6 transition; it seems like it shouldn't since no matter how we the node testing, we'll likely want this behavior of stubbing i18n everywhere but specifically i18n tests.

As a sidenote, I think we should probably while we're thinking about this area rename translations.js to i18n.js because the current name is a confusing anomaly.

The other quirk here is that we never actually test translations.js.  All the app tests bypass it with the stub.  And then the actual quote-unquote i8n test is actually testing i18next.  Which might be a silly thing to test, since it's not even our code.

I re-pushed to put the i18n cleanup at front.  Gonna work on some naming cleanup next.

Merged, thanks @showell!  I'm pretty confident in these changes and we can always fix forward if we come up with a better way.

For some of the i18n-related discussion here, see my follow up PR #14071.


repeatable crash - possibly due to specific photo

I've been trying to track down a crash importing photos, but I found every time I try to scoll to a specific date range, I get what seems to be the same crash.  If I'm in browse view, it doesn't matter if I use the scroll bar, the mouse wheel, or up- or down-arrow to get the the offending date or image.  In filmstip view, it also crashes when I get to near a particular image/date.  I can select from the time-line either before or after, but if I select the right time - crash.
The following is one line I've seen repeatedly, which seems really strange to me, and I hope will help track this down:
System.Exception: Something is horribly wrong, this should never happen: no default version!
scroll_crash.txt
scroll_crash2.txt
Note I've looked at every image within the area that causes the crash, and I don't see anything special about any one of them.

That's the same error as in issue #112. It seems that some bug  - probably on importing photos - results in a corrupted database. You should be able to identify the image with this sql query:
select * from photos outer left join photo_versions on photos.id = photo_versions.photo_id and photos.default_version_id = photo_versions.version_id;
http://sqlitebrowser.org/ is a nice tool to work with sqlite databases. You should also make a backup of your f-spot database (~/.config/f-spot/photos.db).

The sql query is missing a where clause:
select * from photos outer left join photo_versions on photos.id = photo_versions.photo_id and photos.default_version_id = photo_versions.version_id where photo_id is null;

Every photo in the db has a list of photo versions assigned to it. If no photo version exists (not even a single one) you will see this exception. So for some reason the photo with id 5403 has a version_id set that does not exist.
Search for a row in photo_versions table that has photo_id = 5403. If that exists, set default_version_id in photos table of photo with id 5403 to the version_id of that row in photo_versions.
If none exists either delete the row with id = 5403 in photos or create an entry in photo_versions on your own.

If you happen to have some stack traces of exceptions that occured on import then please post them here. They might include the line of code that caused this issue.

error.txt
This has a bunch of imports which ended in the crash.  Hopefully they point to the culprit.

Unfortunately the log doesn't help. The root cause exceptions seem to occur in a background thread and we only see the unhandled-exception exception. Maybe we can add some code to log the unhandled exception stack trace as well...

Would it be possible (and useful) to run under gdb?  I've had no luck getting mono-develop installed on my Gentoo box, but maybe I can try on my Win7 laptop.  Would that be at all useful?  (I have no idea if I would still get the crashes on the Win7 box, however.)  Is this crash that spurious that only a few users seem to get bit by it?

PR #115 fixes the bug that causes the exception (and crash) on import. This will prevent new inconsistencies in the database. The already introduced inconsistencies in the database can not be fixed this way and need to be fixed manually.

I just did three imports with 118, 157, and 323 photos, with no crash.  I think you got it!  If I can, I'll close this issue as resolved.


IC versus Intercompany

It appears in the latest release of business central that the objects have intercompany spelled out; therefore, if you do any of the above searches for IC you will get no results.
E.G.  IC Chart of Accounts is Intercompany Chart of Accounts

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

ID: c748d8ad-0f5e-126e-0555-b047af1e8c96
Version Independent ID: beb88306-1c4e-3e69-cb6d-06d62ddd71a6
Content: Set Up Intercompany Transaction Posting - Business Central
Content Source: business-central/intercompany-how-setup.md
Service: dynamics365-business-central
Product: unspecified
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Thank you for catching this. We'll get this improved - and yes, fortunately our user interface strings are getting easier to understand :-)

Fix ready for the weekly update on Monday.


Document stress tool

It would be great if the stress tool were documented in the web docs. Currently they only reside in the source code: https://github.com/influxdata/influxdb/tree/master/stress &  https://github.com/influxdata/influxdb/blob/master/stress/stress.toml
If I get time, I'll try to translate these into usable docs. Hopefully someone gets to it before me :P

@pauldix are we going to encourage people to benchmark 1.0 themselves? If so we need to make the stress tool easy to use.

@beckettsean yeah, I think it should be well documented and easy to use. It's great for users to help them figure out sizing requirements.

@jwilder @mjdesa @jackzampolin @rossmcdonald @kostasb @mark-rushakoff
Any thoughts on who should document the stress tool for end users? @rkuchan and I will happily turn your spaghetti notes into coherent prose, but we need a couple of pages of what it does and how in order for us to get started.

I think @mjdesa @jackzampolin might be the most familiar with it.

I'll sync up with @rkuchan to get it documented.

https://github.com/influxdata/influxdb/blob/master/stress/v2/README.md
Can we turn that into something in the docs?
@jackzampolin it's a great writeup for those familiar with the system, but I didn't quite understand how to launch it for evaluating my own cluster. Can you work up some step-by-step instructions to launch it against an InfluxEnterprise cluster, including what numbers to look at to determine if the cluster is well-provisioned?

@timhallinflux It looks like influx-stress replaced the one described here and seems fairly well documented in the README (https://github.com/influxdata/influx-stress). Is this something we want to put into the 1.x docs now?


expand lua support to include cmsgpack replacement

Feature request type
enhancement
Is your feature request related to a problem? Please describe
Some redis clients, such as the BullMQ library for Node.js, expect the server to have the cmsgpack library loaded into the Lua environment. The cmsgpack library is one of the external libraries documented as loaded in the redis API docs.
Describe the solution you'd like
The two documented functions cmsgpack.pack and cmsgpack.unpack should be added to the Lua environment, likely by using a C# implementation like MessagePack.
Describe alternatives you've considered
No response
Additional context
No response

If this is needed, one could also use/update any usable OSS version of cmsgpack to work with NLua. Such as https://github.com/valkey-io/valkey/commits/unstable/deps/lua/src/lua_cmsgpack.c

Also interested in this.  I'm trying to use garnet with BullMQ, but it is not working as a drop in replacement for redis due to this issue.


[tinygltf] fix json path

This is part of #12199
when using tinygltf with json it will not find it the right place, this fixes that

Thanks for the fix!


Error with the new weight value

Hi! the new weight value shows a error:
"ValueError: You are trying to load a weight file containing 12 layers into a model with 14 layers."
You should update the model.py script

The one uploaded is for hybrid-can not mtts-can. We have hybrid-can defined in model.py. We will release other models soon too.


application undefined

Cannot ready property 'application' of 'undefined'. Says it's a type error, but cannot guess what it means by that, please help
{
  "errorMessage": "Cannot read property 'application' of undefined",
  "errorType": "TypeError",
  "stackTrace": [
    "AlexaSkillKit.execute (/var/task/AlexaSkillKit.js:86:62)",
    "exports.handler (/var/task/index.js:89:8)"
  }
}

Log
START RequestId: e72676c8-cdae-11e6-96b5-075249fb707f Version: $LATEST
2016-12-29T10:09:36.911Z	e72676c8-cdae-11e6-96b5-075249fb707f	Unexpected exception TypeError: Cannot read property 'application' of undefined
2016-12-29T10:09:36.950Z	e72676c8-cdae-11e6-96b5-075249fb707f	{"errorMessage":"Cannot read property 'application' of undefined","errorType":"TypeError","stackTrace":["AlexaSkillKit.execute (/var/task/AlexaSkillKit.js:86:62)","exports.handler (/var/task/index.js:89:8)"]}
END RequestId: e72676c8-cdae-11e6-96b5-075249fb707f
REPORT RequestId: e72676c8-cdae-11e6-96b5-075249fb707f	Duration: 60.51 ms	Billed Duration: 100 ms 	Memory Size: 128 MB	Max Memory Used: 10 MB

It says 'application' is undefined, but exports.handler function in index.js calls execute function, please help

I have the same issue. how to fix this ?

@phpmind
Go into your aws lambda account, go to your function, Since you've uploaded the code, click the actions->configure test event->select "Alexa start session" from sample event template, and in the bottom, click save and test button, there, it works :)
PS: I'll keep it open so that it attracts other people with same problem and avoiding creating new threads

Thanks i've had the same issue!

and this solved it!!

It  worked. Thanks

@notvishwanth I tried this but now I get this error: "errorMessage": "No url found for application id”
Can you please help?

Can you post the log please?

Here is my log:
START RequestId: 36094d33-01bf-11e7-89ea-37cc308e99d3 Version: $LATEST
2017-03-05T16:17:21.695Z	36094d33-01bf-11e7-89ea-37cc308e99d3	{"errorMessage":"No url found for application id"}
END RequestId: 36094d33-01bf-11e7-89ea-37cc308e99d3
REPORT RequestId: 36094d33-01bf-11e7-89ea-37cc308e99d3	Duration: 49.87 ms	Billed Duration: 100 ms 	Memory Size: 128 MB	Max Memory Used: 17 MB
and my lambda code is:
"use strict"
var http = require('http');
var URLParser = require('url');
exports.handler = function (json, context) {
try {
// A list of URL's to call for each applicationId
var handlers = {
'appId':'url',
'amzn1.ask.skill.XXXXXXXXXXXXXXXXXXXX':'http://XXXXXXXXXXX'
};
    // Look up the url to call based on the appId
    var url = handlers[json.session.application.applicationId];
    if (!url) { context.fail("No url found for application id"); }
    var parts = URLParser.parse(url);

    var post_data = JSON.stringify(json);

    // An object of options to indicate where to post to
    var post_options = {
        host: parts.hostname,
        auth: parts.auth,
        port: (parts.port || 80),
        path: parts.path,
        method: 'POST',
        headers: {
            'Content-Type': 'application/json',
            'Content-Length': post_data.length
        }
    };
    // Initiate the request to the HTTP endpoint
    var req = http.request(post_options,function(res) {
        var body = "";
        // Data may be chunked
        res.on('data', function(chunk) {
            body += chunk;
        });
        res.on('end', function() {
            // When data is done, finish the request
            context.succeed(JSON.parse(body));
        });
    });

any idea?

Hey there! Please be advised that we're no-longer providing support for this project and so instead, please check out the replacement Alexa Skills Kit SDK for Node.js:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs
Also, we have a number of sample skills based on this newer SDK, under here:
https://github.com/alexa


Dummy PR

Docs should not build on this.
@ablaom

Yeah something's not working. The debug logs will help a lot with this.

Okay I think I found it: https://github.com/alan-turing-institute/MLJBase.jl/pull/470#issuecomment-736116921


VF assignment/reassignment to a Pod

I was wondering how does Multus behave today if it is not able to assign a VF to a Pod? Does it try to select another VF from a Pool and assign to a Pod?

@devdattakulkarni
I am assuming you are referring to SR-IOV VF? In that case, Multus has no role in VF assignment to any Pod. In Kubernetes, HW resources are managed by a Kubelet device plugin manager with an associated device plugin. For SR-IOV network interfaces, it is SR-IOV network device plugin.
Multus only able to look up allocated Pod devices if there is a k8s.v1.cni.cncf.io/resourceName annotation given in net-attach-def CR.

Thanks @ahalim-intel for the note.
Yes, this question was related to SR-IOV VFs.
Thanks for the pointer that it is handled in the SR-IOV network device plugin. I will check with that team.


This library will break in a week when PZ is updated, (no version control)

https://github.com/arjun-prakash/pz_dilemma/blob/a13926a758e62eb51dbacb2be8a0d3ea7812f6b1/src/environments/simple_pd/dilemma.py#L47
I don't even see a PZ dependency specified, maybe I'm mistaken?

Congrats! Let me or another PZ dev know when you've done it and we'll add it back to the docs


Manually trigger plugin

Hello!
I saw there is quite a significant delay between the document being updated on firebase and that change being reflected on Algolia in a search result.
Is there any way to force this plugin to trigger manually to expedite the change, or is the only way around it to manually update those entities in Algolia through the REST API?
Thank you so much!

I am not sure I understand what you mean by "manually trigger".  By changing the document, Firestore will trigger the Algolia indexing process.

Are there any more insight on what you are looking for here.  If not, I will close this issue.


possbile LitePullConusmer rebalance bug

Please describe the issue you observed:

What did you do (The steps to reproduce)?

What did you expect to see?

What did you see instead?

In our production environment, I find some msgs lost when a new consumer started(causing rebalance), the RMQ version we use is 4.7.1 and we use the new LitePullConsumer API.
From the rocketmq-client log, something unexpected happened:

the same messageQueue is detected should cancel its pullTask in two different threads in almost the same time.

2021-03-09 20:16:19.911 WARN  [PullMsgThread-c_g1] (Slf4jLoggerFactory.java:115) - The Pull Task is cancelled after doPullTask, MessageQueue [topic=t, brokerName=rmq-b5, queueId=3]
2021-03-09 20:16:19.911 WARN  [PullMsgThread-c_g2] (Slf4jLoggerFactory.java:115) - The Pull Task is cancelled after doPullTask, MessageQueue [topic=t, brokerName=rmq-b5, queueId=3]

before rebalance, there are two consumer(two consumer cid), when a new consumer is started, it becomes three(3 consumer cid), but the rebalance triggered several times with wrong cid count, which means findConsumerIdList API returns wrong value. I think the wrong rebalance should not cause any msg lost since rebalance is done in a single thread and finally should be correct.  But why wrong cid returned is interesting( calling a wrong broker? slave? but why ?).

below is the logs for rebalance result.(I changed some inner ip and brokerName info for security reasons)
2021-03-09 20:16:19.777 INFO  [RebalanceService] (Slf4jLoggerFactory.java:100) - rebalanced result changed. allocateMessageQueueStrategyName=AVG, group=c_g, topic=t, clientId=XXX_C1, mqAllSize=24, cidAllSize=3, rebalanceResultSize=8, rebalanceResultSet=XXX (3 cid, corrent)
2021-03-09 20:16:19.779 INFO  [RebalanceService] (Slf4jLoggerFactory.java:100) - rebalanced result changed. allocateMessageQueueStrategyName=AVG, group=c_g, topic=t, clientId=XXX_C1, mqAllSize=24, cidAllSize=2, rebalanceResultSize=12, rebalanceResultSet=XXX (2 cid, wrong)
2021-03-09 20:16:19.781 INFO  [RebalanceService] (Slf4jLoggerFactory.java:100) - rebalanced result changed. allocateMessageQueueStrategyName=AVG, group=c_g, topic=t, clientId=XXX_C1, mqAllSize=24, cidAllSize=3, rebalanceResultSize=8, rebalanceResultSet=XXX (3 cid, correct)
2021-03-09 20:16:19.784 INFO  [RebalanceService] (Slf4jLoggerFactory.java:100) - rebalanced result changed. allocateMessageQueueStrategyName=AVG, group=c_g, topic=t, clientId=XXX_C1, mqAllSize=24, cidAllSize=2, rebalanceResultSize=12, rebalanceResultSet=XXX (2 cid , wrong)
2021-03-09 20:16:19.785 INFO  [RebalanceService] (Slf4jLoggerFactory.java:100) - rebalanced result changed. allocateMessageQueueStrategyName=AVG, group=c_g, topic=t, clientId=XXX_C1, mqAllSize=24, cidAllSize=3, rebalanceResultSize=8, rebalanceResultSet=XXX (3 cid, correct)

from rocketmq-client log the rebalance notification from broker found slave broker ips

additional info:
in one java process we have one consumer and one producer with different clientId; the consumer is polling messages for one group and one topic(only one subscription); the producer is sending messages to many topics( different from consumer topic);

Please tell us about your environment:

RMQ 4.7.1
LitePullConsumer

When a new consumer sends a heartbeat to a broker, the broker will notify all consumers of the related group to do rebalance. If there are multiple brokers, a consumer will receive multiple notifications.
In the rebalance process, the consumer selects a broker randomly to look up the consumer list. If the consumer did not send any heartbeat to the broker at the time, the returned list is incorrect.

When a new consumer sends a heartbeat to a broker, the broker will notify all consumers of the related group to do rebalance. If there are multiple brokers, a consumer will receive multiple notifications.
In the rebalance process, the consumer selects a broker randomly to look up the consumer list. If the consumer did not send any heartbeat to the broker at the time, the returned list is incorrect.

yes, and incorrect consumer list should not result in lost msgs since it will be corrected anyway.  My major confusion is the first question, why one messageQueue is  processed(Pull Task) by two pull threads(suggested  by rocketmq-client log).  Do you have any ideas?

@Zanglei06 Multiple rebalance process with different consumer lists will cause this issue.

Heartbeat failure may cause load balancing problems

Heartbeat failure may cause load balancing problems

the LB problems should not include msgs lost. only some short time msg duplicates occurs.  can you explain why the 1st log appears?

I had reproduce the bug in this commit:
https://github.com/areyouok/rocketmq/commit/a54599ec45f2473acb647d2e7b15eb55983607d7
At first, create a topic with only one queue:
./mqadmin updateTopic -n <IP_ADDRESS>:9876 -t TopicTest -r 1 -w 1 -c DefaultCluster
then run LitePullConsumerBug, it send two messages, receive one, and the offset is update to consumerOffset.json
The output:
RocketMQLog:WARN No appenders could be found for logger (io.netty.util.internal.PlatformDependent0).
RocketMQLog:WARN Please initialize the logger system properly.
SendResult [sendStatus=SEND_OK, msgId=AC1128381E4718B4AAC2691C5DF80000, offsetMsgId=AC11283800002A9F0000000000000C60, messageQueue=MessageQueue [topic=TopicTest, brokerName=broker-a, queueId=0], queueOffset=18]
09:51:07,801<PHONE_NUMBER> get queue
09:51:07,803<PHONE_NUMBER> pull step 1
09:51:08,776 start consumer 2
09:51:09,787 203029914 get queue
09:51:09,787<PHONE_NUMBER> lost queue
09:51:09,788 203029914 pull step 1
09:51:10,790<PHONE_NUMBER> get queue
09:51:10,791<PHONE_NUMBER> pull step 1
09:51:10,808<PHONE_NUMBER> pull step 2
09:51:10,814 submit 1 msgs
09:51:10,815 drop 1 msgs
09:51:12,792 203029914 pull step 2
09:51:13,793<PHONE_NUMBER> pull step 2
SendResult [sendStatus=SEND_OK, msgId=AC1128381E4718B4AAC2691C815A0001, offsetMsgId=AC11283800002A9F0000000000000D10, messageQueue=MessageQueue [topic=TopicTest, brokerName=broker-a, queueId=0], queueOffset=19]
09:51:15,806 submit 1 msgs
receive msg: AC1128381E4718B4AAC2691C815A0001
09:51:15,807<PHONE_NUMBER> pull step 1
09:51:18,807<PHONE_NUMBER> pull step 2

The root cause in DefaultLitePullConsumerImpl.PullTaskImpl.run
...
long offset = nextPullOffset(messageQueue);
...
updatePullOffset(messageQueue, pullResult.getNextBeginOffset());
After a ProcessQueue is dropped, but the PullTask is still run. The invalid task will call updatePullOffset.

Merged


Unable to reliably to use Connect-IPPSSession behind SNAT

Hello wonderful GitHub community!  Our company just switched over to Active/Active firewalls and now our automated scripts to connect to Security and compliance powershell fail with error: "The request for the Windows Remote Shell with ShellId  failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation."  According to MS documentation here, this is due to the connection request using multiple source addresses.  Firewall team says they can't do source-based routing and won't change the SNAT having multiple IPs.  Do I have any options with Connect-IPPSSession or is there a way to successfully work around that?

@officedocsbot assign @yogkumgit

Hello @DDog80sRocked, how are you? For your inquiry I need to kindly suggest opening a support ticket directly from your tenant's administration, they will be able to help you as here we are limited to documentation issues and improvements.
Support URL: https://docs.microsoft.com/microsoft-365/admin/contact-support-for-business-products.
Thank you!

@dariomws  Thank you very much for the contribution and sharing this explanation. @DDog80sRocked Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also


Add schema for recommendations API requests

Summary

Defines a JSON schema for the structure of recommendations API requests that will be received by TorchServe
Fields level, parent, and has_content will be generated in preprocessing in the TorchServe handler
TODO: unit tests to ensure schema does what we expect

@jamalex :: @akolson and I worked on a JSON schema to nail down the format of the data sent to TorchServe for topic recommendations. We followed your example in the example pipeline code. Does it look sufficient?
Other questions:

Do we need has_content to represent whether a topic has non-topic resources? Or is that only representative of whether it has subtopics?
What is category and do we need it?

Hi @jamalex I was able to incorporate the feedback. It was pretty clear so need for the call. We should now be more closer to the final request body 🤞. Please let me know incase there is anything that may require an update. @bjester  a few files have been renamed as pointed out by Jamie in his comment. Also, any feedback is welcome. Thanks


Scope descriptors and ranges at cursor point

Prerequisites

[x ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I'm not sure if this is a bug or intended behaviour. Would somebody with more knowledge please explain.
Given the string $foo = "foobar";, using the PHP grammar, and placing the cursor directly before the first opening quote character.
If I call editor.scopeDescriptorForBufferPosition(point), the scopes returned will include string.quoted.double.php. Yet, If I call editor.bufferRangeForScopeAtPosition('string.quoted.double.php', point), it will return undefined. There appears to be a disparity between the two calls.
If this is intended behaviour, I can code around it. I'm just worried this is something that will change, breaking my code.
Versions
1.19.5

Thanks for reaching out!
Because we treat our issues list as the Atom team's backlog, we close issues that are questions or don't represent a task needing to be completed. For most questions about Atom there are a lot of options, check out:

The Atom Flight Manual
The Atom FAQ on Discuss
Discuss, the official Atom and Electron message board
Join the Atom Slack team

On Discuss and in the Atom Slack team, there are a bunch of helpful community members that should be willing to point you in the right direction.
In particular for API questions, Discuss and the Atom Slack are probably the best places to get help.


Leaflet toolbar plugin

This PR replaces all of the toolbars in Leaflet.draw with toolbars from Leaflet.Toolbar as proposed in #324.
In particular, this pull request:

Has each draw handler inherit from L.ToolbarAction instead of L.Handler. L.ToolbarAction is a new class from L.Toolbar, inheriting from L.Handler and including defaults for the toolbar icon and methods for building the icon and submenu.
Replaces src/draw/DrawToolbar.js with a control-style drawing toolbar in src/draw/control.
Replaces src/edit/EditToolbar.js with a control-style editing toolbar in src/edit/control.
Adds a new popup-style editing toolbar in src/edit/popup.
Prunes Leaflet.draw CSS, as much of the toolbar styles can now be pulled in from Leaflet.Toolbar.

There are live examples of the new toolbar functionality for Leaflet.draw at:
http://manleyjster.github.io/Leaflet.Toolbar/examples/control.html
http://manleyjster.github.io/Leaflet.Toolbar/examples/popup.html.
I also wrote a short blog post about designing Leaflet.Toolbar and porting the Leaflet.draw toolbars over to the new plugin - you can check that out here: http://justinmanley.io/blog.
Documentation for Leaflet.Toolbar is in a wiki: https://github.com/manleyjster/Leaflet.Toolbar/wiki/API-Reference.
I'm excited to get a conversation started about this PR!

Awesome work! Had a quick look but will wait for @jacobtoye to weigh in.
I think you should rebase the pull so that it merges to master cleanly.

Yup, will do.  Didn't want to rebase prematurely in case there was development going on in the master branch. I'm happy to rebase for a clean merge once everyone's had a chance to look through the PR and we've resolved any questions / issues.

Awesome. I will give this the attention it deserves as soon as possible. Hopefully over the next few days.

I'm thinking we chould add Leaflet.toolbar as a submodule for Leaflet.draw, since Leaflet.draw will now have a dependency on Leaflet.toolbar. This would mean people who are already using Leaflet.draw can just download the built code still. Other wise they would need to also download Leaflet.toolbar.
I potential issue with this would be that if people wanted to use both Leaflet.draw and roll their own toolbar for something else they may unknowingly include Leaflet.toolbar twice.
What are you thoughts?
Other than that could you back out the changes to built files. We don't include changes to these in pull requests.

@jacobtoye - Ooops - I had meant to keep the built files out of the PR.  Not sure how they made it in, but I'll remove them when I rebase.
What do you have in mind when you say "submodule"? Are you suggesting that we git-submodule Leaflet.toolbar, or that we add Leaflet.toolbar to the build/deps.js file for Leaflet.draw and include it in the built Leaflet.draw distribution?  I don't think the first is a good idea, but I'm fine with including Leaflet.toolbar in the build.deps. Application developers who want to use both .draw and .toolbar should be able to avoid loadingLeaflet.toolbar twice by simply loading Leaflet.draw before any other scripts that use Leaflet.toolbar.
@kyletolle - Agree that the naming is not completely consistent. The difference is that L.Edit.Control.Edit is a top-level action, while L.Draw.Cancel and L.Draw.RemoveLastPoint are sub-actions that are exposed once their parent top-level action is triggered. L.Draw.Cancel and L.Draw.RemoveLastPoint are analogous to L.EditToolbar.Save and L.EditToolbar.Undo, which are contained in src/edit/control/EditToolbar.Control.js.
I think maybe the best way to resolve this is to put subhandlers into their own directory.  So I would create src/edit/control/subhandler/ and move L.EditToolbar.Save and L.EditToolbar.Undo into subhandlers (probably renaming them), and do the same for the  Draw.Control subhandlers.  Thoughts?

Thanks for the additional explanation. The L.Draw.Cancel and L.Draw.RemoveLastPoint are definitely sub actions like L.EditToolbar.Save and L.EditToolbar.Undo.
In the code, you've moved from L.Handler to L.ToolbarAction. What about renaming the folders to have the action name? So, the folders could be src/edit/control/actions and /src/edit/control/subactions instead of handlers and subhandlers. Same thing could be done for the Draw actions and subactions, like you mentioned.

Additionally, Leaflet.draw currently highlights the currently edited marker and gives a tooltip to the cursor:

Using the both the control and popup demos, I didn't notice this functionality when editing a marker.
The marker doesn't change visually at all when in edit mode.

I also think the examples will need updating to work with these changes.

@manleyjster Yeah I was thinking git-submodule. Was just trying to avoid people who are already using Leaflet.draw to have to know to download Leaflet.toolbar too. But we can just do a new version and include a note in the Readme.md.
@kyletolle thanks for finding that! I'll make sure I checkout @manleyjster's branch and double check all example are working.

@jacobtoye - I understand where you're coming from, but I don't think git-submodule is a good idea. I've wrestled with it enough to not want to do so any more - it's not always intuitive to work with, and it's a huge pain to get rid of.
I would suggest doing a new minor version release. We can add Leaflet.toolbar as a dependency in the package.json file and then include it in build/deps.js so that the source for Leaflet.toolbar is included in the source for Leaflet.draw. At the very least, that means that people won't have to add an extra script and link tag for the Leaflet.toolbar dist files. Would you be comfortable with that?

@manleyjster yeah no problem. Just wanted to run the idea past you. I'm happy to do as you say. Will do it this weekend.

@manleyjster could you please rebase with master and also back out the changes to the /dist files.

@jacobtoye - Don't worry - I haven't forgotten about this - it's on my to do list. I'd still like to resolve one issue with Leaflet.draw + Leaflet.Toolbar (see https://github.com/Leaflet/Leaflet.toolbar/issues/18) before rebasing. I also need to merge https://github.com/Leaflet/Leaflet.toolbar/tree/single-toolbar-on-map (a Leaflet.Toolbar bugfix) into Leaflet.Toolbar master.
Once that's done, I'll back out the dist/ changes and rebase.
Sorry for the delay - it's been tough for me to find spare time to think about how to approach the outstanding bugs / issues on Leaflet.Toolbar. I hope to be able to resolve these soon.

Just rebased. I also just released a new version of Leaflet.toolbar (0.1.2), which fixes many of the bugs that folks have posted in the above comments and in the Leaflet.toolbar issue tracker.  Should be ready to go!
One last impediment - I didn't include Leaflet.toolbar in the build.deps for Leaflet.draw. My concern was that Leaflet.toolbar is still in early stages, and I expect that important bugfixes will be coming out fairly regularly. I don't want you to have to update the version of Leaflet.toolbar included with Leaflet.draw every time that happens - that's going to quickly become unmanageable.
Correct me if I'm wrong, but I think that folks who want the latest version of Leaflet.toolbar should be able to simply include the source in a <script> tag after Leaflet.draw. Is that correct? If so, then I'm fine with including Leaflet.toolbar in the build for Leaflet.draw.
If we take this route, I suggest that (at the very least), we split Leaflet.toolbar out of Leaflet.draw once Leaflet.draw reaches a 1.0-level release.

Has there been any movement on this? I am very much interested in using Leaflet.draw with a customized toolbar.

@manleyjster Sorry for the long time for getting to this. Only just found time.
The examples and documentation needs to be updated. I'm happy to do this.
Since L.Control.Draw has been removed there is no longer a way a control with both the Draw and Edit toolbars.
E.g.
map.addControl(new L.Control.Draw({
	edit: { featureGroup: drawnItems }
}));

I think re-creating L.Control.Draw as L.Draw.Control (like this naming convention better) where I create both the draw and edit toolbars would be sufficient. What do you think?

@jacobtoye - I'm happy to make the changes you suggest, but I'm a bit confused...
Did you actually merge this PR in? None of the changes I made are showing up on the tip of the master branch, either online, or when I git pull locally. Did you revert this PR after merging?

Work has finally allowed me some time for Leaflet.draw. I didn't realize the above restriction until I tried to get this pull working with the examples.

What we want to have is essentially three parts to Leaflet.draw: the draw control, the toolbar and the draw/edit handlers. One day I think it would be better to create a new repo for the handlers.
To solve the dependency problem I think we need to create an intermediate ToolbarAction handlers that call the Draw/Edit handlers. E.g. L.Draw.polygon.ToolbarAction.
@manleyjster what do you think?

This is how I hacked up the L.DrawToolbar.Control to pass through the options:
L.DrawToolbar.Control = L.Toolbar.Control.extend({
	options: {
		className: 'leaflet-draw-toolbar'
	},

	initialize: function (options) {
		L.setOptions(this.options, options);

		this.options.actions = {
			polygon: {
				action: L.Draw.Polygon,
				options: options.polygon
			},
			polyline: {
				action: L.Draw.Polyline,
				options: options.polyline
			},
			circle: {
				action: L.Draw.Circle,
				options: options.circle
			},
			rectangle: {
				action: L.Draw.Rectangle,
				options: options.rectangle
			},
			marker: {
				action: L.Draw.Marker,
				options: options.marker
			}
		};

		L.Toolbar.Control.prototype.initialize.call(this, options);
	},

	appendToContainer: function(container) {
		var baseClass = this.constructor.baseClass + '-' + this._calculateDepth(),
			className = baseClass + ' ' + this.options.className,
			Action, action,
			i, j, l, m;

		this._container = container;
		this._ul = L.DomUtil.create('ul', className, container);

		/* Ensure that clicks, drags, etc. don't bubble up to the map. */
		this._disabledEvents = ['click', 'mousemove', 'dblclick'];

		for (j = 0, m = this._disabledEvents.length; j < m; j++) {
			L.DomEvent.on(this._ul, this._disabledEvents[j], L.DomEvent.stopPropagation);
		}

		/* Instantiate each toolbar action and add its corresponding toolbar icon. */
		for (var actionIndex in this.options.actions) {
			Action = this._getActionConstructor(this.options.actions[actionIndex].action, this.options.actions[actionIndex].options);

			action = new Action();
			action._createIcon(this, this._ul, this._arguments);
		}
	},

	_getActionConstructor: function(Action, actionOptions) {
		var args = this._arguments,
			toolbar = this;

		return Action.extend({
			initialize: function() {
				Action.prototype.initialize.apply(this, args.concat(actionOptions));
			},
			enable: function() {
				/* Ensure that only one action in a toolbar will be active at a time. */
				if (toolbar._active) { toolbar._active.disable(); }
				toolbar._active = this;

				Action.prototype.enable.call(this);
			}
		});
	},
});

Hey @jacobtoye - how about this?
L.DrawToolbar.Control = L.Toolbar.Control.extend({
	options: {
		// default shape options
		polygon: {},
		polyline: {},
		circle: {},
		rectangle: {},
		marker: {},

		className: 'leaflet-draw-toolbar'
	},
	initialize: function(options) {
		L.setOptions(this.options, options);

		var actions = [
			L.Draw.Polygon.extend({ options: this.options.polygon }),
			L.Draw.Polyline.extend({ options: this.options.polyline }),
			L.Draw.Marker.extend({ options: this.options.marker }),
			L.Draw.Rectangle.extend({ options: this.options.rectangle }),
			L.Draw.Circle.extend({ options: this.options.circle })
		];

		this.options.actions = options.actions || actions;
	}
});

To solve the dependency problem I think we need to create an intermediate ToolbarAction handlers that call the Draw/Edit handlers. E.g. L.Draw.polygon.ToolbarAction.

Can you explain what you mean by this?

I've started too complete the integration of Leaflet.toolbar with Leaflet.draw in branch: https://github.com/Leaflet/Leaflet.draw/tree/integrating-toolbar

@jacobtoye very cool to see you working on this again!


Change AVS monitor naming convention

Description
Changes the naming convention of newly created AVS monitors for SKRs by replacing subAccountId with instanceId.
Related issue(s)

This must not be merged yet, as it will break integration with the reporting tool


[Application] End Screen

Currently, after submitting the application form, the screen does not change.
Add a final screen that

[x] Inform that the application has been received
[x] Inform about the next steps

For now we don't have a back to the app button, because there is no deep linking. We have to discuss if this is needed.
Find issue here https://github.com/digitalfabrik/entitlementcard/issues/661

was solved by https://github.com/digitalfabrik/entitlementcard/pull/648


Found Typo

There are Kasaragod and Kasargod in Kerala data in state_district_wise.json
You can ignore Kasargod.

Hi, i would like to work on that.

Thanks for the report. Fixed in the sheet.


renderer: support GitHub-syntax callouts

GitHub allows the following format for callouts:
> [!IMPORTANT]
> Crucial information necessary for users to succeed.

e.g.

[!IMPORTANT]
Crucial information necessary for users to succeed.

This adds some special handling to the quote renderer to render callouts as Notion callouts, and also strip the prefix [!IMPORTANT] from the actual callout. See golden test, and also a real life example of the output:

#5
#4  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bobheadxi and the rest of your teammates on  Graphite

Notion callout supports background color, maybe we should take advantage of that? Same background color does not seem to provide enough visual importance 🤔

Same background color does not seem to provide enough visual importance 🤔

I've noticed that too, I'll take a look later today 😁


Remove SystemExit usage

SystemExit inherits from BaseException and should be used very sparingly.
https://docs.python.org/3/library/exceptions.html#SystemExit
Currently, the docs and examples are using it in several places.
https://docs.pydantic.dev/latest/concepts/pydantic_settings/#subcommands-and-positional-arguments
I suspect the core issue is the leaking of an argparse implementation detail (which  internally calls sys.exit).
This is also perhaps the source of inconsistencies in exit codes when an error occurs. Sometimes it's 1 and sometimes it's 2.
Acceptance Criteria

Remove usage of SystemExit in the docs
CLI Examples should adhere to the standard style for Pydantic error catching (e.g., ValidationError)

Possible Solutions

In Python 3.9, argparse added exit_on_error flag  to help solve this friction point with exit being called.
Subclass argparse.ArgumentParser and override .exit() or error() to raise the appropriate exception (from status != 0) instead of calling sys.exit.

Thanks @mpkocher for reporting this issue.
@kschwab Could you please take a look at this issue?

Yes, I agree with what @mpkocher raised. I'll work to push a fix in the next few days.

@mpkocher, I've modified the acceptance criteria one to:

Remove usage of SystemExit in the docs for non-zero exit codes

Otherwise, any application that calls --help would raise an exception. i.e., this issue only removes exit on error in favor of raising a SettingsError exception.

Actually, the more I think on this the more I see it as a feature request to add a cli_exit_on_error flag. Hardcoding exit_on_error=True isn't ideal either. Therefore, we can:

Standardize CLI parsing errors to raise SettingsError exceptions.
Provide a cli_exit_on_error config that defaults to True, just like argparse.

@mpkocher, I've modified the acceptance criteria one to:

Remove usage of SystemExit in the docs for non-zero exit codes

Otherwise, any application that calls --help would raise an exception. i.e., this issue only removes exit on error in favor of raising a SettingsError exception.

The CLI source has a fundamental difference over other all the other current sources in pydantic-settings.
There's no reading --version from an dotenv or YAML file and return "1.2.3" to the console. This isn't a mechanic of the other sources. This new CLI mechanic (--version, --help) needs to somehow be handled with the current "empty" constructor (e.g., MySettings() design . I believe this error handling is also coupled to the design (or the lack thereof design) of the main calling layer.
Misc thoughts that are perhaps more high level.

Overall, the design of Sources in pydantic-settings might have been better to use composition instead of inheritance. However, this ship has sailed.
If it's going to use inheritance, then perhaps using explicit constructor/init/factory methods of .from_env() or .from_cli() and avoid abusing/overriding the default Pydantic style constructor to be empty-able (e.g., MySettings()) This impacts the expected error modes.
settings_customise_sources is verbose. It would be useful if there was a terse and explicit way to communicate that you only want X source, or sources X, Y. This seems like a very common use case.
Perhaps adding .from_sources(Sources.ENV, Sources.CLI), or defining this at the declarative layer inheriting from BaseSettings.
argparse is thorny. I would try to hide the argparse implementation details as much as possible. If someone wants to dig/hook into a private method, there isn't anything stopping them. Making this public could dramatically increases the surface area of supported issues and use cases.

Thanks @mpkocher for sharing your thoughts.
I agree with you that pydantic-settings has some design issues. probably we can make it better in future.
are you happy with @kschwab implementation to address the SystemExit issue?
BTW, we are open to changes and PR is welcome to fix any of the mentioned issues.

argparse is thorny. I would try to hide the argparse implementation details as much as possible.

Agreed. My main feedback here is the solution can't be hardcoded, and argparse's exit_on_error behavior (for this issue) is reasonable.

There's no reading --version from an dotenv or YAML file and return "1.2.3" to the console. This isn't a mechanic of the other sources. This new CLI mechanic (--version, --help) needs to somehow be handled with the current "empty" constructor (e.g., MySettings() design .

Can you help me understand the relation here between this and removing SystemExit? If anything, I believe it will make things worse. e.g., with "no exit" on --help below, it results in a ValidationError since v1 is a required field:
import sys
from pydantic_settings import BaseSettings

class Settings(BaseSettings, cli_parse_args=True):
    v1: str

sys.argv = ['example.py', '--help']
Settings()
"""
 pydantic_core._pydantic_core.ValidationError: 1 validation error for Settings
 v1
   Field required [type=missing, input_value={}, input_type=dict]
     For further information visit https://errors.pydantic.dev/2.7/v/missing
"""

Wouldn't a user just do something like this:
import sys
from typing import NoReturn
from pydantic_settings import BaseSettings

class Settings(BaseSettings, cli_parse_args=True):
    version: bool = False

    def main(self) -> None | NoReturn:
        if self.version:
            print(self.get_version())
            exit(0)

    def get_version(self) -> str:
        return '1.2.3' # from dotenv, YAML, etc.

sys.argv=['example.py', '--version=true']
Settings().main()
#> 1.2.3

Or, perhaps more "pydantic", like this:
import sys
from os import environ
from typing import NoReturn
from pydantic_settings import BaseSettings

class Settings(BaseSettings, cli_parse_args=True):
    prog_version: str  # from any pydantic settings source (e.g., environment)
    version: bool = False

    def main(self) -> None | NoReturn:
        if self.version:
            print(self.prog_version)
            exit(0)

environ['PROG_VERSION'] = '1.2.3'
sys.argv=['example.py', '--version=true']
Settings().main()
#> 1.2.3

As a side, disregard the --version=true. We need to add a CliFlag[bool] notation that allows for marking optional bool fields as flags, such as --version.
Are you saying you want a chance to intercept the CLI parsed args before they get consolidated into the final object, such that you could check for a --version flag and exit early?
We could definitely do that, but it would be a new feature (i.e., separate from SystemExit). I think these are two separate issues.

Can you help me understand the relation here between this and removing SystemExit? If anything, I believe it will make things worse. e.g., with "no exit" on --help below, it results in a ValidationError since v1 is a required field:

I'm suggesting that parsing the args is tangling up the "app" part and "source" processing layer. There isn't really an "app" part of the current API.
The current "CLI Source" is fundamentally different than other sources and  perhaps warrants a different approach. For example, a new thin "CLI App" and "Cmd" abstractions (which you're somewhat hinting at in the examples you've listed above).
For context, I'm trying to port internal tools from pydantic-cli to pydantic-settings, then trying to write a small migration guide on pydantic-cli, then archive the project. However, I'm running into a bunch of friction points with duplication of layers in each tool because of the lack of an "app" layer. Specifically for CLI tools that are design with subcommands.

Are you saying you want a chance to intercept the CLI parsed args before they get consolidated into the final object, such that you could check for a --version flag and exit early?

I don't think there should be a requirement to have a general hook mechanism for --do-action. However, the basic functionality of --version (via cli_prog_version, or similar ) and --help should be supported.

We could definitely do that, but it would be a new feature (i.e., separate from SystemExit). I think these are two separate issues.

I believe the error handling mechanism is tangling these layers together. I'm not sure more configuration is the answer to the problem. There's already too many configuration parameters.

Something perhaps in this direction.
import sys
from pydantic_settings import EnvSource, CliSource, CliApp, Cmd

class AlphaCmd(Cmd, cli_name="alpha"):
    # define model inline, but can also use inheritance.
    name: str
    age: int

    def run(self) -> int:
        print(f"Mock running {self}")
        return 0

class App(CliApp):
    sources = (CliSource(parse_none_str=True), EnvSource())
    model: AlphaCmd

if __name__ == '__main__':
    exit_code = App().run(sys.argv) # useful style for testing
    sys.exit(exit_code)
    # or
    App().run_and_exit()

And Subcommands would be the same:
from pydantic import BaseModel
from pydantic_settings import EnvSource, CliSource, CliApp, Cmd

# You can use inheritance or define the model inline,
# or import it from your lib code. There's no difference.
class Alpha(BaseModel):
    name: str
    age: int

class AlphaCmd(Alpha, Cmd, cli_name="alpha"):
    def run(self) -> int:
        return 0

class BetaCmd(Cmd, cli_name="beta"):
    color: str
    def run(self) -> int:
        return 0

class App(CliApp):
    sources = (CliSource(cli_name="example-02", parse_none_str=True), EnvSource())
    model: AlphaCmd | BetaCmd

if __name__ == '__main__':
    App().run_and_exit()

More comments and notes on API design choices.

@mpkocher, many of the points raised above are relevant to #335. Can we address those points over there instead?
For resolving this issue, Remove SystemExit usage, I'm specifically focused on what happens when (in the latest example) a user runs App and passes --version (correctly) or --verizon (incorrectly). Is it expected that:

The CLI will always exit, even if error is encountered?
The CLI will only exit if no error, otherwise raise exception?
The CLI will never exit and only ever raise exception?

For resolving this issue, we can:

Support all three as a config.
Support a subset as a config.
Support only one (e.g., the current implementation always exits).

The only assertions I am making is to avoid no 3, and that solution no 1, which includes raising SettingsError on exit(status=0), doesn't make sense.
i.e., can "Remove SystemExit usage" be closed by solution no 2, cli_exit_on_error flag, or is there something else needed?


Chapter 11 - GCM and Scheduling

Main source of information:
Global code motion/global value numbering, Cliff Click.
https://courses.cs.washington.edu/courses/cse501/06wi/reading/click-pldi95.pdf
Additional sources of information:
Dominator Tree:
Figure 9.24, chapter 9, p 532, of Engineering a Compiler.
Also described in the paper 'A Simple, Fast Dominance Algorithm'
by Keith D. Cooper, Timothy J. Harvey and Ken Kennedy.
Loop discovery is described in:
Principles, Techniques and Tools, p604, 1986 ed
Discord comments:
15/May/24
Cliff: the anti-deps will be needed and are not in the paper.
so paper will work until we do fancy control flow with loads & stores, then you'll get rare loads-bypassing-stores illegally.
we can cross that bridge when we get there.
The dom depth in the GVNGCM paper:
11/May/24
what is meant by dom_depth in the paper?
Suppose I have dominator tree - is the depth the same for all children of a node?
Yasser:
i think Hayley and I ran into it being the opposite direction to what we figured
but it's depth in the dom tree yea
Hayley:
Should do, it's how many dominators a node has.
Indeed the comparisons need to be the other way around versus Cliff's thesis.
Impacts Find_FCA() - reverse the dom depth comparison.
Issue: Xmilia reported Scheduling moves Stores incorrectly
struct S { int f; }
S s = new S;
if (arg == 0) {
    s.f = 1;
} else if (arg+1 == 0) {
    s.f = 1;
}
return s;

since both s.f = 1 are GVNed and then the least common block is outside of the if blocks
Cliff: 17/May/24
as usual, lots of ways to slice these games -
split the CSE'd uses so no extra computation.  C2 eventually did this, but did not start this way
add Control to stores; C2 does this, so didn't CSE stores.

In general, think of these algos's and the SoN edges as tools to work with, not Golden Rules to follow.
If some setup of your edges or graph walking isn't suiting you, change it.
C2 does, I've left AA undecided for now.  Simple needs to pick soon.
25/May/24
Cliff:
pass#1, DFS post-order on inputs (a "upwards" walk, starting from Stop), sched early, set slot 0 of every data op to its highest input using dom-depth (computed in same pass).  Unreached If T/F projections indicate a never-reached infinite loop - should be handled before.  You can add anti-deps here as well, adding dependence-inputs to a Store before scheduling it high.
pass#2, sched late, DFS post-order on outputs (a "downwards" walk, starting from Start).  In the idom-path from down-most and up (still in slot 0), pick lowest frequency, estimated here by loop depth.
Here I don't need a side-array for the global part.
I do find it useful to have an array for the local part - the basic block - which you'll probably want to hand off to e.g. register allocation.  If you're just going to an infinite register machine (say, emitting C or Java not asm) you might could skip that as well.
28/May/24
RIght - 3 possible fixes -
Add control.  Adds an edge, Stores won't CSE.
Make Stores just NOT CSE
After CSE, re-split stores if they not fully used on all paths.

As soon as the Store does not CSE, it sinks in GCM to its lowest use, which is always where it started from

Handling anti-deps
From discord chat:
Darrick 28/May/24
Ok, there are a few pieces:
In the Graph class:
    public Graph build_ante_deps() {
        for( Node n : _nodes() )  n.build_ante_deps();
        return this;
    }

in the Node class:
    public void build_ante_deps() {
        for( Node n : ante_users() )  createName(_g.ad(), n);
    }

    // By default a node has no ante-users.
    public NodeUtil.Iter ante_users() {
        return NodeUtil.Iter.get(null,0);
    }

in nodes that are part of a chain, mem gets the previous node in the chain:
``
public NodeUtil.Iter ante_users() {
return mem().fast_users().filtered(n -> !(n instanceof CramStoreNode));
}

That's it!

My node structure has the idea that I can have named deps. I add a new named dep using createName, and the "name" is an AD object that I get by calling _g.ad():

public class AD {
public int _i;
public AD(int i) { _i = i; }
@Override public final int hashCode() { return (int)Util.mix_hash(_i); }
@Override public final boolean equals(Object x) { return x==this; }
public String toString() { return "AD[" + _i + "]"; }
}

More from Cliff:
01/June/24
I looked at C2's anti-deps.  I understand what its doing (I did write the code, but 25yrs ago).  Its fast & minimal, but complex.  We can lose at least 50% of whats going on, since Simple is simpler, but there's still plenty in there.
Here's a "short" description of the algorithm.
Run schedule early.
Run schedule late- add anti-deps DURING running schedule late.
Look backwards from the Load (follow the mem edge) to the "memory definer" - a start-mem-projection, or a phi-mem, or a store.
Look forwards from the mem-def to all its mem-def users.  There's always at least 1; there may be many.  These completely (all of it) and exactly (no doubling up) cover the forward memory space, sorta like a network flow problem.  (be sure to limit yourself to same-alias, because e.g. start-mem-proj produces all aliases).  Also, we can limit loads against final fields (we have none at the moment).
So now you got a candidate set of mem-defs; some of these need the anti-dep on the Load, but not all.
Since we're in the middle of "schedule late", we've already computed all the late schedules of a Load's users, and we have the Loads "Least Common Ancestor" of uses, the LCA or late position.
We inspect the set of mem-defs that might impact the Load, and either add a anti-dep from Store to Load, or raise the Loads effective LCA.
Going back one mem step from the Load, we have the Loads' mem-def.
Going forwards 1 set fro the mem-def, we have a set of candidate mem-defs that might impact the Load.
For Phi mem-defs, we look at the Phi inputs and place an effective use on that block; this will be used to raise the Load's LCA.
For stores, we do the same - until/unless we find stores with the SAME block as the Load's LCA.  Then we add the anti-dep edge to force ordering within the same block.
Anyways, I started at C2's anti-deps.  As said its fast & accurate & a little subtle.
It relies on the early-schedule, and the late-schedule of the Load's uses (before scheduling the Load).
It needs a Basic BLock structure; this can be represented in any number of ways.
It needs a side-field in the BB (again any number of ways, array-of-structs, struct-of-arrays, etc whatever)
Original
struct Bar { int b; }
Bar bar = new Bar;
bar.b = arg;
int x = 3;
while( hot_loop ) {
  if( common ) {
    b.b = 1;
  } else { // Very rare
    int tmp = b.b;
    x = x + tmp;
    b.b = 2;
  }
}
return x;

Here I expect @Darrick Wiebe and @Hayley Patton 's algo to add anti deps between BOTH Stores to the Load.
This will result in an effective schedule:
struct Bar { int b; }
Bar bar = new Bar;
bar.b = arg;
int x = 3;
while( hot_loop ) {
  int tmp = b.b;  // Load hoisted to hot common path
  if( common ) {
    b.b = 1;
  } else { // Very rare
    x = x + tmp;
    b.b = 2;
  }
}
return x;

Correct, but definitely sub-optimal.
Another bit:
"Cliff:
"yes" - because its simpler. Every node probes the hash table, no exceptions. Its quick & easy, no need for any cutout logic.
"no" - because GVN should never trigger any changes, so its pointless.
"yes" - because in a very closely related IR called a PDG, you CAN have GVN trigger on control nodes. A slight tweak and we're there.
"no" - However, the PDG "flattening" algorithm (ie the GCM equivalent) is a lot more difficult."
During last week's Simple demo, Simple did in fact make a new IfNode twice and hit the 2nd one in the GVN table - and this was intentional, and the peep in question would have failed if the IfNode was not GVN'd.

From Discord 20th June
Cliff:
Here's rough draft of algo:

Place Store first
Walk the idom path for where the Load could go (gonna get walked anyways looking for lowest frequency placement), and tag the path somehow.
Walk the Store's idom path from placement to shared Load->mem input.

If you touch a tagged block, you need an anti-dep.


⚠ Bofrost.at has degraded performance

In 477de3e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 846 ms

Resolved: Bofrost.at performance has improved in 8a01518.


useViewportScroll has been depreciated

https://github.com/framer/motion/blob/main/CHANGELOG.md#deprecated

Thanks for notifying @MrUltimate, I'll try and add support for v6.5.0 in the following days 👍

Hey @breadadams, thanks for dealing with this so quickly! I had another question I wanted to ask you: I'm building scroll based animations that rely on scroller-motion however, disabling it for mobile unmounts it completely. Is there a better way to keep existing animations on mobile without writing all the animation logic with native scroll fallbacks?

Np @MrUltimate!
I'm not sure I fully understand, would it be possible to provide a basic example (either a repo or a codesandbox/stackblitz style environment)?
If your animations that depend on scroller-motion are because they use the scroll position (e.g. taken from useScrollerMotion), you could probably fallback to the position from useScroll when disabling scroller-motion - but I might be misunderstanding the question.


Make logger configurable as a stdlib compatible interface

Proposal
In order to support different logging libraries, it would be nice to have logging be an interface to something compatible with the current stdlib log package.
For example:
import "log"

type Logger interface {
	Fatalf(format string, v ...interface{})
	Errorf(format string, v ...interface{})
	Warnf(format string, v ...interface{})
	Infof(format string, v ...interface{})
	Debugf(format string, v ...interface{})
}

Thank you for your proposal.
As I commented in another issue, for now, I'm still likely to use log/slog. But it is still open to change, so feel free to leave any idea about it.

But I need to figure out the interface-type logger. I think just the log/slog package would satisfy almost every case since there are already a lot of ecosystems built on top of log/slog.Handler for adapting third-party loggers. IMHO, only log/slog could be a logger that everyone agrees on like gofmt.

https://github.com/KimMachineGun/automemlimit/issues/5#issuecomment-1892329832

As I commented, v0.6.0 has been released with log/slog.
This issue is closed, but feel free to reopen it if you need further discussion about it.


SLuaSetting.cs cannot be complied for player

SLuaSetting.cs cannot be complied for player since it using UnityEditor features.
using UnityEditor;

#if UNITY_5
					_instance = AssetDatabase.LoadAssetAtPath<SLuaSetting>(path);
#else
					_instance = (SLuaSetting)AssetDatabase.LoadAssetAtPath(path,typeof(SLuaSetting));
#endif
					if(_instance == null){
						_instance =  SLuaSetting.CreateInstance<SLuaSetting>();
						AssetDatabase.CreateAsset(_instance,path);
					}

		[MenuItem("SLua/Setting")]
		public static void Open(){
			Selection.activeObject = Instance;
		}

Your code not updated

fixed


pythonPackages.karton-asciimagic: 1.0.1 -> 1.1.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123887 at d7e1537f run on x86_64-linux 1

2 packages built successfully:

python38Packages.karton-asciimagic
python39Packages.karton-asciimagic

Result of nixpkgs-review pr 123887 run on x86_64-linux 1

2 packages built:

python38Packages.karton-asciimagic
python39Packages.karton-asciimagic


remove gratipay from frontend

fix #1966
Any further comments to the service integration in other areas needed?
Let me know and point me, please!

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @tooomm!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS


Consider removing implicit 'map' argument in API functions

You can specify which map to operate on in may API functions by passing in an optional parameter, defaulting to the current global map, like so:
local tile = Map.tile(10, 10) -- same as Map.tile(10, 10, Map.current())

local map = InstancedMap:new(50, 50)
tile = Map.tile(10, 10, map)

This is convenient, but could lead to unexpected behavior if the user forgets to add the map argument even though they intended to. This has happened to the author on several occasions. This is annoying since there's no indication of this mistake except for mutated state in the current map. Then you have to figure out where the global map is being mutated from, which is not always obvious.
Making this a required parameter forces you to be explicit about the map you use.
local map = Map.current()
local tile = Map.tile(10, 10, map)

However, this would mean you'd no longer be able to write short one-liners like this (in the REPL, for example):
Chara.create("elona.putit")

Instead, you'd have to do this:
Chara.create("elona.putit", nil, nil, {}, Map.current())

(Of course, you could just write a replacement for Chara.create() for prototyping purposes that has the old behavior.)
Essentially, this would be a tradeoff of convenience for maintainability. Also, this is one of those design issues that's really hard to change later, so it has to be set in stone early on.

Note to self: Since Map.global is so common we could do this instead:
local tile = Map.tile(10, 10, "global")

Consider this: you want to implement a mod that contains multiple maps linked to one another updating at the same time. As in, the logic for a full turn can be run on a map even if the map is not the current one loaded. This means things like enemies coming up after you on stairs after a short delay become possible.
The only chance for this to become possible without forcing people to make changes to their mods is to remove the implicit map argument, if it doesn't affect the current map. Otherwise it will become a subtle bug that needs to be fixed in anything that can be run in a different map.
But this is if we were specifically aiming for having no bugs at all, and there will always be bugs in mods, sometimes catastrophic ones, so it's a question of what to optimize for, while such a thing is still possible to decide.

We should remove {ownerless=true} and instead do
Item.create("elona.putitoro", "ownerless")

and throw if the second argument is nil.

We should try to remove objects that are stored in locations outside the current map when it is saved.

If an object is ownerless, explicitly set location to "ownerless".
Set location to nil on save somehow.
On load, when a location is deserialized fully, make it set the location of all of the objects in its pool to itself.
Somehow remove objects with a nil location after this.

To avoid allocation we may have to call :deserialize() on the object to restore the location that got set to nil in the :serialize() method.


Remove BayesSearchCV(iid=) parameter deprecated in sklearn 0.24

Fixes https://github.com/scikit-optimize/scikit-optimize/issues/978
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/987
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/927
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/990
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/981 via updated scikit-learn
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/1006
Fixes https://github.com/scikit-optimize/scikit-optimize/issues/718
Closes https://github.com/scikit-optimize/scikit-optimize/pull/951

LGTM except for that one language suggestion.

LGTM except for that one language suggestion.

Please merge this!

my commit on this merge request. Sorry, but Ive got 2 troubles with this merge request on sklearn 0.24

@trinebrockhoff

@betatim We need to ship this fix. Afterwards, we need someone to tackle https://github.com/scikit-optimize/scikit-optimize/issues/718.

Any update on when this PR will get merged? @betatim

I suppose not as long as it's failing the CI. I'm tackling related years-overdue https://github.com/scikit-optimize/scikit-optimize/issues/718. Give me a few more days. :sweat_smile:

Looks promising!
With the latest commit, I've migrated the class to use sklearn's BaseSearchCV._run_search() API (https://github.com/scikit-optimize/scikit-optimize/issues/718). Thanks to @homarb's sketch, not a lot was needed. Unfortunate it didn't find its way in already in 2018.

Feel free to merge this when this looks OK and then move on with all the other patches :-) Thanks for the work @kernc !

@glouppe Would the notable change go into the 0.8.2 or the 0.9.0 whatsnew, in your opinion?

Time for 0.9!

Shall we merge? :)

I believe so. I think also a prompt release would be well accepted. This PR closes 7 issues with tens of subscribers. :grimacing:
git log v0.8.1..HEAD shows a few more notes to add to 0.9.0 changelog.

Is there anything blocking this? It appears to be passing CI with the author (@kernc) and a skopt contributor (@glouppe) agreeing that its ready to merge

I suggest adding support for multimetric scoring to BayesSearchCV to provide an interface closer to that of GridSearchCV and RandomSearchCV. Currently, trying multimetric scoring (e.g. because GridSearchCV was replaced by BayesSaerchCV) yields an obscure KeyError at L411, due to the result dict naming scheme changing between multimetric and single metric.
This doesn't appear too hard, as only L411 and L471 need to be adapted. I believe this is sufficient:

adding a new parameter to BayesSearchCV, for instance optimized_scoring, that defaults to "score". If multimetric scoring is used, this parameter must be set to the key of the scorer to use, similar to the refit argument (see below why the refit argument is not used)
adding a check for the above requirement to specify the additional argument. It is possible to use None as the default value, check for multimetric scoring by using the same code as BaseSearchCV.fit(), and defaulting or raising if no value was passed. Or we simply check for "score", assuming no metric is named "score" in a multimetric setting.
changing L411 to local_results = all_results["mean_test_" + self.optimized_scoring][-len(params):] or local_results = all_results["mean_test_" + (self.optimized_scoring or "score")][-len(params):] if a None default is used
adapting L471 to handle the multimetric case. This check is easier than the one for the new parameter, because at that point self.multimetric_ -- provided by BaseSearchCV -- is available

Using refit for this purpose requires handling callable refit (at least to raise an error if unsupported) and might change the effect of that parameter compared to BayesSearchCV and RandomSearchCV, so I think having a dedicated parameter is easier to implement and provide more functionality.
If @kernc and @glouppe approve this idea, I am happy to make a small PR.

adding a new parameter to BayesSearchCV, for instance optimized_scoring

The multimetric feature is more thoroughly discussed in https://github.com/scikit-optimize/scikit-optimize/issues/797. I'm leaning to reusing refit= as far as possible. If you can make a PR that effectively fixes https://github.com/scikit-optimize/scikit-optimize/issues/797, that'd be welcome.

Sorry for missing #797 !
I think I have a working PR, using refit as indicated. I tried to keep as much of GridSearchCV's functionalities as I could, and to provide clear errors for the few bits that are not supported (callable refit for instance).
Since the changes depend on your PR, should I PR on your fork @kernc , or should I make a separate PR in this repo ?

PR on your fork

I think that would be the easiest wrt integration.

@kernc Feel free to click the green button and merge this PR. The work comes mainly from you :) (It will then be easier for everyone else to build upon...)

True. The dev docs ask not to merge own PRs, but with everyone's approval ...

@QuentinSoubeyran You should now make a fix against master directly. :+1:

Is this merged into master? I just installed today, still a problem :(

Yes, this has been merged. Can you report the issue you have?

Hello, is there a schedule for a stable release including this fix? Currently, release 0.8.1 is still broken.

@glouppe This is what I was referring to. When I use 0.8.1 and still get this problem with sklearn version 0.24.2

Same here, still an issue with sklearn 0.24.1 and skopt 0.8.1. Line 432 of searchcv.py throws a wobbly unpacking the zip(*out)

Can anyone post an example? I'm away from home at the moment.

Even I am facing this issue.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Miniconda3\envs\pyga\lib\site-packages\skopt\searchcv.py", line 692, in fit
    optim_result = self._step(
  File "C:\Miniconda3\envs\pyga\lib\site-packages\skopt\searchcv.py", line 579, in _step
    self._fit(X, y, groups, params_dict)
  File "C:\Miniconda3\envs\pyga\lib\site-packages\skopt\searchcv.py", line 431, in _fit
    (test_scores, test_sample_counts,
ValueError: too many values to unpack (expected 5)

Hi!
Are there any plans to fix the issue with unpacking the zip(*out)?
Thanks!

While this PR was merged into the master branch, scikit-optimize 0.9 has not been released yet. The scikit-optimize version on PyPi (0.8.1 at the time of writing) is still incompatible with scikit-learn 0.24+.
For anyone needing the compatibility, you can install scikit-optimize directly from source with
pip install git+https://github.com/scikit-optimize/scikit-optimize.git

If you also need multimetric BayesSearch, you need to install from my fork until #1030 is merged:
pip install git+https://github.com/QuentinSoubeyran/scikit-optimize.git@multimetric

Hope this helps.

@kernc Could you make a release? I think that would help a lot of users :-)

(And in general, we need help from all of you with the project! No one is actively maintaining it anymore, unfortunately.)

Can you clarify that nobody is maintaining anymore? I see that a number of
employers and institutions (including big companies like Northrop Grumman)
have worked on it in the past?
On Thu, Jul 29, 2021 at 12:20 PM Gilles Louppe @.***>
wrote:

(And in general, we need help from all of you with the project! No one is
actively maintaining it anymore, unfortunately.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scikit-optimize/scikit-optimize/pull/988#issuecomment-889284828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBJO6DMVCGGH77XUMY7VNTT2F5V3ANCNFSM4WOLPEVA
.

--
Tony Kelly
829 Concorde Circle Unit 4202
Linthicum Heights, MD
Cell:<PHONE_NUMBER>
@.***
We can only see a short distance ahead, but we can see plenty there that
needs to be done. - Alan Turing

For anyone needing the compatibility, you can install scikit-optimize directly from source with

@QuentinSoubeyran , thanks a lot!
Your version from source is not rising the deprecated iid or zip unpacking errors anymore!

(And in general, we need help from all of you with the project! No one is actively maintaining it anymore, unfortunately.)

@glouppe is the problem fixed? Do you just need someone to publish a v0.9 release to PyPI? Or does more work need to happen still? I might be willing to answer a "call for maintainers", but it'd be helpful to know what's involved.
I'm also very interested in @QuentinSoubeyran's multimetric version, and if/how that can be merged upstream.

Any news on when 9.0 with sklearn >0.24 support will be released?

Thanks @QuentinSoubeyran
How can I update to the 0.9 version and get the multi-metric feature that I had installed from your branch above?
Narayan


python311Packages.google-cloud-speech: 2.20.0 -> 2.21.0

Changelog: https://github.com/googleapis/python-speech/blob/v2.21.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 241886 run on x86_64-linux 1

4 packages built:

python310Packages.google-cloud-speech
python310Packages.google-cloud-speech.dist
python311Packages.google-cloud-speech
python311Packages.google-cloud-speech.dist


Add E2E testing tool

📄 Context
The idea is to have automated regression testing when new changes are deployed. Unit tests are good, but they only deliver a certain level of guarantee, which is evident when mocking starts (No evil here, just part of the usual flow). Also, E2E tools have the advantage that they are often not attached to any specific underlying tech, behaving as a real user who also does not care what the App is running on. 😏
🔍 Tracking

[ ] Add Playwright setup to run against the application locally.
[ ] Add test cases for the Navigation menu.
[ ] Add test cases for the Home page.
[ ] Add test cases for the Applications page.
[ ] Add test cases for the Input's page.
[ ] Add test cases for the Application's input page.
[ ] Add test cases for the Send transactions
[ ] Add Integration with Github actions to run against the live website.

That is the gist. I will be converting each of the task list items into an issue later, but I think that is the gist of it.  Maybe the Send Transaction one will need to be broken into more pieces since the first may be the hardest one because it needs to interact with a wallet to be able to do any action (also will become the blueprint for the rest)
cc: @nevendyulgerov , @dandheedge


Subscribing to "test/+" does not receive any message

Describe the bug
Subscribing to "test/+" does not receive any message, but when I subscribe to "test/2" and publish to "test/2" I receive two messages.
To Reproduce
var options = new ManagedMqttClientOptionsBuilder()
            .WithAutoReconnectDelay(TimeSpan.FromSeconds(5))
            .WithClientOptions(new MqttClientOptionsBuilder()
                .WithClientId("ApiServer")
                .WithTcpServer("<IP_ADDRESS>")
                .WithProtocolVersion(MQTTnet.Formatter.MqttProtocolVersion.V500)
                .Build())
            .Build();

var _mqttClient = new MqttFactory().CreateRxMqttClient();
await _mqttClient.StartAsync(options).ConfigureAwait(false);
_mqttClient.ConnectedEvent.Subscribe(_ => Console.WriteLine("Client connected"));
_mqttClient.Connect($"test/+")
    .SelectMessage()
    .Subscribe(m =>
    {
        Console.WriteLine($"\tTopic {m.Topic}");
        Console.WriteLine(m.ConvertPayloadToString());
    }
    );

_mqttClient.Connect($"test/2")
    .SelectMessage()
    .Subscribe(m =>
    {
        Console.WriteLine("\tTopic test/2");
        Console.WriteLine(m.ConvertPayloadToString());
    }
    );

Hi, at glance TopicFilter is used to match topics, why not use MqttTopicFilterComparer  which has the same function and doesn't use RegEx ?
Thanks.

Thank you that's great 👍


Missing file input parameter type

Describe the Bug
Actions with file input parameters are not rendered correctly
Steps to Reproduce the Bug or Issue

In GA Designer, create a SFTP Get file content action
Input valid parameters, save
Change to Preview Designer and open the SFTP action
The file parameter will not be rendered properly

Workflow JSON
No response
Expected behavior
The file input field should show the correct file path.
Screenshots or Videos
Expected

Current

Platform And Browser

OS: Windows
Browser: Chrome, Edge

Additional context
No response
AB#17078835

yep this is just a missing feature, we never got the file picker editor in, for public preview, I can take this

Also should work against the onedrive file picker

Finished in #2165


social icons under profile don't allign

Environment

Minimal Mistakes version: 4.23.0
Ruby gem or remote theme version: minimal-mistakes-jekyll (4.23.0, 4.22.0) -> output from gem list
Jekyll version: 4.2.0
Git repository URL: https://github.com/RinkiyaKeDad/rinkiyakedad.github.io
GitHub Pages hosted (if yes provide URL to site): arshs.tech
Operating system: MacOS 11.3.1

Expected behavior
Social Icons under the profile should be alligned.

Steps to reproduce the behavior
By default.

Other

You need to add fa-fw to the classes.
https://fontawesome.com/how-to-use/on-the-web/styling/fixed-width-icons

I think I have done that. Here's the code from my _config.yml:
links:
    - label: "Email"
      icon: "fas fa-fw fa-envelope"
      url<EMAIL_ADDRESS>    - label: "GitHub"
      icon: "fab fa-fw fa-github"
      url: "https://github.com/RinkiyaKeDad"
    - label: "Twitter"
      icon: "fab fa-fw fa-twitter-square"
      url: "https://twitter.com/RinkiyaKeDad"
    - label: "LinkedIn"
      icon: "fab fa-linkedin"
      url: "https://www.linkedin.com/in/arsh4/"
    - label: "Dev.to"
      icon: "fab fa-dev"
      url: "https://dev.to/rinkiyakedad"
    - label: "Instagram"
      icon: "fab fa-fw fa-instagram"
      url: "https://instagram.com/rinkiya.ke.dad"

    - label: "LinkedIn"
      icon: "fab fa-linkedin"
      url: "https://www.linkedin.com/in/arsh4/"
    - label: "Dev.to"
      icon: "fab fa-dev"
      url: "https://dev.to/rinkiyakedad"

Oh I totally missed that 😅  Thank you so much for helping @iBug :)


A star

🛠 Issue (Number)

Issue no #556
👨💻 Changes proposed
Created AStar algorithm in C++, Java, Python
✔ Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[X] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots
C++

Python

Java

A star algorithm is huge, we can't reduce the number of lines in C :(

All SSoC'23 PRs will be accepted after 1st June 2023


Cannot see column names within tables/views or console

Hello,
I am new to DBeaver and have came across issue:  cannot view column names of tables or views.  Have tried various options to visualize them with no luck.  Is there a setting within the environment that will correct this; or a particular version of DBeaver?  I had the current version with this issue and did an uninstall and reinstall of prior version that an associate was using and was able to see the column names.  Both the current version and 21.1.5 did not correct my issues.  Please advise.
System information:

Edition	Windows 10 Enterprise
Version	21H1
Installed on	10/5/2021
OS build	19043.928
Experience	Windows Feature Experience Pack 120.2212.551.0

DBeaver tried both current version and 21.1.5 (another user had this previous version and column names were available)

using Redshift AWS

unable to see column names within tables or views, and within properties/columns console.
Steps to reproduce, if exist:  click drop down from table/view; 'loading' appears but column names do not.  clicking on view diagram/properties does not show views either.

I can recommend an Advanced connection view.

And again - screenshots can help us.

This would be an example of the script that is used creates a copy of
another schema/view and would be similar to:
'create or replace view CopyView.v_tableA as select * from
SourceView.tableA' with no schema binding'.
Does that make sense?
On Thu, Oct 21, 2021 at 2:03 PM Anastasiya @.***> wrote:

@kkoehleranalyst https://github.com/kkoehleranalyst
An example of table/view DDL (without columns) will be helpful. And info -
is the table in external schema or not.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/14331#issuecomment-948916807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWFBAMV6EEEIIRFJHWBQCFDUIBPY7ANCNFSM5GOJCH2Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

SourceView.tableA DDL will also be useful.

there is no update on the issue for a long time. if it is still actual for you - feel free to reopen it with additional info


pip for python2

It seems that pip is not installed for python2 by default. This is very confusing as this is usually the standard.
If we have python2, I suggest we add python2-pip

Maybe Arch is trying harder than other distros to move to Python3. I appreciate that. Has any package for Arch that you use really a dependency on python2-pip?

No it's not needed from my side. However, as long as we have python2 installed in my opinion we should have it installed properly.

Hm, I guess we should. Although this python duality is really ugly.

Added in b67142e37a51526cff5d03f901092a681d418430.


ARcore Plugin Off when building the first hololens scene

Message of this type are happening in the console : Failed to unload 'Assets/GoogleARCore...
Then in spectator Android scene, the prefab for camera is missing
ARCore Device (Missing Prefab)
Missing Prefab (Dummy)
However, we could build 2 different scenes with 2 projects (one for android & one for hololens) but we cannot find how to do the spatialisation alignement with QRcode

what version of spectator view are you using and what android scene are you trying to use? Master currently relies on ar foundation compared to ar core.

We have tried the 1.1.0 branch as it was indicated in the tutorial
We will try this week to work with the master branch and AR fondation
De : Chris Barth<EMAIL_ADDRESS>Envoyé : mardi 15 septembre 2020 19:48
À : microsoft/MixedReality-SpectatorView<EMAIL_ADDRESS>Cc : GAZZOTTI Stéphane 244849<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [microsoft/MixedReality-SpectatorView] ARcore Plugin Off when building the first hololens scene (#414)
what version of spectator view are you using and what android scene are you trying to use? Master currently relies on ar foundation compared to ar core.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/MixedReality-SpectatorView/issues/414#issuecomment-692873928, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ6JDZ4WT2NVJHL5ZKGU4WDSF6SGVANCNFSM4RE6WFGQ.

can you give the master link to use with git for the master branch ?

De : Chris Barth<EMAIL_ADDRESS>Envoyé : mardi 15 septembre 2020 19:48
À : microsoft/MixedReality-SpectatorView
Cc : GAZZOTTI Stéphane 244849; Author
Objet : Re: [microsoft/MixedReality-SpectatorView] ARcore Plugin Off when building the first hololens scene (#414)
what version of spectator view are you using and what android scene are you trying to use? Master currently relies on ar foundation compared to ar core.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/MixedReality-SpectatorView/issues/414#issuecomment-692873928, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ6JDZ4WT2NVJHL5ZKGU4WDSF6SGVANCNFSM4RE6WFGQ.

I guess I have found the right one
I have deployed on HoloLens and android
Application runs on HoloLens and android
When I launch the IP adress I can see axes (red blue and yellow) on HoloLens and the QR code is on the phone
Then Nothing happen ...
What is the next step ?
Thanks for your answer

De : GAZZOTTI Stéphane 244849
Envoyé : mercredi 16 septembre 2020 15:10
À : microsoft/MixedReality-SpectatorView; microsoft/MixedReality-SpectatorView
Cc : Author
Objet : RE:[microsoft/MixedReality-SpectatorView] ARcore Plugin Off when building the first hololens scene (#414)
can you give the master link to use with git for the master branch ?

De : Chris Barth<EMAIL_ADDRESS>Envoyé : mardi 15 septembre 2020 19:48
À : microsoft/MixedReality-SpectatorView
Cc : GAZZOTTI Stéphane 244849; Author
Objet : Re: [microsoft/MixedReality-SpectatorView] ARcore Plugin Off when building the first hololens scene (#414)
what version of spectator view are you using and what android scene are you trying to use? Master currently relies on ar foundation compared to ar core.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/MixedReality-SpectatorView/issues/414#issuecomment-692873928, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ6JDZ4WT2NVJHL5ZKGU4WDSF6SGVANCNFSM4RE6WFGQ.

It was an issue with qrcode reading


Integrate WebTransport Protocol Support into Swift-libp2p Library

In the current implementation of the Swift-libp2p library, there is a lack of support for the WebTransport protocol. This omission limits the library's utility in scenarios where low-latency, high-throughput communication is required, especially in web-based P2P applications.
I would like the Swift-libp2p library to integrate support for the WebTransport protocol. This integration should enable seamless, efficient peer-to-peer communication capabilities within web environments, leveraging the strengths of WebTransport such as minimal latency, better throughput, and improved connection stability compared to traditional HTTP/HTTPS transports.
An alternative considered was to utilize WebSocket or HTTP/3 protocols for P2P communications. However, these do not offer the same level of performance and flexibility in terms of bidirectional data streams as WebTransport.
The integration of WebTransport is particularly crucial in the context of developing advanced web-based decentralized applications (dApps) and services that require efficient real-time data transfer, such as streaming, gaming, or collaborative tools. Implementing WebTransport can significantly enhance the capabilities and applicability of the Swift-libp2p library in these emerging domains.

Hey @minchopm!
Thanks for putting this request together. I agree on multiple fronts here, swift-libp2p's current functionality is fairly limited, and that's partly due to missing key transport packages like WebTransport.
I haven't been able to devote as much time as I would like to swift-libp2p recently. Hopefully in the new year I'll be able to give this project the time it deserves.
In the meantime, if you would be interested in attempting to implement WebTransport yourself, I'd be more than happy to help answer any questions you might encounter along the way.


Cant take effect when chinese characters are in the text

As the title. It shows nothing.
And the flake8 can work with the same text.
works
print("this is a test")
doesnt work
print("这是一个测试")
After a while, ill test other languages.

Same issue.
linter-flake8 does not work with CJK (Chinese, Japanese, and Korean languages) characters, as I've just tested. It does not show any errors or issues when there are CJK characters in the file.

Niether Hebrew characters

Can you provide more details on your systems? I originally thought this was a duplicate of #282, but I'm actually unable to reproduce this as it works perfectly for me.

Actually, turns out that I was still using a test build of flake8 from the proposed fix for #282... which although these look like different issues might potentially be the same underlying issue.

Closing based on the fact that the fixed build of flake8 wasn't able to reproduce this.