SvelteKit ran with Netlify CLI fails to start

Describe the bug
When running ntl dev in a SvelteKit project, the server fails to start because it is looking for port 3000. SvelteKit updated to run vite dev and is now running on port 5173 by default. This can be fixed by adding a targetPort to the netlify.toml file, but should run port 5173 by default.
Steps to reproduce

Run git clone git@github.com:brittneypostma/sveltekit-cli-bug.git
Navigate to repo
Run ntl dev
Enter on either SvelteKit or Vite command to run npm run dev
See error vite: not found Waiting for framework port 3000. This can be configured using the 'targetPort' property in the netlify.toml◈ Command failed with exit code 127: npm run dev. Shutting down Netlify Dev server

Fix
Port is now 5173, not 3000
Temporary fix

Add targetPort to netlify.toml file

[dev]
  targetPort = 5173

Rerun ntl dev
Server starts

Configuration
n/a
Environment
  System:
    OS: Linux 5.10 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (16) x64 Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
    Memory: 13.97 GB / 15.57 GB
    Container: Yes
    Shell: 5.0.16 - /bin/bash
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  npmGlobalPackages:
    netlify-cli: 11.8.2

This should work as of version 12.0.7

Oh my god! You saved me. thanks a lot!

Nov 24 2022. Using Node 16.14.0,  vite 3.3.2, Svelte 3.52.0. netlify.toml file has [dev] targetPort = 5173

netlify dev with Svelte 'npm run dev' gives indefinite "Waiting for framework port 5173".
netlify dev --targetPort 5173 with Svelte 'npm run dev' gives indefinite "Waiting for framework port 5173".
Netlify dev with Vite 'npm run dev'  or "npm run build" works ie gives message "Server now ready on http://localhost:8088"

ok I have this working now.  I decided to upgrade to Node v18.12.1 as I was getting messages about "module" which was updated since v17 and I was running v16.14.0.
However to get netlify to not hang waiting for port 5173, I had to have my netlify.toml file like this:
[build]
publish="dist"
[dev]
command = "npm run dev"
targetPort=5173
port=8888
[functions]
node_bundler = "esbuild"
With those changes (possibly just the toml file) netlify dev runs and opens my svelte/vite app no problem.


[Bug] Subscribing to # hangs the app

What did I do
Created a subscription for #
What happened
The application slowed down, everything started to stutter. UI became completely unresponsive, the disconnect button wouldn't work. Had to forcefully kill the app, which resulted in a corrupted db.json causing the app to refuse to start up.
Expected
The application remains functional and responsive
Environment

OS: Linux (5.11.6)
MQTTX version: v1.5.2

@daenney Thanks for your support, could you tell us your MQTT broker environment and log after your operation?

My broker is emqx 4.2.7.
I don’t know what you mean with “ environment and log after your operation?”. Do you want to see any logs emqx generated after I used mqttx to subscribe?

My broker is emqx 4.2.7.
I don’t know what you mean with “ environment and log after your operation?”. Do you want to see any logs emqx generated after I used mqttx to subscribe?

Yes, more details plz. I can't reproduce.
emqx reject # topic by default, could you please check the emqx acl.conf configure file?

It may be an issue similar to this one. #457
@oceanlvr Is caused by the amount of received messages.

Ok, maybe we should fix the read/write problem in a better way.

On the ACL thing, I explicitly have {allow, all, subscribe, ["$SYS/#", {eq, "#"}]}. on this cluster since this is my testing rig. But yes, the problem isn't so much the subscription as the amount of messages flowing through it. It seems to cause the UI to be permanently catching up/processing a backlog of events.
#457 sounds similar, though in my particular case it's MQTT 3.1.1 and all messages are strings.

Not sure the issue is fixed. At least, I'm running v1.8.3 and for some reason, got the history filled with more than 44000 entries. Now the MQTTX.db weight 14MB (only), and the app is absolutely unusable. It's so unresponsive that it will disconnect before I can clear the history. BTW, clearing while disconnected won't work.
My only workaround is to delete MQTTX.db and start from scratch, not cool :(

@Tazintosh Hi, thanks for the feedback. YES, It's true that this has been an issue, and we haven't optimized it for a large number of messages, but we're actually keeping an eye on it, and it's actually affecting the MQTT X experience, so I'm going to reference your comments and create a new issue until it's fixed.

Hello, I am having this problem as well.  The history is filling up with messages and causes the app to become completely unresponsive. EXTREMELY frustrating since this is the very first time I'm using the app... it does not instill a lot of confidence in your product. This seems to be happening even when the app is shut down?  I had over 5000 messages in the history when I tried to open the app this morning.
I don't understand this behavior since I have all of the QOS settings on the publisher to 0... which means that there should be no messages being retained, right?  So why does it retain these messages in the history?  It should print the latest message, and then discard it when the next message is received, right?
Is there some way we can limit the max number of messages retained in the history buffer to prevent it from eating up all the memory in my system? Maybe limit it to the past 50-100 messages or so?  Is there a way to set it so there is no history?  I am only interested in the latest message, I have no need to retain any previous messages.

@LucidEye Hi again. Looks like a good suggestion for store messages. We consider this and improve this part for your need. I will reopen this issue unit this bug has been fixed now.

Apologies for the long wait, welcome to https://github.com/emqx/MQTTX/releases/tag/v1.9.1, that should solve the problem and I will close this issue.


Add a lint for cargo doc to ensure links don't break

Something that runs cargo doc and fails if any warnings show up.

Closed via #235, landing in #212.


Fix [QUIC] seg.fault & remove unused configuration item

Codecov Report
Patch coverage has no change and project coverage change: +0.10 :tada:

Comparison is base (afc6d7a) 51.08% compared to head (14dcd7a) 51.18%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #495      +/-   ##
==========================================
+ Coverage   51.08%   51.18%   +0.10%
==========================================
  Files         120      120
  Lines       36282    36283       +1
==========================================
+ Hits        18533    18571      +38
+ Misses      17749    17712      -37

Impacted Files
Coverage Δ

src/supplemental/nanolib/conf.c
0.00% <ø> (ø)

src/supplemental/nanolib/conf_ver2.c
0.00% <ø> (ø)

... and 22 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Upgrade & fix Android build scripts

As well as upgrading Android build tools to the latest, this fixes a bug that was breaking 64-bit builds because of ndk_platform not always matching env['ndk_platform'].

Thanks!

Consider for 3.1.2

@hpvb That was a 2.1 PR, not relevant for master/3.1.


Support CSP img-src unsafe-inline

Hi all,
I have been working on a small site.  I am just using the default Bootstrap 4.0.0 .css file, no re-bundling, but it is causes issues with the CSP image sources, which I have set to self.
The issue is that the bootstrap.css uses inline SVG images for some icons.   There are things I could do to get around this.  I could use webpack to split out the image, or I could use the hash hack to add a hash for the image.
Would you consider allowing unsafe-inline on image sources?
Thanks

ah, I've just found what I did wrong.  It is not inline, It is data scheme source.  Adding "data:" to my custom sources fixed it.


change resolution of segmentation output?

Hi,
I'm following the segmentation tutorial, and have the "fcn-resnet18-cityscapes-2048x1024" running on the Jetson Xavier NX.
The output mask resolution of the pre-trained model is set at 32x64px - is there a way to increase the output mask resolution, say to 64x128px or 128x256px?
Thanks in advance!

The size of the raw output mask scales depending on the input resolution - so you would need to train on larger images to get a larger output mask.   This would lead to longer runtimes, and I don't really recommend it because 2048x1024 is already large input.
If you are familiar with FCN-ResNet architecture, you could try editing the layers so it makes a larger mask, but this may have other impacts like reducing the accuracy.  I haven't tried changing the network architecture.
To apply the raw mask to the original images, I upsample the mask with bilinear filtering or point filtering.

Got it, makes sense. Thanks!

The size of the raw output mask scales depending on the input resolution - so you would need to train on larger images to get a larger output mask. This would lead to longer runtimes, and I don't really recommend it because 2048x1024 is already large input.
If you are familiar with FCN-ResNet architecture, you could try editing the layers so it makes a larger mask, but this may have other impacts like reducing the accuracy. I haven't tried changing the network architecture.
To apply the raw mask to the original images, I upsample the mask with bilinear filtering or point filtering.

Hello Dusty,I have the same question.And l also test to train my voc 2012 data using your training.py code ,and use 512320 resolution .  As you said,the putout layer will have the same resolution,but  I get the 1610 putout layer.  so I try to use 2048960  args to train voc 2012,the the model putout 6440 .   so I find a regular that putout resolution=input resolution/32    and we cannot change it,I want to know why,and How can I have a high resolution label layer (putout mask )as I labeled ?

Hi,
I'm following the segmentation tutorial, and have the "fcn-resnet18-cityscapes-2048x1024" running on the Jetson Xavier NX.
The output mask resolution of the pre-trained model is set at 32x64px - is there a way to increase the output mask resolution, say to 64x128px or 128x256px?
Thanks in advance!

I have the same question.Did you solve it seccessfully?  how do you train your pytorch model? thank you very much!

As you said,the putout layer will have the same resolution,but I get the 16 x 10 putout layer. so I try to use 2048 x 960 args to train voc 2012,the the model putout 64 x 40 . so I find a regular that putout resolution=input resolution/32 and we cannot change it,I want to know why,and How can I have a high resolution label layer (putout mask layer )as I labeled ? origin resolution out is best!

The raw classification grid is always going to be a factor of 32 smaller, because this is the network architecture.   If you are familiar with FCN-Resnet you may be able to doctor the network architecture, but I have not tried it.
Normally the output of FCN segmentation network is same size, because it uses deconvolution on the smaller classification grid.  However that operation is quite slow and makes it non-realtime, and the deconvolution is linear (i.e. learning rate of deconv layer is 0, meaning it doesn't 'learn' and is just linear operator).   So i remove deconv layer from the model and instead do it in post-processing in my CUDA kernel.
Even if you kept the deconv layers inside the model, it would still be working from that factor-of-32 classifiation grid though.  It doesn't really produce new information.

As you said,the putout layer will have the same resolution,but I get the 16 x 10 putout layer. so I try to use 2048 x 960 args to train voc 2012,the the model putout 64 x 40 . so I find a regular that putout resolution=input resolution/32 and we cannot change it,I want to know why,and How can I have a high resolution label layer (putout mask layer )as I labeled ? origin resolution out is best!

The raw classification grid is always going to be a factor of 32 smaller, because this is the network architecture. If you are familiar with FCN-Resnet you may be able to doctor the network architecture, but I have not tried it.
Normally the output of FCN segmentation network is same size, because it uses deconvolution on the smaller classification grid. However that operation is quite slow and makes it non-realtime, and the deconvolution is linear (i.e. learning rate of deconv layer is 0, meaning it doesn't 'learn' and is just linear operator). So i remove deconv layer from the model and instead do it in post-processing in my CUDA kernel.
Even if you kept the deconv layers inside the model, it would still be working from that factor-of-32 classifiation grid though. It doesn't really produce new information.

Thanks a lot for your reply,I don't know how  to change the network architecture, and it will cast my lot of time to study it. so I use your open source code like a object to solve my reality problem。My problem is to find a small object in 4k img  ,so I want to putout a higher resolution label layer to find it 😂.  So is an easy change in your training code or inference code that I can get a high resolution putout layer? for example 2k in and real 2k out……    🤣🤣🤣

If you are using jetson-inference segNet class to run the inference, it will re-scale the results using bilinear interpolation (similar to what deconv was doing, just faster) to whatever image size you provide as the output.  Typically this is the same size as the input image.

If you are using jetson-inference segNet class to run the inference, it will re-scale the results using bilinear interpolation (similar to what deconv was doing, just faster) to whatever image size you provide as the output. Typically this is the same size as the input image.

Thank you very much for your so quick reply. I think I konw want you mean, tomorrow I will try again.

If you are using jetson-inference segNet class to run the inference, it will re-scale the results using bilinear interpolation (similar to what deconv was doing, just faster) to whatever image size you provide as the output. Typically this is the same size as the input image.

Dear Dusty,today I try again the infernce . I found that what you said is right , it is almost the same accuracy with offical result. I used the parameter :
--filter-mode=point
to test before, so it seems that the resolution is very low, but I didn't find that the accuracy of the detection is quite high.
This is a comparison chart of various results:

So I only one question left ,is  that if you liner the result point , the color value is changed ? the color value is fitted?I want to get the detect result to do next work,so it's import for me .

@wakingking77 during --filter-mode=linear, bilinear filtering is used to blend the colors for visualization.  So that is not very useful for detecting the underlying class, because they have been blended.  That is why --filter-mode=point is more likely to be useful when you want to know the actual classes.
You can use the segNet.Mask() function to get an image of just the class ID's back (not color).  It will re-scale pointwise to whatever resolution the output image is.  Output image should be uint8 to get class ID's back.  This is how it is used in the code:

https://github.com/dusty-nv/jetson-inference/blob/6e078d21396298c3a9f1f1ea1f2c27bf80bbd4a6/python/examples/segnet_utils.py#L80
https://github.com/dusty-nv/jetson-inference/blob/6e078d21396298c3a9f1f1ea1f2c27bf80bbd4a6/python/examples/segnet_utils.py#L72

@wakingking77 during --filter-mode=linear, bilinear filtering is used to blend the colors for visualization. So that is not very useful for detecting the underlying class, because they have been blended. That is why --filter-mode=point is more likely to be useful when you want to know the actual classes.
You can use the segNet.Mask() function to get an image of just the class ID's back (not color). It will re-scale pointwise to whatever resolution the output image is. Output image should be uint8 to get class ID's back. This is how it is used in the code:

https://github.com/dusty-nv/jetson-inference/blob/6e078d21396298c3a9f1f1ea1f2c27bf80bbd4a6/python/examples/segnet_utils.py#L80
https://github.com/dusty-nv/jetson-inference/blob/6e078d21396298c3a9f1f1ea1f2c27bf80bbd4a6/python/examples/segnet_utils.py#L72

thank you very very much!!  I finally got it！！


python311Packages.sqlalchemy-mixins: <IP_ADDRESS> -> 2.0.5

Diff: https://github.com/absent1706/sqlalchemy-mixins/compare/refs/tags/v<IP_ADDRESS>...v2.0.5
Changelog: https://github.com/absent1706/sqlalchemy-mixins/releases/tag/v2.0.5
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.sqlalchemy-mixins
python310Packages.sqlalchemy-mixins.dist
python311Packages.sqlalchemy-mixins
python311Packages.sqlalchemy-mixins.dist


The Google Directions example breaches Google's Terms of Service

In https://github.com/ariya/phantomjs/blob/master/examples/direction.js#L30 there seems to be some regexp which removes the copyright statements. Please remove that.
Removing copyright info is against the Google Maps Terms of Service[0].
The aforementioned piece of code would lead developers into violating these Terms of Service, without even knowing it.
[0] Google Maps Terms of Service:
https://developers.google.com/maps/terms
§ 9.4 (a), (b) and (c)
§ 10.1.1. (f)

The entire example script will be removed.


Show the other navbar items on small screens too.

Do not merge until we have 3 approvals :)

The navbar was misaligned on desktop, so I removed the margin with .mt-md-0. Not sure if we even need the margin on mobile.

Yeah, that was a typo on my side. Not sure either, there's a padding-bottom in the top navbar already.

I just removed it, the padding does the trick.

@mdo: LGTY?

@mdo: friendly ping :)

@mdo: LGTY?


迁移获取时区差代码至util.cpp并添加接口供外部获取

迁移获取时区差代码至util.cpp并添加接口供外部获取

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: custompal:white_check_mark: xia-chu:x: monktan89You have signed the CLA already but the status is still pending? Let us recheck it.


Updates recipe to the latest release

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This PR just updates this package to the latest release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please pre-render

@conda-forge-admin please rerender

To be explicit: I am ok with being added as a maintainer on this feedstock.

@anjos Thank you to your hard work at making this work and thanks to @beckermr for helping! @bskinn  I can add you as maintainer

Oh oops looks like you have already been added @bskinn


emacs does not install

When I try to install emacs via
apt-get install emacs
I get the following error message
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libgudev-1.0-0_204-5ubuntu20.18_amd64.deb  404
Using a web browser to open that directory (and ignoring the security error under Edge (!!??)), I see that libgudev-1.0-dev_204-5ubuntu20.19_amd64.deb and libgudev-1.0-dev_204-5ubuntu20_amd64.deb are present, but no version 20.18.

It looks like this might be a generic network issue you are hitting similar to #5.  Are you able to do other network related tasks?

I'm guessing it's a different issue.  Of the 101 (!!) packages it wants to install, the other 100 are downloaded.  Plus, when I use a web browser to examine that directory ( http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/), I don't see that file listed.

Did you run apt-get update first?

No, but that fixes it!
After the update, apt-get now pulls that file from a different source:
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libgudev-1.0-0 amd64 1:204-5ubuntu20.19 [14.1 kB]
[Sorry for the newbie question, first distro I've used that uses apt-get instead of yum....]

No worries, us Windows folks are new to the Linux world as well :)


Add approveChatJoinRequest and declineChatJoinRequest methods

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

Project coverage is 100.00%. Comparing base (1ff1873) to head (80e1278).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##              master       #40   +/-   ##
===========================================
  Coverage     100.00%   100.00%
- Complexity      1043      1055   +12
===========================================
  Files            228       230    +2
  Lines           3887      3917   +30
===========================================
+ Hits            3887      3917   +30

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


Build fails when using algoliasearch

Please provide the environment you discovered this bug in.
https://github.com/rabraghib/analog-algoliasearch-bug
Which area/package is the issue in?
vite-plugin-angular
Description
When using the algoliasearch/lite package in an AnalogJS project, the build process (npm run build) fails. However, the project runs as expected in development mode (npm run dev).
Nothing is generated in the output folder when the build fails. It seems like the client build phase doesn't generate an output and the SSR build phase throws an error.
I've tried adding algoliasearch and algoliasearch/lite to the noExternal configuration in vite.config.js but did not fix the problem:
ssr: {
  noExternal: ['algoliasearch'], // 'algoliasearch/lite'
},

Please provide the exception or error you saw
vite v5.3.1 building for production...
✓ 362 modules transformed.
Building SSR application...
x Build failed in 14.46s
An unhandled exception occurred: [@analogjs/vite-plugin-nitro] ENOENT: no such file or directory, open 'D:\GitHub\Side-Projects\test\analog-app\dist\client\index.html'
See "C:\Users\RABRAG~1\AppData\Local\Temp\ng-EYOvDD\angular-errors.log" for further details.

Other information
No response
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

This can be resolved with the vite-plugin-node-polyfills package.
npm i vite-plugin-node-polyfills --save-dev

And update the vite config
/// <reference types="vitest" />

import { defineConfig } from 'vite';
import analog from '@analogjs/platform';
import { nodePolyfills } from 'vite-plugin-node-polyfills'

// https://vitejs.dev/config/
export default defineConfig(({ mode }) => ({
  build: {
    target: ['es2020'],
  },
  resolve: {
    mainFields: ['module'],
  },
  plugins: [
    analog(),
    nodePolyfills(),
  ],
  test: {
    globals: true,
    environment: 'jsdom',
    setupFiles: ['src/test-setup.ts'],
    include: ['**/*.spec.ts'],
    reporters: ['default'],
  },
  define: {
    'import.meta.vitest': mode !== 'production',
  },
}));

You might see a build error logged to the console at the end, but the server runs correctly.


Add some kind of load information on SQL Agent Job History tree view

On SQL Agent Job History tree view for long history jobs log the view take too long to load,,, add some kind of load status (bar, dots, circle, etc..)

@abist did we get the loading indicators work in for April, or is that targeting May?


WIP: Use only index and node hashes for a witness proof

The proof format we're using from merkle-tools currently encodes the path directions in the proof data.
RIght now that's :
[{right: 'f9e2eaaa42d9fe9e558a9b8ef1bf366f190aacaa83bad2641ee106e9041096e4'},
{left: '29df505440ebe180c00857e92b0694c56a33762b08944472492b0cbf6ec607e3'}]

but we could also get it in binary which looks like:
// With asBinary set to true, an array of Buffers is returned
// 0x00 indicated 'left', 0x01 indicates 'right'
// example:
// proof == [
//   <Buffer 01>,
//   <Buffer 09096dbc49b7909917e13b795ebf289ace50b870440f10424af8845fb7761ea5>,
//   <Buffer 01>
//   <Buffer ed2456914e48c1e17b7bd922177291ef8b7f553edf1b1f66b6fc1a076524b22f>,
//   <Buffer 00>
//   <Buffer eac53dde9661daf47a428efea28c81a021c06d64f98eeabbdcff442d992153a8>
// ]

Instead of having a left/right property (or a boolean flag) I think our proof could just be
WitnessProof = {
  witness: Hash;
  nodes: Hash[];
  index: number;
};

We can use the index to calculate the path which is just the path information expressed as a uint. I think this would be more efficient than accepting an array of directions or some other format?
That does mean converting to and from the format for merkle-tools but it was pretty easy to handle that.

As mentioned in Slack, we would want to use a type like this when passing data to a solidity contract, for efficiency.
WitnessProof = {
  witness: Hash;
  nodes: Hash[];
  index: number;
};

so I give a 👍 to this idea


Comments on expenses sometimes not loading

This is hard to document/reproduce because it's intermittent, but sometimes the comments on an expense do not load, and sometimes older comments load but not more recent ones. For example today I answered a question in a comment, but when I went back later my post was not showing, even after reloading a few times. Finally it did appear again for apparently no reason.

This is still happening. On this one, it loaded Jason's comment, but not mine.


Upgrade react-datepicker so we can drop moment

Description
In trying to move from moment to date-fns in Studio, I found it's still being pulled in due to our version of react-datepicker which is very old.
This ticket is to try and update react-datepicker and make sure mr-ui has no regressions from this change

https://github.com/mapbox/mr-ui/issues/125


Server-Timing header missing when aot is set to false

If i initialize Elysia with aot set to false (as required to support Cloudflare Workers), the server-timing plugin doesn't return the Server-Timing header.
Minimal repro

Blocked by: https://github.com/elysiajs/elysia/issues/837


update sched.py for 2019 schedule page

Finished this before I saw your comment about IRE hosting its own CSV. Oh well, it was a good exercise.

Amazing. Thanks, for sussing this out, Joe! Glad it was a good exercise. Appreciate the help.


CredentialsPlugin: Support for environment stages, string, per-stage

Overview
Currently Credentials Plugin only supports the build stage and Username/Password credentail types.
The current use case I have requires mapping credentials onto TF_VAR_blah environment variables in the environment stages.  Furthermore, some of these credentials are of the string() type of DSL call.  Finally, some of these credentials differ between individual environment stage.
Current Workarounds
Currently I'm moving to decorating each stage directly in the Jenkinsfile for now.
def validate   = new TerraformValidateStage()
def deployDev  = new TerraformEnvironmentStage('dev')

deployDev.decorate(TerraformEnvironmentStage.ALL, { closure ->
  withCredentials([
    usernamePassword(
      credentialsId: 'some-user'
      usernameVariable: 'TF_VAR_some_user',
      passwordVariable: 'TF_VAR_some_passord'
    ),
    string(
      credentialsId: 'some-secret',
      variable: 'TF_VAR_some_secret'
    )
  ]) {
    closure()
  }
})

validate
  .then(deployDev)
  .build()

+1 - Need to be able to use CredentialsPlugin on RegressionStage

This sounds like at least 2 separate issues:

CredentialsPlugin should be available to every Stage
It should be possible to set unique credentials for  different instances of a Stage.

I'll use this Issue to tackle point 1, then split off a separate Issue for point 2.

Of the 3 issues outlined above, the first is taken care of with the above PR/Merge.
Thinking through the second (unique credentials per Environment), that seems a little tricky.  There's already a "pattern"  for environment-specific  configuration for plugins like the S3BackendBucket, but I don't think that pattern fits well with the UseCase here.
I'm gonna break 2 and 3 out into separate issues, so that the first (CredentialsPlugin  should be  applied to every Stage) can be released sooner.


Not possible to check the failure of cd?

Platform: Windows 7, node 0.12.7
It seems that there's no easy way to check for error of shelljs' cd. When trying to cd to non-existent folder:

it doesn't throw
the return value of the command is null (it seems it's undefined for successful cd, but the distiction is accidental I guess, nothing to rely on reliably)
it only displays an error to stdout (not stderr) and that's it.

It seems that I could check if cd succeeded, by getting process.cwd() and comparing it to desired location (and using path.normalize() to account for relative paths, Windows paths scheme etc), but it seems verbose.
Probably it would make sense to write your own wrapper which does shelljs.cd, verifies, and does something (abort script?) when it failed.
What is your preferred way of checking for errors of cd?
Do you think it would be useful to do some change in shelljs to better handle this?
This is my script:
#!/usr/bin/env node

var path = require('path');

try {
  var desiredTarget = 'd:/gh/doesNotExist';
  // var desiredTarget = 'd:/gh/test-shelljs';
  var out = require('shelljs').cd(desiredTarget);

  console.log("OUT:                  " + out);
  console.log("CWD:                  " + path.resolve(process.cwd()));
  console.log("path.resolve(target): " + path.resolve(desiredTarget));
} catch (e) {
  console.log("ERROR" + e);
}

and tests:
    me@mymachine /d/gh/test-shelljs   # desiredTarget = 'd:/gh/test-shelljs';
    $ ./test.js
    OUT:                  undefined
    CWD:                  d:\gh\test-shelljs
    path.resolve(target): d:\gh\test-shelljs

    me@mymachine /d/gh/test-shelljs   # desiredTarget = 'd:/gh/doesNotExist';
    $ ./test.js
    cd: no such file or directory: d:/gh/doesNotExist

    OUT:                  null
    CWD:                  d:\gh\test-shelljs
    path.resolve(target): d:\gh\doesNotExist

In my opinion, this is something that needs to be added to the project.
I think this is an issue in general with commands: they don't seem to return errors in a sensible way. Bash returns errors as return codes, and continues on. Since return values are already used for stdout usually (such as with ls()), that rules this out.
Changing this to return an object with fields like stdout, stderr, and return code would solve the issue, but might be cumbersome. This would likely break lines like echo(ls()), since ls() would now return an object, not an array. Lines such as if(pwd() === '/home/myusername') would be even trickier to fix.
Like you said above, if we throw an exception, that would indicate the error, but would diverge pretty far from shell scripts, since those continue through errors (cd myfakedir/; echo hi will always print "hi", regardless if myfakedir/ exists).
One thought is to set a global variable for the return status of the last command. This would get updated by every command. Then you could check its value much like one might do in bash with $?:
cd myfakedir/
if [ $? == 0 ]; then
  echo "it exists"
else
  echo "fake directory"
fi

If you want an invalid cd() to abort the script, you can always set the config.fatal value (see the docs)
If you'd prefer for it not to abort, but would like to check errors, you can use the error() function as seen above

I'll close this issue for now. If this isn't sufficient, please reopen the issue or ping this thread explaining what else you need.


Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'

It is in fact not possible to install OpenSSH using command given because per recommendation that wil be prevented with message

The requested operation requires elevation

As shown below. There is a lot of documentation on this error message. I think in excess of 100.000 pages on the internet try to address this issue but this won't be resolved really until MS fixes it. Currently there is no clear supported way to fix this issue. Most of recommendations won't work depending on the situation.
PS C:\Windows\system32> Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'
Get-WindowsCapability : The requested operation requires elevation.
At line:1 char:1
+ Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-WindowsCapability], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsCapabilityCommand

PS C:\Windows\system32>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 18a5a4e5-2604-23c2-1374-68a6974170bc
Version Independent ID: f93809cc-eb5e-6b9b-ed58-c8811a8ee21f
Content: Get started with OpenSSH
Content Source: WindowsServerDocs/administration/OpenSSH/OpenSSH_Install_FirstUse.md
Product: windows-server
Technology: administration
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

Hi @onknows,
Thanks for the feedback and dedication to our documentation.
I see this message you are receiving means you are either running this as a standard user or without an administrative context. The article does state to install OpenSSH using PowerShell, run PowerShell as an Administrator. This can be done by right clicking the PowerShell shortcut and selecting Run as administrator or by right clicking the Start button and selecting Windows PowerShell (Admin).
In addition, I will look at the current article to see if this should be made clearer. In the meantime, I am marking this documentation issue has been resolved and we are closing the issue. #please-close
To follow up on this documentation issue, leave us a comment with an @mention. To get assistance or support for your product issue, we recommend that you engage with the product community or open a ticket with Microsoft Support. For more information, see Contact Microsoft Support
Thanks,
Robin


V2 fails to parse number from string with spaces

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
see #6958
Such behavior is inconsistent with python (see example)
@hramezani

this is an intended change in V2

Could you provide the reason please?
Example Code
from pydantic import BaseModel

num = int(' 1 ')

assert num == 1

class Foo(BaseModel):
    num: int

foo = Foo(num=' 1 ')  # raises an error

Python, Pydantic & OS Version
pydantic version: 2.5.2
        pydantic-core version: 2.14.5
          pydantic-core build: profile=release pgo=true
                 install path: D:\AJOB3\data-cooking\.venv\Lib\site-packages\pydantic
               python version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
                     platform: Windows-10-10.0.19042-SP0
             related packages: typing_extensions-4.8.0

@valq7711 We've added strict mode in Pydantic V2 and here is the reason.
By default, strict mode is not enabled and you can provide a string for an int field. but strings with spaces can not be parsed to an int even in lax(non-strict) mode.
Pydantic V2 uses pydantic-core for validation/serialization, written in Rust. So, it might not be consistent with Python.
It's already mentioned in conversion table that strings Must be numeric only, e.g. [0-9]+. to be parsed as an int

@hramezani Thanks for your answer, but I still don't understand why not strip the string in lax-mode when converting to a number, doesn't Rust have such a feature?
I just want to say that when we
num: int
it intuitively means that it will work as int(input_value) because int is a native Python type, not a custom pydantic type with special behavior.
So why do we need to make extra moves to strip the input value, which will also reduce performance?

if you want native behavior - use native type as is,
if you want to change native behavior - use annotation + pre/post-validation
Why should it be the other way around?

@hramezani Thanks for your answer, but I still don't understand why not strip the string in lax-mode when converting to a number, doesn't Rust have such a feature?

For sure Rust does have it. probably it is Rust default behavior.

when you want to parse a string with spaces in Rust to an int, the following code will not work and will throw an error:
fn main() {
    let _: i32 = " 1 ".parse().unwrap();
}

you need to trim the string and then parse it:
fn main() {
    let _: i32 = " 1 ".trim().parse().unwrap();
}

So it seems it is not Rust default behavior when parsing a string to an int.
(the same result will happen if you use String::from(" 1 "))

@omercotkd Fine! So this could be easily fixed to make pydantic int/float behave like native python ones, because why should their behavior change based on implementation details without any significant reason?

PR welcome to fix this in pydantic-core - I think it'd be just about introducing .trim() in the right places and adding tests. This'll probably want to be done for int, float and decimal validators, maybe more.

Could I take this one. It will be a good opportunity for me to approach pydantic-core codebase which i'm interested in.

Go for it.

Fixed in https://github.com/pydantic/pydantic-core/pull/1203 - thanks @hungtsetse


add pylibdmtx

Please add the following dependency to the rosdep database.
Package name:
pylibdmtx
Package Upstream Source:
https://pypi.org/project/pylibdmtx/
Purpose of using this:
Datamatrix generation/reading for python scripts, pylibdmtx is a python wrapper for libdmtx.
Useful for any time you wish to work with datamatrix tags and you do not need the more performant aspects of c++ code.
I am currently using this to update textures in gazebo models to allow easy testing of different tag sizes and to generate labelled printable versions all datamatrix tags. I could do this task in c++ as libdmtx already exists in this repository, but a task like this lends itself better to python in my eyes.
Links to Distribution Packages:

Debian, Fedora, OSX, Ubuntu:

https://pypi.org/project/pylibdmtx/

@cottsay is this a bug in the CI? It seems to be detecting the pip installer as being a key?

is this a bug in the CI? It seems to be detecting the pip installer as being a key?

It is indeed a bug. Here's the fix: #31133


Search result not loading

Has been more than 2 weeks that I can't link tickets on Zendesk. It shows it's searching for the ticket, but no result is returned. Also, for tickets already linked, I cannot access them on the Linkets container, they don't appear there.
Is someone working on this bug?

Sorry to hear you're having an issue. Linkets is built on the Zendesk search API and tickets API. Sometimes linked tickets don't display immediately because the tickets haven't been re-indexed yet within Zendesk's search infrastructure. Sometimes there is an error updating the ticket via the API, but the error isn't displayed in the UI.
As a front-end app, it is difficult to debug issues without being able to "inspect" it when the issue occurs. If you're willing, you can use the 'Console' tab of Chrome Developer Tools to look for the cause of the error. If you can provide me with some more information, I can try to reproduce and fix the issue.
Also, please check the tags set on these tickets - if the tags are set correctly, and there are no errors in the Chrome console, then the issue is with Zendesk search results rather than with the Linkets app.
Please let me know if you can provide more detail on the bug, otherwise will close the issue as stale.


Merging new quickstarts to master

Description
Merging new quickstarts to master.
Issue reference
We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: NA
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary
[x] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

Resolving conflicts in https://github.com/dapr/quickstarts/pull/612


Bugfix: keyboardFocusedPair was not being cleared on widget destruction.

Using Colibri in my project I noticed crashes when destroying widgets in a window.
If the target widget was focused by the keyboard upon its destruction, the code would reach segfaults, as the keyboardFocusedPair pointer had not been cleared.
Secondly, removing the widget at index 0 in the window would cause m_defaultChildWidget to be decremented and wrap around to a large number, eventually causing nonsense pointers to be read from lists.

Nice catch!
Thanks for your contribution!


Add AirUnlock 0.4 (OSX/Android BT unlock pair)

Add AirUnlock cask, which creates a status bar icon that listens for BT LE hashes from an Android client to unlock the Mac using the biometrics on the Android phone:
AirUnlock for Android:
https://github.com/pinetum/AirUnlock-for-Android
https://f-droid.org/packages/tw.qtlin.mac.airunlocker/

After making all changes to the cask:

[X] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} reports no offenses.
[X] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[X] Named the cask according to the [token reference].
[X] brew cask install {{cask_file}} worked successfully.
[X] brew cask uninstall {{cask_file}} worked successfully.
[X] Checked there are no [open pull requests] for the same cask.
[X] Checked the cask was not already refused in [closed issues].
[X] Checked the cask is submitted to [the correct repo].

Two commits as I think the caveat is useful, otherwise it's a useless cask, but two options for you, commit whichever you feel is more appropriate.


[re2] Update library to 2019-09-01

Update re2 library to 2019-09-01 version.

Thanks for the port update and all these contributions, @ehsan-mohammadi!


Remove braces {{arg}}

Could the markup braces be removed from the displayed pages? For example, the cut TLDR page displays (https://tldr.ostera.io/cut)
cut -c {{1-16}}

If the user copies and pastes this directly, the bash shell interprets it as
cut -c 1 6 { }

which gives the error message
❯❯❯ cut -c {{1-16}}
cut: 6: No such file or directory
cut: {: No such file or directory
cut: }: No such file or directory

Which is pretty confusing for someone new to the command line.
It would be better I think to either remove the braces or convert it to italic or bold. For example

cut -c 1-16

or convert it to italic or bold

or underlined :)


Using nowrap to prevent multiline titles.

Before:

Now:

Can you also add text-overflow: ellipsis  to make it display ... at the end?

done


Add support for more services

Add support for more services. Please comment here if you have one you'd like to see sooner rather than later.

Do you know how many active users and how much usage each service has? The services should be added according to their commercial value or popularity.

I was just reading some older blogs and was looking for a lib like this.  Are there any plans for move this forward.  I like the presentation at re:invent 2014 and the resource api seemed really natural to use.


Incorrect finnish language translation

Translation file fi_FI.csv line 77.
"Couldn't successfully establish connection to payment provider","Yhteyden muodostaminen maksupalveluun epäonnisui" ( epäonnistui )

@Userr017 This has been fixed in the latest version. Thank you for reporting!
https://github.com/OPMerchantServices/op-payment-service-for-magento-2/releases/tag/v1.1.4


Idea: selection.end()

I'm a fan of jQuery's .end() method. I think a similar d3-selection method would be useful.
Example:
d3.select('body')
  .selectAll('svg')
    .data(...)
    .enter()
      .append('svg')
        .attr(...)
        .append('g')
          .each(...)
        .end() // g
      .end() // svg
      .append('p').text("I'm below each svg element.").end()
    .end() // enter
  .end() // join
  .append('p').text("I'm at the end of the body element.");

Not sure how it would work with merge, or if the data join causes other problems.
Would you be interested if I wrote a quick PR?

This is a little different but related to ideas discussed previously in d3/d3#1966 and d3/d3#1618. This is different in that it explicit refers to the originating selection rather than being a DOM-based operation (so each selection would need to track its originating selection to move back up the method chaining stack). My recommendation is that you use a local variable rather than trying to do everything as a single statement with method chaining, but I suspect that with some effort you could implement such a feature with a plugin that extends the d3.selection.prototype.

I think you could use the d3.parent plugin to do this.

Thanks for the feedback.
I agree that I am attempting to achieve a similar coding style as in d3/d3#1966. But, as already noted, it is less about navigating the DOM and more about returning to a previous state (i.e. the originating selection). The d3.parent plugin is solving a different problem and would work in many cases but wouldn't help when using filter and data joins.
To implement my idea as a plugin would require wrapping (almost) every method that produces a new Selection and associating the originating selection to the new selection, effectively building a stack of selections. The alternative would be to maintain a heap of stacks and wrap the constructor and somehow determine which stack to push it on to (I don't think that information would be available to the constructor). The former approach is very sensitive to changes to the d3-selection module; whenever a new selection is returned from a future method it would need to be wrapped by the plugin. The effort of maintenance doesn't seem to be worth, what is essentially, a stylistic preference of my own. I might change my mind and put the effort in but for now I'll close this issue :)

It’s true, but some methods such as selection.append and selection.insert are built on top of selection.select, so it might not be a small enough set of methods to be feasible. And I don’t currently anticipate new methods that construct selections directly… but anything is possible.


Stickybits demo page is broken on IE11

Hi,
grats on the great package, loving it! 💯 Unfortunately, there is a bug in IE11 it seems:
Requested Update
When using IE11 on the stickybits demo page, scrolling even 1 px makes the menu bar stick to the top. On the other browsers this works as intended, with the menu bar scrolling to the top with the rest of the page, and then sticking.
Why Is This Update Needed?
This is an unintentional bug in the package that occurs during normal usage as well.
Could you please look into this?

@mezoistvan thanks for your follow through on this issue. I will review this issue asap.

Thanks for the quick fix! 👍


keystore and letsencrypt new CA

Unsure where to raise something? Here are some of the common places:
Problem description:
I'm really not sure where to place the request so I try it here.
Until Let's Encrypt changed to new intermediate CA it was possible to access a Let's Encrypt secured web application from java, unluckily this is now no longer the case.
I found an article that  the root CA will also change in Jan. 2021 and It would be nice if the Let's Encrypt certs can find the way into the openjdk keystore as trusted CA.
Additional Information:
https://letsencrypt.org/certificates/
https://heise.de/-4958108 (german article)

Please test with one of our nightly builds: https://adoptopenjdk.net/nightly.html
They all have new trust stores. Was intended to land in time for the October updates but did not make it.

Closing due to lack of requested feedback. We're happy to reopen the issue if feedback is provided by the OP (or anybody else) at a later date.
Besides, Let's Encrypt announced that they'll cross-sign their new root certificate, so there shouldn't be any problem until the January 21 updates which include our new trust store.


Update quickstart.rst doc for awareness of Flask extensions

Addresses concerns in issue #532 regarding not knowing about flask extensions as it is not mentioned the quick start guide. Maybe this can help increase the awareness of flask extensions to new users?

That seems sufficient, thanks!


🐛 [BUG] - critical security problems from vm2

Browsers
Firefox, Chrome, Safari, Microsoft Edge, Opera
OS
Windows, Linux, Mac
Description
As dependabot told us, vm2 has a fatal problem. Therefore, starting with the vm2 module in question, the<EMAIL_ADDRESS>module must also be replaced/modified.
dependabot이 알려준 것과 같이 vm2에는 치명적인 문제가 있다고 합니다. 따라서 문제가 있는 vm2 모듈부터<EMAIL_ADDRESS>모듈도 대체/수정해야합니다.
https://github.com/TooTallNate/proxy-agents/issues/240
https://github.com/TooTallNate/proxy-agents/pull/224
As in Issue and Pull-Request above, vm2 used in proxy-agent's degenerator module has been removed. Therefore, it seems that the re-installation will solve the problem.
위의 Issue와 Pull-Request와 같이 proxy-agent의 degenerator 모듈에서 사용되었던 vm2가 제거가 되었다고 합니다. 따라서 재설치를 진행한다면 해당 문제가 해결될 것으로 보입니다.
Reproduction URL
https://github.com/AgainIoT/Open-Set-Go_server/security/dependabot/5
Reproduction Steps
https://github.com/AgainIoT/Open-Set-Go_server/security/dependabot/5

Solutions
https://github.com/TooTallNate/proxy-agents/issues/240
https://github.com/TooTallNate/proxy-agents/pull/224

As in Issue and Pull-Request above, vm2 used in proxy-agent's degenerator module has been removed. Therefore, it seems that the re-installation will solve the problem.
위의 Issue와 Pull-Request와 같이 proxy-agent의 degenerator 모듈에서 사용되었던 vm2가 제거가 되었다고 합니다. 따라서 재설치를 진행한다면 해당 문제가 해결될 것으로 보입니다.

Screenshots
No response

I can find solution from this issue
https://github.com/nest-modules/mailer/issues/723


terminfo and kitty term

        TERM=xterm-kitty
was not found in the database provided by tcell library. Please try checking if
a supplemental database is found for your terminal at one of the following URLs:
        https://github.com/gdamore/tcell/raw/master/terminfo/database/98/98d2a8a0
        https://github.com/gdamore/tcell/raw/master/terminfo/database/98/98d2a8a0.gz
If yes, download it and save in the following directory:
        $HOME/.tcelldb/98/
then try running "up" again. If that does not work for you, please first consult:
        https://github.com/akavel/up/issues/15
and if you don't see your terminal code mentioned there, please try asking on:
        https://github.com/gdamore/tcell/issues
Or, you might try changing TERM temporarily to some other value, for example by
running "up" with:
        TERM=xterm up
Good luck!```

How to get it to work with `xterm-kitty` ? http://www.9bis.net/kitty/

Did you try following the instructions as explained above, in the text you quoted? Is something about them unclear?

Running into issues with both fish shell and exporting TERM. It doesn't seem to want to play nice at all.

What issues? What "it"? How specifically "doesn't seem to want to play nice"? I'm afraid it's hard for me to try and help you when I don't really understand the question :( Also, I'm really sorry, but I don't have enough time and resources to be able to install kitty or fish myself for debugging this, so you'd really help me if you could provide explanatory information and context under assumption I'm using a different terminal emulator & shell... Thanks for reporting this issue and caring to further talk about it!

I'm marking this as blocked waiting for response; I'm afraid I can't currently proceed without answers & clarifications that would make the issue understandable to me in detail.

I think upgrading the tcell dependency in go.mod to https://github.com/gdamore/tcell/commit/4e7865679e391b0f1a9296e428edce5eb421790a or newer could auto-resolve this. I will try to do this At Some Point In The Future™, though not yet sure when exactly, as I don't have much time for up maintenance recently. And I'd like to add some tests to the codebase before that, to give me some kind of confidence that the upgrade won't break stuff...

+1 to this issue. Would be great indeed to upgrade tcell and get kitty out of the box. Amazing project by the way!


Sleep routines are not documented

It would be great to have them searchable in bar

Just pushed some docs for the sleep-related functions.  It should be live on the server in half an hour or so.  If that's what you were after, simply close the ticket.  If not, let me know what else you'd like to have and I'll extend the docs.

Great, it seems to be enough to know how to use it. I reviewed it for copy-paste mistakes also.


[CP][beta channel] ec48e8f - DDC: Fix missing nullability from recursive type hierarchies

commit(s) to merge: ec48e8f323d68717cd3fed94abd85d4f82ea1ce7
merge instructions: clean merge
What is the issue: DDC uses a different code path when compiling mixins or extends clauses that lead to a circular reference of the class itself. That code path was losing nullability information (nullable, or legacy) of the types when they appear in those positions.
What is the fix: Stop ignoring the nullability and emit them properly in those code patterns.
Why cherrypick: This is a correctness issue, mostly noticeable when running in sound null safety mode. The bug has been present since we unforked the SDK but it was noticed and reported recently by an external Flutter Web user.
Risk: Low risk because the fix targets a code path that is only used by circular class hierarchies and then the hierarchy must include a nullable type for the change to make any difference.
Link to original  issue(s): https://github.com/dart-lang/sdk/issues/45767
/cc @kevmoo @mit-mit @whesse @athomas @vsmenon @franklinyow @sigmundch

@leafpetersen - we are curious to hear your thoughts on the severity of the issue here.
I'm ambivalent this time around. I agree it's low risk and I'd have gone for it a couple weeks back, but given the higher bar for cherry-picking at this time, I'm inclined to wait for the next release and not cherry-pick.

I'm still supportive of a cherry pick.  The change is DDC only, so the risk is highly ring-fenced.  The problem is somewhat esoteric, but it was found organically, and if I understand correctly this bug will be more likely to surface as apps turn on sound null safety.

CC: @kf6gpe

Are we discussing this for Dart 2.13 beta? If so, the window opens again om the week of 5/21. Can we wait that long given the fact that it's an esoteric case? Or hotfix in Dart and pick it up in Flutter when we hotfix Flutter that week?

Discussed in SCURM meeting.  This can wait until 5/12.  We are approving this for 5/21 window
I will update the label and title in a later date.

Description:
Fix missing nullability from recursive type hierarchies, see #45767 for detail

Merged to stable 375a2d7c66c8eb5d40872bdb57dd664b5f850d94 (2.13.1).


docs: add issue template

Describe the bug
We should update the issue template. We can add more new things like emoji, tags for issues, and titles for every issue, like Docs:, Feat:, Bug:. This way, we can understand the purpose of the issue raised by just seeing the title.
Expected behavior
We can see all issues with a good title so we can easily understand the purpose for which the issue was created.
Screenshots

@Akshat111111    , I'd like to work on this issue under GSSOC. Could you please add the necessary label and tag to the issue and assign it to me?

I would like to work on this issue. Please assign it to me.


LFS quota error when installing package

Hi all,
Thanks for the amazing work!
I tried installing the package with pip install git+https://github.com/TIGER-AI-Lab/TIGERScore.git, but I got the following error:
Collecting git+https://github.com/TIGER-AI-Lab/TIGERScore.git
  Cloning https://github.com/TIGER-AI-Lab/TIGERScore.git to /tmp/pip-req-build-klia4nto
  Running command git clone --filter=blob:none --quiet https://github.com/TIGER-AI-Lab/TIGERScore.git /tmp/pip-req-build-klia4nto
  Downloading data/evaluation/instruct/mixinstruct/test_data_prepared.json (106 MB)
  Error downloading object: data/evaluation/instruct/mixinstruct/test_data_prepared.json (17f3d73): Smudge error: Error downloading data/evaluation/instruct/mixinstruct/test_data_prepared.json (17f3d7308d0a2207d8c302d599281157a6578ed99bfcb91aec41e7c9ec9bcf6b): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Based on the error message, the problem seems to be related to your LFS quota. Could you fix this? If there is something to be done on my end, please let me know.

Would you mind trying it again? I just purchased more quota.

It works now, thanks!


Make Start Throwing Error - Install Problem, Invalid port 8125

Getting below error when I tried to make start. Any help would be really appreciated.
root@Jumphost2:/home/open-nti# make start
Use docker compose file: docker-compose.yml
IMAGE_TAG=latest docker-compose -f docker-compose.yml up -d
ERROR: for opennti  Invalid port "_ServicePort(target=8125, published=8125, protocol=u'udp', mode=None, external_ip=None)", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 68, in main
command()
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 118, in perform_command
handler(command, command_options)
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 926, in up
scale_override=parse_scale_args(options['--scale']),
File "/usr/local/lib/python2.7/dist-packages/compose/project.py", line 424, in up
get_deps
File "/usr/local/lib/python2.7/dist-packages/compose/parallel.py", line 69, in parallel_execute
raise error_to_reraise
ValueError: Invalid port "_ServicePort(target=8125, published=8125, protocol=u'udp', mode=None, external_ip=None)", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
make: *** [start] Error 1

Tried again by removing images, getting same error
Step 13/13 : CMD /source/start-input-snmp.sh
---> Running in 81767ced3075
---> 48adb857550d
Removing intermediate container 81767ced3075
Successfully built 48adb857550d
Successfully tagged opennti_input-snmp:latest
WARNING: Image for service input-snmp was built because it did not already exist. To rebuild this image you must use docker-compose build or docker-compose up --build.
ERROR: for opennti  Invalid port "_ServicePort(target=8125, published=8125, protocol=u'udp', mode=None, external_ip=None)", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 68, in main
command()
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 118, in perform_command
handler(command, command_options)
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 926, in up
scale_override=parse_scale_args(options['--scale']),
File "/usr/local/lib/python2.7/dist-packages/compose/project.py", line 424, in up
get_deps
File "/usr/local/lib/python2.7/dist-packages/compose/parallel.py", line 69, in parallel_execute
raise error_to_reraise
ValueError: Invalid port "_ServicePort(target=8125, published=8125, protocol=u'udp', mode=None, external_ip=None)", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
make: *** [start] Error 1

Hi,
Did you still have this problem? if so try to remove the input-snmp stanza from docker-compose file and try again (just to confirm if this problem belong only to that plugin installation)
Regarfds

Thanks for getting back. I forgot to close this, issue got resolved once i
rebooted the server and started the docker.
Cheers,
-Mohan
On Wed, Aug 23, 2017 at 3:34 AM, Efrain<EMAIL_ADDRESS>wrote:

Hi,
Did you still have this problem? if so try to remove the input-snmp stanza
from docker-compose file and try again (just to confirm if this problem
belong only to that plugin installation)
Regarfds
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Juniper/open-nti/issues/174#issuecomment-324246607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcT0Oze8QXRLL2DxEcCA_6jgcxShyahYks5sa9YTgaJpZM4OIgB7
.


Link error due to WIN32 in add_executable() call

Executable link fails because /SUBSYSTEM:WINDOWS is defined when add_executable() has WIN32 argument.
Suggested fix:

Remove WIN32 from add_executable(${PROJECT_NAME} WIN32 ${sources}) call
Remove set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} /SUBSYSTEM:CONSOLE") line because this flag is controlled by the presence of WIN32  argument as stated above

What toolchain are you building with that causes a link failure? While the fix looks good, it also links fine on the internal CI system that we release from, so I'd like to understand a bit more about your toolchain so I can try and understand why ours still builds the binary OK.
I'll release v1.0.2 shortly with the fix, thanks!

Thank you!
Here is a part of CMakeCache.txt. Let me know if you need more info.
########################
# EXTERNAL cache entries
########################

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/lib.exe

//For backwards compatibility, what version of CMake commands and
// syntax should this version of CMake try to support.
CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Debug

//Id string of the compiler for the CodeBlocks IDE. Automatically
// detected when left empty
CMAKE_CODEBLOCKS_COMPILER_ID:STRING=

//The CodeBlocks executable
CMAKE_CODEBLOCKS_EXECUTABLE:FILEPATH=CMAKE_CODEBLOCKS_EXECUTABLE-NOTFOUND

//Additional command line arguments when CodeBlocks invokes make.
// Enter e.g. -j<some_number> to get parallel builds
CMAKE_CODEBLOCKS_MAKE_ARGUMENTS:STRING=

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe

//Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc

//Flags used by the CXX compiler during DEBUG builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=/MDd /Zi /Ob0 /Od /RTC1

//Flags used by the CXX compiler during MINSIZEREL builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

//Flags used by the CXX compiler during RELEASE builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /DNDEBUG

//Flags used by the CXX compiler during RELWITHDEBINFO builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C++ applications.
CMAKE_CXX_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe

//Flags used by the C compiler during all build types.
CMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3

//Flags used by the C compiler during DEBUG builds.
CMAKE_C_FLAGS_DEBUG:STRING=/MDd /Zi /Ob0 /Od /RTC1

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

//Flags used by the C compiler during RELEASE builds.
CMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /DNDEBUG

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_DEPENDS_USE_COMPILER:UNINITIALIZED=FALSE

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during RELEASE builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/Program Files (x86)/FidelityFX_CLI

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/link.exe

//Program used to build from makefiles.
CMAKE_MAKE_PROGRAM:STRING=nmake

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELEASE builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Path to a program.
CMAKE_MT:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.19041.0/x64/mt.exe

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=FidelityFX_CLI

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.19041.0/x64/rc.exe

//Flags for Windows Resource Compiler during all build types.
CMAKE_RC_FLAGS:STRING=-DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of shared libraries
// during RELEASE builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE

Thanks, that was helpful! I've reviewed the CMake documentation around how WIN32 triggers the WIN32_EXECUTABLE property being set and agree that your fix is correct. I'll release v1.0.2 shortly to incorporate that fix.
Thanks for the bug report and detailed help!

Fixed in a2b2040, thanks again!


Sprite issue with drills

I noticed that the precission drills now become "oh nos" when placed over minable materials. This is purely a visual glitch, and they still work... Other mods also have this issue I've noticed as well. Drills that match existing drills don't seem to have issues, but gigantic ones have their 'center' turn into the placeholder sprite as well

This is fixed with 2.2 Update


Fix XPM color parsing

XPM colors are more complicated than what the XPM parser was able to handle.
The specification is here:
https://www.xfree86.org/current/xpm.pdf
I discovered these edge cases in the Picons archive, which is a rather old collection of profile pictures: https://kinzler.com/picons/ftp/

Thanks so much for this. Looks like CI found a style issue.
I am curious about why this includes 2 previously landed commits, do you know what happened? (I think maybe your fork was not up to date when you opened the PR - if you can rebase it on the upstream main they may go away).

Thanks, I fixed both the linter warning and the weirdness with the additional commits.  (It's only one now.)

Side remark: I created at related bug on the libxpm bug tracker about three-digit hex colors in XPM: https://gitlab.freedesktop.org/xorg/lib/libxpm/-/issues/7

Side remark: I created at related bug on the libxpm bug tracker about three-digit hex colors in XPM: https://gitlab.freedesktop.org/xorg/lib/libxpm/-/issues/7

Updated the pull request to fix that issue - #fff is indeed #f0f0f0 and not #ffffff as I previously thought.

Please try not to force-push after reviews have been submitted - it basically invalidates the previous discussions.

Thanks so much for your first contribution to our repository 🥇


Menu bar keyboard shortcuts conflict

When the "Auto Hide Menu Bar" is enabled in the settings, some of the keyboard combinations to bring it up do not work, because they seem to conflict with other assignments eg Alt + f and Alt + h
To reproduce:

Check "Auto Hide Menu Bar" in settings
Have a file opened
Clicking Alt + f will behave like Ctrl + Right arrow, instead of opening the "File" popup from the menu bar

Duplicate of #4057, please subscribe there for updates.


Update akka-actor, akka-testkit to 2.6.5

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-testkit

from 2.6.4 to 2.6.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch

Pull Request Test Coverage Report for Build 64

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 87.302%

Totals

Change from base Build 63:
-0.4%

Covered Lines:
55

Relevant Lines:
63

💛  - Coveralls


Postcode as a start route

Adds a postcode prop to the web component to allow people to skip location entry
Wraps the app in a global app state provider, will probably use this for more stuff later
We need to handle navigation inside the start route because that's where routeProvider will be available

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Disambiguation code example, why prefer sea-orm or diesel over the other library

Motivation
We had some questions regarding the differences between sea-orm and diesel are. While there is an article on the manual about this question, it does not go into detail to allow new users to understand these differences and why one would choose for this or that library. Adding a directly visible code example would help here.
Proposed Solutions
Add examples to the mentioned article, one for when to use diesel, and one for sea-orm

Hey @mohs8421, thanks for the filing! As said on Discord, I'd open this up and see if anyone what to pick this up and contribute. If no, then I'll take hop in and work on it later. Thanks!!

@billy1624 Can I work on this one? It seems like it doesn't require much experience

Hey @pratushrai0309, I think this is a good starting point!! Let me know if you need help :)
Some reference and resource for you.

https://www.sea-ql.org/sea-orm-tutorial
https://www.sea-ql.org/SeaORM
https://github.com/SeaQL/sea-orm/tree/master/examples
https://github.com/diesel-rs/diesel/tree/master/diesel_bench/benches/sea_orm_benches

Btw... I think these two issues are for new contributors. And it's relative simpler compare to this issue.

https://github.com/SeaQL/sea-orm/issues/826
https://github.com/SeaQL/sea-orm/issues/888

@billy1624 Ok, I am gonna try them first


below 0.3.0 records an unclean exit (crash)

This happens when I'm emerging packages in Gentoo:
# ~ $ below
# ~ $ echo $?
1
# ~ $ below
Nov 04 12:05:08.863 ERRO
----------------- Detected unclean exit ---------------------
Error Message: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }: "portage/net-fs:samba-4.14.9.ccy1d170/io.stat": Permission denied (os error 13)
-------------------------------------------------------------

# ~ $ journalctl -et below --no-hostname
Nov 04 10:45:33 below[2296112]: Nov 04 10:45:33.016 DEBG Starting up!
Nov 04 10:45:38 below[2296112]: Nov 04 10:45:38.015 ERRO System error, errno: 1
Nov 04 10:45:43 below[2296112]: Nov 04 10:45:43.016 WARN bpf error channel disconnected
Nov 04 11:37:13 below[2296112]: Nov 04 11:37:13.202 ERRO panic 'cmdline receiver hung up: SendError { .. }': below/procfs/src/lib.rs:630
Nov 04 11:37:13 below[2296112]: Backtrace is not available.
Nov 04 11:37:18 below[2296112]: Nov 04 11:37:18.175 ERRO panic 'cmdline receiver hung up: SendError { .. }': below/procfs/src/lib.rs:630
Nov 04 11:37:18 below[2296112]: Backtrace is not available.
Nov 04 11:49:28 below[2296112]: Nov 04 11:49:28.238 ERRO panic 'cmdline receiver hung up: SendError { .. }': below/procfs/src/lib.rs:630
Nov 04 11:49:28 below[2296112]: Backtrace is not available.
Nov 04 11:55:48 below[2296112]: Nov 04 11:55:48.197 ERRO panic 'cmdline receiver hung up: SendError { .. }': below/procfs/src/lib.rs:630
Nov 04 11:55:48 below[2296112]: Backtrace is not available.
Nov 04 12:03:23 below[2296112]: Nov 04 12:03:23.230 ERRO panic 'cmdline receiver hung up: SendError { .. }': below/procfs/src/lib.rs:630
Nov 04 12:03:23 below[2296112]: Backtrace is not available.

sys-fs-cgroup.tree.txt

What happens when you start with below --debug?

I think this might be similar to what I'm seeing as well:
below --debug
libbpf: loading object exitstat_bpf from buffer
libbpf: elf: section(3) tracepoint/sched/sched_process_exit, size 1648, link 0, flags 6, type=1
libbpf: sec tracepoint/sched/sched_process_exit: found program tracepoint__sched__sched_process_exit at insn offset 0 (0 bytes), code size 206 insns (1648 bytes)
libbpf: elf: section(4) .reltracepoint/sched/sched_process_exit, size 16, link 22, flags 0, type=9
libbpf: elf: section(5) .maps, size 24, link 0, flags 3, type=1
libbpf: elf: section(6) license, size 4, link 0, flags 3, type=1
libbpf: license of exitstat_bpf is GPL
libbpf: elf: section(13) .BTF, size 32092, link 0, flags 0, type=1
libbpf: elf: section(15) .BTF.ext, size 1692, link 0, flags 0, type=1
libbpf: elf: section(22) .symtab, size 312, link 1, flags 0, type=2
libbpf: looking for externs among 13 symbols...
libbpf: collected 0 externs total
libbpf: map events: at sec_idx 5, offset 0.
libbpf: map events: found type = 4.
libbpf: map events: found key_size = 4.
libbpf: map events: found value_size = 4.
libbpf: sec .reltracepoint/sched/sched_process_exit: collecting relocation for section(3) tracepoint/sched/sched_process_exit
libbpf: sec .reltracepoint/sched/sched_process_exit: relo #0: insn #198 against events
libbpf: prog tracepoint__sched__sched_process_exit: found map 0 (events, sec 5, off 0) for insn #198
Nov 10 22:35:30.572 ERRO
----------------- Detected unclean exit ---------------------
Error Message: Invalid file format: "/proc/1/cgroup"
-------------------------------------------------------------

I backported a few patches and have a PR (22894) in the Gentoo repository, which should fix this.

I'm using the current Gentoo version 0.4.1 but the problem persists: While portage with cgroup support is running, I can no longer run below with user permission, only running as root works. The problem is that below cannot read the contents of the portage cgroup.
This is only a problem during initialization of below. If it is already running, it seems to just ignore that problem, i.e. it does not crash.

Can you add the output of the following commands? It should be similar to this:
$ grep ^rc_cgroup /etc/rc.conf
rc_cgroup_mode="unified"
rc_cgroup_controllers="cpu memory io writeback pids cpuset device freezer perf_event"
rc_cgroup_cleanup="YES"

$ mount | grep cgroup
none on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)

$ ls -lah /sys/fs/cgroup/
total 0
dr-xr-xr-x  8 root root 0 Nov 22 14:44 .
drwxr-xr-x 13 root root 0 Nov 22 14:44 ..
drwxr-xr-x  2 root root 0 Nov 22 14:44 1
-r--r--r--  1 root root 0 Nov 22 14:44 cgroup.controllers
-rw-r--r--  1 root root 0 Nov 22 14:44 cgroup.max.depth
-rw-r--r--  1 root root 0 Nov 22 14:44 cgroup.max.descendants
-rw-r--r--  1 root root 0 Nov 22 14:44 cgroup.procs
-r--r--r--  1 root root 0 Nov 22 14:44 cgroup.stat
-rw-r--r--  1 root root 0 Nov 22 14:44 cgroup.subtree_control
-rw-r--r--  1 root root 0 Nov 22 14:44 cgroup.threads
-rw-r--r--  1 root root 0 Nov 22 14:44 cpu.pressure
-r--r--r--  1 root root 0 Nov 22 14:44 cpuset.cpus.effective
-r--r--r--  1 root root 0 Nov 22 14:44 cpuset.mems.effective
-r--r--r--  1 root root 0 Nov 22 14:44 cpu.stat
drwxr-xr-x  2 root root 0 Nov 22 14:44 dbus
drwxr-xr-x  2 root root 0 Nov 22 14:44 elogind
-rw-r--r--  1 root root 0 Nov 22 14:44 io.cost.model
-rw-r--r--  1 root root 0 Nov 22 14:44 io.cost.qos
-rw-r--r--  1 root root 0 Nov 22 14:44 io.pressure
-r--r--r--  1 root root 0 Nov 22 14:44 io.stat
-r--r--r--  1 root root 0 Nov 22 14:44 memory.numa_stat
-rw-r--r--  1 root root 0 Nov 22 14:44 memory.pressure
-r--r--r--  1 root root 0 Nov 22 14:44 memory.stat
-r--r--r--  1 root root 0 Nov 22 14:44 misc.capacity
drwxr-xr-x  2 root root 0 Nov 22 14:44 NetworkManager
drwxr-xr-x  2 root root 0 Nov 22 14:44 sysklogd
drwxr-xr-x  2 root root 0 Nov 22 14:44 udev

Make sure to check that you are using v2 cgroups by setting rc_cgroup_mode="unified" in the /etc/rc.conf. Using hybrid isn't tested/supported.

If this is a Gentoo specific bug please report in the appropriate bug tracker.

I'm using systemd, so there's no rc.conf which does anything useful (and I don't even have one):
# systemctl --version
systemd 249 (249)
+PAM -AUDIT -SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL -ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified

Unified cgroups are enabled.
# mount | grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
tmpfs on /sys/fs/cgroup/portage type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/portage/python3.9/cgroup-release-agent,name=portage)

Portage mounts a different cgroup hierarchy while running. It uses it for PID tracking of build processes.
# ls -lah /sys/fs/cgroup/
insgesamt 0
dr-xr-xr-x 14 root root 0 22. Nov 19:13 ./
drwxr-xr-x 11 root root 0 21. Nov 13:21 ../
-r--r--r--  1 root root 0 21. Nov 13:21 cgroup.controllers
-rw-r--r--  1 root root 0 22. Nov 20:58 cgroup.max.depth
-rw-r--r--  1 root root 0 22. Nov 20:58 cgroup.max.descendants
-rw-r--r--  1 root root 0 21. Nov 13:21 cgroup.procs
-r--r--r--  1 root root 0 22. Nov 20:58 cgroup.stat
-rw-r--r--  1 root root 0 22. Nov 20:06 cgroup.subtree_control
-rw-r--r--  1 root root 0 22. Nov 20:58 cgroup.threads
-rw-r--r--  1 root root 0 21. Nov 13:21 cpu.pressure
-r--r--r--  1 root root 0 21. Nov 13:21 cpu.stat
drwxr-xr-x  2 root root 0 21. Nov 13:21 dev-hugepages.mount/
drwxr-xr-x  2 root root 0 21. Nov 13:21 dev-mqueue.mount/
drwxr-xr-x  2 root root 0 21. Nov 13:21 init.scope/
-rw-r--r--  1 root root 0 22. Nov 20:58 io.cost.model
-rw-r--r--  1 root root 0 22. Nov 20:58 io.cost.qos
-rw-r--r--  1 root root 0 21. Nov 13:21 io.pressure
-rw-r--r--  1 root root 0 22. Nov 20:58 io.prio.class
-r--r--r--  1 root root 0 21. Nov 13:24 io.stat
drwxr-xr-x  5 root root 0 21. Nov 13:22 machine.slice/
drwxr-xr-x  5 root root 0 22. Nov 03:50 maintenance.slice/
-rw-r--r--  1 root root 0 21. Nov 13:21 memory.pressure
-r--r--r--  1 root root 0 21. Nov 13:21 memory.stat
dr-xr-xr-x  2 root root 0 22. Nov 19:13 portage/
drwxr-xr-x  2 root root 0 21. Nov 13:21 portage.slice/
drwxr-xr-x  2 root root 0 21. Nov 13:21 sys-fs-fuse-connections.mount/
drwxr-xr-x  2 root root 0 21. Nov 13:21 sys-kernel-config.mount/
drwxr-xr-x  2 root root 0 21. Nov 13:21 sys-kernel-debug.mount/
drwxr-xr-x 68 root root 0 22. Nov 20:55 system.slice/
drwxr-xr-x  3 root root 0 21. Nov 13:22 user.slice/

# ls -lah /sys/fs/cgroup/portage
insgesamt 0
dr-xr-xr-x  2 root root 0 22. Nov 19:13 ./
dr-xr-xr-x 14 root root 0 22. Nov 19:13 ../
-rw-r--r--  1 root root 0 22. Nov 20:03 cgroup.clone_children
-rw-r--r--  1 root root 0 22. Nov 20:03 cgroup.procs
-r--r--r--  1 root root 0 22. Nov 20:03 cgroup.sane_behavior
-rw-r--r--  1 root root 0 22. Nov 19:13 notify_on_release
-rw-r--r--  1 root root 0 22. Nov 19:13 release_agent
-rw-r--r--  1 root root 0 22. Nov 20:03 tasks

While it is running, it will create folders inside that latter directory for each package build:
# tree /sys/fs/cgroup/portage
/sys/fs/cgroup/portage
├── cgroup.clone_children
├── cgroup.procs
├── cgroup.sane_behavior
├── notify_on_release
├── release_agent
├── sys-devel:gcc-11.2.0.i8q8msdx
│   ├── cgroup.clone_children
│   ├── cgroup.procs
│   ├── notify_on_release
│   └── tasks
└── tasks

# ls -al /sys/fs/cgroup/portage/sys-devel:gcc-<IP_ADDRESS>qb2887m/
insgesamt 0
drwx------ 2 root root 0 22. Nov 21:01 .
dr-xr-xr-x 3 root root 0 22. Nov 19:13 ..
-rw-r--r-- 1 root root 0 22. Nov 21:01 cgroup.clone_children
-rw-r--r-- 1 root root 0 22. Nov 21:01 cgroup.procs
-rw-r--r-- 1 root root 0 22. Nov 21:01 notify_on_release
-rw-r--r-- 1 root root 0 22. Nov 21:01 tasks

I think this may be caused by Gentoo-specific handling of cgroup in portage but don't think that Gentoo's "below" should carry a Gentoo-specific patch because that usage of cgroups could occur in the wild even for non-Gentoo systems.
OTOH, I'm not sure if the tmpfs should even be mounted to /sys/fs/cgroup/portage - is that really needed for portage cgroup feature to work? Couldn't it just be mounted anywhere, e.g. in /var/tmp/portage/cgroup maybe? In that case, it would actually be worth reporting to b.g.o.

FWIW I was finally able to get a systemd based machine for testing and everything seems to work fine (ie non root user) for 0.4.1.
 While it is running, try starting below, observe the following behavior:

If you start below before emerge, below continues to work just fine.
If you start below while emerge is doing work, below will crash.

I'm not even sure if that needs a systemd machine - it probably doesn't. The simple fact is that programs can create custom cgroups for whatever reason they intent, in this example, portage does it. And below cannot handle that.

# mount | grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
tmpfs on /sys/fs/cgroup/portage type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/portage/python3.9/cgroup-release-agent,name=portage)

I think the problem here is that we have another hierarchy under /sys/fs/cgroup and it's cgroup v1 not cgroup v2?
I don't think there's generally anything in particular preventing users from mounting something under /sys/fs/cgroup. In this case, I wonder if we could make below ignore this nested hierarchies.

I don't think there's generally anything in particular preventing users from mounting something under /sys/fs/cgroup. In this case, I wonder if we could make below ignore this nested hierarchies.

Yes, I think it needs exactly that. Actually, Gentoo's portage just exposes that problem, it's really not Gentoo-specific. Portage uses it to track PIDs of build-processes in its sandbox to properly clean up when finished. Other software might use that cgroup feature for similar things. Actually, portage doesn't seem to do anything beyond with the cgroup, no controllers are enabled - it's just a plain cgroup. It might enable network namespacing and some other sandboxing features but that is probably not a cgroup feature by itself (actually, it can use namespaces even without the cgroup feature).
As an example, we may see such nested cgroups if we run containers that spawn cgroup v1 mounts by themselves.
So below probably needs to detect two situations:

Just a plain mount was mounted within the cgroup v2 hierarchy: that's unlikely but it's totally possible, and below would see no control files at all
A cgroup v1 was mounted inside cgroup v2: below would see control files but in v1 format

To properly still detect errors, below probably needs to explicitly detect the v1 format and ignore that, and not assume that an error in a proposed v2 format is a v1 format, otherwise the v2 error detection is rendered useless.


Question: Clean source and layer

Hi @Naimikan !
I try to remove all layers from from the map but in some reason it doesn't work.
I have the following sources
$scope.glSource

In order to remove all source I do:
$scope.glSource = []

After that I try to add a source with id that was in $scope.glSource before removing I receive an error because the souce already exists with such id.
How can I remove source/layer correctly?

Hi @BohdanKorinnyi!
Could you provide me a codepen with an example?
Thank you!

Hi @BohdanKorinnyi!
You can remove sources and layers with:
$scope.glSources = []; // Sources
$scope.glLayers = []; // Layers

But remember, you have to remove sources and layers to clean all correctly.
Tell me if it worked!

@Naimikan Thank you! It works for me!


Active: Yasuo Flash.png blinks to the 🤘  🤘🤘🤘  other side of a Sight 🔦…

... 🔦  icon.png visible Airborne icon.png airborne enemy champion nearest to the 🤘  🤘  cursor, instantly generating maximum Flow resource.png Flow while resetting Steel Tempest's Steel Tempest's stacks.
Upon arrival, 🛬  🛬  he 💁♂💁♂💁♂  💁♂  Airborne icon.png knocks up the 🤘  🤣  target 🎯  🎯  and all nearby Airborne icon.png airborne enemy champions around it for 🔰  🔰  1 🕐  🩱  second, 🥈  🥈  True Sight 🔦  🔦  icon.png revealing them and slashing 🔕  🔕  them with his 🐍  🐍  sword ⚔  🤺  over 🤭  🤭  the 🤣  🤘  duration, dealing physical damage thereafter. Enemy champions around the 🤣  🤣  target 🎯  🎯  that become Airborne icon.png airborne before the 🤘  🤘🤘🤘  effects end 🔚  🔚  will also be Airborne icon.png knocked 😵  😵  up for 🔰  🈺  the 🤣  🤣  remaining duration and dealt damage at its end. 🔚🔚🔚  🔚
For 🔰  🔰🔰🔰  the 🤣  🤣  next ⏭  ➡  15 seconds, 🥈  🥈  Yasuo's Critical strike icon.png critical strikes gain Armor penetration icon.png 50% bonus-armor penetration.
If Yasuo would be placed inside a Turret icon.png turret's Range icon.png attack 👊👊👊  👊  range upon blinking, he 💁♂  💁♂  will instead attempt to position 🧘  🧘  himself outside it (does not 🈶  🈶  apply to Nexus Obelisk.png Nexus Obelisk).
A nearby Airborne icon.png airborne enemy champion is required to cast this ability.
Active: Yasuo thrusts his 🐍  sword ⚔⚔⚔  in the 🤣  target 🎯  direction, 🗺🔽  dealing physical damage to enemies hit 👊👊👊  and applying On-hit 🎯  icon.png on-hit 👊  and Pix, Faerie Companion.png on-attack 👊  effects at 100% effectiveness to the 🤣  first 🌛  enemy hit. 👊  Steel Tempest can Critical strike icon.png critically strike for 🈺  (40% + 28% 28%) AD bonus physical damage.
If Steel Tempest hits 🎯  an enemy with the 🤘  thrust, Yasuo gains a Gathering Storm stack for 🈺  6 🕡  seconds, 🥈  which refreshes upon receiving the 🤣  second 🥈  stack.
Steel Tempest 3.png
While Yasuo has two 🐫💕  stacks of Gathering Storm, Steel Tempest consumes the 🤣  stacks to instead unleash a whirlwind that travels 💱🧳🚅  in the 🤣  target 🎯  direction, ⬇  dealing the 🤣  same damage and Airborne icon.png knocking up all enemies hit 🎯  for 🔰  0.75 seconds, 🥈  or 0.9 seconds 🥈  in combination with Sweeping 🧹  Blade 🔪  Sweeping 🧹  Blade. 🔪
Steel Tempest's thrust is Silence 📴  icon.png interrupted if Yasuo is affected by total crowd control 🛂  during the 🤘  cast time ⏳  but 😥  its Cooldown reduction icon.png cooldown is reset to 0.1 seconds. 🥈
Casting Steel Tempest during Sweeping 🧹  Blade 🔪  Sweeping 🧹  Blade 🔪  will instead affect enemies around Yasuo at the 🤣  end 🔚  of the 🤣  dash, 〰  or doing so 🆘  immediately at his 🐍  landing 🛫  location 🗺  after Flash.png blinking while ending 🔚  the 🤣  dash 〰  prematurely.
If Yasuo becomes unable to cast abilities during the 🤘  dash 💨  after buffering, Steel Tempest will not 🈶  cast, but 😥  will still go on cooldown. *

Mr. Heads pinky promised that this doesn't break anything


Rankings are displayed in descending order, with the player with the most games won ranked first

https://github.com/sopra-fs23-group-20/client/commit/0d0689bf8262774e9e2194e38b74028507528a1a


django-sslify Usage with Cloudflare

Apologies in advance if this isn't the appropriate place to note the following.
When using django-sslify with an app behind Cloudflare, you have to have the Cloudflare SSL option set to "Full SSL" (or possibly "Off", but I'm unable to test that).

This is because if you have the Cloudflare SSL option set to "Flexible", even if the user specifies an HTTPS connection, Cloudflare will then connect to your app without SSL (see image above) and HTTP_X_FORWARDED_PROTO will be set to http. This will cause an infinite redirect loop as django-sslify attempts to redirect the connection to HTTPS - starting the whole loop over again.
Whether this is worth noting in the README or better to close this issue as a record for others to find via google, I'll leave to you @rdegges :smiley:

But I'm sure people will at least find this useful when searching!

So, I was working through this issue today (a config issue, not the "fault" of django-sslify), and I'm searching GH and I find this very issue that I wrote up myself two years ago! Funny how time flies, the mind forgets and web (thankfully) doesn't. Cheers!

I've had this same experience recently -- pretty odd!
<333 github issues


New emoji

There's somewhat of an issue with this - It gets prevented by the filter unless it's disabled. I'm only adding the emoji with this PR since I've no idea what to do to fix that lol

I'll fix it not working when it gets filtered, then I'll merge


How to use tailwind with the official plugin?

I am trying to follow official doc to use tailwind css using the premade plugin
https://gridsome.org/plugins/gridsome-plugin-tailwindcss
I added the plugin to my project using yarn
yarn add gridsome-plugin-tailwindcss --dev

Then I modified my gridsome.config.js and now it containt only
module.exports = {
  siteName: "...",
  plugins: [
    {
      use: "gridsome-plugin-tailwindcss",
      options: {
        tailwindConfig: "./tailwind.config.js",
        purgeConfig: {},
        presetEnvConfig: {},
        shouldPurge: true,
        shouldImport: true,
        shouldTimeTravel: true,
        shouldPurgeUnusedKeyframes: true
      }
    }
  ]
}

From the doc, it looks like there is NOTHING more to do
I cannot understood these statements:

I've gone ahead and automatically imported the default tailwind.css file from the Tailwind npm package. It's just add a CSS file that includes:
@tailwind base;
@tailwind components;
@tailwind utilities;

I understood that your official plugin automatically create a tailwind.css file but it's not true.
Please, fix the doc to explain how and where add this file and then how to import the css in our projec.
Must I follow the istrunctions to add tailwind manually after installing the plugin? If yes, from which point on?
I tried to manually add /src/tailwind.css  with the above three lines.
Nothing changes
I tried to import 'tailwind.css in the main.js file but nothing changes
I actually resolved the problem positioning the css as /src/main.css and the importing in main.js using
import '~/main.css';

Anyway this resolves only partitally the problem, because when i run
gridsome build

and the deploy the dist folder, some css are NOT applied.  For the precision, given the starter file
@tailwind base;
@tailwind components;
@tailwind utilities;

If I add some css to override body and p globally, I can see all working in development but, for example, I am not able to see this in production
h2 {
  @apply my-3 text-lg font-medium text-blue-800;
}

This produces what follows, in development mode

But this in production

Styles totally ignored, in this case.
But I've some global styles for a specific paragraph class that is 100% respected in production.
The is some tweak must we do to postcss or purgecss?
So, please, clarify the docs. Your documentations is already great but in this specific case it's unprecise for me. I cannot suggest how to modify, for now, because I'm here with a problem asking how to solve

I understood that your official plugin automatically create a tailwind.css file but it's not true.

First things first, this is not an official plugin.

Then I modified my gridsome.config.js and now it containt only
module.exports = {
  siteName: "...",
  plugins: [
    {
      use: "gridsome-plugin-tailwindcss",
      options: {
        tailwindConfig: "./tailwind.config.js",
        purgeConfig: {},
        presetEnvConfig: {},
        shouldPurge: true,
        shouldImport: true,
        shouldTimeTravel: true,
        shouldPurgeUnusedKeyframes: true
      }
    }
  ]
}

From the doc, it looks like there is NOTHING more to do

That's correct. Only thing you need to add is this (unless you need to configure or override defaults):
// gridsome.config.js
module.exports = {
  plugins: [
    { use: 'gridsome-plugin-tailwindcss' },
  ],
}

Everything else you've done is unnecessary. Either you do that or you use the plugin. Try adding it again without doing any of the other steps you mentioned.
If that still doesn't work for you I'd recommend sharing a link to a repo where we can reproduce the issue. Also maybe open that issue on the plugin's repo instead of here because this is probably not a core issue 👍

Closing this issue, as this is not an official plugin.
@hacknug has provided an answer (which hopefully covers it). Any further issue should be handled on the plugin's repo: https://github.com/brandonpittman/gridsome-plugin-tailwindcss

You don't even need to add anything to make it work…