[Bug] Can't copy paste from Excel/Access VBA code window to Notepads

Describe the bug
When trying to copy some code from a VBA (Microsoft Visual Basic for Application) project in Excel or Access, I found that I'm not able to paste it directly to Notepads. The same works for the normal Notepad, so I don't understand where the issue is.
To Reproduce
open Microsoft Visual Basic for Application window from an Excel or Access file. Create a new module, write some code (or start from the code you already implemented), copy a portion of the code and paste it on Notepads.
Expected behavior
The code should be pasted, but that doesn't happen.
Desktop (please complete the following information):

OS: Windows 10 Home 19042.906
Version  <IP_ADDRESS>

Known issue, it has something to do with Windows clipboard.

Just a small update, I tried with other notepads as well (Notepad++, another "Notepad" from windows store, Editpad lite) and none of them is having the same issue.


feat(spanner): add processing_units to Instance resource

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/c5b0af2b-a60a-4a99-ac72-8aaa71f68655/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

PiperOrigin-RevId: 378758342
Source-Link: https://github.com/googleapis/googleapis/commit/d8698715e4f5b7c45505dadd679255987c260180

@larkee just waiting on https://github.com/googleapis/synthtool/pull/1138 to land so some post-processing will run. It will clean up the diff here considerably.

@dwsupplee Can we merge this PR?


Make left pane shrinkable and render latest images below latest posts on mobile breakpoints

Fixes issue #1
https://github.com/syrno9/HikariLynx/assets/3119646/3c97dc6e-ffef-423f-877d-ca3516a6e4e2

Please refer to https://github.com/Transfusion/LynxChan/commit/e47ee4af5d943e1eb55391d481c64c337999d991 for the backend changes needed. src/be/data/defaultPages.json and src/be/engine/domManipulator/static.js need to be replaced.


distrho: 2020-07-14 -> 2021-03-15

Motivation for this change
Things done

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

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

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

Result of nixpkgs-review pr 118928 at f55466d7 run on x86_64-linux 1

1 package built successfully:

distrho

3 suggestions:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/audio/distrho/default.nix:93:5:
   |
93 |     license = with licenses; [ gpl2 gpl3 gpl2Plus lgpl3 mit ];
   |     ^

warning: unclear-gpl
lgpl3 is a deprecated license, please check if project uses lgpl3Plus or lgpl3Only and change meta.license accordingly.
Near pkgs/applications/audio/distrho/default.nix:93:5:
   |
93 |     license = with licenses; [ gpl2 gpl3 gpl2Plus lgpl3 mit ];
   |     ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/applications/audio/distrho/default.nix:93:5:
   |
93 |     license = with licenses; [ gpl2 gpl3 gpl2Plus lgpl3 mit ];
   |     ^


Out of Memory errors appear to be ignoring custom configuration

Description
I have a single Xcode codebase which compiles to many variant apps. Because I'm more interested in seeing errors as a whole rather than per app, they all report to the same Bugsnag project. I override the configuration's appVersion and bundleVersion to my custom codebase version, which is based on tagged commits, while reporting the app's actual version and build number using custom metadata entries:
let config = BugsnagConfiguration.loadConfig()
config.appVersion = codebaseVersion
config.bundleVersion = codebaseVersion

config.addMetadata(Bundle.main.infoDictionary!["CFBundleVersion"] as! String, key: "appBuild", section: "SingleApp")
config.addMetadata(Bundle.main.infoDictionary!["CFBundleShortVersionString"] as! String, key: "appVersion", section: "SingleApp")

Bugsnag.start(with: config)

Issue
Regular errors are coming through as I expect, but out of memory errors appear to be ignoring the configuration completely. They don't have my overridden app and bundle version keys, and they don't include the metadata. These errors are also causing problems in the Bugsnag dashboard because it is generating releases which don't match my codebase versions (but rather the specific app versions, which vary widely in version numbers).
Environment
Library versions:

Bugsnag 6.0.0 (most variant apps are using this version, a few newer ones use newer versions of Bugsnag though I've not seen any OOM errors produced by them, probably due to low volume)
CocoaPods 1.9.3
iOS/tvOS/macOS version(s): 10+
debug mode or production?: Production

@Aquilosion thanks for opening the issue.  Currently Out of Memory crash handling only supports a basic pre-determined dataset.  However, we do have a project open to review options for expanding that dataset to allow for the metadata, which would cover your example.  We'll keep this issue thread posted with any updates.


Computing on an Array and a literal has inconsistent behavior?

Description
The following compute is computed on init "_computeArray(orgArray.splices)" but it doesn't seem to be possible (?) to know from _computeArray that orgArray is what was passed in (since the computed function is called with splices) - I have tried using something like this "_computeArray(orgArray.splices, 'orgArray')" - but this has the effect that the computed is not called on init (even though orgArray has 2 values).
Live Demo
http://plnkr.co/edit/OMKjXEp67dnRhWDeYY6T?p=preview
(If the push is uncommented in attached than it computes correctly, or if the second variable is removed from the computed)
Expected Results
For the computation to occur on init as it does with only the splices of the original array for an argument.
Actual Results
Value is not computed until the original array is modified.
Browsers Affected

[X] Chrome
[X] Firefox

The .splices path doesn't notify when the array itself changes, only when it's spliced. So in most cases you're better off using the wildcard, orgArray.* instead: https://www.polymer-project.org/1.0/docs/devguide/observers#deep-observation
For a wildcard observer, you get a change record argument that includes a base property—that will be the array you're observing. (In the case of a .splices change record, you can look at indexSplices.object).
So you can simplify this to:
properties: {
    ...
  computedArray: {
    type: Array,
    computed: "_computedArray(orgArray.*)"
   },
},
_computedArray: function(_) {
  return _.base.map((item) => {
    return item + 's'
  })
},

Here it is running:
http://plnkr.co/edit/umP8AMvGyM4zx6SNa38r?p=preview

@arthurevans - Thanks for the reply - that's not really what the docs suggest (maybe they could be clarified?):

Array mutation paths

When used as the last segment in a path, splices represents any array mutations to the identified array (additions or deletions). For example, if users is an array, the path users.splices identifies any additions to or deletions from the array.

also I'm not really sure how your answer explains why  "_computeArray(orgArray.splices)" computes initially but  "_computeArray(orgArray.splices, 'orgArray')" does not - what's special about the later as opposed to the former?

Hm. Do you mean it could be clearer here that .splices doesn't notify when you replace the whole array? I agree, the next paragraph talks about limitations but omits this important note.
Computed properties and complex observers aren't actually supposed to support literals at all. According to the docs, literals are only supported on computed bindings. So the fact that it does anything is a little unexpected. A simpler approach would simply be to pass the array directly instead of having he indirection and the this.get call:
'_computeArray(orgArray.splices, orgArray)'
(Or, as I said, use changeRecord.base.)
There is an issue elsewhere with a multi-property observer with a .splices path not firing when a single-property observer with .splices does. The inconsistency you're seeing may be related:     https://github.com/Polymer/polymer/issues/3878

Hm. Do you mean it could be clearer here that .splices doesn't notify when you replace the whole array? I agree, the next paragraph talks about limitations but omits this important note.

Yes, that would be good (unrelated to the bug filing though). Also not that splices is notified with undefined when the array is initialized when it is a single argument to the computed.

Computed properties and complex observers aren't actually supposed to support literals at all. According to the docs, literals are only supported on computed bindings. So the fact that it does anything is a little unexpected. A simpler approach would simply be to pass the array directly instead of having he indirection and the this.get call:
I guess it's an undefined detail that literals do work? That said I very much think it would be good if they were, since that allows one to write generic methods in a behavior which can be re-used (or otherwise to have every computed splice / changes to pass in the base property name being modified).

There is an issue elsewhere with a multi-property observer with a .splices path not firing when a single-property observer with .splices does. The inconsistency you're seeing may be related: #3878

I can't make much sense of the bug report, but yes that would be the correct summary of this issue. Particularly neither _computedArray(orgArray.splices, orgArray.*) or _computedArray(orgArray.splices, 'literal') will fire when initialized although as I mentioned the singular _computedArray(orgArray.splices) does fire.  I suspect this might be related to the multi-property computed requirement that both properties be defined ? Where as .splices is not defined until it is pushed to.
I suppose the solution is to not use .splices at all (since it's current implementation is pretty useless) but to use orgArray.* always. This does have a disadvantage though, that in fact .* on an array is triggered twice for push action (once on .splices and once on .length) so one must guard against performing (e.g. if using an observer) the same action twice for a single event, which is again an implementation detail but perhaps not so nice to expose users to.

It has been a while and this area of docs has significantly improved: https://www.polymer-project.org/2.0/docs/devguide/observers#array-observation including the following note:

Polymer only calls the array mutation observer when the array items change, not for changes to the top-level array

Therefore I am closing this issue. @pik feel free to reopen if you are still running into issues!


Fixes #43: error when using SVGs with no viewBox

Fixes #43

I've updated the PR to not add a viewBox attribute if there isn't one in the source SVG file


[FEATURE] Add integration tests for json

As shown in #1281, we could produce json by parse and typecheck from all the tests files that we have in src/tla. @shonfeder do you there is a simple solution that does not require us to copy & paste tests for all the files?

On a second thought, @Kukovec will first try to do it directly with ScalaCheck. This looks like a perfect case for PBT.

This is mainly done with Scalacheck in #1291 now. However, we have to add a few integration tests, just to make sure that things do not break somewhere else.

I’d just suggest not actually looking at the content of the json in the integration tests. You can check that the expected file is created, or that you can produce and then read in the file, but I wouldn’t recommend against inspecting the json itself. That amounts to testing the json serialization lib in the integration tests, and m might be brittle and not deliver much value.

Yes, I agree that we should not look inside just do parse-parse or typecheck-parse.

We have unit tests, ScalaCheck tests, and a few integration tests. So I am closing this issue.


Vanilla resteasy-jsonb application doesn't start

Describe the bug
Apprently this extension has hidden dependencies to jackson, which causes app to crash while booting up if only quarkus-resteasy-jsonb is present.
To Reproduce
mvn io.quarkus:quarkus-maven-plugin:1.13.2.Final:create \
    -DprojectGroupId=problem \
    -DprojectArtifactId=quarkus-resteasy-problem-playground \
    -DclassName="problem.HelloResource" \
    -Dpath="/hello" \
    -Dextensions="resteasy,resteasy-jsonb"
cd quarkus-resteasy-problem-playground
// add quarkus-resteasy-problem:0.9.5 to pom.xml
./mvnw clean quarkus:dev

App will not start properly, error stack trace in the logs:
Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.ObjectMapper

Expected behavior
App should start without errors.

There are actually multiple problems related to that:

build-time detection for some classes give false-positives but ClassNotFoundExceptions are thrown in the runtime (com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException)
lack of tests for bare-bones application with minimal dependencies


Add support for overlaying stacks on top of each other

Uses the layer support in Cornerstone 0.12.0. Still a work-in-progress.
Demo:
https://rawgit.com/swederik/cornerstoneTools/stackOverlays/examples/layeredImageStacks/index.html

Coverage increased (+0.03%) to 3.922% when pulling 3c5896db014bf0831ad6751e32598ccaed9d4c39 on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage increased (+0.03%) to 3.917% when pulling efea678cb1a1ccca6d390506cd4a21822b9e91be on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage increased (+0.03%) to 3.917% when pulling c5e9cdcbe12171ae283b8086bbbb86c73fd79ca8 on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage increased (+0.0003%) to 3.889% when pulling ce8e38a6fba7d96d13e6764d51a0513a8c36b774 on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage decreased (-0.006%) to 3.883% when pulling 639b34b26cc6dda20e41c607f6a472e99391eb35 on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage decreased (-0.006%) to 3.883% when pulling 0f41367e2c28e955b5c1b37a549a4d27de0e8461 on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.

Coverage decreased (-0.007%) to 3.882% when pulling fab1e3d4179fddd07653a20d395781e301aafb4d on swederik:stackOverlays into 61e251a85ea539ae3ec027b654f35ff8363901e1 on chafey:master.


Better document how to add logos

As a thesis author, I want to be informed about the option of adding the logo images to my thesis, in order to not miss this feature.
I personally was not sure about how to add the logo images to my thesis after the Studienreferat told me that I still need to add them (until Toni told me that the swa template already has some logic for them and I just need to put the files inside it), and I know of a student who even handed in the thesis without ever adding the logo images. The intended process here (e.g. where to get the images from and where to put them, so that they are incorporated automatically) should either be reworked, or at least communicated very actively to the author.

If you're on the latest commit, this should be fixed…

Oh okay, then I guess it is just the old version that I used...


other cuda version

Hello,
i have another cuda(12.1) and tensorrt version, how could i generate a specific .trt file?

We will release the code soon.

Hello, i have another cuda(12.1) and tensorrt version, how could i generate a specific .trt file?

Have you solved it yet


Add automated login events tests to php

Description
Add automated login events tests to php
Motivation

Workflow

⚠⚠ Create your PR as draft
Follow the style guidelines of this project (See how to easily lint the code)
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Once your PR is reviewed, you can merge it! :heart:
Reviewer checklist

[ ] If this PR modifies anything else than strictly the default scenario, then add the run-all-scenarios label (more info).
[ ] CI is green

[ ] If not, failing jobs are not related to this change (and you are 100% sure about this statement)

if any of build-some-image label is present

is the image labl have been updated ?
just before merging, locally build and push the image to hub.docker.com

Sorted @cbeauchesne


UX: Classes to investigate if should go to ADMINISTER

CTR-793

The reason for every change can be read in every commit message


Merge ARIA roles and properties into element attributes

This is a follow on to #67. Fixes #7.

Now that #67 has been merged, I believe this needs to be rebased on main?


Provide a standardised way to apply defaults to an extension

Expected Behavior
Theoretical usage with the help of Gradle:
// HasDefaults is provided by Gradle
interface MyPluginExtension : HasDefaults {
    val enabled: Property<Boolean>

    @get:Nested
    val remote: MyNestedExtension // instrumented by Gradle to call initDefaults

    override fun initDefaults() { // called by Gradle
        enabled.convention(false)
    }
}

interface MyNestedExtension : HasDefaults {
    val url: Property<String>
    val timeoutSeconds: Property<Int>

    override fun initDefaults() { // called by Gradle
        timeoutSeconds.convention(60)
    }
}

override fun apply(project: Project) {
    val extension = project.extensions.create("myExtension", MyPluginExtension::class.java)
    // defaults are applied to extension
}

Current Behavior (optional)
I've been using the following pattern throughout dozens of extensions to apply the default values:
// Defined in a common library:
interface HasDefaults {
    fun initDefaults()
}

interface MyPluginExtension : HasDefaults {
    val enabled: Property<Boolean>

    @get:Nested
    val remote: MyNestedExtension

    override fun initDefaults() {
        enabled.convention(false)
        remote.initDefaults()
    }
}

interface MyNestedExtension : HasDefaults {
    val url: Property<String>
    val timeoutSeconds: Property<Int>

    override fun initDefaults() {
        timeoutSeconds.convention(60)
    }
}

override fun apply(project: Project) {
    val extension = project.extensions.create("myExtension", MyPluginExtension::class.java)
    extension.initDefaults()
}

Context
Some properties in a custom extension might have default values set by calling Provider.convention(...) after the extension has been created. Gradle should provide a standardised way to apply the conventions, including for arbitrarily nested extension properties.

We need more information to understand the request. Could you please provide more context about what you want to achieve?
If we receive a clear use case description, we may be able to suggest a workaround.
This issue will be closed after 7 days unless you provide more information.

The expected approach to address that problem is to apply conventions from plugin definition. This also applies for pre-compiled script plugins.
If this does not work for you, please provide more context/details to explain why.


Support for Docker 1.4

The plugin's unit tests break with Docker 1.4, so it's probable that the plugin doesn't support Docker 1.4.

Yeah, I think I can confirm that it doesn't work with 1.4
[ERROR] Failed to execute goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images (build) on project row-change-event-channel: Execution build of goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images failed: HTTP 500 Internal Server Error -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images (build) on project row-change-event-channel: Execution build of goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images failed: HTTP 500 Internal Server Error
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

Maybe for the meantime you could add a maximum supported version to the README?

Hi Jasper!
Can you tell me what kind of build-images block you have configured? This should still work.
The only real problem seems to be with the way I integration test registry integration. It shouldn't break in production environments.

I have this in my pom file:
            <plugin>
                <groupId>net.wouterdanes.docker</groupId>
                <artifactId>docker-maven-plugin</artifactId>
                <version>3.0</version>
                <executions>
                    <execution>
                        <id>build</id>
                        <goals>
                            <goal>build-images</goal>
                        </goals>
                        <configuration>
                            <images>
                                <image>
                                    <id>row_change_event_channel</id>
                                    <dockerFile>${project.basedir}/docker/Dockerfile</dockerFile>
                                    <keep>true</keep>
                                    <nameAndTag>haploid/row-change-event-channel:${project.version}</nameAndTag>
                                    <artifacts>
                                        <artifact>
                                            <file>${project.build.directory}/${project.build.finalName}.jar</file>
                                            <dest>/app</dest>
                                        </artifact>
                                        <artifact>
                                            <file>${project.build.directory}/lib</file>
                                            <dest>/app</dest>
                                        </artifact>
                                    </artifacts>
                                </image>
                            </images>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

And this in my environment variables (for boot2docker):
declare -x DOCKER_CERT_PATH="/Users/haploid/.boot2docker/certs/boot2docker-vm"
declare -x DOCKER_HOST="tcp://<IP_ADDRESS>:2376"
declare -x DOCKER_TLS_VERIFY="1"

On a mvn clean verify it fails with:
ERROR] Failed to execute goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images (build) on project row-change-event-channel: Execution build of goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images failed: HTTP 500 Internal Server Error -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images (build) on project row-change-event-channel: Execution build of goal net.wouterdanes.docker:docker-maven-plugin:3.0:build-images failed: HTTP 500 Internal Server Error
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
...

This is on docker 1.4.1.

Sorry, I should have also copied:
Caused by: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
	at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:968)
	at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:795)
	at org.glassfish.jersey.client.JerseyInvocation.access$500(JerseyInvocation.java:91)

I thought for a second that it might've been the / in the nameAndTag (people forget to escape stuff, sometimes), but it doesn't make a difference if I pick a much simpler name like "bob".

Made a bunch of fixed in 3.1.0 that should fix these server errors. Please let me know if it still breaks.


delete should not be a Java keyword

JAVA_KEYWORDS includes COMMON_KEYWORDS includes "delete", but delete is not a Java keyword: http://docs.oracle.com/javase/tutorial/java/nutsandbolts/_keywords.html
Noticed in JaCoCo output.

Unfortunately, I don't know a good way to include a list of languages for each C-like language independently without expanding the download size.


Sometimes, the request fails

First of all thanks for the great work you have done with the B1SLayer, I hope that all the time you have saved us developers to implement the service layer, will be returned to you in life.
My issue is that sometimes the calls fail me and the code below is the trace. See if you can see something, if you need more information, let me know.
   at System.Net.Http.HttpConnection.<SendAsyncCore>d__61.MoveNext()
   at System.Net.Http.HttpConnectionPool.<SendWithVersionDetectionAndRetryAsync>d__86.MoveNext()
   at System.Net.Http.DiagnosticsHandler.<SendAsyncCore>d__10.MoveNext()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Net.Http.DecompressionHandler.<SendAsync>d__16.MoveNext()
   at System.Net.Http.HttpClient.<<SendAsync>g__Core|83_0>d.MoveNext()
   at Flurl.Http.FlurlRequest.<SendAsync>d__29.MoveNext()

Hi, @qcsfb. Thank you for your kind words.
Unfortunately, the trace you provided is not enough information to help me understand the cause of the issue. Could you maybe provide a code snippet of a request using B1SLayer where you observe the issue? What's the exception you get?
If I can reproduce the issue on my end, that would be ideal.

Hi, i enabled logs in the service layer and the trace of a example (post orders)
 [proxy_http:error] [pid 24460:tid 1100] (OS 10054)Se ha forzado la interrupci�n de una conexi�n existente por el host remoto.  : [client ::1:59952] AH01102: error reading status line from remote server <IP_ADDRESS>:50002
 [proxy:error] [pid 24460:tid 1100] [client ::1:59952] AH00898: Error reading from remote server returned by /b1s/v1/CompanyService_GetCompanyInfo
 [proxy_http:error] [pid 24460:tid 1100] (OS 10054)Se ha forzado la interrupci�n de una conexi�n existente por el host remoto.  : [client ::1:60280] AH01102: error reading status line from remote server <IP_ADDRESS>:50003
 [proxy:error] [pid 24460:tid 1100] [client ::1:60280] AH00898: Error reading from remote server returned by /b1s/v1/CompanyService_GetCompanyInfo
 [proxy_http:error] [pid 24460:tid 1088] (OS 10054)Se ha forzado la interrupci�n de una conexi�n existente por el host remoto.  : [client ::1:60358] AH01102: error reading status line from remote server <IP_ADDRESS>:50010
 [proxy:error] [pid 24460:tid 1088] [client ::1:60358] AH00898: Error reading from remote server returned by /b1s/v1/CompanyService_GetCompanyInfo
 [proxy_http:error] [pid 24460:tid 1088] (OS 10054)Se ha forzado la interrupci�n de una conexi�n existente por el host remoto.  : [client <IP_ADDRESS>:55930] AH01102: error reading status line from remote server <IP_ADDRESS>:50009
 [proxy:error] [pid 24460:tid 1088] [client <IP_ADDRESS>:55930] AH00898: Error reading from remote server returned by /b1s/v1/Orders
 [proxy_http:error] [pid 24460:tid 1100] (OS 10054)Se ha forzado la interrupci�n de una conexi�n existente por el host remoto.  : [client ::1:60923] AH01102: error reading status line from remote server <IP_ADDRESS>:50002
 [proxy:error] [pid 24460:tid 1100] [client ::1:60923] AH00898: Error reading from remote server returned by /b1s/v1/CompanyService_GetCompanyInfo

I dont think if this is helpful for you.

@qcsfb, What's the .NET version you are using for your project?

Net standard 2.1

You use .NET Standard in a project type of class library, right? I mean the project of the application that compiles into an executable.
There can be problems with old .NET Framework versions where you can set the TLS version globally and it should fix this issue:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

This should be done at your application startup (not the class library project). Let me know if it helps.

To answer your first question. The structure of my project is as follows. I have a main project that is a minimal API in .net7 that uses another project (where your library is) that uses standard 2.1.

@qcsfb, from what I could investigate so far, this could be related to your client and server not agreeing on the TLS version. However, this is just one of the possibilities.
A number of factors like the .NET version or the OS configuration could be causing this, so a further investigation on your environment would be needed to nail it down to the exact cause.
You can try adding additional TLS versions to your application, overwriting any .NET or OS configuration. Add the line below in the startup (Program.cs) of your .NET 7 API project and see if it fixes the issue.
ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

In any case, I don't believe this issue is directly related to B1SLayer.

Hi, thanks for your time, you are right. I think is not related to B1SLayer because I tried with insomnia (its like postman) and sometimes i get proxy error.

I think its something wrong in my server, do have any idea what could be the reason of this problem??
Thanks a lot.

Indeed, this indicates that there is something wrong on the server side. I believe it could be related to the Service Layer installation or the HTTP server itself (Apache), but this is just speculation on my part.
I recommend you asking a question in the official SAP Community page with the "SAP Business One Extensibility" tag. Or, if you can, report an incident directly to the SAP Business One Support Team under the component "SBO-SDK-SVL".

Thank you for ur fast response. I will ask in the sap forum. I think if I fix issue in the service layer it will be fixed in B1SLayer
thanks, a lot!

@qcsfb, I'm closing this issue. Let me know if you still need assistance.


[broker][monitoring]Support push metrics data to remote endpoint

Is your enhancement request related to a problem? Please describe.
Currently, pulsar only support expose metrics data by PULL.
I believe we also need to support PUSH.
If we support expose metrics data by PUSH, it could solve some existing problems:

scraping metrics data cause high network usage
high CPU usage when calculate metrics data.
high memory usage when write metrics data

All of above problems could resolved by PUSH. We can split metric into segments, calculate and push them by segment.
Describe the solution you'd like

Support push metrics data to remote endpoint
Even better, support segment reporting metrics data

@codelipenghui  Please assign to me


release: correct release script to build docs properly

This will correctly copy the docs files as well as update docs/manifest.json.
Two problems were happening, explained in code comments...

Coverage remained the same at 100.0% when pulling 7c035d0979182be315d7aefa055c36fee5c8daa3 on stephenplusplus:master into 41f5233b9e0e8fcada3f1a97c5ff3ad75b4ca92d on GoogleCloudPlatform:master.

Big monies, no whammies!


HIRO Media: Remove unused parameters

Relevant PR on main project repo: https://github.com/prebid/Prebid.js/pull/1107

Should this be merged? The relevant change was merged and released in 0.22.2

Thanks @ronenst !


Setting tracingId in PersistenceException

What this PR does:
Setting tracingId from the backend result in PersistenceException and in turn in ErrorMessage in case of an error and when the tracing is ON
Checklist

[X] Changes manually tested
[X] Automated Tests added/updated
[X] Documentation added/updated
[X] CLA Signed: DataStax CLA

@kathirsvn This was merged today in main (v2.x), merged to v2.1 (and patched via #2857 to apply to C-4.1, dse-next). But I think there'd be some work needed for cndb persistence backend.


Add licensing information to gemspec.

This should make it easier for automated tools to find out what license is used.

Thank you for your change! The license was added to the gemspec in #79, so closing this since it's no longer needed.


The library broke on Next >=13.4.5

Hello! How are you?
First, thank you so much for your awesome library and work! It's by far my favorite to use!
Unfortunately, after I updated to Next >=13.4.5, the library stopped working when I build my website. In development, it works as usual, but when I try to build, nothing works. I tried everything I could think, without any success.
I don't know if it's still being maintained, if it is, can you look into it, please?
Again, thank you for your work! Big hug!

Hi @NRech, thank you. Could you elaborate a bit more on what is not working and what error message you got? You can create a PR with the fix and I'd be happy to assist you.

Heya! Thanks for answering!
That's the weird thing, it doesn't give any error message. At first I debugged  the line inside "getStaticProps":
	const { default: lngDict = {} } = await import(../locales/${locale}.json);
the lngDict was always an empty object, so I loaded it directly into a var and converted to a string, and it arrived ok at the "_app.js" "pageProps".
Then i just passed to the component as usual:
<I18nProvider lngDict={lngDict} locale={router.locale}>
But the "i18n.t" method doesn't return anything anymore. No error, it just returns nothing. And only during the build process. While in development, it works as it should.
I'm out of time this week, but I'll try to look more into it as soon as I can. For now, I'm using<EMAIL_ADDRESS>

Running into this issue as well! The locale copy is getting loaded fine, but rendering empty strings on pages.

Feel free to create a PR!


Dockerfile warning

Prerequisites

[X] I am using the latest version of Locust
[X] I am reporting a bug, not asking a question

Description
default Docker file at build time have warnings as shown below
if it is possible to contribute i am willing to be assigned and become contributor as well

can use below one to fix it
# Stage 1: Build web front end
FROM node:18.0.0-alpine AS webui-builder

ADD locust/webui locust/webui
ADD package.json .

# long yarn timeout necessary in certain network environments
RUN yarn webui:install --production --network-timeout 60000
RUN yarn webui:build

# Stage 2: Build Locust package
FROM python:3.11-slim AS base

FROM base AS builder
RUN apt-get update && apt-get install -y git
# there are no wheels for some packages (geventhttpclient?) for arm64/aarch64, so we need some build dependencies there
RUN if [ -n "$(arch | grep 'arm64\|aarch64')" ]; then apt install -y --no-install-recommends gcc python3-dev; fi
RUN python -m venv /opt/venv
ENV PATH="/opt/venv/bin:$PATH"
ENV SKIP_PRE_BUILD="true"
COPY . /build
WORKDIR /build
# bring in the prebuilt front-end before package installation
COPY --from=webui-builder locust/webui/dist locust/webui/dist
RUN pip install poetry && \
    poetry config virtualenvs.create false && \
    poetry self add "poetry-dynamic-versioning[plugin]" && \
    poetry build -f wheel && \
    pip install dist/*.whl

# Stage 3: Runtime image
FROM base
COPY --from=builder /opt/venv /opt/venv
ENV PATH="/opt/venv/bin:$PATH"
# turn off python output buffering
ENV PYTHONUNBUFFERED=1
RUN useradd --create-home locust
# ensure correct permissions
RUN chown -R locust /opt/venv
USER locust
WORKDIR /home/locust
EXPOSE 8089 5557
ENTRYPOINT ["locust"]

Command line
docker build -t locust .
Locustfile contents
default one!

Python version
3.11
Locust version
latest
Operating system
22.04

Good catch!
Fork the repo, make a branch and then open PR to our master branch and I’ll accept it!

appreciate your kindness i will do that

@cyberw
Hey there, #2814 fixed this, right? Would be awesome to get this closed :)


Install authorino-operator in Air-gapped environment or helm chart of the Operator

Dear Team,
Do we have a way to install Operator in disconnected kubernetes cluster ? Or maybe there is a helm-chart to install and configure it using ArgoCD.  Please refer to the link or location where I can find the details about it

@vchauhan1, the 2 recommended ways to install Authorino Operator are by using OLM or the install script (dev workflow and demos mainly.) These methods are slightly trickier to adapt for disconnected install.
However, provided you have cert-manager already installed, you can install the operator by applying, for example, this single manifest file: https://raw.githubusercontent.com/Kuadrant/authorino-operator/v0.9.0/config/deploy/manifests.yaml (which is basically what the install script does.)
You can create a copy of the file and tweak with it a little bit. In the authorino-operator and authorino-webhooks deployments, modify the images with ones you push in advance to your registry and maybe set imagePullPolicy: IfNotPresent.
The Authorino CR also allows setting image and imagePullPolicy to override the defaults. This may require some additional watching for potential version mismatch between operator and operand and therefore caution when rolling out upgrades.

@guicassolato , Thanks for the response. This is amazing and it worked.  If we can have Helm chart for Operator to get it installed in disconnected envs would be great.

We now have a helm chart for installinf Authorino Operator https://artifacthub.io/packages/helm/kuadrant/authorino-operator
@guicassolato Do you think we can close this issue?


feat(nuxt): allow passing dynamic route params in useFetch via options

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Currently, to make a useFetch request with a path containing dynamic segments, we need to use string interpolation/concatenation to substitute these with real values. This PR allows for keeping the request path unmodified.
It exposes a routeParams property (key-value pairs), which provides autocompletion for the keys by extracting dynamic segments from the request's path. Dynamic segments of the unmodified path are substituted internally with the real values provided via this property.
An example:
await useFetch("/api/posts/:post-id/comments/:comment-id/**/**:slug", {
    routeParams: {
        ":post-id": 1,
        ":comment-id": 2,
        "**": "catch-all",
        "**:slug": "named-catch-all"
    }
})

The current syntax for routeRules requires the keys to be unique, therefore making it impossible to specify different values for two different segments named in the same way, e.g /api/posts/:id/comments/:id or /api/posts/**/comments/**. However, as Nuxt allows for flexibility in naming, these two examples could be taken care of by the users and updated to e.g. /api/posts/:post-id/comments/:comment-id or /api/posts/**:posts/comments/**:comments.
I would very much value the team's feedback on this, whether this is something worth proceeding with or not.
Things to consider (if feedback is positive):

making it an experimental feature
applying it to $fetch as well
improving DX by providing a warning when dynamic segments are left with no routeParams provided
keeping the routeParams keys exactly the same as in the path vs coming up with different format and mapping accordingly

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[ ] I have updated the documentation accordingly.

Related: https://github.com/nuxt/nuxt/issues/21532

I would use this in my projects.
If the routeParams option is introduced, should we consider deprecating the params option? It is currently an alias for the query option and might become confusing.

Closing in favor of https://github.com/nuxt/nuxt/issues/21532.


Allow for separate frontends

This is big, so let me explain and solicit feedback before continuing on working on it.
Goal:
Support more than one frontend for browser chrome.
Non goal:
Support more than one set of content / about pages.
I had two initial ideas:

Build it as a single react app that allows switching out one of the higher level container components depending on some sort of frontend pref.  That pref would be loaded / chaged in the rendering process.

Pros:

Could switch browser chrome immediately in a window without messing up webview state
Easy, limited build system changes, no need to communicate back to main process

Cons:

Ties any frontends into the single application

Change the URL that the main process uses to load and build two or more completely separate apps that are loaded in a different HTML pages.  Pull out some of the core chrome components (location bar, page, etc) into the shared directory and then webpack two separate bundles.

Pros:

Additional frontends could use whatever tech they wanted
Better potential for loading frontends from an external URL if we want to do that in the future.

Cons:

Extra build system work
Can only really switch browser chrome when a new window is opened (requires a top-level navigation which would lose track of all webviews). I think this is an OK restriction though, since it seems likely we'd be shipping a different frontend based on the build mostly, not so much focused on runtime switching.
Can be tricky to figure out what components are 'shared chrome' and what is specific to a frontend.  I think long term depending on frontend designs, things like a Location bar is shared, but NavBar isn't.  We might also need to be able to inject styles and possibly extra options into the shared things.

@victorporof @linclark @jsantell any thoughts?  Am I missing another approach?  If there ends up being a consensus around this, there's still more to do:

Fix up tests
Refactor duplication in the build system
Figure out the UI and IPC mechanism for switching between the frontends.  Some kind of preference that applies to all new windows?

This PR is implementing idea number 2 - mostly shuffling files around and build system changes to make two separate bundles.

I am very much in favor of idea 2, with the caveat that we should try to reuse as much code as possible.

Just pushed a rebase / update based on the initial comments.  Only thing I didn't address is getting rid of duplication in build system

Also in favor of method 2; I don't think there's any value in being able to 'hot swap' out UIs while saving state. While cool, reminds me of this gif titled, "How responsive web designers think users use their site".
Also, there's not going to be unified components and style and state right off the bat, and we still may end up with unshareable components due to goals (which, while we have some better ideas, far from concrete), and method 2 atleast can be eased in over time

Agreed, method 2 seems like it gives us flexibility that we'll potentially need to use different tech across frontends. If the build system work is manageable, then that sounds like the better solution.

Really nice work here @brian. This is going to help us a lot in the near future.

Thanks for feedback all.  Closing this in favor of #734


Support for defaulting height not just width

Now, I can set 'size' to set the width (move the vertical splitter bar). Are there plans to support setting the height?
Thanks!
David

Hi Guys,
This is a fairly important feature, that would quality as a bug..
Without a way to "disable splitter bar drag" or launch in an iframe as work around, for most applications outside of some mobile layouts, this controller is unusable.
Please fix so I don't have to move back to jquery
thanks

I also want this feature... ;)
Is there any chance to support this?
http://stackoverflow.com/questions/37168758/how-do-i-make-6-elastic-panes-1-header-5-panes-with-default-width-and-height


Use util.promisify.custom to improve promisify support of db.run()

Fixes #658
Currently, promisifying db.run() results in a loss of information of lastID and changes.
In this PR, I customized the promisification of db.run() using util.promisify.custom to solve the problem.

It is likely the tests fails due to https://github.com/nodejs/node-gyp/issues/1933

@kimamula Would you mind rebasing on top of master so CI can be run? 🙂


Support for full compilation of projects (ie. TypeScript)

As stated here:
https://github.com/brunch/typescript-brunch/blob/master/README.md#errors
Brunch doesn't really support compilation of an entire project directory. Perhaps it might be worth adding a function callback to the plugin API called compileProject or similar, wherein all filepaths matching the prototype.pattern are handed to the function.
The current way TypeScript compilation is done is a bit too hacky for me and a showstopper.

Same as this user, I'd like to know what changes are being made in this PR:
https://github.com/brunch/brunch/pull/1664#issuecomment-314840313

Something similar would be beneficial for elm-lang-brunch as well, since all Elm-projects are built from an entry point.
Right now, I am playing with getDependencies to build a dependency tree which brunch can keep track of. For any non-entry file, the compile function just parses the imports, assigns them to the file so that getDependencies can get the paths for all the modules imported. This way, brunch keeps track of all the dependencies so that when saving an imported file, the entry file gets compiled.
The caveat? Well, when compiling a non-entry file, I have to emit the file or getDependencies will not be executed. So I set the data of the file to an empty string (file.data = '';) but this causes brunch to emit an empty module definition (e.g. require.register('elm/MyModule.elm', function () {}}) in the output file.
It should be possible to remove such superfluous registrations with a decent optimizer, but optimally there would be a way to tell brunch not to include the file when concatenating the final file.
Perhaps this path is something that would work for typescript-brunch as well?

We are going to drop javascript.joinTo in #1664 and make compile method of, let's say, typescript-brunch called only once per entry point.


incorect ECBDIC <-> ASCII conversation tables

Hello, all.
In the wrapperutils.c file, I believe that the EBCDIC <-> ASCII conversation tables are not quite right.
DJ

Thanks for you information. Could you please share us the source link of the EBCDIC <-> ASCII conversation tables?

Two examples:

For a2e, according to https://www.ibm.com/docs/en/iis/11.7?topic=tables-ascii-ebcdic , a2e[21] should be 4F = 79
For e2a, according to https://www.ibm.com/docs/en/iis/11.7?topic=tables-ebcdic-ascii, e2a[5A] should be 5D = 93


(feature) Polymer: Remoting controller for Polymer 3.

Google will release Polymer 3 at Google I/O 2018 this week (conference sessions on May 9th). With Polymer 3 we'll still have the option to use <remoting-controller> as mixin for PolymerElement. But the stated goal of the Polymer team it to allow lighter and more loosely coupled elements, hence they'll introduce LitElement (headed for 1.0 release in the coming months). This new Web Component base class will be the successor of PolymerElement.
To support PolymerElement in Polymer 3 we probably have to additionally provide <remoting-controller> on npm registry. It would also be nice if the element is converted to JavaScript modules, though still using HTML imports should still be fine. The PolymerElement will not see active development in the future.
To support LitElement in Polymer 3 we'd have to rethink how Dolphin Platform communicates changes to this base class. It will get rid of the Polymer data system and template stamping (no property effects with set() and splice(), no templates with two-way bindings). The Polymer team suggests to use Redux state store instead, but also says with LitElement you should be free for more different options.

Regarding LitElement, lit-html, and redux stores. I played a bit with Dolphin Platform and found following obstacles:

Dolphin ▶ redux ▶ LitElement: Using the Dolphin's approach to identify beans by object reference and redux's nature (freeze'd objects) give some obstacles. Redux has the concept of selectors (see: reselect [1]) which could be helpful to specify changes/splices to bean properties). LitElement uses lit-html which takes the complete property tree (say: Dolphin model) and only update the template parts that causes changes, i.e. only applies the subproperties that causes these changes.

LitElement ▶ redux ▶ Dolphin: Here we probably need to diff the objects, to explictly send the changes to the Dolphin controller. The immer library [2] could be helpful, if it allow to retrieve a list of changed subproperties.

Additionally how to mix uni-directional changes (the LitElement/redux appoach) and bi-directional changes (the PolymerElement approach) is an open question.
References:

[1] https://github.com/reduxjs/reselect
[2] https://github.com/mweststrate/immer

This issue was moved to rico-project/rico#7

This issue was moved to rico-project/rico#11


Android device says plugin is not installed but it is

I am having this problem here, again, I am 100% sure I have had this problem before but I am not sure how I solved it.
Any idea how to fix this? Actually I have the plugin installed, but when I run on device (Android) is says I have not:
[15:28:26]  console.warn: Ionic Native: tried calling BackgroundGeolocation.configure, but the BackgroundGeolocation plugin is not installed.
[15:28:26]  console.warn: Install the BackgroundGeolocation plugin: 'ionic cordova plugin add cordova-plugin-mauron85-background-geolocation@alpha'
[15:28:26]  console.warn: Ionic Native: tried calling BackgroundGeolocation.isLocationEnabled, but the BackgroundGeolocation plugin is not installed.
[15:28:26]  console.warn: Install the BackgroundGeolocation plugin: 'ionic cordova plugin add cordova-plugin-mauron85-background-geolocation@alpha'

Plugins:
± % cordova plugin list                                                                                !40
com.googlemaps.ios 2.7.0 "Google Maps SDK for iOS"
com.telerik.plugins.nativepagetransitions 0.6.5 "Native Page Transitions"
cordova-android-support-gradle-release 2.0.1 "cordova-android-support-gradle-release"
cordova-plugin-add-swift-support 1.7.2 "AddSwiftSupport"
cordova-plugin-android-permissions 1.0.0 "Permissions"
cordova-plugin-camera 4.0.3 "Camera"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-console 1.1.0 "Console"
cordova-plugin-contacts 3.0.1 "Contacts"
cordova-plugin-device 2.0.2 "Device"
cordova-plugin-email-composer 0.8.15 "EmailComposer"
cordova-plugin-facebook4 3.1.0 "Facebook Connect"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-globalization 1.11.0 "Globalization"
cordova-plugin-googleplus 5.3.2 "Google SignIn"
cordova-plugin-ionic-keyboard 2.1.3 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 2.2.0 "cordova-plugin-ionic-webview"
cordova-plugin-linkedin 1.2.1 "LinkedIn"
cordova-plugin-mauron85-background-geolocation 2.3.6 "CDVBackgroundGeolocation"
cordova-plugin-media 5.0.2 "Media"
cordova-plugin-nativeaudio 3.0.9 "Cordova Native Audio"
cordova-plugin-nativegeocoder 3.1.2 "NativeGeocoder"
cordova-plugin-network-information 2.0.1 "Network Information"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-streaming-media 2.2.0 "StreamingMedia"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova-plugin-x-socialsharing 5.4.1 "SocialSharing"
cordova-sqlite-storage 2.5.0 "Cordova sqlite storage plugin"
es6-promise-plugin 4.2.2 "Promise"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-barcodescanner 8.0.0 "BarcodeScanner"
phonegap-plugin-push 2.1.2 "PushPlugin"
twitter-connect-plugin 0.6.0 "Twitter Connect"

Ionic Info:
± % ionic info                                                                                !41

cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-utils  : 1.19.2
    ionic (Ionic CLI) : 3.20.0

global packages:

    cordova (Cordova CLI) : 7.1.0

local packages:

    @ionic/app-scripts : 3.2.1
    Cordova Platforms  : android 6.3.0 ios 4.5.5
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 26.1.1
    ios-deploy        : 2.0.0
    ios-sim           : 6.0.0
    Node              : v8.11.3
    npm               : 5.6.0
    OS                : macOS
    Xcode             : Xcode 10.1 Build version 10B61

Environment Variables:

    ANDROID_HOME : /Users/francisco/Library/Android/sdk

Same issue here with the 3.0.0-alpha.50 version

It'is happening to mee too.

Same issue here running on Android 8.0.0

Were you able to fix it? having the same problem here...

Yes, I did fix, how? Removing platforms and adding them again,  and yet removing node_modules dir and running npm install again.
In the end of the day Ionic has so many troubles that I am surely migrating to React Native (piece by piece)


solved HW9

solved and I hope I did it well

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Program.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Program.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Program.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/BinaryConversion.cs  2
- Src/BootCamp.Chapter/printEmonicons.cs  1
- Src/BootCamp.Chapter/DecimalConversion.cs  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
- Added 3

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/ArrowMovement.cs  1
- Src/BootCamp.Chapter/BinaryConverter.cs  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/ArrowMovement.cs  1
- Src/BootCamp.Chapter/BinaryConverter.cs  3

See the complete overview on Codacy


Avoid allocations in publications

It seems inefficient to always build a Vec<u8> to hold publish data if the data length is relatively constant.  For example, if always publishing i32 or f32/f64, etc., it is a waste to always have to create a new Vec<u8> every time.
A suggestion is to make Publish with a minimum buffer size (something like 8 bytes should work for most primitive data types):
pub enum Payload {
    Fixed([u8; 8], u8),    // 8-byte buffer, length
    Vec(Vec<u8>),        // Variable length
}

pub struct Publish {
    topic: Cow<'static, str>,
    payload: Payload,
    qos: QoS,
    retain: bool,
}

fn new_4<T: Into<Cow<'static, str>>(topic: T, payload: [u8; 4]) -> Publish {
        let mut buf = [0_u8; 8];
        buf[0..4].copy_from_slice(payload);
        Publish { topic: topic.into(), payload: Payload::Fixed(buf, 4), qos: QoS::AtMostOnce, retain: false, }
    }
}

pub fn new_i32<T: Into<Cow<'static, str>>(topic: T, payload: i32) -> Publish {
    Self::new_4(topic, payload.as_le_bytes())
}

This also uses Cow<'static, str> to avoid allocations when topic names are constants (which may happen a LOT).

A new PR is submitted with the changes.

Thanks for your interest in the crate, these are intriguing ideas.
For optimisations like this I'd probably like to see benchmarks to prove that this actually makes publish faster. Could you put together some microbenchmarks reading and writing to Cow<'static, str>, String, Vec and your Payload to show your versions are faster?
I'm trying to support compiling under the Rust stable toolchain, so please keep the benchmarks (requiring the #![feature(test)] attribute on the crate) in a separate bench test library or behind a Cargo feature flag bench.

I'm trying to support compiling under the Rust stable toolchain

That's strange... I have been using stable all this time and there hasn't been a problem...

As for benchmarks, I am not sure how it would be meaningful as the network latency is likely to dwarf any savings on the publication side...  Admittedly it is not going to be an earth-shattering optimization because very few clients are going to do rapid-fire publishes...  It may only be meaningful for very resource-constrained devices.
The optimizations are not difficult and they only tune for the common scenario: repeat publishes to the same topics with small amounts of data.

I agree that network latency could well dwarf any savings, and that these changes could be most helpful in devices with limited memory.
I did a little Googling and there's actually a crate -- smallvec -- that does this same optimisation (store data inline when small, use a Vec when enough elements are stored). What's more surprising is that in the benchmarks here smallvec often performs worse than a plain vector because heap allocation is so fast.
So I'm not sure about the Payload change: adding an extra dependency and some cognitive load for the user for possibly a slight decrease in performance.
As for the topic name, using Cow is an interesting idea but I'm not sure about that change either without seeing any benchmarks.

I did a little Googling and there's actually a crate -- smallvec

I didn't know that!  Good find!

Thanks for the input but I'm going to close this now without positive benchmarks to show it helps.


[WFLY-15734] / [WFLY-15356] Remove security-plugins dependency from EJB3.

https://issues.redhat.com/browse/WFLY-15734
This PR is just removing some code which should no longer be in use for legacy security integration so we can delete the legacy security modules and get the PicketBox dependency removed.

@tadamski / @chengfang Would it be possible to please get a review on this one?

@chengfang I have added the name of the security domain to the log message, if you are Ok I think I can get this through tomorrow.


Remove Rx#filter and refactor implementation accordingly

Also adds Rx#foreachNext and Rx#get, not sure it's wise to have them in public api...
@olafurpg what do you think?

I think get should be scary, I would consider it as bad a Option#get, i.e. if you use it for anything but tests you are doing it wrong...

but will .get ever throw an exception? If not, then I think we should use a different name since Option.get does throw an exception. Maybe underlyingValue?

Alright I'm sold on .value :smile:


FilterPolicy rules are all executed instead of the first matching rule

Describe the bug
According to the documentation, the first FilterPolicy rule that matches the incoming request, will be executed. However, Ambassador seems to execute ALL matching rules in a FilterPolicy.
Quote from the docs:

Edge Stack will choose the first FilterPolicy rule that matches the incoming request. As in the above example, you must list your rules in the order of least to most generic.

Effectively, this also means that the below snippet (taken from the documentation) won't work:
---
apiVersion: getambassador.io/v3alpha1
kind: Filter
metadata:
  name: param-filter # This is the name used in FilterPolicy
  namespace: standalone
spec:
  Plugin:
    name: param-filter # The plugin's `.so` file's base name

---
apiVersion: getambassador.io/v3alpha1
kind: FilterPolicy
metadata:
  name: httpbin-policy
spec:
  rules:
  # Don't apply any filters to requests for /httpbin/ip
  - host: "*"
    path: /httpbin/ip
    filters: null
  # Apply param-filter and auth0 to requests for /httpbin/
  - host: "*"
    path: /httpbin/*
    filters:
    - name: param-filter
    - name: auth0
  # Default to authorizing all requests with auth0
  - host: "*"
    path: "*"
    filters:
    - name: auth0

To Reproduce
Steps to reproduce the behavior:

Deploy Ambassador
Deploy the httpbin application
Deploy the Filter and FilterPolicy listed above
Make a request to /httpbin/ip

**Expected behavior**
Expect that no filters are triggered. However, actually the param-filter and auth0 filter will be triggered.
Versions (please complete the following information):

Ambassador: 3.3.0
Kubernetes environment: AWS EKS
Version: 1.23

I was thrown off by an error in one of my plugins that made me think Ambassador wasn't handling things properly..


fix(entry.server): provide nonce to react scripts

This patch provides the nonce option to the React renderToPipeableStream function so that React will add it to scripts dynamically injected (e.g. the <Suspense> inline scripts).
Ref: https://react.dev/reference/react-dom/server/renderToPipeableStream#parameters
Ref: https://github.com/facebook/react/issues/26026#issuecomment-1398640424
Ref: https://github.com/remix-run/remix/issues/5156#issuecomment-1397935995

Test Plan

Checklist

[ ] Tests updated
[ ] Docs updated

Screenshots

Honestly not sure how I missed this 🙃


bump node-mime to 2.x

Thank you for the pull request.
Unfortunately we're not ready to upgrade this yet. Mime 2 supports only Node 6+, and we still have users on Node 4.
I'm going to leave that pull request open until next major update of superagent when we'll be able to bump requirements to Node 6.


Update intro/getting started docs

This PR fixes a couple issues with the docs:

The Getting Started page is hard to find as the link is the heading and the heading has no visible indication of being clickable
The index page (linked to from the Components heading) duplicates a lot of this info but the two pages have drifted out of date over time.

In this PR, I've combined the two pages and made it the index page, and changed the left nav so that a "Getting Started" page appears in the nav; this redirects to the index page and I've set up a now redirect to handle the change.
This also includes the changes from #785
Demo: https://primer-components-git-mkt-some-docs-updates.primer.now.sh/components/

Hey! It looks like by merging the index page, About link, and Getting Started page, we lose the hero image and some of the content that was originally in the index.
I think we should just merge About and Getting Started and keep the index page as is with the hero and a little intro, but maybe remove some of the content that's also in Getting Started and just link to the getting started docs on that page? So the index page would essentially be: hero image, What are Primer Components?, Principles and maybe Local Development?

Hey! It looks like by merging the index page, About link, and Getting Started page, we lose the hero image and some of the content that was originally in the index.

Ah I totally missed the hero image, that was my fault. But let it be known that I really dislike our hero image; it takes up almost the entire screen for me. (But that's a different discussion :)

I think we should just merge About and Getting Started and keep the index page as is

What are you referring to when you mention About? I only merged two pages (getting started and index).

Oh wait, it's the new heading I added 🙈
So do you think the Components subheading should still link to the index page, and have some of the original content (and hero image) and the About Link and Getting Started page should lead to the same page (with installation instructions and such)?

I added the Hero and the stuff I missed copying over; still think it needs to be two pages? I'm not exactly sure where to link to them from given the subheadings are suboptimal.

This is what I had in mind:
Index:

Hero image
Intro
Principles
Local development (heads up the markdown heading is currently broken just for this heading for some reason 🤔, it's just showing the hashes instead of turning it into a heading )

About:

redirects to Getting Started
Doesn't have a hero image

Getting Started:

no hero image
has all the getting started docs
doesn't include intro/principles/local development

Gotcha. Do you think the index page should still be linked to from the Components subheader?


knife ec backup failures

Describe the problem
I just ran across two different knife ec backup failures.
One failure was while running a local terraform external postgresql scenario, after I logged into the chef-server box and tried knife ec backup.
The other issue was with the nightly umbrella test, fresh-install scenario.  Although the scenario was green, knife ec backup had failed there also.  Which brings up a third issue - we did not know we had a failure because the test was green.
Acceptance criteria:

[x] knife ec backup works, standalone-fresh-install scenario.
[x] The standalone fresh install umbrella scenario fails if knife ec backup fails.
https://github.com/chef/umbrella/pull/200
[ ] knife ec backup works, external-pg scenario (when ran locally via terraform, after logging into the box).
We might consider adding knife ec backup to this and other scenarios (currently it's only standalone-fresh-install).

Software Version

PLATFORM=ubuntu-18.04 INSTALL_VERSION=14.9.23 UPGRADE_VERSION=14.10.23 SCENARIO=external-postgresql ENABLE_ADDON_PUSH_JOBS=false ENABLE_GATHER_LOGS_TEST=false ENABLE_PEDANT_TEST=false ENABLE_PSQL_TEST=true ENABLE_SMOKE_TEST=false ENABLE_IPV6=false ENABLE_ADDON_CHEF_MANAGE=false make apply

See https://buildkite.com/chef/chef-umbrella-main-chef-server/builds/846#9129b904-f2ea-4507-a6a5-6fd5a67bec28

Replication Case

sudo /opt/opscode/bin/knife ec backup /var/opt/knife-ec-backup/ --with-user-sql --with-key-sql -VVV -c /etc/opscode/pivotal.rb

See  https://buildkite.com/chef/chef-umbrella-main-chef-server/builds/846#9129b904-f2ea-4507-a6a5-6fd5a67bec28.


Feature/fe rework small styling changes

Hey @EmilyHazlehurst , do you mind if I push a bit of code to this branch?
It's related to redirectLegacyDocumentUrls and breaking some of it's functionality out into a function called getDocumentBySourcePath.

That's fine with me :)

The PR looks really good btw, there are just a few things related to how docs and uploads work - I'll follow up tomorrow 😄

Hey @EmilyHazlehurst would you mind testing/reviewing the changes that I've added.
I made the changes rather than give feedback, as I wasn't really sure about a solution and didn't want to give bad advice. I'm absolutely happy to revert all my edits or for you to change them.
My changes include:

Adding a helper function to the Documents class that gets a document id from a URL.
An update to getFileDownloadParams to use the Documents helper function.
A modification to getFormattedFilesize, so that the function doesn't read from the filesystem. This is because documents and the Medial Library items are offloaded to S3 as soon as they are uploaded.


fix: saving VO2_MAX recording does not work

Hi!
I'm trying to record VO2_MAX, but the "vo2MillilitersPerMinuteKilogram" field is being transmitted from the JS side

@matinzd I just happened to.)


Be more transparent about dynamic scoring

Make it so that teams don't have to dig into our source code to find out how our dynamic scoring system works.
We should display our scoring formula somewhere (maybe as a page on our website with a link to the page under the point values of every dynamically scored challenge) along with parameters such as initial points, minimum points, and number of solves to reach minimum.
This way people don't have to reverse engineer the parameters by solving math equations (it would be a nice CTF challenge though). A stretch goal is to implement a playground where participants can calculate their scores or place on the scoreboard based on hypothetical solves. We can even make a customizable scoreboard like OOO's scoring-playground.

We basically removed dynamic scoring so I'm closing this.


Add a plugin manager.

A plugin manager is required to register new plugins and provide easy mechanism for the CLI to discover and extract information to build CLI options from available plugins

PR: https://github.com/log2timeline/PlasoScaffolder/pull/22

called scaffolder manager now: https://github.com/log2timeline/PlasoScaffolder/commit/25fa1239a256f875d6ac30dd7e3cd86e3ee8bf29
this is done


bug: Multiple popover have all the same scope since beta.14

Type: bug
Platform: all
If there is multiple popover in the same page, for example in a list, they all get the same scope.
The problem is not present when using beta13, but is in beta.14 and rc.0.
Remove one popover and you can't open the other ones ... (reopen the same one)
Here's a pen that show the bug.:
http://codepen.io/kbenoit/pen/OPZoeV

Here's a workaround, it implies creating the popover just in time and removing it when it is hidden:
http://codepen.io/kbenoit/pen/emrPdr

+1. Was quite hard to detect what was going on exactly.

+1, Please look into this.

I tried again @kristianbenoit solution, but now is not even working in his codepen if we update to ionic.rc.3.
Please, this was working before until beta.14 was released...

+1

I confirm the workaround I proposed does not work anymore in 1.0.0-rc.3 and nightly.

+1, Someone know the solution for the bug?

@YongdeCHEN, so far use my work around with ionic-1.0.0-rc.2

@brodykidd, this is the issue I mentioned in the email ;)
Just in case you need to update the status.

+1

could this issue also be related? http://codepen.io/anon/pen/yNPmvL

@liyo, that's the same problem. Using the solution I provided above should fix your problem (create the popover in the ng-click handler).

@kristianbenoit, what about version 1.0.0? Your solution doesn't work with the "stable" version, right?
Thanks anyway.

@kristianbenoit, actually I tried your method with the latest version and it worked! Great, thanks.

@kristianbenoit thank you, I was able to make it work with the latest Ionic version and your method. To avoid an infinite loop when popovers were removed on hide (because for some reason popover.hidden is still firing on remove), I had to manually remove the popover backdrop DOM elements manually, see: http://codepen.io/liyo/pen/XbZreg

@alejandromagnorsky, as @liyo says, there is an issue involving an infinite loop in the previous solution, where we call popover.remove while on "popover.hidden", at this point the popover is not hidden yet so on "popover.hidden" is called again. Solution, call stopListening() before popover.remove.
$scope.$on('popover.hidden', function() {
      stopListening();
      popover.remove();
});

Here's a pen with the working solution.
http://codepen.io/kbenoit/pen/BNVomX

@liyo, the pen you provided, does not remove the popover (it's leaking DOM elements). Did you forget to click save ?

@kristianbenoit yes indeed I forgot to save, I have updated it now just for reference.
Anyway, your new solution works great and there is no need to do a manual DOM removal of popover elements. Thank you!

This works great. However, the weird thing is that it doesn't appear to work in ionic view, but it works in ionic serve and the emulator.

Nevermind. Solution works fine. I realized that my reference to my template was wrong. I named it popOver.html and didn't realize that my URL was pointing to popover.html... :cry:

Hi,
I've just had the same issue.
It seems to be related on how the template urls are handled by ionic ($ionicTemplateLoader actually).
When using $ionicPopover.fromTemplateUrl, the popover modal is returned after $ionicTemplateLoader.load is done getting the template. Loading the same url multiple times at the same time returns the same unique promise and therefore a single modal I suppose.
Another simple workaround is to use the angular template system (taking advantage of the templateCache).
So instead of doing:
$ionicPopover.fromTemplateUrl('mytemplate.html', { scope: $scope })
    .then(function(popover) {
        $scope.popover = popover;
    });

By injecting $templateRequest:
$templateRequest('mytemplate.html')
    .then(function (tmpl) {
         $scope.popover = $ionicPopover.fromTemplate(tmpl, { scope: $scope });
    });

PS: I haven't tried but I'm pretty sure this issue also happens with $ionicModal


Error while handling request

Good afternoon, I have an OCPP error in some transactions, all of the same type (DeAuthorized).
ERROR - Error while handling request '<Call - unique_id=fe87613f-a4a7-4434-8c1a-4451242c76a9, action=StopTransaction, payload={'idTag': 'MLG4C4F9U29HNUZCIHZM', 'timestamp': '2023-12-26T19:27:38.289Z', 'meterStop': 892000, 'transactionId':<PHONE_NUMBER>, 'reason': 'DeAuthorized'}>'
V1.6 Json
Can you help me? Thank you.

What is the error? Can you elaborate.
To me, this seems fine.  The StopTransaction indicates the end of a charging session. The reason DeAuthorized seems to indicate that someone provided an RFID to end the session and unplug the cable.


in FALSEHOODS.md, point #9

I am not certain (because I'm not an expert in phone number rules), but I believe you forgot to include +54 within the "transformed number" in point #9 in FALSEHOODS.md

This transforms +54 9 2982 123456 into 02982 15 123456.

It says "to dial a mobile number domestically", so the country calling code is dropped.
See:
http://libphonenumber.appspot.com/phonenumberparser?number=%2B5492982123456
National format	02982 15-12-3456
International format	+54 9 2982 12-3456
The point is that it's not a straightforward "change the digits in front somehow" to go from one to the other.


Rename Column Headers in Extracted SNAP data

I am trying to rework the following code that Kata developed to extract CRU TS V4.3 data from  sample points, so that it will extract data from the my AK specific UAF SNAP climate data.
https://github.com/pafrank89/AlaskaShrubs/blob/master/R_Script/ClimateData_Extract.R
**Lines 117-127
After extracting data we want to rename the column headings. The CRU TS V4.3 data is organized starting 1901 progressing through the months from January to December for each year up to 2015 (ex. 1901-Jan, 1901-Feb, 1901-Mar ect...)
To do that the code looks like this:
years <- 1901:2015
 month <- c("Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec")
names(snap.pre.shrubs) <- paste(rep(years, each=12), rep(month, times=113), sep="_")
The SNAP data is structured by month, so it starts with all the January values between 1901 and 2015 (ex. 1901-Jan, 1902-Jan, 1903-Jan, ect...) So I need to rework this so that the columns in the snap data are correctly renamed, but am unsure after looking at the documentation for paste and rep, that I understand how to update this code to make it work.
Thanks for your help!

If I understand correctly, try
eg<-expand.grid(years,month)
monyr<-paste(eg$Var2,eg$Var1,sep='-')

That's perfect!
Thank you James


EntityQuery only has private setters

EntityQuery only has private setters which blocks us from using it.
https://github.com/wallee-payment/wallee-csharp-sdk/blob/master/src/Customweb.Wallee/Model/EntityQuery.cs

You are right, all EntityQuery*.cs models are read-only.
I will fix this and make a new release.


fix "runAsGroup is specified without a runAsUser"

set PodSecurityContext RunAsUser to avoid error
set InitContainer RunAsUser = 0 to avoid permission error when calling chown -R

Sorry for the late response. Many thanks for your contribution


Support launching devtools from the flutter tool

This could be done via an additional keycode command, like K. The logic to launch devtools is fairly straightforward. For example, see the following code in dwds:
https://github.com/dart-lang/webdev/blob/master/dwds/lib/src/servers/devtools.dart

cc @jacob314 @zanderso

I think it would be good for the tool to delegate as much as possible (spinning up the server, launching the browser, etc.) to the devtools package(s). In that case calls like serveDevTools() and launchDevTools() from here look promising.
It looks like we first need to get package:devtools_server bumped far enough forward to pick up all the calls. This is probably the right time in the release cycle to update dependencies like this.

It looks like we first need to get package:devtools_server bumped far enough forward to pick up all the calls.

Oh, it looks like a version of devtools_server that includes launchDevTools() hasn't been published yet if I'm reading things right. (https://github.com/flutter/devtools/pull/1365). @DanTup @devoncarew

Looks like that change landed 28 days ago, and the last release (0.1.13) was 11 Dec, so I would expect that change to be in there. It is possible to launch DevTools from earlier versions, but it had to be done over the VM service (whereas now it can be done via stdin).
I presume the server would only be spun up once the user asks for it (and not at startup)? Otherwise, we should be sure to skip it when running in --machine mode, since IDEs might spawn their own copy (and having multiple copies of DevTools try to register the same VM services would likely cause issues).

I'm only seeing 0.1.12 on pub: https://pub.dev/packages/devtools_server

I presume the server would only be spun up once the user asks for it (and not at startup)?

That's right, e.g. when pressing a key at the command line hot reload prompt.

Oops sorrry, I was looking at https://pub.dev/packages/devtools/versions and didn't realise the server didn't get the same last update.
@jacob314 @kenzieschmoll FYI (I think @devoncarew will also want this for https://github.com/flutter/flutter-intellij/issues/3503). If there's a DevTools release coming soon, it'd be good to include the server.

@DanTup it looks like you're listed as an uploader for devtools_server. Is all that is missing here pushing 0.1.13 to pub?

When a new server is published, then devtools needs to also be updated to reference that version and be published. I don't have access to that account to publish anymore; @jacob314 may be the best person to ask about releases.

This is done in https://github.com/flutter/flutter/pull/53902


fix: dynamic oracle loading (sklearn version)

Addresses #163
This is a draft PR with a rough sketch. Let's discuss here :)

Draft PR for dynamic loading of oracles dependent on sklearn version.
Idea: Determine the sklearn version at runtime. Then, load the correct version of the oracle, i.e., the one that was trained with the sklearn version that the current user has. Disadvantage: Users with different sklearn version will see slightly different predictions for the same Oracle-smiles pair.
The idea would be to just append a _sklearn>024 to the filename of the original model on your COS
This should be minimally invasive as it is perfectly backwards compatible and does not have side effects

TODO:

[ ] I do not know the codebase well enough to see whether this sklearn versioning problem might arise in other places of the package as well.

@kexinhuang12345 @futianfan

I tried to merge the work from #167 into this PR.
I debugged with 3 sklearn versions, 0.23.0 (which was stable already before), 0.24.2 (broken up to now) and a very recent release (1.0.2 also broken up to now).
It seems functional, that's really great :)
I only debugged with the GSK3 oracle
only drawback that I see now is that if a user downloads an oracle and THEN upgrades sklearn, an error will occur. This could be prevented by saving the models locally with different names such as gsk3_legacy and gsk3_current. But not sure it's worth it - up to you

@jannisborn
Hi Jannis, i create a new branch that merge #167 (my version) and #168 (your version). we hope to use two oracle files: jnk3.pkl (<=0.23 sklearn) and jnk3_current.pkl (>0.23 sklearn). It would be great if you can take a look. If you find it is ok, can you use the new code to submit PR again? thanks so much for your contribution!

Hi @futianfan
Should be done now! you can delete your sklearn_merge_168_167 branch, it's integrated here

Thanks! it would be really great if you could release a new version :)
Then we could update our TdC dependency to that version and relax sklearn

Thanks Jannis! We do plan to release a version in the next week

HI @kexinhuang12345, any updates on this?

Hi Jannis, sorry for the delay.  We were planning to release it with https://github.com/mims-harvard/TDC/pull/161 but there is some data upload issue holding the schedule back. Do you need it urgently? if so, we can release it under 0.3.8 today - let me know!

Hi Kexin, thanks for the rapid feedback. No it's not super urgent, we were hoping to integrate some more TdC oracles (the ones affected by this PR) into our library and we're getting a bit behind schedule. I dont want to cause you more work, we just prefer installing from PyPI rather than from source, so having a new release soon would be cool :)

I see that makes sense! how about we will wait for another two days? On Wednesday if the data issue is still not resolved, we will release a new version first. Hope this would work!

Cool, thanks a lot!

Hey Jannis, a quick heads up, TDC is just updated to 0.3.7!

Thanks a ton Kexin, much appreciated 👍🏼


gcloud datastore container to allow configuration for consistency

gcloud beta emulators datastore start takes an optional --consistency argument. For local tests, setting this to 1.0 can be useful.
Propose adding .withConsistency(Float) to configure the startup command.
/cc @eddumelendez wdyt?

I agree. not an expert with the emulators but improvements like this will improve the DX. Thanks Ray!

See https://github.com/testcontainers/testcontainers-java/pull/5993 😃

Fixed by #5993.


Handle NaNs in y in same manner as 'plot' command

There has been several discussions of handling NaNs on the Matlab toolbox page. While there are several options for handling NaNs in all cases, e.g. in x, or y, or in the patch, etc. The simplest and most typical case is to handle NaNs in y in the same manner as 'plot' command so that non-contiguous lines are supported.
Consider this plot:
x = 1:10;
y = x + rand(1, 10);
boundary = 2 * ones(1, 10);
boundedline(x, y, boundary);  % requires boundedline function to be on path

Now when we add a NaN in y, this is not supported:
y(5) = NaN;
boundedline(x, y, boundary);  % error

This is the desired behavior:

This is akin to the way the 'plot' command would handle this case:
plot(x, y);  % with y(5) = NaN

okay, I've received enough feedback on this topic that I'll try to implement the behavior above.  I think I'll allow for a couple different behaviors:

remove NaNs/Infs
Keep them in the line, resulting in gap, but inpaint past them in the patches
Create a gap in both the line and the patch

If anyone has additional behaviors they'd prefer, please post here.

I reckon 3 should be the default.

In the end, #1 ended up being more complicated than anticipated to add to the code without major changes, so I've implemented just 2 and 3 in the most recent update.  See the new 'nan' input parameter to specify this.  I've kept fill-and-smooth as the default behavior for back-compatibility purposes (since that was the behavior in more recent versions).
So far testing has gone smoothly, and I'm in the process of writing up a more in-depth discussion of this function and its new options for my blog; will post here when that's done.

The option 1) remove NaNs/Infs was posted on the toolbox page by Eelke Spaak, this didn't work?

To fix this, I added the following around line 313, right before the actual calls to line() and patch():
% remove nans
for k = 1:numel(xp)
naninds = isnan(xp{k}) | isnan(yp{k});
xp{k} = xp{k}(~naninds);
yp{k} = yp{k}(~naninds);
end

Since it connects the points which were NaN, it basically linearly interpolates.

Removing from just the patches would be pretty straightforward, but
somewhat redundant because the results are almost identical to the 'fill'
option, which simply uses a slight smoother interpolant to fill the point
rather than the linear one the graphics fill in.  I was worried that users
would interpret "remove" to also apply to the line, and that would make
coding a bit more complicated. But I've gone ahead and added the
remove-from-patches-only option (to be uploaded shortly).
Known limitations from my test cases so far:

gap: Doesn't handle one-sided NaNs.  If there's a NaN in either side of
the bounds, it's a gap right now.
fill: Doesn't handle one-sided NaNs at the beginning or end of the line
well.  Creates a sloped edge in the patch.
remove: Same one-sided NaNs on end issue as 'fill'.  Also, two-sided
NaNs on the ends results in a gap, which may or may not be the user's
desired outcome.

On Wed, Feb 17, 2016 at 9:51 AM, alexperrone<EMAIL_ADDRESS>wrote:

The option 1) remove NaNs/Infs was posted on the toolbox page by Eelke
Spaak, this didn't work?
To fix this, I added the following around line 313, right before the
actual calls to line() and patch():
% remove nans
for k = 1:numel(xp)
naninds = isnan(xp{k}) | isnan(yp{k});
xp{k} = xp{k}(~naninds);
yp{k} = yp{k}(~naninds);
end
Since it connects the points which were NaN, it basically linearly
interpolates.
—
Reply to this email directly or view it on GitHub
https://github.com/kakearney/boundedline-pkg/issues/1#issuecomment-185323675
.


Implement no-segments-on-sliced-layers

Sliced layers (Entities, Features, Widgets, Pages) should not have folders with conventional segment names in direct children.

[ ] Write the rule
[ ] Write positive test
[ ] Write negative test
[ ] Add documentation in form of a README and link that in the main README of the repo

Hi guys!
I have no experience in open-source software development yet. But I’m interested in it and would like to start somewhere. I chose this project because I really like FSD and have successfully implemented it in several projects in my company and my personal projects. I think you have done an outstanding job and I look forward to helping you where I can.
Could you assign this task to me? Or how it is done in your organization.

Hi @daniilsapa! Glad to hear about your positive experience with FSD and thank you for taking the time to contribute. I assigned you to this ticket, so feel free to start working on it. If you need any help, I'll be here to answer any questions you have :)

@illright
Thank you! Starting working on it 👌

@illright
To avoid possible confusion, as far as I understand, there is a typo in the task description, instead of “Shared” it should say  “Entities”. Because the "Shared" layer is just segmented.

@daniilsapa yes, that's correct, fixed the description

@illright
I created a PR for this feature. Could you review it when you have time? Thank you in advance

Quality checks failed for my PR and I think I know why. I'm fixing it


Sync of changes in Dockerfiles with upstream

Sync of changes in Dockerfiles with upstream

https://github.com/quarkusio/quarkus/pull/28362
https://github.com/quarkusio/quarkus/commit/f335f7e084429d2744ff839e6273d64f017948eb
https://github.com/quarkusio/quarkus/commit/79d7ed54b396fc045c5313a8fecd0175209bcec7

Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[x] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

run tests

Helm related failures are really strange
10:45:03 Caused by: java.io.IOException: Cannot run program "helm" (in directory "target"): error=2, No such file or directory
10:45:03 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
10:45:03 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
10:45:03 	at io.quarkus.test.bootstrap.QuarkusHelmClient.runCli(QuarkusHelmClient.java:178)
10:45:03 	... 74 more
10:45:03 Caused by: java.io.IOException: error=2, No such file or directory


367 Use IA config for identification, fixed metadata error too

Pull Request Overview

IA config data used for Identification rather than hardcoding
metadata validation code duplication fixed
Tests updated to use valid algorithm for zebra

draft as this will depend on the outcome of DEX 234

LGTM

/rebase


Spark error checking

Logs success (info) or failure (warn) of all (that can be done) Spark MAX settings - ramp rate, PID controls, soft limits, etc.
Resolves #55

I think it's better to make the call, and only report if unsuccessful as best practice (also assuming the happy path leaves the logs uncluttered ... and they are getting full). It also seems like we aren't printing the error value if it does fail.  I'm going merge the pull request, but not delete the branch. Let me look a bit before I decide.


[BUG] exit() calls std::exit() instead of raising a SystemExit

Bug description
When calling exit() in Python code, it will immediately exit the parent process instead of throwing a SystemExit like CPython. This is a problem for in-game scripting because it gives the user an opportunity to inadvertently crash the game.
Steps to reproduce
VM* vm = new VM();
try {
    vm->exec("exit(42)");
} catch (const pkpy::Exception &e) {
    print("Whoopsie")
}
print("This happens after the VM exits.")

The program will terminate with exit code 42 without printing any additional messages.
Environment information
main branch, OS is not relevant.
Additional context
It is possible to override this behavior by rebinding the exit() function as follows:
bind(builtins, "exit(code=0)", [](pkpy::VM* vm, pkpy::ArgsView args) {
    // Do something here
    return vm->None;
});

I'd be happy to contribute a fix as follows:

Define a SystemExit exception and make the exit(code=0) Python function raise it.
The void exit() function should catch the SystemExit exception and use std::exit for compatibility. (Alternatively we could break backwards compatibility because this behavior is unlikely to be used in anything but trivial examples.)
Add a new int exec_with_return_code() function which returns the exit code as intended.
When calling _exec on a CodeObject_, the returned pkpy::PyVar should contain an integer with the exit code.

Please let me know if you want me to work on this.

I don't want to change this. If you are unhappy about default "exit", we recommend you to delete/replace it.


optimize:add independent nacos for the CI process.

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
fixes: 6832
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

貌似可以了，让我们等待ci的最终运行结果。
It looks like it's working now. Let's wait for the final CI results.

登记完pr信息后，CI流程又失败了。 DefaultCoreForEventBusTest.test:124 NullPointer

这个问题跟你这个pr无关，不用担心

Thank you for your contributions to Seata. If possible, please send your Dingtalk contact information to my email, and I will invite you to join the Seata developer group.
<EMAIL_ADDRESS>


Missing Nepal

Oddly we seem to be missing Nepal from ne_50m_admin_0_boundary_lines_land. It is not missing from our ne_10m nor our ne_110m downloads. The original file from Natural Earth does have it, as verified in qgis.

Here is what the corresponding Natural Earth shapefile looks like in QGIS:

This seems like it is fixed in v0.6.1 (tested locally). Can we try clearing the cache in demo.tegola.io for zooms 3 and 4 to see if that fixes this there?

I'm doing some work on the server right now and this fits right in.

@PetersonGIS, I've installed v0.6.1 for the osm/demo project and regenerated the zoom level 3 & 4 tiles but don't see any difference. The data you're looking at is pulled from the server or a local copy?

Interesting. I was pulling from a local copy, which was originally from that data though. I'll dig deeper to further look at the data differences as well as the toml and json differences that there might be between my local setup and what's on the demo.

My suspicion would be that there's a difference in the .toml. Nepal is in _disputed?

I was wrong, it isn't fixed locally. I was looking at ne.ne_50m_admin_0_countries rather than ne_50m_admin_0_boundary_lines_land. Nepal is still missing in ne_50m_admin_0_boundary_lines_land when served by tegola but not missing if we look at ne_50m_admin_0_boundary_lines_land in qgis.

Verified there are 361 rows in ne_50m_admin_0_boundary_lines_land as reported in both qgis and local natural earth db. Suspect 361 in our ne cloud db too. So something is making it not render though it is there in the db? It is a fully enclosed line, does that make a difference to the renderer?

Missing these fully enclosed lines in the ne_50m_admin_0_boundary_lines_land data too.

@PetersonGIS turn simplification off for that layer locally. I have a feeling that polygon is getting removed during simplification. Simplification might not be necessary for those layers too since they're already simplified.

@ARolek that was the solution!
[[maps.layers]] 	name = "boundary_lines_land" 	provider_layer = "ne.ne_50m_admin_0_boundary_lines_land" 	dont_simplify = true 	min_zoom = 3 	max_zoom = 4

@PetersonGIS beautiful! PR has been merged. Time to close this one out ;-)


Tables Inside Borders Problem

Sorry for my English and my programming level, I'm very new
I'm submitting a ...  (check one with "x")
[X] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see

**Current behavior** and **Expected behavior**

Some time ago I downloaded from the primeng page the expandable tables function, and it worked in a separate project. But now that I want to add it to a project that I'm working on, and it doesn't work properly. I can't see the borders of the table, if I add borders to the table  only see the outside ones, but the inside ones its impossible whatever i do.

 and how it looks in the project I want to insert.

https://image.prntscr.com/image/vRqjNHgJQkaXJhR8hEVWFg.png
[https://image.prntscr.com/image/vRqjNHgJQkaXJhR8hEVWFg.png](url)

I tried to load the plunker but I don't think I did it correctly.

Thank you so much for everything.

**Please tell us about your environment:**
<!-- Windows 10 64 bits, Visual Studio Code, Localhost, ... -->

* **Angular version:** 2.0.X
<!-- Check whether this is still an issue in the most recent Angular version -->

* **PrimeNG version:**  "4.2.0-rc.1",

* **Browser:** [Firefox 55.0.3 (32-bits)]

* **Language:** [all]

* **Node (for AoT issues):** `node --version` =  6.11.3

Hey dude. This is not PrimeNg. You need to go here

Thank you @ManpreetSingh80 i dont know why i put here, but i have a problem with the smart tables ng2 admin.