text:
Super scaffolding breaks roles.yml with improper indentation

I did this:
./bin/super-scaffold crud Billing::SubscriptionExtension Team extension_team_id:super_select{class_name=Team} --trace

And got this output:
Writing './app/controllers/account/billing/subscription_extensions_controller.rb'.
Fixing Standard Ruby on './app/controllers/account/billing/subscription_extensions_controller.rb'.
Writing './app/views/account/billing/subscription_extensions/index.html.erb'.
Writing './app/views/account/billing/subscription_extensions/_menu_item.html.erb'.
Writing './app/views/account/billing/subscription_extensions/_index.html.erb'.
Writing './app/views/account/billing/subscription_extensions/_subscription_extension.html.erb'.
Writing './app/views/account/billing/subscription_extensions/edit.html.erb'.
Writing './app/views/account/billing/subscription_extensions/show.html.erb'.
Writing './app/views/account/billing/subscription_extensions/_form.html.erb'.
Writing './app/views/account/billing/subscription_extensions/new.html.erb'.
Writing './app/views/account/billing/subscription_extensions/_breadcrumbs.html.erb'.
Proceeding to generate './app/views/api/v1/billing/subscription_extensions'.
Writing './app/views/api/v1/billing/subscription_extensions/_subscription_extension.json.jbuilder'.
Writing './app/views/api/v1/billing/subscription_extensions/index.json.jbuilder'.
Writing './app/views/api/v1/billing/subscription_extensions/show.json.jbuilder'.
Writing './config/locales/en/billing/subscription_extensions.en.yml'.
Writing './app/controllers/api/v1/billing/subscription_extensions_controller.rb'.
Fixing Standard Ruby on './app/controllers/api/v1/billing/subscription_extensions_controller.rb'.
Writing './test/controllers/api/v1/billing/subscription_extensions_controller_test.rb'.
Fixing Standard Ruby on './test/controllers/api/v1/billing/subscription_extensions_controller_test.rb'.
Updating './test/factories/billing/subscription_extensions.rb'.
Updating './app/models/team.rb'.
rake aborted!
Psych::SyntaxError: (<unknown>): mapping values are not allowed in this context at line 4 column 9
<internal:/Users/jgreen/.asdf/installs/ruby/3.2.1/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
<internal:/Users/jgreen/.asdf/installs/ruby/3.2.1/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
Tasks: TOP => bullet_train:super_scaffolding
(See full trace by running task with --trace)

Adding --trace didn't get me any additional info.
I finally traced the issue down to the fact that the first few lines of roles.yml had been updated to this:
default: # AKA : listener
  models:
  Billing::SubscriptionExtension: read

Instead of this:
default: # AKA : listener
  models:
    Billing::SubscriptionExtension: read

I corrected the indentation and then re-ran the scaffolding command and then the rest of the scaffolding process seemed to work.

Strange, the indentation is working for me 🤔 Can I ask what you wrote for rails g model?

I think it was something like rails g model Billing::SubscriptionExtension team:references extension_team:references.

Looked over this one again today, can't seem to reproduce... I don't want to close it though if it really is a problem, so I think I'll leave this one be until we can pin down what the actual issue is.
If anything, the only thing that comes to mind is the BlockManipulator and how we've changed the indentation logic in the past. Will consider looking into that if we make any progress.

I just tested this again and it has something to do with the comment on the first line. With no trailing comment everything works as expected, but a trailing comment on either of the first to lines causes different problems.
With this I get the error and broken indentation described in the original issue.
default: # test
  models:
    Team: read

With this there's no error thrown, but the new model ends up being added in the wrong spot.
default:
  models: # test
    Team: read

Instead of the new model being added under default.models it's added under editor.models.
default:
  models: # test
    Team: read
    Membership:
      - read
      - search
    Platform::Application: read
    Webhooks::Outgoing::Endpoint: manage
    Webhooks::Outgoing::Event: read
    Webhooks::Outgoing::Delivery: read
    Webhooks::Outgoing::DeliveryAttempt: read
    Invitation:
      - read
      - create
      - destroy

editor:
  models:
    Billing::SubscriptionExtension: read
    Scaffolding::CompletelyConcrete::TangibleThing: manage
    Scaffolding::AbsolutelyAbstract::CreativeConcept:
      - read
      - update

admin:
  includes:
    - editor
  manageable_roles:
    - admin
    - editor
  models:
    Billing::SubscriptionExtension: manage
    Team: manage
    Membership: manage
    Scaffolding::AbsolutelyAbstract::CreativeConcept: manage
    Platform::Application: manage

I suspect the problem is here:
https://github.com/bullet-train-co/bullet_train-core/blob/779fdd93b6414953e3cdfab8c4e4d9e219af47a6/bullet_train-super_scaffolding/lib/scaffolding/file_manipulator.rb#L53
We're expecting the line to exactly match instead of checking that it starts with the right thing. Or maybe we should strip comments and then check for an exact match?

authors: gazayas jagthedrummer


text:
🛑 Website is down

In 5b54aef, Website ($MAIN_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Website is back up in 1dd301d.

source: gharchive/issue

repo: buluma/uptime

license: MIT

license_type: permissive

license_source: github-api


text:
Transcription output

Hi,
Good paper! I'm trying to run your trained model and want to get some transcriptions. However, I find it difficult to save the transcriptions to a file so that I can do some research. Could you please help me with that?
Many thanks,
Zhaofeng

Hi,
Thanks for your interest in the paper.
Are you trying to transcribe a list of audio files?
This should be easy to do by adding a "transcribe" function to "AudioEfficientConformerInterCTC", "VisualEfficientConformerInterCTC" and "AudioVisualEfficientConformerInterCTC" in models_zoo.py similar to what is done in the NeMo toolkit.
The function could take the list of audio file paths as argument, return a list of transcriptions.
You could then use this function to transcribe your data and then save them to a text file.

Hi,
Thanks a lot for your suggestion. I will try that!
Many thanks

authors: burchim chaufanglin

repo: burchim/AVEC


text:
Autocomplete Doesn't Respect Capitalization

I typed "Airport" as the name of a location. The first autocomplete suggestion was "a", which changed my capital A to a lower-case a. Ignoring the autocomplete suggestion, I typed "irport", which resulted in "airport" instead of "Airport."
Related: both "a" and "A" are in the autocomplete list; presumably we could end up with both "tokyo" and "Tokyo" (and "tOkYo"), which should probably all be grouped into a single case-insensitive entity.

Still an issue in v3

OK so I now have two behaviors for autocompleting text fields:
Restricted Entry
For input fields where only known values are allowed, autocomplete will offer options if there are multiple, or simply complete the word if there is only one match.
For example, of the only two Rangers with handles starting with "E" were Easy E and El Weso, typing a "E" into the Rangers input field will show two options, and typing "Ea" will complete to "Easy E".
The "Restricted Entry" behavior applies to the Ranger, Incident Type, and Concentric Street Address input fields.
Unrestricted Entry
Location names don't currently autocomplete in v3 but when they do, you will be allowed to type anything into the field.  In order to get a completion value, you have to choose it; at no point will it complete a word for you.  This is done by putting whatever you have entered into the field in as the first option in the completions list, before all of the pre-existing location names.
This avoids the annoying behavior described in #20 and also respects case.
The "Unrestricted Entry" behavior will apply to the Location Name input field.
I'll leave this open until I add autocomplete into the location name field, so it can be verified.

Location names complete in https://github.com/burningmantech/ranger-ims-mac/commit/1cab1e8cd18c59ae5be8bae4cb756de5ded701e7 in the manner noted above.

Please verify with [Incidents 3.0a1] (https://github.com/burningmantech/ranger-ims-mac/releases/tag/v3.0a1).

repo: burningmantech/ranger-ims-mac

license_source: bigquery


text:
Update composer.json

PHP Version requirement in CakePHP was briefly 5.4.19 , was relaxed to 5.4.16
Refer to: cakephp/app@7e28901

#35 Removing the php version from the require of composer.json The version requirement will be fulfilled by the CakePHP dependency. If you look at DebugKits composer.json it doesn't specify the version either. And I think it makes sense to no specify it except the plugin requires a higher version.

But composer.json did specify the version as 5.4.19 in 3.0 branch
composer.json. perhaps i didnt understand something. Your plugin is the
only thing requiring php update with cake 3.0.
Best regards,
Lauri Pihlajakangas
On 6 Jun 2015 00:50, "Florian Krämer" notifications@github.com wrote:

#35 https://github.com/burzum/cakephp-imagine-plugin/pull/35 Removing
the php version from the require of composer.json The version requirement
will be fulfilled by the CakePHP dependency. If you look at DebugKits
composer.json
https://github.com/cakephp/debug_kit/blob/master/composer.json it
doesn't specify the version either. And I think it makes sense to no
specify it except the plugin requires a higher version.
—
Reply to this email directly or view it on GitHub
https://github.com/burzum/cakephp-imagine-plugin/pull/35#issuecomment-109448797
.

Yes, the plugin specified the version, but instead changing it I removed it for the reasons I've explained before: The plugin tells composer it requires CakePHP 3.x. CakePHP 3.x tells composer what php version it needs and composer checks that version. Imagines minimum requirement is 5.3 https://github.com/avalanche123/Imagine/blob/develop/composer.json so it's fine to remove the php version requirement from the plugins composer.json as I did.

source: gharchive/pull-request

authors: burzum lpihlajak

repo: burzum/cakephp-imagine-plugin

license: mit


text:
Update datetime_helpers.py

Cleaner approach using mapping for freq_to_timedelta, more pythonic, should also be slightly more efficient.

Minor change to make freq_to_timedelta function more readable, more efficient, and  just more Pythonic.  No conflicts with base. Easy merge.

Closed as I have added more and will make a more comprehensive PR for numerous functions in the datetime_helpers.

repo: business-science/pytimetk


text:
simpsons.csv refactor to be The Family Guy

https://github.com/busse/kodumisto-playground/blob/main/simpsons.csv
Refactor this csv file to represent The Family Guy instead of The Simpsons.

Between #29 and #30 I added the model variable to the PR. #29 which used gpt-4 is noticeably better; arguably more "correct"

repo: busse/kodumisto-playground


text:
Floating-Point Representation and Precision Error in transaction amount calculation

The issue is related to floating-point arithmetic in Python, which affects the accuracy of transaction amount calculations. Specifically, when performing arithmetic operations with floating-point numbers, the results can sometimes be slightly off due to the way floating-point numbers are represented in binary format and when these transactions accumulate, the final account budget result is different from the reality(sometimes by a significant amount). This can lead to incorrect financial tracking and budgeting
Example
For instance, the calculation -9.95 * 100 results in -994.9999999999999 instead of the expected -995 and results in amount of -9.94 added to ActualBudget instead of -9.95.
This might be a breaking change for some users that implemented float-type amount insert using actualpy
References

Python decimal module documentation
Floating-point arithmetic issues

Hello @maxtacu ,
I do not feel like we should drop support the float, but instead handle it better and round the result. It seems like the issue is due to the fact that the int function will truncate the number, rather than rounding it. I was actually unaware of this behaviour. We could get around this by rounding the final floating number, or first converting it to decimal before doing any operations.
For example:
>>> int(-9.95*100)
-994.9999999999999   # does not work
>>> round(-9.95*100)
-995                                 # works

Let me know what do you think, here are the proposed changes:
diff --git a/actual/database.py b/actual/database.py
index 07cd232..eda9750 100644
--- a/actual/database.py
+++ b/actual/database.py
@@ -594,7 +594,7 @@ class Transactions(BaseModel, table=True):
         self.date = int(datetime.date.strftime(date, "%Y%m%d"))

     def set_amount(self, amount: Union[decimal.Decimal, int, float]):
-        self.amount = int(amount * 100)
+        self.amount = int(round(amount * 100))

     def get_amount(self) -> decimal.Decimal:
         return decimal.Decimal(self.amount) / decimal.Decimal(100)
diff --git a/actual/queries.py b/actual/queries.py
index 7cc1a15..916e7bb 100644
--- a/actual/queries.py
+++ b/actual/queries.py
@@ -175,7 +175,7 @@ def create_transaction_from_ids(
         id=str(uuid.uuid4()),
         acct=account_id,
         date=date_int,
-        amount=int(amount * 100),
+        amount=int(round(amount * 100)),
         category_id=category_id,
         payee_id=payee_id,
         notes=notes,
(END)

@bvanelli rounding sounds good!
as long as Actual doesn't add support for 3 digits decimal numbers 😄

@bvanelli rounding sounds good! I will update the PR as long as Actual doesn't add support for 3 digits decimal numbers 😄

Yeah, I wonder if they will ever add that, I believe is required when they support multi currency because of cryptocurrency.
Anyways, would you mind adding a test for the failing case (i.e. adding one transaction with -9.95) as value?

Looks good to me, there is one issue with the pre-commit and one issue with the typing, but I'll fix that once merged. I created https://github.com/bvanelli/actualpy/issues/80 to also document the pre-commit stuff.

authors: bvanelli maxtacu

repo: bvanelli/actualpy


text:
server rendering with WindowScroller

I'm using next.js for server rendering.
Below code has a console warning
Warning: Expected server HTML to contain a matching <div> in <div>.
I think client rendering is failed with this warning, so the List has no row.
If I change WindowScroller to AutoSizer, then there is no console warning.
I don't know what causes this warning.

If I skip server rendering like below, it also has the warning but the rows are rendered correctly on client side.
render() {
    if (!IS_CLIENT) {
      return null;
    }
    ...

WindowScroller depends on a window object, else it falls back to a width and height of 0. I guess we could add serverWidth/serverHeight props, but it's possible that the server and client markup would still different based on the actual size of the client window.
Edit Looks like you already opened a PR for this. (Thanks!) I don't mind making this addition, although I'm going to tweak it slightly.

Going out as 9.14.0

authors: bvaughn landvibe

repo: bvaughn/react-virtualized


text:
Avoid extra conditional checks with function params

Assigning null and then doing x || this.x means you end up doing an extra check that's not really needed. You always have this.state and this.props, and both _updateScrollLeftForScrollToColumn and _updateScrollTopForScrollToRow are never called with falsy values. (If it were possible for em to get called with falsy values, you'd probably wanna skip the = null in the function param instead.)

[Current coverage][cc-pull] is 95.89%

Merging [#239][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master       #239   diff @@
==========================================
  Files            30         30
  Lines           952        948     -4
  Methods          85         85
  Messages          0          0
  Branches        206        202     -4
==========================================
- Hits            913        909     -4
  Misses           39         39
  Partials          0          0

Powered by Codecov. Last updated by [6876cb2...a11459e][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bvaughn/react-virtualized/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bvaughn/react-virtualized/compare/6876cb27a89b626ccb5c4227b7d3739550880657...a11459ec5bef4d8b3646be79c4f0d2b62c80731b
[cc-pull]: https://codecov.io/gh/bvaughn/react-virtualized/pull/239?src=pr

authors: cesarandreu codecov-io


text:
🛑 Prakruthi Villas Sarjapura is down

In d54b879, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 235 ms

Resolved: Prakruthi Villas Sarjapura is back up in 0e21ac9.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Sai Gardens Temple Side is down

In 52f8e0a, Sai Gardens Temple Side (https://cloud.tymly.in/status/1074) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sai Gardens Temple Side is back up in 0b17b54.


text:
🛑 Trifecta Esplanade P Block is down

In 3f758c8, Trifecta Esplanade P Block (https://cloud.tymly.in/status/1017) was down:

HTTP code: 521
Response time: 21163 ms

Resolved: Trifecta Esplanade P Block is back up in b531858.


text:
🛑 Adithya Pristine KMC is down

In 7661ac3, Adithya Pristine KMC (https://cloud.tymly.in/status/1028) was down:

HTTP code: 521
Response time: 207 ms

Resolved: Adithya Pristine KMC is back up in f0cc43b.


text:
🛑 Sumadhura Silver Ripples Club House is down

In 8e23a5b, Sumadhura Silver Ripples Club House (https://cloud.tymly.in/status/1090) was down:

HTTP code: 521
Response time: 20235 ms

Resolved: Sumadhura Silver Ripples Club House is back up in 5337225.


text:
🛑 PSR Aster 1 is down

In a5e207a, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 235 ms

Resolved: PSR Aster 1 is back up in 4c981cc.


text:
🛑 SMR Vinay Cascade A Block is down

In f2c6a77, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SMR Vinay Cascade A Block is back up in 7e736b8.


text:
🛑 SMR Vinay Cascade A Block is down

In d4a253e, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20252 ms

Resolved: SMR Vinay Cascade A Block is back up in d079c5e.


text:
🛑 Dasta Concerto Basement is down

In 47d2800, Dasta Concerto Basement (https://cloud.tymly.in/status/1138) was down:

HTTP code: 521
Response time: 20236 ms

Resolved: Dasta Concerto Basement is back up in af7f7c7.


text:
🛑 Sumadhura Silver Ripples Club House is down

In 2158ad2, Sumadhura Silver Ripples Club House (https://cloud.tymly.in/status/1090) was down:

HTTP code: 521
Response time: 20234 ms

Resolved: Sumadhura Silver Ripples Club House is back up in 85c967b.


text:
🛑 Prakruthi Villas Sarjapura is down

In e23fb15, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 215 ms

Resolved: Prakruthi Villas Sarjapura is back up in d17071c.


text:
🛑 Trifecta Esplanade Security is down

In 34dbb53, Trifecta Esplanade Security (https://cloud.tymly.in/status/1168) was down:

HTTP code: 521
Response time: 222 ms

Resolved: Trifecta Esplanade Security is back up in 03e4b1e.


text:
🛑 Mahaveer Varna A1 is down

In 2e146a3, Mahaveer Varna A1 (https://cloud.tymly.in/status/1083) was down:

HTTP code: 521
Response time: 20242 ms

Resolved: Mahaveer Varna A1 is back up in 78e5777.


text:
🛑 Mahaveer Varna A1 is down

In f4bca7b, Mahaveer Varna A1 (https://cloud.tymly.in/status/1083) was down:

HTTP code: 521
Response time: 20254 ms

Resolved: Mahaveer Varna A1 is back up in d6f4c20.


text:
🛑 Trifecta Esplanade C Block is down

In 5c94d63, Trifecta Esplanade C Block (https://cloud.tymly.in/status/1155) was down:

HTTP code: 521
Response time: 20222 ms

Resolved: Trifecta Esplanade C Block is back up in ebce66e.


text:
🛑 Sai Gardens Community Hall is down

In 93939b9, Sai Gardens Community Hall (https://cloud.tymly.in/status/1073) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sai Gardens Community Hall is back up in a695aba.


text:
🛑 DSR Sunrise Towers 2 is down

In 2eab919, DSR Sunrise Towers 2 (https://cloud.tymly.in/status/1027) was down:

HTTP code: 521
Response time: 20247 ms

Resolved: DSR Sunrise Towers 2 is back up in acbbc8f.


text:
🛑 Sumadhura Silver Ripples Club House is down

In 0669992, Sumadhura Silver Ripples Club House (https://cloud.tymly.in/status/1090) was down:

HTTP code: 521
Response time: 20234 ms

Resolved: Sumadhura Silver Ripples Club House is back up in 0c71841.


text:
🛑 DSR Sunrise Towers is down

In 79ce0da, DSR Sunrise Towers (https://cloud.tymly.in/status/1025) was down:

HTTP code: 521
Response time: 230 ms

Resolved: DSR Sunrise Towers is back up in 8d71ee1.


text:
🛑 Trifecta Esplanade Security is down

In dcff245, Trifecta Esplanade Security (https://cloud.tymly.in/status/1168) was down:

HTTP code: 521
Response time: 241 ms

Resolved: Trifecta Esplanade Security is back up in 4c04b9b.


text:
🛑 SMR Vinay Cascade B Block is down

In ec20f60, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20238 ms

Resolved: SMR Vinay Cascade B Block is back up in c2ddc56.


text:
🛑 VBHC Serene Town A Block is down

In 5d7e3a7, VBHC Serene Town A Block (https://cloud.tymly.in/status/1129) was down:

HTTP code: 521
Response time: 20246 ms

Resolved: VBHC Serene Town A Block is back up in af1a9aa.


text:
🛑 Trifecta Esplanade C Block is down

In 93e181c, Trifecta Esplanade C Block (https://cloud.tymly.in/status/1155) was down:

HTTP code: 521
Response time: 232 ms

Resolved: Trifecta Esplanade C Block is back up in f308848.


text:
🛑 Desai Grandeur 1 is down

In 6f15d7f, Desai Grandeur 1 (https://cloud.tymly.in/status/1133) was down:

HTTP code: 521
Response time: 214 ms

Resolved: Desai Grandeur 1 is back up in dbccebd.


text:
🛑 Trifecta Esplanade A Block is down

In 5b06e2f, Trifecta Esplanade A Block (https://cloud.tymly.in/status/1153) was down:

HTTP code: 521
Response time: 20262 ms

Resolved: Trifecta Esplanade A Block is back up in 336d850.


text:
🛑 Dasta Concerto Basement 2 is down

In 4e1de00, Dasta Concerto Basement 2 (https://cloud.tymly.in/status/1188) was down:

HTTP code: 521
Response time: 20246 ms

Resolved: Dasta Concerto Basement 2 is back up in 4be5c85.


text:
🛑 United Elysium is down

In 30fdcd9, United Elysium (https://cloud.tymly.in/status/1019) was down:

HTTP code: 0
Response time: 0 ms

Resolved: United Elysium is back up in 87255ef after 890 days, 23 hours, 41 minutes.


text:
🛑 SNR Silver Ripples is down

In 0b43de6, SNR Silver Ripples (https://cloud.tymly.in/status/1039) was down:

HTTP code: 521
Response time: 20242 ms

Resolved: SNR Silver Ripples is back up in a020079.


text:
General Question: What is $stateParams and how should we use it here?

https://github.com/bwann52/Bloc-Chat/blob/list-messages/app/scripts/controllers/HomeCtrl.js#L19

These are state parameters and associated with the angular-ui-router you setup in app.js https://github.com/bwann52/Bloc-Chat/blob/list-messages/app/scripts/app.js#L10
I did some quick google looking for more information about $stateParams:
angular-ui routing
AngularJS: $stateParams
Learning: UI-Router and passing values in $stateParams


text:
Smart Switch Support

Please explain your feature request in a one or two sentences.
I wanted to add my Meross Smart Switches to homebrige with this plugin but they didn't show up. In the log it said:

[Smart Switch] is currently not supported, do create a github issue https://git.io/JtfVC with info:
{"uuid":"2105109139581890850948e1e970e0d5","onlineStatus":1,"devName":"Smart Switch","devIconId":"device027_un","bindTime":1631345651,"deviceType":"mss710r","subType":"un","channels":[{}],"region":"eu","fmwareVersion":"4.2.3","hdwareVersion":"4.0.0","userDevIcon":"","iconType":1,"skillNumber":"","cluster":1,"domain":"mqtt-eu.meross.com","reservedDomain":"mqtt-eu.meross.com","firmware":"4.2.3","hbDeviceId":"2105109139581890850948e1e970e0d5","model":"MSS710R"}

...and for the second one:
[Smart Switch] is currently not supported, do create a github issue https://git.io/JtfVC with info:
{"uuid":"2105109694958990850948e1e970f78a","onlineStatus":1,"devName":"Smart Switch","devIconId":"device027_un","bindTime":1631345649,"deviceType":"mss710r","subType":"un","channels":[{}],"region":"eu","fmwareVersion":"4.2.3","hdwareVersion":"4.0.0","userDevIcon":"","iconType":1,"skillNumber":"","cluster":1,"domain":"mqtt-eu.meross.com","reservedDomain":"mqtt-eu.meross.com","firmware":"4.2.3","hbDeviceId":"2105109694958990850948e1e970f78a","model":"MSS710R"}

The product number is MSS710HKIT. I read that there is support for the regular MSS710 but aparently not the HomeKit version.
The Github link is dead but I thought I should post here.

Is your feature request related to a problem? Please describe.
No

Any particular Meross devices that this relates to?
The Meross Smart Wi-Fi Switch with HomeKit support

Anything else?
Thanks for making this plugin!

It's working! I had to use my username and password though. With only the key it didn't work but that could also be my fault.
Thanks for the quick fix! :)

The key is used for local control, and you need to configure the device in the plugin settings for local control too.
Using just the key on its own will not work, this may be of help:
https://github.com/bwp91/homebridge-meross/wiki/Local-Control#device-setup

Thanks it's working now! :D
Should I close the issue?

Closed!


text:
CS0138 and CS0234 errors when trying to build

Describe the bug
I'm getting CS0138 on the start - "using namespace" can be only used towards namespaces. Element "Json" is a type not namespace.
Then I'm getting CS0234 on the whole thing. Stuff like Type or namespace "GraphQLTypeAttribute" doesn't exist in the namespace of "MyNamespace.ZeroQL"
Not sure if it's' the API i'm using is not compatible or what but I cannot get it work.
If you'd like to test then this is a public API - https://graphql.anilist.co
Also while at it is it possible to turn off auto generation on each build?  I'd like to implement INotifyPropertyChanged on the classes. If not possible I guess I'll have to map them to my own ones. But it would be great if it was possible to derive from interfaces in the future. INotifyPropertyChanged is heavily required on any UI application in .NET.

I have skipped the following section during bug creation. It would be nice to have it. It will definitely help with investigation.
Environment (please complete the following information):

Nuget package version [6.0.0]
IDE: [VS, VS for Mac, Rider, VS Code]
.Net Version [6.0.400, 7.0.100]

I have tried to reproduce the issue with the 7.0.0-preview.5 version and everything compiles works as expected. I don't see any issues.
The error itself signals that some core parts of library is missing completely. Are you sure that you installed the CLI tool and nuget package correctly?

When I followed exactly your CLI steps it worked. Idk why I couldn't get it to work on existing one. Works good, the learning curve is there definitely. Seems weird at first. Is there a possibility for me to edit classes somehow without regeneration?

Is there a possibility for me to edit classes somehow without regeneration?
The generated classes main goal is to help to define the GraphQL query. They are not intended as the DTO objects.
As a result, there is not way to edit them.


text:
Error in execution

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'cme smb 172.16.0.1/24  -u 'use3r -p 'password' --shares ''
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Traceback (most recent call last):
File "src/gevent/greenlet.py", line 766, in gevent._greenlet.Greenlet.run
File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg/cme/protocols/smb.py", line 110, in init
connection.init(self, args, db, host)
File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg/cme/connection.py", line 47, in init
self.proto_flow()
File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg/cme/connection.py", line 82, in proto_flow
self.login()
File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg/cme/connection.py", line 251, in login
if self.plaintext_login(self.domain, user, password): return True
File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.2.dev0-py3.8.egg/cme/protocols/smb.py", line 281, in plaintext_login
self.conn.login(username, password, domain)
File "/usr/lib/python3/dist-packages/impacket/smbconnection.py", line 265, in login
return self._SMBConnection.login(user, password, domain, lmhash, nthash, ntlmFallback)
File "/usr/lib/python3/dist-packages/impacket/smb.py", line 3385, in login
self.login_extended(user, password, domain, lmhash, nthash, use_ntlmv2 = True)
File "/usr/lib/python3/dist-packages/impacket/smb.py", line 3293, in login_extended
type3, exportedSessionKey = ntlm.getNTLMSSPType3(auth, respToken['ResponseToken'], user, password, domain, lmhash, nthash, use_ntlmv2 = use_ntlmv2)
File "/usr/lib/python3/dist-packages/impacket/ntlm.py", line 631, in getNTLMSSPType3
ntResponse, lmResponse, sessionBaseKey = computeResponse(ntlmChallenge['flags'], ntlmChallenge['challenge'],
File "/usr/lib/python3/dist-packages/impacket/ntlm.py", line 39, in computeResponse
return computeResponseNTLMv2(flags, serverChallenge, clientChallenge, serverName, domain, user, password,
File "/usr/lib/python3/dist-packages/impacket/ntlm.py", line 902, in computeResponseNTLMv2
responseKeyNT = NTOWFv2(user, password, domain, nthash)
File "/usr/lib/python3/dist-packages/impacket/ntlm.py", line 891, in NTOWFv2
return hmac_md5(theHash, user.upper().encode('utf-16le') + domain.encode('utf-16le'))
File "/usr/lib/python3/dist-packages/impacket/ntlm.py", line 882, in hmac_md5
h = hmac.new(key)
File "/usr/lib/python3.8/hmac.py", line 153, in new
return HMAC(key, msg, digestmod)
File "/usr/lib/python3.8/hmac.py", line 51, in init
raise TypeError("Missing required parameter 'digestmod'.")
TypeError: Missing required parameter 'digestmod'.
2020-06-06T19:51:50Z <Greenlet at 0x7f1db2b67590: smb(Namespace(aesKey=False, clear_obfscripts=False, co, <protocol.database object at 0x7f1db2b05640>, '172.16.0.9')> failed with TypeError
Crackmapexec info

OS: Kali 2020-1
Version of CME [e.g. v5.0.2]
using latest release

Additional context
no

https://github.com/byt3bl33d3r/CrackMapExec/issues/386

authors: meetgyn mpgn


text:
Limit heap size in app and libc

Hi,
According to this, the WASM uses:

libc heap,  when exporting malloc/free.
app heap, otherwise.

Is there a way to limit the libc heap as it is with app heap?
According to wasm_runtime_instantiate, the heap_size only affects the app size.

When exporting, the (app) heap size is set to 0.

We believe that we can limit it by using,

--max-memory=   Maximum size of the linear memory

from wasm-ld, but it will limit the full linear memory, not just the heap.

The maximum libc heap size I have been able to allocate has always been less than expected by the formula in all the tests I have run. I guess we'll have to check https://github.com/WebAssembly/wasi-libc/blob/main/dlmalloc/src/malloc.c in detail.
I'll close it for now.

repo: bytecodealliance/wasm-micro-runtime


text:
使用emcc编译.c文件时会报错，但能正常生成.wasm文件并运行正常，请问如何消除错误提示。

我在一个hello.c文件中申明了：
int foo(int a, int b);
void foo2(char * msg, char * buffer, int buf_len);
EMSCRIPTEN_KEEPALIVE
int test2(char* strParam ,int iParam)
{
printf("p1:%s , p2:%d .\n",strParam,iParam);
int c = foo(3, 3);
printf("test2 add:%d .\n",c);

char * msg = "hello";
char buffer[100];
foo2(msg, buffer, sizeof(buffer));   // call into native foo2()
printf("test2 buffer:%s .\n",buffer);

return 1;
// return "from wasm test1 api";

}
使用命令：emcc -O3 hello.c -o hello.wasm -s STANDALONE_WASM --no-entry

不过可以正常运行输出结果：

error: undefined symbol: foo (referenced by top-level compiled C/C++ code) warning: Link with -sLLD_REPORT_UNDEFINEDto get more information on undefined symbols warning: To disable errors for undefined symbols use-sERROR_ON_UNDEFINED_SYMBOLS=0 warning: _foo may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library error: undefined symbol: foo2 (referenced by top-level compiled C/C++ code) warning: _foo2 may need to be added to EXPORTED_FUNCTIONS if it arrives from a system library Error: Aborting compilation due to previous errors
我要如何消除这个错误提示呢？

IIUC, foo and foo2 are undefined symbols. what's your expectation on whole program?

我要在c++中加载这个wasm。foo和foo2的申明放在wasm文件中，foo和foo2定义在c++本地，我想在使用emcc编译时能以正确的方式编译，并不会报错。我不确定是不是我的操作有什么问题。因为虽然能编译出wasm并能正常运行，但感觉不完善，因为他是报过错的。
我要怎么写这个wasm文件，能正常调用外部函数，并在编译时不会报错？感谢！

in that case, callback is an example to start with. Please be aware of that, there is no need to prepare callback.wat. You should write a c++ program and use emcc to compile it to Wasm.
In C/C++, use import_name and import_module to declare a import function.


text:
Census of binaryen/wasm-opt passes that might be relevant to Cranelift

What is Cranelift's job (in the context of Wasmtime)? To take Wasm that is produced by LLVM and already optimized 99% of the time and do the architecture-specific code generation that LLVM cannot do when targeting Wasm (e.g. instruction selection, regalloc). We don't want to duplicate all of LLVM's mid-end optimizations, only the ones that are beneficial for cleaning up and improving code after we've lowered Wasm memory operations into raw base + offset memory operations, etc. This is an interesting place for a compiler to be, and it means the set of passes and trade offs we have are different from what one might assume by default.
There is another compiler that is in a similar space, at least as far as consuming already-optimized-by-LLVM Wasm binaries and attempting to further optimize them: binaryen and wasm-opt. The big difference is that wasm-opt is emitting another Wasm binary while we are emitting machine code. But maybe they have passes that are not specific to targeting Wasm and which are beneficial to run on already-optimized-by-LLVM Wasm binaries? AIUI, the LLVM IR to Wasm lowering introduces some suboptimal code patterns.
So I did an informal census of what passes are run by wasm-opt, filtering out anything that looked overly specific to targeting Wasm. Results are summarized in the table below, and might give us some food for thought as we start looking into Cranelift's code quality some more. (FWIW, I wasn't 100% sure about some things below, so if you see something that you know is incorrect, feel free to edit this issue and correct it!)

Pass
Description
Cranelift has equivalent?
Discussion

local-cse
Perform common-subexpression elimination within a block
Yes
Our GVN should cover all of this.

dce
Perform dead code elimination to remove unreachable blocks and unused expressions
Yes

optimize-instructions
Peephole optimizations
Partial
We have some peepholes, but not as many as wasm-opt, and could definitely add more. Although, they care a lot about Wasm encoding tricks for peepholes where we do not. Probably better to look at LLVM itself here for inspiration. Finally, they also have some Souper-synthesized peepholes, and we should really add some of our own once the e-graphs work lands.

pick-load-signs
Look at uses of a load to determine whether to use sign extension or zero extension for the load (e.g. if the load instruction is i32.load8_u but a majority of uses are prefixed with i32.extend8_s, then change the load to i32.load8_s, remove the now-redundant sign extends from the majority of uses, and insert zero extends for the other uses.)
No
Unclear how much this is worth it in practice, especially if our primary goal is code speed rather than code size.

precompute[-propagate]
Constant propagation and folding
Partial
We have a couple peepholes in simple_preopt that do some of this, but only 2 levels deep. Should investigate doing this more completely once the WIP e-graphs work merges.

code-pushing
Push defs down towards uses. Might move the def into a block on the other side of a conditional, making it so that it is not executed unless needed.
No
Unsure whether their pass is aware of loop boundaries, and whether this might "undo" some manual LICM the programmer/LLVM did (this comes before their LICM in their phase ordering; our LICM won't create partially dead code, fwiw.) Although maybe we start (or can start) doing this with the new e-graphs work?

code-folding
Merge common tails of all of a block's predecessors into the block itself.
No
I don't believe we do any block-level optimizations that look at multiple predecessors or multiple successors at the same time (i.e. we can merge one successor block into its sole predecessor). FWIW, I don't see a dual pass for merging common heads of successor blocks into their predecessor block in wasm-opt, but that seems like an obvious thing to implement if you've implemented merging common tails of successor blocks. Totally possible it exists and I missed it.

merge-blocks
Sort of Wasm-specific, but essentially merge a block into its sole predecessor.
Yes

duplicate-function-elimination
Interprocedural optimization to deduplicate identical functions.
No
When the new incremental caching infra is enabled, I guess we could get this for free? But also depends on implementation (which I am not personally familiar with) and order of function compilation scheduling in the face of our parallelism.

inlining
Inline a callee function into its caller, removing function call overhead and, more importantly, providing opportunity for more optimization based on the actual arguments to the call.
No
We probably don't want this for regular core Wasm modules right now, since LLVM did all the profitable inlining already and has way better heuristics than anything we are going to come up with on the first try. If something is both small and not inlined into callers by the time we see it, then it was probably either marked no-inline or cold or something like that and we just don't have those annotations anymore. However, with the component model this is going to change: callees will remain a black box until after component linking time (so LLVM won't ever have had a chance to inline these calls) and we will have lots of oppotunities to do some nice cross-module inlining ourselves.

directize
Turn call_indirects into calls. Devirtualization.
No
Probably not profitable for us to do this, since LLVM already does it, but could be very profitable when done optimistically in concert with PGO data and then inline the callee into the caller.

Thanks for this in-depth look! This is a really valuable comparison.
I agree that Cranelift's goal in context as a backend for Wasmtime, with today's Wasm ecosystem, largely results in an optimization design-space that discounts traditional heavyweight analysis and calls for more directed work. I sort of touched on this recently in this comment with a from-first-principles breakdown of how should expect Cranelift to be able to optimize further as coming from (i) Wasm-to-CLIF semantic gap, (ii) CLIF-to-machine semantic gap, and (iii) regalloc quality. The meat of the (remaining) issue is in (i) and that's what you're pointing to with "cleaning up and improving code after we've lowered Wasm memory operations"; so, fully agreed.
I do also want to emphasize your point about inlining and the component model: late-binding two modules together, that have not met before and were compiled separately, completely changes the tradeoffs in that it means all of the traditional LLVM-style heavyweight analyses will find low-hanging fruit when inlining across that boundary. For that reason, and for the reason that Cranelift is also used (and hopefully used more in the future) in non-Wasm contexts, I think it's valuable to keep thinking about the heavyweight analyses even if they are turned off in a one-Wasm-module context.
(I suspect that having different meta-settings or "opt levels" would make sense here, with a preset for "one Wasm module, likely produced by an optimizing compiler" and a preset for "Wasm components with multiple modules linking together" and a preset for "unoptimizing frontend driving Cranelift".)
On the particular opts (aside from inlining covered above):

precompute-propagate and code-pushing should both be subsumed by the mid-end optimizer with its already-existing work in the prototype: in particular, the constant folding is more complete (follows an arbitrarily-long chain) and the code-motion allowed by scoped elaboration naturally pushes defs down when they are "partially redundant" (not used on some paths following computation).

we don't have anything like code-folding; I'd be curious to see how often it occurs in already-optimized modules. It should primarily benefit code size, and only indirectly speed (by reducing icache footprint); so useful if it applies but IMHO not likely to produce huge gains. I suspect this is an artifact of wasm-opt's focus on module size as well as speed.

duplicate-function-elimination should indeed fall out of the incremental compilation cache; in a mode where we care about maximizing this we could do a MapReduce-style thing where we (i) generate IR and compute cache keys for every function, then (ii) sort and deduplicate, then (iii) compile only once for each cache key. Thoughts @bnjbvr?

directize: yes absolutely, once we inline across multiple modules, I suspect this will be a very important optimization. One difficulty is that it is generally best as an interprocedural analysis, as one can reach stronger conclusions about constant function pointers this way (e.g., not only "I directly stored this function pointer" case, but "I read this field and across the program, the only function pointer stored into this field is this value" cases). That might require a bit of scaffolding to do properly.

Not covered above because out-of-scope for Wasm-to-Wasm (wasm-opt), but IMHO still important for us to build: bounds-check elimination and the value-range analysis that can feed into it.

That's all I can think of for now, but we should dump more thoughts about building any of the above here and/or split out specific issues as needed. (Also at least inlining has #4127 but I don't know if the others do already.) Thanks again for the survey!

duplicate-function-elimination should indeed fall out of the incremental compilation cache; in a mode where we care about maximizing this we could do a MapReduce-style thing where we (i) generate IR and compute cache keys for every function, then (ii) sort and deduplicate, then (iii) compile only once for each cache key. Thoughts @bnjbvr?

Indeed we should get this for free as long as the FunctionStencils are exactly the same for two different functions (think newtypes, (proc-)macro-generated code like cranelift-entity's entity_impl! or derive(serde), etc. tend to create lots of duplicated code).
Now this is the first time I hear of this MapReduce-style idea, and IIUC this is semantically equivalent to what we have right now, just changes the order of operations: in the existing implementation, a CacheStore would do the deduplication by reusing hashed entries (and likely run into race conditions which handling is deferred to the cache store impl), while in the proposal the deduplication would happen earlier, and then only the CacheStore would be probed for existing entries.
If I'm not mistaken, the MapReduce approach makes parallel compilation of functions a bit harder, as it requires precomputing all the cache keys for all functions in a module, thus reading every function's body before compiling them. I don't imagine that we expect performing streaming compilation using Cranelift any time soon.
Right now we can compile all functions in a module, in parallel, and let the CacheStore implementation handle races via locking. To explicit what I mean here: two duplicated functions may start getting compiled at the same time, the CacheStore wouldn't see existing cache entries for both, so it could compile both and store the same compiled artifact twice. The MapReduce approach would prevent all such race conditions in the CacheStore, by providing a set of unique cache keys in the first place.

authors: bnjbvr cfallin fitzgen

repo: bytecodealliance/wasmtime


text:
wasi-sockets: Implement initial listen backlog

Allow set_listen_backlog_size to be called before listening. This enables us to pass the backlog value to the initial listen syscall, which is more widely supported. This is in line with the explanation in https://github.com/WebAssembly/wasi-sockets/issues/34
Silently clamp the provided backlog value, instead of failing with OutOfMemory.

I've just committed an additional line that got lost while resolving the conflicts. Should be good to go now.


text:
Wasmer bindings

I'm opening this issue to follow up on the PR that we created a few months ago adding support for Wasmer bindings: https://github.com/bytecodealliance/wit-bindgen/pull/173, given that the project has already matured a bit.
Right now the wit-bindgen repo is supporting different bindings over runtimes that are actually not maintained by the Bytecode Alliance, namely:

JS API
Spidermonkey
Rust

In general, we believe that adding official support for more runtimes is not only desired for the community but also beneficial, as it standardizes all bindings into one repo with one name and place to go for support.
Given the comment from @tschneidereit on the PR, I understood that it might not be on the willingness of the project maintainers to add support for Wasmer bindings, but I want to be clear that this will probably imply a hard fork on the project, which I believe might not be on the best interests of the community.
I also would like to mention that Wasmer will fully cover the maintenance of the its bindings on this repo in case we agree that convergence (of one repo hosting all bindings) is the most optimal path, so no one else will need to assume the maintenance burden.
I'm opening this issue to see if we can converge on an agreement before doing any hard fork, so in the end, the Wasm users are the main beneficiaries.
Looking forward to hearing your thoughts!
Note: for anyone searching for Wasmer support on wit-bindgen in the future, here's the repo! https://github.com/wasmerio/wit-bindgen

There are a few reasons.
First one is discoverability: if people search for wit bindgen, it's very likely that they will land on this repo first. Which will make them more likely to use the runtimes supported in the "official repo", and harder for them to search for the one that is not on the main repo.
Even if Wasmer has the wit-bindgen repo, google deprioritizes forks in their search engine which makes it harder for that repo to appear in the results (try searching for "wasmer wit bindgen" and see how easy is for you to find the wasmer fork).
Second one is installation. Right now wit-bindgen is an empty crate, but it's likely that the default way of using it will be through cargo install wit-bindgen.
Once the crate is published, people will gravitate towards installing the base wit-bindgen, which will also make them gravitate mainly towards the runtimes supported there.
I frankly don't see any strong technical reason on why Wasmer bindings couldn't be on this repo. But here are some reasons on why I think it will be beneficial to have the Wasmer bindings integrated:

Both Wasmer bindings are already fully tested (we have the tests already integrated in both Wasmer Rust and Wasmer Python)
It doesn't add any more overhead for maintainers compared to other runtime integrations such as the JS or SpiderMonkey.
it doesn't require people maintaining them actively since we (Wasmer) will actively collaborate on making them up to date (we are super happy to also jump on any PR that might be refactoring stuff and update wasmer bindings accordingly, so there's 0 overhead for current maintainers)
It also incentivizes more entities to collaborate more with the repo rather than maintaining our ideas separately.
It unifies community instead of split it (a hard fork will likely not help towards unification)

In general, collaboration is usually better than not collaboration. So that's the gist ;)

There's still not been any material change to the key reasons I gave last time for not adding 3rd-party bindings to this repository.
The move to the full component model implementation is still very much in full swing, so lots of churn will necessarily still happen.
More importantly, nothing has changed about the more fundamental reasons I gave last time either. Here's the relevant part of my reply from last time:

To manage expectations for the future though, while we haven't decided on any kind of formal policy, I'm not sure we'll ever want to maintain an open-ended list of 3rd-party bindings in this repository. wit-bindgen is a project with specific stakeholders working on it with specific goals in mind, and we need to ensure that we stay focused on these. We'll base decisions around which bindings to host here strictly on whether we see it as beneficial to wit-bindgen as a project and its stakeholders, on a case-by-case basis.

The stakeholders of wit-bindgen see the bindings maintained in this repository as valuable and furthering the goals we're focused on, which is why they're included here.
As @Kylebrown9 points out, you should be able to use wit-bindgen as a dependency instead of forking it. I gave more detail on that last time, too:

Since we do appreciate that it's attractive to make use of the work done here without having to invest the considerable effort to do and maintain a full separate implementation, we structured wit-bindgen in a way that makes it easy to maintain bindings externally and make use of wit-bindgen through an API. While that API will necessarily undergo churn for a while, too, we aim to eventually have that settle down and follow semver versioning. I'd encourage you to investigate making use of this for your bindings.

If that for whatever reason doesn't work for you, then a fork might indeed be the right choice. That'd also have the added benefit of allowing you to catch up to latest developments at your own pace.
Alternatively, you could also consider doing your own completely independent implementation under a different name, which would have two significant benefits: one is that it'd allow you to fully tailor it to your needs. The other is that, as I mentioned to you in a WASI subgroup call a few months ago, having independent implementations of standardized concepts is tremendously useful in a standardization process, so by going this route you'd be able to actually support the process. It'd also solve the discoverability problem, as people intending to use Wasmer would naturally use the bindings generator you're promoting.
I hope that answers the questions you had, so I'll go ahead and close this issue.

Alternatively, you could also consider doing your own completely independent implementation under a different name

I'm not sure if you understood what I meant with a hard fork, so let me clarify.
A hard fork happened with node.js some time ago: the project was forked and distributed under a different name (io.js) because of internal disagreements on how things were moving forward (io.js was not a new implementation of node.js, was simply a fork with a different name and driven by different goals).
Hard forks are usually not beneficial for the community, so I'm trying to steer things towards collaboration before doing it.
But if a hard fork is the only option given, we'll go with it 😉 (there is no shame in doing it since everything is already open-source).
If you don't want to have Wasmer bindings in wit-bindgen, that's ok... we don't want to force anyone!
But that will have some implications, I just wanted to make sure you fully understood those, and we all try to put community first!
Feel free to re-open the issue if at some moment you decide that community interests should prevail :)

How about providing a link to your project in the README?  It is not much effort for this project to list third party implementations of the binding generators.  Plus the current implementation of the wit-bindgen binary is also a bit underbaked.  For example, it could use the same extension strategy as cargo, e.g. cargo-expand to add subcommands.
I still don't understand the cause for a fork.  Your library is dependent on the wit parser and core generator. If you find issues with these, then a PR would add value to all current and future generators. Is it because you want people to find wasmer's implementation when searching for wit-bindgen? If so, then adding your generator to the readme would help increase your SEO.

It looks like @syrusakbary you may be out of the loop a bit with this repository so I'll try to summarize the current state of things:

As Till mentioned there's still lots of work to do in this repository and https://github.com/bytecodealliance/wit-bindgen/issues/314 is an example of a large amount of churn now which, while done now, happened since you opened this issue.
Work in this repository is pivoting towards standards-based collaboration in the upstream component model repository with the start of a description here for *.wit syntax/semantics.
The work on *.wit has always intended to align with the component model. This isn't simply some random IDL we conjured up to work with a few guests and hosts, and this is codified in the wit-component library which allows generating components from *.wasm and extracting *.wit from components. Furthermore this is the basis for collaboration and features in *.wit.
For example collaboration resource types were removed from this repository temporarily and is being designed upstream now.
All host generators are being removed from this repository for example here and here. The JS generator will eventually move to its own repository as well, just takes time.

Overall if you're genuinely interested in collaborating on wit-bindgen I would encourage you to follow issues/discussions here. Chats happen on zulip and there are weekly in-person meetings on zoom to attend as well. The wheels aren't always turning at a lightning-fast pace over here so progress may seem slow sometimes but we're all always trying to march towards the shared vision of the component model.

authors: alexcrichton syrusakbary tschneidereit willemneal

repo: bytecodealliance/wit-bindgen


text:
运行报错

kali 运行报错，请问这是什么原因。

应该是内存不足，建议16g以上的内存来扫描。 如果你的app特别复杂， 可能需要专门的服务器来扫描。

authors: nkbai zhongxiaokui

repo: bytedance/appshark


text:
Updated gradle usage to take advantage of new features in 2.2

I updated the gradle version, added enableBuildCache in the gradle.properties (as per instructions here http://tools.android.com/tech-docs/build-cache) (it doesn't seem to work yet, but hopefully it will do something eventually), and added a dependency on the ConstraintLayout library ("For improved layout performance, you should convert older layouts to ConstraintLayout" - see https://developer.android.com/studio/write/layout-editor.html#convert-constraint and https://developer.android.com/training/constraint-layout/index.html)

This change is

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

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


text:
Update fargate module

Update fargate module to latest version and new repo.

Could use a rebase but otherwise LGTM.

Looks like Jamie beat me.

authors: GaryGSC joshgubler

repo: byu-oit/hello-world-api


text:
Imitate general ControlW behavior

FEATURE REQUEST
_: current cursor
You can not delete a word if there is a space before the cursor.
>>> get pod _

When this change is patched,
>>> get _

You can delete the word before cursor even if there is a space after word

Nice PR!
(Actually, my friend is also comment this behavior is wrong. Thanks)

repo: c-bata/go-prompt


text:
Support for .pdf not available as answer, rather than only .png (image)

Tried pdf documents as answer, not working, ok, acceptable, just mentioning here.

Imagine those .pdf's as already prepared small .pdf's with only a few sentences in it, so not a big article or so.


text:
Problem: multi scheduling cron-like config with exrm

Cron-like config works fine with exrm when there is only one scheduled job. Ex.:
config :quantum, cron: [
  "* * * * * MyApp.MyModule.my_method"
]

But if we define another one then release for your app can't be generated. Suggested solution is to define named scheduling like this:
config :quantum, cron: [
  news_letter: "* * * * * MyApp.NewsLetter.send",
  weekly_news_letter: "@weekly MyApp.NewsLetter.send",
  stats_gathering: "* * * * * MyApp.Stats.gather",
  daily_stats_gathering: "@daily MyApp.Stats.gather"
]

Or using another form:
config :quantum, cron: [
  news_letter: [
    schedule: "* * * * *",
    task: "MyApp.NewsLetter.send" # maybe {MyApp.NewsLetter, :send} will be supported too
  ]
]

This also may be useful for pausing/deleting jobs using its names.
P.S. This doesn't break any existing config styles and behaviour. Just an option for compatibility with exrm.

I like the idea of named jobs. Given the two alternatives you describe (and I assume there might be more), we should find and then decide for the most practical one.
Could you please describe why exrm cannot generate a release if two or more jobs are defined? Is there an error message or any known limitations? I would like to understand the root cause of the problem first.
Thanks!

Sorry, it looks like config with multi scheduling works now. I forgot that I've recently updated exrm to the latest version but still was sure that it doesn't work properly (I use just one scheduled job). The problem was:
for config
config :quantum, cron: [
  "* * * * * MyApp.MyModule.perform1",
  "* * * * * MyApp.MyModule.perform2"
]

in the final config file rel/my_app/releases/0.0.1/my_app.conf (built with conform) we have the following:
...
quantum.cron = "* * * * * MyApp.MyModule.perform1", "* * * * * MyApp.MyModule.perform2"
...

and exrm crashed while parsing this. Now it works fine but I'll check this out once again.

OK, thanks for the feedback. Please close this issue if confirmed.
We should open another issue for named jobs then.

Unfortunately, I can reproduce the issue. Release was built successfully, but I can't start my app, I got:
** (Protocol.UndefinedError) protocol Enumerable not implemented for <content of my_app.conf>
The problem is here:
...
# Provide documentation for quantum.cron here.
quantum.cron = "* * * * * MyApp.MyModule.perform1", "* * * * * MyApp.MyModule.perform2"

I've created simple application for that: QuantumTest

Thanks! That is very helpful. :+1:
Looks like a problem in conform: https://github.com/bitwalker/conform/issues/20.
Maybe I find a fix or workaround later today.

This should be working fine in conform now (using master). I'll be pushing a new release to hex once I've vetted it a bit.

Confirmed! conform's master branch works fine now (thanks to @bitwalker). So we can close this issue and open new one for named jobs.

@bitwalker thanks for fixing!
@alPacino thanks for confirmation!
So I close this issue.

authors: alPacino bitwalker c-rack

repo: c-rack/quantum-elixir


text:
AiQus routing

Is your feature request related to a problem? Please describe.
At the moment AiQus URL routes are straight under the root path /

/ocbv/*
/static/*
/ocbv
/da
/bl
/sp
/docs
/docs/*
/openapi.json

Describe the solution you'd like
We should rebase AiQus's paths so they're all below the /aiqus base path.
Describe alternatives you've considered
Remove the AiQus deployment from our live instance. The AiQus we have is just a demo one, so we could remove it if no one needs it after the May 2023 review.
Additional context
#235

This will not be an issue, because AIQUS includes the descriptors to set up the routes.


text:
🛑 www.zisk.eu is down

In 4644d74, www.zisk.eu (https://www.zisk.eu/sk/Home.alej) was down:

HTTP code: 403
Response time: 1091 ms

Resolved: www.zisk.eu is back up in c18db2d.


text:
🛑 www.rosler.sk is down

In 1a036a3, www.rosler.sk (https://www.rosler.sk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.rosler.sk is back up in 7504d2c after 48 minutes.


text:
🛑 master.kabernet.sk is down

In 7b86ae6, master.kabernet.sk (https://master.kabernet.sk/) was down:

HTTP code: 503
Response time: 1347 ms

Resolved: master.kabernet.sk is back up in 0f75f94 after 7 minutes.


text:
c3os-agent segfault on RPI4

Here after is the journald log
Feb 03 12:01:47 monitor systemd[1]: c3os-agent.service: Scheduled restart job, restart counter is at 1.
Feb 03 12:01:47 monitor systemd[1]: Stopped c3os agent.
Feb 03 12:01:47 monitor systemd[1]: Started c3os agent.
Feb 03 12:01:47 monitor c3os[3034]: panic: runtime error: invalid memory address or nil pointer dereference
Feb 03 12:01:47 monitor c3os[3034]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0xb83bc4]
Feb 03 12:01:47 monitor c3os[3034]: goroutine 1 [running]:
Feb 03 12:01:47 monitor c3os[3034]: main.agent({0xf9042f, 0x15}, {0x40009018d8, 0x2, 0x2}, 0x0)
Feb 03 12:01:47 monitor c3os[3034]:         /work/cli/agent.go:42 +0x94
Feb 03 12:01:47 monitor c3os[3034]: main.main.func6(0x40002be160)
Feb 03 12:01:47 monitor c3os[3034]:         /work/cli/main.go:165 +0x10c
Feb 03 12:01:47 monitor c3os[3034]: github.com/urfave/cli.HandleAction({0xc4fde0, 0x1195e48}, 0x40002be160)
Feb 03 12:01:47 monitor c3os[3034]:         /go/pkg/mod/github.com/urfave/cli@v1.22.5/app.go:524 +0xfc
Feb 03 12:01:47 monitor c3os[3034]: github.com/urfave/cli.Command.Run({{0xe3b142, 0x5}, {0x0, 0x0}, {0x4000936070, 0x1>
Feb 03 12:01:47 monitor c3os[3034]:         /go/pkg/mod/github.com/urfave/cli@v1.22.5/command.go:173 +0x5fc
Feb 03 12:01:47 monitor c3os[3034]: github.com/urfave/cli.(*App).Run(0x400025a000, {0x40000b2000, 0x2, 0x2})
Feb 03 12:01:47 monitor c3os[3034]:         /go/pkg/mod/github.com/urfave/cli@v1.22.5/app.go:277 +0x618
Feb 03 12:01:47 monitor c3os[3034]: main.main()
Feb 03 12:01:47 monitor c3os[3034]:         /work/cli/main.go:338 +0x1458
Feb 03 12:01:47 monitor systemd[1]: c3os-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 03 12:01:47 monitor systemd[1]: c3os-agent.service: Failed with result 'exit-code'.

Hi! thanks for the feedback, indeed looks like it stops there if there is c3os config found, but it should rather stop.
I will fix this soon, as a heads up if you don't plan to use c3os vpn capabilities you can disable the agent entirely - or otherway a cloud-config must be provided with the c3os network token.

authors: matclab mudler


text:
Let generated models and collections can implement some interfaces

Add two API:

addModelInterface(classname)
addCollectionInterface(classname)

突然想到如果你用 schema 新增了 interfaces ，那 BaseModel 有些 method 也要同時被生產出來，不然會沒辦法滿足 interface

應該可以用 trait 來處理

yeah, you're right

On Jun 24, 2015, at 16:25, Ronmi Ren notifications@github.com wrote:
應該可以用 trait 來處理
—
Reply to this email directly or view it on GitHub https://github.com/c9s/LazyRecord/pull/96#issuecomment-114782409.

coverage 好像沒過
我 rebuild 看看

coverage 應該是因為沒寫 add/getCollectInterface 的測試的關係，我瞧瞧

立馬來 Merge!
對了你是在做 OAuth 相關的東西嗎?


text:
Fix 639

Related to  https://github.com/cBournhonesque/lightyear/issues/639
The problem is that we used to only do entity mapping from the Sender -> Receiver, i.e. the entity map was only present on the receiver. With authority transfer we updated entity mapping, and it can be done both on the sending side or on the receiving side.
Some of our existing logic on the receiver (for example: https://github.com/cBournhonesque/lightyear/blob/1e1cbfadc6fcdcfca61a7b6cf091e24ceaf4a0ba/lightyear/src/shared/replication/receive.rs#L196) still work under the expectation that the entity map only exists on the receiver. (and that every local entity is present in the entity map. This is not the case anymore, which is why this function fails (https://github.com/cBournhonesque/lightyear/blob/1e1cbfadc6fcdcfca61a7b6cf091e24ceaf4a0ba/lightyear/src/client/interpolation/spawn.rs#L39).
https://github.com/cBournhonesque/lightyear/blob/1e1cbfadc6fcdcfca61a7b6cf091e24ceaf4a0ba/lightyear/src/shared/replication/receive.rs#L177
Potential solutions:

include the received tick in Replicated so that ALL entities have it (not just the ones with prediction/interp). Could work but maybe inefficient?
In general using the ChannelReceiver to get the confirmed tick seems very 'flimsy'. Maybe use something else?
Fix the code paths that still expect all entities to be present in the entity map

This PR currently has a unit test but no fix

I'm merging this because it provides some useful changes:

change some data that depends on remote_entities to instead depend on local_entities -> this is important because in some cases we might not know about the remote entities.

I tried to implement a change where when you change replication from c1 to s or c2, then we potentially send a ShouldBeInterpolated or ShouldBePredicted to c1. Unfortunately it doesn't work because c1 doesn't accept it since it hasn't received yet the message that it doesn't have authority anymore.. In general this was a bit of a hack, so i'll keep thinking of better ways to handle Prediction/Interpolation.

@philpax in the meantime, is it possible for you to always start spawning entities on the server, instead of on clients? That would make things simpler, and I suspect that interpolation/prediction won't panic

I haven't been able to work on the project that I originally needed this for, so I can't test this change exactly.
However, I've been working on another project using Lightyear, also using client replication, and I've had to revert this change on my local branch because I'm being spammed with log errors that look like this:
2024-10-02T21:53:19.660639Z ERROR lightyear::shared::replication::receive: updating confirmed tick for entity remote_tick=Tick(8305) local_entity=Entity { index: 112, generation: 1 }
2024-10-02T21:53:19.677335Z ERROR lightyear::shared::replication::receive: updating confirmed tick for entity remote_tick=Tick(8307) local_entity=Entity { index: 112, generation: 1 }
2024-10-02T21:53:19.760975Z ERROR lightyear::shared::replication::receive: updating confirmed tick for entity remote_tick=Tick(8315) local_entity=Entity { index: 112, generation: 1 }
2024-10-02T21:53:19.777760Z ERROR lightyear::shared::replication::receive: updating confirmed tick for entity remote_tick=Tick(8317) local_entity=Entity { index: 112, generation: 1 }

No interpolation or prediction, just replicating a single entity from the client. The errors occur on both the server and receiving clients.

@philpax in the meantime, is it possible for you to always start spawning entities on the server, instead of on clients? That would make things simpler, and I suspect that interpolation/prediction won't panic

This is a bit difficult for the project that this was originally for, but not impossible. For now, I'm content operating without interaction/prediction, but I'll revisit that at a later stage.

Ah sorry about that; I just removed the extra logs (in main)

authors: cBournhonesque philpax

repo: cBournhonesque/lightyear


text:
Stream Sharing

It would be nice if you added the ability to split an incoming stream to multiple clients. xTeVe does this. Here is an example.
You pull in one stream from Fox News then 5 TVs in your home can all watch Fox News at the same time. So you are only pulling 1 copy of the stream, not 5.
Also xTeVe will send a video image to clients if there are no more "tuners" available so they don't just get weird errors because there are no more tuners available. Instead on the client they see a screen saying "Sorry. There are no more free tuners available for this channel. Please try this channel later."
I personally think the xTeVe web interface stinks and it has not been updated in over a  year.

This seems like a great idea, but has a few gotchas that need to be worked through.  Thought I would lay out some thoughts on the topic.
Good news is that there is a separate process per stream and a single multi-threaded process containing all client requests, so we can tie multiple client threads to a single stream process, fairly easily.
It would help with providers that do not like multiple connections from a single IP.
Also, a good thing would be the stupid kodi pvr-tvh app that disconnects and reconnects every time there is a 10 second delay between incoming stream segments.  It would basically keep feeding the segments to the new client; although, how we restart the second client stream could easily cause some deja vu replaying of segments when buffered or missing segments, if not buffering.
Also, we need to address the VOD channels.  These provide the entire movie at one time to the client.  Should we in this case start a separate provider stream to start the movie from the beginning, or start at some point in the middle based on the current client connection.  My thought currently is to use separate process streams.
The biggest issues is the operating system forking errors. There is an operating system condition with python that the new forked process does not establish communication pipes like it should.  Right now, when the pipes fail to establish, the stream process is terminated and restarted.  Then, it is checked again to see if the pipe has formed correctly.  This actually happens quite often.
So, in summary, we need to:

Determine how to handle the startup of the second stream associated with buffering.  We could just send the current stream (no buffering), which for the pvr-tvh issue would lose at least one segment. Or, we could send what we have currently for backup and that would give the stream some buffering, which for pvr-tvh would cause a deja vu condition.
Determine how to handle VOD.  VOD is special case, in that, the entire movie is provided at the start and normally it is the client that squelches the data rate (not Cabernet).  If we use the same provider process, it would make sense to not start at the beginning (which may not be what is expected). Or, provide a new stream process for each VOD and do not mux the stream together.  That way the streams would all play from the beginning.
Determine how to handle the case when a forked process fails to start correctly and the pipes between processes do not work.  Currently the process is terminated, but if multiple clients are connected to the process, then it does not make sense to restart the process.

As for sending video back to the client, there are two groups on that. One is to terminate the connection when too many tuners are in use.  The other is to send something that makes it looks like a tuner is available to the media server.  We are currently doing what TVH does, which make it consistent with our logical processes.  That means we termination of the connection when too many connections are in use.  This helps a ton when starting a recording and some of the tuners just need to timeout.  TVH will go through a timeout and then retry the connection to see if the connection will work.  This also works great when the provider is giving connection refused and needs to go through a timeout before it will work correctly.  I do not see any advantage for displaying a video on the screen, considering all the negatives.

Plan is to implement during the 0.9.12 updates.

Too many changes for 0.9.12, moving to start of 0.9.13

Fixed in 0.9.31.01

repo: cabernetwork/cabernet


text:
Error in RSS/Atom feed when setting app_locale to de

I'm getting an Undefined offset error in src/Models/Incident.php line 118 when setting the default language to 'de'. Perhaps some translation strings missing?

Translations should fall back to en if they're missing. I'll take a look.

Fixed :)

you're fast ..

authors: jbrooksuk maltorfer

repo: cachethq/Cachet


text:
Update to elixir 3.3.1, removed unused elixir.json format bower.json

@jbrooksuk This enables browsersync for us :)

@joecohens Could you get this sorted on StyleCI/StyleCI too please?

@GrahamCampbell Sure!

authors: GrahamCampbell joecohens


text:
clarification on the safety requirement for the Locker interface

What is your question?
re: https://github.com/caddyserver/certmagic/blob/master/storage.go#L75
How is the Lock used for the purpose of certmagic? Is it used to save on redundant work (e.g. it is ok to try to renew a certificate a second time), or to guarantee correctness (e.g. absolutely no one else is able to update the certificate other than me otherwise the world catches on fire).
While the comment hints to me that it is the former, it is not at all clear to me that if certmagic relies on the correctness of the locking property.
For context, I'm trying to integrate certmagic in a personal project with an abstract KV interface. While the rest of the Storage interface is straightforward, I'm unsure about the guarantee that Locker provides (hence, expectations of the underlying implementation).

This is potentially related to #58

Locker is not an optional interface, if that's what you're asking :slightly_smiling_face:
An improper implementation may cause ACME challenges to fail because two instances are presenting different credentials for the same domain at the same time. Or two instances will successfully fail to share or coordinate the certificate they obtained, resulting in rate limit overages. It's also using for distributed STEK coordination, so if locking is not properly implemented, clients' TLS sessions will end and performance will decrease.
The underlying storage mechanism must support atomic operations (for example, S3 does not).
Does that help?

I understand that Locker is not optional 😂
Let me just give an example for better explaining. Suppose that the Locker interface is implemented using Cloudflare's Workers storage offerings, either KV or Durable Objects, the requirement by certmagic of its Locker implementation may change which storage solution one chooses.
KV (https://developers.cloudflare.com/workers/learning/how-kv-works/):

Write a fresh key in SFO
Reading of the said same key will have the value immediately (no matter if you are reading from SFO, DFW, or FRA)
However,
Write a fresh key in SFO
Read the said key in another region
Write to the same key again with a different value in SFO
Now all bets are off. You can read old value, or new value, but eventually you see the new value

Durable Objects (https://developers.cloudflare.com/workers/learning/using-durable-objects/):
Provides serializable transaction on the said key, which is "atomic" in that sense
What is not clear to me is that,

once certmagic invokes Lock(key), does the storage implementation need to guarantee Get(key) by non-lock holders will not see the Store(key) by the lock holder, until Unlock(key) is called (like BeginTX and CommitTx)?
The underlying storage mechanism must support atomic operations (for example, S3 does not) I assume that it applies to Locker, but what about the surrounding Storage operations? Do you need to immediately Read-Your-Writes (Get/Store)? Or you can get more relaxed with Get/Store while providing stronger guarantee to Lock/Unlock?

Ah I see, good questions.

once certmagic invokes Lock(key), does the storage implementation need to guarantee Get(key) by non-lock holders will not see the Store(key) by the lock holder, until Unlock(key) is called (like BeginTX and CommitTx)?

If I understand you right, it sounds like you are asking about Lock/Unlock being used to guard or synchronize Load/Store/etc.
Load/Store/etc should be blocking and synchronous on their own; meaning that when Store() returns, all future calls to Load() for a key should return the last value stored for that key.
Based on what you described about Cloudflare KV, it sounds like this would require waiting for propagation or something like that, before returning from an implementation of Store(). Because yeah, you wouldn't want future calls to Load() to return a previous value.
Lock and Unlock, though, are a little different. Think of them just like sync.Mutex. If CertMagic (or another importer of the code) wanted to sync a critical section, it would call Lock() to start, then Unlock() when it's done.

The underlying storage mechanism must support atomic operations (for example, S3 does not) I assume that it applies to Locker, but what about the surrounding Storage operations? Do you need to immediately Read-Your-Writes (Get/Store)? Or you can get more relaxed with Get/Store while providing stronger guarantee to Lock/Unlock?

So yes, callers should be able to immediately read their writes. Lock/Unlock are not expected to be used around synchronous calls to Load/Store.

Thank you, just gotta make sure about the requirement of the Storage interface, because you know, as if implementing a distributed counter is easy 😂
related: https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

Can we assume that if CertMagic calls Lock(abc), it is guarding mutual exclusion against Store(abc)? Asking because I want the implementation protect again expired lock because of arbitrary delay in network.
You can imagine that once it calls Lock(abc), the Store must also provides a token to ensure that it is still holding an up-to-date lock.

Can we assume that if CertMagic calls Lock(abc), it is guarding mutual exclusion against Store(abc)?

No; locks are basically named mutexes, they have nothing to do with individual files/keys. Usually a lock name represents a specific/unique operation or job that is being performed.
The storage implementation should do its own sync for file reads/writes. For example, it should block calls to Load() while Store() is happening for the same key/filename. (I believe standard system disk file systems do this sync for us, like those we use in calls to os.Open(). Databases also commonly do this as well.)
Think of Lock/Unlock as on a different level from the sync needed to do Store/Load. With Lock/Unlock, you are providing a mutex as a service to the caller, regardless of whatever other methods are happening. With Store/Load, the caller doesn't know or care about the mutexing, they just expect that to immediately be able to Load() what was Store()'ed. They should be able to call Load/Store synchronously without corruption.

authors: mholt zllovesuki

repo: caddyserver/certmagic


text:
upstream configuration of socks5 (cloudflaer warp socks5)

In the past, the upstream upstream configuration of socks5 (cloudflaer warp socks5) could proxy normally, but after warp-svc reached version 2024.6.497, it could not proxy normally.

Forward proxy stops working after WARP service upgrade to 2024.9.346.0
Previously, with this configuration:
route {
forward_proxy {
basic_auth user1 0NtCL2JPJBgPPMmlPcJ
ports     80 443
hide_ip
hide_via
probe_resistance secret-link-kWWL9Q.com
upstream socks5://127.0.0.1:40000
}
file_server
}
After upgrading WARP service to version 2024.9.346.0, the proxy stopped working. The WARP socks service is still running on port 40000.

It's not a forwardproxy problem it's a warp-svc version problem.https://community.cloudflare.com/t/cloudflare-warp-version-2024-9-346-0-proxy-mode-issue/720751/28

repo: caddyserver/forwardproxy


text:
How to use nnpack accelerate? Can I select MKL ?

Hello, I am a new user of caffe2, and I got a lot of problems.
When I use caffe framework, I can choose MKL or OpenBlas to accelerate my net. And I can use "export MKL_NUM_THREADS" to assign threads num. Now I don't know how to use nnpack and how to choose mkl.
I have run a model transferred from caffe, I got this warning :
W0803 10:48:50.294745 26961 conv_pool_op_base.h:554] You are hitting a case where Caffe's legacy padding calculation is hit. This leads to inefficient and sometimes incorrect results. We are keeping this behavior for backward compatibility, but you are strongly recommended to move away from it.
And caffe2 is slower than caffe, this is my test result:
caffe MKL use 4 threads :63.7196612358   caffe2 NNPACK : 81.6432404518
Could anyone know how to solve those problems, thank you very much !

To build with MKL - cmake .. -DBLAS="MKL"

-DBLAS="MKL" is the right way to go.
For NNPACK, you can set the engine of the operators to "NNPACK" and it should be able to use the nnpack ops then.

authors: QiYueFeiXue Yangqing deepali-c


text:
Calling operators within an operator

Hi
Is there a way to call other "operators" from within the implementation of a new operator?
Thanks.

Only very hacky ways. This is not recommended usage :)
What are you trying to do?

I am trying to implement a custom C++ operator for something similar to Yolo's last detection layer, and it has inside it softmax, sigmoid, exp, and other operators on slices of the input. So I was thinking one way would be to slice the input, and pass them to already-implemented operators.
So I guess a better question: what is the recommended way to "compose" operators in C++ to form a new custom operator?

@mohamedadaly I would recommend doing just that. Slice the input and run the ops you need against the different chunks. As long as you use the DAGNet executor and have enough threads, the ops will run in parallel.

And sure, you can implement this as a single op and then dispatch from there, but then you're effectively replicating what Caffe2 can already do for you through the DAGNet executor.

authors: mohamedadaly pietern


text:
chore(*): cherrypick release-1.2 optimization and bug fixes…

… to release-1.1 (#47)

feat(*): enable filebeat statistic API (#24)

higher resource limit (#32)

(cherry picked from commit d17d4bbd97ecd00db98d24a53515e2edc305d449)

Update Filebeat version to 6.5.4 for upstream bug fix (#36)

bump filebeat verson to 6.5.4

improve Makefile

(cherry picked from commit eecbb3a34cbba7a12bb2f919b04402c964bde2d3)

fix(*): monitor subprocess status (#43)

refactor subprocess start and stop

refactor watch /config/filebeat-output.yml

fix bug

fix bug

(cherry picked from commit cae2680f823a1c6920b621b4a56b17e3711d9a5e)

chore(*): add mount propagation (#45)

(cherry picked from commit f0b561a568f6cae135fc4581f297e15239771c1b)

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @lichuan0620

Release note:

NONE

/hold wait for test

/close

repo: caicloud/log-pilot


text:
Use babel to compile ES2015

Since 2.2.0, this module is no longer compatible with non-latest versions of Node and most browsers.
It'd be great to use Babel to compile ES2015 before publishing on NPM.
Here is one of my repository doing it (https://github.com/GitbookIO/node-gitbook-api), you can setup the same config with .babelrc, .npmignore and the prepublish in package.json.

Indeed.
Considering as a bug and will apply Babel before publishing.

yep! I can confirm this as a bug.

As discussed on this PR
We can't use Babel, since it will make the code slower.
I removed all fancy ES2015+ from the code and it should run on every ES5 environment.
Let me know if you find more bugs.

Without babel compilation I get this error:
Uncaught ReferenceError: cacheDefault is not defined

@ankerek Sorry for that, I forgot to remove one const
Can you retry?

New version published https://www.npmjs.com/package/fast-memoize

Works fine now. Thanks

You're welcome.
Sorry for the mess.

authors: SamyPesse ankerek caiogondim sebas5384


text:
Use dotnet-sonarscanner package for dotnet core

You might use the dotnet-sonarscanner package for dotnet core instead of your own MSBuild.SonarQube.Runner.Tool.
The advantage would be to get updates faster (direct from vendor) instead of waiting for community contributions.

@twenzel I took a quick look into the implementation and noticed CORECLR_TOOL_NAME. You can simply add the dotnet-sonarscanner from SonarSource to your Cake build and set UseCoreClr to true. This will use the dotnet tool.
#tool nuget:?package=dotnet-sonarscanner&version=5.0.4

var sonarBeginSettings = new SonarBeginSettings();
sonarBeginSettings.UseCoreClr = true;
// Your configuration.

Unfortunately this does not use the dotnet tool.
We're launching for CoreCLR with executable C:/Agents/smith04.01/_work/79/s/tools/MSBuild.SonarQube.Runner.Tool.4.8.0/tools/sonar-scanner-msbuild-4.8.0.12008-netcoreapp3.0/SonarScanner.MSBuild.dll

I'm pretty sure it does. I use it in a couple of builds e. g. here. Did you add the package to Cake? This is my task.

@HofmeisterAn You were right. The problem was, that I also had referenced the old MSBuild.SonarQube.Runner.Tool.
Now it's working fine, thanks,

authors: HofmeisterAn twenzel


text:
🛑 XMR Asia Servers is down

In 66422db, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 73dc397 after 34 minutes.

repo: cake-tech/upptime-cakewallet


text:
🛑 XMR USA Servers is down

In e660d02, XMR USA Servers ($XMR_USA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR USA Servers is back up in e7b89e2 after 7 minutes.


text:
Updated to allow arrays - Update

Changes to include test cases and code coverage compliancy from previous pull request #6.

@dcodadigital,
I see you had a lot of work on your code. Can you please provide me some explanation with code examples? What should your code do? Some pieces don't look very clean, however, appreciate your work ;)
Bob

@dcodadigital I added some comments. I really appreciate your work, but I really want it to be clean and the best, so I'm very strict in PR's. You've learned a lot, so go on! :)

@bobmulder I appreciate all your comments and thank you for taking the time to do that. As you may be able to tell I am new to github and code collaboration in general so even if this is not merged I have learnt a ton since last week. So thanks for being patient with me. :)
To explain what I was after achieving (I will submit inline comments after and make any updates if it's worth while for you) is I am using this on a project as a settings registry which it is perfect for that very reason and the only enhancement I needed for it to work with project was to be able insert and read arrays as well as insert into arrays in the same way Configure:: does for example:-
Configure::write('foo.firstname','Bob');
Configure::write('foo.lastname','Mulder');

Which when read
$foo = Configure::read('foo');

Which would give me both values in an array which is useful for me. So I was trying to apply the same idea in the same way so the following would be stored as 2 records with the arrays serialized as the value IE:-
Setting::write('foo.firstname','Bob');
Setting::write('foo.lastname','Mulder');

I also might need to fetch them individually as well which can be done by:-
Setting::read('foo.firstname');

Hope that makes sense and sorry this post has turned into a Charles Dickens novel.

Hi @dcodadigital,
I like you think you are as good as Charles Dickens ;)

so even if this is not merged I have learnt a ton since last week. So thanks for being patient with me. :)

I've had that period as well (not a long time ago), so I completely agree by learning tons in a week and getting very much feedback ;)
I like your feature, and I think it should be added to the plugin, however it doesn't fit completely because of the naming that the plugin uses at the moment. At the moment this standard is used: PluginOrPrefix.SettingName. In your example you approach the Settings like the Configure class of CakePHP itself and I have to be honest, I think thats the right solution. So I agree by changing code to allow nested stuff / array's.
Next question is, does it fit in the current code or do we need to transform our whole structure and schema's to work with nested stuff?
A possible approach could be:
// writing this
Setting::write('foo.bar.firstname', 'Bob');
Setting::write('foo.bar.lastname', 'Mulder');
// should be saved in the table as

name
value

foo.bar.firstname
Bob

foo.bar.lastname
Mulder

When you want to get data:
Setting::read('foo.bar.firstname');
// should return:
Bob
Setting::read('foo.bar');
// should return:
[
    'firstname' => 'Bob',
    'lastname' => 'Mulder'
]

Would like to hear what you think about this! I would like to have a chat with you! (https://gitter.im/bobmulder).

Hi Bob

I like you think you are as good as Charles Dickens ;)

If only! :+1: :-)

I've had that period as well (not a long time ago), so I completely agree by learning tons in a week and getting very much feedback ;)

I bet your thinking the same as me then why we did not go through the process even sooner. I've always just downloaded stuff of github and never really understood the collaboration aspect and how useful it is as to setting code standards and I think now it is a hurdle everyone should look to jump over.

Next question is, does it fit in the current code or do we need to transform our whole structure and schema's to work with nested stuff?

That is a good question I realize storing seralized arrays may not be the cleanest approach? The only advantage I can see of the serialized aspect from your examples which is a lot cleaner to the way that I approached it is if you need to have complex nested arrays as well as inter nesting arrays which would potentially require a lot of loops to separate them out by keys into the database? For me I am using a component which the app I am working on requires nested arrays for posttypes and taxonomies (shown at the bottom) which inter nest into one final array giving the posttypes and taxonomies for the project. So I think maybe mine is probably more of an isolated case use I'm not sure. What do you think?

May I ask you where you are working on? It looks like you are building a cms/admin-panel for Cake?
For your solution I would suggest the following: Just save your 'array' as string (json-encoded?) as setting. When you need data you get the string, decode it and its free to use. I think that's for you now the cleanest solution. If you want I can provide you an example.
On the other side, don't forget the settings plugin is only for storing small settings, not replacing stuff that should be an apart table! ;) I can imagine that you would like to store posttypes in an apart table and using a meta-table to store optional data (wich I am working on, so contact me for that progress).
About the general purpose, because settings are loaded every 'request' we have to be carefull by the amount of queries called. Note that complex queries (when you got a large application) will slow your application. So, that's why I chose for this strategy. We have to think about the main strategy: currently PluginOrPrefix.Name, why should we replace that? Only to allow nested stuff (like foo.bar.firstname)? We could easily implement a functionality to store and get arrays (so, getting foo.bar, but not foo.bar.firstname). What do you think about that?
I would like to have a chat with you! (https://gitter.im/bobmulder).

authors: bobmulder dcodadigital

repo: cakemanager/cakephp-settings


text:
Fixed Bug #596, #123 - changeColumn resets the nullable option if not specified

Fetching column options before performing changeColumn Action

Whats the bugfix status here?

authors: dereuromark saitejaprasadam

repo: cakephp/phinx


text:
Enhancement: Pipes That Don't Connect to Inventories

It would be very cool if a pipe was available that does not connect to inventories, but connects to other pipes, like the BuildCraft sandstone pipe, or a wrench that could remove connections to an inventory.
For example, I could craft any pipe together with some sand, which would give me a version of that pipe that would not connect to inventories.

Noted, thanks for the suggestion!

Rigid pipes have been added as of v1.1.0

authors: JoshMayberry cakewhip

repo: cakewhip/ezpas


text:
Featured work default state

Feature Name: Featured work default state
Feature Description:

If an artist's current feature work is deleted, a new one from his existing works (if any) will be assigned to be the new featured work
Previously deleteWork does not update the state of the ArtistProfile – added a line to update the state. Not sure if necessary / intentionally left out.

Related PRs
None.
Migrations
None.
Tests Performed, Edge Cases
Tested on all artists.
Screenshots
CC: @by-co

Thanks for the comments + suggestions- have reflected them in latest commit!

repo: calblueprint/SFAI


text:
[Table] Allow displaying checkbox on specific rows

With the current implementation, you can either display checkboxes on all TableRows or not. I currently have a table that contains different sections:

Meaning that mi section header TableRow only contains the title of the section, and the following rows contain items that the user can select.
It would be nice if I could display the checkboxes only in the rows that contain items and not in the section headers (which are another TableRow).
Is there a way to achieve this?

@tonyjmnz https://github.com/callemall/material-ui/blob/master/CONTRIBUTING.md#asking-questions
This isn't possible right now, but I wonder if this might help: https://github.com/callemall/material-ui/pull/3663

Thanks, and sorry about posting my question here.
That would do the trick. Unfortunately it isn't merged yet.

authors: mbrookes tonyjmnz

repo: callemall/material-ui


text:
Fixes #2522 SVGIcon incompatibility with bootstrap

Fixes a bug that makes icons in IconMenus partially invisible when bootstrap CSS is included.
Idea courtesy of "Francois Bissonnette" on #2522 who later deleted his comment.

Does this bug only affect svg-icons? aren't font-icons affected? @oliviertassinari What do you think?

@thomasantony Could you have a look at https://github.com/callemall/material-ui/pull/2525. I'm not a huge fan of adding style to fix an external dependency.

@cgwyllie Please take a look and see if #2633 fixes it.

authors: oliviertassinari subjectix thomasantony


text:
Headers

fix for #25

ac197b0d5d228543fbda6d47daa26f9bc2ef2d4d

repo: calvinmetcalf/leaflet-ajax


text:
fix wrong fbit config during tests

Fix invalid pipeline config used during tests.

Uhhh, nice. We got a panic https://github.com/calyptia/api/runs/7961711404?check_suite_focus=true#step:7:172

repo: calyptia/api


text:
Patch of documentation to address #267 (lack of statusInfo in SessionInfo)

What type of PR is this?
Add one of the following kinds:

correction
documentation

What this PR does / why we need it:
Clarifying that only the qosStatus can be polled, but not the statusInfo which is provided only within EventQosStatusChanged
Which issue(s) this PR fixes:
This documentation patch does not fix the issue #267 finally.
Special notes for reviewers:
While creating this PR, I'm not any more sure that we should fix the issue in this way, even short-term. Instead there is the option to create a patch release v0.10.1 which adds the statusInfo also to SessionInfo.
Left the version number open for discussion.
Changelog input
 release-note

Additional documentation
This section can be blank.
docs

@RandyLevensalor @eric-murray Would you do your final review ... I will prepare the patch release as soon this is merged.

repo: camaraproject/QualityOnDemand


text:
add all files in bsvpath to abspaths for path lookup

This fixes issues where a bsv file may include a file with a different suffix (like .defines)

Looks good to me.

repo: cambridgehackers/connectal


text:
styles not working for collapsible

hello, i am trying to implement this module, but seems that not working
<CardStack
 height={this.state.trucksAvailable.length * 100}
 width={400}
 background="#f8f8f8">
 {
        this.state.trucksAvailable.map(truck => {
        return (
         <Card
          key={truck}
          background={this.generateColor()} >
          <TeamMemberCard {...truck} />
           </Card>
  )})}
</CardStack>

const TeamMemberCard = (props) => (

{props.Vendor_str}

{props.VendorName_str}

            <DetailsRow
                title={props.TruckType}
            />

            <DetailsRow
                title={props.Weight_Capacity}
            />

            <DetailsRow
                title={props.Fei_str}
            />

);

const DetailsRow = ({ title }) => {
    return (

                    {title}

    );
};

but seems that the each child have same height than CardStack, it do that all card is in overlapping or so i think

Hey @mealbarracin10, thanks for the issue! Sorry about the extremely delayed response, I haven't been actively maintaining this repo. Out of curiosity, were you able to resolve the issue?

repo: cameronbourke/react-cardstack


text:
README: Improve formatting by removing unneeded indent.

This is an optional stylistic improvement to the README formatting, please see if you like it and feel free to merge.

Since a fenced code block (three backticks) is already used, there's no need to indent code blocks. Either a fenced code block or an indent alone is enough.
Also use tabs instead of spaces in Go code to make it gofmt-compatible, and use Go syntax highlighting for Go code blocks.
Unlike 1e1ffecf4f148c30fb214feeb491c7de5fe54e56, only use Go syntax highlighting for complete Go code block, since GitHub renders it poorly for partial Go code.

Thanks!

authors: campoy shurcooL

repo: campoy/jsonenums


text:
Abstract provider detection

Mount the volume in a container to detect which provider to use.
Depends on #146.

LGTM

authors: cryptobioz mcanevet

repo: camptocamp/conplicity


text:
DefaultWaitTimeProvider has a min wait time of 30s

https://github.com/camunda-community-hub/zeebe-client-csharp/blob/bfc0fbca7b177e9fd3816e8da37bdbce108cebf5/Client/ZeebeClient.cs#L37-L38
The Math.Max should be Math.Min.

Great catch @csleead thanks for reporting I will create a new release with the fix

authors: Zelldon csleead


text:
Keep applicable properties during morph

This applies especial to technical meta-data such as ids and listeners.
We cannot simply copy everything, i.e. need to remove user task related extensions when changing to service task.
See forum thread, bpmn-io/bpmn-js/issues/415.

Closed in favor of https://github.com/camunda/camunda-modeler/issues/370.

repo: camunda/camunda-modeler


text:
Implement Basic Linting UI

[ ] display information about linting errors and warnings (e.g. number of linting errors) in status bar
[ ] display detailed information about linting errors and warnings in dedicated UI (similar to existing log)

Depends on https://github.com/camunda/camunda-modeler/issues/2326
Child of https://github.com/camunda/camunda-modeler/issues/2323

Sketch