SUMO-235493 Fix the CloudFormation template for Kinesis log sources

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.
We changed following SizeInMBs from 4 to 1 as the recommendations we gave to our customer for their Kinesis firehose configuration
        BufferingHints:
          IntervalInSeconds: 60
          SizeInMBs: 1

I have no access to the old link reference thus I added a new yaml file directly in this folder. @kimsauce Please let me know if this works.

[X] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request needs to update the downloadable CloudFormation template for CloudWatch logs ingestion via Kinesis log source.

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions, .clabot
[ ] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

thank you, @yuting-liu !

@kimsauce Can you please merge the PRas I don't have the permission to commit the change? Thank you.

@kimsauce Can you please merge the PRas I don't have the permission to commit the change? Thank you.

Sure thing!


Add  to the list of merchants

What's the name of your business?
YogiWay
What's the URL of the website?
https://yogiway.cz/
Write a brief description of your business/service (max 50 characters)
yoga mats, bags and yoga accessories
Enter the URL where a Monero mention can be found
https://yogiway.cz/content/1-doprava-a-platba
How do you accept Monero? (choose only one option)

[ ] Monero integrations (github.com/monero-integrations)
[ ] Globee
[X] Native wallet
[ ] Other payment gateaway (Coinpayments, Morphtoken, etc. Please specify)

How would you categorize your business? (choose only one option)

[ ] Exchange
[ ] Block Explorer
[ ] Payment Gateway
[ ] Web Hosting
[ ] Tool
[ ] Service
[X] Goods
[ ] Entertainment

Comment

A correctly completed request, a rare sight! :P
Looks OK.

Cross posting a link to the PR for visibility: https://github.com/monero-project/monero-site/pull/1467

@Peter-Liska YogiWay has been added to the list of merchants. https://www.getmonero.org/community/merchants/

Nice 👍


Add some callbacks of copy/read/write/map

CTS case： bufferreadwrite
(cherry picked from commit 73591ab)

#36


Revert "fix wheel selection"

Reverts DavHau/mach-nix#471
reason: https://github.com/DavHau/mach-nix/issues/475

@DavHau: Thank you!


Add GoatCounter tracking

@Razzeee proposed to add basic visitor tracking using GoatCounter like on the wiki.
If people agree this is worthwhile, this is the code to include:
<script data-goatcounter="https://koditv.goatcounter.com/count" async src="//gc.zgo.at/count.js"></script>

Hrm, would that add to the same counter?

As the wiki? No

This seems fine to me. I'll take a look at integrating into the header via the SEO component.

Done with da08b6a99a6bcb69af21f8c20d3e379fbbd8ee9d. I verified that the script is in the header and clicked around a bit. Whatever login is required at GoatCounter isn't included in the 1Password vaults to which I have access (website or Entire Team), so I couldn't check to see if they were being properly stored or not.  I'll mark this as needs testing until we confirm the hits are making it to Goatcounter.


do not error when processing sources that include node hashbang

cc @koshic  @tommy-mitchell re https://github.com/iambumblehead/esmock/issues/215
this PR removes the hashbang line from the sources before prepending import expressions, then re-adds any hashbang line to the final result returned by the loader

@tommy-mitchell thank you for giving esmock your valuable attention. Feel free to leave any comments or advice.
This PR builds on the test from your earlier PR

this test is failing in windows and maybe a different PR should resolve it. It relates to filesystem paths
"test-metaresolve": "rimraf dist && tsc && cross-env \"NODE_OPTIONS=--experimental-import-meta-resolve --loader=esmock\" NODE_NO_WARNINGS=1 ava",

the win32 could probably be resolved soon, but slow internet speeds here make it difficult to setup a windows virtual machine to run tests with latest node 18

I have a Windows x64 machine, would that work for reproducing? I could try resolving it

@tommy-mitchell that would be great. Here is where I think the problem is. I think import.meta.resolve is returning the path n the wrong format
const resolve = isMetaResolve ?
  (import.meta.resolve.constructor.name === 'AsyncFunction'
    ? async (id, p) => import.meta.resolve(id, asFileURL(p))
      .catch(() => resolvewith(id, p))
    : (id, p) => {
      try { return import.meta.resolve(id, asFileURL(p)) }
      catch { return resolvewith(id, p) }
    })
  : resolvewith

cd into the tests-source-map folder and npm install then npm test to run the tests

Maybe we should only support the async variant of import.meta.resolve, eg node 20+ and fallback to resolvewith for every other case. Any solution you recommend is good too

possibly related https://github.com/nodejs/node/issues/35518

Pinning the node version number to 18.16 resolved the pipeline error. A ticket for that node 18.17 issue is created here https://github.com/nodejs/node/issues/48948 and so this PR for hashbang support is complete and ready for review

if anyone has retro-active review comments feel free to leave those


subprocess.CalledProcessError

Hi,
I'm getting the following error when I try to run unsloth on Windows with WSL,
any idea what causes it?
Python 3.10
model, tokenizer = FastLanguageModel.from_pretrained(mistralai/Mistral-7B-Instruct-v0.2)
FastLanguageModel.for_inference(model)
 output_ids = model.generate(
            input_ids=input_ids,
            attention_mask=attention_mask,
            generation_config=generation_config
        )

   output_ids = model.generate(
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
      return func(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/transformers/generation/utils.py", line 1544, in generate
      return self.greedy_search(
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/transformers/generation/utils.py", line 2404, in greedy_search
      outputs = self(
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
      return self._call_impl(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
      return forward_call(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/accelerate/hooks.py", line 166, in new_forward
      output = module._old_forward(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/unsloth/models/mistral.py", line 211, in MistralForCausalLM_fast_forward
      outputs = self.model(
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
      return self._call_impl(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
      return forward_call(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/accelerate/hooks.py", line 166, in new_forward
      output = module._old_forward(*args, **kwargs)
    File "/mnt/d/Prace/transformers/prompting-venv-wsl/lib/python3.10/site-packages/unsloth/models/llama.py", line 602, in LlamaModel_fast_forward
      layer_outputs = decoder_layer(
    File "/mnt/d/Prace/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
      return self._call_impl(*args, **kwargs)
    File "/mnt/d/Prace/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
      return forward_call(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/accelerate/hooks.py", line 166, in new_forward
      output = module._old_forward(*args, **kwargs)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/unsloth/models/llama.py", line 398, in LlamaDecoderLayer_fast_forward
      hidden_states = fast_rms_layernorm(self.input_layernorm, hidden_states)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/unsloth/kernels/rms_layernorm.py", line 150, in fast_rms_layernorm
      out = Fast_RMS_Layernorm.apply(X, W, eps)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/torch/autograd/function.py", line 553, in apply
      return super().apply(*args, **kwargs)  # type: ignore[misc]
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/unsloth/kernels/rms_layernorm.py", line 106, in forward
      _rms_layernorm_forward[(n_rows,)](
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/triton/runtime/jit.py", line 532, in run
      self.cache[device][key] = compile(
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/triton/compiler/compiler.py", line 614, in compile
      so_path = make_stub(name, signature, constants, ids, enable_warp_specialization=enable_warp_specialization)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/triton/compiler/make_launcher.py", line 37, in make_stub
      so = _build(name, src_path, tmpdir)
    File "/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/triton/common/build.py", line 106, in _build
      ret = subprocess.check_call(cc_cmd)
    File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/gcc', '/tmp/tmpbd9p8vsg/main.c', '-O3', '-I/mnt/d/transformers/prompting-venv-wsl/lib/python3.10/site-packages/triton/common/../third_party/cuda/include', '-I/usr/include/python3.10', '-I/tmp/tmpbd9p8vsg', '-shared', '-fPIC', '-lcuda', '-o', '/tmp/tmpbd9p8vsg/_rms_layernorm_forward.cpython-310-x86_64-linux-gnu.so', '-L/usr/lib/wsl/lib']' returned non-zero exit status 1.

accelerate==0.27.2
aiohttp==3.9.3
aiosignal==1.3.1
alembic==1.13.1
aniso8601==9.0.1
annotated-types==0.6.0
anyio==4.3.0
async-timeout==4.0.3
attrs==23.2.0
bitsandbytes==0.42.0
blinker==1.7.0
certifi==2024.2.2
charset-normalizer==3.3.2
click==8.1.7
cloudpickle==3.0.0
contourpy==1.2.0
cycler==0.12.1
dataclasses==0.6
dataclasses-json==0.6.4
datasets==2.18.0
dill==0.3.8
distro==1.9.0
docker==7.0.0
docstring-parser==0.15
entrypoints==0.4
exceptiongroup==1.2.0
filelock==3.9.0
Flask==3.0.2
fonttools==4.49.0
frozenlist==1.4.1
fsspec==2024.2.0
gitdb==4.0.11
GitPython==3.1.42
graphene==3.3
graphql-core==3.2.3
graphql-relay==3.2.0
greenlet==3.0.3
gunicorn==21.2.0
h11==0.14.0
httpcore==1.0.4
httpx==0.27.0
huggingface-hub==0.21.3
idna==3.6
importlib-metadata==7.0.1
itsdangerous==2.1.2
Jinja2==3.1.2
joblib==1.3.2
kiwisolver==1.4.5
Mako==1.3.2
Markdown==3.5.2
markdown-it-py==3.0.0
MarkupSafe==2.1.3
marshmallow==3.21.0
matplotlib==3.8.3
mdurl==0.1.2
mlflow==2.11.0
mpmath==1.3.0
multidict==6.0.5
multiprocess==0.70.16
mypy-extensions==1.0.0
networkx==3.2.1
numpy==1.26.3
nvidia-cublas-cu12==<IP_ADDRESS>
nvidia-cuda-cupti-cu12==12.1.105
nvidia-cuda-nvrtc-cu12==12.1.105
nvidia-cuda-runtime-cu12==12.1.105
nvidia-cudnn-cu12==<IP_ADDRESS>
nvidia-cufft-cu12==<IP_ADDRESS>
nvidia-curand-cu12==<IP_ADDRESS>
nvidia-cusolver-cu12==<IP_ADDRESS>
nvidia-cusparse-cu12==<IP_ADDRESS>
nvidia-nccl-cu12==2.19.3
nvidia-nvjitlink-cu12==12.1.105
nvidia-nvtx-cu12==12.1.105
openai==1.13.3
packaging==23.2
pandas==2.2.1
peft==0.9.0
pillow==10.2.0
protobuf==4.25.3
psutil==5.9.8
pyarrow==15.0.0
pyarrow-hotfix==0.6
pydantic==2.6.3
pydantic_core==2.16.3
Pygments==2.17.2
pyparsing==3.1.1
python-dateutil==2.9.0.post0
pytz==2024.1
PyYAML==6.0.1
querystring-parser==1.2.4
regex==2023.12.25
requests==2.31.0
rich==13.7.1
safetensors==0.4.2
scikit-learn==1.4.1.post1
scipy==1.12.0
sentencepiece==0.2.0
shtab==1.7.0
six==1.16.0
smmap==5.0.1
sniffio==1.3.1
SQLAlchemy==2.0.27
sqlparse==0.4.4
sympy==1.12
threadpoolctl==3.3.0
tiktoken==0.6.0
tokenizers==0.15.2
torch==2.2.0
torchaudio==2.2.0+cu121
torchvision==0.17.0+cu121
tqdm==4.66.2
transformers==4.38.2
triton==2.2.0
trl==0.7.11
typing-inspect==0.9.0
typing_extensions==4.8.0
tyro==0.7.3
tzdata==2024.1
unsloth @ git+https://github.com/unslothai/unsloth.git@d862d053ed7deb2275e47d2aec2f7cd587decf0e
urllib3==2.2.1
Werkzeug==3.0.1
xformers==0.0.24
xxhash==3.4.1
yarl==1.9.4
zipp==3.17.0

`

@pauli31 Sorry on the issue! :( Maybe this might help: https://github.com/pytorch/builder/issues/1318 ? It seems like maybe your torch package is partially broken probably, and so Triton can't seem to link properly - it's best to reinstall Torch and Triton :(

Thank you are right. It is something with the libraries versions, unfortunately, I was not able to figure it out.

@pauli31 Have you tried our notebooks on Colab or Kaggle if those help?

Thank you not, yet I'll try it.

请问您 这是否解决了

Could you please tell me if this has been resolved?

I made the installation probably a bit easier on the Readme - maybe it might help!


http(s) server has no types

hi there.
When referencing either httpServer or httpsServer, these objects seem to miss their types.

only app and logger objects have their types

Node version: 16.17.0
TypeScript Compiler version: 4.8.4
Visual Studio Code version: 1.73.0 (user setup)
express-zod-api package version: 8.3.4

nvm, just had to npm install -D @types/node


f08 flag available for TAF

What changes does this PR introduce?
New feature to allow passing -f08 flag to TAF
What is the current behaviour?
No -f08 flag
What is the new behaviour
-f08 flag available
Does this PR introduce a breaking change?
NA
Other information:
Default float is still -f95
Suggested addition to tag-index
Allow for -f08 flag to be passed to TAF through TAF_COMMON_FLAGS

Thanks for this addition. Work for me.
Minor comment: Does it make sense to move this part
https://github.com/MITgcm/MITgcm/blob/6519d6065182f3d9cd4c2499f109c674671b329a/tools/adjoint_options/adjoint_default#L11-L17
which sets TAF_FORTRAN_VERS if unset, to just before l47? In this way, the version-code is in one place.

which sets TAF_FORTRAN_VERS if unset, to just before l47? In this way, the version-code is in one place.

Moved that stanza up.

Also, I am going to adjust the tag-index addition, to mention TAF_FORTRAN_VERS instead of TAF_COMMON_FLAGS since the former is the env. var that needs to be set and is recognized by the optfile while the later is just an internal variable that the user don't have to worry about.

Nothing new to add from me


Feature Request: Diagonal ghost blocks in TE

Now that we can shimmy along diagonal walls, it would make sense to have the option of ghost blocks doing the same. Currently in TE we can only have the normal square-shaped ones.

I moved this issue into the TE repo instead: https://github.com/MontyTRC89/Tomb-Editor/issues/774


Preloader mime never finishes in some directories

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
kitty-0.32.2
Yazi version
yazi 0.2.3 (e51e8ad 2024-02-24)
Did you try the latest main branch to see if the problem got fixed?
Tried, but the problem still
Describe the bug
Navigating most directories (not all), the task "Run preloader mime with xx target(s)" never finishes.
https://github.com/sxyazi/yazi/assets/91850165/53f4410d-c9d9-4a9f-b370-442a0102f4b1
Expected Behavior
The task finishes.
To Reproduce
Just build and run, navigate around. Directories with various files seem more prone. The problem does not manifest while navigating inside this repo's directory. /etc or ~ manifest the problem right away on my machine.
Configuration
No config at all.
Anything else?
Newer commits (8ea7556) made it worse - when this bug happens, either left and middle panes, or right pane are empty (navigation still works, the footer shows the current file/dir under cursor)

Thank you for the report!
Please run sh --help and sh -c "file -v" and paste their output here.
Then open the task manager with w and press <Enter> to see if there are any errors, and paste them here as well.

❯ sh --help
sh: 0: Illegal option --
❯ sh -c "file -v"
file-5.45
magic file from /usr/share/misc/magic

Please note I tried the same with following patch and it didn't change anything in this matter
diff --git a/yazi-plugin/src/external/shell.rs b/yazi-plugin/src/external/shell.rs
index 76d1ca7..d76e1d8 100644
--- a/yazi-plugin/src/external/shell.rs
+++ b/yazi-plugin/src/external/shell.rs
@@ -33,7 +33,7 @@ pub fn shell(opt: ShellOpt) -> Result<Child> {

    #[cfg(unix)]
    return Ok(unsafe {
-       Command::new("sh")
+       Command::new("zsh")
            .env("YAZI_LEVEL", (level + 1).to_string())
            .arg("-c")
            .stdin(opt.stdio())

The output of sh looks a bit strange, which sh are you using? Is it possible to see its version information? Mine looks like this:
sh --help
GNU bash, version 3.2.57(1)-release-(arm64-apple-darwin22)
Usage:	sh [GNU long option] [option] ...
	sh [GNU long option] [option] script-file ...

So we seem to come back to https://github.com/sxyazi/yazi/discussions/718 :)

Haha this could be relevant. I need to investigate further.

~ ❯ ll `which sh`
Lrwxrwxrwx root root -  01-01 23:00 sh -> /usr/bin/dash

This is nothing of my doing. Linux Void. I know for certain Debian has the same.
Because I stumbled upon this in another project - "#!/bin/sh"-scripts written in an old Centos didn't work in Debian.
Long story short: when you write #!/bin/sh you should expect only the POSIX functionality, not the bash addons.
Dash is POSIX compliant, so it correctly rejects various non-POSIX addons.
When you want bash, you have to write #!/usr/bin/bash

--- /yazi-plugin/preset/plugins/mime.lua
+++ /yazi-plugin/preset/plugins/mime.lua
@@ -1,6 +1,7 @@
 local M = {}

 local function match_mimetype(s)
+	ya.err(s)
 	local type, subtype = s:match("([-a-z]+/)([+-.a-zA-Z0-9]+)%s*$")
 	if string.find("application/audio/biosig/chemical/font/image/inode/message/model/rinex/text/vector/video/x-epoc/", type, 1, true) then
 		return type .. subtype

Please apply this patch to build Yazi, perform the same operation, and then copy the contents of ~/.local/state/yazi/yazi.log here.

ERROR yazi::components::manager: runtime error: [string "yazi-plugin/src/plugin.rs:25:13"]:17: attempt to index a nil value (local 'style')
stack traceback:
	[C]: in metamethod 'index'
	[string "yazi-plugin/src/plugin.rs:25:13"]:17: in method 'render'
	[string "yazi-plugin/src/plugin.rs:29:13"]:29: in function <[string "yazi-plugin/src/plugin.rs:29:13"]:18>
    at yazi-fm/src/components/manager.rs:17

  2024-02-24T18:07:22.594815Z ERROR yazi_plugin::utils::log: image/png

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594838Z ERROR yazi_plugin::utils::log: image/png

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594845Z ERROR yazi_plugin::utils::log: video/x-matroska

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594854Z ERROR yazi_plugin::utils::log: image/png

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594858Z ERROR yazi_plugin::utils::log: application/pdf

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594865Z ERROR yazi_plugin::utils::log: application/pdf

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594871Z ERROR yazi_plugin::utils::log: application/pdf

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594875Z ERROR yazi_plugin::utils::log: text/x-shellscript

    at yazi-plugin/src/utils/log.rs:10

  2024-02-24T18:07:22.594881Z ERROR yazi_plugin::utils::log: regular file, no read permission

    at yazi-plugin/src/utils/log.rs:10

Hi, I made a new PR to fix this, https://github.com/sxyazi/yazi/pull/725, let me know if it works for you!

Works, thank you!

Nice, thanks for testing! Let me merge it then


PowerToys Run error during search

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
ALT+space to bring up search. Typed in a file name and during the brief search, the error appeared
✔ Expected Behavior
The file name to show up in the list.
❌ Actual Behavior
Error below:
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22622.0
IntPtr Length: 8
x64: True
Date: 8/8/2022 8:54:37 AM
Exception:
System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Other Software
No response

/dup #18166

For any users that are able to replicate this consistently, can you please update to 0.68.1 and disable thumbnail generation to verify if it fixes the issue? Please let us know on #18166!


Vi bindings not working after setting in .zpreztorc

Description
Setting key bindings to vi in .zpreztorc does not set the key bindings as they are still emacs
Expected behavior
In insert mode, pressing 'v' should invoke the vim to edit the command line
Actual behavior
Nothing happens when 'v' is pressed. Pressing ^X^E invokes vim.
Steps to Reproduce
As above
Versions

Prezto commit: commit 5d7c990eec21e83c0735f6b8e7d1d669102cbb4f
ZSH version: 5.7 (x86_64-apple-darwin18.2.0)
OS information: OS X 10.14.3

This is the desired behavior. The reason is that if we were to have v go to the editor it then stops you from being able to use v movements like you would in vim. I am not a huge fan of the amount of keys I have to hit to get to the editor, but there are tradeoffs for everything.


cant authenticate - last working version 0.17.1

Copilot Chat Extension Version: 0.18+
Version: 1.92.2 (Universal)
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.6.0
Logs:
024-08-17 14:26:42.365 [info] [ContextKeysContribution] You are not signed in to GitHub. Please sign in to use Copilot.
2024-08-17 14:26:42.421 [info] [gitExtensionService] Successfully activated the vscode.git extension.
2024-08-17 14:26:42.421 [info] [gitExtensionService] Enablement state of the vscode.git extension: true.
2024-08-17 14:26:42.421 [info] [gitExtensionService] Successfully registered Git commit message provider.
2024-08-17 14:26:58.334 [info] [auth] GitHub login failed
2024-08-17 14:26:58.341 [info] [auth] GitHub login failed

sometimes getting:
2024-08-17 14:28:23.972 [info] [auth] GitHub login failed
2024-08-17 14:28:23.972 [info] [LanguageModelAccess] LanguageModel/Embeddings are not available without auth token
2024-08-17 14:28:23.972 [info] [LanguageModelAccess] Error: GitHubLoginFailed
at RS.authShowWarnings (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:633:13828)
at RS.getCopilotToken (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:633:11894)
at Q_.getCopilotToken (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:144:2645)
at PS._getAuthSession (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:634:2188)
at /Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:634:1777
at PS._registerEmbeddings (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:634:1747)
at async Promise.all (index 1)
at async Promise.allSettled (index 0)
at Zct (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:1365:4403)
at Xct (/Users/amosg/.vscode/extensions/github.copilot-chat-0.18.1/dist/extension.js:1365:3372)
at m.n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:144:6409)
at m (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:144:6372)
at m.l (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:144:5829)
Steps to Reproduce:

install
try to login (in any way - profile, chat, copilot logo on bottom)

same problem on Linux Mint, downgrading extension to v0.17.1 make authentication work again

Can you please try these steps?
https://github.com/microsoft/vscode-copilot-release/issues/1444#issuecomment-2278793021


Performance on Middleburry and Sintel

Hi, can you tell me how did you set the image size for Middleburry and Sintel evaluation? Since I notice that input size matters a lot.

Hi! From https://github.com/simonmeister/UnFlow/blob/master/src/eval_gui.py#L28:

middlebury: height = 512, width = 640
sintel: height = 512, width = 1024

Thanks a lot!


[Compatibility] Disable pruning

Description
Should hopefully help make it faster. Also fix small bug.
Already fixed fullnode.yaml on the one currently running host. This is to ensure the rewrite is correct in case the file ever gets deleted from the host.
Test Plan
testinprod

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@sadhansood could you chime in on the tradeoffs here? Will it speed up fullnode sync speed materially? And from what I've observed, I'm not necessarily seeing a large decrease in disk usage from having had pruning enabled before this change vs now. The machines that this is running on are a bit constrained with disk space (~420GB SSD), which, with pruning, was completely filled after syncing to epoch 755 on testnet.

don't think it's going to speed up the sync dramatically, but worth a shot.
Space-wise, we've observed that automatic background compactions do not reclaim space fast enough.
However, after a manual full table compaction run on the testnet, the object's size decreased four times

Abandoning based on input from @phoenix-o . I think with sharding we won't need the incremental speed up. At that point, disk space will be the more pressing constraint.


HDDS-4307.Start Trash Emptier in Ozone Manager

What changes were proposed in this pull request?
The change here is to implement a Trash emptier for Trash Deletion. This feature basically introduces Trash for Ozone File System by leveraging the hadoop code for Trash ( Trash.java) . When a client does a delete on the filesystem, it calls the fs.rename( src,dst,Options) api which does a rename to the Trash Path. As an initial approach all operations are on the KeyTable itself.
This pr starts a TrashEmptier and deletes all the files obtained by fs.getTrashRoots(). By passing an OFS uri pointing to the root to this fs  instance covering all volumes and buckets will be ensured.  Thus  the background service starts the emptier thread which basically iterates through the trash roots and does the checkpointing and then deletion from checkpointed directories.
bin/ozone fs -rm  o3fs://buck1.vol1/Test2
2020-10-20 18:42:12,779 [main] INFO fs.TrashPolicyDefault: Moved: 'o3fs://buck1.vol1/Test2' to trash at: /.Trash/sadanand.shenoy/Current/Test2
bin/ozone fs -ls -R  o3fs://buck1.vol1/
-rw-rw-rw-   1 sadanand.shenoy sadanand.shenoy          0 2020-10-20 18:42 o3fs://buck1.vol1/.Trash/sadanand.shenoy/Current/Test2
after checkpoint interval
-rw-rw-rw-   1 sadanand.shenoy sadanand.shenoy          0 2020-10-20 18:45 o3fs://buck1.vol1/.Trash/sadanand.shenoy/201020184500/Test2
The key gets deleted after the trash interval.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4307
How was this patch tested?
Manually as well as few unit Tests.

Can you address the CI failures ?

Thanks @sadanand48 for the contribution. I've added few comments, please go through it.

Thanks @rakeshadr for the review. Addressed your comments . Will incorporate the changes you suggested on the BackgroundService when i include it in the next patch.

+1 LGTM


[DRH-3]: Fix import for celery 5.0

Celery 5.0 no longer contains the celery.task module.  The Task class has been moved into the celery namespace.

@erikcw we have to add fake JIRA ticket syntax since we can't figure out a way to get rid of it for now.

@erikcw we have to add fake JIRA ticket syntax since we can't figure out a way to get rid of it for now.

This fix is not quite complete since in the newer version of Celery the task won't get registered by default. I think converting it to a shared_task is the correct approach here?


toThrowError not working

Describe the bug
it expect with exception should work
Reproduction
import { describe, expect, it } from 'vitest';
import { ZodError } from 'zod';
import z from 'zod'

describe('ZOD validation', () => {

    it('test object validation', () => {
        const CarSchema = z.object({
           sits: z.number().lte(5).positive(),
           haveAlarm: z.boolean(),
          sport: z.boolean().optional(),
        });

        expect(CarSchema.parse({
            sits: -5,
            haveAlarm: true,
            sport: 'yes',
        })).toThrowError(ZodError);
    });
});

console info:

 FAIL  tests/validation.zod.test.ts > ZOD validation > test object validation
ZodError: [
  {
    "code": "too_small",
    "minimum": 0,
    "type": "number",
    "inclusive": false,
    "message": "Number must be greater than 0",
    "path": [
      "sits"
    ]
  },
  {
    "code": "invalid_type",
    "expected": "boolean",
    "received": "string",
    "path": [
      "sport"
    ],
    "message": "Expected boolean, received string"
  }
]

System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (4) x64 Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz
    Memory: 3.87 GB / 15.89 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.18 - ~\.yarn\bin\yarn.CMD
    npm: 8.18.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 107.0.5304.107
    Edge: Spartan (44.19041.1266.0), Chromium (107.0.1418.56)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vitest: ^0.25.3 => 0.25.3

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You need to wrap your call in function:
-  expect(CarSchema.parse({
+  expect(() => CarSchema.parse({
      sits: -5,
      haveAlarm: true,
      sport: 'yes',
  })).toThrowError(ZodError);

Otherwise it's impossible to catch the error. Please, read documentation before creating an issue.

strong type of expect should be stronger then


add typescript support to e2e tests

Summary
Add Typescript support to e2e tests
Ticket Link
https://mattermost.atlassian.net/browse/MM-45386
Related Pull Requests
N/A
Release Note
NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/212575

@mickmister I've added you to further check on how this will play with E2E tests of https://github.com/mattermost/mattermost-plugin-apps which imports this repo as its dependency with custom commands/helpers.

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/216953


Added a schedule for updating the SHIR version in the base image

Also disabling auto-update as it is broken in a windows container per:
https://docs.microsoft.com/en-us/azure/data-factory/how-to-run-self-hosted-integration-runtime-in-windows-container#limitations

I'm going to merge this after monitoring the SHIR on test for teh weekend

Will merge now


Change back question ID length to 8 bytes

Change the ID length of questions during Election create back to 8 bytes.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
27 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.5%) to 60.393%

Files with Coverage Reduction
New Missed Lines
%

services/dkg/pedersen/handler.go
13
84.84%

services/shuffle/neff/handler.go
14
79.63%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
2978

Relevant Lines:
4931

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
27 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.5%) to 60.393%

Files with Coverage Reduction
New Missed Lines
%

services/dkg/pedersen/handler.go
13
84.84%

services/shuffle/neff/handler.go
14
79.63%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
2978

Relevant Lines:
4931

💛  - Coveralls


[feature] use css file for HTML report generation

🧩 Feature
Description
Prompt users to define a reference to a css file to be used for the generated HTML report.

inline the CSS
provide a wiki article containing the used skeletton

will be obsolete by: #13


Cloudflare KV state store and Queues binding - new components

Description
This PR adds two new components:

state.cloudflare.kv is a state store backed by Cloudflare KV
bindings.cloudflare.queus is a binding that allows publishing messages to Cloudflare Queues

This is implemented as a binding and not pubsub because (at least at the moment), subscribers to Queues can only be Workers, so Dapr cannot receive messages from a Queue.

They are implemented in the same PR because they share the entire underlying "infrastructure". Both components, in fact, require a Cloudflare Worker to be deployed to work.
The Worker can be deployed automatically by the components. A new internal package takes care of deploying the Worker (and upgrading it if needed) by invoking the Cloudflare APIs. Additionally, all requests from Dapr to the Worker must be authenticated using a JWT signed by Dapr using EdDSA (using Ed25519).
Metadata properties
Both components share a number of required metadata properties to work:

workerName: This is the name of the Worker that is deployed. This should be unique per each component: that is, users should not use the same worker to bind to two different KV namespaces or two different Queues, or to bind to a Queue and a KV namespace
key: Ed25519 private key (PEM-encoded) that is used by Dapr to issue JWT tokens to authenticate with the Worker.

This is generated with openssl genpkey -algorithm ed25519 -out private.pem
Note: on MacOS, this is not available with the built-in LibreSSL that is invoked with openssl; instead, install OpenSSL via Homebrew and then use `/opt/homebrew/opt/openssl@3/bin/openssl

There are then two options:

The user can pre-create the Worker and have it deployed manually (I'll write docs for that).

In this case, the user must set workerUrl to the URL of the worker, for example https://daprdemo.mydapr.workers.dev

Dapr can create a Worker (and upgrade it if needed) automatically. Required metadata properties:

cfAPIToken: API token for Cloudflare (created with the "Workers" template)
cfAccountID: Cloudflare account ID

For the Queues binding, this is needed too:

queueName: Name of the Cloudflare Queue

Must be pre-created for example with npx wrangler queues create <queuename>

For the KV state store, this is needed too:

kvNamespaceID: ID of the KV namespace

Must be pre-created, for example with npx wrangler kv:namespace create <namespacename>
The ID is a hex string returned by the command above, not the name

Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[ ] Enable Conformance tests

[ ] I have reached out to some contacts at Cloudflare to see if we can get an account, as certain features require the paid Workers plan ($5/month)

[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: @ItalyPaleAle TODO

Great components to have, thanks for the PR. I do have questions around the expected usability aspect when working with these components from compute (Dapr in this case) that's not deployed in a Cloudflare edge data centers - and if it's recommended or expected for users running compute outside of Cloudflare to use Cloudflare's KV and queue systems in regards to latency.

Those are good questions.
The latency should not be a major concern. I haven't done accurate measurements, but Dapr would make requests to the closest CF datacenter, so latency would not be worse than any other cloud state store we support (like hosted SQL databases) - actually, given how many datacenters Cloudflare has, I would expect latency to be among the best of the cloud-hosted services.
With regards to KV, one thing to keep in mind is that its consistency model is closer to a "session-level" consistency (although it's "session-less"). Requests that hit the same Cloudflare datacenter see the data immediately updated. But if a request were to hit a different datacenter, there could be a delay of up to 30-60s before KV data is consistent. This shouldn't be a big issue in the case of Dapr, since the compute is normally running in a single DC (and if people use geo-redundancy... then that's on them to figure it out :) )
As for the use case, I see the KV component more like a step into integrating Dapr with the Workers ecosystem and enabling more interoperability with code that's running on Workers. Outside of users that are also using Workers for other things, I wouldn't otherwise recommend using KV as a general purpose state store however, unless users have some very specific needs.
Different story is for Queues. The Dapr integration in this case is, in my mind, a way to enable scaling Dapr apps so they can leverage Workers. The idea is that you have some work that you want to perform in a Worker, so you use Dapr to add that to a queue, and then a Worker would take it up. I think there's a lot of use for this.
For context, the Queues binding was the first thing I added (and you can see that in the name of the branch). I added the KV state store later because I wanted to create a "common infra" for Workers-based components, and adding KV was the forcing function for me to do that: after I created the internal package with the common infra, adding the KV state store was a very low-hanging fruit. I am envisioning that the "common infra" could then be used for a bunch of other things, including other components (maybe Cloudflare D1?) and even for the "compute" component I've proposed in dapr/proposals#16

@yaron2
Those are good questions.
The latency should not be a major concern. I haven't done accurate measurements, but Dapr would make requests to the closest CF datacenter, so latency would not be worse than any other cloud state store we support (like hosted SQL databases) - actually, given how many datacenters Cloudflare has, I would expect latency to be among the best of the cloud-hosted services.
With regards to KV, one thing to keep in mind is that its consistency model is closer to a "session-level" consistency (although it's "session-less"). Requests that hit the same Cloudflare datacenter see the data immediately updated. But if a request were to hit a different datacenter, there could be a delay of up to 30-60s before KV data is consistent. This shouldn't be a big issue in the case of Dapr, since the compute is normally running in a single DC (and if people use geo-redundancy... then that's on them to figure it out :) )
As for the use case, I see the KV component more like a step into integrating Dapr with the Workers ecosystem and enabling more interoperability with code that's running on Workers. Outside of users that are also using Workers for other things, I wouldn't otherwise recommend using KV as a general purpose state store however, unless users have some very specific needs.
Different story is for Queues. The Dapr integration in this case is, in my mind, a way to enable scaling Dapr apps so they can leverage Workers. The idea is that you have some work that you want to perform in a Worker, so you use Dapr to add that to a queue, and then a Worker would take it up. I think there's a lot of use for this.
For context, the Queues binding was the first thing I added (and you can see that in the name of the branch). I added the KV state store later because I wanted to create a "common infra" for Workers-based components, and adding KV was the forcing function for me to do that: after I created the internal package with the common infra, adding the KV state store was a very low-hanging fruit. I am envisioning that the "common infra" could then be used for a bunch of other things, including other components (maybe Cloudflare D1?) and even for the "compute" component I've proposed in dapr/proposals#16

We now have a (free) Cloudflare account, which is enough for the Conf test for the KV state store (but not for Queues).
I have updated the PR to add the test. They're passing when I run them locally, but because the test requires secrets, we won't know if it works here until the PR is merged in "master".

Different story is for Queues.

Agree, queues are less latency sensitive from the publisher perspective so it makes sense to have Dapr invoke queues that worker functions then consume.

but Dapr would make requests to the closest CF datacenter, so latency would not be worse than any other cloud state store we support (like hosted SQL databases) - actually, given how many datacenters Cloudflare has, I would expect latency to be among the best of the cloud-hosted services.

Latency within an AWS region is ~3ms, where latency from code (Dapr) deployed in an AWS region to a CF DC is ~50ms, so that's considerably slower writing to CF KV than to DynamoDB within the same region, for example.
In any case I don't see this as a showstopper for the component.

Update:

I have updated the PR to add the test. They're passing when I run them locally, but because the test requires secrets, we won't know if it works here until the PR is merged in "master".

In coordination with @berndverst we created a new branch in dapr/components-contrib (so not a fork) and run the conf tests there, where secrets are available. Tests are passing and the cleanup steps work too. All good :)

@ItalyPaleAle don't forget the docs issue please!

@berndverst done: https://github.com/dapr/docs/issues/3026


Style: Use different dark-mode color for desktop navbar.

Description of PR
SideNav(Desktop)/TopNav(Mobile) Color is darker than the background in light mode which is good. When I switch to dark mode complete page color get chaged to one color but the SideNav(Desktop)/TopNav(Mobile) color should be little dark.
Type of PR

[Yes] Bugfix
[No] New feature

Relevant Issues
Fixes #1416
Checklist

[Yes ] Compiles and passes lint tests
[Yes] Properly formatted
[Yes] Tested on desktop
[Yes] Tested on phone

Label
Image

Expected

Current Behaviour

Thanks, I approve :)

@jeremyphilemon @nitishk72 why you guys removed icons of demographics, faq etc...

The icons is hidden by this code and this is code was edited by someone else.

okay, may be maintainer found it bettter in that current way.


Incorrect Label for ArchiMate Shape in Technology Category

Preflight Checklist

[x ] I agree to follow the Code of Conduct that this project adheres to.
[x ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
A label issue has been identified in the ArchiMate shapes under the Technology category. Specifically, the label of the shape "Device" is wrong. It should be named "System Software"
To Reproduce
Steps to reproduce the behavior:

Open the ArchiMate shapes library.
Navigate to the Technology category.
Locate the shape with two overlapping circles (intended to represent "System Software" but it is named "Device").
Compare this shape with the rectangular "System Software" shape, which correctly displays the symbol in the top right corner.

Expected behavior
The two overlapping circles should be correctly labelled as "System Software" and not "Device" to match the symbol used in the rectangular "System Software" shape.
Screenshots
If applicable, add screenshots to help explain your problem.

draw.io version 24.7.7

Desktop (please complete the following information):

OS: iOS
Browser [Chrome]
Browser Version [Version 128.0.6613.85 ]

Smartphone (please complete the following information):

Device: [N/A]
OS: [N/A]
Browser [N/A]
Version [N/A]

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

yes

yes

Additional context
Add any other context about the problem here.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."


[ios] purchaseUpdatedListener trigger is not called after confirming the purchase

Description
Each time after a purchase, the purchase confirmation window opens again.
purchaseUpdatedListener trigger is not called after confirming the purchase.
Expected Behavior
After confirmation of purchase should be called purchaseUpdatedListener trigger
Screenshots
And so on forever!
Environment:
    "react": "18.2.0",
    "react-native": "0.73.0",
    "react-native-iap": "12.12.1",

react-native-iap:
react-native:
Platforms (iOS, simulator):

To Reproduce
Steps to reproduce the behavior:
Wrote everything according to the documentation:
https://react-native-iap.dooboolab.com/docs/guides/purchases

how to solve it ？

Also having this issue. Trying to find other fixes. Will report back if I find something that works.


Fix file ownership issues for runners

Following in the footsteps of https://github.com/webbertakken/unity-builder/pull/141
Current impl imports assets and generates artifacts as root:root, requiring chown to resolve file ownership errors.  Recommend adopting the elegant solution introduced in unity-builder Action, running container as correct user/group from the get-go.

Great idea! Accepting PRs.

This should be fixed by the latest release of the docker images.


Allow using variables in Config File Name

Using templates in this field, as {project-name}, would allow to use the package without storing files (with sensitive info) in the project, for those who work in a team.

Hi there, you can already achieve this in one of several ways (assuming you're looking to hide passwords).

Use public-private key authentication. This can be configured to use a default folder, or at the very least each user can update it to point to their key, thus not exposing sensitive information.

By extension, you could set the useAgent field to true to use the systems SSH agent, thus requiring no changes to .remote-sync.json by other team members. Assuming an agent is installed and the keys are added.

These next two assume you are using git for version control:

Not sure if this is a good idea, or even really works, but you could attempt to commit an initial template and then ignore it thereafter using git update-index --assume-unchanged <file>. Though I think this may only work on your local repo.

What I have done in the past, when it wasn't really worth the time setting up SSH (which isn't hard, I'm just lazy), is to commit a file called .remote-sync.json.template with all the configuration except for the username and password. Then I set a rule in .gitignore for my personalised remote-sync.json. Each user can then make a copy this file after checking out and safely add their own username and pass. This of course requires maintenance of two files, but really, it's generally a one-off setup with the odd addition to the watch list.


Unable to send slack notifications

@manireddyk creating a new issue for this error
I got the below error after I upgrade the schema

I can able to create incidents in default organization but its not sending the slack notifications

If I try to switch diff org, while trying to create incident its not even creating

thats y would like to revert it back, can you please share the db schema revert steps/how to revert with older version
Originally posted by @manireddyk in https://github.com/Netflix/dispatch/issues/2708#issuecomment-1318464448

I've opened #2712 which should address this error.


Mlflow docs patch

PR Checklist

[X] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes
Minor formatting pages to the docs/quickstart including the MLflow section.

Thanks @tdas - created #516


Prepare repo for cloudfoundry push

Added Procfile and manifest.yml for cloudfoundry deployment
There is a version of the application currently pushed to the dev environment here

Codecov Report

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

@@          Coverage Diff          @@
##           master     #7   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          43     43
=====================================
  Hits           43     43

Continue to review full report at Codecov.

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


[Bug] Side content tab underline breaks on browser window resize

[Bug] Side content tab underline breaks on browser window resize
UI-related bug.
Bug description
The SideContent component was updated in PR #740 to make use of BlueprintJS 3's Tabs component. This includes an addition of an animated blue underline that moves between tabs when tabs are switched.
When the side-content width is modified by dragging the central divider, the position of the underline decouples from that of the selected tab. However, upon releasing the <Resizable> divider, the underline recomputes its position and snaps back under the currently selected tab.
Additionally, all of

resizing the browser window,
minimising it from a maximised state, and
opening the browser's developer console (F12)

also triggers this decoupling, afterwhich the underline fails to recompute its position, remaining frozen in an incorrect position until the side-content width is modified again or a tab is selected.
This bug seems to occur in all available workspaces (assessment, grading, playground, mission editor).
Reproduction steps

Open the mock front-end (as of commit #796) in either Chrome or Firefox.
Proceed to the Playground.
Attempt to resize the central divider - this should demonstrate the decoupling of the animated underline.
Undock the browser window from a maximised state, then attempt to resize it by dragging its borders - this should demonstrate the frozen underline. Alternatively, press F12 to bring up the Developer console.

Development environment
Browser: Google Chrome Version 75.0.3770.142 (Official Build) (64-bit)
Browser: Firefox Quantum 68.0.1 (64-bit)
Last updated 3 Aug 2019, 00:15AM

Unfortunately this is a side effect of centering the tabs. The calculations for the position of the line come from the left margin
We could align the tabs to the left and it would solve this issue. Or we can disable the line altogether

Hmm not sure. The bug is real, but minor. The underline is nice, and the centering looks good.

Hmm not sure. The bug is real, but minor. The underline is nice, and the centering looks good.

I think we could live with this for now? It is a core issue/feature request with Blueprint, that it does not allow tabs to be centered. Currently it is done by overriding their CSS styles with our own

ok

OK, let's live with it.

Closed as the issue is resolved by #879.

Closed as the issue is resolved by #879.

Hi prof @martin-henz, any elaboration on steps to reproduce the issue?

This issue has gone away with the refactoring of the frontend. Let's close it.


Do not perform second call to config_with_absl

Avoid double-defined flags errors as reported in https://github.com/deepmind/launchpad/issues/5 by not executing logic in config_with_absl if it has been already called.

In our use case this function is currently called twice (from the user code and from one of the imported libraries). We could add a logic to not call this method for the seconds time in the liobrary, but basically it would be equivalent to this proposal. Maybe we could add a parameter "fail_on_double_call" and default to true?

Sounds good, thanks.


It would be nice to support a white background

Hi guys.
Just a quick note - it looks like MouseText was designed to mimic the Mac, and have a white background. You can see how this would fix several display quirks that Quinn complained about at Kfest. Anyway, great work! : - )
Exhibit A!
https://archive.org/details/Developers_Handbook_for_the_Apple_II_MouseText_Tool_Kit
(Don't worry, only the cover is French!)
Cheers,
Nick.

The color can't be controlled, and there aren't inverse MouseText characters in the ROM. The look it has is the only option. :)

Well, I was thinking just the window text contents, which can be white on black. But yeah, I suppose if you have MouseText on controls in the Window - which I now see is the case in the style guide in the doc I linked to - some of those controls can't be black on white.
Ticks for radio buttons and checkboxes would be ok, but Apple has flipped on the style in the guide and gone with white on black for the rest.
Still, if you haven't seen it you might want to look at the window "chrome" (title and scroll bars) on the original event driven Mouse Took Kit. Antoine pointed me to the disks:
http://www.brutaldeluxe.fr/documentation/forumdesdeveloppeurs.html
I'll paste an image below.
Cheers,
Nick.


List of assets without mandatory tags.

❔ Question
How do I make the mandatory tags reflect here instead of Application ? I have already changed the mandatory tags in the Admin console.

You need to update mandatory in the config service then it should reflect here.

Can you provide me the link to the doc on how to follow ?


Update docs Rubygems version to beta

Fixes #23292

@XhmikosR https://github.com/twbs/bootstrap/pull/23300

Sorry that is just wrong. Push here.

I went ahead and did it manually, but it would be nice if you got the gist of how things work for future contributions.


Migrate CI to travis.com

Codecov Report

Merging #146 into master will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #146      +/-   ##
==========================================
- Coverage    40.5%   40.42%   -0.08%
==========================================
  Files          36       37       +1
  Lines         958      977      +19
==========================================
+ Hits          388      395       +7
- Misses        570      582      +12

Impacted Files
Coverage Δ

src/e2e/node-lib/project/src/lib/polynomial.ts
36.84% <0%> (ø)

Continue to review full report at Codecov.

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


Allow putting custom certs without copying them

Is your feature request related to a problem? Please describe.
When certificates are injected externally there is no option to just place them to the final cert location since the playbook just copies them from the own cert/key location. When using own cert/key vars/location the playbook copies those certs.
When own certs are not provided and lets encrypt is disabled self signed certs will be created. This is fine but there are situations where one doesn't want local LE nor a self signed cert.
Describe the solution you'd like
An option that allows placing own certs in the final destination, hence 'disable self signed', 'disable letsencrypt', 'disable copy certs'.
Describe alternatives you've considered
Placing the actual certs twice into the system. But this doesn't make sense. Though it works currently.
# bbb_ssl_cert: "/etc/letsencrypt/live/{{ bbb_hostname }}/fullchain.pem"
# bbb_ssl_key: "/etc/letsencrypt/live/{{ bbb_hostname }}/privkey.pem"
bbb_ssl_cert: "{{ bbb_own_cert }}"
bbb_ssl_key: "{{ bbb_own_key }}"
# These two variables below can be used to copy a local cert/key file to the target
# which then is used.
# Need to set `bbb_letsencrypt_enable: false` then
bbb_own_cert: "/etc/ssl/acme/domain.pem"
bbb_own_key: "/etc/ssl/acme/domain.pem"

Additional context
Enough said I hope.
Thanks!

If I understood this issue right, please bear with me..
You want to use SSL/TLS but don't want to provide a Letsencrypt cert, own cert or self signed cert. Because certificates are injected externally.
In a sense like NGINX proxy for all BBB Server and only that proxy has the SSL/TLS Certs?
Could you please elaborate a bit more what the use-case is exactly?

Sorry for not giving a clear example.  I try to give more background to explain it.
The actual goal is to be able to define the certificates in the configuration that will be used without any change or further handling by the ansible role itself. No copy task, no csr, no Let's Encrypt task, etc. The cert must be on the host already before the Ansible playbook is run.
Providing the cert location with the "custom" vars won't work as it's working currently since those certs are only copied when the Ansible deploys them. Not practical with automatic cert renewal that does not directly run on the BBB node.
But how is the cert deployed?
Short version
There is another node generating and managing certificates that pushes new or renewed certificates to the target server and restarts required services. Hence the "externally injected".
Long version
This description may be out of scope for this project but it explains a bit more why it should be possible to allow certs being pushed from external sources.
LE ACME --> Cert Manager Server (creates and holds certs) --> Deployment Script --> Target Server --> Deployment Hook (Copy Cert/Restart service)

There is a central server that manages all let's encrypt certificates (cert manger). Those may be DNS based challenges or webbased, doesn't matter for this example.
The central server pushes new certificates to whatever server one configures on the cert manager. I can also restart services, do config checks, make cert backups and allows rollback in case of an unhandled error.
The cert manager also commits new certs and automatic generated deploy scripts into a private and locally hosted git repository (cert backup and history)
And more stuff
Using the awesome acme.sh
Using Ansible to deploy and manage it all

I am happy to provide a merge request since this shouldn't be to hard to implement. But for that I would need to know if the certs are being used anywhere else than in the nginx config and if the whole bbb role itself relies on the default location for the certs somewhere else or if it just uses the vars.
Is there a hard coded location for the certs when using the bbb installer script as fallback solution in case that one needs to use that? (I am not planning on doing so, but it might be used by someone else).
Thanks!

Closed due to inactivity

Well, I was waiting for more input and there was none. :-/

Hi @DerDanilo, this problem was addressed in another issue/PR though.
Look at #246


Add client settings for Redis to appsettings.json

It was really painful to try to reverse engineer what the configuration was supposed to look like for the Redis client. You can sort of find it in unit tests in the Connectors repo, but the samples should probably show it directly... so here it is.

@tillig,
Thanks for the feedback, I'll update all the Readmes with a link to the documentation which contains the information you were looking for...
Dave


Only create per-object webhooks for configured types

We currently create one almighty "object" webhook that, if broken, can effectively block every object operation in the entire cluster (minus critical system namespaces), even for objects that are not being monitored by HNC.
We should modify the HNCConfiguration reconciler to dynamically generate webhooks only for the objects types that are being propagated by HNC. Note that we need to insert new webhooks into the existing webhook config, since HNC's copy of cert-controller mentions the HNC webhook config by name, so creating a whole new webhook config won't work. But that should be pretty easy.
I'm guessing the best place to do this is to build a function similar to [syncObjectReconcilers](https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/281b24ff4c6d9fbbed59f6ac473b9c3cad79450f/internal/hncconfig/reconciler.go#L268), maybe called syncObjectWebhookConfigs or something like that.
I don't think this is a requirement for v1.0 but it would be nice if you felt like getting it in.
/assign @erikgb
/cc @rjbez17

/reopen

/remove-lifecycle rotten

Thanks for working on this :)
On Sun, May 28, 2023 at 9:11 AM Erik Godding Boye @.***>
wrote:

/remove-lifecycle rotten
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/152#issuecomment-1566136906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43PZF4FDE4MI6XP5Y4GMDXINFIFANCNFSM5P7EQRIQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey Folks,
Checking if this is still being worked on?

Sorry, been very busy but looking at that PR now

Hey Folks,
Checking if this is still being worked on?

Hey @omaratdgtl There are only a few things left in the PR to clean up and then we can get it merged. Unfortunately those working on the PR are quite busy. If you wanted to take over the PR here https://github.com/kubernetes-sigs/hierarchical-namespaces/pull/285 and clean up the last few items we can get it reviewed and merged!


Add a prompt to create new named zettels

This new feature would allow to create new Zettels with names.
The current way with telescope is not enough since the string doesn't have to match 100% for telescope to find a Zettel.
The user can call require('neuron.prompt').prompt_new_zettel() to see a small prompt asking for the new id of the file. If it exists it's opened and edited, else it's created and edited.

since we already use popup.nvim for telescope, can you use that implementation for the floating window so there is no code duplication.


cat-dog-dataset.sh in tools directory won't work as expected

Hello! I run the script, and it keep telling me:

./cat-dog-dataset.sh: line 34: /usr/bin/shuf: Argument list too long
cp: missing file operand
rename function not working : change JPEG to jpg.  I change the 'rename' command in the script to 'rename.ul', but it still won't work.

Has this script been throughly tested ?

It was developed and working on my Ubuntu 16.04 host system.  Are you using it on 18.04 or another OS?

From: Jackson Rong<EMAIL_ADDRESS>Sent: Friday, July 26, 2019 8:11:03 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [dusty-nv/jetson-inference] cat-dog-dataset.sh in tools directory won't work as expected (#374)
Hello! I run the script, and it keep telling me:

./cat-dog-dataset.sh: line 34: /usr/bin/shuf: Argument list too long
cp: missing file operand
rename function not working : change JPEG to jpg. I change the 'rename' command in the script to 'rename.ul', but it still won't work.

Has this script been throughly tested ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/374?email_source=notifications&email_token=ADVEGKYKVFV45O4VU3WQ7O3QBOHBPA5CNFSM4IHH5PKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HB2GDKQ, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADVEGK4XQGEVMHGEN6NNCJDQBOHBPANCNFSM4IHH5PKA.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Hello!
Thanks for the quick response.  I was running  the script on Jetson Nano development kit, Jetpack 4.2.1, believed to be Ubuntu 18.04.

Unfortunately I am away from my systems and can't test it at this time.  I do recall including a link in the source to where I found the command for randomly selecting the files.  If unable to debug, you might find it easier to create a new one or pull the files manually.

From: Jackson Rong<EMAIL_ADDRESS>Sent: Friday, July 26, 2019 8:25:34 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] cat-dog-dataset.sh in tools directory won't work as expected (#374)
Hello!
Thanks for the quick response. I was running the script on Jetson Nano development kit, Jetpack 4.2.1, believed to be Ubuntu 18.04.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/374?email_source=notifications&email_token=ADVEGK4FP6XMWIK4UWQS4ILQBOIX5A5CNFSM4IHH5PKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD257QJY#issuecomment-515635239, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADVEGK4WMOEUZNA32KCHYCDQBOIX5ANCNFSM4IHH5PKA.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Hello! Dustin,
   Thanks.  I do find another interesting thing when running the next script:checking every plants in the test directory. The script failed and I got the message: cd: ~/datasets/PlantCLEF_Subset: No such file or directory  cp: cannot stat 'test': No such file or directory
  It seems the bash shell can not recognize the '~' character. Maybe you are right, Jetson Nano Jetpack was a minimized Ubuntu 18.04, some function might be accidentically been removed.
Best Regards,Jackson Rong
在 2019年7月27日 星期六 上午08:29:32 [GMT+8]， Dustin<EMAIL_ADDRESS>寫道：

Unfortunately I am away from my systems and can't test it at this time. I do recall including a link in the source to where I found the command for randomly selecting the files. If unable to debug, you might find it easier to create a new one or pull the files manually.

From: Jackson Rong<EMAIL_ADDRESS>Sent: Friday, July 26, 2019 8:25:34 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] cat-dog-dataset.sh in tools directory won't work as expected (#374)
Hello!
Thanks for the quick response. I was running the script on Jetson Nano development kit, Jetpack 4.2.1, believed to be Ubuntu 18.04.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/374?email_source=notifications&email_token=ADVEGK4FP6XMWIK4UWQS4ILQBOIX5A5CNFSM4IHH5PKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD257QJY#issuecomment-515635239, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADVEGK4WMOEUZNA32KCHYCDQBOIX5ANCNFSM4IHH5PKA.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hello! @Jackson-Rong
Try to replace the '~' symbols with the $HOME variable (on Ubuntu it points to the home directory by default)
Then I found a possible error in labels path, where I need to remove the '../' in labels=$DATASET/../labels.txt $f $f
This is the new script:
`#!/bin/bash
NET="$HOME/jetson-inference/python/training/imagenet/plants_epoch_100"
DATASET="$HOME/datasets/PlantCLEF_Subset"
cd $DATASET
cp -r test test_output
FILES="$DATASET/test_output/*.jpg"
cd $DATA
for f in $FILES
do
echo "Processing $f"
imagenet-console --model=$NET/resnet18.onnx --input_blob=input_0 --output_blob=output_0 --labels=$DATASET/labels.txt $f $f
done`

Hello! @SimoGira ,
Thanks.  The new script works well.  Now only the cat-dog-dataset.sh still won't work.   It seems the redirection command caused some problem in cp function.


New version: MLJTuning v0.3.1

Registering package: MLJTuning
Repository: https://github.com/alan-turing-institute/MLJTuning.jl
Created by: @ablaom
Version: v0.3.1
Commit: c3ec5d5ba0773a12574b8589bb232144a0ea4663
Git reference: master
Release notes:

[x] (enhancement) Add RandomSearch tuning strategy (https://github.com/alan-turing-institute/MLJ.jl/issues/37 PR #30)

[noblock] I assume the CI fail is not something I can do anything about at my end?

Thanks @DilumAluthge ❤


[improvement][install.sh] fix the install Error "Command not found rmr"  & su…

[BUG][install.sh] fix the install Error "Command not found rmr"  & support ZooKeeper (3.4.6+)

CI exception is zk related dependency version detection exception. If zk-3.8 is used as the default option, there will be no problem with this dependency check.

CI exception is zk related dependency version detection exception. If zk-3.8 is used as the default option, there will be no problem with this dependency check.

Error:  org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2020-36569'
org.owasp.dependencycheck.data.update.exception.UpdateException: org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2020-36569'
CVE-2020-36569 Authentication is globally bypassed in githubcom/nanobox-io/golang-nanoauth between v000-20160722212129-ac0cc4484ad4 and v000-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token authentication complexity vector not available not available not available confidentiality integrity availability not available not availabl
No correlation seen

CI exception is zk related dependency version detection exception. If zk-3.8 is used as the default option, there will be no problem with this dependency check.

Error: org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2020-36569' org.owasp.dependencycheck.data.update.exception.UpdateException: org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2020-36569'
CVE-2020-36569 Authentication is globally bypassed in githubcom/nanobox-io/golang-nanoauth between v000-20160722212129-ac0cc4484ad4 and v000-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token authentication complexity vector not available not available not available confidentiality integrity availability not available not availabl
No correlation seen

I'm talking about this part 'https://github.com/apache/dolphinscheduler/actions/runs/3867927850/jobs/6597354529#step:7:1027',
OWASP detection is not mandatory to succeed.

Codecov Report

Merging #13163 (bee500a) into dev (1edee62) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #13163      +/-   ##
============================================
- Coverage     39.47%   39.43%   -0.05%
+ Complexity     4313     4309       -4
============================================
  Files          1083     1083
  Lines         40756    40710      -46
  Branches       4673     4655      -18
============================================
- Hits          16088    16052      -36
+ Misses        22880    22873       -7
+ Partials       1788     1785       -3

Impacted Files
Coverage Δ

...r/plugin/registry/zookeeper/ZookeeperRegistry.java
43.54% <0.00%> (-6.46%)
:arrow_down:

...eduler/api/dto/schedule/ScheduleCreateRequest.java
83.33% <0.00%> (-2.39%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...e/dolphinscheduler/service/queue/TaskPriority.java
51.31% <0.00%> (-1.25%)
:arrow_down:

...cheduler/plugin/alert/dingtalk/DingTalkSender.java
34.13% <0.00%> (-0.78%)
:arrow_down:

...pache/dolphinscheduler/common/utils/DateUtils.java
68.13% <0.00%> (-0.73%)
:arrow_down:

...inscheduler/plugin/registry/etcd/EtcdRegistry.java
50.34% <0.00%> (-0.69%)
:arrow_down:

...he/dolphinscheduler/plugin/task/java/JavaTask.java
58.50% <0.00%> (-0.69%)
:arrow_down:

...duler/plugin/storage/hdfs/HdfsStorageOperator.java
11.76% <0.00%> (-0.61%)
:arrow_down:

... and 25 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix joke ID caching

Joke ID caching currently doesn't quite work right (jokes with already cached IDs will be served again in under 10 re-requests).
Line that causes the issue

For all I know it should be fixed in 8bf9eaebf8992f267fda7126a4277c4ecb0baa6a


Typo "**Azure～Update 1 **"→"Azure～Update 1"

https://docs.microsoft.com/en-us/azure/devops/repos/git/commit-details?view=azure-devops

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Personal information

Coverage increased (+0.1%) to 66.066% when pulling 1beee2608bfbe935a34df68f7e960a972bef506b on personal-information into 453e024d6ad55851c4612baa15aceb0c18fb7bc2 on master.


ARROW-6645: [Python] Use common boundschecking function for checking dictionary indices when converting to pandas

The new function is faster and this means less code to maintain. I had originally suggested doing away with the boundschecking but unless we demonstrate that it really is a performance issue this should be good enough for now.

+1


(gh-642) Lookup Openstack credentials from ENV

Can one of the admins verify this patch?

@anodelman fixed


edited incorrect port

(from ms sql linux support) corrected port 51999 to 51000 for consistency throughout doc  (we dont list 51999 anywhere else on this page, we meant 51000)

@joshts0 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @joshts0! We appreciate you catching this!
#sign-off


Update Boost properties in CMakeLists.txt

See #102

Change looks reasonable @Thantalos ?

This change looks perfect. I already use it in a production environment. For me this fixes my problems and I hope it fixes problems others might have who use FMI4CPP in conjunction with Boost.
I'm happy to be in line with upstream again. Thank you.


fixed search issue due to e.preventdefault

Description of PR
Search box not working after visiting demographics page.
Fixed by adding specific key code for event.preventDefault. Behaves as expected in other cases.
Relevant Issues
Fixes #2200 #2032
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[ ] Tested on phone

Seems obsolete now that demographics has been deprecated


Implement output formatters

Many commands such as stubb images list cimg would benefit from the option of output formats. I'm thinking normal/human/table, JSON, and csv.

Closing due to stopping active dev on this repository.


How to call a method of the parent class instead?

I have an object instance of RevivePlayerConfirmationMenu and I would like to call IP2Menu.CloseMenu() instead of RevivePlayerConfirmationMenu.CloseMenu(). Is there a way to do this with 0.7.6?
// Assembly-CSharp
class Vengeance.Client.IP2Menu : Vengeance.Client.IP2Behaviour
{
    ...
    System.Void CloseMenu(); // 0x0163c760
    ...
}
// Assembly-CSharp
class Vengeance.Client.RevivePlayerConfirmationMenu : Vengeance.Client.IP2Menu
{
    ...
    System.Void CloseMenu(); // 0x00e96578
    ...
}

In the meantime, I am using the following code:
if (currentMenu.class.type.name == "Vengeance.Client.RevivePlayerConfirmationMenu"){
    var closeFunc = new NativeFunction(AssemblyCSharpImage.class("Vengeance.Client.IP2Menu").method("CloseMenu").virtualAddress, 'void', ['pointer'])
    closeFunc(currentMenu.handle)
}

lol, there is an option that this is an overloaded method, then there is no point in calling

lol, there is an option that this is an overloaded method, then there is no point in calling

What do you mean? CloseMenu() is not overloaded, its an overridden method.

I would like to skip over some code and call IP2Menu.CloseMenu().

you probably don't quite understand me. in version 0.7.0, the "base" property was removed and it seemed to me quite a logical solution, but you are now demonstrating the opposite situation. Having api 0.7.6, it is probably impossible to call this function, due to the fact that the number of parameters matches, the return type too. You can try calling via the frida api, that is, via NativeFunction, then you will have to process the parameters yourself.

Thanks @kruvcraft21 and @vfsfitvnm for you inputs!


feat: Onboard NASA wildfire

Description
Pipeline: past_week
Checklist
Note: Delete items below that aren't applicable to your pull request.

[x] Please merge this PR for me once it is approved.
[x] If this PR adds or edits a dataset or pipeline, it was reviewed and approved by the Google Cloud Public Datasets team beforehand.
[x] If this PR adds or edits a dataset or pipeline, I put all my code inside  datasets/nasa_wildfire and nothing outside of that directory.
[x] This PR is appropriately labeled.

@adlersantos @happyhuman @nlarge-google please review the code after the changes as per review comments


Not worked with jsonb column in Rails 4.2.4, Thanks.

# schema.rb
    t.jsonb    "delivery_info",         default: {}

  # order.rb

  # add return_logistics_image accessor method.
  store_accessor :delivery_info, :return_logistics_image
  mount_uploader :return_logistics_image, ImageUploader, serialize_to: :delivery_info

When create a new order object, exist following error:
NoMethodError (undefined method `return_logistics_image_changed?' for #<Order:0x007f1af7c68338>):
  app/models/order_transition.rb:7:in `block in <class:OrderTransition>'
  app/models/order.rb:182:in `transition_to!'
  app/models/order/buyer_action.rb:10:in `accept'
  app/models/concerns/set_order_action_callback.rb:13:in `public_send'
  app/models/concerns/set_order_action_callback.rb:13:in `block (2 levels) in method_added'
  app/models/concerns/set_order_action_callback.rb:12:in `block in method_added'
  app/api/api/buyer_action.rb:26:in `accept'
  app/controllers/orders_controller.rb:33:in `action!'
  app/controllers/buyer_orders_controller.rb:131:in `action!'

Sorry, NoMethodError (undefined method `return_logistics_image_changed?'  is fixed when restart server, But,  order.return_logistics_image = params[:return_logistics_image] is not worked in controller.

Can worked with jsonb, sorry!


HARVESTER: keep the param referer on the newly opened grafana page.

Summary
In the imported Harvester clusters, it is necessary to include the parameter referer when accessing the Grafana page. This parameter is required by the backend to identify the origin of the request from which cluster.

Occurred changes and/or fixed issues

https://github.com/harvester/harvester/issues/4087

Technical notes summary

Areas or cases that should be tested

https://github.com/harvester/harvester-installer/pull/512#issue-1759490781
Areas which could experience regressions

Screenshot/Video

@DaiYuzeng is this needed for 2.7.5?

Hi @mantis-toboggan-md ! I think it's not needed for 2.7.5, thanks! cc @WuJun2016


electron

sorry, my mistake.  I am working with electron and was searching for an issue I found.  I am having a problem with stopPolling() on an InEndpoint.  It looks like the 'end' event is never emitted.  I happen to be using Electron.


CUDA setup cleanup

This follows up on #873 (and #703/#527) to slightly clean up the CUDA setup and diagnostics code.
The last commit is the most interesting code-wise; #703/#527 added the sensible-enough behavior to sort CUDA version strings as sequences of integers, but since the retval was again re-sorted in evaluate_cuda_setup(), the sort was a no-op.
This removes the "dumber" sort from evaluate_cuda_setup().
Honestly, I think there's a lot more simplification possible in the CUDA setup and diagnostics code, but that's maybe for a future PR...

Amazing work, once more!


Change builtin's prototype property definitions to be writable

[edit: commit ate my # comments - adding back in this message]
When using the builtins previously we were creating all prototype
properties as writable:false.
Doing this on the Object prototype causes failures in existing
third-party code.
Due to strict mode, with builtins enabled, the following code
causes  an error to be thrown:-
var o = {}
o.ref = null
This breaks the principle of least surprise.
I originally ran into the problem when including the library in a
Meteor project.
To reproduce:
meteor create myproject
cd myproject
meteor npm install
meteor npm install --save rdf
meteor
// Then in a new window, go to server/main.js
// and add the following
var rdf = require('rdf')
rdf.setBuiltins()
console.log(rdf)
In the window running Meteor, there will be an exception from
deep inside Node, caused by the call to console.log().
The offending code was simply assigning some properties to an
object created by Object.create(null) - the root cause of the
problem is that strict mode causes an error to be thrown if
code tries to assign to an existing property that is not writable.
This change allows us to play nicely with others a little more
when using the builtins - we shouldn't block others when they
are simply using Object in a normal fashion.

What's the exact error you're getting?
What's the minimal test case?
As far as I can gather, the assignment is on the prototype, which shouldn't affect the ability to assign that property on any instance of an object. Something else is trying to assign a property like "l" or "tl" on Object itself, which is conflicting. If that's the case, changing "writable" to false isn't the solution.
The principle of least surprise is a double-edged sword like this.

The exact error is:-
W20161205-23:38:45.418(0)? (STDERR) /Users/jimsmart/.meteor/packages/meteor-tool/.1.4.2_3.1rd9djy++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20161205-23:38:45.419(0)? (STDERR) 						throw(ex);
W20161205-23:38:45.419(0)? (STDERR) 						^
W20161205-23:38:45.419(0)? (STDERR)
W20161205-23:38:45.420(0)? (STDERR) TypeError: Cannot assign to read only property 'ref' of [object Object]
W20161205-23:38:45.420(0)? (STDERR)     at arrayToHash (util.js:202:15)
W20161205-23:38:45.420(0)? (STDERR)     at formatValue (util.js:268:21)
W20161205-23:38:45.420(0)? (STDERR)     at inspect (util.js:143:10)
W20161205-23:38:45.421(0)? (STDERR)     at exports.format (util.js:24:24)
W20161205-23:38:45.421(0)? (STDERR)     at Console.log (console.js:39:34)
W20161205-23:38:45.421(0)? (STDERR)     at meteorInstall.server.main.js (server/main.js:8:9)
W20161205-23:38:45.422(0)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:181:9)
W20161205-23:38:45.422(0)? (STDERR)     at require (packages/modules-runtime.js:106:16)
W20161205-23:38:45.422(0)? (STDERR)     at /Users/jimsmart/workspace/jigsaw/.meteor/local/build/programs/server/app/app.js:160:1
W20161205-23:38:45.422(0)? (STDERR)     at /Users/jimsmart/workspace/jigsaw/.meteor/local/build/programs/server/boot.js:295:34
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.
Like I said, it's deep inside the version of Node bundled with Meteor. I traced it back to a simple function which can be seen in this file at line 255
https://coverage.nodejs.org/coverage-4aca347527fecab0/root/util.js.html
Steps to reproduce in a simple Meteor project are included in the original post, but this would probably do it (untested)
It's a hard-restriction in strict mode to throw when attempting to assign to a non-writable property - but this is not the case when not in strict mode.
'use strict';
var rdf = require('rdf')
rdf.setBuiltins()
var o = {}
r.ref = 'foo'
Changing writable to true stops Meteor from exploding. It also gives improved compatibility with any other third-party code.
Adding stuff to the prototype for Object isn't friendly unless those things are easily clobberable ;)

The code in question that throws the error just wants to assign some stuff to a map on a vanilla Object - it doesn't care that our .ref() method got clobbered.

I also tried changing 'configurable' to true, but that didn't fix the issue.
configurable:false blocks the prop from being further redefined by calls to Object.defineProperty - which might stop us playing nicely with other stuff - but we can deal with that if it ever arises.
But overrides to the Object prototype should play nicely - to the best of their abilities. Not only does it improve compatibility / not violate principle of least surprise, it makes also makes it easier to extend and monkey patch the library from external code.
Cheers

Another possible option would be to make it a user-configurable option to have hard/soft property extensions for the builtins.
Make setBuiltins() take optional parameters to select the required behaviour.
Possible configurations:-

As in current code: non-writable, non-configurable - In strict mode these are totally unclobberable, cannot be assigned to, and cannot be reconfigured by other's calls to Object.defineProperty. In strict mode, this setting can cause maximum breakage to/with third-party code, and at a very low-level (because folk expect objects to behave in a certain fashion). In effect this setting gives non-overridable priority to the object prototype modifications of the rdf library itself, at expensive of everyone else. With this configuration, if a third-party developer using the rdf library runs into problems, the exception would likely come from some other vendor's code (never underestimate the amount of casual map usage, eventually something somewhere will use a key of, say, 'ref' in some totally unrelated code), and the friction is perceived as being between the rdf library and another vendor's code. Either way, the developer isn't able to easily fix this, they just have to not use 'builtins' (big shame). But no silent bugs :)
'Softer' properties: writable, non-configurable - In strict mode, one regains the ability to use a vanilla object as a map with arbitrary keys, but objects still cannot be reconfigured by other's calls to object.defineProperty. The disadvantage to this setting is that, somewhere along the line, someone may clobber one of the properties of an object that is returned to- or used in interactions with- the rdf library itself. But this configuration lessens the chance of incompatibilities with libraries that are lower-down in the stack - any problems encountered are 'more likely' (no hard data, just seems logical from my experience) to be between the user's code and the rdf library (it's very unlikely that code lower-down in the stack will try to accidentally add a property to one of the library's objects, and then return it to us). Possibility of silent bugs. (Perhaps we should think of the different possible causes, and consequences? Can we even guess?)
Softest properties: writable and configurable - In strict mode, maps work as expected, plus third-party code can happily reconfigure arbitrary properties on a vanilla object. Obviously this configuration gives all of the above, plus a little bit more. But if some code deep down in some third-party stack wants to define its own property called 'ref' (via a call to Object.defineProperty) on a vanilla object, for any reason, they can. The disadvantage to this configuration is that now the rdf library's builtin stuff can be broken in more ways by third-party stuff. Possibility of a few more silent bugs than the previous option.

Hard/medium/soft? Other terms entirely? Expose more explicit but wordier configuration?
For a user of the library, having hard properties (and no option to configure that) is the worst position to be in. The breakage was deep inside third-party code, from normal usage of an object as a map, with some arbitrary keys in a function to hash an array. There's no way they'll fix that for me, they'll advise me not to override the prototype for Object. But the real kicker for me is that if the extensions to builtins used softer properties, then the problem I'd encountered would just go away - yet everything else would still work (for me, at least in this situation). Other options: don't use the extensions to builtins - or fork (with or without upstream pulls).
I like the builtins in this rdf library, and certainly would like to keep using them - and it'd be great if they were more compatible with the world at large.
— Thoughts?

@jimsmart Sorry for taking so long on this, I'll get some time to investigate this sometime this week. Thanks for your patience!

There's now an unsetBuiltins function that can remove the builtins.
If there's anything else I can do please feel free to open a new issue.


Citekey dependent on input method

Support log ID:
CKP8H2AQ-refs-euc
Expected behavior:
The Citekey should be independent of which input method for author names is used (single field/two fields).
Actual behavior:
The Citekey is dependent of which input method for author names is used.

Just got an email saying that I did not upload a support log ID even though I did...

CKP8H2AQ-refs-euc

That's a bug in the bot, I'll look into that, but wrt the issue itself, it's complicated - zotero itself makes this distinction for a reason, single-part name fields usually denote proper nouns with spaces, so it's not clear to me how I should detect it's actually a two-part name.
I don't have access to my computer right now and it'll be a bit before I do - what is the single-part name in question?

Okay, I see that Zotero makes a difference in the bib-file. But the output in biblatex is the same... Maybe the biblatex algorithm could be used to determine the CiteKey in order to avoid this problem?
Two-field export:
@incollection{bonjour_there_2013,
  title = {Is {{There A Priori Knowledge}}?},
  booktitle = {Contemporary {{Debates}} in {{Epistemology}}},
  author = {Bonjour, Laurence and Devit, Michael},
  editor = {Steup, Matthias and Turri, John and Sosa, Ernest and Steup, Professor of Philosophy Matthias and Turri, John and Sosa, Romeo Elton Professor in the Department of Philosophy Ernest},
  date = {2013},
  publisher = {{John Wiley \& Sons, Incorporated}},
  location = {{Somerset, UNITED STATES}},
  url = {http://ebookcentral.proquest.com/lib/sub/detail.action?docID=1245461},
  urldate = {2021-05-05},
  isbn = {978-1-118-32814-9},
  keywords = {Knowledge,Theory of.}
}

One-field export:
@incollection{laurencebonjour_there_2013,
  title = {Is {{There A Priori Knowledge}}?},
  booktitle = {Contemporary {{Debates}} in {{Epistemology}}},
  author = {{Laurence Bonjour} and Devit, Michael},
  editor = {Steup, Matthias and Turri, John and Sosa, Ernest and Steup, Professor of Philosophy Matthias and Turri, John and Sosa, Romeo Elton Professor in the Department of Philosophy Ernest},
  date = {2013},
  publisher = {{John Wiley \& Sons, Incorporated}},
  location = {{Somerset, UNITED STATES}},
  url = {http://ebookcentral.proquest.com/lib/sub/detail.action?docID=1245461},
  urldate = {2021-05-05},
  isbn = {978-1-118-32814-9},
  keywords = {Knowledge,Theory of.}
}

Also Zotero seems to figure out rather well how to switch from one-field to two-field input and vice versa. Maybe their algorithm could be used to determine a stable cite-key?

I'll take a peek, but why not just switch to the two-part name? My worry is dat some proper nouns are only meaningful as a whole, and then I'd be stacking kludge on kludge to tell them apart. The zotero field splitter has the benefit that you see the results and can edit them when they're not what you want, that interactivity does not exist for key generation.

Yes, there may be good reasons for sticking to how it works currently. I am not able to see the whole picture. All I experienced was that I entered a name in the one-field format which worked fine for biblatex but that I could not find the CiteKey as usual in the <lastname>_<title>_<year> format. Now I see that BetterBibTeX is set to [auth:lower]_[shorttitle1_1:lower]_[year]. And [auth:lower] apparently does not imply the guessing of the last name as zotero's one to two field switch does. Maybe a new field could be added such as [auth:lower_last] or so which does create the stable CiteKey as I expected? And maybe this could even become the new default (leaving people who are used to the [auth:lower] non-interfered with...)?

… but why not just switch to the two-part name?

Precisely. Not using two-part fields for conventional personal names will cause no end of trouble further down the line. Except for sheer luck, one will not get "correct" output from something like author = {{Laurence Bonjour} and Devit, Michael}. (If in doubt, try a few different biblatex styles, in particular author-year variants …) And I don’t see why BBT should go out of its way to facilitate such bad practices.

Thanks. That is helpful to know but does not solve the problem of wrong expectation. I don't think it's to be expected that a typical user of Zotero/Better BibTeX has this kind of knowledge. After all, these tools enable people to use BibTeX even without any knowledge of BibTeX files. But maybe Zotero and not Better BibTeX is to blame for my expectations then? There is a placeholder in the one-field input that reads "(full name)". Taking the typical meaning of "full name" in English, this creates the expectation that entering "Laurence Bonjour" is equivalent to entering "Bonjour" and "Laurence" in the two-field input which has the placeholders "first" and "last". And in fact it is in Zotero when switching between one- and two-field input. Maybe these are not equivalent. Then it would be good if Zotero would inform the user what they are for. Maybe by choosing a more accurate placeholder for the one-field input?

Fair enough. I realize "full name" could indeed be considered a bit of a misnomer. (The citeproc-js docs use "Institutional name" – would that be any clearer?)
And, surprisingly, there doesn’t seem to be any discussion of this in the Zotero docs at all.
You might want to take this up with the Zotero developers.

Keys also do not update unless the entry changes, or you manually refresh the key. (re)installation of BBT won't change/refresh any keys.

Now it is the last name of the author again. I know that it changed because it broke my document. I'll keep an eye on it. Maybe it has to do with me using Zotero on different computers. Maybe on one of them another format is used which creates some sort of conflict?

If you are generating keys one more than one system, and these systems have different patterns, and the generated bib files with these keys end up in the same place, then yes, they will differ, but that should not be surprising.