ODE solver in LTC cells

Another question. I'm currently trying to adapt LTC4 to Keras3 in order to compare it to legacy LNN code (which is here: https://github.com/mlech26l/ncps/tree/master/ncps/keras).
There is one thing I don't understand in LTC4 code, which is when the ODE solver is used? In the legacy code there is an explicit method defined to do so (https://github.com/mlech26l/ncps/blob/master/ncps/keras/ltc_cell.py#L255), whereas in your code it looks like the solver option is never used by anything. Moreover it's not defined in AbstractRNNCell class, or even in MinimalRNNCell, and changing the ODE_solver value to something different than 0/1/2 doesn't affect the code, I'm able to use the LTCCell while putting solver value to 5 for example, which tends to show that neural state calculation is not using it.
Am I missing something here???

Thank you for your input.  You were correct in observing that the initial implementation of the LTCCell uploaded here had an unused solver parameter. In the original code, while the solver option was included in the cell's initialization, it wasn't actually used to influence the neural state updates, effectively making it redundant.
Revisions Made:
We have now added the released code which included three different ODE solvers—SemiImplicit, Explicit, and RungeKutta—based on the Liquid Time-Constant Neural Network (LTCN) framework. Each of these solvers provides a unique method for updating the cell's state:
Semi-Implicit Euler Method: This solver performs a semi-implicit update of the neural state, providing a balance between stability and computational efficiency.
Explicit Euler Method: An explicit method that directly uses the activation to update the state, which is simpler but can be less stable for stiff equations.
Fourth-Order Runge-Kutta Method: A more advanced and accurate method that approximates the solution by considering multiple slopes (k1, k2, k3, k4) for a single step.
Integration into call Method: We integrated these solvers into the call method of the LTCCell. Now, the chosen solver option (ODESolver.SemiImplicit, ODESolver.Explicit, or ODESolver.RungeKutta) determines how the cell's state is updated during each time step.

Thanks for the reply, it makes things much clearer now

BTW, I think there is a typo in the definition of the Explicit and SemiImplicit solver:
https://github.com/michaelkhany/liquid_time_constant_networks/blob/main/LTC4.py#L71
For the step size I suppose one should use 1.0/self._ode_solver_unfolds (as in RK solver)  and not self._ode_solver_unfolds.


fix: skip upstream tasks when running tekton tasks

This caused issues in this PR:
https://github.com/redhat-appstudio/release-service-bundles/pull/192

I added a second commit to test that it works as expected. And it did: https://github.com/redhat-appstudio/release-service-bundles/actions/runs/6172019788/job/16751422790?pr=199
Now I removed the testing commit again.


Ensure future compatibility, drop old code (v1/v2 support)

This PR does two things.
Make sure that once (if ever) Linux kernel will start supporting capabilities v4, this library won't stop working. This relies on the assumption that v3 will still be supported.
Drops v1 and v2 API.
v3 API is used since the Linux kernel 2.6.26.
Since go 1.18 (no longer supported as of go 1.20 release), the minimum Linux kernel requirement is 2.6.32 (see 1). So, it does not make sense to support capabilities v1 and v2 any more.
Drop the support.

Same as https://github.com/syndtr/gocapability/pull/23

Previously LGTMed by @avagin here.


Should document how to create a custom Params

Our Params structure is #[non_exhaustive], which I believe is the correct way to go (because we will almost certainly want to add flags or something to it, e.g. to handle the new difficulty rule for testnet4, whatever that turns out to be). However this makes it super non-obvious how users are supposed to construct this thing, if they want to support their custom networks.
The "right" way to do this, I think, is for them to call Params::new(Network::Regtest) (maybe with testnet rather than regtest) and then manually edit the specific fields they want to change. This matches the typical "start with regtest then tweak the network magic or whatever" mode of creating test networks.
But the docs don't say anything about this and they should.
https://docs.rs/bitcoin/latest/bitcoin/consensus/params/struct.Params.html

Since we made so much effort with Params and Network this release this should go in the release IMO. I'll prioritize it.

Also we may want to add const constructors for any/all of the types that are used in Params so folk can create const getters (eg., pub const fn magic above).

Yep, this looks like what I had in mind.

Also we may want to add const constructors for any/all of the types that are used in Params so folk can create const getters (eg., pub const fn magic above).

Yeah, ideally everything related to params should be const.


feat: Create project if not found

https://github.com/denoland/deployctl/assets/4871949/7c5f93ea-88fb-4524-a1ee-29b557cbfe43

Generally I'm in favor of the idea of creating a new project if the specified one doesn't exist, but I guess there might be a case where the project name is just a typo, in which case it would be undesirable to create a new project automatically. So what about prompting a user like Project xxx not found. Do you want to create one? [y/N] to check if the user really wants it?

I prefer the optimistic approach, as the name of the project is fairly incosequential and easy to change. I'll add a line outputing the link to the project settings to help users in this regard.


In Demo version invited member cannot accept a invitation request.

Describe the bug
In a demo version of better auth, if we invite a member and invitation link is send to mail but we we click  Join Team button it get redirects to vercel and vercel says you aren't a team member. I don't know its a bug or it is as it like

To Reproduce
Steps to reproduce the behavior:

Go to Demo Url
Create an account and Create new organization
Click to invite member, fill up the details
When you receive a mail click onjoin team
See error

Expected behavior
It should redirect to dashboard
Screenshots

Desktop (please complete the following information):

OS: MacOS Latest
Browser : Brave
Version : latest

Additional context
If it's as expected behaviour please mention me.

this is no longer a case


TypeError: sequence item 2: expected str instance, list found

Describe the bug
TypeError  sequence item 2: expected str instance, list found generated instead of DDLParserError
To Reproduce
Steps to reproduce the behavior:

Take file https://github.com/shurashs/CDW_DWH/blob/024dee59c808f8d57ef9694b7344917b54009b10/Projects/Metrics/Common/PT005/META/META_CRITERIA_COMBO.sql?raw=True
Use code ddl = parse_from_file(filepath)
See error TypeError  sequence item 2: expected str instance, list found

Expected behavior
DDLParserError with a clear error explanation
More examples

https://github.com/DevStreet/FinanceAnalytics/blob/9dd4afee3dd8b0cee99dde57cb8879bc08f34f92/projects/OG-MasterDB/src/main/resources/db/create/hsqldb/sec/V_51__create_sec.sql?raw=True
https://github.com/nikulinn/Joomlasite/blob/ff7ec716015559dda0cf6a519e49f6a117dde967/Загрузки/jdk1.7.0/demo/db/programs/toursdb/ToursDB_schema.sql?raw=True
https://github.com/gmeurant/benerator/blob/a2cc4ab5bee15d464b76bf5c1db706dd97d7636d/benerator/tags/release-0.7.6/src/demo/resources/demo/shop/derby/create_tables.derby.sql?raw=True

fix released in version 0.27.0 (https://pypi.org/project/simple-ddl-parser/), continue working on other issues


Links breakpoint in Breakpoint View with Code Editor for scala class file

NOTE: no tests added because need non headless mode to run

LGTM


Issue 53 refactore components

Tipo da mudança

[ ] Resolve erros do esLint
[ ] Retira modais inúteis
[ ] Issue que resolve erro do esLint  (Issue 30)

Pull Request Test Coverage Report for Build 105

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 98:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


event_hook.py:132: Удалить или задокументировать...

The puzzle 802-ba09c822 from #802 has to be resolved:
https://github.com/blablatdinov/tg-quranbot/blob/686fe4a4224e67820a84993d231830e322988ca2/src/srv/events/event_hook.py#L132-L132
The puzzle was created by Ilaletdinov Almaz on 20-Jun-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 802-ba09c822 has disappeared from the source code, that's why I closed this issue.


Delete peruse branch

Now that peruse is in master there is no need for the peruse branch. Once PRs & any references have been switched over we can delete this branch

Closing legacy issues - Peruse branch has been deleted


Connect to BTCPayServer Node prompting for Password

When connecting to the BTCPayServer LND Node, using the GRPC Connection String, I get prompted for the wallet password. When entering password the following exception is returned: "Cannot read property 'walletunlock' of null".
Wallet isnt locked in the first place
Your Environment

Zap version: 0.7.4
BTCPay Server version <IP_ADDRESS>

Same, im connecting directly to LND but my wallet is automatically unlocked with --wallet-unlock-password-file option
2021-10-29 19:51:52.994 [ERR] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet]: wallet already unlocked, WalletUnlocker service is no longer available

I removed the unlockWallet step and its working fine now, not really sure how to selectively show this prompt when login is required..
Maybe this could be a quickfix for @mrfelton
https://github.com/LN-Zap/zap-desktop/blob/33fc554d37c0aa5a748c95cd8936412c82061600/renderer/containers/Onboarding/Steps/Login.js#L11

Pretty sure this should be fixed in latest v0.7.6-beta release. Could you verify please @v0l ?

Pretty sure this should be fixed in latest v0.7.6-beta release. Could you verify please @v0l ?

I am getting the same issue with v0.7.6-beta.. FYI tried only custom build to enable testnet

unlockWallet,

Not working for me... I am not expert of NodeJs but just trying to setup a test node with btcpayserver to demonstrate how btc payment works and how to make it cheaper and fast with lightening network.

@mrfelton this version connects fine for me now. Maybe @gandalf7777 is having a different issue

Works for me on clearnet connections.
But connection to Umbrel (default host name umbrel.local) over tor still produces error with version 0.7.6
"Cannot read property 'unlockWallet' of null"

I have the same issue connecting to a LND node

+1 here
Wallet is already unlocked, but it keeps asking me the password. Even providing the correct password, the connection fails

I have the same problem connecting to litd over clearnet. If I however connect to litd over VPN (using local IP address instead of my DDNS URL) then it works fine.

i knew it, just had to be the 'autounlock' - but the questions remain ; why doesnt zap see that the wallet is unlocked ? As long as this isn't answered, ppl will keep experiencing the same issue. or an easier solution might be to reach out to Raspiblitz and ask them kindly to mention it in their documentation i.e -ZAP doesn't approve of autounlocking 'features'. - so remember folks -No hanky-panky with your eyes closed... i mean, no shortcuts - read the docs : p


Wip front g UI

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@b7115b5). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   24.64%
=======================================
  Files           ?        9
  Lines           ?      280
  Branches        ?        0
=======================================
  Hits            ?       69
  Misses          ?      211
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Frontend


[enhancement] Sample help text for each fields

Observed keeping invalid values in fields are allowed, but when download and kept in nginx conf. file hitting issues.
Dummy samples or some validations can be given in UI for each available options.
Error message for policy mentioned in attached image:
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: {
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: "completed_successfully" : false,
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: "error_message" : "Failed to import Policy 'policy_name' from '/etc/app_protect/conf/waf.json': Unknown Open API Content format.",
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: "error_line_number" : 23
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: }
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal nginx[1832]: nginx: [error] APP_PROTECT { "event": "configuration_load_failure", "software_version": "3.639.0", "error_message":"Failed to import Policy 'policy_name' from '/etc/app_protect/conf/waf.json': Unknown Open API Content format.","completed_successfully":false,"error_line_number":23}
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal systemd[1]: nginx.service: control process exited, code=exited status=1
Sep 16 07:42:45 ip-172-31-21-251.ap-south-1.compute.internal systemd[1]: Failed to start NGINX Plus - high performance web server.

I see two items here:

Issue: schema doesn't validate openapi link content
Enhancement: notify a user what content is acceptable in the field

Missing link format validation in new UI as well

Error Message:
Dec 22 07:48:14 ip-172-31-20-26.ap-south-1.compute.internal nginx[1703]: {
Dec 22 07:48:14 ip-172-31-20-26.ap-south-1.compute.internal nginx[1703]: "completed_successfully" : false,
Dec 22 07:48:14 ip-172-31-20-26.ap-south-1.compute.internal nginx[1703]: "error_message" : "Failed to import Policy '/etc/app_protect/conf/waf-1639385507591.json' from '/etc/app_protect/conf/waf-1639385507591.json': Wrong link format, should be 'file:///FILE_NAME' or 'http(s)://DOMAIN_NAME/FILE_NAME'",
Dec 22 07:48:14 ip-172-31-20-26.ap-south-1.compute.internal nginx[1703]: "error_line_number" : 19
Dec 22 07:48:14 ip-172-31-20-26.ap-south-1.compute.internal nginx[1703]: }


Error : Invalid Client_id

Created native app in iTwin Platform

Application type: Native

-Redirect URIs: http://localhost:3000/signin-callback
Added Client app ID in “ITwinAppIdHelper” actor details
Added Itwin Model ID in “iTwinImodel” actor details
Unable to authorize after entering: iTwin Model ID in “iTwinImodel” actor details
This error pops up in the browser authorization window

Kindly let us know how to troubleshoot this.

Hi AnantaVC, can you share a capture of your app settings from https://developer.bentley.com/apps?


Create csv-options-export.py

Based off the original csv-export.py, this script will export all your options trades from Robinhood.

I wanted to contribute to this project by providing a way to also export options trades. I created a separate file in order to not cause any issues with the original csv-export.py file.
We do have to update the Robinhood.py file to include this new endpoint for this to work.
"optionsOrders":"https://api.robinhood.com/options/orders/"

Thanks for this. Would you mind including the change to Robinhood.py in your pull request?

Hey Josh, kind of new to this and couldn't figure out how to add another file to the existing pull request, so I ended up doing a 2nd pull for this Robinhood.py update.

No worries, thanks for getting that in. Much appreciated.

Hi Josh, we may update the readme to reflect the new commands:
Something like this?
For exporting stock trades, run:
python csv-export.py
For exporting options trades, run:
python csv-options-export.py

Done! Thanks again.


[Feature Request] Different coloured XP globes for each skill

I would love to have each skill's xp globes in a different colour, just like in konduit, I think it makes them look a lot nicer, customisable colours would be even better.

Being worked on:
https://github.com/runelite/runelite/pull/2255


Publishing an OTA after eas:build crashes the app due to missing env vars

Couldn't find any exact issue on this, so decided to ask here.
Anyway, I built an app through eas build, then installed the APK on android, and everything works fine for the specific release channel.
When trying to test that OTA updates work using expo publish on the same release channel, the APK app crashes right after it downlaods the update.
Upon further inspection, the issue is that expo publish doesn't have access to the ENV variables defined in the eas.json file, while eas build does use them perfectly fine.
And yes, I tried --target bare as well for publishing.
So is it not possible to access ENV vars from eas.json when running expo publish? Or do I just need to wait for eas update to be publicly released?

@dsokal Hello, I noticed you assigned someone to this. I was wondering if you could confirm then: Can expo publish NOT access eas.json env variables?

this is covered in docs now: https://docs.expo.dev/build-reference/variables/#common-questions


Update repositories.txt

tuya-zigbee-mcu-sdk-arduino-library

Hello @fangamy.
I see you have already fixed the error reported by the bot. However, Library Manager works exclusively from Git tags, so the bot won't be able to see the fix you made until you create a new release or tag in the library repository. You can see that at the time of the release, the problem still existed:
https://github.com/tuya/tuya-zigbee-mcu-sdk-arduino-library/blob/v0.0.2/library.properties#L8
url=

Remember to update the version field in the library's library.properties file as needed before making a release/tag.
Once you have done that, simply mention @ArduinoBot in a comment here to trigger it to run the automated checks again. After those are passing, your library will automatically be added to Library Manager.


Current Location

I'am chiness , I hava a problem , when I use this demo,  "mLastKnownLocation" always equals null , so I can't get  Latitude and Longitude, In my project , I only need   Latitude and Longitude  ,so I am not use Google Map , then cause this problem.   ( mLastKnownLocation = LocationServices.FusedLocationApi
.getLastLocation(mGoogleApiClient); )  ,  I want you help me solve  this problem , thank you!

Fixed with null check in PR #141


Test with maxHeapSize=2048m

AppVeyor tests are really frequently failing by Java heap size error. It's not a "solution", but let's get maxHeapSize up...
Can you have a look, @muga?

#714 might have fixed the testing problems. Closing this PR without merging.


Feature Request: autocomplete for export in an imported module

Expected Behaviour:
import {} from 'module';

when cursor is in  {} (or what ever valid format)
import {_} from 'module';

It should show list of available exports

We can utilize this node library get-exports-from-file

I don't mind having a go at this
could you kindly add a Hacktoberfest label to this please :smile:?

sure!


App crashes on select in taskbar

Was working OK on first install but then when changed username and password to blank it crashed.  Now won't stay running, when select icon in tray it quits.  Have tried uninstall re-install but the same. Also rebooted Windows (10).
So can't reinstall or anything.

Hi @GledholtHall. What username and password do you mean? For the scheduled task?
In that case, you can run this command from an elevated command prompt:
schtasks /delete /tn HASS.Agent
Afterwards, open this folder in Explorer:
%appdata%\LAB02 Research\HASS.Agent\config
There, delete the file appsettings.json.
Afterwards, restart HASS.Agent and you'll start at onboarding, without losing your commands/quickactions/sensors.
Let me know if this fixes it for you :)

It was the MQTT credential I blanked out.
Followed the above steps through onboarding but still crashed on startup.  It had retained the MQTT broker settings - I'll have a look where those are stored and try deleting that prefs file too.

The MQTT credentials are definitely stored in appsettings.json. Can you please look if there's anything in the logs, and if so, send me the content (please remove any credentials)? They're in %appdata%\LAB02 Research\HASS.Agent\logs.

I'm closing the ticket as it's solved, but if you do find anything interesting in the logs, please let me know :)


Tag and release first version

Done by @derpoliuk: https://github.com/eggheadgames/ReceiptKit/releases/tag/1.0.1.


XIVY-13506: Fix overflow of header inside autocompletion-details

With this small fix, I can prevent the header text from overlapping other elements. Unfortunately, I don't really have the energy today to  figure out, how to send a shorter type for the header in the core. If you still wish to have the whole thing fixed in the core, I would create a follow-up story and address it after my vacation.

I will have a look at it tomorrow or on thursday 👍

As this type header can be big anyways, I think it makes sense to fix the style and not change the type in the lsp itself.
I've fixed the header type height, so it should no longer overflow


How to configure syslog_drain_binder with custom cipher suites

[ ] I found a bug - here are some steps to recreate it.
[ ] I have an idea for a new feature - please document as "As a user, I would
like to..."
[x] I am having trouble getting setup, understanding documentation, or using
Loggregator in some way - please highlight any resources you are using.
[ ] This is an architecture change that will result in cleaner more efficient
code - Tell us why you think this is a good idea.

Hi,
given that commit https://github.com/cloudfoundry/loggregator/commit/371b5f0eb7902dfee9ba26d5dedbde5bc0758f8d removed the possibility to configure custom cipher suites for the syslog_drain_binder, what is the recommended way to do this now?
Thanks,
Peter
/cc @smoser-ibm

You should not need to configure cipher suites for syslog_drain_binder. The syslog_drain_binder is a client for both etcd and cloud controller. It accepts whatever cipher suites the server negotiates. We removed this property since we want clients to be permissive.
Do you have a use case for syslog_drain_binder to need configurable cipher suites?

@jasonkeene We have clients that use Nagios Log Server via syslog-tls. That setup broke with an update to CF 253. To fix it, it was enough to change the cipher suite on the Nagios Log Server to contain
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

But this is not always possible, e.g. when the service is not self-hosted.
So please correct me if I'm wrong, but it looks like the cipher suite is hard coded on CF side.

You might be running a version of Doppler that enforces cipher suites when talking via TLS to syslog drains. If so that is was bug. I'm fairly sure it is not in the product anymore. I will double check though.

I just double checked and the way we create TLS config for syslog writers is via plumbing.NewTLSConfig here: https://github.com/cloudfoundry/loggregator/blob/0910f42b98b306a6a568347c3da9a242b2bc9081/src/code.cloudfoundry.org/loggregator/plumbing/tls.go#L21-L26 It used to set CipherSuites but no longer does.

@jasonkeene Excellent! Thanks for your help.


Android Shared User Not Working

Describe the bug
android:sharedUserId="android.uid.my_shared_user"
As soon as the shared user is set in the AndroidManifest.xml the following error occurs on the first log entry:
W/System.err: LOGGER WARN: No logging framework implementation found in classpath. Add tinylog-impl.jar for outputting log entries.
This is reproduceable without proguard.
        release {
            debuggable true
            minifyEnabled false
            shrinkResources false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }

I use the following config.
writer1 = rolling file
writer1.file = #{logs.folder}/my_app_{date: yyyy-MM-dd}.log
writer1.backups = 10
writer1.policies = daily, size: 8000KB
writer1.format = {date:yyyy-MM-dd HH:mm:ss:sss} {message}
writer2 = logcat
writer2.format = {message}

An set the the logs folder like:
File appDirectory = new File(app.getApplicationInfo().dataDir);
File logDirectory = new File(appDirectory, "logs");
System.setProperty("logs.folder", logDirectory.getAbsolutePath());

To Reproduce
Steps to reproduce the behavior:

Set android:sharedUserId in AndroidManifest.xml

Environment
compileSdkVersion 30
buildToolsVersion "30.0.3"
minSdkVersion 23
targetSdkVersion 30

implementation 'org.tinylog:tinylog-api:2.3.2'
runtimeOnly 'org.tinylog:tinylog-impl:2.3.2'

Unfortunately, I'm not able to reproduce this issue.
My MainActivity:
public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        File appDirectory = new File(getApplicationInfo().dataDir);
        File logDirectory = new File(appDirectory, "logs");
        System.setProperty("logs.folder", logDirectory.getAbsolutePath());

        Logger.info("Hello World!");
        Logger.info("Logs can be found in \"{}\"", logDirectory);

        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
     }

}

My AndroidManifest:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.tinylog.demo">

    <application
        android:allowBackup="false"
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        android:roundIcon="@mipmap/ic_launcher_round"
        android:supportsRtl="true"
        android:sharedUserId="android.uid.my_shared_user"
        android:theme="@style/AppTheme">
        <activity android:name=".MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    </application>

</manifest>

Output on runtime:
2021-07-27 12:51:09.091 6267-6267/org.tinylog.android.demo I/MainActivity: Hello World!
2021-07-27 12:51:09.092 6267-6267/org.tinylog.android.demo I/MainActivity: Logs can be found in "/data/user/0/org.tinylog.android.demo/logs"

My full demo project: tinylog-android-example.zip

@pmwmedia thanks for the fast response.
I have the same issue in your application if I set the on the manifest tag where it should be.
Android Manifest
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.tinylog.demo"
    android:sharedUserId="android.uid.my_shared_user">
...

2686-2686/org.tinylog.android.demo W/System.err: LOGGER WARN: No logging framework implementation found in classpath. Add tinylog-impl.jar for outputting log entries.
Interesting is that there is an additional log entry which I missed so far.
2686-2686/org.tinylog.android.demo W/ActivityThread: ClassLoader.getResources: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
If I add these line in front of the Logger it works.
Thread.currentThread().setContextClassLoader(getClass().getClassLoader());
Probably you can't do much about that in the library as it seems to be an android thing right?
However, I am not exactly aware of the side effects of shareUserId, will try to find some more info.

I have the same issue in your application if I set the on the manifest tag where it should be.
Android Manifest

Thanks for the correction! I have never used android:sharedUserId before.

If I add these line in front of the "Logger.info("Hello World!")" it works.
Thread.currentThread().setContextClassLoader(getClass().getClassLoader());
Probably you can't do much about that in the library as it seems to be an android thing right?
However, I am not exactly aware of the side effects of shareUserId, will try to find some more info.

This is indeed a very strange side effect of android:sharedUserId. Maybe we can find a way for setting the correct class loader for tinylog automatically?

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.tinylog.demo"
    android:sharedUserId="android.uid.my_shared_user">
...

I'm not even able to install my example app in the emulator.
07/27 14:20:21: Launching 'app' on Pixel_3a_API_30_x86.
Installation did not succeed.
The application could not be installed: INSTALL_FAILED_SHARED_USER_INCOMPATIBLE

I tested back in my application and it works like that.
I have only to set the class loader once before I log the first entry.
I have multiple activities and do the first log call in my derived class from Application.
May this is required on the first logger call as some initialization is done there?
Not sure if this should be in the library as it is security related.
Moreover sharedUserId is deprecated in Android API 29 SharedUserId.
My application will run on a specific android device (with API 27) as a system app and won't be distributed over a store.
Thanks for your support, feel free to close the issue.

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.tinylog.demo"
    android:sharedUserId="android.uid.my_shared_user">
...

I'm not even able to install my example app in the emulator.
07/27 14:20:21: Launching 'app' on Pixel_3a_API_30_x86.
Installation did not succeed.
The application could not be installed: INSTALL_FAILED_SHARED_USER_INCOMPATIBLE

Try to uninstall the old app first, and or change the shared user id and application id.

@epsmae Thank you for your input and research results. I will fix this issue even SharedUserId is deprecated. tinylog 2,4 will use the class loader from the class, if it cannot find any service files via the context class loader of the current thread. This solution is very general and maybe also useful for other class loader related issues,


MyApp crashes on MacOS Monterey with 6.0.401 with CS8802

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/run
Operating System: macos
I have followed steps on the tutorial and got run failed on attempt to run newly created app.
dotnet run MyApp. This was a fresh install from dmg file for Silicon chip M1
donten build or run returns :
/private/tmp/MyApp/Program.cs(2,1): error CS8802: Only one compilation unit can have top-level statements. [/private/tmp/MyApp/MyApp.csproj]
➜  MyApp dotnet --info
.NET SDK (reflecting any global.json):
Version:   6.0.401
Commit:    0906eae6f8
Runtime Environment:
OS Name:     Mac OS X
OS Version:  12.5
OS Platform: Darwin
RID:         osx.12-arm64
Base Path:   /usr/local/share/dotnet/sdk/6.0.401/
global.json file:
Not found
Host:
Version:      6.0.9
Architecture: arm64
Commit:       163a63591c
.NET SDKs installed:
2.1.4 [/usr/local/share/dotnet/sdk]
3.1.404 [/usr/local/share/dotnet/sdk]
5.0.101 [/usr/local/share/dotnet/sdk]
6.0.401 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.10 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.10 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info

I'm exactly not sure but i think many versions of several dotnet versions must be interfering in working
Keep the only version you need right now  or better uninstall all versions and install latest
Install it by this command
brew install dotnet

Was that able to resolve your issue?

I didn't try yet. But I do have multiple net representations such as mono and may be olde .net code versions. I will try to follow provided suggestions. thank you

Brew install helped.  Btw clean up older versions of .net
Thank you
dotnet --info
.NET SDK (reflecting any global.json):
Version:   6.0.401
Commit:    0906eae6f8
Runtime Environment:
OS Name:     Mac OS X
OS Version:  12.5
OS Platform: Darwin
RID:         osx.12-arm64
Base Path:   /usr/local/share/dotnet/sdk/6.0.401/
global.json file:
Not found
Host:
Version:      6.0.9
Architecture: arm64
Commit:       163a63591c
.NET SDKs installed:
6.0.401 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download


More details about the experiment?

hi, thanks for the great work.
I do agree the following descriptions.
The language representations might be a better method for leveraging LLM in autonomous driving
'''
The discrepancy between language and numerical representations poses a significant challenge to incorporating human experiential knowledge and reasoning capability into existing driving systems, thereby widening the chasm from genuine human driving performance.
'''
By the way, I cannot find the appendix in the paper which makes reproducing the experiment difficult. Will it be possible to provide more details about the experiment?  Such as the number of GPU cards, etc.

Hi,
We indeed provide supplement in the updated draft: https://arxiv.org/pdf/2311.10813.pdf. Have you checked it out?
Thanks,
Yue

Hi,
We indeed provide supplement in the updated draft: https://arxiv.org/pdf/2311.10813.pdf. Have you checked it out?
Thanks, Yue

Great. I did not find it is updated.
Thanks for the reminder :).


[tsserver] api to find references to a file

Search Terms

find references (shift f12)
TypeScript server

Problem
If you run find all references on an import path, tsserver will return a list of locations where this file is imported:

However it would also be useful to be able to run this command for a file without first having to find where it is imported. Some example use cases:

Add a command to find references for the currently active file.
Add a right click option in the explorer to find references to a selected file.

See https://github.com/microsoft/vscode/issues/66150 for details on the VS Code side
Proposal
Add a new FileReferences request to the tsserver protocol. This command would take a file path (and optional project name) and return a list of references:
interface FileReferencesRequest extends FileRequest {
    // empty
}

interface FileReferencesResponseBody {
	/**
	 * The file locations referencing the symbol.
	 */
	refs: readonly ReferencesResponseItem[];
	/**
	 * The name of the symbol.
	 */
	symbolName: string;
}

interface FileReferencesResponse extends Response {
	body?: FileReferencesResponseBody;
}

Running this command should return a list of locations where the given file is imported (this matches what running find all references on an import path does)

https://github.com/microsoft/TypeScript/blob/master/src/compiler/program.ts#L758 this should have list where file is referenced from


Works in Zabbix 2.4.8

Fantastic daemon!  :clap:  I got it working with our web front ends running Ubuntu 16.04 using a Zabbix 2.4.8 server.  Happy to post more details, if needed.

Great news. Sure, if you have any feedback or information on the steps it takes, go ahead. It could be useful to include this procedure, along with any gotchas, on the wiki or even in an additional readme-type file.

Install on Ubuntu 16.04:
sudo apt-get install zabbix-sender
sudo npm install -g pm2-zabbix
# test: pm2-zabbix --discover
# run interactively:  pm2-zabbix --monitor

This installed as /usr/bin/pm2-zabbix -- not /usr/local/bin/pm2-zabbix as in the examples.  Also, the user is ubuntu -- not debian.  So configure for systemd:
# swap debian for ubuntu and remove local from path
wget -qO - https://raw.githubusercontent.com/greatcare/pm2-zabbix/master/install/init/systemd/pm2-zabbix.service | sed 's/\/local//' | sed 's/debian/ubuntu/' | sudo tee /etc/systemd/system/pm2-zabbix.service

Edit sudoers as per #1, adding:
zabbix  ALL=(ALL:ALL) NOPASSWD: /usr/bin/pm2-zabbix

sudo systemctl enable pm2-zabbix
sudo systemctl start pm2-zabbix
# stop:  sudo systemctl stop pm2-zabbix
# restart:  sudo systemctl restart pm2-zabbix

Add the UserParameter to Zabbix agent and restart:
wget -qO - https://raw.githubusercontent.com/greatcare/pm2-zabbix/master/install/zabbix-agent/pm2-zabbix.conf | sed s/debian/ubuntu/ | sudo tee /etc/zabbix/zabbix_agentd.d/pm2-zabbix.conf

sudo systemctl restart zabbix-agent

Here is my template Template App PM2 as exported from Zabbix 2.4.8.  It's still work in progress -- but the Item prototypes work, I'm still tweaking/testing the Trigger prototypes.
Thanks again!

I've posted the steps to here (and bootstrapped the wiki along the way):
https://github.com/greatcare/pm2-zabbix/wiki/Install-on-Ubuntu-16.04
Thanks for the contribution - really appreciated. Not closing the issue at the moment in case you have more insight as to the triggers.

I'll post an update in a bit when I have them dialed in.

I don't suppose the wiki is getting an improvement w.r.t. installing on Ubuntu 16.04 any time soon. Closing.


Cherry pick API review suggestions

Update task_query_response.prompty

remove required keys

Update task_simulate.prompty

Update task_query_response.prompty

Update task_simulate.prompty

Fix the api_key needed

Update for release

Black fix for file

Add original text in global context

Update test

Update the indirect attack simulator

Black suggested fixes

Update simulator prompty

Update adversarial scenario enum to exclude XPIA

Update changelog

Black fixes

Remove duplicate import

Fix the mypy error

Mypy please be happy

Updates to non adv simulator

accept context from assistant messages, exclude them when using them for conversation

update changelog

pylint fixes

pylint fixes

remove redundant quotes

Fix typo

pylint fix

Update broken tests

Include the grounding json in the manifest

Fix typo

Come on package

Release 1.0.0b5

Notice from Chang

Remove adv_conv template parameters from the outputs

Update chanagelog

Experimental tags on adv scenarios

Readme fix onbreaking change

Add the category and both user and assistant context to the response of qr_json_lines

Update changelog

Rename _kwargs to _options

_options as prefix

update troubleshooting for simulator

Rename according to suggestions

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-evaluation


SQLite INTEGER and REAL types are generated as int32 and float32 despite being stored as 64-bit

Describe the bug
Per this page about SQLite's data types, INTEGER and REAL columns are loaded into memory as 64-bit ints and floats, respectively. However, jet generates these as 32-bit values, losing some precision:
Environment (please complete the following information):

OS: Linux
Database: SQLite
Database driver: mattn
Jet version v2.10.1

Code snippet
For example, if I have this schema:
sqlite> pragma table_info(shift_recommendations);
0|user_id|INTEGER|1||1
1|ranking|INTEGER|1||2
2|shift_id|INTEGER|1||0
12|date_updated|DATETIME|1||0

user_id, etc should be 64-bit ints, but Jet makes the following model:
type ShiftRecommendations struct {
	UserID          int32 `sql:"primary_key"`
	Ranking         int32 `sql:"primary_key"`
	ShiftID         int32
	DateUpdated     time.Time
}

Expected behavior
By default, INTEGER and REAL models should be 64-bit objects in Go.
I am aware that setting the column types in SQLite to BIGINT and DOUBLE generates 64-bit Go types, but these aren't actually real dtypes in SQLite and would therefore prevent using STRICT tables.

Yeah, I agree. The fix would probably break some builds, but it is better to be safe.
In the meantime, you can use generator customization to change model types.

I'm using jet with SQLite exclusively for now and this behavior also leads to awkward type wrangling throughout the codebase.
Since this would be a breaking change, any plans to make the int64, and float64 the defaults in the next major 3.x.x release?


Update to PHPUnit 6

As we support PHP 7, I've updated our suite of tests to PHPUnit 6.
PS: I won't apply this StyleCI changes. There are not related to this PR.

Thanks!


Update linux-prerequisites.md

Ubuntu 18.x provides libcurl4 in the base packages by default, while libcurl3 is available if universal is enabled.
libcurl4 should be fine for dotnet based on comment here: https://github.com/Microsoft/azure-pipelines-agent/issues/1990#issuecomment-442508288
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Thanks for your PR @BookOfGreg.
@leecow @Petermarcu can you guys help review this PR re. required Ubuntu libraries for .NET Core?

@livarcocc @joshfree  @danmosemsft - I'm not sure where we make use of libcurl. Can we get positive confirmation that all will be well if we update guidance to include libcurl4 where it is available?


Add files via upload

Add ptu16 Mala Vyska

@mirajmv Please provide us with an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the school

@mirajmv You might miss my previous comment. Please react.

Sorry. We provide general secondary education, this includes 2 years of computer science education.

@mirajmv Thank you for the clarification. Pull request merged.


Refactor and modularize user guide

This refactors our user guide, with the goal of being more modular and easier to quickly browse through from the top-level menu. It tries to group things according to their natural theme or topic, and tries to keep the content per-page to be relatively short.
It doesn't change any content in a meaningful way (though adds some explanation here and there to provide more context), it is almost entirely just a renaming / splitting into multiple files / etc PR. Though it touches a lot of files so it will look messier than it is :-)
Given that this touches all of our user guide docs, I'd appreciate if we could have a quick review to make sure it seems reasonable, and then merge and iterate from there so that it doesn't become out of date.

Old user guide:

New user guide:

I believe I addressed all of these @drammock !

Ah yes - OK I think I got that one too

great improvement @choldgraf, thanks!


unreachable code in asio/buffer.hpp with optimizations

MSVC generates this warning:

1>c:\users\vinnie\src\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code

We need to first determine if it is a beast problem.

Same problem here:
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): error C2220: the following warning is treated as an error
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): error C2220: the following warning is treated as an error
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
D:\Sittig\Sources\boost\boost\asio\buffer.hpp(244): warning C4702: unreachable code
LINK : fatal error LNK1257: code generation failed

@Gibson85 Which version of boost are you running?

I am using version 1.72

@Gibson85
Can you quickly check that line to be sure I'm looking the correct code?
My source file is:
  /// Construct a non-modifiable buffer from a modifiable one.
  const_buffer(const mutable_buffer& b) BOOST_ASIO_NOEXCEPT
    : data_(b.data()),        <<<--- LINE 244
      size_(b.size())
#if defined(BOOST_ASIO_ENABLE_BUFFER_DEBUGGING)
      , debug_check_(b.get_debug_check())
#endif // BOOST_ASIO_ENABLE_BUFFER_DEBUGGING
  {
  }

Does that match yours?

That's consistent with what I see.

Yes, that's the line.

Disabling "Whole Program Optimization" did not fix the warning for me, I had to completely disable optimizations with /Od.
Disabling inline function expansion (/Ob0) moves the warning from asio to beast:
C:\libs\boost_1_72_0\boost\beast\core\impl\buffers_cat.hpp(198): warning C4702: unreachable code

    struct dereference
    {
        const_iterator const& self;

        reference
        operator()(mp11::mp_size_t<0>)
        {
            BOOST_BEAST_LOGIC_ERROR_RETURN({},
                "Dereferencing a default-constructed iterator");
        }

        template<class I>
        reference operator()(I)
        {
            return *self.it_.template get<I::value>(); // <--- line 198
        }
    };

Using Boost 1.72.0.

Thanks for narrowing this down. We need to figure out how to modify the beast code to make this warning stop.

For me at least, this also causes a compiler crash (internal compiler error) using MSVC 2017. Although that might not related to the potential bug in boost/asio, it definitely makes it slightly more serious since it's not possible to simply disable the warning.
I've currently worked around it by disabling optimizations for the specific translation unit, but although I do not care too much about performance in my use case, it seems quite wrong, especially considering this is code intended for release.
Is there any other workaround (eg. using another buffer type somehow) or any update on a fix for this?
Thanks.

Is there any other workaround (eg. using another buffer type somehow) or any update on a fix for this?

 If we could put together a small reproducible main function that exhibits the problem, then it might be tractable.

@laudrup if you could share a complete 1-function program that exhibits the crash I'll take a look.

@madmongo1
To be honest, I've only experienced the ICE problem in our build pipeline and haven't been able to reproduce the crash on my development machine, but I assume the actual issue is the "unreachable code" warning.
The warning issue can be reproduced by simply compiling the http_client_async example in release mode using either MSVC 2017 or 2019 (haven't tried with earlier versions) using boost 1.72. Not sure if that can be boiled down more than that.
Not really sure how much more I can help since I have limited knowledge of boost asio/beast internals, but of course I'll be happy to provide any help I can.

@madmongo1 https://developercommunity.visualstudio.com/content/problem/880290/internal-compiler-error-with-msvc-2017-15918-boost.html

It seems like this has been fixed in later versions of MSVC 2019 from around version 16.6.
To be honest I haven't tested exactly which version fixes the issue (switching compiler version on Windows is a bit of a hassle), but I can compile the http_client_async example just fine with version 16.6.1 at least.
Not sure if any actions should be taken, but I wanted to share that information at least.

@laudrup Thanks for letting us know. To be honest, I'm at a loss as to how we should proceed with this, if at all.

@maddinat0r My bad. I had forgotten that it is only an issue in release builds (ie. with optimizations enabled).
Sorry about the confusion. This is still an issue :-(

I do seem to be able to suppress the warning (ie. -wd4702) and have the code build and run without any issues though, so the ICE is at least no longer an issue (for me at least).

I did some digging and I think I found the culprit of those warnings:
https://github.com/boostorg/beast/blob/6f57e5934c1f307e4510ee11dd09594526a3f5d0/include/boost/beast/core/impl/buffers_cat.hpp#L55
Changing that macro to return v for example gets rid of those warnings.
I think it's safe to say that ignoring that warning is a viable solution, as the compiler is warning about something we intentionally want to happen.

Beautiful! So, I think a good fix would be:
#ifdef _MSC_VER
# define BOOST_BEAST_UNREACHABLE_RETURN(v) __assume(v)
#else
# define BOOST_BEAST_UNREACHABLE_RETURN(v) __assume(false)
#endif

I did some digging and I think I found the culprit of those warnings:
https://github.com/boostorg/beast/blob/6f57e5934c1f307e4510ee11dd09594526a3f5d0/include/boost/beast/core/impl/buffers_cat.hpp#L55
Changing that macro to return v for example gets rid of those warnings.
I think it's safe to say that ignoring that warning is a viable solution, as the compiler is warning about something we intentionally want to happen.

This does work. Although just ignoring the warning is not an option at all for codebases that are threating warnings as errors.

There are 2 uses of this macro that I could see:
Here's one:
        net::mutable_buffer
        operator*() const
        {
            BOOST_BEAST_LOGIC_ERROR_RETURN({},
                "Dereferencing a one-past-the-end iterator");
        }

It seems to me that the use of __assume(false) is an un-necessary optimisation, since in a well-defined program the code will never be called in any case.
__assume(false) is a useful optimisation when (for example) one knows that a certain case will not be taken in a switch statement that is executed often.
In this case the code path will be taken exactly once in a program's life, followed by a break into the debugger.

@madmongo1 Yeah, that's true. Btw you can see similar issues here: https://stackoverflow.com/questions/5512560/is-there-a-workaround-for-this-c4702-link-time-warning
It's the very same problem. The person there is trying to catch an invalid usage of template operator() and it is getting that error.
Anyway, I guess that you can just remove __assume(false) as proposed to get the compiler happy. :)

Yup, I'll go ahead and do that in the morning.
On Thu, 18 Jun 2020 at 20:28, Nikolay Baklicharov<EMAIL_ADDRESS>wrote:

@madmongo1 https://github.com/madmongo1 Yeah, that's true. Btw you can
see similar issue here:
https://stackoverflow.com/questions/5512560/is-there-a-workaround-for-this-c4702-link-time-warning
It's the very same problem. The person there is trying to catch an invalid
usage of template operator() and it is getting that error.
Anyway, I guess that you can just remove __assume(false) as proposed to
get the compiler happy. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boostorg/beast/issues/1582#issuecomment-646233621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHOZSISSLKTUQBGUSFNBATRXJMFVANCNFSM4HHJ2NLQ
.

--
Richard Hodges
<EMAIL_ADDRESS>office: +442032898513
home: +376841522
mobile: +376380212

@madmongo1 Just a remainder in case you forgot to change that. :)

Thanks :) The release has been pretty hectic.

@madmongo1 Sorry but I still don't see changes in that regard. Forgot again? :)

Not forgotten. Just dealing with all the other stuff :)

Hmm. doesn't seem to cure it for me. What have I missed?

Don't know, it does fix it for me when I try it...

The problem is back.
boost 1.81
Visual Studio 2022 17.4.3

Disabling inline function expansion (/Ob0) moves the warning from asio to beast:

boost\beast\core\impl\buffers_cat.hpp(206): warning C4702: unreachable code
        template<class I>
        reference operator()(I)
        {
->          return *self.it_.template get<I::value>();
        }

The problem is back once more (I think) with boost 1.84.
target_compile_options(sandbox
	PRIVATE
	    $<$<CXX_COMPILER_ID:MSVC>:/W4 /permissive- /WX /diagnostics:caret /std:c++20>
)

This is addressed in https://github.com/boostorg/beast/pull/2803. You need to upgrade to Boost 1.86.

Ah mb


PLAT-68796: Add more aria property values to verify visually (for debug aria feature)

Checklist

[x] I have read and understand the contribution guide

[ ] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Currently, only aria-label and aria-valuetext display when 'debug aria' is enabled.
It would be helpful if adding more aria properties to verify aria features visually.
This PR will cause more debug aria properties to be displayed on the screen.
Resolution
Support the following property categories in debug aria feature except for few semantical aria properties (ref: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques#States_and_properties)

Role (role)
Widget attributes (aria-checked, aria-disabled, aria-hidden, aria-label, aria-pressed, aria-valuetext)
Live region attributes (aria-live, role)
Relationship attributes (aria-controls, aria-labelledby, aria-owns)
All (All of the above-mentioned attributes)
(sampler:

)

If you want to enable debug aria in your app, the aria property of the category is displayed on the screen by putting the names of the above categories after the debug aria class.
(e.g.)

debug aria role
debug aria widget
debug aria live
debug aria relationship
debug aria all

Additional Considerations

Fixed issue where debug features was not enabled but debug class was included in the sampler

AS-IS
Line: 151~153
if (Object.keys(classes).length > 0) {
	classes.debug = true;
}

TO-BE
Line: 162~165
for (const key in classes) {
	if (typeof classes[key] !== 'undefined') {
		classes.debug = true;
	}
}

LGTM


Cherry pick 5269 to release 0.37

cherry-pick of #5269
Prometheus metrics scraped from virt-handler are now served from the VMI informer cache, rather than calling back to the Kubernetes API for VMI information.

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/lgtm
/approve

/override pull-kubevirt-e2e-k8s-1.19

/override pull-kubevirt-e2e-k8s-1.17
/override pull-kubevirt-e2e-k8s-1.18

Failed on well known flaky tests on this release.


RFP: Tabula - liberate table data from PDF files

Tabula is a tool for liberating data tables trapped inside PDF files
About: http://tabula.technology
Releases: https://github.com/tabulapdf/tabula/releases
Why: If you’ve ever tried to do anything with data provided to you in PDFs, you know how painful this is — you can’t easily copy-and-paste rows of data out of PDF files. Tabula allows you to extract that data in CSV format, through a simple web interface.

Status: Review
https://chocolatey.org/packages/tabula

Status: Published
https://chocolatey.org/packages/tabula
Can be closed.

Thank you!


Bugfix/keep previous data error

closes #1659

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support for RemoteUserBackend with the new mobile app

@borisyankov I'm going to setup a test Zulip server with this branch so that you can test the mobile-side integration.  Will get you details when ready.
I think what the mobile side of this implementation should do is:
(1) If RemoteUserBackend is enabled, then after the user enters the server URL, do an immediate post to /accounts/login/sso with a mobile_flow_otp included in the body of the POST request so that the user can authenticate (well, we could do an interstitial "login" screen, but the only thing on that screen would be an organization name+logo and a "Login" button, which seems superfluous).

Sounds good.

Can you confirm that the mobile_flow_otp replaces all other potential logins like password, Google, GitHub? Or is it possible it is in addition to them?

Just to be clear, mobile_flow_otp is not supported for the password-style logins.  It's only for SSO things: Google, GitHub, and (now) the REMOTE_USER backend.  That backend works by basically letting you do whatever you want on an Apache server that sets the REMOTE_USER variable, and Zulip uses that variable to look up which user it is.  Popular in enterprises that have some random enterprise SSO solution that we haven't integrated with directly.
So this REMOTE_USER backend should functionally work the same as Google auth, except that sites using the REMOTE_USER backend only support that backend, so if that backend is enabled, there's no need to provide a page with options for how to login (there will only ever be one).

Yeah, what you did explain is absolutely clear. Not sure I have the whole picture.
We do a POST to /accounts/login/sso. Do I get the auth in response to this?
What actions would typically the server do to authenticate the user?

Typically, the POST to /accounts/login/sso will redirect or iframe to some third-party SSO auth site (e.g. a login page for their SSO system), and then eventually redirect back to /accounts/login/sso.  But it could also just have e.g. Apache basic auth deployed there, which is what we'll use for testing.

Ah, OK. So we need to do the POST inside a webview then! All clear now.


Import ICA results form EEGLAB

Describe the problem
EEG .set files can contain ICA results. Related data are populated in fields icaweights, icasphere, and icawinv as far as I know. Although users can build mne.preprocessing.ICA objects by hand from these fields, as proposed in here, this requires a good knowledge of the internals of MNE to deal correctly with pre-whitening and similar preprocessing steps such that the results obtained in EEGLAB are reproducible in MNE. It is also error-prone.
Describe your solution
To add an import function to MNE to import ICA components from EEGLAB .set files in a transparent manner.

I'll take a look.

Let me know how it goes. I will need this pretty soon for my analyses so I can code it if needed and share the piece of code I'll come up with. But if you already have some useful code lying around, let me know. It would save me a bit of head-scratching!

A small tentative snippet of code.
from eegip.utils import loadmat
from mne.preprocessing import ICA
import numpy as np
from mne.io import read_raw_eeglab

file_name = '/project/def-emayada/eegip/london/derivatives/lossless/sub-s601/ses-m06/eeg/sub-s601_ses-m06_eeg_qcr.set'

def read_eeglab_ica(file_name):
    mat_file = loadmat(file_name)

    ica_ind = mat_file["EEG"]["chaninfo"]["icachansind"]-1
    ch_names = np.array([chan["labels"] for chan in mat_file["EEG"]["chanlocs"]])[ica_ind]

    ica = ICA(method='imported_eeglab', n_components=len(ch_names))

    mat_file = loadmat(file_name)

    ica.current_fit = "eeglab"
    ica.ch_names = ch_names.tolist()
    ica.n_pca_components = None
    ica.max_pca_components = len(ica.ch_names)
    ica.n_components_ = len(ica.ch_names)

    ica.pre_whitener_ = np.ones((ica.n_components_, 1))
    ica.pca_mean_ = np.zeros(ica.n_components_)
    ica.pca_components_ = mat_file["EEG"]["icasphere"]

    ica.unmixing_matrix_ = mat_file["EEG"]["icaweights"]
    ica.mixing_matrix_ = mat_file["EEG"]["icawinv"]

    return ica

raw_data = read_raw_eeglab(file_name, preload=True)
ica.apply(raw_data)

A few things. The loadmat function is just a version of scipy.io.loadmat that does a better job at reading mat files, in line of what is discussed here https://stackoverflow.com/a/29126361/1825043
Not sure I got right the MNE-EEGLAB correspondence for ICA properties. However, I am not even sure that it is possible to have a perfect correspondence because EEGLAB does not export variables expected by MNE such as the pca_mean_ values and because of differences in preprocessing (e.g., sphering versus whitening and such... as discussed in here ). Anyway, this code runs but its output is not really tested yet. I'll work on coding tests to compare results in EEGLAB and MNE but I thought that I would post this preliminary snippet in case more knowledgeable people (e.g., @cbrnr, @agramfort, @larsoner ) have comments that could save me lot of time investigating obvious issues that I would take a long time to debug because of my limited knowledge about ICA algorithms and MNE internals.

One hint is that we use mne.externals.pymatreader.read_mat to unify over old-style and new-style .mat files. Regarding the other stuff I'm not sure offhand, hopefully your investigations plus our documentation can make things clear.

Thanks for the hint. I replaced eegip.utils.loadmat by mne.externals.pymatreader.read_mat and it works without issues with the rest of the snippet. I'll be happy to drop eegip.utils.loadmat and not have to care for this code anymore.

do yo plan to open a PR?

@agramfort I'll be happy to open a PR when I'll have something suffiently well tested if you think it can help.

Please do share what you have when you are happy about it

I got some code that I'll prepare for PR. It has been tested using
from mne.io import read_epochs_eeglab
from mne.preprocessing import read_eeglab_ica
from mne.externals.pymatreader import read_mat
import numpy as np
import os

mica_root = '/home/christian/Documents/mica_release/'
file_name = os.path.join(mica_root, 'datasets', 'ap82.set')
file_name_cleaned_matlab = os.path.join(mica_root, 'datasets', 'ap82.cleaned.set')

epochs = read_epochs_eeglab(file_name)
epochs_cleaned_matlab = read_epochs_eeglab(file_name_cleaned_matlab)

mark_to_remove = ["manual"]
mat_file = read_mat(file_name_cleaned_matlab)["EEG"]
comp_info = mat_file["marks"]["comp_info"]

if len(comp_info["flags"].shape) > 1:
    ind_comp_to_drop = np.unique(np.concatenate([np.where(flags)[0] for flags, label in zip(comp_info["flags"],
                                                                                comp_info["label"])
                                                 if label in mark_to_remove]))
else:
    ind_comp_to_drop = np.where(comp_info["flags"])[0]

ica = read_eeglab_ica(file_name_cleaned_matlab)
eeg_epochs_cleaned = ica.apply(epochs.copy(), exclude=ind_comp_to_drop)

assert (np.all(np.isclose(epochs_cleaned_matlab.get_data(), eeg_epochs_cleaned.get_data())))

The file used for testing has been downloaded here and processed in Matlab using
file_name_in = '/home/christian/Documents/mica_release/datasets/ap82.set';
EEG = pop_loadset(file_name_in);
N_of_Components = 60;
[EEG.icaweights, EEG.icasphere] = runica(reshape(EEG.data,EEG.nbchan,EEG.pnts*EEG.trials), 'pca', N_of_Components);
EEG.icawinv    = [];
EEG.icaact     = [];

flags = zeros(N_of_Components, 1);
flags(5) = 1;
flags(32) = 1;
flags(43) = 1;
flags(56) = 1;
s = struct('label', 'manual', ...
           'line_color', [0.7000 0.7000 0.7000],...
           'order', 1,...
           'flags', flags);

EEG.marks.comp_info = [s];
EEG = eeg_checkset(EEG);

EEG = pop_marks_select_data(EEG,'component marks',[],'labels',{'manual'},'remove','on');
pop_saveset(EEG, 'filename', [file_name_in(1:end-4) '.cleaned.set']);

I wil prepare the PR but I wont include this test in it because of the dependance on the ap82.set and Matlab. A possibility would be to add both ap82.set and ap82.cleaned.set to the testing datasets of MNE but since it involves adding about 200 MB of data, I do not think it is a good idea. Something with a smaller file could probably be prepared. Alternatively, a test could depend only on ap82.set and a Matlab-python interface library like this one but I do not like the idea of adding an additionnal dependency and a dependency on Matlab.

We already have these test files
https://github.com/mne-tools/mne-testing-data/tree/master/EEGLAB
If you adapt your code to run on these, then we don't have to add any new data.

... oh, except I guess the bits needed to reconstruct the ICA from what you compute in MATLAB

OK. Just seen your comments @larsoner after creating the PR. I can create a separate PR for the tests  (or look at how to modify the current PR to include it).
Yes... so I would need to add two files "test_epochs.cleaned.fdt" and "test_epochs.cleaned.set" based on the Matlab code. I think that this is MUCH better than creating some dependencies on Matlab to generate these files within MNE test suite. I'll look into it.

Yes please do modify the branch in your PR directly. See instructions for adding new test data:
https://github.com/mne-tools/mne-testing-data#add-or-change-files-in-the-repo-for-use-with-mne

@larsoner OK, I pushed the dataset. If I understand well your procedure ("Once your PR is merged, ask a maintainer to cut a new release of the testing data"), I need to wait for one of you to merge this PR request to run my tests. I check to hack the value returned by mne.datasets.testing.data_path(verbose=True) to point it to my git repository of mne-testing-data but this code seems a bit involved.
On a side note, the instructions to run the test does not seems to work on my setup
$ make test
python setup.py build_ext -i
running build_ext
rm -f .coverage
py.test -m 'not ultraslowtest' mne
ERROR: usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --cov-report=
  inifile: /home/christian/mne-python/setup.cfg
  rootdir: /home/christian/mne-python

You have an idea how to get around this? I'd like to run the tests in their current state before adding my new test...

You have an idea how to get around this? I'd like to run the tests in their current state before adding my new test...

You probably do not have pytest-cov installed

... and to test your specific one you should really do something more like:
pytest mne/preprocessing/tests/test_ica.py -k test_ica_from_matlab

Doing make test will take forever.
Then do make flake and make docstyle before pushing your commits to your PR branch. That way you ensure style compliance.
FYI the md5sum I get for testing 0.75 is 51d2ca16c449bbb27a54f53590283f16


Extending CSE support

This PR provides infrastructure and tests in order to extend the support we have for CSE. In particular:

it adds a number of CSE-related tests into a separate CI job; some are not run because of a bug in the booster that is to be fixed by this PR.
To relieve pressure off of the CI, we are running only the CSE versions of the CSE-related tests and commenting out not the non-CSE ones. Eventually, both should be run since they will allow for a precise comparison of the effects of CSE.
It adds a file with lemmas useful for CSE. These lemmas may be upstreamable to KEVM in subsequent PRs.

Make sure to coordinate with @anvacaru , who has some work here: https://github.com/runtimeverification/kontrol/pull/347.
I think it may be useful to focus on internal functions in parallel to his work on automating CSE.

@PetarMax @anvacaru this is becoming quite a huge change, and I'm worried about it stalling out! Is there a subset of the changes that are working well that can be cherry-picked into its own PR?? Then we can get taht merged, and rebase this. Always best to get functionality and tests merged as soon as possible, so everyone is working from the common base and that functionality is guaranteed to be working by CI.

There is an adjustment that needs to be made, please don't merge this PR until the following commit.


Option: log only url and status (building, done,..)

New Feature Use Case
Please, provide an option so we could have in console only something like this:
The server is running on http://localhost:8080
Status: builded // or 'building' or 'error' (and show the error)

Everytime the bundle is updated it should keep showing url and status. Nothing more.
The webpack-dev-server has the option quiet which allows to hide clutter stats but then you must define custom logging and that's too much low level. It would be great if there would be some option which just do that.
Thanks for any response!

Sad panda 🐼 😢  You removed portions of the issue template, so we have to close your issue as invalid. Please don't ignore Issue or Pull Request template sections. They're in the template because they're useful to the maintainers of this project.


Faulty core fix: Array elements aren't aligned at the =>

Given this example:
<?php

array(
	'aaa' => 'b',
	'c' => 'd',
	'eeeeeee' => 'f',
);

The array elements aren't being aligned at the =>. This behaviour isn't explicitly noted in the handbook, just recommended. I can make it more explicit in the Hanbook, thought.

Discussion over on the Core ticket: https://core.trac.wordpress.org/ticket/41057

Additional notes:

As mentioned on Slack: I checked the history of the ArrayDeclaration sniff which used to be included in Core and found that up to May 2015 the array alignment was sniffed for by that sniff, but this was (accidentally ?) taken out when auto-fixing of errors from that sniff was introduced in #378. /cc @JDGrimes
I could not find any discussion about this.
If checking of array assignment alignment would be introduced, should we also revisit the discussion about non-array multi-statement alignment ?$a = 123;
$abc = 'abc';

This is currently also not checked for.
There is an upstream sniff for this Generic.Formatting.MultipleStatementAlignment which has some configuration options.
This sniff was part of the original standard when the project began. Got taken out again in #139, was proposed to be added again in #382 and rejected for not being refined enough in this discussion.

As mentioned on Slack: I checked the history of the ArrayDeclaration sniff which used to be included in Core and found that up to May 2015 the array alignment was sniffed for by that sniff, but this was (accidentally ?) taken out when auto-fixing of errors from that sniff was introduced in #378. /cc @JDGrimes

It looks to me like it was already commented out prior to that: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/378/files#diff-8eb86ff485de5031b1b1644112295065L386
And this goes all the way back to the initial commit:
https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/blob/04fd547c691ca2baae3fa8e195a46b0c9dd671c5/Sniffs/Arrays/ArrayDeclarationSniff.php#L406-L426
Or is there another alignment check that I missed?

@JDGrimes I see what you mean. Seems I was looking in the wrong place (assignment operators in single line arrays which was not previously commented out): https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/blob/04fd547c691ca2baae3fa8e195a46b0c9dd671c5/Sniffs/Arrays/ArrayDeclarationSniff.php#L117-L145

This behaviour isn't explicitly noted in the handbook, just recommended. I can make it more explicit in the Hanbook, thought.

I personally do not think alignment is a good practice to recommend. Adding or removing an item from the array then means all of the items in the array will need to get re-aligned, resulting in messy diffs and conflicting patches. It's also a direct contradiction of the subsequent point in the coding standards, about use of a comma after the last item in an array:

Note the comma after the last array item: this is recommended because it makes it easier to change the order of the array, and makes for cleaner diffs when new items are added.

Adding or removing an item from the array then means all of the items in the array will need to get re-aligned, resulting in messy diffs

That could be partially accounted for by an $exact = false property, similar to how it's done in the ScopeIndent sniff.

Adding or removing an item from the array then means all of the items in the array will need to get re-aligned, resulting in messy diffs and conflicting patches. It's also a direct contradiction of the subsequent point in the coding standards, about use of a comma after the last item in an array

The array might re-aligned, depending on whether you're adding or removing the longest key.
I also find myself less and less concerned about the cleanliness of a diff, vs. the cleanliness of the actual code - I look at diffs and revision history that would be affected by this occasionally, I work with the actual code all day, every day. It seems like a reasonable trade off to make the common case nicer.

To paraphrase - making the resulting code easier to read for everyone >>> making the diff cleaner for the few people who need to read the commit / chase down blames.

I've been working on this sniff and have a couple of questions:

I presume this sniff should be added to the Core ruleset (even though it's not explicit in the handbook) ?

Generally speaking, everything that can be auto-fixed is an error. However, even though this can be auto-fixed, this is currently a recommendation, not a requirement, so should this be an error or a warning ?

If checking of array assignment alignment would be introduced, should we also revisit the discussion about non-array multi-statement alignment ?

On that note: anyone remember why the sniff for this was previously deemed not refined enough ? Particularly code samples would be very welcome so I can see if the upstream sniff can be improved.

On that note: anyone remember why the sniff for this was previously deemed not refined enough ?

I think the main issue I had with the sniff was that it always aligned assignments that were on consecutive lines, regardless of the difference in length between the variable names. I usually only align the assignments if they are within like 5-10 spaces. Sometimes when the difference is greater than that aligning just doesn't make sense (depending on the values being assigned), and can actually decrease readability. I don't think this was configurable, but I might be remembering wrong.
Of course, for array alignment, I tend to not worry about how many spaces need to be used, since it is all part of a single statement. Aligning in an array is almost always more readable. Though I will admit that I'm sometimes pragmatic about alignment even then.

Sometimes when the difference is greater than that aligning just doesn't make sense (depending on the values being assigned), and can actually decrease readability. I don't think this was configurable, but I might be remembering wrong.

It actually is configurable (and looks like it always has been) using the $maxPadding property: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Customisable-Sniff-Properties#genericformattingmultiplestatementalignment

Of course, for array alignment, I tend to not worry about how many spaces need to be used, since it is all part of a single statement. Aligning in an array is almost always more readable. Though I will admit that I'm sometimes pragmatic about alignment even then.

I intend to implement a similar $maxPadding property for the WP Array assignment alignment sniff, so for those of us who want a little more pragmatism, it will be configurable.

On a different note: Based on what I have so far, the sniff would have some overlap with the WordPress.WhiteSpace.OperatorSpacing sniff which checks that:

there is a minimum of 1 space between array keys and the arrow (doesn't check exact spacing before to allow for alignment)
there is exactly 1 space between the arrow and the array value

That would currently result in slightly conflicting error messages addressing the same issue:
  86 | ERROR | [x] Array double arrow not aligned correctly; expected 3 space(s) between
     |       |     "'a'" and double arrow, but found 0
     |       |     (WordPress.Arrays.AssignmentOperatorSpacing.ML_DoubleArrowNotAligned)
  86 | ERROR | [x] Expected 1 space before "=>"; 0 found
     |       |     (WordPress.WhiteSpace.OperatorSpacing.NoSpaceBefore)

Options:

I could remove the double arrow from the WhiteSpace.OperatorSpacing check completely.
Or I could remove the duplicate bits from the Arrays.AssignmentOperatorSpacing sniff, that would lower the maintenance burden as the WhiteSpace.OperatorSpacing sniff comes from upstream, but would make that Arrays.AssignmentOperatorSpacing sniff feature incomplete for when it would be upstreamed at some point (and, yes, this is a candidate for that as it would partially solve upstream https://github.com/squizlabs/PHP_CodeSniffer/issues/582 ).
We could decide that the duplication is is something we can live with and leave it as is.

Opinions ?

I think these are really independent checks that someone might decide to use one without the other. So I don't think that either of them should be removed. Perhaps the ruleset should simply silence WordPress.WhiteSpace.OperatorSpacing.NoSpaceBefore. And/or maybe it could be updated to say "Expected at least 1 space".

Perhaps the ruleset should simply silence WordPress.WhiteSpace.OperatorSpacing.NoSpaceBefore. And/or maybe it could be updated to say "Expected at least 1 space".

The problem with that is that the upstream sniff handles the whitespace checking for a large number of operators and the is no difference in the error codes, so we can't silence it only for the double arrow.
Similarly, "Expected at least 1 space" is only the behaviour for (all type of) assignment operators. For all the other operators, the behaviour is to demand exactly 1 space. Again, as the error code is the same for all operators, we cannot change the message just and only for the assignment operators.

Ah, right. Maybe just remove the double arrow from the WhiteSpace.OperatorSpacing check then. I don't really understand the alternative of removing part of the Arrays.AssignmentOperatorSpacing sniff—how would it still work, what would it still do?

I don't really understand the alternative of removing part of the Arrays.AssignmentOperatorSpacing sniff—how would it still work, what would it still do?

@JDGrimes Having thought about this some more based on the questions you posed, I think removing part of the Arrays.AssignmentOperatorSpacing sniff will in actual fact be the best option. I will also rename the sniff to something like Arrays.MultipleStatementAlignment (better name suggestions welcome).
In the WIP branch, I was checking both spacing before as well as after the => array assignment operator, similar to what the upstream Squiz.Arrays.ArrayDeclaration sniff does and the - now deprecated - WP version of that once did.
For single line arrays, this meant: enforcing exactly one space before and after the double arrow.
For multi-line arrays, enforcing alignment before the double arrow and one space after.
(with some configuration options, but that's besides the point)
This is basically already covered by the WhiteSpace.OperatorSpacing except for the alignment before the arrow.
So, I think it's best to narrow the focus of the sniff and only target the multi statement alignment for multi-line arrays.
That would still yield an overlapping message when no space at all is found between an array index key and the double arrow, but would eliminate the other duplications.
I will adjust the WIP branch and expect to be able to pull this tomorrow.

Ok, so I've pulled two branches now:

#1135 to sort out the double arrow alignment in arrays
#1136 to sort out the equal sign alignment for multiple assignment statements after each other.

One important thing to note about these PRs:
The maxPadding property in the Generic.Formatting.MultipleStatementAlignment sniff works differently than the maxColumn property in the new WordPress.Arrays.MultipleStatementAlignment sniff.

maxPadding determines the maximum whitespace padding between the variable token and the equal sign independently of the position of either on a line.
maxColumn only looks at the position on a line.

I've made the choice to implement a maxColumn property rather than maxPadding for the new sniff as the whitespace padding required is reset for each "group" of assignments by a blank line, a comment, a non-assignment statement, or, if that would be the case, the needed padding getting out of hand.
An array however is never "broken" up like that, so I've let consistency prevail.
Regarding the fact that only blank lines, comments and non-assigment statements break a group of assignments in the Generic.Formatting.MultipleStatementAlignment sniff:
this also means that this code from the tools/i18n/t/NotGettextedTest.php file would get reformatted to align the = for $code with the one for $tokens:
		$code = '
<?php
	$s = 8;
echo /* WP_I18N_GUGU*/ 	"yes" /* /WP_I18N_UGU		*/;
	if ($x == "18181") { wp_die(sprintf(/*WP_I18N_DIE*/\'We died %d times!\'/*WP_I18N_DIE*/)); }
?>';
		$tokens = token_get_all( $code );

This has to do with it $code being assigned a multi-line string, but it still being the same statement.
There is currently no option in the sniff to break the grouping if there are "more than x lines" within in an assignment statement, which when an assignment is an array or a closure could be desirable.
Opinions welcome.

There is currently no option in the sniff to break the grouping if there are "more than x lines"

I don't think it would, or necessarily should, get much use - that feels like it's introducing an exception.
If someone doesn't want an alignment (as I wouldn't if my own code contained this), then they can add a blank line.

There is currently no option in the sniff to break the grouping if there are "more than x lines"

This must be why I stopped using this sniff before. IMO this makes code far less readable, rather than more readable.
That said, as @GaryJones pointed out, you can just add a blank line to overcome this, so an option isn't really needed. I tend to add blank lines to my code liberally anyway, so I probably could live with it.
In fact, I'd prefer if blank lines were added for most of the fixes in WPCS for multiline assignments rather than padding being added.


image Segmentation:why is the tensor value of the dimension resolved when reading tfrecord files is twice as much as is required to rescontruct the dimension？

ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 26136 values, but the requested shape has 13068
[[Node: Reshape = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw, Reshape/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356
[[Node: Reshape_1 = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw_1, Reshape_1/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356
[[Node: Reshape_1 = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw_1, Reshape_1/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356
[[Node: Reshape_1 = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw_1, Reshape_1/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356
[[Node: Reshape_1 = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw_1, Reshape_1/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356
[[Node: Reshape_1 = Reshape[T=DT_UINT8, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](DecodeRaw_1, Reshape_1/shape)]]
ERROR:tensorflow:Exception in QueueRunner: Input to reshape is a tensor with 8712 values, but the requested shape has 4356

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce


Added i18n

Coverage remained the same at 97.54% when pulling ee89f0edc69bfad1f45c922eddf87254316b75b8 on paa001:master into 7ce15bef83e7a8eacd7a076f9171288cd407770e on comfy:master.

Coverage decreased (-0.01%) to 97.54% when pulling 3a822bd014f469f6037401255656094384262dd2 on paa001:master into 7ce15bef83e7a8eacd7a076f9171288cd407770e on comfy:master.

Coverage remained the same at 97.54% when pulling 477dec9d56ecef315e004b9d8b9807a04a470c5b on paa001:master into 7ce15bef83e7a8eacd7a076f9171288cd407770e on comfy:master.

Coverage remained the same at 97.54% when pulling 477dec9d56ecef315e004b9d8b9807a04a470c5b on paa001:master into 7ce15bef83e7a8eacd7a076f9171288cd407770e on comfy:master.

Coverage remained the same at 97.54% when pulling 477dec9d56ecef315e004b9d8b9807a04a470c5b on paa001:master into 7ce15bef83e7a8eacd7a076f9171288cd407770e on comfy:master.

Awesome! Merged.
I tweaked it a bit. Added missing attributes and made pluralization work, so those are reset to English at the moment.


Add "Add To Wallet" buttons for token addresses on the Info page

It seems like this issue can be closed now.

For some reason, after I add the first token in the wallet, subsequent adds do not work.


Use semver to decide whether a plugin can start or not

Is your feature request related to a problem? Please describe.
Currently, all versions between OpenSearch and plugins must match exactly for OpenSearch + plugin to start. Otherwise you get an error (TODO: details of the error).
To work around this problem what we're doing is that we are pre-labelling everything the same version number, e.g. 1.0.0-rc1, build everything with that version, then everything works together. Then we find bugs and do it again, so we end up with multiple artifacts called 1.0.0-rc1. What should happen is that every build produces a new artifact, with a build number e.g. <IP_ADDRESS> and we don't need to label anything rc1 or beta1 (that just wastes time for everyone having to constantly update their build scripts), then we can assemble the artifacts that make up an rc1 together, e.g. security <IP_ADDRESS>, alerting <IP_ADDRESS>, etc.
Describe the solution you'd like
Fix https://github.com/opensearch-project/OpenSearch/issues/622 and use semver to decide whether the plugin is compatible with OpenSearch. Currently that would be that major and minor versions must match, but not a build number or a qualifier.

@nknize would like your comments

@mch2 want to take this assuming Nick agrees with what I'm proposing here?

I think we can do even better here: Split the plugin API into its own version namespace and use that to determine compatibility.
That gives us the ability to define Plugin API 1.0, and implement it in OpenSearch 1.x, 2.x, 3.x etc. Plugins can code against API 1.0 (or 2.0) and not have to care whether they are running in OpenSearch 1.x, 2.x, or 3.x - all they care about is whether this instance of OpenSearch supports the right Plugin API version.
Being able to evolve the plugin API independently of the implementation gives us a lot of flexibility.
Incidentally, I think we should do the same thing for the REST API as well.

@camerski suggestions are good, but I would first fix the problem we have to fix for 1.0, then redesign the compatibility matrix in some future

Yeah, makes sense. Can we relax the strict minor version requirement, though? It seems reasonable for plugin-1.3 to work with opensearch-1.0, or for plugin 1.0 to work with opensearch 1.5.

I'm a little confused how the problem in #622 occurs. Looks like currently the required OpenSearch version of a plugin is always consist of 3 numbers without the version qualifier (alpha, beta, rc ...)
The required version is stated in property "opensearch.version" in plugin-descriptor.properties, like below:

It can be seen from the code, the version used there has 3 components:
https://github.com/opensearch-project/OpenSearch/blob/9c95cf424b405693196deb98f526b5a05916b905/buildSrc/src/main/groovy/org/opensearch/gradle/plugin/PluginBuildPlugin.groovy#L105
https://github.com/opensearch-project/OpenSearch/blob/9c95cf424b405693196deb98f526b5a05916b905/buildSrc/src/main/java/org/opensearch/gradle/Version.java#L104

I was seeing this at some point before beta1, it may have already been fixed, someone needs to double-confirm.

I was seeing this at some point before beta1 and only with -SNAPSHOT and other qualifiers, it may have already been fixed, someone needs to double-confirm.

Seems there is no related changes after that. Looks like the required OpenSearch version is set without the build qualifier.
Meanwhile I think @camerski's idea can relax the developers a lot. 😄

I think the issue I remembered doesn't exist anymore. I installed beta1 and loaded an rc1 job-scheduler and it worked. I'll close this for now.

@camerski will you please open a new issue describing what you're suggesting?


fix(binary): add hashbang on Windows

fix https://github.com/privatenumber/pkgroll/issues/10

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Thanks @privatenumber 👍


Fix history .undo() - unnecessary condition

Hi, I think that this throw Error is unnecessary, becouse if in the tree is stored value that returns false in the if condition you can't use methods .undo (), because it always returns throw error.
This blocking me, because I have a lot of value in the tree like null, false and i get error when i try undo to this value.

Hello @whitcik. You are right, there is a bug here. However, instead of just dropping this condition,  it would be better to change the way the method and the Archive class works so that we may throw the error when needed.

@Yomguithereal hmm, what do you want to change in class Archive and method? I think that works well, and there is no need throw the error.

There is a need to throw an error if you attempt to go back further than it is possible.

@Yomguithereal I added throw an error  in Archive.back(), please check this


requirements.txt problem

C:\stock-trading-bot-master>pip3 install -r requirements.txt
Collecting alpaca-trade-api==0.53.0
Using cached alpaca_trade_api-0.53.0-py3-none-any.whl (36 kB)
Collecting beautifulsoup4==4.9.3
Using cached beautifulsoup4-4.9.3-py3-none-any.whl (115 kB)
Collecting bs4==0.0.1
Using cached bs4-0.0.1.tar.gz (1.1 kB)
Preparing metadata (setup.py) ... done
Collecting certifi==2020.12.5
Using cached certifi-2020.12.5-py2.py3-none-any.whl (147 kB)
Collecting chardet==4.0.0
Using cached chardet-4.0.0-py2.py3-none-any.whl (178 kB)
Collecting idna==2.10
Using cached idna-2.10-py2.py3-none-any.whl (58 kB)
Collecting numpy==1.20.1
Using cached numpy-1.20.1.zip (7.8 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error

Have you ever been able to install numpy? - pip3 install numpy

This is the first time that I try

Is the version of NumPy is important?

I succedded, but
"when installing the dependencies I get the following error:
The conflict is caused by:
The user requested websockets==9.1
alpaca-trade-api 0.53.0 depends on websockets<9 and >=8.0"
the same result like him

I was trying anything it doesn't work.

I can fix in a bit

ERROR: Failed building wheel for pandas
Failed to build pandas
ERROR: Could not build wheels for pandas, which is required to install pyproject.toml-based projects
I think that it is because python 3.10 should I change the version of python?

Perhaps, current requirements.txt works for me.

I checked it on another device and it worked

I was able to run it on docker but there I encountered another error
Traceback (most recent call last):
File "runner.py", line 65, in
alpaca = alp.Alpaca()
File "/alpaca.py", line 8, in init
self.account  = self.api.get_account()
File "/usr/local/lib/python3.8/site-packages/alpaca_trade_api/rest.py", line 184, in get_account
resp = self.get('/account')
File "/usr/local/lib/python3.8/site-packages/alpaca_trade_api/rest.py", line 162, in get
return self._request('GET', path, data)
File "/usr/local/lib/python3.8/site-packages/alpaca_trade_api/rest.py", line 125, in _request
return self._one_request(method, url, opts, retry)
File "/usr/local/lib/python3.8/site-packages/alpaca_trade_api/rest.py", line 154, in _one_request
raise APIError(error, http_error)
alpaca_trade_api.rest.APIError: request is not authorized

@dididadawd did you find a solution to this problem?

Did you get yourself new alpaca api keys and plug those in?

Yes, thank you. I had plugged the in the wrong way.

Had the same issue. Just update the versions in the requirements.txt and it should work.

Stay with docker image its running python 3.8 and all the requirements work there

i keep getting an error when i install requirement.txt   cant create the numpy wheel. I googled it and nothing works for me
can anyone help?

What work with me is delete the update specification in pandas and numpy inside requirement.txt


Add prepared Rollable Tables for Item Piles

Item Piles ca use Rollable Tables to quickly setup Merchants.
Having several prepared Rollable Tables for different types of items, or by rarity would help setup interesting traders easier.

Done in v1.1.0


System.MissingMethodException: 'Method not found: 'Void BoDi.ObjectContainer.RegisterTypeAs(System.String)'.'

I have no idea what's happening but I am encounter this error when I run my test scenarios.

Hello @juanp817,
Unfortunately this project is not maintained anymore as you can find everything in  SpecFlow.DependencyInjection


Serve a webpage from each scanner which explains the scanner's purpose

Have each scanner serve a redirect to a static page explaining why we are scanning.  This gives customers another method to identify our scanners and hopefully head off any abuse reports.
Here is a good example:
http://researchscan273.eecs.umich.edu

Maybe also (if possible) put that in the "whois" data for those scanners? That way if someone tries to track back an observed scan, by looking up the IP, they can know where to go?

If I follow what @IanLee1521 is saying, then I think don't that's possible here. The source IPs belong to the cloud service provider, and we likely have no equity in modifying what ownership info ARIN represents in WHOIS.

Ah, yes a good point. If you weren't using a cloud provider this might be relevant, but I suspect you are in most (all) cases, so you can ignore my comment. :)


Gene list search: provide options for exact and partial matches

Previously the gene list search returned any gene starting with a given gene id/name. For example PSY also returned PSY1,2,3 genes.
In version, 4.0 we changed this to return only exact matches. For example, PSY only returns PSY genes.
It would be nice to have both options exact and partial matches. Could be implemented as a wildcard (PSY*) or as a check box.

The code filtering on the user-provided gene list is in KGUtils. filterGenesByAccessionKeywords().
As you can see, it is based on exact matching of genes's accessions or names and for genes in the current TAXIDs.
We could change this into searching the user genes via Lucene. This would allow us to also support the Lucene syntax (eg, TP*).
However, it's not clear if such syntax should be enabled by default, enabled based on "quotes" or a similar mechanism. Related to this, we might have problems like: in TOB1-AS1, '-' is likely meant to be a literal part of the accession, while in Lucene it means 'without AS1'. Lucene supports "quoting" or \escaping, but hardly the end-user will find that easy to use (and it might be problematic for copy-pasted lists).
Another option might be to introduce some special prefix to enable Lucene syntax, eg, ||TOB1-AS1. In this case, the default would be exact matching.
Another similar problem would be that, if Lucene syntax is enabled by default, all search strings would be tokenised and all tokens would be used for partial matching. Eg, TOB AS1 is split into TOB and AS1 and then TOB1-AS1 or TOB-AS10  would both match, while neither TOB nor AS1 would match (cause the space is interpreted as AND). This can be overcome by "TOB AS1", but again, not so easy for the end-user.

Current logic is:
Set<String> userGeneIDs = set from user-provided list
for each gene in configured TAXIDs:
  if gene's ID in userGenes:
    add to result

This is has a linear complexity, O(n+m), where: n := # genes in TAXIDs, m := # user list.
With any non-exact matching (partial, REGEx, fuzzy, etc), it's impossible to check if an ID is in the user-provided IDs with complexity O(1), unless some index is used.
Our Lucene already stores what's needed, it just needs some time to be implemented here.

Gene list search doesn't feel slow from a UX perspective, although n=115,000 in wheat. Using Lucene would be the ideal solution, but only if it's not to much work to implement, otherwise the O(n+m) complexity is not a concern for now.

Right now it's fast enough, but the problem is that, if we have to use something more complex than exact matching, we can't use Set.contains() anymore, and it would become O(n*m) without an index.

Ok sounds like we should implement it the Lucene way, would be a nice feature to include in the 5.0 release and at the same time we can claim to have improved the performance of the gene list search. :)

fyi Marco is working on it

@KeywanHP this is done. I've written several unit tests and checked it manually, have a look you too and possibly close this issue.

This is epic! Thank you @marco-brandizi
I'll do a bit more testing before closing the ticket.


Use Laravel Auto-Discovery

Thanks for the PR!
Before I accept it, could you help remove the extra closing bracket below composer require maqe/laravel-sqs-fifo?

@tuwannu sorry, fixed

Thanks again!