JS error translations not working (Strapi >= 4.1.4)

I've been trying to get this plugin working, installing going well. The plugin is there and enabled, the fields appear in the editor. The copy function from other language does work but translation feature from a source language isn't.
When I trigger a translation i get an console error:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘data’)     at main.50a6bd34.js:2:1487884     at c (main.50a6bd34.js:2:2132705)     at Generator._invoke (main.50a6bd34.js:2:2132493)     at Generator.next (main.50a6bd34.js:2:2133134)     at t (main.50a6bd34.js:2:562)     at u (main.50a6bd34.js:2:773)

I did run npm audit as well which returns:
ansi-regex  >2.1.1 <5.0.1 Severity: moderate  Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw fix available via npm audit fix --force Will install<EMAIL_ADDRESS>which is a breaking change node_modules/plop/node_modules/ora/node_modules/ansi-regex   strip-ansi  4.0.0 - 5.2.0   Depends on vulnerable versions of ansi-regex   node_modules/plop/node_modules/ora/node_modules/strip-ansi     ora  2.0.0 - 4.0.2     Depends on vulnerable versions of strip-ansi     node_modules/plop/node_modules/ora       plop  2.2.0 - 2.7.6       Depends on vulnerable versions of ora       node_modules/plop         @strapi/generators  *         Depends on vulnerable versions of plop         node_modules/@strapi/generators           @strapi/plugin-content-type-builder  *           Depends on vulnerable versions of @strapi/generators           node_modules/@strapi/plugin-content-type-builder           @strapi/strapi  *           Depends on vulnerable versions of @strapi/generators           node_modules/@strapi/strapi             strapi-plugin-deepl  >=0.1.3             Depends on vulnerable versions of @strapi/strapi             node_modules/strapi-plugin-deepl
Any ideas here on how to get it working?

Just fixed it in adc263705c9e107a0e31aa6b2202420736dfbaf3 and the fix is also included in the new version (0.3.3) of the plugin.
The bug was that the function formatComponentData was renamed to formatContentTypeData in the strapi helper plugin in version 4.1.4

Hello,
now I am using Strapi 4.1.5 and I am getting the following error:
TypeError: (0 , r.formatContentTypeData) is not a function
I assume it has something to do with this?

@sargreal Please excuse my request, the Admin Panel did somehow not rebuild correctly, everything works now!

Hello there,
Im using Strapi v4.1.3 and deepl plugin v0.3.5. Set up the config with free api key from the deepl account but I still get the same error as described in the first post. Any recommendations for solving this problem?

Same error as first message is present again in:
"@strapi/strapi": "4.5.5",
"strapi-plugin-translate": "1.0.0",
"strapi-provider-translate-deepl": "1.0.0"

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'data')

After further testing turns out that the error only appears if there is a "has one" relation field set to translate.

@anatolykopyl can you please create a new issue for this, with minimal conten-type example?

@sargreal created issue #78


fix: Fix JS syntax error and compile latest version of app.js

An upgrade to phoenix_live_view requires recompiling the app.js file.
Closes #72
Added notes:

The updated JS appears to be backwards compatible for apps that haven't yet upgraded to LV 0.20.
I tested this by force-downgrading the LV dependency in this repo to 0.19.5, kept the recompiled JS file, and the dev app still seems to work as normal with the 0.20.0-recompiled JS file.

🚀 Thank you for your contribution! 🚀


Added my pixel

Checklist

[ x] I ran npm test locally and it passed without errors.

[ x] I only edited the _data/pixels.json file.

[ x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x ] I acknowledge that all my contributions will be made under the project's license.

Hey @LostCoder11 it seems like you already have a pixel merged so I'll close this one as a duplicate. Thank you for your contribution!


IE 11 issues with 0.9.2

Hi All,
I have just grabbed the latest (0.9.2) and have hit an issue with IE11.
in the validate-binding-behavior bind method
the target is undefined and blows up (no null checking)
quick fix >>
var target = this.getTarget(binding, source);
if (target === undefined || target === null)
      return;

Another issue regarding undefined objects in the unbind method
  if (binding.validationController !== undefined && binding.validationController.unregisterBinding != undefined)
    binding.validationController.unregisterBinding(binding);

Yeah, I'm seeing lots of IE only errors with the latest validation module.  I'll see about getting a repro together

Yes, I've had an IE problem with return controller.view.firstChild.parentElement;  changing it to return controller.view.firstChild.parentNode; seemed to fix it.

The root issue seems to be in the getTarget method of the validate binding.
In my testing this fixes the issue for IE where the getTarget method was returning undefined.

@jdanyow could be that the other fix suggested by @huw489 is better. To be honest I didn't really understand the intention of the controller part of the getElement method

@maverix the getTarget method's job is to get the DOM element associated with the data-binding.  Most of the time it's pretty easy... it's the binding's target but sometimes the binding's target is an aurelia custom element, which is a javascript class, so we need to use the controller to locate the actual DOM element.

now there's a comment in the code explaining what it does ^^^

Thanks @janus007. i'm really enjoying working with Aurelia.  Its the first time that javascript development has felt more productive than my traditional server-side MVC stack


Convert Json::Object to use HashMap instead of BTreeMap

Fixes #56
One side effect of this, is Json no longer derives PartialOrd since
HashMap doesn't derive it. That said, I don't really see why it should
derive it in the first place.
[breaking-change]

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

I think I would personally like to hold out and hear some more opinions on #56 before moving on this. Some more details here as well: https://github.com/rust-lang/rustc-serialize/issues/56#issuecomment-74463112


🐛Cherrypick live-iso option to Image's DiskFormat for v1a5 in release-0.5

This PR will add the live-iso option for v1a5 in release-0.5 branch and changes are done according to main branch https://github.com/metal3-io/cluster-api-provider-metal3/pull/527

/test-v1a5-ubuntu-integration

I think the yaml(crds) should be generated as well. There should be a make target.

/approve


Data mappers refactoring

In this refactoring, I've extracted a common logic from AttributesDataMapper and OptionsDataMapper, covered it with more tests, and arranged it in services. Enjoy 🖖

@loevgaard according to our conversation, I've lowered the abstractness of some services, also moved attributed and options mapping to metadata. Should be better now 🖖 let me know if you have any more doubts


encode_image() broken after latest commits

Ubuntu 22.04, gtx 2080 and m40 both result in an all NaN tensor when running the encode_image() function.
device, dtype = detect_device()
model_id = "vikhyatk/moondream1"
tokenizer = Tokenizer.from_pretrained(model_id)
moondream = Moondream.from_pretrained(model_id).to(device=device, dtype=dtype)
moondream.eval()
image = Image.open("/test.png")
image_embeds = moondream.encode_image(image)

A temporary fix is :
Moondream.from_pretrained(model_id, revision="1e62d51745be03c0d3a5c582afcada6c1f98f454")

No Errors were printed.

oh no! looking into this

After no one else chimed in having the same problem I got suspicious. And lo and behold, the issue was mostly just me being dumb. Moondream.from_pretrained(model_id) always gets the newest model. And apparently this new model had a different architecture in regards to the encoder? So it REQUIRED the most up to date version of the repository, with the new encode_image function. Which I had not git pulled.
I think in the future it would be helpful if breaking changes in the model used a different version numbered name so existing code doesn't break from one day to the next. (Some people may use modified forks of this repo for example, and huggingface will download the new model without asking). But at the same time I really should have tried pulling before opening an issue :sweat_smile:

Apologies for this, lesson learned on my part! Will make sure to bump version if there's ever a non-backward compatible change.


Separate UI-related end-user docs from commands section

Summary
Currently the Using /jira commands page has information about using the modals shuffled into the command explanations. This PR separates the two sections into different pages.

Codecov Report

Merging #780 (bd39322) into master (154646c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #780   +/-   ##
=======================================
  Coverage   32.38%   32.38%
=======================================
  Files          52       52
  Lines        5361     5361
=======================================
  Hits         1736     1736
  Misses       3423     3423
  Partials      202      202

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 154646c...bd39322. Read the comment docs.

@justinegeffen Do these docs-related PRs need to be cherrypicked into the docs branch, or should they just go into the docs branch in the first place?

@justinegeffen I think is ready to merge, though I'm not sure what branch this should be targeting. Should we avoid using master for the docs PRs?

@justinegeffen After merging this PR, the docs don't show the newly added interacting-with-forms page. Do you know why this might be the case?


fix: js name parsing - reading subsection ids >= 128 and error handling

Wrapping most of it with a try catch

Great catch, I thought you could read regular integers as LEB128 as well but good to know that can cause issues!
Out of curiosity, did you encounter an issue, or was this something you just realized while looking at the code?

Updated PR description.

Great catch, I thought you could read regular integers as LEB128 as well but good to know that can cause issues!

With LEB128 parsing If the high bit was set on the subsection id, part of the subsection length would accidentally be parsed into it. Right now I don't think anyone's used >= 128 subsection ids in the name section, but nothing is stopping them.

Out of curiosity, did you encounter an issue, or was this something you just realized while looking at the code?

I didn't encounter any issue, I just heard you mention reading the subsection id as a LEB128 in your teamlog so I dug into the code to see if it was left like that. The other changes are just paranoia about corrupt modules being passed into the observe sdk and it being tricky to track down.

Great work, thank you!


Settings Sync landing page image is missing

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62
OS Version: Windows 10

Steps to Reproduce:

Sign in using settings sync

Is this a settings sync extension that you have installed, or the built-in Settings Sync feature?

Yes this is coming from Settings Sync extension, please file issue against that extension.


How to receive sent data?

I'm sending data like this:
await watch.sendMessage({
  "type": "test",
  "data": "Hello from Flutter",
});

I'm trying to receive it like this:
class CommunicationService : WearableListenerService() {
    override fun onMessageReceived(messageEvent: MessageEvent) {
        super.onMessageReceived(messageEvent)
        Log.d(TAG, "onMessageReceived: ${messageEvent.path}")

        // Process the received message
        handleMessage(messageEvent.path, messageEvent.data)
    }

    private fun handleMessage(path: String, dataBytes: ByteArray) {
        val data = String(dataBytes, Charsets.UTF_8)
        val data2 = dataBytes.toString()
        Log.d(TAG, "data: $data")
        // Handle the message based on the path and data
    }

    companion object {
        private const val TAG = "CommunicationService"
    }
}

The result is something like this (from logcat):

data: ��??sr??java.util.HashMap���`�??F??
loadFactorI??	thresholdxp?@??????????w????????????t??datat??Hello from Fluttert??typet??testx

Apparently you can write something like this to convert it:
/**
 * Interprets the byteArray as a Map<String, Any>.
 * If that's not possible, returns null.
 */
fun ByteArray.asMap(): Map<String, Any>? {
    val byteArrayInputStream = ByteArrayInputStream(this)
    val objectInputStream = ObjectInputStream(byteArrayInputStream)

    return try {
        val obj = objectInputStream.readObject()

        if(obj !is Map<*, *>) throw Exception()
        @Suppress("UNCHECKED_CAST")
        obj as Map<String, Any>;
    } catch (e: Exception) {
        e.printStackTrace()
        null
    } finally {
        objectInputStream.close()
    }
}

...

val data = messageEvent.data.asMap()

The idea is you use flutter on both sides, but I should probably expose those conversion methods so people doing native android can use them without copy/paste

Actually nevermind you wouldn't have access to the flutter plugin on the native android side 🙃. Maybe I should make a native android wrapper, but that's a task for another day.

Yeah, I found the conversion methods and after copypasting them the serialization and deserialization works.
Using flutter for the wear os app isn't really an option. Battery life is extremely limited and we want to use the native widgets due to their looks and performance.
It would be nice to have a section in the readme about how to send and receive data in a native wearOS app.


Setting height to 100%

Hi jasper07,
I was about to write you an issue.
Actually I have solved it viewing the demo "directionstestwaypoints".
Maybe it is a word worth in your README.file that to achive a 100% responsive map it is needed a special css config for ma1-map. :-)
Kind regards,
Alex

contributions welcome

Hi @gepparta & @gepparta ,
I have tried adding css for 100% height, but the map disappears if I use the below css code.
#__xmlview4--map-map, #__xmlview4--map{
	height: 100% !important;
}

can you tell me how to override the element style height of 20em, so that I can fit it in a VBox.
Thanks
Prateek


Issues with Hardware Metrics semantic conventions

What are you trying to achieve?
Follow recommendations on: https://opentelemetry.io/docs/specs/semconv/system/hardware-metrics/
What did you expect to see?
Consistent and implementable specification.
Additional context.
Ran across following issues when trying to map GPU metrics to the semantics...
Non-implementable / unspecified items:

Single firmware_version won't work:

Devices have multiple types of firmware (display, media, scheduling/power management etc)

hw.errors have just hw.error.type attribute, although:

Errors can be correctable, uncorrectable (data lost), or fatal (functionality lost, at least reset needed to recover)
Errors can originate from different parts of the SW stack (FW, kernel, userspace driver)
Errors can originate from different parts of the device HW (display, media, compute, 3d etc)
=> I suggest adding .category attribute, similarly to Level-Zero spec:

https://spec.oneapi.io/level-zero/latest/sysman/api.html#zes-ras-error-cat-t

Inconsistencies:

hw.gpu.power vs. hw.power{hw.type="gpu"} confusion

If both are valid, why there's no hw.gpu.energy to match hw.energy{hw.type="gpu"}?

Common HW name & id attributes vs. GPU model & serial attributes

Should all of these be provided despite overlap?

Why vendor attribute is used for GPU devices, but manufacturer for (host) device: https://opentelemetry.io/docs/specs/semconv/resource/device/
Inconsistent attribute examples for GPU metrics missing from spec:

system.cpu.frequency vs. hw.cpu.speed
.utilization vs. .*_ratio [1] suffix for things like (frequency) throttling
whether in addition to base metric, one should provide .utilization / .*_ratio, or .limit value?

[1] Used e.g. in: https://opentelemetry.io/docs/specs/semconv/system/hardware-metrics/#hwfan---fan-metrics
PS. Summing errors is not very meaningful (rate is more interesting), but maybe additional all category could be provided just for indicating whether there are any errors (within query period) from given HW?  It could be useful both  when more fine-categories are missing, and in addition to them.

FYI @bertysentry

@eero-t Thank you for the feedback, give me a few hours to answer your questions. We will address all issues!

Thank you for the feedback, @eero-t!
I will try to answer your questions and we will discuss parts what will require an update of the conventions to be able to cover your use cases.

Single firmware_version won't work:

Devices have multiple types of firmware (display, media, scheduling/power management etc)

Unfortunately, we cannot include all cases of firmware sub-components in the specifications for metrics semantic conventions. However, I know the group is working on a different type of entity (like a Resource) where one could put these kind of attributes describing the monitored component, without polluting the timeseries with too many attributes.
In the meantime, we recommend using the firmware_version attribute to put all necessary information. It's a free format string, it doesn't need to be exactly x.y.z. You set this attribute to: display 23.1; media 1.0.00; scheduling 2.13A.

hw.errors have just hw.error.type attribute, although:

Errors can be correctable, uncorrectable (data lost), or fatal (functionality lost, at least reset needed to recover)

Errors can originate from different parts of the SW stack (FW, kernel, userspace driver)

Errors can originate from different parts of the device HW (display, media, compute, 3d etc)

=> I suggest adding .category attribute, similarly to Level-Zero spec:

https://spec.oneapi.io/level-zero/latest/sysman/api.html#zes-ras-error-cat-t

The hw.error.type is a free format string that you can set to any applicable value.

[!TIP]
As this is an UpDownCounter metric, we recommend to make sure that one error is not counted several times (e.g. once with hw.error.type="correctable" and once with hw.error.type="display"). Most users will first display the total number of errors as sum(hw.error{hw.type="gpu"})` before breaking down by error type.

hw.gpu.power vs. hw.power{hw.type="gpu"} confusion

This is totally an oversight. The hw.gpu.power metric must be removed from the semantic conventions. Please use hw.power{hw.type="gpu"}.

Why vendor attribute is used for GPU devices, but manufacturer for (host) device: https://opentelemetry.io/docs/specs/semconv/resource/device/

That's a very good point. In hardware metrics, we've preferred vendor over manufacturer, because it's easier for the end-user to identify the vendor. Example: the vendor of a disk may be "Dell-EMC", while the manufacturer is "WD". Both have value, but in case of a failure, the end user is more likely to contact the vendor rather than the real manufacturer.
We're totally open to discussion on this point. Again, this may be better implemented as part of the new "entity" thing (I can't retrieve the link to the proposed spec for this).

system.cpu.frequency vs. hw.cpu.speed

Are you suggesting we add hw.gpu.speed? It's probably a good idea! What speed would we be reporting? (per core, memory, etc.)
WRT to frequency or speed I agree we should use the same terminology everywhere and use the term that the industry commonly uses.

.utilization vs. .*_ratio [1] suffix for things like (frequency) throttling
whether in addition to base metric, one should provide .utilization / .*_ratio, or .limit value?
[1] Used e.g. in: https://opentelemetry.io/docs/specs/semconv/system/hardware-metrics/#hwfan---fan-metrics

In OpenTelemetry, *.utilization metrics are usually used in conjunction with corresponding *.usage and *.limit. In the case of fan speeds, some fans don't indicate their real speed in rpm and their maximum speed. Also in this case hw.fan.speed.utilization was really improper.

PS. Summing errors is not very meaningful (rate is more interesting), but maybe additional all category could be provided just for indicating whether there are any errors (within query period) from given HW? It could be useful both when more fine-categories are missing, and in addition to them.

For proper aggregation and rate calculation, it is important (when possible) to store the total number of errors and then let the timeseries database calculate the rate for you on a period of time chosen at query time.
Thank you again for the thorough review. We will start by fixing the hw.gpu.power which is not supposed to be here. For other suggestions, we will need the input from the rest of the team:

system.cpu.frequency vs. hw.cpu.speed
vendor vs manufacturer
Add hw.gpu.speed?

The hw.error.type is a free format string that you can set to any applicable value.

Not really the answer I was expecting... :-/

@bertysentry I mean, different categories of errors require different responses, and from different people:

User-space (driver) errors: automatically blacklist given deployment / image version => until service developer updates it
Kernel & FW errors: Taint device, drain node, update kernel/FW and reboot => cluster admin can do it remotely
HW & some FW errors: Taint/drain node, replace HW, power up again => needs HW admin local access

Semantics for such differences should be explicitly specified, and separate from whether given error is correctable or uncorrectable (i.e. what's the severity of given error category), not included in some "freeform" string.
Otherwise one cannot group the errors meaningfully over different device types (are there e.g. errors that require on-site admin presence).
And please comment also on this:

Common HW name & id attributes vs. GPU model & serial attributes

Should all of these be provided despite overlap?

The hw.error.type is a free format string that you can set to any applicable value.
@bertysentry I mean, different categories of errors require different responses, and from different people:

User-space (driver) errors: automatically blacklist given deployment / image version => until service developer updates it
Kernel & FW errors: Taint device, drain node, update kernel/FW and reboot => cluster admin can do it remotely
HW & some FW errors: Taint/drain node, replace HW, power up again => needs HW admin local access

Semantics for such differences should be explicitly specified, and separate from whether given error is correctable or uncorrectable (i.e. what's the severity of given error category), not included in some "freeform" string.
Otherwise one cannot group the errors meaningfully over different device types (are there e.g. errors that require on-site admin presence).

@eero-t Don't worry, we totally understand there are different types of errors that need different responses. That's the reason of the hw.error.type attribute, to cover different types (or categories) or errors. Error types are not just "correctable" or "non-correctable", these are just mere examples of error types for GPUs. The semantic conventions allow you to extend to any type or category of errors as required. This allows the instrumentation to be exhaustive, while the spec remains flexible and future-proof.
Actually, we may change hw.error.type to simply error.type in the future. error.type is the only required attribute for errors, in general, in Otel semantic conventions.

Common HW name & id attributes vs. GPU model & serial attributes

Should all of these be provided despite overlap?

serial_number and id are not necessarily the same. If they are same in your instrumentation, you can drop serial_number, as it's not a required attribute (only "recommended")
Same for name and model: you can drop model if it's always the same as the name attribute in your instrumentation. Simply make sure to always follow the same logic for all devices.

@eero-t Don't worry, we totally understand there are different types of errors that need different responses. That's the reason of the hw.error.type attribute, to cover different types (or categories) or errors. Error types are not just "correctable" or "non-correctable", these are just mere examples of error types for GPUs. The semantic conventions allow you to extend to any type or category of errors as required. This allows the instrumentation to be exhaustive, while the spec remains flexible and future-proof.

@bertysentry My point was that those items are semantically orthogonal and should therefore have separate attributes in the semantics spec.  Current spec seems to be confused about the role of the errors .type attribute(s) which I think is also is a good indication that it should be split into multiple ones.
For example:

.severity: correctable, uncorrectable (data loss), fatal (functionality loss)
.type: type / category of the error; timeout, memory-parity-error, hw-programming-error etc
.location / .origin / .cause / .whatever: e.g. http-endpoint, display (part of GPU with some memory), compute (GPU pipeline setting)

Actually, we may change hw.error.type to simply error.type in the future.

Yes, please!  Getting rid of overlapping & redundantly differing parts in the attribute names, and using already existing common ones, makes both the spec, and the metrics output compliant with it, more readable.

error.type is the only required attribute for errors, in general, in Otel semantic conventions.

Hm. Instead of stuffing semantically different types of error attributes as free-from text into single .type attribute (your recommendation), this page recommends to:

Use a domain-specific attribute
Set error.type to capture all errors, regardless of whether they are defined within the domain-specific set or not.

?


onDidChangeBreakpoints event not triggered by adding function breakpoints

VSCode Version: 1.49
OS Version:

Steps to Reproduce:

add function breakpoint in BREAKPOINTS section by entering the function name
onDidChangeBreakpoints event not triggered, no log printed under test code

Does this issue occur when all extensions are disabled?: Yes
Hi, I'm developing my own debug extensions. I'd like to use onDidChangeBreakpoints event to show breakpoint info message on screen. Seems it works well with source breakpoints when clicking on editor, but the event doesn't work when it comes to Function breakpoints cases. VSCode debugging docs shows the only way to add function breakpoints is by using BREAKPOINTS section. Would you please take a look at this? Or is there any other event triggered by adding function breakpoints in the section? Or any workaround?  Thank you. @weinand @isidorn

it's a issue

it's a issue

@weinand let me know if you would like to investigate this.
I just quickly checked, and we are sending a onDidChangeBreakpoints when a new function breakpoint is added.
Technically we send a onDidChangeBreakpoints first when a new function breakpoint is added without a name, once user enters the name in the input box we send another event.

@weinand let me know if you would like to investigate this.
I just quickly checked, and we are sending a onDidChangeBreakpoints when a new function breakpoint is added.
Technically we send a onDidChangeBreakpoints first when a new function breakpoint is added without a name, once user enters the name in the input box we send another event.

@isidorn yes please, it would be great if you could investigate. Thanks!

@isidorn yes please, it would be great if you could investigate. Thanks!

Since adding a function breakpoint for VS Code is a two step process, first the empty input is created and then the name gets set.
Thus VS Code first sents an BreakpointUpdate event with the added for the new function breakpoint, and then another event with the updated once the name gets set.
I have just made sure this works, and have also removed an error being thrown (since it was checking if the functionName is truthfull, which is not true since exception breakpoints are first set with an empty "" name)
@kevingty please get latest vscode insiders from tomorrow and try it out
@weinand if we want to change this two event being sent out than the mainThreadDebugService would need to have a bit of smartness to not sent the first added event, and the next update to transform to add. Though I did not do this for now as I am not sure it is really necessery

Since adding a function breakpoint for VS Code is a two step process, first the empty input is created and then the name gets set.
Thus VS Code first sents an BreakpointUpdate event with the added for the new function breakpoint, and then another event with the updated once the name gets set.
I have just made sure this works, and have also removed an error being thrown (since it was checking if the functionName is truthfull, which is not true since exception breakpoints are first set with an empty "" name)
@kevingty please get latest vscode insiders from tomorrow and try it out
@weinand if we want to change this two event being sent out than the mainThreadDebugService would need to have a bit of smartness to not sent the first added event, and the next update to transform to add. Though I did not do this for now as I am not sure it is really necessery

@isidorn Thanks a lot.  Which branch or commit did you push the fix to ? Can it be viewed ?

@isidorn Thanks a lot.  Which branch or commit did you push the fix to ? Can it be viewed ?

The commit is traced in this issue, it is pushed on master.
Here's the commit https://github.com/microsoft/vscode/commit/543af670531f1b1c13e30c840c233d14602f5da4

The commit is traced in this issue, it is pushed on master.
Here's the commit https://github.com/microsoft/vscode/commit/543af670531f1b1c13e30c840c233d14602f5da4

It works. Thanks. @isidorn

It works. Thanks. @isidorn

Lovely thanks, adding verified label.

Lovely thanks, adding verified label.


Jblas SVD incorrect result

SVD gives incorrect V and U* when I used it on a 434 x 32 matrix. When I compare (V * S * U^T) with original matrix, the result is way off. Comparing with matlab result, lots of entries of V appears to have the wrong sign, although abs values of those entries seems to be correct. Also singluar values appears to be OK.
I reported this on Jblas, but I thought people who are using clatrix should know.

Just realize it U is transposed, different from matlab.


segmentation fault in benchmark.lua

OSX latest LuaJIT 2.1.0-beta3
luajit benchmark.lua
Benchmarking 	1000000 times.
cjson encode	 Elapsed: 	1.818497s
capnp encode	 Elapsed: 	0.104733s
cjson decode	 Elapsed: 	2.268937s
[1]    52312 segmentation fault  luajit benchmark.lua

I'm experiencing the same issue on Linux 5.3.5. (tested with LuaJIT 2.1.0-beta3 and LuaJIT master branch)
luajit benchmark.lua

Benchmarking 	1000000 times.
cjson encode	 Elapsed: 	4.262157s
capnp encode	 Elapsed: 	0.053436s
cjson decode	 Elapsed: 	4.290664s
Segmentation fault (core dumped)

@calio  Can you please help?


Medium icon versions

Hey, this is an awesome repo! Many thanks.
Are there any plans to add the medium/non-solid versions of the icons?

Hey, this is an awesome repo! Many thanks.
Are there any plans to add the medium/non-solid versions of the icons?

Already available suffixed with "Outline". Or do you mean something else?
https://www.github.com/impulse/react-native-heroicons/tree/master/src%2Ficons

Ah, awesome! If you allow pull requests, i would love to make this clear in the README 👍

Made a pull request with updates to the README: #4

Merged in 035fc01210bcb034b7c2bb32c5a3c18c7fd1e628


Incorrect completion commits

Basic info

OS: [Any]
VSCode version: Latest
Extension version: Latest

Further Information
When creating a new variable/function, if inserting parenthesis, it autocompletes to another item.
This is due to #162 .

@BoomShotKapow 👀

Love it

I'll look into it now, my apologies.


Coming back from Full screen in Landscape, gets the app to portrait.

I am using ImageSlideshow in UIScrollView. It works fine in the portrait mode. But when I rotate to landscape mode and then go to full screen to view images, when I tap cancel and come back, the whole app gets rotated to portrait even though I am holding device in landscape mode. Also half of the view is black. Please view the simulator screen shot for the reference. Facing same issue on the device as well.

It will be helpful if you share an example project of causing this.

I using this library in a very simple way. In story board I am using autolayouts. Sliding view has constraints of leading and trailing space to 60 & height equal to 291. Below is the code for image sliding: imagesSV.backgroundColor = UIColor.white         imagesSV.slideshowInterval = 5.0         imagesSV.pageControlPosition = PageControlPosition.insideScrollView         imagesSV.pageControl.currentPageIndicatorTintColor = UIColor.lightGray         imagesSV.pageControl.pageIndicatorTintColor = UIColor.black         imagesSV.contentScaleMode = UIViewContentMode.scaleAspectFill         imagesSV.currentPageChanged = { page in //            print("current page:", page)         }         imagesSV.contentScaleMode = .scaleAspectFit         // try out other sources such as afNetworkingSource, alamofireSourceorsdWebImageSourceorkingfisherSource`
imagesSV.setImageInputs(localSource)
    let recognizer = UITapGestureRecognizer(target: self, action: #selector(PDSummaryVC.didTapImagesSlider))
    imagesSV.addGestureRecognizer(recognizer)

func didTapImagesSlider() {
    imagesSV.presentFullScreenController(from: self)
}`

May be it's autolayout or something else which u might make the device which force to landscape -> portrait. If you are doing that, please refer to this question =>
http://stackoverflow.com/questions/28938660/how-to-lock-orientation-of-one-view-controller-to-portrait-mode-only-in-swift
Try show us the current state using : http://www.cockos.com/licecap/
or it will be helpful if you share your example project so we can look into your storyboard or codes


Steam_Language

At the moment steam is sort of inconsistent in providing default locale. That cookie might help a little.

Where does this cookie come from? I don't see it on steamcommunity.com when logged into my account

Unfortunately, I don't know the answer to this, but if you navigate through one/two pages you will notice it appear.
Because it's not obvious
Yet this cookie is present, and you can change it manually calling POST https://steamcommunity.com/actions/SetLanguage/ with language=english, sessionid={sid} (It is being called when you access Change language in profile name dropdown)

Eh, I can't imagine this hurting anything, so I'll merge it


dash.js

dash.js verwenden, kommerzielle Player entfernen

Done. Viblast and Bitmovin were removed and dash.js was added


Change checkbox to a checkmark instead of a solid fill

Context (What would this enhancement solve that is not possible today?)
It looks kinda weird on the post create page that the checkbox for making the post a draft is a solid fill instead of a checkmark

Ideal solution (What would you like to see implemented?)
This is how bootstrap does it. We should try to emulate this functionality

@jsolly , I'm having issues working on this cos I can't access the post-create page. The link was removed from the navbar

@jsolly , I'm having issues working on this cos I can't access the post-create page. The link was removed from the navbar

I also tried accessing the page by typing it manually in the browser, but I'm forbidden access

You have to be logged in. If you run the latest migrations, there should be an account admin/admin

Despite implementing various recommended solutions, the checkbox styling remains non-functional
The following steps were taken to address this issue:

Utilization of custom CSS and HTML adjustments in accordance with recommended guidelines.
Attempting multiple rendering approaches for the 'draft' field individually and in conjunction with other form fields.
Exploring Django's form rendering capabilities while targeting the 'draft' field for customized styling.

@freedompraise there was some dumb CSS styling that I put on it when I was migrating away from Bootstrap awhile back.

Fixed in https://github.com/jsolly/awesome-django-blog/commit/946f9cd90f3ce066b46be05a4aebb644cc18124a

Ohhh.
Knew something was wrong somewhere 🤣


Error when executing a sys.ls

I added a file into my workspace and asked the default assistant "what is in my workspace".  It errors up with:

OK. I think I have figured out the issue here, and it's very strange.
The LLM doesn't explicitly have the sys.ls tool but it intuits the existence of the tool from the prompt in the github.com/gptscript-ai/tildy tool.
When LLM tries to use it, it will request that the sys.ls function be called. GPTScript will do that and send the response back to the LLM. However, OpenAI doesn't like the . in the function name and blows up.
If you give the tildy tool explicit access to the sys.ls tool, then gptscript will add it as ls and the LLM uses it properly.
TL;DR: this is a problem with the tildy tool.

@sangee2004 I believe this has been addressed.

This issue is not seen anymore when testing with latest version of  tildy tool.


Data check for CLV and Best value for Penalizer for BG/NBD and Gamma-Gamma model

Hi Cameron,
I have transactional data set with nearly 15000 customers and their transactional data history for past 2 years and trying to predict CLV using BG/NBD OR MBG/NBD followed by Gamma-Gamma Model
Below are the questions which I am seeking help

What the tests which i need to check with my dataset before i proceed using BGNBD model?
As of now I have the correlation between frequency and monetary value which is -0.3 (Looks this is not highly correlated)

How to arrive at the optimal cut off value for penalizer for model building

Thanks for the help in advance

+1

O


Fix & break up the test for Part 01 Step 17

From j1939-84 created by mmschaefer: SolidDesignNet/j1939-84#43
Unit tests for Part 01 Step 17 need to broken down to one error per test and the test need to be update to cover all lines of code.  Verification to the latest version of the spec (issued 6/24/2021) is also included here.

[x] Break up test
[x] Added additional tests
[x] Verified to latest version issued June 24, 2021 Specification


Support multi-language orgs in Opp Record Type settings & rollups

From owiener as a comment on issue #968
from your post dated October 2014, 2, you said: "As for the the record type issue, the current settings are storing the record type's name (not devname), which can get translated. The code then tests against name. So if you save your membership record type setting in French, then the rollups will work correctly in a French instance. You get problems, as reported above, when the setting is saved in one language, and then the code is run from another language. The fix for this would be to save all picklist and recordtype settings by their underlying value (for picklists) and DevName (for recordtypes), and always that those in the code. Unfortunately, this would break current user's settings where the saved setting doesn't match."
Did you progress on this one ? The solution you proposed last year (ie translate the record type in french on the english translation) won't work when we use a second language. I though I could create a new record type (which would be the equivalent of the english one), then in NPSP Settings > Donations > Donor Statistics >Opp Rec Types Excluded for Contact Rollup add that new record type, and re run the rollup donations batch. But that produce a very strange result: the donation linked to the english record type are back in the contact donation total (but should be in Memberships total), and the one using the newly created record type only appears in the Household donation totals (it doesn't appear in the contact donation totals and not in the membership totals) ?
I'm sorry to bother you with this subject again but I really need a solution to work with 2 or more languages.

See my early comment on issue #968 for an outline of the work this fix would entail.

@davidhabib Your follow-up is greatly appreciated ! Thanks !

**lurch: add

Tracking W-008285

Hi there,
thanks for the follow-up. Any idea when this will be in place ?
All the best,
O. Wiener
PS if i click on the link W-008285, i'm having the following msg: "Your IP address is not trusted. Verify your network / VPN connection."

@owiener The tracking links in issues are to our internal project management system.

Thanks Judi for that answer !

Here's the outline of a potential solution, taken from the discussion in #968.  Note that this is a large amount of work that covers many settings, and the approach described here has not been tested.
I investigated changing the record type settings to change from storing the recordtype Name, to store the recordtype Id. The thought being we could have the settings facade detect when loading old settings that weren't Id's, and we could try to query for the correct Id. I do believe we could make this work, but it will be a non-trivial change. here are the things that would have to be done:

the facade would need to map non Id's to Ids.
code using the properties (rollup code) would need to change to expect these as Id's and use them accordingly.
the Settings pages that display these would need to handle displaying in readonly mode the record type name from the Id.
the settings pages would need to change to use Id's in the multiselect listboxes, not Names.
the installation script would need to change to setting the defaults for these properties to Id's, not Names.
several test cases would need to be modified to either store Id's, unless they are going through a wrapper we could change to handle the mapping.
The same steps for the picklist value settings apply as in #3 above. We'd need the settings facade to verify each item against the list of picklist values, and see if it matched either the name or label, and then save the label. Similarly, we'd have to modify code to test against labels, and settings pages to display labels when they hold the value instead.

Thanks @davidhabib for the clear steps. I am a bit concerned about item 4 though. I can imagine that being a poor user experience as users won't know which Id to use (for example in exclusions for roll ups) and telling them to go find it would be a much worse experience than it is now.  Do you have any ideas for a good workaround for that?

The multiselect listboxes would still display localized names.  it's just that internally they would be storing the recordtype Id's, not names.  sorry if that wasn't clear!

Included in beta release 3.79 (Beta 5)

Included in production release rel/3.79


Android 29 SDK breaks native element layouts

[x] statusbar not visible
[x] always pin webview to top of display  - use viewport-fit=auto OR safe-area-inset-* to position in relation to statusbars / navigation bars

Use var(--safe-area-inset-*)

[x] Deprecate adjust_content_insets

Set in config.json: android.viewport_fit = auto | cover

[x] Deprecateforge.layout.setContentInsetAdjustmentBehavior if possible

Hi, I currently still have problems with the --safe-area-inset CSS variables on Android 10.

Trigger Version:  v2.8.1alpha-5
Phones: Pixel 3a and One+6
Android: 10 /API level 29
"viewport_fit": "cover" in config and html meta

The forge call for layout.getSafeAreaInsets returns for the first call a top inset of 11px and for all subsequent calls it reduces down to 0.00005px. Still 11px is not correct. The trigger version 2.7 returned 24px.
The CSS variable --safe-area-inset-top is set but only has a value of 4.36756px which is also not correct.
Did I miss anything to configure?

Ideally you should be able to get by with just css now and drop layout.getSafeAreaInsets entirely.
That said:

There was indeed a bug where layout.getSafeAreaInsets() was reducing on subsequent values. I always forget that Java assigns by reference rather than value! 🤦🏼♂
There has been a semantic change to the insets to bring us in line with the browser-based html/css behaviours. Previously I think we used to include nav bars etc. in the inset size - now we automatically offset the webview to account for it and just return the offset for any notches.
There's plenty of weirdness from Android 10 itself where I'm getting sizes that are off by fractions of a pixel. I'm not entirely sure what to do about that yet.

I've pushed some changes, can you try forcing a rebuild against v2.8.1alpha-5?
I've also added a bit more info to Step 4 of the migration guide: https://trigger.io/docs/current/api/migration_guide_27_to_28.html
Any code snippets or screenshots are welcome too!

I'm using the snippet from the migration guide now var(--safe-area-inset-top); and enabled the flag ios_also_set_css_safe_area_inset_env_as_var.
Currently it works on both Android 10 phones and on the iOS13 on a iPhone7.
Thanks for the fast fix 👍
PS: Looks like a typo in the documentation: https://trigger.io/docs/current/api/migration_guide_27_to_28.html  -> Step 4  -> you two times wrote core.android.adjust_content_insets

I've found another issue with Android 5.
Same setup as above.  (Chrome 76.x)
Using var(--safe-area-inset-top); but I only get 0px

Hrrm… it may be that the older Android's either don't support CSS var lookups or don't allow setting them via Javascript.
What happens if you do something manual like:
body {
    --safe-area-inset-top: 100px;
    padding-top: var(--safe-area-inset-top);
}

That said you should still be okay, there aren't any < Android 9 devices in the real world that have notches or safe area insets - Google only introduced it in the last release.

I'm trying to work around the status bar at the top.
As the following setup works fine I assume that the variables are supported.
: root {
   --custom-safe-area-inset-top: 24px
}
html {
  padding-top: var(--custom-safe-area-inset-top);
}

I debugged this and I always get 0px in the --safe-area-inset-top CSS property and for the deprecated layout.getSafeAreaInsets() too.
Device: Samsung S4
OS: Android 5.0

You should never get a safe area inset value other than 0.0 on devices earlier than Android 9.0 as far as I understand as safe area insets only came into existence after Android 9!
If there's a problem with the status bar overlapping the webview it's more likely that this is because either the particular device, Android 5 or its WebView isn't doing layout correctly.
Can you post some screenshots of the Android 5 issue as long as well as what it's looking like on a working version of Android?
If you can post some HTML/CSS I can use to try reproduce it on an emulator on this side that can also help.
Worst case you may have to do some device detection and/or manual workarounds to get things working on that device.

Yeah I know, but this is what I was talking about when I said we've changed the semantics to match what the browser implementations are doing.
If you can give me the screenshots I asked for and something I can use to reproduce on my side I can see if this is something you'll have to workaround on your end or whether I can hack around it on my end.

Okay ..  here a minimal snipped:
<!DOCTYPE html>

  <meta http-equiv="content-type" content="text/html; charset=utf-8" />
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
  <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover" />
  <title>The title</title>

Some nice text!1!

And the screen shot:

Tx! Can you please also add a screenshot from a device where this layout works?
From what I can see so far this does look like a layout bug on Android 5's side.
On Android, irrespective of what viewport-cover is set to the WebView is supposed to be placed so that the top is aligned to the bottom of the status bar, not the top of the screen.

Sry my fault. The snippet does not work on Android 10. I'll update the snippet and come back.

Do you perhaps have the status bar set to transparent? :-)
I'm not even sure why we still have that as an option as it's not part of the modern Android look & feel anymore.

Indeed. The status bar was transparent. Now without it the versions still differ. (I updated the snippet above.)
v2.8.1beta-1

v2.7.6

Drat, I don't have a Galaxy S5 here and I'm having issues reproducing this on the Android Emulator:

AVD: Samsung Galaxy S5 Android 6.0 (Emulator)
This may be because:

The issue only shows up on 6.1 and the emulator only has Android 6.0 available.
This only shows up on the Samsung Galaxy S5 hardware
This only shows up on Samsung's versions of Android

Not the first time that Samsung has given us this kind of weirdness :-)
Do you have any other devices handy that show the bug? Can you please give me a list of hardware & Android versions if you do?
This is all the testing hardware available to me on this side:

From left to right:

Android 6.0: Alcatel 4034x
Android 6.0: Sony F3311
Android 7.0: RedMi Note 4
Android 9.1: Huawei p30 lite
Android 10.0: Essential PH-1

Also (and this is a long shot!) can you please try building against v2.8.1beta-2 and see if it makes any difference?

Also, to eliminate any potential red herrings can you please also attach the src/config.json you're using for your test app.

Seems to work on all my test devices now. Here are the logs:
From the S5:
09-16 09:15:18.943  7734  7734 I Forge   : Hey Martin! I'm trying to work around the bug because I'm an Android 23 device, my manufacturer is: |samsung| and my model is: |SM-G900F|

From S4
I/Forge   (31666): Hey Martin! I'm trying to work around the bug because I'm an Android 21 device, my manufacturer is: |samsung| and my model is: |GT-I9505|

Tx Martin!

Sorry for reporting another glitch.
I tried the landscape mode with Notch devices.
On the P20 lite the bar around the notch get's black. On the other devices it remains white. I added the background-color: blue to the html block.
For me it looks the old SDK versions WebView also managed the area around the notch and now it does not. (v2.8.1beta-2)
From left to right:

One+6 Android 9.0
One+6 Android 10.0
Huawei P20 lite - Android 8.0

Non-notch devices are not affected.

Tx for the report Martin, there are always wrinkles every time iOS & Android do a major version update so this really helps! :-)
This actually looks like its a Huawei issue though. I'd say that they are not reporting their notch metrics correctly to the operating system.
In fact, the P20 came out with Android 8 on it and Google only added notch support in Android 9. That would explain why it won't be able to display content in the notch area.
What's the Android version on the P20 currently?

The P20 lite (Android 8.0.0, EMUI 8.0.0, Patch Level 1st July 2018) on the right side is the only one that looks fine to me. The safe area around the notch is black.
For me having a white bar around the notch on the One+ devices looks rather ugly.

Doh! Sorry I thought you'd added those insets.
Let me figure out what's going on, it's probably a bug on my side :-)

So that escalated quickly. I just spent the last three days rewriting our Android UI layer. 😑
There are some new limitations imposed by the diversity of layout combinations and Android versions/manufacturers we need to be able to support:

All Android versions: Status Bars are hidden when device is rotated into landscape mode (this mirrors iOS behaviour so I quite like this one)
All Android versions: Status Bars are opaque when viewport_fit: auto
All Android versions: Status Bars are opaque when the navigation bar is enabled
Android < 28: Status Bars are always opaque
Android >= 28: Status Bars are transparent for viewport_fit: cover

This is a pretty major change so I won't be surprised if there's some weird new breakage. 🙂
Particular things  to watch out for during testing:

That Android >= 28 devices with notches from different manufacturers behave the same.
That everything still plays nicely with v3.1 of the tabs module.
That the fix for the Galaxy S4/S5's still works.

If you force a rebuild against v2.8.1beta-2 it should pick up the changes.
Release notes: https://trigger.io/docs/current/api/beta_release_notes.html

I just re-tested your change on all my Android devices including some tablets. As far for now I could not find any glitch. Thanks for the great work 👍


Repository never gets updated

Someone else should probably take over this repository to allow new changes to be introduced. @thelinmichael

agreed! so many new changes, and no maven access

I also added a feature a month ago, not accepted yet... that's frustrating... especially this is called the "official" spotify java api.

Hey guys and grills,
I just started to read a book about RESTful Web APIs that Michael gave to me. Also I need to get up to speed with jUnit tests and the whole structure of this repo.
I currently have other projects I'm working on, but I volunteered to maintain ("take over" as you call it) this repository a few months ago. So it's basically my New Year's resolution to work on this project as my others don't seem to be finished in the next weeks. One of these projects builds upon this repo, which makes me interested in seeing progress here.
Sorry for being unresponsive for so long, it seems that I have to get my priorities right. Don't be mad, if you don't hear back from me very soon, as I still need to read and learn some things and want to do everything - yes soon, but also - right.
Wishing you a happy and progressful New Year!

Very good news my friend, thank you very much!!! Happy new year!

Hey guys and girls,
it is already March and I tried to contact @thelinmichael several times now. But sadly I did get no response. I don't know why though, because he read my messages (Facebook status icon) ...
I wrote him an email a few minutes ago as a last try, but my motivation starts to fade. All I can do is to offer my help.
I'm sorry that - under these circumstances - I can't meet your expactation that I'll be the future maintainer of this project. I would like to, but it seems that the opportunity isn't there any more.
Maybe I'll start an unofficial fork / copy on which pull request are merged. I think the MIT license allows that idea. But of course I do not want to "steal" this project!
So all I can say is sorry, I tried. I hope that this project is going to be updated some day.
Until then! Greetings from Germany

Jonas Thelemann

Hey guys and girls,
about one year later @thelinmichael finally added me to this project! "Better late than never?!" he says, on which I agree :D
Right now I start studying at my local university so my time is limited. But I'll try to take care of this project whenever I can. I hope this is good news to you! ;)
Greetings from Germany

Jonas Thelemann

Really great news!
Am 10.10.2017 20:25 schrieb "Jonas Thelemann"<EMAIL_ADDRESS>
Hey guys and girls,
about one year later @thelinmichael https://github.com/thelinmichael
finally added me to this project! "Better late than never?!" he says, on
which I agree :D
Right now I start studying at my local university so my time is limited.
But I'll try to take care of this project whenever I can. I hope this is
good news to you! ;)
Greetings from Germany

Jonas Thelemann

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thelinmichael/spotify-web-api-java/issues/72#issuecomment-335564495,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL9clkqe63g68TPj4T6PlAT8VoxS3mGKks5sq7abgaJpZM4K4l2Z
.

Yeah!! I'm very  happy this is happening!

Apologies for the delay, people. Not a lot to say except that there's been a lot of things happening in my private life, causing this to be put on the back burner. Looking back, it'd been wise to hand over full access to @Dargmuesli as soon as possible after he made a visit to the Spotify office in Stockholm.
So, thanks for taking this on @Dargmuesli - much appreciated! I'll ping you regarding deploy rights to the Maven repository. Hopefully I'll be more active in the future, but at least I won't be on the critical path.
If anyone else is interested in helping out, let me and @Dargmuesli know. (You'll have access within a year! Kidding.)

Thanks, I started to dive into this project!
I still need to keep up with university though ;)

Hey guys,
here's a small update on my progress.
I worked on branch "v2" over the last days. It's going to be a complete revision of all project files with breaking changes. I pushed around 100 commits with many more to come. The jungle of classes needs to be cleaned up! It has to be clearly visible which API endpoints aren't implemented yet and it should be easier to add them. We need documented source code #95 and a unified implementation of API endpoint wrappers.
As soon as I'll get Maven deploy rights, @thelinmichael, I'll fix all bugs in the current master branch. When v2 is finished, v1 will remain in its own branch and v2 will become master.
I'll be less active within the next weeks though, as I seriously need to focus more on my university education. I spent far too much time using Intellij IDEA in the last week ;)
Any help is appreciated!
A merry christmas to all of you,
Jonas Thelemann

Hey guys,
I have great news for you:
About 450 commits later version 2.0.0-RC1 of spotify-web-api-java was just released! Try it.
And try to find bugs ;)
All endpoints are supported now and we have a great documentation as well as good test coverage.
Have fun developing your Spotify API Java software again,
Jonas Thelemann


About page should have an actual description of the application

User Story
As a user I can go to the About page to learn more on what the app is for
Acceptance Criteria

[ ] About page should have an accurate description of the app
[ ] About page has a Purpose heading describing the purpose of the app
[ ] About page has a Features heading describing the features of the app
[ ] About page has a section mentioning CS156's role in creating/maintaining CS LAs app along with a link to the GitHub

Implementation Todos
Front end:

[ ] Left align headings
[ ] Main Heading should be About Us
[ ] Subheadings: Purpose, Features, Team
[ ] Short description under each subheading

Back end:
None
Testing:

[ ]  All previous tests still pass

Guidance/Information:

You have Creative Freedom to design the About page along with any content in it.  You might look at what Prof. Conrad wrote in the #proj-ucsb-courses-search channel on the Slack about the overall purpose of the app, and/or ask the TAs/LAs that are familiar with the app for guidance.
Changes should be in javascript/src/main/pages/About/About.js
More on Typography in Bootstrap
Headings are usually wrapped in <h1> tags with subheadings <h2>, <h3> and so on.
Content after headings are wrapped in <p> tags
About page already has an example of this heading then paragraph layout, we just need to change it and add more headings!

branch name: 5pm-2-aboutpage
Task to write an about page description

@Tuckwilliger I wonder if you closed this by mistake?  I'm reopning, but if you really wanted to close it, let me know why you needed to do that.


ESLint is not actually running

My fix to ESLint broke it. Trying to do the right thing locally results in some crazy require-related errors, which I think relate to the babel stuff we do in shopify-codemod.

Is eslint doing anything other than appending a newline?  Can we remove eslint and append EOF newlines if that transformed JS doesn't have one?

There are a bunch of other fixes, not sure how much they are getting us but I think they are worth having.


Crash on nil pointer dereference while reading from RemoteDB

I have a track bought from Google Play: Stonebank - By Your Side (feat. Emel) which crashes the app everytime it is played. Found out that it is the Label field which causes the exception, however there are no visible metadata under this field inside the ID3. As a workaround I hardcoded empty string instead of the actual data and it worked.
Panic log (don't mind that /root, it's inside a LXD container ;)):
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x68515b]

goroutine 54 [running]:
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink.(*RemoteDB).queryTrackMetadata(0xc4200da280, 0xc420039cfc, 0xc4202120f8, 0xc420210318, 0x12ad3a7a884ba801)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/remotedb.go:295 +0x3cb
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink.(*RemoteDB).executeQuery(0xc4200da280, 0xc420039cfc, 0x0, 0x0, 0x0)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/remotedb.go:233 +0xf5
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink.(*RemoteDB).GetTrack(0xc4200da280, 0xc420039cfc, 0xe, 0xc42021c0f0, 0x6d4e00)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/remotedb.go:216 +0xaa
go.evanpurkhiser.com/prolink-overlay/server.(*StatusMapper).trackMetadata(0xc42022c4b0, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/server/json.go:130 +0x50
go.evanpurkhiser.com/prolink-overlay/server.(*StatusMapper).trackStatus(0xc42022c4b0, 0x757611, 0xb, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/server/json.go:146 +0x149
go.evanpurkhiser.com/prolink-overlay/server.(*StatusMapper).(go.evanpurkhiser.com/prolink-overlay/server.trackStatus)-fm(0x757611, 0xb, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/server/json.go:103 +0x48
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus.(*Handler).reportPlayer(0xc420210360, 0xc420234504)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus/handler.go:152 +0x15a
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus.(*Handler).trackMayBeFirst(0xc420210360, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus/handler.go:256 +0x120
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus.(*Handler).playStateChange(0xc420210360, 0xc42025c1e0, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus/handler.go:274 +0x387
go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus.(*Handler).OnStatusUpdate(0xc420210360, 0xc42001e330)
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/trackstatus/handler.go:330 +0x48c
created by go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink.(*CDJStatusMonitor).activate.func1
        /root/go/src/go.evanpurkhiser.com/prolink-overlay/vendor/go.evanpurkhiser.com/prolink/status.go:233 +0x107

Thank you for your amazing work btw!

Super late on the response to these PRs, but - You don't happen to still have this track and would be able to email this to me would you?
Also I'm interested in what you're doing with a LXD container :) A workaround to running on the same host as rekordbox perphase?

Haha I see :D I can send it to you, hopefully the ID3 remained unchanged since then.
I was running it in LXD container (on my NAS) because it was FAR easier to build the project in real Linux environment rather than in Windows Subsystem for Linux, and it handles the "same IP issue" as well

Thanks! I'll have a go at testing soon :) You don't happen to have any idea what version you built do you? Unfortunately I only recently even had the program report it's version.

I do not however my container remembers :) cc41bf0

I can't seem to reproduce this. Going to close for now. The new prolink-server has sentry setup in it, so I should be able to get better insight into errors in the future.


[ActionSheetIOS] Crashes consistently on iPad with iOS 8.

Terminating app due to uncaught exception 'NSGenericException', reason:
'UIPopoverPresentationController (<_UIAlertControllerActionSheetRegularPresentationController:
0x78a99e30>) should have a non-nil sourceView or barButtonItem set before the presentation occurs.'

Needs something like this:
UIViewController *viewController = [[[[UIApplication sharedApplication] delegate] window] rootViewController];

// Center the popover controler for iPad. UIActivityViewController shows up as a popover controller on iOS 8 for iPads.
if ([activityView respondsToSelector:@selector(popoverPresentationController)] ) {
  CGRect temp = CGRectMake(viewController.view.center.x, viewController.view.center.y, 1, 1);
  activityView.popoverPresentationController.sourceRect = temp;
  activityView.popoverPresentationController.permittedArrowDirections = 0;
}

[viewController presentViewController:activityView animated:YES completion:nil];

Another approach is to pass reactTag from JS and then in native find corresponding view from viewRegistry and set as sourceView.

duplicate #1890, #2395

Canonical issue: #2395


[BUG] error response on ChatGPT(GPT-4)

Describe the bug
Only shows "Error", it doesn't work even restart the app. But web browsing works.
Screenshots
https://ibb.co/fSy5LzB
Desktop (please complete the following information):

ChatALL: Version 1.18.14 (1.18.14)
OS and version:macOS 12.3.1 (21E258)

fixed in 2092c7a109df2a2af086404d2790ff30372b5e83


Email OTP resend Code does not work

Describe the issue:
When Email used as MFA and CaptureandUpdate option enabled an issue occurred. After we entered wrong OTP , OTP resend Code does not work.
Expected behavior:
OTP entering page should be render.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version:  IS 5.10.0
OS:  Linux
Database: MSSQL
Userstore:  JDBC

Duplicate Issue : https://github.com/wso2/product-is/issues/8435
Fixed Already


Buffering strategy re-appears after editing a LES

In the following LES http://beta.moses.et-model.com/testing_grounds/389, I noticed that the strategy Buffering of heat in heat pumps keeps being switched back on after I edited the LES. Here what I do, step-by-step:

I open http://beta.moses.et-model.com/testing_grounds/389
I switch the Buffering of heat in heat pumps strategy off (it is on by default)
I edit the LES, hit Save followed by Save all and view LES
When viewing the LES, the Buffering of heat in heat pumps is switched on again

The previous behaviour is only there for this particular strategy.
After discussing with @ChaelKruip  assiging @grdw.

The strategies are not saved. Don't know why. But I'll look into it tomorrow.

On a related note: #660

He now does remember the selected strategies. So I'll close this for now :)


MM-11223: Add getUnreadPosts

Summary

Add getUnreadPostsAction
Add getUnreadPosts initial state
Add getUnreadPosts API to client4

Ticket Link
https://mattermost.atlassian.net/browse/MM-11310
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit tests passed
[x] Ran make flow to ensure type checking passed
[x] Added or updated unit tests (required for all new features)
[ ] All new/modified APIs include changes to the drivers

Test Information
This PR was tested on: [mac Highsierra]

@enahum 👍

Although non-blocking, but this is awaiting PR https://github.com/mattermost/mattermost-server/pull/9108


Consider adding to Stackage

Hello! This is a great library. I use it in my simple-parser library to show pretty errors (example). Would you consider adding it to Stackage? I can make the PR in the stackage repo if you +1 it. Typically the burden as a library author is just getting an issue notification if your package falls out of the package set due to constraint failures. I doubt this will happen with the few common dependencies you have. Thanks!

Hey there! I'll add the next release (soon™) to Stackage.

PR has been made!


feat: add php.trace.server

make php.trace.server: verbose print trace log.

@felixfbecker looks like one of CI(s) is broken...

@felixfbecker Yes, I tested this.

I suggest changing php id to php-intellisense. It's easier to separate different processes in VS Code this way. I can make a new PR.


[SPARK-17273][SQL] Move expression optimizer rules into a separate file

What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various expression optimization rules into a single file.
How was this patch tested?
This should be covered by existing tests.

Test build #64518 has started for PR 14845 at commit de2e35b.

lgtm

Merging in master

Test build #64518 has finished for PR 14845 at commit de2e35b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class OptimizeIn(conf: CatalystConf) extends Rule[LogicalPlan]
case class OptimizeCodegen(conf: CatalystConf) extends Rule[LogicalPlan]

Merged build finished. Test PASSed.

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


.github/labeler.yml: Add lib label

Description of changes
Was looking for lib documentation PRs, but they seem impossible to find without a label like this.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

See also https://github.com/orgs/community/discussions/36946


Enhance the docker (daemon) logging

Right now it is really hard to debug what is going on inside of docker when you are trying to work with it. If you are using upstart you can find some logs in /var/log/upstart/dockerd.log, and you can run docker in debug mode, to get a little more detail but sometimes it isn't enough.
It would be nice to make the docker logs more consistant. Ideally we would by default add logs to /var/log/docker/dockerd.log, and allow people to pass in parameters to override the default log file location and name.
It would be nice to have different configurable log levels as well: DEBUG, INFO, ERROR, etc.
It would be really nice if we could break out logs by different parts of the system (API, etc), but one file is fine for now.
Hopefully once we make this infrastructure changes, then we can add more logging statements to the code base.
really cool future feature, would be the ability to stream the docker logs via the API, so that you can collect those logs in one place and watch more then one server at once.
I would love to hear what people think about this idea?

@blalor "docker logs --timestamps"

So in 1.4 you can set both the logging level and the there are timestamps attached.
And logs go to stdout, so you tell it to send logs wherever you want.
Does this address this issue?

Closing since this imo is generally resolved.
if that's not the case, please open a new issue with specific details on what might be lacking from the current logging format for the daemon.
Thanks!

Do timestamps have to be enabled somewhere? I'm running docker 1.8.3 and I don't see any timestamps in /var/log/upstart/docker.log ...

@mausch It depends.
If the output has a TTY allocated, then the format is different than without a TTY.

@cpuguy83 Thanks for the quick response! This is a default install of Docker on Ubuntu. I don't think any TTY is attached to the daemon... The log format I'm getting is ESC[34mINFOESC[0m[165381] POST /v1.20/images/create?fromImage=rabbitmq&tag=latest

@mausch Yeah, for some reason a TTY is detected there.
W/o a TTY it uses a json format with timestamps and such.
Not sure what upstart is doing here.

@cpuguy83 That's where the docker daemon logs go in a default install on Ubuntu 14.04... Just to confirm, timestamps should be enabled by default, correct? I'll see if I can repro on a clean box and create a new github issue. Cheers.

@mausch Can you make sure to point to that issue? On a clean Ubuntu install, 1.8.3's daemon is using the apparent "tty" format, e.g.:
DEBU[4102] Calling GET /containers/json
INFO[4102] GET /v1.20/containers/json

(I have a "-D" in my DOCKER_OPTS in the /etc/default/docker file).

This is due to docker running under upstart in Ubuntu 14.04, and how upstart handles logging: http://upstart.ubuntu.com/cookbook/#console-log
Can confirm that in the docker-engine_1.9.0 package for ubuntu 14.04 this is still logging in the TTY format (without timestamps)


In GitHub Codespaces, after copying a file in Explorer, I can only paste that file in Jupyter notebook

Repro steps:

Open GitHub Codespaces, in the Explorer select a file, and press Ctrl-C (or right click - Copy) to copy it.
Switch to another tab or application, and copy some random text.
Return to Codespaces, and open a Jupyter notebook. When I press Ctrl-V in a markdown or code block, it will paste the file I copied in step 1, instead of the text I copied later.
Copy some text inside the Jupyter notebook itself, and the clipboard functionality returns to normal.

I can reproduce this in both stable and insider versions.
Not sure if it's relevant, but I installed the Jupyter extension.
Version: 1.82.0-insider
Commit: ebd67244fb2da33ab078bb2baa96106fda29f336
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/115.0.1901.203
Embedder: codespaces

I believe the root cause is that on web, resource that are copied aren't written to the real clipboard but instead stored in internal state (this is because the web apis don't support writing to the clipboard in this way)
https://github.com/microsoft/vscode/blob/5413247e57fb7e3d29cd36f08266005fe72bbde4/src/vs/platform/clipboard/browser/clipboardService.ts#L154
This means that when you switch to another app and copy some text, VS Code still incorrectly remembers that you have a resource copied and continues using that instead
Not sure how best to workaround this or if the web clipboard api support what we need yet

This is probably also related to https://github.com/microsoft/vscode/issues/185466 which was reported to be fixed in 1.80.0 but for me is still broken in 1.80.2

This really sounds the same as https://github.com/microsoft/vscode/issues/185466
I can reproduce the issue. When we copy to clipboard from the explorer we seem to call into this method:
https://github.com/microsoft/vscode/blob/9293e05e89108972c3c70a9326bd454b2a2ea8d3/src/vs/platform/clipboard/browser/clipboardService.ts#L153-L155
And then when you paste into the editor we call readResources:
https://github.com/microsoft/vscode/blob/9293e05e89108972c3c70a9326bd454b2a2ea8d3/src/vs/editor/contrib/dropOrPasteInto/browser/copyPasteController.ts#L419
I am not able to reproduce this issue when e.g. pasting into a search input field, so I think this is specific to how the editor handles pasting. I am not sure why this would not reproduce everywhere though.

Quite sure this is fixed.


include references in grin scrape

Currently, the grin scrape does not include references to scientific publications.
As discussed in #11 , including the references in the scrape is desirable.

optionally, provide mapping from reference text (freeform text) to DOIs using something like crossref.

scraper will now provide pipe (i.e. |) delimited list of references as part of the output. Comments related to citations are ignored.
For example, https://npgsweb.ars-grin.gov/gringlobal/AccessionDetail.aspx?id=1265054 will produce output that includes
M.N. Rouse and Y. Jin. 2011. Stem rust resistance in A-genome diploid relatives of wheat. Pl Dis 95:941-944.|C.C. Anker and R.E. Niks. 2001. Prehaustorial resistance to the wheat leaf rust fungus, Puccinia triticina, in Triticum monococcum (s.s.). Euphytica 117:209-215.


Sc 200214/bridge write default configs

[[8046209027809048845, "bridge-dbg",<PHONE_NUMBER>,<PHONE_NUMBER>, {"sampleIntervalMs": 1200000, "sampleDurationMs": 300000, "subsampleIntervalMs": 60000, "subsampleDurationMs": 30000, "subsampleEnabled": 0, "bridgePowerControllerEnabled": 0, "alignmentInterval5Min": 1, "samplesPerReport": 2, "transmitAggregations": 1, "currentReadingPeriodMs": 60000, "softReadingPeriodMs": 500, "rbrCodaReadingPeriodMs": 500}]]

I think it's probably fine, but can you imagine any issue with not rebooting after writing these configs?

@towynlin This is pretty safe since we're doing all of this in the init functions before we actually use the configs. I could only imagine a problem if we try to save a new config on the fly while the data is trying to be used.
If we want to reboot - we may want to consolidate where we read the configs out of NVM. Otherwise, as it's written, we'd reboot three times for a blank config

Thanks. The triple reboot is not a reasonable tradeoff in the manufacturing process for handling an edge case that we think may never happen. Love it. :shipit:


MRR score uses a "mean" instead of "min"

If I'm not mistaken, MRR score is a mean of reciprocal rank scores over a set of examples, where reciprocal rank is given as 1 / (rank of the first positive item).
Currently implementation in spotlight takes a mean over ranks of positive items. I think this is not correct. It is also inconsistent with lightfm. It also makes it impossible to have mrr score of 1 even with perfect model (even if positive items are ranked [1, 2, 3], taking the mean gives result lower than 1).
Can I send a PR to fix this?

elanmart, I think worst case you can make a fix on repository you forked and share it here, I would also love to see it

It's not necessarily incorrect, but I can see why you might want to do it differently.
Could you make a PR that keeps the current code as default, but allows the alternative as an option? You could pass a mode argument that's either mean or min.

Hi @elanmart, are you still interested in contributing this option?

Oh, yes, sorry. I'll submit the PR ASAP.

Can I bump this. I really think that all literature discusses reciprocal rank as a per-user measure (per-query for information retrieval), and the average is taken across users. For instance, in the Croft book page 319, "reciprocal rank... is defined as the reciprocal of the rank at which the first relevant document is retrieved"
Therefore .min() should be the default.
Taking the .mean() is more similar of the reciprocal ranks is, in an adhoc way, to Mean Average Precision, and should be deprecated in favour of that.
Happy to contribute a PR. My own implementation also supports rank cutoffs and not dropping users with no relevant test items, but setting them to 0 in the array.

bump


noisy conda deactivate

Need to revisit our shell scripts:
$> conda deactivate
unwrapped_simplebuild: command not found

Likely the dev null redirection here fails:
eval "$(unwrapped_simplebuild --env-unsetup)" 2>/dev/null || true
However, why the command is not available is unclear to me?

So a quick test says that $CONDA_PREFIX is still set when the deactive script is sourced, but perhaps CONDA_PREFIX/bin has already been removed from the path?

Possible replacement for the current line?:
  9 #We want to unsetup any active simplebuild environment. However, if invoked as a│
 10 #conda deactivation script, CONDA_PREFIX/bin might have already been removed    │
 11 #from the path, so we reinject it in that case:                                 │
 12 if [ "${CONDA_PREFIX:-x}" != "x" ]; then                                        │
 13     PATH="${CONDA_PREFIX}/bin:${PATH:-}" \                                      │
 14         eval "$(unwrapped_simplebuild --env-unsetup 2>/dev/null)" 2>/dev/null || true
 15 else                                                                            │
 16     eval "$(unwrapped_simplebuild --env-unsetup 2>/dev/null)" 2>/dev/null || true
 17 fi

But needs to be unit tested and tested for all shells.

It works now in my local tests + the CI tests.


delete() may return false on success

When a delete operation is successful, there is a chance that the s3 object is still available, maybe for a few milliseconds. Therefore calling has($path) immediately after delete return true. So this code can return false even on success:
    public function delete($path)
    {
        $location = $this->applyPathPrefix($path);

        $command = $this->s3Client->getCommand(
            'deleteObject',
            [
                'Bucket' => $this->bucket,
                'Key'    => $location,
            ]
        );

        $this->s3Client->execute($command);

        return ! $this->has($path); // File is deleted but possibly still available.
    }

My assumption was that when I am sure the file really exists then I call delete() and it returns false, it means that s3 failed to delete and I must retry.

This is unfortunately not solvable, in V2 this is already solved since there is no has call before a delete. Closing this because it's a breaking change and that's already covered in V2.


Hashing and store generation

Addresses #13

Looks good to me! I think we could have a bit more comprehensive testing of every part of the AST (car/cdr/etc) but that can wait till another PR.
Also the SerDe to IPLD will be in another PR as well, correct?

Yes, I think that can lead us to a new rabbit hole

Can we squash and merge?


Rename usages of client =

See attachment below:

This will take some time to complete.

This will take some time to complete.

We were underestimating the size of this issue here, there are literally hundreds of references to the term client scattered all throughout the bot environment.
It is a shame that the change wasn't brought about earlier on when the bot was at a smaller scale, because now it is quite overwhelming. Renaming these references will take well over a full day in review time to complete without any errors.

I'm unsure what to do moving forward, because this may well not be possible at the scale the bot has now become. We are thinking about it.


Auto add super user

add migrations file 0003 that auto add admin super user close issue #48
the migrations file 0002 here only because 0003 releted him, can delete 0002 after it will marge to not cause error

@kobihk
set_password() is necessary because it keeps the password encoded and without it it is impossible to connect to the user


Do and Don't List

Use this issue to refactor the component: Do and Don't List
Refactor checklist

[x] Sass file contains comments, using the comments template format
[x] Refactor code using BEM for naming
[x] Remove / refactor any code smells
[x] Remove / refactor any 'random numbers' or make comments where it is necessary to use

Component checklist

[x] SCSS
[x] SCSS lint
[x] HTML template
[ ] HTML validate & lint
[x] Nunjucks macro
[x] A standalone example
[x] README/Documentation
[x] Pseudocode tests
[x] Visual tests
[ ] Tested against our testing policy (Resolution, Browser & Accessibility)
[x] Print stylesheet considered
[x] CHANGELOG

Error on the W3 HTML validator, SVG related. Attribute src not allowed on element image at this point.


User Story 13

As a Registered User
I want to have transparency and peace of mind regarding delivery timelines and product quality.
So that I can track my orders and ensure they are delivered on time and meet my expectations.
Additional Considerations
Acceptance Criteria:

[ ] Users have access to the order history.
[ ] Users are able to see the current status of their orders.

Priority: Must-have
Estimates: Medium

Reviewed by CE.

Reviewed by J.O'N


Open BPMN diagram

Describe the Bug
The tab crashed due to unexpected error.
Steps to Reproduce

Open Camunda Moduler
BPMN diagram

Expected Behavior

[diagram_1.bpmn] No provider for "propertiesProvider"! (Resolving: alignToOrigin -> WysiwygPropertiesProvider -> propertiesProvider)
at a (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:112:11)
at error (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:98:14)
at get (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:152:18)
at file:///D:/CAMUNDA/Camunda%20Moduler/Camunda%20v5.0.0/resources/app.asar/public/4.4.js:1:35854
at Array.map ()
at map (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:170:30)
at fnDef (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:185:14)
at providers (webpack:///node_modules/bpmn-js/node_modules/didi/dist/index.esm.js:146:43)
at file:///D:/CAMUNDA/Camunda%20Moduler/Camunda%20v5.0.0/resources/app.asar/public/4.4.js:1:60660
at Array.forEach ()
at forEach (webpack:///node_modules/bpmn-js/node_modules/diagram-js/lib/Diagram.js:49:13)
at file:///D:/CAMUNDA/Camunda%20Moduler/Camunda%20v5.0.0/resources/app.asar/public/4.4.js:1:60814
at options (webpack:///node_modules/bpmn-js/node_modules/diagram-js/lib/Diagram.js:139:56)
at call (webpack:///node_modules/bpmn-js/lib/BaseViewer.js:635:10)
at _init (webpack:///node_modules/bpmn-js/lib/BaseViewer.js:65:7)
at call (webpack:///node_modules/bpmn-js/lib/BaseModeler.js:22:13)
at call (webpack:///node_modules/bpmn-js/lib/Modeler.js:136:14)
at call (webpack:///node_modules/camunda-bpmn-js/lib/base/Modeler.js:25:14)
at call (webpack:///node_modules/camunda-bpmn-js/lib/camunda-cloud/Modeler.js:50:14)
at super (webpack:///src/app/tabs/cloud-bpmn/modeler/BpmnModeler.js:36:4)
at Function.createCachedState (webpack:///src/app/tabs/cloud-bpmn/BpmnEditor.js:802:20)
at createCachedState (webpack:///src/app/cached/WithCachedState.js:55:19)
at ui (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:132:169)
at vf (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:167:148)
at Og (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:180:29)
at Tg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:232:21)
at bi (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:233:283)
at ci (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:249:347)
at Di (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:248:143)
at Yh (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:245:331)
at Xh (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:243:85)
at qf (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:130:227)
at enqueueSetState (webpack:///node_modules/react/cjs/react.production.min.js:13:223)
at file:///D:/CAMUNDA/Camunda%20Moduler/Camunda%20v5.0.0/resources/app.asar/public/bundle.js:83:156316 [ error ]
This error may be the result of a plug-in compatibility issue. [ info ]
Environment

OS: [e.g. MacOS 10.2, Windows 10]
Camunda Modeler Version: [e.g. 2.0.0]
Execution Platform: [e.g. Camunda Platform, Camunda Cloud]
Installed plug-ins: [...]

@JGCosta1 This is clearly related to a plug-in you have installed:
[diagram_1.bpmn] No provider for "propertiesProvider"! (Resolving: alignToOrigin -> WysiwygPropertiesProvider -> propertiesProvider)

Please uninstall or fix that plug-in and you're good.

But I haven´t any plugin installed ate this version of camunda.
I have plugin's in last version, but I don't know how this version show the plugins of last version.
I have the folder plugins empty.
Thanks


Fix #15,16,17

Fix issues found at Dyalog'22

Ravel is not the right solution, see the new code in llEach


[BUG] [SM] Cannot find account with name "SharedNetwork"   - account is in "suspended" state

Required Basic Info

Accelerator Version: v1.5.1-a
troubleshooting initial run
Load Accounts
config.json based on reference-artifacts/SAMPLE_CONFIGS/config.lite-NFW-example.json

Describe the bug
The error message says SharedNetwork account was not created. However, I would expect that that account would be created by the StateMachine.
Using the AWS Organizations page I can see that the SharedNetwork account was created under the Infrastructure OU, but like the other accounts it is in a "suspended" state.
Failure Info
{
  "errorType": "Error",
  "errorMessage": "Cannot find account with name \"SharedNetwork\" and email<EMAIL_ADDRESS>  "trace": [
    "Error: Cannot find account with name \"SharedNetwork\" and email<EMAIL_ADDRESS>    "    at Runtime.Q40 [as handler] (/var/task/index.js:1374:27256)",
    "    at processTicksAndRejections (internal/process/task_queues.js:95:5)"
  ]
}

Required files

I don't see an upload file button anymore for the config.json upload

Steps To Reproduce

Create a brand new account. Make it an Org. Follow all the steps in https://catalog.us-east-1.prod.workshops.aws/workshops/f3ed5d0f-d2f1-47e8-a305-168da9179aaa/en-US/sea-administrators
to setup the org and root account.
Upload the config.json file to an S3 bucket
Launch the AWSA CF template using latest release

Expected behavior
State machine does not fail
There should not be extra preparation steps not mentioned in the workshop for admins docs:
https://catalog.us-east-1.prod.workshops.aws/workshops/f3ed5d0f-d2f1-47e8-a305-168da9179aaa/en-US/sea-administrators
State-machine should create the SharedNetwork account/VPC
Account should be "available" or StateMachine should notify admin that the account state is pending, include instructions on how to fix this, and slowly poll until it is available.
Screenshots
Additional context
Might be tangentially related to https://github.com/aws-samples/aws-secure-environment-accelerator/issues/523

Hi,
I've never seen an account flip to suspended status during account creation.  The account creation API returns "In Progress", Failed", or " Succeeded.  We do create all the accounts and wait for all newly created accounts to flip from In-Progress to Succeeded / an Active status.  We do also automatically skip Suspended accounts.  If an account is suspended, it requires manual intervention to re-open and is beyond the scope of anything we can handle in code.  Please open an AWS support case to determine why your account was suspended (and only they can unsuspend it).
Love it if you would report back as to the root cause of the accounts flipping to suspended status.
The only thing I can think of is you exceeded your "[Default maximum number of accounts]" Service Quota for AWS Organizations (Can only be checked in us-east-1), but this would be new behavior - previously the API call would have failed with an Account Limit exceeded error.

It appears AWS was not happy with us using team names for the Account which did not match the name on the Credit card. That's my best guess. After  70 hours the suspension was lifted, but we were not told what the root problem was.
Now the accounts dot now show the "Suspended" state, however, there is still an SCP policy AWS-QuarrantineNewObject
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyAllAWSServicesExceptBreakglassRoles",
      "Effect": "Deny",
      "Action": "*",
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalARN": [
            "arn:aws:iam::*:role/OrganizationAccountAccessRole",
            "arn:aws:iam::*:role/ASEA-*",
            "arn:aws:iam::*:role/aws*"
          ]
        }
      }
    }
  ]
}

And I cannot delete this policy because it says it is still in use.
The state machine now runs to the "DeleteDefaultVpcs" step where it fails without much info.
I went to the root account's VCP and discovered there were a few items left, but I deleted everything and it still fails at that step. So not sure if i'm still missing something or if it's the lingering SCP policy.

I've not touched any of the member accounts, so I presume it's not failing there, but I can't login to debug as the user account for cross-account roles i created does not satisfy the Quarantine SCP.

Hi,

The logs should indicate which account and region has something blocking deleting the default VPC.

in the above screenshot - under VPC - select see all regions and you should see which region has a remaining default VPC (if its the root account)
go to that region an manually delete the VPC.  While the GUI will ask you if you want to delete all the "stray objects" associated with the VPC - we abort if customer objects exist - this can include a simple security group.
if its a sub-account, you need to go into the sub-account - you can assume the ASEA-PipelineRole from the root/mgmt account to fix it up.

The SCP remains attached until the SM succeeds to prevent an account from being used before all guardrails are properly applied.

Thanks for that.
Using all regions, I deleted 7 other VPCs and that fixed it.
I was in the mgmt account.
This issue is resolved.


Support for mouse drag

I've done a little bit of preliminary work on this in Codepen to see how we might best approach this:
https://codepen.io/rbrtsmith/pen/GmbdGE

This would be nice to have.


RuntimeError: Input type (CUDAFloatTensor) and weight type (CPUFloatTensor) should be the same

I am getting this error on runtime. Does any one know what the problem might be?

Hi! Looks like the model is on the GPU, but the data is on the CPU. The WaveNetTrainer class has the attribute dtype which should be torch.cuda.FloatTensor if you're using a GPU. Are you running the train_script.py or the Jupyter notebook?

JUPYTER notebook which is deployed on the GPU AWS instance and accusing it from my Mac

Hello, how did you fix this error?

Adding a model.cuda() before training solve the issue.


Use unregistered mail view if it exists

This small change will allow using an existing mail view even if it has not been registered by the plugin. The mail_template should refer to the fully qualified view path (e.g. "author.plugin::mail.myview")

Is that going to be considered for merging or should I close this?
Thanks.

Sorry @mjauvin, i've missed this one
Will make some room today to get this merged 🙌


Add support for flat buffer codecs

FlatBuffer should have their own ZIO Schema Codec.

@jdegoes Should this be added in a subproject like zio-schema-flatbuffer?

Does anyone mind if I take over this task?

Yes, in a subproject would be best! (But in this same repo.)

steps:
(1) figure out how a Schema[A] from zio schema, maps to the flatbuffer spec.
(2) from a schemaA: Schema[A] derive a schema.fbs file that conforms to the flatbuffer spec.
(3) the flatc compiler binary must be available on the system. for a batteries-included experience, zio-schema could detect if flatc is available on PATH and install/build it, if it's not there.
(4) Use flatc (the FlatBuffer compiler) to generate a Java classes & helpers that can access and construct binary data.
wdyt @jdegoes ?
ref
flatbuffer Usage in brief