Unable to download and attach PDF of SOME Dashboards

Description
I can't find a specific pattern to why this happens, but some Dashboards can be downloaded via the CLI while others cannot. This applies across the board to multi-page Dashboards, but also to some single page Dashboards.
Error Message
./nr-reports-cli/bin/nr-reports.sh --debug -d <DASH_GUID>
[Mon, 12 Dec 2022 20:51:37 GMT] engine Created temporary directory dashboards-xJsCa4
[Mon, 12 Dec 2022 20:51:37 GMT] nerdgraph {"query":"mutation($guid: EntityGuid!){\n      dashboardCreateSnapshotUrl(guid: $guid)\n    }","variables":{"guid":"<DASH_GUID>"}}
[Mon, 12 Dec 2022 20:51:38 GMT] nerdgraph {"data":{"dashboardCreateSnapshotUrl":null},"errors":[{"extensions":{"errorClass":"SERVER_ERROR","type":"UNSUPPORTED_OPERATION"},"locations":[{"column":7,"line":2}],"message":"Unsupported operation on dashboard with given guid: <DASH_GUID>","path":["dashboardCreateSnapshotUrl"]}]}
[Mon, 12 Dec 2022 20:51:38 GMT] nerdgraph GraphQL post error for query: {"data":{"dashboardCreateSnapshotUrl":null},"errors":[{"extensions":{"errorClass":"SERVER_ERROR","type":"UNSUPPORTED_OPERATION"},"locations":[{"column":7,"line":2}],"message":"Unsupported operation on dashboard with given guid: <DASH_GUID>","path":["dashboardCreateSnapshotUrl"]}]}
[Mon, 12 Dec 2022 20:51:38 GMT] engine {}
Error: GraphQL post error for query: {"data":{"dashboardCreateSnapshotUrl":null},"errors":[{"extensions":{"errorClass":"SERVER_ERROR","type":"UNSUPPORTED_OPERATION"},"locations":[{"column":7,"line":2}],"message":"Unsupported operation on dashboard with given guid: <DASH_GUID>","path":["dashboardCreateSnapshotUrl"]}]}
    at NerdgraphClient.post (~/nr-reports/nr-reports-core/lib/nerdgraph.js:115:13)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async NerdgraphClient.query (~/nr-reports/nr-reports-core/lib/nerdgraph.js:145:25)
    at async downloadDashboardPdf (~/nr-reports/nr-reports-core/lib/engine.js:104:15)
    at async ~/nr-reports/nr-reports-core/lib/engine.js:268:11
    at async Promise.all (index 0)
    at async Engine.runDashboardReport (~/nr-reports/nr-reports-core/lib/engine.js:270:25)
    at async main (~/nr-reports/nr-reports-cli/index.js:142:9)
[Mon, 12 Dec 2022 20:51:38 GMT] engine Removing temporary directory dashboards-xJsCa4...

@dantectl can you try to recreate on the latest v3.0.0 release?  Multi-page dashboards are not supported at this time.  If it is a single page dashboard, please share an example.

Closing this because it is stale.  @dantectl create a new issue if it still occurs.


Vanilla shadows "Prefer in PvM" not working at Grotesque Guardians?

Hi, i hope I'm not misunderstanding here but according to the hover description of Vanilla Shadows, the setting "Prefer in PvM" should retain the circular shadow of the falling rocks which is helpful, but disable the cast shadow of the rocks? That doesn't seem to be working here, it's very difficult to see Jagex's shadow already with HD on but the cast shadows make it worse. Thank you

Thanks a lot! cant wait

Fixed in https://github.com/117HD/RLHD/commit/f84b1f121a65fc0f9e47787bb40c70d4fa18f0eb, which should be in the next release. I've also changed the behaviour of 'Prefer in PvM' to only hiding HD shadows in specific cases, which currently only includes falling crystals at Olm, and falling rocks at Grotesque Guardians. I have a feeling people who want to disable shadows for bosses too might as well just disable shadows entirely. If it turns out people were actually relying on that behaviour though, I might add another setting for it.

Thanks! I think scurrius is another one. I guess people who are serious turn off shadows for bosses or just turn off HD? idk, its just the shadow of falling rocks that bother me especially the damage radius at GGs


Magic smpi cp4cds

The recipe recipe_smpi_4cds.yml was adjusted to the cp4cds datasets and was tested on Jasmin. Due to the memory requirements of this recipe and the available memory at the high-mem nodes we need to choose between 17 models/10 years or 5 Models/25 years or something in between.
We used the following resource request:
#!/bin/bash
#BSUB -q high-mem
#BSUB -o %J.out
#BSUB -e %J.err
#BSUB -W 05:00
#BSUB -M 256000
#BSUB -R "rusage[mem=256000]"

This is the useage summary:
    CPU time :                                   56341.02 sec.
    Max Memory :                                 220927 MB
    Average Memory :                             179419.31 MB
    Total Requested Memory :                     256000.00 MB
    Delta Memory :                               35073.00 MB
    Max Swap :                                   1196104 MB
    Max Processes :                              16
    Max Threads :                                480
    Run time :                                   11555 sec.
    Turnaround time :                            11555 sec.

Regarding the high memory consumption: what value did you use for max_parallel_tasks in your config user file?

Just a closing remark here. Thanks @bouweandela for the reminder to the max_parallel_tasks. I set this to 1 and it reduced the memory requirement as expected down to a max of 136 GB till it timeout after 14h with 17 models and 25 years (full set possible). I will try again giving it more time and using a different queue.


Display redraws slowly on ATMEGA1284

The code works perfectly on ATMega328.  I decided to use an ATMEGA1284 for more RAM but the display appear3e to run extremely slow.   I then altered the code to use PORTA insead of PORTD (to avoid clashing with the timerOne pins) but it didn't seem to help.   Is there anything else I can try?

I assume the problem is the PMW state detction in the scan() function. I built it so that the display is only refreshed in the "off"-state of the enable pin. This way artefacts of half drawn lines are prohibited. The following to lines in the code achieve that (blocking while loop):

uint16_t r = -2000;  //timeout
while (!(PIND & (1<<3)) && ++r);

To fix the problem when you are using a different PWM source than pin D3, change the "PIND & (1<<3)" to the real PWM-pin you use. Make sure that the PWM-frequency is at high enough to avoid flickering. If you don't care about the artefacts, you can either set r = -1 instead of -2000 or remove the two lines entirely.
Hope that helps.

Brilliant!  I shall give that a test when I get back to the lab!
Once I've fixed this, I hope to include the changes into the main library to make this library compatible with other chips!
Thanks!

It works like a charm!
Thanks!


Question about WalletConnect v2.0 migration schedule

Hi,
I noticed that the WalletConnect package has a migration schedule for version 2.0 and it's not backwards-compatible with version 1.0. I was wondering if the maintainers have any plans to upgrade the package and coordinate a migration schedule to ensure that end-users do not suffer from this transition?
Reference:

https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e
https://docs.walletconnect.com/2.0/advanced/migrating-from-v1.0

Cool, I planned to create a new connector named WalletConnectorV2 for this migration. This issue has not yet been started so welcome any contributors to jump in and make your mark :)

Starting from v0.9.x, WalletConnect v2 is supported.


Error Domain=com.alamofire.error Code=-999

When cancelling an image download (e.g. loading another image in an UIImageView while the previous request is still running), AlamofireImage executes the completion block with .Failure(error) like so:
Error Domain=com.alamofire.error Code=-999 "ImageDownloader cancelled URL request: https://mywebsite/image.jpg" UserInfo={NSLocalizedFailureReason=ImageDownloader cancelled URL request: https://mywebsite/image.jpg}

Now this looks good but the error domain is set to alamofire (com.alamofire.error) and code -999 is not defined in this error domain but it seems that it is actually coming from NSURLErrorDomain and that would be code NSURLErrorCancelled. Shouldn't the domain really be NSURLErrorDomain rather than  com.alamofire.error?

Thanks for reporting this @ivasic. You are completely right. The domain has been fixed in b2eb1005.
Cheers. 🍻


Bump used Kotlin version to 1.0.3

Kotlin is at 1.0.3 by now, while KotlinTest is still using 1.0.1-2, which causes intelliJ to fail the gradle sync because of mismatching dependency version. I don't really want to go back to an earlier Kotlin version for my project and miss out on the faster compiling just to use KotlinTest...

I've released 1.3.1 which runs on Kotlin 1.0.3.


chore(blockifier): create unit tests for contract_class_manager

This change is

#2768  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Diagnostics slow to update

Product and Version: Visual Studio
OS Version: Windows
Live Share Extension Version: 0.3.371.21991
Target Platform or Language: C# - WPF Desktop application
Steps to Reproduce / Scenario:

Although tracking another person is fairly snappy, other parts are just too slow. The error list can take a bit of time to update as you resolve, so if you're both working on fixing errors across multiple files only the host will really know how many errors are left. The same issue appears in code too. Those red squiggly lines can take an age to disappear/update unless you're the host. You tend to feel like you're always a step behind the host, making it difficult to make any real contribution and in the end leaves you frustrated.
Developer review when in collaboration session.

@tomntech Thanks for the feedback. Can you give us more details on your scenario, especially solution size / internet connection speed? Also, were you using relay or direct connection?

This issue is has been closed due lack of any recent activity. We've made lots of improvements to Live Share since this issue. Please re-open the issue, if this issue persists.
🤖Live-Share-Clean-Up-Bot🤖


Proposed feature #3 - non-RDB images

This is difficult and likely not feasible/appropriate.
The UAE4All (at least the PS-Vita version) unfortunately works only with non-RDB images. You have created a HstWB version for it, so you know this well.
Now, Hst-image is meant for mastering RDB images, while a non-RDB seems really out of scope.
Nevertheless, if this could create non-RDB images (I guess the only option is FFS here) it would close another corner-case.
Once again, thank you for your consideration.

Non-RDB images or single partition hdf files would require geometry defined for each command. However only following commands would be of interest for Non-RDB images:

blank
rdb part add (only dos type will be used, size will either be ignored as its given by the image file size or the image file is resized to the given size)
rdb part format

Non-RDB images can currently be created by exporting a partition to a file. This will function same way as a Non-RDB image and WinUAE requires sectors set to 63 instead of 32 when added (63 if default sectors used when running rdb init).

I worked on support for formatting non-RDB partitions and seems to got it working with latest released version v0.9.257. This has only been tested with WinUAE and not with an emulator like UAE4ALL on a PS Vita.
Here's an example of creating and formatting a DOS\3 non-RDB partition image file.
hst.imager.exe blank dos3_non-rdb.hdf 10mb
hst.imager.exe rdb part format dos3_non-rdb.hdf 1 WorkbenchDOS3 --non-rdb --dos-type DOS3

And an example of creating and formatting a PFS\3 non-RDB partition image file.
hst.imager.exe blank pfs3_non-rdb.hdf 10mb
hst.imager.exe rdb part format pfs3_non-rdb.hdf 1 WorkbenchPFS3 --non-rdb --dos-type PFS3

Adding non-RDB in WinUAE requires setting geometry surfaces to 16 and sectors 63 (others if different CHS is used) and select file sys.

Booting WinUAE with Amiga OS 3.1 Workbench adf and non-RDB image file shows following:

I have a PS Vita and need to do some testing to see what's possible. It sounds more like it's the size of the image thats the limiting factor and not what surfaces or sectors are used. But I do recall I prepared the UAE4ALL image files with surfaces set to 2 and sectors to 32. Maybe UAE4ALL supports PFS3 by manually editing the config files, I need to test it.
I knew it would be useful to tweak cylinders, heads and sectors so the option is already available to format with surfaces set to 2 and sectors set to 32 with following commands:
hst.imager.exe blank dos3_non-rdb.hdf 1900mb
hst.imager.exe rdb part format dos3_non-rdb.hdf 1 WorkbenchDOS3 --non-rdb -chs 0,2,32 --dos-type DOS3

The trick is the option -chs 0,2,32 when formatting, which sets cylinders to 0 (0 = max cylinders calculated), heads to 2 (same as surfaces) and sectors to 32.
The 2 commands outputs the following:
hst.imager.exe blank dos3_non-rdb.hdf 1900mb
[16:35:11 INF] Hst Imager v0.1.0 (12/09/2022 12:48:18)
[16:35:11 INF] Henrik Noerfjand Stengaard
[16:35:11 INF] [CMD] blank dos3_non-rdb.hdf 1900mb
[16:35:11 INF] Creating blank image at 'dos3_non-rdb.hdf'
[16:35:11 INF] Size '1.9 GB'<PHONE_NUMBER> bytes)
[16:35:11 INF] Done

hst.imager.exe rdb part format dos3_non-rdb.hdf 1 WorkbenchDOS3 --non-rdb -chs 0,2,32 --dos-type DOS3
[16:35:16 INF] Hst Imager v0.1.0 (12/09/2022 12:48:18)
[16:35:16 INF] Henrik Noerfjand Stengaard
[16:35:16 INF] [CMD] rdb part format dos3_non-rdb.hdf 1 WorkbenchDOS3 --non-rdb -chs 0,2,32 --dos-type DOS3
[16:35:16 INF] Formatting partition in Rigid Disk Block at 'dos3_non-rdb.hdf'
[16:35:16 INF] - Size '1.9 GB'<PHONE_NUMBER> bytes)
[16:35:16 INF] - Cylinders '60800'
[16:35:16 INF] - Heads '2'
[16:35:16 INF] - Sectors '32'
[16:35:16 INF] - Low Cyl '0'
[16:35:16 INF] - High Cyl '60799'
[16:35:16 INF] - Reserved '2'
[16:35:16 INF] - DOS type '0x444F5303' (DOS\3)
[16:35:16 INF] - Volume name 'WorkbenchDOS3'
[16:35:17 INF] Done


[High High Priority] Marking COI projects as null in ballot

Reported COI should have impact=0, in the ballot, like retrolist is set to null in OP-UI but when reported in our UI, they are in the ballot.

related thread in Slack: https://mrnikkhahgmai-sjg9938.slack.com/archives/C06S2B5CM36/p1730322160669249

could you please tell me more about this issue for testing @MoeNick @mmahdigh

Mark some projects as conflict of interest, and when updating the ballot, they should be out of the ballot at the bottom, like the image I provided @maryjaf


feat(plugin): ai prompt template

Summary
This plugin adds the ability to provide tuned AI prompts to users, who only need to fill in the blanks with variable placeholders (in moustache format: {{variable}} )
It is to be used in conjunction with ai-proxy plugin, as with other AI Family plugins.
AI-Proxy plugin
This allows prompt tuning to be started, or performed, by the experience LLM users in an organisation, and then consumed by anyone.
When activated, it looks for template references in the following forms:
Chat:
{
	"messages": "{template://developer-chat}",
	"properties": {
		"language": "python",
		"program": "flask web server"
	}
}

Prompt:
{
	"prompt": "{template://developer-prompt}",
	"properties": {
		"language": "python",
		"program": "flask web server"
	}
}

Based on this gateway configuration:
_format_version: "3.0"

services:
- name: default
  host: localhost
  path: "/"
  port: 9900
  protocol: https
  routes:
  - name: openai-chat
    paths:
    - "~/openai/chat$"
    methods:
    - POST
    plugins:
    - name: ai-proxy
      config:
        route_type: "llm/v1/chat"
        auth:
          header_name: "Authorization"
          header_value: "Bearer REDACT"
        logging:
          log_statistics: true
          log_payloads: false
        model:
          provider: "openai"
          name: "gpt-3.5-turbo"
          options:
            max_tokens: 512
            temperature: 1.0
    plugins:
    - name: ai-prompt-template
      config:
        allow_untemplated_requests: true
        templates:
        - name: "developer-chat"
          template:  |-
            {
              "messages": [
                {
                  "role": "system",
                  "content": "You are a {{program}} expert, in {{language}} programming language."
                },
                {
                  "role": "user",
                  "content": "Write me a {{program}} program."
                }
              ]
            }
        - name: "developer-prompt"
          template:  |-
            {
              "prompt": "You are a {{language}} programming language expert. Write me a {{program}} program."
            }

It has been designed to work with other formats as soon as they are supported.
It also sanitises string inputs to ensure that json control characters are escaped, preventing arbitrary prompt injection.
Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - docs PR for all four "AI Family" pluigins is still being worked on separately.

Issue reference
Internal project.

All addressed in https://github.com/Kong/kong/pull/12340


Adding the key for the first time

when you add a document for the first time you can not see the id in the firestore console, only you can see it when you update the doc.

HI @hsouiri97 can you provide an example?

@amranidev  when we call this function this.$firestore.persons.add() for the first time we can save the object in firestore however we can not see the id or ".key" value in firestore console, but if we looped trough the list of objects in our application and console log them we can see that they have and id value, so then if we call  this.$firestore.persons.doc(person['.key']).update() we can see that the ".key" value has been added to firestore console.


Triangulation by Ear Clipping

After providing set of points, I had been getting this output but how to clip those edges??

Hello @ThanbirTamim,
Unfortunately Delaunator does not support it. Visit this thread for more info.
Cheers

Hello @ThanbirTamim, Unfortunately Delaunator does not support it. Visit this thread for more info.
Cheers
Acknowledged. Thank you dear.


When MDR change connection state from new to connected, then this change is ready for a calculation job.

Issue moved to Energinet-DataHub/geh-aggregations #617 via ZenHub


[windows] updated v5.4.0

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

license_file entry is missing, but is required.

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender

@conda-forge/suitesparse This is a version bump and ready for review and merge. Thanks!

please rebase from master, it's 5.7.2 now

@jschueller
It looks like the SuiteSparse for Windows build lives for its own on this separate branch since this and it takes the source from this project instead: https://github.com/jlblancoc/suitesparse-metis-for-windows, which attempts to keep CMake recipe for cross-platform compiling and now it is ported to v5.4.0.
I don't think doing a simple rebase of this feedstock can take it to v5.7.2. Or maybe I misread your comments? What's the step I should take?

oh, right, I did not see that.

@conda-forge/suitesparse @conda-forge/core This is ready for review and merge. Thanks!

pls only bump the team and not core on these. We can help if this is not merged for about a week or so.

@conda-forge-admin, please rerender

@isuruf Btw, I saw there are some warnings like these:
Do you recommend to add libopenblas to the run requirements? Currently I am only adding blas meta-package as the run dependency.
WARNING (suitesparse,Library\bin\cholmod.dll): Needed DSO Library\bin\openblas.dll found in ['libopenblas']
WARNING (suitesparse,Library\bin\cholmod.dll): .. but ['libopenblas'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)

@isuruf hmm, the CI seems not to like the changes. What should we do for the next step?

Try and delete %PREFIX%/Library/lib/cmake/ ?

@isuruf Just wondering, what's the latest doc for how to integrate with blas? Is this one still updated to dated? https://conda-forge.readthedocs.io/en/latest/blas.html

It's the one at https://conda-forge.org/docs/maintainer/knowledge_base.html#blas

I see, so I probably looked at a old site (https://conda-forge.readthedocs.io/) instead of the latest one (https://conda-forge.org/docs/index.html).

Thanks. I'll see if I can get that old site deleted.

@conda-forge/suitesparse Friendly ping. I think this is ready for merge. Thanks.

Great to see this happening. I was planning to get around to doing this myself after having build suitesparse for windows within conda-forge/cvxopt-feedstock#42.
I detailed some of that in #51 - I believe (hope?) that metis is not necessary and that we can go to 5.7.2 directly.

Great to see this happening. I was planning to get around to doing this myself after having built suitesparse for windows within conda-forge/cvxopt-feedstock#42.

Happy to see the progress on this too. For my short-term goal, I just want to have ceres Windows port with suitesparse enabled, so I can do a conda-forge feedstock for https://github.com/cartographer-project/cartographer. And I am happy to see any attempts to get it converged toward to that direction. :)

I am inclined to go ahead and merge this soon given that it is now passing CI. That said, I don't have experience with Windows + SuitSparse/METIS and would appreciate any feedback from other maintainers.

@seanyen True, there's no reason not to merge this, any progress can come on top of this PR.

Thank you all!


Updated forward mode and related tests

Codecov Report

Merging #18 (8041691) into main (cbcaecf) will increase coverage by 0.24%.
The diff coverage is 84.48%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
+ Coverage   96.22%   96.47%   +0.24%
==========================================
  Files           4        5       +1
  Lines         636      680      +44
==========================================
+ Hits          612      656      +44
  Misses         24       24

Flag
Coverage Δ

unittests
96.47% <84.48%> (+0.24%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

autodiff/demo.py
0.00% <0.00%> (ø)

autodiff/autodiff.py
99.28% <100.00%> (+4.54%)
:arrow_up:

autodiff/tests/test_simpleautodiff.py
100.00% <100.00%> (ø)

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 cbcaecf...8041691. Read the comment docs.


Resolve upstream tasks when template field is XComArg

closes: #8054

Make sure to mark the boxes below before creating PR: [x]

[ ] Description above provides context of the change
[ ] Unit tests coverage for changes (not needed for documentation changes)
[ ] Target Github ISSUE in description if exists
[ ] Commits follow "How to write a good git commit message"
[ ] Relevant documentation is updated including usage instructions.
[ ] I will engage committers as explained in Contribution Workflow Example.

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

Oh, I think I've got to open this PR against master to start github actions...


VM hardware resource states disappear after changing new offering

in Zstack manahement the VM hardware resource states is empty now, I thought that would be show some hardware resource information such as CPU usage, harddisk,memory.........
current states please refer to attached picture. Thank

Does it happen after change VM's offering?

Yes. this happen after change VM's offering

This bug looks like a UI bug only. The VM Instance data structure is correct, when doing queryvminstance operation in zstack-cli.

this is handled by the new UI. Open it if it's still found in the new UI


SkyDNS support for etcd version 3?

Hi!
Does skyDNS currently support etcdv3?
If it doesn't... Would it be possible to have an optional parameter passed during its startup?
That way, say, by default it supports the original etcd backend, but with the additional parameter it would support the new etcd version 3.

@fbdlampayan basically if we support etcd v3, we will support both etcd v3 and v2.

Hi!
@AdoHe Yes that is true.
As far as I understood, etcdv3 storage "coexists" with v2, in a paralllel but separate manner.
So does skyDNS now support etcd v3?

[ Quoting<EMAIL_ADDRESS>in "Re: [skynetservices/skydns] SkyDNS ..." ]

Hi!
@AdoHe Yes that is true.
As far as I understood, etcdv3 storage "coexists" with v2, in a paralllel but separate manner.
So does skyDNS now support etcd v3?

don't know about etcd2/3 storage, but skydns uses the etcd client, so
communicating with etcd should work regardless of v2/v3

hi
the interface towards etcd changed between v2 and v3, so new backend is needed if v3 etcd was to be supported.
Is such change planned, or can be proposed for skydns?
thanks
gergo

[ Quoting<EMAIL_ADDRESS>in "Re: [skynetservices/skydns] SkyDNS ..." ]

hi
the interface towards etcd changed between v2 and v3, so new backend is needed if v3 etcd was to be supported.
Is such change planned, or can be proposed for skydns?

Nothing is planned, but sure, v3 support should be added to skydns.
/Miek
--
Miek Gieben

[ Quoting<EMAIL_ADDRESS>in "Re: [skynetservices/skydns] SkyDNS ..." ]

hi
the interface towards etcd changed between v2 and v3, so new backend is needed if v3 etcd was to be supported.
Is such change planned, or can be proposed for skydns?

doesn't sound hard though: https://github.com/coreos/etcd/blob/master/Documentation/op-guide/v2-migration.md
Might take some work to neatly integrate it all.
/Miek
--
Miek Gieben

@miekg actually etcd v2/v3 use different wire protocol, so we may need a backend storage factory, thus we can support both v2 and v3.

our initial idea was to have a parameter to define which version to use, so skydns once started, would only support one api version.
sthing like an additional parameter at startup would define the etcd api version to be used, based on which the v2 or v3 etcd client and backend would be instantiated
the backend would implement the new v3 api.
another issue is that unfortunatelly new etcd release is needed for the ttl retrieval, so we need to wait this release: https://github.com/coreos/etcd/pull/6321
how could this dependency ( from etcd version), be handled in skydns ( meaning skydns etcd v3 backend can be used only with this given etcd version) ?

@GergoBota I understand what you mean, adding an additional parameter to determine the storage version. I will open a PR asap.

hi, ok thanks.
i imagine "storage version" will mean using coreos/etcd/clientv3 in backends, and thus have full v3 support in skydsn
Getting ttl, lease time from etcd will not be available until the mentionned etcd fix, how do you plan to handle that? is it ok to have maybe a hardcoded default value, than when etcd support is there, this part will be adjusted?
thanks

hi @AdoHe
we might also have a solution for this, not sure what are the plans about your PR, when it could be published or if we could, should we propose our solution; what do you think? thanks

If I am reading this correctly, skydns will not work with etcd +v3.0 and I should stick to v2.3?

[ Quoting<EMAIL_ADDRESS>in "Re: [skynetservices/skydns] SkyDNS ..." ]

If I am reading this correctly, skydns will not work with etcd +v3.0 and I should stick to v2.3?

I think we merged etcd3 support some time ago?

I just tried with a v3 setup and this didn't work. Entries would not get registered in etcd.

[ Quoting<EMAIL_ADDRESS>in "Re: [skynetservices/skydns] SkyDNS ..." ]

I just tried with a v3 setup and this didn't work. Entries would not get registered in etcd.

you might have more luck pushing (or fixing) this issue:
https://github.com/coredns/coredns/issues/341
coredns right now should be a drop in replacement for skydns and it has more
momentum.
/Miek
--
Miek Gieben


firstDeploymentManifest was unexpected at this time

I have a nodejs application.
Repro steps.
From DevOps (VSTS), when launch my deploy pipeline I do:

Create a new Slot (to have something completely fresh all the time)
Deploy (here is the yml file:)

  - task: AzureRmWebAppDeployment@4
    displayName: 'Deploy'
    inputs:
      azureSubscription: '53141-UAP Dev (e035b49f-6351-4b0b-9963-26568006e37c)'
      WebAppName: 'dev-uap-api'
      deployToSlotOrASE: true
      ResourceGroupName: 'Dev-UAP'
      SlotName: 'dev-uap-api-slot'
      packageForLinux: '$(System.DefaultWorkingDirectory)/apps/api/bundle'
      ScriptType: 'File Path'
      ScriptPath: apps/api/bundle/deploy.cmd

Error
\SiteExtensions\Kudu\85.11024.4154\bin\Scripts\firstDeploymentManifest was unexpected at this time.
Detail log
##[debug]release.releaseName=undefined
##[debug]system.TeamFoundationCollectionUri=https://dev.azure.com/se-devops/
##[debug]system.teamProjectId=81930716-5d7d-4de1-b740-f1dfade42103
##[debug]build.requestedfor=Jean-Yves Couet
##[debug]build.buildId=4030
##[debug]build.buildNumber=v2019.314.06
##[debug]build.sourceVersion=c6440055c0fbca5bcb46b302bf1a9e85734e4c91
##[debug]build.repository.name=seweb
##[debug]build.repository.provider=TfsGit
<EMAIL_ADDRESS>##[debug]build.sourcebranchname=azureScripts
##[debug]build.buildUri=vstfs:///Build/Build/4030
##[debug]release.releaseUri=undefined
##[debug]build.buildId=4030
##[debug]release.releaseId=undefined
##[debug]build.buildNumber=v2019.314.06
##[debug]release.releaseName=undefined
##[debug]system.TeamFoundationCollectionUri=https://dev.azure.com/se-devops/
##[debug]system.teamProjectId=81930716-5d7d-4de1-b740-f1dfade42103
##[debug]build.sourceVersion=c6440055c0fbca5bcb46b302bf1a9e85734e4c91
##[debug]build.repository.name=seweb
##[debug]build.repository.provider=TfsGit
##[debug]system.teamproject=All-In
##[debug]setting affinity cookie ["ARRAffinity=3b3c4aff831332571e895a2cd63f49c33a9ddf728147b0f73911a1b2189dcda2;Path=/;HttpOnly;Domain=my-website-my-website-slot.scm.azurewebsites.net"]
<EMAIL_ADDRESS>##[debug]updateDeployment. Data: {"statusCode":200,"statusMessage":"OK","headers":{"cache-control":"no-cache","pragma":"no-cache","content-length":"1191","content-type":"application/json; charset=utf-8","expires":"-1","server":"Microsoft-IIS/10.0","x-ms-request-id":"cdccf810-8586-4bd1-ba74-264d3c924998","x-aspnet-version":"4.0.30319","x-powered-by":"ASP.NET","date":"Sun, 10 Nov 2019 23:15:30 GMT","connection":"close"},"body":{"id":"40301573427730605","status":3,"status_text":null,"author_email":null,"author":"Jean-Yves Couet","deployer":"VSTS","message":"{\"type\":\"Deployment\",\"commitId\":\"c6440055c0fbca5bcb46b302bf1a9e85734e4c91\",\"buildId\":\"4030\",\"buildNumber\":\"v2019.314.06\",\"repoProvider\":\"TfsGit\",\"repoName\":\"seweb\",\"collectionUrl\":\"https://dev.azure.com/se-devops/\",\"teamProject\":\"81930716-5d7d-4de1-b740-f1dfade42103\",\"buildProjectUrl\":\"https://dev.azure.com/se-devops/81930716-5d7d-4de1-b740-f1dfade42103\",\"repositoryUrl\":\"https://se-devops@dev.azure.com/se-devops/All-In/_git/seweb\",\"branch\":\"azureScripts\",\"teamProjectName\":\"All-In\",\"slotName\":\"my-website-slot\"}","progress":null,"received_time":"0001-01-01T00:00:00","start_time":"2019-11-10T23:15:31.0391856Z","end_time":"2019-11-10T23:15:31.0391856Z","last_success_end_time":null,"complete":false,"active":false,"is_temp":false,"is_readonly":false,"url":"https://my-website-my-website-slot.scm.azurewebsites.net/api/deployments/40301573427730605","log_url":"https://my-website-my-website-slot.scm.azurewebsites.net/api/deployments/40301573427730605/log","site_name":null,"provisioningState":null}}
Successfully updated deployment History at https://my-website-my-website-slot.scm.azurewebsites.net/api/deployments/40301573427730605
##[debug]Active DeploymentId :40301573427730605
##[debug][POST]https://management.azure.com/subscriptions/e035b49f-6351-4b0b-9963-26568006e37c/resourceGroups/Dev-UAP/providers/Microsoft.Web/sites/my-website/slots/my-website-slot/publishxml?api-version=2016-08-01
##[debug]Could not parse response: {}
##[debug]Response: undefined
App Service Application URL: http://my-website-my-website-slot.azurewebsites.net
##[debug]set AppServiceApplicationUrl=http://my-website-my-website-slot.azurewebsites.net
##[debug]Processed: ##vso[task.setvariable variable=AppServiceApplicationUrl;issecret=false;]http://my-website-my-website-slot.azurewebsites.net
##[debug]Deployment failed

Note
I think that it's linked with the fact that it's a "new" environment all the time... so there is an issue with this "firstDeployment". Can't we turn this off? so that it's just executing my custom script?

Umm .. wasn't the error coming from your customized deploy.cmd?   If so, you could fix it in your script, no?
Internal Ref:
Kudu
| where PreciseTimeStamp > datetime(2019-11-10 23:15) - 5m
| where PreciseTimeStamp < datetime(2019-11-10 23:15) + 5m
| where EventPrimaryStampName == "waws-prod-am2-127"
| where RoleInstance == "SmallDedicatedWebWorkerRole_IN_57"

It's really strange! I'm doing some echo or set variables... Then I have this error. That's why I don't think that it's coming from my script.
Also I can see that I have 2 deployment folder.
As I said, it's a new slot all the time, can this be the issue? There is a must 'firstDeploymentManifest'?

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:///Users/Shared/Dropbox/Sites/website.com/node_modules/grunt-grunticon/node_modules/svg-to-png/lib/phantomscript.js. Domains, protocols and ports must match.

At first I thought this error was responsible for grunticon not completing. However, after a little digging I found the culprit and opened Issue #206
It would still be nice to not see this notice/error. :)
Running "grunticon:svg" (grunticon) task
Look, it's a grunt icon!
grunticon now minifying the stylesheet loader source.
grunticon loader file created.
Coloring SVG files
Converting SVG to PNG
svg-to-png now spawning phantomjs...
(using path: /Users/Shared/Dropbox/Sites/website.com/node_modules/grunt-grunticon/node_modules/svg-to-png/node_modules/phantomjs/lib/phantom/bin/phantomjs)
Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:///Users/Shared/Dropbox/Sites/website.com/node_modules/grunt-grunticon/node_modules/svg-to-png/lib/phantomscript.js. Domains, protocols and ports must match.

I tried adding "--web-security=false" to node_modules/grunt-grunticon/node_modules/svg-to-png/lib/svg-to-png.js but it didn't seem to change anything.
execFile( phantomJsPath,
    [
        "--web-security=false",
        phantomfile,
        input,
        output,
        opts.pngfolder,
        opts.defaultWidth,
        opts.defaultHeight
    ],
...

Unfortunately, this is a PhantomJS issue that we can't get around - https://github.com/ariya/phantomjs/issues/12697

Crossframe-Scripting is not possible when the two frames have different domains -> Security. This means that youtube is trying to reach out to the caller frame for some reason and it's disabled because it would be a cross-domain call.
The better solution is to change the iframe.src to a url on the same domain, but which was actually an html re-direct page to the desired domain. The other domain then showed up in your iframe without any errors.
Another solution could be to use a local file which retrieves the remote content.


File reading error in Parameter Estimation Task.

Hi,
I am following parameter estimation tutorial (https://basico.readthedocs.io/en/latest/notebooks/Parameter_Estimation_Example.html) and I reached to the step 4 where I run
run_parameter_estimation(method='Statistics')

but I get the following error:
ERROR:root:Error while initializing parameter estimation: >ERROR 2022-04-18T09:47:44<
  CFitting (8): Failure reading file '~/../Tutorials/2017-ICSB/MAPKdata.txt'.

I do not have this directory /Tutorials/2017-ICSB/ on my computer. Do I need to provide the path for this file MAPKdata.txt explicitly in run_paramtere_estimation function? I tried to look at the list of arguments it takes but I could not see the file path can be specified. Please suggest what I am missing here?
Thanks

Hasan, that is an "error" in the copasi file I supplied you. This is not a BasiCO bug.
I forgot to remove the absolute path for the data file. I can edit that and send you a corrected file.

Oh ok. Thank. looking forward to receiving it.


Docker container

Fixes #38

Hey @Sarthak027, i have reviewed the code at high level, do the required changes then i will test the code.

Also update the readme file, how to run using docker.


Verify that email isn't shared with another user before updating

email_exists( $email )

v8.0.3


Can you get video previews of calls?

Scenario: Multiple live streams are occurring on different users' channels. On the app's feed, is it possible to show video previews of each call, similar to twitch?

preview video or just picture?

Preferably video, but just a picture updated periodically could do as well

you can join the channel and add render widget to preview remote video. but only one at the same time.

I'd like to fetch previews of multiple channels, going at it one at a time
seems rather inefficient. Is there any other way?
On Sun, Jun 28, 2020, 5:54 PM Arthas<EMAIL_ADDRESS>wrote:

you can join the channel and add render widget to preview remote video.
but only one at the same time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AgoraIO/Flutter-SDK/issues/151#issuecomment-650762932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFRISQZ6JR2GCR4ZNM3K4J3RY5DQJANCNFSM4OJGKT7A
.

the best way is getting preview from CDN.


fix array_random_shuffle

You want to make a PR to Wrangle
Thanks so much :) First, please take a moment to carefully check through
the below items:
Sanity

[ ] I'm aware of the implications of the proposed changes
[ ] Code is PEP8
[ ] I'm making the PR to master

Docs

[ ] Docs are updated
[ ] Docs version is correct (index.html and _coverpage.md)

Tests

[ ] Changes have gone through actual use testing
[ ] All local tests have passed (run ./test.sh in /talos)
[ ] Tests have been updated to reflect the changes

Hello @mikkokotila! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file test_script.py:

Line 81:80: E501 line too long (90 > 79 characters)

In the file wrangle/array/array_random_shuffle.py:

Line 4:60: W291 trailing whitespace
Line 6:1: W293 blank line contains whitespace
Line 34:1: W293 blank line contains whitespace
Line 37:1: W293 blank line contains whitespace
Line 43:1: W293 blank line contains whitespace
Line 45:1: W293 blank line contains whitespace
Line 57:1: W293 blank line contains whitespace
Line 63:1: W293 blank line contains whitespace
Line 65:1: W293 blank line contains whitespace


kube-aws: increase verbosity

#hackday
It would be nice to have status updates while creating the cluster.
"creating a cloud formation stack..."
"configuring TLS..."

+1

Closing this as the kube-aws tool has changed considerably, and specific tool verbosity being discussed here: https://github.com/coreos/coreos-kubernetes/issues/353


Messages V1 Pagination

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
I have added next and prev pagination to the old messages page.
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[x] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@Haarolean, this one is ready for QA

seems not all messages are displayed within topic, there are 103 messages but displayed only 19. therefore pagination is not right. as we corrected the limitation for each page should be 100
pagination.mov

This is an old bug that is not related to the where you navigate to the page from the topic page the url, actually the code does not get updated before the request, once you refresh the page you will see 100 limited element in the messages
But i will see what i can do to fix it , cause the code in that particular is a bit messy. @Haarolean


[LogBox] Add NSWindow based version

Related to #621
Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
LogBox is the preferred way to view warnings/errors in v0.63.0.
Changelog

[macOS] [Added] - NSWindow based version of LogBox
TODO
Still minor things to do, but the meat of the patch can be reviewed.

[ ] Navigation buttons in header don't work yet
[ ] Source-maps seem wrong, but that may just be a RNTester thing that doesn’t need to block this PR

Test Plan

Microsoft Reviewers: Open in CodeFlow

The navigation buttons in the header not responding appears to be due to Image swallowing the event https://github.com/microsoft/react-native-macos/blob/2c46cccdee7b568111a326ecf73f8955c32d68a9/Libraries/LogBox/UI/LogBoxInspectorHeader.js#L107

The issue with the navigation buttons was an actual issue with coordinate translation, which is fixed now 👍

Unsure why I was seeing a source-map issue before, seems to work fine:

@tom-un This should be good to go.


Add confirmation prompt on delete key objects

Launch a confirmation modal dialogue when deleting works, publishers, imprints, contributors, series, or funders.

We'll want to implement this as a generic pure component that takes a message and a callback


[feat] Objects as middleware

Adding support for using objects as middleware
Currently Koa requires middlewares to be functions. To make developing class-based controllers a bit nicer, it would be helpful to also allow objects to be used as middlewares. For example:
const myMiddleware {
  [Symbol.for('koa-middleware-invoke')]: ctx => {

  },
}

koa.use(myMiddleware);

Alternatively, a base class could be used that Koa recognizes via instanceof:
class MyMiddleware extends KoaMiddleware {

  invoke(ctx) {

  }

}

koa.use(new MyMiddleware())

Although I suspect that the symbol approach is closer to today's Javascript meta.
There are of course workarounds possible, but this seems like a pretty low-overhead ergonomic feature. The implementation of .use() can optimize this away:

  use (fn) {
    // This line is new.
    if (Symbol.for('koa-middleware-invoke') in fn) fn = fn[Symbol.for('koa-middleware-invoke')];

    if (typeof fn !== 'function') throw new TypeError('middleware must be a function!')
    debug('use %s', fn._name || fn.name || '-')
    this.middleware.push(fn)
    return this
  }

Happy to provide a PR for this if this is interesting, but thought I would first gauge interest.
Checklist

[X] I have searched through GitHub issues for similar issues.
[X] I have completely read through the README and documentation.

Why no just passing the desired method from an object?

This feature request is for increasing ergonomics/ DX. Especially when dealing with routes there's a fair amount of repetition.
Of course helper functions are possible or as you say just work around this, but I asked because it will result in more elegant code.

Can you provide a reference for this pattern you suggest? My understanding is semantically it makes no difference: there is a method which koa would call. But instead of providing that method directly you suggest we give an object and koa will look for that special method by itself.  Now I can't see how this would make the code nicer or more developer friendly.

A specific example is that I want users to be able to build controllers as such:
class MyController extends Controller {

  get(ctx: Context) {
      /* ... */
  }
}

And I would like users to be able to add this controller using this form:
app.use(new MyController())

My feature request would allow me to define the Controller baseclass in a way that Koa can pick this up. Not having this feature requires me to either ask users to call something like:
app.use((new MyController())->mw())

Or add a helper function
app.use(mw(new MyController())

/**
 * Takes a ResourceController subclass, instantiates it and returns
 * a koa-compatible middleware.
 */
export function mw(cl: typeof ResourceController): Middleware {

  const controller = new cl();
  return controller.dispatch.bind(controller);

}

Because this has to be done for each route/controller, this is kind of an annoying overhead.
Full ResourceController for reference:
/**
 * The ResourceController is a base class for controllers that
 * maps HTTP methods like GET, PUT to class methods like 'get', 'put'.
 */
export class ResourceController {

  constructor() {

    // HEAD fallback. It could be desirable to reimplement HEAD faster, but this is an OK default and just as slow as GET but with fewer bytes sent.
    if ('get' in this && !('head' in this)) {
      (this as any).head = this.get;
    }

  }

  options(ctx: Context) {

    ctx.body = '';
    ctx.set(
      'Allow',
      METHODS.filter(method => method.toLowerCase() in this).join(',')
    );

  }

  dispatch(ctx: Context): void|Promise<void> {

    if (!METHODS.includes(ctx.method)) {
      throw new NotImplemented(`HTTP method not implmented ${ctx.method}`);
    }

    const classMethod = ctx.method.toLowerCase();
    if (typeof (this as any)[classMethod] === 'function') {
      return (this as any)[classMethod](ctx);
    } else {
      throw new MethodNotAllowed(`The ${ctx.method} method is not supported at this endpoint`);
    }

  }

}

Well I would have done it like this:
A global middleware factory:
function ControllerObj(c, ...params) {
  const controllerInstance = new c(...params)

  return function mw(ctx, next) {
    const method = ctx.method.toLowerCase()
    if(typeof controllerInstance[method] !== 'function') {
      ctx.throw(405)
    }
    controllerInstance[method](ctx, next)
  }
}

An controller class:
class ControllerX {
  constructor(aKnob) {
    this.aKnob = aKnob  // Some tweaks for this route
  }
  async get(ctx, next) {
    ctx.status = 200
    ctx.body = this.aKnob
    await next()
  }
  // more methods here...
}

And finally:
app
  .use(ControllerObj(ControllerX, 'desiredResponse'))

My belief is that this is not such a general pattern to be implemented in Koa. A plugin maybe...

Sure, this is subjective. Let's see what the maintainers say.

Sure, let's see what the maintainers say. Your approach doesn't really make a difference in terms of cognitive overhead.

Encapsulating state for middleware can be useful, but also a foot gun IMHO.
This can easily be achievable in user space or as a plugin. and there's nothing prohibiting you from extending Koa and overloading use for this effect. I have actually done this myself in a few production apps.
Sometimes I would just compose an object with Koa and a Router effectively overloading use (through composition and delegation rather than inheritance though), but sometimes if I remember correctly I would just extend koa.Application#use and check for objects.
I am not involved in Koa anymore so whatever I say is my own opinion but following the general design of Koa I would consider this to be bloat and better fitted as a plugin, much like routers are.

Completed?


Deny packages not allowing for version numbers

In the recent release the denied packages code is just doing a split on the package name so it only checks based off the package itself and not the version.
We should have it account for versions and potentially a > check so we can do specific versions above the given one (I don't believe the purl spec defines that)

@Killklli I like the proposal. We need to hash it out more explicitly. In principle I see two things here:

Add support for version numbers when blocking specific packages through deny-package. The scope here is very straightforward.
Add support for version comparisons (greater than, less than, etc.) on package version numbers. I feel this task is much greater in complexity: not all ecosystems use semantic versioning, and some manifest files don't specify a version number at all. For an example, see the version field in the following snippet:

$ gh api -H "Accept: application/vnd.github+json" repos/future-funk/refactored-chainsaw/dependency-graph/compare/ed6ace2b7a13ad8a80f1ae499436c256cf90ebf5...e99997ea27c964ddd84390e0a98a57a9e0afe706
[
  {
    "change_type": "added",
    "manifest": "Gemfile",
    "ecosystem": "rubygems",
    "name": "afterclass",
    "version": ">= 0",
    "package_url": "",
    "license": null,
    "source_repository_url": null,
    "scope": "runtime",
    "vulnerabilities": []
  },

If you want to write a PR for specific versions I'd be happy to help. For version comparisons I think the ask is much bigger and I'd need to read a more fleshed out version of how this would play along the existing code.

Specific versions should be manageable now through the use of PURLs, closing this issue. Please re-open if needed.


[BUG] ERROR: ACCESS DENIED

Platform where the error occurred?: Douyin
The endpoint where the error occurred?: (WEB) /api/hybrid/video_data?url=
Submitted input value?: (any videos or example url video) or https://www.douyin.com/user/MS4wLjABAAAAcMI81XJI-7nHmdmRrdGGe24GTJQe5XbIAPzIrNWfvwpc2r2tNmRwlPOd-lak3c5D?from_tab_name=&modal_id=7354391006353067302
Have you tried again? Yes, the error still exists after X time and other videos url
Have you checked the readme or interface documentation for this project? Yes, and it is very sure that the problem is caused by the program.

Sorry my bad, just use download platform to solve the problem


Always a error when uses main_pipeline

Hi all,
I'm encountering an issue with my .bids data in discover-eeg, but always showed these error.
_Dot indexing is not supported for variables of this type.
Error in plot_badchannels (line 36)
chanlabels = {EEG(1).urchanlocs.labels};
Error in main_pipeline (line 207)
plot_badchannels(params,ALLEEG);_
What could be causing this issue? Thanks for your help!

Problem solved, use fieldtrip's bids convert function, and same matlab version.

Problem solved, use fieldtrip's bids convert function, and same matlab version.


update cluster dashboard

Brief summary of the change made

Are there any other side effects of this change that we should be aware of?
Describe how you tested your changes?

Pull Request checklist
Please confirm you have completed any of the necessary steps below.

[ ] Meaningful Pull Request title and description
[ ] Changes tested as described above
[ ] Added appropriate documentation for the change.
[ ] Created GitHub issues for any relevant followup/future enhancements if appropriate.

Superseded by: https://github.com/EnAccess/micropowermanager/pull/358


ansible-lint: Unset PYTHONPATH in wrapper

Description of changes
Since the update of ruamel.yaml to 0.17.32 (5330b05d9952aad7606d5c0658d65faf1955c659), ansible-lint is broken with the following error, when ran from a nix-shell:
Traceback (most recent call last):
  File "/nix/store/20wbbb8w5d95k23hyf417aqh85qjmzp9-ansible-lint-6.17.1/bin/.ansible-lint-wrapped", line 6, in <module>
    from ansiblelint.__main__ import _run_cli_entrypoint
  File "/nix/store/20wbbb8w5d95k23hyf417aqh85qjmzp9-ansible-lint-6.17.1/lib/python3.10/site-packages/ansiblelint/__main__.py", line 39, in <module>
    from ansiblelint import cli
  File "/nix/store/20wbbb8w5d95k23hyf417aqh85qjmzp9-ansible-lint-6.17.1/lib/python3.10/site-packages/ansiblelint/cli.py", line 29, in <module>
    from ansiblelint.yaml_utils import clean_json
  File "/nix/store/20wbbb8w5d95k23hyf417aqh85qjmzp9-ansible-lint-6.17.1/lib/python3.10/site-packages/ansiblelint/yaml_utils.py", line 15, in <module>
    import ruamel.yaml.events
ModuleNotFoundError: No module named 'ruamel.yaml'

I did some investigation, and it appears to have something to do with different versions of Python namespaces. I'm not very familiar with the Python packaging and module loading process, so that was as far as I got. @tjni has been working on this (see here), so I hope that he understands the problem better than I do. In any case, I found that unsetting the PYTHONPATH environment variable fixes the problem for ansible-lint so this PR does exactly that.
I think a better fix needs to be found in the future, but for now, this fix at least mitigates the issue.
In addition, since an update for ansible-lint was released in the meantime, this PR includes a version bump.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Closed in favor of #252021


App installation failed on iOS - Bundle identifiers must be unique.

Steps to Reproduce
Good evening, first of all I'm a noob on programming.
The problem that I had is not quite reproducible, because that appends only on the iOS part, the Android one solves it or for my perspective handles it better.
I cannot share the app source code (for legal reasons), because I'm a member of a bigger team of from a company and for my review in the code I don't seen the problem in it (its other).
The problem that a have is that when I try to launch the application to the device it shows the error:

This application or a bundle it contains has the same bundle identifier as this application or another bundle that it contains. Bundle identifiers must be unique.

I add already pushed one to the App Store Connect, and when a tried the second time it was rejected because of the error above (that I tried myself to test it on release mode). I already asked the iOS team and the support team, they redirect me to you (flutter HQ team).
I have also an off topic question: - I launch an application on debug mode (actually 2) to an iOS device, and a found that after some time (like some days), if the apps are in the device and unplugged from the android Studio (platform that I use to work) they not even start, go down after trying to display the first screen. The apps that I used for this little experiment were the default app and one that a developed (actually a tutorial).
Logs
[  +30 ms] executing: [/Users/daniel/Development/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +37 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] executing: [/Users/daniel/Development/flutter/] git rev-parse --abbrev-ref HEAD
[  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[        ] executing: [/Users/daniel/Development/flutter/] git ls-remote --get-url origin
[  +10 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] executing: [/Users/daniel/Development/flutter/] git log -n 1 --pretty=format:%H
[  +12 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 5391447fae6209bb21a89e6a5a6583cac1af9b4b
[        ] executing: [/Users/daniel/Development/flutter/] git log -n 1 --pretty=format:%ar
[  +11 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 8 days ago
[        ] executing: [/Users/daniel/Development/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +11 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.0.0-0-g5391447fa
[ +270 ms] executing: /Users/daniel/Library/Android/sdk/platform-tools/adb devices -l
[  +10 ms] Exit code 0 from: /Users/daniel/Library/Android/sdk/platform-tools/adb devices -l
[        ] List of devices attached
           ce061606357a663003     device usb:3145728X product:hero2ltexx model:SM_G935F device:hero2lte transport_id:176
[  +11 ms] executing: idevice_id -h
[  +67 ms] executing: which ideviceinstaller
[   +4 ms] Exit code 0 from: which ideviceinstaller
[        ] /usr/local/bin/ideviceinstaller
[        ] executing: which iproxy
[   +4 ms] Exit code 0 from: which iproxy
[        ] /usr/local/bin/iproxy
[   +4 ms] /usr/bin/xcrun simctl list --json devices
[ +247 ms] More than one device connected; please specify a device with the '-d <deviceId>' flag, or use '-d all' to act on all devices.
[   +7 ms] /Users/daniel/Library/Android/sdk/platform-tools/adb -s ce061606357a663003 shell getprop
[  +79 ms] ro.hardware = samsungexynos8890
[   +4 ms] SM G935F • ce061606357a663003                       • android-arm64 • Android 8.0.0 (API 26)
[   +1 ms] Kingston • 04210186bc41a3571f6a719ead92f49b5f62e88c • ios           • iOS 12.1.1
[  +13 ms] "flutter run" took 664ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:26:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:249:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:379:11)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:335:33)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:326:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:196:27)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:401:21)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:361:19)
<asynchronous suspension>
#20     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:111:29)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:111:11)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:241:18)
#24     run.<anonymous closure> (package:flutter_tools/runner.dart:60:20)
<asynchronous suspension>
#25     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#26     _rootRun (dart:async/zone.dart:1124:13)
#27     _CustomZone.run (dart:async/zone.dart:1021:19)
#28     _runZoned (dart:async/zone.dart:1516:10)
#29     runZoned (dart:async/zone.dart:1463:12)
#30     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#31     runInContext (package:flutter_tools/src/context_runner.dart:43:24)
<asynchronous suspension>
#32     run (package:flutter_tools/runner.dart:51:10)
#33     main (package:flutter_tools/executable.dart:51:9)
<asynchronous suspension>
#34     main (file:///Users/daniel/Development/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#35     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#36     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

No issues found! (ran in 1.5s)

[✓] Flutter (Channel beta, v1.0.0, on Mac OS X 10.14.1 18B75, locale en-PT)
    • Flutter version 1.0.0 at /Users/daniel/Development/flutter
    • Framework revision 5391447fae (8 days ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/daniel/Library/Android/sdk
    • Android NDK at /Users/daniel/Library/Android/sdk/ndk-bundle
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/daniel/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 31.1.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] Connected device (2 available)
    • SM G935F • ce061606357a663003                       • android-arm64 • Android 8.0.0 (API 26)
    • Kingston • 04210186bc41a3571f6a719ead92f49b5f62e88c • ios           • iOS 12.1.1

• No issues found!

I have also an off topic question: - I launch an application on debug mode (actually 2) to an iOS device, and a found that after some time (like some days), if the apps are in the device and unplugged from the android Studio (platform that I use to work) they not even start, go down after trying to display the first screen. The apps that I used for this little experiment were the default app and one that a developed (actually a tutorial).

probably better to create a new issue for that

你们用flutter开发什么类型的应用啊?是直接在生产环境用吗?

你们用flutter开发什么类型的应用啊?是直接在生产环境用吗?
Hi, if the translator is not tricking the answers for that questions are:
1- I'm developing an app with iap purchases included;
2- What you mean by the second question? "Is it used directly in the production environment?".

I get the same issue and I solved it by changing the CFBundleIdentifier in this file :
ios/Flutter/AppFrameworkInfo.plist
I added .app to the flutter BundleId XXX :
<key>CFBundleIdentifier</key> 	<string>XXX.app</string>

I get the same issue and I solved it by changing the CFBundleIdentifier in this file :
ios/Flutter/AppFrameworkInfo.plist
I added .app to the flutter BundleId XXX :
<key>CFBundleIdentifier</key> <string>XXX.app</string>

I get the same issue and I solved it by changing the CFBundleIdentifier in this file :
ios/Flutter/AppFrameworkInfo.plist
I added .app to the flutter BundleId XXX :
<key>CFBundleIdentifier</key> <string>XXX.app</string>

Hi there, have to question:
1º- The "XXX" is my bundle identifier, correct?;
2º- Why the bundle id of the framework needs to be different?.

I'm really not an expert on this but what I understand is : there is a subproject Flutter in the app. And the IOS failed because the two projects have the same bundleId.
In my case, I need my project to have the bundleId that I declare on firebase. That's why I changed the flutter one.

I get the same issue and I solved it by changing the CFBundleIdentifier in this file :
ios/Flutter/AppFrameworkInfo.plist
I added .app to the flutter BundleId XXX :
<key>CFBundleIdentifier</key> <string>XXX.app</string>

Hi there, have to question:
1º- The "XXX" is my bundle identifier, correct?;
2º- Why the bundle id of the framework needs to be different?.

This did not work for me.

@JoseFMP any luck with the issue ?


Linefeed fixer cannot be blacklisted

Hi,
I'm working on Windows with the need to have CRLF EOLs. When running PHP-CS-FIXER, i add the option --fixers=-linefeed, as such:

"C:\php\php.exe" "C:\php7\lib\php-cs-fixer.phar" "fix" "C:(...)\ColumnHydrator.php" "--level=symfony" "--fixers=-linefeed" "--diff" "--ansi" "--no-interaction"

My file gets converted to LF EOL except for the first line! Doesn't seem the wanted behaviour to me.

That's because our other fixers assume the correct linefeed is used when they make modifications (but not otherwise).

Hi @GrahamCampbell,
I'm not sure to understand: in my experience the whole file is changed to LF EOLs, even when the other fixers don't touch anything.
But anyway: is it the desired behaviour, to get fixers other than linefeed to change line endings? That makes it unusable on non-LF workflows...

I'm not sure to understand: in my experience the whole file is changed to LF EOLs, even when the other fixers don't touch anything.

This should not happen as fixers have one task, however;

is it the desired behaviour, to get fixers other than linefeed to change line endings? That

no, but some of the fixer might add linebreaks when needed. Those fixers use \n for linebreaks. Currently PHP-CS-Fixer can not be configured to use \r\n for linebreaks.
Can you provide the version of the PHP-CS-Fixer you are using together with your configuration, command line (with arguments) and PHP version and maybe a small example of file that gets touched the wrong way, with that we can start debugging.

a lot of playing around new lines is made by braces fixer. if you have a lot of fixes from it then that could be the reason why you have whole file changed.
Indeed, we are assuming correct line ending, which in general in PHP world is \n. If you are not following it we have a fixer for you ;)
If you don't want to switch, feel free to contribute to make it configurable.

ping @amorel-ljsl can you provide an example?

Hi @SpacePossum,
We are not using PCF anymore on the current project. However the example is very easy to reproduce, on Windows. If i run any PHP file through the fixers, with the command line given in first post, the whole file becomes LF, except for the first line.
If you absolutely need a file, i can try to make one example for you, by the end of the week.
@keradus : not sure what you mean by "correct line ending" :) line ending is not a language thing, but more of a platform one. And sometimes (rearely), some external factors keep you stuck with \r\n, as it is in our case.

@amorel-ljsl you can retry using the 2.0 release, there you can configure the line ending (i.e \r\n vs. \n) explicitly.
I could not reproduce your issue, so in order to bug hunt your case further we really need an (minimal) code sample showing the issue, the PHP-CS-Fixer version you are using (php-cs-fixer -V), PHP version (php -v) and the version of Windows.

I think this issue is not longer valid on 2.x line.
if it is, create new, clean issue with requested informations.
closing


set the TitleView Width according to device width

Hi Aditya,
Its great code.
I am using this in my project, but one point i am facing problem.
I want to  divide the device width of the available views title , means if there are 3 views so it show equally size not set the text like Green as Greeeeeen  and Red as Reed .

Okay, i' ll add fix width option

Fixed added new propery
_pageControl.iCustomTabWidth =  [[UIScreen mainScreen] bounds].size.width/3;


Upgrade view tests changes

💬 Description
A couple of changes accumulated whilst adding tests for the Upgrade view.

Adds flex direction CSS helper
Changes children proptype on TooltipWrapper to node, as it was throwing errors with certain other render types

🔗 Links
Links that relate to the PR (Trello, Figma etc.)
📹 GIF (optional)
A short GIF of the changes in action.
🚪 Start Points
Where is a good place to start the review? If there are multiple changes it may be worth listing multiple files.
👫 Related PRs (optional)
Any PRs that relate to the changes.
✅ Checklist

[ ] Tests written
[ ] Browser tested
[ ] Added to documentation
[ ] Added to storybook

 Pricing Page App Tests


[Suggestion] sv_pure bypass? (Give me your thoughts)

As i said above^^

Please use the search function. There are atleast 3 issues still open about this.

ik

i just wanted thoughts

not a suggestion


Fix SignatureHelpProviderTests

Current master is broken since @cartermp's commit 50e7a829c5ca46976d62866eed2884498dfbfec7
This is an attempt to fix it, but I'm not sure if the test is broken or the code itself

So what does it mean? Fixing tests or code?

Before:

Looks the same.

Why are "arg0" and "An object to write using format" on different lines? It should be fixed.

@vasily-kirichenko @forki There's something in Roslyn method displays we can't control here - I'm sure we can get them to change it eventually
arg0 is the name of the parameter in the .NET metadata
.method public hidebysig static void  WriteLine(string format,
                                                object arg0) cil managed noinlining
{
  .permissionset linkcheck
             = {class 'System.Security.Permissions.HostProtectionAttribute, mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089' = {property bool 'UI' = bool(true)}}
  // Code size       13 (0xd)
  .maxstack  8
  IL_0000:  call       class System.IO.TextWriter System.Console::get_Out()
  IL_0005:  ldarg.0
  IL_0006:  ldarg.1
  IL_0007:  callvirt   instance void System.IO.TextWriter::WriteLine(string,
                                                                     object)
  IL_000c:  ret
} // end of method Console::WriteLine

@dsyme what I don't like here is that "arg0" and its XML Doc are on different lines, that's all.

ok seems there are more to come. but since I can't compile this it will take some time until I have the tests fixed

ok changed test a bit to actually report all issues.

this should become green now and therefore fix the build on master. @dsyme / @KevinRansom / @cartermp please take a look and merge if you think it's ok

@forki Thanks.  Not sure why this went wrong, but I imagine the document created temporarily by the tests on the server is different than that on my machine when I updated these tests.  That would explain the discrepancy in TextSpans.
I think that first item in the tuple can just be outright ignored.  I don't think that verifying that the correct TextSpan is the same is very meaningful from a test perspective.  The important bit is that the current argument and total number of arguments is accurate.
@dsyme @vasily-kirichenko I don't think that behavior is going to change in Roslyn, or at least not for vs2017 RTM.  To clarify, what this means is that you would be requesting that F# be treated as a special case on signatures to show all parameters for a given method at all times, (something we currently generate in our codebase, but would likely have to pass off to Roslyn) and have Roslyn highlight the current parameter of that set.  I very much disagree that this is the correct thing to do, but there is a discussion at #1910.

@cartermp Right now I think I'm just totally focusing on recovering parity with VS2015 rather than working out what's actually right/wrong :)
I think one key post RTM is to implement other relevant navigation aids (go to generated signature, F1 help etc), and cleanup quick info too.

@dsyme I figured it out; it's entirely on our end and has nothing to do with Roslyn.

Tbh most important right now is green build ;-)
Am 06.12.2016 6:25 nachm. schrieb "Phillip Carter"<EMAIL_ADDRESS>
:

@dsyme https://github.com/dsyme I figured it out; it's entirely on our
end and has nothing to do with Roslyn.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/1949#issuecomment-265213768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNG01TnAN9idTEoWKB5UqLaTNZG4Jks5rFZqRgaJpZM4LFSJp
.

@forki Agreed, this is tangential and not related to this PR

AppVeyor failures don't seem to be an issue.  @KevinRansom can you verify and pull this if it's all good?  This fixes a test in CI that's been going red for unrelated PRs.

Please please merge.


[add-resource] New Plugin/Theme

I would like to add my new plugin/theme to the Grav Repository.
Here are the project details:  https://github.com/Flamenco/grav-plugin-editor

Thanks will get this added soon.

@rhukster Did I do something wrong, or is this still pending?

@rhukster Still not seeing it.  Maybe I have an issue with my versioning?

Ugg.. i never commited it.. should show soon

Thanks Andy.  This is going to be a useful one!


Add option to disable line drawing

This PR adds an option to disable the line drawing between points, so a Line Chart turns into a scatter plot. See #1880 for more details.

Oh, I missed the test :)

+1 to merge as soon as tests pass

Tests are passing now. I initially thought the test would inherit from the global config ;) Don't know if you want a new test case to test if the lines are not being drawn.

@mathiask88 a test covering not drawing the line would be nice if you can add one. If not, it's okay.

@etimberg I added a test. Is that ok? Did not look closely at all tests.

Looks good!


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In b38bafb, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 7722 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in d7e5015.


Remove cypress suppression of uncaught exceptions

Closes: https://issues.redhat.com/browse/RHOAIENG-10715
Closes: https://issues.redhat.com/browse/RHOAIENG-7565
Description

These snippets had been introduced to work around a Patternfly bug with ExpandableSection https://github.com/patternfly/patternfly-react/issues/10410 This has been fixed - removing these suppressions because they can hide other uncaught exceptions.
How Has This Been Tested?

Run Cypress test files modelVersionArchive.cy.ts and registeredModelArchive.cy.ts and check whether they run fine.

Test Impact

Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@manaswinidas it looks like we're still getting the exception - I think we need to upgrade PatternFly to pull in the fix.
According to this PR it was released in<EMAIL_ADDRESS>but we're still on 5.3.3.

good question... looking into it

I'm confused by the test failing on "after each" hook for "Restore from archive version details", I don't see an afterEach in there anywhere

The tests are passing for me locally too... I think maybe there's a rendering race condition and the exception isn't necessarily always thrown. Maybe we can just upgrade PF and make sure it passes and that's sufficient.

@mturley<EMAIL_ADDRESS>is still in pre-release according to npm versions history

/hold
holding this until PatternFly releases 5.4.0 and we can upgrade to that version in this PR. The Jira is blocked until that happens - The PatternFly team says the release is expected today. If there are further delays we'll need to roll over the issue to the next sprint.

Once PF releases and we unblock this, let's make sure to also remove the newly introduced instance of this in https://github.com/opendatahub-io/odh-dashboard/pull/3116/files#diff-cfd373dd2cc4bd02bbf6aa15837b2b82aed88e0ef783079334d738c8b22d6ceaR206-R208

/unhold


Old image of the bit BlazorUI project on the home page of the Platform website

Old image of the bit BlazorUI project on the home page of the Platform website:

the updated image should be something like this (coming from the home page of the bit BlazorUI website):

not planned anymore!


BUG：cogvlm2-llama3-chinese-chat-19B model crushed--Expected all tensors to be on the same device

Describe the bug
Due to network restrictions, I cannot use Xinference to pull models online. I downloaded the model weight of cogvlm2-llama3-chinese-chat-19B to the local computer, and then used Xinference (docker container) to register the model cogvlm2-llama3-chinese-chat-19B to cogvlm2-llama3-chinese-chat-19B-self. After that, I started the custom model cogvlm2-llama3-chinese-chat-19B-self on 4 GPUs. The startup failed, and the following error message was displayed: RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:2 and cuda:3!
To Reproduce
To help us to reproduce this bug, please provide information below:

I use docker image--xprobe/xinference:v0.12.0
Full stack of the error.

Traceback (most recent call last):  File "/opt/conda/lib/python3.10/threading.py", line 1016, in _bootstrap_inner    self.run()  File "/opt/conda/lib/python3.10/threading.py", line 953, in run    self._target(*self._args, **self._kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context    return func(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 1758, in generate    result = self._sample(  File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 2397, in _sample    outputs = self(  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl    return self._call_impl(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl    return forward_call(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/accelerate/hooks.py", line 166, in new_forward    output = module._old_forward(*args, **kwargs)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/modeling_cogvlm.py", line 649, in forward    outputs = self.model(  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl    return self._call_impl(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl    return forward_call(*args, **kwargs)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/modeling_cogvlm.py", line 390, in forward    images_features = self.encode_images(images)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/modeling_cogvlm.py", line 362, in encode_images    images_features = self.vision(images)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl    return self._call_impl(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl    return forward_call(*args, **kwargs)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/visual.py", line 130, in forward    x = self.transformer(x)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl    return self._call_impl(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl    return forward_call(*args, **kwargs)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/visual.py", line 94, in forward    hidden_states = layer_module(hidden_states)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl    return self._call_impl(*args, **kwargs)  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl    return forward_call(*args, **kwargs)  File "/root/.cache/huggingface/modules/transformers_modules/cogvlm2-llama3-chinese-chat-19B/visual.py", line 83, in forward    output = mlp_input + mlp_outputRuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:2 and cuda:3!

reproduce step:
Download the cogvlm2-llama3-chinese-chat-19B model from huggingface to a local directory named /home/llm/image-model/
Run the following command to start the container: docker run -d -v /home/llm/image-model:/root/models -p 9998:9997 --gpus all xprobe/xinference:v0.12.0 xinference-local -H <IP_ADDRESS>
Use the browser to access http://localhost:9998/ui
Click Register Model, select the IMAGE MODEL tab, enter the model name "cogvlm2-llama3-chinese-chat-19B-self" and path "/root/models/cogvlm2-llama3-chinese-chat-19B", and click Register Model.
Launch the model: cogvlm2-llama3-chinese-chat-19B-self
I used dify to link the model that xinference started, and uploaded a picture to ask the question. Error happened:  RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:2 and cuda:3!

Expected behavior
It is hoped that Xinference can perform cogvlm2-llama3-chinese-chat-19B model inference on multiple GPUs.
Additional context
Add any other context about the problem here.

The same!


Web components

🚀 Feature Proposal
Matching elements inside web components.
Motivation
Current way of matching elements (using querySelectorAll does not find any elements that are placed inside a web component. I.e. puppeteer's waitForSelector method works fine.
Example
Example in related article
Pitch
As a user it makes perfect sense to me to use toMatchElement and to expect an element to be found.

We will not go in this direction. expect-puppeteer will probably be deprecated in favor of pptr-testing library.


Setup Instructions

The setup instructions seem to be dated compared to Google's current API platform, I can't seem to find the steps listed.

Feel free to submit a PR to improve them.

Will do!


Profiler fails with KLL sketch enabled for null columns

Describe the bug
When KLL is enabled for profiling to calculate percentile quantiles, if a column is all null values (completeness = 0), the conversion of the quantile percentiles fails from java [''] to python list in the java_list_to_python_list function in scala_utils.
To Reproduce
Steps to reproduce the behavior:

create a data-frame with column_1 defined as a Numeric type
add only null values to column_1
calculate the profile with KLL enabled
Failure:
pydeequ/scala_utils.py", line 101, in <listcomp>  vals = [datatype(i)  for i in java_list[start+1:end].split(',')] ValueError: could not convert string to float:

Expected behavior
Profile should be calculated and percentiles should be None
Proposed Change
Change the behavior so that empty values are handled as None except for string values.
https://github.com/awslabs/python-deequ/pull/11

code to generate the issue:
schema = StructType().add(StructField("numeric_column", LongType()))   df = spark.createDataFrame([{"numeric_column": None}], schema=schema)   ColumnProfilerRunner(self._spark).onData(df).withKLLProfiling().run()

code to generate the issue:
schema = StructType().add(StructField("numeric_column", LongType()))   df = spark.createDataFrame([{"numeric_column": None}], schema=schema)   ColumnProfilerRunner(self._spark).onData(df).withKLLProfiling().run()


Compatibility with SignalLab250-12

Hi, is PyPRL API compartible with RedPitaya SignalLab 250-12?

No, it's not. I am working on a migration, but the natural order of things will be

merge all open pyrpl PR's
migrate pyrpl to use pypga as backend for FPGA design
implement SignalLab 250-12 support in pypga
Pyrpl would now automaticaly support SignalLab 250-12.
This might unfortunately take a while.


1921/deprecate update methods

Ticket: #1921
Issue
There were some random update() methods on the main objects that let you update meta data — but that was about it.
Solution
Deprecate 'em!
Impact
People will get deprecation notices
Considerations
Perhaps one day, a project will come about to unify all of WP's various read/update/delete methodology, but it will not be this one
Testing
Updated the relevant tests to just use WP native functions. Updated one test to watch for the deprecation notices

Coverage decreased (-0.02%) to 95.016% when pulling d99b23b26c8f0b03987e47218e6baea2a1e509f7 on 1921/deprecate_update_methods into 7717418be03fca0cdbd7c27b3ef2a9ed97d46782 on 2.x.

@gchtr this is ready for review. Coverage decreased, but only because those methods are now not counted as covered because they're deprecated

yup, agree with all those! just had to make one tweak so those would match the tests. Mergin'!

@jarednova I think it's a good move that these are getting deprecated. You said:

Perhaps one day, a project will come about to unify all of WP's various read/update/delete methodology, but it will not be this one

Are you imagining Timber picking this up again one day? It could be something we can look at for Lumberjack if not - staring with inserting/updating/deleting posts & meta.


Not all python tests run on presubmits.

/kind bug
Only the SDK tests are running during presubmits.
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version:
Knative Version:
KFServing Version:
Kubeflow version:
Minikube version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

fixed now
/close


Epic issues Api

This library lacks support for Epic issues API. This is available only on Ultimate and Gold editions of GitLab.
I may add a PR to add this API support. Others' contributions are very much welcome too.

@shuklaalok7
I am in the process of doing a release with the TagsApi and will add this API.  I just ask that you test it as I do not have access to the Ultimate version of GitLab.

For testing it, one can simply create any open-source project and GitLab enables, I think, Gold edition features for that.
I can test it, no problem.

@shuklaalok7
Are you looking only for the Epic Issues API or both the Epic Issues AOI and the Epics API?
https://docs.gitlab.com/ee/api/epics.html
https://docs.gitlab.com/ee/api/epic_issues.html
While I normally like to have an API class per GitLab API I'm considering combining these two into one class called EpicsApi.  Your thoughts?

I am looking for both these APIs, I was going to create two separate issues for them.
Keeping separate classes for Epics and Epic issues will help in reducing confusion between already confusing named APIs, so I vote for keeping these two classes separate.

I believe having a single API class actually simplifies and clarifies things.  This class (EpicsApi) would include endpoint methods for both the Epics API and Epic Issues API, and this would be very obvious in the Javadocs.  Three classes would be created:

EpicsApi - The API class as just described
Epic - The model class for objects returned by the GitLab Epics API
EpicIssue - The model class for objects returned by the GitLab Epic Issues API (extends the existing Issue class).

I am also working on some additional documentation that basically is a map of the GitLab API doc pages to the GitLab4J API class that implements that specific GitLab API, will make it clear on what GitLab4J API class to use.  Will have this done in a couple weeks.

@shuklaalok7
I have released 4.8.30 with support for both the Epics API and the Epic Issues API.  I appreciated your input, but decided to go the one API class route. Some of the things that led me that direction was the relatively small size of these, the Epics API web page actually referenced the Epics Issues API, and they both use the same basic endpoints.
I'm going to go ahead and leave this issue open, will allow you to report any bugs found in the implementation.

@shuklaalok7
Haven't heard anything back so I assume this is working for you.  I'm closing the issue, you can always reopen it or create another if you find any problems.


Use RandomAccessInput instead of seeking in Lucene90DocValuesProducer

We use manual seeking and reading instead of random access in this class. That seems just unnecessarily complicated and potentially slower due to the need for updating pointer field in the index input.

Thanks Adrien!

Looks like there was a slowdown on some taxo facets tasks (which use binary doc values to store the taxonomy). OrHighMedDayTaxoFacets, AndHighHighDayTaxoFacets and MedTermDayTaxoFacets had a slowdown with a low p-value. On the other hand, BrowseMonthTaxoFacets went a bit faster (p-value is not so low, but this is the best data point in a long time, which suggests it's not noise). https://benchmarks.mikemccandless.com/2<IP_ADDRESS>.20.19.html
We should not revert, but I'll annotate. I'm curious if someone has ideas on the cause. Also cc @stefanvodita @gsmiller since you have interest in facets.

I dont think this is a real slowdown caused by the commit here. It is more caused by the Hotspot optimizer misinterpreting something. We should get the assembly code from the benchmark and compare them to figure out why it gets worse.
Actually the non-random access modifies global state (moves position), so actually optimizer does a harder job, so the slowdown is very strange.

I was a bit afraid that this might have been caused by missing "prefetch()" implementation, but for MemorySegmentIndexInput also the random access slice uses the correct implementation.
My only idea could be that there's a difference between the inlining decisions for interface RandomAccessInput and the class IndexInput (both implemented by MemorySegmentIndexInput, but the first is using invokeinterface which the latter is using invokevirtual bytecode). This could make a difference here, so we need a dump of which methods were inlined before/after.

I think we simply underestimate the variance luceneutil which results in p-values that are too low. See https://github.com/mikemccand/luceneutil/pull/308 for a suggested fix. The QPS have since recovered from the tiny dip seen here .


[Fix] The card featured-post-card is getting blend with white background in Light mode

Description
In the light mode the card that shows the blog information gets blend with the background (both have same background so it doesn't differentiate as a card). But the card in the dark mode has differentiation it has different color than the backgorund one so it looks good but that feature is not in the light mode.
Current Behavior
The card skeleton needs an different background (light background) that doesn't appear blend to the background, and also need a border around it just like the latest posts cards and then the should be left rounded to make it look good with border.

Proposed Enhancement
There should be a slight different background color of the card and a border around it.

Use Case
This would enhance the user experience and make our UI more flexible and user-friendly.
Blockers
No response
Additional Information/ Attachments
No response

@krishnaacharyaa kindly response/assign this issue...!


Where are official binary packages?

The files stored on sourceforge.net are also source code files. Where are official binary packages stored?

I have solved the problem using NuGet.

This is indeed the preferred solution currently - https://github.com/xianyi/OpenBLAS/wiki/Precompiled-installation-packages - for the reasons given in #1675


Fix trino_cluster example

Current behaviour
Running with errors
Expected behaviour
Should run OK
How to reproduce?
make test
Suggestion(s)/solution(s) [Optional]

Review trino.hcl
Review trino_cluster/

Checklist (after created issue)

[x] Added label(s)
[ ] Added to project
[ ] Added to milestone

Closing, duplicate of #110


Timeseries widget: the scale bar and label in the y-axis (voltage) are missing

Originally part of #18

@lfrank @khl02007
I could use some help designing the y-axis (voltage) label.
Note: the y-axis unit is not always voltage (e.g., whitened or simulated data), so I would not want to hard-code that label in there.
Should the axis be on all channels? Or just one? Where should it appear? Do we put tick marks? Do we want to toggle this on/off?

My main concern is ticks and labeks for the ticks so we know the magnitudes of the values. I don’t think a y axis label is necessary, although in cases where it is known (e.g. data from an NWB timeseries with a units entry) one could use that.
I would always wants ticks and labels, but a toggle can’t hurt if that’s easy to add.
I’m not sure what you mean by all channels, though.

On Jul 19, 2021, at 6:53 AM, Jeremy Magland @.***> wrote:
@lfrank https://github.com/lfrank @khl02007 https://github.com/khl02007
I could use some help designing the y-axis (voltage) label.
Note: the y-axis unit is not always voltage (e.g., whitened or simulated data), so I would not want to hard-code that label in there.
Should the axis be on all channels? Or just one? Where should it appear? Do we put tick marks? Do we want to toggle this on/off?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/magland/sortingview/issues/22#issuecomment-882566918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABV4PSKTF2YHTIUMNMWB5HLTYQU6DANCNFSM5AN2PIJA.

@magland

Note: the y-axis unit is not always voltage (e.g., whitened or simulated data), so I would not want to hard-code that label in there.
When would we need to plot whitened data? or perhaps you're thinking of using the widget for a number of use cases beyond sortingview?

Should the axis be on all channels? Or just one?
All the channels have the same y-scale at the moment, so I think having it on just one would be sufficient

Where should it appear?
doesn't matter too much as long as it (the scale bar) doesn't obscure the data.

Do we put tick marks?
on the axis or on the scale bar? provided we're going with the scale bar and it is of reasonable size, I don't think this matters too much

Do we want to toggle this on/off?
You could implement this feature but seems also OK to just leave it on all the time

This will be resolved by PRs #68 and #69


offline - Wake up not working

I tried it with 2 different microphones (both usb), but the wake up event hasn't been triggered. My Console stuff:
daniel@daniel-8o23dad:~/respeaker_python_library$ sudo python examples/offline_voice_assistant.py
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
INFO:mic:Start detecting

So how can I get that offline example working?

Hi, the logs you posted here are not enough to address the problem, they just seem all the way ok. You might take the following steps to check your audio configuration:

sudo alsamixter - to check your volume configuration
use arecord to record some audio from particular microphone, and check if the captured sound ok

Will close this issue, please open a new issue if you have further questions.