warning on invalid exif data

Another feature related to the exif data. Some exif data in our images (in that case not legacy ones, they were synced yesterday) is invalid:
$ curl https://iiif.bdrc.io/bdr:I8LS26144::I8LS261440003.jpg/full/full/0/default.jpg -o full.jpg
$ exiftool full.jpg |grep Warning
Warning                         : IFD1 pointer references previous ExifIFD directory

This makes the thumbnail impossible to extract by exiftool, and I think is a probable cause of the iiif server not reacting well when trying to extract the icc profile.

@TBRC-Travis Please find out the source of this image.

This is from W8LS20439 which I synced from the Mangaram backlog

 Why we need a platform

to give a bit more context: the iiif server is happy with this image and so are the web browsers so it's fine. I encountered this issue while trying to extract the jpg thumbnail from the image with exiftool (to measure its size I think), but it's not at all a common usage of our images so I think we can live with it. I also can't reproduce this issue in Java


Numpy nonzero large tensor fix

This fixes nonzero against large tensors.
Also cleaned up the loop a little bit.
Because of cub uses int in function declaration this pr only fixes the cpu version

@mxnet-bot run ci [unix-gpu ]

Again pytest run results ?

Again pytest run results ?

?? rest LGTM!

Again pytest run results ?

?? rest LGTM!

Sorry I was working on another task. Will make the changes and paste run results here before requesting for merge.

test result:
ubuntu@ip-172-31-38-169:~/incubator-mxnet$ pytest tests/nightly/test_np_large_array.py::test_nonzero
/home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
  return f(*args, **kwds)
/home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
  return f(*args, **kwds)
/home/ubuntu/anaconda3/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
  return f(*args, **kwds)
============================================ test session starts =============================================
platform linux -- Python 3.7.7, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /home/ubuntu/incubator-mxnet, inifile: pytest.ini
plugins: remotedata-0.3.2, openfiles-0.4.0, astropy-header-0.1.2, hypothesis-5.8.3, arraydiff-0.3, doctestplus-0.5.0
collected 1 item

tests/nightly/test_np_large_array.py         .                                                                 [100%]

============================================== warnings summary ==============================================
tests/nightly/test_np_large_array.py:88
  /home/ubuntu/incubator-mxnet/tests/nightly/test_np_large_array.py:88: DeprecationWarning: invalid escape sequence \
    '''

tests/nightly/test_np_large_array.py:568
  /home/ubuntu/incubator-mxnet/tests/nightly/test_np_large_array.py:568: DeprecationWarning: invalid escape sequence \
    '''

-- Docs: https://docs.pytest.org/en/latest/warnings.html
================================= 1 passed, 2 warnings in 166.16s (0:02:46) ==================================

@mxnet-bot add [pr-awaiting-merge]


Tablesorter headers not working in 2.0-wip

While doing some more testing against 2.0-wip, I noticed that the tablesorter styles (mouse pointer, up/down arrows) are no longer compiled in to the CSS.  They are currently commented out in the tables.less file: https://github.com/twitter/bootstrap/blob/2.0-wip/lib/tables.less
Is there a reason for this, or is it just an oversight?

They're back now in 2.0-wip.

Awesome, thanks!  Didn't want to send a pull request in for out just in case it was done on purpose...


upgrade(meta): noarch

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [29].
License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin please rerender

@conda-forge-admin please rerender


Using ID's Dragonform skills crashes the game with GBFR installed

While using ID's Dragonform, if you use RB+X or RB+Y, there's a 50/50 chance to crash the game, not only for you, but for anyone using GBFR in the party.
GBFR version : 1.6.1
Granblue version : 1.3.2

It happens very frequently when fighting Proto Bahamut in the quest : The Tale of Bahamut's Rage. Only when casting RB+X or RB+Y while in ID's Dragonform.

Fixed in https://github.com/false-spring/gbfr-logs/commit/572a6a080a9527cefae88c0ce32902eac1215ad7


CLI Version for Create bulk dummy documents in SharePoint Document library

Add CLI version for:
https://pnp.github.io/script-samples/create-dummy-docs-in-library/README.html?tabs=pnpps

Can you please assign this to me?

Hi @Jitenparmar - I'm going to release for others to contribute to, please let us know if you are planning on working on this one :-)


[!!!TASK] Make all classes final

This library has a very large number of extension points via interfaces and abstract classes. All other classes should not be extended by users and shall theirfor be marked as final.
There are a few classes left that should also be marked as final but those require some extra attention.

:+1:
I see you also made some DTOs final (without interfaces). If these DTOs are part of the public API (either return or parameter type), this can block legitimate extension points (e.g. you can not add new properties to such DTO from a decorator). Not sure if this applies to any of the classes in this PR, but just so you are aware of this.

Thanks @wouterj, I'm aware that this might block extensions, I think we need some extra interfaces, I will review that per case.  However I think some of the helper classes will be marked as internal and should never be exposed to the world as they are part of the internals of this libraries.


Broken link in Contributing.md file

The link for google's javascript guide line is broken in Coding Rules Block.
url: http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml

Nice reason for small PR

@valorkin , Thanks for the encouragement. pull request #3171 has been submitted for the same.


Refactor renderer::launch so it doesn't handle the filesystem.

Users of renderer::launch will probably want more control over the title of the window and how save files are accessed. This PR makes it so the caller of renderer::launch decides what is done when the game calls diskr and diskw.
Changes:

renderer::launch now takes a Backend, display scale, title, and two callbacks for reading and writing the save files.
--save-path/-s option added for the CLI.

The old -s option (display scale) has been changed to -d (display scale) because -s fits --save-path much better than --display-scale.

A module has been created at cli/src/disk.rs which holds functions that create common callbacks for writing and reading save files. This is used by the CLI and is now created in wasmstation template projects. It was not included in the main wasmstation crate because I'm trying to keep that OS-independent in the future (for embedded).
The CLI now imports log to emit a nice error message when the cart bytes can't be read. In the future I'd like to remove all instances of .unwrap() and .expect() in the CLI and have it only emit nice looking errors from pretty_env_logger.

Hi Grant,
I agree with the change so far. However, you could probably improve usability by moving the callbacks and possibly other things into a LaunchConfig struct, which has sensible defaults. This way, the caller of launch() will not have to figure out what to pass if they don't want to mess with the details. If they do want to change the behaviour, they can have a look at the LaunchConfig struct and drill deeper. If not, they'll simply pass Config::default().
While suggesting this is easy, it may have some pitfalls though because LaunchConfig will proably have to take type parameters as well, for which sensible defaults will have to be provided as well; so it may not be as simple as just implementing the Default trait for the LaunchConfig struct. So maybe this suggestion is more for another change rather than putting it on top of this one.

Alright, here's what it currently looks like:
classDiagram
    class LaunchConfig {
        +DiskManager disk
        +u32 display_scale
        +String title

        +from_path(cart) Self
        +from_name(name) Self
    }

    LaunchConfig <.. DiskManager

    class DiskManager {
        +read()
        +write()
    }

    DiskManager *-- DebugDisk
    DiskManager *-- UserwideDisk
    DiskManager *-- Wasm4CompatibleDisk

    class DebugDisk
    note for DebugDisk "prints log messages on read/write"

    class UserwideDisk {
        +new(name) Self
    }

    class Wasm4CompatibleDisk {
        +new(cart_path) Self
    }

I'm not that familiar with UML/class diagrams so I'm not sure exactly if this is how it's supposed to be used but I think this demonstrates what's happening.
Looks good?

Eh, now that I think more about the refactors I'd like to do I don't think this abstraction is particularly useful. renderer::launch is explicitly for rendering on the desktop (which has filesystem access). It's not a big deal to have the desktop renderer access the filesystem. The web renderer will be in charge of managing save files too, it can store it in its own way.


[Diagnostics] Don't assume that contextual type for optional chain is optional

While checking validity of the optional chain, let's not assume
that the contextual type associated with is optional because
enclosing expression could too be invalid.
Resolves: rdar://85166519

@swift-ci please smoke test

Just going to land it, since the change is trivial.


Documentation of what happens when you submit a search query

This new doc aims to explain what happens when you submit a search query at a high level (e.g. searching from a plane).
With this kind of general doc it's hard to know how detailed to get.
If you spot places where more detail would be useful (in this doc, or in an additional doc) let me know.
https://trello.com/c/l36JE4uU/820

Thanks, @barrucadu, I made some changes to the commit. Could I ask for another review?

Thanks, I made a couple of changes.


jsSchedulingOverhead warnings

I'm quite embarrassed to say that I'm finally getting around to debugging my JSX code on the phone.
I'm getting these jsSchedulingOverhead warnings:

Should I be worried? Could it be caused by the fact that I'm debugging w/ chrome?

What it means is that the start date passed on the timer creation (Date.now() on JavaScript) is 800ms ahead of the current time on iOS ([NSDate now]), when you're running the app on the device and the executor on your computer it's very unlikely that the times will be the same at the millisecond level. So no, don't worry about it.

How can I not worry about though warrnings obscure a half of screen and I can't disable them...

I don't know if you realise, but this issue is from 6 months ago, and at the time there were no YellowBox, but yes, you can disable them, try:
console.ignoreYellowBox = ['jsSchedulingOverhead'];

@nicklockwood maybe we should remove this warning?

@tadeuzagallo I've no context on what this warning means, but it seems very spammy. Maybe YellowBox should have an upper limit on warnings displayed at once?

@tadeuzagallo looks like it's console.ignoredYellowBox not console.ignoreYellowBox

pasted console.ignoredYellowBox = ['jsSchedulingOverhead'];  on my code and it worked on the phone, but Xcode still shows the warning.

Do you have any workaround for this? for now I put my computer some seconds behind.

This warning is clogging up my Chrome console, repeating indefinitely and obscuring all relevant console logs. Is there any way around this except changing the computer's cloclk? console.ignoredYellowBox = ['jsSchedulingOverhead']; only removes the warning from the phone, not the Chrome or Xcode consoles.

+1
This is happening to me too, and making debugging while running on a device impossible. Why is this request closed?
It's clearly affecting a bunch of other people, cf: https://github.com/root-two/react-native-drawer/issues/44, https://github.com/facebook/react-native/issues/2046, https://github.com/lwansbrough/react-native-camera/issues/32, https://github.com/facebook/react-native/issues/5136 etc.
Thanks

Temporary workaround: comment out line 179 of React/Modules/RCTTiming.m

+1

Re-opening because this is a common problem when developing on a device.

+1

+1. Seems commenting out that line is the only effective way remove . by @lrettig https://github.com/facebook/react-native/issues/1598#issuecomment-172890857

+1

+1

I agree with everyone that this is an annoying issue developing on a device. I've pushed a possible fix in https://github.com/facebook/react-native/pull/5731, will try to poke some people at Facebook to review the change.

@lrettig your commenting out method works well

+1

+1

Wow this is a year old simple issue and still has no progress!

Warning removed in https://github.com/facebook/react-native/commit/2d27cf0ceb6441e0044e9dada3482fd6fe2672df. Sorry that took so long!


Add/local dev env

Description
Adds the first step towards integrating local dev environment into vip command.
This adds vip dev-environent start command. Which will create (if non-existing) and start the environment.
It is a slightly reduced version of our internal tool. Things I dropped to make it easier for the first step (we can add them later):

lookup of config by site id
auto cloning of clients code (client can still clone their code manually and point to the path of that)
more operations (stop/destroy) - TBA in follow-up work

Maybe the command should be first hidden behind a isVIP flag for the first iteration untill we get support for all operations. For that we could use https://github.com/Automattic/vip/pull/699 after merged.
Steps to Test
Try variants of command. Use --help to learn about a possible parameter. Please let me know if help doesn't make sense or is incomplete in some sense.
It's usefull to have export DEBUG="@automattic/vip:bin:dev-environment,@automattic/vip:bin:vip" to see more info like instance path so you can remove that folder to start fresh.

Should we consider shortening this to dev-env or even just dev?

@rinatkhaziev I am thinking it is OK to be more verbose especially as this is end customer-facing. I would be OK to shortening it to dev-env (although I think dev-environment is better as that leads to less confusion about what the env means :) ).

Thanks for the feedback - @netsuso !
In my mind, most of the end users won't really work with multiple dev-environments (I know I rarely am, and that is only because I have one multisite and one single site). Which makes commands related to the management of environments kinda less important (like list, stat) imho. So you know I would wait for a feedback before building those up.
Now we have full control of the commands we want to provide, and I think it would be great if we split it and provide two commands:

create: it receives all parameters to configure the environment, but it doesn't start it
start: simply starts an existing environment. So you can start it, then stop it, and start it again, without needing to recreate it.

The current start command does both create and start. If you have already an existing environment it will just work as start in your example. If you don't it will create it and then start as our sandboxes do. I kinda like this simplicity. What drawbacks do you see to this approach. On the other hand, I don't have a too strong opinion on this, so I am fine with splitting it as you suggest.
The one thing I would push against is making the slug positional and therefore required argument in the dev-env operation. Again I am kinda expecting that in most cases the user will only really have one environment.

In my mind, most of the end users won't really work with multiple dev-environments

I'm not sure about this... There are quite a few customers that run multiple sites, and I bet they will want to have multiple dev environments for them. But maybe @parkcityj has a more informed opinion on this :)

In my mind, most of the end users won't really work with multiple dev-environments

I'm not sure about this... There are quite a few customers that run multiple sites, and I bet they will want to have multiple dev environments for them. But maybe @parkcityj has a more informed opinion on this :)

Actually, we could even consider that the slug becomes the siteid+environment, which is the usual way of handling the vip tool. In that case. For the most cases, we want to allow customers to simply "create an local dev env for this siteId/environment". The only problem is that we wouldn't allow multiple dev envs for a single site, but that might be not so important...

In my mind, most of the end users won't really work with multiple dev-environments

I'm not sure about this... There are quite a few customers that run multiple sites, and I bet they will want to have multiple dev environments for them. But maybe @parkcityj has a more informed opinion on this :)

Actually, we could even consider that the slug becomes the siteid+environment, which is the usual way of handling the vip tool. In that case. For the most cases, we want to allow customers to simply "create an local dev env for this siteId/environment". The only problem is that we wouldn't allow multiple dev envs for a single site, but that might be not so important...

I like that idea. We can always leave the option to put a custom name for the environment (and therefore have more of them), as it is now. We would just change the default name to be more dynamic (if they provide site id that is).

There definitely will be customers using this for many sites (think partner agencies' developers or the likes of NCA which have dozens of sites)

The only problem is that we wouldn't allow multiple dev envs for a single site, but that might be not so important...

Agree on this one.

Yes, I think a lot of customers will spin up multiple dev environments for different applications - likely including their nonproduction apps.   The way the CLI currently works is vip @appname.environment - so that should still work fine, as long as running multiple apps is supported.

I split the start to create and start commands. I also added some more usefull error messages (e.g. when you try to start environment that doesnt exist or create one that already exists).

I split the start to create and start commands. I also added some more usefull error messages (e.g. when you try to start environment that doesnt exist or create one that already exists).

I think we can go ahead with the current branch, to avoid making it much bigger, so we can merge it and keep working on it. E.g, I'd suggest adding stop and destroy/remove commands, as they should be easy and give a lot of value.

Should we at some point add more commands, such as list, stop and delete? I think this would make this even more powerful, we could then maybe even remove the defaultSlug and replace it with a random string, similar as Docker does for containers.

Yep, this is just the initial branch, but there will be more to come. You can also read my comment about what you mention :)


Added checkPreAuth call before checkPostAuth

By adding this check it's possible to add the default checks isAccountNonLocked, isEnabled & isAccountNonExpired by using the AdvancedUserInterface.

@tmilos it looks like there is an error with the HHVM configuration;
HHVM needs to be a minimum version of HHVM 3.9.0
Is this a configuration issue?

Aha... the php-cs-fixer issue. Thanks, I'll upgrade that in separate issue.
Thanks for the PR


Yaml File Not Loading from default Folder

Yaml Files is not being loaded from default folder.
The program is always is looking into /etc/pg2mongo/pg2mongo.yml if the file is not present there program gets terminated.

This has been involved in the current push. It doesn't have to be /etc/pg2mongo/pg2mong.yml anymore.. it can be accessed from the current working directory.


Ignore blank lines in csslint output

csslint outputs errors as blocks for each file, with a blank line separating them. Including these lines in the call to extract_messages results in the error:
Unexpected output: unable to determine line number or type of error/warning for message

Merged in c977e5a.


Use JaCoCo 0.8.1 by default

This JaCoCo release is mainly about Java 10 support.
Full changelog - http://www.jacoco.org/jacoco/trunk/doc/changes.html

Thanks @Godin !


racerd: 2019-03-20 -> unstable-2019-09-02

Motivation for this change
while reviewing #70309 I noticed it was broken, most likely from the rustc bump.
Updating the project seems to have fixed the build.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @
[2 built, 0.0 MiB DL]
https://github.com/NixOS/nixpkgs/pull/70313
3 package were build:
rustracerd vimPlugins.YouCompleteMe ycmd

@GrahamcOfBorg build rustracerd vimPlugins.YouCompleteMe ycmd

Thanks!
ported to 19.09 in https://github.com/NixOS/nixpkgs/commit/8e1ce32f491422e0944f398eb24f653f8499b1a8

I had to revert the backport, as the bump actually breaks builds for rust<1.38. This will still need to be backported if we decide to bump rustc for 19.09
revert https://github.com/NixOS/nixpkgs/commit/4a10b030ce9a67c3c04e72e315460432248050f4


Handling tab change?

When you leave the game for a moment (inactive tab) and you come back, there's graphic bugs.

Can we detect tab change?
We need to investigate that matter...

See https://github.com/Elao/curvytron/issues/110


Make Integer comparison spec compliant

This also changes the way Floats are converted to bignums. Instead of using dtoa I now use snprintf (see the new String constructors). This seems to yield similar results to ruby. For example applying dtoa to<PHONE_NUMBER>854775847.0 yields<PHONE_NUMBER>854776000.0 but snprintf yields<PHONE_NUMBER>854775808.0 which is what ruby returns.

This looks great. I originally imported dtoa in this commit because I couldn't get snprintf to produce the same results as Ruby. But if you figured it out (seems the specs agree with you :smile:), then this is great. Can we remove dtoa.c entirely?


Headers in codeblocks should be ignored

I noticed that # within Codeblocks (within 3 backticks) are taken into account for the table of content.
Additionally, they are rendered within the codeblock.

Uhm... nasty. This could be a bug in the discount markdown library.
Did you try escaping the #s with a backslash? That normally does the trick. Not ideal, but a workaround at least!

Uhm... nasty. This could be a bug in the discount markdown library.
Did you try escaping the #s with a backslash? That normally does the trick. Not ideal, but a workaround at least!

I haven't tried escaping yet. I must admin that the document is kind of strange. I have a rather large codeblock there with hundrets of short lines, many of them begin with a hash.
I also noticed this message twice when processing the .md: (!) Snippet 'catalogReturnLink' not defined.
Unfortunally, I could not give you the source because it contains secret internals of our company.
So I just tried to assemble a simple document which triggers the behaviour.
For this I created that:
# Test

## Test

```
# comment
# another comment
a string with backslashes d:\folder\file.ext
; somthing *else*
# everything within a code block should be printed out as is?
```

But with this, I get this error:
fatal.nim(49)            sysFatal
Error: unhandled exception: index out of bounds, the container is empty [IndexDefect]

I haven't tried escaping yet. I must admin that the document is kind of strange. I have a rather large codeblock there with hundrets of short lines, many of them begin with a hash.
I also noticed this message twice when processing the .md: (!) Snippet 'catalogReturnLink' not defined.
Unfortunally, I could not give you the source because it contains secret internals of our company.
So I just tried to assemble a simple document which triggers the behaviour.
For this I created that:
# Test

## Test

```
# comment
# another comment
a string with backslashes d:\folder\file.ext
; somthing *else*
# everything within a code block should be printed out as is?
```

But with this, I get this error:
fatal.nim(49)            sysFatal
Error: unhandled exception: index out of bounds, the container is empty [IndexDefect]

OK this is weird, I just ran the snippet you posted through HastyScribe and didn't get any error, furthermore the conversion looks alright, and #s within the code block are ignored:

Test

Test

# comment
# another comment
a string with backslashes d:\folder\file.ext
; somthing *else*
 # everything within a code block should be         printed out as is?

There must be something else in your document that causes that behavior.
The other error about the snippet not being found should be due to a string like {{catalogReturnLink}} somewhere in your document. That basically is a reference to a text snippet (which is however not defined anywhere) according to HastyScribe syntax.

OK this is weird, I just ran the snippet you posted through HastyScribe and didn't get any error, furthermore the conversion looks alright, and #s within the code block are ignored:

Test

Test

# comment
# another comment
a string with backslashes d:\folder\file.ext
; somthing *else*
 # everything within a code block should be         printed out as is?

There must be something else in your document that causes that behavior.
The other error about the snippet not being found should be due to a string like {{catalogReturnLink}} somewhere in your document. That basically is a reference to a text snippet (which is however not defined anywhere) according to HastyScribe syntax.

Hello, thank you. Yes, I tried the last example again by myself, and it worked. I think I should better hit save in the editor before trying something like this. Ok, I'll try to derive a document from the real one to narrow down the cause - tomorrow.

Hello, thank you. Yes, I tried the last example again by myself, and it worked. I think I should better hit save in the editor before trying something like this. Ok, I'll try to derive a document from the real one to narrow down the cause - tomorrow.

Just tested the suspicious codeblock alone, and it just works well.
So the reason for the "hickup" is some other fact.
I'll investigate further....

Just tested the suspicious codeblock alone, and it just works well.
So the reason for the "hickup" is some other fact.
I'll investigate further....

While testing, the following failed:
```
    <location path="Default Web Site">
        <system.webServer>
            <handlers accessPolicy="Read, Execute, Script">
                <add name="Tclsh" path="*.tsh" verb="*" modules="CgiModule" scriptProcessor="D:\htdocs\cgi-bin\cgitcl.exe "%s"" resourceType="File" requireAccess="Execute" />
            </handlers>
            <security>
                <authentication>
                    <windowsAuthentication enabled="true" />
                    <anonymousAuthentication enabled="false" />
                </authentication>
            </security>
        </system.webServer>
    </location>
    <location path="Default Web Site/cgi-bin">
        <system.webServer>
            <handlers>
                <add name="ZoomSearch" path="*.cgi" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" />
            </handlers>
        </system.webServer>
    </location>

</configuration>
```

The resulting webpage looks like this:
``` <system.webServer> </system.webServer> <system.webServer> </system.webServer>
``

It should't matter what´s inside the backticks?

While testing, the following failed:
```
    <location path="Default Web Site">
        <system.webServer>
            <handlers accessPolicy="Read, Execute, Script">
                <add name="Tclsh" path="*.tsh" verb="*" modules="CgiModule" scriptProcessor="D:\htdocs\cgi-bin\cgitcl.exe "%s"" resourceType="File" requireAccess="Execute" />
            </handlers>
            <security>
                <authentication>
                    <windowsAuthentication enabled="true" />
                    <anonymousAuthentication enabled="false" />
                </authentication>
            </security>
        </system.webServer>
    </location>
    <location path="Default Web Site/cgi-bin">
        <system.webServer>
            <handlers>
                <add name="ZoomSearch" path="*.cgi" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" />
            </handlers>
        </system.webServer>
    </location>

</configuration>
```

The resulting webpage looks like this:
``` <system.webServer> </system.webServer> <system.webServer> </system.webServer>
``

It should't matter what´s inside the backticks?

I think I got it!
I'm very sorry. I had a construct somewhere like this:
...... [...comment....].......

I think the square brackets are interpreted as part of a link structure like this:
[name](url)

After I changed the text to
.... {...comment...}......

everything works fine!

I think I got it!
I'm very sorry. I had a construct somewhere like this:
...... [...comment....].......

I think the square brackets are interpreted as part of a link structure like this:
[name](url)

After I changed the text to
.... {...comment...}......

everything works fine!

Just tried another example, but it works perfectly well:
# Test

```
# Test11
Other
## Test12
```

Wrong link: [Something in square brackets] not directly followed by (round brackets)

```
# Test21
Other
## Test22
```

It seems to me that the reason for the error was a unknown combination of things which I couldn't easily put into an easy example for testing yet.

Just tried another example, but it works perfectly well:
# Test

```
# Test11
Other
## Test12
```

Wrong link: [Something in square brackets] not directly followed by (round brackets)

```
# Test21
Other
## Test22
```

It seems to me that the reason for the error was a unknown combination of things which I couldn't easily put into an easy example for testing yet.


How to use the routing model in lumen

I'm used "  'bindings' => \Illuminate\Routing\Middleware\SubstituteBindings::class "  in lumen
but  it's wrong
Target [Illuminate\Contracts\Routing\Registrar] is not instantiable while building [Illuminate\Routing\Middleware\SubstituteBindings]
How do I solve it

Hi there,
Welcome to Laravel and we are glad to have you as part of the community.
Unfortunately this GitHub area is not a support area for general application issues. This is only for issues/bugs with the framework code itself.
I will be closing your ticket here. Instead please try asking your question on one of the many great community support areas that will likely give you a better answer more quickly:

Laravel Slack (https://larachat.co/)
Laravel.io Forum (https://laravel.io/forum)
Laracasts Forum (https://laracasts.com/discuss)
StackOverflow (http://stackoverflow.com/questions/tagged/laravel)

If you feel I've closed this issue in error, please provide more information about how this is a framework issue, and I'll reopen the ticket.
Thanks in advance.


Can't upload files in the Windows client

I drag and drop files in to the Keybase "Files" UI and the files don't get uploaded.

I was having the same issue for Windows 10. I think I was at Windows version 1903, but updated to 1909 last night. Now I seem to be able to upload files correctly.


Invoking Quick Tabs on Chrome 79 closes all tabs(?)

I've submitted this to Google as feedback on Chrome behavior. But am I the only person experiencing this? Is it my imagination? Thanks:

Chrome v. 79.0.3945.88 (Mac OS) appears to be incompatible with the "Quick Tabs" extension. Invoking the extension frequently causes all open tabs to close. I first noticed this bug in Chrome v. 77 or 78, and reported it – but I've just identified "Quick Tabs" as the trigger for tabs closing.
"Quick Tabs" is not optional for my work. This extension provides an MRU (Most-Recently Used) list of tabs, allowing rapid reopening of closed tabs.
This is an essential productivity feature that should have been native to Chrome long ago. Instead, the removal of Add-Ons, and current restrictions on Extensions, have both diminished Chrome's native features, and hobbled what Extensions can fill in.
Please work with the developer to resolve the apparent incompatibility between recent Chrome versions and this essential Extension.

One possible cause could be having no key mapping assigned to the 'Close all displayed tabs shortcut', I'm taking that option out inn the next release to replace it with a popup command to make things a little more predictable / deliberate

@babyman: Thanks, I just (re-)assigned a key mapping to that command, to see if it helps.
I might have slightly misstated the glitch: Chrome doesn't close all tabs, nor exit. It closes all open tabs, while restoring the one tab I requested from the MRU list.

@babyman: I've experienced no collapsed tabs since I restored a key mapping for the 'Close all displayed tabs' shortcut. If this holds up, I'm assuming you analyzed this accurately. Thanks.

Nice, I have completely replaced the 'close all' shortcut with a search command /close <query> to help avoid this.

Please feel free to reopen this ticket if you see the issue again
Evan


handle edge case of more than 5 lines in title

This also dynamically scales the font size down as the number of lines increases so that it can more easily fit in the image. Scaling down by 5 points per line seems to be okay for all the images on my blog, the main objective was solving the 5 lines problem.
The other alternative would be to increase the characters per line, but without the final else there would always be the possibly that a user overruns.

Hi @mark-pitblado, thank you a lot! I'll have a look and merge it soon.

Okay, LGTM, merging it shortly. Thanks again!


HMR gets 404 on .hot-update.json

Version: 2.0.0
When webpack configuration has publicPath = "/" (build everything to root) ConditionalProxyMiddleware fails to proxy requests to webpack-dev-server. In my case all requests to root (like http://localhost:5000/7d8b1be5454ed9e44b78.hot-update.json) fails with 404.
It was working fine for preview2 but does not work for new bits.
After reviewing/debugging your code I found that the following lines were added to ConditionalProxyMiddleware.cs:
             if (!pathPrefix.StartsWith("/"))
             {
                 pathPrefix = "/" + pathPrefix;
             }

then it actually fails when performing a check:
        public async Task Invoke(HttpContext context)
        {
            if (context.Request.Path.StartsWithSegments(_pathPrefix))
            {
                var didProxyRequest = await PerformProxyRequest(context);
                if (didProxyRequest)
                {
                    return;
                }
            }
...

Here if _pathPrefix is "/" and context.Request.Path = "/7d8b1be5454ed9e44b78.hot-update.json" then StartsWithSegments will return false.
Interesting that pathPrefix in ctor is actually an empty string (passed from WebpackDevMiddleware). That is why it was working for previous (preview2) version.
The fix would be to skip inserting slash in case pathPrefix is an empty string. Or change the code of actual check in Invoke method.
Please let me know if you want me to submit a pull request.

I'm wondering if this is what's causing the EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection. that's causing HMR not to work as well.

Thanks for reporting this. It's now fixed.

is there a quick workaround for this?
thank you

@spnm , yes. You will need to change publicPath to something different for development build only.
Assume you have isProduction variable then the code in your webpack.config will look like this:
if (!isProduction) {
    clientConfig.output.publicPath = "_/";
    serverConfig.output.publicPath = "_/";
}

I have a fully functional example/template here:
https://github.com/mocoding-software/spa-template

This bug is not fixed.
New workaround:
if (!isProduction) {
    clientConfig.output.publicPath = "/_/";
    serverConfig.output.publicPath = "/_/";
}

Looks like this may be fixed in the dev branch but not part of 2.0.1?


Modify build-up & tear-downs in ServiceRegistryJpaImplTest so Travis CI won't choke

Describe the bug
When Travis CI attempts to run resource intensive junit tests, such as in ServiceRegistryJpaImplTest, the tests get Assert errors when they should not get Assert errors. This only happens in the Travis CI environment and appears to be a limitation in the Travis CI environment.
To Reproduce
Steps to reproduce the behavior:

Run the ServiceRegistryJpaImplTest junit tests a few hundred times in a non-Travis CI system
Never see an assert error from ServiceRegistryJpaImplTest
Run the ServiceRegistryJpaImplTest junit tests 3-4 times in Travis CI
See Assert error in various places
(NOTE: the "ERROR ...Job with Id 1 cannot be deleted"  is normal and not part of the issue with the junits. That line can be ignored)

Environment Information

Opencast github Travis CI

Possible solution:  The fails appear to be race conditions associated to the build up and tearing down of test resources around each test in that class. It might help if the core test resources are built at test class load and kept in tact between each test, only cleaned between tests, but not torn down between test. Tear down all resources when the class unloads.
Related issue: #1281

Also related to #1068

FYI -  My concern is that valid junit tests are being actively removed from the code base because Travis CI occasionally says something like  1 + 1 ==  3 , not 2. The "temporarily" ignored tests are being stripped from the code base to "clean up the code". Yet, the code that the junits were testing is still left in the code, just in an untested, unprotected, state.

Sorry to tell you that these issues are not at all limited to builds on Travis CI. I've been regularly restarting builds on Greg's buildbot cluster since they fail with the same issue and I have seen this locally as well though far less often. Generally, it seems like the more powerful the machine you are building on, the less likely it seems that the issue will pop up.
I agree that having tests is nice but if they happen to fail on a regular basis – which the ones we got rid of clearly did – they are hurting the project far more than the tests help. I have seen people ignore failed builds a few times already since “it must be a Travis/buildbot issue” while it was not and thus broken code got in. That's not good. It makes the tests untrustworthy and additionally causes work since (mostly Greg or I) need to restart the tests.
All in all, I'm happy about more tests. But they must be rock-solid and not cause any false build errors.

Adding on to @lkiesow's comment, I think there is a sweet spot where this happens.  I see it on ci.opencast.org, and Travis.  I see it on my testing cluster at home here, but not on my dev machine which is particularly low powered.  I think there's a minimum spec before it starts to trigger, which suggests to me that @karendolan is right and it's somehow related to setup/teardown.
If you want to spend time on this, have at it, but I suspect the ROI here is low considering the change velocity in the SR.

@gregorydlogan  and @lkiesow  the issue was a race condition with the test asserts and the dispatch loop timing. The jobs get into an intermediate state during dispatch and a normalized state after dispatch. The assert errors were when the assert timing got the job when it was in the middle of the dispatch process. Adding extra control in the tests to launch the dispatch process prior to doing an assert mitigates the test timing issue.


Use cos-lib instead of a fork of AlertRules

Enhancement Proposal
Recently we encountered some issues that in part result from deviating from cos-lib:

#353
#340

We should eliminate the existing code duplication. Some refactoring may be needed:

Maybe change AlertRules.add_path to take a topology arg, instead of passing it to the loki-push-api constructor.
Why cos-config has "skip" topology for logs but not for metrics?

As #331 already introduced the dependency on cosl, it should be (hopefully, ideally, in a perfect sphere-shaped world) transparent to include.


chore: added smooth transition for sidebar accordion

Fixes Issue
Closes #596
Changes proposed
I have added a smooth transition for the opening and closing of the accordion in the sidebar.
Screenshots
https://github.com/rupali-codes/LinksHub/assets/77151837/fe6aa947-9f6f-47a9-ba32-0750e55607ff
Note to reviewers
For the file where I did my changes, there is an "isOpen" prop that is no more needed. However, I did not remove it. And honestly speaking, this seemed a bit more than just a level 1 issue 😅

@rupali-codes Could you please elaborate the issue? Because I didn't notice any such thing when running on my machine.

@bose-aritra2003 checkout this

@rupali-codes @CBID2 I think this is related to the Operating System and not to the browser because I ran on both Chrome and Safari and did not notice that issue. I am currently on macOS 13.0.1. So could anyone please help me figure it out because I don't have access to any other operating system at this moment?

@rupali-codes @CBID2 I think this is related to the Operating System and not to the browser because I ran on both Chrome and Safari and did not notice that issue. I am currently on macOS 13.0.1. So could anyone please help me figure it out because I don't have access to any other operating system at this moment?

I'm experiencing this in chrome, brave and edge. What is your screen resolution?

@rupali-codes @CBID2 I think this is related to the Operating System and not to the browser because I ran on both Chrome and Safari and did not notice that issue. I am currently on macOS 13.0.1. So could anyone please help me figure it out because I don't have access to any other operating system at this moment?

I'm experiencing this in chrome, brave and edge. What is your screen resolution?

@rupali-codes My screen resolution is 2560 × 1600

@rupali-codes @CBID2 I think this is related to the Operating System and not to the browser because I ran on both Chrome and Safari and did not notice that issue. I am currently on macOS 13.0.1. So could anyone please help me figure it out because I don't have access to any other operating system at this moment?

I'm experiencing this in chrome, brave and edge. What is your screen resolution?

@rupali-codes My screen resolution is 2560 × 1600

Maybe its screen size issue, not the browser ones

Could @CBID2 confirm whether you are facing the same issue ? And @rupali-codes, have you tried opening the web app on other devices and seeing whether the issue persists or not? Because I have absolutely no idea why that scrollbar is appearing in the beginning.

Could @CBID2 confirm whether you are facing the same issue ? And @rupali-codes, have you tried opening the web app on other devices and seeing whether the issue persists or not? Because I have absolutely no idea why that scrollbar is appearing in the beginning.

I'm still seeing it in my phone and tab, though i don't know the exact issue. @ujjawaltyagii & @CBID2 do you guys have any idea?

I don't see it on the mobile. I'll try it on desktop mode later and see the issue happens there @bose-aritra2003

@CBID2 @rupali-codes any update on this PR ?

@CBID2 @rupali-codes any update on this PR ?

Hey sorry @bose-aritra2003. I didn't have a chance to check. Will do tomorrow

@CBID2 let me know

Yep !! I can also see this scrollbar on mobile as well as in brave/chrome/edge whenever we open any category

Is there any fix you could suggest? Because I am unable to see that on my devices. Maybe because of different operating system (Mac and iOS)

Yep !! I can also see this scrollbar on mobile as well as in brave/chrome/edge whenever we open any category

Do you have any suggestions to fix this issue?

@rupali-codes how does it look ? (did some changes)
https://github.com/rupali-codes/LinksHub/assets/115401171/e55e6124-4af7-43af-bd25-61db7dbae0cc

@rupali-codes how does it look ? (did some changes)
fixx.mp4

Looks great 👀

so basically idk if i will explain well or not but i tried and did bunch of things :
modified overflow property, added usestate hook to manage the expanded state, use of isExpanded variable to get this output.
(now i think i should have opened a PR for this :)

@rupali-codes so basically idk if i will explain well or not but i tried and did bunch of things : modified overflow property, added usestate hook to manage the expanded state, use of isExpanded variable to get this output. (now i wish i should have opened a PR for this :)

You have the rights to edit the files in here, or just suggest the changes :)

Hey @bose-aritra2003 could you please update the description and add closes #747 as well

Hey @bose-aritra2003 could you please update the description and add closes #747 as well

@rupali-codes done

OOPs !! I accidently committed the changes instead of suggesting them :) @rupali-codes @bose-aritra2003 do check the deployment and feel free to modify the changes if you want !

OOPs !! I accidently committed the changes instead of suggesting them :) @rupali-codes @bose-aritra2003 do check the deployment and feel free to modify the changes if you want !

@ujjawaltyagii The accordion arrow symbol is reversed for the Frontend tab.

@bose-aritra2003 Ig rest is working fine like that scroll-bar issue which was appearing when we were opening any category so you can commit the rest of the changes !

@bose-aritra2003 are you still working on this?

@bose-aritra2003 are you still working on this?

Yes I am. I was actually very busy for the last few days and therefore couldn't work on it. I am going to fix that by tomorrow if possible.

@bose-aritra2003 are you still working on this?

Yes I am. I was actually very busy for the last few days and therefore couldn't work on it. I am going to fix that by tomorrow if possible.

Umm... can we make this PR  just to resolve the opened frontend tab issue on starting? i guess that would be better, as the issue is being addressed in another PR

@bose-aritra2003 are you still working on this?

Yes I am. I was actually very busy for the last few days and therefore couldn't work on it. I am going to fix that by tomorrow if possible.

Umm... can we make this PR just to resolve the opened frontend tab issue on starting? i guess that would be better, as the issue is being addressed in another PR

@rupali-codes I just now added a commit and found out that it was actually a very simple fix. I think now it is alright. Please review it.


highlight.js style won't change

Thank you for this precious theme, it's great work!
I'm having troubles with highlights.js colors, apparently changing the string on config file has no effect, at least for me. This is what  I tried:
[markup.highlight]
anchorLineNos      = false
codeFences         = true
style              = '1c-light'
tabWidth           = 4

or any other style that are not base16snazzy, they won't work either.
Am I doing something wrong?
Thank you!

Hi @biccio, thanks for the love for this theme!
I’ll look into it when I have some time, which shouldn’t be long!

Hi @biccio, hope you are doing well.
The issue is that the documentation incorrectly describes Highlight.js, whereas Hugo actually uses Chroma as a compile-time syntax highlighter.
To explore all available Chroma themes, you can visit the Chroma Playground.
We appreciate your feedback and will work on rectifying the documentation.
Best regards,
Junyi.


Black screen after login

After login the screen is full black. Does not allow me to do anything. I am using Windows 11, Dell computer.

@JLombar It's fixed now!


Refactor tablet get data size

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Problem Summary(Required) ：

Add singleReplica parameter.
For LocalTablet, get total data size of all replicas if singleReplica is true, else get max replica data size.
For StarOSTablet, singleReplica is not used.

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 8 / 9 (88.89%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/http/rest/ShowMetaInfoAction.java
0
1
00.00%

:large_blue_circle:
com/starrocks/catalog/MaterializedIndex.java
1
1
100.00%

:large_blue_circle:
com/starrocks/catalog/LocalTablet.java
6
6
100.00%

:large_blue_circle:
com/starrocks/common/proc/TabletsProcDir.java
1
1
100.00%


SMTP Client does not handle empty RCPT TO

For whatever reason, one of our SMTP-based clients tried to do RCPT TO:<> and was met with an exception from the following code:
https://github.com/postalhq/postal/blob/2595481b266199d8e29347dea2764f2c10202805/lib/postal/smtp_server/client.rb#L254-L256
The problem is that uname.split will not work as uname isn't defined.
I have tried the following changes to no avail

Stack trace:

I don't know any ruby really so if someone could point me in the right direction, I would appreciate it.

I think you should null check the variable rcpt_to instead of uname.

I think you should null check the variable rcpt_to instead of uname.

Try to put the return keyword before the 550 error strings, maybe without it the code continues executing.

Try to put the return keyword before the 550 error strings, maybe without it the code continues executing.

Same as https://github.com/postalhq/postal/issues/1019

Same as https://github.com/postalhq/postal/issues/1019

Oh yeah, thanks for the link @rbozan. Fortunately, the process should be kept alive by Procodile but its not perfect.
Thanks for the tip @SilverCard, I'll try that later.

closing in favour of #1019


Rucio Rest Client

Description
Initialize the rucio rest client to

handle GET, POST requests to handle JSON and JSON stream content types
handle rucio auth tokens automatically ( make sure requests are authenticated else redirect user to login page)

Motivation
No response
Change
No response
Additional Information

[ ] The Rucio API needs to be changed.

Duplicate of #83


fix: preserve artwork details in the flow

The type of this PR is: Bugfix
This PR resolves SWA-288
Description
This PR fixes the problem that after a user:

fills in artwork details
presses Save & Continue button
navigates back to the Artwork Details step

the draft submission details are lost (because they are cleared from the GlobalStore).
Video
https://user-images.githubusercontent.com/42584148/156792016-7976dfbf-38f7-41af-8ead-af0416b2f79f.mp4
PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Dev changes
Changes applicable to devs only.

This PR contains the following changes:

Dev changes (Changes applicable to devs only.)

  Generated by :no_entry_sign: dangerJS against caa3a029b7a39872acda547e01e843d60f0b6214


Shell navbar menu extension

This modified "shell" component extends menu functionality (primarily adds support for icons in menu items and styling menu items as buttons). This pull request also contains a sample hybrid menu demo file menu_demo.sql.

I have updated this pull request to include all changes made in "Parse JSON menu_item for SQLite and skip blank items", so that this pull request could be merged without conflicts after the other one is accepted. Please take a look at the extended "shell" component and accept the pull request, if you think it is OK, or let me know of any issues.

Thanks  for the PR !
There are multiple things here.
I'm still not convinced by the looks of this

But I clearly see the interest of fixed_top for instance.
Can you open distinct pull requests ? This will make it easier to merge what can be merged now, and to discuss what still needs to be discussed.

To clarify, the three new PRs are just that (parts of the previous bigger PR).

Great, I already merged the sticky top menus. I'm closing this one in favor of the others, then


feat: add diffusers image support

Description
Add diffusers images (API+Job) as the default image for customers
Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

will recommit


Tutorial Page cp-ias-azure-ad-cf.md Issue. PROD

Tutorial issue found: https://github.com/sap-tutorials/Tutorials/blob/master/tutorials/cp-ias-azure-ad-cf/cp-ias-azure-ad-cf.md  - file path is not unique. Your tutorial was not created.
Affected server: PROD

Tutorial was moved to another repository.


HiveMQ replacing VerneMQ

Ready for review :)

Gitguardian will fail, cause i pushed ~10 private keys :D

@JeremyTheocharis Let's not merge this, without Documentation updates

@JeremyTheocharis Also checkout "Setting up the HiveMQ PKI" on notion

Added to Changelog (0.9.10)


Error on HTML5

Works fine on default doctype but if i set it to HTML5 it fails with this message:
"delimiter ">" invalid: only name, "#IMPLIED" and parameter separators are allowed" Line no: 1
My first line is just this:

Same problem... any suggession?

Same problem... any suggession?

use https://github.com/jzaefferer/grunt-html instead


Crash when breaking stairs/slabs with Immersive Engineering steel block

The title kinda explains it, I'm getting this error that causes my game to crash when i break a stair or slab with an IE steel block
https://pastebin.com/Z4ih1mYe
Edit: i've just noticed that it doesn't happen everytime, but quite often

This is the same problem as #39. You are using an old version (0.3.6). Try using the newest version (0.4.0) or ask the developer of the modpack to update to the newest version.
Regards, Manu


ERROR  [SyntaxError: Unexpected EOF]

So I figured out this lib few days ago and I'm already falling in love with it.❤ But I recently ran into a problem and In order to contribute a bit with the communit I just want to share this little problem and the solution I got.
The problem:
The erro is: SyntaxError: Unexpected EOF I got this by just adding // @solid at the begining of the file. This error occurs once I save the file and doesnt let me run the app at all at any point.
After sometime removing some of the code, I figured out that you can't have a break line like this, This was an easy fix but I wasnt expecting that would break in solid cause it works fine without it. Is there any chance we get an update for this in future?
I would love to make a PR with the fix for this If I did know how ;p

I'm glad you're liking it so far!
Looks like Solid itself doesn't support this JSX syntax.
However, it's worth noting that in react, that label would have the string "...\n          ...", which I doubt is what you want?
I would recommend using something like
        <Image
          accessibilityLabel="...\
..."

which will work correctly in Solid, although react will treat it as "...\\\n...".
In general, React treats strings in JSX somewhat like HTML, while Solid treats them like usual JS strings. Personally, I think the latter is much easier to work with, as it means that – in solid – foo="bar" is identical to foo={"bar"} – but this is not the case in React.

Tl;dr: Solid treats strings in JSX identically to JS strings, and so this errors because it isn't a valid string in JS. This isn't a bug, just a difference in the treatment of JSX.

That will works accessibilityLabel="...\ thanks for clarify me this ;)


EMFILE: too many open files

Describe the bug
When i trying to use the API of workflow in 3000 times, it show me this error
Screenshots
{
"statusCode": 500,
"success": false,
"message": "EMFILE: too many open files, open 'C:\Users\gaoby\AppData\Roaming\npm\node_modules\flowise\node_modules\flowise-ui\build\index.html'",
"stack": {}
}

Setup

Installation npx flowise start
Flowise Version : 1.8.4
OS: Win11

Additional context
Add any other context about the problem here.

Not sure how to fix this, but can you add throttling or some delays between API requests?


updated arq (5.1.8)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Merged as 93a00e53ee3d51ad4307479390bb6b3564bf0f28.


Root $id not overrided by S.extend

Unfortunately S.extend doesn't work as expected. I have been too optimistic.
The problem is here: https://github.com/fastify/fluent-schema/blob/master/src/utils.js#L140-L150
Basically, fluent-schema adds attributes to the last prop declared. However with S.extend(base).id('extend') the id will be added to the last prop from the base rather than the root document.
I have the feeling we need to change the syntax to:
S.object()
  .id('extend')
  .prop('bar').extend(S.object()id('base').prop('foo'))

I need to dig into more
For now, this PR contains only the tests to expose the issue

Could you use symbols to ignore prop that has been imported/extented in the main S.object?

Not sure if I get what you mean.
Are you referring to S.extend(Base).id('extended') case?
the issue is in how we add an attribute.
const setAttribute = ({ schema, ...options }, attribute) => {
  const [key, value] = attribute
  const currentProp = last(schema.properties)
  if (currentProp) {
    const { name, ...props } = currentProp
    return options.factory({ schema, ...options }).prop(name, {
      [key]: value,
      ...props,
    })
  }
  return options.factory({ schema: { ...schema, [key]: value }, ...options })

currentProp is the last prop added so the id will be added to the last prop added in the base not at the root level as the syntax let you imagine.
In order to fix that I had to change the order:
const base = S.object().id('base')
S.object().id('extended').extend(base)

With this approach extend can merge the extended and base schemas in the right order
 const extended = merge(state, schema)

notice: this is breaking change. The previous API is broken and I can't figure out a way to support the original approach S.extend(S.object().id('base').prop('foo')).id('extended').prop('bar')


[Docs] Update Documentation on creating Windows clusters in Rancher

The Rancher documentation on how to provision a Windows cluster is out of date. The page lists the steps required to provision an rke1 windows cluster, however windows support on RKE1 is EOL and should no longer be used. We need to update these docs to outline the steps needed to provision an rke2 windows cluster.
As a part of this ticket we should also look over the versions listed as supported for both Linux and Windows, as well as the recommended system requirements for Windows nodes.

Superseded by https://github.com/rancher/rancher-docs/issues/1260


fix(forest-client)!: rename property "clientAcronym" to "acronym"

Description
Rename the property ForestClientDto.clientAcronym to acronym, in accordance to the Forest Client API.
This is a breaking change and will affect the results from the endpoints under the ForestClient tag.
Fixes FSADT2-629
Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit and manual tests

Checklist

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

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

@craigyu, this changes the result of an endpoint you might be working with at the moment.


[Feature] Install as package

Added -p and -P options during install to install rez as a package under the given install directory (typically a packages)

:robot: See our Experimenting with actions - PR 579 GitHub actions workflow for some experimental CI and tests! :robot:

For now, this PR will only focus on install.py to perform a production friendly install just requiring python. The rez package will be setup up with the variants:

platform-system platform name (e.g. linux), and
python-MAJOR.MINOR for the Python version used to run python install.py

So far, it is not intended to replace rez bind rez, but maybe at some point (see below).
It does install the rez package in a similar structure and performs package commands to setup the following:

Add {root}/bin/rez into PATH
Copy {root}/lib/python*//rez* into {root}/python (for clean Python imports of rez* modules)
Add {root}/python into PYTHONPATH

e.g. for commit d987f7d

python install.py --help
usage: Rez installer [-h] [-v] [-s] [-p | -P PACKAGE] [DIR]

Install rez in a production ready, standalone Python virtual environment.

positional arguments:
  DIR                   Destination directory. If '{version}' is present, it
                        will be expanded to the rez version. Default: /opt/rez

optional arguments:
  -h, --help            show this help message and exit
  -v, --verbose         Increase verbosity.
  -s, --keep-symlinks   Don't run realpath on the passed DIR to resolve
                        symlinks; ie, the baked script locations may still
                        contain symlinks
  -p, --as-rez-package  Install using rez package structure as 'rez'. (DIR
                        should be a rez packages directory)
  -P PACKAGE, --as-package PACKAGE
                        Given a package name, install using rez package
                        structure. (DIR should be a rez packages directory)

python install.py -p ~/packages will install as:
~/packages
~/packages/rez
~/packages/rez/2.47.2
~/packages/rez/2.47.2/package.py
~/packages/rez/2.47.2/platform-linux
~/packages/rez/2.47.2/platform-linux/python-2.7
~/packages/rez/2.47.2/platform-linux/python-2.7/python
~/packages/rez/2.47.2/platform-linux/python-2.7/bin
~/packages/rez/2.47.2/platform-linux/python-2.7/lib
~/packages/rez/2.47.2/platform-linux/python-2.7/include
~/packages/rez/2.47.2/platform-linux/python-2.7/completion

rez view rez
URI:
/home/runner/packages/rez/2.47.2/package.py

CONTENTS:
name: rez

version: 2.47.2

description: Standalone, production-ready Rez installation

variants:
- - platform-linux
  - python-2.7

commands: "\"\"\"Setup PYTHONPATH (inspired by src/rez/bind/rez.py).\"\"\"\nimport\
  \ os\nenv.PATH.append(os.path.join('{root}', 'bin', 'rez'))\nenv.PYTHONPATH.append(os.path.join('{root}',\
  \ 'python'))\n\nif defined('SHELL'):\n    is_csh = \"csh\" in str(env.SHELL)\n \
  \   ext = \"csh\" if is_csh else \"sh\"  # Basic selection logic\n    source(os.path.join('{root}',\
  \ 'completion', 'complete.' + ext))"

base: /home/runner/packages/rez/2.47.2

This feature was originally suggest for v2.27 but has been rebase'd and adapted to the latest rez versions since. Needless to say, the various evolution and improvements to rez has put this feature in an interesting spot.
Highlights from discussions below
pip install compatible
rez now uses pip install internally in install.py! Therefore after downloading/git clone this repository, one can install rez via several methods (assuming you're running from same folder as rez's install.py/setup.py):
# 1. The OG method into a Python venv (production safe), then install rez using venv's pip install
python install.py DEST_DIR

# 2. pip install using current folder as pip package
pip install --target DEST_DIR .

# 3. if you have rez already installed, install rez as pip Python package into local package path
# See https://github.com/nerdvegas/rez/wiki/Configuring-Rez#local_packages_path
rez-pip --install .

In the current state of this PR/feature, it more closely follows 1. It's able to install rez even if rez is not currently installed.
Since pip based 2 and 3 installs do not install rez into a venv, more work will need to be done to this PR to get it to be pip friendly. See https://github.com/nerdvegas/rez/pull/579#issuecomment-504947600, https://github.com/nerdvegas/rez/pull/579#issuecomment-526801383, https://github.com/nerdvegas/rez/pull/579#issuecomment-528693763
Deprecate rez bind rez
Since this PR installs into a similar structure/package declaration as the rez package produced by rez bind rez, given some extra work, maybe even this PR can deprecate the rez rez bind.
rez bind rez currently sets up only the rez Python modules into a rez package. This is similar to the pip style installs (2 and 3), but just without the bin folder/tools.
See https://github.com/nerdvegas/rez/pull/579#issuecomment-526801383, https://github.com/nerdvegas/rez/pull/579#issuecomment-526872658

Hi @j0yu , this is pretty useful, we made rez as a package 4 years ago, but I think it was more complicated, maybe because our enrvironment with CentOS-6. I sort of remmeber that one of the problem is the python version that is shipped with rez.  I'll dig in the history, but from memory and at first glace seems quite different to this.
But I guess if  this is working fine for you, then it is fine. I can also give it a try at this branch

Solved once wheel and pypi support get merged.
$ rez wheel --install rez==2.30.0

Hi @j0yu, just letting you know I'm aware of this PR and I agree with the functionality. I'm just waiting til after there's some work on updating the installer, which will be happening within a few weeks. I'll either merge or cherrypick from this PR as part of that effort.
Thx
A

Solved once wheel and pypi support get merged.
$ rez wheel --install rez==2.30.0

@mottosso Interesting! I'll give it a test and maybe even port this functionality over so you can directly during install using pip install --install-option="--as-package=rez"
Great stuff on #614 and #625, so right now I'm looking to run something like these?
$ pip install --user bleeding-rez  # I'll see if I can add --install-option here to do "rez wheel" after install
$ rez wheel --install rez==2.31.4

Hi @j0yu, just letting you know I'm aware of this PR and I agree with the functionality. I'm just waiting til after there's some work on updating the installer, which will be happening within a few weeks. I'll either merge or cherrypick from this PR as part of that effort.

Thanks @nerdvegas, I'm happy to rebase this branch over whenever the installer is updated. Just drop a message on here and I'll update this PR to the latest master branch.
I saw there's a lot of discussion about install.py in other PRs and I wouldn't mind porting this feature to whichever/all install methods. I'm just lazy and want to install rez as a package right-off-the-bat in a one-liner

so right now I'm looking to run something like these?

Yes, that's exactly right! Except at the moment rez itself isn't on PyPI, so for a working version today till then from a fresh system, it would be:
$ pip install --user bleeding-rez
$ rez pip --install bleeding-rez  # wheel got renamed back to `pip` in the bleeding-rez version

And you'd have Rez both on your system and as a package.

I'll see if I can add --install-option here to do "rez wheel" after install

Double inception! Haven't thought of that, let me know how that goes.

I just tested this, but it creates a very strange rez package:

The package payload actually contains a virtualenv-based production install of rez
The package actually then uses the rez installation if you request it.

See in its commands:
def commands():
    """Setup PYTHONPATH (inspired by src/rez/bind/rez.py)."""
    import os
    import rez  # <- this picks up installed rez!
    env.PATH.append(os.path.join('{this.root}', 'bin', 'rez'))
    source(os.path.join('{this.root}', 'completion', 'complete.sh'))

    rez_path = os.path.dirname(rez.__path__[0])

A rez package of rez should just be the rez API, independent of whatever the current installation is. It's entirely feasible to have (for eg) installed rez-2.40.0, but rez package ~/packages/rez/2.39.0, and so on. This is actually pretty normal at Method for eg - our installation is updated first, and the rez rez package is deployed later, once the installation has been tested for a while.
As it happens, I've just done some testing with the recent rez-pip improvements, and this actually works very well:
]$ cd <rez source clone>
]$ rez-pip --install .

I think this approach should be fine, as rez-pip is installing directly from source here, and doesn't need to download anything. There's a little massaging to do though - namely, the bin tools should be removed (because they are only guaranteed to function correctly in a production install); as well as a couple more subtleties that I won't delve into here.
So my thoughts at the moment are that we should:

provide python install.py -p option, much like here
not give the option to change the rez package name
if rez-pip is available, use it to do a rez-pip --install .
add some hardcoded stuff in pip.py to detect if rez itself is getting installed, and do some massaging as mentioned above.
If rez-pip is not available, then do a temp rez install, and use the rez-pip from there, to then do steps 3,4,5.

I'm inline with what @nerdvegas said. Though, I think differently of adding a -p argument to the install.py script. I would just document how someone can create a rez rez package by using rez-pip --install . from the source, or by doing rez-pip --install rez (so downloading from PyPI).
I would also add that we could make the package variant'ded (on python) so that it is only usable when using a compatible python version. That is it cannot be used with python 3 for example. Or the day we fully support python 3, then only specify the python versions with which it is compatible with (wild guess will be 2.7+|>=3.4|<=3.7).

If rez-pip is not available, then do a temp rez install, and use the rez-pip from there, to then do steps 3,4,5.

In which case can this happen?
Also, should we deprecate the rez bind officially (I mean the rez-bind -i rez)?

Thanks for the feedback, I should have mentioned that I just did a basic rebase I haven't fully tested it with the new rez versions yet but it seems you guys have beat me to testing it out.
I agree with the comments, so I'll crack on and see how much of these I can get done:

[ ] Fix/remove import rez
[ ] Make sure (Docker) tests work again... CI?
[ ] Implement and test cd <rez source clone> && rez-pip --install .
[ ] Figure out compatibility from setup.py + run time OS/platform to build variants based off it
[ ] Switch to rez-pip based install

Also, should we deprecate the rez bind officially (I mean the rez-bind -i rez)?

Not sure how/if I should do something in this PR for that @nerdvegas? Something like:

Deprecation warning when run
"Alias" it to run the rez-pip install ... command

On another note, @nerdvegas is pip install rez suppose to pull down the latest 2.42.2 version? I'm only getting/seeing 2.0.ALPHA.52 on pypi.org

You have to build the wheel locally as builds are not yet published to pypi

The pip installation should occur from the local source. Any option to install rez as a rez package, from install.py, I would not expect to fetch externally.
I mentioned a few caveats about installing rez via rez-pip; they're worth going over here.
The first is cli tools. The rez rez package doesn't have any, yet rez-pip will create them. So I am actually thinking... since pip-installed rez cli tools aren't safe anyway, maybe we should remove them altogether? We could do this simply by providing an empty entry point list in setup.py, unless some env-var is set (which only install.py would set). This seems clean to me - it removes potentially unsafe cli tools, and it means one less caveat for rez-pip-installing rez itself. It also means we don't need any warnings in the docs/tools about those tools potentially misbehaving.
The second is varianting. The rez-pip tool variants on python-MAJOR.MINOR, even if it could theoretically variant on a looser python version range. The reasons for this have been gone over elsewhere, but the short of it is, due to python "environment markers", it's possible to end up with odd/overlapping python version ranges. However, we know that rez doesn't need to be varianted on MAJOR.MINOR - in fact, pretty soon (when py3 port is finished) it won't need to be varianted at all, and instead could just require python-2.7+. I think we need to address this, otherwise newer rez installs will install to narrower python version variants than previously, and that could break existing studios' processes.
To address the varianting issue, I wonder if we could do it in a general way. Is it possible to author metadata in a python package, that could communicate this (and potentially other) info to rez? Ie, can we embed into into a native python package, about how it should be varianted in rez? I think this would be the best approach, as it would solve an issue specific to this PR, as well as being a generally useful new feature.

So I started to get back onto this again but I've decided to go step by step and return the scope of this PR to the original, simpler quest of:
Can I run python install.py -p ~/packages to install rez as a production, venv based rez package?
I feel there's more opportunities to get rez-pip to work too but I feel like I need re-think about this PR since rez has evolved a lot since 2.27.0.
I've also update the PR description too with some bits I picked out from the discussions

See https://github.com/nerdvegas/rez/pull/845


link the pricing page

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #4449
Description
This PR is about fixed the error showing page is not found in the navbar dropmenu pricing page.

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before:

After:
https://github.com/user-attachments/assets/4aeab3ab-75cc-4e49-973d-a27527e4e4a8
Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

https://github.com/user-attachments/assets/d240650c-8ad4-4bb1-a49b-193075437567
in the more dropdown , there are links to pages that are imptt but are kind of ignored .
u can add these links to the Quick Links section ( in another row) of the home page .
eg : community chat , read later , reader connection etc...
and delete the books prefer page .

u may work on the issue and raise pr .

ok @abhi03ruchi
I have to add important links in the navbar quick section and delete the book quiz in all pages of your website???

footer quick links . someone else is working on navbar .

Like these???

footer quick links . someone else is working on navbar .

add these only  community chat , read later , reader connection .
community spotlight is in navbar so dont add .
ensure proper spacing .

Ok


docker-compose up

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

(HTTP code 404) no such image - no such image: docker/compose:latest: No such image: docker/compose:latest how to solve this problem.


Convert LessThanInstruction classes closer to .NET Core implementation

Do they have additional tests for these things as well?

I found this: https://github.com/dotnet/corefx/blob/master/src/System.Linq.Expressions/tests/InterpreterTests.cs

Looking through .NET Core repository, I don't see dedicated tests to Instruction classes, such as the one in this PR.
Should we add the Interpreter test in a separate PR?

I don't think we can use the InterpreterTests from .NET Core as is. Better to leave it for another PR. We should look into creating some basic tests for the instructions though.

@gpetrou Thanks for the PR, sorry it took so long to get merged in.


Submit

I've just done another round of edits and I think we are ready to submit this.
@Smit-create , if you agree, could you please take care of it?

@oyamad absolutely!  Please go ahead.

Sure, thanks @oyamad and @jstac. Let's plan to submit it on Friday?

@jstac Can you please have a final look to have a green signal?


[Request for external] page 408 "G/L Balance by Dimension" - CopyDimValueToBuf

Can you change procedure CopyDimValueToBuf to global?

It doesn't make much sense as a global procedure on a page, will leave it as local, you can copy the code if you need it elsewhere.


Remove observer AFHTTPRequestSerializer for "allowsCellularAccess" crash

After updating from 2.3.1 to 2.4.1, my app crashes immediately on launch. I've put breakpoints everywhere but can't seem to find the line that does it. However, the crash message is:
*** Terminating app due to uncaught exception 'NSRangeException', reason: 'Cannot remove an observer <AFHTTPRequestSerializer 0xdbac8f0> for the key path "allowsCellularAccess" from <AFHTTPRequestSerializer 0xdbac8f0> because it is not registered as an observer.'
Rolling back to 2.3.1 for now...

I'm encountering the same problem and have created a project with minimal code to reproduce the problem. You can find it at https://github.com/r3b3l/AFNetworkingXCTestFail
Happens under AFNetworking 2.4.0 and all above.

2.5.2 problem is urgent


set as a TermElab

E.g. in this slightly silly example, rather than writing
def a (t : Nat) (h : t < 7) : Nat :=
  if t = 0 then 0 else
  let b : Nat := t - 1
  (a b (by rw [(show b = t - 1 by rfl)]; sorry)) + 1

I'd like to be able to write
def a (t : Nat) (h : t < 7) : Nat :=
  if t = 0 then 0 else
  set b : Nat := t - 1 with h
  (a b (by rw [h]; sorry)) + 1

This will make set a keyword, which will prevent its use as an identifier or function name, which seems undesirable. Also the with h is quite unusual for term-mode syntax; we should try to find a way to use something similar to the analogous match syntax x@h:pat for this.
Also, there are enough parts of term mode available in tactic mode that you can kind of just add by at the start and nothing has to change except exact before terms:
def a (t : Nat) (h : t < 7) : Nat := by
  if t = 0 then exact 0 else
  set b : Nat := t - 1 with h
  exact (a b (by rw [h]; sorry)) + 1

Ok, well I really don't mind what it is called (let would also be fine! let/set distinction is perhaps a lean 3 relic anyway), and the precise syntax doesn't matter either, that match style would be good. But I would like to avoid entering tactic mode in my use case if possible, maybe the term generated will be the same but I have a very very long def so it feels more in control to remain in term mode.

What you can do these days is use simp to unfold a let binding like so:
def a (t : Nat) (h : t < 7) : Nat :=
  if t = 0 then 0 else
  let b : Nat := t - 1
  (a b (by simp (config := {zeta := false}) only [b]; sorry)) + 1

(The zeta config is to keep it from unfolding b without mentioning it. by simp only; sorry also unfolds b.)
There's also by unfold_let b; sorry using mathlib.


proxy不起作用

Describe the problem
[init] ERROR: failed to obtain version manifest from https://piston-meta.mojang.com/v1/packages/505270a5ebc9b400370bdcbb1769a860d1a45562/1.20.4.json (0)
应该是proxy不起作用，我填写的是http://<IP_ADDRESS>:20172，在jellyfin上能够生效，所以应该不是代理的问题。
Translation by chatgpt: "It seems that the proxy is not working. I have entered http://<IP_ADDRESS>:20172/, which works on Jellyfin, so it shouldn't be a proxy issue."
Container definition

Container logs

Can you set the environment variable DEBUG to "true" and provide those logs?

DEBUG

Can you set the environment variable DEBUG to "true" and provide those logs?

我之前的那个删了，这次简单配置了一下，打开了debug，请看看，谢谢
Translation by chatgpt:   ''I deleted the previous one. This time I made a simple configuration and turned on debug. Please take a look. Thank you.''

The proxy does not seem to be fully functional. It seems to have correctly handled https://launchermeta.mojang.com/mc/game/version_manifest.json but then is not handling the URL reported in the logs you posted.
Please post the logs as text next time since it is difficult to work with screenshot images.

代理似乎没有完全发挥作用。它似乎正确处理了 https://launchermeta.mojang.com/mc/game/version_manifest.json 但随后没有处理您发布的日志中报告的 URL。
下次请将日志作为文本发布，因为很难处理屏幕截图图像。

依旧不行  Still no


I can't access to the data from a "Flexible Content" ACF json object.

Hi,
I'm trying your plugin but I can't access to the data from a "Flexible Content" ACF json object. I can console.log the filelds but can't show totally them in the view.
{{ product.meta }} or {{ product.meta }} returns the array I need, but I can't deep more. Once there, how can I access to the keys/values from that array?
thanks for this great plugin!,
s.

It's hard to tell exactly @t0t, can you share some more of the code for productos.html?
It looks like the data is all there (via this plugin), but the way you're accessing it in AngularJS needs some tweaking.

Hey thanks for reply!
Yes, the data is all there, I'm so close to do amazing things... but as web designer I'm a beginner with Angular and MVC's. I'm learning as fast as I can.
Wp-api has changed the paradigma of traditional WP themes and your plugin is the bridge between WP-API+ACF.
I would really appreciate your help on this if you can take a look.
I've pushed this theme here:
https://github.com/t0t/maderlim/tree/3
Do you know any wp-theme using wp-api/angular? I like this: https://github.com/1fixdotio/angularjs-demo-theme
;)
s.

It looks like acf.product is an array, so when you're accessing product.vistas you actually need to access acf.product[0].vistas, or, more likely, as there may be multiple objects in that array, you should iterate over acf.product.
Let me know if you've been able to sort it. I'll close this issue though as it's not directly a problem with the plugin itself.


AWS goobi: mixed content warning

The Goobi Dashboard on AWS shows a mixed content warning, appears to be the RSS feed

switch RSS feed to https and the warning is gone


Transfer ownership to webvrrocks GitHub org

If you could, when you get a chance can you transfer this repo to the webvrrocks org? That way, I can more easily manage the Heroku deploys and manage the settings. Thanks!

done!


Add plate source

This is basically covered in https://github.com/atulloh/oddball/pull/4
The goal was to take out all the hacky tweaks that were happening with the initial OpenSCAD code, and pull out all parameters into a single file.
I've added the scad files and also the output STL and DXF files for the plates and bearing mount.


Added sippreg_unregister API function

Don't know why retest failed.

You branch is behind main. Rebase or Merge should help.

Thanks, now done and OK.

How did you merge? Looks like the last main commits are now part of this PR. I see no merge conflicts but wonder if this merge nicely. Maybe a new branch/PR would be safer.

Will try again.


[Bug]:  Error executing model: Error computing NN outputs.

What happened?
While trying to run a basic script mentioned below I'm seeing an issue.
import chromadb
chroma_client = chromadb.Client()
switch create_collection to get_or_create_collection to avoid creating a new collection every time
collection = chroma_client.get_or_create_collection(name="my_collection")
switch add to upsert to avoid adding the same documents every time
collection.upsert(
documents=[
"This is a document about pineapple",
"This is a document about oranges"
],
ids=["id1", "id2"]
)
results = collection.query(
query_texts=["This is a query document about florida"], # Chroma will embed this for you
n_results=2 # how many results to return
)
print(results)
Issue:
2024-07-22 21:04:26.098904 [E:onnxruntime:, sequential_executor.cc:516 ExecuteKernel] Non-zero status code returned while running CoreML_2809954737722992935_1 node. Name:'CoreMLExecutionProvider_CoreML_2809954737722992935_1_1' Status Message: Error executing model: Error computing NN outputs.
Versions
chroma-hnswlib  0.7.5, chromadb 0.5.4, MAC OS MOnterey (12.7.5), Python: 3.12.4
Relevant log output
$ python chroma_db_basics.py

2024-07-22 21:04:26.098904 [E:onnxruntime:, sequential_executor.cc:516 ExecuteKernel] Non-zero status code returned while running CoreML_2809954737722992935_1 node. Name:'CoreMLExecutionProvider_CoreML_2809954737722992935_1_1' Status Message: Error executing model: Error computing NN outputs.
Traceback (most recent call last):
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/chroma_db_basics.py", line 5, in <module>
    collection.add(
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/api/models/Collection.py", line 80, in add
    ) = self._validate_and_prepare_embedding_set(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/api/models/CollectionCommon.py", line 279, in _validate_and_prepare_embedding_set
    embeddings = self._embed(input=documents)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/api/models/CollectionCommon.py", line 568, in _embed
    return self._embedding_function(input=input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/api/types.py", line 211, in __call__
    result = call(self, input)
             ^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/utils/embedding_functions/onnx_mini_lm_l6_v2.py", line 200, in __call__
    return cast(Embeddings, self._forward(input).tolist())
                            ^^^^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/chromadb/utils/embedding_functions/onnx_mini_lm_l6_v2.py", line 143, in _forward
    model_output = self.model.run(None, onnx_input)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/varkeyvincent/Desktop/LLM_learning_journey/LLM_Journey/my_venv/lib/python3.12/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 220, in run
    return self._sess.run(output_names, input_feed, run_options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : Non-zero status code returned while running CoreML_2809954737722992935_1 node. Name:'CoreMLExecutionProvider_CoreML_2809954737722992935_1_1' Status Message: Error executing model: Error computing NN outputs.

@varkeyvincentindia, thanks for reporting this. This would appear to be onnxruntime issue. Can you tell us what version do you have:
pip show onnxruntime

The last time we saw similar issues was when Onnx bumped a minor version at around 1.17.
Another issue might be CoreML.
How did you come by this error? Did you upgrade to a new configuration, or is this a green field project?

onnxruntime v1.18.1., coremltools v7.2. Yes, this is a green field project.

@tazarov Any update on the fix ?

same issue. macos with intel chip

same, macos, Intel, from under conda (microconda)

same issue. macos with intel chip

@varkeyvincentindia, @oharlem, @nhanngh I did some further digging and it seems that there are cases where CoreML provider for the Onnx Runtime might not be properly supported. To resolve this you can use CPU provider as follows:
from chromadb.utils.embedding_functions.onnx_mini_lm_l6_v2 import ONNXMiniLM_L6_V2 # this is how you import in Chroma 0.5.0+
# from chromadb.utils.embedding_functions import ONNXMiniLM_L6_V2 # legacy import for Chroma <=0.4.24

ef = ONNXMiniLM_L6_V2(preferred_providers=["CPUExecutionProvider"])
import chromadb
client = chromadb.Client()
collection = client.get_or_create_collection("<collection_name>", embedding_function=ef)
collection.upsert(
documents=[
"This is a document about pineapple",
"This is a document about oranges"
],
ids=["id1", "id2"]
)

The above code will create a collection with the default embedding function with the CPU provider.

closing as this is a valid fix. @tazarov do you think this is worth adding to https://docs.trychroma.com/troubleshooting?

@jeffchuber, I think there are two steps we can take:

Document it in troubleshooting (I'll raise a PR for that)
Change the defaults for Mac as this seems to be a frequently encountered issue for Mac users with onnx. Maybe I'll benchmark this to ensure the performance hit between CoreML and CPU providers is insignificant.

@tazarov can we introspect the architecture from python/js and set accordingly?


Numeric literals - should Limit is 100 work?

I just got an issue on rockstar-py regarding this:
Limit is 100 was being transpiled to Limit = 0 (it was treated as a poetic number literal and, since there was no alphabetical character, it resulted to 0), instead of Limit = 100.
The FizzBuzz minimalist example in the docs uses this syntax, but this is not described anywhere else in the specs. As of right now, I don't think it should work. What do you guys think?

Very interesting. I think this is very tightly related to the ongoing discussion in #129. If we figure out an alternate syntax for is expressions with math, this is proper behavior, however, if we settle on having math expressions within is expressions, this should set limit equal to 100.


(Modrinth Only) but the mod logo on a black png

Is your feature request related to a problem? Please describe.
it looks bad on a gray background
Describe the solution you'd like
put the logo on a black background
Additional context

Looks like modrinth sets the background based on light/dark mode, on light mode it looks ok.
I set a background manually


Crash in AccessibilityAnnouncer class on release

Hi, after creating release version (distributed via fabric) I get crash on iPhone (tested on iOS: 11.1.2 and 10.3.3)
AccessibilityAnnouncer.swift line 80
specialized AccessibilityAnnouncer.createProducerForNotifier(String) -> SignalProducer<(), AccessibilityAnnouncer.NotificationError>

When running debug mode on cable everything is ok and the crash does not happen. What's the solution?

Please provide a full backtrace, as I am not seeing this issue myself.

I have a suspicion this is related to ReactiveSwfit + optimizations. Please try the v1.0.0, which has an updated version of Reactive Swift.


pretrained weights

Hello, your paper is enlightening to me very well. Have you ever considered releasing the pretrained weights ?

I am also interested in pretrained weights.
Seeing that the above post is two years old I assume its not possible. But could you possibly do it for ChangeStar2?

Thank you for your feedback and good to know you guys need pre-trained weights. I will release some useful pre-trained weights in https://github.com/Z-Zheng/pytorch-change-models later.
By the way, just curious about how you want to use pre-trained weights. It would be helpful for me to design more useful APIs for you guys. Thanks.

I want to use pre-trained weights for change star since its hard to find change detection models with the weights included, especially for models trained on xView2.  Also I was running into a lot of issues running the code for training. I was able to use the OpenCD version of Changestar, but the ability to train on xview2 was not implemented for that repo (whereas you have done so).


fix for re global flags expression

Hello,
When trying to provision a new Oracle setup, the following error is raised:
TASK [opitzconsulting.ansible_oracle.orahost_meta : Extract SGA parameters, choose sga_max_size over sga_target if both are definied] ***
task path: /Users/talek/.ansible/collections/ansible_collections/opitzconsulting/ansible_oracle/roles/orahost_meta/tasks/main.yml:41
Thursday 07 November 2024  18:43:16 +0200 (0:00:00.029)       0:00:12.053 *****
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: re.error: global flags not at the start of the expression at position 1
fatal: [mol-main-abc]: FAILED! => {"msg": "Unexpected failure during module execution: global flags not at the start of the expression at position 1", "stdout": ""}

It seems that Ansible/Python is picky and expects that the global (?i) option to be specified at the very beginning of the regex:
talek@MacBookPro ~ % ansible -m debug localhost -a "msg='{{ 'SGA_target' | regex_search('^(?i)sga_target$') }}'"
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: re.error: global flags not at the start of the expression at position 1
localhost | FAILED! => {
    "changed": false
}
talek@MacBookPro ~ % ansible -m debug localhost -a "msg='{{ 'SGA_target' | regex_search('(?i)^sga_target$') }}'"
localhost | SUCCESS => {
    "msg": "SGA_target"
}

Some additional details. It depends apparently on the python version. For example, no problem with Python 3.9.18:
$ python3 -V
Python 3.9.18
$ ansible -m debug localhost -a "msg='{{ 'SGA_target' | regex_search('^(?i)sga_target$') }}'"
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
    "msg": "SGA_target"
}

But it failse with Python 3.12.7:
talek@mac ~ % python3 -V
Python 3.12.7
talek@mac ~ % ansible -m debug localhost -a "msg='{{ 'SGA_target' | regex_search('^(?i)sga_target$') }}'"
[WARNING]: No inventory was parsed, only implicit localhost is available
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: re.error: global flags not at the start of the expression at position 1
localhost | FAILED! => {
    "changed": false
}


inconsistent props (server/client)

related? #163
Inconsistencies cause issues when trying to use certain features (e.g. sidebar-toggle)

vendors.js:24365 Warning: Prop `href` did not match.

Virtual folders compute stable names for usage in as [name]-enabled query parameter now, so this specific issue should be fixed/mitigated.


Is the null check normal?

First of all, I'm not good at English, so please forgive me.
When checking for title and description null, is there any reason to use openGraphResult!!.title.equals("null") ? It's actually null, but it's not a string, so it's not a normal null check.
library : openGraphResult!!.title?.isEmpty() == true || openGraphResult!!.title.equals("null")
I think this is it
openGraphResult!!.title?.isNullOrEmpty() == true || openGraphResult!!.title.equals("null")
It's always in good use. please check.
Thank you 😀

@sta-con can you link this issue to the PR you created?

Sorry. I'm not sure what you mean
I'm not very good at using Git 🙏