login redirection - logic error, and sensitivity to / in URL

Running our 'coco pharma' lab helm chart, deployment goes well, and the presentation server pod is started as expected
However login fails
$ kubectl logs lab-odpi-egeria-lab-presentation-78cb55bf9f-wpnbw                                               [15:33:26]

<EMAIL_ADDRESS>prod /home/node/egeria-react-ui/cra-server
NODE_ENV=production node index.js
getServerInfoFromEnv() 1
getServerInfoFromEnv() 2
Found server name coco
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
Server listening on port: 8091
segment1 user
/user
undefined
segment1 favicon.ico

This could be an issue in how the image is built.
Any ideas @davidradl
To clarify- the build process currently just does

npm install / run build in client, then server
in server runs 'npm run prod' in the cra-server directory

See the 'Dockerfile' for what is RUN, and .github/workflows/node-build.yml for what is built.

This could be an issue in how the image is built.
Any ideas @davidradl
To clarify- the build process currently just does

npm install / run build in client, then server
in server runs 'npm run prod' in the cra-server directory

See the 'Dockerfile' for what is RUN, and .github/workflows/node-build.yml for what is built.

This occurs when using the base URl ie https://71b52643-eu-gb.lb.appdomain.cloud:8091 which now redirects to a login page.
When entering https://71b52643-eu-gb.lb.appdomain.cloud:8091/coco/login as before, a blank screen is shown both in safari & chrome
However https://71b52643-eu-gb.lb.appdomain.cloud:8091/coco works ok
So overall the behaviour is more sensible, but may be confusing for prior users, also looks like some more changes are needed on the redirect from the other urls

This occurs when using the base URl ie https://71b52643-eu-gb.lb.appdomain.cloud:8091 which now redirects to a login page.
When entering https://71b52643-eu-gb.lb.appdomain.cloud:8091/coco/login as before, a blank screen is shown both in safari & chrome
However https://71b52643-eu-gb.lb.appdomain.cloud:8091/coco works ok
So overall the behaviour is more sensible, but may be confusing for prior users, also looks like some more changes are needed on the redirect from the other urls

Quick observation - the animation is quite distracting

Quick observation - the animation is quite distracting

Discussed with @davidradl via webex
It turns out the issue is, given an organization name 'org'
http://server:8091/
-> Shows full login page
-> A valid user login results in 'Logic Error'
-> We need a 'good' landing page that explains this is invalid - we have no tenant information in context
https://server:8091/org
-> Shows a blank page
-> This should show the login page IMO, the same as .....
https://server:8091/org/
-> Shows the login page
-> Login works fine
https://server:8091/org/login
-> Blank Page
-> optionally could redirect - but not essential. If not should show error
https://server:8091/org/login/
-> Blank Page
-> either redirect or show error as we have enough context for the org to use in the URL
https://server:8091/acme/
-> Shows login page
-> Login works
-> Seems like an error. That page should show an error (no such tenant etc). Also the login shouldn't work (which credentials?). (An error does occur if one then tries to use the UI, but this IMO is too late)

Discussed with @davidradl via webex
It turns out the issue is, given an organization name 'org'
http://server:8091/
-> Shows full login page
-> A valid user login results in 'Logic Error'
-> We need a 'good' landing page that explains this is invalid - we have no tenant information in context
https://server:8091/org
-> Shows a blank page
-> This should show the login page IMO, the same as .....
https://server:8091/org/
-> Shows the login page
-> Login works fine
https://server:8091/org/login
-> Blank Page
-> optionally could redirect - but not essential. If not should show error
https://server:8091/org/login/
-> Blank Page
-> either redirect or show error as we have enough context for the org to use in the URL
https://server:8091/acme/
-> Shows login page
-> Login works
-> Seems like an error. That page should show an error (no such tenant etc). Also the login shouldn't work (which credentials?). (An error does occur if one then tries to use the UI, but this IMO is too late)

@planetf1 please can you verify on the current build; it was looking in the wrong place for its minified resources.

Testing with the latest build in dev mode gives me

npm start takes me to http://localhost:3000/
attempt to login as garygeeke/admin - fails with Logic error as before. (I expect the login to be invalid, but we need to correct how that landing page is rendered & whether there even is a login option)
Trying http://localhost:3000/coco - works, without the trailing slash - so this is an improvement

So the / is working in this env, but we still have a problem with the root page
Not tested prod yet. Will update when I have.

I see the same behaviour in the container environment.
I also note that going to https:///acme/
renders a page and then a logic error is produced.
I see two options
Either
a) Land on some kind of error/not here page
b) Just return the same error as if userid/password is incorrect -- ie not admitting to the fact that endpoint is valid or not..?

@planetf1 Please confirm this is now working as expected for you. There has been more than one change in this area to address the issues.

@davidradl Thanks. Not going to be able to test immediately, so I will assign to myself to verify

I retested this with 2.7 and noticed:

If I go straight to the base URL I get a page prompting for server name (see #90)
Entering coco correctly redirects me to the correct login URL
Entering a bad server name still gives me a login page, though attempting login results in The URL is not valid. You will be asked to put in a valid Server Name. - is this as expected? I had thought the initial url like https://localhost:8091/banana might immediately produce the error
On the initial page prompting for server name, I can click to login, however the natural inclination is to enter the server name and hit ENTER - this does not work

@planetf1
If I go straight to the base URL I get a page prompting for server name (see #90) working as expected
Entering coco correctly redirects me to the correct login URL working as expected
Entering a bad server name still gives me a login page, though attempting login results in The URL is not valid. You will be asked to put in a valid Server Name. - is this as expected? I had thought the initial url like https://localhost:8091/banana might immediately produce the error I can see this could be improved, though I am not giving this any priority at this time; unless the community thinks this should be looked at with some urgency.
On the initial page prompting for server name, I can click to login, however the natural inclination is to enter the server name and hit ENTER - this does not work I think an explicit login button is acceptable here

In this release I note that a url like https://server:8091/coco no longer appears to work for login as it redirects to a request for server.
Error, forbidden URL. Please supply a valid Server Name in the URL.
However https://server:8091/coco/login does still work

https://host:8091/ redirects to page asking for 'server'
Entering 'coco' in this fails and reloads the page prompting for server
Entering https://host:8091/coco works fine
Entering https://host:8091/banana results in Error, forbidden URL. Please supply a valid Server Name in the URL.


Many playbacks with 0-1 seconds of activity

Is your feature request related to a problem? Please describe.
I am setting up Jellystat for the first time with my Emby server, and I'm seeing many instances of tiny playbacks of 0-1 seconds in length:

I'm not sure why it's coming into Jellystat with this data, my reporting on the Emby server shows a reasonable play count (though it's possible that reporting is doing some combination/filtering already).
Describe the solution you'd like
Would it be possible to have a user-configurable setting for a 'minimum length' in seconds for a playback to be considered a valid activity?
Describe alternatives you've considered
Potentially each entry under a length is combined, so 10 playbacks of 2 seconds would instead be 1 playback of 20 seconds? But I personally would prefer just excluding things under a specified length.
Additional context
Environment Details:

OS: Docker
Browser: Chrome
Jellystat Version: v1.0.9
Emby Version: Emby v<IP_ADDRESS>

Hey @zodac , this has been fixed in v 1.1.0, which is currently on the unstable branch, your free to use it  as its actually pretty stable and ready for release, just a few bugs that already exist in 1.0.9 that have not been fixed that are holding it back

That's good to know, thanks! I'll try out the unstable image and give it a shot. :)


¿How to load third-party text fonts

¿How to load third-party text fonts
I have a package installed and which I use its sources, and add them to the angular.json file
"assets": [
              "src/favicon.ico",
              "src/assets",
              {
                "glob": "**/*",
                "input": "node_modules/@mylibrary/scss-theme/theme/assets",
                "output": "assets"
              },
            ],

When I test it locally it works, but in production it does not, it still points to the main path, that is, to the project that registers the applications, I hope you can help me.
Libs:

@angular/core version: 9.1.7
single-spa-angular version: 4.2.0

When you build for production, are you providing the --deploy-url flag? Example at https://github.com/joeldenning/coexisting-angular-microfrontends/blob/925dd8ec4f7f149eeba305f4e3cc4e9783abf3db/app1/package.json#L11
The --deploy-url flag tells Angular the base URL to use when loading assets in a production build.

in your example you put --deploy-url / dist / app1 does this have to do with setting your angular.json?
"outputPath": "dist / app1"
or should the domain where the application in production is being deployed go? example:
--deploy-url mydomain.com

Well, I tried it in various ways with --deploy-url but it doesn't take effect, it still makes the call from the root of the container (my root config application that registers to the other applications) some tip?

in your example you put --deploy-url / dist / app1 does this have to do with setting your angular.json?

It has to do with where the code is hosted.

Well, I tried it in various ways with --deploy-url but it doesn't take effect, it still makes the call from the root of the container (my root config application that registers to the other applications) some tip?

You can try Angular's rebaseRootRelativeCssUrls option. See https://github.com/single-spa/single-spa.js.org/pull/282/files and https://angular.io/cli/build

As far as I know deploy url works, but still some cases are not cover by it, which means, for example, that css background url is not affected by it. Anyway our solution was to get all needed fonts in our loader, this way this files is available even if it's not getting from the app location.
Another possible solution (we think about it but we currently do not need it) is to do a post build alteration, meaning that any missing asset url will be fixed after the app build

Closing since a solution seems to have been reached.

When you build for production, are you providing the --deploy-url flag? Example at https://github.com/joeldenning/coexisting-angular-microfrontends/blob/925dd8ec4f7f149eeba305f4e3cc4e9783abf3db/app1/package.json#L11
The --deploy-url flag tells Angular the base URL to use when loading assets in a production build.

It took 2days to find this solution, anyway that's my fault to delete the single spa boilerplate code.
Really thank you @joeldenning 💯 working


Announcements - env variable

I tried to implement this just as you implemented front end and back end urls, and can't figure out why it is not working. Could you please take a look at this when you get the chance @josephmaxwellhyland ? https://github.com/hto-projects/friendpardy/tree/audio-env

Thanks @josephmaxwellhyland https://github.com/hto-projects/friendpardy/pull/277


Option to print previous exception

Hey.
Currently there's no option for Collision to print the Throwable::getPrevious() exception alongside the main one, but it'd be nice to have one.
Our use case specifically is this: we have Laravel integration tests that make HTTP requests. When a HTTP code assertion fails due to an exception during the request, Laravel attempts to add some debugging information by adding this kind of text stack trace to the exception message (by modifying Exception::$message through reflection):
The following exception occurred during the last request:

TypeError: [redacted]: Return value must be of type float, null returned in [redacted]
Stack trace:
.. a lot of trace lines here
#84 /app/tests/TestCase.php(144): Illuminate\Foundation\Testing\TestCase->postJson()
.. a lot of trace lines here
#96 /app/vendor/phpunit/phpunit/src/TextUI/TestRunner.php(63): PHPUnit\Framework\TestSuite->run()
#97 /app/vendor/phpunit/phpunit/src/TextUI/Application.php(177): PHPUnit\TextUI\TestRunner->run()
#98 /app/vendor/phpunit/phpunit/phpunit(99): PHPUnit\TextUI\Application->run()
#99 {main}

----------------------------------------------------------------------------------

[redacted]: Return value must be of type float, null returned

  at tests/[redacted]
    290▕                        ],
    291▕                ])
  ➜ 292▕                        ->assertSuccessful()
    293▕                        ->assertJson([
    294▕                                'meta' => [
    295▕                                        'rules' => [

  Tests:    1 failed (1 assertions)
  Duration: 20.35s

Although this does work, it'd be much nicer to have the original exception rendered natively by Collision. Laravel could then set Exception::$previous instead of the Exception::$message and it'd be rendered something like this:
at tests/[redacted]
    290▕                        ],
    291▕                ])
  ➜ 292▕                        ->assertSuccessful()
    293▕                        ->assertJson([
    294▕                                'meta' => [
    295▕                                        'rules' => [

Caused by an exception at tests/[redacted]:103: Return value must be of type float, null returned

    101▕                // code
    102▕                // code
  ➜ 103▕                // code
    104▕                // code
    105▕                // code
    106▕                // code

  Tests:    1 failed (1 assertions)
  Duration: 20.35s

That would improve QoL by reducing the stack trace (from 100+ lines of vendor code to just a few lines that are actually important) and rendering it in an eye-friendly way.
Besides the need of a new option and some additions to the inspectors, this addition looks trivial to implement, so if this is something that can get merged, I can PR the changes.

So it turns out it does work, just not at all how you expect it to. The "previous" exception is included in the trace, but this is how it currently looks:
  at [redacted]
    106▕                        // code
    107▕                        // code
    108▕                        // code
    109▕                        // code
  ➜ 110▕                        // code
    111▕                        // code
    112▕                        // code
    113▕                        // code
    114▕        }

  1   app/SomeFile:67
      NunoMaduro\Collision\Exceptions\TestException::("asdasd")
  2   app/SomeFile:67

A few things here:

instead of the actual exception class name, we get NunoMaduro\Collision\Exceptions\TestException
throw location is duplicated twice
only 1 usable trace line is included. If you run tests with SHELL_VERBOSITY=1, it does show the complete trace - but in that case it also includes 100 trace lines from vendor which clutters the output. I'd rather see the complete stack trace of userland code than 1 line.


Bug: Build Script should exit with non-zero if package compilation fails

Describe the bug
The CD system for this repo was reporting build succeeded even though the packages failed compilation.
Upon further inspection, it looks like the build script returns 0 no matter what happens to the package compilation
(This is related to https://github.com/OnionIoT/openwrt-imagebuilder-wrapper/issues/4)
To Reproduce

Setup this repo: bash onion_buildenv setup_sdk
Make some changes to make the package compilation fail (the current CD system uses ubuntu 20.04 which causes the failure)
Try to compile the packages: bash onion_buildenv build_all_packages
Observe errors in compilation output
Run echo $? and observe 0

Expected behavior
Expecting the onion_buildenv script to return 1 if any of the packages cannot compile correctly.
More context
Attaching full CD logs
Relevant parts:
Error compiling packages
make[2]: Leaving directory '/codebuild/output/src642488073/src/openwrt-sdk/package/toolchain'
--
787 | time: package/toolchain/compile#0.28#0.07#0.30
788 | ERROR: package/toolchain failed to build.
789 | make[1]: *** [package/Makefile:116: package/toolchain/compile] Error 1
790 | make[1]: Leaving directory '/codebuild/output/src642488073/src/openwrt-sdk'
791 | make: *** [/codebuild/output/src642488073/src/openwrt-sdk/include/toplevel.mk:223: package/omega2-base/compile] Error 2
792 | make: Leaving directory '/codebuild/output/src642488073/src/openwrt-sdk'
793 | \n>> ERROR: Compile of package omega2-base returned code 2
794 | \n>> PACKAGE COMPILATION ERROR!\n

But the next CD phase includes a check that the build succeeded, and it passes:
 make[1] package/index
make: Leaving directory '/codebuild/output/src642488073/src/openwrt-sdk'

[Container] 2023/04/28 17:45:59 Phase complete: BUILD State: SUCCEEDED
[Container] 2023/04/28 17:45:59 Phase context status code:  Message:
[Container] 2023/04/28 17:45:59 Entering phase POST_BUILD

Resolved in PR https://github.com/OnionIoT/openwrt-sdk-wrapper/pull/6, closing this issue


use DataCollatorWithFlattening when not sample packing

https://research.ibm.com/blog/hugging-face-training-flash-attention

ran a quick experiment against l3-3B with microbatch size of 8. losses stack on top pretty closely, but flattening is good bit faster.

I should make this have an auto option that automatically enables this when not using packing with micro batch size > 1


lib: add filterMap

Description of changes
Needed this enough times I thought it deserved to be in the standard library.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@bb010g Your function behaves like pred: f: attrs: mapAttrs f (filterAttrs pred) attrs, i.e. map after filter. Shouldn't it be mapFilterAttrs then?
Also I'm not sure we should have it because it doesn't pass the Fairbairn threshold.
filterMap is also close to that threshold, but at least does a bit more than just sequencing two functions, specifically because everything happens in a single callback. That's useful because you can have a let binding in the callback for both the purpose of filtering as well as transforming. (Solving similar problem to the module system types' distinct check and merge functions.)

You mention that that filterAttrs is strict in the items

I agree it is a little too hand-wavy what I wrote.
Regarding the implementation of a function like filterMapAttrs, concatMapAttrs might be a good choice to build on. Or become a good choice, because I'd consider adding that functions to the builtins. It seems to be most general form of attrset transforming functions after zipAttrsWith, which adds list allocations that concatMapAttrs wouldn't need.
As for strictness, concatMapAttrs works fine, because you can return the relevant part of the attrset while the "map" part of the computation is only performed when the attribute value is evaluated. Also if you use concatMapAttrs directly instead of via filterMapAttrs, you get to write let bindings that are used by both the "predicate" logic and the "map" logic, similar to what this PR achieves.

I'd also like to see some bench results for your current filterMap implementation using foldl' compared to an implementation using filter & map and an implementation using concatMap.

filter and map basically causes you to iterate the list twice, so I can't imagine it would be competitive, performance wise. foldl' and concatMap are both builtins, however, so their comparison might be a bit more interesting. I might be able to put together a quick and dirty benchmark.


Update Magnum to latest & fix various minor buildsystem issues

Motivation and Context
Changes that aren't really related to the upcoming second batch renderer PR, thus submitting them separately.
Regular update of Magnum submodules:

Adapting to a minor API deprecation (BoolVector -> BitVector, for consistency with new BitArray containers and because it's one character less to type)
Using now-builtin std::hash specialization for Containers::String
No other changes worth mentioning, the major piece of work done lately isn't published yet

And some minor fixes. For faster iterations I'm having a second build directory that uses a system-installed Magnum and has various features disabled, and various code rot prevented that from working:

Various CMake updates that are needed if Magnum is external (and are no-op if it's a subproject)
Making a build without Bullet work again
Making a build with dynamic Magnum work again

And finally, certain bindings code used a private header from magnum-bindings. It's private so I don't guarantee any forward compatibility, I don't want anybody to use it :stuck_out_tongue_closed_eyes:, and it doesn't even get installed which causes a build failure if Magnum is external. I made a copy of that utility directly inside Habiat and the bindings code now uses that instead.
How Has This Been Tested
Builds locally.
Types of changes

[x] Docs change / refactoring / dependency upgrade

Using now-builtin std::hash specialization for Containers::String

Nice.

Hmm... "$SRC_DIR/src/esp/bindings/GfxBindings.cpp:15:10: fatal error: 'esp/bindings/EnumOperators.h' file not found"

Lol, sorry. Fixed.

Now clang-format is complaining a bit.

Fixed.
(Note to self: don't open PRs at 8 PM.)


Move gateways to separate packages

DO NOT MERGE THIS YET!
All done.
See:

https://github.com/notifymehq/campfire
https://github.com/notifymehq/gitter
https://github.com/notifymehq/hipchat
https://github.com/notifymehq/pagerduty
https://github.com/notifymehq/pushover
https://github.com/notifymehq/slack
https://github.com/notifymehq/twilio
https://github.com/notifymehq/webhook

Done.

Nice!

:boom:


[Dropdown] - useLabels: false in onVisible resets values

Hi,
When using onVisible on a dropdown with useLabels: false, the dropdown is reset each time it's opened.
Demo
The blue and green in the Demo is identical, except "useLabels: false"
Best regards
Alexander N

Hi @alexnicolaisen, the gist of it is that you shouldn’t be initializing a dropdown every time a popup becomes visible—initialize it only once. The following is a standard reply.
Thank you for posting, but although it’s a valid usage question, we’ve limited GitHub Issues to bug reports and feature requests, keeping the board more manageable for maintainers; see the contributing guidelines for more information on what kind of posts should find themselves into the GitHub Issues board.
To get answers or feedback that might allow you to repost or reopen this issue, please use one of our other support resources:

Gitter chatroom
Official forums
StackOverflow


result URL with invalid id errors instead of 404

If you put a string that is not a job id in the result route
http://<IP_ADDRESS>:5000/result/x
The app returns an error
AttributeError
AttributeError: 'NoneType' object has no attribute 'description'

In addition, any jobid that is not saved as part of a result will also return an error.  This means that is a result is deleted but the user tries the URL, the output is an error.
In addition, If you run a job when not logged in, no 'result' record is saved.  The output of the job is still available via the jobs route eg.
http://<IP_ADDRESS>:5000/jobs/anon819-qxb6y3vi
it's the same error (because of course there is no corresponding result id since no result record was created)
Solution is to check the 'result' exists and return 404 instead of crash.  however, for anonymous jobs, do we want to still show the output  (especially given suggested solution to #240 to only show results on a the /results/ route )

Do we want to have a separate page for either of these issues (rather than a 404) or do we want to just flash a message and redirect someplace?

Closed with pull request


WSL build info missing dependencies

Describe the bug
Not sure if this is relevant but with latest distros in WSL, you also need to install gcc and make packages (and their automatic dependencies) otherwise the compiling fails - see complete steps below.
Steps to reproduce the behaviour
Ubuntu/Debian

Info for WSL installation: https://www.linuxfordevices.com/tutorials/linux/install-debian-on-windows-wsl

Install Ubuntu/Debian on WSL and start:
wsl -d <distro> # use Ubuntu or Debian

Change to user directory and update packages:
cd
sudo apt update
sudo apt upgrade

Install required modules (gcc and make are needed):
sudo apt install git libusb-1.0-0-dev pkg-config gcc make

Clone repository and compile:
git clone --depth=1 https://github.com/raspberrypi/usbboot
cd usbboot
make

Start USB boot script:
sudo ./rpiboot

Device(s)
Other
Compute Module IO board.
No response
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response

I don't think we need specific instructions for WSL, I'm sure people can figure out how to install gcc / make on platforms they aren't already present.


[Question] Scoped effects in effectful

Hi!
Does effectful support something like polysemy's Scoped?
If not, is there a way to handle having state transactions in my business logic in a type safe way, i.e.

I should not be able to use my "stateful effect" outside a transaction
I should not have to leak the implementation of the transaction (e.g. acquiring an sql connection from a pool)

?

Does effectful support something like polysemy's Scoped?

There is no Scoped in effectful at the moment, but I'm pretty sure it can be written.

@googleson78 I've read a bit about this.
Do I understand correctly that Scoped is basically a way to abstract away running a dynamically dispatched effect into a dynamically dispatched effect itself?


View the SAP BTP from 10,000 Meters

Tutorials: https://developers.sap.com/tutorials/cp-explore-cloud-platform.html
The buttons on the tutorial do not work correctly. Neither in Safari, nor in Firefox.
When you submit an answer, you get a "Technical error" after a while.
Kind regards,
Steffen

The buttons work again (actually a week ago). @Amster2017  Is everything OK for you? Please don't be discouraged and please go ahead and complete the tutorial.


IDEA 2017.1 compatibility changes

Fixes the received user report for
java.lang.NoSuchMethodError: com.intellij.ide.ui.laf.darcula.DarculaUIUtil.paintFocusRing(Ljava/awt/Graphics;IIII)V
...
and a couple other issues with javax.annotation.Nullable.

I guess these changes break 2016?  I don't think we can merge this until 2017 is released and we're committing our next release to it.
Alternatively it may make sense to create an EAP branch and merge this in there. We could even push a release targeting the EAP only so that those users can use our plugin.

Yeah, I won't merge til we move to IJ 2017 (i.e., while tests don't pass).
EAP branch sounds good, but we'd still need to release the plugin normally right? e.g., Alpha and default channels, etc.

You can apparently release multiple binaries with the same 'version' but
targeting different idea platform versions. I haven't tested it though.
On Tue, Mar 14, 2017 at 9:23 AM, João Martins<EMAIL_ADDRESS>wrote:

Yeah, I won't merge til we move to IJ 2017 (i.e., while tests don't pass).
EAP branch sounds good, but we'd still need to release the plugin normally
right? e.g., Alpha and default channels, etc.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1296#issuecomment-286419172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HUS0aCOdiDzpiroHjpUnMwKAT46Yks5rlpTdgaJpZM4MbbfG
.


Unexpected blank screen behind notch

Current behavior

Expected behavior

To Reproduce
Just a typical render of views that occupy the whole width and height of the screen
Platform:

[x] iOS

Environment
Version 1.4.2

Is this package dead?


bug: role in list filter cause js error

in https://github.com/Talend/react-talend-components/blob/master/src/List/Toolbar/Filter/Filter.component.js
role="search" cause js error.

form
className="navbar-form navbar-right"
role="search"
onSubmit={onSubmit}

error:
unmountComponentAtNode(...): Target container is not a DOM element.
Invariant Violation: unmountComponentAtNode(...): Target container is not a DOM element.
    at invariant (webpack:///./~/fbjs/lib/invariant.js?:44:15)
    at Object.unmountComponentAtNode (webpack:///./~/react-dom/lib/ReactMount.js?:440:220)
    at OverlayTrigger.componentWillUnmount (webpack:///./~/react-bootstrap/lib/OverlayTrigger.js?:178:27)
    at eval (webpack:///./~/react-dom/lib/ReactCompositeComponent.js?:409:25)
    at measureLifeCyclePerf (webpack:///./~/react-dom/lib/ReactCompositeComponent.js?:75:12)
    at ReactCompositeComponentWrapper.unmountComponent (webpack:///./~/react-dom/lib/ReactCompositeComponent.js?:408:11)
    at Object.unmountComponent (webpack:///./~/react-dom/lib/ReactReconciler.js?:79:22)
    at ReactCompositeComponentWrapper.unmountComponent (webpack:///./~/react-dom/lib/ReactCompositeComponent.js?:418:23)
    at Object.unmountComponent (webpack:///./~/react-dom/lib/ReactReconciler.js?:79:22)
    at ReactCompositeComponentWrapper.unmountComponent (webpack:///./~/react-dom/lib/ReactCompositeComponent.js?:418:23)

This issue was moved to Talend/ui#48


[Migrated] fix: Decoding issue for windows in zappa init

Originally from: https://github.com/Miserlou/Zappa/issues/1746 by penguindustin
Description
Some windows machines can't decode the title text from zappa init causing it to fail. This change should allow for a safe alternative text to be displayed in those cases.
GitHub Issues
#825

not enough info
closing.


bugfix  webpack4 tap 'failed' hook

when  setting  'bail': true, the compiler will tap failed hook.

Thanks for the contribution ! Can you add a test for this ?

ok. I will add a test for this.


Label priority score

Every label could be given a priority score which is default 0 for compitable. When list issues or pull requests, there is a new option to list according label scores.

This sounds similar to issue priority. What would be the difference, just more granular?

@jolheiser It's not the same. You could create three labels, high priority, normal priority and low priority and give 3, 2, 1 score. That it is.
For issue priority, you have to change one by one issue and it's difficult to decide which issue's more prior than another.

Presumably you mean that the score of the issue would be the sum of its labels?
Would you want to sort by this score?

@zeripath yes


[Feature Request]I want to create a bot that does not use RAG

Describe the solution you'd like
I want to give instructions to LLM and create a chat that does not use the RAG function
Why the solution needed
There are use cases that do not utilize RAG.
Additional context
If you can create chats other than RAG as shown below, the range of usage will expand.
https://github.com/aws-samples/generative-ai-use-cases-jp
Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?

[x] Yes, I am able to implement the feature and create a pull request.
[ ] No, I am unable to implement the feature, but I am open to discussing the solution.

You can create a bot without RAG by setting "Knowledge" section as empty.

It's done. thank you.


Removed horrid faceit stuff dictionaries

Honestly not even tested but it builds 👀

No longer needed as we will move to @18swenskiq code for FaceIt API stuff


[feature request] Open sidebar

Currently, the command Show Day Planner Timeline populates the sidebar, but the sidebar remains closed. To get focus, you have to open the sidebar and click the appropriate tab. Most other sidebar commands automatically take focus. It would be good to remove these extra steps so that the command could become a reflex.

Hello, @kmaustral, please update the plugin and re-check.

Works great now. Sorry I overlooked leaving a message with the 3 coffees. I appreciate your work.

this issue should be closed


🐛 Copyright only displays the year

Describe the bug
Copyright only displays the year.
I installed the latest version of Hugo v0.113.0 and found that the theme errors when running. So I updated the theme using Git, and everything seemed to be fine. However, I noticed that the copyright at the bottom of the webpage only displays the year. I then checked the languages.zh-CN.toml file and found that the copyright setting does not work, while the title settings do work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
copyright = "©{ year } #0000CD · [署名-非商业性使用 4.0 国际](https://creativecommons.org/licenses/by-nc/4.0/deed.zh)"
Screenshots

Desktop (please complete the following information):

OS: win11
Browser firefox
Version 115

Hugo & Blowfish versions

Hugo v0.113.0
Blowfish v2.35.1

Additional context
Add any other context about the problem here.

https://github.com/vicevolf/test223
https://test223.pages.dev  zh or en

Hi, I think you can statically configure this via:
https://github.com/nunocoracao/blowfish/blob/main/config/_default/languages.en.toml#L14

Hi, I think you can statically configure this via:
https://github.com/nunocoracao/blowfish/blob/main/config/_default/languages.en.toml#L14

I have set it before, but zh is invalid, only en is effective 🤔
https://github.com/vicevolf/test223/tree/main/config%2F_default
https://test223.pages.dev/

@vicevolf can you try placing copyright within a params like this:
[params]
  copyright = "©{ year } #0000CD · [署名-非商业性使用 4.0 国际](https://creativecommons.org/licenses/by-nc/4.0/deed.zh)"

@vicevolf have you tried the above?

@vicevolf can you try placing copyright within a params like this:
[params]
  copyright = "©{ year } #0000CD · [署名-非商业性使用 4.0 国际](https://creativecommons.org/licenses/by-nc/4.0/deed.zh)"

Which settings file should I insert? My computer is recycled, haven't tried it yet, sorry.

The one specific to the main language you are using.

its work! https://github.com/vicevolf/test223/commit/41c2ccaa9d9aa2126b2c350b9d6deca8599a545c

Closing the issue


Clarification on metadata endpoint

There was an on-going discussion in #101 on the new metadata endpoint, but the discussion should have it's own issue (separated from the naming issue).
Imho, we should add a section that adds more clarity on the intended use of the endpoint introduced in this spec during verification (e.g., by making the resolution of the key using this endpoint mandatory during verification if the JWS header indicates web-based key resolution).
Perhaps adding a small part to the "Verification and Processing" section makes sense?
Prior discussion was here: https://github.com/vcstuff/draft-terbu-sd-jwt-vc/issues/101#issuecomment-1595828680

Relates to #168

Fixed by #175

Closing this issue since we merged PR #175


Can not enable E10M20-T1 on DS1621+

After execute the sh file, I still can not enable E10M20-T1 on my DS1621+ fully. It can not recognice my nvme ssd, only NIC work.
I've add DS1621+ in /usr/syno/etc.defaults/adapter_cards.conf file, both E10M20-T1_sup_nvme and E10M20-T1_sup_sata, but still not work.
After execute ls /run/synostorage/disks, it shows no nvme drives. ls /sys/block | grep nvme return
nvme0n1
nvme1n1

I think it may because 1621+ only have x4 lanes PCIe while E10M20-T1 has 8. But I think E10M20-T1 may be a plx card so it actucally can work on PCIe x4?

When I added support for enabling a M2D20, M2D18, M2D17 for models that don't officially support them I did wonder if the E10M20-T1 would work as both a NIC and NVMe on any NAS model.
On the DS1618+ is listed as supporting E10M20-T1_sup_nic, E10M20-T1_sup_nvme and E10M20-T1_sup_sata.

The Intel Atom C3538 CPU in the DS1618+ has 12 Gen 3 PCIe lanes which can be configured in x2, x4, x8.
The AMD Ryzen V1500B CPU in the DS1621+ has 16 Gen 3 PCIe lanes.

So you'd think the DS1618+ can fully support the E10M20-T1 then the DS1621+ should be able to as well.
There was someone who used the dual 10GbE E10G18-T2 card (in a DS1821+ I think) that found when both 10GbE ports were used the 2nd port ran at half the speed of the first port, due to not enough PCIe lanes.
According to this review the does have a PLX passthrough for the NVMe slots.
Were you wanting to use the NVMe drives on the  E10M20-T1 as a cache or volume?
Synology officially only support M.2 drives in PCIe cards as cache drives. But my Synology_M2_volume script can see the NVMe drives on a PCIe card and create the storage pool, then after a reboot you go into storage manager and create your volume.

Thanks for your reply. I just want to use the NVMe drives on the E10M20-T1 as a cache, the problem is I didn't see any drive on the E10M20-T1 in DSM.
I've found that RS1221+ supports E10M20-T1 which have same CPU and PCIe x4 slot like 1621+, so I think there may be a way to enable E10M20-T1 fully on 1621+.

Comparing synoinfo.conf between the RS1221+ and DS1621+ the only difference that may be related is the RS1221+ has:
netif_seq="3 2 1 0"
netif stands for network interface. Both models have 4 1GbE ports so I don't know why the RS1221+ has netif_seq="3 2 1 0" and the DS1621+ doesn't.
Both models have 99% the same files that contain E10M20-T1:

adapter_cards.conf
storage_panel.js
libhwcontrol.so
libsynodiskmap.so

The one file that is different is the binary dtb file located in model.dtb where the RS1221+ model.dtb file contains a section of M.2 PCIe cards including the E10M20-T1
I had to google what a .dtb file is:
"During the Linux boot process, a "Device Tree Blob" (DTB) file is loaded into memory by U-Boot / UEFI, and a pointer to it is passed to the kernel. This DTB file describes the system's hardware layout to the Linux kernel, allowing for platform-specific code to be moved out of the kernel sources and replaced with generic code that can parse the DTB and configure the system as required."
I could decompile both model's model.dtb files and then compile a new one but:

I don't know if DSM has checksummed that file and would fail to boot if it doesn't match the checksum.
Messing around with the boot process of my own Synology, let alone someone else's, is not something I'd want to try.

I noticed that the DS1618+ and DS1819+ support the E10M20-T1, M2D20 and M2D18 yet it have no model.dtb file. So I thought maybe the model.dtb file is only needed for models with a Ryzen CPU but then I noticed plenty of Intel CPU models also has the model.dtb file.
Without kernel support I think it may not be possible to make the DS1621+ see the E10M20-T1 (or any M.2 PCIe card) but I'll keep looking.

Omg, thank you so much for your thorough investigation. I am planning on attempting to modify my device tree file to see if I can get the E10M20-T1 to work fully on the DS1621+. Your research has given me valuable insights, and I hope that I can contribute some new information to this issue.
Once again, thank you for your work!

If you can figure it out I'd really like to know.
I've attached a copy of the model.dtb file from the RS121+ DSM 7.2-64570
RS1221+_DSM_64570_model-dtb.zip
Since my last reply I've found that model.dtb also exists in /etc/model.dtb after DSM is installed.
The DSM .pat file contains 2 identical copies of the model.dtb file:

/etc.defaults/model.dtb
model.dtb  <-- this one is in the root of the .pat file where all the boot files including bios.ROM and rd.gz etc and probably gets copied to synoboot.

 After modify model.dtb file, it works!

Following steps below

Use dtc -I dtb -O dts -o model.dts model.dtb  to decomplie dtb file to editable dts file

Add lost E10M20-T1 support. It comes from 1221+'s dtb file you gave to me.

Use dtc -I dts -O dtb -o model.dtb model.dts to complie dts file back to dtb file and replace /etc.defaults/model.dtb. Just only need to replace this file.

Reboot

Really thank you a lot!!!

Awesome. Thank you.

PS you're Synology account email address is showing in your first picture.

Thank you for your concern. However, please be assured that there is no problem. The account displayed is my publicly shared personal account, and I believe Synology would not object to my action.

Hi guys
Thanks for sharing !! Does it mean we can do this procedure with every model having a PCIE slot ? Why does synology removes stuff like this…
what happens after an upgrade of the dsm ?

I think it's not. This way is only for the device that use device tree. You can ls /dev, if your sata device show like "sata1, sata2..." it use device tree; if there are "sda, sdb...", it's not.

@karsayor What model Synology NAS do you have?
Editing the model.dtb file is only needed for DS1821+, DS1621+ and DS1520+
I have a pre-release version of this script that does it for if you have a DS1821+, DS1621+ or DS1520+ and have installed a E10M20-T1, M2D20 and M2D18
https://github.com/007revad/Synology_HDD_db/releases/tag/v3.1.57-RC

Hey
currently I have a 1618+ so the card is supported. But when it will be eol I plan to change for a new with PCIe x4 slot as well if I take the card.
A little bit too much future thinking I know 😝
But i find all this interesting to know. Maybe in 2-3 years I would swap my unit so i’m hopping to keep the card.
And I also wonder why Synology removes the support of this…

What PCIe card do you have?

And I also wonder why Synology removes the support of this…

In DSM 7.2-64570 Synology did add more Synology NAS models to support the M2D18 adapter card: RS822RP+, RS822+, RS1221RP+ and RS1221+. I have no idea why they didn't already support the M2D18 adapter card in DSM 7.0,.x and 7.1.x

E10M20

E10M20

Sorry, I forgot to answer your question. I doubt Synology would drop support for the E10M20-T1 but if they did I can enable it.
https://github.com/007revad/Synology_enable_M2_card

@FlintyLemming
Can you do me a favor and tell me what this command returns on your DS1621+
cat /sys/firmware/devicetree/base/power_limit && echo

14.52,7.26
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Dave Russell @.>
发送时间: Saturday, September 23, 2023 12:21:19 PM
收件人: 007revad/Synology_HDD_db @.>
抄送: FlintyLemming @.>; Mention @.>
主题: Re: [007revad/Synology_HDD_db] Can not enable E10M20-T1 on DS1621+ (Issue #97)
@FlintyLemminghttps://github.com/FlintyLemming
Can you do me a favor and tell me what this command returns on your DS1621+
cat /sys/firmware/devicetree/base/power_limit && echo
―
Reply to this email directly, view it on GitHubhttps://github.com/007revad/Synology_HDD_db/issues/97#issuecomment-1732206174, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AESHCR5ARGWTUQBRIXAYNF3X3ZPT7ANCNFSM6AAAAAAZQFALA4.
You are receiving this because you were mentioned.Message ID: @.***>

Interesting. Because you are using 4 NVMe drives I expected to see 4 power limit values instead of the regular 2.
Are you using DSM 7.2 Update 1, 2 or 3?

Oh I'm using 2 nvme ssds now, sorry for my misleading
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: Dave Russell @.>
发送时间: Saturday, September 23, 2023 4:23:43 PM
收件人: 007revad/Synology_HDD_db @.>
抄送: FlintyLemming @.>; Mention @.>
主题: Re: [007revad/Synology_HDD_db] Can not enable E10M20-T1 on DS1621+ (Issue #97)
Interesting. Because you are using 4 NVMe drives I expected to see 4 power limit values instead of the regular 2.
Are you using DSM 7.2 Update 1, 2 or 3?
―
Reply to this email directly, view it on GitHubhttps://github.com/007revad/Synology_HDD_db/issues/97#issuecomment-1732252194, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AESHCR6FM3XJSXPUVAQSUMDX32MA7ANCNFSM6AAAAAAZQFALA4.
 After modify model.dtb file, it works!

Following steps below

Use dtc -I dtb -O dts -o model.dts model.dtb  to decomplie dtb file to editable dts file
Add lost E10M20-T1 support. It comes from 1221+'s dtb file you gave to me.

Use dtc -I dts -O dtb -o model.dtb model.dts to complie dts file back to dtb file and replace /etc.defaults/model.dtb. Just only need to replace this file.
Reboot

Really thank you a lot!!!

I have already installed e10m20-t1 in 1821, but I cannot compile DTS. Has the latest script from the script author solved this problem? Can we directly install e10m20-t1.

@loonyd
I just answered your other issue https://github.com/007revad/Synology_M2_volume/issues/133
https://github.com/007revad/Synology_enable_M2_card does it all for you.

In other words, the two built-in SSDs I installed before have already formed raid0. Now I have added a new e10m20-t1 and a SSD. I want to run the script again to make a single storage space, but I don't want to delete the raid0 with two built-in SSDs that I have already completed.


Wiki Page 1.5: Definitions linking to 1.4

On the wiki page:
https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API
The documentation is for 1.5:
First you'll need to install TypeScript >=1.5 from npm.
Definitions Raw File
The definitions file is pointing to the 1.4 on the line:
Going directly to the source on our repository.
This links to:
https://github.com/Microsoft/TypeScript/blob/release-1.4/bin/typescript.d.ts
It should link to:
https://github.com/Microsoft/TypeScript/blob/v1.5.0-alpha/bin/typescript.d.ts
Definitions Installer
Also the command:
tsd query typescript --action install
Installs the 1.4 definitions files

Have fixed the link but not sure what to do about the tsd command
#5

Don't worry about the tsd command, I'll take care of it now. Thanks for the PR!


fix: Add Volume button on Cloud Manager Linode page causing browser to freeze

Description 📝
Reverts the changes from this PR to remove the useEffect so that the page doesn't crash. Note that this means there will be a console error again - we'll have to look into how to handle that issue differently.
Changes  🔄

Reverts change to remove useEffect

Target release date 🗓
10/2
How to test 🧪
reproduction steps

On the Linode Storage tab, when clicking 'Add Volume', notice how the page freezes afterwards

Verification steps

confirm the page freeze no longer happens

As an Author I have considered 🤔
Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

I may have answered my own question after reading this:

React only lets you update the same component’s state during a render. If you update another component’s state during a render, you’ll see an error. A condition like items !== prevItems is necessary to avoid loops. You may adjust state like this, but any other side effects (like changing the DOM or setting timeouts) should stay in event handlers or Effects to keep components pure.

Merging this to staging as all checks have passed! @bnussman-akamai you might need to resolve a small changelog conflict afterwards


Missing Key Annotation

Hello,
Thanks for releasing the data the annotation 1124 for the Baseline-FORGE2020 seems to be missing.
Maybe a wrong parsing ?
Kindest regards

@nilinykh, could you please have a look? It is about this file:
https://github.com/WebNLG/webnlg-2020/blob/main/submissions/rdf2text/en/Baseline-FORGE2020/human/primary.json


Which Alphabet?

It appears there can be different Base64 "alphabets" depending upon the transport protocol to be used. As such, it would be advisable to document which alphabet is in use and which standard (if any) it matches.

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

ID: ddf7e483-b740-8572-f7d0-57d7a09ad79a
Version Independent ID: 58a76596-0e63-5347-1fd3-bedd3f6e5348
Content: CryptographicBuffer.EncodeToBase64String(IBuffer) Method (Windows.Security.Cryptography) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.security.cryptography.cryptographicbuffer.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: lastnameholiu
Microsoft Alias: alholiu

Hi @kburgoyne , thanks for submitting your feedback. Appreciate you pointing this out. I'll pursue this suggestion and add in a work item to get it fixed. Look back for this thread for updates in the future once this is completed.

Hello. We apologize for the delay in resolving this issue. As we transition to a new feedback system, we are closing all outstanding issues. Any issues that can be addressed will be tracked using a different internal tool, and we regret that we won't be able to provide further updates on this particular matter. We value your input and assure you that all feedback is reviewed. We recommend visiting the Microsoft Q&A site, where your issue may have already been discussed.


Types are not being included with the package

Bug Description
When pip installing fideslang the types are not being included even though they are present so when using the package types have to be ignored.
Steps to Reproduce

Install fideslang
Run mypy

Expected behavior
Types should be included.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Version: 1.3.3
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

solved when I switched things over to pyproject.toml, as it includes package data by default


Remove references to EOL Windows 10, version 1903

There are several references to Windows 10, version 1903 which is EOL.  All of these references are related to containers.  I've updated the container image tags to not reference OS-specific tags. This makes their maintenance easier and still gives the same effect as if the OS had been defined.

@mthalman : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mthalman - can you confirm theses changes are still needed, and if so add the following comment to your PR: #sign-off. Thank you! If it is no longer needed, please close this PR. Thank you

#sign-off

@mthalman: I'm sorry - only the author of this article, @ghogen, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.