installing route Unknown blueprint: route

Hi,
I installed https://github.com/zkwentz/ember-simple-auth-firebase and I read all the issues concerning   code to be inserted in /config/environment.js  ENV.emblemOptions = {
blueprints: false
}; plus npm install plus bower install plus I updated ember to the version
ember-cli: 2.13.1
node: 6.10.3
os: darwin x64 but I still get installing route Unknown blueprint: route with just above at Function.Addon.lookup (/Users/artedys/authe
ntication/ember-simple-auth-firebase/node_module
s/ember-cli/lib/models/addon.js:1610:27) and where I search for addon.js I find nothing Globally I try to run ember authentication with firebase and I find no program that run. Is someone there who found a solution ? Bug or global ember authenticate with firebase that run in ember-cli: 2.13.1 because the old versions are no longer operational
Here is the entire bug when I type ember g route application
I get
s/ember-cli/lib/models/addon.js:1610:27)
DEPRECATION: Overriding init without calling thi
s._super is deprecated. Please call this._super(
), addon: Ember CLI ic-ajax
at Function.Addon.lookup (/Users/artedys/authe
ntication/ember-simple-auth-firebase/node_module
s/ember-cli/lib/models/addon.js:1610:27)
DEPRECATION: Overriding init without calling thi
s._super is deprecated. Please call this._super .init && this._super.init.apply(this, arguments) ; addon: torii
at Function.Addon.lookup (/Users/artedys/authe
ntication/ember-simple-auth-firebase/node_module
s/ember-cli/lib/models/addon.js:1610:27)
DEPRECATION: Overriding init without calling thi
s._super is deprecated. Please call this._super .init && this._super.init.apply(this, arguments) ; addon: torii
at Function.Addon.lookup (/Users/artedys/authe
ntication/ember-simple-auth-firebase/node_module
s/ember-cli/lib/models/addon.js:1610:27)
installing route
Unknown blueprint: route

For anyone facing the same Issue: I had the same error. As a temporary workaround, I just delete ember-cli-emblem entry in my package.json, generate route and add the package again. Works for me for the time being.
cc @EmberJSParis

Also, this issue is a duplicate of https://github.com/Vestorly/ember-cli-emblem/issues/55 . This can probably be closed.

thank you for submitting issue - same as #55


Write API tests for Apple Pay

Interested in working on this one, but I assume it may require the ApplePay functionality in #190 is already done?

added you jarod based on comment and included in project board.


Call to a member function getStatusCode() on null

This happens when there is no response, this package uses guzzlehttp, GuzzleHttp provides a method to return status code called getStatusCode()
$code = $response->getStatusCode(); // 200
You should use try catch block to catch RequestExceptions


Documentation: make some of the policy examples valid

Add the brackets so that each example can be taken seperately
and loaded. Makes it more copy / paste friendly.
Also use the correct syntax for ports so we don't end up with empty
toPorts, thanks André for pointing this out.
Signed-off-by: Alexander Alemayhu<EMAIL_ADDRESS>

Good catch. What would be better in my opinion is a way for us to substitute these files into the docs. That way we could do some validation on the files themselves as part of the build instead of realizing retroactively that we have to change them. Do you think this is feasible?

@ianvernon sounds good. Please create an issue for tracking but patches are also welcome ;)

@scanf  #1845 created


Bump golang version to 1.20.5

What this PR does / why we need it:
This PR bumps the golang version to 1.20.5
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist

[ ] Documentation added
[ ] Tests updated

Actually I think there were two issues with the CI but running it in another PR by me made also this PR's CI green. (probably matched by the same commit hash)
Anyway, this PR didn't update the go version in CI therefore I'm creating a new one.


Add support for custom actions (IS-9, IS-10)

This PR adds supports for signing and verification of custom actions through
distributed auth. To do this, it adds two new functions:

sign_custom_payload
verify_custom_payload

LGTM!


permission denied error when trying to write to node_modules

Whenever the -s command is passed, an EACCESS error is thrown. How to fix?

This can be solved by running sudo before weather -s, but I don't think people are gonna want to run as admin

This can be solved by running sudo before weather -s, but I don't think people are gonna want to run as admin

This is only an issue if users are installing npm modules in a directory that they do not have permissions to write to.
I usually just add
prefix=/Users//npm
to ~/.npmrc
And then add /Users//npm/bin to my PATH
This installs all global npm modules to a directory to that your user owns, and prevents any of these kinds of permission problems. If you are ever using sudo when using npm you will probably run into issues down the road.
That being said, because it is very common for users to install global node modules in the directory that they do not own, it is probably best to save the configs in such a way that will not break when that is the case.

I'm trying to work out a solution with child processes running a sudo command and I'll branch it soon

For now, I'll branch something and you guys can pull against it and I've published a new version where, if the -s argument is passed, it'll say something about running sudo


⚠ Processors has degraded performance

In 32ef99b, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 40 ms

Resolved: Processors performance has improved in ac1b789.


Cleanup: Remove dev-armada from docs/dev

With @suprjinx work on localdev, we no longer need the dev-armada make target and the config files.
A correspond PR should address the following:

Remove docs/dev/config
Remove references to dev-armada make target and its correspond items.
Update docs/dev/README.md to point to new method for setting up development environment.

Hey team! Please add your planning poker estimate with Zenhub @ClifHouck @dejanzele @headphonejames @kannon92 @richscott @Sharpz7 @suprjinx


Add missed serialization schema argument for PulsarOutputFormat

The constructor of PulsarOutputFormat expects a serializationSchema passed in otherwise it's member serializationSchema will be assigned by itself.

run integration tests

run integration tests

run integration tests


Add links to the rukpak one pager hackmd design documentation

Goal: Ensure devs/users can discover design documentation over time.
Right now most of the design (e.g. one pagers) documentation is hosted on a rukpak team hackmd. It might be worth surfacing that public link somewhere in the short term.

I'm not sure you can link to the rukpak team notes directly -- if I try on a private browser session, I get a 403.
Does this imply we should provide direct links to each public note?

Does it make sense to have those one pagers live in-tree for this repository then? Those designs should be public facing anyways.

I opened a PR which compromises: it includes a link to all the HackMD documentation.
Copying it and having it live in tree is an alternative, but this approach is less toil and just as useful.


template --pre-render option

Hello there!
First, thanks for your hard work :)
I encountered a need and I don't think I'm the only one who wants to do that, I would love to have a pre-render option for the template command.
The use case:
I got multiple applications, deployed the same way with helm charts and kustomize.
Actually kustomize let me injects labels on specific ressources , but I need to statically define each infra-environnements, I can't do logical stuff there.
And here's the catch, I want to enforce specific rules on this labels to be able to not let anybody else put some bad labels there, and then manage this "labels rules" in the helm charts build and release ci steps.
Having a pre-render kustomize capacity would let me use helm templates in kustomize, and will be able to inject this labels before the template is rendered, and use variables defined in the values.yml or given in the environment when deploying, giving me the possibility to use kustomize injection dynamically.
Dunno if there's a way to do this, but I think it's not a bad feature to add :)

Would the post-renderer flag do what you're looking for? You could run it with the template command:
      --post-renderer postrenderer   the path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path (default exec)

Actually I want to inject template in an already packaged helm chart template, without injecting any values in it.
My use case is to add annotations template in an already existing helm chart (which does not have annotations), without having to mirror it or edit the original charts themselves, and before applying values to the templates, like what kustomize do, but before applying values to the templates... In a pre render hook or something else.
The only "way" I found to stay with a full helm / kustomize stack is to use a job I which will act as an injector, like for the vault injector.

For more information, I opened an issue in kustomize as well: https://github.com/kubernetes-sigs/kustomize/issues/4519


Do Dynamic Device Groups work for conditional access policies?

Does conditional access also work with azure dynamic device groups as well? I don not see it mentioned specifically in the article, only that it talks about users, but not devices.

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

ID: cae7bc92-8489-ff66-9ce0-b4fab08eb7b8
Version Independent ID: 55dfcb5c-62cd-8485-7d55-de3459cb2854
Content: Users and groups in Conditional Access policy - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/conditional-access/concept-conditional-access-users-groups.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

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

#reassign:@MicrosoftGuyJFlo

No, you cannot address devices using dynamic groups. Best bet is to use Filters for Devices.
#please-close


Component development

Added new factories:

Dual polarization grating coupler
Straight Ge detector with contacts in the Si
MMI-based 90 degree hybrid

Thank you Marc!


execlineb complaint when terminating container

When running one of the examples and when I hit ctrl+c to terminate I see:
==> Caught signal: terminated
==> Gracefully shutting down agent...
    2016/01/06 20:45:30 [INFO] consul: client starting leave
execlineb: usage: execlineb [ -p | -P | -S nmin ] [ -q | -w | -W ] [ -c commandline ] script args
[cont-finish.d] executing container finish scripts...

Perhaps related but at the very end I see s6-svscanctl error:
[s6-finish] sending all processes the TERM signal.
    2016/01/06 20:45:30 [ERR] dns: error starting tcp server: accept tcp <IP_ADDRESS>:8600: use of closed network connection
    2016/01/06 20:45:30 [INFO] agent: requesting shutdown
    2016/01/06 20:45:30 [INFO] consul: shutting down client
    2016/01/06 20:45:30 [WARN] serf: Shutdown without a Leave
    2016/01/06 20:45:30 [INFO] agent: shutdown complete
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[s6-finish] sending all processes the KILL signal and exiting.

@matthewvalimaki, can you remember which example? It's not obvious to me from the output...

@smebberson sorry for the delay.
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
Error connecting to Consul agent: dial tcp <IP_ADDRESS>:8400: connection refused

That I see by doing docker run --rm --name consul-server smebberson/alpine-consul and then hitting CTRL+C.

This has been fixed in recent releases.


Cannot Connect To Local TPU-VM

Describe the bug
When I try to connect to the TPU to finetune, it gives me this error:
Traceback (most recent call last):
  File "main.py", line 257, in <module>
    main(args)
  File "main.py", line 251, in main
    estimator.train(input_fn=partial(input_fn, global_step=current_step, eval=False), max_steps=params["train_steps"])
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_estimator.py", line 3110, in train
    rendezvous.raise_errors()
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/error_handling.py", line 150, in raise_errors
    six.reraise(typ, value, traceback)
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/six.py", line 703, in reraise
    raise value
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_estimator.py", line 3100, in train
    return super(TPUEstimator, self).train(
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 346, in train
    hooks.extend(self._convert_train_steps_to_hooks(steps, max_steps))
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_estimator.py", line 2973, in _convert_train_steps_to_hooks
    if ctx.is_running_on_cpu():
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_context.py", line 531, in is_running_on_cpu
    self._validate_tpu_configuration()
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_context.py", line 699, in _validate_tpu_configuration
    num_cores = self.num_cores
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_context.py", line 429, in num_cores
    metadata = self._get_tpu_system_metadata()
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow_estimator/python/estimator/tpu/tpu_context.py", line 333, in _get_tpu_system_metadata
    tpu_system_metadata_lib._query_tpu_system_metadata(
  File "/home/nikhilnayak/.local/lib/python3.8/site-packages/tensorflow/python/tpu/tpu_system_metadata.py", line 135, in _query_tpu_system_metadata
    raise RuntimeError(
RuntimeError: Cannot find any TPU cores in the system (master address ). This usually means the master address is incorrect or the TPU worker has some problems. Available devices: [_DeviceAttributes(/job:localhost/replica:0/task:0/device:CPU:0, CPU, 268435456, -3188567715276368833)]

To Reproduce
Steps to reproduce the behavior:
I followed the instructions for finetuning on this github page.
Expected behavior
The finetuning program should finetune with my dataset without datasets.
Proposed solution
N/A
Environment (please complete the following information):

TPU Version: v2-alpha
TPU Type: v3-8
Architecture: TPU-VM

This codebase is not actively maintained and was created before TPU VMs existed. You’ll probably have to figure it out yourself, unfortunately.
You may want to check out Mesh Transformer Jax, which is a more actively maintained Jax-based TOU framework


[FEATURE] More experience settings

As talked about in #67, the experience settings provided are somewhat lacking. I'll be working on this next; most likely adding an uncapped variant of vanilla and a percentage based version.

Changes so far

The experience storage types have changed as such: [ALL, DEFAULT, CUSTOM] -> [ALL, VANILLA, NONE]
MaxCustomXPLevel has been renamed to levelCap.
A new config option, percentage, has been added.

Storage types

ALL:
All experience is calculated.
VANILLA:
Experience is calculated based on the vanilla algorithm (level * 7).
NONE:
Experience is always calculated as 0.

How the new system works
This can be explained in three steps:

The experience is calculated based on the storage type.
Said experience is multiplied by the configured percentage (and rounded).
The level cap is enforced.

I'm debating whether percentage should be used on the experience after it's been calculated or on the level before experience calculation. Here's what each would look like (I think the latter makes more sense):
Experience after calculation
If you're L30 when you die (1396 experience points), and have percentage set to 50, you'd end up level 22 and some change  upon grave retrieval (698 experience points).
Level before calculation
If you're L30 when you die, and you have percentage set to 50, you'd end up L15 upon grave retrieval.

Alright, I think this is feature complete and tested. It'll be part of the 3.2.0 update that should come out soon™. For now, here's the options I've settled with:
"experience": {
  "expStorageType": "ALL (Default) | VANILLA | NONE",
  "percentage": 100,
  "percentageType": "POINTS (Default) | LEVELS",
  "cap": -1,
  "capType": "LEVELS (Default) | POINTS"
},

I think this particular blend of options should be versatile and allow users to fine tune it to their liking. For example, you could tax people on death with percentage or replicate vanilla's amount of experience with this configuration:
"experience": {
  "expStorageType": "VANILLA",
  "percentage": 100,
  "percentageType": "POINTS",
  "cap": 100,
  "capType": "POINTS"
},

I'm closing this as it has been added in 3.2.0 (which has been released for 1.19.2 so far, the later versions will likely come later this week).


unicode is evaluated instead of being printed as it is in the code

def characterLiteralsUnicodeLiteralStrings(res0: String) {
    val c = '\u0061' //unicode for a

    c.toString should be(res0)
  }

prints to
val c = 'a' //unicode for a
Source code: https://github.com/scala-exercises/exercises-stdlib/blob/master/src/main/scala/stdlib/LiteralStrings.scala
Page: https://www.scala-exercises.org/std_lib/literal_strings

Thanks for reporting this. Do you have a proposal how to fix it or would you like to remove this part?

looks like a framework bug. The Oct code is parsed properly.
Temporary walkaround would be a better comment.


Disable integration tests on macOS to unblock CI

SwiftPM command plugins can only be run when the Swift concurrency libraries are available. For some reason these libraries are no longer available in the macOS used in SwiftCI so this disables those tests after performing a check to see if concurrency is available.
This mirrors the implementation in SwiftPM itself here: https://github.com/apple/swift-package-manager/blob/dd7e9cc6/Sources/SPMTestSupport/Toolchain.swift#L55

@swift-ci please test

@swift-ci please test

@swift-ci please test


Move all the GpuShuffleExchangeExec shim v2 classes to org.apache.spa…

Move all the GpuShuffleExchangeExec shim v2 classes to org.apache.spark.rapids.shims.v2
Fixes #3609
Signed-off-by: Chong Gao<EMAIL_ADDRESS>

build

LGTM

Make all the packages of GpuShuffleExchangeExec shim v2 consistent.
The Databricks version, MapOutputStatistics is in spark private package, so move all GpuShuffleExchangeExec shim v2 to org.apache.spark.rapids.shims.v2 package, make all of them consistent.

since touched DB shims, added [databricks]  for CI build

build


Version up to 1.3.0rc1

Summary

How to test

Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added integration tests to cover my changes.
[ ] I have added the description of my changes into CHANGELOG.
[ ] I have updated the documentation accordingly

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (5c3e21a) 78.48% compared to head (da09c88) 78.47%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1007      +/-   ##
===========================================
- Coverage    78.48%   78.47%   -0.02%
===========================================
  Files          237      237
  Lines        26973    26973
  Branches      5369     5369
===========================================
- Hits         21171    21167       -4
- Misses        4532     4534       +2
- Partials      1270     1272       +2

Flag
Coverage Δ

macos-11_Python-3.8
?

ubuntu-20.04_Python-3.8
78.47% <ø> (+<0.01%)
:arrow_up:

windows-2019_Python-3.8
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

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


Missing project license

Hey,
I came across this tool and it seems very useful.
Would you be OK with adding an explicit license? Without a specific license, it defaults to exclusive copyright on GitHub, meaning users are not allowed to use, modify or share the code. This even includes just running the software as is.
I see there are already several forks that adds to the work which technically is a breach unless I'm mistaken.

The current situation from GitHubs docs: https://choosealicense.com/no-permission/
Adding a license docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license
StackOverflow thread on this topic: https://opensource.stackexchange.com/questions/1720/what-can-i-assume-if-a-publicly-published-project-has-no-license

The https://choosealicense.com offers you three very popular licenses a click away with a short description of what they're about.
Thanks!

Thanks for bringing this to my attention. ea0ce2ccb6b4757420aa56ab7cf5eba27313fd60 Done.


Uplampling2D args:interpolation='nearest' isn't supported in TFLite or TFLite converter

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):18.04
TensorFlow installed from (source or binary):binary
TensorFlow version (or github SHA if from source):2.2.0

Tensorflow installed using pip3 insall tensorflow==2.2.0
$pip3 show tensorflow
Name: tensorflow
Version: 2.2.0
Summary: TensorFlow is an open source machine learning framework for everyone.
Home-page: https://www.tensorflow.org/
Author: Google Inc.
Author-email<EMAIL_ADDRESS>License: Apache 2.0
Location: /home/nymble/.local/lib/python3.6/site-packages
Requires: wrapt, google-pasta, gast, protobuf, six, opt-einsum, absl-py, astunparse, tensorboard, scipy, keras-preprocessing, grpcio, wheel, tensorflow-estimator, numpy, termcolor, h5py

Model code :
import tensorflow as tf
from  tensorflow.keras import models
from tensorflow.keras import layers
from tensorflow.keras.optimizers import SGD, Adam
#-----------------------------------------------------##
model = models.Sequential()
model.add(layers.Conv2D(32, (3, 3), padding='same', input_shape=(224, 224, 3)))

model.add(layers.Conv2D(32, (3, 3), padding='same'))
#model.add(layers.BatchNormalization())
model.add(layers.Activation('relu'))
model.add(layers.MaxPooling2D((2, 2)))

model.add(layers.UpSampling2D((2, 2), interpolation='nearest'))
model.add(layers.Flatten())
model.add(layers.Dense(1, activation='sigmoid'))

model.summary()

Model's summary looks like this:
Model: "sequential"
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
conv2d (Conv2D)              (None, 224, 224, 32)      896
_________________________________________________________________
conv2d_1 (Conv2D)            (None, 224, 224, 32)      9248
_________________________________________________________________
activation (Activation)      (None, 224, 224, 32)      0
_________________________________________________________________
max_pooling2d (MaxPooling2D) (None, 112, 112, 32)      0
_________________________________________________________________
up_sampling2d (UpSampling2D) (None, 224, 224, 32)      0
_________________________________________________________________
flatten (Flatten)            (None, 1605632)           0
_________________________________________________________________
dense (Dense)                (None, 1)                 1605633
=================================================================
Total params: 1,615,777
Trainable params: 1,615,777
Non-trainable params: 0
__________________________

Trained this model and saved it as sample_model.h5.
Loaded this model again in a separate code using:

model_dir = '/home/nymble'
nymble_model = models.load_model(os.path.join(model_dir,'sample_model.h5'))
print("Model loaded")

converter = tf.lite.TFLiteConverter.from_keras_model(nymble_model)
#converter.optimizations = [tf.lite.Optimize.OPTIMIZE_FOR_SIZE]
tflmodel = converter.convert()

Running this code gives error at 6th line :

Exception: /home/nymble/.local/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py:865:9: error: 'tf.ResizeNearestNeighbor' op is neither a custom op nor a flex op
        self._initialize(args, kwargs, add_initializers_to=initializers)
        ^
/home/nymble/.local/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py:959:5: note: called from
    concrete = self._get_concrete_function_garbage_collected(*args, **kwargs)
    ^
/home/nymble/.local/lib/python3.6/site-packages/tensorflow/lite/python/lite.py:435:5: note: called from
    concrete_func = func.get_concrete_function()
    ^
/media/nymble/Nymble_Storage/ML_Data/my_passport/keras_data/convert_keras_to_tflite.py:20:1: note: called from
converter = tf.lite.TFLiteConverter.from_keras_model(nymble_model)
^
<unknown>:0: error: failed while converting: 'main': Ops that can be supported by the flex runtime (enabled via setting the -emit-select-tf-ops flag): ResizeNearestNeighbor.

Also if i use 'bilinear' interpolation parameter in Upsampling2D, Tflconverter doesn't raises this error.
Attached is the sample_mdoel.h5 graph to look into.
sample_model.zip

The above ResizeNearestNeighbor op can be supported via Select TF ops. You can follow the below guides to add the Select TF ops:
https://www.tensorflow.org/lite/guide/ops_select#android_aar
https://www.tensorflow.org/lite/guide/reduce_binary_size

@pranshugo,
I was able to convert the model without any issues on TF v2.3. Please find the gist of it here.
Could you please update TensorFlow to v2.3 and check if you are facing the same issue. Thanks!

Yes, please try the latest version of TF, as I believe this op was updated recently.

Yeah that solves my confusion.
Got it working.

@Pranshu195,
Thank you for the update. Marking this issue as closed, as it is fixed. Please feel free to re-open if necessary.


Using "dynamic" to use archives for the same function makes the program hang

Here is the code that decides what the dynamic is:
dynamic archive;
switch (type)
{
    case ".zip":
        archive = ZipArchive.Open(path);
        break;
    case ".7z":
        archive = SevenZipArchive.Open(path);
         break;
    case ".rar":
         archive = RarArchive.Open(path);
         break;
    default:
         throw new NullReferenceException();
}

And here is the code that extracts the files:
foreach (var entry in archive.Entries)
{
    if (thingInZip != null && entry.Key.Contains(thingInZip))
    {
        entry.WriteToDirectory(temppath, new ExtractionOptions()
        {
            ExtractFullPath = true,
            Overwrite = true
        });
    {
{

When doing this, unzipping the archive just makes the program hang.

need more detail.  but also: you don't need to do that.  Just use the base interface


Missing file game-settings.js

cloud/controller/js/game-settings.js as described on page 36 of Cloud Derby Setup Instructions is missing in this repo.

Oh I see the file is in the repo as settings.js and all the code references this file correctly. Looks like the doc just needs to be updated.

This has been renamed into settings.sh. I also updated the tutorial to reflect this.


Error maps from the API return as [object Object]

Seems related to #20 and #29. Also related to phoenixframework/phoenix#3323.
It seems like the various createFooError(errorMessage)s and the various upstream handlers all expect errorMessage to be a string. If my API returns a map instead we get [object Object].
In the other ticket I filed, I post a solution for preprocessing the error message into a string. However, I was wondering if it's reasonable to just check for stringiness in this library, and call JSON.serialize on the message if it's not a string?
A simple example would be changing createRequestError() to be:
const createRequestError = message =>
  new Error(`request: ${typeof message === 'string' ? JSON.stringify(message) : message}`)

(Would obviously benefit from more abstraction!)

Message must be string by spec.
We could consider adding support to extensions.

Duplicate of #29 (Let's follow the discussion there)


⚠ Bofrost.es has degraded performance

In ec2034f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1466 ms

Resolved: Bofrost.es performance has improved in d50d79f after 6 minutes.


mention render/renderString changes in the CHANGELOG

Thanks I updated the text, and pushed to pub.
Breaking change: Template.render and Template.renderString methods no longer take the optional lenient and htmlEscapeValues. These should now be passed to the Template constructor.

Thumbs up!


VS Code should use the CMake file API to work out the compiler being used

Brief Issue Summary
This is a follow-up to #2121 (that issue is locked, so I can't comment there directly).
VS Code shouldn't be trying to use CMAKE_C_COMPILER and CMAKE_CXX_COMPILER variables from the CMakeCache.txt file to determine the compilers being used. Toolchain files may (and frequently do) define those variables as ordinary non-cache variables, and CMake doesn't save those in the cache. This is expected and correct behavior. In such scenarios, the "No compiler found in cache file" error arises.
VS Code should instead use CMake's file API to query the toolchains object kind and obtain the compiler details from there. There's no reason it should be looking in the cache for this information. The file API should reliably provide it in all cases.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

Thanks for reporting this issue @craigscott-crascit.


Compatibility with Chinese SWR meter?

Hi.
A (Chinese ?) SWR meter claims compatibility with "G8GYW" firmware.
Is that THIS firmware, please?
Thanks.

I believe so, but as I have no connection with the seller and haven't seen their meter I can't confirm it.
Owen Duffy has reviewed a Chinese version here: https://owenduffy.net/blog/?p=26973.

Many thanks.


react-static create should include starter .gitignore

Is your feature request related to a problem? Please describe.
Unnecessary manual step to git init after react-static create. The painful bit is looking up a starter .gitignore. I come to the react-static git repo, find a suitable .gitignore such as this one.
Describe the solution you'd like
Deliver .gitignore as part of react-static create which I can modify or delete

This is a bug with npm pack. Currently it ignores .gitignore files in templating systems like React Static. We'll figure out a way to make this work better in the future.

@tannerlinsley What would be a basic gitignore file?
node_modules
tmp
artifacts

Anything else to add to this list?

Probably want to ignore dist/ too.

What would be a basic gitignore file?

See .gitignore in the templates:
https://github.com/react-static/react-static/tree/master/packages/react-static/templates

We'll figure out a way to make this work better in the future.

As of March 2021, this issue hasn't been fixed yet.
Let's reopen this issue?


Missing functionnality: online submission to specific tasks (and not all tasks)

This option is missing on the online submission form while this seems to be a possibility for bot-submissions (see example_submission.py)

Just started on this issue. Should be solved by the end of the week, if not before.


fixed the catch statement causing an error

Requirements for Contributing a Bug Fix
Identify the Bug

Description of the Change

Thanks

Thanks


[HxInputTags] Disabled - allows removing tags, displays AddButton

The control should not allow changing the value (tags).
But how should it look like when disabled?

Should we display the AddButton? While Naked? When no tags are there?
Should we display the Remove buttons on individual tags?

cc @crdo, @jirikanda

@Harvey1214, can you please check the behavior of HxInputTags when it is Enabled="false"? I think this was already fixed and we can close this issue.


Folder Size

Wonderful tool.
Does the job in a timely fashion. Any possibility to include the total size of folder along with the hash?
I know I could use "du -sh" but was just curious. Thanks.

In general, I like the unix philosophy of "make each program do one thing well".
Out of curiosity:

Is there a particular use case you need to cover?
What would you expect the flags for this to be? What would you expect the output to be (how should it be formatted)?

Just a simple output similar to "df -h"
Flag could be " -S " as there is an "s" already in place.


Docker build fails with "invalid argument" on encfs

I tried moving my Docker directory to a directory in my $HOME, which is encfs-encrypted and therefore has a pretty short filename length limit (143 characters?). Most Docker commands that "do" something (i.e., docker build, docker run) fail at some point with "invalid argument". Moving the directory outside of encfs makes everything go fine. I wonder if there's a chance to solve that issue or give at least a better error message.

what's your graph driver? Maybe you can provide docker version docker info uname -a and that we may can do more help

$ uname -a
Linux samsux 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ sudo docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

$ sudo docker info
Containers: 18
Images: 153
Storage Driver: aufs
 Root Dir: /home/docker/aufs
 Dirs: 189
Execution Driver: native-0.2
Kernel Version: 3.13.0-37-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 4
Total Memory: 7.508 GiB
Name: ***
ID: ***
WARNING: No swap limit support

Please note that /home/docker is outside of my encfs, where I am currently using it.

I don't know that this can be fixed if this is a character size limit. But the error message can certainly be improved.

We need to disallow aufs to be used on encfs or Docker on encfs entirely. Disabling aufs on encfs would solve the problem of not using aufs on top of encfs, but volumes would still have this problem. There's no point in giving the impression this works properly and error out later during a pull or during a similar operation.
The proper solution would be to forbid the use of an encfs fs path as a Docker directory and also blacklist it in aufs.

btw, error messages have been updated so at least you know where the error is coming from and at what point :)

Closing because encfs is not supported by the underlying CoW filesystems and docker will now error out if you try to use this configuration.


Stable safe events

An implementation of the events iterator which does not need impl Trait. This allows users of the crate to access the events without resorting to either nightly or unsafe.
I think of this implementation as a temporary solution while we wait for impl Trait. When impl Trait lands on stable, we can go back to the previous, more elegant, solution. Users should not need to change their code at that point, as along as they are just iterating over whatever the events() method returns (which should be the common use case).

Looks great.


Remove log spamming message

The "scanning" message burst from time to time, spamming log with thousand log lines in short period of time (under 30s).

Gentle ping?

will remove it for now but entire app needs to change logging to use different log levels for better logging and configuration (dev/prod)...


[WIP] repro hydrate() causes unhandled promise rejection with a throwing prefetchQuery

Debugging an issue where I see A query that was dehydrated as pending ended up rejecting. [${query?.queryHash}]: Error: server error; The error will be redacted in production builds logged, but my SSR render also returned a status code of 500.
Upon digging into the code, I think I found that hydrate() can cause an unhandled promise rejection from here when dehydrateQuery catches an error and returns a Promise.reject because a queryFn threw.
It seems like no tests are covering this, due to them ending before the rejection happens, but when I run the tests with the change in this PR, I get the following:

Test run
   ✔  nx run @tanstack/query-core:build  [existing outputs match the cache, left as is]
   ✔  nx run @tanstack/query-persist-client-core:build  [existing outputs match the cache, left as is]
   ✔  nx run @tanstack/react-query:build  [existing outputs match the cache, left as is]
   ✔  nx run @tanstack/query-devtools:build  [existing outputs match the cache, left as is]
   ✔  nx run @tanstack/react-query-persist-client:test:lib  [existing outputs match the cache, left as is]
   ✔  nx run @tanstack/react-query-devtools:test:lib  [existing outputs match the cache, left as is]
———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
✖  nx run @tanstack/react-query:test:lib
><EMAIL_ADDRESS>test:lib /Users/alvar/Code/query/packages/react-query
> vitest --retry=3
  Testing types with tsc and vue-tsc is an experimental feature.
  Breaking changes might not follow SemVer, please pin Vitest's version when using it.

   RUN  v2.0.5 /Users/alvar/Code/query/packages/react-query
        Coverage enabled with istanbul

   ✓ |@tanstack/react-query| src/__tests__/queryOptions.test-d.tsx  (18 tests)
   ✓ |@tanstack/react-query| src/__tests__/infiniteQueryOptions.test-d.tsx  (10 tests)
   ✓ |@tanstack/react-query| src/__tests__/useQueries.test-d.tsx  (6 tests)
   ✓ |@tanstack/react-query| src/__tests__/useInfiniteQuery.test-d.tsx  (7 tests)
   ✓ |@tanstack/react-query| src/__tests__/useQuery.test-d.tsx  (9 tests)
   ✓ |@tanstack/react-query| src/__tests__/useSuspenseQueries.test-d.tsx  (6 tests)
   ✓ |@tanstack/react-query| src/__tests__/suspense.test-d.tsx  (9 tests)
   ✓ |@tanstack/react-query| src/__tests__/prefetch.test-d.tsx  (5 tests)
  stderr | src/__tests__/prefetch.test.tsx > usePrefetchQuery > should let errors fall through and not refetch failed queries
  Error: Oops! Server error!
      at /Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:137:13 {
    [stack]: 'Error: Oops! Server error!\n' +
      '    at /Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:137:13',
    [message]: 'Oops! Server error!'
  }

  The above error occurred in the <Suspended> component:

      at Suspended (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:39:64)
      at Suspense
      at ErrorBoundary (/Users/alvar/Code/query/node_modules/.pnpm/react-error-boundary@4.0.13_react@19.0.0-rc-4c2e457c7c-20240522/node_modules/react-error-boundary/dist/react-error-boundary.development.esm.js:14:5)
      at App (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:126:29)
      at QueryClientProvider (/Users/alvar/Code/query/packages/react-query/src/QueryClientProvider.tsx:400:3)

  React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary.

  stderr | src/__tests__/prefetch.test.tsx > usePrefetchQuery > should be able to recover from errors and try fetching again
  Error: Oops! Server error!
      at /Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:200:13 {
    [stack]: 'Error: Oops! Server error!\n' +
      '    at /Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:200:13',
    [message]: 'Oops! Server error!'
  }

  The above error occurred in the <Suspended> component:

      at Suspended (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:39:64)
      at Suspense
      at ErrorBoundary (/Users/alvar/Code/query/node_modules/.pnpm/react-error-boundary@4.0.13_react@19.0.0-rc-4c2e457c7c-20240522/node_modules/react-error-boundary/dist/react-error-boundary.development.esm.js:14:5)
      at App (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:204:47)
      at QueryClientProvider (/Users/alvar/Code/query/packages/react-query/src/QueryClientProvider.tsx:400:3)

  React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary.

   ✓ |@tanstack/react-query| src/__tests__/useQueries.test.tsx  (19 tests) 673ms
   ✓ |@tanstack/react-query| src/__tests__/useMutation.test.tsx  (23 tests) 869ms
  stderr | src/__tests__/prefetch.test.tsx > usePrefetchInfiniteQuery > should prefetch an infinite query if query state does not exist
  Warning: Each child in a list should have a unique "key" prop.

  Check the render method of `Suspended`. See https://react.dev/link/warning-keys for more information.
      at div
      at Suspended (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:337:72)
      at Suspense
      at App (/Users/alvar/Code/query/packages/react-query/src/__tests__/prefetch.test.tsx:366:29)
      at QueryClientProvider (/Users/alvar/Code/query/packages/react-query/src/QueryClientProvider.tsx:400:3)

   ✓ |@tanstack/react-query| src/__tests__/HydrationBoundary.test.tsx  (7 tests) 180ms
   ✓ |@tanstack/react-query| src/__tests__/ssr-hydration.test.tsx  (3 tests) 127ms
   ✓ |@tanstack/react-query| src/__tests__/QueryResetErrorBoundary.test.tsx  (13 tests) 1842ms
   ✓ |@tanstack/react-query| src/__tests__/prefetch.test.tsx  (9 tests) 1971ms
   ✓ |@tanstack/react-query| src/__tests__/useInfiniteQuery.test.tsx  (26 tests) 2448ms
   ✓ |@tanstack/react-query| src/__tests__/useSuspenseQueries.test.tsx  (6 tests) 37ms
   ✓ |@tanstack/react-query| src/__tests__/useIsFetching.test.tsx  (5 tests) 350ms
   ✓ |@tanstack/react-query| src/__tests__/fine-grained-persister.test.tsx  (3 tests) 46ms
   ✓ |@tanstack/react-query| src/__tests__/useMutationState.test.tsx  (7 tests) 732ms
   ✓ |@tanstack/react-query| src/__tests__/ssr.test.tsx  (5 tests) 15ms
   ✓ |@tanstack/react-query| src/__tests__/QueryClientProvider.test.tsx  (4 tests) 62ms
   ✓ |@tanstack/react-query| src/__tests__/suspense.test.tsx  (22 tests) 10490ms
   ❯ |@tanstack/react-query| src/__tests__/useQuery.test.tsx  (139 tests | 1 failed) 10864ms
     × useQuery > should retry failed initialPromise on the client
       → Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:

          data:
          client

  Ignored nodes: comments, script, style

            failure:

            data:
            client

       → Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:

          data:
          client

  Ignored nodes: comments, script, style

            failure:

            data:
            client

       → Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:

          data:
          client

  Ignored nodes: comments, script, style

            failure:

            data:
            client

       → Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:

          data:
          client

  Ignored nodes: comments, script, style

            failure:

            data:
            client

  ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯

   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
  TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:

          data:
          client

  Ignored nodes: comments, script, style

            failure:

            data:
            client

   ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
   ❯ src/__tests__/useQuery.test.tsx:6587:11
      6585|
      6586|     const rendered = renderWithClient(clientQueryClient, <Page />)
      6587|     await waitFor(() => rendered.getByText('failure: redacted'))
         |           ^
      6588|     await waitFor(() => rendered.getByText('data: client'))
      6589|     expect(count).toBe(1)

  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/4]⎯

  ⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯

  Vitest caught 4 unhandled errors during the test run.
  This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

  ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
  Error: redacted
   ❯ ../query-core/src/hydration.ts:90:31

  This error originated in "src/__tests__/useQuery.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
  The latest test that might've caused the error is "should retry failed initialPromise on the client". It might mean one of the following:
  - The error was thrown, while Vitest was running this test.
  - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

  ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
  Error: redacted
   ❯ ../query-core/src/hydration.ts:90:31

  This error originated in "src/__tests__/useQuery.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
  The latest test that might've caused the error is "should retry failed initialPromise on the client". It might mean one of the following:
  - The error was thrown, while Vitest was running this test.
  - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

  ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
  Error: redacted
   ❯ ../query-core/src/hydration.ts:90:31

  This error originated in "src/__tests__/useQuery.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
  The latest test that might've caused the error is "should retry failed initialPromise on the client". It might mean one of the following:
  - The error was thrown, while Vitest was running this test.
  - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

  ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
  Error: redacted
   ❯ ../query-core/src/hydration.ts:90:31

  This error originated in "src/__tests__/useQuery.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
  The latest test that might've caused the error is "should retry failed initialPromise on the client". It might mean one of the following:
  - The error was thrown, while Vitest was running this test.
  - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

   Test Files  1 failed | 22 passed (23)
        Tests  1 failed | 360 passed (361)
  Type Errors  no errors
       Errors  4 errors
     Start at  16:52:31
     Duration  15.39s (transform 1.15s, setup 9.32s, collect 4.87s, tests 30.71s, environment 18.06s, prepare 1.41s, typecheck 2.72s)

   ELIFECYCLE  Command failed with exit code 1.

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
NX   Ran target test:lib for 3 projects and 4 tasks they depend on (19s)
✔  6/7 succeeded [6 read from cache]
✖  1/7 targets failed, including the following:
  - nx run @tanstack/react-query:test:lib

View structured, searchable error logs at https://nx.app/runs/yruFhd2Ecu
ELIFECYCLE  Command failed with exit code 1.
 </details

@alvarlagerlof is this happening because of the .then chain?
const initialPromise = Promise.resolve(promise).then(deserializeData)

Ideally, what we wanted to achieve is if the promise from the server fails, it would get retried on the client (since we pass it to the retryer). I'm wondering if adding a .catch(noop) here would stop those retries from happening ...

@alvarlagerlof is this happening because of the .then chain?

Yes the lack of .catch cause an unhandled promise rejection.

Ideally, what we wanted to achieve is if the promise from the server fails, it would get retried on the client (since we pass it to the retryer). I'm wondering if adding a .catch(noop) here would stop those retries from happening ...

I realised the same about the retries. I tried adding .catch(() => {}) that does ofc fix the unhandled promise, but as you suspected it breaks retries.
Test log

```
  ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯

   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
  TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:
          ["query_136"] data is undefined

          data:

  Ignored nodes: comments, script, style

            failure:
            ["query_136"] data is undefined

            data:

   ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
   ❯ src/__tests__/useQuery.test.tsx:6586:11
      6584|
      6585|     const rendered = renderWithClient(clientQueryClient, <Page />)
      6586|     await waitFor(() => rendered.getByText('failure: redacted'))
         |           ^
      6587|     await waitFor(() => rendered.getByText('data: client'))
      6588|     expect(count).toBe(1)

  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/4]⎯

   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
  TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:
          ["query_137"] data is undefined

          data:

  Ignored nodes: comments, script, style

            failure:
            ["query_137"] data is undefined

            data:

   ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
   ❯ src/__tests__/useQuery.test.tsx:6586:11
      6584|
      6585|     const rendered = renderWithClient(clientQueryClient, <Page />)
      6586|     await waitFor(() => rendered.getByText('failure: redacted'))
         |           ^
      6587|     await waitFor(() => rendered.getByText('data: client'))
      6588|     expect(count).toBe(1)

  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/4]⎯

   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
  TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:
          ["query_138"] data is undefined

          data:

  Ignored nodes: comments, script, style

            failure:
            ["query_138"] data is undefined

            data:

   ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
   ❯ src/__tests__/useQuery.test.tsx:6586:11
      6584|
      6585|     const rendered = renderWithClient(clientQueryClient, <Page />)
      6586|     await waitFor(() => rendered.getByText('failure: redacted'))
         |           ^
      6587|     await waitFor(() => rendered.getByText('data: client'))
      6588|     expect(count).toBe(1)

  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/4]⎯

   FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
  TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

  Ignored nodes: comments, script, style

          failure:
          ["query_139"] data is undefined

          data:

  Ignored nodes: comments, script, style

            failure:
            ["query_139"] data is undefined

            data:

   ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
   ❯ src/__tests__/useQuery.test.tsx:6586:11
      6584|
      6585|     const rendered = renderWithClient(clientQueryClient, <Page />)
      6586|     await waitFor(() => rendered.getByText('failure: redacted'))
         |           ^
      6587|     await waitFor(() => rendered.getByText('data: client'))
      6588|     expect(count).toBe(1)

  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/4]⎯

   Test Files  1 failed | 22 passed (23)
        Tests  1 failed | 360 passed (361)
  Type Errors  no errors
     Start at  12:22:17
     Duration  19.78s (transform 6.78s, setup 11.99s, collect 22.31s, tests 34.73s, environment 22.41s, prepare 6.71s, typecheck 18.40s)

   ELIFECYCLE  Command failed with exit code 1.

Not sure why it's "unhandled" then. The retryer does handle it 😅 - on the client

Not sure why it's "unhandled" then. The retryer does handle it 😅 - on the client

I just tried this:
      // Note: `Promise.resolve` required cause
      // RSC transformed promises are not thenable
      const initialPromise = Promise.resolve(promise).then(deserializeData)

      // this doesn't actually fetch - it just creates a retryer
      // which will re-use the passed `initialPromise`
      void query.fetch(undefined, { initialPromise }).catch(() => {
        /* noop */
      }

It also resolved the unhandled promise rejection. So maybe something in the fetch is actually where the issue lies.
But the added sleep seems to cause a test fail regardless:
Test log

       FAIL  |@tanstack/react-query| src/__tests__/useQuery.test.tsx > useQuery > should retry failed initialPromise on the client
      TestingLibraryElementError: Unable to find an element with the text: failure: redacted. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

      Ignored nodes: comments, script, style

              failure:

              data:
              client

      Ignored nodes: comments, script, style

                failure:

                data:
                client

       ❯ Proxy.waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@testing-library/dom/dist/wait-for.js:163:27
       ❯ src/__tests__/useQuery.test.tsx:6587:11
          6585|
          6586|     const rendered = renderWithClient(clientQueryClient, <Page />)
          6587|     await waitFor(() => rendered.getByText('failure: redacted'))
             |           ^
          6588|     await waitFor(() => rendered.getByText('data: client'))
          6589|     expect(count).toBe(1)

      ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/4]⎯

       Test Files  1 failed | 22 passed (23)
            Tests  1 failed | 360 passed (361)
      Type Errors  no errors
         Start at  14:23:31
         Duration  16.57s (transform 4.25s, setup 6.11s, collect 12.24s, tests 36.34s, environment 12.65s, prepare 3.76s, typecheck 10.56s)

       ELIFECYCLE  Command failed with exit code 1.


feat: Share util functions

This PR does 3 things:

Share util functions between builders
Ensure the files we create do not already exist (O_EXCL)
Add sanity checks when downloading an artifact for the non-existence of the file

I started looking into
https://github.com/slsa-framework/slsa-github-generator/blob/0f97cca414ee57448ec44667e92aa65c46a23eb6/internal/builders/go/main.go#L87
and https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/attest.go#L165
Then I realized that a malicious developer can use this function to sign any file present in the generator directory. The reason is that if the file already exists, this function does not return an error and continue silently. Fortunately we don't checkout the developer repository (by design), because it might have allowed the developer to set the path to a file they control.
I think an attacker could only have selected files with .intoto.jsonl extension, so just a few testcase files. I have not tested filenames like some-file\0(to remove the extension in https://github.com/slsa-framework/slsa-github-generator/blob/0f97cca414ee57448ec44667e92aa65c46a23eb6/internal/builders/go/main.go#L86), but I doubt it would work...
So I created the CreateNewFileUnderCurrentDirectory() function which uses O_EXCL and use it across the 2 existing builders.
Besides these changes, the rest is mostly re-factoring.

Thanks, I'll give this a review tomorrow

I'll wait for an ack from @ianlewis before merging.


Question about GetAssemblies

Hi. I really apologize for the off-topic question, but I'm just stuck and I'm starting to lose hope. My game has protection. For example: locking System.Reflection and AppDomain in il2cpp_class_from_name, empty methods(il2cpp_image_get_class, il2cpp_image_*, il2cpp_method_get_param_name, and etc.). I'm stuck on il2cpp_domain_get_assemblies. As you can see from ida the method just doesn't make sense

__int64 __fastcall il2cpp_domain_get_assemblies(__int64 a1, _QWORD *a2)
{
  __int64 result; // x0

  result = 0LL;
  *a2 = 0LL;
  return result;
}

But I found the GetAssemblies method in the AppDomain. Its pseudocode from ida:

System_Reflection_Assembly_array *System_AppDomain__GetAssemblies_66651848(
        System_AppDomain_o *this,
        const MethodInfo *method)
{
  return (System_Reflection_Assembly_array *)sub_200071C(this, 0LL);
}

__int64 sub_200071C()
{
  __int64 *v0; // x19
  __int64 v1; // x0
  __int64 *v2; // x22
  __int64 v3; // x20
  int v4; // w8
  __int64 v5; // t1
  int v6; // w24
  _QWORD *v7; // x21

  v0 = sub_DE1EC4();
  v1 = il2cpp_array_new_0(qword_45ED790, (v0[1] - *v0) >> 3);
  v2 = (__int64 *)*v0;
  v3 = v1;
  if ( *v0 != v0[1] )
  {
    v4 = 0;
    do
    {
      v5 = *v2++;
      v6 = v4 + 1;
      v7 = (_QWORD *)(v3 + 32 + 8LL * v4);
      *v7 = sub_DE3B70(v5);
      sub_DFBC2C(v7);
      v4 = v6;
    }
    while ( v2 != (__int64 *)v0[1] );
  }
  return v3;
}

For a test, I tried to hook it. My hook looks like this(I added System_Reflection_Assembly_o m_items[0] to struct Il2CppArray):
BNM::IL2CPP::Il2CppArray* hooked_getassemblies(BNM::IL2CPP::Il2CppAppDomain* domain, const MethodInfo* method) {
    auto domains = GetCurrentDomain();

    uintptr_t symbol_address = g_il2cppELF.findSymbol("il2cpp_assembly_get_image");
    using il2cpp_assembly_get_image_t = Il2CppImage*(*)(Il2CppAssembly*);
    il2cpp_assembly_get_image_t il2cpp_assembly_get_image = reinterpret_cast<il2cpp_assembly_get_image_t>(symbol_address);

    auto assemblies = original_getassemblies(domains, nullptr);

    auto& assembly_items = assemblies->m_Items;  // Referencing the items in the Il2CppArray
    auto assembly_count = assemblies->max_length;

    for (int i = 0; i < assembly_count; ++i) {
        auto& assembly = (Il2CppAssembly*)assembly_items[i];

        if (assembly) {
            Il2CppImage* image = il2cpp_assembly_get_image(assembly);
            if (image) {
                KITTY_LOGI("Retrieved image for assembly: %s", image->name);
            } else {
                KITTY_LOGE("Failed to retrieve image for assembly at index %d", i);
            }
        }
    }

    return assemblies;
}

But the logs just don't make sense. It just spams a bunch of “Retrieved image for assembly: .????x”
The count of assemblies is 128
Can I even use this function to retrieve assemblies? If so, I don't understand how I should modify the BNM code to make it work. Would it even be appropriate to use BNM in this game?

BNM can be used in any il2cpp game, when all methods and structs that used in game same as BNM's. Most helpful thing for you now is il2cpp's src code. That can be found in Unity itself and on Github.

So, i need to replicate those methods manually. Do i understood it correctly? I mean if AppDomain.GetAssemblies has Assembly::GetAllAssemblies() then i clearly can produce the same behavior as il2cpp_domain_get_assemblies, right?

Okay, i got it. Thank you for your help!


fix: profile specific plugins were not matched

fixes #3966

Thanks again! This will roll out to our snapshot versions soon, and you can try it out from there before the next release:
https://docs.openrewrite.org/reference/snapshot-instructions


check dropdown responsiveness in Windows

Just confirmed that dropdowns work as intended in Windows. This was probably related to the touch/mouse event issue with PCs that have both mouse input and a touch screen.


Amazon Authentication

Describe the bug
After entering email, password and captcha it asks me to verify with SMS or push to one of my ios devices.  I entered my phone number in the filed provided and it then displays a popup with a line that has required and submit.  No code came through and I can not get past this point.
To Reproduce
Steps to reproduce the behavior:

Go to 'Set up a new integration'
Click on 'Alexa Media Player'
Scroll down to 'Fill out email address and password for Amazon and complete captcha, then chose either sms of a push to ios devise, enter mobile number for SMS'
No code is sent

Expected behavior
A clear and concise description of what you expected to happen.
Should have received a code to complete Amazon authentication.
Screenshots
If applicable, add screenshots to help explain your problem.
https://www.dropbox.com/s/s63y0wu21mdq3hq/2020-04-15_21-49-43.png?dl=0
System details

Home-assistant (version):
System | HassOS 3.12
-- | --

Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).

alexa_media  (version from const.py or HA startup):

alexapy (version from pip show alexapy or HA startup):

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
Add any other context about the problem here.

Dupe of #568 . Workarounds and request for info there.


Fix for autogenerated etags - make them work even if input stream does not support mark/reset

For bug discussed in issue #1170
PR contains a fix for the bug, plus test (test is failing without the bugfix applied, and passed after applying the fix)

Nice catch, thank you @grzegorzbor !


Correctly access the vocab_size

Whenever I run:
import tensorflow.keras as keras
l = keras.layers.experimental.preprocessing.TextVectorization()
l.set_vocabulary(["hello", "world"])
l.get_vocabulary()

I get:

AttributeError: 'TextVectorization' object has no attribute 'vocab_size'

This PR fixes it.

Hi! Are there plans to merge this? This is currently breaking the get_vocabulary method of TextVectorization layers.


Module.zero_grad() does not work

Optimizer.zero_grad() works fine, but Module.zero_grad() doesn't seem to do anything. To reproduce this easily, modify the MNIST example's training loop as follows:
        model.zero_grad()   // this should zero out all the gradients, but it doesn't
        for (name, param) in model.named_parameters() do
            let grad = param.grad()
            let n =
                if isNull grad then 0L
                else torch.count_nonzero(grad).item<int64>()
            if n > 0 then
                printfn $"{name} gradient has {n} non-zero values"

Output:
Running MNIST on CUDA
Dataset: mnist
Epoch: 1...
conv1.weight gradient has 288 non-zero values
conv1.bias gradient has 32 non-zero values
conv2.weight gradient has 18419 non-zero values
conv2.bias gradient has 64 non-zero values
fc1.weight gradient has 1086148 non-zero values
fc1.bias gradient has 127 non-zero values
fc2.weight gradient has 1270 non-zero values
fc2.bias gradient has 10 non-zero values

This is curious -- I'll take a look

Okay, it was a simple fix... The Module.zero_grad() default implementation did not consider any submodules, only the top. Fortunately, a workaround is straight-forward, too.
Here's what the Module.zero_grad() implementation should look like:
public virtual void zero_grad()
{
    THSNN_Module_zero_grad(handle);
    CheckForErrors();

    foreach (var (_,m) in named_modules()) {
        m.zero_grad();
    }
}

and it will, in the next release.
The temporary workaround is to override zero_grad in any custom module and add the loop after a call to base.zero_grad(). If you're using Sequential, you may need to derive a class from it and add the override. For now.

Not so fast! The fix only works for modules composed entirely of submodules. Any module with its own parameters still fails.

The correct loop in Module.zero_grad() (and any workaround) is this:
foreach (var (_, p) in named_parameters()) {
    var grad = p.grad();
    if (grad is not null) {
        grad.zero_();
    }
}

Okay, the new fix also works for custom modules, as long as RegisterComponents() has been called (if it hasn't, then all kinds of unrelated trouble will also occur).


Reinitializing Scribble

Hey, I keep getting "SCRIBBLE_WARNING_REINITIALIZE" - I run scribble_init once in an object's Create event, it happens after game_restart() - should I just disable warning?

Ideally, you should not be using game_restart() at all. It is a function that can cause any number of problems throughout your game.
If you want to shoot yourself in the foot by continuing to use game_restart(), then you're welcome to turn set SCRIBBLE_WARNING_REINITIALIZE to false. Scribble should continue functioning appropriately, but I cannot guarantee that.


Extract out check_permissions() from `BaseView

I'm going to refactor this stuff out and document it so it can be easily used by plugins:

https://github.com/simonw/datasette/blob/4a4164b81191dec35e423486a208b05a9edc65e4/datasette/views/base.py#L69-L103
Originally posted by @simonw in https://github.com/simonw/datasette/issues/1660#issuecomment-1074136176

A slightly odd thing about these methods is that they either fail silently or they raise a Forbidden exception.
Maybe they should instead return True or False and the calling code could decide if it wants to raise the exception? That would make them more usable and a little less surprising.

Though at that point check_permission is such a light wrapper around self.ds.permission_allowed() that there's little point in it existing at all.
So maybe check_permisions() becomes ds.permissions_allowed().
permission_allowed() v.s. permissions_allowed() is a bit of a subtle naming difference, but I think it works.

The other difference though is that ds.permission_allowed(...) works against an actor, while check_permission() works against a request (though just to access request.actor).

One benefit of the current design of check_permissions that raises an exception is that the exception includes information on WHICH of the permission checks failed. Returning just True or False loses that information.

Idea: ds.permission_allowed() continues to just return True or False.
A new ds.ensure_permissions(...) method is added which raises a Forbidden exception if a check fails (hence the different name)`.

Also calling that function permissions_allowed() is confusing because there is a plugin hook with that name already: https://docs.datasette.io/en/stable/plugin_hooks.html#permission-allowed-datasette-actor-action-resource

Updated documentation: https://github.com/simonw/datasette/blob/e627510b760198ccedba9e5af47a771e847785c9/docs/internals.rst#await-ensure_permissionsactor-permissions

This method allows multiple permissions to be checked at onced. It raises a datasette.Forbidden exception if any of the checks are denied before one of them is explicitly granted.
This is useful when you need to check multiple permissions at once. For example, an actor should be able to view a table if either one of the following checks returns True or not a single one of them returns False:

That's pretty hard to understand! I'm going to open a separate issue to reconsider if this is a useful enough abstraction given how confusing it is.


gnuradioPackages.grnet: init for gr 3.8, 3.9

Motivation for this change
gr-grnet is a set of useful TCP and UDP blocks for GNU Radio.
In this PR I added grnet for GNU Radio 3.8 and 3.9. 3.7 isn't added because I failed to build dependencies python27Packages.{jinja2,flake8} for GNU Radio 3.7. I'll added the support for 3.7 once these dependencies will be fixed.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Also the commit history can be squashed into 1 commit.


COM-251: remove license types micro and subscription from admin

This PR removes the license types micro and subscription from the comet admin.
Acceptance Criteria

[x] Add changeset

How would this work for existing files, that have one of those both options selected? The label in the select wouldn't be shown anymore. Maybe it should be disabled instead, and require a new selection upon editing the file?

How would this work for existing files, that have one of those both options selected? The label in the select wouldn't be shown anymore. Maybe it should be disabled instead, and require a new selection upon editing the file?

Hmm it wouldn't throw an error and we have a migration in #1531 that replaces all license types with one of those two values with RIGHTS_MANAGED. I don't think it's worth putting in more work into that, since it has such a small usage and value. @thomasdax98 whats your opinion on that?

I just tried it: The select is empty and MUI shows a warning. Not ideal UX, but we can probably live with that.

Hmm it wouldn't throw an error and we have a migration in https://github.com/vivid-planet/comet/pull/1531 that replaces all license types with one of those two values with RIGHTS_MANAGED.

Please consider that a release of the next major version may take months 😅 Why don't remove the license types in main completely? To my information they aren't used for anything at the moment, so we could treat it as an internal change...

I just tried it: The select is empty and MUI shows a warning.

I just realized that I didn't think that through properly. I don't like that.
Now I concur with @johnnyomair. Let's close this PR and merge https://github.com/vivid-planet/comet/pull/1531 to main instead

I changed the target of #1531 to main and force pushed a new branch from main with the commits cherry picked.


docs(changelog) add clarification on OpenResty version bump

Fixes #6151
@jeremyjpj0916 please take a look, let me know if this is what you'd expect to find there!

@hishamhm LGTM!


support worker of juicefs can be update by runtime

Ⅰ. Describe what this PR does
support https://github.com/fluid-cloudnative/fluid/issues/3409
worker in runtime can update the following configs:

nodeSelector
networkMode
volumes & volumeMounts
labels & annotations
options
resources
envs

Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@zwwhdls please fix lint and build check. Thanks.


Use OpenTofu to have single .tfvars files for each environment, rather than nested modules

Intro
OpenTofu is a drop-in replacement for Terraform; just swap the terraform binary with tofu. There was a fork. Their feature sets are slowly diverging.
One of the latest features in OpenTofu is the ability to use variables in backend configurations. This allows us to significantly DRY up our infrastructure code. I don't expect Terraform to implement this feature any time soon: making it easier to use alternative backends conflicts with Hashicorp's business model.

Why bother switching?

Before
After

Usage
Install OpenTofu using your favorite version manager, navigate to the terraform/app directory, and then run:

aws sso login
tofu init -var-file=dev.tfvars
tofu plan -var-file=dev.tfvars

Discussion
This has fewer footguns than before. Now that backends are configured via .tfvars, if you run tofu init -var-file=dev.tfvars and then accidentally use production variables later (tofu plan -var-file=prd.tfvars), Tofu will warn you that your backend configuration has changed and refuse to proceed. 🙂
Now that we don't have .tfvars and .tfbackend files competing for autocompletion, typing commands is more ergonomic. tofu plan -var-file=d + Tab autocompletes to tofu plan -var-file=dev.tfvars. 🙂
When running tofu init with a different environment from what's configured on your local machine, Tofu still prompts users to choose between -migrate-state and -reconfigure. 😕
I haven't bothered replacing the word "Terraform" with "Tofu" in all the places, yet.
This module restructuring clobbers the existing state, but I don't really want to fill up the template with a bunch of moved blocks.

Supersedes #980

Looks like byu-oit/github-action-tf-plan-analyzer@v2 also explicitly runs terraform show, leading to our latest CI failure.

We're waiting on a mainline release of OpenTofu 1.8.0 before merging this, BTW.

It's been released! 🎉


added DotNet.ReproducibleBuilds

added DotNet.ReproducibleBuilds to fix #8

Very good stuff, thank you for your contribution! Would you like your name to be listed under the contributors?

just add my username from github

just add my username from github

Mia San Mia
Done

Included in release 6.1.1 :)


fix(popover): provide fallbackFocus

Overview

Popover: add fallbackFocus option to focus trap (this is to prevent a default error that will be thrown if the focus trap contains no elements in its tab order)

Note: we were seeing this error in the monolith once we updated the notification dropdown with show all/clear all functionalities. since the empty notification did not have any focusable element anymore, it throws an error. With this option you can specify a fallback element to programmatically receive focus if no other tabbable elements are found. See more here.
In the existing notifications list (that we will soon deprecate), the empty notifications text lives in a button (w/ no action). I presume this is to avoid that focus trap error.
code here:
& story
If you turn on voice over & test the story I added - when you hit enter on the popover, youll hear the content of the popover read
PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.b53867.0@codecademy/gamut@25.3.5-alpha.b53867.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6038225c820d246fe150e618--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.cbabe9.0@codecademy/gamut@25.3.5-alpha.cbabe9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60382c50bff61b0096e80ddd--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.1e17e5.0@codecademy/gamut@25.3.5-alpha.1e17e5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60383006604848007ead6561--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.60d1a0.0@codecademy/gamut@25.3.5-alpha.60d1a0.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.5b3988.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://603874d850b25b34bbb9e2fb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@10.2.2-alpha.0ac2b1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60398da9265811154b9466cb--gamut-preview.netlify.appDeploy Logs


Container Database

12c introduced multitenant which is available when started as a container DB. Is it possible to start this as a container db. If so, is it documented anywhere?

Well haven't gotten very far on this. To enable containerDatabase, add -createAsContainerDatabase true diff.
However, the database initialization usually fails. I increased shared memory to avoid one error, but it is still failing to startup.
docker run --shm-size=1024MB -p 8080:8080 -p 1521:1521 -v /tmp/oracle:/u01/app/oracle oracle-cdb

Hi @drewwells I'll take a look once I'll have a time for this
Cheers

Thanks @MaksymBilenko here's the output of trace: https://gist.github.com/drewwells/5d7c337e85d563b538fd

@drewwells Sorry, for now don't have time for this.
I'll keep this issue open and I'll take a look at this when I would have some time.
If you do need this functionality - you can play around database creation parameters and post here some suggestions and tweaks
Cheers


[feat] add [Portuguese] language in NSIS available language

Describe the problem

This language is available in the specified url. This is the tauri.conf.json
"windows": {
  "nsis": {
    "languages": ["French", "English", "Portuguese", "Spanish"]
  }
}

I only have the warning for Portuguese
Describe the solution you'd like
Add this language to the available list removing the warning
Alternatives considered
No response
Additional context
No response

we have PortugeseBR here, but we didn't get any PRs for Portugese, would you be willing to open a PR for it? it is a simple as translating this file https://github.com/tauri-apps/tauri/blob/dev/crates/tauri-bundler/src/bundle/windows/nsis/languages/English.nsh.

Thank you


Implement database integration test harness

This commit adds a utility script to stand up a postgres container so we
can run tests against it. It also adds skeleton integration test file
that establishes a connection to the database. Future patches will build
out the tests.

/retest

I'm unable to reproduce this locally, but the postgres container is failing to start:
 Health status: starting...
Health status: starting...
Health status: starting...
Failed to wait for pgsql container to come up
time="2022-06-16T21:30:38Z" level=error msg="Error removing timer for container cff81e19a4a652e7f3356bdda3daee27130beb66bc1b3fab356ec026e23095b6 healthcheck: unable to get systemd connection to remove healthchecks: dial unix /tmp/podman-run-1001/systemd/private: connect: no such file or directory"
postgres
time="2022-06-16T21:30:38Z" level=error msg="Error removing timer for container cff81e19a4a652e7f3356bdda3daee27130beb66bc1b3fab356ec026e23095b6 healthcheck: unable to get systemd connection to remove healthchecks: dial unix /tmp/podman-run-1001/systemd/private: connect: no such file or directory"
cff81e19a4a652e7f3356bdda3daee27130beb66bc1b3fab356ec026e23095b6
make: *** [Makefile:36: test-database-integration] Error 1


Use Web Inspector alongside Chrome Dev Tools

When having a debugging session opened and I open Dev Tools in Chrome, I get kicked out from debugging in Sublime. If I try to start a new debug session I can no longer choose localhost:8000 but instead it's been replaced by chromedevtools://.....
Is there any possibility of being able to both have Chrome Dev Tools opened and at the same time have a debug session opened in sublime?

Tentatively assigning to myself. There's no simple fix, but we're proposing a separate node server that would enable such multiplexing.


[WIP] staged_ledger: no hashing while validating txns

This pulls all of the logic for applying transactions and creating undos from Coda_base.Ledger and into Transaction_logic functor. We only use it in one new place: the Transaction_validator.  The Transaction_validator has no notion of undo and avoids all hashing.
This prevents a substantial amount of hashing when creating a diff.

Unfortunately not. The last use of Ledger.undo is in staged ledger, in snarked_ledger (which works by undoing the transactions that are still pending in the parallel scan state).


DSA section is added with some minor nav change

Description
The DSA section is added and the navbar has active underline while navigation
Fixes # (issue)
Added DSA section at app router
Test Required (Yes / No)
If Yes then How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Test A
[x] Test B

Test Configuration:

Platform: (Linux)
Architecture: (x86/x64/Arm/Amd)..
Version: 1.x.x

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is

https://github.com/user-attachments/assets/8e17eb96-c90c-473b-a2ee-5ab3eb9c6c15
effective or that my feature works

[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

New Features

Introduced a new page for browsing, searching, and viewing Rust data structures with code snippets and descriptions.
Added modal functionality to display and copy code snippets.
Integrated a new "DSA Examples" menu item in the mobile navigation.

Enhancements

Updated button text in the Books section from "See More Tools" to "See More Books."
Improved Navbar with active link management for better user navigation.

@FrancescoXX can you look it!

please remove the changes to the navbar, that would require a different issue (the project is very active and people are working on different things at the same time, included me, which is nice, but we need to coordiante)


"Type a slash (/) to change..." is misleading, misses huge opportunity

Describe the bug
The "Block" sidebar instructions to type a "/" to change block type mystified me until I read the discussion where the empty block instructions was proposed. I think it's essential to make the functionality discoverable this way, but the word "change" suggests (to me, and probably others) that it was supposed to be used in a block that already had a type, or that had content, both of which are exactly wrong.
I strongly suggest changing the instruction to indicate that this is to be done in a new empty block, and that it is to set the block type, not change it! I would combine this with information about using the "+" sign.
For instance:
To set the block type, click in a new empty block then:

Click on the "+" sign to select a block type, or
Type "/" and use the autocomplete menu to select a block type.

More context
I had been using Volto for several weeks, mystified by the "/" instructions and assuming it was just wrong until I stumbled on the discussion where the instructions were proposed. I am a big Notion user, where "/" is used in related but extended ways, so that may have been part of why I was misdirected. However, "change" is just wrong, and unnecessarily misleading, and the opportunity to provide guidance just where it's needed, in the empty block "Block" sidebar tab, should be used to maximum advantage.

@sneridagh and @tisto, this issue might make a significant difference for people's first impressions of Volto. Considering the imminent release of Plone 6, there might be an unusual large amount of people getting their first impression, so I thought I'd elevate attention to this small change in case it's seen to possibly make a positive difference for those first experiences.

@kenmanheimer You might want to try the experimental add button implementation that was added in #3815.
https://6.dev-docs.plone.org/volto/configuration/experimental.html
It doesn't change how the / key works, but it makes it so that you no longer have to add an empty block before you can see an add button.

@davisagli I think this ticket is about a small improvement (some help text) that would make a difference for those faced with "default Volto experience". As far as I'm concerned, this could be easily implemented, as the content of the sidebar for the text block was mostly a "placeholder" until we figure out exactly what we want there (I can say that, as I'm the initial author of that implementation)

Actually, changing the placeholder for the text block would be even better.
Also, for context: https://github.com/plone/volto/issues/3811#issuecomment-1296272500

This should also be written in the Editor docs. See issue https://github.com/plone/volto/issues/3827

Replying to my own question, it occurred to me that in the "build from packages" method I could include the experimental setting code in some of the package configuration code. I'll have to take a look at that.

@kenmanheimer You might want to try the experimental add button implementation that was added in #3815.
https://6.dev-docs.plone.org/volto/configuration/experimental.html

Yes, I heard about this in response to the first Volto issue that I posted, #3856 (comment) . I'm quite eager to give it a try, but have been slow to do so because I haven't yet implemented any Volto code artifacts. I may be missing something, but it seems like I would have to implement something like a trivial addon and include that in my build in order to change the experimental setting - is that right?

It doesn't change how the / key works, but it makes it so that you no longer have to add an empty block before you can see an add button.

Yep, it looks to me a more clear way to arrange the "+" functionality!

@kenmanheimer notion has "'/' for commands..." which is perhaps more general and inviting.
No harm in having better wording.
With regard to the the + to add, https://github.com/plone/volto/pull/3815,
I've been using this in production @davisagli and what I've found is that the most common thing you want to do is add a text block after something. If its after a text block then you will hit enter and all is good. but after a listing or something else you commonly click (+). The annoyance is that you keep having to type text or pick it to get the text block.
I'm wondering if it makes more sense for the + to insert a text block with the invitation to type "'/' for commands..."?

@davisagli I know this but it doesn't feel natural and it's not very discoverable. even though i know it works I still don't do it. Try making a bunch of pages

Regardless if you believe me that users won't discover and use this without training,
It still makes sense that the click based way of adding a block should optimise to insert a text block over other blocks as that is far more common. One click would be ideal.
Again, get new users to make a small site and see for yourselves.

Back to the issue of the slash as reported by @kenmanheimer, I consider myself a new user to Volto. I discovered / out of curiosity. I was editing a text block. Then I noticed the active tab Plone Site to the right, along with another tab Block. "What's this?" thinks me, so I clicked it, and discovered all the shortcuts that I never knew existed. That resulted in two issues https://github.com/plone/volto/issues/3811 and https://github.com/plone/volto/issues/3827.
To improve this, I would change the text block's placeholder attribute (as @tiberiuichim suggested as a fix) from Type text... to Type text, or set the block type with the "/" key, and choose the block type from the menu.. Unfortunately that is too verbose and won't fit on narrow screens. For brevity, and to make it fit, Type text, or set block type with "/" key.

Would that resolve this issue?

Regardless if you believe me that users won't discover and use this without training,
It still makes sense that the click based way of adding a block should optimise to insert a text block over other blocks as that is far more common. One click would be ideal.
Again, get new users to make a small site and see for yourselves.


Display defaultInput value to be edited

Thanks so much for the package! It's incredibly useful!
Is it possible to display the defaultInput to the user so that they can edit it as opposed to needing to type a brand new value?
For example:
readlineSync.question('Please edit value: ', {defaultInput: 'DEFAULT_VALUE'})

Please edit value: DEFAULT_VALUE

My use case is as follows:
Inputs have a maximum length. If value.length > max then I want to prompt the user to shorten the input without having to retype the entire value.

Hi @ecwyne, thank you for the proposal and your evaluation of readlineSync.
I understand that the feature may be useful for users who was inured to GUI. And I examined it before, but I didn't implement it.
Because it's not common CLI style (it may not be good about usability for CLI). And also, I think that implementing it is difficult.
See https://github.com/anseki/readline-sync/issues/16.
I think that CLI (i.e. the readline style) is unsuitable for input very long text. It might be good to reconsider the interface of your program.
For example, a input text that contains multiple somethings should be input separately as possible, such as first-name and last-name.
Or, re-input only a part of text, such as a byte of IP address.
Or, write the text that should be edited to clipboard, and the user can paste it to edit it. Node.js modules allow access to clipboard (e.g. node-copy-paste). But, I think that this may be not good idea because it makes the user confuse, and also, almost all terminals have "Copy" and "Paste" commands.
Or, you can use TUI library. Actually, the input style you requested is TUI.

No reply came, and I close this issue.


Update the support libs!

Sorry for my late reply.
support-v4 is a transitive dependency of recyclerview-v7.
If you want to update the version of support-v4 lib,
you can do it by configuring your build.gradle
to exclude recyclerview-v7 and add it again with your desired version:
dependencies {
    compile('com.github.ksoichiro:android-observablescrollview:1.6.0') {
        exclude module: 'recyclerview-v7'
    }
    compile 'com.android.support:recyclerview-v7:xxx'
    compile 'com.android.support:support-v4:xxx'
}

I'll close this issue but if you are talking about compatibility problem
(e.g. in newer version of support-v4, some APIs are removed and this lib uses them,
which causes app crashing), please reopen the issue and let me know details.


[0x7FFB70BF6740] ANOMALY: meaningless REX prefix used

C:\src\flutter\bin\flutter.bat --no-color packages get
[0x7FFB70BF6740] ANOMALY: meaningless REX prefix used

Hi @s3hengwu
Please check this  comment
Please create an issue against pub so they can take a look.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


support non-tile-multiple shard height (in progress)

@shwetankTT this is merged, right? close it?


Update contribution URL in README.md

Noticed the contribution URL in the README was referencing the older repository or based on gem instantiation

Thanks Zac!


Adjust card padding and icon size to be more consistent with other cards

Is your feature request related to a problem? Please describe.
When looking at this card inline with others. The look does not quite fit in with the current default HA cards and many others that adopt similar stylings.
Describe the solution you'd like
After experimentation, I propose the following modifications to the styles.ts file:

".content" - Adjust padding to "16px". This is equal to HA default card content padding and still seems to fit content fine.
".main-icon" - Adjust --mdc-con-size to "40px". This matches some other cards I've seen and looks better to me with the padding adjustment.
".main-icon" - Adjust height to "40px". See above.
".headline" - Remove margin-left. This results in the text centering better between the icon and the card border.
Unsure if caption icon size and margins should be reviewed. They don't seem to be in use with my configuration.

This is somewhat of a duplicate of #133. I'll close since that issue includes a suggested workaround that has been validated as working.


Fix contribtest

Why are these changes needed?

Related issue number
Closes #2453
Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 26.08696% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 38.65%. Comparing base (ded2d61) to head (caccbe0).

Files
Patch %
Lines

autogen/math_utils.py
35.71%
9 Missing :warning:

autogen/retrieve_utils.py
0.00%
6 Missing :warning:

...ntchat/contrib/qdrant_retrieve_user_proxy_agent.py
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2454      +/-   ##
==========================================
+ Coverage   33.33%   38.65%   +5.32%
==========================================
  Files          83       83
  Lines        8636     8637       +1
  Branches     1835     1980     +145
==========================================
+ Hits         2879     3339     +460
+ Misses       5516     5037     -479
- Partials      241      261      +20

Flag
Coverage Δ

unittest
12.56% <0.00%> (?)

unittests
38.23% <26.08%> (+4.89%)
:arrow_up:

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

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


Pci fixbug

Summary
1.pci.c: fix warning when CONFIG_PCI_ASSIGN_ALL_BUSES=n
2.pci.c: fix pci 32bit warning
3.toolchain/ghs: Fix ?? "trigraphs not allowed" warnings
4.pci_qemu_test.c: fix compiler warning
Impact
Testing

[Experimental Bot, please feedback here]
NuttX PR Requirements Review
This PR appears incomplete.  Here's a breakdown based on the provided information:
Summary:

Insufficient: While it lists files changed and hints at fixes, it lacks clear explanations of:

Necessity: Why are these warnings problematic? What issues did they cause?
Functionality: Which code parts are affected (beyond file names)?
Mechanism: How do the changes address the warnings?  Code examples would help.

Missing: Issue/PR references are absent. Were these changes prompted by existing reports?

Impact:

Entirely Missing:  This section is crucial.  The PR needs to address ALL impact points, even if the answer is "NO" with justification.

For example, a warning fix might seem like no user impact, but could subtly change build behavior if flags were modified.

Testing:

Insufficient:  Simply stating "changes are verified" is not enough.
Missing:

Specifics: What build hosts and targets were used?  Vague terms aren't helpful.
Logs:  "your testing logs here" is unhelpful placeholder text.  Provide ACTUAL logs demonstrating the issue before and the fix after.

Conclusion:
This PR needs significant work to meet NuttX standards.  Focus on clarity, completeness, and providing concrete evidence of both the problem and the solution.