Allow instantiation with arbitrary arguments.

Crap, forgot about this.
So basically you instantiate your chart with an auth.User for example, that the get_data method uses. Now where does that user come from when you render in the AJAX method?
... or at the very least document this.

Solved by rendering into the page. Not ideal for long running charts, but those shouldn't really even be in an AJAX request, use a reporting task/scheduled thing.

Solved by rendering into the page. Not ideal for long running charts, but those shouldn't really even be in an AJAX request, use a reporting task/scheduled thing.


Files logs missing

Tosker does not put the install.log stop.log uninstall.log file in the /tmp/tosker/{app}/{component} directory.
These are the (usuall) files store in the directory.
configure.log  configure.sh   create.log     install.sh     start.log      start.sh       state          stop.sh        uninstall.sh

There is a log file for each one of the lifecycle operation of a software component. Thus they are:  create.log, configure.log, start.log, stop.log, delete.log.


Containerd failing to pull image

Details
Error:
Failed to pull image "codercom/code-server:3.9.0": rpc error: code = FailedPrecondition desc = failed to pull and unpack image "docker.io/codercom/code-server:3.9.0": failed commit on ref "layer-sha256:1860da6d8902305631883be7a65a6a60d5f24be9048bf82c8c454ac2748d3950": unexpected commit digest sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, expected sha256:1860da6d8902305631883be7a65a6a60d5f24be9048bf82c8c454ac2748d3950: failed precondition

A corresponding temporary solution can be found here to solve this issue: https://github.com/containerd/containerd/issues/3974
I followed the instructions and removed the /var/lib/containerd/io.containerd.content.v1.content/ingest/ directory and then needed to bounce my pod to initiate another image pull and it worked.


Bug - Conditional updates can modify resource body such that conditional URL no longer applied.

Describe the bug
Conditional updates are behaving inconsistently with respect to the supplied resource not satisfying the conditional URL.
Please refer to:

https://hl7.org/fhir/R5/http.html#cond-update

To Reproduce

Create a new Patient, for example:

POST https://hapi.fhir.org/baseR4/Patient

{
    "resourceType": "Patient",
    "identifier":
    [
        {
            "system": "http://kookaburra.text/id",
            "value": "kookaburra1"
        }
    ],
    "gender": "male",
    "birthDate": "1980-07-03"
}

Attempt to conditionally update this Patient with an incorrect identifier.value in the conditional URL:

PUT https://hapi.fhir.org/baseR4/Patient?identifier=http://kookaburra.text/id|kookaburra2

{
    "resourceType": "Patient",
    "identifier":
    [
        {
            "system": "http://kookaburra.text/id",
            "value": "kookaburra1"
        }
    ],
    "gender": "male",
    "birthDate": "1980-07-03"
}

This fails as expected with a HAPI-0929.

Attempt to conditionally update this Patient with an incorrect identifier.value in the body:

PUT https://hapi.fhir.org/baseR4/Patient?identifier=http://kookaburra.text/id|kookaburra1

{
    "resourceType": "Patient",
    "identifier":
    [
        {
            "system": "http://kookaburra.text/id",
            "value": "kookaburra2"
        }
    ],
    "gender": "male",
    "birthDate": "1980-07-03"
}

This succeeds but it shouldn't. Note the conditional URL and resource body no longer match.
Expected behavior
Step 3 above should also result in a HAPI-0929 because the supplied resource does not satisfy the conditional URL.
Screenshots

Environment (please complete the following information):
GET https://hapi.fhir.org/baseR4/metadata

	"software": {
		"name": "HAPI FHIR Server",
		"version": "6.9.3-SNAPSHOT/7f15e62e20/2023-09-05"
	},

Additional context
Meow.

A couple things:

You are getting the 929 error code as, since there are no matches, you are creating version 1 of a resource, which causes the conditional create validation to occur.
Conditional Updates are permitted to invalidate the conditional URL post-update as done in your Step #3. This is not strictly defined in the spec, and the comment here BaseHapiFhirDao.java indicates that we permit it.

I recommend we do what the comment suggests, and add a toggle to control this behaviour for users who wish to prevent this.

Thanks, @tadgh. Will update the ticket to treat as a feature request. Appreciate your help!

@dmuylwyk this could be lateral to the feature main point but could be the subject of a new bug.
in 2. you mentioned: Because no such resource exists in the repository, this is treated as a conditional create. However, according to the spec, a ccreate must include an If-None-Exist: [search parameters] header, which is not included here, so maybe this shouldn't be treated as a ccreate?


minor fix to agentic_rag_toolservice example

this pr makes a couple of small tweaks to the agentic_rag_toolservice.ipynb example to smooth out the setup process.
what’s changed:

add llama_index install to notebook

added %pip install llama_index in a jupyter cell.
fixes modulenotfounderror when trying to use llama_index.

update .gitignore for ide settings

added .idea/ to .gitignore.
keeps jetbrains ide settings out of version control, so everyone's configs stay local.

clean up .idea directory

ran git rm -r --cached .idea/ to remove the .idea folder from the repo.
keeps the repo clean by getting rid of those ide files that snuck in.

these are just small changes to keep the repo tidy and make setup a bit easier. let me know if you need anything else!

Thanks @alexfazio !


Use centos/stream9 vagrant box

These are finally published on Vagrant Cloud which means it can automatically retrieve the latest version.
When I just tested this elsewhere I couldn't get the latest image to boot, so perhaps this isn't ready yet. Marking as draft until I can verify it works.

Current image is broken due to https://bugzilla.redhat.com/show_bug.cgi?id=2227722


update design for version 2.5

[x] add fontawesome
[x] expand footer (#436)
[x] add publications page (#435)
[x] remove contact page, expand team section on about
[x] add animated buttons: https://github.com/IanLunn/Hover

Starting point:

Closes #436, closes #435
Original pull request by @bmesuere on Sun Jan 18 2015 at 15:15.
Merged by @bmesuere on Sat Feb 14 2015 at 14:14.

Original comment by @bmesuere on Fri Feb 13 2015 at 19:58.

Original comment by @bmesuere on Fri Feb 13 2015 at 20:00.

Original comment by @bmesuere on Fri Feb 13 2015 at 20:16.


Issue 529, Added support for pnpm

 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.:x: Lee182 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


More Info on the Firmware update screen

It would be nice if on the Upgrade BCN3D Sigma Firmware screen were some information of the BCN3DSigma Folder created when downloading the files from github. Adding a Info icon or something would be nice too!
Also I think the folder should be called BCN3D, because is not only for the Sigma 3D Printer.

For example:

Cura BCN3D is going to download the required files from github.com and is going to store then in >your hard drive under C:/Users/Documents.... the folder will be called BCN3D and there you can find >the source code for the firmwares as well the compiled version.

Done!


What is the difference between hand_landmark_lite.tflite and hand_landmark_full.tflite?  Can I replace hand_landmark_full.tflite with hand_landmark_lite.tflite?  The hand_landmark_lite.tflite model looks smaller

What is the difference between hand_landmark_lite.tflite and hand_landmark_full.tflite?  Can I replace hand_landmark_full.tflite with hand_landmark_lite.tflite?  The hand_landmark_lite.tflite model looks smaller

Hi @LMR2018, You can find the complete details from here https://drive.google.com/file/d/1-rmIgTfuCbBPW_IFHkh3f0-U_lnGrWpg/preview


EKF: Revert "Make covariance matrices of type matrix::SquareMatrix"

Fixes https://github.com/PX4/ecl/issues/745
Log used for replay testing here: https://logs.px4.io/plot_app?log=e7623a61-20fc-4179-b048-38abe9ac6c6e
Log from replay using master at commit b399698: https://logs.px4.io/plot_app?log=66a8dfba-c1c2-4ea2-81fc-bbc5836d2c5b
Summary Plot

Log from replay of this PR using PX4/Firmware branch https://github.com/priseborough/Firmware/tree/debug_using_ecl_master: https://logs.px4.io/plot_app?log=6daac421-cc73-4937-82b0-f33ba077c20e
Summary Plot

There is a change the external interface access to the covariance data - see https://github.com/PX4/ecl/compare/master...priseborough:debug_using_ecl_master?expand=1#diff-0be2b3391d4586f3ecc561669eee2529. This could probably be avoided. Suggestions are welcome.
The matrix::SquareMatrix changes can then be reintroduced starting with non-functional changes and using the sensor replay capability added by https://github.com/PX4/ecl/pull/717 to verify output.

Habe you seen the code style check failures?

Yes, and there are also failures of the build for the sensor simulator that I need to follow up. I need to update my build environment before I can run the style checker.

This PR has broken the test program which relied on the square matrix accessor functions, so those interfaces will need to be restored.

I have the tests fixed and I'll fix format now

replaced by #747


Gracefully handle attempt to instantiate non-existent connector type

Instead of showing the raw REST response, display the properly formatted list of available connector plug-ins.

Done.


Update package.json to use<EMAIL_ADDRESS>

Summary
Update to use latest terra-dev-site release

I'm making changes around this in the next version of terra-dev-site. I'm not sure why it's complaining now though.

@mjhenkes Yeah looks like this is going to need a fix in terra-dev-site before we can consume it.

With terra-dev-site 0.4.2 i think the initial draw of the site is decently faster.


Prestine nuxt project fails to boot properly

Version
v2.10.0
Reproduction link
https://github.com/nuxt/create-nuxt-app/issues/355#
Steps to reproduce
Repro steps present at link.
What is expected ?
Working server/default project.
What is actually happening?
This shows up in DevTools:
https://camo.githubusercontent.com/8f11ac3655907c26a60f8c161c006fe67f5f3424/68747470733a2f2f6d656469612e646973636f72646170702e6e65742f6174746163686d656e74732f3437333430363030343735313439393237352f3632383938363830373936363439383832372f756e6b6e6f776e2e706e67
Additional comments?
Issue identified using create-nuxt-app:
https://github.com/nuxt/create-nuxt-app/issues/355#

This bug report is available on Nuxt community (#c9854)

Same issue here with 2.10.0 release.

Got the same thing after upgrading to 2.10.0 on a project that works fine on 2.9.2.
Had to revert back in the meantime.

Having a similar issue with a pristine SSR project:

With no chosen UI framework works well.

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well by the way.

Can confirm I'm on Ubuntu
On Thu, Oct 3, 2019, 10:18 PM DennisKot<EMAIL_ADDRESS>wrote:

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well
by the way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/6506?email_source=notifications&email_token=AAAFA5XOWIS7Y376HLXOIZDQM3G3DA5CNFSM4I42L6H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAKN7YA#issuecomment-538238944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFA5TVWP2GXZYQ7CVSU7LQM3G3DANCNFSM4I42L6HQ
.

I'm having the same poblem but only on Ubuntu. On Windods 10 it works well by the way.

At first I used create-nuxt-app as following:
package manager: Yarn
UI framework: Vuetify
server framework: Express
Nuxt modules: Axios + PWA
Lint: ESLint + Prettier
test framework: Jest
rendering mode: SSR

I'm having the problem on a Windows 10 machine, can't confirm for Linux though. I had the project configured to use Vuetify and the above problem occurred. I checked if the same happens when no UI framework is being selected and indeed, it then works.
I then used this config:
package manager: Yarn
UI framework: none
server framework: Express
Nuxt modules: Axios + PWA
Lint: ESLint + Prettier
test framework: Jest
rendering mode: SSR

You can mitigate this issue by installing/upgrading to vue-meta v2.3.0 manually
Also see: https://github.com/vuetifyjs/vuetify/issues/9181

For me the issue is now resolved. I'm not sure if installing vue-meta is helping. When I do a pristine SSR project it works. An inspection in the yarn.lock learns me that vue-meta 2.3.0 is installed so I guess that indeed helped.

Problem disappeared for SPA mode for me in Nuxt 2.10.1, vue-meta is updated in this release

Thanks, the issue is solved in v2.10.1 indeed. Will close this issue because of that


Fixed reporting encoding warning, fixed remote package deploy

Thanks for the contribution! Manually merged with 9cd5e54c1e937bc6ccadb84f2763ce633f58dc07 and bd2e81f510e8bd6c060eb9c08d2c2597683d5d50


Use switch instead of if statement in editor_node.cpp

Use a switch statement instead of many if statements.
Reasons for:

Follows the rest of the code base
Prevents p_what from being checked at each if statement uselessly

Thanks!


Unable to load tflite file in android, It provides =" Internal error: Failed to run on the given Interpreter: tensorflow/lite/kernels/transpose.cc:55 op_context->perm->dims->data[0] != dims (3 != 2) 03-10 16:42:09.948  8010  8010 D check here: Node number 6 (TRANSPOSE) failed to prepare."

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
colab link to tensorflow model = https://colab.research.google.com/drive/1BI0661FaM6L4oqjNX1MYfHpJCKwKQhjt?usp=sharing
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: Samsung Galaxy M30 s
TensorFlow installed from (source or binary):  pip3 install tensorflow
TensorFlow version (use command below): 2.4.1
Python version: 3.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
Unable to load tflite model file , It provides Internal error. PLease find Log data that raised for this issue :
03-10 16:42:09.948  8010  8010 D check here: java.lang.IllegalArgumentException: Internal error: Failed to run on the given Interpreter: tensorflow/lite/kernels/transpose.cc:55 op_context->perm->dims->data[0] != dims (3 != 2)
03-10 16:42:09.948  8010  8010 D check here: Node number 6 (TRANSPOSE) failed to prepare.
03-10 16:42:09.948  8010  8010 D check here:
03-10 16:42:09.948  8010  8010 D check here: 	at org.tensorflow.lite.NativeInterpreterWrapper.run(Native Method)
03-10 16:42:09.948  8010  8010 D check here: 	at org.tensorflow.lite.NativeInterpreterWrapper.run(NativeInterpreterWrapper.java:163)
03-10 16:42:09.948  8010  8010 D check here: 	at org.tensorflow.lite.Interpreter.runForMultipleInputsOutputs(Interpreter.java:360)
03-10 16:42:09.948  8010  8010 D check here: 	at org.tensorflow.lite.Interpreter.run(Interpreter.java:319)
03-10 16:42:09.948  8010  8010 D check here: 	at com.example.testforlite.MainActivity$1.onClick(MainActivity.java:89)
03-10 16:42:09.948  8010  8010 D check here: 	at android.view.View.performClick(View.java:5794)
03-10 16:42:09.948  8010  8010 D check here: 	at com.google.android.material.button.MaterialButton.performClick(MaterialButton.java:1119)
03-10 16:42:09.948  8010  8010 D check here: 	at android.view.View$PerformClick.run(View.java:22729)
03-10 16:42:09.948  8010  8010 D check here: 	at android.os.Handler.handleCallback(Handler.java:751)
03-10 16:42:09.948  8010  8010 D check here: 	at android.os.Handler.dispatchMessage(Handler.java:95)
03-10 16:42:09.948  8010  8010 D check here: 	at android.os.Looper.loop(Looper.java:154)
03-10 16:42:09.948  8010  8010 D check here: 	at android.app.ActivityThread.main(ActivityThread.java:6138)
03-10 16:42:09.948  8010  8010 D check here: 	at java.lang.reflect.Method.invoke(Native Method)
03-10 16:42:09.948  8010  8010 D check here: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:893)
03-10 16:42:09.948  8010  8010 D check here: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:783)
I have passed input with correct dimension, still There is some error when I run tflite using Interpreter
Describe the expected behavior
Expected behaviour should load tflite model and provide output values for the provided input
Standalone code to reproduce the issue
colab tensorflow model : https://colab.research.google.com/drive/1BI0661FaM6L4oqjNX1MYfHpJCKwKQhjt?usp=sharing
android Code link : https://github.com/Adeesh2411/TensorflowAndroidAPP
tflite file can be found in asset folder

@Adeesh2411 could you make sure that your android client has a TFLite dependency, which has the same or higher version of the TF version used for TFLite model conversion?

The old runtime may not be able to run the models generated with a newer version. My recommendation is upgrading TF version of your android client if the client has a lower version than 2.4.

@abattery I converted my tensorflow vesion = 2.4.0 and tflite = 2.4.0.
Still it provides same issue

@Adeesh2411 could you confirm which TF version you are using for android?

My dependency :
dependencies {
implementation 'org.tensorflow:tensorflow-lite:2.4.0'
implementation 'androidx.appcompat:appcompat:1.2.0'
implementation 'com.google.android.material:material:1.3.0'
implementation 'androidx.constraintlayout:constraintlayout:2.0.4'
testImplementation 'junit:junit:4.+'
androidTestImplementation 'androidx.test.ext:junit:1.1.2'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'

}
In MainActivity file I'm importing : import org.tensorflow.lite.Interpreter;
then I initialize  ByteBuffer My_byte = loadModelFile(MainActivity.this, Model);             tflite = new Interpreter(My_byte);
I didn't get what you meant by saying TF version in android . Is there anything I need to add in dependency?

@abattery  Thank you for looking into my issue.
I got working with model now.
Isuue was with tflite dependency :
I converted my tensorflow verion in python :
tensorboard==2.2.2
tensorflow==2.2.0
tensorflow-estimator==2.2.0

and in android my dependency version to :
implementation 'org.tensorflow:tensorflow-lite:2.2.0'


nixos: /run/opengl-driver/lib/gbm/dri_gbm.so not available

Describe the bug
Programs, such as Electron, expect that /run/opengl-driver/lib/gbm/dri_gbm.so is available. But on latest stable it doesn't happen.

Steps To Reproduce
Steps to reproduce the behavior:

ls /run/opengl-driver/lib/gbm/dri_gbm.so
realise it doesn't exist (also some programs complain about it)

Expected behavior
That specific file exists

Screenshots

Additional context

Metadata
fetching git input 'git+file:///home/lucasew/.dotfiles'
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.67, NixOS, 24.11 (Vicuna), 24.11pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Lix, like Nix) 2.91.1
System type: x86_64-linux
Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
Features: gc, signed-caches
System configuration file: /etc/nix/nix.conf
User configuration files: /home/lucasew/.config/nix/nix.conf:/etc/xdg/nix/nix.conf:/guix/current/etc/xdg/nix/nix.conf:/home/lucasew/.guix-home/profile/etc/xdg/nix/nix.conf:/home/lucasew/.guix-profile/etc/xdg/nix/nix.conf:/home/lucasew/.local/share/flatpak/exports/etc/xdg/nix/nix.conf:/var/lib/flatpak/exports/etc/xdg/nix/nix.conf:/home/lucasew/.nix-profile/etc/xdg/nix/nix.conf:/nix/profile/etc/xdg/nix/nix.conf:/home/lucasew/.local/state/nix/profile/etc/xdg/nix/nix.conf:/etc/profiles/per-user/lucasew/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf
Store directory: /nix/store
State directory: /nix/var/nix
Data directory: /nix/store/bimspgs3cpapsbz7a2vi690916fgrvs5-lix-2.91.1/share`
 - nixpkgs: `/nix/store/4hpdrd3qvj7nks3rrimqm2jdmcga8isc-source`

Notify maintainers

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I also encountered this problem a few days ago and now the master branch has been fixed for me

Did anyone bisected the exact diff that solved that to be backported?

I sent a NixOS test to check that https://github.com/NixOS/nixpkgs/pull/368393

Seems like a hardware configuration problem.

i5 7200U: Happens
Ryzen 5 5600G + RTX 3060: Doesn't happen

CC @K900 mesa and libdbm maintainer

That file is new in Mesa 24.3, which is currently only available on unstable. Don't mix channels.


Fix Precision Handling in array.linalg.norm

Closes #7718, where the concern of unintended coercion to double precision in array.linalg.norm was raised.
Added tests to validate that the precision aligns with NumPy's standards for single and double precision, both for floating-point and complex numbers.
Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

I've removed the tests that compare the output data types of Dask and NumPy. In Python 3.9 with NumPy 1.22, these tests fail because numpy.linalg.norm() always returns a double precision output.

Hi @phofl ,
Many thanks for checking out this PR!
Following your suggestion, I've added a test to check that the the output of dask.array.linalg.norm  is of equivalent dtype as the input array. All tests pass except in Windows py3.11,   where only one test ([gw0] [ 12%] FAILED dask/array/tests/test_array_core.py::test_setitem_hardmask ) fails.
It seems the test that failes is not related to dask.array.linalg.norm, and I am not sure why it failed. Do you have any clue what might happen?

I've added a test to check that dask.array.linalg.norm output's precision matches numpy.linalg.norm, however, for py3.9, Numpy's version doesn't compute at the input precision for float32.

I think you can ignore the setitem failure
I would xfail the test for python 3.9

Many thanks for your feedback  @phofl ,
I've xfailed the tests with Numpy < 1.23 as before that version there was no i/o precision consistency for all the combinations of arguments of linalg.norm (see https://github.com/numpy/numpy/pull/17709).
A new error appears for Ubuntu py3.12 in  dask/dataframe/tests/test_arithmetics_reduction.py, which is unrelated to the linalg.norm, I guess it can be ignored (?) .

thx @joanrue
yes ci is a little flaky at the moment unfortunately


remappings.txt should not accept malformed remappings

Component
Forge
Describe the feature you would like
remapping.txt appears to silently accept some types of malformed lines.
> echo foobar > ./remapping.txt
> forge remappings
[forge panics here]

> echo "foo=bar" > ./remapping.txt
> forge remappings

foo=bar/

AFAICT this mapping won't be used (because there is no slash at the end of foo), but it's not clear this is the case. Would be nice if this flavor of mistake was detected, especially since it's easy to make.
Additional context
No response

Can you please post the panic? This should not cause a panic - I also don't think it uses remapping.txt, just remappings.txt but I'm not sure

Yes, sorry, it's remappings.txt indeed.
Panic:
config error: no prefix found in Remapping Provider
The application panicked (crashed).
Message:  failed to extract foundry config
Location: config/src/lib.rs:355

Ah right - but this does indeed mean that we don't accept malformed remappings already, right? The error is: "config error: no prefix found in Remapping Provider"
Is this issue about improving that message (I agree it's a bit vague)?

No, the issue is the second example.
foo=bar
Will be silently accepted, but I don't think it does anything. (Specifically, it interacts poorly with autodetected foo/=baz)

That remapping is not malformed, it just points to something that doesn't exist - it's still valid, since the format is valid. We can add a check to see if the destination exists, but I don't think it should result in an error. At most I think it should be a warning

Fair enough. I think a warning would be helpful.

To clarify, what is the difference between foo=bar/ and foo/=bar/? If there is none, I think these remappings should not be allowed to cooexist.

Hmm I guess we could throw an error for malformed remappings that do not have a trailing /, although I thought we internally append that trailing / to fix things if it doesn't exist? cc @mattsse

The difference is that with the foo=bar/ remapping foo/something.sol would be rewritten as bar//something.sol, and for foo/=bar/ it would be rewritten as bar/something.sol - it's a dumb string replace.
The implication of not supporting remappings w/o trailing slash is that this remapping would not work:
ERC20.sol=some/library/ERC20.sol (which means you can now import ERC20.sol instead of using the full path)

OK - convinced, great argument @onbjerg. Closing then.


Docker Built Version of Example Project: Camunda web-app not working

Issue: When using any of the example projects and generate a docker image, the Camunda web-app isn't working.
Environment:
Java 8 & 15 (tried with both)
Latest versions of the repositories.
Steps to Reproduce:
./gradlew clean dockerBuild -p micronaut-camunda-bpm-example
docker run -p <IP_ADDRESS>:8080:8080  micronaut-camunda-bpm-example:latest

In a browser, navigate to http://localhost:8080/camunda
Result:
No data is sent for the request.
Note, when using the "./gradlew run" approach, then the web-apps are available.

Hi @osh-onstructive ,
I can confirm the behaviour you describe. We'll try to find the root cause and fix it.

Hi @osh-onstructive ,
the error can actually be reproduced very easily with a Micronaut Application created from scratch with "mn create-app simple-app" and changing the runtime to Jetty. So it's basically a problem running Jetty in Docker.
The problem is that Jetty by default only listens on "localhost" but would need to listen to <IP_ADDRESS>, see also

https://github.com/moby/moby/issues/2522
https://stackoverflow.com/questions/11808075/how-to-make-jetty-server-accessible-from-lan

Unfortunately, I haven't found a nice way of to make Jetty listen on all interfaces by configuration.
It works if JettyServerCustomizer::onCreated explicitly configures a connector, but that is hacky:
ServerConnector connector = new ServerConnector(jettyServer);
connector.setHost("<IP_ADDRESS>");
connector.setPort(8080);
jettyServer.setConnectors(new Connector[] {connector});

Do you have an idea how to either

configure Jetty to listen on all interfaces, i.e. <IP_ADDRESS> ?
or
configure the docker container so that the request is routed to the correct interface?

Hi @osh-onstructive ,
I found a solution: please configure the following property micronaut.server.host: <IP_ADDRESS>.
We'll either document this in the README or maybe even configure that as default.
Does this solution work for you?

Hi @tobiasschaefer
Excellent, that works for me. What I did so that this is just part of the "docker" settings, is added the following to my build.gradle file where I am also controlling the port, etc. in the docker deployment:
dockerfile {
  args.set(['-Xmx128m', '-Dmicronaut.server.port=8080', '-Dmicronaut.server.host=<IP_ADDRESS>'])
  instruction """HEALTHCHECK CMD curl -s localhost:8090/health | grep '"status":"UP"'"""
}

Hi @osh-onstructive ,
as an open source project we're not aware of all installations. However, we'd love to hear your feedback. And of course we would also like to discuss what you are using the Micronaut Camunda Integration for to prioritise the next steps. I'm curious what you are using it for.
Are you interested in an exchange via mail or online meeting? I'd be happy if you contact me at<EMAIL_ADDRESS>


Apply a shader to the whole material instead of every character of my string

I've created a text using three-bmfont-text. I want to apply a shader to my whole material but as soon as the shader is on, I notice that it applies on every character separately. Here are two screenshots of the before and after states. Does anyone now how to fixe this ? Thank you very much !

You would probably have to render the string of text to a WebGLRenderTarget, then render that target with a shader.
Other ways you may be able to achieve this:

If you want a fragment effect like distortion, use the screen space texture coordinates
Pass attributes for each character so that your custom shader can do its thing

These things are outside the scope of this library so you are on your own. Good luck!

On Nov 30, 2018, at 6:33 AM, michaelgrc<EMAIL_ADDRESS>wrote:
I've created a text using three-bmfont-text. I want to apply a shader to my whole material but as soon as the shader is on, I notice that it applies on every character separately. Here are two screenshots of the before and after states. Does anyone now how to fixe this ? Thank you very much !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


How to use chatgpt 4?

Details
If I want to use chatgpt4 model to translate latex, what should I do?

Checklist

[X] Modify latextranslator/chat.py ✓ https://github.com/habaneraa/TransLaTeX/commit/6f0c5e5dba8c080d1111484ef2fe4fcf2735ff8a Edit
[X] Running GitHub Actions for latextranslator/chat.py ✓  Edit
[X] Modify latextranslator/translator.py ! No changes made  Edit
[X] Running GitHub Actions for latextranslator/translator.py ✗  Edit

Hi @xiajunwen1007
The bot had gave a correct answer 😂. Just modify the paramter model_name of the API requests. Parameters are defined in latextranslator/chat.py file.


redundant method call in UpdateSecurityStampAsync method of UserManger class

redundant method call in  method below
public virtual async Task UpdateSecurityStampAsync(TUser user)
{
ThrowIfDisposed();
GetSecurityStore();  // This code in not doing anything and have no use of this method call
      if (user == null)
        {
            throw new ArgumentNullException("user");
        }

        await UpdateSecurityStampInternal(user);
        return await UpdateUserAsync(user);
    }

This is deliberate. It's a way of checking if the store implementation supports the API. As it's an internal call we're not so worried about naming.


Usage of Managed Identity instead of SA keys

Is it possible if I use Managed Identity details to create a persistent volume claim instead of keys?

@jremeneses
Thanks for your feedback! We will investigate and update as appropriate.

@jremeneses
Thanks for posting your question! Can you please confirm if your issue is related to a document that you are following and want to point out an issue in the document or share feedback to a document to avoid such failures you have reported?  In this case could you provide the URL of the specific documentation that your feedback is applicable to? That way, we can make sure your feedback is addressed by the right team and it can help others who are looking for help on similar topics.

I would like to create a persistent volume but upon checking the documentation, it requires a storage account key. I would like to eliminate the usage of keys and use Managed Identity instead. Is it possible?
Here is the link:
https://learn.microsoft.com/en-us/azure/aks/azure-csi-files-storage-provision

@jremeneses
I've delegated this to @MGoedtel, a content author, to review and share their valuable insights.


Modify ledger.GetBlockByNumber to additionally return OK

Description
The ledger.GetBlockByNumber returns nil,nil when it is asked to retrieve a block which is not in the DB.  This is not a bug, but seems to cause considerable confusion to consumers.
Most code seems to follow the pattern:
block, err := ledger.GetBlockByNumber(n)
if err != nil {
    return err
}
block.doStuff()

This causes a nil pointer dereference, and was seen in state transfer which was fixed, but api.go currently follows this pattern as well and would conceivably cause a crash.
After discussions with @srderson he convincingly argued that this is not an error condition, it is an expected condition, so setting error is inappropriate.
Instead, to prevent this misuse, the GetBlockByNumber call should return *pb.Block, bool, error to indicate whether or not the block was actually retrieved and the callers should wrap and propagate this pattern.

This would be a great first issue if someone wants to try it out. Nothing too complex and will give you a chance to explore the code.

I don't understand why we need to have 3 values returned?  What are the possible combinations?  Are there really 8 different possible outcomes?

@corecode I think the argument would be that, this is essentially a read from an IO based map, so following the golang idioms, a map returns (value <type>, exists bool) while IO returns (value <type>, err error), so, smashing these together we have (value <type>, exists bool, err error).
I agree that there aren't that many possible outcomes, I can only think of three.

nil, false, err
block, true, nil
nil, false, nil

Since the block being nil implies ok = false, you can argue that the argument is superfluous, but, based on the usage patterns we've seen, people interpret the current return parameters in a golang idiomatic way, and do not check for a nil result when err is unset.  It's caused nil pointer dereference bugs in two different people's codes, and worse, because the nil,nil case is so rare, it is not generally discovered by routine testing.

Or we just return an error, because there is no such block (yet)?

Maybe @srderson can be more articulate, as he convinced me, but setting errors should be reserved for conditions which are abnormal.

Then maybe we should return ok only?

Although this gets into the territory of 'What should I do if I get back an error from the DB?', it seems to be the golang way to propagate errors up, and simply returning false would not do that.

Because the DB is I/O, it seems possible to me that there is a non-persistent error. For example, if a JSON-RPC request ends up invoking ledger.GetBlockByNumber and there's an error, I feel returning a 500 and leaving the system up may be better than killing the peer.

So returning an error if the block is not available is correct?  Then we don't need ok.

@jyellick @srderson @corecode
I am not sure what the conclusion is on this issue to implement. Could the author edit the description to capture that.
My 2 c,  we should follow HTTP and report NOT FOUND condition, and we should define status codes (again, just follow HTTP codes). In HTTP, response is simply a payload and a status code. So returning {nil, {code: 404, msg: NOT FOUND}} would probably be preferred, so that application could check status code and react accordingly.

I'd be in favor of returning an ErrNotFound as the error, as rest_api.go already replies to that with a 404.  Assuming there's consensus (in particular from @srderson, as you originally opposed not found as an error condition) I'll update the description and original issue to reflect this.

makes sense to me

@srderson, your take?

I stand by my original opinion, but it sounds like I'm out voted. My second choice is the ErrNotFound option.
You will now have both ErrOutOfBounds if the block never existed or ErrNotFound if the block exists and is not present for some reason. Just something to keep in mind.


Display enemy FOV on the map

Probably whenever enemy actor is pointed at? This should make sneaking and ranged attacks against short-sighted/blinded/sleeping foes more fun.
Also, display own FOV more easily (currently only toggled via Setting menu option and visible in targeting mode only). Also, make the display better; it's quite intrusive right now despite using bright black for the highlight colour and it looks inconsistently in the web frontend.

Bright black background may be not a bad idea, but then I'd need to forbid using bright black as foreground, which limits the already modest choice of colours. However, it wasn't particularly visible on black, especially in case of small glyphs, anyway.

It would be great to also display FOV of an enemy faction whenever all our actors are outside the FOV (either really or as far as our faciton can determine). This doesn't happen too often and is a tense moment, so the extra visual noise is a good thing, even regardless of usefulness of the information. However, this is tricky from architectural perspective, because FOV is right now available only on the server, particularly enemy faction FOV. Also FOVs are large beasts and their updates even more so.

The BrBlack colour is too bright to be a background, but it can't be much darker, because it needs to be readable in grayed-out menu entries, etc. In fact it's so bright, that even tiny single dot items or terrain in this colour is visible on the map, albeit not very comfortably. Still, it should not be forbidden, though some games may choose not to use it for map nor terrain.
So we need plan B. Perhaps a cheat, where BrBlack as background is much darker than BrBlack as foreground or highlight? We are already cheating past 16 colour by having two shades of white to make adjacent rows of text distinct and so minimize the risk of the eye jumping.

However, the player may have limited knowledge of enemy FOV not only due to limited own FOV, but also due to not knowing identify of sight radius affecting (and other, e.g., noctovision) items. Also, not knowing terrain obstacles precludes accurate assessment of enemy FOV. So server sending intersection of FOVs is not enough to represent the asymmetric knowledge. Even worse if we restrict factions from knowing equipment of visible enemies (currently not restricted in any way, but not displayed in UI, so undecided).
A more accurate solution, where client (conservatively) reconstructs FOV of another faction using own limited knowledge of items and of terrain has the extra advantage that the huger FOV data structures don't have to be sent from server to client. However, it's not clear what 'conservative' means. What if an unknown item makes an enemy blind? Should we assume each enemy with equipped unknown item (or even unknown temporary condition) is blind? Should we assume each unknown terrain is translucent to be on the safe side? What if games, such as LamdaHack, have dark walls and so they are unknown from afar and so any heuristic misses the mark most of the time?
It seems, intersection of FOVs should be public knowledge after all, as unrealistic as it is. Even though that lets players deduce properties of unknown items and translucency of unknown terrain with some accuracy. I guess AI should never take advantage of that, even if there were no more pressing features to add. Anyway, gameplay (stealth fun, in this case) trumps realism every time, It's just they were rarely at odds so far.

Not sure how exploitable it is, but I think enemy FOV may even serve to deduce location of enemies that are not seen. To fix that, we'd need to store FOV of each individual actor and only reveal FOV of seen actors. But storing such FOVs is very costly and FOV is already a bottleneck (to be precise we store per-actor raw FOV, but not FOV adjusted by dynamic and static lighting; that adjustment is done on total FOV, not per-actor). I'm not quite sure how fun the mini-game of deducing hidden actors would be. I hope it'd be fun or rare enough,
However, it's much worse if it actually reduces stealth play suspense. E.g., if potential enemy of the other side of the wall is not a threat, because I would see that enemy's FOV (due to seeing one of his teammates elsewhere). Even worse, to hide from me, the enemy would be better off wearing blindness-inducing items!
So perhaps per-actor light-adjusted FOV is a must, but that's a big performance cost.


fixed.

Removed non-ASCII odd character. (  ِِApplication )
Reformatted.
Remove illegal whitespace from filename. (" test05 short way for sum .ring" → "test05 short way for sum.ring") - make sure " test06 put&get .ring" in Windows Explorer.

Thanks for the update


Insert Contents of Project-README into Package Index Files

Background
The IA for this project has, among other items:
Getting Started

sw-build
sw-cli
sw-lib

Advanced

etc. ...

The consensus of the group seems to be that priority both in work and presentation be sw-build and sw-cli, followed by other issues; and items under Advanced to be downplayed.
Proposal
The proposal is to:

Include the package source files contents currently generated by Project-README.hbs. This would basically put this content on the top-page for the modules they belong to (a page like this, for example.).
Remove them from the github landing page.

Implementation
Two possible ways:

Automate it.
Build it by hand.

I would like input and comments before I proceed.

@gauntface @jeffposnick

The github landing page was altered to what you asked for originally where you wanted the Github Readme to be the same for the github pages index.
Whatever you think is best I'm down for.
+1 this suggestion.

That was before the IA. This suggestion wouldn't have made sense then.


litmus: init at 0.13

Motivation for this change
Add litmus (a WebDAV server comliance tester) to Nix.
Things done

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

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

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

Notify maintainers
cc @rkoe

Closing because review comments are not being fixed.


Does Chinese data need additional change in the code?

Or will it  work just fine with Chinese?
Really interesting work!

Thanks for your interest!
In principle you shouldn't need to do much. You need to switch the English BERT models (incl. the initial bi-encoder and the base model) to Chinese ones. E.g., for bi-encoder you could use simcse-chinese-roberta-wwm-ext (I randomly retrieved this one from google); and the corresponding base model is hfl/chinese-roberta-wwm-ext.

Thank you for replying so quickly. Yes, the model definitely need to change. I was mainly concerned about data processing. I will try it tomorrow.

@drxmy 请问你做过尝试了吗，效果怎么样

@drxmy 请问你做过尝试了吗，效果怎么样

我用的自己的数据集，现在的结果有一点奇怪，可能代码哪里没改对。bi-encoder每个cycle会验证两次，第一次指标很高，第二次就很低。不过最近一直没时间看是什么问题


Navbar search is not rendering as expected in latest chrome (version 50 to 52)

More details here..
http://stackoverflow.com/questions/36825618/materialize-css-navbar-search-is-broken

Hello,
Same issue on chrome 50.0.2661.86.
How to fix ?

I also noticed this.
The answer here worked for me: https://stackoverflow.com/questions/36825618/materialize-css-navbar-search-is-broken

This pull request fix the bug https://github.com/Dogfalo/materialize/pull/3013/files

Jesus christ this is still open from APRIL!? The work around at stack overflow isn't working for me either :(. Any updates on this issue?

Fix does not work.

@tpav96   I agree. I had to write a CSS rule that manually set the search bar to be 64px high. But I've had people insist that it's "fixed" so ¯_(ツ)_/¯

Yeah it is definitely still broken on Chrome.Setting the height manually
like you said also worked for me.
On Mon, Feb 6, 2017 at 10:06 AM Native-Coder<EMAIL_ADDRESS>wrote:

@tpav96 https://github.com/tpav96 I agree. I had to write a CSS rule
that manually set the search bar to be 64px high. But I've had people
insist that it's "fixed" so ¯_(ツ)_/¯
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Dogfalo/materialize/issues/3082#issuecomment-277708293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJqq-dlqmkDoe4GMq00lEOPknnfpJURdks5rZzX9gaJpZM4IOlSA
.

@tpav96 @Native-Coder This is still an issue in chrome and materialize latest?

Honestly have not tried. I implemented the temporary fix outlined a few
posts above and I have just left my site as is since it seems to correct
the issue.
On Tue, May 2, 2017, 10:38 AM Fabian Gutierrez<EMAIL_ADDRESS>wrote:

@tpav96 https://github.com/tpav96 @Native-Coder
https://github.com/Native-Coder This is still an issue in chrome and
materialize latest?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Dogfalo/materialize/issues/3082#issuecomment-298654724,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJqq-Xl-3B18F6JUqy8Ng7HReYuf3_Rhks5r1z_HgaJpZM4IOlSA
.


docs: Use invite link for Discord Server in README

Description
The previous link only works for folks who are already part of the server. This link should work for anyone, and put them in the #fga-general channel.
References
Discord discussion: https://discord.com/channels/759188666072825867/930524706854031421/1133095840676859934
Review Checklist

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

CI Failures look unrelated to the README-only change.

Updated via changes to sdk-generator && https://github.com/openfga/js-sdk/pull/25


[BUG] Article 'Published' and 'Last Updated' dates have different formats

Mandatory Step
I am using latest production release of Elegant
Description
On pages with date and modified metadata defined, the date format used for each is different.
This results in the following appearing on pages:

To Reproduce
Steps to reproduce the behavior:

publish a page with date and modified metadata (e.g. the sample from the Pelican docs)

Expected behavior
The 'Published' and 'Last Updated' sections should use the same date format.
Additional context
$ pelican --version
4.5.1
$ locale | grep LC_TIME
LC_TIME="en_GB.utf8"

It seems the 'Published' section uses article.locale_date, while the 'Last Updated' section uses per-element string formatting of article.modified (i.e. day, then month, then year).
From the Pelican docs, locale_date is the date as formatted by date_format, so I think this could be fixed by also formatting modified using date_format.
I've checked this works with a test site and would be happy to submit a pull request.

Thanks @ishigoya that would be great, remember, when submitting a PR to do it against the 'next' branch.

Duplicate of #613


import graphql/**/*.mjs instead of graphql/**/*.js files in ESM build output

This PR adds an extra post-build step to update imports from graphql/**/*.js to graphql/**/*.mjs.

looks like mocha is not happy when the lib is importing .mjs file. I will find another time to check different behaviour with different esm usage (such as if using esbuild / webpack / etc)


Which database is being used to persist the hashes ?

In the code i see that the hashes are being persisted to file and on startup the db is being populated from previously existing file.
What are these files ? Can they be normal text files ?
I'm not familiar with go that's why i'm facing trouble understanding the code.

As mentioned in another issue, the "database" is just the in-memory structure containing hash prefixes and other blacklist metadata. As far as saving/loading files goes, the code is using the gob package, which serializes a Go data structure into a binary format. In addition, the file is gzipped to save space. So the in-memory structure is being serialized and compressed as it is written to the disk.

The "another issue" in question is #21


Remove state update in componentWillUpdate

This PR removes the setState() in componentWillUpdate of the ProgressBar component.
See React.Component componentwillupdate documentation.

Coverage remained the same at 99.242% when pulling c0aef89d3813a40b7489c1d90b1a5ec2108475e5 on mawi12345:dev into cfe0c7ce16e376bb32df1ac6b27ac715a6cf6c1f on react-boilerplate:dev.

With this PR it is possible to switch to Inferno by running:
yarn add inferno inferno-compat
yarn remove react react-dom

and adding in webpack.base.babel.js:79 the alias configuration:
  ...
  resolve: {
    alias: {
      react: 'inferno-compat',
      'react-dom': 'inferno-compat',
    },
  ...

LGTM 👍


Zarget - website visitors’ behaviour tracking

Please add Zarget to the hosts list.
As described by Zarget: "Get detailed insights on website visitors’ behaviour".
Live example: www.sygic.com
Sygic track file: http://cdn.zarget.com/179341/476372.js

Can anyone confirm further URLs to be added for this?
zarget.com
cdn.zarget.com
That example link also brings up an interesting case for Facebook events:
facebook.net
connect.facebook.net
Can anyone confirm if those URLs are only analytics and if they will conflict with normal Facebook usage? Preferably by testing both from a desktop and mobile setting, as apps make different connections.

Thanks @xetorixik and @ScriptTiger.  Closing.


Window focus is changed on item-drop

Is your feature request related to a problem? Please describe.
I am not sure if it is a bug or by design, but the problem I have is, that every time I drop on element the focus changes. This causes other libraries like  react-query to reload data.

Code:
import { useEffect } from "react";
import { render } from "react-dom";
import Example from "./example";
import { DndProvider } from "react-dnd";
import { HTML5Backend } from "react-dnd-html5-backend";

function App() {
  useEffect(() => {
    console.log("FOCUS ADD LISTENER");
    window.addEventListener("focus", () => {
      console.log("FOCUS CHANGED", Date.now());
    });
  }, []);
  return (
    <div className="App">
      <DndProvider backend={HTML5Backend}>
        <Example />
      </DndProvider>
    </div>
  );
}

const rootElement = document.getElementById("root");
render(<App />, rootElement);

https://codesandbox.io/s/peaceful-vaughan-1e33c?file=/src/index.tsx:0-612
Describe the solution you'd like
I would like to not have those focus-changes. Maybe to not break code from others add some parameter so the user can turn it on/off.
I have no idea if this is possible cross-plattform. Any help is appreciated :)

This causes the whole tree to rerender. Even when I use the DnDProvider in a single deep subcomponent.


Bruno CLI Install Not Completing

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Running on WSL2 Ubuntu 24.04 LTS
Used mise for node installation
Node Version 22.11.0
NPM Version 10.9.0
Wanting to get the CLI tool installed by running npm install -g @usebruno/cli
The progress indicator flips for a bit and then freezes and the installation never completes. I've waited as long as ten minutes for completion and it doesn't happen.
 The log files (attached below) don't offer me any insight.
Many thanks for any assistance!
.bru file to reproduce the bug
No response
Screenshots/Live demo link
2024-11-27T19_05_53_151Z-debug-0.log

okay... it takes an hour to run this install...
is there a good reason for that?
$ npm install -g @usebruno/cli-next
npm warn deprecated<EMAIL_ADDRESS>this library is no longer supported
npm warn deprecated<EMAIL_ADDRESS>The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.

added 278 packages in 1h

34 packages are looking for funding
  run `npm fund` for details
Reshimming mise 22.11.0...
wobbet@ATAZ013:~$ bru --version
1.19.0

Hey @wobbet,
Thanks for reporting this. I tried installing @usebruno/cli version v1.35.0 on my WSL, and it installed pretty quickly for me. Also, @usebruno/cli-next is no longer supported. I noticed in your logs that you're installing @usebruno/cli-next. Could you please remove that and install @usebruno/cli instead?
PS: I'm attaching a video showing the installation process and the speed difference. If you face the same issue, could you please update us here?
https://github.com/user-attachments/assets/df9c3a86-0cfd-4eb1-b666-6d622b16a22e

Same thing using /cli instead of /cli-next...
Is there a way to get timestamp info in the log files instead of just step numbers? That might help me diagnose where the issue is coming from.


Could not find a version that satisfies the requirement tensorflow-compression~=2.12.0 (from versions: none)

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
fail
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
3.9.12
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I try to pip intsall tensorflow-federated it fail, so i build it on source, i pip install --requirement "requirements.txt" then happened this error. can i know how to solve this problem?
Standalone code to reproduce the issue
-

Relevant log output
ERROR: Could not find a version that satisfies the requirement tensorflow-compression~=2.12.0 (from versions: none)
ERROR: No matching distribution found for tensorflow-compression~=2.12.0

Hi @xueyee0802 ,
AFAIK , tensorflow-compression binaries available only for 2.13 version onwards. Could you please refer to Pypi source here.
Please try importing 2.13 version. Also for any further bugs please report concern repo attached here.Thanks!

Hi @xueyee0802 ,
AFAIK , tensorflow-compression binaries available only for 2.13 version onwards. Could you please refer to Pypi source here.
Please try importing 2.13 version. Also for any further bugs please report concern repo attached here.Thanks!

Hi @SuryanarayanaY,
I tried pip intsall tensorflow_compression-2.13.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, to get the 2.13 version, but i getting this error.
ERROR: tensorflow_compression-2.13.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl is not a supported wheel on this platform.

Hi @xueyee0802 ,
Please use just pip install tensorflow-compression and it will install latest version of tensorflow-compression based on the platform you are using.

pip install tensorflow-compression
Hi @SuryanarayanaY,

I tried before pip install tensorflow-compression, there are some error.


AADSTS16000

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[x]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>Description
Please see this link for additional info and solution. The same issue exists in MSAL and ADAL library.
https://github.com/AzureAD/azure-activedirectory-library-for-js/issues/580
The issue is specifically with MSA passthrough accounts with more than one account signed in. The token does not return enough information so it is ambiguous and the user can not log in. Using the data from the 'email' field to replace the 'upn' field when it is not present works as a solution in ADAL as suggested in the link, and I assume the same fix would work for MSAL.
Error Message
AADSTS16000
I just recreated this issue, since it was closed without fixing: https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/1816
I believe this is an existing bug in the library, the code here lists checking how this behaves when the idtoken has no upn as a todo, which I don't think works right now
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/266c6e98c861b5cfb124647c04d377ebf8412087/lib/msal-core/src/ServerRequestParameters.ts

@ranjanmicrosoft You could try passing in a session id (sid) as part of the request. This is an optional claim that will help you bypass account selection, as detailed on the docs here.

i'm using the msal-angular library, not making these requests on my own. would i need to reimplement the MsalInterceptor to make that change?

@ranjanmicrosoft Unfortunately, it is a known issue that you are unable to pass additional options to the acquireTokenSilent call made inside the MSAL Interceptor. This is something we are planning to address soon. For now, you can reimplement the MSAL Interceptor to be able to pass additional parameters to the acquireTokenSilent call.

Passing additional parameters to the interceptor is now possible in MSAL Angular v2 alpha: https://github.com/AzureAD/microsoft-authentication-library-for-js/releases/tag/msal-angular-v2.0.0-alpha.0
Closing.


Continue #801: slim down mojos and add tests

I'm going to restart working on refactoring. I've implemented some tests using the mock-webserver, to see if the approach is applicable. It was not so easy to test e.g. the openshift binary build, but it can be done.
I'm going to work next on fixing the spring-boot watch mojo, so I've refactored the port-forward thing into a service (and also the client tools service, to isolate it in order to remove it in the future). There's this pr https://github.com/fabric8io/kubernetes-client/pull/707 (going to fix it shortly) that will eventually be used for port-forwarding without the client tools.
I started migrating stuff into the hub... it will be a long migration...

This should be closed.


LogBufferUnblocker::unblock activeTermCount/expectedTermCount

For the following function, if the following situation happens then the blockedoffset is used with the wrong term id.
IF
blockedPosition is within TermId = 0 (the second half because otherwise the pub=lmt doesn't cross two terms)
activeTermCount is now at 1
Then
index = 1
termId = 1
However given that blockedOffset refers to term 0, working with termBuffers[index] doesn't make sense.
It seems like we should use the expectedTermCount to compute the index instead.
LogBufferUnblocker::unblock()
{
final int termLength = termBuffers[0].capacity();
final int positionBitsToShift = Integer.numberOfTrailingZeros(termLength);
final int activeTermCount = activeTermCount(logMetaDataBuffer);
final int expectedTermCount = (int)(blockedPosition >> positionBitsToShift);
final int index = indexByTermCount(activeTermCount);
final long rawTail = rawTailVolatile(logMetaDataBuffer, index);
final int termId = termId(rawTail);
...
    final int tailOffset = termOffset(rawTail, termLength);
    final int blockedOffset = computeTermOffsetFromPosition(blockedPosition, positionBitsToShift);

}

You are talking about the Java code and not the C++ code, correct... the use of "::" had me confused.
If I follow your logic, there are some tests for this case. Specifically, doesn't shouldUnblockWhenPositionHasNonCommittedMessageAndTailPastEndOfTerm work how you mention? Or at least the spirit of it.
If I don't understand the test case, it should be straight forward to construct it in LogBufferUnblockTest.java.

I think this is an issue in the Java code. I've been testing and about to push a fix. It has been a typo when I realised a missing case and my solution is not right.

It would be good to review if what I pushed makes sense.

That last push has an issue. I'm fixing.

Let me know when you are happy and I will review and reflect on the C side.

The reported issue is applicable to Java and C.
For the unblock section of the code I think we should use expectedTermCount.
For the rotateLog sections, I think we should still use the activTermCount though.

Sorry I replied too rapidly I will review the latest changes later and post my feedback

@goglusid I'm jetlagged badly, so it takes very little to confuse me. ;)

The latest changes resolved the issue. ;) Thanks


Fixed some bugs in the middleware that caused the cache/i18n-js.yml and t

Fixed some bugs in the middleware that caused the cache/i18n-js.yml and translations.js file to be generated on each page load.  They will now be generated only when language files have changed.

Thanks for your patch! Just applied on master.


Initial script for export all entities

What kind of change does this PR introduce?
This PR introduce a simple script that can auto generate index files that exposes internal webpack entities.
The idea is that the index files are committed and when necessary can be generated again.
If auto generation is not welcome I can just use it once to generate initial indexes and manually remove/add exports.
Once the idea is approved I think that it will be preferred to organize the top level lib files more carefully inside folders for easier generation. and maybe also generate the main webpack index file that way.
I also exported AsyncDependenciesBlock manually in the main index

I only generated few folders to show the idea.

Did you add tests for your changes?
No. In this stage I only want to know if the idea is acceptable and if so what and how exactly we want to test.
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?

All exported entities? - this is a huge effort that should be contributed as time passes.

how to determine what should be public?

Let's solve it in another PR, here just solve original issue

Ok I open a PR that resolve only the issue that originally raised  #12987

Actually my idea with these manual exports was that we export as least as possible as everything exported becomes part of the public api and we can't easily change it anymore because it may cause breaking changes.

I have a lot to say here but since we are not going to agree I will spare this.

@barak007 What do you need more?


Add Android "R/W External Storage" runtime permission request

Permission request came with Android 6. Because if you need to make sensitive operation like write or read external storage, you need to ask to user for permission an make this operation. In Godot has only include camera, record audio and vibration permission. We need to write and read some data in game for save and load states. So I add write and read external storage permission requests and all permission request result callback but I am not sure results were emiting on Main Loop.

Pull Requests should be made against the master branch in priority, which will be used for our next main release (3.2).
For Android the buildsystem changed a bit for 3.2, so it's fine to have one PR for master and one for 3.1, but the master one will need to be merged first.

Okay, I will add this feature to 3.2 and open a PR to master. In 3.2 there is some difference about Android that you say, I will develop new codes.

I opened PR to master #31598

@volzhs can you review this? same as #31598

@cagdasc Should this PR be closed since it'll be replaced by PR #32246?


feat: Inline Begin Transaction

@jskeet this is ready for review.
The first three commits are refactors for making things easier later on. And then inlining is introduced gradually. Tests passed after each commit.

@olavloite In case you want to review.
@bshaffer FYI

(And the breaking changes are expected)

Thanks - I'll try to get to the review today; I may well send out review notes on a per-commit basis.

Closing and reopening for the breaking change detector benefit.


AttributeError: 'SyncRPCFilterRequestBuilder' object has no attribute 'limit'

Describe the bug
A clear and concise description of what the bug is.
The Python client doesn't support limiting rows in an RPC call and fails with "AttributeError: 'SyncRPCFilterRequestBuilder' object has no attribute 'limit'"
To Reproduce
Steps to reproduce the behavior:
function_data = supabase.rpc("function", {"param": "a"}).limit(5).execute().data
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> AttributeError: 'SyncRPCFilterRequestBuilder' object has no attribute 'limit'

Expected behavior
A clear and concise description of what you expected to happen.
Returns a list of the results of "function" limited to 5 rows.
This works in the JS client:
const { data } = await supabase.rpc(fxn, { param: 'a'}).limit(5);

I can confirm this is a bug in the Python library.

I have a version of this working locally but there seem to be a few more filters missing so I'm going to try and get them all added before creating a PR for this.
Missing: select, single, maybeSingle, limit, explain, range, offset, order and a few more.

I've created a PR over in the postgrest-py project to get this issue fixed https://github.com/supabase-community/postgrest-py/pull/372

This has now been merged and is available in the latest 2.3.8 version of the library on PyPi. https://pypi.org/project/supabase/

Closing this out as there has been no update from OP and a fix has been out from 2 weeks ago.


Added the new skim

The new skim is added to the StdBase.py file as it's requested here [1].
[1]
https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/1384/2.html

test this please

@vytjan We should add you to the list of DMWM contributors if you're going to be contributing semi-regularly. @hufnagel ?


Add tests for odo catalog search failing

Adds tests for odo catalog search failing
Closes https://github.com/openshift/odo/issues/2147

Expected
        <string>:  ✗  The current directory does not represent an odo component. Use 'odo create' to create component here or switch to directory with a component

@cdrage I guess this PR needs a rebase as https://github.com/openshift/odo/pull/2134 is already in

Authentication required for https://<IP_ADDRESS>:8443 (openshift)
[odo] Username: Password: Login failed (401 Unauthorized)
[odo] Verify you have provided correct credentials.
[odo]  ✗  challenger chose not to retry the request

/retest

/retest

/retest

Travis failure is fixed in #2164
/lgtm


support relative URIs per RFC1808 and RFC3986

need to support leading . and .. for "format" : "uri"

or a least leading ..

CC.txt
Schema.txt

I was able to add a format to support different URIs than defined by the package.


Change the special character lookup tables to statics

See https://github.com/raphlinus/pulldown-cmark/issues/119#issuecomment-552158266
In addition, this PR also implements LUT switching so that the performance of plain CommonMark is not affected by adding extensions. The full commit message explains the performance impact of that change.
Here's the overall effect:
⌁  g/pulldown-cmark ╍ (static-scanner-lut) cargo bench --bench html_rendering -- --baseline baseline crdt_parse
    Finished bench [optimized] target(s) in 0.16s
     Running target/release/deps/html_rendering-09cbd52ae1f5c0d2
crdt_parse              time:   [337.56 us 338.25 us 338.96 us]
                        change: [-2.0951% -1.8117% -1.5011%] (p = 0.00 < 0.05)
                        Performance has improved.

(I would also note these benchmarks were running on a pretty noisy machine, and the baseline fluctuated quite a lot later (still centred on where it was). You can at the very least say that plain-spec perf is no longer dependent on the number of extensions & extra special chars that need to be scanned to support them.)

This is very interesting, and I applaud you for putting in the work. My machine produces very similar performance deltas as the ones you reported, which is encouraging.
I do need a bit more time to fully digest this. In particular, the following bit that you wrote here,

SIMD wasn't impacted by the static change, probably because the _mm_loadu_si128 call was itself inlined into a bunch of setup instructions based on the const.

is exactly in line with my understanding of how it gets to perform well. But I don't see how that can be preserved when the lookup table isn't fixed (without polymorphism).
The const to static change looks like a clean win and the rest seems sensible, I just need a bit more time to fully digest it!

I don’t see how that can be preserved when the lookup table isn’t fixed

@marcusklaas I did think about this, and I would guess it’s still inlined, but with lookups in each instruction rather than constants. I would have to study the asm more, but it’s comforting that there isn’t an overall regression. Are there actually realistic input patterns where SIMD is a lot faster rather than just slightly faster? For me the rest of the parse seems to dominate with the crdt_parses being 320 vs 350us. Maybe big tables.

(Just thinking - it might be slightly quicker if MaybeSimdLut was a pointer to a pair rather than a pair of pointers, as it would be 8 fewer bytes on the FirstPass struct, whose size seems to influence things.)

Oh, I remember what I meant — simd cannot reuse the setup work in the way the scalar version can — so it was only using the compile-time computation of what the setup should be called with not the setup itself, as the setup is done in registers. So we’re still reusing the precomputed shifts, nothing has changed. Hence no delta.

Okay, I've finally had another go at this. The performance boost should be greatest in the scenario where no options are set, right? I'm having trouble getting a consistent delta on crdt_parse, because the benchmark results are kind of noisy.
Thank you for your explanation on the SIMD stuff, that makes sense now.
It seems we should try to create a benchmark with a lot of optional tokens like | or ~ in them, to get a feel of how much we stand to gain.

Looking for a performance boost is not the best way to think about it. The layout changes in Parser will probably negate the construction or at least make them hard to measure. Maybe you'd see it with lots of optional tokens. But these are the two improvements:

Removes some O(LUT size) setup code constructing the LUT in scalar parse_line.
Allows unextended CommonMark mode to avoid the cost of scanning characters it isn't interested in.

Yes, (2) offers perf improvements in theory, but we don't scan that many extra special chars at present and they're not very common characters, so it's measurable in theory but I doubt anyone actually cares. So the benefit is mostly realised when adding features like smart punctuation. Because doing that increases LUT size AND requires scanning more characters. So a better comparison is between {a PR adding a feature like smart quotes, against where master is now} and {the same PR rebased against this PR}.
(I have such a PR cooking at https://github.com/raphlinus/pulldown-cmark/compare/master...cormacrelf:smartypants.)

A few pings on the issue brought me back here, and thinking about this anew, maybe varying the lookup table is best done with compile-time cargo features. That is, to enable a feature (and autocomplete that option in your editor) you must enable a cargo feature. Features == conditional LUT additions, plus some extra code enabled. Why?

I get a sense that while there’s a use case for runtime options, the scanner receiving loop can just ignore disabled options, rather than dynamically selecting a slower LUT and erasing some of the win with the LUT-switching. If you want full speed, compile with no features enabled. This would be the default. Pay for what you use by enabling it at compile time.
Markdown features tend to be additive/somewhat well-defined when enabled together. So this fits well enough as cargo features. Dep crates + your own Markdown needs should turn out okay, you’ll get the “slowest common denominator”.
I also get a sense that having knowledge of the options at compile time would be generally useful outside the LUT. Some checks and codepaths could be eliminated, and you might be able to tune pure CommonMark even faster. Does that sound accurate?

Hi Cormac, so sorry for the long radio silence here.
I am very keen on merging this soon. Smart punctuation is the last remaining major feature that pulldown has not implemented, and you've done excellent work here. Even if you've (understandably!) moved on, I'd like to take what you've done in this PR and the one you've linked to above and complete them to full smart punctuation support.
On the distinction between compile-time vs dynamic options: it's tricky. From a dogmatic perspective, I am in the compile-time camp like you. It seems that the use case for dynamically changing options is narrow, and we'd get optimal performance with compile-time options. Pragmatically however, it seems a bit problematic. It'd be a major breaking change, and going by your benchmarks, for very limited speed gains. I'm certainly open to it, but such a change would require broad support from other users and maintainers.

I took your ideas and used them to implement smart punctuation. Too bad this code didn't make it into master, but the effort wasn't wasted. Thanks for your PR!

I saw that, great job and I'm glad I could help!


Additional "-amd64-" release

Hello, I want to build a multi-arch Docker image that includes lua-language-server. I am running this command to download a release curl -sLo lua-lsp.tar.gz https://github.com/sumneko/lua-language-server/releases/download/3.2.4/lua-language-server-3.2.4-linux-${TARGETARCH}.tar.gz.
TARGETARCH is a variable from Docker buildx set to the current architecture for the image.
The value in this variable for the x64 architecture is amd64 leading to a failure for the amd64 build. (the arm64 build is fine as a release with arm64 exists).
From my perspective amd64 is a very common naming so I would appreciate additional (to not break automation that use x64) releases (for darwin and linux) named with amd64.
Thanks for this great lsp 👍
Cheers!
Michael

Just a name, I think you can easily solve it.

Thanks for your reply.
You're right, just a name. I was just surprised about this being the first tool of many which I install that doesn't name the artifacts with "amd64"
For others coming around, my workaround is
RUN ....
&& if [[ "${TARGETARCH}" == "amd64" ]]; then TARGETARCH=x64; fi \
&& curl -sLo lua-lsp.tar.gz "https://github.com/sumneko/lua-language-server/releases/download/3.2.4/lua-language-server-3.2.4-linux-${TARGETARCH}.tar.gz" \
...


Website not charging to download

Dear MCScanX team,
I am trying to download the software but this website: chibba.pgml.uga.edu/mcscan2/ is not working.
Could you provide me with a working website please? I would love to be able to use this software.
Thanks a lot,
Marc

Hi, I'm having the same problem! Can someone help?

Hi, I could download it through github:
$ wget https://github.com/wyp1125/MCScanX/archive/refs/heads/master.zip


Server App not support CH343

I'm building a custom tracker board using CH343 to replace CH340 for smaller size, but the server app can't detect COM with CH343 properly. The COM port is good when download firmware through it.

Should be fixed with
https://github.com/SlimeVR/SlimeVR-Server/pull/245
It will filter for "usb" and "seri"

@SSV-Normandy Can you confirm is this has been fixed (and close the issue if it is)?
Link to a build from latest commit (f3d32da4cd0b5221f0fb25176bf7fe10029faec4): https://github.com/SlimeVR/SlimeVR-Server/suites/8877865892/artifacts/405644841


Added backend validation for length of group names

This branch contains code from the previous branch for validation of special characters also.
The length of the name is validated if it less than 256, and displays the exception message.
Before you contribute, please review these guidelines to help ensure a smooth process for everyone.
Thanks.

Read how to properly contribute to open source projects on Github.
Fork the project.
Use a feature branch.
Write good commit messages.
Use the same coding conventions as the rest of the project.
Commit locally and push to your fork until you are happy with your contribution.
Make sure to add tests and verify all the tests are passing when merging upstream.
Add an entry to the Changelog accordingly.
Please add your name to the CONTRIBUTORS.md file. Adding your name to the CONTRIBUTORS.md file signifies agreement to all rights and reservations provided by the License.
Squash related commits together.
Open a pull request.
The pull request will be reviewed by the community and merged by the project committers.

Why are there so many commits ? Did you base off master ?

never mind, I saw the code now, i always dash and dot.


False raid names can be created using the twitter reset function.

If you use the twitter refresh in-game and add the text
参加者募集！参戦ID：[RAID CODE] [RAID NAME]
eg
参加者募集！参戦ID：114514810
Lv100 ケルベロス
(found at https://twitter.com/megakureiXrdR/status/807071380277579776/photo/1)
it shows up in the raid listing even if the tweet is removed (image: http://i.imgur.com/3iAFJLu.png, I was testing to see how the cerberus one showed up and added a fenrir one by accident. Deleted the tweet but the listing still remains 2 days later.)

Thanks for the report!


Do not write to workspace settings

This is the version published to the marketplace. (I didn't have commit rights to this repo)
fyi @waderyan

@alexandrudima thanks!


unhandled 'error' event : cannot read property 'toUpperCase' of undefined

Hi,
I get an error with jhipster uml when I try to parse my diagram. I created a simple class diagram with only one class and two attribute (Integer and String)  and when I use the command :
jhipster-uml myfile.uml
this error is thrown :
Found the .jhipster/UMLTest.json configuration file, automatically generating the entity
The entity UMLTest is being created.
events.js:141
throw er; // Unhandled 'error' event
^
TypeError: C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster
entity\templates\src\test\java\package\web\rest_EntityResourceTest.java:53
51|
52|     private static final DateTimeFormatter dateTimeFormatter = DateTimeFormat.forPattern("yyyy-MM-dd'T'HH:mm:ss'Z'");<% } %>

53| <% for (fieldId in fields) {
54|     var defaultValueName = 'DEFAULT_' + fields[fieldId].fieldNameUnderscored.toUpperCase();
55|     var updatedValueName = 'UPDATED_' + fields[fieldId].fieldNameUnderscored.toUpperCase();
56|

Cannot read property 'toUpperCase' of undefined
at eval (eval at  (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\ejs\lib\ejs.js:455:12), :100:77)
at C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\ejs\lib\ejs.js:482:14
at Object.exports.render (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\ejs\lib\ejs.js:316:13)
at copy.process (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\mem-fs-editor\actions\copy-tpl.js:14:18)
at applyProcessingFunc (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\mem-fs-editor\actions\copy.js:13:16)
at EditionInterface.exports._copySingle (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\mem-fs-editor\actions\copy.js:51:16)
at EditionInterface.exports.copy (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\mem-fs-editor\actions\copy.js:23:17)
at EditionInterface.module.exports [as copyTpl] (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\mem-fs-editor\actions\copy-tpl.js:12:8)
at EntityGenerator.template (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\actions\actions.js:134:11)
at EntityGenerator.files (C:\Users\noside\AppData\Roaming\npm\node_modules\generator-jhipster\entity\index.js:876:10)
I tried with UML Designer and GenMyModel (with XMI export) but i always get the same issue
FYI : The version of my jHipster is v2.16.0, I installed this version to work with java 7.
Thank you for your help,
Noside

Hello, can you post a pic of your diagram or at least copy/paste your XMI? I think you may have an error in your diagram.

XMI :

<uml:Model xmi:version="20131001" xmlns:xmi="http://www.omg.org/spec/XMI/20131001" xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML" xmi:id="_K9CMIJ8XEeWzicw_Cnjtpg" name="NewModel">

</uml:Model>

Seems ok to me. Can you copy/paste TestUML.json from the .jhipster folder please?

{
"relationships": [],
"fields": [
{
"fieldId": 1,
"fieldName": "idTest",
"fieldType": "Integer"
},
{
"fieldId": 2,
"fieldName": "label",
"fieldType": "String"
}
],
"changelogDate": "20151210143708",
"dto": "no",
"pagination": "no"
}

I don't see any error (except a tiny one about the id, but I highly doubt it can cause that). Try updating JHipster (generator-jhipster) and JHpster_UML to the latest version.

I can't update jHipster because I want to work with Java 7, I think I will have to create my entities manually.
Thanks for your support
Regards,
Noside

You could do that, or downgrade the version of JHipster-UML v1.2.1 (warning, there were some bugs back in the day).


[Toolkit bug]: Viewport resolution resets after each restart.

Contact Details (Optional)
No response
Describe the bug
Viewport resolution resets to screen native res after each restart. Should stick to whatever user sat it to.
How do you reproduce the bug?

Start Toolkit, set preferred viewport res
Restart Toolkit

What is the expected behavior?
The toolkit should...
Version
2024.1.1

I created REMIX-2685.

I created REMIX-2685.

Hi sjgillard! Any updates on this issue?


Hello, there is a problem with the deployment of vercel. Please help.

Hello, after I have finished installing with vercel, the query functions such as IP, whois, mailbox and so on cannot be used.
The following error occurred in querying IP
Domain not found
Looks like the domain whois.com hasn't been registered yet.
The following error occurred in querying the domain name
An unexpected error occurred.
Error code: unauthorized

我部署的网站域名是，whois.ls

see #24


tilt/haml.rb:77: Haml::Engine#precompiled_method_return_value forwards to private method Haml::Compiler#precompiled_method_return_value

amber 0.3.12 when rendering a page shows a lot of
/var/lib/gems/2.5.0/gems/tilt-2.0.8/lib/tilt/haml.rb:77: warning: Haml::Engine#precompiled_method_return_value at /usr/lib/ruby/2.5.0/forwardable.rb:157 forwarding to private method Haml::Compiler#precompiled_method_return_value
It's probably benign but spoils the output.

sorry for the noise, I just had to update haml (4.0.7->5.0.4)


Django 1.10 incompatibility

Hey,
I just upgraded to Django 1.10, and here's the startup error:
Traceback (most recent call last):
  File "./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "xxx/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 367, in execute_from_command_line
    utility.execute()
  File "xxx/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 341, in execute
    django.setup()
  File "xxx/venv/lib/python3.5/site-packages/django/__init__.py", line 27, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "xxx/venv/lib/python3.5/site-packages/django/apps/registry.py", line 85, in populate
    app_config = AppConfig.create(entry)
  File "xxx/venv/lib/python3.5/site-packages/django/apps/config.py", line 90, in create
    module = import_module(entry)
  File "/usr/local/Cellar/python3/3.5.2_1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 665, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "xxx/venv/lib/python3.5/site-packages/django_mobile/__init__.py", line 10, in <module>
    from django_mobile.conf import settings
  File "xxx/venv/lib/python3.5/site-packages/django_mobile/conf.py", line 23, in <module>
    class defaults(object):
  File "xxx/venv/lib/python3.5/site-packages/django_mobile/conf.py", line 33, in defaults
    for loader in django_settings.TEMPLATE_LOADERS:
  File "xxx/venv/lib/python3.5/site-packages/django/conf/__init__.py", line 54, in __getattr__
    return getattr(self._wrapped, name)
AttributeError: 'Settings' object has no attribute 'TEMPLATE_LOADERS'

I use this as a temporary fix:
TEMPLATE_LOADERS = TEMPLATES[0]['OPTIONS']['loaders']

yeah, I did that too, but still, it's deprecated.

Hey thanks for the report! I'm not actively using django-mobile in any project currently, so I won't fix this any time soon. But I'm very happy about any PRs if you want to try and tackle the problem.

Does the commit above mean that this package is now compatible with 1.10?

Worth noting that approach with TEMPLATE_LOADERS = TEMPLATES[0]['OPTIONS']['loaders'] may be too naive, because you can use Jinja as first template engine, which doesn't have loaders section at all. Better way is to look up NAME == "django"

@gregmuellegger Are you still maintaining this project?

To anyone landing here who use more recent versions of Django, you might have some luck here:
https://github.com/selwin/django-user_agents


[3752] Use api instead api2

Context
In the api docs, we referred to the endpoint as api2 instead we should
be referring to api.
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Don't link https://api2.publish-teacher-training-courses.service.gov.uk/api/public/{version} as it's not a valid link. We can probably fix this link so that it does work.

@misaka I was wondering about the dns changes. As we haven't published these docs could we still merge this for the time being?

Blocked until DNS has been done


test versioned copy with urlencoded keys

test case for https://github.com/ceph/ceph/pull/25498

@alimaredia i rewrote this in boto3, can you please review?

Test is passing on master: http://qa-proxy.ceph.com/teuthology/amaredia-2019-06-04_21:38:09-rgw:verify-master-distro-basic-smithi/4005101/teuthology.log


Help removing alpha patch

Hi!
I've been using your build of st but would like to remove the alpha patch (since I don't need it). Going on the suckless website for the alpha patch, it looks like you're using a different one. I would appreciate if you could give me refer me to the code that adds alpha patch functionality to your build.
Thanks.

Yeah I'm trying to remove it as well

@GroosL After some help by @bakkeby, I've successfully removed the alpha patch from the build. This commit explains it better.


Added different page size for our needs

I'm using a library to generate the pdf, unfortunately as it is right now it doesn't have the possibility to change the page size, what would be required. Therefore, I forked the repo and added personal size. Later on, the idea would be to have a function that allows to set the size before to generate the pdf.
I don't know if forking a repo is a good solution or not?! To be discussed...

Still needed @Cr4spy? Happy to make a pull request. The B size are a good amendment anyway.

Apparently already implemented with the AddPageSize function. See https://godoc.org/github.com/jung-kurt/gofpdf#example-Fpdf-PageSize

Closing because of age


Invoke-Build v2.14.5

Updated to the latest version.

Is it forgotten? On the other hand, a new version is coming a few days, so it's not a big deal.

Sorry. I'm not sure why I didn't merge this after liking it. Thanks for the reminder.


Paths Aggregation

Coverage remained the same at 94.118% when pulling f79e490ba87e6ff5df5490f53b2247e0af154043 on feature/Paths_Aggregation into 71dbf403a7d56e71bf28f01bcb7bf45313ab5b28 on master.


Add hide_if_single_page option

@ongakuer
Thank you this very nice library.
I would like to hide the indicator when there is single page.
So I added this option.

Thanks your PR.
I think it is not necessary to add this option. When you update your adapter, you can change indicator visibility.
mCircleIndicator.setVisibility(mPagerAdapter.getCount() >= 0 ? View.VISIBLE : View.GONE);

Oh..
That way looks good. Thank you!


Wayland windows' colors are too dark

breakout-wayland.log

kwin
bevy: cb4e8c83
Nvidia GTX 970

Bloom has known issues with transparency, which will be fixed by https://github.com/bevyengine/bevy/pull/6677.
The lightness shift is interesting though.

Alright, removing bloom from the title to keep the issue focused.
For what it's worth, I tested on gnome as well, and it's behaving the same, so likely not a compositor bug.

wayland on the left, x11 on the right
The colors on X11 are consistent with what I see on Windows and wasm, (just confirming it's wayland that is off, and not x11)

From the wayland logs, it looks like we're creating the right kind of surface:
[1036841.262]  -> wl_surface@18.frame(new id wl_callback@43)
[1036841.622]  -> zwp_linux_dmabuf_v1@45.create_params(new id zwp_linux_buffer_params_v1@51)
[1036841.633]  -> zwp_linux_buffer_params_v1@51.add(fd 51, 0, 0, 5120, 50331648, 5234708)
[1036841.639]  -> zwp_linux_buffer_params_v1@51.create_immed(new id wl_buffer@54, 1280, 720, 875713089, 0)
[1036841.644]  -> zwp_linux_buffer_params_v1@51.destroy()

We're creating a surface with the 875713089 format, which is AR24 in fourcc (ARGB8888)
I'm not really sure how to dig further. I took some RUST_LOG=debug logs from running the breakout example as well. Let me know if there's any other way I can help.
breakout-debug-wayland.log

So we should be able to fix this once we land wgpu 0.15, but it requires using texture_views on non-srgb surfaces (and we should still default to srgb surfaces if they're available).
The problem is I wasn't able to get them working without a ton of vulkan validation errors, so I opted out of it for that PR.

@Elabajaba the recently released wgpu 0.15.1 should fix this. Do you mind taking another stab at it?

@JMS55 I found the color is still too dark on Wayland with the lasted commit (eaac730617103b61fd5ede9dca463243f2d7900e) which contains wgpu 0.15.1 update:
On Wayland:
RUST_BACKTRACE=1 RUST_LOG=info WGPU_BACKEND=vulkan cargo run --features wayland --example fog

and on X11:
RUST_BACKTRACE=1 RUST_LOG=info WGPU_BACKEND=vulkan cargo run --example fog

bug exists on nvidia-dkms it seems. testing nvidia-open-dkms to see if there is a difference.
nvidia-dkms/525.89.02 with an RTX 3070 lhr
running cachyos linux kernel 6.1.12-1
running said apps with wayland and using swrast/lavapipe gets me the correct colors so that leads me to believe its a driver issue, while testing this i also discovered that the bloom example has a bug where the window is transparent when intensity is postive
xorg:

wayland:

So this problem only happens on NVIDIA's GPU?  Are there any similar issues on Intel or AMD?
I'm also using nvidia-dkms-open and experiencing this problem.

So this problem only happens on NVIDIA's GPU?  Are there any similar issues on Intel or AMD?
I'm also using nvidia-dkms-open and experiencing this problem.

I'll try and get a pr up tomorrow to use an srgb texture view when the surface format isn't srgb now that it was fixed on the wgpu side.

Surprise fix 😲


Allow passing a default timestamp to prometheus decode API

Modify prometheus decode API to receive opts struct which encapsulates errbuf/errbuf_size
Add default_timestamp option

@edsiper the reason I added a default_timestamp option (instead of calling cmt_time_now() directly when parsing) is that it is more flexible and allows easier testing. I've added a test example, but you can use current scrape timestamp like this:
const char *inbuf = ...;
struct cmt *cmt;
struct cmt_decode_prometheus_parse_opts opts = {
    .errbuf = NULL,
    .default_timestamp = cmt_time_now()
};
cmt_decode_prometheus_create(&cmt, inbuf, &opts);

This API change will also make it easier customize parsing in the future without breaking existing callers.
fix #67

thanks!


Add release notes for SwiftPM 5.6

Modifications:

add Documentation/ReleaseNotes/5.6.md file

@swift-ci please smoke test


Version: 0.1.3 - source folder always comes back with ./

Tried to use the DNX Tasks Build Web, but run into an error where the script adds ./ in front of the source directory even when I provide fully qualified path e.g. ".\F:\agent_work\57\s\xxx\Service\project.json". To be clear I tried relative path but the script BuildWebPackage.ps1 keeps inserting ./ no matter what.

You are right, the path is always relative to the Working Folder.
If you do not have the src folder you can leave this field blank.
I did not think about absolute paths here. Can you please explain why you need to specify an absolute path here?
I will try to get this working with your requirements.
Greetings,
KirK

when leaving the source folder blank I'm getting the following error:
Cannot bind argument to parameter 'Path' because it is an empty string

I think the problem here is that VSTS allows you to use a full qualified path, but your scripts do not check for fully qualified paths and instead enforce .\ on everything regardless of input.

Hi,
an empty path should be ok for this. But it does not work. I will do some work on this in the next days.
So hopefully this is fixed in a short amout of time.
Thanks for the Feedback.
KirK

Hi,
I did some work on this issue and published a new version of the extension.
There is now a check if the given path is an absolute path. Also the empty field should now work as intended.
Can you give this a try?
CU, KirK


Fix build with GCC13

Due to changes in GCC13 the stdint include needs to be changed from C to C++ style.
Upstream PR: https://github.com/mfontanini/libtins/pull/496
issue: SW-137831

@pyian-cerebras Please approve this PR.
(This repo seems to be very locked down and it requires a reviewer with write access to approve it.)

Write access for @chris-cerebras : CBSD-9242