.json endpoint may also be useful?

Returning something like that
{
  "code": 404,
  "message": "Not Found"
}

or even better, whole page to be represented as json, for example including the text description, and code references.
{
  "code": 404,
  "message": "Not Found",
  "description": "A 404 status code does not indicate whether this lack of...",
  "references": [
    "Rails HTTP Status Symbol :not_found",
    "Go HTTP Status Constant http.StatusNotFound"
  ]
}

This may be a duplicate of #36. I would like this. The references could also be an object, with
{
  "Rails HTTP Status Symbol": ":not_found",
  "Go HTTP Status Constant": "http.StatusNotFound"
}

for example. It is stored that way in the source, so might make more sense?

Thanks for the feedback! I've been intending on adding this functionality but I have been sidetracked from this project recently, I'll make time for this asap as there is more demand than I thought.
I have some questions for those interested in this functionality:

How should the description be formatted, is Markdown (how it appears in codes/410.md) minus the front matter optimal, or should it be provided in rendered HTML? Alternatively both could be provided, along with plain text. Any information on how you intend on consuming the API would help inform this decision.

The opening paragraph of each status code is emphasised on the site because the project guidelines require that the opening paragraph describe meaning, should this opening paragraph be available as its own value via the API. For example "meaning" (the opening paragraph) and "description" (the entire description) or should the consumer be responsible for any formatting?

What is the most sane approach to providing the list of status codes, should they be grouped by class (eg: /4.json) or should they be provided all together (eg: /list.json) and the consumer is responsible for retrieving which class they are interested in?

Thanks!

@Caster  The references could also be an object

Yea, I thought for this. But maybe it would be more useful keys to be just the language name for better access.
{
  "rails": ":not_found",
  "go": "http.StatusNotFound"
}

@citricsquid I like your questions. For the first one, I think that it make more sense all in the json response to be plain text and yes it make sense for separate values for meaning and description. But yea, it also be useful to have and the markdown formatted text - maybe markdown endpoint make sense?
What I'm thinking for now:
/404.json
{
  "code": 404,
  "message": "Not Found",
  "description": "A 404 status code does not indicate whether this lack of...",
  "meaning": "The origin server did not find a current representation for the target resource
or is not willing to disclose that one exists.",
  "references": {
    "rails": ":not_found",
    "go": "http.StatusNotFound",
    "node": "http.STATUS_CODES[404]"
  }
}

Also maybe make sense to add statusCode alias of code.
I'm not very sure, currently, how markdown endpoint can look like.

Ooh, and maybe type property to answer what is the kind of error: "client error", "informational" and so on.

@tunnckoCore But maybe it would be more useful keys to be just the language name (...)

Yes, I fully agree. The only reason I used the other format is that that is what is in the Markdown right now, but that could be parsed out quite easily.
I like all other points you mention. For the plain text/Markdown/HTML question: maybe one could have /404.json with plain text, /md/404.json and /html/404.json or something along those lines?
So yes, I would be in favor of having a separate endpoint for every status code. It could be useful to have one large list with all codes, possibly ordered by category. I do not see a use for having a list per category (could be extracted easily from the large list anyway), but I may overlook something.
Example format:
[
  {
    "category": "Informational",
    "id": 1,
    "codes": [100, 101, 102]
  },
  {
    "category": "Success",
    "id": 2,
    "codes": [200, 201, 202, 203, 204, 205, 206, 207, 208, 226]
  },
  {
    "category": "..."
  }
]

have /404.json with plain text, /md/404.json and /html/404.json

this not looks good, lol and not make sense. :laughing:
In addition to your example I think it also can have more advanced look, like not only the code, but code object like this for 404 for example.
[
  {
    "id": 4,
    "category": "Client Error",
    "codes": [..., {
      "code": 404,
      "message": "Not Found",
      "category": "Client Error",
      "description": "A 404 status code does not indicate whether this lack of...",
      "meaning": "The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.",
      "references": {
        "rails": ":not_found",
        "go": "http.StatusNotFound",
        "node": "http.STATUS_CODES[404]"
      }
    }]
  }
]

Maybe yours make more sense, but mine to be accessed with some query param.

Maybe I should clarify. The /404.json would contain plain text description and meaning, the /md/404.json would have Markdown-formatted description and meaning, et cetera. This could also be done with /404.json?textformat=md or something like that... I just proposed this because it can be generated statically, which matches the rest of this repository. Anything works for me.
How would you propose to do it?
The latter is of course an option, but would make for a huge response, which I personally would not like very much if you only need one or two codes. Query parameter would do it, but would of course require server-side code. Not sure if that is an option?

if you only need one or two codes

Then you request their endpoints, not the list endpoint, lol.

Maybe I should clarify. The /404.json would contain plain text description and meaning, the /md/404.json would have Markdown-formatted description and meaning, et cetera.

Haha, got it. Great idea. And it looks better than query params.

Thank you for sharing your thoughts. I'll formulate a plan over the weekend and report back here so that we can discuss further.
Something to note: because this is a static site it would be difficult to implement a parameter based API, the web server would need to be configured to use the parameters to determine which file and that adds complexity that I'm not sure is justifiable -- ideally this site is something anyone can deploy anywhere, just build and copy the files at its simplest.

I just created a fork that provides an additional JSON endpoint, f.e. to get the JSON info of the 200 OK:
GET https://httpstatuscodes.io/200.json
The known web page is still available at https://httpstatuscodes.io/200


SWDL , SWAP, CP Patch

Which patching process showed the unknown filesize error?
Please list which patching process showed the error (CP, SWAP, SWDL)
All: SWDL , SWAP, CP
What is your firmware?
Please add your firmware-train like i.e. MST2_EU_SE_ZR_P0480T
MST2_EU_SK_ZR_P0138T
Uploading support.zip…
Attach the support-dump as .zip file
Go to Tools -> Dump necessary files to SD folder /dump/.../support and zip the support folder

You did not provide support files.


Two small fixes for two small crater crashes

Hello! This is just a small one with QoL fixes for two crater-related crashes:

Quote URL in reproduction command, to help parse sources with spaces in their name
Create cache directory (~/.fontc_crater_cache) if it does not exist yet

Both can be reproduced and tested by copying the reproduction command for 'Konkhmer Sleokchher.glyphs' from the hosted fontc_crater results and running it without a ~/.fontc_crater_cache directory present :boom:
Note: this is a personal contribution independent of my employer, and so I've submitted from a fork under my personal profile and email to make this distinction

Thanks!


Add snippet to import using single quotes (as in Angular2)

Add snippet to import using single quotes (as in Angular2, angular-cli, etc) as importq, additional to import.
I see this has been debated here https://github.com/TypeStrong/atom-typescript/issues/203 and here https://github.com/TypeStrong/atom-typescript/issues/259.
Right now the checks run OK, but the snippet generates imports with only double quote characters.
Using the import snippet generates an import statement with double quote characters ("), and if the preferred quote character was ' it complains that they should be single quote characters. But currently there is no snippet to generate imports with single quote characters from the beginning.
I think this additional snippet might help keep happy both sides (single and double quote "sides").

All compiled assets are included (atom packages are git tags and hence the built files need to be a part of the source control)

Note: there were no changes to TS files.

Would it be possible to use the Preferred quote character from the settings to make sure "both sides" can use the same import snippet?

I wish it was possible, but as far as I know, it isn't.
There doesn't seem to be a way to use variables to customize snippets using the standard Atom snippets.
Here are the references I see relevant: http://flight-manual.atom.io/using-atom/sections/snippets/ and https://github.com/atom/snippets.

Nevertheless, I'm one of the "single quoters" (following Angular 2 style) and I would be OK with "having to" use the alternate import snippet (importq), actually that's what I'm doing currently with my forked version. And as there is an import snippet for double quote imports, and an importr for CommonJS imports (var myModule = require('myModule')) I wouldn't see it problematic having another "kind" of import snippet.
Also, if there are people using different code styles for different projects (e.g. Angular 2 with single quotes and NodeJS with double quotes) it could be nice to have both snippets available, otherwise it would require them changing the Preferred quote character settings each time they switch to work in each project.

SGTM 👍

Thanks for mergin @guncha !


Configure port in pimatic config

As Chris requests below. Have the option to change the port in pimatic config
would it be possible to set the port in the settings of the plugins?
i always can’t start pimatic after install/update pimatic-node-red, because i have to change the port manually…
Mit freundlichen Grüßen
Chris

Solved by #16


Clear orphan SSLs

Remove orphan SSLs directory and certificates

@athandle @cpswan - Script is almost done and working on handling for pool UUID(getting from API).

@cpswan - Please review the below PR and let me know your feedback.
https://github.com/atsign-company/secondaries-scripts/pull/43/files

@cpswan  @athandle - I have rollout script for all prod swarms and enabled cronjob.

@cpswan  can we close this?

#43 needs to be merged, and please also confirm that the code has been deployed. Once those things are done this can be closed.


Default is_published to True in Event and Proposal

As discussed in issue https://github.com/luanfonceca/speakerfight/issues/37, the default value to "is_published" of Event and Proposal should be True.

Coverage remained the same at 91.4% when pulling 55478ee1bac850e12fbd81ea323c5e59b4af9ce6 on cacarrara:default-published-to-true into 4c857e366b808f8d65131395490ece539f53da53 on luanfonceca:master.


Fingerprinting Test Fails

I did a test on firstpartysimulator.org aka PanoptiClick after dragging user.js into profile folder  but it seems like the site can still fingerprint me and get my info. I did not modify anything nor i don't have any add-ons.

you'll have to explain more: are you talking about the third party stuff, or the actual fingerprinting results


[Session - Pomodoro Focus Timer] Resume Session

Extension
https://www.raycast.com/jameslyons/session
Description
There's a pause command, but no resume. There's only start previous session, which doesn't work the same
Who will benefit from this feature?
anyone who pauses a session, then wonders how to resume the session via raycast without opening the application
Anything else?
No response

Hello! The "Pause" command also resumes sessions. I have a PR open to make that clearer in the copy.


Error messages don't report the correct type of object causing the error

Some error messages report an incorrect type of object as the cause for the error. For example, if a curve C1 has its X-values out of order the error is reported as:
Error 230: Curve has nonincreasing x-values link: C1

A code review of how all error messages are composed is needed.

This issue has been addressed in PR #360.


fix: Doc error --docker-server

Small fix, the flag --docker-registry is not a valid flag but --docker-server is.
Referring to the official Kubernetes documentation here: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-secret-by-providing-credentials-on-the-command-line

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #442 (0fe3beb) into master (f12a5ab) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #442   +/-   ##
=======================================
  Coverage   65.60%   65.60%
=======================================
  Files          21       21
  Lines        2035     2035
=======================================
  Hits         1335     1335
  Misses        571      571
  Partials      129      129

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Add support for flake8 and pylint

Summary:

Adds two new run steps, one each for flake8 and pylint.
Adds respective run_flake8 and run_pylint config options.
Adds a heavily customized .pylint config to the repo and fixes a few outstanding lint errors.
Includes unit tests and updates existing tests to pass

Test Plan:

Run ptr and it passes
Introduce lint errors
Run ptr and it fails with lint errors

Issue: #20

Updated to fix nits, but now the ptr integration builds failed, and I'm going to bed.

Wow - 3.7 fails Integration, 3.6 does not:
/home/travis/build/facebookincubator/ptr/setup.py:
************* Module ptr_tests
/home/travis/build/facebookincubator/ptr/ptr_tests.py:18:0: W0611: Unused Dict imported from typing (unused-import)
/home/travis/build/facebookincubator/ptr/ptr_tests.py:18:0: W0611: Unused List imported from typing (unused-import)

Did this not fail locally too?

I tested locally on 3.6, just haven't had time to try it with 3.7 and see what's what.  Not sure why pylint would complain about it on one version and not another...


Runs the js-sdk image build workflow only if Dockerfile changed

Description
Runs the js-sdk image build workflows only if Dockerfile changed
Changes
these workflows will run only if Dockerfile change instead of running on every push to development:

.github/workflows/build_image_with_trc.yml
.github/workflows/build_image.yml
.github/workflows/build_vdc_image.yml

Related Issues
List of related issues
Checklist

[ ] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

What if it depends on other files that can be changed?

as  discussed

this will keep all of the images outdated.


Open HLS (m3u8) url

I could not succeed to open an m3u8 url with this library. Is it ever possible?
The following URL opens fine with video_player on iOS and Android but not on MacOS with this library.
https://live1pop03.kablowebtv.com/Live/HLS/1022/1022.m3u8

The following url works fine on MacOS, Android and iOS:
https://bitdash-a.akamaihd.net/content/sintel/hls/playlist.m3u8
Do you have any idea about how to fix this?

@postacik we do video transcoder and content checks on all our user generated content and convert them to standard MP4's so we have no need for that format.
You'd need to make a pull request to fix it :-)
If you're not doing transcoder and adult checks you are playing a risky game 😎

@ollyde I'm totally confused by your answer.
The following url is playing fine on MacOS with this package:
https://bitdash-a.akamaihd.net/content/sintel/hls/playlist.m3u8
However the following one is not playing at all:
https://live1pop03.kablowebtv.com/Live/HLS/1022/1022.m3u8
The second one is playing fine with video_player package on iOS.
This package is also using AVPlayer as video_player does on iOS.
I'm just trying to figure out what I can do to make the second url play on MacOS with this package.
When I open the MacOS project with Xcode, I see the following error in the log:
Query fired: did not receive all answers in time for live1pop03.kablowebtv.com:443
I hope, my question is clearer now.


expose livecrawl and liveCrawlTimeout from beta

There were some typing errors; I fixed them and simplified the code.
I removed some logic that seemed redundant, was it necessary @eugenechantk ?


As guest and host, I see the recipe suggestion of the API including the list of ingredients which will be brought by friends, in order to have a good overview.

Acceptance Criteria

[ ] There is only one recipe suggestion displayed
[ ] There is a button which will bring the user back to the Landing Page

Development Tasks
Backend:

[ ] sopra-fs23-group-03/sopra-fs23-group-03-server#57
[ ] sopra-fs23-group-03/sopra-fs23-group-03-server#58
[ ] sopra-fs23-group-03/sopra-fs23-group-03-server#59

Frontend:

[x] sopra-fs23-group-03/sopra-fs23-group-03-client#16
[ ] sopra-fs23-group-03/sopra-fs23-group-03-client#17
[x] sopra-fs23-group-03/sopra-fs23-group-03-client#18

Notes

In case the API offers more suggestions, only one recipe suggestion will be chosen randomly
A list will show which guest will bring which ingredient
A user can return to the LANDING PAGE again

Changed user story, bc we cannot map the ingredients used in the API back to the members. E.g. a user is providing pasta and in the recipe its "nidi capellini nest" which is used. Also a form of pasta, but not be able to map it back without e.g. a ML model


[OOM]Offset map reached to 75% pc-broker-poll thread would keep polling records lead to OOM

Hi team,
from pc_metadata_space_used metric we can see after 17:38 framework stop encoding

and we can see the log:
io.confluent.parallelconsumer.state.PartitionState couldBeTakenAsWork 649 PartitionState.java - Not allowed more records for the partition (XXX) as set from previous encode run (blocked), that this record (571268) belongs to, due to offset encoding back pressure, is within the encoded payload already (offset lower than highest succeeded, not in flight (true), continuing on to next container in shardEntry.
But pc-broker-poll poll records all the time( from the below kafka_consumer_fetch_manager_bytes_consumed_rate metrics) :

and from pc_waiting_records metrics we can see waiting records keep increasing.

And service threw OOM at the end
And I have two concerns now:

pc_waiting_records metric values are negative, Is that normal?
when offset map reached to 75% and not allowed more records been processed, would pc-broker-poll thread keep polling records bring any memory issues?

BRs,
Dumont

@rkolesnev
back pressure logic is worked. It is indeed pausing the processing of records now, but the pausing of polling is not worked. It keeps polling records and causes OOM.
configuration：
ordering=KEY
maxConcurrency=14
commitmode=PERIODIC_CONSUMER_SYNC
No other parameters are explicitly specified.
scenario:
My test scenario is a scenario where 50% of records fail, and if it fails, it will keep retrying until it succeeds (in fact, it will never succeed, just keep retrying). At this time, the CPU is almost 100%.
So it is high load,high number of retries.
BRs,
Dumont

@dumontxiong - the backpressure logic is exactly the logic that controls the polling for records - so there must be an issue in there - potentially caused by something being off with the calculation of retries (given that your scenario seems to be with high number or retries). It is separate from accepting work into worker threads based on metadata size usage.
Can you provide a reproduction code for this? either as a small application or integration test?

@rkolesnev
Here's  two. Scheduled tasks,
one is publish records to topic1 with random key(half with THROW_EXCEPTION_FLAG header),
one is publish records to topic2 with key 0 - 999 (half with THROW_EXCEPTION_FLAG header),
`@Scheduled(fixedRate = 2, timeUnit = TimeUnit.MINUTES)
public void publishEventsNoKey() {
for (int i = 0; i < 1000; i++) {
kafkaEvent.setHeader(THROW_EXCEPTION_FLAG, i%2);
publisher.publish(kafkaEvent);
}
}
@Scheduled(fixedRate = 2, timeUnit = TimeUnit.MINUTES)
public void publishEventsOneThousandKey() {
	for (int i = 0; i < 1000; i++) {
                  kafkaEvent.setKey(i);
                  kafkaEvent.setHeader(THROW_EXCEPTION_FLAG, i%2);
	     publisher.publish(kafkaEvent);
	}
}`

Here's  two. subscriber , one is subscribed to topic1 the other is  subscribed to  topic2,and both of them concurrency = 14
           ParallelConsumerOptions.ParallelConsumerOptionsBuilder<KafkaEventKey, T> builder =              ParallelConsumerOptions.builder().ordering(ProcessingOrder.KEY).maxConcurrency(14).consumer(this.consumer);             ParallelConsumerOptions options = builder.build();             this.parallelStreamProcessor = ParallelStreamProcessor.createEosStreamProcessor(options);            this.parallelStreamProcessor.subscribe("topic1);             this.parallelStreamProcessor.poll((context) -> {                 try {       Thread.sleep(100);     } catch (InterruptedException e) {      //     }     if (kafkaevent.getHeader(THROW_EXCEPTION_FLAG) != null && event.getMeta(THROW_EXCEPTION_FLAG, Integer.class) == 0){       throw new RuntimeException("THROW_EXCEPTION_FLAG_HAPPENED");     }             });
           ParallelConsumerOptions.ParallelConsumerOptionsBuilder<KafkaEventKey, T> builder =              ParallelConsumerOptions.builder().ordering(ProcessingOrder.KEY).maxConcurrency(14).consumer(this.consumer);             ParallelConsumerOptions options = builder.build();             this.parallelStreamProcessor = ParallelStreamProcessor.createEosStreamProcessor(options);            this.parallelStreamProcessor.subscribe("topic2);             this.parallelStreamProcessor.poll((context) -> {                 try {       Thread.sleep(100);     } catch (InterruptedException e) {      //     }     if (kafkaevent.getHeader(THROW_EXCEPTION_FLAG) != null && event.getMeta(THROW_EXCEPTION_FLAG, Integer.class) == 0){       throw new RuntimeException("THROW_EXCEPTION_FLAG_HAPPENED");     }             });

Thank you for the repro code - will run and see if i can reproduce / see where the issue occurs.

Is the CommitMode set to PERIODIC_CONSUMER_SYNC in the example code above - or its left as default (PERIODIC_CONSUMER_ASYNCHRONOUS)?
You mentioned above that you are using PERIODIC_CONSUMER_SYNC in your tests - but in the example code it doesnt seem to be specified...

In addition - those events that have the THROW_EXCEPTION_FLAG - are they set to throw exception always? i.e. retried indefinitely and always fail due to throwing exception or they only throw exception first time - but are not failing on retry?
Its not 100% clear what this block does as those objects are not in the code sample provided:
(kafkaevent.getHeader(THROW_EXCEPTION_FLAG) != null && event.getMeta(THROW_EXCEPTION_FLAG, Integer.class) == 0)

recreated issue.
it is due to #817.

Is the CommitMode set to PERIODIC_CONSUMER_SYNC in the example code above - or its left as default (PERIODIC_CONSUMER_ASYNCHRONOUS)? You mentioned above that you are using PERIODIC_CONSUMER_SYNC in your tests - but in the example code it doesnt seem to be specified...

sorry for miss this one
.commitMode(PERIODIC_CONSUMER_SYNC);

In addition - those events that have the THROW_EXCEPTION_FLAG - are they set to throw exception always? i.e. retried indefinitely and always fail due to throwing exception or they only throw exception first time - but are not failing on retry? Its not 100% clear what this block does as those objects are not in the code sample provided:
(kafkaevent.getHeader(THROW_EXCEPTION_FLAG) != null && event.getMeta(THROW_EXCEPTION_FLAG, Integer.class) == 0)

throw exception would always fail


[Feature]: Feedback drawer

Contact Details
No response
Description
Implement a simple drawer where users can provide feedback and ask questions on the site
Link to figma / design node
No response
Link to other planning document
No response
Anything else?
No response

Duplicate of #436


firefox-wrapper: remove dead npapi plugin code

Motivation for this change
Support for npapi plugins (except for flash) was dropped from firefox some time ago. None of the versions in nixpkgs actually supports them.
So remove support for them from the wrapper.
Things done

Verified that the hash does not change when building with default options
Tested that building with one of the removed nixpkgs options throws an error as expected

Most of the plugins in pkgs/applications/networking/browsers/mozilla-plugins/ can probably be removed as well. Not sure if something else is still using them though.

After looking through pkgs/applications/networking/browsers/mozilla-plugins/ and some use of grep, I am fairly sure that everything there except for the flashplayer is unused in nixpkgs. Should I add a commit to this pr for removing them, or over a new pr for that?

IMHO add it to this PR.

Sorry, I missed this PR before. It would have been great if the throw could have been a warn for some period of time to avoid hard breaking of existing configurations.

Sorry, I missed this PR before. It would have been great if the throw could have been a warn for some period of time to avoid hard breaking of existing configurations.

You think its worth changing that still?

I think it should be fine to keep the throw unless more complaints arise. I've removed the options from HM so people's configurations should now build OK again. But for future changes like this it would good to have a grace period during which a warning is printed instead of immediately going for a hard error.


[Documentation][Spec Decode] Add documentation about lossless guarantees in Speculative Decoding in vLLM

Add documentation about lossless guarantees in Speculative Decoding in vLLM. The documentation documents the finding in this issue here #7627

/ready


Make queries account based rather than hgp based

What is the expected enhancement?
Related to #107, queries, such as backends() and jobs(), should be account based rather than hgp based, with optional hgp filters.

backends() and jobs() are both already account level


Users call activity

This feature will return high level call statistics for all users in a single group. The data will then be outputted to a CSV file so the data is more human friendly.

Requirements

Can we specify if internal or external
Have the UserId in the columns
How much history can we capture? 1, 3, 6, 12 months


Installation instructions are wrong?

running  npm install --save-dev graphql @graphql-codegen/cli does not place any graphql-codegen comand in $PATH, Are the instructions correct?

@marcosfede Like any other Node library, you have to either run it with NPM scripts (create a script under scripts section of package.json, then run the script with npm run myscript), or, use npx, or use Yarn (yarn graphql-codegen)

@dotansimha I forgot to mention that I've tried that already. neither writing a script in package.json nor  running with npx is working. I've just tried using yarn and it works with no problems, so I think its not working correctly with npm

@marcosfede can you please share a reproduction of the issue in a repo? Which OS, Node and NPM do you use?


added function to convert seconds to week

Why:
To convert seconds to week

Yes (link)[https://github.com/codinasion/program/issues/3640]

3640

Closes #ISSUE_NUMBER
What's being changed:

@akp111
The issue is assigned to someone else. Please look for other issues to contribute. Make sure you type !assign to grab the issue
Thank you!


FancyZones does not recognize multiple monitors

Microsoft PowerToys version
0.35.0
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Launched layout editor to set up zones
✔ Expected Behavior
Three separate monitors to switch between to set up individual layouts on all three monitors
❌ Actual Behavior
FancyZones appears to recognize all three monitors as a single monitor
Other Software
No response

Do you have "Allow zones to span across monitors" enabled in settings?  If so that will is what allows us to have zones that can be between monitors.


integrate in php

I am new to js. Can I have a steps to integrate email-builder in my php project.
Facing below issue

Unfortunately, we don't have any experience with php so we are unable to help here. If you end up using Node, you can look at our self-hosting instructions here: https://github.com/usewaypoint/email-builder-js?tab=readme-ov-file#self-hosting-the-editor

Okay thank you. But, I need some developer documentation. i.e., hiding left navigation bar(template area). Hiding some top options (like, download JSON file, Import JSON). Where can I find this details. I could not see any documents in the github. Could you please share the details


no autostart for CT after OOM

latest LXD from snap (latest/stable:    4.18        2021-09-13 (21497))
[Sun Sep 19 20:44:49 2021] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=lxc.payload.c2035,mems_allowed=0,oom_memcg=/lxc.payload.c2035,task_memcg=/lxc.payload.c2035,task=init,pid=4496,uid=0
[Sun Sep 19 20:44:49 2021] Memory cgroup out of memory: Killed process 4496 (init) total-vm:33260kB, anon-rss:1124kB, file-rss:8kB, shmem-rss:0kB, UID:0 pgtables:104kB oom_score_adj:0
[Sun Sep 19 20:44:49 2021] oom_reaper: reaped process 4496 (init), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

Usually init is not killed by oom but in this case it happened and container was not started after it was killed. And this is definitely bad.
Is it possible to configure LXD to start containers in such case?
If not, is it possible to implement?
boot.autostart: "true" for this container.

As far as LXD is concerned, init exited and so the container is stopped.
LXD will restart the container only if the container asks the kernel for it.
boot.autostart is used to control what containers should be brought back up after a host system restart.
As it stands, LXD cannot differentiate a container being stopped by init exiting normally to one exiting because of the kernel killing the init process so there isn't anything we can do at this level yet.
@brauner would it be worth adding something to liblxc so that the post stop hooks can differentiate normal exit of init from a kill? If we can get something like that in liblxc then it'd unblock basic restart policies on crashes in LXD.

@brauner ping

As far as LXD is concerned, init exited and so the container is stopped.
LXD will restart the container only if the container asks the kernel for it.
boot.autostart is used to control what containers should be brought back up after a host system restart.
As it stands, LXD cannot differentiate a container being stopped by init exiting normally to one exiting because of the kernel killing the init process so there isn't anything we can do at this level yet.
@brauner would it be worth adding something to liblxc so that the post stop hooks can differentiate normal exit of init from a kill? If we can get something like that in liblxc then it'd unblock basic restart policies on crashes in LXD.

We do current expose the exist status in the common shell format
 *   0-126       exit code of the application
 *   128+n       signal n received by the application
 *   255         lxc error

already in the error_num member of the container.
I don't think exposing information in the post-stop or on-stop hook environment is the way to go for this. We would need to come up with an easy digestible and parseable format so that hooks could consume exit information in the environment. That's not impossible but I would go that route only if the hook really needs that information.
What I'd rather suggest we do is that we add a new struct exit_status in struct lxccontainer that not just contains the standard information such as the status, the exit number, the signal number, if the signal was sent by the kernel or by another process, which process etc. etc. but also additional information such as whether the container was killed by the oom killer or not. The struct itself doesn't need to be accessed we can add read-only getters to retrieve the relevant pieces of information. So when onStop() runs in LXD and it detects a container exit it can call the API method and consume the information it needs to determine whether a given restart policy applies or not.

Not sure how that would work though as onStop runs inside of LXD and not from the process which spawned the container, so it does not have access to the struct.
onStop is effectively called through a LXC hook which is why I was asking about post-stop or similar hooks having that be exposed to them.

Not sure how that would work though as onStop runs inside of LXD and not from the process which spawned the container, so it does not have access to the struct.

As usual we'd expose it through the command socket.

onStop is effectively called through a LXC hook which is why I was asking about post-stop or similar hooks having that be exposed to them.

Ok, that should be fine. We'll need to bump our minimal LXC version a bit though as we currently say 3.0 or higher but only 4.0 allows for access to the monitor from within a hook context. Prior releases have a blocking single threaded mainloop and so when a hook is running, it's impossible to do anything over the command socket.


Difference between Dividers.

There is something wrong between Divider and VerticalDivider.
color and thickness is not working same.
Exampla Code:

Column(
children:[
SizedBox(
height: 250,
child: VerticalDivider(color: Colors.blue))),
SizedBox(width:150,child: Divider(color: Colors.blue, thickness: `0.3))])`

``

I just checked and they working fine. Check your flutter version if you are using stable version or not.
`class DividerExample extends StatelessWidget {
const DividerExample({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
return Scaffold(
body: Column(children: const [
SizedBox(
height: 250,
child: VerticalDivider(
color: Colors.red,
thickness: 2,
)),
SizedBox(width: 150, child: Divider(color: Colors.red, thickness: 2))
]));
}
}`

I just checked and they working fine. Check your flutter version if you are using stable version or not.
```
       class DividerExample extends StatelessWidget {
  const DividerExample({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        body: Column(children: const [
      SizedBox(
          height: 250,
          child: VerticalDivider(
            color: Colors.red,
            thickness: 2,
          )),
      SizedBox(width: 150, child: Divider(color: Colors.red, thickness: 2))
    ]));
  }
}

```

@aliaktas-tr Which Flutter version are you using? Please try on the latest version (stable 3.3.10 and master 3.7.0) with @IsmailAbdirahman's sample code as suggested above.


nats msgs in - msgs out is not converging to zero

The delta between in and out looks like a constant:
$ docker run --rm --network=ampnet appcelerator/alpine:3.5.2 curl -s "http://nats:8222/varz" | jq '.in_msgs - .out_msgs'
8176

and the rate on this cluster is low at that moment (2 msgs in per mn, 2 msgs out per mn).

I ran the following investigation:
$ amp cluster create

Then checked the dashboard:

$ docker run --rm --network ampnet appcelerator/alpine curl -s http://nats:8222/connz | jq
{
  "now": "2017-07-07T21:04:50.746220128Z",
  "num_connections": 4,
  "total": 4,
  "offset": 0,
  "limit": 1024,
  "connections": [
    {
      "cid": 1,
      "ip": "<IP_ADDRESS>",
      "port": 40842,
      "start": "2017-07-07T20:52:52.790759518Z",
      "last_activity": "2017-07-07T21:04:49.993457439Z",
      "uptime": "11m57s",
      "idle": "0s",
      "pending_bytes": 0,
      "in_msgs": 3992,
      "out_msgs": 0,
      "in_bytes": 1552217,
      "out_bytes": 0,
      "subscriptions": 0,
      "name": "_NSS-test-cluster-send",
      "lang": "go",
      "version": "1.3.0"
    },
    {
      "cid": 2,
      "ip": "<IP_ADDRESS>",
      "port": 40844,
      "start": "2017-07-07T20:52:52.791551191Z",
      "last_activity": "2017-07-07T21:04:49.993705847Z",
      "uptime": "11m57s",
      "idle": "0s",
      "pending_bytes": 0,
      "in_msgs": 48,
      "out_msgs": 4039,
      "in_bytes": 403,
      "out_bytes": 1595327,
      "subscriptions": 9,
      "name": "_NSS-test-cluster-general",
      "lang": "go",
      "version": "1.3.0"
    },
    {
      "cid": 3,
      "ip": "<IP_ADDRESS>",
      "port": 48944,
      "start": "2017-07-07T20:52:57.440237223Z",
      "last_activity": "2017-07-07T21:04:49.993705847Z",
      "uptime": "11m53s",
      "idle": "0s",
      "pending_bytes": 0,
      "in_msgs": 2021,
      "out_msgs": 2021,
      "in_bytes": 28902,
      "out_bytes": 1504516,
      "subscriptions": 4,
      "lang": "go",
      "version": "1.2.2"
    },
    {
      "cid": 4,
      "ip": "<IP_ADDRESS>",
      "port": 52032,
      "start": "2017-07-07T20:53:30.317165355Z",
      "last_activity": "2017-07-07T21:04:49.993457439Z",
      "uptime": "11m20s",
      "idle": "0s",
      "pending_bytes": 0,
      "in_msgs": 2018,
      "out_msgs": 2018,
      "in_bytes": 1566425,
      "out_bytes": 48059,
      "subscriptions": 2,
      "lang": "go",
      "version": "1.2.2"
    }
  ]
}
$ docker run --rm --network ampnet appcelerator/alpine nslookup <IP_ADDRESS>
nslookup: can't resolve '(null)': Name does not resolve

Name:      <IP_ADDRESS>
Address 1: <IP_ADDRESS> amp_ampbeat.1.2la9552opslr8j74mfvx2w61i.ampnet
$ docker run --rm --network ampnet appcelerator/alpine nslookup <IP_ADDRESS>
nslookup: can't resolve '(null)': Name does not resolve

Name:      <IP_ADDRESS>
Address 1: <IP_ADDRESS> amp_agent.9phz9q1y90bph58q2a6ewqldi.d2v0jgo3ysdi18eyemtlajylv.ampnet

We can see there are 4 connections:

2 of them are coming from <IP_ADDRESS>, which is nats-streaming connected to nats which have
1 connection from ampbeat
1 connection from agent

The 2 connections coming from amp services have the same number of incoming and outgoing messages:

ampbeat:

      "in_msgs": 2021,
      "out_msgs": 2021,

agent:

      "in_msgs": 2018,
      "out_msgs": 2018,

The 2 connections from nats-streaming have the following:
      "in_msgs": 3992,
      "out_msgs": 0,
      "in_msgs": 48,
      "out_msgs": 4039,

Once summed up, it gives:
      "in_msgs": 4040,
      "out_msgs": 4039,

So it seems that the off by one message error comes from nats streaming itself.

thanks for the analysis @bquenin .
It's may not even be an internal error, these 2 connections are respectively responsible of Send/Publish and Request/Subscribe between the streaming server and nats. We may not have to expect to have an equal number of requests.
We should check if we're able to filter out these two connections from the metrics so that our stats reflects our real usage of the service.

@ndegory agreed. There is a way to filter out the first 2 connections using this query:
docker run --rm --network ampnet appcelerator/alpine curl -s http://nats:8222/connz\?offset\=2 | jq
{
  "now": "2017-07-07T21:47:34.05422077Z",
  "num_connections": 3,
  "total": 5,
  "offset": 2,
  "limit": 1024,
  "connections": [
    {
      "cid": 3,
      "ip": "<IP_ADDRESS>",
      "port": 57466,
      "start": "2017-07-07T21:25:10.798226683Z",
      "last_activity": "2017-07-07T21:47:25.275560173Z",
      "uptime": "22m23s",
      "idle": "8s",
      "pending_bytes": 0,
      "in_msgs": 3134,
      "out_msgs": 3134,
      "in_bytes": 44133,
      "out_bytes": 6176943,
      "subscriptions": 4,
      "lang": "go",
      "version": "1.2.2"
    },
    {
      "cid": 4,
      "ip": "<IP_ADDRESS>",
      "port": 50130,
      "start": "2017-07-07T21:25:49.470395253Z",
      "last_activity": "2017-07-07T21:47:25.275311852Z",
      "uptime": "21m44s",
      "idle": "8s",
      "pending_bytes": 0,
      "in_msgs": 3089,
      "out_msgs": 3089,
      "in_bytes": 2558374,
      "out_bytes": 73259,
      "subscriptions": 2,
      "lang": "go",
      "version": "1.2.2"
    },
    {
      "cid": 6,
      "ip": "<IP_ADDRESS>",
      "port": 42226,
      "start": "2017-07-07T21:33:35.264929317Z",
      "last_activity": "2017-07-07T21:47:05.287692957Z",
      "uptime": "13m58s",
      "idle": "28s",
      "pending_bytes": 0,
      "in_msgs": 85,
      "out_msgs": 366,
      "in_bytes": 1777,
      "out_bytes": 16826275,
      "subscriptions": 2,
      "lang": "go",
      "version": "1.2.2"
    }
  ]
}

However, I'm not sure how to configure the nats exporter accordingly ...

not a bug


Southbear/dw 5/modal to sign message

Description
@southbears creating a PR for you to fill out until permissions are sorted.
Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

This is what it looks like in product:

Closing to @southbears can open their own.


Change Schedule Inflation to be More Forgiving

Change
This is a minor PR fix to allow valid appointments to be loaded even if there exists some invalid appointments in the data file. Test cases were updated to reflect this change.
Related Issues

Closes #195

Codecov Report

Merging #202 (6ca0730) into master (51999fa) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #202      +/-   ##
============================================
- Coverage     72.63%   72.56%   -0.08%
- Complexity      997      998       +1
============================================
  Files           137      137
  Lines          3062     3065       +3
  Branches        350      350
============================================
  Hits           2224     2224
- Misses          775      778       +3
  Partials         63       63

Impacted Files
Coverage Δ

...seedu/contax/storage/JsonSerializableSchedule.java
100.00% <100.00%> (ø)

...java/seedu/contax/storage/JsonScheduleStorage.java
86.95% <0.00%> (-13.05%)
:arrow_down:

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 51999fa...6ca0730. Read the comment docs.


Add .deb publishing

Publishing automated .tar.gz files for consumption by a custom shell script is useful, but really, it would be even nicer to have a few .deb channels for this:
experimental or snapshots
Corresponds to the current content at https://builds.perlang.org/; built automatically for each commit to the master branch. As the project grows and the number of commits per day potentially make this unfeasible, this could be switched to a nightly release cadence instead. For now, this works perfectly fine.
Challenge: How do we generate the Debian changelog for this? Should we create a changelog based on the latest stable/testing version and just auto-generate a new entry for the snapshots version? Or should we somehow fetch the latest snapshot changelog and add an entry to it (this becomes much more complex)?
testing
Corresponds to the currently released versions at https://github.com/perlang-org/perlang/releases. Released every now and then, but much more seldom than the snapshots. This is the version you'd typically use a non-development machine, where you just want something that "works" and typically don't have any grave, major bugs present.
Where do we host it?
This is a good question. Regretfully, it might be easiest that we just host it on our own infra for now, even though it would be nice to have this on something like GitHub Packages. Unfortunately, it doesn't support support .deb packages currently. :neutral_face: We could look into other options also. Just putting it on our own infra works, it's just one more service to be responsible for ourselves... so if there was a shared "public transport" for this, it would be really nice to just "take the train" in this case instead of having to "drive your own car". :thinking: Worth considering.
Webpage instructions
Once this is in place, we should make sure to update the https://perlang.org/download/ page to make mention of the .deb package hosting. We'll still keep the .tar.gz files for sure; they are useful to non-Debian users. (I consider Ubuntu, Mint and other users to be Debian users here, since they are essentially part of the Debian ecosystem in a broader sense)

Where do we host it?
This is a good question. Regretfully, it might be easiest that we just host it on our own infra for now, even though it would be nice to have this on something like GitHub Packages. Unfortunately, it doesn't support support .deb packages currently. 😐

If/when we switch to GitLab, we could hopefully use its .deb repository support, with the caveat that it's not fully ready yet.


Add Ruby 2.5 testing to Travis

Time to get started
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

i believe there are real test failures on 2.5.0 although they're masked by the wonky travis stuff

The integration test failures are certainly legit


Add PDF links for the ICDE 2024 workshop paper and the SIGMOD 2024 demo paper

Add a published link for the publication "Data Science Tasks Implemented with Scripts versus GUI-Based Workflows: The Good, the Bad, and the Ugly".
Add a published link for the publication "Demonstration of Udon: Line-by-line Debugging of User-Defined Functions in Data Workflows".

Approved.


Building netCDF with HDF5 1.12.0 vs 1.10.6

Hello,
I've been building netCDF with HDF5 (v1.10.6) for a while but decided to upgrade to v1.12.0 for no particular reason other than simply having a more recent version. The compilations of HDF5 for both versions are with autotools and include the flag --with-zlib. However, the new compilation (from source) of netCDF (with cmake) returns the error:
...
-- Found HDF5: /opt/hdf5/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so (found version "1.12.0") found components: C HL
-- Found HDF5 libraries version 1.12.0
-- Using HDF5 include dir: /opt/hdf5/include
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Looking for H5Pget_fapl_mpio in hdf5
-- Looking for H5Pget_fapl_mpio in hdf5 - not found
-- Looking for H5Pset_all_coll_metadata_ops in hdf5
-- Looking for H5Pset_all_coll_metadata_ops in hdf5 - not found
-- Looking for H5Z_SZIP in hdf5
-- Looking for H5Z_SZIP in hdf5 - not found
-- Looking for H5Pset_libver_bounds in hdf5
-- Looking for H5Pset_libver_bounds in hdf5 - not found
-- Looking for H5free_memory in hdf5
-- Looking for H5free_memory in hdf5 - not found
-- Looking for H5allocate_memory in hdf5
-- Looking for H5allocate_memory in hdf5 - not found
-- Looking for H5resize_memory in hdf5
-- Looking for H5resize_memory in hdf5 - not found
-- Looking for H5Dread_chunk in hdf5
-- Looking for H5Dread_chunk in hdf5 - not found
-- Performing Test HAVE_HDF5_ZLIB
-- Performing Test HAVE_HDF5_ZLIB - Failed
CMake Error at CMakeLists.txt:778 (MESSAGE):
  HDF5 was built without zlib.  Rebuild HDF5 with zlib.

I have cleaned up and recompiled, but it always spits out the same error. Other than the HDF5 libraries having different numbers, I haven't noticed any outstanding difference. Thanks.

Which version of netcdf-c are you building? I'm trying to duplicate this issue.  Also, can you provide the libhdf5.settings file generated for your hdf5 1.12.0 build?

I just cloned it from the Github repository. The HDF5 info reads:
            SUMMARY OF THE HDF5 CONFIGURATION
            =================================

General Information:
-------------------
                   HDF5 Version: 1.12.0
                  Configured on: Tue Aug 11 20:39:39 UTC 2020
                  Configured by: ubuntu@instance-20200811-1633
                    Host system: x86_64-unknown-linux-gnu
              Uname information: Linux instance-20200811-1633 5.4.0-1021-oracle #21-Ubuntu SMP Fri Jul 10 06:33:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
                       Byte sex: little-endian
             Installation point: /opt/hdf5

Compiling Options:
------------------
                     Build Mode: debug
              Debugging Symbols: yes
                        Asserts: yes
                      Profiling: no
             Optimization Level: debug

Linking Options:
----------------
                      Libraries: static, shared
  Statically Linked Executables:
                        LDFLAGS:
                     H5_LDFLAGS:
                     AM_LDFLAGS:
                Extra libraries: -lz -ldl -lm
                       Archiver: ar
                       AR_FLAGS: cr
                         Ranlib: ranlib

Languages:
----------
                              C: yes
                     C Compiler: /usr/bin/gcc
                       CPPFLAGS:
                    H5_CPPFLAGS: -D_GNU_SOURCE -D_POSIX_C_SOURCE=200809L   -UNDEBUG -DH5AC_DEBUG -DH5B2_DEBUG -DH5CX_DEBUG -DH5D_DEBUG -DH5F_DEBUG -DH5HL_DEBUG -DH5I_DEBUG -DH5O_DEBUG -DH5S_DEBUG -DH5ST_DEBUG -DH5T_DEBUG -DH5Z_DEBUG -DH5_DEBUG_API
                    AM_CPPFLAGS:
                        C Flags:
                     H5 C Flags:  -std=c99  -Wall -Wcast-qual -Wconversion -Wextra -Wfloat-equal -Wformat=2 -Winit-self -Winvalid-pch -Wmissing-include-dirs -Wno-c++-compat -Wno-format-nonliteral -Wshadow -Wundef -Wwrite-strings -pedantic -Wbad-function-cast -Wcast-align -Wdeclaration-after-statement -Wdisabled-optimization -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpacked -Wredundant-decls -Wstrict-prototypes -Wswitch-enum -Wswitch-default -Wunused-macros -Wunsafe-loop-optimizations -Wlogical-op -Wlarger-than=2560 -Wsync-nand -Wframe-larger-than=16384 -Wpacked-bitfield-compat -Wstrict-overflow=5 -Wjump-misses-init -Wunsuffixed-float-constants -Wdouble-promotion -Wtrampolines -Wstack-usage=8192 -Wvector-operation-performance -Wdate-time -Warray-bounds=2 -Wc99-c11-compat -Wnull-dereference -Wunused-const-variable -Wduplicated-cond -Whsa -Wnormalized -Walloc-zero -Walloca -Wduplicated-branches -Wformat-overflow=2 -Wformat-truncation=2 -Wimplicit-fallthrough=5 -Wrestrict -Wattribute-alias -Wcast-align=strict -Wshift-overflow=2 -Wattribute-alias=2 -Wmissing-profile -ftrapv -fno-common -g -fno-omit-frame-pointer -Wno-aggregate-return -Wno-inline -Wno-missing-format-attribute -Wno-missing-noreturn -Wno-suggest-attribute=const -Wno-suggest-attribute=pure -Wno-suggest-attribute=noreturn -Wno-suggest-attribute=format -Wno-suggest-attribute=cold -Wno-suggest-attribute=malloc -Og
                     AM C Flags:
               Shared C Library: yes
               Static C Library: yes

                        Fortran: no

                            C++: no

                           Java: no

Features:
---------
                   Parallel HDF5: no
Parallel Filtered Dataset Writes: no
              Large Parallel I/O: no
              High-level library: yes
                Build HDF5 Tests: yes
                Build HDF5 Tools: yes
                    Threadsafety: no
             Default API mapping: v112
  With deprecated public symbols: yes
          I/O filters (external): deflate(zlib)
                             MPE: no
                   Map (H5M) API: no
                      Direct VFD: no
              (Read-Only) S3 VFD: no
            (Read-Only) HDFS VFD: no
                         dmalloc: no
  Packages w/ extra debug output: AC,B2,CX,D,F,HL,I,O,S,ST,T,Z
                     API tracing: yes
            Using memory checker: no
 Memory allocation sanity checks: yes
          Function stack tracing: no
       Strict file format checks: yes
    Optimization instrumentation: no

Were you able to reproduce the issue?

I was and am investigating now; sorry for the delayed response!

BTW I am building routinely with 1.12.0 in my CI, with no apparent problems.
On Fri, Aug 28, 2020 at 4:10 PM Ward Fisher<EMAIL_ADDRESS>wrote:

I was and am investigating now; sorry for the delayed response!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/issues/1806#issuecomment-683167709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCSXXBHRVYTMRD3W7SHSG3SDATNDANCNFSM4P3OYTKQ
.

I built the system with HDF5 1.10.6 (as I mentioned upgrading to 1.12.0 was a very minor thing). I will try again sometime in the future but maybe this was an isolated glitch.

Possibly this issue should be closed. I just checked and can confirm that hdf5-1.12.0 is running on all my branches and has been for some time, and has never failed where 1.10.6 has passed.

Agreed, I thought I had duplicated this but realized I had conflated it with a different HDF5 issue I had recreated.  @afernandezody, if you can recreate this when you try again in the future, feel free to comment and/or reopen the issue. Thanks all!


[fix] GovBanner typescript warning

ReactUSWDS Version & USWDS Version:
from app package.json
"react": "^17.0.1"
"typescript": "^4.0.3",
"@trussworks/react-uswds": "^1.10.0",
"uswds": "^2.10.0",

Describe the bug
When trying to use GovBanner with props get typescript warning that breaks compilation.  Right now just using without props and it works fine.
"Type '{ language: string; tld: string; "aria-label": string; }' is not assignable to type 'IntrinsicAttributes & ClassAttributes<HTMLElement> & HTMLAttributes<HTMLElement>'.
  Property 'language' does not exist on type 'IntrinsicAttributes & ClassAttributes<HTMLElement> & HTMLAttributes<HTMLElement>"

To replicate:
Try to use GovBanner with props in the example app.
Expected behavior
Can use GovBanner with props.
Screenshots
n/a app breaks
Additional context

Oops, its because the new props aren't released yet. My mistake 🤦


Added logarithm

Added logarithm, not sure if upper limits are appropiate or need a tweak.

Looks good!


Routing removes non-InstantSearch query params

🐛 Current behavior
Access to the route https://qqsx4m-3000.csb.app?test="test" remove the query param https://qqsx4m-3000.csb.app
🔍 Steps to reproduce

Enter to the codesandbox
Replace the url with a query param, example ?test="test"
Reload the url
The query param should be removed

Live reproduction
https://codesandbox.io/p/sandbox/next13-4-4-forked-rdd5h9
💭 Expected behavior
The query param should not be removed
Package version
7.0.3
Operating system
No response
Browser
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @RodrigoTomeES,
Do you mean it removes search params that are unrelated to InstantSearch ? If so, that's how the InstantSearch router functions, regardless of the framework used.
When I got to https://qqsx4m-3000.csb.app/?instant_search[refinementList][brand][0]=Samsung however it doesn't remove the param as it's recognized by InstantSearch.
If you want non InstantSearch params to be persisted, you can implement your own createURL and parseURL to persist your other parameters : https://www.algolia.com/doc/guides/building-search-ui/going-further/routing-urls/react/#rewriting-urls-manually

@aymeric-giraudet Yes, I mean that it removes search params that are unrelated to InstantSerch for example if the URL has UTM params we can't track it because InstantSearch removes it. I think that resolve it implementing our own createURL and parseURL tt's a lot of work for a simple problem. Is there no way to disable this behavior?

InstantSearch is the source of truth for routing. If you want certain keys to stay you can:

read the utm parameters before starting InstantSearch and store them
in router.createURL, add the utm parameters back to the URL

We don't yet have a manner of simplifying this.

@Haroenv Okay, I will implement it, but I don't understand why do you need to remove it 😅. Thanks!
I will put here the code when I implemented it and then close the issue.

I've achieved the same issue for UTM query params with Next + ReactInstantSearch.
I had to migrate from React instant search v6 to v7.
I set serverStateProps props to my <InstantSearch /> component.
Then in createInstantSearchRouterNext in routerOptions, I wrote parseURL and createURL methods like this :
parseURL({ qsModule, location }) {
  return qsModule.parse(location.search.slice(1));
}

createURL({ qsModule, location, routeState }) {
  const { origin, pathname, hash } = location;

  const queriesFromUrl = qsModule.parse(location.search.slice(1));

  // Get all extraneous queries from the URL used for UTM
  const utmQueries = Object.keys(queriesFromUrl)
    .filter((key) => !Object.keys(routeState).includes(key))
    .reduce((acc, cur) => {
      acc[cur] = queriesFromUrl[cur];

      return acc;
    }, {});

  // Create query string with facet filters and UTM queries
  const queryString = qsModule.stringify({ ...routeState, ...utmQueries });

  return `${origin}${pathname}?${queryString}${hash}`;
}

I hope it will help!

@Hashs7 thanks for sharing your code! I will try it because I didn't have time to implement it yet

Thanks, I've just added code similar to the one shared by @Hashs7 to the documentation. Thanks for your contribution and testing!


Adding Cannon Lock to the team page

@CannonLock ping me when you have resized the image, I'll go ahead and merge then.

Down to 24kb, good enough for me.


Nano and Midnight Commander don't work properly on Docker for Windows beta

BUG REPORT INFORMATION
Output of docker version:
Client:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:        Wed Jul 13 03:28:51 2016
 OS/Arch:      windows/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:        Wed Jul 13 03:28:51 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 35
 Running: 0
 Paused: 0
 Stopped: 35
Images: 6
Server Version: 1.12.0-rc4
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 91
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host null bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 991.1 MiB
Name: moby
ID: SDJH:HJ44:NFEB:HQ4E:TBOI:JXRI:3IDX:B4MT:R57R:25HK:TMK3:7WYB
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Local machine Windows 10 PRO Version 1511 (OS Build 10586.494)
Steps to reproduce the issue:

run some distro
install nano or mc

Describe the results you received:
http://take.ms/oU6j3
With nano strange next line moving
With mc encoding and arrow keys problems
Additional information you deem important (e.g. issue happens only occasionally):
I tried cmder, git-bash, powershell, cmd and everywhere the problem exists. Also, I tried to connect to a remote server to compare and it was ok. I'm not the only one https://stackoverflow.com/questions/38555071/nano-and-midnight-commander-dont-work-on-docker-for-windows-beta/38567570

Thanks for the report.
This is more an issue with the lack of terminal emulation in the various Windows shells. I was able to reproduce the issue on standard Windows 10 pro 1511 (build 10586) but it works fine on a recent insider build with Powershell (I tested with build 14367).
Microsoft will soon release RS1 which should have the improved terminal emulation available.

Closing as it is an upstream Windows issue, but feel free to continue discussing here as I am sure that other people will run into this.

I'm sorry, maybe it's a dumb question but why it works with no docker environment? I mean for example with a remote server using the same terminals.


User Settings & Config Rejigging

Use CFG instead of registry for some settings.
Put CFG in user's appdata to preserve settings between DSMapStudio updates.
Param 'CSV' export delimiter sanity checks (since it needed to be heavily modified to consistently use CFG anyway).

I broke the branch while doing merge testing, will make another PR later.


Self is not defined

When trying to include in react with:
import Localforage from "localforage"
I am getting the following error:
root//node_modules/localforage/dist/localforage.js:1162
})(typeof window !== 'undefined' ? window : self);
ReferenceError: self is not defined
Using browserify. This issue is probably related to #469

This should be fixed with the next release, because we're using Browserify's definition of the global object instead of our own custom global object.

Released a new version (1.4.1), should be on npm once Travis builds it (should take < 30mins max).
Thanks for reminding me to release a new one 😄


Background property overwrites background-size property

Overview of the problem
Oruga version: [0.5.9]
Vuejs version: [2.7.10]
OS/Browser: any
Description
Using the background shorthand css property to set the color only overwrites other background css property like background-size.
Steps to reproduce
https://user-images.githubusercontent.com/9740270/203086376-23aeabf1-6e77-48fb-8d93-de978bab5635.mov
Expected behavior
background-size shouldn't be overwritten by background property
Actual behavior
background-size property effect is lost

Probably you are right, can you make a PR?


option_env does not get updated when rebuilding and value of the key changed.

Problem
I expected to see this happen:
Recompiling with cargo build / cargo run should update the value received from option_env to the current value of the key in the environment.  Setting CARGO_INCREMENTAL=0 doesn't seem to affect this. It only causes a recompile the first time around since incremental compilation is turned on by default.
Instead, this happened:
The value received from option_env only changes when running cargo clean before.
Steps
This is a minimum example.
fn main() {
    let var = option_env!("TEST_OPT_ENV");
    match var{
        Some(str) => println!("{}", str),
        None => println!("Hello, World!"),
    }
}

$ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.36s
     Running `target\debug\hello_world.exe`
Hello, World!
$ TEST_OPT_ENV="Using Option Env" cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
     Running `target\debug\hello_world.exe`
Hello, World!
$ cargo clean
$ TEST_OPT_ENV="Using Option Env" cargo run
   Compiling hello_world v0.1.0 (C:\Users\jschw\CLionProjects\hello_world)
    Finished dev [unoptimized + debuginfo] target(s) in 0.38s
     Running `target\debug\hello_world.exe`
Using Option Env
$ CARGO_INCREMENTAL=0 TEST_OPT_ENV="Using Option Env Test 2" cargo run
   Compiling hello_world v0.1.0 (C:\Users\jschw\CLionProjects\hello_world)
    Finished dev [unoptimized + debuginfo] target(s) in 0.28s
     Running `target\debug\hello_world.exe`
Using Option Env Test 2
$ CARGO_INCREMENTAL=0 TEST_OPT_ENV="Using Option Env Test 3" cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
     Running `target\debug\hello_world.exe`
Using Option Env Test 2

Possible Solution(s)
https://github.com/rust-lang/rust/pull/71858 should provide the necessary information once it is merged.
Why I think I need this:
I'm compiling (and linking to) a rust library from a build script (different target) and want the option_env to get updated when I rebuild with a different value set for the key specified in the option_env.
Notes
Output of cargo version:
cargo 1.45.0-nightly (9fcb8c1d2 2020-05-25)
rustc --version --verbose:
rustc 1.45.0-nightly (ad4bc3323 2020-06-01)
binary: rustc
commit-hash: ad4bc3323b9299d867697e9653dcea1b5e1ad283
commit-date: 2020-06-01
host: x86_64-pc-windows-msvc
release: 1.45.0-nightly
LLVM version: 10.0

Thanks for the report! Indeed there's not a whole lot Cargo can do about this, but https://github.com/rust-lang/rust/pull/71858 is targeted at fixing Cargo.

This is now fixed by #8421.


adds illustrations to help understand attribute service and building steps

This PR

Answers how Hypertrace uses attribute service
Adds schematic representation for attribute service
Adds flows involving attribute service
Add steps to build image locally
link to dockerhub image source

@adriancole @buchi-busireddy rleiwang is still a code owner.
We should clean that up first.

@adriancole @buchi-busireddy rleiwang is still a code owner.
We should clean that up first.

that's independent I think and can go here or another PR or commit to master doesnt' matter. If any of this happens @JBAhire can rebase if that helps or just ignore for this PR

@JBAhire To fix snyk issue, update below library version from 0.1.3 to 0.2.0 in below files
From:
./attribute-service-impl/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-context-utils:0.1.3")
./attribute-service/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-server-utils:0.1.3")
./attribute-service-client/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-client-utils:0.1.3")

To:
./attribute-service-impl/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-context-utils:0.2.0")
./attribute-service/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-server-utils:0.2.0")
./attribute-service-client/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-client-utils:0.2.0")

@JBAhire To fix snyk issue, update below library version from 0.1.3 to 0.2.0 in below files
From:
./attribute-service-impl/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-context-utils:0.1.3")
./attribute-service/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-server-utils:0.1.3")
./attribute-service-client/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-client-utils:0.1.3")

To:
./attribute-service-impl/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-context-utils:0.2.0")
./attribute-service/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-server-utils:0.2.0")
./attribute-service-client/build.gradle.kts:  implementation("org.hypertrace.core.grpcutils:grpc-client-utils:0.2.0")

Thanks, Ronak! Let me try that!


Added Java 8 InstantParam with test.

Some java 8 users might want to avoid Joda-Time in favor of Instant

Coverage increased (+0.01%) to 84.535% when pulling 53d78e59341fa9dac64c69dbb1dedb228b4384a7 on lightswitch05:feature/instant-param into cebf1d67dffc14ae235806e3fffae4f607b459dc on dropwizard:master.

Coverage decreased (-0.01%) to 84.51% when pulling 8710100e40e395069fe1ede537482a22323ddf77 on lightswitch05:feature/instant-param into cebf1d67dffc14ae235806e3fffae4f607b459dc on dropwizard:master.

Coverage increased (+0.03%) to 84.551% when pulling ccf006c027ab8e903c6a2dcc28b490bc4654ef61 on lightswitch05:feature/instant-param into cebf1d67dffc14ae235806e3fffae4f607b459dc on dropwizard:master.

@joschi I made the requested changes, let me know if it needs more work

@lightswitch05 Thanks!


bugfix: 修复 Agent 安装失败：'NoneType' object has no attribute 'get' 的问题 (f…

…ixed #587)

Codecov Report

Merging #592 (f70db6a) into V2.2.7-rc (241db45) will increase coverage by 0.01%.
The diff coverage is 50.00%.

@@              Coverage Diff              @@
##           V2.2.7-rc     #592      +/-   ##
=============================================
+ Coverage      71.21%   71.23%   +0.01%
=============================================
  Files            290      290
  Lines          21042    21043       +1
=============================================
+ Hits           14986    14990       +4
+ Misses          6056     6053       -3

Impacted Files
Coverage Δ

...components/collections/agent_new/query_password.py
92.85% <50.00%> (-1.69%)
:arrow_down:

apps/backend/views.py
83.23% <0.00%> (ø)

...nents/collections/agent_new/choose_access_point.py
96.51% <0.00%> (+0.49%)
:arrow_up:

apps/backend/subscription/steps/plugin.py
49.26% <0.00%> (+0.63%)
:arrow_up:

Continue to review full report at Codecov.

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


[Logs] Update docs to reflect latest logpush template

@Kbman99 Please review the changes for network-analytics-logs dataset, and fix internal logshare-api repo if needed.

@Kbman99 I'm merging this PR but could you please address @soheiokamoto comment to review the changes for network-analytics-logs dataset, and fix internal logshare-api repo if needed.


drop bad queue time events

What does this PR do?:
Queue time events which are committed during a profiler dump may end up with null scheduler and task attributes, if they are committed just as the class map is being cleared, because the lock can't be acquired when looking up the class name. These events aren't very useful so we'll drop them for now.
Motivation:

Additional Notes:

How to test the change?:

For Datadog employees:

[ ] If this PR touches code that signs or publishes builds or packages, or handles
credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
[ ] This PR doesn't touch any of that.

Unsure? Have a question? Request a review!

Dropping an event isn't too significant except at the trace level - it doesn't change sampling statistics, the events are latency thresholded and tend to occur in batches, so if we drop some during clearing the class map, we'll usually get some just before or after. We can revisit this if we want to change the way buffering works during dumping the recording.


[v1 Snackbar] Update with correct event on snackbar action dismiss

Problem
When we click the action button on a Snackbar it incorrectly calls dismiss().
https://github.com/microsoft/fluentui-android/blob/master/fluentui_transients/src/main/java/com/microsoft/fluentui/snackbar/Snackbar.kt#L212
This calls dispatchDismiss(BaseCallback.DISMISS_EVENT_MANUAL) in BaseTransientBottomBar.
Instead it should directly call  dispatchDismiss(BaseCallback.DISMISS_EVENT_ACTION)
Fix
DISMISS_EVENT_ACTION indicates that the snackbar was dismissed via an action click
DISMISS_EVENT_MANUAL indicates that the snackbar was dismissed via a call to dismiss()
Since here the snackbar is being dismissed via action click, the correct event should be DISMISS_EVENT_ACTION
Fixes issue #101
Validations
Validated in Fluent demo app, snackbar is getting dismissed with the correct event
Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] Automated Tests
[ ] Documentation and demo app examples
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and RTL layouts
[ ] Size classes and window sizes (notched devices, multitasking, different window sizes, etc)

basecallback is dismissed?

sorry, couldn't get your question, can you please elaborate?


Add Calikronic's File

created a branch, created a file and made a commit, and opened a pull request


adding http -> https redirection for production env

cc @jdorfman

:+1:

This is nice but it seems to fail for the naked domain. Try https://hstspreload.appspot.com/?domain=bootstrapcdn.com which is what I aim to fix eventually with #700.


Fix HttpOpSensorTest to use fake resquest session

The SimpleHttpOperator and HttpSensor in HttpOpSensorTest were originally reaching out to google.com  via HttpHook, and causing occasional timeout failure in unit test. By mocking request.Session we no longer have to depend on real connections. (Ref #1218 )  @criccomini

Coverage remained the same at 66.377% when pulling bd7234fdd9484dd377ab8b2f226b0847f94bf97a on jgao54:mock-request-in-test into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

Coverage remained the same at 66.377% when pulling 86eb9dedf794407d0c3754cb2fc095519da2f3ac on jgao54:mock-request-in-test into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

Coverage remained the same at 66.377% when pulling 5859bb90ce088bf24e34caa2882b0c823cec5998 on jgao54:mock-request-in-test into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

Thanks for the contribution! Please follow these http://chris.beams.io/posts/git-commit/ guidelines for your commit message. It helps creating changelogs and release notes in the future.

@bolkedebruin  ack

Coverage increased (+0.03%) to 66.403% when pulling f6996c2206e16d4c81c9c702ad941154fa1f6163 on jgao54:mock-request-in-test into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

All other builds ok, not sure why it's hitting the following error for Python 3.4 with mysql.
ERROR: InvocationError: '/home/travis/build/airbnb/airflow/.tox/py34-cdh-airflow_backend_mysql/bin/coveralls'


🛡 Eliminate client certificate for dependency-watchdog-probe

How to categorize this PR?

/area security
/kind enhancement
/merge squash
What this PR does / why we need it:
This PR was initially proposed/merged with https://github.com/gardener/gardener/pull/5011 and got later reverted with https://github.com/gardener/gardener/pull/5289 due to https://github.com/gardener/dependency-watchdog/issues/36.
However, now that https://github.com/gardener/dependency-watchdog/issues/36 got fixed, released and incorporated in gardener/gardener with https://github.com/gardener/gardener/pull/5675, we can reintroduce this PR.
Similar to #4931, this PR eliminates the client certificate for the dependency-watchdog-probe in favor of a token managed by the TokenRequestor controller in gardener-resource-manager.
Which issue(s) this PR fixes:
Fixes #4661
Part of #4878
Special notes for your reviewer:
/invite @BeckerMax
/cc @ashwani2k @himanshu-kun @unmarshall
Release note:

`dependency-watchdog-probe` does no longer use a client certificate but an auto-rotated `ServiceAccount` token which is only valid for `12h`.

/assign


Add fi locale support

Add support for Finnish names.
Note that this has capitalized days and months even though they are not capitalized when used in the Finnish language—is this ok?

Hi @vsaarinen, thanks for your PR.

Note that this has capitalized days and months even though they are not capitalized when used in the Finnish language—is this ok?

If there's not a single place in the Finnish language where the capitalized form is used (not even at the beginning of a sentence?) then I guess there's no point capitalizing them.

Days and months are capitalized at the beginning on sentences, so I guess this can be merged as-is.

Merged.
I've also release a new patch version including this change and the fix from your other PR.


Softmax + concat does not work with cuDNN enabled ?

I have implemented a simple neural network and a true multi-class Hinge Loss to perform multiclass classification. However the behavior of the backpropagation seems to differ when cuDNN is enabled or not in the softmax function, due to the use of F.concat. I have attached 2 python files, run "python small_example.py" and change use_cnn to False/True to observe the different behavior (accuracy 95 % after 10 epochs if disabled, 22% if enabled). Maybe it's a bug on my cuDNN.
issue_chainer.zip

Hi, thank you for reporting the problem. I am afraid it is hard for me to identify where the problem is. So, is it possible for you to make a minimal code in which problem occurs so that we can narrow the problem?

I have enclosed a simple example code, you mean something even more minimal
?
On Tue, Sep 6, 2016 at 8:33 AM, Kenta Oono<EMAIL_ADDRESS>wrote:

Hi, thank you for reporting the problem. I am afraid it is hard for me to
identify where the problem is. So, is it possible for you to make a minimal
code in which problem occurs so that we can narrow the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pfnet/chainer/issues/1605#issuecomment-244872088, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANKFTnODVppiyjUmLUb-bZNUTFA6XBcXks5qnRdkgaJpZM4J09vX
.

you mean something even more minimal?

Yes, it is what I thought in mind. As it involves some work, it is OK as much as you can. But I would like you to extract the point where some inconsistencies occur as much as possible.


kata-env: Add ability to output as JSON

Having a direct JSON output for kata-env will help record
results in our CIs in some instances. Add that ability with
a kata-env command line extension.
Fixes: #474
Signed-off-by: Graham Whaley<EMAIL_ADDRESS>

Part of the reason I've pushed this is to see what the CI thinks, as I've not quite figured out how to sanely get the 'make check' to run on this locally yet... ;-)

Updated the tests and re-pushed.
If CI's pass go tests, pls review.

Haha: cli/kata-env_test.go:1::warning: file is not gofmted with -s (gofmt) - thought I'd done that already... repushed

@amshinde ptal

lgtm

\o/


[Java][Release] Remove Java related codes from release scripts

Describe the enhancement requested
Release scripts: https://github.com/apache/arrow/tree/main/dev/release
We also need to update our release document: https://github.com/apache/arrow/blob/main/docs/source/developers/release.rst
Component(s)
Java, Release

Issue resolved by pull request 44854
https://github.com/apache/arrow/pull/44854


Powershell scripting

A couple of simple PowerShell scripts.  One to copy the Nuspec files for a new DX version and one that builds the packages for each Nuspec files in the spec folder.

Hi @seankearon,
Thanks for submitting this PR. I appreciate it.
I've finally managed to spend some time on this project, and I see you have a few of commits here, so let me address them:

The Powershell script for updating the version number in the .nuspec files for a new version is interesting, but the resulting package will not be 100% reliable because DevExpress adds/removes assemblies and references in each new version, so the .nuspec files have to always be re-generated based on the new assemblies for each version. I mentioned in the README that I have a quick n' dirty C# app that does that work (i.e. maps assemblies dependencies via reflection and generates the .nuspec files) and I'll continue using that until either I manage to refactor it and add to this repository or someone else sends a PR with an app or script that does the same.

I thought how I'd like to handle the different versions of the .nuspec files moving forward, and I concluded that being able to diff between versions and see exactly which assemblies got added/removed in each version is super valuable, so I've decided not to keep folders side-by-side like I initially thought (e.g. v14.1.7, v14.1.8, etc.), so instead I'm overwriting the .nuspec files for every version, on the same folder.

I'm creating tags and releases for each version, and if I have to patch an old version I'll just branch off one of the tags and patch it there.

With that said, I won't take the changes in this PR as they are currently, but feel free to send a revised one for the Powershell script that builds the packages (as your version looks better than mine) or anything else you'd like to propose.
Thank you!

Thanks Caio - I'll keep my eye out for updates.  This is a really useful piece and takes away some of the friction from working with DevExpress.
Cheers
Sean


[AIRFLOW-3231] Basic operators for Google Cloud SQL

Add CloudSqlInstanceDeployOperator, CloudSqlInstancePatchOperator and CloudSqlInstanceDeleteOperator.
Each operator includes:

core logic
input params validation
unit tests
presence in the example DAG
docstrings
How-to and Integration documentation

Additionally, small improvements to GcpBodyFieldValidator were made:

add simple list validation capability (type="list")
introduced parameter allow_empty, which can be set to False
to test for non-emptiness of a string instead of specifying
a regexp.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@334bc1e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #8   +/-   ##
=========================================
  Coverage          ?   77.93%
=========================================
  Files             ?      199
  Lines             ?    15974
  Branches          ?        0
=========================================
  Hits              ?    12449
  Misses            ?     3525
  Partials          ?        0

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 334bc1e...657d7c0. Read the comment docs.

I've created a separate PR fixing the issue with flake8 tests failing on Travis. It already got merged and I rebased this PR to include the fix.
Apart from that I also noticed there were inconsistencies in variable names between our operators and the Python Google API / docs (namely we had name for the instance name, when the docs have instance, similarly we had project_id while in the docs it was simply project).
That's why I also added a fixup to unify all the names. These changes are minor, but feel free to take a look if you wish before I close this PR and create the one to the apache/incubator-airflow repo.

I'm leaning toward sticking with project_id despite the API using "project".

It's consistent with most GCP operators (there have previously been inconsistency issues)
The docs suggest it only accepts project_id as opposed to project_number, so calling it project_id should reduce cognitive load.

Closing this internal PR, will squash and open a new one to apache.


chore: remove socket.io

@pradel

Deleted createServer client part as I believe this won't be used for a while
Commented out socket io parts from buildApp queue as I wasn't completely sure about whether it is best to delete or leave it for now. If it's better to delete, let me know and I will update PR.
Rest of the changes are really obvious I believe :)

Closee #133


Werkzeug 2.1.0 fails with WERKZEUG_SERVER_FD error

Upgrading to 2.1.0 leads to the following error:
"message": "Starting REST API"
"message": "'WERKZEUG_SERVER_FD'",
"exc_info": "Traceback (most recent call last):
  ...
  self.app.run(host=self.host, port=self.port, debug=self.debug)
  File \"/usr/local/lib/python3.9/dist-packages/connexion/apps/flask_app.py\", line 104, in run
  self.app.run(self.host, port=self.port, debug=self.debug, **options)
  File \"/usr/local/lib/python3.9/dist-packages/flask/app.py\", line 920, in run
  run_simple(t.cast(str, host), port, self, **options)
  File \"/usr/local/lib/python3.9/dist-packages/werkzeug/serving.py\", line 1047, in run_simple
  fd = int(os.environ[\"WERKZEUG_SERVER_FD\"])
  File \"/usr/lib/python3.9/os.py\", line 679, in __getitem__
  raise KeyError(key) from None
  KeyError: 'WERKZEUG_SERVER_FD'"
"message": "SHUTDOWN"

Environment:
$ lsb_release -d
Description:	Debian GNU/Linux 11 (bullseye)

$ python3 --version
Python 3.9.2

# selected packages
$ pip3 list
Package               Version
--------------------- --------------
connexion             2.13.0
Flask                 2.1.0
Werkzeug              2.1.0

Workaround:
freezing Werkzeug @ 2.0.3 in requirements.txt (which we didn't have before as don't use it directly but it's rather a prerequisite of connexion and Flask)
Werkzeug==2.0.3

Looks like connexion is messing with the dev server internals in a way that tricks it into thinking it's running in the reloader when it's not. Since it's not actually running in the reloader, certain things that it expects aren't set up correctly. You'll need to report this to connexion.

@davidism could you point me to where connexion is messing with the dev server internals? I'm having a hard time reproducing the issue.

Yeah, I had a look and can't reproduce this either. If anyone is setting WERKZEUG_RUN_MAIN manually for some reason, that's what would mess with it.

@davidism, thanks for the hint. Apparently, it was set in systemd service file, removing that solved the issue.
# required to disable Flask debugging banner: "Serving Flask app (lazy loading) ..."
Environment="WERKZEUG_RUN_MAIN=true"

The fact that you're running this in systemd indicates a severe security issue with that application. Do not run the development server in production. It is not intended to be secure, stable, or efficient. The fact that you have to set an internal variable just to disable this message should be a strong indicator that you're doing something incorrect.

Thanks for the info. Will review what was done there :)


Better error handling on the backend side

Currently, the backend returns "internal server error" even if there was not actually a problem on the server side. This PR tries to improve error handling in KeyConjurer so that a user gets more info in errors returned by KeyConjurere.
Main updates:
*Introduced standard errors for the Okta client. The client now inspects errors from Okta a bit deeper and wraps them into one of the standard errors.

Introduced standard errors for authentication providers. The Okta provider now also inspects Okta's errors a bit deeper and returns one of the standard errors.
When getting SAML assertion, the lambda handler now checks errors from the authentication provider to pick up a right error code.
Added several tests.

Thanks for the review @trinitroglycerin ! The comments make sense to me. In fact, there are a few more functions that should not be exported. I've addressed your comments.


Integration tests

What about using vcr to record the live responses so you so don't have to issue external requests when running tests (unless recording a new response)?

@rossta that won't prove that the gem works with actual API. VCR is good when you rely on some external API, but not depend on it. But in case of API gem it is essential to ensure that all real requests work as expected.

@honestweb thanks, I will merge it as it is and take over adding actual API key for CI.

Ok, but then other developers won't be able to run the integration tests without access to the API key - or at least tests that inspect the contents of actual responses. What do you think on enabling these specs only on Travis?

@rossta I will be glad to review and merge a PR that does that


[C++] Row batch not reset notNull data if strip doesn't have PRESENT stream.

In ORC, PRESENT stream is optional, and ORC Reader reused ColumnVectorBatch to read data. So if it don't reset notNull data in ColumnVectorBatch, it will use last notNull data incorrectly.

Thank you for reporting, @kaka11chen .


Implement new behavior, RepeatSequence

Implements new behavior RepeatSequence which acts like a Sequence but repeats forever as long as a conditional behavior succeeds (or fails) that precedes the sequence. The condition is only checked before the sequence runs and not during the sequence, unlike in While behavior.
I am testing this on my own application soon to see if anything should be changed but here's the initial idea draft anyway.
Related issue: https://github.com/Sollimann/bonsai/issues/23

Hey, sorry for late reply. Will have a look on your PR sometime in the next couple of days. Been quite busy lately

I added the required changes but I could not verify that RepeatSequence works as intented when it comes to the timing values since I failed to understand how it they are supposed to work. I added one test for RepeatSequence, test_repeat_sequence_timed, that asserts the returned time values, but I am not sure it makes sense. Can you verify that?
It seems that the other behaviors (or at least While) also panic when empty sequence is given to them in addition to the initial condition, so added panic message to RepeatSequence. Perhaps other behaviors need this as well, or the panic cases should be fixed.

pre-commit is failing, so you need to make the fixes as suggested by the failing checks.
https://github.com/Sollimann/bonsai/actions/runs/6944779061
to install pre-commit for this project, see: https://pre-commit.com/
Its basically:

sudo -H pip install pre-commit
pre-commit install in root of this repo

Also, I have invited you to be collaborator on the project. That should give you some more privileges for the project.

Other than that, I think it looks good now. Will approve when all the checks pass. Great work! :)

Also, can you bump version to 0.5.0? I will release a new version to crates.io once merged.

Thanks! I also had to do some cosmetic changes to the boids example to get through the pre-commit. Looks good now?

I´ll make a new release once you have merged it to main :)


Refactor selectWorkspaceFile to automatically detect and incorporate any known rootFolder

Fixes https://github.com/microsoft/vscode-azurecontainerapps/issues/684
This PR does the following:

Enables the utility function to work more optimally for multi-root workspaces when a rootFolder property is detected on the context
Only show the relative path in the description rather than the absolute path

What's this work for? For security? For AI?

Needed to fix multi-root for running the test projects 🫡


VoIP support

Might be nice to have additional helper code for VoIP signalling in the SDK.
From what I've been doing with VoIP bridging, I've found it's easiest to use an object representing calls. It might be nice to be able to listen for incoming calls, being provided with a call object to represent it, which can then be used to send and receive signalling specific to that call.
This could help make VoIP bridging more widespread since a number of bridges depend on this SDK.
Is there any interest in something like this?

This is being done as part of MSC3401: https://github.com/turt2live/matrix-bot-sdk/pull/227


Need auto run TypescriptAddMissingImports, TypescriptRemoveUnused, TypescriptOrganizeImports on save file

Hey @bigzhu! You can try adapting this bit from my config:
local Format = vim.api.nvim_create_augroup("Format", { clear = true })
vim.api.nvim_create_autocmd("BufWritePre", {
  group = Format,
  pattern = "*.tsx,*.ts,*.jsx,*.js",
  callback = function()
    if vim.fn.exists(":TypescriptFixAll") then
      vim.cmd("TypescriptFixAll!")
      vim.cmd("TypescriptRemoveUnused!")
    end
  end,
})

You can try something like what @mmirus mentioned, but this is fundamentally not well-supported for reasons out of our control (see #5 if you're curious as to why).

That's a good point. Thanks! I forgot about that discussion.


Typo and grammar fixes

Related PR: https://github.com/operator-framework/operatorhub.io/pull/324

@Fryguy, thank you :+1:


Add OpenAPI spec to PHP Library

One small nitpick for this and #34: add OpenAPI code generation, or maybe just "Add code to interact with the Svix API".
Feel free to ignore me 😂


Fix queue length stats for Publishing API.

https://trello.com/c/sSFxdCHU/86-fix-publishing-api-worker-speed-and-throughput-to-not-show-sum-of-sidekiq-workers
The queue length reported by each instance is for the entire queue,
which means the use of 'sum' was counting the entire queue length
multiple times. Using avg should give us a more reasonable number!

Good spot Ben, no idea why I thought that was a good idea...


[WIP] add local spark test notebook in sample

Description

Resolves #770
How was this PR tested?

Execute in local VS code Jupyter notebook.
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to clarify your proposed changes.

@Yuqing-cat I see outputs are submitted with this PR, could you please clean up?

Closing this as a container based sandbox feature has been added, the sandbox comes with local spark, local redis, local jupyter server, local feathr registry in one docker image. For anyone who is interested to try sandbox, please check this doc https://feathr-ai.github.io/feathr/quickstart_local_sandbox.html


[Feature] webhook trigger: Improve client secret integration

WHY are these changes introduced?
Related tasks:

https://github.com/orgs/Shopify/projects/4831/views/1?pane=issue&itemId=16213451
https://github.com/orgs/Shopify/projects/4831/views/1?pane=issue&itemId=16450983

WHAT is this pull request doing?
It renames --shared-secret to --client-secret (shared-secret still there but showing a deprecation warning)
It allows you to use a secret automatically from the app config:

.env file if you've previously done env pull
server, by asking about the app (or guessing it because you only have one or because your folder matches any of the existing ones)

A graphic explanation of the new flow:
graph TD
    start[Get Shared-Secret flow] --> flag{--shared-secret}
    flag --> |it's set| usef[Use --shared-secret flag value]
    flag --> |it's not set or empty| man>Prompt: Set manually?]
    man --> |yes| many>Prompt for secret] --> manys[Use secret]
    man --> |no| env{.env & secret present}
    env --> |yes| envyp[/Print: Using .env secret/] --> envyu[Use .env secret]
    env --> |no| autoa(retrieve available apps)
    autoa --> |some options available| autof(get current folder name) --> autofy{folder name in list?} --> |yes| selappr(retrieve app secret) --> autofyp[/Print: Using app secret/] --> autofyu[Use app secret]
    autofy --> |no| only{Only one app}
    only --> |yes| selappr
    only --> |no| selapp>Prompt to select app] --> selappr
    autoa --> |no options| noapp>Prompt for secret] --> noappu[Use secret]

How to test your changes?
spin up:
schema: v1
extend: identity
repos:
  - partners:
      env:
        DISABLE_SHOPIFY_INTERNAL_API_INTERCEPTOR: "1"
  - captain-hook
  - shopify
  - storefront-renderer
  - webhook-receiver
  - web

These are the cases I've tested ✅ :

try the command with --shared-secret. It should work (do not prompt for secret), but show this warning:

The flag shared-secret has been deprecated in favor of client-secret and will be eventually deleted.
Please use --client-secret instead.

try the command with --client-secret. It should work without warning

Try the command without the secret flag. You should be prompted for:

?  Do you want to set the client-secret manually?

>  (y) Yes, I'll type it myself
   (n) No, try to get it from the app config

If you select (y) then you should be prompted for secret and it'll be used

The following cases apply when you select (n)

Create .env file without SHOPIFY_API_SECRET: It should go through the prompt process (see from point 7 on)

Create a .env file with SHOPIFY_API_SECRET: It should use the secret stored in that file

If you have no app: You should get prompted for secret value (you'll be prompted for org and app selection previously)

If you only have one app: Your app secret should be used

If you have several apps and one of them matches the name of your current folder: The app secret should be used

If you have several apps and none matches the name of your current folder: You will be prompted to select app and its secret will be used

Post-release steps
Post-release: Update dev docs. No hurry because the two flags are accepted and the contract is not broken
Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[ ] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

@pacocastrotech just released this: can I assume you're going to track the post release steps separately?

@pacocastrotech just released this: can I assume you're going to track the post release steps separately?

@Arkham yes, I will take care of the docs update (it's a flag renaming and we're maintaining the two flags with a deprecation warning so the docs are still good!). Thanks!


Fixes #7259

Fixes #7259
This inserts line breaks into Stereo Groups when the line would become longer than 80 chars.

I fixed the merge conflict in the web editor (always a bit risky...)
will merge after the CI builds go through


Disable some tests for which dependencies are not available in Windows

This allows building the test suite on Windows.

@swift-ci please test


deps: remove deprecated content-scope-utils

Reviewer:
Asana:
Description
Steps to test

Current dependencies on/for this PR:

main

PR #384   👈

This comment was auto-generated by Graphite.


add: publish settings

Summary by CodeRabbit

New Features

Implemented continuous publication workflow for the Scala project using GitHub Actions.
Added support for automated releases to the Sonatype repository.

Chores

Integrated sbt-ci-release plugin for enhanced publication process.
Updated project configuration for better metadata management and distribution.

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

Comparison is base (91261c5) 78.86% compared to head (635240b) 78.86%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #126   +/-   ##
=======================================
  Coverage   78.86%   78.86%
=======================================
  Files          25       25
  Lines         459      459
  Branches       43       43
=======================================
  Hits          362      362
  Misses         97       97

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


add order list component in NFTPage and TopPage

Related
https://github.com/kaguraswap/monorepo/issues/94
https://github.com/kaguraswap/monorepo/issues/105

doing with #125