fix: Button and text alignment on ratings page

Pull Request Details
Description
Fixed alignment of buttons and text on ratings page.
Fixes
This PR fixes #909
Type of PR

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

Screenshots

Checklist

[x] I have read and followed the Pull Requests and Issues guidelines.
[x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
[x] I have not borrowed code without disclosing it, if applicable.
[x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
[x] I have tested these changes locally.
[x] My code follows the project's style guidelines.
[ ] I have updated the documentation accordingly.
[x] This PR has a corresponding issue in the issue tracker.

Summary by CodeRabbit

Style

Improved the layout and responsiveness of the platform box component on the user dashboard by adjusting CSS classes for better positioning and margins.

@holopin-bot @vinayak-vohra c-st


Build Broken When Using ASAN

System: Arch Linux
Rust: rustc 1.52.0-nightly (0fc6756b4 2021-02-08)
Linker: LLD 11.0.1 (compatible with GNU linkers)
Affected Hyper Version: > 0.14.2
Reproduction
Build hyper using RUSTFLAGS="-Zsanitizer=address -Clink-arg=-fuse-ld=lld" cargo +nightly build --target=x86_64-unknown-linux-gnu
Output:
  = note: ld.lld: error: undefined hidden symbol: __start_asan_globals
          >>> referenced by 108v8orxopd2lq03
          >>>               /home/xxx/target/x86_64-unknown-linux-gnu/debug/deps/hyper.108v8orxopd2lq03.rcgu.o:(asan.module_ctor)
          >>> referenced by 108v8orxopd2lq03
          >>>               /home/xxx/target/x86_64-unknown-linux-gnu/debug/deps/hyper.108v8orxopd2lq03.rcgu.o:(asan.module_dtor)

          ld.lld: error: undefined hidden symbol: __stop_asan_globals
          >>> referenced by 108v8orxopd2lq03
          >>>               /home/xxx/target/x86_64-unknown-linux-gnu/debug/deps/hyper.108v8orxopd2lq03.rcgu.o:(asan.module_ctor)
          >>> referenced by 108v8orxopd2lq03
          >>>               /home/xxx/target/x86_64-unknown-linux-gnu/debug/deps/hyper.108v8orxopd2lq03.rcgu.o:(asan.module_dtor)
          collect2: error: ld returned 1 exit status

Git Bisect
3ae1581a539b67363bd87d9d8fc8635a204eec5d is the first bad commit
commit 3ae1581a539b67363bd87d9d8fc8635a204eec5d
Author: Sean McArthur<EMAIL_ADDRESS>Date:   Thu Jan 7 17:22:12 2021 -0800

    feat(ffi): Initial C API for hyper

This seems to break it:

checkout v0.14.2
add the following to Cargo.toml

[lib]
crate-type = ["lib", "cdylib"]

Hum, so if a library produces a cdylib, it cannot be used with ASAN? If there's nothing else that hyper did specially, I'd probably consider that a bug in cargo or rustc.
(I do wish there was more control over being able to enable the crate-type through a CLI argument, but slightly off-topic...)

ok fair enough. I did some more minimization and opened rust-lang/cargo#9159 . No idea if it is cargo or rustc though.


Eureka sample service periodically fails when client connects

I am following the example from this repo.
Eureka server is running on localhost:8080.
As a next step I attempt to run the sample service, like this:
    ./gradlew :eureka-examples:runExampleService
Here is the output that I get:
$ ./gradlew :eureka-examples:runExampleService --stacktrace
    Inferred project: eureka, version: 1.4.6-SNAPSHOT
    Publication mavenNebula not found in project :.
    [buildinfo] Properties file path was not found! (Relevant only for builds running on a CI Server)
    Publication named 'mavenNebula' does not exist for project ':' in task ':artifactoryPublish'.
    None of the specified publications matched for project ':' - nothing to publish.
    :eureka-client:compileJava UP-TO-DATE
    :eureka-client:processResources UP-TO-DATE
    :eureka-client:classes UP-TO-DATE
    :eureka-client:writeManifestProperties UP-TO-DATE
    :eureka-client:jar
    :eureka-examples:compileJava
    warning: [options] bootstrap class path not set in conjunction with -source 1.7
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    1 warning
    :eureka-examples:processResources UP-TO-DATE
    :eureka-examples:classes
    :eureka-examples:runExampleService
    [main] WARN com.netflix.config.sources.URLConfigurationSource - No URLs will be polled as dynamic configuration sources.
    [main] INFO com.netflix.config.sources.URLConfigurationSource - To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
    [main] INFO com.netflix.config.DynamicPropertyFactory - DynamicPropertyFactory is initialized with configuration sources: com.netflix.config.ConcurrentCompositeConfiguration@46ee7fe8
    [main] INFO com.netflix.config.util.ConfigurationUtils - Loaded properties file file:/Users/lenok/Documents/Programming/Github/eureka/eureka-examples/conf/sample-eureka-service.properties
    [main] WARN com.netflix.config.util.ConfigurationUtils - file:/Users/lenok/Documents/Programming/Github/eureka/eureka-examples/conf/sample-eureka-service.properties is already loaded
    [main] INFO com.netflix.appinfo.providers.EurekaConfigBasedInstanceInfoProvider - Setting initial instance status as: STARTING
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using JSON encoding codec LegacyJacksonJson
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using JSON decoding codec LegacyJacksonJson
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using XML encoding codec XStreamXml
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using XML decoding codec XStreamXml
    [main] INFO com.netflix.discovery.shared.resolver.aws.ConfigClusterResolver - Resolving eureka endpoints via configuration
    [main] INFO com.netflix.discovery.DiscoveryClient - Disable delta property : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Single vip registry refresh property : null
    [main] INFO com.netflix.discovery.DiscoveryClient - Force full registry fetch : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Application is null : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Registered Applications size is zero : true
    [main] INFO com.netflix.discovery.DiscoveryClient - Application version is -1: true
    [main] INFO com.netflix.discovery.DiscoveryClient - Getting all instance registry info from the eureka server
    [main] INFO com.netflix.discovery.DiscoveryClient - The response status is 200
    [main] INFO com.netflix.discovery.DiscoveryClient - Starting heartbeat executor: renew interval is: 30
    [main] INFO com.netflix.discovery.InstanceInfoReplicator - InstanceInfoReplicator onDemand update allowed rate per min is 4
    Registering service to eureka with STARTING status
    Simulating service initialization by sleeping for 2 seconds...
    Done sleeping, now changing status to UP
    [main] INFO com.netflix.discovery.DiscoveryClient - Saw local status change event StatusChangeEvent [timestamp=1458260744041, current=UP, previous=STARTING]
    Waiting ... verifying service registration with eureka ...
    [DiscoveryClient-InstanceInfoReplicator-0] INFO com.netflix.discovery.DiscoveryClient - DiscoveryClient_SAMPLEREGISTERINGSERVICE/Alenas-MacBook-Pro.local: registering service...
    [DiscoveryClient-InstanceInfoReplicator-0] INFO com.netflix.discovery.DiscoveryClient - DiscoveryClient_SAMPLEREGISTERINGSERVICE/Alenas-MacBook-Pro.local - registration status: 204
    Waiting ... verifying service registration with eureka ...
    Waiting ... verifying service registration with eureka ...
    Service started and ready to process requests..
    > Building 88% > :eureka-examples:runExampleService

After I start the client, like this:
$ ./gradlew :eureka-examples:runExampleClient
    Inferred project: eureka, version: 1.4.6-SNAPSHOT
    Publication mavenNebula not found in project :.
    [buildinfo] Properties file path was not found! (Relevant only for builds running on a CI Server)
    Publication named 'mavenNebula' does not exist for project ':' in task ':artifactoryPublish'.
    None of the specified publications matched for project ':' - nothing to publish.
    :eureka-client:compileJava UP-TO-DATE
    :eureka-client:processResources UP-TO-DATE
    :eureka-client:classes UP-TO-DATE
    :eureka-client:writeManifestProperties UP-TO-DATE
    :eureka-client:jar
    :eureka-examples:compileJava
    warning: [options] bootstrap class path not set in conjunction with -source 1.7
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    1 warning
    :eureka-examples:processResources UP-TO-DATE
    :eureka-examples:classes
    :eureka-examples:runExampleClient
    [main] WARN com.netflix.config.sources.URLConfigurationSource - No URLs will be polled as dynamic configuration sources.
    [main] INFO com.netflix.config.sources.URLConfigurationSource - To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
    [main] INFO com.netflix.config.DynamicPropertyFactory - DynamicPropertyFactory is initialized with configuration sources: com.netflix.config.ConcurrentCompositeConfiguration@46ee7fe8
    [main] INFO com.netflix.config.util.ConfigurationUtils - Loaded properties file file:/Users/lenok/Documents/Programming/Github/eureka/eureka-examples/conf/sample-eureka-client.properties
    [main] WARN com.netflix.config.util.ConfigurationUtils - file:/Users/lenok/Documents/Programming/Github/eureka/eureka-examples/conf/sample-eureka-client.properties is already loaded
    [main] INFO com.netflix.appinfo.providers.EurekaConfigBasedInstanceInfoProvider - Setting initial instance status as: STARTING
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using JSON encoding codec LegacyJacksonJson
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using JSON decoding codec JacksonJson
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using XML encoding codec XStreamXml
    [main] INFO com.netflix.discovery.provider.DiscoveryJerseyProvider - Using XML decoding codec XStreamXml
    [main] INFO com.netflix.discovery.shared.resolver.aws.ConfigClusterResolver - Resolving eureka endpoints via configuration
    [main] INFO com.netflix.discovery.DiscoveryClient - Disable delta property : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Single vip registry refresh property : null
    [main] INFO com.netflix.discovery.DiscoveryClient - Force full registry fetch : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Application is null : false
    [main] INFO com.netflix.discovery.DiscoveryClient - Registered Applications size is zero : true
    [main] INFO com.netflix.discovery.DiscoveryClient - Application version is -1: true
    [main] INFO com.netflix.discovery.DiscoveryClient - Getting all instance registry info from the eureka server
    [main] INFO com.netflix.discovery.DiscoveryClient - The response status is 200
    [main] INFO com.netflix.discovery.DiscoveryClient - Not registering with Eureka server per configuration
    Found an instance of example service to talk to from eureka: sampleservice.mydomain.net:8001
    healthCheckUrl: http://Alenas-MacBook-Pro.local:8001/healthcheck
    override: UNKNOWN
    Connected to server. Sending a sample request: FOO Thu Mar 17 17:11:33 PDT 2016
    Waiting for server response..
    Received response from server: BAR Thu Mar 17 17:11:33 PDT 2016
    Exiting the client. Demo over..

    BUILD SUCCESSFUL

    Total time: 9.497 secs

It basically connects to the server and waits for response, etc.
At the same time on the service terminal I see the following happening. Sometimes when I do these actions I see the successful response on the eureka service:
  Client got connected... processing request from the client
    Received a request from the example client: FOO Thu Mar 17 17:30:16 PDT 2016
    Sending the response to the client: BAR Thu Mar 17 17:30:16 PDT 2016
    Simulating service doing work by sleeping for 10 seconds...
    Removing registration from eureka
    [main] INFO com.netflix.discovery.DiscoveryClient - DiscoveryClient_SAMPLEREGISTERINGSERVICE/Alenas-MacBook-Pro.local - deregister  status: 200
    Shutting down server. Demo over.

    BUILD SUCCESSFUL

    Total time: 4 mins 53.331 secs

And sometimes it gives errors, like here:
 Client got connected... processing request from the client
    Received a request from the example client: FOO Thu Mar 17 17:33:30 PDT 2016
    Sending the response to the client: BAR Thu Mar 17 17:33:30 PDT 2016
    Simulating service doing work by sleeping for 10 seconds...
    Removing registration from eureka
    Exception in thread "main" java.lang.NoClassDefFoundError: com/netflix/discovery/shared/transport/decorator/EurekaHttpClientDecorator$2
    	at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.cancel(EurekaHttpClientDecorator.java:71)
    	at com.netflix.discovery.DiscoveryClient.unregister(DiscoveryClient.java:886)
    	at com.netflix.discovery.DiscoveryClient.shutdown(DiscoveryClient.java:869)
    	at com.netflix.eureka.ExampleServiceBase.stop(ExampleServiceBase.java:89)
    	at com.netflix.eureka.ExampleServiceBase.start(ExampleServiceBase.java:80)
    	at com.netflix.eureka.ExampleEurekaService.main(ExampleEurekaService.java:45)
    Caused by: java.lang.ClassNotFoundException: com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator$2
    	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    	... 6 more
    :eureka-examples:runExampleService FAILED

    FAILURE: Build failed with an exception.

    * What went wrong:
    Execution failed for task ':eureka-examples:runExampleService'.
    > Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1

    * Try:
    Run with --info or --debug option to get more log output.

    * Exception is:
    org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':eureka-examples:runExampleService'.
    	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
    	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
    	at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
    	at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)
    	at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
    	at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:42)
    	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
    	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
    	at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
    	at org.gradle.api.internal.AbstractTask.executeWithoutThrowingTaskFailure(AbstractTask.java:305)
    	at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.executeTask(AbstractTaskPlanExecutor.java:79)
    	at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:63)
    	at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:51)
    	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:23)
    	at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:88)
    	at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:29)
    	at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62)
    	at org.gradle.execution.DefaultBuildExecuter.access$200(DefaultBuildExecuter.java:23)
    	at org.gradle.execution.DefaultBuildExecuter$2.proceed(DefaultBuildExecuter.java:68)
    	at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
    	at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62)
    	at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:55)
    	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:149)
    	at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:106)
    	at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86)
    	at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:80)
    	at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:33)
    	at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:24)
    	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:36)
    	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26)
    	at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
    	at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
    	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
    	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
    	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
    	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
    	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
    	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
    	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
    	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
    	at org.gradle.launcher.Main.doAction(Main.java:33)
    	at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
    	at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
    	at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
    	at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
    	at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
    	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)
    	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:56)
    Caused by: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
    	at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:365)
    	at org.gradle.process.internal.DefaultJavaExecAction.execute(DefaultJavaExecAction.java:31)
    	at org.gradle.api.tasks.JavaExec.exec(JavaExec.java:60)
    	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:63)
    	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:218)
    	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:211)
    	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:200)
    	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:579)
    	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:562)
    	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
    	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
    	... 47 more

    BUILD FAILED

    Total time: 1 mins 1.267 secs

What might be the problem?

@lenadroid are you running the client and server from the same git repo? Wondering if there may be a version mismatch somewhere as the server has a dependency on the client also.

@qiangdavidliu yeah, from the same.

@lenadroid this is a pretty weird one. The class that's failing with ClassNotFound is there, and your successful executions also prove that. Are you able to see the same sort of problems with a more complicated set up than the simple examples provided?

eureka is pretty unstable and avoid to use it in serious applications.

@SphereUser I'm curious to the unstability that you are seeing. We internally run eureka at very large scale and it has been stable for many years. One thing we are trying to update is documentation on configuration and operation of the servers, which currently on github is lacking some advanced info.

Closing this issue as the problem is specific (after more investigation) for the example when ran with gradle using the gradle applications plugin. Using the dist option and also in real operation the ClassNotFoundExceptions are not seen.


fix: remove old view prop types

Platforms affected
Web for React Native Web 0.12+
iOS and Android on React Native older than 0.44
What does this PR do?
Removes the usage of old ViewPropType
ViewPropType has been deprecated for a while, and completely removed from the react-native-web. trying to import ViewPropTypes causes an error with react-native-web.
This will also cause a breaking change for projects using older versions of react native that still uses ViewPropTypes.
What testing has been done on this change?
Test on iOS and Android Simulator
Tested features checklist

[x] Default setup (example)
[ ] Carousels with and without momentum enabled (prop enableMomentum)
[ ] Vertical carousels (prop vertical)
[ ] Slide alignment (prop activeSlideAlignment)
[ ] Autoplay (prop autoplay)
[ ] Loop mode (prop loop)
[ ] ScrollView/FlatList carousels (prop useScrollView)
[ ] Callback methods
[ ] ParallaxImage component
[ ] Pagination component
[ ] Layouts and custom interpolations

Thanks for the PR @Naturalclar!
However, I fear that View.propTypes.style is not defined in recent versions of React Native, and therefore this change will break the plugin.
For example, I've just tried with version 0.61.4 of RN and it broke immediately.

This change is my last hurdle to getting react-native-web working for our App so I'm keen to move it along. @bd-arc would something like the following be acceptable to remove the compile-time dependency on React.ViewPropTypes while maintaining backwards compatibility?
// src/ViewPropTypes.js:
import React from 'react-native';
const ViewPropTypes = React.ViewPropTypes || React.View.propTypes;
export default ViewPropTypes;

// src/pagination/Pagination.js:
import ViewPropTypes from '../ViewPropTypes';
// ...
containerStyle: ViewPropTypes.style,
dotColor: PropTypes.string,
dotContainerStyle: ViewPropTypes.style,

@ncjones I'm not aware of what might break with react-native-web since it has never been the focus of this plugin. If it solves things for web users, count me in.
The only thing I'll ask is that you try this with RN 0.61 and then with RN 0.62. If it works for both and you're positive it won't break anything on older versions, I'll gladly merge your upcoming PR :-)

@bd-arc Thank you for the review!
I've made a fix in the PR.
I couldn't make the change work without removing both ViewPropTypes, and View.propTypes altogether, since View.propTypes does not exist in later version of React Native, and ViewPropTypes has been removed from react-native-web.
iirc, the core react-native package has already deprecated the use of propTypes and ViewPropTypes will eventually be removed from the core in the future releases.
changing the proptype to PropTypes.object makes the typing less strict, but it was the only workaround I could think of while continuing to use propTypes.

@bd-arc Actually both React.View.propTypes and React.ViewPropTypes are deprecated in react-native and therefore not supported by react-native-web so the above solution definitely will not work as it stands. Validating the style props as simply "object" when there is no ViewPropTypes available would probably work but obviously is not as strict.
The react-style-proptype package looks like it would work if you are ok with adding a new dependency.
I'm not sure if dropping prop types and relying on Typescript and/or flow is an option but that is what is suggested in the react-native web release notes.
BTW I'm interested in react-native-web not to build a web app from a single source but to enable testing our react native app with Cypress.

@Naturalclar @ncjones Thank you both for your input!
I'd love nothing more than to migrate the plugin to TypeScript. All of our recent projects are Typescript-based and it's a shame this plugin isn't.
However, I don't currently have time for that — the little I had was used to work on the brand new version of the plugin. I know it's a stretch, but if one of you feel like implementing Typescript for v4, that would be awesome!

@Naturalclar  This plugin might help you out:
https://github.com/oliviertassinari/babel-plugin-transform-react-remove-prop-types
It seems like its working for me so far with the current release of react-native-snap-carousel. 😊


Alice demo: Type Error: expected str, bytes or os.PathLike object, not int

Hi,
I'm trying to run the Aries demos... but I'm getting an error when I run Alice.
I'm using Ubuntu 20.04.1  and when I run faber everything works well, it expects a connection...
command used:
LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber
But when I run Alice I get this error:

command used:
LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice
I can't seem to find a solution or a cause of this problem... Have anyone seen this before?
Thanks in advance.

I'm running on Ubuntu 18.04 and everything worked fine.  I notice that some of the messages from the script I'm running are different from yours -- notably:
~/repos/aries-cloudagent-python/demo [main] 09:32 $ LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice
Preparing agent image...
sha256:8c1508e46dc1a6dca8dd634dc49bca3e588c19966d858a55fbec18f0a9a50f4b
Trying to detect ngrok service endpoint
ngrok not detected for agent endpoint
<IP_ADDRESS>
Starting [alice] agent with args [--port 8030]

#7 Provision an agent and wallet, get back configuration details
Alice      | ['/home/indy/.pyenv/versions/3.6.13/bin/python', '-m', ...

Is it possible you aren't up to date on the code?  Even then, I wouldn't expect a problem.
I'm running the same python 3.6.9, so it's not that.
@ianco -- any ideas on what might be wrong?

@ianco -- any ideas on what might be wrong?

No, it's odd that faber works but alice doesn't, they both use the same common code to start up the agent

I figured it out, I was giving it a specific seed instead of a random one. My fault, thanks for your reply though! On 5 Mar 2021 17:41, Ian Costanzo<EMAIL_ADDRESS>wrote:
@ianco -- any ideas on what might be wrong?
No, it's odd that faber works but alice doesn't, they both use the same common code to start up the agent
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Correspondance between query and negative_key

Hi, thanks for your implementation. I would love to confirm the following case with you:
Suppose I have each query that has one positive key and two negative_keys, should I organise my input as:
query[0] -->positive_key[0] --> negative_key[0] & negative_key[1]
query[1] -->positive_key[1] --> negative_key[2] & negative_key[3]
....
Thanks very much.

Sorry for the late reply. Each query sample is paired with exactly with one positive key. But the negative keys are not paired with the query at all. The set of negative keys is completely distinct from the query.
The query and positive_key arrays should have the same number of samples and dimensionality. The negative key can have any number of samples as long as the feature dimensionality is the same.
For example:
      q = torch.randn(64, 48)
      pk = torch.randn(64, 48)
      nk = torch.randn(5, 48)

      l = loss(query=q, positive_key=pk, negative_keys=nk)

For most contrastive learning tasks you don't need the explicit negative keys.
I added it because I needed it when I was looking at the Spatially-Correlative Loss for image translation.
I am thinking of removing the negative_key parameter and adding a separate repository for a loss with it, because most people interested in InfoNCE won't need it and it's only confusing.

Adding an option such that the user can choose how the negative key behaves is probably the best option.


Text change: flush delay duration

Description (what needs to be done) / Expected Behavior
in last screen of the dao creator, the phrase "flush delay duration" should be changed to "proposal execution delay", to say consistent text as earlier page
Acceptance Criteria
text is changed, and it matches the phrase on the dao creator page where the user sets the proposal execution delay
Supporting information (Figma link, notes, etc)
When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

Fixed on #438


SSL Database Error: MYSQLi was configured for an SSL connection, but got an unencrypted connection instead!

Introduction
I encountered a persistent error when connecting to a Planetscale database which requires the SSL_CA to be provided as part of the connection string.
The error

MYSQLi was configured for an SSL connection, but got an unencrypted connection instead!
Filename: system/database/drivers/mysqli/mysqli_driver.php
Line Number: 223

This error also occurs when the pdo driver is used with a correct mysql dsn string

PDO_MYSQL was configured for an SSL connection, but got an unencrypted connection instead!
Filename: system/database/drivers/pdo/subdrivers/pdo_mysql_driver.php
Line Number: 191

Environment

PHP 8.2.3
Codeigniter 3.1.13

What I resolved
The error disappeared after changing this snippet
// Prior to version 5.7.3, MySQL silently downgrades to an unencrypted connection if SSL setup fails
:
:
version_compare($this->_mysqli->client_info, '5.7.3', '<=')

to
version_compare($this->_mysqli->server_info, '5.7.3', '<=')

This change was suggested in the codigniter forum but wasn't responded to.
Question

Is the fix valid and safe?
Could the issue be with at the database provider's end?

**Note: This is the first time I encountered this error for a db configured with SSL.

I'm also encountering this issue, it works fine using the planetscale sample code without any framework.

Did you resolve it?.


Local Token Validation

Description
In a micro-service architecture where the bearer token is passed to each service, it's much more efficent for each micro-service to validate the token locally than calling a centralized authorization service.
Expected behaviour
Point "x-tokenInfoUrl" (or a different attribute) to a local function that will validate the bearer token locally.
Actual behaviour
"x-tokenInfoUrl" only accepts URLs.

@horomena we (at Zalando) actually support local token validation via HTTP, e.g. by running https://github.com/zalando/planb-tokeninfo as a sidecar in your Kubernetes pod :smirk:
But in general it sounds like a good idea and it's related to #124.


Scale fit updates

Overview
This update to the scale fitting algorithm improves the rendering of dataset axes. The fitting algorithm was changed from 2 passes to 2.5 passes. This allows the fit function of each scale to be passed an object containing the margins around the scale. The margin is the unused area that can be used if necessary. For a horizontal dataset axis, this is the area underneath the vertical axes on the left and right sides of the chart. When rendering labels, especially rotated labels, this area is used to prevent unnecessary padding of the left side of the chart.
Old display

New Display

@tannerlinsley @derekperkins check this out please.


Fix possible spdlog version mismatch

ThermoFun is also linking with spdlog so it's better to depend on it explicitly to have a correct pin in its dependencies.

Checklist

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

@conda-forge-admin, please rerender

Note: we were getting a version of thermofun built with spdlog 1.12 and chemicalfun depending on spdlog 1.13, so it was conflicting at runtime.


Classes for implementation are missing or guide is outdated

I am currently rewriting the entire project, expect a new version within the coming weeks.


Pass fixes

This fixes a couple of problems in CheckPointPass and LiveVariablesPass:

CheckPointPass: I was manually incrementing the instruction iterator, which was causing some instructions to be skipped
LiveVariablesPass: I am no longer using a default value for the size of the live locations

LGTM. Ready to merge?

@vext01 Yep, seems ready to me.


Get Signal information of Client?

Can i get Channel, WiFi Signal Strength of a client.

"""
https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-signal-quality-history
Returns signal quality (SNR/RSSI) over time for a device or network client
"""
import meraki
Defining your API key as a variable in source code is not recommended
API_KEY = '6bec40cf957de430a6f1f2baa056b99a4fac9ea0'
Instead, use an environment variable as shown under the Usage section
@ https://github.com/meraki/dashboard-api-python/
dashboard = meraki.DashboardAPI(API_KEY)
network_id = 'L_646829496481105433'
response = dashboard.wireless.getNetworkWirelessSignalQualityHistory(
network_id
)
print(response)


Display code coverage in pull requests

Related to https://github.com/autowarefoundation/autoware-documentation/issues/2, I would like to add the feature to measure and display code coverage for pull requests to improve review process.
Considerations

About the reporter, whether to use CodeCov or to create a function to measure and report in GitHub Actions.
How to specify labels for coverage by label, whether to automatically collect all labels or to specify the labels we want to set.

:+1:
I think using CodeCov at first is efficient.

@KeisukeShima Can this be closed?
Or will you work on coverage by label in this issue? If so, I think the title should be changed.

@KeisukeShima Can this be closed? Or will you work on coverage by label in this issue? If so, I think the title should be changed.

I think that getting coverage by label is also part of this issue.
If we need to change the title, how about changing it to Display labeled code coverage in pull request?

I think we can close this for now. (Codecov integration is done.)
We'll reconsider this in https://github.com/autowarefoundation/autoware.core.


[material-ui][TextField] When with minRows, it makes the height from small to final height

Steps to reproduce

open https://stackblitz.com/edit/nextjs-ziwkdm?file=package.json
click refresh multiple time

you will see the height of textarea change from:

to:

Current behavior
The height will change from a small height to the final height
Expected behavior
No height change, it will make web page cls metric bad
Context
fix the web page cls, you can see the prompt input box height change:
https://github.com/mui/material-ui/assets/41773861/b1b01e6f-ea0b-4015-b33b-c8540849d9ca
Your environment

npx @mui/envinfo
   System:
    OS: macOS 14.5
  Binaries:
    Node: 20.13.1 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/node
    npm: 10.8.1 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/npm
    pnpm: 9.1.0 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/pnpm
  Browsers:
    Chrome: 125.0.6422.142
  npmPackages:
    @emotion/react: ^11.11.4 => 11.11.4
    @emotion/styled: ^11.11.5 => 11.11.5
    @mui/material: ^5.15.19 => 5.15.19
    @types/react: ^18 => 18.2.75
    react: ^18 => 18.2.0
    react-dom: ^18 => 18.2.0
    typescript: ^5 => 5.4.5

Search keywords: TextField, minRows, height

@ZeeshanTamboli do you know if this might be related to the recent TextareaAutosize fixes?

do you know if this might be related to the recent TextareaAutosize fixes?

Doesn't look related to the recent TextareaAutosize fixes. I cannot reproduce the issue:
https://github.com/mui/material-ui/assets/20900032/a68dbed2-be67-42f5-8d50-f896da7aaeba

@ZeeshanTamboli Try open the devtools and disable cache.

@ZeeshanTamboli You can more easily to reproduce by using performance throttle to slow down performance:

chrome126 support throttling x20 😄

Some cases can use minHeight, but sometimes the initial height is large than final actual height.

@mi-na-bot can you provide a piece of simple code to demo?

Thanks your help @mi-na-bot I also decide give up official minRows property and set the minHeight/maxHeight manually


#19 #20 Do not return duplicates from the vector index

#19 #20

@tomusher Tried to write a test but I'm not getting it quite right...


HDDS-1502. Add metrics for Ozone Ratis performance.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
923
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
457
trunk passed

+1
compile
217
trunk passed

+1
checkstyle
54
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
867
branch has no errors when building and testing our client artifacts.

+1
javadoc
145
trunk passed

0
spotbugs
333
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
580
trunk passed

_ Patch Compile Tests _

+1
mvninstall
502
the patch passed

+1
compile
259
the patch passed

+1
javac
259
the patch passed

-0
checkstyle
34
hadoop-hdds: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
722
patch has no errors when building and testing our client artifacts.

+1
javadoc
163
the patch passed

+1
findbugs
595
the patch passed

_ Other Tests _

-1
unit
219
hadoop-hdds in the patch failed.

-1
unit
1787
hadoop-ozone in the patch failed.

+1
asflicense
37
The patch does not generate ASF License warnings.

7748

Reason
Tests

Failed junit tests
hadoop.ozone.container.common.statemachine.commandhandler.TestCloseContainerCommandHandler

hadoop.ozone.client.rpc.TestBCSID

hadoop.ozone.container.TestContainerReplication

hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion

hadoop.ozone.container.common.transport.server.ratis.TestCSMMetrics

hadoop.ozone.om.TestOzoneManagerHA

hadoop.ozone.om.TestOmAcls

hadoop.ozone.container.common.statemachine.commandhandler.TestCloseContainerByPipeline

hadoop.ozone.om.TestOMDbCheckpointServlet

hadoop.ozone.ozShell.TestOzoneShell

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/833

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 2c6ce6e248b1 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 0d1d7c8

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/artifact/out/diff-checkstyle-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/testReport/

Max. process+thread count
3780 (vs. ulimit of 5500)

modules
C: hadoop-hdds/container-service U: hadoop-hdds/container-service

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-833/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

@bshashikant  Thanks for working on this! The changes look good to me. I have a minor rename comment. +1 o.w.

Thanks @lokeshj1703 for the review. I have committed this change to trunk.


TEST: Added test for translations

Codecov Report

Merging #83 (7bab6ba) into master (c6c09df) will increase coverage by 7.82%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #83      +/-   ##
==========================================
+ Coverage   88.26%   96.08%   +7.82%
==========================================
  Files           6        6
  Lines         358      358
==========================================
+ Hits          316      344      +28
+ Misses         42       14      -28

Flag
Coverage Δ

pytests
96.08% <ø> (+7.82%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sphinx_proof/translations/_convert.py
93.33% <0.00%> (+93.33%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c6c09df...7bab6ba. Read the comment docs.


Issues joining game after failure to join

If a player fails to connect to a game, and tries to join again without reloading the page, the "waiting for other players" page will display, even though the player still hasn't connected.

Failure to connect in this case being a mistyped room code.

Config was fixed and app rebooted.


How to upgrade sidercar does not affect the application

My environment：k8s 1.15 istio1.6
I refer to this article https://istio.io/v1.6/docs/setup/upgrade/, I found that upgrading the data plane will still affect the existing applications.
Is there any automated tool that can upgrade sidecar without affecting existing applications?
Supplement: don't affect existing applications, which means to update sidecar without restarting the application

This is not currently possible. See https://github.com/istio/istio/issues/33072


Packages dashboard for #25

In order to merge #25 we need to update this packages:

[x] utils
[x] model
[x] module
[x] prisma
[x] rest
[x] rest-fastify
[x] graphql
[x] graphql-yoga
[x] aws-sqs
[x] aws-lambda-sqs
[x] aws-lambda-rest
[x] cron
[x] example

Packages that have a good test coverage:

[ ] utils
[x] model
[x] module
[ ] prisma
[ ] rest
[ ] rest-fastify
[ ] graphql
[ ] graphql-yoga
[ ] aws-sqs
[ ] aws-lambda-sqs
[ ] aws-lambda-rest
[ ] cron
[ ] example

The PR now compiles, I'll merge it into develop so we can start working on a different branch for every issue.


Reattach to DevTools inspector

Is there a way to reattach an already open devtools inspector after the app has been closed and reopened? It's really annoying having to reopen the devtools window every time. Here's a screenshot to illustrate:

I'd be happy to send a PR if anyone sends directions for how to fix this

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

Unfortunately we can't really fix this.  Perhaps we should focus on fixing it in Chrome itself?

I was wondering if stetho could automatically close the opened devtool when the app process is killed?
It would also be handy to programmatically open a devtool when the app starts (if a stetho is configured to of course).

@lynfogeek  see #161

2019! No plan to reopen this issue and actually implement the requested feature?


WASM/Javascript build of OpenTimelineIO

Would be nice to have a javascript compatible wrapping of the core library.

We recently had some discussions about this in Slack. I'm just copy/pasting the important bits here for wider visibility.
@JeanChristopheMorinPerso has done some promising work on building JS bindings to OTIO via WASM recently. He says:

I have opentime, Imath, serialization and deserialization functions, SerializableObject, SerializableObjectWithMetadata (including exchange of metadata between JS and C++), custom schema registration and subclassing working. These are all working pretty well (though I need to port the python  unit tests to JS)

@rogernelson experimented with building opentime via emscripten.

JS + wasm bindings is something I'd be very interested in.  One of the first things I did was emscripten bindings of the opentime library, just as a PoC to see if it would work (which it did).  I used it to make a timecode calculator in running in the browser (not especially useful, just an exercise to make sure it worked).

There is a mostly-working WASM build of Raven, which includes OTIO.
Also, for reference.

Adding Python WASI support to Wasm Language Runtimes
SQLite Wasm in the browser backed by the Origin Private File System - Chrome Developers

Also, we've been hearing second hand from people attempting to use OTIO in web-native contexts that the lack of Javascript bindings is leading developers to read/write OTIO JSON without using the OTIO API. We would like to discourage that route since it will inevitably lead to incorrect/mismatched behavior and version incompatibility.


Remove Excel lock file

Removes Excel lock file and adds a .gitignore to prevent any more being added by mistake.

+1


Error when downloading jpgs from Onedrive

I am trying to use rclone to sync a Onedrive folder to a Ubuntu machine running in Amazon AWS and I am getting some errors when processing some files. These files are all jpgs and the problems I see are similar to this:
"2016/04/23 19:56:03 Maria Duenas/Mision olvido (252)/cover.jpg: Corrupted on transfer: sizes differ 35395 vs 22482"
I have attached here the file that gives the error. It does not happen with all jpgs, some transfer fine but it only happens with jpg files, does not happen with other kind of files

More info below

What is your rclone version (eg output from rclone -V)

v1.29

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Ubuntu 64bit running headless in Amazon AWS

Which cloud storage system are you using? (eg Google Drive)

Onedrive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync granados-onedrive:/Libros/Biblioteca Biblioteca

A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)

Too big to paste here, attaching as doc file
rclone -log.docx

I'm pretty sure this is the same problem as #399
This is caused by a known bug in onedrive which they haven't been fixing for the last 18 months!
I'm leaning towards the --no-check-size option as you'll see from that which is a work-around.

Yes, that seems the same problem, so I am going to close this. The --no-check-size option seems a nice solution

I've implemented an --ignore-size flag which you can use to work-around this issue.  I've verified it does the right thing.
Here is a beta with that fix in for you to try.
http://pub.rclone.org/v1.29-1-gbb75d80-62-g46135d8β/


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
When trying to install the VLC Package it tries to install a "newer" version.
Official download is 3.0.16. Winget lists the version 3.0.17

Steps to reproduce
Open CMD or Powershell.
Use the following Command "winget install VideoLAN.VLC"
Actual behavior
Tries to install Version 3.0.17 of VLC Media Player and returns and error.
Expected behavior
Trying to install Version 3.0.16 of VLC Media Player.
Environment
C:\Users\thomas.kisling>winget --info
Windows Package Manager v1.2.10271
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.556
Package: Microsoft.DesktopAppInstaller v1.17.10271.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Screenshots and Logs

Via the link given in the Winget command you can download the MSI and EXE
https://get.videolan.org/vlc/3.0.16/win64/vlc-3.0.16-win64.exe
https://get.videolan.org/vlc/3.0.16/win64/vlc-3.0.16-win64.msi
But the error still persists on Winget install VideoLan.VLC

Issue doesn't appear in free environment.
I will need to look into the first environment for trouble shooting.
Thanks for the help!


Use codegen on non-input types

It seems that with the current version of the plugin, validation schemas are only generated for graphql input types found in the schema. i was wondering if it would be possible to add an option to the plugin to generate validation schemas for graphql type as well as input?

@willd-i2o I'm just curious.
How do you think the usage if available code generation for type too.

@Code-Hex
I use apollo client alongside graphql-codegen
My form state is populated with data from useQuery, these queries utilise the type objects defined in the schema, so therefore my form state is typed against these type objects.
My validation schema has to match the form state, since I'm running the validation schema via the zod resolver for react-hook-form.
The input types are only used when I'm submitting the form and transforming my form state data into a mutation input type. The input types don't match 1-to-1 with the type types used in the query, so the codegen producing validation schema's for my input types doesn't help me with constructing a validation schema for my form.

@willd-i2o Thanks for your explanation.
I want to confirm my understanding is correct. for example, there is a schema.
type Human {
  name: String!
  age: Int!
}

input HumanInput {
  name: String!
  age: Int!
}

Then you want to validate only for type Human. and convert any users who have been inputted type Human to input HumanInput when submitting to mutation, right?

@Code-Hex
Yeah that sounds about right

@willd-i2o Thanks. Don't you use fragment also?
I think this a little bit difficult.

@Code-Hex
I think I could do what I would like to do without the codegen supporting fragments, but not entirely sure.

I'm sorry. After due consideration, I did not feel this desperately needed to be addressed. If there are other requests, I will revisit this issue.

@willd-i2o I'm sorry.
After due consideration, I did not feel this desperately needed to be addressed. If there are other requests, I will revisit this issue.

I use Zod to validate data from my database and other sources as well. Sure that incoming data should be in the model you expect. Of course, corrupted data or a service that broke their API contract would then cause errors in your app.
I can write my own Zod schemas, of course. But I have to define my outgoing type anyway in graphQL.
Let's take this example:
  type User {
    id: ID!
    email: String!
    disabled: Boolean
    createdAt: String
    updatedAt: String
  }

  input NewUser {
    id: ID!
    email: String!
  }

  type Query {
    user(id: ID!): User
  }

At some point I am going to assemble that User JSON for my user() resolver. Let's say I am fetching the data from something like Firebase Firestore. Well, Firestore give you any as the base type. Sure, I can cast it in a few ways - but if I don't actually validate that data - it might not be valid.
If I can auto-generate zod types from the graphql types, then I can further pick, omit, extend, etc... the zod schema for my DB.


o + enter doesn't work

Describe the bug
o + enter key doesn't work
Reproduction
https://stackblitz.com/edit/vitejs-vite-akegze?file=package.json
Steps to reproduce
npm run dev
o + enter key
System Info
Mac Os

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I can't reproduce on Mac. o+enter properly opens the app in the browser.

@patak-dev
all key (h + q + c + o + r) + enter work , except o + enter ,
I will check my mac shortcut

Closing for now as we cannot reproduce and it's unactionable.


fix: better errors on failed uploads

Addresses #258

@juliusmarminge This is something that I hacked together in ~2 min, we should probably figure out how best to do something like this though.

This won't work for the same error in server uploads though

because of DOMParser? We can swap it for some other parser, or I can write a regex to extract the strings we want...

This won't work for the same error in server uploads though

because of DOMParser? We can swap it for some other parser, or I can write a regex to extract the strings we want...

Yes, it's a browser thing.
Regex could work I guess :)

@juliusmarminge here's a regex version for you

Hi @markflorkowski
Maybe I'm missing something, but it looks like to me that you are extracting the error code despite the fact that it's not used anywhere.
On the image below error constructor receives parsed message only

@Mr0Bread Yes, I was playing around with what info is returned from s3 to see what would be most useful. Probably should merge the two and return a formatted string, or pass both into the error (one as cause, one as message). This was not meant to be merged as is, more just getting an idea down so we can figure out the correct way to pass this information to the users.

I added some stuff @markflorkowski


fix: golang version on go.mod & FOR_DEVELOPERS.md

👏 解決掉的 issue / Resolved Issues

close #76

📝 相關的 issue / Related Issues
none
⛏ 變更內容 / Details of Changes

remind everyone to support golang 1.16

LGTM


Add runtime support for Linux target

Apollo Android v3 doesn't currently target Linux.

+1 over here.
It looks like most of the Kotlin/Native world is forced to use Ktor for client HTTP. On Linux, Ktor currently only supports cURL for networking, with CIO maybe to come later. So, with that in mind, I have 2 questions 😬

Can Apollo runtime work on top of Ktor + cURL, which would then support all Kotlin/Native targets out of the box?

What's the main blocker for runtime support on Linux, given that Mac is already supported?

Thanks! <3

Hi @milosmns 🐧 👋

Nope, apollo-runtime isn't compiled for linux at the moment so you can't make it work with cURL. You can though use apollo-api directly without apollo-runtime (documentation). It contains the parsers and everything you need to compose a query but not the actual HTTP client.

I don't think there's a hard blocker, it's mostly a matter of prioritization and linux support hasn't been a focus lately. The main problem I can envision is that apollo-runtime currently expects a DefaultHttpEngine and I'd prefer we don't pull ktor in the dependencies by default. But I think starting with a placeholder HttpEngine that throws NotImplementedException would be fine. Then we'd need a separate ktor HttpEngine that users could register at runtime. Then we'd also need linuxArm64 maybe?

All in all, you can use linuxX64 today if you write the networking code yourself. Getting apollo-runtime will require some plumbing but it's certainly doable.

Thanks for the quick response @martinbonnin!
Alright, makes sense, appreciate the update. I think that your proposal with a "not implemented" error on Linux should also work for the time being and would reduce the amount of plumbing needed for whoever wants to use this on Linux. But Linux for ARM is another beast altogether... not sure if even Ktor is supporting it, I'd need to check.


How to encrypt TOC under NexT theme

It is said that TOC can be encrypted in themes/next/layout/_macro/sidebar.swig.
However, after I used another one's code hexo博文加密 , there is some bug in the TOC of encrypted article.
I want the presentation like this Hexo Blog Encrypt . How can I make it?

I just found the way to solve the problem. I will write a blog about it and put it here later.


chore: add grpc-health-probe for Health checks

Description
Adds the grpc-health-probe binary to the OpenFGA container during the Docker build process.
Since OpenFGA is a gRPC server with an HTTP proxy on top of it, it makes sense to expose the Health checks via the grpc-health-probe. This is the defacto standard way of doing Health checks for gRPC, and it aligns with the gRPC Health Check Protocol as well.
https://kubernetes.io/blog/2018/10/01/health-checking-grpc-servers-on-kubernetes/
https://github.com/grpc-ecosystem/grpc-health-probe/
We will use this in the official OpenFGA Helm chart as well with:
...
readinessProbe:
  exec:
    command: ["/bin/grpc_health_probe", "-addr={{ .Values.grpc.addr }}"]
  initialDelaySeconds: 5

References
https://github.com/orgs/openfga/discussions/109
Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Looks like I need to fix the make function-test target (which uses docker build ..). Docker builds need to happen against a particular OS/ARCH combination since the container embeds a grpc-health-probe binary inside of it.
That's why the functional tests are failing right now.

This does not seem to be working (based on the included docker-compose.yaml)

Realized I needed to update the image first, but note that building on this branch seems broken:

Realized I needed to update the image first, but note that building on this branch seems broken:

The issue is that the container build depends on os/arch specific combinations, and so a simple docker build doesn’t do it. You’ll need to set the build args for it to work e.g.
docker build --build-arg OS=linux --build-arg ARCH=amd64 -t openfga/openfga:testing .
I'm working on adding these changes to the Makefile 👍

Tested and working as expected 👍🏽
Any chance we can default the OS to "linux" and ARCH to "amd64"? I think we and folks are most likely to build for these for this combo, and we have the ability to override for those who need it

@rhamzeh yep, I committed your suggestions. That's a good idea, thanks!


Add initial jutut instructions

Fixes #38
Description
What?
[ANSWER HERE]
Why?
[ANSWER HERE]
How?
[ANSWER HERE]
Fixes #
Testing
Remember to add or update unit tests for new features and changes.

How to test your changes in A-plus
How to test accessibility

What type of test did you run?

[ ] Accessibility test using the WAVE extension.
[ ] Django unit tests.
[ ] Selenium tests.
[ ] Other test. (Add a description below)
[ ] Manual testing.

[ADD A DESCRIPTION ABOUT WHAT YOU TESTED MANUALLY]
Did you test the changes in

[ ] Chrome
[ ] Firefox
[ ] This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken
Translation

[ ] Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

[ ] Did you follow our style guides?
[ ] Did you use Python type hinting in all functions that you added or edited? (type hints for function parameters and return values)

Have you updated the README or other relevant documentation?

[ ] documents inside the doc directory.
[ ] README.md.
[ ] Aplus Manual.
[ ] Other documentation (mention below which documentation).

Is it Done?

[ ] Reviewer has finished the code review
[ ] After the review, the developer has made changes accordingly
[ ] Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!

The text looks good to me (with couple of small suggestions). If we don't have one already, we should have some sort of acknowledgments section to credit those who have provided input to the manual.

Acknowledgements for the whole project are here:
https://apluslms.github.io/about/authors/
It combines people from all components include the Aplus-manual repo.


Updated firsttime

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[ x] Refactoring

What's new?

[ ] PR closes #<issue_number>
[x ] I updated the firsttime doc in GitHub to match the one I updated in our docs

Before submitting Pull Request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[ ] Fill up your KSM address: Payout

Community participation

[x ] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

I accidentally opened a new branch within the initial one. This
First_Time.md is updated with the First_Time.md that we have in our
documents
On Tue, Apr 26, 2022 at 3:14 AM roiLeo @.***> wrote:

@.**** commented on this pull request.
what's the difference with #2901
https://github.com/kodadot/nft-gallery/pull/2901?
—
Reply to this email directly, view it on GitHub
https://github.com/kodadot/nft-gallery/pull/2902#pullrequestreview-952873313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSXNDXLNLYYGDBTM77JUULVG6JWJANCNFSM5UKZOGJA
.
You are receiving this because you authored the thread.Message ID:
@.***>


docs: update ExpensiMark link

Details
The README.md link to ExpensiMark was looking for an ExpensiMark.js file which no longer exists. Updated to ExpensiMark.ts
Related Issues
n/a
Manual Tests
n/a
Linked PRs
n/a

I have read the CLA Document and I hereby sign the CLA


Research and PoC - Turn off instances in an environment overnight

User Story
There is no reason to have non production instances (EC2, RDS, etc) constantly running, outside of working hours they should be shut down.
Value
Save money and increase the sustainability of the platform.  This also encourages work life balance if instances are not accessible at night.
Questions / Assumptions
There should be some way of excluding instances eg a tag.
Production instances should not be included.
This would need to be across all the mp accounts, could this be done centrally or would it need to be done on a per account basis?
Possible solutions include systems manager automation documents or a lambda.
We need to ensure instances can be started and stopped on a schedule without human intervention, application teams will also need to ensure this.
https://aws.amazon.com/blogs/mt/systems-manager-automation-documents-manage-instances-cut-costs-off-hours/
Definition of done

[ ] readme has been updated
[ ] user docs have been updated
[ ] another team member has reviewed
[ ] tests are green

Reference
How to write good user stories

https://github.com/ministryofjustice/modernisation-platform/pull/1253

One solution that I got working on Sprinkler is by using the third-party terraform module terraform-aws-lambda-scheduler-stop-start as follows:
#------------------------------------------------------------------------------
# Schedule stop/start EC2 instances
#------------------------------------------------------------------------------

module "stop_ec2_instance_nights" {
  source                         = "github.com/diodonfrost/terraform-aws-lambda-scheduler-stop-start?ref=3.1.3"
  name                           = "stop_ec2_instance_nights"
  cloudwatch_schedule_expression = "cron(0 21 ? * * *)" # Everyday at 21:00 GMT
  schedule_action                = "stop"
  autoscaling_schedule           = "false"
  ec2_schedule                   = "true"
  rds_schedule                   = "false"
  cloudwatch_alarm_schedule      = "false"
  scheduler_tag                  = {
    key   = "stop_nights"
    value = "test" # only for the test environment
  }
}

module "start_ec2_instance_mornings" {
  source                         = "github.com/diodonfrost/terraform-aws-lambda-scheduler-stop-start?ref=3.1.3"
  name                           = "start_ec2_instance_mornings"
  cloudwatch_schedule_expression = "cron(0 6 ? * * *)" # Everyday at 6:00 GMT
  schedule_action                = "start"
  autoscaling_schedule           = "false"
  ec2_schedule                   = "true"
  rds_schedule                   = "false"
  cloudwatch_alarm_schedule      = "false"
  scheduler_tag                  = {
    key   = "stop_nights"
    value = "test" # only for the test environment
  }
}

resource "aws_kms_grant" "stop_start_scheduler" {
  key_id            = aws_kms_key.ebs.id
  grantee_principal = module.start_ec2_instance_mornings.lambda_iam_role_arn
  operations        = [
    "Decrypt",
    "DescribeKey",
    "CreateGrant"
  ]
}

https://github.com/ministryofjustice/modernisation-platform/pull/1260

We had a conversation with the team after today's scrum and decided that AWS Instance Scheduler is another alternative which might be the closest to what we will need in the end: https://aws.amazon.com/solutions/implementations/instance-scheduler/. While the terraform module would work, AWS Instance Scheduler allows cross-account and flexible scheduling, which might be beneficial for configuration at platform level. Only downside is that it's a new feature and there doesn't seem to be terraform module for it yet. We need a separate POC to see how this solution would work.

Having used AWS Instance Scheduler previously, it's supplied as a cloudformation template by default. It could be migrated into terraform with some work, although there are (from memory) some interactions with dynamodb which are configured using an AWS-supplied CLI python package. Again (from memory) I believe those can be conducted either manually, or ported into Terraform as they're just DynamoDB entries ( relevant resources in the AWS provider are probably aws_dynamodb_table / aws_dynamodb_table_entry ).

Having looked into this the following things stand out:

Instance Scheduler is supplied in two cloudformation templates. Would we recreate this in terraform, and if so where would we store the code?
Which account would the main Instance Scheduler resources be deployed?
The scheduler works by reading a tag - eg availability - and then matching the value to a schedule defined in dynamodb - eg weekdays. Is a single tag/key relationship enough for us?
Do we expect this to be something teams opt into or opt out of?

For the proof of concept we're using the Amazon-supplied Cloud Formation Templates.
We've discussed internally which accounts to make use of.
We've agreed that the scheduler is sufficient as is.
We've agreed that the scheduler will be something teams will opt out of.

At present we have two CFTs deployed and can see CloudWatch logs indicating that we're successfully assuming a role in a remote account and querying instances appropriately. We also see an error message indicating that the schedule we've set up is not matching the schedule name being read despite the two appearing identical.
I have raised a support request in the calling AWS account to see what support AWS can offer us.

Resolved issues we had with schedules not reading.
Confirmed that we can apply a schedule across accounts and shut down / start up instances based on schedules.
Might be some more value we can drive out of this card, but generically it looks like this will meet our needs and will demo / discuss next steps with @davidkelliott and the rest of the team.

Success fully demonstrated. Will raise issues to move this along into production use


[admin] Superuser can't delete a regular user #110

It is but normal that a superuser should able to
delete any object including organizationuser.
Thus, I fixed the issue by updating the
has_delete_permision of organizationuser to
return True for superusers
Fixes #110

Coverage increased (+0.01%) to 97.037% when pulling a615f0cdeba4f05848598ecaa3de91130d578dbb on NoumbissiValere:superuser_delete_orguser into 7cf38c11ec51f40a0a28fab4bbafc95bedf951be on openwisp:master.

@okraits I think this fixes the issue


Upgrade mongodb driver version

Upgrade mongodb driver version to <IP_ADDRESS>

@arnenissen Please create Jira ticket for this version upgrade and add the JIRA ID in your commit message as well.


Fix home dir substitution

See the discussions in https://github.com/Bash-it/bash-it/commit/953e422bed2f9b0ba01ec998fe619e523819551f#commitcomment-58148656 . Tested with bash 5.1 and  bash 3.2

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] If my change requires a change to the documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
[x] I have added tests to cover my changes, and all the new and existing tests pass.

Is there a reason we're not using \w?

Is there a reason we're not using \w?

\w of course !

The quotes are necessary to avoid word splitting and will be rejected by the automated checks

Soo the quotes do not appear to be necessary in the context on an assignment:
test.sh
#!/usr/bin/env bash

# assign with no quotes
wd=${PWD/#$HOME/\~}
echo "${wd}"

# direct usage with no quotes
echo ${PWD/#$HOME/\~}

shellcheck
$ shellcheck test.sh

In test.sh line 8:
echo ${PWD/#$HOME/\~}
     ^--------------^ SC2086: Double quote to prevent globbing and word splitting.

Notice that the assignment did not generate a warning.

/Side Note : @gaelicWizard  I've been meaning to tell you that I came across you in the wild:

http://hints.macworld.com/article.php?story=20070206110939423

I was researching an issue for my work laptop (i.e not related to bash-it at all) and found your posts there.
I just thought it was cool and wanted to mention it ...

rejected by the automated checks
Can you elaborate?

The Bash It repo is set up to run shellcheck on everything, and it's fairly pedantic about quoting variables (and can be made more pedantic, optionally), and I love it. I first began contributing code to Bash It because it wouldn't run on my system with a space in $BASH_IT, so it seems I may be the unofficial quoter-in-chief for the time being! 😃


Use with static (unrolled) RNN?

Hi guys, thanks for your contribution. I wanted to give some feedback and request that you add a static (unrolled) RNN to your test suite. If/when I get a chance to spend more time on this, I'm happy to contribute this myself.
I tried using your code with a 2-layer LSTM RNN using dynamic_rnn and hit the same issue as here: https://github.com/openai/gradient-checkpointing/issues/9
I converted my model to use static_rnn. This removes the while loop by statically unrolling for a fixed sequence length. At this point, your code was unable to automatically find articulation points. So, I tried adding manual checkpoints in a few intuitive places (at output of each layer, or at every unrolled loop iteration, or at every k unrolled loop iterations). In all cases, the memory usage was still higher than the baseline. I investigated the modified backprop graph. It seemed to be doing a lot of redundant computation and not working as described in your writing. I suspect I wasn't checkpointing correctly. A working static RNN test case would be a helpful reference.

@yaroslavvb have the same error with RNN


Add comet

Closes #99.

Currently CI is failing and one potential reason to that is not disabling the multiprocessing while scoring. There is a bug in the comet implementation, see this issue.

Any ideas for CI failing @Sophylax ? Some notes below:

Test preserves around 4.5 GB memory, this is a similar case with Prism
The PR addressing bug fix for the issue on unbabel/COMET is merged. Still with num_workers=0 it is failing.

Any similar situations experienced with your tests @ricardorei ?

Yes I had some problems with testing COMET using CI. Have you tried running the test with a smaller model?
For example [wmt21-cometinho-da](https://github.com/Unbabel/COMET/blob/master/METRICS.md)?

which version of COMET are you currently using?

Nice! I am happy to help, tag me if you need something else.
I'll do that. Actually, I need to update all the documentation, it is extremely outdated...

Thanks @ricardorei, appreciate it. Thanks for the comment about the repo as well, yes one of the milestone is that supplying a diverse set of metrics to people to make the evaluation in NLP more properly :).


Update CodeEditTextView to 0.6.2

Description
Update CodeEditTextView to 0.6.2
Related Issues
n/a
Checklist

[x] I read and understood the contributing guide as well as the code of conduct
[x] The issues this PR addresses are related to each other
[x] My changes generate no new warnings
[x] My code builds and runs on my machine
[x] My changes are all related to the related issue above
[x] I documented my code

Screenshots
n/a

Since we're not using the Preference dependency, would here be a good place to remove it?

Thanks for the suggestion @luah5. It is now removed.

All checks pass. Merging now because the current code in main is broken without this.


Added links to examples in readme.

Added links to usage examples. This should fix issue #3.

Thank you for adding!


SpanOption DisableQuery

Hi, this PR attempts to cover the DisableQuery functionality, this time as opposed #25, it makes only the attribute not set.
It tries to cover the expected functionality by #22

Hi @XSAM this time I am trying to disable the query itself. I wonder if would make sense to set the value with something like "-" instead of not sending it. wdyt ?

Hi @XSAM this time I am trying to disable the query itself. I wonder if would make sense to set the value with something like "-" instead of not sending it. wdyt ?

I think not sending the value is make sense to me. You can check the example value from the specification.


Failed to publish image with new tag to Sonatype Nexus3 v3.29.2

Environment:

Jib version: 2.7.1
Build tool: Maven
OS: Alpine Linux in container

Description of the issue:
We are building Docker images and publish them to the Nexus Docker Registry as a part of CI process.
Registry is configured with disabled redeployment, and our images are uniquely tagged with pipeline id, to avoid confusion with image/app versions.
But, even with unique image tag I'm getting the following error:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:2.7.1:build (default-cli) on project adhocer-taxon-desc-back: Tried to push image manifest for coe-dcr.vimpelcom.global/test-maven-project:1.1.1_275 but failed because: other: blob upload invalid | If this is a bug, please file an issue at https://github.com/GoogleContainerTools/jib/issues/new: 400 Bad Request
[ERROR] PUT https://coe-dcr.vimpelcom.global/v2/test-maven-project/manifests/1.1.1_275
[ERROR] {"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid","detail":"Repository does not allow updating assets: coe-docker"}]}

Expected behavior:
Image tagged and published in Nexus Docker Registry
Steps to reproduce:

Configure projects pom.xml with approprieate jib. plugin configuration
Setup Nexus Docker Registry with disabled re-deployment
Try to build/publish image

jib-maven-plugin Configuration:
            <plugin>
              <groupId>com.google.cloud.tools</groupId>
              <artifactId>jib-maven-plugin</artifactId>
              <version>2.7.1</version>
              <configuration>
                <from>
                  <image>coe-dcr.vimpelcom.global/openjdk:8u111-jdk-alpine</image>
                </from>
                <to>
                  <image>coe-dcr.vimpelcom.global/test-maven-project:${env.VERSION}</image>
                  <auth>
                    <username>${env.NEXUS_MAVEN_USER}</username>
                    <password>${env.NEXUS_MAVEN_PASSWORD}</password>
                  </auth>
                </to>
                <appRoot>/app></appRoot>
                <format>OCI</format>
                <container>
                  <environment>
                    <PROJECT_DIR>/app</PROJECT_DIR>
                    <MAIN_CLASS>ru.beeline.mircoservices.adhocer_taxon_desc.DimTaxonDescApplication</MAIN_CLASS>
                  </environment>
                  <jvmFlags>
                    <jvmFlag>$JVM_FLAGS</jvmFlag>
                  </jvmFlags>
                  <args>
                    <arg>$APP_FLAGS</arg>
                  </args>
                </container>
              </configuration>
            </plugin>

Note: kaniko is working perfectly in the same setup

Hi @echupriyanov,
We learned in the past that disabling redeployment in Sonatype Nexus prevents updating any assets, including existing images (technically speaking, "image manifests", which are simple JSON files). Using a fresh new tag doesn't matter, because the asset in question is the manifest.
What's happening in your case is that, because of Jib's strong reproducibility, consecutive Jib builds are generating the exact same manifest JSON (i.e., the image SHA digest doesn't change), and pushing the manifest fails because Nexus prevents updating existing manifests (images). Note that the only way to add a new tag with the Docker Registry API is to push a new manifest. Kaniko doesn't hit this issue because it always generates a new, different image whenever it builds an image.
For example, if I push the same image with different tags using the Docker CLI to Nexus with redeployment disabled, it fails with the same error message.
$ docker tag busybox localhost:5443/busybox:mytag1
$ docker tag busybox localhost:5443/busybox:mytag2
$ docker push localhost:5443/busybox:mytag1
The push refers to repository [localhost:5443/busybox]
6b245f040973: Pushed
mytag1: digest: sha256:56853b711255f4a0bc7c44d2158167f03f64ef75a22a0249a9fae4703ec10f61 size: 527
$ docker push localhost:5443/busybox:mytag2
The push refers to repository [localhost:5443/busybox]
6b245f040973: Layer already exists
blob upload invalid: blob upload invalid

From my perspective, it's arguable that disabling redeployment should also prevent adding a new tag for an existing image. I don't know if Nexus intended it, or it's just what it is due to the server locking down every existing assent.
In any case, Jib is working correctly as intended. I'll close the issue.
There are some workarounds you can think of, depending on your situation.

Just don't push if you are not building a different image. (-Djib.skipExistingImages may be useful.]
Always create a different image (manifest). For example, using USE_CURRENT_TIMESTAMP. Of course, this affects reproducibility.

Great thanks for clarification! Will try suggested workarounds


Global URL doesn't comply with web standards since 0.25.1, when using happy-dom

Describe the bug
Mock Service Worker (msw) no longer handles requests after upgrading from Vitest 0.25.0 to 0.25.1 when using happy-dom or jsdom +<EMAIL_ADDRESS>(the version included in happy-dom).
Reproduction

Create a vitest test including a mock service worker.

import { setupServer } from 'msw/node';
import { rest } from 'msw';

const server = setupServer(
  rest.get('http://foo.com/', async (req, res, ctx) => {
    console.log('intercepted request');
    return res(ctx.status(200));
  }),
);

describe('foo', () => {
  beforeAll(() => server.listen());

  it('makes a request to the server', async () => {
    await fetch('http://foo.com/')
  })
});

Install vitest 0.25.0 and any version of happy-dom. (Or use jsdom +<EMAIL_ADDRESS>adding import { fetch } from 'node-fetch' to the test script.)

Run vitest --environment happy-dom (or jsdom) and note that it prints intercepted request to the console.

Upgrade to vitest 0.25.1.

Re-run vitest and note that it prints this:

[MSW] Warning: captured a request without a matching request handler:

  • GET ///

It no longer works.
UPDATE: Actually it works with 0.25.0. It is 0.25.1 that causes the error. I believe the problematic commit is 922e525244d1f69ea3e8f609e88e2ba503a069d4.
UPDATE 2: If you remove 'URL' from LIVING_KEYS in packages/vitest/src/integrations/env/jsdom-keys.ts then it works.
System Info
System:
    OS: Linux 6.0 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 16.67 GB / 23.40 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.18.0 - ~/.nvm/versions/node/v16.18.0/bin/node
    Yarn: 1.22.19 - ~/.local/share/pnpm/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v16.18.0/bin/npm
  Browsers:
    Chromium: 107.0.5304.110

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[x] The provided reproduction is a minimal reproducible example of the bug.

fetch is not defined in node 16. Please, provide correct reproduction

@sheremet-va Updated the reproduction steps. One can reproduce by either using jsdom +<EMAIL_ADDRESS>or by using happy-dom (which includes node-fetch@2.x.x).

Actually it works with 0.25.0. It is 0.25.1 that causes the error. I believe the problematic commit is 922e525244d1f69ea3e8f609e88e2ba503a069d4. The adjustment to integrations/env/utils.ts perhaps?

If you remove 'URL' from LIVING_KEYS in packages/vitest/src/integrations/env/jsdom-keys.ts then it works.

But why JSDOM URL cases an error with MSW? 🤔

Interesting 🤔 Node URL and happy-dom URL return different objects 🤔

Ok, I found it. JSDom/Happy-dom has a bug when parsing new URL, it seems.

I checked in Safari, and it does parse like NodeURL:

JSDOM also returns correct object.

Not sure about msw, but I could reproduce in a nextjs app / react as well:
https://github.com/vitest-dev/vitest/issues/2331
Regarding happy-dom, I'm a bit confused cause in my case it works with 0.25.0, but from vitest 0.25.1 seems that sometimes the URL constructor receive an URLrather than a string

Regarding happy-dom, I'm a bit confused cause in my case it works with 0.25.0, but from vitest 0.25.1 seems that sometimes the URL constructor receive an URLrather than a string

Before 0.25.1 Vitest had a bug, where it used Node's URL instead of happy-dom's URL, when happy-dom was used as environment. Now the bug is fixed, and happy-dom fails, because its URL implementation is wrong.

this has been fixed by upgrading happy-dom to the latest version such as 8.0


[Task]: Host google fonts in repo

If we fetch google fonts from google URLs, we should download the font in the repository directly to avoid issues.
https://twitter.com/jwildeboer/status/1562077629284585474?t=h7IDOqgQnWkTFWRGooxwyw&s=19

Looks good

I can see a font in the blog, the branch where we store the iota changes is feat/iota-blog


Raid History Enhancements

Past raids are currently accessible from the realm details history panel and empire page, but an expanded individual raid view (with URL accessibility) should be implemented

[ ] Add a string of sayings e.g "The Sacking of Shomlom" to name each raid (might need to assign this on Indexer or on-chain so names don't change each time viewed)
[ ]  Show initial army compositions, and units/vitality lost by each side
[ ]  Links for social sharing

assigning to @RedBeardEth

closing this as stack has changed


Add search method that takes into account the current feature ranking

e.g.  "Filter numerator to features with an x-rank greater than", and then the the user types in a number for a minimum x threshold.
Would make analyzing huge datasets a ton easier, at least until we get #83 working.

Something I've been thinking about is combining this with #141 (and this would fit really well with #140). This would let the user select a search type from something like greater than or less than, and then the selected feature metadata field would be interpreted as numeric (non-numeric values would just be ignored in the search, I guess? or maybe colored a special classification color but idk).
This solution would work pretty much out of the box with fields like Confidence. For making it work with the currently selected ranking we'd just need to expose qurro_x (or whatever it's named) in the feature metadata selects, and it'll work then (only caveat is that the user can re-sort the rank plot and the feature classifications on the rank plot won't change -- shouldn't matter though as long as we make it clear this is expected behavior, and user should be able to just redo this by clicking "Regenerate plots" again after resorting rank plot).
We might want to change the name of qurro_x to make it clearer that this refers to the current ranking. Maybe qurro_current_ranking, which would match up with the tooltip title for qurro_x? Or we could just use Current Ranking, and have that refer internally to qurro_x (this would mean that the feature metadata can't contain any columns called Current Ranking, though).
In any case, this should be doable.

I guess we can close this now that #141 and #189 are done / en route to being merged in.


Fixed image resolution for familiar references

Fixes #31

Hey @crashvb, what do you think about this change. :)

Sorry for the delay; changed jobs so my timing is a little off. LGTM at first glace, but I'd like to run it through some downstream tests on the RH side to make sure that behavior is limited to only DH.

Hey @crashvb, gentle reminder to see if you manage to test these changes. :)

@kyatite Can you test this downstream, please?

Superseded; see comments in #31


Wrong type declaration

Wrong type declaration of FilePond.addfFile options argument when add file without load.
addFile: (source: ActualFileObject | Blob | string, options?: { index: number }) => Promise;
Options argument same as this comment.

Feel free to submit a PR

#528


gc

Cluster information
Cluster version: 3.1.0
Cluster size: 8 servers, 128g memory per server, 4 nodes per server, 32 nodes in total
Problems encountered:
Using regexp_replace to replace '\r\n 'in the string field of the table, the size of the table is 200g, with 400 million pieces of data, the task will run for a period of time and there will be gc exception (at this time only the current task is executing), how can I configure to solve this problem, or can you help me provide better advice to deal with this problem

16G per node
the table have 32 shards，every node has one

Please also answer the second question.


fix(search): show no-results div when no results

Had been bugged such that no-search-results recovery suggestions would never show.
Change to show when there's no hope of results.
After: no results:

After: some results

Glad you think so, @Doug-Reed ! I do think it'll help some. At the least maybe it will reduce user inhibitions to hit that "Give feedback" link and tell us if we're over-estimating how good this user experience is.


fix: Fixed indentation in CI workflow

:tada: This PR is included in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat!: generate themes from catppuccin/iterm

#1 is no longer needed with this PR, I don't think we need to include that key in the first place. This PR adds a new build system that uses a Swift script to convert each flavor from our iTerm port into a Terminal.app theme file. I took https://github.com/lysyi3m/macos-terminal-themes/blob/master/tools/iterm2terminal.swift as a base and modernized it quite a bit with what little I know about Swift. Unfortunately I don't think we can use easier tools like Deno or Whiskers for this port due to the cursed nature of the .terminal file format - the data for each color is a representation of Apple's NSColor, encoded with NSKeyedArchiver.

We should probably set up https://github.com/sgoudham/update-git-submodules here as well on latest commit mode.

Sure, that works too :)


Feature Support insert only transactional hive table on be side.

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Error opening swagger/ui with dotnet6 runtime 4 azure function

Describe the issue
When I open the swagger ui page locally aswell as in a deployed environment i get the following error in my console:

Even though i have my swagger definitions defined:

To Reproduce
Steps to reproduce the behavior:

Run functionapp
Open swagger/ui page
error:

Expected behavior
Swagger ui appears
Screenshots

Running in verbose mode gives me the following errors:
[2021-12-02T14:43:59.349Z] Host lock lease acquired by instance ID '0000000000000000000000000B7F9A3E'.
[2021-12-02T14:44:00.865Z] Executing HTTP request: {
[2021-12-02T14:44:00.865Z]   requestId: "eb652e01-896b-48fb-b62a-a80890da8801",
[2021-12-02T14:44:00.865Z]   method: "GET",
[2021-12-02T14:44:00.865Z]   userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36",
[2021-12-02T14:44:00.865Z]   uri: "/api/swagger/ui"
[2021-12-02T14:44:00.865Z] }
[2021-12-02T14:44:01.023Z] Executing 'Functions.RenderSwaggerUI' (Reason='This function was programmatically called via the host APIs.', Id=6ffffe67-10f6-469e-a33b-5b3b218b7e8c)
[2021-12-02T14:44:01.041Z] SwaggerUI page was requested.
[2021-12-02T14:44:01.150Z] Executed 'Functions.RenderSwaggerUI' (Succeeded, Id=6ffffe67-10f6-469e-a33b-5b3b218b7e8c, Duration=147ms)
[2021-12-02T14:44:01.376Z] Executed HTTP request: {
[2021-12-02T14:44:01.376Z]   requestId: "eb652e01-896b-48fb-b62a-a80890da8801",
[2021-12-02T14:44:01.376Z]   identities: "",
[2021-12-02T14:44:01.376Z]   status: "200",
[2021-12-02T14:44:01.376Z]   duration: "507"
[2021-12-02T14:44:01.376Z] }
[2021-12-02T14:44:01.628Z] Executing HTTP request: {
[2021-12-02T14:44:01.629Z]   requestId: "306895fb-20c0-466c-878a-219b4bf0d189",
[2021-12-02T14:44:01.629Z]   method: "GET",
[2021-12-02T14:44:01.629Z]   userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36",
[2021-12-02T14:44:01.629Z]   uri: "/api/swagger.json"
[2021-12-02T14:44:01.629Z] }
[2021-12-02T14:44:01.641Z] Executing 'Functions.RenderSwaggerDocument' (Reason='This function was programmatically called via the host APIs.', Id=d574257f-7cc6-49e1-ab3e-aaa75a277f69)
[2021-12-02T14:44:01.644Z] swagger.json was requested.
[2021-12-02T14:44:01.704Z] Scheme MUST be provided
[2021-12-02T14:44:01.706Z] Executed 'Functions.RenderSwaggerDocument' (Succeeded, Id=d574257f-7cc6-49e1-ab3e-aaa75a277f69, Duration=75ms)
[2021-12-02T14:44:01.706Z] Executed HTTP request: {
[2021-12-02T14:44:01.707Z]   requestId: "306895fb-20c0-466c-878a-219b4bf0d189",
[2021-12-02T14:44:01.707Z]   identities: "",
[2021-12-02T14:44:01.707Z]   status: "500",
[2021-12-02T14:44:01.707Z]   duration: "78"
[2021-12-02T14:44:01.707Z] }

Environment

OS: MacOS
Chrome
11.6.1

Additional context
Add any other context about the problem here.

Closing issue as it is working locally now.


The plugin is not working properly

I had my PyMOL with student license. After the installation of the plugin, I can't get the visualization of the molecule I want but instead something like this:

My friend also used the same input file with exactly the same procedure in his computer and it worked:

I also had him checked all of my procedure and nothing was wrong.
Is the student license a problem, does it limit what I can do?

Hello @andamthe, could you please provide your POSCAR/CONTCAR file and OUTCAR file for that system? I can take a look into this.
You may upload files by dropping them into the text section.

Hello @andamthe, could you please provide your POSCAR/CONTCAR file and OUTCAR file for that system? I can take a look into this.
You may upload files by dropping them into the text section.

OUTCAR.txt
I converted it to txt here. My friend use this one and it worked properly in his computer. He does not have student license as I have so I am suspecting the limit due to the student license

Hello @andamthe, could you please provide your POSCAR/CONTCAR file and OUTCAR file for that system? I can take a look into this.
You may upload files by dropping them into the text section.

OUTCAR.txt
I converted it to txt here. My friend use this one and it worked properly in his computer. He does not have student license as I have so I am suspecting the limit due to the student license

Hello @andamthe, thank you for the OUTCAR file. I have repeated the error on Windows 10 but did not have the same issue on Mac OS.
I have now modified the code and it should be fixed now. You may download the latest code and reinstall to pymol. Please let me know if the problem persists. Thanks.

Hello @andamthe, could you please provide your POSCAR/CONTCAR file and OUTCAR file for that system? I can take a look into this.
You may upload files by dropping them into the text section.

OUTCAR.txt
I converted it to txt here. My friend use this one and it worked properly in his computer. He does not have student license as I have so I am suspecting the limit due to the student license

Hello @andamthe, thank you for the OUTCAR file. I have reproduced the error on Windows 10 but did not have the same issue on Mac OS.
I have now modified the code and it should be fixed now. You may download the latest code and reinstall to pymol. Please let me know if the problem persists. Thanks.

I have installed the latest code but the problem persists. Could it be due to the limitation of the license?
What should I do?

Hi @andamthe, I checked again and did got the same issue with Windows pymol. Then, I modified the code and it works on my windows 10 pymol-2.5.0 now.

I feel there is some inconsistency in pymol at different operating systems. Is your friend also using windows pymol or a different version of pymol from yours?

It is working for me now. Thank you very much.
Best regards.

It is working for me now. Thank you very much.
Best regards.

Hi @andamthe, I checked again and did got the same issue with Windows pymol. Then, I modified the code and it works on my windows 10 pymol-2.5.0 now.

I feel there is some inconsistency in pymol at different operating systems. Is your friend also using windows pymol or a different version of pymol from yours? (The type of license should have no impact on the use of pyvibms.)

My friend also use Windows 10 and he is using the version with 1 month of free trial

Hi @andamthe, I'm glad to hear that this problem is now solved for you. Could you please check the version of the pymol you and your friend are using by checking the "About PyMOL"? The version number could be 2.5.0 or else.

Hi @andamthe, thank you for the information. This could be helpful and I can contact the developers of pymol to report this issue in different versions of pymol.


Auto pin the repositories which a user has pinned on their profile

The original feature can't be done easily or properly as there is no API to get the pinned repos.
Instead, it would be useful to add the ability to sort by the last time that the repositories were updated.