Fix broken install on darwin

While following the Quickstart on a 2018 MacBook Pro, after running
scripts/install.sh

I've got the following exception
./src/storage.zig:189:18: error: expected type 'io.darwin.ReadError', found 'error{ConnectionTimedOut}'
            error.ConnectionTimedOut,
                 ^
./zig/lib/std/os.zig:521:5: note: 'error.ConnectionTimedOut' not a member of destination error set
    ConnectionTimedOut,
    ^
tigerbeetle...The following command exited with error code 1:
./tigerbeetle/zig/zig build-exe ./tigerbeetle/src/main.zig -OReleaseSafe --cache-dir ./tigerbeetle/zig-cache --global-cache-dir ~/.cache/zig --name tigerbeetle -target native-native -mcpu x86_64 --enable-cache
error: the following build command failed with exit code 1:
./tigerbeetle/zig-cache/o/9a26526d85723d3f56f183ce39ae0ead/build ./tigerbeetle/zig/zig ./tigerbeetle ./tigerbeetle/zig-cache ~/.cache/zig -Dcpu=baseline -Drelease-safe

I've just started looking at zig this week so forgive me if I'm miss-interpreting the error or missing something with the fix on this PR.

Thanks @bermi — we ran into this in parallel yesterday and a partial fix was done in https://github.com/coilhq/tigerbeetle/commit/800a600f178bc15fcd43d9f2470778fa579720d0
Would you please rebase? I think that'll leave just one switch prong in your PR which we still need.
cc @kprotty

@jorangreef rebased! Thanks for building tigerbeetle!


feat(company wallet): add revoke credential

Description
add revoke credential feature

Revoke Icon Addition
Tooltip on Hover
Confirmation Overlay
Success/Error Handling

Why
new feature
Issue
#767
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

dependent on https://github.com/eclipse-tractusx/ssi-credential-issuer/pull/149


Background logic change:  Log exception and continue further processing

Currently, when executing the background logic if a repo processing fails, it raises an exception and aborts the further processing.
This change will log the error, in case of an exception, and continue processing with next repository. It fixes issue_4527

Unit testing output

thanks 👍
welcome to abapGit as a contributor 🎉

Thank you.


What is a SubType Group

"To define the rows and columns of fields, you add SubType Group controls to the Group control".
Can you please explain how one would add a SubType Group to a Group Control.  The only SubTypes listed in the Designer are Group, Repeater, CueGroup, FixedLayout, and GridLayout. "Add a Subtype Group" implies that a SubType Group is a type of Group. But there does not appear to be such a type of Group.

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

ID: 10104440-fe72-0332-8908-859377294d6c
Version Independent ID: 8668d4e8-ccc3-577b-73d0-726f2b99eaac
Content: Layout Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-layout-property.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Hello, thanks for the feedback. I agree, with your assessment. There is no Subtype group. The paragraph has been rewritten and an update published soon.


Optionally include additional metadata with nwis_client get requests

This PR adds an include_expanded_metadata switch to nwis_client.iv.IVDataService.get. This is a boolean switch that adds the following columns to the resulting dataframe: ['siteName', 'srs', 'latitude', 'longitude', 'siteTypeCd', 'hucCd', 'countyCd', 'stateCd']. These data were always present in the raw json, but were previously ignored. This addition should benefit any geospatial applications.
Additions

New include_expanded_metadata parameter. Default is set to False.

Removals

Removed infer_datetime option per pandas``UserWarning from datetime conversions.

Changes

No change in overall behavior.

Testing

Added two new tests for get_raw and get using the new parameter.

Notes

Todos

Checklist

[x] PR has an informative and human-readable title
[x] PR is well outlined and documented. See #12 for an example
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (see CONTRIBUTING.md)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output) using numpy docstring formatting
[ ] Placeholder code is flagged / future todos are captured in comments
[x] Reviewers requested with the Reviewers tool :arrow_right:

Appears 3.7 error is unrelated.

Agreed and updated column names.

Deployed:
https://pypi.org/project/hydrotools.nwis-client/3.3.1/


fix(cve): support-bundle

https://github.com/longhorn/longhorn/issues/7152

@mergify backport v1.5.x v1.4.x


Localsend prevents a computer/screen from going to sleep

Describe the bug
I'm working on a MacBook connected to a power adapter.
With Localsend running - even idle, i.e. with no transfer in progress - neither my displays nor a computer itself go to sleep.
The problem disappears after the app is quit.
FWIW, Wake for network access OS option is set to Only on Power Adapter.
To reproduce
That's tricky.

Open the app.
Observe your computer stay awake.

I don't know if it's possible, but maybe LocalSend can make use of a Wake for network access capability in OS and - if the app has a Quick save option enabled - automatically accept transfers even while sleeping.
Screenshots
No response
Desktop (please complete the following information)

OS: MacOS 14.5 (23F79)
LocalSend version: 1.14.0 (45)

Smartphone (please complete the following information)
No response
Additional context
No response

This is probably a duplicate of #1723: Localsend acquires a suspend lock while doing transfers and never releases it until you press the "done" button. That bug mentions that setting "autocomplete" in the receive setting (even if the bug happens when sending) makes the program auto press the Done button and release the lock (FWIW that option is not present on my old Localsend version 1.10.0 (32)
It's easy to repro on Windows 10 with Localsend 1.10.0 (32): send a file and don't press on the "done" button, you can then run as administrator "powercfg /requests" and observe
C:\Windows\System32>powercfg /requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume3\Program Files\Localsend\localsend_app.exe
...

Looks like the api for acquiring that lock is SetThreadExecutionState

Well spotted @antoniotejada - just noted this too.  I'd recorded it as a bug for PowerToys Awake at https://github.com/microsoft/PowerToys/issues/36294 but then ran a powercfg /requests in Windows Command Prompt and noted the same:
DISPLAY:
[PROCESS] \Device\HarddiskVolume4\Program Files\LocalSend\localsend_app.exe

SYSTEM:
[PROCESS] \Device\HarddiskVolume4\Program Files\PowerToys\PowerToys.Awake.exe

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

I have auto-accept transfers enabled.


Support for Python SDKs

Similar to how we support the JDK and Go, it might be good to add native support for Python now that we have stable packages for it.

Happy Hermit user here -- I just ran into this too. I'd like to learn more about IntelliJ plugin development -- is this something I could reasonable do in a day or two?

@Ubehebe All contributions would be highly appreciated! 😄
I think it should be doable in a couple of days. Every language plugin in IntelliJ seems to handle their SDKs slightly differently, so you would have to see how the Python plugin manages its SDKs. But once that is done, you should be able to use our GoSDK and JDK updates as a template to add it to the plugin.
Basically, you will need a conditional config block like this: https://github.com/cashapp/hermit-ij-plugin/blob/main/src/main/resources/META-INF/plugin.xml#L52 That only gets loaded if the python plugin is present, and then you can add a Python specific handler to Hermit property changes like this: https://github.com/cashapp/hermit-ij-plugin/blob/main/src/main/resources/META-INF/goland.xml#L7
Happy to help if you have any questions!


Fix comment and post downvotes

Bug:
We get true, false, and null back from the api to represent upvote,
downvote, and no vote respectively. Currently the code is trying to
coerce false to -1. This doesn't work since it actually gets coerced to
0. So downvotes from the api were not being represented in the ui.
Fix:
Use a switch statement to normalize the api values to 1, 0, and -1. Also
name the validator likes since this is a super specific validator.
Additional changes:
There was an additional potential bug from a recent patch. Since the
api can return falsey values, we don't want to check for falseyness as
a way to determine if we need the fallback value. Although this happens
to work out currently, its ambiguity is probably dangerous.
The fix for this is to check explicitly for undefined since this
implies a missing key. Any other value value means it was explicitly set.
:eyeglasses: @schwers

:fish:


thrift.transport.TTransport.TTransportException: TSocket read 0 bytes

I'm trying to connect to hive using python. I tried using both pyhive and pyhs2 but it gives the following error.
Traceback (most recent call last):
File "hello.py", line 8, in
database='hello') as conn:
File "/usr/local/lib/python2.7/dist-packages/pyhs2/init.py", line 7, in connect
return Connection(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pyhs2/connections.py", line 47, in init
res = self.client.OpenSession(TOpenSessionReq(username=user, password=password, configuration=configuration))
File "/usr/local/lib/python2.7/dist-packages/pyhs2/TCLIService/TCLIService.py", line 154, in OpenSession
return self.recv_OpenSession()
File "/usr/local/lib/python2.7/dist-packages/pyhs2/TCLIService/TCLIService.py", line 165, in recv_OpenSession
(fname, mtype, rseqid) = self._iprot.readMessageBegin()
File "build/bdist.linux-x86_64/egg/thrift/protocol/TBinaryProtocol.py", line 148, in readMessageBegin
File "build/bdist.linux-x86_64/egg/thrift/transport/TTransport.py", line 60, in readAll
File "build/bdist.linux-x86_64/egg/thrift/transport/TTransport.py", line 161, in read
File "build/bdist.linux-x86_64/egg/thrift/transport/TSocket.py", line 132, in read
thrift.transport.TTransport.TTransportException: TSocket read 0 bytes
Nothing mentioned in forums or internet was able to help me bypass this issue. Is there a workaround for this ?

Any progress with this one?


Fix typos

Trade-off is always used as a noun, so I think it's a single word.
Its is used in the possessive form, so it shouldn't have an apostrophe.
Add full stops to one of the unordered list items for consistency with the rest of the article.

Thanks @mderriey!


Documents not creating...

python elasticsearch-stress-test.py --es_address <IP_ADDRESS> <IP_ADDRESS> --indices 4 --documents 5 --seconds 120 --not-green --clients 2
Test is done! Final results:
Elapsed time: 132 seconds
Successful bulks: 0 (0 documents)
Failed bulks: 26 (26000 documents)
Indexed approximately 0 MB which is 0.00 MB/s
Cleaning up created indices..  Done!

Can you please provide the output of:
curl <IP_ADDRESS>:9200/_cluster/health
curl <IP_ADDRESS>:9200/_cluster/health
Thanks,
Roi.

both health status is 'red' now.
But before testing the python script both health status were 'green'.

How many nodes are in each cluster?
They are both different clusters, right?

no, same cluster.
<IP_ADDRESS> --> master node
<IP_ADDRESS> --> client node

So that is the issue..
You should only place the client.
The ability to use multiple addresses is for different ES clusters.
Check all your red indices, delete them and run the script again using only one address (preferably the one of the client node).
Ill update the docs to better clarify the issue.
Please let me know if that worked out

Its working now.
Thank you

Awesome. Good day!

The cluster health status always remain 'red' after inserting

Can you please past the exact command you are running,
And also the output of curl http://cluster:9200/_cat/indices before, and after the run.
Thanks

Before:
curl http://$(curl ident.me):9200/_cat/indices?v  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                             Dload  Upload   Total   Spent    Left  Speed

100    14    0    14    0     0     26      0 --:--:-- --:--:-- --:--:--    26
health status index pri rep docs.count docs.deleted store.size pri.store.size
After:
curl http://$(curl ident.me):9200/_cat/indices?v  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100    14    0    14    0     0     25      0 --:--:-- --:--:-- --:--:--    25
health status index          pri rep docs.count docs.deleted store.size pri.store.size
red    open   hfpbtkluffey     3   1
red    open   quaxpgkzqpcvte   3   1
red    open   qn               3   1
red    open   ydy              3   1

And the command you used to run?
Did you use the --no-cleanup flag?
What is your ES version and topology? (how many nodes from each type)
Any shard awareness configured?

python elasticsearch-stress-test.py --es_address XX.XX.XX.01 XX.XX.XX.02 --indices 4 --documents 5 --seconds 120 --no-cleanup --not-green --clients 2

Elasticsearch version--2.3.3, and two nodes from each type

No shard awareness configured

Again, you are running the test on two nodes instead of one..
python elasticsearch-stress-test.py --es_address XX.XX.XX.01 --indices 4 --documents 5 --seconds 120 --not-green --clients 2
Only one node from each cluster should be in use.
And remove the --no-cleanup flag.. using it make the script not to cleanup after itself

I also tested it on one node, and same result found

one node, and without the --no-cleanup
Why are you closing the issue?

I've to work more on elastic-search version-2.3.3 then I'll test it.

ok. LMK

Ok, Thank you.


Get the logstash logs of a running logstash container.

Hi Everyone,
After running an image of logstash, I wanted to monitor its logs but don't know where to find that. This is what I did I connected into the running container with the command,
docker exec -i -t containerId /bin/bash

I went to the folder /var/log/logstash but that folder was empty. I whethering how I can get the logs of the running container.
Any clue please?
Thanks.

Logstash sends logs to stdout by default so you can use
docker logs -f containerId

@panmichal the current docker image (5) is configured to log to file not to stdout.
Is this intentional or a bug?

@jalberto that sounds like a bug -- https://github.com/docker-library/logstash/blob/0f53eec1fe093f059f7bc3aa0ee1a429378a4b00/5.0/Dockerfile#L40-L48 :disappointed:

Looks like the value got renamed:
path.logs: /var/log/logstash

https://github.com/docker-library/logstash/pull/67 :+1:

@tianon great! any idea when it will be merged?

@neddogg @tianon  looks like this could be closed, right?

Indeed, thanks @mi-hol!


Intershpinx :mod:attrs no longer resolves

As of attrs 22.2.0, the intersphinx reference
:mod:`attrs`

no longer resolves.
Sample failed CI downstream CI run:
https://github.com/inducer/pytato/actions/runs/3774274601/jobs/6416277949

Confirmed that no module objects are exposed: https://webknjaz.github.io/intersphinx-untangled/www.attrs.org/.

Sample failed CI downstream CI run:
inducer/pytato/actions/runs/3774274601/jobs/6416277949

Here's the relevant part of that log:
/home/runner/work/pytato/pytato/doc/design.rst:234: WARNING: py:mod reference target not found: attrs
/home/runner/work/pytato/pytato/doc/design.rst:237: WARNING: py:mod reference target not found: attrs
/home/runner/work/pytato/pytato/doc/design.rst:244: WARNING: py:mod reference target not found: attrs
[...]
build finished with problems, 3 warnings.
make: *** [Makefile:20: html] Error 1
Error: Process completed with exit code 2.

@inducer Here's alternatives for you to use @ https://github.com/inducer/pytato/blob/5aee209/doc/design.rst#dataclasses--modattrs:
:doc:`attrs <attrs:index>`

:doc:`attrs <attrs:overview>`

:doc:`attrs <attrs:api>`

:doc:`attrs <attrs:why>`

Provided that you fix your https://github.com/inducer/pytato/blob/5aee209/doc/conf.py#L17-L32 to use modern syntax with a mapping with attrs as a key for the corresponding intersphinx link.

This patch is at fault: 15230d9 (#1067).
cc @hynek dunno if this was intentional, but I'd treat intersphinx objects as public API.
P.S. @inducer it is possible to cache the object.inv files right in your repo making your builds more predictable.

Yeah this was not on purpose, so sorry for the breakage.
I've fixed and while looking at it, noticed there's some mangled names like attr.attr.cmp_using sigh.
Is the untangling link supposed to update somehow?

I've fixed and while looking at it, noticed there's some mangled names like attr.attr.cmp_using sigh.
Is the untangling link supposed to update somehow?

@hynek I see that api.rst has .. currentmodule:: attr this is what is prepended to all the definitions in that document. So the reference created by .. autofunction:: attrs.cmp_using becomes
:py:func:`attr.attr.cmp_using`

I suppose that you may want to decide how you want things to be documented and either drop the explicit prefixes or remove the current module directive. I think there's a setting in Sphinx controlling how your API definitions are displayed, too.
P.S. I noticed that there's both .. autofunction:: attrs.cmp_using and .. function:: attr.cmp_using. I think this is redundant.

Another useful setting is :canonical: — https://www.sphinx-doc.org/en/master/usage/restructuredtext/domains.html#directive-option-py-function-canonical. See also add_module_names: https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-add_module_names.

Tracking issue backreference: https://github.com/python-attrs/attrs/issues/1077.

P.S. I noticed that there's both .. autofunction:: attrs.cmp_using and .. function:: attr.cmp_using. I think this is redundant.

I suspect that sphinx is just being smart if it knows the symbol name (autofunction) vs not.

@hynek but wasn't it you who added both lines?

I'm somewhat confused by the question in this context. For posterity: I've added both such that people can refer to :mod:attr and `:mod:`attrs as OP wanted.
I'm currently splitting the file up in #1080, though.


[SPARK-24963][K8S][TESTS] Add user-specified service account name for client mode test driver pod

What changes were proposed in this pull request?
Adds the user-set service account name for the driver pod in the client mode integration test
How was this patch tested?
Manual test against a custom Kubernetes cluster

@skonto can you sign off here before I merge?

ok to test

Test build #93808 has started for PR 21924 at commit 8afc4e9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/1502/

Test build #93808 has finished for PR 21924 at commit 8afc4e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93808/
Test PASSed.

Merged build finished. Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/1502/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1502/
Test PASSed.

LGTM. I have the same change locally and it works.


Rails 5.1.0.beta1 tagged_with doesn't work

with rails 5.1.0.beta1 i get an error by using tagged_with
NoMethodError: super: no superclass method `quote_value' for #<Class:0x00557b9ce28ca0>
Did you mean?  quote_bound_value

This occures only if i search for an existing tag, If the tag dose not exist the result is just an empty ActiveRecord::Relation as expected.
Rails 5.0.1
>> Price.tagged_with(['expert'])
  ActsAsTaggableOn::Tag Load (0.5ms)  SELECT "tags".* FROM "tags" WHERE (LOWER(name) = LOWER('expert'))
  Price Load (0.5ms)  SELECT "prices".* FROM "prices" JOIN taggings prices_taggings_b780d25  ON prices_taggings_b780d25.taggable_id = prices.id AND prices_taggings_b780d25.taggable_type = 'Price' AND prices_taggings_b780d25.tag_id = 4
=> #<ActiveRecord::Relation [#<Price id: 117, ... >]>

Rails 5.1.0.beta1
> Price.tagged_with(['expert'])
  ActsAsTaggableOn::Tag Load (0.5ms)  SELECT "tags".* FROM "tags" WHERE (LOWER(name) = LOWER('expert'))
NoMethodError: super: no superclass method `quote_value' for #<Class:0x00557b9ce28ca0>
Did you mean?  quote_bound_value
  from (irb):9
>>

+1

+1

+1

this is already fixed on master, but not yet released. So to use master for now:
# TODO: remove once new stable version > 4.0 is released
# https://rubygems.org/gems/acts-as-taggable-on
gem 'acts-as-taggable-on', github: 'mbleigh/acts-as-taggable-on'

Any chance of a release with this?

+1

Any idea on a timeline for a release? Anything I or the community can help with?

I am getting the same error at following specs
Ruby ruby 2.2.2p95
rails 5.1.0
acts-as-taggable-on 4.0.0
The solution suggested by @doits requires 2.2.7 for gem version 5.0.0. I am using 2.2.2. So is it anyway to make it run without upgrading ruby?

Getting this error with Ruby 2.2.0-x64, rails 5.1.1. Tried acts_as_taggable_on v. 4.0.0 and 4.0.0.pre and still got the error.

Using master branch worked for me.

@zeeshangulzar Any luck getting this working on 2.2.2?

Same error on:
Rails 5.1.4
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
acts-as-taggable-on 4.0.0
Solution was to follow @doits post above and change Gemfile to:
gem 'acts-as-taggable-on', github: 'mbleigh/acts-as-taggable-on'

@digifinity I was shifted to ruby version 2.2.7.

Hi @sebg, I'm using the same stack as you.
You can also update the gem to v5, seems to solve the problem also.
gem 'acts-as-taggable-on', '~> 5.0'


Users with first-time PAM authentications cannot access profile page (HTTP 500)

Gitea version (or commit ref):
Git version: bfb44f885468839259bc2ead999953cdd85654e1 (master)
Operating system: Linux Debian 8
Database:

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
Hi everyone,
I have an issue of late when users who have never logged into gitea before authenticate over PAM. The users are authenticated correctly and can access repos (explore) or create their own repos. They are shown in the admin "users" tab.
If these users try to access their dashboard, profile page or private repos page, they are confronted with an empty page and the server returns a statuscode 500 (without showing the usual error page). Any reference to the users profile - including avatars shown in "explore" - return a broken image link. The same applies if any other user attempts to access these users profiles/repos.
There are no error messages, neither in the logs (gitea.log, xorm.log or http.log). The page loaded is simply empty (no source). The HTTP 500 error code only becomes visible when debugging using firefoxes developer mode.
If the same users are created by an admin first, they can login and everything works as expected...
gitea uses HTTPS and was built with the tags "pam certs bindata".
Any advice on how to further debug this issue?
Best regards,
ichrispa

On a side note: I do not remember this error occuring when using the sqlite backend. I recently switched to MySQL (fresh install, the sqlite contents where not ported).

Maybe you can find the error information on console or file that will be helpful.

Retested after Upgrade to 1.4.1; issue appears to have been resolved.
@lunny: Sorry for the long lingering issue and thank you for your assistance.


onCloseClick property passing

I'm just learning React and I'm not trying to be a smart guy, but I think the way the onCloseClick property is passed is not the best practice.
This is because whenever the Employee component renders, a new function is being created and passed as input.
...
export default class App extends Component {
    ...
    onCloseClick = () => {
        this.setState({ employee: null })
    }

    render() {
        ...
        return (
            ...
                { /* employee && <Employee employee={employee} onCloseClick={() => this.setState({ employee: null })}/> */ }
                { employee && <Employee employee={employee} onCloseClick={this.onCloseClick}/>  }
            ...
        )
    }
}

The problem with onCloseClick={this.onCloseClick} is that the this context is lost, so this.setState will be undefined and result in an error.  Instead you can do onCloseClick={this.onCloseClick.bind(this)}, which also results in a new function being created, which is why I like using one line arrow functions for really simple event handlers.

The change that I made works though.  I don't see an error.

Ah, I misread your declaration of onCloseClick.  You're using an ES7 property initializer to bind onCloseClick to this.  I suppose you've got a point, that probably is better.  Such is life with React, best practices evolve quickly :)


Column Action - button position

The column action is placed in a wrong position in the AdminLteTemplate.
TemplateDefault

AdminLteTemplate

I am working to solve this issue.

I solved using this code inside
\resources\views\vendor\admin-lte\default\display\datatables.blade.php
just after the table closing tag

				@foreach ($actions as $action)
					{!! $action !!}
				@endforeach


pair loss

seems the mps loss described in the paper is not the same with the code, which one is the right one?

理解错了tf.reduce_max的意思···


Simplified Chinese Translation w/ minor English i18n file fix

Added Simplified Chinese translation.
Fixed duplicate in original English i18n file on pages.event.subpages.admin.stream_card, the unlinked_stream and linked_stream value.

Fixed 👍

@ssysm Thank you!!
Merged 🚀

Glad to be of help! 🎉


Sending multiple messages using binding to servicebus via IAsyncCollector

Is there a way/sample showing how to send out multiple messages using "Message" datatype instead of string. When I tried doing it via C#, it gave exception (shown below).
I would like to send messages using Message data type so as to be able to populate UserProperties on Message type using which I can have Rules in Azure Servicebus to filter for subscriptions.
Microsoft.Azure.WebJobs.Host.FunctionInvocationException: Exception while executing function: OnOrderPlacedHandler ---> Newtonsoft.Json.JsonSerializationException: Error getting value from 'ExpiresAtUtc' on 'Microsoft.Azure.ServiceBus.Message'. ---> System.InvalidOperationException: Operation is not valid due to the current state of the object.
at Microsoft.Azure.ServiceBus.Message.SystemPropertiesCollection.ThrowIfNotReceived()
at Microsoft.Azure.ServiceBus.Message.get_ExpiresAtUtc()
at lambda_method(Closure , Object )
at Newtonsoft.Json.Serialization.ExpressionValueProvider.GetValue(Object target)

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

ID: 0440205f-adcc-0fc5-3adb-db4dbe1d1292
Version Independent ID: 14ad1300-590c-8102-6887-366078e1882a
Content: Azure Service Bus bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-service-bus.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hi @rishabhsajmera - Thank you for your feedback! We will review and update as appropriate.


Fix redux compose undefined error

Fix Uncaught ReferenceError: compose is not defined in create-store

Thank you! Again this is something I'd fixed in my private clone of this boilerplate but forgot to merge it back here


GCP-provider not working

Hi, I installed everything but not able to install gcp-provider. Keep getting:
error: unable to recognize "provider.yaml": no matches for kind "ProviderConfig" in version "gcp.crossplane.io/v1beta1"
Could you please help?
Thanks,
Anil

Hey @anilnokia , thanks for raising this issue!
What version of Crossplane is installed in your cluster? What version of provider-gcp?
Also, can you please send here the output of the following commands:
kubectl describe pkg <your-provider-gcp-name>
kubectl describe pkgrev <your-gcp-provider-revision-name>

Hi,
I installed 1.7 version of both. But gcp is not showing me healthy. Can I delete and try to install again? I tried to delete but was not successful.
It seems like I am behind proxy so it is timing out. How can I fix this?
Thanks,
@.*** ~]$ kubectl describe configuration.pkg.crossplane.io/xp-getting-started-with-gcp
Name:         xp-getting-started-with-gcp
Namespace:
Labels:
Annotations:
API Version:  pkg.crossplane.io/v1
Kind:         Configuration
Metadata:
Creation Timestamp:  2022-04-25T23:34:56Z
Generation:          1
Managed Fields:
API Version:  pkg.crossplane.io/v1
Fields Type:  FieldsV1
fieldsV1:
f:spec:
.:
f:ignoreCrossplaneConstraints:
f:package:
f:packagePullPolicy:
f:revisionActivationPolicy:
f:revisionHistoryLimit:
f:skipDependencyResolution:
f:status:
Manager:         kubectl-crossplane
Operation:       Update
Time:            2022-04-25T23:34:56Z
Resource Version:  5759179
UID:               4aafe9e3-1250-43f0-b2cd-4f99210b72d5
Spec:
Ignore Crossplane Constraints:  false
Package:                        registry.upbound.io/xp/getting-started-with-gcp:v1.7.0
Package Pull Policy:            IfNotPresent
Revision Activation Policy:     Automatic
Revision History Limit:         0
Skip Dependency Resolution:     false
Events:
Type     Reason         Age                  From                                      Message

Warning  UnpackPackage  58s (x524 over 12h)  packages/configuration.pkg.crossplane.io  cannot unpack package: failed to fetch package digest from remote: Get "https://registry.upbound.io/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 8:13 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Hey @anilnokiahttps://github.com/anilnokia , thanks for raising this issue!
What version of Crossplane is installed in your cluster? What version of provider-gcp?
Also, can you please send here the output of the following commands:
kubectl describe pkg
kubectl describe pkgrev
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109718869, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQWRNVETETCSXKWXZFLVG7MUBANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

docker search crossplane/getting-started-with-gcp
NAME      DESCRIPTION   STARS     OFFICIAL   AUTOMATED
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 9:05 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
It seems like I am behind proxy so it is timing out. How can I fix this?
Probably that's the problem. I installed the same Configuration in my local cluster and its healthy.
[image]https://user-images.githubusercontent.com/11353912/165304987-244fd118-c352-44cd-b9e1-d02b237b5770.png
I don't know how to debug your proxy problems, but it looks like you are timeouting when trying to GET from the upbound registry.
Please, try to kubectl delete your Configuration and apply this one instead:
apiVersion: pkg.crossplane.io/v1
kind: Configuration
metadata:
name: xp-getting-started-with-gcp
spec:
ignoreCrossplaneConstraints: false
package: crossplane/getting-started-with-gcp
packagePullPolicy: IfNotPresent
revisionActivationPolicy: Automatic
revisionHistoryLimit: 0
skipDependencyResolution: false
The only difference here is that you would pull from the docker hub instead of upbound registry. Can you check if this works for you?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109771943, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQSCGMO5J6VMKTVJUNTVG7SWHANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

First of all I thank you very very much for replying to me. I really liked step by step instructions you have. I am so close to making this work and your help is invaluable.
Strange but when I put that in yaml file it still gives me timeout but manually I am able to pull it. Should I just pull on all cluster nodes?
Then I can try kubectl apply -f gcp.yaml
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 9:18 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Is it a local or remote cluster? If it is remote, maybe there is some network configuration blocking the communication.
What happens if you docker pull crossplane/getting-started-with-gcp:master?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109786913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQU5UP5WP2LP2G477ILVG7UJ7ANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It still times out! I do not understand! I got image on all nodes
Warning  UnpackPackage  45s   packages/configuration.pkg.crossplane.io  cannot unpack package: failed to fetch package digest from remote: Get "https://index.docker.io/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  UnpackPackage  14s   packages/configuration.pkg.crossplane.io  cannot unpack package: failed to fetch package digest from remote: Get "https://index.docker.io/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 9:18 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Is it a local or remote cluster? If it is remote, maybe there is some network configuration blocking the communication.
What happens if you docker pull crossplane/getting-started-with-gcp:master?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109786913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQU5UP5WP2LP2G477ILVG7UJ7ANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It still fails:
error: unable to recognize "STDIN": no matches for kind "ProviderConfig" in version "gcp.crossplane.io/v1beta1"
I also tried v1
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 9:18 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Is it a local or remote cluster? If it is remote, maybe there is some network configuration blocking the communication.
What happens if you docker pull crossplane/getting-started-with-gcp:master?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109786913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQU5UP5WP2LP2G477ILVG7UJ7ANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It is local on prem
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 10:55 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Is your cluster remote or local?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109899650, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQR64KEMHM5YKWFSE3TVG77U7ANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I'm fairly sure that's commucation problem between your cluster and the registries rather than a Crossplane issue.
I think I can't help you more than that because I don't know about your context. If you just want to test Crossplane, I think its easier if you use a local cluster. I would recommend trying it with minikube, kind or k3d

Ok so I created cluster on external network and now that part is working. I would like to create a sample gke cluster. But it fails. Do you have simple sample yaml file to create gke cluster?
Thanks,
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 11:00 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
I'm fairly sure that's commucation problem between your cluster and the registries rather than a Crossplane issue.
I think I can't help you more than that because I don't know about your context. If you just want to test Crossplane, I think its easier if you use a local cluster. I would recommend trying it with minikubehttps://minikube.sigs.k8s.io/docs/start/, kindhttps://kind.sigs.k8s.io/ or k3dhttps://k3d.io/v5.4.1/
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109905056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQUP4GZQW6WPF2H6D2DVHAAFPANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

This is the error I get:
unable to recognize "gke.yaml": no matches for kind "GKECluster" in version "container.gcp.crossplane.io/v1beta1"
unable to recognize "gke.yaml": no matches for kind "NodePool" in version "container.gcp.crossplane.io/v1alpha1"
Here is my yaml:
apiVersion: container.gcp.crossplane.io/v1beta1
kind: GKECluster
metadata:
name: gitops
spec:
forProvider:
location: us-east1-b
initialClusterVersion: latest

apiVersion: container.gcp.crossplane.io/v1alpha1
kind: NodePool
metadata:
name: gitops
spec:
forProvider:
locations:
- us-east1-b
clusterRef:
name: gitops
initialNodeCount: 1
config:
preemptible: true
machineType: e2-standard-2
oauthScopes:
- https://www.googleapis.com/auth/cloud-platform
autoscaling:
enabled: true
minNodeCount: 1
maxNodeCount: 2
management:
autoUpgrade: false
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 11:00 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
I'm fairly sure that's commucation problem between your cluster and the registries rather than a Crossplane issue.
I think I can't help you more than that because I don't know about your context. If you just want to test Crossplane, I think its easier if you use a local cluster. I would recommend trying it with minikubehttps://minikube.sigs.k8s.io/docs/start/, kindhttps://kind.sigs.k8s.io/ or k3dhttps://k3d.io/v5.4.1/
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1109905056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQUP4GZQW6WPF2H6D2DVHAAFPANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

You can check what kinds are available for provider-gcp in this website. I think the provider is now healthy, right?

Yes it is.
Thanks

From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 4:31:32 PM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
You can check what kinds are available for provider-gcp in this websitehttps://doc.crds.dev/github.com/crossplane/provider-gcp. I think the provider is now healthy, right?
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1110221431, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQVFRISKCHJ4V4QW4ODVHBHCJANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID: @.***>

I modified kind and now it says created bit when I do describe on cluster I get following. Could you please help? I am so close to it!
Last Transition Time:  2022-04-26T21:42:33Z
Message:               connect failed: ProviderConfig.gcp.crossplane.io "default" not found
Reason:                ReconcileError
Status:                False
Type:                  Synced
Events:
Type     Reason                   Age                 From                                         Message

Warning  CannotConnectToProvider  14s (x19 over 13m)  managed/cluster.container.gcp.crossplane.io  ProviderConfig.gcp.crossplane.io "default" not found
Thanks,
From: Gabriel Ferreira @.>
Sent: Tuesday, April 26, 2022 5:42 PM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
Closed #430https://github.com/crossplane/provider-gcp/issues/430.
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#event-6502177017, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQQ5ZF52PSDWWXOXXT3VHBPLZANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

As you can see in your logs:
  Warning  CannotConnectToProvider  14s (x19 over 13m)  managed/cluster.container.gcp.crossplane.io  ProviderConfig.gcp.crossplane.io "default" not found

You need to create a ProviderConfig and reference it in your managed resources. I would recommend you to read more the Crossplane documentation to understand these resources

Thanks.
So I tried mysql example and it works fine. Is there an example to create gke cluster for this provider? That is what I am looking for. Example I ran had trouble. Please let me know if you have very simple gke cluster example which I can use and build on the top of it.
Thanks a million for your help.
From: Gabriel Ferreira @.>
Sent: Wednesday, April 27, 2022 4:36 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
As you can see in your logs:
Warning  CannotConnectToProvider  14s (x19 over 13m)  managed/cluster.container.gcp.crossplane.io  ProviderConfig.gcp.crossplane.io "default" not found
You need to create a ProviderConfig and reference it in your managed resources. I would recommend you to read more the Crossplane documentationhttps://crossplane.io/docs/v1.7/ to understand these resources
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1110715029, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQVKNF22VJK4Y3UWMILVHD355ANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I guess your manifest for the GKE cluster should be fine, you just need to reference the ProviderConfig that you have installed in your cluster. (if you don't have one, you need to create it. Check the documentation to do it)
kubectl get providerconfig will output its NAME, then you can use it in the field spec.providerConfigRef.Name
Here is the field for the Cluster kind and here is for the NodePool.
There is an example file in this repository, you can check it at examples/gke/gke.yaml. Please note that this example file doesn't expose a providerConfigRef field, so it will use the name default. If you have a ProviderConfig created with another name in your cluster, you should reference it by specifying the spec.providerConfigRef.Name

Ok thanks.
I am using an example. Now a get permission issue:
observe failed: cannot get GKE cluster: googleapi: Error 403: Required "container.clusters.get" permission(s) for "projects/astral-field-348017/zones/us-east1-b/clusters/example-cluster"., forbidden
Reason:                ReconcileError
From: Gabriel Ferreira @.>
Sent: Wednesday, April 27, 2022 9:05 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
I guess your manifest for the GKE cluster should be fine, you just need to reference the ProviderConfig that you have installed in your cluster. (if you don't have one, you need to create it. Check the documentationhttps://crossplane.io/docs/v1.7/getting-started/install-configure.html#get-gcp-account-keyfile to do it)
kubectl get providerconfig will output its NAME, then you can use it in the field spec.providerConfigRef.Name
@.#spec-providerConfigRef-name> is the field for the Cluster kind and @.#spec-providerConfigRef-name> is for the NodePool.
There is an example file in this repository, you can check it at examples/gke/gke.yamlhttps://github.com/crossplane/provider-gcp/blob/master/examples/gke/gke.yaml. Please note that this example file doesn't expose a providerConfigRef field, so it will use the name default. If you have a ProviderConfig created with another name in your cluster, you should reference it by specifying the spec.providerConfigRef.Name
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1110975869, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQQLHYPEIML5ENXZR5TVHE3QHANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It seems to work now after I added more roles to service account!
Thanks
From: Gabriel Ferreira @.>
Sent: Wednesday, April 27, 2022 9:05 AM
To: crossplane/provider-gcp @.>
Cc: Rana, Anil (Nokia - US/Murray Hill) @.>; Mention @.>
Subject: Re: [crossplane/provider-gcp] GCP-provider not working (Issue #430)
I guess your manifest for the GKE cluster should be fine, you just need to reference the ProviderConfig that you have installed in your cluster. (if you don't have one, you need to create it. Check the documentationhttps://crossplane.io/docs/v1.7/getting-started/install-configure.html#get-gcp-account-keyfile to do it)
kubectl get providerconfig will output its NAME, then you can use it in the field spec.providerConfigRef.Name
@.#spec-providerConfigRef-name> is the field for the Cluster kind and @.#spec-providerConfigRef-name> is for the NodePool.
There is an example file in this repository, you can check it at examples/gke/gke.yamlhttps://github.com/crossplane/provider-gcp/blob/master/examples/gke/gke.yaml. Please note that this example file doesn't expose a providerConfigRef field, so it will use the name default. If you have a ProviderConfig created with another name in your cluster, you should reference it by specifying the spec.providerConfigRef.Name
—
Reply to this email directly, view it on GitHubhttps://github.com/crossplane/provider-gcp/issues/430#issuecomment-1110975869, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFOUWQQLHYPEIML5ENXZR5TVHE3QHANCNFSM5UKJGW2A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I am just trying example of creating gke cluster from:
https://github.com/crossplane/provider-gcp/blob/master/examples/gke/gke.yaml
but it keep giving me permission problem. Do I need to do something before I create cluster?
Message:               observe failed: cannot get GKE cluster: googleapi: Error 403: Required "container.clusters.get" permission(s) for "projects/astral-field-348017/zones/us-east1-b/clusters/auto-k8s"., forbidden
Reason:                ReconcileError
Status:                False


Proposal: Remove store.Create, always return empty document from store.Fetch

@Jeffail, this is an opinionated proposal, if you don't like it please close it immediately.
There is no reason to do this if there are lots of valid use-cases for having create.

The idea is to remove store.Create and have store.Fetch always return an empty document, if a document doesn't exist. It'll still need an err response for internal errors, and in cases where documentId is too large or in a format not support by the storage engine.
A long with this I would probably suggest that we also reduce auth to only care about permissions Edit and ReadOnly. So technically someone could still prevent new documents, by restricting access using auth (ie. forbid anyone from editing a document that doesn't exist). But as far as curator goes, it seems like a lot of extra cases to deal with.

Unrelated My goal with this is to build an etherpad-like thing. Just more robust, better scalability and less maintenance, my biggest concern for now is complexity of the API, ie. there is a lot of corner cases that I don't think most people will care about.
The last concern is scalability, specifically I see some locks both curator and binder level... I filed a bug for the curator level lock to not cover I/O, but the binder level kick user locks seems to be about slow web sockets (are they able to make the document slow for all users?). Granted I'm less concerned about those for now.

Also if we do this, perhaps store.Fetch and store.Store should be renamed, get/set, and operate on `[]byte, so that any future model that does more fancy things can use the different stores too...
Proposed interface:
type Store interface {
	Set(id string, content []byte) error
	Get(id string) ([]byte, error)
}

I doubt anyone is going to do new document models... Text is pretty useful, though it would be nice to have some JSON properties for editor settings. But then again, when storing in blob storage, it's nice that all documents are plain text in terms for backup, etc.

Not sure if it would be feasible, but adding:
RegisterHandlers(register register.PubPrivEndpointRegister) error
Would also be nice, notably because different storage engines supports different ways of listing/search/finding documents.


link to docker completion file returns 404 Not found - needs update

File: machine/completion.md, CC @londoncalling

Fixed by #3701

Under the Mac instructions, the link https://raw.githubusercontent.com/docker/docker-ce/master/components/engine/contrib/completion/bash/docker still returns 404, so anyone using that command will get a file with the contents "404 Not found" in it, instead of a working completion file.
Line 24 and 30.

True. My fix only was for the zsh version.
I updated with a new PR.


118 march23 update

Creating a pull request because it's at least functional and people are griping about the new changes.
Let's push this ASAP. We can fix remaining nits as we have time, but let's at least get it basically functional.
I've been using it for my reviews without issue. I've also created a new account so I could have some lessons to examine.
I've also tried to only add rules and not delete anything (just in case they decide to revert back to the old stuff, even temporarily).
Looks good enough to go live now, imo, since review/lesson pages are totally broken without these changes.

Ping.
Any chance you can take a look at this?


TypeError: process2predict() takes 1 positional argument but 3 were given

Thanks for sharing the code! The predict.py cannot run successfully. It reports TypeError: process2predict() takes 1 positional argument but 3 were given

I find the answer which is changing the code from def process2predict(cell_feature): to def process2predict(cell_feature, s_norm, rul_norm):
The output of this code is:
training_RUL_mae:21.695
training_S_mae:21.179
testing_RUL_mae:48.420
testing_S_rmae:34.240


Custom Role Example Doesn't Work?

I tried the Custom Roles example and couldn't get it to work with that granular of a scope when creating the role assignment.  I had to set the role assignment at the service level in order for the user to see the service in the portal.
I'm using the az cli 2.0.32 instead of powershell, but same concept.

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

ID: 7f6c6659-7532-1696-7875-b4bf01d3862e
Version Independent ID: ad6e75d0-691f-a08b-e5f0-3f94cbf68fdf
Content: How to use Role-Based Access Control in Azure API Management
Content Source: articles/api-management/api-management-role-based-access-control.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

In fact, I can't seem to get this example to work at all.  When I try it, the user can still edit other APIs that weren't given to him via the scope.

@freedumb Thank you for the feedback.  We'll look through the documentation and get back to you soon.

@vladvino We should also let customer know that in order to see APIs in APIM or even APIM in Azure portal, they need to assign a read permission at APIM scope level not at the API level. Many customers are confused about why they can't see APIM in their Azure portal even when they have grant a read permission to the API

@vladvino Please also let users know that in order to see APIs in APIM or even APIM in Azure portal, they need to assign a read permission at APIM scope level not at the API level. Many users are confused about why they can't see APIM in their Azure portal even when they have grant a read permission to the API

Thanks for the feedback. I have added them to our work backlog.
#please-close

@freedumb We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@BryanTrach-MSFT Did you manage to update the docs? I am trying to reuse the custom role example to create API revisions and import OpenApi schema into them, but I am getting the following error (both on az apim api revision create and az apim api import):
AuthorizationFailed: The client 'XXX' with object id 'XXX' does not have authorization to perform action 'Microsoft.ApiManagement/service/apis/write' over scope '/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.ApiManagement/service/XXX/apis/XXX;rev=5' or the scope is invalid. If access was recently
granted, please refresh your credentials.

And I believe I have the role defined as in the example:
{
    "assignableScopes": [
      "/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.ApiManagement/service/XXX/apis/XXX"
    ],
    "description": "This is a custom role",
    "id": "/subscriptions/XXX/providers/Microsoft.Authorization/roleDefinitions/XXX",
    "name": "XXX",
    "permissions": [
      {
        "actions": [
          "Microsoft.ApiManagement/service/apis/write",
          "Microsoft.ApiManagement/service/apis/*/write"
        ],
        "dataActions": [],
        "notActions": [],
        "notDataActions": []
      }
    ],
    "roleName": "XXX",
    "roleType": "CustomRole",
    "type": "Microsoft.Authorization/roleDefinitions"
  }

Just to be clear, I also tried a custom role with additional permissions derived from API Reader Role:
[
      "Microsoft.ApiManagement/service/apis/write",
      "Microsoft.ApiManagement/service/apis/*/write",

      "Microsoft.ApiManagement/service/*/read",
      "Microsoft.ApiManagement/service/read",
      "Microsoft.Authorization/*/read",
      "Microsoft.Insights/alertRules/*",
      "Microsoft.ResourceHealth/availabilityStatuses/read",
      "Microsoft.Resources/deployments/*",
      "Microsoft.Resources/subscriptions/resourceGroups/read",
      "Microsoft.Support/*"
]

However, this didn't change the behaviour. Throughout the entire exercise, my SP also had a Reader role added on the entire API Management Service resource.


v9 support lower Redis versions?

I did a quick test with v9 of this package.
It works with v7 of Redis as mentioned in docs.
When I tried it with v6 of Redis, it did not connect.
Do I have to use v8 of this package to use with v6?
Is there a chance that v9 of this package can support v6 and v7 of Redis?

Adding to the question, I'd like to understand the differences between major versions (regular, v8, v9), because I couldn't find in docs.
It would be great to have a migration description from one to another aswell.

If you are using Redis 6, install go-redis/v8:
go get github.com/go-redis/redis/v8

If you are using Redis 7, install go-redis/v9:
go get github.com/go-redis/redis/v9

But github.com/go-redis/redis/v9 should also work with Redis 6.


Revert "[APIDiff] Add baseline management flags"

Reverts apple/swift-package-manager#3532

We'll re-merge after test runs on latest main

Reverting doesn't unblock builds, so abandoning.


Service registration

Context
It'd be awesome if synapse was able to expose service calls to home assistant, in addition to entities. This would enable more standard interactions via hass.call, instead of weird side workflows involving buttons
Some chatgpt proof of concept to visualize python side.
from homeassistant.helpers import config_validation as cv
import voluptuous as vol

async def handle_service_call(call):
    # Handle the service call here
    service_data = call.data
    # Example: service_data might include parameters passed to the service

async def async_setup(hass, config):
    service_schema = vol.Schema({
        vol.Required('field1'): cv.string,
        vol.Optional('field2', default='default_value'): cv.string,
        vol.Required('field3'): cv.positive_int,
    })

    service_description = {
        "description": "Description of what this service does",
        "fields": {
            "field1": {
                "description": "Description of field1",
                "example": "example_value"
            },
            "field2": {
                "description": "Description of field2",
                "example": "example_value"
            },
            "field3": {
                "description": "Description of field3",
                "example": 42
            }
        }
    }

    # Register the service
    hass.services.async_register(
        domain='your_domain',
        service='your_service',
        service_func=handle_service_call,
        schema=service_schema,
        description=service_description
    )

    return True

Blocked by https://github.com/Digital-Alchemy-TS/hass/issues/34

Needs consideration for

Comms protocol
How to handle conflicts
Using other domains?
Schema
Return responses

Schema

Seems like this might be best approached with something that do validation. class-validator, zod, and the like have the ability to check on the incoming values.
Also have build in flows for translating to json schema, which can then be converted back for vol in python

Not sure what the flavor of the month for validators is tho

How to handle conflicts

Maybe an expansion issue here. Seems like v1 should allow some foot gun and allow conflicts
A follow up might have apps that are conflict-y emit some warnings


hyprland: init at unstable-23-04-2022

Description of changes

Added hyprland: A dynamic tiling Wayland compositor that doesn't sacrifice on its looks.
Since hyprland also requires wlroots-git to build, I also packaged wlroots-git.
Closes: #168392
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I'm not very familiar with the submission process but I was wondering what's stopping this going through into nixpkgs?

I'm also kinda against merging this until there is a release that targets a tagged version of wlroots. If you do want to use/test hyprland, there is a flake in the official repo now. https://github.com/vaxerski/Hyprland/blob/main/flake.nix

There is now a tag at 0.1.0beta!
but Hyprland has a module and definition (see flake.nix) that I think are a but cleaner than this? https://github.com/vaxerski/Hyprland
The module needs some work, but the package is fine

I think now that there is a tagged release, and that there seems to be more interest in getting this packaged, I'm no longer against merging this. It still requires wlroots-git so I just overrode wlroots for hyprland instead of creating a wlroots-git package.

It no longer requires wlroots-git as wlroots it is bundled https://github.com/vaxerski/Hyprland/releases/tag/v0.2.0beta

I think the best course of action here is to still override wlroots without building the bundled version as there are issues with building the bundled version on nix: https://github.com/vaxerski/Hyprland/pull/86#issuecomment-1141908574.


[BUG] Messages with an ItemHover tooltip do not send on dedicated server when the ItemStack has NBT

What happened?

Messages with an HoverEvent.ShowItem tooltip do not send on dedicated server when the ItemStack has NBT

What should happen?

The message should appear; instead it does not get sent to clients

Steps to reproduce

Install Quark and DI-forge (any newer version works)
Press Shift-T over an item without NBT (e.g. water bucket)
Press Shift-T over an item with NBT (e.g. enchanted sword)
Water bucket will share properly, but sword wil lnot

Version

[ ] 1.12
[X] 1.16

Platform

[X] Forge
[ ] Spigot

Mod version:
Additional info

After some debugging, I think this is due to an issue with the Adventure library this uses, specifically here: in more recent versions, NBT tags on items are serialized to complex JSON objects rather than raw strings. I am not certain, however, and more research may be required

Second confirmation on this issue - messages aren't getting sent because your event handler is crashing with a jda exception - "Title may not be empty"
Relevant server log : https://gist.github.com/Shadows-of-Fire/79777ffa1dfbfaa9dc80245bb485e1f1


build(deps): update fastlane and other deps

This PR resolves PHIRE-105
Description
update fastlane and other deps via bundle update fastlane

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

update fastlane and other deps - gkartalis

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (update fastlane and other deps - gkartalis)

  Generated by :no_entry_sign: dangerJS against 720a2be53b40804086e2dde72862f3f5d3ccf581


Add Mel filterbank and MFCC feature extraction

1.migrate from my C++ code
or
2. write from scratch
or
3. write port to SPTK

I have already a MFCC function that wraps SPTK's mfcc function. I close this.


Add a bunch of logging to Darwin MTRDevice/MTRClusters

We should log things like:

When operations are queued.
When operations are pulled from the queue and started.
When operations are completed.

Ideally including the fabric index and target id in the logs.

@jtung-apple what's left here after https://github.com/project-chip/connectedhomeip/pull/23784?

@jtung-apple what's left here after #23784?

Fabric index. I'll make a PR to add this.


Query Parser crashes on some "NOT IN" clauses, tuple not in, not related to yada param

The below query does not succeed to be parsed.
The reason might be perhaps the "NOT IN" clause is confusing the parser; but please note that it does not user any yada parameters ?x ..
Please note that the 'NOT IN' is also using a "tuple NOT IN" clause; which is probably nowhere in your test cases, but handy handy.
INSERT into DISMISSED_DATA(inv_upload_id,excel_rix,md5,depot,orig_json,is_active,mod_emp521,mod_time)
SELECT inv_upload_id,excel_rix,md5,depot,orig_json,1,mod_emp521,mod_time
FROM PROCESSED_DATA
WHERE INV_UPLOAD_ID=?n
AND IS_IGNORE_ROW=1
AND (depot,md5) not in (SELECT depot,md5 FROM DISMISSED_DATA where is_active=1)
The query works written as:
INSERT into DISMISSED_DATA(inv_upload_id,excel_rix,md5,depot,orig_json,is_active,mod_emp521,mod_time)
SELECT p.inv_upload_id,p.excel_rix,p.md5,p.depot,p.orig_json,1,p.mod_emp521,p.mod_time
FROM PROCESSED_DATA p LEFT JOIN DISMISSED_DATA d on (p.depot=d.depot and d.md5=p.md5 and d.is_active=1)
WHERE p.INV_UPLOAD_ID=?n
AND p.IS_IGNORE_ROW=1
AND d.depot is null
Example invocation:
http://localhost/yada.jsp?j=[{"qname":"DSMT+Commit+Dismissed+Rows+step+1b",DATA:[{"INV_UPLOAD_ID":"99"}]}]

After upgrading to the latest version of JsqlParser, I couldn't reproduce this issue.  Further testing is required though before closing.  At the very least the original query should be tested.

The original issue is not reproducible.  My suspicion is that the upgrade to the latest version of JSQLParser/JSqlParser fixed it, but it might also have been the mods to IN clause processing.


Update Composer dependencies (2022-12-21-00-12)

Visual regression test passed!
View the visual regression test report


With Astro instructions for global styles and dark mode need to use layout

With Astro instructions for global styles and dark mode need to use layout
The instructions right now suggest to place these in the index.astro file which is dedicated for the home page only. These should rely on Astro's layout files of wherever the root html layout is set.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


support external state change that can fail

I changed the state mutator to be able to return a boolean - so the set state can fail
this can be used when trying to set the state in DB using optimistic locking, which can fail to set the state.

I'll have to look into this PR a little bit more, as I had my own idea for implementing this.


Updated the login page @nirmalyax

Crteated the Login and Signup page for the website #125

Thanks for the PR. It has been merged.


[realm-core-2.8.1] Assertion failed: m_schema_version != ObjectStore::NotVersioned

Reported by a user from HelpScout:
https://secure.helpscout.net/conversation/381267285/10294/?folderId=440773
Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:358: [realm-core-2.8.1] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0 Realm 0x00000001042c23d0 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 44
1 Realm 0x00000001042c26a8 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 388
2 Realm 0x00000001040c1e04 _ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 312
3 Realm 0x000000010400d704 +[RLMRealm realmWithConfiguration:error:] + 5476
4 RealmSwift 0x00000001055b489c _TTOFCSo8RLMRealmCfzT13configurationCSo21RLMRealmConfiguration_S_ + 160
5 RealmSwift 0x00000001055b4b8c _TFC10RealmSwift5RealmcfzT13configurationVS0_13Configuration_S0_ + 600
6 RealmSwift 0x00000001055b4f38 _TFC10RealmSwift5RealmCfzT13configurationVS0_13Configuration_S0_ + 488
7 0x00000001006adfd4 _TFFFC1214KMRealmManager6updateFT6objectCS_8MFYImage6paramsGVs10DictionarySSP___T_U_FT_T_U_FT_T_ + 640
8 0x00000001006ae138 _TTRXFo__zoPs5Error__XFo__iT_zoPS___ + 36
9 libswiftObjectiveC.dylib 0x00000001061196b4 _TF10ObjectiveC15autoreleasepoolurFzT8invokingFzT_x_x + 68
10 0x00000001006adc5c _TFFC1214KMRealmManager6updateFT6objectCS_8MFYImage6paramsGVs10DictionarySSP___T_U_FT_T_ + 240
11 0x000000010057fde8 _TTRXFo___XFdCb___ + 44
12 libdispatch.dylib 0x0000000180fa5200 <redacted> + 24
13 libdispatch.dylib 0x0000000180fa51c0 <redacted> + 16
14 libdispatch.dylib 0x0000000180fb3444 <redacted> + 928
15 libdispatch.dylib 0x0000000180fa89a8 <redacted> + 652
16 libdispatch.dylib 0x0000000180fb538c <redacted> + 572
17 libdispatch.dylib 0x0000000180fb50ec <redacted> + 124
18 libsystem_pthread.dylib 0x00000001811ae2b8 _pthread_wqthread + 1288
19 libsystem_pthread.dylib 0x00000001811adda4 start_wqthread + 4
IMPORTANT: if you see this error, please send this log to<EMAIL_ADDRESS>

Hello, We have also encountered similar issue at our end.
Realm Version: 2.8.3
Encryption: On
/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:358: [realm-core-2.8.1] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x032db950 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 48
1   Realm                               0x032dbd0c _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 492
2   Realm                               0x031aaa8b _ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 283
3   Realm                               0x03139490 +[RLMRealm realmWithConfiguration:error:] + 4464
4   RealmSwift                          0x039ae9d6 _TTOFCSo8RLMRealmCfzT13configurationCSo21RLMRealmConfiguration_S_ + 166
5   RealmSwift                          0x039aed6a _TFC10RealmSwift5RealmcfzT13configurationVS0_13Configuration_S0_ + 778
6   RealmSwift                          0x039af219 _TFC10RealmSwift5RealmCfzT13configurationVS0_13Configuration_S0_ + 505
<REDACTED>
14  libswiftObjectiveC.dylib            0x0726a491 _TF10ObjectiveC15autoreleasepoolurFzT8invokingFzT_x_x + 49
<REDACTED>
18  libdispatch.dylib                   0x0743cf05 _dispatch_call_block_and_release + 15
19  libdispatch.dylib                   0x07467cc9 _dispatch_client_callout + 14
20  libdispatch.dylib                   0x07448517 _dispatch_root_queue_drain + 1635
21  libdispatch.dylib                   0x07447e4c _dispatch_worker_thread3 + 138
22  libsystem_pthread.dylib             0x077c6c7a _pthread_wqthread + 1070
23  libsystem_pthread.dylib             0x077c6826 start_wqthread + 34
IMPORTANT: if you see this error, please send this log to<EMAIL_ADDRESS>

have the same issue:
/Users/yizhongzhuang/Desktop/github/xmail/XMail/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:361: [realm-core-2.8.6] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x000000010ec86b78 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 40
1   Realm                               0x000000010ec86f05 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 517
2   Realm                               0x000000010ea13c2c _ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 332
3   Realm                               0x000000010e920ea4 +[RLMRealm realmWithConfiguration:error:] + 7012
4   RealmSwift                          0x0000000110201caa _T0So8RLMRealmCABSo0A13ConfigurationC13configuration_tKcfCTO + 138
5   RealmSwift                          0x0000000110201b34 _T010RealmSwift0A0CACyKcfc + 100
6   RealmSwift                          0x0000000110201a66 _T010RealmSwift0A0CACyKcfC + 54
72018-05-02 14:24:35.026045+0800 XMail[14128:580575] [WRITE] 05-02 14:24:35.026
[file:]
[line:228]
[func:]
WRITE:["mail.mailID:9--"]
XMail                               0x000000010c38bc33 _T05XMail12StoreManagerC7myRealm33_5B725453E0E39D06960D24A54ED5900ELL0E5Swift0E0CSgvg + 83
8   XMail                               0x000000010c38dd59 _T05XMail12StoreManagerC6objectxSgxm6ofType_q_13forPrimaryKeyt10RealmSwift6ObjectCRbzr0_lF + 105
9   XMail                               0x000000010c5e31e9 _T05XMail4MailC4mailACSgSS4with_tFZ + 201
10  XMail                               0x000000010c5e5a0e _T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycf2018-05-02 14:24:35.026336+0800 XMail[14128:580575] [WRITE] 05-02 14:24:35.026
[file:]
[line:228]
[func:]
WRITE:["mail.mailID:10--"]
U_yACcfU0_ + 110
11  XMail                               0x000000010c5e6159 _T05XMail4MailCs5Error_pIgxzo_ACsAD_pIgizo_TR + 25
12  XMail                               0x000000010c5ee48b _T05XMail4MailCs5Error_pIgxzo_ACsAD_pIgizo_TRTA + 27
13  libswiftCore.dylib                  0x000000011896f54f _T0s8SequencePsE7forEachyy7ElementQzKcKFTf4gn_n + 351
14  libswiftCore.dylib                  0x000000011889749d _T0s8SequencePsE7forEachyy7ElementQzKcKFTm + 13
15  libswiftCore.dylib                  0x0000000118775700 _T0s8SequencePsE7forEachyy7ElementQzKcKF + 16
16  XMail                               0x000000010c5e567d T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycfU + 413
17  XMail                               0x000000010c5ee351 _T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycfU_TA + 33
18  XMail                               0x000000010c2bc9fd _T0Ieg_IeyB_TR + 45
19  libdispatch.dylib                   0x000000011933d73b _dispatch_call_block_and_release + 12
20  libdispatch.dylib                   0x000000011933e779 _dispatch_client_callout + 8
21  libdispatch.dylib                   0x00000001193461b2 _dispatch_queue_serial_drain + 735
22  libdispatch.dylib                   0x00000001193469af _dispatch_queue_invoke + 321
23  libdispatch.dylib                   0x0000000119348cf8 _dispatch_root_queue_drain + 473
24  libdispatch.dylib                   0x0000000119348ac1 _dispatch_worker_thread3 + 119
25  libsystem_pthread.dylib             0x0000000119902169 _pthread_wqthread + 1387
26  libsystem_pthread.dylib             0x0000000119901be9 start_wqthread + 13
IMPORTANT: if you see this error, please send this log to<EMAIL_ADDRESS>14:24:35.027662+0800 XMail[14128:579667] /Users/yizhongzhuang/Desktop/github/xmail/XMail/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:361: [realm-core-2.8.6] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x000000010ec86b78 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 40
1   Realm                               0x000000010ec86f05 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 517
2   Realm                               0x000000010ea13c2c _ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 332
3   Realm                               0x000000010e920ea4 +[RLMRealm realmWithConfiguration:error:] + 7012
4   RealmSwift                          0x0000000110201caa _T0So8RLMRealmCABSo0A13ConfigurationC13configuration_tKcfCTO + 138
5   RealmSwift                          0x0000000110201b34 _T010RealmSwift0A0CACyKcfc + 100
6   RealmSwift                          0x0000000110201a66 _T010RealmSwift0A0CACyKcfC + 54
7   XMail                               0x000000010c38bc33 _T05XMail12StoreManagerC7myRealm33_5B725453E0E39D06960D24A54ED5900ELL0E5Swift0E0CSgvg + 83
8   XMail                               0x000000010c38dd59 _T05XMail12StoreManagerC6objectxSgxm6ofType_q_13forPrimaryKeyt10RealmSwift6ObjectCRbzr0_lF + 105
9   XMail                               0x000000010c5e31e9 _T05XMail4MailC4mailACSgSS4with_tFZ + 201
10  XMail                               0x000000010c5e5a0e T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycfU_yACcfU0 + 110
11  XMail                               0x000000010c5e6159 _T05XMail4MailCs5Error_pIgxzo_ACsAD_pIgizo_TR + 25
12  XMail                               0x000000010c5ee48b _T05XMail4MailCs5Error_pIgxzo_ACsAD_pIgizo_TRTA + 27
13  libswiftCore.dylib                  0x000000011896f54f _T0s8SequencePsE7forEachyy7ElementQzKcKFTf4gn_n + 351
14  libswiftCore.dylib                  0x000000011889749d _T0s8SequencePsE7forEachyy7ElementQzKcKFTm + 13
15  libswiftCore.dylib                  0x0000000118775700 _T0s8SequencePsE7forEachyy7ElementQzKcKF + 16
16  XMail                               0x000000010c5e567d T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycfU + 413
17  XMail                               0x000000010c5ee351 _T05XMail4MailC8addMailsySayACG_SS2toyycSg8completetFZyycfU_TA + 33
18  XMail                               0x000000010c2bc9fd _T0Ieg_IeyB_TR + 45
19  libdispatch.dylib                   0x000000011933d73b _dispatch_call_block_and_release + 12
20  libdispatch.dylib                   0x000000011933e779 _dispatch_client_callout + 8
21  libdispatch.dylib                   0x00000001193461b2 _dispatch_queue_serial_drain + 735
22  libdispatch.dylib                   0x00000001193469af _dispatch_queue_invoke + 321
23  libdispatch.dylib                   0x0000000119348cf8 _dispatch_root_queue_drain + 473
24  libdispatch.dylib                   0x0000000119348ac1 _dispatch_worker_thread3 + 119
25  libsystem_pthread.dylib             0x0000000119902169 _pthread_wqthread + 1387
26  libsystem_pthread.dylib             0x0000000119901be9 start_wqthread + 13
IMPORTANT: if you see this error, please send this log to<EMAIL_ADDRESS>

/Users/ramsey/Work/Codes/esv/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:433: [realm-core-5.23.5] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x0000000107be57dc ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   Realm                               0x0000000107be5a3c ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 324
2   Realm                               0x000000010791e25c ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 176
3   Realm                               0x000000010785ab94 +[RLMRealm realmWithConfiguration:error:] + 1600
4   RealmSwift                          0x0000000108dbe324 $sSo8RLMRealmC13configurationABSo0A13ConfigurationC_tKcfCTO + 148
5   RealmSwift                          0x0000000108dbe4b0 $s10RealmSwift0A0C13configurationA2C13ConfigurationV_tKcfC + 200
6   ESV                                 0x0000000104b2773c $s3ESV11RealmHelperC5realm0B5Swift0B0CyF + 200
7   ESV                                 0x0000000104b27e78 $s3ESV11RealmHelperC10getObjects_12filterString0B5Swift7ResultsCyxGSgxm_SSSgtAF6ObjectCRbzlF + 292
8   ESV                                 0x0000000104ea60d0 $s3ESV7UtilityC8getTokenSSSgyF + 1636
9   ESV                                 0x0000000104934990 $s3ESV10NetworkAPIO5tokenSSSgvg + 104
10  ESV                                 0x00000001049344c0 $s3ESV10NetworkAPIO7headersSDyS2SGSgvg + 864
11  ESV                                 0x00000001049358d8 $s3ESV11RequestablePAASo8NSObjectCRbzrlE25setupNetworkComponentWith6netapi7mapType18mappedObjectHandle8moreInfo12isBackgroundyAA0E3APIO_qd__myqd__cSgyAA9CSMessageO_SbtcSgSbt0L6Mapper8MappableRd__lFySb_SS_SSttcfU + 1264
12  ESV                                 0x0000000104935f68 $s3ESV11RequestablePAASo8NSObjectCRbzrlE25setupNetworkComponentWith6netapi7mapType18mappedObjectHandle8moreInfo12isBackgroundyAA0E3APIO_qd__myqd__cSgyAA9CSMessageO_SbtcSgSbt0L6Mapper8MappableRd__lFySb_SS_SSttcfU_TA + 116
13  ESV                                 0x000000010493aef8 $s3ESV11RequestablePAASo8NSObjectCRbzrlE13isNeedRequest3for10completionyAA10NetworkAPIO_ySb_SS_SSttctFy5Cache6ResultOySSGcfU1_Tf2nni_n + 1620
14  ESV                                 0x000000010493afe0 $s5Cache6ResultOySSGIegg_ADIegn_TR + 64
15  Cache                               0x000000010617a6d4 $s5Cache12AsyncStorageC6object6forKey10completionySS_yAA6ResultOyxGctFyAHyAA5EntryVyxGGcfU + 288
16  Cache                               0x00000001061785dc $s5Cache12AsyncStorageC5entry6forKey10completionySS_yAA6ResultOyAA5EntryVyxGGctFyycfU + 1196
17  Cache                               0x0000000106178710 $sIeg_IeyB_TR + 52
18  libdispatch.dylib                   0x00000001091f1828 _dispatch_call_block_and_release + 24
19  libdispatch.dylib                   0x00000001091f2c04 _dispatch_client_callout + 16
20  libdispatch.dylib                   0x00000001091f9b74 _dispatch_lane_serial_drain + 744
21  libdispatch.dylib                   0x00000001091fa710 _dispatch_lane_invoke + 448
22  libdispatch.dylib                   0x0000000109205ae4 _dispatch_workloop_worker_thread + 1324
23  libsystem_pthread.dylib             0x00000001a9ae3fa4 _pthread_wqthread + 276
24  libsystem_pthread.dylib             0x00000001a9ae6ae0 start_wqthread + 8!!! IMPORTANT: Please send this log and info about Realm SDK version and other relevant reproduction info to<EMAIL_ADDRESS>15:33:10.183786+0800 ESV[1050:442268] /Users/ramsey/Work/Codes/esv/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:433: [realm-core-5.23.5] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x0000000107be57dc ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   Realm                               0x0000000107be5a3c ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 324
2   Realm                               0x000000010791e25c ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 176
3   Realm                               0x000000010785ab94 +[RLMRealm realmWithConfiguration:error:] + 1600
4   RealmSwift                          0x0000000108dbe324 $sSo8RLMRealmC13configurationABSo0A13ConfigurationC_tKcfCTO + 148
5   RealmSwift                          0x0000000108dbe4b0 $s10RealmSwift0A0C13configurationA2C13ConfigurationV_tKcfC + 200
6   ESV                                 0x0000000104b2773c $s3ESV11RealmHelperC5realm0B5Swift0B0CyF + 200
7   ESV                                 0x0000000104b27e78 $s3ESV11RealmHelperC10getObjects_12filterString0B5Swift7ResultsCyxGSgxm_SSSgtAF6ObjectCRbzlF + 292
8   ESV                                 0x0000000104ea60d0 $s3ESV7UtilityC8getTokenSSSgyF + 1636
9   ESV                                 0x0000000104934990 $s3ESV10NetworkAPIO5tokenSSSgvg + 104
10  ESV                                 0x00000001049344c0 $s3ESV10NetworkAPIO7headersSDyS2SGSgvg + 864
11  ESV                                 0x00000001049358d8 $s3ESV11RequestablePAASo8NSObjectCRbzrlE25setupNetworkComponentWith6netapi7mapType18mappedObjectHandle8moreInfo12isBackgroundyAA0E3APIO_qd__myqd__cSgyAA9CSMessageO_SbtcSgSbt0L6Mapper8MappableRd__lFySb_SS_SSttcfU + 1264
12  ESV                                 0x0000000104935f68 $s3ESV11RequestablePAASo8NSObjectCRbzrlE25setupNetworkComponentWith6netapi7mapType18mappedObjectHandle8moreInfo12isBackgroundyAA0E3APIO_qd__myqd__cSgyAA9CSMessageO_SbtcSgSbt0L6Mapper8MappableRd__lFySb_SS_SSttcfU_TA + 116
13  ESV                                 0x000000010493aef8 $s3ESV11RequestablePAASo8NSObjectCRbzrlE13isNeedRequest3for10completionyAA10NetworkAPIO_ySb_SS_SSttctFy5Cache6ResultOySSGcfU1_Tf2nni_n + 1620
14  ESV                                 0x000000010493afe0 $s5Cache6ResultOySSGIegg_ADIegn_TR + 64
15  Cache                               0x000000010617a6d4 $s5Cache12AsyncStorageC6object6forKey10completionySS_yAA6ResultOyxGctFyAHyAA5EntryVyxGGcfU + 288
16  Cache                               0x00000001061785dc $s5Cache12AsyncStorageC5entry6forKey10completionySS_yAA6ResultOyAA5EntryVyxGGctFyycfU + 1196
17  Cache                               0x0000000106178710 $sIeg_IeyB_TR + 52
18  libdispatch.dylib                   0x00000001091f1828 _dispatch_call_block_and_release + 24
19  libdispatch.dylib                   0x00000001091f2c04 _dispatch_client_callout + 16
20  libdispatch.dylib                   0x00000001091f9b74 _dispatch_lane_serial_drain + 744
21  libdispatch.dylib                   0x00000001091fa710 _dispatch_lane_invoke + 448
22  libdispatch.dylib                   0x0000000109205ae4 _dispatch_workloop_worker_thread + 1324
23  libsystem_pthread.dylib             0x00000001a9ae3fa4 _pthread_wqthread + 276
24  libsystem_pthread.dylib             0x00000001a9ae6ae0 start_wqthread + 8!!! IMPORTANT: Please send this log and info about Realm SDK version and other relevant reproduction info to<EMAIL_ADDRESS>

@seamusapple

How often do you see this?
Is this reproducible? How?
Do you know anything about the circumstances when it occurs?

@seamusapple

How often do you see this?
Is this reproducible? How?
Do you know anything about the circumstances when it occurs?

Only once.
So i can not reproduce it.
Sorry i don't know. I just use realm delete, and then it crashed. It is stable used before.

HI @bmunkholm ,
I got the same issue.
it keeps throws this issue in my Xcode. and the Realm file is created but empty without any models.
And I don't know how to make it work again.
realm Version: 3.19.0
/Users/mac/code/3-bitmark/ourbeat/ios/Pods/Realm/Realm/ObjectStore/src/shared_realm.cpp:433: [realm-core-5.23.5] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   Realm                               0x000000011136c29c _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   Realm                               0x000000011136c556 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 390
2   Realm                               0x0000000111054e9d ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 189
3   Realm                               0x0000000110f7e878 +[RLMRealm realmWithConfiguration:error:] + 2104
4   RealmSwift                          0x00000001126afcd1 $sSo8RLMRealmC13configurationABSo0A13ConfigurationC_tKcfCTO + 145
5   RealmSwift                          0x00000001126afe87 $s10RealmSwift0A0C13configurationA2C13ConfigurationV_tKcfC + 183
6   OurBeat Dev                         0x000000010e73dca2 $s11OurBeat_Dev11RealmConfigO07currentD00D5Swift0D0CyKFZ + 850
7   OurBeat Dev                         0x000000010e7386d1 $s11OurBeat_Dev7StorageC28performSerialBackgroundWrite33_0FFAEE7E3C7FDDC84B4052F48C9C9023LL10writeBlock010completionR0yy10RealmSwift0T0CKc_ys5Error_pSgcSgtFyycfU + 97
8   OurBeat Dev                         0x000000010e72121d $sIeg_IeyB_TR + 45
9   libdispatch.dylib                   0x0000000116093dd4 _dispatch_call_block_and_release + 12
10  libdispatch.dylib                   0x0000000116094d48 _dispatch_client_callout + 8
11  libdispatch.dylib                   0x000000011609b5ef _dispatch_lane_serial_drain + 788
12  libdispatch.dylib                   0x000000011609c17f _dispatch_lane_invoke + 422
13  libdispatch.dylib                   0x00000001160a7a4e _dispatch_workloop_worker_thread + 719
14  libsystem_pthread.dylib             0x0000000116510763 _pthread_wqthread + 290
15  libsystem_pthread.dylib             0x00000001165105c3 start_wqthread + 15!!! IMPORTANT: Please send this log and info about Realm SDK version and other relevant reproduction info to<EMAIL_ADDRESS>

Hi @bmunkholm,
I can reproduce this issue very easily within my app:
Context

I have a multi user application, where there is one Realm for one user. (But the issue can be reproduced for single user/realm too)
When a user logs out, I want to remove their content from the Realm and delete the Realm, because of security reasons.
The application heavily builds on the observation/notification feature of Realm.
Only the open source components of Realm are used (RealmSync not)).
I use RealmSwift 4.3.2 and RealmCore 5.23.8.

Steps
The issue happens when the user logs out, then logs back in during the same app session. When logout happens:

I invalidate my observation tokens via Realm invalidation
I delete all objects from Realm
I delete the realm db files with the static deleteFilesForConfigiration method (I tried only deleting object OR only deleting files, but the issue remains).

Next time the user logs in, I create the Realm with the following config (as every time before):

predefined file path with user name
deleteRealmIfMigrationNeeded set to true
objectTypes set to my RealmObjects,
shouldCompactOnLaunch has the condition of max 50MB and used/total bytes is under 70%.
I also set the schemaVersion (this might only change between releases, in this case it is not changing).

I see the following SIGABRT crash (Anonymised):
!!! IMPORTANT: Please send this log and info about Realm SDK version and other relevant reproduction info to<EMAIL_ADDRESS>APP_DERIVED_DATA/SourcePackages/checkouts/realm-cocoa/Realm/ObjectStore/src/shared_realm.cpp:433: [realm-core-5.23.8] Assertion failed: m_schema_version != ObjectStore::NotVersioned
0   AppName                               0x0000000105f72228 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 32
1   AppName                               0x0000000105f724b0 _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 236
2   AppName                               0x00000001059c752c _ZN5realm5Realm17set_schema_subsetENS_6SchemaE + 176
3   AppName                               0x0000000105afeb60 +[RLMRealm realmWithConfiguration:error:] + 1600
4   AppName                               0x0000000105b549ec $sSo8RLMRealmC13configurationABSo0A13ConfigurationC_tKcfCTO + 148
5   AppName                               0x0000000105b54b04 $s10RealmSwift0A0C13configurationA2C13ConfigurationV_tKcfC + 84

I tried to debug and understand how Realm creation works, what I can see:

Realm is heavily cached (In the RLMRealmUtil in a NSMapTable per file path per thread + also in the RealmCoordinators layer)
When I try to recreate the RLMRealm, it creates a new wrapper, set's the wrapped CPP realm::Realm from a RealmCoordinator cache, then uses a previously cached RLMRealm to setup its schema. (RMRealm.mm Line 479 set_schema_subset). At this point the cached CPP realm::Realm's schema version is Object::NotVersioned, which is strange.

When I call resetRealmState on RLMRealm the issue is not occurring, because both RLMRealm cache and the coordinator cache is cleared. Unfortunately this is only ok for me for a single user. When a second user is logged in, I would not clear the cache as I assume, everything stored as a weak pointer and that would render my application unresponsive for data changes.
To summarise this, I think this could be a Realm Caching issue.
Any help is much appreciated :)

@WiesnerPeti Thanks a lot for the analysis! It would be super useful if you could possibly reproduce this in a minimal test-app that you could share?

Calling invalidate does not actually close the Realm, so after deleting the Realm file and reopening it you have two different files open at the same path. We (incorrectly) assume that file paths uniquely identify files, and then hit an assertion failure in the first place where that assumption being violated matters. resetRealmState works around this by closing all open Realms, which obviously isn't a good answer if you want to be keeping other Realms open.
This specific assertion failure is probably pretty easy to fix, but you'd probably still run into more problems elsewhere.

What is your suggestion @tgoyne ?
I i know that invalidate won't close Realm, it just invalidates the objects (tokens, lists) managed by Realm (per documentation). As I learned Realm in other languages (like JAVA) has a close method, but on iOS it depends on releasing the strong references to the Realm.
An API similar to resetRealmState just for a single realm, would be great, I think.
I was able to create a test project. You can download it here.
Steps:

Set "Automatically manage signing" to build + add All Exception breakpoint
Run app
Tap on "Create" 2-3 times fast (see debug logs + crash)

Good news: I it will show the assertion failure. Bad news: It does not 100% similar the issue I have. In my original case, I use the new deleteFiles API, that won't delete actually the Realm files as the connection is open, yet my issue occurs.  In this case, I delete the Realm by hand, so @tgoyne 's  scenario happens.

Hi @tgoyne , @bmunkholm ,
what is the resolution here? Are you looking to improve on this or I should make sure all Realm strong reference is released?
Thank you for the answer in advance! :)

Hi @tgoyne , @bmunkholm
we are seeing increased crash rates due to this bug, can you please share an update on this issue? Did the sample project help?

@WiesnerPeti Really sorry about the lacking response here! I know tgoyne wanted to write up something for you, but he has been rather backlogged for a while. The gist of it is that until we can make this easier for you, you will have to ensure that you don't use a realm that isn't properly closed. tgoyne may be able to give you more hints on how to do that when he frees up.

@bmunkholm Thank you for the response :) Any additional hint is welcomed :)
I ended up revisiting our memory and thread management regarding Realm and I fixed the issue :) In our application, we not only disposed Realm, but also the threads the user's realm was used on. We recreated the threads with the same name once the user logged in. Maybe the thread with the same name, but different memory address (id) could mess with the internal Realm Cache?
Thank you very much for your help and advice!

Sounds like you got it fixed now then? But you also mention any hints are welcomed? So not sure if you still need help or we can close this issue?

Sorry for the misunderstanding:

Yes, my issue is fixed :)
In general, any (tgoyne) hints about how to make Realm properly close, is welcomed (on my side ) :)


Can't extract scoped npm package?

Laravel Mix Version: 2.1.11
Node Version: 9.11.1
NPM Version: 5.8.0
OS: macOS High Sierra (10.13.4)

Description:
It seems trying to mix.extract() a @scoped/npm-package doesn't work (results in Module not found: Error: Can't resolve)
Steps To Reproduce:

npm install @mobiscroll/javascript-lite
Write this in webpack.mix.js:

mix.setPublicPath('public')
  .js([
    'src/js/app.js',
  ], 'public/js/app.js')
  .extract([
    '@mobiscroll/javascript-lite',
  ], 'public/js/vendor.js');

npm run watch

Expected result
No error.
Actual result
 ERROR  Failed to compile with 1 errors                                                 3:47:29 p.m.

This dependency was not found:

* @mobiscroll/javascript-lite in multi @mobiscroll/javascript-lite

To install it, you can run: npm install --save @mobiscroll/javascript-lite
          Asset       Size  Chunks             Chunk Names
     /js/app.js     2.3 kB       0  [emitted]  /js/app
  /js/vendor.js  217 bytes       1  [emitted]  /js/vendor
/js/manifest.js    3.84 kB       2  [emitted]  /js/manifest

ERROR in multi @mobiscroll/javascript-lite
Module not found: Error: Can't resolve '@mobiscroll/javascript-lite' in '/Users/benface/Projects/project'
 @ multi @mobiscroll/javascript-lite

Am I doing anything wrong? Thank you for your time.

It looks like you haven't installed the dependency as the output suggest.
To install it run npm install --save @mobiscroll/javascript-lite
I use mix to extract scoped packages and it works just fine.

@SaurabhKharivale Thank you for replying. Can you give me an example of a scoped package that works fine with extract() so I can test it in my project on my machine? I confirm that I did install the package (it is in package.json and at node_modules/@mobiscroll/javascript-lite) and am still getting this error. I also tried extracting another scoped package, @angular/core, just in case the issue was with mobiscroll, and I'm getting another but similar error (Can't resolve 'rxjs/Observable'). Maybe not all dependencies can be extracted?

I use these packages and they work fine for me when extracting
@fortawesome/fontawesome
@fortawesome/fontawesome-free-solid

Thank you! It does work with these. So is there a problem with @mobiscroll/javascript-lite (and @angular/core for all it's worth) or is it a bug in Mix?

@benface Hello, were you able to fix the issue by any chance?

@petrorington No, I gave up. I still don’t know if it’s an issue with Mix or with some specific packages.

@benface I see. I have got a similar issue with ckeditor.
Anyway thank you for your note.


Rsync folders via ssh proxy if connected to remote hypervisor.

If controlling VMs on remote libvirt host, rsync to VM can fail if VM is not visible directly from our machine. This can be solved with ssh proxy. Remote libvirt host will act as proxy.

Closing due to supporting vagrants rsync and no comments on this for ~2 years; if this feature is still required please comment or open a new issue.


Fix doctor

Current dependencies on/for this PR:

main

PR #16

PR #17

PR #18   👈

This comment was auto-generated by Graphite.

Codecov Report

Merging #18 (3c8cd9a) into be-2916-fix-coveralls-on-elixir_app_gen (aa752f9) will not change coverage.
The diff coverage is n/a.

@@                           Coverage Diff                           @@
##           be-2916-fix-coveralls-on-elixir_app_gen     #18   +/-   ##
=======================================================================
  Coverage                                     0.00%   0.00%
=======================================================================
  Files                                           26      26
  Lines                                          679     679
=======================================================================
  Misses                                         679     679


[otp_ctrl] Update interface signals and LFSR reseeding

This aligns the IO signals of the OTP controller, and switches the EDN update interface for LFSR reseeding to req/ack. A 16bit counter is added to the LFSR timer in order to periodically requests entropy for LFSR reseeding from EDN.
Ssince the power manager feedback signals are defined in the pwrmgr_pkg, I had to update the "example design" version for this to work standalone (second commit).

Thanks for the reviews!