Oracle Database 12c EE -ORA-48122: error with opening the ADR block file

I ran Oracle Database image as following command. However error that DB instance could not create ADR file has happened. Whole log is following.
> docker run --name orcl -p 1521:1521 -p 5500:5500 -e ORACLE_SID=orcl -e ORACLE_PDB=pdb1 oracle/database:<IP_ADDRESS>-ee

ORACLE AUTO GENERATED PASSWORD FOR SYS, SYSTEM AND PDBAMIN: 1kVjkSBHSjg=1

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 27-DEC-2016 16:28:35

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Starting /opt/oracle/product/<IP_ADDRESS>/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/4c5a2d9ca68f/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                27-DEC-2016 16:28:35
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/4c5a2d9ca68f/listener/alert/log.xml
Listening Endpoints Summary...

SQL*Plus: Release <IP_ADDRESS>.0 Production on Tue Dec 27 17:08:10 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>
System altered.

SQL>
Pluggable database altered.

SQL> Disconnected from Oracle Database 12c Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
#########################
DATABASE IS READY TO USE!
#########################
Tue Dec 27 17:04:48 2016

ERROR: ORA-48178 encountered when checking if the process is able to
ERROR: create the ADR schema in the specified ADR Base directory [/opt/oracle]
ERROR: The ORA-48178 error is caused by the ORA-48122 error.
ORA-48122: error with opening the ADR block file [/opt/oracle/diag/rdbms/orcl/orcl/metadata/ADR_INTERNAL.mif] [0]
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 22: Invalid argument
Additional information: 2
ERROR: Check if the directory is readable and check if the OS version is supported for ADR.
ERROR: The process will switch back to the pre-ADR method of tracing and logging.

I ran the command on following environment. Especially differences between with common environment is that this docker host use ZFS storage driver and Unbreakable Enterprise Kernel on Oracle Linux.
>  docker info
Containers: 15
 Running: 9
 Paused: 0
 Stopped: 6
Images: 98
Server Version: 1.12.3
Storage Driver: zfs
 Zpool: error while getting pool information strconv.ParseUint: parsing "": invalid syntax
 Zpool Health: not available
 Parent Dataset: storage/docker
 Space Used By Parent: 13221888
 Space Available:<PHONE_NUMBER>88
 Parent Quota: no
 Compression: off
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge overlay null host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.1.12-61.1.19.el7uek.x86_64
Operating System: Oracle Linux Server 7.3
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.11 GiB
Name: home
ID: 5N6W:2EGL:XOSR:U3IY:5RHG:T2MG:YCCR:4LP7:PSLX:ERRT:QJ4M:EK6O
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
 provider=generic
Insecure Registries:
 <IP_ADDRESS>/8

Database instance seems to write to /opt/oracle/diag directory using O_DIRECT. However any file system such as NFS and ZFS can not use O_DIRECT.
If docker host use these file system as /var/lib/docker , Database instance can not create file to  /opt/oracle/diag. Docker container need to mount /opt/oracle/diag onto other file system such as ext4 on docker host.

We don't support ZFS on Oracle Linux at all, so this is a completely unsupported environment.


[SUPPORT] Does Hudi support just column re-order?

Does Hudi support column re-ordering if there are no column additions/removals? According to https://hudi.apache.org/docs/schema_evolution/, it states that "Add a new nullable column and change the ordering of fields" is not supported. So if I perform only the 2nd half of that statement, which is "change the ordering of fields", will Hudi support this?
To Reproduce
Steps to reproduce the behavior: In my test script, I have 3 sets of data, 1) initial data, 2) update 1, 3) update 2. In update 1, I'll be re-ordering the columns.

Run test script: TestData.txt
Observe output.
Initial Data

Update 1

Update 2

Expected behavior
Does Hudi officially support just column-reordering? My existing Hudi table may have a certain column order, while the incoming data batch will contain the same columns but in different order.
ENVIRONMENT:
AWS EMR: 5.33.1
Hudi version : 0.7.0-amzn-1
Spark version : 2.4.7
Hive version : 2.3.7
Hadoop version : 2.10.1
Storage (HDFS/S3/GCS..) : S3
Running on Docker? (yes/no) : no

I don't think its supported as of now. Its actively been worked upon.
You can follow the progress here.
CC @codope @xiarixiaoyao

@WTa-hash
Hudi can't support column order adjustment very well at present, and rfc-33 is doing this
We are testing rfc-33 in a production environment, once done will update the pr.

Great to see rfc 33 moving and thanks @xiarixiaoyao for driving the work there! @WTa-hash if no further questions, let's close this. thank you.


featuresupport delete condition

Proposed changes
[Vectorization]Support delete condition in Storage layer
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

I'll add some UT tests later

hi @wangbo , please resolve the conflict

@morningman conflicts has been resolved


[Backend] Search a keyword on Google

Resolve https://github.com/Lahphim/go-crawler-challenge/issues/14
What happened 👀
Provide a service for searching data in the Google according the keyword.
Insight 📝

[x] Create a service for scraping google result with a given keyword
[x] Collect result with some expected selector

Extra:

Set up colly : lightning fast and elegant scraping framework for gophers
Set up go-vcr : simplifies testing by recording your HTTP interactions and replaying them in future runs in order to provide fast, deterministic and accurate testing of your code.

For colly's configuration, I use this configuration here below because I want to specific to just only one latest browser for scraping the page.
const currentBrowser = "Chrome/88.0.4324.182"
const currentOs = "Macintosh; Intel Mac OS X 10_15_5"

These are selectors which using to scrap content.

"nonAds": #search .g .yuRUbf > a
"bottomLinkAds": #tadsb .d5oMvf > a
"otherAds": #rhs .pla-unit a.pla-unit-title-link
"topImageAds": #tvcap .pla-unit a.pla-unit-title-link
"topLinkAds": #tads .d5oMvf > a

Proof Of Work 📹
We can submit keyword from /dashboard page.

Searching with keyword nintendo, it shows result like this.
Visit link: https://www.google.com/search?q=nintendo&lr=lang_en

@Lahphim What about the HTML code of the pages? How are we going to store them? 🤔

@carryall @olivierobert I've created a helper function to random a user agent for the fixed user agent issue already ✌


pull request for e2e test at 02/03/2017 17:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Don't cache MongoLockProvider in the integration test

The properties tested in the abstract test suite should still hold, even when the lock provider is created on demand (it's synonymous to multiple clients trying to acquire the lock). Unfortunately, when only a single instance is used in the test, it's easy to make an uncaught mistake when writing a custom implementation. In my case I've made an error of using regular set updates in my insertRecord implementation (instead of correct setOnInsert) and all tests still passed.

Thanks

@lukas-krecan-lt I have another PR with an actual improvement to the Mongo provider lined up for submission once/if you merge this :)

Hi, I'd like to merge this but tests do not pass in the PR. They are quite fragile, but it seems that your change breaks them (I have no idea why and how). I want to look at it over the weekend.

Released as 2.1.0


DIMSE Message classes command field elements should be set using pydicom

For some reason they're all set by hand. A better way would be to build them into a command set attribute using pydicom.
I suspect the code predates the inclusion of command elements into pydicom

This is a fairly large change as its been rolled into a refactoring of the way the DIMSE Message classes are constructed and implemented, but so far it seems to be working OK

Completed in 97b6059a6714a8d6bd8281fed9429e30269c5668


First class App Insights integration

Today it is possible to integrate Azure Functions with Visual Studio Application Insights by manually referencing the app insights SDK and updating your function code to send metric/event/exception data. Unfortunately this is lots of work, error prone, and still won't capture everything (e.g. if an error occurred while flushing an output, this will occur after execution has left user code and won't be captured by any user catch block).
Ideally, Azure Functions users could turn on first class app insights support, perhaps built on top of a rich host level eventing model as discussed in #281.
More discussion is required to figure out exactly what behavior needs to be configurable and what should be turned on by default once the customer enables the integration.

It would be great if a basic version of this can be added soon. For instance, if an instrumentation key is provided (app setting or in host.json), fire function execution events (success/failure, duration) and exceptions into App Insights. That would be a great start. The existing tooling in the functions portal for viewing metrics and exceptions are difficult to use, especially for apps that have a lot of invocations.
AWS Lambda will apparently have something similar soon with their X-Ray integration.

+1

+1

+2

A quick update - we're beginning work on this. Expect more activity on this topic in February.

Can you please provide an update on this as we are eagerly waiting on this?

Great progress. We've got private deployments running with Application Insights and the experience is a huge improvement, very excited. We'll be sharing some information how to use the private bits soon, but hopefully will have it fully integrated in the next 2-3 months.

If you're interested, we have an early preview of Application Insights integration available. See here for details: https://github.com/Azure/Azure-Functions/wiki/App-Insights-Early-Preview

Can this issue be closed now?

Yes, thanks.
Sent from my Windows Phone

From: Mathew<EMAIL_ADDRESS>Sent: 5/23/2017 3:31 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [Azure/azure-webjobs-sdk-script] First class App Insights integration (#727)
Can this issue be closed now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-webjobs-sdk-script/issues/727#issuecomment-303551235, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANIhbR95QMa-0ttUn1iCtpAxokR7UmgAks5r814HgaJpZM4KIJqm.

@mathewc - it depends on if we want to wait until it's GA or not. I don't have a strong opinion on how to manage that.

We'll open new issues to address moving AI support to GA.

I filed a top level issue for tracking the GA here:
https://github.com/Azure/Azure-Functions/issues/388


strange content in security best practices page

"Using the default session cookie name can open your app to attacks" - what?
Using hpkp is not a best practice, it's a foot cannon

Using the default session cookie name can open your app to attacks

If your session cookie name is named "session" (default), it gives away two things:

You are likely using Express (server fingerprinted)
Since you love defaults, even your cookie signing keys may be one from the examples or the Keygrip default: "key1", "key2", "keyboard cat", "sha1". Since I know the keys, I can tamper your session cookie at will rendering signed cookies meaningless.

Using hpkp is not a best practice, it's a foot cannon

It is being realized over time that HKPK was actually not such a clever idea. Explained here - https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/he9tr7p3rZ8/eNMwKPmUBAAJ

If the concern is server fingerprinting, it would be better to do the right thing by default - randomize it if not configured.

The HPKP thing, OTOH, should just be removed.  It's bad advice.


webapp:Upon deleting a service plan, it is not possible to recreate it for same resource group + region

This is autogenerated. Please review and update as needed.
Describe the bug
Upon deleting a service plan, it is not possible to recreate it for same resource group + region. I have tried redoing it for days after deleting the initial service plan and had to temporarily create one for a different region, i.e. East Asia instead of SoutheastAsia. Currently in QA, but clients will not accept this on production.
Command Name
Bug is appearing using 3 means: ARM templates, CLI, manually via Portal.
Errors:
"Cannot find Web space rg-big-paceaisph-dev-SoutheastAsiawebspace for subscription 878ee15c-1efd-43de-b6ad-3f7e15338b1d. (Code: NotFound)"
Initially I was getting error of the type 'already exists', then message switched to the above 'cannot find'.
In either case recreation of the service plan, regardless of name, for same RG + Region is impossible.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Portal:
subscription: BIG SFA Project (id: 878ee15c-1efd-43de-b6ad-3f7e15338b1d)
resource gr: rg-big-paceaisph-dev

Local:
Windows-10-10.0.17763-SP0
Python 3.6.6
azure-cli 2.0.69 *
Shell: powershell.exe

DevOps Pipelines:
...

Additional Context
We cannot allow ourselves to face this issue on Production.

This not specific to CLI,  we will talk to our experts & get back to you. Just to confirm are you trying to create the AppservicePlan with the same name?

Hi there,
Yes, it is not specific to CLI, but this is the only suitable place I found to submit an issue, I am still waiting on permission from our Portal subscription admin to let me submit through there, it may take a while.
Also, I have tried using same SP name, then I tried with different name. Changing name of SP did not work, I got around the error only after changing the region. It's a work-around I can get around in QA, but later in the project this will not be doable.

@azlatarov-cocacola  can you share the CLI commands you run here for creating the ASP the full end to end list , including your workaround command. Thanks!

It's ran through an ARM template executed by a devops pipeline, the json is following:
    {
        "condition": true,
		"type": "Microsoft.Web/serverfarms",
        "apiVersion": "2018-02-01",
        "name": "[variables('hostingPlanName')]",
        "location": "[parameters('rgLocation')]",
        "sku": {
            "name": "Y1",
            "tier": "Dynamic"
        },
        "properties": {
            "name": "[variables('hostingPlanName')]",
            "computeMode": "Dynamic"
        }
    }

variable hostingPlanName resolves to something like asp-ph-dev-bib
parameter rgLocation resolved initially to southeastasia, not to eastasia
In addition, I want to mention that trying to manually create the service plan directly in Portal did give me same results. I believe the problem is deep in the Azure cloud than in CLI as a scripting interface.

@btardif can you help answering this query? Thank you.

@azlatarov-cocacola is the app service plan you are trying to create a Dynamic app service plan to host Consumption based functions?

Hello, yes it is.
Regards,
Atanas
From: Byron Tardif<EMAIL_ADDRESS>Sent: 28 ноември 2019 г. 1:51
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: ATANAS ZLATAROV<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] webapp:Upon deleting a service plan, it is not possible to recreate it for same resource group + region (#11249)
@azlatarov-cocacolahttps://github.com/azlatarov-cocacola is the app service plan you are trying to create a Dynamic app service plan to host Consumption based functions?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/11249?email_source=notifications&email_token=ANY3OFC536UIB2ZTI6GQBCDQV4BVVA5CNFSM4JNVMTVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFLBC6I#issuecomment-559288697, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANY3OFHFCRLQJ3IIYTSKEY3QV4BVVANCNFSM4JNVMTVA.
Classified - Confidential

CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.

DISCLAIMER AND CONFIDENTIALITY NOTICE
Your privacy is important to us. This privacy notice https://coke.box.com/s/fu1iunu3zceptbqneui32tr540onpg44 applies to the interactions that the Coca-Cola Company entities established in the European Economic Area and N.V. Coca-Cola Services S.A. have with you, for example at events and/business meetings, when we correspond with you, or when you contact our Consumer Interaction Center about Coca-Cola products. This privacy notice explains the personal data that we process, how we processes it, and for what purposes.

I have the same issue, I tried to delete my resource group and recreate it entirely using the same ARM package and it failed with the same message when trying to create the service plan.

@spplante is your case a Dynamic ASP for Consumption based functions as well?

@ahmedelnably FYI since this is related to Functions.

Yup.
Right now I get around this issue the same way I get around storage accounts that used to stay persisted somewhere after deleting a resource group and recreating it, by append a unique string based on the resource group ID to the service plan name using a variable in my ARM template :
"variables": {
    "DynamicServicePlanName": "[ take(concat('MyServicePlan-', uniqueString(resourceGroup().id)), 31) ]",
  },

@ahmedelnably can you help with this?


Amazon Multiple Images

Hi,
First of all this is great work.
I want to know how can I get multiple images in Slider.

Feel free to fork the repo and add in additional fields. I'd love to have scraping definitions updated as well as more fields for each. I'll review any pr's that are opened. I just don't have a ton of time to dedicate to keeping things up-to-date. @wahengchang @ineffablep


Use different storage objects to deal with account root file and blocks

self.storage = PathOptimizedFileSystemStorage()

->
self.account_root_files_storage = PathOptimizedFileSystemStorage()
self.blocks_storage = PathOptimizedFileSystemStorage()

This way we can apply different depth and caching policy

Current implementation:
class FileBlockchain(BlockchainBase):
    def __init__(..., storage_kwargs=None, ...):
      ...
      self.storage = PathOptimizedFileSystemStorage(**(storage_kwargs or {}))
      ...

Instead of passing block_storage_kwargs and account_root_files_storage_kwargs to FileBlockchain I suggest to use dependency injection and pass both storages to FileBlockchain as dependencies:
class FileBlockchain(BlockchainBase):
    def __init__(..., block_storage=None, account_root_files_storage=None, ...):
        self.block_storage = block_storage or PathOptimizedFileSystemStorage()
        self.account_root_files_storage = account_root_files_storage or PathOptimizedFileSystemStorage()

@dmugtasimov Any objections?

@dmugtasimov Please check https://github.com/thenewboston-developers/thenewboston-node/pull/97

@dmugtasimov Another thing to consider: instead of FileBlockchain managing directories where blocks and account root file are stored I'd rather delegate it to storages. So we pass directory to storage on creation and forget about it on blockchain level. Like this:
block_directory = '...'
block_storage = PathOptimizedFileSystemStorage(path=block_directory)

account_root_files_directory = '...'
account_root_files_storage = PathOptimizedFileSystemStorage(path=account_root_files_directory)

blockchain = FileBlockchain(block_storage=block_storage, account_root_files_storage=account_root_files_storage)

This will also enhance security. Right now we pass absolute file paths to storages so you can overwrite something by a mistake. After we pass base directory to the storage it will operate only on files within this directory.

@andbortnik I like the last suggestion. I wanted to do it myself, but considered low priority, so kept as is. I am OK if you implement it.
Regarding dependency injection. I will review it now.

@andbortnik do not see strong reason having dependency inject here, especially because we will need implement an extra layer of abstraction to deal with configuration. We can review this idea later when have more reasons for change.

@andbortnik I like the last suggestion. I wanted to do it myself, but considered low priority, so kept as is. I am OK if you implement it.

@dmugtasimov
Let's implement it in a separate task. I can create it. Do we close this one?

@andbortnik ok for separate task, just do not forget to add it to the project

Created here https://github.com/thenewboston-developers/thenewboston-node/issues/98


[FEATURE] Preserve existing dotfiles

Is your feature request related to a problem? Please describe.
It would be ideal if an installation of bombadil dotfiles could be completely reversible. Currently if there is an existing hard link file eg ~/.someapp.cfg, and you have your own version in your dotfiles repo, eg bombadil-dir/someapp.cfg, "bombadil link" will clobber the existing file.
Describe the solution you'd like
If bombadil finds an existing file in place of where it wants to deploy a symlink, it saves a copy of the file to bombadil-dir/.dots/previous_state_files/. When running "bombadil unlink", this will restore any saved hard link dotfiles to their original location.
Describe alternatives you've considered
Alternative is the existing functionality. Not a huge issue, but the above feature would be a nicety.
Additional context
Add any other context or screenshots about the feature request here.

I think this is beyond the scope of a dotfile manager. You probably want to use git along with tom-bombadil do to this.


Improve commentaarlevel

Treatment of "commentaar" level is not correct. The contents of such levels are analysed as content (and usually discarded because they do not meet the right syntax. To be solved by JO. Concrete example in which this happens ElsdeJong/STAP_01_silver.xlsx

solved locally by JO. Still requires integration


Run unit tests in CI

Ensure all unit-tests are run on CI.
I have created a new action for this purpose. The action installs rust, protoc and runs all unit-tests defined in the lib folder.
I have also introduced a make check-all which can be used to run all tests locally.
TODO

[x]  Fix the broken unit-test

The work to run the python tests is tackled in another MR

Rebased on top of #242

ACK https://github.com/Blockstream/greenlight/pull/239/commits/a7524ba20d59c9e08d9147748a0c7ce629740544


Too pessimistic handling of SQLFeatureNotSupportedException for Postgres binary fields

Environment
HikariCP version: 3.4.1
JDK version     : 1.8.0_222-b10
Database        : PostgreSQL
Driver version  : 42.2.8

Hikari closes connection on SQLFeatureNotSupportedException which leads to problems handling scenarios when exact driver implementation is not known so client code can execute potentially not implemented operations.
Specifically, this happens when using Hikari with Postgres as a connection pool for ActiveJDBC layer. ActiveJDBC tries to implement both Oracle and Postgres ways of storing binary data (https://github.com/javalite/javalite/blob/master/activejdbc/src/main/java/org/javalite/activejdbc/DB.java#L690) and handles SQLException itself. However subsequent use of the setObject() fails as the connection is already closed by Hikari.
This might seem to look like ActiveJDBC issue although I cannot propose any way for them to handle this situation in a driver-agnostic way. Hikari approach seems to be rather unexpected and was introduced in https://github.com/brettwooldridge/HikariCP/issues/1003
I haven't yet filed an issue for ActiveJDBC, it would be really appreciated if this would be fixed either in Hikari, or there could be a good way to implement it in client code like ActiveJDBC. I would like to avoid hackish solutions like putting custom HikariProxyConnection on the classpath.

Created PR (https://github.com/brettwooldridge/HikariCP/pull/1509) to help address this generally.
Regarding SQLFeatureNotSupportedException (sql state 0A000) some engines (Vertica) will partially support some features (like altering column types) and eviction is not ideal. Instead the caller should be able to handle the error and reuse the connection. PR https://github.com/brettwooldridge/HikariCP/pull/1509 addresses this generally by making configurable all exceptions/states/codes that would result in eviction.

For what it's worth, until this is fixed (via #1509 or otherwise) we are working around this issue with the following:
    private final HikariDataSource dataSource; // initialized elsewhere
    private static volatile boolean errorStateHackApplied = false;

    /**
     * Hikari ProxyConnection tries to handle error states returned from the database
     * which does not handle '0A000' appropriately. It was introduced to fix:
     * https://github.com/brettwooldridge/HikariCP/issues/1003
     * This change causes the connection to automatically get closed by Hikari when the database returns
     * a state 0A000, which is not correct in all cases.
     *
     * A subsequent ticket was opened (https://github.com/brettwooldridge/HikariCP/issues/1489) to challenge
     * the handling of '0A000' as a connection failure.
     *
     * For now, we will just remove the inappropriate error state handling via reflection
     * ERROR_STATES.add("0A000"); // FEATURE UNSUPPORTED
     */
    private void applyErrorStateHack() {
        if (!errorStateHackApplied) {
            try (Connection conn = dataSource.getConnection()) {
                if (conn instanceof ProxyConnection) {
                    Field field = ProxyConnection.class.getDeclaredField("ERROR_STATES");
                    field.setAccessible(true);
                    Set<String> errorStates = (Set<String>) field.get(conn);
                    errorStates.remove("0A000");
                    errorStateHackApplied = true;
                }
            } catch (SQLException sqle) {
                LOGGER.warn("Unable to apply error state hack", sqle);
            } catch (Exception e) {
                LOGGER.error("Unable to apply error state hack", e);
                System.exit(1);
            }
        }
    }

@acehead @westse I have implemented this is a slightly different way than pull request #1509.  This change keeps the configuration surface area to a minimum, as well as allowing purely text-based (e.g. property-based) configuration.
You can see an example usage here and here.
This will likely be released in several days along with several other fixes and after the completion of documentation.

@brettwooldridge did you also see the feedback from this issue? https://github.com/brettwooldridge/HikariCP/issues/1388#issuecomment-581473381

I'm fine with this solution. Nevertheless I still think it is wrong in the majority of cases to consider SQLTimeoutException an eviction reason as implemented due to https://github.com/brettwooldridge/HikariCP/issues/1308. I think handling SQLTimeoutException is something for the application to handle.
Maybe you should consider adding a default SQLExceptionOverride that returns DO_NOT_EVICT for SQLTimeoutException.


skeletal impl

This is an initial commit to get a structure in place to allow others to contribute. There are loads of warts, but I want to capture those in issues and go from there.
Fixes #1 #2

Ran into the following error while running
TASK: [jboss_bxms | Extract BPM Suite] ****************************************
failed: [<IP_ADDRESS>] => {"failed": true}
msg: Failed to find handler to unarchive. Make sure the required command to extract the file is installed.

FATAL: all hosts have already failed -- aborting

https://github.com/rhtconsulting/jboss_bxms/pull/4/commits/84001ca175f4cd3e474d1a49259675576354ff7e should fix that. I pushed that likely after you pulled. Please pull again.

lgtm. merging


[Question] Support for LIS3DH and MAX7219/21

@propanu, @w4ilun, I've got my hands on those two subj modules and noticed there seems to be no support for either of them (there's LIS2DS12, which is very close, but still a bit different from LIS3DH and the latter seems to be more widespread being cheaper) in UPM.
Is that correct? If so, are you interested in getting those in, I could give it a shot if no one works on that or plans to.

@alext-mkrs I don't think those 2 modules are in development, would be great if you could add them!

Good, thanks for the information :) I'll follow the standard PR flow then, when it's ready.


Request to upgrade BBC Microbit display driver to support Microbit v2 model

Is your enhancement proposal related to a problem? Please describe.
The current version of the BBC Microbit display driver doesn't work with Microbit v2.
Describe the solution you'd like
In Microbit v2, the LED matrix display has changed internally from a logical 3x9 mapping to a 5x5. An upgrade would be required to support Microbit v2 with backward compatibility to the original Microbit model.
Describe alternatives you've considered
I have tested basic control of the new LED matrix layout but this has been limited to simple LED and PWM tests.
The BBC Microbit developers from Lancaster University offer display control but currently only for Microbit v1. It appears that so far, only Micropython from the BBC Microbit supports the new Microbit v2 display layout.
Also the Arduino core for the BBC Microbit currently only supports v1.
Additional context
Add any other context or graphics (drag-and-drop an image) about the feature request here.

I have some patches for this, but the agreement was to introduce a proper generic led-matrix display drivers with correct Devicetree bindings instead of just updating the old driver. I don't currently have time to do that, maybe @LingaoM does.

Thanks Carles.
Agreed, a new version of the display driver with devicetree bindings would be preferable.

I've reached out to Lingao Meng for his comments and potential plans. Thanks.

@key1066  CC https://github.com/zephyrproject-rtos/zephyr/pull/32532

What’s the current plan for microbit v2 display support?
Is the plan to develop a display driver with devicetree bindings or go ahead with @LingaoM update? Thanks.

Hi,
Any updates on where things are with getting microbit v2 display support in the next Zephyr  release?
Are we going ahead with your existing changes or are you going to develop a display driver with devicetree bindings as suggested by @carlescufi?
Thanks.

On Feb 22, 2021, at 5:00 AM, Lingao Meng @.***> wrote:
@key1066 CC #32532
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@key1066 we need reviewers for #32532, specifically deciding which direction to take there: whether to merge it as-is or to turn it into a generic LED matrix driver.

@key1066 we need reviewers for #32532, specifically deciding which direction to take there: whether to merge it as-is or to turn it into a generic LED matrix driver.

IMHO, there is no such thing as a "typical" LED matrix in terms of pcb wiring.  In the case of the micro:bit, it is directly obtained by from GPIO, but it is much more frequent to find LED drivers that require an SPI like protocol to push the data. Some drivers implement PWM, others do not, etc.
So it does make sense to have something generic in terms of contents and geometry, but the implementation will most likely vary from one pcb to another to be efficient. User supplied drawing and refresh functions could be the answer, but not something like a user defined wiring topology. Having the latter generic would mean an enormous complexity in the specification, whereas writing the update function is most likely not that difficult.
Regards
-- P.

Submitted a related pullrequest, see here:
https://github.com/zephyrproject-rtos/zephyr/pull/36264

OK, now I really think I got it right. With the exception of the right pin for sound output, all the microbit samples seem to work with the V2 and the new display driver and it has become much simpler.
https://github.com/zephyrproject-rtos/zephyr/pull/36280

Very good! I look forward to trying out the new display driver. Thank you.

Yet another attempt to support Micro:bit v2 board #40144

This is now a duplicate of #40208


Set FCM notifications as High priority

This will show the push notification on Android even if the device is in doze mode.

Hey @cpanato can you merge this, build it, publish it (github release v5.8.1), etc ???

sure, will do it tomorrow

@cpanato do not forget about this one ;)


People Picker Context is not Taking this.props.context value in SPFx 1.10 but same piece of code is working in 1.8 version

[Bug]
Hi Team,
I am having issue in getting webpart context in SPFx 1.10 version.
I have checked the same code in SPFx 1.80 solution which is working fine.
below is the error i am getting.
"Type 'IWebPartContext' is not assignable to type 'WebPartContext | ExtensionContext'.
Type 'IWebPartContext' is missing the following properties from type 'WebPartContext': _domElement, _statusRenderer, _teams, _sdks, and 29 more.ts(2322)
IPeoplePicker.d.ts(14, 5): The expected type comes from property 'context' which is declared here on type 'IntrinsicAttributes & IntrinsicClassAttributes & Readonly & Readonly<...>'"
""
below is dependencies from package.json file-
" "dependencies": {
"@microsoft/sp-core-library": "1.10.0",
"@microsoft/sp-lodash-subset": "1.10.0",
"@microsoft/sp-office-ui-fabric-core": "1.10.0",
"@microsoft/sp-property-pane": "1.10.0",
"@microsoft/sp-webpart-base": "1.10.0",
"@pnp/sp": "^2.0.3",
"@pnp/spfx-controls-react": "^1.17.0",
"@types/es6-promise": "0.0.33",
"@types/react": "16.8.8",
"@types/react-dom": "16.8.3",
"@types/webpack-env": "1.13.1",
"office-ui-fabric-react": "6.189.2",
"react": "16.8.5",
"react-dom": "16.8.5",
"react-simple-tooltip": "^2.6.1",
"sp-pnp-js": "^3.0.10"
},"
Expected / Desired Behavior / Question
Context should not throw the error . I have also tried to use "this.context.pageContext" in .tsx file but component is giving context undefined error.
Observed Behavior
I have double checked the props and the property being used(passed) for webpart context from .ts file.
Steps to Reproduce
Kindly create Solution with SPFx 1.10 version.

I am closing this as i have used context as a WebpartContext.below is code-
context={this.props.context as WebPartContext}


Add TypeScript definition files

You can use following code to check their correctness.
npm i -g dtslint
npm run dtslint

In types/index.d.ts,
import * as DRange from "drange";
// Like `const DRange = require("drange");`

declare class RandExp {
    static sugar(): void;
    // Is a static function

    constructor(pattern: string | RegExp, flags?: string);
    // `string | RegExp` means "`string` or `RegExp`"

    max: number
    // Is a `number` member variable

    randInt: (from: number, to: number) => number;
    // Is a member variable of a function which takes two `number` and returns a `number`
}

@fent Are you still watching this PR? I'm going to move this PR to DefinitelyTyped.

Yep, I can look at this again. But which is preferred? For the definition files to exist here or in DefinitelyTyped?

I'd like to add definition file here to smaller my package. Could you review my changes again?

Looks good. Thank you! 👍

Thank for you too, this PR helps me a lot.


[General]: non-required fields became required in v11.0.0

Is there an existing issue for this?

[X] I have searched the existing issues

Package/Plugin version
11.0.0
Platforms

[X] Android
[X] iOS
[ ] Linux
[ ] MacOS
[ ] Web
[ ] Windows

Flutter doctor

Flutter doctor

[✓] Flutter (Channel stable, 3.22.2, on macOS 14.4 23E214 darwin-arm64, locale en-GB)
    • Flutter version 3.22.2 on channel stable at /Users/techouse/fvm/versions/3.22.2
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (6 weeks ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/techouse/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/techouse/Library/Android/sdk
    • Java binary at: /Users/techouse/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Users/techouse/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] IntelliJ IDEA Community Edition (version 2024.1.4)
    • IntelliJ at /Users/techouse/Applications/IntelliJ IDEA Community Edition.app
    • Flutter plugin version 80.0.2
    • Dart plugin version 241.17890.8

[✓] Connected device (5 available)
    • Pixel 6 (mobile)                • xxx                       • android-arm64  • Android 14 (API 34)
    • techouse’s iPhone (mobile)      • xxx                       • ios            • iOS 17.5.1 21F90
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.4 23E214 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.4 23E214 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 126.0.6478.127

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Minimal code example

Code sample

FormBuilderTextField(
  name: 'middle_name',
  initialValue: context.store.middleName,
  autocorrect: false,
  autofillHints: const [AutofillHints.middleName],
  inputFormatters: [
    LengthLimitingTextInputFormatter(64),
  ],
  textCapitalization: TextCapitalization.words,
  decoration: const InputDecoration(
    labelText: 'Middle name(s)',
    hintMaxLines: 1,
  ),
  validator: FormBuilderValidators.compose([
    FormBuilderValidators.maxLength(64),
  ]),
  textInputAction: TextInputAction.next,
  onSubmitted: (_) => debugPrint('onSubmitted'),
);

Current Behavior
With v11 this field became required even though FormBuilderValidators.required() was not one of the validators.
Expected Behavior
Before v11 this field was not required and would allow the user to skip it.
Steps To Reproduce

create non-required field
try to submit form with non-required field
validator throws error

Aditional information
With regards to the breaking changes in v11, I would have thought that non-required fields would have behaved the same.
Does this now mean that checkNullOrEmpty effectively replaces FormBuilderValidators.required()? If so, could the documentation highlight this change?

Yes @techouse, the checkNullOrEmpty by default is true and that is the breaking change on 11.0.0 version.
Can set checkNullOrEmpty : false to avoid this behaviour that do you not want.
What do you think that are the best way to write this on README? We are open to change

Maybe @martijn00 can join to this discussion

What do you think that are the best way to write this on README? We are open to change

I'm not quite sure why this change was even done as we already had FormBuilderValidators.required() which did the same thing, just as an opt-in instead of an opt-out.
If nothing else some sort of migration document should be created highlighting the change.

This change was done because null check behaviour was inconstant between a lot of the validators. It made sense for me to have checkNullOrEmpty set to true to avoid have all kinds of checks again which would be different per validator.
Feel free to submit a PR to clarify the behaviour.

This change was done because null check behaviour was inconstant between a lot of the validators.

So in other words, an internal implementation detail is the culprit of this external API change. 😧
Right, I'll do my best to write up a migration guide.

Sorry for that @techouse. We try to improve the package but maybe this behaviour isn't the best.
What do you think about checkNullOrEmpty set false by default? Do you think that .required validator maybe don't make sense anymore?

We try to improve the package but maybe this behaviour isn't the best.

This will break A LOT of logic. A breaking change like this should not be a footnote in a wall of text. 😅 Not sure it's the best approach.

What do you think about checkNullOrEmpty set false by default?

Possibly, but then that defeats @martijn00's work. 😅

Do you think that .required validator maybe don't make sense anymore?

Well, in v11 it certainly doesn't make any logical sense to have both checkNullOrEmpty and a dedicated FormBuilderValidators.required() validator, however, semantically something like required should exist as it is one of the most basic building blocks of form validation.

It's not just an implementation detail. Half of the validators would just blow up and crash when using null or empty. That's a big bug and solved by this implementation. I could look into making the behaviour the other way around, but that has side effects as well. This was a major version update so it is acceptable to make a breaking change that benefits future users.
Let's have an open discussion about the best way to handle this generically and then see if it needs to be implemented.

Let's have an open discussion about the best way to handle this generically and then see if it needs to be implemented.

Agreed. There is no simple answer here.

It just dawned on me that this could be mitigated with dart fix as described in Data-driven Fixes.
What do you guys think?

It could maybe be migrated with dart fix, but that would probably confuse usage. If you think about the expected behaviour of validators, how would it be? Would all accept a null or empty value as valid? In most cases you don't want that, but depending on your app on some you do. That's why there is a property for it.
There is definitely a need for better documentation on this. I'm just struggling to find a different way to handle this in the code. On itself the Required validators is still a valid one and works fine. Just when combining with other validators it has no use anymore because they would already check it.

I think the intuitive behaviour here would be to let required validator decide if null or empty value is passed to the rest of the validators. Only if the required validator is present - the empty value is passed to the rest of the validators. Otherwise it should be assumed that the field is empty and there is nothing to validate.
And I guess it then would be fine to leave it default to true and present on each validator. It is just that a required validator is now feels useless, but it also the one every developer new to the package is looking for when implementing such functionality, so it cannot be removed.

FormBuilderValidators.maxLength(64) should not throw a error even if its empty or null, it does not make sense

ugh, yeah this was a bit of a weird change for sure. as far as i can tell, most of the places where i had both a min and a max length validator, everything was fine. but in places with just 1 max length validator, my essentially optional fields become required ones.
oh well, i should have read the changelog a bit better + had UI tests? :'D
but i gotta say:
Add optional check (default: true) for null value on every validator
does not sound too optional to me...
maybe it would have been better with default: false?


PPO2 assertion that should probably be a warning

Describe the bug
PPO2 includes the following code snippet:
assert self.n_batch % self.nminibatches == 0, ("The number of minibatches (`nminibatches`) "
                                               "is not a factor of the total number of samples "
                                               "collected per rollout (`n_batch`), "
                                               "some samples won't be used."
                                               )

Having this be an assert statement causes code to be unable to run, even though it likely could run mostly fine. This means it should probably be a warning.  The error messages also seems to imply this. I can do a little PR if the maintainers agree with this.
System Info
Not applicable.

Hello,

Having this be an assert statement causes code to be unable to run, even though it likely could run mostly fine. This means it should probably be a warning. The error messages also seems to imply this. I can do a little PR if the maintainers agree with this.

if it runs, yes this should be converted to a warning, as we did for SB3: https://github.com/DLR-RM/stable-baselines3/pull/270
However, we are currently having trouble with Travis CI (no more open source credits, see https://github.com/hill-a/stable-baselines/pull/1081 and https://github.com/hill-a/stable-baselines/pull/1067) and we are currently having trouble contacting @hill-a  (the owner of the repo which is the only one that can deactivate that requirement).
Anyway, as SB2 is in maintenance mode, I would recommend you to switch to SB3 if possible.

Fixed in SB3


系统time_wait连接数增多

https://github.com/openGemini/opengemini-client-go/blob/49423902a3ca16ac35fa57265f70914d470a964d/opengemini/client_impl.go#L93-L110
http.Client默认MaxIdleConnsPerHost=2，且该参数无法配置。意味着在同时发送大量请求后，超过两个的tcp连接会进入time_wait状态，占用系统资源。未配置合适的连接池导致创建连接的行为，与预期不符。

potential problems here. we need to perform a stress test to analyze the optimal value of MaxIdleConnsPerHost under different concurrency conditions.
we could implement a client connection pool and support MaxIdleConnsPerHost configurability.

@xuthus5 Honestly, I don't see any risk at the moment. Implementing a client connection pool sounds like a huge change to me. I would prefer to wait until users report this problem. Please let me know if I am mistaken.

@shoothzj To be honest, this question is a common trap to use. All that needs to be done is simply to open up a sensible configuration. HTTP connections will automatically be reused in net/http.

@xuthus5 Honestly, I don't see any risk at the moment. Implementing a client connection pool sounds like a huge change to me. I would prefer to wait until users report this problem. Please let me know if I am mistaken.

a simple way to reproduction problem, I created 1000 concurrency for my test program.
package main

import (
	"encoding/json"
	"io"
	"net"
	"net/http"
	"time"

	"github.com/gin-gonic/gin"
)

var client = &http.Client{
	Timeout: time.Second * 3,
	Transport: &http.Transport{
		DialContext: (&net.Dialer{
			Timeout: time.Second * 3,
		}).DialContext,
	},
}

func startHttpServer() {
	r := gin.Default()
	gin.SetMode(gin.ReleaseMode)
	r.GET("/ping", func(c *gin.Context) {
		c.JSON(http.StatusOK, gin.H{
			"message": "pong",
		})
	})
	err := r.Run(":30388")
	if err != nil {
		panic(err)
	}
}

func doRequest() {
	request, err := http.NewRequest("GET", "http://localhost:30388/ping", nil)
	if err != nil {
		panic(err)
	}
	response, err := client.Do(request)
	if err != nil {
		panic(err)
	}
	defer response.Body.Close()
	readAll, err := io.ReadAll(response.Body)
	if err != nil {
		panic(err)
	}
	var m = make(map[string]interface{})
	err = json.Unmarshal(readAll, &m)
	if err != nil {
		panic(err)
	}
}

func concurrentExecution() {
	for i := 0; i < 1000; i++ {
		go doRequest()
	}
}

func main() {
	go startHttpServer()

	time.Sleep(time.Second)

	go concurrentExecution()

	time.Sleep(time.Hour)
}

@wolfbolin @xuthus5 I won't object if it's easily to change. Expose http configuration param looks good to me.

I noticed that we have config transport config, Is that means we already config it to no limit?
Transport: &http.Transport{
 			DialContext: (&net.Dialer{
 				Timeout: config.ConnectTimeout,
 			}).DialContext,
 			TLSClientConfig: config.TlsConfig,
 		},

closed by #111


2021 multi-meter purchase

Oringinally issue isolation for https://github.com/130s/hut_10sqft/issues/537#issuecomment-919488539

Can't think of wholistic requirements as I'm new to these things, so this set of reqs is subject to change, that said:

Can check LED.

May play with a bunch of LEDs with home projects.

(Vague) Not full-fledge nor too light featured.
(Vague) Good usability for beginner but eager-to-learner. Not professional complication.

Other than that I couldn't think nor afford much effort. Went with the top pick of https://www.techgearlab.com/topics/electronics/best-multimeter, AstroAI Digital Multimeter TRMS 6000.


Server chooses cipher suite not matching its certificate

If the server only has either ECDSA or RSA certificates, it needs to choose the corresponding cipher suite, even if the client announces a preference for a cipher suite of the other type.
How to reproduce:

Run the server (master branch): go run examples/listen/selfsign/main.go. It will generate a self-signed ECDSA certificate.
Connect with OpenSSL s_client, without client certificates, with preference for ECDSA (works):
openssl s_client -dtls1_2 -connect <IP_ADDRESS>:4444 -debug -cipher aECDSA:aRSA
Do the same, but with preference for RSA (fails):
openssl s_client -dtls1_2 -connect <IP_ADDRESS>:4444 -debug -cipher aRSA:aECDSA

The fail makes s_client send a fatal alert and exit immediately printing:
140576763131264:error:1416F17F:SSL routines:tls_process_server_certificate:wrong certificate type:ssl/statem/statem_clnt.c:1958:

The go server then exits too because of the fatal alert:
net.Error: handshake error: alert: Alert Fatal: IllegalParameter
panic: handshake error: alert: Alert Fatal: IllegalParameter

This issue was mentioned in https://github.com/pion/dtls/pull/350#issuecomment-798403320.

It seems like certificate selection is just by server name, not by certificate type. So for each server name, the server supports either ECDSA or RSA and it should restrict the cipher suites accordingly.

Had the same issue (CA issued RSA certs & keys) but client was always proposing ECDSA meaning failure to connect. the associated PR fixes the problem.

Fixed by b8f72f3774497508fd9bc960a676dc395c572416
Thank you @lukaslihotzki !


Proper fees dialogs behavior if direct route available, single free PFS or single free route

Fix #596

There's a new method available, Raiden.directRoute, similar to findRoutes, which can get earlier if a direct route is available

This can be used to skip PFS fee & mediation fee dialogs
It resolves to undefined if no direct route is found; rejects only if validation fails (e.g. token address), not on route not found like findRoutes

findPFS will throw only if pfs is disabled in config (config.pfs=null), directRoute before can skip this error if direct transfer is possible; it uses set config.pfs, or fetches from ServiceRegistry only if undefined (default)
Should skip PFS fee dialog if findPFS finds a single free (price=0) PFS
Should skip mediation fee dialog if findRoutes finds a single free route

So, general dApp workflow should be like:

call Raiden.directRoute

if there's a direct route: use it as paths for transfer in last point directly
else (resolves to undefined)

call findPFS

if throws, show error, means no direct route and PFS disabled
if returns a single free PFS, auto-confirm (skip) PFS fee dialog
else, show dialog and let the user select and confirm payment for a PFS

call findRoutes with selected pfs above

if there's a single free route, auto-confirm (skip) mediation fee dialog
else, show dialog and let user select and confirm a route and its fee

call transfer with selected paths

This would fix #408

@andrevmatos I should be done with the dApp part. I did try it by hand also and it seems to work properly. I am not sure if you also want to have a look.
I would like to re-evaluate what happens if for example you have free pfs and there is no route. Do you go back to the previous transfer screen or you go to the select PFS step. But these are mostly UX matters. We can try the scenarios mentioned and then maybe @taleldayekh can help us plan the user flow in these cases better.


chore: update CI workflow to utilize new composite actions and format with terraform-docs v0.16.0

Description

update CI workflow to utilize new composite actions with terraform-docs v0.16.0 (default version for v1.1.0 of pre-commit composite action)

~:warning: A GitHub personal access token will need to be created and either added to just this repo for now, or added as an organization secret (defined in one place and available across all repos in the org). You can see more here https://github.com/clowdhaus/terraform-composite-actions/tree/main/commit#github-token-permissions - this is to enable the automatic formatting of PRs. To be transparent - I don't know how this will fair on PRs that do not check the Allow edits and access to secrets by maintainers checkbox. The workflow is designed to allow for failures without failing the whole CI so it should be ok~
unfortunately I don't see a secure way around the authentication flow on forked copies. either the terraform-aws-modules organization has to extend access to forks to use the token created, or users must create their own token and upload it to their forked projects. The first option won't work because we don't want to expose access to a writable token, and the latter seems less likely to happen by users unfortunately. Therefore, I have removed this functionality from the PR
Motivation and Context

consolidate CI workflow logic

Breaking Changes

No

How Has This Been Tested?

See test PR https://github.com/clowdhaus/terraform-release-test/pull/8

The version of terraform-docs is specified as an input variable here where the current default is v0.16.0 which is the latest.
you can also update the action to specify which version should be used as well, something like:
...
	- name: Pre-commit Terraform ${{ steps.minMax.outputs.maxVersion }}
        uses<EMAIL_ADDRESS>        with:
          terraform-version: ${{ steps.minMax.outputs.maxVersion }}
          terraform-docs-version: v0.12.1 # or whatever version is desired

however, I will say - running terraform-docs through pre-commit has been a horrible headache. pre-commit is designed to work of changes that are staged for the next commit, and so running it in this type of workflow can be problematic as opposed to using the tool directly.
for example:
scenario 1 (ideal): user creates changes, does git commit -m "my changes" and pre-commit will check the staged changes and format/update docs accordingly
scenario 2: user creates changes and bypasses commit hooks using the -n flag like git commit -m "my changes". if you then try to run manually with pre-commit run -a, pre-commit may or may not detect the changes and update (I have not been able to identify a pattern). whereas using the terraform-docs tool directly, it picks up the changes everytime regardless, same with terraform fmt
to be clear, this isn't a limitation of the workflow or actions shown here - they are merely just calling pre-commit as requested and therefore pre-commit is the uknown here that is causing these weird issues

it currently is v0.16.0 because that is what is what is specified at the time of the v1.3.0 release of the action. if a new version comes out, nothing will happen here
If there is a new release of terraform-docs we have two options, either route will require a PR to change the repository to use the different version:
a. The default version is updated here, a new release of the actions is created, and a PR is opened against a module repo to use the newly released version which also contains the newly released version of terraform-docs
b. We specify the version in the module repo using the terraform-docs-version: v#.#.#, when a new version of terraform-docs is released we open a PR to update the v#.#.# version
either route, changes are tied to a release of some sorts; there is no "floating release" that can come into play unknowningly. I'll update to add the version here as well


Implementation of  MongoDBAtlasVectorCollection

Summary by CodeRabbit

New Features

Enhanced vector collection management with advanced search capabilities.

@ceejeeb Thanks a lot for the PR, please check my suggested fixes and accept it if it makes sense

@all-contributors please add @ceejeeb for infrastructure, tests and code

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: ceejeeb:white_check_mark: HavenDV:x: ChrisBrookesWorkYou have signed the CLA already but the status is still pending? Let us recheck it.

Thank you very much for your contribution. Please write me your name in discord if you want and I will add you to the list of contrubutors and dev channel discussing development and immediate plans

Thank you very much for your contribution. Please write me your name in discord if you want and I will add you to the list of contrubutors and dev channel discussing development and immediate plans

You are welcome. I hope I can contribute more.
ceejeeb on discord.

Please join https://discord.gg/Ca2xhfBf3v


Install problem on Python 3.11, via psautohint

Just in case others run into this:
I tried to pip install gftools on macOS 14, with Python 3.11 and it failed trying to build wheels for psautohint.
It turns out psautohint doesn't have wheels for 3.11, and is unmaintained/deprecated, and building it locally somehow didn't work in my setup.
I solved it by using Python 3.10 instead.

Thanks Just! I'll look into getting this repo to work on 3.11 and 3.12.

afdko 4.0.0:

depends on psautohint 🤔
includes otfautohint 🫢

Same on Windows. I also tried to fork AFDKO, remove psautohint from requirements.txt and tried to install. The installation failed while trying to build wheels for AFDKO.
Works if Visual Studio is installed: https://github.com/ftCLI/FoundryTools-CLI/issues/118#issuecomment-1783856177

The standalone psautohint appears to be deprecated, https://github.com/adobe-type-tools/psautohint#important-note-otfautohint. @simoncozens any reason why we can't use the AFDKO's otfautohint? we already have the AFDKO has a dependency,

Installs for me on OS X 13.1, python 3.12. Lemme check 3.11. I'm thinking about adding tox.

It could very well be that my dev env is slightly messed up. However, no wheels for psautohint also means no install for people without dev tools installed.

psautohint dep was removed in afdko 4.0.1


New version: ParallelUtilities v0.2.0

Registering package: ParallelUtilities
Repository: https://github.com/jishnub/ParallelUtilities.jl
Created by: @jishnub
Version: v0.2.0
Commit: 03f07c42e622eb92caac1f1ecbbdc590dc87b100
Reviewed by: @jishnub
Reference: https://github.com/jishnub/ParallelUtilities.jl/commit/03f07c42e622eb92caac1f1ecbbdc590dc87b100#commitcomment-37185863

@jishnub Please retrigger Registrator in order to fix the merge conflict.
[noblock]


Added StopWatch App

@Sulagna-Dutta-Roy I appreciate your work. But before creating a PR, you have to create an issue. Then I will assign it to you. Then, your PR will be merged.


Runtime article covering Architecture, runtime selection (DNX_HOME), Features model

Closing as we are moving from DNX to the new .NET CLI.


Character n-grams

Allowing tokenize documents with character n-grams would be useful.

Partially addressed in #45

I could look into implementing a ngram and skipgram iterator? Similar to the util functions in NLTK http://www.nltk.org/_modules/nltk/util.html#ngrams

Thanks @joshlk that would be very useful! Maybe without the rightpad/leftpad options for a start? It would also be interesting to have something that would work with ngram_range parameter as in scikit-learn CountVectorizer,

The lower and upper boundary of the range of n-values for different word n-grams or char n-grams to be extracted. All values of n such such that min_n <= n <= max_n will be used. For example an ngram_range of (1, 1) means only unigrams, (1, 2) means unigrams and bigrams, and (2, 2) means only bigrams.

Though the extension of this parameter to skip grams is not clear.
There is also a question of how to chain tokenization + n-grams iterators https://github.com/rth/vtext/issues/21

PR: #82
Please take a look when you get a chance


plugin-clboss: Killing plugin: JSON-RPC response "id"-field is not a u64

My clboss got killed after running for a few days. The message in the log was:
 plugin-clboss: Killing plugin: JSON-RPC response "id"-field is not a u64
Unfortunately I didn't have DEBUG logs enabled for clboss.
The log message prior to the error was:
lightningd: Sending 279628174msat over 7 hops to deliver 278212722msat

Also now getting this in the console (not in the log), not sure if this is related but I haven't seen it before:
 Unhandled exception in concurrent task!
Sqlite3::Tx:
			DELETE FROM "OnchainFeeMonitor_samples"
			 ORDER BY id
			 LIMIT :limit
			     ;
			: near "ORDER": syntax error
...main loop continuing...

The second issue looks like a problem with the SQLITE on your system; there is a build option for SQLITE to enable this syntax: https://sqlite.org/compile.html#enable_update_delete_limit .  Looks like it would be a good idea to move SQLITE3 inside external/ in order to ensure we have control of the SQLITE3 flags; on Linux systems I have seen, the flag is enabled and ORDER BY is understood by the system SQLITE3.
Can you try this on your system?
$ sqlite3 :memory:
sqlite> CREATE TABLE "Foo"(id INTEGER PRIMARY KEY);
sqlite> DELETE FROM "Foo" ORDER BY id LIMIT 1;

(exit sqlite3 by ^D or .quit)
If you get the same error then it seems the system SQLITE3 does not enable the flag.  If so, a workaround you can try would be to compile SQLITE3 from source, and make sure the flag is enabled (there are probably a bunch of flags that need to be enabled, like foreign key flags), creating a library.  Then ./configure in CLBOSS, indicating the appropriate SQLITE3_CFLAGS and SQLITE3_LIBS:
env SQLITE3_CFLAGS=-I/path/to/sqlite3 SQLITE3_LIBS=-l/path/to/sqlite3/libsqlite3.a ./configure && make

(The above is untested, merely theoretical, sorry; it "should" work and I use a fairly commonly-used SQLITE3 setup macro for autoconf, so it "should" work, but I have not tried this myself)
You can see more information on ./configure --help.

  Sigh.  Lemme try something that should help fix this.  This would be tested by running a script that continuously does lightning-cli getinfo to stress-test the id.
Unfortunately I will be offline for a few days for some internal garbage-collection processes, but lemme try to push a quick fix for the id issue on master (though you do have problems with autoreconf -i too right.....).

Hi @hosiawak , pushed a quick fix, hope it works.  Try this package, ignore the version number for now: clboss-0.9A.tar.gz  It includes fixes for both the id and the DELETE..ORDER BY issues.  I have it running for like 5 minutes now (LOL).

Running for an hour now, seems okay.

Still up, so at least the bugfix did not introduce yet another bug.... probably only question is if it actually fixes the bug.

Going offline.  Bye!

I left my C-Lightning node running, but it got hit by https://github.com/ElementsProject/lightning/issues/4240 since I was using logrotate.  Hmmm.  Lemme run a stress-test.

I left it running (without using your modified version) and it got killed 2 days ago for the same reason:
2020-11-30T18:32:41.193Z INFO    plugin-clboss: FundsMover: Failed at source, cannot advance further.
2020-11-30T18:32:42.302Z INFO    plugin-clboss: Killing plugin: JSON-RPC response "id"-field is not a u64

I'm going to compile the version you posted above and let that run for a while. Thanks.

2 days later clboss is still running so I guess this issue is now fixed :)

Okay, let us close?


Add no index option to field type

Change Summary
This PR replaces #61.

I added the missing index field to the Field struct.
The typesense documentation (https://typesense.org/docs/0.20.0/api/collections.html#with-pre-defined-schema) describes a  index option that can be set on fields:

Declaring a field as non-indexable
You can ensure that a field is not indexed by setting "index": false. This is useful when used along with auto schema

I did not get the whole openapi-codegen thing working. It always created a lot of changes (even when I did not do any changes to the openapi.yml file). Maybe you can help me out on that 😃
PR Checklist

[x] I have read and signed the Contributor License Agreement.

I'm sorry, in the settings of cloud.drone.io the "Disable forks" option was checked, I disabled it and pipeline started.

@v-byte-cpu Thanks a lot. I will have a look at it and fix the errors that are shown.


Can we allow pipelineRef.resolver and pipelineRef.name to exist at the same time?

Feature request
Currently, our number of pipelines is getting bigger and bigger, however, we also observe
that there are many pipelines that are not active and will not even be used in the future.
We want to archive this part of the pipeline. When we try to archive part of the pipeline,
some users use it again, so we need to recover it again.
We noticed that there is a new featureTEP-060 that seems to be sufficient, but it does not fully
meet the needs.
Can we allow pipelineRef.resolver and pipelineRef.name to exist at the same time, and pipelineRef.name
has a higher priority, when pipelineRef.name cannot be obtained, then pipelineRef.resolver is used
to resolve the pipeline. We can even use a parameter to control whether when pipelineRef.resolver
and pipelineRef.name exist at the same time, if pipelineRef.name cannot be obtained, it can be resolved
through pipelineRef.resolver and the pipeline is created in the cluster.
Use case
The detailed description is as above.
The specific configuration example is as follows:
...
  pipelineRef:
    resolver: git-example
    params:
    - name: url
      value: https://git.example.com/cicd/remote-pipeline.git
    - name: revision
      value: production
    - name: pathInRepo
      value: pipeline.yml
    name: cicd
...

/remove-lifecycle stale

/cc @jerop @vdemeester @pritidesai

We can even use a parameter to control whether when pipelineRef.resolver and pipelineRef.name exist at the same time, if pipelineRef.name cannot be obtained, it can be resolved through pipelineRef.resolver and the pipeline is created in the cluster.

@cugykw wdyt of doing this in a new resolver instead of the API -- say a combination of the cluster and git resolvers

We can even use a parameter to control whether when pipelineRef.resolver and pipelineRef.name exist at the same time, if pipelineRef.name cannot be obtained, it can be resolved through pipelineRef.resolver and the pipeline is created in the cluster.

@cugykw wdyt of doing this in a new resolver instead of the API -- say a combination of the cluster and git resolvers
Thanks for your suggestion, it seems possible to use a custom resolver.


Added docs and new workflow

Added documentation and new workflow for automatic release

PR won't be accepted until all workflows work correctly


Update dependencies

Webpack build requires NPM package of ccv-js: https://github.com/forresto/ccv-js/issues/1

@automata @forresto ping on this one

@automata should be good to go now


⚠ Panoramas has degraded performance

In 24cfcd2, Panoramas ($SITE_URL_PANORAMAS) experienced degraded performance:

HTTP code: 200
Response time: 7168 ms

Resolved: Panoramas performance has improved in 84c9a10 after 9 minutes.


implement ExternalIsSubclass for Rust

This change implements ExternalIsSubclass for Rust following similar behavior as for Golang.  This essentially says that a type is only a subclass of itself.  The patch is from @gj in Slack (thanks Gabe!).
This fixes a panic I ran into:
thread 'main' panicked at 'not implemented: Unhandled event ExternalIsSubclass { call_id: 2527, left_class_tag: Symbol("Instance"), right_class_tag: Symbol("Fleet") }', /home/dap/.cargo/registry/src/github.com-1ecc6299db9ec823/oso-0.22.0/src/query.rs:89:26

I'm not sure what else might be needed for this PR -- please let me know!

I'm happy to sign the CLA (I'm waiting for the bot to say what I need to do), but this contribution is probably better attributed to @gk since this is the patch he sent me in Slack as-is.

I have read the CLA Document and I hereby sign the CLA

Thanks!  I will look at adding a test for it and reach out on Slack if I run into trouble.

I took a first swing at writing a new test called test_subclass.rs.  I tried to stick to your suggestion @samscott89 but I found that the test succeeded even without my fix so I don't think it exercises the code path.  This might be a result of changes I made to your suggested policy.  The main one was that I changed Project.parent to just Project.public, since struct Project cannot contain another Project directly.  (I also tried Option<Box<Project>>, but ToPolar isn't implemented for Box<T>.)
I can instead try to start with the case where I originally hit this and simplify it as much as possible but I figured I'd check first to see if I'm way off the mark.  Even if we find an example that works, will we have sufficient confidence that it will continue to exercise the right code path?

I've pushed commit 3664b31e, which changes the test to more closely match the most recent case where I hit this.  It triggers the unimplemented panic prior to my fix.  But I can't say I understand why it hits that code path or whether it's a good test case for that code path.  Note that this policy uses == instead of =, which is wrong even with the panic fixed.  But using = prevents this code path from being hit altogether.
Sorry for the mess of test cases.  I don't feel I understand Oso well enough to generate a simple test case here, but I'm hoping you can point me in a better direction.

I took a first swing at writing a new test called test_subclass.rs. I tried to stick to your suggestion @samscott89 but I found that the test succeeded even without my fix so I don't think it exercises the code path. This might be a result of changes I made to your suggested policy. The main one was that I changed Project.parent to just Project.public, since struct Project cannot contain another Project directly. (I also tried Option<Box<Project>>, but ToPolar isn't implemented for Box<T>.)
I can instead try to start with the case where I originally hit this and simplify it as much as possible but I figured I'd check first to see if I'm way off the mark. Even if we find an example that works, will we have sufficient confidence that it will continue to exercise the right code path?

Ah, that makes sense! Yeah, it's a bit of a non trivial example in an attempt to trigger this with a real, working policy.

I've pushed commit 3664b31, which changes the test to more closely match the most recent case where I hit this. It triggers the unimplemented panic prior to my fix. But I can't say I understand why it hits that code path or whether it's a good test case for that code path. Note that this policy uses == instead of =, which is wrong even with the panic fixed. But using = prevents this code path from being hit altogether.
Sorry for the mess of test cases. I don't feel I understand Oso well enough to generate a simple test case here, but I'm hoping you can point me in a better direction.

Thanks for trying a few things! Yeah, I see the problem with the first one. It seems like this is actually kind of a hard test case to hit in regular (non data filtering) usage.
I think we can probably just push up a less realistic use case. I'll try one now.


Sitemap generation for published site

Please Select if your Request is Either something new or an Enhancement

[ ] Enhancement of an existing Feature.
[x] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[x] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
My publicly published notes can take a while to show up in search engines, as they have to crawl the entire site in order to find the newly published and changed content.
Describe the solution you'd like
A sitemap would give search engines a reference point for new and changed content, likely reducing indexing time.
Describe alternatives you've considered
I could generate a sitemap externally (e.g. via Netlify plugins), but I'm not sure I could accurately convey the modification times. Given that Dendron keeps track of these in the frontmatter I think it makes sense for Dendron to generate the sitemap.
Additional context

Thanks for the issue. You're right, sitemap is something that Dendron can and should generate. We're currently working on Dendron's nextjs publishing which we aim to release by end of the month. For now, I would recommend generating this using a script.
If you run the Nextjs Pod, it will create a file called notes.json. This contains the ids of every note that will be published. Your sitemap should be {siteUrl}/notes/{id}.html.
I'm also adding this issue to our community roadmap which means it will show up as an upcoming CROP.

heads up that this was shipped in v71. see https://wiki.dendron.so/notes/yQVhJtdQ40n3SLHJKAeeU.html#options


Refactor UG to be user centric and include headers overview

Fixes #230
Fixes #238
Fixes #233

Codecov Report

Merging #239 (1d9a0c7) into master (c8e0fc0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #239   +/-   ##
=========================================
  Coverage     69.74%   69.74%
  Complexity      638      638
=========================================
  Files            94       94
  Lines          1980     1980
  Branches        269      269
=========================================
  Hits           1381     1381
  Misses          496      496
  Partials        103      103

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


How to set time and date manually with yi hack?

I am going to use the camera with yi hack in the house that I have in the field, there is no internet in that house and I would like to know if you can configure the date and time manually

No, it's not possible. The cam has no backup battery and when you switch it off the time is lost.
But you can use a local ntp server.


Skip layout transitions in QF release ops

Not entirely sure about this. I'm going to get some more tests going before trying to land this

@chrisforbes, how are you now feeling about this change?

Obsolete


Support for postcss-for and postcss-each?

The postcss-cssnext support is great in this package, but I'm wondering it would be possible to add support the @for and @each syntax provided by postcss-for and postcss-each respectively?
Obviously this isn't 'true' CSS and falls outside of the CSS spec, but these two standalone packages have a pretty large user base with 13k and 28k installs via NPM in the past month, so I feel it would be a worthwhile addition if possible.
Below is a screenshot of how the highlighting currently appears for these two rules.

Sorry. I feel like if I support for and each, then I'll have to support everything on PostCSS. I was okay with supporting cssnext because...

Most of the work was already done. All I had to add was nested CSS.
Everything in cssnext is backed by a W3C spec.

As you mentioned, for and each fall outside the specs. Also, nested CSS blocks are really tricky to get right. The more nested blocks I support, the harder it will be to debug when highlighting or completions aren't working right.
So I'm sorry I can't add this, but thanks for raising the issue! It was worthwhile to research. I'm not a front-end guy, so the way I find out about new and interesting CSS is from users like yourself 🙂


Coordinator stopped forwarding new orders to apps

The limit orders were being created and the maker was receiving confirmation on the orderbook WS, but at least 2 production apps were not getting new orders.
Restarting the coordinator fixed the issue.
During this time, the app was emitting a lot of https://github.com/get10101/10101/issues/2447. This seems to suggest that the app was able to learn about order deletions through the orderbook WS.

I'm closing this as we think this was related to an issue with our production setup. Reopen if it happens again.


Support sqlite (again)

Similar to previous PR, but starting from a newer main branch commit

@stuartmcalpine sorry to ask you to look at basically the same thing twice.
This is the branch (made after your large-scale changes) I meant to make a PR from.  It shouldn't have any merge conflicts.


Gist is not always run automatically

For example, this URL:
https://dev.lfortran.org/?gist=certik/7e2652943bbff7f0d0963dd4fcf1813a
Sometimes automatically runs the new gist, but sometimes it doesn't.
It should always run it.

This might be the same error as #101.


Payload is wrong after 16 bytes

Somehow bytes after byte 16 appear to be corrupt.
The following FRM payload (hex):<PHONE_NUMBER>8d2a0020000001e40001a30200000000
with the session keys:
	Newskey: AES128([26, C0, 7D, F9, 16, 69, F7, B2, FD, 67, E5, 6B, 53, E9, 6D, BF])
	Appskey: AES128([3C, 23, 2D, 71, 18, 1C, FE, 34, 6C, E7, 54, 39, 37, 23, F5, 30])

Becomes the following base64 PhyPayload: gCYCAEgAGAACYMbhumG/XnwtUwxnGPPe4CuawEsYOjRtKg==
When I use this online decoder resource to parse it, I get the following response:
  FRMPayload = 60C6E1BA61BF5E7C2D530C6718F3DEE02B9AC04B18 (from packet, encrypted)
                        =<PHONE_NUMBER>8D2A0020000001E40001A33A032FF09B (decrypted)

As you can see, after byte 16, it's wrong. The payload does seem to roundtrip properly within the rust-lorawan though.
I'll try to find a minute to write a unit test about this today, but I thought I'd log it for now and maybe you know where to look for the fix @ivajloip

This should be fine now (both for lorawan and lorawan-encoding crates) with v0.6.1.


Removed Ring struct to reduce memory use and copying of data

Most members were used rarely anyway.

I had the exact same optimization get rejected. Daniel wants to keep the Ring struct.
https://github.com/Loopring/protocol/pull/64

@BenjaminPrice Did you misread Ring for Rate? The pull request you referenced removed the Rate struct as far as I can see, I removed the Ring struct.

Ah, you're right. Totally misread that.

I'm merging this to another branch to test it.


'TextFieldConfiguration' isn't a function

i got an error like this when i try code in example
error: The name 'TextFieldConfiguration' is defined in the libraries 'package:flutter_typeahead/flutter_typeahead.dart' and 'package:flutter_typeahead_web/flutter_typeahead.dart (via package:flutter_tagging/flutter_tagging.dart)'. (ambiguous_import at ...)

@brizaldi seems like you're using flutter_typeahead package too. The package already includes typeahead package.


Add entry type concept

Allow registering entry types in the Pageflow configuration. Add a
type_name attribute to Entry which can be used to look up the
corresponding EntryType object.
REDMINE-17208, REDMINE-17213

Coverage remained the same at ?% when pulling fcace11d9e1009f19c4756d3fbe1977088286e4e on tf:entry-type-config into dcd9e4853c49b0b510fca0b43cff76423ff7d343 on codevise:master.


Small change to code to humanize things.

Addresses part of #159. Specifically, implements the advice in
http://peter.bourgon.org/go-in-production/#testing-and-validation so that go test ./... just executes unit tests

Current coverage is 54.00% (diff: 100%)

Merging #160 into master will not change coverage

@@             master       #160   diff @@
==========================================
  Files           102        102
  Lines          5157       5157
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2785       2785
  Misses         2132       2132
  Partials        240        240

Powered by Codecov. Last update f207a8f...7f04070

I hadn't noticed this pattern before but I really like it, nice find.


authorization for OSSMC tests + initial smokes

I was tinkering with authorization, but was unable to get it working using API - we can look into that later.
This PR introduces authorization for tests using new cy.session method, which can persist across multiple spec files. For initial testing this should be enough.
Few tests to verify the routes are bundled as @smoke for OSSMC. There will be more smokes to verify that the actual UI of Kiali is loaded and displayed  correctly. Also there are few TODO comments we can adders later.

I  was able to run the regression using yarn cypress:open, OCP login works for me


prevent posting if ip address is banned

Basic functionality to prevent posting if user's IP address is in the 'bans' table. Returns 403 Forbidden in case matching IP is found  and ban expiry date has not yet been passed.
Very limited testing done from the performance perspective. I ran this locally in dev mode with approx. 0.9 million rows in the bans table, with no noticeable effects. Raw SQL query seems to take less than 20 milliseconds.

It looks fine to me. Sorry for the delay, I've been away so it took a while to respond and merge this.


Can we integrate resume functionality with this library.

You have pause and play method,
If you want to start from a specific location you can use startSeconds in loadVideoById
Also you can use fetchCurrentTime.


[FLINK-30729][state/changelog] Refactor checkState() to WARN of StateChangelogWriter to avoid confusing IllegalException

What is the purpose of the change
Refactor checkState() to WARN of StateChangelogWriter to avoid confusing IllegalException.
Brief change log

Replace checkState() with LOG.warn() when StateChangelogWriter is closed.

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@masteryhx Thanks for the review, also refactor the checkState() in method append(), please take a look again.

LGTM.


Allow translators: comments.

A bugfix upstream now causes Doc comment short description must start with a capital letter errors for /* translators: ... */ comments.
Excluding the offending rule to continue to allow these type of comments.
Ref: https://github.com/squizlabs/PHP_CodeSniffer/pull/855

@jrfnl I'm surprised that PHPCS is reporting an error for this since such translators comments aren't in phpdoc block comments (/** ... */) but just vanilla multiline comments (/* ... */). Shouldn't PHPCS be skipping phpdoc validation for the latter?

That seems to me a discussion to take upstream.
However, in the mean time, WPCS checked builds should pass when they contain translators comments...
If and when upstream would decide to change this, we can always reverse the exclusion.

@jrfnl I cannot reproduce the issue, however.
If I do:
phpcs --standard=WordPress-Docs --sniffs=Generic.Commenting.DocComment

It only complains about the second instance, not the first:
/* translators: 1: the id argument, 2: sidebar name, 3: recommended id value */
_doing_it_wrong( __FUNCTION__, sprintf( __( 'No %1$s was set in the arguments array for the "%2$s" sidebar. Defaulting to "%3$s". Manually set the %1$s to "%3$s" to silence this notice and keep existing sidebar content.' ), 'id', $sidebar['name'], $sidebar['id'] ), '4.2.0' );

/** translators: 1: the id argument, 2: sidebar name, 3: recommended id value */
_doing_it_wrong( __FUNCTION__, sprintf( __( 'No %1$s was set in the arguments array for the "%2$s" sidebar. Defaulting to "%3$s". Manually set the %1$s to "%3$s" to silence this notice and keep existing sidebar content.' ), 'id', $sidebar['name'], $sidebar['id'] ), '4.2.0' );

@westonruter You can see the issue with /* */ syntax here:
https://travis-ci.org/tollmanz/debug-bar-cron/jobs/127228904 which refers to this line of code:
/* translators: %s is number of seconds. */

But yes, there is something funky going on with the sniff as it seems to only pick up the second instance.
In the file the above code comes from, it's not complaining about the same syntax on line 385

I can't reproduce the issue on that line either. Try this:
$ curl -sG https://raw.githubusercontent.com/tollmanz/debug-bar-cron/2f4173b043c1b04b64ad199d768c4294b9f75288/class-debug-bar-cron.php | phpcs --standard=WordPress-Docs -v --sniffs=Generic.Commenting.DocComment
Registering sniffs in the WordPress Docs standard... DONE (1 sniffs registered)
Creating file list... DONE (0 files in queue)
Processing STDIN [PHP => 4436 tokens in 638 lines]... DONE in 82ms (0 errors, 0 warnings)
Time: 961ms; Memory: 9Mb

Actually, the error being reported is a different issue than Generic.Commenting.DocComment. It seems to actually be the Squiz.Commenting.InlineComment sniff:
$ curl -sG https://raw.githubusercontent.com/tollmanz/debug-bar-cron/2f4173b043c1b04b64ad199d768c4294b9f75288/class-debug-bar-cron.php | phpcs --standard=WordPress-Docs -s

FILE: STDIN
----------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------
 454 | ERROR | Inline comments must start with a capital letter
     |       | (Squiz.Commenting.InlineComment.NotCapital)
----------------------------------------------------------------------

Even weirder as I'm pretty sure I copied & pasted it from my locally run log which would indicate two different sniffs being potentially buggy for the translators comments.... or did I ? Where's my head ? Anyone seen it ? If you find it, give me a shout will ya ?
In the mean time: adjusted the PR to address the right sniff.


how negative numbers affect gradient descent.

The loss may be negative number in the model. The reason is that the reinforce loss is often to be a negative number since the reward is the larger the better. But I am very confusing about how negative numbers affect gradient descent.
I also notice that the hybrid loss tend to be zero eventually. How can loss increase with  gradient descent?

This is a standard approach to use negative loss values in reinforcement learning to turn gradient descent into gradient ascent. Minimizing negative loss is maximizing the same loss without minus sign. To my knowledge there is no issues in pytorch with this.
In A3C algorithm (used in this project) the loss can increase during training. The reason is that reinforcement loss is measured as the advantage over baseline prediction. Baseline is network that is learned during training and in the start of the training, it's prediction are poor and it's very easy to have an advantage over it.

@malashinroman Hi, May I ask why is this an A3C algorithm?
To me, all the images in a batch share the same agent. And the update is not asynchronous. While in A3C, the agents are different in different processes, and they update asynchronously to the central network.  Please let me know if I'm wrong. I'm new to RL. Thanks!

I think you're right. I thought about different environments, but there are no asynchronous agents
Roman среда, 17 марта 2021г., 22:50 +03:00 от litingfeng  @.*** :
@.*** Hi, May I ask why is this an A3C algorithm?

To me, all the images in a batch share the same agent. And the update is not asynchronous. While in A3C, the agents are different in different processes, and they update asynchronously to the central network.  Please let me know if I'm wrong. I'm new to RL. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly,  view it on GitHub , or  unsubscribe .


Scolling in modal dialog on IOS doesn't work

Can't scroll on any modal dialogs that require scolling such as the Projects dialog:

This has been fixed.


[seal] Fixed cannot find SEAL.

Describe the pull request

What does your PR fix?
Fixes an issue that seal cannot be found. The fix is changing seal's cmake configuration files' path.

Which triplets are supported/not supported? Have you updated the CI baseline?
x64-windows/x86-windows are not supported as the library only supports static linkage in Windows.
No change to the CI baseline.

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Could you please also update port-version in manifest ?

What do you mean? I tried to add "port-version": 0 to manifest file. Then vcpkg complains about it: Error: The port seal is not properly formatted.
Running vcpkg format-manifest ports/seal/vcpkg.json remove the line I added.
Should I increment port-version to 1?

Could you please also update port-version in manifest ?

What do you mean? I tried to add "port-version": 0 to manifest file. Then vcpkg complains about it: Error: The port seal is not properly formatted.
Running vcpkg format-manifest ports/seal/vcpkg.json remove the line I added.
Should I increment port-version to 1?

Yes, you should add "port-version": 1, to manifest files.

Got it. Done.

Thanks for your fixing @WeiDaiWD.


Update create_semantic_types.cql

Added a first statement to compensate for having more HCUIs in new construction. What it does is uses the HCUI-Code-CUI relationships to create semantic types for the ones that would have had dbXrefs before doing the hierarchical traversal. Note that this MERGE approach does not limit to one Semantic per HCUI (that was not really needed and could at some point change the rest of this to be more general also).

This has changes to code that no longer exists. Closing it for cleanup purposes.


If a meeting is un-finalized, it is not possible to delete it - though it has a "blue" trash-icon

Either remove blue style from trash icon, or make it possible to delete these unfunalized minutes.

The 2nd idea sounds complicated... as we have to keep "Open Topics" and "Closed Topics" of the meeting series in sync.

After thinking about it: though more complex: I would vote for the second option.
From a user-perspective: After un-finalizing I would expect to be able to delete the complete minutes.

Well, then I would suggest to add a new field "isNew" to our topic. With this field it is easy to check if the topic is exclusive for the "to-be-deleted-minute" and will be removed from the open or closed topics of the related meeting series.
Additionally we have to take care about closed topics which were closed within the "to-be-deleted-minute". They can also be identified by the "isNew"-Flag. So all closed-topics of the "to-be-deleted-minute" which are not new will be opened again and added to the open topics of the related meeting series.

I tested on port :4000 version. new solution works like a charm!
Thx.!  ;-) I will close this issue.


Add context menu item to make switching between an elastic and normal deformable component

Closing all my "todo" issues that have been around forever. They don't need to be issues