Update Posts “code”

Automatically generated by Netlify CMS

👷 Deploy Preview for festive-saha-f7160e processing.
🔨 Explore the source changes: 2e418790126afaa5dabdc480c507c98b0e91318f
🔍 Inspect the deploy log: https://app.netlify.com/sites/festive-saha-f7160e/deploys/618e98a072187b00073d63d7


Stake not working again - in app browser not opening anymore

Since the last Stake disconnect last night, I cannot connect to any mirror anymore.
It's not opening the modal window with the website for the security verification. I just get "login failed" right away.
Also, Primedice disconnected a few hours back and wont connect anymore. Already changed the API Key but it wont work.

hello,
Update to new version https://github.com/GamblingWonder/Dicebot/releases/tag/<IP_ADDRESS>


fix(ib): Add SVG Support to images.

Fixes #113
Describe the changes you have made in this PR -

Custom Image Builder that supports SVG and falls back to default for other types of images.

Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 10 (10.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 75.692%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ui/views/ib/ib_page_view.dart
1
10
10.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
3855

Relevant Lines:
5093

💛  - Coveralls


[FLINK-33470] Implement restore tests for Join node

What is the purpose of the change
Implement restore tests for Join node
Verifying this change
This change added tests and can be verified as follows:

Added restore tests for Join node which verifies the generated compiled plan with the saved compiled plan

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

I think it looks mostly good. There is one comment from me left and the comments from Timo.  FLINK-33727

Yes.  I've commented on the Flink JIRA; I think the issue is concurrency with the RestoreTestBase implementations.


⚠ Quirk Club Argentina (API endpoint) has degraded performance

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

HTTP code: 200
Response time: 8238 ms

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


[std.algorithm] Improve canFind docs

Improve wording.
Fix wrong LREF.
Don't repeat same array literal in example.
Don't use == true.
Use meaningful lambda parameter names.
Fix typo.
Also fix wrong REF to among.

Ping


Items stay hidden after alch until clicking

Specifically when using F-Keys to swap back to inventory (F1/1 in my case) after alching at least once, whereas clicking the inventory button unhides the items.
Clicking anywhere causes items to return

While I understand why this is the case, I would appreciate if F-Keys were supported too.

Aww dang it. This worked before. It looks like I broke this when fixing #6 (plugin compatibility).
I am getting a fix out for it ASAP.

You can track the release of the new version here: https://github.com/runelite/plugin-hub/pull/6392


Feature Request: Add Setting to open VS Code without default unsaved tab being opened

VSCode Version: 1.13.0
OS Version: Windows 10

Steps to Reproduce:

Close all files/tabs in VS code.
Close VS code.
Open VS code.

The application will open up with a default Untitled-1 tab already open that you can start typing into.
It would be nice to have a setting that allows VS Code to start without opening any tabs. e.g. it looks like this:

The reason this is desirable is I often open VS Code and then open the file I'm after, by using Ctrl+O or the File -> Open Recent menu. This means always having to close the default tab that VS code opened when it started, which is annoying.
Alternatively, you could perhaps still have the default blank tab open with VS Code, but close it automatically once any other file is opened and that tab is still blank.

Looks like this was already reported in https://github.com/Microsoft/vscode/issues/16161 and I missed it when searching, so closing this issue.


spike: Where do Rust docs live?

We don't currently have live docs for Rust, but once we do we should figure out which docs site those belong on.

[ ] Rust tutorials
[ ] Rust API docs
[ ] Might be helpful to explain why there are two versions and guide folks towards a specific version based on their needs

Closed by https://github.com/swimos/swimos-docs/pull/196


Round benchmark time in compact mode

The benchmark time didn't have its precision capped in compact mode, generating entries like this: ... status code 200 in 0.03279600013047457 seconds
This PRs rounds the benchmark time the same way we already round in non-compact mode: rounding to 6 decimal places.

Thanks!


Error: signing escrow-transfer transactions via web-interface & SDK

Expected Result - Broadcast 'escrow_transfer'
Actual Result - General Error: 'Oops! Something went wrong!'
After trying many combinations of arguments I've have been unable to use the steemconnect sign function to successfully create a hot signing link (same result using web interface.)The error page has zero insight into what the issue might be.
Taking the following example can anyone spot if I am doing something obviously wrong. The same parameters work with the steem.js equivalent escrowtransfer() but fail for steemconnect.
via sdk -
          let params = {
            from: 'sambillingham',
            to: 'jeffbernst',
            sbd_amount: '0.000 SBD',
            steem_amount: '1.000 STEEM',
            escrow_id: 28760349,
            agent: 'cutemachine',
            fee: '1.000 STEEM',
            ratification_deadline: '2018-03-24T19:08:45',
            escrow_expiration: '2018-04-20T19:08:45',
            json_meta: JSON.stringify({terms: 'test'})
          }

          steemconnect.sign('escrow-transfer', params);

Try link as such
https://steemconnect.com/sign/escrow-transfer?from=seller&to=buyer&agent=agent&escrow_id=28760349&sbd_amount=0.000 SBD&steem_amount=1.000 STEEM&fee=1.000 STEEM&ratification_deadline='2018-03-24T19%3A08%3A45'&escrow_expiration='2018-04-20T19%3A08%3A45'&json_meta='{"terms"%3A "test"}'
Always returns an error.
thanks.

Operation worked for the user using Steem.js. https://steemd.com/b/20860579#17fa066e898c8765c0b0d1f19e2965a1235f9a6b

hey @bonustrack yes that is the issue. The operation works using steem.js but not with Steemconnect signing. If possible can you please test with Steemconnect SDK or web UI?

Operation worked for the user using Steem.js. https://steemd.com/b/20860579#17fa066e898c8765c0b0d1f19e2965a1235f9a6b visible on this block: https://api.steemjs.com/getBlock?blockNum=20860579

@bonustrack I noticed you edited your comment and added the block data. Can you calrify what you are suggesting here?
I agree there are no issues with steem.js.
Have you tested a similar transaction using the steemconnect sign function?

Thanks for working on #210 so quickly @gregory-latinier.
my issue is with the escrow_id - cause: escrow_transfer.escrow_id = 36071238	 cause: Illegal value: 36071238 (not an integer) do you know the correct way to specify the argument for the escrow_id parameter?

also looking into this. thanks

We need to change escrow_id from string to integer when we parse one of these operations: escrow_transfer, escrow_dispute, escrow_release or escrow_approve.

This is a little more complicated than that.
Those operations are not currently parsed and validated like transfer, vote, etc.
I need to create the different operation helpers that's why I'm changing the difficulty to 2

@Sambillingham we pushed the changes on production can you confirm that everything is working fine by now for you?

@bonustrack I have just tested all of the functionality and it is working. @Sambillingham created this issue because I requested him to help me with it. I also requested you on Discord. Thank you for all the hard work you and the team have done.

@bonustrack Just checked and signing the escrow transaction is now working as expected. Nice work. Thanks for getting this working. Good to close from my perspective. 👊


Phpstan phpcsfix integration via grumphp

For the developers of this module only.
Does no change anything for consumers.
This will integrate grumphp.
So php-cs-fixer and phpstan are trigger automatically before commit.
Checks are ran on on new or updated files only.
Commit is reject if php-cs-fix or phpstan fails.
Also added a composer script to check all files of the module.
composer run fop_check
Features :

no more 'cs fix commits'
ensure minimal code quality
help fixing already submitted code (composer script)

phpstan level is the lowest possible, 0 as a starting point for fixing already pushed code.
This needs to be changed quickly. But I'm not really sure of the level to target.
Any idea ?

To test :

pull the pull request on your computer.
composer update
copy grumphp.yml.dist to grumphp.yml
edit grumphp.yml : fill the path to a local prestashop installation

(don't worry if your installation is not correct, phpstan will warn you).

first commit (6be6e78) is not related to this feature.

@SebSept  i got an error when i try to install it with php7.2

We should consider support it if possible as all the prestashop versions < 1.7.7 use it.

fixed php7.2 compat.
Ready for review

did you have trouble configuring it or was it easy ?
Do you think it could be improved for this point ? @nenes25

@SebSept  everything was working out of the box for me through the command line.
It's less visible when commiting in phpstorm but it does the work :)

Thanks for feedback.
I agree, the balloon it not convenient on phpstorm.


Minor changes to support compilation with both clang and clang++

Could you provide a bit more details to the change? Looks like we're moving a lot of code from the wasi_socket_ext.c to a header file.

Sorry my bad. I selected the wrong file. Will close this and open a new one with the rigth .c file


topoplot channel exclusion

Perhaps more an improvement if the topoplot function could include a channel inclusion argument. For Biosemi at the moment it signal that the external electrodes have overlapping position and thus won't plot anything:
ssvep0[0].topoplot_snr()
ValueError: The following electrodes have overlapping positions, which causes problems during visualization:
EXG1, EXG2, EXG3, EXG4, EXG5, EXG6, EXG7, EXG8, STI 014

Ah interesting! Yes, that's a good idea.

@rb643 I don't think I could ever reproduce this but I think that's because I was maybe using a more up-to-date version of this?
This works for me:
import mne
import ssvepy
from pathlib import Path

file = Path('debug/EG-CTR-0115-Face-Categorisation.bdf')

raw = mne.io.read_raw_edf(
    file, montage=mne.channels.read_montage('biosemi64'),
    eog=[f'EXG{n}' for n in range(1, 9)]
)
raw.info['subject_info'] = {
    'pid': file.name[7:11],
    'group': file.name[3:6]
}

events = mne.find_events(raw)
events = events[events[:, 2] < 255, :]

epochs = mne.Epochs(
    raw, events,
    tmin=0, tmax=4, preload=True
).set_eeg_reference().load_data().apply_proj()

ssvep = ssvepy.Ssvep(epochs, [1.2, 6], compute_tfr=False)

ssvep.topoplot_snr()

I just released a new version, so maybe try and install from there!

Fixed :)


Remove old Parameterized method stubs

Removes deprecated Parameterized methods which were moved onto the .param accessor.

Codecov Report

Merging #592 (34914ed) into master (c4a9e32) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #592      +/-   ##
==========================================
- Coverage   82.05%   81.94%   -0.11%
==========================================
  Files           4        4
  Lines        3014     2941      -73
==========================================
- Hits         2473     2410      -63
+ Misses        541      531      -10

Impacted Files
Coverage Δ

param/parameterized.py
82.18% <ø> (-0.18%)
:arrow_down:

numbergen/__init__.py
79.89% <0.00%> (-0.03%)
:arrow_down:

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 c4a9e32...34914ed. Read the comment docs.

Wooooooo, thanks @maximlt!


Multiple instances draw

https://github.com/vulkano-rs/vulkano/blob/67ace6b1c5e7506dbf623741a7d940d4a77d2298/vulkano/src/command_buffer/auto.rs#L1076
Here is instanceCount param stubbed to 1. Could we add instance_count arg to the method also?
pub fn draw_indexed<V, Gp, S, Pc, Ib, I>(
       mut self, pipeline: Gp, dynamic: DynamicState,
       // instance_count: u32,
       vertices: V, index_buffer: Ib, sets: S, constants: Pc)
         -> Result<Self, DrawIndexedError>

...

    .draw_indexed(ib_infos.num_indices as u32, 1, 0, 0, 0);
    // .draw_indexed(ib_infos.num_indices as u32, instance_count, 0, 0, 0);

Well, I found ::draw() method call an instances buffer ::len() to get instanceCount. I got a result I expected.


Prevent Model from resetting draw commands for picking

This PR refactors Model such that it doesn't resetDrawCommands() every time a feature is picked and colored translucent. Here's the local Sandcastle I used for testing: note that resetDrawCommands() shouldn't be called at any time a picked feature is being colored. In fact, the only time it needs to call resetDrawCommands() in that Sandcastle is for toggling between feature ID labels and custom shaders.
While refactoring this, I also included a fix that closes #10625. Here's the sandcastle to demonstrate that it works (on main it crashes).
Finally, to match Cesium3DTileset's API I added makeStyleDirty(), which forces the Model to reapply its style. This is to account for changes like so:
model.style = ....
style.color = // new color function here

Without makeStyleDirty(), the changes won't take effect. This behavior is the same for Cesium3DTileset.
TODO: write unit tests for the affected files

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

@ptrgags this is ready for review!

To confirm there was a performance improvement, I did some profiling:
I tested picking with b3dms with old Model (1.96) vs. ModelExperimental (1.96) vs. new Model (this branch). For this test I used this modified 3D Tiles Interactivity Sandcastle to profile between the three. I waited for all visible tiles to be loaded (with no additional camera movement), then I recorded the performance for 11 seconds, moving my mouse across the buildings at random so that they would toggle the yellow translucent styling.

Model Version
Result

Model (1.96)

ModelExperimental (1.96)

new Model (this branch)

@ptrgags updated!

Updates look good, thanks @j9liu!


Yup context issues & How to reload the form with his new context

Hi,
Issues that i found are :

When you place a context props to the yup resolver like {context: {test: "test"}} validation trigger no more, specially for the case of abortEarly which have to be set to false to make it rework properly.
I expect the form to work even if abortEarly is not set.
How can i trigger the new validation form if the context has change ?
You can follow this example -> https://codesandbox.io/s/magical-almeida-j941j?file=/src/App.js
User can change his language. If language is 'fr-FR' the test number must less than 2. If language is "en-US" the number must be less than 4.
You can find those logics in the yup schema.
Every times the user change the language i call the trigger method to revalidate the form. Now please follow those steps:
Start typing "6" to the input and you will get an error. The language is set to 'en-US' and must be less than 4. So type 4. The error disappear.
Now switch to the language "fr-FR". Nothing happen ( mode is onChange, reValidateMode is onChange ).
I expect to get an error message to be test must be less than or equal to 2.
Now click on Submit. It's working !
Now reduce the number ( with the bottom arrow ) to switch from 4 to 3. The message disappear.
I expect to have the same error message.
Resubmit and you get your message back.

So i think that you have maybe a sort of cache behind the form for the context that keep in memory the first form state. And if you check the log, the lang switch from "fr-FR" to "en-US" every time you submitted or you typed. So you have to different version of this value in your form. One from the form initialisation, One when you submitted the form.
@bluebill1049  can you help me ?

Thans i will take a look at those issues.

https://github.com/react-hook-form/resolvers/issues/29


Document the contextual diff mode

Related to PR #23 which has been merged, I updated the README so that it mentions the contextual_diff mode existence.
I added some explanation, while trying to keep it as brief as possible. The example section makes sense to me to illustrate the difference between the two modes, but I could remove it if you find it too long.

Thanks @humbertogaliza, I appreciate!


Correction of existing dashboard queries which has reporter

Part of fix for this issue: https://github.com/istio/istio/issues/27595
In this PR, we are mainly fixing the dashboard prometheus queries which hasreporter. Fixes include:
(1) Istio Service Dashboard:

General Section
TCP Received Bytes and TCP Sent Bytes should be reporter=destination (aka, we should presents those two charts from the perspective of the current service)
Service Workloads:
Bytes Received from Incoming TCP Connection and Bytes Sent to Incoming TCP Connection, incoming is for destination that those are incoming requests. Therefore, the reporter=destination here as well.

(2) Istio Mesh Dashboard
Discussed with @douglas-reid , we decide to use reporter=source to be more inclusively have what the traffic is currently happening.
(3) Istio Performance Dashboard
Data rates: Bytes transferred / sec section, to avoid double counting, we are replacing reporter=source+destination to reporter=source
Todo in next PR: need to discuss with the community about how should we treat if a request send from source fails, do they still/also want to count that in for the Istio Workload dashboard or not?
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
81dd5d39a43f1829fe782baa5d03420adc62ca65
link
/test release-notes_istio

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

Tested locally, all fixes being correctly populated to each charts.

/retest

this lgtm. @mandarjog or @nrjpoddar or @howardjohn can one of you sanity check?

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
208b64f52ad06b871dd51fba77a20c253b3569c5
link
/test integ-security-multicluster-tests_istio

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

@carolynhu can you post a raintank link?

This PR needs a release note.

/retest

@carolynhu can you post a raintank link?
sure, i can make the dashboards editable in the raintank only, so that you could check about those updated queries.

https://snapshot.raintank.io/dashboard/snapshot/W20Wit702W8Qo17vlItBbKmei72pNpeQ
https://snapshot.raintank.io/dashboard/snapshot/vUN2InthREw2QalwkNeppumbhH4KP0RM
https://snapshot.raintank.io/dashboard/snapshot/6rGupq0r7vK2NAYqenm9p2uqLDP1GoIz

@mandarjog ptal

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
c78cfeee50fa2c81ad21721b28e2d13221f2461c
link
/test integ-operator-controller-tests_istio

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

@carolynhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
c78cfeee50fa2c81ad21721b28e2d13221f2461c
link
/test integ-operator-controller-tests_istio

integ-telemetry-mc-k8s-tests_istio
c78cfeee50fa2c81ad21721b28e2d13221f2461c
link
/test integ-telemetry-mc-k8s-tests_istio

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

/reset

/retest

In response to a cherrypick label: new pull request created: #29001


Fix dependencies, 1.8 support and update maven's config options

Important:
Instead of using dir for export directly given in pom.xml, I introduce the export_dir variable.
To use it, just add -Dexport_dir='my\dir\to\plugins', or in your software options add key: export_dir and value: my\dir\to\plugins. With this, I'm able too to run this, without getting error that it don't find your own folder.
I fixed:

MySQL pro husk project has changed their repo.
MySQL's method require SQLException.
InventoryGUI was creating error with /pa settings <name> because PlayerSwapHandItemsEvent was not found.

I can't seem to find where 1.8 support has been added, can you explain that please?
Thanks for the PR.

I can't seem to find where 1.8 support has been added, can you explain that please? Thanks for the PR.

Sure. It's with InventoryGUI because the old version had an error with it.


No graph data

I have updated the plugin and uninstalled the eve app and reinstalled it to see the graphs. But, unfortunately, no graph data is shown. Is there another way to enable this?

The first points of the graph should appear after 10-30 minutes after starting homebridge. When you open the details of the empty graph, do you see entries in the measurements list?
Did you set any interval in the plugin? Or do you use the default one of 4 minutes?
Can you start homebridge with the debug option for my plugin and post the output?
sudo DEBUG=homebridge-weather-station-extended homebridge -D -U /var/lib/homebridge
/var/lib/homebridge is my homebridge folder, it might be different depending on your installation. If you are running homebridge as a service, you can either change your start options or stop the service and start homebridge manually with the given example command.

opening the empty graph and looking at measurements, no data is shown
I set the interval to 15 min. Now, I have set is to 4 min and did a reboot, log will be created now

I will post the log when it is running for 30 min. Where can I find the log when I start Homebridge with the syntax you provided.

If you start homebridge with the command, the log will be in your console. If you start homebridge as a service the log should be a part of /var/log/syslog

@naofireblade
Enclosed the logfile
log2.txt

Thanks for your log. I can see that the history module is starting and that 2 datasets are added. But I can't see any request for the history.
Can you provide another log where you close, and reopen the eve app and select the history for e.g. temperature? Homebridge must be running for at least 20 minutes before that.

@naofireblade Enclosed the log file. I can see new entries in de chart. Every 10 min an entry is logged using the DEBUG method. After I restart the Pi the logging stops. The difference is that after the restart Homebridge starts using systemd.
note: I see this only history on the iPhone not on the iPad.
log_2018-02-09.txt

@naofireblade after running Homebridge in debug mode for several hours I stopped the program and started using systemd again. I made one adjustment by setting the debug mode on. It’s running now for 8 hours and all the graphs are recording measurements. Also the graphs for the evohome plugin.

Hm so it's working now? Also with systemd? The debug mode cannot be the reason.

It’s working now. I also use the evohome plugin and I did have the same problems with the graphs. On the iPad I can see the graphs with measurements for the last 24 hours. On the iPhone and still have empty timeframes.
Ps. I did close the eve app several times during logging. And also did some forced refresh. Let’s hope is stays this way 😇

One last thing: can you explain why the iPhone is missing data in certain timeframes while the iPad shows data in the same interval.

I came across problems around this as well. This plugin will set the global timer interval for FakeGatoHistory to 4032 minutes. This may affect other plugins as well since this timer will be shared across different plugins. This timer needs to fire to update the history entries and write the history to the filesystem (new feature of version 0.4.0).
https://github.com/naofireblade/homebridge-weather-station-extended/blob/cf38245b12e58f8d601f664f227d6350a3d8cb6f/index.js#L433
I updated the FakeGatoHistory package to 0.4.0 and replaced the line above with:
this.historyService = new FakeGatoHistoryService("weather", this, {
  storage: 'fs'
});

This resolved the issue of missing history data and added support for the new history persistence feature.

@awein The number ist the max amount of frames, not the interval. I will try to update to the recent fakegato package on the weekend :) .
@tomsteenbakkers The gaps happen when you restart homebridge before pulling the history on all your devices. After a restart homebridge currently no longer knows the old history data and can't provide it to devices that didn't pulled the history yet. This will be solved in the next update when i integrate the new fakegator release.

I'll close this as your initial problem is solved. If you have any other questions please don't hesitate creating a new issue.


Add another GetAppServiceIdentityAsync that only uses token [enhancement]

Hi,
Currently we have a method in IPrincipalExtensions with this signature
public static Task<T> GetAppServiceIdentityAsync<T>(this IPrincipal principal, HttpRequestMessage request) where T : ProviderCredentials, new()

Which is very useful in the context of a controller.
However I have the need to get this credential from the zumo auth token and not from a HttpRequestMessage.
Basically the code only needs the request to read the zumo auth token from its headers (https://github.com/Azure/azure-mobile-apps-net-server/blob/master/src/Microsoft.Azure.Mobile.Server.Authentication/Extensions/IPrincipalExtensions.cs#L53).
So my workaround is to create a fake request with the x-zumo-auth header but I am not very fond of this.
Could we create a method with this signature ?
public static Task<T> GetAppServiceIdentityAsync<T>(this IPrincipal principal, string zumoAuthToken) where T : ProviderCredentials, new()

I can provide a PR in no time: it would only add 5 lines of code as 99% of the logic is shared.
Thanks!

closing this bug as it is a duplicate of https://github.com/Azure/azure-mobile-apps-net-server/issues/87 that I did not see beforehand.


Use static NAN version

Updates #402 by specifying a static NAN version in package.json.

This builds and runs fine on OSX as well as on Travis.  Merge and cut a release, please?

LGTM


[question] Support for room thermostat Danfoss DRS11

I am wondering if it would be possible to somehow add support for Danfoss DRS11 room thermostat. I am able to pair it, but sits at unknown product
"hexId": "0x0002-0x8003-0x8001",
"dbLink": "https://devices.zwave-js.io/?jumpTo=0x0002:0x8003:0x8001:0.0",
"productLabel": "Unknown product 0x8001",
"productDescription": "0x8003",
"manufacturer": "Danfoss",
It is not fully paired, because thermostat won't show temperature (that's done after it is paired successfully). Also, after adding it, it looks like it is woken up, but after some time goes to sleep, and neither of buttons will wake it up.
Full debug info below:
{
  "id": 90,
  "name": "",
  "loc": "",
  "values": [
    {
      "id": "90-114-0-manufacturerId",
      "nodeId": 90,
      "commandClass": 114,
      "commandClassName": "Manufacturer Specific",
      "endpoint": 0,
      "property": "manufacturerId",
      "propertyName": "manufacturerId",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Manufacturer ID",
      "stateless": false,
      "min": 0,
      "max": 65535,
      "list": false,
      "value": 2,
      "lastUpdate":<PHONE_NUMBER>122,
      "newValue": 2
    },
    {
      "id": "90-114-0-productType",
      "nodeId": 90,
      "commandClass": 114,
      "commandClassName": "Manufacturer Specific",
      "endpoint": 0,
      "property": "productType",
      "propertyName": "productType",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Product type",
      "stateless": false,
      "min": 0,
      "max": 65535,
      "list": false,
      "value": 32771,
      "lastUpdate":<PHONE_NUMBER>123,
      "newValue": 32771
    },
    {
      "id": "90-114-0-productId",
      "nodeId": 90,
      "commandClass": 114,
      "commandClassName": "Manufacturer Specific",
      "endpoint": 0,
      "property": "productId",
      "propertyName": "productId",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Product ID",
      "stateless": false,
      "min": 0,
      "max": 65535,
      "list": false,
      "value": 32769,
      "lastUpdate":<PHONE_NUMBER>123,
      "newValue": 32769
    }
  ],
  "groups": [],
  "neighbors": [],
  "ready": true,
  "available": true,
  "hassDevices": {},
  "failed": false,
  "inited": true,
  "hexId": "0x0002-0x8003-0x8001",
  "dbLink": "https://devices.zwave-js.io/?jumpTo=0x0002:0x8003:0x8001:0.0",
  "productLabel": "Unknown product 0x8001",
  "productDescription": "0x8003",
  "manufacturer": "Danfoss",
  "endpointsCount": 0,
  "endpointIndizes": [],
  "isSecure": false,
  "isControllerNode": false,
  "keepAwake": false,
  "deviceClass": {
    "basic": 4,
    "generic": 255,
    "specific": 0
  },
  "deviceId": "2-32769-32771",
  "status": "Asleep",
  "interviewStage": "ProtocolInfo",
  "_name": "NodeID_90",
  "statistics": {
    "commandsTX": 1,
    "commandsRX": 1,
    "commandsDroppedRX": 0,
    "commandsDroppedTX": 0,
    "timeoutResponse": 0
  },
  "manufacturerId": 2,
  "productId": 32769,
  "productType": 32771,
  "protocolVersion": 1,
  "nodeType": 1,
  "security": "None",
  "supportsSecurity": false,
  "supportsBeaming": false,
  "isListening": false,
  "isFrequentListening": false,
  "isRouting": true,
  "maxDataRate": 40000,
  "lastActive":<PHONE_NUMBER>123,
  "isBatteryPowered": false
}

interviewStage": "Protocol Info"

You have to wake it up. The interview isn't finished.

It actually did not work like that.
After factory resetting the sensor, I paired it. ZwaveJS says node was added, and when I look it up, it is all green (means protocol info and node info already completed), device is added, but the only thing it shows is Manufacturer (Danfoss). Rest is unknown. After a while, sleep icon goes to "zzz" indicating device went to sleep.
However it is not paired, because thermostat itself shows temperature on display only when it is paired successfully. So I hit "reinterview node" and once I do that, it never passes "protocol info" again. Neither of buttons will wake it up. It just shows "zzz" and "protocol info" spins forever.

Neither of buttons will wake it up

If the wakeup procedure isn't described in the device manual, try these:

re-insert battery
triple click the buttons instead of single-clicking
use a fresh battery

If nothing helps, try excluding and including it again, this time make a driver log, loglevel debug or silly and attach it here as a file.

Log is attached. It is Node 91.
After I factory reset it, I tried to add it. Here is how it looks right after addition, all green like it has already been interviewed, and is awake (that itself is fishy, because other battery operated devices usually take some time to do protocol and node info after addition).

It sits like that until I do re-interview, then it shows as asleep.

I did try new batteries, no change. Single click, triple click, neither of buttons make any difference. I ended up removing it, factory resetting it and I can pair it back to danfoss on first attempt and it works.
I also do not see DRS11 listed in database, only DRS21.
zwavejs_2021-12-20.log


WIP,MNT: GUI API

This PR follows #10253 and refactors the GUI API, improve testing and overall consistency.

Using Dropdown, Button and HBox there might be a way to develop an alternative of menu bar for ipywidgets. If it works and is consistent with Qt, I'll add it in here too.

Ipywidgets
Qt

I must admit, when the dropdown got back to the menu name it's a bit rough but it works and is consistent with Qt.
I updated testing accordingly.
What do you think @larsoner, @hoechenberger ?

Thanks @GuillaumeFavelier, great improvements to avoid accidental mistakes when using the API 👍


Tags

Task:
Create tags connected to certain categories, topics for tracking content on pages
Additional notes:
Tags are tied to articles by adding them to the doc-page, match the search by path /tag/{tag_name}
Feature acceptance criteria:

Tags must be between the article and its title, styled as a label in block
Tags must be searchable by clicking on it and landing on that specific tag's page, where are all connected articles to it
Tags must represent main categories of topics
There must be the page of all current tags in use on the blog. And it's expected they should also by clicking on them go to the detail tags' page (see p.2 here)

Status: Opened


Non breaking error messages in API test

  delete
Unhandled rejection Error: notifyAdminsOfCollective> can't notify collective.comment.created: no collective found with id null
    at /home/********/project/server/lib/notifications.js:11:2531
    at Generator.next (<anonymous>)
    at Generator.tryCatcher (/home/********/project/node_modules/bluebird/js/release/util.js:16:23)
    at PromiseSpawn._promiseFulfilled (/home/********/project/node_modules/bluebird/js/release/generators.js:97:49)
    at _drainQueueStep (/home/********/project/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/home/********/project/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/home/********/project/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/********/project/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:439:21)
    at process.topLevelDomainCallback (domain.js:131:23)

    ✓ Deletes the conversation when the root comment gets destroyed

  edit
Unhandled rejection Error: notifyAdminsOfCollective> can't notify collective.comment.created: no collective found with id null
    at /home/********/project/server/lib/notifications.js:11:2531
    at Generator.next (<anonymous>)
    at Generator.tryCatcher (/home/********/project/node_modules/bluebird/js/release/util.js:16:23)
    at PromiseSpawn._promiseFulfilled (/home/********/project/node_modules/bluebird/js/release/generators.js:97:49)
    at _drainQueueStep (/home/********/project/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/home/********/project/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/home/********/project/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/********/project/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:439:21)
    at process.topLevelDomainCallback (domain.js:131:23)

Sample run: https://circleci.com/gh/opencollective/opencollective-api/23149
Likely happening in models.Conversations.test.js.
Bonus: models.Conversations.test.js should be wrapped in a root describe call like in every other test files.

Will be solved in https://github.com/opencollective/opencollective-api/pull/2994 (see https://circleci.com/gh/opencollective/opencollective-api/23170?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)


WIP: ica.find_bads_ecg does not pass ch_name to create_ecg_epochs

Currently, if you do something like
ica.find_bads_ecg(raw, "CUSTOM_ECG_NAME")
it will internally create ecg_epochs by calling create_ecg_epochs(inst). The problem with this is that if, for some reason, "CUSTOM_ECG_NAME" is not defined properly as the only ECG channel, it will pick the wrong channels, and possibly create bad ecg epochs.
This should in principle be very rare (which is why it's not been discovered so far), but can happen for example with the HCP files.
This change passes the ch_name to the create_ecg_epochs call.
Still needs a test.
@dengemann makes sense?

Coverage decreased (-10.5%) to 80.305% when pulling d6e404ea7b511eba88da1161c510e9ef125c4a8f on jona-sassenhagen:patch-9 into b25fbf28a83ea45021933d891a74f02b4bdfe5a9 on mne-tools:master.

Add to this: if no ecg events are found, the error message is a somewhat less than optimally helpful ValueError: No matching events found for 999 (event id 999). There should be a better error message. I'd include it in this PR.

Coverage decreased (-8.9%) to 81.949% when pulling e39aea89a1ed7f72c09179523e92ef9474cbb511 on jona-sassenhagen:patch-9 into b25fbf28a83ea45021933d891a74f02b4bdfe5a9 on mne-tools:master.

Coverage decreased (-9.6%) to 81.242% when pulling e39aea89a1ed7f72c09179523e92ef9474cbb511 on jona-sassenhagen:patch-9 into b25fbf28a83ea45021933d891a74f02b4bdfe5a9 on mne-tools:master.

@dengemann I'll let you look at this.
@jona-sassenhagen see why travis complains

Coverage increased (+0.03%) to 90.839% when pulling 9c5fcd5dd5ef095e7a2a3852fecd37e32a8d0141 on jona-sassenhagen:patch-9 into b25fbf28a83ea45021933d891a74f02b4bdfe5a9 on mne-tools:master.

Coverage increased (+0.04%) to 90.853% when pulling e37b8535dd9087e440d37e414535d45c104fd4c5 on jona-sassenhagen:patch-9 into b25fbf28a83ea45021933d891a74f02b4bdfe5a9 on mne-tools:master.

@Eric89GXL do you have an idea of what circleci is telling me here?
ImportError: cannot import name _check_copy_dep

Why did you change a line to import that? Did you have a bad rebase perhaps?

Yeah, very messy :(

I'll just do a new PR, this one's just gonna have an unnecessarily messy commit history.


Unreliable when diffing days to today's date

Description of the Issue and Steps to Reproduce:
(Today's date is 2017/07/26)
Go to https://momentjs.com/
Open dev tools
In the console enter moment().add(30, 'days').diff(moment(), 'days')
Run multiple times. Sometimes you'll get 29 instead of 30.

Environment:
Chrome 59 on OSX
Take a Look at This:
// THE FOLLOWING CODE IS UNRELIABLE

main = function() {
    thirtyDaysFromToday = moment().add(30, 'days')
    today = moment()
    differenceInDays = thirtyDaysFromToday.diff(today, 'days')

    if (differenceInDays !== 30) {
        console.log({
            thirtyDaysFromToday: thirtyDaysFromToday,
            today: today,
            differenceInDays: differenceInDays,
        })
    }

    return differenceInDays
}

count = 0
while (count < 1000) {
    main()
    count++
}

// THE FOLLOWING CODE IS RELIABLE

main = function() {
    thirtyDaysFromToday = moment(moment().add(30, 'days').format('YYYYMMDD'))
    today = moment(moment().format('YYYYMMDD'))
    differenceInDays = thirtyDaysFromToday.diff(today, 'days')

    if (differenceInDays !== 30) {
        console.log({
            thirtyDaysFromToday: thirtyDaysFromToday,
            today: today,
            differenceInDays: differenceInDays,
        })
    }

    return differenceInDays
}

count = 0
while (count < 1000) {
    main()
    count++
}

+1 i thought i was going crazy

Correct. The rounding behavior is such that if it's a millisecond over two days, you get three days. Like so:
var fakeNow = moment();
fakeNow.clone().add(30, 'days').diff(fakeNow, 'days'); //=> 30
fakeNow.clone().add(30, 'days').subtract(1, 'millisecond').diff(fakeNow, 'days'); //=> 29

Since you call moment() twice and then compare them, sometimes those will resolve during different milliseconds. Combine that with rounding and you get what you got. You can do what I did above by making sure that the current time is held in a variable instead of re-queried each time, or you can customize rounding to suit your needs.


clicking checkboxes generated by angular-schema-form cause the error 'cannot read property 'length' of undefined'

Question
I have the following schema and form declared in my controller:
$scope.schema = {
"type": "object",
"properties": {
"s4_0": {
"type": "array",
"title": "CHECKBOXES",
"items": {
"type": "string",
"enum": [
1,
2,
3
]
}
}
}
};
$scope.form = [
    {
        "key": "s4_0",
        "type": "checkboxes",
        "titleMap": [
            {
                "value": "1",
                "name": "box 1"
            },
            {
                "value": "2",
                "name": "box 3"
            },
            {
                "value": "3",
                "name": "box 2"
            }
        ]
    },
    {
        "type": "submit",
        "title": "Submit"
    }
];

My view has the following form declaration:
<form name="myForm"           sf-schema="schema"           sf-form="form"           ng-submit="onSubmit(myForm)"></form>
Actual behaviour
When rendering the checkboxes show correctly but clicking on them gives the following error
angular.js:13424 TypeError: Cannot read property 'length' of undefined
at schema-form.min.js:1
at $watchCollectionAction (angular.js:16734)
at Scope.$digest (angular.js:16869)
at Scope.$apply (angular.js:17133)
at $$debounceViewValueCommit (angular.js:26702)
at $setViewValue (angular.js:26674)
at HTMLInputElement.listener (angular.js:23277)
at HTMLInputElement.dispatch (jquery-1.12.4.min.js:3)
at HTMLInputElement.r.handle (jquery-1.12.4.min.js:3)
When i paste my schema and form into the angular-schema-form playground this works fine but in my app it keeps throwing an error. Also when submitted the value of the field gets saved as "false" instead of the array of options chosen.
Any idea what I could be doing wrong?
I would be happy to post more information that could be more helpful.
@json-schema-form/angular-schema-form-lead

looks like there is already a known bug thats causing this. closing this issue

Reopening this since this schema and form work in the playground so wondering if there's a different issue causing this not to work

@taimoorq I suspect your issue is related to either file ordering or model data on load, either way I can't help further without a plunker, but given it works in the demo app I suggest trying to strip out other parts of the form that may be causing the error to narrow down your search.
Please re-open if you do not feel the question has been answered sufficiently or a demo can be provided.

@Anthropic Sorry bad link. Let me know if this works for you:
https://embed.plnkr.co/xcQ3wfpWgPqvIZirJvdM/

Hey @Anthropic . Just wondering if you were able to view the plunker with that last link?

Hi @taimoorq I missed your follow up, thanks for the nudge!
The line of code your error is on has been removed in dev branch, could you try it with the latest build in develop? I can't see anything obvious causing it, but I am sleepy, remind me on the weekend and I will try to take a better look.

Thanks for the offer @Anthropic.  I didn't have a $scope.model variable set up since im using pouchdb and didn't think i needed it. Added that in and it worked. Looks like the length error is valid, just FYI.
Thanks for your help with this and apologies for the rookie mistake


Jest won't run a specific test spec file from CLI

Do you want to request a feature or report a bug?
Bug report
What is the current behavior?
When I run all my test spec files together jest runs them all. But when I want to run a single spec file using 'jest path/to/my-test.js' I get the following error:
No tests found in C:\Users\User\Documents\folder12 files checked.  testMatch: **/__tests__/**/*.js?(x),**/?(*.)(spec|test).js?(x) - 4 matches   testPathIgnorePatterns: \\node_modules\\ - 12 matchesPattern: .\_tests_\API\tickers.spec.jS - 0 matches error An unexpected error occurred: "Command failed.Exit code: 1
Code structure:
tests
API
tickers.spec.js
What is the expected behavior?
tickers.spec.js should run
Run npx envinfo --preset jest in your project directory and paste the
results here
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz  Binaries:    Yarn: 1.5.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 5.6.0 - C:\Program Files\nodejs\npm.CMD

Seeing as you're on windows, have you tried jest path\to\my-test.js?

kindly include test match in the "jest":{"testMatch":[path that you wants to run]} of package.json.
and then simply write jest in cmd.

Wonder if this PR https://github.com/facebook/jest/pull/5941 fixes it?  You should be able to try this using jest@beta


Hi

I cannot seem to hide this.
How can I make this streamer mode safe?

https://aixxe.net/2017/09/steam-overlay-rendering


Thread interactions and ajax when running with Selenium?

How is HtmlUnit handling the threads when it is run via the driver?
I have been running it on an ajax heavy website according to the faq on your website (niceleysync ajax controller and waitForJs set to 150000) yes some aspects are still not working as expected.
I am now wondering if the main thread goes to sleep after a certain amount of time and does not respond to any followup ajax commands from the server.
Specifically, the parts where I either receive an attachment response in up to a minute after a page loads or a popup window are not working as expected. I am using Selenium waits.
I also seem to have issues when dispatching a click event (var event = new Event(click) and (element.dispatchEvent(event) via javascript.
The code above works perfectly in Firefox when ran in the console, but does not trigger when ran via the js executor in selenium.
Is there a way or a configuration option for the main thread to keep taking in the those requests? Or does it actually do so already?
And the attachment handling you implemented is perfect, sorry for not commenting on the issue earlier. It really makes downloading attachments a breeze!

Thanks for closing - is this solved?

It was related to the other two issues I opened - the click event not firing and the isAttachment triggering only after the full file has been downloaded. One has been closed, the other is on your enhancement list. So thought I would clean up after myself and close these.
I also used VisualVM to check how the threads are spawned.


cluster auto switch connect?

Environment

OS: Centos 7
Erlang/OTP:
EMQ: 2.0.4

Description
A description of the issue
Excuse me ~ I have two node (A and B)
A node and B node on same one cluster , then topic tree copy to other node
If A node connect close ...
How can I setting emqttd cluster of auto switch B node ??


Flutter's release mode prompts Isar.Open error.

Steps to Reproduce
Flutter debug will not report an error when debugging. When packaging the release mode, it will prompt Isar.open to fail.
IsarError: Could not initialize IsarCore library for processor architecture "ios_arm64". If you create a Flutter app, make sure to add isar_flutter_libs to your dependencies.
Invalid argument(s): Failed to lookup symbol 'isar_version': dlsym(RTLD_DEFAULT, isar_version): symbol not found #0
initializeCoreBinary (package:isar/src/native/isar_core.dart:78)
#1      openIsar (package:isar/src/native/open.dart:81)
#2      Isar.open (package:isar/src/isar.dart:107)
#3      initIsarService (package:app/helper/services/isar_service.dart:19)
#4      registerServices (package:app/helper/services/register_services.dart:75)

deps
isar: 3.1.0+1
isar_flutter_libs: 3.1.0+1
isar_generator: 3.1.0+1

Code sample
  final dir = await getApplicationSupportDirectory();
 isar = await Isar.open(
  [
    DWorkSpaceSchema,
  ],
  directory: dir.path,
  maxSizeMiB: 512,
  )

Details

Platform: iPhone 14
Flutter version: 3.7.12
Isar version:  3.1.0+1

[ x ] I searched for similar issues already
[ x ] I filled the details section with the exact device model and version

target 'Runner' do
use_frameworks! :linkage => :static  use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end

After removing 'use_frameworks! :linkage => :static ', 'pod install' cannot be packaged.


Update ONNX feature documentation

@faxu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Replacing this with a PR in the private repo: https://github.com/MicrosoftDocs/azure-docs-pr/pull/95206
#please-close


feat: Add Support for EKS Pod Identity

This pull request implements a new feature to add support for EKS Pod Identity as requested in issue #19
Summary
This pull request introduces support for EKS Pod Identity in the module. The changes include the addition of new variables, resources, and documentation updates to enable the creation of Pod Identity roles and policies.
Changes

Documentation Updates:

Added instructions for enabling Pod Identity role and policy in README.md
Updated examples in README.md to include a new module configuration for Pod Identity.

New Resources:

Created iam_pod_identity.tf to define IAM resources for Pod Identity, including:

aws_iam_policy.pod_identity
aws_iam_role.pod_identity
aws_iam_role_policy_attachment.pod_identity
aws_iam_policy_document.pod_identity_assume

Examples:

Added a new example configuration lbc_with_pod_identity_role in main.tf.

Variables:

Added new variables in variables.tf to support Pod Identity:

pod_identity_role_create
pod_identity_role_name_prefix
pod_identity_policy_enabled
pod_identity_tags

Impact

These changes do not break existing functionality.
Users can now enable Pod Identity support by setting the appropriate variables.

How to Test

Follow the updated instructions in the README.md to enable Pod Identity.
Use the new example configuration in main.tf to test the Pod Identity setup.

Notes

Ensure that the AWS IAM permissions are correctly configured to allow the creation of the new IAM resources.

Closes #19
Please review the changes and provide feedback.

Hi @unitmatrix, adding support for EKS Pod Identity is a welcomed enhancement, but I would like to approach it without renaming existing IRSA related variables as it introduces unnecessary breaking changes. I would try to approach this as a separate functionality with own file, variables etc. Policy itself can be shared.

Reply Message
Hi @jaygridley,
Thank you for your feedback. I have made the following changes to address your concerns:

Separate Functionality:

I have implemented the EKS Pod Identity support as a separate functionality with its own file (iam_pod_identity.tf) and variables.
The existing IRSA-related variables and functionality remain unchanged to avoid any breaking changes.

Shared Policy:

The policy for Pod Identity is defined separately but can be shared if needed.

I believe these changes align with your suggestions and maintain backward compatibility. Please review the updated implementation.
Thank you for your guidance.
Best regards.

Thank you for the requested changes, @jaygridley.
Summary of Changes:

Renamed Variables and Resources:

Updated variable names and resource names to use the eks_pod_identity prefix instead of pod_identity for clarity and consistency.
Example: pod_identity_role_create is now eks_pod_identity_role_create.

Updated Documentation:

Modified the README and example files to reflect the new variable names.

Logical Condition Update:

Updated the logical condition for the creation of the IAM policy document to ensure that EKS pod identity can be implemented independently of the IRSA role.

Please review the changes and let me know if any further adjustments are needed.

I think we just need to update https://github.com/lablabs/terraform-aws-eks-load-balancer-controller/pull/23#issue-2733447671 comment with latest changes in the variables a we are good to go. In the meantime I will try to test this out in our setup.

I am considering one more thing by adding also https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_pod_identity_association into the module. I think it can help with the integration of EKS Pod identity further.

Hi @jaygridley ,
Thank you for the suggestion. I have added the aws_eks_pod_identity_association resource into the module and updated the README accordingly.
Best regards.


Several Improvements

Add option to run Lintian after build
Add option to build via ccache to speed up repeated builds
Use apt cache to speed up package installations
Support DEB_BUILD_PROFILES
Add support for unprivileged podman
Several performance and output improvements

Commenting to confirm that this pull request works well with rootless/unprivileged podman. Tested building a package using Ubuntu 22.04, as well as 23.04 (copy Dockerfile-ubuntu-22.04, change version number in tag). Am not a regular docker-deb-builder user, so cannot comment on other changes.

I'm not sure if it's your patch or my docker version but I needed to use the following patch to make this work
diff --git a/build b/build
index 9ad7e93..e495404 100755
--- a/build
+++ b/build
@@ -113,7 +113,7 @@ if [[ "$depdir" ]]; then
     docker_args+="-v $(abspath "$depdir"):/dependencies:ro "
 fi

-docker_args+="-v $(abspath "$srcdir"):/build/source:O "
+docker_args+="-v $(abspath "$srcdir"):/build/source "
 docker_args+="-v $(abspath "$outdir"):/output "
 docker_args+="-v $(cd "$PROG_DIR"; pwd)/build-helper.sh:/build-helper.sh:ro "
 docker_args+="--mount type=tmpfs,tmpfs-size=4G,destination=/tmp "

Without this the docker command/s errored out as "O" was not a recognised option for the volume.

I'm not sure if it's your patch or my docker version but I needed to use the following patch to make this work
...
Without this the docker command/s errored out as "O" was not a recognised option for the volume.

The overlay volume option seems to be a podman only feature, dropped that change.

Hi @cgzones! I have looked at your work and you have really done a lot of improvements here 🙏
Like I have put in the project description, I intended this project originally as a tutorial.  Back then I had some one-off package that I wanted to build myself and came up with the idea to upload it as an example for others that might be looking to do the same.  I thought this project as something that anyone could go through quickly and understand fully - just a screenful or two of scripts. I would prefer keeping this scope. I think I would have bit tough times testing and supporting full-featured script for a production use case 😅
That said, if you don't mind, would you like to host another project with all your great improvements (ccache, lintian, podman, tmpfs, ansi-color highlights) and I would point that from this project as improved version, better suited for production?

Cool! Thanks for understanding @cgzones. I linked your project here, on the Overview chapter.


Make tests runnable without Rake to enable (IDE) debugging

We are able to run a single test using for example:
rake test_derby TEST=test/db/derby/simple_test.rb TESTOPTS="--name=/test_count_with_limit/"

This also works in an IDE like Rubymine.  However running a single test the regular way fails:
$ jruby test/db/derby/simple_test.rb --name=test_count_with_limit
LoadError: no such file to load -- db/derby
  require at org/jruby/RubyKernel.java:1072
  require at /Users/uwe/.rvm/rubies/jruby-1.7.20/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:54
   (root) at /Users/uwe/workspace/jruby/activerecord-jdbc-adapter/test/db/derby/test_helper.rb:1
  require at org/jruby/RubyKernel.java:1072
   (root) at /Users/uwe/.rvm/rubies/jruby-1.7.20/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:1
   (root) at test/db/derby/simple_test.rb:2

Also running the Rake task with debug enabled fails to stop at break points (at least in my environment).
This makes it very hard to debug and develop the code base.
Is there anything I can do to make debugging with break points work in the current code base?
If not, can we change the test setup to allow running tests directly by loading the test files?

I have a proof of concept for making the tests runnable both from Rake and stand alone.  It involves requiring ```test/test_helper`` in every test file you want to be runnable.

rake is needed to setup the path to ROOT/jdbc-derby ... otherwise running single file tests using rake test_derby TESTOPTS="--name=/int/" ... would prefer to not default to LOAD_PATH manipulation in test helper so manually one can still test against different driver versions.

OK, how about adding the path to the test directory and lib directory at least to be able to load the code and tests, and then load the driver files based on an environment variable like ARJDBC_TEST_DRIVER?
How do you usually set what driver version you want to test against?

usually with a local Gemfile for running the whole suite using rake test_xxx or for running single tests with the load path:  ruby -Ilib:test:../driver_path: test/db/mysql/simple_test.rb --name=...


Unable to activate module

Describe the bug
Trying to activate the module in FoundryVTT but it is greyed out and when you hover over it you get the following message: This module requires a maximum system version of 3.9.0 but your version is 4.0.0.
To Reproduce
Steps to reproduce the behavior:

Go to "two cogs in upper right"
Click on "Manage Modules"
Try to click on "DDB-Importer: A D&D Beyond Integrator"
See error

Expected behavior
Being able to activate the module.
Screenshots

Environment:

Foundry Version 12.331
5e System Version 4.0.0
Module Version 5.2.36
Does this behaviour occur with other modules disabled: Yes

As per announcements on Patron and Discord, this module does not yet support v4.x of the D&D system due to the massive changes for Activities. A limited functionality version will be available this week.

Resolved.


Update bearerTokenAuthenticationPolicy.ts

This adds the ability to send tokens to a URL prefixed with "http://localhost"
Packages impacted by this PR
@azure/core-rest-pipeline
Issues associated with this PR
This PR fixes #25206
Describe the problem that is addressed by this PR
Users are unable to issue requests containing a Bearer token (in cleartext) to their developer servers running locally.
See the description of the referenced issue for more details.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

Simply removing the check entirely, since the calling code controls the url via the endpoint and would know the connection is clear-text if passing a URL prefixed http://.
A boolean option to allow sending tokens over an insecure connection was already attempted but later reverted.
An option with a callback could be used to provided more granular (per request) control.
A generated autorest typescript client could avoid calling into this code and bring its own implementation of this policy.

The suggestion seem to be the most pragmatic, given the allowInsecureConnection option was reverted and this seemed like the least intrusive fix for my immediate issue.
Are there test cases added in this PR? (If not, why?)

I would like to get some early feedback on the feasibility of this PR getting merged before investing the time to write tests for this.

Provide a list of related PRs (if any)

#17517
#17749

Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

cc @joheredi since you're the author of the two PRs I'm referencing above.

not particularly useful to send real, active AAD tokens to insecure endpoints

a local server acting as a mock service, there's no reason to send it a credential

Please correct me if I'm wrong: It's my current understanding that this package (as with autorest in general) is ment to be used in the context of any webservice declared via an Open API spec. In the context of our a dev server (which is not a mock, but our actual server running locally), it accepts access tokens (via an insecure connection) to determine the identity of the "user" performing the request. If we didn't have that we would have to have completely different flows on the client and server to establish this identity, unnecessarily bloating both. And it would make it harder to work on anything involving the issuing and validation of these tokens.
I agree that matching against http://localhost is a bit arbitrary: I would actually prefer that the allowInsecureConnection boolean would be put back in, but I didn't want to suggest that in a PR as it seemed it was already tried and abandoned. A console.warn to make it obvious that tokens are being sent in clear text.
Any attack exploiting this would have to control the endpoint or allowInsecureConnection: I don't see any of these as likely candidates for values controlled by end-users. If they were, the attacker could easily point this to an https:// url in their own control?
To be clear, I would suggest making it the responsibility of the developer to avoid pointing the client to a malicious endpoint. I see that as a good tradeoff between usability and security. While you want secure defaults, there should be no reason for this package to assume the developer using it, don't know what they're doing.

Thank you @kraenhansen for taking the time to explain your scenario. I think I understand much better now. I presume you are using some kind of limited scope like openid / email / profile to uniquely identify the user.
I have a suggestion for how to proceed:

Move back to using an allowInsecureConnection check in this policy
Add a new option to the BearerTokenAuthenticationPolicyOptions that enables the behavior of the previous point. That is to say, only if this new policy option and allowInsecureConnection on the request are set to true will the token be passed along.

That way we know that both the client author and the consumer of the client are opting into this behavior.
Does that sound like it would work for your scenario?

I presume you are using some kind of limited scope like openid / email / profile to uniquely identify the user.

It's just a JWT with a payload that contains a user-id, but I don't think that is important in this context. The important part is that I want the client to authenticate towards the server as it will when it's deployed behind a load balancer (which will be SSL enforced).

Does that sound like it would work for your scenario?

I believe so.

It is inconvenient that I would have to implement a client constructor extending the generated constructor to remove and re-add the bearerTokenAuthenticationPolicy to enable this. I suppose the generator could have a way to expose this to the client author.
As a consumer of the client, it would be great if this could be configured on a per client instance basis and not a per request.

It is inconvenient that I would have to implement a client constructor extending the generated constructor to remove and re-add the bearerTokenAuthenticationPolicy to enable this. I suppose the generator could have a way to expose this to the client author.

We could perhaps make this a bit more ergonomic, though since this is a feature only for developing the SDK package, I think some small amount of overhead is okay. Presumably your SDK consumers wouldn't ever need this option?

As a consumer of the client, it would be great if this could be configured on a per client instance basis and not a per request.

We usually accomplish this using a custom PipelinePolicy. It should be doable to add one using the additionalPolicies option to the client.

I'll close this for now as it doesn't seem to be the right solution and follow up with another PR to fix https://github.com/Azure/azure-sdk-for-js/issues/25206 taking the feedback on this PR into account.


Fix typo in the CLI suggestion for bpftrace

The current suggested command-line for bpftrace trace produces the error:
-bash: syntax error near unexpected token `('

Assuming it's designed for Bash, the $ seems to be missing, which is what this PR fixes.

Ah,tThat's me and my fish shell :)


Markdown grammar fixes

Why:
There was grammar errors.
What's being changed:
A word in the documentation guide.
Check off the following:

[ ] All of the tests are passing.
[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks so much for opening a PR to make this fix @jsgv! I'll update the branch and get this merged once tests are passing 🎉


Adding our own base image to test on Openshift CI

Signed-off-by: Mohammed Zeeshan Ahmed<EMAIL_ADDRESS>What is the purpose of this change? What does it change?

See title

:white_check_mark: odo build 1981 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/e1f88b297d by @mohammedzee1000)

:white_check_mark: odo build 1982 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/be0d03ea66 by @mohammedzee1000)

:white_check_mark: odo build 1983 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/0bd58f8d3d by @mohammedzee1000)


add trigger to automated deployment step

Customer had an issue due to missing step. This restores the missing step and fixes the issue.

The best way to maintain consistency is to keep them separate, just like they are in the docs. Otherwise we end up with different copy-paste procedures for every repo we have, and we'll end up introducing a lot of overhead and more mistakes in the process.

The best way to maintain consistency is to keep them separate, just like they are in the docs. Otherwise we end up with different copy-paste procedures for every repo we have, and we'll end up introducing a lot of overhead and more mistakes in the process. @idohalevi

I'm talking about taking some stuff off. I can't see how your comment is related. It will save us from issues that got us to this PR in the first place


[release-1.13] Fix sync issue in GCP platform

Manual cherrypick required.
#40700 failed to apply on top of branch "release-1.13":
Applying: Fix sync issue in GCP platform
Using index info to reconstruct a base tree...
M	pkg/bootstrap/platform/gcp.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/bootstrap/platform/gcp.go
CONFLICT (content): Merge conflict in pkg/bootstrap/platform/gcp.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix sync issue in GCP platform
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

https://github.com/istio/istio/pull/40791 has been merged. This issue is closed.


Can't use Github for mac and Chrome with Atom together.

Recently I use atom to coding in my work. But after some time, I found Github for mac can't push, pull sync, commit. It also tell me file exists or something. At the mean time Goolge Chrome browser cant load any page either. Quit atom, all things get back. Github can commit, pull, push, sync, and Chrome can load page. I don't know what happened, but every time this happen, I just restart atom.
Atom version: 0.16x ~ 0.17x, I can't remember if an ealier version had this issue.
Here's my installed packages.
atom-beautify
auto-update-packages
autocomplete-gocode
autocomplete-paths
autocomplete-plus
autocomplete-snippets
compass
emmet
file-icons
git-plus
hex
project-manager
save-session
seti-syntax
seti-ui
webbox-color

What versions of OS X and GitHub for Mac are you running?

Can you report the exact error message that GitHub for Mac shows?

I can confirm this behavior and was collecting data for a bug report.
The issue is broader; no further processes can be forked.
This issue was present for me since 0.14x.

Huh, I've never experienced this on OS X 10.10.x. @achalatsis I'd like to see what you find

OS X 10.10.1
Github for Mac Honourary Brit (194)

Here's a screenshot.
When I want to commit, Github for Mac tell me file exists. Restart Atom will resolve this.

By the way, this time I found Photoshop can't lanuch either...

This looks like a GitHub for Mac issue and not something we will be able to fix here.
Please reach out to GitHub Support via https://github.com/contact if you are still experiencing this issue.
I'll be able to follow the ticket in our help system and try to figure out how Atom may be impacting GitHub for Mac.

This is NOT a GitHub for Mac only issue (note that the original poster said it also affects Chrome, not just GitHub for Mac). I see similar issues when running Atom on my Mac. At some point after running Atom, Chrome will not longer open Web pages (or shows a web page crashed), SourceTree fails on commits, running node in the terminal can no longer exec, etc. Basically once an hour I need to quit and relaunch Atom to make things work. I have never seen any odd app to app interaction like this on my Mac before. I will try to diagnose further, but am unsure why other Mac users are not seeing this as well. I will see if I can get any more console log files to help diagnose.

I will see if I can get any more console log files to help diagnose.

That would be great, any further details would be great, perhaps also checking the Activity Monitor when this happens and seeing how many Atom Helper processes exist when this starts happening and what their CPU and memory usage is.

Just had things error again and this is what I see:

Activity monitor shows 6 Atom Helpers
cpu usage is low (0.1 %), 27 threads
Atom memory is 80 MB, helpers are between 100 and 400 MB

Spawning a node command gets this:
npm ERR! argv "node" "/Users/bpillow/.nvm/versions/node/v0.12.2/bin/npm" "run" "jsnotebooks"
npm ERR! node v0.12.2
npm ERR! npm  v2.10.0
npm ERR! file sh
npm ERR! path sh
npm ERR! code ELIFECYCLE
npm ERR! errno EAGAIN
npm ERR! syscall spawn sh

At this point, most new Chrome windows end up in "Aw Snap" (crashed). No useful output in the console :-( Sometimes if I wait a bit (without exiting Atom), reloading some Chrome windows will work, intermittently. I've just never seen anything like this on a Mac where one app can affect another in this way. FWIW, I am on Yosemite, 10.10.4

Apparently this is not an Electron issue. My apologies. After seeing a related bug report (https://github.com/facebook/nuclide/issues/84) over on the Nuclide repo, I removed all my Nuclide packages. Since I did that, I have had none of the issues reported here. It seems Nuclide has the problem (perhaps from some native modules it uses?). When the issue occurs, it prevents other processes from spawning child processes. This causes new pages in chrome, SourceTree commits, npm commands, etc. to all fail, as they spawn child process that end up returning an error. I believe you can close this out and we can hope that Nuclide gets fixed at some point.

I never use Nuclide packages, and this happens. So I dont think it's a Nuclide issue.

Odd, that getting rid of Nuclide worked for me. Perhaps their use just exacerbates some underlying issue in Atom (I meant Atom, not Electron in my previous post)?


Is it possible to store all epochs instead of just evert Xth?

I assume that this would result in smoother curves. Maybe we also miss something in the oscillation if we don't store all of them.
@gfrogat, would this be possible? Or is that a storage/runtime problem?

Might get very large for many runs. Also the database size scales with the number of instances.
I’ll generate a complete database in the next days and report the numbers.

One possibility is to quantize the softmax probabilities to Integers [0-255]. Error is relatively small ~ 0.004 and we're quantizing it anyway when generating the softmax heatmaps. Was able to reduce the size of a test database from 240 to 80 Megabytes.
Quantizing is fine as long as we don't start to compute new stuff from the softmax probabilities (e.g. (cross)entropy).
If we store a complete run we're over 2 GB.
It really depends on what we need and want to do

For recent runs @HendrikStrobelt and @gfrogat will store all epochs.
Therefore I close this issue. Please open a new issue, if there is a specific request.


feat(nav): FOR POC ONLY _ NOT TO BE MERGED! (VIV-000)

was opened only for POC.
WAs done in:
https://github.com/Vonage/vivid-3/pull/1512
https://github.com/Vonage/vivid-3/pull/1672


[FR] use the Terminal as a console output

I would really love to see the possibility to use a terminal as console output.
The reason is that we would benefit from all amazing features from xterm.js
Obviously one is colour output.
There are actually 2 ways to do that:

give the possibility to run a command inside the Terminal while listening for stdout, stderr, close. Also this would allow stdin! Which would be amazing from for extensions!
allow to "append" text to the console without it executing a command.

I can give more details on what i am trying to achieve if necessary

@farfromrefug the general desire is understood, but can you be more precise when you want to use the terminal as console output: when running tasks? when debugging a program?

@egamma The idea came from my vscode extension. It's an extension to build Titanium Mobile projects (kind of like PhoneGap projects).
From the get i wanted to have a more interactive/beautiful console. I wanted a colorized console so that i could quickly and easily read the output.
So at first i used the "output colorizer" extension. It worked quite well but was really slow with long outputs, and it broke links to code (like test.js:23:2)
Now i know what xterm.js can do and i know it can fill all my requirements and even more:

colors: well it would work right away, and i could even use the power of  node utils to colorize even more
links: this could be handled using the linkify addon of xterm.js. Even better, we could imagine an entry point for extensions to add new regexpfor links, and "override" the default "click" behavior.
stdin: well this could be very useful for extensions running command line commands. As they could use the stdin of the terminal.

I know it would require quite some work on you side, but the benefit for extensions would be quite awesome! ;)

@farfromrefug VS Code has an integrated terminal and the terminal provides API to launch a process that runs in the terminal (extensions are already using this support).
We are planning to run VS Code tasks inside the terminal and for that we are investigating into enriching the terminal API further.

This would be resolved if vscode had an API to launch a Node process in the terminal like how Language Servers are launched (i.e. using vscode's Node binaries).

@egamma Yes there is an api for the terminal. But we can't do much with it, we miss big features:

clear the terminal
run command and "listen" for it like you would do with exec/spawn
listen for stdin
enable / disable addon (like linkify)
add your own addon to xterm.js
disable stdin (to create a console)

@farfromrefug good suggestions, could you split this issue out into individual API requests?
The listen ones are already captured here https://github.com/Microsoft/vscode/issues/13337, and we currently don't use any xterm.js addons, nor are they particularly polished upstream.

Thanks for creating the issues @farfromrefug, I'll close this off in favor of them now


GHC version check appears to not be correct

Reported by @jneira
Error while checking GHC version: "D:\\\\bin\\\\stack\\\\x86_64-windows\\\\ghc-8.8.3\\\\lib\\bin\\ghc: readCreateProcess: does not exist (No such file or directory)"

Reported at the bottom of this comment with no further details.
https://github.com/mpickering/ghcide/pull/32#issuecomment-626235387
@pepeiborra

This is the expected behaviour if ghc-check cannot figure out the runtime version of GHC: print the underlying exception and continue the execution.
Would it help if we change the print line to make this explicit? E.g.
Warning: unable to validate that ghcide was compiled with the same version of GHC: ...

I have opened a separate issue in the ghc-check tracker to investigate why the logic to guess the ghc binary location didn't work in this case, as I have not tested it with stack:
https://github.com/pepeiborra/ghc-check/issues/2

Just in case the ghc executables is not in D:\\\\bin\\\\stack\\\\x86_64-windows\\\\ghc-8.8.3\\\\lib\\bin\\ghc but in D:\bin\stack\x86_64-windows\ghc-8.8.3\bin\ghc
I ws not using stack but cabal (in ghc codebase using the script that builds with cabal), it turns out that i use the ghc's installed by stack for cabal too.

Thanks, turns out the GHC installation layout is different in Windows. I'll update the logic in ghc-check

I copied all contents of one folder to another. Stupid, but it worked.

Afaik ghc-check already has the fix for that


Breaking change from version 3.6.* to 3.9.*

I'm using version 3.6.3, and I implemented my own inheritor of IEntityFrameworkSecondLevelCacheProvider
Inside that implementation, I'm using IReaderWriterLockProvider.
I've tried to upgrade to 3.9.*, but the code doesn't compile anymore, because IReaderWriterLockProvider has been removed.
Breaking changes are normal/expected for major version bumps, but are very unusual for minor versions bumps.
My suggestion is to comply with Semantic Versioning 2.0.0 and:

Reintroduce IReaderWriterLockProvider interface and it's implementor in 3.* versions, in order to keep uniform compatibility
Bump up the current release to major version to 4.*, so that user knows that there are breaking changes

I don't want to do that, and you have no right to tell me what to do.


Fix potrace link

I noticed that the potrace link points to rembg as well. Not sure if the Sourceforge link is what you want. I also found a GitHub mirror.

Sorry for the slow response on this one, thanks for the catch! I'll merge this fix in


tdigest aggregation and post aggregation are missing

I was trying out the tdigest module in druid. Looks like this library currently does not support it.
Query Example:
{
    "queryType": "groupBy",
    "dataSource": "rollup-data1",
    "granularity": "ALL",
    "dimensions": [],
    "aggregations": [{
        "type": "tDigestSketch",
        "name": "merged_sketch",
        "fieldName": "ingested_sketch",
        "compression": 200
    }],
    "postAggregations": [{
        "type": "quantilesFromTDigestSketch",
        "name": "quantiles",
        "fractions": [0, 0.5, 1],
        "field": {
            "type": "fieldAccess",
            "fieldName": "merged_sketch"
        }
    }],
    "intervals": ["2016-01-01T00:00:00.000Z/2021-05-31T00:00:00.000Z"]
}

Fixed by #26
Closing it :) Thank you @tannaga !


[Email] is mandatory ?

I only want to use it as Slack message but when build a config.ini like below

[Server]
host=localhost
port=5672
username=guest
password=guest
vhost=%2f
queues=tasks
check_rate=10
[Conditions]
ready_queue_size=0
unack_queue_size=0
total_queue_size=0
consumers_connected=1
open_connections=1
nodes_running=1
node_memory_used=100
[Slack]
url=https://hooks.slack.com/services/xoxb-xxxxxx
channel=tasks
username=rabbitmq-barisv-bot

and tries to run it. It says

Traceback (most recent call last):
File "./rabbitmqalert.py", line 160, in
main()
File "./rabbitmqalert.py", line 135, in main
options = optionsresolver.OptionsResover.setup_options()
File "/my-plugins/rabbitmq-alert/rabbitmqalert/optionsresolver.py", line 68, in setup_options
options["email_to"] = cli_arguments.email_to or config_file_options.get("Email", "to")
File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'Email'

Hello @barisvelioglu.
You are right, none of the notification methods should be mandatory in the configuration file.
I'll provide a fix very soon.
Thanks for your time.

Hello again @barisvelioglu.
I created a, somewhat, hotfix as I'm already in the process of refactoring the process of parsing the options, but as said, its still in progress.
Please, get the new version. I would suggest throught ```pip`` (advise the README file of the project).
Thank you.


Few questions about akka-ddd status

Hello,
We in Actor are considering implementing a database-agnostic persistence layer. We are going to use event-sourcing for everything, but it leads us to a question: how we should build dashboards, do analytics, if we don't have a consistent data representation available for use by third-party systems?
We were considering implementing our own solution for synchronizing state of Persistent Actors (like User and Groups names, Group participants, User balances, etc.). But today I've stumbled upon akka-ddd and found out that you already have solutions for this, and now I'm considering an ability to modify akka-ddd for our needs and use it in actor-platform. And contribute our modifications to akka-ddd project too of course.
But before we finally decide use akka-ddd there are some questions:
– Some of our deployments use Cassandra for events persistence. Do I understand right that akka-persistence-* modules needs to be extended for compatibility with akka-ddd? Is there a way to completely replace eventstore-akka-persistence by another akka-persistence-* module?
– We are using protobuf in our client-server protocol, we are migrating our internal server's serialization to it too, using ScalaPB. It is backward- and forward-compatible, fast and produces small-sized serialized data. Is there a way to use custom serialization with akka-ddd?
Thanks for your time, looking forward hearing your feedback!

Hello Andrey,

Is there a way to completely replace eventstore-akka-persistence by another akka-persistence-* module?

Currently Akka Persistence does not support queries (like: give me all events for particular Aggregate Root class). Akka-DDD resolves this problem by using EventStore's projections. The consequence are:

view-update module depends on eventstore-akka-persistence module (so you can not just replace eventstore-akka-persistence module with another one).
if you want to use Saga or Receptor pattern you must provide implementation of EventStreamSubscriber (contained in akka-ddd-messaging module) interface. Currently the only implementation of EventStreamSubscriber exists in eventstore-akka-persistence module.

Suggested approach
Quite recently Akka team has started to work on Improve the Query Side issue. Looks like they have decided to ship first version of this functionality with Akka 2.4-M3 (next milestone of Akka 2.4!). Therefore I would suggest you to consider Akka 2.4 as your target platform if your concern is database agnosticism of the view-update functionality. I believe Akka-DDD could incorporate query-side goodies coming with Akka 2.4.

Is there a way to use custom serialization with akka-ddd?

Core functionality of Akka-DDD is not tied to particular serialization format except functionality provided in pl.newicom.dddd.process package (Receptor and Saga patterns). If you take look at pl.newicom.dddd.office.OfficeInfo you will find JsonSerializationHints class being used. OfficeInfo is used by Receptor/Saga and view-update.
I wish you good luck with your project and hope you can benefit from Akka-DDD and/or Akka-Persistence now or in the near future.

So I think we will implement things manually, looking back to akka-ddd. Thank you for such informative explaination!

@prettynatty - have you made any progress in incorporating Cassandra in akka-ddd? Thanks!

We ended up with our own solution based on Akka Persistence.
Actually we separated C and Q by dumbly putting them into traits, both are mixed into one actor.  We had to do this because we encountered bugs in PersistentViews. We are going to do a real separation after moving to Akka 2.4.0 – it has great opportunities like persistent streams.
Also we've discovered another one project. We liked their simple abstractions and may be we will port them to our CQRS-ish solution.


From private repo

@v-alje : Thanks for your contribution to the Azure documentation! The author, @jonbeck7, has been notified to review your proposed change.


Request for nonexistent InputMap action then getting custom Input action from a plugin

Godot version:

since 3.2.4rc4
(3.2.4rc3 and 3.2.3 work without errors)
OS/device including version:

Linux
Issue description:

tool
extends EditorPlugin

func _input(event):
	if event is InputEventMouseButton:
		print(Input.is_action_just_pressed("click"))

When activating this plugin and clicking  anywhere (the 'click' action is on Mouse Left click), I get the error:
Request for nonexistent InputMap action 'click'.

Steps to reproduce:

Create a project
Add new Input Map action, name it "click" and bind Mouse Left button on it.
Create a plugin with the code above.
Ensure the plugin is enabled (reactivate if needed)
Click somewhere
As you can see the error is printed in Output

Minimal reproduction project:

That's a regression from #40937, CC @27thLiz.
Most likely it means that prior to that PR this script would still not have handled the actions properly, but done so silently?

It seems to me that when tool scripts are executed in editor the Input Map of the editor is used, not the game's one.
May not seem very intuitive at first but IMO this is the way it should work. Probably this should be noted somewhere in the docs.
If you need to use some custom action in editor you can add it via InputMap singleton like this:
func _enter_tree():
	if not InputMap.has_action("click"):
		InputMap.add_action("click")
	var event = InputEventMouseButton.new()
	event.button_index = BUTTON_LEFT
	InputMap.action_add_event("click", event)

The case that you provided would also not work in previous versions with the only difference being the absence of error messages.

I think we can drop the regression label, as even if it looks like one, it's actually a bugfix - previous code would fail silently, now it fails with an explicit error.

Does that mean one should not use is_action_just_pressed from a plugin?

Does that mean one should not use is_action_just_pressed from a plugin?

You can use it, but the actions available are the actions of the editor itself (which should be the same as the built-in ui_* actions also available in projects by default).


[otbn] Produce assembly for modulo exponentiation with OTBN v0.1 syntax

Produce an assembly snippet for doing a modulo exponentiation in the OTBN v0.1 syntax as proposed in #2393.

Assembly is here: https://github.com/felixmiller/ot-dsim/blob/new-isa/asm/otbn_bn.asm

Left to do: add it to the "snippet collection" in the hw/ip/otbn tree.

Just a quick note: this needs a little bit of editing to assemble with the proposed otbn-as tool. The changes I've noticed are:

The first operand of bn.mulqacc.so should have .L or .U rather than .l or .u (or we need to change the docs).
The shifts in calls to bn.addc need a B suffix (so w4 << 16B)
The calls to bn.cmpb have an extra operand (probably was the destination register?)

I just started a PR to add the otbn_bn.asm to a new snippets collection. But I noticed a Chromium licence in the directory: is this a derived work, that needs the chromium licence on it too? @felixmiller (who wrote/rejigged the code).


Region/Konstellation/System Filters

Make it possible to filter the posting of the bot by region / konstellation or system.

Implemented in eb621563d5f8b61c56bf1a3c3f58815c2a81f4e4

implemented in 62428017cb16863f60a8caabab6d87e43140b534


Include ball in radar view?

Great project! Thanks for sharing. I hope to test it out more extensively in the near future.
Is it possible to include the ball position in the radar view? That would give a bit more context to the player movements.

Hi @gdubya 👋🏻 yup, I will probably include it in the radar view.

@SkalskiP Note that including the ball into the radar view is tricky as it is not always on the ground and hence its location will be wrong for flying balls. Any ideas how to tackle this issue?

@SkalskiP Watching the circles that represent the ball position over time, you can often see the parabolic trajectory.  Perhaps there is a way to look at this history to determine if the ball was in the air.  It would likely need to be done as a post processing step as you would need to get the ball path coord history first  and then to try and estimate the height... seems a bit complex though as the camera is often moving as the ball is!

@SkalskiP @gdubya @ms82119 @druefena     Please consider the solution proposed here https://github.com/fenaux/soccer-applications

@fenaux, your work on that is precious; thanks a lot! But I have an issue: the ball is poorly detected in front of the stands. So, the parabolic trajectory is uncompleted. Do you have the same problem?

@clairesecehDS  on which video ? Due to the fact missing detections are replaced by a linear interpolation, if that happens during a parabola, this will lead to false linear segment or false acceleration peak.  If you wish to submit a video please provide a link in my repo. Thanks for your interest.


set 2LD contenthash offchain resolver

Bug Report
Current behavior
we're unable to set content hash when the domain is stored on the blockchain.
Expected behavior
we must be able to store the contenthash the same way we do for subdomains stored in the database
Steps to reproduce

register a domain through the dapp
try setting the contenthash through the gateway

Other information
a possible solution would be to store the contenthash on the texts database instead of the domain since it would be missing when the domain is a 2LD

solved by #161


Difference between Gen 1 vs Gen 2 is never explained?

Why is it that MS documentation never explain the difference between Generation 1 vs Generation 2 VPN Gateway SKU's?
When you configure it you get the option to select Gen1 vs Gen2.  But nowhere in any MS document does it explain why we should prefer one Gen1 over the other.
Now it seems somewhat obvious Gen 2 is newer and use that.  If Gen 1 is older and legacy, why does it still exist after 5 years?  Is there a reason and a time to select Gen1?

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

ID: 45d7ab31-fdf3-9b0f-1439-6a01fb257aab
Version Independent ID: af13a45f-3061-2f0e-7452-b52d700b4805
Content: About Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-about-vpngateways.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@D-Moonesinghe  thanks for your feedback. We shall review it and get back to you soon

@D-Moonesinghe You are correct.
Generation 2 VPN Gateways are newer versions and offer additional features as compared to their Generation 1 counterparts.
For example, Throughput observed per tunnel, Packets per second per tunnel observed, No. of P2S and S2S Connections.
You should choose the SKU and Generation that best fits your scenario and requirement.
Currently, there is no announcement for deprecating Generation 1. You can keep a watch on Microsoft Azure Blog for such updates.

#reassign:aybatra

Articles are updated for SKU information. There is no real description for Gen1 and Gen 2. We'll be closing this issue. #please-close


DockerDetection Fix

Logic was defaulting docker as true even when Player Counter was launched from exe

There are moments where GetEnvironmentVariable can fail here, so I rather try to parse the data, and if it fails for some reason, we can assume it's false; however, other than that it looks pretty good to me.
Thank you 👍


Insert and delete directly on JSON data

The Insert and delete directly on JSON data not working as expected
I try insert and delete directly on Json data but get error : Uncaught Error: Parse error on line 1.
and I would like to know if is possible to insert and delete from directly Json data ?
This is my example:
https://jsfiddle.net/nataliarosa9/u8bgjwe4/

Interesting - looks like you cant delete or insert on json. Hmm. Sounds really strange.
I have to look for examples. I have a feeling this worked in prev. versions.

Hi @nataliarosa9
Did you solve this problem?
I have the same issue.

No, I didn't.
I'm sorry

Tks for the answer!


Add execute_only to bonsai sdk

Future note: we could probably now implement the Executor trait for the BonsaiProver now.


What is the purpose of the 2nd bullet point in "Parsing C++ command-line arguments", given that argv[0] never uses double quotes ('')?

2nd bullet-point in "Parsing C++ command-line arguments":
The first argument (argv[0]) is treated specially. It represents the program name. Because it must be a valid pathname, parts surrounded by double quote marks (") are allowed. The double quote marks aren't included in the argv[0] output. The parts surrounded by double quote marks prevent interpretation of a space or tab character as the end of the argument. The later rules in this list don't apply.
I know that the double quote marks aren't included in the argv[0] output, but the characters themselves, stored in memory at the address given by argv[0], never seem to show double quotes. So, what is the reason for the paragraph above?
I have used the "Example of command-line argument parsing" to arrive at my conclusion:
// command_line_arguments.cpp
// compile with: /EHsc
#include <iostream>

using namespace std;
int main( int argc,      // Number of strings in array argv
          char *argv[],   // Array of command-line argument strings
          char *envp[] )  // Array of environment variable strings
{
    int count;

    // Display each command-line argument.
    cout << "\nCommand-line arguments:\n";
    for( count = 0; count < argc; count++ )
         cout << "  argv[" << count << "]   "
                << argv[count] << "\n";
}

The results I have obtained for argv[1], argv[2] and argv[3] were equivalent to the results shown in the section "Results of parsing command lines", but as I wrote before, the characters contained in argv[0] for each one of those processes, didn't have a double quote ('') in the string of characters.

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

ID: e0c5ec8f-dc90-d0bd-5aa5-1340ccc877c3
Version Independent ID: 19646aca-3da3-14e8-ea9a-fcb3020cf51c
Content: main function and command-line arguments (C++)
Content Source: docs/cpp/main-function-command-line-args.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@jabelloc
The bullet point is meant to draw a distinction between the double-quote processing of the program name and double-quote processing for the rest of the arguments, which is more complex. It isn't possible to create an executable with a double-quote character in the name, so the more complex rules aren't needed. There isn't an easy way to illustrate it, but here's an example of a program name in quotes, using your example code, with the executable renamed to "command line args.exe":
C:\test\command_line_args>"command line args.exe" arg1 "arg 2" "arg ""3"""

Command-line arguments:
  argv[0]   command line args.exe
  argv[1]   arg1
  argv[2]   arg 2
  argv[3]   arg "3"

The example shows the extra processing done for the argv[3] value, which isn't done for the executable name because it isn't needed.