rustfmt 0.6.0 seems broken

I just updated my rustfmt to 0.6.0 and now RustyCode always says Cannot format due to syntax errors, which is weird, cause manually invoking cargo fmt works just fine without any warnings. It might just be me, but it used to work before, so it's kind of weird that it doesn't now.

This is fixed by https://github.com/saviorisdead/RustyCode/pull/161

Oh, totally missed that. Thanks for the fix :D

It seems to me like #161 does not fix rustfmt 0.6.0. Looking at the output of rustfmt's diff, it seems to have changed.
https://github.com/rust-lang-nursery/rustfmt/commit/a0de408198d5f1e8e2d96b471450af3742dfdddc#diff-4867ec103faeb4d5bb7651bcdb33994a

@kdar good catch, at the time I wrote the PR the version of master I was on didn't have the changed output. I suppose we're going to need to write in a backwards compatibility layer too 😞. I'll add it to my todo list.

If you are looking for a solution to this now, here is a patch which works with rustfmt 0.6.0:
https://gist.github.com/physhh/e686d1ef3d43ff15b0073a0f888e9fc2
Relevant code of rustfmt:
https://github.com/rust-lang-nursery/rustfmt/blob/e1759ae295a65b28636d4635f76daa129eed9be0/src/filemap.rs#L151
https://github.com/rust-lang-nursery/rustfmt/blob/35624c54e5d7db6db232a2c814441473acc37cfd/src/rustfmt_diff.rs#L118
Patch does not care about backward compatibility to older rustfmt versions.

Awesome! Thank you @physhh

This is fixed with backwards compatibility in #173 👍

Anything left to do here?

Nope, it seems to work perfectly :)
2016-10-23 20:03 GMT+02:00 Alex Hirsch<EMAIL_ADDRESS>
Anything left to do here?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/saviorisdead/RustyCode/issues/164#issuecomment-255603632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYmbvXDQMykawLk2ccx83ki7R6KY_tsks5q26GDgaJpZM4Jj4Z4
.


Get upload speed

Is it possible to get the upload speed on progress? such as 100kbps, etc.
Thanks!

see https://github.com/danialfarid/ng-file-upload/issues/355


Sliding down multiple times past the top of the page crashes the app

Slide v0.5.11, iPhone SE 10.2.1
Sorry if the title doesn't make sense, don't know how else to put it. CrashReporter doesn't grab a crash log so I'm not sure how to post one here.
Videos of the issue:
https://streamable.com/c5rtm
https://streamable.com/jt2i6
https://streamable.com/an9po

Happens too on iPad Pro 9.7 iOS 12 DB1 on Slide 1.0 Beta RC

Fixed!


Seperated trigger_constant_contract from trigger_const_smart_contract_function method

needed the full dict returned by "wallet/triggerconstantcontract"

Hi! Why do we need another method if it just returns a fixed path of a different one? Just call the original method and access needed data at path

The original method filters out some important parameters such as energy_used and energy_penalty and only returns the constant_result parameter.

But it appears the original method  returning the constant_result is used, so i had to create another function to first return the complete data then the original function to parse out only the constant_result so that there is no breakage in the code.

Ah sorry, I've misread the diff. Thanks for the explanation
Hint: you can rebase your branch to avoid all those commits stacked together when you submit changes

okay, thank you.


consider options for showing a "timeline" of histor(ies) of endpoints

this is taken care of now that things are stored in prometheus


fix(connection): separate send/receive debug logging

This PR splits the logging for send and receive messages in to separate debug channels.
This way it is easier to filter and takes advantage of debug's automatic coloring to make
it easier to visually parse on the command line.
Before PR:

After PR:

@jackfranklin Even in light of the plans to make debug platform-agnostic, this patch seems acceptable. Do you agree? PTAL

Thanks @jackfranklin & @mathiasbynens!


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.4.178",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c33402b056de61104b6146dedbe138ca8d7ec62b"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "c33402b056de61104b6146dedbe138ca8d7ec62b",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.178 by commit c33402b056de61104b6146dedbe138ca8d7ec62b. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000168


✨ Enabled Aggregate API for Virtual Cluster

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/166
@christopherhein @Fei-Guo
This PR only covered VirtualCluster but does not cover nested control plane, will fix nested control plane in another PR.
@wangjsty ^^

Did you mean to remove the changes you made in controlplane/nested/component-templates/nested-apiserver/nested-apiserver-statefulset-template.yaml prior?

Did you mean to remove the changes you made in controlplane/nested/component-templates/nested-apiserver/nested-apiserver-statefulset-template.yaml prior?

@christopherhein for now, yes, I want to use this PR for virtual cluster and then create another PR for nested control plane soon, hope it is OK.

Sounds good, just wanted to make sure. :+1:
/lgtm
/approve

@gyliu513 @christopherhein， One more comment even through the PR was merged.
I validated the PR again, looks like it's good, but please - --requestheader-allowed-names=front-proxy-client to replace the current - --requestheader-allowed-names="". Thanks.

@gyliu513 @christopherhein， One more comment even through the PR was merged.
I validated the PR again, looks like it's good, but please use - --requestheader-allowed-names=front-proxy-client to replace the current - --requestheader-allowed-names="". Thanks.

Good find, @wangjsty can you make sure an issue is filled and @gyliu513 can you do this as well?

@christopherhein Done at https://github.com/kubernetes-sigs/cluster-api-provider-nested/pull/179


update-imported-docs in golang

update-imported-docs/config.yaml should have the src and dest paths for the target files.
/assign @steveperry-53
I'm not sure what branch (master or release-1.9) should this PR target.

This change is

/assign @apelisse

@mengqiy The master branch is fine for this PR.

@steveperry-53 Are you going to use this script to update the imported docs for 1.9 release? Or if you want to keep the PRs that are manually crafted i.e. #6614 #6619 #6628?

@mengqiy I was thinking I would use this script, and make a new PR to replace #6614, #6619, and #6628. Does that sound reasonable?

SG. I guess you only need to run it once after you populate the config.yaml. IOW, I guess you will only need 1 PR.
One concern: if this PR is merged into master branch, will you guys do fast-forward (or something else) to make 1.9 branch have this program as well?

@mengqiy At this point, we should wait until after the 1.9 release to merge this PR. On Wednesday, 12/13, the plan is to merge kubernetes/website/release-1.9 into kubernetes/website/master. After that, we can merge this PR into master. In the meantime, I have cloned mengqiy/website:play, and am running the script to generate docs. I'll submit those generated docs in a PR to kubernetes/website:release-1.9. I should be able to do that tonight.

See #6658.

Thanks for you feedback.
Can you provide me the config.yaml?
So I can reproduce it and check why it happens. And then fix it.

repos:
- name: kubernetes
  remote: https://github.com/kubernetes/kubernetes.git
  branch: release-1.9
  files:
  - src: docs/admin/cloud-controller-manager.md
    dst: docs/reference/generated/cloud-controller-manager.md
  - src: docs/admin/kube-apiserver.md
    dst: docs/reference/generated/kube-apiserver.md
  - src: docs/admin/kube-controller-manager.md
    dst: docs/reference/generated/kube-controller-manager.md
  - src: docs/admin/kubelet
    dst: docs/reference/generated/kubelet.md
  - src: docs/admin/kube-proxy.md
    dst: docs/reference/generated/kube-proxy.md
  - src: docs/admin/kube-scheduler.md
    dst: docs/reference/generated/kube-scheduler.md
  - src: docs/user-guide/kubectl/kubectl.md
    dst: docs/reference/generated/kubectl/kubectl.md
- name: federation
  remote: https://github.com/kubernetes/federation.git
#  # Change this to a release branch when federation has release branches.
  branch: master
  files:
  - src: docs/admin/federation-apiserver.md
    dst: docs/reference/generated/federation-apiserver.md
  - src: docs/admin/federation-controller-manager.md
    dst: docs/reference/generated/federation-controller-manager.md
  - src: docs/admin/kubefed_init.md
    dst: docs/reference/generated/kubefed_init.md
  - src: docs/admin/kubefed_join.md
    dst: docs/reference/generated/kubefed_join.md
  - src: docs/admin/kubefed.md
    dst: docs/reference/generated/kubefed.md
  - src: docs/admin/kubefed_options.md
    dst: docs/reference/generated/kubefed_options.md
  - src: docs/admin/kubefed_unjoin.md
    dst: docs/reference/generated/kubefed_unjoin.md
  - src: docs/admin/kubefed_version.md
    dst: docs/reference/generated/kubefed_version.md

Thanks! I will dig it tomorrow or next Monday.

See #6658. Notice that in some topics, the synopsis appears twice.

Do you mean it appears once in synopsis and once in Example?

Example: kubectl options.

The link you gave actually links to kubefed options.
After digging this a bit, I found it's not the problem of this script. The generated doc looks the same. So if the format is wrong, then the issue is in the federation repo.

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@mengqiy Thanks for checking into this. My mistake on the link text; I meant it to say kubefed options. Ar you ready for me to merge this PR now?
These are the files that had the double synopsis:

kubectl.md
kubefed.md
kubefed_init.md
kubefed_join.md
kubefed_options.md
kubefed_unjoin.md
kubefed_version.md

The synopsis appeared once just below the title and once just below the Synopsis heading. This commitshows the files where I removed the synopsis that appeared under the title.
When I get a chance, I'll take a look at the federation scripts, and see about getting those fixed.
Before I did the removal, the pages looked like this:
kubefed init
Initialize a federation control plane
Synopsis
Init initializes a federation control plane.


Action / Intention / Execution Recognition

I wonder if I can interact with bot and it recognize several words or phrases that fire an Action or recognize an Intention that interact with external source and give me a response.
eg:
User: How about the weather today?
Bot : , ... forecast today.
or: (intention)
User: I want to run outside today.
Bot : It may rain today.
or (action/execution)
User: Turn on living room lights.
Bot: Sure ! A minute!
Bot: Done, enjoy!
I don't know if LogicAdapter, StorageAdapter either I/OAdapter is the right place to put this logic.
Maybe some kind of Intention/ActionAdapter, that complements an kind of specific answers that have an special blank space to fill in with results from integration.
Thanks.

@davizucon My views are like this. Yes you could truly achieve this task but you have to apply some chatterbot hacks here.
The chatterbot requires some training data, You have to prepare a your train data with some external input methods for example external REST API calls. There are many open external event generators through REST  API. My suggestion google REST API event
I have described above through an example. Related issue https://github.com/gunthercox/ChatterBot/issues/482
# -*- coding: utf-8 -*-
from chatterbot import ChatBot

# Create a new instance of a ChatBot
bot = ChatBot(
    'Action or Intent Response Example Bot',
    storage_adapter='chatterbot.storage.SqlStorageAdapter',
    logic_adapters=[
        {
            'import_path': 'chatterbot.logic.BestMatch',
            'statement_comparison_function': 'chatterbot.comparisons.jaccard_similarity',
            'response_selection_method': 'chatterbot.response_selection.get_first_response'
        },
        {
            'import_path': 'chatterbot.logic.SpecificResponseAdapter',
            'input_text': 'Help me!',
            'output_text': 'Ok, here is a link: https://openweathermap.org/current'
        }
    ],
    trainer='chatterbot.trainers.ListTrainer'
)

# Train the chat bot with a few responses
bot.train([
    'Current weather in London',
    'http://samples.openweathermap.org/data/2.5/weather?q=London,uk&appid=b1b15e88fa797225412429c1c50c122a1',
    'Have you read the documentation?',
    'No, I have not',
    'This should help get you started: http://chatterbot.rtfd.org/en/latest/quickstart.html'
])

# Get a response from bot
response = bot.get_response('weather in London?')
# Handle JSON data, get all required data and print them
print(response)

@vkosuri nice hack! Issue #482 for is very specific, anyway I'll give a try!
By the way, my initial idea would be to have something apart from the conversation,  but its ok, using your hack, it can be extended with some metadata inside it.
What you think ?
eg:.
bot.train([
'Current weather in London',
'{"adapter":"chatterbot.logic.SpecificResponseAdapter"},
'Have you read the documentation?',
'No, I have not',
'{ "text" : "This should help get you started", "url": "http://chatterbot.rtfd.org/en/latest/quickstart.html"}'
])

@davizucon I think the specified information is sufficient, I am closing off this issue, please feel free reopen if you have any specific question on this issue.


feat(font): stylistic sets & other OpenType features

This fixes our current editor.fontLigatures flag to be able to take in a string of features, similar to what VSCode has.
I.e. "editor.fontLigatures": "'ss02'" enables the second stylistic set.
This is achieved through a custom parser using Angstrom.
Fixes #1294

/azp run

Would you mind updating the docs, here, to describe the new editor.fontLigatures setting? https://github.com/onivim/oni2/blob/master/docs/docs/configuration/settings.md#editor

@bryphe definitely!

Looks great, thanks for adding the docs @zbaylin 👍


[WIP] Adding Test for Circuit Serialization

Summary
Adding circuit serialization tests to qiskit-experiments package as suggested in #1063
PR checklist

[x] Add test to RB
[ ] Add test to Hahn Echo
[ ] Add test to Ramsey

@ItamarGoldman This looks good to me, but Chris made a suggestion here of using the json serializer rather than the qpy functions directly. I didn't update https://github.com/Qiskit/qiskit-experiments/pull/1059 to follow that suggestion. Have you looked at that option?

Another issue came up when I was testing #1183. QV circuits are currently not serializable when Aer isn't installed because Statevector.probabilities() returns a numpy array:
https://github.com/Qiskit/qiskit-experiments/blob/38678c283f1d2463792650a29492fb77f0170f26/qiskit_experiments/library/quantum_volume/qv_experiment.py#L157
This needs to be cast to a list and tests should be added that check both Aer and Aer-less circuits.

@ItamarGoldman This looks good to me, but Chris made a suggestion here of using the json serializer rather than the qpy functions directly. I didn't update #1059 to follow that suggestion. Have you looked at that option?

Thanks! I changed the serialization to be used with the json serialization method (I used 'assertRoundTripSerializable(exp)' ) I will add the tests to other experiments.

@ItamarGoldman Yes, the numpy array in the ideal_probabilities field comes from that line I posted above, so I think we're generally talking about the same thing. The good thing is the issue with numpy serialization will be fixed once Qiskit/qiskit-ibm-provider#648 is merged.

you are right. The problem was the output of the method _get_ideal_data in qv_experiment.py  was ndarray instead of List[float]. I casted the output into a list so it will be the same as in type hint.


Specify when all with no senders

 Issue by bustercopley
Friday Oct 14, 2022 at 18:19 GMT
Originally opened as https://github.com/brycelelbach/wg21_p2300_execution/pull/3

See https://github.com/NVIDIA/stdexec/pull/482

bustercopley included the following code: https://github.com/brycelelbach/wg21_p2300_execution/pull/3/commits

@ericniebler I think this is fixed in the wording of R10:
https://cplusplus.github.io/sender-receiver/execution.html#spec-execution.senders.adaptor.when_all
(actually, I think the behaviour for 0 is not specified in the design, but we're passed that and in the wording stage anyway).


[swim] implement Join function

Subject
write here
Detail
implement swim join function
assignee
@ChaeByunghoon

@junbeomlee


Adjust Docs For Ansible Vault

The instructions created a shell variable that would not have been passed into execution environment causing the described process to fail
A friend let me know the instructions were not working and I confirmed it myself locally (@penguinpages)

TY @timway ! Good find


Email Sender

Add a Email sender.

[x] Email Sender

https://github.com/Astrotomic/notifynder-sender-email


Fix 'RuntimeError: generator raised StopIteration' on Python 3.7 and …

This fixes the crash caused by PEP479 - 'Change StopIteration handling inside generators'
As of Python 3.7, when a StopIteration is raised inside a generator, it triggers a RuntimeError, crashing apt-mirror-check. This commit fixes that by quietly catching the StopIteration before it can propagate.

Rebase and merged.
Thanks!


Camel K should use duck types to recognize Knative sinks

We're currently analyzing channels and services by looking at their types, but e.g. some channels are moving to their own CRD in Knative (e.g. KafkaChannel), so they won't be recognized.
https://github.com/knative/eventing/issues/1216

This is an issue with knative 0.8+ releases where e.g. channels have been moved from eventing.knative.dev to messaging.knative.dev

Fixed by https://github.com/apache/camel-k/pull/961


fix(login): User should login by default when he registers

Current coverage is 72.50% (diff: 71.42%)

Merging #278 into master will increase coverage by 0.03%

@@             master       #278   diff @@
==========================================
  Files            59         59
  Lines          4072       4073     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2951       2953     +2
+ Misses          797        795     -2
- Partials        324        325     +1

Powered by Codecov. Last update fb5e41c...5b053c8


Bug: When AWS_LWA_INVOKE_MODE: response_streaming with empty body, LWA fails to send termination chunk

First, thank you for such an amazing tool!
I'm running Next.js in Lambda with Lambda Web Adapter via Function URL behind CloudFront with AWS_LWA_INVOKE_MODE: response_streaming. I'm using Authjs/NextAuth to redirect users to Cognito to authenticate and then Cognito redirects the user back to my Next.js app to /api/auth/callback/cognito?code=123abc where NextAuth picks up the request and then sends a redirect (302) back to client to redirect user to the app's home page. Currently, CloudFront is timing out the request (default 30 sec) which makes for poor UX. I've worked with AWS Support because at first I thought this was a CloudFront issue. But the CloudFront Support team has told me it's not an issue with CloudFront but an issue with the lambda since the request has Transfer-Encoding: chunked but it's not sending the correct termination chunk. When NextAuth sends the redirect it has a body size of 0. When I force the body size to be > 0 then the request succeeds which is my current work around. So I think there is a bug in LWA that when there is a body size of 0 it fails to send the termination chunk which should look like:
0\r\n
\r\n

see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding#chunked_encoding
I have more information to share if needed based on CloudFront Support team's analysis that I can share privately.

Thanks for reporting this issue.
I'm not so sure this is the root cause of your issue. In the FastAPI Response Streaming example, the app's root path redirect to "/demo" with 0 length body, and it works perfectly with CloudFront. You could deploy that example and put a CloudFront distribution in front of it to verify.

Hi Team. I've helped @bestickley through the troubleshooting, and the issue is not happening all the time. The exact same type of requests sometimes goes through immediately, and other times takes as long as the origin read timeout set on CloudFront. When we look into the logs, we observe that CF sends the request to Lambda Function URL and Lambda responds very fast. CloudFront receives all the headers of the response very fast in all circumstances. However,  for requests that eventually timeout, there is a 0 size body, while for the requests that don't timeout there is a very small body size. As CloudFront makes the request to Lambda Function URL using HTTP1.1 and the response is coming with response header Transfer-Encoding=chunked, there should be always size body different than zero to accommodate the termination chunk sequence. Our understanding is that the timeout is happening because that sequence is not received by CloudFront in some situations. Again, it is not happening all the time so @bestickley configuration might be hitting some edge case triggering this behaviour. Please reachout to me where i can share specific details on how these was troubleshooted.

@gfmsb  Thanks for the details. Reaching out you for more details.

We confirmed this is not a bug with Lambda Web Adapter.


Update README.md for spinel-cli

Codecov Report

Merging #1659 into master will increase coverage by 1.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1659      +/-   ##
==========================================
+ Coverage   68.02%   69.63%   +1.61%
==========================================
  Files         169      166       -3
  Lines       20226    19191    -1035
  Branches     2506     2337     -169
==========================================
- Hits        13758    13364     -394
+ Misses       5605     5003     -602
+ Partials      863      824      -39

Impacted Files
Coverage Δ

examples/platforms/posix/misc.c
0% <0%> (-66.67%)
:arrow_down:

src/core/api/icmp6_api.cpp
50% <0%> (-50%)
:arrow_down:

src/ncp/spinel.c
52.4% <0%> (-24.7%)
:arrow_down:

src/core/net/ip6.hpp
66.66% <0%> (-22.23%)
:arrow_down:

src/core/api/ip6_api.cpp
43.75% <0%> (-17.19%)
:arrow_down:

src/core/mac/mac_whitelist.cpp
76.59% <0%> (-17.03%)
:arrow_down:

src/core/api/netdata_api.cpp
57.44% <0%> (-14.9%)
:arrow_down:

src/core/net/icmp6.hpp
89.47% <0%> (-10.53%)
:arrow_down:

src/core/net/ip6.cpp
54.24% <0%> (-9.44%)
:arrow_down:

src/core/api/thread_api.cpp
29.08% <0%> (-7.57%)
:arrow_down:

... and 23 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 7c7519f...d47f072. Read the comment docs.


Sequence issue with new fixture population code on postgres

I'm seeing a regular test failure on postgres only, that indicates that fixture population operations are not always happening in the correct order/sequence. I've definitely seen this on node v4, not sure about v0.12 and v0.10.
The error is with the "should populate all fixtures correctly" integration test that I added to core/test/integration/migration_spec.js before I did the refactor, in order to prove that both versions did the same thing. The problem is happening in a special assertion I wrote which is intended to check that each permission gets assigned to the correct roles.
The error is as follows:
  1) Database Migration (special functions) Fixtures should populate all fixtures correctly:
... (big perms object here) ...
 expected Array [ 'Editor', 'Administrator', 'Author' ] to equal Array [ 'Administrator', 'Editor', 'Author' ] (at '0', A has 'Editor' and B has 'Administrator')
      at Assertion.fail (node_modules/should/lib/assertion.js:91:17)
      at Assertion.Object.defineProperty.value [as CompletePermissions] (node_modules/should/lib/assertion.js:163:19)
      at core/test/integration/migration_spec.js:177:59
      at tryCatcher (node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (node_modules/bluebird/js/release/promise.js:503:31)
      at Promise._settlePromise (node_modules/bluebird/js/release/promise.js:560:18)
      at Promise._settlePromise0 (node_modules/bluebird/js/release/promise.js:605:10)
      at Promise._settlePromises (node_modules/bluebird/js/release/promise.js:684:18)
      at Promise._fulfill (node_modules/bluebird/js/release/promise.js:629:18)
      at PropertiesPromiseArray.PromiseArray._resolve (node_modules/bluebird/js/release/promise_array.js:125:19)
      at PropertiesPromiseArray._promiseFulfilled (node_modules/bluebird/js/release/props.js:78:14)
      at Promise._settlePromise (node_modules/bluebird/js/release/promise.js:565:26)
      at Promise._settlePromise0 (node_modules/bluebird/js/release/promise.js:605:10)
      at Promise._settlePromises (node_modules/bluebird/js/release/promise.js:684:18)
      at Async._drainQueue (node_modules/bluebird/js/release/async.js:126:16)
      at Async._drainQueues (node_modules/bluebird/js/release/async.js:136:10)
      at Immediate.Async.drainQueues [as _onImmediate] (node_modules/bluebird/js/release/async.js:16:14)

The order of attribution of roles to permissions is not actually important, so this could be fixed by updating the assertion to not care about order.
However, as all the operations are done using sequence, I would expect them to always be the same? The tests are not failing on sqlite3 or MySQL, so I'm interested to get some feedback from someone who knows postgres on why the behaviour here is different and what a correct fix to preserve order might be.

Disclaimer: I haven't looked at this specific problem. However, I know from experience with these errors in the past that sometimes it's actually a bug and Postgres just happens to work slightly faster/different and that's why you see the failure there.

Ok, I've been playing around with this, and I think I've figured out what's happening.
The roles and permissions are all getting inserted in the correct order, whoop. I've not seen a single case where they aren't.
However, the fetch for permissions with their roles don't provide a specific order to return the related results in. MySQL and SQLite both always seem to return these things ordered by their primary key no matter what, pg seems to be more flexible about the whole thing.
Seeing as the order doesn't actually matter in this case, I can update the assertions to not care and be happy that nothing horrid is happening here.


Overriding username and password fields

Is it possible to override the username and password; e.g. so that they come from another ActiveRecord model?  I've got an ID and pin already stored in another model, and want to use that data instead of the traditional "username" and "password".  Extending from User doesn't seem to make sense since the login method is elsewhere.  Hints?

I don't think this is possible with Yii2-user.


slirp4netns: use --disable-host-loopback

Closes: https://github.com/containers/libpod/issues/2642
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

LGTM assuming happy tests

/lgtm

looks like there are two broken tests but still the openshift-robot merged :(

I don't know if I trust it anymore - it doesn't seem to work well for our multi-CI-system environment.
We might have to start restricting /lgtm to having manually inspected all the tests and verified they are green.

@mheon: PR here: https://github.com/containers/libpod/pull/2653


Apply max request body to gRPC channel

Today we support setting a max request size for the gRPC server, but we don't apply it to the gRPC channel that Dapr uses to talk to the app.
This means that if a user sets a 16MB limit, Dapr will allow the call to go through one Dapr instance to another, but will fail when trying to deliver the message to the app.
This call option: https://github.com/dapr/dapr/blob/e9ef871f8eeed59a3680a3aa8fd8dcb6673f7950/pkg/messaging/direct_messaging.go#L171
Should be added here: https://github.com/dapr/dapr/blob/e9ef871f8eeed59a3680a3aa8fd8dcb6673f7950/pkg/channel/grpc/grpc_channel.go#L93.

I would like to take this if possible.

@daixiang0 for this issue there's already a contributor in the pipeline. in the meantime we are busy reviewing all your other great work :)

@yaron2 thanks for your careful  review :)

@yaron2 Sure, will do that

@daixiang0 for this issue there's already a contributor in the pipeline. in the meantime we are busy reviewing all your other great work :)

@yaron2 thank your for looking into this. Please assigning it to me.

@daixiang0 for this issue there's already a contributor in the pipeline. in the meantime we are busy reviewing all your other great work :)

@yaron2 thank your for looking into this. Please assigning it to me.

Assigned.

@yaron2 Yaron, I am already working on that issue.

@yaron2 Yaron, I am already working on that issue.

@apuzyrevsky @yaron2 I have already fixed the issue and was about send the pull requests.  Let me know whatever works.
https://github.com/alvinhenrick/dapr/tree/max-req-grpc-channel-issue-3265

Well, long response and you can lost your task 😅
@alvinhenrick It seems ok, I can do a review of your PR when you'll send it.

Well, long response and you can lost your task 😅
@alvinhenrick It seems ok, I can do a review of your PR when you'll send it.

@apuzyrevsky Will do it now :) . Thanks

Thank yoi both :)


How To Use Docker Application To Run Python Discord Bot

Writing sample(s):
https://en.wikipedia.org/wiki/Discord (software)
Proposed article introduction
Discord is a voice platform with IP, instant messaging, and digital distribution. Users communicate in private conversations or as part of "servers" via voice calls, video calls, text messaging, media, and files. [Footnote 1] Server is a collection of permanent chat sites and voice chat channels accessible through invitation links. Windows, macOS, Android, iOS, iPad, Linux, and web browsers all support Discord. The service has had over 350 million registered users and 150 million active users since 2021.
Bots can use the Discord field to perform automated tasks by responding to human commands. As a result, this post will show you how to use the Python-based Discord bot in the Docker container.
Key takeaways

Make your own Discord request.
Set Requirements.
Make Discord Bot.
Activate Discord Bot.
Join Discord Server with Bot.

Article quality
This post will include the implementation of the Docker Application Application to Run the Python Discord Bot in a step-by-step and in-depth manner.
References
Docker application
Tutorial template
Python

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large. Please feel free to suggest an alternate topic to explore. 🚀
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.
If you believe your article is unique enough - please present your case to explain how it will be different from what is currently out there?
https://www.google.com/search?q=Docker+Application+To+Run+Python+Discord+Bot&rlz=1C1CHBF_enUS891US891&sourceid=chrome&ie=UTF-8


Easily identify stream graph bottleneck

@BugenZhao
We may investigate if it's possible to inspect the back-pressure metrics next time so we can find which fragment is slow at a single glance. :lark-cry: Await-tree has bear too much...
https://github.com/risingwavelabs/risingwave/pull/11696

Oops, seem like @BugenZhao is already working on it:

I’m currently investigating the flow chart in Grafana: https://github.com/rekha86sundararajan/grafana-diagram

I think the dashboard based solution is kind of inadequate for cluster with large number of stream jobs. I found the backpressure graph takes too long to load. Further, the dashboard approach is not user facing. I would like some form of metrics that the cloud side can scrape, and that we can display in our dev-dashboard.
Btw this is not to diminish the great work that @BugenZhao has done 🙌 , it is very useful for diagnose bottleneck for small to medium size clusters, and also to give an idea of how we can identify bottlenecks in the stream graph in an automated way, and potentially how we can also visualize it in for users.
Feel free to chime in, if perhaps there's some way we can repurpose our existing solutions.

I found the backpressure graph takes too long to load.

For this specific point, I think https://github.com/risingwavelabs/risingwave/issues/17510 can help.

I would like some form of metrics that the cloud side can scrape, and that we can display in our dev-dashboard.

Bugen tried to place a DAG graph in Grafana board, but it turned to be hard because Grafana doesn't provide a way to dynamically generate an DAG diagram. Due to this, perhaps our kernel dashboard is the best way to achieve this goal.

the dashboard approach is not user facing.

Currently yes, but I don't think it's a major problem. As long as it works well, we can port it into the Cloud portal quickly. What we need now is to prove this to be an efficient way for users to self-diagnosis.

I would like some form of metrics that the cloud side can scrape, and that we can display in our dev-dashboard.

Bugen tried to place a DAG graph in Grafana board, but it turned to be hard because Grafana doesn't provide a way to dynamically generate an DAG diagram. Due to this, perhaps our kernel dashboard is the best way to achieve this goal.

In terms of the design, is it more reasonable to have a table of actors which are currently the bottleneck? I think Grafana can support this.
Using system catalogs like rw_actor_id_to_ddl users can then quickly find the bottleneck MV, and drop it if needed.

As long as it works well, we can port it into the Cloud portal quickly.

Oh that's true.

The way forward:

https://github.com/risingwavelabs/risingwave/issues/17510 to optimize the graph.
Start using it for bigger clusters more instead of await-tree.
3.. If it works well, port it to cloud portal.

I slightly prefer visualizing it as a table, since when DAG is really large, it may be hard to navigate and see the bottleneck MV. But I think that could be an implementation detail. Since now that we have a DAG, we can traverse it can come up with the bottleneck spots ourselves.

Btw, another issue is that we can only check the bottleneck MV at a the current_time. But if it occurs during off-peak hours, because we don't collect historical data of the MV, we can easily lose this data of which MV and actor is the bottleneck.

Btw, another issue is that we can only check the bottleneck MV at a the current_time. But if it occurs during night-time hours, because we don't collect historical data of the MV, we can easily lose this data of which MV and actor is the bottleneck.

True. With Prometheus approach we're able to retrieve historical statistics.

Btw, another issue is that we can only check the bottleneck MV at a the current_time. But if it occurs during night-time hours, because we don't collect historical data of the MV, we can easily lose this data of which MV and actor is the bottleneck.

True. With Prometheus approach we're able to retrieve historical statistics. That's also one of reasons I chose Grafana to visualize the back-pressure graph in the very first attempt (#13422).

Actually to put the graph is grafana is sufficient. Because we can view the graph at a specific point-in-time.

Based on our discussions here's my thoughts on the approach:

Polish up the existing solution first, since it's what we have.
a. Show the MV-level bottleneck graph, so users can trace which MV is causing the backpressure.
b. Allow users to select a specific bottleneck, view it.
c. Change the dashboard bottleneck graph to use prometheus metrics, and support historical data querying.
Port this existing solution over to the cloud portal. Users can self-service and use this feature.

An idea: Shall we show the current epoch for each actor? Particularly, we may highlight the actors that are in the lowest epoch.
This is an useful technique when we use await-tree to find bottleneck. Besides, it doesn't need Promethues because the actor's epoch can be found in task_local or LocalBarrierManager.

There can be a case where upstream and downstream actors are in the same epoch, but the data between them is backpressured due to the downstream actor being a bottleneck.
In such a case it seems only the info about actor blocking or await-tree can let us know what is the bottleneck.

There can be a case where upstream and downstream actors are in the same epoch, but the data between them is backpressured due to the downstream actor being a bottleneck.
In such a case it seems only the info about actor blocking or await-tree can let us know what is the bottleneck.

Yeah, I guess both of these information can lead to the same conclusion - which actor/fragment/MV is the bottleneck. Basically, there will be a subgraph in the entire graph that has low epoch number and high backpressure.

Another thing worth to mention: sometimes the backpressure metrics can't directly point out the real cause of the problem.
For example, a 1000x join amplification may happen at actor A,
 X ---\
       A ==> B ===> [C]
 Y ---/

If B is simple, the 1000x traffic may not cause any issue. It might be until a further downstream actor C, that has some complicated window function logic, and finally become a bottleneck.
To address the problem correctly, I think throughput is another important metrics. We had better show both of these info in the visualization graph.

If the duration the actor blocks is longer than the interval at which we poll the meta service, it will currently show up as no backpressure in the dashboard. That's because when we poll, because the actor is still blocking, there's no change in the blocking duration metrics. Only when the actor has output the chunk downstream it will increment the blocking duration metrics.
When stream graph is congested, we often see in the await tree that an actor can be blocked for several minutes. So this issue can definitely occur. https://github.com/risingwavelabs/risingwave/issues/18215 is a fall-back solution, needs further investigation.

Remaining task is: https://github.com/risingwavelabs/risingwave/issues/18215. We can close this as the dashboard work is done.


Default constructor and begin() method added.  Closes Issue #11

This is a proposed temporary update to the library, providing a default constructor + begin() method for immediate use, pending more extensive API upgrades by the library author.

Hi, happy to merge this one, I'll get to it later this week once I'm in an environment where I can test the changes out.


API Documentation References Old URLs

Describe the bug
In the API Documentation the example URLs still reference the test-datastore URLs.
Example:

Expected behavior
The examples reference the updated site, e.g.
https://datastore.iati.cloud/api/activities/?has_crs_add=True&fields=title,crs_add&format=json

Correct. Those links will still work, but once we move beyond QB test phase, we should have the production name there.


Passing a parameter to a validation callback

My use case :
I have a custom built multi-step JS form where submission takes place only after the last step of the form has been filled in, and each step needs to be validated before one can move on to the next.

My code :
I created a validation callback like this :
var $form2 = jQuery('#form').parsley().subscribe('parsley:form:validate', function(formInstance) {
    // if one of these blocks is not failing do not prevent submission
    if (!formInstance.isValid()) {
        if (typeof (formInstance.submitEvent) !== typeof (undefined)) {
            // else stop form submission
            formInstance.submitEvent.preventDefault();
        }
    }
    return;
});

I'm manually triggering the validation event by clicking a link :
jQuery('.control').click(function(e) {
    if (!$form2.validate()) {
       e.preventDefault();
    }
});

My problem :
I would like to be able to attach this validation function to multiple controls and pass a different parameter to the validate function, based on which control is being triggered.
So my click handler would be changed to something like this :
jQuery('.control').click(function(e) {
    if (!$form2.validate($(e.target).data('validationgroup'))) {
       e.preventDefault();
    }
});

In the validation callback, I would then replace formInstance.isValid() with formInstance.isValid(validationgroup), so each time the validation is triggered, it runs only for one specific validation group corresponding with the control that was pressed (which I can set dynamically by passing a parameter to the validation callback).
What I don't understand is whether it's possible to pass the validationgroup to the validate function and how I should do that in case it is possible.

That's a question too, but the answer is that there might a missing feature, i.e. the form validation events should probably include the group being validated.

@marcandre :
I'm currently using a workaround :
jQuery('.control').click(function(e) {
    $form2.validationGroup = $(e.target).data("validationgroup");
    if (! $form2.validate()) {
        e.preventDefault();
    }
});

var $form2 = jQuery('#form').parsley().subscribe('parsley:form:validate', function(formInstance) {
    if (!formInstance.isValid(formInstance.validationGroup)) {
        if (typeof (formInstance.submitEvent) !== typeof (undefined)) {
            // else stop form submission
            formInstance.submitEvent.preventDefault();
        }
    }
    return;
});

This allows me to pass my validation group to the validation callback.
This still doesn't work as expected, though.
When running the validation for validation group validationGroup, I'm getting error messages for all validation groups, while I would expect to see only messages related to validation group validationGroup.

You're calling $form2.validate(), when you should be calling $form2.validate($form2.validationGroup), no?

@marcandre :
While $form2.validate($form2.validationGroup) does fix the latter problem, being forced to access the custom property validationGroup to my instance just to get access to the name of the validation group feels like a dirty hack.
The validation group should be present in formInstance when validate is called with a parameter.
Also, for other use cases it makes sense to by able to pass custom parameters, to further refine the behavior of the validation callback.
The code I'm currently using :
jQuery('.control').click(function(e) {
    $form2.validationGroup = $(e.target).data("validationgroup");
    if (! $form2.validate($form2.validationGroup)) {
        e.preventDefault();
    }
});

var $form2 = jQuery('#form').parsley().subscribe('parsley:form:validate', function(formInstance) {
    if (!formInstance.isValid(formInstance.validationGroup)) {
        if (typeof (formInstance.submitEvent) !== typeof (undefined)) {
            // else stop form submission
            formInstance.submitEvent.preventDefault();
        }
    }
    return;
});

Latest version passes the parsleyInstance as last parameter. I believe this solves this issue :smile:


Unknown File - hallo.ts

File pages/api/hallo.ts
See if the file needed in the project
if not: remove it from the project

@MichalPorag  I'd like to take the issue (:


Update useNetlifyIdentity.js

Return Gotrue Token, so devs can choose whether or not to use the authorizedFetch function

Hey, thanks for the PR and thoughts! I'm actually going to opt to not include this feature at this time. Part of this library is to fully encapsulate the gotrue-js library and a part of that is not exposing it to the consumer of this library. Ideally the consumer of this library shouldn't have to think about gotrue-js at all. They shouldn't have to learn about or be concerned about the underlying GoTrue Token. In that sense, I don't want to expose it.
Folks can use authorizedFetch when they want, but if they don't want that they can always use the default, standard fetch too. I'm not totally sure what problem this PR aims to fix!

Thanks for your feedback Jon!
However many people don't want to use fetch but instead use something like axios. When I have the GoTrue Token I can make the decision which one to use...


Support for RTU “server”

I'm submitting a ...
Feature

( x ) feature request

What is the motivation / use case for changing the behavior?
 have been working with these nodes for some time now and everything works as expected. Currently bringing in data from multiple sources and assigning it to the desired registers. Able to retrieve those values from other third party devices as expected. Utilizing the modbus flex server via node red as it lends itself well to being able to gather data from multiple data sources via multiple protocols and consolidate them into a single modbus tcp server. That being said, while most people are not generally going this direction, there are some times where a local serial connection from a field device to node red would be useful. Looking to see if it would be possible to add a configuration to the modbus flex server node to accommodate rs485 requests.
Node red SOAP / SNMP / MODBUS TCP -> modbus flex server -> modbus rtu master. Modbus RTU master being a third party device querying the flex server.
Current behavior

( x ) I am using just the Node-RED package and got modbus-serial package installed with it
( x ) I have installed modbus-serial package global from source (using git clone)
( x ) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial.
The node-modbus package is just for the Modbus Server node.

Device :

( ) macOS: v
( x ) Linux: Ubuntu 18.6
( ) Windows: v
( ) Raspbian: v
( ) Other:

Name:
Version:

Hi, like #123 ?

Apologies I created this thread from my phone which made it difficult to add much clarity around my question.
Attached are two pictures -
full flow:

records read from a .csv
pulling out just the part required for the payload of the SOAP call
results returned and scaled (for decimal place within modbus)
joined back together with the corresponding description of the value being returned
formatted to be sent to influxdb
formatted for MODBUS Flex Server

Modus Flex Server Config:
My question is more around this node specifically.  Right now I am able to point modbus TCP requests at my instance of Node Red / device (unit-id) / register(s) I am storing the data in and get the correct response back.  No problem all good there.
Now what I am curious about is if there is a way either within this same node or some combo of other nodes to have it also listen for requests on a serial port (usb to rs485).
What I am after here is to be able to utilize Node-Red to collect data from multiple sources feed that to an instance of influx for my own purposes as well as expose that data to a third party MODBUS Master via rs485.
In this case node red would need to act as a modbus slave which as mentioned it already does for TCP no problem.  What I cant seem to locate or wrap my head around is how to retrieve that same data locally over serial.
Modbus Master initiate request for register 30006 over RS485 connected directly to Node-Red.  Node-Red respond with corresponding register value.
Thank you,

quick aside for not only this project but others I see you are involved in... I have access to plenty of MODBUS (IP or Serial) / SOAP / BACNET (IP or MSTP) / SNMP / etc. devices if further testing or evaluation / troubleshooting is ever needed.  Have been looking for a way to contribute to these projects as I see great value in the flexibility node-red offers.


[Feature Request] Spray Properties tool in Palette UI

Problem: when you have the larger model (meaning with many elements and several different properties ) it is tiresome to selectively apply property value to several elements in the view.
I would like to use the tool such as known from the photographic management tools like Adobe Lightroom.  (Or format "sprayer" from Office tools).
The usage:

select the element with desired property value
click on the sprayer tool
modal window opens with request which properties you want to spray - select and click [Spray] button
cursor is changed to spray cursor
navigate across the view and click on elements where you want to update or create the selected properties
click on any other tool in the palette to finish the task

What is the underlying problem? Is it:
"Be able to easily add existing property key/value pairs to selected objects"
If so, a "spray" tool is not really the ideal solution as this kind of thing is more suited to UI elements.

@Phillipus You are correct we should distinguish between mass applying the visual representation (ala Office spray) and property setting.
Those might be 2 cases. I would like to conclude here on the property setting.
I think the desired approach is still valid. Only the naming + icon of the tool should be different.

The other approach is:

multi select the elements, where the property is to be updated
change the property in the Properties list to apply across selected elements

This would require to rework the Properties listview.

I feel that the seal use case is simply to enable user to create and use profiles in Archi.

I have read through profiles and I am still suggesting the idea of the tool for stamping the properties onto elements.
"Stamp" is rather the valid tool in our case, apology for the spray (which comes from Adobe Lightroom).


Update instructions to only publish package configuration files

When calling php artisan vendor:publish  the provider name should be appended as to avoid publish other packages files.

Thanks, but this is already OK imo. Less to type, and good enough.

People doesn't even type it, just copy paste it.

+1 I had this issue and it created a lot off junk in my project, harder for new users.


[caffe2] Fix contrib/script build

Fixes a missing line in https://github.com/caffe2/caffe2/commit/ff2c9735477e4d5076da4ddfc964eb0fd3c360bf
@zdevito @jamesr66a

Is this not covered in FB contbuild?
On Nov 29, 2017, at 10:49 PM, Dmytro Dzhulgakov <notifications<EMAIL_ADDRESS>wrote:
Fixes a missing line in ff2c973https://github.com/caffe2/caffe2/commit/ff2c9735477e4d5076da4ddfc964eb0fd3c360bf
@zdevitohttps://github.com/zdevito @jamesr66ahttps://github.com/jamesr66a

You can view, comment on, or merge this pull request online at:
https://github.com/caffe2/caffe2/pull/1540
Commit Summary

[caffe2] Fix contrib/script build

File Changes

M caffe2/contrib/CMakeLists.txthttps://github.com/caffe2/caffe2/pull/1540/files#diff-0 (1)

Patch Links:

https://github.com/caffe2/caffe2/pull/1540.patch
https://github.com/caffe2/caffe2/pull/1540.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/caffe2/caffe2/pull/1540, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEd-SFq8YCzBkVogscFV6-pPrdOz-vtXks5s7iXQgaJpZM4Qv_J3.

I just downloaded latest caffe2, ubuntu 16.. installed it successfully.. Still see this error:WARNING:root:Debug message: /home/outkasst/caffe2p3home/caffe2/build/caffe2/python/caffe2_pybind11_state_gpu.so: und
efined symbol: _Py_ZeroStruct
CRITICAL:root:Cannot load caffe2.python. Error: /home/outkasst/caffe2p3home/caffe2/build/caffe2/python/caffe2_pybind
11_state.so: undefined symbol: _Py_ZeroStruct
I am a noob in this, but looks like the above fix in the thread fixes it.. How do i get the fixed version? Or any idea on how to fix this?
thx
Outkasst

@outkasst Your issue is different. It's very likely you have built caffe2 with python2 and then later import it into python3.

@bddppq , hi, how to resolve this issue? I am installing caffe2 inside a virtualenv.. with python3(3.5)..
thx

Hi @bddppq , I have successfully installed the latest Caffe2, but see this error:
`lxbdeMacBook-Pro:~ xiangbinli$ cd caffe2/build/
lxbdeMacBook-Pro:build xiangbinli$ python
Python 3.6.0 |Anaconda custom (64-bit)| (default, Dec 23 2016, 13:19:00)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

from caffe2.python import core
WARNING:root:This caffe2 python run does not have GPU support. Will run in CPU only mode.
WARNING:root:Debug message: No module named 'caffe2.python.caffe2_pybind11_state_gpu'
CRITICAL:root:Cannot load caffe2.python. Error: dlopen(/Users/xiangbinli/caffe2/build/caffe2/python/caffe2_pybind11_state.so, 10): Symbol not found: _PyCObject_Type
Referenced from: /Users/xiangbinli/caffe2/build/caffe2/python/caffe2_pybind11_state.so
Expected in: flat namespace
in /Users/xiangbinli/caffe2/build/caffe2/python/caffe2_pybind11_state.so`

Is the wrong version of python cause that? Thanks a lot!

Hi , I get the same error as @outkasst , but only when running on a jupyter notebook (on a script it works fine ) :
WARNING:root:This caffe2 python run does not have GPU support. Will run in CPU only mode.
WARNING:root:Debug message: /usr/local/caffe2/python/caffe2_pybind11_state_gpu.so: undefined symbol: _Py_ZeroStruct
CRITICAL:root:Cannot load caffe2.python. Error: /usr/local/caffe2/python/caffe2_pybind11_state.so: undefined symbol: _Py_ZeroStruct
An exception has occurred, use %tb to see the full traceback.

SystemExit: 1

/home/sterblue/.local/lib/python3.5/site-packages/IPython/core/interactiveshell.py:2918: UserWarning: To exit: use 'exit', 'quit', or Ctrl-D.
  warn("To exit: use 'exit', 'quit', or Ctrl-D.", stacklevel=1)


Make stepping with debugger possible - resolve steps immediately

What are you trying to achieve?
Stepping using debugger while watching test execution in browser.
What do you get instead?
I get a bunch of promises that evaluate immediately, meaning the browser does nothing until I hit pause() or the test completes, then the commands start to execute.
/// <reference path="../steps.d.ts" />

Feature('Checking debug');

Scenario('test something', (I) => {
  I.amOnPage("/");
  I.see("CRM Online");
  pause(); // or a breakpoint
  I.see("Log in with your registered account");
  I.click("Next");
  // step to here, and browser is still not doing anything.
});

Details

CodeceptJS version: 1.3.0
NodeJS Version: 8.11.3
Operating System: win10 64bit

That's why we have pause() 🤗
If you want TRUE step-by-step execution just put it into async function and add await for each operator.
But basically you don't need to do the heavy debugging unless you are fixing something in CodeceptJS core... For everything else you have pause()

Some people just want to single step.
I'll see if the await-everything solution satisfies them.

I'm planning to improve pause() to provide step-by-step debugging experience.
But not sure when

Proper debugging is still no possible ?

I am looking for some help doing the same thing in vs code, stepping through my codeceptjs async scenario one line at a time without adding await before each line.  The same thing is happening to me as the first comment, when I step over a console log, it prints to the console.  But any other step does not execute until the end of the scenario unless I add the await command before it.  I see the last entry here is from 2018, has anything changed to make this possible?


confirm: fix fast click input cannot get beyboard instantly

Please makes sure the items are checked before submitting your PR, thank you!

[x] Rebase before creating a PR to keep commit history clear.
[x] Only One commit
[x] No eslint errors

Codecov Report

Merging #3420 into v2 will decrease coverage by 0.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##               v2    #3420     +/-   ##
=========================================
- Coverage   19.41%   19.32%   -0.1%
=========================================
  Files         226      226
  Lines        5603     5609      +6
  Branches      710      712      +2
=========================================
- Hits         1088     1084      -4
- Misses       4396     4406     +10
  Partials      119      119

Impacted Files
Coverage Δ

src/components/confirm/index.vue
9.09% <0%> (-2.03%)
:arrow_down:

src/components/inline-calendar/util.js
71.76% <0%> (-7.06%)
:arrow_down:

src/components/selector/index.vue
18.6% <0%> (+4.65%)
:arrow_up:

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 94c5ab7...5b4db59. Read the comment docs.


[Feature Request] Integration with Prisma Extensions

Is your feature request related to a problem? Please describe.
I am using several prisma extensions that modify the default prisma client and change the query section to add custom computed fields. how can I integrate this with zenstack?

Hi @sakgoyal , could you check if this fresh new doc helps 😄?
https://zenstack.dev/docs/guides/client-extensions

Oh perfect. Thank you. I didn't see this before


SuperMD span support, PRETTY PLEASE

Zine currently supports SECTION directive for formatting a block of text but no in-line directive within a SuperMD document (e.g. ).
The ability to apply CSS formats to a SECTION is WONDEFUL. But I would really like to also be able to apply CSS to certain selection of text within a SuperMD file (i.e. beyond what Markdown already supports like bold, italic). And it seems to me that this feature would be very similar to implement to the $link directive.
e.g.
My paragraph/table includes [this span text]($span.attrs("mycolor","myfont")) and more.
FWIW, I think this SPAN-support is pretty much the only missing functionality preventing me from switching from Hugo today. I otherwise really like how simple the Zine syntax is compared to Hugo.

FWIW, I think this SPAN-support is pretty much the only missing functionality preventing me from switching from Hugo. I otherwise really like how simple the Zine syntax is compared to Hugo.

Implemented as $text in v0.7.1, enjoy.

Awesome! THANKS!


Fixing security role logic to handle missing privileges

modifying logic to allow for priveleges that do not exist to not fail the script

Hm ... isn't
if (not priv.startswith('nx-repository-') and priv in privmap) or priv in privmap:

the same as
if priv in privmap:

?

If I remember correctly, the idea here was to only filter out autogenerated privileges that didn't exist. If you create a privilege in Nexus and then delete it, it will always (as far as I'm aware) remove that privilege from any roles that use it.  This is a bug in Nexus, and this code prevents said bug from crashing the migrator.
The thing is, I don't know of any other situations where a privilege will be referenced by a role, yet not exist. If I don't know what those situations are (or even if there are any), then I don't know what the right thing to do is in those situations, and I certainly don't know that the right thing is to remove that privilege from the role without notifying the user. The only correct choice is to allow it to fail, until we know for certain what should be done instead.
I wonder why you made this PR? Specifically, did you encounter a crash because of this logic? If so, we can try to discover the source of the problem, which will allow us to decide what the appropriate change should be.

Here's what I found (and I'm not immediately at my work computer, but can get some additional debug logs once I am). When running the initial configuration, it would consistently fail to read the security settings successfully.
I added some debug messages, I found that an existing (Nexus-created) role, had 7 privileges tied to it. Something like nx-repository-view-*, then it had 6 "T" priveleges...T1, T2, T3, T4, T5, T6. I found that 3 of those privileges mapped correctly to current privileges that the role had applied (I think T1, T3, and T5 were ok). But T2, T4, and T6 had no privilege in the map. Looking in the Nexus UI, I found the role only had 4 privileges showing, which map to the nx- privilege plus the T1, T3, T5 privileges. So I didn't know of a way to effectively remove the privileges from that role as it didn't appear they should be attached.
What my change would do is verify that any privilege that doesn't start with 'nx-repository-' is available in the privatemap since that would be required in the next line -- and the reason the script failed since T4 wasn't in the map, but it was attempted to be retrieved.

Attached is the debug log file. I added additional info lines to print the privmap and role so that I could see what the role referenced for privileges and what the privilege map contained.
logfile.txt

I see. This instance was upgraded from Nexus 2, correct? Nexus 2 uses these T1, T2, etc names to refer to its handful of built-in privileges. They must have been introduced improperly by the upgrade process.

What my change would do is verify that any privilege that doesn't start with 'nx-repository-' is available in the privatemap since that would be required in the next line -- and the reason the script failed since T4 wasn't in the map, but it was attempted to be retrieved.

The reason the code didn't already do this is because I don't know for a fact that blindly and automatically ignoring these missing privileges is always going to be the right decision. Depending on the situation, assuming a privilege shouldn't exist might be a security problem, and allowing the exception to be thrown during migration is the fastest way to let the user know that something might be wrong, so that's what the current code does in the general case. There is currently one special case when dealing with built-in privileges (which all have names starting with nx-repository-) where I know that ignoring is the proper choice, but in general the safest bet is to throw exceptions until more special cases can be included.

Looking in the Nexus UI, I found the role only had 4 privileges showing, which map to the nx- privilege plus the T1, T3, T5 privileges.

Hm ... that makes me think Nexus is designed to ignore privileges that don't exist, and pretend that roles don't use them. If that's true, your approach would be correct in the general case I think, especially if it turns out that the upgrade process allows broken privileges in general, and it's not some special handling for the built-in ones (the former seems more likely). If that's actually the case, I think I would be okay with accepting this.

What my change would do is verify that any privilege that doesn't start with 'nx-repository-' is available in the privatemap since that would be required in the next line

Your change verifies that privileges that don't start with nx-repository- are in the privmap. The original code already verified that privileges that do start with nx-repository- are in the privmap. The resulting code just verifies that the privilege is in the privmap, so the following is equivalent:
if priv in privmap:
    privs.append(privmap[priv])

 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.Peter Kreidermacher seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing due to age. Please re-open if necessary.


Cache enable with a ttl value always returns cached data

The TTL value is never checked to expire the cached results.

Hi @n3cr0cr0w
I'm publishing the new version of the library, adding some new features:

Cached whois responses
OCR parser (images with email)
Custom providers

v0.5.0 released! :muscle:
https://packagist.org/packages/kevinoo/panorama-whois#0.5.0


feat: bump 'osmpbfreader:0.16'

osmpbfreader fixes a bug with smartstring:1.0.0 which doesn't work with rustc:1.67.0.
See https://github.com/bodil/smartstring/issues/38
smartstring:1.0.1 fixes the problem, version which have been released into osmpbfreader:0.16.0.
See https://github.com/TeXitoi/osmpbfreader-rs/issues/44 and the fix https://github.com/TeXitoi/osmpbfreader-rs/pull/45

@woshilapin you can also bump the version of the crate (0.11.0)

@datanel indeed. Done in ba7c9b9.

can anyone review this pull request please ? @amatissart @antoine-de @remi-dupre

nop, I don't have merge rights anymore, sorry

Thank you for the fix :) sorry for the delay, I was on holidays


Allow changing plex address

My plex is set to prefer secure connections, this means that plex responds with a https address as the first address. This connection is using the plex-generated certificate, which by nature is not trusted on this IP.
My request is twofold, an option to not validate ssl certificates for connections to media server, and the ability to specify the address ourself.

ETV will try all advertised addresses to find one that works. You should add the address you would like to use to Plex's Settings > Network >  Custom server access URLs. After saving those changes, restart ETV and it should update it's list from Plex's API and try each address again. It might also be worth enabling debug logs in ETV's Settings page before doing this so you can see each address that is attempted.

I am aware this is how it is done, thus why the mismatched certificate is a thing. I only have a https endpoint listed as a local LAN  Custom URL, which is not a issue for anything else communicating to plex outside of the docker network.

plex responds with a https address as the first address

The addresses are effectively unordered; ETV will try every address that Plex sends until it finds one that succeeds.

the ability to specify the address ourself

This will not be added to ETV when Plex contains an official way to advertise additional addresses.

an option to not validate ssl certificates for connections to media server

This shouldn't be needed - why are the Plex certificates not trusted? Have you configured DNS rebinding so the plex.direct addresses can succeed?
If you enable debug logs as I suggested you will see all addresses that ETV tries to use; you can also query the database directly with sqlite3 ersatztv.sqlite3 'select Uri from PlexConnection'.

I have no plex.direct in my connection strings. ETV also wasn't happy with the connection it tried to established to my domain (which is overridden in dns to take the direct route, to a valid certificate). The plex clients have no issues with the connections strings.

I'm happy to help troubleshoot when you provide the output of the following command (run in ETV's config folder):
sqlite3 ersatztv.sqlite3 'select Uri from PlexConnection'

Change the hostnames if you desire, but please leave schema, port, private ips, etc intact.

I do plan to come back to this, I just dont have any logs to give atm


WIP : added retry send message

Added RetrySend in swarm as PR for  #364 .

Pull request to issue #364

@g-laz77 it seems that this code does not compile, is this because it is still WIP?

@antonlerner yes. But I will look into the issue

closed due to inactivity


how to solve

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az appservice plan create
Errors:

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az appservice plan create --name {} --sku {} --location {} --resource-group {}

Expected Behavior
Environment Summary
Linux-5.4.0-1067-azure-x86_64-with-debian-10.2 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.6.10
Installer: DEB

azure-cli 2.32.0

Extensions:
ai-examples 0.2.5
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

route to CXP team to help with

@amitsingharoy Thanks for reporting the issue. The error details is blank. Looking at the issue details, I am assuming you are creating an app service plan. Please execute the below commands in order:

az account set --subscription "1234---1234" # set the right subscription id
az group create -l azRegion -n MyResourceGroup # create the resource group
az appservice plan create -g MyResourceGroup -n MyPlan # create a basic web app Plan

Refer the examples here.
Hope this helps. Please let us know if you need any further assistance on this. Awaiting your reply.

@amitsingharoy This is a quick follow-up to check if you had a chance to follow the action plan in my above comment. Please let me know if you are still facing the issue. Awaiting your reply.

@amitsingharoy Please follow the above mentioned action plan once you get a chance. We will now proceed with the closure of this issue. If you need any further assistance, please feel free to reopen this github thread. We would be happy to help.


Marriage in Spain changes

Marriage abroad tool outcomes in Spain are getting a brand new custom outcome.
Technically Spain is a CNI country, however I have decided to create a new outcome for Spain as the majority of the phrases are Spain-specific. It used to be the case before as well, thus making the CNI outcome a bit convoluted (the other two most prominent culprits are Italy and Germany).
This is currently out for fact check.

This is now back from FC, could someone review the latest changes that address FC feedback (commit named "Remove references to sending fee in Spanish outcomes" and onwards)? The older commits have been reviewed in separate branches.

Looks good to me.


Site loads funny in Chrome

This is what I'm seeing in Chrome 38.0.2125.122 on Mac if I load the site over https:

It looks fine in Safari but in Chrome since it looks like the stylesheets are hardcoded to non-https URLs you're getting a failure of some of the css to load.

Using the customized bootstrap.css fixes the issue more or less, is it required to use the http://getbootstrap.com/examples/jumbotron/jumbotron.css?

Sorry for the delay. I noticed the behavior in the screen cap above once or twice a while ago, but not recently and I can't seem to recreate now. Still an issue?

Nope, looks good now. Thanks!

Thanks


[PE-D][Tester D] Out of Bound Index Unchecked

While Linking a flight to a location, the /from and /to input didn't check where the index is out of bound. The image below is the UI after input linklocation /fl 2 /from 1 /to 3, under the case that there is only one location in prescence.

Labels: type.FunctionalityBug severity.Medium
original: chen-jerry-junior/ped#9

Solved. Added check to ensure the input two locations are valid, before performing link operation.


No update of risk state since today

The app does not update the risk state anymore. The error occurs since today. The last successful update has been yesterday at 21:33 CET.
Phone: iPhone SE 2020.

I see, there is a also the same or a similar bug report for android.

@AnOtherMuenchner  See comment https://github.com/corona-warn-app/cwa-app-android/issues/4723#issuecomment-1019450264
should be working now

Thank you!

@AnOtherMuenchner
Can you close this issue?


Crawl LinkedIn skills

Hi! I'm looking for a way to extract a list of skills used by LinkedIn. This used to be not so hard until some two years ago, but not so anymore since the site structure changed. Any ideas on how to extract skill data?

@tedvanderveen Hi, are you talking about all linkedin or in a specific location?
scrapedin only works for profile, and it's extracting the profiles skills, eg.:
skills:
   [ { title: 'Data Analysis', count: '31' },
     { title: 'Research', count: '30' },
     { title: 'Psychology', count: '14' } ],

All LinkedIn skills. Full set. To be able to make sure to use same base set on our site versus what is being used at LinkedIn

@tedvanderveen The best shot about it is looking in their official API because that's about their private data.
In this project, we're only able to collect public data, I'm sorry.


docs: add the list of component using a directive

Fix #1410
Now the list of component will be generated at each build from the content of the "components" folder.
This directive reads the file names, extract the url (based on main) and read the descriptions to build the component list.
I slightly changed the list structure:

I used a simple link instead of a code inline marker
I added a bit of explainantion on the .html suffi
A link to the file in main branch
A description that I set as html comments for each component file.

technical choices:

I used a pure html comment format instead of jinja because bs4 don't know how to parse it
I used pure html in the directive because that very simple with a list. If you would prefer to use a docutils list node instead let me know.

Instead of using BS4, could you just search for the sentinel {# and #} markers? e.g. re.compile(r'(?<={#).*?(?=#})').
A

For anybody arriving here, I'm stucked as I don't manage to use the reference node in the list.
I made a small summary of my tries and findings in this SO post

For anybody arriving here, I'm stucked as I don't manage to use the reference node in the list. I made a small summary of my tries and findings in this SO post

been a while since I dabbled in directly creating docutils reference nodes. Maybe this working example is helpful? It's fairly different in intent but it's short, might be a source of ideas.
https://github.com/mne-tools/mne-python/blob/main/doc/sphinxext/newcontrib_substitutions.py

it finally works: https://pydata-sphinx-theme--1476.org.readthedocs.build/en/1476/user_guide/layout.html#built-in-components-to-insert-into-sections

beautiful!  Since these "docstring" comments in the templates are now becoming part of our user-facing docs, OK if I touch up the wording on them?


[Pointer] Ability to pass a custom object to use on the curved beam

At the moment the curved beam is always made up out of spheres.
It would be good if you could pass a custom object that would be used instead,

Completed with 8baae717f8fd4f71587bae661bdf7535c586f880


UPGMA Trees are None-rooted

This might be an intentional feature, but just in case...
The PDM class's upgma_tree() method produces a "None"-rooted tree, similarly to the default Tree class. Is this on purpose? I can't imagine why a user would assume UPGMA creates an unrooted tree.
Best,
Niko

No, this is a bug. I overlooked setting the rooting state. Will do so. Thanks for pointing it out!

Ok, glad to help. Two more things:

Is this correct practice for rooting/unrooting trees?

root_status = True # False
my_tree.is_rooted = root_status
my_tree.update_bipartitions()

The "nj_tree" method also appears to create None-rooted trees.

Yep! There's more to it under the hood (is_rooted is actually a managed property as is is_unrooted; both is_rooted=True and is_unrooted=False, and vice versa, update the underlying hidden attribute correctly), but for client code that's all there is to it!

Perfect, I'll mark this as closed then.
Thanks for developing this extremely useful library!

No problem.
Thanks for taking the time to report this and other issues and thereby improve the library!
But I'm re-opening this to keep it open till I actually get around to updating the code to set the rooting.

Fixed in 285d33b .


Adds missing schema attributes for Species

I am not a smart human

No-one's perfect! Thus open source fills the gaps! :)


Cover ListPool with benchmarks

Description
As a developer I want to know benefits of using this implementation.
Solution
To be sure how much we get and in which cases cover each use case with benchmarks.

done :)


runtime/pprof: doesn't dump goroutine labels when stacks collected

What version of Go are you using (go version)?

$ go version
1.21.3

What did you do?
when collecting all goroutine call traces for debug purposes (e.g. using gops tool) one expects to see labels associated with goroutines. However, writeGoroutine() with debug>=2 which calls writeGoroutineStacks() do not provide them.
Yet legacy call traces provided with debug<2 in call like this:
pprof.Lookup("goroutine").WriteTo(conn, 1)

provide goroutine labels.
What did you expect to see?
goroutines stacks with labels.
What did you see instead?
goroutines stacks without labels.

Thank you for the report.
Looks like debug=0 and debug=1 worked with Go 1.18 and stopped working with Go 1.19. Looks like debug=2 may never have worked?

Yet legacy call traces provided with debug<2 in call like this:
pprof.Lookup("goroutine").WriteTo(conn, 1)
provide goroutine labels.

It looks to me like this was true for Go 1.18, but is no longer the case.  Seems you faced another "bug"... if you add
	go pprof.Do(context.Background(), pprof.Labels("key123", "val456_VALUE_IS_HERE"), func(ctx context.Context) { time.Sleep(time.Hour) })

you will notice it starts to work with debug=1 (https://go.dev/play/p/lgGnPLuSN1Z).
I'm not sure whether it's an issue with the main thread or labels are applied on spawn of new goroutine only...

Here's some previous discussion of "include labels in debug=2 goroutine profile", but it's mixed in with discussions of adding labels to other profiles: https://github.com/golang/go/issues/23458#issuecomment-620149386 . I don't see an issue specifically for that request / proposal. @mknyszek might have more context paged in on what obstacles we might need to overcome to make that happen.
Yes, I see now that with debug=0 and debug=1, the labels are missing only from the single goroutine that captures the profile. (The finalizer goroutine gets some other special handling, which is working properly.) https://go.dev/play/p/YTkp_laHyly I'll send a CL to repair that and add the missing test.
CC @mknyszek @golang/runtime

@rhysh Is this fixed as of https://go.dev/cl/537515? Closing optimistically; let me know if we should reopen.

@mknyszek I understood this to be a feature request, asking that goroutine labels be included in the debug=2 output. Then while trying to understand the request, I accidentally discovered a bug with debug=0 and =1 which I fixed with CL 537515 — but the original feature request remains unaddressed. I think we should reopen the issue, thanks.

However, writeGoroutine() with debug>=2 which calls writeGoroutineStacks() do not provide them.

Got it, misunderstood. Thanks!

Any chance this to be fixed as it's very important to be able to see labels on goroutines for debugging. Thanks!


[release-v0.25] Set CI config gen. to 0.25.3

If we update our CI config (for the release-v0.25 branch), we should respect the actual promotion we have on Openshift CI / release repo..
/assign @devguyio

I am working on another idea that will also fix this, let me give it a try first
/hold

I am working on another idea that will also fix this, let me give it a try first

we could read the name of the branch too


chore(deps<EMAIL_ADDRESS><EMAIL_ADDRESS>

Description of the Change
Upgrade to<EMAIL_ADDRESS>EDIT: now also<EMAIL_ADDRESS>to see if it fixes "Browser Tests" step.
Benefits
fixes a deprecation warning when installing mocha:
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
Possible Drawbacks
None that I'm aware of.

Coverage remained the same at 94.143% when pulling 9af5d078f2f32193661fe3fede820a301a68745b on AviVahl:debug-4.3.1 into bc8ce0535d2b94c6f4cd3c23a0d9ccce87d6e53b on mochajs:master.

nope. still getting:
TypeError: Cannot read property 'deleteSession' of null
    at SaucelabsLauncher.<anonymous> (/home/runner/work/mocha/mocha/node_modules/karma-sauce-launcher/dist/launcher/launcher.js:139:26)

will re-open PR once master gets fixed, if no one beats me to it.


Ingest text data via Dataset.Text

Difficulty: ★★☆☆☆

Background
AIQC has datasets of multiple types.
As an example, Dataset.Tabular consists of a single File.Tabular. Here, the file contains both features and labels.
Alternatively, the Dataset.Image consists of many Files.Image because images aren't easily structured in a Parquet file.
Problem
There is no way to ingest txt files or strings for NLP.
Solution
Since strings can be easily incorporated into tabular parquet files with dtype protection, and we already have a lot of ways for working with tabular data -- let's attempt to start by ingesting many strings into a single File.Tabular. Where each string sample is just a row in the dataframe.
So the Dataset.Text class would have the creation methods: from_strings(strings:list),  from_folder(), from_pandas():

Construct a pandas dataframe with a specific column txt from the strings. This column could be a default input for by preprocessing and read methods?
Create a File.Tabular from that dataframe.

^ In order to accomplish the above bullets, you could even use the Tabular methods Dataset.Tabular.from_pandas() and Dataset.Image.from_folder() to make this easy.
Discussion
Should the final dataset_type='text', so that preprocessing and other downstream methods know how to handle it?

Although the current implementation for Text Dataset can be subsumed in the Tabular class, I think having a separate dataset type for text will give us more flexibility in future.


feat: cluster deregistration

Description
Implements the deregistration of an Enterprise cluster. The SyncSet is removed and the cluster is soft-deleted afterwards.
Verification Steps

Create an OCM cluster
Run the KFM locally, but don't target this cluster
Register the cluster using the enterprise registration endpoint
Make sure that registration was successful and that the Observability resources have been created
Deregister the cluster by calling the deregistration endpoint
Make sure that the Observability resources are removed, the cluster only soft deleted in the database.

@machi1990 @pawelpaszki @miguelsorianod @ziccardi I've addressed your feedback, would you mind taking another look?

@pb82 - as Manyanda mentioned, unit tests for cluster handler need to be fixed. otherwise I think it looks good

@pawelpaszki @machi1990  all tests are fixed now

@pawelpaszki @machi1990 all tests are fixed now

Thanks @pb82
Looking good now. I've left two more suggestions for the tests. Thanks for having a look!


playing skippable ads on iOS

Hello,
i'm getting
Ad error: AdError 1005: The provided ad type: skippablevideo is not supported.
on iOS Safari, and the main video is not playing. As far as know it doesn't currently support skippable ads, but why does it blocks player from watching the movie.
The media could not be loaded, either because the server or network failed or because the format is not supported
And the play button always in loading state. I have a standard simple config.
        player.ima(imaOptions);
        player.ima.requestAds();
        // Remove controls from the player on iPad to stop native controls from stealing
        // our click
        var contentPlayer =  player.el().getElementsByTagName('video')[0];
        if ((navigator.userAgent.match(/iPad/i) ||
              navigator.userAgent.match(/Android/i)) &&
            contentPlayer.hasAttribute('controls')) {
          contentPlayer.removeAttribute('controls');
        }
        // Initialize the ad container when the video player is clicked, but only the
        // first time it's clicked.
        var startEvent = 'click';
        if (navigator.userAgent.match(/iPhone/i) ||
            navigator.userAgent.match(/iPad/i) ||
            navigator.userAgent.match(/Android/i)) {
          startEvent = 'touchend';
        }
        player.one(startEvent, function() {
            player.ima.initializeAdDisplayContainer();
            player.play();
        })

Movies without ads (Empty VAST file) playing ok.
BTW is there any updates on playing skippable ads on iOS, like on youtube.
Regards,
Tony

Are you still seeing this issue? If I test in our advanced example with a sample skippable tag I see the content play.

fixed all the problems with iPhones by not loading IMA on iPhones at all until it will not support skippable ads. As i'm currently have only skipable ads. As far as i know the problem disappeared, may be it was some cache issue or similar.

This doesn't seem to work, for example paste this sample tag in the advanced example:
https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/single_ad_samples&ciu_szs=300x250&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ct%3Dskippablelinear&correlator={timestamp}

Error:
Ad error: AdError 1005: The provided ad type: skippablevideo is not supported.

According to this thread this is still not supported by the main IMA SDK:
https://groups.google.com/forum/#!msg/ima-sdk/jYE6j4_YCko/m6HuIkM9uKMJ


workspace/configuration Error: Method not implemented yet -> implement

this is like
 :opts                                                 Show current options settings

Idris.Main> :opts
showimplicits = False
showmachinenames = False
shownamespace = False
showtypes = False
eval = normalise
editor = vim

from repl
but should return json with https://github.com/idris-community/idris2-lsp?tab=readme-ov-file#configuration-options
I want to use it to check if setting was already applied https://github.com/ShinKage/idris2-nvim/blob/31776fdafe7536c465d5fea661803fa630486662/lua/idris2/commands.lua#L9-L29

this is incorrect way to do this


Disintegration of MLJModels

Maintenance of MLJModels has become increasingly burdensome for several reasons. Perhaps the biggest problem is that it's centralised approach to providing model API implementations ("glue code") means:

Testing takes a long time. Tolerable, just.

[extras] must include a very large number of packages which invariably cause fatal version conflicts with the packges in [deps] during CI. (As I understand it, during a test, the [deps] are essentially pinned when [extras] are loaded.) Less tolerable.

With the existing package manager, we have no way to specify bounds on the algorithm-providing packages (the ones in [extras]). The latest release compatible with [deps] always get's loaded. If just one (of these many) packages makes a breaking change to the "glue code", then MLJModels CI fails.

While https://github.com/JuliaLang/Pkg.jl/issues/1285 may help with the second and third issue, I don't think that is close to being resolved. We have also observed elsewhere that code loading using Requires.jl can be slower than otherwise. (And there is https://github.com/alan-turing-institute/MLJModels.jl/issues/243)
While the plan has always been for all algorithm-providing packages to implement their MLJ interfaces natively, this is not going to happen quickly. In the meantime, it would be good to address the issues above.
In discussions of the core team, @tlienart has suggested the following remedy: Move the glue code for each package X into its own repository Xglue, with its own testing, and make X an ordinary dependency of  Xglue. (The package Xglue would be purely a "utility" package and essentially invisible to general users.)
Such migrations could be performed incrementally and I believe each migration would trigger only a patch release, basically because the model registry (which tracks where to find glue code) is part of MLJModels (and so is opaque to MLJ).
I think this a good idea and propose beginning this disintegation; See TODO list.
cc @DilumAluthge

See also @tlienart 's earlier post at https://github.com/alan-turing-institute/MLJ.jl/issues/276

Great, and just to stress it, we don't want this to be the rule, we want this to be a temporary solution and hope that the packages for which we end up writing glue code will integrate and own said glue code.
We definitely do not want other package devs with brand new cool packages to suggest a glue package. They should just own the interface like ParallelKMeans, EvoTrees or MLJLinearModels

FWIW, we now have support for storing multiple registered Julia packages inside subdirectories a single Git repository.
So e.g. if I already have a Git repository for my package MyPackage.jl, I can now make a subdirectory inside that repository, and inside that subdirectory I can store a package called MyPackageGlue.jl.

FWIW, we now have support for storing multiple registered Julia packages inside subdirectories a single Git repository.
So e.g. if I already have a Git repository for my package MyPackage.jl, I can now make a subdirectory inside that repository, and inside that subdirectory I can store a package called MyPackageGlue.jl.

This works exactly the same as if MyPackage.jl and MyPackageGlue.jl are stored in different Git repositories. But I figure that at least some people will find it easier/more convenient to store MyPackage.jl and MyPackageGlue.jl in the same Git repository.

that's great! though here I think that having separate repos has the advantage that when eventually the original package (e.g. MultivariateStats) owns the glu code, we can just archive the repo whereas here you'd have to remove a subrepos which might be messier to maintain overall (?)

So it's not a subrepo or anything fancy. It's just a regular folder. So if you want to move the glue code to the main package, just rename and move the files.

Does that explanation make sense?
Here's an example repo with two packages: https://github.com/dilumaluthge/foobar
There's nothing fancy, just regular folders. If you want to move the Bar package code into the Foo package code, just move/rename the files. If you want to delete the Bar package entirely, just delete the files.

@DilumAluthge How do release notes work in a Repo hosting multiple packages?

The idea is that you would make tags that look like this:

PkgA-v1.2.3
PkgB-v4.4.6

In the appropriate tag, you have release notes for the relevant package only.

You can have any system you want of course. That is just a suggestion.

I think this is cool but I also think that in this particular case having separate repos is simple & would help see clearly where the code ought to be & the git history, I have a feeling this will cause more headaches especially for new maintainers. The aim is that this code ends up outside MLJModels and is integrated in other packages so I think having subfolders (I understand it's not subrepos) is just not the right approach here even if it's fully supported by Pkg.

Yeah, given the long term goal here, I think it makes sense to keep these "glue" packages in separate Git repositories.

Packages with implementation code to migrate out to separate package:

[ ] ScikitLearn
[ ] MultivariateStats
[ ] DecisionTree*
[ ] GLM
[ ] LIBSVM
[ ] NaiveBayes
[ ] NearestNeighbors
[ ] XGBoost*

Those marked with * are candidates for algorithm-providing package to host model implementation code.
Others get migrated to new package called "MLJPackageInterface".
Important
The package_name trait should stay the same but the load_path traits will need to reflect new location of the model implementation code. For example:
name = "Birch",
package_name = "ScikitLearn",
load_path = "MLJScikitLearnInterface.Birch"

cc @tlienart

The MLJ.jl README has a very nice visualization of the dependency graph, stored in the repo at https://github.com/alan-turing-institute/MLJ.jl/blob/master/material/MLJ_stack.svg
As we break up MLJModels and MLJBase, we should definitely remember to keep this image up-to-date.

All done 🎉
Thanks to all who helped in this large project, especially @OkonSamuel @tlienart and @ExpandingMan


Front/backend communication refactoring

👍  just a sidenote -- in case you want to be "conventional," I typically use the [WIP] prefix to denote "work-in-progress" PR's, like this one

I don't know if you're still working on it, but have tried 2715372 and still getting https://github.com/ethereumproject/emerald-wallet/issues/311

can't send transaction with ledger

Let's merge it and continue development


Create communication between BCDBs

[ ] Learn how BCDB works
[ ] Fetch data from another BCDB
[ ] Push a request to another BCDB
[ ] Create working POC and host on grid

Each bcdb run with a 3bot ID (registered in explorer)
All BCDB client APIs take optional threebot_id where you can call (local bcdb instance in the cluster) but ask it to get data from remote bcdb represented by  this threebot_id and it will talk to explorer and resolve the ip addres of that instance then talk to it and get data if the data has an ACL containing the hreebot_id of the calling bcdb
for simplicity and remove need for explorer we can provide all bcdbs in a cluster with the same identical peer-file containing ids, ips, publik keys for each node having bcdb


Make POW work on GTSs and Lists the same way numerical functions do

Use a different approach.
Used in conjunction with #832, makes POW work on GTSs.


Disabled URL Encoding of Reserved Characters Caused Signature Mismatch on Some S3-Compatible Storage Servers

Are there any plans to enable URL encoding of reserved characters (e.g., $, @, &, ...) in the SDK core?
In https://github.com/aws/aws-sdk-cpp/blob/master/aws-cpp-sdk-core/source/http/URI.cpp#L124
            switch(c)
            {
                // §2.3 unreserved characters
                case '-': case '_': case '.': case '~':
                // The path section of the URL allow reserved characters to appear unescaped
                // RFC 3986 §2.2 Reserved characters
                // NOTE: this implementation does not accurately implement the RFC on purpose to accommodate for
                // discrepancies in the implementations of URL encoding between AWS services for legacy reasons.
                case '$': case '&': case ',':
                case ':': case '=': case '@':
                    ss << c;
                    break;
                default:
                    ss << '%' << std::setfill('0') << std::setw(2) << (int)((unsigned char)c) << std::setw(0);
            }

Files with reserved characters, for example<EMAIL_ADDRESS>are uploaded to S3 successfully but the request path is not URL encoded (e.g., PUT<EMAIL_ADDRESS>HTTP/1.1). However, some third party S3-compatible storage services (SwiftStack) fail with a signature mismatch because the SDK does not URL encode the path.
It looks like the Python botocore package does enable URL encoding for reserved characters so I am just curious if the C++ SDK will enable URL encoding for reserved characters as well.
What platform/OS are you using?
I am using Linux and macOS platforms:

CentOS 7.5, and
macOS 10.14

Which version of the SDK?
1.7.138 (https://github.com/aws/aws-sdk-cpp/tree/1.7.138)
What compiler are you using? what version?
On Linux, I am using g++ 4.9.2. On macOS, I am using Xcode 10.
What are your CMake arguments?
Can you provide a TRACE level log? (sanitize any sensitive information)

Hi @shanebarnes, thanks for pointing this out.
It might be a bug, I will take a look at it and as always, we're open for contributions, if you have a solution for this in mind.


Added doc for manual promotion and added spock unit tests

References #159

@rtyler @GiriDandu Please review the manual promotions doc

Are the tests only config related?

:+1:


Credentials don't allow per-request configuration

Each credential has its own HTTP pipeline, separate from any service client's. All credentials accept kwargs to get_token but may not pass them through to these pipelines.
Also, azure-core's BearerTokenCredentialPolicy doesn't pass request context to get_token, so per-request configuration provided to a service client won't reach the credential's pipeline.

@chlowell could you provide more information? :)

Per-request pipeline kwargs passed to client methods don't apply to authentication requests because the client's pipeline doesn't pass them to the credential's pipeline. To give a concrete example, when someone calls client.Foo(raw_request_hook=some_callback), the client will call some_callback for the service request but not for a token request, should the credential send one. I opened this issue because although get_token(**kwargs) in the auth policy solves the problem, I believe it requires some more thought. I was uncertain whether blindly passing along all kwargs is a good idea, and how big a problem this is, i.e. what customer scenarios, if any, are blocked by it.