text:
Chain / group multiple DATA/METHODS/CONSTANTS declarations

I just checked the available rules, but could not find a rule that groups consecutive declarations into one.
For example, when I have this code:
DATA one   type string.
DATA two   type string.
DATA three type string.

I would want the cleaner to group these consecutive declarations into one single declaration, like so:
DATA: one   type string,
      two   type string,
      three type string

This should work for:

DATA
CLASS-DATA
CONSTANTS
METHODS
CLASS-METHODS

Most important for my use case would be DATA and METHODS, the others would just be nice to have.
Is it possible to add such a rule?

Might I ask why you would want to do this? It is actually the opposite of what is recommended in the clean ABAP style guide, which abap-cleaner is meant to follow.

Hi robinbaeurle,
yes, I remember a similar request in the Inner-Source phase of ABAP cleaner. It would certainly be technically possible, but as Josh pointed out, is it desirable (explicitly going against the style guide)? Maybe let's set this to "discussion wanted"!
Kind regards,
Jörg-Michael
P.S.: In our team, people did like these declaration chains, because PrettyPrinter was able to align TYPEs inside them. But that's not an argument with ABAP cleaner anymore :-)

P.S.: In our team, people did like these declaration chains, because PrettyPrinter was able to align TYPEs inside them. But that's not an argument with ABAP cleaner anymore :-)

Hmm, but doesn't indenting unchained statements go against the style guide as well? Specifically "Don't align type clauses". Indenting unchained statements is also introducing a lot of whitespace changes whenever a variable is changed. The way I see it, the default profile's setting for "Action for consecutive non-chains" in rule "Align declarations" goes against the style guide.
PS: I'm not sure where my personal stance on this topic is 😅

authors: ConjuringCoffee jelliottp jmgrassau robinbaeurle

repo: SAP/abap-cleaner


text:
Refac prog

Note for reviewer: Review single commits rather then the entire diff.

Tested with INTF and example.

@huber-nicolas can you do manuell testing? The unit-tests are green and I could generate a folder for INTF with example and readme,  but I guess there is more to test. We don't want to have regressions in this report.

source: gharchive/pull-request

repo: SAP/abap-file-formats-tools

license: MIT

license_type: permissive

license_source: github-api


text:
opening the terms and conditions page redirects user to first step of checkout

Environment Details

Spartacus: dev branch
Browser: chrome

Steps to Reproduce
Add items to cart
Proceed to checkout
On last step of checkout, click on "Terms and Conditions"
Observed Results
The terms and conditions page is loaded. However, there's no way to go back to checkout, except by pressing the browser's back button, which then redirects the user to the first step of checkout.
Expected Results
Don't know if this is the intended behavior, otherwise, maybe open it in a new window?

Bill said he would like it to be opened in a new tab.

Tested on dev22 (updated on april 3rd, both backend and frontend).
Terms And Conditions page now opens in a new tab.

source: gharchive/issue

repo: SAP/cloud-commerce-spartacus-storefront


text:
Detail new guidelines for css refactoring and css variables

Come up with naming conventions and rules for the new css variables that will be added in the style refactoring. Also come up with general practices for the new styles after the refactoring.

Draft 1:
• Try to flatten the structure as much as possible (use css-grid) - accessibility?
• No need to use BEM, simple class name will suffice because of styling encapsulation provided by the shadow DOM (emulated or not)
• Certain features can be defined in the theme and activated via a flag. These flags could even be grouped in a mixin that activates a feature
• Avoid unnecessary markup, avoid outer div. Instead, use the :host selector to apply style to the component
• Try to avoid masking big duplicated chunks of html using css and rather use ts?

Css variables (custom properties)
• A css variable should be provided where a rule is defined and likely to be changed.
• Variables should be formatted like "--cx-{name of the rule}".
• When assigning a value to a rule and also providing a css variable for the same rule, provide the default using the fallback. i.e. `margin: var(--cx-margin, 0 10px 0 10px);`.
• Not everything need a variable. They should be added only if necessary and some styling should remain opinionated and not provide easy configuration.
• We should not add variables without a fallback unless the value is specified at the root of the component:

Bad
.test {
	Margin: var(--cx-color);
}

Ok
:root {
	--cx-color: red;
}

.test {
	Margin: var(--cx-color);
}

Most css variables will be scoped to a class or element but we should still aim to provide variables with a global scope. To distinguish the two types of variables, we should use a separate naming convention for global variables. These variables should be named --cx-theme-{name of the rule}.
Bonus
Suggestion: Use css variables in the theme. At the moment, we are mostly using sass variables with at static value. These values should be replaced with a css var and a fallback. This allows easier customisation for theme variables used inside of the styles lib rather than outside. For example, the font sizes are used inside the type mixin. Therefore there is no easy way to change the value of those variables so they have an effect inside the mixin. To fix this, we can do : $h1-font-size: var(--cx-theme-h1, $font-size-base * 2.25);. Afterwards, this variable can be modified in the :root of the app styles.

@LTiger14 I actually thought this ticket was going to be only about the list of css variables :) That being said, this list is also needed, and should be based on https://github.com/SAP/cloud-commerce-spartacus-storefront/issues/11#issuecomment-438174669.
we could either change this ticket, or start with a new one to come up with the css variable list. Where I think we should have 2 groups:
Theme variables:

--cx-theme-border-radius
--cx-theme-transition-time
...

Component variables:

--cx-width
--cx-margin
...

The effort of this/that ticket would be to come up with an initial list.
btw. I wouldn't mind to find a shortcut for --cx-theme...

I'd prefer to transition this ticket and have it more focused on getting the list.

Like @tobi-or-not-tobi mentioned, we should have to groups of css variables.
Theme variables:

--cx-theme-primary, --cx-theme-secondary (colors)
--cx-theme-border-radius
--cx-theme-transition-duration
--cx-theme-animation-duration
--cx-theme-gutter-width
--cx-theme-font-weight-normal/bold...
--cx-theme-spinner-size ?

Side note: In the styles library theme, there are multiple variables that aren't !default and therefore can't be easily overridden in their use within the styles lib. If the objective is also to override them we could add the following:

--cx-theme-font-size-base
--cx-theme-h1-font-size (h2,h3,h4...)
--cx-line-height-base
--cx-heading-line-height

Similarly :

--cx-theme-input-heigh (for example)
i.e. $input-height: var (--cx-theme-input-heigh, 48px);

Component variables:

--cx-margin
--cx-padding
--cx-height
--cx-width
--cx-min-height
--cx-min-width
--cx-border-width/style/color
--cx-grid-row/column
--cx-grid-template-columns/rows
--cx-justify-self/--cx-align-self/--cx-place-self
--cx-justify-items/--cx-align-items
--cx-text-align
--cx-color
--cx-background-color
--cx-grid-column-gap/--cx-grid-row-gap
--cx-flex-direction
--cx-justify-content
--cx-align-self/items/content
--cx-zoom
--cx-opacity
--cx-position ?
--cx-display ?

Documentation added


text:
Missing Statement in Migration Documentation about PropertySource Annotation when migrating from spring-xsuaa to SAP BTP spring-security

Issue Summary
The migration guide at https://github.com/SAP/cloud-security-services-integration-library/blob/2.14.1/spring-security/Migration_SpringXsuaaProjects.md misses the fact that the
@PropertySource(factory = IdentityServicesPropertySourceFactory.class, ignoreResourceNotFound = true, value = { "" }) // might be auto-configured in a future release

line must be added to the WebSecurityConfigurerAdapter as described in https://github.com/SAP/cloud-security-services-integration-library/tree/2ceaf87fc709cd4ce09d94823efaf886a1ffa5e5/spring-security#setup-spring-security-oauth-20-resource-server .
Without that line, the migration is incomplete and no configuration data is provided to the XsuaaServiceConfiguration(s).

Issue Report Checklist

[x] Real, current bug
[x] Not a duplicate
[x] Not covered in "Common Pitfalls" section of corresponding module's README.md e.g. java-security#common-pitfalls
[x] Reproducible
[x] Good summary, well I think so
[x] Well-documented , all below not applicable

[ ] log level increased to DEBUG debug logs provided, not applicable
[ ] POM provided, not applicable
[ ] dependency tree provided, not applicable
[ ] code snippet provided (when applicable), not applicable

Closing as the migration documentation has been updated.

authors: clnative liga-oz


text:
Search Page bugs fix

Search Page bugs fix
#299
Description
Minor UI bugs have been fixed
Checklist for Pull Requests

[x] Supplied as many details as possible on this change
[x] Included the link to the associated issue in the Issue section above
[x] The code conforms to the general development guidelines.
[ ] The code has unit tests where applicable and is easily unit-testable
[x] This branch is appropriately named for the associated issue

Hi @sanat-thukral,
I've checked the fixes and when light theme is active, the icons for product and component filters are now not visible unless I hover:

Could you please check?

please don't forget changeset too :-)

Thanks for the review @Klaus-Keller. The button has now been fixed :)

authors: Klaus-Keller sanat-thukral theStiggySpd

repo: SAP/guided-answers-extension


text:
Problem on fileUploader when changing context App

OpenUI5 version: 1.38
Browser/version (+device/version): Chrome
Any other tested browsers/devices(OK/FAIL): FireFox
Steps to reproduce the problem:

I have 2 application in my launchpad. When i Enter in one and trying to upload file via fileUploader Its ok! And i Can do that again. But when i am exiting of this app, and trying to enter on the second one that has a link to enter to the first one and i click on it, and trying again to upload: It's fail.

On debugger consol I constate the the Input type file had as file property Empty.
You can check that with  file attribute on this input that you can get it by its Id.
Thanks
My Object is the view is like that:
<VBox>
                    <u:FileUploader         id                  =   "FilesUploaderFT"
                                            name                =   "myFileUploadFT"
                                            uploadUrl           =   "/sap/opu/odata/sap/ZFT_GW_FILE_MNGMT_SRV/FileMngmtSet"
                                            uploadComplete      =   "uploaderUploadComplete"
                                            change              =   "uploaderValueChange"
                                            typeMissmatch       =   "uploaderTypeMissmatch"
                                            style               =   "Emphasized"
                                            valueState          =   "{UploadImage>/urlState}"
                                            iconOnly            =   "true"
                                            icon                =   "sap-icon://add"
                                            fileType            =   "png,jpg,jpeg"
                                            sendXHR             =   "true"
                                            width               =   "150px"
                                            visible             =   "{Edit>/EditOn}"
                                            value               =   "{UploadImage>/URL}"
                                            class               =   "sapUiTinyMarginBegin sapUiTinyMarginEnd"/>

                    <Input                  value               =   "{UploadImage>/description}"
                                            visible             =   "{Edit>/EditOn}"
                                            valueState          =   "{UploadImage>/descriptionSate}"
                                            width               =   "150px"
                                            class               =   "sapUiTinyMarginBegin sapUiTinyMarginEnd"/>
                </VBox>

When i debbug on change event i have no value on the fileList
uploaderValueChange: function (evt){
    console.log(evt);
}

My result is like that: enter image description here

Thanks for your help if somebody know this issue.
I am using SAPUI5 1.38 in production.

Hello @shmoolki ,
Could you please provide a url or jsbin where the issue is reproducible?
I am understanding that the issue is reproducible between two apps but we need a reproducible example in order to investigate the issue.
Regards, Diana

Since there is no response from the author for more than 4 weeks I'm closing the ticket.

authors: Shtilianova shmoolki

license_source: bigquery


text:
removeAllMessages() function does not work if we set a new model

OpenUI5 version: Latest from https://sapui5.hana.ondemand.com/resources/sap-ui-core.js
URL (minimal example if possible): https://js.do/derexa/sapui5error
Steps to reproduce the problem:

Add error message to a component with .getMessageManager().addMessages()
Set a new model
Function .removeAllMessages() no longer works

What is the expected result? The input field is no longer in "error state"
What happens instead? The input state is still in "error state"
Any other information? (attach screenshot if possible)

Hello @derxe ,
Thank you for sharing this finding. I've created an internal incident 2070436327. The status of the issue will be updated here in GitHub.
Regards,
Tsanislav

Hello @derxe ,
I have looked into this and found that .removeAllMessages() does indeed work. All messages in the message model are removed. The issue here is that the ValueState of the control is not reset after switching the model. We are looking into this and will update this ticket once there is news.
Greetings,
Peter.

Hello @derxe ,
We have provided a fix for the issue. Problem was that after a control had its Binding removed (unbindProperty or setting a different model) the ValueState of the control was not reset. MessageModel.removeAllMessages() worked as intented.
The fix will be available with OpenUI5 version 1.86.
Greetings,
Peter.

authors: PeterBuchholz derxe tsanislavgatev


text:
Getting error as 'Instance of Client has no entity_sets as member'

please help me with this error. refer the screenshot below.

Odata version: V4
Code:
import requests
import requests.auth
from requests_ntlm import HttpNtlmAuth
import pyodata
// This is just the example credential
username = "example"
password = '*********'
// Good unit is the name of the entity
directorURL = 'https://odata.ca-build.com/odata/GoodUnit'
directorSession = requests.session()
directorSession.auth= HttpNtlmAuth(username,password)
directorReqData = pyodata.Client(directorURL,directorSession)
abc = directorReqData.entity_sets.GoodUnit.get_entity(1).execute()

I am terribly sorry but OData V4 hasn't been merged to the latest version of PyOData. Please, subscribe for news at https://github.com/SAP/python-pyodata/issues/39

authors: filak-sap sohebkm

repo: SAP/python-pyodata


text:
[FEATURE] buildThemes: Add "compress" option

Thank you for your contribution! 🙌
To get it merged faster, kindly review the checklist below:
Pull Request Checklist

[ ] Reviewed the Contributing Guidelines

Especially the How to Contribute section

[ ] No merge commits
[ ] Correct commit message style

Coverage increased (+0.006%) to 90.282% when pulling 27785bde9fec69611f86a768c4fe1c35b83cb72a on buildThemes-compress into fdb0241faec60062b1da52cc296dc343507fb802 on master.


text:
Update js executor method calls

Related to new require and https://github.com/eclipse/dirigible/pull/1170

@tdermendjiev could you please rebase the PR on the main branch and increase the Dirigible version to 5.12.21?

authors: ThuF tdermendjiev

repo: SAP/xsk


text:
Set Up SAP Business Application Studio for Development

Tutorial URL: https://developers.sap.com/tutorials/appstudio-onboarding.html
Hi Raz,
I think the first steps are not needed anymore in trial. One can access the Business Application Studio right from the start from the Quick Tool Access section without subscribing or assigning roles.
Could you check that? It worked for me with a new trial account and I also heard that from others.
Thanks,
René

Hi @renejeglinsky ,
That's correct. For new trial accounts, BAS setup is automated and the subscription si auto-enabled.
I plan to update the tutorial accordingly.
Regards - Raz

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.

authors: MichaelCzcz raz-korn renejeglinsky

repo: SAPDocuments/Tutorials


text:
Process restructuring

This is a major restructuring to solve several shortcomings:

the processor now accepts geometries spanning multipe UTM zones (https://github.com/SAR-ARD/S1_NRB/issues/32)
the SNAP processing has been outsourced to a new module snap
SNAP processing is now much more efficient by

combining all procesing steps of pyroSAR.snap.geocode and pyroSAR.snap.noise_power (https://github.com/SAR-ARD/S1_NRB/issues/39)
reusing intermediate processing output for multi-UTM processing
geocoding only to areas that are needed for the current UTM zone

no longer create DEM MGRS tiles but rather only create scene-specific mosaics in EPSG:4326 (the MGRS tiling was done to save time because EGM2008 conversion used to be very slow. This is no longer an issue nad the storage space can thus be saved)

Great, thanks John! Is it still work in progress? I could do some tests later today.

Hi Marco. This is almost ready. However, so far I have only fully tested it with IW GRD images because for SLCs I got a weird SNAP error during terrain flattening, something about slant range - ground range lookup tables. Haven't figured out what the source is yet.
You are very welcome to give it a try. I was going to ask you to revise the logging functionality. The pyroSAR log messages are now printed twice. I don't quite understand your logging module yet :sweat_smile:.

The duplicate log messages are now fixed and I added a few other improvements.
Error: SARGeoCoding: srgrConvParams not set is the one you also get when processing SLC, right?
TF works with tf.parameters['outputSimulatedImage'] = False, but other than that I didn't find anything else 😕

Sorry @maawoo, I forgot to mention that this PR depends on changes in pyroSAR in https://github.com/johntruckenbrodt/pyroSAR/pull/225 and https://github.com/johntruckenbrodt/pyroSAR/tree/feature/dem_enhance. It seems you have figured that out yourself anyways though :muscle:.

Yes, I figured that out 🙂
The problem also occurs in the SNAP GUI and using an auto-downloaded DEM. So two factors that can be ruled out.

I just had a look into the TF source code looking for srgrConvParams and I think line 812 needs to be moved after the if (isGRD) clause line 820. But maybe I'm wrong 😅 Anyway, I think this issue is out of our hands and needs to be reported.

I just had a look into the TF source code looking for srgrConvParams and I think line 812 needs to be moved after the if (isGRD) clause line 820. But maybe I'm wrong 😅 Anyway, I think this issue is out of our hands and needs to be reported.

Thanks @maawoo for having a look. I have created an issue:
https://forum.step.esa.int/t/terrain-flattening-output-simulated-image-fails-for-s1-slcs/37359

authors: johntruckenbrodt maawoo


text:
Expose a way for user to set different element speed matrices/tensors

For both 2D and 3D provide a way for the user to set the element Tet "M" or Tri "T" values.

done here 563732023569fdd71382e72e735400f5a859edb2


text:
UI intent parser producing invalid links

In GitLab by @mweston on Jan 23, 2020, 10:10
The UI intent parser is producing invalid structured request links
To reproduce:

Pick a document, e.g. https://docs.google.com/document/d/1Q7_iFHgCOkI3ls4l9ZqbKOZ7UgQraZT0sy5pby7Na5g
Add-Ons -> Intent Parser -> Generate Structured Request
The link that is produced is:
http://intentparser2.sd2e.org//document_request?1Q7_iFHgCOkI3ls4l9ZqbKOZ7UgQraZT0sy5pby7Na5g
which returns a "Resource Not Found" web page.
This has an extra slash and won't resolve, extra slash needs to be removed.

Some observations

The UI version appears to be "2.3post" - is this the new release version with the regressions we have been discussing?

In GitLab by @mweston on Jan 28, 2020, 17:39
Resolved, previous version of IP deployed

In GitLab by @mweston on Jan 28, 2020, 17:39
closed


text:
Unemplemented cancel button for email confirmation code

The button "x" and cancel, which is used to shut down the email confirmation code field, is displayed, but their functionalities are not emplemented.

The issue can be refered to #15

repo: SDD-Time-Traveler-Team/EZcalendar-Web


text:
Implement NativeQueryBuilder

User story
as a programmer using SpringHarvest I want to have more control over the queries passed to the db.
Specifications · Screen design
Based on TypedQueryBuilder
Related tasks
#25

Add issue key here

Not enough time left


text:
Module 2 Exercise 3 [Edith Kwablah]

Please "drag & drop" exercise 3 file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.
Edith Kwablah_module 2_Ex3.docx

Excellent analysis!

authors: JuliePeeling edythneska

repo: SERVIR-WA/GALUP


text:
orderc, orderd, and orderi have inconsistent documentation

These functions all determine the order of elements in a character (orderc), a double precision float ('orderd), and an integer (orderi`) array.
All three are exhibiting the same behavior, so I will use orderc as the example. Here is the cspyce inputs and returns:
    Inputs:
      string[*] array  = Input array.

    Returns:
      int       iorder = Order vector for array.

When this unit test is run:
import cspyce as cs
import numpy.testing as npt

inarray = ["a", "abc", "ab"]
expected_order = [0, 2, 1]
order = cs.orderc(inarray)
npt.assert_array_almost_equal(expected_order, order)
# Using ndim
order = cs.orderc(inarray)
npt.assert_array_almost_equal(expected_order, order)

It gives the following error:
Traceback (most recent call last):

  File ~/venv/lib/python3.10/site-packages/spyder_kernels/py3compat.py:356 in compat_exec
    exec(code, globals, locals)

  File ~/GitHub/pds-cspyce/unittests/untitled0.py:7
    order = cs.orderc(inarray)

  File ~/GitHub/pds-cspyce/cspyce/cspyce2.py:11221 in orderc
    return cs1.orderc(array)

  File ~/GitHub/pds-cspyce/cspyce/cspyce1.py:871 in orderc
    return cspyce0.orderc(array, len(array))

TypeError: orderc() takes 1 positional argument but 2 were given

A look into cspyce0_part2.i confirms that this function has more to it that one argument and one return:
%rename (orderc) my_orderc_c;
%apply (void RETURN_VOID) {void my_orderc_c};
%apply (SpiceInt DIM1, SpiceInt DIM2, ConstSpiceChar *IN_STRINGS)
                {(SpiceInt ndim, SpiceInt arrlen, ConstSpiceChar *array)};
%apply (SpiceInt *SIZE1, SpiceInt **OUT_ARRAY1) {(SpiceInt *n, SpiceInt **iorder)};

%inline %{
    void my_orderc_c(
        SpiceInt ndim, SpiceInt arrlen, ConstSpiceChar *array,
        SpiceInt *n,   SpiceInt **iorder)
    {
        *n = ndim;
        *iorder = my_int_malloc(ndim, "orderc");
        if (*iorder) {
            orderc_c(arrlen, array, ndim, *iorder);
        }
    }
%}

This needs to be fixed. Here is the CSPICE equivalent:
Brief_I/O
   VARIABLE  I/O  DESCRIPTION
   --------  ---  --------------------------------------------------
   arrlen     I   String length.
   array      I   Input array.
   ndim       I   Dimension of array.
   iorder     O   Order vector for array.

Just delete the code in cspyce1.py for the three order functions.  (Lines
868-881)
I should have deleted them earlier. They were part of a failed experiment.
On Wed, Jul 19, 2023 at 01:40 esimpsons3ti @.***> wrote:

Assigned #116 https://github.com/SETI/pds-cspyce/issues/116 to @fyellin
https://github.com/fyellin.
—
Reply to this email directly, view it on GitHub
https://github.com/SETI/pds-cspyce/issues/116#event-9856293320, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABC2LIIB7IZVZOKBHOVCZMLXQ4NGVANCNFSM6AAAAAA2PC4ZLA
.
You are receiving this because you were assigned.Message ID:
@.***>

--
Sent from Gmail Mobile

repo: SETI/pds-cspyce


text:
Update cassini vims preview key link to pdf

Replaced existing key file COVIMS_previews.txt with /holdings/documents/COVIMS_0xxx/VIMS-Preview-Interpretation-Guide.pdf

Rather than linking to /holdings/documents/COVIMS_0xxx/VIMS-Preview-Interpretation-Guide.pdf, I think I'd prefer to copy that file into /cassini/vims and link to it there. Do you have reservations with that approach?

This looks good to me. It closes issue #70

repo: SETI/pds-website


text:
[Feature] Support JSON Resume Schema

Describe the solution you'd like
Implement a JSON import utility that can import external JSON data in JSON resume schema.

https://jsonresume.org/schema/

repo: SHENG-X/simple-resume


text:
🛑 Website is down

In fcc7ee4, Website (ELTeam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Website is back up in afa7ecb after 19 minutes.

repo: SIRMaxis/uptime-robot


text:
🛑 DNS2.electro is down

In 4beabdf, DNS2.electro (ns2.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS2.electro is back up in 1fa4042 after 14 minutes.


text:
🛑 Website is down

In c872677, Website (ELTeam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Website is back up in 3f4c732 after 30 minutes.


text:
🛑 DNS2.electro is down

In 0f13f1f, DNS2.electro (ns2.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS2.electro is back up in 1bab99a after 27 minutes.


text:
🛑 DE Server is down

In 16bd72b, DE Server (de1.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DE Server is back up in 53c0ae8 after 48 minutes.


text:
🛑 DNS2.electro is down

In 022ea32, DNS2.electro (ns2.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS2.electro is back up in dd69105 after 21 minutes.


text:
🛑 DE Server is down

In e2fe6cb, DE Server (de1.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DE Server is back up in 296f41f after 6 minutes.


text:
🛑 DE Server is down

In 30deacd, DE Server (de1.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DE Server is back up in 5e96851 after 21 minutes.


text:
🛑 DE Server is down

In 12a8a49, DE Server (de1.elteam.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DE Server is back up in 94a7228 after 12 minutes.


text:
KeyError: 'ConvWS is already registered in conv layer'

When i run train.py, this error occured.
File "/home//PycharmProjects/Oriented_object_detect/r3det-on-mmdetection/mmdet/ops/conv_ws.py", line 23, in
class ConvWS2d(nn.Conv2d):
File "/home//anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 122, in _register
module_class=cls, module_name=name, force=force)
File "/home/***/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 58, in _register_module
raise KeyError(f'{module_name} is already registered '
KeyError: 'ConvWS is already registered in conv layer'

When i run train.py, this error occured.
File "/home//PycharmProjects/Oriented_object_detect/r3det-on-mmdetection/mmdet/ops/conv_ws.py", line 23, in class ConvWS2d(nn.Conv2d): File "/home//anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 122, in _register
module_class=cls, module_name=name, force=force)
File "/home/***/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 58, in _register_module
raise KeyError(f'{module_name} is already registered '
KeyError: 'ConvWS is already registered in conv layer'

use this structure and everything will be OK
install dependencies: (use cu101 because colab has CUDA 10.1)
!pip install -U torch==1.5.1+cu101 torchvision==0.6.1+cu101 -f https://download.pytorch.org/whl/torch_stable.html
install mmcv-full thus we could use CUDA operators
!pip install mmcv==0.6.1
Install mmdetection
!rm -rf r3det-on-mmdetection
!git clone https://github.com/SJTU-Thinklab-Det/r3det-on-mmdetection
%cd r3det-on-mmdetection
!pip install -r requirements/build.txt
pip install "git+https://github.com/open-mmlab/cocoapi.git#subdirectory=pycocotools"
!pip install -v -e .  # or "python setup.py develop"
install Pillow 7.0.0 back in order to avoid bug in colab
!pip install Pillow==7.0.0

It does work for me. Thank you!

When i run train.py, this error occured.
File "/home//PycharmProjects/Oriented_object_detect/r3det-on-mmdetection/mmdet/ops/conv_ws.py", line 23, in class ConvWS2d(nn.Conv2d): File "/home//anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 122, in _register
module_class=cls, module_name=name, force=force)
File "/home/***/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 58, in _register_module
raise KeyError(f'{module_name} is already registered '
KeyError: 'ConvWS is already registered in conv layer'

use this structure and everything will be OK
install dependencies: (use cu101 because colab has CUDA 10.1)
!pip install -U torch==1.5.1+cu101 torchvision==0.6.1+cu101 -f https://download.pytorch.org/whl/torch_stable.html
install mmcv that match mmdetection version 2.1.0
!pip install mmcv==0.6.1
Install mmdetection
!rm -rf r3det-on-mmdetection
!git clone https://github.com/SJTU-Thinklab-Det/r3det-on-mmdetection
%cd r3det-on-mmdetection
!pip install -r requirements/build.txt
!pip install -v -e . # or "python setup.py develop"
install Pillow 7.0.0 back in order to avoid bug in colab
!pip install Pillow==7.0.0

hi @nimaone
I follow your steps. But, when i run the !pip install -v -e . # or "python setup.py develop", there is an error like this.

ERROR: Command errored out with exit status 1: /home/user/anaconda3/envs/R3Det/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/user/code/r3det-on-mmdetection/setup.py'"'"'; file='"'"'/home/user/code/r3det-on-mmdetection/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

How can I solve this problem?
Thanks a lot

https://stackoverflow.com/questions/63508264/how-i-can-solve-the-error-command-errored-out-with-exit-status-1
------------------ 原始邮件 ------------------
发件人:                                                                                "SJTU-Thinklab-Det/r3det-on-mmdetection"                                                                                @.>;
发送时间: 2021年4月23日(星期五) 下午4:12
@.>;
@.>;"State @.>;
主题: Re: [SJTU-Thinklab-Det/r3det-on-mmdetection] KeyError: 'ConvWS is already registered in conv layer' (#5)
When i run train.py, this error occured.
File "/home//PycharmProjects/Oriented_object_detect/r3det-on-mmdetection/mmdet/ops/conv_ws.py", line 23, in class ConvWS2d(nn.Conv2d): File "/home//anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 122, in _register
module_class=cls, module_name=name, force=force)
File "/home/***/anaconda3/envs/mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 58, in _register_module
raise KeyError(f'{module_name} is already registered '
KeyError: 'ConvWS is already registered in conv layer'
use this structure and everything will be OK
install dependencies: (use cu101 because colab has CUDA 10.1)
!pip install -U torch==1.5.1+cu101 torchvision==0.6.1+cu101 -f https://download.pytorch.org/whl/torch_stable.html
install mmcv that match mmdetection version 2.1.0
!pip install mmcv==0.6.1
Install mmdetection
!rm -rf r3det-on-mmdetection
!git clone https://github.com/SJTU-Thinklab-Det/r3det-on-mmdetection
%cd r3det-on-mmdetection
!pip install -r requirements/build.txt
!pip install -v -e . # or "python setup.py develop"
install Pillow 7.0.0 back in order to avoid bug in colab
!pip install Pillow==7.0.0
hi @nimaone
I follow your steps. But, when i run the !pip install -v -e . # or "python setup.py develop", there is an error like this.
ERROR: Command errored out with exit status 1: /home/user/anaconda3/envs/R3Det/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/user/code/r3det-on-mmdetection/setup.py'"'"'; file='"'"'/home/user/code/r3det-on-mmdetection/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.
How can I solve this problem?
Thanks a lot
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: HsLOL Richard-mei nimaone


text:
Verbesserungsvorschlag Manueller Umbruch in Text

Hallo,
erstmal wieder sehr geile Arbeit. Der neue Adapter ist jetzt schon der Hammer!!
Wäre es wie beim "alten" Energiesfluss-adapter möglich, einen manuellen Umbruch in den Text einzubauen?  hat leider nicht funktionert. Eilt aber nicht.
Vielen Dank!

Aktuell könntest Du ja 2 der Textbausteine anlegen. Da diese "Text-zentriert" sind, wirkt es, wie ein Textumbruch.

habe den Adapter mal getestet, ja, sehr modern, man kann wirklich sehr viel einstellen, dass macht es etwas Arbeitsreicher, aber ok. Kann man nicht die Konfiguration vom anderen Adapter übernehmen?

Die Adapter basieren auf verschiedenen Einstellungen und Daten. Ein Import ist nicht vorgesehen.

Hallo, dein Fehler wurde in der aktuellen Version berücksichtigt.
Bitte installiere diese Version und prüfe, ob alles erledigt ist.
Falls ja, bitte das Issue schließen.
Vielen Dank!

authors: SKB-CGN raidsec reihd


text:
color bug fix

bug #6

well done!

repo: SMACS-MtSAC/smacs-website


text:
How to use userData in custom assign protocol?

Assign protocol provides userData that can be passed to member in consumerGroup.
For each member userData can be different (generated in protocol implementation) but there are no handlers for that data.
I'm trying to pass some extra data for each consumer in group, but can't get all data from syncGroupResponse cleanly
I do something like this:

const oldHandler = this.consumerGroup.handleSyncGroup.bind(this.consumerGroup);
this.consumerGroup.handleSyncGroup = (syncGroupResponse, callback) => {
        this.userData = syncGroupResponse.userData;
        oldHandler(syncGroupResponse, callback);
};

But I think It's not good way to do this.
Therefore I have some questions:
Did I understand correctly logic of userData parameter in protocol?
If yes, how to pass userData to member correctly?
If no, what is the aim of userData parameter?

I believe the userData is only available in the joinGroupResponse so that the leader is able to act on the userData.

authors: hyperlink makhtev

repo: SOHU-Co/kafka-node

license: mit


text:
Create topics sync returns before the topics are actually created

Hi,
I use the following code in order to create a topic
function createTopics(topics) {
    console.log('Creating kafka topics', topics);
    var promise = new Promise(function (resolve, reject) {
        producer.createTopics(topics, false, function (err, res) {
            if (err) {
                console.error('Failed to create topic(s)', err);
                return reject(err);
            }
            console.log('Kafka topic(s) created');
            return resolve(res);
        });
    });
    return promise;
}

The output looks like this:
Creating kafka topics [ 'test3' ]
  kafka-node:Client create topics currentAttempt 1 +0ms
Kafka topic(s) created
  kafka-node:Client kafka reported topics [] +114ms
  kafka-node:Client Topics left test3 +15ms
  kafka-node:Client create topics currentAttempt 2 +204ms
  kafka-node:Client kafka reported topics [ 'test3' ] +8ms
  kafka-node:Client Topics created test3 +1ms

As you can see, "Kafka topic(s) created" message is printed before the topic was actually created.
Is this a bug or the expected behavior?
Thanks

I see the wording in the readme is confusing about this but passing false should yield the callback right away.

So how can I wait or verify that the topics were created?

If you pass in true instead the callback will be called once it has verified all topics were created (or it ran out of retries).

Thanks

I think you updated this already right? can this be closed?

Not quite, the API in the Readme.md should be updated, since the wording is very confusing.
I suggest something like

When async is set to true, the callback is called after it has been verified that all topics were created or an error ocurred. If async is set to false, the callback will be called immediately without verifying the creation.

instead of

When async is set to false, this method does not return until all topics are created, otherwise it returns immediately.

At least that is how I interpret the source code of the createTopics method ;)
In addition, I think it's very confusing that the method throws an exception when one of the topics has an illegal name, only if async is set to false and the callback is called with that error if it's set to true.

authors: 0x530302 CharlesWall hyperlink kobik


text:
Fixing keyed partitioner

This pull request solves the problem of https://github.com/SOHU-Co/kafka-node/issues/354
When sending the first events with the producer, the topic metadata is not yet updated and the partitions array is empty. It causes the partitioner to return NaN which fails the producer.
This pull request returns 0 as the chosen partition as long as the partitions array is empty.
It still feels like a workaround, since I would expect the producer to update the metadata before firing the ready event. So it would be great if anyone could pick that up.

Great job @itamarwe !

From our use of the library we came across the same issue when using the producer as it doesn't have any previous metadata about a partition. We got around it temporarily by refreshing the metadata once the client and producer are both connected and ready, as this gives the necessary information to the buildPayloads method of the HighLevelProducer, as we haven't had time to figure out the best place to fix the issue. As part of the send it already checks the payload against the metadata, fails, refreshes the metadata and then fails checks a second time.
I agree that simply returning 0 is a workaround, especially in our case where messages with the same key are placed on the same partition to ensure order. In this case returning 0 for the first message on boot of the process, would cause out of order messages. In my opinion this means the KeyedPartitioner is no longer useful, as you use that partitioner to have finer grained control over which partition your messages go onto.
Currently our workaround looks like:
this.client = new kafka.Client(this.connectionString, this.name);
this.producer = new kafka.HighLevelProducer(this.client, {
    partitionerType: 3, // Keyed partitioner
});
this.producer.on('ready', () => {
    this.client.refreshMetadata(this.topics, (err) => {
        if (err) {
            this.emit('error', err);
        }
        this.emit('ready');
    });
});

I would propose to cause a metadata refresh during the connect method of the HighLevelProducer, but would require knowledge of the topics or cause a natural refresh of the metadata during construction of the client. Ideally the best solution would be to rebuild the payload following a failure of the clients send method, as the refresh will have been performed. But I couldn't make up my mind on the best approach to go down, so thought it would be worth a discussion.

Well, though this PR does not fix the root cause (i.e. partitioner.getPartition() must be called after successful metadata update) it at least temporary fixes issues caused by the current and wrong behavior.

@estliberitas How would you fix the root cause? I don't mind investing some time on it.
I think the relevant cases are on initialization (the metadata is empty) and after an update.
Any ideas of how to solve this properly?

@itamarwe well, since the work on module was iterative without any limitations, design goals, etc. I let myself say it's just got very complex and I already don't understand how things work there. If we ever to change things, we would re-design it and make it a much better piece of code. Or provide a plan for iterative refactoring.

@itamarwe last comment was for the long-term, in a short-term: we should care about buildPayloads() being called only if metadata exists already. Right now there is no restriction for that at least in high-level producer as far as I see.

When we get 'brokersChanged' event, it's already some kind of race condition, right?
https://github.com/SOHU-Co/kafka-node/blob/master/lib/highLevelProducer.js#L85
And it's not reflected in send() or buildPayloads() in any way, right?
https://github.com/SOHU-Co/kafka-node/blob/master/lib/highLevelProducer.js#L104

Would you say the send method should update the metadata and rebuild the payload in case of failure?
Another option would be to restrict sending when the metadata is not updated, but on the other hand, due to the asynchronous nature of node, the brokers can update from the moment the send function was invoked until the message is actually delivered. So upon a brokers change, some messages will fail regardless.
Perhaps the right solution is to have a mechanism that updates the metadata and rebuilds the payload upon failure?

@estilberitas I would disagree that adding in other "wrong" behaviour is worth a temporary fix. Because if you need to guarantee ordering of messages being placed on kafka, having the first message when the process boots up being placed to partition 0 will allow messages to be out of order. The whole reason you want to use the keyed partitioner is you want all messages with the same key to be placed on the same partition, and this temporary fix will stop it doing that. It will also be incredibly hard to track down where the inconsistency is coming from, where as at the moment it throws and error, which using something like my workaround above will fix and guarantee ordering.
If you don't care about ordering of messages, then the partition that a message is placed into doesn't really matter, and you can just use a partitioner like the CyclicPartitioner.

@mrjpsycho I tend to agree with you. Let's try to find a more suitable solution.
Nevertheless, will your workaround survive brokers change? Any other event we should account for?

@mrjpsycho agree.
@itamarwe it won't survive brokers change, because it's only wrapper around initialization, forcing metadata refresh.

@itamarwe as @estliberitas says it won't survive things like brokers changing, we added in some additional attempts to refresh the metadata if a send from the HighLevelProducer fails incase a broker goes down, to mitigate the issues somewhat. This was the whole reason we've not been able to figure out the best place(s) to add in refreshing of metadatas, as there are potentially many scenarios that require it, on both producing and consuming sides. Its going to need some careful consideration for the best location for the refresh to occur.

@itamarwe @mrjpsycho let's create a separate issue for this - meaning correcting of flow for publisher only for now. My plan is to fix publishing part once and for all. And consider as more cases as possible: brokers changing, streaming, batching, async (de)compression, etc. The only problem is I almost don't have a time for this now. So if you'd start, I'd join discussion later.

Hi,
I have also just come across this bug and I have implement a workaround in the HighLevelProducer that seems to work.
Currently the send method looks like this:
HighLevelProducer.prototype.send = function (payloads, cb) {
    this.client.sendProduceRequest(this.buildPayloads(payloads, this.client.topicMetadata), this.requireAcks, this.ackTimeoutMs, cb);
};

I have changed it to be this:
HighLevelProducer.prototype.send = function (payloads, cb) {
    var self = this;

    var required = payloads.filter(function(p){ return !p.hasOwnProperty('partition') }).map(function(p){ return p.topic });
    var missing = required.filter(function(t){ return !self.client.topicMetadata[t] });

    var doSend = function() {
        self.client.sendProduceRequest(self.buildPayloads(payloads, self.client.topicMetadata), self.requireAcks, self.ackTimeoutMs, cb);
    };

    if (missing.length) {
        // Need to refresh meta data because it is not set
        // for some of the topics and we won't able to calculate
        // the correct partitions for some of the payloads
        return this.client.refreshMetadata(missing, function() {
            doSend();
        });
    }

    doSend();
};

The issue as mentioned above is that the topicMetadata isn't set when you try to send. This means there isn't a list of topic partitions needed to calculate the partition number to use based on the hash of the payload key. My work around checks for topicMetadata for each of the specified topics and if there are any missing then it will refresh the topicMetadata and then send. Otherwise it just sends as expected.
Not sure if this is the correct fix, but seems to do the trick for me.

@craighardcastle Your fix looks good to me. What worries me, is that it will refresh the metadata for every send until the metadata is refreshed. It would probably be better to only do it once, and then send all of the outstanding events once the metadata is refreshed.

Yeah valid point @itamarwe. I have only been using a simple test app and therefore had no concurrent send requests. The simplest way to solve that issue is to use a async queue with a concurrency of 1:
var HighLevelProducer = function (client, options) {
    //... other constructor code

    this.sendQueue = async.queue(function(task, callback) {
        task(callback);
    }, 1);

    this.connect();
};

HighLevelProducer.prototype.send = function (payloads, cb) {
    var self = this;

    this.sendQueue.push(function(next) {
        var required = payloads.filter(function(p){ return !p.hasOwnProperty('partition') }).map(function(p){ return p.topic });
        var missing = required.filter(function(t){ return !self.client.topicMetadata[t] });

        var doSend = function() {
            self.client.sendProduceRequest(self.buildPayloads(payloads, self.client.topicMetadata), self.requireAcks, self.ackTimeoutMs, function(err, data) {
                cb(err, data);
                next();
            });
        };

        if (missing.length) {
            // Need to refresh meta data because it is not set
            // for some of the topics and we won't able to calculate
            // the correct partitions for some of the payloads
            return self.client.refreshMetadata(missing, function() {
                doSend();
            });
        }

        doSend();
    });
};

@craighardcastle Nice fix. Still, this would mean that the events would always be sent synchronously, which isn't always desired.
I was thinking more in the direction of using a flag while updating the metadata:
var HighLevelProducer = function (client, options) {
    //... other constructor code

    this.refreshingMetadata = false;
    this.sendQueue = [];

    this.connect();
};

HighLevelProducer.prototype.send = function (payloads, cb) {
    var self = this;
    var required = payloads.filter(function(p){ return !p.hasOwnProperty('partition'); }).map(function(p){ return p.topic; });
    var missing = required.filter(function(t){ return !self.client.topicMetadata[t]; });

    this.sendQueue.push(function(next) {
        var required = payloads.filter(function(p){ return !p.hasOwnProperty('partition'); }).map(function(p){ return p.topic; });
        var missing = required.filter(function(t){ return !self.client.topicMetadata[t]; });

        var doSend = function() {
            self.client.sendProduceRequest(self.buildPayloads(payloads, self.client.topicMetadata), self.requireAcks, self.ackTimeoutMs, function(err, data) {
                cb(err, data);
            });
        };

        if (missing.length===0){
          return doSend();
        }

        if (self.refreshingMetadata||self.sendQueue.length){
           return self.sendQueue.push(doSend);
        }

        self.refreshingMetadata = true;
        self.client.refreshMetadata(missing, function() {
            self.refreshingMetadata = false;
            while (self.sendQueue.length) {
              sendFn = self.sendQueue.shift();
              sendFn();
            }
            doSend();
        });
    });
};

Hi. Async queue is asynchronous not synchronous. If you mean it will send the queued messages in series then yes that is true, but it seems important to me to make sure that the queued requests are sent in the order in which the send method was called and the async queue guarantees this. Without making sure they are done in order then the topic could receive the messages out of order and this could cause all kinds of problems for consumers.
The problem here is that until send is called the code doesn't know whether it has the meta data for the specified topic(s). So the simplest solution is to wrap up the send in the async queue but this does affect all topics and makes every send request be processed in series. I guess you could maybe go a bit further and make an async queue per topic, thereby making it only series per topic, which doesn't seem bad to me, however the send() method takes a list of payloads that can each have a mixture of topics but that all have one callback, so writing the code to handle the multiple refresh calls and then the separate topic queues would be tricky.
Not sure on this one. Maybe @mrjpsycho @eugeneware @estliberitas or @mpj might have an opinion?
You could just change the docs to say "you must call refreshMetadata() before you send the first message to a new topic using a keyed message" :)

Right. I see what you mean about the different topics. My code above does not address that.
Regarding the synchronous vs asynchronous discussion, I think that the producer should leave the decision of whether or not to send the payloads in series to the developer. A developer could decide to send all events in order by waiting for the callback, or to send all events asynchronously. That way, the developer has the flexibility to decide.

Agreed, which is why the solution is tricky. But generally speaking I would think it you are using keyed messages then you do want the messages to be sent in order (per topic partition), but this method needs to work with all the partitioner types, and for some of those the send order is not necessarily important.
Starting to think just calling client.refreshMetadata() before you send the first message to a new topic might be the best workaround for now. Then, as you said, a developer can have total control of ordering and can just make sure they call refresh before calling send for the first time.

authors: craighardcastle estliberitas eugeneware itamarwe mrjpsycho


text:
Option to auto commit offsets on first join - Resolves #886

Record offsets at their current position, so that consumers are properly
registered to the topic.

@hyperlink is there any concerns with this PR?

@hyperlink any update on this?


text:
Define Treaty Struct

Define a struct called Treaty with the following fields:

uuid
signature count
duration time in days that the treaty will last, will be decremented each day
condition - enum of hp, food, floor and other conditions.
condition_op - a comparison operator for numbers
condition_amt - the amount to which the agent's condition must be compared
request - what must be done if the treaty condition is fulfilled, for example eat, leaveFood, dontEat ... others can be added
request_amt - if the request is eat then this is the amount that must be eaten.

For example you could have a treaty that looks like:
{"iweur", 1, 4 days, hp, >, 5, leaveFood, 2}
This treaty would say:
if agents hp > 5 then
leave at least 2 food on the platform for the floor below

Thinking about how this will fit in with handlers, would it be feasible for a base agent function to take in the op code and constraints in order to see if a treaty can be fulfilled?

This is already being handled in this branch

This is already being handled in this branch

Might be nice to put the treaty struct inside of util/global types and import it?

This is already being handled in this branch

Might be nice to put the treaty struct inside of util/global types and import it, since baseAgent will need access to this data type

Don't agents import messages already? They would get it from there wouldn't they?

This is already being handled in this branch

Might be nice to put the treaty struct inside of util/global types and import it, since baseAgent will need access to this data type

Don't agents import messages already? They would get it from there wouldn't they?

Yeahhh but as an important data type it might be nice to stick it in utils

authors: MattScottEEE Silvertrousers jzzheng22 woonmoon


text:
🛑 CAOS is down

In b543e8b, CAOS (http://caos.ayi-asociados.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CAOS is back up in 7b1741f after 28 minutes.

repo: SOPORTEAYIGROUP/AYIGROUP


text:
🛑 CAOSBI is down

In b819c3b, CAOSBI (https://caosbi.ayi-asociados.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CAOSBI is back up in 9d4ecc5 after 5 minutes.


text:
fix: ordering the list of items on the shelter edit page

Correção da listagem dos itens da página de edição de um abrigo.
Posteriormente a listagem estava ordenada de Z - A.

Após a correção, temos a listagem ordenada de A - Z.

Fix seems to work!

authors: alexanderscheibler gi-carnaval

repo: SOS-RS/frontend


text:
Support 1.7, 1.8, 1.9, 1.10, 1.11 and 1.12.

Let's make spu more *****!

NEVER. THESE OLD VERSIONS SHOULD ALREADY BE IN THE RUBBISH CAN.

I had been thinking a lot, and finally I decided to support these old versions to help increase the amount of players for newer versions.
It's duplicates with #24 now.

repo: SPGoding/spu


text:
:bug: Add missing strictScoreHolderCheck

Related to SPGoding/datapack-language-server#694

:tada: This PR is included in version 3.0.5 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:

authors: ChenCMD SPGoding

repo: SPGoding/vscode-datapack-helper-plus


text:
ADFT0015: Type [managedVirtualNetwork\default\managedPrivateEndpoint] is not supported.

I have a problem when trying to make release between environments in Azure DevOps build pipelines. I use managed virtual network and private endpoints in Azure Data Factory. What I want to achieve is to change names of private endpoints and privateLinkResourceId during deployment. In my private endpoints names I specify environment. Is it generally possible or I need to create private endpoints everytime I create new environment?
During deployment I get error:
ADFT0015: Type [managedVirtualNetwork\default\managedPrivateEndpoint] is not supported in Azure DevOps console.
I attach my config file.
test-config.txt

Moved issue to azure.datafactory.devops

I'll add to it. Doing deployment from Powershell. It actually works if you don't have to change anything inside the resource json. It blows up when you need to change something:
- [managedVirtualNetwork].[default]
- [managedVirtualNetwork\default\managedPrivateEndpoint].[pe1]
- [managedVirtualNetwork\default\managedPrivateEndpoint].[pe2]
===================================================================================
STEP: Replacing all properties environment-related...
Config file:   ./deployment/params_Dev.json
Write-Error: C:\Users\gshapiyev\1\Documents\PowerShell\Modules\azure.datafactory.tools\0.95.1\private\Update-PropertiesFromFile.ps1:65:19
Line |
  65 |  …    $objArr = Get-AdfObjectByPattern -adf $adf -name $name -type $type
     |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | ADFT0015: Type [managedVirtualNetwork\default\managedPrivateEndpoint] is not supported.`

I was able to get around the issue by adding another case in the switch in \private\Get-AdfObjectByPattern.ps1

        'managedPrivateEndpoint'
        {
            $r = $adf.ManagedPrivateEndpoints | Where-Object { $_.Name -like $name }
        }
        'managedVirtualNetwork\default\managedPrivateEndpoint'
        {
            $r = $adf.ManagedPrivateEndpoints | Where-Object { $_.Name -like $name }
        }
        default

authors: gshapiyevInspereX mrWiecek


text:
Why is currentItem nil when playlist played to the end?

Can your answer be found elsewhere?

[x] I have searched existing issues and found no similar question.

[x] I have browsed the available documentation and found no answer to my question.

Detailed question
When we play a playlist to its end it seems the players currentItem is nil.
But anyway canReplay() returns true and we can restart that item.
Shouldn't currentItem still be set to the last item or maybe to the first item? This way we could easily display to the user which item was just played or which will be played once we call replay()?

As discussed with you this is a tricky behavior. Some apps might want to display nothing, some apps might want to stick with the last content being played or, as in your case, some apps might want to display the first item in this case.
The behavior is tricky and introducing a behavioral parameter to govern the player behavior for something that is more UI-related in the end would probably lead to a lot of complexity. On the app side, though, the code required is mostly:
var displayedItem: PlayerItem? {
    currentItem ?? items.first
}

or
var displayedItem: PlayerItem? {
    currentItem ?? items.last
}

since item / current item changes are automatically observed by Player and lead to view bodies being recalculated.
TL;DR Better do nothing and let the app decide. Flexible and much simpler / safer for everyone.

authors: defagos mbruegmann

repo: SRGSSR/pillarbox-apple


text:
✨ Mobile | Show LinkedIn against profiles

Hi team
Now that we have the ability to add a LinkedIn profile in Settings, we now need to show these against profiles.
Tasks

[ ] Show a LinkedIn icon on items on the Leaderboard if that user has a LinkedIn profile set

[ ] Maybe show these icons on the Network page as well

[x] On profile pages, show that user's LinkedIn profile and allow them to tap and open that link

Acceptance Criteria

[ ] Meets Definition of Done - https://github.com/SSWConsulting/SSW.Rewards.Mobile/blob/main/_docs/Definition-of-Done.md

Thanks!

Show a LinkedIn icon on items on the Leaderboard if that user has a LinkedIn profile set

Not done.
The purpose of the Leaderboard is to provide visibility and recognition to users, so LinkedIn information doesn't seem to belong there.
We also don't have enough space on the Leaderboard list item to accommodate social media information as we already shorten names and points.
When a user adds their LinkedIn profile, that action will appear on the Activity page.

Maybe show these icons on the Network page as well

The Network page might be the right place to show such information, but the page will require a re-design to accommodate the varying number of social media platforms.

On profile pages, show that user's LinkedIn profile and allow them to tap and open that link

Done, see the screenshot below.

Figure: LinkedIn profile icon which will open a browser when tapped.

authors: AntPolkanov zacharykeeping


text:
Harvesting

Add the ability to right-click harvest crop blocks, Simular to older versions of Minecraft.

This should be converted to a buff and support a range with a new sickle tool. Higher level sickle tools should harvest and replant up to a 5x5 grid!

Converted to buff-harvesting

This is now completed ready for 1.3

authors: ProjectHSI nomadjimbob

repo: STEMMechanics/Drustcraft


text:
-DHPX_WITH_GENERIC_CONTEXT_COROUTINES=ON, cannot find boost (missing context)

Expected Behavior
With -DHPX_WITH_GENERIC_CONTEXT_COROUTINES=ON in the CMake configuration,
HPX should be able to find boost and then compiles successfully.
Actual Behavior
With -DHPX_WITH_GENERIC_CONTEXT_COROUTINES=ON, HPX cannot find the boost (missing context) and failed to compile. In the CMakeCache.txt, it shows that
BOOST_ROOT:UNINITIALIZED=/autofs/nccs-svm1_sw/summit/.swci/1-compute/opt/spack/20180914/linux-rhel7-ppc64le/gcc-8.1.1/boost-1.61.0-dfvdknm3scg6h7xmvwiaoiucnbixkzvo

CMake error:
CMake Error at /autofs/nccs-svm1_sw/summit/.swci/0-core/opt/spack/20180914/linux-rhel7-ppc64le/gcc-4.8.5/cmake-3.15.2-xit2o3iepxvqbyku77lwcugufilztu7t/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Boost (missing: context) (found suitable version "1.61.0",
  minimum required is "1.61")
Call Stack (most recent call first):
  /autofs/nccs-svm1_sw/summit/.swci/0-core/opt/spack/20180914/linux-rhel7-ppc64le/gcc-4.8.5/cmake-3.15.2-xit2o3iepxvqbyku77lwcugufilztu7t/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /autofs/nccs-svm1_sw/summit/.swci/0-core/opt/spack/20180914/linux-rhel7-ppc64le/gcc-4.8.5/cmake-3.15.2-xit2o3iepxvqbyku77lwcugufilztu7t/share/cmake-3.15/Modules/FindBoost.cmake:2142 (find_package_handle_standard_args)
  cmake/HPX_SetupBoost.cmake:68 (find_package)
  CMakeLists.txt:1576 (include)

-- Configuring incomplete, errors occurred!

However, with same other settings yet removing this cmake option, HPX finds boost and has BOOST_ROOT initialized correctly.
Steps to Reproduce the Problem
... Please be as specific as possible while describing how to reproduce your problem.
Cmake configure:
    cmake \
            -DCMAKE_BUILD_TYPE=$BUILD_TYPE                                      \
            -DBOOST_ROOT=$OLCF_BOOST_ROOT                                       \
            -DHPX_WITH_GENERIC_CONTEXT_COROUTINES=ON                            \
            -DHPX_WITH_NETWORKING=ON                                            \
            -DHPX_WITH_PARCELPORT_MPI=ON                                        \
            -DHPX_WITH_PARCELPORT_TCP=OFF                                       \
            -DHWLOC_ROOT=                                                       \
            -DHPX_WITH_MALLOC=system                                            \
            -DCMAKE_INSTALL_PREFIX=$INSTALL_PATH                                \
            -DHPX_WITH_EXAMPLES=ON                                              \
            -DHPX_WITH_TOOLS=OFF                                                \
            -DHPX_WITH_MAX_CPU_COUNT=168                                        \
            -Wdev                                                               \
            $HPX_PATH

Specifications
... Please describe your environment

HPX Version: commit f9cd98b0634cb0cfdbbb18e13b2608488d3f54e0
Platform (compiler, OS): Summit IBM machine

I don't know if this issue was created before or after I responded via slack, but for completeness, I'll include here my build settings for summit
https://github.com/biddisco/biddisco.github.io/wiki/summit-(power9)
In short, I would almost never consider using a system installed boost and instead use the settings provided in the link provided
#environment
# setup versions we will use
GCC_version=9.1.0
CMAKE_version=3.15.2

# Versions
INSTALL_ROOT=$HOME/apps/gcc/$GCC_version

HWLOC_VER=2.0.4
JEMALLOC_VER=5.1.0
OTF2_VER=2.1.1
BOOST_VER=1.68.0
BOOST_SUFFIX=1_68_0
BOOST_ROOT=$INSTALL_ROOT/boost/$BOOST_VER
PAPI_VER=5.5.1
VC_VER=1.4.1
HDF5_VER=1.10.4

module unload gcc
module load   gcc/$GCC_version
module load   cmake/$CMAKE_version
module load cuda

export CC=gcc
export CXX=g++
export CFLAGS=-fPIC
export CXXFLAGS="-fPIC -mcpu=power9 -mtune=power9 -ffast-math -std=c++17"
export LDFLAGS=-dynamic
export LDCXXFLAGS="$LDFLAGS -std=c++17"

#Boost
wget http://vorboss.dl.sourceforge.net/project/boost/boost/$BOOST_VER/boost_$BOOST_SUFFIX.tar.gz
tar -xzf boost_$BOOST_SUFFIX.tar.gz
cd boost_$BOOST_SUFFIX
./bootstrap.sh
./b2 cxxflags="$CXXFLAGS" --prefix=$BOOST_ROOT --layout=system threading=multi link=shared variant=release architecture=power address-model=64 --without-mpi --without-python --without-graph --without-graph_parallel -j8 install

#cpptest
git clone git@github.com:biddisco/cpptest.git
cmake -DBOOST_ROOT=$BOOST_ROOT ~/src/cpptest/

#hwloc
cdb
wget --no-check-certificate https://www.open-mpi.org/software/hwloc/v2.0/downloads/hwloc-$HWLOC_VER.tar.gz
tar -xzf hwloc-$HWLOC_VER.tar.gz
cd hwloc-$HWLOC_VER
# cuda ?
# export CPPFLAGS='-I/opt/cuda/include'
# export LDFLAGS='-L/opt/cuda/lib64 -L/usr/lib64/nvidia'
# ./configure --prefix=$INSTALL_ROOT/hwloc/$HWLOC_VER  --enable-cuda
# no cuda
./configure --prefix=$INSTALL_ROOT/hwloc/$HWLOC_VER
make -j8 install

#jemalloc
cdb
wget https://github.com/jemalloc/jemalloc/releases/download/$JEMALLOC_VER/jemalloc-$JEMALLOC_VER.tar.bz2
tar -xjf jemalloc-$JEMALLOC_VER.tar.bz2
cd jemalloc-$JEMALLOC_VER
./autogen.sh --prefix=$INSTALL_ROOT/jemalloc/$JEMALLOC_VER
make -j8 -k install

#HPX (release, benchmarking)
cmake \
 -DCMAKE_BUILD_TYPE=Release \
 -DCMAKE_INSTALL_PREFIX=$INSTALL_ROOT/hpx/ \
 -DHPX_WITH_MAX_CPU_COUNT=168\
 -DHPX_WITH_CXX17=ON \
 -DCMAKE_CXX_FLAGS=$CXXFLAGS \
 -DCMAKE_EXE_LINKER_FLAGS=-dynamic \
 -DHWLOC_ROOT=$INSTALL_ROOT/hwloc/$HWLOC_VER \
 -DJEMALLOC_ROOT=$INSTALL_ROOT/jemalloc/$JEMALLOC_VER \
 -DBOOST_ROOT=$INSTALL_ROOT/boost/$BOOST_VER \
 -DHPX_WITH_MALLOC=JEMALLOC \
 -DHPX_WITH_HWLOC:BOOL=ON \
 -DHPX_WITH_NETWORKING=OFF \
 -DHPX_WITH_PAPI:BOOL=OFF \
 -DHPX_WITH_APEX:BOOL=OFF \
 -DAPEX_WITH_OTF2:BOOL=OFF \
 -DHPX_WITH_THREAD_IDLE_RATES:BOOL=OFF \
 -DHPX_WITH_TESTS:BOOL=ON \
 -DHPX_WITH_TESTS_BENCHMARKS:BOOL=ON \
 -DHPX_WITH_TESTS_EXTERNAL_BUILD:BOOL=OFF \
 -DHPX_WITH_TESTS_HEADERS:BOOL=OFF \
 -DHPX_WITH_TESTS_REGRESSIONS:BOOL=ON \
 -DHPX_WITH_TESTS_UNIT:BOOL=ON \
 -DHPX_WITH_EXAMPLES:BOOL=ON \
  $HOME/src/hpx

Also, can you check that libboost_context.so/a actually exists in /autofs/nccs-svm1_sw/summit/.swci/1-compute/opt/spack/20180914/linux-rhel7-ppc64le/gcc-8.1.1/boost-1.61.0-dfvdknm3scg6h7xmvwiaoiucnbixkzvo/lib?

@biddisco thanks! @weilewei, I wouldn't go with HPX_WITH_NETWORKING=OFF in your case, though.

@weilewei did you solve this in the end?

@msimberg problem solved. Thanks!

@msimberg problem solved. Thanks!

Thanks!

authors: biddisco hkaiser msimberg weilewei

repo: STEllAR-GROUP/hpx


text:
MPI init fixes

Attempts to fix MPI tests running on Rostam, but I would appreciate some input from @biddisco, @hkaiser on how we could do this better.

When using the parcelport option in hpxrun I added the priority configuration option to force the use of the chosen parcelport. The way the configuration is set up on master is that all available parcelports are enabled in the configuration, meaning that doing --hpx:ini=hpx.parcelport.tcp.enable=1 has really no effect. If in an MPI environment (like slurm with MPI support) the TCP parcelport would not be used.
I moved the MPI initialization so that it happens later in the startup process. On master the MPI environment is checked and initialized before the command line options are parsed, meaning that options like --hpx:ini=hpx.parcelport.mpi.enable=0 are not even considered when initializing MPI. Moving it even later leads to problems that I do not quite understand (it seems like all localities might think that they're locality 0, and try to do the full bootstrap procedure, not quite sure...).
OpenMPI may be broken on rostam. MPI_Finalize segfaults in an hwloc call... I'm changing the configurations to use only mpich for now.

I'm opening this as a draft to check if this even works on rostam. It seemed to work from my limited testing, but I'm 100% sure I've broken some other configuration like this.
Ideally I'd like to have the MPI parcelport only do the MPI initialization, instead of it happening early as it does now (with the exception for when networking is off and MPI really is a special case), but I'm not sure what that would require.

I think I'd prefer to leave this out of 1.5.0 since I'm not confident that this is correct, especially as the initialization is mostly unchanged from 1.4 and should keep working as before. We do need something like the priority changes, but I'm still unsure what's caused by the MPI setup on Rostam and what's HPX's fault. If I manage to find something before the release let's of course get it in, but I suspect that this is better left for a patch release afterwards.

I think I'd prefer to leave this out of 1.5.0 since I'm not confident that this is correct, especially as the initialization is mostly unchanged from 1.4 and should keep working as before. We do need something like the priority changes, but I'm still unsure what's caused by the MPI setup on Rostam and what's HPX's fault. If I manage to find something before the release let's of course get it in, but I suspect that this is better left for a patch release afterwards.

I think we should get Alireza (@akheir) involved here. He has done some MPI/SLURM integration work on rostam that might have the unneeded side effects we're seeing...

I think I'd prefer to leave this out of 1.5.0 since I'm not confident that this is correct, especially as the initialization is mostly unchanged from 1.4 and should keep working as before. We do need something like the priority changes, but I'm still unsure what's caused by the MPI setup on Rostam and what's HPX's fault. If I manage to find something before the release let's of course get it in, but I suspect that this is better left for a patch release afterwards.

I think we should get Alireza (@akheir) involved here. He has done some MPI/SLURM integration work on rostam that might have the unneeded side effects we're seeing...

Yes, he knows that we're having some difficulties with MPI, but I wanted to undestand things a bit better first before involving him further. I'll keep him in the loop when there's something to deal with.

I've rearranged things a bit again.

OpenMPI seems to be fine now, I was mixing different hwloc versions.  (MPICH not, but this is due to the version of MPICH coming with CentOS.)
I've kept the changes to parcelport priorities and hpxrun.
From local testing the only failing test seems to be thread_mapper. Let's see if anything else fails on jenkins.
I fixed the CUDA flags, so those should now finally be correct.

@hkaiser the thread_mapper test reports 4 parcelport threads, when it expects only 2. This is because both the MPI and TCP parcelport service pools get started (I don't think they're both actually used, only the one with higher priority). Is this actually intended or desired behaviour? This seems to be a result of the config entries hpx.parcel.x.enable all being 1 if the parcelport is there, and the service pool being started in that case. This is a new test, and jenkins on daint doesn't test the MPI parcelport, so that's why it never came up earlier.

@hkaiser the thread_mapper test reports 4 parcelport threads, when it expects only 2. This is because both the MPI and TCP parcelport service pools get started (I don't think they're both actually used, only the one with higher priority). Is this actually intended or desired behaviour? This seems to be a result of the config entries hpx.parcel.x.enable all being 1 if the parcelport is there, and the service pool being started in that case. This is a new test, and jenkins on daint doesn't test the MPI parcelport, so that's why it never came up earlier.

Ok, this needs fixing. I'll see what I can do.

@hkaiser the thread_mapper test reports 4 parcelport threads, when it expects only 2. This is because both the MPI and TCP parcelport service pools get started (I don't think they're both actually used, only the one with higher priority). Is this actually intended or desired behaviour? This seems to be a result of the config entries hpx.parcel.x.enable all being 1 if the parcelport is there, and the service pool being started in that case. This is a new test, and jenkins on daint doesn't test the MPI parcelport, so that's why it never came up earlier.

Ok, this needs fixing. I'll see what I can do.

Ok, thank you. Please let me know if I can help with that. Also feel free to push to this branch.
Unrelated, but I forgot to mention one more change: I've forced the launch_process test to run only with the TCP parcelport. Dynamically connecting MPI ranks is not possible, or am I mistaken?

retest lsu

retest lsu

@hkaiser I have a simple fix in place for the multiple parcelport service pools being started. I simply start the bootstrap parcelport and the highest priority parcelport (just one if they're the same). If this looks reasonable to you I can move out the logic of getting those parcelports into one place and use it for the other parcelport functionality as well. The minimal needed change is for starting and stopping the service pools, and the rest seems to gracefully do nothing or at least nothing harmful. It'd probably be good to filter out unnecessary parcelports from other operations as well. Or would there be a good reason to keep them initialized but doing nothing otherwise?

Unrelated, but I forgot to mention one more change: I've forced the launch_process test to run only with the TCP parcelport. Dynamically connecting MPI ranks is not possible, or am I mistaken?

It should work even if run using the MPI parcelport. The only caveat is that connecting processes will always use TCP, even if the main application runs using a different parcelport.

@msimberg please  note, I have pushed a fix for the failing thread_mapper test here.

Unrelated, but I forgot to mention one more change: I've forced the launch_process test to run only with the TCP parcelport. Dynamically connecting MPI ranks is not possible, or am I mistaken?

It should work even if run using the MPI parcelport. The only caveat is that connecting processes will always use TCP, even if the main application runs using a different parcelport.

@msimberg please note, I have pushed a fix for the failing thread_mapper test here.

Ah, please see the preceding commit as well. I'll leave it up to you to decide what we should do here. Your comment about the launch_process test makes it sound like we actually do want both the MPI and TCP parcelports to be started even if the MPI one has higher priority.

Ah, please see the preceding commit as well. I'll leave it up to you to decide what we should do here. Your comment about the launch_process test makes it sound like we actually do want both the MPI and TCP parcelports to be started even if the MPI one has higher priority.

To avoid doing this always, we could enable the TCP parcelport if it's the only one or only if the --hpx:expect-connecting-localities option (or similar) is provided (well, or if it's explicitly enabled using hpx.parcel.tcp.enable=1).

Ah, please see the preceding commit as well. I'll leave it up to you to decide what we should do here. Your comment about the launch_process test makes it sound like we actually do want both the MPI and TCP parcelports to be started even if the MPI one has higher priority.

To avoid doing this always, we could enable the TCP parcelport if it's the only one or only if the --hpx:expect-connecting-localities option (or similar) is provided (well, or if it's explicitly enabled using hpx.parcel.tcp.enable=1).

Currently all parcelports are enabled unless explicitly disabled, which is why the priorities are important. I'm fine with having them all enabled if that's expected behaviour. Especially as they don't really do anything with one locality (a few extra context switches for the pools maybe, but nothing significant). I'm really indifferent (and unsure) about what the right thing to do here is.

Currently all parcelports are enabled unless explicitly disabled, which is why the priorities are important. I'm fine with having them all enabled if that's expected behaviour. Especially as they don't really do anything with one locality (a few extra context switches for the pools maybe, but nothing significant). I'm really indifferent (and unsure) about what the right thing to do here is.

As long as you don't see any reason to change the current behavior I'd say, let's leave it unchanged. The user can always directly disable the TCP parcelport (for instance) if he/she wants to avoid instantiating it.

Currently all parcelports are enabled unless explicitly disabled, which is why the priorities are important. I'm fine with having them all enabled if that's expected behaviour. Especially as they don't really do anything with one locality (a few extra context switches for the pools maybe, but nothing significant). I'm really indifferent (and unsure) about what the right thing to do here is.

As long as you don't see any reason to change the current behavior I'd say, let's leave it unchanged. The user can always directly disable the TCP parcelport (for instance) if he/she wants to avoid instantiating it.

Yep, sounds sane. I'll have another look at the launch_process test to see if that still requires the changes it has now or not.

retest lsu

authors: hkaiser msimberg


text:
Incorrect bitfield definitions for lsm6dsv16bx_tap_time_windows_t and lsm6dsv16bx_tap_thresholds_t

The following structures in the lsm6dsv16bx driver have incorrect bitfield definitions that do not match the LSM6DSV16BX datasheet:

lsm6dsv16bx_tap_time_windows_t

Current:typedef struct {
  uint8_t shock : 1;
  uint8_t quiet : 1;
  uint8_t tap_gap : 1;
} lsm6dsv16bx_tap_time_windows_t;

Correct:typedef struct {
  uint8_t shock : 2;
  uint8_t quiet : 2;
  uint8_t tap_gap : 4;
} lsm6dsv16bx_tap_time_windows_t;

lsm6dsv16bx_tap_thresholds_t

Current:typedef struct {
  uint8_t x : 1;
  uint8_t y : 1;
  uint8_t z : 1;
} lsm6dsv16bx_tap_thresholds_t;

Correct:typedef struct {
  uint8_t x : 5;
  uint8_t y : 5;
  uint8_t z : 5;
} lsm6dsv16bx_tap_thresholds_t;

Suggested Fix
Update the bitfield definitions to match the datasheet.

Yes, thx. I will commit the modifications asap

authors: Rechenmaschine avisconti


text:
🛑 SPCast / Loadbalancer is down

In 54d7d24, SPCast / Loadbalancer (https://loadbalancer.sp.radio.fm/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SPCast / Loadbalancer is back up in 10a9ec7 after 8 minutes.


text:
🛑 SPCast / Loadbalancer is down

In 727d256, SPCast / Loadbalancer (https://loadbalancer.sp.radio.fm/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SPCast / Loadbalancer is back up in dd4ef04 after 16 minutes.


text:
🛑 SPCast / Loadbalancer is down

In 60c64e0, SPCast / Loadbalancer (https://loadbalancer.sp.radio.fm/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SPCast / Loadbalancer is back up in 7991e46 after 8 minutes.


text:
🛑 SPCast / Loadbalancer is down

In 9f43cd5, SPCast / Loadbalancer (https://loadbalancer.sp.radio.fm/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SPCast / Loadbalancer is back up in 67ba639 after 7 minutes.


text:
Regarding "onlayoutchange" event is not getting correct result on rearrangement of items

As of documentation of "ReactGridLayout",
/**
* Callback so you can save the layout.
* Calls back with (currentLayout) after every drag or resize stop.
*/
onLayoutChange?(layout: Layout[]): void;
Issue is : react grid layout onlayoutchange is not called on rearranging of items
Can you help me to understand which event is used to capture the same ?

Could you provide a repo or codemirror, or perhaps even a snippet of your implementation?

Hey Team,
Sorry I could able to figure out the issue related with the same.
The issue is : onLayoutChange event internally uses "isEqual" method to compare the old and new object.  So in my case it no. of properties to which we added to the new one was always differing due to which the event was continuously getting trigged
so fixed the no. of properties binded to the same
Thanks you

repo: STRML/react-grid-layout


text:
openstack-ardana: fix build pool cleanup

Fixes the cleanup logic used to determine the list
of old stacks in a stack pool which need to be
deleted when a job begins.
The current logic fails to cover cases where the number
of old jobs is lower than the maximum number set for the
job pool. The effect is that a new job deletes all old
stacks that it finds.
Replacing tail with awk helps better encode the logic of
selecting "all but the first X-1, chronologically sorted
stacks" used to determine which stacks need to be deleted.

Your commit message could use a deeper explanation of the symptoms that were occurring and how this change fixes the issue.

(commit message was updated, colleens other question got answered)

authors: cmurphy dirkmueller stefannica

repo: SUSE-Cloud/automation


text:
Change velero entrypoint

For both support install Velero server by helm install and velero install, change the velero entrypoint to /velero as upstream is. Ref https://github.com/vmware-tanzu/velero/blob/master/Dockerfile-velero#L33.
For helm install, it supports to change the entrypoint https://github.com/vmware-tanzu/helm-charts/blob/42f79f4bd7846bed7f4d10395a39ada070a3c33b/charts/velero/templates/deployment.yaml#L51.
For velero install, it uses hardcode entrypoint path

https://github.com/vmware-tanzu/velero/blob/c832e52905dc1b00b2fa4354e37b483dc13cbbe8/pkg/install/deployment.go#L146
https://github.com/vmware-tanzu/velero/blob/c832e52905dc1b00b2fa4354e37b483dc13cbbe8/pkg/install/daemonset.go#L93

Therefore, for support both installation way, change the velero entrypoint to /velero.

@davidcassany Please help on review this :bowing_man:

repo: SUSE/caasp-container-images


text:
Bump EiriniX

Signed-off-by: Ettore Di Giacinto edigiacinto@suse.com

Pump it

authors: jimmykarily mudler

repo: SUSE/eirini-loggregator-bridge


text:
Add functionality to the Transcription section

Checks

[X] This template is only for feature request.
[X] I have thoroughly reviewed the project documentation but couldn't find any relevant information that meets my needs.
[X] I have searched for existing issues, including closed ones, and found not discussion yet.
[X] I confirm that I am using English to submit this report in order to facilitate communication.

1. Is this request related to a challenge you're experiencing? Tell us your story.
I can't upload a large volume of audio files in the "Transcription data" section to create a dataset through the audio file upload window, everything freezes. My file size is 20 GB
2. What is your suggested solution?
Can you add a window in "Gradio" in the "Transcription data" section where I can specify the path to the folder where the audio files are located, this will eliminate the freeze and make it possible to upload a large volume of files to create a dataset.
Thank you
3. Additional context or comments
No response
4. Can you help us with this feature?

[ ] I am interested in contributing to this feature.

I don't have the interface in front of me at the moment, but there is an audio from path checkbox in the gradio training interface if memory serves.
You can then place your files into the dataset subdirectory of your dataset.
i.e. if your dataset is called voice1, the directory would be voice1/dataset
Hope this helps a bit.

Thank


text:
Can i use FFmpeg instead of Av Library

Can i use FFmpeg instead of Av Library.

You can, transcribe function accepts mono 16khz audio arrays

Okay

repo: SYSTRAN/faster-whisper


text:
Add a 10 second option to the timer

I'm an avid player of pool tables with a 10 second countdown, it's something present on the community edition of the table and I'd love to see it on this version as well.
I'm not 100% sure other changes aren't also needed, do tell me if there are or if there's any process you'd like for PRs

closing in favour of https://github.com/Sacchan-VRC/MS-VRCSA-Billiards/pull/4

repo: Sacchan-VRC/MS-VRCSA-Billiards


text:
fix: catch internal errors caused by wrong synthetic nodes created by completion provider

Summary of Changes
Triggering completion could lead to errors like Error: SdsMap:result is not a valid reference id.. These are now caught, since the completion provider inevitably sometimes creates the wrong synthetic nodes before invoking the scope provider.

:tada: This PR is included in version 0.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.10.0
GitHub release

Your semantic-release bot :package::rocket:

repo: Safe-DS/DSL


text:
test: fix tests for check that compares declarations and file extension

Summary of Changes
For the test files that compare the declarations in a module with the file extension:

Fix file extension
Fix expected message

:tada: This PR is included in version 0.2.0 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


text:
using knitmd=FALSE doesn't find md file in current directory

It seems something changed in knitr, so that the generated md file is not in the cache folder, but in the directory where the Rmd file is.
> knit2synapse::storeAndKnitToFileEntity(file="downloads.Rmd", parentId="syn4892835", knitmd = FALSE)
Error in knitfile2synapse(file = file, owner = owner, parentWikiId = parentWikiId,  :
  markdown file downloads.md does not exist at this location: downloads_cache/downloads.md

Ah. This only occurs if you use the built in knit function in RStudio (or otherwise use knit). If using knit2synapse then it stores the md in the cache dir.

Closing, this appears to be working.

authors: jaclynbeck-sage kdaily


text:
Add a chatbot

Want to add a chatbot to our website.

can I use jquery to add a chatbot to this website?

Yes you can

I have added the chatbot but alongwith some existence js code it is not working properly otherwise it is working completely fine after removing preloading function code.
How should I resolve that problem @SahityaRoy ?

After changing and removing preloder you can simply Push your code in your branch

Ok
On Sat, Oct 16, 2021, 10:18 PM Tanwi Kumari @.***>
wrote:

@tanwi1234 https://github.com/tanwi1234 ???
Yeah, I am working on it will update you by tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SahityaRoy/E-Learning-freesite/issues/47#issuecomment-944952160,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARLSWZDOKAAUL66VQ5CKPSTUHGUHPANCNFSM5AI3GCFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

any chatbot service provider available.....?

I want to solve this issue can I work on this

repo: SahityaRoy/E-Learning-freesite


text:
🛑 Nostr Relay - wss://nostr.fly.dev is down

In a575484, Nostr Relay - wss://nostr.fly.dev (https://nostr.fly.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nostr Relay - wss://nostr.fly.dev is back up in 6d0fae3.

repo: Sakhalinfox/orangepilldevuptime


text:
Add Logo image to Grant application

OVERVIEW
Add logo image to Grant application record and display on the Grant document, show Logo on Exported PDF
ACCEPTANCE CRITERIA
Display logo on the exported Grant documents PDF or Word documents
OUT OF SCOPE

Added as part of Feature #50 and #70

repo: Salesforce-org-Impact-Labs/GrantGuides


text:
[BUG] B2C_INSTANCENAME validator is wrong

Describe the bug
The validator says that B2C_INSTANCENAME "must start with a letter -- and only contain letters and numbers"
In a world of On Demand Sandboxes this is not true.
All of my sandbox names of of the format [4 letter REALM_ID]-[3 digit number].dx.commercecloud.salesforce.com.
These names are automatically assigned.
To Reproduce
Steps to reproduce the behavior:

Create a SFCC ODS
follow the steps to set up the B2C Commerce Configuration Properties
Run the validations.  Especially 'npm run crm-sync:b2c:verify'
notice the validation error that is wrong.

Expected behavior
Not to have a validation error on a system generated name.
Screenshots

Your local environment details:

Node version (node -v): v12.21.0
NPM version (npm -v): 6.14.11
SFDX version (sfdx -v) sfdx-cli/7.194.1 win32-x64 node-v18.15.0

Your remote environment details:

Salesforce B2C Commerce version: Version: 23.10 Last Updated: Oct 9, 2023 (Compatibility Mode: 22.7)
Salesforce Core version: [e.g. 52]

Additional context
Add any other context about the problem here.

N/m.  I just got to the step where it is used.  This is a SFDC requirement not and SFCC requirement.

Need a comment to close.


text:
Remove lodash and bluebird.

Like it says on the tin. Only one minor code change (in two files).
Description

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Don't forget to update the package-lock.json file. :)

Don't forget to update the package-lock.json file. :)

All of the changed package-lock.json files have already been committed! 😉

authors: kevinxh wjhsf

repo: SalesforceCommerceCloud/pwa-kit


text:
Setup Travis CI and update builds badge.

\cc @stash-sfdc
It would be nice to have this done, but I don't have permissions to do that.

OK, I'll look into this. I need to do it for all the modules I brought over.

OK, should be done!

authors: inikulin stash-sfdc

repo: SalesforceEng/tough-cookie


text:
error on gift entry for npsp_payment_type__c

Getting an error on gift entry trying to Process Batch. (attached)
Note - the auto-creating payments is disabled
I've verified the mapping and npsp_Payment_type__c is only mapped once (attached)
I've deleted that field, tried to do a batch, and got the same error
It worked fine on October 2021, but tried again in December 2021 and getting the error.
I've tried different batches, still getting errors

.

We do not provide direct support of issues here in Github. Please open a support case for further troubleshooting assistance. Thanks!

repo: SalesforceFoundation/NPSP


text:
Fixes

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

Merged into #7178


text:
[DO NOT MERGE] Placeholder for 234

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Asteroids DoD document to see any additional details for the items below

[ ] Any net new LWC work has Sa11y tests & 50% or above lines JEST test coverage
[ ] CRUD/FLS is enforced in Apex
[ ] Permission sets are updated to account for CRUD|FLS|Tab|Classes
[ ] Field sets are updated to account for new fields
[ ] UX approval or UX not necessary
[ ] Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name (https://github.com/SalesforceFoundation/PMM/pull/303)
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer
[ ] QA

[ ] PR contains draft release notes
[ ] QE story level testing completed

Unaggregated Pull Requests

[Robot] Switch fieldsets on bsdt [PR526]
New Program Engagement from Participant Adder [PR538]
Constrain cohort options by program in New Program Engagement (234) [PR539]
New Program Engagement modal: New Contact layer [PR540]
Final adjustments and fixes on New Program Engagement modal [PR541]

Thanks for the contribution! It looks like @kselvocki is an internal user so signing the CLA is not required. However, we need to confirm this.

@AndersonTarren - Because I no longer have access to Google Docs, I can't complete that linked form.

authors: jjbennett kselvocki

repo: SalesforceFoundation/PMM


text:
Possible to pass in a constructor argument to a class when using CustomJS?

Is it possible to pass in a parameter to a constructor in a class when using CustomJS?
I don't use JS that much, so apologies if this is silly/obvious to you :)
I would like to pass in the DataView dv object to the class to avoid having to pass in dv to any functions that need to use it, so that is the use case.
I have tried doing this but get errors if I do anything except
const {ClassNameOnly} = customJS;
Many thanks :)

You have a good instinct! Generally speaking, in JS that would be a better way to do it. However, until Obsidian can support regular imports on mobile (this is likely more difficult than it sounds), I'm forced to use eval which is why the customJS usage is so restrictive in general (one class per file, etc).
All that to say, it isn't possible to allow users to pass anything to the constructor directly. A possible way to support common plugins like dataview would be to allow users to set whether they want it passed in the settings. But I don't have the time to test it out right now unfortunately. If I find time to try it later I will, but for now you'll have to pass it to each method as you mentioned.

Hi, you can set instance fields via setters.
class Foo {
    plusOne = nul

    setPlusOne(myField) {
        this.plusOne = plusOne
        return this
    }

    getTwo() {
        return 1 + this.plusOne
    }

   getThree() {
        return this.getTwo() + this.plusOne
   }
}

Then use it like:

const fooInstance = customJS.Foo.setPlusOne(1)

fooInstance.getTwo() // returns 2

fooInstance.getThree() // returns 3

Thanks @jbiros91 ! That's a cool idea. Adds one line of boilerplate to a dataviewjs block, but saves you from having to pass  objects to every method. Seems like a good compromise.

Another way is to use the class as a module or name-space and define classes as fields with the class expression.
class MyModule {
  MyClass = class {
    constructor(param) {
      this.myField = param
    }
  }
}

Usage:
const { MyModule } = customJS
const myInstance = new MyModule.MyClass('foo')

You can even inherit from classes within your module (define super-classes before you extend from them; there's no hoisting here AFAIK)

A little more involved example using Templater's dynamic command:
// my-module.js
class MyModule {
  MyClassA = class {
    constructor(param) {
      this.myField = param
      console.debug(
        `${this.constructor.name} constructor called with param-value ${param}.`,
      )
    }
  }

  MyClassB = class extends this.MyClassA {
    constructor(param, otherParam) {
      super(param)
      this.myOtherField = otherParam
      console.debug(
        `${this.constructor.name} constructor called with otherParam-value ${otherParam}.`,
      )
    }
  }

  constructor() {
    console.debug('MyModule initialized.')
  }
}

// my-module.test.js
class MyModuleTest {
  run() {
    const { MyModule } = customJS

    const instanceA = new MyModule.MyClassA('foo')
    const instanceB = new MyModule.MyClassB('bar', 'baz')
  }
}

<!-- templater-test.md -->
MyModule Test <%+ customJS.MyModuleTest.run() %>

Expected console output (level verbose/debug):
MyModule initialized.
MyClassA constructor called with param-value foo.
MyClassB constructor called with param-value bar.
MyClassB constructor called with otherParam-value baz.

Ah the nested classes are a great idea, I'll leave this issue open so it's easier for others to find.

Thanks all for the great input!

Arguably a bit odd to advertise a "competing" OSS project in an issue, but I don't actually use Obsidian anymore and have just been maintaining this for the users so it's cool. Gonna close this issue though since the conversation has now strayed from the original focus.

I was thinking maybe we'd merge (the good bits) of mine into yours -- didn't intend to steamroll you.
Thanks for maintaining your project, despite stepping away from Obsidian :pray:

Definitely open to collaboration, I just merged in a PR from someone a week or two ago. Exciting to know people are using the plugin!
Feel free to open a new issue and we can discuss how the two plugins may be able to work together.