Can't send msg

Hi all!
I have a problem with sending message by this module. I write code like at example, but it does not work. I created a new account on skype and added to my contacts list - live:8584067c9701be5c, because for old contacts in my contact list i can't send msg too. And if i will not put tokenFile param into Skype init i can't login by my acc, but it is another story':). So look:
sk = Skype(login, get_pass(), tokenFile=".tokens-fred.2")  # connect to Skype
ch = sk.contacts['live:8584067c9701be5c'].chat
ch.sendMsg('hello')
And i get the error:

Traceback (most recent call last):
File "%user_path%/bot/bot_main.py", line 88, in
ch.sendMsg('hello')
File "%user_path%\lib\site-packages\skpy\chat.py", line 140, in sendMsg
"Has-Mentions": mentions, "skypeemoteoffset": meOffset})
File "%user_path%lib\site-packages\skpy\chat.py", line 81, in sendRaw
auth=SkypeConnection.Auth.RegToken, json=msg).json().get("OriginalArrivalTime")
File "%user_path%\lib\site-packages\skpy\conn.py", line 215, in call
raise SkypeApiException("{0} response from {1} {2}".format(resp.status_code, method, url), resp)
SkypeApiException: ('400 response from POST https://client-s.gateway.messenger.live.com/v1/users/ME/conversations/8:live:8584067c9701be5c/messages', <Response [400]>)
Uncaught exception

Thanks for all and best regards

Hi, please set SKPY_DEBUG_HTTP=1 in your environment and try it again -- this will output the underlying requests to Skype's servers, so please include the request and response for the 400 error above.  Are you able to retrieve messages from the conversation (SkypeChat.getMsgs()) or does that fail too?

And if i will not put tokenFile param into Skype init i can't login by my acc

As in, you can't login at all without a token file, but can if you choose to write one?  (As opposed to loading an existing one, which would have required a successful login without a token file before.)

endpoint_error.txt
So, i attached a file with stacktrace of the error. It is problem with endpoint. I can skip this error if i will comment out
if endpoint:
    endpoint.config()
    self.endpoints["main"] = endpoint
    self.syncEndpoints()
this code and then i can get a token and connection. And then i be able to retrieve messages from the conversation (SkypeChat.getMsgs()) by this token. But i can't send message.
P.S. Second question about connect only with tokenFile param closed :+1: )

So I think this part is interesting:
<= [09/02 11:01:03] POST https://client-s.gateway.messenger.live.com/v1/users/ME/endpoints
{'json': {'endpointFeatures': 'Agent'}}
=> [09/02 11:01:05] 200
[{u'id': u'2cd7916c-4472-7ac0-d06e-7349d13392c1',
  u'isActive': True,
  u'networks': [],
  u'policies': {},
  u'subscriptions': [{u'channelType': u'TcpSocket',
                      u'conversationType': 0,
                      u'eventChannel': u'',
                      u'eventServiceName': u'',
                      u'id': 0,
                      u'interestedResources': [u'/abch',
                                               u'/v1/threads/ALL',
                                               u'/v1/users/ME/conversations/ALL/messages',
                                               u'/v1/users/ME/conversations/ALL/properties',
                                               u'/v1/users/ME/contacts/ALL'],
                      u'packageSid': u'',
                      u'template': u'',
                      u'type': u'Subscription',
                      u'xuid': u''}],
  u'type': u'Endpoint'}]
<= [09/02 11:01:05] PUT https://client-s.gateway.messenger.live.com/v1/users/ME/endpoints/2cd7916c-4472-7ac0-d06e-7349d13392c1/presenceDocs/messagingService
{'json': {'id': 'messagingService',
          'privateInfo': {'epname': 'skype'},
          'publicInfo': {'capabilities': '',
                         'nodeInfo': 'xx',
                         'skypeNameVersion': 'skype.com',
                         'type': 1,
                         'version': '908/<IP_ADDRESS>'},
          'selfLink': 'uri',
          'type': 'EndpointPresenceDoc'}}
=> [09/02 11:01:05] 404
{u'errorCode': 729,
 u'message': u'You must create an endpoint before performing this operation.'}

We try to create an endpoint for you, which returns 200 success rather than 201 created, suggesting you already have one.  But the response only contains a different endpoint -- it's a TcpSocket type so presumably you were running a desktop/mobile client on the same account?  The configure call tries to configure that endpoint rather than the one we want.  🤔
Can you try it again but also printing out the headers, specifically for the call to POST https://client-s.gateway.messenger.live.com/v1/users/ME/endpoints?
Until I can improve the debug code, you can add this to conn.py:
diff --git a/skpy/conn.py b/skpy/conn.py
index de1fcdd..58df16c 100644
--- a/skpy/conn.py
+++ b/skpy/conn.py
@@ -116,4 +116,5 @@ class SkypeConnection(SkypeObj):
         if os.getenv("SKPY_DEBUG_HTTP"):
             print("=> [{0}] {1}".format(datetime.now().strftime("%d/%m %H:%M:%S"), resp.status_code))
+            print(pformat(dict(resp.headers)))
             try:
                 print(pformat(resp.json()))

endpointResp_header.txt
i attached a file with headers which you mybe want. Because error raise in other method: endpoint.config(). And your print do not work. So i found, that there was not endpoint into token header and content is empty too.

It seems you're not given an endpoint at all.  🙁  I'm not sure what the correct behaviour is here as I haven't come across this with my test accounts before.  The next step would be to compare with Skype for Web and see how that handles this case, if you're up for the challenge...
Sign in at https://web.skype.com with DevTools open on the Network tab, and look for a POST request to /v1/users/ME/endpoints (either from client-s.gateway.messenger.live.com, or a subdomain like db1-client-s.gateway.messenger.live.com) -- check if the response differs from what SkPy gives you.  I'll also need to know what other requests it makes to get an endpoint.
Unfortunately there's a lot of cruft and noise from analytics and other non-important requests going on.  If you're using Chrome, here's a filter string to cut some of it out:
-method:OPTIONS -domain:browser.pipe.aria.microsoft.com -domain:trouter.io

Hi!
Exuse me for delay, week-ends :)
I investigated response of web skype and found some information. So, look at the pictures:
1)It was the error to get the endpoint:

Error text with hint:

And location:

I think it is answer to my problem. Can you check it, please?

Ok, so that's the expected behaviour -- you get your endpoint in the registration token, and you get sent to a different cloud host.  Both of these cases should be handled, but this call in SkPy is giving you a different result in the first place.  Presumably the request body still only includes endpointFeatures = Agent as it does in SkPy?
If you've used Skype for Web (or just signed in with the corresponding Microsoft account) on that device/browser before, it may be caching some credentials and altering the login flow, so it may perform differently if you clear your cookies / go incognito (though I am doubtful).

Hey, i investigated network log again and found another responce with endpoint. First responce with OPTION method and had 200 return code like in SkPy without endpoint data. And after, the second responce had return code 404 and message about "Location" parameter. Look attached zip wtih .har log file( try  this resource, Please, change it to .har format, because github have not wanted to attach .har file and in zip too o_O)
web.skype.com.txt

Thank you a lot! I resolved problem and using module now. :1st_place_medal:

Oh?  🙂  What was the solution in the end?


Migrate runtime/observatory/tests/service/ tests off unittest

There are 176 test files in that directory that use the ancient unittest package. That package was deprecated years ago, well before Dart 2.0. It has not been touched or maintained in ages. We do not intend to migrate it to NNBD and would like to completely delete it from the SDK repo.
Ideally, they would be migrated to only use "package:expect/expect.dart" and "package:async_helper/async_helper.dart". If that's too difficult of a migration, the libraries "package:expect/minitest.dart" and "package:async_helper/async_minitest.dart" provide an API that mirrors a subset of the unittest API. Migrating to those should be fairly straightforward.
(I intend to merge "minitest.dart" and "async_minitest.dart" into a single library. If I do, I will update this issue.)
Who owns these tests? Can they own this migration?
@a-siva cc @vsmenon

/cc @bkonyi @rmacnak-google

Thanks for alerting me to this @alexmarkov. This was resolved a couple of months ago and there's no longer any usages of package:unittest in the runtime tests.


Addition of "$ref" property to enable flexible configuration composition

Problem
Multiple teams collaborating on a common codebase may have different dependency or setup needs and currently this is done by sharing a single devcontainer.json configuration with all of their individual needs combined. https://github.com/microsoft/dev-container-spec/issues/6 describes support for multiple configuration files, but there isn't set a way to consolidate the shared configuration into a single file.
A simpler approach to solving this problem is proposed in https://github.com/microsoft/dev-container-spec/issues/22 while this aims to be a more complete solution. However, it's unclear if this level of support is truly necessary.
Proposed Solution
Taking influence from JSON Schema and the Open API 3.0 specs, a special property named "$ref" would allow importing all or part of a referenced document. Here is an example:
Given a file "defaults.json":
// .devcontainer/defaults.json
{
    "name": "microsoft/foo",
    "extensions": [
        "/root/hello-githug.vsix"
    ],
    "forwardPorts": [80, 5432]
    "hostRequirements": {
        "storage": "64gb",
        "memory": "32gb"
    },
    "portsAttributes": {
        "80": {
            "label": "web"
        },
        "5432": {
            "label": "postgres"
        }
    }
}

If a team would like to introduce a team-specific configuration that adds ports for Redis, they can add a new configuration:
// .devcontainer/redis-team.json
{
    "$ref": "defaults",
    "extensions": [],
    "forwardPorts": [ { "$ref": "defaults#/forwardPorts" }, 6379], // Explicit merge behavior
    "hostRequirements": {
        "memory": "64gb"    // Require more memory
    },
    "portAttributes": {
        "$ref": "defaults#/portAttributes",                        // Explicit merge behavior
        "6379": {
            "label": "redis"
        }
    }
}

Resulting in a final configuration:
{
    "name": "microsoft/foo",
    "extensions": [],
    "forwardPorts": [80, 5432, 6379],
    "hostRequirements": {
        "storage": "64gb",
        "memory": "64gb"
    },
    "portAttributes": {
        "80": {
            "label": "web"
        },
        "5432": {
            "label": "postgres"
        }
        "6379": {
            "label": "redis"
        }
    }
}

Allowed Values for $ref
The value of a $ref contains a file and optionally a JSON Pointer path separated by a "#"

Import an entire document:  "default", "ports.json",
Import the "forwardPorts" value: "defaults.json#/forwardPorts"

See here for more examples of JSON Pointer paths.
Remote Reference:

File in the same directory, extension optional: "document"
File in the same directory with extension: "document.json"
File in a subdirectory:  "defaults/ports.json"
File in a parent directory:  "../other/defaults.json"

URL Reference:

File at a URI: "https://github.com/microsoft/foo/blob/master/.devcontainer/devcontainer.json"
File at a URI: "https://example.com/configuration.json"

How does this experience differ from https://github.com/microsoft/dev-container-spec/issues/22? Both seem to allow referencing / building off of another devcontainer.json, perhaps with this proposal allowing for referencing a specific property rather than entire file.

They solve basically the same problem, but in different ways. #22 uses a single top-level "extends" keyword to a file that is treated as a "parent" document with while this approach is more flexible, but consequently more complicated. I opened up separate issues for them since they aren't incompatible with one another.


Docs for Transcript should be split between users and implementors

If protocol implementation authors follow the advice on how to use Merlin, it will be exposed to their API clients. This means that the docs for the Transcript struct need to be aimed both at the end-users of cryptographic protocols, as well as implementors.
So the Transcript docs should start by having end-user docs (how to create a transcript and pass it to some protocol) and leave the documentation on how to use it to implement protocols for later.

Not sure when this was fixed, but this is done as of 1.0.3


[Minor bug] error check in hk.transform_with_state

On this line: https://github.com/deepmind/dm-haiku/blob/6f2769e8c8dd35b3fc0e66905c877debea7d525f/haiku/_src/transform.py#L441
the check should be if state is None instead of if state. The current version will trigger if a state is passed in that is empty (i.e. state={}) which leads to a confusing incorrect error message with the wrong method signature
ValueError: Apply must be called with an RNG as the second argument, the required signature is: `apply(params, rng, *a, **k)`

Thanks for the report @albertfgu , I'll get a fix in for this. Here is a minimal reproducer:
>>> f = hk.transform_with_state(lambda: None)
>>> f.apply({}, {}, 'a')
ValueError: Apply must be called with an RNG as the second argument, the required signature is: `apply(params, rng, *a, **k)`. The object was of type <class 'str'>: a


New to front-end and JS

How can I open this project in my machine? Which IDE's should I use? I managed to pull it on docker, but I wanted to see how it works from inside!

@MathGuiMach
I use vscode and this project is optimised to use by it.

@chrisleekr I know you're busy... but when you have a chance try to document something about this on the wiki... I've created a link for called "Developers Corner"... I think this would help other devs to join the project and send their PRs with possible bug fixes, improvements and new features.

@chrisleekr could you explain how it's possible to require files from the directory in this way:
const { logger, mongo } = require('./helpers');
I've got an error because of it. When I rewrite on
const logger = require('./helpers/logger');
it works

@chopeta
Yeah, definitely. When I get time, I will add some.

Hey @dmitriy-sokolyanskiy
That is super weird.
In the helpers folder, there is a file called index.js which exports all the helpers.
That way, this const { logger, mongo } = require('./helpers'); is possible.
It is built under node 14 latest, so it shouldn't have any issue.

@MathGuiMach
I use vscode and this project is optimised to use by it.

I see. Do you have a list of plugins? I'll try figuring out by myself, but it would help;

@MathGuiMach
It should already recommend plugins that I use for the project.
https://github.com/chrisleekr/binance-trading-bot/blob/master/.vscode/extensions.json


How add dropdown suggestion ?

Hi, how to add dropdown suggestion into columns  when writing xls file ?
thanks

If you are referring to "List Data Validations", that is a feature of our Pro builds.  If not, share an example and we can look further.


fixing tslint configuration

Fixes 'tslint.json' file and a few double quotes. Several minor package updates.

Wait to approve it as I'm also updating the Changelog.

Note that I updated the changelog with September 17 as the new release date but we can advance it if you are ok with it.


Fails to build on RN 0.76

Expected Behavior
Package should build succesfully
Current Behavior

Task :amplitude_analytics-react-native:compileDebugKotlin FAILED
e: file:///home/johnf/work/gladly/mobile/node_modules/@amplitude/analytics-react-native/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt:64:25 Type mismatch: inferred type is String? but String was expected

Possible Solution
diff --git a/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt b/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
index cfe7bcab8600fcfdf5d8dd77aeb4ba68ac0a8100..93f2101121cf7e69878f7faeb09ba0e298b9812e 100644
--- a/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
+++ b/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
@@ -55,7 +55,7 @@ class LegacyDatabaseStorage(context: Context, databaseName: String) : SQLiteOpen

     private fun queryDb(
         db: SQLiteDatabase,
-        table: String?,
+        table: String,
         columns: Array<String?>?,
         selection: String?,
         selectionArgs: Array<String?>?,

Steps to Reproduce
Standard steps to add @amplitude/analytics-react-native to your project
Environment

JS SDK Version: 1.4.10
Installation Method: yarn
Browser and Version:  React Native 0.76

Other
As a side note is this package built from this repo? I tried to do a PR but the file in question doesn't exist

I am facing the same issue but with RN 0.73.6

This is on Kotlin SDK, here is a proposal to fix it: https://github.com/amplitude/Amplitude-Kotlin/pull/228

The RN SDK does not use the kotlin SDK underneath. This is the file that needs to be changed
https://github.com/amplitude/Amplitude-TypeScript/blob/v1.x/packages/analytics-react-native/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
But I wonder why its failing now though? Its been like this for a long time. Do y'all use a stricter type checking that makes this fail?

The RN SDK does not use the kotlin SDK underneath. This is the file that needs to be changed
https://github.com/amplitude/Amplitude-TypeScript/blob/v1.x/packages/analytics-react-native/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
But I wonder why its failing now though? Its been like this for a long time. Do y'all use a stricter type checking that makes this fail?

@izaaz Ah, good point, we'll have to patch this version with the fix then.
This issue has only existed since version 0.76 of RN, probably due to a change in compatibility with Kotlin

@johnf there's a missing change fyi
diff --git a/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt b/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
index cfe7bcab8600fcfdf5d8dd77aeb4ba68ac0a8100..9f54fd283f079629ee0eed735d007c83236c43fc 100644
--- a/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
+++ b/android/src/main/java/com/amplitude/reactnative/LegacyDatabaseStorage.kt
@@ -59,7 +59,7 @@ class LegacyDatabaseStorage(context: Context, databaseName: String) : SQLiteOpen
         columns: Array<String?>?,
         selection: String?,
         selectionArgs: Array<String?>?,
-        orderBy: String?,
+        orderBy: String,
     ): Cursor? {
         return db.query(table, columns, selection, selectionArgs, null, null, orderBy, null)
     }
@@ -225,7 +225,7 @@ class LegacyDatabaseStorage(context: Context, databaseName: String) : SQLiteOpen
                 ),
                 DatabaseConstants.KEY_FIELD + " = ?",
                 arrayOf(key),
-                null,
+                DatabaseConstants.ID_FIELD + " ASC",
             )
             if (cursor!!.moveToFirst()) {
                 value = if (table == DatabaseConstants.STORE_TABLE_NAME) cursor.getString(1) else cursor.getLong(1)

any update on this change getting added please?

It seems surprising that Amplitude isn't being very responsive about their React Native SDK (this issue, new architecture...)
This appears particularly noteworthy given React Native's growing popularity among major apps and companies.
One has to wonder if Amplitude's Product Managers are aware of this situation. https://reactnative.dev/showcase

It seems surprising that Amplitude isn't being very responsive about their React Native SDK (this issue, new architecture...)
This appears particularly noteworthy given React Native's growing popularity among major apps and companies. One has to wonder if Amplitude's Product Managers are aware of this situation. https://reactnative.dev/showcase

++
A week to merge an one-line fix seems like an unusually relaxed timeline for resolving an issue that's completely blocking Android functionality on the latest production React Native version, especially from a market leader in analytics.

Apologies for the delay folks.
Here's the PR.
It looks like this issue only happens when the compileSdk version is set to 35.

@huextrat - Thanks for the fix on the kotlin SDK too. It starts throwing an error when I set the compile SDK version to 35 so i'll merge that PR as well.

@johnf can you please try version 1.4.11?

@izaaz looks good


[Migrated] Add Support for using an existing ALB and Listener

Originally from: https://github.com/Miserlou/Zappa/issues/1833 by whahoo
Description
I have been following along and using the ALB events and provisioning PR #1807  that was just merged in by @PeteW and @youcandanch.
I was using those changes and integrating my Lambda's into an existing ALB provisioned via terraform
I have some proposed zappa settings and code changes to allow the use of an existing ALB, multiple Zappa projects can then be deployed onto the same ALB
GitHub Issues

#1832

marking as duplicate of:
https://github.com/zappa/Zappa/issues/723
closing


Drivers are not afraid of shots.

I noticed a bug in which car drivers are not afraid if you shoot near them.

Need to compare it to PC version first. But looks like they act the same.


[WIP] Allow for Custom Margin in  Vertical Stepper Widget

Description
Allow users to set custom margins on the vertical stepper as a hard-coded margin is currently set.
Related Issues
This addresses.
#50635
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[ ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

Hello,
thank you for this work.
When I created the proposal I wanted to be able to custom the margin when calling the Stepper constructor.
More like this :

add " ```
this.margin = const EdgeInsetsDirectional.only(
start: 60.0, end: 24.0, bottom: 24.0)"

-and so declare the parameter in the class `
  final EdgeInsetsGeometry margin;`

What do you think of my vision ?

@QuentinSc right, I was originally trying to initialize it as an optional named parameter but I understand more clearly what you want now. I have added it to the Stepper constructor instead

@maschad
Why is there no further progress?

@proninyaroslav I am still unsure which solution is best, my second opinion or @QuentinSc 's. What do you think?

@maschad
Your option seems more flexible.


Release 2

The first release post-launch, put together following the process outlined in https://github.com/dxw/DataSubmissionService/pull/54.
Changes in this release:

Updated content on the URNs page
Updated home page to show different content to signed in users
Authenticated session required on relevant pages
Release process documentation

:shipit:


More specific message for not allowlisted accounts

Until the user is allowlisted for our service, he/she gets neutral statuses Namespace is not allowed! for the configured jobs requiring allowlisted user. This could be more specific e.g. github.com/<namespace> needs to be approved before building. (initially proposed here) - specify which namespace is being handled with and maybe what the allowlisting is needed for (building here).
TODO:

[ ] agree on a message format
[ ] implement
[ ] update it in the documentation

Currently, the instructions are present:
https://github.com/packit/packit-service/blob/307974f7bba1f349d5b0f9d0c0d3eaa6e988d2b4/packit_service/constants.py#L45-L52
There will be a link to the relevant issue -- covered by #1481
So the last bit is the namespace in the status.

Update:

Redirecting after the installation is not easy to do (this should be covered by #1481)
Here, we can provide the link when trying to use Packit -- as a team, we agreed on a search through the existing issue. (Filtering can be done both in this repo or added to OGR.)

I've updated the TODOs in the description...


[User Story] Penalty for misuse of pauses

Story
As a tutor I would like to have system penalize the student for extra pauses so that the misuse of pauses for gaining thinking time can be avoided.
Description
Currently in unaided study a student can pause the sessions as many times as he likes. However a student can misuse this pause for gaining thinking time for a questions which is unaccounted. Hence if the system can penalize pauses over a threshold (say 2) by cutting points (say 5 per additional pause), the misuse can be avoided.

Agreed, Vivek. Assigned to implementation backlog.


Remove bootstrap-decorator.js from bower distribution

When I install v. 0.8.13 with bower, the bower_components/angular-schema-form/dist directory has the following contents
WHERE_IS_BOOTSTRAP_DECORATOR.md
bootstrap-decorator.js
bootstrap-decorator.min.js
schema-form.js
schema-form.min.js

bootstrap-decorator.js and (bootstrap-decorator.min.js) should not be included in this distribution, because the docs and WHERE_IS_BOOTSTRAP_DECORATOR.md state that this has been moved to a separate repository.
Also, bootstrap-decorator.js contains references to templates in directives/decorators/bootstrap that no longer exist.
I assume one should be using bower_components/angular-schema-form-bootstrap/bootstrap-decorator.js? If so, the version distributed with angular-schema-form should be removed to prevent this confusion from arising.

Duplicaate of #699


Statement under Buy a Reserved Instance needs to be modified

"For the Cloud Solution Provider (CSP) program, only the admin agents or sales agents can buy reservations."
should be:
For the Cloud Solution Provider (CSP) program, only the admin agents or sales agents can buy reservations,
unless the partner granted an access to the CSP customers to purchase RI.
Thank you
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 46c0b618-094a-d1c9-f475-c7c9d12a9eda
Version Independent ID: 92c56a66-b596-52f0-8238-91038172fd02
Content: Prepay for Azure virtual machines to save money - Azure Virtual Machines
Content Source: articles/virtual-machines/prepay-reserved-vm-instances.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @vikramdesai01
Microsoft Alias: vikdesai

@v-sashig Thanks for the Feedback. We will check and update the document as appropriate.


🚀 [Feature] Hide GDT display when 0

:rocket: Feature

Hide GDT display when 0
Discussion:
Is this useful? Should we use it as incentive to get some? @BerndHueckstaedt
-> "Buy some GDT today"

I would not hide. I would show 0
Good idea: "Support Gradido now and be thanked with 15x GDT.".

closing in favor of https://github.com/gradido/gradido/issues/188
-> No change for displaying the 0 GDT
-> Needs concept for advertising buy options


TST: test_kolmogorov passes in 32-bit

Another patch aimed at fixing 32-bit wheel build issues described in https://github.com/MacPython/scipy-wheels/pull/37 & with local verification of fix using an i386 docker container as described in #9493.
test_oneovernclose() seemed to need two "fixes" to pass:

use a sized (np.float32) type since float is apparently a C double (float64) in an i386 Python interpreter on 64-bit architecture
reduce the tolerance stringency to something more suitable to single precision

That said, the above fix is only necessary for one of the two tests of this type & even better may be to robustly & portably detect interpreter architecture & dispatch the test stringency from there, maybe. Not sure if that is in scope for this fix / for now.

@tylerjereddy wrote:

use a sized (np.float32) type since float is apparently a C double (float64) in an i386 Python interpreter on 64-bit architecture

I am confused by this statement.  Are there any platforms or architectures out there where a Python float is not a IEEE 754 64 bit floating point number?   (I haven't looked into the problem you are trying to solve, so your fix might be OK, but the justification sounds fishy.)

Are there any platforms or architectures out there where a Python float is not an IEEE 754 64 bit floating point number?

should always be the case AFAIK

I'd prefer to mark this test as knownfail in 1.2.x, and then investigate what's really going on here and fix it correctly later on in master.

I am confused by this statement. Are there any platforms or architectures out there where a Python float is not an IEEE 754 64 bit floating point number? (I haven't looked into the problem you are trying to solve, so your fix might be OK, but the justification sounds fishy.)

Well if the 64-bit floating point number is involved in any kind of casting or comparison operation internally on a 32-bit interpreter it is certainly possible that an issue may arise that doesn't if it were typed 32-bit, but I'll go ahead and just adjust the unit test to skip or xfail as requested.

AFAIK, Python "float" is always double precision. The C conventions, "float", "double", "long double" are different and not to be confused with the Python convention.

@charris wrote:

The C conventions, "float", "double", "long double" are different

Is there any compiler in wide use today that you know of in which float is not 32 bit (single precision) or double is not 64 bit?

Python float is always double precision and that's the problem here -- we don't understand why without dissecting the internal code a bit more so I'll apply the xfail type flag instead. Is it really hard to believe that a high-precision internal comparison or a casting operation somewhere might break on 32-bit interpreter but not 64-bit when the input is higher precision?

Revised based on comments from @rgommers above -- the conditional xfail is based on the 64-bit platform IS_64BIT check used in the NumPy test suite in a few places.

I didn't check for the test skip locally in an i386 docker container again though -- perhaps that's something that belongs in main repo CI eventually.


feat: add d.ts

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


⚠ ClamAV has degraded performance

In c8aa67e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 7a6e792.


from tensorflow.contrib.layers.python.layers.initializers import variance_scaling_initializer

from tensorflow.contrib.layers.python.layers.initializers import variance_scaling_initializer
ImportError: No module named slim.layers.python.layers.initializers
is there a new way to do this ?

@andreixxi You can import variance_scaling_initializer as from tensorflow.contrib.layers import variance_scaling_initializer.
Please check the gist here. Thanks!
I am closing this issue as it was resolved. Feel free to reopen if the issue persists. thanks!


Download ebook as PDF failed with error fork/exec <download_path> permission denied

Hi, thanks for creating this useful app.
As title suggest, I encountered error when downloading ebook as PDF with error: fork/exec <download_path>: permission denied

How could I solve this issue?

遇到相同问题。

不清楚是怎么安装wkhtmltopdf的，我这边没法复现，或者是保存的目录没有写权限？


Check for nested tags in malicious html (Ajaxer)

Let Ajaxer.cleanHtml() call itself to find potentially malicious html (nested tags not being caught by regex). Potential fix for issue #12.

See, this is awesome. Simple and elegant solution.


Last error code changes on the new get/delete documents routes

Related spec: https://github.com/meilisearch/specifications/pull/236
Motivation
Implement the last changes proposed in the specification:

Get rid of the invalid_document_delete_filter and always use the invalid_document_filter
Introduce a new missing_document_filter instead of returning invalid_document_delete_filter (that’s consistent with all the other routes that have a mandatory parameter)
Always return the original_filter in the details (potentially set to null) instead of hiding it if it wasn’t used

Impacted teams
@meilisearch/docs-team @meilisearch/integration-team

Closed by #3775 and released into v1.2.0-rc.2


Adding propertyNames to json schema failes speccy

Detailed description
I found a bug: I added as a response schema with $ref the following json schema:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "propertyNames": {
    "enum": ["Key1", "Key2"]
  }
}

I got the entry for propertyNames from this stackoverflow question.
When I start speccy via speccy serve openapi/index.openapi.yml -j --verbose it fails with:
GET /path-to-json/seeabove.json #
Expected object or boolean as schema, got array
Expected object or boolean as schema, got array
Expected object or boolean as schema, got array
undefined

Removing the part or renaming it e.g. from "propertyNames" -> "propertyName" at least starts the webserver (even if this schema is not working).
Possible implementation
If displaying some stuff for such validation is hard then at least do not fail or print better message when calling the command. Without the --verbose flag I just got returned undefined and the program exited with code 1.
Your environment

Node Version: v10.1.0
Operating system and version (e.g. Ubuntu 16.04, Windows 7): Kubuntu 18.10
speccy: 0.8.7

Yep this would be expected. The -j switch was designed to convert certain JSON Schema  functionality to OpenAPI, and not all of it has been done. propertyNames is JSON Schema, and that is not a keyword in OpenAPI v3.


Clear or RemoveAll Methods

(Translated by Google)
Hello
How can I clean or empty the grid?
Isn't there a method "clear" or "removeAll" or something similar?
Thank you

Hi marcoas,
There is no "clear" or "removeAll" method available at this moment.
Alternatively, you may load an array with a single empty object to "simulate" clear all rows.
Please take a look this pen for more.
Hope it can help!


Describe result code structure in examples

In the diagrams we use no we only add "200 - OK" as responses. This should be more detailed according to the OOAPI standard

Open questions:
What should the HTTP code be when there is a successful communication, but there are functional errors why the message cannot be handled (example: student association added to a cancelled offering)
2 ways to reason: communication was succesfull:
A. http OK - 200 and detailed status in payload.
B. http Errror - 400? and detailed status in payload
So will use a payload in json with details anyway.

Core -team
PUT :
200 OK
400 - Bad Request - for syntax
409 - Conflict - business rule
401 - Unauthorised
403 - Forbidden
405 - Method not allowed
429 - too many request
500 - server probleem
altijd een reply:
title -
details optional -
GET
200 met data
404 - not found of endpoint is not online.
en andere 4xx codes


Remove any query strings at end of the filename

This fixes the problem you get when trying to save a profile image
pulled from the Facebook graph API.
Example image string:
https://fbcdn-profile-a.akamaihd.net/hprofile-ak-xpf1/v/t1.0-1/10222917_
10152323446467649_8217804623745092321_n.jpg?oh=6eba1683174247d11810cec33
0b2eb5e&oe=54953C34&gda=1422013996_8ff849b29f4370ae833f4b4d8078be5c
If we try to save this image with Stapler, we get the following  error:
Imagine\Exception\InvalidArgumentException
Saving image in
"jpg?oh=6eba1683174247d11810cec330b2eb5e&oe=54953C34&gda=1422013996_
8ff849b29f4370ae833f4b4d8078be5c" format is not supported, please use
one of the following extension: "gif", "jpeg", "png", "wbmp", "xbm"

This issue was not fixed in 1.0.02. If so, can you please specify the commit? I only see the remote file redirect issue being fixed


State root mismatch when running fraud detector

Followed instructions as per https://github.com/omgnetwork/optimism-v2/tree/develop/boba_community/fraud-detector (git commit d7e1311).
After initial sync, all is well. Since yesterday, suddenly mismatches start appearing. Does this have to do with the network maintenance yesterday?
 Same result, state root mismatch for block height 233726.

Thank you for the report! A game on Boba used blockhashes as a source of randomness and this exposed a mismatch between the Geth gas limit settings of mainnet and the develop branch geth .env settings. A fix is pending merge (https://github.com/omgnetwork/optimism-v2/pull/236). Once that is merged, then just restart the fraud-detector and it will correctly verify block 233726. Thank you again for running a fraud detector!

Update - the Geth TARGET_GAS_LIMIT is now reconciled between the develop branch (which is what is used to parametrize the fraud-detector) and mainnet (which is what you are pointing the verifier at).

Thanks for the update. I've ran the detector again and this time all state roots check out. Cheers!


DOM nodes  dragged

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

What problem does this feature solve?
The current DOM node cannot be dragged，However, nodes must use DOM nodes to implement
What does the proposed API look like?
for example ：group.addShape('dom',{attrs:{......},name:'dom-shape',draggable: true,xxxxx:true }

脑袋没转过弯来，自己写原生的就好了。。。。。。


[jsx-pascal-case] Warns on single-character identifiers

If I reference a component using a single character I get a PascalCase warning.
import C from 'common/components/Conditional';
<C ...>

Yep would be nice to fix this one.
import H1 from '../../../UI/Elements/H1';
import A from '../../../UI/Elements/A';

const TermsOfService = () => (

    Terms of Service

);


Unable to commit memory into the active BoI process

Using new version 1.4.4.
[2016-01-24 00:03:54 AM] [TID: 7032] [INFO ] ========== Missing HUD 2 v1.4.4 ==========
[2016-01-24 00:03:54 AM] [TID: 7032] [INFO ] Starting DLL injection monitor thread.
[2016-01-24 00:03:55 AM] [TID: 7032] [INFO ] GitHub reported no updates available.
[2016-01-24 00:04:07 AM] [TID: 3656] [INFO ] BoI process found, time to inject...
[2016-01-24 00:04:07 AM] [TID: 3656] [INFO ] Waiting 4788 milliseconds before injecting.
[2016-01-24 00:04:12 AM] [TID: 3656] [ERROR] Injection thread error occured: [HookBoIProcess] Unable to commit memory into the active BoI process. (Error Code: 0)
[2016-01-24 00:04:26 AM] [TID: 7032] [INFO ] Missing HUD 2 exiting with exit code 0.
[2016-01-24 00:04:26 AM] [TID: 7032] [INFO ] Stopping DLL injection monitor thread.

Nvm, seems like its a tboi problem, not the mod.


Minter becomes "orphaned" when its controller is configured to a different minter

Here is the test case -

masterminter configures (controller, minter1)
controller configures minter1 to have allowance x on denom.
masterminter configures (controller, minter2)
now minter1 is not controlled by any one: nobody can configure her or remove her, even the owner.
minter1 still has the allowance x on denom so she can mint denom to anyone up to the allowance.

Is that a bug?

Blacklisting minter1 can stop her from minting. But is that the solution?

PR #345 has been submitted to fix this issue.


Backport "HBASE-26366 Provide meaningful parent spans to ZK interactions" to branch-2.5

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.5 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 51s
branch-2.5 passed

+1 :green_heart:
compile
3m 52s
branch-2.5 passed

+1 :green_heart:
checkstyle
1m 11s
branch-2.5 passed

+1 :green_heart:
spotless
0m 39s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 52s
branch-2.5 passed

-0 :warning:
patch
0m 43s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 45s
the patch passed

+1 :green_heart:
compile
3m 48s
the patch passed

+1 :green_heart:
javac
3m 48s
the patch passed

-0 :warning:
checkstyle
0m 32s
hbase-server: The patch generated 1 new + 13 unchanged - 1 fixed = 14 total (was 14)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m 20s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotless
0m 40s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m 14s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

44m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4519

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux eb698e71bb6f 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / f4a4f0c05e

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
69 (vs. ulimit of 12500)

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 51s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 51s
branch-2.5 passed

+1 :green_heart:
compile
1m 16s
branch-2.5 passed

+1 :green_heart:
shadedjars
4m 26s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
branch-2.5 passed

-0 :warning:
patch
5m 48s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 32s
the patch passed

+1 :green_heart:
compile
1m 14s
the patch passed

+1 :green_heart:
javac
1m 14s
the patch passed

+1 :green_heart:
shadedjars
4m 25s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 24s
hbase-common in the patch passed.

+1 :green_heart:
unit
2m 29s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 35s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
178m 36s
hbase-server in the patch passed.

205m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4519

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8c9e488ce763 5.4.0-1025-aws #25~18.04.1-Ubuntu SMP Fri Sep 11 12:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / f4a4f0c05e

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/testReport/

Max. process+thread count
2311 (vs. ulimit of 12500)

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 12s
branch-2.5 passed

+1 :green_heart:
compile
1m 24s
branch-2.5 passed

+1 :green_heart:
shadedjars
4m 26s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  3s
branch-2.5 passed

-0 :warning:
patch
5m 56s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 57s
the patch passed

+1 :green_heart:
compile
1m 25s
the patch passed

+1 :green_heart:
javac
1m 25s
the patch passed

+1 :green_heart:
shadedjars
4m 24s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  2s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 37s
hbase-common in the patch passed.

+1 :green_heart:
unit
2m 54s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 38s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
176m 57s
hbase-server in the patch passed.

205m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4519

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ab3632dcbdde 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / f4a4f0c05e

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/testReport/

Max. process+thread count
2520 (vs. ulimit of 12500)

modules
C: hbase-common hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4519/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Use pkg-config To Link CUDA Libraries

It'd be good if collenchyma would link to CUDA libraries out of the box when using it as a feature.
To run the leaf-examples on my machine, I needed to provide my own build.rs to get the cuda lib dir added for link searching.
See this thread on rust users.

Related: https://github.com/autumnai/leaf-examples/issues/7#issuecomment-194841964

We have a build.rs for rust-cudnn, which should be adaptable to this. It should also allow for static linking though I've never tried that out.
Did the leaf-examples build after you added the build script?
I originally planned to add build scripts to the respective packages after #3 and #4 have been resolved, but maybe it also works in this repo. Also related to #46.

It did work once I'd added a build script including my CUDA lib dir. But I'm fairly new to CUDA so I wasn't sure if I'd just installed it incorrectly. Based on your links it looks like there's a bit more complexity in doing this properly than just cowboying it

pkg-config introduce make which introduces a whole lot of new issues

@bklooste As per cargo guide for build scripts using pkg-config is the advocated way. I don't know about any better and widely spread alternative that solves the same problem as pkg-config, but am open to suggestions.

That may be but its a productivity killer ( when it leads to  autoconf/automake)  , was hoping cargo would take us further. .. A lot of large projects over the years went to cmake and Atom and OK  results but then cargo looses its place.
AFAIK cudnn and cuda does not produce pkg-config files  so it still wont be found ,  so you need to create your own pkg-config pc file and rely on LD_LIBRARY_PATH  , which defeats the purpose .. Basically you have to ensure those lib folders are in the LD_LIBRARY_PATH  path and that is mainly due to the way nvidia works.

AFAIK cudnn and cuda does not produce pkg-config files so it still wont be found

pkg-config found both cudnn and cuda easily when the typical build failed, so this is wrong.


Create proper schema

@jeanpaulrsoucy I'm not sure what the scope of this item is, but if this relates to the schema of the API responses, I would like to support this wholeheartedly.
Having versioned APIs, and immutable API response schemas (along with test cases) would go a long way in preventing breakage from clients consuming these APIs.
Nonetheless, thank you for the incredible work in maintaining this great resource.


AlertList panel does not work anymore on latest version

Hi, I tried to upload multiple dashboards today on Grafana (some that I modified and some I did not). I'm using Jenkins to upload my dashboard and it pulls the latest grafonnet version. I have an Alert List dashboard with multiple Alert List panels that I did not modified and used to work with the previous grafonnet version.
However today it seems that the dashboard does not work anymore. I identified the following json code :
      "pluginVersion": "v11.0.0",       "title": "Business Alerts",       "type": "AlertList"
However, a working json is the following :
      "pluginVersion": "v11.0.0",       "title": "Business Alerts",       "type": "alertlist"
Is there a way to change the type ?
Thanks

Not fixed, I'm afk now.


[App] Many features on wandb dashboard are disabled/not available

Describe the bug
I have been experiencing several issues in the past few days when using the wandb dashboard. Some of the issues I am facing include:

Unable to delete an individual run (the 'delete run' option is greyed out)
When I select multiple runs (either to add tags to these runs or to delete them), the options at the top to tag the runs or to delete the runs are greyed out (do not work).

I have tried logging into the wandb dashboard from different browsers but the problem persists.
To Reproduce
Steps to reproduce the behavior:
Try to select multiple runs (on the tables page of the workspace) to add tags or to delete runs
OR
Select a single run, go to the info page, and attempt to delete the run (the confirm delete run option is greyed out for me)
Expected behavior
I should be able to delete a single run, or to perform actions on multiple runs on the tables page of the workspace (such as adding tags or deleting runs)
Screenshots

Operating System

OS: Windows 10
Browser Firefox and Chrome
wandb version: 0.12.7

Hey there, this is a known issue that we are working on right now. I'll notify you once the issue is resolved.

Hi,
The issue seems to be resolved, thanks!


allow geographiclib 2.x

surprisingly hard to track down an upstream changelog, https://geographiclib.sourceforge.io/html/C/changes.html suggests that the API is basically unchanged despite the major version bump.

Thanks!


"All controller endpoint must be async." Possible to make ModelControllerBase async?

I'm trying to take full advantage of djano-ninja's async support. However when I apply AsyncJWTAuth() to a ModelControllerBase I get the error:
Exception: You are using a Controller level Asynchronous Authentication Class, All controller endpoint must be `async`.
Controller=MaterialController, endpoint=create_item_ebca41

I don't see anything about this in the docs. Is the ModelControllerBase abstraction only usable when not using async?
Thanks!
from ninja_extra import ModelConfig, ModelControllerBase, ModelSchemaConfig, api_controller, route

from materials.models import Material
from ninja_jwt.authentication import AsyncJWTAuth

@api_controller("/materials", auth=AsyncJWTAuth())
class MaterialController(ModelControllerBase):
    model_config = ModelConfig(
        model=Material,
        schema_config=ModelSchemaConfig(
            read_only_fields=[
                "id",
            ],
        ),
    )

@evanheckert ModelController at the moment supports only synchronous functions. I am currently looking into an async solution. But for now, ModelController can only work with synchronous Auth functions

Feature is live @evanheckert


operator-sdk new app-operator failed

What did you do
operator-sdk new app-operator failed. It has created app-operator, go.mod, tools.go then it shows new Go scaffold failed, illegal character U+0073 's' in escape sequence (and 11 more errors)).
This is the error shown when I am trying to create new go operator.
What did you see instead? Under which circumstances?
C:\Users\goworkspace\src\github.com\example-inc>operator-sdk new app-operator

time="2019-05-21T10:04:26+05:30" level=info msg="Creating new Go operator 'app-operator'."
time="2019-05-21T10:04:26+05:30" level=info msg="Created go.mod"
time="2019-05-21T10:04:26+05:30" level=info msg="Created tools.go"
Error: new Go scaffold failed: (C:\Users\jz754x\goworkspace\src\github.com\example-inc\app-operator\cmd\manager\main.go:13:7: illegal character U+0073 's' in escape sequence (and 11 more errors))
Usage:
  operator-sdk new <project-name> [flags]

Flags:
      --api-version string          Kubernetes apiVersion and has a format of $GROUP_NAME/$VERSION (e.g app.example.com/v1alpha1) - used with "ansible" or "helm" types
      --cluster-scoped              Generate cluster-scoped resources instead of namespace-scoped
      --dep-manager string          Dependency manager the new project will use (choices: "dep", "modules") (default "modules")
      --generate-playbook           Generate a playbook skeleton. (Only used for --type ansible)
      --header-file string          Path to file containing headers for generated Go files. Copied to hack/boilerplate.go.txt
      --helm-chart string           Initialize helm operator with existing helm chart (<URL>, <repo>/<name>, or local path)
      --helm-chart-repo string      Chart repository URL for the requested helm chart
      --helm-chart-version string   Specific version of the helm chart (default is latest version)
  -h, --help                        help for new
      --kind string                 Kubernetes CustomResourceDefintion kind. (e.g AppService) - used with "ansible" or "helm" types
      --skip-git-init               Do not init the directory as a git repository
      --type string                 Type of operator to initialize (choices: "go", "ansible" or "helm") (default "go")

Global Flags:
      --verbose   Enable verbose logging

***operator-sdk version:
operator-sdk version: v0.7.0+git
*** Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:30:48Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
***go version:
go version go1.11.8 windows/amd64
***git version:
git version 2.21.0.windows.1
***dep version:
dep:
version     : v0.4.1
build date  : 2018-01-24
git hash    : 37d9ea0a
go version  : go1.9.1
go compiler : gc
platform    : windows/amd64
***operating system:
windows10
Please, someone help me with this to solve my problem.

Are you able to face the same issue if you use the master branch of operator-sdk?

@BaddamJhansi we don't test operator-sdk on Windows, so we don't claim to support it. However, we don't think there should be anything that prevents it from working on Windows.
Unfortunately, that error message is not very helpful. Taking a shot in the dark here, could you post the first line of the go.mod file that was generated?

As an aside, that message shows that we don't log much context for these errors. I'll open a PR tomorrow to improve the error messages so that we can try to figure out where this is coming from.

@joelanford Thank you so much for looking into my issue.  I am not unable to open go.mod file. Even main.go file which is in app-operator/cmd/manager/main.go is also empty.

@camilamacedo86 i am facing same issue even using master branch.

@joelanford  Thank you so much for looking into my issue. I am unable to open go.mod file. Even main.go file which is in app-operator/cmd/manager/main.go is also empty.

@BaddamJhansi just to clarify:

You have a go.mod file, but you can't open it to see it's contents? What issue are you having with opening it?
You also have cmd/manager/main.go, but it is empty?
Other than go.mod, tools.go, and cmd/manager/main.go, do any other files exist?

@joelanford  go.mod type is Movie Clip when I am trying to play it is showing

Windows Media Player cannot play the file. The Player might not support the file type or might not support the codec that was used to compress the file.

yes cmd/manger/main.go file is empty.

No, only go.mod, tools.go, and cmd/manager/main.go are created.

 You should be able to open it with a text editor like VS Code, notepad, etc.

@joelanford I think this might be problem with windows machine. It was working fine with ubuntu on virtual box.

@BaddamJhansi I agree that this is likely Windows-specific. My hunch is that we don't handle Windows path segments and file separators correctly. It's hard to know for sure without more information, but I think #1487 may fix your issue.

@BaddamJhansi if you can build the SDK from master and try again, let us know if your issue is fixed.

@BaddamJhansi we think this is fixed for Windows on the latest master. If you get a chance to try it and find that it is not fixed. Please leave a comment and we can re-open.


Do not allocate many string when building str or repr

... for nested data types like lists with multiple elements.
@cjhopman pointed to this issue.

Technically, yes, however:

fmt::Formatter cannot be created directly, only by implementing fmt::Debug or fmt::Display traits, which is not always convenient
fmt::Formatter contains formatter flags, which are not used in to_repr or to_str implementations


feat(project information): add pre-application

:tada: This PR is included in version 2.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fatal: not a git repository, Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Pardon me for the unclear title but even I don't know what else to name it. You can help me in editing this.
Details
I have recently installed futter in my Ubuntu 20.04.1 LTS and now flutter is giving me some errors that I am unable to resolve from the issues already provided here and other websites.
The main issue is that it is showing some errors whenever I try flutter doctor or if I create a new project and try to run it. For installing flutter in Ubuntu, I have followed the steps provided on the official website. I tried installing flutter both via  git clone https://github.com/flutter/flutter.git and by downloading the zip file. But the error keeps showing up in both cases.
Here is my flutter doctor -v:
anupam@anupam-G3-3500:~$ flutter doctor -v
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Failed to find the latest git commit date: VersionCheckError: Command exited with code 128: git -c log.showSignature=false log -n 1
--pretty=format:%ad --date=iso
Standard out:
Standard error: fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Returning 1970-01-01 05:30:00.000 instead.
[✓] Flutter (Channel unknown, 0.0.0-unknown, on Linux, locale en_IN)
    • Flutter version 0.0.0-unknown at /home/anupam/snap/flutter/common/flutter
    • Framework revision  (), 1970-01-01 05:30:00.000
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/anupam/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /home/anupam/Documents/ANDROID_STUDIO/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Android Studio (version 4.0)
    • Android Studio at /home/anupam/Documents/ANDROID_STUDIO/android-studio
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.48.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.14.0

[!] Connected device
    ! No devices available
! Doctor found issues in 2 categories.

Even while running the new project, it is not running and waiting for indefinite time.
anupam@anupam-G3-3500:~/proj$ flutter run
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Using hardware rendering with device sdk gphone x86 arm. If you notice graphics
artifacts, consider enabling software rendering with
"--enable-software-rendering".
Launching lib/main.dart on sdk gphone x86 arm in debug mode...
Running Gradle task 'assembleDebug'...
Checking the license for package Android SDK Build-Tools 28.0.3 in /home/anupam/Android/Sdk/licenses
Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.
Checking the license for package Android SDK Platform 28 in /home/anupam/Android/Sdk/licenses
Warning: License for package Android SDK Platform 28 not accepted.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
     build-tools;28.0.3 Android SDK Build-Tools 28.0.3
     platforms;android-28 Android SDK Platform 28
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

  Using Android SDK: /home/anupam/Android/Sdk

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5m 32s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                       333.3s (!)
Exception: Gradle task assembleDebug failed with exit code 1
Please help.
Target OS Version
anupam@anupam-G3-3500:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal

Here is the git status:
anupam@anupam-G3-3500:~/proj$ git status
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Device
Dell G3 3500

@akcgjc007
I don't want to be "that guy" that answer with "do this instead",
but I believe we, Ubuntu users, have by far the best flutter installation experience
and it's a pity not to exploit it.
You may want to try, installing flutter through snap instead of git
Then if you want the master channel just run
flutter channel master
flutter upgarde -f

Hi @iapicca
I am following ur suggestions.
So I ran this command sudo snap install flutter --classic, and this happened as I have already flutter installed.
anupam@anupam-G3-3500:~$ sudo snap install flutter --classic
[sudo] password for anupam:
snap "flutter" is already installed, see 'snap help refresh'

Following other two commands of yours are following:
anupam@anupam-G3-3500:~$ flutter channel master
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Switching to flutter channel 'master'...
git: fatal: not a git repository (or any parent up to mount point /)
git: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Switching channels failed with error code 128.
anupam@anupam-G3-3500:~$ flutter upgrade -f
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
ProcessException: Process exited abnormally:
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
  Command: git fetch --tags

The current status of flutter doctor is:
anupam@anupam-G3-3500:~$ flutter doctor
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Doctor summary (to see all details, run flutter doctor -v):
Failed to find the latest git commit date: VersionCheckError: Command exited with code 128: git -c log.showSignature=false log -n 1
--pretty=format:%ad --date=iso
Standard out:
Standard error: fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Returning 1970-01-01 05:30:00.000 instead.
[✓] Flutter (Channel unknown, 0.0.0-unknown, on Linux, locale en_IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.48.2)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Please suggest something I can do.
Also if someone can suggest me how do I uninstall flutter. Maybe reinstalling might help.

Hi @akcgjc007
Can you please go to the existing flutter setup and execute git reset --hard. If you see a git error, it might git related issues. After git reset --hard works then flutter doctor -v
Check your git installation git --version, please update it to the latest git version and try git clone flutter again and delete the existing one.
Let me know if this helps your situation
Thank you

@akcgjc007
sorry for creating confusion,
I meant to uninstall the previous on first,
not to snap install on top of it

anupam@anupam-G3-3500:~$ sudo snap install flutter --classic
[sudo] password for anupam:
snap "flutter" is already installed, see 'snap help refresh'

Thanks @iapicca . Uninstalling the previous version of flutter using sudo snap remove flutter and then reinstalling using sudo snap install flutter --classic helps.
anupam@anupam-G3-3500:~$ sudo snap install flutter --classic
flutter 0+git.142868f from Flutter Team* installed
anupam@anupam-G3-3500:~$ flutter doctor
Initializing Flutter
Downloading https://storage.googleapis.com/flutter_infra/releases/stable/linux/flutter_linux_1.20.3-stable.tar.xz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  530M  100  530M    0     0   757k      0  0:11:56  0:11:56 --:--:--  717k^[[3~
Flutter initialized
Flutter 1.20.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 216dee60c0 (6 days ago) • 2020-09-01 12:24:47 -0700
Engine • revision d1bc06f032
Tools • Dart 2.9.2
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.3, on Linux, locale en_IN)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.48.2)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Can't tell if it was a git caused issue. I was using git version 2.25.1, have now updated it to the latest version. Still thanks @TahaTesser


"duplicate session" error when re-attaching

Cool package. Thanks for making this.
I have a package.json script: "start": "tmex -r -n dev",
When I do npm start I get an error:

duplicate session:

I'd expect -r to make it so that it attaches to the existing session, avoiding this error. If I do tmux a I can manually reattach.

Hey @altano, thanks for reporting this. Have to admit I'm a bit puzzled by it – when I add this as a package.json script and run it things seem to work as expected. There's a section of code which determines whether to attach-session or kill-session here:
    # either attach to an existing session or kill it based on specified behavior
    if tmux has-session -t "${argsession}" 2>/dev/null; then
      if [[ "${argreattach}" == true ]]; then
        tmux attach-session -t "${argsession}"
        exit 0
      else
        tmux kill-session -t "${argsession}"
      fi
    fi

    # execute constructed tmux command
    tmux "${tmuxargs[@]}"

In my case, ${argsession} is "tmex" (the default if you don't provide a session name) and the first branch of that if statement executes because if tmux has-session -t "${argsession}" is true. However, if I force that to be false, execution skips to the bottom – tmux "${tmuxargs[@]}" – and I see the "duplicate session" error you're running into.
 I'm wondering if there's some differing behavior between tmux versions I'm unaware of.
$ if tmux has-session -t "tmex"; then echo "session 'tmex' found"; fi
session 'tmex' found

Hey @evnp, thanks for looking into this.
I figured out the issue with your pointer.
My package name has periods in it, e.g. "my.package.name". The tmux session getting created is "my_package_name". So tmex can't find it, because it's using "my.package.name".
Workarounds:

Option 1: manually specify the session, e.g. change package.json to:

"scripts": {
    "start": "tmex my_package-name -r -n dev",
    ...
}

Option 2: change the package name to a valid tmux session identifier

If you're feeling generous you could try to fix this in tmex, but I cannot find reference documentation on what tmux considers valid and what it does to automatically convert session names, so I'm not sure what that fix would look like.
I'm going with workaround option 1 for now. Thank you again for your help.

Ah, that makes perfect sense! I was unaware that tmux did any manipulation of session name strings (and had briefly forgotten about the npm package name -> session name feature when writing that response – thanks for figuring out the rest).
Nothing too generous, but I would like to avoid others running into this in the future – what do you think of https://github.com/evnp/tmex/commit/5d3a4ef6fe5360b2d7990768bb6a996b2f77d3fc as a fix? At least for the use-cases I'm aware of, it seems to allow --reattach to work as expected without anything disruptive (eg. raising an error message if troublesome chars are present).

Thanks again @altano, https://github.com/evnp/tmex/releases/tag/v1.0.9 is now published with the fix.


Provide ability to manage metadata

If we provide the ability for an entity to manage its own metadata
To the engineers
Then they will be able to augment an instantiated object with further data attributes without having to redefine the class
To validate this we will:

[x] - Demonstrate that a struct can be modified to add the necessary attributes dynamically
[x] - Demonstrate that a struct can be modified to add the metadata attribute optionally
[x] - Demonstrate that a impl new() can be modified to set the necessary attribute values without overwriting any existing core attributes
[x] - Demonstrate that a impl new() can be modified to set the metadata attribute value if the attribute exists in the struct
[x] - Ensure all the tests are passing
[x] - Confirm documentation is up to date

Release in version 0.1.0


Update serv.css

Added the padding needed to make the cards look more readable and visually appealing.
This fixes the issue #103

Hello sir! The pull request doesn't have a WOB label..could you please add it. Thank you.


Error when using with react-native-web

while use with react-native-web when run yarn web successfully created but when running on browser have an err

while use with react-native-web when run yarn web successfully created but when running on browser have an err

"react-native-vector-icons": "^10.0.3",
"react-native-web": "^0.19.10",
"react-native": "0.73.4",

I can't see anything in the screenshot that is RNVI related. Can you share a reproducible example?

Closed due to no response


Cannot pul any image from docker hub registries

Hello,
just accessed PWD this morning, was working fine last time I used this but today cannot pull any image. See below:

[node1] (local<EMAIL_ADDRESS>~
$  docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout.
See 'docker run --help'.
[node1] (local<EMAIL_ADDRESS>~
$ docker run -dp 80:80 docker/getting-started:pwd
Unable to find image 'docker/getting-started:pwd' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
````

maybe temporary outage from some sort? I see no problems now.
On Sun, Feb 12, 2023 at 4:56 AM fckbo @.***> wrote:

Hello,
just accessed PWD this morning, was working fine last time I used this but
today cannot pull any image. See below:
[node1] (local) @.*** ~
$  docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout.
See 'docker run --help'.
[node1] (local) @.*** ~
$ docker run -dp 80:80 docker/getting-started:pwd
Unable to find image 'docker/getting-started:pwd' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

—
Reply to this email directly, view it on GitHub
<https://github.com/play-with-docker/play-with-docker/issues/570>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMBLWQ46MXMONKVJYTLSW3WXCJSVANCNFSM6AAAAAAUZFFB7U>
.
You are receiving this because you are subscribed to this thread.Message
ID<EMAIL_ADDRESS>


Select component has overlapping icons on the far right

Bug report
Version: 0.6.1
There seems to be 2 icons overlapping - one in a <span> while the other as a background-image for the Select component

Did a bit of digging - this is cause I'm using the select wrapped within a form element, and tailwindcss has its own innate class style to give that down chevron for all select fields

Did a bit of digging - this is cause I'm using the select wrapped within a form element, and tailwindcss has its own innate class style to give that down chevron for all select fields

@joshenlim i'll take a look 👍

@joshenlim i'll take a look 👍

fixed in next release.

fixed in next release.


Release 1.6.7

This PR will release the next patch version 1.6.7.

@spotbugs/core-devs please review this PR, to release new patch version. Thank you!


⚠ Bofrost.nl has degraded performance

In d193381, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 903 ms

Resolved: Bofrost.nl performance has improved in cc6d16d.


fix stop Rich text Editor from crashing on Modal

Description
Changed Rich text Mechanism of onDestroy to fix Rich text Editor on Modal.
Fixes #6035
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
UI verification
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/6035_RTE_in_modal

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
51.9 (0)
33.51 (-0.01)
30 (0)
52.57 (0)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
50.59 (-0.24)
39.41 (-0.84)
36.21 (0)
54.77 (-0.27)

/ok-to-test sha=69a2f85

/ok-to-test sha=75e35c1

@rahulramesha I am able to repro the issue on Firefox. Working fine on chrome and safari.

/ok-to-test sha=d0c4993

@rahulramesha Getting something went wrong on RTE on firefox.

@vivekverma2312 , could you share me that app, it seems to be working fine in the app i was testing.

@rahulramesha Please use below link to debug. Error is observed for the 2nd click in action button.
https://deploy-preview-6077--appsmith-editor-ce.netlify.app/applications/60e44fa66dac1a490b6a50da/pages/60e44fa66dac1a490b6a50dc

/ok-to-test sha=762c4fa

@rahulramesha It's working fine now.

Rerunning all test, Unrelated tests failed

/ok-to-test sha=5c71bc9

/ok-to-test sha=10ad7a8


Adding special price both mobile and desktop version are broken

Version master
Mobile and desktop version  adding special price will break the display
It should be even and the display of each images in mobile version are broken too. What is exactly the size of the product thumbnail?
Adding special price

Thumbnail for multiple images is not responsive

CURRENCY CODE causing this issue. I have issue posted here. In order this to be fix is to fix the currency symbol to display properly not the currency code.

But the multiple thumbnail in the mobile version still a problem. It is not responsive.

The only fix of this is to correct the currency symbol to display properly. Causing the issue is the currency code that being display. Try to change into USD currency it will display properly. I hope they can fix it ASAP

@knif3rdev
the bug is verified and fixed., you may take the pull from the master branch and then check.
Feel free to reopen the issue anytime.


build(deps): update scalafmt-core from 3.4.1 to 3.4.2

Updates org.scalameta:scalafmt-core from 3.4.1 to 3.4.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #47 (7a0e0fe) into main (a9e07cf) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           18        18
  Branches         1         1
=========================================
  Hits            18        18

Continue to review full report at Codecov.

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


bin/brew: Preserve the LC_* localization variables

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Can you explain why this is the case and how it is used?

Can you explain why this is the case and how it is used?

The file brew.sh needs to be executed with the LANG, LANGUAGE, and LC_* environment variables from the user environment, this is currently not the case as seen at https://discourse.brew.sh/t/brew-failing-to-handle-localisation/8234/21

Sorry, of course. I should have given context. The origin of this PR is this discourse discussion https://discourse.brew.sh/t/brew-failing-to-handle-localisation/8234 and this stale issue https://github.com/Linuxbrew/brew/issues/568
Homebrew env filtering filters out the user's locale settings, the LC_* environment variables. This PR preserves these environment variables.

Should LANG and/or LANGUAGE be preserved? See https://superuser.com/questions/392439/lang-and-language-environment-variable-in-debian-based-systems

I've reread that stale issue, and we've already had this same debate/discussion before. See https://github.com/Linuxbrew/brew/issues/568#issuecomment-359166923
@MikeMcQuaid Does your opinion remain the same?
@russel Is your original issue fixed by PR https://github.com/Homebrew/brew/pull/8047, which changes the default locale on Linux to C.UTF-8? If so, I'll close this PR without merging.

@sjackman  Is #8047 now in the current released system? I can only try it if it is unless there is an easy way of trying the merged system. Given the experiments so far, it seems that brew.sh is never going to be called with the user's locale set (unless something akin to this merge request is merged) so the default local is the always locale, not the default locale.

Is #8047 now in the current released system? I can only try it if it is unless there is an easy way of trying the merged system.

I've merged PR https://github.com/Homebrew/brew/pull/8047. You can test it out with HOMEBREW_DEVELOPER=1 brew update.

Given the experiments so far, it seems that brew.sh is never going to be called with the user's locale set (unless something akin to this merge request is merged) so the default local is the always locale, not the default locale.

Correct.

I've merged PR #8047. You can test it out with HOMEBREW_DEVELOPER=1 brew update.

Is this a one way trip, a one-off trip, or a reversible state change trip? If either of the latter two, I'll certainly give it a go.

Is this a one way trip, a one-off trip, or a reversible state change trip? If either of the latter two, I'll certainly give it a go.

It's reversible with cd $(brew --repo) && git reset --hard 2.4.8

I ran this:
|> brew update
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.sh: line 4: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
Already up-to-date.

|> HOMEBREW_DEVELOPER=1 brew update
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.sh: line 4: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Already up-to-date.

506 lynet:~
|> brew update
Already up-to-date.

|> HOMEBREW_DEVELOPER=1 brew update
Already up-to-date.

I checked the Git repo and it had been switched from stable to master. I can switch that back later.

The warning /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) has gone away, so it looks as though your issue is resolved by PR #8047? If so, I'll close this PR without merging.

@sjackman  Your choice, but I think documentation needs to make it clear to users that brew runs in C.UTF-8 no matter what the user's locale is.

Homebrew is not currently localized, so I don't see much benefit to running it in a different locale. Do you have a use case in mind?

Not really. It was just that if the brew command was worrying so much about locale in the script system, and was claiming to use the user's locale, then it should. If it is going to impose C.UTF-8 as the execution environment then that needs saying, and all the locale handling code stripped out so as not to have redundant code.
As it is, I am a happy bunny – no need to install irrelevant locales, and no messages telling me I am a bad person. :-)
Thanks for all your work on this.

With HOMEBREW_NO_ENV_FILTERING=1 Homebrew will use the user's locale if it's UTF-8 and otherwise C.UTF-8 on Linux and en_US.UTF-8 on macOS. Without HOMEBREW_NO_ENV_FILTERING Homebrew will use C.UTF-8 on Linux and en_US.UTF-8 on macOS.

Thanks for all your work on this.

👍


Tracking or Traffic issues  - JupyterCon

There has been a significant drop (year over year) in traffic from jupyter.org to jupytercon.com. Either something is broken or the placement/size of the JupyterCon message on the home page has affected traffic. Flagging this now and we can discuss further when I have details from the O'Reilly marketing team. #276

@Ruv7 we are currently linking to:
https://conferences.oreilly.com/jupyter/jup-ny?cmp=ex-data-confreg-home-jpny18_pj_site
not jupytercon.com.
I don't how how O'Reilly is tracking traffic coming in from us. Was there any update after your Tuesday meeting?

Traffic is down 50% Year over Year (approximately 3,000 clicks instead of 6,000) though it's unclear if that's due to tracking links not being used in the CFP announcement blog post or if it could be placement of the graphic on jupyter.org. As long as we're linking to the proper place there is not much else we can do except move this to a more prominent place asap. We are still investigating if the tracking mechanism is working properly on the back end.


Fundus goes async

This may be one of the biggest updates to Fundus recently.
With this PR Fundus' download logic finally utilizes python's async features. The Crawler respectively the Pipeline gets articles from initialized publishers/scrapers now in an asynchronous batch with size:= len(publishers/scrapers). This benefits Fundus' speed, stability, and readability. As a downside, it is no longer possible to get articles from scrapers directly without using a Pipeline or any of its subclasses.
Since this PR changes a lot of Fundus core logic I addressed some other things as well:

HTML now holds references to both the requested and the responded URL. Closes #230
Adds an optional url_filter parameter to the crawler which excepts a callable to filter out articles both post- and pre-download based on requested/responded URL
Adds an only_unique parameter to the crawler so articles yielded will be unique on the responded URL
The delay parameter now defines the delay time between batches so a publisher is now crawled every max(execution_time, delay_time) seconds. Closes #223
The URLSource's are now requested asynchronously as well. Closes #220
Improved error handling, error logging and fixed several bugs. Closes #209

Closes #222

I botched the merge with main.
I will continue to review this, but @MaxDall you have to fix the merge. The only file I am worried about is the test generation script.

@MaxDall I finished my review. Overall I like these changes, my comments are mostly about style and doc strings. If you research some best practices, I encourage you to share these to ensure consistency across the project.

I actually don't know what to do here. It seems that @Weyaaron broke the branch with b3d849332fe4a872a5c8db66a8b84a89da633ed9. The branch's code isn't up to date, but I can't merge the missing code because the head is already past master. Luckily I have a backup of the branch pre "revert" but then @dobbersc review is lost. @dobbersc do you have any idea on how to fix this?

I actually don't know what to do here. It seems that @Weyaaron broke the branch with b3d8493. The branch's code isn't up to date, but I can't merge the missing code because the head is already past master. Luckily I have a backup of the branch pre "revert" but then @dobbersc review is lost. @dobbersc do you have any idea on how to fix this?

I am deeply sorry for causing this, I did research and then followed the results. The issue with https://github.com/orgs/community/discussions/59809 might be related, I am not quite sure. I attempted to reach the actual GitHub support, but I was unable to locate an actual support address<EMAIL_ADDRESS>has been shut down)
Regarding the possibility that the review will be lost: Maybe we can change the branch this PR is based on without losing the comments? I will look into this.

This branch will now be reset to 70f6ccca487b37879b6f86db83d1d5970b899faa.

As far as I can tell, this one has worked out, congrats @MaxDall

I actually don't know what to do here. It seems that @Weyaaron broke the branch with b3d8493. The branch's code isn't up to date, but I can't merge the missing code because the head is already past master. Luckily I have a backup of the branch pre "revert" but then @dobbersc review is lost. @dobbersc do you have any idea on how to fix this?
Update: 11:54 I will do a hard reset. I will test this with another PR before attempting it here.
Update: 12:02 I tested both git reset --hard HEAD~2 and git push -f on #254 and it seems to work perfectly here. I will now reset and force push this branch.

Thanks for looking into this. Besides the merge conflicts everything looks right now.

@Weyaaron I would suggest moving your open comments to an Issue about general code documentation so this issue can be merged.

@Weyaaron I would suggest moving your open comments to an Issue about general code documentation so I can merge this PR.

For sure, go ahead and merge this one and we'll talk about these later on.


Support Environments API

v6.0 supports environments API. current SDK support version  is v5.1.
Environments API

Team, did you have ideas on what this can be implemented? This feature will power related Terrsform Azure devops environment resource, would be really great to have it.

Team, did you have ideas on what this can be implemented? This feature will power related Terrsform Azure devops environment resource, would be really great to have it.

Hello. This repository looks abandoned, no one seems to looks after tickets in 22 days or even since august 2020.
cc @tedchamb


Add validation for safely deletion of SubNamespace

What
When a SubNamespace is deleted, a related Namespace is deleted by the accurate controller.
However, sometimes the Namespace deletion does not complete, and it remains terminating.
At this time, the owner of the SbuNamespace may not manage the terminating namespace.
The reason why the Namespace cannot be deleted is that some namespaced resources in it cannot be deleted due to the finalizer or any other reasons.
How
Add validation when deleting a SubNamespace.
If there are any namespaced resources left in the related namespace, deny the deletion.
Checklist

[ ] Finish implementation of the issue
[ ] Test all functions
[ ] Have enough logs to trace activities
[ ] Notify developers of necessary actions

It seems that no one is interested in implementing this. Closing.


Atomic finding saving

:warning: Note on feature completeness :warning:
We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
Description
We were working on improve the import scan proccess more fast, reading some foros and Django docs, we found that enclosing a database inserting proccess  inside an atomic transaction will decrease the inserting time, getting a more efficient import scan proccess. We been testing this on our DevSecOps proccess last month and we've been getting better timing results at import scan
Test results
All test passed.
Documentation
Please update any documentation when needed in the documentation folder)
Checklist
This checklist is for your information.

[x] Make sure to rebase your PR against the very latest dev.
[x] Features/Changes should be submitted against the dev.
[x] Bugfixes should be submitted against the bugfix branch.
[x] Give a meaningful name to your PR, as it may end up being used in the release notes.
[x] Your code is flake8 compliant.
[x] Your code is python 3.11 compliant.
[x] If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
[x] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[x] Add applicable tests to the unit tests.
[x] Add the proper label to categorize your PR.

Extra information
Please clear everything below when submitting your pull request, it's here purely for your information.
Moderators: Labels currently accepted for PRs:

Import Scans (for new scanners/importers)
enhancement
performance
feature
bugfix
maintenance (a.k.a chores)
dependencies
New Migration (when the PR introduces a DB migration)
settings_changes (when the PR introduces changes or new settings in settings.dist.py)

Contributors: Git Tips
Rebase on dev branch
If the dev branch has changed since you started working on it, please rebase your work after the current dev.
On your working branch mybranch:
git rebase dev mybranch

In case of conflict:
 git mergetool
 git rebase --continue

When everything's fine on your local branch, force push to your myOrigin remote:
git push myOrigin --force-with-lease

To cancel everything:
git rebase --abort

Squashing commits
git rebase -i origin/dev

Replace pick by fixup on the commits you want squashed out
Replace pick by reword on the first commit if you want to change the commit message
Save the file and quit your editor

Force push to your myOrigin remote:
git push myOrigin --force-with-lease

Thanks for this PR. We've tried transactions in the past and they caused more problems then what they solved.
We're also looking at improving import speed so keep your eye on future PRs in that area.