Initial re-implementation for Double.parseDouble/Float.parseFloat

Hi @konsoletyper . This is initial (and therefore unfinished) implementation for Double.parseDouble improvement. Code was borrowed from https://android.googlesource.com/platform/libcore/+/d5e2817/luni/src/main/java/java/lang/Double.java Android source repository (Apache 2.0). Test was borrowed from there as well. So, test shows that we have issues in Double.toHexString (suppose will be fixed separately) and with parsing. I reused implementation and replaced native implementation to the most naїve approach instead of real implementation (should be transformed from C++ https://cs.android.com/android/platform/superproject/+/master:libcore/luni/src/main/native/java_lang_StringToReal.cpp;l=92;drc=master ). Is it worth continuing working on this PR or stop here?
It appears that even naїve implementation covers most of the tests that currently present.

There's already existing implementation that works quite well except for few corner cases. Isn't it better to fix it rather than to replace everything by another implementation?
Current implementation of Double.parseDouble uses common engine to turn decimal exponent + decimal mantissa into IEEE 754 binary exponent + binary mantissa (see DoubleSynthesizer). The same engine used by TDecimalFormat, so whenever you change something, you should also take care of TDecimalFormat
This algorithm uses naive approach that was implemented in TeaVM quite some time ago. Looks like acting in terms of IEEE 754 doubles does not provide enough accuracy, so I replaced everything with integer math. Using long to store mantissa gives 64 bits instead of 52 bits.
This is not only inaccurate, but also slow approach. Computing 10^x every time may be slow compared to using tables.
Recently, I improved my implementation to use compile-time-calculated 100%-precise tables to convert between decimal and binary mantissa (I used BigInteger, then cut first 64 bits). This gave much far better result, not 100% accurate though.
You should test any changes there WRT consistency between parseDouble/Double.toString (i.e. feed result of Double.toString to parseDouble for large amount of random numbers). After my recent changes there's approx. 0.2% of numbers that give only 1 ULP inaccuracy (i.e. binary mantissa differs only by 1). Did you test your changes this way?

Here is your comment https://github.com/konsoletyper/teavm/issues/735#issuecomment-1718063424 . According to it you managed to produce 99,5% and 96,5% accurate parse for doubles/floats respectively. This just means that it's (I'm not saying impossible) complicated and unneeded to spend efforts to improve custom self-written algorithm. It's better to reuse common knowledge shared under Open-Source-friendly license. Together with the code it comes with applicable tests. I understand that it's pretty challenging, but it's not worth your/my time.
Thanks for the info, I didn't consider it in beginning. Still, formatting is about toString, not parsing. Then I suppose that changes for toString also should be included to be consistent. In Android test suite only 4 tests failed in JDK, so I'm assuming that this implementation is pretty similar and precise.
This naїve approach was used just to make code working. Check TODO link. There is C++ code that uses same tables approach under the hood. It just needs to be rewritten in Java.
See 3.
See 3.
Sure, it should be tested well, basic question is unanswered: whether continue working on this PR or just drop it? I didn't test my changes WRT consistency because I don't want to prepare full PR (this is not 1-day work obviously) which later will be refused.

This just means that it's (I'm not saying impossible) complicated and unneeded to spend efforts to improve custom self-written algorithm.

No, I can't agree. At least, after all my efforts I can't let you throw away my almost perfectly working code.

It's better to reuse common knowledge shared under Open-Source-friendly license.

Yes, and get the code that neither you, nor I understand. And moreover, you need to somehow port it from C++.

Sure, it should be tested well, basic question is unanswered: whether continue working on this PR or just drop it

In this form drop it. You can take some tests from Harmony/Android implementation to find issues in current implementation, as well as fix these errors in current code. You can read some papers about decimal-to-binary conversion to improve accuracy and fix current algorithm. But in this current it's almost impossible to review.


Prince/ translation workflow security mitigation

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

@prince-deriv
Can the below be implemented additionally like in the below reference link snippet instead of referencing the ${{ github.event.workflow_run.head_branch }}' directly in echo.
It's not a good security practise to inject a variable directly inside the '. The method has string escaping built in. This would mean to implement something like this
env: BRANCH_NAME: ${{ github.event.workflow_run.head_branch }} run: | echo "pUshIng strings and translations from $BRANCH_NAME"

https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#good-practices-for-mitigating-script-injection-attacks
Also having the CLEAN_BRANCH sanitization would be additional security protection after the initial pre push security checks.


Add AppSignal

Adds the appsignal gem
Configure to be active on production, and inactive on all other environments
Update Fargate task for the production web server to pull the APPSIGNAL_PUSH_API_KEY variable from AWS Parameter Store (which I have added manually)

 CHORE: Developers notified of 500 error in application


test: more meaningful AnimatedNumber component test

Summary

This was presented during Developer Meeting October 30th.  The goal was to ask developers to re-consider the use of toMatchSnapshot which doesn't really give enough information what the component AnimatedNumber is doing and why it's rendering the way it did.
In order to get coverage % when running this test, you'd have to temporarily update the jest.config.js file:
-    coveragePathIgnorePatterns: ['/node_modules/', '/components/', '/screens/'],
+    coveragePathIgnorePatterns: ['/node_modules/'],

npm run test app/components/animated_number/index.test.tsx -- --collectCoverageFrom=app/components/animated_number/index.tsx --coverage --watch

 PASS  app/components/animated_number/index.test.tsx
  AnimatedNumber
    ✓ should render the non-animated number (155 ms)
    ✓ should removed the non-animation number after getting the correct height (7 ms)
    ✓ should switch to the animated number view (4 ms)
    ✓ KNOWN UI BUG: should show that there will be an issue if the text height changes, due to the non-animated number view has been removed (3 ms)
    should show the correct number of animated views based on the digits
      ✓ should display 1 view(s) for 1 (1 ms)
      ✓ should display 2 view(s) for 23 (3 ms)
      ✓ should display 3 view(s) for 579 (2 ms)
      ✓ should display 4 view(s) for -123 (3 ms)
      ✓ should display 4 view(s) for 6789 (3 ms)
      ✓ should display 5 view(s) for 23456 (4 ms)
    should show the correct number
      ✓ should display the number 123 (3 ms)
      ✓ should display the number 9982 (4 ms)
      ✓ should display the number 12345 (4 ms)
      ✓ should display the number 901876 (6 ms)
      ✓ should display the number -157 (2 ms)
    should rerender the correct number that it animates to
      ✓ should display the number 146 (4 ms)
      ✓ should display the number 144 (4 ms)
      ✓ should display the number 1 (3 ms)
      ✓ should display the number 1000000 (6 ms)
      ✓ should display the number -145 (5 ms)

=============================== Coverage summary ===============================
Statements   : 100% ( 37/37 )
Branches     : 100% ( 16/16 )
Functions    : 100% ( 13/13 )
Lines        : 100% ( 35/35 )
================================================================================

Ticket Link

Checklist

[X] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.
[ ] Have run E2E tests by adding label E2E iOS tests for PR.

Device Information
This PR was tested on:
Screenshots

Release Note

@rahimrahman Maybe I am missing something, but aren't we missing the snapshots on the PR? I am surprised the CI did not yell about that. Maybe something we should look into.

@rahimrahman Maybe I am missing something, but aren't we missing the snapshots on the PR? I am surprised the CI did not yell about that. Maybe something we should look into.

I thought I copied this test from another test somewhere, but for the life of me, I couldn't figure out where now.
Or, I wrote the original test to showcase how toMatchSnapshot() could be deceiving.  With the thought of creating the newer test as educational purpose.

@yasserfaraazkhan I didn't make any major changes to animated_number/index.tsx other than adding testID and using a better index for the views.  I don't think it warrants even regression testing, but if you feel the need, do specify.


Trying to pass Data from a Table to a vuestrap modal component.

Im trying to pass two variables from a table within one child vuestrap modal component. That modal will be reused from all the TD's of the table where the checkbox calls the modal. but Im not understanding the logic to do that. I have opened a question, I would apreciate if you can help.  https://laracasts.com/discuss/channels/code-review/how-to-pass-data-to-a-vuestrap-component
http://stackoverflow.com/questions/33149197/how-to-pass-data-to-a-vuestrap-modal-component

as Im reading of course the following is wrong but im trying to figure it .

                @{ {slide.name}}
                @{ {slide.message}}

                <input type="checkbox"  v-on="click:showMod = true| PassValueToModal(slide.name,slide.message)" v-model="slide.published" >

new Vue({
el:'#ordertbl',

components: {
    'modal':VueStrap.modal
},

data: {
    showMod: false,
    sortKey: '',
    reverse:false,

},
modal:{

    data: function () {
       return {
           name: '',
           message: ''
       }
    }
},

ready:function(){

    this.fetchMessages();

},
methods:{

        fetchMessages:function() {

        this.$http.get('/admin/slider',function(slides){

            this.$set('slides',slides);

        });
    },

       PassValueToModal:function(name,message){
        this.modal.name = name;
        this.modal.message=message;

    }

}

});
and at the html
Nothing works, but Im trying to get help about it , please help :D @yuche

here is a screen of what I have  http://workupload.com/file/92Q7vehU

I want to do the following
$('#exampleModal').on('show.bs.modal', function (event) {
  var button = $(event.relatedTarget) // Button that triggered the modal
  var recipient = button.data('whatever') // Extract info from data-* attributes
  // If necessary, you could initiate an AJAX request here (and then do the updating in a callback).
  // Update the modal's content. We'll use jQuery here, but you could use a data binding library or other methods instead.
  var modal = $(this)
  modal.find('.modal-title').text('New message to ' + recipient)
  modal.find('.modal-body input').val(recipient)
})

which is pass the data from my tds to the reusable Modal.
the fact is dont know how to acces it.

I solved, it, thanks anyway


API Convert CMS forms to bootstrap

Merge with:

CMS PR https://github.com/silverstripe/silverstripe-cms/pull/1550
Asset admin PR https://github.com/silverstripe/silverstripe-asset-admin/pull/205
SiteConfig PR https://github.com/silverstripe/silverstripe-siteconfig/pull/31

Replaces https://github.com/silverstripe/silverstripe-framework/pull/5697

Something broke; Don't merge.

@clarkepaul can you please review my fix for cms add page?

@tractorcow Those template changes only effect the old forms and not the bootstrap ones. I can't seem to swap themes through settings either to test the old forms.

@clarkepaul see https://github.com/silverstripe/silverstripe-framework/pull/5826/commits/d9dada66f3c6293c817c0a6634024745b393f7d4#diff-ca97eb869e783103f4f6f1c4b234e195L1 which is on the new bootstrap template.

Shouldn't all the HTML be in a template?

The add page functionality seems all good, just needs the styles to match now which are here https://github.com/silverstripe/silverstripe-framework/pull/5728/files

Shouldn't all the HTML be in a template?

This is the end goal, yes. We are slowly moving templates out of PHP into SS files.

Sorry I don't have auth to merge, but all looking good to be merged

Reviewing now.

On SQLite I'm seeing failures in these tests:

CheckboxFieldTest::testReadonlyCheckboxField
NumericFieldTest::testReadonly
TextareaFieldTest::testReadonlyDisplayUnicodes
TextareaFieldTest::testReadonlyDisplaySepcialHTML
GridFieldDetailFormTest::testViewForm

Noted issue that we are going to fix in a subsequent story; The "insert link into page" form isn't working properly.

I've tested behat locally, but a few things aren't working:

Insert link (see above)
Assets section (it's getting removed anyway, so shouldn't be a blocker)


Security System unsupported

Prerequisite

[X] Yes

Version
1.7.0-beta.32
Device Infomation JSON File
"active_time":<PHONE_NUMBER>,
    "biz_type": 18,
    "category": "wfcon",
    "create_time":<PHONE_NUMBER>,
    "icon": "smart/icon/ay1524194438166Zg2hZ/8aef12f2f551213109d9e2d54f2d0354.jpg",
    "id": "",
    "ip": "",
    "lat": "",
    "local_key": "",
    "lon": "",
    "model": "DP-W2.1",
    "name": "Security System",
    "online": true,
    "owner_id": "",
    "product_id": "bsck4bhwubkpggmb",
    "product_name": "Alarm Security System",
    "status": [],
    "sub": false,
    "time_zone": "-07:00",
    "uid": "",
    "update_time":<PHONE_NUMBER>,
    "uuid": "baa29f26f32a64e1",
    "schema": []

Device Control Mode
None
Logs
No response
Other Infomations
I have a security system (https://www.amazon.com/gp/product/B08YYD28L1) which is recognized correctly by the Smart Life app. In the Tuya developer interface, this device appears as the following:
Product Name
RF 防区版网关
Product Category
wfcon
However, Homebridge produces these errors on attempting to load the device:
[3/9/2023, 10:05:20 PM] [TuyaPlatform] [TuyaDeviceManager] Get device specification failed. devId = ***********, code = 2009, msg = not support this device
[3/9/2023, 10:05:21 PM] [TuyaPlatform] Unsupported device: Security System.
I have enabled debug mode and see MQTT messages from other devices, but none from this one.
In Apple Home, a "Security System" device gets loaded, but it says "Not Supported" and I'm unable to turn it on or off (which makes sense, as this device doesn't come up under Accessories list in Homebridge).
Does anyone have any advice on how I could get this working? Thank you!

Thank you, yes...in the Tuya Developer site's product details section, I see that the "Product Type" is "Connector". I set the Control Instruction Mode to "DP Instruction" and see a long list of "DP Instructions" on the left and matching "Standard Instructions" to the right, but after I read the Advanced Options page on overrides (https://github.com/0x5e/homebridge-tuya-platform/blob/develop_1.7.0/ADVANCED_OPTIONS.md) I couldn't figure out how to proceed. These are the codes that appear in the DP Instructions (the exact same list appears on the "Standard Instructions" side):
true
bj
kg
bjsc
bjy
yl
xxpj
ykqts
cgqts
cmys
hjys
y1
pjts
c1
pjls
When I hover over the instruction "bj", I get a pop up withe following, and I'm not sure what I should be typing into the overrides dialog:
Code:bj
Function Name:Alarm
Data Transfer Type:Send & report
Data Type:Boolean
Remarks:bj
I'm sorry -- clearly I'm new to this and don't know what I am doing...I'm trying! :)

It's like a guess game.. first you can see the security system document to see what schema it has, then you can use tuya web debug tool to try your device schema one by one, to test each one's feature. then add plugin configs to overwrite their code. good luck :)

Hello again. Thanks for pointing me in the right direction. I set the device type to "mal" (Alarm Host - Tuya documentation here).
I then added the two required overrides -- "sos_state" (Boolean) and "master_mode". Adding the sos_state override was straightforward, and it works correctly, with my iPhone alerting me immediately when the alarm is tripped. Excellent! However, I'm not sure what to do with the master_mode control code. In the Tuya app, the enum options are "1", "2", and "3", which correspond with "arm", "disarmed", and "home".
Can you please let me know how to set up the override to remap between "1" "2" and "3" to "arm" "disarmed" and "home"?
Thanks!

Tuya mal documentation for "master_mode" has {“range”:[“disarmed”, “arm”, “home”, “sos”, “work”, “play”]}
What I have entered in my overrides is the following:
"code": "true",
"newCode": "master_mode",
"type": "Enum",
"property": {
"range": [
"1",
"2",
"3"
]

the map between 1/2/3 and arm/disarmed/home can be like this:
"deviceOverrides": [{
        "id": "your_device_id",
        "schema": [{
          "code": "master_mode",
          "onGet": "{'1': 'arm', '2': 'disarmed', '3': 'home'}[value] || 'default_value'",
          "onSet": "{'arm': '1', 'disarmed': '2', 'home': '3'}[value] || 'default_value'",
        }]
      }

Not tested, the default_value on onGet can be arm/disarmed/home, on onSet can be 1/2/3, as I'm not familar with the security system logic, you can determine it.

Ah, I see where you're going with this. Very helpful. I've tried several variations of this, but I get a syntax error, and I'm not sure whether it's because of the syntax in the override snippet I'm using or if there's something off in SecuritySystemState.ts or one of the other files :
[3/25/2023, 10:24:22 AM] SyntaxError: Unexpected token ':'
    at SecuritySystemAccessory.OverridedBaseAccessory.eval (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:238:58)
    at SecuritySystemAccessory.getOverridedStatus (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:294:27)
    at SecuritySystemAccessory.getStatus (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:305:17)
    at /var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/characteristic/SecuritySystemState.ts:64:38
    at SecuritySystemAccessory.updateAllValues (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:113:46)

Currently what I have is this:
        "deviceOverrides": [
            {
                "id": "xxxxxxxxxxxxxxxx",
                "category": "mal",
                "schema": [
                    {
                        "code": "true",
                        "newCode": "master_mode",
                        "onGet": "{1: 'arm', 2: 'disarmed', 3: 'home'}[value] || 'home'",
                        "onSet": "{'arm': 1, 'disarmed': 2, 'home': 3}[value] || '3'"
                    },
                    {
                        "code": "bj",
                        "newCode": "sos_state",
                        "type": "Boolean"
                    }
                ]
            }
        ]

The bj > sos_state override works, but the true > master_mode override does not. (Also, as a sidenote, the DP code for master_mode really is actually called "true" for whatever reason. I don't understand why they didn't choose something else, but that's just what they decided to call it.)
Is the onGet JSON logic you have here something like, "If you get '1', then return 'arm' as the [value], otherwise return the default_value (which could be "arm", "home", or "disarmed")? I do see a number of examples at https://github.com/0x5e/homebridge-tuya-platform/blob/develop_1.7.0/ADVANCED_OPTIONS.md, but none that reflect the syntax in the example you created above.
Your thoughts?

Ah, I see where you're going with this. Very helpful. I've tried several variations of this, but I get a syntax error, and I'm not sure whether it's because of the syntax in the override snippet I'm using or if there's something off in SecuritySystemState.ts or one of the other files :
[3/25/2023, 10:24:22 AM] SyntaxError: Unexpected token ':'
    at SecuritySystemAccessory.OverridedBaseAccessory.eval (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:238:58)
    at SecuritySystemAccessory.getOverridedStatus (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:294:27)
    at SecuritySystemAccessory.getStatus (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:305:17)
    at /var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/characteristic/SecuritySystemState.ts:64:38
    at SecuritySystemAccessory.updateAllValues (/var/lib/homebridge/node_modules/@0x5e/homebridge-tuya-platform/src/accessory/BaseAccessory.ts:113:46)

Currently what I have is this:
        "deviceOverrides": [
            {
                "id": "xxxxxxxxxxxxxxxx",
                "category": "mal",
                "schema": [
                    {
                        "code": "true",
                        "newCode": "master_mode",
                        "onGet": "{'1': 'arm', '2': 'disarmed', '3': 'home'}[value] || 'home'",
                        "onSet": "{'arm': '1', 'disarmed': '2', 'home': '3'}[value] || '3'"
                    },
                    {
                        "code": "bj",
                        "newCode": "sos_state",
                        "type": "Boolean"
                    }
                ]
            }
        ]

The bj > sos_state override works, but the true > master_mode override does not. Is the onGet JSON logic you have here something like, "If you get '1', then return 'arm' as the [value], otherwise return the default_value (which could be "arm", "home", or "disarmed")?
I do see a number of examples at https://github.com/0x5e/homebridge-tuya-platform/blob/develop_1.7.0/ADVANCED_OPTIONS.md, but none that reflect the syntax in the example you created above.
It is interesting that DP code for master_mode really is actually called "true" for whatever reason. I don't understand why they didn't choose something else, but that's just what they decided to call it. Here's what I get in my log if I don't add the master_mode override:
  {
    code: 'true',
    mode: 'rw',
    type: 'Enum',
    property: { range: [ '1', '2', '3', [length]: 3 ] }
  },

And here's what I get in the log when I use the Smart Life app to set the system to "Home":
[3/25/2023, 3:04:11 PM] [TuyaPlatform] [TuyaOpenMQ] onMessage:
topic = cloud/token/in/xxxxxxxxxxxxxxxxxxxxx
protocol = 4
message = {
  "dataId": "xxxxxxxxxxxxxxxxxxx",
  "devId": "xxxxxxxxxxxxxxxx",
  "productKey": "xxxxxxxxxxxxxxxxxx",
  "status": [
    {
      "101": "3",
      "code": "true",
      "t": "1679781851",
      "value": "3"
    }
  ]
}

Yes, you've completely understand what I'm trying to do, I'm not JS expert and don't know why it failed. We can change a way to do this:
"onGet": "['', 'arm', 'disarmed', 'home'][parseInt(value)]",
"onSet": "['', 'arm', 'disarmed', 'home'].indexOf(value).toString()"

the index of an array is started from 0, so I add an empty string to hold the first index.
Yeah the schema code named true is funny...

That worked! Well done, and thank you!
For future reference for others who may have this system, I am including the configuration for this device below. Apparently, HomeKit only supports alarm triggers and mode configuration. The system has other features (e.g., built-in light settings), but it the iOS interface doesn't seem to surface any of those in the user interface, such as the switch_alarm_light setting that I added to the overrides below. Apparently the iOS app only works with sos_state and master_mode.
{
    "options": {
        "projectType": "2",
        "accessId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "accessKey": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "countryCode": 44,
        "username": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "password": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "appSchema": "smartlife",
        "deviceOverrides": [
            {
                "id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
                "category": "mal",
                "schema": [
                    {
                        "code": "bj",
                        "newCode": "sos_state",
                        "type": "Boolean"
                    },
                    {
                        "code": "kg",
                        "newCode": "switch_alarm_light",
                        "type": "Boolean"
                    },
                    {
                        "code": "true",
                        "newCode": "master_mode",
                        "onGet": "['', 'arm', 'disarmed', 'home'][parseInt(value)]",
                        "onSet": "['', 'arm', 'disarmed', 'home'].indexOf(value).toString()"
                    }
                ]
            }
        ]
    },
    "platform": "TuyaPlatform"
}

Just out of curiosity (and for anyone else reading this thread), let me make sure I understand the syntax you're using here.
Based on http://jibbering.com/faq/notes/square-brackets, in onSet--are you taking the array enclosed in the brackets and looking up the index number of the set value (e.g., "arm", which would be 1), then passing that index number (1) along as a string to Tuya in order (effectively setting the true to 1)?
And for the onGet, is Tuya supplying a string version of "1" that is then parsed as an integer instead which is then used to identify the element within the array that is meant to be selected (e.g., 1 = 'arm')?

Yes, because your enum are 1/2/3 so can be easily use parseInt()/toString() to convert. But not all device are lucky like this, so a generic solution should use an map to convert like this (multiline version):
var map = {
  '1': 'arm',
  '2': 'disarmed',
  '3': 'home',
};
return map[value];

But don't know why there's an syntax error when using with eval()...

Yes, because your enum are 1/2/3 so can be easily use parseInt()/toString() to convert. But not all device are lucky like this, so a generic solution should use an map to convert like this (multiline version):
var map = {
  '1': 'arm',
  '2': 'disarmed',
  '3': 'home',
};
return map[value];

But don't know why there's an syntax error when using with eval()...

Okay. Well, interesting case. Thank you for your help!

For anyone else that runs across this and is looking for a solution- I loaded Tuya Local on Home Assistant and modified the existing security system yaml code to work with my system just like this one DP-W2.1. I really like this security system as it watches my barn-remotely- now integrated with Home Assistant its even more powerful.  Not familiar with HomeBridge so not sure if it will work for everyone.


REST API do not validate Prototyped APIs with invalid inline scripts

Description:
When we are Deploying the API as Prototyped APIs with inline script using the [REST API|https://docs.wso2.com/display/AM210/apidocs/publisher/#!/operations#APICollection#apisPost], it does not validate the inline script therefore, we are allowed to create and update Prototyped APIs with erroneous scripts with REST API.
Public JIRA : https://wso2.org/jira/browse/APIMANAGER-6017
Suggested Labels:
2.1.0, 2.x.x
Suggested Assignees:
Affected Product Version:
2.1.0
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

I’m closing this issue because it has been inactive for more than two years. Please reopen if you still encounter this issue with the latest version.


⚠ Bofrost.fr has degraded performance

In a61eb5c, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1579 ms

Resolved: Bofrost.fr performance has improved in 3403e97.


Reuse @TestContainers and @Container

I found there is a new annotation @TestContainer added to control testcontainer Container. https://github.com/arquillian/arquillian-testcontainers/blob/main/src/main/java/org/jboss/arquillian/testcontainers/TestContainersObserver.java#L28
The basic support of Spring Boot testcontiners just adds a @ServiceConnection to the container declarations to setup the connection properties automatically.
@SpringBootTest
@Testcontainers// from testcontainers
class MyTeset {

   @Container // from testcontainers
   @ServiceConnection // from spring Boot
   static AContainer container = ...
}

If possible, reuse the testcontainers existing @Testcontainers and @Container to controll the container lifecycle, and ensure Arquillian sets up the application server adapter's properties after the successful waiting strategy. Then perform the deployment that is defined by @Deployment.

Those annotations will not work in all cases. For example, in WildFly there is the ability to implement a ServerSetupTask which allows for configuration of WildFly before the deployment is done. You cannot inject the same instance of the Testcontainer in the ServerSetupTask without Arquillian managing the lifecyle of the Testcontainer.

Testcontainers have wait strategies, can the Wildfly/Glassfishs test deployment step wait for testconainters be ready for deployment?

@hantsy Yes, that should be possible AFAIK. If you have an example of what it would look like without Arquillian, I can confirm.
What should happen though is the Testcontainer is started before the class. The class should then be created and the deployment done. Once the class is complete, the Testcontainer should stop.

I tried this way in an example before: https://github.com/hantsy/arquillian-testcontainers-example/blob/autodeployment/src/test/java/com/example/it/GreetingResourceTest.java#L51
(ignore this example in autodeployment branch, I was trying to use AutoDeployment provided in Arquillian, but not sure why the deployment was not started)
The @Container and @Deployment archives can be ready before running tests, Arquillian can utilize the wait strategy provided by Testcontainers, etc. to check the startup status of the application server and decide when to deploy.

That could be done by extending the testcontainer. Note that the @Testcontainer annotation for JUnit 5 in the Testcontainer project is different than this. This project is for injecting a GenericContainer<?> as an @ArquillianResource.


Error while loading

Hi. When trying to install Qsys-qrc i'm getting the following two errors. Can someone help me to solve it? Thanks very much.
Logger: homeassistant.setup
Source: setup.py:416
First occurred: 13:56:06 (1 occurrences)
Last logged: 13:56:06
Error during setup of component qsys_qrc
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 416, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/qsys_qrc/init.py", line 259, in async_setup
CONF_CONFIG: config[DOMAIN],
~~~~~~^^^^^^^^
KeyError: 'qsys_qrc'

found the solution in closed issues. sorry


Build failure: octoprint

Steps To Reproduce
Steps to reproduce the behavior:

build octoprint

Build log
[root@nixpi:~]# nix-shell -p octoprint
these 2 derivations will be built:
  /nix/store/qy4fk0p7x3ikz4ybchjw6ahyi3pp523r-source.drv
  /nix/store/ifabqk77dx0sc3dr409hp6bp739g1hlq-python3.10-OctoPrint-1.9.3.drv
building '/nix/store/qy4fk0p7x3ikz4ybchjw6ahyi3pp523r-source.drv'...

trying https://github.com/OctoPrint/OctoPrint/archive/1.9.3.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 5765k    0 5765k    0     0  2898k      0 --:--:--  0:00:01 --:--:-- 4256k
unpacking source archive /build/1.9.3.tar.gz
error: hash mismatch in fixed-output derivation '/nix/store/qy4fk0p7x3ikz4ybchjw6ahyi3pp523r-source.drv':
         specified: sha256-SYN/BrcukHMDwk70XGu/pO45fSPr/KOEyd4wxtz2Fo0=
            got:    sha256-71uE8JvcS++xH8WSVWj5x0+9s3XIwf3A64c6YtxpSRc=
error: 1 dependencies of derivation '/nix/store/ifabqk77dx0sc3dr409hp6bp739g1hlq-python3.10-OctoPrint-1.9.3.drv' failed to build

Additional context
This is done on a raspberry pi 4, I believe this patch here meant to fix an issue on darwin is related to my issue. The previous has was correct for me on rpi4.
https://github.com/NixOS/nixpkgs/commit/29441c4a472289150bc58f5ec3d8a8ed4046a725
Note: I am very new to nix/nixos so I might just be missing something trivial.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[root@nixpi:~]# nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-linux"`
 - host os: `Linux 6.1.21, NixOS, 23.11 (Tapir), 23.11pre536534.ca012a02bf83`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Looks like a duplicat of #261934

You are absolutely right... Rooky mistake.
Running the following resolved my pebcak issue:
nix-channel --add https://nixos.org/channels/nixos-23.05 nixos
nix-channel --update

That actually a system downgrade. You were on unstable but not you on 23.05 (stable) (:


Refactor readme examples

Instead of providing a simple code block with all possible config options, I split it into several snippets for different use cases. I think it's more readable, since it allows us to give more context, to link to the Strapi docs, and to rely less on code comments.
I think it's also more convenient to have a basic config example that suits most users, and that's easy to copy and paste.
I'm setting this as a draft, since I'll rework this PR to match our internal documentation styleguide. (thanks Piwi for telling me about it!)

Thanks @remidej ! I've just read it and it looks nice, thank you :-)
I've just added a suggested change, to remove a duplicate word.
I don't think you need to rework it, as READMEs do not require to strictly adhere to the styleguide we use for documentation deployed on strapi.io.
So it looks good to me, congrats 👏

Thanks for reviewing this @pwizla :)
I just renamed the top level titles to use verbs, like in the documentation. I thing the 3 steps (install, set up, query) are more clear that way.


does load with webpack vue js

I am no expert but when I previously used the @2.0.1 version, adding the plugin to webpack worked, but when the new version is added, even the webpack server will not output to the browser.

@ilbrigz this issue has been fixed in the latest version. Let me know if you get the same behaviour after updating

Hello, I'm geting the same scenario. I've tried everything but nothing seems to work. It does work on other machines though

if it can not be reproduced on other machines, i suggest removing node_modules folder entirely, cleaning npm caches and reinstalling dependencies. let me know if it still an issue


Updated Error handling

May Close #49

It doesn't seem to solve the issue #49. You are using try/catch for NullPointerException which actually doesn't solve the issue it just only hides it... null pointer shouldn't be coming in the first place.


Font selector instead of input field

It would be so much easier to choose fonts if Atom's Setting had an ctual dropdown instead of an input field for the font. Please add it.
Also, can you make each line in the dropdown to be rendered with the font that it represents?

Would be nice :+1: -- follow https://github.com/atom/settings-view/issues/286 for updates.


submission

fleng: http://www.call-with-current-continuation.org/fleng/fleng.html
this evolved from a strand implementation by the same author: http://www.call-with-current-continuation.org/strand/strand.html

Added.


multiple address models break unique related_name constraint

I've ran into this bug while trying to run tests (http://stackoverflow.com/questions/10058277/django-test-fails-when-creating-test-database/) and a user of one of my plugins has ran into it when running my migrations: https://github.com/Lacrymology/django-shop-area-tax/issues/1
The issue seems to be the existence of two models with ForeignKey(User, related_name="[shipping|billing]_address"..), i.e.: your own user-defined models and shop.addressmodel.Address.
Even if you don't add shop.addressmodel to your user models, the tests import them to use them, and then conflict arises, in the case of the bug the other user is reporting,  I'm not sure where the import's coming from.
But it has lead me to think that my own app will have the same problem, if a user wants to use the l10n app, but wants to provide their own Address model. I think I'll have to move it out of my app's models.py file, that'd do the trick, wouldn't it?

Closed. Please check version 0.9. Please look at the docs about deferred models.


Bug report about the data size in backward() of chainer (maybe?)

If your issue is a request for support in using Chainer,
please post it on Stack Overflow.
If it is a bug report, feature request or suggestion,
please take a look at our contribution guide.
Specifically, if it is a bug report, these information are very helpful:

Conditions

Chainer version
CuPy version
OS/Platform
CUDA/cuDNN version
etc.

Code to reproduce
Error messages, stack traces, or logs

Thank you for your cooperation!
Support is available on our Slack Chat.

Platform: Linux-4.15.0-42-generic-x86_64-with-Ubuntu-18.04-bionic
Chainer: 5.3.0
NumPy: 1.16.2
CuPy:
  CuPy Version          : 5.3.0
  CUDA Root             : /usr/local/cuda
  CUDA Build Version    : 9000
  CUDA Driver Version   : 10000
  CUDA Runtime Version  : 9000
  cuDNN Build Version   : 7402
  cuDNN Version         : 7500
  NCCL Build Version    : 2307
  NCCL Runtime Version  : 2307
iDeep: Not Available

< Code to reproduce >
import chainer.functions as F
from chainer.link import Chain

from fgnt.chainer_extensions.binary_cross_entropy import binary_cross_entropy
from fgnt.chainer_extensions.links.sequence_linear import SequenceLinear
from fgnt.chainer_extensions.links.sequence_lstms import SequenceBLSTM
import numpy as np
from chainer import Variable
from chainer import cuda
from chainer import optimizers
from chainer import serializers

class MaskEstimator(Chain):
    def _propagate(self, Y, dropout=0.):
        raise NotImplemented
    def calc_masks(self, Y, dropout=0.):
        res1, res2 = self._propagate(Y, dropout)
        return res1, res2
    def train_and_cv(self, A, B, C, dropout=0.):
        res1, res2 = self._propagate(A, dropout)
        loss_X = binary_cross_entropy(res2, B)
        loss_N = binary_cross_entropy(res1, C)
        loss = (loss_X + loss_N) / 2
        return loss

class SimpleFWMaskEstimator(MaskEstimator):
    def __init__(self,numFilters):
        self.numFilters=numFilters
        relu_1 = SequenceLinear(self.numFilters, self.numFilters*2, normalized=True)
        sig1 = SequenceLinear(self.numFilters*2, self.numFilters, normalized=True)
        sig2 = SequenceLinear(self.numFilters*2, self.numFilters, normalized=True)
        super().__init__(
                relu_1=relu_1,
                sig1=sig1,
                sig2=sig2
        )
    def _propagate(self, Y, dropout=0.):
        relu_1 = F.clipped_relu(self.relu_1(Y, dropout=dropout))
        res1 = F.sigmoid(self.sig1(relu_1))
        res2 = F.sigmoid(self.sig2(relu_1))
        return res1, res2

model=SimpleFW(32)

A1=Variable(np.random.rand(100,6,32).astype(np.float32))
B1=Variable(np.random.rand(100,6,32).astype(np.float32))
C1=Variable(np.random.rand(100,6,32).astype(np.float32))
A2=Variable(np.random.rand(20000,6,32).astype(np.float32))
B2=Variable(np.random.rand(20000,6,32).astype(np.float32))
C2=Variable(np.random.rand(20000,6,32).astype(np.float32))
print('--> 1')
loss1 = model.train_and_cv(A1, B1, C1)
print('--> 2')
loss2 = model.train_and_cv(A2, B2, C2)
print('--> 3')
loss1.backward()
print('--> 4')
loss2.backward()
print('--> 5')

=====================================================
<    execution   >

python3 test_Chainer.py
--> 1
--> 2
--> 3
--> 4

Traceback (most recent call last):
File "test_Chainer.py", line 64, in
loss2.backward()
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 981, in backward
self._backward_main(retain_grad, loss_scale)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 1061, in _backward_main
func, target_input_indexes, out_grad, in_grad)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/_backprop_utils.py", line 109, in backprop_step
target_input_indexes, grad_outputs)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/function.py", line 145, in backward
variable._check_grad_type(self, x, True, gx, False)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 74, in _check_grad_type
raise typ(detail + msg)
TypeError: Function <property object at 0x7fb19ad347c8> (SequenceBatchNormalizationFunction) has a bug.
Please report this error to the issue tracker with the stack trace,
the information of your environment, and your script:
https://github.com/chainer/chainer/issues/new.
Dtype of data and grad mismatch
grad: float64 != data: float32

Hi,
I am very thank you for your library!
It is easy and useful.
But, I think there is a bug.
Here is my situation.
I have,
-> (A & B & C).size   = [400 x 6 x 32]
-> (A2 & B2 & C2 ).size = [100000 x 6 x 32 ]
-> A,B,A2 and B2 are answer (target, labels). They consist data 0 and 1 only in float32.
-> C and C2 are inputs. They consist data -1~1 in float 32.
-> model = stacked fully connected layer
I run,
loss1  =model.train_and_cv(A,B,C)
loss2 = model.train_and_cv(A2, B2, C2)
loss1 & loss2 are calculated well.
But, when I run,
loss1.backward()
loss2.backward()
the loss1 done well.
the loss2 give me ERROR. (I attached the error log at the bottom.)
As the error said, I tried to change
-> the data type of input&output
-> the data type of loss2
and etc., but I can't figure it out.
So, I thought "Maybe  I did mistakes when I make the A2,B2,C2".
But I think it isn't. (you can see the reason why in below)
Then, I run this,
(I reduce the data size only for test.
)
A3=A2[:200,:,:]                       -> A3 size [200 x 6 x 32]
B3=B2[:200,:,:]                       -> B3 size [200 x 6 x 32]
C3=C2[:200,:,:]                       -> C3 size [200 x 6 x 32]
loss3 = model.train_and_cv(A3, B3, C3)
loss3.backward()
the loss3 does not complain anything!

**In summary,
loss1 & loss3 backward() done good, which uses A1 & A3 (smaller size data).
loss2 backward() got ERROR, which uses A2 (larger size data).
=> So, I think maybe there is a problem at backward() in datasize.
+) I can change A3 size to [10922 x 6 x 32].
But I set A3 to [10923↑ x 6 x 32] , then I get error (same as below)

_Traceback (most recent call last):
File "", line 1, in
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 981, in backward
self._backward_main(retain_grad, loss_scale)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 1061, in _backward_main
func, target_input_indexes, out_grad, in_grad)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/_backprop_utils.py", line 109, in backprop_step
target_input_indexes, grad_outputs)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/function.py", line 145, in backward
variable._check_grad_type(self, x, True, gx, False)
File "/home/nam/.local/lib/python3.6/site-packages/chainer/variable.py", line 74, in _check_grad_type
raise typ(detail + msg)
TypeError: Function <property object at 0x7fea3d4707c8> (SequenceBatchNormalizationFunction) has a bug.
Please report this error to the issue tracker with the stack trace,
the information of your environment, and your script:
https://github.com/chainer/chainer/issues/new.
Dtype of data and grad mismatch
grad: float64 != data: float32_

The error occurred in SequenceBatchNormalizationFunction.
Could you tell me what SequenceBatchNormalizationFunction is?
Could you share the code if possible?

Oh, I thought chainer_extension as the library in the chainer, but it isn't!
I'm sorry, I should look at the extension library.
The link of the code is here,
https://github.com/fgnt/nn-gev/blob/master/fgnt/chainer_extensions/sequenze_batch_normalization.py
Thank you for your support! :)


Only vectorise innermost loop for Scoped Parallelism on the host

This change is important for good performance in both LLVM and GCC on CPUs. Without it, the performance is lower, particularly for GCC (and to a lesser degree for LLVM).

I have a similar suspicion elsewhere, so LGTM.
Do you have any intuition as to why this makes a difference?
My initial guess would be, that the index might not be detectable as being in a unit stride anymore -> more masking / less efficient memory accesses or something in that direction?
Let's @hipsycl-ci-bot test this as well.

Hi Tom,
this is already contained in my local copy of the scoped parallelism branch (I just hadn't committed it yet), along with some other minor improvements. Is it okay if we just use my version? Otherwise I'd need to split up the commit.
@fodinabor We found it out empirically. IMHO this code is as intended by the OpenMP spec. To me it looks like a limitation in LLVM.

@illuhad Your local copy is fine! Just need to not forget to push this 😄

@tomdeakin Done :)


DataGrid columnDef autoHeight= true it seems not working

Hi,
I try to use the property autoHeight= true in a columnDef and it seems that does not work.
What I need is if the text for that column is bigger than the space the height would be bigger to show all the text.
Un Saludo
Juan Ramírez

hi,
if that column has 'showAs' = text, add a style to it, with : white-space: normal;


Update trustworthy-database-property.md

Hi,
I have added the following section, the reason is that you can escalate from db_owner to sysadmin within MSDB (this can't be performed with lower privileges such as DDL_ADMIN....etc within MSDB. I have published the PoC here for technical eveidence: https://databasesecurityninja.wordpress.com/2022/08/28/sql-server-privilege-escalation-from-db_owner-to-sysadmin-by-design/
So, its worth adding the following paragraph:
**The following SQL code can be used to obtain a list of databases users in MSDB that are granted DB_OWNER role. Accounts granted DB_OWNER role can escalate to SYSADMIN role.
SELECT    roles.principal_id    AS RolePrincipalID
,    roles.name       AS RolePrincipalName
,    database_role_members.member_principal_id  AS MemberPrincipalID
,    members.name      AS MemberPrincipalName
FROM sys.database_role_members AS database_role_members
JOIN sys.database_principals AS roles
ON database_role_members.role_principal_id = roles.principal_id
JOIN sys.database_principals AS members
ON database_role_members.member_principal_id = members.principal_id where  roles.name='db_owner' and members.name <>'dbo'
GO**
Thanks
Emad

Hi @emad-almousa! Thanks for adding this. We'll need to investigate this.
@AndreasWolter - Hey Andreas, can you please help comment on this?

Hi @emad-almousa
thanks for looking at this and warning users about this risk.
Yes, it is true that with trustworthy there are ways a user can elevate to sysadmin. This goes for any database though, not just msdb.
Hence I would rewrite some of your additions to be more generic.
@VanMSFT I am not keen on updating a PR in the middle. For me it would be ok to just publish this, and right afterwards I would make my changes. I would just need to know when this happens.
I found some other parts where I should edit at this opportunity as well.

Hi @AndreasWolter thanks for your update. Your statement is correct... I just wanted you to warn users since by default MSDB has trustworthy "on" account with db_owner can escalate to sysadmin.
Thanks

Hi @emad-almousa - Thanks again for these additions. I've pulled in your commit to a private branch so that we can expand further on your contributions. We'll go ahead and close this PR for now, and you should get credit for the edits in my PR when published.
FYI - @AndreasWolter
https://github.com/MicrosoftDocs/sql-docs-pr/pull/28061


how-to-npm issues are mostly human error compounded by an annoying bug

Challenge http://www.freecodecamp.com/challenges/waypoint-manage-packages-with-npm.
The dist-tag bug in how-to-npm 2.0.0 is trivial if you know the cause and how to deal with it. The bug is actually triggered entirely by human error: e.g., if you try to add or remove an invalid dist-tag, 403 or 404 errors will begin to accumulate. The tutorial should have delivered a descriptive error message in these cases.
If at any point you see a 403 or 404 error your only recourse is to run how-to-npm again, and in some cases you may need to repeat a prior step.
Here are some common causes for these errors;

Try not to use commands out of sequence. For example, avoid using npm publish on steps that do not ask you to publish. Even if you enter a valid npm command, the tutorial will often break if you do things it isn't expecting for a given test. If you need to repeat a command, you may be better off returning to the relevant test before picking up at your current step.
npm version should be followed by a version number (e.g., 1.0.2) or by a keyword indicating a semver type (e.g., 'patch'). See npm help version for examples. (You may also set the version number manually in package.json, but npm version works if you understand the syntax.)
You can not change the dist-tag of the version tagged latest until you've assigned latest to a different version.
dist-tags can not be added to a version number beyond the highest existing version. For example, if you've set  and published version 2.0.0, you can not add a dist-tag to 2.0.1.
Finally, if you set latest to a low number (e.g., 0.0.1) you're eliminating or vastly reducing the available version numbers to which you can assign dist-tags.

Any of these (and more like them) will cause 403 or 404 errors and will require users to step back, rerun how-to-npm, and be careful not to repeat mistakes.

@denmch and I had an extensive discussion about this in Slack, and we've updated the challenge. I'm closing this issue. Huge thanks to @denmch for isolating these issues and synthesizing clear simple work arounds for our campers!

The problem with this entire set is that it's designed to teach by guessing. Please make simple and clear instructions in a tutorial. Don't TRY to fool students by leaving the solution out of the lesson. The I still don't know how to tell the name of my package or what the function of a package or dependency actually is.

The how-to-npm should not list steps as "Completed"...   if things have been broken inside that will make further steps impossible.
I wish someone could post actual working commands. I wish I knew where the clear, simple workarounds are posted.  I should have looked elsewhere for more informative npm information before wasting so much time on this challenge.

This is actually ridiculous and I cannot pass it no matter what I have done. I skipped the entire challenge after it would NOT work the 1000 different things I tried, I have spent 3 hours on this.

I can usually build a lightweight site and code it in less than 3 hours. This is probably the longest I've EVER spent on something and especially without reward.

Also, how-to-npm verify skip  DOES NOT WORK.

  We are working on a replacement for it - something that would run on top of HyperDev (instead of the command line) and would not involve a lot of package creation-specific tasks (that you can learn if and when you choose to create npm packages yourself).
Would you be interested in helping us design a replacement?

Thank you Quincy for being on this. I am willing to help with the questions
that a novice would ask given that I am one. I've put off FreeCodeCamp for
months because of this blockade. Had some help try to clarify for me, but
it's still something over my head as a concept. Regardless, you've been
awesome with leading this resource. If you could use my help, please let me
know.
-Steve
On Jul 29, 2016 12:59 AM, "Quincy Larson"<EMAIL_ADDRESS>wrote:

@kaym0 https://github.com/kaym0 yes - this Node School module is
seriously broken. We are working on a replacement for it - something that
would run on top of HyperDev (instead of the command line) and would not
involve a lot of package creation-specific tasks (that you can learn if and
when you choose to create npm packages yourself).
Would you be interested in helping us design a replacement?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/758#issuecomment-236118225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL3-JYu-Uwf6sfodsyZdWEUGJ_E8pzzhks5qabLDgaJpZM4EwY9Q
.

@Philosophist Thanks for your kind words. Sad to hear that this has blocked you. Yes - we will work to replace these challenges. I will talk with the core team and create some issues. We are coordinating our curriculum expansion here, so feel free to dive in and contribute:  https://github.com/FreeCodeCamp/CurriculumExpansion/

@QuincyLarson I would love to help, but I'm not sure if I have the technical capacity to do so.

@QuincyLarson Although, let me know what you need done and I will see if I can help!

@QuincyLarson Didn't notice the Git link above. Have saved it and I will look at it shortly! In the mean time, what will we miss out by not actually completing the 'how-to-npm dist-tag' and the few challenges beyond it? Would it be safe to move forward and come back to finish that after the fix has been made?

@kaym0 honestly, you won't miss much. Most of the generally applicable npm knowledge is at the beginning of that challenge. I recommend you keep on moving forward.

@QuincyLarson
Thanks. Looking forward to the replacement curriculum.

@QuincyLarson I'm confused. "Manage Packages with npm" looks like a normal challenge (if such a challenge even exists :-) ).  If there's still something seriously wrong with how-to-npm then shouldn't people be warned about it inside the FCC challenge. I would like to contribute...

@oppositive if things go well, we will replace these Node School challenges completely within the next week or so. But if you want to dig in and figure out which how to npm challenges have issues and produce a list we could update it.

Hi, everyone. I have spent my morning trying to very carefully get around step 11 but I keep getting a 404 error.  I go back and repeat steps 09 and 10, but still get the 404. I have deleted the directory and started a new one, carefully repeated the steps, and still get the 404, even after once again repeating steps 9 and 10 and always using the next to most recent version # (if current version is 3.00.00, I attach a dist tag to 2.00.00, for example)
   {
     "name": "@newuser/fcc01",
     "version": "3.0.0",
     "description": "this is a test",
     "main": "0",
    "sc....

 olddognewtrix123:~/workspace/fcc01 $ npm dist-tag add<EMAIL_ADDRESS>[beta]
 npm ERR! Linux 4.2.0-c9
 npm ERR! argv "/home/ubuntu/.nvm/versions/node/v4.6.1/bin/node"         "/home/ubuntu/.nvm/versions/node/v4.6.1/bin/npm" "dist-tag" "add"<EMAIL_ADDRESS>"[beta]"
 npm ERR! node v4.6.1
 npm ERR! npm  v4.0.2
 npm ERR! code E404

npm ERR! 404 missing : -/package/fcc01/dist-tags

I get the same errors as @olddognewtrix123. All my previous challenges are "COMPLETED", but trying to add a dist-tag just doesn't work.

Finally got work.
It seems when you create a project, in the name give something like "@username/packagename". And before you add a tag, try to use npm dist-tag ls to see what tags are there first.
But still want the author to update the instructions, get some newbie to test the steps and update. It will save a lot of time for many people.

I continue to get a 404 when trying to point latest to a different version.  Please supply better instructions on this step.  I've tried googling and referring to npm documentation, with no luck.  Please advise or revise.

I took a few (geeze, a lot actually) months of from FCC just to build some
games and sharpen my coding skills in other areas. Now I'm circling back to
FCC and need to complete the rest of the Node projects so I can get the
back end cert.
That said, I'm completely ignoring those how-to-npm tutorials. Instead, I'm
plowing through the Net Ninja video tutorials on youtube. That should get
me to a point where I can build the required stuff for FCC without hassling
with a poorly written tutorial.
Take away: there's lots of other really great sources to learn node js.
  Find something that works for
you.
On Jul 14, 2017 2:49 PM, "Julie"<EMAIL_ADDRESS>wrote:
I continue to get a 404 when trying to point latest to a different version.
Please supply better instructions on this step. I've tried googling and
referring to npm documentation, with no luck. Please advise or revise.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/758#issuecomment-315437119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASRAdQxi3_9BnODa6dFAxTrioNTOmrkRks5sN7hJgaJpZM4EwY9Q
.

I guess I'm having the same problems with npm dist-tag add   and have tried several workarounds. Can you give us credit for this tutorial if we make it through 10? When are you guys gonna update or fix this?

@thenerdywiz We are removing the Node School challenges completely in favor of our own challenges. These are in the beta curriculum: beta.freecodecamp.com/map

Hi Quincy...I'm sorry to pester you but I'm now having some problems with the beta curriculum. I have setup my account with Glitch and somewhat understand its workings. However, the "show live your app" opens a page with just 'Manage Node.js projects and npm packages using package.json
Part 1 of Free Code Camp Backend Challenges' and a grey screen. What's worse is that the beta fcc is not letting me get going even though I have a valid key inside my package.json file? I checked the logs and I'm not getting any errors? Can you help me out please?

@thenerdywiz It sounds like you may have identified a bug. Can you take some screenshots and create a separate issue for this?

As I get it ,to start Back End I have to go straight to beta challenges and skip Node School challenges.
Am I right?

i got it to work after about an hour of frustration and it was an AHA moment. here is my solution,
npm dist-tag add<EMAIL_ADDRESS>beta
p.s. your name and file name have to be all lowercase. for instance, mine looked exactly like this:
npm dist-tag add<EMAIL_ADDRESS>beta

Hi all,
Rarely am I stumped, but here I am; I'm quite familiar with the term beta; what is the meaning of FCC in the context of this thread?
Thanks muchly!
Steve

From: Daniel Paul Pereira<EMAIL_ADDRESS>Sent: Thursday, June 8, 2017 6:14 PM
To: freeCodeCamp/freeCodeCamp
Cc: Subscribed
Subject: Re: [freeCodeCamp/freeCodeCamp] how-to-npm issues are mostly human error compounded by an annoying bug (#758)
Restarted entire tutorial following "solution" steps exactly. Still exact same error. Total garbage.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/freeCodeCamp/freeCodeCamp/issues/758#issuecomment-307184460, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACKXS65ZHNf85kxdq26dzV6aLVvF9kv8ks5sCDoXgaJpZM4EwY9Q.

List available dist-tags
npm dist-tag ls
Adding a dist-tag
npm dist-tag add<EMAIL_ADDRESS>beta
Removing a dist-tag
npm dist-tag rm @"yourname"/"yourfilename" beta
Pointing "latest" tag somewhere else
npm dist-tag add<EMAIL_ADDRESS>latest
If you face any problems with the last one, first change the version in package.json and then run the command.


Add aerialway=j-bar to presets

I noticed that from the aerialway presets, j-bar, described in the wiki as a type of aerialway=drag_lift seems to be missing. T-bar already exists in the presets.
https://wiki.openstreetmap.org/wiki/Tag:aerialway%3Dj-bar

Thanks @westnordost 👍


feat(cache/in-memory): new voice state fields

Add new fields to the cached voice state type that have since been added to the twilight_model variant. These fields are self_video and request_to_speak_timestamp. Getters have been added for these fields.

Can the cached voice state's channel_id really be None?

No, looks like we remove the voice state from cache when the channel_id is None


[material-ui][Snackbar] Remove notistack library

Closes #42615
Originally, we added Material UI's Snackbar usage with notistack to show vertically stacked Snackbars. I was working on implementing this feature directly in Material UI (see PR https://github.com/mui/material-ui/pull/31991), but the PR was halted for various reasons.
Should we show usage with other libraries like react-toastify or sonner for vertically stacked snackbars?
Also, should this be cherry-picked to the master branch? I think it should.

I agree to replace notistack, but it's not possible to use react-toastify or sonner for our Snackbar. I checked their documentation and tried with Material UI Snackbar. We documented notistack because it provided a design similar to Material UI's Snackbar. So, we shouldn't merge this PR until we find an alternative. Ideally, we should have our own solution in the library. Alternatively, we could suggest this solution with an embedded CodeSandbox in our docs.

Base UI will eventually work on their Toast component, which is planned for Q3 in the latest roadmap I could find.
What would you say is the urgency of this issue @ZeeshanTamboli? If it can wait until Q4, I think we can add it to the Base UI refactor milestone.

I think we can add it to the Base UI refactor milestone.

I think you meant the Material UI refactor milestone, right? I'm fine with that. Before removing notistack, we should implement vertically stacked snackbars in our library. I'll close this PR and we'll continue recommending notistack for now, even if it's unmaintained, as it solves our issue.

I think you meant the Material UI refactor milestone, right?

This one: https://github.com/mui/material-ui/milestone/51
I'll add the issue to it


Wrong code points for ZWNJ and ZWJ

The section “Invalid Combining Marks” mentions the Unicode code points “ZWJ (zero width joiner; U+200C), the ZWNJ (zero width non-joiner; U+200D)”.
In actual Unicode, the code points are assigned differently: U+200C ZERO WIDTH NON-JOINER, U+200D ZERO WIDTH JOINER.

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

ID: aad9cb38-9a74-d136-23f6-0fdc5dca33c8
Version Independent ID: ef6b84e4-d3a7-8c34-78ac-1b5788765fb8
Content: Developing OpenType Fonts for Khmer Script - Typography
Content Source: typographydocs/script-development/khmer.md
Product: typography

Thank you for reporting the issue. Fixed!


Can you provide more examples of SPX (not SPY) Option Chain?

Hello Graeme,
Came across this AMAZING library and interested in more examples / jupyter notes of option chain
For instance,
How can we call SPX to understand

available strikes across the option chain for today (e.g. +/- 25 strikes)
For each strike, its put, call
each put/call's bid and ask price (Or a midpoint price?)
each put/call's delta / in-the-money probability

Hey! Take a look at the documentation here: https://tastyworks-api.readthedocs.io/en/latest/tastytrade.html#tastytrade.option.get_option_chain
And an example for your question 1:
from tastytrade.session import Session
from tastytrade.option import get_option_chain
from datetime import date

session = Session('user', 'pass')
chain = await get_option_chain(session, 'SPX', date(2023, 5, 19))
print(chain.get_all_strikes())

Question 2 I don't understand, each strike has a put and a call.
For question 3, you need to use the DataStreamer:
from tastytrade.streamer import DataStreamer
from tastytrade.dxfeed.event import EventType

streamer = await DataStreamer.create(session)
option = chain.options[10]  # this is a list of all options in the chain

quote = await streamer.stream(EventType.QUOTE, [option.symbol_dxf])
print(quote)

If I recall correctly, ITM probability is just a calculation based off of the option greeks, so you could do:
greeks = await streamer.stream(EventType.GREEKS, [option.symbol_dxf])
print(greeks)

For more examples, you can look at my CLI: https://github.com/tastyware/tastytrade-cli

In general, the documentation is a bit lacking, but I'm currently working on an overhaul of the whole API, so hopefully there will be better documentation soon.


fix: try perf no plusplus

try perf the no plus plus rules, and see if there is still has regression

Ok as I expected, so then


Connection pooling and a few other minor things

@qasaur Like I said in our email convo, there's probably a few things you'll want to look through before merging into your master branch.

Thank you for your contributions @jpiontek!


By default have Google keywords module disabled

Since Google is not including the query string anymore, this module should be disabled by default and add a command line option to display it. ~./goaccessrc should include a flag as well.

This has been disabled by default. It can be enabled in the config file if needed.


Collect appropriate outputs from PyMARE Estimators

Currently, we only grab the most basic FE results from the new IBMA estimators, but we should identify the most appropriate/useful ones and extract those instead.

Do we want heterogeneity statistic maps (Cochran's Q, I^2, and/or H)?
Also, do we want the estimate and/or tau^2 confidence intervals?

Based on the lack of response, I'm guessing no one feels strongly about the outputs I listed, so I'm going to close this.


Taking screenshot in afterTest hook throwing error

Problem
I'm creating a screenshot in the WebdriverIO afterTest hook:
afterTest: function (test) {
    browser.saveScreenshot(filepath)
}

Then this error is thrown:
TypeError: this.context.push is not a function
    at module.exports.addScreenshotContext
    at WdioMochawesomeReporter.onAfterCommand
    at reporters.forEach.reporter
    at Array.forEach
    at BaseReporter.emit
    at EventEmitter.browser.on.result
    at Object.afterTest

Because of the mochawesome reporter it's impossible to create a screenshot in the afterTest hook. This would be the place where one would create screenshots on test failure.
Reason
I looked into the source code and found out that addScreenshotContext adds an object to this.context:
this.context.push({
    title: 'Screenshot',
    value: `data:image/jpeg;base64,${value}`
})

But at the time this method is called, this.context is already stringified. Thus this.context.push is not a function.
onTestEnd (test) {
    this.currTest.duration = test._duration
    this.currTest.updateResult(test)
    this.currTest.context = JSON.stringify(this.currTest.context)
    this.currSuite.addTest(this.currTest)
    this.results.stats.incrementTests(this.currTest)
}

@Antict this works for me:
  afterTest: function(test) {
    if (test.error !== undefined) {
      browser.takeScreenshot();
    }

@drptbl For me it doesn't. Have you added mochawesome to your reporters array in the wdio configuration?
reporters: [
    ['mochawesome', {
        outputDir: './reports/mocha-results/',
        outputFileFormat: function(opts) {
            return `mochawesome-result-${opts.cid}.json`
        },
        stdout: false
     }]
]

afterTest hooks signature has extended a bit in latest wdio v5 versions
afterTest: function(test, context, result) {
}

The context is mocha's this, I think it might be be useful.


fix: Add delete supplement note functionality

Description
Adds the ability to remove a note from a case file
Bug # CE-601
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Manual testing?

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

@Scarlett-Truong I'm not sure I follow what you mean. When I was testing I was making sure to test when there wasn't any other outcome type so I never ran into a problem deleting. I'm not sure that dispatching the caseId makes sense becasue when I create/update/delete a note one of the things I do is reload the casefile to make sure that the changes get applied. Can you show me what you mean tomorrow?

@Scarlett-Truong I see what you mean now. I've updated the notes to reflect that change.

@Scarlett-Truong I see what you mean now. I've updated the notes to reflect that change.

Have you pushed the update @marqueone-ps ? Cuz I haven't seen any changes 😅

Besides the sonar cloud fail at cypress test, everything looks good to me.


For Ruby 2.7 tests use dedicated bundler version

Bundler 2.4.22 is last version to support Ruby 2.7 and needs to be directly installed to prevent an error resolving the supported version. This requirement occurred with the release of bundler 2.5.0.

non-pipeline jobs are still failing. https://github.com/theforeman/jenkins-jobs/tree/master/theforeman.org/scripts/test needs to be updated. @pcreech is working on that now.


[Regression] dbt --quiet ls --output json should not print warnings in 1.6 and 1.7

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I observe this problem with dbt-core 1.7.14. I do not observe this problem with dbt-core 1.7.11
The following command prints a warning, which makes the output invalid json
dbt --quiet ls --output json

[01:19:50  [WARNING]: Deprecated functionality,,User config should be moved from the 'config' key in profiles.yml to the 'flags' key in dbt_project.yml.,{"name": ...

Expected Behavior
Output should be valid json
dbt --quiet ls --output json

{"name": ...

Steps To Reproduce
profiles.yml file:
foo_profile:
  target: bigquery
  outputs:
    bigquery:
      type: bigquery
      method: "{{ var('method', 'oauth') }}"
      keyfile: "{{ env_var('GOOGLE_APPLICATION_CREDENTIALS', '') }}"
      project: "{{ var('data_project', '<redacted>') }}"
      dataset: "{{ var('dataset', 'dbt_' ~ env_var('USER', 'unknown_user')) }}"
      retries: 2
      threads: 8
      timeout_seconds: 300
      location: US

config:
  send_anonymous_usage_stats: False

Then execute
dbt --quiet ls --output json

With dbt-core 1.7.14:
$ dbt --version
Core:
  - installed: 1.7.14
  - latest:    1.7.14 - Up to date!

Plugins:
  - bigquery: 1.7.7  - Update available!
  - postgres: 1.7.14 - Up to date!

$ dbt --quiet ls --output json
01:30:30  [WARNING]: Deprecated functionality

User config should be moved from the 'config' key in profiles.yml to the 'flags' key in dbt_project.yml.
{"name": "...<redacted>

With dbt-core 1.7.11
$ dbt --quiet ls --output json
{"name": "...<redacted>

Relevant log output
see above

Environment
- OS: Linux
- Python: 3.11.8
- dbt:

$ dbt --version
Core:
  - installed: 1.7.14
  - latest:    1.7.14 - Up to date!

Plugins:
  - bigquery: 1.7.7  - Update available!
  - postgres: 1.7.14 - Up to date!

Which database adapter are you using with dbt?
bigquery
Additional Context
No response

Thanks for reporting this @darist !
Digging into the details
Looks like the change the introduced the ProjectFlagsMovedDeprecation warning for you was introduced in dbt-core 1.7.14 - May 02, 2024:

Move flags from UserConfig in profiles.yml to flags in dbt_project.yml #9183 / #9998

This would also likely be an issue in 1.6 and 1.8 because this is included in these PRs as well:

dbt-core 1.6.14 - May 02, 2024: #10008
dbt-core 1.8.0-b1 - February 28, 2024: #9289

Things I tried
Attempt 1
Using dbt-core 1.7.14, I tried both of the following, neither of which had any effect:
dbt --warn-error-options '{silence: all}' list -q
dbt --warn-error-options '{"silence": "ProjectFlagsMovedDeprecation"}' list -q

Log output:
15:16:00  [WARNING]: Deprecated functionality

User config should be moved from the 'config' key in profiles.yml to the 'flags' key in dbt_project.yml.

Attempt 2
Attempting the same commands in dbt-core 1.8.0rc1 raised a ValidationError, and the stack trace ended with:
    raise ValidationError(f"{item} is not a valid dbt error name.")
dbt_common.dataclass_schema.ValidationError: P is not a valid dbt error name.

Attempt 3
I also tried adding this to dbt_project.yml:
flags:
  warn_error_options:
    silence:
      - ProjectFlagsMovedDeprecation

This gave a different error:
Runtime Error
  Do not specify both 'config' in profiles.yml and 'flags' in dbt_project.yml. Using 'config' in profiles.yml is deprecated.

Next steps
In the ideal world for dbt-core 1.6 and 1.7, both errors and warnings should be completely silenced by --quiet without users needing to do anything else. But practically, we might have some other considerations that come into play.
Labeling this as refinement for us to figure out how users should silence warnings like this in versions 1.6, 1.7, and 1.8+.

@dbeatty10 I am wondering how I should handle this with dbt 1.8. Personally, I think it would be good to print out warnings and errors as standard error, not as standard out. By doing so, those doesn't disturb output. Our issue is that the warning message appears in standard out. So, we can't parse resulting output of a dbt Macro with run-operation.  What do you think?

Trying to upgrade to v1.8.4, but this is still a problem. Any idea on ETA for a fix?  Thanks!

@darist we don't have a timeline for this.
But I agree that all warnings should be suppressed whenever the --quiet flag is included.
See below for an example where the UnusedResourceConfigPath warning is suppressed but the ProjectFlagsMovedDeprecation warning isn't.
My (totally unconfirmed) guess is that it has something to do with profiles.yml being parsed earlier than dbt_project.yml and somehow the configuration of the logger is changing in between the parsing of those two files.

Reprex

Create a dbt project that will trigger warnings for both ProjectFlagsMovedDeprecation and UnusedResourceConfigPath:
dbt_project.yml
name: "my_project"
version: "1.0.0"
config-version: 2
profile: "postgres"

models:
  my_project:
    nonexistent_folder:
      +materialized: view

profiles.yml
config:
  use_colors: false

Then list the resources in the project:
dbt list

$ dbt list
00:25:51  [WARNING]: Deprecated functionality

User config should be moved from the 'config' key in profiles.yml to the 'flags' key in dbt_project.yml.
00:25:51  Running with dbt=1.8.3
00:25:51  Registered adapter: postgres=1.8.2
00:25:51  [WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources.
There are 1 unused configuration paths:
- models.my_project.nonexistent_folder
my_project.my_model

Try again with the --quiet flag included and note that the 2nd warning is suppressed from the terminal output whereas the 1st warning still gets through:
$ dbt list --quiet
00:26:46  [WARNING]: Deprecated functionality

User config should be moved from the 'config' key in profiles.yml to the 'flags' key in dbt_project.yml.
my_project.my_model

@yu-iskw I think the only workaround right now is to make the code change to make this warning go away entirely -- in this case, move content from the config: key in profiles.yml to the flags: key in dbt_project.yml.

https://github.com/dbt-labs/dbt-core/pull/10534 will be included in v1.9 when it is released.
https://github.com/dbt-labs/dbt-core/pull/10541 is the backport that will be included in the next patch release for v1.8.


onPress (or onPressIn) not work unless I remove Portal component from container

I can't get onPress or onPressIn events to work with a very basic bar chart. I debugged it for a while and if I remove line #94 from victory-container.js (Portal component) onPressIn event is triggered properly. Is this a new bug or any ideas what's wrong with my code?
I have very basic bar chart like this:
      <VictoryBar
        events={[{
          target: 'data',
          eventHandlers: {
            onPressIn: () => alert('Clicked!')
          }
        }]}
        data={[
                { x: 1, y: 4 },
                { x: 2, y: 3 },
                { x: 3, y: 4 },
                { x: 4, y: 5 },
                { x: 5, y: 5 },
              ]}
      />

And installed versions:
"react": "16.0.0",
"react-native": "0.51.0",
"victory-native": "0.16.1",
"react-native-svg": "6.0.1-rc.1",

@sampsasaarela: I got the similar trouble, but my issue was closed (https://github.com/FormidableLabs/victory-native/issues/206)
Would test removing the line mentioned above to see if it is the exact same problem I encounter

Fixed in<EMAIL_ADDRESS>

@boygirl : I tried 0.16.3, still have to comment out Portal component to have it work

Same here @athirah-yahya. @boygirl, the problem still exists in<EMAIL_ADDRESS>

I investigated this a little bit more and seemed that touches are not delegated through the View component to the SVG component.
I tested to add pointerEvents="none" property to the View (line #91) around the Portal component and it then worked without removing the Portal component.
I saw you @boygirl added touchAction="none" property to the same View, but I didn't find any documentation for that property? pointerEvents property is documented here.
Can you confirm @athirah-yahya if pointerEvents="none" would fix this for you too? And what do you think @boygirl?

@sampsasaarela Yes, I will add that as well.

@sampsasaarela the solution ended up being pointerEvents="box-only". This fix will go out in the next few minutes.

<EMAIL_ADDRESS>

Thanks, @boygirl, works now perfectly.

@boygirl the most recent version has the same issue and the pointerEvents prop has been overwritten

@wkwyatt  Did you find any resolution on this with vicotry-native or did you end up finding another library?  We are using Victory for our web applications and wanted to stay in the Victory Family when going to mobile, but this onPress with a bar graph is the one issue. Just trying to get an idea of other options.

@dahudson88 Luckily my app was only for Android and I ended up using react-native-chart-android, if you need a multi-platform solution then victory-native would probably be better if we could get the onPress to work.

@wkwyatt DANG....aight...cool thanks for the info...Im gonna keep digging to see if I can get something working!

Might be related to this issue


Support for AWS codewhisperer

Awesome project!
I am searching for an AWS code whisperer plugin and found this project. I guess this would be the best place to insert a new AI tool.

sure, PRs are welcomed


Build error with Gradle (5.1.1)

Could not get unknown property 'deps' for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
Build scan at: https://scans.gradle.com/s/6ss2zlss2j2uq

I figured out how to configure the build.gradle file with enough information to pull log4j, and with the 1.2 api compatibility. The following worked for me (with gradle 5.1.1, jdk8):
plugins {
    id 'application'
}

mainClassName = "com.willeke.LDIFGenerator"
executableDir = ""

repositories {
    mavenCentral()
}

dependencies {
  compile group: 'org.apache.logging.log4j', name: 'log4j-api', version: '2.1'
  compile group: 'org.apache.logging.log4j', name: 'log4j-core', version: '2.1'
  compile group: 'org.apache.logging.log4j', name: 'log4j-1.2-api', version: '2.1'
}

distributions {
    main {
        contents {
            from {
                "archiveIncludes"
            }
        }
    }
}

Feel free to enter a pull request and update the code.

Okay, but I haven't worked in Java since 1999 -- there are a half dozen other issues. The build artifacts don't work at all. The batch file generates incorrect paths, and the even the main class name isn't being specified right :)

i.e. You've got it trying to run com.willeke.LDIFGenerator but it's actually com.willeke.ldap.ldif.LDIFGenerator

Got it running but now Java's wonderful (mis)handling of high DPI is another fun thing hah


Add camera fixes

https://mega.nz/folder/ykZglR6J#LOG-hGTqJ3ZOTROwTlG5Hw

These patched executables fix the ancient client bugs that cause your mouse cursor to reset to the center of your screen and / or cause your camera to jump to a different location when clicking. Rename to "Wow.exe" to use with patching tools such as vanilla-tweaks. Source code and offsets are available in the Assembly folder.

Also see discussion in the Turtle WoW Discord:

xxx: I don't think I ever saw that happen but is it related to camera sometimes snapping to random position when you hold down right click?
yyy: this should also fix that bug, they're related

[16:54]Bon: all i had to do was make the cursor position reset function point to the variable that stores your mouse coords when you click, and move the stored position away from the edge of the screen if it's too close
[16:54]Bon: so the bug still happens, but it doesn't matter because it resets to where it should be

Pasting these here for the record so I don't have to look them up on Discord every time.

Adding more details since it's interesting. So basically, the patch was created by Bon (discord name bonbigz), and this is the description he posted on the Turtle WoW discord:

i patched vanilla, tbc, and wotlk clients, which can be found here:
https://mega.nz/folder/ykZglR6J#LOG-hGTqJ3ZOTROwTlG5Hw
i don't plan on patching any other clients, but everything necessary to apply it yourself can be found in the Assembly folder if you're willing to learn how to use Ghidra
the problem is that there's a race condition in the cursor reset code, sometimes the cursor will reset before it releases control of the camera and snap your camera or send your cursor to the center of your screen when you release left or right click
the patch gets around the problem by setting the stored cursor position variable to the position of your cursor when you started controlling the camera instead of the center of your screen (the race condition still happens, but it doesn't matter since it resets to the position it already is)
but this creates a new problem where you can't control your camera if your mouse is on the edge of your screen, so i also move your cursor slightly away from the edge of your screen if it's too close


allOf doesn't work

Not quite sure how to reproduce this in a useful way, I have a schema like this, which extends a schema in allOf. Even though I have ensure that the accept exists in header in programmatic level, it is not reflected in the type generated by this library.
import { FromSchema } from "json-schema-to-ts";

const defHeaderSchema = {
	type: "object",
	properties: {
		header: {
			properties: {
				accept: {
					type: "string",
					pattern: "application/(?:\\*|json)|\\*/\\*"
				}
			},
			required: ["accept"]
		}
	},
} as const

const postSchema = {
	allOf: [ defHeaderSchema ],
	type: "object",
	properties: {
		body: {
			type: "object",
			properties: {
				number: {
					type: "string"
				},
			},
			required: ["number"]
		}
	}
} as const;

let obj!: FromSchema<typeof postSchema>

See the final type by hovering on obj

Hi @winston0410 ! See https://github.com/ThomasAribart/json-schema-to-ts/issues/79 : Your header schema misses a type: "object" keyword !

Right after adding that back in, the type is generated perfectly. Thanks!


CI: stress test - save last two db states

When a CI stress test fails, it is not possible most of the times to reproduce the error if the db is not saved.

duplicate of #798


Show permanent toast if duration is None

Hi,
Currently all toasts will be destructed after a few seconds, but sometimes we need to show permanent toasts, namely toasts that will not be automatically destructed, even after the program exits.
Now we can pass duration=None to specify that we do not want our toasts to be automatically destructed.

Brilliant fork, works very well imo.

In case anyone is interest, I have merged this branch and the callback features on this fork

@Berailitz this does not work on my PC. I installed directly from your git repository but the toast still disappears.
t = ToastNotifier()
t.show_toast('Hey', duration=None, threaded=True)

My PC is:

Windows 10 Pro 1803
Anaconda python 3.7

Any updates on the state of this PR and whether or not it will be merged, @jithurjacob? I'm looking to use this package in one of my projects and this is the one feature I need that is missing.


Should the azure-npm work with AKS & Advanced Networking?

Is this a request for help?:

Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
Which release version?:

Which component (CNI/IPAM/CNM/CNS):
CNI / azure-npm
Which Operating System (Linux/Windows):
Linux
For Linux: Include Distro and kernel version using "uname -a"

For windows: provide output of "$(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion"

Which Orchestrator and version (e.g. Kubernetes, Docker)
Kuberentes: Azure AKS (1.11.5) with Advanced Networking
What happened:
Installed

kubectl apply -f https://raw.githubusercontent.com/Azure/acs-engine/master/parts/k8s/addons/kubernetesmasteraddons-azure-npm-daemonset.yaml

but network policies get ignored
What you expected to happen:
Network Policies get enforced
How to reproduce it (as minimally and precisely as possible):
Apply  kubectl apply -f https://raw.githubusercontent.com/Azure/acs-engine/master/parts/k8s/addons/kubernetesmasteraddons-azure-npm-daemonset.yaml and try to deny traffic to a namespace.

Anything else we need to know:

Hi @cmendible , could you please share the policy yaml you are applying? Everything in my cluster works fine.

Hi @saiyan86 I was using the policy explained here to deny all traffic:
https://github.com/ahmetb/kubernetes-network-policy-recipes/blob/master/01-deny-all-traffic-to-an-application.md

@cmendible
#307 should address this among a bunch of new changes.


ImproperlyConfigured

ImproperlyConfigured is raised when creating an assignment.

I cannot recreate this.. Can you drop your database and look, if this appears again?

I cannot replicate the problem after dropping the database. Fixed.

I was wrong. Problem still occurs. It seems to be related to the projector view.

Can you provide your database and instructions how to recreate? (E.g. mailing it to me)

Steps to replicate problem:

Open Antrag 1
Click "Projezieren"
Click 1. Abstimmung bearbeiten
Click "Abstimmungsergebnis projezieren"

fixed with #67

No, we must not yield them: They are yielded, if the motion is yielded, because the motion is the root rest element.

Aha, I see. You're right. I need to watch the motion:

No, you can just watch for the motionpoll. This should work, because it is an own model in the client.

The debugger cannot find the motionpoll.


compiler error on dynamic_vector_buffer

I am trying to yse a dynamic_vector_buffer with an underlying uint8_t vector. (This is a class data member). But when I declare the dynamic_vector_buffer I see the following compiler error.
asio::dynamic_vector_buffer   m_in_db = asio::dynamic_buffer(_in_buf);
and my _in_buf is of type vector<uint8_t>
--- Error I see ---
srvr.cpp:89:35: error: missing template arguments before ‘m_in_db’
asio::dynamic_vector_buffer   m_in_db =
Also I am not sure on using boost::optional to declare the dynamic_vector_buffer as a data member.
Appreciate the help note @vinniefalco

This is an asio question.
The error message is telling you that dynamic_vector_buffer is a template class, and you have not provided template arguments.
Let's wait until we have solved that, before we talk about the boost::optional question.

Got it. I did fix
asio::dynamic_vector_buffer<uint8_t, std::allocator<uint8_t>>   m_in_db =
asio::dynamic_buffer(_in_buf);
I would like to have this m_in_db as a data member as I have my handler a bit involved and not easy to put as a lambda

You'll probably find that you can leave out the , std::allocator<uint8_t> part as this is the default.
The asio dynamic buffers are designed to be lightweight, copyable references to an underlying data buffer (e.g. _in_buf).
You can create the dynamic_buffer when you need it. You don't need to store it anywhere. The operation that uses it will dynamically update the underlying vector _in_buf.

Ahh so if I understand it right - just do an asio::buffer(_in_buf) when I call async_read or async_write ? and the _in_buf will be automatically used as its the underlying storage ?

You'll probably find that you can leave out the , std::allocator<uint8_t> part as this is the default.
The asio dynamic buffers are designed to be lightweight, copyable references to an underlying data buffer (e.g. _in_buf).
You can create the dynamic_buffer when you need it. You don't need to store it anywhere. The operation that uses it will dynamically update the underlying vector _in_buf.

I did leave it and it complained about the template class needing 2 params.

Ahh so if I understand it right - just do an asio::buffer(_in_buf) when I call async_read or async_write ? and the _in_buf will be automatically used as its the underlying storage ?

Yes, but only for ASIO async operations. Beast async operations require that you use the Beast dynamic buffers, which are different, and passed by reference.

I did leave it and it complained about the template class needing 2 params.

My mistake.

Ahh so if I understand it right - just do an asio::buffer(_in_buf) when I call async_read or async_write ? and the _in_buf will be automatically used as its the underlying storage ?

Yes, but only for ASIO async operations. Beast async operations require that you use the Beast dynamic buffers, which are different, and passed by reference.
You mean some thing like beast::multi_buffer ? I really need an under lying uint8_t based storage container in the buffers.
and the dynamic_vector_buffer seems to be a good fit. Doesnt that gel well with beast websocket stream async_read and write calls ?

I did leave it and it complained about the template class needing 2 params.

My mistake.

Can we consider this issue closed?

Yes thanks for the help. By the way where can I post questions on ssl::context specifically on set_password_callback for private key files ?

ssl::context is a thin wrapper around OpenSSL.
The OpenSSL documents are a good place to start, and stackoverflow has a good deal on inormation.
You can also join the CppLang slack and see who's online to help you, start in the #beast channel where I live.
https://cppalliance.org/slack/


Revert "Changes to analog design consistency checks."

Reverts efabless/mpw_precheck#164

@jeffdi As per my slack comment, you probably want to remerge this.
As you are probably painfully aware, the precheck for analog designs is not passing. I see some changes in caravel/caravel-lite that will solve the current issue, but I think there is another hidden issue. I believe we had a problem before with the requirement that the user_analog_project_wrapper be connected to nets named vccd1_core, vssd1_core etc. At one point this text was added to the layout so the nets would extract with the correct names, but the gds implementation also caused these nets to become ports. Because of the port mismatch, I believe these texts were removed which leaves us with the original problem.
I created a pull request to mpw_precheck that uses caravan.v instead of caravan.spice for the consistency checks. This should work without having to update the caravel/caravel-lite repos.

@d-m-bailey :  If we're generating GDS with a recent PDK now, then this issue should be solved---ports should be written to and be read back from GDS correctly.

@RTimothyEdwards It's not a port issue! It's an internal net issue - is that what you're referring to - being able to label a net without having it extracted as a port?
Incidentally, changing the magic tech file cifin variant may be causing problems in the precheck XOR.
Loading "/Volumes/export/isn/soumil/efabless/mpw_precheck/checks/xor_check/erase_box.tcl" from command line.
"sky130(vendor)" is not one of the CIF input styles Magic knows.


[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

/cc knative/operations-wg-leads
/assign knative/operations-wg-leads

/ok-to-test
/lgtm
/hold
@houshengbo why is operator so far behind?


[YUNIKORN-1597] e2e tests: Recover assigned pods in Bound state

What is this PR for?
The PR contains an e2e test which validates that YK can recover properly with Running/Pending placeholders.
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1597
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

I don't think we want to add the taints/tolerations to helm or refer to kind directly, as these tests are meant to be runnable on all types of clusters (not just kind). Can we eliminate this?

Alternate approach: Query the cluster for nodes with available capacity, and construct nodes with nodeAffinity specified so that they are only schedulable on those nodes.

I'm -1 on this approach as it doesn't allow for running on anything but a Kind cluster. Our tests should be cluster-agnostic, and adapt to the environment they are run in so that they can be used on real clusters as well.
Yeah, most tests are agnostic, but there are some (maybe just the one which I modified) which already depends on having 3 nodes (1 control + 2 worker). Perhaps the existing tests should be fixed, too in a follow-up JIRA.

Alternate approach: Query the cluster for nodes with available capacity, and construct pods with nodeAffinity specified so that they are only schedulable on those nodes.
Hm, interesting. I'll try this.

Test failure seems to be unrelated.

@pbacsko PR has introduced new methods to set/remove node labels etc. There was a need to add taint/untaint node methods as well to remove the dependency on k8s test framework. Hence used some methods from this PR to above said PR. So, Please rebase your wc and take it forward.


Ugly aliasing artifacts on gauges and slider tracks

I'd like to simply increase the size of the overlay so that the background color is completely obscured. Haven't found a reliable way to target these elements yet.

Related to #66


Rendering commands replay cause GPU crash if the “Ref all Resources” option is checked

Description
If "Ref all Resources" option is not checked, it's fine.

Steps to reproduce

Captured file:
GPUDeviceLostOnReplay.zip
NoCrashVersion.zip
Environment

RenderDoc version: 1.33
Operating System: Windows 10 22H2
Graphics API: Vulkan
GPU: Nvidia RTX 3060
Nvidia Driver Version: 551.52

Sorry to say unable to reproduce the crash on two different nVidia system.
Both systems have newer drivers than used in the capture and this might explain why the crash is not reproducible.
In case, it hasn't been done it would be worth checking your application is free of Vulkan Validation Errors when running outside of RenderDoc. RenderDoc relies upon and requires correct API usage and accidental API mistakes can cause errors and crashes in RenderDoc (and drivers).
There should be no requirement to use "Ref All Resources", be good to know if you are seeing a problem in the working capture that was the rationale for using "Ref All Resources"

Thank you very much for your comments and suggestions! I tried installing the latest version of NVIDIA driver 560.70 and the crash doesn't happen anymore. There are no errors reported at the validation layer level, so I think this is indeed an underlying driver issue.


Correct the spelling of CocoaPods in README

This pull request corrects the spelling of CocoaPods 🤓
https://github.com/CocoaPods/shared_resources/tree/master/media
One day I’ll make a bot that looks through the READMEs of all Pods, looks to see if it uses “Cocoapods” and PRs “CocoaPods” :D— Ørta (@orta) February 10, 2016

Created with cocoapods-readme.

Hey you know, the instructions should use pod update instead of pod install.. let me know if you would like me to correct that as well https://guides.cocoapods.org/using/pod-install-vs-update.html

Assuming you're referring to:

Then, run the following command:

$ pod install

You don't want to change that 👍  - that's correct

my bad!

😕

^ confused

When bringing in a CocoaPod for the first time in your project, you want to run pod install for first time installation. This command keeps the current pods already resolved in the lock file intact and just installs the new Pod (in this case, PrediKit). pod update will run the dependency resolver and update every pod as well as installing the new pods referenced in the Podfile.

Thanks for the correction though! I always make this mistake and remember to change it later. Merging.


GlobalVariable.mqh compilation error

Hello,
I have this compilation error:
⛔ : '=' - type mismatch (293,12)
For the line:
m_hm = new HM;
Can you help me to solve it plz?
I found on the web that could be a compilator version error but i think mine is the latest (Version 5 build 2408)

The problem is a recurring one... Because it is a less commonly used technique, I think the support of this language feature in MetaTrader is buggy. I will look into refactoring this part to avoid this.


refactor : refactoring double quotes, some return statements, and fix #142

This PR is about refactoring some if and return statements and fixing the #142 by changing ngSwitch to ngIf and href to uiSref.

Coverage decreased (-0.6%) to 94.083% when pulling 5b6b24cc3d83b77ca2e5078d9d47e0d772a68b04 on Skahrz:fix-142 into e6e92aa5722d8e8036d405bdd9a5b2dea15da31e on ncuillery:master.


Make Node#numeric_type? aware of rational and complex literals

This PR makes Node#numeric_type? aware of complex and rational literals.
These literals could be treated as numeric.
42r.is_a?(Numeric)  # => true
42i.is_a?(Numeric)  # => true
42ri.is_a?(Numeric) # => true

Thanks! Released in 1.13.0