Example demo-ssr not working

I am unable to get leptos-tiptap to work in an SSR environment with axum. Using tag leptos-tiptap/v0.6.0 results in a Tiptap instance that does not seem to run.
Running the example demo-ssr results in an empty editor field, where normally (editable and formatted) content would be displayed. The "HTML Output" field below the editor does show the example paragraph, but it is unformatted (as intended). Running demo-csr does have a working Tiptap editor instance.
I encounter the same issue after integrating leptos-tiptap in my own project.
If it matters, running cargo leptos watch in the demo-ssr directory results in the error below. The demo can only be started with cargo run --feature ssr.
...
Front compiling WASM
Error: at `/Users/USER/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.7/src/compile/front.rs:47:30`

Caused by:
    0: at `/Users/USER/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.7/src/compile/front.rs:120:10`
    1:

       it looks like the Rust project used to create this wasm file was linked against
       version of wasm-bindgen that uses a different bindgen format than this binary:

         rust wasm file schema version: 0.2.92
            this binary schema version: 0.2.91

       Currently the bindgen format is unstable enough that these two schema versions
       must exactly match. You can accomplish this by either updating this binary or
       the wasm-bindgen dependency in the Rust project.

       You should be able to update the wasm-bindgen dependency with:

           cargo update -p wasm-bindgen --precise 0.2.91

       don't forget to recompile your wasm file! Alternatively, you can update the
       binary with:

           cargo install -f wasm-bindgen-cli --version 0.2.92

       if this warning fails to go away though and you're not sure what to do feel free
       to open an issue at https://github.com/rustwasm/wasm-bindgen/issues!

Either of the suggested commands does not alleviate the issue of running through cargo leptos watch.
$ rustup --version
info: The currently active `rustc` version is `rustc 1.76.0 (07dca489a 2024-02-04)`

I'm fairly new to both leptos and rust. If I can provide any additional information that is useful, please let me know.

Have you tried running:
cargo install -f wasm-bindgen-cli --version 0.2.92
cargo update -p wasm-bindgen --precise 0.2.91

in your terminal?

@JosVerheij This can come from time to time when you have non matching versions installed. As you can also see from the logs, the error originated in cargo-leptos. As @RamirezAlex already pointed out, performing the two commands mentioned or just doing a
cargo install cargo-leptos
cargo install wasm-bindgen-cli
cargo install wasm-bindgen

so that everything is up-to-date (which should generally work well together) should do the trick.

My bad. I had an older version of cargo-leptos installed (0.2.7). Updated to 0.2.16 by running cargo install cargo-leptos and I can get the example running.
Had not noticed cargo-leptos was apparently not updated through running cargo update.
Thanks for your help!


Wrong start key for GSIs

Hey,
To handle pagination on a GSI, DynamoDB needs primary keys of both the table and the GSI, but the marshalling function strips the table keys:
https://github.com/awslabs/dynamodb-data-mapper-js/blob/0912ab9cdb63803ca737debbc28fbb4357ca3765/packages/dynamodb-data-mapper/src/DataMapper.ts#L855
Which returns Exclusive Start Key must have same size as table's key schema
Of course the ideal solution would be to directly access and pass the LastEvaluatedKey

According to the DynamoDB guide on secondary indices, GSI keys do not need to overlap with the table keys at all.
Have you modeled all the keys of the index being queried?

The LastEvaluatedKey contains both the table keys and the GSI keys

I did a bit of experimentation and found that while LastEvaluatedKey typically contains the table and index keys, the exact keys returned are not uniform across multiple queries of the same index. According to this AWS forum post, only LastEvaluatedKeys returned from previous requests on the same index are officially accepted as ExclusiveStartKey values.
Both query and scan will need to be updated to marshall the values provided instead of the keys defined.


[tools]Update pack.sh for cordova all-in-one suite shared mode packing.

Please provide the UT result.

Checked done, It is ok with this patch.

LGTM


Connect Hololens via USB to Ethernet network

Is it possible to connect the Hololens via a (HP Micro USB to Ethernet adapter) to a ethernet network?

This is not possible.


Colour Picker available in other file types.

VSCode Version: 1.17.0-insider
OS Version: Windows 10

Could we have the new colour picker available for other file types.
Vuejs template files .vue have

https://github.com/vuejs/vetur/issues/374

Is there a reason this was closed?


Transactor Permissioning Documentation

The following PR is adds description to the sysadmin guide about how to use Transactor Permissioning.
This PR is built on top of #766 Implement Off-Chain Transactor Permissioning as this document covers it as well.

rebasing before merge


[Closes #17] relx compatible

Added required applications entry.

There' already a PR for this.

merged.
Thank you!


Use single address options

Only use one address as option when creating the wallet.
Todo:

Add a switch while creating a wallet
Add single_address option with wallet create request

Will be implemented in v2.0.0


Escape char outside the string

See example below:
x:="foo"\13"bar"; //escape char outside the string
x:="I said:"\""As he said";

\n \r work now, but need improvments


Needs to be updated for Tailwind 1.0

I installed the dusk dashboard today and noticed it looked quite different from the screenshots.

Using<EMAIL_ADDRESS>instead of the current version of Tailwind makes it look just like the README.
I believe most of the class names relating to colours were changed in 1.x, so that needs to be updated.
I can take a stab at it?

I can confirm this

Or just import 0.7 for now.

Same here


Use CUDA_VISIBLE_DEVICES in ChainerX tests

Currently ChainerX always uses GPU {0,1} for testing. It should be randomly selected like done in chainer-test.
https://github.com/chainer/chainer-test/blob/8420a5880e12cabb00d7cde5796870891c2c2892/docker.py#L812-L822

Let me test it on Jenkins.
Jenkins, test this please.

This fix makes the test configuration nondeterministic.
Is it appropriate?

Now I think it's OK to shuffle devices randomly, as the devices on Jenkins are physically identical.
(Btw I want a brief comment about the intent.)

I've added comment.

Jenkins, test this please.

Hm, still OOM 🤔

Jenkins CI test (for commit eee0aedf411701a46a93422c654f1a1c9536fa55, target branch master) failed with status FAILURE.

Jenkins, test this please.

Jenkins CI test (for commit eee0aedf411701a46a93422c654f1a1c9536fa55, target branch master) succeeded!

OOM might have been caused by old builds triggered before this PR (is/was going to be merged).

LGTM!


Improve reflection capabilities in mjSpec API

Is your feature request related to a problem? Please describe.
I am working on using mujoco as the multi-body dynamics engine for a larger simulation software. The future release of mjSpec will be extremely useful for our use case, which is users loading some spec (XML, URDF, etc), the program reflecting on said spec, and modifying it as needed. For example, we have wrappers for mujoco actuators so that the force/torque they produce can be set through models in our software.
We had a previous implementation working by reading and rewriting the original XML and reloading that (I know...), so an officially supported mjSpec wy will go a long way. I have been toying with the latest version in main, and while creating an mjSpec from scratch seems to work great, it is difficult to introspect on existing mjSpec. Particularly, I find it impossible to find and safely access existing elements using the API.
Describe the solution you'd like
I'd like methods to safely cast a mjsElement* to the specific mjsXYZ* class:
mjsBody* mjs_asBody(mjsElement* element);

With these methods and the existing mjs_firstChild/mjs_nextChild, one should be able to traverse the body tree and access/modify all elements contained in it.
The other capability I'd like to see is a way to iterate over non-tree elements, like actuators or sensors.
Given that the API is a WIP, some of these features might be planned (or even already available, and I'm just not seeing them).
Thank you for all the good work on mujoco!

Now added. Please let us know what other issues you encounter!


PowerToys Run bug

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
2022-06-05.txt
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

This might be caused by some older files not being uninstalled correctly.
Would you mind:
1 - Uninstall PowerToys.
2 - See if the PowerToys install directory (default: C:\Program Files\PowerToys) is still there. If it is, delete it manually.
3 - Install PowerToys.
Please let us know if this works for you.
/needinfo


[cephfs] RBAC, security, and deployment improvements

This does a handful of small things to smooth deployments and improve security

Fixes up the example RBAC-enabled deployment with configuration in-repo (adds PROVISIONER_SECRET_NAMESPACE=cephfs env, which is necessary in lieu of broad clusterwide secret permissions and enabled by #550)
Adds a note to the README explaining circumstances under which an admin might need to add clusterwide secret permissions, along with how to do it
Fixes adminSecretNamespace parameter in example storage class to match instructions in README
Simplifies namespace and admin secret generation
Removed whole-tree read permissions for generated users - it's highly untenable in terms of security.  Testing with Ceph Luminous + Kubernetes 1.9.4 on Fedora kernel 4.15.3, this does not seem to be necessary - I'd be interested to find out how far back one would have to go before it is necessary

I've been trying to figure out where the MDS "allow r" requirement came from, specifically...can't seem to find anything other than that it was to work around a kernel cephfs bug.  @rootfs Do you have some insight?  Maybe it makes sense to put that particular change behind a feature flag rather than making it across-the-board?

This all seems reasonable to me, but not sure if we still need. @cofyc can you take a look? ty

@mcronce
How about updating docs only in this PR?

@mcronce
Hi, could you rebase it on latest master?


New docs directory

New docs directory populated with developers.md
Content is exchanges API functions

Documentation should be added for strategy functions by someone familiar with strategies.
Documentation of database layout would also be good


Pass Additional props remove localstorage related code for storing data and username from App.tsx to index.tsx

Pass onChange, initialData, user, onUsernameChange props to Excalidraw App.

any update on this ?

I just realized this PR prevents loading from backend.

I just realized this PR prevents loading from backend. I'll just remove the && !this.props.initialData condition until we factor out backend logic as well.

Nice catch @dwelle , was there any specific reason for adding this check?
coz initially, we use to fetch from local storage so it worked but now we can't have this check here since data is received from host app and shouldn't the condition be isExternalScene && this.props.initialData instead ? so we show the warning when initialData is there and trying to load from external scene.

shouldn't the condition be isExternalScene && this.props.initialData instead

Only for the purpose of displaying a warning. We still need to load from backend for the sake of our own app.
But I don't think displaying a warning is worth it because in the next PR we'll factor out backend loading as well, I presume.

shouldn't the condition be isExternalScene && this.props.initialData instead

Only for the purpose of displaying a warning. We still need to load from backend for the sake of our own app.
But I don't think displaying a warning is worth it because in the next PR we'll factor out backend loading as well, I presume (at least the init logic).

got it 👍


Dependencies

Hi @hereariim
While working on https://github.com/conda-forge/napari-blossom-feedstock/pull/5
I noticed python_requires = ==3.8, is there a reason for that strict pinning?
https://github.com/hereariim/napari-blossom/blob/main/setup.cfg#L45
Cheers!

Hi @goanpeca
Initially, there is no reason.
I can't get my module to work from built-in napari. In doing so, I thought that the tensorflow package would work, and by transitivity, the module would work. Unfortunately, it didn't. You can remove it if you think it's unnecessary.
Best!

@hereariim I will need to add a patch tio be able to build the recipe, otherwise it wont work. Could you add. please change this to python_requires = >=3.8 ?
Cheers

@hereariim it also seems all your dependencies are hard pins. That can generate issues when solving environments
install_requires =
    numpy==1.23.0
    magicgui==0.6.1
    qtpy
    opencv-python-headless==<IP_ADDRESS>
    tensorflow==2.11.0
    scikit-image==0.19.3
    napari
    focal_loss==0.0.7
    pillow==9.3.0
    tqdm==4.64.1

Please try to use >= or <=, and not ==

thanks, i added modifications,
best,

@goanpeca thanks, i added modifications,
best,


Vue and SvelteKit

Since it's named vite-plugin-stylex, I expect it to work on other vite projects. I tried it with Vue, it works. Not sure about SvelteKit and other frameworks. Are you planning on supporting them as well?

Since it's named vite-plugin-stylex, I expect it to work on other vite projects. I tried it with Vue, it works. Not sure about SvelteKit and other frameworks. Are you planning on supporting them as well?

StyleX itself is framework agnostic, so this plugin should attempt to be as compatible as possible. I'm not familiar with how those frameworks expect vite plugins to treat their source files and if it's going to be compatible with the official StyleX babel plugin this project uses under the hood.
It's early to say, but let's let people experiment with it and see how it goes. Trying this with Remix is next on my to-do list.

@walmartwarlord SvelteKit support added in v0.3.0!
Vue works because it follows the SPA approach by default. Nuxt probably doesn't work out of the box given that every framework that has something to do with SSR requires some work on the plugin side, but shouldn't be hard to add. I'll create an issue for it.
As for other frameworks, I need to revisit Qwik and Astro with the new approach, then try Solid Start, and possibly even Angular lol.
Closing this one for now, but keep in mind there's also work happening in the official StyleX repository (https://github.com/facebook/stylex) to support Vite, many of us are exploring different approaches to make a plugin for vite work well.
Thanks! :smile:


World chunks

The world must be split into 9x9 (platforms) sized chunks so that only nearby areas need to be send to new clients.

Structures are now split up into chunks as of 7718c4e8b37b882b7260363371311463ca29b306
Next is unloading/reloading chunks based on distance.

Far away chunks are now no longer rendered, mostly useful on the server where structures must not be unloaded.

Complete as of https://github.com/ForLoveOfCats/SkyOfSteel/commit/952f3b6e3024a3ab6745afd52c56a3dbc34b2940
Crashes occasionally when sending chunks to client due to Godot Mono bug, investigating 3.1 Alpha 4

Godot 3.1 fixed the crash, changing target Godot version to 3.1 Alpha 4

Crash is fixed as of https://github.com/ForLoveOfCats/SkyOfSteel/commit/c12f2a59e40c0b662033af5634ea5b5ccf154da6


Add error documentation

This PR adds the initial documentation page for errors presented to user of the API. All existing errors should be listed. Links supplied by error messages to documenation is also fixed, as was missing the .html extension.

 (2) Document existing API errors

👍 Good work

Should we also update errors in the the API reference section to match the errors page?


Settings Screen

It would be super useful to be able to have a platform ware settings screen. https://pub.dev/packages/settings_ui does it very nicely, but has some unwanted features that do not work well with flutter_platform_widgets, for example the forced dark-mode awareness (I want to make a settings screen to add manual dark mode) and the inability to override the platform.

Not sure about doing a whole settings page. Perhaps raise an issue there so it uses the Theme.of(context).platform rather than Platform.isIOS and Platform.isAndroid (https://github.com/yako-dev/flutter-settings-ui/blob/master/lib/src/settings_section.dart#L22) and to better support Dark mode

Also consider using the systems dark mode, because this is how it is intended to be. And this might actually have consequences in the store approvals in the future (a very very personal assumption, not to take granted!)

Closing as this project is not designed to build a page like this.


Scrolling doesn't work for autos list

Describe the bug
Scrolling in the paths pane works as expected however in the autos pane it does not scroll
To Reproduce
Steps to reproduce the behavior:

Open pathplanner with many autos
Try to scroll
It doesn't scroll

Expected behavior
Being able to scroll to view all of my autos
Screenshots
If applicable, add screenshots to help explain your problem.
Versions: (please complete the following information):

OS: Windows 11
GUI Version: 2024.1.6
PPLib Version: n/a
PPLib Language: n/a

Additional context
Add any other context about the problem here.

I am also seeing this.  I noticed it's scrollable for a second, and if I can manage to get the scroll bar to appear, I can scroll by dragging the bar, but generally, it's not scrollable.
I rolled back to 2024.1.4, and did not have this problem

I'm not able to reproduce. So, I will need some more info about your exact setup + screenshots or videos if you can.

I'm not able to reproduce. So, I will need some more info about your exact setup + screenshots or videos if you can.

I have the same issue as well, I am running PathPlanner on Windows 11 (version 2024.1.6).

I'm not able to reproduce. So, I will need some more info about your exact setup + screenshots or videos if you can.

Hello, I am having this issue on MacOS as well. Here is a video. There are more autos on the right but I cannot scroll to them. I can work around this by changing the view of the list of autos, but that is annoying. Also I have had this issue on both v2024.1.2 and v2024.1.5. https://youtu.be/qaXpJkYPeD8

@mjansen4857 At your request, here's a GIF of v1.4 working

Here's a GIF of v1.5 not allowing me to scroll via my trackpad, nor bringing up the scrollbar on the right

The setup is simply a standard Windows 11 laptop running the loadable 1.4 and 1.5 versions of PathPlanner.

@mjansen4857 At your request, here's a GIF of v1.4 working

Here's a GIF of v1.5 not allowing me to scroll via my trackpad, nor bringing up the scrollbar on the right

The setup is simply a standard Windows 11 laptop running the loadable 1.4 and 1.5 versions of PathPlanner.

I was using a trackpad as well. If that is useful information.

I still can't reproduce, but I think I found a difference that could cause issues on some trackpads for some reason. If you get a chance, can you try a build from here and see if that solves the issue?

Yes, this fixed the issue on my macbook. Can't test on my Windows 10 laptop until tommorow but I can assure it fixed it for MacOS. Thank you!

Ok, I'm gonna assume that is the fix then. Thanks

I can also verify that the problem is fixed for me as well in the dev build


1.18 | Does not render / load edits for blocks under Y0

When performing my ususal coreprotect command, watson only recognizes the lines in which in my case diamond_ore is mined in a Y-layer higher then 0. Everything below 0 does get recognized by CP, but not by Watson in the menu.

EDIT: This is on a waterfall/purpur server (paper). This server always ran on 1.17 and just updated to 1.18, adding the 1.18 generation underneath the 1.17 world

duplicate #20

works perfectly. My apolagies, didnt see the issue in the closed tab


Issues when cloning in a path with whitespaces

Hi,
I've run into troubles with installing / running wdlTools from a path with whitespaces.
First, ROOT_DIR was not set in the Makefile when trying to make on my MacOS system; It would set it to "".
I've replaced ROOT_DIR:=$(shell dirname $(realpath $(firstword $(MAKEFILE_LIST)))) with ROOT_DIR=$(shell pwd) and it worked.
Second, almost all tests failed with java.io.FileNotFoundException: Path does not exist
At this point, I decided to clone wdlTools elsewhere.
Cheers,
Laurent

I think the complex command is used in the case where you run make /path/to/makefile from a directory other than the one that contains the Makefile. It is a known issue that command doesn't handle paths with spaces. I think it's a reasonable restriction to say make must be run from the project folder, so I will update the build script with your change.


Unexpected "update" history entry after doing a revert

I'm getting an unexpected update at the history after upgrading and reverting. This is the sequence I've used:
$ ./prospero update perform --dir=/tmp/wildfly-prospero/
Updates found:
  [*]io.smallrye:jandex                                    3.0.5                ==>  3.0.3
  [*]jakarta.activation:jakarta.activation-api             2.1.1                ==>  2.1.0
  [*]jakarta.mail:jakarta.mail-api                         2.1.1                ==>  2.1.0

[*] The update list contain one or more artifacts with lower versions then currently installed. Proceed with caution.

Continue with update [y/N]: y
Applying updates
Feature-packs resolved.
Packages installed. 100%
JBoss modules installed. 100%
Configurations generated.

Conflicting changes detected in the update:

Update complete!
Operation completed in 58.03 seconds.

$ ./prospero history --dir=/tmp/wildfly-prospero
[d1d24f6a] 2023-01-26T11:57:39Z - update
[c18672ec] 2023-01-26T11:49:12Z - install

$ ./prospero history --dir=/tmp/wildfly-prospero --revision=c18672ec
Updates:
  [Updated artifact] jakarta.mail:jakarta.mail-api:     2.1.1 ==> 2.1.0
  [Updated artifact] jakarta.activation:jakarta.activation-api:     2.1.1 ==> 2.1.0
  [Updated artifact] io.smallrye:jandex:        3.0.5 ==> 3.0.3

$ ./prospero revert perform --dir=/tmp/wildfly-prospero --revision=c18672ec
Feature-packs resolved.
Packages installed. 100%
JBoss modules installed. 100%
Configurations generated.

$ ./prospero history --dir=/tmp/wildfly-prospero
[cb68e947] 2023-01-26T12:00:20Z - update
[e26eb3e7] 2023-01-26T11:59:25Z - rollback
[d1d24f6a] 2023-01-26T11:57:39Z - update
[c18672ec] 2023-01-26T11:49:12Z - install

$ ./prospero history --dir=/tmp/wildfly-prospero --revision=e26eb3e7
No changes found

$ ./prospero history --dir=/tmp/wildfly-prospero --revision=cb68e947
No changes found

$ ./prospero history --dir=/tmp/wildfly-prospero --revision=d1d24f6a
Updates:
  [Updated artifact] jakarta.mail:jakarta.mail-api:        2.1.0 ==> 2.1.1
  [Updated artifact] jakarta.activation:jakarta.activation-api:        2.1.0 ==> 2.1.1
  [Updated artifact] io.smallrye:jandex:        3.0.3 ==> 3.0.5

The cb68e947 hash is unexpected. In addition, the output generated when printing the Updates needs a minimal tweak giving more space for the G:A section.

Some additional information, it looks like the rollback entry is created by the prepare-revert operation and the update is created by the apply-revert. Having a history entry due to a prepare-revert is also unexpected to me.


Memory of remaining live for monsters

Hi,
I am just wonder. It is possible to make a monstrum, move him away from board and later summon that same monstrum with the same number of remaining lives? Exactly the same thing is in original scenario Escape from Innsmouth. I hope you understand me.
Please, every single advice or idea will be welcome.

I believe this functionality is already scheduled for Later
https://github.com/NPBruce/valkyrie/issues/594

You might want to have a look at my scenario 'In the Dark'.
A big monster is removed from the board but (because Valkyrie does support keeping the lives) I have to leave it visible in the monster tray.
Most players don't mind as they just ignore it in the Horror Check stage.

Great! Thank you very much. The idea about ignoring monster by player is the most easy way. It is not perfect but the most of players using Valkyria will have no problem with that. In my next scenario I will need it ;-)


"Filename too long" Error in github action

What Happened?
Got a "Filename too long" error in github action
Checking out the ref
  /usr/bin/git checkout --progress --force -B main refs/remotes/origin/main
  Error: error: unable to create file pages/<a 160 chars chinese here>.org: File name too long

Reproduce the Bug
submit a file with long filename to your repo.
Expected Behavior
No response
Desktop or Mobile Platform Information
No response

Hi. This github action relies on git for versioning. If your graph is unable to work with git then unfortunately it won't work for this action. I'm happy to make this more explicit in the readme if that helps

Closing as I haven't heard back on improving documentation


GPU NOT FOUND

it was not able to find my "NVIDIA Quadro RTX 5000 with Max-Q Design" in my windows 11, can anyone help me?

I will add this card to whitelist in the next version.


Add endpoint argument to web-service test

The default behavior is to automatically start up a server locally.

@mmocny

Hey, looks really good!  Do you have access to merge yourself?

I don't think I do yet.

I don't think I do yet.

You now have the permissions.

Cool, thanks.


⚠ Secret Website 2 has degraded performance

In 1e76c95, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 4508 ms

Resolved: Secret Website 2 performance has improved in 17c51ba.


[graphql] Name a few more quries to improve datadog representation.

Related to https://github.com/artsy/metaphysics/pull/1225

👍 cooool!


Outlook Connection/Redirection Error

Hello, and thank you for producing such a great tool.
Upon trying to open Outlook, I am presented with a page that says "Use the following link to open this mailbox with the best performance:"
Upon clicking the link provided, the connection times out.
I have previously been able to open Outlook in prior testing of other accounts. I am also able to access the rest of the tools without issue, changing access tokens and Client IDs as required.
How should I go about accessing Outlook in browser? Or if not possible with the account I am currently testing, would a custom Graph request to dump inbox be my alternative solution?
Thank you and I look forward to hearing back.

Absolutely, and thank you for getting back to me.
The link is as follows<EMAIL_ADDRESS>Then it redirects for a long while before ultimately closing the connection.

I think you are right. It appears to be on-premises and RESTAPI is not enabled
When I run the custom request (with the required access token and scopes), I get the following response
 {
    "error": {
        "code": "MailboxNotEnabledForRESTAPI",
        "message": "The mailbox is either inactive, soft-deleted, or is hosted on-premise."
    }
}

What would you advise?

I truly appreciate this guidance.
The outlook issue where the mailbox link never connects is quite confusing, considering that I am redirected to pages like "https://mail.example.com/owa/", and that several tokens I can produce have permissions like "EAS.AccessAsUser.All", "Ews.AccessAsUser.All", and "OWA.AccessAsUser.All"
Based on this combination of factors, I can imagine the cause of the connection problem being something else, not being hosted on-prem. Do you have any ideas?
One more question if you don't mind. For MFA methods, Graphspy provides the following error message:
"[Error] Failed to obtain Available Authentication Info."
I am using the correct resource (MicrosoftAppAccessPanel)
Thank you and I will see what I can do ;)

Interesting. When I get the access token with the exact correct audience, the decoded token does not display "mfa" under amr.
It instead displays:
"amr": [
        "pwd"
    ],

The stack trace generated is:
[get_available_authentication_info():494] ERROR: Failed to obtain AvailableAuthenticationInfo. Received status code 401
Would requesting an ngcmfa claim produce a different result?
(I know the documentation discusses ngcmfa being necessary for FIDO keys, but any mfa would be sufficient.)
On the note of the possibility that the on-prem exchange server is being decommissioned, I can with certainty that I know the website is in existence and operating.
My current theory on my inability to access is geoblocking (based on my current location, the requested device login location, and/or the user recipient location, or VPN usage.
For illustration, user recipient is in country A, the device code request was for country B, and I am (currently, but not for long) in country C.


Restore pdflatex compatibility

Compiling currently fails with pdflatex with error Encoding scheme "TU" unknown. (see e.g. aside in issue #23 about compiling with xetex).
This is because the academicons package, required for the "awesome" icons doesn't support pdflatex and doesn't seem very likely to.
This PR adds a compiler switch to the CV styles using the "awesome" icons to fallback to "marvosym" if compiling with neither Xe(La)TeX nor Lua(La)TeX (the compilers supported by academicons).
As for documenting/noting, etc., that is not addressed here, but either a print-out warning about falling back or adding comments / flags to the template file (or documentation) may be in order.

I had to update the build-pdf.yml to add apt update since we were otherwise having errors finding all the packages. This makes sense as a permanent change.

I had to update the build-pdf.yml to add apt update since we were otherwise having errors finding all the packages. This makes sense as a permanent change.

Oh I completely forgot to do that, thanks a lot!

Oh I completely forgot to do that, thanks a lot!


odim 523:Updating the completed task index for the task which is having  task state as  Exception

closing the pr raised on the wrong base branch


Copilot chat error

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Even though I logged in with my Copilot account it is asking to start 30-day free trial
Inline suggestions are working but chat is not working

This just happened to me as well after I updated VS Code to v1.86. I had to rollback to v1.85 to fix it.
Here is how to rollback:

Quit VS Code.
Install VS Code v1.85. Download it here.
Open VS Code. Go to Code -> About Visual Studio Code to make sure your version is 1.85.x.
Uninstall the GitHub Copilot Chat extension.
Reinstall the GitHub Copilot Chat extension.
Reload VS Code.

Hello @sephraim  I tried your suggestions but I still can't get it to work. Are there any additional suggestions you can kindly furnish me with?
Many thanks in advance

You could any try the following:

First, go to Code -> About Visual Studio Code and make sure your VS Code version is 1.85.x.
Next: Reload VS Code by running: Cmd+P (or Ctrl+P) -> Developer: Reload Window
Still not working? Try uninstalling / reinstalling both the GitHub Copilot and the GitHub Copilot Chat extensions. Make sure to Cmd+P (or Ctrl+P) -> Developer: Reload Window after reinstalling the extensions.
Still not working? Try installing a previous version of the GitHub Copilot extension (see GIF below for how to do that). Make sure to Cmd+P (or Ctrl+P) -> Developer: Reload Window after reinstalling the extension.
Still not working? Try installing a previous version of the GitHub Copilot Chat extension (see GIF below for how to do that). Make sure to Cmd+P (or Ctrl+P) -> Developer: Reload Window after reinstalling the extension.

Image source
Hope that helps!

Okay, so I rolled back to v0.11.0 which is from a month or two ago and it worked (GitHub Copilot Chat). Many thanks lads

This issue is caused by VS Code not properly supporting multiple auth sessions. Not much can be done on the extension side until VS Code fixes this. It was a bug that this worked before
Ref:
microsoft/vscode#203850
microsoft/vscode#127967

I can confirm that GitHub Copilot Chat v0.11.1 works fine with VS Code v1.86.2. However, GitHub Copilot Chat v0.12.0 / v0.12.1 / 0.12.2 all give the "30-day free trial" error.


Is there any way to convert property names of json data to lower case in JSON output

If you know the headers just simply specify them in headers parameter.
If you do not know, then you can change the json object in .subscribe callback

Thanks. I don't think headers property will work for my case because what I want is to do case insensitive comparison between file header names and master headers list available in database. if it is matching then JSON object property should have property as it is available in database, not what is there in file.


Traffic Ops riak.conf: Accept a list of TLS versions to enable

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue.

This PR updates the Traffic Ops config for communicating with Riak to accept a "TLSVersions" array instead of the single "MaxTLSVersion" value that #4573 added.It leaves TLS 1.1 as the default enabled version for communicating with Riak.
Motivations for the config option name change
After #4573 was merged, some concerns were brought up about the fact that, even though the config option was named MaxTLSVersion, versions below MaxTLSVersion but greater than or equal to the default TLS minimum version were not tried. So the question became whether MaxTLSVersion was an accurate name for that config option. TLSVersions is more straightforward.
Reasons for checking for a list of versions

Without any additional config changes after #4573, Traffic Vaults that have TLS 1.0 and TLS 1.2 enabled but not TLS 1.1 are effectively unreachable by Traffic Ops. While we should still leave it up to our users as far as what TLS versions they want to enable, Traffic Ops should not be limited to either succeeding with 1 specific TLS version or failing to reach Traffic Vault.
Even though Go 1.14.2 uses TLS 1.3 by default, its default tls.Config.MinVersion is TLS 1.0, so the fact that basho/riak-go-client doesn't attempt handshakes with TLS versions lower than the maximum version is a bug.

Which Traffic Control components are affected by this PR?

CDN in a Box
Documentation
Traffic Ops

What is the best way to verify this PR?

Run Traffic Ops unit tests
Run Traffic Ops API tests to check for regressions
Start CDN-in-a-Box, verify that Traffic Ops stores TLS keys in Traffic Vault
Build docs, verify there are no warnings but also make sure they look nice

If this is a bug fix, what versions of Traffic Control are affected?

master (764aaf0abb)

The following criteria are ALL met by this PR

[x] This PR includes tests
[x] This PR includes documentation
[x] This PR includes an update to CHANGELOG.md
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Let's not enable TLS 1.0 by default. Removed TLS 1.0 from the default enabled TLS versions for Traffic Ops to try in 4342d18d2.

Let's not


[WIP] MaaS Horizon Site Name Check

This commit fixes a bug in the horizon_check.py plugin for MaaS.
Previously in the horizon check plugin it would search for the
horizon site name using a hardcoded value. This causes the
MaaS check to fail if the horizon site name is overridden in
the user variables file.
This is fixed setting the default value for horizon_site_name
in the rpc_maas main.yml that will get overridden if
horizon_site_name is set in user variables. That value is
passed to the horizon check plugin through the
horizon_local_check.yaml.j2 template and used by the horizon
check plugin as an argument for site name regex search.
 The idea right now is to set the default in the main.yml for rpc_maas so that if it is set elsewhere it should override the default in rpc_maas and be passed as an argument to the horizon maas plugin.
[1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L48
[2] https://github.com/openstack/openstack-ansible-os_horizon/blob/7a0b2665fea077428d9c61cb2c01e080525e9c6a/templates/horizon_local_settings.py.j2#L719-L721

We noticed the the wrapper script, run_plugins_in_venv.sh, invokes the plugins with the bash arguments not delimited with quotes. This could cause issues with multi-word bash arguments. The solution here was to use $@ with double quotes like so:
python2.7 "$@". We are going to go ahead and include that in this patch.

We are going to go ahead and include that in this patch.

No. That should be a separate bug and a separate pull request which blocks this one.

This is being blocked by PR #1259

This is ready for review.

I wonder if we need a release note outlining the addition of the new argument in the horizon_check.py plugin. IMO it'll definitely be worth mentioning it somewhere. Also I believe the documentation needs updating[1]
[1] https://github.com/rcbops/rpc-openstack/tree/master/maas/plugins#horizon_checkpy

Not tested but the wiring seems ok for me.
Wondering if a weird name in the horizon_site_name containing a valid regexp will cause failures, because it's not escaped. It's probably fine 'though.

Tested - works.
Ready to merge, pending gate checks.

RPC-AIO-Ceph-Liberty-PR: Fail

Added a release note to the PR

RPC-AIO-Liberty-PR: Fail

@mancdaz - feel free to merge if you're satisfied with the change.
Although if we're having gating issues re: MaaS this probably won't pass gate just yet.

gonna merge - has 2 +1's and @mancdaz's concern has been addressed.


Roll engine 12bf95fd49b7..49d6552e76c0 (16 commits)

https://github.com/flutter/engine/compare/12bf95fd49b7...49d6552e76c0
git log 12bf95fd49b7..49d6552e76c0 --first-parent --oneline
2019-12-11<EMAIL_ADDRESS>Verify accounting for loop counts in Gif and WebP assets is consistent. (flutter/engine#14321)
2019-12-11<EMAIL_ADDRESS>[fuchsia] Do not Execute paint tasks when there is no vsync (flutter/engine#14298)
2019-12-11<EMAIL_ADDRESS>Roll src/third_party/dart c74a8ec2c46e..bcd18e67dcae (9 commits) (flutter/engine#14317)
2019-12-11<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from nqJnP... to UdfLO... (flutter/engine#14316)
2019-12-11<EMAIL_ADDRESS>Roll src/third_party/skia 732c49739fa5..5afc7b2af854 (16 commits) (flutter/engine#14315)
2019-12-11<EMAIL_ADDRESS>Roll fuchsia/sdk/core/mac-amd64 from 9C6UA... to h4iiT... (flutter/engine#14314)
2019-12-11<EMAIL_ADDRESS>[web] Update build_web_compilers to 2.7.1 (flutter/engine#14305)
2019-12-11<EMAIL_ADDRESS>Cleanup the IO thread GrContext (flutter/engine#14265)
2019-12-10<EMAIL_ADDRESS>Fix for tab not working (flutter/engine#14165)
2019-12-10<EMAIL_ADDRESS>[SkParagraph] Convert the height override flag in text styles (flutter/engine#14283)
2019-12-10<EMAIL_ADDRESS>Roll src/third_party/dart 02a8b015ad..98c13ba18f (5 commits) (flutter/engine#14280)
2019-12-10<EMAIL_ADDRESS>Remove specificity on Android and iOS (flutter/engine#14282)
2019-12-10<EMAIL_ADDRESS>Create separate objects for isolate state and isolate group state (flutter/engine#14268)
2019-12-10<EMAIL_ADDRESS>Roll src/third_party/dart 8b8894648f..02a8b015ad (26 commits) (flutter/engine#14278)
2019-12-10<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from Zkpa_... to nqJnP... (flutter/engine#14274)
2019-12-10<EMAIL_ADDRESS>Roll src/third_party/skia e56cc054dbae..ab26643258ad (3 commits) (flutter/engine#14273)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://github.com/flutter/flutter/runs/343299264 , https://github.com/flutter/flutter/runs/343299258 , https://github.com/flutter/flutter/runs/343299251 , https://github.com/flutter/flutter/runs/343299247 , https://github.com/flutter/flutter/runs/343299240 , https://github.com/flutter/flutter/runs/343299218 , https://github.com/flutter/flutter/runs/343299204 , https://github.com/flutter/flutter/runs/343299197

Commit queue failed; closing this roll.


config.logs.enabled=true when config.jobs.deploy-k8s-false is broken

Using the following config file:
(note logs.enabled=true and jobs.deploy-k8s=false)
workertags:
  caasp4: suse-internal

jobs:
  deploy-k8s: false
  deploy-kubecf: true
  smoke-tests: true
  cf-acceptance-tests-brain: false
  sync-integration-tests: false
  minibroker-integration-tests: false
  cf-acceptance-tests: false
  upgrade-kubecf: false
  deploy-stratos: false
  destroy-kubecf: true
jobs_ordered:
- deploy-k8s
- deploy-kubecf
- smoke-tests
- cf-acceptance-tests-brain
- sync-integration-tests
- minibroker-integration-tests
- cf-acceptance-tests
- upgrade-kubecf
- deploy-stratos
- destroy-kubecf
backends:
  caasp4: true
  aks: false
  gke: false
  eks: false
availabilities:
  sa: true
  ha: false
  all: false
schedulers:
  diego: true
  eirini: false
catapult:
  uri: https://github.com/SUSE/catapult
  branch: master
brain:
  verbose: false
  inorder: false
  include: ""
  exclude: ""
cats:
  nodes: 3
  flake-attempts: 5
  timeout-scale: "3.0"
s3minibroker:
  bucket: minibroker-helm-charts
  region: us-east-1
  regexp: minibroker-charts/minibroker-(.*).tgz
s3:
  bucket: kubecf
  region: us-west-2
  regexp: kubecf-bundle-v(.*).tgz
# Scheduling is required for nightly builds, enabling it removes regular trigger on kubecf bundle.
schedule:
  enabled: false
  start: 12:00 AM
  stop: 12:10 AM
  location: America/Vancouver
logs:
  enabled: true

Gives me:
apply configuration? [yN]: y
error: invalid pipeline config:
invalid resources:
        resource 's3.klog-destination' is not used

This is happening because the klog script is only called inside the destroy-k8s task: https://github.com/SUSE/cap/blob/515c930fd6e235099fd1feef1fa62bbed733496b/cap-ci/common/destroy_k8s.tmpl#L40-L52
Yet (rightly) the definition of the resource has nothing to do with destroy_k8s:
https://github.com/SUSE/cap/blob/515c930fd6e235099fd1feef1fa62bbed733496b/cap-ci/pipeline.yaml.tmpl#L88-L98
Possible solutions:

IMHO, the correct solution would be to create another task klog analogous to destroy_k8s, that is run on_failure if enabled. This means calling a common_klog just before all common_destroy_k8s, if klog is enabled. Gave a kick try in https://github.com/SUSE/cap/compare/viccuad/fix-klogs-destroy, but fails so far. See commit messages.

A cheap, spaghetti solution would be: (pseudocode) {{- if ($config.logs.enabled or $jobs.deploy-k8s == false) }} in https://github.com/suse/cap/blob/master/cap-ci/pipeline.yaml.tmpl#L88

There is a fundamental issue of design here. klog should not be part of destroy k8s job (aka destroy-kubecf flag) https://jira.suse.com/browse/CAP-1564


Ldap Auth.  IdentityServer4.LdapExtension

https://github.com/Nordes/IdentityServer4.LdapExtension add proje Ldap

Hi @murattdogan - thanks for tip - I will check it later - same issue is here: #521


How to install?

Thanks for your interest in the project. I haven't officially launched the download page yet. When I do it'll be available on itch.io here:
https://craftworkgames.itch.io/sprite-factory
However, I am looking for early beta testers, if you'd like a download key let me know how I can send you a private message and I'll send you one.


Weekly and Monthly Pattern with time zone not working.

I created a monthly event with PST timezone. And my local system have IST time zone when I apply the rule. It's not giving the right date.
For eg:
Time.zone = "America/Vancouver"
pst_time = Time.zone.parse("201601082000000") # -08:00
#> Fri, 08 Jan 2016 20:00:00 PST -08:00
s = IceCube::Schedule.new(pst_time)
s.add_recurrence_rule IceCube::Rule.monthly.day_of_month(9).count(10) #every month 9th
s.next_occurrences(2)
#> [Tue, 09 Feb 2016 20:00:00 PST -08:00, Wed, 09 Mar 2016 20:00:00 PST -08:00]
s.start_time = Time.now # 2016-01-22 01:17:20 +0530
s.next_occurrences(2)
=> [2016-02-09 01:18:01 +0530, 2016-03-09 01:18:01 +0530]

RRULE: FREQ=MONTHLY;INTERVAL=1;BYMONTHDAY=9;COUNT=10
Start Time: 2016-02-08 22:00:00 UTC
End Time: 2016-02-08 23:00:00 UTC

System Time Zone was in EST. It should give.

Start Time: 2016-02-08 17:00:00 EST
End Time: 2016-02-08 18:00:00 EST

But it’s giving

Start Time: 2016-02-09 17:00:00 EST
End Time: 2016-02-09 18:00:00 EST

apply_ical= "DTSTART;TZID=PST:20160108T200000\nRRULE:FREQ=MONTHLY;BYMONTHDAY=9;COUNT=10"
s = IceCube::Schedule.from_ical(apply_ical)
s.next_occurrence(2)
# => [2016-02-09 20:00:00 +0530, 2016-03-09 20:00:00 +0530]

When we convert the rule into IST it should give 10th of every month. As IST ahead of +05:30.
did I miss something to convert the timezone for the rule. Are this is the way it works??

When you change the start time, the rules are not changed. It still uses the 9th day of the month if you lock that in with day_of_month. Try like this:
pst_tz = ActiveSupport::TimeZone['America/Vancouver']
ist_tz = ActiveSupport::TimeZone['Asia/Kolkata']
pst_time = pst_tz.parse("201601092000000") # -08:00
ist_time = pst_time.in_time_zone(ist_tz)

schedule = IceCube::Schedule.new(pst_time) do |s|
  s.rrule IceCube::Rule.monthly.count(10)
end
schedule.next_occurrences(2)
#=> [Tue, 09 Feb 2016 20:00:00 PST -08:00, Wed, 09 Mar 2016 20:00:00 PST -08:00]

schedule.start_time = ist_time
schedule.next_occurrences(2)
#=> [Wed, 10 Feb 2016 09:30:00 IST +05:30, Thu, 10 Mar 2016 09:30:00 IST +05:30]


chore(benchmarks/jsx): Update benchmark

Update the compared libraries to the latest version
Add a benchmark script when using "react-jsx"
Additional targets for bundle size comparison

Result
% npm run bench:node

><EMAIL_ADDRESS>bench:node
> esbuild --bundle src/benchmark.ts | node

Hono x 437,736 ops/sec ±0.25% (95 runs sampled)
React x 56,216 ops/sec ±1.09% (99 runs sampled)
Preact x 266,304 ops/sec ±0.21% (98 runs sampled)
Nano x 60,715 ops/sec ±0.21% (98 runs sampled)
Fastest is Hono

% npm run bench:bun

><EMAIL_ADDRESS>bench:bun
> bun run src/benchmark.ts

Hono x 390,353 ops/sec ±0.44% (97 runs sampled)
React x 45,185 ops/sec ±0.29% (98 runs sampled)
Preact x 257,160 ops/sec ±1.51% (96 runs sampled)
Nano x 57,867 ops/sec ±3.02% (95 runs sampled)
Fastest is Hono

% npm run bench:react-jsx:node

><EMAIL_ADDRESS>bench:react-jsx:node
> esbuild --bundle src/react-jsx/benchmark.ts | node

Hono x 341,062 ops/sec ±0.45% (99 runs sampled)
React x 55,241 ops/sec ±0.47% (100 runs sampled)
Preact x 287,187 ops/sec ±0.27% (94 runs sampled)
Nano x 54,391 ops/sec ±0.37% (95 runs sampled)
Fastest is Hono

% npm run compare-bundle-size

><EMAIL_ADDRESS>compare-bundle-size
> esbuild --minify --minify-syntax --tree-shaking=true --bundle src/{hono,react,preact,nano}.ts --outdir=dist

  dist/react.js   76.9kb
  dist/nano.js    35.3kb
  dist/preact.js  15.3kb
  dist/hono.js     3.4kb

⚡ Done in 41ms

Analysis
It might be possible to optimize a bit more for the "react-jsx" case, but that is a topic for another PR. (It just seems to be quite difficult)

@usualoma
Cool! I also ran the benchmarks in my machine and results are same. Hono's JSX is really fastest and smallest!
I've left a comment, please check it.


[FLINK-10179] [Startup Shell Scripts] .bat script to start Flink history server

Flink history server started after historyserver.archive.fs.dir key is configured.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@zentol are you still on Windows?

yes, I'm still using windows.
I believe we should have a larger discussions as to how powerful the windows scripts should be, and whether we want to look into a solution where we can share more between unix/windows. This (and related) PRs are effectively duplicating existing scripts.
This poses a maintenance problem both for keeping them in sync and ensuring that they actually work. We don't have windows CI, and I'd rather not have us rely on me (since no(?) other committer works on Windows) going through every single script each release.

The Flink developers have decided that we don't want to extend windows script support for now: https://lists.apache.org/thread.html/r7693d0c06ac5ced9a34597c662bcf37b34ef8e799c32cc0edee373b2%40<dev.flink.apache.org>. I'm very sorry because you already invested time in this.


Break in new stable channel 1.17.0

Describe the bug
I try to launch flutter in new stable Chanel
To Reproduce
just build
and get error
 Compiler message: ../../../Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/get-2.0.6/lib/src/snackbar/snack_route.dart:279:8: Error: The method 'SnackRoute.install' has more required arguments than those of overridden method 'OverlayRoute.install'.   void install(OverlayEntry insertionPoint) {        ^ ../../../Downloads/flutter/packages/flutter/lib/src/widgets/routes.dart:41:8: Context: This is the overridden method ('install').   void install() {        ^ ../../../Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/get-2.0.6/lib/src/routes/default_route.dart:242:9: Error: No named parameter with the name 'animation'.         animation: animation,         ^^^^^^^^^ ../../../Downloads/flutter/packages/flutter/lib/src/cupertino/route.dart:435:3: Context: Found this candidate, but the arguments don't match.   CupertinoFullscreenDialogTransition({   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../../../Downloads/flutter/.pub-cache/hosted/pub.dartlang.org/get-2.0.6/lib/src/snackbar/snack_route.dart:289:18: Error: Too many positional arguments: 0 allowed, but 1 found. Try removing the extra positional arguments.     super.install(insertionPoint);
Flutter Version:
1.17.0
Get Version:
2.0.6
Describe on which device you found the bug:
ex: Oppo k3 - Android.

Wow! Finally version 1.17 became stable, I couldn't take any more workround to listen to dialogs because the previous version didn't even have the RouteSettings property.
I will do the update now, but you can use the version
get: ^2.0.9-dev
Thanks for notifying me!

Great !! work on 2.0.9-dev

Solve in 2.0.10


Update to 1.20

I've already updated the mod in my fork and tested it and it works properly
https://github.com/Ryhon0/Replanter/tree/fabric1.20

Hi, I created a GitHub account just to ask this question.
I'm a total noob at coding and modding, so how do I make the .jar file out of this?
That or do you have a download link somewhere I could use? Thanks!

It doesn't look like the owner of this project is interested in it anymore so I'm working on my own fork that adds 1.20 support and hopefully more features. It's available on https://github.com/Ryhon0/ReplanterPlus
and on Modrinth once it gets approved https://modrinth.com/mod/replanter-plus

Awesome!
-------- Original Message --------
On Jul 29, 2023, 2:51 AM, Ryhon wrote:

It doesn't look like the owner of this project is interested in it anymore so I'm working on my own fork that adds 1.20 support and hopefully more features. It's available on https://github.com/Ryhon0/ReplanterPlus
and on Modrinth once it gets approved https://modrinth.com/mod/replanter-plus
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Better split

Breaking change!
VelenCommand#getShortcuts() now returns a String[] so it doesn't get changed later.
The command parsing alg is reworked to be more readable.
The args get parsed more intelligent with respect to escapes and double qoutes.

I also added a new util method to allow named arguments like:

I wonder if it would be better to make this a non-breaking change for now by adding the original methods but with a deprecated annotation instead unless I am missing a point here over "so it doesn't get changed later."? 🤔

Lists can change their length, so returning an array is better, because it shouldn't change.

I see, is this ready to go or do you want to add more since I will be pushing it to the master branch to place it on its own version?

Its ready to go

Thanks for the PR, then! 🧇


Event Endpoints and General Fixes && Improvements

Also, I want to alphabetically sort classes in models.py and serializers.py (according to dependency situation obviously) if it's ok? @cerob

Of course it's something we should do as early as possible


Rationalise ratelimit exemption rules.

Make it clearer as to what the rule does. See:

https://github.com/alphagov/govuk-aws-data/pull/1276

/me regenerates the docs again 🙃


T265 Viewer not working on Windows, Mac and Linux

The Intel T265 doesn't show up in any of the three system platforms. I compiled from source the librealsense library 2.19 both in Linux and Mac, and in both  cases, the viewer doesn't detect the device. The enumerate-device tool doesn't detect it either. In Windows 10 10 (1809), I downloaded the exe of the viewer and it has exactly the same problem.
On Linux, I can see the device being connected when running dmesg:
[943971.513902] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[943971.662609] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150
[943971.662613] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[943971.662616] usb 3-1: Product: Movidius MA2X5X
[943971.662619] usb 3-1: Manufacturer: Movidius Ltd.
[943971.662621] usb 3-1: SerialNumber: 03e72150
[944430.562800] usb 3-1: USB disconnect, device number 5
[944438.461932] usb 5-2: new high-speed USB device number 2 using xhci_hcd
[944438.678518] usb 5-2: New USB device found, idVendor=03e7, idProduct=2150
[944438.678522] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[944438.678525] usb 5-2: Product: Movidius MA2X5X
[944438.678528] usb 5-2: Manufacturer: Movidius Ltd.
[944438.678530] usb 5-2: SerialNumber: 03e72150

but again, no device is actually detected by the Intel software tools, not even when running with sudo.
Any insights or ideas of why it doesn't work in any of these platforms?

Related to #3361. I was able to get the T265 to work by plugging in and running the rs-pose example: https://github.com/IntelRealSense/librealsense/issues/3361#issuecomment-470978666. The API should work.

@hbadino Are you using a hub to connect the T265? We have had some users tell us that some models of USB3 hub prevent the T265 from working properly. If so, you might want to try again after connecting the device directly to your computer.

@harville, thanks for the reply. No, I'm using no hubs.
@antmusco, thanks as well. I was aware of that post, it doesn't solve my problem. In fact, I have three OS versions on three different machines and none of them work.

I have a similar issue.   https://forums.intel.com/s/question/0D50P00004GB93ASAT/t265-is-recognized-as-movidius-ma2x5x-and-not-as-a-realsense-camera.  I have two T265 they both behave the same.

Could you verify cmake contains BUILD_WITH_TM2=ON and you run it with connection to the Internet (e.g. with the correct proxy configuration) ? That solved https://github.com/IntelRealSense/librealsense/issues/3384 .

Could you verify cmake contains BUILD_WITH_TM2=ON and you run it with connection to the Internet (e.g. with the correct proxy configuration) ? That solved #3384 .

I confirm it was configured and build with BUILD_WITH_TM2=ON and with connection to Internet.

I have a similar issue running Viewer binary but what the different thing is that my Realsense camera cannot stop showing Connected and Disconnected intermittedly. The log is as follows:
22/03 15:16:57,206 INFO [23692] (tm-context.cpp:77) TM2 Device Detached
22/03 15:16:57,224 DEBUG [21272] (frame-archive.h:147) CallbackFinished,Gyro,198,DispatchedAt,1553293017225.026855
22/03 15:16:57,224 DEBUG [21272] (frame-archive.h:154) Frame Callback [Gyro#198] overdue. (Duration: 782.405762ms, FPS: 200, Max Duration: 4ms)
22/03 15:16:57,224 DEBUG [21272] (frame-archive.h:147) CallbackFinished,Accel,65,DispatchedAt,1553293017225.081299
22/03 15:16:57,224 DEBUG [21272] (frame-archive.h:154) Frame Callback [Accel#65] overdue. (Duration: 780.465820ms, FPS: 62, Max Duration: 15ms)
22/03 15:16:57,224 INFO [21272] (win-helpers.cpp:85) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorCollection) returned: HResult 0x80070490: "Element not found."
22/03 15:16:57,823 INFO [23692] (tm-context.cpp:71) TM2 Device Attached - 000001BA5833ADB0
22/03 15:20:47,992 INFO [21272] (rs.cpp:2109) Framebuffer size changed to 0 x 0
22/03 15:20:47,992 INFO [21272] (rs.cpp:2109) Window size changed to 0 x 0
22/03 15:23:02,437 INFO [21272] (rs.cpp:2109) Framebuffer size changed to 2560 x 1377
22/03 15:23:02,439 INFO [21272] (rs.cpp:2109) Window size changed to 2560 x 1377
22/03 15:23:03,059 INFO [21272] (rs.cpp:2109) Framebuffer size changed to 0 x 0
22/03 15:23:03,059 INFO [21272] (rs.cpp:2109) Window size changed to 0 x 0
22/03 15:23:21,373 INFO [21272] (rs.cpp:2109) Framebuffer size changed to 2560 x 1377
22/03 15:23:21,373 INFO [21272] (rs.cpp:2109) Window size changed to 2560 x 1377
Its Firmware version <IP_ADDRESS>29.

@hbadino, We have released an updated librealsense 2.19.2, please give this newer version a try on your system.  Support for T265 is Linux and Windows 10.
Can you also outline what type of platform, CPU, etc that you are using.

@hbadino hello,
Do you need more assistance with this one ?

No, the latest version fixed the issues. Thanks.
On Thu, Apr 18, 2019, 8:21 AM ev-mp<EMAIL_ADDRESS>wrote:

@hbadino https://github.com/hbadino hello,
Do you need more assistance with this one ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/3436#issuecomment-484371556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2BHTXOIB3BI4D2FD7FX4LPRAHNZANCNFSM4G4YTKWQ
.

Thanks for confirming, closing it now.

Seeing the exact same error in 2013 with the lates v2.54 version of the RealSense ADK. This is my dmesg log:
[  522.314602] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0/input/input34
[  522.314684] usbcore: registered new interface driver uvcvideo
[  577.814598] usb 3-1: new high-speed USB device number 7 using xhci_hcd
[  577.963883] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150, bcdDevice= 0.01
[  577.963886] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  577.963888] usb 3-1: Product: Movidius MA2X5X
[  577.963888] usb 3-1: Manufacturer: Movidius Ltd.
[  577.963889] usb 3-1: SerialNumber: 03e72150

Why is this still happening? It seems to be misidentifying the device.

Seeing the exact same error in 2013 with the latest v2.54 version of the RealSense ADK. This is my dmesg log:
[  522.314602] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0/input/input34
[  522.314684] usbcore: registered new interface driver uvcvideo
[  577.814598] usb 3-1: new high-speed USB device number 7 using xhci_hcd
[  577.963883] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150, bcdDevice= 0.01
[  577.963886] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  577.963888] usb 3-1: Product: Movidius MA2X5X
[  577.963888] usb 3-1: Manufacturer: Movidius Ltd.
[  577.963889] usb 3-1: SerialNumber: 03e72150

Why is this still happening? It seems to be misidentifying the device.
EDIT: Nevermind, it appears they just removed support for T265 and L535 in v2.54: "Removed deprecated camera PIDs, such as T265, L535"

did you solve this problem on another version of SDK?


just --fmt: includes are injected instead of formatted

Taking the example from the README
# justfile
!include justfile.inc

a: b
  @echo A

# justfile.inc
b:
  @echo B

executing the formatter as
just --fmt --unstable --justfile justfile

will update the justfile and insert the content of the included file:
# justfile

# justfile.inc
b:
    @echo B

a: b
    @echo A

which is unexpected. I think this should format the included file instead and keep the include statement.

Looks like a duplicate of #1585


Make it clear that Astro Actions (no JS only) are limited by the size of the browsers cookies

📚 Subject area/topic
Actions
📋 Page(s) affected (or suggested, for new content)
https://docs.astro.build/en/guides/actions/
📋 Description of content that is out-of-date or incorrect
Astro actions, when using form actions i.e. no JavaScript, appear to use cookies to store the payload returned by the action.
This works but cookies have a size limit that is set by the browser of ~4kb. This means that if you have a large response (in my case an LLM transcription) the request is successful but no data is available on the client, with no obvious reason why.
This is likely a niche scenario but it's taken me hours to debug, can it please be made clear that actions use cookies and that they shouldn't be used for large responses?
🖥 Reproduction in StackBlitz (if reporting incorrect content or code samples)
No response

Hi, thank you for reporting this! I'll tag @bholmesdev in here for comment because docs always documents expected, intended behavior and maybe this isn't intended, or maybe there's an alternative we should be documenting, or maybe this means we need some error handling in the code... or maybe there's some work around entirely at the code level.
Ben, what action would you suggest docs take here?

Thanks for flagging! We do have a warning in the docs that cookies are used, but we should definitely call out the size limit as well. Still, I think an error message in development would be far more helpful than a docs note you have to find. I think we can check the serialized payload size to catch these cases early. I'll make a note for core about this.

Hi @bholmesdev. I actually missed the warning about using cookies in the docs the first time I looked at it. So the error message in development definitely feels like the best solution! If you're happy for me to take a look at it, I can make a PR to implement this?
I've made the changes to the docs and submitted this PR. @sarah11918 let me know if there's anything I've missed.


Introduce set_errno

What does this PR do
This adds a way to set errno, it makes it possible to fully drop errno crate in crates that already use nix.
Checklist:

[x] I have read CONTRIBUTING.md
[x] I have written necessary tests and rustdoc comments
[x] A change log has been added if this PR modifies nix's API

How about a usage example?

If you are asking for a use case, I simply noticed that fish shell depends both on nix and errno, so I digged into it and that's how I found out that nix does not have a way to set errnos.
As to why they need a way to set errno, the project is transitioning from C++ so errno is being used on the API boundary in some places I suppose.
But same need would arise if one is writing rust libs meant for consumption from C.
And if you are asking me to add rustdoc usage example, sure I can do that, just let me know that I misunderstood the question.

And FTR, what function from the errno crate does this replace?

Simply errno::set_errno

Yeah, a rustdoc example would be great.  Also, you'll have to rebase to fix the CI failure.

Rebased, examples added to module docs, and to set and clear functions

I'm not sure if this should be top level function, if clear is a static method already?
Currently we have:
pub fn errno() -> i32;
pub fn set_errno(errno: Errno);

impl Errno {
    pub fn clear(); // Does the same'ish action as set but lives in diferent scope
    pub fn last() -> Errno;
}

So that's not consistent.
But moving set to a method does not seem entirely right either?
impl Errno {
    pub fn set(&self); // Like so?
    pub fn set(errno: Errno) // Or perhaps like this?
}

Personally I would just move clear to top level as well to make it consistent, but that's already part of public API, so I would rather not break it for no reason.

Excellent question.  I agree that the current situation is inconsistent.  I'm a fan of namespaces, so my preference would be:
impl Errno {
    fn set(self) {...}
    fn clear() {...}
    fn last() { ...}
}

I'm not sure if this should be top level function, if clear is a static method already?
Currently we have:
pub fn errno() -> i32;
pub fn set_errno(errno: Errno);

impl Errno {
    pub fn clear(); // Does the same'ish action as set but lives in diferent scope
    pub fn last() -> Errno;
}

So that's not consistent.

It is indeed not consistent.
I think the following approach is ok:
impl Errno {
    pub fn set(errno: Errno) {}

So when people use it, Errno:: would just behave like a namespace.

For nix::errno::errno() -> i32, Maybe we should also move it to:
impl Errno {
    /// Returns the platform-specific value of errno
    pub fn last_raw() -> i32 { }
}

And nix::errno::from_i32() (consts::from_i32()) should be marked pub(crate) so that we don't expose 2 interfaces for 1 thing.
@asomers thoughts on this?

I agree with renaming errno() to Errno::last_raw.  But what exactly do you want to rename from_raw, and why?

I agree with renaming errno() to Errno::last_raw. But what exactly do you want to rename from_raw, and why?

Just for symmetry:
impl Errno {
    pub fn from_raw(raw: i32) -> Errno
    pub fn last_raw() -> i32
}

To deprecate an interface, we do it like this.

To deprecate an interface, we do it like this.
The version of the next release will be 0.28.0.

Done.
Although I have no idea why the CI is failing, I can't figure out where is the code that causes this error:
error: use of deprecated associated function `errno::<impl errno::consts::Errno>::from_i32`: please use `Errno::from_raw()` instead
   --> src/time.rs:251:20
    |
251 |         Err(Errno::from_i32(ret))
    |                    ^^^^^^^^
    |
    = note: `-D deprecated` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(deprecated)]`

There is no line 251 in nix/time module :shrug:

I agree with renaming errno() to Errno::last_raw. But what exactly do you want to rename from_raw, and why?

Just for symmetry:
impl Errno {
    pub fn from_raw(raw: i32) -> Errno
    pub fn last_raw() -> i32
}

LGTM! Thanks!
But I would like to know @asomers's view on the new APIs before merging this PR.


allow groovy scripts to read yaml configs

Used for testing/development. This will allow you put various yaml config files onto the Docker container so that the groovy init scripts can parse out data for configuring Jenkins.
Note: not sure if this is what we want to do when it comes to running ansible plays. Sensitive data is likely to be passed via ansible to the system and stored in memory, not on the FS.
cc @edx/devops

@estute for ansible docker right now we have an ansible_overrides.yml file we COPY into the box, but we don't currently copy secrets (because we don't use docker in prod anywhere).  secrets for us won't ever end up in containers, they'll be dynamically sourced in during runtime.  As for secrets targetting a machine, we tend to run ansible on our laptops and<EMAIL_ADDRESS> happy to talk through that process.
This code looks fine/good for the testing process.


validates format with complex regex generates invalid json

Model:
class Link < ActiveRecord::Base
  validates :address, :format => {:with => URI::regexp(['http','https'])}
end

View:
= semantic_form_for @link, :validate => true do |f|
  = f.input :address

I'm getting a javascript parse error when loading this form, indicating that the json version of the (ridiculously complicated) regex is invalid. I've worked up a failing test for this, which I'll attach separately.
(Note: I know URI::regexp is lousy for validating URLs. This is easier to test than the better one, http://daringfireball.net/2010/07/improved_regex_for_matching_urls, which also triggers the same error.)

See https://github.com/bcardarella/client_side_validations/pull/174
It's not been fixed


Optional tag exclusion

removes dead code for "metric messages" which weren't being used.
adds support for the EXCLUDED_TAGS to avoid sending particular tags to Datadog.

The rationale for this second point is that the path= tag in Heroku logs includes the full HTTP path - including, for instance, query parameters. This makes is very easy to swarm Datadog with numerous distinct tag/value pairs; and Datadog has a hard limit of 1000 such distinct pairs. When the limit is breached, they blacklist the entire metric.

We can make metrics whitelisting definition more flexible using configuration file or ENV variables . This is good first step. Thanks for contributing.


It is not related with the real problem but, your --floodType parameter is wrong, you can only pass syn, ack or synack.


As a CIF developer, I want to have a widget that allows me to update a Routinely Updated Field without going to the "Amendments & Other Revisions" page (frontend widget)

Description:
This ticket is about creating a widget for Routinely Updated Fields and adding it to the Project Overview page for Project Status.
Context:
Shortcut workflows for updating the Routinely Updated Fields have been designed and validated by the CIF team. With such, users can update the field with a few clicks without having to click on the "New Revision" button and follow the steps there on the Amendments & Other Revisions page.
This can be done by allowing users a shortcut to the fields below without following the "New Revision" workflow. Backend logic for this handled in https://github.com/bcgov/cas-cif/issues/1380
The figma link "Example 1" shows an example where a routinely updated field can be updated directly from the 'view' page. There will be no reverting these changes with a revert button as the changes will be committed immediately.

Detailed notes
Detailed grouping of fields on the "Fields" tab of this spreadsheet
Generic example 1: for fields with Dropdown as front-end component
Generic example 2: for fields with Date Picker or Text Input as front-end component

Acceptance Criteria:
Given I am a CIF developer
When I transform a form field to be routinely updated
Then I have a widget to use that implements that functionality out of the box
Development Checklist:

[ ] Create a widget for routinely updated fields. The widget should use the original field's widget (pass as a prop) (?), update the database onChange, and should have an update button that commits the revision (will use the mutations created in https://github.com/bcgov/cas-cif/issues/1380; for now, use mock function, see dev checklist bullet 3). There's a similar widget for amendment status that could perhaps be made more generic to work everywhere.

[ ] configuration of the widget can be either through a widget factory (that creates a widget with the proper form/arguments) or through some static values in the ui schema - there's a bit of exploration on how difficult it is to configure the mutation call

[ ] the widget calls a mock mutation function that just logs a message to the console when called

[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

This could be worked on and implemented without a mutation being called nor a flow being decided @BCerki

You mean the Update button in the widget should do nothing in this ticket, and we hook it up to the mutation later?
Re the flow--if this ticket becomes just widget creation, I agree

Hey team! Please add your planning poker estimate with Zenhub @BCerki @dleard @gurjmatharu @mikevespi @sam-warren @Sepehr-Sobhani

This will be the first of the forms to implement the routinely updated field workflow

This might be an 8, to make sure it's well tested and that the form/widget configuration mechanics are usable and documented

@LindsayMacfarlane This is all code and nothing to test.

Thank you @Sepehr-Sobhani!


fix: nokogiri version bump

This PR allows for Nokogiri versions >= 1.10 but < 2.0.

Coverage remained the same at 100.0% when pulling da83584380b80f13c766f984cef220957a17c573 on nokogiri-patch into b6f71e381c8f9141619e0856a50607955e38e1f8 on develop.

Coverage remained the same at 100.0% when pulling da83584380b80f13c766f984cef220957a17c573 on nokogiri-patch into b6f71e381c8f9141619e0856a50607955e38e1f8 on develop.


Cache first when querying.

Thank you for this great package, would love to first load data from cache then server, this would help in reducing cost on firestore side and good user experience, I thank you in advance.

Hey @richard457!
You mean Firestore cache?

@demchenkoalex yes firestore cache.

So I think Firebase is using some cache underneath itself and everything above that - there was a very similar discussion in #45 you can read it there


Question/Query are endpoints and refresh intervals supported?

Ok so I built my single page UD app a few times now but each time it errors:-

I mean it's highly likely this is me being a dinlow but I'm using an SQL module im importing endpoints and refresh intervals and calling the dashboard like:-
Start-UDDashboard -Port 10008 -Dashboard ($dash ) -Endpoint $Endpoint
Is there something I am missing or just being plain stupid?

@psDevUK I just found a bug in the JS code. Gonna release a new version right now.
Can you also make sure to set the port to 8001 and use the -Wait parameter for Start-UDDashboard?

ok man I am still trying...and failing...but I know this must work as you posted it working...so I decided to now build your test dashboard the one you did....so about the New-BurntToastNotification did you have that moduled imported at the time of building to get that into the .exe or is there a special trick?

Hmmm so I found your demo page and literally just changed it to New-UdInputAction -Toast $Message instead of new-burntToastNotification and I still get this error when trying to launch the .exe

But builds without errors.

You have powershell 6 or 7 installed?

running windows 10 x64 powershell 5

Try setting the -PowerShellHost parameter to powershell.

Yes you are the man @adamdriscoll please put that in the readme for all others using VS Code..You the man!


Components

Created a new directory called components and implemented the app structure.

Hello @coker2019
Your project is complete!  There is nothing else to say other than... Congratulations! 🎉
Status: APPROVED :fire:  :fire:
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Use CSS in rule descriptions

This is a follow up for issue #68 fixed by PR #69
As commented in the PR, we should define the used color codes in a central place, as all rule descriptions make use of the same coloring. This would reduce redundancy and make future refactorings a lot easier.
Since using CSS in rule descriptions doesn't seem to be that straightforward, we might need to find a workaround, maybe as suggested by @hohwille:

As a nice-to-have we can later ask in SonarQube forum for help how CSS could be used or try some own solution e.g. via generation by processing the HTML with maven during the build...

EDIT: Topic on the SonarSource forum

There was an answer from the SonarQube team for this issue:
They support basic HTML without style information in their rule description. There is currently no plan to add styling.
For the full answer, see the topic referenced in the original issue text.

There was an answer from the SonarQube team for this issue:
They support basic HTML without style information in their rule description. There is currently no plan to add styling.
For the full answer, see the topic referenced in the original issue text.


Error when importing eventbrite object

Hi there,
I just installed a package on a CSR version of reactJS. Basically the server is running on node.js, and I get this error when importing the module:
import eventbrite from 'eventbrite';

Results on this error, both on front and back-end side:
Error: Cannot find module 'encoding'
    at webpackMissingModule (webpack-internal:///./node_modules/isomorphic-fetch/node_modules/node-fetch/lib/body.js:5:80)
    at eval (webpack-internal:///./node_modules/isomorphic-fetch/node_modules/node-fetch/lib/body.js:5:163)
    at Object../node_modules/isomorphic-fetch/node_modules/node-fetch/lib/body.js (/front/build/server.js:3410:1)
    at __webpack_require__ (/front/build/server.js:27:30)
    at eval (webpack-internal:///./node_modules/isomorphic-fetch/node_modules/node-fetch/index.js:5:338)
    at Object../node_modules/isomorphic-fetch/node_modules/node-fetch/index.js (/front/build/server.js:3399:1)
    at __webpack_require__ (/front/build/server.js:27:30)
    at eval (webpack-internal:///./node_modules/isomorphic-fetch/fetch-npm-node.js:1:15)
    at Object../node_modules/isomorphic-fetch/fetch-npm-node.js (/front/build/server.js:3388:1)
    at __webpack_require__ (/front/build/server.js:27:30)

The strange thing is that I only IMPORT evenbrite, I am not even using it.

Node version: running on docker container node:10-alpine
Browser name and version: Any
Operating system: Docker

Can you send over a repro repo?
I have a working codesandbox that uses either require or import, but I realize webpack resolution can be much different than codesandbox.
Thanks

Same error to me for the same Docker env, Node 14

Same error to me for the same Docker env, Node 14

I solved following this
https://dev.to/mukul_singhal/write-es6-in-node-using-babel-3m7p
Basically it can work thanks to Babel transpiler

Thanks I appreciate the follow up.


Different evaluation results are obtained on different GPUs

Hi,
Thanks for your amazing work!
I recently encountered a problem, I ran the evaluation of the KITTI dataset on different GPUs and they got different results from the run.
The GPU I used are：

Tesla P100-16GB (provided by Colab)
RTX 3090-24GB (desktop)
RTX 3060-8GB   (laptop)

The version of dependency packages are:
torch                     1.11.0+cu113             pypi_0    pypi
torchaudio                0.11.0+cu113             pypi_0    pypi
torchvision               0.12.0+cu113             pypi_0    pypi
opencv-python             <IP_ADDRESS>                 pypi_0    pypi
python                    3.7.13               h12debd9_0
scipy                     1.4.1                    pypi_0    pypi
scikit-image              0.18.3                   pypi_0    pypi
pykitti                   0.3.1                    pypi_0    pypi
kornia                    0.6.4                    pypi_0    pypi

The final metric results are as follows:
## RTX 3090
'loss': 0.0, 'metrics': [0.15538795390363738, 2.7975851661019338, 5.625108310379362, 0.18630796428342675, 0.8499496491823949, 0.9419053045479213, 0.9715246053337913], 'metrics_correct': [0.1553879539036371, 2.797585166101927, 5.625108310379343, 0.18630796428342658, 0.849949649182393, 0.941905304547917, 0.9715246053337869], 'valid_batches': 4317.0, 'loss_loss': 0.0, 'metrics_info': ['abs_rel_sparse_metric', 'sq_rel_sparse_metric', 'rmse_sparse_metric', 'rmse_log_sparse_metric', 'a1_sparse_metric', 'a2_sparse_metric', 'a3_sparse_metric']

## RTX3060
loss': 0.0, 'metrics': [0.15538795390363738, 2.7975851661019338, 5.625108310379362, 0.18630796428342675, 0.8499496491823949, 0.9419053045479213, 0.9715246053337913], 'metrics_correct': [0.1553879539036371, 2.797585166101927, 5.625108310379343, 0.18630796428342658, 0.849949649182393, 0.941905304547917, 0.9715246053337869], 'valid_batches': 4317.0, 'loss_loss': 0.0, 'metrics_info': ['abs_rel_sparse_metric', 'sq_rel_sparse_metric', 'rmse_sparse_metric', 'rmse_log_sparse_metric', 'a1_sparse_metric', 'a2_sparse_metric', 'a3_sparse_metric']

## P100 (provided by colab)
'loss': 0.0, 'metrics': [0.050102306426327375, 0.29000417841479736, 2.2656219501116497, 0.08224765892285756, 0.9723125736912782, 0.9907187367026828, 0.9957081838727743], 'metrics_correct': [0.0501023064263273, 0.29000417841479575, 2.2656219501116426, 0.08224765892285742, 0.9723125736912774, 0.9907187367026803, 0.9957081838727698], 'valid_batches': 4317.0, 'loss_loss': 0.0, 'metrics_info': ['abs_rel_sparse_metric', 'sq_rel_sparse_metric', 'rmse_sparse_metric', 'rmse_log_sparse_metric', 'a1_sparse_metric', 'a2_sparse_metric', 'a3_sparse_metric']

Full evaluation logs are attached as bellow:
colab_p100_eval_log.txt
RTX3090_eval_log.txt
RTX3060_eval_log.txt
I found that 3090 and 3060 run with the same result, but it differs greatly from the result of P100, which is very closed to the result provided by the paper.
I did not change any code during the above evaluation process, and they use the same data set.
Have you encountered this problem?
Could you please give me some advice?

Hi,
thanks for being interested in our work and for providing such detailed information to the problem!
I have never seen this behavious before.
When looking at the logs, it seems to me that initially, all gpus produce very good predictions (see first two lines in the evaluation log).
Then, the RTXs become gradually worse. This leads me to believe that the issue lies with summing / averaging the metrics between the different batches.
Could you replace line 106 in evaluater/evaluater.py from
self.logger.debug(f'Evaluating {self._progress(batch_idx)} Loss: {loss.item() / (batch_idx + 1):.6f} Metrics: {list(total_metrics / (batch_idx + 1))}')
to
self.logger.debug(f'Evaluating {self._progress(batch_idx)} Loss: {loss.item() / (batch_idx + 1):.6f} Metrics: {list(metrics)}')
and send me the logs again?
Best,
Felix

This result is what makes it so difficult for me...
Personally, I don't think this is due to a PyTorch version issue; after all, the P100 also uses PyTorch 1.11.0 （All GPUs were all kept in the same environment during the experiment）and gives a good result.
Also, since the RTX30 series only supports cuda11 and newer, and PyTorch 1.5 requires cuda10, there is no way to use such a low version of PyTorch for the RTX30 series GPUs. It makes me feel helpless...
Anyway, thank you very much for your reply!
Please let me know if you can think of other possible reasons. Your help is much appreciated!
Best

This result is what makes it so difficult for me...
Personally, I don't think this is due to a PyTorch version issue; after all, the P100 also uses PyTorch 1.11.0 （All GPUs were all kept in the same environment during the experiment）and gives a good result.
Also, since the RTX30 series only supports cuda11 and newer, and PyTorch 1.5 requires cuda10, there is no way to use such a low version of PyTorch for the RTX30 series GPUs. It makes me feel helpless...
Anyway, thank you very much for your reply! Please let me know if you can think of other possible reasons. Your help is much appreciated!
Best

Hi,
I also encountered the same issue. This is due to the Ampere architecture used in NVIDIA 30xx seires. You can correct the results by simply set torch.backends.cuda.matmul.allow_tf32 = False. You can also refer to this for further information. Hope it is helpful to you :)
Best


Appstudio update test-component-pac-mqjs

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-mqjs-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
4 seconds
init

✅ Succeeded
12 seconds
clone-repository

✅ Succeeded
23 seconds
build-container

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
13 seconds
sanity-inspect-image

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
34 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
14 seconds
sanity-optional-label-check

✅ Succeeded
14 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary


BUG: Issues with huge folders game doesnt want to mount vpk or something else

when trying to mount the materials folder into a game the game doesn't want to actually load it mind you its a SDK 2013 SP mod but the issue is I also tried creating the materials folder vpk with the normal version of vpk on windows and the game loads it totally fine
might there be some issue that might cause this like something in the vpk header not being there for the game to load?
other stuff like models and sound loaded in fine to the mod

ok so seems like models get loaded into the game perfectly fine the issue right now is VTF and sounds
those are the only files not being loaded into the game

i pak modles sounds and materials into a big pak01 vpk and it will only load in models the other things like materials and sounds don't get loaded or they fail to be loaded here is what happens when we try to load in a sound file
here is an image


[Flaky Test] task functions ParallelN [It] should run the tasks

How to categorize this issue?

/area testing
/kind flake
Which test(s)/suite(s) are flaking:
task functions ParallelN [It] should run the tasks
CI link: https://prow.gardener.cloud/view/gs/gardener-prow/pr-logs/pull/gardener_gardener/8912/pull-gardener-unit/1742838404367781888
Reason for failure:
  STEP: Checking active tasks after initial ParallelN call @ 01/04/24 12:18:59.264
  [FAILED] in [It] - /Users/foo/SAPDevelop/go/src/github.com/gardener/gardener/pkg/utils/flow/taskfn_test.go:181 @ 01/04/24 12:19:00.265
  [FAILED] in [AfterEach] - /Users/foo/SAPDevelop/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.13.0/internal/node.go:463 @ 01/04/24 12:19:00.713
  << Timeline

  [FAILED] Timed out after 1.000s.
  Expected
      <int>: 0
  to equal
      <int>: 2
  In [It] at: /Users/foo/SAPDevelop/go/src/github.com/gardener/gardener/pkg/utils/flow/taskfn_test.go:181 @ 01/04/24 12:19:00.265

  There were additional failures detected.  To view them in detail run ginkgo -vv

Anything else we need to know:
Steps to reproduce:
# get the stress tool
go install golang.org/x/tools/cmd/stress@latest

# build a test binary
% ./hack/tools/bin/ginkgo build ./pkg/utils/flow
Compiled flow.test

% stress -p 1 ./pkg/utils/flow/flow.test -ginkgo.focus "should run the tasks"
...
3m35s: 1327 runs so far, 85 failures (6.41%)
3m40s: 1351 runs so far, 87 failures (6.44%)
3m45s: 1367 runs so far, 90 failures (6.58%)
3m50s: 1399 runs so far, 92 failures (6.58%)

Introduced with https://github.com/gardener/gardener/pull/8815.
cc @dimityrmirchev

/assign


[2023 social media - quarterly highlight] Budget and Program plan - Transparency

https://docs.google.com/spreadsheets/d/1-j0SmFHSRw4pXMsdsY1x0R2HffIUZ3SQni_5zpoBdE8/edit#gid=1254202074
Description
#MicroProfileTransparency:  The #MicroProfile yearly Program Plan is drafted and worked in the open with the #MicroProfileCommunity. The annual Budget covers the priorities in the Program Plan, publicly accessible. #ByCommunityForCommunity #opensource
https://microprofile.io/workinggroup/#mptab-program-plan-budget
Schedule
6 times in 2023
can be weekends and weekdays

scheduled to go out 6 times

@rstjames,
Did you adjust the card to include the budget?

@aeiras yes