Switch consul resolver to use ServiceAddress

Signed-off-by: Andrew Cornies<EMAIL_ADDRESS>

Hi, can you maybe shed some light around this change? what's the benefit?
https://stackoverflow.com/questions/40756293/difference-between-consul-service-definition-address-and-service-address

Hi @orefalo This change facilitates faas-nomad on single-node instance w/ multiple interfaces (docker0 +) etc. I suspect this will be the same address as before in most use cases.

Hi @acornies, that's what I understood from the link I provided, but glad you clarified.  I also found you other repos; especially this one - https://github.com/acornies/faas-nomad-demos. battling vagrant (actually more vbox) on catalina at this point


bug: Command failed with exit code 2 You may not have the required environment or OS to build this project

Type: bug
Platform: desktop browser
> ionic build ios
ERROR building one of the platforms: Error: /Applications/MAMP/htdocs/myApp/platforms/ios/cordova/build: Command failed with exit code 2
You may not have the required environment or OS to build this project
Error: /Applications/MAMP/htdocs/myApp/platforms/ios/cordova/build: Command failed with exit code 2
at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:131:23)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:756:16)
at Process.ChildProcess._handle.onexit (child_process.js:823:5)
OS Mac Maverich, have followed this tutorial http://ionicframework.com/docs/guide/installation.html

Greetings @shivanshuit914!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

This issue was moved to driftyco/ionic-cli#282


Update FilterCardinalityTransformer

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.69%. Comparing base (82ff57a) to head (2a96783).
Report is 19 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #336      +/-   ##
==========================================
+ Coverage   99.54%   99.69%   +0.15%
==========================================
  Files          49       49
  Lines        1305     1311       +6
  Branches       50       50
==========================================
+ Hits         1299     1307       +8
+ Misses          6        4       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fixup! Rename workflows folder to fix typo and fix broken builds

Stack:

#3
#8
#5
#7
#4
#6

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.


Support binding PVC to specific PV

Scenario

Volumes are not automatically defined
PVC requests will not complete
Egeria will not start

Required

Define volume manually
specific identifier for storage volume (PV) in our claims - for kafka, zookeeper, egeria, jupyter etc etc
Egeria will start

Currently egeria charts are only tested in environments where storage is automatically allocated. There are some issues open to support 'StorageClass' consistently. (currently we use the default storageclass)
The ‘claim’ is the request for storage
usually ‘the system’ will look at various aspects of the claim and decide which volume to allocate
For manual assignment, one suggestion is here -> https://stackoverflow.com/questions/34282704/can-a-pvc-be-bound-to-a-specific-pv
It looks like you would need to define the pv name in the spec of the pvc. That should probably be a variable exposed to the values file, and default to not being specified
For egeria pods, and for jupyter (since we define the pod) that seems fairly easy.
For kafka/zookeeper it would need to be in our kafka_cluster definition. https://strimzi.io/docs/operators/in-development/configuring.html has appropriate information
@dwolfson Can you add any further clarification on the scenario, how volumes are allocated, and what identifiers need to be matched
As a workaround it may be possible to retrospectively EDIT the PVCs that egeria has created, and modify appropriate fields to allow the pvc-pv link to be made

On further investigation it appears that the ability to specify storage class is in fact sufficient.
This was added in #252


kubectl 1.4.x not able to talk to Rancher Server v1.2.0-rc1

Rancher Version:
v1.2.0-rc1
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16.04 on AWS (Server: m4.large, Agents: t2.medium)
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)

Single-node Rancher Server layer
3 Rancher Agents
local auth configured
kubectl config generated via Rancher console

Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
k8s
Steps to Reproduce:
Install kubectl version 1.4.6 (latest release at this time)
Results:
$ kubectl get pod
Unable to connect to the server: http: server gave HTTP response to HTTPS client

Expected:
Accurate list of pods.
@deniseschannon

@soumyalj

Test with v1.2.0-rc2

Verified with v1.2.0-rc2


Field-level read policy should filter out the unmet data returned from findMany if the field is used in the filter

model User {
    id       Int    @id @default(autoincrement())
    email    String @unique @email @length(6, 32) @allow('read', auth() == this)

    // full access to all
    @@allow('all', true)
}

current

// count returns 1 correctly
db.user.count({ where: { email: { contains: 'web.com' } } };

// It returns all users, but only shows the email for current user.
db.user.findMany({ where: { email: { contains: 'web.com' } } })

expected
findMany should also return one record same as count.

Fixed in 2.5.0


MGMT-14686: Support extra manifests

/test ?

/assign @danielerez

/test unit-test

tested okay with with Factory and config-ISO machine configs.
will followup with a Doc PR.

/retest

/retest

/lgtm


How do I use this plugin?

I put the DiscordBotSP-0.7.2-jar-with-dependencies.jar in the plugins file on my server
where do I put DiscordBot-master. At the moment I put it in the plugins file.
When I start up the server I get this error
30.09 12:45:18 [Server] ERROR Could not load 'plugins/DiscordBotSP-0.7.2-jar-with-dependencies.jar' in folder 'plugins'

Try downloading from the link below - What is your server version?
http://jenkins.lolnet.co.nz/view/Lolnet Projects/job/DiscordBot/lastSuccessfulBuild/artifact/DiscordBotSP/target/DiscordBotSP-0.7.2-jar-with-dependencies.jar

My server version is 1.10.2
I got the same error


Find the triggering element of an event

What is missing?

I would like to see the actual trigger from an event as object in the data.
For example, imagine a div that can be either hidden or expanded. There can be a button that can be clicked to do this, but there can also be multiple buttons or links for that same action. I would like to be able to find the actual button that caused the event.
Bootstrap has this:
$element.on('shown.bs.collapse', function(e) {
    var $clickedBtn = $(e.target).data('bs.collapse').$trigger;
});

I would like to see something similar
$(document).on('on.zf.toggler', '.collapse', function(e) {
    var $clickedBtn = $(e.target).data('zf.toggler').$trigger;
} )

What is wrong now ?

Right now I have to find the triggering button by .find(`[data-toggle='${$(this).attr('id')}']`), but there might be other buttons that target the same ID.
Possible Solution

...
Context

I'm trying to make it as simple as possible. And the "on.zf.toggler" whatever event might also be a trigger for some other event, and that should also give back the triggering button.
Your Environment

Foundation version(s) used: 6.5.1
Browser(s) name and version(s): Safari
Device, Operating System and version: Mac

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] here are no other issues similar to this one.
[x] The issue title and template are correctly filled.

This would be really useful for all zf events.  I have an accordion and want to use data on the triggering item for some other actions.  It seems event propagation is halted before my event listener can react.
It looks like with the event ( in the case of accordionMenu, up.zf.accordionMenu ), it also returns the $target, however, this doesn't seem too useful in my case.  It would be great if we could get something like:
this.$element.trigger('up.zf.accordionMenu', [$target, $trigger]);
But it doesn't look like the $trigger gets passed into the up function, so I don't have a good sense of how big this change would be.
In the mean time, I wonder if there is a sane way to get the triggering element back?

Ok, well, I think this still stands as a valid request, but my situation was easily solved, maybe it will solve yours too.  Essentially, just add event listeners to all of your buttons.
var buttons = $('.button-1', '.button-2').on('click' function() { console.log($this.prop('id')); });
It's not so elegant, since you have to have selectors for all of the buttons beforehand which is a problem if someone adds a button you are unaware of.

e.target, e.currentTarget and so on should resolve this.
Not sure how a different solution should look like.
Do you have an idea for a proper solution?


Show what's going on while minting to user

While people use simple or classic mint, some bugs may happen or process goes successfully.
However if a user is on slow internet, the user really doesn't know if something is happening in the background
Would be probably nice to show the user what's happening in the background in some meaningful way.

I could take this one

@AndreyGrin are you working on that? If so, can assign you! :)
Could be joined with #722 I guess, it could be upper bounty range ;)

If someone wants to work on this 👀
Take charge whole experience of minting is important as first touch for new artists

It would be time to revisit and handle what's happening in the background for the user.

It would be time to revisit and handle what's happening in the background for the user.

can you imagine it as an infographic - animated SVG
I think there are 3 phases of minting going on:

upload to IPFS
writing to the blockchain
listing on the blockchain

or is it something else?

Do you have an idea of how the toast notification will look like?  @yangwao

It would be time to revisit and handle what's happening in the background for the user.

can you imagine it as an infographic - animated SVG I think there are 3 phases of minting going on:

upload to IPFS
writing to the blockchain
listing on the blockchain

or is it something else?

the process is a bit more complex but sure, @vikiival might expand on this and @thea-exe might take it :)

Do you have an idea of how the toast notification will look like?

we can re-use our fun facts loader or modal with infinity animation, or if you want to come up with something very own, let's go :)

Do you have an idea of how the toast notification will look like?
Yup we use notifications from buefy
https://buefy.org/documentation/notification

we can re-use our fun facts loader or modal with infinity animation,
Yeah this would be better

the process is a bit more complex but sure,

First tell user about publishing to ipfs
Then say upload success
user should sign the payload
waiting for tx processing
waiting for block finalization

First tell user about publishing to ipfs

Then say upload success

user should sign the payload

waiting for tx processing

waiting for block finalization

I can do:
5+1 (the sixth will be "done") SVG animations that will be loaded during the process
or one that explains the 5 points
example: https://codepen.io/madetoday/pen/MYxYeo/
what do you say?  @vikiival @yangwao @thea-exe

we have something like that now


[updatecli] Update Ldap crond docker image digest version to 422143538cb3a81f3d98d9054190b2076f7279397df7af6d15205c36bcda6138

Changelog
We couldn't identify a way to automatically retrieve changelog information
Reports
Source:
	✔  (dockerDigest)

Condition:

Remark
This pull request was automatically created using olblak/updatecli.
Please report any issues with this tool here

Superseded by https://github.com/jenkins-infra/charts/pull/420


Error opening Welcome after reloading

Make sure the File Explorer is visible
Create temporary profile
Reload window

🐛 Welcome editor fails to open.
https://github.com/microsoft/vscode/assets/22350/0d863c27-6db2-4e11-b05b-71cb17ab8474
cc @sandy081

Is probably due to: https://github.com/microsoft/vscode/pull/184770.

@cwebster-99 and I also reproduced this when testing out her walkthrough changes: https://github.com/microsoft/vscode-python/pull/21411


Native REPL should allow for environment configuration

For a lot of Python projects, in my case Django web projects, simply running a straight Python REPL isn't very helpful. There's a lot of environment setup and initialization that is required for the REPL to be useful within the context of the project. That's why there are facilities such as ./manage.py shell and with django-extensions ./manage.py shell_plus.
Those tools are already capable of launching different Python REPLs such as the default one, bpython and iPython. It would be great if they could seamlessly launch the VSCode native Python REPL in the same way.
Failing that, there should still be extensive configuration options for the native REPL. What directory does is run in? What environment variables to set automatically? What Python code to run automatically at the start of every REPL instance?
iPython profiles is a good place to start looking for what kinds of configuration options are desirable. Every time I have ever wanted to change the behavior of a Python REPL, I've found it was possible to do with iPython.

Hello @Apreche, thanks much for your suggestions on improving the REPL experience. I kindly appreciate it.

Failing that, there should still be extensive configuration options for the native REPL. What directory does is run in? What environment variables to set automatically? What Python code to run automatically at the start of every REPL instance?

I do agree with you that equivalent or similar concept of IPython profiles would be great addition to the REPL experience, especially some sort of start up script that would run at the start of session which would allow users to automatically set their desired variables (such as environment variables) in a consistent manner. Or moreover, additional things that are listed in the example config file such as which scripts to automatically execute in each instance of iPython.
In terms of django related, I believe there is already a feature request on this: https://github.com/microsoft/vscode-python/issues/13027

I think the bot closed this one by mistake, since there was no additional information requested by @anthonykim1, but rather an acknowledgement that it would be a neat feature. So, should we reopen this? :)

@jgorset Correct, let me reopen this with a better tag this time.

I am keeping this opened since it already has over 9 votes.

Related as well: https://github.com/microsoft/vscode-python/issues/13027

I generally like how it looks comparatively to the usual terminal and I also like how it opens on the right side of vscode.
I would like to know if there are any details regarding making it easier for me to use in relation to my current projects.
For now however, I find it a bit harder to use with poetry as my environment is not interconnected with Python RELP or I just have little information regarding how to use it appropriately. My imports from my other scripts no longer work within the same file location of my script. My usual process was running python interpreter from the terminal and then hitting (shift + enter) to run selected lines and piecing them together one by one until I felt comfortable with the script running. Is it still possible to do something similar to this?
Thank you and best regards


Settings editor needs minimum size constraints

The new settings editor should have minimum size constraints:

For example, the old settings editor can't go smaller than this:

Cool, I didn't realize I could do that...


Fix Download CSV button position

resolves https://github.com/aqualinkorg/aqualink-app/issues/914
Updates the condition of placing extra padding

@PullRequest, since this is all open source you can actually follow the links manually here.
Here is a link to the site that has been deployed in a surge staging environment: https://aqualink-app-915.surge.sh/sites/184
Here is a link to the original issue showing the CSV Download option has no padding during the load operation.
https://github.com/aqualinkorg/aqualink-app/issues/914
This appears to be fixed now.


NumberBox AutomationProperties.Name and Min/Max is Ignored by AutomationPeer

Describe the bug
Setting a NumberBox's AutomationProperties.Name attached property is ignored by its AutomationPeer. The Minimum/Maximum values are also not used but should be.
Steps to reproduce the bug

Set the AutomationProperties.Name attached property of a NumberBox in XAML
Using the Windows Narrator, focus the NumberBox (and therefore the InputTextBox inside it)
The NumberBox AutomationPeer and Narrator will not use the AutomationProperties.Name when the InputTextBox is focused
The NumberBox AutomationPeer and Narrator will not use any Minimum/Maximum values

Expected behavior
This should behave the same as the Slider. The AutomationProperties.Name should be used first then a description of the value. Additionally, the AutomationPeer should really give the min/max values of the range as well. The Slider just gives a percent but the NumberBox needs to be more specific.
Screenshots
N/A
Version Info
NuGet package version:
Microsoft.UI.Xaml 2.4.0

@StephenLPeters Yea, thought it sounded familiar. I should have looked in more detail. That said, I'm expanding it to also add the Minimum/Maximum values as well as that's pretty important for accessibility.
I ran across this over the weekend with WinUI 2.4.0. I'll update to 2.4.2 and test again for the Name property.

I looked at the change and I do think it should fix the name issue. @YuliKl is there someone from the accessibility team we can ask about what to do about the min and max values?

The API looks similar to RangeBase - should the peer support IRangeValueProvider ?

@StephenLPeters I tested this again with latest 2.4.2 of WinUI -- it still has an issue and doesn't read aloud the AutomationProperties.Name.
"Edit zero, zero selected" is all I get with the below code.
<mux:NumberBox
  x:Name="Channel1NumberBox"
  AutomationProperties.Name="Red Channel"
  Grid.Column="1"
  Grid.Row="1"
  CornerRadius="0,2,2,0"
  VerticalAlignment="Center" />

I also notices that IRangeValueProvider is implemented already
https://github.com/microsoft/microsoft-ui-xaml/blob/86a7d62bf8141a1f3e141d3ade7a69bce02063c1/dev/NumberBox/NumberBoxAutomationPeer.cpp#L66
I think the issue might be related to focus. It's behaving as if only the InputBox is focused -- and it is but only as a part of the NumberBox. NumberBoxAutomationPeer is not used and instead narrator is just using the default AutomationPeer for TextBox.

@SavoySchuler FYI. Perhaps you can reach out to someone on the Accessibility team for help.
I'm also wondering whether #1882 is related.

I think the issue might be related to focus. It's behaving as if only the InputBox is focused -- and it is but only as a part of the NumberBox. NumberBoxAutomationPeer is not used and instead narrator is just using the default AutomationPeer for TextBox (which doesn't have an AutomationProperties.Name set as that is part of NumberBox).

I think that's exactly right. You'd expect to have the same issue with AutoSuggestBox, but in its OnApplyTemplate is forwards the Automation name to the TextBox part. It looks like editable ComboBox needs the same treatment.
More generally maybe we should teach TextBoxAutomationPeer to work with its templated parent when it's acting as a template part. In the example of NumberBox, it needs to be a range provider for the sake of min/max.

@MikeHillberg Is there anything we can do in WinUI 2 to prevent the TextBoxAutomationPeer to interfere with us here and allow us to pass Min/Max to UIA?
@ranjeshj Would it be fine if I create a PR to pass the AutomationProperties.Name to the TextBox so we can fill that gap? Also, when AutomationProperties.Name is not set, but the header of the NumberBox is set, should we pass the header value as AutomationProperties.Name value? After all, that is one of the ways the TextBox gets its UIA name.

@chingucoding lets give the same treatment for automation name in the mean time (and open a separate issue to track TextBoxAutomationPeer to understand the templated parent scenario).

@ranjesh Just to be sure, so should we apply to the same header handling logic to numberbox or should we just pass the AutomationProperties.Name value to the textbox?

Do we have the header handling logic in WinUI already ? If so, lets match that pattern. I was thinking we can lookup the automationproperties.name and use if if it is valid, if not fallback to the header.

I think we have a helper for this that get's us the appropriate UIA name depending on the properties set. Though this would require us to listen to changes on the AutomationProperties.Name property so we can update the textboxes UIA name accordingly.


[V2] Provided AWS iam policy no longer works

The policy provided at https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2_ga/docs/install/iam_policy.json is no longer valid for amazon/aws-alb-ingress-controller:v2.0.0-rc3
It looks like the default tags being put on the resources has changed from ingress.k8s.aws/cluster  to elbv2.k8s.aws/cluster. Changing all instances of ingress.k8s.aws to elbv2.k8s.aws in the iam policy document resolved the issue

Fixed with https://github.com/kubernetes-sigs/aws-alb-ingress-controller/pull/1498


Japanese translarion request for Tenant to tenant migration feature of Dynamics 365

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Link to article:
Original (en-us)
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/move-instance-tenant
Translation (ja-jp)
https://docs.microsoft.com/ja-jp/dynamics365/customer-engagement/admin/move-instance-tenant
Problem:
Original version was published on April 25 2019 and it says "now upports tenant to tenant migration.". Translated version was published on January 15 2019 and it still says "doesn't support tenant to tenant migration."
Please prioritize to translate this article because many japanaese customers are interested in tena;t to tenant migration feature on Dynamics 365 v9.x.

@SonjaSaltzman Can you please take a look at this issue?

@vinceno and @krisre  could you please check into this?

@TakiyaNakano-MSFT - Takiya, this file will be included in our HO next week and the string will be updated to the correct phrasing.  I apologize it is taking so long to get this fixed.
@SonjaSaltzman @vinceno - FYI.


Use .rustfmt.toml

Summary of changes

Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes #2512
Other information and links

Change checklist

[ ] I have performed a self-review of my own code,
[ ] I have made corresponding changes to the documentation,
[ ] I have added tests that prove my fix is effective or that my feature works (if possible),
[ ] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

It's a bit weird that the max comment length is shorter than the max line length. Can we increase the former? Or do you think it's better this way?

I guess yes, we had too long comment lines @LesnyRumcajs

I guess yes, we had too long comment lines @LesnyRumcajs

@tyshko5 I think what @LesnyRumcajs means is the default comment_width being shorter than max_width

I guess yes, we had too long comment lines @LesnyRumcajs

@tyshko5 I think what @LesnyRumcajs means is the default comment_width being shorter than max_width

Yeah, exactly. Personally, I'd change it but it's not a huge deal.

They must have chosen these defaults for some reason, I don't think it's a big deal either so let's merge this as it is? @LesnyRumcajs


Create multiple databases

When using root access I am not able to create multiple databases inside a single container. I get grant privileges error.
mysql> CREATE DATABASE demoDB;
Query OK, 1 row affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON demoDB.* TO 'demo'@'%' IDENTIFIED BY 'demo';
ERROR 1044 (42000): Access denied for user 'root'@'%' to database 'demoDB'

To resolve this I have to:
mysql> UPDATE mysql.user SET Grant_priv='Y', Super_priv='Y' WHERE User='root';
mysql> FLUSH PRIVILEGES;
mysql> GRANT ALL ON *.* TO 'root'@'localhost';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON demoDB.* TO 'demo'@'%' IDENTIFIED BY 'demo';
Query OK, 0 rows affected (0.00 sec)

By default, root user does not have grant and super privileges.
Any help is appreciated. I need to make sure the mysql 5.6 images works out of the box for me otherwise I will have to rebuild a new image.

@hhorak something you guys are interested fixing?

@nitintutlani root should have super privileges. When I start the container with docker run -ti -e MYSQL_ROOT_PASSWORD=pass --rm openshift/mysql-56-centos7 and then execute mysql from inside of the container, I can see this:
mysql> select user,host,Grant_priv,Super_priv from mysql.user where user='root';
+------+--------------+------------+------------+
| user | host         | Grant_priv | Super_priv |
+------+--------------+------------+------------+
| root | localhost    | Y          | Y          |
| root | 3945ff9feb04 | Y          | Y          |
| root | <IP_ADDRESS>    | Y          | Y          |
| root | ::1          | Y          | Y          |
| root | %            | N          | Y          |
+------+--------------+------------+------------+

So that means that the Grant privilege is only enabled if you are connecting from localhost. Can you verify that creating a new database and then granting the access rights to the user will work when executed from the inside of the container?
We could grant the granting privilege to root no matter where he connects from.

Sorry and yes, the error I received is related grant_priv only. Looking at the above I am hopeful, this should work and can be also be fixed from inside container shell.
However, if you consider this to be part of database container assembly, I would request you to update this image. So we can get a true root access without any post assemble tweaks.


gowin_pack broken -> apicula 0.3.1 needed

The problem with gowin_pack presents as in ticket YosysHQ/apicula#99 and has been fixed in apicula 0.3.1
But apycula=0.3 is set as dependancy for the pip package yowasp-nextpnr-gowin 0.3.dev303, which prevents new installs getting a working version (where I tripped over it).
Recommend changing that dependancy to  apycula>=0.3<0.4 so any other minor fixes like this to apycula get picked up and fixed without requiring further change to the dependancy setting here.
For now a workaround is  pip install -U apycula which then complains that yowasp-nextpnr-gowin is incompatible because it requires apycula=0.3, but otherwise works.

The build script takes the last version of apycula from pypi and encodes that as a dependency so that the versions always match. So the next release will have the latest apycula as a dependency. There is indeed no guarantee about backwards compatibility, so while it might work most of the time, it's better to ensure matching versions.

Okay, then if apicula bumps, the build script also ought to bump, each time a fresh version hits pypi. It's a bit embarrassing to have something broken for three weeks when it could have been fixed.
Apycula 0.3.1 was on pypi April 12th, and it's obviously only a non-breaking minor release update to fix this issue; otherwise it'd have been version 0.4, if it did break anything.
Is there any problem with at least trying to generate a new, matching version as soon as it bumps, for minor point releases like this? Does this 0.3.1 bump really actually break compatibilty, or are you just assuming it does? Is there really much danger in using a dependancy code like >=y.x,<y.(x-1)?  (where y.x is a match for current minor version).
Surely if they're just going to drop a .1 on the end of their version, for a release which is only a fix, and not a break, it shouldn't be difficult to just regen a matching version assuming no breakage? That way, you don't need to intervene when your dependancy is just fixing a little gaffe like that, and your own release gets fixed about as quickly, and isn't stale for three weeks or until someone trips over it. Beware newcomers can and will trip up on minor things like this, and rather than bothering to open a ticket, will often just discard the whole project into the 'too hard' bin. This is never good for a project. They'll remember that YoWASP is unreliable, but the fresh versions elsewhere worked, and just put it down to YoWASP not being ready to depend on.
Odds are, if they do break something and mislabel it as just a version_string+'.1' , then you could complain, and have them re-release a non-breaking minor version (perhaps merged from an older commit, before the blamed one) with just another minor point increment.
This is how version numbers are supposed to work. The whole point is to allow the author to fix tiny errors and omissions like this and just increment the minor number so everyone gets the fix, whilst being able to trust that an update like this does NOT risk breaking compatibility.
You're in the sticky situation of needing to be closly-coupled to the bleeding edge of your main dependancy. That means, I think, that you should just have your build system automatically bump for at least minor point updates - anything in after the second period in the version number. It shouldn't take a ticket.

Does this 0.3.1 bump really actually break compatibilty, or are you just assuming it does?

Since it is not guaranteed that a bump like this will never break compatibility I assume that it does to be on the safe side.

They'll remember that YoWASP is unreliable, but the fresh versions elsewhere worked, and just put it down to YoWASP not being ready to depend on.

This is exactly the kind of scenario I'm trying to avoid. Right now, you get an error from your package manager that clearly indicates that there may be a compatibility issue; and prompts you to open a ticket, or perhaps avoid using this package entirely. These are acceptable outcomes. If there was an incompatibility, and it was silently accepted by the package manager, then you could silently get a bad bitstream, which is a significantly worse outcome: it would result in a lot more wasted time, and is a bigger breach of trust.

This is how version numbers are supposed to work. The whole point is to allow the author to fix tiny errors and omissions like this and just increment the minor number so everyone gets the fix, whilst being able to trust that an update like this does NOT risk breaking compatibility.

Bluntly, I do not care how version numbers are 'supposed' to work. I have asked @pepijndevos how they work, and they do not work like that for Apycula. YoWASP will change its policy if and only if Apycula changes their policy to provide the necessary guarantees.

This is exactly the kind of scenario I'm trying to avoid.
You didn't.

Right now, you get an error from your package manager that clearly indicates that there may be a compatibility issue;
Right now, everything a-OK - no errors, we're back to what you were trying to avoid. 0.3.post31.dev324 is just fine.

But the thing is, I didn't get here directly because of that error. There was no error when I installed yowasp-nextpnr-gowin.
What happened was that I installed yowasp-nextpnr-gowin, and it pulled in the broken 0.3 version of apycula, without an error. Everything seemed good.
But the first time I tried to use it,  gowin_pack failed with an obtuse error. Because it was broken. This also would have happened to everyone else, most notably including everyone giving yowasp a try for gowin.
So I went hunting the problem with Apicula. It seemed the sort of thing that would honestly not have been your fault - it didn't even occur to me to come here first.
The only reference I found, after digging through both open, and closed tickets, was something that seemed a match. Pn that ticket, it was resolved with:

Try the master branch

And hence clearly already fixed before catkira reported it on the second of April.
I then forced apycula with the manual install -U line 'workaround' I quoted above.
At that point, having already solved my problem (when I noted that Apicula was indeed fixed) I realised the problem was that you were out of date - and now got the incompatibility warning from pip.
Looking at the last-published date for apicula 0.3.1 on pypi, I was astonished to see it three weeks stale.
How could this be? Isn't the point of YoWASP to be automatically rebuilt? Clearly someone isn't respecting how the version numbering system convention works.

Bluntly, I do not care how version numbers are 'supposed' to work.

🤷♂  Sure. Though in this case, they did work how they were supposed to. The 0.3 release was essentially a mistake, to be overridden everywhere downstream with 0.3.1 without risk of new breakage, as indicated by the version number convention.

... we'll run out of space in about 4 months of daily nextpnr commits.
This is why it's done manually.

Okay, I only mean to suggest that whenever apycula goes to a greater step, which now would be >0.3.1, but <0.4, that the upload ought to go ahead without requiring manual intervention, as an exception to handle this sort of fix, which is fairly likely to be a common occurrence, the state of art being what it is right now.
That way you're not waiting for the good fortunes of good Samaritan appearing to contribute time to submit a ticket appearing to prompt you to fix something that you otherwise could have avoided breaking.
Deps in your pypi packages indeed ought to stay an equality match; I didn't mean to imply that it shouldn't.
My apologies for miscommunication - that's on me and my poor writing.
Nightly is indeed overkill, and not doing them is reasonable given your limitations.
But I think a point update push from above like this is probably always urgent enough to make it an exception.
Thanks again.
And by all means things are fine now - ticket closed, issue resolved, all is well. 👍

Okay, I only mean to suggest that whenever apycula goes to a greater step, which now would be >0.3.1, but <0.4, that the upload ought to go ahead without requiring manual intervention, as an exception to handle this sort of fix, which is fairly likely to be a common occurrence, the state of art being what it is right now.
Deps in your pypi packages indeed ought to stay an equality match; I didn't mean to imply that it shouldn't.

There's now infrastructure (https://github.com/whitequark/track-pypi-dependency-version/) to handle this sort of thing, though it's not currently used for Apycula.


fix gruntfile for github

@lucyhe can you take a look at this, how did this work before? that npm never had dist/ directory, did it?

@salomegeo I think you fixed this a couple days ago by running the build command for freedom-social-github, are you fine with closing this?

correct


Footer overlaps with mapping on

This issue relates to using IPT for publishing Camtrap DP and is not applicable to production IPTs.
On the mapping page (schemaMapping.do) the footer overlaps and hides mapping fields:

Couldn't reproduce that, it seems it was fixed in the 2.6

Try https://ipt3.gbif-uat.org/manage/schemaMapping.do?r=camtrap-test&id=http%3A%2F%2Frs.gbif.org%2Fschemas%2Fcamtrap-dp&mid=2 in Firefox.

Redeployed new versions there, Firefox is fine now too. Closing this

This issue is still present or returned on ipt3.gbif-uat.org. Maybe the deployment there has not caught up with 8a10381?

Thanks @peterdesmet
I'll investigate

I removed some redundant css and don't experience this issue.
@peterdesmet Could you confirm please


Issues with the guide "ToDo List app"

Describe the bug
I'm new to Avalonia and MVVM, so I wanted to take one of the tutorials to get easily started. But the guide is not matching with the current Avalonia version in terms of stuff looking different in Visual Studio and on the guide.
To Reproduce
Steps to reproduce the behavior:

Follow this guide step by step: https://docs.avaloniaui.net/docs/next/tutorials/todo-list-app/

Expected behavior
A beginners guide is most useful when it can be followed 100% the experience described. Please let someone knowledgable go through it and fix the issues coming up in the documentation.
Screenshots
Issue 1
As an example I adjusted my content like shown here:
https://docs.avaloniaui.net/docs/next/tutorials/todo-list-app/main-window-content

But getting an error of "Unable to resolve type MainWindowViewModel from namespace using:ToDoList.ViewModels Line 13, position 6"
As correctly the "MainWindowViewModel" is not created it seems.

Issue 2
Here is written "Locate the Models folder": https://docs.avaloniaui.net/docs/next/tutorials/todo-list-app/creating-a-model
Which is not created by default.
Same issue here: https://docs.avaloniaui.net/docs/next/tutorials/todo-list-app/creating-a-view-model#view-model-to-model-dependency
As "MainWindowViewModel" is not existing
This leads to other issues later on following the guide.
Desktop (please complete the following information):

OS: Windows
Version Avalonia for Visual Studio 11.1

Additional context
For me as beginner it's hard to get into Avalonia and MVVM programming when the basic tutorial is not working. As I'm confused by the missing MainWindowViewModel and other stuff. I solved some if it by looking at other tutorials but that's not the intention of a tutorial for new users.
Sure it's an additional learning oportunity, but I would like to understand the basics first before I start debugging it.
Thanks you

Hi @Biepa and welcome,
... yeah we had a huge release a few weeks ago which changed just a lot. I need to work on this sample to update it. It's on my list, but as I have to do it after my "normal" job it takes some time. Sorry for the inconvenience 🙈 .
Meanwhile please also explore: https://github.com/AvaloniaUI/Avalonia.Samples It's already up to date.
also feel free to join out telegram community chat: https://t.me/Avalonia
Note: I'll move this issue into Avalonia.Samples as this is where it belongs to. Stay tuned :-)
Happy coding
Tim


[Question] Some questions about the state of the project

Is the project active?
Is there a plan to migrate to .net 7 (and in future .net 8)?
When is there a plan to release "stable" version 2?

As explained in https://github.com/natemcmaster/DotNetCorePlugins/issues/117, the only pieces of work I had originally planned to do were for maintenance.
However, given little interest I have in maintaining this and that there have been more questions asked than real bugs in the code, I'm considering archiving this on GitHub so there is less confusing about whether opened issues will actually get fixed or not. Basically -- they won't because I'm was the only maintainer and I lost interest in this project years ago.

It’s good to hear you found it useful!
To be clear, I haven’t archived yet. I’m considering it. If other people want to chip in to maintain it, we can keep this alive. But as you can guess by the slow responses, I’m not very active on GitHub anymore.

Big fan of this library -- it's by far the easiest to use of the few that are out there. For my project, the hot reloading feature is absolutely fantastic. Users don't have to restart the entire application to get an updated version of a component 😄

I want to chime in that I'm also a huge fan of this project. I wrote an internal-use app using the 2.0 Beta version that has gone into production and the developers that maintain it are thrilled with the simplicity of adding new functionality by releasing simple plugins.
I don't know if you've had any luck in getting someone to help you maintain it, but I'm willing to donate some time to get 2.0 to a release if there's a cogent list of changes that need to be made.

I just wanted to mention that this project is a gem in the .net ecosystem especially when working with microservices. I think we should all put efforts to pushing it keeping it alive.
Also wanted to drop this here to show that it's not just me, and there are thousands of us out there! :)

Thanks all for the supportive comments!
I released the 2.0 beta to nuget almost 2 years ago, around the time personal changes in my life made it so I had less time for open source. I parked all open source work, but am finding myself with a little time to look at things again.
As far as getting 2.0 to a stable release, the main thing to do is test and make sure it works. If I recall correctly, the only real change between 1.4 and 2.0 beta was that I deleted a bunch of dependencies that were necessary to make plugin loading work in .NET Core 1 and 2. Now that .NET 5+ has stabilized quite a bit, I think those old versions of .NET are not working supporting anymore. Dropping that simplifies the dependencies of this library.
If there are other big features or bugs you want to contribute, let me know. We can review the backlog of issues open on this repository for ideas.

I also would like to say thank you for your time and effort.
I'm in the process of preparing to migrate an old plugin-based app that used Autofac to .NET8.
When searching for alternatives I see your packages in multiple places and after reading GitHub issues I'm sure it will work perfectly.
I'll try to prepare POC in the next couple of days using version 2.0.0 and report any problems/bugs. Or course I'll try to contribute as much as I can.
Again, thank you 🙂


add enum error for carplatenot found and add ت plate for taxis

You need to run 'cargo fmt' to pass the style check


Fix comms benchmark import issues and support MPI/slurm launching

Currently users need do either launch with ds_bench, deepspeed or append the DeepSpeed repo to their PYTHONPATH to avoid an import error when launching communication benchmarks.
These changes both fix the import errors by automatically appending the python sys path before import, and enable automatic MPI/slurm environment discovery similar to how we detect it in [deepspeed/comm.py](https://github.com/microsoft/DeepSpeed/blob/4ae3a3da0dfd19d7ab7a76e7c742ac12f44fc1c0/deepspeed/comm/comm.py#L664). This also enables MPI launching for both the pytorch distributed and deepspeed comm backends.
Tested on up to 2k GPUs.
I also updated the README to be more specific and comprehensive.
@jeffra @awan-10

These test failures look unrelated to the PR

Looks like some conflicts are showing up with the changes in https://github.com/microsoft/DeepSpeed/commit/0acf7e9c489def74d3ac05ee91eabfb8280a1dba.
The reason for runtime-checks like https://github.com/microsoft/DeepSpeed/blob/3879a503ae601deb7ad9a3758d488cc91889a08f/benchmarks/communication/all_gather.py#L40 and the lack of top-level deepspeed imports is to enable users to benchmark communication ops using pure torch.distributed even without deepspeed installed (e.g. users of NeMo, Megatron-LM, fairseq, ColossalAI, etc).
I'm of the opinion that we should preserve this behavior for the comms benchmarks (i.e. no deepspeed.* top-level imports and wrap all deepspeed- or torch.distributed-specific code in an if args.dist == 'torch/deepspeed' check), but I think someone from the deepspeed team like @tjruwase and/or @jeffra have the final say. Can one of you provide comment?

Conflicts are resolved, and CI failures look unrelated @jeffra

I have no idea why formatting CI tests are failing now. I ran pre-commit checks before committing? I can't seem to reproduce these on my end.

@Quentin-Anthony, check your pre-commit and clang-format versions. Upgrading worked for me.

Ok all checks are finally passing!


Support following fetch redirect responses

There are instances where redirect responses to fetch requests aren't being followed:

https://github.com/mswjs/msw/issues/2266
https://github.com/nock/nock/issues/2755

Caution
Before fixing this, we need to write compliance tests for different request modules in accordance to how they follow or don't follow redirects. Note that not all request modules may have redirect following built-in. For example, I believe the http module doesn't do that, thus the existence of designated third-party modules just for that functionality.
Roadmap

Add failing compliance tests for following redirect responses (can start from fetch). A good start: https://github.com/mswjs/interceptors/pull/581
Analyze existing solutions to learn how they implement redirect response following. Use Undici as an example, I believe it has that built-in.
Implement the redirect following.

Looks like the failing tests have been added already: https://github.com/mswjs/interceptors/pull/581. We may need more, but this is a good start.

Added failing compliance tests for fetch here: https://github.com/mswjs/interceptors/pull/627
Confirm that Undici's fetch does follow redirect responses as described in the expected behavior.

Released: v0.35.0 🎉
This has been released in v0.35.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


dj responds to 'gong'

dj gong should be equivalent to dj -1

https://github.com/labzero/hedwig_mopidy/pull/19


Patch doesn't work in spec tests

When trying to patch some code, the following error appears:
 ** (exit) exited in: GenServer.call(Patch.Mock.Supervisor, {:start_child, {{Patch.Mock.Server, :start_link, [EpochProcessingTestRunner, []]}, :temporary, 5000, :worker, [Patch.Mock.Server]}}, :infinity)
         ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
     code: SpecTestGenerator.generate_tests("mainnet", "capella")

There's a minimal reproduction of the error in this branch.
The error seems to indicate that the patch call is being run in compile time instead of at runtime. This might also be related to #288

This was fixed by the spec-test refactor


GH-256 Added Kotlin variant for java code

Added Kotlin variant for java code
https://github.com/spring-projects/spring-modulith/issues/256

That's polished and merged, thanks!


Deploy Frontend UI and API on Different Docker Containers (Docker Compose)

[x] I have created my request on the Product Board before I submitted this issue
[x] I have looked at all the other requests on the Product Board before I submitted this issue

Please describe your feature request:
Would be great if we could have devs provide docker-compose files for deploying the frontend UI and backend API on separate docker containers for use in swarm/stack deployment.

I've transferred this over to our Docker repo as it's not directly related to the Strapi code-base, but implementation using docker

I've been playing around with compose and strapi for the last few days. My docker-compose file so far:
version: '3'
services:
  backend:
    container_name: backend
    build:
      context: ./backend
      dockerfile: Dockerfile
    environment:
      DATABASE_CLIENT: ${DATABASE_CLIENT}
      DATABASE_NAME: ${DATABASE_NAME}
      DATABASE_HOST: ${DATABASE_HOST}
      DATABASE_PORT: ${DATABASE_PORT}
      DATABASE_USERNAME: ${DATABASE_USERNAME}
      DATABASE_PASSWORD: ${DATABASE_PASSWORD}
    ports:
      - 1337:1337
    volumes:
      - ./backend:/app:delegated
      - /app/node_modules
    depends_on:
      - db
    networks:
      - strapi-app-network

  frontend:
    container_name: frontend
    build:
      context: ./frontend
      dockerfile: Dockerfile
    volumes:
      - ./frontend:/app:delegated
      - /app/node_modules
    ports:
      - 3000:3000
    environment:
      NODE_ENV: development
      CHOKIDAR_USEPOLLING: "true"
    tty: true
    stdin_open: true
    depends_on:
      - backend
    networks:
      - strapi-app-network

  db:
    container_name: strapi_db
    image: postgres
    restart: always
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${DATABASE_USERNAME}
      POSTGRES_PASSWORD: ${DATABASE_PASSWORD}
      POSTGRES_DB: ${DATABASE_NAME}
    ports:
      - 5432:5432
    networks:
      - strapi-app-network

  pgadmin4:
    image: dpage/pgadmin4
    container_name: pgadmin4
    environment:
      PGADMIN_DEFAULT_EMAIL: ${PGADMIN_EMAIL}
      PGADMIN_DEFAULT_PASSWORD: ${PGADMIN_PASSWORD}
    ports:
      - "8080:80"
    networks:
      - strapi-app-network

networks:
  strapi-app-network:
    driver: bridge

volumes:
  pgdata:

Some notes:

I have an .env file for the environment variables.
Frontend is merely just create-react-app application.
This is specifically to utilise postgres as db but I've tried with Mongo and that worked as well.
I've added pgadmin for a db GUI.

Hope this helps somebody.


Fix v1.1 (parser, exception, test, UI)

add sort by tag feature

Ui tidied
Test folder added (with a dummy test)

Todo:
parser fix bug, add parsing new command, add exception


[ADD] take U forward

Site URL
https://www.youtube.com/@takeUforward
Description of the above provided site
"Take U Forward" is an excellent YouTube channel specializing in competitive programming and DSA. With its well-curated content, including tutorials, problem-solving techniques, and explanations, it's a valuable resource for both beginners and those looking to enhance their skills.
Category
Youtube
Sub Category
Competitive Programming
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

This resource is already added.


[Bug]: Tapping 'spending balance' on Transfer Funds pages doesn't react as defined in design spec

Describe the bug
Our design spec shows a transition when tapping 'SPENDING BALANCE' on all the Transfer Funds 'PLEASE CONFIRM', 'SPENDING BALANCE' and 'Receiving Capacity' pages. Tapping here does nothing in the app.
Reproduce
See screengrab
Screenshots / Recording
https://github.com/synonymdev/bitkit/assets/74595920/3d3a5fc2-88fc-484d-863d-c922172423bf
https://github.com/synonymdev/bitkit/assets/74595920/2bb9e047-cba2-4646-aca2-d3d73d48cbe0
https://github.com/synonymdev/bitkit/assets/74595920/0abd21fc-64c5-4de2-8afb-e22e44d716c0
Operating system
Android 13 TKQ1.220829.002
Bitkit version
2c5b07726fd35cb796a9566c47d0f6c36fda4ef4
Log output
No response

Tested on v128 e8f5056
Tapping on these now convert between unit type. This isn't how the design defines it but it may be what we want. @limpbrains let's check this and request design change if needed.

Tapping amount should always result in converting to unit type. It may be an error in the Figma.


Stabilize FileSearchProvider API

@roblourens I created this issue in the hope FileSearchProvider is going to get finalized at some point. If yes, maybe add the api-finalization label here.
If I'm out of order creating this, or if I've overlooked another issue dealing with its finalization, please close.

Yeah, it's about time...

@jrieken @roblourens Can we revisit this -- so we can move forward with some kind of search provider functionality. I've been dying for this for a LONG time now and its blocking really cool use-cases in both GitLens and RemoteHub.

@jrieken @roblourens Can we revisit this -- so we can move forward with some kind of search provider functionality. I've been dying for this for a LONG time now and its blocking really cool use-cases in both GitLens and RemoteHub.

And the TextSearchProvider API too please (#59921) 🙏

@jrieken eleven months ago you wrote:

Yeah, it's about time...

Please can this get onto the April 2020 milestone? 🙏 📿

This is not my decision, search is owned by @roblourens, I own the API-process which ensures all API look and feels alike

Please finalize this, this is really needed to fully implement extensions that use the FileSystemProvider, thanks! Do you need input?

Any news about this? I'm creating an extension which isn't much worth without this functionality. I tested it and it works perfectly, but unfortunately I can't submit it to the marketplace... @roblourens

Hi, @roblourens  could you tell us how this problem is developing? thanks and regards.

@roblourens please can we blow the dust off this and get it into Stable? Or else get an understanding of what's holding it up? IMO as more and more FileSystemProvider implementations show up (aka virtual filesystems) the more important it becomes to resolve this.

To echo @gjsjohnmurray, can this please be addressed?
This is blocking adoption of an extension (as we need to rely on a beta version for 'Find Files' functionality), and by extension, blocking adoption of VSCode as the IDE of choice for our application platform.

@roblourens does this also need to be reassigned to @andreamah in order to stand a chance of being finalized?

@andreamah should my extension respect FileSearchOptions.maxResults? Or is the correct behaviour to return all results and let VS Code rank them?
From my testing it seems better to return all results (specifically for Ctrl+P behaviour)

@andreamah do you still own this area? Either way please can we get this API finalized?
Pinging @kieferrm for iteration planning.

@andreamah Do you what still needs to be done here for this to be stabilized? These search APIs have been around for many years and are used by many "1st" party extensions.

It looks like the API was worked on and put aside quite a while ago, so we just need to look back into it and ensure there weren't any big blockers on it (and polishing it). For example, considering whether we allow extensions to also control how the result sorting and filtering works.

It's been almost 5 years since this issue was opened, I'm really hoping to get search working in VSCode SSHFS! @andreamah is there any update on this? Or is there someone else we can re-assign to? Thanks

@andreamah Now that you're reviewing this API, can you add some clarification for how implementers of this API should interpret query.pattern? For example, here's the  very detailed description of WorkspaceSymbolProvider's query argument:

The query-parameter should be interpreted in a relaxed way as the editor will apply its own highlighting and scoring on the results. A good rule of thumb is to match case-insensitive and to simply check that the characters of query appear in their order in a candidate symbol. Don't use prefix, substring, or similar strict matching.

Should this API's query.pattern be interpreted in the same way? If so (or if not) can the API's description say how it should be interpreted?

Good point. I created https://github.com/microsoft/vscode/issues/214175 to track that. Do you think you'd benefit from an alternative method of fuzzy matching and highlighting that is custom-defined? I would assume that something like what we have for WorkspaceSymbolProvider should be sufficient for this API?

Something specific to our file system is that for some folders, the actual name of the document is different than the path.basename of the Uri. For example, we'll have a document in our file system called User.Test.cls, but the Uri in VS Code will be something like isfs://iris:user/User/Test.cls. Even though our provider returns that Uri for a query like User.T, VS Code filters it out. It would be nice if VS Code would "trust" that our provider is returning results that make sense and only rank our results rather than filtering them too. I'm not sure if that's a common problem though so I understand if making an API change to support this isn't reasonable.

I had a conversation with @TylerLeonhardt, who takes care of the quick picker and more UI-facing part of presenting search results, and it seems a little tricky to add logic for this. For a bit of context, the ranking/filtering/highlighting happens on the side of the picker.
The reasons we'd be hesitant about supporting custom highlight/filtering logic are as follows:

Quickpick behavior is outside of the internal search service, so we'd need to change how the quickpick interacts with the file search call. In the simplest implementation, we'd maybe provide manual highlights from the search service to tell the quickpicker that the entry has a valid fuzzy score (and therefore not to filter it out), but that also complicates the picker-search relationship a bit also. This is not even discussing calling back into the extension host to provide filtering/sorting logic, which would be even more complicated (perhaps a different provider overall?)
The quickpick also does some caching that would be difficult to perform with a contributed fuzzy match score.

I hope that sheds some clarity on why we'd likely just keep this the way it is.

Profoundly grateful this is getting attention.  I've had to create my own "quick pick" up until now, which is just not very user-friendly as it's a separate command (and thus probably key binding) from what they expect.
I would utilize custom fuzzy matching if it was available, but can live without it.
As they say, perfection is the enemy of done.

Thanks for the explanation @andreamah, that all makes sense! I can definitely live without any custom fuzzy matching.

Thanks for starting looking to it @andreamah! It would be great to have a proper cloud search integrated into our extension.

Some news: in case you missed it, I'm finalizing this API with some other related APIs. You can see the status (plus a diagram) here. Since they're so intertwined, I felt that it made the most sense to me to address all the APIs as a group.

I cleaned up the search APIs a little bit. There should no longer be any mentions to New. Rather, "new" versions of the APIs should be suffixed by "2".
This also affects:
https://github.com/microsoft/vscode/issues/48674
https://github.com/microsoft/vscode/issues/59924
https://github.com/microsoft/vscode/issues/59921

As for API status, our current state can be illustrated as so:

And we are trying to aim for a shape that looks more like:

Unfortunately, I'll be stepping away from VS Code-related work, so I really hope this can get picked up by someone else soon.

Thanks for the update and all of your work in this area recently @andreamah! Hopefully this can brought over the finish line soon.

You are stepping away @andreamah ?  Oh no... you were our only hope!

Question for anyone picking this up - will this also be supported for Custom Editors?
I noticed that there are concepts of text/line numbers in the diagrams, but it would be amazing if extensions could have custom handling for focus/highlight behaviour in a custom editor.

Welcome @osortega.  We are excited to have you in charge of this!


Add an RFC about application tagging

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/rebase


Add Tracking support for Yanwen

Hi,
Please add tracking support for Yanwen.
Example: https://track.aftership.com/trackings?courier=yanwen&tracking-numbers=AC550032883YN
Thanks

Hi @pedrobotelho, should be working now.
Regards

Working fine!
Thanks


Including node_modules folder in .bazelignore with the intellij plugin breaks intellisense for JS, TS, Angular etc projects

It's recommended to list node_modules in the .bazelignore file, due to making bazel build //… very slow (large number of files) or NPM packages that include BUILD or bzl files causing issues.
Since #1194, the plugin has added all items listed in the .bazelignore file as excluded in IJ, however this breaks intellisense for Javascript, Typescript and such other projects (eg Angular templates) as IJ doesn't index the node_modules folder.
A quick patch to get us working again internally was to ignore lines in the .bazelignore file that contained node_modules, to allow IJ to handle these as library roots (if this approach is acceptable, then I'll open a PR for the change).

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.


[Audio]: S4 League - Come On (Tunnel)

Check if this audio is already added to RetroStudio.

[X] The audio is not already in game.

Is this for the main-menu playlist?

[ ] Add to main-menu playlist.

Is this song from an old Roblox era or a sound effect?

[X] This song is from old Roblox or is a sound effect.

A link to the audio on Roblox
https://www.roblox.com/library/12676956072/New-audio
A link to the audio file to download.
https://drive.google.com/file/d/1wx4kYBE0LspbYSvbW_HVaDO4a2K6VCJT/view?usp=sharing
Notes
This song has been used in old Simon Says, Mega Wave, and The Stalker.  TEACH ME SO I CAN UPLOAD SOME SONGS PLEASE :D

PAST

Lol i just uploaded it without modifications and it worked. The game has also been shut down 2 years ago permanently. Dw if you are that worried then you can rename the audio to something unrelated and do it on a throwaway :D

google drive link is closed


Added inference of set and get

Coverage increased (+3.6%) to 70.976% when pulling de84dd692cb7e3e25fe563d237802aa463be5c6f on set_get into e0366ed828203358c9221f80c0a619292da06e70 on master.


Move repo to bevy_oxr now that the crate is named that way

Github will still redirect from bevy_openxr to bevy_oxr

done!

hooray! the brand identity is forever sealed!


dbeaver/pro#1971 skip parameter numbers used instead names in old PG versions

Please check procedures DDLs with parameter names and without (just data types) in PG and in our Greenplum. You can check Redshift just to avoid many problems again.

Also test procedure execute (from navigator)

verified


Update snippets to use console type for snippets

shell or bash expects the entire snippet to be a bash script, while console highlights only lines prefixed with $ as bash.

Whoa! I had no idea this was a thing!

Me neither until 5 minutes ago! I was reading the readme and thought that there must be a proper way of highlighting those snippets, and finally ended up on https://github.com/github/linguist/blob/7efa7b3380ad0221c499f9ef1ca84c4dfcc0b299/lib/linguist/languages.yml#L5594-L5605 , which works!
BTW the DCO is complaining that my commit (which I authored from the web UI) is not signed..... I guess I need to do a proper one from my laptop and force push.
I must say I don't really understand what signing commits actually buys you though.

@tiziano88 thanks for the PR
yes, you need to do git commit --amend --no-edit --signoff and push again

Done now.


lib64 symlinked to lib causes duplicate collection warnings

In a virtualenv where lib64 is a symlink to lib, I'm encountering repeated "Multiple versions" warnings for Ansible collections:
WARNING  Multiple versions of 'amazon.aws' were found installed, only the first one will be used...

This behavior appears to be related to this PR: https://github.com/ansible/ansible-compat/pull/379
Steps to Reproduce:

Create a virtualenv
Symlink lib64 to lib within the virtualenv
Install Ansible
Run Ansible commands, ansible-lint for example.

Expected Behavior:
Ansible should not report duplicate collection warnings when lib64 is symlinked to lib.
Additional Information:
ls -lah /opt/app-root/ | grep lib
drwxrwxr-x 1 default root 4.0K Aug 26 13:34 lib
lrwxrwxrwx 1 default root    3 Jun  5 12:03 lib64 -> lib

ls -lah /opt/app-root/lib/python3.12/site-packages/ansible_collections/
total 208K
drwxrwxr-x 50 default root 4.0K Aug 26 13:34 .
drwxrwxr-x  1 default root 4.0K Aug 26 13:34 ..
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 amazon
drwxrwxr-x  6 default root 4.0K Aug 26 13:34 ansible
-rw-rw-r--  1 default root  714 Aug 26 13:34 ansible_community.py
-rw-rw-r--  1 default root  200 Aug 26 13:34 ansible_release.py
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 arista
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 awx
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 azure
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 check_point

ls -lah /opt/app-root/lib64/python3.12/site-packages/ansible_collections/
total 208K
drwxrwxr-x 50 default root 4.0K Aug 26 13:34 .
drwxrwxr-x  1 default root 4.0K Aug 26 13:34 ..
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 amazon
drwxrwxr-x  6 default root 4.0K Aug 26 13:34 ansible
-rw-rw-r--  1 default root  714 Aug 26 13:34 ansible_community.py
-rw-rw-r--  1 default root  200 Aug 26 13:34 ansible_release.py
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 arista
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 awx
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 azure
drwxrwxr-x  3 default root 4.0K Aug 26 13:34 check_point

Same here and it's pretty annoying as it is flooding the entire output if ansible-community is installed due to the amount of collections.

Current versions this message no longer appears and in any case, this has nothing to do with venvs. Adding these symlinks to them seems like a recipe for breaking things.

Thanks for just closing the issue... This symlink is added automatically on venvs, nothing was configured manually here just install Ansible in a venv and give it a try. However, as this seems to be the new working mode across the Ansible community, maybe it's time to switch to another config management system.


Deactivate account

Gitea version (or commit ref): 1.1.0
Git version: last version
Operating system: FreeBSD 11
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

There is a bug when I deactivate account emails with all work progress are sending still to email from deactivated account. When account is deactivated it must be deactivated totally, all functions of account should be deactivated when account will be deactivated.
...

If this issue involves the Web Interface, please include a screenshot

@lunny You can assign me to this issue

@daviian only members can be assigned to issue but work freely on it

Currently there are two flags describing the active state of a user.
The is_active and prohibited_login flags. Imo a user is inactive if one of both is set.
Please correct me if I am wrong.

Just found some different between the two flags.
is_active is false, you and your public repos will not be visited by others.
prohibited_login is false, you and your public repos will still be visited by others

But user should not get notifications in both cases I think

@lafriks I agree with that.

resolved by #2384


[move-prover][libra-framework] Pragma export_ensures + AccountLimit specs

This PR adds some specs to AccountLimits (not complete). In the way of doing so, it became apparent that error reporting in the new translation scheme is sometimes inprecise. While the root cause for this is unclear, it appeares once all actual errors are removed from the spec/code, it works.
As a workaround, a new pragma export_ensures is introduced. This can be temporarily used on module level to fall back partly to the old compilation scheme (namely ensures of inlined functions are generated). This seems to fix the error problem, but is off by default because not every test is termination with it.
Motivation
New translation scheme
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Add new verification problems.
Related PRs
NA

@bors-libra r=sblackshear

:pushpin: Commit 786ba48 has been approved by sblackshear

:hourglass: Testing commit 786ba483386ea8be0351f80bebd1d0c9327a7b2f with merge 6f90fa3dc0c369159b8839b8a7407aa1eec41cae...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: sblackshear
Pushing 6f90fa3dc0c369159b8839b8a7407aa1eec41cae to master...


update templates go dependencies

Related: #24

For contributor use:

[x] Targeted PR against main branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (994706f) 81.88% compared to head (4841768) 81.88%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage   81.88%   81.88%
=======================================
  Files           5        5
  Lines         254      254
=======================================
  Hits          208      208
  Misses         46       46

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Contribution by BrodyUnderwood1

Again I'll say, please don't hurt me.

Your pull request have been reviewed and auto closed because it's breaks the code of conduct and the merge policy constructed by the open source policy community. Please review the reason in it's fully form here in this link and/or appeal the claim.

@BennyCarlsson I wasn't paying attention to which PR this was and you got me.


[DNM] server: handle test request in the batch commands

What have you changed? (mandatory)
Handle the batch test message type in order to set up a fuzz test around message batching.
See pingcap/kvproto#384
What are the type of the changes? (mandatory)
Misc (other changes)
How has this PR been tested? (mandatory)
make dev
Does this PR affect documentation (docs) or release note? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

/rebuild

/rebuild

/rebuild

/rebuild

/rebuild

/rebuild

/release

PTAL @benpigchu  , should we close this PR?

This PR is being closed because it is inactive.


Invoking helper function via dot rather than box

The following lines:
fun grandpas [p: Person] : set Person { 	p.(mother+father).father }
pred NoSelfGrandpa { 	no p: Person | p in p.grandpas }
test expect {   nsg : {NoSelfGrandpa} is theorem }
Produce the following error:
  expected: (or/c node? integer?)
  given: #<procedure:...nchmarks/gp-nsg.frg:34:30>
  in: the 1st argument of
      (->
       (or/c node? integer?)
       #:info
       nodeinfo?
       #:op
       symbol?
       node/expr?)
  contract from:
      (function intexpr->expr/maybe)
  blaming: <pkgs>/forge/lang/ast.rkt
   (assuming the contract is correct)
  at: <pkgs>/forge/lang/ast.rkt:129:18```

I don't believe this isn't something we want to support at the moment, although IIRC Alloy permits it. We do need a better error message, and can likely adapt the work we did to add errors for invoking helpers with the wrong number of arguments. Self-assigning.


Update README.md

This would have made my life easier when I was discovering Mineshot. A good thing to have, I think.

Yes, this seems a good idea for those that aren't familiar with Github. I've added it to the bottom below my recent additions of the README.


Problems with identifying the type of a ROOT object

It seems unnecessarily difficult to figure out what an object's type is once read from a ROOT file. I often want to open a ROOT file and then scan across the TKeys to find the one(s) that corresponds to a TTree, for example. But this is what I run into with uproot:
>>> import uproot
>>> file = uproot.open('run0.root')
>>> tree = file.values()[0]
>>> type(tree)
<class 'uproot.rootio.TTree'>
>>> isinstance(tree, uproot.rootio.TTree)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'uproot.rootio' has no attribute 'TTree'

I can do this:
>>> isinstance(tree, uproot.tree.TTreeMethods)
True

but there's no intuitive reason to check TTreeMethods unless I dig into the documentation and eventually find that TTrees are a subclass of it.
It would be slightly better if I could do this:
>>> tree._classname == 'TTree'
False

...but that also fails because I need to check against a byte literal:
>>> tree._classname
b'TTree'
>>> tree._classname == b'TTree'
True

which is also very non-intuitive.
Is there a way to make something like isinstance(tree, uproot.TTree) work, or to make tree._classname == 'TTree' work, or both? Why doesn't uproot.open() have a namedecode option like arrays()?

It's also important to be able to identify the type of an object without reading it (i.e. to decide whether you want to read it). For that, there's classes as an alternative to items.
The Python class ones for each C++ class might already have a type name string (attached to the object itself), though I hadn't thought that it should be user-accessible. Maybe that should be exposed as a classmethod (what should the name be?).
The bytes-to-Unicode conversion and C++-to-Python name conversion are done at the same time—C++ names (with possible [<>:] characters) are raw bytes read from the ROOT file and Python names (pure [a-zA-Z_][a-zA-Z_0-9] and str type) are used as actual class names, converting [<>:] to distinct sequences (by losing _ as an unencoded character). It sounds like you want Unicode names without the [<>:] translation.
Suggest an economic solution as a PR.

I think all I really want is ._classname, but without having to worry about byte literals (and maybe being able to drop the underscore). Is there any reason why the class name shouldn't just always be a normal string? A further frustrating thing is that some classes give a byte literal and some give a string:
>>> import uproot
>>> file = uproot.open('run0.root')
>>> file._classname
b'TDirectory'
>>> file.values()[0]._classname
b'TTree'
>>> file.values()[1]._classname
'TNamed'

This still requires you to read an object before knowing what type it is, which I consider to be a liability.
But anyway, I am suggesting that you make the interface you would like to see as a PR. To get classname as a no-underscore string, add a property that does the encoding to uproot.rootio.ROOTStreamedObject. Don't change the underscored member—it's needed internally, just as a property or method view.

I think this is done. I see a merged PR here. Let me know if I'm wrong.


support pull-cache build flag

Every flag is supported.
https://docs.docker.com/engine/api/v1.25/#operation/ImageBuild


Reject any filename parameters that aren't alphanumeric

Check if the filename has any non-alphanumeric characters to address security concerns from Kathmandu

Just a small nitpick thing, in case you care, you inserted a tab on that empty line...


Allow users to specify a release for a package

Currently, the AppRegistry Server will download the latest release of
a package from quay. This update allows users to specify a specific
release.

@tkashem I have addressed your comments, please let me know if there are any additional changes you'd like to see.


implement the new page format for Parquet 2.0

as defined in
https://github.com/Parquet/parquet-format/pull/64
https://github.com/Parquet/parquet-format/issues/44
PR: https://github.com/apache/incubator-parquet-mr/pull/75
Reporter: Julien Le Dem / @julienledem
Assignee: Julien Le Dem / @julienledem
Note: This issue was originally created as PARQUET-117. Please see the migration documentation for further details.

Tim / @tsdeng:
Issue resolved by pull request 75
https://github.com/apache/incubator-parquet-mr/pull/75


Missing required module 'Minizip'

Bug Report
spm add swift-tooklit
What happened?
import R2Shared
Expected behavior

Readium version: 2.5.0

Development environment
swift version build  5.7
xcode 14

I can't reproduce on Xcode 14.3, Swift 5.8 from a blank test project. Could you try again after clearing the build folder and DerivedData?
rm -rf ~/Library/Developer/Xcode/DerivedData

And what do you see in the resolved Package Dependencies? The Zip 2.1.12 dependency must be present.

I can't reproduce on Xcode 14.3, Swift 5.8 from a blank test project. Could you try again after clearing the build folder and DerivedData?
rm -rf ~/Library/Developer/Xcode/DerivedData

And what do you see in the resolved Package Dependencies? The Zip 2.1.12 dependency must be present.

I run  rm -rf ~/Library/Developer/Xcode/DerivedData
show this error

and then File->package-> update to latest package version
still show same error

I wonder if you give me the different module‘ xcframwwork by complice by   Swift 5.7.2 compiler of xcode14.2  or give me the   xcframwwork that can support all   Swift version compiler  by set  “build libraries for distribution” as YES?

I'm not sure I understand what you mean? When using Swift Package Manager, there are no XCFrameworks involved.

Do you have the same issue when building the Readium Test App? (using make spm in the TestApp folder, see its README).

I'm not sure I understand what you mean? When using Swift Package Manager, there are no XCFrameworks involved.

I used to use carthage to manage  [swift-toolkit],but while uodatin update  xcode to 14.2  ,my project failed to complied by the swift verison peoblem such like this"Module compiled with Swift 5.6.1 cannot be imported by the Swift 5.7 compiler" when  my code need import “R2Shared” or other Class from swift-toolk

I have tried to carthage update  swift-toolkit,but it always been failed!
so I  try to switch the manager way to spm, but it still failed show other  error above pic ,
I am upset。so wonder if u can give me some xcframeworks (version 2.3.0 or 2.4.0 complied by swift 5.72)，so that I can drag them to floder “Build” in folder “Cartahge”

Do you have the same issue when building the Readium Test App? (using make spm in the TestApp folder, see its README).
I used to use carthage to manage [swift-toolkit],but while uodatin update xcode to 14.2 ,my project failed to complied by the swift verison peoblem such like this"Module compiled with Swift 5.6.1 cannot be imported by the Swift 5.7 compiler" when my code need import “R2Shared” or other Class from swift-toolk like this pic

I have tried to carthage update swift-toolkit,but it always been failed!
so I try to switch the manager way to spm, but it still failed show other error above pic ,
I am upset。so wonder if u can give me some xcframeworks (version 2.3.0 or 2.4.0 complied by swift 5.72)，so that I can drag them to floder “Build” in folder “Cartahge

I have tried to carthage update swift-toolkit,but it always been failed!

It's often messy with the Carthage update. You really need to clear all the Carthage caches. For example, from the root of your project:
rm -rf ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/Caches/org.carthage.CarthageKit
rm -rf ~/Library/Caches/carthage
rm -rf Carthage

mkdir -p Carthage/Build/iOS
carthage update --use-xcframeworks --platform iOS

I am upset。so wonder if u can give me some xcframeworks (version 2.3.0 or 2.4.0 complied by swift 5.72)

No, sorry.
Do you have the same SPM issue when building the Readium Test App? (using make spm in the TestApp folder, see its README).

I have tried to carthage update swift-toolkit,but it always been failed!

It's often messy with the Carthage update. You really need to clear all the Carthage caches. For example, from the root of your project:
rm -rf ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/Caches/org.carthage.CarthageKit
rm -rf ~/Library/Caches/carthage
rm -rf Carthage

mkdir -p Carthage/Build/iOS
carthage update --use-xcframeworks --platform iOS

I am upset。so wonder if u can give me some xcframeworks (version 2.3.0 or 2.4.0 complied by swift 5.72)

No, sorry.
Do you have the same SPM issue when building the Readium Test App? (using make spm in the TestApp folder, see its README).

yes I face. the  problem  using  SPM ，fpr example. other file  need import 'R2Shared', show error “No such module ”！！！！！


No worries!
To be clear, the issue there appears to be that your main class is named SpiGUI as is, of course, SpiGUI itself and you’ve imported your main class instead of SpiGUI, so I’d recommend renaming your main class to avoid confusion and importing the wrong file.


Really love the package

Thank you for making this package really love the fluency even though i am not a rust guy it reminds me of scala ADT https://docs.scala-lang.org/scala3/reference/enums/adts.html

Thank you very much!


rgbds-structs doesn't work anymore

The faulty line is this one:
https://github.com/ISSOtm/rgbds-structs/blob/39b4cd67fd0a1c843d011c41cecd09ece23561a9/structs.asm#L306
The error produced leads me to believe that the line is interpreted as a macro instead of as a label. I'm not sure why.
git bisect said:

c75a9539bac624b5e524c74ffa37a065f532585a is the first bad commit

Ok, found the problem.
https://github.com/ISSOtm/rgbds-structs/blob/39b4cd67fd0a1c843d011c41cecd09ece23561a9/structs.asm#L357
When called with the second argument being .player, this yields symbol sizeof_.player. c75a953 restored what I'm assuming is correct behavior, but the error message should be made different, I believe.
What's weird is that the following program compiles and prints $0:
sizeof_.something equ 0

Using a '.' in a symbol name should have been allowed. Sorry about that. I've submitted a PR to fix it.

Coincidentally, I have just proposed #399, which features a different test than your #398. Which one do you think is better?

I think it's good that you're testing more special characters. I did like how I used a new "print" macro to shorten some of the test cases. You can add that if you think it's a good idea. I'll close my PR.

I used printt with a bracket expansion. I think that should work the same?

I meant that I shortened the existing test cases that were using printv followed by printt.

Oh, I'll do that, then.

Done, once CI completes I will merge the PR.

Thanks.

Closed via #399.


Heartbeat dont show Forts in near

Hey,
you know why the Heartbeat dont show more any Forts in my near?
 In the App i see any Pokestop and Arena but with the API i become only a empty object http://pastebin.com/3MsLNwY3

https://github.com/Armax/Pokemon-GO-node-api/issues/200


Refactoring of the existing security-secrets-setup code

Refactor the existing code to accept new changes for pki-init integration and better testable code

Abstract os.Exit() call so it can be tested without losing code coverage
Abstract pki-init option so that it can accept the pki-init options later
Change the local logging client to use global one so that it is more consistent with security-proxy and the logger can be used through out all options in this service
Refactor the execution of -configFile into function so that it can be integrated later with better generation option
Add unit test for main.go for increasing test coverage from the origin
Add unit test for x509.go for increasing test coverage from the origin

Related to: Issue #1635
Signed-off-by: Jim Wang<EMAIL_ADDRESS>

pkiOption_test.go file may need "gofmt -w -l -s" . Other than that it looks good to me.

@tingyuz Tingyu, I ran that, and gofmt tool reports clean to me on that. so we are fine.

@anonymouse64 Ian, any feedback? I am expecting to merge this onto master pretty soon.

@anonymouse64 Ian, any feedback? I am expecting to merge this onto master pretty soon.

I will try to review this today

Thanks for your valuable comments and feedback, @anonymouse64 Ian, I put some replies to your comments and have addressed your PR feedback.  Please check it. Thanks! -Jim

@anonymouse64  Ian, I have rebased and squashed to the single commit. Thanks for great feedbacks. This one commit should be ready to merge onto master.

Hi @mkbhanda Malini, if changes are good for you, please approve it. Thanks and have a nice weekend!
-Jim W.


No 'visible' attribute ?

Trying to make button invisible using Fun.SetTKAttrib(uiName,'Button_39','visible','Hidden'), but I can not get what I want.

Tkinter does not support the visible attribute, but I received your request. I will add a switch to this attribute in the next version.


Gateway monitoring doesn't work for Wireguard after upgrade to 21.1

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
Wireguard gateways have Offline statuses, but they are working fine.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
Relevant log files
There are similiar lines for every gateway:
/system_gateways.php: The WG_1_GW IPv4 gateway address is invalid, skipping.

Additional context
Gateways IPs are set to dynamic. Monitor IP is real gateway ips.
Environment
OPNsense 20.1 (amd64, OpenSSL).

What was the last working version?

20.7.7 or 20.7.8.

I have seen this as well but have started on 21.1.3 so I do not have any tests on older versions.
See screenshots from Gateway setup in OPNsense vs pfSense. (which I am migrating from)
Dynamically created gateways with IP dynamic does not seem to work with gateway IP and monitorIP.
(even if they are available in the IPSec Routed P2 config.)
OPNSense

pfSense

Best regards
Dan Lundqvist
Stockholm, Sweden


Implement post construct method for classes

After constructing a class, if a postConstruct method is present on the class instance, invoke it.

Implemented via 5669230fd75539551d


RemovedInDjango41Warning: 'django_extensions' defines default_app_config

After upgrading to Django 3.2 the warning below appears in terminal:
../usr/local/lib/python3.8/site-packages/django/apps/registry.py:91
  /usr/local/lib/python3.8/site-packages/django/apps/registry.py:91: RemovedInDjango41Warning: 'django_extensions' defines default_app_config = 'django_extensions.apps.DjangoExtensionsConfig'. Django now detects this configuration automatically. You can remove default_app_config.
    app_config = AppConfig.create(entry)

I think it is a common warning raised by some libs after upgrading to Django 3.2.
Django version is 3.2
Django Extersions version is 3.1.2

This is fixed in master.
A new release will be out soon :-)


Error when installing on windows via pnpm

Bug report
Describe the bug
preinstall script failed to run. Looks like opts.url is wrong. Should be https://github.com/supabase/cli/releases/download/v1.1.6/supabase_1.1.6_windows_amd64.tar.gz instead of https://github.com/supabase/cli/releases/download/v1.1.6/supabase.exe_1.1.6_windows_amd64.tar.gz (no ".exe").
Screenshots

System information

OS: Windows
Version of supabase cli: 1.1.6
Version of Node.js: 16.13.0

Thanks for reporting. I've released a new version to fix the download path.


feat: adding feature documentation

Description

Adding section to make features more accessible

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


fmt: fmt.Scan does not expect an io.EOF from a fmt.Scanner

If I want to scan through a string, I can do this:
package main

import (
   "fmt"
   "strings"
)

func main() {
   r := strings.NewReader("west north east")
   for {
      var s string
      _, e := fmt.Fscan(r, &s)
      fmt.Printf("%q %v\n", s, e)
      if e != nil { break }
   }
}

Result:
"west" <nil>
"north" <nil>
"east" <nil>
"" EOF

I recently discovered fmt.Scanner [1], so I thought I would try to implement it. I came up with this:
package main

import (
   "fmt"
   "strings"
)

type comma struct { tok string }

func (c *comma) Scan(s fmt.ScanState, r rune) error {
   tok, err := s.Token(false, func(r rune) bool {
      return r != ','
   })
   if err != nil {
      return err
   }
   c.tok = string(tok)
   if _, _, err := s.ReadRune(); err != nil {
      return err
   }
   return nil
}

func main() {
   r := strings.NewReader("west,north,east")
   for {
      var c comma
      _, e := fmt.Fscan(r, &c)
      fmt.Printf("%q %v\n", c.tok, e)
      if e != nil { break }
   }
}

Result:
"west" <nil>
"north" <nil>
"east" unexpected EOF

So the result is pretty similar, but what bothers me is the unexpected EOF. It seems it is due to this code:
https://github.com/golang/go/blob/3075ffc93e962792ddf43b2a528ef19b1577ffb7/src/fmt/scan.go#L956-L966
It seems like EOF should be valid in this case, or perhaps I dont understand the reasoning for it to be unexpected.

https://golang.org/pkg/fmt#Scanner

Looks like the code was added here https://github.com/golang/go/commit/87fe958a493bd016519e88c8512f09d4cdd4da78

Looks like the code was added here https://github.com/golang/go/commit/87fe958a493bd016519e88c8512f09d4cdd4da78
The only other implementation I found was under math/big, which just ignores EOF for some reason:
https://github.com/golang/go/blob/3075ffc93e962792ddf43b2a528ef19b1577ffb7/src/math/big/natconv.go#L223-L225

Looks like the code was added here https://github.com/golang/go/commit/87fe958a493bd016519e88c8512f09d4cdd4da78
The only other implementation I found was under math/big, which just ignores EOF for some reason:
https://github.com/golang/go/blob/3075ffc93e962792ddf43b2a528ef19b1577ffb7/src/math/big/natconv.go#L223-L225
changed here: https://github.com/golang/go/commit/cfa93ba51fb62252633c62ddc9351d56c18ce018

If I'm reading the documentation right, I don't think fmt.Fscan or fmt.Scanner ever indicate that a scanner should return an io.EOF. I think if you're processing an io.Reader and notice an io.EOF, you're supposed to handle it silently, if the Scan operation is still happening correctly. io.EOF is generally just used as a marker for end-of-input in the io.Reader interface. IIUC you should only propagate an io.EOF if, as the conversion to ErrUnexpectedEOF indicates, it's unexpected.
I don't think there's any bug here though. I suggest asking questions about these APIs on https://groups.google.com/g/golang-nuts first, and then filing an issue if it appears there's a bug or the documentation is incorrect or something. In any case, closing for now.

Alternatively, if you have a suggestion for how you think this should behave differently, that's also a reason to file issue. Though note the Go 1 Compatibility Promise which limits the Go project from changing behavior of APIs if it would break existing programs.

If I'm reading the documentation right

I don't think

I think

generally

IIUC

I don't think

From these quotes, you dont seem very certain about your position, so why would you close the issue?

Duplicate of #17246

If I'm reading the documentation right

I don't think

I think

generally

IIUC

I don't think

From these quotes, you dont seem very certain about your position, so why would you close the issue?

You're welcome to reopen the issue if you disagree (and so are the actual owners of the package), but as @seankhliao points out this is already tracked as #17246, so I don't see a reason to reopen it.


setup.cfg: are linters/tools applicable to having configurations moved in?

I use most of these utilities on my personal projects and have everything in setup.cfg. It would take more input than just me to justify/check on moving to setup.cfg, but it would clean up the root directory significantly.
Applicable?

[ ] docformatter
[ ] pytest
[ ] flake8
[ ] yapf
[ ] isort
[ ] autopep8
[ ] unify

For any of the above, any chance of workflows breaking?

I'd be interested in this change. We have a number of repositories that we'd like to copy our autolinting to, but maintaining many copies of these files would be a headache.
The biggest win for us would be having prospector pick up on some of these files too, so our rules matches our auto-lint and lint steps.
If you have an example of this, we'd definitely me interested in a PR!

@agjohnson
Greetings. I have a lot on my plate at the moment.
As a preliminary, let me show you my setup.cfg I use on my projects (Switched some names around)
[flake8]
inline-quotes = single
max-line-length = 100
max-complexity = 10
exclude = .git,
          __pycache__,
          readthedocs/static,
          my/node_modules

[tool:pytest]
DJANGO_SETTINGS_MODULE=readthedocs.settings.test
addopts=--ignore my/node_modules/ --ignore other/node_modules/

[isort]
combine_as_imports= true
default_section = THIRDPARTY
include_trailing_comma = true
multi_line_output = 3
known_django = django
known_pytest = pytest,py
known_docutils = docutils
known_first_party = readthedocs
sections = FUTURE,STDLIB,PYTEST,DJANGO,DOCUTILS,THIRDPARTY,FIRSTPARTY,LOCALFOLDER
line_length = 79
not_skip = __init__.py

[mypy]
show_column_numbers = True
show_error_context = True
ignore_missing_imports = True
follow_imports = skip
incremental = True
check_untyped_defs = True
warn_unused_ignores = True

The biggest win for us would be having prospector pick up on some of these files too, so our rules matches our auto-lint and lint steps.

It's my first time hearing about it. Careful about pulling it in as a dependency, it's GPLv2.
I will follow up on this ASAP. I have to square away some things on my end first

We have the common repo now, is this issue still relevant?


feat: add eventlistener

TASK: Highlight that this cna be expensive, has additional cost

FYI, enabled branch protection


fix fix wrong string column length after executing ctas from external table

Proposed changes
Issue Number: close #xxx
Problem summary

create table tbl1 as select * from hive.db.tbl;

Error: length of input is too long than schema

add more metric to scanner's profile
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.08 seconds
load time: 439 seconds
storage size:<PHONE_NUMBER>3 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221108173742_clickbench_pr_42268.html

https://github.com/apache/doris/pull/13906
这个pr我也修改了类似一个问题，也是ctas创建的表字段长度有问题

https://github.com/apache/doris/pull/13906

@morningman #13906 这个pr我也修改了类似一个问题，也是ctas创建的表字段长度有问题，代码有交叉的地方

I rebased