Android Studio won't build/launch Tutorial's Release variant

Need to confirm details, but it seems related to https://b.corp.google.com/issues/111118208
Seems like Android Studio doesn't want to create unsigned release builds of apps by default (or more specifically, unsigned builds of apps that aren't debuggable or profileable).
I don't think that we should just assign the debug key that we're using for Validation to it though, Tutorial is a reference app so we shouldn't providing reference code that uses an unprotected key to sign a release variant.
So what I'm thinking is I'll first standardize the key signing configuration in build-logic. Then, for all apps, I'll disable the default "Release" variant and replace it with a "TestRelease" variant that is signed with the same key.
This should be done with #435 to make sure everything works correctly.

Confirmed that this has not been fixed yet.


DSD-165 added new icons and enabled color selection

Fixes DSD-165
https://jira.nypl.org/browse/DSD-165
This PR does the following:

added three new icons: Error (solid and outlined), Speaker Notes
enabled icon color selection

Front End Review:

[ ] View the example in Storybook

@bigfishdesign13 The tests should run now.
In the last commit I made these changes:

Updated mocha test runner .extensions so it can ignore .svg files.
Cleaned up and returned the actual SVG react component from the SVG file import.
Updated how export and import was done in IconSvgs.tsx. It's not a big deal because the previous one would work but wanted to make it clearer what was being exported. Now, the default from each svg file is being exported rather than the "ReactComponent" or the "default" export. Export/import can be tricky.
Updated the tsconfig.json file because there were unnecessary files and directories in the include attribute. (I initially thought this was what was the problem for including the svg files).
Updated the webpack config but I should revisit that later.

Now I need to know what's left to do because

the ticket says to include the Alert and Speaker Notes svgs but I only see Speaker Notes here. In the changelog I see there it explicitly says it also includes "Error solid" and "Error outlined", but there are so many new SVGs that were added that are not in the changelog. I'm assuming the changelog just hasn't been updated. I can update it but just want to confirm that all the svgs in the "icons/svg/new" directory should be included. If so, they should just go in "icons/svg" without the "/new" subfolder (unless if there's something I don't know and we need this).
The Icon.stories.mdx file should be updated and I can do that. I think it'll be beneficial to include all svgs as a showcase along with mixes of new props in place.

Is there anything else I'm missing before I continue?

@bigfishdesign13  Alright, updated the mdx storybook page and fixed the directory of the new svg files. Almost all logo svgs are way too big and there's no size prop to display it correctly. This screenshots shows how they're cut off:

I noted that this is a work in progress. Either we remove these svgs or we merge this in and make a ticket to fix this issue later. What do you think? Easier to see in the deploy - https://deploy-preview-541--stoic-murdock-c7f044.netlify.app/

I updated the spacing variables. @hokei @wluisi can you both take a look at this PR? It's a blocker for other work.

Just for prettiness, can there be a bit of a padding around the icons in the storybook?


Use Yaml instead of JSON

What does this PR do?
JSON return unicode strings under Python2, even if this is a better
behavior it would be a breaking change compare to the previous version
of the Agent not using this lib to embed Python. Yaml returns bytes
under Python2 and Unicode under Python3. Since JSON is a subset of Yaml
we use 'yaml' here.

Will be merged as part of https://github.com/DataDog/datadog-agent/pull/3468


Circuit breaker does not work for interservice calls

I am trying to apply the Circuit Breaker for interservice calls that go through the Feign Client. Looked at the official documentation. Specifically https://istio.io/latest/docs/ops/common-problems/network-issues/, and can't seem to get the effect to work for interservice calls. Tell me, please, maybe somewhere it is described in detail how to handle this situation. Thank you in advance!

Please add more information about what you did, and what did not work. https://github.com/istio/istio/wiki/Troubleshooting-Istio can help explain how to get detailed config dumps as well

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: istio-test
spec:
hosts:
#- "*"

istiogateway.server
service.istio-test.svc.cluster.local
service2.istio-test.svc.cluster.local
service3.istio-test.svc.cluster.local
gateways:
istio-test/istio-test-gateway
mesh
http:
match:

uri:
prefix: "/service/service"
gateways:

istio-test/istio-test-gateway
rewrite:
uri: "/service"
route:

destination:
port:
number: 8080
host: service
subset: v1
weight: 100
destination:
port:
number: 8080
host: service
subset: v2
weight: 0
timeout: 2s
retries:
attempts: 3
perTryTimeout: 2s

match:

uri:
prefix: "/service2/service2"
gateways:

istio-test/istio-test-gateway
rewrite:
uri: "/service2"
route:

destination:
port:
number: 8080
host: service2

match:

uri:
prefix: "/service3/service3"
gateways:

istio-test/istio-test-gateway
rewrite:
uri: "/service3"
route:

destination:
port:
number: 8080
host: service3

match:

uri:
prefix: "/service"
gateways:

mesh
route:

destination:
port:
number: 8080
host: service.istio-test.svc.cluster.local
subset: v1
weight: 100
destination:
port:
number: 8080
host: service.istio-test.svc.cluster.local
subset: v2
weight: 0

match:

uri:
prefix: "/service2"
gateways:

mesh
route:

destination:
port:
number: 8080
host: service2.istio-test.svc.cluster.local

match:

uri:
prefix: "/service3"
gateways:

mesh
route:

destination:
port:
number: 8080
host: service3.istio-test.svc.cluster.local

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
name: service
spec:
host: service
subsets:

name: v1
labels:
version: v1
trafficPolicy:
connectionPool:
http: {}
tcp: {}
loadBalancer:
simple: RANDOM
outlierDetection:
baseEjectionTime: 15s
consecutiveErrors: 1
interval: 5s
maxEjectionPercent: 100
name: v2
labels:
version: v2
trafficPolicy:
connectionPool:
http: {}
tcp: {}
loadBalancer:
simple: RANDOM
outlierDetection:
baseEjectionTime: 15s
consecutiveErrors: 1
interval: 5s
maxEjectionPercent: 100

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: istio-test-gateway
namespace: istio-test
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:

port:
number: 80
name: http
protocol: HTTP
hosts:

"*"
I set the specified settings. I have 1 pod of the service "service" version v1 running. Artificially spoil 1 request from the service "service" so that it returns 503 status. After that, rest-requests to the "service" service do not pass through the ingressgateway (no healthy upstream), which is correct. But if I call the service api "service3" through the Ingressgateway, which first calls the service api "service2" through the client, and that in turn calls the service api "service", then the service is available and no error occurs. Here I expected that the "service" service would be unavailable for both direct invocation through ingressgateway and inter-service invocation. Please help and point out what I am doing wrong and how to close the interservice calls.

You mentioned 3 different services. Do they all have sidecars injected?
It would help to get config dump and access logs from the gateway and service3, service2, and service 1. https://github.com/istio/istio/wiki/Troubleshooting-Istio has info on this. thanks

Hello, I have a question about outlierDetection. If the fuse is triggered and the service is evicted, I learned that the eviction time=baseEjectionTime*the number of evictions, then is there a maximum eviction time? If there is no maximum, does it mean that you will be evicted for an infinite period of time if the service is not stable enough? I did not find a detailed description of the maximum eviction time. Can you help me out?


Standardize our gem's configuration interface

We should provide a ReadySet.configure method that can be used to configure our gem's setting, similar to what is done here. For now, the only configuration option the gem requires is the ReadySet connection string. This method would likely be called somewhere in config/environments or config/initializers (likely wherever a user has other gems configured).

Starting on this issue now. I'll use the gem you linked as a reference. Thank you for finding that! It's perfect.


Release 0.2.0

The main thing I'd like to release is the code for producing indexes (#49). May not get to it for a few weeks due to the holidays.


Undefined variable $selectedFileName

Hi after update the package, i got error Undefined variable $selectedFileName

Hey @Virgo-SSS ,
Can you please clear the view cache?
php artisan view:clear

it's working fine, thank you
can close the issue

Glad it helped :)


Remove object-fit polyfill files

Update Node modules
Remove object-fit polyfill files. object-fit is supported in all modern browsers.

You need to update the gulpfile.js', app.html, and index.html` files

Rerun npm install and commit updated package-lock.json appears to be missing npm-force-resolutions items.


Update github.com/aws/aws-xray-sdk-go to latest version

The current version (1.6)  of aws-xray-sdk-go of https://github.com/aws/aws-xray-sdk-go/blob/v1.6.0/go.mod#L15 has outdated dependencies (fasthttp 1.24.0 ) with vulnerabilities.
More Details https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMVALYALAFASTHTTP-2407866
updating aws-xray-sdk-go to version >= 1.7 should fix it.

Hello, I'm pleased to announce that an updated version of aws-xray-sdk-go has been included in v1.9.0 of the datadog-lambda-go libarary.


Reduce race condition likelihood, remove redundant diff download

This PR introduces a few changes to the sanity-vuln-check-updates job

Will reduce (not eliminate) the likelihood of a race condition that occurs when the definitions.stackrox.io GCS bucket is updated after the sanity-check-vuln-updates job has started (which has been observed).  It does this by using the age of the GCS diff.zip as close to the 1hr age check as possible (instead of the age determined when the job started)
The CloudFlare age header is now also logged for future troubleshooting / logic as necessary, it shows the actual cache age (for the particular CloudFlare node)
Each diff was being downloaded multiple times (back to back), once for extracting a manifest.json, and the other for extracting the cache-control headers.  This PR removes the redundant download (wget) which should reduce bandwidth and potentially speed up the job (further reducing race condition likelihood)
The temporary diff.zip downloads have been moved into the job's $WORKING_DIR so that cleanup can perform as expected

Smoke tested locally:
$ ./sanity-check-vuln-updates.sh
-----------------------------------------------------------------------
diff_id                  : 0133c2cf-8abe-4d79-9250-9b64b5b3e43e
gsutil_last_update       : Mon, 06 Feb 2023 21:58:07 GMT
gcs_object_age_seconds   : 8283
gcs_object_age_secs_now  : 8283

url_gsutil               : gs://definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip
url_cloudflare           : https://definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip
url_gcs_https            : https://storage.googleapis.com/definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip

metadata_cloudflare      : {"since":"2020-09-08T17:02:45.481154658Z","until":"2023-02-06T21:07:39.922044426Z"}
metadata_gcs_https       : {"since":"2020-09-08T17:02:45.481154658Z","until":"2023-02-06T21:07:39.922044426Z"}

cache_age_cloudflare     : 0
cache_control_cloudflare : cache-control: public, max-age=3600
cache_control_gcs_https  : cache-control: public, max-age=3600

md5sum_cloudflare        : 7c730179c770172308499094982549db
md5sum_gcs_https         : 7c730179c770172308499094982549db

...

/retest


keplerproject.org dead

Hello,
Sorry, this issue is not to do with luarocks. For almost  a week now I have not been able to reach keplerproject.org. This, unfortunately, is causing problems with other websites. In particular, a LOT of projects link keplerproject.org/doc.css in their user documentation. This causes pages to not load or hang for a very long time. This has a pretty large impact on such a small community. Is there anything I can do to help fix this? Can I offer hosting for the domain? Can we get a rewrite rule on doc.css to a cdn copy?

Some modules had been fixed a long time ago. Could you email me a list of the modules which has this issue? I can submit PRs for them. (email address should appear in my profile).
I don't think hosting keplerproject.org is worth it. Most modules these days had been updated to use local links to css files and also to use github pages to host the docs.
I'll close this now, since it's not LR related, but send me that module list.


Drop Node.js 7 from CI builds

I don't see any good reason for keeping Node.js 7 in the CI builds. It's not an LTS release and the "latest and greatest" has been superceded by Node.js 9.
Should we drop Node.js 7 from Travis CI and AppVeyor?

I support this.
Node 7 is EOF since 2017-06-30 (https://github.com/nodejs/Release#release-schedule)

IT needs to be dropped for sure.


Fixing import_file exception test

Fixes: N/A
Summary/Motivation:
Fix a test that was calling the wrong function
Changes proposed in this PR:

call import_file (not run_file) in the test added in #70.

Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution:

I agree my contributions are submitted under the BSD license.
I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

Codecov Report

Merging #74 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #74   +/-   ##
=======================================
  Coverage   62.85%   62.85%
=======================================
  Files          87       87
  Lines        8777     8777
=======================================
  Hits         5517     5517
  Misses       3260     3260

Continue to review full report at Codecov.

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


Tried to call protected function in combat

Using 1.2.1
20x [ADDON_ACTION_BLOCKED] AddOn 'LFGSpamFilter' tried to call the protected function 'LFGSpamFilterReportHelperButton:Hide()'.
[string "@!BugGrabber\BugGrabber.lua"]:519: in function <!BugGrabber\BugGrabber.lua:519>
[string "=[C]"]: in function `Hide'
[string "@LFGSpamFilter\modules/ui.lua"]:40: in function <LFGSpamFilter\modules/ui.lua:37>
[string "=[C]"]: in function `LFGListFrame_SetActivePanel'
[string "@FrameXML\LFGList.lua"]:330: in function `LFGListFrame_FixPanelValid'
[string "@FrameXML\LFGList.lua"]:143: in function <FrameXML\LFGList.lua:138>

How to reliably reproduce:

Open LFG and leave it open
Go to Dungeons
Enter combat
Close LFG window

Basically any time you try and close the LFG window while in combat after being on a pane that LFG Spam Filter had modified.

Should be fixed in 1.2.2, thanks for the report.

Confirmed it's fixed. Thanks for the quick turnaround!


pod issues

[!] Unable to read the license file LICENSE for the spec collection-view-layouts (0.1.2)

Duplicate of #21


STAR-426 Add specific CQL statement to record dropped columns

Co-authored-by: Sylvain Lebresne<EMAIL_ADDRESS>

I haven't finished yet, I wonder if I need to understand the problem and solution or just trust DSE code ?

I think it would help if places where port was not automatic would got some short author note as a self-review PR comment.

Sure, I can do that

But I have one major question: will we not break backward compatibility or downgradabilty between StargazerDB and OSS? This is a bit different from new types e.g. as it does not require to make concious use of the new types or code constructs.

Good question - we do need to be clear on expectations/what we intend to support.
Do you mean by dumping the schema using DESCRIBE in SGZR and re-creating in OSS?
There are two options there: if normal DESCRIBE is used, I think it will be okay, as the DROPPED COLUMN RECORD syntax is not included in the output.
If DESCRIBE is used WITH INTERNALS, then the DROPPED COLUMN RECORD syntax is included and this would not work on an OSS cluster.
AFAICT, WITH INTERNALS is something new in OSS; it was not present in DSE and I do not think DSE has a user facing way to expose dropped columns.
Both OSS and DSE are maintaining dropped column metadata for use in backup/restore scenarios. DSE replaced the use of ALTER TABLE DROP/ADD with DROPPED COLUMN RECORD in DB-3460 which is being ported here. The main motivation for it is Astra.

I haven't finished yet, I wonder if I need to understand the problem and solution or just trust DSE code ?

I probably cannot add more than what is found in DB-3460, but am happy to have a discussion about it.
I think the short answer may be that this is needed for Astra in backup/restore operations.


[Relay][Op] Add instance norm op

Some of our models use the IBN-Net structure, so we need an instance norm op in TVM. I've tested on our models and it works fine.
@kevinthesun @masahi @junrushao1994 Could you have help review?

@hlu1 @antinucleon @vinx13 @Huyuwei can you help review the high level api ? We mainly want to make sure API consistency  https://docs.tvm.ai/contribute/code_review.html#deliberate-on-api-and-data-structures
@bindog can you also comment about the related APIs in the existing packages

I update the MXNet frontend converter and test cases, I think the API is compatible with the existing packages. The instance norm is similar to relay.op.nn.nn.batch_norm except that instance norm doesn't need moving_mean and moving_var, and it also consistent with other framework like mxnet.gluon.nn. InstanceNorm

I think the API is fine, as it is similar to batch_norm and layer_norm in relay.

@bindog Thanks, this is merged


Fix custom-server-typescript not typechecking

Hi
In the current version of the example custom-server-typescript, types are never checked.
For instance, change the following line :
const dev = process.env.NODE_ENV !== 'production'

by :
const dev: number = process.env.NODE_ENV !== 'production'

then run npm run dev. The application launches perfectly, no error is thrown.
In dev environnement, it is preferable to check types all the time, to get immediate feedback. This PR activates type checking. Only when using nodemon, so no impact on production.
Now the above code will (rightfully) refuse to compile :
TSError: ⨯ Unable to compile TypeScript
server/index.ts (6,7): Type 'boolean' is not assignable to type 'number'

Thank you very much!


Tests fail when remote uses SSH syntax

When a user has a remote using git@github.com:path, the tests will fail when trying to pip install the URL that pytest-perf installs, e.g. setuptools.git@git+git@github.com:pypa/setuptools.git.

Workaround is to use the HTTPS syntax for the remote or URL syntax:
https://github.com/pypa/setuptools or
<EMAIL_ADDRESS>


Documentation: can you specify in azds.yaml what docker target to use?

We are using multi-stage Docker builds and would like to use single dockerfile for azds as well.
Can you specify in azds.yaml what docker target to use?
Specifying "target" as mentioned in https://docs.docker.com/compose/compose-file/
did not worked.
kind: helm-release
apiVersion: 1.1
build:
context: ....
dockerfile: ....\Dockerfile.develop
target: dev-app1
useGitIgnore: true
....

Unfortunately as of today we don't support a Target parameter in the azds.yaml.
I created a work item to track this and I'll keep you posted on the progress.
In the mean time you will have to use the Dockerfile.develop as a workaround.

Thank you @lolodi  !
Any rough ETA - week, month ?

We have still to get a full estimate of the work to be done, but I'd expect in the ~month range. Can't be more precise right now.


cvxpy does not export variables names with cplex

Describe the bug
Export mps with cvxpy / CPLEX hides the name of the variables
To Reproduce
import cvxpy as cp
Define and solve the CVXPY problem.
nbBus40 = cp.Variable(name="nbBus40",integer=True)
nbBus30 = cp.Variable(name="nbBus30", integer=True)
cost = 500nbBus40+400nbBus30
prob = cp.Problem(cp.Minimize(cost),[40nbBus40+30nbBus30>=300,
nbBus40>=0,nbBus30>=0
])
prob.solve(solver=cp.CPLEX,verbose=True, cplex_filename= "c:/temp/model.mps")
print("status = ",prob.status)
Print result.
print("\nThe minimal cost is", prob.value)
print("number buses 40 seats = ",nbBus40.value)
print("number buses 30 seats = ",nbBus30.value)
Expected behavior
In the .mps I would expect to see nbBus40 but I see x1 and x2!
Output
In the mps I get
NAME
ROWS
N  obj1
L  c1
L  c2
L  c3
COLUMNS
MARK0000  'MARKER'                 'INTORG'
x1        obj1                          500
x1        c1                            -40
x1        c2                             -1
x2        obj1                          400
x2        c1                            -30
x2        c3                             -1
MARK0001  'MARKER'                 'INTEND'
RHS
rhs       c1                           -300
BOUNDS
FR bnd       x1
FR bnd       x2
ENDATA
Version

OS:
CVXPY Version:

Additional context
Add any other context about the problem here.

Hey @AlexFleischer thanks for raising this issue.
cvxpy supports exporting variable names from cplex, see the related PR here #1169 . I am not sure why these values are not being shown in the .mps file. If you are willing to make a contribution to resolve this, you can look into how the mps file is generated and maybe will just need to make sure the variable names are being passed there as well?


chore(deps): update dependency rollup to v4.9.0

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

rollup (source)
4.6.1 -> 4.9.0

Release Notes

rollup/rollup (rollup)
v4.9.0
Compare Source
2023-12-13
Features

Fully support arbitrary strings as import and export identifiers (#5298)

Pull Requests

#5296: Do not assume setTimeout return type (@kapouer)
#5298: Fully support arbitrary module namespace identifiers for all formats (@lukastaegert)

v4.8.0
Compare Source
2023-12-11
Features

Improve experimentalMinChunkSize to take already loaded modules from dynamic imports into account (#5294)

Pull Requests

#5294: Find more merge targets for experimentalMinChunkSize (@lukastaegert)

v4.7.0
Compare Source
2023-12-08
Features

Add build for Linux riscv64 architecture (#5288)

Bug Fixes

Improve error message when native Windows build does not start (#5284)

Pull Requests

#5278: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5281: Add logs and experimentalLogSideEffects to REPL (@lukastaegert)
#5284: Add friendly error for missing MSVC redistributable (@sapphi-red)
#5285: chore(deps): update dependency vite to v5.0.5 [security] (@renovate[bot])
#5288: Add support for linux riscv64 gnu (@kxxt)
#5290: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Renovate Bot.

This has been combined into https://github.com/apollographql/apollo-ios-dev/pull/209.


Use minus (-) character in alias name

Please allow the minus character in alias names as requested here:
https://forum.opnsense.org/index.php?topic=4626.msg17839#msg17839

I'm late to the party, sorry.
Aliases are macros in pf.conf, the parsing of macro expansion can only match alphanumeric characters and the underscore character. During macro expansion the minus character is used as a breaking delimiter, e.g. for port ranges.
The relevant code line is this: https://github.com/opnsense/src/blob/master/sbin/pfctl/parse.y#L5702

@fichtner so if I understood correctly this request is technical, not possible, at least not in the never future, right?

Yes and no. There's no easy fix here, but we could use a double underscore to encode the minus in the rules, but it takes a bit of work and care that "__" is not used in an alias already, maybe even deny using this combination.

@fichtner, Ok, thanks for the explanation. I think it will be really handy if this will be included future (major) releases, the minus is really often used in (server) hostnames, maybe this becomes handy for a lot of people. but again, only if possible of course.
Thanks anyway!

I'll see what we can do, thank you for the feedback :)

In case you use UTF-8 systemwide, it's maybe possible to do something like mb_str_replace("-", "‑", $string); which would change the normal "minus-sign" to"non-breaking hyphen". They look graphically same, but are different glyphs in UTF-8 charset.

but that still won't allow use in pf.conf ASCII syntax :(
the best solution is stuffing, e.g. replacing "" (one) by "__" (two) internally and using "-" as "". that still requires audit of validation and code paths, also readings and mapping it back.

timeout

Why was this closed?
It's still not fixed.

@Tragen because nobody worked on it.


API Wrapper Error Handling

When no GPU is available the following is returned:
Curl returns the error "{"errors":[{"message":"There are no longer any instances available with the requested specifications. Please refresh and try again.","path":["podFindAndDeployOnDemand"],"extensions":{"code":"RUNPOD"}}],"data":{"podFindAndDeployOnDemand":null}}"
This needs to be handled by the language API and returned.

Currently, you must print raw_response https://github.com/runpod/runpod-python/blob/b01e6b62d03273776692f6e88d9d57862c4d27cd/runpod/api_wrapper/ctl_commands.py#L37
to visualize the error. It would be preferable to either raise an exception or implement another method of notifying the user.


[BUG] - Right padding on Switch component

NextUI Version
2.4.8
Describe the bug
Padding is applied to the right side of the Switch component. What I'm curious about is whether this right padding should be applied when the text on the right side of the Switch component is activated. Currently, the padding on the right side of the Switch component is unconditionally applied, so when you use the Switch component, there is always a margin on the right side, which is frustrating.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
In the Switch component's official documentation, right padding is unconditionally applied.

Expected behavior
There is no string text in the Switch component, but padding is always applied to the right, so when using this Switch component, it is cumbersome to work with the UI due to the right padding.
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

Ideally it should be applied when there is a label. Closing this as duplicate because it has been reported here: https://github.com/nextui-org/nextui/issues/3806


Improve TwoBodyElectronicIntegrals.to_second_q_op performance

Summary
This improves the performance of the TwoBodyElectronicIntegrals.to_second_q_op method.
The unusable performance was observed when attempting to run the following:
import time

from qiskit_nature.drivers.second_quantization import PySCFDriver

driver = PySCFDriver(atom="O 0 0 0.115; H 0 0.754 -0.459; H 0 -0.754 -0.459", basis="cc-pVDZ")
props = driver.run()
print(props.get_property("ParticleNumber"))

start = time.time()
props.second_q_ops()
stop = time.time()
print(stop - start)

which is a system of size:
ParticleNumber:
        48 SOs
        5 alpha electrons
                orbital occupation: [1. 1. 1. 1. 1. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.]
        5 beta electrons
                orbital occupation: [1. 1. 1. 1. 1. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.]

On latest main, this snippet takes longer to execute than I am willing to wait (>10 minutes). After this PR, it will take 4.484 seconds.
Details and comments
I also ran the following benchmark:
import time

import numpy as np

from qiskit_nature.properties.second_quantization.electronic.bases import ElectronicBasis
from qiskit_nature.properties.second_quantization.electronic.integrals import (
    TwoBodyElectronicIntegrals,
)

sizes = range(1, 50)
times = []

for size in sizes:
    print(f"{size} MOs: ", end="")
    ints = TwoBodyElectronicIntegrals(
        ElectronicBasis.MO,
        (
            np.random.random((size, size, size, size)),
            None,
            None,
            None,
        ),
    )
    local = []
    for i in range(10):
        start = time.time()
        op = ints.to_second_q_op()
        stop = time.time()
        local.append(stop - start)
    times.append(np.average(local))
    print(f"{times[-1]}s")

Note, that this is a worst case scenario because we have a dense, non-zero matrix. Chemistry applications are highly sparse and all zero-terms will be skipped. However, iteration still needs to happen over #SO**4 matrix elements..
Here are the benchmark results on 72d5445d59a0829ec5a65f1ba0e36be26d63e63f
1 MOs: 0.0003814220428466797s
2 MOs: 0.003143501281738281s
3 MOs: 0.01747605800628662s
4 MOs: 0.10729048252105713s
5 MOs: 0.4813446283340454s
6 MOs: 2.6585819482803346s
7 MOs: 10.059082674980164s
8 MOs: 33.26701810359955s

And here are the results with this PR:
1 MOs: 0.0001928091049194336s
2 MOs: 0.00028238296508789065s
3 MOs: 0.0008608579635620117s
4 MOs: 0.005258703231811523s
5 MOs: 0.010203838348388672s
6 MOs: 0.02182309627532959s
7 MOs: 0.049395179748535155s
8 MOs: 0.07928628921508789s
9 MOs: 0.12792351245880126s
10 MOs: 0.20389955043792723s
11 MOs: 0.32534089088439944s
12 MOs: 0.5057589530944824s
13 MOs: 0.6290717124938965s
14 MOs: 0.8679617881774903s
15 MOs: 1.2400678396224976s
16 MOs: 1.8723540782928467s
17 MOs: 2.1375882148742678s
18 MOs: 2.7122227430343626s
19 MOs: 3.2011844635009767s
20 MOs: 3.8472093820571898s
21 MOs: 4.834750986099243s
22 MOs: 5.815815830230713s
23 MOs: 7.087169241905213s
24 MOs: 8.564099335670472s
25 MOs: 9.87972595691681s

(Note: #SOs = 2 * #MOs)
Note: in the future we can take this optimization further by parallelizing the implementation. However, this generation is I/O bound rather than compute bound which means that a straight-forward application of qiskit.tools.parallel_map which actually result in worse performance (see also https://github.com/Qiskit/qiskit-terra/issues/7741). One solution could be the use of shared memory, as attempted here: https://github.com/Qiskit/qiskit-terra/pull/7789.
For the time being, performance is greatly improved by this PR and in the near future it is unlikely that we need to generate the second quantized operators for 100+ spin orbitals. At that point storage will also become concern so we will need to support the usage of sparse matrices anyways, which will also improve the performance of this method.

So basically this builds out the FermionicOp having first created all the terms rather than building one and then augmenting it term by term. Is there any aspect of the performance around how the methods used before that could considered in the future though perhaps always building it out in one go may faster than how things were done.

Yes I believe that the previous way of building out the FermionicOp will always be less performant, simply because of the overhead involved with constructed 5 instances of FermionicOp per iteration, compared to a single instantiation in the new case. Obviously, this single instantiation now can take considerably longer than the previous single ones, but as you can see from the speedup achieved here, this is not a problem.
I think the old implementation was a bit more instructive/educational in terms of how the integral indices determine which creation/annihilation operator to use, but this is not worth the performance deficiencies.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
21 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.003%) to 83.535%

Files with Coverage Reduction
New Missed Lines
%

qiskit_nature/properties/second_quantization/electronic/integrals/one_body_electronic_integrals.py
2
95.56%

qiskit_nature/properties/second_quantization/electronic/integrals/two_body_electronic_integrals.py
4
92.0%

qiskit_nature/properties/second_quantization/electronic/integrals/electronic_integrals.py
15
90.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
9031

Relevant Lines:
10811

💛  - Coveralls


[ENH] - Added test function for compute_spatial_information_2d

In the process of creating test functions for other functions that don't yet have one. Related to issue #34
What's added:

adds test_compute_spatial_information_2d function for compute_spatial_information_2d within spatial\information.py.

Look great, merging in now!


"Segmentation fault" error occurred after<EMAIL_ADDRESS>version.

Problem
"Segmentation fault" error occurred after<EMAIL_ADDRESS>version.
Tobe
It should work fine as of version 0.5.8
Environment

uv : after 0.5.9
os : windows10 build 19045.4291

Reproduce

install<EMAIL_ADDRESS>
$ uv version
uv 0.5.9 (0652800cb 2024-12-13)

run any uv command (with errors)

$ uv run hello.py
Segmentation fault

$ uv python list
Segmentation fault

downgrade to<EMAIL_ADDRESS>version

$ uv version
uv 0.5.8 (80d41671b 2024-12-11)

run any uv command (run successfully)

$ uv run hello.py
Hello from application!

$ uv python list
cpython-3.13.1+freethreaded-windows-x86_64-none    <download available>
cpython-3.13.1-windows-x86_64-none                 <download available>
...

Huh, very little changed between these two releases. Maybe #9815?


Dissallow names less than 2 characters long or more than 32 characters

Show a Snackbar after pressing the connect button or disable the button until more than two characters have been typed?

Show a Snackbar (toast message) after pressing the connect button or disable the button until more than two characters have been typed?

disable + some sort of hint

Hi, I would like to work on this.

Hi, I would like to work on this.

Great! I've updated the issue too to be more correct

I have completed the task and created a PR.

#56


Interface is all tinted black

@jgonzales20 ios i suppose?

That is correct, uploaded this from my phone. Here's more details,
Build 2.8.2 Build 118
IOS 18.1
IPhone 14 Pro.
On a side note, please allow photo upload for the in app feedback form.

—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Akylas_oss-2Dweather_issues_239-23issuecomment-2D2483072278&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=2XUfCNqtxoC3tCnHzKsC7Qin0KWk7eCOuqzmfAeWux4&m=ZRmrd_qb8IhXoMJvL_bISOauCwBVv7ix3grnNR1IRWST9uWZ3UBdJwTgy19gK0Vn&s=3nexteyOwLg-QwVxMb_4sAQNzcuRCDOpPV_wC4-gnCg&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BKZRZ245PCOXGMUAIIH2QVT2BHUZDAVCNFSM6AAAAABR7VXPUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTGA3TEMRXHA&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=2XUfCNqtxoC3tCnHzKsC7Qin0KWk7eCOuqzmfAeWux4&m=ZRmrd_qb8IhXoMJvL_bISOauCwBVv7ix3grnNR1IRWST9uWZ3UBdJwTgy19gK0Vn&s=SOiKCFbPaPzYGajtBg5UIbmkPX1uJUwoMRtE5TCPNzE&e=.
You are receiving this because you were mentioned.Message ID: @.***>
This email is from an external sender. Use caution when replying, following links, or opening any attachments.

@jgonzales20 thanks publishing a new version with the fix!

Thank you, I use this app daily.

From: farfromrefuge @.>
Sent: Monday, November 18, 2024 9:08 AM
To: Akylas/oss-weather @.>
Cc: Jacob Gonzales @.>; Mention @.>
Subject: Re: [Akylas/oss-weather] Interface is all tinted black (Issue #239)
@jgonzales20https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_jgonzales20&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=2XUfCNqtxoC3tCnHzKsC7Qin0KWk7eCOuqzmfAeWux4&m=B9R1YexpB03yhLCRK2ImJ8kw3OBr4t8o0WidtnRHDdbvsU9n1xssktMOnp4HqrAF&s=GFolO3m32ZR_6FyD7Sc4LJX60bGmvhLsri5ubFeIC1I&e= thanks publishing a new version with the fix!
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Akylas_oss-2Dweather_issues_239-23issuecomment-2D2483150105&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=2XUfCNqtxoC3tCnHzKsC7Qin0KWk7eCOuqzmfAeWux4&m=B9R1YexpB03yhLCRK2ImJ8kw3OBr4t8o0WidtnRHDdbvsU9n1xssktMOnp4HqrAF&s=Z0jOxWGlSpSUuZVuyafLM9zDa4l5gDeiH8wmj1u1hXw&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BKZRZ243PQMNKMCDMBTMMID2BHYE7AVCNFSM6AAAAABR7VXPUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTGE2TAMJQGU&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=2XUfCNqtxoC3tCnHzKsC7Qin0KWk7eCOuqzmfAeWux4&m=B9R1YexpB03yhLCRK2ImJ8kw3OBr4t8o0WidtnRHDdbvsU9n1xssktMOnp4HqrAF&s=mzmvj6vnJqnr6ICxY_LuYkbzgxQaWZ5H8hVueAPvgho&e=.
You are receiving this because you were mentioned.Message ID: @.***>
This email is from an external sender. Use caution when replying, following links, or opening any attachments.


Use modules everywhere

This updates our package.json to use modules everywhere.
There are a few things to consider before we merge this.  Not all tools are ready for module type packages.  For example, webpack supports ESM config files but doesn't yet support ESM loaders (or probably other plugins) - see webpack/webpack#13233.  In addition, Karma doesn't support loading ESM config files - see karma-runner/karma#3677.  And as you might guess, JSDoc doesn't fully support ESM in templates (I didn't create an issue, but it assumes a template will have a publish.js that can be require()d).
We can work around these things with a couple different strategies:

If a tool allows an extension to be provided when configuring a plugin or similar, use the .cjs extension.
If the option above doesn't work, include a package.json with "type": "commonjs" in the directory or a parent directory of the config/plugin code.

The alternative to these workarounds is just to change our package.json to "type": "module" when we are building the package before publishing.  That would be pretty straightforward.  I took on the changes here to see how much closer things are to being able to use ESM all the way.  I'm not attached to this and can resurrect it later if we decide not to do it right now.
I've added a test/node directory where we can place tests that are not browser-specific.  For now, I've just copied in the ol/array tests.  We could decide that all tests that don't do DOM manipulations should run directly in Node (this is a much simpler setup than the Karma/webpack setup).  If others think this is a good idea, I could continue porting some of the existing Karma tests to run directly in Node.
You can try out the results with npm install ol@module.
Examples:

with esbuild openlayers/ol-esbuild#2
with Rollup openlayers/ol-rollup#5
with Parcel openlayers/ol-parcel#1
with webpack openlayers/ol-webpack#3

Fixes #10821.
Fixes #12186.

I'll look into the failing ol.renderer.webgl.PointsLayer test later.  It also looks like I'll need to restore sourcemaps for the Karma tests.

Next puzzle is to figure out why the rendering tests never finish now.  Last successful run was https://github.com/openlayers/openlayers/runs/2444136446 (for be806f6c9f5753a4782755f7827c69fea3d527d5).  The run https://github.com/openlayers/openlayers/runs/2464262655 for a rebased version of the same commit (0b2ec1e747f11db32d119051985e01a32cbceed1) appears to be hung.


function module variable wrong with PEP420 namespace packages

I'm having a problem with a cython module and pickle. I think I've tracked it down to the fact that the __module__ variable for the function is wrong. I'm using a PEP420 native namespace package. I'm using the master branch checked out just a few minutes ago.
Python 3.7.0 (default, Aug 15 2018, 09:03:42)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cython
>>> cython.__version__
'3.0a0'
>>> import cdcdvh.pyseqdist.cDistance
>>> cdcdvh.pyseqdist.cDistance.edit_distance.__module__
'pyseqdist.cDistance'

It seems that namespace packages are not being considered when calculating the fully qualified module names. This is handled by the package detection machinery in Cython/Utils.py.
Note, however, that it's not entirely obvious how to interpret PEP 420 when it comes to compiling a module from a specific file path. There is no import going on in this case, and the module search path is not being looked at (and might not even contain the namespace package directory, since we're at build time).
PR welcome if there is a good way to do it, but failing that, it might turn out to be easier for users to specify the full module name in their setup.py script, rather than relying on namespace packages for their builds.

https://github.com/pypa/setuptools/issues/97
is the setuptools discussion of this exact situation.

The ticket is very long, proposes multiple approaches and then splits up into further tickets. Could you please sum up their solution, so that we can see if it applies similarly to Cython?

They ended up creating a new function: find_namespace_packages
I'm actually using setuptools Extension objects in my setup script with the full module name. Given the way setuptools handled it I thought that was the most obvious way to get the correct setting. I've been trying to follow how that name moves through the Cython pipeline and why the compiler is even trying to re-derive the name from the path for the module variable. It's been a convoluted spelunking trip so far. I plan on doing an interactive debug of the compile process at work tomorrow. Holiday schedule permitting I hope to get a PR together for the issue before too long.
I'm not sure if something else should be done with the cythonize procedure to deal with namespace packages.

Sigh well. I spent a long time working on this and it has turned out to be a PEBKAC error (not surprising). I had an old version of the .so hanging around which was being found first on the lib path. I removed that and things seem to be OK now.


[grpc] update patch file to apply cleanly for grpc 1.18.0

This is a small fix to the patch file to update it to match grpc 1.18.0 source code.
Current patch file will generate warnings like this:
Checking patch CMakeLists.txt...
Hunk #6 succeeded at 3808 (offset -10 lines).
Hunk #7 succeeded at 3817 (offset -10 lines).
Hunk #8 succeeded at 3938 (offset -10 lines).
Hunk #9 succeeded at 3948 (offset -10 lines).
Hunk #10 succeeded at 4940 (offset 10 lines).
Hunk #11 succeeded at 4949 (offset 10 lines).
Checking patch src/core/lib/iomgr/resource_quota.cc...
Hunk #1 succeeded at 937 (offset 1 line).
Checking patch src/core/lib/security/credentials/alts/check_gcp_environment_windows.cc...
Applied patch CMakeLists.txt cleanly.
Applied patch src/core/lib/iomgr/resource_quota.cc cleanly.
Applied patch src/core/lib/security/credentials/alts/check_gcp_environment_windows.cc cleanly.

Thanks for the fix!
It has been merged to master.


The Latex input panel closed after a prompt selected

Each time I select a prompt the plugin having given, input panel from the Latex block closed and my input was interrupted by this. And I have to reopen the Latex block.

I see. I will try to fix it.


wasted @import font call

Can you change the font to use a web-safe font instead of the google font?
The google font import makes an unnecessary call when the font is overridden in my project styles. When using bower it is not best practice to change anything in the packages you use. I import the package .css into my .css and then override specific rules. This doesn't work for the font @import. I can also copy the package .css to my project folder, but again this is not ideal as I'd essentially be forking the code locally.
This is a super small issue, but solving it would make this this already awesome plugin even awesomer!

I completely agree. Removed in the next version that will be pushed today or tomorrow.


See list of tx involving this object

While on NFTs page, see list of transactions involving this NFT/object. Helps users gauge the value of these NFTs and become curious to click through to project url. Furthermore as owner they can easily track thru history and see activity.

@bwann52 - how does this differ from #1211?

Yes, this one is about showing all txs. Whereas #1211 will require some UX/UI design.


Triggering e2e tests when deploying to staging

Description
Triggering e2e tests when deploying to staging, and getting test results

Summary by CodeRabbit

New Features

Introduced a new job step in the deployment workflow to trigger end-to-end (e2e) tests after application deployment.
Added a new workflow for reporting e2e test results, allowing manual triggering and input for test run ID and results.

Bug Fixes

Enhanced error handling and reporting for e2e test failures.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.52%. Comparing base (c5d99fb) to head (903eb71).

:exclamation:  There is a different number of reports uploaded between BASE (c5d99fb) and HEAD (903eb71). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (c5d99fb)
HEAD (903eb71)

2
1

Additional details and impacted files
@@             Coverage Diff             @@
##              dev     #509       +/-   ##
===========================================
- Coverage   83.11%   70.52%   -12.60%
===========================================
  Files         291      129      -162
  Lines        2967     1357     -1610
  Branches      178       78      -100
===========================================
- Hits         2466      957     -1509
+ Misses        490      400       -90
+ Partials       11        0       -11

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix mysterious zipped module specific issue with memory deallocation …

…for static stack variables

Ah, there it hit me, the premature optimization. Of course I would consider creating the string handle again and again a waste and used a static... That being said, I am interested what you mean with zipped module specific? How does the data reach the function compared to normally? Or is the module run differently? I am always a bit lost on the current setup... Two things, though. First, I like refactoring. If I read this right, then the wChar String can now be initialized later, directly with the needed space (been a while, but I am sure there was something to set the intial size?) , basically where the resize was before, same with the receiving string buffer. And with the string buffer being temporary, the string should now be moved to the receiving string (... = std::move(...)) (and the name for the receiver parameter changed), to avoid the copy. Second... in no project I will create, are PRs directly done to main. 😉 The zip issue is important btw. I have some statics in use in some graphicsReplacer functions... we need to know the reason and how to avoid it.

You can also keep your code but add compiler flag: /Zc:threadSafeInit

And this solves the issue? I just find it strange that it works a few times... at this point, the variables would need to be intialized a long time...

Since we changed the approach to the compiler flag, this can be closed.
That being said, it looks like it might have been possible to avoid a copy here or there. Whatever.


Fix Code Sign settings for Xcode 8

Xcode 8 introduced a new way to code sign apps and frameworks.
The current settings in the framework have a developer id hardcode, which prevents it from when used by other teams.
This PR fixes it 😊
See https://twitter.com/_petegoldsmith/status/782778069777997824

Update the PR touches iOS and tvOS targets.
This PR explicitly set the Provisioning Style to Automatic in the iOS, tvOS, and watchOS target.
I didn't touch the macOS one because it was set to manual, and I thought there might have been a reason for that. If that's not the case I'm happy to update with macOS as well.
Cheers

@ashleymills any chance of this getting merged?

@mokagio Thanks for the PR
Cheers
Ash

No worries, thanks for building this ☺👌💖


Latest version of glutin depends on yanked version of winnit.

❯ cargo run
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: no matching version `^0.10.1` found for package `winit` (required by `glutin`)
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.11.0, 0.10.0, 0.9.0, ...

https://crates.io/crates/winit/0.10.1

#987 should fix that.


Fix the issue that num_locusts could be 0

When running locust with -c 1 on 3 locust clients, locust exit silently.
Not sure about the original design, so just add a simple fix to set
num_locusts to 1 when it was 0 on round()
ISSUE - https://github.com/locustio/locust/issues/989

@ztou If you fix the failing tests I might be able to merge this PR.

I believe this was fixed by #1113


refactor: add first version of refactoring on swap

Just missing to fix/add tests now, the state machine is done

Found two issues:

When changing tabs with DAI on Top

Price impact on swap with maximum

https://user-images.githubusercontent.com/3941923/174509006-fe30a1fc-797d-4045-9aae-efa43a3ebf0a.mov
2.


Feature/view ld json noscript

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Fixed issues

You could add a unit test,
Thank you.

I'm not sure if we should add it. What do you think @yiisoft/reviewers ?


Feat: add modifier to check if inputs are less or equal to zero.

PR#3 feat: modifier used to check if the user is trying to pass zero values.

i.e., all address and values arrays MUST have a length of 1 or more to pass.

i.e., If the length of the address or values arrays is 0 or less, the modifier should revert the transaction,
with the error ZeroValues().

@Markus-55, I wrote the unit tests for Spread.sol, This PR is ready to merge into the main branch.
Good job!


Completion no longer works

As mentioned previously, one of my machines is fine (with the latest GoSublime), however my laptop is not. Just opening in case anyone has ideas, I'll cross-check config when I'm home and see if I can find what the issue might be. It works for some packages but not others (even stdlib), my Go config etc is fine, and unchanged from before GoSublime became active again.

I'm seeing similar behaviour. Curious what it may be.

Ended up just being cross-compiling for me, I was missing the .a files, I didn't realize gocode didn't work from source.

You save my day @tj . I am using Express.js/koa.js. 👍
After go install -i , I got all .a files of my packages, and autocomplete works.
For others who encounter the same issue:
My GoSublime.settings :
{
    "comp_lint_enabled": true,
    "comp_lint_commands": [
        {"cmd": ["golint *.go"], "shell": true},
        {"cmd": ["go", "vet"]},
        {"cmd": ["go", "install", "-i"]}
    ],
    "on_save": [
        {"cmd": "gs_comp_lint"}
    ]
}


Features / Chat service

This pull request resolves #53 and adds a new microservice backend/chat.
This service has a separate database and connects to the main service backend/forum via REST API.
To check if client's token is valid, chat creates an /api/internal/check-session?token=<token> request to the forum service.
To instantly remove client from chat when user logs out, there's a new /api/internal/revoked-sessions endpoint implemented. This endpoint uses Server-sent events to stream revoked sessions in real time:
https://github.com/merpw/forum/assets/43277901/e00892e6-ae51-4d4b-aba8-8bc75bf01aa7
Here's a new scheme of the whole infrastructure:

Attention! Deployment has changed:

The old backend image is not supported anymore. It was renamed to backend-forum, so

Docker compose file on production should be changed. Maybe I'll push it later

We now have two databases with default names forum.db and chat.db. If one wants to keep using database.db for forum service, it can be done using custom DB_FILE env variable.

The new chat service can be tested using our Postman Workspace and the frontend in features/chat-frontend

I don't have permission in Postman Workspace :(

yes, you have to use Postman Desktop, it doesn't work in browser for me, even in fork

yes, you have to use Postman Desktop, it doesn't work in browser for me, even in fork

Yeah, it's a Postman web limitation :(

please update the branch :3

please update the branch :3

Done 👍

It is possible to create chat with yourself.
All the data being stored (Ids, messages etc) however it's error 500 (no rows in result set) on /chat/chatIdWithYourself
What was the idea behind that? It is unclear if we are going to implement single user chats and why???

It is possible to create chat with yourself. All the data being stored (Ids, messages etc) however it's error 500 (no rows in result set) on /chat/chatIdWithYourself endpoint
What was the idea behind that? It is unclear if we are going to implement single user chats and why???

The idea was to be able to create a group chat with only one user (or chat with yourself) like in Telegram and Discord. This is a cool feature which makes possible to use messenger as a storage for some text/files. However, this feature is not going to be implemented in real-time-forum, so it makes sense to disable it for now.

I've added some restrictions to prevent users from creating chats with users that don't exist, multiple chats between two users and chats with yourself

This is a cool feature which makes possible to use messenger as a storage for some text/files.

Yes but not sure about implementation.. because the data (f.e. in Memberships) is being duplicated in this case


Browser global export's name is wrong

Ah! What a rookie mistake. Thanks for the pull request @kennyki, I merged in your changes.
:+1:

No problem :-D


2.6 UX: Implement Cluster Tools

Add a new view to the cluster explorer - see attached PDF.
ClusterTools.pdf
This will make it easier to discover and install/upgrade cluster tools such as monitoring and logging.

1 is covered elsewhere.
I don't think we're going to do 2 - please create a separate issue if you want us to consider this post 2.6
3 needs broader discussion - this is always how its been and is difficult for us to fix in the UI alone - I would suggest creating a defect report in the rancher/rancher repo.
Moving to To Test - please move to done if you're okay with the above.


Crashes

My csgo crashes when I try to inject the cheat? I haven't edited anything except that I had to change SDK version "10.0.17134.0" but don't think it would make a difference?

That shouldnt make a difference

Could you please attach debugger and post output?

Remove configuration file if present.

I am validating files, this will make the config go away right? and if not where would I find it

Validating didn't work

Nevermind found the config

I also had same issue but I can't find the config file can you give me the path to the config file?

@gokdenizq Documents/Osiris


fix: same audio gets repeat again while playing from URL

Description

while playing a audio the normal behaviour of SoLoud is to check if there is cache for it or not and then play it, for some reason it is not working as expected

Steps To Reproduce

runs the basic example app and replace load from file to load from url

Expected Behavior

plays different sound on different url

how does i confirm it is i cloned SoLoud and removed the condition
original
 static Future<SoundProps?> loadFromUrl(String url) async {
    try {
      final now = DateTime.now();
      final tempDir = await getTemporaryDirectory();
      final tempPath = tempDir.path;
      final filePath = '$tempPath${Platform.pathSeparator}'
          '${now.year} ${now.month} ${now.day}';
      final file = File(filePath);

      if (!file.existsSync()) {
        final response = await http.get(Uri.parse(url));
        if (response.statusCode == 200) {
          final byteData = response.bodyBytes;
          final buffer = byteData.buffer;
          await file.create(recursive: true);
          await file.writeAsBytes(
            buffer.asUint8List(byteData.offsetInBytes, byteData.lengthInBytes),
          );
        } else {
          debugPrint('Failed to fetch file from URL: $url');
          return null;
        }
      }
      return _finallyLoadFile(file);
    } catch (e) {
      debugPrint('Error while fetching file: $e');
      return null;
    }
  }

my workaround
 static Future<SoundProps?> loadFromUrl(String url) async {
  try {
    final now = DateTime.now();
    final tempDir = await getTemporaryDirectory();
    final tempPath = tempDir.path;
    final filePath = '$tempPath${Platform.pathSeparator}'
        '${now.year} ${now.month} ${now.day}';
    final file = File(filePath);

    // ignore: literal_only_boolean_expressions
    if (true) {
      final response = await http.get(Uri.parse(url));
      if (response.statusCode == 200) {
        final byteData = response.bodyBytes;
        final buffer = byteData.buffer;
        await file.create(recursive: true);
        await file.writeAsBytes(
          buffer.asUint8List(byteData.offsetInBytes, byteData.lengthInBytes),
        );
      } else {
        debugPrint('Failed to fetch file from URL: $url');
        return null;
      }
    }
    return _finallyLoadFile(file);
  } catch (e) {
    debugPrint('Error while fetching file: $e');
    return null;
  }
}

Thanks for reporting this!
Sorry for the late but my PC motherboard burned!!! (not this lib fault :) )
I would change the generated temp file name using the String url hash code like replacing this
final filePath = '$tempPath${Platform.pathSeparator}'
        '${now.year} ${now.month} ${now.day}';

with this
final filePath = '$tempPath${Platform.pathSeparator}'
          '${shortHash(url)}';

doing so the url string becomes almost unique and the sound remains cached.
Let me know if this is working for you


feature request: change the way tinyurl handles error

Sometimes, tinyurl will fail and output a error. If tinyurl returns Error have RSS post the link instead
<+gNews> [Huffington] An Open Letter To The Loudest Person In The Room → Error

this is more a bug than a feature request. :-)


Doc/rfc9000

Add RFC9000 translation

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.贺志平00041831 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.


release: v2.0 :tada:

thanks for https://github.com/oven-sh/setup-bun/pull/76
Fixes https://github.com/oven-sh/setup-bun/issues/79
Fixes https://github.com/oven-sh/setup-bun/issues/81

Hello there, I'd like to ask something: (why) is it intended that the bun-version-file is called .bumrc instead of .bunrc? 🤔
Other popular projects often use their name + rc, e. g.: .eslintrc.json, .prettierrc, .nvmrc, so I believe this might just be a typo?

Hello there, I'd like to ask something: (why) is it intended that the bun-version-file is called .bumrc instead of .bunrc? 🤔 Other popular projects often use their name + rc, e. g.: .eslintrc.json, .prettierrc, .nvmrc, so I believe this might just be a typo?

I think it's because in the original pr - https://github.com/oven-sh/setup-bun/pull/76 it is meant like https://github.com/owenizedd/bum

Oh okay, that makes sense - thanks for adding .bunrc as a second option then. :)

Why .bunrc when bunfig.toml exists? If the goal is to just specify the bun version and no further config, why not .bun-version instead of .bunrc?

Sure, we can do that ;)

Could it be a good idea to always check for a .bun-version file and use the version from there, even without any bun-version-file input being passed?
I don't think anyone would have such a file and not want the version in there to be used.

Could it be a good idea to always check for a .bun-version file and use the version from there, even without any bun-version-file input being passed? I don't think anyone would have such a file and not want the version in there to be used.

That's true but it leads to hidden behaviour and I'm not sure if that's what we want

That's true but it leads to hidden behaviour and I'm not sure if that's what we want. Probably can be done by setting bun-version-file to .bun-version by default

Setting it as default might make sense, though then it'd be better to check for a bun-version input first/with priority (not sure which input would override the other one right now).
That would only cause hidden behavior if there is no bun-version nor bun-version-file input, but a .bun-version file exists.

Ready to merge, tomorrow

A small note in the release on why you decided this is major would be appreciated

A small note in the release on why you decided this is major would be appreciated

I’m curious too

So it's not possible to have it via an argument? It feel bad to have to add an almost empty file to lock the version used (and probably it will be hard to share this file with the what manage your production version (like docker))


Addition of option to allow empty row groups in pyarrow

While our use case is not common, I was able to find one related request from roughly a year ago. Could this be added as a feature?
https://issues.apache.org/jira/browse/PARQUET-1047
Motivation
We have an application where each row is associated with one of N contexts, though a minority of contexts may have no associated rows. When encountering the Nth context, we will wish to retrieve all the associated rows. Row groups would provide a natural way to index the data, as the nth context could naturally relate to the nth row group.
Unfortunately, this is not possible at the present time, as pyarrow does not support writing empty row groups. If one writes a pyarrow.Table containing zero rows using pyarrow.parquet.ParquetWriter, it is ommited from the final file, and this distorts the indexing.

JIRA created.
https://issues.apache.org/jira/browse/ARROW-3020


feat: add specific ServiceAccount and update rbac w/same

Fixes: #23
Closes: #17
Signed-off-by: Piaras Hoban<EMAIL_ADDRESS>

Thank you, @phoban01
Just some naming convention to match the project's name, please.

Thanks @chanwit; all updated to reflect correct naming convention.

Thank you so much @phoban01 :1st_place_medal:

@phoban01 I'll release an RC so that we can test this feature on an EKS.


butane: New example

We have a lot of useful syntax and semantics in Butane, and it
helps tie our story to Ignition.
(What would be interesting is a tool that "splits" an butane/Ignition
into things like storage that need to be firstboot config, and
builds the rest as a container)

(We could also demo extensions here...it's currently experimental though)


updated hero page + clean up/ui update

quick push to update the hero page + minor updates

expected failure to build - in the process of getting fixed. will force merge.


pygnmi no longer installable via pip since 0.8.0

The new requirements of 0.8.0 seem to break pip. 'protobuf --no-binary=protobuf' does not seem to be a valid dependency in setup.py.
quoth:/tmp$ python3 -m venv pygnmi-venv
quoth:/tmp$ . pygnmi-venv/bin/activate
(pygnmi-venv) quoth:/tmp$ pip install pip -U >/dev/null
(pygnmi-venv) quoth:/tmp$ pip --version
pip 22.2 from /tmp/pygnmi-venv/lib/python3.8/site-packages/pip (python 3.8)
(pygnmi-venv) quoth:/tmp$ pip install pygnmi
Collecting pygnmi
  Using cached pygnmi-0.8.0.tar.gz (21 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      error in pygnmi setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Invalid requirement, parse error at "'--no-bin'"
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Hey @sebageek ,
it was indeed. It is fixed in the latest hotfix <IP_ADDRESS> published to pypi few minutes ago and will be also incorporated into the subsequent releases.
Best,
Anton

Working properly since 0.8.2

Thanks, works again.


Component rendering/refresh does not work in SPA

The smart-edit.service.renderComponent does not render or refresh  a component.
When the component is changed in SmartEdit it calls renderComponent with one attribute - the slot id that contains the changed component. But the slot is not refresh.
Same problem happens with newly added component.
Environment Details

Spartacus:  latest
Browser: Chrome latest

Steps to Reproduce (Edit)

Go to SPA storefront
Open any component (ex. Paragraph)
Change the data in the component
Save
Nothing has been changed on storefront (only browser refresh helps)

Steps to Reproduce (Add)

Go to SPA storefront
Add new paragraph component on the storefront
Save
New component is not visible on storefront (only browser refresh helps)

I cannot reproduce it on my local. Slot is re-rendered if I add/remove component; and component is also re-rendered if I edit it.

I will close this ticket, because Stepan said: When I build smartedit in production mode it starts working.

Unfortunately the problem is not related to building the app in production mode.
Now we understand why the rendering works for Wei and does not work for anyone else. When the Redux extension is enabled the rendering on Spartacus side works fine and when it's disabled the rendering stops working. So SPA team should do the following: disable Redux extension and try to debug the reRendering functionality.

To QA/code reviewer:
To test this ticket, you need disable the redux extension in browser.
In smartedit, go to homepage. You can edit/add/remove any components. The component should be refreshed automatically

They are still seeing issues (see https://jira.hybris.com/browse/CMSX-8739) but i'm trying it out

Adding, Editing and Removing a component is rendered properly on the storefront now (with redux extension disabled). Tested with the FAQ page on dev2 server.


Add LWTRetryPolicy interface

RetryPolicy may want to return different decisions from GetRetryType depending on whether query is LWT or not - to prevent executing LWT on non-primary replica.
This is not possible with current interface, because GetRetryType doesn't know the query type.
This PR introduces new interface, LWTRetryPolicy. If configured retry policy also implements LWTRetryPolicy, then methods from LWTRetryPolicy will be called for LWT statements instead of methods from RetryPolicy.
There are alternative approaches to this issue:

Introduce LWTRetryPolicy as another field in Session and Query: requires changes in user code.
For LWT queries ignore GetRetryType and retry on the same host: it's less configurable

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

ASAIK LWT Queries are run in SERIAL or LOCAL_SERIAL, so AttemptLWT should avoid q.SetConsistency( for LWT
And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

AFAIK LWT Queries are run in SERIAL or LOCAL_SERIAL CL, so AttemptLWT should avoid q.SetConsistency( for LWT And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

Good catch about this q.SetConsistency.

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

AFAIK LWT Queries are run in SERIAL or LOCAL_SERIAL CL, so AttemptLWT should avoid q.SetConsistency( for LWT And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

Good catch about this q.SetConsistency.

But in that case it's no longer DowngradingConsistencyRetryPolicy, that's why I thought it would be best to skip it for now.
Btw what is the use case for this policy? If someone is fine with using lower consistency level, then why use the higher one at all?

@wprzytula failed test is flaky according to @sylwiaszunejko , could you rerun CI?

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

AFAIK LWT Queries are run in SERIAL or LOCAL_SERIAL CL, so AttemptLWT should avoid q.SetConsistency( for LWT And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

Good catch about this q.SetConsistency.

But in that case it's no longer DowngradingConsistencyRetryPolicy, that's why I thought it would be best to skip it for now. Btw what is the use case for this policy? If someone is fine with using lower consistency level, then why use the higher one at all?

The idea is to use a higher consistency level normally, but as an exception allow lower consistency when higher cannot be immediately obtained because of write/read timeout. This is to cope with spikes of load over short time that would otherwise result in timeouts due to requested consistency not reached in time.

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

AFAIK LWT Queries are run in SERIAL or LOCAL_SERIAL CL, so AttemptLWT should avoid q.SetConsistency( for LWT And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

Good catch about this q.SetConsistency.

But in that case it's no longer DowngradingConsistencyRetryPolicy, that's why I thought it would be best to skip it for now. Btw what is the use case for this policy? If someone is fine with using lower consistency level, then why use the higher one at all?

The idea is to use a higher consistency level normally, but as an exception allow lower consistency when higher cannot be immediately obtained because of write/read timeout. This is to cope with spikes of load over short time that would otherwise result in timeouts due to requested consistency not reached in time.

Applications choose a consistency level used that is required for their correctness. If the application is still correct with lower consistency level, then it can use this lower level. If it is not, then downgrading consistency will make the application not correct.
Anyway, I don't see a good semantics for LWT for this policy. Imo we should skip this, it's not important to solve now.

There is one more policy left to cover - DowngradingConsistencyRetryPolicy

There is. I'm not sure how it should be modify, I'd really like some advice

IMO the only change needed for LWT case is replacing the only occurence of RetryNextHost in GetRetryType with Retry.

AFAIK LWT Queries are run in SERIAL or LOCAL_SERIAL CL, so AttemptLWT should avoid q.SetConsistency( for LWT And as @wprzytula suggested GetRetryType should not go for Retry where it does RetryNextHost

Good catch about this q.SetConsistency.

But in that case it's no longer DowngradingConsistencyRetryPolicy, that's why I thought it would be best to skip it for now. Btw what is the use case for this policy? If someone is fine with using lower consistency level, then why use the higher one at all?

The idea is to use a higher consistency level normally, but as an exception allow lower consistency when higher cannot be immediately obtained because of write/read timeout. This is to cope with spikes of load over short time that would otherwise result in timeouts due to requested consistency not reached in time.

Applications choose a consistency level used that is required for their correctness. If the application is still correct with lower consistency level, then it can use this lower level. If it is not, then downgrading consistency will make the application not correct. Anyway, I don't see a good semantics for LWT for this policy. Imo we should skip this, it's not important to solve now.

See java driver documentation for reference.


[Feature-13428][Resource Center] Add support for writing task logs to Google Cloud Storage

Purpose of the pull request

close: #13428

Brief change log

Add support for writing task logs to Google Cloud Storage

Verify this pull request
UT and manually tested

configure in the common.properties

resource.storage.type=GCS
# the location of the google cloud credential, required if you set resource.storage.type=GCS
resource.google.cloud.storage.credential=/path/to/credential
# gcs bucket name, required if you set resource.storage.type=GCS
resource.google.cloud.storage.bucket.name=<your-bucket>

Upload files and directory in the resource center

Check files in the GCS

I will add related LICENSEs later.

Hi, @zhongjiajie , I've updated the known_dependencies, could you please help review this?


DOWNLOADING

Steps to reproduce
I have a hard time downloading dubbed anime videos so I can watch offline
Expected behavior
.
Actual behavior
.
Mangayomi version
.
Device
.
Other details
.
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.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

This is kinda an issue with gogo and aniwave. aniwave downloading it slightly buggy and gogo just doesnt start.

Fixed !!


Update process_data.sh to be compatible with the latest datasets releases

The process_data.sh script under the master branch (commit https://github.com/spine-generic/spine-generic/commit/bb09d74049fdda4043356f4157244e92cbeff06a) is currently incompatible with the latest release of the data-multi-subject dataset (r20230223: https://github.com/spine-generic/data-multi-subject/tree/r20230223).
Points to fix (not exhaustive list):

remove _rms, _RPI_r, etc suffixes from filenames because .nii.gz and .json files were renamed:

update MTS filenames (suffixes updated in https://github.com/spine-generic/data-multi-subject/pull/135) -- related to https://github.com/spine-generic/spine-generic/issues/272
fix atlas labels
make sure the process_data.sh script is also compatible with data-single-subject

Some statistics:
ls derivatives/labels/*/*/*T2w_seg-manual.nii.gz | wc -l   267
ls derivatives/labels/*/*/*T2star_seg-manual.nii.gz | wc -l  266
ls derivatives/labels/*/*/*T2star_gmseg-manual.nii.gz | wc -l  18
ls derivatives/labels/*/*/*T1w_seg-manual.nii.gz | wc -l  267
Thus, I assume strings like RPI_r or rms should be removed from filenames of data_processed files.
Contrary, it means that proces_data.sh will never execute sct_deepseg_sc for T2w, T1w and almost never for T2star. And, qunatitative results will everytime be proportional to existing manual segmentations. So that raise the question: Do we want process_data.sh to behave that way everytime?

Utilizing existing _seg-manual, gmseg_manual and _labels_manual (commit 9cd6af1), the process_data.sh ended with error for following 7 scans:
sub-brnoUhb02 (T1w labeling)
sub-brnoUhb07 (T1w labeling)
sub-brnoUhb08 (T1w labeling)
sub-geneva01 (T1w labeling)
sub-oxfordFmrib04 (MTS analysis sct_register_multimodal)
sub-oxfordOhba02 (sct_dmri_moco)
sub-tokyoIngenia06 (T1W labeling)
Errors were related to T1w labeling in 5 cases, multimodal registration in MTS analysis in 1 case, and dMRI preprocessing in 1 case. I am going to check if segmentation fit the images in the 5 T1w files.

Processing of sub-brnoUhb scans fails due to mismatched T1w scan and its manual segmentation as reported here


fix: update path to main file in package.json. Fixes #192

@vriad Not sure why this was changed in first place - perhaps it was an accident, as I'm unfamiliar with this syntax.

Bug introduced in https://github.com/vriad/zod/commit/31a8544d42e4f30aafd36a48d457c5cbf0018b6b

Whoops...weird. Thanks for the PR! Merged, fixed, and published to NPM.


pip install django-tgbot in host

Hi,
I try to install Django-tgbot on my host(Linux host), but I face this problem

I solved this problem
.
in host:
clone to this repository and then
python setup.py install
.
or in VPS:
no problem occurs when using 'pip install Django, but 1st solution still work


VSCode installation name in Windows (and perhaps for other OS)

OS Version: Windows 10

-- Sorry for the English, I used Google Translator --
I noticed that the Windows installer's name is now VSCodeSetup-ia32-1.13.1 and VSCodeSetup-ia32-1.14.0-insider.
I particularly do not remember seeing some installer with 'ia32' or 'ia64'.
It would be better to change to:
- X32: VSCodeSetup1.13.1:x: or VSCodeSetup :white_check_mark:  / VSCodeSetup-insider  :white_check_mark:

 Since we can install VSCodeX32 on Windows X64

 - X64: VSCodeSetup1.13.1_x64 :x: or VSCodeSetup_x64 :white_check_mark: or VSCodeSetup :white_check_mark: / VSCodeSetup-insider :white_check_mark: or VSCodeSetup-insider_X64 :white_check_mark:

 There are programs that do not even show the architecture. Then he would not think it strange not to show. Since the size of the installer varies, the 'X64' is greater than 'X32', the vast majority (or total).

 Load the version number or not? I am not for or against, but I would vote for not to bring. When smaller the better. (Except for something very specific.)

 See the installation of SQL Server, Service Pack for Windows and Microsoft Office, they bring 'X32 and X64' instead of 'ia'.

Sorry, there doesn't seem to be a good enough reason to readdress this.

-- Sorry for the English, I used Google Translator --
@joaomoreno There is no official documentation, but in my view a few points can be taken:
1. 'X32' or 'X64' is much more used. Placing 'ia32' or 'ia64' soon connects to 'Intel Architecture'. Soon amd32 or amd64 links the company.
1.1.  On the website itself uses x32 (x86) or x64 to inform the OS version, why not use it in VSCode? Many programs use this. Much more intuitive. The system itself reports platform / architecture x32 or x64.
1.2.  So much more intuitive that it seems that changed the message in case #29537  of 'ia32 or ia64' to '32 bits or 64 bits'. Or it could also be 'x32 or x64'.
1.3. Do not tell what architecture is for the x32 installer, leaving only the name, I do not know what can be harmful.
2. Before the installer did not bring the version. This is good because it always makes new users fetch the latest version. Staying informed the version would be more for year to year, or long time.
2.1.  Up because (at least on Windows) in Setup properties or simply leaving the mouse on the installer it shows the version information. This again makes it unnecessary to put the version in the name.
2.2.  It is a suggestion (tell me if I think the idea that I open a case for her is legal). When trying to install an old version of VSCode inform the user (since it had internet connection) that there is a newer version and if you would like to install the new version or continue the version that is and update later (being that when downloading This new version should not redirect to the site, the installer should be able to put in temporary files).
I'm waiting for your opinion again.


main property of bower.json is incomplete

Main Property of the bower.json file is pointing to only bootstrap.less which in return references other less files. This is causing tools like mimosa to copy only bootstrap.less to project folder.
I think it should also include the referenced less files.

+1


Yield when running the GC

Issue summary

The garbage collector runs in a tight loop and has no natural yield points. This means it blocks the tokio runtime (even though it is marked as async) and prevents Forest from doing a graceful shutdown. Sensible yield points can be inserted to get around this problem. Feel free to suggest other solutions, though.
Other information and links

GC is being replaced so this is no longer relevant.


Spelling fix.

Hi @davenewza, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@mimig1

#sign-off Looks good, thanks for the fix! @rmca14


Re-factor DirDiffUtil.getDirDiff  to traverse and test files once.

Summary
Re-factor DirDiffUtil.getDirDiff to minimize calls to sun.nio.fs.*
Details
Profiling a real-world job showed ~38% of the time being spent in DirDiffUtil.getDirDiff for a given profile snapshot.  Investigating it seems that the call to DirDiffUtil.areSameFile is the primary cause of DirDiffUtil.getDirDiff showing up high on this particular profile.  Looking at the code there is the following comment:
  // TODO MED shesharm: this compares each file in directory 3 times. Categorize files in one traversal instead.

Re-factored creation of the lists filesToUpload, filesToRetain, and filesToRemove to iterate on the files once which reduces the number of times DirDiffUtil.areSameFile is called.
The re-factor should reduce the number of calls by reducing the number of calls to areSameFile.  it is also noticed that inside of areSameFile there are calls to getting owner and user.  The expected number of users/groups is very small and the repeated calls to get the name from the id can be cached effectively.  Overload creation of areSameFile to cache calls to get user and owner.
JIRA=SAMZA-2783
Testing
./gradlew clean && ./gradlew test

Updated PR from memoizing results of areSameFile.test to re-factoring population of filesToUpload, filesToRetain, and filesToRemove.  The resulting code is smaller and makes the logic of when each list is populated clearer.

Thanks for the improvements @asautins. cc @shekhars-li to review.
FMI, is there something atypical about the job / environment that causes the getDirDiff() call to be so expensive? This should only happen once per task per commit, which is typically only once a minute, so 38% of time seems very large. Optimizations make sense regardless.

I agree that the profile doesn't make sense.  We've profiled multiple times and all show getDirDiff to show higher than one would think if it were to run once a minute with a few files.  A few things that come to mind that may contribute:

Beam - The job is a beam job, not just a low-level or high-level samza job.  I wouldn't think that would matter.
200k/sec - The job process ~200k records/second from 3 topics.  While that's not a lot, it's more than a little.
Join - The job joins a stream following the model in the Beam Programming Guide section 11.5.1. Joining clicks and views.
GC using timers - There is also a timer use for garbage collection following the pattern in the Beam Programming Guide section 11.4 garbage collecting state.
~15 stateid/~5 event timers -  So more than a few but less than a lot.

Will update the ticket if we understand why we currently see getDirDiff so high in our profiles.

@asautins For context, the purpose of adding file metadata to the snapshot during upload is to be able to check if we need to restore the file during a restart (e.g. local file may be stale, or for a different instance of a job). In practice, the job should have a stable uname / group name in the cluster, and local state directories should be isolated between job instances on each host, so removing the uname/group check here is quite reasonable. Although removing it from the metadata while maintaining rollback compatibility is not trivial.
For the latest commit, would prefer keeping FileMetadata stateless (i.e. not use static fields). It may be created concurrently for several files. IIRC it is also serialized/deserialized as JSON
Changing it to maintain uid/gid alone will not work since they can be different across hosts in a cluster for the same user / group.

Thanks for the context and makes sense.  Sorry for being over zealous and thanks for the context, especially on the statelessness and concurrency.

Thanks a lot for the patch and the UTs along with it @asautins. Looks good to me!

@prateekm can you please merge it?

FYI addessed failed workflow by adding license information to new file.

cleanup checkstyle errors on ./gradlew check


Be more specific on client usage

For example, http://docs.feathersjs.com/clients/socket-io.html does not mention that it is for plain websocket usage so it is not clear that you should read this instead of using the Feathers client.

What do you think about moving those sections for REST, Primus and Socket.io to guides instead? For example, this section. I think it will make the client side much more digestable for people.

Closed by 68bb9ef5e1efc847d4b1889d0cd983f42ab24dc9


Approve/Decline images using GPIO/keyboard

Allow more flexible configuration of gpio and keyboard input to approve/decline images.

reference to another post: https://github.com/photobooth-app/photobooth-app/issues/203#issuecomment-2199200479

Yes, as i said in the other topic, It would be nice, that you could controll the box with a few buttons.
Touch screens have a big dissadvantage in "Public" areas, because everybody touches it, even with dirty fingers and then there is sauce on the screen and so on, especially, because this device will be used at a party, with drunk people.


Rewrite CEMS archiver to use API

See #68. This PR modifies the API guide provided for bulk data access here: https://github.com/USEPA/cam-api-examples/blob/main/Python/bulk_data_api_demo.py#L9
The sandbox deposition created by this PR is here: https://sandbox.zenodo.org/record/1224605
To do:

[ ] Fix 'connection closed' errors
[ ] Do we want to add our own date range here, or just download all available data - present?
[ ] Add in-line documentation
[ ] Very archiver working as expected
[ ] Run production for 2022

Still to resolve:
ImportError while loading conftest .../PUDL/pudl-archiver/tests/conftest.py'.
tests/conftest.py:6: in <module>
    from pudl_archiver.frictionless import DataPackage
.env_tox/lib/python3.10/site-packages/pudl_archiver/__init__.py:28: in <module>
    ARCHIVERS = {archiver.name: archiver for archiver in all_archivers()}
.env_tox/lib/python3.10/site-packages/pudl_archiver/__init__.py:24: in all_archivers
    __import__(module)
.env_tox/lib/python3.10/site-packages/pudl_archiver/archivers/epacems.py:69: in <module>
    parameters = {"api_key": os.environ["EPACEMS_API_KEY"]}  # Set to API key
../../../../mambaforge/envs/pudl-cataloger/lib/python3.10/os.py:680: in __getitem__
    raise KeyError(key) from None
E   KeyError: 'EPACEMS_API_KEY'

Running into some weird hiccups with Zenodo on this archiver. Running the full archiver successfully downloads/uploads all datasets, but produces the following error when trying to upload the datapackage.json:

Then, when I try to run the archiver again on that archive, I get a "list index out of range" error and the request just returns an empty file list. The archive uploads to Zenodo but the datapackage file is corrupted.
@zschira Is this an error you've encountered elsewhere in dealing with the archivers, or do you have any thoughts on what piece of the puzzle to try to debug here?

Did some digging, and it looks like the we're getting bad responses from the api, and so what's actually in the CSV files in just the JSON from the error response. We've set the aiohttp session to not raise exceptions on bad responses, so this kind of quietly fails right now, which is definitely not ideal, and I'll rethink how we should handle bad responses. I'm still not 100% sure why/if this is causing the weird zenodo errors, but I think this is a good place to start.
I assumed the bad responses were a result of not passing the api key to the requests, but I changed it to pass the key, and it's still giving bad responses. I'll continue digging on this and see what I can come up with.

Still getting Connection closed errors even with a concurrency of 1. Something must still be wrong here.


feat: Support create persistent cluster

@fengye87 this PR is ready for reviewing, but before merge it need wait cluster-api-provider-virtink new release that support create persitent cluster.


Height not changing when window is resized (stays at shrink state and not expanding)

A parent page, let's say, www.maingames.com has an iframe page happywheelsgames.com and loads perfectly using this plugin. The frame page has a modal inside, and changes the body height in every click of the anchor links inside (just doing show and hide here displaying lists and grid of data).
However, the problem occurred when the user loads the site, in minimized window (not full screen), then opens the modal (and also after they closed it), and maximizes the browser window, it stays on its "shrink" state and not expanding the whole iframe like it used to.
Here's my code:
`
var windowHeight = window.innerHeight || document.documentElement.clientHeight;
var headerHeight = $(".header").outerHeight();
var footerHeight = $(".footer").outerHeight();
var contentHeight = windowHeight - (headerHeight + footerHeight);
$("iframe.gamesData").on("load", function() {
$(this).iFrameResize({
heightCalculationMethod: 'max',
minHeight: contentHeight,
enablePublicMethods: true
});
});
`
I also tried using lowestElement and taggedElement but it's not resizing even on the loading of the page. I also tried inserting another iFrameResize function inside a "$(window).on("resize", function ()" but it returns a warning saying something like "iFrame already setup. Ignore [FrameName]", and not actually resizing. I believe there's already a "resize" function inside the plugin, pls correct me if I'm wrong.
Any suggestion or piece of advice is very much appreciated.

Thanks!

You can force the iFrame to resize from the parent page as follows.
document.getElementById('myIFrame').iFrameResizer.resize();

Thanks for the reply! Sadly, the problem still occurs!
Yes, I did put the code below and forced the frame to resize from its parent but it's not working on my end.
Btw, I put it inside a resize event on my JS.
Please advise and thank you!

I edited the code and added the iFrameResize to a separate function with a parameter so it'll dynamically change the minHeight.
What I did so far:
`var windowHeight = window.innerHeight || document.documentElement.clientHeight;
var headerHeight = $(".header").outerHeight();
var footerHeight = $(".footer").outerHeight();
var contentHeight = windowHeight - (headerHeight + footerHeight);
function callFrame (content) {
var newHeight = content;
$("iframe.gamesData").iFrameResize({
heightCalculationMethod: 'lowestElement',
minHeight: newHeight ,
});
}
$(window).bind('resize', function() {
var windowHeight = window.innerHeight || document.documentElement.clientHeight;
var contentHeight2 = windowHeight - (headerHeight + footerHeight);
callFrame (contentHeight2);
});
`
I almost thought it's perfect but yeah, the console warning saying "iFrame already setup. Ignored" something pops out again.
Is there a way I can do this from your perspective/iFrameResize perspective? I tried using the one you mentioned (document.getElementById('myIFrame').iFrameResizer.resize();) but it says undefined function.
Thanks!

if i've well understand your problem, to solve you should change the heightCalculationMethod for example to:
heightCalculationMethod:'bodyScroll'
but there are more if it do not fit your needs. This should resolve.

@rustedsoul you have to change myIFrame to the id of your iFrame.

I have got same issue as @rustedsoul.
URL change, the resize works well, but when the content height change (using angular to change the UI-Route state) it does not resize.
[iFrameSizer][corepratice-iframe] Trigger event: Mouse Up
VM10328 iframeresizer.contentwindow.js:150 [iFrameSizer][iframe] Parsed 338 HTML elements
VM10328 iframeresizer.contentwindow.js:150 [iFrameSizer][iframe] Element position calculated in 2ms
VM10328 iframeresizer.contentwindow.js:150 [iFrameSizer][iframe] No change in size detected

If you can create a simple test case I will have a look. Expect their might be some race condition happening.

I am sorry, your IFrameResizer has been fine.
I have found out a problem from my javascript. It conflicts with yours.


Increasing test coverage and reducing console.log() spam

:tada: This PR is included in version 3.5.2 :tada:
Your semantic-release bot :package::rocket:


feat(plot): Use GazeDataFrame in tsplot

Codecov Report
Patch coverage: 81.25% and project coverage change: -0.19 :warning:

Comparison is base (b989872) 100.00% compared to head (31303e8) 99.81%.

Additional details and impacted files
@@             Coverage Diff             @@
##              main     #338      +/-   ##
===========================================
- Coverage   100.00%   99.81%   -0.19%
===========================================
  Files           44       44
  Lines         1630     1638       +8
  Branches       354      357       +3
===========================================
+ Hits          1630     1635       +5
- Partials         0        3       +3

Impacted Files
Coverage Δ

src/pymovements/plotting/tsplot.py
95.38% <81.25%> (-4.62%)
:arrow_down:

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


fix/test: fix Clippy lints and a bug that Clippy found

The upper_limit test actually compared () with () instead of the
deserialised vectors.

This change is

r? @canndrew
(maidsafe_highfive has picked a reviewer for you, use r? to override)

r? @ustulation

Reviewed 7 of 7 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


improve change http to https in doc

Proposed changes
Issue Number:  close #20730
[Feature] Perfect docs
In the source code compilation of official documents, the source code of window is compiled, and the source code for downloading doris is git clone http://github.com/apache/doris.git. I think http can be changed to https, git clone https://github.com/apache/doris.git
屏幕截图 2023-06-13 103604
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

lgtm

@xiaokang

@xiaokang hello，Are you still considering merging?

Are you still considering merging?


ModuleNotFoundError: No module named '_pywrap_tensorflow'

I was able to install it on windows, but as soon as any Python related command is executed, this exception is thown "ModuleNotFoundError: No module named '_pywrap_tensorflow'".
Is there anything else I have to do?

Never mind, I gave up on it.


Add stream::Zip trait

This is a core iteration "order of execution" operation, enabling people to author:
after
let s1 = async_iter::repeat(0).take(5);
let s2 = async_iter::repeat(1).take(5);
let s3 = async_iter::repeat(2).take(5);

for await (n1, n2, n3) in (s1, s2, s3).zip() {
    assert_eq!((n1, n2, n3), (0, 1, 2));
}

This is better than the nested tuple approach of non-trait based zip.
Design
pub trait Zip {
    /// What's the return type of our stream?
    type Item;

    /// What stream do we return?
    type Stream: Stream<Item = Self::Item>;

    /// Combine multiple streams into a single stream.
    fn zip(self) -> Self::Stream;
}

Tasks

[x] Zip trait https://github.com/yoshuawuyts/futures-concurrency/pull/73
[ ] impl Zip for vec
[ ] impl Zip for array
[ ] impl Zip for tuple
[ ] benchmarks

For the Zip variant: we may want to skip directly ahead to #22 in terms of implementation, creating an output slot of Container[MaybUninit<T>] where we write into, and then mem::swap on each iteration.
Metadata would need to be stored in an accompanying PollState slot. The main things to keep an eye will be to:

ensure to implement the PinnedDrop trait to drop memory in the case of a cancellation
switch between PollState::Pending and PollState::Ready while data is actively being yielded, and only switch to PollState::Consume at the end.

The semantics of Zip are that if at any point one of the streams yields Poll::Ready(None), all other streams are cancelled. We should create a case where one stream yields more times than the other streams so that we can exercise miri's checkers during CI.

Filed a concern in https://github.com/rust-lang/rust/issues/80094 since its existence requires us to author:
let mut s = Zip::zip([a, b, c]);

instead of:
let mut s = [a, b, c].zip();