Error - google-analytics - The client-side rendered virtual DOM tree is not matching..

When I added the ga plugin there is en error:
[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content.

@alexchopin
If I understand correctly the error is because the GA in only rendered on the client-side:
if (process.BROWSER_BUILD && process.env.NODE_ENV === 'production') {
   [...]
}

And then Nuxt complains about that server side rendered html is different than client side.
How to fix it?
Thanks in advance.

The problem was in the default.vue layout. I included bootstrap js script. It cause the problem with GA plugin.


Stop generating undesired tokens from GPT4All

@baskaryan  In this PR, I made a small modification in gpt4all.py in the project folder libs/langchain, more precisely in the method _call. I added a unit test for the additional function remove_stop_words in libs/lanchain/llms/utils.py
It fixes the issue https://github.com/langchain-ai/langchain/issues/10345
There is no additional packages.
By executing  make format, make lint and make test locally, it works.

If necessary, you can take into account this PR @eyurtsev, @hwchase17, @rlancemartin.

I think this would be undesirable, and I'm curious if the root issue was that stop wasn't getting passed to gpt4all (either from self.stop or from the function param one). Would you want to investigate that instead, and see if passing some param to it would solve your issue?


cookiecutter model

Tasks

[ ] pinned main
[ ] branch
[x] readme documentation
[ ] dev documentation
[x] support for files
[x] support for requests
[x] support for expandable fields
[x] support for custom fields
[x] support for relations

Required for

[x] NR
[x] MOSBRI

moved directly to oarepo-cli


Having a MAX_PUB_EXPONENT makes this crate unusable with some applications

Some applications use very large numbers, including ones from factoring challenges, for the exponent part of the key.
Having a MAX_PUB_EXPONENT makes this crate unusable with such applications without using a patched source tree.
If the concern is compatibility with platforms that do enforce such limits, then the limit should be optional, and the purpose of it should be stated explicitly, IMHO.

The concern is potential misuse: increasing the size of the public exponent e decreases the size of the private exponent d. In practice there is no need for a public exponent larger than 65,537 (and really 3 is sufficient with proper padding).
Or in other words: using a larger e only subtracts from the overall security of the key.
If d is smaller than the 4th root of n, it can be recovered using Weiner's attack.
For this reason it's fairly common for RSA libraries to enforce a maximum size on the public exponent.

Sure. But in practice, sometimes you can't control the exponent used by others, or by default/policy. And the limit imposed is still too small.
For example, I have a use-case where 1024 bit long values are used for n. And a fixed 212 bit long exponent is used. d still doesn't get small.

We could add another hazmat type feature, which allows larger sized exponents, still preventing default users from using larger exponents by default.

I am personally very much in favor of allowing potentially unsafe features, as long as the public default api doesn't expose it. To avoid exactly the issue of forks and patches that are potentially much more problematic (and just make it harder for folks to move forward)

Yeah, this somewhat exists already with the (unreleased) RsaPublicKey::new_with_max_size
We could relax that into a fully unchecked version

I opened #206 which adds RsaPublicKey::new_unchecked which bypasses all checks.


Strawberry Type created from create_type can't be instantiated via kwargs

Describe the Bug
When using the strawberry.tools.create_type function to create a Strawberry GraphQL Type, trying to instantiate an instance of that type results in an error indicating the constructor was not expecting that kwarg.
Seems like there's a problem somewhere in how the class is constructed inside create_type that prevents the dataclass wrapping from working correctly.
To Reproduce:
from typing import Callable

import strawberry
from strawberry.tools import create_type

class ExplicitTestClass:
    first_name: str
    age: int

def generate_resolver1() -> Callable:
    def first_name(root) -> str:
        return root.first_name
    return first_name

def generate_resolver2() -> Callable:
    def age(root) -> str:
        return root.age
    return age

ExplicitStrawberryClass = strawberry.type(ExplicitTestClass)

DynamicStrawberryClass = create_type(fields=[
    strawberry.field(resolver=generate_resolver1(), name="first_name"),
    strawberry.field(resolver=generate_resolver2(), name="age")
], name="DynamicStrawberryClass")

print(ExplicitStrawberryClass(first_name="John", age=30))  # This works
print(DynamicStrawberryClass(first_name="John", age=30))   # This does not work

I also checked out the repo and attempted to do the same in the test_create_type() unit test:
def test_create_type():
    @strawberry.field
    def name() -> str:
        return "foo"

    MyType = create_type("MyType", [name], description="This is a description")
    definition = get_object_definition(MyType, strict=True)

    assert definition.name == "MyType"
    assert definition.description == "This is a description"
    assert definition.is_input is False

    assert len(definition.fields) == 1

    assert definition.fields[0].python_name == "name"
    assert definition.fields[0].graphql_name is None
    assert definition.fields[0].type is str
    MyType(name="foo")  # Added this to test

System Information

Operating system: Mac OS Sonoma 14.6.1
Strawberry version (if applicable): 0.247.0
Python 3.11.2

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Ah, seems like the root of the problem is if you provide the field with the same name, dataclasses won't pick up the annotation because it probably thinks its a static variable


Update japanese-ime.md

In the Japanese IME, “natu” is equivalent to “natsu”. Most people would type “natu” just because it’s fewer keystrokes.

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/input/japanese-ime.md
92
100
83
79

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx


Allow empty keys as defined in the JSON spec.

Hi,
the lib currenty disallows empty JSON keys although they are allowed by the JSON spec. I found several other libs with similar issues, where fixes have been suggested and pulled, so I'm quite confident it is correct to allow empty keys.
My use case worked with this fix although I'm not sure if there are other implications (tests do not cover this).

Hi @umulmrum ,
Thanks for contributing and hope you found this lib useful for you.
I'm not sure object's key could be empty according to specification RFC8259 https://tools.ietf.org/html/rfc8259 , ECMA-404 http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf :

An object structure is represented as a pair of curly brackets
surrounding zero or more name/value pairs (or members).  A name is a
string.  A single colon comes after each name, separating the name
from the value.

To ensure we are talking on same side: are we talking about object's key as about name of name/value pair?
Could you please send part of JSON of your use-case and link to spec you found object's key could be empty? Maybe your specific JSON doesn't follow standard and tries to use object in case where array is suitable? :)

Hm I found this one in ECMA-404:

The JSON syntax does not impose any restrictions on
the strings used as names, does not require that name strings be unique, and does not assign any
significance to the ordering of name/value pairs

So it allows following JSON:

{"": "value"}

Did you you mean this case?


Fix profile activation for non-apple silicon

Relying on <activeByDefault>true</activeByDefault>
does not work when a profile, such as the IntelliJ profile is active

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-01-18T09:28:38.396+0000

Duration: 47 min 7 sec

Commit: bd32ea0d1dda9d93085866159df90e967b59aaf2

Test stats :test_tube:

Test
Results

Failed
0

Passed
2442

Skipped
16

Total
2458

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark test.

run compatibility tests : Run the JDK Compatibility test.

run integration tests : Run the APM-ITs.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


added Wildlife theme

Added Wildlife (Day and Night theme)
Updated themes.json and README.md

thanks

You are welcome
Sent from my iPad

On 18 Sep 2015, at 8:50 p.m., Gianluca Guarini<EMAIL_ADDRESS>wrote:
thanks
—
Reply to this email directly or view it on GitHub.


' Uncaught TypeError: (row[columnKey] || "").toLowerCase is not a function '  When sorting or filtering

Happens to me on latest chrome and firefox, when I am trying to sort or filter records.
Here is my setup:
A simple line in template:
{{fixtable-grid columns=fixTableCols content=reports filterDebounce=1000 }}
The column definition looks like this:
  fixTableCols: [
    {key:'name', header:'Name',  sortable:true, filter:{type:'search'}, component:'fixtable-name-link'},
    {key:'label', header:'Label',sortable:true, filter:{type:'search'} },
    {key:'description', header:'Description',sortable:true,filter:{type:'search'} },
    {key:'reportPath', header:'Path',sortable:true, filter:{type:'search'} },
    {key:'reportSections', header:'Sections',sortable:true,  component:'report-fixtable-section'},
    {key:'parameters', header:'Parameters',sortable:true,  component:'report-fixtable-parameter'},
  ],

and the model looks like this:
  name: attr('string'),
  label: attr('string'),
  description: attr('string'),
  reportPath: attr('string'),
  // relations
  reportSections: DS.hasMany('report-section'),
  parameters: DS.hasMany('parameter'),

I have found out that if I change the sort / filter key part of the code from simple [key] lookup to .get(), the sort and filter works.
(addon/componments/fixtable-grid.js)
Ln 162:   var cellData = (row[columnKey] || '').toLowerCase();
change to
Ln 162:   var cellData = (row.get(columnKey) || '').toLowerCase();
Could this be due to I have hasMany in the model?
Or it is something else on my setup is quirky?
And, is this the right way to fix this? If yes, I can send in pull request : )

What version of this addon are you using? This seems like the issue that was fixed by PR #58, so I believe updating your version will make this error go away.

Ahh.. My bad! I am still on 0.2.1..
Closing issue..


crash on volume change

After the update to 2.4.0 the app crashes when using the volume up/down buttons repeatedly:
6-09 22:46:22.635 10235 10235 D AndroidRuntime: Shutting down VM
06-09 22:46:22.636 10235 10235 E AndroidRuntime: FATAL EXCEPTION: main
06-09 22:46:22.636 10235 10235 E AndroidRuntime: Process: org.xbmc.kore, PID: 10235
06-09 22:46:22.636 10235 10235 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void org.xbmc.kore.ui.widgets.VolumeLevelIndicator.setVolume(boolean, int)' on a null object reference
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at org.xbmc.kore.ui.generic.VolumeControllerDialogFragmentListener.applicationOnVolumeChanged(VolumeControllerDialogFragmentListener.java:159)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at org.xbmc.kore.host.HostConnectionObserver.onVolumeChanged(HostConnectionObserver.java:453)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at org.xbmc.kore.jsonrpc.HostConnection$19.run(HostConnection.java:849)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:751)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:95)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:154)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6186)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
06-09 22:46:22.636 10235 10235 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
06-09 22:46:22.639  4135  6243 W ActivityManager:   Force finishing activity org.xbmc.kore/.ui.sections.remote.RemoteActivity

I can reproduce it on two devices (just repeatedly change volume using the hardware volume up/down buttons).

@poisdeux duplicate of #551?

right, missed that one.

This seems to still be occurring on the beta. @rigid @poisdeux  can you please confirm. And what steps do you take to trigger the crash? I can't replicate it, but we have reports of crashes on the play console.

I haven't had a crash since the update. I can paste a logcat if it happens again.

It seems to happen only when VolumeControllerDialogFragmentListener.applicationOnVolumeChanged is called. So my guess would be that there is still a fragment listening to application events while its view has been destroyed.
We unregister the application listener in onDestroy but first call the onDestroy method from the parent. That's where the dialog gets dismissed and this might explain the crashes as the fragment is still listening to application events.
However, I am not able to reproduce the issue in 2.4.1. Which makes this hard to debug...

I can't reproduce it either. @poisdeux I'm not sure that that little race condition (if it is indeed one) would be sufficient to cause so many crashes. Anyway, we can move the super.onDestroyView() to the end of the method.

It might be better to move the registration and unregistration to onResume and onPause.
Another thing I just thought of is that the timed dismissal of the dialog might be the cause.
It calls [dismiss] (https://github.com/xbmc/Kore/blob/master/app/src/main/java/org/xbmc/kore/ui/generic/VolumeControllerDialogFragmentListener.java#L75) on the dialog, which AFAICT doesn't call the onDestroy on the Fragment. We might need to replace this with dismiss() from the fragment which dismisses both the fragment and the dialog.

I created a new PR #559 which fixes two issues I could find. However, I'm not sure that this will fix the reported NPEs. I have a feeling there is a race condition we are missing...

Yeah, it still isn't fixed. The good news is that i can replicate it: Make sure you're connected through TCP, use the volume keys to open the volume dialog fragment, then on Kodi, keep changing the volume until the dialog closes (use a physical remote or the volume dialog on Kodi). It might take a couple of tries but it crashes

So, AFAICT this is the sequence of events:

VolumeLevelIndicator.onDetachedFromWindow is called, which calls Butterknife unbind therefore making the local View references null:
https://github.com/xbmc/Kore/blob/d11dbe68531f8e9f17cbbead11fa4a879eb89ee4/app/src/main/java/org/xbmc/kore/ui/widgets/VolumeLevelIndicator.java#L67

VolumeControllerDialogFragmentListener.onDestroyView is only called after 1, and it is there that we are unregistering the connection observers:
https://github.com/xbmc/Kore/blob/d11dbe68531f8e9f17cbbead11fa4a879eb89ee4/app/src/main/java/org/xbmc/kore/ui/generic/VolumeControllerDialogFragmentListener.java#L126

So, if between 1) and 2) a volume change occurs in Kodi and the connection is through TCP, the TCP listener thread on HostConnection will pick it up, notify HostConnectionObserver, which will notify VolumeControllerDialogFragmentListener (because it hasn't unregistered yet), which will call setVolume on VolumeLevelIndicator, which will try to access the local View variables that just got set to null...
So, we can:

hack it - in VolumeLevelIndicator.setVolume check if the variables are null before accessing them
find out some other lifecycle methods on VolumeLevelIndicator and VolumeControllerDialogFragmentListener that work correctly. We need to unregister the observers before any view is destroyed/detached/whatever.

@poisdeux any thoughts on how we could do that, or should we go with the hack

I believe VolumeLevelIndicator.onDetachedFromWindow is bounded to onDestroy. So moving registration to onStart and unregistration to onStop should solve this.

Sorry for the late reply. Like i said, i think that the issue is that the lifecycles of the view and the dialog fragment aren't aligned, specifically VolumeLevelIndicator.onDetachedFromWindow and VolumeControllerDialogFragmentListener.onDestroyView, so we should take care when unbinding to make sure that we don't do it too early.
This led me to question why do we need to unbind. AFAICT this just sets the variable to null so it's not stricly necessary. The Butterknife docs don't contain much detail but they just reference unbind in the context of fragments (justifying it by saying that the fragment lifecycle isn't strictly aligned with the activity's...), but we're using it here in the context of a view.
I removed the call to unbind in VolumeLevelIndicator.onDetachedFromWindow, and it fixes the NPE. The local variables should just be GC when the time comes. PR #563

The unbind in the view is probably redundant. I added the unbind in fragments to solve some memory issues when running the instrumented tests.
Should we keep this issue open during the next beta run?

I'll close it for now. If it happens in beta i'll reopen it.


Update broken link

I want to merge this change because...
The installation guide leads to an error page.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Thanks @the-bionic!


feat(formly-form): move form out of formly-form component.

Hi,
I would like to use ngSubmit and I figured out that is not possible with the current implementation, so I propose to not include form in the formly-form to allow more flexibility.
thanks in advance :smile:

@aitboudad update the readme file. Thanks

done #98


[Feature] Generalise template building further

Is your feature request related to a problem? Please describe.
We'd like to minimise work needed to create a new template from new source data.
Describe the solution you'd like
A well-designed and documented way to make a template that

uses default methods for each step, to minimise effort
avoid duplications by e.g. ensuring default names for files, and writing intermediate files, and the default methods for template generation steps mentioned above.
makes it easy to customise steps for which the new data is tricky

Describe alternatives you've considered
\
Additional context
Currently considering decorator, strategy and template pattern, but also might like to think about non-OO approaches to this, that might be simpler.

Some pseudocode for idea:
from template_building import TemplatePrepper

# for easy atlases
if __name__ == "__main__":
    crab_template = TemplatePrepper("crab")
    crab_template.run()

#----------------------------------------------------

# for harder atlas
class DifficultTemplatePrepper(TemplatePrepper):
    def __init__(config):
        pass

    def initialRegistrationStep(self):
        # do a fancier initial registration
        pass

# for hard atlases
if __name__ == "__main__":
    crab_template = DifficultTemplatePrepper("crab")
    crab_template.run()


Autoupdating query - single item

Goals
Results are able to autoupdate even if the initial query is empty.
class IDObject: Object {
    dynamic var identifier:Int
}

let results:Results<IDObject> = realm.objects(IDObject.self).filter(NSPredicate(format:"identifier = %d", 1)
print (results.count)  //=>0
let obj = IDObject()
obj.identifier = 1
realm.add(obj)
print (results.count)  //=>1

However, what if we want a single object?
let result:IDObject? = realm.objects(IDObject.self).filter(NSPredicate(format:"identifier = %d", 1).first
print (result)  //=> result is nil
let obj = IDObject()
obj.identifier = 1
realm.add(obj)
print (result)  //=> result is still nil

Expected Results
One way to handle this would be to always get a Results object and then have to unwrap .first every time we wanted to access the single object.
However, it would be great if there was a SingleResult<T> class which would only hold one or zero objects.  That object could be autoupdating as well, which would protect from this use case.

Hi @dmorrow. Thanks for reaching out about this. Someone will review what you've shared and follow-up with a solution or additional questions. Cheers!

Thanks for getting in touch with us! This sounds like a great idea for an enhancement; I will add it to our backlog until the relevant engineers can discuss it.

I'm not sure this is something we'd want. It would lead to super surprising results. Just as an example, keep in mind that Results aren't guaranteed to preserve their sorting order across Realm transaction versions, so the object you're holding on to could become a whole different object at a later time.
Even if you sort the Results, the same thing could happen when a different object becomes first in the ordering.
Not to mention that we'd need to keep the query alive and running for the duration of this object's lifecycle, which is a lot more expensive than just keeping a pointer to the object you got originally...
For these reasons, I'm closing this ticket. I hope you understand @dmorrow.


IndexError: list index out of range

Hello All,
Summary :
I'm trying to validate the current master (https://github.com/mlcommons/power-dev/commit/5e3dbeab467fc7c98a8b564c92f1608369d84683)  branch's workflow. I'm running this with our new Yokogawa WT333E multichannel meter. It's erroring out with an index out of range error as follows, on our NVIDIA code workflow based submission (error below).
When I launch resnet50 server inference workload for example with the following client and server settings, it runs the benchmark and is not generating any power related log files inside the --output folder.
run_workload.sh file
#!/bin/bash
set -ex

make run_harness RUN_ARGS="--fast --benchmarks=resnet50 --log_dir build/logs/power --scenarios=Server --config_ver=default --test_mode=PerformanceOnly"

run_power.sh file
#!/bin/bash
set -ex

python3.7 power-dev/ptd_client_server/client.py \
        --addr <IP_ADDRESS> \
        --output "./cout" \
        --run-workload "./run_workload.sh" \
        --ntp <IP_ADDRESS> \
        --loadgen-logs "/work/build/logs/power/R750xa_A100-PCIE-80GBx4_TRT/resnet50/Server" \
        --label "resnetserver" \

IndexError: list index out of range
....
....
07-18-2021 02:43:20.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:21.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:21.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:21.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:21.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
ptd-server 2021-07-17 21:43:21,980 [INFO] Got command from the client 'session,2021-07-17_21-41-18_resnetserver,stop,ranging'
07-18-2021 02:43:22.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:22.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:22.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:22.903: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:23.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:23.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:23.903: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:23.903: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:24.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:24.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:24.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:24.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:25.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:25.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:25.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:25.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:26.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:26.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:26.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:26.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:27.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:27.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:27.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:27.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:28.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:28.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:28.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:28.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:29.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:29.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:29.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:29.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:30.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:30.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:30.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:30.902: WARNING: Uncertainty unknown for the last measurement sample! channel 2
07-18-2021 02:43:31.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:31.902: WARNING: Uncertainty unknown for the last measurement sample! channel 1
07-18-2021 02:43:31.902: ERROR: Can't evaluate uncertainty of this sample!
07-18-2021 02:43:31.903: WARNING: Uncertainty unknown for the last measurement sample! channel 2
ptd-server 2021-07-17 21:43:31,980 [INFO] Sending to ptd: 'Stop'
07-18-2021 02:43:31.980ptd-server 2021-07-17 21:43:31,980 [INFO] Reply from ptd: 'Stopping untimed measurement'
: Response to client sent: Stopping untimed measurement
ptd-server 2021-07-17 21:43:31,980 [ERROR] Got an exception
Traceback (most recent call last):
  File "..\ptd_client_server\lib\server.py", line 576, in handle_connection
    reply = self._handle_cmd(cmd, p)
  File "..\ptd_client_server\lib\server.py", line 649, in _handle_cmd
    return unbool[self.session.stop(Mode.RANGING)]
  File "..\ptd_client_server\lib\server.py", line 860, in stop
    self._maxVolts, self._maxAmps = max_volts_amps(
  File "..\ptd_client_server\lib\server.py", line 165, in max_volts_amps
    if not parser.check(f"Ch{channel_range[0]}"):
IndexError: list index out of range
ptd-server 2021-07-17 21:43:31,980 [INFO] Sending reply to client 'Error: exception'
ptd-server 2021-07-17 21:43:31,980 [INFO] Connection closed
ptd-server 2021-07-17 21:43:31,980 [WARNING] Client connection closed unexpectedly
ptd-server 2021-07-17 21:43:31,980 [INFO] Sending to ptd: 'Stop'
07-18-2021 02:43:32.730: Completed test
07-18-2021 02:43:32.730: Avg watts 1623.218947, min watts 983.800000, max watts 1979.000000, samples 95, errors 0, valid 95
ptd-server 2021-07-17 21:43:32,730 [INFO] Reply from ptd: 'Error: no measurement to stop'
07-18-2021 02:43:32.730: Response to client sent: Error: no measurement to stop
ptd-server 2021-07-17 21:43:32,730 [INFO] Sending to ptd: 'SR,V,Auto'
07-18-2021 02:43:37.746: Volt range set to Auto
07-18-2021 02:43:37.809ptd-server 2021-07-17 21:43:37,808 [INFO] Reply from ptd: 'Range V changed'
: Response to client sent: Range V changed
ptd-server 2021-07-17 21:43:37,808 [INFO] Sending to ptd: 'SR,A,Auto'
07-18-2021 02:43:42.824: Ampere range set to Auto
07-18-2021 02:43:42.887ptd-server 2021-07-17 21:43:42,887 [INFO] Reply from ptd: 'Range A changed'
: Response to client sent: Range A changed
ptd-server 2021-07-17 21:43:42,887 [INFO] Set initial values for Amps Auto and Volts Auto
ptd-server 2021-07-17 21:43:42,887 [INFO] Stopping ptd...
07-18-2021 02:43:42.888: No data returned by socket read.
07-18-2021 02:43:42.888: Shutting connection down...
07-18-2021 02:43:42.888: Connection is down.
07-18-2021 02:43:42.888: Waiting for a connection...
ptd-server 2021-07-17 21:43:42,902 [INFO] Done processing

Here is my server.conf file:
# Server Configuration Template
# To use change the section of the config that you'd like to change.

[server]
# NTP server to sync with before each measurement.
# See "NTP" section in the README.md.
ntpServer: <IP_ADDRESS>

# A directory to store output data. A relative or absolute path could be used.
# A new subdirectory will be created per each run.
# The name of this sub-directory consists of date, time, label, and mode (ranging/testing).
# The loadgen log is fetched from the client if the `--send-logs` option is enabled for the client.
# The name of the directory is determined by the workload script running on the SUT, e.g. `ssdmobilenet`.
# The power log, named `spl.txt`, is extracted from the full PTDaemon log (`ptdLogfile`)
#outDir: D:\ptd-logs-new\

# (Optional) IP address and port that server listen on
# Defaults to "<IP_ADDRESS> 4950" if not set
#listen: <IP_ADDRESS> 4950

# PTDaemon configuration.
# The following options are mapped to PTDaemon command line arguments.
# Please refer to SPEC PTDaemon Programmers Guide or `ptd -h` for the details.
[ptd]
# A path to PTDaemon executable binary.
ptd: D:\PTD\ptd-windows-x86.exe

# A path to a logfile that PTDaemon produces (`-l` option).
# Note that in the current implementation this file is considered temporary
# and may be overwritten.
#logFile: logs_ptdeamon.txt

# (Optional) A port on that PTDaemon listens (`-p` option). Default is 8888.
#networkPort: 8888

# Power Analyzer numerical device type. Refer to `ptd -h` for the full list.
# 49 corresponds to Yokogawa WT310.
deviceType: 77

# interfaceFlag and devicePort describe the physical connection to the analyzer.
# interfaceFlag is either one of -n, -g, -y, -U, or empty.
# Refer to SPEC PTDaemon Programmers Guide or `ptd -h` for the details.
# Below are some examples of interfaceFlag and devicePort pairs.

# Use RS232 interface.
# Empty interfaceFlag corresponds to RS232.
#interfaceFlag:
#devicePort: COM1

# Use GPIB interface.
#interfaceFlag: -g
#devicePort: 0

# Set GPIB board number (`-b` option)
#gpibBoard: 0

# Use TCPIPv4 ethernet interface.
#interfaceFlag: -n
#devicePort: <IP_ADDRESS>

# Use Yokogawa TMCTL for USB or ethernet interface.
# devicePort should be either the IP address or device serial number.
interfaceFlag: -y
# I have the correct value in there
devicePort: C2XXXXXX

# (Optional) Channel number for multichannel analyzers operating in single channel mode. (`-c` option)
# Channel value should consist of two numbers separated by a comma for a multichannel analyzer.
# Channel value should consist of one number or be disabled for a 1-channel analyzer.
channel: 1,2

It runs the workload benchmark and it doesn't create any files in the cout directory (inside the client) other than just the directories as seen below:
(mlperf) rakshith@mlperf-inference-rakshith:/work/cout$ tree
.
└── 2021-07-17_21-41-18_resnetserver
    └── power

Here is the error on the client side:

....
....
&&&& PASSED Default_Harness # ./build/bin/harness_default
[2021-07-17 21:43:22,117 main.py:280 INFO] Result: result_scheduled_samples_per_sec: 104029, Result is VALID

======================= Perf harness results: =======================

R750xa_A100-PCIE-80GBx4_TRT-default-Server:
    resnet50: result_scheduled_samples_per_sec: 104029, Result is VALID

======================= Accuracy results: =======================

R750xa_A100-PCIE-80GBx4_TRT-default-Server:
    resnet50: No accuracy results in PerformanceOnly mode.

client 2021-07-17 21:43:22,171 [INFO] Sending command to the server: 'session,2021-07-17_21-41-18_resnetserver,stop,ranging'
client 2021-07-17 21:43:32,178 [INFO] Got response: 'Error: exception'
client 2021-07-17 21:43:32,179 [CRITICAL] Got an unexpecting response from the server

Other things I tried:

Ran the test multiple times just to make sure it's not somehow a noisy sample somewhere
Made the log dir paths absolute
explored with --force argument
Verified if indeed inference benchmark loadgen logs exist at build/logs/power
With and without keeping and --fast

I suspect because it's not creating any log files, it's erroring out with an out of index?
Any suggestions to fix this would be appreciated.

In server.py
https://github.com/mlcommons/power-dev/blob/5e3dbeab467fc7c98a8b564c92f1608369d84683/ptd_client_server/lib/server.py#L162
The while loop tries to continue even after it has exhausted the configured channels. Even after it has channel_range.pop(0)'ed all available channels, the loop will continue and error out when it tries to manipulate an empty list.
I found that adding an extra check at the end to break out of the while loop allowed me to proceed past this issue.
                while not parser.is_finished():
                    is_sutable_channel = True
                    if not parser.check(f"Ch{channel_range[0]}"):
                        is_sutable_channel = False
                    else:
                        channel_range.pop(0)
                    . . .
                    if len(channel_range)==0:
                        break

Hi Trevor - Thanks.    @trevor-cockrell   - can you check with @nvpohanh  on how to get a code change in so that this can be fixed.
@rakshithvasudev  - could you use Trevor's workaround to make progress.  We will track and close this with high priority.

Will file a PR by EOD

will be fixed by #249

Thanks Po-Han (@nvpohanh ) . @rakshithvasudev   - Please comment once you have tested.

Thanks @s-idgunji @trevor-cockrell @nvpohanh
Will keep you updated once I get a chance to test it.

That fix worked. Additionally I had to update my time zone to UTC thanks to @trevor-cockrell  for that tip.


TypeError: (0 , _reactFastCompare.default) is not a function when running tests

Get the following error when running tests with V2.2
TypeError: (0 , _reactFastCompare.default) is not a function
11:34:40        node_modules/react-popper/lib/cjs/usePopper.js:75:42

Hi, do you have all the dependencies installed? react-fast-compare is a new dependency

But it isn't a peer dependency, I shouldn't have to install it... that should just happen.
It looks like some other package uses an older version, so possible conflict?

I'm not sure how to help without a reproduction example I can play with, sorry.

I have the same issue and a clean install does not fix it. I have gone back to 2.1.
Thank you for your hard work on this, but please be more considerate of following semver, as this can cause quite an issue with many people's applications and cost a lot of time in a big team, as it did for us today.
The Release notes for 2.2 say:

This release is shipped as a minor patch but it's actually a complete rewrite of the library

2 things wrong with this:

Anything that is a 'complete rewrite' is clearly going to break something somewhere and should be a major version.

It was released as a Minor version, not a "patch". Patch means something very specific in semver.

reference: https://semver.org/

Sorry that I can't make a repro at the moment, but it may have to do with @storybook/components, which depends on "react-popper-tooltip": "^2.8.3",, which depends on "react-popper": "^1.3.7"

react-fast-compare only ships a CJS version, but Popper imports it as a module. Usually this is fine, but not in the case of Jest, because of the following I think:
// this
import isEqual from 'react-fast-compare';

// becomes
const isEqual = require('react-fast-compare').default;

// but the function is not at `.default`.

I think bundlers usually don't require this with their ESM-CJS interop, but Jest does require it.

Why does it work in our tests and in my CRA app then?

It likely depends on the configuration

The library does module.exports = function isEqual(..., so there's not a named export, it should fallback to the default export.
If I try to do import { isEqual }  it throws an error because it's not exported  that way.

<EMAIL_ADDRESS>check line 75

Oh cool, why 😳

Fixed in 2.2.1


Usage with roles?

Thanks for this great project, I really like it!
Is it possible to extend its functionality so it can also create UML diagrams for the tasks in roles?

Thanks too, good job !
Not sure to answer to your question @rndmh3ro but, I tested it on one of my role. I wrote as test a simple playbook and tried playbook2uml on it, and I got the image below which shows how my role works:

Thanks for replying.
I noticed what my problem is. I use include_role.
Code:
- name: ansible-os-hardening
  hosts: all
  collections:
    - devsec.hardening
  tasks:
    - include_role:
        name: os_hardening

resulting UML:
@startuml
state "= Play: ansible-os-hardening" as play_1 {
    play_1 : | gather_facts | None |
    play_1 : | hosts | all |
    play_1 : | serial | [] |
    play_1 : | strategy | linear |
    state "== workaround for https://github.com/ansible/ansible/issues/66304" as task_1
    task_1 : Action **set_fact**
    task_1 : | ansible_virtualization_type | docker |
    task_1 : ....
    task_1 : **become** yes
    state "== include_role : os_hardening" as task_2
    task_2 : Action **include_role**
    task_2 : | name | os_hardening |
    task_2 : ....
    task_2 : **become** yes
}
[*] --> task_1
task_1 --> task_2
task_2 --> [*]
@enduml

It's logical that only the task include_role and not the contents of the role are shown.
Maybe another feature request: There could be an option that the role included by include_role should be displayed too?

Thank you for your contribution to Issue.
I will write code to add the --role option this weekend.

Maybe another feature request: There could be an option that the role included by include_role should be displayed too?

Could you use import_role loads a role statically instead of include_role.

Could you use import_role loads a role statically instead of include_role.

Thanks, that works! Then I get all the tasks in the roles. Awesome!

I added -R or --role option.
Could you checkout 2-usage-with-roles branch and test ?
An example is following:
zsh 📁 playbook2uml on  2-usage-with-roles via 🐍 v3.8.12 (ansible)
❯ fd . test/roles/test_1
test/roles/test_1/tasks/
test/roles/test_1/tasks/main.yml
zsh 📁 playbook2uml on  2-usage-with-roles via 🐍 v3.8.12 (ansible)
❯ python -m playbook2uml.cli --title "test_1 role flow" --theme blueprint -R test_1 test
@startuml
title test_1 role flow
!theme blueprint
state "== test_1 : Say Hello" as task_1
task_1 : Action **debug**
task_1 : | msg | Hello `test_1' role |
state "== test_1 : Say 💩" as task_2
task_2 : Action **debug**
task_2 : | msg | 💩 |
[*] --> task_1
task_1 --> task_2
task_2 --> [*]
@enduml

This works great, thank you for your fast implementation!

Thank you for testing 😃
merged to main branch.


hotfix for large ecntt

Describe the changes

This PR is a hotfix for large ECNTTs of size 2^18 x 64 and above
Rust bindings benchmarks and correctness test against Arkworks to come in subsequent PRs

Linked Issues
Resolves #

the comment by @yshekel will be resolved as discussed


BUG: User can move to home, about page without logging in by changing the url routes manually. There is no prevention of this in code.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Problem creation:

There is no stoppage (as login needed) from entering the platform .
I want to work on this
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I've already added this as an existing issue prior to this, you might want to uncheck that option


Can't install ESLint 1.2.11

Hi, I'm trying to install ESLint 1.2.11 and it fails silently. I click on the install button and almost instantly the button becomes green again. Is there a way to debug why this happens?
Thanks,
Paul

VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:13:11.413Z)
OS Version: Darwin x64 16.5.0
Extensions:

Extension
Author
Version

prettier-eslint-vscode
RobinMalfait
0.7.1

vscode-styled-jsx
blanu
0.1.1

vscode-es-beautifier
dai-shi
0.2.4

vscode-npm-script
eg2
0.1.9

code-runner
formulahendry
0.6.15

terminal
formulahendry
0.0.8

vscode-auto-open-markdown-preview
hnw
0.0.4

ftp-simple
humy2833
0.4.23

ftp-sync
lukasz-wronski
0.3.3

prettify-json
mohsen1
0.0.3

csharp
ms-vscode
1.9.0

debugger-for-chrome
msjsdiag
3.1.2

Material-theme
zhuangtongfa
2.8.3

@joaomoreno assigning to you.
@paulbrie does you home folder contain a .vscode/extensions/dbaeumer.vscode-eslint-1.2.11 folder?. If so can you try to delete the folder and try to install eslint again?

Thanks, problem solved :)


[GSoC2024] - fix/attribute-text-length-limited-for-adding-values

Doubled the maximum length of the attribute values.
Motivation and context

It provides a solution to the issue here
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have created a changelog fragment
- [ ] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes
[x] I have linked related issues (see GitHub docs)
- [ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

New Features

Doubled the maximum length of attribute values, allowing for more detailed entries in the system.

@Marishka17
Do you have any comments to the pull request?

@coderabbitai review

@coderabbitai review

@Marishka17
Can you please review it?


Source Code?

Source code anywhere?

https://github.com/EvanKrall/cronsul

man..   For some reason I assumed they were compiled binaries.

:D it happens
On Thu, Sep 3, 2015 at 6:50 PM, Shane Starcher<EMAIL_ADDRESS>wrote:

man..  For some reason I assumed they were
compiled binaries.
—
Reply to this email directly or view it on GitHub
https://github.com/EvanKrall/cronsul/issues/1#issuecomment-137622248.


Position property for CornerDialog

Corner dialog is a bit different from main dialog in terms of it provides nicer default UI for prompts/confirmations. Having position property, similar to tooltips, would be handy.
Is there any sense in such PR?

Are you thinking it'd be used to change which corner the dialog is anchored to?

Yes, to make it a lightweight alternative to big dialogs.
Would be also nice to have “alignButtons” property.
On Thu, Mar 14, 2019 at 12:09 PM Matt Shwery<EMAIL_ADDRESS>wrote:

Are you thinking it'd be used to change which corner the dialog is
anchored to?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/segmentio/evergreen/issues/520#issuecomment-472938921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASUIxWVOoisAJDbM3NS8cmwChy93lSbks5vWnQogaJpZM4b0Sl6
.

I could come up with PR


add script to test rhel 8.4 virt for image type rhel-edge-commit

added script to test rhel 8.4 virt test for image type rhel-edge-commit.
added kitebot jenkins job

closing this pull request, to sync upstream and downstream code


Markdown "alerts" (admonishments or admonitions) in option descriptions

#2213 added support for rendering github-flavoured "markdown alerts":
> [!TIP]
> This is a tip

Using the mdbook-alerts preprocessor, we now renders this as:

    tip

This is a tip

[!TIP]
This is a tip

However, we render our option descriptions using nixos-render-docs, via the optionsCommonMark function.
https://github.com/nix-community/nixvim/blob/e864f2c9e0cda66b0f419b2c3e36374c177d3712/docs%2Fmdbook%2Fdefault.nix#L13-L18
This takes an options.json file parses its markdown to an AST and spits out commonmark, asciidoc, or manpages (as requested).
Because it uses an abstract syntax tree, recognized-but-invalid symbols (such as [foo] where there's no corresponding [foo]: URL) end up being escaped (\[foo\]) in the resulting commonmark output.
It's also probably not a good idea to use syntax not supported by nixos-render-docs in option descriptions, since it will render poorly in the manpage docs.

As documented here, nixpkgs have adopted an alternative syntax for admonitions:
::: {.warning}
This is a warning
:::

This is based on pandoc’s fenced divs syntax which is intended to be used to add HTML classes or IDs to the rendered div.
nixos-render-docs options commonmark will render the above as **Warning:** This is a warning, which mdbook then renders as:

Warning: This is a warning

Warning: This is a warning
Implemented here.

Rendering
I'm wondering if we need to use a patched nixos-render-docs? We could patch the commonmark render code to something like:
def _admonition_open(self, kind: str) -> str:
    pbreak = self._maybe_parbreak()
    self._enter_block("> ")
    return f"{pbreak}> [!{kind}]\n{pbreak}> "
def _admonition_close(self) -> str:
    self._leave_block()
    return ""

Parsing
We would probably also want to patch the parsing code to accept the GFM syntax? Or alternatively write a preprocessor to convert nixpkgs-style admonitions to GFM-style alerts.
If we don't do one of these, then we'd have to use GFM syntax in user-guides and plugin-descriptions, while using nixpkgs syntax in option descriptions...

Yeah I don't think it's too bad to patch out some programs to improve our documentation

#2218 implements the rendering side, which is the biggest blocker to actually using alerts in option descriptions.

nixos-render-docs uses MarkdownIt to parse option descriptions, so we'll need to dig into that library a little and maybe write a plugin for it.
There's already a handful of related MarkdownIt plugins out there, this one is the most relevant: https://github.com/ByPikod/markdown-it-github-alert (MIT license)
We could look into how they do things, but we can't use the full implementation since we want to tokenise GFM alerts to the tokens nixos-render-docs already uses for its admonitions; e.g. AdmonitionKind.

If consistency is all we're aiming for, perhaps it'd be simpler to implement nixpkg's admonitions syntax in mdbook, or as a pre-build step in our derivation before calling mdbook.
That way we could use a consistent syntax in both places, even if it isn't the syntax I'd personally prefer. :thinking:
If adding GFM-alert parsing to nixos-render-docs is simple, I'd prefer that though.


Edit bash scripts for linkerd and osm

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Tests are being run. So, PR is WIP
Signed commits

[x] Yes, I signed my commits.

Ok seems I found a tiny bug in the install script... maybe fixing that should resolve the trick
https://github.com/meshery/meshery.io/blob/58e355bea9e558f91bc152af4cc8c3eff8a35e06/install#L237

@alphaX86 Thanks for updating this.

@alphaX86 There is still 500 error when deploying app on OSM: https://github.com/layer5io/meshery-smp-action/runs/8124771122?check_suite_focus=true#step:5:44

@gyohuangxin I wonder if its the issue on OSM mesh adapter, could you confirm if its working fine on linkerd side?

@alphaX86 It seems working fines on linkerd side https://github.com/layer5io/meshery-smp-action/runs/8127842569?check_suite_focus=true#step:5:55

Gotcha... So the issue is on osm adapter. I'll fix this in a new PR 👍

@alphaX86 Thanks!


Fix interactive debugger while accessing cell vars

Resolves #913
Resolves #1037

@davidism I think this is ready -- should I target 0.15.x or master?


feat: Option to provide existing private keys.

Changes
Allow users to provide their own private keys when generating credentials through kube-aws render credentials.
This patch was paramount for my team to be able to upgrade from kube-aws 10.1 to kube-aws 12.2. It allowed us to use our existing clusters certificates and upgrade in a smooth fashion.

/assign @davidmccormick

Thanks Dominic!
/lgtm

Please can you also PR this feature to the master branch?  Otherwise this functionality will be lost when 0.13 is released! 🙏

@DominicGunn  Many thanks for your contribution!

Thanks for the merge, PR for master coming right up


Modified project details page with added in-page form

@saggu The old files have an 'underscore' suffix.


Practice App: Feature- Search by tag API

What's up?
As discussed in meeting notes #14 I will create the API for search by tag. Given a tag name this API will return a list of all of the art items tagged with that tag (in json format).

API  endpoint
API Method
API Description

api/searchbytag/<str:tag>
GET
Return all of the art items with the given tag name

To Do

[x] Create new branch feature/search_by_tag off of practice_app.
[x] Add the URL for the endpoint.
[x] Create the corresponding view.
[x] Use api decorators.
[x] Write unittests for the API.
[x] Test them out.
[x] Create Pull request and assign to @KarahanS   as reviewer as stated in meeting notes #14

Deadline
Creation: 15.05.2022 @21.00
Testing: 17.05.2022 @21.00
Review: 18.05.2022 @21.00
Additional Information
No response
Reviewers
@KarahanS

url works with the name of the tag not the id.  If you're having trouble with tag names make sure it is encoded in the url format. Such as # -> %23. For reference https://www.w3schools.com/tags/ref_urlencode.asp
Added urlpatterns = format_suffix_patterns(urlpatterns, allowed=['json', 'html'])  to urls.py in order to give us the option to choose between default Response template and regular json
Extend the url with <?format=json> to get json
If you're having any trouble with your views make sure you added format=None to the arguments

Added tests folder to api.
Created unit tests for search_by_tag.
Ran the test.
Created fake data for the test.
Test compares the result status and the data to make sure they are equal as expected.
Use py manage.py test api to run the test.

Implemented a frontend page, to get the requested tag name with user interface. Please refer to #111

Created pull request #114

Changed/added some error messages for the API.
In accordance with that added some more tests and ran them.
Related commit here.

Practice App Implementation is over. No action is taken, closing the issue.


Maximum Depth of Binary Tree Go

File(s) Modified: 104-Maximum-Depth-of-Binary-Tree
Language(s) Used: Go
Submission URL: _https://leetcode.com/submissions/detail/757498262/_

@Ahmad-A0 here is another solution, please

Thanks, @MaratKhakim!


Crash when first playing AVPlayer video and then recoding audio in AudioKit

I'm having trouble using AudioKit in an app that also uses AVPlayer (for video). In the attached xcode project there are one page with a video (AVPlayer) and one page with a record and play button that uses AudioKit. If the video is played before the AKNodeRecorder, AudioKit crashes with the following message:
2018-04-13 13:18:10.576116+0200 AVPlayer_vs_AudioKit[1854:580107] [mcmx] 338: input bus 0 sample rate is 0
2018-04-13 13:18:10.576361+0200 AVPlayer_vs_AudioKit[1854:580107] [avae] AVAEInternal.h:103:_AVAE_CheckNoErr: [AVAudioEngineGraph.mm:1839:InstallTapOnNode: (err = AUGraphParser::InitializeActiveNodesInInputChain(ThisGraph, *inputNode)): error -10875
2018-04-13 13:18:10.576691+0200 AVPlayer_vs_AudioKit[1854:580107] *** Terminating app due to uncaught exception 'com.apple.coreaudio.avfaudio', reason: 'error -10875'
*** First throw call stack:
(0x183a3ed8c 0x182bf85ec 0x183a3ebf8 0x1893671a0 0x189383f58 0x189393410 0x18940c5e8 0x1893fc6e8 0x104e7db90 0x104d7d170 0x104d7d714 0x18d76e6c8 0x18d88f8a4 0x18d77477c 0x18d8aa1dc 0x18d7f1a48 0x18d7e68f8 0x18d7e5238 0x18dfc6c0c 0x18dfc91b8 0x18dfc2258 0x1839e7404 0x1839e6c2c 0x1839e479c 0x183904da8 0x1858e7020 0x18d8e578c 0x104d801a4 0x183395fc0)
libc++abi.dylib: terminating with uncaught exception of type NSException
AVPlayer_vs_AudioKit.zip

I've downloaded your zip, and I'll have a look, but I really think you should post this question to StackOverflow.


Enable ability to type dates on mobile/tablet

Is your feature request related to a problem? Please describe.
The city of Seattle gets at least one email a week to our help inbox about someone who is unable to figure out how to use the date picker on mobile.  Generally this happens to older individuals who remark that it takes to long to scroll to their birth year and eventually accidentally picks the wrong year or they give up.
Describe the solution you'd like
An easier way to pick/enter dates on mobile.  Such as clicking in the field and manually typing in the date.

Is this a configuration that causes the inability to type the date rather than using the picker?


Add compressed file to existent archive file

What would you like to have changed?
I wonder if it supports to add a new compressed file to for example a bz2 file that already exists.
Why is this feature a useful, necessary, and/or important addition to this project?
Don't want to create a new bz2 file.
Please link to any relevant issues, pull requests, or other discussions.
Similar request: https://unix.stackexchange.com/questions/13093/how-to-add-update-a-file-to-an-existing-tar-gz-archive

You want to add a .bz2 file to an existing archive file?
Or you want to add an existing file to an archive file compressed with bz2?
I'm confused.
But if you want to add a file to an existing compressed tar file (like tar.gz) then you can't really do that without creating a new one. (I actually found the same post on Unix Stack Exchange when I was writing this lib.)
Closing, as I don't think this is actionable without more/new information.


how to import it?

import createAction from 'redux-actions';
or
import { createAction } from 'redux-actions';
??
Why is this missing in the readme?

A quick look at the source code which you can find (here)[https://github.com/acdlite/redux-actions/blob/master/src/index.js] will tell you that you should do
import { createAction }  from 'redux-actions'

@johanneslumpe do you think this should be incorporated into the README, maybe right under the npm install instructions?

Closing this, because the README has been adjusted since this issue.


fix(exthost): Successful install and load extension (flutter/dart) (#2097)

Change property extensionKind to list of strings as described in
https://code.visualstudio.com/api/advanced-topics/remote-extensions#:~:text="extensionKind"%3A ["workspace,extensions fall into this category
The property extensionKind have only
"extensionKind": ["workspace"]
"extensionKind": ["ui"]
"extensionKind": ["ui", "workspace"]
"extensionKind": ["workspace", "ui"]
Therefore the old way "extensionKind":"workspace" or "extensionKind": "ui"
is not valid anymore and has also be updated in InitData.re
Fixes #2097

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@reinies This has to be backward compatible though, so it has to support both list and a string.

Hey @tristil,
thanks for your response. Do you have an example which is using this property as a string. So I could test it while developing.
Thanks you =)

Just for testing purposes I can change it by hand in the flutter package and try to install it. But is there an extension which have it by default? Maybe from the beginning it was never a string but a list.

Ah, no.. prior version 1.4 of the visual studio code release it was only a string. Found on https://code.visualstudio.com/api/advanced-topics/remote-extensions#:~:text="extensionKind"%3A ["workspace,extensions fall into this category
 Note: Prior releases allowed an extension to specify single location as a string and it is deprecated in favor of multiple location support (array).
Therefore you are right. I should change it to support both, list and string.

@reinies Here is one that uses the old format https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync

Thanks @tristil . So I go back to the drawing board and search a way to support both.

Thanks @reinies for the help investigating and fixing this, and @tristil for the review. Really appreciate it!

Thanks @tristil . So I go back to the drawing board and search a way to support both.

Indeed - this was a little confusing for me too (took me a while to wrap my head around the 'decoder' strategy - the approach we use is inspired by decoders in Elm: https://guide.elm-lang.org/effects/json.html)
There's a one_of decoder that takes a bunch of decoders and tries them to see if one works - so it's a good way to handle parsing different kinds of JSON (either a string, or a list of strings) - and then in the single-string case, we can just map it back to a list. I gave this a go here: https://github.com/onivim/oni2/pull/2098/commits/78aaad6f97d5e90e64bcbd530752eb01dc0c7615

Looks like the extension at least gets past parsing now - thanks @reinies and @tristil for the help!

@bryphe great work. Love the solution you build thumbs up


Ignition: Bad networkd translation

Description
One of our .network file had a little issue when launching flatcar. The ignition file looked fine, the problem occurs when installing flatcar with this file.
The problematic line is this one:  Type=!vlan bond bridge, it got translated as Type=!vlan+bond+bridge in the .network file.
We managed to work around it by moving our networkd units to the files section.
Impact
The network interface in question didn't work at all.
Environment and steps to reproduce
FlatCar version: 3227.2.0
Expected behavior
Spaces shouldn't be replaced by plus signs.

Hi, thanks for the report!
It's actually an interesting one - in the translation, url.QueryEscape encodes the content of the networkd:
url.QueryEscape("!vlan bond bridge")
%21vlan+bond+bridge

Which is later decoded by Ignition to:
vlan+bond+bridge

Space is encoded differently (+ or %20) whether it's being in the path or in the query of an URL - Ignition seems to expect the URL to be encoded with from the path.
Will patch the converter and the test case to our coverage.


[bug]  Mobile accordion has text overflow clipping issues

Describe the bug

Which Component?
rh-footer
Steps to reproduce

Go to https://redhat.com
Shrink the browser to mobile mode so that the accordion kicks in.
You should be seeing the white boxes around the headers.

Expected behaviour
We should add the fix to either rh-footer or rh-accordion
Screenshots
No response
Element HTML
No response
Operating System (OS)
macOS
Browser
Chrome
More browser information
No response
Additional Info
No response

This is a super weird issue.  Half of the people see it, half don't.
User 1: visual regression
MacOS: 13.2
Chrome: 111.0.5
User 2: no visual regression
MacOS: 13.2
Chrome: 111.0.5

Not sure if this is the same issue or not

Yes, that's the same issue.  It seems to be an issue with rh-accordion-header::part(text) being set to overflow:auto

yup, good catch @brianferry and @heyMP, this is a scrollbar issue


Support for gatesgarth

Yocto 3.2 Gatesgarth is now release, can someone please review this for meta-iotedge to parse with it?
https://lists.yoctoproject.org/g/yocto/message/51262

@myagley any update on this? Or do you expect me to fix the CI somehow?

@myagley any update on this? Or do you expect me to fix the CI somehow?

@myagley I've fixed CI as well and included changes from https://github.com/Azure/meta-iotedge/pull/58 to make it compatible with newer meta-rust which is needed for compatibility with gatesgarth as well.

@myagley I've fixed CI as well and included changes from https://github.com/Azure/meta-iotedge/pull/58 to make it compatible with newer meta-rust which is needed for compatibility with gatesgarth as well.


Convert as web extension

It is possible to convert it as web extension?
In this way I don't need greasemonkey just for this script?

this!

landed in v0.10.0

BUt is not published yet on addons.firefox and Chrome Webstore right?

The extensions are pending reviewing by someone on those sites. It may take days.

The extension on addons.mozilla.org is up.

Seems that musescore can detect that extension :-(

fixed in v0.11.4

Confirmed now is working :-D


Add docs about getting an IP address of a client who initiated a request

Modifications:

Add Getting an IP address of a client who initiated a request section to server-basics.rst.

Thank you for reviewing!


Migration ToolKit For Virtualization StorageMap Resource Handler

Short description:
Migration ToolKid For Virtualization StorageMap Resource Handler
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified

/lgtm


compile cub/thrust with no unique symbol

In many cases we may want to combine cupy with other frameworks (like pytorch or TensorRT).
when using pytorch and cupy together, since both of them compiled with cub/thrust, there would be a conflict with the static variable.  this may result cuda runtime error (when calling both cupy.argsort and torch.argsort in the same process) or stuck (it's hard to reproduce the stuck behavior here since this happens in my unittest).
this PR fixes this issue and cupy can work well with other frameworks.
the related issue may be #2409.
for detail you can see that https://github.com/NVIDIA/thrust/issues/1401#issuecomment-806403746

Hi @twmht, thank you for the pull-request! I'm still unable to reproduce this issue in my local environment. Could you share your pip freeze output?

@kmaehashi
i can provide the other code snippet which can reproduce the similar errors.

More context: https://github.com/pytorch/pytorch/issues/52663

Could you share your pip freeze output?

Yes indeed. In addition to a reproducer we also need to know your Python env (specifically, the version of each package). For example this issue should be gone if you're on PyTorch 1.9+, but even before 1.9 I've never encountered any issue.

I have created a gist to reproduce the runtime error.
https://gist.github.com/twmht/d9b2ae03162942b1ebc0bed86133ce1f
and my environment is:
absl-py==0.13.0
addict==2.4.0
albumentations==0.4.3
appdirs==1.4.3
astor==0.8.1
bcolz==1.2.1
cachetools==4.2.2
certifi==2019.11.28
-e git+https://github.com/chainer/chainer.git@522e017a18008ee00e39f4ae4b30f4f9db3824b2#egg=chainer
chardet==3.0.4
-e git+https://ming-hsuan-tu@bitbucket.org/acer4smartanywhere/charmander.git@387744dd352fa55dbe09a7bc6dfd48eb202eb237#egg=charmander_v2
charset-normalizer==2.0.4
colorama==0.4.4
contextlib2==21.6.0
cupy==9.0.0
cycler==0.10.0
Cython==3.0a6
dataclasses==0.6
decorator==4.4.1
easydict==1.9
fastrlock==0.6
filelock==3.0.12
future==0.18.2
glog==0.3.1
google-auth==1.35.0
google-auth-oauthlib==0.4.5
graphviz==0.8.4
grpcio==1.39.0
hyperopt==0.1.2
idna==2.9
imageio==2.6.1
imgaug==0.2.6
importlib-metadata==4.6.4
inplace-abn==1.0.11
joblib==0.14.1
json-tricks==3.15.5
kiwisolver==1.1.0
llvmlite==0.37.0
lmdb==0.98
Mako==1.1.1
Markdown==3.3.4
MarkupSafe==1.1.1
matplotlib==3.1.2
-e git+https://github.com/open-mmlab/mmcv.git@21c57d7503a445fbabd998b1583591ce9c39a367#egg=mmcv
-e git+https://github.com/open-mmlab/mmcv.git@21c57d7503a445fbabd998b1583591ce9c39a367#egg=mmcv_full
-e git+https://github.com/open-mmlab/mmdetection.git@d64e719172335fa3d7a757a2a3636bd19e9efb62#egg=mmdet
mmpycocotools==12.0.3
mxnet==1.6.0
netifaces==0.11.0
networkx==2.4
ninja==1.10.2
-e git+https://github.com/microsoft/nni.git@9a4d0d67506f5e1197238344fed858305fbb4494#egg=nni
numba==0.54.0
numpy==1.20.3
nvidia-dali-cuda110 @ file:///home/shared/nfs/acer-share/nvidia_dali_cuda110-1.0.0-2159930-py3-none-manylinux2014_x86_64.whl
oauthlib==3.1.1
onnx==1.10.1
opencv-python-headless==<IP_ADDRESS>
-e git+https://github.com/openpifpaf/openpifpaf.git@5ce0e4b6e2dcc2b1479cd21fb0e8f5cd1ac4c1f1#egg=openpifpaf
Pillow==6.2.2
prettytable==2.1.0
progress==1.6
protobuf==3.17.3
psutil==5.8.0
ptflops==0.5.2
pyasn1==0.4.8
pyasn1-modules==0.2.8
pybind11==2.7.1
pycocotools==2.0.2
pycuda==2019.1.2
pymongo==3.12.0
pyparsing==2.4.6
pysparkling==0.6.1
python-dateutil==2.8.1
python-gflags==3.1.2
python-json-logger==2.0.2
python-rocksdb==1.0
PythonWebHDFS==0.2.3
pytools==2020.1
-e git+https://github.com/NVIDIA/TensorRT.git@eb8442dba3c9e85ffb77e0d870d2e29adcb0a4aa#egg=pytorch_quantization&subdirectory=tools/pytorch-quantization
PyWavelets==1.1.1
PyYAML==5.3
requests==2.26.0
requests-oauthlib==1.3.0
responses==0.13.4
rsa==4.7.2
schema==0.7.4
scikit-image==0.16.2
scikit-learn==0.22.1
scipy==1.4.1
simplejson==3.17.5
six==1.13.0
sphinx-glpi-theme==0.3
tabulate==0.8.9
tensorboard==2.6.0
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.8.0
tensorboardX==2.0
tensorrt @ file:///home/shared/nfs/acer-share/TensorRT-<IP_ADDRESS>/python/tensorrt-<IP_ADDRESS>-cp37-none-linux_x86_64.whl
terminaltables==3.1.0
thop==0.0.31.post2005241907
threadpoolctl==2.2.0
torch @ file:///home/shared/nfs/acer-share/torch-1.8.0%2Bcu111-cp37-cp37m-linux_x86_64.whl
torchvision @ file:///home/shared/nfs/acer-share/torchvision-0.9.0%2Bcu111-cp37-cp37m-linux_x86_64.whl
tqdm==4.41.1
-e git+https://ming-hsuan-tu@bitbucket.org/acer4smartanywhere/treecko.git@7e2154ea28815de961bcdc6c593a6c4f522bc28d#egg=treecko
typing==<IP_ADDRESS>
typing-extensions==<IP_ADDRESS>
urllib3==1.25.8
wcwidth==0.2.5
websockets==9.1
Werkzeug==2.0.1
yapf==0.31.0
zipp==3.5.0

Thanks for the info! I could reproduce the error:
RuntimeError: merge_sort: failed to synchronize: cudaErrorIllegalAddress: an illegal memory access was encountered

with a fresh pyenv:
% pip install 'torch==1.8.0' -f https://download.pytorch.org/whl/cu111/torch_stable.html
% pip install 'cupy-cuda111==9.0.0' -f https://github.com/cupy/cupy/releases/v9.0.0

and also confirmed this patch fixes the issue.
According to the gcc docs, the side effect caused by this option is dlclose to be ignored:

-fno-gnu-unique
On systems with recent GNU assembler and C library, the C++ compiler uses the STB_GNU_UNIQUE binding to make sure that definitions of template static data members and static local variables in inline functions are unique even in the presence of RTLD_LOCAL; this is necessary to avoid problems with a library used by two different RTLD_LOCAL plugins depending on a definition in one of them and therefore disagreeing with the other one about the binding of the symbol. But this causes dlclose to be ignored for affected DSOs; if your program relies on reinitialization of a DSO via dlclose and dlopen, you can use -fno-gnu-unique.

but I guess this is harmless as Python extensions will not be dlclosed until process termination.
Although the original problem seems almost resolved in PyTorch 1.9.0 (by wrapping cub namespace: https://github.com/pytorch/pytorch/issues/57505), I think it's better to merge this PR as other Python libs may be linking to CUB/Thrust.

Not only pytorch, TensorRT plugins also link to cub/thrust  (https://github.com/NVIDIA/TensorRT/tree/main/third_party).

/test

Merging as test failures are unrelated.
Thanks, @twmht!

Thanks, @twmht!


Cartographer map for 5 silver locks up the game

So I've had an issue with the cartographer villager when he's spawned in (egg or natural) with a trade of 5 silver for a map. It gives him full (or maybe over full) bar and makes everything freeze up, quitting save loops the world needing to be task managered, and when going back on it has rolled back a few actions. So far in my test it's only them. Not even shepherd with a similar trade (5 silver for shears) only gives half bar
here's the log
https://mclo.gs/tLVlrNQ

Are you sure this isn't a duplicate of https://github.com/wisp-forest/numismatic-overhaul/issues/93 ?

It seems it can be. But then the only fix is to edit the mod itself. So the solution would be to make a compat mod or add Yung's structures in a mod update.


Reconverge

Handle problems where reconverging constantly thinks the cluster has changed. This was happening because the test for a change didn't include default options whereas the server's response had default options, so the configs never matched. Thanks to Andy from the community slack, I came up with some code to compare only the necessary options.
Fixed a problem that appears only in TK where *.vagrantup.com hosts are ignored, but still processed later on.
Also re-implemented the rs_member_ips that was removed in 6f3f2ca and fixes #179.
As a result of this, test kitchen replica tests run again:
sean~/play/mongodb (reconverge *)$ chef exec kitchen verify replicaset3-centos-73
-----> Starting Kitchen (v1.19.2)
-----> Setting up <replicaset3-centos-73>...
       Finished setting up <replicaset3-centos-73> (0m0.00s).
-----> Verifying <replicaset3-centos-73>...
       Detected alternative framework tests for `inspec`
       Loaded tests from {:path=>".Users.sean.play.mongodb.test.integration.replicaset3.inspec"}

Profile: tests from {:path=>"/Users/sean/play/mongodb/test/integration/replicaset3/inspec"} (tests from {:path=>".Users.sean.play.mongodb.test.integration.replicaset3.inspec"})
Version: (not specified)
Target:  ssh://vagrant@<IP_ADDRESS>:2202

  Service mongod
     ✔  should be installed
     ✔  should be enabled
     ✔  should be running
  Bash command
     ✔  mongo --eval "rs.status()" | grep name | wc -l exit_status should eq 0
     ✔  mongo --eval "rs.status()" | grep name | wc -l stdout should match "3"
  Bash command
     ✔  mongo --eval "rs.status()" exit_status should eq 0
     ✔  mongo --eval "rs.status()" stdout should match /.*^connecting to: test\n\{\n\t{1}"set" : "kitchen"\,$.*/
     ✔  mongo --eval "rs.status()" stdout should match /.*^\t{3}"_id" : 0\,\n\t{3}"name" : "mongo1:27017"\,$.*/
     ✔  mongo --eval "rs.status()" stdout should match /.*^\t{3}"_id" : 1\,\n\t{3}"name" : "mongo2:27017"\,$.*/
     ✔  mongo --eval "rs.status()" stdout should match /.*^\t{3}"_id" : 2\,\n\t{3}"name" : "mongo3:27017"\,$.*/

Test Summary: 10 successful, 0 failures, 0 skipped
       Finished verifying <replicaset3-centos-73> (0m0.52s).

lgtm 👍

Thank you!


Please implement Overlapping in tiling.. Remi knows what to do!

Can you still put a little description of the problem plz.


Upgrade to go1.18.7

This will have effect immediately, so I'm holding off merging it until the datadog-agent PR is merged.


Create [US]-15-jiaojiaofan.md

I just copy from Zheng and still editing.

Could you help me add? I have finished all, I guess.


Strategy for triaging issues

Lodash has an interesting strategy for handling their github issues: here
In short:

Feature requests are closed issues with feature label and votes needed label, and a 👍 emoji reaction
Bugs are open issues tagged with bug label

For a project like Moto where there are an endless number of feature requests (every time AWS adds a service/endpoint), this feels very appealing. It would be great for us to be able to separate out the triage work. Establishing an easy way to give prioritization feedback would also be very helpful.
Any downsides? cc @JackDanger @terrycain

This sounds really good. I don't know if there's an easy way to automate this but it's a great policy and I'd be happy to help triage things like this.

I don't know if there is a way to automate it, but I'm optimistic it will be much easier to stay on top of things and keep them in order.
I think it will also require us to have a better definition of bugs. I'm leaning toward bugs being regressions only (or other egregious mistakes on our part).

Thats really cool. But yes we'd need to properly define bugs, and might need to rename feature requests every now and again so they're easily spotted/searchable. And also be super clear in the readme about how to go about pleading for features.

It has been a year and I'm liking this more and more. We get so many feature requests that it seems impossible to maintain a project like this without a better strategy.
I'm going to work on a PR with an explanation of a philosophy in the README + CONTRIBUTING. I'll tag this issue once I create that. If everyone agrees on that, then we can work on some scripts to cleanup existing issues.

Sounds good to me
On Tue, 9 Jul 2019, 05:06 Steve Pulec<EMAIL_ADDRESS>wrote:

It has been a year and I'm liking this more and more. We get so many
feature requests that it seems impossible to maintain a project like this
without a better strategy.
I'm going to work on a PR with an explanation of a philosophy in the
README + CONTRIBUTING. I'll tag this issue once I create that. If everyone
agrees on that, then we can work on some scripts to cleanup existing issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spulec/moto/issues/1659?email_source=notifications&email_token=AAPE6XOBRBK7T4D5PEL6QIDP6QFGHA5CNFSM4FCRSHFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZPAPIQ#issuecomment-509478818,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPE6XLPN6RNTIIL5NXBGFTP6QFGHANCNFSM4FCRSHFA
.

Draft opened here: https://github.com/spulec/moto/pull/2314
Feedback appreciated!

Since this discussion, we've gotten much better at dealing with incoming feature requests. Issues are now properly tagged, and the total list is much smaller. So I feel like this is no longer necessary, and the drawback of having 'invisible' issues, and having to educate users on why, outweighs the positive effects in my mind.
I'll close this - but feel free to correct/discuss if you disagree!


Store profile pictures

Store profile pictures using SupaBase storage then add a profilePicUrl field in account DB
update tweet display component to integrate that

way too expensive for now


Buttons checkbox and radio should use appropriate markup

I read that we can now add a checkbox or a radio behavior to a button group (http://markdotto.com/bs2/docs/javascript.html#buttons)
That's great, but I think it would be better if we could use as underlying markup actual HTML checkboxes and actual HTML radio buttons, i.e :

It implies re-styling completely the input field.
This would allow to use button groups in forms.
And no javascript would be required to get the wanted behavior, the browsers would be handling it.

This is exactly how the team at @Harvest wrote UniformJS.

I wanted to use the checkbox button groups just yesterday when I realized that indeed those are just styled buttons and that I needed a whole bit of HTML and jQuery underneath to actually make them work.
I gotta say I was indeed kind of disappointed and since we're already including a .js to make those buttons work I think it would be a good idea to already put the underlying markup and JS in Bootstrap.

Wow, I was sleepy when I wrote that comment.
I meant @harvesthq who wrote Chosen.
See: https://github.com/harvesthq/chosen
This is also true of Uniform JS.
See: http://uniformjs.com/

We'll take a look at this in a future release, but not for 2.0—too crunched for time right now.

I agree with the sentiment of using actual form elements.
Given that this won't be ready for 2.0, does anyone have examples/documentation of how to make use of the buttons?

For checkbox you can get away using a label wrapping the desired input.
.btn input {
    display: none;
}

<label class="btn" data-toggle="button"><input type="checkbox" />Toggle meh!</label>

You can rely on server side to assign the active class to the label.
Radios are a bit harder... Some js is required to sync button states.

@Steren here's an actual implementation http://jsfiddle.net/charettes/WUXjX/11/

And a fully css one http://jsfiddle.net/charettes/SauLj/.

the css exampel works great


New release?

It's been 6 months since the last published npm release. Any chance we could get an updated release? I see there's a release.yml that does the github release, it would good to include the npm release as part of that to reduce friction as much as possible.

Any update on when this will release? Could really use some of the new icons. 🙏

Done

https://github.com/microsoft/vscode-codicons/releases/tag/0.0.36
<EMAIL_ADDRESS>


Inconsistent RequestTelemetry.Name in AspNetCore when using UseExceptionHandler or UseStatusCodePagesWithReExecute

List of NuGet packages and version that you are using:

Microsoft.ApplicationInsights.AspNetCore 2.22.0

Runtime version: net8.0
Hosting environment: Windows

Describe the bug
When using UseExceptionHandler and/or UseStatusCodePagesWithReExecute in an AspNetCore application, the values of RequestTelemetry.Name are inconsistent.
The logged request name in Application Insights for the same url/controller action
is different depending on whether the request was unauthorized, an exception was thrown or otherwise status code 400-599 was returned.
This is really unexpected and makes analyzing failures in Azure Portal very difficult if not impossible, because Application Insights user interface shows requests grouped by their name.
Related to this issue #1555, but it's closed. So I'm creating this issue with detailed information and a repo so it will hopefully be addressed this time.
To Reproduce
I have created a simple repo to reproduce the behavior here:
https://github.com/ohlus/app-insights-request-name
The home page shows a few links that lead to differences in the logged RequestTelemetry.Name by calling simple MVC controller actions
and a simple custom middleware to show that the behavior is also different without using routing/endpoints.

/Test/OnlyPostSupported action is decorated with [HttpPost].
Based on the name, the actions/middleware will either return an empty response with status code set or throw an exception.
If I comment out UseExceptionHandler and UseStatusCodePagesWithReExecute, then even without re-execution there is a difference in the request name:

url
resultCode
name
OK
expected name

https://localhost:7266/Test/AuthorizationPolicy
401
GET /Test/AuthorizationPolicy
❌
GET Test/AuthorizationPolicy

Note the leading /. For controller actions I expect that the / won't be there,
because then requests to this one specific action will be in two different groups.

Really hoping to see this fixed. It makes it incredibly hard to troubleshoot issues when everything gets lumped together. Does anyone have a workaround for this until there is an official fix?

@JarrodJ83 This is the current state of my workaround. The idea is to use a middleware that generates and saves the request name to a HttpContext feature on the first execution of the request pipeline. If the pipeline is being re-executed, it detects it because of the already set feature on the HttpContext.
Then after the _next was executed it sets the RequestTelemetry.Name. It can't do that at the beginning, because RequestTelemetry feature isn't available yet.
I'm not claiming this is 100% correct, but so far I haven't found anything better.
Perhaps the right solution would be possible using the DiagnosticListener, but I haven't spent too much time investigating it.
I hope this helps you and others. If anyone has an opinion on this, I'm interested 😄
app.UseRouting();
app.UseAppInsightsRequestTelemetryMiddleware(); // This must be right after UseRouting.

public static class AppInsightsRequestTelemetryMiddlewareExtensions
{
    public static IApplicationBuilder UseAppInsightsRequestTelemetryMiddleware(this IApplicationBuilder builder)
        => builder.UseMiddleware<AppInsightsRequestTelemetryMiddleware>();
}

public sealed record RequestTelemetryNameFeature(string? RequestName)
{
    public static readonly RequestTelemetryNameFeature NullRequestName = new(RequestName: null);
}

public sealed class AppInsightsRequestTelemetryMiddleware
{
    private readonly RequestDelegate _next;

    public AppInsightsRequestTelemetryMiddleware(RequestDelegate next)
    {
        _next = next;
    }

    public Task InvokeAsync(HttpContext httpContext)
    {
        // detect re-execution
        if (httpContext.Features.Get<RequestTelemetryNameFeature>() is not null)
        {
            return _next(httpContext);
        }

        var name = AppInsightsRequestTelemetryHelpers.GetRequestNameFromHttpContext(httpContext);
        if (string.IsNullOrEmpty(name))
        {
            httpContext.Features.Set(RequestTelemetryNameFeature.NullRequestName);

            return RunNextAndSetNameAsync(httpContext);
        }

        httpContext.Features.Set(new RequestTelemetryNameFeature(name));

        return RunNextAndSetNameAsync(httpContext);
    }

    private async Task RunNextAndSetNameAsync(HttpContext httpContext)
    {
        try
        {
            await _next(httpContext);
        }
        finally
        {
            SetRequestTelemetryName(httpContext);
        }
    }

    private void SetRequestTelemetryName(HttpContext httpContext)
    {
        if (httpContext.Features.Get<RequestTelemetryNameFeature>() is { RequestName: string name }
         && httpContext.Features.Get<RequestTelemetry>() is { } requestTelemetry)
        {
            requestTelemetry.Name = name;
        }
    }
}

This helper generates the request name. Because this library doesn't expose the implementation at NETCORE/src/Microsoft.ApplicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs, it needs to reimplement it:
public static class AppInsightsRequestTelemetryHelpers
{
    public static string? GetRequestNameFromHttpContext(HttpContext httpContext)
    {
        var nameCandidate = GetNameFromRouteValueDictionary(httpContext.Request.RouteValues)
                         ?? httpContext.Request.Path.Value;

        if (string.IsNullOrEmpty(nameCandidate))
        {
            return null;
        }

        var name = httpContext.Request.Method + " " + nameCandidate;
        return name;
    }

    public static string? GetNameFromRouteValueDictionary(RouteValueDictionary routeValues)
    {
        // same logic that AI dotnet uses:
        // NETCORE/src/Microsoft.ApplicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs

        if (routeValues.Count <= 0)
        {
            return null;
        }

        string? name = null;
        routeValues.TryGetValue("controller", out var controller);
        var controllerString = (controller is null) ? string.Empty : controller.ToString();

        if (!string.IsNullOrEmpty(controllerString))
        {
            name = controllerString;

            if (routeValues.TryGetValue("action", out var action) && action != null)
            {
                // ReSharper disable once RedundantToStringCall
                name += "/" + action.ToString();
            }

            if (routeValues.Keys.Count > 2)
            {
                var sortedKeys = routeValues.Keys
                    .Where(
                        key => !string.Equals(key, "controller", StringComparison.OrdinalIgnoreCase)
                            && !string.Equals(key, "action", StringComparison.OrdinalIgnoreCase)
                            && !string.Equals(key, "!__route_group", StringComparison.OrdinalIgnoreCase))
                    .OrderBy(key => key, StringComparer.OrdinalIgnoreCase)
                    .ToArray();

                if (sortedKeys.Length > 0)
                {
                    var arguments = string.Join('/', sortedKeys);
                    name += " [" + arguments + "]";
                }
            }
        }
        else
        {
            routeValues.TryGetValue("page", out var page);
            var pageString = (page is null) ? string.Empty : page.ToString();
            if (!string.IsNullOrEmpty(pageString))
            {
                name = pageString;
            }
        }

        return name;
    }
}

I've also used a similar method but as a TelemetryInitializer - yours seems more robust. I found this chasing down 404 errors that show up under /Error from the status code handler.
This really needs an official solution - shouldn't be this difficult for a premium product


docs: remove docs for our promql path

What's Changed in this PR
Removes our own /promql API from docs to avoid misunderstanding.
Checklist

[x] Please confirm that all corresponding versions of the documents have been revised.
[x] Please ensure that the content in summary.yml matches the current document structure when you changed the document structure.
[ ] This change requires follow-up update in localized docs.

I think it's not confusing currently because the documents describe it clearly. We'll refactor the user guide, leaving it right now would be good.


A custom workflow

Hi @CarlosBarroso! I saw your post in the Community Forum. For some reason, the bot is not responding as expected. I think the reason may be the capitalization of your file name. Could you please rename the file to be lowercase, like
.github/workflows/approval-workflow.yml?
I have manually moved the bot on to the next steps, but by doing that, I also stopped the bot from posting the next step instructions. I'll include them here, so you can move on in this course. 😊  Please let me know if you have any other questions, or get stuck again.

Add a job
Great work! Let's get some more practice with jobs. Apply the suggested change below or follow the instructions.
In a later step, we'll use an action that adds a label to any pull requests after a preset number of approvals. These labels could be used as a visual indicator to your team that something is ready to merge, or even as a way to use other actions or tools to automatically merge pull requests when they receive the required number of approvals.

Step 16: Create an approval job in your new workflow
:keyboard: Activity: In your new workflow file, create a new job that'll use the community action

Edit your newly created workflow file
Create a new job called labelWhenApproved.on: pull_request_review
jobs:
  labelWhenApproved:
    runs-on: ubuntu-latest

Commit your changes to this branch

I'll respond when you commit something to this branch.


Merge latest new_rollup

@dmihal I merged the latest changes of the new_rollup branch into erc777 so its ready.
Only merge conflict I needed to resolve was https://github.com/OffchainLabs/arbitrum/pull/763

Closing the PR as there is no more need to merge in the changes as described in https://github.com/OffchainLabs/arbitrum/pull/744#issuecomment-780711966


Add husky and lint-staged

Pull Request Test Coverage Report for Build 1305

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1304:
0.0%

Covered Lines:
41

Relevant Lines:
41

💛  - Coveralls


Fix extrude

This PR enables extruded geometry mappings on GPUs.

The fastd² version of curve_props now returns the correct length normal and velocity zero vectors.
The \ operator now uses a special non-allocating method for a=SMatrix{2,3}. I added a test set for this and will put together a PR for StaticArrays.

Fixes #16


s3tests_boto3/test_sts: Changing code for proper cleanup

Signed-off-by: Kalpesh Pandya<EMAIL_ADDRESS>

Passing teuthology: https://pulpito.ceph.com/kapandya-2022-01-18_06:29:54-rgw:sts-wip-rgw-sts-error-distro-basic-smithi/


Can't throw AssertionError because in practice it hides the problem.

In practice, as soon as I get an AssertionError I have to change it for something else because it just hides the problem. I mean, in tests or logs, when I print an AssertionError I should get some useful information.
Suppose I do:
if (x > 64) throw AssertionError(x);

It just tells me:
Assertion failed

What's the point of allowing a message in its constructor, if it just throws it away?
Instead, it should say:
Assertion failed: 78

I propose its toString() method should be:
String toString() => "Assertion failed with message: $message";

What tool are you using?  E.g., web / native?  debug / prod? - I don't think they are consistent here.

@vsmenon Depending on the tool, since the toString() doesn't print the message, the tool could check if the error is of type AssertionError and then go fetch the message and print it. But I don't think we should depend on the tool. It could be, for example, some logger in a cloud-function that we have no control of. The only piece of information we are reasonably sure to always get is the toString() output.

Sorry, I meant that different compilers / runtimes themselves are implementing the toString() differently.  Which are you testing?  The VM (AOT or JIT)?  DDC?  Dart2JS?
I'd expect the debug runtimes to give good messages.  The prod ones may not (as they are typically run in a mode where asserts are disabled anyway).

That said, I'd expect the actual message to be in all of them.

I'm developing for Flutter, running a test, in Windows desktop, IntelliJ Community.
class AssertionError extends Error {
  /** Message describing the assertion error. */
  final Object message;
  AssertionError([this.message]);
  String toString() => "Assertion failed";
}

Duplicate of #40245.
The change has already landed, https://dart-review.googlesource.com/c/sdk/+/132640, so it should show up in your Dart "real soon now".


Not being executed inside promise callback

Here's a snippet of my code:
getUser(authData)
                        .then(function (data)
                        {
                            console.log(data); // this is logged to console as expected

                            RoleStore.defineRole('USER', function (roleName, transitionProperties)
                            {
                                console.log('define user role'); // this is not logged to console

                                return true;
                            });

console.log(RoleStore.getStore()); // empty Object
                        });

Please help

Hi @masterspambot ,
Thank you for the speedy response, that was quite helpful.
I do have another quick question about something I was not able to find in the documentation.
What is the expected redirectTo behavior in the following scenario:
$stateProvider
  .state('agenda', {
    [...]
    data: {
      permissions: {
        only: ['MODERATOR'],
        except: ['SUBSCRIBER'],
         redirectTo: {
           MODERATOR: 'agendaList',
           default: 'login'
        }
      }
    }
  })

I know we can specify the state to redirect the user who does not have the MODERATOR role, but is there also a way to specify the state to redirect the user who has the SUBSCRIBER role?
Thanks so much,


How to create one-to-one relation?

Hi @pikhovkin
We don't support defining the relation type as we try to be close to what is the database structure.
Yet, we discussed in https://github.com/azimuttapp/azimutt/issues/166 the possibility to show relations as one-to-one when they meet the criteria (link to a unique column).
Still not done yet but it's on our list.
What do you think about it?

Hey @loicknuchel,
I was confused^1 by the criteria you mentioned above and probably misunderstood what you meant with link to a unique column. As I may not be the only person, here's a how I would name the criteria for showing a one-to-one relation:

foreign key constraint defined on/placed on/attached to a unique column^2
or
link from a unique column^2

Would you agree? I'm sorry, I haven't gotten around to contribute any code to azimutt yet. It's on my bucket list of things to do before I die, but I have no idea when that will be. Keep up the great work!
^1: because foreign key constraints must point to a unique column^2, otherwise it's not a foreign key.
^2: or a unique column group enforced by a composite unique constraint

Hi @michi-zuri
You're right, I wrote too quickly, it's not a "link to a unique column" but a foreign key with a unique constraint.
In fact, both side of the relation should have a unique constraint, but it's often the case for the target as we link to primary keys ^^
On the "unique column group", you are right, but for now Azimutt handles composite unique constraints but not composite foreign keys (big refacto in the data model for this ^^).
Don't worry about your contribution ;)
You can do it when you have time and you can ping me if you need some help to get started.
++


during dev-deploy create neardev/dev-account.env for future env-cmd usage

Creates a second file in the neardev folder. This file is structured like an environment variable file that stores:
CONTRACT_ID=dev1234567890123 instead of just the account id.
This is the first step in enabling us to allow Windows users to use some of our quick-start tools like create-near-app. There will be forthcoming pull requests in create-near-app for this.
Essentially we will be loading this new file as an environment variable so that parcel can run on Windows.
One of the issues we currently have with quick-start tools like create-near-app is we're cating the previous file (neardev/dev-account) in order to set an environment variable. I have reason to believe this will never work for Windows, but we can leverage cross-platform dependencies like cross-env and env-cmd if we use an approach where we can load a file for this instead.
That's the whole picture, and this PR is the first step toward that.

Travis getting "Error:  { Error: Transaction nonce 3197 must be larger than nonce of the used access key 3197" which is unrelated to this PR.


added profile pic for user model, updated code to upload profile pic in user edit, few changes in list pages

#101

Coverage decreased (-0.9%) to 64.542% when pulling 937ddb2bb1b6d50da11098bd0a6d0432dd5f0134 on test_fixes into 56c9a74461a870db7b3d5949b9a2d35ca41d7bd1 on master.


[BUG]: CUDA test suite fails

Description
When running the CUDA test suite, the following error is encountered:
icicle/icicle/primitives/test_kernels.cuh:4:10: fatal error: ../curves/bls12_381.cuh: No such file or directory
Reproduce
Follow the instructions for building and testing in the README
Expected Behavior
The tests should run and pass
Environment
Please complete the following information:
OS + Version:
Cargo Version:
GPU type:
Additional context

As commented on Discord, I will start working on this.


Disable SSL by default

The microgrid API does not use SSL by default, so it makes sense to disable it by default in the client. This was the behavior in previous versions, and it was changed by mistake in a previous commit.
Also prepare the release notes for the next patch release.

Tested against the sandbox.

I just sneaked in a dependabot fix too. Will force merge as this is all pretty trivial and want to make the release soon so we can release the SDK too.


Corner icon adjustment

Adds padding to the (?) corner button
addresses https://github.com/macadmins/nudge/issues/246

wtf - why is Utils.swift in there...... ugh