Cannot import saved variables

Description
What steps will reproduce the problem?

Started Spyder
In the variable explorer window, I selected the import data button.
That is causing the error. The variables are not being imported and the submit error screen shows up.
I updated Spyder to the latest version (4.1.3). I tried restarting anaconda, as well as my PC. But the error persists.
This issue  is similar. The fix in this issue was upgrade to spyder 2.3.7. However, I am on a more recent version of spyder.
Traceback
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder/plugins/variableexplorer/widgets/namespacebrowser.py", line 207, in <lambda>
    triggered=lambda: self.import_data())
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder/plugins/variableexplorer/widgets/namespacebrowser.py", line 444, in import_data
    error_message = self.shellwidget.load_data(self.filename, ext)
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder/plugins/ipythonconsole/widgets/namespacebrowser.py", line 125, in load_data
    timeout=CALL_KERNEL_TIMEOUT).load_data(filename, ext)
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 542, in __call__
    call_dict, call_data, self._comm_id)
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder/plugins/ipythonconsole/comms/kernelcomm.py", line 114, in _get_call_return_value
    call_dict, call_data, comm_id)
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 420, in _get_call_return_value
    return self._sync_error(reply['value'])
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 480, in _sync_error
    error_wrapper.raise_error()
  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 90, in raise_error
    raise self.etype(self)
Exception in comms call load_data:

  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 342, in _handle_remote_call
    buffer['call_kwargs'])

  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 353, in _remote_callback
    *call_args, **call_kwargs)

  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/console/kernel.py", line 249, in load_data
    data, error_message = load_func(filename)

  File "/Users/jacob/anaconda/envs/py3/lib/python3.7/site-packages/spyder_kernels/utils/iofuncs.py", line 406, in load_dictionary
    data = pickle.loads(fdesc.read())

ModuleNotFoundError: No module named 'sklearn.preprocessing.imputation'

Versions

Spyder version: 4.0.1
Python version: 3.7.0
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Darwin 18.7.0

Dependencies
applaunchservices >=0.1.7    :  0.2.1 (OK)
atomicwrites >=1.2.0         :  1.3.0 (OK)
chardet >=2.0.0              :  3.0.4 (OK)
cloudpickle >=0.5.0          :  1.3.0 (OK)
diff_match_patch >=20181111  :  20181111 (OK)
intervaltree                 :  None (OK)
IPython >=4.0                :  7.13.0 (OK)
jedi =0.14.1                 :  0.14.1 (OK)
nbconvert >=4.0              :  5.6.1 (OK)
numpydoc >=0.6.0             :  0.9.2 (OK)
pexpect >=4.4.0              :  4.8.0 (OK)
pickleshare >=0.4            :  0.7.5 (OK)
psutil >=0.3                 :  5.7.0 (OK)
pygments >=2.0               :  2.6.1 (OK)
pylint >=0.25                :  2.4.4 (OK)
pyls >=0.31.2;<0.32.0        :  0.31.9 (OK)
zmq >=17                     :  18.1.1 (OK)
qdarkstyle >=2.7             :  2.8 (OK)
qtawesome >=0.5.7            :  0.7.0 (OK)
qtconsole >=4.6.0            :  4.7.1 (OK)
qtpy >=1.5.0                 :  1.9.0 (OK)
rtree >=0.8.3                :  0.9.3 (OK)
sphinx >=0.6.6               :  2.4.0 (OK)
spyder_kernels >=1.8.1;<2.0.0:  1.8.1 (OK)
watchdog                     :  None (OK)
cython >=0.21                :  0.29.15 (OK)
matplotlib >=2.0.0           :  3.1.0 (OK)
numpy >=1.7                  :  1.18.1 (OK)
pandas >=0.13.1              :  0.25.0 (OK)
scipy >=0.17.0               :  1.4.1 (OK)
sympy >=0.7.3                :  1.5.1 (OK)

@jac0bmath3w, this error is most probably due to you having saved your data with one Scikit-learn version and trying to open it with a different one or in a different Python installation.
So you have to be sure your two Scikit-learn versions (after saving the date and before loading it) are exactly the same, and using the same package manager (i.e. conda or pip). Otherwise, your data won't be loaded correctly.

Thank you for your reply.
I believe I had saved all the variables before exiting, but I understand
why this error might have happened.
In the meanwhile, I had re-imported all data from scratch. But I will keep
this in mind for the future.
Thank you.
On Sat, Jun 27, 2020 at 12:11 PM Carlos Cordoba<EMAIL_ADDRESS>wrote:

@jac0bmath3w https://github.com/jac0bmath3w, this error is most
probably due to you having saved your data with one Scikit-learn version
and trying to open it with a different one or in a different Python
installation.
So you have to be sure your two Scikit-learn versions (after saving the
date and before loading it) are exactly the same, and using the same
package manager (i.e. conda or pip). Otherwise, your data won't be loaded
correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/13120#issuecomment-650587397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADBFKDP4OAIPUOSCZRMRY6TRYYR5RANCNFSM4OJZPN6Q
.

--
Regards,
Jacob Mathew,
Grad Student in Civil Engineering
University of Illinois at Urbana Champaign

Closing because this is quite old now. Hopefully you managed to solve this problem.


Opening files in a project does not insert them into the recent files list

Version and Platform (required):

Binary Ninja Version: 3.6.4819-dev
OS: macOS
OS Version: 14.1
CPU Architecture: arm64

Bug Description:
Files opened in project browser should be inserted into the ui/recentFiles list.
Steps To Reproduce:

Open file in project
Hit new tab button.

Added in 4.0.4827-dev


CB-13817 Add new alias uwp for --appx param including tests

https://issues.apache.org/jira/browse/CB-13817
What does this PR do?
Adds uwp as an alias for uap to the --appx param so one can also use it to trigger a Win10 build.
What testing has been done on this change?
Locally + CI.
Checklist

[x] Reported an issue in the JIRA database
[x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[x] Added automated test coverage as appropriate for this change.

Test failures are identical to current master.


Support for 3D Tiles

Hi! We're using geo-three for interactive maps.
Now that Google has opened up the 3D Tiles API (https://cloud.google.com/blog/products/maps-platform/create-immersive-3d-map-experiences-photorealistic-3d-tiles?hl=en), I was wondering if you're planning to add support for that API?
That would be awesome! Thanks

Hello
Thanks a lot for the suggestion.
Yes this is something that im considering to work on for the library.
Thanks a lot!


Ensure tx meta is v2 when getting ledgers with protocol version <10

As explained by @MonsieurNicolas in #1902:

There is some missing meta in protocol version older than version 10. This impacts transactions with one time signers (that get removed after operations in v9 and earlier; and during signature verification in v10 and later). Those changes are invisible in the meta which may confuse certain ingestion processors that keep track of signers on accounts.

It's possible that users will use stellar-core without SUPPORTED_META_VERSION=2 and in such case ingestion system can process meta incorrectly. I think we should check the protocol version of the ledger in DatabaseBackend.GetLedger and if it's <10 it should check if txmeta version is equal 2. Otherwise it should return error.

Fixed in #2099.


How to convert simple string to LaTeX string programmatically ?

if we try TextMobject(" \# \{ \} ")
it works fine.
but if we try following code TextMobject(" # { } ")
it will result into following error
File "manimlib\utils\tex_file_writing.py", line 67, in tex_to_dvi
    "See log output above or the log file: %s" % log_file)
Exception: Latex error converting to dvi. See log output above or the log file: ./media\Tex\c2fe0a3b9407ff29.log

is there any way to convert simple string " # { } " to LaTex string " \# \{ \} " ?
something like print(StringToLaTexString(" # { } "))
Output should be \# \{ \}
So that we can use something like TextMobject(StringToLaTexString(" # { } ")) to avoid error.

i created following function
def latex_escape(str):
    # Replace a \ with $\backslash$
    # This is made more complicated because the dollars will be escaped
    # by the subsequent replacement. Easiest to add \backslash
    # now and then add the dollars
    # Must be done after escape of \ since this command adds latex escapes
    # Replace characters that can be escaped
    # Replace ^ characters with \^{} so that $^F works okay
    # Replace tilde (~) with \texttt{\~{}} # Replace tilde (~) with \texttt{\~{}}
    list = ["\\", "^", "~", '&', '%', '$', '#', '_', '{', '}']
    change_to = ["$\\backslash$", "\\^{}", "\\texttt{\\~{}}", '\\&', '\\%', '\\$', '\\#', '\\_', '\\{', '\\}']

    for i in list:
        if i in str:
            str = str.replace(i, change_to[list.index(i)])
            break
    return str

and remember that you can't create a single curly brackets '{' or '}' in LaTeX
means you can't create TextMobject(" \{") or TextMobject(" \}")  or TextMobject(" \{aaa")
so you can try following methods
https://github.com/3b1b/manim/issues/941#issuecomment-620319805


Question about your words: "ES2015 is the latest standard of ECMAScript"

Hi, in your doc you said the ES2015 is the latest, hasn't the latest ES7 passed and standared?? according to Brian Terlson and the http://www.ecma-international.org/ecma-262/7.0/index.html.
And I found that you have finished the babel-preset-es2016, isn't it??
So why don't put the link of babel-preset-es2016 to the home page so that visitor could use es 2016 conveniently??

Yeah its just not updated that's all. Also the es2016 preset only includes es2016 specific transforms. I merged https://github.com/babel/babel.github.io/pull/878 which should help


chore(main): release 1.11.19

:robot: I have created a release beep boop
1.11.19 (2023-07-20)
Bug Fixes

slack message when restaurant is closed (a7e7bdf)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/devoteam-se/devolunch/releases/tag/v1.11.19 :sunflower:


Staticman no longer allows comments

Environment

Minimal Mistakes version: 4.16.3
Ruby gem or remote theme version: n/a
Jekyll version: n/a
Git repository URL: justinrummel/jr.com-mm
GitHub Pages hosted (if yes provide URL to site): No
Operating system: n/a

Expected behavior
Currently not able to post comments.
Steps to reproduce the behavior
It appears that Staticman is enforcing CORS, and current MM sites that use Staticman can no longer post comments.  Confirmed this is also impacting your own site.

Have you filed an issue on Staticman's repo to track?

Working on the research now, posting mostly for awareness....

Curious to see what changed on Staticman's end of anything. Looking at the repo dev branch was last updated 4 months ago and master 2 months.
Wonder if where they host changed something? Guess this is another reason to host your own instance vs. using the public Staticman endpoint.

Confirmed solution at github.com/eduardoboucas/staticman/issues/278#issuecomment-475170669.  Need to update from dev.staticman.net to api.staticman.net for v3.
I've tried to figure out how to host my own instance several times and failed every single time.  If you figure it out and document, I'd be happy to verify the directions.

Nice. Was wondering when the dev instance would stop working.
Thanks for digging into it.

Wonder if this line needs to be updated for v3
https://github.com/mmistakes/minimal-mistakes/blob/102924ff940d5b7f03493bb70aedcbad2d99286f/_includes/comments.html#L38

Shouldn't need to change. The endpoint for v3 is set in the config. Just need to switch from dev to api there.

@justinrummel Not sure if you experienced this one yet, but the dreaded "Too many requests" error is happening again once switching to api.staticman.net v3 instead of using dev.staticman.net.
Looks like even with using a GitHub application there's still some sort of API limit Staticman is hitting and comments don't go through.
There's this issue if you want to track any developments https://github.com/eduardoboucas/staticman/issues/279

Curious if you're going to make staticman v3 a first-class citizen or not? Right now in the _config.yml it only calls out staticman and staticman_v2:
comments:
  provider               : # false (default), "disqus", "discourse", "facebook", "staticman", "staticman_v2", "utterances", "custom"

I just found issue #2036 and left a comment on it to see if we could get it reopened regarding adding staticman v3 support.

@deadlydog I don't have any plans to change how Staticman is enabled in the theme. With all it's issues the last year I'm not really motivated to until it stabilizes.
Even the new v3 GitHub application endpoint is having it's issues. Calling it out as an official comment solution for the theme has only brought more attention to it and put me in a support role for when it goes bad.

Having the link you provided in #2036 does effectively show how to use staticman v3 with minimal configuration changes, and is just what I was looking for 👍

@deadlydog I don't have any plans to change how Staticman is enabled in the theme. With all it's issues the last year I'm not really motivated to until it stabilizes.
Even the new v3 GitHub application endpoint is having it's issues. Calling it out as an official comment solution for the theme has only brought more attention to it and put me in a support role for when it goes bad.

Under Staticman v3, no matter how the Node.JS code inside the app changes, I don't think the URL scheme (i.e. input) and the rendered output YML file structure would change.  Provided that this theme's integration works well with a self-hosted Staticman v3 instance, nothing much can be done by a static blog theme, apart from offering advices in documentations/README.
Btw, I suggest using an alternative/self-hosted Staticman API instance to avoid unexpected interruption of static comments service due to unnotified update on the main public production/testing Staticman API instance, say in https://github.com/eduardoboucas/staticman/issues/283.  You might refer to my post for self-hosting Staticman if interested.
P.S. I wrote the linked docs for Staticman v3, and I built @staticmanlab.

@deadlydog I don't have any plans to change how Staticman is enabled in the theme. With all it's issues the last year I'm not really motivated to until it stabilizes.
Even the new v3 GitHub application endpoint is having it's issues. Calling it out as an official comment solution for the theme has only brought more attention to it and put me in a support role for when it goes bad.

Glad to know I read this before using Staticman on my own site.

Thanks @VincentTam
I'll take a look at your blog post again and try to follow the directions.  If there are spots that I feel are unclear I'll reach out to you.

Seems like the best approach these days is to fork  the Staticman repo and spin up your own instance on a free Heroku plan.
Closing as there’s nothing the theme can do about improving the reliability of the public endpoint.

Seems like the best approach these days is to fork the Staticman repo and spin up your own instance on a free Heroku plan.

Staticman's maintainer has recommended users to set up their own API instance: https://github.com/eduardoboucas/staticman/issues/317#issuecomment-565250060


Index out of range when calling the positional encoder

Thank you for the awesome paper and for sharing the code.
I tried running ./scripts/train.sh on both the Lorenz dataset (./data/lfads_lorenz.h5) and the autonomous chaotic RNN dataset (generated via the script) but I get this error for both:
    return torch.embedding(weight, input, padding_idx, scale_grad_by_freq, sparse)
IndexError: index out of range in self

which is called by this line:
neural-data-transformers/src/model.py", line 294, in forward
    src = self.pos_encoder(src)

I used Python 3.6.10 and Pytorch 1.5.0
Do you happen to know what is causing this error? Thank you.

It seems like the spike count you are embedding is too large for the embedding layer. I'm not sure why it's failing on these datasets, but you should see that src.max() > max_spikes + 2 ( set ~ line 174). Could you let me know if this is the case, and make sure what's being fed into the model is in range(0, max_spikes)?

Just wanted to mention that I was not able to replicate this error. Steps I took:
Fresh conda environment via conda env create -f environment.yml
Activated the new environment via conda activate pytorch
Fresh clone of repository
Made a copy of configs/arxiv/lorenz.yaml to configs/my_config.yaml
Edited the CHECKPOINT_DIR specification (first line)
I didn't need to do this, but one would also want to edit the DATAPATH specification
./scripts/train.sh my_config
Then trained for a few hundred epochs with no issues.
So more details would probably be required to address this.

Thank you both!
I rerun with a fresh environment and a fresh clone of the repository just in case, but still got the same error. I think the issue might be in the data file I am using?
I followed the same steps except that I replaced DATAPATH, TRAIN_FILENAME and TEST_FILENAME to use the provided lfads_lorenz.h5 file. This is how the config file was changed:
CHECKPOINT_DIR: "runs/"
DATA:
  DATAPATH: "/data"
  TRAIN_FILENAME: 'lfads_lorenz.h5'
  VAL_FILENAME: 'lfads_lorenz.h5'

max_spikes is equal to 23
I added these lines in src/model.py after line 292:
    def forward(self, src, mask_labels, **kwargs):
        print('input src.max', src.max())
        src = src.permute(1, 0, 2) # t x b x n
        src = self.embedder(src) * self.scale
        print('embedder output src.max', src.max())
        src = self.pos_encoder(src)

And this is what I get:
input src.max 17
embedder output src.max tensor(0.7336, grad_fn=<MaxBackward1>)

I used a docker image on a different machine, so this should be independent from any of my setups:
docker run --rm -ti continuumio/anaconda3 /bin/bash

Here I install some requirements, clone the repo and create the conda env
apt-get update
apt-get install gcc python3-dev vim

# install git lfs
curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash
apt-get install git-lfs
git lfs install

cd home/
git lfs clone https://github.com/snel-repo/neural-data-transformers.git
cd neural-data-transformers/
conda env create -f environment.yml
export PYTHONPATH=.

Then I modify the lorenz configuration file as follows:
CHECKPOINT_DIR: "runs/"
DATA:
  DATAPATH: "/data"
  TRAIN_FILENAME: 'lfads_lorenz.h5'
  VAL_FILENAME: 'lfads_lorenz.h5'

and run the training
vim configs/arxiv/lorenz.yaml
./scripts/train.sh arxiv/lorenz

I also try generating the autonomous chaotic RNN data (the generate_chaotic_rnn_data.py file required some changes because the tensorflow version in environment.yml does not work, so I changed import tensorflow as tf to import tensorflow.compat.v1 as tf and also also converted ndatasets to an int in line 133). Then I am able to generate the data
cd data/
vim chaotic_rnn/gen_synth_data_no_inputs.sh
vim chaotic_rnn/generate_chaotic_rnn_data.py
./chaotic_rnn/gen_synth_data_no_inputs.sh
cd ..

Again, I modify the configuration file to this:
CHECKPOINT_DIR: "runs/"
DATA:
  DATAPATH: "data/chaotic_rnn/data_no_inputs/"
  TRAIN_FILENAME: 'chaotic_rnn_no_inputs_dataset_N50_S50'
  VAL_FILENAME: 'chaotic_rnn_no_inputs_dataset_N50_S50'

And run
vim configs/arxiv/chaotic.yaml
./scripts/train.sh arxiv/chaotic

And I get the same error:
(pytorch) root@2f8792cf3485:/home/neural-data-transformers# ./scripts/train.sh arxiv/chaotic
logs/chaotic exists
removing logs/chaotic
2021-04-21 17:12:16,250 Using cpu
2021-04-21 17:12:16,250 Loading chaotic_rnn_no_inputs_dataset_N50_S50 in train
/home/neural-data-transformers/src/dataset.py:47: UserWarning: To copy construct from a tensor, it is recommended to use sourceTensor.clone().detach() or sourceTensor.clone().detach().requires_grad_(True), rather than torch.tensor(sourceTensor).
  rates = torch.tensor(rates)
2021-04-21 17:12:16,380 Clipping all spikes to 9.
2021-04-21 17:12:16,380 Training on 1040 samples.
2021-04-21 17:12:16,380 Loading chaotic_rnn_no_inputs_dataset_N50_S50 in val
2021-04-21 17:12:16,496 number of trainable parameters: 415040
Traceback (most recent call last):
  File "src/run.py", line 144, in <module>
    main()
  File "src/run.py", line 58, in main
    run_exp(**vars(args))
  File "src/run.py", line 137, in run_exp
    runner.train()
  File "/home/neural-data-transformers/src/runner.py", line 335, in train
    metrics = self.train_epoch()
  File "/home/neural-data-transformers/src/runner.py", line 390, in train_epoch
    return_outputs=False,
  File "/opt/conda/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 550, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/neural-data-transformers/src/model.py", line 294, in forward
    src = self.pos_encoder(src)
  File "/opt/conda/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 550, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/neural-data-transformers/src/model.py", line 355, in forward
    x = x + self.pos_embedding(self.pe) # t x 1 x d
  File "/opt/conda/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py", line 550, in __call__
    result = self.forward(*input, **kwargs)
  File "/opt/conda/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/sparse.py", line 114, in forward
    self.norm_type, self.scale_grad_by_freq, self.sparse)
  File "/opt/conda/envs/pytorch/lib/python3.6/site-packages/torch/nn/functional.py", line 1724, in embedding
    return torch.embedding(weight, input, padding_idx, scale_grad_by_freq, sparse)
IndexError: index out of range in self

Is there maybe a mismatch between the data files I am using and the configuration files?

Thank you for all this helpful info @mazabou . Could you check if your data/lfads_lorenz.h5 file is a binary file, or text?
If the latter, this is likely an issue with git lfs not being installed - we can add the relevant instructions now, but at a high-level,
the conda environment needs git-lfs
inside the git repo you need to do git lfs install and git lfs pull
Once I did that I was able to train a network based on the data/lfads_lorenz.h5 file. Could you check this out and get back to us?

Actually, I apologize. I see in your more detailed second set of that you did install git lfs

Hm, I apologize as I misread the initial issue. Could you set _C.MODEL.POSITION.OFFSET = False? I think as is, the model embeds [1:T], but we might want [0:T-1].

Yes this was it, it works after setting _C.MODEL.POSITION.OFFSET = False.
Thank you both for your help!!


Update _config.yml

Resolves #ISSUE_NUMBER

Before the change?

After the change?

Pull request checklist

[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been reviewed and added/updated if needed (for bug fixes/features)

Does this introduce a breaking change?

[ ] Yes
[x] No

Summary by Sourcery
Chores:

Update the Jekyll theme and remove the logo.

Description by Korbit AI
What change is being made?
Change the Jekyll theme from "minimal" to "cayman" and remove the logo property in the _config.yml file.
Why are these changes being made?
The update to the "cayman" theme offers a more suitable visual style for the project, enhancing aesthetics and possibly readability. The removal of the outdated logo property reflects a decision to not rely on external images which could be unavailable or irrelevant.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Summary by CodeRabbit

New Features

Updated website theme to a new design for improved aesthetics.

Bug Fixes

Removed logo specification, which may resolve display issues related to logo rendering.

:white_check_mark: Build POC-dotnet-Dijkstra 1.1.387 completed (commit https://github.com/GuilhermeStracini/POC-dotnet-Dijkstra/commit/3148c1cab6 by @gstraccini[bot])


Lambda variable highlighted as red (nonexistent)

It is no longer colored as red but entirely uncolored now. On the other hand, variables get a purple coloring when it is not used as the command. Interesting.

The reason for the aforementioned phenomena is caused by edit.writer not joining styles correctly, which has been fixed in 69dca19b68757ac092af38deccdf1cfe2b8e4660. Now they are red again.


feat: design data structure holding WebR output

This would need to be something capable of interfacing with OpenStreetMap (OSM). Needs to store both the index values that OSM should map and parameters, e.g. color, style for the map

Addressed. WebR will output a GeoJSON. One of the features of the GeoJSON will be an "index" column. This column contains the index that the WebR script has recalculated.


Handle indexes with too many compound keys

FerretDB version
v1.3.0
It is not possible to create a compound index with more than 32 fields in MongoDB. We should return the correct error when the index spec violates this constraint.
Backend
PostgreSQL
Environment

OS: Ubuntu 22.10 x86_64
Deployment: v1.3.0
Deployment details: 23.0.3

What did you do?
See #2818
What did you expect to see?
        "ok" : 0,
        "errmsg" : "Index build failed: 66726630-53d7-4179-8a13-184f7225bc48: Collection test.compound_index_max_fields ( 7f2ba2c5-0cb9-4540-92af-ef60a9f16fd2 ) :: caused by :: index build on empty collection failed: 66726630-53d7-4179-8a13-184f7225bc48 :: caused by :: too many compound keys",
        "code" : 13103,
        "codeName" : "Location13103"

What did you see instead?
        compound_index_max_fields
        assert: command did not fail with any of the following codes [ 13103 ] {
                "ok" : 0,
                "errmsg" : "[msg_createindexes.go:126 pg.(*Handler).MsgCreateIndexes] [transactions.go:137 pgdb.(*Pool).InTransactionRetry] non-retriable error: [transactions.go:91 pgdb.(*Pool).InTransaction] [indexes.go:222 pgdb.createPgIndexIfNotExists] ERROR: cannot use more than 32 columns in an index (SQLSTATE 54011)",

Nice catch!


penalize duplicates

The idea behind this patch is primarily to save upload bandwidth by sending fewer nodes back to duplicate requests from IPs. It only affects nodes that actually make it into the ping_queue, but any request from an IP that's in the queue receives 3 nodes, instead of the configured number (16 by default).
My experience is that at least a 1/3rd of all incoming requests fall into this category.

lgtm


Compile warnings for SIGALIGN when FLEN is 64 in arch_test.h

New arch_test.h, pulled on Jan 3rd, now doubly defines SIGALIGN when FLEN is 64. This generates very verbose compile warnings.
Please remove it from the == 64 clause, since the FLEN > XLEN check fully resolves the issue.
#if FLEN==64
#define FLREG fld
#define FSREG fsd
#define FREGWIDTH 8
#define SIGALIGN 8
#else
#if FLEN==32
#define FLREG flw
#define FSREG fsw
#define FREGWIDTH 4
#endif
#endif
#if FLEN>XLEN
#define SIGALIGN FREGWIDTH
#else
#define SIGALIGN REGWIDTH
#endif

This should be fixed by #277

Looks like this doubling has been cleaned up in the latest repo. Thanks!


classification report

Hello,
2 problems in classification report.
with titanic dataset and logistic regression like this :
from verticapy.learn.linear_model import LogisticRegression
drop(schema + ".rl_titanic", cursor = cur, method = "model")
model = LogisticRegression(name = schema + ".rl_titanic",
                   penalty = 'None',
                   tol = 1e-4,
                   C = 1.0,
                   max_iter = 100,
                   solver = 'Newton',
                   l1_ratio = 0.5)
model.fit(titanic_copy, ["fare", "age"], "survived")
model.predict(titanic_copy, ["fare", "age"], "survived_pred")
titanic_copy.eval("survived_pred2", "case when survived_pred <= 0.5 then 0 when survived_pred > 0.5 then 1 end")
titanic_copy = titanic_copy.sort({"col_id" : "asc"})

classification report result is :

the problems are f1_score and cutoff.
With this code in python :
#calcul du f1 score et cutoff en py
import sklearn as sk
df_titanic = titanic_copy.to_pandas()
df_titanic = df_titanic.loc[(df_titanic["fare"].notna()) & (df_titanic["age"].notna())]
py_class_report = pd.DataFrame([[0] for i in range(2)],
            index = [ "f1_score", "cutoff"],
            columns = ["value"])

py_class_report.loc["f1_score"] = np.round(sk.metrics.f1_score(df_titanic["survived"], df_titanic["survived_pred2"]),10)

fpr, tpr, thresholds = sk.metrics.roc_curve(df_titanic["survived"], df_titanic["survived_pred"])
optimal_idx = np.argmax(tpr - fpr)
py_class_report.loc["cutoff"] = thresholds[optimal_idx]

I have :

for f1_score, with the code :
from verticapy.learn.metrics import f1_score
f1_score("survived", "survived_pred2", titanic_copy)

I have the same result that python. In classification report, you inverse tnr and ppv in the formula.
for cutoff, in verticapy, you use :
from verticapy.learn.model_selection import roc_curve
roc_curve("survived", "survived_pred2", titanic_copy, nbins = 30, best_threshold = True)

that return 0.9666667. But with :
roc_curve("survived", "survived_pred", titanic_copy, nbins = 1000, best_threshold = True)
we have 0.36, like python.
We must increase the parameter bins to have the good result, but we can't change this parameter in classification report function.
Regards
Alexandre

Thanks a lot Alexandre,
It will be corrected in the next PR.


Tflite Micro Hello-world continuously restart on ESP32-S3

@tensorflow/micro
System information
Host OS Platform and Distribution (e.g., Linux Ubuntu): Ubuntu 18.04
TensorFlow installed from (source or binary): source
Tensorflow version (commit SHA if source): 2.3.0
Target platform (e.g. Arm Mbed OS, Arduino Nano 33 etc.): ESP32-S3
Describe the problem
I am trying to setup the ESP32-S3 for TFlite.
I have compiled TFLite hello-world for ESP32-S3. The compilation got successful but when I flash the image on ESP32-S3, it continuously restarted the board.
Please let me know how can i build and flash TFLite hello-world for ESP32-S3.
Please provide the exact sequence of commands/steps when you ran into the problem
Clone the tensorflow repository:
git clone https://github.com/tensorflow/tensorflow.git -b r2.3
Generate the examples The example project can be generated with the following command:
make -f tensorflow/lite/micro/tools/make/Makefile TARGET=esp generate_hello_world_esp_project
Building the example Go the the example project directory:
cd tensorflow/lite/micro/tools/make/gen/esp_xtensa-esp32/prj/hello_world/esp-idf
Set the target:
idf.py set-target esp32s3
Then build with idf.py:
idf.py build
Flashing an image:
idf.py --port /dev/ttyACM0 flash monitor
But the image when flashed does not work. It keeps restarting.
Any suggestions for this issue?
cyclic_reboot_ESP32S3.pdf

Something similar happened with me. I was burning the esp32 firmware and the device went busy after the firmware was uploaded I could not save the hello world file, due to "device busy" message popping up. Any leads for this?

Hi @priyanshu-makhiyaviya is this a solved problem? You have a similar issue raised on espressif's tflite-micro-esp-examples repo and it seems to resolved for you.
If the problem is still seen, please share the logs for the same.

Hi @vikramdattu ,
I was trying with both repo , tensorfloe/tflite-micro and tflite-micro-esp-examples
The issue raised on espressif's tflite-micro-esp-examples repo got resolved.
This is the issue with the tensorfloe/tflite-micro repo. The log is already attached.
But anyway I got a working example with the tflite-micro-esp-examples and currently not focusing on tensorfloe/tflite-micro
Thank you.

Marking the issue as resolved since, it is no more a problem for you.


initial fastlane structures

In preparation of your potential listing with F-Droid.org – but also for your (now) existing listing in my repo: using these (standard) structures, you can maintain your app's metadata yourself in one place, and feed them all (also works for Play Store). Please expand by e.g. moving your screenshots in. My Fastlane Cheat Sheet might be helpful as guide.
The format I've used for full_description.txt is what I call "Markdown lite" and proved the best compromise for all 3 places (i.e. it works fine with all 3 of them). Find a few hints on that in my wiki.

Thanks! If you want to add a new badge to your Readme, here is mine – and this would be the link target :smiley:

Thanks! If you want to add a new badge to your Readme, here is mine – and this would be the link target :smiley:

PS: Should you add screenshots and/or per-release changelogs, please let me know so I can enable them on my end.

PS: Should you add screenshots and/or per-release changelogs, please let me know so I can enable them on my end.

Thank you so much for the PR! I pushed the phone screenshots to fastlane according to the specs. It would be much appreciated if the screenshots were enabled and synched to your repo.
I do have a question. Will the screenshots be updated for each release or will it update itself each time the fastlane directory in this repo is changed?

Thank you so much for the PR! I pushed the phone screenshots to fastlane according to the specs. It would be much appreciated if the screenshots were enabled and synched to your repo.
I do have a question. Will the screenshots be updated for each release or will it update itself each time the fastlane directory in this repo is changed?

It would be much appreciated if the screenshots were enabled and synched to your repo.

Just synced them manually and enabled them for future updates.

Will the screenshots be updated for each release or will it update itself each time the fastlane directory in this repo is changed?

Whenever a new release is fetched, fastlane is checked on files "newer than" what's already here. For screenshots, that also includes purging here what's no longer there – but only if new screenshot(s) were found.
Thanks for adding the download button! :green_heart:

It would be much appreciated if the screenshots were enabled and synched to your repo.

Just synced them manually and enabled them for future updates.

Will the screenshots be updated for each release or will it update itself each time the fastlane directory in this repo is changed?

Whenever a new release is fetched, fastlane is checked on files "newer than" what's already here. For screenshots, that also includes purging here what's no longer there – but only if new screenshot(s) were found.
Thanks for adding the download button! :green_heart:

Thank YOU ❤

Thank YOU ❤


Japanese pages: nav items in header different

Original:

Hlx:

Assigning it to @hparwani2

nav-tree.json wasn't published. it's replicated now.


add test cases for footer, App, sourcesView components. Update readme

What Does this PR do?

Add More tests to test the App, sources-view, and Footer components.
Update README

Coverage decreased (-19.5%) to 46.711% when pulling 34017e0bab473fe892fd7c17d7ccf2f0d1f2873c on add-more-test into 5c786064cc19c55f961e0eec83b045359d9972a8 on develop.


Rustup for retagging

Matches rust-lang/rust#55316
Also make our use of -Z flags more consistent.

The retagging PR is in nightly now.


Created archive.py

Since Swas loves to archive channels very too often, here's an archive command which will archive the channel.
(Can be used only by admins, and has a seperate command for setting the archive category)

Alright i will do that soon

Alright done, havent tested it but should work


YAXAttributeForClass attribute is ignored when a YAXCustomSerializer is defined on the property's type

A simple type is defined like this:
<YAXCustomSerializer(GetType(MyCustomSerializer))>
Public Class MyType

   Private _foo As String
   ...

End Class

The custom serializer MyCustomSerializer simply serializes MyType as its _foo string in all cases.
Let's define the following class "Sample", which holds a property of type 'MyType'.
Public Class Sample
        <YAXAttributeForClass>
        <YAXSerializeAs("attr")>
        Public Property Prop As MyType
End Class

If we try to serialize Sample, then the property 'Prop' is always serialized as an inner element, and not as an attribute, as specified by YAXAttributeForClass ...
The problem can be worked around by specifying the custom serializer on the property instead of the property type.
Public Class Sample
        <YAXAttributeForClass>
        <YAXCustomSerializer(GetType(MyCustomSerializer))>
        <YAXSerializeAs("attr")>
        Public Property Prop As MyType
End Class

Then YAXAttributeForClass is honoured correctly.
This looks like a bug in YAXLib to me, but I might be wrong! What do you think ?

The behavior of YAXLib corresponds to the issue description, including the workaround found.
Also, the SimpleTypeSerializer is discovered for Sample.Prop, but not the SerializeAs attribute.
The workaround covers custom serialization for ICustomSerializer.SerializeToElement and ICustomSerializer.SerializeToAttribute, but not for ICustomSerializer.SerializeToValue.
@NKnusperer I would consider this a missing piece of implementation. Your opinion?
Source to reproduce the issue:
YAXLib_Issue_97.zip

@axunonb I would considers this as a missing edge case too. No reason why this shouldn't work.


Upgrade to django 1.8

We should upgrade to the latest version of django if we can.

Dealt with in #108


seems no need to use std::pair

seems no need to use std::pair to group keys and values where keys are potentially duplicated.

i think pair is needed. keys[i] stores the key for values[i]. if you sorted the keys into temp_keys, temp_keys[i] is no longer the key for the values[i].
i'm going to close the pr, please feel free to reopen it.


MyEnergi Integration Zappi Wallbox 2.1.etc.

Zappi 2.1 provides a good 22kw Wallbox with many PV Charging Options on Board. However, I can't Inegrate DC Sensors because of missing Space and it has no connection to Cars. So EVCC could be powerful combination.
Myenergi also is a hub to connect heating, batteries, etc. So in combination with evcc and car connection it could the most powerful solution on the market.
Describe the solution you'd like
Integrationof the Zappi v.2.1 Wallbox and if you like of the other Ecosystem Parts, too. But the wallbox most important, because since the wallbox would be integrated, it could manage the other possible connections in wireless slave mode alone.
Describe alternatives you've considered
I also tried it with the Solution "Clever-PV" but their OCPP is beta and doesn't work. Also everything "smart" like pv Charging would need subscription...
The included Cablesensors do not fit in my Zählerkasten / Meterbox.
Additional context
MyEnergi has many connection features and comes with an similar looking dashboard and system, so it would be an impressive combination. Please consider to integrate it.🙏🏻
https://www.myenergi.com/de/zappi/

I also tried it with the Solution "Clever-PV" but their OCPP is beta and doesn't work.

What's missing if the Box supports OCPP?

Cross ref: https://github.com/evcc-io/evcc/issues/461

It rarely stops and starts but doesn't seem to control the power level according to pv levels.
So it seems that the ocpp on both sides, but mainly the "clever-pv" ocpp has issues.
Zappi has api and ocpp options so it would have many more options together with evcc if you can add. (Thank you for your product in general!)

Von: andig @.>
Gesendet: Dienstag, Juli 30, 2024 8:24:35 AM
An: evcc-io/evcc @.>
Cc: Stevin13 @.>; Author @.>
Betreff: Re: [evcc-io/evcc] MyEnergi Integration Zappi Wallbox 2.1.etc. (Issue #15141)
I also tried it with the Solution "Clever-PV" but their OCPP is beta and doesn't work.
What's missing if the Box supports OCPP?
—
Reply to this email directly, view it on GitHubhttps://github.com/evcc-io/evcc/issues/15141#issuecomment-2257560659, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKGDPPRQ66ZUOOTPEKZXFALZO4WSBAVCNFSM6AAAAABLVBIGEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGU3DANRVHE.
You are receiving this because you authored the thread.Message ID: @.***>

Repeating the question: did you try ocpp with evcc?


Exception when invalid date

Given a reform class with a date input, eg:
class SomeForm < Reform::Form
  property :starts_on, type: Date
end

When a user submits an invalid date (eg 31 Sept), an exception is raised when reform parses the date params. The exception is simply "invalid date" (ie no exception class). I think it's raised by Date.
Here's the relevant backtrace:
reform (1.0.1) lib/reform/form/multi_parameter_attributes.rb:30:in `new'
reform (1.0.1) lib/reform/form/multi_parameter_attributes.rb:30:in `params_to_date'

@zubin any update? I'm going to close this as Multi-parameter attribute handling has moved to reform-rails.
If this is still not working as expected can you create a new issue there?


tools-2661 change module path to github.com/aerospike/asconfig

The purpose of these changes is to make getting sub packages of asconfig easier.
like go get http://github.com/aerospike/asconfig/asconf .


WIP - GRANT - eligibility fixes and status flow

Summary:

update status flow to only allow Admins to proceed past Workshop status
automate ASSIGNED status when application is assigned to a user

Safety:

[x] lint;
[x] test;
[x] prettier;

I addressed some of these comments in here: https://github.com/bcgov/BCAT/pull/74
please take a look


Check IP Services - Plugin

Needs Check IP Services - plugin support
https://github.com/opnsense/core/pull/3002

checkip.dyndns.com is blocked in China. need this plugin enhancement to replace it.


[BUG] Failed to connect to GCS.

Bug Report Checklist

[ ] I provided code that demonstrates a minimal reproducible example.
[ ] I confirmed bug exists on the latest mainline of AutoGluon via source install.
[x] I confirmed bug exists on the latest stable version of AutoGluon.

Describe the bug
Getting the below error.
ERROR utils.py:1395 -- Failed to connect to GCS. Please check gcs_server.outfor more details.
Previously, I was able to run the same code without this error.
Now, ray stop solves the issue.
 GCS may have been killed. It's either GCS is terminated by ray stop or is killed unexpectedly. If it is killed unexpectedly, see the log file gcs_server.out. https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure. The program will terminate.
more details:
Fitting model: CatBoost_r70_BAG_L1 ... Training model for up to 29656.42s of the 29656.41s of remaining time.         Fitting 8 child models (S1F1 - S1F8) | Fitting with ParallelLocalFoldFittingStrategy (8 workers, per: cpus=2, gpus=0, memory=0.01%)         Warning: Exception caused CatBoost_r70_BAG_L1 to fail during training... Skipping this model.                 System error: Broken pipe Detailed Traceback: Traceback (most recent call last):   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/trainer/abstract_trainer.py", line 1817, in _train_and_save     model = self._train_single(X, y, model, X_val, y_val, total_resources=total_resources, **model_fit_kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/trainer/abstract_trainer.py", line 1763, in _train_single     model = model.fit(X=X, y=y, X_val=X_val, y_val=y_val, total_resources=total_resources, **model_fit_kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/abstract/abstract_model.py", line 854, in fit     out = self._fit(**kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/stacker_ensemble_model.py", line 165, in _fit     return super()._fit(X=X, y=y, time_limit=time_limit, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/bagged_ensemble_model.py", line 273, in _fit     self._fit_folds(   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/bagged_ensemble_model.py", line 689, in _fit_folds     fold_fitting_strategy.after_all_folds_scheduled()   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/fold_fitting_strategy.py", line 649, in after_all_folds_scheduled     X, y, X_pseudo, y_pseudo = self._prepare_data()   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/fold_fitting_strategy.py", line 814, in _prepare_data     X = self.ray.put(self.X)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/auto_init_hook.py", line 24, in auto_init_wrapper     return fn(*args, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/client_mode_hook.py", line 103, in wrapper     return func(*args, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/worker.py", line 2597, in put     object_ref = worker.put_object(value, owner_address=serialize_owner_address)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/worker.py", line 704, in put_object     self.core_worker.put_serialized_object_and_increment_local_ref(   File "python/ray/_raylet.pyx", line 2939, in ray._raylet.CoreWorker.put_serialized_object_and_increment_local_ref   File "python/ray/_raylet.pyx", line 2831, in ray._raylet.CoreWorker._create_put_buffer   File "python/ray/_raylet.pyx", line 412, in ray._raylet.check_status ray.exceptions.RaySystemError: System error: Broken pipe Fitting model: LightGBM_r196_BAG_L1 ... Training model for up to 29655.89s of the 29655.87s of remaining time.         Fitting 8 child models (S1F1 - S1F8) | Fitting with ParallelLocalFoldFittingStrategy (8 workers, per: cpus=2, gpus=0, memory=0.01%)         Warning: Exception caused LightGBM_r196_BAG_L1 to fail during training... Skipping this model.                 System error: Broken pipe Detailed Traceback: Traceback (most recent call last):   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/trainer/abstract_trainer.py", line 1817, in _train_and_save     model = self._train_single(X, y, model, X_val, y_val, total_resources=total_resources, **model_fit_kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/trainer/abstract_trainer.py", line 1763, in _train_single     model = model.fit(X=X, y=y, X_val=X_val, y_val=y_val, total_resources=total_resources, **model_fit_kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/abstract/abstract_model.py", line 854, in fit     out = self._fit(**kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/stacker_ensemble_model.py", line 165, in _fit     return super()._fit(X=X, y=y, time_limit=time_limit, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/bagged_ensemble_model.py", line 273, in _fit     self._fit_folds(   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/bagged_ensemble_model.py", line 689, in _fit_folds     fold_fitting_strategy.after_all_folds_scheduled()   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/fold_fitting_strategy.py", line 649, in after_all_folds_scheduled     X, y, X_pseudo, y_pseudo = self._prepare_data()   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/autogluon/core/models/ensemble/fold_fitting_strategy.py", line 814, in _prepare_data     X = self.ray.put(self.X)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/auto_init_hook.py", line 24, in auto_init_wrapper     return fn(*args, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/client_mode_hook.py", line 103, in wrapper     return func(*args, **kwargs)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/worker.py", line 2597, in put     object_ref = worker.put_object(value, owner_address=serialize_owner_address)   File "/home/cizind/anaconda3/envs/autogluon/lib/python3.9/site-packages/ray/_private/worker.py", line 704, in put_object     self.core_worker.put_serialized_object_and_increment_local_ref(   File "python/ray/_raylet.pyx", line 2939, in ray._raylet.CoreWorker.put_serialized_object_and_increment_local_ref   File "python/ray/_raylet.pyx", line 2831, in ray._raylet.CoreWorker._create_put_buffer   File "python/ray/_raylet.pyx", line 412, in ray._raylet.check_status

@namelessperson0 Can you please provide example code that reproduces this issue?


Improve TypeScript support for media templates

Typing media templates can be cumbersome. I've spent a fair amount of time to figure out the following type declarations and casts compliant with TypeScript's strict mode:
import { ThemedCssFunction } from 'styled-components';
import { css } from './styled-components';
import ThemeInterface from './theme';

const sizes = {
  small: 600,
  medium: 1024,
  large: 1440,
  xlarge: 1920,
};

// Iterate through the sizes and create a media template
export const media = (Object.keys(sizes) as (keyof typeof sizes)[]).reduce(
  (acc, label) => {
    acc[label] = (first: any, ...interpolations: any[]) => css`
      @media (min-width: ${sizes[label]}px) {
        ${css(first, ...interpolations)}
      }
    `;

    return acc;
  },
  {} as { [key in keyof typeof sizes]: ThemedCssFunction<ThemeInterface> },
);

One of the possible solutions is writing docs including the aforementioned code snippet. An other way to get around the issue and lower the amount of boilerplate code required even for vanilla JS projects is to create a method which encapsulates the functionality above:
import { mediaTemplates } from 'styled-components';

const media = mediaTemplates({
  small: 600,
  medium: 1024,
  large: 1440,
  xlarge: 1920,
});

@kripod does the trick still work for you? After upgrading from<EMAIL_ADDRESS>to 4.1.1...4.1.8 component props seem to no longer work inside media queries. Investigating.

I also noticed this @kachkaev.
Styled Components version 4.1.2, using Typescript 3.1.1.
In the following component:
const Foo = styled.div`
  ${media.md`
    flex-shrink: 0;
    flex-basis: ${(props: CellProps) =>
      props.width ? `${props.width}px` : 'auto'};
    flex-grow: ${(props: CellProps) => props.grow};
  `};

with the mediaquery function noted in the docs at (https://www.styled-components.com/docs/advanced#media-templates)[https://www.styled-components.com/docs/advanced#media-templates],
I am noticing that only flex-basis is being applied. flex-grow does not appear on the component. It seems all props in the mediaquery function are applied, until the first dynamic prop. All other props after that (dynamic or otherwise) are not being set.

Imho writing media templates as template functions is not a good idea, because linting, syntax highlighting and auto completion won‘t work with its content css.
It is way eqsier and imho better to just create strings with the @media definitions:
const phone = „@media (max-width: 480px)“

const MyComponent = styled.div`
    background: palevioletred;
    ${phone} {
        background: dodgerblue;
    }
`

The media definitions could also read from the theme, this would work similarly.

If there's anything else to be done here, feel free to open an issue over at DefinitelyTyped.

Many thanks for your suggestion @fabb! I refactored my media templates as you suggest and all typescript issues were gone, plus I got better autoformatting by Prettier in a couple of places 🎉
Wondering if docs could be to change to this:
const customMediaQuery = (maxWidth: number) =>
  `@media (max-width: ${maxWidth}px)`;

const media = {
  custom: customMediaQuery,
  desktop: customMediaQuery(922),
  tablet: customMediaQuery(768),
  phone: customMediaQuery(576)
};

const Content = styled.div`
  height: 3em;
  width: 3em;
  background: papayawhip;

  /* Now we have our methods on media and can use them instead of raw queries */
  ${media.desktop} {
    background: dodgerblue;
  }
  ${media.tablet} {
    background: mediumseagreen;
  }
  ${media.phone} {
    background: palevioletred;
  }
`;

render(<Content />);

Looks much simpler and easier to read
100% understood by Prettier
Perfectly works in TS with no added magic
Is probably a bit faster because additional calls to css`...` are removed 🎉

@probablyup do you think this would make sense? I can submit a PR if that's potentially interesting.

Cheers!

@fabb @kachkaev This syntax is so simpler. Thank you! I've started to migrate to this syntax and the code feels much more readable and prettier has a good time formatting it.
That being said, be careful when coupling this with conditionals.
// The old way looks and works as expected.
const ComponentWithConditional = div`
  ${props => props.isResponsive && media.medium`
    display: block
  `}
`

// The new way looks correct but isn't.
// We are only interpolating the string literal.
// So when `!isResponsive` we get an "orphan" `display: block` which we didn't expect.
const ComponentWithConditional = div`
  ${props => props.isResponsive && media.medium} {
    display: block
  }
`

// The correct way. We don't get autocompletion with this but it is an acceptable
// trade-off if you don't have many conditions coupled with your breakpoints.
const ComponentWithConditional = div`
  ${props => props.isResponsive && `${media.medium} { display: block }`}
`

After the fact, it seems like a silly mistake to make, but it took me a while to see it. I hope it will save someone from the frustration.

@nayaabkhan I usually do it like this:
const ComponentWithConditional = div`
  ${media.medium} {
    display: ${p => p.isResponsive ? "block" : "inherit"};
  }
`

Of course this can become convoluted when defining several css properties.

import { css, CSSObject, SimpleInterpolation, FlattenSimpleInterpolation } from 'styled-components'

type Breakpoints = {
  xs: number
  sm: number
  md: number
  lg: number
  xl: number
  xxl: number
}

const sizes: Breakpoints = {
  xs: 480,
  sm: 576,
  md: 768,
  lg: 992,
  xl: 1200,
  xxl: 1600,
}

const initAcc: Interpolation<Breakpoints> = {
  xs: () => '',
  sm: () => '',
  md: () => '',
  lg: () => '',
  xl: () => '',
  xxl: () => '',
}

type BreakpointEntry = [keyof Breakpoints, Breakpoints[keyof Breakpoints]]
type Interpolation<T> = {
  [key in keyof T]:
    | ((
        first: CSSObject | TemplateStringsArray,
        ...interpolations: SimpleInterpolation[]
      ) => FlattenSimpleInterpolation)
    | (() => string)
}

interface CustomObject extends ObjectConstructor {
  entries<K extends keyof Breakpoints, T>(o: { [s in K]: T } | ArrayLike<T>): [K, T][]
}

const object: CustomObject = Object

export const media = object.entries(sizes).reduce<Interpolation<Breakpoints>>((acc, cur: BreakpointEntry) => {
  const [key, value] = cur
  acc[key] = (first, ...interpolations) =>
    css`
      @media (max-width: ${value}px) {
        ${css(first, ...interpolations)}
      }
    `

  return acc
}, initAcc)

@kachkaev  Thanks so much!

import { css, CSSObject, SimpleInterpolation, FlattenSimpleInterpolation } from 'styled-components'

type Breakpoints = {
  xs: number
  sm: number
  md: number
  lg: number
  xl: number
  xxl: number
}

const sizes: Breakpoints = {
  xs: 480,
  sm: 576,
  md: 768,
  lg: 992,
  xl: 1200,
  xxl: 1600,
}

const initAcc: Interpolation<Breakpoints> = {
  xs: () => '',
  sm: () => '',
  md: () => '',
  lg: () => '',
  xl: () => '',
  xxl: () => '',
}

type BreakpointEntry = [keyof Breakpoints, Breakpoints[keyof Breakpoints]]
type Interpolation<T> = {
  [key in keyof T]:
    | ((
        first: CSSObject | TemplateStringsArray,
        ...interpolations: SimpleInterpolation[]
      ) => FlattenSimpleInterpolation)
    | (() => string)
}

interface CustomObject extends ObjectConstructor {
  entries<K extends keyof Breakpoints, T>(o: { [s in K]: T } | ArrayLike<T>): [K, T][]
}

const object: CustomObject = Object

export const media = object.entries(sizes).reduce<Interpolation<Breakpoints>>((acc, cur: BreakpointEntry) => {
  const [key, value] = cur
  acc[key] = (first, ...interpolations) =>
    css`
      @media (max-width: ${value}px) {
        ${css(first, ...interpolations)}
      }
    `

  return acc
}, initAcc)

For some reason your implementation doesn't seem to work for me.
const ResponsiveBox = styled.div`
  color: white;
  height: 100px;
  width: 500px;
  ${media.lg} {
    width: 300px;
    background-color: green;
  }
  ${media.md} {
    width: 200px;
    background-color: red;
  }
  ${media.sm} {
    width: 400px;
    background-color: blue;
  }
`;


[REEF-824] Use diamond operator for generic instance creation

This PR replaces old-style generic instance creation with diamond operator
to improve code readability.
JIRA:
REEF-824
Pull Request:
This closes #

Looks good, I'll test and merge
I'm curious as for what tool you used to detect these warnings en masse, and whether there is a way to enforce this syntax over old style one? A quick search finds a custom Checkstyle check  DiamondOperatorForVariableDefinitionCheck (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/src/main/java/com/github/sevntu/checkstyle/checks/coding/DiamondOperatorForVariableDefinitionCheck.java)

Thank you. That's a great idea, and sevntu-checkstyle looks great. For this issue, I used my eyes with IntelliJ.


Fix flaky unit test

Closes: #1199

What changed?
Changed the interval time for pollAuthStatus. Sometimes it was checking the call count before making a call.

Why?

How did you test it?

Release notes

Documentation Changes

@jpellizzari good question. I couldnt replicate the issue after many runs when making this change. So I cannot tell you if it is fully fixed or less likely. I do know that I can make it fail 100% of the time by tweaking that number to 6. I believe it is fully fixed with this change.

What about this issue @J-Thompson12 ?: https://github.com/benbjohnson/clock/issues/8
It has been fixed in a newer release than the one we currently have...

good question. I couldnt replicate the issue after many runs when making this change.

I think the underlying problem here, at least for me, is that it’s tricky to understand the sequence of events that the test is looking for, and where the race condition came from in the first place. I think the flaky test is coming from the fact that we’re setting the mock clock to the exact time that we’d expect a retry, but it’s hard to be confident of that from the code itself. I can think of a few possible ways to address this:

More explanation in the test code, to make the relationships between values clearer. For instance, if we had interval set to 4 seconds, we could increment the current time by interval + time.Second, to make it clear that we want to be sure the interval has passed, and similarly .
A few more comments alongside the code, to make the intention clearer.
More context in the commit message. This has the benefit of not having to worry about space constraints (potentially even going full-on ASCII art timeline), but it’s further away from the code. I put a lot of stock in commit messages, but I don’t know yet how much they’re a part of the company culture here.

What do you think, @J-Thompson12? Do we have an opportunity here to make the intent of the code clearer, while also fixing a flaky test?

@jpellizzari good catch. I didnt even see that was turned off.


Fix signed/unsigned char warning (fixes #604)

@ggardet can you see if this builds with -Werror on the platforms you mentioned? Looking through the code, this is the only place I can see where there is an assumption of signed char. If this fixes it, great. If not, I will go to the trouble of reproducing it and testing it properly. Thanks!

I'm not guillaume but I can confirm this PR fixes the warning on aarch64. thank you!

That indeed fixes the issue. Thanks!


Support fetching exact MPP resolutions

This PR supports fetching exact micron-per-pixel (MPP) resolutions from the WSI using large_image as an optional dependency. The rationale here is that different WSIs have different encodings for the internal levels and different scan resolutions. large_image handles this by parsing the internal metadata for a wide range of formats beyond those supported by openslide and interpolating between levels when needed to fetch exact MPP resolutions independent of the slide format, scan resolution, manufacturer etc.
If the user doesn't have large_image installed but asks for an mpp resolution, they are prompted to install it.
@alessiamarcolini @ernestoarbitrio @nicolebussola This is the key feature from the forked version. I added tests for (hopefully) everything, but they are skipped if large_image is not installed. So if you'd like all the tests to run to maintain coverage, I suggest adding the large_image installation to test environment.

Description

Types of Changes

[x] Core
[ ] Bugfix
[x] New feature
[x] Enhancement/optimization
[ ] Documentation

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Ok I ran out of time. I'll take another look once these comments are addressed

@ernestoarbitrio Thanks, all addressed.


Rename repository?

For improved organizational clarity this repo should probably phyloref/phyloref-ontology or phyloref/ontology, rather than phyloref/phyloref (which is a result of moving over the early proof-of-concept from hlapp/phyloref).

Renamed now to phyloref-ontology.


xwayland: 23.2.1 -> 23.2.2

Changes: https://lists.x.org/archives/xorg/2023-October/061514.html
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 263305 run on x86_64-linux 1

2 packages marked as broken and skipped:

gnomeExtensions.easyScreenCast
xmonad_log_applet

9 packages failed to build:

houdini
mir
mir.dev
mir.doc
miriway
python310Packages.qtile-extras
python310Packages.qtile-extras.dist
python311Packages.qtile-extras
python311Packages.qtile-extras.dist

167 packages built:

adapta-gtk-theme
bottles
bottles-unwrapped
breath-theme
cage
cagebreak
cinnamon.cinnamon-gsettings-overrides
dwl
dwl.man
gamescope
gamescope.lib
gnome-browser-connector
gnome.gdm
gnome.gdm.debug
gnome.gdm.dev
gnome.gnome-applets
gnome.gnome-control-center
gnome.gnome-control-center.debug
gnome.gnome-flashback
gnome.gnome-initial-setup
gnome.gnome-panel
gnome.gnome-panel-with-modules
gnome.gnome-panel.dev
gnome.gnome-panel.man
gnome.gnome-session
gnome.gnome-session.debug
gnome.gnome-session.sessions
gnome.gnome-shell
gnome.gnome-shell.debug
gnome.gnome-shell.devdoc
gnome.gnome-terminal
gnome.gnome-tweaks
gnome.gpaste
gnome.mutter
gnome.mutter.debug
gnome.mutter.dev
gnome.mutter.devdoc
gnome.mutter.man
gnome.mutter43
gnome.mutter43.debug
gnome.mutter43.dev
gnome.mutter43.devdoc
gnome.mutter43.man
gnome.nixos-gsettings-overrides
gnomeExtensions.gsconnect
gnomeExtensions.gsconnect.installedTests
gnomeExtensions.system-monitor
grimblast
hikari
hyprland
hyprland.dev
hyprland.man
hyprpicker
kde-rounded-corners
labwc
labwc.man
latte-dock
libsForQt5.applet-window-appmenu
libsForQt5.bismuth
libsForQt5.kde-cli-tools
libsForQt5.kdeplasma-addons
libsForQt5.kdev-php
libsForQt5.kdev-python
libsForQt5.kdevelop
libsForQt5.kdevelop-unwrapped
libsForQt5.khotkeys
libsForQt5.khotkeys.bin
libsForQt5.khotkeys.dev
libsForQt5.kinfocenter
libsForQt5.kmenuedit
libsForQt5.krohnkite
libsForQt5.kwin
libsForQt5.kwin-dynamic-workspaces
libsForQt5.kwin-tiling
libsForQt5.kwin.dev
libsForQt5.kzones
libsForQt5.parachute
libsForQt5.plasma-bigscreen
libsForQt5.plasma-browser-integration
libsForQt5.plasma-desktop
libsForQt5.plasma-disks
libsForQt5.plasma-disks.bin
libsForQt5.plasma-disks.dev
libsForQt5.plasma-mobile
libsForQt5.plasma-remotecontrollers
libsForQt5.plasma-workspace
libsForQt5.plasma-workspace.dev
libsForQt5.powerdevil
libsForQt5.systemsettings
libsForQt5.systemsettings.bin
libsForQt5.systemsettings.dev
libsForQt5.xdg-desktop-portal-kde
lightly-boehs
lightly-qt
mojave-gtk-theme
monitor
mpvpaper
nordic
nwg-panel
nwg-panel.dist
pantheon.elementary-greeter
pantheon.elementary-gsettings-schemas
pantheon.elementary-session-settings
pantheon.gala
pantheon.switchboard-plug-a11y
pantheon.switchboard-plug-bluetooth
pantheon.switchboard-plug-mouse-touchpad
pantheon.switchboard-plug-pantheon-shell
pantheon.switchboard-plug-power
pantheon.switchboard-plug-security-privacy
pantheon.switchboard-with-plugs
pantheon.wingpanel
pantheon.wingpanel-applications-menu
pantheon.wingpanel-indicator-a11y
pantheon.wingpanel-indicator-bluetooth
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-indicator-keyboard
pantheon.wingpanel-indicator-network
pantheon.wingpanel-indicator-nightlight
pantheon.wingpanel-indicator-notifications
pantheon.wingpanel-indicator-power
pantheon.wingpanel-indicator-session
pantheon.wingpanel-indicator-sound
pantheon.wingpanel-with-indicators
phoc
phosh
phosh-mobile-settings
python310Packages.pywlroots
python310Packages.pywlroots.dist
python310Packages.qtile
python310Packages.qtile.dist
python311Packages.pywlroots
python311Packages.pywlroots.dist
python311Packages.qtile
python311Packages.qtile.dist
qt-video-wlr
qtile
river
river.man
rivercarro
sierra-breeze-enhanced
sway
sway-contrib.grimshot
sway-contrib.grimshot.man
sway-unwrapped
swayfx
tinywl
vimix-gtk-themes
wacomtablet
waybar
waybox
wayfire
wayfire-with-plugins
wayfirePlugins.wayfire-plugins-extra
wayfirePlugins.wcm
wayfirePlugins.wf-shell
weston
whitesur-gtk-theme
wingpanel-indicator-ayatana
wl-gammactl
wlprop
wlroots (wlroots_0_16)
wlroots.examples (wlroots_0_16.examples)
wlroots_0_15
wlroots_0_15.examples
xdg-desktop-portal-hyprland
xwayland

Flagging as security-relevant because of CVE-2023-5367, CVE-2023-5380 & CVE-2023-5574.
Not sure if it's reasonable to apply the patches themselves or whether to just go to 23.2 on 23.05 which seems to be affected as well.

cc @NixOS/security

For 23.05 it would mean larger bump of 23.1.2 -> 23.2.2.  (I haven't looked at the span of changes, though.)


FindHWLOC.cmake: fix syntax error

@junghans can you change this pull request to point at master instead of stable?

@chuckatkins please let me know if you have any concerns about this

Nice, github implemented that feature just in time:
https://github.com/blog/2224-change-the-base-branch-of-a-pull-request

Ping @chuckatkins

@streichler: we should add a test case to the ci running cmake -DLegion_USE_HWLOC=ON.

+1

@streichler : I think this can be merged!


[Fix]: Made GitHub buttons mobile responsive

This fixes issue #46
Made the GitHub buttons in header to be mobile responsive.

Hi @vinitshahdeo , as today is the last day for hacktoberfest, can you please review and merge if it's fine?

Hey @mani-rsg
I fixed this yesterday as I had the launch planned on Product hunt.
Please take a look: https://www.producthunt.com/posts/topmate-io-readme-badge-generator

Hey @vinitshahdeo ok no problem. BTW, Congrats on your launch


pipelines.cpp uses wide lines feature without enabling it

Pipelines.cpp doesn't enable the wide lines feature, nor does it add line width to the dynamic state enables.  Adding the dynamic state flag causes the line width to work, but I still get validation errors because during device creation wide lines was not enabled.
This is a tricky fix because it requires a PhysicalDeviceFeatures pointer to be passed into the DeviceCreateInfo structure during the call to vkCreateDevice, but this call happens in the constructor for the base class, so the individual example classes can't modify the input parameters.  It's may not be desirable to pass in the results of vkGetPhysicalDeviceFeatures as enabling all the available features whether you plan to use them or not might impact performance.
I've made a change locally by adding an additional optional VkPhysicalDeviceFeatures parameter to VulkanExampleBase in which I can pass a statically statically initialized structure that has wide lines enabled, and this quiets validation, but I don't know if it's a good general purpose approach.

I noticed that too. My initial idea was the same as yours, but I think I'll go with a virtual function in the base class that can be used in the derived example to pass a custom physical device feature set. Adding something to the base class (constructor) would require a change to all examples, and since there are already several virtual functions in the base class that can be derived I think that's the better choice.
I also think that's a bit cleaner and as future examples may require other physical device features to be enabled I guess I'll go with this one.

A virtual function wont work.  The device is created in the base class
ctor.  when a virtual function resolves in a ctor, the derived class
doesn't exist yet, so it would always call the base class version.
On Mon, May 30, 2016, 04:12 Sascha Willems<EMAIL_ADDRESS>wrote:

I noticed that too. My initial idea was the same as yours, but I think
I'll go with a virtual function in the base class that can be used in the
derived example to pass a custom physical device feature set. Adding
something to the base class (constructor) would require a change to all
examples, and since there are already several virtual functions in the base
class that can be derived I think that's the better choice.
I also think that's a bit cleaner and as future examples may require other
physical device features to be enabled I guess I'll go with this one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SaschaWillems/Vulkan/issues/165#issuecomment-222469967,
or mute the thread
https://github.com/notifications/unsubscribe/ABdmyvc8fvWaIvH_81ng7YXPREOnP_K-ks5qGsYYgaJpZM4IpZZw
.

Ah well, then I'll have to go with another solution.


Not calculating size and rendering Calendar for version 1.11 or higher but works on 1.8.0

Hello,
I have been using the calendar with version 1.8 without any problem with rendering the calendar view.
After update to the version 1.11 it just doesn't render it anymore, no code change.
And besides trying to set the content again at viewWillAppear just to make sure my view is completed nothing change.
Also is find to find any documentation mention something like "If you want to force layout user this"
Of course, tried to use setNeedsLayout and layoutIfNeeded but no success

Hi @felipeflorencio - I suspect this is due to this change https://github.com/airbnb/HorizonCalendar/pull/150
Previously, if you were using MonthsLayout.horizontal (horizontally-scrolling layout), then you had to guess how tall your calendar should be and set a height constraint that provided enough space for all of the calendar's content to fit in the vertical dimension. This was complicated and error-prone. See issues: https://github.com/airbnb/HorizonCalendar/issues/88, https://github.com/airbnb/HorizonCalendar/issues/110, and https://github.com/airbnb/HorizonCalendar/issues/125.
Starting in v1.11, CalendarView has an intrinsic content size. Now, you only need to give your CalendarView instance an X/Y position and width constraint. The height is determined based on the width. You can also set a height constraint if you'd like to make the calendar taller or shorter than its intrinsic height.

If you can post a screenshot of your view hierarchy (a screenshot of the Xcode view debugger would be helpful too), then I can help you figure out exactly what's wrong. I also think that if you look at the Example project, you can see how the constraints are set up https://github.com/airbnb/HorizonCalendar/blob/master/Example/HorizonCalendarExample/HorizonCalendarExample/Demo View Controllers/DemoViewController.swift#L49-L73

@felipeflorencio going to close this out since I haven't heard from you. Hope you got things working!


INT-B-21478 Add Oconus Rate area to prime v3 getMoveTaskOrder  api

B-21478
Summary
This PR introduces changes to the Prime V3 getMoveTaskOrder API to return Oconus (ie.. Alaska postal codes) Rate Area for all shipments.
It introduces two new OPTIONAL fields: originRateArea, destinationRateArea:

select * from re_rate_areas where id = '<ID>';
RateArea display is derived off Pickup and Destination postal codes. originRateArea/destinationRateArea will only be present if code is an OCONUS(Alaska) zip code and its location is determined based on shipment type. All non-PPM shipment will display rateArea on the root level of shipment while PPM will display on the PPMShipment level.
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Login as customer and create and submit a move containing all shipment types. For each shipment use all permutations for pickup and destination addresses with alaska and other continental states. NOTE -- at this time the system is not capable of accepting Alaska postal codes for PPM shipments. Need to follow up with Danny M on how to test with current restriction. For non-PPMs, you can use Alaska postal codes but you can't use AK for state. For now, just select any state but make sure to use an Alaska postal code.  select distinct state, postal_code from addresses where state = 'AK';
Login as service counselor and click  for move.
Login as TOO and find move. Select all shipments and click
Login Prime Sim. Open web developer and go to network tab. Click on move and go to details view.  In network tab view, select getMoveTaskOrder request. It will typically be at the bottom of the network request stack. View response json and confirm originRateArea/destinationRateArea if present/not present based on test cases.
Verify placement of rateArea information. Root level of shipment for non-PPM shipments and PPMShipment level for PPMs.

Goto http://primelocal:3000/swagger-ui/prime_v3.html#/moveTaskOrder/getMoveTaskOrder. Copy moveID from Prime Sim UI and execute. Verify rateArea info. Must match what is seen in step 5.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Able to see the rate areas with shipment to AK.


Extension forces space after :: in passage title

While this maybe a better code style, it's just a stylistic choice, and it would be great to have the ability to customize this behavior in extenson options. Especially since the extension doesn't fix this automatically and the users are forced to manual find/replace.

Added setting twee3LanguageTools.twee-3.warning.spaceAfterStartToken to disable the warning. Hope that helps! Automatic fixing is on the list of todos, will get to it soon.

Wow, that's fast! Thanks!

@cyrusfirheir Should this issue be resolved?


:tada: NEW: CSR admin ui (entities metadata)

After this PR, you can "reload entities" and it will use the session bearer.

Local storage key for Auth will also be back to work, as request will happen on client side.

To add tomorrow : don't return anything when the admin flag is not allowed!


update to latest libkv library

libkv evolved and each backend now needs to be registered with the library.
libkv also update the etcd client to the official coreos supported client, replacing the deprecated go-etcd client.

to fix
https://github.com/AcalephStorage/kviator/issues/3


Added mutators reference documentation

Also moved silencing to overview from getting started.

Closes #202

Whoops, I completely missed the commands and stdin/out specification because there are two specification sections!

@palourde I addressed comments - ready for review once again!


Comparison of outputs between CPU and GPU

Maybe change to an abstract scenario?

Changing because that's not in the scope of DITest


Keda 2.5 does not cleanly update from 2.4

Report
There appears to be a bug that prevents a clean and safe upgrade from keda 2.4 to keda 2.5, possibly related to this PR which changed metric names or This one . This affects pre-existing ScaledObjects are are present at the time of the 2.4 upgrade.
The symptom would be that the HPA loop would be attempting to evaluate a metric which did not actually exist within the Kubernetes external metrics API. Below is a snippet of the output of a kubectl describe hpa where the new keda 2.5 format of metrics would be queried and the log output of the external-metrics API
Metrics:                                               ( current / target )
  "s1-prometheus-burrow_lag" (target average value):   <unknown> / 120M
  resource cpu on pods  (as a percentage of request):  108% (3267m) / 100%

  Warning  FailedGetExternalMetric  3m6s (x791 over 3h22m)  horizontal-pod-autoscaler  unable to get external metric s001/s1-prometheus-burrow_lag/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name:,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: No matching metrics found for s1-prometheus-burrow_lag

kubectl get --raw '/apis/external.metrics.k8s.io/v1beta1/namespaces/s001/s1-prometheus-burrow_lag?labelSelector=app=myApp' | jq
Error from server: No matching metrics found for s1-prometheus-burrow_lag

Reverting to Keda 2.4 would immediately fix the issue and resume using the old names.
When in an errored state, remediation was possible by deleting all ScaledObjects and recreating them. This appeared to cause a reconciliation for the recreated scaledObject to the point the new-style metric becomes available.
Expected Behavior
Expect Keda 2.5 to immediately and reliably work out of the box for existing scaledObject definitions.
Actual Behavior
Upgrading from Keda 2.4 to Keda 2.5 is disruptive for pre-existing scaledObject-managed HPAs. New style metrics are inaccessible from the keda metrics APIserver
Steps to Reproduce the Problem

Deploy Keda 2.4
Create scaledObjects of Prometheus
Upgrade to Keda 2.5

This issue may be difficult to reproduce. This only occurred in 2 out of my 30 kubernetes clusters. But it consistently happened within those 2. I am entirely unclear as to why the 2 clusters persistently had the issue: they should be identically configured as the rest.
Logs from KEDA operator
 Warning  FailedGetExternalMetric  3m6s (x791 over 3h22m)  horizontal-pod-autoscaler  unable to get external metric s001/s1-prometheus-burrow_lag/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name=myApp:,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: No matching metrics found for s1-prometheus-burrow_lag

KEDA Version
2.5.0
Kubernetes Version
1.20
Platform
Other
Scaler Details
Prometheus
Anything else?
No response

Hi,
The change in the name is the expected behavior. Is the metric server updated to v2.5 too?
If you query available metrics manually, are you getting old names? The update should be automatic in both cases, the operator should update the HPA and the metric server should expose it without any extra action from your side.

This issue resurfaced on me again, after a several hour delay. This is the second time I have had the issue surface on me, each failing several hours after first release.  I will note that following the incident of the first time, I had deleted and recreated all scaledObjects and HPA objects while already deployed to keda 2.5 to ensure that there wouldn't be any potentially stale references left over. As I have had the issue a second time in multiple environments: this has not helped.
I support many environments, across these many environments I have two sets of behaviours:

One where keda 2.5 works without issue
One where keda 2.5 works for approximately 9~ hours before the new style metrics begin failing to resolve. This has happened 5 times now across 3 days and 3 environments.

For scenario 1) I have the following example where I DO see a mismatch between the enumeration of the available resources and what's actually queryable. This behaviour is consistent and reproducible across
(⎈)➜  ~ kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1" | jq

{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "external.metrics.k8s.io/v1beta1",
  "resources": [
    {
      "name": "prometheus-https---thanos-example-com-burrow_lag",
      "singularName": "",
      "namespaced": true,
      "kind": "ExternalMetricValueList",
      "verbs": [
        "get"
      ]
    },
}

(⎈)➜  ~ kubectl get --raw '/apis/external.metrics.k8s.io/v1beta1/namespaces/pool/s0-prometheus-burrow_lag?labelSelector=scaledobject.keda.sh/name=myApp' | jq
{
  "kind": "ExternalMetricValueList",
  "apiVersion": "external.metrics.k8s.io/v1beta1",
  "metadata": {},
  "items": [
    {
      "metricName": "s0-prometheus-burrow_lag",
      "metricLabels": null,
      "timestamp": "2021-12-05T23:30:10Z",
      "value": "0"
    }
  ]
}

Just as part of writing this up, I note that if I restart the (already 2.5) keda metrics API server, it begins returning the correctly named metrics when enumerating, data works properly just the same

(⎈ beta-barb-main-p-k8s-a:pool)➜  ~ kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1" | jq
{
"kind": "APIResourceList",
"apiVersion": "v1",
"groupVersion": "external.metrics.k8s.io/v1beta1",
"resources": [
{
"name": "s0-prometheus-burrow_lag",
"singularName": "",
"namespaced": true,
"kind": "ExternalMetricValueList",
"verbs": [
"get"
]
}

In 2) where keda actually fails I receive the following error messages and an inability to query the metrics.

apiVersion="autoscaling/v2beta2" type="Warning" reason="FailedGetExternalMetric" message="unable to get external metric s001/s2-prometheus-burrow_lag_sensor/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: csspcontentapi,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: No matching metrics found for s2-prometheus-burrow_lag_sensor"

Unfortunately I don't have a live example of the API output from today, but when I was investigating this for the first time I had the following unusual output. I now wonder if there is a cache expiring, or maybe a leader election changing of some sort that is causing a revert of the metric names. I do believe the two metrics below of the new format were fixed as the result of deleting and re-creating the ScaledObject definition. I wonder if restarting the metrics API server would have again refreshed the metrics to the point they resolve correctly. But needing to restart keda every few hours remains undesirable behaviour :)

friday morning example broken
kubectl get --raw '/apis/external.metrics.k8s.io/v1beta1' | jq '.resources[].name'
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag_sensor"
"prometheus-https---thanos-example-com-burrow_lag"
"s0-prometheus-burrow_lag_sensor"
"s1-prometheus-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"

But KEDA doesn't expose the same metric in different ways depending on the lifetime, I mean, maybe could you have more than 1 instance? The index is calculated inside the scaler in all GetMetricSpecForScaling and it's evaluated internally, so I can't understand for example this output:
kubectl get --raw '/apis/external.metrics.k8s.io/v1beta1' | jq '.resources[].name'
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag_sensor"
"prometheus-https---thanos-example-com-burrow_lag"
"s0-prometheus-burrow_lag_sensor"
"s1-prometheus-burrow_lag"
"prometheus-https---thanos-example-com-burrow_lag"

Despite if the index had been wrong, you should have all with s0-xxxx 🤔
I'm not sure if the metrics are cached at k8s level (maybe yes and that's the problem), I know that KEDA Metrics Server caches metric name, but again, the metric name should contain sx-xxxx
Do you know more about this @zroubalik @coderanger ?

Just to double-check, you have tried deleting and creating again the ScaledObjects, right? I mean, in the clusters where you have problems, did you also delete and create them again?

Here is a screenshot of the metric values over time. Note the flatline occurring in the middle of the night. That flatline continued until keda 2.4 was reverted at which points metrics began to flow again using the old name convention.
During the period of the flatline when the issue starts, the metrics server begins throwing 500s because it's unable to resolve requests for the metric name
  Warning  FailedGetExternalMetric  3m6s (x791 over 3h22m)  horizontal-pod-autoscaler  unable to get external metric s001/s1-prometheus-burrow_lag/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name:,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: No matching metrics found for s1-prometheus-burrow_lag

Given that I seem pretty capable of reproducing this issue, is there a guide anywhere documented for how to attach gdb to the metricsServer? Or where I can find symbols for that.

Could you run kubectl get pods -n {KEDA_NAMESPACE} -o jsonpath="{..imageID}" and paste the output please?

kedacore/keda@sha256:8fba3ab792c0e9d14ab046cda739e0925a39277c991122fd40474a59958bbd19
ghcr.io/kedacore/keda-metrics-apiserver@sha256:77e4967dc13cb8b3c6f1dcf0b6c5ad9e44e09daa621b567d73f7318627551756

The images look good :/
Tomorrow I will prepare an environment with KEDA v2.4 and I will try to reproduce the problem with any ScaledObject with Prometheus triggers updating to v2.5 (here it's 2h00 now).
It's weird because the difference is not at trigger level, it's at ScaledObject level and I updated KEDA in our (company) clusters without any issues, basically the new version of the operator updated the HPAs and the new version of the metrics server exposes them. We use RabbitMQ triggers but as I said, the change is at ScaledObject level 🤔
Maybe there is any specific behavior in prometheus scaler but I don't think so... Let's see tomorrow

Hi there.
Has there been any update on this issue?
We're also seeing a similar issue. We have 3 clusters where we have upgraded from 2.4.0 to 2.5.0, and two of them are producing errors.
We are using Azure Service Bus for the events, and getting this output
As you see below, the metric "s1-azure-servicebus-st-xxx" is showing as 'unknown'.
.
kubectl describe hpa keda-hpa-file-xxx

Name:                                                              keda-hpa-file-xxx
Namespace:                                                         default
Labels:                                                            app.kubernetes.io/managed-by=Helm
                                                                   scaledobject.keda.sh/name=file-xxx
Annotations:                                                       <none>
CreationTimestamp:                                                 Fri, 10 Dec 2021 11:51:54 +0000
Reference:                                                         Deployment/file-xxx
Metrics:                                                           ( current / target )
  "s1-azure-servicebus-st-xxx" (target average value):   <unknown> / 5
  "s1-azure-servicebus-mi-xxx" (target average value):  0 / 5
Min replicas:                                                      1
Max replicas:                                                      15
Deployment pods:                                                   1 current / 1 desired
Conditions:
  Type            Status  Reason            Message
  ----            ------  ------            -------
  AbleToScale     True    ReadyForNewScale  recommended size matches current size
  ScalingActive   True    ValidMetricFound  the HPA was able to successfully calculate a replica count from external metric s1-azure-servicebus-mi-xxx(&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: file-xxx,},MatchExpressions:[]LabelSelectorRequirement{},})
  ScalingLimited  True    TooFewReplicas    the desired replica count is less than the minimum replica count
Events:
  Type     Reason                   Age                    From                       Message
  ----     ------                   ----                   ----                       -------
  Warning  FailedGetExternalMetric  34s (x782 over 3h18m)  horizontal-pod-autoscaler  unable to get external metric default/s1-azure-servicebus-st-xxx/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: file-xxx,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: No matching metrics found for s1-azure-servicebus-st-xxx

🤦
I have to apologize, I didn't have so much time and I totally forgot this issue :(
I will take a look during the next week
Sorry

For this particular metric, when querying the metrics manually, we're seeing s0 instead of s1  in the metric name...
"s0-azure-servicebus-st-xxx"

FYI, we are seeing issues with multiple metrics

could your problem be related with this?

^ That actually does sound somewhat related. I definitely observed mismatches between what the metricNames were according to the metricsServer and what the HPA loop was actually querying.

okay, there are 2 different workarounds if you are affected by this error:

Update the SO to bump the generation (update de manifest, not delete and create it again)
Restart KEDA pods to recreate the cache

Could you check if these workarounds mitigate the problem? Just to know if this is the root cause and not invest time digging in the problem

First I'll need to see if I can actually find a way to reproduce this issue reliably: So far I've only been able to trigger it in my largest 4 environments :)
I'll see about trying to reproduce this today in a dev space. If I find a way to reproduce, what I'll actually do is build keda myself and cherrypick in your cache deletion commit to see if that fixes it.

nice!
Thanks for your help ❤
I'm thinking and probably updating the SO name is enough to avoid the cache because the (cache) key is generated using the name and namespace

Our team will be testing this in the new year.

@glassnick Did you manage to give this a try?

I tried myself to reproduce the error that I had originally seen in a dev environment, but I was unable to.
I had observed the error only in my largest environments so I had the suspicion that the error was related to number of objects in the cluster. Unfortunately just throwing large numbers of objects at a dev environment was not enough to reproduce at least the error cases I had seen.
My next step is kind of the nuclear one with running keda in my largest environments where I can reproduce the bug under the delve debugger and breakpointing exactly what's failing. It might be a while before I have time to continue at that level of debugging for my own particular issues though.


message_send: Fix tests to use json encoded 'to'.

OpenApi docs requires to to be json encoded.

Hmm, are some of these supposed to be lists of direct message recipients, though?

Hmm, are some of these supposed to be lists of direct message recipients, though?

Hmm yes, that is another thing that is being handled implicitly during parsing in the endpoint (converting dm recipients to a list). This too should be address whenever the raw string issue is addressed.
I have changed the test cases to lists.


store the base64 images

I have a base64 image in my request and want to store this on the file as png file
How should I do this?
In document I read it said I should send file to the sharp and as you know base64 is just an string and I need to store data as png or jpg file on server

Please see #104


Now waits for editor initialized event before sending commands

Newer versions of Froala editor spits out warning when trying to access methods before it is being fully initialized. Now prevents accessing those methods before editor is fully initialized.

@stefanneculai
Would it be possible to create a fix release (v2.3.1) to incorporate this pull-request. Really annoying to see all those froala warnings in the browser and test windows.

We'll make a release V2.3.1 shortly. We keep this version in sync with the editor version.

Ok, thanks @stefanneculai