NOTICK - Adding keys and timestamp for genesis

Added in keys for validators from sheet.
Updated chainspec.toml values from updates to production/chainspec.toml.
Set timestamp to 2020-09-18 18:00 UTC (2PM EST, 11AM PST) today.

bors r+

bors r+

bors r+


[Lecture 9] Calculating Output feature size

If I calculated the output feature size and the decimal point comes out, how do I deal with the decimal point?

In my opinion, If the result is a decimal, it seems that you should use flooring to discard the decimal part and keep only the integer part.

@junehyeok129 @sumin819 Thank you for the comment and the correct answer:)


[PLAT-8994] Support service workers

Goal
To support the ability to use Bugsnag within a service worker, particularly use cases such as background scripts in chrome extensions
Design
The browser notifier is bundled with many plugins which are either unnecessary, or would need to be rewritten to support service workers, so a new simple worker notifier provides the opportunity to define worker related features off of a stable base
Changeset

new web-worker notifier package
new delivery-fetch package, consumed by the web-worker notifier

Testing

Added unit tests for delivery-fetch and web-worker packages
Added end to end tests for web-worker package

Apologies, got a lot of commits on this one now - but will squash when I merge into the integration branch


Create new header bar partials for easier customization

Seems common to tweak the header bar (header.blade.php).
Probably worth splitting this down to extra components, with at least:

View for existing links/buttons.
Empty view at the start of existing links/button specifically for customization.

This would need test to cover like existing customization-only views.

Could maybe split out logo and search. Not sure there's much desire, but would allow easier moving/removal within header.blade.php overrides.

Already exacted profile menu in b90033a73032da8657f1bd3ec3687aa4426d8cc1, might be worth thinking through organisation though, rather than bloating common.

Changes made in d5a3bdb7aa7876f667256fb3e0d36ef46940adf9.
New header link extension view at layouts/parts/header-links-start.blade.php.
While not a change to our official supported API, might be polite to warn about changes to the common/header.blade.php (Moved and changed) in update notes since this may have been a common customization.


ipv6PrefixCheck — Failure to trigger update after router restart

I have seen two situations were a restart of the router (FRITZ!Box) did not lead to the updated IPv6 prefix being noticed.

After a power outage (affecting the router but not the host running the script).
After a reboot of the FRITZ!Box (due to a software update).

Effectively both cases are similar in that the router suddenly disappears and when it reappears it reconnects to the Internet receiving new IPs and IPv6 prefix. On OpenBSD this will lead to two public IPv6 addresses being present, one with the old IPv6 prefix and another with the new one. The old IPv6 address will be non-functional of course as it will not be routed to the WAN interface of our router. The timeouts before this situation resolves itself can be on the order of 2 hours in my setup.
This situation may cause the script to fail to recognise that the actual IPv6 prefix has changed, until the lifetime of the old public IPv6 address has been reached and the address is removed from the interface.

Determining the current public IPv6 prefix may be accomplished more easily by asking slaacd(8) for the advertised prefix using slaacctl(8) instead of parsing routing tables:
slaacctl show interface 'em0'|grep 'prefix:'|grep -v 'prefix: fd'

(Get current slaacd(8) data for interface em0, extract the lines containing the word prefix:, then filter out those that contain the ULA prefix. Extracting the actual prefix is then fairly easy.)
This yields output similar to this:
		prefix: 2001:dead:beaf:42::/64

This method needs to be explored further to determine if it consistently works …
From there it would be very easy to determine the public IPv6 address of the host on the given interface.


Enhancing expandable headers

What are you changing in this pull request and why?
Enhances the collapsible header feature:

Changes the icon from "+" to ">"
Moves the icon to the front of the text
Changes the icon color to orange (to match existing expandables)
Alters the description text

Checklist

[ ] I have reviewed the Content style guide so my content adheres to these guidelines.
[ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

No longer need this feature


Linux / AUR

Is it possible to add this to the AUR so it's possible to use on arch linux based distributions?

@LilKurisuu It is python package so it needs to be installed by pip3. You can easily install it by the command in the Installation section of README.md

Arch does not support pip.

@authorisation Arch is a Linux, Linux supports pip. If Arch supports python then it should support pip.

Arch has it's own package manager (pacman) and is incompatible with pip. The AUR is a great place for something like this.
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try 'pacman -S
    python-xyz', where xyz is the package you are trying to
    install.

    If you wish to install a non-Arch-packaged Python package,
    create a virtual environment using 'python -m venv path/to/venv'.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip.

    If you wish to install a non-Arch packaged Python application,
    it may be easiest to use 'pipx install xyz', which will manage a
    virtual environment for you. Make sure you have python-pipx
    installed via pacman.

P.S. No, thanks.

@authorisation I don't know how to add it to AUR, I have no clue what is AUR and honestly I don't want to deal with Arch Linux in general. So, I'll wait for someone to add it there or for Arch Linux to add pip support.

That's fine but I would keep the issue open in that case.


Remove parsers.csv_file

CSVReader wraps csv into an iterator and CSVWriter does some kind of buffering thing. But the reader could just use NumPy's genfromtxt or Pandas's read_csv or even the plain csv. Everything that uses CSVWriter also appears to write everything entirely, so it can just use csv directly.

I think these are all the instances where CSVReader and CSVWriter are used:

find_accession.py
genome_extractor.py

After deleting phage_file and phage_file_2_2_30, I don't think CSVWriter is needed at all.
So the two parts to this issue:

Delete [parsers/csv_file].(https://github.com/phageParser/phageParser/blob/4e98ef123edacb6b33b255c3a1d6f7dc6ef1846a/parsers/csv_file.py)
Change find_accession.py and genome_extractor.py to use the csv module for the reader object.

looks like genome_extractor (now getgenomes) is ok,
and find_accession would just need this line changed to csv.reader(blast_file, dialect=excel_tab)

@morrme sounds good - there's also this line in genome_extractor as well as the import statements in both files.

@QuLogic @mbonsma I created PR #146 with my fix.


Add Contiguous Integration (CI)

As a developer
I need to test my code whenever I make a pull request
So that ensure only good code gets deployed and used by others (e.g., my teammates)
Details and Assumptions

We will use GitHub Actions for CI
Local tests should still be run before PR
CI will help enforce 95% tests code coverage

Acceptance Criteria
Given CI set up with GitHub Actions
When I make a pull request
Then GitHub Actions will run all tests and prevent PR with failed tests

To do with #26


Modify gevent wsgi and libev dependencies

The goal of this PR is to migrate from libevent to libev and from gevent's wsgi module to pywsgi .

Addresses #649

+1, this worked for me when installing locally


Upgrade Prettier to v3

Summary
This is #14108 without changing the version used by our packages - just the version of prettier used to format the jest code base

Test plan
Green CI

Apparently inline snapshots fail to update if Prettier v3 is installed. The existing once work fine until they are passing, only jest -u fails. See https://github.com/jestjs/jest/issues/14305#issuecomment-1627221402
It might be good to fix the problem before merging this PR. Seems like this is similar to what eslint-plugin-prettier was facing: TypeError: prettier.resolveConfig.sync is not a function.

Hmm, I was hoping we were still using prettier v2 with this. Might need to add a dev dep to jest-config or something? Or set prettierPath in our config

Played around some more with using @prettier/sync (see latest commit 536a80a (#14311)), but since we use a custom parser, I don't think we can use it: https://github.com/prettier/prettier-synchronized/issues/4#issuecomment-1649355749


Flag that lists functions to inline

Currently, the inline flag (--wp-inline) will inline all of the function calls. We should have a flag that lists which functions we want to inline, ex: --wp-inline-funcs=food,bar,baz.
When the inline flag is set, the wp plugin creates an inline_env which passes in spec_inline as the default function spec: https://github.com/draperlaboratory/cbat_tools/blob/master/wp/lib/bap_wp/src/precondition.ml#L464-L475
When the environment is created, it initializes a handler for each sub in the program. If the subroutine doesn't match the prerequisites for spec_verifier_error, spec_verifier_assume, or spec_verifier_nondet, it will be mapped to spec_inline as seen in https://github.com/draperlaboratory/cbat_tools/blob/master/wp/lib/bap_wp/src/environment.ml#L114-L122
At this point, we can specify exactly which functions we want to be inlined and map other specs to the remaining functions.
BAP flags can be set in the wp.ml plugin file: https://github.com/draperlaboratory/cbat_tools/blob/master/wp/plugin/wp.ml#L142-L161

Handled in #64


Handled the recent update to conda-forge for testing, perhaps relating to GEOS update.

Relates to the thing identified in https://github.com/SciTools/iris/pull/2890#issuecomment-342498165
Requires https://github.com/SciTools/test-images-scitools/pull/9 for this to go green.
Requires https://github.com/SciTools/test-iris-imagehash/pull/12 for this to go green.

@pelson Awesome, thanks 👍


issue 93 remove chartjs code

Issue 93: removing chart.js code
Remove chart.js from package.json, package-lock.json, and yarn.lock

Hey @sarabpj @zjrosen1!
Even after this PR, src/screens/ModelPage/ModelPage.js still has:
https://github.com/covid-projections/covid-projections/blob/2e4033958c29e8ae53e822f0ccac7c65bf816dc2/src/screens/ModelPage/ModelPage.js#L3
And I can't run this site because I get:

Already fixed in develop

ffddf6b7fdb26282f19d176cf8682214a690b363 fixes this

@szhu  sorry about that @zjrosen1 thank you!


Fix for issue #44

Commit based on PR #50 that was never merged.
Added code to incorporate functionality for attachments with signer
requests

@martinytodorov - please verify updates.

Amended the commit and re-pushed @martinytodorov

Hey @oconnor-sn I checked out the branch on my machine and made a few tests. I realized that there are couple of more things that need to be fixed.

You added the attachments to the function _send_signature_request_with_template. You should remove it from there.
Although you added attachments to _send_signature_request, you are not using them in the payload for the request.

Here's some tips you should follow when opening the PRs:

Always test you changes. If you are adding attachments to signature_request/send and signature_request/create_embedded, then you should use the SDK and make test requests to make sure that your changes are working. Here's my test request if you need one.
Use an IDE that can highlight problems for you. That first problem mentioned above is something that my IDE caught. I am using VSCode.

Let me know if you have any questions.

@martinytodorov - anything outstanding on this PR?


Search background on dark mode in beta

I guess the background shadow should not be pink?
📟 @exezbcz

seems in light is pinkish too

👋

yup, it should be solid black.  Do you know if the search result is otherwise complete? I see several things that are incorrect about it.

Here?

#4090


[Question] How do I remove a key bindings

Question
I use <space-f> instead of <to_resident>, but it doesn't work. I found that the space key would be captured first, so I used the unmap command to remove it, but this didn't work. Did I misunderstand the purpose of unmap?
gnunmap <space>
gnunmap f
gnnoremap <space-f> <to_resident>

I think it should be as below. However, I have no way to try it out.
gnunmap <space-f>
gnnoremap <space-f> <to_resident>

Unfortunately, that doesn't work

Oh, now I remember the space key is not a special key so maybe you can map two key strokes like this:
gnnoremap <space>f <to_resident>

Oh, now I remember the space key is not a special key so maybe you can map two key strokes like this:哦，现在我记得空格键不是一个特殊的键，所以也许你可以像这样映射两个击键：
gnnoremap <space>f <to_resident>

Oh my god, it ran successfully, thanks for your help.


Check the modulus bit length

The check was missing in DH_check and DH_check_params.
DH_check_pub_key_ex was accidentally calling DH_check,
so results were undefined.
[extended tests]

Checklist

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

Can I cherry-pick the commit
fc0f536 "DH_check_pub_key_ex was accidentally calling DH_check"  to 1.1.1
and
fdde60f  "Use BN_clear_free in DH_set0_key"  to all 1.1.1, 1.1.0 and 1.0.2

Is this for master only? If not, it should be labeled appropriately

Yes, sorry for confusion, but whenever I look somewhere, something comes up.

I'm okay with cherry picking the changes.

Merged to all branches where applicable, cherry-pick for 1.0.2 did fail,
maybe I'll make another PR for that.  Thanks!


Rating system explanation

Hi guys,
Thank you for this awesome LD support project! You're rockstars)
Please help me to understand the core system (link to exact line of code is also fine). So if i have a project and have no comments on other project my rating is 0. Then i commented P of the projects, and my raing is N.
What the algorithm to get N from P, and how N affects to my project position on the board :) Thank you.

Hi Zulman,
The relevant lines in the code are:

This, to get how N is computed: https://github.com/mkalam-alami/ludumdare-feedback-friends/blob/master/includes/score.php#L32
Also, this to understand why we speak of "points" and not directly "comments": https://github.com/mkalam-alami/ludumdare-feedback-friends/blob/master/includes/score.php#L3

If you want to read more about the reasoning behind the rating calculation, you can also check issue #4 (before that I only made a straightforward subtraction).

Thank you!


master -> live

OPS Build status updates of commit 810c994:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/api/overview.md
:white_check_mark:Succeeded
View

docs/api/package-details-template-resource.md
:white_check_mark:Succeeded
View

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

docs/tools/Package-Manager-UI.md
:white_check_mark:Succeeded
View

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


@datafire/mailchimp api version 1.3 is no more working.

should change mailchimp api version to 3.0
Or create new @datafire/mailchimp3

Which version of @datafire/mailchimp are you working with? Some fixes were pushed in 3.0.0.
I'm able to use the mailchimp client successfully with my account, but it was created when 1.3 was still supported. Regardless we should update to 3.0.

1.3 is not working for me (maybe my MailChimp account just support 3.0)
I have tried to use curl connect to MailChimp 1.3 -- not working.
changing openapi.josn --- make to use 3.0 which is working.
I have tried ""datafire integrate --openapi http://api.mailchimp.com/schema/3.0/Swagger.json --name mailchimp30"
get invalid Swagger so maybe datafire itegrate does not support openapi josn with external files or urls.
Dong

-------Original Message-------
From: Bobby Brennan<EMAIL_ADDRESS>To: DataFire/Integrations<EMAIL_ADDRESS>Cc: git2dfc<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DataFire/Integrations] @datafire/mailchimp api version 1.3 is no more working. (#5)
Sent: 18 Aug '17 00:02
Which version of @datafire/mailchimp are you working with? Some fixes
were pushed in 3.0.0.
I'm able to use the mailchimp client successfully with my account, but
it was created when 1.3 was still supported. Regardless we should
update to 3.0.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

OK, looks like the issue is the external files. I've added some logic to resolve external $refs, but swagger-parser seems to be triggering a rate limit and is unable to download every resource.
Regardless, should be able to add Mailchimp 3.0 support in the next day or so.

Good news: Mailchimp 3.0 support is published in<EMAIL_ADDRESS>If you spot any problems feel free to open another issue here.
Thanks for the report!


Deprecation warnings in new app

I'm just getting started with locomotive, and I've found some hiccups with the Getting Started documentation. First, when I create a new app using lcm create and run it, I get the following errors:
$ lcm --port 8080 server
CLI ENV: development
Locomotive 0.4.2 application starting in development on http://<IP_ADDRESS>:8080
connect deprecated multipart: use parser (multiparty, busboy, formidable) npm module instead node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:56:20
connect deprecated limit: Restrict request size at location of read node_modules/express/node_modules/connect/lib/middleware/multipart.js:86:15
connect deprecated methodOverride: use method-override npm module instead config/initializers/30_middleware.js:16:20
HTTP server listening on <IP_ADDRESS>:8080

Hi @JetForMe,
These warnings are all tied to Express rather than locomotive.    I spent some time earlier this year dealing with this disconnect.
I've found that updating your package.json to include all of the express stand-alones will solve this, but I don't believe there is an automated process available today.

Okay, thanks!


Normalize state shape (redux store) if necessary

See:
https://redux.js.org/docs/recipes/reducers/NormalizingStateShape.html
https://www.robinwieruch.de/tips-to-learn-react-redux/#flatState
Normalizr
https://github.com/paularmstrong/normalizr
https://tonyhb.gitbooks.io/redux-without-profanity/content/normalizer.html

Flatten nested data that's returned from the API. Consider using Normalizr library.


Allow transfer from a substrate address to a evm address

Currently there 2 ways to deploy a contract to the chain.

Through the polkadotjs app, click developer -> rpc, call evm.create.
Using tools like remix or truffle to deploy through the http rpc.

Both of them requires that the source evm address(H160) has enough balance to pay the gas, but currently the only way to specify balance of an evm address is through genesis config, which is not convinent.
This pr added a transfer api, so anyone with a evm private key and some token can create contract on chain.
How to test:

Build the template node. cargo build -p frontier-template-node
Run it. ./target/debug/frontier-template-node --dev
Generate evm keypair using metamask.
Transfer some token from alice to the H160 address.
Deploy contract using truffle.

If not the the transfer, truffle would fail because lack of money, see:

I'm not sure to see the benefit. Why not simply use the balance.transfer extrinsic to achieve the same ? The client can do the conversion itself, I don't think there is a need to have a specific extrinsic for that

@crystalin Sorry didn't understand you, do you mean that I can transfer from a substrate address to a evm address using the transfer api, with library like polkadotjs? If so, I tried and didn't work.

@crystalin Sorry didn't understand you, do you mean that I can transfer from a substrate address to a evm address using the transfer api, with library like polkadotjs? If so, I tried and didn't work.

should work, transfer directly to the mapping substrate address of the evm address as your code does, ui convert tool here: https://hoonsubin.github.io/evm-substrate-address-converter/


Bitwise Calculator adding more function like  nand , nor , xnor

Description
I want to add feature of calculation and , nor and xnor operation could you please assign it to me under gssoc label.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

/assign

Status of your PR @agastya3636

Working


Uninstall does not work

In the uninstall menu, when I try to uninstall a batch, the batch is not erased.

The reason for this bug is that the batch name contains spaces. It needs to be corrected by enclosing it in double quotation marks. I had tried to fix it that way, but it did not work. I think you need to fix it in another way.


revisit mls

it likely probably doesnt really work on systemd systems due to XDGRUNTIMEDIR usage of systemd , logind, plus selinux unfriendlyness by systemd but.
when i revisit it. one thing to keep in mind is that i need sys.subj:systemhigh to range transition to systemlow on creation of pretty much anything in /dev and /sys
i do not have file context specs for these mountpoint so if i dont take care of rangetransitions then some stuff there ends up on systemhigh requiring processes that have business with any of those objects read up access.... (not good)

i will likely end up adding file context specs for /dev /dev/pts at systemlow, then in addition make kdevtmpfs and co. rangetransition to systemlow on creation of any object in /dev except the few ones that need to be at systemhigh
in theory the same would apply to /sys/fs/cgroup except that is not being reset by anything automatically and i would have to force a relabel with tmpfiles.d (which i really do not want to do)


No need to use a personal access token anymore for Github Pages

As discussed in the recent comments in this page: https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/td-p/26869, it is not needed anymore to use a personal access token to push to Github Pages, and the standard GitHub Token works.
I also tested it and indeed this seems to work.
I suggest, therefore, to simplify the README removing the need of setting up a personal access token.
BTW, thanks for the great work on this action!

good suggestion!
the PAT is also referenced on the language-specific examples - eg the python example


Endless loop in HystrixMetricsStreamServlet

I follow the wiki to integrate hystrix-metrics-event-stream module, when I visit http://<IP_ADDRESS>:8410/hystrix.stream it never get response. So I debug and find that the HystrixMetricsStreamServlet is in a endless loop which is:
while (poller.isRunning() && !isDestroyed) {     ... }
How can I solve this problem?

The intent of the HystrixMetricsStreamServlet is to provide data for as long as the connection to the servlet is open.  That's why it's structured as an infinite loop with a way to exit out.
It sounds like the problem is that you're not getting a response.  When you make a request to the servlet, have you already executed commands at that point?

I have executed some commands.When I am debugging, I can see the command infos I have executed in the variable List<String> jsonMessages = jsonListener.getJsonMetrics(); . But it just can't get out from    the loop.

Since the while-loop is running in a try-catch, any sort of error will exit the loop.  One such example is the client going away.  This causes response.getWriter().checkError() to return true, which throws an IOException and exits the loop.
When I run this metrics servlet and then start a curl against it, I receive data for as long as I'm connected and the server thread is working/asleep in the Thread.sleep for the duration.  When I kill the curl, the above error path gets hit, and the server thread is no longer doing any work.  Have you tried something like that to observe how the pieces fit together?

thank u, I know what's going on : )

I have similar issue with hystrix 1.5.2 using on Jboss. When hitting the hystrix stream URL in browser, it's going in infinite loop and nothing is responding back to web page. I can see the metrics as JSON string in debug mode.
whats going on ? @rocky-luo - Can you please share what was that ?


modify allowed location for Linehaul Transportation(LHS) to origin: #163407346

Description
Change Linehaul Transportation(LHS) item location from NEITHER to ORIGIN. And display O vs N where appropriate.
Reviewer Notes

Created a migration to update the allowed_location
Database value wasn't being used when generating the base shipment line item location. Modify the code to use the database data vs hard coding the allowed location for each base shipment line item.
Update test data to use correct location value.

Setup
Run db migrations to ensure you have updated data.
Code Review Verification Steps

Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #dp3-engineering

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Screenshots
TSP:

OFFICE:

I updated generator_test and update_invoice_upload_test to ensure LHS has the appropriate code. This makes me wonder if we should eventually have tests to check if our data matches what we expect to see...
There were a few tests that started failing when we added validation to the ShipmentLineItem. Updated those tests and added a general function to display any validation error we encounter.


(#47) - Add support _db_updates feeds

Follow detects whether an url (or db or uri) ends with /_db_updates and changes
its internals accordingly.
There is no need for extending the API and the change is fully backwards compatibel,
because the can't exist a db called _db_updates.
With one exception: If a user was to route a couchdb database on an endpoint
which is _db_updates it will not work the same anymore :)
Btw: I have moved the logic to support the variants to set the db: url and uri into the follow function to allow setting url property of the feed object, because speaking about db sounds wrong in this context.

PunjabJobs4u.in can offer you the latest updates on Punjab Govt Jobs, Central Government Jobs, walk-in interview, Latest jobs notifications, Latest news on career and alternative vital data. Get Government jobs, IT jobs, Fresher jobs, engineering jobs, railway jobs, teaching jobs, bank jobs, university jobs etc.


Refactor

Codecov Report

Merging #743 (8a7f608) into main (8d82e02) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #743   +/-   ##
=======================================
  Coverage   85.57%   85.57%
=======================================
  Files         311      311
  Lines       28945    28945
=======================================
  Hits        24771    24771
  Misses       4174     4174

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 8d82e02...8a7f608. Read the comment docs.


Use Visual Studio 2019 image

I think the image Visual Studio 2019 is already available

'vstest.console' is not recognized as an internal or external command,
operable program or batch file

what is this vctest.console?

Related: https://help.appveyor.com/discussions/problems/23916-visual-studio-2019-vstestconsole-not-found-loggerappveyor-not-found
It looks like it is something that the test project is using. Maybe it is not in the path of the non-preview images 🤷♂

okay, let's wait for a while with this one then. I've just subscribed for notifications of appveyor ticker.

@SSE4 we have to assign every PR to a milestone before merging so we don't miss any change 👍


The current model segfaults when predicting new pcap

Issue
When trying to predict a new pcap, the predict script segfaults.
The segfault occurs at line 49 in predict script, method joblib.load imported from sklearn.externals
from sklearn.externals import joblib
classifier = joblib.load("./classifier-nb.dmp")

A quick solution to this was to change replace this method with load from joblib
from joblib import load
classifier = load("./classifier-nb.dmp")

But this solution fails to load the current trained model -as the dumping format is not compatible- rendering this model useless.
Environemnt
I faced this issue with two different setups

1st setup using debian based os

Ubuntu 18.04.1
python2.7, python3.5

2nd setup was on archlinux

Archlinux - Linux  4.19.13
python2.7.15 & python3.7.1

Steps to reproduce

Capture a packet using the provided ./pcap/capture.sh duckduckgo
Try to predict this packet using python predict.py ./pcaps/duckduckgo/duckduckgoXXXXX.pcap

Fixed.


[BUG] Planet not visible on it's moon's sky (but planet's ring is!)

[Please fill out the form below and delete the sections in square brackets after reading them]
Version of Advanced Rocketry

AdvancedRocketry-1.12.2-1.7.0-232-universal.jar

Have you verified this is an issue in the latest unstable build
N/A
Version of LibVulpes

LibVulpes-1.12.2-0.4.2-75-universal.jar

Version of Minecraft

1.12.2-forge1.12.2-<IP_ADDRESS>47.jar

Does this occur without other mods installed
Y
Description of the problem

Create solar system with at least one planet, with or without ring, and at least one moon.
Example:
[(https://pastebin.com/GEy5hqpB)]
Fly to moon (DIMID=3 in example)
Look at the sky - you will see ring, if parent planet has it, but not a planet!
Change time of day - if there is a ring, you will find a moment when almost whole ring without planet is visible, if there is a ring. If no ring, you will see only stars.

The parent planet is actually visible, but for some reason there's a bug that makes it very small:

I think this is part of the same bug, after setting the orbital distance of my moon, it appears very large (as I intended) from the planets surface, but for some reason when looking at the planet from the surface of the moon, the planet appear significantly smaller, the planet should appear larger from the moons surface than the moon does from the planet, but for some reason, they don't.


Rename state props

I modified the Store interface a little so it is more conventional with usual Kotlin design.
The getState() method is not appropriate because it is a getter, and in Kotlin we use properties instead.
A property is a combination of a implicit getter and a backing field, so explicit getters like getState() are not required anymore. Also, there was a property named state so the Kotlin compiler would generate a getState() function for this property that clashes with the other getState() method you created. As a consequence, Java users would not be able to use your getState() because they generated getState() replaces it.
To summarize:
fun getState()  →  val state
val state       →  val stateChanges

Ah, the naming :) This is something I  struggled with as well while trying to make this library idiomatic in Kotlin. I like the proposal to change the name from getState() to simply state. I should have done that from the get go, but used a convention we have here at SoundCloud in a Java context, and I don't think it's the right call for a public Kotlin project.
I'm gonna think about the name for the state observable a little more, although stateChanges is quite nice, maybe even stateObservable since it's just so darn obvious.

Pondered over other names. Read through the code a few times. I like it! Let's go with it :)


Initializer is not Thread-Safe

Registering polymorphic serializers for credential types sometimes happens twice. Adding spring-boot-devtools to a service's classpath triggers this, if the Initializer is called upon startup

Is this still an issue?

i don't know. adding it to my backlog

we can reopen, if it happens again


Make automatic HEAD -> GET configurable

The automatic conversion of HEAD requests to GET requests when there is no HEAD method in the route should be configurable (i.e. turn it on or off).

This behavior is not very clear (using 4.12.2). Take for example, registering routes in this order:
app.get('/resource/:id', getHandler);
app.head('/resource/:id', headHandler);

Done this way you will never ever hit the headHandler. However, if you reverse the order:
app.head('/resource/:id', headHandler);
app.get('/resource/:id', getHandler);

Both handlers are called when the application encounters the appropriate verb.

@rsandor yes, this is a sad situation :( This is one of the reasons we added .route() to Express 4.x, though, so you won't ever hit this issue:
app.route('/resource/:id'')
.get(getHandler)
.head(headHandler)

As a bonus, using .route() is more efficient, so you'll have a slightly higher throughput for the equivalent non-.route() app.

Sorry to bump an old issue - Is .route() always preferred, or just in situations where you have a single URL with a few HTTP methods?
Is it more efficient just in general?

It is always preferred and more efficient in general, due to the stack being more compact.

@dougwilson - Are the use of routes now enforced at an interface level in the newest versions of the library? If not, I highly suggest either making them so or simply fixing this issue. It seems like bad form to let a problem like this persist :/

@rsandor , you're welcome to express your displeasure of the pace of this project to<EMAIL_ADDRESS>, as this project is under StrongLoop and I am just a Collaborator.

@dougwilson - kudos for not answering my question and taking the critique as a personal attack. Sorry I confused you with someone who could have an impact on the project.

No problem!


Add proper map of Kant Island

I think this is a good starting point with many iconic attractions. This part of work will be valuable even if this will be the only part of the city represented in this project.

https://www.openstreetmap.org/#map=19/54.70635/20.51172
Screenshot
https://www.asciiart.eu/image-to-ascii
ASCII gradient: Minimalist
Edge Detection: Yes, 2
Space Density: 40

ba37ea05e66a08f0e0818464dc68465a2a2ff7ff

5263ca54a65ae38de188497b5f535eb337335a23

Deprecated in favour of #16.


Requests don't seem to have a timeout, this can lead to indefinite hanging

We have observed calls that seem to hang forever.  Looking over the client it doesn't look like it has a default timeout set on requests, and it is possible that the get to retrieve jobs while polling for results hangs forever.

Hi @dabacon, with the new PR merged (thanks!), are you still observing the troublesome calls that you found before? Or shall we close this particular issue now?


[Feature Request] Improve keyboard use within the signature adder

Could it be possible to have some improvements in signature adder window?

When manually entering the Description, Enter should enter the signature instead of inserting a new line and Shift+Enter would insert a new line instead.
Would it be possible have customer WH Type entries ? Often times when scanning Shattered wormholes, I can't find WH Type in the dropdown list, it's just different from what's available in the list. Would it be possible to have a Custom type that you enter by yourself if it's not in the list ?

:star2: Feature request accepted
Great feature request! I really like your idea.
Please, keep in mind that new features need some time to be implemented. New requests are always prioritized by their cost/benefit for all users.
:information_source: Feel free to ask for the current route map in our dev-chat: #Slack

Auto-generated response

Arrow keys (up, down, left, right) can now be used to navigate inside the signature table
return key can be used to "open" in-place editor for current focused cell
return key can be used to "save" in-place editor

Inside "description" textarea,  return adds new line break. ctrl + return can be used to save that field.


[SERVER-SIDE] With connector change merged, change setup.py to use main branch

duplicate of https://github.com/snowflakedb/snowpark-python/pull/1862#pullrequestreview-2151873093


[Bug Report] something wrong with  Cascader  component

Element UI version
2.3.6
OS/Browsers version
mac OS / chrome version: 65.0.3325.181
Vue version
2.5.17-beta.0
Reproduction Link
https://jsfiddle.net/sekygrande/x7p5vwzm/
Steps to reproduce
just click A , B ,C in the cascader component and see what show on the input and console.log
What is Expected?
click A , the input show A and the console.log is A
What is actually happening?
when i click B , the console.log is B but the input is only A , and click C the input is 'A-B',and it happened by accident , same code but different result ,sometime its right.

I don't know what you mean.
I can see only one output with 'A-B-C'

Then please minify your project and provide a valid reproduction.

@wacky6 @Leopoldthecoder this is what happened.. and it does'nt happen all time..same code  and in other view its right..

https://jsfiddle.net/sekygrande/mmx38qxw/1855/ this is my code

You should at least make sure your demo actually runs without error.


ENH: ICA support for qt-backend

What does this implement/fix?
This implements support for plotting ICA with ICA.plot_sources(raw) and when mne-tools/mne-qt-browser#40 is merged also ICA.plot_sources(epochs).
Additional information
Depends on mne-tools/mne-qt-browser#54

Remaining failing CI's are either unrelated (Windows 3.9 pip pre) or they will go green when #10297 is merged (Ultraslow PG).

We should wait for mne-tools/mne-qt-browser#54 to be merged before this one is merged

Windows pip pre can be ignored if the failures are in reading head positions and one EGI test

@larsoner And this one would be great, because mne-tools/mne-qt-browser#40 and mne-tools/mne-qt-browser#54 depend on some of the changes here as I just noticed.

Tested locally and Test Ultraslow_PG passes when https://github.com/mne-tools/mne-qt-browser/pull/54 is merged.

The PG test run failures look real

Yes thanks, one error in Ultraslow_PG was real the other depends on merging https://github.com/mne-tools/mne-qt-browser/pull/54

Yes thanks, one error in Ultraslow_PG was real the other depends on merging https://github.com/mne-tools/mne-qt-browser/pull/54

Same deal as a few days ago -- this is not good because it means that, if I merge this and we merge https://github.com/mne-tools/mne-qt-browser/pull/54, devs with mne-qt-browser who update to latest main here will suddenly have test failures. Is there some way to relax the test such that it passes here even without https://github.com/mne-tools/mne-qt-browser/pull/54 ? Or triage based on version / attribute of mne-qt-browser what the value should be?

I suppose we could then skip then all qt-backend tests for mne-qt-browser<=0.2.0 or at least for test_plot_raw_white and test_plot_raw_selection. What would you prefer?
So if I understand correctly the CI's here are only to detect bugs coming from the mne-python side and otherwise it should always work with the latest stable release of mne_qt_browser, right?

So if I understand correctly the CI's here are only to detect bugs coming from the mne-python side and otherwise it should always work with the latest stable release of mne_qt_browser, right?

Ideally the MNE-Python tests will work (i.e., be skipped or pass) with whatever version(s) of mne_qt_browser have been released during the given MNE-Python release cycle. It's bad if we force MNE-Python devs to upgrade another dependency (mne-qt-browser) outside of release time to make pytest mne work.
Taking an extreme example, let's say we push out MNE-Python 1.0 and mne-qt-browser 0.2.0 on Friday. But then mne-qt-browser 0.3.0 comes out a month later. And 0.4.0 a mont after that. At the MNE-Python side, if the contract is that we only support the latest mne-qt-browser, if the new tests to accomodate 0.3.0 and then 0.4.0 break something for a dev who installed 0.2.0 at release time, now pytest mne/viz has broken for them two months in a row, forcing them to upgrade each time. Putting in smart version checks at the MNE-Python env makes it so that people who work on / are interested in mne-qt-browser can easily upgrade to test the latest mne-qt-browser release, but not have tests fail if they haven't upgraded yet.

Yes thanks, it took me a while do understand that and I try not to forget next time. Are you content with the latest solution leaving room for future skips?


:killserver command

boring

why

why not

why not
Why yes?

wtf does "why yes" mean

wtf does "why yes" mean

An inversal of the question "why not"

Interesting

Faster than :shutdown

Lies, slander

Lies, slander

:shutdown takes like 10 seconds just to show the message that it's shutting down

Lies, slander

:shutdown takes like 10 seconds just to show the message that it's shutting down

I feel likes it's due to this \/ code
Function = function(plr: Player, args: {string})
if Core.DataStore then
Core.UpdateData("ShutdownLogs", function(logs)
table.insert(logs, 1, {
User = plr and plr.Name or "[Server]",
Time = os.time(),
Reason = args[1] or "N/A"
})
local nlogs = #logs

if nlogs > 1000 then
table.remove(logs, nlogs)
end
return logs
end)
end
Functions.Shutdown(args[1])
end

Lies, slander

:shutdown takes like 10 seconds just to show the message that it's shutting down

I feel likes it's due to this / code
Function = function(plr: Player, args: {string})
if Core.DataStore then
Core.UpdateData("ShutdownLogs", function(logs)
table.insert(logs, 1, {
User = plr and plr.Name or "[Server]",
Time = os.time(),
Reason = args[1] or "N/A"
})
local nlogs = #logs

if nlogs > 1000 then
table.remove(logs, nlogs)
end
return logs
end)
end
Functions.Shutdown(args[1])
end

Why is this necessary?

Lies, slander

:shutdown takes like 10 seconds just to show the message that it's shutting down

I feel likes it's due to this / code
Function = function(plr: Player, args: {string})
if Core.DataStore then
Core.UpdateData("ShutdownLogs", function(logs)
table.insert(logs, 1, {
User = plr and plr.Name or "[Server]",
Time = os.time(),
Reason = args[1] or "N/A"
})
local nlogs = #logs
if nlogs > 1000 then
table.remove(logs, nlogs)
end
return logs
end)
end
Functions.Shutdown(args[1])
end

Why is this necessary?

It saves a log of the shutdowns to a datastore to prevent abuse. But its the issue causing it to delsy the shutdown for longrt

Lies, slander

:shutdown takes like 10 seconds just to show the message that it's shutting down

I feel likes it's due to this / code
Function = function(plr: Player, args: {string})
if Core.DataStore then
Core.UpdateData("ShutdownLogs", function(logs)
table.insert(logs, 1, {
User = plr and plr.Name or "[Server]",
Time = os.time(),
Reason = args[1] or "N/A"
})
local nlogs = #logs
if nlogs > 1000 then
table.remove(logs, nlogs)
end
return logs
end)
end
Functions.Shutdown(args[1])
end

Why is this necessary?

It saves a log of the shutdowns to a datastore to prevent abuse. But its the issue causing it to delsy the shutdown for longrt

I've never known Datastores to take so long to finish with their operation

This feels... unwise.


Error when trying to have bookmarks

Hello,
When trying to download today I get this error message and when trying with the url link it works so I guess it's the bookmarks that are the problem.

Thanks for your help.

They changed the bookmarks url again?

It works. Thanks for the quick fix ;)


No registered namespace for type org.example.mynetwork.Trade

I am following the tutorial under hyperledger Composer (https://hyperledger.github.io/composer/tutorials/developer-guide.html) and am getting the error when I do an npm install.  I have Composer v0.8.0 installed

Please try this again with v0.9 and reopen if still an issue.


Add Field for Persistent Directories

What would you like to be added?
User is able to choose directories which will be persistent in runtime. (https://github.com/robolaunch/robot-operator/pull/191) These directories should be selectable over UI. Tag selecting experience can be convenient for such operation. An example from Stack Overflow:

Why is this needed?
It's needed to extend user's control over a robot or an application.

These directories should be added by default and grayed out:

/var
/etc
/opt
/usr

Regex for input: ^(/([a-z0-9/])+:)*(/[a-z0-9/]+)$

The feature has been added successfully. This feature will be available for v0.26.0 and later.
Thank you for your interest.


Cleanup tonic-web cors support and replace it with tower-http

Motivation
The CORS code in tonic-web is not 100% compliant with cors spec and cannot be detached from the rest of the tonic-web protocol implementation. This can be problematic for some use cases where the tonic-web layer is just a part of the server, and some other cors layer is used before (as far as i understand in particular for https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests).
Some other grpc-web implementations where cors is separate from the protocol implementation:

https://armeria.dev/docs/server-grpc/#grpc-web
https://github.com/grpc/grpc-web/blob/35284bfe156fc41bbcdd554ac423a587d93ff8da/net/grpc/gateway/examples/helloworld/envoy.yaml#L30

How
As described here: https://github.com/hyperium/tonic/pull/1119#issuecomment-1285123214. the idea is to:

Remove all the tonic-web cors handling logic
tonic_web::enable composes CorsLayer from tonic-http and GrpcWebLayer introduced by #1119. If a user wants more control over the CorsLayer, they can just instantiate manually GrpcWebLayer and compose it with whatever configured cors layer they want (not necessarily the one provided by tower-http)

Breaking changes

Config gets removed
Behavioral changes for the cors layer, more conform to the spec

Notes

The current cors implementation is "strict", returning an error status code when headers, origin and whatnot are not compatible with the cors configuration, e.g. https://github.com/hyperium/tonic/blob/b409ddd478959e239aeef3cb8715cd3ace470a8f/tonic-web/src/service.rs#L300
This seems to be the opposite of what should be, see https://github.com/tower-rs/tower-http/pull/224 and in particular the fetch spec https://fetch.spec.whatwg.org/#http-responses

A successful HTTP response to a CORS-preflight request is similar, except it is restricted to an ok status, e.g., 200 or 204.
Any other kind of HTTP response is not successful and will either end up not being shared or fail the CORS-preflight request.

This because in the preflight request the server just replies back to the browser with its cors configuration, then it's up to the browser to figure out whether it should proceed or not with the actual request.

Ok finally got to reading this and it all makes sense to me!


Adding java chaincode for private-data sample

-Reflects all transactions as in chaincode-go
-Tested with application JS

Incorporated PR so far. Ready for another look.

This one is ready for review.


Cannot create MultiDC cluster on cassandra 4.1+

What happened?
Due to releasing https://issues.apache.org/jira/browse/CASSANDRA-12988 creating multidc clusters stucked on first cassandraDatacanter.

K8ssandra-operator creates first cassandraDatacanter with k8ssandra.io/initial-system-replication: '{"xxxx-dca":3,"xxxx-dcb":3}' and wait cassandraOperatorProgress = "ready"
Cass-operator receives 500 in loop from mgmt-api POST /api/v0/ops/auth/role

2023-01-26T10:15:40.257Z    INFO    calling Management API create role - POST /api/v0/ops/auth/role    {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "cassandraDatacenter": {"name":"xxxx-dca","namespace":"default"}, "namespace": "default", "name": "xxxx-dca", "reconcileID": "c01b266e-4461-4122-98f9-a40d28d64bb1", "pod": "xxxx-xxxx-dca-rack1-sts-0"}

2023-01-26T10:15:40.367Z    ERROR    incorrect status code when calling Node Management Endpoint    {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "cassandraDatacenter": {"name":"xxxx-dca","namespace":"default"}, "namespace": "default", "name": "xxxx-dca", "reconcileID": "c01b266e-4461-4122-98f9-a40d28d64bb1", "statusCode": 500, "pod": "<IP_ADDRESS>", "error": "incorrect status code of 500 when calling endpoint"}

Cassandra 4.1 Cannot achieve EACH_QUORUM consistency because k8ssandra-operator didnt create second DC

INFO  [epollEventLoopGroup-5-3] 2023-01-26 10:14:59,138 RpcExecutionException.java:39 - Failed to execute method NodeOps.createRole
org.apache.cassandra.exceptions.UnavailableException: Cannot achieve consistency level EACH_QUORUM in DC xxxx-dcb

K8ssandra Operator version: v1.4.1

Anything else we need to know?:
It can be fixed by changing auth_write_consistency_level

Yes, I can easily reproduce it, and your analysis is spot on.
We're going to refactor the code to alter keyspaces as new DCs get added, instead of listing all DCs ahead of time.


gpu version not working on ubuntu 20.04

after starting gpu version 2.4.0 with command:
./engraver_gpu  -d -i xxx -p /mining -g 0:0:0 -n 500000 --sn 0
i get the errors:
###################### OPENCL PROGRAM BUILD DEBUG OUTPUT ######################
input.cl:262:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:268:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:275:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:282:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:288:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:295:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:302:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:308:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:315:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:322:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:328:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:335:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:342:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:348:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier
input.cl:355:12: error: OpenCL C version 1.1 does not support the 'static' storage class specifier

you can try adding the following code at the start of file "src/ocl/kernel.cl":
#ifdef cl_clang_storage_class_specifiers
#pragma OPENCL EXTENSION cl_clang_storage_class_specifiers : enable
#endif

It's working for me with AMD opencl impl.

excellent. Indeed opencl 1.1 is not supported out of the box and needs this definition. Will amend kernel.cl. Thx!


[Feature] Locational Prompts

What if image slices from the left and image slices from the right were compared to different prompts? Slices in the center and slices at the edge?
Perhaps if it was set to check for a jungle on the edges, and for a toucan in the center, it would create an image of a toucan in a jungle with a broad background of jungle.
While an interface for such a thing may get convoluted quickly, as long as it's kept to simple options like left/out and right/in and midpoint with a toggle for left/right or edge/center or up/down or what have you it shouldn't get too outrageous for a user.

there's quite huge room for various processing logic and prompts algebra of such kind, which does not bring any advantage to the method in general. feel free to fork this repo for further development of cosmetic usability on your taste.


Fmovies URL change

Source information
FMovies 14.23
Source language
English
Source new URL
Fmovies24.to
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

It's in the anime extensions


TypedPredictor bool always returns True

Likely a user error but when I tried to use dspy.TypedPredictor to return a boolean answer it always returns True despite the question. e.g. Q:"Is the sky brown?" A:True. I checked and if I change  the output var to be str it works as expected returning Q: "Is the sky brown?" A:"False". I tried with OpenAI(GPT3.5) and Ollama(Mistral).
  import dspy

  class QABoolean(dspy.Signature):
      "Given a question provide a boolean answer"
      question: str = dspy.InputField(prefix="Question:")
      answer: bool = dspy.OutputField(desc="either True or False", prefix="Answer:")

  # lm = dspy.OllamaLocal(model="mistral", stop=["\n", "\n\n"])
  lm = dspy.OpenAI(model="gpt-3.5-turbo", stop="\n\n")
  dspy.settings.configure(lm=lm, temperature=0.0)

  checker = dspy.TypedPredictor(QABoolean)

  code = 'print("Dspy is cool!")'
  question = "Is this code dangerous to run" + code
  response = checker(question=question)
  print(response.answer) # Returns True -> Correct

  question = "Is the sky brown?"
  response = checker(question=question) # Returns True -> Wrong

Fixed that in a recent push.
Please try again with the latest code from main.


Update to Forge <IP_ADDRESS>08

Updating to a more recent forge. There were a large number of broken functions where the mapping names had changed.
In addition, there was a fix (e9a0e660077cc8f374aabfca029f30a1582495e) which broke all custom item rendering.

There is no actual need to update mappings versions. Nor does anything actually change in the final build with updating forge.
Also you're not quite right on the item rendering issue. That's not what broke it; the whole BakedCustomItemModel thing needs to go


any code realease plan?

@eleboss The code was released, as outlined in the README, in advance of ECCV 2024. We uploaded our implementations on September 29, 2024, with further documentation and optimization examples to be added soon.


upgrade to phpseclib 3.0 to match google's upgrade of phpseclib

Google have updated phpseclib in their API client to 3.0. This allows consumers of this library to keep packages up to date.

@marickvantuil running this in prod with no issues

I've been getting the same errors as in #111 and here so I've reverted it back to 2.x for now. Hope it doesn't break anything.


Question: Folder or files named as 'concepts' dont build

Hi all,
There some reason for why slate dont build properly if I have some markdown file or folder named as  'concepts'?
error  build/includes/en/concepts/notifications
error  build/includes/en/concepts/messages
error  build/includes/en/concepts/handle-notifications
error  build/includes/en/concepts/handle-messages
error  build/includes/en/concepts/handle-commands
error  build/includes/en/concepts/extensions
error  build/includes/en/concepts/commands
error  build/includes/en/concepts/channels
error  build/includes/en/concepts/addressing
If I change the files or folders name everything works fine :|
Operating system: Windows 10
Last upstream commit (run git log --author="Robert Lord" | head -n 1): 17b259a40da6ef3e0561db76371754b6620e1e43
Ruby version (run ruby -v):  2.3.3p222

Sorry for the slow reply. As you see above, I seem to be able to have that folder name without any problem?

(Closing due to inactivity, but glad to continue the discussion — feel free to reopen if you'd like to chat!)

Hello @lord, sorry for the delay :(
It was my bad. I really can not reproduce this problem in my fork.
Just to let you know this is my project https://github.com/takenet/blip-docs
Thank you very much and congrats for your great job. 👍

Huh, no worries, glad it's solved now! Your project looks good, glad to see another person using Slate 😄


set hint to prevent SDL from configuring a signal handler

After AudioDevice is created, pressing Ctrl+C no longer quits the application. During sdl2::init() SDL sets a signal handler so that the signal resulting from Ctrl+C gets stored as an sdl2::Event::Quit event, but since nothing polls the SDL event loop the signal is ignored.

thank you


Remove unused features from time.

This also removes a dependency on time 0.1.x which has a open RUSTSEC advisory.

Thanks 👍


user: Show highlighted custom profile fields first

Draft PR because the API isn't yet final. This uses the API from the current server-side prototype, https://github.com/zulip/zulip/pull/21588 .
Fixes: #5363

The server PR has been merged.

Updated, and tested manually against CZO. Merging!


Added Argument value and cleaned up SimpleAdd test (it should pass now).

Updated to fix some styling issues.


Can't submit circuits (with my token) using css

What is happening?
For some reason, even after refreshing my token many times, I was getting the following error:
SuperstaQException: Status code: 400, Message: 'Non-retriable error making request to SuperstaQ API, Your CQ token is invalid. The token you are using has probably expired. Refresh it.'
when attempting to run this code.
However, when submitting using @vtomole 's SuperstaQ token, or just submitting through SuperstaQ directly, everything ran smoothly.
How can we reproduce the issue?
The script I ran was :
token = "token"

service = css.Service(token)

qubits = cirq.LineQubit.range(2)
circuit = cirq.Circuit(
    cirq.H(qubits[0]),
    cirq.CNOT(qubits[0], qubits[1]),
    cirq.measure(qubits[0]),
    cirq.measure(qubits[1]),
)

job_css = service.create_job(
    circuit=circuit, repetitions=100, target="cq_hilbert_simulator", options=options
)
result_css = job_css.counts()

print(f"Counts from cirq-superstaq submission: {result_css}")

What should happen?
It should run the circuit on the Hilbert simulator, and print out the counts.
Environment

SuperstaQ version: 0.3.33
general-superstaq version:
cirq-superstaq version:  0.3.24
qiskit-superstaq version:
Operating system:
Python version:
Any other relevant dependencies:

Any additional context?
No response

@pgoiporia is looking into it

It should work now @SalahedeenIssa

Works!


[mtl] fix render pass compatibility check wrt sample count

Addresses https://github.com/gfx-rs/wgpu/issues/1046 on master
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:

Actually no longer sure it's the right fix. Need to think about it with a fresh head

bors r+


used for my own dataset

nice work! Thanks for your sharing!
What should I do to train it on a new dataset?

Hi,
For your own dataset please use voc.py in lib/dataset as a template/reference to create your own dataset class. You need to ensure that getitem() and len() work as required
Then add the dataset reference in dataset_factory.py so that it can be given in the configuration file.


Week 27 Updates

Fixing now.

@jofsky Would you mind refreshing this PR to pick up Paul's 3.39.1 release?


AwesomeOpenSource

We are creating a github org for all awesome open source repos. I am working with a few individuals who are also managing their own awesome repos, and I think to gain more traction we need to work together. What are your thoughts about collectively moving your awesome repos to https://github.com/AwesomeOpenSource
The idea is that visibility for these repos would be increased due to more traffic to the org. What are your thoughts? Let me know if there is anything you'd like to discuss!

repo link broken.
close?


修改MELOG_TRACE宏定义

小修  见diff

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


Daily fixes

fix fullscreen functionality and drop warning

I'm making full screen (borderless) default for practical reasons @guusw , have a look please

I think fits also mobile devices where stuff is full screen anyway

Actually I'm not so convinced, maybe we need a fullscreen parameter like before?

I held of on this since having a fixed parameter is not that useful without being able to switch on demand, but I'm fine with adding it like this.

I held off on this since having a fixed parameter is not that useful without being able to switch on demand, but I'm fine with adding it like this.

But I mean, it's resizable when not fullscreen (windowed) anyway no?

The issue is we make no distinction without maximixed and full screen with this PR

We might want a flag


setting correct koreader mount path on windows.

I cannot get the mount path for my kindle e-reader right on my windows machine.
Since the plugin doesn't throw any kind of message, it is a little difficult to tell whether something is happening whenever the user hits "sync".
Also, it is a little unclear from the example in the plugin, whether the mount path has to point to koreader's folder or the root dir of the devices running koreader.
Does the plugin expect unix-style paths only?

It doesn't appear to be. I'm looking at the console on desktop, it looks like if there's a leading backslash in the file path it'll try to pop "C:" in front of it. and if I don't it'll try to search inside of the obsidian vault.
What worked for me on windows just now was copying all the .sdr folders with all of the highlights and whatnot into the windows filesystem and pointing the plugin at that. I tried using it on my phone but it doesn't appear to be mobile-enabled.
What I'm going to do is use syncthing to automate that and just run it once in a while.


[STORM-737] Check task->node+port with read lock to prevent sending to closed connection

It's based on Nathan's comment, please refer to https://github.com/apache/storm/pull/349#issuecomment-87778672
https://github.com/apache/storm/commit/861a92eab8740cfc0f83ac4d7ade9a2ab04a8b9b seems to make a regression.
But it also introduces optimizations of sending, it shouldn't be discarded.
I changed send logic to let TransferDrainer matches task to node+port so then we can still enjoy optimization of sending logic.
I'm still not familiar with clojure so please review and comment if it can be optimized.
Thanks!

@nathanmarz @d2r You may want to take a look since it's based on your discussion, https://github.com/apache/storm/pull/349#issuecomment-87778672.

@HeartSaVioR , I am sorry I have been swamped with another task, and I have not had a chance to review.
I had a branch, but I had not taken an opportunity to really test it yet.
I will try to get back to this within the week.

@d2r Thanks for comment, I can wait it. :)
Btw, your branch doesn't follow Nathan's comment.
In short, the code in the write-lock is fine – it's the code in the read lock that needs to be fixed. As part of that, the code looking up the node+port for a task needs to be moved back to this function and not happen before the tuple goes on the transfer queue.

Root reason is from mk-transfer-fn.
It matches task and node+port but there's some latencies from adding Transfer queue to sending via Netty. Task to node+port can be changed during latency so we should delegate matching it to very close to sending, within read lock to get safely.
 Thanks!

@HeartSaVioR
Thanks for taking a look. Well, I was trying to follow his comments. :)
I noticed though, that the line in my let binding
valid-node+ports (vals task->node+port)

maybe should have been
valid-node+ports (vals @task->node+port)

with the @.
task->node+port is actually an atom, however, so if we dereference it within the read-lock there, we should have the accurate task assignment before we add anything to the queue to be sent.  I believe this addresses the concern you cited from @nathanmarz.  The other change was to encapsulate the separate TransferDrainer#add, since it does not need to be a separate public method.
So, @HeartSaVioR, since we have both looked at my branch already, do you want to take my changes into your branch and continue the discussion from there?  It seems like a smaller set of changes to begin with, and maybe it would be easier going forward?

@d2r
First of all, I'm sorry I did some mistakes about expression.
I mean, your approach follows some of Nathan's comment, but not all.
Your patch can also resolve STORM-737, with dropping some tuples when task->node+port is changed, while we can save these.
@nathanmarz said 861a92e made a regression, so it means, before applying 861a92e (0666c41387fc11c0422b26ab27ebc38c30fe26af) was right.
AFAIK mk-transfer-fn is looking inside task->node+port while it should be handled from read-lock, and that's the point of regression.
You can find out I'm trying to revert it when you see changeset of mk-transfer-tuples-handler in that commit.
Current PR takes same logic (yes, same) from old thing but playing with TransferDrainer.

Please note that packets shouldn't have values which can be changed while passing to transfer flow.
task->node+port can be changed (I mean node+port for tuple can be changed), but task id for tuple is not.

@d2r
First of all, I'm sorry I did some mistakes about expression.

No worries.

So, I'd like you to review current PR, and find out issues, and go together.

OK, sounds good to me. Let me take a look.

I see 4 test errors using your branch.  They all appear to be test timeouts.

integration-test/test-basic-topology
messaging-test/

test-receiver-message-order
test-local-transport

netty-integration-test/test-integration

I ran mvn test on Linux and OSX and got the same results.  Can you please check?

@d2r I can't reproduce test failures. I'll give it a try again.

@d2r I can't reproduce test failures. I'll give it a try again.

OK, please update your branch, and I will re-run the tests.

@d2r
Modified TransferDrainer to re-group messages by destination when send has called.
I left TransferDrainer.add() cause it plays as buffer, but I'm ready to remove Transfer.add() when we think it's better to have other buffer.
I've done upmerging, and ran unit tests with no issue.

@clockfly
I'd like you to have a look since I don't want to destroy your optimization, but just fix the issue.
Thanks in advance!

We may be better to revert mk-transfer-fn to 0666c41387fc11c0422b26ab27ebc38c30fe26af as grouping by task can be handled (or doesn't need to be handled) from mk-transfer-tuples-handler.

I made another changeset which reverts whole things to 0666c41 (without try-serialize-local) but leaves TransferDrainer as buffer and grouper (by host+port).
https://github.com/HeartSaVioR/storm/commit/6ef2f11e9eade772c8ae67a6410d537871739938
If we think latter is better to move on, I'll post a new PR based on 6ef2f11e9eade772c8ae67a6410d537871739938.

Nathan's comments for clarifying its real issue completely makes sense.
But we should verify what codes we should change while applying.
IMO it is a critical path for transfer efficiency, so it would be better to have more reviewer for this patch.

@HeartSaVioR,
I see you are right.  There are two race conditions here:

If we do not check assignments in the read-lock, then we could use an invalid connection. There could be an exception if we lose this race.

If we group by destination node+port when we equeue tuples for sending, we lose the information needed to update the destination node+port when we dequeue for sending, since assignments task->node+port can change in the meantime.  If we lose this race, then tuples for which there is a new assignment may be dropped unnecessarily (if we fix 1.) or sent to the wrong worker.

(Formerly, I did not realize 2. was also a regression with 861a92e, so I was looking for a smaller change in this PR.)

If you think latter is better to move on, I'll post a new PR based on 6ef2f11.

OK, I will take a look at your other branch.

IMO it is a critical path for transfer efficiency, so it would be better to have more reviewer for this patch.

I agree. The more, the better.

I made another changeset which reverts whole things to 0666c41 (without try-serialize-local) but leaves TransferDrainer as buffer and grouper (by host+port).
HeartSaVioR@6ef2f11
If you think latter is better to move on, I'll post a new PR based on 6ef2f11.

I do prefer the changes on your other branch above those in this pull request because the other branch is cleaner, but it is up to you.  Either way we will want to be careful.
Thanks for looking at this.

@d2r Thanks for reviewing!
I'd like to get 6ef2f11 to pulled in, so I'm closing this PR unless we agree #521 is better than #557.

Since #557 has performance regression, we picked this PR.

@d2r @ptgoetz Applied @d2r's comments.

Tested with https://github.com/yahoo/storm-perf-test with the following arguments:
--ack --bolt 4 --name test -l 1 -n 1 --workers 4 --spout 3 --testTimeSec 900
-c topology.max.spout.pending=1092 --messageSize 10

OK, I found both the data-rate and the latency are improved with this patch in my tests:
master at 512d3def:
Throughput in MB/s:
max: 0.1519711812
99:  0.1510783919
90:  0.1276066783
50:  0.1100190481
min: 0.07258733114
Complete Latency/10m: 265ms
This PR 85c5096e merged to master at 512d3def:
Throughput in MB/s:
max: 0.1760864258
99:  0.1707911174
90:  0.1550458272
50:  0.1419607798
min: 0.1128451029
Complete Latency/10m: 204ms
I am also fine with the changes.
+1
Thank you for your patience, @HeartSaVioR.

@d2r No Problem, thanks for reviewing and taking performance test!

@ptgoetz Could you take a look in order to complete current PR? Thanks in advance!

I'm +1. As I mentioned on the other pull request this patch actually improves performance while the alternate approach created a performance regression.


Feature Request: Ignore ChoiceSet by default

The ChoiceSet RE modifies itself on execution to store the selected choice. As a result, any feat or feature with a ChoiceSet will always pop up as modified rules. There may be occasions where the feature's rule also ACTUALLY changed, so maybe put a toggle in the settings to say whether you want to examine ChoiceSet REs, and default to no.

That is very interesting. It does not do that for me using the latest version. The Item I am testing with is the Methodology for the Investigator, which properly ignores "selection".
Can you send me information of the Item you are looking at, as well as the version of PIR that you are running?

Never mind, call this a no repro. Perhaps this was an issue in the past, but when I dug deeper on all the examples I could find with my current actors, they all featured changes, if frequently very small ones.


[3.x] Add fill method to Array and Pool*Array

Backport of #46476

Could this be added to LocalVector too? I swear I've added this (on more than one occasion) to draft PRs. :grinning:

Thanks!


Internal ownedTokensIndex not properly cleared when removing a token from its owner in ERC721

🎉 Description
See this comment for more info. In the scenario that a token is removed from its owner, if that token was in the last index of the owner's array, the ownedTokensIndex keeps a reference to the token that should be deleted.
This does not cause any issues in the external interface of the contract, but the data structure it should be properly cleared. Thanks @mudgen for catching it.

🐛 This is a bug report.

I'm inclining towards not fixing this 'bug', for the following reasons:

I argue there isn't really a bug in the first place, since the Solidity interface is not affected by it.
The 'issue' is that a deleted token's index in its owner's array (_ownedTokensIndex) is not cleared. However, 'clear' simply means 'setting to 0', and 0 is a valid index value. This means that there's no potential for this 'tyding-up' to prevent future bugs.
This data structure is only ever used (read from) when deleting tokens in _removeTokenFrom. Any deleted token must obviously first be created, at which point the index will be set to the correct value, yielding zero negative consequences for not clearing the index, and increased gas costs when doing it (both for the SSTORE that sets it to 0, and the SSTORE that changes it from 0 to a different value, which is even more expensive).

This is related to #1541, where I propose getting rid of more cleanup of this sort.

Actually the additional SSTORE should result in a cheaper transaction because it's zeroing out a storage slot. @nventuro and I have been doing some tests though and it doesn't seem to be that way. We're still not sure why but will keep looking into it.

Yup, my comment was based on tests, not my understanding of the platform (which is clearly wrong, since I'd expect the zero-ing out to refund 10k gas).


ConfigurationError: Could not find name 'devtest.sandiegodata.org' in group 'accounts'.

python -m unittest test_library.Test.test_s3_push

http://pastebin.com/6TJ4uUFa
It seems I need access and secret for devtest.sandiegodata.org , but do we really need to use remote servers for testing? I think it should be replaced with local data (or mocked if there is not way to use local data).

Well, if we're going to push to S3, there should probably be a test that actually pushes to S3. But, the cache code has moved to the ckcache package, so maybe it would be better to test it there.
The easiest way to solve the problem is make the s3-remote not have a remote cache URL. SO, in test/bundles/testbundle/library-test-config.yaml, change

    s3-remoted:
      remotes:
        - 's3://devtest.sandiegodata.org/s3-remote#compress'

To a reference to  a local file, like

    s3-remoted:
      remotes:
        - '{root}/mock-s3-remote'


Set the image's width so images are square

Fixes issues like:

I'm gonna close this PR. Forcing images to be square doesn't make sense.
This thumbnail should remain as a rectangle.


[Bug]: Number field breaks increments on drag

Reproduction
https://stackblitz.com/edit/vitejs-vite-vj2uag?file=src%2FApp.vue
Describe the bug
Hello everyone im using this package in my personal project and found a bug with the number field component, the way i came across this is that i was scrolling on my phone on a grid of elements, each element had the number field component and by pressing down the plus button on the component and dragging down it triggers a never ending increment, it even happens on the official example page, the only way to stop it is pressing again the same plus button, it also happens when having max or min limits. Check my video:
NOTE: It can be tested with a mouse in any browser
https://github.com/radix-vue/shadcn-vue/assets/47479471/3e333286-0432-4c7e-82c7-e4af6e4c49a9
System Info
System:
    OS: Linux 6.8 Fedora Linux 40 (Workstation Edition)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1270P
    Memory: 6.14 GB / 15.28 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.12.2 - /usr/bin/node
    npm: 10.5.0 - /usr/bin/npm
  npmPackages:
    @vueuse/core: ^10.9.0 => 10.9.0
    radix-vue: ^1.8.3 => 1.8.3
    vue: ^3.4.26 => 3.4.26

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

This is an upstream issue, related to radix-vue itself, I'll create a PR to resolve that, thanks for reporting !


feature: progress tracking for each module for signed in users

Is your feature request related to a problem? Please describe.
By looking at the website, there isn't a way to let the user keep track of where he left last and what he has read and completed.
Describe the solution you'd like

So if a user opens up a module say Exporting and Importing modules, it has 11 lessons, suppose a user is on the first lesson and reads it completely, and to go to the next page, there's a next button. Instead of next, we could rename it to complete and next and so on.
When a user leaves, his track is stored and when he opens up the same module again, he would be directed to the last incomplete lesson.
When a user comes on the root route, he will see a completed button right next to the number of lessons defined. If the user has not completed/started the module, then he will be shown the percentage of the module completed.

Additional context

This could potentially give some motivation to complete the modules to the end user.

@hkirat what say about this feature?


Support to weaken strong ETags when compressing/decompressing

Title: Support to weaken strong ETags when compressing/decompressing
Description:
Currently, when using the compressor filter, there are basically two options to handle (strong) ETags:

when setting disable_on_etag_header: true then do not compress a response
when setting disable_on_etag_header: false then throw away the strong ETag (only keep weak ETags)

But one other option, that is popular in other HTTP proxies/caches, for example Varnish HTTP Cache, is:

weaken any strong ETag by prepending it with the "W/" prefix when compressing a response before sending it to the client

When searching the web, there are numerous stackoverflow, bugzilla (or other bug tracking tools) and blog posts about how to handle ETags and how to do it in the least surprising ways (surprising for any developer or server/platform operator).
Now, since we were using Varnish and I was familiar with the "weaken any strong ETag when compressing" behaviour, it caught me by surprise that the Envoy compressor does not provide such an option (only the above two mentioned options).
My current use-case is to compress/decompress the traffic between each two Istio sidecars when the backends do not:

advertize in client requests that they support compressiong via Accept-Encoding
compress the response themselves when the client did advertize support for it and then adding a Content-Encoding response header

Would it be possible to provide a way to weaken any strong ETag with Envoy's compressor here?

cc @kbaichoo @mattklein123

Not stale.

Sorry, this fell off my radar @httpdigest. This sounds reasonable to me if it's an additional option. e.g. we have several modes of how etag is supported and the behavior you described being one of them.

Yeah, having the option to configure it like that, would be very much preferable for us.


when data is changed,How to make the check boxes of all nodes unchecked, just like the initial load

Hi @dingxuelan - would you mind posting this on Stack Overflow? You can leave a link here if you like - and likely someone from our team will provide suggested solutions. We try to use this space for bugs/issues and keep "how to" type question on SO. Thanks!


RootObject field name for ContentType

Loosely related to #79 (not conceptionally but would require same type of change):
I had a look at 7ef186b only due to recent (now-resolved) conflicts and got confused because the commit message doesn't seem to square with the changes. The changes decrease readability (PEP8, consistency between variables) but were said to be made to conform to Django standards.
Unless I'm getting things confused here (and this is about something different?), the Django docs recommend the spelling content_type for a field used to reference a model's ContentType. I would thus suggest to revert the field name, or better, to stick to the docs, i.e. drop the self_ prefix and use just content_type.
Note this isn't me trying to be nitpicky but wanting us to avoid changes for the worse (if not actively working toward changes for the better).

seems we have both versions in place contenttype and content_type. We should decide for one

FTR: waiting for the old relation implementation to get dropped, then we might even be able to drop the field alltogether


Error Opening Links using button in message

Hello,
When user is creating a new message, the link added in the button is tested using the preview method and the correct link opens. However, once message is sent out, the button opens a different link than the one seen in the preview.
This is a problem as the link opening is inconsistent between the actual message and the one in the preview.
It's the same link but in preview opens one and in the actual message opens another.
Is this a bug?

Fixed on CC Community Fork - v4.45


Add BinaryFbetaResult

Codecov Report
Attention: Patch coverage is 83.67347% with 8 lines in your changes missing coverage. Please review.

Project coverage is 99.59%. Comparing base (2077869) to head (da2ce6b).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

src/arkas/result/fbeta.py
83.33%
8 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main     #226      +/-   ##
===========================================
- Coverage   100.00%   99.59%   -0.41%
===========================================
  Files           81       82       +1
  Lines         1943     1992      +49
  Branches       181      184       +3
===========================================
+ Hits          1943     1984      +41
- Misses           0        8       +8

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


Allow globally suppressing compiler warnings

When adding NuGet packages with common dependency but with different versions in a Jupyter notebook, compiler warning CS1701 occurs. To suppress this, each code cell needs #pragma warning disable CS1701. This becomes distracting when using a notebook as an interactive tutorial, so it would be great if suppression could be done globally - perhaps even a Directory.Build.props file in a parent or ancestor directory (like MSBuild project files). Or, at the very least, if a single #pragma would disable a warning for all cells.
An example of the error without the #pragma would be using the following in a code cell:
#r "nuget:Azure.Identity"
#r "nuget:Azure.Security.KeyVault.Secrets"

(8,27): warning CS1701: Assuming assembly reference 'Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8' used by 'Azure.Security.KeyVault.Secrets' matches identity 'Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8' of 'Azure.Core', you may need to supply runtime policy

Here's an example of where I have to add #pragmas to suppress these, and on one of the executable blocks it doesn't even work (see toward the bottom where the warning is still emitted): https://github.com/heaths/azure-sdk-notebooks/blob/master/dotnet/Secrets in Key Vault.ipynb

I have a block that is emitting 3 of these warnings, and the pragma statement only removes 1 of them, leaving the other 2 present.

We would probably implement a fix for this related to #890. The general goal there is to make sure that we use existing, familiar implementations as much as possible.
One theory as to why the #pragma doesn't seem to stick is that each submission (e.g. cell) is actually compiled into a different assembly. Any thoughts on this, @tmat?

RE CS1701: This warning is obsolete and shouldn't be reported at all. The script engine can suppress warnings globally.
RE #pragma - yes, these are scoped per compilation unit, i.e. submission. The host can define host-level command to suppress warnings globally.

Any news on this? This is super actionable as especially in the AI craze, there are a lot of prerelease packages from Microsoft, OpenAI and others, and every cell that uses anything from those packages currently needs to have the pragma warning disable.

One approach that could work would be a magic command (e.g. something like #!suppress-warnings CS1701) that suppresses a warning for current and future submissions. This would probably be fairly simple to add even for a first-time contributor to the project.


feat: :sparkles: Concatena '&' em url já parametrizadas

Ao ler uma url com a existencia de parametros ele concatena com '&'

Codecov Report

Merging #148 (fce3f61) into develop (8042aaf) will decrease coverage by 0.29%.
The diff coverage is 60.00%.

@@             Coverage Diff             @@
##           develop     #148      +/-   ##
===========================================
- Coverage    95.54%   95.24%   -0.30%
===========================================
  Files           44       44
  Lines         1280     1284       +4
  Branches        74       76       +2
===========================================
  Hits          1223     1223
  Misses          44       44
- Partials        13       17       +4

Flag
Coverage Δ

integrationtest
95.24% <60.00%> (-0.30%)
:arrow_down:

unittests
95.24% <60.00%> (-0.30%)
:arrow_down:

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

Impacted Files
Coverage Δ

test/models/GA.spec.ts
100.00% <ø> (ø)

src/ts/models/Adobe.ts
94.33% <50.00%> (-3.70%)
:arrow_down:

src/ts/models/GA.ts
97.22% <50.00%> (-2.78%)
:arrow_down:

test/models/Adobe.spec.ts
100.00% <100.00%> (ø)

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 8042aaf...fce3f61. Read the comment docs.


eror wnen i firstly go play

Hi @51bear, thanks for the report.
From the logs I take that you selected GooKeeper to play.
We are aware that this gameplay mode crashes the game and decided to sunset GooKeeper as its content is not worth the effort to fix it.
It will be removed with the next release.
For playing, I'd recommend the JoshariasSurvival or MetalRenegades gameply modes.
I'll close this issue as it's a known problem we decided to not fix.


JAVA installation on Windows platform

SUMMARY
JAVA is not installed to Windows hosts with 'win_chocolatey' module because of incorrect Ansible fact is used
ISSUE TYPE

Bug Report

COMPONENT NAME

task/main.yml
task:

name: "Choose platform based task "

ANSIBLE VERSION

ansible 2.5.5

CONFIGURATION

ALLOW_WORLD_READABLE_TMPFILES(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = True
ANSIBLE_FORCE_COLOR(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = True
DEFAULT_HOST_LIST(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = [u'/etc/ansible/se-provision/playbooks/sdl/vagrant_inventory']
DEFAULT_MODULE_PATH(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = [u'/etc/ansible/se-provision/library']
DEFAULT_ROLES_PATH(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = [u'/etc/ansible/se-provision/roles']
HOST_KEY_CHECKING(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = False
RETRY_FILES_ENABLED(/etc/ansible/se-provision/playbooks/sdl/ansible.cfg) = False
OS / ENVIRONMENT

STEPS TO REPRODUCE

- name: Install java
  hosts: windows
  roles:
    - role: ../../roles/ansible-role-java
      java_major_version: 8
      java_package: "jre"
      transport: "win-chocolatey"

EXPECTED RESULTS

Get jre 8 installed to Windows hosts with win_chocolatey module
ACTUAL RESULTS

Instead of 'tasks/system/Windows.yml' 'tasks/system/not-supported.yml' is called by 'tasks/main.yml'

in 'tasks/main.yml' Ansible fact needs to be changed:

name: "Choose platform based task "
include_tasks: "{{ platform }}"
with_first_found:

- "system/{{ ansible_facts.system }}.yml"        - like it is now
- "system/{{ ansible_os_family }}.yml"          # should be like this I suppose to call 'Windows.yml'
- "system/not-supported.yml"

loop_control:
loop_var: platform


{ungoogled-,}chromium,chromedriver: 119.0.6045.199/105 -> 120.0.6099.71

Description of changes
Note: requires #271677 (17ca7f65295805d8ebfeef2b81b68122fb30886e specifically) -- will undraft when #271677 has been merged into master.
https://chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop.html
This update includes 10 security fixes.
CVEs:
CVE-2023-6508 CVE-2023-6509 CVE-2023-6510 CVE-2023-6511 CVE-2023-6512
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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

[x] Fits CONTRIBUTING.md.

nix-build -A stable -A ungoogled nixos/tests/chromium.nix
/nix/store/mdd1nzcfwkinw5mmjw3vnyns7qqknkrv-vm-test-run-chromium-stable
/nix/store/96fmx186k2yhk3ngcpdz0c5zn04mq0j1-vm-test-run-chromium-ungoogled

Result of nixpkgs-review pr 272487 run on x86_64-linux 1

23 packages built:

chromedriver
chromium
chromium.sandbox
fast-cli
google-chrome
mermaid-cli
mermaid-filter
netflix
percollate
playwright-test
puppeteer-cli
python310Packages.pytest-playwright
python310Packages.pytest-playwright.dist
python311Packages.pytest-playwright
python311Packages.pytest-playwright.dist
selendroid
selenium-server-standalone
sharedown
sitespeed-io
ungoogled-chromium
ungoogled-chromium.sandbox
vhs
wayback

nix-build nixos/tests/chromium.nix -A ungoogled -A stable
/nix/store/755rn0pjr9vqm4g3g2x1jxgdisfy0x1l-vm-test-run-chromium-ungoogled
/nix/store/f9i1x8qkabdl6ffhvc4r9iigpfiywch4-vm-test-run-chromium-stable


Try deeper galaxy model and wider bottleneck

We'd particularly like to see the figure-eight pattern disappear from the residual images.

@ZachariahPang has tried this, it just didn't work; so I think we can close this issue.


Work Package wp-md.csv

I would like to work on this please!

Results of Phase 1
wp-md-results - Sheet1.csv

I completed this work package.

wp-md-results.csv

I would like to work on this please!

I completed this work package.

Results of Phase 1
wp-md-results.csv

I would like to work on this please!

Results of Phase 2
wp-md-results.csv

Results of Phase 1
wp-md-results.csv


How to handle std::vectorstd::uint8_t

I have built my own sockets layer, which works for an application I am working on.
The response from the Send returns a "complex" type containing the following data
std::vector<std::string> headers;
std::vector<std::uint8_t> body;

The reason the complex type represents the body as vector of bytes is the api will also transfer binary data as well as JSON string data.
My problem is when I do HTTP post, my data is sent correctly to the server. It updates the database, and then returns to my client. In the response, there is JSON data. I am trying to work out how to construct a JSON "object" that I can call contains to query the structured information for the certain returned data.
I have tried
nlohman::json _json(_response.body);
but it appears unable to find the nodes when I query the using contains. I have manually tried converting the vector of bytes to a string and parsing that, to no available.
I guess what I am asking for, is what section of the help should I look at more closely, to find the solution.

Hello Elliot Alderson,
How about something like
nlohmann::json j;
j = nlohmann::json::parse(response.body.begin(), response.body.end());


Cannot bind parameter 'NewerThan'

I watched your video and I never knew what I was missing, really cool.
I tried to install it on PS 5.1 and I am getting the below error:
Cannot bind parameter 'NewerThan'. Cannot convert value "True" to type "System.DateTime". Error: "The string was not recognized as a valid DateTime. There is an unknown word starting at
index 0."
Not sure if anyone else is getting this.

Ok,
I am already doing some digging, a few things I am noticing.

I have OneDrive mapped to my profile path $PROFILE
E:\OD\OneDrive - [company]\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

In the code you are querying a different path:
$env:userprofile + "\Documents\WindowsPowerShell"
Which returns "C:\Users[user]\Documents\WindowsPowerShell"

Note sure whey you are using:
If ((Test-Path -Path ($env:userprofile + "\Documents\WindowsPowerShell") -ne "True")) {

Wouldn't:
If (-not (Test-Path -Path ($env:userprofile + "\Documents\WindowsPowerShell"))) {
work the same?  I know it does not throw the error above

Here is how I addressed the issue
    #check to see if OneDrive Profile is registered
    if ($PROFILE.StartsWith($ENV:OneDrive)) {
        $varProfilePath = $ENV:OneDrive
    }
    elseif($PROFILE.StartsWith($ENV:OneDriveConsumer)){
        $varProfilePath = $ENV:OneDriveConsumer
    }else{
        $varProfilePath = $env:userprofile
    }

    if (-not(Test-Path -Path $PROFILE -PathType Leaf)) {
        try {
           # Detect Version of Powershell & Create Profile directories if they do not exist.
           if ($PSVersionTable.PSEdition -eq "Core" ) {
               If ((Test-Path -Path ($varProfilePath + "\Documents\Powershell")) -ne "True") {
                   New-Item -Path ($varProfilePath + "\Documents\Powershell") -ItemType "directory"
               }
           } elseif ($PSVersionTable.PSEdition -eq "Desktop") {
               If ((Test-Path -Path ($varProfilePath + "\Documents\WindowsPowerShell") -ne "True")) {
                   New-Item -Path ($varProfilePath + "\Documents\WindowsPowerShell") -ItemType "directory"
               }
           }

            Invoke-RestMethod https://github.com/ChrisTitusTech/powershell-profile/raw/main/Microsoft.PowerShell_profile.ps1 -o $PROFILE
            Write-Host "The profile @ [$PROFILE] has been created."
        }
        catch {
            throw $_.Exception.Message
        }


[ENG-122] Optimize pagecounter id-splitting data migration

Purpose
Speed up the pagecounter migration and make run incrementally on a Production environment (if not DEBUG_MODE). The migration will run on the whole DB at once, while the management command will run one page at a time only. When doing a forward migration with the management command, it will send a message to Sentry when it is complete.
The reverse migration isn't strictly necessary. It's handy for debugging, but the proper reverse migration will just drop the columns from the table, so there's not as much work gone into notifying if the reverse migration is complete.
And I am hoping to make this pattern kind of a more regular thing, so if it seems like a good idea, we can formalize it a bit better.
Changes

Add a management command to do the migration work
Update the forward and reverse migrations to be pure SQL
Add a check for DEBUG_MODE to know whether to run the migration automatically.

Ticket
https://openscience.atlassian.net/browse/ENG-122

LGTM! 🚢


Error field of GetResult of type string instead of ErrorDetails

WHAT

Change the type of field Error to string instead of ErrorDetails.

WHY

Error field is used only in MultiGet which returns a string error rather than ErrorDetails. If an error occurred for one of the documents in the MultiGet request this causes the following unmarshalling error:

json: cannot unmarshal string into Go value of type elastic.ErrorDetails
this obscured the actual error.
WHO
@yayalice

To clarify the above mentioned error happens when running the following code:
multigetRequest = es.MultiGet()

noSourceContext := elastic.NewFetchSourceContext(false)

for _, docID := range docIDs {
	request := elastic.NewMultiGetItem().
		Index(index).
		Type(docType).
		Id(docID).
		FetchSource(noSourceContext)

	multiGetRequest.Add(request)
}

response, err := multiGetRequest.Do(context.Background())

The faulty unmarshalling happens at mget.go#L134

Hmm... if I look at the Java source and the response from HTTP requests (see below), it seems that it returns *ErrorDetails not a string, but maybe I'm missing something.
$ curl -H 'Content-Type: application/json' -is 'http://localhost:9200/no-such-index/_mget?pretty' -d '{"ids":["1", "2"]}'
HTTP/1.1 200 OK
content-type: application/json; charset=UTF-8
content-length: 1352

{
  "docs" : [
    {
      "_index" : "no-such-index",
      "_type" : null,
      "_id" : "1",
      "error" : {
        "root_cause" : [
          {
            "type" : "index_not_found_exception",
            "reason" : "no such index",
            "resource.type" : "index_expression",
            "resource.id" : "no-such-index",
            "index_uuid" : "_na_",
            "index" : "no-such-index"
          }
        ],
        "type" : "index_not_found_exception",
        "reason" : "no such index",
        "resource.type" : "index_expression",
        "resource.id" : "no-such-index",
        "index_uuid" : "_na_",
        "index" : "no-such-index"
      }
    },
    {
      "_index" : "no-such-index",
      "_type" : null,
      "_id" : "2",
      "error" : {
        "root_cause" : [
          {
            "type" : "index_not_found_exception",
            "reason" : "no such index",
            "resource.type" : "index_expression",
            "resource.id" : "no-such-index",
            "index_uuid" : "_na_",
            "index" : "no-such-index"
          }
        ],
        "type" : "index_not_found_exception",
        "reason" : "no such index",
        "resource.type" : "index_expression",
        "resource.id" : "no-such-index",
        "index_uuid" : "_na_",
        "index" : "no-such-index"
      }
    }
  ]
}

The exception in ES is created here. However, ElasticsearchException.generateFailureXContent(...) has a detailed parameter which can be set to false to return a simple string instead (though detailed is true for MultiGet). So maybe there's a way to trigger a simplified error message. In that case I think Elastic should still use *ErrorDetails and initialize with the string returned from ES.
Can you construct a query that returns a string only?

I am closing this as I think what happened was that I used the wrong library version. Will reopen if this was not the case