Fix typos for package, encrypted & decrypted in README.md

Description
Typos for the encrypted and decrypted methods on plaintext object. Copy and paste of code showed error
Motivation and Context
Fix minor typos
How Has This Been Tested?
Documentation only update.  Tested via copying and pasting code, and executing to confirm fix.
Checklist:

[x] I have submitted a CLA form
[X ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

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

Looks like the original PR is gone.  I'll incorporate this change manually.  Thanks @oztimpower !


Scroll position resets when delete a file (Video demo)

Explain the bug
when delete a file, scroll position resets
To reproduce

go to any folder that have many files
scroll down
delete any file

logfile
debug.txt
Screenshots
https://user-images.githubusercontent.com/79398439/126982452-cdf1ebd8-575c-4a79-847b-e98ab661a2a6.mp4
System Information

Versión: <IP_ADDRESS>
OS Version: 10.0.22000.100

This issue should be resolved in main.


Allow different HardBreaks settings for documents and comments

GH has different HardBreaks behaviour for markdown comments and documents.
Comments have hard breaks and documents have soft breaks - therefore Gitea's rendering will always be different from GH's if we only provide one setting.
Here we split the setting in to two - one for documents and one for comments and other things.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Unit test panics:

I don't understand why on Earth copying text in a drone log is so 🤬 difficult.

@guillep2k unit tests fixed

make lg-tm work

@lafriks do I need to add warning to the documentation about the changes?

As we will backport it I don't think it's needed as this will set back previous behavior that we made as breaking change in 1.12.0-rc1

make lg-tm work


Add ghcup www, design from rustup

Already uploaded for testing: https://www.haskell.org/ghcup/

Honestly I don't see what it means to say "ghcup is an official Haskell project". Like, haskell.org hosts it now sure, so you could note that. But even ghc isn't an "official Haskell project" -- unlike rust there's no body (including the haskell.org committee) in a position to make such designations :-) Perhaps it could just say "ghcup is hosted by haskell.org".
Also, I visited from a mac and it said "You appear to be running Unix." Which, I guess, isn't exactly wrong, but nonetheless. It would maybe be better to say "Unix or OS X" or the like?
And finally, the "other installation options"  should link to the downloads page, even though it remains a mess. The platform page now just recommends ghcup for linux (and will probably soon do so for os x) so it'll create a link cycle.

It would maybe be better to say "Unix or OS X" or the like?

I find that a bit confusing. It's like guessing :)
The js code is able to detect this, but what is the value of this distinction? It's a unix-like system, we probably have POSIX and that's all we need to know...

I also noticed the page looks funny if JS is disabled in the browser.

The js code is able to detect this, but what is the value of this distinction? It's a unix-like system, we probably have POSIX and that's all we need to know...

Sure its all we need to know, but it would be confusing to many users, who really don't think of OS X as a unix, and hence would be confused by text saying they were running unix, and perhaps think that there was a mistake.

Maybe just mirror Rustup and say "It looks like you’re running macOS, Linux, or another Unix-like OS." (or keep the "You appear to be running" start).

Should be all fixed now.

Also, I visited from a mac and it said "You appear to be running Unix." Which, I guess, isn't exactly wrong

Piece of useless esoterica: from all mentioned OS in the commit, Mac OS is the only one that can be called UNIX® (because it's UNIX® certified™).

@gbaz people have been raising concerns about the visibility of the page https://www.reddit.com/r/haskell/comments/b4kcfg/ghcup_homepage_now_at_haskellorg/ej9karl/?context=3
At least https://www.haskell.org/platform/#linux-generic should probably point to the new homepage now.


To add blog related to data science and machine learning.

Description
To add blog related to machine learning and deep learning for beginer.
Screenshots
No response

I would Love to contribute to this issue.. @AyushJain001


Added create-react-class to support later versions of React. Updated …

…examples to use ES classes

dupe of #61


(psycopg2.OperationalError) FATAL: database "public" does not exist

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.15.0
Expected results
Show the result of SQL
Actual results
(psycopg2.OperationalError) FATAL: database "public" does not exist

Steps to reproduce
access PostgreSQL through SQL Lab,

Does it work if you don't specify the schema?

@xrmx does not work, but preview works sometime

Does it work if you SELECT ... FROM activity instead of public.activity?

it works no matter
SELECT *
FROM public.vintage LIMIT 100

or
SELECT *
FROM vintage LIMIT 100

just if I did not select any schema from let panel.

I can confirm that I'm facing the same issue. If I choose the schema explicitly in the left pane and try to query a table with either
SELECT * FROM <schema_name>.<table_name>
or
SELECT * FROM <table_name>
I get the error
(psycopg2.OperationalError) FATAL: database <schema_name> does not exist
If I don't choose the schema name from the drop down and try to do
SELECT * FROM <schema_name>.<table_name>, everything works fine.

Hello,
+1 - I am having the same issue, running superset in docker.

Is there a full stacktrace from the server logs?

Most likely the issue is around confusion between the database and schema "namespacing" in Postgres. Databases have different semantics in that area on how they name these logical groups (database, schema, owner) and how many levels of them they have, and SQLAlchemy takes a bit of a common denominator approach.

Since we don't use Postgres at Airbnb I'd like for someone to step in and help fix this.

I have similar problem. Can`t deselect schema.

+1 here, getting error regardless of the schema selected and format of the FROM statement.

It's same/duplicated issue with https://github.com/airbnb/superset/issues/1558, and my PR was merged the last couple of days. You can use that feature in the next release.

https://github.com/airbnb/superset/pull/1789

0.17 is out!

The problem continues on 0.17.3

Notice: this issue has been closed because it has been inactive for 381 days. Feel free to comment and request for this issue to be reopened.


Improve documentation for stable ingestion url

The section regarding the ingestion url in these docs:
https://learn.microsoft.com/en-us/azure/azure-monitor/containers/prometheus-remote-write-managed-identity
<INGESTION-URL> | Metrics ingestion endpoint from the Overview page for the Azure Monitor workspace

Is a bit misleading, as the portal will provide an url in format:
https://developmentuk-monitoring-.../streams/Microsoft-PrometheusMetrics/api/v1/write?api-version=2023-04-24
However this recent api-version=2023-04-24 is incompatible with the remote-write configuration in prometheus.
Either the docs should reflect the stable/supported url format. Or the newer API should be fixed to behave correctly.
https://learn.microsoft.com/en-us/azure/azure-monitor/containers/prometheus-remote-write#hitting-your-ingestion-quota-limit
These docs list the supported url format:

The INGESTION-URL uses the following format: https:///dataCollectionRules//streams/Microsoft-PrometheusMetrics/api/v1/write?api-version=2021-11-01-preview

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

ID: 26735545-9efe-5cfe-07df-fc61bf3f84aa
Version Independent ID: 552d907c-c8c1-746d-3308-412eabaf2bcc
Content: Remote-write in Azure Monitor Managed Service for Prometheus using managed identity - Azure Monitor
Content Source: articles/azure-monitor/containers/prometheus-remote-write-managed-identity.md
Service: azure-monitor
Sub-service: containers
GitHub Login: @EdB-MSFT
Microsoft Alias: bwren

@mdhomer
Thanks for your feedback! We will investigate and update as appropriate.

@mdhomer - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can review and update accordingly.

@mdhomer - Can you describe what error are you seeing while using api-version=2023-04-24 ? Also, it would be great if you could share more details about the incompatibility, you are seeing while  using the new  api-version=2023-04-24. Thanks!

#reassign:rakshith210


[Shadowrun 5th Edition (Advanced)] Technomancer Complex Forms are not working properly

Every time you would roll for a complex form, regardless of changes to bonuses, skills, and levels, the complex forms will only roll with a software skill of two [2], ignoring any in-sheet bonuses, and setting the fading value to a flat Fade = [Level] + 0, regardless of whatever changes done. Situational bonuses still change the amount of dice rolled, but anything else is ignored.

While I found an error in the formula I cannot reproduce your errors.
I publish the fix to the formula and then you can try again. If the issue persists I need your values for everything software related, resonance and an example complex form

https://github.com/Roll20/roll20-character-sheets/pull/11676

@Dragonmoy the fix is live

@nmbradley due to no further feedback: this can be closed


library page desktop & mobile

Closes #2, introducing the library page on desktop and (preliminary) mobile.
Notes:

still need to optimize the topics section for mobile, pending designs
The topics are referred to as "research items" in the CMS page document – this is an assumption on my part, since I saw this field already created in the config file. If this field is supposed to manage some other piece of content, lmk and I'll reroute the topics into their own field
this PR also introduces an animation.js file to keep track of framer-motion animation props

@lougroshek changes made:

Restyled a couple sections in accordance with Sasha's redesigns
I initially implemented a slugify function for the labels per your suggestion, but connecting the anchors to the containers ended up triggering the native behavior where the window scrolls the container into view, which feels disruptive. For this reason, I've ditched the hrefs on the labels for now – I think I'm going to use History.pushState() at a later date to place the label into the hash without triggering this behavior.
I pulled in the label you added to the menu
Fixed the reinflation bug you noticed
As for the "na" fields, I'm comfortable handling the frontmatter in these entries in whatever way we'd like – I only placed text in certain fields because they were required in order to publish, and I'm not familiar with how they integrate into the design.

Still TODO:

Sasha introduced a dropdown for the topics on mobile. I'm working on this now and should have it pushed up shortly, but wanted to go ahead and send you what I have in case you need to get this on staging before turning to other work.


protocol: Fix u8 consts

Looks fine to me since we know b'#' will always be the correct value in rust.


ISPN-10275 add memcached TOUCH operation

https://issues.jboss.org/browse/ISPN-10275
This PR will add support for the Memcached TOUCH operation.

test this please

The only other thing I see looking at the document is whether we also need get and touch gat operation as well?

The only other thing I see looking at the document is whether we also need get and touch gat operation as well?

java.lang.UnsupportedOperationException: Get and touch is not supported for ASCII protocol

	at net.spy.memcached.protocol.ascii.AsciiOperationFactory.getAndTouch(AsciiOperationFactory.java:86)
	at net.spy.memcached.MemcachedClient.asyncGetAndTouch(MemcachedClient.java:1510)
	at net.spy.memcached.MemcachedClient.getAndTouch(MemcachedClient.java:1167)
	...

Should I really implement features the used testing library isn't capable of?

We could use xmemcached which does have that API.

sorry, I realize now that we should really be implementing the binary protocol

so can this PR be merged or are there any other changes required?

Merged, thanks !


[bugfix] Abide: dont validate hidden fields

This addresses #8039 where hidden fields can cause error messages to be hidden, making it unclear why a form was not submitted.
It also moves the skipping of [data-abide-ignore] fields to validation-time such that if that property is added or changed with javascript, it will still be respected by Abide.
I welcome feedback and suggestions. Sorry I don't have time to really backfill tests for Abide.

Great, thanks @sdhull.  Nice work.


Profile Stats With Bio Info

This building block addition shows a profile image with stats underneath. You can also show and hide bio information under the stats.

@bryananthonylewis Somehow doesn't look like your commits made it into this branch. Can you push the latest commits to the branch so we can review it? Thanks!

Sorry about that! Looks like the files are uploaded now.

Cool! I'm testing for merge now!

@bryananthonylewis Great Building Block! I made some comments that need to be edited before merge - ping me when they're up and merge it in!

Just for references, this closes #159 on merge!

Thanks @rafibomb ! I made the updates that were requested. Let me know if those look okay to you.

@bryananthonylewis Just a lesson for your future git and github betterment,
Please use semantic names for commit/issues/PRs specially title. The title should describe the changes you made and not what you personally done.
✅   Good:

Changed name to Card Profile Stats.
Fix #xxx - Changed SCSS Variables to match Foundation colors.

❌   Bad:

Apply changes asked by @someone
I fixed #xxx
Here some changes, btw beautiful weather today, isn't it ?

Sorry about that @IamManchanda. I'm learning. will try to keep this in mind for next time.

Man oh Man, No issue, believe me I was in the same situation some time back... and you learn from your mistakes :D

@bryananthonylewis and @IamManchanda  You both rock! And BTW - I put my Pull Requests up for scrutiny all the time. We're all learning together to be better and more efficient. Great work!


Large Types IRGen Pass: bugfixes for large-type returns

radar rdar://problem/28680453
This PR resolves various bugs that were found while testing the new large-type returns support in the large loadable types IRGen pass + adds interesting test cases.

@swift-ci Please smoke test


Fixing the type MediaTrackConstraints so the fields mandatory and opt…

Fixing the type MediaTrackConstraints so the fields mandatory and optional are not longer required as obrigatory.
More details can be found here:
https://linear.app/dailyco/issue/ENG-3201/fixing-the-type-mediatrackconstraints-on-react-native-webrtc

what's the reason for / impact of this -- is it a bug? I think the code does what it says, but I can't review the impact of doing it

The new version of react-native-webrtc, this fields mandatory and optional are legacy support. Now we can define the constraints this way:
{
  video: {
    width: 480,
    height: 640,
    frameRate: 30,
  },
  audio: true,
}

Instead of this way:
{
  video: {
    mandatory: {
      minWidth: 1024,
      minHeight: 768,
      minFrameRate: 10,
    },
    optional: [],
  },
  audio: true,
}

Looks like our TS definition has gotten ahead of DefinitelyTyped's: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-native-webrtc/index.d.ts.
Might be cool "bonus points" to open a PR to update the "semi-official" type definitions there, if they apply to the upstream react-native-webrtc and not just our fork of it!

Agree @kompfner , have created a task so we can remember to do that:
https://linear.app/dailyco/issue/ENG-3425/create-a-pr-to-update-the-type-definitions-for-react-native


How to create a unique lowercase index?

Hi,
How to create a unique lowercase index in schema?

Use the @UniqueConstraint mapping (or equivalent, depending on mapping format)

@Ocramius I know, But I want create index based on lower case for example:
CREATE UNIQUE INDEX lower_case_username ON users ((lower(username)));

That's not supported, since it's a DB-specific feature (indexes on functions applied to columns): use a DB migration.

@Ocramius Thank you.


Improve player profile page

Users can now filter entries by product.
Add dailies to player profile page.

Fixes https://github.com/leonard-thieu/toofz-necrodancer/issues/22

Codecov Report

Merging #19 into master will increase coverage by 0.23%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
+ Coverage   84.83%   85.07%   +0.23%
==========================================
  Files          33       35       +2
  Lines         587      623      +36
  Branches       59       59
==========================================
+ Hits          498      530      +32
- Misses         74       75       +1
- Partials       15       18       +3

Impacted Files
Coverage Δ

...er.WebClient/src/modules/enemies/enemies.module.ts
100% <100%> (ø)
:arrow_up:

...ient/src/modules/leaderboard/leaderboard.module.ts
100% <100%> (ø)
:arrow_up:

...Client/src/modules/pagination/pagination.module.ts
100% <100%> (ø)
:arrow_up:

toofz.NecroDancer.WebClient/src/app.module.ts
95.23% <100%> (ø)
:arrow_up:

...s/player-profile/player-entries-controller-base.ts
100% <100%> (ø)

...Dancer.WebClient/src/modules/items/items.module.ts
100% <100%> (ø)
:arrow_up:

...nt/src/modules/leaderboards/leaderboards.module.ts
100% <100%> (ø)
:arrow_up:

...rc/modules/player-profile/player-profile.module.ts
100% <100%> (ø)
:arrow_up:

...lient/src/modules/toofz-rest-api/toofz-rest-api.ts
77.23% <100%> (+3.16%)
:arrow_up:

.../player-profile/player-daily-entries-controller.ts
100% <100%> (ø)

... and 8 more

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 8568c2b...44cbee9. Read the comment docs.


dvc (data): save tweets  to build database & push to DVC

📖 Describe what you want
This issue must be completed only after issue #75 is completly done.
Run the feature built for issue #75 to download locally tweets from twitter API.
Make sure you have enough place available and your machine works correctly before doing so.
Then push these tweets with DVC to the AWS S3 storage service.
Determine the amount of tweet to request per day and per candidate after consultation with the others members of the project.
You should download tweets for one candidate with the start_date: 7 days ago and end_date: 6 days ago.
The .csv file must have at least this start_date and the last tweet ID in its name, like advised in issue #75, in order to be able to complete the data for this day and candidate later if possible.
This dataset should be reproductible :  you must save somewhere the query sent to the Twitter API, either in the .csv file or in another file dedicated to it. The idea is to be able to publish this dataset on thr Huggingface Hub, and it requires reproductibility.
✔ Definition of done
Tweets for ONE candidate and ONE day in the right amount regarding our request capacity are saved in the data/raw/twitter directory (or data/raw/twitter/week_#x/) and pushed to the DVC remote storage.
The script should suggest the user to perform the commands to add and push the data obtained to the dvc remote.
Every data obtained from the twitter API should be pushed to the dvc remote.
The query used to obtain the tweet must be saved.

It is not enough specific @guillaume-salle. What we want is to run the feature of the script describe in issue #75 with the correct starting point (start_date or tweet ID). So maybe you should evoke that and the script should suggest the user to perfrom the command to do the dvc add/push.

Done in issue #75 .


ocamlPackages.jingoo: 1.4.1 -> 1.4.2

Motivation for this change
https://github.com/tategakibunko/jingoo/releases/tag/v1.4.2
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @ericbmerritt

Result of nixpkgs-review pr 108140 1

1 package built:

ocamlPackages.jingoo

Result of nixpkgs-review pr 108140 1

1 package built:

ocamlPackages.jingoo

Please set useDune2.

done!

Please set useDune2.

done!


How do I download and use this software with my Midi Commander?

Hi guys,
Im completely new to github (got it for this)
Im trying to get Loopy Pro (iOS looping softare) to recognise my Midi Commander through midi learn, the same way it recognizes my other devices. It sounds like if I download and install this software that would work but I cant even see where to begin, if somebody is willing to guide me through getting this midi controller set up so I can use it with Midi Learn im happy to pay them $20 of any cryptocurrency they like.

Hi!
Strange thing, i have read on the net that the midi Commander is recognized from loopy pro🤔
Have you tried with some other software,just to test it?
Do you have the otg cable?

Hi, I ended up returning this pedal and settled on making my own midi controller. I tried and tried to get the pedal to work with LoopyPro and with AUM. I could get AUM to show me that it was detecting an input but it refused to communicate with Midi Learn. I have never had an issue with midi devices and these two apps so I'm fairly convinced its an issue with the way the Midi Commander is set up.

I use it with Loopy Pro.  My setup is:
IPAD < Lightning Adaptor < Camera Adapter < Usb < UMC204HD < midi IN < MidiCommander
It works with this firmware.
I thing MidiCommander usb connection is buggy (it freezes), but MIDI cable works ok.


Delete default port tests

Fixes https://github.com/aspnet/AspNetCore-Internal/issues/2854
These tests are never reliable and fail frequently. We can't rely on binding to a static port, even with the extra double-check we do before running the test. I'd rather just delete them or make them manually ran tests. These scenarios are covered by CTI too.

@anurse you had one alternate proposal to containerize these?

My only question is if we should come up with something to replace these tests before removing them. Maybe CTI testing is enough, but part of the reason we haven't removed these yet is because doing so would likely decrease our motivation to add less/non-flaky replacement tests.

I think the cost-benefit of keeping/replacing this test is fairly high. Let's say we want to spin up containers to verify default port selection. Then we would need to set up infrastructure to run those either manually or automatically. My guess is it would take a week to get that work done. And the benefit is low: CTI covers default port selection well. We also still test IPV4 and IPV6 selection.

Perhaps, but such infrastructure could be used for a lot more than just these tests.

Here's a spicy question: Have these tests ever caught a regression that we wouldn't expect CTI to catch?

Containerizing is a solution but has a non-zero cost (from past experience, docker-related tests can themselves be flaky, plus they wouldn't work on macOS). I don't know that I see a big enough benefit to make it worth the cost of having these tests (assuming we have adequate CTI coverage).

Can we configure them to skip on the CI but to run locally? E.g. [SkipOnCI]. These tests are primarily useful during development to check for refactor regressions.

Alright between:

Delete these tests
Keeping tests and always skipping them on CI (which requires a new attribute)

What do people prefer?

I prefer just skipping on the CI, but I don't feel too strongly either way.

Agreed, skipping on the CI gets rid of the flakyness and still lets us have some refactor coverage.

I disagree but 2 against 1, I won't fight it.

I'm going to make a change to extensions to do a few things:

Move the SkipOnHelix attribute to Extensions
Create a new attribute SkipOnCI
Remove a bunch of copied contents in all tests. Today, all test projects have like 10 extra files that only a few tests need:

This includes the SkipOnHelixAttribute.

Waiting on https://github.com/aspnet/Extensions/pull/2186.


Auto detection of device in same network

Hi,
The auto-detection feature of the Greengrass group is not working for those devices which is in the same network. I think this should at least detect those devices which are in the same network rather than provide the device IP address manually in core connectivity.
Problem: 2
Secondly using the Greengrass SDK I'm not able to attach more than one device in the  Greengrass group. When I'm trying to attach a new device, it overrides the existing device. This should be fixed in SDK.
Problem: 3
Using Greengrass SDK not able to create a stream manager client. Getting below error, I search on the support page but couldn't able to find anything related to this issue.
com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl: Connect failed. Status: UnsupportedProtocolVersioncom.amazonaws.greengrass.streammanager.client.exception.ConnectException: Connect failed
[2020-11-05T14:19:28.584Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.connect(StreamManagerClientImpl.java:173)
[2020-11-05T14:19:28.584Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.(StreamManagerClientImpl.java:91)
[2020-11-05T14:19:28.584Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientFactory.build(StreamManagerClientFactory.java:49)
I hope the team will address my concern about the stability of the Greengrass service.
thanks
regards,
raj

IP auto-detection is a feature which must be enabled. Have you enabled the feature? Please see: https://docs.aws.amazon.com/greengrass/latest/developerguide/gg-core.html#ip-auto-detect
The Greengrass SDK which is provided in this GitHub repository is not used for controlling Greengrass Groups. For that you should use the Greengrass Console or use the AWS SDK. See: https://docs.aws.amazon.com/greengrass/latest/apireference/createdevicedefinitionversion-post.html
The stream manager SDK must be used from within a lambda function which is running on the Greengrass device, and the device must have the stream manager lambda enabled (see: https://docs.aws.amazon.com/greengrass/latest/developerguide/configure-stream-manager.html#check-stream-manager-console).

Hi Mike,
Regarding UnsupportedProtocolVersion the Stream Manager protocol version in greengrass core is 1.1.0. Below you could see this:
[2020-11-06T09:46:53.628Z][ERROR]- (nioEventLoopGroup-3-1) com.amazonaws.iot.greengrass.streammanager.server.protocol.ConnectHandler: Protocol version not supported. RequestId: 8e00fdf1-2a6c-4abe-ad63-53d974cbadf0, ProtocolVersion 1.1.0
and AWS IoT Greengrass SDK is latest one which I download from here https://github.com/aws/aws-greengrass-core-sdk-java
but unfortunately still I'm getting same error.
[2020-11-06T09:46:53.724Z][ERROR]-com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl: Connect failed. Status: UnsupportedProtocolVersioncom.amazonaws.greengrass.streammanager.client.exception.ConnectException: Connect failed
[2020-11-06T09:46:53.724Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.connect(StreamManagerClientImpl.java:173)
[2020-11-06T09:46:53.724Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.(StreamManagerClientImpl.java:91)
[2020-11-06T09:46:53.724Z][ERROR]-	at com.amazonaws.greengrass.streammanager.client.StreamManagerClientFactory.build(StreamManagerClientFactory.java:49)
Could you suggest what else I have need to look into it.
thanks!

Hi Mike,
Regarding UnsupportedProtocolVersion the Stream Manager protocol version in greengrass core is 1.10.0. Below you could see this:
[2020-11-06T09:46:53.628Z][ERROR]- (nioEventLoopGroup-3-1) com.amazonaws.iot.greengrass.streammanager.server.protocol.ConnectHandler: Protocol version not supported. RequestId: 8e00fdf1-2a6c-4abe-ad63-53d974cbadf0, ProtocolVersion 1.1.0
and AWS IoT Greengrass SDK is latest one which I download from here https://github.com/aws/aws-greengrass-core-sdk-java
but unfortunately still I'm getting same error.
[2020-11-06T09:46:53.724Z][ERROR]-com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl: Connect failed. Status: UnsupportedProtocolVersioncom.amazonaws.greengrass.streammanager.client.exception.ConnectException: Connect failed
[2020-11-06T09:46:53.724Z][ERROR]- at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.connect(StreamManagerClientImpl.java:173)
[2020-11-06T09:46:53.724Z][ERROR]- at com.amazonaws.greengrass.streammanager.client.StreamManagerClientImpl.(StreamManagerClientImpl.java:91)
[2020-11-06T09:46:53.724Z][ERROR]- at com.amazonaws.greengrass.streammanager.client.StreamManagerClientFactory.build(StreamManagerClientFactory.java:49)
Could you suggest what else I have need to look into it.
thanks!

Thanks, Mike for your input.


keyDB is going to opensource it's rocksDB support

https://docs.keydb.dev/docs/coming-soon#keydb-flash-support
Support for KeyDB FLASH using the RocksDB engine will become available September 2022

what do you think about that news ?

I never use KeyDB. But from the news, it seems KeyDB is compatible with Redis Commands and data structure and try  to solve the same problem -- extending to disk. So I am glad there are many solutions for the same feature. Actually Redis Lab also support Flash disk but not open sourced (so no free because the feature is for the Enterprise edition of Redis only).
I recommend to try every tools and select the best one for the clients' situation.
By the way, for the RAFT feature, BunnyRedis I coded is another alternative solution (KeyDB and Redis Lab's Reids Enterprise also have the similar solutions).  You  can try it.
Good luck.

Yes keydb is a fork of redis so it's almost 100% compatible.
Thanks for your answer :+1


"notify" parameter missing in "project.py"

I had to add notify to ".temp/tools/project.py"
        try:
            export(
                mcu,
                ide,
                build=options.build,
                src=options.source_dir,
                macros=options.macros,
                project_id=options.program,
                zip_proj=not bool(options.source_dir) or options.zip,
                build_profile=profile,
                app_config=options.app_config,
                export_path=options.build_dir,
                notify=TerminalNotifier(),
                ignore=options.ignore
            )

Without that I get the following error when exporting (personal project path replaced with "."):
Traceback (most recent call last):
  File ".\.temp\tools\project.py", line 424, in <module>
    main()
  File ".\.temp\tools\project.py", line 415, in main
    ignore=options.ignore
  File ".\.temp\tools\project.py", line 145, in export
    notify.info("Using targets from %s" % targets_json)
AttributeError: 'NoneType' object has no attribute 'info'
[mbed] Working path "." (library)
[mbed] Program path "."
[mbed] Exec "C:\Python27\python.exe -u .\.temp\tools\project.py -i gcc_arm -m NUCLEO_F030R8 --source . --profile debug" in "."
[mbed] ERROR: "C:\Python27\python.exe" returned error.
       Code: 1
       Path: "."
       Command: "C:\Python27\python.exe -u .\.temp\tools\project.py -i gcc_arm -m NUCLEO_F030R8 --source . --profile debug"
       Tip: You could retry the last command with "-v" flag for verbose output

Version:
mbed --version
1.8.3

Further potentially usefull information:

This is for an MBED2 project.  mbed.bld is set to https://mbed.org/users/mbed_official/code/mbed/builds/e95d10626187 to resolve the issue of a missing "mbed.h"

Internal Jira reference: https://jira.arm.com/browse/IOTBTOOL-381

It looks like this issue may have already been resolved in later versions of the mbed-cli tooling, but is not in place for the legacy tooling used by mbed-2. Thanks for the report.

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.

Closing this issue demonstrates a major issue with MBED: backward compatibility support.
MBED5 is not compatible with the platform we used, this is why we turned to MBED2.
This is one of the reasons that we dropped MBED.

Hello @mdeweerd , we should strive for backward compatibility as long as we can. If there is a breakage, it should be reported (captured in the release notes and easily identifiable). However, there are cases like this one (I would like to know more how this one got in).

MBED5 is not compatible with the platform we used, this is why we turned to MBED2.

Do you have more specific examples what was not compatible?
This can be reopened as valid bug. More information why it was closed: https://os.mbed.com/blog/entry/Improving-the-management-of-community-in/

I think I found it.
This commit touched the main function and removed notify from export https://github.com/ARMmbed/mbed-os/commit/44030c23d37a15f787a7cc22a820f63223f4b4f4. I can't find a reason for that removal but might be just "a miss" there. as I see notify used in other export functions.
How can we reproduce locally this one ?


Capstone JavaScript: Billions Seasons Review

This project is an implementation of a review application in which the user can like and comment on a given season of a series.
Obs: The series data used in this project is from TV Maze API. For more info use this link. The comments and likes are stored at the Involvement API. For more information follow this link
Additional description of the project and what we applied to this project:

Use JavaScript to make websites dynamic and build basic single-page apps.
Use ES6 syntax.
Use ES6 modules.
Use callbacks and promises.
Use Webpack.
Apply JavaScript best practices and language style guides in code.
Use AAA pattern for unit tests.
Write units tests for a JavaScript app.
Follow Gitflow.
Solve simple git conflicts.
Send and receive data from an API.
Use API documentation.
Understand and use JSON.
Make JavaScript code synchronous.
Perform a code review for a team member.

Built With :robot:

HTML
CSS
JavaScript (ES6)
Webpack

Deployed Preview :computer:
Preview
Video Presentation :clapper:
Video

Thank you, we updated the video as requested.


Buildbot changes needed to run MachSuite executables on zb1

Currently Buildbot runs executables on zb1 with ssh zb1 /mnt/kernel.
MachSuite apps have presented two problems with this approach.

data files need to be copied (they're copied over to buildbot at job submission)
need to log into zb1 and run executable from /mnt because file paths in the executable are relative

It'll be nice to maintain buildbot capability to run jobs without files and with generic names such as sdsoc.

Hi! I agree with item 2—that's an easy fix we can do right now (just cd into the right directory before running). But I don't understand item 1—what's the alternative to copying data files? What does it mean to "maintain buildbot capability to run jobs without files"? If the benchmark doesn't need to ready any files, it doesn't have to… but if it needs input files, I don't see any way around copying them around.

#199 is that aforementioned quick fix, for your reviewing convenience.

But I don't understand item 1—what's the alternative to copying data files? What does it mean to "maintain buildbot capability to run jobs without files"? If the benchmark doesn't need to ready any files, it doesn't have to… but if it needs input files, I don't see any way around copying them around.

Yup, I just meant the change should work when it doesn't need input files. ie. #200 fails in that regard.

#199 allows makefiles to run with data files. #200 allows regular flow to run with data files.


SAKIII-4016 Allow defaults to be set for all content copyrights

https://jira.sakaiproject.org/browse/SAKIII-4016

Verified and merged.


Maven integration

Hi, would it be possible to upload this library to maven central?

see also #31
The issues are related because Gradle is using Maven repositories.

Okay, there are enough people using this now that I should release it properly! I'm too busy right now but will do it as soon as I can.

I have published the library aar file to the central maven repository with coordinates com.davemorrissey.labs:subsampling-scale-image-view:2.2.0. My apps are using a mix of old build systems and SDKs so could someone please confirm everything works as expected?

Pom bug fixed and 2.2.1 is deployed. I've tested this with a new gradle project.

@davemorrissey do you want to mention this in your wiki/readme?

@davemorrissey any updates on sources?

Opened #402 for sources. There's nothing new to release at the moment.


smithy format puts postfix inline comments in the wrong place

smithy format will turn this:
operation Demo {
    input: Unit // No input
    output := {
        foo: String
    }
}

into this:
operation Demo {
    input: Unit

    // No input
    output := {
        foo: String
    }
}

I would expect a trailing comment to adorn the syntactical element it's sharing a line with and not with the element following it.

Possible duplicate of #2279

Correct, closing as a duplicate of #2279


Load SCBE backend on startup and implement the Activate Interface

Load the SCBE backend during the Ubiquity server start up
Add the relevant SCBE config parameters
Implement SCBE backend Activate interface. The Activate should login to SCBE and to validate that the default service is actually available.
Enable default values to few parameters : Port=8440, VerifySSL=true

How to test good path :

configure ubiquity server.conf as here with ScbeConfig tags. (make sure you have the directory mentioned in SpectrumScaleConfig.configPath, yes for now we took the config from this param)
Make sure u have SCBE up and running with one service delegated to the interface, and also configure this service as the default one.

Run ubiquity server and make sure you see "scbe init start" and "scbe init end" in the log file (by default /tmp/ubiquity.log)

Configure the ubiquity DVP(docker volume plugin) conf file (make sure you have the directory /etc/docker/plugins).
make sure to remove the [SpectrumNfsRemoteConfig] tag so it will use the SCBE backend and not SScNFS

Run the ubiquity DVP

Now simulate DVP activation by just trigger this command:
#> curl -X POST http://<IP_ADDRESS>:9000/Plugin.Activate
Verify : you should see in the log file that scbe activation line : "scbe remoteClient: Activate success"

@shay-berman , please take a look at this and let me know what do you think commit. The idea is, if a backend is specified in the activate call, we will activate just the speciefied backend. If the backend is not specified, we will activate all backend.


build: acme.sh 2.9.0 -> 3.0.4

Redo of #1063 with fixes.
Fixes #1035

@pini-gh could you take a look at this PR ?
Also, do you think we should update the dependencies installed inside the image to match those in acme.sh's Dockerfile ?
I guess some of those are needed for some of the DNS integrations, right ?

@pini-gh could you take a look at this PR ?

LGTM.

Also, do you think we should update the dependencies installed inside the image to match those in acme.sh's Dockerfile ?
I guess some of those are needed for some of the DNS integrations, right ?

Yes. We have to trust acme.sh to know its dependencies well.

I added acme.sh missing dependencies except cronie, we really don't want a cron process running inside the container.


CI: remove audit workflow

Coverage remained the same at 69.406% when pulling b80f192ec19063352e419add89d9c2efb15f545c on ci-rm-audit into d87fecb96e94217d5046d2282118274c291544ea on master.


$schema property in additional language files pointing to wrong URL

Expected value :
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.Localization.schema.json",
Actual value in generated app package :
"$schema":"https://developer.microsoft.com/en-us/json-schemas/teams/v1.11/MicrosoftTeams.schema.json"

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

ID: 7da63b6f-15d7-a6dd-82fc-d183afaeb816
Version Independent ID: 82d1ca83-28dd-220e-ab0c-a4833f8f8143
Content: Manage your apps with the Developer Portal - Teams
Content Source: msteams-platform/concepts/build-and-test/teams-developer-portal.md
Product: msteams
GitHub Login: @surbhigupta
Microsoft Alias: surbhigupta

We are looking into this. We will update you.

We tried this at our end and we see the below schema property :
"$schema":"https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.schema.json"
As mentioned in Localize JSON schema reference, value generated in app package is correct only. Its mentioned that Your file must conform to the schema hosted at https://developer.microsoft.com/en-us/json-schemas/teams/v1.8/MicrosoftTeams.Localization.schema.json, but that is not the actual schema value.

You can still upload the manifest to Teams and it works. To verify it you can validate the manifest in the Developer portal/App studio and you wont see this error.


build: drop xwayland option

This is unnecessary because Xwayland logic doesn't bring in new dependencies. We can just compile in our Xwayland-related code when wlroots has been built with Xwayland support.
See this Sway patch: https://github.com/swaywm/sway/pull/8165

@emersion, any reason this PR is not yet merged in master?

Just forgot about it, thanks for the ping (and review)!


[bug]: ReferenceError: config is not defined

turns out the config for jest allows globals and i just wasnt setting any, the config for webpack doesnt support the provide plugin for jest build, which is something to look at on the specific issue


allow coverage instrumentation of multiple files

This PR is a quick hack to enable code coverage on multiple files. It allows you to set the coverage option to:

a string, in which case all source files with an absolute path matching the string will be included in the coverage report.
a regexp, in which case all source files with a path that matches the regexp will be included.
true, in which case only the file specified with the code option will be included in the coverage report.

Hi @bjouhier!
Instead of overloading the coverage option as a string or Regex, do you think it would make more sense to add a new key for files?
While your proposed change provides flexiblility for specifying the coverage files, it wouldn't allow setting the other coverage options, like  dir or reporters.
lib/coverage.js
options = {
    dir: 'coverage',
    reporters: ['lcov', 'json'],
    files: null
};

Not quite as clean, but then the matcher function could be something like this:
matcher = function(file) {
    if (options.coverage.files) {
        if (typeof options.coverage.files === 'string') return file.indexOf(options.coverage) === 0;
        else if (options.coverage.files instanceof RegExp) return options.coverage.test(file);
    }
    return file === options.code.path;
}

An even better solution might utilize pattern globbing, but perhaps as a future enhancement.

@fyockm Hi Drew!!!
That's a good point. I've followed your suggestion to use options.coverage.files and I've also enabled arrays. So you can specify an array of files or regexps.

merged

Thanks @kof

@kof @fyockm I just tried the regexp feature and found out that it is completely broken. Problem is that options are serialized between testrunner and child and JSON does not like regexps!

thats true, do we really need regexp there?

Can you add some tests?

I can manage without regexps. Looked like a cool and easy-to-implement feature but it's only cool.
I'll remove regexps and add tests but I'll do it a bit later.

:+1:


update link to roadmap

The old link responds with a 302 and a location header of /docs/docs/more/roadmap, which does not exist
[old]
https://yew.rs/docs/roadmap
[new]
https://yew.rs/docs/more/roadmap

Oops, thanks for fixing!


consolidateDataPoints sometimes causes ZeroDivisionError in rare cases

When timeRange is lower than series.step, when calculating bestXStep it can cause ZeroDivisionError exception here https://github.com/brutasse/graphite-api/blob/master/graphite_api/render/glyph.py#L1250
For example, in my case timeRange was 21541 seconds, but timeStep for serie was 86400, that caused 'divisor' to be 0 and resulted in exception. It should either be computed as float and casted to int on line 1250, or it should be maxed, as there is only one point to display.

Seems to be Ceres's problem


CPU maxed while song playing and tab is in focus

Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

[x] You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
[x] The issue has not been reported before
[x] This is not a "how to install on Windows" or "why is my npm messed up" question
[x] You're a cool person

All checked? Now also make sure your issue

[x] Is associated with a version. Or better yet, a commit.
[x] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
[] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
[x] Is in English, 因为我不说中文。

So I recently reinstalled Koel from scratch. This seemed to have fixed the errors I had before.
However something that has been constant across all browsers and versions of Koel has been the high cpu usage while the tab is in focus. Any time I have the tab open, and am playing a song my CPU gets pinned at 60%-100%.
Nothing is displayed in the console, but doing my best to inspect, it seems to be something connected with the GPU and "update layer tree" being constantly called. My bets is on something connected to updating the player progress.
Any help on this would be appreciated.

Can you share how long it takes to max the CPU? How many songs, roughly? Thanks.

It happens from the first song, within I would say 10-20 seconds.
Looking more carefully, CPU usage from the browser hovers around 60% (on my ~2015 Macbook Pro) while tab is in focus, dropping to  less than 10% when the tab is not in focus. And less than 3% when koel is not open.
Other music sites such as spotify or soundcloud don't tend to have anywhere near this impact, so I doubt it has anything to do with audio playback

I'm not familiar with this problem tbh – never heard or seen before. What
browser/version, and not less important, do you have any funny addons
installed?
On Tue, Nov 15, 2016 at 2:04 AM, Porco-Rosso<EMAIL_ADDRESS>wrote:

It happens from the first song, within I would say 10-20 seconds.
Looking more carefully, CPU usage from the browser hovers around 60% (on
my ~2015 Macbook Pro) while tab is in focus, dropping to less than 10% when
the tab is not in focus. And less than 3% when koel is not open.
Other music sites such as spotify or soundcloud don't tend to have
anywhere near this impact, so I doubt it has anything to do with audio
playback
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/481#issuecomment-260411971, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0i09r7aB2_sXK3BFx2WFHGbcoWpXks5q-KKTgaJpZM4KwcCi
.

This issue happens for chrome and Vivaldi, Safari is less prone but usage still hovers around 25%
It might be an isolated issue, but I thought I would raise it anyway, incase its a common to others.
Some simple changes might result in better performance. I'll try to see if I can pin it down to something more specific.

This is fixed in my fork
@phanan This is due to the song-bar animation. Please check this commit
Basically, CSS animation takes too much CPU (even when very small) because they cause a complete redraw. Using a GIF file instead allows the browser to only replace the part that's modified, and it's invisible to the user, dropping the CPU usage from 30% to ~1,5% for me.
Since the animation is just eye-candy, it's not worth burning CPU for this.

@X-Ryl669 See what I have for months in my Koel todo list ;)

Do you have a transparent background gif though? That's what I fail to create.
And thanks for the comment/offer of course!

Gave it a shot.

Thanks, @Porco-Rosso, but the bars don't fade or transform as softly as the CSS version (especially if you notice that last one to the right).

@Porco-Rosso By the way, can you try adding transform: translateZ(0) into .bar like below and see if the CPU goes down?

@phanan
I made the gif very quickly with an online tool. Maybe if I take the time to make one properly, It will look nicer.
Adding transform: translateZ(0) doesn't seem to help.

Put my poor GIF editing skill to test – better contribution for the animation welcome!

GIF only allow a single color out of 256 to be transparent. Since the initial animation is using alpha, that can not work well. That's why I've made the animation with the "official" background color instead (and also, without transparency, it takes less CPU since no blending is required by the browser).
The best would have been APNG or WebP, but it's either Gecko either Webkit and I'm not sure for Edge support.


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 1265 ms

Resolved: Bofrost.fr performance has improved in d498366 after 27 minutes.


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
minor
8.15.16 -> 8.16.2

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.19.8 -> 1.19.9

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.16.2
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#792) (9e09d12)

v8.16.1
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v1.19.9 (#804) (f7c0465)

v8.16.0
Compare Source
Features

adds the ability to pass CBR rules in DA. It adds a new variable instance_cbr_rules in DA variables. (#805) (6ca6516)

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.19.9
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/event-notifications/ibm to v1.15.8 (#260) (60b2496)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline


Support LLVM Mainline

I am using llvm 5.0.0svn and enabled the LLVM flag in make/config.mk
but it gives this error.
src/codegen/llvm/llvm_common.cc: In function ‘llvm::TargetMachine* tvm::codegen::GetLLVMTargetMachine(const string&, bool)’:
src/codegen/llvm/llvm_common.cc:100:7: error: ‘class llvm::TargetOptions’ has no member named ‘LessPreciseFPMADOption’
   opt.LessPreciseFPMADOption = true;

I wasn't able to find LessPreciseFPMADOption in TargetOptions.h
I think they removed this for later llvm
<EMAIL_ADDRESS>

You are right, we need to add support for mainline llvm. For now please use llvm4.0

Should be fixed by #356

got this issue when building directly using LLVM 6.0 on my local machine. How to fix it, thanks!

PLease use the latest code from master, which should already resolved this issue


TOC not converted for 2017-08-01-convert-to-xen

In the web page, docs/home/system-builds/clifton/2017-08-01-convert-to-xen.html, the journal scroll bar is identified as:

    2016-09-07 1 Build VM

    2020-01-09 Install Oracle Client

This snippet is not being converted at all.

I managed to bypass the issue by editing the affected pages by adding style="display:grid" to the unadorned DIV tags that enclose the journal scroll bars.


next: record save (part 1)

connect #708
require #719
This PR is mainly about moving code from skydb to record gear with some small refactoring to make it compile successfully.

Let me rebase first, because the sqlbuilder has some update, auth gear should not be working.


Module not found error can't resolve 'ws' in puppeteer-core/lib

Puppeteer version: 1.9.0
Platform / OS version: Oracle Linux 7
Node.js version: 8.11.4

What steps will reproduce the problem?
const puppeteer = require("puppeteer-core");
    (async () => {
      const browser = await puppeteer.launch({
        executablePath: '../../chrome/chrome'
      });
      const page = await browser.newPage();
      await page.goto(DashboardConstants.LANDING_PAGE_PATH + "&embed=true");
      await page.pdf({path: "example.pdf", fullPage: true, format: "A4"});

      await browser.close();
    })();
  }

git clone kibana
git checkout v6.4.2
add puppeteer-core in package.json
download chrome and extract at src/core_plugins/kibana/
edit src/core_plugins/kibana/public/dashboard/dashboard_app.js with code

What is the expected result?
I should Pass and kibana will be running
What happens instead?
I got Module not found error message.
Error Message:
error  [05:44:03.811] [fatal] Error: Optimizations failure.
8270 modules
ERROR in ./node_modules/puppeteer-core/lib/WebSocketTransport.js
Module not found: Error: Can't resolve 'ws' in '/home/ELK/kibana-test/kibana/node_modules/puppeteer-core/lib'

at FsOptimizer.failedStatsToError (/home/ELK/kibana-test/kibana/src/optimize/base_optimizer.js:429:17)
at compiler.run (/home/ELK/kibana-test/kibana/src/optimize/fs_optimizer.js:36:26)
at onCompiled (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/Compiler.js:241:12)
at applyPluginsAsync.err (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/Compiler.js:514:14)
at next (/home/ELK/kibana-test/kibana/node_modules/tapable/lib/Tapable.js:202:11)
at Compiler.<anonymous> (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/CachePlugin.js:78:5)
at Compiler.applyPluginsAsyncSeries (/home/ELK/kibana-test/kibana/node_modules/tapable/lib/Tapable.js:206:13)
at compilation.seal.err (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/Compiler.js:511:11)
at Compilation.applyPluginsAsyncSeries (/home/ELK/kibana-test/kibana/node_modules/tapable/lib/Tapable.js:195:46)
at self.applyPluginsAsync.err (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/Compilation.js:671:19)
at Compilation.applyPluginsAsyncSeries (/home/ELK/kibana-test/kibana/node_modules/tapable/lib/Tapable.js:195:46)
at self.applyPluginsAsync.err (/home/ELK/kibana-test/kibana/node_modules/webpack/lib/Compilation.js:662:11)
at next (/home/ELK/kibana-test/kibana/node_modules/tapable/lib/Tapable.js:202:11)
at /home/ELK/kibana-test/kibana/node_modules/uglifyjs-webpack-plugin/dist/index.js:282:11
at step (/home/ELK/kibana-test/kibana/node_modules/uglifyjs-webpack-plugin/dist/uglify/index.js:90:11)
at done (/home/ELK/kibana-test/kibana/node_modules/uglifyjs-webpack-plugin/dist/uglify/index.js:99:22)
at /home/ELK/kibana-test/kibana/node_modules/uglifyjs-webpack-plugin/dist/uglify/index.js:105:15
at /home/ELK/kibana-test/kibana/node_modules/worker-farm/lib/farm.js:191:19
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)

Kibana looks like they have quite an extensive dependency system on top of just package.json. I'd file the issue there. puppeteer-core definitely depends on ws and it should be installed when you add it.

I am having the same issue,
But I am not sure I understand what the fix was?
I ran this, but it did not change anything.
npm install --save ws
What was done to solve the OP problem?

@AirborneEagle this seems to be a downstream issue, please file a bug to kibana

I am confused. I am not using Kibana.
I am using puppeteer in my own application.
More specifically I am using pdf-puppeteer.
https://github.com/westmonroe/pdf-puppeteer#readme

Did this ever get resolved?
I am getting the same error, either if I use puppeteer  or puppeteer-core
I am using inside Electron if that makes any difference but it shouldn't.
Help ?

Did this ever get resolved?
I am getting the same error, either if I use puppeteer or puppeteer-core
I am using inside Electron if that makes any difference but it shouldn't.
Help ?

It happened to me when I accidentally tried to ran puppeteer from inside a browser code.
If that's your case by any chance.

@tomermes  Yea it's similar. Electron acts like a browser in many ways, because it uses Chromium etc under the hood.
Tried looking around and it seems that you can not use Puppeteer inside Electron :disappointed:

Tried looking around and it seems that you can not use Puppeteer inside Electron

@AnthoniG Electron has a lot of powerful APIs on its own. Why would you want to?

I am getting the same error while compiling.
ERROR in ./node_modules/puppeteer/lib/WebSocketTransport.js
Module not found: Error: Can't resolve 'ws' in 'c:...\project\node_modules\puppeteer\lib'
How to fix this? I checked the path, it exist.

@aslushnikov Electron is very powerful yes. However in order to automate scraping simple websites I have to use IPC and it gets very messy very quickly.
Using puppeteer sandbox I could do it in a few less lines and there was no messing about with IPC at all. So having this inside Electron, or if there's anything similar you might now, would be absolutely great.

I am getting the same error while compiling.
ERROR in ./node_modules/puppeteer/lib/WebSocketTransport.js
Module not found: Error: Can't resolve 'ws' in 'c:\...\project\node_modules\puppeteer\lib'

How to fix this? I checked the path, it exist.

I also tried the same bug when i used to webpack it does not work for me

Having the same trouble. I want to run puppeteer in the context of the electron. So when I run script with pupeeter scraping like node test.js its working. But when I require it inside the electron app to be able to run this script on button click from within electron app I get
./node_modules/puppeteer-core/lib/WebSocketTransport.js
Module not found: Can't resolve 'ws' in .....

Guys, if you're attempting to use it from the create-react-app bundle, then it's not going to work.
According to their npm page:
https://www.npmjs.com/package/ws
Note:

This module does not work in the browser. The client in the docs is a reference to a back end with the role of a client in the WebSocket communication. Browser clients must use the native WebSocket object. To make the same code work seamlessly on Node.js and the browser, you can use one of the many wrappers available on npm, like isomorphic-ws.

Also, for bundling Puppeteer for browser use, see https://github.com/GoogleChrome/puppeteer/blob/master/utils/browser/README.md

For me, this happened when bundling with webpack, intending the bundle to be used in node.  The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

@dfoverdx +1 for your solution. I was using webpack too (it's not a web application tho, it's just running on node) and it definitely worked for me.
My initial error output was as follows:
$ webpack && node dist/bundle.js
Hash: 1b2fd47f36807b1b273d
Version: webpack 4.38.0
Time: 1573ms
Built at: 07/28/2019 10:10:40 PM
    Asset      Size  Chunks             Chunk Names
bundle.js  1.53 MiB    main  [emitted]  main
Entrypoint main = bundle.js
[0] fs (ignored) 15 bytes {main} [built]
[1] ./BrowserFetcher (ignored) 15 bytes {main} [built]
[2] util (ignored) 15 bytes {main} [built]
[3] util (ignored) 15 bytes {main} [built]
[4] rimraf (ignored) 15 bytes {main} [built]
[5] child_process (ignored) 15 bytes {main} [built]
[6] readline (ignored) 15 bytes {main} [built]
[7] ./node6/lib/Puppeteer (ignored) 15 bytes {main} [built]
[./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {main} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {main} [built]
[./src/index.ts] 3.25 KiB {main} [built]
    + 78 hidden modules

ERROR in ./node_modules/puppeteer/lib/WebSocketTransport.js
Module not found: Error: Can't resolve 'ws' in '/Users/jm/Documents/Joel/scraper/node_modules/puppeteer/lib'
 @ ./node_modules/puppeteer/lib/WebSocketTransport.js 16:18-31
 @ ./node_modules/puppeteer/lib/Launcher.js
 @ ./node_modules/puppeteer/lib/Puppeteer.js
 @ ./node_modules/puppeteer/index.js
 @ ./src/index.ts
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

But when I just added
externals: {
        puppeteer: 'require("puppeteer")',
        // ...
},

to webpack config, it worked like a charm:
$ webpack && node dist/bundle.js
Hash: 1bd4c72ee57858351a97
Version: webpack 4.38.0
Time: 1117ms
Built at: 07/28/2019 10:26:41 PM
    Asset      Size  Chunks             Chunk Names
bundle.js  17.7 KiB    main  [emitted]  main
Entrypoint main = bundle.js
[./src/index.ts] 3.25 KiB {main} [built]
[puppeteer] external "require(\"puppeteer\")" 42 bytes {main} [built]
✨  Done in 5.34s.

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

Can anyone tell me where to add this config?

@shubuu97
Inside webpack.config.js. Here's my config as an example:

const path = require('path');

module.exports = {
  entry: './src/index.ts',
  devtool: 'inline-source-map',
  mode: 'development',
  // the webpack config just works
  // SEE https://github.com/webpack/webpack/issues/1599
  target: 'node',
  node: {
    __dirname: false,
    __filename: false,
  },
  module: {
    rules: [
      {
        test: /\.tsx?$/,
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        test: /\.ts$/,
        loader: 'tslint-loader',
        enforce: 'pre',
        options: {
          fix: true,
          tsConfigFile: 'tsconfig.json',
        },
      },
    ],
  },
  resolve: {
    extensions: ['.tsx', '.ts', '.js'],
  },
  output: {
    filename: 'bundle.js',
    path: path.resolve(__dirname, 'dist'),
  },
  externals: {
    puppeteer: 'require("puppeteer")',
    fs: 'require("fs")',
  },
};

Do we need to do anything else after adding this because i'm still facing the same error

i got an error we require is not defined

i got an error we require is not defined

@kalimuthu123 what environment are you running it in?  My solution was for use in Node.  Browsers would not have require defined.
I know I saw documentation once for running it in the browser, but I can't seem to find it now.  Since you don't need to download Chromium for use in the browser, you should use puppeteer-core.

@dfoverdx I followed the guide for building puppeteer-web.js
I have this code inside background.js file
const puppeteer = require('puppeteer');
console.log(puppeteer);

I am getting
Uncaught ReferenceError: puppeteer is not defined

@dfoverdx I followed the guide for building puppeteer-web.js
I have this code inside background.js file
const puppeteer = require('puppeteer');
console.log(puppeteer);

I am getting
Uncaught ReferenceError: puppeteer is not defined

Do you install puppeteer? It is ok which I test from Repl.it .

这个是webpack include 的问题，可以把test文件写到src外面，并修复package.js 的jest配置项即可

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

+1 for your solution
save my life

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

it's helpful for me. Thanks for u.

how do i fix this problem if Im using react-native?

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
     The trick was to set puppeteer as an external.
const config = {
// ...
externals: {
puppeteer: 'require("puppeteer")',
// ...

Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/issues/3466#issuecomment-723806667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARGBR2JXFKRDXIJMDR4LUN3SO6H5DANCNFSM4GAE743Q
.

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.

Can anyone tell me where to add this config?

For me, this happened when bundling with webpack, intending the bundle to be used in node. The trick was to set puppeteer as an external.
const config = {
    // ...
    externals: {
        puppeteer: 'require("puppeteer")',
        // ...
    },
};

Wrapping it in require() is important because puppeteer doesn't have a global export like jQuery and React do.
after using this config， web throw an error

@tomermes Yea it's similar. Electron acts like a browser in many ways, because it uses Chromium etc under the hood.
Tried looking around and it seems that you can not use Puppeteer inside Electron 😞

Each Electron app has a single main process, which acts as the application's entry point.
The main process runs in a Node. js environment, meaning it has the ability to require modules and use all of Node. js APIs.
If scripts run in electron main process, it's a nodejs environment not browser enivronment,can use fs API etc..., but why still thow this error ?
ws does not work in the browser. Browser clients must use the native WebSocket object


Refactor IntervalData.select_by_time() by using Iterators

@DaniBodor This is my final attempt at making this look good and be readable. The items() method was something I had wanted to look at anyway. It takes care of zipping the intervals and values. The filtering is in this case done by an iterator that yields interval-value pairs that are (partly) within the selected interval.
We've tried to come up with 4 different ways now. I think I like the implementation in #168 best.

We've tried to come up with 4 different ways now. I think I like the implementation in #168 best.

😅
I genuinely think any of them is fine. My favorite is still 0c78723, but at this point it really feels like its down to personal preferences, so go ahead with whichever you like best.


Improve TryExamples customization

Closes #122, #127
This PR updates TryExamplesDirective to use the standard method of allowing custom css in Sphinx to customize the buttons as suggested by Carreau here. It also adds customization of min_height to the config file try_examples.json so that the minimum height can bet changed at runtime. An option has been given to the directive to set the specific height of the iframe container for the embedded notebook and the min_height option has been removed. The specific height overrides the minimum height set in try_examples.json. I've also attempted to improve the documentation, and have added an example_class option to the directive which can be targeted in custom css as suggested by Carreau.

Ok, let's get that in. I'll open an issue to think about validating the height and example_class

Thanks @Carreau!


.NET 4.6 build

Needed for #2857

Needed for #2857

It is more a "nice to have" / "should have" than a "must have".

Instead of net46, then it could be net472 or net48. They add support for portable-pdb, that reduces size of pdb-file to 0.2 MB (Instead of 2.5 MB)
Would be great if there was a netframework version that included the optimizations for concurrentqueue, that have been added to NetStandard2.0

Would be great if there was a netframework version that included the optimizations for concurrentqueue, that have been added to NetStandard2.0

Any Idea if this has implemented recently?

Any Idea if this has implemented recently?

Nope apparently too difficult. At least not included for net48


Some pick 2 cards are broken

e.g.: https://github.com/ircah/irc-against-humanity/blob/master/irc-against-humanity.json#L29
This card is obviously a pick 2 card, but the bot only lets you pick one.

That's because the bot doesn't (yet) infer the number of picks from the number of %s. To do that, we should add an optional end marker or something so that _____ and _____ isn't shown for cards like What's the next superhero/sidekick duo?.

Found 3 broken cards in the IRC Against Humanity card pack so far:
29:     {"text": "I've never seen %s and %s in the same room. Don't wanna jump to conclusions but..."},
30:     {"text": "I've always prefered %s over %s."},
34:     {"text": "%s can't melt %s."}

Fixed in f26ba5c (irc-against-humanity@a74f4f3). Keeping open in case I find issues with the other packs.

No issues in the other card packs as far as I can tell.


Add configuration for emergency restart key combination

Win+Space conflicts with Windows PowerToys run-dialogue hotkey.

Oh, I see. Thanks for the heads-up, I will do that for today's release.
You can manually remove/change it in the meantime by editing these lines at the very end of modules\hotkeys.ahk:
RWin & Space::
LWin & Space::
Reload
ExitApp

You're awesome! Thanks! :)

v1.54.4 is now live and includes customization of that hotkey-combination. I'll leave this thread open for now, in case something else comes up.


Workaround F1 2020 artifact bug.

This PR is an attempt to fix the artifacts in F1 2020. While developing it I was not aware of the TGSM barrier workaround, and I basically discovered the same trick independently. However, the TGSM barrier workaround as it is currently implemented in DXVK does not completely fix the issue, although it goes really close, so I would like to propose my solution as well. My current patch is definitely not ready for inclusion, so I am writing to know from DXVK developers their opinion on accepting a more complete solution for the F1 shader bugs.
Context: what is the problem with the buggy shaders
I did this analysis on F1 2020; I guess the same is happening for earlier versions of F1, but I am not sure. A compute shader used to preprocess lighting divides the scene into a number of 16x16 tiles, and would like to compute for each tile the minumum (and maximum, but let us focus on the minimum) of an array of 64 values (which happen to be depth values for that tile). A thread group is spawned for each tile, and 64 threads are spawned in each thread group. In the interesting section, the 64 threads are executing along the lines of this pseudo-code:
float x[64];    // the array for which we want to compute the minimum, which is in TGSM
if (thread_id < 32) {
    x[thread_id] = min(x[thread_id], x[thread_id+32]);
    x[thread_id] = min(x[thread_id], x[thread_id+16]);
    x[thread_id] = min(x[thread_id], x[thread_id+8]);
    x[thread_id] = min(x[thread_id], x[thread_id+4]);
    x[thread_id] = min(x[thread_id], x[thread_id+2]);
    x[thread_id] = min(x[thread_id], x[thread_id+1]);
}
float minimum = x[0];    // this is the result

This code is correct as long as the seven lines inside the if block are executed in lockstep and all writes are immediately visible to other threads, which is not enforced by the code. I don't know why it works with D3D11, but clearly it does not with Vulkan.
Why the current solution does not completely fix the problem
The current solution simply causes a memory barrier to be inserted between the seven lines inside the if block in my pseudo-code, generating this pseudo-code:
float x[64];    // the array for which we want to compute the minimum, which is in TGSM
if (thread_id < 32) {
    x[thread_id] = min(x[thread_id], x[thread_id+32]);
    memory_barrier();
    x[thread_id] = min(x[thread_id], x[thread_id+16]);
    memory_barrier();
    x[thread_id] = min(x[thread_id], x[thread_id+8]);
    memory_barrier();
    x[thread_id] = min(x[thread_id], x[thread_id+4]);
    memory_barrier();
    x[thread_id] = min(x[thread_id], x[thread_id+2]);
    memory_barrier();
    x[thread_id] = min(x[thread_id], x[thread_id+1]);
    memory_barrier();
}
float minimum = x[0];    // this is the result

This clearly helps a lot, but doesn't completely fix the problem, because, since they are not control barriers, a thread might be reading for the following line while another hasn't even issued to write for the previous line. So, even if writes are assumed to be immediately visible, the more advanced thread will miss the read. What we really need is a memory and control barrier between each line in the if block.
Unfortunately we cannot just change the memory barriers in control barriers, because control barriers cannot be inserted inside dynamic control flow.
The problem here is not just theoretical: I can still see some artifacts even with the TGSM barrier workaround enable. Sure, they are much much fewer and much much smaller, but still there they are (on my Intel iGPU I can see a few pixels worth of artifact every ~10 seconds).
My solution
My solutions attempts to completely tackle the problem (and I couldn't observe any artifacts with it) by putting actual control barriers in the code and modifying control flow so that the resulting code is legal. In practice, the code above is changed to this:
float x[64];    // the array for which we want to compute the minimum, which is in TGSM
int condition = thread_id < 32;
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+32]);
}
memory_and_control_barrier();
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+16]);
}
memory_and_control_barrier();
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+8]);
}
memory_and_control_barrier();
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+4]);
}
memory_and_control_barrier();
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+2]);
}
memory_and_control_barrier();
if (condition) {
    x[thread_id] = min(x[thread_id], x[thread_id+1]);
}
memory_and_control_barrier();
float minimum = x[0];    // this is the result

This should be correct both theoretically and practically. It is also very complicated, unfortunately, because it has to track at least to some degree the flow of the shader code. Also, for the moment it works by patching the DXBC code, not the SPIR-V code, hijacking the DXBC decoder in a very unclean way.
So the final question to DXVK authors is this: could you give me some suggestion on how to rework this patch in a way that can be accepted in DXVK? The hard part IMHO is how to manage the control flow: does DXVK have any facility to help with that?

Which GPU is this a problem on? All current Nvidia and AMD GPUs have a subgroup size of at least 32, so control barriers should not be needed.
Ultimately this is still a game bug though and I'd rather not introduce any of this disgusting control flow hackery. DXVK does not have any way to deal with this properly.

Which GPU is this a problem on? All current Nvidia and AMD GPUs have a subgroup size of at least 32, so control barriers should not be needed.
Ultimately this is still a game bug though and I'd rather not introduce any of this disgusting control flow hackery. DXVK does not have any way to deal with this properly.

Yes, I totally agree that they should fix their shaders, but I have no leverage for that. Though I also understand you're not willing to include such a patch, my only hope was that there was some better way to write this I was not aware of, and apparently there is not. Fortunately the current TGSM barrier workaround is close enough.

Yes, I totally agree that they should fix their shaders, but I have no leverage for that. Though I also understand you're not willing to include such a patch, my only hope was that there was some better way to write this I was not aware of, and apparently there is not. Fortunately the current TGSM barrier workaround is close enough.

Can you test this branch with the game and see if that resolves the artifacts?
If not, then in addition to forcing the subgroup size, we may need to introduce control barriers that operate on the Subgroup scope, which should be allowed in non-uniform control flow (rather than Workgroup).

Can you test this branch with the game and see if that resolves the artifacts?
If not, then in addition to forcing the subgroup size, we may need to introduce control barriers that operate on the Subgroup scope, which should be allowed in non-uniform control flow (rather than Workgroup).

Unfortunately with that branch the game works correctly until I reach the screen when the bug is visible, but blocks at that moment and after a few dozen seconds it crashes. For the record, the HUD reports device Intel(R) UHD Graphics 630 (CFL GT2), driver version 20.3.3 and Vulkan version 1.2.145.

Unfortunately with that branch the game works correctly until I reach the screen when the bug is visible, but blocks at that moment and after a few dozen seconds it crashes. For the record, the HUD reports device Intel(R) UHD Graphics 630 (CFL GT2), driver version 20.3.3 and Vulkan version 1.2.145.

Got any log files? It's important to know whether this is a GPU hang or something else going wrong.
Anyway, if this doesn't work, I'd rather just leave this broken.

Got any log files? It's important to know whether this is a GPU hang or something else going wrong.
Anyway, if this doesn't work, I'd rather just leave this broken.

BTW, given that the TGSM barrier workaround is good enough and Intel cards are not generally advised for gaming, I am not interested in this issue any more. Since I guess upstream isn't too, I am closing.


Feature/process listening on port store jv address david review round 2

Addresses latest store PR review comments https://github.com/stackrox/stackrox/pull/4328

/test gke-postgres-nongroovy-e2e-tests

/test gke-postgres-nongroovy-e2e-tests


WIP - Adding GenerateMnemonic API

Description

Adding GenerateMnemonic API

Checklist

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] CHANGELOG is updated.

@jwmdev CreateWallet API is added. It accepts monotonic and wallet names to create a new wallet. Password is optional.
We can use this API to create/restore wallets in GUI.
Please check and if it is OK, feel free to merge it.
Thanks


issue with continuing installation of wirepod on a raspberry pi.

upon attempting to install, it appears its not downloading GO. ive installed it manually, and still getting the same issue.

What is the operating system?

Try using Armbian 23.02.2 Bullseye

What is the operating system version?

Latest Debian

Make sure you're using a 64-bit Raspberry Pi OS. The default Raspberry Pi OS has a 64-bit kernel, but links with 32-bit, and setup.sh can't detect that at the moment.

Will try.
On Thu, Nov 2, 2023, 8:15 a.m. Wire @.***> wrote:

Make sure you're using a 64-bit Raspberry Pi OS. The default Raspberry Pi
OS has a 64-bit kernel, but links with 32-bit, and setup.sh can't detect
that at the moment.
—
Reply to this email directly, view it on GitHub
https://github.com/kercre123/wire-pod/issues/215#issuecomment-1790618417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQWV6JUHGSUOI3GWRHQ6BGTYCOFE3AVCNFSM6AAAAAA6Z6X7FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQGYYTQNBRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

alright. chipper running. as per the following step(s)
[Authenticate a production bot]
It is recommended to clear your bot's user data. This is not required, and you can still authenticate with wire-pod without it (as long as the last server you have authenticated the bot with was the DDL/Anki production stack), but it may cause unexpected behavior.
Place Vector on the charger
Double press his button
Lift his lift up then down
Take Vector off of the charger and twist one of the wheels until the cursor is on "RESET" (or "CLEAR USER DATA")
Lift the lift up then down again
Move the wheel until the cursor is on "CONFIRM"
Lift the lift up then down again
Refresh the vector-wirepod-setup page and follow the instructions  <<<<<-----  I get to here, refreshing does nothing.

with V all brand new, with a new ID#, hes jus sittin on his charger with his head up with anki.com/v across his face

Follow the instructions on the page. It will detect that Vector isn't in recovery mode and will authenticate him rather than put a different firmware on him.

Just wanted to say I ran into this same issue and following the instructions, was able to get it resolved. I have a brand new raspberry pi 4b that came with a pre-installed OS. I ended up downloading the latest 64bit os and started from scratch and that helped.
And then during the setup stage I also got Vector into the state described above. I realized I needed to double-tap Vector's button to get into pair mode. And then after updating the firmware when that Pair With Vector button was shown, to then just double-tap Vector's button again. On the first go around I made the mistake of holding his button down for 15 seconds to pair him again (which I think reset his firmware). That may have been obvious to others, but thought I'd say that here in case anyone else new makes that mistake.


[Feature Request] supporting witness rule as listed in NEP-21

details can be seen here https://github.com/neo-project/proposals/blob/dapi/nep-21.mediawiki

@overlordsecurity Hi, We have supported witness rules now, you can get it [here] first(https://github.com/NeoNEXT/neoline/releases/tag/v3.6.1) if you want it, the online version is pending review now.


APIM + DataBox events

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Messaging.EventGrid


Method srs_rtmp_publish_stream Constantly Failing. Connection refused on port 1935.

When trying to run srs_h264_raw_publish, I'm getting 'Simple Handshake Failed'. I'm using Ubuntu 12.04.

check your h264 format


Create separate auth tag for authentication of users and owners

These things should come inside auth tag:

Verify User Email Otp
Login Access Token
Owner Login Access Token (duplicated across login and owner tag)
Verify Owner Email Otp

ok


Slanted Container (experimental)

Changes

Playing around with new modifier for the Container pattern, based on some lovely mocks from the design team. Posted to save for later, and for feedback/discussion.

Not ready for merge. :rotating_light:
Screenshots

And on a content page...

And experimenting with some bolder colors in the Web Inspector. Perhaps a .-loud modifier.

I like that!

PURPLE AND YELLOW IN THE MOCKS

Rebased against latest dev, and added "loud" container modifier in code. Also made an experimental version of the Header's "banner" modifier based on Action Page mock.

Another screenshot:

And with the Prove It section:

:skull:


[UT] add more condition to improve the coverage of DecoderCrashTest

https://rbcommons.com/s/OpenH264/r/1132/

Should this be two commits?


Installing OMF plugins does not work

Whenever I try to install a OMF plugin I get the same error message.
Example:
# fisher install omf/plugin_peco
Installing plugin/s
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/oh-my-fish/plugin_peco/'
No plugins were installed

https://github.com/oh-my-fish/plugin_peco/ the plugin does not exist at this repo.
The correct command would be: fisher install omf/plugin-peco.
Although granted, the error is confusing. we'll keep this issue open for further discussion.

OK I see. Are OMF dependencies handled? I installed plugin-weather which got many errors because plugin-config was missing. Alas https://github.com/oh-my-fish/plugin-weather/blob/master/bundle

At the moment, they are not.
@bucaran is this on the roadmap?

@jethrokuan @ypnos OMF bundles are handled, problem here is plugin-config is a package designed to work exclusively with OMF variables, essentially a clever way to guarantee incompatibility with other systems.
@ypnos TBH, the weather package is not that impressive considering you can:
curl wttr.in/tokyo

Closing as the config package can't be supported.


How to determine final database field name

Currently, we define type struct model. I have a use case and I would like know what is the field name used in database.
type User struct {
    CreatedAt time.Time
}

Final field name will be created_at but I can't found no method in Gorm to found this.

created_at is automatic CamelCase->snake_case conversion that gorm performs.
gorm.Model uses CreatedAt as one of it's fields.
If you do not embed it on User — you will not have an issue.

Also, look at how you can use annotations to set the column name yourself:
CreatedAt time.Time `sql:"column:creation_date;"`

I would like determine (with a internal Gorm method), the field name generated.
CreatedAt time.Time `sql:"column:creation_date;"`
UpdatedAt time.Time

Field name given will be creation_date and updated_at.
Your internal method to determine final field name to use in database is it public ?

I don't know if you found the answer or not. but this what I found.
You can user Scope For example:
userScope := db.NewScope(User{})
createdAtField, ok := userScope.FieldByName("CreatedAt")
fieldName := createdAtField.DBName


Upgrade psfmatch to Alard & Lupton kernel method

Here's their seminal paper: http://adsabs.harvard.edu/abs/1998ApJ...503..325A  It only has 767 citations so they'll be glad of ours.  Let's read this and see if what it would take to implement a simple version. We may also be able to import an existing package that does this work (hotpants?)

Currently we don't do any psf matching. Maybe we don't need to do this!


Enable Dark Reader settings to follow the accent color

Generate a new themeInfo.json with the classname corresponding to the Slider control in Dark Reader Settings section
Description

Remove unwanted mozilla specific style for slider
Run npm run build-theme-info
This step generates a modified themeInfo.json

Motivation and Context

Fixes #644
How Has This Been Tested?

Tested locally in Windows 10 dev environment.
Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project (run $ npm run lint).

@kytwb : Have made the fix. Can you pls check?


CMake Intel DPC++ compiler support

Brief Issue Summary
Please, consider adding Intel DPC++ compiler support to CMake kits detection.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
Here is some info https://www.intel.com/content/www/us/en/develop/documentation/oneapi-dpcpp-cpp-compiler-dev-guide-and-reference/top/compiler-setup/use-the-command-line/use-cmake-with-the-compiler.html
The one may be downloaded here:
https://www.intel.com/content/www/us/en/develop/documentation/oneapi-dpcpp-cpp-compiler-dev-guide-and-reference/top/compiler-setup/use-the-command-line/use-cmake-with-the-compiler.html

Thank you for the feature idea. We may not be able to get to this immediately, but I'm tagging it for further discussion.

add these lines to the .vscode/cmake-kits.json:
[
    {
        "name": "DPC++",
        "environmentSetupScript": "/opt/intel/oneapi/setvars.sh",
        "compilers": {
            "C": "icx",
            "CXX": "icpx"
        }
    }
]

Did it work for you? It didn't work for me.

Thanks @LXYan2333, need to check.
Qt plugin generates something similar  https://codereview.qt-project.org/q/project:qt-labs%252Fvscodeext
I am sure that this approach may be part of Intel plugin if not the CMake extension


[anirip] Error: validating session: could not verify session

Hi,
I tried to download some shows today and I keep getting the same message
[anirip] Error: validating session: could not verify session
Does this have anything to do with Cloudfare Protection? Because I heard that every other script is not working anymore.

I've had this same problem off and on for awhile now. Usually I wait about a day and it clears itself up, but that doesn't seem to be the case this time. I was actually on my way here to see if anyone was having the same issue.
In the meantime, you could use youtube-dl. It seems to still work.

I've had this same problem off and on for awhile now. Usually I wait about a day and it clears itself up, but that doesn't seem to be the case this time. I was actually on my way here to see if anyone was having the same issue.
In the meantime, you could use youtube-dl. It seems to still work.

youtube-dl is having the same issue as well. looks like crunchyroll did change something with its cloudfare protection so it requires you to do a captcha manually

My guess is that crunchyroll finally added captcha to its login which it previously didn't have (or if it did have it I just never noticed and this app never should have worked to begin with). The fix for this  (hopefully) is to use the mobile app API (see streamlink's implmenetation). If I get some free time I'll work on a PR for this to fix it.

any update on this one? we are a bit stuck for now...

switched to https://github.com/hama3254/Crunchyroll-Downloader-v3.0

Thanks for the recommendation @hekmon . I use this method currently because it's easy to automate and leave in the background. Is it easy to manage multiple shows with this software. Also at the moment I archive the download to a separate drive and create a blank empty file with the same name to trick the software into think its downloaded without taking up space. Would I have to do something similar for this application too?

Wow. I have no idea 🤔
Your usage of the app is for more advanced than mine 😅

I do also automate a bit with anirip to sync the show I want on a regular basis.
The one you suggested to work, but cannot be automated at all, you can only process 2 at once, cannot queue more... must wait to complete to get another one...
ok it do the job, but not the way we were expecting with anirip.

same issue here, thank you for the recommendation @hekmon


是否能在wechaty.instance(params)中添加flashstore的路径配置

如果是在实体机安装，.wechaty（flash-store）的路径就在命令运行的目录下
如果是在docker环境下，没有把.wechaty mount出来的话，paas类环境进行更新应用时，会recreate 容器，于是.wechaty会丢失
，造成bot.Room.find({id})行为返回了空的对象，
是否能在wechaty.instance(params)中添加flashstore的路径配置
[enhancement]
// 初始化
const bot = new Wechaty({
  memory: new MemoryCard({ name : config.memorypath }),
  puppet: new PuppetPadplus({
    token: config.token,
    flashstore: { name: ".wechaty"} //添加类似memory-card的配置方式
  }),
  name: config.name
})

It's a great question with the PaaS use case.
We will consider this situation and try to fix it in the future.
Before we fix it, I believe there are workarounds for this problem:

mount your volume for your container to the directory: ~/.wechaty before start wechaty
link ~/.wechaty1 to your volume path in the container before start wechaty

I hope my workaround can solve your problem, and please feel free to let me know if you have more questions.

for other situation，ex：
workdir ：/app —— readonly for src
datadir ：/data —— writable for cache，logs ...
i think wechaty may have a config option for all storage path prefix