Variable register (master variable list)

Regarding the structure of the MIP_variables.json file, I think this should be consistent with what was proposed long ago in viewgraphs (see especially slides 17 and 18) and in more detail in sections 3 and 4 of this document.  Considerable thought went into the structure defined there and I think before agreeing to the format of the "variable register" or master variable list, we need to state what purposes we hope it will serve.
One purpose for putting all the variables together in a single file is that separating them into "tables" always will involve somewhat arbitrary decisions. (For example, what realm does surface temperature, "ts" belong in?  It's currently in "AP", but of course "ts" is not a property of the atmosphere but of the surface).   By putting them into a single table, the user should be able to easily look up the variable and determine what variants exist.  The number of different tables will certainly grow over time making their names more and more inscrutable.
Here's a use case:  If a new variable is proposed by a MIP, we should be able to easily check whether the variable already exists and what its current variants are (i.e., what frequencies and methods of sampling have been needed in past data requests).  In curating the “master list”, we will want to avoid adding a variable that already is in the list but perhaps sampled slightly differently.  For example, if someone wanted to add time-mean ua (wind) reported every 3 hours and modeling groups have for years been reporting 3-hourly winds synoptically, we want the person requesting the variable to say why they can't use synoptic rather than time-mean winds.  Only if they can justify doing something different from the norm should we allow the variable to be added.  The originally proposed JSON file structure makes it easy to avoid adding new variables when an existing variable would be acceptable.
The originally proposed structure has "standard_name" as the top level entry.   The standard names have been thoroughly vetted and precisely defined, so they provide superior identification of different quantities.   Under each "standard_name" are the prefixes used in constructing a branded variable name.  There is usually only 1 of these per standard name, but not always.  (Note that there are fewer branding prefixes than there were "outnames" in CMIP6 because some of the variations on outname are unnecessary when the full branded name suffix is used to uniquely identify a variable.  For example, ta500 and ta700 were outnames in CMIP6, but both of these can share the same branded name prefix="ta" because the pressure level is indicated by text in the suffix.) If tables are used to identify variables, we must either have multiple names for the same physical quantity or deal with an expanding number of tables.
In my spreadsheet of CMIP6 variables where I have successfully generated branded variables (and done much more than that), I determined that in CMIP6 out of the 2062 variables defined, there were 929 distinct standard names and 1081 distinct root names.  This means the levels of the proposed json file structure would include 929 items at the top level and for about 15% of these more than 1 prefix is needed, so most standard_names are served by a single root name and on average there are about 2 ways each of these has been sampled (e.g., both monthly and daily).  In fact most quantities are sampled in a single way, but a few are sampled in more than a dozen different ways.  It should be noted that there are more than 200 more CMIP6 outnames (1282?) than there are branding prefixes (1081?).  This is because, as mentioned above, in CMIP6 variables like ta500 and ta700 had different outnames but they will share the same branding prefix (ta).
The originally proposed structure of the json file groups together all variables representing the same physical/chemical quantity, as identified by the standard_name.  The meaning of the standard_name does not change from one CMIP phase to the next.  (This is in contrast to the variable “outnames” which have evolved and will continue to evolve over phases.)   Under each standard name, there can be multiple “prefixes” that distinguish among variables that aren’t identified uniquely by the branding suffix.  And under each of these, are the fully branded variables, which distinguish different ways of spatially and temporally sampling a variable.  Finally, nested further down is the list of frequencies for which the variable has been requested.
The json file currently in mip_cmor)tables does not guarantee that closely related variables will be found together.  It also continues the unscalable practice of relying on a table name as one of the primary identifiers of a variable.  As the number of tables grows, I think this becomes less and less acceptable.  I hope we don't go down a path that will have to be almost immediately corrected.  That would be confusing.
Hope to hear everyone's thoughts.  The structure proposed in section 4 of the document already referenced above is my attempt to establish a registry that will serve both short-term and long-term needs.  I'm sure that with everyone's input, it will eventually serve us well.

@taylor13 thanks for thinking this through and reading the links to the supporting docs. I'll try and pull some of this logic briefly into the CVs drop in slides

In November I shared by email this simplified simplified/updated version of the document mentioned above.  This new document shows how to create a master list of variables from the spreadsheet.  It should not be difficult to write a python code that would create a mip_variables.json file.
Among the advantages of the proposed mip_variables.json file over the current one are that the new one

organizes variables by "standard_name" at the top level which provides a better way to determine whether a variable already exists.
Allows new variables to be tentatively proposed and reviewed before acceptance (when the name status will change from "proposed" to "accepted"
transfers from the spreadsheet information that will help in reviewing/correcting the CMIP6 variables, including:

specific_issues I've identified with suggestions for how these should get revised going forward (see columns GX-HI of spreadsheet)
recording of the number of institutions that reported the variable
recording of the number of models that reported the variable

Moreover, I think it will better serve input4MIPs and obs4MIPs in that different (shorter) CMOR tables might be more easily defined for their special needs.
The whole new json file can, I think, be generated automatically from the spread sheet (after writing a simple python code).  Note that in the document just referenced There is a generic listing of items in the table followed by a specific example.  The spreadsheet column numbers are only shown in the first table.

As I understand it, the main 6.5.X.2 milestone is to develop a "Simple web interface to add new / explore variables."  Wouldn't it make sense to first write a simple python code to create the mip_variable.json file from my spreadsheet which includes all of my suggestions for changes?  I would think that would take a day or two to accomplish, but it would preserve all the work I've done and put us on track for the 6.6 milestones.

@taylor13 Yes it can be part of both. It  be useful to schedule a dedicated meeting where we figure out exactly to do with them and I can then get on with the work.

@wolfiex Excellent!  I'll speak to Paul and suggest a time to meet.  In the mean-time, I'd like to understand better what changes were made in going from the CMIP6 tables to the CMIP6plus tables.  This will affect what the most efficient way might be to proceed.  So some quick questions:

Is there a machine-interpretable mapping (perhaps in a json file) making it easy to determine what each CMIP6 <variable_id><table_id> corresponds to in the new CMIP6plus <variable_id><table_id>?  (e.g., how can I find which CMIP6plus table contains ta_amon?)
Have any of the 2062 CMIP6 variables been omitted from the CMIP6plus tables?
Have any changes been made to the metadata associated with each variable in the new tables, or did you just copy of the metadata from the old (CMIP6) tables?

Thanks.
Karl

@wolfiex great. To be honest, I think cleaning up the contents of the tables (including generating MIP_variables.json) is a far higher priority than a web interface to manage/add new vars etc - so I would toggle the milestones so that the currently labelled 6.5.x.x becomes a 6.6.1.x after we have our clean 6.6 version minted, and the deadline for the 6.6 is ~April, ASAP really. Content is more important than how we manage it.


doc: Update the list / status of builders / generators

Seems fine. Might be worth getting Kara to over the language a bit before a release is done.

Good point.


Migrating from SASS @import to @use & @forward

Description
When migrating the SASS from the deprecated @import statement to the new @use and @forward statements, no CSS is output to a file at all and there is no link tag in the index.html file.
You can see an example of this migration not working in this PR: https://github.com/RehanSaeed/rehansaeed.github.io/pull/268.
Steps to reproduce
Go to your src/assets/index.scss file which is imported in main.js with import "~/assets/style/index.scss"; and instead of using @import, switch it to use @use and @forward.
Expected result
CSS should be output as normal.
Actual result
There is no CSS file after running a build and no link tag in the HTML.
Environment
Paste the information here as shown by gridsome info
System:
    OS: Windows 10 10.0.21292
    CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
  Binaries:
    Node: 13.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 88.0.4324.182
    Edge: Spartan (44.21292.1000.0), Chromium (88.0.705.74)
  npmPackages:
    @gridsome/plugin-critical: ^0.2.0 => 0.2.0
    @gridsome/plugin-google-analytics: ^0.1.2 => 0.1.2
    @gridsome/plugin-sitemap: ^0.4.0 => 0.4.0
    @gridsome/source-filesystem: ^0.6.2 => 0.6.2
    @gridsome/transformer-remark: ^0.6.4 => 0.6.4
    gridsome: ^0.7.23 => 0.7.23
    gridsome-plugin-brotli: ^0.1.3 => 0.1.3
    gridsome-plugin-flexsearch: ^1.0.5 => 1.0.5
    gridsome-plugin-pwa: ^0.0.18 => 0.0.18
    gridsome-plugin-remark-prismjs-all: ^0.3.5 => 0.3.5
    gridsome-plugin-robots: ^0.2.1 => 0.2.1
    gridsome-remark-embed-snippet: ^1.0.3 => 1.0.3
    gridsome-source-static-meta: ^1.0.1 => 1.0.1

The issue is described very well in this blog post: https://carterbancroft.com/sass-and-webpack/
The solution is to switch from using the node-sass NPM package to https://www.npmjs.com/package/sass instead. Once you do this, everything works again. This should be the new default.

Thanks for finding a solution, @RehanSaeed. I see our docs here are suggesting node-sass. But I just noticed that the node-sass package is deprecated. So we should probably update the docs :)

This issue should be closed, as I have updated this section of the docs
https://github.com/gridsome/gridsome.org/commit/19695fd22c384630e27141f6dd64a7450d26d13c#diff-fdec52953e6fe8f7f51330dabed9be9891a38048b0e8e3e04c01f0088a4bb9be


Use a "src" directory?

I recently saw the rationale for using a "src" directory described in http://andrewsforge.com/article/python-new-package-landscape/ and was curious what you think.

this is another good reference https://blog.ionelmc.ro/2014/05/25/python-packaging/#the-structure

Use of src or not is 100% personal preference. It doesn't really matter. For example, neither Flask, Zappa, Django, Requests, Responses, Responders, etc use the src approach. It's a legacy of another time, nothing more.
Thank you for your consideration, but I'm closing this as a wontimplement.

I agree that it is a personal preference. But to say it "doesn't matter" and "legacy of another time, nothing more", is a curt reply to the question. There is a rational for the src-layout as discussed in several blog articles. Even pytest has a use case where they recommend it, https://docs.pytest.org/en/latest/goodpractices.html. Also, there is a long thread in PyPUG issue #320 on this topic. @jab was asking for the your opinion, I guess he got it.

My apologies if i came across as being curt. There are better ways forme to express my opinion. I'll try to do it better next time.

@pydanny, hope you're doing well. Just hit this issue again. Re your comment citing Flask as a counterexample, @davidism moved several of the Pallets projects (Flask, Jinja, Click, Werkzeug, etc.) to using a src directory a while ago. Not sure if you had time to read any of the links cited above, but they actually provide technical justifications for doing this, rather than it being 100% personal preference or nothing more than a legacy of another time. When I opened this issue, I was genuinely curious if you had any technical counterarguments to the rationale presented above, and I still am, in case you're interested to dig into this a little more. Thanks :)


update test and add logic to open ports

We need to manage the ports to be opened / closed based on the requested haproxy configuration. The opening/closing of ports will be done before applying the new haproxy config.

in ingress mode, port 80 and 443 will be opened and all other ports closed
in legacy mode, after generating the service definition, each port specified will be opened, all other ports are closed.
in default mode, only port 80 will be opened.

Exceptions related to opening/closing port will flow to the charm level and put the charm in an error state, therefore no validation is done (mainly regarding the legacy ports which can request any port value)
Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Managing Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

Labeling this to complex as we need to discuss whether to do validation for legacy ports, or let the exception flows.
Hi @gregory-schiano, can you take a look at this PR and review it when you have the time? Thanks!


Document somewhere the intent and distinction of Planet Cassandra (in comparison to cassandra.a.o)

Request came in

It would be incredibly useful if this intention was documented somewhere. That would allow both review of the overall intention and review of content against that intention which I think could significantly reduce the number and frequency of concerns being raised.

I'll come up with some draft text of this intent, and I hope we can find the right place to put it.

My first draft:
As community around the Apache Cassandra project, Planet Cassandra aims to compliment the wider ecosystem.
Planet Cassandra is a place where content from vendors or that promoting a vendor can be submitted.  Planet Cassandra also acts as an aggregator of existing external web content.
This makes it a facilitator to the broader ecosystem, and a place where commercial actors can be active where they otherwise cannot be within the project.  Formally, within the ASF projects only individual contributors are recognised to ensure a vendor-neutral and sustainable open source project, see The Apache Way for more on this.
Everything official and formal to the Cassandra project is found on cassandra.apache.org. This includes all documentation, technical blog posts (especially those from our committers), and information about approved events.
The Apache Cassandra project recognises that success of the project is bound to the commercial success of entities in its ecosystem, and in line with the ASF's commercially friendly but vendor-neutral ethos, embraces Planet Cassandra in this mission.

FYI @ramseur @pmcfadin @StefanVinica @allisonnokes

@michaelsembwever we will get this done asap

we added this on the contribute page

perfect. thanks @StefanVinica !

Ill push it to Prod by EOD


support for more fieldTypes and generating unique ids for the fields

depends on
#3
Test URLs:

Before: https://form-block1--nedbank--vdua.hlx.live/en/personal/borrow/personal-loans-form
After: https://form-block2--nedbank--vdua.hlx.live/en/personal/borrow/personal-loans-form

The review comments have been incorporated in #1 itself.


pure-rust via cfg("aegis_backend" = "..") vs cfg(feature = "..")

Hey thanks for working on this! Great stuff
Would you be open to moving the cfg(feature = "pure-rust") into as:
cfg("aegis_backend" = "libaegis" | "rust" | ..)
Happy to send a PR - ideally the selection is automatic but we provide "overrides" in curve25519_dalek f.ex.
We had extensive discussion over here re: features vs cfg when we bumped to curve25519 to v4:

https://github.com/dalek-cryptography/curve25519-dalek/issues/414

I would recommend having this mutual exclusive override as cfg due to;

Allows top-level binary composing the primitive as the overarching choice and transients not having any say
Transient dependencies don't need to "relay" it down - dalek itself (via ed/x f.ex.) long time didn't relay the overrides
The compiler / cargo has now taken official stance on it to support the pattern
Composes as mutually exclusive feature vs features are not mutually exclusive
Other issues discussed in the long winded ref'd issue

The compiler now supports validating cfg (requires high MSRV though so we've ignored it until MSRV is high enough)

https://github.com/dalek-cryptography/curve25519-dalek/pull/652
https://blog.rust-lang.org/2024/05/06/check-cfg.html

Ref:

https://github.com/RustCrypto/AEADs/issues/1

Hi!
I'm not fluent enough in Rust to understand the difference
However, unless it removes a bug that can't be addressed otherwise, or makes things faster, or adds a feature, what I really care about is avoiding breaking changes.
People should be able to update the library version without having to change anything to their code. This includes compiling to WebAssembly without requiring any special tweaks.
Maybe what you propose is just some internal changes that wouldn't change any user-facing feature. In that case why not. Rust has so many completely different ways to do the same thing.
The pure Rust implementation was added for people wanting to compile it to WebAssembly, that don't necessarily have a WebAssembly C compiler installed. But it's incomplete and maintaining two implementations in the same project is not fun. So, the plan is rather to precompile libaegis as a webasssembly module, and just link it on that platform, as done by other projects. So that all platforms can share the same code.
If you need to cross-compile to a target that isn't supported by cargo-zigbuild, or don't have a C compiler for some reason, crypto-rust has all the AEGIS variants implemented in pure Rust. It's better than the Rust code we have here.


Inconsistent: Integers vs Strings in Array of Network Objects

Schema version 1.6 states the network port objects are arrays of string, the Cobalt Strike Sighting has integers in the Behavior section.

          {
            "behavior": "DLLHOST performed hundreds of network connections to local network",
            "id": "ced277c3-f68a-42b5-b153-55e1983d17ec",
            "type": "Network Accessed",
            "protocol": "tcp",
            "dstIp": [
              "#{PRIVATEIP}"
            ],
            "dstPort": [
              445
            ],
            "srcPort": [
              "#{high port number, eg. 63794}"
            ],
            "parentProcess": "C:\\\\Windows\\\\System32\\\\dllhost.exe",
            "att&ck": {
              "discovery": [
                "T1046 - Network Service Scanning"
              ]
            }
          },

    - behavior: DLLHOST performed hundreds of network connections to local network
      id: ced277c3-f68a-42b5-b153-55e1983d17ec
      type: Network Accessed
      protocol: tcp
      dstIp:
      - '#{PRIVATEIP}'
      dstPort:
      - 445
      srcPort:
      - '#{high port number, eg. 63794}'
      parentProcess: C:\\Windows\\System32\\dllhost.exe
      att&ck:
        discovery:
        - "T1046 - Network Service Scanning"

Inconsistency in TA551
In TA551 Sighting the connections array has network ports as integers.
    - behavior: MSHTA connected to public server via HTTP
      id: 68c2a8a7-cc23-4367-9001-2875b0ad08f4
      type: Network Accessed
      connections:
        - dstIp:
          - 45[.]144.29.211
          url: http://wilkinstransportss[.]com/bdfh/M8vW0wEDKC/13990/98945/78577/UqmtFoUgSxQJgcBW2fbvUZ2w7h9ymtYJSptD/sumej1?m4m=uGAi7rUeR3HcNJNavdx&cid=LtbWPeO8zSCYlRGIYaA4Nf&H4PX=6Qrvk6oCdF49I89tjCSo&time=h9tCXQxzNuY1C4oJM4SS7q1cYDVUb
          dstHost: wilkinstransportss[.]com
          protocol: tcp
          dstPort:
          - 80
          userAgent:
          - "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)"
          method: GET
        - dstIp:
          - 80[.]92.206.122
          dstHost: steptransport2017b[.]com
          protocol: tcp
          dstPort:
          - 80
          userAgent:
          - "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; HCTE; Zoom 3.6.0)"
          method: GET

Fixed. The documentation was wrong. Port field is an integer (Array integer). We will modify the documentation as soon as possible.
However, in the case of Cobalt Strike Sighting, we are giving an idea about the use of elevated ports with variables (#{var}). We have removed the string and we have put that information in the notes section.


stl.py not python-3.4 compatible

I've installed numpy-stl with pip3 for python-3.4 and pip for python-2.7
The following code works with python 2.7:
from stl import mesh
But with python-3.4 I get the following error:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.4/dist-packages/stl/mesh.py", line 1, in <module> from . import stl
File "/usr/local/lib/python3.4/dist-packages/stl/stl.py", line 49
 except RuntimeError, (recoverable, e):
                    ^
SyntaxError: invalid syntax

Editing line 49 to except RuntimeError (recoverable, e): removes the error and put another one:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.4/dist-packages/stl/mesh.py", line 1, in <module>
    from . import stl
  File "/usr/local/lib/python3.4/dist-packages/stl/stl.py", line 155
    except AssertionError, e:
                         ^
SyntaxError: invalid syntax

Python 3 is indeed not working yet, I'll add it to my todo but it's slightly more work than I had hoped :(

I did a test with 2to3.
$> 2to3 --output-dir=numpy-stl-3 -W -n numpy-stl-1.4.2
This seems to go a long way towards the changes needed. After doing this I could use pip to install the package and import it. Interestingly, the utilities work in one direction:
This works fine:
stl2ascii mybinary.stl myascii.stl
This fails:
$> stl2bin myascii.stl mybin.stl
Traceback (most recent call last):
File "/home/matt/anaconda3/bin/stl2bin", line 9, in
load_entry_point('numpy-stl==1.4.2', 'console_scripts', 'stl2bin')()
File "/home/matt/Downloads/test23/numpy-stl-3/stl/main.py", line 80, in to_binary
update_normals=not args.use_file_normals)
File "/home/matt/Downloads/test23/numpy-stl-3/stl/stl.py", line 198, in save
write(fh, name)
File "/home/matt/Downloads/test23/numpy-stl-3/stl/stl.py", line 227, in _write_binary
fh.write(struct.pack('@i', self.data.size))
TypeError: must be str, not bytes
Obviously, this must be to the changes in string and byte handling in python 3. Would love to help more, but I'm not an expert.

That's indeed the problem I ran into, it's not impossible to fix but it's just taking slightly more time than I have right now :)
Still a work in progress though.

ok, if I end up doing any more work on it for my application, I will try to post my findings here.

I've just committed a few changes to make it slightly better, but something is fundamentally different in how py3k handles things, just try and run the test suite and you'll see that something is a bit weird :)

I've just released version 1.5 which has Python 3 support as well as Python 2 support :)


support AC3 and E-AC3

Hello,
this PR supports Linux x64 only.
Source: https://github.com/Muril-o/electron-chromium-codecs/tree/main/v20.1.1
Cheers
midzer

hacktoberfest-accepted


Move compute method to dart sdk

I followed https://flutter.dev/docs/cookbook/networking/background-parsing to parse json network responses to dart objects in a separate isolate to avoid ui jank, i.e. I now use compute() to spawn an isolate which parses the data after it has been received from the network. So far, so good.
However, the network call and parsing should be part of a library that is pure dart without dependencies to the flutter sdk. Thus, my proposal would be to move the compute method into the dart sdk instead of providing it in the flutter sdk so that pure dart libraries also have access to it.
Are there other dependencies to the flutter sdk that the compute method currently has that would make this difficult?
In the meantime, how can I replace the compute method with a pure dart method?
Should I use IsolateRunner.run from the isolate package? Are there disadvantages when using IsolateRunner.run instead of compute in flutter?

However, the network call and parsing should be part of a library that is pure dart without dependencies to the flutter sdk

If you want to discuss additions to the dart-sdk, it would be better to raise an issue on https://github.com/dart-lang/sdk. The flutter team, to note, is perfectly happy with the functionality as is.


err BSON

{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version
The magic happens on port 8080
events.js:141

bad read documentation

close

wait, how did you fix it?

@abebraham updating your mongoose dependancy to the latest version should do the trick 😉


Refresh option for search results preview functionality

It would be good to have an option to refresh the search preview results. Typically we see the source MD and the search results preview side by side. Currently, if I update the metadata title, I need to close the search preview and reopen it. Refresh functionality would be much better.

AB#299672

It appears we do have an automatic refresh when updating metadata title for search results preview. After some testing it seems to work based on the title metadata in the yaml-frontmatter in the markdown file and not from the H1 tag. And although there is a slight delay maybe 2 seconds, it seems to automatically refresh. Maybe more details can be provided and I cant test with a specific file to see if there is a bug or issue that I can repro. I tested in azure-docs-pr with a cosmos-db markdown file.


your apprise webpage doesn't work

Error message [404] 404 Not Found for thrivingkings.com/apprise/ port 80

Thanks for the note! My hosting company appears to have be down. I'm working on switching this over to a better environment


1033 abandoned indicator player sumary

fixes #1033
This should address this issue.

The issue with party_size should be fixed and show up in future matches.  Do you want to put that change in this PR as well?

Yes, I'll do that. Thanks!
On Sun, Jul 30, 2017, 1:10 PM Howard Chung<EMAIL_ADDRESS>wrote:

The issue with party_size should be fixed and show up in future matches.
Do you want to put that change in this PR as well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/odota/ui/pull/1092#issuecomment-318919125, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGjCgozvsIczOPpbTEH6axUowvx0uAkaks5sTMcKgaJpZM4Ono4i
.

@blukai Not sure how to respond to this. Is this a request to shrink them? How much would seem not too big to you?

@blukai Great feedback! I've updated my code to fit better with your suggestions.


Platform Expection(Stale Token)

I keep getting this error on initializing my flutter application
[keycloak_wrapper] PlatformException
(PlatformException(token_failed, Failed to get token: [error: invalid_grant, description: Stale token], null, null))

Can you provide more context into this issue?

I keep getting this error:
AssertionError ('package:keycloak_wrapper/src/wrapper.dart': Failed assertion: 'isInitialized': Make sure the package has been initialized prior to calling this method.)
Below I have also attached a screenshot to it looks like.

It means you didn't initialized this package inside your main method but this error is different than the previous one. 🤔

If you truly follow the example, then your Keycloak configuration is probably wrong. Double check your given values and also check your Keycloak Admin Console settings too.

I tried the first option. Same thing.
For the example, I replaced the Configuration with my values (Bundle ID, Realm, Client ID...).
Same Error.

Would u mind to give me your Keycloak configuration values so I can double check it?

Here you go:
    bundleIdentifier: 'com.issl.test',
      clientId: 'flutter-cli',
      frontendUrl: 'https://keycloak.issl.ng',
      realm: 'Testing',

It's a Token thing. I was able to clear the cache & restarted the App.
Thank you.


Pushthis Implementation

I have created a Pusher clone and charging 50% less as Pusher is ridiculously expensive; Just about into beta for it. Wondering if I can do a pull request and add in my Laravel package to this once the beta is live.
My package doesn't use Laravel broadcasting, so you can send data from a controller, trait or an event!
Use Pushthis\Pushthis;

$pushthis->send([
            'channel' => 'example-channel',
            'event' => 'example-event',
            'data' => [
                'message' => 'Hello World'
            ]
        ]);

.env
PUSHTHIS_KEY
PUSHTHIS_SECRET
PUSHTHIS_NETWORK

Great work with Pushthis! Sending a PR to this effect won't be accepted as the laravel-chat project was specifically made for Pusher. However, you are free to fork the project and add your implementation with Pushthis.


Switch spanner datastore to use the built-in stats table for estimating rel count

While this will be far less accurate of an estimate, it removes the need to write to a stats table on every write and delete, which should help with performance

Updated


Add fail test

Error upload file .svg : $mimeType == Null (\yii\validators\FileValidator::validateExtension)
FileValidator: [extensions] => ['svg']
Error after upload: "Only files with these extensions are allowed: svg"
~/www/yii2$ vendor/bin/phpunit tests/framework/validators/FileValidatorTest.php
PHPUnit 4.8-dev by Sebastian Bergmann and contributors.

.......F..............

Time: 75 ms, Memory: 6.75Mb

There was 1 failure:

1) yiiunit\framework\validators\FileValidatorTest::testValidateMimeTypeMaskValid with data set #0 ('test.svg', 'image/*')
Failed asserting that false is true.

/home/GURTAM/zibr/www/yii2/tests/framework/validators/FileValidatorTest.php:358
/home/GURTAM/zibr/www/yii2/vendor/phpunit/phpunit/phpunit:35

FAILURES!
Tests: 22, Assertions: 71, Failures: 1.

That happens because file's mime type is text-plain.
# > file --mime-type test.svg
test.svg: text/plain

When I try to upload your test file via web form, browser sends the following data:
------WebKitFormBoundaryBMShRGnGSB5cL0nu
Content-Disposition: form-data; name="TestForm[file]"; filename="test.svg"
Content-Type: image/svg+xml

So we can say the Chrome makes it possible to handle SVG uploads correctly. But it does not work for saved file. Unfortunately, the problem is out of Yii framework scope.
Thank you for your report!


Feature/14 update formatting

cleanup the remaining files
removed trailing spaces
format according to black
update pipfile and settings for vscode environment

close #14

the codacy issue will also be addressed in #19


In Blazor creating the Same Element Multiple times in DOM.

Is there any possibility of appending the same element multiple times in the DOM. I have tried this below case.
<button @onclick="clicked">Update DOM</button>

@if(rendered) {

Showed in DOM

 }

@code{`

     private bool rendered { get; set; } = false

     private void clicked() {
        this.rendered = true;
        this.StateHasChanged();
     }
}

In this case the same element is not appended in the DOM for multiple times. Any solution for this ?

@Indrajith-Sync thanks for contacting us.
You don't need to call state has changed yourself. Blazor re-renders the entire UI and updates it based on the changes from the previous render (if any).
In your case you are simply rendering a single element conditionally, so that's what you will get. If you want to render multiple elements you would have to do something like keeping a counter of elements to render and writing a foreach loop for them.
<button @onclick="clicked">Update DOM</button>

@foreach(var index in Enumerable.Range(0,elementsNumber)) {

Showed in DOM

 }

@code{`

     private int elementsNumber { get; set; } = 0

     private void clicked() {
        this.elementsNumber++;
     }
}

Thank you for your suggestions...! @javiercn


pids and ets ids leaks

3> f(Pid1), f(Pid2), [Pid1, Pid2] = [erlang:spawn_link(fun() -> receive _ -> ok = folsom_metrics:new_histogram(<<"sorry">>, slide) end end) || _ <- lists:seq(1, 2)].
[<0.45.0>,<0.46.0>]
4>  Pid1 ! Pid2 ! sorry.
sorry
5> supervisor:which_children(folsom_sample_slide_sup).
[{undefined,<0.49.0>,worker,[folsom_sample_slide_server]},
 {undefined,<0.50.0>,worker,[folsom_sample_slide_server]}]
7> ets:tab2list(folsom_histograms).
[{<<"sorry">>,
  {histogram,slide,{slide,1028,20506,<0.50.0>}}}]

I expected that there would be only one child of folsom_sample_slide_sup. So the second child and its  ets are leaked.
supervisor:count_children(folsom_sample_slide_sup) =/= erlang:length(ets:tab2list(folsom_histograms)).

metrics with the same leaks:

history
spiral
duration

Folsom has moved, please resubmit your issue at https://github.com/folsom-project Thanks!


fix: redirect to a proper page from reconciliation account page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/46083
PROPOSAL: -
Tests

PREREQUISITES: You need to have Expensify Card and accounting connection enabled. If you don't have any connection enabled, comment out this line: https://github.com/Expensify/App/blob/c486e5627d3787ee7355a120e6d87002ad1ba6e0/src/components/ConnectionLayout.tsx#L132
and then you can access the page by adding '/settings/workspaces/[workspaceID]/accounting/[connection]/card-reconciliation/account` to the base url

Go to Workspace > Accounting > Connect to Sage Intact
Go to Card Reconciliation > Turn toggle ON > Click on "Expensify Card Settlement Account" Link
Verify that you're redirected to a proper page

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

same as above

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes

[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)

[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

https://github.com/user-attachments/assets/44f83054-9fe2-4a7d-9002-9e77d57192a9

iOS: mWeb Safari

https://github.com/user-attachments/assets/cb26dcbb-cf61-4966-a5e3-9b7c42e9f928

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/9d3cc585-2e15-4ca5-b95c-8351195a5ee3

MacOS: Desktop

https://github.com/user-attachments/assets/326129b7-1713-4d86-86a3-d52d52f2f284

opening but I couldn't test on Android - emulator doesn't want to cooperate 😅

@DylanDylann not yet :/

@allgandalf not yet :/

@allgandalf I can help @koko57 to test on the Android emulator. The video will be ready soon 😄

aaah sorry for tagging you @DylanDylann! and thanks a lot!!! ❤

https://github.com/user-attachments/assets/48d6cc94-2050-4d26-9934-1517e2dc45ca
@koko57 @allgandalf  Working well for me

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.17-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.17-2 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.17-2 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.17-2 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


get fullName() doing endless loop

I dropped a console.debug() inside the get fullName() function while testing out something else and I noticed that it loops endlessly, even if the values of firstName and lastName don't change.
get fullName(){
   console.debug('fullname');
   return `${this.firstName} ${this.lastName}`;
}

there's a comment above the fullName property that explains what is happening and what you can do to resolve it:
https://github.com/aurelia/skeleton-navigation/blob/master/src/welcome.js#L8-L14
  //Getters can't be observed with Object.observe, so they must be dirty checked.
  //However, if you tell Aurelia the dependencies, it no longer needs to dirty check the property.
  //To optimize by declaring the properties that this getter is computed from, uncomment the line below.
  //@computedFrom('firstName', 'lastName')
  get fullName(){
    return `${this.firstName} ${this.lastName}`;
  }

Ah, I see. And what would be the advantage of not including @computedFrom every time and leaving it to loop for ever?

Excellent question-
It's a judgement call.  Sometimes dirty checking isn't going to add any measurable overhead (as in this case).  Other times it can cripple your app's perf.
@computedFrom's use is pretty limited.  It only works when the computed property's dependencies are defined on the same object as the computed property.  You may have no choice but to use dirty-checking in some scenarios.

Closing this now that we have computedFrom


Handling of server header responses with carriage return \r (IE11)

Hi, this is a copy of the closed #422
I hope I can deliver a better explaination later on when speaking to the backend fellows I work with, but the core problem seems to be that some of our pages returns response headers with carriage returns or something (they all look simular but the result differs).
Line 374 in fetch.js
preProcessedHeaders.split(/\r?\n/).forEach(function(line) {

makes the normalizeName throw an error
If I change it to
preProcessedHeaders.split('\r\n').forEach(function(line) {

The result looks the same and works again.
This might be a problem in our application that sends weird headers but you might want to check it out, again? =)
Regards Per

The problem with IE11 is that it doesnt handle split with regex correctly. I was able to add in a pollyfill for split() to handle the regex correctly.
Split polyfill: https://gist.github.com/slevithan/2048056

This is discussed in #748.


Enable retries by default

Retries are now enabled by default!  They are configurable via the service config, as described in https://github.com/grpc/proposal/blob/master/A6-client-retries.md.
Caveats:

Transparent retries are not yet implemented.  That will be coming in the near future.
Hedging is not yet implemented.

IMPORTANT NOTE: The gRPC C++ API requires that the application call Finish() before unreffing the call.  If your application is not doing this, use of the retry code will cause memory leaks.  In this release, the memory leak will occur only if retries are configured via the service config.  However, in a future release, when we implement transparent retries, the retry code will be used for all calls, so this will affect all applications that fail to call Finish().  All gRPC users are advised to make sure that their code is calling Finish() on every call.

This change is

This now includes the changes from #26789.

This now includes the changes from #26803.

(Subscribe)

@yashykt, can you please review this?  Donna reviewed it already before she left town, but I've made a few more changes since then.  Thanks!

Most of the changes to this PR have now been split into #26838, #26839, and #26840.  Those will all be merged before this PR is merged, so the only changes in this PR will be directly related to enabling the retry filter by default.

This PR now contains only the changes to enable retries by default.

Known issues: #24204 #26595
The "Bazel C/C++ Dbg MacOS" test is an infrastructure failure.


Hyper link text.

The second behavior link text is confusing consider updating it to match the intent, Behavior.

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

ID: 065e1a1e-af92-486c-78d0-a457876e9074
Version Independent ID: 72d03409-d9fa-30b8-6f9d-8cf0c9f81bc3
Content: Introduction to Behaviors - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/behaviors/introduction.md
Service: unspecified
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

@jfversluis fixed this for us! Thanks for noticing.


[Feature]: Add a monospace font

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
It would be useful to be able to display text using a monospace font, such as courier, as it would allow text in the Text widget to be aligned
Why should this be worked on?
I have this text which is the output of a javscript function: https://i.imgur.com/jg72MRa.png
But as none of the fonts available in appsmith are monospace it displays like this: https://i.imgur.com/gu6ftnB.png

@cwarnock have you considered using a different output formats, e.g. a table?

I want this feature too. Sometimes I want to display some formatted texts on the interface, like a code snippet or a simple image composed of characters. A monospace font can help a lot.

Will fixed this here https://github.com/appsmithorg/appsmith/issues/20365


[GOBBLIN-881] Add job tag field that can be used to filter job statuses

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-881

Description

[x] Here are some details about my PR, including screenshots (if applicable):

With multi-dataset support in gaas, it is more convenient to have an extra field that can be used to filter when querying the job status (this would be dataset name in most cases).
This PR allows jobs to include job.tag field then when querying jobStatus, specifying tag in the query will return only job statuses with that tag.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Updated test

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@arjun4084346 please review

Codecov Report

Merging #2735 into master will increase coverage by 0.01%.
The diff coverage is 30.76%.

@@             Coverage Diff              @@
##             master    #2735      +/-   ##
============================================
+ Coverage     45.04%   45.05%   +0.01%
- Complexity     8751     8752       +1
============================================
  Files          1884     1884
  Lines         70311    70318       +7
  Branches       7716     7718       +2
============================================
+ Hits          31672    31685      +13
+ Misses        35697    35692       -5
+ Partials       2942     2941       -1

Impacted Files
Coverage Δ
Complexity Δ

...pache/gobblin/configuration/ConfigurationKeys.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../org/apache/gobblin/metrics/event/TimingEvent.java
70% <ø> (ø)
15 <0> (ø)
:arrow_down:

...gobblin/service/monitoring/JobStatusRetriever.java
0% <0%> (ø)
2 <0> (ø)
:arrow_down:

...org/apache/gobblin/service/FlowStatusResource.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...g/apache/gobblin/service/monitoring/JobStatus.java
22.22% <0%> (-1.31%)
4 <0> (ø)

...ervice/modules/orchestration/TimingEventUtils.java
95.65% <100%> (+0.19%)
4 <0> (ø)
:arrow_down:

...a/org/apache/gobblin/service/FlowStatusClient.java
72.34% <100%> (ø)
7 <0> (ø)
:arrow_down:

...obblin/service/monitoring/FlowStatusGenerator.java
74.19% <40%> (-7.95%)
11 <4> (ø)

...ache/gobblin/couchbase/writer/CouchbaseWriter.java
66.27% <0%> (-2.33%)
11% <0%> (ø)

.../org/apache/gobblin/metrics/RootMetricContext.java
78.12% <0%> (-1.57%)
15% <0%> (-1%)

... and 6 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c358719...b9c81ea. Read the comment docs.

+1 LGTM.

@sv2000 please merge


Support multiple primary keys in schema. Fixes #280

I will resubmit a version of this against latest.

At some point it seems like you guys had multiple primary key support and then someone pulled it out.  Any chance to get this put back in?  I can create a pull request if required although it should be pretty similar to what was proposed here:  https://github.com/oysteinkrog/SQLite.Net-PCL/pull/160

Yup, also have my own imp here https://github.com/softlion/SQLite.Net-PCL

At first I was against composite PKs, but after reviewing the changes needed - I guess we could do them.


How to project 3D BBoxes from prediction to 2D BBoxes ?

Anyone can show me how can I project 3D BB from prediction to 2D BB accurately way?

I have the same question

@Bynow76
Hello, I figured out the solution. When you do the projection: 3D coordinate project into the image plane [8, 3] --> [8, 2], after that find the min, max value along each column so that this rectangle will cover the object.
import torch
Coord_3D = torch.tensor(
[[672.59971903,<PHONE_NUMBER>4],
[654.37659384,<PHONE_NUMBER>7],
[6585.47537053,<PHONE_NUMBER>9],
[677.84173596,<PHONE_NUMBER>4],
[672.59971903,<PHONE_NUMBER>4],
[654.37659384, 1.11569124],
[658.47537053,<PHONE_NUMBER>8],
[677.84173596,<PHONE_NUMBER>1]])
Coord_2D = torch.cat([torch.min(A, dim=1)[0], torch.max(A, dim=1)[0]], dim=1)
print(Coord_2D)

thanks a lot!


Fix ToC height

Example page: http://docs.codacy.com/repositories-configure/codacy-configuration-file/#which-tools-can-be-configured-and-which-name-should-i-use
Before:

After:

This is a great fix! :ok_hand:


Add a parameter to the request to support postback to the url

For our use case, the form is a formal document representation of other functionality, as such, there is no need for the overhead of having a static form page created for each instance. Preferable would be to have a template url that can consume a json payload via POST, render the form with the mapped in data, and then pass this data via the same request to pdf bot - basically thinking of having a 3rd optional parameter called formdata, an arbitrary object blob, and having a value in this field changes the request to a post.
This is so compelling for us vs having to instantiate every form prior to making the pdf-bot request, that I may end up forking and implementing, if you are at all interested in a PR...

Closing this upon digging into the code - I see that a) html-pdf-chrome would have to change for what I'm asking, and b) html-pdf-chrome supports data urls - this gives me an easy way to stage the requests to get what I'm asking for - still will be 2 requests, but no need for intermediate doc identity / storage which is really what I'm after


How can i delete/insert/update item in PageListAdapter item forward by PageList not by room

/* Remove this comment
Reporting an issue with the Architecture Components or the samples?
Question about Architecture Components?
If you want to ask how to do something, or to understand why something isn't working the way you expect it to use Stack Overflow. Post your questions using these tags:

Questions about the architecture guide or using components together: android-arch https://stackoverflow.com/questions/tagged/android-arch
Questions about the Room library: android-room https://stackoverflow.com/questions/tagged/android-room
Questions about the Lifecycle library: android-arch-lifecycle https://stackoverflow.com/questions/tagged/android-arch-lifecycle

Bug report or feature request for Architecture Components?
If you find an issue with the Architecture Components libraries or consider that a feature is missing, report it using the Google issue tracker: https://issuetracker.google.com/issues/new?component=197448&template=878802
Before filing a new issue, please check if it is listed in the Release Notes or reported in the issues list.

Release Notes: https://developer.android.com/topic/libraries/architecture/release-notes.html
Issues list: https://issuetracker.google.com/issues?q=componentid=197448 status:open&s=modified_time:desc

Issue with the samples?
Please add the sample name ("all", "GithubBrowserSample", "BasicRxJavaSampleKotlin", etc.) and include it in the title if it applies.
*/

Generally, this is what the invalidate API on your DataSource is for. You can file feature requests or issues with Paging on the Paging issue tracker.


Remove ~ sign on the routing page.

From Makoto San:

we should remove the ~
also cap it to 2 decimals

And also now it's capped to 1 decimal, we need 2


Allow to control where prose indent is applied

Defining a prose.indent property causes the first line of every paragraph indented. However, in books that first line indentation is often skipped for the first paragraph after a heading, table, image, i.e. if the preceding content element is not a paragraph in turn.
It would be nice if one could choose between these application modes of the setting.

Can you point me a book that uses this style so that I can study it?

Does this help?

Can you cite which book that is an in which reader you are using to view it?

I found two references for this rule, which seems to be called "full out indent".

https://selfpublishingadvice.org/10-typesetting-rules-for-indie-authors/
https://www.louiseharnbyproofreader.com/blog/when-to-indent-text-laying-out-narrative-and-dialogue-in-fiction

Both Chicago and APA require the indentation on the first paragraph, so there are clearly two styles.
As far as the code is concerned, we do have the ability to check if the previous sibling is a paragraph, so technically its possible to support. Though we do need to decide how this is going to be expressed in the theme. To keep with the CSS theme, we could using something like prose_first_of_group_indent which would allow you to zero it out for the first paragraph in a sequence of paragraphs. The other option would be to focus on the indent key itself, such as prose_indent_style: full-out.

I also found this reference on MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/text-indent#skipping_indentation_on_the_first_paragraph

Here's what I propose. If prose-text-indent is set, then it is applied to every paragraph. If prose-adjacent-text-indent is set, it is only applied to a paragraph that follows an adjacent paragraph.
prose:
  margin-inner: 0
  adjacent-text-indent: 10.5

Does that sound reasonable?

Thanks for all this research, Dan. Happy to let you decide here, as you're by far more intimate in how the inter-relationship of configured properties works in other places already.

Thanks for the feedback Oliver.
I was thinking that since we use the term "inner" to refer to the margin between adjacent paragraphs, we should stick with that terminology here as well. That could help make the key more intuitive.
prose:
  margin-inner: 0
  inner-text-indent: 10.5

Unless there is an objection, I'll move forward with this proposal.

When coming back to this with fresh eyes, I realized that the placement of the "inner" keyword is not consistent between the two terms, which could be confusing. I propose making it parallel:
prose:
  margin-inner: 0
  text-indent-inner: 10.5

The inner qualifier means it only applies at the intersection of two adjacent paragraphs.

I can confirm this now works as expected. Happy to adjust configuration property name as you see fit.

That looks great! Thanks for sharing!

I have a tiny follow-up for this one: Asciidoctor Bibtex extension renders each entry as paragraph, which now causes all entries but the first one to be indented (see below). I fully understand why it renders the way it renders and am afraid that it's hard to fix without Bibtex fundamentally changing the way it renders the entries.
Do you see a short-term workaround accidentally?

As I've expressed before, asciidoctor-bibtex should be generating the bibliography as a list, not as separate paragraphs. If that extension were producing a list, you would not get this behavior.

Using asciidoctor/asciidoctor-bibtex#84 as a hacky workaround for now.


[BUG] /arccot does not work

Description
\arccot shows in red instead of showing arccot regularly.
To Reproduce
use !dm to create a math block
enter \arccot
Expected Behavior
\arccot shows in red in the preview
Additional Info

Windows
Both Latex Suite 1.8.3 and 1.8.4 exhibits this issue.

Also, arccot does not autocomplete to \arccot but arc\cot instead, while \arccot autocompletes to \arc\cot.

This is a LaTeX thing; arcsec, arccot and arccsc are not native LaTeX commands. You would have to use something like \text{arccot} \right($0 \left) $1 for an arccot shortcut, or just \text{arccot} \right( \left) for some LaTeX code.

Thanks a lot!


🐞 Bug : Changes in Pop-up after adding, mentors and members

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When adding members/ Mentors to the group, when there are 0 invalid emails, the notification pop-up shouldn't mention about it,
It should only tell about how many members added.
Steps To Reproduce

Go to Groups
Add Mentos/ Members. (All valid emails)
See the Notification pop-up on the screen.

Expected Behavior
The pop should read  "All users are valid and were added successfully"
Screenshots

Device Information [optional]
- OS: Windows
- Browser: Chrome

Additional context
No response
Are you working on this issue?
Yes

@Kiran-pande-30 can you please assign me this issue

@saloni0419  Only Maintainers of the Repositories can assign issues to the contributors.

@Kiran-pande-30 @saloni0419  After reviewing the issue, I believe I've found a potential solution. If you could kindly direct your attention to app > helpers > utils.rb, specifically around line 31, there seems to be a spot where we can address this concern.

@Kiran-pande-30 you can work on better response messages

@tanmoysrt suggestion for the Issues Figma Design

this is the response of covering of the cases inviting group members and mentors. Working on further response message


Docs and test workflow

As proposed in https://github.com/exercism/xelm/issues/23, I copied the elm-package.json file to each exercise directory and updated the docs to reflect this change.
I also adapted the TESTS.md from the exercism/xgo repo. I'm going to throw something in ABOUT/LEARNING/RESOURCES docs as well, but I wanted to get this up for your perusal @parkerl

Eh... fixing up the travis test...

Turns out it takes a lot longer to run through the CI tests with this elm-package.json per exercise scheme (~20min vs 5-7!). I put the root elm-package.json file back and reverted my changes to build.sh. It'll mean needing to add the slug/path to both the config.json and root elm-package.json, but only as a one time thing.

@parkerl I think this should be good to go now. If this approach works for you, I'll update and PR all of the exercises I have queued up.

Thanks @tgecho! I want to give these changes a good look which I haven't had time for yet, but looks great at first glance.

Sounds good!


Changes needed to fix autofill context menu position

Changes needed to fix https://github.com/brave/browser-laptop/issues/3359

cc: @darkdh @bridiver

Once this is approved and merged, we can rebuild our prebuilt electron and then accept this PR:
https://github.com/brave/browser-laptop/pull/3389

++


Implement Simple Features in Shuffle - Play Random YouTube Songs

I have few ideas left to implement in my webapp. If you're interested, have a look.
https://github.com/amitness/shuffle/issues
You're also free to suggest new features. Let's discuss and implement it. Please open a issue for discussion.

hi, if you want, i can help you with some features

@maur3s Sure. What are the features you're interested in?

Hi @studenton ,  Can you share a documentation or something about this project to analyse it. Actually I am new to open source projects and i am pretty inexperienced  in this open source stuffs.

@Asutosh989 I can help you along the way. Please have a look at the code once and tell me the areas you're having trouble understanding.

@studenton  I have some problems in understanding the js files as I have started learning js and nodejs recently. Can i contact u over slack or email or something of that stuff so as to discuss the issues.

@Asutosh989 Sure. Here's my email<EMAIL_ADDRESS>

I am interested and want to contribute

@omokehinde Great. What do you want to work on?

hi studenton, sorry if i'm late!
i think that one of best features of your shuffle is a button to skip actual song and go to next one.

@maur3s Actually, it's implemented already on the site: https://studenton.com/shuffle. There is a button called Reload on the navbar.

I've seen it, but i'm talking about something that allow you to go forward and back into my random playlist.
I'm thinking about two buttons like << and >>, but you must save last 10 or 20 songs to allow you to go back.
i hope i can explain my idea!

@maur3s Understood. I got a rough idea how it could be implemented. Currently, we choose a song based on its index in the playlist. See this line. So for forward and back, if you can increase or decrease the index, you'll get the previous and next song in playlist.
But since a playlist has a max number of items, which is given by playlist.max in Line 18, so it has to be between 0 and that maximum value. We can do something like (index + 1) % max or (index-1) % max to confine it within that range.
Do you want to try to implement this?

@maur3s Any update on the feature you were implementing?

@omokehinde Any updates? If you're stuck somewhere, feel free to ask.

Hi all! I would be interested in contributing to the project. I had an idea for a similar app that would play random videos associated with a certain search term. I would be happy to work on the back and forward buttons that were mentioned previously, or I could suggest other features.

@thenorthstarblues Sure. Let's work on the back and forward buttons and then we could discuss your suggested features as well.

@amitness Cool! I'll start on it right now.


Dependency on conduit should be relaxed

Currently it depends on conduit == 0.0.*.

Thanks, fixed.


Add ext_monitor gem to improve Monitor class's operations

Which issue(s) this PR fixes:
Fixes https://github.com/fluent/fluentd/issues/2645
What this PR does / why we need it:
From ruby 2.6.5, Monitor class became slower due to fixing a deadlock bug (https://bugs.ruby-lang.org/issues/15992).
https://github.com/nurse/ext_monitor/ mitigates performance for ruby 2.6.5 or later and improves it for prior to 2.6.4  by 2x(https://github.com/fluent/fluentd/issues/2645#issuecomment-546817682).
Docs Changes:
no need
Release Note:
same as the title

I'll merge this after https://github.com/fluent/fluentd/issues/2380

By introducing ext_monitor in ruby 2.7, how about changing to if ext_monitor is installed, fluentd uses it? It reduces the dependencies and fluentd works even if ext_monitor has a problem.

Sorry, I had a mistake about a condition of installing.
Ruby 2.7 is bundled ext_monitor like mitigation code by default so 2.7 is fast enough without ext_monitor.

It reduces the dependencies and fluentd works even if ext_monitor has a problem.

Does it mean like below? and removing gem.add_runtime_dependency("ext_monitor", [">= 0.1.1", "< 0.2"]) from gemspec?
if Gem::Version.create(RUBY_VERSION) >= Gem::Version.create('2.7.0')
  require 'monitor'
else
  begin
    require 'ext_monitor'
  rescue LoadError => _
    require 'monitor'
  end
end

Does it mean like below?

Yes.

fixed.
https://github.com/fluent/fluentd/pull/2670/commits/4ae541676e6dce64a2caa90bcc62700f62184638
This log always outputs to STDOUT without ext_monitor. it might be noisy. what do you think of that? @repeatedly

Maybe, such message is not needed.
td-agent and docker images will install ext_monitor.
So most users don't have Monitor issue.
Add to instruction to gem install article is enough.

Maybe, such message is not needed.

:+1:
fixed https://github.com/fluent/fluentd/pull/2670/commits/0a772f2a72b3f8141a762f7d70bea9d7742cd50e


RFC: Deprecate password validation rules in favour of a strength rating

Affected Version
4.x, 5.x
Description
SilverStripe supports a number of password strength rules, e.g. minimum and maximum length, and a number of regex based tests that must pass (e.g. lowercase, uppercase, digits, punctuation).
In a modern world, entropy and complexity can turn a passphrase (e.g. correct horse battery staple) into a more secure (and more memorable) password than something like oi(2hH!@!R#!x. The topic of using a passphrase instead of a password is not the point of this RFC.
We may deprecate these APIs in favour of using a library to measure entropy and complexity, giving a strength rating back, and replace the minimum requirements API with a "must be at least 50% rated" or something similar.
zxcvbn is a popular JavaScript library written by Dropbox that measures this, giving a rating of 0-4 for the strength of your password. It has a third-party PHP version.
I propose that we:

Deprecate minimum length
Deprecate maximum length
Deprecate test patterns and minimum test score
Introduce a third party library like this to measure entropy and complexity
Introduce an API for the minimum strength rating
Introduce this in a 4.x minor release via a new pluggable PasswordValidator
Remove the deprecated code in 5.0

As a side note, the introduction of multi factor authentication may also reduce the need to have overly complex/strong passwords, since the second factor takes a lot of risk out of this equation. It may be acceptable for someone to use a weak password as long as they have MFA enabled.
cc @silverstripe/core-team

zxcvbn is a popular JavaScript library written by Dropbox

Just a side note that this particular one doesn't appear to be actively maintained anymore. The last PR was merged more than 2 years ago (Feb 11, 2017) and the last release has been made about that time too on Feb 7, 2017.

Cool, will have a look for alternatives

I think the RFC shouldn't be about deprecating/removing the lengths and patterns methods and replacing them with a strength library, it should rather be about deprecating them for being hardwired and replace with a password validator adaptor interface which, in a first instance, have the same features as the existing methods.
Then any kind of validation can be plugged in via this interface/service and it will eventually achieve the same as suggested here without causing too much pain for whoever wants to rely on the current behaviour.
If that's already the case behind the RFC, it's not obvious other than mentioning the pluggable validator (but nothing about being able to keep the current functionality).
Just remember how many hurdles SS had to skip to get to a stable versioned assets functionality. This is definitely smaller footprint change, but can be similarly difficult to deal with for some developers.

The current PasswordValidator class was already intended to be used as the base class for a pluggable service. So I agree with @michalkleiner that we should leave the current behaviour as one option and implement strength as a second option.
We could introduce a new PasswordValidatorInterface and have two implementations , PasswordValidator (the current) and StrengthPasswordValidator.
These are accessed as an Injector service in Member::password_validator(). For BC we should keep the service name being PasswordValidator rather than PasswordValidatorInterface.
The only method the interface needs is:
    /**
     * @param String $password
     * @param Member $member
     * @return ValidationResult
     */
    public function validate($password, $member)

A strength-based password validator will need access to the "don't re-use historic passwords" feature of the current one. You could do this by breaking that out into a separate validator and providing a CompositePasswordValidator interface, or possibly by supplying the composite stuff as a helper class to the two validators we propose. A helper class is less flexible, but it's simpler, and that might be a better way to go for now.

just a little pointer to https://github.com/dhensby/silverstripe-zxcvbn which does this already.
I would support moving to a strength based password validator over arbitrary rules.

Deprecate minimum length
Remove the deprecated code in 5.0

There's some regulatory environments which enforce different password standards. I'd say those are universal enough to keep in the framework. Our common point of reference is the NZ Common Web Platform, which needs to comply with the NZISM

The problem with custom "strength ratings" in third party libraries is that they'll never find their way into compliance frameworks like the NZISM. They have some additional rules like "don't reuse passwords", but in the end it needs to be expressed in a few sentences, not a bunch of code in a library.
I think we should push people towards strong passwords through libraries like that, but for that to happen we don't need to deprecate the existing logic. That push can happen through better defaults in new projects, and opt-in additions in new minor releases.

Yep fair enough, would you see a strength-based validator in core as well as what's there at the moment, or perhaps a configurable option to enable it on the existing validator? I'm not 100% sold that zxcvbn is the right way to go at the moment to be honest, the PHP library looks a little under maintained at a glance, but it's still better than using only entropy calculations.

would you see a strength-based validator in core as well as what's there at the moment, or perhaps a configurable option to enable it on the existing validator?

I'd like this to be a module, we already do enough in core. It would probably be part of our "recommended default recipe", which likely also includes MFA. But that doesn't automatically mean it becomes a supported module which we're on the hook for forever (which would be the case if it's in "core")

From what I can tell, I have a 👍 from @maxime-rainville , and a 👎 from @robbieaverill @dhensby @dnsl48 @sminnee on replacing or deprecating the current validation rules.
And there's a general consensus that we should make this pluggable. Has anyone identified blockers with this? PasswordValidator doesn't have a PHP class interface, which makes it a bit wonky to re-implement, but its definitely injectable.
Does anyone feel strongly that this is high value enough to maintain as a parallel opt-in implementation in core, as opposed to making this a module? Unless that's the case, I'm inclined to close this RFC as rejected, since it doesn't require core adjustments (beyond the creation of a PHP interface?)

It can be a satellite module =) let's close. Thanks everyone!


CCC Event issue

I have skills running on - the script always stops because it accidently clicks the character and no t the skill due to the slot thing...

I haven't tried running the event with the script yet. I'll do an update on it when I get home

Alright, after taking a look I am not sure why the slots would cause a situation where the program doesn't click correctly. I'll have to do some testing to further investigate the situation

Will be solved after we implement a proper observer function.
In the meantime, there'd be ugly wait() everywhere in the code.


1.3.0 Crashing on iOS (EXC_BAD_ACCESS)

The iOS system logs don't seem to be very helpful.
As soon as I update the version, the app crashes on start or the first query, not exactly sure.
Date/Time:           2021-10-19 12:15:54.0756 +0200
Launch Time:         2021-10-19 12:14:42.8908 +0200
OS Version:          iPhone OS 15.0.2 (19A404)
Release Type:        User
Baseband Version:    2.09.10
Report Version:      104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
VM Region Info: 0 is not in any region.  Bytes before following region:<PHONE_NUMBER>
      REGION TYPE                 START - END      [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      __TEXT                   102cc0000-102ccc000 [   48K] r-x/r-x SM=COW  ...er.app/Runner
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: SIGNAL; [11]
Terminating Process: exc handler [1339]

Terminating Process: exc handler [1339]
Triggered by Thread:  30

Thread 30 name:  DartWorker
Thread 30 Crashed:
0   ???                           	               0x0 ???
1   ???                           	       0x10a506b08 ???
2   ???                           	       0x13990a744 ???
3   ???                           	       0x13990a580 ???
4   ???                           	       0x13990a330 ???
5   ???                           	       0x13990a03c ???
6   ???                           	       0x139904eb0 ???
7   ???                           	       0x139904b80 ???
8   ???                           	       0x13990494c ???
9   ???                           	       0x139903c2c ???
10  ???                           	       0x1399032bc ???
11  ???                           	       0x120d55000 ???
12  ???                           	       0x120d522f4 ???
13  ???                           	       0x120d51e04 ???
14  ???                           	       0x120d51a10 ???
15  ???                           	       0x120d50950 ???
16  ???                           	       0x120d4f1ec ???
17  ???                           	       0x120d4eec8 ???
18  ???                           	       0x120d4ebac ???
19  ???                           	       0x120d4e748 ???
20  ???                           	       0x120d4e640 ???
21  ???                           	       0x120d299e0 ???
22  ???                           	       0x120d0e620 ???
23  ???                           	       0x10a5032e4 ???
24  Flutter                       	       0x1067e3ec4 0x106290000 + 5586628
25  Flutter                       	       0x1068025a8 0x106290000 + 5711272
26  Flutter                       	       0x10683b2b4 0x106290000 + 5943988
27  Flutter                       	       0x10683ad50 0x106290000 + 5942608
28  Flutter                       	       0x10697596c 0x106290000 + 7231852
29  Flutter                       	       0x1068d06b4 0x106290000 + 6555316
30  libsystem_pthread.dylib       	       0x1f2ec9a60 0x1f2ec8000 + 6752
31  libsystem_pthread.dylib       	       0x1f2ec8f5c 0x1f2ec8000 + 3932

Thread 30 crashed with ARM Thread State (64-bit):
    x0: 0x0000000282fddb80   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000003
    x4: 0x0000000000000000   x5: 0x00000001a11eba80   x6: 0x0000000000000a00   x7: 0x0000000000000000
    x8: 0x0000000000000000   x9: 0x00000001a11eba80  x10: 0x0000000000000005  x11: 0x0000000000bf3d01
   x12: 0x0000000000004009  x13: 0x0000000104d0c000  x14: 0x0000000000003fff  x15: 0x000000016e5a1360
   x16: 0x0000000000000000  x17: 0x000000011cb57438  x18: 0x0000000000000000  x19: 0x0000000000000000
   x20: 0x0000000113d20ca0  x21: 0x0000000000000003  x22: 0x0000000000000000  x23: 0x00000001042dcfb0
   x24: 0x0000000104088041  x25: 0x000000016e4bf000  x26: 0x000000011cb56e00  x27: 0x00000001399857f0
   x28: 0x0000000400000000   fp: 0x000000016e5a1350   lr: 0x00000001a11eb8d8
    sp: 0x000000016e5a1320   pc: 0x0000000000000000 cpsr: 0x60001000
   far: 0x0000000000000000  esr: 0x82000006 (Instruction Abort) Translation fault

Looks good. Thanks!


maven repo support

There's no maven repository for developers. Can you add one for the working master branch?

I used to host it myself but am no longer ready for that. I'll have to see if there are any good public ones we can use.

Might be able to use GitHub Packages for free in the mean time?

Might be able to use GitHub Packages for free in the mean time?

I'd like to use this, but it's mostly useful once the API becomes more robust. For #160 I was thinking maybe we can move API features like this Service to an entirely separate package and offer just the Service files and other core API models like the PreSavePrismRecordEvent.java and PrismRecord.java


doc: Move install instructions to the top

Moves installation instructions to the top for easier parsing by users. In reference to issue #24

Not sure what the procedures are here, but ptal @oa-coinbase from the commit history :). Do let me know if there's some procedures I need to go through!


Build error

Please answer these questions before submitting your issue. Thanks!

What version of Rust are you using (rustc --version)?

rustc 1.28.0-nightly (41affd03e 2018-06-04)

What operating system and processor architecture are you using?

Ubuntu 16.04

What did you do?
If possible, provide a recipe for reproducing the error.
Make release under tikv

A complete runnable program is good.

What did you expect to see?

Build finishes
5. What did you see instead?
Compiling rocksdb v0.3.0 (https://github.com/pingcap/rust-rocksdb.git#2a150c32)
error[E0658]: procedural macros cannot expand to modules (see issue #38356)
--> src/server/metrics.rs:17:1
|
17 | / make_static_metric! {
18 | |     pub label_enum GrpcTypeKind {
19 | |         kv_get,
20 | |         kv_scan,
...  |
50 | |     }
51 | | }
| |_^
|
= help: add #![feature(proc_macro_gen)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/server/metrics.rs:64:66
|
64 |       pub static ref GRPC_MSG_HISTOGRAM_VEC: GrpcMsgHistogramVec = register_static_histogram_vec!(
|  _____________________________________________________________^
65 | |         GrpcMsgHistogramVec,
66 | |         "tikv_grpc_msg_duration_seconds",
67 | |         "Bucketed histogram of grpc server messages",
68 | |         &["type"],
69 | |         exponential_buckets(0.0005, 2.0, 20).unwrap()
70 | |     ).unwrap();
| |^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/server/metrics.rs:71:67
|
71 |       pub static ref GRPC_MSG_FAIL_COUNTER: GrpcMsgFailCounterVec = register_static_int_counter_vec!(
|  ___________________________________________________________________^
72 | |         GrpcMsgFailCounterVec,
73 | |         "tikv_grpc_msg_fail_total",
74 | |         "Total number of handle grpc message failure",
75 | |         &["type"]
76 | |     ).unwrap();
| |_____^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error[E0658]: procedural macros cannot expand to modules (see issue #38356)
--> src/storage/engine/metrics.rs:19:1
|
19 | / make_static_metric! {
20 | |     pub label_enum RequestStatusKind {
21 | |         all,
22 | |         success,
...  |
53 | |     }
54 | | }
| |_^
|
= help: add #![feature(proc_macro_gen)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/storage/engine/metrics.rs:74:9
|
74 | /         register_static_int_counter_vec!(
75 | |             AsyncRequestsCounterVec,
76 | |             "tikv_storage_engine_async_request_total",
77 | |             "Total number of engine asynchronous requests",
78 | |             &["type", "status"]
79 | |         ).unwrap()
| |_________^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/storage/engine/metrics.rs:82:9
|
82 | /         register_static_histogram_vec!(
83 | |             AsyncRequestsDurationVec,
84 | |             "tikv_storage_engine_async_request_duration_seconds",
85 | |             "Bucketed histogram of processing successful asynchronous requests.",
86 | |             &["type"],
87 | |             exponential_buckets(0.0005, 2.0, 20).unwrap()
88 | |         ).unwrap()
| |_________^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error[E0658]: procedural macros cannot expand to modules (see issue #38356)
--> src/storage/mvcc/metrics.rs:17:1
|
17 | / make_static_metric! {
18 | |     pub label_enum MvccConflictKind {
19 | |         prewrite_write_conflict,
20 | |         commit_lock_not_found,
...  |
36 | |     }
37 | | }
| |_^
|
= help: add #![feature(proc_macro_gen)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/storage/mvcc/metrics.rs:51:9
|
51 | /         register_static_int_counter_vec!(
52 | |             MvccConflictCounterVec,
53 | |             "tikv_storage_mvcc_conflict_counter",
54 | |             "Total number of conflict error",
55 | |             &["type"]
56 | |         ).unwrap()
| |_________^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error[E0658]: procedural macros cannot be expanded to expressions (see issue #38356)
--> src/storage/mvcc/metrics.rs:59:9
|
59 | /         register_static_int_counter_vec!(
60 | |             MvccDuplicateCmdCounterVec,
61 | |             "tikv_storage_mvcc_duplicate_cmd_counter",
62 | |             "Total number of duplicated commands",
63 | |             &["type"]
64 | |         ).unwrap()
| |_________^
|
= help: add #![feature(proc_macro_non_items)] to the crate attributes to enable
error: aborting due to 9 previous errors
For more information about this error, try rustc --explain E0658.
error: Could not compile tikv.

which rust version are you using?

Please try with the rust version we provided in RUST_VERSION file (see README). We have not adapted to the latest rust nightly yet.


No image and warnings

Hello,
Firs tof all thanks for this code, its exactly what I was looking for.
One remark, you code is no longer aligned with jsmpeg library. I had to find older versions of jsmpeg lib for the code to work .... The minified version does not suppor sending a websocket as an argument.
I am trying to use your code to display a FOSCAM IP webcam I have at home though a rapsberry pi.
I have a nodejs express that is getting the url I am calling and starting the stream.
I call node-rtsp-stream on port 3333
my videostream is http://login:password@ip:554/videoMain
my port is 333
Then I create using localtunnnel a tunnel to one of my hosted servers
this maps the local port 3333 to the url given by localtunnel
This all goes fine and generates a html page with the relative infos ....
Result is this :
  Your Browser does not supprt Canvas.
I get a blank page with this in the console :
86[.WebGL-000002121E2B6A00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
85[.WebGL-000002121E2B6A00]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
85[.WebGL-000002121E2B6A00]RENDER WARNING: texture bound to texture unit 2 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
1:1 WebGL: too many errors, no more errors will be reported to the console for this context.
[Violation] 'setTimeout' handler took 114ms
[Violation] 'message' handler took 155ms
[Violation] 'setTimeout' handler took 58ms
[Violation] 'message' handler took 727ms
[Violation] 'message' handler took 156ms

@msj-fr thanks for the info. I haven't actually tried to use this with a newer version of jsmpeg. Is it only the minified version that doesn't work?
It might be from your error message that "Your Browser does not supprt Canvas" Have you tried using a modern browser? Most of them should have Canvas support.

I've updated the codebase to work with the latest jsmpeg. Hope this helps! Closing.

Hello,
Thank you for replying, I have tried with both minified and updated version
of the library. I get the same errors. I am testing using latest version of
chrome.
Here is what I am trying to achieve :
IP Camera (onvif) => Raspberry Pi <= localrunnel <= browser
I get the expected web page in the browser but I seem te get garbage frames.
I have gotten it to work with other solutions, but there is always a delay
(between 2 to 10 seconds). I was hoping to reach below 1s.
Thanks
Jérôme
Le mer. 15 mai 2019 à 03:41, David Jsa<EMAIL_ADDRESS>a écrit :

@msj-fr https://github.com/msj-fr thanks for the info. I haven't
actually tried to use this with a newer version of jsmpeg. Is it only the
minified version that doesn't work?
It might be from your error message that "Your Browser does not supprt
Canvas" Have you tried using a modern browser? Most of them should have
Canvas support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kyriesent/node-rtsp-stream/issues/30?email_source=notifications&email_token=ALYFJU464QXYDNRYFHFCKH3PVNS3JA5CNFSM4HDZ6ANKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNIKVA#issuecomment-492471636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALYFJUZBBE3SJ4XLR3FAB4LPVNS3JANCNFSM4HDZ6ANA
.

Are you using version 0.0.8 of node-rtsp-stream? Anything before that is going to fail with the new JSMPEG.
I have never been able to get <1s delay with this solution. I'm not sure what the bottleneck is and haven't invested serious time into figuring it out. It could be FFMPEG, it could be Node, it could be ws, it could be decoding video in JS browser side. Not sure unfortunately.
I was able to get lower delays with this nginx module: https://github.com/arut/nginx-rtmp-module
I used an MPEG-Dash player with it. It still wasn't instant, but it was faster than this method.


now aws ls throws

how to reproduce: now aws ls
> Error! An unexpected error occurred in provider ls: TypeError: provider[subcommand] is not a function
    at main (/snapshot/now-cli/dist/now.js:9709:31)
    at process._tickCallback (internal/process/next_tick.js:109:7)
    at Module.runMain (pkg/prelude/bootstrap.js:1282:13)
    at run (bootstrap_node.js:469:7)
    at startup (bootstrap_node.js:193:9)
    at bootstrap_node.js:584:3

HI @kandros - Apologies for the delay; are you still facing this issue?

@Qix- I can confirm that this is still an issue -- I got the same thing when trying to list aws deployments:
$ now aws ls
> Error! An unexpected error occurred in provider ls: TypeError: provider[subcommand] is not a function
    at main (/snapshot/now-cli/dist/now.js:9709:31)
    at process._tickCallback (internal/process/next_tick.js:109:7)
    at Module.runMain (pkg/prelude/bootstrap.js:1282:13)
    at run (bootstrap_node.js:469:7)
    at startup (bootstrap_node.js:193:9)
    at bootstrap_node.js:584:3

Same here for gcp

We have concluded that we are not going to maintain any of the third party platforms (Google Cloud Platform or Amazon Web Services) and are therefore removing them from Now CLI.
Since the third-party providers were not functioning properly anyways, we are hard-deprecating them as of now (there will not be a replacement).
They are removed in https://github.com/zeit/now-cli/pull/1601.


support float, time and bool datatypes

Wow great work, thanks for contributing!! Hoped they would work automatically.


Permissive MemoryStream typename

Fixes #4773 by treating string and MemoryStream types as a prefix match on the mscorlib identity,
hoping to more closely match Type.GetType's behavior.

@ericstj This was what you meant by using a prefix match, right?


Hardware is  Raspberry Pi 3 Model B.
~/.asoundrc file as follow:
pcm.!default {
type asym
capture.pcm "btmic"
playback.pcm "btspeaker"
}
pcm.btspeaker {
type plug
slave.pcm {
type bluealsa
device "1C:52:16:17:A8:F4"
profile "a2dp"
}
}
pcm.btmic {
type plug
slave.pcm {
type bluealsa
device "1C:52:16:17:A8:F4"
profile "sco"
}
}

Please try new master code, since a LOT of changes has been made to HSP/HFP profiles.


macOS: Fix set_configuration and reset by using USBDeviceOpen

Fixes #87
USBDeviceOpen is not required for claiming interfaces. The documentation says it's required for control transfers, but it works without. It is, however, required for set_configuration and reset.
Having an interface claimed does not cause set_configuration and reset to fail on macOS like it does on Linux. After doing some testing, I ended up doing what libusb does and attempting to USBDeviceOpen when opening a device to try to get exclusive access, but ignoring failures, and trying again and requiring success only before set_configuration and reset. That's not perfect -- you can be the second process to open a device and fail  USBDeviceOpen, then the first process closes it, and a third process is then able to call these methods, but I can't find a better way.

Though, I'm curious why not use USBDeviceOpenSeize() instead of USBDeviceOpen() same as libusb does.

The old documentation describes both:

USBDeviceOpen: Open up the IOUSBDevice for exclusive access.
USBDeviceOpenSeize: Open up the IOUSBDevice for exclusive access. If another client has the device opened, an attempt is made to get that client to close it before returning.

I don't know what it does to the other app, but that doesn't seem like the desired behavior. I guess that means I should test what happens when libusb opens a device that nusb has already opened.

that doesn't seem like the desired behavior

Yep, I agree.

I guess that means I should test what happens when libusb opens a device that nusb has already opened.

I dug a bit more and found this description. Assuming everything behaves the same way since that was published, I would expect that: if the app that's holding exclusive access to a device doesn't register to receive those IOServiceInterestNotifications and act on them, both USBDeviceOpen and USBDeviceOpenSeize will fail in the same way.


Windows touch keyboard should treat the location bar as a location bar

The windows virtual keyboard displays differently for browser url bars, including a ".com" button for example.

Fixed in #237


Host user entry not found in UserPortal against default portal(site)

Description of bug
Host user entry not found in UserPortal making it not searchable by Email (there could be other issues as well). Mean while when create a portal or site and same host for that newly created portal then a entry in Userportal is added, but somehow no entry for default site. This issue is occurring when installing DNN product without Installation wizard i.e when browsing http://[siteurl]/Install/Install.aspx?mode=install
Steps to reproduce
Install any DNN product. And after successful installation, go to
Settings > SQL Console and run following query
select * from userportals;
Current result
you won't see any record of
userid (1) and portalid (0)
Expected result
There should be a record for
userid (1) and portalid (0)

Affected version

[x] 9.2.2
[x] 9.2.1
[x] 9.2
[x] 9.1.1

Superusers are not always listed as site users, only if they have been created as site user first.
This is a known limitation, implemented from DNN 1. There are ideas to streamline handling of site users and superusers, but there is currently no timeframe for implementation.
In User Management of DNN 9.2.x, there is an option to display superusers, this should support search by E-Mail as well. SELECT * FROM dbo.vw_Users WHERE email = N'...' should include superusers as well.

@sleupold
This issue is only occurring when installing without wizard as I also update in the description, i.e. installing by browsing http://[siteurl]/Install/Install.aspx?mode=install

the issue is occuring as well, when adding a new superuser via UI

and this applies to most upgrades sites and their superusers

Unluckily It is getting relate with search, but it is due to installation without wizard


ZMQ_IMMEDIATE

This PR is a trying to implement ZMQ_IMMEDIATE socket option

You may wanna try again, and not write your code directly in GitHub.
Great free book on how to use Git: http://git-scm.com/book/en/v2


integrating with refile

Has anyone integrated with refile https://github.com/refile/refile/issues/434?

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.

In case anyone comes across this, here is the SO Post: http://stackoverflow.com/questions/35285939/refile-simple-form-undefined-method-attachment-field/


Add tidyverse packages

For #7

Heads-up @martynabogacz and @andysouth the commit above should (assuming I set the deploy settings right ; ) add new packages. Please add more new packages in that way (assuming it works).


After upgrade to Kafka 1.0.0 version : java.lang.OutOfMemoryError: Java heap space

Description
I upgraded Kafka from <IP_ADDRESS> to 1.0.0 version. And only from then, I'm seeing the kafka service going down because of below issue:
ERROR [KafkaApi-1] Error when handling request ; (kafka.server.KafkaApis) {replica_id=-1,max_wait_time=500,min_bytes=1,topics=[{topic=xxxx,partitions=[{partition=1,fetch_offset=847134777,max_bytes=1048576}]}]} java.lang.OutOfMemoryError: Java heap space
Even after increasing the HEAP size (KAFKA_HEAP_OPTS) to 7G, still the same error is coming.
Can you please help on this issue.
How to reproduce
Upgrade from <IP_ADDRESS> version to 1.0.0 version.
Checklist
Please provide the following information:

[ ] Confluent.Kafka nuget version:
[x] Apache Kafka version: 2.12-1.0.0
[ ] Client configuration:
[x] Operating system: Centos 7
[ ] Provide logs (with "debug" : "..." as necessary in configuration)
[ ] Provide broker log excerpts
[ ] Critical issue

How many partitions are you consuming?
Does it help to decrease fetch.message.max.bytes on the consumer?

Thanks Edenhill for your reply.
3 partitions are being consumed, with replication factor 2.
As i see, there shouldn't be an issue with the fetch.message.max.bytes on the consumer because before the upgrade, it was working perfectly fine without any issues. So, this wouldn't make difference.

Also provide your client configuration (see Checklist above)

I'm using Apache Kafka: version - 2.12-1.0.0.
Consumer instance is logstash to pull data from kafka.
Not using librdkafka.redist/confluent.kafka.

So you are not using confluent-kafka-dotnet?

Nope. I'm using only Apache Kafka. If this is wrong place to post the question, can you please direct the right link.

This repo is for issues with Confluent's .NET kafka client only.
For questions about Apache Kafka itself, use the kafka-users mailing list:
https://kafka.apache.org/contact

Thank you, and sorry for the trouble.


fix: support new arch

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: