proxy: add tests for batch http sql

Problem
This PR adds an integration test case for batch HTTP SQL endpoint. https://github.com/neondatabase/neon/pull/4654/ should be merged first before we land this PR.
Summary of changes
Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

the only change is https://github.com/neondatabase/neon/pull/4793/commits/32f595bad64bc2f56c2f4bc9322989bf888b06f9

a little change for the endpoint format: returning a JSON array in REST API is prune to some attacks, and therefore it's changed to a json object of { "result": [xxxx] } instead. https://github.com/neondatabase/neon/pull/4793/commits/dd555b942b4a9dc2754f37bb8cca091357f91461


physics_bone_joint_fix is failing checks

Issue description
https://github.com/V-Sekai/godot/tree/physics_bone_joint_fix is failing checks
Some checks were not successful 11 failing and 2 successful checks.
Steps to reproduce
Build the engine on github actions.
Minimal reproduction project (For SDK or engine issues)
None
Using a released version?
No
What OS? Any other relevant information? (V-Sekai version, Godot revision, System information)
Windows 11, V-Sekai Godot Game, Vulkan Nvidia 3000

Resolved as of https://github.com/V-Sekai/godot/tree/groups-4.x at dfe91ac79cde65162296f80a1ad6036a9d7a5a20


Gradlew build fails: app.notifee.core.ForegroundService, was not found in the project or the libraries [MissingClass]

I am setting up my application to use the microphone during the foreground execution.
<service
        android:name="app.notifee.core.ForegroundService"
        android:foregroundServiceType="microphone" />

But when I try to run:
./gradlew :app:build
I am receiving the following error message:
...android/app/src/main/AndroidManifest.xml:45: Error: Class referenced in the manifest, app.notifee.core.ForegroundService, was not found in the project or the libraries [MissingClass]
          android:name="app.notifee.core.ForegroundService"
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 Explanation for issues of type "MissingClass":
 If a class is referenced in the manifest or in a layout file, it must also
 exist in the project (or in one of the libraries included by the project.
 This check helps uncover typos in registration names, or attempts to rename
 or move classes without updating the XML references properly.

Can anyone give me a hint on this issue?

I am experiencing this issue as well, and have not found a solution for it.


"Args should each be on their own line" error happening when it shouldn't

Getting the two errors seen below. Bug might stem from arguments of the inner function are being required to be on their own line.
export default DragDropContext(HTML5Backend)(     //Args should each be on their own line (args on start line): DragDropContext(...)
	DropTarget(NativeTypes.FILE, specObj, collectFunc)(   //Args should each be on their own line (args on start line): DropTarget(...)
		connect(
			state => ({dirtyState: state.get('dirtyState')}),
			{
				addDirtyState,
				removeDirtyState
			}
		)(PostBase)
	)
);

I looked into it briefly and from what I can tell, the getLinesFn isn't returning the correct information when there is more than one nesting of a function.
this seems to pass
firstFn(arg1)(
     secondFn(arg2)
)

this does not pass
firstFn(arg1)(
     secondFn(arg2)(
          thirdFn()
     )
)

Thanks for debugging all of this Bryce :)
I'll also take a look and see what I can find out.

Thanks Bryce, there were some errors with the argument parsing. I've gone ahead and fixed it with 9866f0d.
If you run npm install -g check-source-formatting@next you should be good to go.
Thanks again!


OCM-12347 | ci: fix id:60688

fixed case id: 60688

It cannot use the registryConfig file which is not in the shared directory.
In afterEach step, it needs to specify the region to delete the oidc-config

Logs on local is https://privatebin.corp.redhat.com/?244971df16e30548#4s1rWZkXX38swr2GGsoKneLQpe4etutfbtryRwzJxYmE

/lgtm


Enable the includeInboundPorts to specify an empty string

Fix https://github.com/istio/istio/issues/54288

Hi @TatsuyaHayashino. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test

@TatsuyaHayashino: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@TatsuyaHayashino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test gencheck

unit-tests-arm64_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@TatsuyaHayashino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test gencheck

unit-tests-arm64_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests-arm64

unit-tests_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@TatsuyaHayashino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests-arm64

unit-tests_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests

gencheck_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@TatsuyaHayashino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
b4751ea0d7085deacd859040a1da0993f3677ec1
link
true
/test unit-tests

gencheck_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test gencheck

unit-tests-arm64_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@TatsuyaHayashino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test gencheck

unit-tests-arm64_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test unit-tests-arm64

unit-tests_istio
fd8a44d18eea68a3009b0b3433a3d50825a18e5b
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

The golden files have not been updated.
I attempted to update data-snapshot.tar.gz using run_update_golden_snapshot.sh, but encountered errors unrelated to the current changes when running make gen.


Fix trailing tabs in comments.

Hi,
please accept the following pull request:

First added a minimal .editorconfig to not destroy your formatting
Fixed trailing tabs in comments if using tabs as indent-style in your editor
Updated to a newer babel version, otherwise building on Windows 8.1 failed with "Don't hotlink internal Babel files" (see http://stackoverflow.com/questions/31062714/react-native-error-dont-hotlink-internal-babel-files)

Thx.

@stefanwalther Thank you for this PR :smile:
Please check my comments.

All your comments included. thx.


feat(TypeParser): add project property

Codecov Report

Merging #61 (0a44323) into main (86c5766) will increase coverage by 0.45%.
The diff coverage is 78.92%.

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   59.90%   60.35%   +0.45%
==========================================
  Files          50       50
  Lines        6015     6568     +553
  Branches       73       73
==========================================
+ Hits         3603     3964     +361
- Misses       2372     2564     +192
  Partials       40       40

Impacted Files
Coverage Δ

src/lib/structures/ConstantParser.ts
56.11% <0.00%> (ø)

src/lib/structures/TypeAliasParser.ts
55.79% <0.00%> (ø)

src/lib/structures/class-parser/ClassParser.ts
53.20% <0.00%> (ø)

...lib/structures/class-parser/ClassPropertyParser.ts
49.07% <0.00%> (ø)

...c/lib/structures/enum-parser/EnumPropertyParser.ts
58.74% <0.00%> (ø)

...ctures/interface-parser/InterfacePropertyParser.ts
57.43% <0.00%> (ø)

src/lib/structures/misc/ParameterParser.ts
55.88% <0.00%> (ø)

src/lib/structures/misc/SignatureParser.ts
53.73% <0.00%> (ø)

src/lib/structures/misc/TypeParameterParser.ts
55.69% <0.00%> (ø)

src/lib/structures/type-parsers/ArrayTypeParser.ts
65.88% <70.00%> (-5.33%)
:arrow_down:

... and 40 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


FR: Multiple Servers Usage Mode (Round-Robin)

Right now I'm observing a random usage of the configured servers. I have only 2 servers and I expected a round-robin mode of usage for the tests, instead it seems random:

So right now it's random by design (reference to code below). So you're looking for test A, next time test B, then A etc.?
https://github.com/alexjustesen/speedtest-tracker/blob/98cf390ac2e6fff8ada7dbb352569d8e12de8143/app/Jobs/SearchForSpeedtests.php#L26

Yes, round-robin. If there are 3 servers: 1, 2, 3 and repeat the cycle from 1.

No problem, nothing urgent.
fail-over I think should not be mutually exclusive to the rest. I mean, if I select round-robin or random, and a server fails, I would prefer ST to skip to the next one.

My two pennies worth.  Fail over shouldn't be an option.  If there is an issue it should fail safe and perform a test on something else.   The next item on a list or if none then another list of reliable servers.

I agree, and it's exactly what I meant in my previous post when I said it shouldn't be mutually exclusive.

+1 on the round-robin approach & the failover! :)
Also if ServerA is unreachable for any reason, then yes, attempting a speed test against ServerB should take place. eg...

Test 1: SevrerA - OK!
Test 2: SevrerB - OK!
Test 3: SevrerA - BAD... Changing target to ServerB - OK!
Test 4: SevrerA - OK!
Test 5: SevrerB - OK!
... and so on.

Can we also do all of them?
I'm very interested in tracking my speed from my server to multiple locations, there are many use cases for this. Then in the dashboard I can view the result of my locations that I chose. That would be awesome.


Add ZipCode Controller and Tests

Added ZipCode Controller and Tests.
In this PR, we add an endpoint /api/zipcode/get that can be used to get information
about the location of a particular zipcode.
dev deployment: http://team01-livjono-dev.dokku-03.cs.ucsb.edu/

Closes #17

LGTM


UltraNest support

Would you be interested to add support for https://johannesbuchner.github.io/UltraNest/ ?
The interface should be very similar to pymultinest.
UltraNest is a very reliable tuning-parameter-free algorithm. I have published some examples where the UltraNest algorithm is unbiased while pymultinest gives a different answer. UltraNest is a pure-python package and very easy to install with pip or conda.
UltraNest also supports resuming from disk and MPI parallelisation, if that is useful to you.

Hi! I came across your work in the literature and I am quite interested in alternative sampling approaches beyond static Nested Sampling in MultiNest.
I currently wrap MultiNest's C API directly with Cython (see pyx and pxd). This is done principally for performance reasons to avoid Python overhead at various levels. My initial tests using Dynesty showed that this was actually a significant run-time cost, at least for this application of spectral cube model fitting. So at this stage changes to the sampler would be non-trivial to implement, but I would very much like to re-evaluate alternative samplers like UltraNest and Dynesty in the future!


PagingData.map not found

Hey! 👋🏻
Thanks for the library :). It's super useful.
PagingData is not exposing any map function so it's quite difficult to map items inside.
Thanks! 🙇🏻

Hi! Did you import the map function with import app.cash.paging.map?

Hey @veyndan! Thanks for your answer. That was exactly the problem.
The library is a bit hard to use because of #5. The import was not suggested by the IDE.
Thank you!


Some livemarks not refreshing automatically

Add-on version
Add-on version: 2.6
Describe the bug
Some of my feeds (e.g. [1], [2]) are not automatically refreshing as expected while others do (e.g. [3], [4]). Manual refreshing works.
To Reproduce
Steps to reproduce the behavior:
Go to pages [1] and [2] and add livefeeds for them (to bookmarks toolbar).
Expected behavior
Automatic refreshing for all feeds after configured refresh interval (for me 5 minutes).
Extra context
[1] https://taz.de
[2] https://twitrss.me/twitter_user_to_rss/?user=anna_cavazzini
[3] http://newsfeed.zeit.de/index
[4] https://netzpolitik.org/feed

Do you see any errors in the Browser Console ?

Do you see any errors in the Browser Console ?

I don't know what you mean. If I open the console with Shift+F5 I can only see messages concerning the currently opened webpage.

https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

I was surveying a bit, but I couldn't see any messages concerning the livemarks.


Cart Recollection

Sometimes errors happen that cause the cart to disappear (never to return).
If we cash the session id (from cookie), we can force Bandcamp to reload it.
In the future this might mean a dropdown of previous carts (could be an issue if you've already paid for everything) or at least store the last cart and provide a way to access that history.
Exporting might be interesting too as long as the session id isn't responsible for user verification in some way (don't want to be sharing logged in sessions)

Sometimes session generation is done using browser fingerprinting and generating a hash of several variables, like the username or timestamp or browser user agent. Sometimes apps will invalidate sessions if one of these variables changes when regenerating a hash.
Might be worth testing this to see if BC will invalidate session when these things change - an easy way to test might be to paste a session from Chrome into Firefox to see if it reloads a cart.

@emcniece just checked loading a session_id from Chrome in Firefox. No issue at all.

not going to implement


feat(charts): Support Rancher Catalog (#130)

Refference

Rancher Overview
Catalogs and Apps
Creating Custom Catalogs Apps

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)

#130

[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

Closes #130

@dexter-mh-lee Thank you.
I don't think that all variables in values.yml need to be able to be changed from the GUI.
For example, the Image repository can be changed from the GUI because we sometimes use Private Registry, but the Image tag input field was removed in the following commit because it is operated to be changed by the developer when the Chart is released.
b894723
If users want to change the values in more detail, Rancher has the feature to edit the YAML file directly.
I think it is better to set items in questions.yml that are commonly changed, and edit questions.yml only when such items are newly added.

@dexter-mh-lee
Could you review it?

ping

hi @eburairu thanks for the contribution, but we feel the team doesn't have the capacity to keep these files updated and provide maintenance.
couldn't this part of a separate community driven repo maintained by you?


Install default-jdk with jenkins

After bringing up the instance the jenkins service fails because there's no associated jdk.
This adds (currently) openjdk 1.8.0 to the install.

Can we get a merge on this @edinc ?

Sorry it took a while @seryl @jondkelley


default template not parsing v2.4

Using v2.4, template files aren't being parsed. I stripped everything down to this:
const webpack = require('webpack');
const HtmlWebpackPlugin = require('html-webpack-plugin')

const config = {
  entry: './source/index.js',
  output: {
    path: 'build',
    filename: 'bundle.js'
  },
  plugins: [
    new HtmlWebpackPlugin({
      template: 'source/default.html'
    })
  ]
};

module.exports = config;

Where source/default.html is just a copy of the default template.
Building this does not parse the template, the output index.html file is just a copy of the default template with the bundle.js script tag injected at the end.  If new HtmlWebpackPlugin is used without a template, the default appears to be parsing correctly.
Am I missing a step or is this a bug?

I grabbed the wrong file (master branch). The correct default index template is a lodash template and renders correctly with the above config.

Just in case someone else gets tripped up by this, the default template link from features/loaders points to the file in master, so it's easy to accidentally slip between branches and end up looking at the wrong file.

@joemaller thx fixed it in https://github.com/ampedandwired/html-webpack-plugin/commit/fd415c047ce8b969db1672fcc4f971912b5c7093


DOCS-11761-v24functionDocBuild-UNEDITED-duke DO NOT MERGE

SHOWING ORIGINAL DIFF that introduces new v2.4 function module build PRIOR TO ANY EDITS

Replaced by https://github.com/mulesoft/docs-dataweave/pull/27.


Linter system

proposal for #532
Linters in Azure repo are becoming a mess. All linters try to make their own tiny linter engine to seperate rules into their own compartment but gets none of the benefits of a centralized linter engine. The other issue is testing linter rules is a mess, every linter rules being enabled at once cause the test to be containing a lot of noise to suppress the other linter rules.
This is a tentative change that introduce @cadl-lang/lint a library providing a centralized linter where a library can register linter rules and decide to enable some from other linters.
Goal of this to solve:

More defined linter solution
Ability to enable a rule from another library helping with reusability

This will enable having a best practice library that contains a lot of rules but doesn't enable any.

Better way to test(can test a single rule at once)

Linter engine in use change in cadl-azure https://github.com/Azure/cadl-azure/pull/2018
Todo:

[x] Provide testing helper testRule

Other potential features:

Tighter connection with diagnostic: A linter rule name must be the name of the diagnostic it will be emitting.

Alternative: Built-in
Alternatively is to also have this built-in the compiler itself.

onValidate validate that the spec is valid. e.g. Validate that there is no duplicate operation path
linter rule provide some good practice validation but without the spec would still be valid.

I think this looks great and is ready to go.  @markcowl, any thoughts about the pattern being used here?  Check out the cadl-azure side PR too: https://github.com/Azure/cadl-azure/pull/2018


Update Readme.md to reflect latest version

The Readme.md has some outdated information and wrong description about using outside repositories instead of the repo in the FOSSASIA org.

hi, I am new to open source. I was looking at some good first issues. Can I work on this?


deploying angular 6 app with telerik kendo ui for angular

<Please be sure to remove any private information before submitting.>
Repro steps:
<Enter steps to reproduce issue>
Action: appService.Deploy
Error type: Error
Error Message:

Microsoft Azure Web App - Error 404

@aangeles77 are you using a custom domain? Did you get a chance to look at the FAQ listed here: https://blogs.msdn.microsoft.com/appserviceteam/2017/08/08/faq-app-service-domain-preview-and-custom-domains/

Closing due to lack of response. Feel free to re-open with more info


In Connection.php

I get this when I try to run  php artisan litepieweb:install :
In Connection.php line 664:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'blog.menus' does
n't exist (SQL: select * from menus where name = admin limit 1)
In PDOConnection.php line 79:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'blog.menus' does
n't exist
In PDOConnection.php line 77:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'blog.menus' does
n't exist

i have the same probleme
please have you solve your ?


Remove 'internal subscription on same subject' feature

This is to remove subscription reference counting and replicating of messages on the same subject rather than subscribing to the subject again going to the server with a new SID.
This would also include making sure we don't leak subject objects in case user code not disposing them. We don't want subscription manager to keep a reference to subject objects keeping them alive even though user code abandoned it.

I'm curious, what were the reasons for removing the reference counting approach?
Does this result in extra overhead, in cases where we have a number of subscriptions to the same subject on a client? i.e. if a client has 3 subscriptions with different SIDs to the same subject, will the server send three separate messages?

@to11mtm I removed the ref counting because it was used to maintain 'in-memory' subscriptions feature, as far as I understood. The decision for removing this in-memory subscription feature had a few reasons:
(1) NATS protocol is designed to handle multiple subscription to the same subject from the same client connections since they would have different SIDs. This is a very important concept to support variety of different messaging patterns where the subject may convey information other than a destination. JetStream for example takes advantage of this a lot.
(2) I wanted to expose the protocol to the user as low level as possible at the core NATS level since JetStream and other APIs will be built on top
(3) If this functionality is required, it could be implemented by the user of this API or as an extension e.g. relying on the channel of NatSub
(4) Simplification in general
(5) It's not actually always saving server resource (i.e. sending a message more than once) without the knowledge of subject semantics. For example if there is a subscription to A.* and A.B messages sent to A.B would be sent twice. - I realise this may not be a good argument against it but just wanted to highlight the fact anyway.
I hope that makes sense.
Was this something you were relying on?

A big reason was also supporting Subscription Options.  There are many new options in NatsSubOpts - options that configure timeouts, server-tracked UNSUB, and support using different Serializers.
The Inbox Subscription is actually a Mux Subscription now under the covers - which is actually a little different.  It listens on a single wildcard such as _INBOX.abcd.> and delivers all of the inbox messages to the proper inboxes.

I appreciate the background, those definitely all make a lot of sense! Especially for cases like JetStream where you really can't do these sorts of things.

Was this something you were relying on?

A project I am working with was using AlterNATS, and due to some of the patterns we were using it was pretty helpful for our use case.
All of that said, I certainly agree that it could be done as an extension on NatsSub or via some other shim class to track refcounts across the connection.
Thank you again for the information!


feat: new realMouseWheel command

add support for mouse wheel scroll

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Shooting system 2D and 3D

Is your feature request related to a problem? Please describe.
I want a package to use for a shoot mechanic so that i can implement it to my project if needed. I prefer if it supports 2D and 3D projects. this speeds up the process of setting it up.
Describe the solution you'd like
A 2D and 3D version of the following mechanics with adjustable settings:

use/shoot
aim
alternate fire
reload

Describe alternatives you've considered
it might be more practical if there are options to turn the features on or off. Think for example if there is no reload or alternate fire in the game. It will also be handy to keep in mind the different types of ways the player can aim. for example in first person or third person.
it might also be convenient to use the newer input system so that you can use a input map for the controls.
Additional context
separating the 2 and 3D versions and the scripts can help for keeping it organized.

@Kazuma-47 I'm happy to say I will make your suggestion into a feature. In the release 1.0.0 it will be there.


k8s deploy server,client receive error response

Bug Description
when i deploy application new server version,Error: rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection failure
Version
istioctl version:1.4.5
kubectl version:1.13.3

Additional Information
this is yaml
kind: VirtualService
apiVersion: networking.istio.io/v1alpha3
metadata:
  name: go-server-grpc-local-service
  namespace: xxx-app
  selfLink: >-
    /apis/networking.istio.io/v1alpha3/namespaces/xxx-app/virtualservices/go-server-grpc-local-service
  uid: dd8796d9-0f00-11ec-9694-18c04d317f73
  resourceVersion: '2238193'
  generation: 8
  creationTimestamp: '2021-09-06T10:54:53Z'
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: >
      {"apiVersion":"networking.istio.io/v1alpha3","kind":"VirtualService","metadata":{"annotations":{},"name":"go-server-grpc-local-service","namespace":"xxx-app"},"spec":{"hosts":["go-server-grpc-local-service.xxx-app.svc.cluster.local"],"http":[{"route":[{"destination":{"host":"go-server-grpc-local-service.xxx-app.svc.cluster.local"}}]}]}}
spec:
  hosts:
    - go-server-grpc-local-service.xxx-app.svc.cluster.local
  http:
    - retries:
        attempts: 3
        perTryTimeout: 3s
        retryOn: reset,connect-failure,cancelled,deadline-exceeded,internal,resource-exhausted,unavailable
      route:
        - destination:
            host: go-server-grpc-local-service.xxx-app.svc.cluster.local

this is k8s apply command:
istioctl kube-inject -f go-server-grpc-local-service.yaml | kubectl apply -f -

Istio 1.4 has been EOLd for almost 2 years. Please upgrade and reopen if you still experience issues. See https://istio.io/latest/news/support/announcing-1.4-eol-final/. Thanks!


[WIP] Add swift-foundation to toolchain build

This is a WIP PR to add the swift-foundation set of projects to the toolchain build for use by swift-corelibs-foundation

https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-corelibs-foundation/pull/4948
https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-corelibs-foundation/pull/4948
https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-corelibs-foundation/pull/4948/files
https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-corelibs-foundation/pull/4948
https://github.com/apple/swift-foundation-icu/pull/22
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/377
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/378
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/378
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/378
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/379
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please build toolchain linux platform

https://github.com/apple/swift-collections/pull/379
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please clean build toolchain linux platform

https://github.com/apple/swift-collections/pull/379
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please clean build toolchain linux platform

https://github.com/apple/swift-collections/pull/379
https://github.com/apple/swift-foundation-icu/pull/22
https://github.com/apple/swift-foundation/pull/573
https://github.com/apple/swift-corelibs-foundation/pull/4959
@swift-ci please clean build toolchain linux platform


[Question] What is the estimated release date of v1.2.2 in npm?

What is the estimated release date of v1.2.2 in npm?

@dclaux / @matthidinger ?

As I looked into the release tag v1.2.2 I noticed only a few pull requests that, I think, affects the JS payload, they are the follow:
#3169
#3407
#3350
Even though they are in short number, these PRs provide bug fixes that improve dialog flow and UX.
So I believe that users and developers would benefit from this release.

@jodufra, we'll be getting the npm packages updated as part of our upcoming Sept patch targeted for end of this month. Thanks.

Also the changelists you mention are actually still in master and have not been pushed out in previous releases at all at this time.

@jodufra, we'll be getting the npm packages updated as part of our upcoming Sept patch targeted for end of this month. Thanks.

Thank you


Add GDS Session documentation

 [🍓] Client documentation

@nvitucci Thanks a lot for the review! I've applied most of your suggestions.

@nvitucci Thank you for the very comprehensive and useful review. Unless you tell me otherwise, I will consider the contents here approved and aim to merge ASAP, and then publish these (in preview).

@nvitucci Thank you for the very comprehensive and useful review. Unless you tell me otherwise, I will consider the contents here approved and aim to merge ASAP, and then publish these (in preview).

Absolutely, go for it.


Crop images and all images on Guides should show in a lightbox when clicked

This has been done for Guide images.  In a guide (for a crop) there's an image at the top left corner, is that the one you're talking about?

No, talking about the ones on the left side of the crop pages (the big
cover image and the smaller ones underneath)
On Mon, Aug 15, 2016, 10:31 AM Taneea S Agrawaal<EMAIL_ADDRESS>wrote:

@roryaronson https://github.com/roryaronson @simonv3
https://github.com/simonv3 Crop images where? In a guide (for a crop)
there's an image at the top left corner, is that the one you're talking
about?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openfarmcc/OpenFarm/issues/534#issuecomment-239869064,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRKS4r1gzbmyFLr1IIAajugMvu8EtGkks5qgKJ4gaJpZM4Dsw5a
.

--

Rory

A lightbox in this context is something like this: http://fancyapps.com/fancybox/
We're using angular-foundations modal pop up to achieve the same thing without having to use a new library.
We have a directive that is a wrapper around this, use it like this:
https://github.com/openfarmcc/OpenFarm/blob/master/app/assets/javascripts/angular-libs/guides/show/guides.show.stage-action.template.html#L15
The directive is defined here:
https://github.com/openfarmcc/OpenFarm/blob/master/app/assets/javascripts/angular-libs/angular.of.directives.lightbox-modal.js
@TanSA05 Let me know if that makes sense! It should be pretty easy to add the link.


Modal hard fails in IE 11

Bug Report
Steps
Create a Modal and set the open property to true.  Open using IE 11 (I'm specifically using 11.1088.15063.0 to reproduce).
Expected Result
The modal opens.
Actual Result
Hard crash.  TypeError: Assignment to read-only properties is not allowed in strict mode.
Version
0.81.0
Testcase
https://codesandbox.io/s/py44qm940

I should note this is a new issue in v0.81.

Looks like this is the portal bug in #2886.  Fixed by #2880.  Closing as duplicate.

I still got this issue


ENSO characteristics notebooks

Working on completing the ENSO characteristics metrics, adding dive down levels
added some more dive downs maps

[x] working on #6
[x] checking #16

OK Great Work! I am going to merge this one for now as I have changed quite a few things.


sparse weights decompression: do not balance oc_block for this feature

@EgorDuplensky

fix was included here https://github.com/openvinotoolkit/openvino/pull/15918


Missing documentation on ExecuteQueryV2Async

This page references a "ExecuteQueryV2Async" as a way that will fix the problem when making these queries from code. But that method appears to be 100% undocumented anywhere.

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

ID: 082142f3-9558-d472-c85b-459b956480a1
Version Independent ID: 3beb35b6-5885-9367-9fc0-2c4fe6b7b824
Content: Query limits - Azure Data Explorer
Content Source: data-explorer/kusto/concepts/querylimits.md
Service: data-explorer
GitHub Login: @shsagir
Microsoft Alias: shsagir

It is also a very confusing API, so using it correctly is incredibly difficult.  I've had to just start slapping "notruncation" on a lot of my queries because I don't know how to use the progressive mode, and that's presumably not ideal for my cluster.

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

@ChadNedzlek Thanks for your feedback. We've submitted a documentation change based on your suggestion, and the updated article should be live by tomorrow. Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.
#please-close


Reproducibilty considerations and tweaks

from #164, we suffer a bit that

the ubuntu docker container is not reproducible per-se
we use apt update leading to a random set of installed packages

To solve these issue, thanks to @h01ger we have some improvements (that should be done to (a) build-with-docker.sh and (b) builds.robur.coop):

use a reproducible (debian) container from https://hub.docker.com/_/debian
use a package snapshot (e.g. http://snapshot.notset.fr/archive/debian/20220523T033231Z/ instead of https://deb.debian.org/ for your apt sources.list) NB: snapshot.notset.fr will soon (tm) also be available as under snapshot.reproducible-builds.org but we are not there yet

We could as well use orb in the GitHub action runner and collect/upload the build information.

Done with #175.


Not compatible with PyCharm 2022.1

Plugin is no longer compatible or usable for the new version of PyCharm 2022.1

Thanks @autoferrit , I'll look into it

I am having the issue in https://github.com/dubreuia/python-inlay-hints-plugin/issues/3 as well. Any updates on getting these fixed?

It is a newer version than the original issue
I've looked into it last week, but I'm having trouble building the plugin with new versions. I'll try to fix this week

All it takes to at least run the plugin in the sandbox is as such:
diff --git a/build.gradle.kts b/build.gradle.kts
index e487e2a..cbcc714 100644
--- a/build.gradle.kts
+++ b/build.gradle.kts
@@ -10,7 +10,7 @@ plugins {
     // Kotlin support
     id("org.jetbrains.kotlin.jvm") version "1.6.0"
     // Gradle IntelliJ Plugin
-    id("org.jetbrains.intellij") version "1.3.0"
+    id("org.jetbrains.intellij") version "1.6.0"
     // Gradle Changelog Plugin
     id("org.jetbrains.changelog") version "1.3.1"
     // Gradle Qodana Plugin
diff --git a/gradle.properties b/gradle.properties
index 7e9f557..08410f1 100644
--- a/gradle.properties
+++ b/gradle.properties
@@ -9,11 +9,11 @@ pluginVersion = 1.0.1
 # See https://plugins.jetbrains.com/docs/intellij/build-number-ranges.html
 # for insight into build numbers and IntelliJ Platform versions.
 pluginSinceBuild = 203
-pluginUntilBuild = 221.*
+pluginUntilBuild = 222.*

-# IntelliJ Platform Properties -> https://github.com/JetBrains/gradle-intellij-plugin#intellij-platform-properties
+# IntelliJ Platform Properties -> https://plugins.jetbrains.com/docs/intellij/tools-gradle-intellij-plugin.html#intellij-extension
 platformType = PC
-platformVersion = 2020.3.4
+platformVersion = 2022.2.1
 downloadSources = false

 # Plugin Dependencies -> https://plugins.jetbrains.com/docs/intellij/plugin-dependencies.html

I haven't tested with anything older than 2022.2.1, but I guess you've got the CI infrastructure set up to do that yourself :)

All it takes to at least run the plugin in the sandbox is as such:

Thanks for code @agatti!

but I guess you've got the CI infrastructure set up to do that yourself :)

lol you greatly overestimate my super scrappy setup

Sorry I'm so slow thanks for the wait fixed in https://github.com/dubreuia/python-inlay-hints-plugin/releases/tag/v1.1.0 will release on jetbrains marketplace


HTML report on instrumented code

We used istanbul instrumenter to instrument all our source code before production. While its running in production, it will collect the coverage object and periodically post it to a node.js server.
In the node.js server we use Istanbul reporter to derive HTML reports out of the coverage object. But the report is constructed on instrumented code. Can the reporter remove the istanbul instrumentation?
Or how is it possible for me to introduce instrumentation in the original code and derive a HTML report which will show me the coverage in the un-instrumented JS code?

Are you instrumenting the code in place (overwriting I mean). If your original sources are in say src/ and you instrument them into src-instrumented/ then the coverage object will have correct paths and use the correct files for the HTML report (assuming the files under src/ are still available at report generation).

Reopen if this doesn't answer your question


Confusing Readme

Hello, I'm slightly confused as to what functionality does this codebase actually provide. Following the readme, the result (at least the one I arrived to) has nothing to do with what you see in the demo. So my question is:
Does this just provide bare-bones functionality for a system that needs custom implementation or, is this supposed to ship with some sort of UI resembling the demo?
In case of the latter, then I'm clearly doing something wrong. Otherwise, I feel like the Readme could provide a bit of clarification on how to implement this functionality.
I believe the case is the latter as the demo folder is way more complex than the engine one.
I case of doubt, my result after just following the read-me is just a div with text and a type error when trying to drag it.
Thank you very much,
Have  a good one.

Hey, the demo is simply a preview of what the engine can do. As explained in the ReadMe, you can design the blocks however you want, and it works the same way, connecting with the arrows and with all the same functionality. I didn't ship it together with a UI as I wanted the engine to be extremely minimal and to allow it to be extremely versatile.
As per the demo folder being "way more complex" it's mostly because I created a "fake UI" to showcase the kind of product that could be built with the engine, the flowchart part though is incredibly simple and lightweight.
If you think it would be good to have a version that comes with a simple UI that can be customized I could also do that, maybe as a starter project that people can edit.

Hey @alyssaxuu, Ok, so I managed to get it working, I had to add styles because I was getting confused of where things were and type error was because js was loading before content.
I still find it confusing to understand the boundaries of the canvas and where the dropping zone starts and ends.
Yes! I think a version with default UI would be great! Though I now understand how this is supposed to work. I wouldn't default to a starter kit, but maybe a set of components that could be inserted at will (say, a dropping zone with default styles, a block component a sidebar/block list component, etc) but, that's just my opinion.
Anyway, thank you very much for promptly clarifying my concerns! :)

If you think it would be good to have a version that comes with a simple UI that can be customized I could also do that, maybe as a starter project that people can edit.

Perhaps adding a js edit-in-place might make for a better demo so that people could adjust to their frame of context.


fix #6093, inject should not be merged with Object.create

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ x When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
fix https://github.com/vuejs/vue/issues/6093
Object.create is not adding 'own property' to the object, which caused injections not injected properly.😭

Thanks for the PR.
Actually there's no need to add another merge strategy function, it's an issue about using Object.keys() to iterate inject object while using for...in on other options. (Object.keys() will not enumerates properties in the prototype chain, but for...in does).
So my suggestion is:
strats.props =
strats.methods =
strats.inject =
strats.computed = function (parentVal: ?Object, childVal: ?Object): ?Object {
  if (!parentVal) return childVal
  const ret = Object.create(null)
  extend(ret, parentVal)
  if (childVal) extend(ret, childVal)
  return ret
}

Just delete this line will fix #6093 :
if (!childVal) return Object.create(parentVal || null)

@javoski You are right, I did think about that too. But I just didn't have the confident to remove that line directly. (I was afraid it's using Object.create for a reason)
Anyway, If it works totally OK without Object.create, it's better to merge your PR, and feel free to close this one when merging it.

Thanks, #6093 seems to be a simpler fix.


Windows Memcached with Django, report [warn] select: No error

I'm using django with memcached store realtime data maybe reset key-value per 1min , however sometimes memcached will crash with problem "[warn] select: No error", and then django will miss getting data from memcached. how can i fix it?

sorry we don't support the a windows version of memcached. if you want to use it, try from the WSL.


minor: allow feedback email to be configured via JSON

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Please also include any acceptance criteria if you have any.
Currently the feedback banner returns empty if the feedback object is empty.

allow feedback.email to be configured (via JSON only)

accepts any valid email
then appends mailto: for the banner

No integration with the designer for now, since that page already has a bug which prevents any saves occurring (schema validation fails) #293.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce
the testing if necessary.
Before PR's can be merged they will need to be tested by QA and approved where
applicable. To flag the change to QA assign @XGovFormBuilder/qa as one of the reviewers.

[x] Unit
[x] manual

Checklist:

[x] My changes do not introduce any new linting errors
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation and versioning
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have rebased onto main and there are no code conflicts
[n/a] I have checked deployments are working in all environments
[x] I have updated the architecture diagrams as per Contribute.md

I guess this is partly a bug fix as well..
FEEDBACK_LINK env variable isn't used for form level anymore. The feedback object in the JSON allows you to this though. If feedback.url isn't a relative URL it will throw an error (I tried that first), so I added feedback.email so we can do the right validation on it


rm const do inline

https://github.com/go-gitea/gitea/pull/30876/files#r1637288202

well If we inline it ... we later can not use them easily in code as we do e.g. with  db.SearchOrderByOldest
the idea was to have them here similar to the db generic order consts
cc @lunny what do you thing ...
I'm personally aganst merging this ...

well If we inline it ... we later can not use them easily in code as we do e.g. with db.SearchOrderByOldest
the idea was to have them here similar to the db generic order consts
cc @lunny what do you thing ...
I'm personally aganst merging this ...

I think it's better to extract variables/functions until it will be used by other places.

@6543 please update the branch


POSIX compliance

shebang changed from bash to sh
replaced bash for loops with POSIX adjacent
replaced echo with printf

I noted that the bell echo produced an extra newline, I assumed this wasn't intentional behavior.


Add unified sentiment analysis based on UIE.

PR types

New features
PR changes

Others
Description

Add unified sentiment analysis based on UIE.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark:<PHONE_NUMBER>:x: tianxintianxin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Put Serv.Api.Analysis in a better location

Right now it's just sort of attached to serv vestigially and because it seemed like a better place to put it than in serv-wai. Honestly, serv-wai is essentially the only user in the near term although this sort of thing might be taken to a whole new level with something like serv-swagger.
If it can be factored out of serv then we can lose text and containers as deps, too, so that's sort of nice. Not that they aren't being pulled in transitively by http-kinder, though.

If nothing else it shouldn't be in the public API!


add working step for line parallel to given line and pass thru givn point under coordinate geo calc

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
i wud like ot work on this

Go ahead
Deadline 25 May,2021


Rerun jobs

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

What is wrong? Have you tried restarting the CIs?

Have restarted the CIs on the feedstock.  Please let me know if that is not the case.

@jakirkham ok, I wanted to make sure.

Of course. Thanks for letting me know.

@jakirkham, it's weird, the linux worker got a timeout when testing (running swig -help)

Looks like it failed when starting tests to me. 😕
In any event, restarted again and it appears to have worked this last time.


Appearance of white squares in vs code

Issue Type: Bug
In vs code, white squares periodically appear in different parts of the window. After some time of work, these white pieces no longer appear. But if you close and reopen vs code, the white shapes reappear.

VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

Merging to https://github.com/microsoft/vscode/issues/154910


stack string default is not prompted if boolean

variables:
  gf_allow_sign_up:
    type: string
    default: "false"
    from:
      prompt:

prompts with default "false"
variables:
  gf_allow_sign_up:
    type: string
    default: false
    from:
      prompt:

prompts without default.
bug or "yaml feature" ?

(examples identical)
false without quotes will get converted to boolean by yaml.

@kke whooops, now edited.

So my point is: it's kinda misleading that type: string is not enough and requires additional as: string. ?

String does not have as anyway.
I think opto's string type handler should really have a to_s sanitizer.
sanitizer :to_s do |value|
  value.nil? ? nil : value.to_s
end

YES!


icebram: Found some bitslices up to 1 times, others only 0 times!

I like to initialize memory and subsitute it after synthesis by instrumenting icebram
reg [31:0] rom_memory [0:1023];

`ifdef SIMULATION
    initial $readmemh("mem_increment.hex", rom_memory);
`else
    initial $readmemh("mem_random.hex", rom_memory);
`endif

The following command issues an error
icebram mem_random.hex mem_increment.hex < build/$(PROJECT).asc > build/$(PROJECT)_reprogrammed.asc

and here is the error
Found some bitslices up to 1 times, others only 0 times!

How should I proceed?

Meanwhile I figured out, that yosys or how I instrument it might be responsible for my finding with icebram

5.8. Executing MEMORY_BRAM pass (mapping $mem cells to block memories).
Processing rom_top.rom_wb_inst.rom_memory:
Properties: ports=1 bits=32768 rports=1 wports=0 dbits=32 abits=10 words=1024
Checking rule #1 for bram type $__ICE40_RAM4K_M0 (variant 1):
Bram geometry: abits=8 dbits=16 wports=0 rports=0
Estimated number of duplicates for more read ports: dups=1
Metrics for $__ICE40_RAM4K_M0: awaste=0 dwaste=0 bwaste=0 waste=0 efficiency=100
Rule #1 for bram type $__ICE40_RAM4K_M0 (variant 1) accepted.
Mapping to bram type $__ICE40_RAM4K_M0 (variant 1):
Read port #0 is in clock domain \clk.
Mapped to bram port A1.1.
Updated properties: dups=1 waste=0 efficiency=100
Storing for later selection.
Checking rule #2 for bram type $__ICE40_RAM4K_M123 (variant 1):
Bram geometry: abits=9 dbits=8 wports=0 rports=0
Estimated number of duplicates for more read ports: dups=1
Metrics for $__ICE40_RAM4K_M123: awaste=0 dwaste=0 bwaste=0 waste=0 efficiency=100
Rule #2 for bram type $__ICE40_RAM4K_M123 (variant 1) accepted.
Mapping to bram type $__ICE40_RAM4K_M123 (variant 1):
Read port #0 is in clock domain \clk.
Mapped to bram port A1.1.
Updated properties: dups=1 waste=0 efficiency=100
Storing for later selection.
Checking rule #2 for bram type $__ICE40_RAM4K_M123 (variant 2):
Bram geometry: abits=10 dbits=4 wports=0 rports=0
Estimated number of duplicates for more read ports: dups=1
Metrics for $__ICE40_RAM4K_M123: awaste=0 dwaste=0 bwaste=0 waste=0 efficiency=100
Rule #2 for bram type $__ICE40_RAM4K_M123 (variant 2) accepted.
Mapping to bram type $__ICE40_RAM4K_M123 (variant 2):
Read port #0 is in clock domain \clk.
Mapped to bram port A1.1.
Updated properties: dups=1 waste=0 efficiency=100
Storing for later selection.
Checking rule #2 for bram type $__ICE40_RAM4K_M123 (variant 3):
Bram geometry: abits=11 dbits=2 wports=0 rports=0
Estimated number of duplicates for more read ports: dups=1
Metrics for $__ICE40_RAM4K_M123: awaste=1024 dwaste=0 bwaste=2048 waste=2048 efficiency=50
Rule #2 for bram type $__ICE40_RAM4K_M123 (variant 3) accepted.
Mapping to bram type $__ICE40_RAM4K_M123 (variant 3):
Read port #0 is in clock domain \clk.
Mapped to bram port A1.1.
Updated properties: dups=1 waste=2048 efficiency=50
Storing for later selection.
Selecting best of 4 rules:
Efficiency for rule 2.3: efficiency=50, cells=16, acells=1
Efficiency for rule 2.2: efficiency=100, cells=8, acells=1
Efficiency for rule 2.1: efficiency=100, cells=8, acells=2
Efficiency for rule 1.1: efficiency=100, cells=8, acells=4
Selected rule 2.2 with efficiency 100.
Mapping to bram type $__ICE40_RAM4K_M123 (variant 2):
Read port #0 is in clock domain \clk.
Mapped to bram port A1.1.
Creating $__ICE40_RAM4K_M123 cell at grid position <0 0 0>: rom_wb_inst.rom_memory.0.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <1 0 0>: rom_wb_inst.rom_memory.1.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <2 0 0>: rom_wb_inst.rom_memory.2.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <3 0 0>: rom_wb_inst.rom_memory.3.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <4 0 0>: rom_wb_inst.rom_memory.4.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <5 0 0>: rom_wb_inst.rom_memory.5.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <6 0 0>: rom_wb_inst.rom_memory.6.0.0
Creating $__ICE40_RAM4K_M123 cell at grid position <7 0 0>: rom_wb_inst.rom_memory.7.0.0

But finally, only a single SB_RAM40_4K  is used, not 8.

=== rom_top ===
Number of wires:                 23
Number of wire bits:            264
Number of public wires:          16
Number of public wire bits:     149
Number of memories:               0
Number of memory bits:            0
Number of processes:              0
Number of cells:                 51
SB_CARRY                        8
SB_DFF                         16
SB_DFFSR                        1
SB_LFOSC                        1
SB_LUT4                        24
SB_RAM40_4K                     1

As you can see,  the following instances are removed by the optimizer

5.10.4. Executing OPT_CLEAN pass (remove unused cells and wires).
Finding unused cells or wires in module \rom_top..
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.6.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.5.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.4.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.1.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.3.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.2.0.0'.
removing unused \SB_RAM40_4K' cell \rom_wb_inst.rom_memory.7.0.0'.

As mentioned, Yosys is removing some RAM instances for optimization purpose. That is absolutely in line with the behavioral model. When I really make use of all the data in RAM, not optimization is performed and I can instrument icebram as anticipated.
Problem solved!


Delay on Streaming

am facing 15sec delay when running from IIS, is there any way to reduce the delay?

Are you using HLS?
If you use OBS studio to publish the stream, it should be better if you set keyframe interval to 1s.
Also the player-side buffer affects the delay a lot.

@josephnhtam
yes am using HLS, grabbing desktop screen using ffmpeg and viewing on VLC. After made changes on ffmpeg command now its working with minimal delay. Thanks.


[Feature][Question] Add builtin_standard for the minetest lua api

I'd like to add a builtin_standard for the minetest lua api (see: https://github.com/minetest/minetest/blob/master/doc/lua_api.md)
Similar to: https://github.com/lunarmodules/luacheck/blob/master/src/luacheck/builtin_standards/love.lua
Give me a :+1: and i open a PR for it.

Sure, this sounds reasonable.
The only catch will be that after you get a PR working to your satisfaction I'll want to see some testing. Since I don't have any involvement in minetest, one other party that actually uses minetest and can verify your PR would be useful, and/or you can setup CI checks on public code somewhere using GH actions so we can see it in action.


Fix bug where wrong NFT shows when visiting URL

Issue: When visiting a URL with ?developerId the traits were always the same (Developer 1's traits).
This fix reloads the Traits when visiting the URL.
Fixes #52

@briangershon Thanks so much for this fix 👏  Appreciate it!


ORCID link not rendering

The icon is showing up, but now id

The link is visible and functional for Castro, Hart and Merz. Leaving open for @wrenaria to approve visuals.


onApiAvailable method name mistype-fix

onApiAvaliable -> onApiAvailable 👍
https://github.com/gribnoysup/react-yandex-maps/blob/c9b17f7a0b94bb63e82214e9c5e2619a38d22eae/src/YMaps.js#L11

Hi @dmtttvn, thank you for your PR!
Unfortunately, this is a breaking change and was already fixed in the next branch (see #44). There is still much work to do before next will be released, this is why it is not in the master yet. But still, thank you for the effort!


Mouse remains hovered on a moving widget

This affects all widgets, and basically the known position of the mouse will only change on mouse movement.  So if several widgets are moving around, any changes to their placement below the mouse would not be registered until the mouse is moved.

color picking - (-) This would require a second render to a buffer.  (+) This technique could eliminate the need for complex mouse coordinate transforms and collision detection on nested transforms. (+) It would be pixel-perfect. (+/-) Also, could render a 'color picking' bitmap at 1/2 size since precision does not need to be pixel perfect.
always updating - update the mouse coordinates on every frame rather than on every mouse move. (-) Seems a bit unnecessary to check all the time. (-) Not performance optimal. (+) Simplest solution.
leave the system as is - (-) not working out
always updating when objects are moving - Could update the mouse coordinates only when an object is moving.  This seems unnecessarily complex.  Something would need to keep track of objects that are moving, and/or possibly provide btrees.
provide a refresh mouse position option - (-) would require responsibility on the part of the widgets. (+)

Issue https://github.com/MarkOates/allegro_flare/issues/48 relates to option 1.

This issue now also affects UIWidget's local_mouse_x and local_mouse_y, which will return the "older" local coordinates.  The position of the local mouse coordinates are only refreshed during mouse movement.

UI widgets are being depreciated in this migration, so this task is no longer planned for any development.


Add Control+Back, Control+Delete bindings to default config

Bound to delete-to-word-begin, delete-to-word-end as for example in VS Code.

I thought some terminals actually implemented this behaviour apart form VS Code's internal terminal, but I just checked again and you are right. I will just have to keep this in my personal config then.

@jplatte This is usually done in the .bashrc/.bash_profile (or whatever configuration your shell might be using). It's possible that VS Code's internal terminal comes with a non-default config.

@chrisduerr: VS Code's internal terminal sends the same escape codes that I added in this PR. (checked with showkey - a)


Update CI Unit Tests Workflow

Signed-off-by: Michael Gasch<EMAIL_ADDRESS>

Codecov Report
Base: 95.83% // Head: 95.83% // No change to project coverage :thumbsup:

Coverage data is based on head (0986ee5) compared to base (251dbe7).
Patch has no changes to coverable lines.

:exclamation: Current head 0986ee5 differs from pull request most recent head 304ddfb. Consider uploading reports for the commit 304ddfb to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #178   +/-   ##
=======================================
  Coverage   95.83%   95.83%
=======================================
  Files          17       17
  Lines        2067     2067
=======================================
  Hits         1981     1981
  Misses         62       62
  Partials       24       24

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

TODO:

[ ] Update branch protection rules to use the updated unit test name

@timbray rebased onto #179 and did three runs, all successful: https://github.com/timbray/quamina/actions/runs/3973740675/usage

Update: I made some more modifications, trying to run the TestRuler tests together with the regular unit tests. To my surprise, it works. See both runs: https://github.com/timbray/quamina/actions/runs/3974871446
We still have to run cover separately due to issues with the race detector it seems (tests still time out/get terminated).
But even in the cover target, I run TestRuler tests (-tags=fromRuler) and they work.
Perhaps we don't need the build tags anymore then?
(disclosure: I updated CI to use Go 1.19, which might have a positive effect here too)

Um, if you're running them all together and now it works, that has to be go 1.19, right? Unless something else changed?
But if you're convinced that the build tags are no longer necessary, feel free to pull them out as part of this  PR.
Hmm, it's now 9:19AM Pacific time and it looks like the unit tests are somehow blocked from finishing? Looks like 3 hours since last commit?

It also occurs to me that I would like to steal a lot more tests from Ruler in the future. Maybe that is an argument for giving them their own spot in the matrix?

Um, if you're running them all together and now it works, that has to be go 1.19, right? Unless something else changed?

It worked with v1.18 too (just used latest in last commit). Not sure what else changed, happy it works :)

But if you're convinced that the build tags are no longer necessary, feel free to pull them out as part of this PR.

Yup.

Hmm, it's now 9:19AM Pacific time and it looks like the unit tests are somehow blocked from finishing? Looks like 3 hours since last commit?

Please change this in branch protection rules (new workflow run name). Might have to wait until this is merged.

It also occurs to me that I would like to steal a lot more tests from Ruler in the future. Maybe that is an argument for giving them their own spot in the matrix?

Not sure that's an argument tbh.

If you're going to remove the build tags, maybe flip the func names back in those two files? Along the lines of
s/^func TestRuler/func Test/
Or I could just roll back #179 since it seems to be useless now.

Actually I like the naming as it indicates Ruler-related tests, no?

Actually I like the naming as it indicates Ruler-related tests, no?

OK, not fussy.  So, LGTM. I wonder why the problem went away?

Oh, still seeing a not-signed problem :(

Oh, still seeing a not-signed problem :(

Haven't added ssh signing. Shall I or merge?

Oh, still seeing a not-signed problem :(

Haven't added ssh signing. Shall I or merge?

Go ahead. But let's please set up signing post-1.0?

Oh, still seeing a not-signed problem :(

Haven't added ssh signing. Shall I or merge?

Go ahead. But let's please set up signing post-1.0?

Go ahead and merge, I meant.


Fix spacing when the license lozenge collapses in responsive mode.

Fixes #293

What a very complicated PR 😂 I told you it was one line of CSS @finestructure 👍


UDP Support for reading bytes from more sockets at the same time

Hi, i've used this library for UDP protocol and, first of all, it's very very good!! There is only one problem that is the loss of packets every 2-3 minuts. I'm using an Ethernet 10 GB. I used UDP Sample with receive buffer of 65504 bytes and segment count 512. Can you help me???? Thanks!!!!

Hello,
Sorry for not answering sooner, for some reason this issue didn't show up under notifications..
It's hard to say given that information, but perhaps the buffer space is running out? there could also be some other issue with the library itself, I've been meaning to update it to use spans but I haven't gotten around to it yet


all: fix and enable more of gometalinter

We now have gometalinter enabled on travis:
https://github.com/google/syzkaller/blob/master/.gometalinter.json
However, not all checkers are enabled and some errors are suppressed. We should gradually enable more checks/errors.
If you want to work on this, please first discuss the plan here or on the mailing list. Potentially we don't want to enable all of the checks.

What remains:

we may want to enable errcheck, but it currently produces 280 warnings
we may want to enable vetshadow, perhaps with err variables ignored (brings down number of warnings from 92 to 16)
strengthen dupl limit
strengthen gocyclo limit

The rest of the checkers does not look interesting.

Status update:

vetshadow is enabled with err variables ignores
dupl limit is lowered slightly, below that it produces lots of semi-false-positive warnings, so I think we are done here
gocyclo limit is lowered, but I think we need to lower it more

What remains:

we may want to enable errcheck, but it currently produces 280 warnings
strengthen gocyclo limit more


Oday slideshow

Added pictures to create a slideshow for Guild O-Day 2023 on the events page.

Make sure you remove DS Store files.


Fix #76519 - Implmented resolveTask for jake

Follow the gulp extention change b6089b1db51dbfb7b096a829261a0b3b9370d6e5 to implement resolveTask for jake (#76519)

Looks good, thank you!


Fix comment format to what doxygen expects by adding an asterisk

Multi-line comments need to start with /** instead of /* for the public API doc comments to show up in the doxygen generated docs.

How did  this get checked-in to master and past the previous CI runs?
I am guessing that because we weren't using correctly formatted docs, the comment/parameter name validation wasn't running.
I am glad we caught this :)
/Users/runner/runners/2.166.4/work/1/s/sdk/core/core/inc/az_json.h:341:11: error: parameter 'out_token' not found in the function declaration [-Werror,-Wdocumentation]
 * @param out_token A pointer to an az_json_token containing the next parsed JSON token.
          ^~~~~~~~~
/Users/runner/runners/2.166.4/work/1/s/sdk/core/core/inc/az_json.h:341:11: note: did you mean 'token'?
 * @param out_token A pointer to an az_json_token containing the next parsed JSON token.
          ^~~~~~~~~
          token


Support for background workers/multithread applications

Adding a control into a usercontrol which gets called from a background worker gives cross-thread exceptions due to non-thread safe methods it seems, perhaps I could modify the methods for thread safety, but I couldn't find the code for VB .Net in the repository.

The UI shouldn't be modified from a thread other than the main thread. Perhaps you're not invoking correctly? (quickly googled a VB.Net example on the subject)
If that's not the case, let me know.
PS: MaterialSkin is written solely in c#. Since both c# and VB.Net compile to CIL (Common Intermediate Language), the library can be used for both.

Thanks for the info.
As far as I am aware my invoke methods are working correctly (due to I use them to add other user controls) and it only throws the exception on the one that contains an element from MaterialSkin (in this case, I was testing with a radiobutton).

I see. Could you perhaps post some more information:

The exception message
The code where the exception gets thrown

That would make it easier to see what's going wrong.


How can i have moving background images like musica.ly have on their app ?

Its not a bug.

Is this a bug report?
(write your answer here)

Have you read the Contributing Guidelines?
(Write your answer here.)
Environment

Steps to Reproduce

(Write your steps here:)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

As the contribution template says, we kindly ask that GitHub issues are kept to bug reports and core development:

We use GitHub Issues exclusively for tracking bugs in React Native. If you're looking for help, the Community page at http://facebook.github.io/react-native/support.html list various resources  that should help you get started.

In this case, Reactiflux Chat and Stack Overflow are the best places to ask others, and the Components and APIs docs also cover functionality that might work for you.


Ido/theme

changed all components to use a single project main CSS
demo page use main theme

add diagnostics to build

set project interface / commons file

set default theme

load default theme in demo

fix: #83 - removed global from components CSS


Arbitration standard with appeal funding at the Arbitrator level

(Was just testing the flow of the new Github project beta)


Attribute extraction task support & benchmarking

https://docs.google.com/document/d/1yKuPHMVfhbO0z5DqCCnbLTRI7Y7uY-t6Wv98zMH_Y7A/edit


ConditionalProxyMiddleware throws when publicPath is absolute

When setting the { output:  { publicPath: 'http://localhost:5000" }} in webpack.config it results in:
System.ArgumentException: The path in 'value' must start with '/'. Parameter name: value    at Microsoft.AspNetCore.Http.PathString..ctor(String value)    at Microsoft.AspNetCore.Http.PathString.op_Implicit(String s)    at Microsoft.AspNetCore.SpaServices.Webpack.ConditionalProxyMiddleware.<Invoke>d__5.MoveNext()
This is needed as a workaround to gets custom fonts working in dev-environment. See: http://stackoverflow.com/questions/34133808/webpack-ots-parsing-error-loading-fonts/34133809#34133809

It seems pretty dubious to hard-code localhost:5000 into your webpack.config.js, but I understand this is to workaround an issue in file-loader.
I'd be happy to take a pull request that implements this. I'd recommend you modify WebpackDevMiddleware.ts so that, when it passes the PublicPath value to .NET (after the comment // Tell the ASP.NET app what addresses we're listening on, so that it can proxy requests here), it first converts the URL to a root-relative one (if it was an absolute one).
I'll close this so you can submit a separate pull request if you want to.


[performance] Use PureComponent instead of Component when extending StyledComponent

If PureComponent is used instead of Component when extending StyledComponent in native-base-shoutem-theme, we may experience improvements in performance.
file: node_modules/native-base-shoutem-theme/src/connectStyle.js:106
react-native, react and native-base version
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Note: I cannot find native-base-shoutem-theme repository and create issue here

@smmoosavi Using PureComponent doesn't make any difference.
You can try and send PR if you find a solution here


Error while trying to use raspi GPIO

Getting this "nrpgio python command not running" in the debug window while trying to use GPIO in a flow

GPIO cant be supported in the add-on until https://github.com/home-assistant/hassio/issues/432 is addressed in hassio.  You'll need to let Home Assistant manage GPIO for now.

got it! thanks


Json for postgres

Summary
Fix handling of some transactions whose JSON encoding would fail to be received by PostgreSQL. Emit stricter JSON, keys are strings, strings are utf8 or base64
Test Plan
Tested against test data from go-algorand e2e test scripts (including new data added there to exercise this condition).

Indexer mostly doesn't use the json encoding of the txn. A few specific fields are used in filters but they aren't affected by this change. The value side of fields was already base64, just the key strings needed fixup.

Indexer mostly doesn't use the json encoding of the txn. A few specific fields are used in filters but they aren't affected by this change. The value side of fields was already base64, just the key strings needed fixup.

Indexer mostly doesn't use the json encoding of the txn. A few specific fields are used in filters but they aren't affected by this change. The value side of fields was already base64, just the key strings needed fixup.

I meant that when a new block is being received and applied, you need to decode the old keys since these might need to get overridden by the new ones. ( i.e. the old one is the b64('key') whereas the new one just just the key )

Indexer mostly doesn't use the json encoding of the txn. A few specific fields are used in filters but they aren't affected by this change. The value side of fields was already base64, just the key strings needed fixup.

I meant that when a new block is being received and applied, you need to decode the old keys since these might need to get overridden by the new ones. ( i.e. the old one is the b64('key') whereas the new one just just the key )


DaemonSet not working

I must be doing something wrong, but for the life of me I can't figure out what.
I'm modifying service per pod to work with DameonSets (with services named after the nodes they are operated on).
This isnt my first rodeo with metacontroller (but I'm also no expert).
Getting an error:
{"level":"error","ts":1642734404.4067523,"logger":"controller.decorator-metacontroller","msg":"Reconciler error","name":"service-per-pod-daemonset","namespace":"","error":"can't find resource \"DaemonSets\" in apiVersion \"apps/v1\"","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.3/pkg/internal/controller/controller.go:227"}

It has me scratching my head, this is not where I expected to get stuck. Some sort of CRD issue? Any help would be apreciated.

Looks like metacontroller does not hand the standard camel case for DaemonSets working only for daemonsets

OK found the documentation. it's non stanadard but documented.
The canonical, lowercase, plural name of the parent resource. (e.g. deployments, replicasets, statefulsets)


[question] multiplication by zero

https://github.com/hill-a/stable-baselines/blob/06f5843a3254ab7c2f6c927792e00365a778009e/stable_baselines/common/distributions.py#L239
I dont fully understand what this line does but it seems that a multiplication by zero is done. It is either unnecessary or wrong.

Sorry in advance for any trouble I might have caused anyone, I answered myself : In order to concat the mean and the logstd, mean and logstd have to share the same shape. But the shape of mean isn't known in advance (it has shape (?,n) where n is the dimention of the action space). So the multiplication by zero trick is used to align the two shapes.
I do belive that this trick does the job, but it seems to me like is is more a trick rather than clean code. In fact, mean and logstd are "de-concatenated" right then in DiagGaussianProbabilityDistribution.init. I would mabe like to see a cleaner implementation of this in the futur...
(For anyone maintaining this repo, and taking the time to read both my posts, thank you.)


Introduce customized HTML elements, fix incorrect AppUrl usages in templates

This PR follows:

#21986
#22831

This PR also introduce customized HTML elements, which would also help problems like:

#17760
#21429
#21440

With customized HTML elements, there won't be any load-search-replace operations, and it can avoid page flicking (which @silverwind cares a lot).
Browser support: https://developer.mozilla.org/en-US/docs/Web/API/Window/customElements
FAQ
Why the component has the prefix?
As usual, I would strongly suggest to add prefixes for our own/private names. The dedicated prefix will avoid conflicts in the future, and it makes it easier to introduce various 3rd components, like GitHub's relative-time component. If there is no prefix, it's impossible to introduce another public component with the same name in the future.
Why the custcomp.js is loaded before HTML body? The index.js is after HTML body.
Customized components must be registered before the content loading. Otherwise there would be still some flicking.
custcomp.js should have its own dependencies and should be very light, so it won't affect the page loading time too much.
Why use data-url attribute but not use the textContent?
According to the standard, the connectedCallback occurs on the tag-opening moment. The element's children are not ready yet.
Why not use {{.GuessCurrentOrigin $.ctx ...}} to let backend decide the absolute URL?
It's difficult for backend to guess the correct protocol(scheme) correctly with zero configuration. Generating the absolute URL from frontend can guarantee that the URL is 100% correct -- since the user is visiting it.
Screenshot

Codecov Report

Merging #22861 (00c49ba) into main (51ab495) will decrease coverage by 0.01%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main   #22861      +/-   ##
==========================================
- Coverage   47.35%   47.34%   -0.01%
==========================================
  Files        1113     1113
  Lines      150176   150176
==========================================
- Hits        71109    71105       -4
- Misses      70635    70643       +8
+ Partials     8432     8428       -4

Impacted Files
Coverage Δ

modules/util/timer.go
85.71% <0.00%> (-14.29%)
:arrow_down:

services/pull/update.go
43.41% <0.00%> (-3.88%)
:arrow_down:

services/pull/comment.go
62.96% <0.00%> (-2.78%)
:arrow_down:

services/pull/temp_repo.go
43.22% <0.00%> (-2.59%)
:arrow_down:

models/unit/unit.go
50.79% <0.00%> (-1.59%)
:arrow_down:

services/pull/pull.go
43.67% <0.00%> (-0.48%)
:arrow_down:

routers/api/v1/repo/pull.go
49.71% <0.00%> (+0.16%)
:arrow_up:

services/pull/check.go
29.29% <0.00%> (+1.17%)
:arrow_up:

models/asymkey/gpg_key_common.go
56.57% <0.00%> (+3.94%)
:arrow_up:

modules/indexer/stats/indexer.go
57.44% <0.00%> (+6.38%)
:arrow_up:

... and 1 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

How do browsers handle the case where a custom element is to be rendered but the script the registers it has not fetched yet? Will it render invisible?

Seems to be treated like a div.

Thought I guess because the <script> is in <head>, browsers might actually treat it as render-blocking, eliminating the issue.

Quote some questions together:

How do browsers handle the case where a custom element is to be rendered but the script which registers it has not fetched yet? Will it render invisible?

Seems to be treated like a div.

Yes, for any undefined tag, they are treated like a div, also have the display:block by default.

Thought I guess because the

@silverwind any more question?


Having trouble downloading kali linux on chromebook

Hello, so I've downloaded multiple Linux distros onto my Chromebook before but i have never encountered any issues like this. so i typed
sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce
and everything was normal until the downloads stopped, i typed
sudo startxfce4
and i was met with the issue
UID 1000 not found in kali-rolling
Can anyone help?

This is a duplicate of the yet unresolve issue #3930, please see https://github.com/dnschneid/crouton/issues/3930#issuecomment-437167573 for more details.
-DennisLfromGA


Translate interpolated strings to JavaScript

This will for sure end up being a template string in JavaScript. I'm thinking about using template strings for strings in general to support multiline strings as well.

Instead of using template strings, I'm using string concatenation instead.


Facing issues when trying to build DGPU driver image via KMM on OKD ie. Openshift upstream

Hello Team,
We are working on the On-premise Build Mode approach via KMM to build DGPU driver image documented in below github link as we are using a 6.x kernel version with OKD.
[https://github.com/intel/intel-technology-enabling-for-openshift/tree/main/kmmo#managing-intel-dgpu-driver-with-kmm-operator]
using On-premise Build Mode
Prior to using this mode, run the following commands to create a ConfigMap and include the dockerfile to build the driver container image:
$ git clone https://github.com/intel/intel-data-center-gpu-driver-for-openshift.git && cd intel-data-center-GPU-driver-for-openshift/docker

$oc create -n openshift-kmm configmap intel-dgpu-dockerfile-configmap --from-file=dockerfile=intel-dgpu-driver.Dockerfile

To use this mode, run the following command:

$ oc apply -f https://github.com/intel/intel-technology-enabling-for-openshift/blob/main/kmmo/intel-dgpu-on-premise-build-mode.yaml

Herein we have slight changes made in the configmap as driver toolkit is not available for OKD & we have build a custom image.  Build is getting triggered & we are seeing below error(snippet below)
Also sharing the complete logs of the build pod for the analysis, require the team support take it up forward.
Turn off this advice by setting config variable advice.detachedHead to false

Generating local configuration database from kernel ...Kernel version parse failed!
make: *** [Makefile:45: olddefconfig] Error 1
error: build error: error building at STEP "RUN git clone ...odules_install": error while running runtime: exit status 2
[intel-dgpu-on-premise-build-mode-build-5mc65-undefined.log](https://github.com/intel/intel-technology-enabling-for-openshift/files/11845798/intel-dgpu-on-premise-build-mode-build-5mc65-undefined.log)

@qbarrand @ybettan could you have a look at this from KMM upstream for OKD support?
This project only deals with OpenShift, and we have no OKD environment.
Thanks!

Linking in the slack conversation:  https://kubernetes.slack.com/archives/C037RE58RED/p1686313602229529
As noted in the discussion, KMM is not supported on OKD.  It is supported upstream in Kubernetes and downstream in OpenShift.  Expectations should be set for minimal best effort for OKD.  Higher level of support is available upstream in the KMM community and downstream with OpenShift.

The DGPU Driver team may not have the backports of the 915 driver for your version of the kernel (6.0.18-200.fc36.x86_64).
Please check with the maintainers of this project: https://github.com/intel-gpu/intel-gpu-i915-backports


Added .DS_STORE to template .gitignores

Added .DS_STORE to all the relevant templates' .gitignore. This might need to changed to **/.DS_Store if they pop up in deeper directories, but hopefully not!
This came about when I tried using the Vercel template and found quite a few .DS_STORE(s): https://github.com/nialldbarber/ndb-remix

Looks like this would address #811.

The root-level gitignore .DS_Store entry will cover all sub-level ds_stores too. I checked on my monorepo, there's no need for **/.DS_Store. On other hand, this PR won't solve #811 but we're going to the right direction. 👍


Add multimedia/document support

Add media attachments field and if populated inject documents per each provider's protocol with exception for Mistral.

Nascent Media support added in 0.0.3


[move-lang] Fix interface generator for 'friend'

Fixed syntax for friends in interface generation

Motivation

Fix for #8403

Test Plan

Verified fix works
It will be run on every test after #8403 lands, but we should think about a dedicated test

/land


Have Msg store text in a queue and spit out a chunk on each loop to avoid freezing Reaper

Added qMsg and printQMsg so scripts can do this manually as needed.


Version of CIFAR to run the example

I cloned the code and tried to run it, but now the issue is - which version of CIFAR10 are you use in example? No data was downloaded automatically by the code. No python neither matlab or C++ version from official cite seems to be suitable for paths presented in the config file. Thank you for your answer.

Hi, we use the default python version (which is the same as torchvision.CIFAR10).
In the config:

root_path is your datasets directory, where you put all your data
image_folder is the folder inside datasets, where cifar-10-batches-py exists (cifar-10-batches-py is the folder torchvision.CIFAR10 looks for as well)

Here is an example to fix your issue. First download the python version you mentioned, an unzip, you will get a cifar-10-batches-py directory.
Then create the following directory structure:
|- datasets/
|-- cifar10-data/
|---- cifar-10-batches-py/
In your config specify:
root_path: datasets/
image_folder: cifar10-data
I will update the README and configs to make this more clear.

I assume the python version was 3.8 since there are some operators as return *[self.dataset.transform(img) for _ in range(self.supervised_views)], target that are invalid in python 3.7 (The one that Google Colab uses)


swipper not work correct on safari browser

Swiper - 1.6.1
Safari - 11.3
macOS - 10.13.6
react - 15.5.4
On Safari i have this
safari
on chrome this
chrome
as you see, first 4 slides doesn't have style attribute which get 360px width and no have some classes, idk why. When i change width from 768, classes and style appears. And it's happens not always.
code below in pic
params
swiper

Any ideas? I'm didn't find any information about this problem. If you need more information please tell.

Hi @Dollar1610 , sorry for my late response. Please provide live demo from Copepen or Codesanbox.
Thank you


[Security] Upgrade the snakeyaml verion to 1.26

Signed-off-by: xiaolong.ran<EMAIL_ADDRESS>Fixes #7928
Motivation
As https://nvd.nist.gov/vuln/detail/CVE-2017-18640 said, the snakeyaml < 1.26
Modifications
In pulsar-functions model:

The snakeyaml 1.19 appears to be included from dependency on org.apache.pulsar:pulsar-functions-secrets:jar:2.6.1 based on included dependency of io.kubernetes:client-java-api:jar:2.0.0:compile Fixed in 9.0.2

The snakeyaml 1.16 appears to be included from the dependency on org.apache.pulsar:pulsar-functions-instance:jar:2.6.1 based on io.prometheus.jmx:collector:jar:0.12.0 Fixed in 0.13.0

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

cherry-picked to branch-2.6


Silent aim should be bindable to a key like regular aim

I suppose this is more of a feature request, but generally silent aim is bound to a key - e.g. Mouse 1 and only fires when the user presses the key. Otherwise the aimbot will fire randomly whenever the user aims at an enemy which is often undesirable.

Well, this is not the goal of this feature.
But more importantly I think we have to find the root cause of the "random fire". Like on my side it works perfectly. Are you using a resampling different to x1 in your graphics settings? Are you using other mods ? Perhaps one of them is interfering.

Apologies, I phrased that incorrectly. By "fire randomly" I mean that you have no control over the aimbot firing. If you have visible enemies in your FOV, it'll shoot at them. That's a trigger bot, not silent aim. Silent aim generally means that when you fire the gun, it'll shoot the bullets towards the enemy instead of changing the camera angles, but the player still has to trigger the actual shooting.
In terms of the code, silent aim would be to adjust the direction in the CreateShotPrefix function, but don't trigger the shooting automatically.


[Feature Req] Add image sharpen filter

Describe your suggested feature:
Add image sharpen filter in filters tab so users can have the option to enable it or disable it.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.

You marked this as "Completed" ? That is incorrect, you didn't add a sharpen filter. Did you mistake "completed" as "not planned" ?


No hot reload --desktop

Problem
No hot reload --desktop. Targeting the web works.
Steps To Reproduce
Create a cargo project, add dioxus and dioxus-desktop.
run:  dx  serve --platform desktop --hot-reload
update app render >div > string
#![allow(non_snake_case)]
// import the prelude to get access to the `rsx!` macro and the `Scope` and `Element` types
use dioxus::prelude::*;

fn main() {
    // launch the dioxus app in a webview
    dioxus_desktop::launch(App);
}

// define a component that renders a div with the text "Hello, world!"
fn App(cx: Scope) -> Element {
    cx.render(rsx! { div { "Hello, world!" } })
}

See terminal ERROR:
[ERROR] I/O Error: The process cannot access the file because it is being used by another process. (os error 32)

Expected behavior
Expected "Hello, world!" to hot reload change on save after changing the string
Environment:

Dioxus version: v0.4.0
Rust version: 1.71.1 (eb26296b5 2023-08-03)
OS info: Windows 11 pro
App platform: desktop

This looks like the same issue as https://github.com/DioxusLabs/dioxus/issues/1286. Closing this as a duplicate. You can follow that issue for updates 🙂


Tests with maxtasksperchild=1 are slow

Close #5494.

I left 267 tests (39.15 s)
I marked 112 slow tests (104.72 s)

jenkins, test this please.

Jenkins CI test (for commit 22f7e8d6c76a5e095032e5e2ae455f5ceb089f1f, target branch master) succeeded!

It seems tests with maxtasksperchild=10 are slow in AppVeyor.

LGTM!


Add support to Pipeline Controller to set the FHIR server username or password

Until #630 is implemented, the Pipeline Controller must be able to send FHIR queries to the server in addition to the JDBC connection. There's no way to set the HTTP basic auth username/password, so the controller only works if the server does not require authentication or happens to use the same default values.

Just saw #670 already fixed this. :)

PR #670 reduces the priority of this but we still need to be able to set FHIR-server username/password for the non-JDBC mode (which will be added soon after #494 is fixed). So reopening with a lower priority.

Note we have support for Basic-Auth username/password in the actual pipeline arguments here but we need to expose these in controller config as well. This is also related to #587 and we should address all auth related issues holistically.


how do i perform mysqldump?

how do i perform mysqldump?

you need to install mysql client at first, but later I will introduce https://github.com/pingcap/dumpling to replace mysqldump.


Smarthing_MyQ stop working

On Feb. 13, 2017 my Smartthing hub stopped opening my MyQ Camberlain Garage Door Opener.  A friend of mine has the same setup and his quit working about the same time.  I do not know if Smartthing did an update that broke the accessibility to the MyQ controller. The door does open using the MyQ Chamberlain app on my Android device.
Thanks you for your help (in advance)

This has been discontinued, but there is new "MyQ Lite" code that was built from copy-ninja's original work by @brbeaird.  I changed over to this new SmartApp and Handlers earlier this week and it's been working flawlessly.  Check out the updated post on the ST community and the GitHub code:
https://community.smartthings.com/t/release-myq-lite-door-and-light-control-for-liftmaster-chamberlain/49150
https://github.com/brbeaird/SmartThings_MyQ
Enjoy!

Sorry little off topic but I used to run the MyQ thru smartthings via IFTTT. I got the MyQ lite version to work but now I can't get ifttt to login to smartthings. Anyone else struggling?
Sent from my iPhone

On Feb 17, 2017, at 11:26 AM, jasonredmond<EMAIL_ADDRESS>wrote:
This has been discontinued, but there is new "MyQ Lite" code that was built from copy-ninja's original work by @brbeaird. I changed over to this new SmartApp and Handlers earlier this week and it's been working flawlessly. Check out the updated post on the ST community and the GitHub code:
https://community.smartthings.com/t/release-myq-lite-door-and-light-control-for-liftmaster-chamberlain/49150
https://github.com/brbeaird/SmartThings_MyQ
Enjoy!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks Jason.  The ST app is open and closing door now. However it is not seeing my sensor. I believe I followed your instructions closely.  however i am also sure I missed something.

If you're talking about the sensor that comes with the MyQ gateway, that won't work as SmartThings can't interact with it. You'll need a separate contact sensor.

OK thanks.  Any model or manufacturer your recommend?

I use the Ecolink tilt sensors myself. Cheap and reliable.

Ecolink tilt sensors worked perfectly for both my door and a friends.  Thanks you for your help


logging from main thread

@keybase/react-hackers
@strib

@chrisnojima thanks!  I just tried installed your build though, and it doesn't seem to work.  I started the app, and didn't find the "Installer check starting now" line in ~/Library/Logs/Keybase.app.log.  Then I shut down the app, and still couldn't find that line.  Am I checking for the right thing?

@strib updated

Oh thanks.  Though I was more concerned in general that logs aren't flushed when the app quits.  But this seems fine for the issue at hand, thanks.

@keybase/react-hackers @buoyad ptal so we can get this in to help debug the kbfs stuff