Create shapes,#204_Bhaskar.html

This pull request introduces a visually appealing and responsive layout to an existing project, focusing on the presentation of content related to the ICC T20 Cricket World Cup. The added styles define a clean and modern look, optimizing the display for both desktop and mobile devices.
The layout is structured using CSS Grid, offering a two-column design for larger screens and transitioning seamlessly into a single column for screens with a width of 768 pixels or less. The design incorporates a hero section with a prominent heading, enticing users to explore the world of cricket. A 'Discover' button encourages interaction, linking to a Wiki page with additional information about cricket and its similarities to baseball.
The content is divided into text blocks, each accompanied by relevant imagery. The first text block introduces the upcoming ICC T20 Cricket World Cup, accompanied by an image of a stadium. The second text block provides an insightful comparison of cricket rules using baseball terminology, complemented by an image of a trophy. This enhances the user experience by combining engaging visuals with informative text.
This addition not only enhances the visual appeal of the project but also ensures a seamless and responsive presentation of cricket-related content, aligning with modern web design practices.

Heartfelt Thanks for Your Contribution to Our Open Source Project!
Dear @BDG10 (Bhaskar Gnanasakthi),
I trust this message finds you in good health and high spirits. I am reaching out with a heart full of gratitude for your recent contribution to our open source project. Your dedication has not only elevated the functionality of our project but has also exemplified the collaborative spirit that lies at the core of thriving open source communities.
A heartfelt congratulations are in order for your exceptional work! Your commitment and expertise have played a pivotal role in the success of our project, and we consider ourselves truly fortunate to count you among our community members.
I must extend my sincere apologies for the delay in responding to your pull request. Your patience and understanding during this time are immensely appreciated. As our project continues to grow, we acknowledge the imperative need to enhance the quality and response time for contributions. To address this, we've kickstarted a call for maintainers and reviewers who can help us uphold the high standards of our project and ensure swift responses to pull requests.
Your involvement and insights would be invaluable in this initiative. If you, or someone you know, is interested in taking on a more active role in the project, please don't hesitate to reach out. We firmly believe that with a robust team of maintainers and reviewers, we can elevate both the quality of the project and the speed of our responses.
On an exciting note, I am thrilled to share that we have activated the sponsorship button for our project. This development allows supporters like yourself to contribute to the sustainability and growth of the project. Your ongoing support, whether through code contributions or sponsorship, is genuinely appreciated.
Once again, congratulations on your outstanding contribution, and thank you for being an indispensable part of our open source community. We eagerly anticipate your continued collaboration and shared success.
Best regards,
Ntem Kenyor K.
Lead
Kwickerhub


Horizontal and Vertical Layout

Hi there,
I've add this at the request of a friend who uses the site.
It adds a horizontal theme which makes the code editor the full width of the page. Please see the screenshot below.

By default the theme is still vertical but the horizontal layout is saved to localstorage if clicked. Further, if the user decides to switch back to the vertical layout then that will be saved also.
The buttons perhaps need some work but other than that, good to go!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2603981). Click here to learn what that means.
The diff coverage is 83.88%.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   83.88%
=========================================
  Files             ?        9
  Lines             ?      180
  Branches          ?       24
=========================================
  Hits              ?      151
  Misses            ?       29
  Partials          ?        0

Impacted Files
Coverage Δ

server/db/mongoose.js
100% <100%> (ø)

server/db/fiddles.js
100% <100%> (ø)

server/app.js
100% <100%> (ø)

server/db/users.js
38.46% <38.46%> (ø)

server/routes/auth.js
65.21% <65.21%> (ø)

server/routes/index.js
66.66% <66.66%> (ø)

server/routes/static.js
66.66% <66.66%> (ø)

server/auth.js
75% <75%> (ø)

server/api.js
94.28% <94.28%> (ø)

Continue to review full report at Codecov.

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


num_api_servers, number of service, and nginx routing don't add up

On alpha we have num_api_servers set to 10.
That leads to 10 services on the machine
sirepo# systemctl list-units --type=service --state=running | grep 'sirepo@'
<EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS><EMAIL_ADDRESS>         loaded active running<EMAIL_ADDRESS>
But, nginx routing is only 0-8
~# grep 'server ' /etc/nginx/conf.d/<snip>conf
server {
    server <IP_ADDRESS>:7000;
    server <IP_ADDRESS>:7001;
    server <IP_ADDRESS>:7002;
    server <IP_ADDRESS>:7003;
    server <IP_ADDRESS>:7004;
    server <IP_ADDRESS>:7005;
    server <IP_ADDRESS>:7006;
    server <IP_ADDRESS>:7007;
    server <IP_ADDRESS>:7008;
server {

The other is a hot spare ;-)


redirectToStdout: httpRequest.latency should be a string and not an object

Hi, not sure if this is an issue with this lib or with the nodejs-logging lib, so I'll start here.
When running the library with redirectToStdout: true  in a container on GCE  the httpRequest serializes the trace-property as an object:
Example:
  "httpRequest": {
    "requestUrl": "/healthcheck",
    "requestMethod": "GET",
    "userAgent": "GoogleHC/1.0",
    "responseSize": 2,
    "status": 200,
    "latency": {
      "seconds": 0,
      "nanos": 1000000
    }
  },

The stackdriver-logging-agent errors out (error message as reported here: https://github.com/GoogleCloudPlatform/fluent-plugin-google-cloud/issues/433) on the httpRequest, since it expects the latency to be a string: https://github.com/GoogleCloudPlatform/fluent-plugin-google-cloud/blob/master/lib/fluent/plugin/out_google_cloud.rb#L1612.
Reference: https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#httprequest (according to this the JSON-representation of the latency is a string, not an object).
If the latency-property on the request log is missing the stackdriver-logging-agent ingests it ok.
Environment details

OS: cos-stable-101-17162-40-16 (with gcr.io/stackdriver-agents/stackdriver-logging-agent:1.9.8
and gem 'fluent-plugin-google-cloud' version '0.12.7')
Node.js version:  v18.15.0
npm version: 9.5.0
@google-cloud/logging-bunyan version: 4.2.2

Steps to reproduce

Set up an express-app as documented here: https://cloud.google.com/nodejs/docs/reference/logging-bunyan/latest#using-as-an-express-middleware
Set the options {redirectToStdout: true} as recommended here: https://cloud.google.com/nodejs/docs/reference/logging-bunyan/latest#alternative-way-to-ingest-logs-in-google-cloud-managed-environments
Deploy the app in a COS-container.
Call the app with curl so a request-trace is printed to stdout.
Tail the stackdriver-logging-agent logs - there will be error-logs in the logs due to the latency not being a string.
Inspect the cloud-logging console for the sent messages. The messages containing the latency-property will not be parsed but passed inside the jsonPayload with the trace-property removed to the logging. Messages not containing a trace-property will be parsed properly by the stackdriver-logging-agent.

Thanks @jonaaasl for opening this issue. I believe documentation is a bit confusing, since on the same page it indicates that latency is actually a string in Duration format.
So I believe that the issue needs to be fixed in stackdriver-logging-agent - please let me know if you have any more concerns or questions.

I'll try to clarify: The latency is a string according to the spec in the Duration format (example 3.5s). The stackdriver expects it correctly to be a string, but it's now written to stdout as an object (example "latency":{"seconds":0,"nanos":11000000}}`.
From what I can tell the httpRequest is written to stdout here: https://github.com/googleapis/nodejs-logging-bunyan/blob/main/src/middleware/express.ts#L107
And created in the nodejs-logging here: https://github.com/googleapis/nodejs-logging/blob/main/src/utils/http-request.ts#L100
Somewhere between the creation and the writing it needs to be turned into that Duration when writing to stdout.

We cannot use latency as a single string (e.g. 3.5s) in our code since Duration is a protobuf structure expected by Cloud Logging service. We could perhaps add a configuration to support single string Duration, but apparently such fix is not going to be a priority. As I mentioned earlier, I believe that the fix should be done in stackdriver-logging-agent (so it can handle all supported formats properly).


Port cdat_info functions

cdat_info.download_sample_data_files has been copied to base.io with some minor changes. The Demo 0 notebook has been run with the updated import statement.
cdat_info.provenance.generateProvenance and dependencies have been copied to base.io with some minor changes. I have combined it with the changes that are currently in base.generateProvenance such as the added packages to record. I have removed references to packages like VCS that are no longer PMP dependencies.

I have not copied cdat_info.get_sampledata_path() because there are no references to it in the PMP production code.
I have removed all references to cdat_info except in deprecated code.
Closes #1003

Still waiting on ENSO notebook testing.

Still waiting on ENSO notebook testing.

Pushed update to ENSO notebook. Now need to debug testing failure.

The line throwing the error (106: author = msg["Author"]) is not found in recent versions of esmpy/init.py. I'm trying to figure out what version is getting pulled by the test suite and if there's a way to grab a newer version.
This esmpy issue provides some additional background: https://github.com/esmf-org/esmf/issues/140

Tried pinning the esmpy version to > 8.4.2 but that caused a failure in setting up the test conda environment. Now trying to pin importlib_metadata to an older version that does not raise the error.

It looks like pinning the importlib_metadata version actually got the test to run successfully. This pin should be removed when we're able to figure out a dev environment that uses a newer esmpy version.

I've created a fix for the build problems in https://github.com/PCMDI/pcmdi_metrics/pull/1107.


[OnlineMeeting&May.25]SeaTunnel community meeting Topic collect meeting

EricJoy2048 invites you to a meeting on Tencent Meeting
Meeting Topic: SeaTunnel Community Meeting
Time: 2023/5/23 20:00-21:00 (GMT+08:00) China Standard Time - Beijing
Click the link to join the meeting or to add it to your meeting list:
https://meeting.tencent.com/dm/UDANouzephGI
#TencentMeeting: 889-560-658
Copy this invitation and open in Tencent Meeting app (V2.13 or later) to join the meeting
Everyone is very welcome to join:
If you have an issue, please submit it one day before the meeting, and provide a specific issue link and context.

New Document Structure

Vulnerability fix

https://z87p7jn1yv.feishu.cn/docx/ZqM7dMM4UoM4KJxOsxjcfdt3nPd


Do not wrap errors for invocations

On both client and server, this does not call errors.Wrap on errors, so the original gRPC error object (with status code and message) is preserved.
Fixes #186

Note: this doesn't stop wrapping all errors. In particular, errors for bindings, queues, etc, continue to stay wrapped as there's no user-customizable gRPC error object underneath anyways.


Adjust Dockerfile Node Version to be Compatible with Hana Client

This issue applies to the following:

Docker Image Version: 1.0.0 (available on dockerhub here: devxci/mbtci)

This docker image uses Node version v12.13.0 which is incompatible with commonly used hana-client packages. This issue is documented in #368
https://github.com/SAP/cloud-mta-build-tool/blob/7eb92592417ed9ff2a471db2ab6d322e971662c1/Dockerfile#L7
I was able to confirm this error by trying to run npm install for a project that uses a hana dependency (in my case<EMAIL_ADDRESS>which has a dependency on<EMAIL_ADDRESS>for both the standard docker images of node:10.13.10 and node:12.13.10 (while also making sure to install other dependencies like node-gyp). What I found was that the install suceeded in the 10.13.10 version and failed in the 12.13.10 version, which is identical to the findings in issue #368.
Given that projects built with this tool will often require interaction with hana, I feel like a compatible version of node should be used in the image.

HI,
As we want to keep our tools up to date we have provided the [lastest stable node].(https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.13.0)
In general, we want to avoid downgrading components to old versions.
Please forward the issue to<EMAIL_ADDRESS>Meanwhile, I've updated our minor release 0.5.0 with  node:10.17.0, see https://hub.docker.com/layers/devxci/mbtci/0.5.0/images/sha256-ec59807852b10eabf3929fd14056a992003fa1d41c89559912f4d8a675018029` use it until the hana-client issue will be solved.

I appreciate you including the old version in the minor release. I'll try to report the issue with the hana-client dependencies but it's a bit more difficult for me as a non-SAPer given those repositories aren't on GitHub 😉

np, i'll try to forward it to the right team :)


Added support for DER encoding to ECSignature

From @stevenroose on March 3, 2014 22:7
Ported this from dartcoin.ECDSASignature.
I implemented the decoding in a quite defensive way by checking validity and throwing a FormatException when something invalid is found. If you don't like this, feel free to omit the checks.
I also know you prefer to omit typechecks, so I used var's instead :)
Copied from original issue: izaera/cipher/pull/66

From @izaera on March 4, 2014 7:27
Let me think about this one. The way to implement encoding I had in mind was by using auxiliar classes: something like, say, "interface SignatureEncoder" and then a "DERSignatureEncoder" implementation. That way, we decouple abstract objects (signatures, keys, and so on) from their encoding.
In your case I'll probably get your code and move it to such encoder. That way, in the future, when ASN.1 is fully implemented, we can get rid of the ad-hoc implementation and use the valid one.
What do you think?

From @izaera on March 4, 2014 7:29
BTW: the case of RSA was different because there's no "abstract RSA signature", the DER encoding has to be fully embedded in the algorithm because it is then hashed to make the signature, so I cannot decouple it.

Well, I thought just because it is only temporarily that an inline implementation was good enough.
This is the way I'm doing it in Dartcoin. I'm doing a lot of inline serialization (usually only +-10 lines), because almost all classes have serialization. If I had to create a separate encoding and decoding class for every regular class, I would have almost 3 times as many files.
If you prefer not adding DER support just yet above accepting this PR, I'm perfectly fine with it, I just thought "I did it for my own class, why not add it to cipher's as well".
(BTW, the reason why I have my own ECDSASignature class was because it required DER encoding and also because it has the ensureCanonical() method to ensure the signature is in canonical format.


pagination-service.d.ts error TS1005: Build:'=' expected

Hi there,
I am having troubles with the typings of the library, I've been looking for the typings in the typing source but they are not there, they are in the dist folder.
So, if I am running the project by node, there is not problem, but when I am running up with Visual Studio. I get 2 errors:

.....\UI\node_modules\ng2-pagination\dist\pagination-service.d.ts(30,14): error TS1005: Build:'=' expected.

......\UI\node_modules\ng2-pagination\dist\pagination-service.d.ts(30,23): error TS1005: Build:';' expected.

I tried to include the typings on the bootstrap file unsuccessfully. Any idea? Thanks!

Hi,
What version of Angular and this library are you using?

Hi,
I have the same problem, and same error messages.
I use Angular 2.0.1 and ng2-pagination 0.5.1.

Sorry, couldn't reply before, same versions from here. I fixed downgrading the version of ng2-pagination.

Thanks @ialex90.  That worked for me too.

Hi,
I have same issue.
Can you please tell me Downgrade to which version?

Hi,
Version 0.4.1 worked for me.

Thanks LasseBrun for your reply.
but still not working,
my app.module.ts file
import { NgModule }       from '@angular/core';
import { BrowserModule }  from '@angular/platform-browser';
import { AppComponent }   from './app.component';
import { PaginatePipe, PaginationService, PaginationControlsCmp } from 'ng2-pagination';
@NgModule({
imports: [
BrowserModule, PaginatePipe],
declarations: [
AppComponent, PaginationControlsCmp
],
providers:[PaginationService],
bootstrap: [ AppComponent ]
})
export class AppModule {
}
it is hitting http://localhost:3000/ng2-pagination
instead of  http://localhost:3000

Thanks LasseBurn.
Now the problem is I am getting ' http://localhost:3000/ng2-pagination 404 (Not Found)' error.

@Sk421 You are importing the components instead the module, that's wrong.
https://github.com/michaelbromley/ng2-pagination/issues/79#issuecomment-252974392

Thanks for your reply @ialex90
Now I am doing this "import { Ng2PaginationModule } from 'ng2-pagination';".
But getting error.

@Sk421 please, provide more info about the error, paste it here and the code for the ngmodule too.

 Let's not forget the subject of the problem,
So, any news about the issue?

Hi. Great to see people stepping in to help one another, thanks 👍🏼
Re the original issue, I'll have time later this week to look into it. Is everyone here using systemjs?

Hi,
Yes, I'am using systemjs.

@michaelbromley me too, thanks :)

I have the feeling that this problem could be solved with the latest version of Typescript, and that just happen in lower than TS 2.0.x, Can you check if that works for you @LasseBrun ?

I use TS 2.0.3. But it might be something wrong with my gulp-typescript. I'll take a closer look at it tomorrow!

@ialex90 The line that your original error points to is:
    readonly defaultId: string;

This suggests to me that the error is due to the fact that this lib is now built with TypeScript 2.x, and perhaps your version of TypeScript is older and does not understand the readonly keyword, which is new.
Check into that.

@michaelbromley this might be helpful:
https://github.com/ng-bootstrap/ng-bootstrap/issues/904#issuecomment-254542060
:)

@ialex90 Thanks, that's good info. So in the next release I will make it compatible with TS 1.8+. 👍


Need to reduce size of whole control or Zoom In/Out should be there on Timesheet Page.

Screenshots
On Live

On Dev

Whole Timesheet design has been changed.


FIPS: DSA/DH changes

Created an internal FFC_PARAMS struct that holds the shared data for DH/DSA domain params.
Common shared methods have been moved into ffc.c
FIPS mode only allows use of either

approved safe prime groups (i.e ffdhe groups) OR
FIPS186-4 (this is for backward compatability in the DH case)

Added code to conform to FIPS186-4/ SP80056A-r3 Generation & Validation of DSA/DH keys.
Notes:

Any new public interfaces for DH/DSA should be removed and replaced with methods that are accessible from the PKEY interface (e.g: additional validation methods). Note also that the existing check methods inside the key ASN method structures are probably in the wrong place.
Once FIPS mode is enabled tests will fail for various reasons (e.g: tests use 1024 bit keys, TLS dh_check call will fail (since fips only allows approved safe prime groups OR fips 186-4 generated key (which require more than just p & g).
The updated safe prime groups were verified by temporarily also loading actual q values and comparing them to the generated q.

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Added documentation for dhparams & dsaparams.

Your pull request description https://github.com/openssl/openssl/pull/8264#issue-253773159 contains a lot of useful information. Please add it to the commit message (at least parts of it).  And please keep https://github.com/openssl/openssl/pull/8763#issuecomment-496244670 in mind.

Addressed by other PR's - so it can be closed..


Long read ingest - exclude existing seq fields from sg meta

This was a total oversight on my part - the changes introduced in https://github.com/populationgenomics/metamist/pull/757 were meant to bring fields from the assay meta into the sequencing group meta, for sequencing groups created from assays where technology == long-read.
The unfortunate side effect was that this also added the fields to the sg meta: sequencing_technology, sequencing_type, sequencing_platform. These are top-level required fields for all sequencing group records, so duplicating these fields in the meta makes no sense.
This change adds those three fields to the list of fields to exclude when porting the assay meta to the sequencing group meta, for long-read assays.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.03%. Comparing base (6c37b9a) to head (1d196bd).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #801   +/-   ##
=======================================
  Coverage   77.03%   77.03%
=======================================
  Files         157      157
  Lines       13068    13069    +1
=======================================
+ Hits        10067    10068    +1
  Misses       3001     3001

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Crash in Samsung S7 with Android 7

Hello
Did you know why the code crash over Samsung S7 with android 7? The error points to a missing file, but file is stil there. :/
io.cpp:36] Check failed: fd != -1 (-1 vs. -1) File not found: /storage/emulated/0/c...
Thanks!

Check this out
Issue #41

It works!
Thank you and sorry for the duplication!


Decorators not working

Hi
I used this for my project and extended the user model , using abstractuser . But My decoraters are not working when I Put them in views . Even the @login_required is not working.

Can you please add snippets of your code.

Did you add LOGIN_URL to your settings?


Support for DS18b20

Could you add support for ds18b20 so no humidity and stuff.
Would be great!

It is not integrated in the pi it's just like the dht22 but it has no humidity sensor and I tried to connect it but it didn't work. If you don't know the sensor google it, it's one of the most famous temperature sensors

I will work on it

After more research, i will not add support for that, since the plugin name contains dht in it and that sensor is a different type of temperature sensor, i would suggest to try a plugin designed for that sensor.
I found this plugin on NPM: https://www.npmjs.com/package/homebridge-ds18b20
@svenbla


Can't Disarm

Hello
I can arm my alarm, but i can't disarm.
i have perimetric mode too.
here are my logs
2024-04-05 11:49:27.249 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Authentication token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:27.249814
2024-04-05 11:49:27.250 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Capabilities token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:27.250181
2024-04-05 11:49:27.250 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request xSDisarmPanel with device_id aa1e25ac73eb4479, uuid aa1e25ac73eb4479 and idDeviceIndigitall
2024-04-05 11:49:27.444 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-05 11:49:27.445 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"errors":[{"message":"4: Requested data not found error.","name":"ApiError","time_thrown":"2024-04-05T09:49:27.423Z","data":{"res":"ERROR","err":"4","status":404},"path":["xSDisarmPanel"]}],"data":{"xSDisarmPanel":null}}
2024-04-05 11:49:27.445 INFO (MainThread) [custom_components.securitas.alarm_control_panel] ('4: Requested data not found error.', {'errors': [{'message': '4: Requested data not found error.', 'name': 'ApiError', 'time_thrown': '2024-04-05T09:49:27.423Z', 'data': {'res': 'ERROR', 'err': '4', 'status': 404}, 'path': ['xSDisarmPanel']}], 'data': {'xSDisarmPanel': None}}, {'app': '{"appVersion": "10.102.0", "origin": "native"}', 'User-Agent': 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.124 Safari/537.36 Edg/102.0.1245.41', 'X-APOLLO-OPERATION-ID': '%BIG_TOKEN%', 'auth': '{"loginTimestamp":<PHONE_NUMBER>025, "user": "%USERNAME%", "id": "OWA_______________"%USERNAME%_______________2024451149250397", "country": "FR", "lang": "fr", "callby": "OWA_10", "hash": "%HASH%"}'}, {'operationName': 'xSDisarmPanel', 'variables': {'request': 'DARM1DARMPERI', 'numinst': '%NUM%', 'panel': 'SDVFAST', 'currentStatus': 'E'}, 'query': 'mutation xSDisarmPanel($numinst: String!, $request: DisarmCodeRequest!, $panel: String!) {\n  xSDisarmPanel(numinst: $numinst, request: $request, panel: $panel) {\n    res\n    msg\n    referenceId\n  }\n}\n'})
2024-04-05 11:49:27.446 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Authentication token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:27.446314
2024-04-05 11:49:27.446 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Capabilities token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:27.446581
2024-04-05 11:49:27.446 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarm with device_id aa1e25ac73eb4479, uuid aa1e25ac73eb4479 and idDeviceIndigitall
2024-04-05 11:49:27.802 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-05 11:49:27.802 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarm":{"res":"OK","msg":"alarm-manager.processed.request","referenceId":"fc082c63-92c6-4844-bf81-8cf2adc4a41d"}}}
2024-04-05 11:49:28.803 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Authentication token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:28.803750
2024-04-05 11:49:28.804 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Capabilities token expires 2024-04-05 11:58:41 and now is 2024-04-05 11:49:28.804067
2024-04-05 11:49:30.805 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarmStatus with device_id aa1e25ac73eb4479, uuid aa1e25ac73eb4479 and idDeviceIndigitall
2024-04-05 11:49:30.890 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-05 11:49:30.890 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarmStatus":{"res":"WAIT","msg":"alarm-manager.processing.request","status":null,"numinst":null,"protomResponse":null,"protomResponseDate":null}}}
2024-04-05 11:49:32.891 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarmStatus with device_id aa1e25ac73eb4479, uuid aa1e25ac73eb4479 and idDeviceIndigitall
2024-04-05 11:49:32.970 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-05 11:49:32.970 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarmStatus":{"res":"WAIT","msg":"alarm-manager.processing.request","status":null,"numinst":null,"protomResponse":null,"protomResponseDate":null}}}
2024-04-05 11:49:34.971 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarmStatus with device_id aa1e25ac73eb4479, uuid aa1e25ac73eb4479 and idDeviceIndigitall
2024-04-05 11:49:35.107 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-05 11:49:35.107 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarmStatus":{"res":"OK","msg":"alarm-manager.status_panel.active_perimetral_alarm_msg","status":null,"numinst":null,"protomResponse":"E","protomResponseDate":"2024-04-05T09:49:33Z"}}}

It has been failing the same for me lately.
It appears that there are some issues with authentication because after some intents if I go to the web, there is a blocking message by their anti-login error system:

@bilbon0bud Do you still have the problem? Sometimes trying a little while later clears issues. If you're still having problems, does your installation have sensors outside (a perimetral alarm)? The logs you sent show that the integration is using the commands for a system with perimetral alarm, but those commands are different for a system without perimetral.

Hello
now i can’t arm or disarm.
I have an outside perimeter alarm.
I can show the status of the alarm only.
‘Best regards

Are you using the latest version of the integration?
Could you send logs of the arming failure? I'm curious to see if you also get a 404 error or something else.
The status in HA is correct and changes after you arm/disarm in the official app?

I ll send you logs in 2 or 3 hours.

Here are the logs

here are the logs when arming
2024-04-27 14:31:12.424 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request xSArmPanel with device_id 06d2a33a2cd1472a, uuid 06d2a33a2cd1472a and idDeviceIndigitall
2024-04-27 14:31:12.692 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarmStatus with device_id 06d2a33a2cd1472a, uuid 06d2a33a2cd1472a and idDeviceIndigitall
2024-04-27 14:31:12.696 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-27 14:31:12.696 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"errors":[{"message":"alarm-manager.alarm_process_error","name":"ApiError","time_thrown":"2024-04-27T12:31:12.671Z","data":{"res":"ERROR","err":"10","status":500},"path":["xSArmPanel"]}],"data":{"xSArmPanel":null}}
2024-04-27 14:31:12.696 INFO (MainThread) [custom_components.securitas.alarm_control_panel] ('alarm-manager.alarm_process_error', {'errors': [{'message': 'alarm-manager.alarm_process_error', 'name': 'ApiError', 'time_thrown': '2024-04-27T12:31:12.671Z', 'data': {'res': 'ERROR', 'err': '10', 'status': 500}, 'path': ['xSArmPanel']}], 'data': {'xSArmPanel': None}}, {'app': '{"appVersion": "10.102.0", "origin": "native"}', 'User-Agent': 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.124 Safari/537.36 Edg/102.0.1245.41', 'X-APOLLO-OPERATION-ID': 'd753753b90d368c06d607fdddc56c3c5c00782a60e9eef86021b6dbf2b5c0b7bf1c4ef4ebc1a8779787dde92c342e98fe08e2455a79837eb0ab9bc344fe94e20', 'X-APOLLO-OPERATION-NAME': 'xSArmPanel', 'extension': '{"mode":"full"}', 'numinst': '%NUM%', 'panel': 'SDVFAST', 'X-Capabilities': 'eyJhbGciOiJIUzI1NiJ9.eyJqdGkiOiI3OWQ3ODVmYi0wN2U2LTQyNDAtODJlNC03NTEyMThkM2E1YWQiLCJpYXQiOjE3MTQyMjA0NTIsImV4cCI6MTcxNDIyMTM1Miwicm9sZSI6IlJFU1RSSUNURUQiLCJpbnMiOiIxNDM1ODI4IiwiY2FwIjpbIkVTVElOViIsIkFSTURBWSIsIkFSTU5JR0hUIiwiUEVSSSIsIkFSTSIsIkdDIiwiQVNJIiwiRVNUIiwiREFSTSIsIklNRyIsIk5PVCIsIkFDVCIsIkNPTkYiLCJDQUxMUklORyIsIkhPTUVNT1ZFIiwiU01BUlROT1QiLCJLRVkiLCJDQU1FUkFTIiwiUExBTiIsIk1ZU0QiLCJQQU5FTENPTkYiLCJTQ0giLCJJTlNUV09SRFMiLCJDT05GU0VSViIsIkNPTkZaT05FUyIsIlBBWU1FTlRHIiwiV0hBVE5FVyIsIkNPTlRNR1JNWVNFUlYiLCJUSU1FTElORSIsIk5PVENPTkYiLCJERVZJQ0VTQ09ORiIsIlJFTUlOREVSUyIsIklOQVBQQ0FNUEFJR04iLCJNQUlMQk9YIiwiQ0FMTCIsIktFWVNSRVBPUlQiLCJBUk1JTlRGUEFSVCIsIkFSTVBBUlRGSU5UIiwiREVBQ1RJVkFURVpPTkUiXX0.O2_LkIMNQ9j93BMGLdIX0SPILPFCsUCph_wTpCBA6_4', 'auth': '{"loginTimestamp":<PHONE_NUMBER>357, "user": "%USERNAME%", "id": "OWA_______________%USERNAME%_______________20244271431424338", "country": "FR", "lang": "fr", "callby": "OWA_10", "hash": "eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJoYXBnbjkzIiwiY250IjoiRlIiLCJjYnkiOiJPV0FfMTAiLCJ2ZXIiOiIxMC4xMDIuMCIsInVzcmlkIjoiNjA1NzYyOCIsImp0aSI6IjYxNDFjODM3LTRhYTItNDMwNS1hOWUxLWYzMmQxYTk2OGYzZiIsImlhdCI6MTcxNDIyMDQ1MiwiZXhwIjoxNzE0MjIxMzUyfQ.awVjSGHUmrziQZtTt7EiNeQ-f9ZCWrMkp4ylN5Y-UbE"}'}, {'operationName': 'xSArmPanel', 'variables': {'request': 'ARMDAY1', 'numinst': '%NUM%', 'panel': 'SDVFAST', 'currentStatus': 'D'}, 'query': 'mutation xSArmPanel($numinst: String!, $request: ArmCodeRequest!, $panel: String!, $currentStatus: String) {\n  xSArmPanel(numinst: $numinst, request: $request, panel: $panel, currentStatus: $currentStatus) {\n    res\n    msg\n    referenceId\n  }\n}\n'})
2024-04-27 14:31:12.792 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-27 14:31:12.792 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarmStatus":{"res":"WAIT","msg":"alarm-manager.processing.request","status":null,"numinst":null,"protomResponse":null,"protomResponseDate":null}}}
2024-04-27 14:31:14.794 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] Making request CheckAlarmStatus with device_id 06d2a33a2cd1472a, uuid 06d2a33a2cd1472a and idDeviceIndigitall
2024-04-27 14:31:14.929 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] --------------Response--------------
2024-04-27 14:31:14.930 DEBUG (MainThread) [custom_components.securitas.securitas_direct_new_api.apimanager] {"data":{"xSCheckAlarmStatus":{"res":"OK","msg":"alarm-manager.inactive_alarm","status":null,"numinst":null,"protomResponse":"D","protomResponseDate":"2024-04-27T12:31:14Z"}}}

The message is 4: Requested data not found error and it's 500 error from their side, so there is nothing much that we can do here.

But everything work from the Verisure app or web…

And you can see the status change in HA when you arm or disarm in the official app?
Have you tried logging out and then logging in in the HA integration?

The status are ok in ha When I change them by the app.
I have try many times to log out and relog or to reinstall the ha app. But … nothing change

I managed to get a 500 error after blocking my account on purpose. After unblocking I have problems similar to what you're having. But I'm also seem to have been flagged as a robot.... I'll try later.

My theory is that the Error 500 comes after a ton of failed authentications. So I think that the debug should be done way earlier, just before the first authentication begins. If I have some time I will start with this because it's killing me not having my automation in place for so long (I've lost the use of disarming in the morning, and it triggers accidentally every other morning)

@SirLouen Same problem for me.

Hello. I have the same problem and what I can say is that it happened after changing the Securitas Direct password and having to reinstall the integration to be able to put the new password in the configuration. Has anyone been able to solve this problem?

Changing from DARM1DARMPERI to DARM1 made it work for me.
No idea why this request uses that const even though i unchecked the "peri" option.

Where can I change it?


When changing an app's category, it does not change. (Kind of)

I was checking out features and noticed that you can change the category of an app. I tried it out on two apps. (FNAF 2 and SFIV CE, which are games but for some reason were in the Apps category.) I changed the category of both to Games. Then restarted the launcher. FNAF 2 was then in the Games category, but SFIV was still in the Apps category.

 Can I set the status bar clock to the 12 hour format instead of 24?

I can't found the code for the actual category change yet, The "Category" field is just there for future implementation, You can check the code for this here and here (The code should be easy enough to understand).
About the Status bar format, you can change it via Settings > Display Settings > Status Bar Text Format. The dialog is not that good yet, you can swipe left and right to choose between Edit and Save, and you can see all {sdf:[format]} format reference here. In your case, It should be only {sdf:dd/M HH:mm} (you should omit the a from there to remove the AM/PM text).

Was fixed in an Action Build.


JBDS-4464 Fuse PLatform does not get added to runtime detection

Fix attaches runtime detection configuration to installation
of fuse tools.

test this

Codecov Report

Merging #782 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #782      +/-   ##
==========================================
- Coverage   97.79%   97.78%   -0.01%
==========================================
  Files          33       33
  Lines        3084     3257     +173
  Branches      259      462     +203
==========================================
+ Hits         3016     3185     +169
+ Misses         68       64       -4
- Partials        0        8       +8

Impacted Files
Coverage Δ

browser/model/jbossfuse.js
89.79% <0%> (+1.22%)
:arrow_up:

browser/model/jbossfusekaraf.js
100% <100%> (ø)
:arrow_up:

browser/model/jbosseap.js
98.09% <0%> (-1.91%)
:arrow_down:

browser/model/helpers/downloader.js
96.94% <0%> (-1.52%)
:arrow_down:

browser/model/cdk.js
99.22% <0%> (-0.78%)
:arrow_down:

browser/model/devstudio.js
88.49% <0%> (-0.7%)
:arrow_down:

browser/model/jdk-install.js
97.29% <0%> (-0.45%)
:arrow_down:

browser/services/data.js
98.71% <0%> (-0.36%)
:arrow_down:

browser/directives/pathValidator.js
100% <0%> (ø)
:arrow_up:

browser/directives/breadcrumb.js
100% <0%> (ø)
:arrow_up:

... and 21 more

Continue to review full report at Codecov.

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

And what happens if you install fuse platform and devstudio without the fuse tooling?


Feature request: when built with /std:c++latest or future /std:c++23, support std::expected<> for wil::reg::try_*

Something like std::expected<std::wstring, HRESULT> = wil::reg::try_get(...) would be a very handy API :)

Ooh, that's super cool! I didn't know about that API. @keith-horton, you might like this---it'd let us have safer nothrow variants!
Something like this, right?
auto value = wil::reg::try_get_dword(...);
if (value.has_value())
{
  std::cout << "value: " << *value << '\n';
}
else if (value.error() == E_FILE_NOT_FOUND)
{
  // ...
}
// ...

At some point, I used this with Boost Outcome's result type, similar to:
template <typename T>
using hr_result = result<T, HRESULT>

// ...

class thing
{
    thing() = delete;
    thing(const thing &) = delete;
    thing(thing &&) = default;
    thing &operator(const thing &) = delete;
    thing &operator(thing &&) = default;

    static hr_result<thing> create();
}

This pattern allows me to avoid exceptions without the need to have out parameters for results. Without a result type like this, it actually wouldn't be possible to delete the default constructor above and two-phase construction ends up being a requirement.
Then I would have macros specifically designed to check the errors, log them if they failed, and return on failure. Back when I did this, I did it with clang-cl so it ended up looking pretty dang decent:
hr_result<DWORD> do_something()
{
    return TRYX(do_a_thing()); + TRYX(do_another_thing());
}

The MSVC alternative would be:
hr_result<DWORD> do_something()
{
    DWORD a{};
    DWORD b{};

    TRY(a, do_a_thing());
    TRY(b, do_another_thing());

    return a + b;
}

or
hr_result<DWORD> do_something()
{
    TRY(DWORD a, do_a_thing());
    TRY(DWORD b, do_another_thing());

    return a + b;
}

which ends up pretty close to how Rust looks with ? syntax, just more verbose.
In future projects, I stopped doing this because the logging of errors on the Windows platform is convoluted to say the least and I needed boilerplate to handle that every time, boilerplate that WIL already handles. I also had to recreate drag the various check macros around specifically meant for Windows result types that had to wrap around boost outcomes result macros. I really like this pattern but the setup was very inconvenient, especially for small codebases.
Just some food for thought.

Is this something that could be done generically across all of WIL at once? Eg a helper of some sort.
Not sure how you could automatically “forward” outparams though…

I used this pattern extensively at a previous workplace... it's very natural for combining 'out' parameters with an error code, and would be a natural fit for using HRESULTs in new / 'modern' C++ code.
I'd envision a helper typedef, something like this:
namespace wil {
template <typename T = void>
using hresult = std::expected<T, HRESULT>;
}

Then, used in an API like so:
wil::hresult<> foo();       // returns 'void' on success; HRESULT on failure
wil::hresult<thing> bar();  // returns a thing on success; HRESULT on failure

Calling functions and checking errors:
// Checking for success is very natural!
if(auto ret = bar()) {
  // Success: Use value in 'ret'... kinda like a smart-pointer
  ret->some_function_on_thing(); // operator-> digs into the return value
  auto my_thing = *ret; // deref to get at the value; alternatively `ret.value()`
} else {
  // Failure: Use error code in `ret.error()`
  HRESULT hr = ret.error();
}

Returning a 'void' on success and HRESULT on failure (i.e., returning wil::hresult<>) is roughly equivalent to just returning a straight HRESULT... but checking for success/failure is more natural... success is true and failure is false!  No SUCCEEDED/FAILED macros required.
Want some result_macros.h-style macros?
#define RETURN_IF_UNEXPECTED(ret) \
do {\
   const auto __errRet = (ret); \
   if(!ret) { \
     return std::unexpected{ret.error()}; \
   } \
}

auto ret = bar();
RETURN_IF_UNEXPECTED(ret);
// Success if we made it here; use value in 'ret'
ret->some_function_on_thing();


docs: Added information about link a web app to Firestore.

This information is provided by the firebase console when a new web app linked to the project is created.
Description
Improvement of documentation.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

This information is already provided here: https://firebase.flutter.dev/docs/installation/web

@googlebot I signed it!

Closing as this information is already provided here https://firebase.flutter.dev/docs/installation/web as mentioned above. Thanks for the PR though!

Closing as this information is already provided here https://firebase.flutter.dev/docs/installation/web as mentioned above. Thanks for the PR though!


The messages blocked as spam should be listed in system logs

Because we do have issues with long messages processing

Won't be listed in system logs but will be registered in a database. Anyway, closed in 9c11a5bcf3c98f9aee55a3bba7263d6411f6ef71


Set time changes

This branch should be changed to general cleanup as much more than set time changes have been added

@GrantBirki Can you point me to the prettier linter/the linter prereqs so I can run them locally

.deploy


[as2_behaviors_platform] Move as2_behaviors_platform actions to as2_msgs

Basic Info

Info
Please fill out this column

Issue(s) this addresses
-

ROS2 version tested on
Humble

Aerial platform tested on
-

Description of contribution in a few bullet points

Move as2_behaviors_platform actions to as2_msgs

Codecov Report

Merging #172 (d3d215c) into main (279fe74) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

:exclamation: Current head d3d215c differs from pull request most recent head dee3892. Consider uploading reports for the commit dee3892 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##            main    #172      +/-   ##
========================================
- Coverage   3.21%   3.14%   -0.07%
========================================
  Files         97      94       -3
  Lines       5004    4988      -16
  Branches     451     466      +15
========================================
- Hits         161     157       -4
+ Misses      4705    4677      -28
- Partials     138     154      +16

Flag
Coverage Δ

unittests
3.14% <0.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...2_behaviors_platform/set_arming_state_behavior.hpp
0.00% <0.00%> (ø)

..._behaviors_platform/set_offboard_mode_behavior.hpp
0.00% <0.00%> (ø)

as2_core/src/platform_state_machine.cpp
42.42% <0.00%> (-13.14%)
:arrow_down:

...2_motion_controller/tests/find_mode_match_test.cpp
45.65% <0.00%> (-6.53%)
:arrow_down:

as2_core/src/utils/tf_utils.cpp
6.12% <0.00%> (ø)

as2_core/src/aerial_platform.cpp
0.00% <0.00%> (ø)

as2_core/src/utils/yaml_utils.cpp
0.00% <0.00%> (ø)

as2_core/include/as2_core/aerial_platform.hpp
0.00% <0.00%> (ø)

as2_core/include/as2_core/utils/yaml_utils.hpp
0.00% <0.00%> (ø)

as2_motion_controller/src/controller_manager.cpp
0.00% <0.00%> (ø)

... and 41 more

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


Issue with merging attribution in Jenkins build

I ran into some issues generating the FBbt release last night, and I think the problem is a knock-on effect of merging in the attribution data during the Jenkins build (which @dosumis and I changed at the end of last year). The most annoying problem is that for some reason the ontology files generated by the build are having the date: and data-version: lines
data-version: 2018-02-21
date: 21:02:2018 22:01

replaced by
data-version: releases/2018-02-21
which doesn't play nice with the release script, because it grabs the data-version: to generate the /releases/ and /tags/ folders. The release script is shared to generate releases for fbbt, fbdv or fbcv, so I don't want to have to change the release script. (I did a quick fix to get the release done last night but I had to manually edit the directory structure in the releases folder afterwards so it's not ideal for long term use).
Another issue with the way the merge works now is that it changes the output files from having a "default-namespace: fly_anatomy.ontology" in the header to having "namespace: fly_anatomy.ontology" in every term. This is a huge drag if we want to check changes with a diff between newly generated release files and previous versions (and I would recommend keeping this checking step in the release SOP). So I manually changed that back in the version of the obo file that I sent to FlyBase. This is annoying for the checking steps but not so much of an issue in terms of what ends up in the release files.
However, there's a couple of other important things I need to add back to the obo header because they're now lost in the merge. But I'm only adding this info manually to the fbbt-simple.obo aka fly-anatomy.obo file that gets loaded into FlyBase - all the other release files will have lost it. Basically, either way we do the merge, we are having to do significant manual edits to the header because either we lose the attribution data, or we lose the date headings and the remark containing info about imports. Neither of these scenarios are good because it means that the majority of release files are losing important info from the header unless it's manually edited.

Ouch.  Pity we didn't catch this earlier. I guess  the easiest fix is to switch back the merge order to the original one and punt the issue of fixing attribution to the next release.

Note to self - Robot doesn't fix merge order issue, but future releases might: https://github.com/ontodev/robot/issues/287


Vercel builds not recognising path aliases

It seems that Vercel is still not able to find modules imported like '~/types/...'


Fading Animation for the opacity of a VMobject

Hi,
i want to change the opacity of a VMobject with an animation and don't know how to manage this.
Does anybody know a solution for my problem?
Thank you in advance for your time and valuable help.

self.play(ApplyMethod(mob.set_opacity, <opacity>))
# or
self.play(mob.set_opacity, <opacity>)

Or
self.play(ApplyMethod(mob.fade, <darkness>))
# or
self.play(mob.fade, <darkness>)

Thanks a lot!
I already tried your first described solution yesterday, but made another mistake and so i thought it doesn't work.


Delete repeated and outdated SolidMotor notebook

Delete repeated and outdated SolidMotor notebook from the docs/notebooks folder.

To be deleted: docs/notebooks/SolidMotor_class_usage.ipynb
To be kept: docs/notebooks/solid_motor_class_usage.ipnb

See issue #185 for details.

Is there a chance of this happening again?


ARROW-2708 [C++] Internal GetValues function in arrow::compute should check for nullptr

This modifies inline GetValues() to log and return nullptr in case one of its arguments / it's contents are nullptr.

Apologies, added a few things last minute. Will close and open new PR.

For future reference, you can keep pushing commits to your branch after opening the PR


http-server inside .out returns module build failed (storybook-angular)

I'm running http-server inside .out folder to check if the static storybook app runs correctly.
Starting up http-server, serving ./
Available on:
http://<IP_ADDRESS>:8080
http://<IP_ADDRESS>:8080
Hit CTRL-C to stop the server
it works properly on
http://<IP_ADDRESS>:8080
but fails on
http://<IP_ADDRESS>:8080
with this error message
Module build failed (from ./node_modules/ts-loader/index.js): Error: error while parsing tsconfig.json at Object.loader (/Users/hrishikeshpotdar/Documents/storybook-master/angular-component-library/node_modules/ts-loader/dist/index.js:19:18)
is there anything that I'm doing wrong in the tsconfig which causes this error? If yes I find it strange how it works on http://<IP_ADDRESS>:8080

Found the issue -
mentioned in the Troubleshoot section
https://storybook.js.org/basics/guide-angular/
forgot to do this part
"exclude": [
"../src///*.stories.ts"
]


Rename to yieldcollect?

Resuming from https://github.com/pytoolz/toolz/issues/557#issuecomment-1435526990 :
I was actually going to suggest just taking this into it's own library, and started workshopping some names.
The best I got was yieldcollect.
Because if I had to summarize the main point/value of putting this out as a separate library, it's collecting generator yields as an ergonomic way to build collections objects.
The compose-as-a-decorator generalization seems less important, and it's good to have a clear theme/focus.
This name is available on PyPI (as of a few days ago).

The caveat is that it depends on what you want here.
If it were me, I'd want a library tightly focused on solving a specific problem. (For example, if I was making yieldcollect, I wouldn't include squeeze.)
If you do want one module serve as a place where you put assorted code that you find useful, then "just a bag of code" is probably a better name.

I guess I could move this code to another library and also make the changes you suggested in #3 this way more people would find it useful.
I was thinking to give it a name somehow related to the word "comprehension", because this is basically what we're doing here - making super complex comprehensions. What do you think?


Localization changes

这个拉取请求对 CoolLKKPS 之前的提交进行了改进,调整了措辞,提高了清晰度,并更贴近原始的 README.md 文件。俄语翻译也已更新为最新信息,并重新措辞以提高可读性。
This pull request improves on the previous commit by CoolLKKPS by adjusting the wording, improving clarity and stay closer to the original README.md file. Russian translation was also updated with the latest information and reworded for better readability.

Great job! Are you interested in translating the text in the mod game into Russian?

@NilaierMusic we want to thx for ur contribution, and yea if u interest the ru localization, feel free to contribution, looks pretty nice really, and i did have some oversight i didn't ask author how does some feature works, oops
will base on ur english translation to change some english config text

btw ur chinese is getting good, even not nature but readable, lets do it for the community!


Breaking changes in 3.0.0

Remove unnecessary ballast:

discontinue javaslang-pure
remove javaslang.Kind1, Kind2
remove Option.nothing()
consider making λ.Memoized package-private/internal
remove Promise (see #1529) - (update: it will most probably stay for we will have new Future API for promises)
rethink or remove run() for Match (see #1216, #1218)
Value.toOption() and Value.getOption() are redundant. Remove one? (However, getOption needs to return this if this instanceof Option)
Widen Validation's List<E> to List<? extends E> in many cases. Also we should consider to change Validation<List<E>, T> to Validation<Seq<E>, T> and use Vector instead of List.
...

Other breaking changes

provide first char upper case static factory methods (see #1431)
indexing collections with int instead of long
consider renaming CheckedFunction0..8 to ThrowingFunction0..8 (one more think to not think about from the user perspective - which one throws, the checked or the unchecked function?)
bring (creational method names of, ofAll) and (conversion names fromXxx, toXxx) into line, e.g.

should it be HashMap.ofEntries(java.util.Map.Entry...) (current state) or HashMap.fromEntries(java.util.Map.Entry...)?
should it be Tuple.fromEntry(java.util.Map.Entry) (#1545) or Tuple.ofEntry(java.util.Map.Entry)
should it be Validation.fromEither(Either) (current state) or Validation.ofEither(Either)
...

We change Match.Pattern.unapply(T) to return R instead of Option<R> by adding PartialFunction to the Pattern type hierarchy. Then we are able to check with isDefinedAt(T) if we are able to unapply an object.
It seems odd to me that Pattern0 'extracts itself'. We should consider that Pattern0.unapply() returns Option<Void>. This would be formally correct because Pattern0 extracts zero parts.

Consideration removing Kind1/Kind2 from core lib
Javaslang claims to be a functional programming library. The algebraic computation layer is important for some of our users. So I ask the question if we can remove Kind1/Kind2 from the javaslang core module while preserving the algebraic extensions contained in the javaslang-pure module.
Status Quo
Currently Kind1/Kind2 live in the javaslang project. These are recursive type definitions without methods:
public interface Kind1<TYPE extends Kind1<TYPE, ?>, T> {
}

public interface Kind2<TYPE extends Kind2<TYPE, ?, ?>, T1, T2> {
}

These interfaces tag types (e.g. List<T>) that can be decomposed into

The context type (e.g. List)
The value type (e.g. T)

The List interface currently looks like this:
public interface List<T> extends Kind1<List<?>, T>, LinearSeq<T>, Stack<T> {
    ...
}

In javaslang-pure the Monad lifts 'ordinary' functions to functions that operate in a monadic context (read: on Monad):
public interface Monad<M extends Kind1<M, ?>, T> extends Functor<T> {

    <U> Monad<M, U> flatMap(Function<? super T, ? extends Monad<M, U>> mapper);

    @Override
    <U> Monad<M, U> map(Function<? super T, ? extends U> mapper);

    Kind1<M, T> narrow();
}

The narrow function is the important part. It allows us to transform the Monad type back to real object type, which is needed to implement Monad.flatMap().
Example: List
static <T> Monad<List<?>, T> of(List<T> list) {
    return new Monad<List<?>, T>() {
        @Override
        public <U> Monad<List<?>, U> flatMap(Function<? super T, ? extends Monad<List<?>, U>> f) {
            return Monad.of(list.flatMap((T t) -> (List<U>) f.apply(t).narrow()));
        }
        @Override
        public <U> Monad<List<?>, U> map(Function<? super T, ? extends U> f) {
            return Monad.of(list.map(f));
        }
        @Override
        public List<T> narrow() {
            return list;
        }
    };
}

Trying to remove Kind1
Our goal is to remove Kind1 from the javaslang core module, e.g.
public interface List<T> extends LinearSeq<T>, Stack<T> {
    ...
}

The javaslang-pure module is adjusted like that:
public interface Monad<M, T> extends Functor<T> {

    <U> Monad<M, U> flatMap(Function<? super T, ? extends Monad<M, U>> mapper);

    @Override
    <U> Monad<M, U> map(Function<? super T, ? extends U> mapper);

    M narrow();
}

The List Monad implementation is then constructed as follow:
static <T> Monad<List<?>, T> of(List<T> list) {
    return new Monad<List<?>, T>() {
        @Override
        public <U> Monad<List<?>, U> flatMap(Function<? super T, ? extends Monad<List<?>, U>> f) {
            return Monad.of(list.flatMap((T t) -> (List<U>) f.apply(t).narrow()));
        }
        @Override
        public <U> Monad<List<?>, U> map(Function<? super T, ? extends U> f) {
            return Monad.of(list.map(f));
        }
        @Override
        public List<T> narrow() {
            return list;
        }
    };
}

The case (List<U>) f.apply(t).narrow() is unsafe. It is correct but cannot be verified by the compiler because Monad.narrow() return M, which is List<?> instead of List<U>.

Removing Monad.narrow() but keeping Kind1
This leads to:
public interface Monad<M extends Kind1<M, ?>, T> extends Functor<T> {

    <U> Monad<M, U> flatMap(Function<? super T, ? extends Monad<M, U>> mapper);

    @Override
    <U> Monad<M, U> map(Function<? super T, ? extends U> mapper);
}

The List Monad implementation can be made safe by making use of intersection types. We can just add the Kind1 interface to the type List (and name it M) because Kind1 contains no methods.
static <T, M extends List<?> & Kind1<M, ?>> Monad<M, T> of(List<T> list) {
    return new Monad<M, T>() {
        @Override
        public <U> Monad<M, U> flatMap(Function<? super T, ? extends Monad<M, U>> f) {
            return Monad.of(list.flatMap((T t) -> (List<U>) f.apply(t)));
        }
        @Override
        public <U> Monad<M, U> map(Function<? super T, ? extends U> f) {
            return Monad.of(list.map(f));
        }
    };
}

Now narrow() is gone and (List<U>) f.apply(t) is safe.
But we loose a common Monad.narrow() in favor of removing Kind1 (and Kind2) from the javaslang core module. This is not eligible because at some point we may want to return from the abstract algebraic computation layer back to the core library layer.
Having said this, we will stay with Kind1, Kind2 in the core lib and also keep javaslang-pure.

CharSeq

rename Seq<CharSeq> splitSeq(...) to Seq<CharSeq> split(...) (CharSeq[] split(...) will be removed)

Memoized might be worth keeping public as I actually had a use case, where I defined a new CustomFunctionX type but overridden the FunctionX.memoized()  to call Memoized.of with a different map implementation (reference map instead of hashmap).

@nfekete We will take it into account. There are some interesting ideas, I opened a separate issue: #1905

I ran into a situation where I need the Lazy#filter to return Lazy and now is not clear whether it will be or not?
https://github.com/vavr-io/vavr/issues/1861#issuecomment-279389738

@danieldietrich: making filter() lazy looks more consistent to my eyes, so let's do the change in 3.0.0

And in this issue I see this point, but it striked out but not completed.
Is this still on question or Lazy#filter always will return Option?
P.S.
Sorry for terrible english :(

@valery1707 Do you have a suggestion what an 'empty' lazily evaluated value could be?
Please also take a look at #1861
I understand declaring a value as 'lazy' means, that there is a value but the evaluation is deferred to the moment the value is needed. Especially we currently can rely on the fact that such a value is always present.
If we allow Lazy to be also empty (read: undefined), it is more like a LazyOption. We could do the same for all other Vavr types, e.g. LazyTry, LazyEither, LazyXyz...
 E.g. instead of Lazy<T> we might want to have Lazy<Option<T>>.

Is there anything a a LazyOption<T> could solve that a Lazy<Option<T>> cannot? Similarly for LazyTry and LazyEither, etc?

@danieldietrich I understand your point of view.
I also do not know to represent empty lazy value :)
I solved my problem just through sort of Lazy<Option<T>>.
The question is removed, thanks for the clarification

@valery1707 nevertheless, your point is valid. I will think about Lazy (filter) for 1.0.0

But we can this:
Lazy<Option<T>> lazyOption = Lazy.of(() -> Option.of(...));
Lazy<Option<T>> filtered = lazyOption.map(o -> o.filter(predicate));

And filtered still be lazy

@valery1707 thx for clarification! That's a really nice solution!
We should Lazy.filter accordingly! I created #2178

Created separate issues for the remaining tasks. See #2182, #2183
Will close this issue.


Wrong opacity behavior on android

Bug
Android color blending is different from others if its parent view has an opacity style.
View -> background red, opacity 0.2
Svg -> fill red
iOS:

Android:

Web:

Environment info
Library version: v13.14.0
Steps To Reproduce
https://snack.expo.dev/LcGquw6tZ

Hi @burakgormek,
It seems like it's not an issue of react-native-svg, but of react-native itself. Can be reproduced even with just a View component, so i suggest opening an issue there.
<View style={{backgroundColor: 'red', opacity: 0.2, flex: 1}}>
  <View style={{backgroundColor: 'red', width: 100, height: 100}} />
</View>


transition to schema.org in our standard demos

Instead of using hardcoded schema defined in manifest files we should import from schema.org

Noticed a couple of issues with importing simple schema.org schemas:

there seems to be some type clashing. E.g., importing schema.org/Event doesn't properly work if Event already exists locally in another manifest.
fields from parent schema aren't being imported

Also (maybe less urgent):

non-basic types are not supported

Couple other notes.

Current supported types I think are declared here, where are as of this writing: var supportedTypes = ["Text", "URL"];

Just those two produce some reasonable types, .e.g.
  {
    "name": "Place",
    "optional": {
      "faxNumber": "Text",
      "address": "Text",
      "maps": "URL",
      "branchCode": "Text",
      "isicV4": "Text",
      "hasMap": "URL",
      "telephone": "Text",
      "map": "URL",
      "globalLocationNumber": "Text",
      "logo": "URL"
    }

But there are other basic types (Integer, Boolean) we don't yet support (and Date, but that's not always basic).

Nested structures are also an issue (for schemas in general). For demos I've done some flattening of data streams so I can fit them into Entity structures.

Feels obsolete, can reopen/dust off if needed.


Autodeployment of statsdumper

For our stats collector we need an influxdb deployed somewhere on a node. AYS needs to be aware of this influxdb service.
We will create a service which wraps influxdb which has some special logic to make nodes join this influxdb, the name of this service will be statsdb (it will consume a influxdb which it will deploy itself, with a fixed dbname).
When a node is deployed and this statsdb service is found the statscollector will be deployed as part of the node.install.
When a node is deployed and the statsdb does not exist this step is skipped.
To make sure all nodes have statscollector running when a statsdb is deployed, we will install the statscollector on the nodes as part of the statsdb.

statsdb blueprint results this error :
    raise j.exceptions.RuntimeError("container didn't stopped")
JumpScale9.errorhandling.JSExceptions.RuntimeError: ERROR: container didn't stopped ((type:runtime.error)
[Mon10 10:02] - RunStep.py          :84  :j.atyourservice.server         - INFO     - runstep 5: error
[Mon10 10:02] - Run.py              :108 :j.atyourservice.server         - ERROR    - error during execution
of step 5 in run 9598d46ffe205a37d3e527857fa61e1a
Error of job: statsdb!two (install):
*TRACEBACK*********************************************************************************
JumpScale9.errorhandling.JSExceptions.RuntimeError: ERROR: container didn't stopped ((type:runtime.error)

Added a check on the status of the statscollector before attempting to stop it.

Software Version
f2c4c5ed9fb94a8316f2b118d16d68fd36078777


Provide a way to flush a queue?

May you provide more details? Examples:

Single node or cluster wide?
Just the queue or also all the jobs inside the queue? And in this case again, should the jobs be evicted cluster-wide?

I can see how sometimes you may want to start from scratch btw, so likely this is going to be needed in one form or the other. A typical example would be an error in the producer that creates a number of useless jobs that can't be processed at all. Another one is development setups.

Testing. During setup you want to wipe up all the queues, otherwise you end of processing jobs from the previous test case/run.

Discussed this with @antirez yesterday. @assaf: for testing, you can run DEBUG FLUSHALL.

@antirez @djanowski sorry I haven't had time to clarify my proposal. I'll provide further info later.

@djanowski did you come to a conclusion with antirez?

I'll re-evaluate this in the next days before 1.0-RC1.

I'm interested in this also. This would be pretty useful  for a huge number of reasons e.g. clearing a queue that a client has flooded with bogus messages.
This is what I propose the command would look like:
QFLUSH <queue> [TTL] [timestamp]

TTL sec flush jobs with a TTL less than this value
timestamp flush jobs created after this timestamp

Any plans for this?

I'd like to see this as well. I've found that it's possible to get into a deadlocked situation where no new messages can be added due to an out of memory condition. Having an easy way to flush a queue from the cluster would be useful when situations like this occur.


Adding users to an org as an owner and other fixes

Closes #4171

[x] Rebased/mergeable

@jeffreyssmith2nd should also take a look at this. Jeff, is this code complete?

@jeffreyssmith2nd should also take a look at this. Jeff, is this code complete?

This work was actually done by @candrewlee14, can you take a look at this?

LGTM!


fix initial selected

These simply fixed #23, please take a look. However, there is another important shortage, the tree doesn't respond to outside selected items changing.

I noticed that the shortage was existed in the old version too. I think it's necessary to realize the feature.

I've taken a slightly different approach in fixing this, see #25. Please verify whether my changes are correct.
About changing the selection from the outside: This is because the SelectedItems are only looked at during first render. So that's why it can't be changed after the first render. I wonder what the use case for this is?

I will look it later, I am going out now.
The reason is that we need to request the selected items from server sometimes, so we need to update it after first render.

A @key on the tree view could help: If you update the key after replacing the list of selected items, the entire tree view will be replaced.

By the way, since we both created pull requests, how can I fetch your code locally? I am a rookie😅.

A @key on the tree view could help: If you update the key after replacing the list of selected items, the entire tree view will be replaced.

Ok, I will try. Thank you.

By the way, since we both created pull requests, how can I fetch your code locally? I am a rookie😅.

I can recommend using the github CLI. In the top right of the PR, you'll find "Open with". If you have the GH CLI installed, you simply execute gh pr checkout 24 to fetch & checkout this PR.

A @key on the tree view could help: If you update the key after replacing the list of selected items, the entire tree view will be replaced.

@page "/selection"
<SourceCodeLink Repository="Blazor.TreeViews" Page="@nameof(Selection)" />

<TreeView @key="SelectedValues" Items="Items" GetParent="GetParent" AllowSelection="true" @bind-SelectedItems="SelectedValues" />

@if (SelectedValues != null)
{
    @string.Join(", ", SelectedValues)
}
<div>
    <button @onclick="@(() =>SelectedValues = new List<string> { })">
        Set nothing Selected
    </button>
    <button @onclick="@(() => SelectedValues = new List<string> { "3" })">
        Set 3 Selected
    </button>
    <button @onclick="@(() => SelectedValues = new List<string> { "3.1" })">
        Set 3.1 Selected
    </button>
    <button @onclick="@(() => SelectedValues = new List<string> { "3.1.1" })">
        Set 3.1.1 Selected
    </button>
</div>
...

I tried using @key to refresh the tree. But there are something strange. If any tree nodes selected, resetting key will lead tree nodes all unselected.


Distinguish Questions and Answers

Improve the user experience by clearly distinguishing between questions and answers in the chat interface, providing visual cues or formatting to differentiate between user queries and system responses.

i will work on this one


[15660:10932:0420/024221.053:ERROR:device_event_log_impl.cc(195)] [02:42:21.053] Bluetooth: bluetooth_adapter_winrt.cc:1057 Getting Default Adapter failed.

Hey man, thanks your project, very helpful me, i havent bluetoth adaptor.Add to line chrome drivers
options.add_experimental_option('excludeSwitches',['enable-logging'])
i dont try firefox.

Thanks for reaching out!
I'm glad you find the project helpful.

Chrome Driver Option: Thanks for letting me know about the excludeSwitches option for Chrome drivers. I'll analyze its impact on logging behavior and consider including it with proper documentation.
Testing Firefox: While you haven't tried Firefox yet, testing across different browsers is a great practice. The project likely includes a function like create_driver('firefox') for launching Firefox. You can explore adding similar test cases for Firefox alongside Chrome.

Next Steps:
I'll analyze the excludeSwitches option and its implications for logging.
I'll consider adding documentation for this option if it proves beneficial.
I would recommend trying the project with Firefox as well. If you encounter any issues, feel free to open a new issue or reach out for help.


Add Note for recognising properties equivalent to foaf:primaryTopic

This PR is a https://www.w3.org/2023/Process-20230612/#class-2 change towards addressing https://github.com/w3c/WebID/issues/24

IMHO this is a major work item that affects test suites.  You would need to gain consensus with the group on:

How substantive the change is
Whether to take it on as a work item
When to prioritize it (superset spec should come first)
The exact set of equivalences

I dont think we should take this on, at this time, in this order.  Once superset is done, and not before that.  The relation between a WebID and a profile document can be established.

IMHO this is a major work item that affects test suites.

I don't believe so.
We have a bigger problem right now, and it takes the form of:
What exactly is a WebID, and what is supposed to be in the WebID Spec.
We are having circular debates as a result of the above.
A WebID is the basic foundation, in the form of an identifier type, used for unambiguous Agent naming that serves the needs of Profile Documents and Authentication Protocols.
A WebID is neither a Profile Document nor an Authentication Protocol. It is an identifier type. The "WebID Identity and Discovery Specification" is a confusing title that attempts acronym recursion in a manner that's backfired --- IMHO.

IMHO this is a major work item that affects test suites.

This change is not a "work item". This is a Note. A non-normative (informative) addition towards addressing the referenced issue.
Which test suites? Are you working on test suites?

You would need to gain consensus with the group on:

How substantive the change is

This PR adds a Note. It is a non-normative (informative) addition. Here is one explanation from the W3C Manual of Style https://w3c.github.io/manual-of-style/#N-I-sections "notes are assumed to always be informative".
The initial comment https://github.com/w3c/WebID/pull/32#issue-2062776903 refers to W3C Process's correction classes ( https://www.w3.org/2023/Process-20230612/#class-2 ) which is a as a guide to help the reviewers assess the proposed change in this PR. And I quote: the "Changes that do not functionally affect interpretation of the document". More details at the referenced link.
That's "how" substantive the change is.

Whether to take it on as a work item

It is not proposed as a "work item". It is proposed a change to the current WebID 1.0 ED, which has been a "work item" of the WebID CG.
If you are interested in what constitutes "work item" and how to approach it the Group, here is the CONTRIBUTING proposal that includes a section on work items: https://github.com/w3c/WebID/pull/31 .

When to prioritize it (superset spec should come first)

Thanks for sharing an answer to your own question.

The exact set of equivalences

No, the proposed text does not suggest that requirement. Furthermore, any equivalences that could be made based on existing vocabulary definitions are not part of WebID CG's "work items", and hence they are out of scope here.

I dont think we should take this on, at this time, in this order. Once superset is done, and not before that. The relation between a WebID and a profile document can be established.

Thank you for your comment.

To clarify.  Hard NACK.  Please gain consensus of the chair and group.

Thanks for sharing an answer to your own question.

@csarven this is completely inappropriate

To clarify. Hard NACK. Please gain consensus of the chair and group.

I don't understand your comment above. I am simply acknowledging what @csarven has contributed. Basically, going beyond a thumbs-up or thumbs-down.
BTW -- why is there an issue drafting PRs? That has nothing to do with "gaining consensus of the chair and group". In the very worst case, a PR doesn't get merged if it isn't approved.
What am I missing here?

/chair hat on

Please gain consensus of the chair and group.

As a group, we have not agreed on a formal process (yet). As the current chair, however, I would like participants to feel free to open PRs as they see fit, provided they accept that opening a PR doesn't mean that such PR will necessarily be approved. Opening a PR should not be subject to the group's or my own agreement. This is the same logic I've followed for https://github.com/w3c/WebID/pull/27 , which was ultimately rejected by the group but still proved quite useful for me personally as I try to figure out how to move the conversation forward in a productive manner.

/chair hat off
I'm -1 on this as it complicates validation.

Can you elaborate on "complicates validation"?
Again, this is a note, an advisory, a consideration, a lower-case may or might or could or can ... It does not require something that needs to have a test case for the purpose of confirming an implementation's conformance for what would be required for interop.

/chair hat off
@csarven insofar as a change is made WRT this topic, I would rather have the spec clearly indicate a minimal amount of triples that a profile document MUST consist of. Not only in examples but as normative content. The spec as-is doesn't mandate anything as far as the contents of the profile document and that is, to me, an issue that primarily affects validation. This note, to me, makes the current spec even less clear by making the examples less of a reference point. See discussion in #33 and #24 .

Can you elaborate on "complicates validation"?

If I may elaborate on that, @csarven, because I guess it is primarily my insistence on a mandatory predicate that got this discussion started.
With the current spec, if someone enters their WebID into an application, when the application dereferences it to its WebID Document, it faces the following problems:

The application has no way of nowing whether it actually retrieved a WebID Document, apart from the presumption that the user would not have entered some other URI.

Even if the application assumes it retreived a WebID Document, it has no way of knowing if it is actually the correct WebID Document of the user, unless it further assumes that neither the user nor the underlying technology has made a mistake (e.g. in setting up wrong redirects).

Now, (1) is nowadays conventionally solved by checking the Document for a statement indicating foaf:PersonalProfileDocument as the rdf:type of the Document's URL, and (2) is by checking for a foaf:primaryTopic statement relating the Document URL to the WebID. My suggestion was therefore to make these conventions requirements, so that applications can actually rely on them to be present.
Broadening the possible predicates to do this makes it less reliable rather than more, that's what I have been trying to tell the group the whole time. This is not about someones preferences for one vocabulary over another, as some are framing it, but about the reliability of applications.^

^ This is actually once more a perfect indication why the "web developer perspective" of @kidehen completely misses the point: hardly any developer will ever have to deal with those terms; a handful of people will write a few WebID libraries that perform those checks, and a few organisations providing WebIDs will write some code inserting those statements in every Document, and that's it. No need to hate on FOAF.

CGs operate on the principle they they:

must be fair and must not unreasonably favor or discriminate against any group participant

This PR has been merged directly into this repo and hence has received disproportionate attention, both from a technical standpoint, and a process standpoint.
It's a one of the reasons that a freeze is needed on ED WebID 1.0, and it's a use of privileges that is disruptive to the functioning of the group.
@csarven this can be easily resolved by redoing the PR from a fork of the repo.  As an experienced group member I am sure you appreciate the principle of fairness here, and a simple resolution.

[@melvincarvalho] It prevents me from adding a review in the top right section

I don't think what you're perceiving is actually what's happening.
See GitHub docs, about-pull-request-reviews --

After a pull request is opened, anyone with read access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "Reviewing proposed changes in a pull request."

There is also this --

By default, in public repositories, any user can submit reviews that approve or request changes to a pull request. Organization owners and repository admins can limit who is able to give approving pull request reviews or request changes. For more information, see "Managing pull request reviews in your organization" and "Managing pull request reviews in your repository."

I do not think that the limits described in the latter paragraph have been imposed on this repository, but if they have, then they should probably be reverted to the defaults, until and unless spammish activity warrants re-imposition of such limits..

/chair hat on
Closing this PR as it's unlikely to gather significant consensus on both technical and process grounds. This should be further discussed within existing issues or a dedicated one. Furthermore, now that we have settled on a process, please open PRs from forks rather than from within this repository (see CONTRIBUTING.md).


Add Badge for file size

Coverage remained the same at 100.0% when pulling 7756b2da4cae073dbf4da801c17ebd1aead3a053 on webcaetano:patch-1 into 90d82f88428f057c4b7a1d46aa38fc7c44d2d869 on blakeembrey:master.

I like the idea, but is there a pointer to the algorithm used for this? Is there any uptime guarantees on the service also?

@blakeembrey The information is generated live.
The server used for this is heroku. Many apps uses heroku (e.g. bower).
Never had a problem(offline, etc..) using this badge on my open-source projects.
More information behind it here: https://github.com/ngryman/badge-size

Coverage remained the same at 100.0% when pulling a7929017bfe326267d84d785f050346b8ce6bc3c on webcaetano:patch-1 into 90d82f88428f057c4b7a1d46aa38fc7c44d2d869 on blakeembrey:master.

I love the idea, but, unfortunately, I don't think I can accept the PR even though I'd love to have something like this. My main issue is that there's no control over your service and it may go offline (intentionally or not) at any time. Do you think there's any way to get it onto shields.io?

We are talking about heroku server.
Same server bower use.
https://status.heroku.com/

Never saw shields.io go offline?

It has before. I know Heroku, but it's your service. There's no guarantee you'll continue paying for it - assuming it is paid right now. If it's not, it has limited uptime. If it is, there's currently zero caching which would mean it can easy go offline if it's used somewhere you don't expect (right now all performance would be due to GitHub caching images).

To be more useful to people, I think it'd be good to generate the bundled size (e.g. Browserified) over a single file which isn't representative of the full size.

I got you point.
Its not my service. Its from an open-source project.
I also assume they use the free heroku plan.
With its not by time limit. But for usage.
The idea of kinda bagde its good.
It just need to be more solid.
I will think in a way to pass that over an shields.io badge.

https://github.com/badges/shields/issues/730

Good to know, thanks! 👍


Revert on dirty bits (unused item parameters)

The goal here is to avoid having orders which look like ERC-721 items with a single byte difference (the ItemType), i.e. a ItemType.NATIVE order ignores the token and identifier fields and so it can be used to look like a ERC-721 token (such as BAYC).

This still needs a lint run, comments, and (importantly) tests to ensure full code coverage; going to merge this in to a new branch so we can finish prep before deciding whether to merge into main!

Can you run yarn lint:fix and recommit?

I did but lint was fine on my side for some reason.


[Bug] "To the top" arrow visually button broken

Description
The "to the top" arrow button in the corner of the results page is broken visually
Reproduction
Go to /search/image?q=dogs and observe the to the top arrow button in the bottom corner.
Expectation
The arrow should be centered
Screenshots

Environment

Device: laptop
OS: macOS
Browser: Confirmed in Chrome and Firefox
Version: Evergreen

Resolution

[ ] 🙋 I would be interested in resolving this bug.

While inspecting this button, I found that when you remove the display:block, it automatically realigns itself.
If we change from display:block to display:inline it should correct itself and  vertical-align: middle doesn't work with display:block

I am using the chevron arrows from the WordPress Library. In this case, the chevron-up. The Figma file has a 24px square size version and I am using it as it is there.


Fix edge cases and refine code style.

This pull request resolves part of problems in the following areas:

Python3 compatibility.
Business error.
Logging.
Output file content.
Typo.

Hello @shishaochen! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file lomap/graphgen.py:

Line 856:80: E501 line too long (111 > 79 characters)
Line 897:13: E122 continuation line missing indentation or outdented
Line 897:80: E501 line too long (119 > 79 characters)

In the file lomap/mcs.py:

Line 1043:80: E501 line too long (98 > 79 characters)

@shishaochen thanks for the fix!

@richardjgowers With your approvement on change, when can this pull request be merged? Thanks.


⚠ ClamAV has degraded performance

In e64a7c2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 160 ms

Resolved: ClamAV performance has improved in 0ab1429.


Problem with AIRFLOW_HOME environment variable

Hi,
A user opened an issue on my docker-airflow repo https://github.com/puckel/docker-airflow/issues/6
I've checked from my side the docker part and to fix the issue with log visualization I had to replace {AIRFLOW_HOME}/logs with the complete path /usr/local/airflow/logs in airflow.cfg
Then I check deeper :
airflow@1d5b38926fc9:~$ getent passwd |grep airflow
airflow:x:1000:1000::/usr/local/airflow:/bin/bash
airflow@1d5b38926fc9:~$ env |grep HOME
HOME=/usr/local/airflow
AIRFLOW_HOME=/usr/local/airflow

When I start the worker I've a new directory created :
airflow@222b6bb890c7:~$ pwd
/usr/local/airflow

airflow@1d5b38926fc9:~$ ls
airflow.cfg  entrypoint.sh  unittests.cfg  {AIRFLOW_HOME}

airflow@1d5b38926fc9:~$ ls \{AIRFLOW_HOME\}/
logs  unittests.cfg

airflow@1d5b38926fc9:~$ ls \{AIRFLOW_HOME\}/logs/
example_bash_operator    example_http_operator    example_xcom
example_branch_operator  example_python_operator  tutorial

I ran airflow worker with strace :
 587   stat("{AIRFLOW_HOME}/logs/example_xcom/push", 0x7ffdd21d3b40) = -1 ENOENT (No such file or directory)
587   stat("{AIRFLOW_HOME}/logs/example_xcom", 0x7ffdd21d38a0) = -1 ENOENT (No such file or directory)
587   stat("{AIRFLOW_HOME}/logs", 0x7ffdd21d3600) = -1 ENOENT (No such file or directory)
587   stat("{AIRFLOW_HOME}", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
587   stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
587   open("/usr/local/airflow/{AIRFLOW_HOME}/logs/example_xcom/push/2015-01-22T00:00:00", O_WRONLY|O_CREAT|O_APPEND, 0666) = 34

My airflow.cfg is the same as https://github.com/puckel/docker-airflow/blob/master/config/airflow.cfg
I've checked also the env part of configuration.py :
>>> import os
>>> import sys
>>> print os.environ['AIRFLOW_HOME']
/usr/local/airflow

@puckel I'm wondering if the way I did it might fix it for you:  https://github.com/heroku/heroku-airflow/blob/master/airflow.cfg
I did have to pin airflow to a commit past the 1.5.1 release to get this to work.


Update README.md

Why do you think the link is worth adding on this list?
It is 3D game engine which doesn't require any programming and can be used in web designing too.It can publish cross-platform games .
Does this project has any License?
Yes, there is a free trial of 14 days and there are two licenses for this Game engine a Basic and a professional license.

Thanks @vazahat :beers:


Potential M1 support

as titled, this should build a relocatable python that is universal for use with m1 macs

My M1 device should be arriving today. I'll give this a go :D


[Bug] Failed to fetch account detail - TooManyRequests

route:
/account/TATGZXFW3OTHPZT4G4IVDD2K7PXIJJXGEVCKP72W
Error: {
 "statusCode":429,
 "errorDetails": {
   "statusCode":429,
   "statusMessage":"Too Many Requests"
 },
 "body": {
  "code":"TooManyRequests",
  "message":"You have exceeded your request rate of 7 r/s."
 }
}

@OlegMakarenko
can you try on this endpont
api-01.eu-central-1.0941-v1.symboldev.network

I have this issue with only this address, other address seem ok, maybe because the data request is less.
Error message
"body": {
  "code":"TooManyRequests",
  "message":"You have exceeded your request rate of 7 r/s."
 }

route: /account/TATGZXFW3OTHPZT4G4IVDD2K7PXIJJXGEVCKP72W
in endpont :
api-t172-01.us-west-1.0941-v1.symboldev.network - new endpoint

api-01.ap-northeast-1.0941-v1.symboldev.network - old endpoint
api-02.ap-northeast-1.0941-v1.symboldev.network - old endpoint

Only working endpoint

api-01.eu-central-1.0941-v1.symboldev.network

i also found out that after page load, if you switch the node, it will actually load all the components (also if it broke during page load)


BigQuery: Several issues caused by splitting scripts on ; characters

I can't remember exactly why we split scripts on semicolons in the original implementation, nor can I find a record of it. I think we were working around some issue.
This prevents us from using some pretty key functionality, like transactions and variables. For example:
BEGIN
  SELECT 1;
END;

and
DECLARE LOWER TIMESTAMP;

SET LOWER = (SELECT lower_limit FROM scratch.base_new_events_limits);

  -- Subset the manifest for performance.
CREATE OR REPLACE TABLE scratch.base_run_manifest
  AS(
    SELECT
      *

    FROM
      derived.base_event_id_manifest

    WHERE
      collector_tstamp >= LOWER
  );

END;

will both work perfectly fine using the BQ console, but won't work via SQL-runner.
Transactions are pretty important and variables are key to eliminating a huge amount of the complexity in our data models (table scans are not limited by subqueries but are limited by a variable that contains a query).
I would say this is fairly essential functionality & we should find a way to instrument it ASAP. Hopefully simply removing the offending line would suffice.

This also caused issues for temp UDFs. See #146 - Potential fix in that ticket too.

A small bit of experimentation jogged my memory a bit - I believe the fix here does indeed resolve it.
I had to update the BQ API to the latest version. This reminded me of why we split the script in the first place - I believe at the time there was an issue with multiple queries in a single script because the BQ go api expected each script to have a single output table. This issue was fixed here. I think we failed to pin down the true cause because that issue caused the API to report an unhelpful error message. As far as I can remember we were pressed for resource and keen to release, so we split the script.
This fix also has the happy side effect of making query errors also more informative - both because the new API reports the underlying query error, and because the reported location of the error in the script now reflects the actual position in the sql file being executed (rather than position in the portion of the split script).
@jbeemster does this make sense to you and seem sensible? Would you have any input on what tests would be required to build confidence in this change?
If you're happy with the approach I'd be keen to quickly roll out a release, as this would remove a roadblock on v1 BigQuery models. (The workarounds we've used previously are just not appropriate for a resilient model).

The above change seems to hide query failures from being returned. Would require a bit of digging to figure that out.


Feature/coveralls fuckup

maybe switching to https://codecov.io

I've been testing https://codeclimate.com/ here it works quite nicely with travis and nyc...


Rework the Iterating page

Discuss the Iterable and Iterator roles more thoroughly
Develop the examples a bit more

In general, I'd like to see these extensive revisions responding to specific issues. It might seem an improvement, but if it's not addressing specific concerns, it might be just going in some direction that might be better, or worse. Besides, it needs revision, so I'd like PRs to be more compact, also if possible. I'll check it out anyway.

Thanks for taking time to go over this PR, JJ! I figured that given the number of issues with it is better to simply close it. I'll move it to a Github gist, and once I've the time try to address all the concerns you've highlighted here. I'll ping you on irc once I've addressed enough of them.

It might seem an improvement, but if it's not addressing specific concerns, it might be just going in some direction that might be better, or worse.

The main issue I have with this page is that it makes many assumptions, which is fine if you know the ins and outs of the language. Things such as composing both Iterator and Iterable into a class, should I always compose both of them, what circumstances merit composing both of them vs just composing Iterable and providing the Iterator via another class, etc.

Thanks for understanding this. I appreciate the work you've done, anyway, and it's piecewise salvageable. Keep them coming!


Update readme of 3D Maze under SSOC 2.O

I got very frustrated when i don't see proper readme of a project, So i will update the readme in order to ease the  idea for everyone to get a glimpse of a project.
I want to update the readme of 3D Maze Project

@TusharKesarwani Kindly assign me this issue under SSOC 2.O

@TusharKesarwani Kindly assign me this under SSOC 2.O


Add fill settings to add prefixes to wrapped lines

Closes #8.
I'm pretty happy with how this turned out in the end.  It's a lot of code in an absolute sense, but it's mostly pretty modular.  The only existing function I had to make a bunch of changes to was wrapLine, but I think I was able to change it in a way that didn't make it much more complex than it already was.  Happy to address any issues or suggestions you might have.

This looks great to me. Thank you for your work on this, and thank you for also adding tests!

  And if you would be so kind as to release to Hackage when you get a chance, that would be great.  Hopefully it should be possible to use the new version of word-wrap with existing versions of brick without having to make a new release of brick as well?

This change is now released in 0.5.

(And yeah, brick has no upper bound on word-wrap and doesn't depend on knowing what fields WrapSettings has.)


Not a number error fix

Pearson correlation returns a NaN value in case of only one value to correlate. For a small mock assembly I have only one test example and therefore the correlation threw an error. This fixes the problem.

That is the correct behavior for a correlation -- it's mathematically incorrect to correlate a single value! I think it would be better to have a test assembly with 2 values


Fix lexicon validation in PWI Discover

Before
https://github.com/user-attachments/assets/917b8388-3eec-4e48-a8af-52959c308984
After
https://github.com/user-attachments/assets/97cf6d7c-16f4-4a85-ba53-7ba2f52b03d7
What?!
None of the media embeds were passing Lexicon validation in the logged out Discover because it did not go through the json-to-lex rehydration codepath, and so blobs were plain objects instead of BlobRef instances.

The fix is to make it go through the same codepath as done in normal circumstances.
I verified we're not using this hack anywhere else so this should be enough.

LGTM, nice find! Can't believe we never realised...

@mackuba noticed and opened #4959 👀

😏

Welp, guess we need to read issues more closely.


Installing twine before deploying.

See https://github.com/travis-ci/dpl/issues/299
Honestly dpl just needs to be fixed and I'd rather never submit this, but this is a fix if need be.

See #1057 as well

LGTM

@tseaver I'm just going to leave this unmerged and hope the problem resolves itself before the next release. I'm subscribed to both travis-ci/dpl#296 and travis-ci/dpl#299 so hopefully I'll hear about a resolution soon.

With the closing of travis-ci/dpl#296 and travis-ci/dpl#299 it seems this fix is no longer needed.


added solutions to first 8 problems of Project Euler from hackerrank …

…in Python
Closing Issue/Referencing Issue
issue reference (#1 )
Changes Made In Pull Request

added solutions to first 8 problems of Project Euler challenge from Hackerrank solved in Python 3
added name and details to README.md

Hi,
Can you merge this branch please.


Add integration tests to github actions

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Calibration at  midpoint is not same as at 50% duration for Polymarket

Distibutions for % market duration seems suspicious to me.
In particular AFAIU 50% and midpont should be same, but they are very different:

You are correct, this is certainly a bug. Thanks for submitting, I'll look into this soon.


Allow non-decimal values in parameters (e.g. std_const)

Also from the discussion here: https://github.com/cucapra/calyx/discussions/1356
The parser currently only allows for decimal values to be given. The best solution would be to adjust the parser to allow other constant forms (hex, binary, octal, etc) and convert those directly into u64 in the parser token generation rather than altering the IR constructs.

Seeing as this isn't really a priority for anyone, we could potentially close this. @bcarlet did you still want this ability? If not feel free to close this out

I don't think this is really needed; I'll close it.