"Autocomplete" page's playground will get 'TypeError' using IE 11

Autocomplete page
Click on "Load in playground", it will show
TypeError: Object doesn't support property or method 'from'

Using IE 11, win10. Edge and Chrome works.

Ok! Thanks for reporting!

@javivelasco FYI you can always use virtualbox + images from http://modern.ie

Very nice, I'll give it a try. Thanks @nathanmarks !

@javivelasco If you have vmfusion or parallels, they tend to perform a bit better than virtualbox for these.


Update requirements.rst

reflect the updates on the document as well..

Hi @laucianexones,
Thanks for the PR! We've decided to add instructions to run 'tridentctl images' to get the list of container images needed for a particular version of Trident. This should lower the confusion of needing to have a version of this table in the documentation for every patch release.


"build_hash" : "unknown" in Opensearch 1.2.3

Title: "build_hash" : "unknown" in Opensearch 1.2.3
We have built the OpenSearch 1.2.3 source code using "./gradlew assemble -Dbuild.snapshot=false"
The build was successful and a non-snapshot version was generated,
but I see "build_hash" : "unknown", in Rest GET / API call.
To Reproduce
Downloaded source code : https://github.com/opensearch-project/OpenSearch/releases/tag/1.2.3
./gradlew assemble -Dbuild.snapshot=false
Used no-jdk-linux-tar (Dir: opensearch/distribution/archives/no-jdk-linux-tar/build/distributions)
rest api GET method returns below o/p with "build_hash" : "unknown",
rest GET /
{
"name" : "eric-data-search-engine-data-0",
"cluster_name" : "eric-data-search-engine",
"cluster_uuid" : "G-5gK8QFT7WJ3Mfr2HMVVQ",
"version" : {
"number" : "7.10.2",
"build_type" : "tar",
"build_hash" : "unknown",
"build_date" : "2021-12-27T09:04:55.654676Z",
"build_snapshot" : false,
"lucene_version" : "8.10.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "The OpenSearch Project: https://opensearch.org/"
}
Expected behavior
rest api GET method should return some "build_hash" : "xxxxx",
**Host/Environment

OS: no-jdk-linux-tar
Version 1.2.3

Note: we have used the same procedure to build OS 1.0.0.

This looks suspicious, did you get a chance to debug it? AFAIK this just returns current version .hash().

sorry, haven't debug.
I have downloaded the tar.gz file from https://opensearch.org/versions/opensearch-1-2-3.html and tested it.
facing the same issue.
rest GET /
{
"name" : "eric-data-search-engine-ingest-tls-865464d8fc-9bhlk",
"cluster_name" : "eric-data-search-engine",
"cluster_uuid" : "aQVf6McmR6CNAOpJIsMphw",
"version" : {
"number" : "7.10.2",
"build_type" : "tar",
"build_hash" : "unknown",
"build_date" : "2021-12-27T09:04:55.654676Z",
"build_snapshot" : false,
"lucene_version" : "8.10.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "The OpenSearch Project: https://opensearch.org/"
}
followed the same procedure to build OS 1.0.0 source code, this issue was not happening in OS 1.0.0.

I'll move it to OpenSearch, something has changed.

Do we have any update?

Do we have any update?

I don't think anyone is looking at this, appreciate if someone/you could.

I am having hard time reproducing this, but I have definitely seen this elsewhere. Something else is going on.
@balar06 care to help?
$ uname -a
Linux ip-172-31-42-1 5.11.0-1027-aws #30~20.04.1-Ubuntu SMP Thu Jan 13 11:46:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ wget https://artifacts.opensearch.org/releases/bundle/opensearch/1.2.3/opensearch-1.2.3-linux-x64.tar.gz
tar vfxz opensearch-1.2.3-linux-x64.tar.gz

$ cd opensearch-1.2.3
$ ./opensearch-tar-install.sh

$ curl -k https://localhost:9200 -uadmin:admin
{
  "name" : "ip-172-31-42-1",
  "cluster_name" : "opensearch",
  "cluster_uuid" : "7FRzJ7m4T469KW_dLBOrlg",
  "version" : {
    "distribution" : "opensearch",
    "number" : "1.2.3",
    "build_type" : "tar",
    "build_hash" : "8a529d77c7432bc45b005ac1c4ba3b2741b57d4a",
    "build_date" : "2021-12-21T01:36:21.407473Z",
    "build_snapshot" : false,
    "lucene_version" : "8.10.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

This is likely coming from https://github.com/opensearch-project/OpenSearch/blob/main/server/src/main/java/org/opensearch/Build.java#L115 which looks suspiciously over-engineered for returning a build hash, we just need a reliable way to reproduce.

@balar06 how can we reproduce this issue? Do you still see this issue on latest OpenSearch 2.1 or OpenSearch 1.3.4 ?

later I haven't faced this issue.

Let's close.


Use Loop::Break/Continue instead of bool in visitor of ForEachActiveO…

Problem
Use a bool to control when to break the loop is not intuitive.
Change overview

Use Loop::Break and Loop::Continue instead of bool in visitor of ForEachActiveObject
ForEachActiveObject will return Loop::Break or Loop::Finish

Testing
Checked unit-tests

Fast tracking given this is just renaming.


Handle error causes by project.json comments

Original issue https://github.com/OmniSharp/omnisharp-vscode/issues/226
Brief: comments in project.json is not supported in dotnet-cli json parser. It throws exception and interrupts editor.

This isn't going to happen at this point.


Xcloud

Hi, until yesterday, when I got version 1.2.1, I was able to press the home button on my controller without it activating the Xcloud menu during the game. With 1.3.1, this came back… Can it be removed again? Since I don’t use an official joystick, my home button is also the button that turns off the controller…
I don’t know if that was a coincidence. Thanks for the script.

I don't remember changing anything that could cause this. You could verify by downgrading the script to 1.2.1.

Hi redphx. Sorry for not returning, I ended up getting distracted this Sunday. Well, even doing a downgrade or a clean installation of version 1.2.1, it still enters the Xcloud menu when pressing home. Sorry, did you add this feature that inhibits the Xcloud menu during the game? It may have been some momentary coincidence that I associated with your script, or your script somehow temporarily inhibited it.

I still don't think it's because of Better xCloud. Or you could disable the script entirely and check again.

From the way you wrote, I was scared. What happened is that before your script, when pressing the home button on the controller, it entered the Xcloud menu, this is normal. When I installed your script for the first time, it somehow inhibited this Xcloud menu, that is, when pressing the home button, it no longer entered the menu. This was beneficial for me.

Eu ainda não acho que é por causa do Better xCloud. Ou você pode desativar o script completamente e verificar novamente. Talvez tenha sido um bug do lado do xCloud e eles o corrigiram.

I still don't think it's because of Better xCloud. Or you could disable the script entirely and check again. Maybe it was a bug on xCloud's side and they fixed it.

It may have been that. I confess it was very good. I think we can now close this topic, since it did not come from your script, this menu inhibitor.


Create new FacilityMatch when all matches rejected

Overview

create a new FacilityMatch record along with a new Facility record
when all other potential matches have been rejected through the UI
add test to verify the FacilityMatch count increments on rejecting
all matches

Connects #255
Demo

Testing Instructions

get this branch, then run the tests to verify that they pass
process a list, then reject all matches for one item in the UI. verify that it changes to NEW_FACILITY status and that it now has one more FacilityMatch than it did before: one created for the new facility

Great, thanks!


vhost-user-vsock implementation

Here is the initial implementation of a fully functional vhost-user-vsock device as part of the GSoC project with @stefano-garzarella and @fidencio. The device has been tested (end-to-end) using iperf and netcat. More testing can be performed once we have the queue mocking framework ready.

@stefano-garzarella I have pushed the requested changes. For tracking the allocated local ports I use a simple bitmap, which restricts the number of concurrent connections to 32 only. This reduces the overhead of maintaining a set. Is this is a fair restriction/assumption?

@stefano-garzarella I included a set to track the allocated port numbers on the host. Also fixed the clippy warnings. One major change is that I squashed all change into 1 commit(there was a lot of unrelated changes which made it harder to group them correctly). However, rebasing the branch onto main causes the i2c device build to fail, and have proposed a temporary fix in pull request #14.

@stefano-garzarella I included a set to track the allocated port numbers on the host. Also fixed the clippy warnings.

@harshanavkis great!

One major change is that I squashed all change into 1 commit(there was a lot of unrelated changes which made it harder to group them correctly).

I think is fine to squash on a single commit, but please update the title and the description of this commit, describing that you're adding a vhost-user-vsock application (virtio-vsock device emulation) and a minimal description of the device (something similar of the first lines of the README).

However, rebasing the branch onto main causes the i2c device build to fail, and have proposed a temporary fix in pull request #14.

Cool, I'll take a look.

This came up in the rust-vmm sync meeting so mentioning for reference: https://github.com/rust-vmm/vm-virtio/issues/128

@stefano-garzarella @stsquad I tried addressing your comments and added more tests to improve the coverage. I am working on testing other parts of the device now. Let me know what you think.

@harshanavkis
I would expect other crates in this workspace to follow what is being done for I2C, where we have reached after lots of reviews. The test coverage is very good as well now. We are also using mock-queue to test the stuff where we need to process virtqueues.
I still see a lot of mismatch if I compare this with I2C and that is the bare minimum, in my point of view, that everyone needs to have. It is more about just copying what's already done for I2C.
Thanks.

During testing I failed to put CONNECT 1234 here which caused a panic in the server:
./target/debug/vhost-user-vsock --socket ~/lsrc/qemu.git/builds/arm.all/vsock.sock --uds-path /tmp/vsock
thread 'vring_worker' panicked at 'called Result::unwrap() on an Err value: UnixRead(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })', vs
ock/src/vhu_vsock_thread.rs:204:80
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
which should probably be handled a little better. Reconnecting to the socket from the host side makes it unable to process the connection and pass a message.

;;; Type C-c C-c to include your comment
I you don't pass CONNECT 1234 here you end up with:
✗  ./target/debug/vhost-user-vsock --socket ~/lsrc/qemu.git/builds/arm.all/vsock.sock --uds-path /tmp/vsock
thread 'vring_worker' panicked at 'called Result::unwrap() on an Err value: UnixRead(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })', vs
ock/src/vhu_vsock_thread.rs:204:80
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
and further attempts to reconnect (even closing nc and reconnecting) fail.

So I think this is looking pretty good and almost ready to merge. I think moving to the virtio-vsock abstraction can be left until later (obviously as it's not merged upstream) but I have checked it's possible. The only outstanding thing from my point of view is can we justify the implementation of LocalTxBuf or use a external crate for it.

@stsquad thanks for the review!
@harshanavkis would be cool to address the latest comments and merge this PR. Let me know if I can help in some way!

Hi, just wanted to let you know that we published virtio-vsock 0.1.0, which has the VolatileSlice packet implementation that we talked about.

@lauralt cool, thanks for the update!
It would be great to reuse it in this MR and merge it. If @harshanavkis doesn't have time and someone wants to complete it is fine :-) If not, I'll try to reserve some time in the next month to complete this MR. It's a shame not to merge it since we are already in a good state.

I restarted to work on this here: https://github.com/stefano-garzarella/vhost-device/tree/vsock-stefano
For now I did the following steps on top of the @harshanavkis work:

updated some dependencies (e.g. vm-memory, etc.)
replaced the deprecated App::from_yaml()
fixed some new clippy warnings
addressed @stsquad comments (panic when CONNECT 1234 is worng, use virtio-vsock 0.1.0 crate from @lauralt )

In the next days I'll clean the git history and do more testing, but since I can't push on this branch, should I open a new PR when it is ready?

I restarted to work on this here: https://github.com/stefano-garzarella/vhost-device/tree/vsock-stefano
For now I did the following steps on top of the @harshanavkis work:
* updated some dependencies (e.g. vm-memory, etc.)

* replaced the deprecated App::from_yaml()

* fixed some new clippy warnings

* addressed @stsquad comments (don't panic when CONNECT 1234 is wrong, use [virtio-vsock 0.1.0](https://crates.io/crates/virtio-vsock) crate from @lauralt )

In the next days I'll clean the git history and do more testing, but since I can't push on this branch, should I open a new PR when it is ready?

New PR here: https://github.com/rust-vmm/vhost-device/pull/216


[http/file_server] Show local network IP

Is your feature request related to a problem? Please describe.
When developing with a local file server, it's often useful to be able to connect to it from other devices (for example, to test how a website looks on mobile). file_server ./path only gives me the localhost address, and I have to check in ifconfig to find my IP address:
➜ file_server .
Listening on http://localhost:4507/

Describe the solution you'd like
Vercel's server prints this output:
➜ npx serve .
(node:30004) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

   ┌────────────────────────────────────────────┐
   │                                            │
   │   Serving!                                 │
   │                                            │
   │   - Local:    http://localhost:3000        │
   │   - Network:  http://<IP_ADDRESS>:3000   │
   │                                            │
   │   Copied local address to clipboard!       │
   │                                            │
   └────────────────────────────────────────────┘

It's be great if file_server showed the "Network" IP too.
Describe alternatives you've considered

This is a valid use case. However, finding and printing the network address of the current machine seems out of scope for std/http/file_server. The reason is that network interfaces vary across machines and OSs. Instead, I think we should provide an example in the documentation that shows how Deno.networkInterfaces() can be used with Deno.serve()'s onListen() option to print the current machine's network address.

@iuioiua Many other file serving tools do this. For example serve and vite dev both print the local network interface when starting up. I think we should also do this in when running deno run -A jsr:@std/http/file_server. It's a very trivial change for us, and it improves user experience. I think we should do it.

Okay, fair points. Would it be worth making this default onListen() behaviour for Deno.serve() instead?

No, I don't think so. This is particularly useful when running a development server like is common with the file_server tool

Now the core team seems strongly against this addition..

Oh, that's unfortunate. I have been using this since it was released, and it has been incredibly useful when developing across multiple devices (mostly for testing on mobile).

To elaborate, the core team is against having this be included in default behavior, as it requires the user to use the --allow-sys permission flag. #5540 aims to improve the situation by making this behavior easily opt-in.


from future import print_function

None of the future features are implemented, including the print function.

https://github.com/google/grumpy/pull/23 has been merged. Thanks again for implementing this!


Allow mapping custom field values via custom annotations

What would you like to be added:  I'd like to add the ability to map custom annotations to custom field names, allowing you to set custom fields using custom annotations values.
An example values file for logging might look like this:
customMetadataAnnotations:
  - name: "application"
    annotation: "splunk.com/application-field"

And then, by specifying an annotation splunk.com/application-field on a pod or namespace would map the given value to a custom field application in Splunk for log events originating from that pod or namespace.
Why is this needed: It's currently not possible to easily customize custom fields with values that may vary from pod to pod, it's only possible to specify static values.  I have tried specifying a static value that included ${record.dig(...)} type expressions, but, because in the config map, the value is wrapped in "", it's error-prone and doesn't quite behave as expected.

Nice! Add ability to set the linebreaking to that order and we really cooking!!

@matthewmodestino do you mind creating a separate issue with your thoughts, that way we can get on it for next release

will do!

@chaitanyaphalak https://github.com/splunk/splunk-connect-for-kubernetes/issues/398


A regex?

You link to a document that says don't use a regex, and then use a regex. At work, we send about 1.6 billion emails a day. We agree with the article. Search for @.

Yes, a regexp is not enought, that's why the pkg provide a method to validate the domain and the mailbox. I prefer to follow the advice of the W3C for the regexp, which gives us a simple regexp, a little more than just '@' : https://www.w3.org/TR/html5/forms.html#valid-e-mail-address


Prometheus scrape config that makes the dashboard work is missing

I've been trying to follow the documentation to get kafka monitoring via prometheus and grafana working. Kafka is working, prometheus is working, grafana is working, but the prometheus configurations that actually scrape the kafka metrics such that the grafana dashboard would work are missing. Without the scrape configuration prometheus does not scrape the JMX metrics exposed by kafka, zookeeper, etc.

Hi
we use the prometheus chart from the stable repository (stable/prometheus). The image jimmidyson/configmap-reload is used there to create dynamically the scrape configuration. The annotation "prometheus/scrape: true" is already set by this chart.
For example: https://github.com/confluentinc/cp-helm-charts/blob/master/charts/cp-kafka/templates/statefulset.yaml#L26

annotation is not work on prometheus. Only servicemonitor


fix small formatting error (missing space)

every time I read the file, I see this and it disturbs me a lot :D if it's too small for a commit, if possible add it to a bigger change
Thanks

Changed commit message slightly and rebased into master: https://github.com/rycee/home-manager/commit/206a4e17b56433768a0ecd83993e7c24feab2937. Thanks for the contribution!


[1.10] fix ui headers to allow ui being opened in iframe

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
https://jira.mesosphere.com/browse/DCOS-45280
Related tickets (optional)
Other tickets related to this change:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label [Ready for Review]

@DanielMSchmidt well, there is an integration test 🤷♂  We could add a system test to our repo…
@brandonc @natmegs @GeorgiSTodorov we need new reviews after I rebased (Github kept them, but mergebot dismissed…) also EE PR needs reviews 🙇

@mesosphere-mergebot label [ship it]


First proof-of-concept of Datasette Library

Refs #417. Run it like this:
 datasette -d ~/Library

Uses a new plugin hook - available_databases()

Is this feature covered by any more recent updates to datasette, or via any plugins that you're aware of?


Additional behaviour in io.on('connection')

I am using socketio-jwt v2.3.1. I want to put additional behaviour in the io.on('connection') event handler. I tried the following:
io.on('connection', function(socket) {
   // do other stuff first

   // authorize
   return socketioJwt.authorize({
     secret: // app secret,
     timeout: 15000
  })(socket)
})

But this threw the following error:
      var Namespace = Object.getPrototypeOf(server.server.sockets).constructor
                                                                                ^
TypeError: Cannot read property 'sockets' of undefined

Is it possible do add additional behaviour to the connection event like this?

I know this issue has been open for a while, but I've found two ways to do this
io.sockets.on('connection', function (socket) {
    console.log('new connection');
});
io.sockets.on('connection', socketioJwt.authorize({
    secret: secret,
    timeout: 15000
}));

Or, using magic...
 io.sockets.on('connection', function (socket) {
   console.log('websocket: new connection');
   socketioJwt.authorize({
       secret: secret,
       timeout: 15000
   }).bind(io.sockets)(socket);
});

@g-murray-sreams I tried your code and it works fine, but when I try to
use it inside a callback function it doesn't work anymore.
I know that I just have to adapt the 'bind' method. I tried
a few things but I am not capable of make it work.
io.sockets.on('connection', function(socket) {

  // Do stuff

  myfunction(arg1, arg2, function(arg1) {
    console.log('websocket: new connection');
    socketioJwt.authorize({
      secret: secret,
      timeout: 15000
    }).bind(io.sockets)(socket);
  });
});

This is what I get:
node_modules/socketio-jwt/lib/index.js:52
        accept(error);
        ^
TypeError: undefined is not a function
    at Object.defaults.fail (/home/user/nodeapp/node_modules/socketio-jwt/lib/index.js:52:9)
    at /home/user/nodeapp/node_modules/socketio-jwt/lib/index.js:106:21
    at /home/user/nodeapp/node_modules/socketio-jwt/node_modules/jsonwebtoken/index.js:86:18
    at process._tickCallback (node.js:415:13)

Guys, thank you very much for reporting this. I think I fixed this issue in v4.3.
Can you give it a try?
Thanks

@jfromaniello I have just checked it and it's working fine in v4.5.0. You can close this one.


Handler response only with 200

I am use Unbox in my project, however on request with server, the return is only true, a String . Is there any way to parser it with Unbox? Some trick of a Model for it?

HI @douglasalexandre. The response that you are getting is not a JSON object, and can therefor not be handled by Unbox, NSJSONSerialization, or any other API that handles JSON. It's easier if you just decode the NSData that you downloaded into a String and compare it to true.

Ok, @JohnSundell. In fact, Its was just doubt! :) Thanks for answer. 👍

No problems 👍


It doesn't work on MacOS

No problem with windows,
It doesn't work on MacOS

Which one plugin?

哪一个插件？

desktop_webview_window: ^0.0.5

Which one plugin?

desktop_webview_window: ^0.0.5
Desktop Web View for Macos also not working on my machine. I m getting this issue.

Can you describe more details about you usage?

Is the example works on your computer?
OS verison?
Flutter version?
Which website are you browsing?
Is there any warning or errror log  print?

Which one plugin?

desktop_webview_window: ^0.0.5
Desktop Web View for Macos also not working on my machine. I m getting this issue.

It seems the build error was caued by swift name shadowed.
Thanks for your details, I will fix this soon.

Can you describe more details about you usage?

Is the example works on your computer?
OS verison?
Flutter version?
Which website are you browsing?
Is there any warning or errror log  print?

I'm building the example project.
OS Version - 10.15.7
Flutter version:-Channel dev, 2.6.0-11.0.pre

Can you describe more details about you usage?

Is the example works on your computer?
OS verison?
Flutter version?
Which website are you browsing?
Is there any warning or errror log  print?

MacOS 11.5.1 or 12.0
Flutter version:2.5.3


few refactoring)

Hey @itwillwork !
This is really nice and tidy thanks for the pull request.
I'm not going to merge this time since I want to avoid as many dependencies as possible, these can be done with minimal code, whereas the merge lodash function is not easily replaceable.
Sorry, but thanks again for taking the time. 👍


Svg morphing animation Issue#166

****WIP Issue #166****
Related Issue
-SVG Morphing Animation Issue#166
Closes: #166
Describe the changes you've made
Work in Progress
Type of change
What sort of change have you made:

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

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Checklist:

[ ] I have commented my code, particularly whereever it was hard to understand.
[ ] My code follows the guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots
Add Screenshots to show your changes
Additional Info (optional)
Any additional information you want to give

@Inventor77 , please explain the changes you made and add screenshots too.

@Inventor77 , please explain the changes you made and add screenshots too.

@Utkarsh1999 Sir I have not made any changes just made a work in progress PR

@Inventor77 , please explain the changes you made and add screenshots too.

@Utkarsh1999 Sir I have not made any changes just made a work in progress PR

Oh, there is no need to made such PRs. I am closing this PR, you can made a new one once you're done with your code.


v21.1.9 release notes

Fixes #10724.
Fixes #11637.

This change is

Should this be an actual "Note" callout? Either way, idk if the entire note needs to be in bold. Also, it probably follows that the sentence after the note, bold or in a callout or not, should be part of the same note.

Ha, I didn't notice the double asterisks when I was editing it. Fixed.

I guess this technically could be parsed as four metrics, but it might help to break it out.

Done.

Fixed a bug introduced in v21.1 where CockroachDB could return an internal error when performing streaming aggregation in some edge cases.

Done.


Key Vault: Treat Async client as a context manager

This is to avoid all of the "Unclosed client session" warnings that pop up

closing issue bc it's a duplicate of #7228


[DO NOT MERGE] Auto PR to update dependencies of mixer

This PR will be merged automatically once checks are successful.
none

This change is

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
7f466d62959f5a9935f49946e969891f921ee20a
link
/test mixer-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Off by 100 values still occur in Measurement.XYZ

Measurement.XYZ is off by a factor of 100 under some conditions. Unknown compatibility matrix between specio and colour...

Nevermind. 3hrs of sleep and working on a plane is a recipe for erroneous bug reports.


package build: selectively pass daisy args & pipeline shift

Concourse will try to interpolate variables even if they are not set in that case if the variable is not set concourse will fail with an "no such variable" kind of error - this change fixes that.
Additionally originally we set extra_repo to the wrong build pipeline, we set it to guest-agent-dev when we should have set it to guest-agent.

/lgtm


App crashes when touching screen with 3 fingers

Description
As mentioned on the title, the app crashes after touching the screen with three fingers both in development and production version.
I have a One Plus 2 device and I needed to take a screenshot of my app. It has Three-finger screenshot gesture control. The app simply restarts on the production version but displays the following error on development version.

Error Message
Cannot record touch end without a touch start.
Touch End: %s
 Touch Bank: %s {"identifier":2,"pageX":97,"pageY":320,"timestamp":78140617} [{"touchActive":false,"startPageX":198.3333282470703,"startPageY":270.3333435058594,"startTimeStamp":78140609,"currentPageX":198.3333282470703,"currentPageY":270.3333435058594,"currentTimeStamp":78140617,"previousPageX":198.3333282470703,"previousPageY":270.3333435058594,"previousTimeStamp":78140609},{"touchActive":false,"startPageX":293,"startPageY":306.6666564941406,"startTimeStamp":78140615,"currentPageX":293,"currentPageY":306.6666564941406,"currentTimeStamp":78140617,"previousPageX":293,"previousPageY":306.6666564941406,"previousTimeStamp":78140615}]

Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts<EMAIL_ADDRESS>npm ls react-native<EMAIL_ADDRESS>npm ls expo<EMAIL_ADDRESS>node -v: v7.4.0
npm -v: 4.6.1
yarn --version: 0.27.5
watchman version: "version": "4.7.0"

Also specify:

Operating system: MacOS Sierra 10.12.6 beta
Phone/emulator/simulator & version: One Plus 2

Hello! This appears to be an upstream React Native issue. I created an issue on the react-native repository for you: https://github.com/facebook/react-native/issues/15059
If possible please provide a link to an example application on Github where this happens for you. If it happens just on any new project, let us know in that thread. Thank you so much for the report!

@brentvatne This issue isn't on the app created with react-native init. Here's the app on the play store created with CRNA .
https://play.google.com/store/apps/details?id=com.ictechmedia.ictaward

The issue is device specific. It's only on One Plus 2. I've tested with some other devices, but they didn't crash.

@tusharkhatiwada - so it happens on a brand new app created with CRNA but not on a brand new app created with react-native init?

@brentvatne Sorry. I just tested with react-native init and it's showing the same error too. I had an App built few months back and wasn't showing the error. So that means the error is with the latest version of react-native.
Sorry, I opened the issue on wrong repo.

i find this problem too, do you have any solution?

@csgsky - sorry to hear that. I see you commented on https://github.com/facebook/react-native/issues/15059 -- that's your best bet for a resolution. feel free to investigate a solution on your own as well and submit a PR!

Same issue on OnePlus 5

I also have this problem and I have proposed some workarounds and possible solution on the react-native issue: https://github.com/facebook/react-native/issues/15059#issuecomment-366948308

Same issue on Oppo A57

Same issue on OnePlus 5T

Hi everyone, the upstream react native issue is where to track/report this. Thanks!


Proposal: Remove tagging for literals during evaluation

We use the ast::Literal type to represent "primitive values" in every representation. In particular, evaluation of binary and unary operations are done checking which Literal variant is being used in the operands.
However, when the code is lowered to the LIR we no longer need to differentiate integers and booleans. We could have a simple newtype struct Literal(i64) to represent all literals. This would simplify our bin_op and un_op functions in Machine to something like
match bin_op => {
    BinOp::Add => l1 + l2,
    BinOp::And => l1 && l2,
   ...
}

Advantages

Evaluation would be faster because it we wouldn't need to destructure literals to do operations over them.
The code inside machine would be simpler.
The memory usage would be lower. The size of ast::Literal is 128 bits (already taking #82 into account). This new literal would take 64 bits only.

Disadvantages

This puts more responsibility into the type system and other static checks we do.
Printing would become tricky. A program like print(1 > 2) would print 0 if we don't do some transformations beforehand like adding the type of what's being printed in the MIR.

In this system what would true and false be in terms of integers? 1 and 0?

A program like print(1 > 2) would print 0

It prints (1 > 2) because it doesn't evaluate its arguments. The problem is print(true > true) it would then print (1 > 1)

yes true and false would be 1 and 0.
We don't have polymorphism yet (I'm working on type inference so this will happen soonish). But when we do, we could dispatch each Print to a PrintInt, PrintBool and so on.
I think we should change Prints behavior to force evaluation.

Edit: I'll take care of that, I think I have an idea

Ok but do I hear some evil laughter somewhere 😈


Remove package.lock.json

Keeping this file is redundant if package.json already present
package.lock.json is automatically generated once user does npm install
Can be removed to the codebase lighter as well

Solved this issue with PR https://github.com/AntonyAshwin/Project-SESAPZG-504-569/pull/16


work progress

Hey there!
I discovered your mod, a few days ago. Yeah, almost year from initial commit :D
It didn't start (many game api updates, etc.), but it's pretty amazing.
Anyways, i have a question, why have you stopped developing ?
Thank you!

Hi,
I also think it would be great to build a City in coop-mode.
I would be happy if this project is going to be continued.
//Override

Hello Inlife and Override92,
I mainly stopped because I needed some in-depth knowledge of the unity engine so I picked up unity and slowly drifted away until I forgot about this.
Yeah, coop cities skylines sounds very tempting, but I am currently working (in my opinion) on a more interesting project atm.
Greetings

Thank you for response!
Im thinking over creating fork and continuing your work.
You made pretty solid base. :smile:
Thank you!

That'd be great Inlife! I would love to support you but I don't have the needed knowledge for that.
//Override

Great, that would be nice. Tell me how it works out for you :+1:


Random newline in Minecraft chat message

There seems to be a problem with the message formatting of minecraft ingame-messages. This might be linked to the newline insertion with hover-texts - this should obviously not happen with non-hover-texts...

Fixed in 2b842ca


Missing Nintendo - Sufami Turbo

find -iname *suf*
./monochrome/png/Nintendo - Sufami Turbo.png
./pixel/png/Nintendo - Sufami Turbo.png
./retroactive/png/Nintendo - Sufami Turbo.png
./neoactive/png/Nintendo - Sufami Turbo.png
./retroactive_marked/png/Nintendo - Sufami Turbo.png
./retroactive_marked/src/Nintendo - Sufami Turbo.svg

No content.

Missing Nintendo - Game and Watch
./monochrome-jagged/png/Nintendo - Game and Watch.png
./monochrome-jagged/png/? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
./monochrome-jagged/png/Game and Watch.png
./monochrome-jagged/png/Game and Watch-content.png
./monochrome/png/Nintendo - Game and Watch.png
./monochrome/png/? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
./monochrome/png/Game and Watch.png
./monochrome/png/Game and Watch-content.png
./monochrome/src/Nintendo - Game and Watch.svg
./monochrome/src/? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
./monochrome/src/Game and Watch-content.svg
./pixel/png/Nintendo - Game and Watch.png
./pixel/png/? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
./retroactive/png/Nintendo - Game and Watch-content.png
./retroactive/png/Nintendo - Game and Watch.png
./retroactive/png/Game and Watch.png
./retroactive/png/Game and Watch-content.png
./neoactive/png/Nintendo - Game and Watch-content.png
./neoactive/png/Nintendo - Game and Watch.png
./neoactive/png/Game and Watch.png
./neoactive/png/Game and Watch-content.png
./retroactive_marked/png/Nintendo - Game and Watch.png
./retroactive_marked/src/Nintendo - Game and Watch.svg

No content. We stopped using Nintendo - Game and Watch?

I'm not sure how or if I can help you with this as a theme contributor.  I've tried to make sure that the RetroActive and NeoActive themes every icon that is included in the baseline Monochrome theme.  That's why there's a duplicate set of icons named "Nintendo - Game and Watch" and "Game and Watch".

I think Nintendo - Game and Watch might be depreciated in favor of Game & Watch (apparently made by Nintendo) so we may have duplicate contents for same thing.
You don't have to do anything if you don't want to as I'm only sharing my findings... and I only see 12 games for Nintendo - Sufami Turbo (All Japan) in the database so most people might not notice this obscure game system... just like Pokemon Mini.

@lollo78 Up for it? baxysquare would use your Sufami icon to complete other themes.

It's sort of odd that most of the time the syntax is "Manufacturer - System" but there are exceptions such as "Game and Watch" as well as "Neo Geo," which I apparently ended up making a duplicate of as "SNK - Neo Geo."  Is there any way we can officially standardize it for consistency or am I making a mountain out of a mole hill?

I cleaned up cheat dirs to stay consistent. Thumbnails have been standardized. I filed bug issues reporting that the Content Downloader isn't consistent right now. I don't think you're making a mountain of a mole hill.
I believe this is the database that RetroArch (and many other groups) have been using to standardize things. You can see it in ${CORE}.info.
"Atari - 2600"
"Atari - 5200"
"Atari - 7800"
"Atari - Jaguar"
"Atari - Lynx"
"Bandai - WonderSwan Color"
"Bandai - WonderSwan"
"Cave Story"
"DOOM"
"FB Alpha - Arcade Games"
"GCE - Vectrex"
"Game and Watch"
"Lutro"
"MAME"
"MAME2003"
"Magnavox - Odyssey2"
"Microsoft - MSX"
"Microsoft - MSX2"
"NEC - PC Engine - TurboGrafx 16"
"NEC - PC Engine CD - TurboGrafx-CD"
"NEC - PC Engine SuperGrafx"
"NEC - PC-FX"
"Nintendo - Famicom Disk System"
"Nintendo - Game Boy Advance (e-Cards)"
"Nintendo - Game Boy Advance"
"Nintendo - Game Boy Color"
"Nintendo - Game Boy"
"Nintendo - GameCube"
"Nintendo - Nintendo 64"
"Nintendo - Nintendo 64DD"
"Nintendo - Nintendo DS (Download Play) (BETA)"
"Nintendo - Nintendo DS Decrypted"
"Nintendo - Nintendo Entertainment System"
"Nintendo - Pokemon Mini"
"Nintendo - Sufami Turbo"
"Nintendo - Super Nintendo Entertainment System"
"Nintendo - Virtual Boy"
"Nintendo - Wii"
"Quake1"
"RPG Maker 2000"
"RPG Maker 2003"
"SNK - Neo Geo Pocket Color"
"SNK - Neo Geo Pocket"
"ScummVM"
"Sega - 32X"
"Sega - Dreamcast"
"Sega - Game Gear"
"Sega - Master System - Mark III"
"Sega - Mega Drive - Genesis"
"Sega - Mega-CD - Sega CD"
"Sega - NAOMI"
"Sega - PICO"
"Sega - SG-1000"
"Sega - Saturn"
"Sinclair - ZX 81"
"Sinclair - ZX Spectrum +3"
"Sinclair - ZX Spectrum"
"Sony - PlayStation Portable"
"Sony - PlayStation"
"The 3DO Company - 3DO"
"Uzebox"


[VS Code] Remove ball on participant cursors when name tag is showing

When displaying the nametag for participants, the ball for their cursor is still showing. Instead, the ball show only appear when it is just the cursor, and disappear when the nametag is displayed.
Current:

Proposed:

Closing this due to inactivity and a lack of any recent customer feedback. Please re-open if you still think this is something we should address. Thanks!

You can just turn this off in the settings json of vscode
https://learn.microsoft.com/en-us/visualstudio/liveshare/use/coedit-follow-focus-visual-studio-code#change-participant-flag-behavior

@AlexNeep You Legend thanks so much!

The name tags should be off by default in my opinion instead of activity

You can just turn this off in the settings json of vscode
https://learn.microsoft.com/en-us/visualstudio/liveshare/use/coedit-follow-focus-visual-studio-code#change-participant-flag-behavior


Recent clan chats

Closes https://github.com/runelite/runelite/issues/4833

A delete button after each recent chat would be a nice to have. If you make a typo and join the wrong CC, you wouldn't want it to appear on this list I think. Maybe outside of the scope of this PR and maybe unnecessary.

Probably not, because this is keeping history of recently joined clan chats and is not your favorited/liked clan chats or something like that

Needs rebase


Converted print statements to errors/warnings; updated tests

Description

This PR removes the use of print statements across the GTFS module where errors can be used in their place.
Fixes #76
Motivation and Context
The motivation of this PR is to improve consistency across the package and to also ensure that any invalid user inputs are being handled correctly.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactor

How Has This Been Tested?

Notes:

Pytest passed locally and on the runners.
Coverage html report showing no loss of coverage across the gtfs module.
Pre-commit passing locally, during commit and also through github actions.

Test configuration details:

OS: Windows 10
Python version: 3.9.13
Java version: N/A
Python management system: Conda

Advice for reviewer

I have decided not to remove the print statement in clean_feed() as it can be addressed in #74 . I am also a bit weary about making changes to this function before the additional function calls included in the fast travel validation PR are merged into dev.
Checklist:

[x] My code follows the intended structure of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Additional comments

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (87216ed) 87.27% compared to head (a53a340) 87.27%.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #137   +/-   ##
=======================================
  Coverage   87.27%   87.27%
=======================================
  Files          11       11
  Lines         896      896
=======================================
  Hits          782      782
  Misses        114      114

Flag
Coverage Δ

unittests
87.27% <100.00%> (ø)

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

Files Changed
Coverage Δ

src/transport_performance/gtfs/validation.py
96.61% <100.00%> (ø)

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


Add TranslatePoLoader

I read in an Ionic blog comment that you'd include loaders in the docs, if anyone wrote some, so thought I'd share.
The loader is for Gettext po files: https://www.npmjs.com/package/ng2-translate-po-loader

Awesome thanks ! I'll add it !

Thanks!
I decided to publish under a name namespace instead, can you update the README?
The new package location is https://www.npmjs.com/package/@biesbjerg/ng2-translate-po-loader
Sorry for the trouble!

Okay, next time do a PR that's easier to merge :)


Fix float format

Plugin worked on assumption, that the only correct format code is 1 - which is format code for PCM. However, Membrane do support float-type raw audio formats (e.g. f32le) which have 3 format code.
Source: https://www.mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/WAVE.html

Closes https://github.com/membraneframework/membrane_core/issues/610


Support for dnxcore50

What does your roadmap looked like for adding the ability to target .NET Core?

Weeeell, roadmap at present doesn't include it - but that's very much a case of not having a fully fledged roadmap.
If you know what to do - or can point me in the right direction - I'll have a look and see what can be done, I'm assuming it's not working for you, if so - it'd be handy to know what isn't working so I can look more in depth.
I'll be frank though - having just run a Portability Report - it looks like it'd be a lot of work to get it in place, and some fairly significant changes - I'm not saying 'no' but just worth bearing it in mind.

I don't know what specifically needs to be done. I am attempting to analyze the feasibility of porting our solution and started with the third party libraries we reference to see if/when they would support it.

OK, well - I'll have a shufty and see how feasible it is!

Thank you Chris.

Keep in mind the ASP.NET 5 project is still making regular breaking changes on each beta.
RTM is due Q1 2016.
My Neo4j project is using ASP.NET 5 since Beta4 but targeting dnx451 only precisely due to lack of support in the nuget ecosystem. I suspect it will take some time for everyone to catch up.

@neutmute I am well aware. The reason I am looking into this is we are trying to utilize docker containers, it only runs on Windows Server 2016 and the support is very flimsy at best. To get around this we were hoping to be able to target the core 50 framework so we could deploy to a linux server as the docker support there is much better.

I'm closing this issue in lieu of #135 targeting .net core...


(#553) Add information about how to replace private variables

Description Of Changes
Adds information about how to replace usages of chocolateyToolsLocation (and it's aliases) and usages of chocolateyPackageFolder (and it's alias).
Motivation and Context
See #553
Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[ ] Minor documentation fix (typos etc.).
[x] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Issue #

Change Checklist

[ ] Requires a change to menu structure (top or left hand side)/
[ ] Menu structure has been updated

Related Issue
Part of #553
Not fully linking as I'm not sure if this is all that was intended to be added to this page.

Thanks for getting this added @TheCakeIsNaOH . Just one comment.

@TheCakeIsNaOH thank you for getting this information added, appreciate it!


solosite files upload

All files uploaded as bulk pending revision of file paths from the local state.

Pull request to be made before final commit of newly uploaded files to main branch.


Takedown: Projects aren't being deleted anymore

I could be wrong. I think I'm not seeing this on our own servers, but maybe I'm mistaken about which account the tests are running on. It might happen on failing tests. I'm not sure everyone can see these because they're not ours, but here's a failing test where deleting the project never runs:
https://github.com/LemmaLegalConsulting/docassemble-DangerLaw/actions/runs/7198403880/job/19607761373#step:3:1892
Here's a passing test where the Project does get deleted:
https://github.com/LemmaLegalConsulting/docassemble-MOHUDEvictionProject/actions/runs/7199780832/job/19612245162#step:3:462
Maybe something's wrong with our action.yml's if check for that Step. Gotta love GitHub actions.

I'm seeing this when the tests fail. If I go into the Testing User's Playground, I'll see a collection of the projects where the test failed.

Closed by #843


Watcher is not watching my folder

Strangely the watcher is not picking up changes, based on the following configuration:
{
      "FastMode": false,
      "Environment": "Html",
      "Name": "Html",
      "Url": "https://sharepoint2013.local/sites/testsite",
      "Files": [
        {
          "Source": "Display Templates",
          "Destination": "_catalogs/masterpage/Display Templates/Content Web Parts",
          "Exclude": "\\.js,\\.css,elements.xml,\\.spdata,\\.tmp",
          "Include": "\\.html"
        }
      ]

},

Which version? Please try it again with 1.2.4. I fixed some errors with paths.


WIP: Admin Status RPC

The Admin server Status RPC returns the count of states for all VASP
registrations and Certificate Requests. This PR also implements
ListVASPs on the Store object in order to support the Status endpoint
and refactors the Store List* methods to use an iterator rather than
materialize the entire list in memory. Finally, any gdsutil that had
been manually listing VASPs has been refactored to use the new List
iterator context.

Codecov Report

Merging #76 (6a45196) into main (13272f6) will decrease coverage by 0.26%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
- Coverage   23.67%   23.41%   -0.27%
==========================================
  Files          25       25
  Lines        3079     3114      +35
==========================================
  Hits          729      729
- Misses       2220     2255      +35
  Partials      130      130

Impacted Files
Coverage Δ

pkg/gds/admin.go
0.00% <0.00%> (ø)

pkg/gds/store/leveldb/leveldb.go
42.43% <0.00%> (-1.04%)
:arrow_down:

pkg/gds/store/store.go
25.80% <ø> (ø)

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 13272f6...6a45196. Read the comment docs.


emscripten: add platforms

@nbp
add platforms so it gets built by hydra.
should I also add this to emscripten-fastcomp?

I've been using the Darwin package and it works find. Could you change it to stdenv.lib.platforms.all?

@matthewbauer
sure. should I also add it to emscripten-fastcomp?

Definitely- I don't think it will hurt.

@matthewbauer , @nbp
OK, added all platforms to both now.

Sorry for the lack of reply before, this sounds fine to me as well.


Set nzmax for qdldl L matrix

The L matrix nzmax was not being set, so code generation resulted in a garbage value. This value is not used anywhere in the code though, so it doesn't seem to have had an observable effect on the solver.
Fixes oxfordcontrol/osqp-matlab#20

Coverage decreased (-0.4%) to 90.816% when pulling e2dd53aad7b99f969b92dbf35aea3383f5201bbf on im/nzmax into e7a51f0e9b05d6d172c411cdd7613d3608dc1212 on develop-0.6.


bug: bottom of interface cut off (again) for some

          Quickgui 1.2.10. I'm still having this problem.

Pop_os 22.04. Not using wayland

Window can not be resized or maximized
Originally posted by @glantucan in https://github.com/quickemu-project/quickgui/issues/100#issuecomment-2325564841

Also happening to me on PopOS

Just installed it on a new computer fresh PopOS 22.04 install. Same thing. Not a big deal form cause I can still use quickemu, but understand this a gui for more or less unexperienced linux users and PopOS seems to be very popular this days as an entry level distro

Also a problem on Kubuntu, can't create VMs now.

I've just found this issue myself, I'm looking in to it.

Ok, this is a bit strange.
We have some lines to set the max, min and default window size. When I increase these so that the window is the right size, the actual window size in pixels doesn't seem to bear any apparent relation to the size I set:

It could be that I'm making incorrect assumptions about how Size() works. @ymauray Do you have any thoughts about this?

@marxjohnson The comments in main.dart, on line 76, says the size also needs to be changed in my_application.cc.
Could that be what the cause of all your troubles ?
main.dart, line 76 :
  // Don't forget to also change the size in linux/my_application.cc:50
  if (Platform.isMacOS) {
    setWindowMinSize(const Size(692 + 2, 580 + 30));
    setWindowMaxSize(const Size(692 + 2, 580 + 30));
  } else {
    setWindowMinSize(const Size(692, 580));
    setWindowMaxSize(const Size(692, 580));
  }

The reason for all those shenanigans is that, depending on the platform, setWinM??Size will or won't take the window decoration into account. Heck, I think on some linux DE, it may or may not do the same thing. May there should be some kind of if (myDe.behaves()) { ... } else { ... } code here, for linux.
linux/my_application.cc, lines 50 and 51 :
  gtk_window_set_default_size(window, 692, 580);
  gtk_widget_show(GTK_WIDGET(window));

I've been changing the gtk_window_set_default_size() call to match the setWindowMinSize() call. Same result, the actual minimum window size is much smaller in pixels that the numbers passed to setWindowMinSize(), even with decorations.
FWIW, I am current running stock Ubuntu 22.04.


added next.js 14 support

closes #575.
On November 7th I messaged him directly on Discord to become a maintainer for the project or for him to approve of the PR.
I don't think he even read the message.
Maybe we should fork and publish it to NPM?

Can we installed this versions?

Please....

Unprofessional

Please merge it already

Is there any issue which needs to be fixed? what is holding up the merge. Happy to help if any.

Been using Next.js 14 with Contentlayer for a while, no problem found. Surely this should be merged since package managers like NPM will throw an unmet peer dependencies error due to the incompatible peer dependency version.

@schickling

If you need to use contentlayer just create next project using npx create-next-app@13 project-name --use-pnpm or without use-pnpm if you want npm. Or switch to 13.5.6 nextjs in package.json and reinstall packages. But anyway this should be merge as soon as possible.

Is contentlayer still actively maintained? I've been excited to add this to my Next.js project the last several weeks, but it seems like the last changes were several months ago in September. Wondering if I need to look into alternate CMS solutions? Happy to help in any way to get this PR merged.

commenting to subscribe for updates

Also commenting to subscribe for updates.

On November 7th I messaged him directly on Discord to become a maintainer for the project or for him to approve of the PR.

up 🙏

Apparently funding has stopped for the project and Netlify owns it.
The current work around is to add this snippet of code to your root package.json.  I am using turbo repo so it has to be the root package.json and if you aren't using a monorepo then you simply need to add it to your single package.sjon file.
    "next-contentlayer": {
      "next": "^14.0.0"
    }
  }```

@leerob cant you guys take over :((

I understood netlify took over the company @schickling is/was working for. They haven't allocated budget yet to continue the maintenance of contentlayer and therefore it is kind of dead.

Hi folks,
Please excuse the late message here and the lack of updates. As others have stated above, the past work on Contentlayer was sponsored by Stackbit which has since been acquired by Netlify who hasn't yet been resuming the sponsorship of the project (still TBD but it's taking a while).
Why isn't this PR merged yet?
Merging this PR alone most likely won't be enough. There needs to be a new release (with a non-trivial release process) incl. updating transitive dependencies which often cause other parts of Contentlayer to break.
In case there is any other company who'd be willing to sponsor the work on Contentlayer, I'd be up for a chat. I'd be happy to continue the work on Contentlayer as I'm excited about it and had many plans for it - and it's sad for me personally to see it neglected like this. (As much as I'd like, I can't currently commit to working on Contentlayer in my spare time.)

hello anyone can merge???

hello anyone can merge???

Please read the comment above, it won't be merged until someone sponsors this project.

closes #575.
On November 7th I messaged him directly on Discord to become a maintainer for the project or for him to approve of the PR.
I don't think he even read the message.
Maybe we should fork and publish it to NPM?

Fork it! Cant believe this project is standing still like this. I dont have the skills yet to take on a fork of this, but would support anyone who wanted to/could do it!


Fix Linux default route configuration.

Coverage remained the same at 63.075% when pulling 07e36208db2d92d983ed595bfe6d401a5f5aa34f on milanlenco:dev into 5af19cb927e74081cc11bb513ff5c7ebb80ec601 on contiv:dev.


the riscv32imc-esp-espidf target may not be installed

I am new in this field,
My PC is Mac m2
rust env info is ....
rustup -V
rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.78.0-nightly (bb594538f 2024-02-20)`

idf.py --version
ESP-IDF v5.2-37-g93ea06fe3e-dirty

rustup toolchain list
nightly-aarch64-apple-darwin (default)
esp

cargo -V
cargo 1.75.0

rustup component list (ignore not install)
cargo-aarch64-apple-darwin (installed)
rust-src (installed)
rust-std-aarch64-apple-darwin (installed)
rust-std-riscv32imac-unknown-none-elf (installed)
rust-std-riscv32imafc-unknown-none-elf (installed)
rust-std-riscv32imc-unknown-none-elf (installed)
rustc-aarch64-apple-darwin (installed)

rustup target list  (ignore not install)
aarch64-apple-darwin (installed)
riscv32imac-unknown-none-elf (installed)
riscv32imafc-unknown-none-elf (installed)
riscv32imc-unknown-none-elf (installed)

when I build this project
cargo build
I got the the err
Compiling peeking_take_while v0.1.2
   Compiling fastrand v2.0.1
   Compiling zero v0.1.3
   Compiling normpath v1.2.0
   Compiling pin-project-lite v0.2.13
   Compiling lazycell v1.3.0
error[E0463]: can't find crate for `core`
  |
  = note: the `riscv32imc-esp-espidf` target may not be installed
  = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0463]: can't find crate for `compiler_builtins`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1622:9
     |
1622 |     use core::mem::ManuallyDrop;
     |         ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1624:13
     |
1624 |     pub use core::{
     |             ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1633:32
     |
1633 |     pub struct AlwaysUnpin<T: ?Sized>(PhantomData<T>);
     |                                ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1635:14
     |
1635 |     impl<T: ?Sized> Unpin for AlwaysUnpin<T> {}
     |              ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1639:43
     |
1639 |     pub struct UnsafeDropInPlaceGuard<T: ?Sized>(*mut T);
     |                                           ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1641:14
     |
1641 |     impl<T: ?Sized> UnsafeDropInPlaceGuard<T> {
     |              ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1648:14
     |
1648 |     impl<T: ?Sized> Drop for UnsafeDropInPlaceGuard<T> {
     |              ^^^^^ not found in this scope

libunwind: malformed __unwind_info at 0x18A5AFCA8 bad second level page
libunwind: malformed __unwind_info at 0x18A5AFCA8 bad second level page
Some errors have detailed explanations: E0405, E0463.
For more information about an error, try `rustc --explain E0405`.
error: could not compile `pin-project-lite` (lib) due to 9 previous errors
warning: build failed, waiting for other jobs to finish...

when i install the esp32 target I got
rustup target add riscv32imc-esp-espidf
error: toolchain 'nightly-aarch64-apple-darwin' does not contain component 'rust-std' for target 'riscv32imc-esp-espidf'
note: not all platforms have the standard library pre-compiled: https://doc.rust-lang.org/nightly/rustc/platform-support.html
help: consider using `cargo build -Z build-std` instead

cargo build -Z build-std
error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel
See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.

how can I fix this problem, I search alot in google but I can not fix it
thanks

You need to use the esp Rust toolchain, by fiurst installing it with the espup utility, and then swithch it as the default with rustup default esp.
OR
you need to use the nightly Rust toolchain with rustup default nightly.
OR
you can - in the meantime - also use the stable toolchain, but you need to do a few tricks, so let's leave that for later.
Please follow this.

the same
rustup show
Default host: aarch64-apple-darwin
rustup home:  /Users/freewolf/.rustup

installed toolchains
--------------------

stable-aarch64-apple-darwin
nightly-aarch64-apple-darwin
esp (default)

active toolchain
----------------

esp (default)
(rustc does not exist)

cargo clean
     Removed 2187 files, 746.1MiB total
cargo build
   Compiling proc-macro2 v1.0.78
   Compiling unicode-ident v1.0.12
   Compiling libc v0.2.153
   Compiling serde v1.0.197
   Compiling memchr v2.7.1
   Compiling cfg-if v1.0.0
   Compiling crossbeam-utils v0.8.19
   Compiling regex-syntax v0.8.2
   Compiling cc v1.0.86
   Compiling syn v1.0.109
   Compiling glob v0.3.1
   Compiling aho-corasick v1.1.2
   Compiling bitflags v1.3.2
   Compiling rustix v0.38.31
   Compiling autocfg v1.1.0
   Compiling clang-sys v1.7.0
   Compiling quote v1.0.35
   Compiling syn v2.0.50
   Compiling rustversion v1.0.14
   Compiling regex-automata v0.4.5
   Compiling log v0.4.20
   Compiling bitflags v2.4.2
   Compiling semver v1.0.22
   Compiling errno v0.3.8
   Compiling crossbeam-epoch v0.9.18
   Compiling bstr v1.9.0
   Compiling serde_json v1.0.114
   Compiling minimal-lexical v0.2.1
   Compiling same-file v1.0.6
   Compiling thiserror v1.0.57
   Compiling nom v7.1.3
   Compiling walkdir v2.4.0
   Compiling crossbeam-deque v0.8.5
   Compiling nix v0.26.4
   Compiling libloading v0.8.1
   Compiling globset v0.4.14
   Compiling cvt v0.1.2
   Compiling home v0.5.9
   Compiling lazy_static v1.4.0
   Compiling itoa v1.0.10
   Compiling bindgen v0.63.0
   Compiling ryu v1.0.17
   Compiling anyhow v1.0.80
   Compiling either v1.10.0
   Compiling heck v0.4.1
   Compiling which v4.4.2
   Compiling cexpr v0.6.0
   Compiling fs_at v0.1.10
   Compiling ignore v0.4.22
   Compiling regex v1.10.3
   Compiling shlex v1.3.0
   Compiling rustc-hash v1.1.0
   Compiling zero v0.1.3
   Compiling fastrand v2.0.1
   Compiling peeking_take_while v0.1.2
   Compiling pin-project-lite v0.2.13
error[E0463]: can't find crate for `core`
  |
  = note: the `riscv32imc-esp-espidf` target may not be installed
  = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0463]: can't find crate for `compiler_builtins`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1622:9
     |
1622 |     use core::mem::ManuallyDrop;
     |         ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1624:13
     |
1624 |     pub use core::{
     |             ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1633:32
     |
1633 |     pub struct AlwaysUnpin<T: ?Sized>(PhantomData<T>);
     |                                ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1635:14
     |
1635 |     impl<T: ?Sized> Unpin for AlwaysUnpin<T> {}
     |              ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1639:43
     |
1639 |     pub struct UnsafeDropInPlaceGuard<T: ?Sized>(*mut T);
     |                                           ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1641:14
     |
1641 |     impl<T: ?Sized> UnsafeDropInPlaceGuard<T> {
     |              ^^^^^ not found in this scope

error[E0405]: cannot find trait `Sized` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pin-project-lite-0.2.13/src/lib.rs:1648:14
     |
1648 |     impl<T: ?Sized> Drop for UnsafeDropInPlaceGuard<T> {
     |              ^^^^^ not found in this scope

   Compiling byteorder v1.5.0
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
Some errors have detailed explanations: E0405, E0463.
For more information about an error, try `rustc --explain E0405`.
error: could not compile `pin-project-lite` (lib) due to 9 previous errors
warning: build failed, waiting for other jobs to finish...
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
error[E0463]: can't find crate for `core`
  --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:76:5
   |
76 | use core::{
   |     ^^^^ can't find crate
   |
   = note: the `riscv32imc-esp-espidf` target may not be installed
   = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1209:27
     |
1209 |             const _: () = assert!(align_of::<u32>() <= align_of::<f32>());
     |                           ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1271:27
     |
1271 |             const _: () = assert!(align_of::<u64>() <= align_of::<f64>());
     |                           ^^^^^^

error: cannot find attribute `derive` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1812:3
     |
1812 | #[derive(Clone, Copy, Debug, Eq, Hash, Ord, PartialEq, PartialOrd)]
     |   ^^^^^^

error: cannot find macro `panic` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1817:9
     |
1817 |         panic!("BigEndian default")
     |         ^^^^^

error: cannot find attribute `derive` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1842:3
     |
1842 | #[derive(Clone, Copy, Debug, Eq, Hash, Ord, PartialEq, PartialOrd)]
     |   ^^^^^^

error: cannot find macro `panic` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1847:9
     |
1847 |         panic!("LittleEndian default")
     |         ^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1962:9
     |
1962 |         assert!(1 <= nbytes && nbytes <= out.len() && nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1971:9
     |
1971 |         assert!(1 <= nbytes && nbytes <= out.len() && nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1999:9
     |
1999 |         assert!(pack_size(n) <= nbytes && nbytes <= 8);
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2000:9
     |
2000 |         assert!(nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2013:9
     |
2013 |         assert!(pack_size128(n) <= nbytes && nbytes <= 16);
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2014:9
     |
2014 |         assert!(nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2027 |         read_slice!(src, dst, u16, from_be_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2032 |         read_slice!(src, dst, u32, from_be_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2037 |         read_slice!(src, dst, u64, from_be_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2042 |         read_slice!(src, dst, u128, from_be_bytes);
     |         ------------------------------------------ in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2047 |         write_slice!(src, dst, u16, to_be_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2052 |         write_slice!(src, dst, u32, to_be_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2057 |         write_slice!(src, dst, u64, to_be_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2062 |         write_slice!(src, dst, u128, to_be_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2067:12
     |
2067 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2076:12
     |
2076 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2085:12
     |
2085 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2094:12
     |
2094 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2103:12
     |
2103 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2115:12
     |
2115 |         if cfg!(target_endian = "little") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2150:9
     |
2150 |         assert!(1 <= nbytes && nbytes <= out.len() && nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2158:9
     |
2158 |         assert!(1 <= nbytes && nbytes <= out.len() && nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2185:9
     |
2185 |         assert!(pack_size(n as u64) <= nbytes && nbytes <= 8);
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2186:9
     |
2186 |         assert!(nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2195:9
     |
2195 |         assert!(pack_size128(n as u128) <= nbytes && nbytes <= 16);
     |         ^^^^^^

error: cannot find macro `assert` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2196:9
     |
2196 |         assert!(nbytes <= buf.len());
     |         ^^^^^^

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2205 |         read_slice!(src, dst, u16, from_le_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2210 |         read_slice!(src, dst, u32, from_le_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2215 |         read_slice!(src, dst, u64, from_le_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1914:9
     |
1914 |         assert_eq!(src.len(), dst.len() * SIZE);
     |         ^^^^^^^^^
...
2220 |         read_slice!(src, dst, u128, from_le_bytes);
     |         ------------------------------------------ in this macro invocation
     |
     = note: this error originates in the macro `read_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2225 |         write_slice!(src, dst, u16, to_le_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2230 |         write_slice!(src, dst, u32, to_le_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2235 |         write_slice!(src, dst, u64, to_le_bytes);
     |         ---------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `assert_eq` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1931:9
     |
1931 |         assert_eq!(src.len() * SIZE, dst.len());
     |         ^^^^^^^^^
...
2240 |         write_slice!(src, dst, u128, to_le_bytes);
     |         ----------------------------------------- in this macro invocation
     |
     = note: this error originates in the macro `write_slice` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2245:12
     |
2245 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2254:12
     |
2254 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2263:12
     |
2263 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2272:12
     |
2272 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2281:12
     |
2281 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error: cannot find macro `cfg` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:2293:12
     |
2293 |         if cfg!(target_endian = "big") {
     |            ^^^
     |
     = note: `cfg` is in scope, but it is an attribute: `#[cfg]`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1910:29
     |
1910 |         const SIZE: usize = core::mem::size_of::<$ty>();
     |                             ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0463]: can't find crate for `core`
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1927:29
     |
1927 |         const SIZE: usize = core::mem::size_of::<$ty>();
     |                             ^^^^ can't find crate
     |
     = note: the `riscv32imc-esp-espidf` target may not be installed
     = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

error[E0405]: cannot find trait `Clone` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:213:5
    |
213 |     Clone
    |     ^^^^^ not found in this scope

error[E0405]: cannot find trait `Copy` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:214:7
    |
214 |     + Copy
    |       ^^^^ not found in this scope

error[E0405]: cannot find trait `Default` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:216:7
    |
216 |     + Default
    |       ^^^^^^^ not found in this scope

error[E0405]: cannot find trait `Eq` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:217:7
    |
217 |     + Eq
    |       ^^ not found in this scope

error[E0405]: cannot find trait `Ord` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:219:7
    |
219 |     + Ord
    |       ^^^ not found in this scope

error[E0405]: cannot find trait `PartialEq` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:220:7
    |
220 |     + PartialEq
    |       ^^^^^^^^^ not found in this scope

error[E0405]: cannot find trait `PartialOrd` in this scope
   --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:221:7
    |
221 |     + PartialOrd
    |       ^^^^^^^^^^ not found in this scope

error[E0405]: cannot find trait `Default` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1815:6
     |
1815 | impl Default for BigEndian {
     |      ^^^^^^^ not found in this scope

error[E0405]: cannot find trait `Default` in this scope
    --> /Users/freewolf/.cargo/registry/src/index.crates.io-6f17d22bba15001f/byteorder-1.5.0/src/lib.rs:1845:6
     |
1845 | impl Default for LittleEndian {
     |      ^^^^^^^ not found in this scope

libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
libunwind: malformed __unwind_info at 0x188E83CA8 bad second level page
error: could not compile `byteorder` (lib) due to 60 previous errors

I already switch esp


Model Content-Transfer-Encoding header

fixes #6793
I had a shot at modeling the header.
As this is a first for me feedback is very welcome. Especially I was not sure whether to model it using CIString or not (RFC states it is case insensitive).

X org.http4s.ember.server.EmberServerSuite.#7216 - client can replace a terminated connection with max total of 1 38.86s java.util.concurrent.TimeoutException: test timed out after 31 seconds
I think this failing test has nothing to do with my changes.


[backport] Replace deprecated URLopener in download.py

Backport of #6694

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit eb4be83a4144d6459fc12ad9c810f48d1c34d21e, target branch v5) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins error (requests.exceptions.HTTPError: 504 Server Error: GATEWAY_TIMEOUT for url: https://coveralls.io/api/v1/jobs) is unrelated to the PR.

Closing as v5 branch has been freezed.


way to fix "magic_number = pickle_module.load(f, **pickle_load_args)  EOFError: Ran out of input"

If you encounter an error similar to the one below, please note your checkpoints file and pfggan files, they could both have only file names but 0 file sizes.

I used this script and had this problem：
’‘’bash scripts/download_models.sh‘’‘
which was solved by using another way to download the file and upload them to the right place

sry, my bad


Refactored modals to using TS and simplified code for modals.

Also added a story for modals to storybook.

Since master is now base branch for this PR, I'm gonna close this and open a new PR


A child Text fattens and fattens - V4

This Text is a child of the character, they both have anchor.set(0.5,1)'s - the Text has .y=-30
When you play around a bit, the text gets bolder, I'm not sure what's causing it, I checked whether it somehow gets re-added, yet that's not the case, as the console.log is only hit once
I also have no plugins on top of PIXI when this happens
Any ideas for the cause?

Yep, thats a bug, can you please try new version?

By the way, where did you get the sprites?

Thanks for the info
I seem to be using the latest one from the bin tho, does the bin's auto-update? last update is 11 days ago
( the sprites are time fantasy sprites : )

I updated it 18 minutes ago but i did not push into gh-pages yet

This is where I get my V4 from: https://github.com/pixijs/pixi.js/tree/dev/bin - Should I check another place?
By the way, I have another very weird bug, wondering whether these 2 issues are related and whether the updated V4 is going to fix it, the main character somehow gets linked to the monsters on the map, each click to the main character goes to random monsters, the main character plays their animations, very bizarre stuff - in it's most basic explanation, the issue causes clicks to one sprite to be diverted to other sprites etc.
Don't know why but today is my pixi bugs day, before today everything was like clockwork :)

I thought you are talking about "bin" which contains my plugins. Its there: https://github.com/gameofbombs/pixi-bin/tree/master/bin
Just dont take pixi.js from there, its experimental :)
I have built V4 for you: https://dl.dropboxusercontent.com/u/46636530/pixijs/pixi.js . Official build will happen next week.

Thank you so much <3
It turns out the fattened font in my case is the side-effect of the glitch I mentioned above, at one point, something flips off in the game, it's like everything is linked to each other, the main character shakes when it absorbs animations meant for other entities, the Text fattens with this shaking
Investigating at this point, I hope it's an easily solveable innocent bug from my side

Well apologies
Turns out it was a bug from my side, a bug + bad variable naming
I had a new routine that I use for adopting properties into a sprite from an object, while copy pasting I didn't rename the arguments, it ended up overriding all monster sprite properties with the properties of the main character sprite, causing the headache inducing issue I described


getsockopt failed strangely: Operation not permitted

Heyo,
the above message gets dropped when trying to run your docker image on kubernetes, any ideas why? I guess it's an issue with the container port being not allowed?
Thanks for your help!

Need to add --cap-add=NET_ADMIN

Need to add --cap-add=NET_ADMIN
@pvlg

The cap_add and cap_drop options are ignored when deploying a stack in swarm mode (doc)

What if i can't use cap-add?

What if i can't use cap-add?

I'm in the same situation, But now that I think about it, maybe I always want the same computer to be my vpn server, so outside the swarm. But then do you need a different machine/VM ? Not sure if we can lunch a docker on the same machine that is part of a swarm..


Development Infra

This is actually hard to run as some of the versions are not specified and some of the configuration files seems to be out-of-date. I now have the thing running with docker containers which should allow for a more streamlined process (and a more reproducible one).
I did review the Ansible setup - but it seems to be out of date? it would be great to have the actual production settings file.
I am currently unable to figure-out how to hydrate the database. So possibly to make further inroads I'll need some help.

This looks fine and the requirements basically match what's in here:
https://github.com/CopticScriptorium/cts/blob/master/coptic/requirements_django_2.txt
But that also specifies celery==4.3.0 - any objections to adding that?

I believe this is possibly an unused requirement that should be removed?
Let's first have a call and make sure I understand to he state of the thing in production and I am capable of running a fully hydrated instance locally before we apply any changes that could break anything. Safety first.


Add Luke Crosby to list of security guidance collaborators.

Luke will be providing formal review and approval input for content going into the repository.

Related PR #155

Hi @AntonyBishop Oops, sorry!
Will do. Thank you.


Data splits for stability task

The TAPE manuscript describes creating the splits for the stability task as

We create training, validation, and test splits ourselves, partitioning the data so that training and validation sets come from four rounds of experimental data measuring stability for many candidate proteins, while our test set consists of seventeen 1-Hamming distance neighborhoods around promising proteins observed in the four rounds of experimentation.

In stability_train.json from the raw data there are a few villin HP35 sequences such as "id": "villin_K48M". I expected all the villin sequences to be in the test split because this was one of the saturation mutagenesis experiments, not one of the four design rounds.
Were some of the saturation mutagenesis data included in the training or validation splits?

I went back to the Rocklin 2017 supplementary files and see that these villin sequences are from the file rd4_stability_scores. That answers my question about the data splitting.