linux: disable WERROR by default

gcc update frequently breaks most recent kernel releases due to blanket -Werror
flag. Let's avoid -Werror in a default build to ease kernel and gcc maintenance.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is this option introduced since 5.15 or why the limiting?

Is this option introduced since 5.15 or why the limiting?

Yeah, it was added in https://github.com/torvalds/linux/commit/3fe617ccafd6f5bb33c2391d6f4eeb41c1fd0151:
$ git tag --contains 3fe617ccafd6f5bb33c2391d6f4eeb41c1fd0151 | cat
v5.15
...
v5.15-rc7
...
v5.18
...
v5.18-rc7


[Feature]: Show pull button on Deploy tab, when there are no changes to commit, but local is ahead of remote repo

Is there an existing issue for this?

[X] I have searched the existing issues

Summary

Why should this be worked on?
Even though pull functionality exists in bottom bar, we should show pull button here too. gitV2.


Add appveyor and travis build scripts for continuous integration

Results
Appveyor: https://ci.appveyor.com/project/jeking3/format/build/1.0.2-develop
Travis: https://travis-ci.org/jeking3/format/builds/286199980
Known Issues
The following builds are commented out because of issues in this or other modules:

ticket
module
issue

13249
test
cygwin build on appveyor fails attempting to use linux calls

13255
test
mingw build on appveyor uses undefined vsnprintf

These should be investigated, fixed, and tests re-enabled.
Maintainer Follow-Up
Maintainer of Boost.Format needs to request admin access on github, travis, and appveyor so that they can enable automatic builds on pull requests to the official repository.
A readme file should also be added with build results, similar to Boost.Uuid.

The travis and appveyor files are much more complicated than the ones I have recently added to other non-CMT libraries which did not have them before. So maybe someone else can comment on whether or not they are valid or not. I do believe we should have travis and appveyor files for all CMT libraries, so I appreciate this effort. A problem, however, is that only the admin can add libraries to be tested using Travis CI, although I believe that is not the case for appveyor, but CMT maintainers do not have admin rights to CMT libraries even if they have write access to those libraries. So even if we get travis and appveyor files for all CMT libraries we will need someone with admin rights for those libraries to setup the travis ( and maybe appveyor ) testing.

These are iterations of the files I have already pushed into uuid, winapi, predef, and random.  I asked for maintainer responsibilities on boost format so I could see this through to completion.  I agree with you that sometimes the files look overwhelming or extraneous, but I customize each one to the repository and its needs.  This one is almost identical to the one I submitted for random.  ANY CI is better than no CI.

If you think it will be worthwhile I can change the build mechanism to use a script that uses a json or yaml file to describe the matrix to pass to bjam, however on appveyor there are limitations on which build image can support which compiler type and version.  I would love to have a more universal script all repositories can use, but in the interim having any CI is better than none for quality.

No, there is no reason to have anything other than a .yml file. I am just not knowledgable enough on the .yml files for travis and appveyor to know whether or not the ones here are correct. My own are largely a copy and simplification of other libaries which already have them, so I can freely admit little expertise in what should be in them for travis and appveyor. That is why I am hoping someone else looks at them. I have no problem merging the PR if told that the .yml files are OK. But if you already have maintainer rights for 'format', you can do so yourself if you like.

I am not officially a the maintainer for Boost.Format at this time.  I did email the mailing list about it.

Thanks, now just waiting for the maintainer application to be approved and move forward.


Search not working

I've been using the search for about a month and it has been working fine until a couple days ago. I'm trying to search for anything and it's not working. My code:
email, username, password =<EMAIL_ADDRESS>'xxx', 'xxx'

search = Search(email, username, password, debug=1)

query = 'elon musk'
latest_results = search.run(
    query,
    limit=100,
    latest=True,  # get latest tweets only
    retries=3,
)

Result:
[success] xxx login success
2023-06-21 10:09:00.120 [DEBUG] :: 'timeline'
2023-06-21 10:09:00.122 [DEBUG] :: No data for: elon musk, retrying in 1.98 seconds
2023-06-21 10:09:02.278 [DEBUG] :: 'timeline'
2023-06-21 10:09:02.279 [DEBUG] :: No data for: elon musk, retrying in 2.17 seconds
2023-06-21 10:09:04.620 [DEBUG] :: 'timeline'
2023-06-21 10:09:04.622 [DEBUG] :: No data for: elon musk, retrying in 4.99 seconds
2023-06-21 10:09:09.776 [DEBUG] :: 'timeline'
2023-06-21 10:09:09.777 [DEBUG] :: Max retries exceeded

I tried:

Without latest
Other search queries
My twitter account is OK, I checked that the search is working on the twitter website

Thanks for this, good catch, they've just moved to a new endpoint. I'll let you know once I've added it.

Actually the endpoint is working. I tested with another library (this one) and it's working. I also tested doing a plain HTTP request and it's also working:

Debugging a little bit I could figure out that the x-csrf-token is not being added to the request.
Response received from request (had to put a print(data) manually in the get function inside search.py):
{'errors': [{'code': 353, 'message': 'This request requires a matching csrf cookie and header.'}]}

print(get_headers(self.session)) inside process function in search.py:
Printed:
{'authorization': 'Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs=1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA', 'cookie'<EMAIL_ADDRESS>flow_token=g;168735834796768345:-1687358348130:gGcdv0PLj0eeI6KCkePoHvu4:13; guest_token=1671528178785873921; password=rolhaGrande14*; username=leandro25632536; auth_token=429b264aabfba403178fe771be87b9f4edd63e0c; guest_id=v1%3A168735834796768345; guest_id_ads=v1%3A168735834796768345; guest_id_marketing=v1%3A168735834796768345; kdt=eld09G7hcVu8n9fATk6j6uLajVsUCUK0JOwos8gD; personalization_id="v1_baOpTDfb2xfE9YwVwLjAag=="; twid="u=1635271498473644032"', 'referer': 'https://twitter.com/', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36', 'x-csrf-token': '', 'x-guest-token': '1671528178785873921', 'x-twitter-active-user': 'yes', 'x-twitter-auth-type': 'OAuth2Session', 'x-twitter-client-language': 'en'}

As you can see, the x-csrf-token is empty: 'x-csrf-token': ''

The problem is in the last commit of twitter/util.py, rolling back this specific file to previous version is working fine
Tested with version 0.9.7 and it is ok

Upon further investigation I can't seem to replicate these errors anymore. It might have been a temporary issue on their end. If this happens again in the future I'll have a look at it. Recent example queries and output are below.
from twitter.search import Search

search = Search(cookies='twitter.cookies',debug=1)

search.run(
    'shaktidb',
    'SAR OR "Synthetic-aperture radar" -tensorflow -tf -jax -trax',
    'vxunderground',
    limit=100,
    latest=True,
    retries=9,
)


ENH: load CDNs when viewing under file://

When I tried to save a local plot as an HTML file and view in my web browser using file://, I could not see the plot. To fix this, in the function to_html I added an optional parameter local_file which defaults to True. When True, it loads the CDNs with http:// and if False it loads under //.
Currently in the default HTML template, the CDNs are being loaded as <script src="//vega.github.io/vega/vega.js"></script> and then because I was viewing local HTML file as file://, it tries to load file://vega.github.io which obviously doesn't exist.

Thanks!
Another option, since the default template is meant just to show a basic example rather than being an all-purpose solution, would be to simply hard-code https:// in the template. I think I'd prefer that just to keep things as simple as possible.

Thanks! Looks good to me, but I'll let @ellisonbg merge.

Thanks!


feat(docs): Update Install docs

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @gaocegege @FogDong

Release note:

NONE

/cc @Thrimbda
The install script is ready, you can install by install.sh, have any question please call me by lark.


Necessary GPUs for Molecular Property Prediction

Hi All,
Hope that you are okay. Just to provide a bit of background, I have been trying to run the finetuneRegr.py script in the conda command line in order to fine-tune the model and predict the conductivity of some compounds.  I formatted my data file according to the steps detailed in #13 and specified the paths to my 1.data, 2. one of the models found in the link, and 3. the vocabulary text file with the added token.
After jumping through some hurdles (mostly changing some lines to account for the updated packages), I am now stuck after I get an error saying that the program needs [0] GPUs to run and I have: []. Could you please confirm that I'm following the right procedure for the task at hand? Are you aware of any way to get around this issue (such as changing the code or using a Cloud GPU Service?
Kind regards,
Diego

What does your trainer look like and how are you defining its parameters? Also, which updated packages are you using?

Closing due to inactivity


Bouncy Castle 1.57 resolves several CVEs

See https://github.com/auth0/java-jwt/issues/178

Thanks @somejeff.

I guess this PR is obsoleted by PR#202. :/


Unicode handling unit tests

Description
Unicode handling unit tests
Type of change

Unit tests (no changes in the code)

Testing steps
Done on CI
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #27 (af74dca) into main (ee19525) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
- Coverage   83.29%   83.21%   -0.08%
==========================================
  Files          17       17
  Lines         425      423       -2
==========================================
- Hits          354      352       -2
  Misses         71       71

Impacted Files
Coverage Δ

ccx_messaging/downloaders/http_downloader.py
62.00% <0.00%> (-0.75%)
:arrow_down:

ccx_messaging/consumers/consumer.py
86.06% <0.00%> (-0.12%)
: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 ee19525...af74dca. Read the comment docs.


[BEAM-714] Converts Datastore to use AutoValue

This style saves a good amount of code and is easier to mimic in new connectors.
I have a few more changes like this lined up.
R: @dhalperi
CC: @jbonofre

Btw can you post a diff of the javadoc output?

To have a javadoc, I added the javadoc plugin to pom.xml.
javadoc diff for the Read transform: https://gist.github.com/jkff/9128e4d33b7defba493df9fdbdd5c365/revisions - it looks almost the same, except methods are abstract and the protected constructor now appears.
I did not change the Write transform because there's no gain to be had from AutoValue in it because it currently has just 1 parameter (project id).

Hmm, the javadoc change ought to be unnecessary, though I'll be darned if I can figure out maven properly. It should be inherited from parents, as we've made Javadoc on-by-default and disabled in certain legacy modules that were not yet ready.
E.g., the old configuration does produce javadoc for GCP IOs: http://beam.incubator.apache.org/learn/sdks/javadoc/0.2.0-incubating/

Aside from the Javadoc config change, LGTM.

Removed javadoc config change - see https://issues.apache.org/jira/browse/BEAM-729

This is nice, Thanks!. LGTM

Looks like something's wrong with the build itself, mvn clean verify passes locally for me.

PTAL, build passed.


default chaise-wide page size

Currently using annotations we can define page_size on table level and if it's not defined, chaise is using 25 by default.  We can define a chaise-config so deployments can change this default value.
We need to discuss this because it might be even useful to have page_size defined in the annotation on schema level.

@RFSH @jrchudy I think we already have this defined in our annotation and it should already be implemented.. Can you guys check?

We have an annotation to define page_size for each table. This issue is about the case that this annotation is not defined. Currently if annotation is not defined, we're using 25 by default. We can make this number a chaise-config instead of a hardcoded value.

Can you check whether we already have this defined? I recalled having a
discussion with Serban about this config for search.
On Tue, Apr 17, 2018 at 1:01 PM, Aref Shafaei<EMAIL_ADDRESS>wrote:

We have an annotation to define page_size for each table. This issue is
about the case that this annotation is not defined. Currently if annotation
is not defined, we're using 25 by default. We can make this number a
chaise-config instead of a hardcoded value.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/informatics-isi-edu/chaise/issues/1458#issuecomment-382123345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZUDOD0yUToGTZ7W-yA4FYkSdqcAQ0cks5tpkokgaJpZM4Shv6n
.

There's a searchPageSize in chaise-config but only search-app is using it.

@robes @bugacov @ljpearlman This shouldn't be difficult.. But is it a high priority?

@RFSH does this annotation get inherit from the schema level?

@hongsudt The current page_size is part of table-display annotation (which is table level). So no.

We are planning to introduce a table-defaults annotation which would also allow us to define the page_size on schema or catalog.  So I'm going to close this issue.


ci: update yaml configuration for CI

Overview
This PR merges the python-app.yml and coverage.yml into one ci.yml to be more clear that this is the continuous integration (CI) configuration.
Fixes #5

The new CI build seem to work great. Self-merging as all checks passed.

LGTM


Modify the valid confirmation period of a COE for Ministry Staff

Modify the valid confirmation period of a COE for Institution #1669
During the implementation of #1590 a valid confirmation period(precisely the end date of this period) of a COE for institution was built with the information present at that moment knowing that it is not final.
Consider a COE with disbursement_date, offering_start_date and offering_end_date.
According to the current logic,
A valid confirmation period for Institutions is any day within valid_confirmation_period_start_date and valid_confirmation_period_end_date
valid_confirmation_period_start_date = disbursement_date - 21 days
valid_confirmation_period_end_date = no end date/indefinite
It is a rare occurence for Ministry Staff to perform this function and IF changes need to occur to the disbursement amount before the ECERT is generated, it is agreed that no UI will be built for Ministry Staff to do it themselves for MVP.  Someone in TBTB will manually adjust the value of the disbursement in the database on an adhoc basis.
** DOES THIS STILL NEED TO BE PART OF THIS TICKET? -->**The logic(number of days) governing valid_confirmation_period_end_date is not final as of now and once it is confirmed please modify the same in backend application and the form.io forms.
Modify the backend application with updated logic on valid_confirmation_period_end_date
Modify the forms student application and program information request.

[ ] Create form for Ministry Staff to modify and approve COE.

There is no currently no validation on any dates for Ministry to approve a COE.  In other words, they can do it whenever they want, before the 21day window and after study end date.


[WIP] Implementation of _select_private_partitions

Description
Implementation of pipelined _select_private_partitions as specified in #8 using pydp.algorithms.partition_selection.PartitionSelectionStrategy.
Affected Dependencies
New Dependency: OpenMined/PyDP aka python-dp.
How has this been tested?
WIP. Awaiting implementation.
Draft of test design:

[ ] Create a synthetic dataset with at least one categorical column
[ ] Pass the dataset N >> 1 times through the DPEngine._select_private_partitions
[ ] Gather histogram of selected categories
[ ] Compare frequencies against theoretical values

Checklist

[ ] I have followed the Contribution Guidelines and Code of Conduct
[ ] I have commented my code following the OpenMined Styleguide
[ ] I have labeled this PR with the relevant Type labels
[ ] My changes are covered by tests

@dvadym Hey Vadym, is this what you had in mind in terms of implementation?

I'm not entirely clear on the use case.
When I self._budged_accountant.request_budget() per row, where each row is (by my guess) a partition pre-aggregation tuple - what weight should I use for the budget?
My intuition is that the weight for eps,delta should be proportional to the
In essence:
def filter_fn(row):
   budget = self._budget_accountant.request_budget(weight=?, use_eps=True, use_delta=True)
   partition_selector = create_partition_strategy("truncated_geometric", budget.eps, budget.delta, max_partitions)
   return partition_selector.should_keep(row[1].privacy_id_count)

I'm a bit unsure about what kind of computation there is, maybe it would be more helpful to define a SQL pseudo-code side by side with the expected python query? Is it something along the lines of

 SQL   PipelineDP

SELECT partition_key, accumulator
FROM (
    SELECT partition_key,
        accumulator(value) as accumulator,
        tsgd(budget(weight)) as tsgd
    FROM collection
    GROUP BY partition_key
)
WHERE tsgd.should_keep(accumulator.privacy_id)

groups = dp_engine._ops.group_by_key("partition_key")
groups = dp_engine._ops.map(groups,
   lambda row: row[0], accumulator(row[1])
)
groups = dp_engine._select_private_partitions(groups,
    max_partitions_contributed)

Sorry, I was not precise enough. request_budget() should be once per _select_private_partitions.
The idea is that (eps, delta) budget is per operation (in this case per partition selection) not per row, not per partition, so changing lines in your example:
budget = self._budget_accountant.request_budget(weight=1, use_eps=True, use_delta=True) # let's set weight = 1 by default
def filter_fn(row):
    partition_selector = create_partition_strategy("truncated_geometric",
          budget.eps, budget.delta, max_partitions)
    return partition_selector.should_keep(row[1].privacy_id_count)

Snippets of usage make sense. I like the idea of snippets. I'll try to add such snippets in future bug descriptions.
More details on accumulators: accumulators will be created in a chain of aggregations (for now 2 group_by_keys, but it may be changed in future), but conceptually it's the same as group_by_key/map in your example.
Does it answer your questions?

Started implementing tests. The draft is already there, but it's failing because it doesn't include the accumulators.
Working on converting the draft data into one with accumulators.


Add graphql gem

I wrote the rbs for the graphql gem.
I would like to use rbs for coding that uses the graphql gem, but it is noisy with many errors.
The rbs to be added in this PR aims to reduce this noise errors as much as possible and focus on the application part.
The graphql gem is a lot of code, but I extracted the code that is actually used, focusing on the generated code.

👣


Typo in comments

Hi,
In the leveldb source code, there are many places the word if is misspelled as iff.

That is likely shorthand for if and only if.

aha! That explains. @ashoemaker Thank you for the note.


docs: [#21] Describe how to configure and start YAAM.

Codecov Report
Base: 27.91% // Head: 27.91% // No change to project coverage :thumbsup:

Coverage data is based on head (3554a61) compared to base (0a3f5da).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage   27.91%   27.91%
=======================================
  Files           8        8
  Lines         437      437
=======================================
  Hits          122      122
  Misses        288      288
  Partials       27       27

Flag
Coverage Δ

unittests
27.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


device activation fails during auth0 login

Description
auth0 login exits with "login error: User is not authorized".
During the login flow in the browser I get "Activation Denied - We are not able to activate your device.".
I am not sure if this is actually an issue in the CLI, but I have no clue where to look for further information on why it fails.
Reproduction

Download latest auth0-cli release for Linux
run auth0 login
Press enter at "Press Enter to open the browser to log in or ^C to quit..."
Confirm "Device Confirmation" in firefox browser window.
Accept the "Authorize App" screen.

This leads to a screen with: Activation Denied - We are not able to activate your device.
And then the client of course says "User not authorized"
But it is unclear to me what to do, what I am missing, or what I have done wrong.

Detail the steps taken to reproduce this error, what was expected, and whether this issue can be reproduced consistently or if it is intermittent.
Where applicable, please include:

Code sample to reproduce the issue
Log files (redact/remove sensitive information)
Application settings (redact/remove sensitive information)
Screenshots

Environment

auth0 version 0.10.2 711dbbda2fc5ed92d3e7c1467e301d615e19397f
Linux
Firefox 90.0 (64-bit)

Something was screwed up in my browser state. Logging out of my auth0 account, put me in a state, where I could not login again on auth0.com until I cleared my browser state. (Login lead to the signup flow, where I could see myself logged in the top corner).


time: fix test flakiness on OpenBSD

The time tests seem flaky on OpenBSD for some reason.  E.g., recent-ish time.TestAfterQueuing failures on openbsd/amd64:
http://build.golang.org/log/7cf643d530ccbe39c97376ffdb2af64db66bcb5d
http://build.golang.org/log/10a9c8a1ffc2a088f48a12fdc9379f91a8bbc8b8
http://build.golang.org/log/702430fd8bf22805d19672d0795f6bc0d1395e6b
http://build.golang.org/log/cb50ea140b06232bdecb4c926134c9113f94e56a
Here's a time.TestReset failure on openbsd/amd64:
http://build.golang.org/log/26bb60d01823523470ffe47c7ed5fa9cdb280513
Flakiness has been seen on openbsd/386 in the past too; e.g.
http://build.golang.org/log/bd19f8590db8c7f317b3f968ac1af5126f5449cf
I've previously conjectured that this could be related to random scheduling delays interacting with repeated absolute<->relative timeout conversions in package runtime, but after measuring this seems unlikely (see https://groups.google.com/d/msg/golang-dev/AbSUgOucZyk/6ea0yP3ba1QJ).
It's possible this is actually an OpenBSD kernel issue.  One conjecture I have at the moment is that the tc_windup() function (http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/kern/kern_tc.c) is not multiprocessor safe, because it doesn't use proper memory barriers.  E.g., the final "timehands = th;" assignment might become visible to another thread before the modifications to the struct timehands's fields become visible.
Aside: I pointed this out privately to PHK in 2010, to which he responded "You are probably right, explicit memory barriers are probably called for." but FreeBSD still does not use memory barriers in tc_windup() either as far as I can tell: https://github.com/freebsd/freebsd/blob/master/sys/kern/kern_tc.c
NetBSD appears to have added explicit memory barriers back in 2007: http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/kern/kern_tc.c#rev1.20

Joel Sing tells me that the old openbsd-386-rootbsd builder was MP, but openbsd-amd64-rootbsd builders was SP.  Looking through old build.golang.org logs, I can't find any evidence of time.TimeAfterQueuing failing on openbsd-amd64-rootbsd (which aligns with my memories of thinking it was an openbsd/386-specific bug).
However, now openbsd-amd64-gce56 is MP too, and it's also exhibiting the bug.  That seems to support my theory that it's a memory barrier issue.
Following up with OpenBSD to see about fixing kern_tc.c.

We should have a Github issue label for kernel-bugs-in-various-operating-systems-that-go-has-revealed

Still jet lagged, so I dug into this some more early this morning.  On my X201s running OpenBSD -current, I was able to reproduce this issue.  I think the kern_tc.c race is still technically a bug, but it doesn't seem to be the root cause of this crash.
My way of easily reproducing currently is:
sed -i.tmp 's/const attempts = 3/const attempts = 1/' src/time/sleep_test.go
go test -c time
yes | head -n 10000 | GOMAXPROCS=4 xargs -P20 -n1 ./time.test -test.short=true -test.timeout=120s -test.run=TestAfterQueuing | grep -v '^PASS$'

(Notably, so far I've only repro'd with GOMAXPROCS>1, but it seems like the builders are using GOMAXPROCS=1.)
A couple things to explain:

With -test.short=true, TestAfterQueuing lowers "delta" to 20ms.

On OpenBSD (at least the arches supported by Go), the processor scheduler has a period of 10ms, whereas on Linux they're 1ms.  I.e., CPU intensive threads can potentially run for up to 10ms uninterrupted on OpenBSD.

When "go test std cmd" runs time.test, it's also busy compiling other packages/commands (i.e., CPU intensive work).

That leads to these consequences:

The first call to testAfterQueuing() tries to create a bunch of interleaved timers on lines 261--263.  If the test process is preempted for >=20ms while creating the timers, it's possible (e.g.) the final After(0 * delta) call occurred more than delta after the call to After(1 * delta).  I've seen this happen in ktrace/kdump output.

(Note: Subsequent retries, the global "slots" array is already sorted, so this cause goes away.  To trigger the failure below with "attempts = 1", move the sort.Ints() call earlier.)

Even when the queued timers are for non-decreasing intervals, there's a possibility that the "timerproc" Go routine gets delayed for >=20ms.  I've traced through timerproc to verify that even in this case, it processes the timers in the right order; but it's not guaranteed the "await" goroutines will be scheduled to execute in the same order.

(Interestingly, in a simplified test case, I'm able to reproduce this non-deterministic goroutine scheduling with GOMAXPROCS>1, but not with GOMAXPROCS=1.  I need to investigate more to find out why this is.)
Takeaway: I don't think "kernel-bug" is an entirely accurate here, but because of OpenBSD's kernel behavior, it might make sense to only set "delta = 20 * Millisecond" for GOOS != "openbsd".

Sigh, still flaking: http://build.golang.org/log/6ae361bdba9c95e35737fe173e291cd45959f1b3
(This was the build from 10f6d3031553 on build.golang.org for openbsd/386.)


Regression in routing on Python 3.11.0b2: ValueError: line 1-0 is not a valid range

After upgrading Python 3.11 to 3.11.0b2, the routing module seems to be broken. This is visible e.g. in werkzeug's tests. Example failure:
_____________________________________________ test_proxy_fix[ipv6 - port, host with port] _____________________________________________
tests/middleware/test_proxy_fix.py:183: in test_proxy_fix
    url_map = Map([Rule("/parrot", endpoint="parrot")])
.tox/py311/lib/python3.11/site-packages/werkzeug/routing.py:1505: in __init__
    self.add(rulefactory)
.tox/py311/lib/python3.11/site-packages/werkzeug/routing.py:1546: in add
    rule.bind(self)
.tox/py311/lib/python3.11/site-packages/werkzeug/routing.py:805: in bind
    self.compile()
.tox/py311/lib/python3.11/site-packages/werkzeug/routing.py:885: in compile
    self._build = self._compile_builder(False).__get__(self, None)
.tox/py311/lib/python3.11/site-packages/werkzeug/routing.py:1073: in _compile_builder
    code = compile(module, "<werkzeug routing>", "exec")
E   ValueError: line 1-0 is not a valid range

To reproduce:

Install Python 3.11.0b2.
tox -e py311

Environment:

Python version: 3.11.0b2
Werkzeug version: git main (bb21bf90b0b121e3ed45b9950b823e4b43a81fd8)

FWIU now you need to set end_lineno along with lineno. I'm not sure if it's intentional, though.

FWICS it's python/cpython@5893b5db98b38b17750c0572c7209774a5034898
Though pytest seems to be affected as well, so I don't really know how I managed to run tests yesterday.

Ah, there's more info on pytest-dev/pytest#10008. The tests can be run with --assert=plain to workaround pytest problem. FWICS upstream has also fixed this in CPython but I think that this particular issue is worth fixing in werkzeug too. I'll submit a PR shortly.


TF2OpenAPI Dockerfile + CloudBuild trigger

What this PR does / why we need it: Add TF2OpenAPI Dockerfile + CloudBuild trigger
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

This change is

/cc @ellis-bigelow
/cc @jiwang576

/lgtm
/approve
This will run whenever we push a tag (i.e. if  we cut a 0.1.1)


Welcome page should be excluded from quick open

Which folder(s) do you have open at that time? I don't see that file being picked up.

@chrmarti this was just https://github.com/Microsoft/vscode-smoketest-express.git, I was in the middle of the smoke test on the quick open step

Found on Linux while the Welcome page is open.

Can't reproduce anymore. Can you?


Recent Change to use bracket <> includes instead of "" includes breaks XCode compiles.

Hello,
I noticed there was a recent change to use bracket includes (i.e. #include <xt/...>) instead of regular quotes. This happens to break XCode9 unless you change a deprecated setting called "Always Search User Paths". <> includes are usually implementation defined anyway, and reserved for framework paths.
The GCC documentation, for example, specifies:

For the angle-bracket form #include , the preprocessor’s default behavior is to look only in the standard system directories. The exact search directory list depends on the target system, how GCC is configured, and where it is installed.

Is it possible to revert that change?
Thanks,
Ramy

@RamiHg thanks for your report!
I am curious how you install xtl to get this error. Do you install xtl in an installation prefix?

Hello,
No, I simply place xtl in my project's private include directories. I don't install any of the libraries (that's the beauty of header-only libraries).
Thanks!

No, I simply place xtl in my project's private include directories. I don't install any of the libraries (that's the beauty of header-only libraries).

Gotcha. We need to decide if this use case should be supported.
Is there a good reason to no install libraries?
For e.g. xtl:
cd build
mkdir build
cmake -D CMAKE_INSTALL_PREFIX=/path/to/prefix ..

will also place the cmake project configuration files in the right place etc...

I would say the biggest reason is self-containment. I.e. not having to worry about different versions of xtl on one's system. Each project that depends on xtl can host its own version. It makes working with dependencies slightly easier.

Not that I am opposed to using quotes, but "self containment" is generally not a good reason to vendor your dependencies in a project even when they are header-only, quite the opposite.
As soon as multiple project use heterogeneous versions of these dependencies, and need to link with each others, you will have all kinds of issues from binary incompatibility and one-definition rules breakages.
A generally used method is to have a non-system installation prefix where you install things, and packages of that installation prefix are not allowed to link outside. This is what tools like conda do with environments.


Increase the replica number of zookeeper for theia_clickhouse_test

Increase the replica number of zookeeper from 1 to 3 for theia_clickhouse_test to prevent disconnection between zookeeper and clickhouse.
Signed-off-by: Yun-Tang Hsu<EMAIL_ADDRESS>

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

May I learn about why do you choose to increase the ZK replica number instead of decrease the commit interval? It is a little bit strange to me that we need to deploy 3 ZK replicas to support only 1 ClickHouse replica. And I also notice the flow visibility e2e test is always stable which may indicate single-replica ZK can handle the flows when insertion rate is under some value? BTW, I'm not sure if increasing the ZK memory size would help. The default value is 5GB, but I think we can increase this default value if it helps.

May I learn about why do you choose to increase the ZK replica number instead of increase the commit interval? It is a little bit strange to me that we need to deploy 3 ZK replicas to support only 1 ClickHouse replica. And I also notice the flow visibility e2e test is always stable which may indicate single-replica ZK can handle the flows when insertion rate is under some value? BTW, I'm not sure if increasing the ZK memory size would help. The default value is 5GB, but I think we can increase this default value if it helps.

The problem is that, for some reason, jenkins-e2e test is not passed every time. And I notice that, it might because of the limited resource on jenkins' node. So the zookeeper will keep disconnecting when we run the test and making the table in readonly mode.
Error:      	Received unexpected error:         	            	code: 242, message: Table is in readonly mode (zookeeper path: /clickhouse/tables/0/default/.inner.flows_node_view_local)

May I learn about why do you choose to increase the ZK replica number instead of increase the commit interval? It is a little bit strange to me that we need to deploy 3 ZK replicas to support only 1 ClickHouse replica. And I also notice the flow visibility e2e test is always stable which may indicate single-replica ZK can handle the flows when insertion rate is under some value? BTW, I'm not sure if increasing the ZK memory size would help. The default value is 5GB, but I think we can increase this default value if it helps.

The problem is that, for some reason, jenkins-e2e test is not passed every time. And I notice that, it might because of the limited resource on jenkins' node. So the zookeeper will keep disconnecting when we run the test and making the table in readonly mode.
Error: Received unexpected error: code: 242, message: Table is in readonly mode (zookeeper path: /clickhouse/tables/0/default/.inner.flows_node_view_local)

Do you mean even if the insertion rate is low, we still get this error in ClickHouse CLI test? I'm just curious about why we do not see the similar failure in TestPolicyRecommendation or TestFlowVisibility, as I think these two tests should consume more resources than TestTheiaClickHouseStatusCommand. Both of these tests deploy extra components like Grafana and Spark, but the ZooKeeper has not been disconnected in these two tests.

Do you mean even if the insertion rate is low, we still get this error in ClickHouse CLI test? I'm just curious about why we do not see the similar failure in TestPolicyRecommendation or TestFlowVisibility, as I think these two tests should consume more resources than TestTheiaClickHouseStatusCommand. Both of these tests deploy extra components like Grafana and Spark, but the ZooKeeper has not been disconnected in these two tests.

I tried to use {recordPerCommit=4000, insertInterval=8} and still saw the issue sometimes. And the reason I used such high recordPerCommit is because the insertionRate in clickhouse is for all tables (not only for the 4 flows tables). It will have around 160 rows/s even there is not traffic sent.

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e


Create multiple jobs for multiquery requests.

[x] Add a new column to the database for "parent_job"
[ ] Return all jobs to client, indicate via field if a job is a "child" of a user run job.
[ ] Return all statuses in status requests
[ ] When returning results, format all reports and return as a zip (unless requesting unzipped)
[ ] When returning a report unzipped, return the "multi-query" result only, when returning zipped, zip all files.
[ ] Query endpoint returns all queries as json?  (maybe this should be an option?)

[ ] parent-id is an array as a job could appear in multiple other multi-query jobs.


operator.make: Fix broken deep-copy code generation

Operator sdk v1.0.0 has dropped code generation utilities in favour of
controller-gen.

Looked good, but doesn't work as it relies on controller-gen to be installed:
https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-737/1/pipeline


Creating concourse in wrong region

Hi,
I set AWS_DEFAULT_REGION=us-east-1, yet it created everything in "eu-west-1".
Shouldn't it create the bosh director and concourse in AWS_DEFAULT_REGION that I set?
I probably made some mistake somewhere. Can you please help me point in the right direction?
Thanks,
--ajay

Hi @akoranne,
You need to use the --region flag to set the region (see https://github.com/EngineerBetter/concourse-up/#region-configuration)
AWS_DEFAULT_REGION is used by terraform to authenticate with AWS — I agree this is confusing so I'll look into whether we can remove this requirement.
cheers,
Pete

Hi Pete,
Thank you for your reply.
Another question, is there a way to put in a username or at a minimum
provide a password (that I want) to Concourse? Where can I modify that?
I downloaded your project and not able to locate where the password is set.
If you can point me, I can change it to my password and rebuild the binary.
Please let me know. Thank you for your help!
With Regards,
--ajay
Ajay S. Koranne
(303) 887.2777
On Wed, Aug 16, 2017 at 10:09 AM, Peter Jones<EMAIL_ADDRESS>wrote:

Hi @akoranne https://github.com/akoranne,
You need to use the --region flag to set the region (see
https://github.com/EngineerBetter/concourse-up/#region-configuration)
AWS_DEFAULT_REGION is used by terraform to authenticate with AWS — I agree
this is confusing so I'll look into whether we can remove this requirement.
cheers,
Pete
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EngineerBetter/concourse-up/issues/8#issuecomment-322837834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJKlnyv99OoXKwp4tpaI0P-8eGWGdOm0ks5sYyIwgaJpZM4O5KOg
.

Hi @akoranne,
The concourse password is randomly generated here: https://github.com/EngineerBetter/concourse-up/blob/master/config/config.go#L60
You can also change the password by editing the config file on AWS. This will be in a bucket with a name like concourse-up-mydeployment-config in a file called config.json. Change the concourse_password field in this file, save it, and run concourse-up deploy again to update the password.

Thank you Pete!
With Regards,
--ajay
Ajay S. Koranne
(303) 887.2777
On Thu, Aug 24, 2017 at 7:24 AM, Peter Jones<EMAIL_ADDRESS>wrote:

Hi @akoranne https://github.com/akoranne,
The concourse password is randomly generated here: https://github.com/
EngineerBetter/concourse-up/blob/master/config/config.go#L60
You can also change the password by editing the config file on AWS. This
will be in a bucket with a name like concourse-up-mydeployment-config in
a file called config.json. Change the concourse_password field in this
file, save it, and run concourse-up deploy again to update the password.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EngineerBetter/concourse-up/issues/8#issuecomment-324650451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJKlnw3i-RB76H-EjXS_exxTyDxXW_tpks5sbYeAgaJpZM4O5KOg
.


Custom hook dependencies with auto()

I wrote a basic version of auto(). It can be used like this:
import { auto } from 'hooks.macro'

function MyComponent() {
  useSomeMacro(() => {
    console.log(foo)
  }, auto())
}

turns into
```javascript
import { auto } from 'hooks.macro'

function MyComponent() {
  useSomeMacro(() => {
    console.log(foo)
  }, [foo])
}

I used inline snapshot output to avoid wrestling with Jest. Will update that later.
What do you think?

Thank you! I love it!
Sorry if it not going to merge it straight away but I need to think a little about how well it works in the wild (by looking at actual hooks that accept a dependencies array).

That's perfectly okay. It's a good idea to not rush API additions.
useAsyncEffect would be a great candidate for using auto():
https://www.npmjs.com/package/use-async-effect
auto() as I implemented it would work well with this as dependencies are retrieved from all function expressions in the hook call. I will publish the updated package at @adrianhelvik/hooks.macro and test things out!

Hooks usage in the wild seems to be all over the place, and equal function references seems to be the bast pattern imo.


ChimeraOS 42 does not boot, even after fresh install

The new release of ChimeraOS completely messed up my setup. It tries to boot up in desktop mode the first time, and gets stuck on a gray screen. Sometimes I manage to get into a tty, but none of the sessions boots up. In 41 only the old Big Picture mode was working properly.
As I know the boot/partition setup could affect, I formatted the drive and reinstalled, to the same result with a fresh install.
System specs:
GTX 1070 Ti
Ryzen 5 2600
ASRock Fatal1ty B450

I too have this issue. Tried a fresh install on a "new" system some days ago, initially got stuck at "Downloading configuration updates" but got passed that but the screen went black/grey.
Tried updating my ASUS gaming laptop from v39 to 42 but the same issue appeared there too after reboot. Cant use the system any longer.
Specs:
ASUS H270i
Intel i5 7400
GTX 1070
16GB RAM
Laptop:
Ryzen 3750H
16GB RAM
GTX 1650 Ti

I ended up installing Pop OS, and configuring Steam with GEProton and to boot straight into Big Picture. Seems to be more reliable until further notice...

Have this same issue from February or March and can't install from new ISO. I move to Winesapos or other Linux.
check ChimeraOS Requirements

I too have this issue. Tried a fresh install on a "new" system some days ago, initially got stuck at "Downloading configuration updates" but got passed that but the screen went black/grey.
you must wait for ending process configuration updates, turn off display when screen flickering

I too have this issue. Tried a fresh install on a "new" system some days ago, initially got stuck at "Downloading configuration updates" but got passed that but the screen went black/grey.
you must wait for ending process configuration updates, turn off display when screen flickering

I've waited for about 24hours without any results, so there must be something else going on there.

I too have this issue. Tried a fresh install on a "new" system some days ago, initially got stuck at "Downloading configuration updates" but got passed that but the screen went black/grey.
you must wait for ending process configuration updates, turn off display when screen flickering

I've waited for about 24hours without any results, so there must be something else going on there.

you can use this:
https://github.com/ChimeraOS/install-media/releases/tag/2023-02-15_432f20f

I’ll try that thank you, but I thought that it just downloads the current version of chimera, but that February iso worked for you at least? Also downloaded the pre release iso of v43 so I should have all the tools needed hopefully.
Skickat från min mobil

Från: darkmasa @.>
Skickat: Wednesday, May 24, 2023 3:12:56 PM
Till: ChimeraOS/chimeraos @.>
Kopia: Northbane-arch @.>; Comment @.>
Ämne: Re: [ChimeraOS/chimeraos] ChimeraOS 42 does not boot, even after fresh install (Issue #619)
I too have this issue. Tried a fresh install on a "new" system some days ago, initially got stuck at "Downloading configuration updates" but got passed that but the screen went black/grey.
you must wait for ending process configuration updates, turn off display when screen flickering
I've waited for about 24hours without any results, so there must be something else going on there.
you can use this:
https://github.com/ChimeraOS/install-media/releases/tag/2023-02-15_432f20f
—
Reply to this email directly, view it on GitHubhttps://github.com/ChimeraOS/chimeraos/issues/619#issuecomment-1561124120, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A75G4B7V3EOG5NI22MVRXCLXHYCNRANCNFSM6AAAAAAYCV2J44.
You are receiving this because you commented.Message ID: @.***>

I’ll try that thank you, but I thought that it just downloads the current version of chimera, but that February iso worked for you at least? Also downloaded the pre release iso of v43 so I should have all the tools needed hopefully.

latest version not worked for me not have EFI have old
today Linux it's not free:(  garuda is good for gamer

Yeah that is a shame. But my PC does meet the sys req though.
I have tried Garuda but I felt it was too bloated.
Den ons 24 maj 2023 16:45darkmasa @.***> skrev:

I’ll try that thank you, but I thought that it just downloads the current
version of chimera, but that February iso worked for you at least? Also
downloaded the pre release iso of v43 so I should have all the tools needed
hopefully.
latest version not worked for me not have EFI have old
today Linux it's not free:( garuda is good for gamer
—
Reply to this email directly, view it on GitHub
https://github.com/ChimeraOS/chimeraos/issues/619#issuecomment-1561297474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A75G4BZ5CSB4HY4C6SOSRN3XHYNHFANCNFSM6AAAAAAYCV2J44
.
You are receiving this because you commented.Message ID:
@.***>

Garuda is have most of desktops. If you like Steamdeck desktop try Winesapos

ChimeraOS 43 may have fixed the anomalies you were experiencing there. Also, make sure your BIOS is up to date, as that was the problem with my install.

I have install on virtualbox for some oldest games

Didn’t fix it I’m afraid, still present in latest build even when I choose nightly in installer the problem is there.
Skickat från min mobil

Från: Alex @.>
Skickat: Friday, July 7, 2023 11:23:43 PM
Till: ChimeraOS/chimeraos @.>
Kopia: Northbane-arch @.>; Comment @.>
Ämne: Re: [ChimeraOS/chimeraos] ChimeraOS 42 does not boot, even after fresh install (Issue #619)
ChimeraOS 43 may have fixed the anomalies you were experiencing there. Also, make sure your BIOS is up to date, as that was the problem with my install.
—
Reply to this email directly, view it on GitHubhttps://github.com/ChimeraOS/chimeraos/issues/619#issuecomment-1626146991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A75G4B246KVQ5N2QZIKHUYTXPB457ANCNFSM6AAAAAAYCV2J44.
You are receiving this because you commented.Message ID: @.***>

worked for me ChimeraOS 43
boot from chimeraos-2023.02.15-x86_64
install on second drive
if not work install on SSD and manually boot
first boot time wait some minutes if black screen
uff too hot today for work:)

ChimeraOS, from what I can tell, is meant for installation on real hardware vs VMs. Glad to see things are working out on a fresh install.

I regulary not use on VMs but only one way for today, fresh install on SSD not working for me, can install only from old ISO file.
"legacy/bios not supported" in descripcion I see

Closing as it seems to be fixed

Still having issues. So not completed / fixed.
Skickat från min mobil

Från: Joaquín Ignacio Aramendía @.>
Skickat: Tuesday, July 25, 2023 1:26:35 PM
Till: ChimeraOS/chimeraos @.>
Kopia: Northbane-arch @.>; Comment @.>
Ämne: Re: [ChimeraOS/chimeraos] ChimeraOS 42 does not boot, even after fresh install (Issue #619)
Closed #619https://github.com/ChimeraOS/chimeraos/issues/619 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/ChimeraOS/chimeraos/issues/619#event-9910493233, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A75G4B6ENBXAYXK6TSYB5BTXR6UOXANCNFSM6AAAAAAYCV2J44.
You are receiving this because you commented.Message ID: @.***>

Hello I have change my motherboard to MSI mobo and I can install, but after install I cant boot Chimera

Probably due to requirement of AMD gpu I reckon.
Skickat från min mobil

Från: darkmasa @.>
Skickat: Sunday, June 16, 2024 11:20:16 AM
Till: ChimeraOS/chimeraos @.>
Kopia: Northbane-arch @.>; Comment @.>
Ämne: Re: [ChimeraOS/chimeraos] ChimeraOS 42 does not boot, even after fresh install (Issue #619)
Hello I have change my motherboard to MSI mobo and I can install, but after install I cant boot Chimera
—
Reply to this email directly, view it on GitHubhttps://github.com/ChimeraOS/chimeraos/issues/619#issuecomment-2171286292, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A75G4B5XKBVJM7DHBFL5QVDZHVKFBAVCNFSM6AAAAABJMN6SRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGI4DMMRZGI.
You are receiving this because you commented.Message ID: @.***>


fix: Cannot read properties of null (reading length) in stream-shift

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #2368

https://github.com/mafintosh/stream-shift/commit/a5636fe3b835e58049e86b36dc5b7824e16e82ee
https://github.com/mafintosh/duplexify/pull/40

Thanks for updating this @PatrickHeneise


Rename HttpRequest.IsSecure -> HttpRequest.IsHttps

Fixes https://github.com/aspnet/HttpAbstractions/issues/179
/cc @blowdart @Tratcher

:shipit:


Dupes, Saves and others

Can you make the temporary version of Saves, Demos and other pages that not ported yet, by loading default GMOD HTML version?

I'm not sure how this would work. For this I would need to take some parts of the HTML menu, and then somehow integrate them into this one. The HTML menu is a single system, if that is even possible, I would have to understand how to load a certain page, understand how to communicate with it in Lua.
I don't think there would be any sense in spending time on adding HTML back. Isn't it better just to write Lua code?
You can always use "menu_swap", if you need the missing features.

And by the way, there are only "Saves", "Demos" and Addon browsing (though you can do the same via Steam Workshop site) missing.


Horizonal slab placement even if shift is pressed

I accidentally put one vertical slab somehow, yet afterwards no matter what I do I just can't put a vertical one. It confuses me.

I don't understand. I can't interact with interactable blocks with slabs in my hand because I would instead put a vertical slab. Yet when it comes to not interactable blocks I would place a vertical slab while placing a horizonal one with shift held.


CREATE DOCUMENTATION UPDATE TEMPLATE

Title of the Pull Request

[x] Have you renamed the PR Title in a meaningful way?

Related Issue
Closes: #1024
Description
This pull request enhances the documentation to improve clarity and usability for new and existing contributors. Key changes include:

Reorganized ISSUE_TEMPLATE for better flow
Updated installation and setup instructions
Added a FAQ section to address common issues
Improved formatting and readability across pages

How Has This Been Tested? ⚙
Documentation changes were reviewed for clarity and tested by setting up a clean environment using the updated instructions. Feedback was also collected from new users to confirm improvements.
Screenshots 📷

Type of change
What sort of changes have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[x] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

@vishanurag the task has been completed. Kindly review the PR

@vishanurag the task has been completed. Kindly review the PR

@vishanurag


get_iplayer: Add version 3.25.0

Added get_iplayer

Thanks for correcting the above!

Why this is not configured to application directory and persited?

Do you suggest that during the installation we should add an environment variable to change the default preferences (see here) folder from %USERPROFILE%\.get_iplayer to ~\scoop\persist\get_iplayer?

@issaclin32 I do still want to merge this, just need to make another PR because this one was committed to the base branch rather than a 'patch' branch.

@issaclin32 I do still want to merge this, just need to make another PR because this one was committed to the base branch rather than a 'patch' branch.

I have sent a new PR, which involves the persist/profile mentioned by Ash. You can test if this works as you expected.


curve25519-java is GPLv3-licensed

When checking license compatibility, I found that you have org.whispersystems:curve25519-java:0.3.1 as dependency.
That library is released under GPLv3.
This means as long as you don't release your own code under GPLv3 too or switch to a curve implementation that is compatible with ASL, you are infringing copyrights.

Ar actually I'm not sure whether you are violating the GPL, but at least as long as you have a GPL-dependency you force anyone that wants to release a product with your lib and the dependency in it to release their stuff under GPL or they  would at least violate GPL otherwise, so if you stay with that dependency, you could as well release your lib under GPL to make it at least clear that currently a consumer of your lib has to release under GPL.

Björn, given that you’re not a lawyer, I’d suggest you refrain from using potentially threatening legal language when discussing these kinds of issues. I’m assuming good intent but telling people they’re “infringing copyrights” or “violating the GPL” is a really bad way to start a discussion like this.
First, the GPLv3’s trigger condition applies to the redistribution of code or the compiled artifacts based on code — specifically, it requires licensees to provide the original source code, retain the license and all copyright information, and allow usage of said code according to the license. I’m not redistributing Whisper Systems’ library, though. The source code is not in this repository, nor are any compiled artifacts. I am not violating the GPL, and I’d appreciate it if you did more homework before accusing me or others of such.
Second, I think you are correct that if you redistributed a copy of Whisper Systems’ library and did not meet the conditions of the GPLv3, you would be in violation of the license. That seems very much like your problem, however, and I suggest you consult a lawyer with experience in software licensing.
Third, “derivative work” is a specific term of legal art which does not mean what you think it means:

A “derivative work” is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications which, as a whole, represent an original work of authorship, is a “derivative work”.

This library is not a derivative work of Whisper Systems’ library.
Fourth, if you’d like to do the work of porting this library over to a Curve25519 implementation which has a more liberal license, I would accept that PR.

As it happens, Bouncy Castle added X25519 support in their last release, and porting it over was super simple. I’ve released 0.9.0, which only depends on Bouncy Castle.
That said, I really wish you’d opened an issue with your problem — that having a GPLv3-licensed dependency makes you nervous or the software you’re working on needs this — instead of half-baked legal analysis. Remember, when you open an issue like this you’re asking a human to take some time out of their day to do free work for you. It’s a lot easier and rewarding for me to do that when I know I’m helping another human with their day.

I'm really sorry if you felt attacked, I just wanted to inform you of the situation.
You are right, I'm no laywer, but your software depended on that curve library to work and thus it is discutable whether it is derivative work.
I still think it was a grey zone and at least it was confusing to your users if they think they depend on ASL2 software and indeed depend on GPLed software.
Anyway, I'm glad you could solve it that easily and reacted that fast.
Many thanks for your work.

To be clear: it is absolutely not a derivative work. There is no ambiguity on this whatsoever. As I mentioned before, that is a specific term in US IP law. It means something else.
Either way, I agree the situation was confusing and I’m happy I could quickly resolve it.


ehancemnet Refactor statistics

Proposed changes

Support for more expression type
Support derive with histogram
Use  StatisticRange to abstract to logic
Use Statistics rather than StatisDeriveResult

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.21 seconds
stream load tsv:          468 seconds loaded<PHONE_NUMBER>9 Bytes, about 152 MB/s
stream load json:         40 seconds loaded<PHONE_NUMBER> Bytes, about 56 MB/s
stream load orc:          76 seconds loaded<PHONE_NUMBER> Bytes, about 13 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230310051525_clickbench_pr_111936.html

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run p0

run buildall

run buildall

LGTM


0.0.8 -> 0.0.9

Issue link

#225
Types of changes
Other (please describe below if you select "Other")
Notes

Should we publish right now or wait for PR #231 merge?

Should we publish right now or wait for PR #231 merge?

Let’s publish now


The tab client leaves ubuntu terminals in raw mode

The tab client fails to disable raw mode on an Ubuntu desktop when it exits (default terminal, bash).

Closed by release #128 and release 0.3.2


[feature request] HTTPS support for secure authentication

Passing API authentication tokens via HTTP is not secure and some observability platforms such as Dynatrace require a HTTPS connection when using any kind of authentication.

Added in PR #73

@genegr I just got round to testing this now and I am successfully scraping metrics into Dynatrace with TLS. Thank you!


--url option is not working for plugin cli-plugin-e2e-cypress

Version
3.0.3
Node and OS info
node 8.9.4", npm 6.2.0", Windows 10 (Platform: win32 (10.0.17134))
Steps to reproduce

Set up a Vue CLI application that uses an external local dev server like IIS (not through npm run serve)
Add cypress e2e test supported by VueCLI
Add "test:e2e": "vue-cli-service test:e2e --url http://localhost:33333" to scripts in package.json
Run npm run test:e2e

What is expected?
Cypress to run as normal, testing http://localhost:33333
What is actually happening?
I receive the following error:
Error: Command failed: C:\Users\...\node_modules\cypress\bin\cypress open --config baseUrl=http://localhost:33333

Set up a Vue CLI application that uses an external local dev server like IIS (not through npm run serve)

So:

that server is already running on port 33333 while you start cypress
you tested it's reachable under that port
And that server is actually serving your app
...and it fails as described above,
while with a dev-server through `yarn serve, it works?

Thanks for the swift response,
More info...
I've tried the above on a different set-up: Mac OS, node 10.7.0, npm 6.1.0 with the same versions of Vue CLI and all the plugins... using a remote url through --url works, so I'll close the issue.

Well if this is a windows-related problem we might still be able to do something. But it might also be a Cypress bug.

To... I found something that may or may not be useful: after clearing out node_modules etc... I re-installed everything. I was served the following message:
Cypress 3.1.0 is already installed in C:\Users\...\AppData\Local\Cypress\Cache\3.1.0
The error from the open command that comes from node_modules looks like this:
Command failed: C:\Users\...\node_modules\cypress\bin\cypress open --config baseUrl=http://localhost:33333/
Around the time this stopped working I updated from:
"@vue/cli-plugin-e2e-cypress": "^3.0.0-rc.7",
To:
"@vue/cli-plugin-e2e-cypress": "^3.0.3",
A funny thing about this project, though it shouldn't have a bearing on Cypress, is: we're not using npm run serve. We're building to dist and watching src. This is because our templates are served by an IIS server through x-template script tags, and, quite honestly, because I can't get the devServer proxy to work.

This https://github.com/cypress-io/cypress/issues/5466 seems to be a root cause of the issue


fix: Could you add a feature request template as I want to suggest a workflow to add next :]

I can make a PR for it, if you'd like.

@andreped thanks! I'll assign this to you!
Here's one in another VeryGoodOpenSource repository that might serve as inspiration:

https://github.com/VeryGoodOpenSource/very_good_templates/blob/main/.github/ISSUE_TEMPLATE/feature_request.md

Here's one in another VeryGoodOpenSource repository that might serve as inspiration:

@alestiago That template is quite clean. What is stopping us from just using this one directly in this repo?

Nothing, feel free to add it yourself as is, that way we can get you as a contributor of the repository too 😉


GitLab and GitLab Enterprise

I forked and added a feature for adding GitLab and GLE. I can create a PR, but it would probably be just as easy for you to add. All that I did was copy the GitHubHandler and change the multiline selection code from #L1-L5 to #L1-5.
Let me know if you'd prefer that I submitted a PR.

Fantastic, thanks for that! I've successfully got it working with https://gitlab.com repositories. I'll try to add support for on-premise GitLab servers soon, and then publish a new version.

I've just published v1.7.0 to the marketplace which has support for both gitlab.com and GitLab Enterprise Edition.
Let me know if you have any problems with it.


The ‘temperature’ parameter in pb.LLMModel needs to be of type float

"""
A class providing an interface for various language models.

This class supports creating and interfacing with different language models, handling prompt engineering, and performing model inference.

Parameters:
-----------
model : str
    The name of the model to be used.
max_new_tokens : int, optional
    The maximum number of new tokens to be generated (default is 20).
temperature : float, optional
    The temperature for text generation (default is 0).
model_dir : str or None, optional
    The directory containing the model files (default is None).
system_prompt : str or None, optional
    The system prompt to be used (default is None).
openai_key : str or None, optional
    The OpenAI API key, if required (default is None).
sleep_time : int, optional
    The sleep time between inference calls (default is 3).

Hi, thanks for bringing this to us! We have fixed this issue in the latest version.


[REEF-647] Remove APIs deprecated since 0.12 from reef-wake

This addressed the issue by:

removing deprecated methods in MessagingTransportFactory and NettyMessagingTransport
which were deprecated since 0.12
removing deprecated methods in NameClient, NameLookupClient and NameServerImpl
which were deprecated earlier but rely on methods mentioned above

JIRA:
REEF-647
Pull Request:
Closes #

@tcNickolas I left a couple comments. Please let me know your thoughts.

I've updated code to keep MessagingTransportFactory constructor deprecated (until we can make it private)

This looks good. I'll test and merge.


Btn022-BtnIconFlat-817 commit

Looks good :+1:
Possible future refactor to merge #817 and #677 with icon prop.


wont run on server 2008

I developed on a Win 7 machine and all works well for testing. I made a setup and included the system*.dll files as well as the ESRI dll files.
Framework is installed and is the same version.
The app is a command line app
It immediately crashes. I have a console writeln at the very start and that doesnt come up either. I have tried x64 and x32 and different frameworks.
Any ideas?

Lance
On May 21, 2017, at 9:46 AM, Mark <notifications<EMAIL_ADDRESS>wrote:
I developed on a Win 7 machine and all works well for testing. I made a setup and included the system*.dll files as well as the ESRI dll files.
Framework is installed and is the same version.
The app is a command line app
It immediately crashes. I have a console writeln at the very start and that doesnt come up either. I have tried x64 and x32 and different frameworks.
Any ideas?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_file-2Dgeodatabase-2Dapi_issues_8&d=DwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=gKDhsz6_N8KnYkc7lQ4sXLmqXsuW-JiktyaDGCU2H-A&m=uCF2nt390SC71xSAvIHStfXP0BnG3qVuxm-qq3ETOYQ&s=ut9pzOw3qyfjGBiz4Iup0noQwK0IKOlRc5WIRI1DlcU&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AC2FJxW4RW5O1FkUhZ2GcWamL2bc0lFYks5r8GpqgaJpZM4Nhpxc&d=DwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=gKDhsz6_N8KnYkc7lQ4sXLmqXsuW-JiktyaDGCU2H-A&m=uCF2nt390SC71xSAvIHStfXP0BnG3qVuxm-qq3ETOYQ&s=aLbB7QyFvxQUzjwnvcnAIdED77Nx8qKaOp-ofy6EDok&e=.


Fix GitHub actions MacOS

Description
Looks like our issue with the MacOs tests evolved and now it doesn't randomly fail anymore. I have found that adding solves it
brew unlink gcc@8 gcc@9 (I hope it doesn't break anything down the line...).

Thanks Ferran! Would it be possible to add one or two comments explaining why these lines where added? With a link with relevant references if this is inspired from something else.

Thanks Ferran! Would it be possible to add one or two comments explaining why these lines where added? With a link with relevant references if this is inspired from something else.

Two relevant issues are:

brew upgrade fails for Python's 2to3 conflict
brew upgrade fails on gcc

Two relevant issues are:

brew upgrade fails for Python's 2to3 conflict
brew upgrade fails on gcc

Two relevant issues are:

brew upgrade fails for Python's 2to3 conflict
brew upgrade fails on gcc

I have now added the extra information. I only implemented the fix for gcc, which was basically what it was suggested by the error message. Let me know if I should add anything else.

Two relevant issues are:

brew upgrade fails for Python's 2to3 conflict
brew upgrade fails on gcc

I have now added the extra information. I only implemented the fix for gcc, which was basically what it was suggested by the error message. Let me know if I should add anything else.


Battery prompt in Termux: permission denied

I'm using Powerlevel9k as my theme in Zsh, with the battery indicator enabled. As I'm trying to make my dotfiles compatible with all my devices, I've stumbled upon the following error that's displayed every time I run zsh on my Android 7.0 tablet.
cat: can't open '/sys/class/power_supply/battery/capacity': Permission denied
cat: can't open '/sys/class/power_supply/battery/status': Permission denied

So it can't read from the sysfs due to permission issues. When I'm executing su -c cat /sys/class/power_supply/battery/capacity instead, it does display the capacity (well, remaining capacity) properly. Same goes for the other one. I've been able to narrow this down to lines 441 and 442 in powerlevel9k.zsh-theme, but changing local capacity=$(cat $bat/capacity) to local capacity=$(su -c cat $bat/capacity) (same goes for the second line) threw up different errors. This made it appear that this modification either caused other functions or variables in that file, or other sourced files to break. At this point I stopped investigating because it appeared that my Vim inside Termux threw in unwanted characters into these files during edits (which weren't saved - I exited with :qa!, but irritating nonetheless).
Basically I'd like powerlevel9k to be able to notice when Termux or Android is being used, and make the battery function either run as superuser, or leverage Termux:API's termux-battery-status (second one would be preferred) when that's the case.
Thanks in advance for looking into this!

Hi @toloveru !
Thanks for the report and the insights. I am opposed to add su to the commands.. The capacity should be a information available to all users. Whom does your capacity file belong? And which access is allowed on this file?
Does it work to access other files in /sys/class/?
I am not a fan of adding another method to get the battery status. This segment is already complicated enough.. Hoping for somebody with a good alternative..
Honestly Andoid is based on SELinux, which secures most accesses to system files. So it might happen on other segments as well.

Sorry for the late reply - the issue was indeed caused by SELinux. When setting the mode to permissive (su -c setenforce 0) it became possible to read out the file. So this issue is solved. Thanks a lot for pointing me in the right direction!


OpenTelemetry Ingresses

Add the ability to create ingresses for the Open Telemetry collectors in helm chart

thank you I am off my game today 😆 @prashant-shahi


Consider flattening the crate and dropping -preview status

As the std version of the Future trait heads toward stabilization, there are a couple questions we should revisit in terms of the organization of this crate:

First, we're close to the point where I think it'd make sense to move futures 0.1 to a different crate name (futures-old or some such), and put out a 0.3.0-beta release on futures proper.

Second, with 0.2 we split up the crate into a bunch of sub-crates to allow for easier iteration on the core APIs. At this point, though, we've had quite a bit of iteration and experience using these APIs with async/await/borrowing. We should consider re-flattening the crates, as well as the extension traits (especially AsyncRead{Ext}, AsyncWrite{Ext}). Doing so would streamline the user experience.

Thoughts?

By flattening do you mean merging all the crates into futures, or keeping some of the existing boundaries?
As far as I'm aware a major reason for the separate sub-crates was to allow semver breaking updates to parts of the API without causing pain in the ecosystem. Using sub-crates to denote this is also good for future compatibility with public/private dependencies, futures-core is intended to be stable long term so can be a public dependency, while futures-util (and by extension futures) can release relatively rapid breaking changes so should be kept as a private dependency (and existential types should make that trivial to do while still returning a combinator based future without a manually written wrapper).
It could make sense to reduce the number of crates drastically though. Maybe even as far as just 3 crates: futures-core as the almost 100% stable core, futures for everything that may require breaking changes and futures-test for testing specific utilities. Basically I guess that would be merging futures-io into futures-core (is it stable enough for this now?) and everything except futures-test directly into futures.
Migrating the uncontroversial functions from the extension traits onto the actual traits could make a lot of sense. I assume there's no major plan that would block this now, like waiting for GATs + existential types so that methods like Stream::next could return an associated type to allow implementors to provide a more optimized implementation instead of the default?
I assume part of the intention with having the separate levels of update schedule would be to migrate other utilities into the more stable crates over time. Taking the same example of moving StreamExt::next onto Stream directly, this will cause conflicts when users have both Stream::next and StreamExt::next in scope; so having a plan to deal with this seems necessary if the intention is to migrate functions after release.

Relevant discussion from back around 0.3.0-alpha.1: https://github.com/rust-lang-nursery/futures-rs/issues/1071

I still feel like channels are less stable than the traits in core, and that Sink is less stable than channels. I have basically no opinion about the futures vs. futures-util split.
in the end though, all I really care about is keeping a -util for fast iteration on new features and combinators that aren't subject to the same stability requirements as the Stream trait and channels.

There's been quite a bit of discussion since. -preview is going away soon, but the separate crates will remain for greater control over versioning.


Please invite me to the GitHub Community Organization

Name
Anas
Discord Username (if applicable)
Kadastross#1601
Additional Context
Over the past few months, I spent my time honing my skills in both frontend and backend development, made a few personal projects. Open Source can often be intimidating for newbies, that's why I would like to be a part of this inclusive community.

@Kadastross

Check your email or organisation page
Thank you for contribution 🙂
Please contribute in Unique-Github-Profiles

@Kadastross
Contribute in Unique-Github-Profiles


Add test for image from a remote source

sync_copy test tries to copy a system image from a remote https source
Signed-off-by: Rafael Garcia Ruiz<EMAIL_ADDRESS>

@Razaloc Can this be closed?

Sure


[Snyk] Upgrade miniflare from 2.5.0 to 2.9.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade miniflare from 2.5.0 to 2.9.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 15 versions ahead of your current version.
The recommended version was released 21 days ago, on 2022-09-16.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Server-side Request Forgery (SSRF) SNYK-JS-UNDICI-2980286
534/1000  Why? Has a fix available, CVSS 6.4
No Known Exploit

CRLF Injection SNYK-JS-UNDICI-2980276
534/1000  Why? Has a fix available, CVSS 6.4
No Known Exploit

CRLF Injection SNYK-JS-UNDICI-2953389
534/1000  Why? Has a fix available, CVSS 6.4
Proof of Concept

Improper Certificate Validation SNYK-JS-UNDICI-2928996
534/1000  Why? Has a fix available, CVSS 6.4
Proof of Concept

Information Exposure SNYK-JS-UNDICI-2957529
534/1000  Why? Has a fix available, CVSS 6.4
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: miniflare

2.9.0 - 2022-09-16Features

💾 Add support for D1. Closes issue #277, thanks @ geelen for the PR. Docs coming soon™... 👀

🚪 Add getMiniflareDurableObjectState() and runWithMiniflareDurableObjectGates() functions to the Jest/Vitest environments. This allows you to construct and call instance methods of Durable Objects directly, without having to fetch through a stub. Closes issue #157, thanks @ jorroll.
http://localhost/"))
);
expect(await res.text()).toBe("4");">// Durable Object class, would probably come from an import
class Counter {
constructor(state) {
this.storage = state.storage;
}
async fetch() {
const count = ((await this.storage.get("count")) ?? 0) + 1;
void this.storage.put("count", count);
return new Response(String(count));
}
}
const env = getMiniflareBindings();
// Use standard Durable Object bindings to generate IDs
const id = env.COUNTER.newUniqueId();
// Get DurableObjectState, and seed data
const state = await getMiniflareDurableObjectState(id);
await state.storage.put("count", 3);
// Construct object directly
const object = new Counter(state, env);
// Call instance method directly, closing input gate,
// and waiting for output gate to open
const res = await runWithMiniflareDurableObjectGates(state, () =>
object.fetch(new Request("http://localhost/"))
);
expect(await res.text()).toBe("4");

🥷 Don't construct corresponding Durable Object instance when calling Miniflare#getDurableObjectStorage(). This allows you to seed data before your Durable Object's constructor is invoked. Closes issue #300, thanks @ spigaz.

☑ Add support for WebSocket#readyState and WebSocket.READY_STATE_{CONNECTING,OPEN,CLOSING,CLOSED} constants. Note these constant names intentionally deviate from the spec to match the Workers runtime.

📜 Add persistent history to the REPL. This respects the MINIFLARE_REPL_HISTORY, MINIFLARE_REPL_HISTORY_SIZE, and MINIFLARE_REPL_MODE environment variables based on Node's.

💵 Add support for Range, If-Modified-Since and If-None-Match headers on Requests to Cache#match. Closes issue #246.

Fixes

Don't wait for waitUntil Promises to resolve before opening WebSocket connections
Allow WebSockets to be close()d on receiving a close event. Closes issue #331, thanks @ awthwathje.
Ensure calling WebSocket#close() before returning a WebSocket response sends the correct close code and reason.
Fix delivery of incoming WebSocket error events
Ensure only scheduled Durable Object alarms are flushed. Previously, flushing all alarms would attempt to execute the alarm handler of every constructed Durable Object instance, even if that instance hadn't scheduled an alarm, or didn't have an alarm handler.
Delay scheduled missed alarms. Previously, if Durable Object persistence was enabled, and an alarm should've executed when Miniflare wasn't running, Miniflare may have crashed on startup. Closes issue #359, thanks @ AlCalzone.
Allow empty-chunk writes to IdentityTransformStream. Closes issue #374, thanks @ cdloh.
Don't hang when fetching from Durable Objects with fake-timers installed. Closes issue #190, thanks @ vlovich.
Match unimplemented Request/Response properties with the Workers runtime. Specifically, throw unimplemented errors when attempting to access Request#{context,mode,credentials,integrity,cache} and Response#{type,useFinalUrl}.
Discard Content-Length: NaN headers as a temporary workaround until cloudflare/kv-asset-handler#295 is released. Closes honojs/hono#520, thanks @ Cherry.
Return byte streams when tee()ing byte streams to match the behaviour of the Workers runtime. Closes issues #317 and #375.
Throw TypeError when calling Fetcher#fetch with an illegal this to match the behaviour of the Workers runtime.

2.9.0-next.1 - 2022-09-10

2.8.2 - 2022-09-10Fixes

Allow WebSocket client connection errors to be caught. Closes issue #229, thanks @ viorel-d.
Return Responses with immutable headers from cache.matchs. Closes issue #365, thanks @ AlCalzone.
Ensure request.cf.clientAcceptEncoding is always a string. Closes issue #362, thanks @ GregBrimble.

2.8.2-d1.0 - 2022-09-12

2.8.1 - 2022-09-08Fixes

Add missing @ miniflare/queues dependencies. Closes issue #360, thanks @ AlCalzone for the PR.
Fix support for queues in Jest/Vitest testing environments

2.8.0 - 2022-09-07Features

⚡ Add custom Vitest testing environment. This behaves almost identically to the Jest environment. However, isolated storage must be installed manually in each test file. Call the setupMiniflareIsolatedStorage() global function and use the returned describe function instead of the regular describe/suite functions imported from vitest. See ⚡ Vitest Environment for more details.
🌐 Populate Workers Sites __STATIC_CONTENT_MANIFEST with site files instead of an empty object. Miniflare will still disable caching of Workers Sites files to ensure the most up-to-date files are always returned. Closes issues #233, #326 and cloudflare/wrangler2#1632. Thanks @ ItalyPaleAle, @ Skye-31, @ CraigglesO, @ Hexstream and @ PolariTOON.
⏱ Add global getMiniflareWaitUntil() method and ExecutionContext class to the Jest and Vitest testing environments. This can be used to await the results of waitUntiled Promises in tests. See 🤹 Jest Environment and ⚡ Vitest Environment for more details. Closes issue #202, thanks @ jamesarosen and @ CraigglesO for the PR.
⏳ Match Web Streams implementations with Workers runtime, closes issue #168, thanks @ leviwolfe:

Add support for the non-standard IdentityTransformStream class.
Add support for the streams_enable_constructors compatibility flag. ReadableStream and WritableStream constructors will throw unless this flag is enabled. ReadableByteStreamController, ReadableStreamBYOBRequest, ReadableStreamDefaultController and WritableStreamDefaultController will only be included in the sandbox if this flag is enabled.
Add support for the transformstream_enable_standard_constructor compatibility flag. TransformStream will behave like IdentityTransformStream if this isn't enabled, ignoring custom transformers. If transformstream_enable_standard_constructor is set, but streams_enable_constructors isn't, the TransformStream constructor will throw. TransformStreamDefaultController will only be included in the sandbox if both flags are enabled.
Add support for BYOB reads to the non-standard FixedLengthStream class.

🇬🇧 Add support for Queues. Docs coming soon™... 👀
🙉 Allow calls to addEventListener, removeEventListener and dispatchEvent in modules mode. Please note, calling addEventListener with a special event type (e.g. fetch, scheduled) will log a warning prompting you to use the export default syntax. Closes issue #207, thanks @ Electroid.
🍟 Add experimental and highly-inaccurate request CPU time measurements. These are not representative of deployed worker performance, should only be used for relative comparisons, and may be removed in the future. Enable measurements with the --inaccurate-cpu/[miniflare] inaccurate_cpu/inaccurateCpu option. Closes issue #161. Thanks @ alexandernst and @ y21.
🦄 Automatically enable watch mode when live_reload = true is set in wrangler.toml.

Fixes

Return Responses with immutable headers from fetches to Durable Objects and service bindings. Closes issue #346, thanks @ Cherry.
Fix CryptoKey#algorithm.name property of NODE-ED25519 keys. Closes issue panva/jose#446, thanks @ ItalyPaleAle.
Disable automatic insertion of Sec-WebSocket-Protocol header. Closes issue #179, thanks @ aboodman and @ grgbkr.
Return Content-Length header is custom Content-Encoding is specified. Closes issue #313, thanks @ vlovich.
Require "automatic" instead of "auto" for the encodeBody option when constructing Requests. Closes issue #357, thanks @ GregBrimble for the PR.
Remove request.cf.cacheTtl/request.cf.cacheTtlByStatus support from the Cache API to match the behaviour of the Workers runtime, which only supports request.cf.cacheKey.

2.7.1 - 2022-08-22 Read more

2.7.0 - 2022-08-19 Read more

2.6.0 - 2022-07-09 Read more

2.6.0-d1.5 - 2022-08-12

2.6.0-d1.4 - 2022-08-09

2.6.0-d1.3 - 2022-08-04

2.6.0-d1.2 - 2022-07-29

2.6.0-d1.1 - 2022-06-29

2.5.1 - 2022-06-19 Read more

2.5.0 - 2022-05-27

    from miniflare GitHub release notes

Commit messages

Package name: miniflare

1c8b804 Bump versions to `2.9.0`, update `CHANGELOG.md` and docs
974c7c2 Bump versions to `2.9.0`, update `CHANGELOG.md` and docs
a98e0f5 De-static-ify D1 `Statement` class, and update `README.md`
6bace6b D1 beta support (#329)
64e1b26 Add `runWithMiniflareDurableObjectGates` for test environments
9a62a02 Throw `TypeError` on `Fetcher#fetch` illegal invocation
31792ba Return byte streams when `tee()`ing byte streams, closes #317
72e5edc Upgrade `jest-environment-miniflare` tests to Jest 29
4da17bb Unexport `parseETag`
932b537 Add support for `If-None-Match` to `Cache#match`, closes #246
38b821d Add support for `If-Modified-Since` to `Cache#match`, ref #246
70a7f13 Use `ReadableStream` for `multipart/byteranges` encoding
9326118 Add support for `Range` requests to `Cache#match`, ref #246
5ba38e8 Discard `Content-Length: NaN` header, closes honojs/hono#520
de5adc8 Match unimplemented `Request`/`Response` properties with runtime
2ca8115 Add persistent history to REPL, closes #304
cdaa62b Add `getMiniflareDurableObjectState()` to environments, closes #157
765e543 Fix typo in `IdentityTransformStream` comment
e5fe3bb Don't hang fetching Durable Object with fake-timers, closes #190
d36f399 Allow empty chunk writes to `IdentityTransformStream`, closes #374
d606d68 Delay scheduling missed alarms until `beforeReload()`, closes #359
9872c6b Only flush scheduled Durable Object alarms
6299d1d Don't construct object on `getDurableObjectStorage`, closes #300
3c9763b Make `StorageFactory#storage` synchronous

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Duplicate of #57


SEO for Next.js-Drupal

Hi,
I would like to ask,if is this possible to use standard drupal SEO modules with Next.js.
For example,the modules Metatag,Pathauto,XML Sitemap,SEO Checklist.
Any help would be great,
Thanks

You can use the metatag module and pull the meta information using JSON:API. Pathauto works with next-drupal as well.
As for XML Sitemap, there are a few ways you can handle this. You can generate the sitemap on Drupal and point your Next.js site to it.

@shadcn Thank you very much

Hey @shadcn,
Sorry to comment on a closed issue but can you please elaborate a little on how to go about this?
I have the metatag module installed. when I console.log my node in Next.js the field_meta_tags & metatag are null

This is from the Drupal edit node page

My Next.js site uses a combination of the Umami & Marketing examples
In pages/[[...slug]].jsx
const PageRouter = ({ global, node }) => {
  return (
    <Layout meta={{ title: node.title }} global={global} slug={node.slug}>
      <Node node={node} />
    </Layout>
  );
};

layout.jsx
<Meta {...meta} />

meta.jsx
    <Head>
      <link
        rel="canonical"
        href={absoluteURL(router.asPath !== "/" ? router.asPath : "")}
      />
      <title>{`${title} | ${siteConfig.name}`}</title>
      <meta name="description" content={description || siteConfig.slogan} />
      <meta
        property="og:image"
        content={`${siteConfig.baseUrl}/images/meta.jpg`}
      />
      <meta property="og:image:width" content="800" />
      <meta property="og:image:height" content="600" />
    </Head>
    ```


Feature/hide user info behind show button

The user's personal data is now hidden by default, and can be shown through the click of a button on their personal data page. These changes will propably create conflicts with #164 but should be fairly easy to iron out. So just don't merge the two pull requests to main at the same time.

The user's personal data is now hidden behind a show/hide button, with working pagination. As of now the contents are hidden again if the user reverts back to the first page of data, but are easy to find again with one click of a button.


Android Tv Support

It runs great on my android tv. Only 2 features are missing.  A launcher would be nice ( im am forced to start over installed apps) and  controller support for the loader screen.

Oh yeah the controller support thing is fair. I'll see if it's not too bad to do and work it in at some point.
As for the launcher thing, are you referring to it not being considered a game for stuff like the Game Launcher, or something else?

It just not shows up as a tv app. I think there have one or two variables to be set. Tv apps have some specific icon i think they appear as a reactangle with more width then height and not square.  I can start the app with a sideload launcher or go to the list of installed apps and open it from there. But is not appears on the "home" screen. For that reason i cant launch it normaly. No deal breaker but is unconvenient.

If the controller thing is to time consuming i would love to see  some sort of auto boot as a replacement. If there are no activity for x seconds launch the last used option.

Gotcha, I'll see what I can do next time i update the app.

I think I've implemented this, so expect to see it in a day or two.

Sorry to respond to a closed issue, but I just tried out the new APK with this support. The app still does not appear in my app lists, even with a fresh install. On top of that, I am unable to login since the keyboard does not seem to function. Either with touch screen or the controller
(pics in album because github has a 10mb file limit)
https://imgur.com/a/7Ic0eQm

Oh yeah, I forgot that part of the request. I just fixed it not showing up in the app list, but I can't seem to replicate the keyboard thing. On my android TV emulator at least, I can fully log in using a TV remote's controls (although it's a bit janky; you hit a button to make it pop up, then can enter your username, then have to hit next for password, and then next works for login; I have no idea if there's a way to register from the TV)

On my TV everything works except of the app apearing in the app list.
I can log in, everything with my remote. I could even play pokemon with the remote (if arrows and a key is enough). With the controller the cursor is not moving in the keyboard section (Login).  Everything else works great.

Die apk from zips works for me thank you

Ironically I'm unable to install that debug APK. I get an "error parsing the package" when attempting to install the APK.
I've seen a few others reporting this error from installing the latest release apk as well in the offline-modding discord channel.

I can confirm that the app now appears on the homescreen, thank you! As for the keyboard what do you mean by remote? Unfortunately, I don't have access to another way to control the system to use the keyboard besides the touchscreen itself. Unless you mean another controller like a Bluetooth xbox controller?

So I actually found a bluetooth controller to try and connect(xbox one if it matters)  and that lets me somewhat use the keyboard for the sign in screen.
I can use the A button to select whatever is selected by default when the keyboard shows up(in this case Q), and also use B to erase whatever I just entered. However, I still can not scroll across the keyboard to select different letters.
Sorry for the spam, I figured this extra information could be useful!

@ItsDeidara

I can confirm that the app now appears on the homescreen, thank you! As for the keyboard what do you mean by remote?

im using the nvidia shield. so i am using the nvidia shield remote.  i have also connected a xbox controller.
the remote is not supporting to go back "press b" or going into the settings menu "start? / select?"
with the xbox controller i cant control the onscreen keyboard. this stuff i do with the nvidia shield remote.
if you dont have a remote you may could connect a bluetooth keyboard?  for mouse control on tv i use "Bluetooth Keyboard & Mouse"  on my android phone.  For Keyboard you may have to pay.
To be honest.  on the nvidia shield its a laggy experience.  i have a pc connected with chimeraos i mostly use (pokerouge win exe with proton). but i dont always to boot the pc to just play 15 minutes pokerouge.  so the nvidia shield works well for that situation. it only starts lagging after some time which i belive is maybe a ram issue caused by webkit?


Superseded by #414.

          Superseded by #414.

Originally posted by @dependabot[bot] in https://github.com/ossf/allstar/issues/412#issuecomment-1553102175

@Thank jeffmendoza


A few small improvements to async slicing

Description
This contains a few small improvements and bug fixes related to the currently experimental async slicing.

Only slice visible layers. This avoids unnecessary work when a layer is not visible. When it changes to visible, it will be resliced.
Disconnect slice observers on shutdown. This removes the cyclic dependency that may have been causing some of the teardown errors in test_async_slicing.
Store weak references to layers. This helps to avoid unnecessary memory consumption and also avoids post-slicing updates if the layer is gone.

I grouped these together to avoid PR management overhead, but it's easy to split them up if desired.

I've pushed a small commit to try to fix CI.

The mypy error is unrelated and on main as well. I sent a PR to fix main:
https://github.com/napari/napari/pull/6088

Thanks for the reviews!


Add -v flag

At the moment, there's no easy way to get the version from an installed Perlang runtime. The following command should work as expected:
$ perlang -v
Unhandled exception. System.IO.FileNotFoundException: Could not find file '/home/per/.perlang/bin/-v'.
File name: '/home/per/.perlang/bin/-v'
   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
   at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
   at System.IO.File.ReadAllBytes(String path)
   at Perlang.ConsoleApp.Program.RunFile(String path)
   at Perlang.ConsoleApp.Program.Main(String[] args)
Aborted

MRI Ruby behavior
$ ruby -v
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]

Python behavior
$ python -V
Python 2.7.16

As of #32, the version number (including git revision) is easily accessible so we should just add the missing -v flag and be able to close this issue.

Fixed in #36, closing.

It would be nice to get these two things as well:

Support for -v. I am currently not aware on how to get this done with System.CommandLine.
Adding the build date in the output as well. Again, unsure on how to get this done.

Support for -v. I am currently not aware on how to get this done with System.CommandLine.

This has subsequently been accomplished (the flag is now -V or --version). :tada:

Adding the build date in the output as well. Again, unsure on how to get this done.

This is actually not done. But we have the git commit (built from git commit 44485bb), so perhaps that's good enough for now.


IBM/sarama Go client library for Apache Kafka support

Depends on branch mk_upload (another pull request)