Migrate API to solclientjs typedef

Is your feature request related to a problem? Please describe.
Since version 10.9.0 "solclientjs" contains TypeScript type definitions for its API. Consequently, @solace-community/angular-solace-message-client does not need to provide the typings anymore.
Describe the solution you'd like
"Angular Solace Message Client" uses typings of solclientjs in its API.
Additional context
<EMAIL_ADDRESS>

During the migration, we encountered the following issues related to solclientjs type definition. We have reported these issues to Solace support and are confident that they will be fixed.
SDTMapContainer#addField is missing
The method should be added as follows: SDTMapContainer#addField(key: string, type: solace.SDTFieldType, value: any): void
Most probably, this method is missing in the current typedef because there exists a deprecated version of it.
Session#subscribe

correlationKey should be changed as follows: correlationKey: object -> correlationKey: object | string | undefined
Typically, a string primitive is used for the correlationKey. In JavaScript, however, primitives are not objects. Also, passing a correlation key is not required, thus should be of the type undefined as well.
requestTimeout should be changed as follows: requestTimeout: number -> requestTimeout?: number | undefined
Passing a request timeout is not required, thus should also be of the type undefined.

Session#unsubscribe

correlationKey should be changed as follows: correlationKey: object -> correlationKey: object | string | undefined
Same rationale as in Session#subscribe
requestTimeout should be changed as follows: requestTimeout: number -> requestTimeout?: number | undefined
Same rationale as in Session#subscribe

Message

Message#setBinaryAttachment should be changed as follows: setBinaryAttachment(value: Uint8Array): void; -> setBinaryAttachment(value: ArrayBufferLike | DataView | string | null | undefined): void;
See anythingToBuffer method in solclient-full.js that solclientjs supports those data types, which is also mentioned in the JSdocs.
Message#getBinaryAttachment should be changed as follows: getBinaryAttachment(): Uint8Array | null -> getBinaryAttachment(): Uint8Array | string | null;
Using the version10 factory profile or older, the binary attachment is returned as a latin1 String; see JSDocs
Message#setCorrelationKey should be changed as follows: setCorrelationKey(value: object): void -> setCorrelationKey(value: string | object | undefined | null): void
Same rationale as in Session#subscribe
Message#setCorrelationId should be changed as follows: setCorrelationId(value: string): void -> setCorrelationId(value: string | undefined | null): void
Same rationale as in Session#subscribe
Message#getDestination should be changed as follows: getDestination(): Destination | null -> getDestination(): Destination
The destination is required. Otherwise, if a project uses strict TypeScript settings, it would have to use the non-null assertion operator (!) to access the destination.
Message#getPriority should be changed as follows: getPriority(): number | null -> getPriority(): number
Priority cannot be null; see initMessage in 'solclient-full.js'

MessageConsumerProperties

MessageConsumerProperties#queueDescriptor should be changed as follows: queueDescriptor: QueueDescriptor -> queueDescriptor: QueueDescriptor | { name?: string; type: solace.QueueType; durable?: boolean }
solclientjs supports passing an object literal with the name as optional field, i.e., not an instance of QueueDescriptor. See line 4301 in solclient-full.js that solclientjs supports that coercion.
For example, when creating a topic endpoint, no queue name is to be specified because set by the broker, e.g.: {type: QueueType.TOPIC_ENDPOINT, durable: false}
MessageConsumerProperties#queueProperties should be changed to optional, as follows: queueProperties: QueueProperties -> queueProperties?: QueueProperties | undefined
From the JSDocs: For durable queues, these must be unset on consumer creation ... values will be populated after the queue is connected

SessionProperties

SessionProperties#publisherProperties should be changed to optional, as follows: publisherProperties: MessagePublisherProperties -> publisherProperties?: MessagePublisherProperties | undefined
solclientjs uses default properties if not set; see line 10508 in solclient-full.js method makeDefaults

MessageConsumer

MessageConsumer#disposed should be changed to boolean, as follows: disposed: void  -> disposed: boolean

solclient-full.js variant leads to runtime error
We noticed that the browser variant 'solclient-full' produces the following runtime error: Uncaught ReferenceError: __nested_webpack_require_1008830__ is not defined. The variant solclient-debug' works fine.
To reproduce:

in tsconfig, overwrite the resolution of solclientjs imports, as follows:{
  "paths": {
    "solclientjs": [
      "./node_modules/solclientjs/lib-browser/solclient-full"
    ]
  }
}

alternatively, you can also change the browser property in package.json of the installed solclientjs NPM module, as follows: "browser": "./lib-browser/solclient.js" -> "browser": "./lib-browser/solclient-full.js"
If reproducing it with Angular, do not forget to delete the Angular cache in the .angular folder.


Initial setup

[x] tailwind config
[x] color scheme
[x] next.ui framework

This issue has been resolved ✅


Setup wiki again

setup the wiki as the old Quadrum wiki on github (+ additional stuff of course)

Working on it. P.S. What do you think of the logo there?


Fixed typos

Please specify parts of this PR update:

[x] Specification
[ ] Schema
[ ] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

Discussion or Issue link:

What this PR does / why we need it:

Special notes for reviewers:
Additional information:

@tsurdilo @cdavernas @antmendoza
Can you guys take a look, please?


Drop dtslint in favor of plain @ts-expect-error

Change-type: patch
Signed-off-by: Thodoris Greasidis<EMAIL_ADDRESS>
Contributor checklist

[x] Includes tests
[x] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci rebase

@balena-ci rebase


New Feature

Can you add the option where the schematic stays loaded on a world, or it always shows where you originally stood to load the schematic?

This was supposed to be solved by session states, but sadly I never got around to finish the feature.


Fix typo Wispher -> Whisper

Closing since author took long time to make changes and I did it for him


feat: Detect changes coming from FCC API responses inside of the classroom mode project

Looking forward for reporting a security issue:
Please report security issues by following our security policy: https://contribute.freecodecamp.org/#/security
Describe the bug
Recently, we came across an issue that seems to have originated from changes on the FCC backend. Our API processing file (/util/api_processor) started creating undefined data inside the allChallenges key inside our CreateDashboardObject function.
The fault came from attempting to access a zeroth index inside of our response object. We did some digging and found that the issue persists despite rolling back changes made to the processing file and files associated with it, leaving us with the assumption that this was caused by changes in the fcc API that we use to build and display classrooms.
To Reproduce
Steps to reproduce the behavior:
This issue will be patched by #401 however, we want to at the very least be more aware of changes happening on FCC's end so that we do not waste time figuring out what caused our code to break.
Expected behavior
We want to set up a job to ping the endpoints used by classroom mode and compare them to what the project is currently expecting. From there, if there is a change detected we want to display what it is and possibly alert the maintainers of the repo (or at the very least set up triggers for associated files) to alert contributors about the changes.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional context
Add any other context about the problem here.

@GuillermoFloresV @ngillux
Related to freeCodeCamp/classroom needing to make corresponding changes via https://github.com/freeCodeCamp/classroom/pull/401
I believe the following changes in freeCodeCamp/freeCodeCamp impacted freeCodeCamp/classroom:

From https://github.com/freeCodeCamp/freeCodeCamp/pull/50769#pullrequestreview-1502560914 by @ojeytonwilliams to @naomi-lgbt on June 28th:

It's not really relevant to this PR, but I wonder if we should switch the meta.json format from
"challengeOrder": [
[
"id": "587d7dbc367417b2b2512bb1",
"title": "Create a Simple JSX Element"
[,
to
"challengeOrder": [
{
"id": "587d7dbc367417b2b2512bb1",
"title": "Create a Simple JSX Element"
},
Working with tuples is nasty and, weirdly, I don't think much code needs to change to accommodate this. What do you reckon?
Anyways, back on topic, some nitpicks:

From https://github.com/freeCodeCamp/freeCodeCamp/pull/50955 by @naomi-lgbt on July 12th:

As mentioned in https://github.com/freeCodeCamp/freeCodeCamp/pull/50769#pullrequestreview-1502560914, this migrates the meta.json files to use objects instead of tuples.

@GuillermoFloresV @ngillux
I want to highlight that a JSON object is unordered by design based on the JSON standard in RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
• When we query the newish FCC API that responds with a JSON object (instead of a tuple), the order isn't guaranteed.
• Item 0 in a JSON object probably won't be the same as array 0 in a tuple, and the ordering in the JSON response can change from one request to the next.
Therefore, when you implement:

We want to set up a job to ping the endpoints used by classroom mode and compare them to what the project is currently expecting. From there, if there is a change detected we want to display what it is and possibly alert the maintainers of the repo (or at the very least set up triggers for associated files) to alert contributors about the changes.

I believe you would need a JSON diff tool that understands semantics and ignores the ordering in the response.
Reference:
From https://datatracker.ietf.org/doc/html/rfc8259.html

An object is an unordered collection of zero or more name/value
pairs, where a name is a string and a value is a string, number,
boolean, null, object, or array.

An array is an ordered sequence of zero or more values.

Thank you!

Sorry about this, I didn't realise that Classroom was relying on the shape of that data. I should have realised given that it changed the schema.
For the short term I'll try and keep that in mind. In the longer term the api-rewrite should handle this issue since any changes to the api will come with a change in the api version.

Actually the challenge data is taken from the client static files.

Right, but we changed that in https://github.com/freeCodeCamp/freeCodeCamp/pull/50955

Yup. I was pointing out this part

For the short term I'll try and keep that in mind. In the longer term the api-rewrite should handle this issue since any changes to the api will come with a change in the api version.

The classroom doesn't use the main API, it gets the challenge data from client static files

Ah, good point.
Just to reiterate, once we have the new API up and running there should no longer be a need to rely on those static files since Classroom will be able to get whatever it needs from (hopefully) stable api endpoints.


DEV: Remove unused code

This code should have been removed as part of b8fe6d2180eb6ea09c16f16d37271a7d41da144a

Thank you @martin-brennan


Support x64 or x86 versions of cscript

Describe the bug
Attempting to test a vbscript file that uses an x86 COM component fails because VS Code tries to use the x64 version instead. Therefore it is unable to locate the COM component.
Code
Set provider = CreateObject("SomeComObjectOnlyDefinedForx86")

To Reproduce
Steps to reproduce the behavior:

Attempt to create a COM object that is only available in x86
Run the debugger and the script fails because it appears CScript is the x64 version, not x86

Expected behavior
Should be able to configure the CScript version to use via the launch.json. Ideally let me select the version of CScript and pass arguments to it in case I need to do more than what the existing launch.json settings allow.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10
VS Code Version: 1.53.1
VBS-VSCode Version 1.2.0

Please use the config variable vbs.interpreter and set the path to c:\Windows\SysWOW64\cscript.exe

Please be more specific or point me to the documentation for this. This option is not valid in launch.json so how would I set this up so I can open a folder in VS code and debug VBS scripts there using x86 version?

Hi please read the VSCode Beginner Documentation how Settings work:
https://code.visualstudio.com/docs/getstarted/settings
Search there for the setting name and config it to your prefered vbs interpreter.
VSCode has settings, which can be configured per Machine, User, Workspace, Language, etc.
Most extensions contributes settings, you can see them, when you click on an extension and on the extension tab "contributions".

Thanks for the info. I'll go this route to get past my issue.
Still I believe that most VBS code assumes x86 and therefore would benefit from either defaulting to that or making it configurable via the debug launch settings so we can run either way without changing the workplace settings.

Couldn't agree. I'm using the default setting Windows is using when you double click an vbs file which is x64.
When you double click your vbs file with the bitness problem you should get same error


Remove chunking from capabilities

Tested with:

http://ocis-latest.owncloud.com/
ownCloud-<IP_ADDRESS>6-daily20200408.pkg
File upload > 10MB

oCIS as of today doesn't support chunking (https://github.com/owncloud/ocis/issues/195), and there's no short term plan for full implementation.
Please stop announcement of chunking capabilities. (see comments https://github.com/owncloud/ocis/issues/194#issuecomment-611448917 & https://github.com/owncloud/ocis/issues/194#issuecomment-611449840)
Calling capabilities
Request:
GET https://ocis-latest.owncloud.com/ocs/v1.php/cloud/capabilities?format=json

Click to expand response
{
    "ocs": {
        "data": {
            "capabilities": {
                "checksums": {
                    "preferredUploadType": "SHA256",
                    "supportedTypes": [
                        "SHA256"
                    ]
                },
                "core": {
                    "pollinterval": 60,
                    "status": {
                        "edition": "community",
                        "installed": true,
                        "maintenance": false,
                        "needsDbUpgrade": false,
                        "productname": "reva",
                        "version": "<IP_ADDRESS>",
                        "versionstring": "10.0.11"
                    },
                    "webdav-root": "remote.php/webdav"
                },
                "dav": {
                    "chunking": "1.0",
                    "chunkingParallelUploadDisabled": false,
                    "reports": [
                        "search-files"
                    ],
                    "trashbin": "1.0"
                },
                "files": {
                    "bigfilechunking": false,
                    "blacklisted_files": [],
                    "privateLinks": false,
                    "undelete": true,
                    "versioning": true
                },
                "files_sharing": {
                    "api_enabled": true,
                    "auto_accept_share": true,
                    "default_permissions": 22,
                    "federation": {
                        "incoming": true,
                        "outgoing": true
                    },
                    "group_sharing": true,
                    "public": {
                        "enabled": true,
                        "expire_date": {
                            "enabled": true
                        },
                        "multiple": true,
                        "password": {
                            "enforced": true,
                            "enforced_for": {
                                "read_only": true,
                                "read_write": true,
                                "upload_only": true
                            }
                        },
                        "send_mail": true,
                        "social_share": true,
                        "supports_upload_only": true,
                        "upload": true
                    },
                    "resharing": true,
                    "search_min_length": 3,
                    "share_with_group_members_only": true,
                    "share_with_membership_groups_only": true,
                    "user": {
                        "send_mail": true
                    },
                    "user_enumeration": {
                        "enabled": true,
                        "group_members_only": true
                    }
                },
                "notifications": {
                    "ocs-endpoints": [
                        "list",
                        "get",
                        "delete"
                    ]
                }
            },
            "version": {
                "edition": "reva",
                "major": 10,
                "micro": 11,
                "minor": 0,
                "string": "10.0.11"
            }
        },
        "meta": {
            "message": "OK",
            "status": "ok",
            "statuscode": 100
        }
    }
}

Workaround
OWNCLOUD_CHUNK_SIZE=0 \
/Applications/owncloud.app/Contents/MacOS/owncloud \
--logfile -

I'd like to have a try at this.
@butonic should the chunking code be removed completely or kept for later ?
if we need to keep it then we should add a config switch, default off, for enabling experimental chunking (since it's broken)

I've grepped through reva code and it seems the chunking can be enabled through the config file.
Proposed change:

[ ] change default config file (in cmd.go) to not set the chunking version: https://github.com/butonic/reva/blob/master/cmd/reva/gen/gen.go#L176
[ ] change capabilities.go to not set chunking version to 1.0 by default: https://github.com/butonic/reva/blob/master/internal/http/services/owncloud/ocs/handlers/cloud/capabilities/capabilities.go#L109
[ ] don't create chunks folder when disabled: https://github.com/butonic/reva/blob/master/internal/http/services/owncloud/ocdav/ocdav.go#L78
[ ] optional: when chunking capability is disabled, also return an error in case the chunk header is sent: https://github.com/butonic/reva/blob/master/internal/http/services/owncloud/ocdav/put.go#L123

as far as I saw there is some chunking v1 code in ocdav in reva, so it does "support" it but I guess it's broken in some way
here's a PR to remove the capability entry in reva: https://github.com/cs3org/reva/pull/678

as far as we saw, chunking v1 (the old one which uses PUT with special file names) is already disabled in ocis-reva as the "bigfilechunking" capability value is set to false
we discovered that the desktop client is not reading that value, raised here: https://github.com/owncloud/client/issues/7849

removed chunking v2 advertising from ocis-reva here: https://github.com/owncloud/ocis-reva/pull/145
I consider this task done from my side.
Next up would be scheduling the client side change.

@PVince81 steps to test-drive this with a client?

best is to wait for the release of ocis-reva which will make the setup easier. (cc @micbar)
setting up basically means following the instructions in the README of the OCIS repo: https://github.com/owncloud/ocis#development

apparently the change in ocis-reva was not enough, also need the change in reva:  https://github.com/cs3org/reva/pull/678


Walrus crashed and restarted because argo workflows failed to install

Describe the bug
Walrus crashed and restarted because argo workflows failed to install.
Steps to reproduce
Deploy Walrus by High Availability Installation: https://seal-io.github.io/docs/deploy/replication
Result
Walrus crashes and restarts:
2023-11-28T10:48:17.710Z        E       workflow        failed to deploy argo workflow: error get release walrus-system:walrus-workflow, error get release walrus-system:walrus-workflow, Kubernetes cluster unreachable: Get "https://<IP_ADDRESS>:443/version": x509: certificate signed by unknown authority
github.com/seal-io/walrus/pkg/server.applyWorkflowDeployment.func1
        github.com/seal-io/walrus/pkg/server/init_workflow_runtime.go:254
github.com/alitto/pond.(*WorkerPool).executeTask
        github.com/alitto/pond@v1.8.3/pond.go:454
github.com/alitto/pond.worker
        github.com/alitto/pond@v1.8.3/worker.go:32

Expected behavior

High availability installation works fine;
A failed argo workflow installation should not affect walrus.

Environment

Walrus version: v0.4.0

Environment

Walrus version: main fc24716b7a80c2db17ff0558b63c83f36db031de
UI version: dev-0b2f2dc

Test Result: pass

root@walrus-kind-control-plane:/# k get all -n walrus-system
NAME                                                                                READY   STATUS      RESTARTS      AGE
pod/database-55fd47f7bc-c6hxb                                                               1/1     Running     0             63m
pod/identity-access-manager-978f95c68-4vcns                                                 1/1     Running     0             63m
pod/test-workflow-490181505738342435-step-secret-490181505738342435-3744763495              0/1     Completed   0             109s
pod/test-workflow-490181505738342435-workflow-step-execution-490181505738342435-989507416   0/2     Completed   0             99s
pod/tf-job-apply-490181421567049763-h8qh5                                                   0/1     Completed   0             2m39s
pod/tf-job-apply-490181525954887714-d4wvt                                                   0/1     Completed   0             97s
pod/walrus-cc57bb88f-ck685                                                                  1/1     Running     1 (62m ago)   63m
pod/walrus-cc57bb88f-nz78z                                                                  1/1     Running     0             63m
pod/walrus-workflow-controller-78b5cb9f5d-f97gq                                             1/1     Running     0             62m

NAME                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/database                  ClusterIP   <IP_ADDRESS>    <none>        5432/TCP   63m
service/identity-access-manager   ClusterIP   <IP_ADDRESS>   <none>        8000/TCP   63m
service/walrus                    ClusterIP   <IP_ADDRESS>   <none>        80/TCP     63m

NAME                                         READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/database                     1/1     1            1           63m
deployment.apps/identity-access-manager      1/1     1            1           63m
deployment.apps/walrus                       2/2     2            2           63m
deployment.apps/walrus-workflow-controller   1/1     1            1           62m

NAME                                                    DESIRED   CURRENT   READY   AGE
replicaset.apps/database-55fd47f7bc                     1         1         1       63m
replicaset.apps/identity-access-manager-978f95c68       1         1         1       63m
replicaset.apps/walrus-cc57bb88f                        2         2         2       63m
replicaset.apps/walrus-workflow-controller-78b5cb9f5d   1         1         1       62m

NAME                                        COMPLETIONS   DURATION   AGE
job.batch/tf-job-apply-490181421567049763   1/1           7s         2m39s
job.batch/tf-job-apply-490181525954887714   1/1           8s         97s


API collection /v1/settings doesn't support filtering

The settings collection on the the api does not respect filtering.
Something like curl://<ip>:<port>/v1/settings?name=db.cattle.database will still return the entire collection.

Closing in favor of rancher/rancher#3847


Support read formatStackTraceAsArray  from configuration

Support read formatStackTraceAsArray  from configuration
What issue does this PR address?
When I Add formatStackTraceAsArray in my configuration file ,this paramater does not take effect.
Like this
    "WriteTo": [
      {
        "Name": "Elasticsearch",
        "Args": {
          "nodeUris": "http://localhost:9200/",
          "typeName": null,
          "formatStackTraceAsArray": true
        }
      }
    ]

So I add paramater to LoggerConfiguration method
Does this PR introduce a breaking change?
No breaking
I add paramater to the end
Please check if the PR fulfills these requirements

[ ] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

Thanks, although added to the back and being optional, does however still makes it breaking. It is not a binary-compatible change as the call site changes. I m a bit hesitant to accept as the method signature is already long, too long IMHO. Is there a way for you to work around it?

It looks like you have a problem with test script
The test is pass but have error in test report stage
The Serilog only support inject paramater in method parameters,can't modify property after constructor.
so when you want to set all properties in a configuration file , must hav a method include all properties of ElasticsearchSinkOptions . It can be an extension method or a constructor ,Add a constructor of ElasticsearchSinkOptions is same as this PR.
I just want to set everything in the configuration file,If that's hard I can continue to set parameters through the program


Allow pass any parameter to pytest

Allow user pass any argument directly to pytest (under the hood).
Example of command:
detect-test-pollution --fuzz --tests tests -m "not qt_test"

use PYTEST_ADDOPTS

Maybe it makes sense to revist this proposal? Yes, you can use PYTEST_ADDOPTS to do this, but this assumes 1) you are aware of this switch 2) command line arguments added by this tool won't override these opts.
When working with the detect-test-pollution tool in the terminal, that is literally my context. Treating it as a blackbox, I type --help and see that it is nowhere possible to pass the additional arguments.
I open the source code, and there is no help either. But I can modify the hardcoded CLI arguments the tool uses, and I end up doing that.
After doing this a few times, I'm thinking about making an MR to add this option, and it turns out there is a closed MR, explaining we should use the cryptic PYTEST_ADDOPTS option.
Adding --runner-options (or similar) argument will also support your vision to support other test runners, not only pytest.
This is also a nice segue to support test collection plugins, like pytest-test-groups (or similar, which use trylast=True). In such case, you want some arguments to be passed only during the collection phase whilst the running phase should only use the previously discovered list of tests. Otherwise you will keep applying the grouping filter to each bisected group, which is wrong.

no thanks


Gmail logo

Describe the requested icon(s)

References

Additional context

following example of the Gmail logo is taken from Boxicons


chore: adding summarizer app

This PR updates the catalog to show the summarizer sample and removes the two models that were in but not actually working

if you want to test it you need https://github.com/redhat-et/locallm/pull/28

Can we update the readme so that is reflects the README from summarizer instead of the one on the root repo

I just copied the part that makes sense.
I omitted the build/run image, ok?


Stop position

I'm always frustrated as I can’t stop the curtains.
Can you add a new position with Up and Down for RTS Somfy curtains ?
Many Thanks un advance

Thank you for your interest and feedback regarding the functionality but I'll have the same answer than the issue #3.


[1.x] ARTEMIS-962 Fix CME when parsing system properties

Add synchronized block against the properties before iterating on them.
JIRA: https://issues.apache.org/jira/browse/ARTEMIS-926

@jmesnil  Can you close this? I pushed a commit for this, saying This closes #969 but it didn't close it.
Can you close it manually please? (only you or apache infra could do it)


ARROW-8231: [Rust] Parse parquet key_value_metadata

The parquet-format FileMetaData struct contains optional key value pairs with additional metadata about the schema.
When the parquet file was generated using the java avro parquet writer, this for example contains the original avro schema under the parquet.avro.schema or avro.schema keys.
Please note that I'm still relatively new to rust, any feedback is appreciated.

It would be nice to run the linter if they exist in here.

Seems I wasn't on the latest master and parts of this are already implemented, will have to rebase.

@jhorstmann running cargo +stable fmt --all should fix all the lint errors in CI


S0205 count limits

Should we remove the limit of 65000 in the counts?

Currently max is unsigned int (about 65.000). Could raise to unsigned long.
Push to 2.0 since it might require changes to implementations.
We should see if other messages has the same kind of limits that should be raised


#625: show rest endpoint for RestErrors

PR details
What is the purpose of this pull request? (put an "X" next to an item)

[x] Technical debt removed

What changes did you make? (Give an overview)

closes #625

blocked by
this PR is waiting for https://github.com/DougMidgley/SFMC-SDK/pull/151 to be published as part of a new SFMC-SDK release @DougMidgley
we then have to bump the required SFMC-SDK version in our package.json here.

result:


Ensuring MatrixConstructor works for Firefox

Currently the MatrixConstructor doesn't really work with Firefox, this fixes the issue.

I signed it!

I signed it!

Thanks for the PR, can you enable the appropriate tests in style/transform_test.js?

Sure thing @concavelenz will do.

I've just removed the returning from the check on GECKO as it doesn't seem to be necessary anymore and they should be all passing AFAIK.

Any news on this?

Looks reasonable to merge, except for the testIs3dSupported change.  Could you please revert that last test change and then squash your commits onto our master?  (you may need to git push -f).

I may be wrong since this went on a long time ago in a galaxy far far away but I that GECKO check is removed so the test can be run against firefox (which was being excluded since it wouldn't work) since the fix is to make it work on Firefox, the test should be run against firefox too. Those are my two cents.

Oh, nah. That test is testing is3dSupported which is false for GECKO < 10. The only reason the tests didn't fail is because we don't run them on older GECKO versions.

Fair enough!

Ping, any updates on this?

Please squash your commits into a single commit, then rebase it on top of master.  You'll need to git push -f to rewrite your fork's history.  Then we can merge.

I tried testing this internally and am getting some errors in Firefox:
ERROR in testScale
An invalid or illegal string was specified
> goog.style.transform.getScale at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform.js:107:18
> setAndAssertScale at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform_test.js:79:17
> testScale at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform_test.js:176:3

ERROR in testScaleZ
An invalid or illegal string was specified
> goog.style.transform.getScale at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform.js:107:18
> setAndAssertScale at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform_test.js:79:17
> testScaleZ at http://vwel10.prod.google.com:17273/google3/javascript/closure/style/transform_test.js:172:3

Closing this as there have been no responses for 2+ years.  Please reopen if you want to continue pursuing it.


{Pipeline} print stacktrace when exception

I met an error in CI checks. I cannot reproduce it in my machine. So I edit pipeline in order to show the detailed error.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/qwordy/azure-cli-extensions.git@alertsmanagement-phase1#subdirectory=src/$EXT&egg=$EXT"

It didnt' trigger the desired job runs on alertsmanagement extension.

It didnt' trigger the desired job runs on alertsmanagement extension.

I am modifying pipeline definition to show the error. It does not aim to trigger the failed doc job.

It didnt' trigger the desired job runs on alertsmanagement extension.

I am modifying pipeline definition to show the error. It does not aim to trigger the failed doc job.

This job verify extension ref should include alertsmanagement like other extensions, but missing:


Disable network SSH tests on windows.

These tests have a high failure rate on Windows, so this disables them for now. I don't know exactly why they are failing. If I had to take a wild guess, I would suspect the use of WinCNG for the SSH backend, which may mean it is out of our control.

@bors r+

:pushpin: Commit ede3bdf2d348cb11cabc56cfe16d14953a61e87f has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit ede3bdf2d348cb11cabc56cfe16d14953a61e87f with merge 274105397f0b905a51bc1b84cdf56fd3a129e844...

:broken_heart: Test failed - checks-actions

@bors retry

:hourglass: Testing commit ede3bdf2d348cb11cabc56cfe16d14953a61e87f with merge b8e63ec6f178194f64a8fe225943600f03461f8b...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing b8e63ec6f178194f64a8fe225943600f03461f8b to master...


Implement Autocomplete

Pull Request Etiquette

[X] I have checked the PRs for upcoming features/bug fixes.
[X] I have read the contributing guidelines.

Changes

[X] Internal code
[X] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
This introduces Discord's upcoming autocomplete feature for Slash Commands. This also features a refactor of the interaction hierarchy to accommodate for the new interaction type.
Using the Interaction
OptionData can now have autocomplete enabled with option.setAutoComplete(true). This can only be enabled on options with types, Integer, Number, or String. Once autocomplete is enabled for an option, you may not add choices (It will not enable if choices are already present on the option).
To respond with choices, you can use the following:
@Override
public void onCommandAutoComplete(@NotNull CommandAutoCompleteEvent event)
{
    event.respondChoices(
            new Command.Choice("choice-1", "one"),
            new Command.Choice("choice-2", "two"),
            new Command.Choice("choice-3", "three")
    ).queue();
}

You can also get the option the user is currently focused on with event.getFocusedOption()
Discussion Points

This implementation adds the focused value to OptionMapping, which I'm not sure should be present there or elsewhere
InteractionHook was split into InteractionHook and ChannelInteractionHook. However ChannelInteractionHook cannot extend InteractionHook
InteractionCallbackAction and ChannelInteractionCallbackAction are kind of janky because of the former
CommandAutoCompleteInteraction and CommandInteraction share a large amount of identical code

Is this ever going to be implemented?

@AfonsoHackers yes.

The question is when I suppose?

Superseded by #1971


Tools for integration testing

(This might end up in cartographer_ros.)
We need tools for doing integration testing: given some data, confirming that Cartographer's behavior doesn't change over time.
This is intended as a tracking issue for work TRI's planning to do on this.
@damonkohler @SirVer @wohe once upon a time, there was code for doing trajectory comparisons. Could that be made available?
@yutakaoka for TRI.

I just fixed #310. The idea is to use this generated ground truth data as input to compute_relations_metric_main, i.e.

Extract the computation of errors into a separate file.
Add support for reading a GroundTruth proto in addition to a text file with unix timestamps.
Use it for an integration test.

@cschuet Is this done with the nighly pipeline running?

With the inclusion of ground_truth data in the nightly pipeline I call this done.


cleanup copilot test

split edge and sidecar envoy tests
there was an error if kubernetes api ran at the same time because of conflicting
service ports
this refactor enables a dedicated service port for edge and sidecar envoys

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: nhsieh
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: sebastienvas
Assign the PR to them by writing /assign @sebastienvas in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @nhsieh. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@nhsieh: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
a1d3b34b92f2ed9bc2e289b87d74510480e62935
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-dashboard

@nhsieh: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
a1d3b34b92f2ed9bc2e289b87d74510480e62935
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


cuda9.1 can not support tensorflow

import tensorflow as tf
Traceback (most recent call last):
File "C:\Program Files\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Program Files\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Program Files\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Program Files\Python36\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Program Files\Python36\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.

I resolved it by the flowing  link

https://github.com/tensorflow/tensorflow/issues/26870
https://blog.csdn.net/qq_36556893/article/details/79433298

@dorothy9297 Good to know the issue is resolved. Will close the issue. Thanks!


Computation of l1 loss

According to the paper, smooth l1 loss is calculated only in cases where there is label of 1 (ie foreground object). However, looking at the code, I saw only a check for label != -1 and then loss is computed directly here.
Can you please tell me where this check is done or if there is some mistake in my understanding of the paper.

As you can see here different between prediction and ground truth multiply by bbox_inside_weights.
This weights was created in Anchor target layer here, all weight =0 at start.
After that, we apply weights =1 only for labels==1.

@loolzaaa thank you so much for the explanation


After  changing the gcc version

When I install gcc 4.9，the old issue was solved, but I meet a new problem following:
gpu2@gpu2-PowerEdge-R730:~/OWFO/TF_Deformable_Net$ python ./faster_rcnn/demo.py --model tf_deformable_net/restore_output/Resnet50_iter_145000.ckpt
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.so.8.0 locally
filename: /home/gpu2/OWFO/TF_Deformable_Net/lib/psroi_pooling_layer/psroi_pooling.so

/home/gpu2/OWFO/TF_Deformable_Net/lib/psroi_pooling_layer/psroi_pooling.so
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE3 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.
  Traceback (most recent call last):
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1022, in _do_call
return fn(*args)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1000, in _run_fn
self._extend_graph()
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1049, in _extend_graph
self._session, graph_def.SerializeToString(), status)
File "/home/gpu2/anaconda3/lib/python3.6/contextlib.py", line 89, in exit
next(self.gen)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/errors_impl.py", line 469, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: No OpKernel was registered to support Op 'DeformConvOp' with these attrs.  Registered devices: [CPU], Registered kernels:
device='GPU'; T in [DT_DOUBLE]
device='GPU'; T in [DT_FLOAT]
 [[Node: res5a_branch2b/DeformConvOp = DeformConvOp[T=DT_FLOAT, data_format="NCHW", deformable_group=4, num_groups=1, padding="SAME", rates=[1, 1, 2, 2], strides=[1, 1, 1, 1]](transpose, res5a_branch2b/weights/read, transpose_1)]]

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./faster_rcnn/demo.py", line 136, in
saver.restore(sess,ckpt)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1439, in restore
{self.saver_def.filename_tensor_name: save_path})
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 767, in run
run_metadata_ptr)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 965, in _run
feed_dict_string, options, run_metadata)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1015, in _do_run
target_list, options, run_metadata)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1035, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: No OpKernel was registered to support Op 'DeformConvOp' with these attrs.  Registered devices: [CPU], Registered kernels:
device='GPU'; T in [DT_DOUBLE]
device='GPU'; T in [DT_FLOAT]
 [[Node: res5a_branch2b/DeformConvOp = DeformConvOp[T=DT_FLOAT, data_format="NCHW", deformable_group=4, num_groups=1, padding="SAME", rates=[1, 1, 2, 2], strides=[1, 1, 1, 1]](transpose, res5a_branch2b/weights/read, transpose_1)]]

Caused by op 'res5a_branch2b/DeformConvOp', defined at:
File "./faster_rcnn/demo.py", line 126, in
net = get_network(args.demo_net)
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/factory.py", line 36, in get_network
return Resnet50_test()
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/Resnet50_test.py", line 21, in init
self.setup()
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/Resnet50_test.py", line 221, in setup
.deform_conv(3, 3, 512, 1, 1, biased=False, rate=2, relu=False, num_deform_group=4, name='res5a_branch2b')
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/network.py", line 41, in layer_decorated
layer_output = op(self, layer_input, *args, **kwargs)
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/network.py", line 192, in deform_conv
dconv = trans2NHWC(dconvolve(data, kernel, offset))
File "/home/gpu2/OWFO/TF_Deformable_Net/lib/networks/network.py", line 182, in
i, k, o, strides = [1, 1, s_h, s_w], rates=[1, 1, rate, rate], padding=padding, num_groups=num_groups, deformable_group=num_deform_group)
File "", line 45, in deform_conv_op
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 763, in apply_op
op_def=op_def)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 2395, in create_op
original_op=self._default_original_op, op_def=op_def)
File "/home/gpu2/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1264, in init
self._traceback = _extract_stack()
InvalidArgumentError (see above for traceback): No OpKernel was registered to support Op 'DeformConvOp' with these attrs.  Registered devices: [CPU], Registered kernels:
device='GPU'; T in [DT_DOUBLE]
device='GPU'; T in [DT_FLOAT]
 [[Node: res5a_branch2b/DeformConvOp = DeformConvOp[T=DT_FLOAT, data_format="NCHW", deformable_group=4, num_groups=1, padding="SAME", rates=[1, 1, 2, 2], strides=[1, 1, 1, 1]](transpose, res5a_branch2b/weights/read, transpose_1)]]

It seems  cuda has error , Do you have some advices?

It seems your GPU driver is not properly installed, do you have normal nvidia-smi output? Can you run other operation in gpu by manually set the device to GPU? Did you set CUDA_VISIBLE_DEVICES  to some other value?
Personally I don't think it's related to my code, what do you think?

Me too, now ,the output of  nvidia-smi are "nvidia: command not found"    I am wondering if  I need to reinstall cuda , I guess it was the change of gcc leads to the  cuda failure

@feitiandemiaomi  have you fixed the problem？ i also met the problem.

@Zealoe Do you also encounter this issue after the reinstal of gcc? I am afraid that the GPU cuda stuff is based on the original gcc. You might want to install the original version gcc or reinstall cuda in current setting.


Traces and Profiles missing extraConfig block

Add support for traces and profiles extraConfig block.

Good to see you are working on this! Is it possible to Cherry pick the fix and merge this already? Currently we are working around this "bug" by patching the configmap after deployment. It would be great if we can leverage your fix without having to patch our helm chart locally.

Currently we have:
extraConfig: ... # Adds config to the "alloy" instance
logs:
  extraConfig: ... # Adds config to the "alloy-logs" instance
  cluster_events:
    extraConfig: ... # Adds config to the "alloy-events" instance
  journal:
    extraConfig: ... # Not used anywhere currently

We could add:
profiles:
  extraConfig: ... # Adds config to the "alloy-profiles" instance

Trace receivers exist on the alloy instance, so the top-level extraConfig should be sufficient.

So, a few options:

Smallest change:
Add exttraConfig for profiles, the only place that is missing the ability:

profiles:
  extraConfig: ... # Adds config to the "alloy-profiles" instance

More logical sense, but breaking:
Deprecate the existing extraConfigs and instead put them inside the alloy instances. to make it clearer where they're being deployed:

alloy:
  extraConfig: ...
alloy-events:
  extraConfig: ...
alloy-logs:
  extraConfig: ...
alloy-profiles:
  extraConfig: ...

My thoughts as a user:
Both options would work for me but option 2 seems more logical. Maybe overthinking but since the alloy block seems to already deal with configs
alloy:
  alloy:
    extraConfig: ...
alloy-events:
  alloy:
    extraConfig: ...
alloy-logs:
  alloy:
    extraConfig: ...
alloy-profiles:
  alloy:
    extraConfig: ...

Afterburner: is there a reason alloy is named alloy-metrics?

Let me chat with some folks internally and we'll make a plan.

Afterburner: is there a reason alloy isn't named alloy-metrics?
Because the "main" alloy instance scrapes metrics, but also opens the receivers, which then can pick up traces, as well as metrics and logs pushed via OTLP, OTLP HTTP, Zipkin, Jaeger, etc... It mostly does metrics, but it can do much more than just metrics.

I assume it's easiest and least intrusive to just merge adding the extraConfig block to profiles:. If this can be merged soonish it would help us. We're in the process of implementing Continuous Profiling and I can't really move to forward to production with needing a workaround (patching ConfigMap after Helm run).

I now see that you merged another way to configure Profiles. I've got my usecase to work with the helm values below. Please disregard my comment above, thank you!
profiles:
  enabled: true
  java:
    enabled: true
    namespaces: [${PYRONS}]
    extraRelabelingRules: |-
      rule {
        source_labels = ["__meta_kubernetes_pod_annotation_profiling_disabled"]
        regex = "(true)"
        action = "drop"
      }
    profilingConfig: {"alloc":"512k","cpu":true,"interval":"30s","lock":"","sampleRate":97}
  ebpf:
    enabled: false


test: Tests for colorPreference and getUserPRVelocity

What type of PR is this? (check all applicable)

[ ]  🍕 Feature
[ ]  🐛 Bug Fix
[ ]  📝 Documentation Update
[ ]  🎨 Style
[ ]  🧑💻 Code Refactor
[ ]  🔥 Performance Improvements
[x]  ✅ Test
[ ]  🤖 Build
[ ]  🔁 CI
[ ]  📦 Chore (Release)
[ ]  ⏩ Revert

Description
This PR is related to Write tests for utility functions #188 and adds tests for the following files:

src/utils/colorPreference.ts
src/utils/getUserPRVelocity.ts

In order to work with window object, modifications were made to the Vite config, setting the environment to 'jsdom',
No other files or tests were changed or affected.
Related Tickets & Documents
[#188]
Mobile & Desktop Screenshots/Recordings

Added tests?

[x]  👍 yes
[ ]  🙅 no, because they aren't needed
[ ]  🙋 no, because I need help

Added to documentation?

[ ]  📜 README.md
[ ]  📓 docs.opensauced.pizza
[ ]  🍕 dev.to/opensauced
[ ]  📕 storybook
[x]  🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

The failing test is passing in my local dev environment.

The failing test is passing in my local dev environment.

Same with me.
@diivi can you try running the tests on your machine?

Weird 😕, can you try changing the test just a bit so the value changes to something else? It passes for me too.

Sure, will revert back

This could be due to the varying timezone of the test runner. The new Date() constructor uses the local timezone by default.
https://github.com/TheLazron/ai/blob/2296205cede6ecd77c1dfb4b6356f42d1e9f5ca8/src/utils/getUserPRVelocity.ts#L8-L13

This could be due to the varying timezone of the test runner. The new Date() constructor uses the local timezone by default. https://github.com/TheLazron/ai/blob/2296205cede6ecd77c1dfb4b6356f42d1e9f5ca8/src/utils/getUserPRVelocity.ts#L8-L13

So should I try changing the time in the tests?

So should I try changing the time in the tests?
Can you try using Math.floorhere?
https://github.com/TheLazron/ai/blob/2296205cede6ecd77c1dfb4b6356f42d1e9f5ca8/src/utils/getUserPRVelocity.ts#L13

Why did changing it to Math.floor work?


Fixed spelling error in line 266

SharePont = SharePoint
Closes #1456

@cabailey - PR is ready for final review based on issue #1456. This is just a simple typo issue.
Thank you.
cc: @kenwith

#sign-off


Doesn't work with files from bundle

I added a file "flac" to the xcode project. I can play this file when It is stored anywhere else (for example in documents folder) but not from the app bundle

Any news about APE? Maybe anybody to face a iOS library to decoding that format?

Technically playing from the app bundle shouldn't be much different from any other path. I would suggest checking url format.

NSString *temp = [[NSBundle mainBundle]<EMAIL_ADDRESS>ofType:@""];
temp = [@"file:/" stringByAppendingString:temp];
temp = [temp stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding];
Result path:
file://Users/gerchicov/Library/Developer/CoreSimulator/Devices/95F3F481-63DC-4DCE-8571-7D8EAF833011/data/Applications/BD6BB55C-2A53-48E0-8AB3-3D684EC9076D/ORGMEngine%20Example.app/Fergalicious.flac
This file exists at the specified path but works when it is placed outside bundle only


create cyclops-paguro module

Paguro is a port of the core Clojure collections api. A PVectorX implementation backed by Paguro would be faster than one backed by pCollections ( BitmappedVectorTrie cf IntTreeMap)

Should build on cyclops-reactor to get Lazy collection support.


Updating canopy cover source code tag we pull from - no review

Updating tag Canopy Cover pulls source from
Will be Alpha_1_4 when merged

Codecov Report

Merging #31 (dc6ed84) into develop (6e49e0e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #31   +/-   ##
========================================
  Coverage    93.27%   93.27%
========================================
  Files            4        4
  Lines          238      238
========================================
  Hits           222      222
  Misses          16       16

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 6e49e0e...dc6ed84. Read the comment docs.


RESERVED_FUNCTION_POINTERS error [duplicate]

We're using QR scanning in long running app, starting and stopping scanning every now and then. For some reason from time to time we're getting following error:
Failed to read QR code. Finished up all reserved function pointers. Use a higher value for RESERVED_FUNCTION_POINTERS.
This seems to be related to emscripten documentation here https://kripken.github.io/emscripten-site/docs/porting/connecting_cpp_and_javascript/Interacting-with-code.html#calling-javascript-functions-as-function-pointers-from-c

#74


Captcha on login?

This is what I get trying to authenticate with Ice. How can this be fixed?

Seems like it's something related to #29 . Ice worked a day ago, maybe bot guard was enabled. Investigating right now.

Please try to use cookie authentication untill login/password will work. If you don't know how, send me your browser and operating system versions and i'll tell you how.

Or just try again after logging in through incognito mode of your browser, google should end their suspicions. Sorry for inconvenience.

It worked once and I had the same issue as described in #29 - Sign In button screenshot. Then it started to show captcha, I tried to log in with browser, clicked "Yes, it was me" on Google's "Suspicious login prevented" bud captcha kept going.
How do I use cookie authentication? I'm running Safari/Chome on OS X 10.11

To use cookies:

Open console in the folder with ice, run ./ingress-ice -r
Log in to ingress in your Chrome
Press the

sign
Press "Show cookies" or something like this
Open the www.ingress.com submenu (
)
Open Cookie files
Click on

Copy it's contents (something like
)
Return to your console, insert the area link and choose yes in the next dialog
Paste (usually Shift + Insert, don't know, how on Mac) your SACSID
In browser, click

Again, copy it's contents and paste into the next dialog
Next steps as usual

Again, sorry for inconvenience.

Thanks, I'll try. Another question here however is the whole point why I started using Ice. I used basic Phantom screenshotter that had a cookie authentication. The problems I ran into were (a) cookies expiring and resulting in "Sign In screen" which needed manual cookie update and (b) - short time after screenshotting Intel started to throw a white screen with "Sorry, but your computer and network appears to be sending automated requests". Won't this happen with Ice if using cookie authentication?

The first is inevitable, cookies tend to stale, but the second shouldn't happen — ice acts as a usual browser without reloading ingress.com. It only clicks when Human presence not detected text appears.

And this is what I get now when trying password authentication on IP where Ice is running. From my home computer this account logs in lust fine

Hmm... Did you get banned for using ice or it happened before? I think there is no way other than to wait to be able to log in successfully. By the way, I've been using ice for 20 days without breaks and it was fine — no any suspicions from Google.

I guess I just made Google suspicious with old version of Ice trying to get through their new login form. I'll keep you posted if something will go wrong with this account

Ask me if you need help :)


Skype deb package <IP_ADDRESS> can't be downloaded (404)

Describe the bug
building '/nix/store/63nkkxr95y7kghxhihswljwi95qmp5b0-skypeforlinux_<IP_ADDRESS>_amd64.deb.drv'...

trying https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_<IP_ADDRESS>_amd64.deb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found

https://repo.skype.com/deb/pool/main/s/skypeforlinux/ doesn't contains skypeforlinux_<IP_ADDRESS>_amd64.deb.
To Reproduce
Steps to reproduce the behavior:

Switch to nixos-20.03 channel.
Add skypeforlinux into environment.systemPackages
Run sudo nixos-rebuild switch

Expected behavior
Skype installed.
Metadata
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
/nix/store/0rbnlnd1pvlpii8p72ybvvg672j2wc2f-bash-interactive-4.4-p23-dev
copying path '/nix/store/0rbnlnd1pvlpii8p72ybvvg672j2wc2f-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...

system: "x86_64-linux"
host os: Linux 5.4.33, NixOS, 20.03.1422.1e90c46c2d9 (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.4
channels(nick): ""
channels(root): "nixos-20.03.1422.1e90c46c2d9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I don't know if you absolutely need the dropbox client but you could consider maestral as an alternative until this is fixed.

@peterhoeg, DropBox? This issue is about Skype. What do you mean?

Sorry, brain fart here.
On Thu, 23 Apr 2020, 22:29 Nick Korsakov<EMAIL_ADDRESS>wrote:

@peterhoeg https://github.com/peterhoeg, DropBox? This issue is about
Skype. What do you mean?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/85724#issuecomment-618427373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFQM5T2HMJTBU6B7ZGPKPDROBGEBANCNFSM4MNUUIWQ
.

Is sthis still an issue after https://github.com/NixOS/nixpkgs/pull/86354?

Fixed.


fmt: inconsistency in 0 padded formatting of Inf and Nan float values

For e.g. "%020f" Inf is not 0 padded but NaN is.
00000000000000000NaN
                +Inf
                -Inf

https://play.golang.org/p/qiO-mme4S6

There is no test case for 0 padded NaN (but for Inf) and it seems this behavior has existed throughout Go 1.x .
C does not 0 pad NaN and Infs which seemed the reason the Infs are treated special in Go too.

This might not be changed anymore due to the Go 1 guarantees but the API documentation does not seem to explicitly mention the treatment for NaN or Inf either.

Not sure if it should just be document or if this should be fixed for 1.7
If ok i can submit a patch that just adds a test case for current Go behavior with a comment that references this issue or make the treatment of NaN consistent with Inf.

It's just saying, "Oooooh, a Nan!".
Might be a consequence of https://go-review.googlesource.com/19721 or might be old. Should be easy to fix regardless.

The NaN issue has existed since Go 1.0. But
the Inf case has changed a little bit:
go version go1
00000000000000000NaN
0000000000000000+Inf
0000000000000000-Inf
go version go1.1.2 linux/amd64
00000000000000000NaN
0000000000000000+Inf
0000000000000000-Inf
go version go1.2.1 linux/amd64
00000000000000000NaN
+0000000000000000Inf
-0000000000000000Inf
go version go1.2.2 linux/amd64
00000000000000000NaN
+0000000000000000Inf
-0000000000000000Inf
go version go1.3 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.3.3 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.4 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.4.1 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.4.3 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.5 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.5.3 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version go1.6 linux/amd64
00000000000000000NaN
+Inf
-Inf
go version devel +e6d6ad4 Sat Feb 20 20:16:27 2016 +0000 linux/amd64
00000000000000000NaN
+Inf
-Inf
so Go 1.3 fixes the Inf problem, but the NaN problem persists.

Writing the patch that rob mentioned made me aware of the NaN case.
I write a patch to fix the NaN case now.
Just wanted to make sure its ok to correct and does not break any Go 1.x guarantees. But since Inf only changed in 1.3 i guess its ok to make them consistent.


Update aspire-manifests for playground projects.

They required an update ....
Microsoft Reviewers: Open in CodeFlow

/azp run


fix: Update overcommit ratio during live VM migration

Description
During live migration of a VM from between hosts having different cgroup versions (cgroupv2 & cgroup), overcommit ratio is ignored.
This PR fixes the above issue.

Steps to reproduce

Set overcommit ratio to 2 for the cluster
Launch a VM
Check value of shares on the host

$ virsh dumpxml --domain i-2-9-VM | grep shares
    <shares>500</shares>

Live migrate the VM to another host which has a different cgroup than the existing host of the VM.
Live migrate the VM back to the original host. And check the shares again.

$ virsh dumpxml --domain i-2-9-VM | grep shares
    <shares>1000</shares>

Stopping and starting the VM on the same host will reset the value back to 500.
This happens only when cgroup is different on the destination hosts during live migration. Possibly introduced in #8252 .

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Not able to reproduce the issue after the patch.

How did you try to break this feature and the system with this change?

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9797

@blueorangutan package

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9807

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-10383)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 44522 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9178-t10383-kvm-centos7.zip
Smoke tests completed. 101 look OK, 9 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

ContextSuite context=TestAnnotations>:setup
Error
0.00
test_annotations.py

test_query_async_job_result
Error
0.00
test_async_job.py

ContextSuite context=TestNetworkACL>:setup
Error
0.00
test_network_acl.py

test_nic_secondaryip_add_remove
Failure
0.07
test_multipleips_per_nic.py

ContextSuite context=TestNestedVirtualization>:setup
Error
0.00
test_nested_virtualization.py

test_01_verify_ipv6_network
Failure
1.66
test_network_ipv6.py

test_08_migrate_vm
Error
43.85
test_vm_life_cycle.py

test_02_cancel_host_maintenace_with_migration_jobs
Error
199.94
test_host_maintenance.py

test_hostha_kvm_host_fencing
Error
109.36
test_hostha_kvm.py

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10041

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-10538)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 46625 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9178-t10538-kvm-centos7.zip
Smoke tests completed. 108 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_cancel_host_maintenace_with_migration_jobs
Error
191.96
test_host_maintenance.py

test_hostha_kvm_host_fencing
Error
185.02
test_hostha_kvm.py

Merging this based on reviews, smoketests and manual QA.


"Segmentation fault" Error using StringTie

Hi, I am trying to assemble RNA-seq data for gene annotation using StringTie. But the program fails returned the "Segmentation fault" error.  The program stop at the Chr1:17731527-19123574 site as followings:
[03/24 01:33:51]>bundle Chr1:17731527-19123574 [18873741 alignments (1578956 distinct), 6571 junctions, 0 guides] begins processing...

The alignment bam file is a merge type with long and short RNA-seq data. The StringTie (latest version: v2.2.1)  command is the following:
stringtie {input.merge_rnaseq_bam} --mix -j 3 -c 3 -o {output.merge_rnaseq_gtf}

I have tried to get the stop bundle file using only one thread with -p 1 following the instructions here Extracting bundle data for debugging. This is the bam file I extracted from the stop site:
samtools view -b merge_rnaseq.bam Chr1:17731527-19123574 > bundle_c1.bam

The extracted bundle_c1.bam file is about 900Mb and shared in dropbox: https://www.dropbox.com/s/efl4wnpdsokz4uj/bundle_c1.bam?dl=0
I wish the problem to be solved quickly.

I slove the problem by splitting the merge_rnaseq.bam file into long.bam file and short.bam file and it succeed.


Image preview on timeline

Consider allowing option to show images on timeline without having to tap on the tweet

I already consider this, but the preview needs a lot of space. If preview are displayed in timeline, I can only read a small amounts of tweets. So, I agree to implement it as an option.


Update libexecdir of Layout GNU from config.layout

The original hard-coded Layout GNU has libexecdir that should better be ${exec_prefix}/libexec+ instead of ${exec_prefix}/libexec.
From the GNU Coding Standards: "The definition of ‘libexecdir’ is the same for all packages, so you should install your data in a subdirectory thereof."(https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
This is also an issue for the correct performing of traffic_layout runroot.

[approve ci]

[approve ci autest]

Cherry-picked to 8.0.x


How can i highlight epub content text using "rangy" in "readium-shared-js" ?

How can i highlight epub content text using "rangy" in "readium-shared-js" ? I can't highlight the text in iframe,but outside the iframe,i can do it . so anyone help me?

Please ignore the Rangy lib. Have a look at plugins/highlights instead:
https://github.com/readium/readium-shared-js/tree/develop/plugins/highlights
This uses a totally different text "selection" method (i.e. translucent div overlays) and this is an active feature in the cloud reader build, which you can try here: https://readium.firebaseapp.com/?epub=epub_content%2Faccessible_epub_3 (for example)


Border and Font Size Options for Code Blocks

Option to add border to code blocks and the ability to change the font size of code blocks
The current font size of code blocks is a bit to small having the ability to customize the size would be great

+1
This is probably not the most healthy way to make this change, but I was able to change the font size of code blocks by modifying the "0.85" number in the following passage within the extremely long line 39 of my_vault_directory/.obsidian/themes/minimal.css
.HyperMD-codeblock,.cm-s-obsidian span.cm-inline-code,.markdown-preview-view code,.markdown-preview-view pre,.markdown-source-view.mod-cm6 .cm-preview-code-block pre.dataview-error{color:var(--text-code);font-size:0.85em}
For example, modifying 0.85em to 1.0em makes them the same size as the regular body font.

Thanks for your suggestion @alicangok
Will you this for the time being and hope that @kepano adds this as a customizable option

Will you this

Will I what? :) If you mean forking or something, I'm not really an expert, so I would rather stay away from it. I just opened the mentioned .css file in my PC using a simple text editor and made the change there. I'm sure my local change will be gone when the plugin is updated on my Obsidian client.

Added in Minimal 5.0


Changing Fission's reference to InfraCloud

InfraCloud is maintaining the Fission project and Platform9 is not active anymore. Project maintainers would like update the reference in landscape to reflect that.
Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

TIL thank you!


Solr option does not dispose of ContentSearch.dll, preventing site deletion

If you try to delete a site in the same session that you've created it, you will receive the following error:

This is most likey because the GenerateSchema method does not dispose of the SchemaGenerator object. https://github.com/dsolovay/Sitecore-Instance-Manager/blob/515d946754ce32bb6b225d4c920c0152e3cbced8/src/SIM.Pipelines/Install/Modules/CreateSolrCores.cs#L162

I could suggest to read assembly bytes to memory stream and then load assembly from memory stream. @dsolovay what do you think?

I'm going to try to resolve with Application Domains (see http://stackoverflow.com/a/28633417/402949) first.

Cannot access SchemaGenerator class accross AppDomain because it is not serializable:

Using this for loading assembly from memory: http://stackoverflow.com/a/20080196/402949

Initial fix working, but needs to be refactored to follow Util class patterns. See cca62caddf2582572f843ce70afbf446d455f244

Pull request opened, so closing this issue.


Add configure options: --with-hdf5 --with-hdf4 and --with-pnetcdf

This is to support #1391

I am not sure I want to revisit this. This a bit like the fortran separation
and people asking us to undo it.
We went to some effort to do this split and I do not see enough complaints
about  this to warrant the change. Still, we can continue to talk about this
and leave the PR open for now.

Just for the reference. The commit that removed --with-hdf5 etc. is:
https://github.com/Unidata/netcdf-c/commit/29e86197879ac28431f4ebacfd17d40a8a57803d#diff-67e997bcfdac55191033d57a16d1408a
It was committed by @edhartnett in 2011 with log message "simplified build system".
This PR is just for connivence. I cannot think of any harm it may cause.

Do we also need to add --with-curl, --with-szip, etc?

I believe HDF5 is doing this for every external library.

Personally I am not a huge fan of this approach, although I originally introduced these for netcdf (also based on the HDF5 example), then later removed them.
If you read the AC_ARG_WITH documentation (https://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/External-Software.html) you will see that this usage is not mentioned. As the autoconf manual describes this macro, it is to be used for external libraries that may be optional in your build. The example they give is the readline library. A --without-readline may cause a package that optionally uses the readline library to not use it, even if it is present on the system.
In this way, we could use --without-hdf5/--with-hdf5 to turn off and on support for HDF5.
But the autotools docs mention there may be cases where AC_ARG_ENABLE is used to handle this case instead (as we have done). So far, so good.
Nowhere does the documentation mention using the --with-* option to specify the location of the library. This is already well-handled by the standard CPPFLAGS, LDFLAGS, etc.
The HDF5 team use it this way, but is that necessary or correct?

I wish you had documented the reasoning when you made the change
all those years ago. Oh well.

Well if I had documented every decision I would have left you with 1000 volumes of detail you could never read. ;-)

Sure we would! But only when we needed it :-)

My suggested option does not affect the results of --without-package.
If it is used, autoconf will set variable with_package to no.
if --with-package is used without argument, then variable with_package is set to yes.
This PR is for convenience, and it does not breaking existing practical usage of autoconf.
In addition to HDF5, bot MPICH and OpenMPI use it.

Next question: should we advertise this option, or deprecate it to try to
force users to use the existing LDFLAGS, etc.

Maybe we can mention this option to the netcdf community to see if it is welcomed.
If someone pointed out it can cause harm, then we can abandon it.

I recommend that this PR be closed and not merged.
This usage of --with-hdf5 here is not in accordance with the automake documentation.
Furthermore, as noted by @DennisHeimbigner, this would imply that we should do the same for all the other libraries we use, and I don't think we want to do that. We would be adding many lines of code to our configure.ac file, for a non-standard way of setting library locations, which we can already do in a standard way. (Also we would be increasing our test burden, since we would have to test these options.)
Although there are some packages that use the --with options this way (ex. HDF5) I believe they are incorrect. And there are many many more packages that to NOT use the --with options in this way.
The documentation is clear, this is not how the --with option is intended to be used. LDFLAGS and CPPFLAGS already handle this functionality in a very well-understood and standard way.
I apologize to @wkliao and all the netCDF team for not better documenting the decision to remove these from netcdf-c configure.ac. But I believe it was the correct decision, and these should not be put back in.
I would also like to add that I very much value your contributions and efforts @wkliao , both with pnetcdf and netcdf-c. Please understand that, although I don't think this PR should be merged, I believe that you bring great value to the scientific data world with your many contributions. ;-)


Updated Search page UI

Fixes Issue
closes #3849
Changes proposed
Added filtering option with tags on Search page as well. Users can select and deselect tags to get the desired results based on the combination chosen. For example: if I select tags open source and DevOps then only those users that have both of these tags will be shown. You can click on the tag again to remove the selection. You can also manually type out in the search bar to get the results otherwise use tags directly. When the user selects a tag from the discover page or their LinkFree profile, it will redirect them to the search page showing the results along with the highlighted tag.

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Working on the build fail

@Ananya2001-an did you mean to close the pull request?

@eddiejaoude I didn't mean to close it. But since I clicked on update main branch accidentally it discarded those changes. But I have the new PR open at #4030. And I am making all my commits to it right now.

Ok thank you 👍


chore: update the roadmap

Which issue does this PR close?
None.
Rationale for this change
The roadmap is too old. Update our recent work about CeresDB 1.0 and subsequent working schedule.
What changes are included in this PR?
The doc about roadmap.
Are there any user-facing changes?
No.
How does this change test
No need.

Codecov Report

Merging #584 (149c009) into main (0163f60) will decrease coverage by 0.15%.
The diff coverage is 64.85%.

:exclamation: Current head 149c009 differs from pull request most recent head 4c6a9bc. Consider uploading reports for the commit 4c6a9bc to get more accurate results

@@            Coverage Diff             @@
##             main     #584      +/-   ##
==========================================
- Coverage   62.75%   62.60%   -0.15%
==========================================
  Files         322      326       +4
  Lines       49929    50232     +303
==========================================
+ Hits        31332    31449     +117
- Misses      18597    18783     +186

Impacted Files
Coverage Δ

analytic_engine/src/context.rs
0.00% <ø> (ø)

analytic_engine/src/row_iter/chain.rs
52.73% <0.00%> (ø)

analytic_engine/src/row_iter/mod.rs
30.30% <ø> (ø)

analytic_engine/src/setup.rs
54.54% <ø> (ø)

analytic_engine/src/sst/header.rs
0.00% <0.00%> (ø)

analytic_engine/src/sst/parquet/hybrid.rs
96.62% <ø> (ø)

analytic_engine/src/sst/reader.rs
92.30% <ø> (ø)

benchmarks/src/merge_memtable_bench.rs
0.00% <0.00%> (ø)

benchmarks/src/merge_sst_bench.rs
0.00% <0.00%> (ø)

benchmarks/src/parquet_bench.rs
0.00% <ø> (ø)

... and 63 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Replaced unavailabel gcr.io/google_samples image

Fixes #44415
Additionally refer PR #44999

@aj11anuj, there is already a PR opened for it. Here is that PR #44225
/triage duplicate

In previous PR, not anyone mentioned about it. Also, no one was assigned to that issue so, I was not aware of the fact that someone has already raised a PR for it.
Thanks for letting me know 👍


Problems using ioBroker/go-e adapter

hello anyone,
i tried using the Go-E-Charger adapter to include the WBEC into my HA-System. But everytime i got an API-Error

any ideas to solve this?

Hi
sorry, wbec emulates only a part of the go-E API (i.e. the main variables needed by Wallbox Steuerung App, openWB and EVCC).
The API seems to increase and increase every few weeks, so it's not possible to remain always up to date. And it doesn't make sense to send dozens of values just with constant default values (from my point of view).
So I'd suggest to solve this on the ioBroker side. Maybe the checks of the unneeded variables can be disabled?

Hi sorry, wbec emulates only a part of the go-E API (i.e. the main variables needed by Wallbox Steuerung App, openWB and EVCC). The API seems to increase and increase every few weeks, so it's not possible to remain always up to date. And it doesn't make sense to send dozens of values just with constant default values (from my point of view).
So I'd suggest to solve this on the ioBroker side. Maybe the checks of the unneeded variables can be disabled?

No problem. i'll do a little bit of json-magic and see what happen.
but thank you for your quick reply!

Is there an official manual how to do the json magic?


Couple of suggestions

Would suggest reducing the space between next line characters
adding caps on top and bottom would be another suggestion.

Multi line formatting needs work, I'm not sure how useful it really is to implement.
A simple workflow is to produce separate labels for each line, and then format them on the PCB?
Can you draw a quick sketch with how you'd like top/bottom caps to look? I can't picture what they would look like.

Some thing like this
Regards,
George

On 13 Jan 2022, at 4:14 AM, Gregory Davill @.***> wrote:

Multi line formatting needs work, I'm not sure how useful it really is to implement.
A simple workflow is to produce separate labels for each line, and then format them on the PCB?
Can you draw a quick sketch with how you'd like top/bottom caps to look? I can't picture what they would look like.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

Hi @anishkgt I don't see an image here.

This seems like the thread for suggestions - I'd love it if there were an ability to tweak labels after they're already placed on the board. Otherwise, on every change, I have to recreate the label from scratch. I know this might be a challenge given that each label is created as its own footprint, but if there's a straightforward way, I could try and implement it myself.

This seems like the thread for suggestions - I'd love it if there were an ability to tweak labels after they're already placed on the board. Otherwise, on every change, I have to recreate the label from scratch. I know this might be a challenge given that each label is created as its own footprint, but if there's a straightforward way, I could try and implement it myself.

Hi @Jkillelea, the feature as you've described is already implemented.
You can find a demo video here: https://github.com/gregdavill/KiBuzzard/pull/65
It's available in the KiCad PCM as a "testing release". Create a new label (Needs to have been created with the newest KiBuzzard). Once placed, with it selected open up KiBuzzard, it should now be editing that label, instead of creating a new one.


Multilingual translation

👍 Thanks!

EN
:
At present, it has not been hung in the domain name, because the current code of perl6 official network is almost a few years ago, not too much consideration of internationalization and fear of destroying the data warehouse of the official network. So I fork a copy, translated into Chinese, at present only the main entrance translation of the home page, some English is not good directly translated into Chinese literal meaning, so free translation, such as The Chinese data warehouse https://github.com/ccworld1000/perl6.org can be spread at Perl 6 Weekly. Maybe there will be a help to translate the school team together, if it doesn't have anything to do with it, but thank you very much for your help.
CN:
目前没有挂在域名下,由于perl6官网目前的代码几乎是几年前的,没有过多考虑到国际化,怕破坏官网数据仓.所以我fork了一个副本,翻译成中文,目前仅完成首页主要入口翻译,部分英文不好直接翻译成中文字面意思,所以采用意译.如果中文数据仓https://github.com/ccworld1000/perl6.org能在Perl 6 Weekly传播,也许会有一起帮忙翻译校队的,如果没有也没有啥关系.不过还是非常感谢你的帮忙.
ScreenShots:


Execution Stack on useState hook

I'm using the last version beta.1 and I'm seeing this behavior:

Render #1 - Start Render with message 'My Message' and state {"isVisible":true,"prevMessage":"My Message"}
Render #1 - End Render with message 'My Message' and state {"isVisible":true,"prevMessage":"My Message"}
Render #2 - Start Render with message '' and state {"isVisible":true,"prevMessage":"My Message"}
Render #2 - SetState with visible 'false' and prevMessage ''
Render #3 - Start Render with message '' and state {"isVisible":false,"prevMessage":""}
Render #3 - End Render with message '' and state {"isVisible":false,"prevMessage":""}
Render #2 - End Render with message '' and state {"isVisible":true,"prevMessage":"My Message"}

Start Render - Before checking the prevMessage agains props.message.
End Render - Just before the return for the render

So basically at the begin of the functional component I set the state to with isVisible to true because the prop message has a value and the prevMessage with the prop value.
As we can see from the render logs, Render # 1 is the first one and goes fine, then from the parent component I set the message to '' that fires Render # 2, since the props.message is different from state.prevMessage I update the state with isVisible to false and the prevMessage to '', that triggers Render # 3 and so far so good. The problem is as we can see after Render # 3 terminated the Render # 2 still executes the remaining instructions which is the return of the render but with wrong value as we can see on the log.
This is the expected behavior, my expectation is that last line of log never gets executed because it's deprecated.

Reproduction: https://codesandbox.io/s/xpv213py2w?fontsize=14

You are right I also upgrade the sandbox from the preview issue and that doesn't happen. The only thing different on my component is that instead of event on click the parent I just update the prop.message to ''. I'm using enzyme/preact to do the setProps on the component.

Hmm, well problem is that I can't seem to reproduce it at this point in codesandbox (tried a bit). So you're only getting this in a testing env?

Yes basically I have a test to start the component with a message and visible and then update the prop to ‘’ to make the component return null (no JSX returned) and it returns the JSX with empty message.
I also have a storyboard for it but storyboard far as I could find recreates the component when using dynamic props instead of just rerender it.


Issue with Memory simulation

Hi,
we are currently updating Amaranth version in Coreblocks (https://github.com/kuznia-rdzeni/coreblocks/pull/461) and unexpectedly some unit tests started to fail. Part of failing unit tests check the whole core on assembler programs. Similar tests using Cocotb and Verilator passed successfully, so I assume some problems with simulation inside Amaranth (as unit tests use amaranth tests framework). After some investigation it looks like the issue is related #893. Here is a reproduction example:
class MemoryReproduce(TestCaseWithSimulator):
    class DUT(Elaboratable):
        def __init__(self):
            pass

        def elaborate(self, platform):
            m = Module()
            self.mem = Memory(width=8, depth=8)
            m.submodules.read_port = self.read_port = self.mem.read_port()
            m.submodules.write_port = self.write_port = self.mem.write_port()
            return m

    def test_minimal(self):
        m = self.DUT()

        def process():
            yield m.read_port.addr.eq(1)
            yield m.read_port.en.eq(1)
            yield
            print((yield m.read_port.data))
            yield
            yield m.write_port.addr.eq(2)
            yield m.write_port.data.eq(14)
            yield m.write_port.en.eq(1)
            print((yield m.read_port.data))
            yield
            yield m.write_port.en.eq(0)
            print((yield m.read_port.data))
            yield
            print((yield m.read_port.data))
            yield
            print((yield m.read_port.data))

        with self.run_simulation(m) as sim:
            sim.add_sync_process(process)

Output for this test case:
0
0
0
14
0

Idea is that we try to read memory from the one address and write to the other one. So we expect that writing has no impact on reading. But as you can see that is not a case in Amaranth simulation. Write cause that on read data output port there is visible written value for one cycle.

cc @mwkmwkmwk

My bad, sorry >_>


Block Assignment Filters

2.8's block assignments have been incredibly useful, but I've found myself doing the following a lot...
{% set title %}

{{ value }}

{% endset %}
{% set title = title | safe %}

Would it be possible to allow moving the filter call into the block assignment call, such as with the following syntax?
{% set title | safe %}

{{ value }}

{% endset %}

(There might be a better / more generally flexible syntax, that's just the one that first occurred to me to try).

:+1:

Actually, the fact that you need to filter your set block as safe feels more like a bug to me since it results in double-escaped data very easily (which is something Jinja is usually pretty good at avoiding!).
Opened another issue about this: #490

#490 alone would definitely solve all my use-cases; if that was pushed through, I'd be happy whichever way you end up deciding this issue.  Without the frequent need to use a 'safe' filter, the block filter syntax is probably more than sufficient for the remaining edge cases that I can think of.


Add explicit PSK for AWS production VPN to Carrenza

Carrenza expects 32 digit alphanumerical PSK
Carrenza needed to configure a single subnet of /20 range in order for
the VPN to work AWS side

aws-data part: https://github.com/alphagov/govuk-aws-data/pull/256
pair: @schmie @stephenharker

Fixed whitespace errors and automated docs update only


fix for autocomplete filter with OR field values

Currently when you are using the HaystackAutocompleteFilter and you also want to reduce the queryset based on fixed value filter fields like: autocomplete=I_want_to_find_this&status=status_1,status_2 this fails with:
  File "/python2.7/site-packages/rest_framework/mixins.py", line 40, in list
    queryset = self.filter_queryset(self.get_queryset())
  File "/python2.7/site-packages/drf_haystack/generics.py", line 82, in filter_queryset
    queryset = super(HaystackGenericAPIView, self).filter_queryset(queryset)
  File "/python2.7/site-packages/rest_framework/generics.py", line 151, in filter_queryset
    queryset = backend().filter_queryset(self.request, queryset, self)
  File "/python2.7/site-packages/drf_haystack/filters.py", line 125, in filter_queryset
    queryset = queryset.filter(self._construct_query(applicable_filters, queryset, view))
  File "/python2.7/site-packages/drf_haystack/filters.py", line 134, in _construct_query
    for field_name, query in filters.children:
TypeError: 'SQ' object is not iterable

filters.children: [(u'autocomplete', u'I_want_to_find_this'), <SQ: OR (status__contains=status_1 OR status__contains=status_2)>]
This PR fixes that.
With this PR the resulting parsed filters are: [<SQ: AND autocomplete__contains=I_want_to_find_this>, <SQ: OR (status__contains=status_1 OR status__contains=status_2)>]
I think this is the expected behaviour.

I do not quite understand why the tests fail. It works for me. Added a test that should pass also.
If I'm totally missing something here please let me know...

Actually, I think I was using the autocomplete filter with the wrong use case. You probably want to leave it as is.

Hi, thanks for taking time to investigate.
Alright, thats fine :)


Gcc/windows

Hi @jschueller, your prompt action is highly appreciated.

I have copied the code manually: https://github.com/libprima/prima/commit/0927504898e3a476a9e7b1708204c73bd0ae3968
Thank you.


Issues with displaying the "Remarks" section.

Instead of the regular, header-like formatting for the word "Remarks" at the beginning of that section, the string "## Remarks" is being displayed.

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

ID: d6ca439b-7edb-a39b-c5a5-2e9aabb0beae
Version Independent ID: e9e00d5a-00ff-ae74-1f08-3dde79ec588a
Content: _WDF_DEVICE_POWER_POLICY_IDLE_SETTINGS (wdfdevice.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdfdevice/ns-wdfdevice-_wdf_device_power_policy_idle_settings.md
Product: windows-hardware
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thanks for the feedback @PawelWMS and apologies for the delay.  I do not currently repro what you report, so maybe this got fixed somehow?  Please reopen if you still see the problem.

No worries, I also don't see it right now, but I'll be sure to let you know, if this happens again.


Drone 1984

About the PR
Gives drones an interaction range check, interaction whitelist and they are no longer immune to status effects and temperature. Closes https://github.com/space-wizards/space-station-14/issues/6998 and closes https://github.com/space-wizards/space-station-14/issues/6637
Changelog

:cl: Rane

tweak: Drones can now only pick up or drag a whitelist of items.
tweak: Drones are now way easier to kill for a variety of reasons.
tweak: Drones can no longer interact with anything within 2½ tiles of a non-drone mob. The nerfs will continue until morale improves.

I have changes that replace the first target check to apply to all entities within 4 tiles ready to go, I want opinions on the perf impact of that first though

I noticed the interaction change was a bit controversial so I reduced the check range to a bit beyond interaction range. You should be able to work within the same room as other people a bit easier.

I have changes that replace the first target check to apply to all entities within 4 tiles ready to go, I want opinions on the perf impact of that first though
edit: yolo

when autoclicker protection is in I don't imagine it being a problem.


Wallet > Contacts: No way of seeing contacts description

Hi,
There is a description field available when creating a new contact but no way to see the description after the contact had been created.
Thanks
Jazmin

will be done. or removed

Now available in wallet v1.1.3, contact info page includes editing/updating icon, description

Tested and confirm that contact description can now be seen

fixed in 1.1.3 confirmed by @jazminrib