Compiling with gfortran

While attempting to compile it with make, I get the following message:
RelEPro/source$ make
gfortran -c -o object/mod.o -O3 -Iobject -Jobject mod.f90
f951: Warning: Nonexistent include directory ‘object’ [-Wmissing-include-dirs]
f951: Warning: Nonexistent include directory ‘object’ [-Wmissing-include-dirs]
mod.f90:290:19:

  290 | END MODULE Constant
      |                   1
Fatal Error: Cannot open module file ‘object/constant.mod0’ for writing at (1): No such file or directory
compilation terminated.
make: *** [Makefile:34: object/mod.o] Error 1

I cloned the repository to try to compile it, however if i am to listen to the warning some parts might need to be in a directory named object? I am running it through gfortran. When making a folder (in source) and naming it object i get a different error:
RelEPro/source$ make
gfortran -c -o object/mod.o -O3 -Iobject -Jobject mod.f90
gfortran -c -o object/int1e.o -O3 -Iobject -Jobject int1e.f90
int1e.f90:937:63:

  937 |         call PowerPAB(.true.,LQSum,ITYPE+LpVp,JTYPE+LpVp,aa,bb,gg,Ra,Rb,tmp,pab)
      |                                                               1
Error: Rank mismatch in argument ‘gg’ at (1) (scalar and rank-1)
int1e.f90:1108:62:

 1108 |       call PowerPAB(.false.,LQSum,ITYPE+LpVp,JTYPE+LpVp,aa,bb,gg,Ra,Rb,tmp,pab)
      |                                                              1
Error: Rank mismatch in argument ‘gg’ at (1) (scalar and rank-1)
make: *** [Makefile:37: object/int1e.o] Error 1

Further comments: I am running this on a Linux mint 21.1 (vera) system, and gfortran ver. 11.4.0.

Dear Christine,
There should be an empty folder "object" in source. Please create it.
Best regards,
Wenli
On Thu, May 16, 2024 at 9:33 PM Christine @.***> wrote:

Further comments: I am running this on a Linux mint 21.1 (vera) system,
and gfortran ver. 11.4.0.
—
Reply to this email directly, view it on GitHub
https://github.com/zorkzou/RelEPro/issues/1#issuecomment-2115264630, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRIFBYXVAYDXRKESL64BTTZCSYUFAVCNFSM6AAAAABH2HBSKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVGI3DINRTGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Dear Wenli
Like i wrote previously, I already did, in the meantime to make it compile I made a few small changes to the int1e.f90 and util.f90, both of which gave me mismatches between what the program expected and what it got, in the first case it gave me a rank mismatch error, where it expected a scalar and got an array of size 1, I modified the code to always take the first entry and expect an array. This was in the subroutine PowerPAB
In the case of the util.f90 the prtcoord subroutine runs a call of the ElemZA routine, this routine complained that it got a CHARACTER size 3 but expected a REAL(kind=8), I messed around with it for a bit trying different options for the placeholder variable zchar, and eventually got it to compile, whether it was as intended i do not know.
I will upload the scripts as i got them to compile into a pull request. You can check if they are still doing what was intended, the values i get from the test do not seem completely off, nor does the output seem off.
Best Regards
Christine

Thank you, Christine!
Since I have classes and graduation defenses in the recent days, I'll check
them this weekend.
Best regards,
Wenli
On Thu, May 23, 2024 at 5:30 AM Christine @.***> wrote:

Dear Wenli
Like i wrote previously, I already did, in the meantime to make it compile
I made a few small changes to the int1e.f90 and util.f90, both of which
gave me mismatches between what the program expected and what it got, in
the first case it gave me a rank mismatch error, where it expected a scalar
and got an array of size 1, I modified the code to always take the first
entry and expect an array. This was in the subroutine PowerPAB
In the case of the util.f90 the prtcoord subroutine runs a call of the
ElemZA routine, this routine complained that it got a CHARACTER size 3 but
expected a REAL(kind=8), I messed around with it for a bit trying different
options for the placeholder variable zchar, and eventually got it to
compile, whether it was as intended i do not know.
I will upload the scripts as i got them to compile into a pull request.
You can check if they are still doing what was intended, the values i get
from the test do not seem completely off, nor does the output seem off.
Best Regards
Christine
—
Reply to this email directly, view it on GitHub
https://github.com/zorkzou/RelEPro/issues/1#issuecomment-2125786285, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRIFBZBIIKS7AMDXMML3ATZDUE6XAVCNFSM6AAAAABH2HBSKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVG44DMMRYGU
.
You are receiving this because you commented.Message ID:
@.***>


Creator "Team" disappears when "Follower Count (About Me)" setting is enabled

What it says on the tin; A creator's team name is removed from their about me when the "Follower Count (About Me)" setting is enabled. This is likely due to both elements having the same parent class and having the same number of children.

As an aside, some people may not want to see the team that a creator's on for one reason or another. As such, this should be added as an option.


BUG

Describe the bug
Donate link goes to a 404
To Reproduce
Steps to reproduce the behavior:

Run the help command
click on 'website pay'

Expected behavior
It goes to some working link
Screenshots

Additional context
The pika!donate links to a different link but also 404s

Please continue in this thread as bug reports and pull requests won't be handled in our GitHub repository anymore


[ERROR]: [line:5] Directive Access-Control-Allow-Headers does not allow multiple values

Consider the following configuration:
server {
  listen 8080
  header {
    Access-Control-Allow-Origin *
    Access-Control-Allow-Headers Authorization, Content-Type, Cache-Control, X-Requested-With
    Access-Control-Allow-Methods GET, POST, PATCH, PUT, DELETE, OPTIONS
  }
}

When we try to use it, the application raises the following error:
[ERROR]: [line:5] Directive `Access-Control-Allow-Headers` does not allow multiple values

but it should allow multiple values separated by comma, since according to Mozilla, it is a valid syntax.

Refs.: https://github.com/silvioprog/see/commit/f0d963cb37f160b6d98e500d82f3a0213ce45b48 and https://github.com/wyhaya/see/pull/11.

Refs.: https://github.com/silvioprog/see/commit/f0d963cb37f160b6d98e500d82f3a0213ce45b48 and https://github.com/wyhaya/see/pull/11.


Maven repository URL incorrect

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server - VSTS or TFS on-premises?

If using TFS on-premises, provide the version:

If using VSTS, provide the account name, team project name, build definition name/build number:

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
[Include task name(s), screenshots and any other relevant details]
Error logs
[Insert error from the logs here]

I am using VSTS task Nexus Artifact Upload and noticed that it was constructing the path to Nexus repository incorrectly
2018-06-13T08:44:25.7199884Z ##[debug]nexusUploadUrl=https://<hostname.com>/nexus/service/local/artifact/maven/content
whereas i wish to upload to content/repositories/snapshots/com
how do i set this in the endpoint setup?  or in the task?

There is not Nexus Artifact Upload task in this repository.  Where did that task come from?  An extension?  You would need to follow up with the author of that task.

Hi Bryan,
I am using Nexus Upload task in my VSTS build definition and would like to deply the war file to Nexus.  We have defined an end point for the same.
I noticed that the VSTS task Nexus Artifact Upload was constructing the path incorrectly.  i.e.
2018-06-13T07:55:38.9878799Z ##[debug]nexusUploadUrl=https:///nexus/service/local/artifact/maven/content
Whereas it should be https:///nexus/content/repositories/snapshots/com/yy/xxxx//<IP_ADDRESS>-SNAPSHOT/-<IP_ADDRESS>-20180608.120507.warhttps://centricitycr.idxasp.com/nexus/content/repositories/snapshots/com/ge/cedi/cedi-ux-webapp/<IP_ADDRESS>-SNAPSHOT/cedi-ux-webapp-<IP_ADDRESS>-20180608.120507.war
In the Nexus Artifact Upload Task
Display Name                                                     Nexus Artifact Upload
Sonatype Nexus service endpoint                 Nexus --> end point defined with the path https:///nexushttps://centricitycr.idxasp.com/nexus, login and pwd
Repository ID                                                     snapshots we tried with content/repositories/snapshots as well still build is not getting the right value in nexusUploadUrl
Group ID                                                              com.yy.
Artifact ID
Artifact version                                                 <IP_ADDRESS>_MAIN-SNAPSHOT
Packaging                                                            war
File                                                                         $(build.sourcesDirectory)\artifact.war
Do you know any other project that has used the VSTS task Nexus Artifact Upload successfully and has constructed the nexusUploadUrl correctly?
Uma Ankolekar
GE HealthCare, Healthcare Technology and Medical Innovation,
Staff Software Build and Release Engineer, Bangalore, KA, IN
M : +91 99208 37273, O : +91 80 4088 3929, WFH : +91 22 2373 5878
Skype<EMAIL_ADDRESS>From: Bryan MacFarlane<EMAIL_ADDRESS>Sent: Wednesday, June 13, 2018 5:53 PM
To: Microsoft/vsts-tasks<EMAIL_ADDRESS>Cc: Ankolekar, Uma (GE Healthcare<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: EXT: Re: [Microsoft/vsts-tasks] Maven repository URL incorrect (#7454)
There is not Nexus Artifact Upload task in this repository. Where did that task come from? An extension? You would need to follow up with the author of that task.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-tasks/issues/7454#issuecomment-396918268, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AmXmrwl8KDpxT_yMHKKUuTQ3Xn0Nlflwks5t8QQcgaJpZM4Ul13v.


AttributeError: 'Namespace' object has no attribute 'func'

I am trying to run demo.py, but I get error:
$ python3 ./demo.py --backend gatttool
Traceback (most recent call last):
  File "./demo.py", line 65, in <module>
    args.func(args, backend)
AttributeError: 'Namespace' object has no attribute 'func'

Hi @adrianmihalko! You need to use the poll command, and append the MAC address of the Bluetooth interface of your sensor, like this: pi@pi3pimatic:~ $ /home/pi/miflora/demo.py --backend gatttool poll C4:7C:8D:61:57:A0

Superb:
Getting data from Mi Flora
FW: 2.7.0
Name: Flower care
Temperature: 19.8
Moisture: 7
Light: 104
Conductivity: 2
Battery: 100
Now I need to modify code to make it work with Domoticz.

Oh, and I just realised that it's you. ✋ Thanks mate! :)

@adrianmihalko not sure about Domoticz but if you have MQTT, consider: https://github.com/ThomDietrich/miflora-mqtt-daemon

@ThomDietrich I already did it, nothing complicated:
https://gist.github.com/adrianmihalko/6e115ad442fa89a2cb4c529a1a15cddc


chore: optimize make help to make it clear to see

Remove duplicated "Usage" Info in make help
Move "MAKE_IN_DOCKER" to Option instead of top messages from make help
Colorize Options and Examples to make them clearer to see.
Fix wrong example since we use image-multiarch not image.multiarch

Now:

Before:

Signed-off-by: Xunzhuo<EMAIL_ADDRESS>

No problem @arkodg ❤, thanks for reviewing this:)


[Extensability Bug] Codeunit FileManagement

The procedures BrowseForFolderDialog and SelectFolderDialog do not have the specification
[Scope('OnPrem')]
and will crash when executing in the Cloud because they use dotnet.
To check alreday at designtime the [Scope('OnPrem')] should be added.

Availability update: We will publish a fix for this issue in the next update for releasee 17.

Update: we've decided to obsolete a few functions, rather than just changing scope. Further updates to the code are to be expected :-)

Update: we've decided to obsolete a few functions, rather than just changing scope. Further updates to the code are to be expected :-)

Availability update: We will publish a fix for this issue in the next update for release 17.

Availability update: We will publish a fix for this issue in the next update for release 17.

Final update: this effort snowballed and has led to the deprecation of many functions. Most changes will hence ship with the upcoming major rather than in a minor.

Final update: this effort snowballed and has led to the deprecation of many functions. Most changes will hence ship with the upcoming major rather than in a minor.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Can't login with Python 2.7

When trying to log in with Python 2.7 (with 3233262 applied), I get urllib2.HTTPError: HTTP Error 400: Bad Request. This doesn't happen when running the same code with 3.4.
from familysearch import FamilySearch

fs = FamilySearch(user_agent, app_key, base='https://sandbox.familysearch.org')
fs.unauthenticated_login(ip)

params = {
    'givenName': 'John',
    'surname': 'Doe',
    'fatherGivenName': 'John',
    'fatherSurname': 'Doe',
}

headers = {
    'Accept': 'application/x-gedcomx-atom+json'
}

q = ' '.join(['%s:%s' % (key, val) for key, val in params.items()])

fs.get(fs.person_search(q=q), headers=headers)

Python 2.7. Ugh.


CaffeOnSpark with mesos ?

Hi
Here, we're trying to use CaffeOnSpark with mesos as the scheduler, rather than yarn. CaffeOnSpark seems to be really focused on Yarn, and we're not sure how to specify the resource allocation when submitting our test job.
As we like to play, here is some additionnal constraints:

we are submitting to the spark mesos dispatcher running on mesosphere DCOS community edition. The dispatcher then creates the driver which then talks to mesos to get the executors
caffeonspark is executed within a docker container from image bhell/caffeonspark_auto which is built on top of mesosphere/spark 1.6.2

1st thing is: spark on mesos is dynamic and will try to gather as much cores and as much executors as possible. We may not know that in advances, so how can we setup the "-device" and the "-clusterSize" parameters ?
2nd thing is: we've tried to constrain the geometry of the subset of machines allowed to one caffeonspark job using the following conf options:

spark.executor.cores    4
spark.cores.max           40
With the following caffeonspark options:
-devices 4 -clusterSize 10

Under some specific context (all docker images being ready to start at job start prior to send the tasks to the executors) the job 0 starts and all machines get a piece of work to do. At the end of the first stage though, I'm encountering the following message:
INFO CaffeOnSpark: total_records_train: 50000
INFO CaffeOnSpark: no_of_records_required_per_partition_train: 25600
Exception in thread "main" java.lang.IllegalStateException: Insufficient training data. Please adjust hyperparameters or increase dataset.
	at com.yahoo.ml.caffe.CaffeOnSpark.trainWithValidation(CaffeOnSpark.scala:261)

I've been able to reproduce this error with less than 10 machines or more than 10, without changing the -clustersize option. I've been through other kind of funny things but I will post more dedicated issues for them.
Anyway, any idea about what could cause this error ?

All right... I found out to have the cifar test running. It was just a problem with the layer description of the dataset (batchsize, image size and channels). I'll be back with more questions...


My Profile Page - Populate & Save [Due 3/5]

Web Path
Home Page -> John Doe -> My Profile

Requirement - Populate

When the page is launched, retrieve user profile from backend using RestAPI, and populate on the page
We don't have user login implemented yet, so please hard code a user ID when you call Rest API.
The User Model in backend doesn't provide all the information you need on web page, such as Linedin URL is missing. We will create another task to fix the Rest API. For now, if any field is missing in the User model, just display some dummy data on web page.
Rest API: getUser: GET /api/user/search/byId/{id}

Requirement - Save

Add Save button.
When Save button is clicked, user profile is saved to database.
Rest API: updatUser: PUT /api/user

Timeline
We implement weekly sprint. This task is given a default of one week. You don't have to finish all requirements in this task, but please submit a Pull Request with whatever code change you have by 3/5. This helps us get the latest development status and plan the next sprint efficiently.

Source Code
\C4SGWeb\app\user\profile\

This issue was moved to Code4SocialGood/c4sg-web#32


Change the conditions for GitHub Workflow

Change the one that specifies both push and pull_request to pull_request only.

I initially misunderstood that pull_request only works when opened. It also works with update, so pull_request only for those that specify both push and pull_request.

Add pull_request to those that are missing.

The binary-release Workflow was missing pull_request, so I add it.

Codecov Report
Patch and project coverage have no change.

Comparison is base (6773bcb) 78.14% compared to head (b47451d) 78.14%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #285   +/-   ##
=======================================
  Coverage   78.14%   78.14%
=======================================
  Files          17       17
  Lines        1725     1725
=======================================
  Hits         1348     1348
  Misses        377      377

Flag
Coverage Δ

unittests
78.14% <ø> (ø)

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

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


$wpsc

Hello,
where does $wpsc variable comes from in wprocket.conf? That sounds like WordPress SuperCache?

Correct. The variable is actually "$wpsc_https" as can be seen at https://github.com/pothi/wordpress-nginx/blob/master/conf.d/common.conf#L33 . Originally, I created the variable for WPSC and since both use the same pattern for SSL powered sites, I used the same variable for WP Rocket too. Nevertheless, it should work as expected, as the variable is defined in conf.d/common.conf file. Thanks.

Hello,
The naming has been changed now as can be seen at https://github.com/pothi/wordpress-nginx/blob/master/conf.d/common.conf#L36 . So, I will close this for now. Please feel free to re-open, if you have any further questions on this.
Thanks.


exp / expires_in should be set to offset

when client.default_max_age is present it should be used as an offset not as a value

Not sure the change on line 106 is correct. expires_in should be a duration, not a date/time.
Ran across the same issue on line 90 with @bauglir today while pairing and we fixed it, without including your conditional logic, which I think is more accurate. I'd accept a PR if you still want to address that.
I'm very sorry this slipped through the cracks until now. We're in a difficult transition these last few months.

Old one.  Re line 90, without the conditional logic with just nowSeconds(req.client.default_max_age) the token will be issued with an immediate exp time when req.client.default_max_age which is fine as long as req.client.default_max_age is never undefined.
It is undefined at the moment for the default "client_name": "Anvil Connect CLI".
Re line 160, not sure now why I thought this should be changed as well, it may be ok as is.  Sorry for leaving this this long.


the pick and ban iu does not work

hi guys i followed these steps

Download latest release
Unzip release to desired install folder
Add http://localhost:9001/frontend?backend=localhost as a browser source in OBS in your ingame scene
Add http://localhost:9001/?backend=ws://localhost:9001/api as a browser source in OBS in your PickBan scene

everything works fine but the last step the pick ban scene when i start a champ select nothing happens  should i do something ?
didn't understand that part plz help

Can you post logs when this issue occurs?

yes but i don't  know  how or where to find the logs

Log-2021-09-08-15-39.log
here is the log sir

Crash-2021-09-08-15-40.log
Crash-2021-09-08-15-43.log
Crash-2021-09-08-15-52.log
yes

also when the champ select ends the app closes and i need to start it again once i'm in the game

Log-2021-09-08-19-17.log
here is the log
and here is the crash logs when i enter champ select nothing happens and the programm crash
Crash-2021-09-08-19-19.log

f


MM-33661 Spurious "join private channel" warning fix

Summary
We are getting unwanted prompts on navigating to already joined private channel by switch between teams as the membership data is not present in the redux store. As a fix we will fallback to server check if membership is false from redux store data.
Ticket Link
https://mattermost.atlassian.net/browse/MM-33661

/cherry-pick cloud

Cherry pick is scheduled.


[release-1.5] Remove log spam from authn

This is an automated cherry-pick of #21282

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.5
7b1ca47c660a52cf9d6381c402f64a0a55a66940
link
/test gencheck_istio_release-1.5

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

/retest


[Bug] SubAck does not return reasonCode，but the subscription is successful

What did I do
mqttx sub but mqtt broker sub ack grantedQosList is empty，mqttx sub successful。
What happened
mqttx sub successful。
Environment

OS: windows 10
MQTTX version, v1.8.2

More detail
mqtt.js sub ack logic seems to be buggy：https://github.com/mqttjs/MQTT.js/blob/main/lib/client.js#L1641
Has been reported to: https://github.com/mqttjs/MQTT.js/issues/1532

Could you please try using an MQTT 5.0 connection to see if a reason code is returned?

A mock MQTT broker subscribes without intentionally returning a Reason code, so the subscription is successful.
模拟的 mqtt broker 订阅，特意没返回 reason code，可以订阅成功。


LinkingSetRelation Explanation

i noticed this in north wind
[LinkingSetRelation(typeof(CustomerRepresentativesRow), "CustomerId", "EmployeeId")]
anything to follwo or read about what it dose and how its doing , i saw its adding reps like in row select

The [LinkingSetRelation(typeof(EntityRow), "field1", "field2")] attribute is used when you are adding multiple selection to a dropdown list. So, when you define the [LookupEditor(typeof(EntityXRow), Multiple = true), ClientSide] attribute on a field to have a dropdown list with multiple selection enabled, you need to place a the LinkingSetRelation attribute on it as well to define the relationship between the field and the selection choices. In the case of the example you're seeing in Northwind, there are multiple selections available for customer representatives, meaning that one customer can have multiple employees assigned to that client. Here, the [LookupEditor(typeof(EmployeeRow), Multiple = true), ClientSide] informs us that the LookupEditor is going to populate with entities from the EmployeeRow and that multiple selection is enabled. The [LinkingSetRelation(typeof(CustomerRepresentativesRow), "CustomerId", "EmployeeId")] attribute informs us that each of the selections of employees is going associate with a specific customer, and those fields are located in the CustomerRepresentativesRow class. When you check the CustomerRepresentativesRow.cs class, you'll see this:
    // ....
    public sealed class CustomerRepresentativesRow : Row, IIdRow
    {
        [DisplayName("Representative Id"), Column("RepresentativeID"), Identity]
        public Int32? RepresentativeId
        {
            get { return Fields.RepresentativeId[this]; }
            set { Fields.RepresentativeId[this] = value; }
        }

        [DisplayName("Customer Id"), Column("CustomerID"), NotNull]
        public Int32? CustomerId
        {
            get { return Fields.CustomerId[this]; }
            set { Fields.CustomerId[this] = value; }
        }

        [DisplayName("Employee Id"), Column("EmployeeID"), NotNull]
        public Int32? EmployeeId
        {
            get { return Fields.EmployeeId[this]; }
            set { Fields.EmployeeId[this] = value; }
        }

    // .....
    }

What's happening behind the scenes is for every employee you select from the dropdown list, when saved Serenity is going to create a new row in the CustomerRepresentatives table in the db, with a unique RepresentativeId, and the CustomerId from the Customer class along with the EmployeeId from the Employee class in their respective fields.
These attributes must be placed on a List field in your EntityRow class, and in your RowFields class you have to define that field as:
public CustomClassField<List<Int32>> FieldName;

I hope this helps clear up some confusion for you.

Thanks a lot @jsbUSMC

thanks that was great


minor issue - install python on window

Hi from Hackhathon Brainthemind Nov 2019 # 2
When following instructions here:
https://mne.tools/stable/install/mne_python.html#installing-python

command lines like "which" may not work in windows but it is fine

python -c 'import mne; mne.sys_info()'
window users should use
python -c "import mne; mne.sys_info()"

Thanks for the info, see #7076


Improve KO chance

this is a WIP I'm going to add all the relevant moves, but yay!

I want to make sure this is what you meant, @Marty-D it does work after testing

also fyi, fixed ko chance of stat dropping moves after this PR :)

This is mergable if you don't see any other issues


Browser support not found

Hi Guys,
Great library. I am wondering if you could tell me where I can find any info on browser support.
Thanks

Looks like this project is abandoned. They have not renewed their domain name with Godaddy and the home page is gone.


npm ERR<EMAIL_ADDRESS>postinstall: "jx installCordovaPlugin.js" npm ERR! Exit status 1

Hello Guys,
Been trying to setup the cordova thali plugin. But I receive this NPM error when firing this command: jx install thali --autoremove "*.gz" --save
My Environment:
OS: Windows 10 x64
Android: Installed Platform 5.1.1
JXCore: v0.3.1 x64
Cordova: 6.0.0
I created an empty app.js under the jxcore folder, after adding android platform under the cordova project. Initialized the package.json and hit: jx install thali --autoremove "*.gz" --save
This does it's business, but @ jx installCordovaPlugin.js fails with status 1
Trying to install jxcore-cordova version: 0.0.8
The cordova info test failed: Error: Current working directory is not a Cordova-based project.
Error: Current working directory is not a Cordova-based project.
Starting to download Thali Cordova plugin from: https://codeload.github.com/thaliproject/Thali_CordovaPlugin/zip/npmv2.1.0
Adding Thali Cordova plugin from: C:\Users\arnab.saha\thaliDontCheckIn\Thali_CordovaPlugin-npmv2.1.0
Failed with - Error: Command failed: Error: Current working directory is not a Cordova-based project.
npm WARN EPACKAGEJSON<EMAIL_ADDRESS>No repository field.
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files (x86)\JXcore\jx.exe" "C:\Users\arnab.saha\.jx\npm\bin\npm-cli.js" "install" "--loglevel" "http" "thali" "--save" "--build-from-source"
npm ERR! node v0.10.40
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: "jx installCordovaPlugin.js"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script '"jx installCordovaPlugin.js"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the thali package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     "jx installCordovaPlugin.js"
npm ERR! You can get their info via:
npm ERR!     npm owner ls thali
Could anyone point me to what is going with my build?
Thanks in advance!
Arnab

Just trying to get around same issue and some tips from my side:

create the package.json file under the jxcore folder
issue the jx install thali --autoremove "*.gz" --save  from your jxcore folder

I did create the package.json under the jxcore folder and issued the jx install thali command from the jxcore folder as well. The reported error persists!

@arniesaha First let me apologize for how painful this is in general. We are trying to get to our first deliverable and so are heads down on that and honestly we haven't made the install process as easy as it should be. In this case the error looks like Cordova doesn't recognize that you are in a Cordova project.  What does it output?

Hey @yaronyg !
Thanks for looking into this. 'cordova info' under the jxcore or the parent path both return:
Collecting Data...
Node version: v0.10.40
Cordova version: 6.0.0
Config.xml file:

ThaliTest

        A sample Apache Cordova application that responds to the deviceready event.

        Apache Cordova Team

Plugins:
cordova-plugin-whitelist
Error retrieving Android platform information: Error: cmd: Command failed with exit code 1 Error output:
'android' is not recognized as an internal or external command,
operable program or batch file.

@arniesaha: One thing that I wanted to ask is in which folder you run the install command to install thali?
Below, I am writing an example set of commands that is probably the simplest setup steps that you need before installation. If possible, please run these into your environment and paste the full output (as a gist, for example) and I'll try to help figuring out what the issue is:
$ cd /tmp
$ cordova create SomeApp
Creating a new cordova project.
$ mkdir SomeApp/www/jxcore
$ cd SomeApp/www/jxcore/
$ jx npm install thali
... lots of output ...

@vjrantal Thanks! I made an error and was not running the install command under cordovaApp/www/jxcore folder, instead under cordovaApp/jxcore !!
Its installed correctly now. Is there a sample app of the thali implementation I could check? Since this is a plugin, there's only the device ready screen that launches in the build. Should this be something I should be looking at https://github.com/thaliproject/postcardapp?
Thanks,
Arnab

@arniesaha: Good that the issue got solved!
The postcardapp is an example app that shows thali usage.


Adds a github workflow for twoops tracker

Description
Adds a GitHub workflow for building twoops tracker image, pushing it to dockerhub and deploying it to dokku
Type of change

[x] New feature (non-breaking change which adds functionality)

Screenshots
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

I think we've been forgetting to run lint/format/tests before merging to main.

I think we can add as a different workflow instead of inside the deployment workflow right?

Just to confirm, pants publish pushes the built image to docker hub directly, yes?

Yes

I take it we'll still extract common things like application name to env

Yes. Will do.

I think we can add as a different workflow instead of inside the deployment workflow right?

The goal is to fail the build/deploy if there are linting/testing errors. If one workflow failing can stop another from proceeding then all good @esirK.

@thepsalmist  I think this was one of the first attempt to add CI

no @kilemensi


✨ Structured results for Binary-Artifacts

Structured results for Binary-Artifacts

@laurentsimon can we wait on this PR until we have clarity on the RuleIDs design and MVP ?


[crane] should we target VS2012?

Currently if you run crane init proj and try to build it in VS2012 nuget restore doesn't work. Should we target VS2012 in a future release?

For now we are not going to target VS2012 specifically.
If you run crane init SallyFx and open it in VS2012 it won't compile. This is because the nuget restore behaviour changes between VS2012 and VS2013. We rely on the automatic restore behaviour in VS2013. However if you run .\build.ps1 first in powershell it will compile as that runs the nuget restore for you.

I will add this to the http://docs.cranebuild.com/en/latest/faq/


Axios 0.18.0 Vulnerabilties

The Node-RED Watson nodes which depend on IBM-Watson, and in turn node-sdk-core are no-longer deploying in IBM Cloud due to a vulnerability in Axios 0.18.0.
The current release of node-sdk-core has a dependancy to Axios at 0.18.0
The dependancy in node-sdk-core needs to be bumped to remove this vulnerability.

Update: This appears to be a problem associated with the rebuild / restage of existing cloud foundry applications. New IBM Cloud applications deploy successfully.
Leading me to think that there may be an incompatibility with Axios and older cloud foundry build packs and / or node.js versions.

@chughts I'm hoping that #96 resolves this issue. @MasterOdin left a comment about why you may be seeing the behavior you mentioned above. Let me know if you are able to resolve the deployment and we can close this issue.

@dpopp07 That explanation makes sense. It's something to be aware of for me. After your update,  and hopefully IBM-Watson's, I can make a dependency change which node-red deployments can force by bumping the node-red dependancy on the Watson nodes.
In the meantime I can ask them to force the axis bump by adding in a direct dependancy to node-sdk-core at 2.4.1

I'll try a direct dependency on
"ibm-cloud-sdk-core":"2.4.1"

Making a direct dependency on 2.4.1 probably will not fix the axios issue if there's a package-lock.json file involved as it will not bump the versions of transient dependencies (so you'll be using ibm-cloud-sdk-core 2.4.1 with axios 0.18.0. A 2.4.2 release (which I guess #97 is warning about?) needs to be cut that specifies axios ^0.18.1 and then doing a direct dependency on ibm-cloud-sdk-core would work for existing projects.


[Program]: Write a F# program to find sum of n natural numbers using formula

Description
Write a F# program to find sum of n natural numbers using formula
formula: n(n+1)/2
Input  : 5
Output : 15

How to contribute

Save the solution in program/program/find-sum-of-n-natural-numbers-using-formula/FindSumOfNNaturalNumbersUsingFormula.fs file

!assign

@harshraj8843 I've completed this issue and just wanted to raise a MR. Is there any branching strategy that you guys follow because I couldn't find that in docs?


Added array to json conversion for sqlite

In reference to #30128, this PR allows SQLite databases to cast arrays as JSON when calling the update method directly on a model.
This allows a more consistent result when testing between mysql and sqlite, especially when using the $casts array on a model.

@staudenmeir I hope this resolves the issue!


Add multiple roles to users

Checks

[X] I have checked for existing issues.

Motivation
Currently user defined via values.yaml can only be granted a single role. If more roles are assigned (via UI/API), sync process will revoke them as soon as it runs again.
I would like to be able to specify multiple roles in array:
users:
  name: some_user
  role: [User, SpecialRoleA, SpecialRoleB]

role attribute should support both single value and an array, for backwards compatibility.
Implementation
No response
Are you willing & able to help?

[X] I am able to submit a PR!
[X] I can help test the feature!

@kmehkeri I like the idea, if you have time to work on it, let's target the 8.7.0 release.
To implement this, you will need to update the templates/sync/_helpers/sync_users.tpl file.


K-9 Crashes went starting a new email beginning with da, like dave.

Strange behavior: Using person's last name to call up email address works as expected.
Submitted report with logs to Google Play Store.
Expected behavior
Bring up enail address from contact list.
Actual behavior
K-9 crashes
Steps to reproduce

Initiate email starting with da or Da.

Environment
K-9 Mail version:5.403
Android version:5.1.1
Account type (IMAP, POP3, WebDAV/Exchange):IMAP

Also crashes on send to: ad.
If you enter the person's last name, k-9 will load the correct email address and work ok.
Exampe: Send to: Dave Smith crashes after entering Da, but Don Smith works ok.
Also,  typing Smith, a label will come up with Dave Smith. Tap on Dave Smith and everything works fine.

Update: Works ok if you type ave Smith for Dave Smith.
Same behavior on the cc: line.

I can confirm the general behaviour. However, the address book entries leading to a crash differ (no problems with the entry "Dave Test", for example). The problem seems to occur only when the 'problematic string' is at the beginning of an address book entry (i.e. 'ti...' crashes, but 'ina' will bring up 'tina...' and work). So far, the crash has always occurred with the second letter typed in.
Thank you for your efforts, m
K9Mail 5.403, Android 6.01, FairphoneOpen

If you go to contact phone list first to the name Dave, then tap email, up will come K-9 mail without a problem.
However, if you are already in K-9 mail and type "Da" for Dave, K-9 will crash on the "a", but if you type "ave", up will come "Dave" from the contact list and you can tap on it without a problem.
I haven't seen this in other letter combinations. I only noticed it because I added "Dave" to my contact list. Before there was no one on the list whose name started with "Da".
On August 18, 2018 7:50:24 AM PDT, mhgithb<EMAIL_ADDRESS>wrote:

I can confirm the general behaviour. However, the address book entries
leading to a crash differ (no problems with the entry "Dave Test", for
example). The problem seems to occur only when the 'problematic string'
is at the beginning of an address book entry (i.e. 'ti...' crashes, but
'ina' will bring up 'tina...' and work). So far, the crash has always
occurred with the second letter typed in.
Thank you for your efforts, m
K9Mail 5.403, Android 6.01, FairphoneOpen
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/k9mail/k-9/issues/3540#issuecomment-414063132

--
Deo Vindice
PGP : AA32DFCC (2023/07/14)

Is this still an issue in the latest K-9 Mail version?
If so, please provide a debug log. See https://github.com/k9mail/k-9/wiki/LoggingErrors

No. They fixed it in one of the last updates.
On March 7, 2019 7:20:14 PM PST, cketti<EMAIL_ADDRESS>wrote:

Is this still an issue in the latest K-9 Mail version?
If so, please provide a debug log. See
https://github.com/k9mail/k-9/wiki/LoggingErrors
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/k9mail/k-9/issues/3540#issuecomment-470790344

--
Deo Vindice
PGP : AA33DFCC (2023/07/14)


Need To customise tree

Need tree expand in both side in example only expand tree in left side i need right side also...

i just try to making this tree graph for only trying for new design.

i hope help this in you application.


Amuse quantities don't use 'future' imported division

When division is imported from __future__, this is not used by quantities.
This may result in unexpected behaviour when using divisions.
E.g.:
from __future__ import division, print_function
from amuse.units import units
print(5 / 4)
# prints 1.25
print(5 // 4)
# prints 1
a = 5 | units.m
b = 4 | units.m
print(a / b)
# expected: 1.25
# actual result: 1

NB: using Python 2.7, I didn't test this in Python3 (when the new division is standard).

One option to fix this would be to just add from __future__ import division to quantities.py. This would force the new behaviour of the division operator.
A better method would be to determine which division method is used (i.e. if the user script uses the from __future__ import), but I'm not sure how to do that yet.

Well, importing future(s) is not something we want here (also it would possibly break existing codes).
I fixed the implementation for truediv and also added floordiv,could you check if this fixes it?

Confirmed, issue is fixed.


Motherboard is burned after running the code

i executed the procedure on dell tower 8 core, 16 G ram and the motherboard is burned. i am not sure the hardware had a problem or the code. any idea?

Unlikely that it's the code per se. The standard settings do intensively use all cores expect one, but heavy CPU usage shouldn't burn your motherboard. So it more seems like a hardware issue.

I was running on ubuntu 12. So ubuntu 12 might not have protection for over heating. I am not sure. I am waiting for the hardware diagnoses from out IT dept. However i ran the code on Google cloud now on Debian and seems fine so far. Another mistake, i think i ran double process. As i thought at some level that the first process died. So it could be ubuntu issue, or dou le process or hardware.

I will update this thread for reference after i get a solid feedback

Problem solved, it was power cable problem. the processing script overheat the cable and it was damage internally. although the power supply led was on. it was not enough to power the server. very odd but true.


Performance on Pascal VOC

Hi! Thanks for your great job!
I am curious about the results of your proposed P2BNet on VOC2007. Could you please show me the performance? Thanks a lot!

The performance on VOC07 is 60.4 AP50. The code and config will be avaliable soon.


Incorrect instruction step

Hi All,
I went through the instruction and I have spotted one incorrect information:
In the section where we are supposed to allow the VMs to retrieve the certificate, step two tells us to open "Access policies" to set this up, this is incorrect. The actual place to do so is "Access configuration". Could you please amend this and update the instruction?
Beside that, great job! Keep it going!
Regards,
Tomasz Mankin

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

ID: 5eae1653-5b40-f2fc-a4e8-0f5020bdceaf
Version Independent ID: 81517c64-b80f-45f7-cb91-7cf3001113ce
Content: Deploy a Service Fabric managed cluster using the Azure portal - Azure Service Fabric
Content Source: articles/service-fabric/quickstart-managed-cluster-portal.md
Service: service-fabric
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@Duch003
Thanks for your feedback! We will investigate and update as appropriate.


using filemanager in api

hi
I'm using Laravel mainly as a backend service. the project's frontend is written in angular 2 and communicates through API. I wanna use the file manager in ckeditor in my frontend,(admin panel mainly). but I'm stuck on what to do for it. the default web and auth middlewares will fire the error 'route[login]' not found(which is logical. I haven't used them). if I use only the web middleware, the error 'trying to get property of non-object' comes.
For our own use, we have a custom middleware called custom_api, and when I use that, I get an error "Class custom_api does not exist".
so basically, how can I totally disable the authentication, and write my own?

For the error you got, maybe you should check if you set up route middlewares in app/Http/Kernel.php. And by the way, the api of file manager contains html. It is also our milestone in v2.0 to leave only json data in the api.

i could ALMOST get it to work. for people reading it, something that worked for me was to disable default routes, copy all the routes in my own route file and do not use any middleware on the routes. then implement your own auth system.

Done in v2.0.0-alpha, ItemController now returns json response.


build: migrate to tsup and tsx

General improvements and simplification of the setup.

Replaces custom build workflow based on rollup with tsup.
Replaces tsm loader with tsx.
Simplifies npm scripts and
Fixes a "bug" when package-lock.json wouldn't get updated along with the package.json during release workflow.

Closes #3

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
25

Relevant Lines:
151

💛  - Coveralls


Deduplicate OptixDeviceContextOptions

My initial implementation had it prefixed with _55 because I wasn't sure if this structure had the same layout in previous versions too, however, now I can see that it should be compatible with previous versions at least down to ABI version 36. Let's remove unnecessary copies by moving this struct and related callback type to shared nvoptix_types.h and remove version prefixes from all of them. We could reintroduce a prefix if we ever encounter a version that is incompatible with the current one.

Yeah. It is not that much that changes between them. There is a change between 41 -> 47 on a couple of functions.. other than that it is just added functions, so it should be doable to squash this a bit :)
I downloaded some OptiX demo's from nVidia github, and was able to compile with 4 different ABI's to verify (hence, i found my misstake in 47 which led me to force-push hehe).

I have been fiddling with this a bit today, but my very limited programming skillz really comes up short.
I see it would have been fairly easy if it had only been adding new functions to the tables like from eg. ABI_36 -> ABI_41, but the case is that in ABI_47 there are 2 existing functions in 36 and 41 that got updated. This kinda makes it hard (for me) to figure out how i can build the tables...
It is probably not that hard, but am i right in that i cannot really RENAME the const struct functioname to something it should not be, cos when whatever app calls this, it would fail? As i understand it now, the table is being built with the correct function names, and #define ASSIGN_FUNCPTR(f) *(void**)(&table->f) = (void*)&f ## _47 is just some sort of macro to link this to the different ABI functions...  Like  ASSIGN_FUNCPTR(optixGetErrorName); will point to optixGetErrorName_47 (for the ABI_47 table) internally only, but if i changed it to ASSIGN_FUNCPTR(optixGetErrorName_47); the app would fail the call because optixGetErrorName would not exist if i did that? Right? :smile:
Making the struct's in the header seemed doable, and i found it could perhaps work neatly enough when using -fms-extensions compile option, cos then i could create the struct like this (small example):
typedef struct OptixFunctionTable
{
    const char *(*optixGetErrorName)(OptixResult result);
} OptixFunctionTable;

typedef struct Optix_36
{
    OptixResult (*optixDenoiserCreate)(OptixDeviceContext context, const void *options, OptixDenoiser *returnHandle);
} Optix_36;

typedef struct OptixFunctionTable_36
{
    struct OptixFunctionTable;
    struct Optix_36;
} OptixFunctionTable_36;

then the OptixFunctionTable_36 would contain both the OptixFunctionTable AND the Optix_36 table (atleast it seems to work like that from a small helloworld sample i played around with).
Dunno if it is worth doing that? Would maybe trunkate it a bit instead of spreading it in 5 headers... Just not sure how to deduplicate the rest.

But maybe we should instead split nvoptix.c into per ABI version implementations, each in its own file, so that _VERSION suffixes aren't necessary because they exist in separate translation units.

I think perhaps that would be nice, given the way the ABI's are built, and after fiddling with this a bit (as a non-programmer) the way they (NVIDIA) adds new functions, and also changes some or removes some (as we see from 41 -> 47) makes this more troublesome to trunkate than i initially thought.
Ill see if i can figure out how that would work... but i do like that idea > trunkating 😄

Started working on this: https://github.com/SveSop/wine-nvoptix/commit/3f6ab4acde566c38d1b89f11e915d58552871c0e
Compiles, but ofc does not work. But its a start..
When calling optixQueryFunctionTable_36 from main, the values are all garbled.. I guess i have messed up someplace with the "static" stuff and whatnot.
Not sure if i am at the right track with this @Saancreed ? :smile:

My guess: does the nvoptix.c compilation unit know about the exact signature of optixQueryFunctionTable_X? We should probably forward–declare them either at the top of nvoptix.c with the exact same parameters or (better) inside each of nvoptix_X.h. Lack of this should generate compiler warnings though, not sure why it doesn't unless winegcc / ninja silences them by default.

I have a couple of simple optix tests i compiled, and if you want to you can check it out perhaps..
If you do this patch
diff --git a/src/nvoptix_36.c b/src/nvoptix_36.c
index af10af9..7304bff 100644
--- a/src/nvoptix_36.c
+++ b/src/nvoptix_36.c
@@ -304,6 +304,8 @@ OptixResult __cdecl optixQueryFunctionTable_36(
         void* functionTable,
         size_t sizeOfTable)
 {
+    TRACE("(%u, %p, %p, %p, %zu)\n", numOptions, optionKeys, optionValues, functionTable, sizeOfTable);
+
     if (sizeOfTable != sizeof(OptixFunctionTable_36)) return OPTIX_ERROR_FUNCTION_TABLE_SIZE_MISMATCH;

     OptixResult result = poptixQueryFunctionTable(36, numOptions, optionKeys, optionValues, &optixFunctionTable_36, sizeOfTable);

And then run the intro_driver_36.exe from the tests, it seem a bit weird...
011c:trace:nvoptix:optixQueryFunctionTable (36, 0, (nil), (nil), 0x470218, 296)
011c:trace:nvoptix:optixQueryFunctionTable_36 (4653592, (nil), 0x128, 0xfffffffffffffff5,<PHONE_NUMBER>)
ERROR: initOptiX() initOptiXFunctionTable() failed: 7802
ERROR: Application failed to initialize successfully.

The values supposed to be passed from main -> nvoptix_36.c source is bonkers as far as i can understand?
Test.zip
PS. If you get it working, there is something strange with the 510.54 driver and OptiX ABI 36 and 41 it seems.. i am pretty sure this used to work with an older driver, but it gets lots of errors now. 47/55 works without errors tho. (The demo files i mean).

I think I fixed it, please take a look at linked PR.

Nice! Ill check it out when i get home from work.
Not sure what would be the reason ABI 36/41 shows this weird errors. I am fairly sure it worked fine with the 495 driver series which was what was used when we started. DAZ 4.16 used ABI 36 too, and it was not a spew of errors when we started dabbling with this. DAZ 4.20 now uses ABI 47, so that works, but it could explain why some have experienced issues with nvoptix and DAZ if they still use 4.16 and have upgraded to the 510 driver series.
Ill test the fixes from your PR, and once the "split" branch is merged i might downgrade my driver to 495 just for testing.. no point in debugging wine-nvoptix if it is a driver bug with the 510 branch.

Might be worth sending an email to NV at their linux-bugs address mentioning issues with older ABI versions and current drivers if the same samples work with older ones.

It seems to happen for my windows box too, so ill look into the sample compiles. It is some CMake stuff that generate a Visual Studio project.. and some tweaks to use different ABI's. It could very very well be something there aswell, cos i am starting to doubt myself now :fearful:

Rightfully so.. It seems some of the generated files (ptx) was not as common as i thought. When i initially did that build i guess i just built 1 by 1 SDK, and tested, but i rebuilt now keeping the subfolders inside their own subfolders, and the demo's are working... so no driver bug only human bug :stuck_out_tongue_closed_eyes:


[M] External link icon is not accessible

Assistive tech does not have access to the "external link" icon next to external links in the nav bar (such as the "Changelog" link in the PyData Theme docs)
TODO:

[ ] This content is added via CSS pseudo-element but where and how exactly? Is the method used in the source code elsewhere? Answer these questions in order to see if there are other such icons, or other such content, in the PyData theme.

I can find reference to the external icon in 3 places:
// src/pydata_sphinx_theme/assets/styles/variables/_icons.scss

  --pst-icon-external-link: "\f35d"; // fa-solid fa-up-right-from-square

//src/pydata_sphinx_theme/assets/styles/sections/_header.scss
.nav-link {
  ...
  &.nav-external::after {

    content: var(--pst-icon-external-link);

// src/pydata_sphinx_theme/assets/styles/sections/_sidebar-primary.scss
nav.bd-links {
  li > a {
    &.reference.external {
      &::after {
        ...
        content: var(--pst-icon-external-link);

I'm not sure we have control over  the .externals, I believe it is created upstream in sphinx. nav-external we should have control over.
I'm not sure how we want to handle that, even if we could modify the html. I've see a few suggestions:

a span that is hidden and has "(external link)"
use alt/desc on the link.

There are a few notes that "external" by itself is not a problem by itself, what is more  a problem for screen-readers is when clicking a link open a new windows by default (target="_blank").
I'm not sure I can judge the best way to move forward.

The original msg confused me a bit. What is not accessible by assistive tech? the icon itself or the link to which the icon should redirect the user to?

This content is added via CSS pseudo-element but where and how exactly? Is the method used in the source code elsewhere? Answer these questions in order to see if there are other such icons, or other such content, in the PyData theme.

The way this is phrased makes it look like we are talking about the icon itself rather than the (underlying) external link, so it would be best to clarify.


assets label incorrectly applying to pull-requests

Expected behavior
For the assets label to not be applied to the affected pull-request.
Observed/actual behavior
Please refer to affected pull-request: axieum/minecord#2
Steps/models to reproduce
Create a pull-request that does not modify any file under the **/assets/** file glob.
Version
n/a
Agreements

[X] I am running the latest version of the mod.
[X] My version of Minecraft is supported.
[X] I have searched for and ensured there isn't already an open issue regarding this.

Other
No response

I'll take a look at fixing this - I'm considering using the same labeler action elsewhere, so getting some experience with it would be good.


Show full repository url

What is version of KubeSphere DevOps has the issue?
v3.3.0-alpha.1
How did you install the Kubernetes? Or what is the Kubernetes distribution?
No response
What happened?
When using github to import the repository, the repository address is not displayed completely.

/priority medium
/assign @kubesphere/sig-devops
Relevant log output
No response
Additional information
No response

This issue was fixed by https://github.com/kubesphere/console/pull/3122

This issue was fixed in v3.3.0-alpha.1


for sharding encrypt rule

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Pull Request Test Coverage Report for Build 6916

91 of 119 (76.47%)  changed or added relevant lines in 29 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 70.763%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/filler/impl/dml/InsertFiller.java
1
2
50.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/column/ColumnSegment.java
2
3
66.67%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/expr/CommonExpressionSegment.java
6
7
85.71%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/expr/EqualsValueExpressionSegment.java
0
1
0.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/expr/FunctionExpressionSegment.java
0
1
0.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/expr/PropertyExpressionSegment.java
0
1
0.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/sql/segment/expr/SubquerySegment.java
0
1
0.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/parser/context/condition/Condition.java
7
8
87.5%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/parser/token/EncryptColumnToken.java
0
1
0.0%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/parser/token/SQLToken.java
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/src/main/java/org/apache/shardingsphere/core/parsing/antlr/filler/impl/OrConditionFiller.java
1
78.0%

Totals

Change from base Build 6915:
-0.03%

Covered Lines:
10865

Relevant Lines:
15354

💛  - Coveralls


[azservicebus] Authorization using Shared Access Signature Token

Feature Request
Hi, with other SDKs, e.g. python or C#, I'm able to connect to an Azure Service Bus using a connection string that contains a shared access signature token for authorization.
if I try to do the same with the azservicebus package, I run into the following error
client, err := azservicebus.NewClientFromConnectionString("Endpoint=sb://example.servicebus.windows.net/;SharedAccessSignature=SharedAccessSignature sr=http%3A%2F%2Fexample.servicebus.windows.net%2F&sig=XXXXXXXXXXX&se=1639528312&skn=RootManageSharedAccessKey", nil)
if err != nil {
	panic(err)
}

// panic: key "SharedAccessKeyName" must not be empty
// or alternatively if Name additionally provided: panic: key "SharedAccessKey" must not be empty

Am I missing something here, or is there maybe an alternative way to get SAS token based auth working with this SDK? If not, is this feature already on the roadmap? I stumbled upon #16104, but wasn't sure if it's related.

In the other referenced thread, this was commented on as being planned still.
Is there a workaround today that we could implement while we wait for this?  For instance, how hard would it be to add the CBS claims to another AMQP provider like Qpid Proton?  Has anyone looked at this?  I have only seen this done in the AMQPlite (C#) project.

I managed!
Just create a new "credential provider" local package. Where you put the code that renews your connection string.
`package sasCredentials
import (
"context"
"strconv"
"time"
"github.com/Azure/azure-sdk-for-go/sdk/azcore"
"github.com/Azure/azure-sdk-for-go/sdk/azcore/policy"

)
type SasCredential struct {
cred azcore.TokenCredential
}
func NewSasCredential() (*SasCredential, error) {
return &SasCredential{}, nil
}
func (c *SasCredential) GetToken(ctx context.Context, opts policy.TokenRequestOptions) (token *azcore.AccessToken, err error) {
response, err := Some http call to receive your SAS string?
parsed, err := ParseSig(res.SasToken)
if err != nil {
	return nil, err
}

// Parse the expiration time
expire, err := strconv.ParseInt(parsed.Se, 10, 64)
if err != nil {
return nil, err
}
tm := time.Unix(expire, 0)
newToken := &azcore.AccessToken{
Token:     res.SasToken, // Thats the actual full SAS Token string
ExpiresOn: tm,
}
return newToken, nil
}
var _ azcore.TokenCredential = (*SasCredential)(nil)
`
Then in the main file. you initialize the client this way:
credential, err := sasCredentials.NewSasCredential()
client, err := azservicebus.NewClient("XXXXXXXXXXXXXXX.servicebus.windows.net", credential, nil)
Voila.


Embedding a Starscream dependent .xcframework into my own .xcframework with Cocoapod

Question

I am implementing a custom .xcframework "C". Within my custom framework, there's another .xcframework within which is "Starscream". I have specified the dependencies within my .podspec as well as the vendor frameworks. Now anytime I try to push to trunk, I get an error about Starscream having a deployment target set to 8 [I have tried to bump the target within the pods - didn't work]. Attached image.

How can I go about this
Environment:

Starscream Version [e.g. 4.0.4]
Xcode version [e.g. 14.3]

Hi, do you solve the issue?


adding storage capacity support

Issue #, if available:
#135
Description of changes:
Adding support for storage capacity and checks for proper increments
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 66a480dd709764938186c36144ceb3e9c47b36b6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 5a50259ef13e0442f9c4710eab010caf494a0e2f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 1346914bce06ce4dd0145eb3b0075cf6fab439d2
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


where to download bitnet model ?

Describe the bug
Where to download bitnet model? Which is shown in this example code:
bitnet.load_model("../model_checkpoint.pth")  # Download model

To Reproduce
Execute example. No model loaded.
Expected behavior
Link to download suitable model

Is there a plan to release the weights? Or is this a bug in loading them?

Is there a plan to release the weights? Or is this a bug in loading them?

I can't find where to download weights for the example and so I can't run example so I've created this bug.
As I understand only models trained for BitNet can be used and not any model.

@xeb @dibu28 we had the weights but the google drive link and the model was just bad. we must train the new verison

@xeb @dibu28 we had the weights but the google drive link and the model was just bad. we must train the new verison

Thank you! I will be waiting for the weights to test your new model.


python37Packages.pyee: 7.0.4 -> 8.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.pyee is: "A port of Node.js's EventEmitter to python"
meta.homepage for python37Packages.pyee is: "https://github.com/jfhbrook/pyee"
meta.changelog for python37Packages.pyee is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 8.1.0 with grep in /nix/store/nw0y7m6118qxqk1znvksrp571hcrq5q3-python3.7-pyee-8.1.0

directory tree listing: https://gist.github.com/fbe92b7324eb337bee277f4e31b97893

du listing: https://gist.github.com/103c765715e32e4a8ddd6f3df3f53e01

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

20 total rebuild path(s)

5 package rebuild(s)

5 x86_64-linux rebuild(s)
5 i686-linux rebuild(s)
5 x86_64-darwin rebuild(s)
5 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python37Packages.pyee
python37Packages.pyppeteer
python38Packages.pyee
python38Packages.pyppeteer
urlwatch

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nw0y7m6118qxqk1znvksrp571hcrq5q3-python3.7-pyee-8.1.0
ls -la /nix/store/nw0y7m6118qxqk1znvksrp571hcrq5q3-python3.7-pyee-8.1.0/bin

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

3 packages failed to build:

python37Packages.pyppeteer
python38Packages.pyppeteer
urlwatch

2 packages built:

python37Packages.pyee
python38Packages.pyee

Maintainer pings
cc @kmein for testing.

Can someone rebase this branch on master to fix the eval error?

@GrahamcOfBorg eval

@ofborg eval

Already on master


Remove stale script

This script should have been removed to avoid confusion.
It's not used anywhere.
Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ayj
Assign the PR to them by writing /assign @ayj in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

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

/assign @douglas-reid

/approve

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

Needs approval from an approver in each of these files:

pilot/OWNERS [geeknoid]

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

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ac91c8f8dd95517d288d2cb69e04bacacbf44c81
link
/test istio-unit-tests

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


leap: add new exercise; travis: test each exercise

You would think these are two unrelated things, but it seems to me that neither can stand on its own: I wouldn't want to add an exercise without assuring that it is in fact good, and making Travis test all exercises will have no effect unless there is some exercise to test.
So these together will get the track's inaugural exercise created and tested on Travis. Now that this work is done, hopefully less work to add future exercises.

In the absence of any other reviewers, I am forced to merge my own PR.


Enhance product generator

Summary
This is a list of improvements and ideas for the product generator. The can be picked up as smaller MR's and/or stories.
Needed to support current products

[x] Allow for int enums to specify the key (instead of _1, _2, etc.)
[ ] updating data structures and/or files might benefit from a parser (instead of grepping/replacing stuff)
[x] create product descriptions for all our products
[ ] support union types (as used for example in the dcc product block)
[ ] sometimes lists in product blocks have different min/max-items depending on lifecycle (for example ListOfIpBgpSaps versus ListOfIpBgpSapsProvisioning). Figure out out good way to specify this in the config file
[x] allow to compress lifecycles in product blocks if they are the same (for example nsistp)
[ ] Some products don't have a full modify, but several workflows to partially update the subscription. For example CoreLink

Additional easy to implement features

[ ] add option to ignore asserts (so the unit tests run out-of-the-box instead of TDD)
[ ] provide optional title in yaml file if the formatting is simple, for example "{name}". Or make this more generic
by supporting properties
[ ] add remove option to complete erase a product

Advanced features

[ ] extend tool to generate the config file from the db (for existing products)
[ ] show diff between actual product and product generated from config
[ ] create the graphs/documentation from the config file

Note: a parser is relatively straightforward to implement using the built-in ast package

Various improvements through the following pull requests have been made.
More generator improvements (https://github.com/workfloworchestrator/orchestrator-core/pull/400)

use correct lifecycle in new product block defination when pointing to existing product blocks
import existing product blocks in all its lifecycle states
add additional new line to lazy workflows and subscription model registry when appending to existing _init.py
remove send_confirmation_email step from default terminate product template
import SubscriptionInstanceList when type is equal to list
update CLI docs on the product block YAML format
remove superfluous space from optional macro
comment out SURF specific load_organisation_info() step in validate template
correct use of required attribute in product blocks and create product templates
update generator CLI docs on use of required field

Even more generator improvements (https://github.com/workfloworchestrator/orchestrator-core/pull/439)

remove python 3.9 Optional support
add default values to inactive product block domain model
add default values to create workflow input form
do not fail dryrun when workflows/init.py does not exist yet
refactor create_summary_form into a shared create and modify summary form
refactor and cleanup create and modify workflows
refactor and cleanup terminate workflow
remove send email support, now handled by additional steps
make summary forms optional again
add todo to fix validator generation
calculate product types module dynamically
use generic Python exceptions

enum support in generator for both fixed inputs and resource types (https://github.com/workfloworchestrator/orchestrator-core/pull/468)
make generator orchestrator-2.0 compatible (https://github.com/workfloworchestrator/orchestrator-core/pull/481)

use Annotated list instead of Sequence
cleaner constrained int definition
simplify imports in templates
change OrganisationId into CustumerId
add namespaced import support to create and modify workflow
add constrained int support to create and modify workflow
add enum support to create and modify workflow
ReadOnlyField is an Annotated Literal instead of a Field
remove superfluous MigrationSummary imports
refactor validations into AfterValidator() and @model_validator()
keep trailing newlines in Jinja template to conform to Python coding standards
change class Config into ConfigDict
consolidate template rendering code
only add fields with supported types to input form
use ruff to format and fix generate python code
correct default values in product blocks and input forms
add unit test for all generated code
more detailed documentation
add script to create cli generate fixture

small generator fixes (https://github.com/workfloworchestrator/orchestrator-core/pull/501)

rename config.create_summary_forms into config.summary_forms
add note on lazy workflow creation to documentation
only ruff files with .py suffix
create missing translation file
pretty print translation json
fix creation of workflows dunder init
remove redundant label_ prefix from Label input fields
refactor ProductSummary from class to TypeAlias
assume that the first of the defined blocks is the root product block
non-optional input fields are also non optional for construct model step in create workflow
remove unused one() import from generator helpers
update generator unit test fixtures

Other improvements should be reassessed.


Don't want middleware to create new ticket

Hey
I much appreciate your work but i stuck some where.
I'm implementing it as for client so don't want to that ticket should be raised by only logged-in user.
Help me ASAP

I am sorry, but it doesn't support guests, only logged in users can create tickets.

any solution @thekordy ?

@sandeep-mishra123 sounds like you're wanting to modify the codebase, you may wish to clone and make changes for your own version


Ability to send attributes to topics

I needed to also pass attribute information to PubSub topics, so I wanted to open a PR for this reason.

@NeoScript This would be extremely helpful for me, as being able to send attributes is required for my use-case. Thanks!


Allow to configure storage size

Closes #368.
FYI @henrjk I believe you had to make this change manually, right?
Tasks:

[x] Updated design documents in docs/design directory or not applicable
[x] Updated user-facing documentation in docs directory or not applicable
[x] Ran tests (e.g. make test) or not applicable
[x] Updated changelog or not applicable

Test failure should be unrelated. The E2E test is flaky, it sometimes times out :(

Yes indeed I had this done manually while using v0.1.1.
During upgrade to v0.2.0  the helm rollout failed because luckily helm install will not decrease pvc size.
So this should now be better for sure.


Add the no-wait argument to ovs-vsctl commands for hw-offload

The "no-wait" argument is needed for ovs-vsctl commands because there is a chance for ovs-vsctl to timeout.
Adding "--no-wait" to the command line would make it such that ovs-vsctl doesn't wait for ovs-vswitchd to update "cur_cfg"
An example of this timeout is shown here:
ovs-vsctl[3265]: ovs|00001|vsctl|INFO|Called as /bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true systemd[1]: ovs-vswitchd.service: start-pre operation timed out. Terminating. ovs-vsctl[3265]: 2023-02-22T22:00:20Z|00002|fatal_signal|WARN|terminating with signal 15 (Terminated) ovs-vsctl[3265]: ovs|00002|fatal_signal|WARN|terminating with signal 15 (Terminated) systemd[1]: ovs-vswitchd.service: Failed with result 'timeout'. systemd[1]: Failed to start Open vSwitch Forwarding Unit.

/cc @bn222
/cc @zshi-redhat
/cc @adrianchiris

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 25.767%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
1949

Relevant Lines:
7564

💛  - Coveralls

This is a great find. Thanks for figuring this one out. I like the idea of adding no-wait we avoid a timeout from systemd. However, I'm wondering what other implications this has. Afaict, not waiting to finish setting hwol to true isn't going to have an impact elsewhere.
/lgtm

@wizhaoredhat  Is this the fix to the ovs-configuration service failure you found on openshift 4.13?

@wizhaoredhat Is this the fix to the ovs-configuration service failure you found on openshift 4.13?

Yes it was in OCP 4.12.


Full LODE implementation

This finishes the LODE code and adds the gradients w.r.t. positions.
Still TODO before we can merge to master:

[x] Add k=0/l=0 term for p=0 / p>3
[ ] port high p=1 level pyLODE tests (Madelung constants, Random Coulomb Structures, Super cells)
[ ] tests for p=0 against SOAP implementation
[ ] add regression tests for compute_k0_contributions, compute_density_fourrier, project_k_to_nlm, compute_structure_factors
[ ] enable parallelism (likely over systems like for the SOAP spherical expansion)
[x] fix all TODO in the code
[ ] Docs

Thanks for this intensive work @Luthaf. I will go through the code and do some initial review. I can also do these check resulting and adding the highlevel tests.

@kvhuguenin and @Luthaf should we rename the former spherical-expansion to soap-spherical-expansion also in the docs? Even though SOAP is not really the expansion it might make things more clear.

@kvhuguenin and @Luthaf should we rename the former spherical-expansion to soap-spherical-expansion also in the docs? Even though SOAP is not really the expansion it might make things more clear.

you mean to distinguish from the lode version? I would rather call the lode version spherical-expansion-kspace

@kvhuguenin and @Luthaf should we rename the former spherical-expansion to soap-spherical-expansion also in the docs? Even though SOAP is not really the expansion it might make things more clear.

you mean to distinguish from the lode version? I would rather call the lode version spherical-expansion-kspace

fine for me. And to be consistent:spherical-expansion-rspace?

I started to rename everything to soap-spherical-expansion and lode-spherical-expansion, and I have a slight preference for these, but we can change it.

fine for me. And to be consistent: spherical-expansion-rspace?

spherical-expansion-kspace is nice and understandable, but spherical-expansion-rspace less so (kspace something used in a lot of places already, rspace or real-space not as much).
We could also do spherical-expansion-soap and spherical-expansion-kspace.

I also like spherical-expansion-kspace.
However, this might now feel like nitpicking but everything we do is 'SOAP': One calculator is computing features in real and the other in k-space. New users might be confused and come up with an idea: spherical-expansion-soap is the most high level representation and includes the k-space and real-space or what ever. Therefore, I highly encourage a name scheme making clear that one is k-space and the other one is real space.
We also might build SOAP power spectra combining real and kspace features, which should also be clear...

I am working on the Madelung Tests right now. For these tests and all tests we have to scale the center atom weight to 0. Currently this option does not exist. For GTO's there is an analytical expression which we will implement.

After a discussion with @PicoCentauri we agreed to merge this in the LODE branch, and start other PR for the remaining TODO items.

Merge this when you are ready @Luthaf and lode into main as well.


Set minimumExpectedPekkoVersion to 1.0.0

Resolves https://github.com/apache/incubator-pekko-http/issues/327#issuecomment-1755949430

@pjfanning So whether or not to use the snapshot is derived by the "pekko.http.build.pekko.version" which you can see here  https://github.com/apache/incubator-pekko-http/blob/7f1441ee25d864a9cbc441eba92199598e26ea01/project/PekkoDependency.scala#L45
and currently this is being set for nightlies, i.e.
https://github.com/apache/incubator-pekko-http/blob/57dcb5dcc64b4c269d83a01909a7a39dcd32bf71/.github/workflows/nightly.yml#L44-L48
You can verify this by looking at https://github.com/apache/incubator-pekko-http/actions/runs/6463888406/job/17547697024, i.e.
[info] Building Pekko HTTP 1.1.0-M0+10-4eccd171+20231010-0214-SNAPSHOT against Pekko 1.1.0-M0+101-1b1f5722-SNAPSHOT on Scala 2.12.18


Fixed CMake lookup of boost Python for Py 3.4, 3.5 and 3.6

Motivation
Building Python wheels is failing in the updated Docker image for Python 3.4, 3.5 and 3.6. Fixing it here by explicitly including the library defined variables.

run java8 tests

run java8 tests


Mention that channel should be a string and correct permission docs

Bot only needs SEND_MESSAGES permission if it's the author of the message, and it is.

Github really likes to add newlines at the end of the file... Now this will probably conflict with #3.


Fix CSAI-2103 run SonarQube only once

In order to run SonarQube only once:

Create a separate job
Move mobtest and SonarQube

Tested here: https://github.com/MOV-AI/movai_DELETE_ME_DAVID/pull/1

Hi @duartecoelhomovai and @AlexFernandes-MOVAI I believe this was used to SonaQube only. Can you confirm that so @diasdm can change it in the sections that Sonarqube is not running anymore?
    steps:
    - name: Checkout
      uses: actions/checkout@v2
      with:
        # Disabling shallow clone is recommended for improving relevancy of reporting
        fetch-depth: 0
        submodules: recursive

The checkout is needed in all jobs that will interact with the repository. The "fetch-depth: 0", was what we added for sonarqube.

@duartecoelhomovai the shallow clone is now done everywhere, with exception of where the Sonar is run.

Re-tested after changes:

https://github.com/MOV-AI/movai_DELETE_ME_DAVID/pull/3
https://github.com/MOV-AI/movai_DELETE_ME_DAVID/pull/4

Deploy: https://github.com/MOV-AI/movai_DELETE_ME_DAVID/actions/runs/2421953206

I agree, possibly even with a few more?

Documentation?
Static analysis
Build
Unit test
Publish
Sonar

But currently, the way it is setup, there is no dependency on the Test step from the Build step. Although we know in the future it will be need. Should we add it now?

I agree, possibly even with a few more?

Documentation?
Static analysis
Build
Unit test
Publish
Sonar

But currently, the way it is setup, there is no dependency on the Test step from the Build step. Although we know in the future it will be need. Should we add it now?

Yes,  I think so (example here: https://github.com/MOV-AI/.github/blob/c7476aaefa80ca82761d876d350483835f051470/.github/workflows/multi-py-deb-workflow.yml#L116)
why do you put Sonar on last step ?

Sorry, it makes more sense to come before Publish (but actually should not run when Publishing):

Documentation?
Static analysis
Build
Unit test
Sonar
Publish

I'll add the dependency on Build and the ${{ inputs.release == 'false' }} so it is not executed when publishing. Agree?

Re-tested https://github.com/MOV-AI/movai_DELETE_ME_DAVID/pull/7

And with publish: https://github.com/MOV-AI/movai_DELETE_ME_DAVID/actions/runs/2595547555

@diasdm you will only want this for ros? Maybe also have it in npm, py and all the other templates

AFAIK the ros-workflow was the only where the multiple runs of Sonar was creating issues. Eventually (hopefully soon) we'll need to do these changes in all workflows. But I was indeed forgetting about it, so I'll merge this PR and re-uniformize the workflows in a different one in the next few days. Do you agree?


fix(gha): restore contents permissions

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area CI

What this PR does / why we need it:
oops / 2
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
Once this PR has been reviewed and has the lgtm label, please assign rohith-raju for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

LGTM label has been added.  Git tree hash: 6bb02bb0be2da1dfacf5287c607de8e464a22b9d

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

Needs approval from an approver in each of these files:

OWNERS [Rohith-Raju]

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


Can I use asymmetrical images as input?

For instance, an image of 500x3000 pixels.

@Tylersuard,
If you are pre-processing the images to resize all of them to fixed size then yes, you can use asymmetrical images as inputs while training.
For more information, you can check this example from Tensorflow, which uses images of different sizes for training.

Thank you for your help!


OCM dependencies should always be on the same version in all projects

User Story: The expressive title of your user story goes here
Description:
There are 2 types of dependencies:

External dependencies
Internal/Cross dependencies from other projects in the OCM github org

Proposal: To help to keep all the projects use the same version, we need a github action/pipeline to:

parse all DIRECT dependencies in the require() section of the go.mod
detect dependencies which have multiple versions defined in all projects
It wont fail/block anything, it is informative

Why?

All ocm internal projects should be compatible with the latest versions of the each other, it ensures that e2e-tests are detecting the problems correctly
It should not be the responsibility of the person starting a new ticket to do this job before they can start working on their new ticket. The person introducing the incompatibilities has a better knowledge of the changes and should make it part of their existing ticket to fix it or create a separate ticket to fix it. This notification will also help the reviewer understand the outcome of the changes.
We will have security scans soon for each individual project, they will scan all dependencies and we should not have repeated/extra vulnerabilities due to different versions of external dependencies

Examples of this problem:
1.
https://github.com/open-component-model/replication-controller/blob/main/go.mod#L7
https://github.com/open-component-model/ocm-e2e-framework/blob/main/go.mod#L140
https://github.com/open-component-model/unpacker-controller/blob/main/go.mod#L89
https://github.com/open-component-model/ocm-controllers-sdk/blob/main/go.mod#L10
https://github.com/open-component-model/mpas-product-controller/blob/main/go.mod#L9
https://github.com/open-component-model/ocm-controller/blob/main/go.mod#L7
https://github.com/open-component-model/remote-controller/blob/main/go.mod#L88
https://github.com/open-component-model/git-controller/blob/main/go.mod#L7

https://github.com/open-component-model/mpas-product-controller/blob/main/go.mod#L29
https://github.com/open-component-model/remote-controller/blob/main/go.mod#L11
https://github.com/open-component-model/replication-controller/blob/main/go.mod#L19
https://github.com/open-component-model/git-controller/blob/main/go.mod#L22
https://github.com/open-component-model/ocm-e2e-framework/blob/main/go.mod#L283
https://github.com/open-component-model/unpacker-controller/blob/main/go.mod#L15
Epic link:

#448

Relevant comments from #448 regarding this issue:
Skarlso commented 2 weeks ago •
👋
Let me try and clarify how dependencies in Go projects work. I highly recommend reading the go modules reference guide in order to fully understand how dependencies are calculated and resolved.
To that end, let me try to clear up some confusion.
Common Dependency Handling: There are a few dependencies which are present in all projects, and we refer to specific versions of a dependency. This created 2 problems:
These are replace statements that are necessary because of OCM, not because of the controllers. OCM deals with a couple of dependencies that require a specific version. These are intrinsic dependencies, and we pin these versions to avoid compiler errors. No one has to revert to anything. These versions already exist on your machine. And you can't use a different one even if you wanted because the project simply wouldn't compile.
This issue is not unique to us. This is a Go based "problem". Even big projects like Kubernetes have replace statements.
Using different dependency versions for different projects. Ideally, they all should be on the same version to get the same functionality and to avoid detecting failing e2e, etc. tests. Eg: ocm-controller versions
Unpacker and remote controller are old. We simply didn't have the time to update them yet.
Have a github actions gather common dependencies from all projects and prevent merging if common dependencies are not on the same/latest version. The versions which should be used should be compiled by the action and stored in a file so that someone who start developing knows the new version they can use locally while developing rather than waiting for the PR to fail and correct before merge
I think that's not necessary. Especially since the mod files will force the versions, they need over the components they dependent upon. If there is a different version requested, they will simply not compile.
ocm cli dependency: The ocm-cli is referred by all projects and apart from the above problem of using different versions, when ever there are changes(refactoring/features) in the CLI, the failures in other projects should be identified and fixed/reported. The failure should not be a landmine for someone starting a new ticket and the failure-fix should be part of the already identified work done on the cli
This problem exists in massive projects that depend on a single source. Just look at CAPA, CAPZ, CAPI projects that depend on Kubernetes. They each have cycles where they update their respective Kubernetes version. And get this. Sometimes they support different versions. ;)
We are a small team. It takes me a full day to update all controllers to the latest OCM version because, usually, it introduces some change that breaks existing behaviour. If it doesn't, it's still at least half a day of work updating the dependencies, approving the PRs, and releasing a new version. This is nothing new, though. And it would be nice to automate it. But the reality is that it's simply not feasible considering the usual changes OCM introduces.
Maybe once we separate the CLI from the Library, it will be an easier task to do so.

Moving back to the backlog as currently working on the IAS adoption ticket, will pick it up after that


Setting worker default volume size to 100GB

I think as a default, 20GB is way too low. For example, GKE uses 100GB.

Oh someone just made a PR to change the official CFN templates:
https://github.com/awslabs/amazon-eks-ami/pull/20
They also state that 20 is too low but then set the default to 20?? 🤷♂

LGTM - This will be released with the next major rev (within the week) since without action (explicitly defining disk size where the 20 GB default was previously used), it would blow away and recreate the worker groups.

it would blow away and recreate the worker groups
I think it will just replace the LC on the ASG? Nothing more?

Good call and apologies on the alarmism. I'm more accustomed to the rolling release setup where entire ASGs are replaced on a change to the underlying LC but those facilities aren't in place here so all remains quiet.


IsarError when calling .clear() or .clearSync() - Write operations require an explicit transaction.

Steps to Reproduce
Originally ran into this problem in our application, so I created a new Flutter project to recreate this issue.
I used the example on pub dev, using the Post class as the object being stored.

Create an Isar instance
Write some objects into the instance.
Call isar.clear() or isar.clearSync()

Both functions throw the same error:
Unhandled Exception: IsarError: Write operations require an explicit transaction.
Code sample
Isar object & initState:
  Isar? isar;

  @override
  void initState() {
    super.initState();
    _initIsar();
  }

Isar Setup:
  Future<void> _initIsar() async {
    final dir = await getApplicationSupportDirectory();

    isar = await Isar.open(
      [PostSchema],
      directory: dir.path,
    );

    for (int i = 0; i < 50; i++) {
      await isar?.writeTxn(() async {
        final post = Post();
        post..title = "Post $i";
        post..date = DateTime.now();
        await isar?.posts.put(post);
      });
    }
  }

Function Call:
onPressed: () {
    isar?.clearSync();
},

I also just have a widget to display the amount of objects in the collection:
Text('Post Count: ${isar?.posts.countSync()}'),

Version

Platform: Tested on iOS - both a simulator and a physical iPhone 12 Pro Max, as well as a iPhone 13 Pro Max
Flutter version: 3.3.0
Isar version: Tested both 2.4.0 that we use in our application, as well as 3.0.0-dev.13
Isar Generator version: Tested both 2.4.0 that we use in our application, as well as 3.0.0-dev.13

Screenshot
Here is the stack trace:

Since clear and clearSync write to the database they need to be wrapped in a write transaction 🙂

Thank you for the quick response.
I just tested this in the sample app and everything is working as expected.
I will mark this issue as closed.


Bump RuboCop version?

Hi,
https://github.com/codeclimate/codeclimate-rubocop/blob/dba3b70ec3042e8ccfb7848e3dfe709b2754380b/Gemfile#L9
It appears that the RuboCop version here is very old. It'd be nice if we could bump the version?
I'd be happy to send a PR if so? 😄
CC: @filipesperandio :)

You can use channel if you want to have a specific version. The newest is currently rubocop-0-89, but I'm not sure if it is available on CodeClimate. rubocop-0-88 is available for sure.

@utkarsh2102: What @krzysiek1507 said.
We may eventually update the master branch (stable channel) to something more recent, till we do, we suggest using the channels for specific versions. rubocop-0-89  was already released.


Add new service to handle route53 DNS records.

Towards: https://github.com/giantswarm/roadmap/issues/1546
This PR adds a new route53 service that's still unused. It will be used in following PRs to create route53 records to be used as custom cloudfront domains.
Checklist

[x] Update changelog in CHANGELOG.md.

also AFAIK in vintage there is nothing that would delete this record when cluster is deleted as the CF will only deleted records created by the CF, so it will block hosted zone deletion
in CAPA we have this sorted as we delete all records with dns-operator-aws

also AFAIK in vintage there is nothing that would delete this record when cluster is deleted as the CF will only deleted records created by the CF, so it will block hosted zone deletion
in CAPA we have this sorted as we delete all records with dns-operator-aws

This is a good point, I will test it specifically


BIGTOP-4086: When using 'brp java repeat jars' in Flink, the version c…

…annot be obtained correctly

Description of PR
How was this patch tested?
For code changes:

[√ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[ √] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

@iwasakims @guyuqi
please help review the code, thanks.

+1, tested on CentOS 7 and Rocky 8 as follows. Good catch @LiJie20190102!
$ curl -sL https://github.com/apache/bigtop/pull/1249.diff | git apply
$ ./gradlew flink-clean flink-pkg repo -Dbuildwithdeps=true
$ cd provisioner/docker
$ ./docker-hadoop.sh -d -dcp -C config_centos-7.yaml -G -L -k hdfs,flink -s flink -c 1

...

BUILD SUCCESSFUL in 2m 5s
28 actionable tasks: 6 executed, 22 up-to-date
Stopped 1 worker daemon(s).
+ rm -rf buildSrc/build/test-results/binary
+ rm -rf /bigtop-home/.gradle
$ ./docker-hadoop.sh -dcp -e 1 flink -v
Version: 1.16.2, Commit ID: 472eeca

Merged into master and branch-3.2.


[Event Request] Codeunit 427 ICInboxOutboxMgt

Could you please add an event  OnMoveOutboxTransToHandledOutboxOnBeforeICOutboxPurchaseLineDelete  in Codeunit 427 (ICInboxOutboxMgt) in function MoveOutboxTransToHandledOutbox   before ICOutboxJnlLine.Delete()  ?  There is an similar event  OnMoveOutboxTransToHandledOutboxOnBeforeICOutboxSalesLineDelete  for sales line.
Thanks.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


feat: remove ds-reset

resolves #2751

I see we have some visual differences, have you reviewed them and are they intended changes or unintended sideeffect?

I have seen the visual tests, but the contents of the class have been added to the Combobox input, the other components already had what it needed


DNS Reverse Lookup

http://linux.die.net/man/3/gethostbyaddr

Implementation updated. Please review before closing issue.

Gonna go ahead and close this issue


⚠ Bofrost.de has degraded performance

In 89ebf1a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 978 ms

Resolved: Bofrost.de performance has improved in 9196a09 after 4 hours, 12 minutes.


Part C Step 2

https://github.com/IBM/banking-digitalization-using-hybrid-cloud-with-mainframes#2-make-a-cognitive-application-using-watson-services
Should this also be in the "EXTRA" part? It seems that it's also a "do it yourself" step like the IoT part.

@AnthonyAmanse ,
No. At this step 2 ("Make a cognitive application using Watson Services"), developers know how to basically use Bluemix because of they successfully did the step 1 "Start with Node.js on Bluemix", which may be difficult for beginners. Indeed in this step 1, I gave directions but I ask developers to read the Bluemix documentation(for getting/pushing/deploying the Hello Worlds project). Learning how to read the Bluemix documentation is essential and necessary, that is why in step 2, I continue illustrating sub-steps but I want to focus on how to reach the right information in the Bluemix documentation . Using Watson services is easy. Learn how to read the documentation may be challenging. The objective of this documentation training for developers is to let them go on Bluemix after this journey, like described in the "Extra" Part, where in developers are totally independent :).