Create and redirect bylaws page

I created the bylaws file according to the docs linked on the footer and changed redirects
What issue is this referencing?
Fixes issue #136

Does the following command run without warnings or errors?

[x] yes! npm run pr-checks

Have you taken a look at our contributing guidelines?

[x] yes!

My node version matches the one suggested when running nvm use?

[x] yes!

Okay I changed a setting that might fix it, rebuilding now

okay so the build is being weird.
This old builds before I pointed to the right folder:

Now they at least see the redircts:

But yours isn;t listed and I am not sure why

Ok haha, now it makes more sense

Excuse me build, it is literally right there:

Checks still failing... What can it be?

The other one works and is the same thing, why it's not working??

hmmmm and on your local if you do localhost:3000/bylaws it works right?

In my localhost both does not work actually

what commands are you running? to build?

npm run build

Doesn't work, then suggests the npm run build command

or maybe npm run start or npx serve
These people seem to be having simiilar issue: https://answers.netlify.com/t/page-not-found-only-when-visiting-directly-with-the-url/94491/16

npm run start may work but it says i'm already using port 3000 but I closed everything, I will check that and see if runs normally

Ok, now it's working but not the redirects

hahaha omg @DerrykBoyd I think I need help.
I fixed it so that netlify does see the redirects and it does list them but it still thinks the page is missing, and I have googled everything I can think of. Any ideas?

hahaha omg @DerrykBoyd I think I need help.
I fixed it so that netlify does see the redirects and it does list them but it still thinks the page is missing, and I have googled everything I can think of. Any ideas?

I'm not sure why it's trying to prerender bylaws. Doesn't do that when I run generate locally. Anyhow... try adding this to the nuxt config, then hopefully it won't prerender that route and build will pass?
    // nitro settings
    nitro: {
        prerender: {
            ignore: ["/bylaws"],
        },
    },

That works!! 🥳 🥳 🥳 🎉 🎉 🎉
Thank you @DerrykBoyd
@CaioCintra add that to this pr and then you should be good!

Oh perfect! Thank you @CaioCintra for working through this!


Updated README.md with TravisCI badge

Updated README.md with TravisCI badge and a Rubygems badge
Closes #20

Can @kringelbach, @bjarkehs and @Kumuluzz take a look at this?


Add GPS coordinates of Site/Facility

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Description
It would be nice to add a field for the GPS coordinates of a site/facility.
Our use-case would be to pull all sites via the Netbox API, and display them on a map (along with circuits between sites).

I did this by adding two custom fields to the Sites model. Latitude and Longitude. They then show up on the API via the custom_fields option.

Implemented in 258373f on the develop-2.4 branch.


Jquery unobtrusive validation does not work with some inputs.

Some forms are processing incorrect with jquery unobtrusive validation.
For example:
I am developing web app (ASP.Net MVC 5, Jquery 2.2.1, Jquery Validation 1.14.0, Jquery Unobtrusive Validation 3.2.3) and i have next model class:
public class PersonalInfo     {         [Required(AllowEmptyStrings = false, ErrorMessage = "Field can not be empty")]         [StringLength(40, ErrorMessage = "First name is too long. Please enter a shorter first name.")]         public string FirstName { get; set; }.     }
How we can see there is 2 validation attribures. What will rendererd in html:

                                          <input data-val="true" data-val-length="First name is too long. Please enter a shorter first name." data-val-length-max="40" data-val-required="Field can not be empty" id="first-name" name="FirstName" type="text" value="Fred" class="input-validation-error">                     First name                     Field can not be empty

And after that magic starts =)  If I am typing into input nothing happens ultil text length less than 40 symbols. After that unobtrusive validation works well. But before that validation does not react on required attribute.

Please provide a way to reproduce it and see it in action. like a codepen or  a fiddle snippet
Closed due inactivity, feel free to reopen it if it is still necessary.


Azure Monitor: Setup test data for extended server timeout requests

This task is to explore how to set up test data for logs client that can help test extended server timeout requests.

This is resolved.


Introduce methods on QueryState to obtain a Query

Objective
Simplify and expand the API for QueryState.
QueryState has a lot of methods that mirror those on Query.  These are then multiplied by variants that take &World, &mut World, and UnsafeWorldCell.  In addition, many of them have _manual variants that take &QueryState and avoid calling update_archetypes().  Not all of the combinations exist, however, so some operations are not possible.
Solution
Introduce methods to get a Query from a QueryState.  That will reduce duplication between the types, and ensure that the full Query API is always available for QueryState.
Introduce methods on Query that consume the query to return types with the full 'w lifetime.  This avoids issues with borrowing where things like query_state.query(&world).get(entity) don't work because they borrow from the temporary Query.
Finally, implement Copy for read-only Querys.  get_inner and iter_inner currently take &self, so changing them to consume self would be a breaking change.  By making Query: Copy, they can consume a copy of self and continue to work.
The consuming methods also let us simplify the implementation of methods on Query, by doing fn foo(&self) { self.as_readonly().foo_inner() } and fn foo_mut(&mut self) { self.reborrow().foo_inner() }.  That structure makes it more difficult to accidentally extend lifetimes, since the safe as_readonly() and reborrow() methods shrink them appropriately.  The optimizer is able to see that they are both identity functions and inline them, so there should be no performance cost.
Note that this change would conflict with #15848.  If QueryState is stored as a Cow, then the consuming methods cannot be implemented, and Copy cannot be implemented.
Future Work
The next step is to mark the methods on QueryState as #[deprecated], and move the implementations into Query.
Migration Guide
Query::to_readonly has been renamed to Query::as_readonly.

I agree that there's a lot of duplication between QueryState's and Query's API and it's good that this is lessened, but just out of curiosity (just to offer a potentially dumb idea), would it perhaps be better if QueryState and Query were just one single struct instead of two?

I agree that there's a lot of duplication between QueryState's and Query's API and it's good that this is lessened, but just out of curiosity (just to offer a potentially dumb idea), would it perhaps be better if QueryState and Query were just one single struct instead of two?

I think the idea is that you need access to the world to actually do querying, but that we want to cache some state that lives longer than that borrow.  So a Query is a &QueryState for the state plus UnsafeWorldCell<'w> and Ticks from the world.
I don't see a clean way to get rid of either.  If you don't have Query then you'd need to pass a world to every method on QueryState, which is terrible ergonomics for even the simplest system.  If you don't have QueryState then you need to look up ComponentIds and match archetypes every time you run a system, which is terrible performance.

I realized I could split this into two independent PRs: One for the methods on QueryState to obtain a Query, and one for the consuming methods on Query.  The consuming methods aren't all that useful by themselves, but the methods on QueryState should be, and those shouldn't be as contentious.  Would anyone like me to split it up like that?

I say go big! Go ahead and remove the methods on QueryState! 😆
You can split it up if you think it would help, but I don't mind bigger PRs.


i18n(zh-cn): Update guides/cms/ghost.mdx

Description (required)
Update guides/cms/ghost.mdx
Upstream PR: #8518
Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
guides/cms/ghost.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add ROS C++ Style Guide CLANG format

Currently we do not apply the ROS C++ style guide as stated inthe contributing guidlines of this repository. I added a .clang-format file with the ROS C++ style guide parameters. After this I formated all source and header files according to the guide lines.

Thanks for contributing! I will take a look.


Fixed Unicode regex pattern and conversion

The Unicode regex pattern would sometimes split emojis which made them break.
The emojiToUnicode() function always returned the wrong value when converting emojis with 1 codepoint consisting of 4 characters. For example \u2708 (airplane) was converted to 9992 (invalid).

thank you for the PR, will review it ASAP

Hey,
some emojis still not working for example "☺",
could you please check the list https://getemoji.com/

I checked it out and the emoji you sent "Smiling Face" has two codepoints. U+263A and U+FE0F, but the last codepoint is just a variation selector that is no longer used for this emoji. Please use this list instead for the latest unicode emoji list: https://unicode.org/emoji/charts/full-emoji-list.html
Android natively only uses the first codepoint and I already tested all emojis on the emoji keyboard including different variations such as skin tone.

Hey, I did update the emoji regex to the same regex from your PR.
For the EmojiToUnicode method, I used Twitter implementation
Thank You :)


python310Packages.altair: 4.2.2 -> 5.0.1

Description of changes
This MR update the altair Python package to the new major version.
This MR changed to way to build the package from Pypi to Github because the Pypi package does not more include tests (200+ tests).
Full changelog here: https://github.com/altair-viz/altair/compare/v4.2.2...v5.0.1

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] Fits CONTRIBUTING.md.

Would you please rebase it again to fix the ofborg error?

Done :smile:

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

2 packages failed to build:

streamlit
streamlit.dist

4 packages built:

python310Packages.altair
python310Packages.altair.dist
python311Packages.altair
python311Packages.altair.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2372

Any update on when it could be merged ?

./results/streamlit/bin/streamlit
Traceback (most recent call last):
  File "/nix/store/wcgsxyflkp22zllhpprsc0m2zmxyb1ph-python3.11-numpy-1.24.2/lib/python3.11/site-packages/numpy/core/__init__.py", line 23, in <module>
    from . import multiarray
  File "/nix/store/wcgsxyflkp22zllhpprsc0m2zmxyb1ph-python3.11-numpy-1.24.2/lib/python3.11/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/nix/store/wcgsxyflkp22zllhpprsc0m2zmxyb1ph-python3.11-numpy-1.24.2/lib/python3.11/site-packages/numpy/core/overrides.py", line 6, in <module>
    from numpy.core._multiarray_umath import (
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/bin/.streamlit-wrapped", line 6, in <module>
    from streamlit.web.cli import main
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/__init__.py", line 55, in <module>
    from streamlit.delta_generator import DeltaGenerator as _DeltaGenerator
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/delta_generator.py", line 36, in <module>
    from streamlit import config, cursor, env_util, logger, runtime, type_util, util
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/cursor.py", line 18, in <module>
    from streamlit.runtime.scriptrunner import get_script_run_ctx
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/__init__.py", line 16, in <module>
    from streamlit.runtime.runtime import Runtime as Runtime
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/runtime.py", line 31, in <module>
    from streamlit.runtime.app_session import AppSession
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/app_session.py", line 35, in <module>
    from streamlit.runtime import caching, legacy_caching
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/caching/__init__.py", line 21, in <module>
    from streamlit.runtime.caching.cache_data_api import (
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/caching/cache_data_api.py", line 32, in <module>
    from streamlit.runtime.caching.cache_errors import CacheError, CacheKeyNotFoundError
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/runtime/caching/cache_errors.py", line 18, in <module>
    from streamlit import type_util
  File "/nix/store/b0jjxhfavfpiapjasmw8sx9mdj2507hf-streamlit-1.24.0/lib/python3.10/site-packages/streamlit/type_util.py", line 40, in <module>
    import numpy as np
  File "/nix/store/wcgsxyflkp22zllhpprsc0m2zmxyb1ph-python3.11-numpy-1.24.2/lib/python3.11/site-packages/numpy/__init__.py", line 141, in <module>
    from . import core
  File "/nix/store/wcgsxyflkp22zllhpprsc0m2zmxyb1ph-python3.11-numpy-1.24.2/lib/python3.11/site-packages/numpy/core/__init__.py", line 49, in <module>
    raise ImportError(msg)
ImportError:

IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.10 from "/nix/store/9c03r86hcdn43dm3hsgjirifvyzfkhwh-python3-3.10.12/bin/python3.10"
  * The NumPy version is: "1.24.2"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Original error was: No module named 'numpy.core._multiarray_umath'

streamlit has some errors with numpy after updating, they seem to be related becuase they don't happen on master or when reseting the commit.

I have seen the same problem before.
https://github.com/NixOS/nixpkgs/pull/231095#issuecomment-1542921767
but I'm not sure what the reason is.

I have seen the same problem before. #231095 (comment)
but I'm not sure what the reason is.

I have seen the error related to nixpkgs-review but it also occurred here for me when just using nix-build :confused:
I don't really have an idea on how we could fix that.

please change the commit adding you as a maintainer to maintainers: add vinetos otherwise this looks good.

Done

Suggestions and modifications applied, Ready to be reviewed

didn't really want to do another round but found two minor things and I can't squash merge because of the maintainer addition which should be kept extra

No problem. MR should be fine :D

I'm getting consistent failures of
FAILED tests/vegalite/v5/test_params.py::test_selection_deprecation - Deprecati
onWarning: jsonschema.RefResolver is deprecated as of v4.18.0, in

on linux-x86_64
just saying in case someone is interested.


Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: cannot connect to Docker endpoint

When I deployed on the k8s，I see Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: cannot connect to Docker endpoint

@myishuohuo - Please take the latest code and retry. I have updated the code repository for the Kubernetes 1.16. It should work now. Thanks.

@myishuohuo - Hope it has worked for you. Closing the issue because of no activity. Feel free to reopen or open a new issue if required. Thanks.

i am on deploying the network on IBM cloud kubernetes service with kubernetes v1.27.12. still facing the same error during instantiation : Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: cannot connect to Docker endpoint


Use typescript + cleanup data

Overview
Fixes #12
Dependency updates:
Closes #13
Closes #10
Closes #9
Closes #8
Closes #7
Closes #6
Closes #5
Closes #4
Closes #3
Closes #2
Description
Okay.

Recode to use typescript instead of javascript.
Use temporary files instead of keeping every file request in memory.
Delete schematic files as well
Extend prune:

Delete files in filesystem without matching record in database
Delete records from database instead of setting them to expired
Validate records have valid entry in filesystem

Preserve original file name while also using random id as file name in storage

Maybe some other changes, but those should be the not as important I guess?
Major version increased as not compatible with older versions:

Database column "expired" removed
File Structure changed

but api endpoints kept the same.
Readme changes pending
Checklist

[x] Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
[x] Ensure that the pull request title represents the desired changelog entry.
[x] I tested my changes and approved their functionality.
[ ] I ensured my changes do not break other parts of the code
[x] I read and followed the contribution guidelines

Oh, I forgot - example instance available @ https://arkitektonika.pschwang.eu/

Why is the expired db column removed? We use that to tell if a schematic once existed but has since been pruned, for user experience reasons. The HEAD request was used to check validity before sending the download request.
However, I don't know TS much so I can't really review this. And beyond that, it looks like if this is merged all of my code is essentially gone so I'm going to leave it up to @NotMyFault and the other IS members. If this merges, it's really not my project anymore and @PierreSchwang will have to take it over as SME.

Why is the expired db column removed? We use that to tell if a schematic once existed but has since been pruned, for user experience reasons.

Basically I understand the idea behind it, in the end I don't see any practical purpose in which this provides a benefit to a user. Basically, the user is only interested in: "Is my schematic there that I uploaded back then? No, good, then it was deleted. Yes, then I can continue to use it."
In that case, it would be a lot of dead data in the database, which you don't really need.

The HEAD request was used to check validity before sending the download request.
I personally couldn't see any real advantage in this either. After all, the GET or POST request says exactly the same in the end. I don't make a HEAD request if I can upload something without the intention to upload something anyway. Same for the download, and even if, you can intercept the status code without downloading the octet stream. But in favor of https://github.com/IntellectualSites/Arkitektonika-Client/blob/main/src/main/java/com/intellectualsites/arkitektonika/v1/ApiClient.java#L96 I would include the HEAD requests again.

However, I don't know TS much so I can't really review this. And beyond that, it looks like if this is merged all of my code is essentially gone

TS should simply bring standardization and type-safety to the project. The content is the same except for slight differences.

@PierreSchwang Considering you already ditched some dependencies, do you mind running a yarn upgrade if it's not too much work? Renovate has risen lots of updates, some of them even covering CVEs.

LGTM, thanks for your contribution. Though I think it would be nice to have GitHub actions tests here as well to test prs and commits as well. But that is something for a different pr/different time, as it ain't no release blocker for this one.

Thought about that as well - Maybe something is coming soon there

Why is the expired db column removed? We use that to tell if a schematic once existed but has since been pruned, for user experience reasons.

Basically I understand the idea behind it, in the end I don't see any practical purpose in which this provides a benefit to a user. Basically, the user is only interested in: "Is my schematic there that I uploaded back then? No, good, then it was deleted. Yes, then I can continue to use it." In that case, it would be a lot of dead data in the database, which you don't really need.

The HEAD request was used to check validity before sending the download request.

I personally couldn't see any real advantage in this either. After all, the GET or POST request says exactly the same in the end. I don't make a HEAD request if I can upload something without the intention to upload something anyway. Same for the download, and even if, you can intercept the status code without downloading the octet stream. But in favor of https://github.com/IntellectualSites/Arkitektonika-Client/blob/main/src/main/java/com/intellectualsites/arkitektonika/v1/ApiClient.java#L96 I would include the HEAD requests again.

However, I don't know TS much so I can't really review this. And beyond that, it looks like if this is merged all of my code is essentially gone

TS should simply bring standardization and type-safety to the project. The content is the same except for slight differences.

It's fine if you want to remove the expire column or HEAD requests. Just be aware that the Java API will need to be updated and released first, so the PR is blocked until then. The Java API used the HEAD requests to know if a schematic once existed but had since been deleted (file gone from disk, but DB marked as expired.) This was an original requirement from City, and that is why it was there. If those requirements have changed, I really don't care then. Just make sure the Java API matches what Arkitektonika provides.
As for TS, I don't have time to learn it and therefore I will not be learning it so that I can remain responsible for Arkitektonika when this merges. Since this is a major change to a dialect that I do not have a strong footing with, when this merges I will no longer be responsible for the project. That will fall to you, since you are making the changes.
If you're not okay with that, then the PR should probably remain blocked until a suitable replacement is found. I am far too busy to uproot my other obligations just to learn TS for this, even if the differences are minimal as you say. I see many things in the diff that I do not currently understand.

It's fine if you want to remove the expire column or HEAD requests. Just be aware that the Java API will need to be updated and released first, so the PR is blocked until then. The Java API used the HEAD requests to know if a schematic once existed but had since been deleted (file gone from disk, but DB marked as expired.) This was an original requirement from City, and that is why it was there. If those requirements have changed, I really don't care then. Just make sure the Java API matches what Arkitektonika provides.

That is a valid concern. I'm not sure where or when we use the API to determine whether a schematic has been deleted or not, maybe we can keep it up if it's actually useful or remove it if we never utilized it in the first place.

The only known utilization iirc was the enum in the arkitektonika client itself. I've never seen a use case where especially expired was checked.

Then we may can remove it, if we don't actually need it.

Then we may can remove it, if we don't actually need it.

https://github.com/IntellectualSites/Arkitektonika-Client/blob/main/src/main/java/com/intellectualsites/arkitektonika/ResourceStatus.java#L37 should be marked as deprecated then - when and if this PR is merged

That probably needs to be removed, if its frontend is no longer aware of it.

https://github.com/IntellectualSites/Arkitektonika-Client/blob/main/src/main/java/com/intellectualsites/arkitektonika/v1/ApiClient.java#L96
Head request usage and checking existence (410 response)
https://github.com/IntellectualSites/SchematicWeb/blob/master/mixin/schematic-workflow-mixin.js#L31
SchematicWeb checks the head response before continuing:

https://github.com/IntellectualSites/SchematicWeb/blob/master/components/download/DownloadInterface.vue#L19
https://github.com/IntellectualSites/SchematicWeb/blob/master/components/delete/DeleteInterface.vue#L19

As it currently stands this will break the Java API and SchematicWeb. I cannot speak to the Java API but SchematicWeb uses the head requests to provide a better user experience. Letting the user know that it knows about the key they provided but that the file was deleted is a better user experience than it telling the user that it has no idea what that key is. It removes a source of confusion, namely that the user can be assured they have a valid key and that the file is simply gone. That was the original intention.
If this is seen as bloat and no longer necessary, it's fine by me. But these will need to be resolved first. I do not currently have time to make these changes in SchematicWeb because I am busy with school. Someone else can submit the PR to process these removals and update the frontend's workflow to handle the deleted HEAD requests. I should be able to review.
There is certainly more utilization than seems to be understood, so there should be more research before blindly removing things.

Letting the user know that it knows about the key they provided but that the file was deleted is a better user experience than it telling the user that it has no idea what that key is. It removes a source of confusion, namely that the user can be assured they have a valid key and that the file is simply gone. That was the original intention.

Good to know, I wasn't aware of that aspect. In my opinion, we should probably keep it for a better UX, considering it was indeed already used before, if that would be possible @PierreSchwang ?

Letting the user know that it knows about the key they provided but that the file was deleted is a better user experience than it telling the user that it has no idea what that key is. It removes a source of confusion, namely that the user can be assured they have a valid key and that the file is simply gone. That was the original intention.

Good to know, I wasn't aware of that aspect. In my opinion, we should probably keep it for a better UX, considering it was indeed already used before, if that would be possible @PierreSchwang ?

Yup, that's a good reason indeed - Gonna re-add that again

Yup, that's a good reason indeed - Gonna re-add that again

After that, I guess we are good to pull this PR. The concerns have been outlined and addressed, no need to keep it on hold longer.

@PierreSchwang is this PR ready for merge?

@PierreSchwang is this PR ready for merge?

Should be, yup  - I haven't thought about migrating existing schematics - that's most likely not possible - is that bad?

What do you mean by migrating existing schematics?

What do you mean by migrating existing schematics?

When updating Arkitektonika to this changes, the old structure is most likely not compatible anymore, as many things changed. therefor uploaded schematics are most likely unusable.

Oic, this likely affects all instances (assuming people run standalone instances) then? But our instance does serve schematics for 30 days, after that they expire anyway.

@PierreSchwang looks like there are needed dependencies neither the docker image nor plain npm installs.

docker build should be called. npm install requires python3 for node-gyp

If nobody else from @IntellectualSites/admins wants to take a further look, I would go ahead to merge the PR and deploy it to our org dockerhub, to go live with it.

I wanted to implement some kind of migration for old data - I've no idea yet when I got the time for that tho

When using this branch to upload a ~501x501 schematic that goes from y=2 to y=314, I still receive a 400 error

When using this branch to upload a ~501x501 schematic that goes from y=2 to y=314 (aka a shit ton of blocks), I still receive a 400 error

@Trichtern A bit late, but could you send me the schematic file for testing purposes? If the schematic should not be shared publicy, feel free to send via Discord (Pierre#9657) - Thanks!

I think it was this schematic
plot.schem.zip

Pierre die a great job on the rewrite. We just confirmed it works with PlotSquared without further modifications of the Java implementation.
If a @IntellectualSites/core-team member would like to review the PR, please go ahead or request yourself as reviewer.
Otherwise I'd say we pull the PR in anytime soon once Pierre is happy with it.


SAMZA-1593: Upgrade gradle nexus plugin.

Current nexus plugin which samza repository is using is not compatible with the gradle versions greater than 3.0.
For doing the ligradle migration at linkedin, we need to update the nexus gradle plugin to the latest version.

@xinyuiscool Please take a look.


Bug: Policy Fragments are not export for single API when referenced

Report
The Policy Fragment Extractor needs to do something similar to the NamedValued Pairs and check the policy xml in the first option as the current PolicyContent check doesn't contain the XML
var isReferencedInPolicy = DoesPolicyReferenceFragment(apiTemplatePolicies, policyFragmentReferenceString,
policyFragment,
baseFilesGenerationDirectory);
var isReferencedInPolicy = apiTemplatePolicies?.Any(x => x.Properties.PolicyContent.Contains(policyFragmentReferenceString));
Expected Behavior
Single API
Export the policy fragment based on fragment id being present in an API policy
Actual Behavior
Single API
Export the policy fragment based on fragment id being ignored for a single API
Steps to Reproduce the Problem
n/a
Component
Extractor
DevOps Resource Kit Version
V0.7
.NET Version
6.0.107
OS
Windows
Configuration
{
"sourceApimName": "apim-name",
"destinationApimName": "?",
"resourceGroup": "apim-rg",
"fileFolder": "demo-openapi-v10",
"apiName": "demo-openapi-v10",
"linkedTemplatesBaseUrl": "?",
"linkedTemplatesSasToken": "?",
"policyXMLBaseUrl": "?",
"policyXMLSasToken": "?",
"includeAllRevisions": "false",
"paramServiceUrl": "true",
"paramNamedValue": "true",
"paramApiLoggerId": "true",
"paramLogResourceId": "true",
"paramBackend": "true",
"paramNamedValuesKeyVaultSecrets": "true"
}
API Management Configuration
SKU: Developer
full admin right : yes
VNET: Yes
Logs
No response
Anything else?
No response
Contact Details
<EMAIL_ADDRESS>

Hello @UniperMaster thank you for raising the issue.
The PR #799 addressing the issue is now merged into the main branch and will be available in future releases.
Please feel free to reopen this issue or create new one in case you will face same behaviour with policy fragments using latest changes.
Best regards.


🥅 Add 404 error page

🤖 Generated by Copilot at 56a234b
Summary
🌐🎨🚀

Refactored the custom 404 page to use a new UI library and support internationalization. Added a new translation namespace for the page and improved the image style. Modified src/pages/404.tsx and src/tools/server/translation-namespaces.ts.

Oh we're the coders of the sea, and we work with harmony
We refactor and translate, to make our pages look great
Heave away, me hearties, heave away
For we've added pageNotFoundNamespaces today

Walkthrough

Update custom 404 page to use mantine UI library, next-i18next library, and next/image component (link, link)
Add translation namespace for the custom 404 page to the translation-namespaces.ts file (link)

I don't think this PR improves anything ? Sorry but it seems really pointless, it's just a generic and not related to homarr. Maybe you could add some more info like, "take me back to safety" or something like that

We want to make the error page more generic, because the current one shows config not found and homarr does long not consist anymore out of only configs. So in our view it would make sense to make a more generic 404 page.

I don't think this PR improves anything ? Sorry but it seems really pointless, it's just a generic and not related to homarr. Maybe you could add some more info like, "take me back to safety" or something like that

The point is, that it should only improve user accessibility. Right now, any route will return "config" not found. We should return a more generic error, because the statement on this page is not true.

I don't think this PR improves anything ? Sorry but it seems really pointless, it's just a generic and not related to homarr. Maybe you could add some more info like, "take me back to safety" or something like that

The point is, that it should only improve user accessibility. Right now, any route will return "config" not found. We should return a more generic error, because the statement on this page is not true.
I can rename the button though if you want.

Then I think you can add more logic to read the current url and return an appropriate error in regards to it, like “dashboard [id] not found” in /[id] or anything else in another page

I don't think this PR improves anything ? Sorry but it seems really pointless, it's just a generic and not related to homarr. Maybe you could add some more info like, "take me back to safety" or something like that

The point is, that it should only improve user accessibility. Right now, any route will return "config" not found. We should return a more generic error, because the statement on this page is not true.
I can rename the button though if you want.

Then I think you can add more logic to read the current url and return an appropriate error in regards to it, like “dashboard [id] not found” in /[id] or anything else in another page

I think we should do that, once we are finished with the authentication branch.
Once this PR is merged, I will add the header and navigation bar to it - but that is located on the authentication branch only.
Therefore, I need this first in dev, before it can be improved.
But if you want more information on it (route, ...), then we can surely add that.
Regarding the more specific errors, I would implement that later, because our current routing on latest and dev is janky.
The slug page forces us, to not be sure what the actual error is or what kind of page is missing.

Then we can merge this PR after the changes are on dev, it would make sense rather than make 2 different PRs wouldn’t it ?

Sure, I'm fine with that

https://nextjs.org/docs/pages/building-your-application/routing/custom-error#404-page
okok so the page has to be static, we can't really have context here. So I think it's fine 👍🏼


Unable to run the project

How do I run this project in eclipse? Readme says cloudsim jar is added but its not present in the master branch please help

I googled it and downloaded the cloudsim jar and add the external jar to the build path. The example9 is running fine so I am marking this issue close


Deal with merge conflict and add in new types

Merges with upstream
Deals with conflict
Adds in type data for new methods
Fixes flake8 issues

Ha. H4CKY54CK -1 | GitHub - more than 1
Thanks, I didn't realize you had done this.


PoC arbitrary dispatch

@NicolasHug @vfdev-5 following our offline discussion. This is just a PoC for F.equalize / transforms.RandomEqualize. I have to clean up a little, but the general structure is there.

Most of our transforms don't touch _transformed_types at all. Here is a list of the ones that do

Dispatcher does not support arbitrary dispatch and would error for unsupported datapoints. Thus, the transform has to filter them out

RandomErasing
FiveCrop
TenCrop
UniformTemporalSubsample
Normalize
RandomPhotometricDistort (This is only partially the right category. The transform uses many dispatchers, but also defines a "dispatcher" itself that doesn't support arbitrary dispatch. If pytorch/vision#7624 goes through, this transform needs to go into the "performance" category below)

The dispatcher supports arbitrary dispatch, but the transform filters for performance reasons (not sure the second half is true, but I can't think of anything else)

Grayscale
RandomGrayscale

Transform has no corresponding dispatcher and thus has to filter itself. We should look into why this is the case. Maybe it has a good reason, but maybe it is just an oversight?

LinearTransformation

Transform only applies to a single type by design. The corresponding dispatcher has no kernels registered

ConvertBoundingBoxFormat
ClampBoundingBox

Transform converts the actual type and thus applies only to a few specific types by design. The corresponding dispatcher has no kernels registered

ToTensor
PILToTensor
ToImageTensor
ToImagePIL

Transform supports tensor images, but no PIL images:

ConvertImageDtype
ToDtype
LinearTransformation (we could implement support here similar to what we do with GaussianBlur: convert to tensor, apply the tensor kernel, and convert back)
Normalize

Apart from these groups, there is also Lambda. It takes the supported types as parameter. Nothing would change with the design in the PR, since it already circumvents _transformed_types.


Add inert

Adding wicg-inert to dependencies and refactoring inertElements to use the new inert polyfill.

Closes #15.


Allow Steem Keychain to be triggered by a click on a Steem Connect link from any Steem dapp

SteemConnect links are widely used on the blockchain for a while now, all parameters in those links can be easily parsed and converted into a parameter for Steem Keychain.
Either Steem Keychain or Steem Plus could inject piece of JS when the current browser tab is on steemit.com or any other Steem condenser. That JS snippet would then check all anchors on the page and if it finds a steemconnect.com API URL, it would then parse and extract the parameters and convert it into a call to one of the Steem Keychain functions.
If Steem Keychain is not installed then render a modal dialog that describes what is the current action was supposed to be (transfer, upvote etc...) and give the user two options:

Install Steem Keychain extension in order to perform that action in a more secure manner
Let them continue to the original Steem Connect link (playing it fair 😊)

Odd issues on github made me think my previous ticket wasn’t created


Documentation for fold options

Description of issue
From this issue:
https://github.com/vim-perl/vim-perl/issues/251
I found fold options that I didn't know existed, and I can't seem to find them anywhere in the README. Would it be possible to add some documentation around what's possible? Is there any other documentation for other features that may be missing?

@srchulo Can you say more please about what options you found that weren't documented?  What can we put in the README that would help future users like yourself?


idea/wishlist: callout fun sound and sprite editor(s)

we talked about doing this on Hype page

For issues we aren't immediately going to address let's take note of them in this doc. I want to test out keeping the filed issues high priority/things we are currently working on. We can reopen these if/when we return to them in the future.


SFDX Plugin Install can't find the Package in the Private NPM (We are using Nexus)

When running sfdx plugins:install hpe-sfdx-plugins, I receive the following message

If I use the public NPM registry everything works fine. Due to compliance issues I had to migrate my package to a private registry and now I can't install the plugin.
The only thing I changed in the Plugin's package.json was this

Im also able to install the package using npm install hpe-sfdx-plugins without a problem.
In the image below I show my global registry (the private one), and after that I install with success the hpe-sfdx-plugins package and then I try to install using sfdx plugins:install hpe-sfdx-plugins and it does not work.

I opened another one for the sfdx-core repo https://github.com/forcedotcom/sfdx-core/issues/233

Duplicate of https://github.com/forcedotcom/cli/issues/410


How to Sign-Out?

Once signed-in, how can you sign-out or sign-in as a different user?

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

ID: 4d685967-b6a6-41d9-4bec-18c080bcd1b7
Version Independent ID: a390f63b-491e-37cd-5b6b-d3c1e7756aba
Content: Join quickstart - Visual Studio Live Share
Content Source: docs/quickstart/join.md
Product: visual-studio-family
Technology: live-share
GitHub Login: @Chuxel
Microsoft Alias: clantz

Hello,
You can sign out in VSCode via the accounts button in the bottom left of the UI.

I appreciate the answer, but I hope it will also be updated in the documentation as it does not appear anywhere that I can find in the liveshare docs.

Closing as resolved, since we re-did the VS Code docs. Thanks!


iOS: Argument 1 Window.getComputedStyle must be an instance of Element

I'm seeing a weird bug on iOS (chrome and safari) if I use the datetimepicker successfully and then begin to scroll around the page (using touch and drag) that if a different input bound to the datetimepicker comes into view I get the following error:
TypeError: Argument 1 ('element') to Window.getComputedStyle must be an instance of Element

It doesn't appear to actually cause any issues with my workflow, but it is triggering an error in the console which is filling up our Sentry error logging.

related to #540


Latte & Used locations support?

Could you please add support for Latte template system? Its similar to html or twig).
My config  "html-css-class-completion.includeGlobPattern": "**/*.{css,scss,sass,latte,html}", but not working :(

This is the first time I heard of Latte. I will try to implement basic support as soon as possible.
I've looked over few samples and its indeed like html/twig. It shouldn't be hard to implement.
I'm on it on this weekend.

Its a primary template system for NETTE framework (https://latte.nette.org/en/) which wins 3 best PHP framework in the world for year 2015.
Really nothing hard, it has same structure like a HTML langguage with own macros (https://latte.nette.org/en/macros).
Thx for good job & thx for fast reply.

For future, is there real chance to do autocompletion for SCSS? (autosuggestioning vars, functions, mixins etc?)
Your plugin is solving what Im still missing   in VSC (II've already reported it several times, without change/chance).

Currently SCSS autocompletes classes from CSS, SCSS, HTML and Slim files.
For vars, functions and mixins. Yes, This is possible and In fact I also need them too! But I will first add latte support.

Great news! I'll look forward to it.
What is still basically missing in vsc is suggesting between 2 environments.
HTML -> CSS (SCSS, LESS ...)
and vice versa
CSS (SCSS, LESS ...) -> HTML
this probably works (plugin to provide it).
main.scss { .test {color: red; } } // when im here, i will see .test2 selector from other css/scss file
rest.scss {.test2 {color: blue;} } / and vice versa
some-file.html  ( plugin to provide it)
still we will see
.test or test2
BUT
in  scss & css file i never see  classes or identifikators from (html / latte ...)
Thx for reply and Im looking forward for latte extension :-)

would it be possible?

Yes. It is possible. I will be working on it at this weekend. (Tomorrow and other day) If nothing goes wrong.

This feature has been added to master branch. I will provide an early beta extension for tests. Keep your eyes on here.

Extension released. Please update your vscode extensions.

Hi, thx for latte support! Works great.
Suggesting between html(latte) and css (scss) works fairly well, it show but only classes (but no identificators "#"), could you add it?
Is possible via some settings turn on extended info about occurences what i´m looking for and what did  plugin find? Like here?  https://marketplace.visualstudio.com/items?itemName=solnurkarim.html-to-css-autocompletion It's better for an idea of what a class or identifier is, it will be very helfpul.
Thx for answer :-)

Yes, I can add id attributes. But let me ask this. When I look your link, I see that css autocompletion shows HTML files locations, where they are located at.
Do you want them? Or you want:
html:

scss/css:
#here-is... # autocomplete here.

Oh, I see, even i've added this feature already something is keeping this feature stopped. I will look into this now.

Do you want them? Or you want:
But its the same or not?

Yes, this is exactly what i  want. (screen when i used previous plugin)

And in html / latte (when I searching class or id from some CSS or SCSS file) - it would be nice to show file where  it was found.

MIXED SCENARIO

When i create new id or class in HTML / LATTE and go to CSS / SCSS ur plugin will find it - COOL, but  how do I know if this is a class from CSS or HTML?
When we solved these things , plugin will be best on the MARKET and i will propage on Twitter and to our firm / colleagues :-)

Well, I was thinking this last week. I was thinking like Go To Definition feature. Sometimes, I also get lost due to this.
I will do my best to bring this to our extension.
I also think one more thing. I would like to separate id and class icons in autocomplete lists.

I also think one more thing. I would like to separate id and class icons in autocomplete lists.
Via some icon or with 2 separated lists?

When you  parse files you probably know file / line where  where the occurrence is located (when this information add to popup window which is shown after suggestion it will be timeless! :-)

I've implemented basic support for this. As you can see ID and Class has different icons. I will also separate them. When you press dot, you only see classes, when typing hash, you will see IDs.

This is how will it look like. A basic proposal.

Good idea.
it could look like this:

When i write some className or identifikator i will see everything in one list (it will be different by icon or some muted postfix/prefix (class) this-is-class or (id) this-is-id.
When i  specify selection with "." or "#" i get classname or id

And will you work previous point (extended info where class or id is located -> file/line or something like that).
Have a nice rest of the weekend

We're getting there...

Looks fantastic!

@Kcko, have you tried what I say on other issue? Still same?

Better naming:

@Kcko, have you tried what I say on other issue? Still same?

Yes, you have an answer, look on video and my description, thx.

@Kcko please try this for "usages"
v1.5.1-beta: https://github.com/gencer/HTML-Slim-CSS-SCSS-Class-Completion/releases/tag/v1.5.1-beta
Note: This is still BETA. Need lot of work but it should give you the idea.
Note 2: Find usages only works in css/scss. So, in css/scss you should see your latte files.

There is a bug. When you create a new class in latte, usages are not listed. I've already fixed and will be available in next build.

Here is the fixed one: https://github.com/gencer/HTML-Slim-CSS-SCSS-Class-Completion/releases/tag/v1.5.2-beta

I will try tomorrow, VSC offers 1.3.x version (http://bit.ly/2UTiXVX)

I did not publish, VSIX file is here: https://github.com/gencer/HTML-Slim-CSS-SCSS-Class-Completion/releases/tag/v1.5.2-beta
I will publish after some additional work.

Latte and find usages are released in marketplace with version of 1.5.3.


Add git version requirement to README

Pull Request Test Coverage Report for Build 307

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.845%

Totals

Change from base Build 304:
0.0%

Covered Lines:
184

Relevant Lines:
194

💛  - Coveralls

Looks good. May I suggest slightly expanding the scope of this PR? We can cleanup the README file in general:

Things like the frontend dependencies can be removed
Also, will the URL for swagger be at /v1/swagger or just /swagger?
And the git version can be included as well in the PR

Sounds good. Will do the necessary changes

All done. @remo5000 @ningyuansg


Add python-swiftlm to trackupstream

A new python-swiftlm package version was published to pypi instead.


pull request for e2e test at 01/04/2017 00:15:14

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


any chromium browser after switching to wayland through ozone takes around 2 to 3 minutes to open

happening on nvidia tried on 2 laptops same result every time any fixes happenes with chrome brave vivaldi ungoogled chromium but dossnt happen on firefox thus i can say only happens on chromium based browsers and only happens after switching to wayland using ozone

misbehaving xdg-desktop-portal most likely. Not a hyprland issue.

misbehaving xdg-desktop-portal most likely. Not a hyprland issue.

tried reinstalling not working flatpak works fine thanks for your time

I just noticed this , If it wasn't for your comment I wouldn't have even figured out that it was actually opening at all after 1 min.
Maybe looking at brave's open issues and see if something similar happens outside of hyprland
I get this on:

hyprland-git 0.41.2.r41.bd526822-1
brave-nightly-bin 1.69.111-1
Linux arch 6.9.9-arch1-1

brave-browser-nightly --enable-features=UseOzonePlatform -ozone-platform=wayland
[40758:40758:0717/105521.352387:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.
[40758:40778:0717/105522.240051:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[40758:40758:0717/105551.437317:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[40758:40758:0717/105621.690315:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512

# 1 minute later ..
# it opens

Even on mouse move in the restored page DOM produces numerous logs like this one ad infinitum:

[41608:41636:0717/105729.028663:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mail
[41608:41636:0717/105729.028728:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[41608:41636:0717/105729.028792:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[41608:41636:

probably not a hyprland issue , just going to leave it here for reference

https://github.com/user-attachments/assets/01acab24-96b6-4225-a301-34086ebdade9


Apple App Store Warning

I received this warning when I recently submitted an app that uses ClusterPrePermissions from the app store:

This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.

I'm not using the Calendar permissions at all, I'm only using microphone permissions.

It seems like the Apple app store code analysis is seeing the use of EKEventStore within the ClusterPrePermissions library and rejecting the app unless I include the NSCalendarsUsageDescription in the Info.plist.

Hey there,
Yeah, this has been on my mind for a while, ever size Apple announce that people will need usage descriptions filled out in their apps.
The easiest thing to do for now would be to go ahead and add the usage descriptions for:
NSCalendarsUsageDescription
NSPhotoLibraryUsageDescription
NSCameraUsageDescription
NSMicrophoneUsageDescription
NSCalendarsUsageDescription
NSLocationWhenInUseUsageDescription
NSLocationAlwaysUsageDescription

In your app's Info.plist.
The real fix would be to either:

Add #ifdef statements all over the place, or
Switch each permission into a separate CocoaPod subspec, or
Rewrite this library in a way to genericize some the repeated flows.

The problem with (1) is that it makes the code ugly, and adding new permissions will continue to be  hard/unmaintainable. The problem with (2) is the extra cognitive load of managing the pods.
Solution (3) is the ideal one, I think. Especially given that the library is still using UIAlertViews and all. A Swift-based solution might help tremendously, with typed enums and enums with associated values.


A descriptive name for my changes

hind encorp resubmited

I have noticed that the master branch of your fork has diverged from the one of the repo. This is probably what causes the mess in the github diff "Files changed".
I would suggest to re-fork the datasets repo and recreate a new branch and a new PR.

You're pretty close to having all things ready to merge !
Feel free to ping me when you have a new PR

Closing this one in favor of #1575


Installing serverless-python-requirements issues

Im trying to install serverless-python-requirements,however, im getting the following error message :
ERROR: Could not find a version that matches serverless-python-requirements
No versions found
Was https://pypi.org/simple reachable?
ive attempted to clear the cache, uninstalling\reinstalling pipenv etc.. but nothing seems to work.  i can install other packages ok ( serverless framework, numpy etc.. ).  here is the pipenv --support details :
$ pipenv --support
Pipenv version: '2018.11.26'
Pipenv location: 'C:\\Users\\TTYY\\AppData\\Roaming\\Python\\Python37\\site-packages\\pipenv'
Python location: 'c:\\program files (x86)\\python\\python.exe'
Python installations found:

3.7.4: C:\Users\TTYY\git\.virtualenvs\test1-BtSuf0k4\Scripts\python.exe
3.7.4: C:\Users\TTYY\git\.virtualenvs\test1-BtSuf0k4\Scripts\pythonw.exe
3.7.4: C:\Program Files (x86)\Python\python.exe
3.7.4: C:\Program Files (x86)\Python\pythonw.exe

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.7.4',
 'os_name': 'nt',
 'platform_machine': 'AMD64',
 'platform_python_implementation': 'CPython',
 'platform_release': '10',
 'platform_system': 'Windows',
 'platform_version': '10.0.17763',
 'python_full_version': '3.7.4',
 'python_version': '3.7',
 'sys_platform': 'win32'}

System environment variables:

ALLUSERSPROFILE
APPDATA
COLORTERM
COMMONPROGRAMFILES
COMPUTERNAME
COMSPEC
COMMONPROGRAMFILES(X86)
COMMONPROGRAMW6432
DRIVERDATA
EXEPATH
FPS_BROWSER_APP_PROFILE_STRING
FPS_BROWSER_USER_PROFILE_STRING
HOME
HOMEDRIVE
HOMEPATH
HOMESHARE
LANG
LOCALAPPDATA
LOGONSERVER
MSYSTEM
NUMBER_OF_PROCESSORS
OS
ONEDRIVE
ONEDRIVECONSUMER
ONLINESERVICES
PATH
PATHEXT
PIPENV_ACTIVE
PIP_DISABLE_PIP_VERSION_CHECK
PIP_PYTHON_PATH
PLINK_PROTOCOL
PROCESSOR_ARCHITECTURE
PROCESSOR_ARCHITEW6432
PROCESSOR_IDENTIFIER
PROCESSOR_LEVEL
PROCESSOR_REVISION
PROGRAMFILES
PROMPT
PS1
PSMODULEPATH
PTSMINSTALLPATH
PTSMINSTALLPATH_X86
PUBLIC
PWD
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED
PROGRAMDATA
PROGRAMFILES(X86)
PROGRAMW6432
REGIONCODE
SESSIONNAME
SHLVL
SYSTEMDRIVE
SYSTEMROOT
TEMP
TERM
TERM_PROGRAM
TERM_PROGRAM_VERSION
TMP
UATDATA
USERDNSDOMAIN
USERDOMAIN
USERDOMAIN_ROAMINGPROFILE
USERNAME
USERPROFILE
VIRTUAL_ENV
VS140COMNTOOLS
WINDIR
_
PLATFORMCODE
PIP_SHIMS_BASE_MODULE

Pipenv�specific environment variables:

PIPENV_ACTIVE: 1

Debug�specific environment variables:

PATH: C:\Users\TTYY\git\.virtualenvs\test1-BtSuf0k4\Scripts;C:\Users\TTYY\AppData\Local\Programs\Git\mingw64\bin;C:\Users\TTYY\AppData\Local\Programs\Git\usr\bin;C:\Users\TTYY\git\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Python\Scripts;C:\Program Files (x86)\Python;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0;C:\windows\System32\OpenSSH;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\windows\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\nodejs;C:\Program Files\Amazon\AWSCLI\bin;C:\Program Files\Amazon\AWSSAMCLI\bin;C:\Users\TTYY\AppData\Local\Microsoft\WindowsApps;C:\Users\TTYY\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\TTYY\AppData\Roaming\Python\Python37\Scripts;C:\Users\TTYY\AppData\Roaming\npm;C:\Users\TTYY\AppData\Local\Programs\Git\cmd;C:\Program Files\Amazon\AWSSAMCLI\bin\sam.cmd
LANG: en_GB.UTF-8
PWD: C:/Users/TTYY/Documents/Visual Studio Code/test1
VIRTUAL_ENV: C:\Users\TTYY\git\.virtualenvs\test1-BtSuf0k4

Contents of Pipfile ('C:\Users\TTYY\Documents\Visual Studio Code\test1\Pipfile'):
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
serverless-python-requirements = "*"

[requires]
python_version = "3.7"

It is not a valid package on pypi.org so you can't installed it by pip or pipenv.
If you are meaning https://github.com/UnitedIncome/serverless-python-requirements, it seems like a plugin of Serverless developed with Javascript.

Hi frostming
thanks for your prompt reply.
if its not a valid package, why does it seem to install when using pip ?  its just that when I use pipenv, the problem exists

@pb321 No
pip3 install serverless-python-requirements
Looking in indexes: https://pypi.org/simple
Collecting serverless-python-requirements
  ERROR: Could not find a version that satisfies the requirement serverless-python-requirements (from versions: none)
ERROR: No matching distribution found for serverless-python-requirements

How did you succeed with it?

Apologies.  yes, it looks like pip also doesnt install serverless-python-requirements.  so, the only way i can install is via the serverless framework...
thanks for your time, its very much appreciated


Mocking resources in the dbt manifest?

I've just come across this package yesterday and it looks like it will be incredibly useful. I'm particularly interested in being able to run sql against my dbt project through the python interface. I have a question...
Once we've loaded the project into memory like so
runner = DbtProject(
    project_dir=...,
    target="prod",
)

how easy do you think it would be to mock/patch models in the runner prior to running individual sql queries against it?
If this feature was available, combined with the provided ability to run sql against a pre-compiled version of the manifest,  it would be quite straightforward to extend this package to support unit testing your dbt models.
I'm quite keen to take a look at how to do this myself to be honest as it's something I've mulling over how to do for a long time now! I'm just keen to hear if this sounds doable before I dig in.

@louis-vines
It would be pretty trivial. You can loop through models, lookup models (like a ref(...) call does), etc. and each model will have an attribute called raw_code in dbt-core >= 1.3 or raw_sql in < 1.3 (I have a constant which does the version tuple check so we can access the right attribute via getattr)
You can manipulate this as needed then run the model, run the SQL, etc.
You can also dynamically patch in macros or override macros from Python which is also interesting in the case you wanted to replace a source or ref macro with something more complex without relying on the user having an override in their project. In this case consider the possibility of using a CTAS to extract a subset of data from a models immediate parents to essentially "pin" the input. You can then run the transformation and "pin" an output deemed correct by the user. Future unit tests can use these pinned states of data stored in some dataset/schema in the data warehouse. Thats how I envision it at least.

What I am describing is very high-level but if you want to dig into the low-level stuff I am pointing at lmk otherwise have at it!
The ref/source like functions BTW are get_ref_node and get_source_node
Alternatively project = DbtProject(...); for node in project.dbt.nodes:

Nice - I'm going to take a look over the next couple of weeks when I've got some free time...

@louis-vines
My suggestion forward is to use https://github.com/z3z1ma/dbt-core-interface as a single file dep you can copy paste into your project and import to have no additional dependency with the benefits of the interface + server.
It will also make its way to pypi eventually.


Using : as separator

I check the source code and find that the dynamic plugin support using : as separator.
https://github.com/egoist/tailwindcss-icons/blob/main/src/dynamic.ts#L23
const nameParts = icon.split(/--|\:/)

But when I write a class like i-[mdi:home] or hover:i-[mdi:home], the plugin does not generate the css code. And I change the class to i-[mdi--home] and hover:i-[mdi--home], the plugin works fine.

Sorry, you cannot use : as delimiter, because i-[mdi:home] is not a valid selector.
You can try it at https://www.cssportal.com/css-validator


fix: Publish time conversion to timestamp for GRPC

The serialiser is unaware of type conversion when using the GRPC connection, causing exceptions to be thrown.
This fixes the data conversion process.

After a second look, I believe this property was never meant to be set by clients during the production of messages.
The API of the message object lead us to make wrong assumptions on its usage.
Maybe it would be good to put guards on the properties used for message production. Then again, it's a totally different story.
I’ll close this for now as it doesn't make sense.


Is the email really generated? when a lead is created

I have worked with many ISVs and I think the emails are not being sent out. Can we check this please?

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

ID: c1a60d4c-0a7a-4deb-9687-047e3041acfe
Version Independent ID: 2e2137fa-b152-1220-8855-23e33fcfb966
Content: Lead management from Microsoft commercial marketplace
Content Source: articles/marketplace/partner-center-portal/commercial-marketplace-get-customer-leads.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @qianw211
Microsoft Alias: dsindona

Thanks for the raising this.
@qianw211  - what is the  escalation/support guidance for this issue?

adding @dsindona for input on how to escalate this ?
@santhoshbomma9  - as this channel is reserved for questions & issues with documentation, we will have to redirect to the appropriate support channel for partner center portal.
A quick scan of the scan of the content yielded these  support options. Also shown in screen-capture below.

We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Quadt#3749

resolving#3749

Hey, @Swastik-Swarup-Dash
Thanks for the PR!
Could you update the PR title according to https://www.conventionalcommits.org/en/v1.0.0-beta.2/#summary ?
As soon as you do that we can approve it

hey @ogabrielluiz I have updated the PR Tilte


python: grpcio: 1.9.0 -> 1.12.0

Updates grpcio to the latest version.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @FRidh

@GrahamcOfBorg  build python27Packages.grpcio python36Packages.grpcio

Failure on x86_64-darwin (full log)
Attempted: python27Packages.grpcio, python36Packages.grpcio
Partial log (click to expand)
  File "/nix/store/30my13v47snx921qsfaxrlbmqn7hcakr-python3.6-bootstrapped-pip-10.0.1/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 78, in run
    _build_ext.run(self)
  File "/nix/store/vidjaj14dsiglsvghxrab1y74kad8d3l-python3-3.6.5/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/private/tmp/nix-build-python3.6-grpcio-1.12.0.drv-0/grpcio-1.12.0/src/python/grpcio/commands.py", line 278, in build_extensions
    raise Exception("make command failed!")
Exception: make command failed!
builder for '/nix/store/nirlrmdlhcqa68vhd170h4pcxlz1csqr-python2.7-grpcio-1.12.0.drv' failed with exit code 1
builder for '/nix/store/xvl1niqlx1al7f84a7jg68bahpnbylr5-python3.6-grpcio-1.12.0.drv' failed with exit code 1
error: build of '/nix/store/nirlrmdlhcqa68vhd170h4pcxlz1csqr-python2.7-grpcio-1.12.0.drv', '/nix/store/xvl1niqlx1al7f84a7jg68bahpnbylr5-python3.6-grpcio-1.12.0.drv' failed

Success on x86_64-linux (full log)
Attempted: python27Packages.grpcio, python36Packages.grpcio
Partial log (click to expand)
running build_ext
copying python_build/lib.linux-x86_64-3.6/grpc/_cython/cygrpc.cpython-36m-x86_64-linux-gnu.so -> src/python/grpcio/grpc/_cython
Found cython-generated files...

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/09ssh5j07cgx6c76v8nzrqdk7h6iy8r4-python2.7-grpcio-1.12.0
/nix/store/da2zjkpbx0kkggdc6md11gjagsgwni9v-python3.6-grpcio-1.12.0

Success on aarch64-linux (full log)
Attempted: python27Packages.grpcio, python36Packages.grpcio
Partial log (click to expand)
running build_ext
copying python_build/lib.linux-aarch64-3.6/grpc/_cython/cygrpc.cpython-36m-aarch64-linux-gnu.so -> src/python/grpcio/grpc/_cython
Found cython-generated files...

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/m6n57i7s3y3dqnds09anp2j2pnbzw6cr-python2.7-grpcio-1.12.0
/nix/store/d1274jp6x1ylaq44ana2xkdki1bsqhl5-python3.6-grpcio-1.12.0

Ran 0 tests in 0.000s

No tests are found. Either the test runner cannot find tests and needs to be patched, or there simply are no tests in which case the tests need to be disabled. Do include a comment explaining why the tests are disabled.

The current version is 1.9.1, not 1.9.0.

Grpc has tests, but they are not included in the package on PyPi. This has not changed since the previous version (see: https://hydra.nixos.org/build/74606746/nixlog/2/tail). I can disable the check phase, but I don't really see why that is necessary.

It would be nicer to disable the tests but let's not hold the bump because of housekeeping.


Unable to download ImageNet-R dataset

Hello,
I am encountering an issue with downloading the ImageNet-R dataset.  Even when I try to download it, the download doesn't seem to proceed. Could you please resolve this issue?
Thank you in advance for your help.
Best regards,
Minguk jang

Have you figure it out? I create a huggingface dataset so that people can have easily access to it. Check it out link


Add Apache license to a few files

Required for ./dev/check-license to succeed

Looks fine. This should also be cherry-picked onto our release branch, right?


Plugin not working in combination with plugin-content-docs?

Hi,
great plugin, but somehow I can't get it to work in combination with the content-docs plugin.
Our repo has a default docs directory and on build it fetches docs from other repos (which get added to the external directory).
This plugin only works for the documentation passed to the docs object in the classic preset but not with the docs in the content-docs plugin. They should be the same, right? Or did I misunderstand something?
In this config the include plugin works for the default docs:
  presets: [
    [
      '@docusaurus/preset-classic',
      {
        docs: {
          id: "docs",
          sidebarPath: require.resolve('./sidebars.js'),
        },
        theme: {
          customCss: require.resolve('./src/css/custom.css'),
        },
      },
    ]
  ],
  plugins: [
    [
      '@docusaurus/plugin-content-docs',
      {
        id: 'doc2',
        path: 'external/docs2/docs',
        routeBasePath: 'docs2',
        sidebarPath: require.resolve('./external/doc2/sidebars.js'),
      }
    ],
  ]

But if I simply replace the docs it works for the docs2:
  presets: [
    [
      '@docusaurus/preset-classic',
      {
        docs: {
           id: 'doc2',
           path: 'external/docs2/docs',
           routeBasePath: 'docs2',
           sidebarPath: require.resolve('./external/doc2/sidebars.js'),
        },
        theme: {
          customCss: require.resolve('./src/css/custom.css'),
        },
      },
    ]
  ],
  plugins: [
    [
      '@docusaurus/plugin-content-docs',
      {
        id: "docs",
        sidebarPath: require.resolve('./sidebars.js'),
      }
    ],
  ]

Thanks for your help in advance

Hi
If I understand your request correctly, you have 2 instances of plugin-content-docs, one loaded from preset-classic (=docs in preset-classic) and another one with another docs folder added on plugins config section?
This is unfortunately not supported by current version of docusaurus-plugin-includes.
The plugin docusaurus-plugin-includes only works with one instance of docusaurus-plugin-docs.
At runtime, docusaurus-plugin-includes is searching for the instance of docusaurus-plugin-docs, then copies the list of files handled by that instance of docusaurus-plugin-docs, and finally adds a WebPack rule to process these files with an additional loader from within docusaurus-plugin-includes (you can find that in the sourcecode in index.ts, configureWebpack).
Regards,
techfreak01


Server error when query string cantain werid characters

Here is the minimal express server
const express = require('express');
const app = express();

app.get('/', function (req, res, next) {
    res.status(200).send('I am alive');
});

app.listen(3000, function () {
    console.log('server started at port 3000');
});

After server started, the following two requests were made:
curl -S 'http://localhost:3000'

respond with expected content. but when some weird characters exist in query string, server fails silently.
curl -S 'http://localhost:3000?plog_id=1516daa51f5f3f49df763f4bde4a147910010???????A4L 2016? 45 TFSI quattro?????_?????A4L0.6??-???'

The response becomes:
curl: (52) Empty reply from server

which is unexprected behavior!

That's because curl is not URLencoding the space characters. Paste the URL in a browser to see it working.
Please post general queries at https://gitter.im/expressjs/express.


Sketches with assets don't work

E.g. fonts, png's that kind of thing. Sample:
function preload()
{
	background= loadImage('background.png');
}

function setup()
{
	createCanvas(background.width, background.height);
}

function draw()
{
	image(background, 0, 0);
}

Access to image at 'file:///...' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https. [file:///C:/...index.html]

Turns up in the debug console after a while. I don't know if this extension is invoking a chrome under the hood - if so passing --allow-file-access-from-files should fix it.

Hey there @rbtcollins, thanks for the report! I'll take a look on the weekend.

I've spent the last couple of hours trying to find a solution, but I don't think there will be one, @rbtcollins :(
In the end there's this github issue and stackoverflow post, and each point to each other hah
https://stackoverflow.com/questions/55841688/vscode-cross-origin-request-inside-webview
https://github.com/microsoft/vscode/issues/72900
Which kinda makes sense, to not allow a random page in a webview to have file access, but it's a bummer.
Perhaps it'd be possible to make it work if the webview loaded a page from, say, localhost:1234 instead of simply a file.

Perhaps you could layer on the go-live extension? https://github.com/ritwickdey/vscode-live-server Using that works, it is just not embedded in a webview obviously...

Hey there Collins! Sorry about the delay, I was focussing on this thing the past couple of weekends.
It has its own live server, so I might feel inclined to port the updates on that to this extension. However, if you're feeling really inspired, a PR would be a m a z i n g.

Unable to preview loading a 3d model. Might be relevant for this thread. Thank you.

Thanks for the report @olgv.
The problem is still the same: it's a lot of work to port the server code from ProcessingP5 to this extension, and it's bug prone, full-of-corner-cases kinda code.
Until that perhaps eventually gets done, you can use ProcessingP5 with the option to edit code in your own editor, vscode in this case, so you get the auto refresh stuff with loading of files working.


REFACTOR-#2059: Consolidate environment variables

What do these changes do?
Consolidate all environment variables used for Modin configuration in single file.
Also introduce the API to manage configuration, could be generalized later for non-envinronment-based options.
Also provide short help on existing options by running python -m modin.config.

Current help
MODIN_BACKEND: Engine running on a single node of distribution
        Provide a string (valid examples are: Pandas, OmniSci, Pyarrow)
        Current value: Pandas
MODIN_CPUS: How may CPU cores to utilize across the whole distribution
        Provide an integer value
        Current value: 8
MODIN_LOG_RPYC: Whether to gather RPyC logs (applicable for remote context)
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_TRACE_RPYC: Whether to trace RPyC calls (applicable for remote context)
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_USE_CALCITE: Whether to use Calcite for OmniSci queries execution
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_ENGINE: Distribution engine to run queries by
        Provide a string (valid examples are: Ray, Dask, Python)
        Current value: Ray
MODIN_DEBUG: Forces Modin engine to be "Python" unless specified by $MODIN_ENGINE
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_EXPERIMENTAL: Turns on experimental features
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_OUT_OF_CORE: Unknown
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_RAY_CLUSTER: True if Modin is running on pre-initialized Ray cluster
        Provide a boolean flag (any of 'true', 'yes' or '1' in case insensitive manner is considered positive)
        Current value: None
MODIN_MEMORY: How much memory give to each Ray worker (in bytes)
        Provide an integer value
        Current value: None
MODIN_OMNISCI_FRAGMENT_SIZE: How big a fragment in OmniSci should be when creating a table (in rows)
        Provide an integer value
        Current value: None
MODIN_ON_RAY_PLASMA_DIR: Path to Plasma storage for Ray
        Provide a string
        Current value: None
MODIN_REDIS_ADDRESS: What Redis address to connect to when running in Ray cluster
        Provide a string
        Current value: None
MODIN_SOCKS_PROXY: SOCKS proxy address if it is needed for SSH to work
        Provide a string
        Current value: None
MODIN_TEST_DATASET_SIZE: Dataset size for running some tests
        Provide a string (valid examples are: small, normal, big)
        Current value: None

[x] commit message follows format outlined here
[x] passes flake8 modin
[x] passes black --check modin
[x] signed commit with git commit -s
[x] Resolves #2059
[x] tests added and passing

LGTM, let's wait @devin-petersohn.

Anything needed from me to get this merged?

Anything needed from me to get this merged?

I think nothing is needed.

@vnlitvinov please restart CI. Tests for Omnisci backend should be working now.

After this I will do merge.

I've rebased off master to make sure I got all recent CI fixes

@anmyachev @devin-petersohn I believe the failure in running OmniSci tests isn't related to this PR (the tests actually pass, all the things crashed and burnt during the exit of the interpreter according to the logs).
I think we should merge this PR.


[Bug?]: @vanilla-extract/vite-plugin causes errors in console during build's transform

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When using Vanilla Extract with the @vanilla-extract/vite-plugin as the first in the list of plugins, I receive lots of errors in the console.
It seems like I get one error per:

reference to .css.ts file, or
to a .ts file from a .css.ts file

Example with a longer stack trace:
Error: Failed to load url /_build/src/util/styling/transitionGroupStyles.ts (resolved id: /_build/src/util/styling/transitionGroupStyles.ts) in /Users/james/code/lexi/apps/web/src/components/organisms/Modal/Modal.css.ts. Does the file exist?
    at loadAndTransform (file:///Users/james/code/lexi/node_modules/.pnpm/vite@4.5.0_@types+node@20.10.5/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21)
    at async getViteModuleNode (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:54:4)
    at async add_by_url (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:86:16)
    at async Promise.all (index 3)
    at async findDeps (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:112:2)
    at async add (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:81:4)
    at async add_by_url (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:89:4)
    at async Promise.all (index 7)
    at async findDeps (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:112:2)
    at async add (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:81:4)
    at async add_by_url (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:89:4)
    at async Promise.all (index 3)
    at async findDeps (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:112:2)
    at async add (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:81:4)
    at async add_by_url (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:89:4)
    at async Promise.all (index 7)
    at async findDeps (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:112:2)
    at async add (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:81:4)
    at async add_by_url (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:89:4)
    at async Promise.all (index 4)
    at async findDeps (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:112:2)
    at async findDependencies (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:127:5)
    at async findStylesInModuleGraph (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/collect-styles.js:156:23)
    at async viteAssets (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/dev-server-manifest.js:46:7)
    at async Object.assets (file:///Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/manifest/dev-server-manifest.js:217:16)
    at async Context.load (/Users/james/code/lexi/node_modules/.pnpm/vinxi@0.1.1_@types+node@20.10.5_preact@10.19.3/node_modules/vinxi/lib/plugins/manifest.js:59:13)
    at async Object.load (file:///Users/james/code/lexi/node_modules/.pnpm/vite@4.5.0_@types+node@20.10.5/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:44323:32)
    at async loadAndTransform (file:///Users/james/code/lexi/node_modules/.pnpm/vite@4.5.0_@types+node@20.10.5/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:54954:24)
    at async viteTransformMiddleware (file:///Users/james/code/lexi/node_modules/.pnpm/vite@4.5.0_@types+node@20.10.5/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:64430:32) {
  code: 'ERR_LOAD_URL'
}

Example with shorter stack trace:
Error: Failed to load url /_build/src/styles/utils.css.ts (resolved id: /_build/src/styles/utils.css.ts) in /Users/james/code/lexi/apps/web/src/pages/Feed/components/FeedList/FeedList.css.ts. Does the file exist?
    at loadAndTransform (file:///Users/james/code/lexi/node_modules/.pnpm/vite@4.5.0_@types+node@20.10.5/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55015:21) {
  code: 'ERR_LOAD_URL'
}

Expected behavior 🤔
I would like it if the console didn't shout at me.
Steps to reproduce 🕹
Steps:

Init a fresh start project
Add vanilla extract as a dependency and add the plugin to site
Create an example style in a .css.ts file
Reference a .css.ts within a Solid component element for the class.
npm run dev or npm run build && npm run start
Load the page in the browser.

I'll try to make a minimal repro soon unless somebody beats me to it.
Context 🔦
I'm not sure what, if any, effect this has on the build. I have had the build working with the errors being logged (rn things are broken but that's a separate issue). Note the errors only seem to arise once a route is loaded in the browser.
Also worth noting, I've only had this issue since I migrated to the new Vinxi/Nitro version of Start.
I'm assuming it's because .css.ts files are transformed and bundled as CSS at build time. This may be more of a Vinxi issue, but I suspect it's more to do with the new defineConfig() Vite config wrapper from @solidjs/start/config. idk really.
Your environment 🌎
OS: macOS Sonoma 14.2.1
Browser: N/A
Node: 20.10.0
pnpm: 8.11.0

npm-deps: # basically everything is up-to-date
    "@solidjs/meta": "0.29.3",
    "@solidjs/router": "0.10.6",
    "@solidjs/start": "0.4.3",
    "@vanilla-extract/css": "1.14.0",
    "@vanilla-extract/css-utils": "0.1.3",
    "@vanilla-extract/dynamic": "2.1.0",
    "@vanilla-extract/vite-plugin": "3.9.3",
    "autoprefixer": "10.4.16",
    "database": "workspace:*",
    "dotenv": "16.3.1",
    "mux.js": "6.3.0",
    "postcss": "8.4.33",
    "rvfc-polyfill": "1.0.7",
    "shaka-player": "4.7.1",
    "shared-utils": "workspace:*",
    "solid-icons": "1.1.0",
    "solid-js": "1.8.8",
    "solid-transition-group": "0.2.3",
    "ts-essentials": "9.4.1",
    "typescript": "5.2.2",
    "vinxi": "0.1.1",
    "zod": "3.22.4"

Related to https://github.com/nksaraf/vinxi/issues/98

Can you provide a repro please. I wasn't able to trigger an error with @vanilla/extract. Seemed to work fine.

It only happens if inside a .css.ts you import from another .ts file.
Repro: https://github.com/emonadeo/solid-start-issue-1224

Dev server won't even start with v4 of the Vanilla Extract Vite plugin.
Repro: https://github.com/rvlzzr/ssve

Looks like this is related to a downstream issue with Vanilla Extract on windows. https://github.com/vanilla-extract-css/vanilla-extract/issues/1344
In any case this issue belongs upstream so probably not much value tracking it here.


Support For JavaBean getter/setter

The following class exposes the firstname field through the getFirstname() method as "givenName"
@XmlRootElement()
public class User {
   private String firstname;
   private String lastname;

   @XmlElement(name = "givenName")
   public String getFirstname() {
      return firstname;
   }
}

To be included in feature #14.


Grace backoff timeout in the client propperly.

In the client even after 60 seconds of reconnect it stops retrying but it doesn't call the disconnect function.

dup of #2946


Polling thread not terminated when client is destroyed

We need to make sure that any threads spawned by the FlagsmithClient class are terminated before destroying the client instance.

Hi @matthewelwell thanks for opening this issue so quickly
I've seen your recent changes here https://github.com/Flagsmith/flagsmith-java-client/pull/83
I'm wondering if the RequestProcessor should be closed as well as it's internally using a thread pool

Hi @aboivin, yes, good spot! I'm working on that now.

@aboivin I've completed that (plus some extra bits around analytics processing) here.

This was completed in v5.0.6


Express Webpack Critical Dependency Error

What is the current behavior?
The express server still starts up and the callback prints "server running", but I get this error in the terminal when I build webpack.
Critical dependencies:  78:29-56 the request of a dependency is an expression
module.exports = {
  ...
  module: {
    exprContextCritical: false,
  }
}

The above config can suppress the error, but I'd rather not do that in case something breaks further down the line.
If the current behavior is a bug, please provide the steps to reproduce.
import * as Express from 'express';

const app = Express().listen(3000, () => console.log("server running"));

var path = require("path")

module.exports = {
  entry: {
    "server": "./server/server.ts"
  },
  target: "node",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: "bundle.js",
    publicPath: "/public/"
  },
  module: {
    loaders: [
      {
        test: /\.ts(x?)$/,
        exclude: /node_modules/,
        loader: "ts-loader"
      }, {
        test: /\.js(x?)$/,
        exclude: /node_modules/,
        loader: "babel-loader"
      }, {
        test: /\.json$/,
        loader: "json-loader"
      }, {
        test: /\.scss$/,
        exclude: /node_modules/,
        loaders: ["style-loader", "css-loader", "postcss-loader", "sass-loader"]
      }, {
        test: /\.css$/,
        loader: ["style-loader", "css-loader", "postcss-loader"]
      }, {
        test: /\.(jpe?g|gif|png|svg)$/i,
        loader: 'url-loader?limit=10000'
      }
    ]
  }
}

What is the expected behavior?
No Critical Dependency Error
**Please mention other relevant information such as the browser version, Node.js version,
Node --version // v6.9.1
<EMAIL_ADDRESS>

Sounds like something that may happen if webpack tries to bundle express. Have you tried setting externals: { 'express': 'commonjs express' }, or maybe using something like https://github.com/liady/webpack-node-externals?

So I don't know why this worked exactly, but when I created a separate webpack.config file for the client and server, the error went away.


Sky problem in mobile application. Unreal 5.1.1

Hello friends. I ran into a problem, I can not solve it for several weeks. I searched all the forums, searched the entire Internet and could not find anything to solve this problem. When compiling the application, I have no atmosphere, just a black screen. I use version Unreal 5.1.1. Can someone help. How to solve this problem. Thank you

Is that on a mobile device of some sort? Some of the information here may help:
https://github.com/CesiumGS/cesium-unreal/issues/661

Do you have the same problem in the Cesium for Unreal Samples project, or does it work there?

works in the project. And when I drop it on the phone it stops. What to do, can you advise?

This photo was taken on an Android device.

You can do it by hand as Kring pointed out on 661 but i got same black screen and i had to use different mesh and material from a iso sky temple i had around from marketplace(an SM_SkySphere mesh and an HDRI... or there is a mobile section on cesium sunsky (outliner->details) to do that automatically, but i couldn't make it work with any mesh/material... I noticed that it changes also some lights/shadow settings (another thing that im trying to make it work around all android blockers), maybe Kring can give us more information on that mobile option, because i couldn't find any info on that around my web search bubble...

You know, I've found that the CesiumSunSky is working fine for me these days with the default settings. I'm not sure what changed. New Android device? New Unreal Engine version? A setting change? That's why I asked if the Cesium for Unreal Samples problem is exhibiting the same problem for you, because it's not for me. If that project works but yours doesn't, it should be a relatively simple matter of finding the difference in settings. So please check and let me know.

Here's what the first level in Samples looks like on my Pixel 6 Pro, packages with UE 5.1.1:

I chose these settings when I built it from the Platforms menu:

These is one artifact with the water material when the specular highlight is pointed directly directly at the camera, though:

Here's what the first level in Samples looks like on my Pixel 6 Pro, packages with UE 5.1.1:

I chose these settings when I built it from the Platforms menu:

These is one artifact with the water material when the specular highlight is pointed directly directly at the camera, though:

I tried everything as you said above!  Here is a photo.

Can you try doing the same in the Cesium for Unreal Samples project and see if it works for you there?

everything is working. thanks) but now I have no shadows, you dont know what it could be?

How did you fix it? Just by using the Cesium for Unreal Samples? It would be helpful to know what was missing from your original project.
Shadows seem to be working for me, but they're finicky... don't appear until you get close, for example, and they sometimes disappear for unknown reasons. I'm not sure how to solve this, though. Cesium for Unreal is essentially just providing Unreal Engine with static meshes. So it might be best to raise the question in a more general UE forum. Perhaps the shadow setting defaults are different on mobile for performance reasons, or there are limitations in the mobile renderer.

I did everything as you wrote. Created a sphere and placed it in the middle. I increased it in size so that it covered my entire map. and assigned a static mesh to this sphere, and assigned the sky to this static mesh. all as you wrote)


Remove the deprecated --debug in istioctl

Currently the default proxy image has curl already, which means --debug option is not needed, and it's deprecated as well.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: wattli
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I wish we'd kept the feature, or clearly document the alternative, instead of deleting it but I guess it's good to not have misleading docs

/lgtm
(with caveat above)

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ldemailly, wattli
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

https://github.com/istio/istio.github.io/pull/1458 for owners issue


RequestExt on http::request::Parts

Once you turn a http::Request into http::request::Parts and hyper::Body using Request::into_parts, you lose the ability to get / set state and data from the request. It would be awesome if the same extensions from the RequestExt could also be added to http::request::Parts via means of a RequestPartsExt.

Great idea! I never noticed that the extensions are defined on head: Parts, not the Request itself. This can definitely help when you need to consume a request (e.g. json payload) but still use data, params or context. At the moment the only solution is cloning, and that is not ideal.
Would you be willing to contribute the PR? :)

Would you be willing to contribute the PR? :)

Sure!

Merged, thanks! I will create a new release this weekend.


Update testMatch to also be compatible with Jest 24

For people who try to use Jest 24, there is a different version of micromatch and it behaves differently.  These changes should make it behave the same before and after changing Jest versions.
Without this change, Jest 24 will come up with no files to test.
I tested with npm run test -- --listTests on two projects, one with the default Jest 23 and another with the new Jest 24.  In addition to numerous normally named test files had some special case files like src/.test.js, src/test.js, and src/somethingtest.js.  Only the first two matched and the third one didn't; both pre-, and post- this change.

Hi @ngbrown, thanks for that. I think this change should be accompanied by a move to Jest 24... but I agree it's necessary for that. Let's hold off until that time, if that's OK?

I submitted this separate because Jest 24 isn't quite ready (facebook/jest#7707) to be pulled into create-react-app. Because Jest 24 has better support for TypeScript people might want to try it out.  Since this is one of the first things they will run into, it might as well be fixed for everyone.
Being able to merge now is why I made sure the new pattern would work equivalently in the older micromatch.

If jest 24 is blocked until a new major, it'd be a good idea to land this in the meantime

I'm not sure this is still needed as we've landed Jest 24 and from my quick tests it seems to be working okay.
@SimenB can you advise? Should we make this change?

If you've tested on windows and it works, this shouldn't be needed

I tested CRA version 3.0.0-next.b0cbf2ca on windows, and it is not detecting any tests.
This PR solves the problem.


PDF generation - include font in package

Context: https://github.com/sanskrit-coders/jyotisha/issues/10#issuecomment-351867006

Where should the font go? It's ideal the user installs it in ~/.fonts. Alternatively, having it in the tex directory will work -- but that is now \tmp?

Just include it in jyotisha/panchangam/scripts/fonts and then use it just as you refer to data directory contents using relative (file) paths?

The user shouldn't need to go install some font - either setup.py should do it for him; or the tex commands should be pointed to the right location upon invocation.

I think this will come in handy!

Fixed long ago.


[Devportal API] Implementing Subscription related API flows

https://github.com/wso2/apk/issues/305