Adding record via API that would generate automatic reverse fails

Hi,
While writing a script to import our existing DNS data I noticed that using API to add a record which results in automatic reverse generation fails with "500 Internal server error". Netbox log shows:
Internal Server Error: /api/plugins/netbox-dns/records/
Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "netbox_dns_record_pkey"
DETAIL:  Key (id)=(773) already exists.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/viewsets.py", line 125, in view
    return self.dispatch(request, *args, **kwargs)
  File "/opt/netbox/netbox/netbox/api/viewsets/__init__.py", line 118, in dispatch
    return super().dispatch(request, *args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/mixins.py", line 19, in create
    self.perform_create(serializer)
  File "/opt/netbox/netbox/netbox/api/viewsets/__init__.py", line 159, in perform_create
    instance = serializer.save()
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 212, in save
    self.instance = self.create(validated_data)
  File "/opt/netbox/netbox/netbox/api/serializers/features.py", line 56, in create
    instance = super().create(validated_data)
  File "/opt/netbox/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 962, in create
    instance = ModelClass._default_manager.create(**validated_data)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/query.py", line 514, in create
    obj.save(force_insert=True, using=self.db)
  File "/opt/netbox/venv/lib/python3.10/site-packages/netbox_dns/models.py", line 737, in save
    super().save(*args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/base.py", line 806, in save
    self.save_base(
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/base.py", line 857, in save_base
    updated = self._save_table(
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/base.py", line 1000, in _save_table
    results = self._do_insert(
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/base.py", line 1041, in _do_insert
    return manager._insert(
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/query.py", line 1434, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/models/sql/compiler.py", line 1621, in execute_sql
    cursor.execute(sql, params)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/netbox/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: duplicate key value violates unique constraint "netbox_dns_record_pkey"
DETAIL:  Key (id)=(773) already exists.

Creating identical record via GUI works and adds the reverse.
Netbox 3.3.5
Netbox-dns 0.13.1

Throwing a 500 error is definitely wrong ... that needs to be addressed.
But could you please provide the API call including data that you used to try to create the record? I occasionally create records using the API (including reverse pointer creation) and never saw that problem. Having your request so I can try to reproduce the failure would help a lot.

Update: I can reproduce it. I think I know what's causing the problem (the save() method for the record is called twice, and the second time causes the exception), but that isnt't (and shouldn't be) an issue when the record is created using the GUI, nor when the tests are calling the methods directly, just with the API.

This is interesting. I just added some logging for debugging purposes and created a new record with the GUI (successful) and then with the API (failed). The issue indeed seems to be the double save() call:
save() called for object test2.zone5.example.com [A]
Calling update_ptr_record() for object test2.zone5.example.com [A]
update_ptr_record() called for object test2.zone5.example.com [A]
save() called for object <IP_ADDRESS>.in-addr.arpa [PTR]
Calling super().save() for object <IP_ADDRESS>.in-addr.arpa [PTR]
Back from super().save() for object <IP_ADDRESS>.in-addr.arpa [PTR], pk is 107
save() called for object 4.0.10.in-addr.arpa [SOA]
Calling super().save() for object 4.0.10.in-addr.arpa [SOA]
Back from super().save() for object 4.0.10.in-addr.arpa [SOA], pk is 15
Calling super().save() for object test2.zone5.example.com [A]
Back from super().save() for object test2.zone5.example.com [A], pk is 108
Back from update_ptr_record() for object test2.zone5.example.com [A]
Calling super().save() for object test2.zone5.example.com [A]
Back from super().save() for object test2.zone5.example.com [A], pk is 108
save() called for object zone5.example.com [SOA]
Calling super().save() for object zone5.example.com [SOA]
Back from super().save() for object zone5.example.com [SOA], pk is 5

Called via the GUI, the super().save() call for the A record from update_ptr_record() returns the new pk 108, then the second super().save() call from save() returns correctly and the record and the associated PTR record are created as expected.
save() called for object test3.zone5.example.com [A]
Calling update_ptr_record() for object test3.zone5.example.com [A]
update_ptr_record() called for object test3.zone5.example.com [A]
save() called for object <IP_ADDRESS>.in-addr.arpa [PTR]
Calling super().save() for object <IP_ADDRESS>.in-addr.arpa [PTR]
Back from super().save() for object <IP_ADDRESS>.in-addr.arpa [PTR], pk is 109
save() called for object 4.0.10.in-addr.arpa [SOA]
Calling super().save() for object 4.0.10.in-addr.arpa [SOA]
Back from super().save() for object 4.0.10.in-addr.arpa [SOA], pk is 15
Calling super().save() for object test3.zone5.example.com [A]
Back from super().save() for object test3.zone5.example.com [A], pk is 110
Back from update_ptr_record() for object test3.zone5.example.com [A]
Calling super().save() for object test3.zone5.example.com [A]

Called via the API, the super().save() call for the A record from update_ptr_record() returns the new pk 110, then the second super().save() call from save() fails with the 'duplicate pkey' error.
The solution should be pretty simple: Avoid the duplicate `super().save() on new records. On the other hand I would like to know why the API behaves differently from the GUI (and from calling the classes directly, which works as well - not surprising as that's what the GUI does).


Additional bump (tags are frozen and 1.0.1 was buggy)

Pull Request Test Coverage Report for Build 57

1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.662%

Totals

Change from base Build 56:
0.0%

Covered Lines:
295

Relevant Lines:
299

💛  - Coveralls


feat(#765): t2d layerwise training

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #764

PR #766   👈

This stack of pull requests is managed by Graphite.


fix: Generated command comportnent code has error

fix #66

that won't fix it haha

Really?
I thought this was the cause, but is it not?
I'm not using any templates, so I'm assuming that the generated code is exactly as written in this file.

I made a mistake. sorry.


wsl2: javascript is not enabled in your browser

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az login
Describe the bug

I am trying to login to azure and getting the following message:
Microsoft account symbol
we can't sign in
Javascript is required to sign in. Your browser either does not support Javascript or it is being blocked.
Enabled Javascript in your browser or use one which supports it.
To Reproduce

Expected behavior

Environment summary

WSL2
Ubuntu 22.04
azure-cli 2.38
Additional context

@jiasli for awareness


Ledger tokens with memo

Token creation and memo refactoring in a single branch

Codecov Report

Merging #223 (b8df064) into main (f2da501) will increase coverage by 0.79%.
The diff coverage is 79.64%.

@@            Coverage Diff             @@
##             main     #223      +/-   ##
==========================================
+ Coverage   69.60%   70.40%   +0.79%
==========================================
  Files          79       86       +7
  Lines        8918    10000    +1082
==========================================
+ Hits         6207     7040     +833
- Misses       2711     2960     +249

Impacted Files
Coverage Δ

src/many-identity/src/cose.rs
81.63% <ø> (ø)

src/many-modules/src/_6_ledger_commands/send.rs
100.00% <ø> (ø)

src/many-modules/src/_9_account.rs
80.48% <ø> (ø)

src/many-modules/src/_9_account/features.rs
80.00% <ø> (ø)

...c/many-modules/src/_9_account/features/multisig.rs
10.34% <0.00%> (-38.50%)
:arrow_down:

src/many-modules/src/_9_account/features/tokens.rs
0.00% <0.00%> (ø)

src/many-modules/src/lib.rs
83.33% <ø> (+3.03%)
:arrow_up:

src/many-types/src/cbor.rs
92.18% <0.00%> (-6.15%)
:arrow_down:

src/many-types/src/memo/legacy.rs
15.62% <15.62%> (ø)

src/many-modules/src/_4_events.rs
73.09% <68.54%> (-2.13%)
:arrow_down:

... and 18 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I think you can start reviewing this PR @hansl

I added the ability to pass arguments to migrations and tests covering this feature.
This is useful for Token Migration, where a single migration can upgrade multiple networks.


$PWD, at launch from taskbar, should default to $home on Windows

Steps to reproduce

Set the content of $PROFILE.CurrentUserAllHosts (profile.ps1 under $home\Documents\PowerShell) to print $PWD (such as Write-Verbose -Message $pwd -Verbose)
Launch PWSH or PWSH-Preview from taskbar icon
Does NOT repro if starting PWSH or PWSH-Preview using full path

Note: The shortcut Target property is set to "C:\Program Files\PowerShell\6 (or 6-preview)\pwsh.exe" -WorkingDirectory ~

Expected behavior

It should list user's $home as the current working directory

Actual behavior

It produces VERBOSE: C:\WINDOWS\system32 as the output

Environment data
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.1.0 or 6.2.0-preview.1
PSEdition                      Core
GitCommitId                    6.1.0 or 6.2.0-preview.1
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@SteveL-MSFT while you are working on #8079, maybe look at this as well ;)

I don't think it can be fixed in both cases.
If we process profile before applying working directory, per @SteveL-MSFT's PR, we cannot also give the profile script access to the about-to-be-set working directory via $pwd.
If we retain current behaviour, where profile script is processed after, a Set-Location call in the profile script will unilaterally override anything set on the shortcut.

I tested against #8079 and the $profile.CurrentUserAllHosts starts in $HOME


nami extension not loading.

I'm facing a neverending spinner on nami.
Haven't used the extension for a year or so now.
mainPopup.bundle.js:73 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'toString')
    at mainPopup.bundle.js:73:87677
    at u (mainPopup.bundle.js:65:41095)
    at Generator._invoke (mainPopup.bundle.js:65:40883)
    at Generator.next (mainPopup.bundle.js:65:41520)
    at n (mainPopup.bundle.js:73:26169)
    at s (mainPopup.bundle.js:73:26372)

that's the minFeeA from here
             case 5:
                                return r = e.sent,
                                e.abrupt("return", {
                                    linearFee: {
                                        minFeeA: r.min_fee_a.toString(),
                                        minFeeB: r.min_fee_b.toString()
                                    },

@fel-eth12 thanks, no funds lost in this, production keys are backed up, just the testnet tokens locked out.
it is a bug report - I'm not able to use nami anymore.


minimum in bst added

Have you read the Contributing Guidelines on Pull Requests?
(Yes)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(#333 )

please review @ankitaggarwal23 sir

@ankitaggarwal23  sir all changes done


[Bug] Post reply appearing in post section in profile!

Steps to Reproduce
Hi, i found a bug in app new version, apparently the replies is showing in wrong section on profile, i don't know if anyone have reported this but, here it is!
Attachments

What platform(s) does this occur on?
Android
Device Info
No response
What version of the app are you using?
1.94.0
Additional Information
No response

I entered in app for look this bug and magically the reply is back to your correct section.
I will keep this issue open, i don't know if this could happen again!
I mean, this could be only a temporary bug or visual, if this doesn't comes back, i will close the issue.


[SUPPORT] Rollback failed clustering 0.12.2

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
Hello, this is a followup from https://github.com/apache/hudi/issues/10878. We managed to run clustering, but I'm obsessed with a potential recovery plan.
So what behavior I know - when .commit.requested and .commit.inflight created, but not .commit - then subsequent write will do a rollback. - this works for normal commits.
However, if I start clustering - if the job stops before .inflight is created - subsequent write will fail if affects partition present in .replacecommit.requested - controlled by hoodie.clustering.updates.strategy. So here I can only either run clustering from CLI or just delete instant(can you confirm? per code looks like it's safe if there is no .inflight).
But - if it fails after start writing files(after .replacecommit.inflight is created, but before .replacecommit is created) - which choices do I have? As I checked through the code - it looks like there is no automatic rollback for replacecommit, and hudi-cli has rollback only for finished instants.
Given this, can you answer 2 questions:

If clustering failed after .replacecommit.requested, but before .replacecommit.inflight - is it safe to just delete commit file itself? Recently you added this PR and it looks to be  doing exactly this https://github.com/apache/hudi/pull/10645/files
If clustering failed after .replacecommit.inflight, but before .replacecommit - what are the recovery steps? If I understand correctly there is no automatic rollback for it, but i may be wrong(working on reproduction).

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.12.2

Spark version : 3.3.0

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) :

Running on Docker? (yes/no) :

Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.

I see this property hoodie.clustering.rollback.pending.replacecommit.on.conflict - is it generally safe to use if we have single writer with inline services only?

Update - dug into the code clusteringHandleUpdate, and see that if:
Updates rejected - write fails.
Updates accepted - if(hoodie.clustering.rollback.pending.replacecommit.on.conflict is true) - those pending clustering instants that conflict with update records - rolled back.
Updates accepted - if(hoodie.clustering.rollback.pending.replacecommit.on.conflict is false) - pending clustering instants left on commit line, updates made to previous files.
So it looks like switching these 2:
hoodie.clustering.updates.strategy -> org.apache.hudi.client.clustering.update.strategy.SparkRejectUpdateStrategy (non-default)
hoodie.clustering.rollback.pending.replacecommit.on.conflict -> true(non-default)
is generally safe for all operations inline and single writer.
e.g. if the commit fails in the middle of clustering - subsequent commit will be run and it will synchronously rollback clustering instants, and writing updates into old files.
Can someone confirm? @nsivabalan

hey @suryaprasanna : Can you take this up and offer some suggestions.

I managed to do it with
hoodie.clustering.updates.strategy -> org.apache.hudi.client.clustering.update.strategy.SparkAllowUpdateStrategy (non-default)
hoodie.clustering.rollback.pending.replacecommit.on.conflict -> true(non-default)
The precondition is that your write should affect clustered partitions, otherwise nothing will happen.
Unfortunately, I don't see any other way to do it(without copypasting some Hudi internals which looks risky for many users).

Thanks @VitoMakarevich . We were also able to resolve the same error using these two configs only as you suggested.
There is a discussion around fixing this in a  long term as part of this JIRA - https://issues.apache.org/jira/browse/HUDI-1045


Sysprep Count

In the fifth paragraph, it states that sysprep can run 8 times on a single image.  However, the link referenced indicates that the sysprep count limit for Windows 10 is 1001.  That article is dated 2017.  Is that out of date or is the count limit for Sysprep 1001?
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/image-builder-gallery
Thanks
Travis
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 45a82eb4-6023-683b-50ad-eb5d5ffd9f4c
Version Independent ID: 672e6918-aa05-3f03-2497-1d3a6ac1488d
Content: Use Azure Image Builder with an image gallery for Windows VMs (preview) - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/image-builder-gallery.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

I think I found the answer.  The link referenced was updated on March 2nd, replacing the 8 count limit with 1001.
https://web.archive.org/web/20210302111722/https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation

@tsrob50 Thanks for the feedback. I'm going to double-check with the Image Builder folks. I'm a bit concerned because that article is focused on Windows 10 (desktops), and there may be different restrictions for sysprep on server SKUs.


Validate python version and add a current dir to linux terminal.

Purpose

A bug fix, when running the script in a Linux terminal, runs the risk of losing the file path for predocs.sh. For example, let's say I'm here /usr/dev/azuredemo... and I execute the command 'azd up'. The terminal will lose the path './scripts/' created by the venv. So, './scripts/.venv' won't find './scripts/fileOne.py' and vice versa.
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code
ATTENTION: using a linux terminal.

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]

Test the code

To see a full flow of sample with correction in linux terminal.
azd up

To see a script runing solo in linux terminal.
It is necessary to be in the project's root directory.
./scripts/prepdocs.sh

What to Check
Verify that the following are valid
prepdocs.sh
Other Information
To verify the fix, use a WSL terminal in Windows or a Bash terminal emulator.

Thanks for the contribution! We've elected not to make this change as it doesn't seem to be affecting a large number of developers.


jsx not rendering

Hi,
I'm following this example from the Framework documentation:
function Greeting({subject}) {
  return
Hello, {subject}!

}

and then
display(<Greeting subject="JSX" />);

Unfortunately jsx code blocks are not executed, but are returned as code blocks:

Any idea what I could be doing wrong?
The complete markdown file is added here below:
test2.md

This feature is marked as prerelease. Unless you are using the top-of-trunk version by cloning this repo and building Framework yourself, it won’t work. It will be released soon as version 1.9.0. Glad you’re excited to try it out!

Framework 1.9.0 is now released! You can create a new project as:
npm exec @observablehq/framework@latest create


fix: parse int status code to str

Description
Automatically parse integer response status codes to string.

Hi @hougesen .
Thanks for the contribution. This looks great from a first look. I will review it properly by tomorrow morning :smile:


gpr_getenv': env_linux.c:(.text+0x49): undefined reference to dlsym'

In my bazel project I include grpc (tag = "release-0_13_0") and protobuf (tag = "v3.0.0-beta-2") via new_git_repository.  Trying to compile greeter_async_client, I got the error below. Adding linkopts "-ldl" to the grpc rule seems to fix the problem. Is this an issue with my specific configuration or is it a BUILD rule bug?
ERROR: /home/dragos/trunk/examples/rpc/helloworld/BUILD:31:1: Linking of rule '//examples/rpc/helloworld:greeter_async_client' failed: gcc failed: error executing command
(cd /home/dragos/.cache/bazel/_bazel_dragos/d6d537d024f15fe49a1f0b1df0136b24/trunk &&
exec env -
/usr/bin/gcc -o bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client -pthread -B/usr/bin/ -Wl,-z,relro,-z,now -no-canonical-prefixes -pass-exit-codes '-Wl,--build-id=md5' '-Wl,--hash-style=gnu' -Wl,-S -Wl,@bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client-2.params): gcc failed: error executing command
(cd /home/dragos/.cache/bazel/_bazel_dragos/d6d537d024f15fe49a1f0b1df0136b24/trunk &&
exec env -
/usr/bin/gcc -o bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client -pthread -B/usr/bin/ -Wl,-z,relro,-z,now -no-canonical-prefixes -pass-exit-codes '-Wl,--build-id=md5' '-Wl,--hash-style=gnu' -Wl,-S -Wl,@bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client-2.params).
bazel-out/local_linux-fastbuild/bin/external/grpc/libgrpc.a(env_linux.pic.o): In function gpr_getenv': env_linux.c:(.text+0x49): undefined reference to dlsym'

Ah, yes. We need to update the build file.
On Feb 27, 2016 14:53, "Dragos Ionescu"<EMAIL_ADDRESS>wrote:

In my bazel project I include grpc (tag = "release-0_13_0") and protobuf
(tag = "v3.0.0-beta-2") via new_git_repository. Trying to compile
greeter_async_client, I got the error below. Adding linkopts "-ldl" to the
grpc rule seems to fix the problem. Is this an issue with my specific
configuration or is it a BUILD rule bug?
ERROR: /home/dragos/trunk/examples/rpc/helloworld/BUILD:31:1: Linking of
rule '//examples/rpc/helloworld:greeter_async_client' failed: gcc failed:
error executing command
(cd
/home/dragos/.cache/bazel/_bazel_dragos/d6d537d024f15fe49a1f0b1df0136b24/trunk
&&
exec env -
/usr/bin/gcc -o
bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client
-pthread -B/usr/bin/ -Wl,-z,relro,-z,now -no-canonical-prefixes
-pass-exit-codes '-Wl,--build-id=md5' '-Wl,--hash-style=gnu' -Wl,-S
-Wl,@bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client-2.params):
gcc failed: error executing command
(cd
/home/dragos/.cache/bazel/_bazel_dragos/d6d537d024f15fe49a1f0b1df0136b24/trunk
&&
exec env -
/usr/bin/gcc -o
bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client
-pthread -B/usr/bin/ -Wl,-z,relro,-z,now -no-canonical-prefixes
-pass-exit-codes '-Wl,--build-id=md5' '-Wl,--hash-style=gnu' -Wl,-S
-Wl,@bazel-out/local_linux-fastbuild/bin/examples/rpc/helloworld/greeter_async_client-2.params).
bazel-out/local_linux-fastbuild/bin/external/grpc/libgrpc.a(env_linux.pic.o):
In function gpr_getenv':
env_linux.c:(.text+0x49): undefined reference todlsym'
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5472.

Odd... you should need to do -DGPR_BACKWARDS_COMPATIBILITY_MODE to get that code path looking at the code here: https://github.com/grpc/grpc/blob/release-0_13/src/core/support/env_linux.c

I think this is stale. If it is not, it'll be caught and fixed with #1951


latest version boiler template please!

hey can you update this boiler template

Sometime this week. Maybe as soon as tomorrow night

Done!


Content block aside elements not aligning correctly

Detailed description
Describe in detail the issue you're having.
The aside elements for both content block simple, content block media content block mixed and content block segmented are not top-aligning as intended.
Current story:

Is this a feature request (new component, new icon), a bug, or a general issue?
Design defect
Is this issue related to a specific component?
content block simple and content block segmented and content block mixed and content block media
What did you expect to happen? What happened instead? What would you like to see changed?
The heading of the aside elements title should be top-aligned to the intro copy of the content block.
As per design spec:

What browser are you working in?
Chrome

What version of the IBM.com Library are you using?
The latest

Steps to reproduce the issue
https://ibmdotcom-react.mybluemix.net/?path=/story/components-contentblocksegmented--with-aside-elements
Additional information
https://ibmdotcom-react.mybluemix.net/?path=/story/components-contentblockmixed--with-aside-elements
https://ibmdotcom-react.mybluemix.net/?path=/story/components-contentblockmedia--with-aside-elements
https://ibmdotcom-react.mybluemix.net/?path=/story/components-contentblocksimple--with-aside-elements

Screenshots or code
Notes

Waiting a Lara's help, because I have some design questions

@larahanlon2, Could you check again ?? This is the deploy preview: https://ibmdotcom-react.s3.us-south.cloud-object-storage.appdomain.cloud/deploy-previews/3680/index.html

Looks great! I don't see any issues now. Thanks @diegomarcuz

Thanks @larahanlon2


Security groups can be referenced by group-name, don't need a data bag entry

fixes https://github.com/chef/chef-provisioning-aws/issues/49
\cc @jkeiser

Confirmed working for me.  https://github.com/chef/chef-provisioning-aws/issues/174#issuecomment-98858430


Long local variable names to identify interesting explaining variables

Possible CLI:
bin/rwr locals
bin/rwr locals --minlength=25
bin/rwr locals --pattern='(.+(_.+){3,}){32,}' # 3+ underscores in name

Guessing on_lvasgn will help with this. http://www.rubydoc.info/github/whitequark/parser/master/Parser/AST/Processor#process_var_asgn_node-instance_method


Move Ghost 2 over to Node.js 10

Closes #178
I don't think Ghost 1 supports/recommends Node.js 10 (yet?) -- I was kind of wondering if Ghost 1 is still actively supported upstream?  (last release appears to be 1.25.7 on Feb 7, which is still plausible for being actively supported)

@tianon as far as I know Ghost 1.x is still actively supported (I haven't heard anything to the contrary)

Awesome, thanks for confirming ♥


Replace "union type" with "custom type"

Also replace "constructor" with "variant" and replace link to union_types.html with link to custom_types.html

Also a fix for: https://github.com/elm/error-message-catalog/issues/271


Runtime error on WASM

When I try to use gluon on Wasm (in a web frontend using trunk serve), I get this runtime error:

Uncaught TypeError: Failed to resolve module specifier "env". Relative references must start with either "/", "./", or "../".

I'm using the latest version with these features:
gluon = { git = "https://github.com/gluon-lang/gluon", default-features = false, features = ["random"] }
gluon_codegen = { git = "https://github.com/gluon-lang/gluon" }

(When I don't call the function that uses gluon, the frontend works fine without errors.)
Any idea why it's not working? :)

Btw, a related question:
How can I add gluon modules that should be are available for import, such that I specify them as string (.glu file content + module name), not as real filename?
In my use case the modules only exist as Strings in RAM (e.g. when running in the Wasm frontend), not as files on the file system. So I'd like to import them from RAM, is it possible somehow? :)

Calling load_script will register the script under the given file name which you can then import by refering to the module name (my/file.glu -> my.file etc)

No idea why WASM isn't working, never tested it throughly so something may have broken.


Updated Views docs after Analysts meeting today

I will add some more when I do some more code, thanks @mrshll1001


Add Spec::HTTP::Client for testing HTTP::Handler instances

Following @asterite's suggestion on the forum, I finally got around to putting the HotTopic stub for HTTP::Client->HTTP::Handler into a PR for the stdlib. The main difference between my shard and this implementation, other than the namespace, is that I had to add support for ignore_body and decompress. Beyond that, it works the same.
I was pleasantly surprised that the pattern I implemented in my shard was already mostly here. It actually looks almost like I extracted spec code rather than independently arriving at a nearly identical solution. :100:
I chose to port HTTP::StaticFileHandler's spec for as the initial one because I'm hoping to add support for the HTTP Range header in another PR.

New types added to the standard library should be documented. If that's not the intent the whole class should be placed under spec/support instead.

New types added to the standard library should be documented. If that's not the intent the whole class should be placed under spec/support instead.

@HertzDevil I'd prefer to get some more input on logistics like where it belongs. I originally put it in spec/support but then thought maybe it belongs in the stdlib (as @asterite) mentioned in the forum thread. If it's decided it belongs in spec/support, I'm not going to waste time documenting it. If you've got input on that, I'd be glad to hear it.

To be fair, even the internal helpers in spec/support should be documented.

It's okay to wait with documentation. But I think it would be better to mark this as a draft then. Or maybe have a separate issue for discussing this feature addition.
While I support adding a spec helper for testing HTTP handlers, I'm actually not sure this is how it should be done.
It feels odd to use an HTTP::Client instance for testing a server component. Sure, HTTP::Client is the technical counterpart of HTTP::Server. But for testing an HTTP handler, you don't really need a client. The removed code in the static_file_handler_spec.cr  helper shows that: There was no client involved before this change because there is not much reason to. IMO it mostly adds more layers and indirection, instead of doing the bare minimal for testing a handler.
If we want to provide a generic spec helper for testing HTTP handlers, why not just abstract the implementation of the handle helper?
I suppose the only benefit you get with an client instance is that you can use the convenience methods for creating HTTP requests. I'm not convinced that's super helpful for specs, though.
A mock client makes sense for testing code that issues HTTP request through an HTTP::Client instance. That's what https://github.com/manastech/webmock.cr does, for example. I don't like it too much because it's intrusive and changes the implementation of HTTP::Client. You could achieve the same with a dedicated sub class.
However, that's actually not really necessary. A plain HTTP::Client instance can easily be used for mocking requests by passing it a dedicated IO. Here is an example for that: https://github.com/straight-shoota/openid_connect/blob/ea4d9483d485fd69855e7ca13afaaba948467ba5/spec/spec_helper.cr#L14-L43. The handler and request contexts are decoupled and run concurrently which allows even complex testing of long running requests and partial processing.

While I support adding a spec helper for testing HTTP handlers, I'm actually not sure this is how it should be done.
It feels odd to use an HTTP::Client instance for testing a server component. Sure, HTTP::Client is the technical counterpart of HTTP::Server. But for testing an HTTP handler, you don't really need a client.

@straight-shoota The funny thing about this is that I've tried several approaches over the past few years before I realized  that stamping out HTTP requests for the HTTP::Handler to process (well, technically I needed the whole HTTP::Server::Context rather than just the request side of it, but the response was trivial) and sending them to that handler is what an HTTP client does.
I had to make affordances for specifying the method, headers, and URL path/query string for the app to handle, and every iteration just got closer and closer to an HTTP client. Then several months ago it dawned on me that I could override exec_internal to just be honest with myself that that's what I was creating.

The removed code in the static_file_handler_spec.cr helper shows that: There was no client involved before this change because there is not much reason to. IMO it mostly adds more layers and indirection, instead of doing the bare minimal for testing a handler.

This is highly reductive. This PR adds one layer of abstraction and "doing the bare minimum" for testing a handler is nowhere near as simple as you're making it out to be here. Check out the boilerplate in this spec, duplicated in every single spec in that directory:
io = IO::Memory.new
request = HTTP::Request.new("GET", "/")
response = HTTP::Server::Response.new(io)
context = HTTP::Server::Context.new(request, response)

handler = HTTP::CompressHandler.new
handler.next = HTTP::Handler::HandlerProc.new do |ctx|
  ctx.response.print "Hello"
end
handler.call(context)
response.close

io.rewind
io.to_s.should eq("HTTP/1.1 200 OK\r\nContent-Length: 5\r\n\r\nHello")

vs with this abstraction:
handler = HTTP::CompressHandler.new
handler.next = HTTP::Handler::HandlerProc.new do |ctx|
  ctx.response.print "Hello"
end

response = Spec::HTTP::Client.new(handler).get("/")

response.headers["Content-Length"].should eq "5"
response.body.should eq "Hello"

This abstraction made this entire spec easier to read, including the assertion. It even allows for laying out the specs in arrange/act/assert stanzas to more easily follow what's being done.
The specs in the PR didn't get quite as simplified because each spec creates an HTTP::Request itself. I could've gone through and updated each spec to use this abstraction directly but that would've required more effort and I mentioned in this PR's description that StaticFileHandler's spec was just the initial one.
Now let's check the diff:
-io = IO::Memory.new
-request = HTTP::Request.new("GET", "/")
-response = HTTP::Server::Response.new(io)
-context = HTTP::Server::Context.new(request, response)
-
handler = HTTP::CompressHandler.new
handler.next = HTTP::Handler::HandlerProc.new do |ctx|
 ctx.response.print "Hello"
end
-handler.call(context)
-response.close
+response = Spec::HTTP::Client.new(handler).get("/")

-io.rewind
-io.to_s.should eq("HTTP/1.1 200 OK\r\nContent-Length: 5\r\n\r\nHello")
+response.headers["Content-Length"].should eq "5"
+response.body.should eq "Hello"

The abstraction provided in this PR could simplify nearly all specs in that directory by removing virtually all of the same lines.

If we want to provide a generic spec helper for testing HTTP handlers, why not just abstract the implementation of the handle helper?

Are these removed lines being extracted into this class somehow not an abstraction of that helper? If not, what is?

I suppose the only benefit you get with an client instance is that you can use the convenience methods for creating HTTP requests. I'm not convinced that's super helpful for specs, though.

As I mentioned above, I've done this several times across several different apps — JSON APIs, server-rendered HTML, and even Turbo-enabled web apps. I started by doing exactly what's in the stdlib handler specs (including copypasta), then generalized with a method (copy/pasted between spec files), then extracting that into a class I could reuse across apps. And after so many iterations, like carcinization, every single implementation of it became indistinguishable from an HTTP client.
If you don't want to call it an HTTP client, I'm open to suggestions, but since it was built on top of HTTP::Client, doing things an HTTP client does, it seemed like a pretty good place to start.

A mock client makes sense for testing code that issues HTTP request through an HTTP::Client instance. That's what https://github.com/manastech/webmock.cr does, for example. I don't like it too much because it's intrusive and changes the implementation of HTTP::Client.

Agreed on all points here. I choose not to use webmock because I don't agree with its approach.

A plain HTTP::Client instance can easily be used for mocking requests by passing it a dedicated IO. Here is an example for that: https://github.com/straight-shoota/openid_connect/blob/ea4d9483d485fd69855e7ca13afaaba948467ba5/spec/spec_helper.cr#L14-L43. The handler and request contexts are decoupled and run concurrently which allows even complex testing of long running requests and partial processing.

I'm not sure what point you're trying to make with this. The only difference between what you did in that file and what I did in this PR, other than allowing for concurrent requests, is that you use an HTTP::Server::RequestProcessor in between the client and handler. I cut all HTTP::Server machinery out of mine that isn't a dependency of HTTP::Handler, as mentioned in the forum post. There's no need to allocate file descriptors for this.
There is also nothing about this class that precludes concurrent request handling. Coincidentally, though, I have a PR open for concurrent specs, too. #8944

@jgaskins Thanks for this very detailed account. First of all, let me clarify that I support adding a spec helper for testing HTTP handlers. I completely agree to what you said about using an abstraction in the compress handler specs. And Spec::HTTP::Client fulfils that. No argument there.
However, I'm still questioning if this shouldn't work without HTTP::Client.
There's lot's of stuff going on in that class which is unnecessary for handler specs (TLS, connection management) or could even be harmful if used. Overriding #exec_internal means the most part of the class is unused. As a spec helper, the only methods being used - besides the constructors - would be #exec and its variants for the HTTP methods. Everything else is irrelevant for use as a spec helper. That begs the question why even inherit from HTTP::Client when almost everything about it is thrown out. I don't see much sense in that.
We could as well just make the overridden #exec_internal a stand-alone method and pass the handler directly to it. Add a convenience overload that constructs a request. Methods for every HTTP method are expendable.
I'd be interested in hearing more about the limitations that you saw with a more minimalistic approach that doesn't involve HTTP::Client.


Add support for integers in Exec measurement

Using an integer as a value in Exec measurement command throws a type assertion error.
Let's parse values as strings, as expected.
GetStringArray is only used in Exec measurement, so I feel confident with changing behavior of this function.

/assign @mborsz

/lgtm
/approve
/hold
Let's wait for Monday with merge.

/unhold


getScreenCTM() behaviour differently on multiple browsers, leading to mismatch coords when scrolling

In the getScreenBox function, it try to reveal the transformation matrix from the event relavent target element, by "getScreenCTM". But it seems that this api have different behaviour on browsers.
On some version of webkit, especially the mobile tablet. "getScreenCTM" returns the matrix value considers the scrollTop. In this case, if still add scrollTop on the the final tip coords will lead to wrong positions.
On firefox and destop UA of Chrome. "getScreenCTM" will return value ignore the scrollTop, which is fine on current logic.
I checked that, this is a bug in webkit browser. "getScreenCTM" should contain the scrollTop/Left, just the  same like clientX/Y in event object.
I recon that should we ignore the scrollTop value in some special UA? This is not easy, because this bug has been fixed in latest Webkit. We need to find out the specific UA.

The issue what I mean as below:
add scrollTop at https://github.com/Caged/d3-tip/blob/master/index.js#L62
and the getScreenCTM at https://github.com/Caged/d3-tip/blob/master/index.js#L292

Bug of getScreenCTM on Webkit : Webkit bug 44083

Triaging issues.  If this is still an issue could you please provide a working example?


'Longest_Common_Subsequence - Java"

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Added Longest Common Subsequence in Java (Algorithms)
Checklist
I've read the contribution guidelines.
I've checked the issue list before deciding what to submit.
I've edited the README.md and link to my code.

While creating an issue make sure you describe the issue as clearly as possible.


Is this still available?

I can't seem to find continuous export anywhere on the application insights blade?
Thank you,
Tim

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

ID: e85e06b6-1be1-ed40-f219-921415f138e6
Version Independent ID: 3b8f7322-3845-1d2e-2bae-d36aca2776a1
Content: Export using Stream Analytics from Azure Application Insights - Azure Stream Analytics
Content Source: articles/stream-analytics/app-insights-export-stream-analytics.md
Service: stream-analytics
GitHub Login: @AliciaLiMicrosoft
Microsoft Alias: ebnkruma

@timmyreilly  Continuous export has been deprecated by the AppInsights teams.  To export data from your Apps you would need to use diagnostics settings and configure it to write to a blob storage or an eventhub.
here is the documentation: https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/app/continuous-export-diagnostic-setting

@enkrumah Thanks for your quick responses.
@timmyreilly
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@timmyreilly
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Expose internal libs, modules and plugins of core

I believe both webpack and rollup suffer from some of the same issues in that their cores are monolithic and expose a surface area too small for developer access. While there are plugins, the internal code and APIs that drive transformation are not fully exposed properly for programmatic use. This limits their value.
On the current track, I am not certain that webpack nor rollup are the answer to module bundling. Their configuration and relationships to babel remain quite incoherent. Babel plugins also attempt to address some of the same issues. While it is possible to develop with this, that or some combination; bundling and build tooling is all growing in a way that is rather undesirable for use to say the least. Rollup also seems to be emulating much of webpack's config that has already been determined to be a significant sore point with developers.
The ask here is to consider exposing the internal libs in a way similar to lodash (that would not involve bringing the whole of the project to get access to these libs, modules or plugins within the core).
There is very good work being done by both projects and I applaud this. That said, the future of bundling may be neither webpack nor rollup specifically but projects that make use of libs that were thoughtfully crafted and exposed by these projects.
https://github.com/rollup/rollup/issues/449

See @Rich-Harris comment here: https://github.com/rollup/rollup/issues/449#issuecomment-172385469
Same is true for webpack. I do my best to make every package, that's worth it, standalone and independed of webpack.
Here some standalone packages that were created to be used by webpack and co:

enhanced-resolve: The Resolver of webpack.
Nearly every loader is webpack independed. You can use loader-runner to run them without webpack, or in another bundler.
tapable: The plugin system.
beautify-lint: CI linting to beautified code.
watchpack: The watching system.
memory-js: In memory filesystem, use i. e. by the webpack-dev-middleware.
fastparse: Cool RegExp parsing library, used i. e. by some loaders.
Some methods in source-map.
source-list-map: The module of the "cheap-source-maps" in webpack.

@scriptjs have you considered to actually require("webpack/lib/...")? You can access the actual Webpack components fairly easily, and the structure is pretty easy to get around with.

Closing as there is a fair answer already.


Update sandbox for v4

Codecov Report

Merging #648 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #648   +/-   ##
=======================================
  Coverage   93.33%   93.33%
=======================================
  Files           6        6
  Lines          30       30
=======================================
  Hits           28       28
  Misses          2        2

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 0900534...f8b178e. Read the comment docs.


Make something new

Hey! I added a new recipe. Try it out!!!!

I made some changes. Please check the commits section now

I merged your recipe and pulled it. But you're poor spelling is now in my repository. Please delete this.


Platform messages still being handled after FlutterView has been destroyed

https://github.com/flutter/engine/blob/51f12604f7aec7e425be41f56ce8637a948dfa3d/shell/common/engine.cc#L517
-> https://github.com/flutter/engine/blob/51f12604f7aec7e425be41f56ce8637a948dfa3d/shell/platform/android/platform_view_android.cc#L358
-> https://github.com/flutter/engine/blob/51f12604f7aec7e425be41f56ce8637a948dfa3d/shell/platform/android/io/flutter/view/FlutterView.java#L673
That code path can trigger when the flutter view has been detached, which in turn implies that the flutter view has been destroyed by Android.  This was observed in the GoogleSignIn plugin, where the plugin triggers an OEM-widget-based sign-in flow.  The Android OS reserves the right to destroy your view whenever it needs to to free up resources (and will re-create it as necessary), so it's valid for a full-screen sign-in flow to trigger the disposal of your FlutterView (followed by a re-creation when the sign-in completes).

/cc @jason-simmons for thoughts on Android and @mravn-google for thoughts on plugin system.

This is similar to https://github.com/flutter/engine/commit/232f4636e5d46df1f8ba2857c8668558afa697a5
The affected code path involves the Java side sending a reply to a message originated by the Dart side.  Given that the Dart side could be shut down by the time the reply is sent, this should be downgraded from an assert to a warning log.


Housekeeping Druid log files

Is there a preferred approach in housekeeping Druid service log files in a production implementation.
Over the period of time, the logs become too large in size causing space issues in server. Simply deleting the logfiles does not seem to resolve the problem, as the process ids of delete command is still running in background

Yes after a long time running, the size of log files could be a problem. There're two ways to clean the logs

use logrotate to rotate the log file and then create a crontab task to delete old enough log files

config log4j2 to output log to files so that log files can be deleted based on your configurations.
to do that, if nodes are started by broker.sh or historical.sh etc, modify the node.sh script shell to redirect stdout of java to /dev/null, and then change log appender of log4j2 from console to RollingFileAppender

In my opinion, druid should use RollingFileAppender in its default configuration.

Here is a detailed solution that I implemented in our production Druid (0.15.1) and logs never have been an issue at all. Always rotated properly
https://webcache.googleusercontent.com/search?q=cache:rIfskAblx68J:https://support.imply.io/hc/en-us/articles/360006216874-How-to-config

@giom-l you have done what the PR above intends to do. Thanks for your sharing.


Growable buffer

Hi,
When encoding msgs with repeating groups and variable length data I am uncertain how large to make the buffer which sbe encodes into; making too small could cause exception for large msg. Have you considered support for a growable encoding buffer?
Thanks.

Would you be happy for the resizing operation to be controlled by you?

Yes we have considered it. That is why interfaces are supported with the work in migrating to RC3. This allows you to provide your own implementation that could grow if you wished. This will have a performance impact and why it is not supported in the base implementation.

Yeah I'd be happy to write the resizing code -- didn't realize a newer version used interfaces that sounds great thanks.

RC3 is currently in development and will be released within a few weeks.

Looks like growable buffers were added in SBE 1.4.0-RC4 courtesy Agrona 0.5. Nice!

Very nice. Thanks for heads up
On Apr 29, 2016 10:05 AM, "Brian Harris"<EMAIL_ADDRESS>wrote:

Looks like growable buffers were added in SBE 1.4.0-RC4 courtesy Agrona
0.5. Nice!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/real-logic/simple-binary-encoding/issues/312#issuecomment-215726627


Add Python 3.11 support

Since Python 3.11 has been out for a while, add tests and update setup.cfg.

Thanks, @dstansby. @will-moore: thoughts on a release here?


Creating Lists on HTML gone wrong

We have writteI want to create a unodered list on my index page. Whenever I type
 and intend to create an , my
 will change automatically to . This is frustrating and delaying my work cos whenever i intend to manually correct it, auto correct will start deleting every elements I intend to corect.

n the needed data into your clipboard because it was too large to send. Please paste.

Sorry, I'm not able to repoduce.

type
: this will complete to

type `<a href

Do you have any extensions enabled?

Whenever I type  <a href, my  changes to . I don't have any new extensions enabled. Its been working perfectly fine until now.

Sorry, not for me:


stats for serialtiles

Uses the tilelive-bridge stats file name + format to dump stats about tile size to disk.
cc @suhasdeshpande

Do we want to bump the patch version?

Let's release as a minor since this is technically a new feature @suhasdeshpande. That'd be 7.4.0 ✔


Add remark to the address book

Submission: Do your changes in a branch named tutorial-adding-command, push to your fork, and create a PR from your fork to your team's repo. You may close the PR soon after.    --tutorial task 2


Convert Client.send to match the api().action() interface

Currently it returns the packet it sent if it is connected, otherwise returns a promise that is resolved after the connection is made and the packet is sent.  Make it consistent with the api().action() interface:

Promise is resolved/rejected based on the response.
Call back is invoked for non-response parts of the conversation.
Call back receives a "done" function to unregister itself.

so
client.send({
    'dst': "$transport"
},function(reply){
   console.log(reply);
});

will now be:
client.send({
    'dst': "$transport"
}).then(function(reply){
    console.log(reply);
});

?


Fixes the bug "More bytes are generated for Key Material than needed for AEAD cipher"

This pull request fixes the issue "More bytes are generated for key_block than needed for AEAD ciphers" (Fixes #12007). In doing the fix, I have reused existing code that was already calculating IV length within the key block. See the discussion at #12007 for more details. It was the idea of @jwalch to use the existing code. I have taken existing code using the so-called "extract function" refactoring pattern. After that, @richsalz has proposed to optimize the code that by removing "k", and just replacing the assignments with return statements, then removing the "else".
This pull request is basically about the two things:
(1) Enables tracing of the key block length to show the bug by adding 'BIO_printf(trc_out, "key block length: %ld\n", num);'
(2) Fixes the bug by creating a function 'tls_iv_length_within_key_block' from existing code and calling it from that old place and from a second (new) place where IV length was taking regardless its context within the key_block.
I have also changed the order of addendums to correspond to one given in the RFC. The old order was somewhat counter-intuitive.
Old:
num = EVP_CIPHER_key_length(c) + mac_secret_size + EVP_CIPHER_iv_length(c);

New:
num = mac_secret_size + EVP_CIPHER_key_length(c) + tls_iv_length_within_key_block(c);

Here is the order in the RFC:
client_write_MAC_key[SecurityParameters.mac_key_length]
server_write_MAC_key[SecurityParameters.mac_key_length]
client_write_key[SecurityParameters.enc_key_length]
server_write_key[SecurityParameters.enc_key_length]
client_write_IV[SecurityParameters.fixed_iv_length]
server_write_IV[SecurityParameters.fixed_iv_length]

So, MAC_key comes first, then come cipher key and then the IV. That's why I put "mac_secret_size" first.
@mattcaswell - please review.

Could you please amend the commit message to be more descriptive and put the Fixes line in the commit message body not on the first line? Use git commit --amend  and then git push --force to do that.

@t8m, I've changed the commit description. Is it OK now?

Unfortunately the formatting is less than perfect. There are missing line separators. For example the Fixes #12007 should be alone on a separate line and without the parentheses. Also the first line should be as concise as possible - something like: TLS AEAD ciphers: do not generate more bytes for key_block than needed

Also the message body does not need to include the history of the changes and it usually is not written in first person, but it also does not hurt so that is up to you.

@t8m I have updated the title and the first line of this pull request and made "Fixes #12007" as a separate line at the end of text. Is it OK?

@t8m or you meant that I needed to additionally update the git commit message with "--amend" to make the commit message multi-line? It is now a single long line.

@t8m I have updated both the pull request description at the github and also the git commit description. It is now multiline. Can you please confirm that it is now OK?

Merged to master. Thank you for the PR.


Add arm darwin support

Currently I need to use ethdo on apple silicon.
Tested with:
nix build ".#ethdo"
nix run ".#ethdo"

@SpontaneousOverthrow adding an extra system like that is going to give the mistaken impression that all the other packages and apps have been tested to work on Darwin. If you run nix flake check from an aarch64-darwin system you'll see that Nethermind for example isn't supported.
You can modify the perSystem entry in packages/default such that for x86_64-linux it includes everything and for aarch64-darwin it only includes ethdo for now until we have time to review what is supported and add them in.

Is this correct that the best way is to use withSystem module, where I need to provide packages for each arch?
https://flake.parts/module-arguments.html#withsystem

Is this correct that the best way is to use withSystem module, where I need to provide packages for each arch? flake.parts/module-arguments.html#withsystem

I've been looking into this a bit more today and It's more complex than I first thought. I'm gonna keep playing around with this branch https://github.com/nix-community/ethereum.nix/tree/feat/multi-system but there are some issues I need to resolve.

Maybe try to use meta attributes and meta.platforms and filter by it?

Like that: just use this function:
  platformPkgs = system: packages:
    filterAttrs (name: value: elem system (value.meta.platforms or [])) packages;

and then use that in current attrset:
    packages = platformPkgs system rec {
       ...
    }

Maybe try to use meta attributes and meta.platforms and filter by it?

I had this same thought, will have a look a bit later in the week.

Closing in favour of #114, we can continue the discussion and refinements there

@SpontaneousOverthrow #114 has been merged. I've tested ethdo a bit on my own M1 mac but I haven't used it in anger. Lemme know if there's any issues.


rspec hangs in the middle of testing

Whether I type "rspec" or "rake spec" in the terminal, it just hangs and never finishes the testing suite. I've commented out tests, ran test files individually, but it still just stops. Closest I got to having it finish was uninstalling and reinstalling rspec-rails. First time I run it, I get it to finish.
Second time, I get this:
$ rake spec
/Users/edmac/.rvm/rubies/ruby-2.1.3/bin/ruby -I/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/lib:/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-support-3.2.2/lib /Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
I, [2015-04-14T11:28:18.114799 #4618]  INFO -- : Not reporting to Code Climate because ENV['CODECLIMATE_REPO_TOKEN'] is not set.
.........*.........*....*.......*..*..*..*.*......^C
RSpec is shutting down and will print the summary report... Interrupt again to force quit.
rake aborted!
Interrupt:
/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/lib/rspec/core/rake_task.rb:69:in `system'
/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/lib/rspec/core/rake_task.rb:69:in `run_task'
/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/lib/rspec/core/rake_task.rb:89:in `block (2 levels) in define'
/Users/edmac/.rvm/gems/ruby-2.1.3/gems/rspec-core-3.2.3/lib/rspec/core/rake_task.rb:87:in `block in define'
/Users/edmac/.rvm/gems/ruby-2.1.3/bin/ruby_executable_hooks:15:in `eval'
/Users/edmac/.rvm/gems/ruby-2.1.3/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => spec
(See full trace by running task with --trace)

I had to shut it down because it was hanging for ten minutes. The next time I run the suite, I get:

$ rspec
I, [2015-04-14T11:35:50.690190 #4777]  INFO -- : Not reporting to Code Climate because ENV['CODECLIMATE_REPO_TOKEN'] is not set.

So try a couple of things, first off run try to run your specs with rspec /spec rather than rake spec that way if you have to CTRL-C you'll get a trace of where your specs are stuck rather than just aborting the rake task.
Secondly do spring stop before running the specs to remove that as a possibility.

@JonRowe's suggestion is a good one, but here's a slightly more robust way to get the stack trace, so we can see what it's stuck at.  Add this code to any file that is loaded as part of your suite (such as spec/spec_helper.rb):
puts "rspec pid: #{Process.pid}"

trap 'USR1' do
  threads = Thread.list

  puts
  puts "=" * 80
  puts "Received USR1 signal; printing all #{threads.count} thread backtraces."

  threads.each do |thr|
    description = thr == Thread.main ?  (Note that it'll print to RSpec's stdout, not to the terminal where you ran kill from).
The nice thing about this compared to ctrl-c is that you get the stacktraces for all threads and it doesn't halt the process -- so you can run it repeatedly to see if it's staying stuck at one spot, or if it's making progress but just going really slow or whatever.

Thanks so much guys, and sorry for the delay in getting back. Not an rspec problem it turned out.  I just had to type out
ps -ax | grep
in the terminal and yes,
killall
or
kill
It took a while to figure out and go through all the different server processes (and the ones on my team mates laptops) but all good now. Cheers!

Hmm thats a bit odd, are the zombie processes belonging to RSpec or rails?

I can't really tell as this was the only the second project where I used RSpec (is there a way I could dig deeper to find out) because when I ran "rails s", the browser was working just fine. The code worked. It just broke when I ran rspec.

thanks, @myronmarston !

@myronmarston -- your suggestion above was a life-saver, thank you!

I have one hanging test. Using the recommendation from @myronmarston I got following output:
Received USR1 signal; printing all 1 thread backtraces.
Main thread backtrace:
/home/mwcruz/cicio-hangmangame/spec/spec_helper.rb:56:in backtrace' /home/mwcruz/cicio-hangmangame/spec/spec_helper.rb:56:in block (2 levels) in <top (required)>'
/home/mwcruz/cicio-hangmangame/spec/spec_helper.rb:52:in each' /home/mwcruz/cicio-hangmangame/spec/spec_helper.rb:52:in block in <top (required)>'
/home/mwcruz/cicio-hangmangame/lib/hangperson_game.rb:37:in block in word_with_guesses' /home/mwcruz/cicio-hangmangame/lib/hangperson_game.rb:36:in each_char'
/home/mwcruz/cicio-hangmangame/lib/hangperson_game.rb:36:in word_with_guesses' /home/mwcruz/cicio-hangmangame/lib/hangperson_game.rb:44:in check_win_or_lose'
/home/mwcruz/cicio-hangmangame/spec/hangperson_game_spec.rb:113:in block (3 levels) in <top (required)>' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:206:in instance_exec'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:206:in block in run' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:430:in block in with_around_and_singleton_context_hooks'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:388:in block in with_around_example_hooks' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/hooks.rb:478:in block in run'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/hooks.rb:616:in run_around_example_hooks_for' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/hooks.rb:478:in run'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:388:in with_around_example_hooks' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:430:in with_around_and_singleton_context_hooks'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example.rb:203:in run' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:559:in block in run_examples'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:555:in map' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:555:in run_examples'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:521:in run' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:522:in block in run'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:522:in map' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/example_group.rb:522:in run'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:115:in block (3 levels) in run_specs' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:115:in map'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:115:in block (2 levels) in run_specs' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/configuration.rb:1627:in with_suite_hooks'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:114:in block in run_specs' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/reporter.rb:77:in report'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:113:in run_specs' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:89:in run'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:73:in run' /home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/lib/rspec/core/runner.rb:41:in invoke'
/home/mwcruz/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.3.2/exe/rspec:4:in <top (required)>' /home/mwcruz/.rvm/gems/ruby-2.3.0/bin/rspec:23:in load'
/home/mwcruz/.rvm/gems/ruby-2.3.0/bin/rspec:23:in <main>' /home/mwcruz/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in eval'
/home/mwcruz/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `'
How may I identify the source of my problem?

@cicio look at the backtrace.  The first 4 lines are from spec_helper.rb and are probably from the trap block you pasted into your spec_helper.rb.
After that comes lib/hangperson_game.rb:37 which is probably the source of your problem.  You can also try sending the signal, waiting a bit (30 seconds or so), sending the signal again, etc.  By sending it multiple times like this you can see if its always stuck at the exact same line or whether it is at different lines.  If it's at different lines, it suggests your code is running some slow algorithm, but is in fact making progress.  If it's the same line, maybe there's some sort of blocking I/O there that just gets stuck.

Thanks @myronmarston for the help: I got alternating results by sending consecutive signals (kill -USR1 : Based on your recommended troubleshooting steps I was able to identified the line of code that caused it. The problem was a condition written with the operator ? : , instead of if else. It is solved. Once the error was removed all test resumed and passed. Thank you

Wanted to also point out that if you binding.pry a test in another window, then try to run RSpec, your test will wait for the other test to finish and therefore never run (unless you were to exit that debugging session).
Restarting your computer could solve this problem if you're just really unsure where the process is but otherwise ps aux | grep ruby could probably show you then you could kill -9 the PID.

I just wanted to add something here for future internet explorers that find this post.
My test suite started hanging and I could not figure it out. No stack trace, no nothing. Restarted my computer and everything, thinking the testing server needed to reboot.
Turns out, I went to test the app manually and BOOM, I had a simple syntax error, unexpected end-of-input, expecting end in a separate controller. However, it was still causing the test suite to hang and there was no stack trace to tell me about the syntax error.
Simple mistake on my part, and nothing to do with Rspec, but just something for others to look into.

@pmichaeljones It's an interesting case. I believe the error message should bubble up. Do you care to open a ticket provided a reproduction example repo?

@pirj I can try to do something within the next week. Quite busy with work at the moment.

Page wallet

Page wallet

Page wallet

Thanks

Wowza, so also adding my experience to future explorers as well. And special h/t to @myronmarston for the trap backtrace code that uncovered the lead.
For us, our test suite was hanging at the very end. After implementing Myron's code, we got the stack trace (abbreviated):
/home/semaphore/app/spec/spec_helper.rb:243:in `backtrace'14:40
/home/semaphore/app/spec/spec_helper.rb:243:in `block (3 levels) in <top (required)>'14:40
/home/semaphore/app/spec/spec_helper.rb:239:in `each'14:40
/home/semaphore/app/spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'14:40
/home/semaphore/app/vendor/bundle/ruby/2.7.0/gems/railties-<IP_ADDRESS>/lib/rails/application/finisher.rb:138:in `lock'14:40
/home/semaphore/app/vendor/bundle/ruby/2.7.0/gems/railties-<IP_ADDRESS>/lib/rails/application/finisher.rb:138:in `run'14:40
/home/semaphore/app/vendor/bundle/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:28:in `before'

So, I explored the Railtie application finisher.rb code and saw it was doing something with mutex locking, probably the GIL.  But what? So, after chasing this down wrongly, I ended up searching the right keywords: "rspec rails application finisher mutex hanging", which then took me to right question/answer on StackOverflow: https://stackoverflow.com/questions/21313628/rspec-hangs-after-it-finishes-running-through-my-tests
In the end, it was SimpleCov that was the culprit. As reported:

When simplecov exists, by default it will try to merge the recorded coverage with what's on disk. To avoid corruption it uses a lock file to guard this merge. Because my virtual box shared fs is not actually posix compliant, the lock file would never acquire, and silently block forever here.

NOTE: this has apparently been fixed in newer versions of SimpleCov (we were running an old version).

+1 to documenting this. I'm upgrading a Rails app and Rspec tests were hanging. Thanks to @myronmarston I was able to connect this issue to this post https://thoughtbot.com/blog/multi-thread-backtrace-for-silently-hanging-tests
Restarting postgres service did the trick for me. My specs were getting stuck specifically in "connection_pool.rb sleep".


Collect back comments

This should eventually be changed to an alloc-less version but this already doesn't allocate on a commentless key
I tried with:
let (keytype, remaining) = key
   .split_once(char::is_whitepace)
   .ok_or(OpenSSHKeyError::InvalidFormat)?;
let (data, comment) = remaining
   .split_once(char::is_whitespace)
   .ok_or(OpenSSHKeyError::InvalidFormat)?;
let comment = if comment.is_empty() {
   None
} else {
   Some(comment.to_owned())
};

But some unit tests didn't pass, so I'm leaving it here.
Should fix #107
This shouldn't be a breaking change.

This seems sane to me. I can confirm indeed that openssh supports comment fields with spaces or tabs.
The code as written doesn't preserve arbitrary space amounts, or tabs. The alternate version looks more correct. What unit tests failed with it?

Here are the 2 tests which fail, hostname_parse and read_keys:
failures:

---- tests::hostname_parse stdout ----
thread 'tests::hostname_parse' panicked at src/lib.rs:939:264:
called `Result::unwrap()` on an `Err` value: InvalidBase64 { detail: "Invalid byte 45, offset 5." }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- tests::read_keys stdout ----
thread 'tests::read_keys' panicked at src/lib.rs:980:69:
called `Result::unwrap()` on an `Err` value: InvalidFormat

failures:
    tests::hostname_parse
    tests::read_keys

I agree that the split_once version seems more correct, since it actually preserves the kind of whitespace in the comment. But since tests failed I assumed something was wrong with it.
If you want to test it locally, I committed it to my repo in the branch split_once.

I found the issue. When data didn't have a trailing space, split_once returned None instead of something like Some(data, <emptystring>).

I applied your suggestion, tests seem to be ok :)

Tis done!

Hi, is there an ETA on this? :)


Using double click event for submission

I want to let users submit a cropped image by double clicking the image (the crop modal). I've tried everything but I can't get jquery to read the double click event. I'm assuming its being overridden by the built-in double click event for toggleDragModeOnDblclick.
I have toggleDragModeOnDblclick:false,
I am trying:
$( ".cropper-modal" ).dblclick(function() {   alert( "Handler for .dblclick() called." ); });
But I have tried #image and various other divs but can't get anything to fire.

Maybe you bind the event before the .cropper-modal is generated.
Try this:
$('#myImage').on({
  ready: function () {
    $(".cropper-modal").dblclick(function () {
      alert("Handler for .dblclick() called.");
    });
  },
}).cropper(options);

So that makes everything but the selection double-clickable. If you double click the background it runs the event, but the selection still overrides it. Thank you for the help though!

Maybe you can set both the cropBoxResizable and cropBoxMovable options to false.


How to Import Build?

In VSCode I can do do cmd+shift+p and search for "metals: import build". How can I trigger this in Zed?

You need to install the LSP as described on the zed website
Next, you need to open the scala file and you will start setting up the project


Software Tool: The 'cat' Command Guide

I will develop a comprehensive guide on using the cat command in Unix/Linux environments, titled "The cat Command Guide." This document covers basic usage such as syntax, and more advanced features like displaying non-printing characters and concatenating files.
I believe this guide could be a valuable addition to the Software Tool Shell section in the class wiki, especially for those new to shell scripting or looking to deepen their understanding of command-line tools.

For sure this command is essential in program development, cannot wait to learn what can I do more with cat command


Managed app ARM templates failing while validation with latest version of ARM-TTK

Hi Team, Hope you are doing good.
Since the upgrade of ARM-TTK our template validation is failing. If I remember it correctly with v0.15 I never encountered this issue.
Also, I believe the reason is wrong or misleading since we already are using the practices which are shared over the documentation.
Ref: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-test-cases
Section: VM size uses parameter
Error:
  VM Size Should Be A Parameter
    [-] VM Size Should Be A Parameter (140 ms)
        VMSize parameter must be declared for the parent template

We are already using vmSize as a parameter, please find below snippets from our respective arm templates:
createUiDefinition.json [Ref: https://learn.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/microsoft-compute-sizeselector]
			{
				"name": "nodeSize",
				"type": "Microsoft.Compute.SizeSelector",
				"label": "Size",
				"toolTip": "The size of VMs to be used as worker nodes in the AKS cluster",
				"recommendedSizes": [
					"Standard_B4ms",
					"Standard_DS3_v2",
					"Standard_D4s_v3"
				],
				"options": {
					"hideDiskTypeFilter": false
				},
				"osPlatform": "Linux",
				"imageReference": {
					"publisher": "Canonical",
					"offer": "UbuntuServer",
					"sku": "18.04"
				},
				"count": 1,
				"visible": true
			},

mainTemplate's parameters:
    "nodeSize": {
      "type": "string",
      "defaultValue": "Standard_B4ms",
      "metadata": {
        "description": "Node Size"
      }
    },

mainTemplate's resources (this is a part of AKS agent pool):
        "agentPoolProfiles": [
          {
            "name": "agentpool",
            "count": "[parameters('nodeCount')]",
            "vmSize": "[parameters('nodeSize')]",
            "enableAutoScaling": true,
            "minCount": "[parameters('nodeCount')]",
            "maxCount": "[parameters('nodeMaxCount')]",
            "osType": "Linux",
            "storageProfile": "ManagedDisks",
            "type": "VirtualMachineScaleSets",
            "mode": "System",
            "vnetSubnetID": "[variables('aksSubnetId')]",
            "maxPods": 50
          }
        ],

Could you please suggest OR correct me if I am doing something wrong?
Thank you,
Sunny

If a full copy of ARM is required, the sample can be found on below URL, since that too is failing and there as well we have vmSize as a parameter:
https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-rm-template?tabs=azure-cli
Section: Review the template
OR here: https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.kubernetes/aks/azuredeploy.json
Thanks,
Sunny

Maybe another repro: https://github.com/Azure/azure-quickstart-templates/tree/master/application-workloads/darktrace-vsensor-standalone

It appears we are not allowing the VMSize parameter to be anything other than VMSize:
https://github.com/Azure/arm-ttk/blob/master/arm-ttk/testcases/deploymentTemplate/VM-Size-Should-Be-A-Parameter.test.ps1#L36
I believe we should adjust this.  But how? Should we require it to be named anything particular?  If not, what heuristic do we use to determine if the top-level parameter is a VMSize?

It should have no naming constraints - the parameter can be named anything.  We just need to verify that any resource property named vmSize has a property value that is a parameter (or a variable that references a parameter)...  Keeping in mind that the param/var could be an object.

@sunnybhambhani
This should be fixed by recent changes to the VMSize tests. Please confirm when you get the chance.


crypto/x509: add missing be to comment about serial number positivity

Was intended to be a PR to upstream, and misfired in UX.


New component: Forms / Character count

https://designsystem.digital.gov/components/form-controls/#character-count
We'll need to recreate their JS implementation of this, and will likely mean touching the existing TextInput & Textarea components.

Requirements
Input types:

Supports both <input type="text" /> and <textarea>

Character limit:

Determined by the maxlength attribute on the input element.
Does not limit the actual input field length, allowing the user to exceed the soft cap.

Placeholder text states:
No input: {maxlength} characters allowed
Input less than max plural/no characters left: {input length} characters left
Input less than max singular: 1 character left
Input over the max singular: 1 character over the limit
Input over the max plural: {input length - max} characters over limit
Event Listeners:
onChange: updates the hint element outside of the form group with the new placeholder template.  Adds invalid class when exceeding the max.
onBlur: if over the limit input field border gets red highlight
Accessibility:

Need to match the aria-describedby with the label and character count message ids.
Screen readers will announce when using the arai-live="polite" attribute on the character count message

React Implementation
TBD


Fix bump version to federal senate script

As it added stuff to the public API I think it's a minor (not micro) version bump — i.e. 9.1.0, nor 9.0.4 ; )

Aw thanks, forgot about that!


Footer aligned in web UI

Footer has been aligned in web UI successfully

#24

Thank you so much.
Just a friendly reminder that do star the repository and watch it so that I can move ahead and merge the pull request.

is there any  issue in this pr mam? @sanika391


[Do not merge] Test upgrade to Gateway API 0.8.0-rc2

Proposed changes
Problem:
Uncertainty if an upgrade Gateway API v0.8.0-rc2 breaks anything
Solution:

Update the Gateway API dependency to 0.8.0-rc2
Update conformance related files

Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Closing in favor of https://github.com/nginxinc/nginx-kubernetes-gateway/pull/1008


Passing "--go_opt=M:<go_pkg>" does not mute "WARNING: Missing 'go_package' option..."

edit for clarity
I'm confused about the intended remediation for:
WARNING: Missing 'go_package' option in "example.proto"
please specify it with the full Go package path as
a future release of protoc-gen-go will require this be specified.

I've been generating protobufs by specifying the go package on the command line when compiling the protobufs using the M option (like --go_out=M<src.proto>:<go_package>,out. This is advantageous for many reasons some of which are highlighted below. However, when upgrading my tooling recently and moving over to the new packages, I've started seeing the warning above. Looking around, I no longer see the M option referenced in the README. And a little bit of digging around the issue tracker uncovers comments like below.
original prose
From https://github.com/golang/protobuf/issues/791:

We're moving towards a world where we double down on the presence of go_package. Any logic that tries to derive the Go package path from the information in protobuf alone leads to insanity in some way or another. The go_package option is the only way to have a sane understanding of how proto files relate to one another in the Go language.

While it may be generally true that some prefix is required, why must go_package be specified in the protobuf source file, and not manually (or automatically by reading the go.mod) when the ultimate source is generated?
I can understand how it might get a little hairy for public packages if someone were to include a package that also included its own generation of types off the same set of proto files (so you'd end up with duplicate types derived from identical proto sources), but this is hardly the common and only use case for protobufs, no?
For example: we find it very handy to be able to generate protobufs in a package of our choosing on the server so we can decorate the types such that they support interfaces required to double as database models whilst generating them more simply on the client in their own way. With a fixed go_package, the client would need to import the server (and all of its transitive dependencies and whatnot) to be able to use the generated code.
Forcing a go_package option to live in the proto source file generally prevents compile-time code generation and thus prevents builds from being structured in a way that treats generated source files as build artifacts. Java's gradle protobuf plugin does exactly this, and everything seems to work just fine for that implementation. Why must go projects depend on checked-in code-gen?
It also strikes me as a little backwards that a source proto file should ever even lay rightful claim to being required let alone able able to assert anything about the ultimate generated source packaging structure. The only invariant that need be maintained, as #791 points out, is that the golang proto compiler plugin knows how to generate source such that the go compiler can make sense of import paths. Why does it matter if two packages want to generate the source files in slightly different packages or using different build strategies if, at the end of the day, the types and service definitions remain compatible?
I totally understand the need to require a go_package option to be specified, even manually, at some point. I don't understand why it has to live in the source proto file.
summary
Maybe I'm just swept up in the whole transition and have a few signals crossed? But it would be really nice to know what the intended end state looks like for projects using the protobuf-go tooling.

I recommend giving @neild's comment here a read: https://github.com/golang/protobuf/issues/1151#issuecomment-646176703, it's  not directly related to your question, but sheds light on the technical complexities involved.
Fundamentally, protoc-gen-go lacks information to derive the Go package path correctly. It works for simple programs, but breaks down as the program scales in complexity. It is better to avoid these troubles by having users provide the information that protoc-gen-go needs to make the right choices from the beginning.

automatically by reading the go.mod

This is an interesting idea, but a challenge is that protoc-gen-go doesn't have access to that information. The only information it has is what the protoc binary passes it, and information about go.mod files is not available because protoc doesn't understand anything about Go modules.

BTW, the title changed since I started writing my response.
The current title of "Allow go_package to be specified as a --go_opt" is actually already available through the "M" flags. For example:
protoc --go_out=Mpath/to/source.proto=path/to/go/protopackage,$ARGS $SOURCES

Yep! I currently use the M option to specify my go package. I guess I was assuming that the M option was going away since I can no longer find documentation on the option in this repo and since the go plugin prints out the
$ protoc --proto_path=src --go_opt=Msrc/foo/foo.proto=example.com/rpc/gen/foo --go_out=gen src/foo/foo.proto
> WARNING: Missing 'go_package' option in "foo/foo.proto", please specify it with the full Go package path as a future release of protoc-gen-go will require this be specified."

message regardless of whether there's an M option or not. If this option will remain in the future, perhaps the warning is simply more aggressive than need be?

The "M" options are here to stay (they are not going away).
If properly used, they will suppress the warning you are seeing. The problem at hand is a mismatch between what's specified in your M flag, and what's being processed. Notice, that the M flag is specified with "src/foo/foo.proto", while the warning is complaining about "foo/foo.proto"? In other words, protoc-gen-go still hasn't been informed about what Go package path to treat "foo/foo.proto" as.

Okay I've tied to edit the original post for clarity BTW. Anyway, it looks like the proto source path passed to M needs to be relative to the proto_path. Removing src/ from the command above indeed mutes the warning!
So that leave me with two thoughts:

Where can I find documentation on the M option? The documentation I had been using previously seems to be missing... leading me to try and infer intentions.
Perhaps a more precise error message is in order indicating that the source file value passed to M can't be found under the proto_path? I probably would have been able to diagnose the problem and could have avoided opening this issue (and a bunch of extra work moving protobufs around to try and accommodate a hard-coded go_package) had the actual problem been clear.

I also think that for M to actually be useful, you need to be able to combine it with paths=source_relative so that you can say something like:
protoc --proto_path=src --go_opt=M=example.com/rpc,paths=source_relative --go_out=gen src/foo/foo.proto

What this means is, "My go_package module (M) is rooted at example.com/rpc, treat all protos as source_relative to such".

I took a stab at making it happen: https://go-review.googlesource.com/c/protobuf/+/240238. Regardless of whether you ultimately want to allow this or not, hopefully it spurs further discussion (:

Where can I find documentation on the M option? The documentation I had been using previously seems to be missing... leading me to try and infer intentions.

I seriously thought we had these documented somewhere, but I can't seem to find them. I filed #1161 to address this.

I also think that for M to useful in the common case it needs to not be a file-specific option but rather simply an import prefix option applying to all imported protos. ... I took a stab at making it happen: https://go-review.googlesource.com/c/protobuf/+/240238. Regardless of whether you ultimately want to allow this or not, hopefully it spurs further discussion (:

There seems to be quite a bit of overlap with your proposed changes at that of https://github.com/golang/protobuf/issues/992. Are you okay with closing this issue and continuing discussion over there?

Closing this as we can continue any discussion on #992. There's improvement for users who do not use the go_package option and we'd like a single cohesive story around how that is presented. https://go-review.googlesource.com/c/protobuf/+/240238 presents a different approach, but it overlaps in functionality.

@dsnet yes that's fine. Thanks for pointing me to https://github.com/golang/protobuf/issues/992


After alarm set if app kills from background getting error and unable to open the app

While developing i set the alarm and its working as expected, facing issue in case while app killed from background after setting alarm. Error is - COULD NOT CONVERT CLASS android.os.UserHandle

after this error app not open until you reinstall it from android studio.
Below are steps i used for setup -

npm i react-native-alarm-manager
Added receiver and service in manifest
adding broadcast receiver in MainActivity.java

any thing i missed in installation ?
Please suggest. Thanks

Hello, @ravi2288
I'm sorry to hear that you have a problem.
No, you did not miss the installation.
I see this error for the first time, so I don't know what is matter.
However, I searched this error and found this issue related with your problem.
It doesn't seem to work properly on Xiaomi models. But not sure.
https://github.com/wix/react-native-notifications/issues/287#issuecomment-595643518
Or, check your android sdk version. -> Check android SDK
I hope your problem is resolved quickly. Thanks.


Start Sceen

Ask the player for name: Use the notebook
Give a short introduction using the notebook
On the left hand side add some kind of button?


opset11 problem

hi, i'd  like to ask onnx_to_tensorrt how can support  opset11(onnx),i use torch.onnx(....,opset 10 )can't support upsample_bilinear2d,only use opset 11 can export onnx model, but i use onnx_to_tensorrt.py parsing onnx(opset 11) get an error :ERROR: Failed to parse the ONNX file.
In node -1 (importResize): UNSUPPORTED_NODE: Assertion failed: (transformationMode == "asymmetric" || transformationMode == "align_corners" || transformationMode == "half_pixel") && "This version of TensorRT only supports asymmetric, align_corners and half_pixel resize!"
ERROR: failed to build the TensorRT engine!
looking forward to your reply! thanks!

I don't have any experience working with onnx opset 11.  Please redirect your question to https://github.com/NVIDIA/TensorRT/issues.


Templates are useless

While I do understand how you can use them, my opinion is that these are useless templates for reason that you are using tables and content is in various  tags, which is basically against the HTML guidelines. This makes it so hard to simply provide content, and run it in the template. It is HTML template, but not usable.

Hey @rmaddox can you be a little more specific about which parts are against which guidelines.
Thanks!

I get the feeling what you get now. I am not a new user of templates, and I am Internet user since before the browser came. I was among first in my area to open up new websites. And I am using now over 150 various templates. Still searching for simplest one, I was thinking your is simplest, but it is not. It is full of tables inside,  etc.
When we speak of a template, I think of: content to be put in the template, isn't it?
This is here what I think that is content:

Something Big...

Hi Stranger,

Kielbasa venison ball tip shankle. Boudin prosciutto landjaeger, pancetta jowl turkey tri-tip porchetta beef pork loin drumstick.    Filet mignon ham hock kielbasa beef ribs shank. Venison swine beef ribs sausage pastrami shoulder.

By the way, if you're wondering where you can find more of this fine meaty filler, visit Bacon Ipsum.

– Mr. Pen

And here is what you think how I shall insert such content:

Something Big...

Hi Stranger,

Kielbasa venison ball tip shankle. Boudin prosciutto landjaeger, pancetta jowl turkey tri-tip porchetta beef pork loin drumstick.    Filet mignon ham hock kielbasa beef ribs shank. Venison swine beef ribs sausage pastrami shoulder.

                                        Share the Awesomeness

By the way, if you're wondering where you can find more of this fine meaty filler, visit Bacon Ipsum.

– Mr. Pen

Sent by Company Name, 1234 Yellow Brick Road, OZ, 99999

<a<EMAIL_ADDRESS>| Unsubscribe

if I wish to place the button, I am supposed to make a table?!
for footer I understand, it is maybe same for all content
content is in
header is also in other

So how am I supposed to insert header and content? Do you get the idea? I know how to do it, I have made my own CMS several times. I know how to insert variables, but it is just not user friendly.
If there is anything like here is content then I expect  to put everything there, and not to separate header in other place outside of content scope.
Basically, template should be template, separate from content, so that any content may be quickly changed and replaced. I would simply insert a variable inside like {$page_content} or something and it would appear as HTML in the template.
Sorry for disturbance.

Tables are annoying and a gross way to do layout — I know. The issue is email HTML is stuck in the year 2001, back when the first browser war had reached it's peak and <blink> and <marquee> tags roamed the web freely. We're still feeling the fallout today, check out Campaign Monitor's chart for a list of which email clients support which CSS rules. It's crazy.
These email templates are written in such a way to maximize compatibility and responsiveness across most email clients. It makes it more difficult to template, but you save yourself some debugging time when a user on Outlook 2007 complains about a button not rendering properly.

yes, thank you.
I was thinking yours was the simplest, but have to degrade it down. It looks nice for me. I just removed the tables and all. I need blank


Fix run timing bug for runs [JENKINS-40162]

Also incidentally fix computation of queue durations (legacy logic was not using run startTime/timestamp like it should, apparently un-noticed because the difference is small).
Run duration (as separate from stage) was not getting the end time directly from the run like it ought to.
JENKINS-40162.

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


server-side + YADCF (data_range filter does not display any data)

I'm using Datatables in server-side mode with custom paging, ordering and searching - I'm just passing the results based on data sent by DataTables to server at each draw - so I'm not loading the entire table.
YADCF text filters works fine, but data_range filters don't and I don't know how to make them work.
Here's my controller code (I'm using Laravel 5.5.48):
public function injectQuery($query, $request, $columns) {
    if ($request['columns'][7]['search']['value'] != null) {
        $date = $request['columns'][7]['search']['value'];
        $date = explode('-yadcf_delim-', $date);
        $min_date = $date[0];

        if ($date && sizeof($date) > 1) {
            $max_date = $date[1];
        }

        if ($min_date)
            $query->whereDate($request['columns'][7]['name'], '>=', $min_date);

        if ($max_date)
            $query->whereDate($request['columns'][7]['name'], '<=', $max_date);
    }

    return $query;
}

public function getDataTablesJsonActivities(Request $request) {
    $query = Activity::query();
    $columns = $request['columns'];

    return DataTables::of($query)
        ->filter(function($query) use ($columns, $request) {
            $query = $this->injectQuery($query, $request, $columns);
        }, true)
        ->toJson();
}

Laravel query result seems to be OK, but no data is populated to Datatables. Here are some videos for more details:
https://streamable.com/pjz41s
https://streamable.com/ibyljl
Perhaps there is way to disable YADCF filtering for this column?
System details

Operating Syste: Ubuntu 16.04 LTS
PHP Version: 7.3.16
Laravel Version: 5.5.48
Laravel-Datatables Version: 8.13.7

Originally posted by @phuthoma in https://github.com/yajra/laravel-datatables/issues/463#issuecomment-617059794

The problem seems to be caused by YADCF, which is sending it's date value to query:

Yajra, can it be removed?

Using filterColumn() method solves this problem.


added helm.mox.sh repo

Signed-off-by: Javier Moreno<EMAIL_ADDRESS>

@javimox The Artifact Hub is live. You can also list your Helm repo there. To do that, you login (or create an account), and list your repository. You can link it to a user or organization.

Thank you @mattfarina. The repo is now listed in artifact hub too.