psycopg2.OperationalError SSL SYSCALL error: EOF detected

An issue I recently run into. After starting the frontend with,
ramp-frontend launch --host <IP_ADDRESS>

the home page works, but I get the following traceback when trying to access /problems/ URL,
<IP_ADDRESS> - - [24/Feb/2019 21:53:17] "GET /problems HTTP/1.1" 500 -
Traceback (most recent call last):
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 2309, in __call__
    return self.wsgi_app(environ, start_response)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 2295, in wsgi_app
    response = self.handle_exception(e)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 1741, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
    raise value
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 2292, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 1718, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
    raise value
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/rth/src/ramp-board/ramp-frontend/ramp_frontend/views/ramp.py", line 82, in problems
    db.session, interaction='looking at problems', user=user
  File "/home/rth/src/ramp-board/ramp-database/ramp_database/tools/user.py", line 153, in add_user_interaction
    session.commit()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/scoping.py", line 162, in do
    return getattr(self.registry(), name)(*args, **kwargs)
  File "/home/rth/src/ramp-board/ramp-frontend/ramp_frontend/views/ramp.py", line 82, in problems
    db.session, interaction='looking at problems', user=user
  File "/home/rth/src/ramp-board/ramp-database/ramp_database/tools/user.py", line 153, in add_user_interaction
    session.commit()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/scoping.py", line 162, in do
    return getattr(self.registry(), name)(*args, **kwargs)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 1023, in commit
    self.transaction.commit()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 487, in commit
    self._prepare_impl()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 466, in _prepare_impl
    self.session.flush()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2436, in flush
    self._flush(objects)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2574, in _flush
    transaction.rollback(_capture_exception=True)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/util/langhelpers.py", line 67, in __exit__
    compat.reraise(exc_type, exc_value, exc_tb)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/util/compat.py", line 277, in reraise
    raise value
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2534, in _flush
    flush_context.execute()
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/unitofwork.py", line 416, in execute
    rec.execute(self)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/unitofwork.py", line 583, in execute
    uow,
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/persistence.py", line 245, in save_obj
    insert,
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/orm/persistence.py", line 1116, in _emit_insert_statements
    statement, params
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 980, in execute
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1099, in _execute_clauseelement
    distilled_params,
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1240, in _execute_context
    e, statement, parameters, cursor, context
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1458, in _handle_dbapi_exception
    util.raise_from_cause(sqlalchemy_exception, exc_info)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/util/compat.py", line 296, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/util/compat.py", line 276, in reraise
    raise value.with_traceback(tb)
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context
    cursor, statement, parameters, context
  File "/home/rth/miniconda3/envs/ramp-board/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) SSL SYSCALL error: EOF detected
 [SQL: 'INSERT INTO user_interactions (timestamp, interaction, note, submission_file_diff, submission_file_similarity, ip, user_id, problem_id, event_team_id, submission_id, submission_file_id) VALUES (%(timestamp)s, %(interaction)s, %(note)s, %(submission_file_diff)s, %(submission_file_similarity)s, %(ip)s, %(user_id)s, %(problem_id)s, %(event_team_id)s, %(submission_id)s, %(submission_file_id)s) RETURNING user_interactions.id'] [parameters: {'timestamp': datetime.datetime(2019, 2, 24, 21, 53, 17, 62040), 'interaction': 'looking at problems', 'note': None, 'submission_file_diff': None, 'submission_file_similarity': None, 'ip': None, 'user_id': None, 'problem_id': None, 'event_team_id': None, 'submission_id': None, 'submission_file_id': None}] (Background on this error at: http://sqlalche.me/e/e3q8)

will investigate and report if I find the cause of it.

Nevermind, that's just the message meaning that connection to the database couldn't be made (was an incorrect password in my case). It might still help to have a more explicit error message when that happens..

No actually, it may be another issue than DB connection I think.
https://stackoverflow.com/q/24130305/1791279 seems to suggest it could be different causes. It happens on the second page when add_user_interaction is called (that why I thought it was initially solved).
I'm using Ubuntu 18.10 where postgres 10.6. Is there any other information that it would be useful to provide in order to debug this?
FWIW, after I create the databoard_test database as done in Travis CI, all tests in ramp-database pass (except for the test_update_leaderboard_functions that fails because of the missing ramp-iris conda env which shouldn't be relevant). So overall the database package and connection  appears to be working as expected.
Tried to re-create the database with,
sudo -u postgres createdb --owner=rampadmin ramp_db2
ramp-utils deploy-ramp-event --force

and updated the database name in config.yml but I still get the same error as above..

For the record, in the logs I was seeing,
2019-03-04 22:11:20.666 UTC [2171] rampadmin@ramp_db2 LOG:  SSL error: decryption failed or bad record mac
2019-03-04 22:11:20.666 UTC [2171] rampadmin@ramp_db2 LOG:  could not receive data from client: Connection reset by peer

and editing
/etc/postgresql/10/main/postgresql.conf

to comment out all lines with SSL, seems to have solved this issue.

Do you also understand why it is solved? (or what the original problem was)

I imagine something wrong with the default SSL config for postgres on Ubuntu 18.10 in my case. Maybe the SSL certificates I had were invalid (I have not done anything special -- just installed postres via apt-get). Anyway for local connection SSL shouldn't matter..

Also, it was a server with a newly installed Ubuntu 18.10 so there shouldn't have been any special environment settings.

OK, so I have the same problem locally with my system postgresql, while with one installed by conda it was working fine. Due to different defaults for ssl (disabled on the conda one), and after commenting out as you mentioned it also works for the system postgres.
There were several people this morning that had the same problem.
Is the only solution to actually disable ssl in postgres? I assume we can fix something in our code that you don't need to disable the ssl?

while with one installed by conda it was working fine

Aww I didn't know that postgres was packaged in conda..

Is the only solution to actually disable ssl in postgres?

I guess postgres should work with default settings, there must be some fix I would think. Also it's interesting to analyze why unit tests still worked in that case (for me at least).

So with app.run(..., processes=1) it works with ssl enabled as well. (before we had there processes=1000 in the code)

So I did a PR to set it to 1 for the test-launch command, which should hopefully fix such problems when testing it out. Of course, if you do an actual deployment, you probably need to use something that scales better.

(before we had there processes=1000 in the code)

Hah, yes that certainly looks like the issue. In general it would have been good to run NGNIX or something in front of flask, though not sure how to do that without requiring lots of extra configuration.


introspection on std::string

The introspection on std::string doesn't work because it refers to a file in the xml tag file.
std::string is an example but there certainly exists other cases which not work.
So, we have to improve the implementation and check file tag if we don't find a result for other tags.

#54


⚠ Bofrost.lu has degraded performance

In e232f8f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1583 ms

Resolved: Bofrost.lu performance has improved in b0fd5a7 after 58 minutes.


added project working

Closes #3
👨💻 Changes proposed
Added the project working -

For the desired username entered information is fetched through Github API ( JavaScript fetch("URL") function is used ).
Validity of user is checked.
Then Data is converted to JSON and then filtered out.
Customised JavaScript function is used to generate the output.

Typo Fixed 👍


[bug] moon does not keep formatting of package.json when updating toolchain version.

Describe the bug
I have my package.json indented with tabs, but moon reformats it using spaces when I update toolchain.yml node/pnpm versions.
Expected behavior
Keep the same formatting and only update version numbers.
Screenshots

Environment
  System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1
    Memory: 52.05 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.proto/shims/node
    pnpm: 9.4.0 - ~/.proto/shims/pnpm
    bun: 0.8.1 - /opt/homebrew/bin/bun
  Managers:
    Cargo: 1.74.1 - ~/.cargo/bin/cargo
    Homebrew: 4.3.3 - /opt/homebrew/bin/brew
    pip3: 22.0.3 - /Library/Frameworks/Python.framework/Versions/3.10/bin/pip3
    RubyGems: <IP_ADDRESS> - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 15.0.0 - /usr/bin/gcc
    Git: 2.39.2 - /opt/homebrew/bin/git
    Clang: 15.0.0 - /usr/bin/clang
    Curl: 8.6.0 - /usr/bin/curl
    OpenSSL: 3.2.1 - /opt/homebrew/bin/openssl
  Servers:
    Apache: 2.4.58 - /usr/sbin/apachectl
  Virtualization:
    Docker: 26.1.3 - /usr/local/bin/docker
    Docker Compose: 2.27.1 - /usr/local/bin/docker-compose
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
    Android SDK:
      API Levels: 32
      Build Tools: 30.0.3, 32.0.0, 32.1.0
      System Images: android-32 | Google APIs ARM 64 v8a
  IDEs:
    Vim: 9.0 - /usr/bin/vim
    Xcode: 15.4/15F31d - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Go: 1.17.7 - /usr/local/go/bin/go
    Perl: 5.34.1 - /usr/bin/perl
    Python3: 3.10.2 - /Library/Frameworks/Python.framework/Versions/3.10/bin/python3
    Ruby: 2.6.10 - /usr/bin/ruby
    Rust: 1.74.1 - /Users/justas/.cargo/bin/rustc
  Databases:
    PostgreSQL: 14.7 - /opt/homebrew/bin/postgres
    SQLite: 3.43.2 - /usr/bin/sqlite3
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 126.0.6478.114
    Chrome Canary: 128.0.6555.0
    Edge: 126.0.2592.68
    Safari: 17.5

@minht11 Does editor config solve this? https://moonrepo.dev/docs/faq#how-to-stop-moon-formatting-json-and-yaml-files

It does.
Though bit annoying that another config file is needed, (I use biome) but it works.
So I guess this would be a feature request to improve formatting if no .editorconfig is present. I am sure it is not trivial, but at least simple cases tabs/spaces should be possible?

Looking into this here https://github.com/moonrepo/starbase/pull/85 Will maybe land in the next version.

Landed in 1.27.


Add mconfigptr CSR

👍

I'm unclear why this needs to be a named extension.  We've already added to Priv 1.12 new CSRs mstatush, mcontext, and scontext, and we're planning soon to add menvcfg, menvcfgh, and senvcfg.  The mconfigptr CSR seems sufficiently fundamental to me that we should make it mandatory in 1.12, but optionally zero, just like mvendorid, etc.

That approach would seem more consistent.

While this is arguable both ways, I would tend to agree with John.  Initially some had suggested that this should be a fast-track extension, but that was without consideration of what John summarized.
Given that there is no other functionality, that this is a read-only register (nominally hardwired in some or many implementations), and that this can even be hardwired to zero in a design that doesn't want to utilize the associated discovery method, the cost of this as a mandatory feature is quite minimal.  I'm all for simplifying the matter and just making this part of Priv 1.12.

Yeah, let's go that route.  I've updated the PR.

I'm interested to know more about the rationale and intent of this Smdisc extension (for example, why it is better to have a memory-mapped block for description of features rather than using read-only CSRs, and how this fits with the existing misa CSR). Is there anywhere I can look to find out more?
Thanks.

I'm interested to know more about the rationale and intent of this Smdisc
extension (for example, why it is better to have a memory-mapped block for
description of features rather than using read-only CSRs, and how this fits
with the existing misa CSR). Is there anywhere I can look to find out
more?

A full answer will be a long answer since there are many aspects to
discover at various levels in the software stack.  So I'll only briefly
mention some things:

To be clear, the mechanism currently being developed is for "low-level"
discovery.  It does not replace, for example, Device Tree or ACPI discovery
structures - which are more "high-level" discovery methods understood by
"rich" OS's and hypervisors.

A CSR-based mechanism (e.g. analogous to CPUID in x86) was considered.
It of course has its pros, but it also has its cons.

Overall there will be many extensions, and a growing list of
extensions over time, that will have discoverable info.  Some may
only require one bit of info, others may require tens of bytes or more.

Hardware cost and need for compression, especially for cost-sensitive
designs, are important factors.

Flexibility is needed to accommodate a wide range of needs as far as
amount and types of discoverable info.  (The amount of info for low-end
cost-sensitive embedded systems will likely be cut down from the amount of
info that would be available for "rich OS" platforms.)

Virtualizing the current approach being developed is easy.  Virtualizing
a register-based approach is not.  (x86 for example unconditionally traps
and software emulates all use of the CPUID mechanism within guest VMs.)
Somewhat similarly, there are issues about controlling what CSR-based
discovery info should be allowed or disallowed to be seen by, for example,
User-level code.

There are even more considerations, but I'll stop here except to note
that the use of the misa CSR for discovery is quite limited.  There are
more extensions (and will be yet more each year) than there are letters in
the alphabet.  So general discovery of even simply what individual
extensions are supported can't use misa effectively.  For example, there is
not one BitManip extension, but a high single-digit number of bitmanip
extensions heading towards ratification this year, and maybe more to come
next or following years.  So what should the misa.B bit mean?  The latest
position is that it doesn't offer much value and won't be allocated for
bitmanip.  The new low-level discovery method being developed will readily
support this granularity of discovery.  (Ditto for some other misa bits
that haven't been officially allocated yet.)

Greg

Is the configuration structure format standardized in https://github.com/riscv/configuration-structure?
Is it good to mandate that mconfigptr approach, when implemented, should be interrogated  by software instead of misa register when probing standard extensions?

The configuration structure is merely a proposal and has not been standardized.
We are not discouraging use of misa, but over time the configuration structure will provide more information than misa.


fix: preprocessor for review_date should use OrdinalEncoder

This PR proposes an update to the preprocessor to use OrdinalEncoder for review_date instead.

No, we shouldn't indeed. :+1: Thank you for spotting that!
The PR has been updated.


About implementation of noise normalization term

Hi,
Firstly, thanks for the great work and the code.
I have some questions on the difference of the "noise normalization term" between released implementation and the paper description.

In the paper and code, as inside the red and blue box, the noise normalization term is calculated by using beta0 which I think is beta3 in the code. But in the code, this term is calculated by using beta2. I don't think there is a big difference since beta2 is 0.999 and beta3 is 1.0, but it might be different if you want to tune the betas.  And I think it might be useful to check if this will effect the experimental results in paper (Although I think it may only lead negligible difference.)

I think this term is a constant during the optimization as long as the betas do not change. So is this acceptable to pre-calculate before optimization start? Or it could be change during optimization? Just want verify my understanding of this algorithm.

Thanks for the reply.

Hi julightzhong10,
Thanks for your comments.

That is a bug in the current open-source implementation of AdaPNM.
It should be beta3. I will correct it as soon.
Thanks a lot for pointing out this problem.

Yes, it is fine to calculate the normalization factor directly before optimization.
This normalization factor is constant during training.
This normalization factor in my implementation can make the optimal hyperparameter settings of PNM/AdaPNM similar to SGD/Adam.

Thanks for the reply, close this issue.


Release 0.1.1

Release v0.1.1:

upgrade crossbeam-channel

https://github.com/cryptape/cita/issues/773


Create a Placeholder RoadMap file for FrontEnd.

We need to have a Placeholder RoadMap file for FrontEnd under Web Dev.

Can i work on this..?

Already done. :)

I want to contribute to this issue : Create a Placeholder RoadMap file for FrontEnd.
Name-Arya Gupta
Domain-Frontend with HTML CSS
Batch-16
Serial No-3172
Issue Number-52
Contribution Approaches-
Describe why it is necessary to learn and work using basics of frontend before diving into frameworks and a step-by-step approach.

@Arya-Gupta See my above message? 🤔


fix TCSReply

A new inspection was created.

The inspection completed: No new issues

Codecov Report

Merging #232 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #232   +/-   ##
========================================
  Coverage    84.77%   84.77%
========================================
  Files           29       29
  Lines         1123     1123
========================================
  Hits           952      952
  Misses         171      171

Impacted Files
Coverage Δ

werobot/replies.py
100% <ø> (ø)
:arrow_up:

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 b40f21c...1fbe5cb. Read the comment docs.

close #230


Add missing blank line before Markdown lists

The troubleshooting checklists for emails and pages were not being rendered correctly:

https://www.mautic.org/docs/en/emails/troubleshooting.html
https://www.mautic.org/docs/en/pages/troubleshooting.html

I think this is because Markdown lists require a blank line before they start, but I can't be sure due to #311 and #312.

I think it's a CSS issue. But let's see if it helps.

Not fixed yet 😕 Does the site automatically get rebuilt on merge?

Yes, it is automatically being rebuilt on merge. It may take a few minutes to get into production. But the problem with  and  tags is this CSS rule:
ol, ul {
    list-style: none;
}

It should be removed. But I'm not sure if it breaks other UI elements.


Support for ARM-based OSes

Firezone would be useful on Raspberry Pi OS (and other ARM-based OSes):
https://www.reddit.com/r/elixir/comments/pyrlcq/comment/hew67bk/?utm_source=reddit&utm_medium=web2x&context=3
https://news.ycombinator.com/item?id=28702827
This will require either AWS Grativon instances or the purchase of a few Raspberry Pis to run self-hosted runners on.
Support for the following ARM-based Linux distros:

Raspberry Pi OS
Ubuntu 18.04, 20.04
Red Hat 7, 8
Amazon Linux 2
SUSE

Seconded.
I use PiVPN in a few places, and whilst its perfectly fine, the extra flexibility that firezone seems to offer would be a game changer for the home/IoT market if it was rolled up into an arm compatible package, or container.

This has been implemented as part of #424 and is available in the Firezone 0.2.10 release. For RaspberryPI OS users, please use the Debian package that corresponds with your RaspberryPI OS version. Thanks!


RBAC support

With this change deis-router became available to work in RBAC-only clusters
Works with both Kubernetes 1.5 and 1.6 (see templates/_helpers.tmpl for details)
Actually tested with 1.5.7 and 1.6.2
Role allows deis-router:

extensions/deployments: get
apps/deployments: get

ClusterRole allows deis-router:

services: get and list
secrets: get
endpoints: get

Jenkins, OK to test

Codecov Report

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

@@           Coverage Diff           @@
##           master     #344   +/-   ##
=======================================
  Coverage   56.47%   56.47%
=======================================
  Files           6        6
  Lines         425      425
=======================================
  Hits          240      240
  Misses        159      159
  Partials       26       26

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 c31737d...adacac6. Read the comment docs.

Jenkins, OK to test

@Bregor thank you for this contribution. I made several comments, but I want to tell you that overall, this looks great!

@krancour thank you very much for your comments! I will try to achieve them in couple hours.

Jenkins, add to whitelist

@krancour thank you once again for you comments and thank you for too long waiting.
Fixed and rebased.

@Bregor did your own testing show that router still worked fine with the reduced permissions?

@krancour I still can create/delete app, set domains an so on.

Thanks, @Bregor. LGTM. Waiting for one other LGTM.


Missing features

Hello, I dont see these features(in the code), as its described in readme.
maybe its planned for future version, but now it can be misleading, remove it or mark as todo 😉

We will add some features and create an amazing cart package for Laravel.


chore: Update e2e image

In order to execute the e2e tests with go 1.22 we need to use 1.22 during the execution
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

/skip-e2e


DataTables warning: table id=tickets-table - Ajax error

Hello guys, I'm new in this world and I'm learning about laravel. Now, I'have a problem loading tables of tickets. My browser says:
"DataTables warning: table id=tickets-table - Ajax error. For more information about this error, please see http://datatables.net/tn/7"
In web browser console I get this errors:
"jQuery.Deferred exception: $(...).tooltip is not a function TypeError: $(...).tooltip is not a function
at HTMLDocument."
"jquery-3.3.1.min.js:2 Uncaught TypeError: $(...).tooltip is not a function
at HTMLDocument."
And with this I get a 500 error code
"tickets/data/active?draw=1&columns%5B0......... 500"
What should I do?

Solved updating files. And editing this line in > panichd/src/views/tickets/datatables/loader.blade.php <
ajax: { 		    url: '{!! route($setting->grab('main_route').'.data', $ticketList) !!}',             type: 'GET'         },
Now we have the problem Unknown column '""' in field list
Departments are disabled.

Change
$a_select[] =   "'-' as dep_ancestor_name"; for
$a_select[] =   \DB::raw("'-' as dep_ancestor_name");
in controller TicketsController function data and is fixed the problem

I am getting the same error
I changed this
$a_select[] = "'-' as dep_ancestor_name"; for
$a_select[] = \DB::raw("'-' as dep_ancestor_name");
but still i am getting error

"error":"Exception Message:\n\nSQLSTATE[42000]: Syntax error or access violation: 1055 'fotocons_new.panichd_tickets.created_at' isn't in GROUP BY
Getting this error now
Can anyone help me to solve this?

I just did a fresh install to check this package out. Laravel 5.8. I corrected this error by modifying:
/vendor/panichd/panichd/src/Controllers/TicketsController.php (line 141)
REMOVED:
$a_select[] = '"" as dep_ancestor_name';
ADDED:
$a_select[] = \DB::raw("'-' as dep_ancestor_name");

I have applied @wladiz2001 dedicated pull request #12 in the latest release posted yesterday. Could you please guys confirm If your related issues continue after updating PanicHD to v0.18.0?


Restructure for page routing

Restructure code for page routing.

Flutter application code was restructured.
main.dart is only to be used for page routing.
lib/pages will be stored in pages directory.
lib/services like calculations, map requests etc. will be stored in services directory.
images and other assets will be stored in assets directory.

@jakubprogramming
please checkout and varify recent changes.
i will merge with master and make a pull request afterwards.

is this still in todo or can be previewed @mayo-s ?


[bug] napi.findFiles() issue: SgNode for file A apparently references text from file B

Idea: use ast-grep napi programmatically.
💻 Code
  const matches = await ts.findInFiles(
    {
      paths: ["../src"],
      matcher: {
        rule: { pattern: "yup.object($OBJ)" },
      },
    },
    processMatch,
  );

function processMatch(err: any, sgNodes: SgNode[]) {
  for (const sgNode of sgNodes) {
    console.log(sgNode.getRoot().filename());
    const obj = sgNode.getMatch("OBJ")!;
    console.log(sgNode.range());
    console.log(obj.range());
     // THIS PRINTS CORRECT CODE:
    console.log(sgNode.text());
    // THIS PRINTS EITHER GARBAGE (text from some other file or some Chinese characters)
    // OR CRASHES (see the message below)
    console.log(obj.text());
  }
}

crash messages are like this:
thread '<unnamed>' panicked at crates/napi/src/doc.rs:95:36:
range end index 1768 out of range for slice of length 1349

🙁 Actual behavior
See comments in the code above
🙂 Expected behavior
The code above should print the correct source code.

Can you also share the file you are scanning?

There should be several ways to debug this issue:

it could be a concurrency issue. Can you reproduce it reliably? How many files are you scanning?
it could be a text encoding issue. Can you find the file you are using non-ascii code?

You can try reduce the issue by deleting files in the repo and find the minimal reproduction.

running into a similar issue. i ran this on my codebase and got a crash similar to the above.
I get a segfault when trying to getMatch an existing metavariable
import { tsx } from '@ast-grep/napi';

// this file will parse itself for simplicity lol

const funcWithArg = (arg: string) => arg;
funcWithArg('hello world');

async function main() {
  tsx.findInFiles({ paths: [__filename], matcher: { rule: { pattern: 'funcWithArg($KEY)' } } }, (err, results) => {
    if (err) {
      console.error(err);
      return;
    }
    results.forEach((result) => {
      console.log(`matched ${result.getMatch('NONEXISTENTKEY')?.text()}`);
      console.log(`matched ${result.getMatch('KEY')?.text()}`);
    });
  });
}

main();

This gives
❯ bin/test-ast-grep
matched undefined
[1]    48095 segmentation fault  bin/test-ast-grep

@harrisonzhu-db would you like to provide a minimal reproduction? Usually it can be done by deleting scanned code.

the bug should be self-contained within the code I pasted - the script is using ast-grep to scan itself, so that should be all you need

Thanks for the report. I found the root issue now.

Fixed in main branch

very awesome! thanks for this


Issue with resampling

Hi, I am trying to resample audio using your lib, when I do the following, I get an mp3 file of 0kb.
    const stream = streamFromWebAudioMicroPhoneConvertedTo16BitPCMAt16000hz();
    const fileName = path.join(os.tmpDir(), 'foogle', uuid.v4() + '.mp3');

    const mp3 = fs.createWriteStream(fileName);

    const resampler = new PCMFormatStream({
      bitDepth: 16,
      channels: 1,
      sampleRate: 16000
    },{
      bitDepth: 16,
      channels: 1,
      sampleRate: 44100
    });

    const encoder = new lame.Encoder({
      // input
      channels: 1,
      bitDepth: 16,
      sampleRate: 44100,
      float: false,
      signed: true,
      // output
      bitRate: 128,
      outSampleRate: 44100,
    });

    stream
      .pipe(resampler)
      .pipe(encoder)
      .pipe(mp3);
    console.log(fileName);

Removing the resampler makes things work, so I an wondering if there are any expectations for resampler's input?

see #1


[Bug]: MySql DATETIME fields detected as Type None and all NULLS -ERROR: org.apache.hop.core.exception.HopValueException

Apache Hop version?
2.2.0 / 2.4.0
Java version?
jre11.0.15 (Azul)
Operating system
Windows
What happened?
MySql DATETIME fields detected as Type None and all NULLS -ERROR: org.apache.hop.core.exception.HopValueException
We have a Table with DATETIME fields in MySql Server running on Red Hat Linux: mysql  Ver 14.14 Distrib 5.7.24
We have a Workflow running a Table Input Action
If you run HOP from Linux the DATETIME fields are detected as TIMESTAMP and are retrieved OK
If you run HOP from Windows the DATETIME fields are detected as Type: None and retrieved as NULLS
In both cases we are using JAVA: jre11.0.15 (Azul) and LIB: mysql-connector-java-5.1.38-bin.jar

If you run HOP from Linux the DATETIME fields are detected as TIMESTAMP and are retrieved OK

If you run HOP from Windows the DATETIME fields are detected as Type: None and retrieved as NULLS

ERROR: org.apache.hop.core.exception.HopValueException

Issue Priority
Priority: 3
Issue Component
Component: Actions

As Hans sugessted me - (Thanks for the tip)
I have turned on "Support the Timestamp data type" but still comes as None/Null

After turning on "Support the Timestamp data type" you must restart HOP and the problem is solved


Fatal error: Property 'ending' of object # is not a function

I'm getting this error after installing 2.1.5:
Fatal error: Property 'ending' of object #<Farm> is not a function

This is not happening in previous versions. If I can get some time, I'll try to reproduce it in an isolated environment outside of my current project.

@robtarr
Thanks, we made some changes to one of the dependency libraries to use a library called worker Farm. We'll look into this today. Otherwise you can switch back two patch versions to avoid the issue.

@robtarr
Oh, and any help you can provide by way of reproducing the issue would be greatly appreciated.

https://github.com/filamentgroup/node-worker-farm/blob/master/lib/farm.js#L311
That's the only spot I can find that might be throwing this exception. It may be the case that our calls are passing in something that is not a callback to workerFarm.end which is defined in:
https://github.com/filamentgroup/node-worker-farm/blob/master/lib/index.js#L24
Seems unlikely since that only place we call end is:
https://github.com/filamentgroup/directory-colorfy/blob/master/lib/colorfy.js#L96
And callback there is definitely a function.

Hmm, so there's this statue where this.ending is null and end sets it to true which could cause this :/
https://github.com/filamentgroup/node-worker-farm/blob/master/lib/farm.js#L299

@robtarr
If you're feeling super helpful you can try to debug what this.ending is and why it's not a function in your the copy of node-worker-farm that npm installed for you locally.

I'll try to get to it. I've got a super busy day, but will do my best. Thanks for tracking it down to that line :)

Thanks for logging the issue! :+1:

I'm having this issue as well. It's something to do with colorfy, as it only started happening when I'm using colors. Sorry for not being more helpful currently!

We've reverted the version of directory-colorfy in Grunticon 2.1.6 - that
should fix this issue.
On Tue, Mar 10, 2015 at 7:04 AM, Oliver Lowe<EMAIL_ADDRESS>wrote:

I'm having this issue as well. It's something to do with colorfy, as it
only started happening when I'm using colors. Sorry for not being more
helpful currently!
—
Reply to this email directly or view it on GitHub
https://github.com/filamentgroup/grunticon/issues/246#issuecomment-78058971
.

@robtarr @loweoj
What are your environments?
OS
Node version
Grunt version
Grunticon version?

OS X & Ubuntu (CircleCI)
node: 0.12.0
grunt: 0.4.5

Taking over this project but I think this has been fixed?

This is an automated message to let you know that a helpful response was posted to your issue and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

If the response works to solve your problem—great! But if you’re still having problems, do not let the issue’s closing deter you if you have additional questions! Post another comment and I will reopen the issue. Thanks!


-webkit-hypens: auto; not supported?

<EMAIL_ADDRESS>commented:

Which version of PhantomJS are you using?
1.5
What steps will reproduce the problem?

Load a page with specifying following html:
<div style="width:100px;-webkit-hypens:auto;hypens:auto;">Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.  What do you see instead?
Expected output would be hyphenated - but it was not...
Which operating system are you using?
MacOS 10.7.4
Did you use binary PhantomJS or did you compile it from source?
Binary
Please provide any additional information below.
Maybe those experimental CSS3 features are not enable in the webkit branch that you are using?
Really love your phantomjs! :)
The icon looks like PacMan - maybe switch to a more PacMan-Style ghost?
PKC

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #572.
:star2:   2 people had starred this issue at the time of migration.

2.5 release will support this feature. Right now only Linux binary has it.


Add a fast glimpse extractor

One task we often have to do is to extract regions of an image or volume given a list of centroids. We should add a generic function to enable this. It would be useful to eventually make this compatible with dask to parallelize it.

There is some nice documentation here:
https://examples.dask.org/applications/image-processing.html#applying_custom_function

We can also leverage InfinitePaddedImage


support for symbols escaping

Adds symbols escaping

Coverage decreased (-0.2%) to 98.361% when pulling ad5d3ee027f88c093e6794fba7aea054afb244ee on feature/symbols_escape into d7a95f022b51468003baaf10c75825648c2103ab on master.


Use custom_namespaces and custom_elements in examples

Currently the examples in readme.md use customNamespaces and custom where they should be using custom_namespaces and custom_elements, respectively.
This pull request fixes #42.

Thanks again @Mithgol!
Since the readme file is built from a template this change would be better in templates/readme/examples.md, but it's easy enough for me to make that change and rebuild the readme.

Since the last comment was on Feb 8th, i'd like to give this a "bump".
The npm module page (https://www.npmjs.com/package/rss) does not reflect the changes. Which is rather obvious since there is no release which includes this fix.
However, the module is downloaded several hundred times a day. So, potentially, there might be several hundred people on the wrong track (like me :smile:).


Atom remembers session on "atom .", even after rm -rf ~/.atom/storage

Hey guys, so is there a way to start atom on a project without remembering the last session? Using "atom .", I looked on the project folder to see if it creates a config file but didnt find anything. Cheers

@vtimbuc atom --clear-window-storage
Also, we're trying to control the amount of Issues that we have to triage and track. For general questions, the Atom message board is where you'll probably be able to find answers faster.

@50Wliu Thanks man. Cheers


Fix race condition in FIRComponentContainer instance creation

Reported in #3967. Users sometimes seeing a crash when multiple threads
concurrently try to create Firestore instances. By inspection I found
that there's a race here where two threads can check for presence in the
cache, see nothing, proceed to creation, both store a value in the cache,
and both return their copies. This would lead to two Firestores being
created for a single App.
This replaces dispatch_sync on a serial queue with good old
@synchronized blocks. dispatch_sync will self-deadlock if called
from a thread already on the queue while @synchronized allows
recursion.
No new tests are added because several tests like
testDependencyDoesntBlock already cover this case.
Fixes #3967. Could possibly address #3778, though the error doesn't seem like it should arise from this.

Any objection to cherry-picking to M57 (6.10.0)?

Any objection to cherry-picking to M57 (6.10.0)?

Merging and cherry-picking, feel free to raise concerns if you have any!


Don't lie about what's Running

Fixes #5964

r? @matklad
(rust_highfive has picked a reviewer for you, use r? to override)

Hmm, looks like there are lots of tests that assert things on
[RUNNING] `rustc ...

How do we want to resolve this?

Oh I don't think we can remove emissions of Running entirely, but I was thinking that we may be able to apply a cargo-check specific fix. The Running directive is often useful for figuring out how to run rustc manually in quick debug situations.

What cargo-check specific fix did you have in mind?

I'm kind of torn about it. Lying is not good, but even a quasi-truth can be useful (as testified by its usage in the testsuite).
What would it take to make cargo-check's "Running" output accurately (or more accurately) reflect reality? For instance, what's the business about --crate-name?

Technically speaking it's not actually lying, it's just speaking the quasi-truth you mention. Cargo sets a number of environment variables for itself which changes its behavior when executed, so to more accurately reflect what's going on we'd need to print env vars as well

Superseded by #6017.


Allow reportAllChanges for LCP for late loaded script

Currently if reportAllChanges=true but web-vitals is loaded late, then it doesn't report all LCP changes as we take the last one.
This can be confusing and make you think only one LCP entry was emitted when multiple ones were. It can be useful to know that multiple entries are emitted and this works for all the other metrics.
I also removed some "// Greater than the image load delay." comments that weren't true.

Not sure what's gling on with the Firefox test. Unrelated to this PR and seems it's using v127.0a1 instead of v125.0.1 (the last successful run 2 days ago) so a dependency upgrade and seems to be ahead of stable now. Will keep digging...

OK I think it's just a case of Firefox Nightly being a bit broken at the mo. Will try rerunning this tomorrow.


I changed my skin in the launcher but it wouldn't change in game

Hey I decided to change my skin but it wouldn't change in the game I think this is a bug

In the Beta rework, this should no longer happen as now the game takes skins directly from Mojang's servers.


Dataspace Connector UI connection ERROR

Hello， I installed the dataspace connector and the dataspace connectorUI as instructed. Here's how:
dataspace connector：
docker run -p 8080:8080 --name connector ghcr.io/international-data-spaces-association/dataspace-connector:latest
dataspace connectorUI：
sudo docker build -t dataspace-connector-ui .
sudo docker-compose up

and the docker build hint：
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
but it build and execute successfully.

Next step, I access the localhost:8083, there are some error int the website:

the log show :

Then I access 'https://admin:password@localhost:8080/api/configurations' by website, it succeed.

Error: connect ECONNREFUSED <IP_ADDRESS>:8080
So, what's wrong with my option and how to solve it，can you help me?
Thanks.

I have the same issue. I have configured a DSC and its UI using docker. I can access the connector API Swagger UI and try many of the request that the UI is giving error.
In the UI I get the same error: Error: connect ECONNREFUSED <IP_ADDRESS>:8080
I have checked the port of the connector is correct.

heya fellas, anyone managed to solve this error?
i tried changing "username" to "key" and "password" to "value"  in the authentication headers, as an old issue suggested, but still no improvement.
thanks again!

I used this docker-compose.yml to solve this problem.
Change CONNECTOR_URL=https://localhost:8080 to CONNECTOR_URL=https://dc:8080
Because CONNECTOR_URL=https://localhost:8080 will access to dataspace-connector-ui self.
version: '3.5'

services:
    dataspace-connector:
        container_name: "dc"
        image: ghcr.io/international-data-spaces-association/dataspace-connector:latest
        ports:
            - "8080:8080"
    dataspace-connector-ui:
        container_name: "dci"
        image: ghcr.io/international-data-spaces-association/dataspace-connector-ui:sha-1d4426a
        environment:
            - CONNECTOR_URL=https://dc:8080
            - CONNECTOR_USER=admin
            - CONNECTOR_PASSWORD=password
        ports:
            - "8083:8083"


UHF-8838: Template for services bulletin listing

UHF-8838

What was done

This thing was fixed

How to install

Use instance of https://github.com/City-of-Helsinki/drupal-helfi-sote
Make sure your instance is up and running on latest dev branch.

git pull origin dev
make fresh

Update the HDBT theme

composer require drupal/hdbt:dev-UHF-8838_Service_listing_seo

Update the drupal-helfi-platform-config

composer require drupal/helfi_platform_config:dev-UHF-8838_Service_listing_seo

Run make drush-updb drush-cr

How to test

[ ] Open https://helfi-sote.docker.so/fi/sosiaali-ja-terveyspalvelut/terveydenhoito/terveysasemat/haagan-terveysasema and check that Services list is now bulletin list instead of cards
[ ] Close the other PR's if valid
[ ] Check that code follows our standards

Designers review

[X] This PR does not need designers review

Other PRs

https://github.com/City-of-Helsinki/drupal-helfi-platform-config/pull/576

Closing this. New PR will replace.


CNAME Cross user banned

Showing this error After sucessfull merge and github verified

We cannot do any thing about this as it is a Cloudflare limitation where you cannot set your CNAME to another domain hosted on Cloudflare.


Double slashes in GitHub pages link on Windows

OS?
Windows 10
Versions.
λ ng --version
angular-cli: 1.0.0-beta.24
node: 7.2.1
os: win32 x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1

Repro steps.
λ ng new test-app
...
λ cd test-app
λ ng github-pages:deploy
Hash: 2bf0e1245eb5e01382d8
Time: 26858ms
chunk    {0} main.1c717b9fe8fd3d6882ab.bundle.js, main.1c717b9fe8fd3d6882ab.bundle.map (main) 2.91 MB {2} [initial] [rendered]
chunk    {1} styles.87416f5cb43dddfee231.bundle.css, styles.87416f5cb43dddfee231.bundle.map, styles.87416f5cb43dddfee231.bundle.map (styles) 1.69 kB {2} [initial] [rendered]
chunk    {2} inline.f4b4f29a7e700f2413a5.bundle.js, inline.f4b4f29a7e700f2413a5.bundle.map (inline) 0 bytes [entry] [rendered]
Deployed! Visit https://tobymurray.github.io//test-app//
Github pages might take a few minutes to show the deployed site.

The issue here (I believe) is the the double forward slashes in the URL. Very minor, mostly cosmetic as the browser still resolves double slashes appropriately in this case but looks like its unintentional. I tried this out in both Cmder (ConEmu) and Windows Command Prompt and it yielded the same message.

Same here

Closed via https://github.com/angular/angular-cli/pull/4385.


Insert nodes created from FixedMenu at the end

Elements from the fixed menu are inserted at the beginning of the content at the moment. This can be cumbersome for the user when there is already some content in the editor. Ideally, such elements should be inserted at the end.
https://vimeo.com/737784830/c7a0074df8
@AbhayVAshokan _a Please take a look.

@labeebklatif _a can you please share your thoughts on this issue?
https://vimeo.com/738148799/92fcb6bd92
cc: @abrahamparayil
low-priority _t

IMO, let's keep this as Low priority as discussed for now. Will look into this once I have some bandwidth.


Solution: Spring serializes Java's date type date problem

issues : #3001
Solution: Spring serializes Java's date type date problem

@BoYiZhang I thinks it's already fixed, could you check it again?

@BoYiZhang I thinks it's already fixed, could you check it again?

?  I just merged this PR and didn't see what you said,  @BoYiZhang , Please check , thx

@dailidong
Customer feedback
Get data through API interface :
For time data such as createtime, the returned data is eight hours later than the normal time
Background data is normal, but after spring serialization, the data will no longer show Beijing time
The reason is that data of date type, after being serialized in spring, will be formatted as:
At present, the main users of the dispatching are China users, so the default settings are increased.
Control the data date returned by API interface

After modification:


Overloading functions with specialized parameters not working as expected.

The below code has a specialized signature for Subscribe function that takes "NotificationClicked" as the event Name and NotificationClickedEventArgs type as the eventArgs parameter. The general signature takes any string as eventName and the base EventArgs as the eventArgs parameter.
My understanding is that typescript should give a compiler error where I am executing the code PublishSubscribe.Subscribe("NotificationClicked", new EventArgs()); because the specialized signature expects a NotificationClickedEventArgs type. As per my observation, typescript is compiling successfully which most likely is a bug. This works correctly on return types though.
class EventArgs{
  EventName: string;
  EventData: any;
}

class NotificationClickedEventArgs extends EventArgs{
  NotificationID: string;
}

class PublishSubscribe{
  static Subscribe:{
    (eventName: "NotificationClicked", eventArgs: NotificationClickedEventArgs):void;
    (eventName: string, eventArgs :EventArgs):void;
  } = (eventName: string, eventArgs: EventArgs) => {  }
}

PublishSubscribe.Subscribe("NotificationClicked", new EventArgs());

This is because you have that catch-all non-specialized signature. Unfortunately, you can't remove it because of an old requirement before string literal types became a thing. #6278 seeks to fix that, but I I'm not sure if we can get it into 1.8. @mhegazy @ahejlsberg?

This behavior is working as expected with return type overloading as shown below. Even though I have the non-specialized signature that is returning the base EventArgs type, TypeScript is deducing accurately that the Subscribe method will be returning NotificationClickedEventArgs when the parameter passed is "NotificationClicked", which makes me believe that the type checking for the following parameter types is not getting stricter based on the parameter values provided for previous parameters.
class EventArgs{
  EventName: string;
  EventData: any;
}

class NotificationClickedEventArgs extends EventArgs{
  NotificationID: string;
}

class PublishSubscribe{
  static Subscribe:{
    (eventName: "NotificationClicked"):NotificationClickedEventArgs;
    (eventName: string):EventArgs;
  } = (eventName: string):EventArgs => {
	  	if (eventName === "NotificationClicked")
		  return new NotificationClickedEventArgs();
		else
		  return new EventArgs();
	  }
}

PublishSubscribe.Subscribe("NotificationClicked").NotificationID //This is allowed
PublishSubscribe.Subscribe("SomethingElse").NotificationID //This errors as expected as NotificationID is not a property of EventArgs

With https://github.com/Microsoft/TypeScript/pull/6744 in place (you can try it in typescript@next), you can remove the string overload, and that will give you the error you expect.

also worth noting, is it will make your function more restrictive, i.e.
class PublishSubscribe{
  static Subscribe:{
    (eventName: "NotificationClicked", eventArgs: NotificationClickedEventArgs):void;
  };
}

PublishSubscribe.Subscribe("NotificationClicked", new EventArgs()); // Erro EventArg is not NotificationClickedEventArgs

PublishSubscribe.Subscribe("NotificationClicked", new NotificationClickedEventArgs()); //  OK

var eventName = "NotificationClicked";
PublishSubscribe.Subscribe(eventName, new EventArgs()); // Error, string is not "NotificationClicked"


spiIOCMessageN(1) is not working on different kernel

Dear author, i have some trouble to make spi work, as i can see you are fetching IO controll numbers by using this conts's
spiIOCMessage0    =<PHONE_NUMBER> //0x40006B00
spiIOCIncrementor = 2097152    //0x200000
i do not know where you got them from, but i guess they are from the kernel spi driver, they simply don't work for me,
any sugestions on how to call the macro SPI_IOC_MESSAGE(N) in #include <linux/spi/spidev.h> directly ?

maybe the problem isn't the macro.
I got the spi working because I changed the spiIOCTransfer type.
My kernel-version: 4.1.15+ #830
I did an spi-driver for myself with yet another interface (ReadWriteCloser):
https://github.com/quinte17/spi
maybe its working for you just to change the type?


Clean up obsolete Bash coding style in bootstrap.sh

If you are going to fix this line, why not make it right by shellcheck -s bash?
if [[ "$1" = '--force' ]] || [[ "$1" = '-f' ]]; then

Reading when -o or || is between is [[ ]] is more difficult. And you should always quote variables except when you want expansion.
=/==/ is covered in the Bash Wiki. This script targets Bash, and [[ (therefore ==) is understood by Bash. Only if you use [ must you use single =. In this project I do not think we are concerned about really old shells or alternatives like Dash.

@Tatsh For the record, shellcheck -s bash bootstrap.sh reported nothing to me. But I took your advices and changed the line as you suggested, thanks!

Hmm that is true. shellcheck tells me to get rid of -o and quote the variables to prevent globbing. But it does not care about || inside of [[ ]]. Also checked bashate and it too does not care. So I guess I just read this as 'best practises' somewhere and I've stuck with it ever since. I am sure my older scripts have horrible unreadable lines with lots of -o or || inside single [[ ]] tests.

@Tatsh Looks like you like this stuff, so I'll share a bit more details with you ;-)
I moved the || inside as you suggested because otherwise the highlighting in Vim was not great. That was already a reason enough for me.
I disagreed with "you should always quote variables except when you want expansion". For one thing, I think you should always quote variables that may contain spaces, typically filesystem paths. Another thing, in your example you quoted -f and --force which are not variables but literal strings. Lastly, the $1 at the left side don't need to be quoted at all. But I took your suggestion anyway, because consistently quoting everything invites less questions and doubts, which is a good thing. And although it's unnecessary to quote literal strings like -f and --force, again Vim highlighting works better if I quote them.
The commits and their messages that I pushed after your suggestion reflect my thought process and how I came to change the line exactly as you suggested. Thanks for the discussion!

@mathiasbynens any other questions or doubts?

I appreciate the patch, but I like my current Bash coding style.


Remove custom exception types

Fix CA1032 and CA2237 by removing unused exception types

Both of these exception types can probably be refactored out anyways. I can merge this in, or if you feel like just replacing all instances of CustomException and AbortEverythingException with Exception e, feel free.
They're left-over from an older version of the exception handler, and as of this point in time, they don't provide anything over Exception. The exception handler used to use these types when determining the options to provide (CustomException stated that it was coming from specific parts of the RTC, AbortEverythingException forced you to quit).

I might as well refactor out all of these old exception types while I'm here.

Removing the old exception type will require a simultaneous fix in Bizhawk_Vanguard. I'll work on that and link the PR in the description.

This can safely be pulled in once this PR is merged into Bizhawk-Vanguard. Until then, I'll leave this as a draft.

See https://github.com/ircluzar/Bizhawk-Vanguard/pull/10#pullrequestreview-433770022

Yep! I'll leave the AbortEverythingException type in. I believe the CustomException type can still be removed.


Implement & Test Java Lexer

@marcauberer Everything should be resolved now. Can you please check again, especially for

expectMultiple(): you somewhere told me that I could simplify my test cases using expectMultiple(). Can you check again if that is correct since I was "only" able to simplify some consume() methods in the Lexer - which is still great, just want to make sure that I didn't miss anythin.
Create constant EOF
Rename FileReader to Reader 😁
And more JavaDocs (Lexer, Token and TokenReader)

I've implemented it step by step, so the commit messages reflect only one change.


test edge-vsphere image

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

For vsphere datacenter6.7 and datacenter7.0-intel, when create vm from UI, user cannot select rhel 9, they can only select rhel 8. After talked to admin of vsphere env, they told me that we can still create rhel 9 vm on these datacenters, it just shows as a rhel 8 machine.


[BUG]: Country code defaults to CH, despite being in the US

Program version
3.4.0
Operating System
Windows
Type
GUI
Service
Crunchyroll
Command used
N/A
Show ID
any show
Episode
I use "download all"
Console Output
Your Country: CH

Additional Information
I do not use a VPN nor a proxy, and yet, it's doing this for some reason, and I can't think of why. And it's limiting my selection of crunchyroll...

 I had my VPN connected on my other computer connected via ethernet and it picked that PC's internet connection as a sort of bridge, for some reason, somehow. After disabling the ethernet cable ,it fixed it.


Improve visual design of rerun repo Readme

[x] Add top banner in the same style as the other marketing material
[x] Design any other assets that exist in the readme
[x] Go through the content to make sure it's clear and maps to the concept map

done!


Develop to next post 1.5.16

Blocked by #3569
Post-release housekeeping.

Musta clobbered a save... I'll fix once #3569 is merged.


PlayStation Vita: various comments

There are a few inaccuracies, errors, or other things to comment in the PS Vita Part 1 article:

Multi-use Port on marked motherboard

N.B.: the internal name for this port is MultiCn, a.k.a. MultiConnector.

The Slim revision retains the same architecture, but exchanges the OLED screen for an LCD to reduce costs. Furthermore, it doesn’t offer a 3G-capable variant anymore. It does, however, feature a bigger eMMC chip… only 52 MB larger! For some strange reason, that was enough to provide an internal 1 GB memory card. In any case, I’ll explain more in the ‘Games’ section.

I guess the Games section is missing, so maybe you planned to mention what follows there, but either way:

I'm not sure the 52MB increase is a reliable Fat->Slim metric - IMO, this is just a detail due to slight vendor/SKU differences
The internal 1 GB memory card can be enabled on Fat models as well, it's just that SCE never did so (all eMMCs are ~4GB)

The PlayStation TV is just a Slim motherboard adapted for the non-portable setting.

The PSTV motherboard is actually something unique. It lacks hardware found on the Fat or Slim (e.g., Fuel Gauge), but also has exclusive hardware (e.g., Ethernet adapter). If any comparison should be made, the PSTV would be "closer" to a Fat, as it shares many ICs with it (Kermit, PMIC, ...).

Many accelerators (some proprietary, others off the shelf), including an ‘AVC Decoder’

The AVC Decoder is not a dedicated hardware block, but a software decoder running on VIP (presumably Venezia Image Processor - it's a sort of Venezia-based DSP, but not much is known about it).

Cache coherency among the cores is automatically handled by the Snoop Control Unit, previously featured in the ARM11MpCore.

N.B.: the SCU only maintains coherency of Data Cache, not Instruction Cache

By the way, in the case of the Cortex brand, only the ‘Cortex-A’ profile includes this package (the ‘Cortex-R’ bundles an MPU instead and the ‘Cortex-M’ includes neither).

Cortex-M actually also features an MPU (see for example https://developer.arm.com/documentation/dui0552/a/cortex-m3-peripherals/optional-memory-protection-unit)

TrustZone: A new security subsystem that adds a dimension to the privilege levels of the MMU. It’s implemented on both the hardware level (by segregating buses between non-secure and secure peripherals)

On Vita, there is no "Secure" and "Non-Secure" bus - all memory transactions are performed on the same bus fabric (but transactions contain a "tag" indicated whether they are secure or not).

Now, the Cortex-A9 (found in the PSVita) improves the original design by applying significant enhancements [8]:
Multi-core support. This is most evident by looking at Sony’s choice of a quad-core package.

Did you mean to write Cortex-A9 MPCore?

On the other side, it’s worth mentioning that Thumb-2EE, the successor of the deprecated Jazelle, has been left unused or even excluded from many Cortex-A CPUs. I don’t think the Vita’s SoC even bothers implementing this.

The correct name is ThumbEE, not Thumb2-EE
While ThumbEE was initially advertised as Jazelle RCT, it is more than just a successor of Jazelle DBX (or simply Jazelle)
According to CPUID registers, Kermit implements both ThumbEE and Jazelle (and the Jazelle implementation is not trivial)
The OS implements the bare minimal support code for both (but as far as I know, no application makes use of either)

The master bus
Another popular product from ARM, the AMBA protocol designed for interconnecting components, carries forward with the Cortex-A9. Still in its third revision, the AXI subset was selected for interfacing the cores and external components outside the MPCore cluster. Curiously enough, it’s the same choice found in the ARM11 and its well-known adopter, the Nintendo 3DS.

AMBA is not a protocol in itself but a specification that describes various protocols, such as APB, AHB and AXI. While AXI was introduced in AMBA 3, the the third AMBA specification, there is no "third revision" of the AXI protocol.
Also note that the PS Vita interconnect fabric does not use AXI but Open Core Protocol (OCP).
The Cortex-A9 is presumably connected to the interconnect via AXI2OCP adapters.

An ‘Image Processing’ co-processor that executes 64-bit SIMD instructions. It can operate different packs of data, from eight 8-bit integers to two 32-bit ones.

N.B.: the coprocessor is called IVC2 (forgot what the abbreviation stands for).
Another important feature is that it has two 256-bit accumulator registers.

There’s another large block of 128 MB of Cached DRAM (CDRAM) predominantly connected to the GPU. CDRAM is yet-another type of RAM that combines the traditional (and cheap/slower) DRAM with a bit of SRAM [23]. The latter acts as cache to speed up frequent memory access.

CDRAM stands for Custom DRAM, not Cached DRAM. The CDRAM is just DDR2 SDRAM connected via a wide bus
to the SoC (similar to how VRAM is connected in GPUs).

Last but not least, the SoC also fits 16 KB of SRAM, but it’s reserved for system functions [24]. You may want to know that it’s the exact amount of SRAM also found in the PlayStation Portable, you’ll soon see why.

From reliable sources, I'm told that the 16 KiB Scratchpad is built in the Allegrex CPU (and thus only visible by it).
I'm not sure whether it's worth mentioning here; I think the following would be more fitting
Last but not least, legacy PlayStation Portable circuitry (the [MIPS CPU](https://www.copetti.org/writings/consoles/playstation-portable/#cpu) **- including its 16 KiB scratchpad -** and the [Graphics Engine](https://www.copetti.org/writings/consoles/playstation-portable/#graphics)).

On the other hand, there are various additional pieces of memory not mentioned (Camera SRAM, Spad32K, Spad128K, CompatSharedSram)

For the remaining I/O, MIPS is not physically connected to the rest of the hardware, only the Cortex-A9 is. Thus, the PSP emulation software (running on the MIPS CPU) requests services to the ARM CPU by following a protocol called ‘Remote Procedure Call’ (RPC) [27] [28].

RPC is not per-se a protocol name (see https://en.wikipedia.org/wiki/Remote_procedure_call)

Thanks for the corrections, I'm working on them now.

The CDRAM is just DDR2 SDRAM connected via a wide bus to the SoC (similar to how VRAM is connected in GPUs).

Do you know how wide (in terms of bits) the bus is?

Thanks for the corrections, I'm working on them now.

The CDRAM is just DDR2 SDRAM connected via a wide bus to the SoC (similar to how VRAM is connected in GPUs).

Do you know how wide (in terms of bits) the bus is?

According to https://web.archive.org/web/20150425204407/http://www.chipworks.com/en/technical-competitive-analysis/resources/blog/sonys-ps-vita-uses-chip-on-chip-sip-3d-but-not-3d/:

Close examination reveals that there are 1080 pads in two blocks of 540 (2 sub-blocks of 45 rows of 6 pads), so likely 2 x 512 bit I/O operation, possibly sub-divided into 4 x 128.

Looking at the first round of correction:

The PSVita deviates a bit from the official hardware implementation of TrustZone. Instead of using dedicated buses, its model relies on a single bus and 'tagged' transactions to indicate whether they are secure or not [@cpu-dmac].

Where is this official hardware implementation information from? The ARM Cortex-A Programmer's Guide says:

The memory system is similarly divided [between Normal and Secure world]. An additional bit, indicating whether the access is Secure or Non-Secure (the NS bit) is added to all memory system transactions, including cache tags and access to system memory and peripherals. This can be considered as an additional address bit, giving a 32-bit physical address space for the Secure world and a completely separate 32-bit physical address space for the Normal world.

(This bit is in fact AxPROT[1] - although we don't know yet what it is translated to at OCP level)
While the last sentence can be understood as saying "you have two separate buses", nothing in the rest of the paragraph seems to go against a shared bus with tagged transactions.

I think the 'separate bus' idea just got stuck with me while I was reading how TrustZone works. I've improved that section now and also included the rest of your corrections. Thanks again.

The CDRAM is just DDR2 SDRAM connected via a wide bus to the SoC (similar to how VRAM is connected in GPUs).

If we're using the chip works article as a reference point, the CDRAM, if it is the Samsung Wide I/O memory it's speculated to be, is SDR, not DDR

The CDRAM is just DDR2 SDRAM connected via a wide bus to the SoC (similar to how VRAM is connected in GPUs).

If we're using the chip works article as a reference point, the CDRAM, if it is the Samsung Wide I/O memory it's speculated to be, is SDR, not DDR

Which source do you think is closer to the truth?

I don't know of any source for Creep's wide bus DDR2 claim. I'm personally inclined to believing the chipworks article though, not many reasons not to.

My source was the Chipworks article but I have misread the relevant section:

(I treated the DDR2 SDRAM as applying to all memories, but the semicolumn clearly indicates it's only applicable to the conventional memory - which the firmware refers to as LPDDR{SUB/TOP/0/1} so there's no ambiguity on that one)
The Samsung paper mentioned says the implementation was SDR, and CDRAM is thus most likely SDR as Bythos mentioned:

(good catch! thanks @bythos14)

Thanks again @CreepNT and @bythos14 . I have amended that line.

I think this completes the list, but feel free to re-open it if you want to flag something else!


sig-buildsystem: nominate xpivarc and brianmcarey as approvers for sig-buildsystem

What this PR does
Before this PR:
sig-buildsystem did have only one approver.
After this PR:
sig-buildsystem has three approvers.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
n/a
The following alternatives were considered:
n/a
Links to places where the discussion took place:
Special notes for your reviewer
/cc @xpivarc @brianmcarey @fabiand @jean-edouard

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

~[ ] Design: A design document was considered and is present (link) or not required~
[x] PR: The PR description is expressive enough and will help future contributors
~[ ] Code: Write code that humans can understand and Keep it simple~
~[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)~
~[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required~
~[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test~
~[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.~
~[ ] Community: Announcement to kubevirt-dev was considered~

Release note

NONE

+1 both suggested approvers are long time KubeVirt contributors.
/approve

@acardace @jean-edouard WDYT?

+1!
LGTM
(not /lgtming to let others see as well)

+1! LGTM
(not /lgtming to let others see as well)

@iholder101 since noone objected here, would you want to lgtm now?

/lgtm


Support deinstantiation (mod.Close)

We need to eventually handle long lived processes, and graceful shutdown. If we had a way to deinstantiate a module, I think we can also handle a WASI quit signal scoped to module instead of the host process (#290)
I think we should make a new type that implements ModuleExports called wazero.InstantiatedModule (we maybe need this for host also, but let's start with normal modules). The only additional function there would be .Close and this would have the following effects.

set a goroutine visible status on the internal moduleInstance  closeCalled

this may need to be an array of length one to ensure visibility across goroutines, and 1 means closeCalled

make shared implementations err if they see this status which will cause existing functions to exit

make engine.call implementations check this status prior to invoking new functions and return an error (I think this handles table also as table is only call_indirect and not exposed otherwise)
make memory, global implementations check this status before read/write and return an error

ensure calls begin with a CancelContext added to the callEngine, and invoke that hook so that any host functions doing I/O finish.

this could possibly be limited to wrapping the context in wazero.StartWASICommand as maybe non-wasi shouldn't be doing I/O anyway

remove all the references for this module in Store added by instantiate

ensure nice errors when calling an imported function, memory, table or global that was removed

This would also be needed for wapc-go (cc @pkedy) because it is otherwise a memory leak. For example, modules are instantiated with instance counters, which I assume would eventually run out of memory depending on the scope and frequency of creation (remember memory is required by WASI and minimum memory is 64KB).
// Instantiate creates a single instance of the module with its own memory.
func (m *Module) Instantiate() (wapc.Instance, error) {
	moduleName := fmt.Sprintf("%d", atomic.AddUint64(&m.instanceCounter, 1))

There's a not really documented thing in AssemblyScript that would also needs this for abort handling. If someone can find docs on it please do!
// envAbort is the AssemblyScript abort handler.
// Ex in WebAssembly 1.0 (MVP) Text Format:
//	(import "env" "abort" (func $~lib/builtins/abort (param i32 i32 i32 i32)))
func (t *thing) envAbort(ctx wasm.ModuleContext, messageOffset, fileOffset, line, col uint32) {
	t.module.Close()
}

Note: AssemblyScript maybe maps this function to WASI sigabrt ...

yeah we also tweak Engine interface so that we can unmap the MMapped memory regions

so the preliminary work #294 has just landed, so the next is to make store goroutine-safe


More Global Options Missing

invoke, invokeOut, scrollcallback, etc are missing in jos global options

added & fixed few more global properties that were missing or in accessible


increase timeout for replication in tests

follow up to https://github.com/crate/crate/pull/12276 - the test still fails often on CI and fails consistently on my Windows laptop (passed only with 100 locally but I guess CI machine should be fine with 50 given that it passes sometimes even with 30)
Checklist

[ ] Added an entry in CHANGES.txt for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

I'd suggest to first see if #12283 maybe solve the timeout issues.

retest this please


[Core-1195] Include Android Notification

Android test checked by Daniel Kang.
Iphone test checked by Miyoung Han.

@intoxicated pr check


Add data rebalance function and set score name according the model spec name when eval

set model score name according the model spec file name
add function to rebalance data when shuffling the dataset
https://github.com/ShifuML/shifu/issues/662

Thanks Zhanghao for this PR :)
Could you summarize changes in this PR? Saw 18 files changed and not clear how i can review it.

There are mainly two changes - 1) set model score name according the model spec file name (before we always use model0, model1, ...); 2) for example if the positive rate is too now, user can adjust positive rate when shuffling norm/clean dataset.  We achieve this by duplicate positive records or adjust the weight of positive records.


$translate.refresh() doesn't clear all keys of $translateTable.

I am using angular-translate on my project. Where I loads the vocabulary on module basis. Now on change preference on application level, I need to clear all the previously loaded vocabularies. I am using $translate.refresh() to load the keys again on further navigation on modules but it loads the translates for current used key only while I want to load the translations keys again on navigate on that particular module after use $translate.refresh() once.

Hello, @gsaini.
The purpose (or, probably, task) of the $translate.refresh() method is to refresh translation tables which are currently present in the $translate module. So, this method deletes old translation tables from the module and asynchronously loads their newer version.
If you want to change the translation table, then you have to combine the $translate.refresh() method with some loader. Something like this:

Configure the loader to return another translation table
Call the $translate.refresh() method

Can you please elaborate which you suggested above or any eaxmple?
& I suggest, It would be great if you can provide $translate.refreshAll() method which can be use to clear all translate tables.

Hm... Really there is a problem. Thanks, @gsaini.
I'm not sure if I am right, but this scenario will lead to error:

Use some lang1 language
Use some lang2 language
Refresh translation tables
Use the lang1 language

Here we will get the old version of the lang1 translation table. It happens because we delete only those translation tables which were re-loaded from the server.
See here: https://github.com/angular-translate/angular-translate/blob/a2ac7000f94bcee6dd8e206cab5d7cec3527dd25/src/service/translate.js#L1651-L1654
@angular-translate/core, is it appropriate to delete all existing translation tables in case the new ones were loaded successfully? Do we need to re-load only the current languages or all languages which were loaded during the current session (this question can also affect separation of fallback language handling)?

In general, a refresh() should refresh the things. So it is looking from the outside like being a bug when a translation has not been refreshed (case: a language is neither a fallback nor active but has been used in the past). I'm not sure if we really should reload all the languages. It would be sufficient ditching them only.
However, one problem is not solved and perhaps that's the original intent for that refresh strategy: If the reloading language was not injected via an async loader (i.e. predefined statically), the translations would be gone forever. This is actually true already nowadays, but only when being a fallback or in use.

@knalli, they won't be missed. An Error will be thrown from the refresh method in case a loader is not specified.
Okay, then. I'll remove all translation tables in that case.

@DWand  You do not get me right: We do not define loaders for a specific language, but in general.

Setup phase:
At first you are add statically translations for language A.
Additionally you are defining a standard url loader.

You are switching the language B.
The new translation will be loaded and everything is okay.
You are invoking a refresh()
Until now: Only B will be refreshed because it is active. A will be untouched and still be available.
With your change: Both A and B will be discarded. A will be fetched by the loader the first time on next demand.

Yeah, this change is intended, but the result could be a problem for anyone using the default static provisioned translations only for static defaults (in case of issues while determining the correct language). Perhaps an opt-in is better..  refresh(true)

@knalli, but we do already have a parameter to specify a language to be updated.
Is the use case you've mentioned common? It looks more like workaround.
Consider the partial loader is used in the application. If we want to refresh translation tables as a result of structural changes in the loader the first scenario will cause real bugs, while the second one might add some uncomfortable delays. Also, this loader provides an ability to specify static parts - they'll be fetched without any xhr requests.

I'm only saying this could cause trouble for some. I would highlight this at least in the release notes. IMHO the translations should be always available via a loader or never. The mixed mode is not really supported (well, it works using the method I've described).

@knalli, such behavior is actually documented in our API docs :smile: So, yeah, this is definitely a bug.

Huh? Where? Also in the code on api level?

@knalli, it is mentioned here:

links to the current master tree: https://github.com/angular-translate/angular-translate/blob/a2ac7000f94bcee6dd8e206cab5d7cec3527dd25/src/service/translate.js#L1590-L1592 and https://github.com/angular-translate/angular-translate/blob/a2ac7000f94bcee6dd8e206cab5d7cec3527dd25/src/service/translate.js#L1602

links to the current canary tree: https://github.com/angular-translate/angular-translate/blob/3facb92487efab8f4a7ed6a2eac6c9812f1c01b9/src/service/translate.js#L1657-L1659 and https://github.com/angular-translate/angular-translate/blob/3facb92487efab8f4a7ed6a2eac6c9812f1c01b9/src/service/translate.js#L1669

That's why, I think, this issue can be considered as a bug - the current behavior differs from what is documented.

Ok.

@gsaini, some changes were merged to the canary branch. Can you check whether the issue is solved?

@knalli @DWand - I am getting the below issue after using the angular-translate.js (build of canary branch from dist folder).
TypeError: preferred.split is not a function
at negotiateLocale (angular-translate.js?dc=1430365756901:183)
at Function.$get.$translate.use (angular-translate.js?dc=1430365756901:1563)
at Object.app.config.getTranslateKeys (states.js?dc=1430365756901:45)
at Object.invoke (angular.js?dc=1430365756901:4169)
at proceed (angular-ui-router.js?dc=1430365756901:411)
at invoke (angular-ui-router.js?dc=1430365756901:407)
at study (angular-ui-router.js?dc=1430365756901:386)
at $Resolve.resolve (angular-ui-router.js?dc=1430365756901:490)
at resolveState (angular-ui-router.js?dc=1430365756901:2889)
at Object.transitionTo (angular-ui-router.js?dc=1430365756901:2601)

@gsaini : Using http://plnkr.co/edit/S0rxYOJRReUDGeLwWXlr?p=info as boilerplate, you can please make a test case?

Anyway. Fixed that possible npe 1aaab98, however, I'm quite not sure why getLocale() should return non string.

And rest was done already. Closed.


Replace mysql-client with mariad-client.

Coverage remained the same at 87.532% when pulling 18cd2101f12a669fcecf0fdbd2188e97020efbf1 on akatsoulas:mariadb-client into db75246026ae23d3c007295cd32961ac74e2d95b on mozilla:master.


client: handle xhr.open() errors

Closes #1149.

Good catch. Thanks!

Wow. You're incredibly fast.
Thanks dude!

Looks like CI failed for unrelated reasons: https://travis-ci.org/visionmedia/superagent/jobs/190088001


[BUG] completed run does not show on on retrieve page properly... waits forever

there is another PR open for this. re-opening the ticket


[IOTDB-1251] optimize route intervals

When data is not partitioned, all data of a sequence is stored in partition 0. Therefore, during the query, we only need to route to partition 0 regardless of the interval. Therefore, partition calculation is not performed.
This reduces the time spent on partition calculation and routing to other partitions.
Current problems:

When
firstLB == Long.MIN_VALUE || lastUB == Long.MAX_VALUE
route all partiongroup.
For other time conditions, partition calculation is performed.

@LebronAl @neuyilan @mychaow @jt2594838 , hi could you please review?
Thanks


Stale branches

transferred_issues
On this branch we have 3 transferred issues:

272 and 277 is completed
276 is partially out of scope and partially a duplicate of #99

ngff-api
This was a temporary dev branch and has been further developed in #45
@mattersoflight Can we delete these?

@ziw-liu yes makes sense to delete the above branches. Thanks.

Done.


fix(Filesystem): upgrading to standard filesystem

:tada: This PR is included in version 7.0.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Could not upload through proxy

Hello, rustup-init failed :
info: syncing channel updates for 'stable-x86_64-pc-windows-msvc'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to 'C:\Users\xxxx\.rustup\tmp\_p5zko48h1tojccg_file'
info: caused by: error during download
info: caused by: [7] Couldn't connect to server (Unsupported proxy scheme for 'https://xx.xx.xx.xx:8080')

Press the Enter key to continue.

Thanks for the report @Harvey13 !

syncing channel updates for 'stable-x86_64-pc-windows-msvc'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to 'C:\Users\xxxx.rustup\tmp_p5zko48h1tojccg_file'
info: caused by: error during download
info: caused by: [7] Couldn't connect to server (Failed to connect to static.rust-lang.org port 443:Timed out)
Press the Enter key to `continue.
is this the same problem?

I have this same issue. Has anyone got an answer for it?
Is there a way to download the full installer as a zip file so that I can install it on my Windows machine in the office. I could potentially install it on my laptop at home, but that doesn't get it on my desktop PC.
Thanks

I found it. There is a stand-alone installers section on this page: https://www.rust-lang.org/en-US/other-installers.html


Run error when using edition = "2018"

I just ran into the following error:
cargo tarpaulin -v
Error during run

Version:
cargo-tarpaulin version: 0.6.8
OS:
Linux x op 4.17.14-arch1-1-ARCH #1 SMP PREEMPT Thu Aug 9 11:56:50 UTC 2018 x86_64 GNU/Linux
rustc:
rustc 1.31.0-nightly (77af31408 2018-10-11)
Reproduce by creating a new project using nightly:
cargo +nightly new foo

I noticed that when removing the edition = "2018" in the Cargo.toml tarpaulin works without problems.

You need cargo-features = ["edition"] at the top of your Cargo.toml. I've had this raised last week to me and the error messaging on develop is better now so when that comes out it'll be clearer.
I'll probably add something to the README as well!

Ah great! Should have searched the closed issues. Thank you =)!:

So I'm traveling so realistically won't get to do this until around Friday. If sometime wouldn't mind doing a PR adding a "Using with Editions" subsection after installation I can approve it I'd be grateful (and do it on master so it's visible to users)

So the code the checks for this feature is all in the cargo dependency, I just work off the Result<_,_> types it's functions output. So it'll be down to how I'm using cargo as a library. Unfortunately parts of it aren't well documented because the vast majority of users are using it as an executable not a library.
If anyone can help with the cargo thing that would be better than the README change for sure! I'm just going to reopen this issue as it's clearly not yet resolved.

Uhh...at least for me this works without putting cargo-features into my cargo.toml.

Just tested following the 2018 edition being stabilised cargo-features is no longer required. So I'm closing this issue


MIT License

Hi, I was wondering if you could add an MIT license so we could try to use this in our projects. Thanks for your work!

No problem, added a MIT License now.
I hope it may be of use in your project!

Thanks!


Reverse Level Order Traversal

In this issue,
Problem Statement: Given a binary tree of size N, we will find its reverse level order traversal.
Input:
10
/
20   30
/  \
40  60
Output: 40 60 20 30 10
Explanation:
Traversing level 2:  40 60
Traversing level 1:  20 30
Traversing level 0:  10
Languages: C++,Java
Please assign me with this issue:
@plazzy99 @rudrakshi99 @nakul-19 @tarun26091999 @OjusWiZard @shreyanspoddar @raksha009 @anjul2000

Hey , this side is Hritik Khurana , GSSOC'21 Participant , looking for 1st pr , please assign this issue to u . I will write code in C++,
Please assign me :
@plazzy99 @rudrakshi99 @nakul-19 @tarun26091999 @OjusWiZard @shreyanspoddar @raksha009 @anjul2000

hey @tarun26091999 can i work on this issue in python?
Thank you!

The issue is not assigned to you.


Plugin Appears to Break Builds With Gradle 8.1, Causing org.objectweb.asm.MethodTooLargeException

With Gradle 8.1 and the following "minimal" project setup all Gradle targets fail with the same exception if the Azure Functions plugin is part of the configuration. Commenting out the Azure Functions plugin makes the build work again.
plugins {
    id("org.springframework.boot") version "3.0.6"
    id("io.spring.dependency-management") version "1.1.0"
    kotlin("jvm") version "1.7.22"
    kotlin("plugin.spring") version "1.7.22"
    kotlin("kapt") version "1.7.22"

    // The plugin will cause Gradle 8.1 to fail with an exception: Method too large
    id("com.microsoft.azure.azurefunctions") version "1.12.1"
}

Running a clean (or any other target) yields a org.objectweb.asm.MethodTooLargeException:
$ ./gradlew clean --stacktrace

FAILURE: Build failed with an exception.
[..]
* Exception is:
org.gradle.api.ProjectConfigurationException: A problem occurred configuring root project 'gradle-playgroud'.
        at org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:84)
        at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:77)
[..]
Caused by: org.objectweb.asm.MethodTooLargeException: Method too large: com/azure/resourcemanager/appservice/implementation/WebAppsClientImpl.$deserializeLambda$ (Ljava/lang/invoke/SerializedLambda;)Ljava/lang/Object;
        at org.objectweb.asm.MethodWriter.computeMethodInfoSize(MethodWriter.java:2088)
        at org.objectweb.asm.ClassWriter.toByteArray(ClassWriter.java:511)
        at org.gradle.internal.classpath.InstrumentingClasspathFileTransformer.lambda$visitEntries$1(InstrumentingClasspathFileTransformer.java:211)
        ... 15 more

The same project setup works with Gradle 8.0.

@rsteppac Thanks a lot for your report, we will investigate this issue soon

@Flanker32 , I just tried the same setup with Gradle 8.1.1 and that works. So it might not be the plugin's fault after all?
Gradle

8.0 works
8.1 works not
8.1.1 works


Issue with in-path parameters

Hi. Thanks so much for providing this library, it's the simplest and lightest I found so far!
I have an issue when generating a Tyepscript client library though. I have a resource definition like this in swagger:
    "/apis/myresources/{id}": {
      "get": {
        "operationId": "GetMyResource",
        "parameters": [
          {
            "name": "id",
            "in": "path",
            "required": true,
            "type": "string"
          }
        ],
      },
    },

Which generates the following Typescript client code:
    public GetMyResource( id:string ):Promise<apiMyResource>{
        const params = {
            "id":id
        };
        return new Promise<apiMyResource>((resolve, reject) => {
            request
            .get("/apis/myresources/{id}")
            .query(params)
            .end(function(error, res){
                if(error){
                    reject(error);
                }else{
                   resolve(res.body as apiMyResource);
                }
            });
        });
    }

This doesn't seem right to me though, since now the request goes to /apis/myresources/{id}?id=123 instead of /apis/myresources/123. Is there anything I missed here or does this need a fix?

I'm also having this issue. As far as I can tell, URL parameters aren't supported at all.

Can you check the latest version from github not NPM? I cant remember exactly but I changed something to do with the querystring in one of my PRs.
If not should be an easy fix.


Registration System Is Missing...

@abhay-raj19 hello, there is no registration system is not present in the website. please assign me to add the features rich registration system.

@nishantmakwanaa Proceed with the idea


Can't signing anymore ?

Hi,
Someone reported me this issue that I'm also able to reproduce.
abc@82ddd3721216:~/workspace/finary_uapi$ python -m finary_uapi signin
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/config/workspace/finary_uapi/finary_uapi/__main__.py", line 452, in <module>
    sys.exit(main())
  File "/config/workspace/finary_uapi/finary_uapi/__main__.py", line 155, in main
    result = signin(args["MFA_CODE"])
  File "/config/workspace/finary_uapi/finary_uapi/signin.py", line 50, in signin
    if xjson["response"]["status"] == "complete":
KeyError: 'response'
abc@82ddd3721216:~/workspace/finary_uapi$

I'll have a look asap.

Mmm I can't reproduce. Do you have MFA on ?

Yes I think I enabled it just recently.
I'm gonna try to remove it if you want.
Le mer. 21 févr. 2024 à 20:42, Nicolas Froment @.***> a
écrit :

Mmm I can't reproduce. Do you have MFA on ?
—
Reply to this email directly, view it on GitHub
https://github.com/lasconic/finary_uapi/issues/177#issuecomment-1956254690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE7NT2HJ6S4MMBZJ4FHA7ELYUW6P3AVCNFSM6AAAAABDSUFDHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGI2TINRZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok I'll add it and test.

It works with 2FA as well.
The code assumes it works. I could add more information if the second call with the 2fa code is not successful. Let me know if you find the root cause.

Deactivating 2FA makes it work again.
Can you try activating it and try again signin 24h+ later (I don't how caching work)?

Got multiple feedback with the same issue from diferent users.
You still not able to reproduce it?

FYI: https://community.finary.com/t/mise-en-place-obligatoire-du-2fa/12549

I'm sorry I can't reproduce. I have 2FA on in finary. I open Google Auth on my phone, run "signin MFA_CODE" where MFA_CODe is the code I read on my app and it works, I'm signed in.
The error message you see is exactly the one I get if I sign in with 2Fa activated by without the 2FA code passed to signin. Are your users aware that they need to pass the 2FA code when they sign in ?

I think Finary is starting forcing 2FA usage for somme user without updating the end user configuration as it deactivated on front-end but some users still experiencing the issue.
While activating the 2FA and passing the generated code through seems to work.
I have one user still having the issue but I'll ask him to force update dependencies to make sure it is not something else. He is not on github so trying to help him as much as I could.

I guess we can close this issue ;)
I was able to reproduce it anymore since I forced using 2FA due that I use Crypto Finary services.


[Revise subclass] isolated congenital microcephaly

Mondo term (ID and Label)
isolated congenital microcephaly
Suggested revision and reasons
All of the descendents are Mendelian and I think we need to define this term as Mendelian and place it under a (partially revised) neurogenetic hierarchy. @ahamosh  thoughts?

I agree.  I am confused by all the parents this has.  Congenital microcephaly is different from acquired microcephaly.  Isolated is different from syndromic.  Let's discuss tomorrow.

microcephaly is usually described as primary or acquired - primary is where you are born microcephalic and acquired is you are born with a normal head size but it eventually is relatively small (does not grow)
we have
'autosomal dominant primary microcephaly' and 'autosomal recessive primary microcephaly'- which are hereditary
should 'isolated microcephaly' be in HPO rather than Mondo?
it makes sense to classify 'isolated congenital microcephaly' as Mendelian. May want to add hereditary to the label.

You can have microcephaly from congenital CNV, the feature is not always Mendelian. However, we would not call the disease "CNV microcephaly" but rather "congenital CNV" and the microcephaly is a feature.
We usually say primary or secondary microcephaly, I think, not "acquired".
I believe all of the diseases that we call " microcephaly are Mendelian (although microcephaly is a feature of many other diseases). My suggestion is the change the name of the term from
isolated congenital microcephaly
to
Familial microcephaly
and to put this under a neurogenetic branch.
@ahamosh  does this sound good?

Can we make it hereditary microcephaly instead of familial microcephaly.  People are moving away from familial because of de novo variants.


Add a type_name function to print a variable's type

Taken from http://stackoverflow.com/a/20170989/64537

SO cannot be wrong

:smile: agreed


Possible bug: Compiler regards nullable type as non-nullable when building for iOS

I've encountered with strange compiler behavior. It is regarding nullable type as non-nullable.
I have a mixin:
@optionalTypeArgs
mixin RemoveOrAddUserToEventMixin<T extends StatefulWidget> on State<T> {
  void Function(html.Event)? _onVisibilityChange;
  void _webVisibilityChange(final html.Event event) {
    if (html.document.visibilityState == 'visible') {
      print('WARN tab is active');
      print('WARN ${html.window.history.state}');
      if (_onVisibilityChange != null) {
        html.window.removeEventListener('visibilitychange', _onVisibilityChange);
      }
    } else {
      print('WARN tab is inactive');
    }
  }
}

Although html.window.removeEventListener has nullable listener parameter:

The Compiler considers it to be non-nullable and throws exception, when building for iOS:
Error (Xcode): lib/features/events/presentation/ui/mixins/remove_or_add_user_to_event_mixin.dart:23:61: Error: The argument type 'void Function(Event)?' can't be assigned to the parameter type 'dynamic Function(Event)' because 'void Function(Event)?' is nullable and 'dynamic Function(Event)' isn't.

Could not build the application for the simulator.
Error launching application on iPhone 15 Pro Max.

And it is pointing to the line with html.window.removeEventListener. At the same time there is no exception when building for web. Also Analizer doesn't show any problem.

What is html? If this is something like package:universal_html then you should report a bug to them: they likely use conditional imports depending on the platform and the signature of method used on VM does not match the one used on Web.

dart:html has EventListener? listener,
their code has non-nullable value: https://github.com/dint-dev/universal_html/blob/45116f0a5125124ce2fbedaa589303e236350217/lib/src/html/api/event_target.dart#L138

(I am not sure what this html is supposed to do on iOS - where things are not running in a browser).

What is html? If this is something like package:universal_html then you should report a bug to them: they likely use conditional imports depending on the platform and the signature of method used on VM does not match the one used on Web.

dart:html has EventListener? listener,
their code has non-nullable value: https://github.com/dint-dev/universal_html/blob/45116f0a5125124ce2fbedaa589303e236350217/lib/src/html/api/event_target.dart#L138

(I am not sure what this html is supposed to do on iOS - where things are not running in a browser).

Yes, forgot to mention, it's package:universal_html. Thank you for pointing it out, it really seems to come from the package.


Add support for 'add member' in room API

Add Room#member method which allows to add member to room.
https://www.hipchat.com/docs/apiv2/method/add_member

Build fails are not related to this my changes in the gem (caused by statistics mocks (from master)).