Implementation of LongestCommonPrefix in Python

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Implementation of python program to find the longest common prefix amongst the given list of strings. If there is no common prefix then returning 0.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
Longest-Common-Prefix #657
Fill up the DCP form
If you are a part of DCP 21, fill up this form after the PR is merged.
The links provided in the form will be checked thoroughly, if someone tries fooling around, strict actions will be taken against the individual.

I have added the description. Kindly, Please have a look into it.

I have added the description. Kindly, Please have a look into it.


Error when modify  presto.max-result-file-byte-size

Demand：
The result size of my query is more than 1GB。
Operation：
yanagishima version:12.0
presto version:0.211
I modified a property value  in conf/yanagishima.properties:
presto.max-result-file-byte-size=10737418240
the default  property value  is<PHONE_NUMBER>
Result：
The status of my query is failed
Error: java.NumberFormatException: For input string：“10737418240”
How should I do?  Is the property value cannot modified?

Unfortunately, Int.MaxValue(2147483647) is the maximum in the current implementation.
Please use a smaller value.

hi wyukawa ,
Thank you for your rapid  reply , You really did me a big favor .  I works .
Thank you very much again.

Hi wyukawa,
As in oracle tools we can download files of higher size, it takes rime to so so. Can we have this feature in Yanagishima where we can download records in some millions or more?
Or is it there , may be I am not aware of.
Need your help in getting UI tool on presto , to download large files.

i set value presto.max-result-file-byte-size=10737418240,if i need to change this values?

@wwwwwwchun Yes, you need to change the value.

thanks,when i change this value,the server is running

Thanks for your confirmation. Could you please close the issue https://github.com/yanagishima/yanagishima/issues/85 ?


Update LICENSE

Applying a license to a repository with an existing license

The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's LICENSE file to a short list of known licenses. Licensee also provides the Licenses API and gives us insight into how repositories on {% data variables.product.product_name %} are licensed. If your repository is using a license that isn't listed on the Choose a License website, you can request including the license.
If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity.
—
Reply to this email directly, view it on GitHub
https://github.com/IRAQ-hacker/hack-instagram/pull/8#event-9564117336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWLTJ7WONQ7CXXPLMCREB3LXL7WJXANCNFSM6AAAAAAZLOJ5FM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Remove warning about offline-plugin in dev

See https://github.com/mxstbr/react-boilerplate/issues/1025.

Coverage remained the same at 98.953% when pulling df38509964e3fbe44d8e3e0b1306ca947b967eed on sedubois:offline-nowarn into 18952bfdcc8ee32778934906ece1799b1daf3987 on mxstbr:dev.

Coverage remained the same at 98.953% when pulling ff3297801fa086bc1eb69488add6dc56be43b48c on sedubois:offline-nowarn into 5f088198e03b179bf41ece3e2689c3a0c67607cf on mxstbr:dev.

FYI, this fix goes away on npm run clean because it isn't in the app.js template


Trim redundant structs

SDL_GpuRect and SDL_GpuColor: can we just use the standard SDL things for this? (even if we typedef them so the typenames all look SDL_Gpu-ish). If not, this is not a dealbreaker.

https://github.com/thatcosmonaut/SDL/commit/4e23d1b9506e1af457807f52be1e1f2ec88118f5


Consolidate Users.cls & SObjectRepository.cls

Users.cls is essentially executing a query, caching the results and then adding some filter methods. The key difference is that the methods in SObjectRepository filter the query before execution; the methods in Users filters the results after a query is executed. This could cause some problems with trying to consolidate, but research needs to be done to see if they can be simplified & consolidated somehow.

This issue is no longer relevant - query caching is now supported for the query builders, and the User class was eliminated a long time ago and I don't have plans to add it back right now.


pytest doctest can't discover functions with @vectorize decorator

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

This problem seems very similar to the issue raised in #6308, which has already been fixed.
Here's my minimum working example:
"""
Test that all docstrings are the same:

>>> len({f.__doc__ for f in (a, b, c, d)})
1
"""
from numba import guvectorize, int64, njit, vectorize

def a():
    """>>> x = 1"""
    return 1

@njit
def b():
    """>>> x = 1"""
    return 1

@guvectorize([(int64[:], int64, int64[:])], "(n),()->(n)")
def c(x, y, res):
    """>>> x = 1"""
    for i in range(x.shape[0]):
        res[i] = x[i] + y

@vectorize([int64(int64, int64)])
def d(x, y):
    """>>> x = 1"""
    return x + y

When I run pytest I get the following results:
pytest -rs -sv --doctest-modules mwe.py
============================== test session starts ===============================
platform win32 -- Python 3.10.8, pytest-7.2.0, pluggy-1.0.0 -- C:\Users\MYUSER\Miniconda3\envs\fdm\python.exe
cachedir: .pytest_cache
rootdir: C:\Users\MYUSER\local_work\sketches\temp
plugins: cov-4.0.0
collected 4 items

mwe.py::mwe PASSED
mwe.py::mwe.a PASSED
mwe.py::mwe.b PASSED
mwe.py::mwe.c PASSED

=============================== 4 passed in 0.71s ================================

As all docstrings are the same, I would expect pytest to run a doctest for the function d, as it did for a, b, and c.

I think doctest will only pickup functions. The @vectorize decorator transforms functions into some callable objects.

Does any of the information / code in #5755 help here with this issue?


Make EmptyCriterion inherit from Criterion

Otherwise, type checkers are confused. Plus, it makes logical sense; my assumption is this omission was just an oversight.
I can work around this temporarily with BaseCriterion = Union[Criterion, EmptyCriterion], but that doesn't seem like the right long-term answer.

Coverage remained the same at 98.365% when pulling 9b0b71e905cde706c448489b24a9308876741d7c on myw:patch-1 into 0db485d5cb5c9be29b47f3b4e5e31d0e9eddccb5 on kayak:master.


Rename setup.sh to run.sh

"setup" can be misunderstood as build-related. Rename the script to avoid confusion. Also add a line of comment what the script does for readers who didn't read (or didn't remember) all of the README.

Thanks @findepi for the change.  I was thinking about the same same. What about a more descriptive name like deployToK8s.sh or startInK8s.sh? Another option is to move k8s related file into a separated directory, like k8s, so that we can keep the name simple as run.sh.

i would use "deploy" if the intent of the script is to deploy to some existing production grade k8s cluster.
i proposed run[.sh] because my understanding is that the intent of the script is to "just run locally" (simplest way possible), but i don't feel strongly about the script name. please tell me which name you'd prefer.

I don't have strong opinion on it. I agreed that deploy makes more sense.


Deploy production

Jira link
HOTT-442
What?
I have added/removed/altered:

[ ] Allow deployment to production on manual gate.

Why?
I am doing this because:

Implementing workflow defined on a team chat.

I think we should remove the hold on deploying to staging since we've got a filter for branches == master

We work a lot to make sure what we've merged has been reviewed, understood and tested and merged branches are highly stable

I think we should remove the hold on deploying to staging since we've got a filter for branches == master

Is that still in? Can't find it...

No it's not! Is my brain fart :)


Implement Variant of ResetPasswordConfirm that validates a token

This implements #45
If the user sets DJANGO_REST_PASSWORDRESET_ALLOW_TOKEN_VALIDATION = True in settings,
the password field becomes optional in ResetPasswordConfirm.  It will return a 200 if a valid token is provided without a password.
If DJANGO_REST_PASSWORDRESET_ALLOW_TOKEN_VALIDATION is not set, or is set to False, ResetPasswordConfirm behaves as it did before - returning a 400 if a password isn't given.
I also added a couple of tests for this and updated the README.

This looks good.

Not API breaking  :+1:
Minimum code changes  :+1:
Documentation/Readme Updated :+1:
Tests  :+1:

That's what a good PR looks like :)
Anyway, personally I would have gone for a separate endpoint, e.g.,  /validate_token/, but sending the token without a password at the same existing endpoint is fine for me too.
I'm going to leave this open for a week or so, as I would like to see some opinions on whether the implemented endpoint logic within this PR is considered as okay or not.

I agree with you about using separate endpoints. That way when the user gets a 200 from /confirm/, they know it means the password was updated and not just that the token is valid.

closed in favour of #60


release zip artifacts do not have intermediate folder

Description:
release zip artifacts do not have intermediate folder like jdk-11.0.18+10-jre. This is required for to publish update server

closing since this is fixed now


Is there some command line to export json compilation database directly

The function export json compilation database is very useful for me. Is there some command line I can use it directly to get the result through this project?

As far as I know there is no such command. I already looked into that when I wanted to automate some parts of out unit test pipeline.

Thanks for your updated info.


Update request: ollama 0.1.31 → 0.1.32

Package name: ollama
Latest released version: 0.1.32

Current version on the unstable channel: 0.1.31
Current version on the stable/release channel: 0.1.28

[X] Checked the nixpkgs pull requests

Notify maintainers

@abysssol

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

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

I tried updating ollama, but it appears to have a problem detecting rocm libraries (similar to #297081), so it'll probably take a while for me to figure it out. I don't want to update ollama if I know it'll break the rocm build.

This builds but I've not had a chance to test all platforms.
diff --git a/pkgs/tools/misc/ollama/default.nix b/pkgs/tools/misc/ollama/default.nix
index fdda6ba3f1e8..b1a69de252e9 100644
--- a/pkgs/tools/misc/ollama/default.nix
+++ b/pkgs/tools/misc/ollama/default.nix
@@ -30,22 +30,24 @@
 let
   pname = "ollama";
   # don't forget to invalidate all hashes each update
-  version = "0.1.31";
+  version = "0.1.33-rc5";

   src = fetchFromGitHub {
-    owner = "jmorganca";
+    owner = "ollama";
     repo = "ollama";
     rev = "v${version}";
-    hash = "sha256-Ip1zrhgGpeYo2zsN206/x+tcG/bmPJAq4zGatqsucaw=";
+    hash = "sha256-sP7ap9RQGR3rffe9Z3LKidoXeYVJMP6kZkpw81P3F50=";
     fetchSubmodules = true;
   };
-  vendorHash = "sha256-Lj7CBvS51RqF63c01cOCgY7BCQeCKGu794qzb/S80C0=";
+  vendorHash = "sha256-7x/n60WiKmwHFFuN0GfzkibUREvxAXNHcD3fHmihZvs=";
+  proxyVendor = true;
   # ollama's patches of llama.cpp's example server
   # `ollama/llm/generate/gen_common.sh` -> "apply temporary patches until fix is upstream"
   # each update, these patches should be synchronized with the contents of `ollama/llm/patches/`
   llamacppPatches = [
+    (preparePatch "02-clip-log.diff" "sha256-rMWbl3QgrPlhisTeHwD7EnGRJyOhLB4UeS7rqa0tdXM=")
     (preparePatch "03-load_exception.diff" "sha256-1DfNahFYYxqlx4E4pwMKQpL+XR0bibYnDFGt6dCL4TM=")
-    (preparePatch "04-locale.diff" "sha256-r5nHiP6yN/rQObRu2FZIPBKpKP9yByyZ6sSI2SKj6Do=")
+    (preparePatch "04-metal.diff" "sha256-Ne8J9R8NndUosSK0qoMvFfKNwqV5xhhce1nSoYrZo7Y=")
   ];

   preparePatch = patch: hash: fetchpatch {
@@ -163,17 +165,16 @@ goBuild ((lib.optionalAttrs enableRocm {
     ./disable-git.patch
   ] ++ llamacppPatches;
   postPatch = ''
-    # replace a hardcoded use of `g++` with `$CXX` so clang can be used on darwin
-    substituteInPlace llm/generate/gen_common.sh --replace-fail 'g++' '$CXX'
     # replace inaccurate version number with actual release version
     substituteInPlace version/version.go --replace-fail 0.0.0 '${version}'
   '';
   preBuild = ''
     # disable uses of `git`, since nix removes the git directory
-    export OLLAMA_SKIP_PATCHING=true
+    export OLLAMA_SKIP_PATCHING=false
     # build llama.cpp libraries for ollama
     go generate ./...
   '';
+
   postFixup = ''
     # the app doesn't appear functional at the moment, so hide it
     mv "$out/bin/app" "$out/bin/.ollama-app"
@@ -189,8 +190,8 @@ goBuild ((lib.optionalAttrs enableRocm {
   ldflags = [
     "-s"
     "-w"
-    "-X=github.com/jmorganca/ollama/version.Version=${version}"
-    "-X=github.com/jmorganca/ollama/server.mode=release"
+    "-X=github.com/ollama/ollama/version.Version=${version}"
+    "-X=github.com/ollama/ollama/server.mode=release"
   ];

   passthru.tests = {```

I tried updating ollama, but it appears to have a problem detecting rocm libraries (similar to #297081), so it'll probably take a while for me to figure it out. I don't want to update ollama if I know it'll break the rocm build.

Was it perhaps this? That's fixed now and merged in NixOS Unstable

Unfortunately, that was a different problem that broke ollama in an entirely separate way (#306654) (interestingly enough, both problems only affected rocm).
Apologies for being unable to keep ollama up to date, but it seems this might be beyond my abilities. I haven't entirely given up yet, but I'm not spending much time on this anymore.
Do you think it would be better to keep ollama up to date and just leave rocm broken?
Also, I updated my ollama flake to 0.1.32, if anyone wants to use that for now. https://github.com/abysssol/ollama-flake

@jonas-w did you perhaps mean to post this on #306375?

Can this be closed now that https://github.com/NixOS/nixpkgs/pull/312608 has been merged?

Thanks for your great work @abysssol! 🙏

@volfyd was a huge help. I doubt I would have gotten rocm working without him.
Thank you @volfyd!

@abysssol  & @volfyd thank you!


gt reports that SeaGOAT server is not running when in fact it does

I've followed a README and started a server in one tab, it indexed the repo and then outputs
Analyzing source code: 0it [00:00, ?it/s]
2023-09-20 20:37:42,312 Analyzed the minimum number of chunks needed to operate.
2023-09-20 20:37:42,312 Analyzed all chunks!

In another ttab running an example query fails
gt "Where are the numbers rounded"
The SeaGOAT server is not running. Please start the server using the following command:

seagoat-server start /home/git/repo

restarting the term session actually fixes this, not sure why

yeah, one thing to keep in mind is that each server is associated with a repo path, and you can run multiple servers.
It could be useful to show a warning that the server is not running for the current repo, but it is running for different repos maybe?

@GautierT it should have worked that way, but now server throws
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "/home/cwiz/anaconda3/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "/home/cwiz/anaconda3/lib/python3.11/threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 79, in _worker_function
    self._handle_task(context, task)
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 66, in _handle_task
    result = handler(context, *task.args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/task_queue.py", line 83, in handle_query
    results = context["seagoat_engine"].get_results(kwargs["limit_clue"])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 208, in get_results
    sorted(
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 212, in <lambda>
    + 0.3 * normalize_file_position(top_files[x.p

It seems another unrelated issue.

@GautierT it should have worked that way, but now server throws
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "/home/cwiz/anaconda3/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "/home/cwiz/anaconda3/lib/python3.11/threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 79, in _worker_function
    self._handle_task(context, task)
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/base_queue.py", line 66, in _handle_task
    result = handler(context, *task.args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/queue/task_queue.py", line 83, in handle_query
    results = context["seagoat_engine"].get_results(kwargs["limit_clue"])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 208, in get_results
    sorted(
  File "/home/cwiz/.local/pipx/venvs/seagoat/lib/python3.11/site-packages/seagoat/engine.py", line 212, in <lambda>
    + 0.3 * normalize_file_position(top_files[x.p

It seems another unrelated issue.

that one should be fixed now, please report it if you face it again with the latest version

Yes, it works now.


Leak in HttpPostRequestDecoder

Expected behavior
No leak report
Actual behavior
Leak report
myleakreport.txt
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
HttpPostRequestDecoder decoder = new HttpPostRequestDecoder(request);
This is line 47 which cause the leak.
Netty version
4.1.114.Final
JVM version (e.g. java -version)
openjdk 17.0.12 2024-07-16
OS version (e.g. uname -a)
Debian 12.7

Check if your top handler which receives the decoded frame is correctly releasing it

Yes, you are right, there is a strong reference from another handler.

I forgot to call decoder.destroy()


Direct Message Notifications

[ ] Send a direct message to the user when they have been warned.
[ ] Send a direct message to the user when they have been kicked.
[ ] Send a direct message to the user when they have been banned.
[ ] Send a direct message to the user when they have been temporarily muted.

const user = .users.get('');
user.send('');


Failed to load config "plugin:react-hooks/recommended" when setting EXTEND_ESLINT=true

Describe the bug
If I install eslint-plugin-react-hooks, then extend its recommended config file in my .eslintrc, and set EXTEND_ESLINT=true in .env, the terminal will complain "Failed to load config "plugin:react-hooks/recommended" to extend from."
Did you try recovering your dependencies?
Yes

Which terms did you search for in User Guide?
Failed to load config "plugin:react-hooks/recommended"

Environment

current version of create-react-app: 3.4.1
running from C:\Users\Zhi\AppData\Roaming\npm-cache_npx\6524\node_modules\create-react-app
System:
OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Binaries:
Node: 10.21.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - ~\scoop\apps\yarn\current\Yarn\bin\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^16.13.1 => 16.13.1
react-dom: ^16.13.1 => 16.13.1
react-scripts: 3.4.3 => 3.4.3
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

$ npx create-react-app foo && cd foo
$ yarn add --dev eslint-plugin-react-hooks
$ echo 'EXTEND_ESLINT=true' > .env
$ echo '{ "extends": ["plugin:react-hooks/recommended"] }' > .eslintrc.json
$ yarn start
The terminal complains Failed to load config "plugin:react-hooks/recommended" to extend from.
This message will show ONLY ONCE every time there's a new meaningful change to a .js file. To show it again, you could change some text in the render of App.js, for instance, add periods after the sentence:

Edit src/App.js and save to reload..

Edit src/App.js and save to reload...

Edit src/App.js and save to reload....

Every time the terminal complains:

Compiled with warnings.
./src/App.js
Failed to load config "plugin:react-hooks/recommended" to extend from.

Expected behavior

Shouldn't have this warning.
Note: the eslint rules are actually working as intended, meaning if there's a bad use of hooks, it'll catch it.
Actual behavior

See above for details.

Reproducible demo
This one would be much more convincing if you reproduce it yourself, the steps are super simple.

Hi @ZYinMD,
not quite sure about the loading problem itself, but react-hooks plugin is already installed in react-scripts@3 and shouldn't be added separately, instead you can just configure the rules yourself.

Hi @petetnt, thanks! To clarify, are both eslint-plugin-react and eslint-plugin-react-hooks installed with react-scripts? In other words, are the following comments correct?
// package.json
devDependencies: {
  "eslint-plugin-react": "^7.20.6", // not necessary
  "eslint-plugin-react-hooks": "^4.1.2", // not necessary
},
"eslintConfig": {
  "extends": [
    "eslint:recommended",
    "react-app",
    "plugin:react/recommended", // not necessary
    "plugin:react-hooks/recommended", // not necessary
  ],
}


Please help "No overload matches this call"

I'm using Quasar Framework. Tried to integrate this library but errors pops up.

@ruzlicali16 Please check now and close this issue.


Fix typo in Method_recommender_system.ipynb

indentity -> identity

Thank you for signalling this typo!
Though, as you might have noticed, this typo is in the ensmallen documentation of a method, and your edit is only patching the output of the jupyter. I have fixed the typo in the ensmallen method documentation at the root, and I will rerun the jupyter to obtain the updated and correct version.
Luca


Renderbox Was not laid out Bug

Exception caught by rendering library =====================================================
The following assertion was thrown during performLayout():
RenderBox was not laid out: RenderViewport#75734 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
'package:flutter/src/rendering/box.dart':
Failed assertion: line 1966 pos 12: 'hasSize'
// Code Here

StreamBuilder(
stream: FirebaseFirestore.instance.collection('Car').where("Myear", isEqualTo: 2019).snapshots(),
builder: (context, snapshot){
if(snapshot.connectionState == ConnectionState.active){
if(snapshot.hasData && snapshot.data !=null) {
return Expanded(child: ListView.builder(
itemCount: snapshot.data!.docs.length,
itemBuilder: (context, index) {
Map<String, dynamic> carData = snapshot.data!
.docs[index].data() as Map<String, dynamic>;
return Column(
children: [
ListTile(
leading: Text(carData["Myear"]),
                            ),

                          ],

                        );
                      }
                  ),
                  );
                }
                else{
                  return  Text("No data Found");
                }
              }
              else{
                return Text("OutSide The Context");

              }

            },

          ),

You have ListView -> Column -> ListTile. Column will always expand to fill available height, but ListView lets it have unlimited height. So your options to fix

Remove the Column
Set mainAxisSize: MainAxisSize.min on the Column

Can you include a full sample code-snippet that will reproduce the same error? More about minimal-reproducible-example

@sharifdujee
This seems like a code implementation issue rather than a bug in framework. Check https://github.com/flutter/flutter/issues/135920#issuecomment-1745610513 for solution or ask raise such issues in support channels like StackOverflow.
Closing from here.


"Object Oriented Programming: Iterate Over All Properties": description formatting typo

Describe your problem and - if possible - how to reproduce it
In the "Object Oriented Programming: Iterate Over All Properties" challenge, there is the following text in the description:

Here is how you add duck’s own properties to the array ownProps and prototype properties to the array prototypeProps:

"duck’s" should probably be "duck’s".
Add a Link to the page with the problem
https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/object-oriented-programming/iterate-over-all-properties
If possible, add a screenshot here

I would like to submit a pr for this, but I'm not sure how to do that now that curriculum is read-only. How should I make this change now?

In this repo there is another branch called next, it contains the curriculum. So you have to do the chnages in that branch and create a PR for that branch.

Thank you @Nirajn2311. I missed that. :) I'll go ahead and get the PR ready

Closing this issue as it got resolved in https://github.com/freeCodeCamp/freeCodeCamp/pull/18287


Support "markdown_ext" config

With markdown_ext supported, simiki will support internal links
and so on.
Closed #59
Compatible with markdown 2.6.x, avoid DeprecationWarning
Fixed #82
Signed-off-by: Xuanwo<EMAIL_ADDRESS>

@tankywoo I made a new pr for dev branch

Coverage decreased (-1.09%) to 73.981% when pulling 856bce3b991a011f8171fce73f9c6d6e94d245ac on Xuanwo:compatible-markdown into 34375cd6fd5657a6f9ab187870ad87b21c768bd8 on tankywoo:dev.

@Xuanwo Cool, thanks for your work. 👍


getOwnPropertyDescriptor return should allow undefined

Fixes #14923 (marked as "Accepting PRs", then fixed, then regressed) and #10904 (remarking on the regression)
getOwnPropertyDescriptor should return undefined in certain situations. This is documented here.
The original fix to 14923 was to the /lib/lib.es2015.proxy.d.ts file instead of /src/lib/lib.es2015.proxy.d.ts. I think this meant that the change got over-written by a generation script that ran as part of a later commit (see note here).

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

The previous fix in https://github.com/Microsoft/TypeScript/pull/10550 was done to an auto-generated file, and not the source. sorry for not catching this in the earlier change. this one should not go anywhere :).


WIP: Add podTrait to specify customPodTemplateSpec

This is still WIP. Currently the test is missing and it's only possible to specify the template from the file. Trait is applied only when IntegrationPhaseRunning state. I had to move util_content and util_sources under util/source to being able to use those also in the trait package.
Fixes #1657.

I've created custom method for merging resources based on map[string]interface{}. I still need to add more tests and sort out the configmaps.  If this will be accepted method could be moved to some *utils.go

@mmelko I've created #2096, that would be the corner stone place to store the PodSpec.

Now that we validated strategic merge patch is a good candidate, we should find the place where the pod template should be stored.
It may be worth exploring #2096 as a possible solution, embedding a PodSpec field inside the Integration resource, and adding an option to the kamel run CLI command, that would source the template into this field.

I update the PR also with adding PodTemplateSpec into integration spec (https://github.com/apache/camel-k/issues/2096). Pod trait is now enabled when template will be passed. That is possible with --pod-template param from CLI e.g kamel run integration.yaml --pod-template template.yaml.  Template is merged with the deployment one using kubernetes strategic merge.

Thanks a lot. Here are a couple of points:

I wonder if we should embed PodSpec instead of PodTemplateSpec. Annotations can already be passed via the Integration, and that would avoid opening the door to Finalizers, OwnerReferences and the like?
Should we filter out fields from the embedded  PodTemplateSpec / PodSpec? Are there any that do not functionally make sense embedding?
We have to add e2e tests covering the first use cases we have in mind, like:

Setting environment variables to the Integration container
Adding an init or side-car container
Setting TopologySpreadConstraints
...

That's a valid point. If we don't need to update/configure metadata for the template (which we probably don't) embedding only thePodSpec would be probably much more safe.
I guess it depends on what we want to allow to configure. I can imagine that we won't allow to modify for example the network properties...I need to investigate it more to understand how/where the pod is being created
Adding into my TODO..

I've created a custom PodTemplateSpec based on  v1core.PodTemplateSpec https://github.com/apache/camel-k/pull/1861/files#diff-df704f21201b6d30fe851b7bee054f77855f8b5720e77d93e8462fffb9c71cb3R225 to reduce the modification posibilities. I've also added simple e2e test to update ENV properties and add sidecar container.

@nicolaferraro @lburgazzoli would you be kind enough for a quick review now this is ready?

Thanks!


Possible to reposition the pagination bar?

Is it possible to reposition the pagination bar. So instead of it being at the bottom it's at the top?

Please see #59


⬆ Upgrade Quarkus 2.6.0.Final

I didn't check if versions were updated in the quarkus-bom. I'm upgrading the kotlin version and double-check all the versions we usually sync from the quarkus bom

mvn cq:sync-versions -N -e does not show any upgrades anymore, so we are good

yes I need to use this !! thanks


Restrict resizable directions

Hi,
First, great work, it looks really nice!
It could be nice to add the ability to restrict the resizability (is that a word?) of a widget to specific directions. For example, I want to be able to resize a widget only vertically (North & South).

Waow great, thanks!!

Hi there, thanks for your feedback! I've added an optional parameter and you can now restrict the directions like that: wg-resizable="{ directions: ['NW', 'NE', 'E', 'SW'] }". I'll update the README in the upcoming days.


initial data fetching issue react

Hello everyone, I'm a little bit stuck with a very simple problem. When I'm fetching my data from the API initially (when I first run my app), my "fetchedData" state doesn't receive any data, despite the fact that my fetch returns the data. It only happens during the initial run; all subsequent re-renders/component updates push the data into the state.
I would be very happy to hear some advice and ideas for better approaches.
Thank you all in advance.

It's because during the first render the state is initialized by the developer and after that API call is made which in turn re-renders the component and populate the state with data. In order to avoid such situation, store the data in a DB or local storage and fetch and initialize the state for first render. This way it remains populated even for the first time.


Merge mysql wordpress deployment files

Deployment files:

https://github.com/GoogleCloudPlatform/kubernetes-engine-samples/blob/master/cloudsql/mysql_wordpress_deployment.yaml
https://github.com/GoogleCloudPlatform/kubernetes-engine-samples/blob/master/wordpress-persistent-disks/wordpress_cloudsql.yaml.template

The above 2 files are almost identical except for the fact that the latter is linked to this tutorial and uses persistent disks.
Some consideration needs to happen to assess how to best merge these or keep only one of them somehow to avoid this duplication.

Please see #96 for more context.


Coord nan equal

Following the discovery #3282,
found that saving regridded cubes would fail because when a regridded dependency coordinate (orography in this case), coord contains NaNs, then "coord != coord".
Changes here implement a nan-tolerant comparison, so a coord containing NaNs does compare equal to an identical one (or itself).
Example of resulting save error :
>>> import iris
>>> import iris.tests.stock as istk
>>> cube = istk.realistic_4d()
>>> orog = cube.coord('surface_altitude').points
>>> orog[10,10] = np.nan
>>> cube.coord('surface_altitude').points = orog
>>> iris.save(cube, 'tmp.nc')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/io/__init__.py", line 408, in save
    saver(source, target, **kwargs)
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/fileformats/netcdf.py", line 2352, in save
    fill_value=fill_value)
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/fileformats/netcdf.py", line 1001, in write
    self._add_aux_factories(cube, cf_var_cube, dimension_names)
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/fileformats/netcdf.py", line 1248, in _add_aux_factories
    key, coord in six.iteritems(factory.dependencies)}
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/fileformats/netcdf.py", line 1248, in <dictcomp>
    key, coord in six.iteritems(factory.dependencies)}
  File "/home/h05/itpp/git/iris/iris_main/lib/iris/fileformats/netcdf.py", line 320, in name
    raise KeyError(msg)
KeyError: "Coordinate is not mapped, AuxCoord(array([[413.93686, 417.8168 , ...
 . . .
>>>

NOTE:
This might call into question whether cube-comparison should also be made nan-tolerant ??
It's harder, as

cube comparison involves a toleranced array difference (though really not a very solid one)
We might further extend array_equal to do toleranced comparison, but that seems over-extension

I think it's also less likely to cause internal Iris errors, like this one
- because Iris doesn't deal in collections of cubes very much (but collections of Coords, quite a lot)
So, I'm choosing to ignore this for now.

@pp-mo It looks like this PR is ready to go!
Do you mind rebasing and then it can be merged?

Rebased !

I am going to restarted all the travis ci jobs now that #3311 that fixes the tests is in.

Tests all pass :tada:
I'm going to merge this in (finally!)

@pp-mo

cube comparison involves a toleranced array difference (though really not a very solid one)

Not sure if it's relevant to your point, but the line in question will change if/when #3250 is merged.


Strobe Duration/delay issue 33UX264

I use the cameras exclusively with a strobe controlled by the GPIO. I originally did so without much issue as the strobe I previously set up had extremely little delay. I was able to achieve <100us exposure with the camera set at "strobe_exposure=1" As nice as it was it was not practical for my design.
I've designed something more practical but it has a slight delay in switching and requires more "on-time". I find it's not possible to sync the strobe whatsoever unless the exposure is set at 10200us. Ideally I should be able to set "strobe_exposure=0" and be able to sync the start of expose manually with the duration/delay controls but I've found several issues.

the strobe duration and strobe delay must match exactly or nothing happens.  Neither will change unless they are both set to the same setting. I need a good 7000us of on time for my opto to switch and my LEDs to hit full bright. Unfortunately this means I have 7000us of delay which the exposure must be set past to catch the strobe;

2)there should be some method of preempting the strobe output. I do not believe the trigger delays and such operate in framerate mode (trigger_mode=0), and even in trigger_mode it looks like the strobe_out follows the start of expose, not the trigger rise/fall.
Being able to set stobe_delay to a negative value or something  would be ideal since it would preempt the strobe output. Of course this would only work if the duration could be changed independently. So far the only way I've found to get anything going with the current strobe hardware is to invert the strobe_polarity (can expose at minimum. 25us), but then it would be on 90% of the time and probably overheat. Am I missing something or is the only way to get a useable strobe is to use the fastest switching method possible?

I don't quite understand what you are seeing there.
Could you
(a) tell us exactly what settings you are using (resolution, framerate, exposure time, all trigger settings, all strobe settings)
(b) try using the Windows software and check whether the behavior is the same?
(c) capture the trigger/strobe signals with an oscilloscope and show us what signals you get depending on the settings you configure in the camera?
The camera does not support a negative strobe delay right now. You could work around that by making the external trigger pulse as long as you need the strobe pulse to be, and directly use that pulse as your strobe signal. You would then set the trigger delay so that the exposure time starts when your light is on.

This is what happens with the cameras running in trigger-mode=0 and strobe_exposure=0:
I can have strobe delay and duration set to 0 and  I will receive no strobe output because my strobe needs longer on-times, . I can change either of those values and no actual change occurs, Listing the current values with either v4l2 or tcam will verify that the parameters have changed but the camera does not actually change the strobe behavior at all. It is only when I set both duration and delay to the exact same number that they both do actually change. I can set the duration long enough that it will turn my strobe on sufficiently, but the problem is that I have also had to set the delay the exact amount to make that work and I have now missed the exposure event unless the exposure is set for long times which defeats the purpose of setting strobe_exposure=0. I can set any strobe delay and duration value but the camera will not actually make the change unless they are both identical values. The camera will report back the value changes have occured, but the change only occurs in reality if they are both exactly the same value.
The changes I would have to make to the machine controlling the cameras to accomodate those tests would not at all be trivial. I also cannot use windows to test anything as my FPGA board Is controlled by the same Linux PC that the camera's work with. It will not work under windows. I designed the strobe to accommodate the open drain output from the camera whereas my FPGA outputs V+, making them incompatible.
I can try to capture the signals with a scope but it is visually obvious what happens. Is this not something you can verify on your side? I updated the firmwares from 78x to 94x (found on Github) with a windows PC and I will test that later.

with the new firmware (942) I am noticing a couple of new glitches as well as slightly different behavior with the above mentioned glitch.
As a test (for my hardware) I wired my original solid state relay that I previously used as my strobe switching device to see if I could improve the delay time since I cannot properly tune it out with software. This did get the exposure time back down to 250us but only if I use strobe_exposure=1 as I cannot tune the strobe duration and delay properly. I notice the issue with this firmware (possibly existed in previous firmware but I've only had to make these adjustments recently) that the cameras do not allow the strobe_exposure=1 setting to actually take effect when strobe_duration and strobe_delay are set to the same value unless it is 0. UVC reports the set values but the camera operates differently. This issue effects both of my cameras but I have opened another issue regarding only one of the cameras, a problem I've had for some time but have just realized the actual problem.

Here's my experience:
I would agree on using strobe_exposure=0 to tune the delay out of my strobe if the duration, delay were working, that would be ideal.
When I switch back to the strobe switching method that has very minimal delay I can achieve exposure times of 250us or better but only if using strobe_exposure=1. I understand what you are saying about strobe_exposure=1 setting the duration of the strobe pulse, but it seems to do so without effecting the cameras delay setting. The actual issue is that I cannot set the strobe_duration without matching the strobe_delay to it when strobe_exposure is set to 0. This renders the ability to increase the duration completely pointless. So strobe_exposure=0 is not likely to help me at all unless this issue gets resolved. At least using Strobe_exposure=1 allows me to have a good exposure as long as I have a fast strobe.
The systems major intention is to be used in trigger mode. I allow a framerate mode for certain uses. High framerates with 2 cameras at full resolution eat up alot of processor and bandwidth. I really have no use for high framerates. The cameras must take quick pictures of a fast moving object with a trigger sync, which they are capable of doing well when tuned properly. 5fps is faster than I trigger in trigger mode.

I can confirm there is definitely something wrong when trying to set strobe timing parameters in linux. I also get Strobe Duration/Delay only being changed when both have the same value.
I will investigate this.


Migrate from spf13/viper to koanf

yeeted lotta things
Revert "yeeted lotta things"
aaaaa

website:


Suggestion: Offer cloud services when a local cell is taking more than 2 minutes to run

Much larger versions of this are in discussions today.


fixed error caused by in-place operations

fixed error in backpropagation caused by in-place operations

Thank you for the contribution!


An unexpected error happened

Hi all,
I have a tendency to get "unexpected errors" from Grafane using the ClickHouse plugin. Here is the output I get.. Im not sure how to troubleshoot it exactly, so any guidance will be appriciated.
My enviroment is:
Grafana 7.0.3 (in docker)
clickhouse-grafana 2.0.1 plugin (manually dropped in the plugins folder)
ClickHouse server version 20.4.4 revision 54434 (also in docker)
here is the fault I get:
An unexpected error happened
Details
TypeError: Cannot read property 'length' of undefined

    in t
    in t
    in div
    in div
    in div
    in div
    in div
    in t
    in t
    in t
    in div
    in Ma
    in div
    in on
    in div
    in div
    in t
    in div
    in t
    in div
    in t
    in div
    in t
    in div
    in div
    in t
    in x
    in div
    in t
    in x
    in r
    in Unknown
    in t
    in Unknown
    in h
    in Unknown
    in Unknown
    in t
    in t
    in l

If I want to reproduce it I do this query:
select
  sum(bytes) as total,
  mysql_app_name
  FROM
  $table CLICKHOUSE
INNER JOIN (SELECT app_id_hex, app_name AS mysql_app_name FROM netflow.applications) MYSQL
ON CLICKHOUSE.appid = MYSQL.app_id_hex
WHERE $timeFilter AND hostname = '$hostname' AND (iface_out_desc = '$iface' OR iface_in_desc = '$iface')
GROUP BY mysql_app_name
ORDER BY total DESC

it looks like this when I put it into a table:

So it looks like the query is fine, but as soon as I change the "Visualization" to a Pie Chart, it crashes with the above fault.
Any ideas?

Hi Eugene (@Slach),
thanks a lot for looking into this problem.. I really appropriate it.
I can confirm that the Pie Chart now works, but there is one catch..
I have to select "Format as Time series", if I select "Format as Table" I still get an error
This is what I mean: "Time series" works, "Table" no joy..

to be sure that I was using the latest master, I forked the repo changed the version to 2.0.2-hyberdk and used that package.

Anyways, this is the error that I am getting (looks like the same as before):
An unexpected error happened
Details
TypeError: Cannot read property 'length' of undefined

    in t
    in t
    in div
    in div
    in div
    in div
    in div
    in t
    in t
    in t
    in div
    in Ma
    in div
    in on
    in div
    in div
    in t
    in div
    in t
    in div
    in t
    in div
    in t
    in div
    in div
    in t
    in x
    in div
    in t
    in x
    in r
    in Unknown
    in t
    in Unknown
    in h
    in Unknown
    in Unknown
    in t
    in t
    in l

Its not critical as the other works, but it still annoying as if you by mistake select the wrong one the dashboard crashes and you have lost all your changes since last save..
Again thanks a lot for looking to my problem!
Esben

@hyberdk could you explain how you make PIE Chart visualization? I don't see PIE chart in default grafana7 visualization plugin list
I also tried to reproduce query look like yours
and currently last master works OK

@hyberdk also the same query from your issue in table format looks good:

I catch it

  grafana:
    image: grafana/grafana:latest
    environment:
      - GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS=vertamedia-clickhouse-datasource
      - GF_INSTALL_PLUGINS=grafana-piechart-panel 1.5.0

so error happens inside Pie Chart plugin
look like PieChart can't work with "table" format
see https://github.com/grafana/piechart-panel/issues/113

Awesome, thanks for investigating this!


Simplify IBMi class

Changes
Introducing new classes to help simplify logic in IBMiSettings class.
How to test this PR
Examples:

Run the test cases
Expand view A and right click on the node
Run 'Execute Thing' from the command palette

Checklist

[* ] have tested my change
[ ] have created one or more test cases
[ ] updated relevant documentation
[ ] Remove any/all console.logs I added
[* ] have added myself to the contributors' list in CONTRIBUTING.md

Okay sending for another review.

@krethan I should give a warning that there is another PR being worked on which separates the UI logic from the backend logic in the IBM i class. That may have to come before this.

Thanks for the heads up


Clusters 009a and 0 b06

This is working PR for shared coded with my team.
Please dont review !!!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing this: no CI passes, description is unclear (it does not say what each clusters are or what the intent of the PR is) and it specifically says "for sharing only".
For sharing, please share branches or PRs in personal forks.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-23-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1369

Questions ?
Please refer to the Backport tool documentation


feature: mailgun eu region api support

I'm new to Node.js, so this needs some review. It's supposed to tackle #274.
I added an apiHost option that sets the host option in the mailgun object constructor.
The npm test unfortunately fails at a line I didn't even touch:
\lib\Staticman.js:508:3: Expected an assignment or function call and instead saw an expression.
line in question: this._initialiseGit
I touched:

config.js
lib/Staticman.js
siteConfig.js
staticman.sample.yml

@OlafHaag that test was also failing for me when I cloned the repo. Ideally builds with failing tests would never get approved and would never make it into master so that you could tell that it was your change that caused the test failure. That would tell you that either your change is incorrect, or the unit test is incorrect. In either case it would require further debugging.
Since I can't speak to the state of the master branch's tests, the easiest way test this is to use git to revert your commits and then run the tests so you can see if that test was failing before you made your changes.

It's really a PITA that this was not merged. I also configured my domain to be in the EU - because I am there and it is nowhere documented that you must use a US domain.

@MichaelRumpler The changes included in this PR are rather straight-forward. You could just fork the project and make the changes to your fork. Or re-create the PR against the current codebase.

Yes, I did that and it worked. Still, it should be merged into the real staticman and not just my fork.


Typo in website

Should say Min. Special chars
It says Min. Specia chars

Thanks for pointing out.


Add module-info via moditech plugin, compile to java 8

Removes Automatic-Module-Name manifest entry and replaces it with module-info via multi-version jar

Since #19 is now closed, I want to make sure to emphasize the order to merge and release this PR before #21:

We would then get the maintainers to release that before we then merge this second PR which bumps to Java ~9~ 11 and get the maintainers to release again a second time.

I believe it is important to have a Java 8 compatible modularized version of this library, as many downstream libs still target Java 8.

Are we sure, we don't need to set Multi-Release: true in the jar manifest? Is the module-info.class placed in the jar's root and still ignored by JREs < 9?

Pretty sure we don't have to set the Multi-Release attribute, because it is not a MR JAR (there's no META-INF/versions). The module-info.class is present in the root of the JAR and is version 53 (Java 9). All other classes are version 52 (Java 8).
To the best of my knowledge, Java 8 has no reason to load the module-info.class class file, if only because its name is not denotable in the language. (You may be able to handcraft some bytecode that refers to a class with the name module-info, and I have no idea what would happen then :-) )

(You may be able to handcraft some bytecode that refers to a class with the name module-info, and I have no idea what would happen then :-) )

One should not access it, however some build tools seem to be too fancy to adhere specs: See https://github.com/google/guava/issues/2970#issuecomment-337618636 (and the following discussion)

One should not access it, however ...

I note that Jackson has module-info without MR Jar so I suspect problems with this approach have to be very rare indeed - but that all said, the more conservative and safe approach is to modify this PR back to use Multi-release Jar and I'm happy to do that, it's a one line change to this PR.
So, shall we go a touch more conservative and use MR Jar?

Frankly, if there's a tool that finds and uses /module-info.class, that tool will most likely also find and use /META-INF/versions/9/module-info.class. I just don't see the need to make this a MR JAR.

That said, there's nothing wrong with this approach, and there's no extra complexity in the build, so if this is what everyone wants, I'm fine with it too.

Frankly, if there's a tool that finds and uses /module-info.class, that tool will most likely also find and use /META-INF/versions/9/module-info.class. I just don't see the need to make this a MR JAR.

You're probably right. Also, Jackson (as mentioned above) strongly indicates that in the meantime most tools should be fixed.
But if MR-Jars were even slightly more forgiving, it might make a difference for other library vendors, that would otherwise not dare to update injection-api out of fear of breaking something downstream.

Maybe just looking for approvals then @Emily-Jiang  @overheadhunter  @Ladicek  ?

Pretty sure we don't have to set the Multi-Release attribute, because it is not a MR JAR (there's no META-INF/versions). The module-info.class is present in the root of the JAR and is version 53 (Java 9). All other classes are version 52 (Java 8).
To the best of my knowledge, Java 8 has no reason to load the module-info.class class file, if only because its name is not denotable in the language. (You may be able to handcraft some bytecode that refers to a class with the name module-info, and I have no idea what would happen then :-) )

IIRC, the file structure is pretty much MR jar layout. I found it is confusing not to state it is a MR jar but place module-info.class using the MR layout (my earlier comment reflected my confusion since I thought it was not a MR jar). I am not sure the module-info.class can be easily loaded by Java 9+ at all. I think it is safer to set as a MR jar and be done with it.

This PR originally produced a MR JAR. Then it wasn't a MR JAR (which is when I approved and also wrote that comment), and now it is a MR JAR again.

I think it is safer to set as a MR jar and be done with it.

Hi @Emily-Jiang , as @Ladicek has pointed out this produces a MR jar.
To explain that a little more, this is compiling to Java 8 bytecode. We can't use the JDK8 javac to compile module-info.java obviously. Instead this uses the moditect-maven-plugin to compile module-info.java and put it into the jar creating a MR jar. The <jvmVersion>9</jvmVersion> configuration option is what specifies to make it a MR jar with the result that the jar contains /META-INF/versions/9/module-info.class  (Multi-release jar containing java 9 bytecode for module-info.class).
Personally, I have used the moditect-maven-plugin a lot myself as it's a really nice and simple way to add proper module-info to projects that still need to compile to java 8. Let me know if you have any questions.
Thanks, Rob.

May I ask to update the title of this PR, please? Moditech seems to be very different company, probably not related to the plugin used.

@pzygielo  done, title updated.

I think it is safer to set as a MR jar and be done with it.

Hi @Emily-Jiang , as @Ladicek has pointed out this produces a MR jar.
To explain that a little more, this is compiling to Java 8 bytecode. We can't use the JDK8 javac to compile module-info.java obviously. Instead this uses the moditect-maven-plugin to compile module-info.java and put it into the jar creating a MR jar. The <jvmVersion>9</jvmVersion> configuration option is what specifies to make it a MR jar with the result that the jar contains /META-INF/versions/9/module-info.class (Multi-release jar containing java 9 bytecode for module-info.class).
Personally, I have used the moditect-maven-plugin a lot myself as it's a really nice and simple way to add proper module-info to projects that still need to compile to java 8. Let me know if you have any questions.
Thanks, Rob.

Thank you @rbygrave for your detail explanation! Let me relay to see whether I understood this correctly. You said it is not a MR jar because there is no META-INF/module-info.class and we only have /META-INF/versions/9/module-info.class. It does not need to be marked as a MR jar as there is no duplicated module-info.class. For Java 9+, JVM should find module-info.class despite it is under META-INF/versions/9/module-info.class. If I understood correctly, this does make sense.

we only have /META-INF/versions/9/module-info.class.

There is only one module-info.class in the jar and yes it is located at /META-INF/versions/9/module-info.class

It does not need to be marked as a MR jar

In the resulting /META-INF/MANIFEST.MF it contains the Multi-Release: true entry.  So I think it is more accurate to say that it IS marked as a MR jar. It is a MR jar with the manifest containing Multi-Release: true plus it has /META-INF/versions/9/module-info.class
That is, if we pull this branch and mvn clean package and look at the resulting target/jakarta.inject-api-2.0.1-SNAPSHOT.jar we see that the manifest is as expected with the Multi-Release: true entry plus we see the /META-INF/versions/9/module-info.class

as there is no duplicated module-info.class.

Correct, there is no  duplicated module-info class @Emily-Jiang

we only have /META-INF/versions/9/module-info.class.

There is only one module-info.class in the jar and yes it is located at /META-INF/versions/9/module-info.class

It does not need to be marked as a MR jar

In the resulting /META-INF/MANIFEST.MF it contains the Multi-Release: true entry. So I think it is more accurate to say that it IS marked as a MR jar.  Then I read @Ladicek 's comments , which he hinted he approved with a non-MR jar approach. I might completely misunderstood what it meant. However, I am happy with the final approach.

That is, if we pull this branch and mvn clean package and look at the resulting target/jakarta.inject-api-2.0.1-SNAPSHOT.jar we see that the manifest is as expected with the Multi-Release: true entry plus we see the /META-INF/versions/9/module-info.class

as there is no duplicated module-info.class.

Correct, there is no duplicated module-info class @Emily-Jiang

In summary, I am happy with the fact of being a MR jar and the entry of /META-INF/versions/9/module-info.class as I think this class will be loaded by Java 9+ with that marker.

Hi Scott @starksm64 , I am looking to find out what the next step is to get this PR merged (and ideally release 2.0.1 with a module-info to maven central). I see you have merged commits so perhaps you can help me / let me know what the next step is?
Thanks, Rob.

Hi @Cousjava I am trying to determine the next step to getting this PR merged. Are you able to help?
Thanks, Rob.

I'm a committer on this project and will merge this PR.

FYI: Adding cross reference to issue https://github.com/eclipse-ee4j/injection-api/issues/17


Primer is hanging in typeshed's CI

See e.g. https://github.com/python/typeshed/pull/11078
The issue is with a project in shard 0. I cancelled the shard after 25 minutes on the first run, and then re-ran it. I cancelled it after 15 minutes on the rerun.

Should the project just be deleted? Commented out for now? Should we change the way we try to clone the projects?
I await the opinions of mypy_primer maintainers :)

Thanks for investigating! I just removed it for now in https://github.com/hauntsaninja/mypy_primer/commit/d1263e0c5f4552c13c0449b62ba0dc8e4167a0bd , can figure out if we should change clone or something later

Thanks very much!


Update softhouse.json

Changed "addedPeer"

can you make sure you have the latest pulled from github and resubmit this pr please


Fixes #2099: Prestissimo not needed with Composer 2.x

Fixes #2099
I don't know if there is a more sophisticated way to deal with this, but by default, Composer 2.x is installed on new projects, and this solution got me past the provisioning error. Composer 2 has hirak/prestissimo 's parallel download feature built in now.

Quite correct! I'll merge this as CI builds started failing here as well. Thanks!


Prevent circular load.properties

fixes #177

LGTM. I think we get this in before #176

@rbygrave please review when you get time


Implement multi-server fallbacks for libbitcoin

@cpacia

This depends on another pull request going through first:
https://github.com/OpenBazaar/python-libbitcoinclient/pull/3


refactor(Algebra/Star/StarAlgHom): mk_coe and coe_mk in StarAlgHom

Add mk_coe and coe_mk results to Algebra/Star/StarAlgHom in analogy with RingEquiv.

Sorry this has been sitting.
bors merge


Added Level Zero link

Added this link with Alison. She says you'll (i.e. Rob) hook up the link.

I copied another ai-tab as a template


Any flag to run the whole model on CPU?

I'm trying to test on CPU, but I've had to make lots of changes to the code. (Remove DataParallel, .cuda() etc.) Is there a flag that can allow me to easily switch between CPU and GPU?

Were you able to do this?


Query/possible bug with multiple arguments

If I invoke my build with the following arguments:
"$(SolutionDir)cake/cake.exe" build.cake -verbosity=diagnostic -root="$(SolutionDir)" -scomDllConfiguration="$(ConfigurationName)"
I have problems using the argument 'root' since it ends up as a string with the actual value of:
C:\dev\squaredup-custbuild\v1" -scomDllConfiguration=Release
Where C:\dev\squaredup-custbuild\v1 is the actual value I passed into 'root' and the remainder is the other argument.
What is the correct way to pass both of these arguments without ending up with an amalgamation of their values?
If the issue here is caused by quotes, what can I do to solve it? (Removing the quotes is not an option: This invocation can use absolute paths which contain spaces)
EDIT:
Interestingly, if I only pass root (-root="$(SolutionDir)") the value is correct, but has an additional quote on the end, leading to 'illegal character in path'.
If I omit the last quote, everything actually works fine (!!) (-root="$(SolutionDir)). Since I'm invoking cake from VS2013 post-build events I'm not sure if I'm looking at a cake bug here, or a VS bug?

OK, after testing this out directly from the command line, it's definitely Visual Studio being crap -_-
(http://stackoverflow.com/questions/11587394/how-to-put-double-quotes-in-vs2010-post-build-step#comment36704367_11620677)
You can close this issue - apologies, I had no reason VS was incapable of parsing double quotes properly

I see. But more importantly, did you get it to work?
If quotes are a problem, would perhaps wrapping the task execution in a custom MSBuild task solve it?

Yes, although back to possibly being a cake bug :-1:
This command works:
"C:\dev\squaredup-custbuild\v1\cake/cake.exe" -verbosity=diagnostic -squaredUpRoot="C:\dev\squaredup-custbuild\v1" -scomDllConfiguration="Release"
But this does not:
"C:\dev\squaredup-custbuild\v1\cake/cake.exe" -verbosity=diagnostic -squaredUpRoot="C:\dev\squaredup-custbuild\v1\" -scomDllConfiguration="Release"
Note the trailing slash on "C:\dev\squaredup-custbuild\v1\ for the non-working version
Is there something inside cake which is reinterpreting the " as the escape sequence for double quote?
(Note that the reason I'm getting the trailing slash is because that's what VS provides with ${SolutionDir})

Hi @DavidR91,
I tested the following script
var squaredUpRoot        = Argument<string>("squaredUpRoot", "Argument missing");
var scomDllConfiguration = Argument<string>("scomDllConfiguration", "Argument missing");

Information("squaredUpRoot: {0}", squaredUpRoot);
Information("scomDllConfiguration: {0}", scomDllConfiguration);

called like this from PowerShell
Cake.exe -verbosity=diagnostic -squaredUpRoot="C:\dev\squaredup-custbuild\v1\" -scomDllConfiguration="Release"

it outputs (truncated diagnostics)
Compiling build script...
squaredUpRoot: C:\dev\squaredup-custbuild\v1\
scomDllConfiguration: Release

Calling from like this from PowerShell
Cake.exe -verbosity=diagnostic -squaredUpRoot="C:\dev\squaredup-custbuild\v1" -scomDllConfiguration="Release"

it outputs (truncated diagnostics)
Compiling build script...
squaredUpRoot: C:\dev\squaredup-custbuild\v1
scomDllConfiguration: Release

Added as post build step
"$(SolutionDir)cake/cake.exe" build.cake -verbosity=diagnostic -squaredUpRoot="$(SolutionDir)" -scomDllConfiguration="$(ConfigurationName)"

and got scomDllConfiguration missing.
Added an this to the script
Information("CommandLine: {0}", System.Environment.CommandLine);

In visual studio output was:
CommandLine: "C:\temp\priv\caketest\cake/cake.exe"  build.cake -verbosity=diagnostic -squaredUpRoot="C:\temp\priv\caketest\" -scomDllConfiguration="Debug"

ran same code in PowerShell and it seems to change commandline
CommandLine: "C:\temp\priv\caketest\cake\cake.exe"  build.cake -verbosity=diagnostic -squaredUpRoot=C:\temp\priv\caketest\ -scomDllConfiguration=Debug

so I changed to command cmd.exe and got this
CommandLine: "C:\temp\priv\caketest\cake/cake.exe"   build.cake -verbosity=diagnostic -squaredUpRoot="C:\temp\priv\caketest\" -scomDllConfiguration="Debug"
squaredUpRoot: C:\temp\priv\caketest" -scomDllConfiguration=Debug
scomDllConfiguration: Argument missing

I would agree this is an issue with Cake and will look into it.
meanwhile what you could to as a work around would be to change postbuild to add a space after $(SolutionDir)
"$(SolutionDir)cake/cake.exe" build.cake -verbosity=diagnostic -squaredUpRoot="$(SolutionDir) " -scomDllConfiguration="$(ConfigurationName)"

And just do a
var squaredUpRoot =  HasArgument("squaredUpRoot") ? Argument<string>("squaredUpRoot").TrimEnd() : "Argument missing";

We will take a look at the argument parsing an post back here when it's fixed.

Interesting it's an .Net console "issue" they are doing something smart;)
args
	[0]	"build.cake"                                                            string
	[1]	"-verbosity=diagnostic"                                                 string
	[2]	"-squaredUpRoot=C:\\temp\\priv\\caketest\" -scomDllConfiguration=Debug" string

System.Environment.CommandLine
        "\"C:\\temp\\dev\\github\\cake\\src\\Cake\\bin\\Debug\\Cake.vshost.exe\" \"build.cake\" -verbosity=diagnostic -squaredUpRoot=\"C:\\temp\\priv\\caketest\\\" -scomDllConfiguration=\"Debug\""	string

Yeah for the time being rather than adding a space, I've been adding an additional \
i.e.:
-squaredUpRoot="$(SolutionDir)\"
so I end up getting stuff like this:
-squaredUpRoot="C:\Program Files (x86)\Jenkins\jobs\Website v2.0\workspace\v1\\"
This seems to work, so I'm presuming that's because it ends up evaluating \ to be an escaped \ before it considers " ?
But yeah, seems to be a minor issue since I can workaround it for the time being.

@DavidR91 ah, what would work as the msbuild format is xml :+1:
But I'm working on an solution, will post back here as soon as I have pushed some bits.

And thanks for reporting the issue @DavidR91 :+1:
Be sure to let us know if you have any questions or feedback, you can also checkout our #cake-build/cake Gitter channel for more interactive discussions.

@devlead Can I close this?

@patriksvensson nope, not fixed yet.

@devlead Can I close this now? :wink:

@patriksvensson issue still remains, investigating now

@DavidR91 Problem seems to be fixed now. Will appear in next released version.

Hi again,
Running 0.42 I'm still seeing issues with this kind of thing
For example this command line:
  "C:\Program Files (x86)\Jenkins\jobs\Website v2.1\workspace\v1\Website\..\cake\cake.exe" -verbosity=verbose -squaredUpRoot="C:\Program Files (x86)\Jenkins\jobs\Website v2.1\workspace\v1\Website\..\" -scomDllConfiguration="Release"
Gives me back this:
More than one build script specified.

Could not find a build script to execute.
Either the first argument must the build script's path,
or build script should follow default script name conventions.

Usage: Cake.exe [build-script] [-verbosity=value]
[-showdescription] [-dryrun] [..]`

The file on disk is build.cake and specifying it explicitly yields the same error
Is this a further parsing issue, or am I making an error here?
Note that previously (around 0.1.30) this kind of command worked provided I did the weird escaping trick (e.g. -squaredUpRoot="C:\Program Files (x86)\Jenkins\jobs\Website v2.1\workspace\v1\Website\\..\\")

From what I can tell, this issue remains regardless of the arguments provided if you execute using an absolute path:
C:\Program Files (x86)\Jenkins\jobs\Website v2.1\workspace\v1\cake\cake.exe
always generates the same error, even if there is a build.cake in

the working directory of the caller
the same directory as the cake.exe

Is it wrongly determining information based on the assembly path/location or something? (And that's why it's choking when run via an absolute path to the EXE?)

Hmm, there is something strange when cake resides in a directory with spaces in its name - perhaps specific to this machine?
For example:
C:\>"C:\cake walk\cake.exe"
Error: Illegal characters in path.
Working directory C:, cake.exe in C:\cake walk\  along with a build.cake in C:\cake walk
But
This works:
C:\>C:\cake\cake.exe C:\cake\build.cake
Is there is something related to spaces in paths that I need to investigate?

Are notifications still enabled for this closed issue, or should I raise a new bug?
This is a pretty serious problem for me and presumably anyone calling cake under folders such as "Program Files (x86)"

Hello David,
Sorry for not answering until now. I'm going on vacation tomorrow and will take a look at your issue then. Sorry again for the delay.
Best regards
Patrik

Hello David,
I've been able to recreate this behavior and I'm writing a fix for it now. I will try my best to have it ready as soon as possible.
/ Patrik

@DavidR91 I have submitted a fix for the bug and it should (finally) be fixed in the next version.


Supported Linux versions is missing RHEL 9.x

The list of supported Linux distros and versions is missing RHEL 9.x .

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

ID: 214e5e81-772a-966b-737d-51339404c42f
Version Independent ID: 87cfbf4e-75bc-1342-91b9-f79667c747c0
Content: Azure Automanage for Linux
Content Source: articles/automanage/automanage-linux.md
Service: automanage
GitHub Login: @mmccrory
Microsoft Alias: memccror

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

@ohthehugemanatee Can you please let me know if you are able to use the RHEL 9.x distor either via portal or ARM templates?    Kindly revert with requested information.

@ohthehugemanatee As of now, we do not support RHEL 9.x. And as we haven't heard from you, we will close the issue for now. If there are further questions, please revert and we will be glad to assist you.


Evaluate while training to find the best model for neural search

PR types
New features || Performance optimization |
PR changes
APIs | Docs |
Description
Evaluate while training to find the best model

readme相应位置更新一下evaluate用法。 @AI-Mart

readme相应位置更新一下evaluate用法。 @AI-Mart

已添加


New features：pdk.kong.upstream

New features：
pdk.kong.upstream
https://discuss.konghq.com/t/data-center-aware-load-balancing/5667

Why is there always conflict?

It's always conflict. Why?


Possibly incorrect x,y player coordinates

When graphing the player coordinates using matplotlib, the plot is not representative of the players actual positions on the field. Is there some kind of translation that needs to be done to transform the player coordinates to proper top down representation? Thanks!

Could you give an example / repro case?
The players positions are in    [-1, +1]  (x-coordinate)  and  [-1/2.25 ,  +1/2.25] for y-coordinate.
For SMM, coordinates are mapped to 96x72 here:
https://github.com/google-research/football/blob/6be1fcfe62ba2d5c73760cdb8403acb9df3a0ecf/gfootball/env/observation_preprocessing.py#L46

What I've done is use the simple115 observation macro to find the player X,Y coordinates which I'm then plotting with matplotlib. The resulting plot of a random step during a match is plot which is incorrect as far as I can tell. Is there something I'm doing incorrectly? Thanks for your time!

I plotted random score dump and it seems legit. The red dots were plotetted from observation['left_team'] and the blue dots are observation['right_team'].
Basically, something like this:
left = obs['left_team']
right = obs['right_team']
pyplot.scatter(left[:, 0], left[:, 1], color="red", s=6)
pyplot.scatter(right[:, 0], right[:, 1], color="blue", s=6)
pyplot.savefig("/tmp/karol_%d" % step)
pyplot.clf()
See examples below for different steps. Definitely not all in one place
https://ibb.co/TTs4LZ8
https://ibb.co/gwvKRw3
https://ibb.co/8XPW3PX
https://ibb.co/rGztGSX
https://ibb.co/NNNMYDr
https://ibb.co/QvXffRw
https://ibb.co/PCVdp7r
https://ibb.co/DbV5gBr
https://ibb.co/XpLSpB2
https://ibb.co/bLk02SL
https://ibb.co/hBPgYF2
https://ibb.co/1q1Qknz
https://ibb.co/xf2qD0x
https://ibb.co/YpBxf7t
https://ibb.co/bdYQ3BS

Okay I will triple check my code and refactor, I appreciate your support!


TypeScript definition file

This is a basic TypeScript definition file I created for use with react-moment in my project. Every prop is marked as optional - I am happy for suggestions on how we can enforce compile-time guards on acceptable prop pairs but I don't think this is possible with TypeScript.

Looks good. Thanks for the code!


Handle PDF files with missing 'endobj' operators, by searching for the "obj" string rather than "endobj" in XRef.indexObjects (issue 9105)

This patch refactors the searching for 'endobj', to try and find the next occurance of "obj" and then check if it was in fact an 'endobj' and continue searching otherwise.
This approach is used to avoid having to first find 'endobj', and then re-check the entire contents of the object and having to run (potentially expensive) regular expressions on arbitrary long strings.
Fixes #9105.

Replaces PR #9253, since the approach used there would cause needless re-parsing of data and potentially bad regular expression performance.

/botio test

/botio-windows test

/botio-linux preview

/botio makeref

Thank you for the fix!


Set default account

Instead of constantly specifying --account prod be able to just define a default account.

Resolved in https://github.com/duo-labs/cloudmapper/commit/ed94cc6a97c495dce9d79b52a55b312ce7934301


Performance on windows is bad due to GPU spiking, this also influences sound

Repro steps

Do a call with several people on windows while monitoring GPU usage
Notice whenever sound has issues, the GPU spikes on the following proces

Expected Result
GPU doesn't spike when using FFC
When the GPU does spike, the audio does not break
Actual Result

Very laggy when this happens
System Info

Fixed.


Feat/Replace SecretDefinitions by ExternalSecrets

Related to https://github.com/3scale/platform/issues/509 and https://github.com/3scale-ops/saas-operator/issues/140

Adds harcoded ExternalSecret CreationPolicy: "Owner" field,  because there is no case in which  we can be interested on overriding this field from any other value different to Owner# Enum with values: 'Owner', 'Merge', or 'None'
# Default value of 'Owner'
# Owner creates the secret and sets .metadata.ownerReferences of the resource
# Merge does not create the secret, but merges in the data fields to the secret
# None does not create a secret (future use with injector)

ExternalSecrets path has a hack to remove the prefix secret/data/ from any possible vault.path https://github.com/3scale-ops/saas-operator/commit/1c6d23f82d6c171a73d645272c498ab0cce0fabf at runtime level. The reason is, current deployed CRDs are using the prefix secret/data/, because it was needed on secret-manager, but it is not needed on external-secrets-operator, so to not break current deployed CRDs, we sanitize the vault.path at runtime. In future releases, once we remove this prefix from current deployed CRDs, this hack can be removed.
Moves the common ExternalSecret fields (SecretReference.Name/SecretReference.Kind and RefreshInterval), from each FromVault key to a new spec.config.externalSecret CRD object field, because on most cases there are different vault keys on the same secret (so no one single vault key per secret), so it makes no sense having those settings being able to be override on every single key with possible collisions among keys

So now, the new spec.config.externalSecret CRD object field is in charge of defining the common ExternalSecret fields which apply to all secrets under the same workload

It replaces all SecretDefinitions by ExternalSecrets on controllers with secrets (cors-proxy, mapping-service, zync, backend, system)
It adds deep testing on every workload with  ExternalSecret resources introspection with both create and update operations
Remove all secrets-manager resources and all its dependencies
Update Docs
Bump alpha release: v0.13.1-alpha.4

Testing

I have tested on dev cluster, running the operator locally with make run WATCH_NAMESPACE=test, that it works as expected:
Execute locally saas-operator main branch, it creates SecretDefinitions, and then secrets-manager operator created target secrets
Turn off secrets-manager operator pods
Execute locally saas-operator current branch, it creates ExternalSecrets, and:

The target secret.data does not change, because it have same content
The target secret gets adopted by its respective  ExternalSecret (with owner references)

{"level":"info","ts":1647359514.917165,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/cors-proxy-system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878281.4065654,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/mapping-service-system-master-access-token","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878281.620975,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/cors-proxy-system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878281.800215,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/backend-system-events-hook","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878282.1560605,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/zync","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878282.4109864,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/backend-internal-api","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878767.2502375,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-app","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878767.7129023,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-backend","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878767.9786918,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878768.3178751,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-events-hook","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878768.6721823,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-master-apicast","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878768.825456,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-multitenant-assets-s3","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878769.181621,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-recaptcha","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878769.4473124,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-smtp","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1647878769.780012,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"test/system-zync","SecretStore":"/vault-mgmt"}

Staging deploy
It worked as expected, old SecretDefinitions needed to be manually created, setting first the secrets-manager operator to 0 pods:
{"level":"info","ts":1648132270.8686328,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/cors-proxy-system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132271.0724626,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/cors-proxy-system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132271.6151276,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/mapping-service-system-master-access-token","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132271.7610803,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/mapping-service-system-master-access-token","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132272.3032942,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/zync","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132272.4250944,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/zync","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132272.6367106,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-app","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132272.8818443,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-backend","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132273.26367,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-database","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132273.3874593,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/backend-system-events-hook","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132273.5100543,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-events-hook","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132273.732001,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/backend-internal-api","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132273.9828744,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/backend-error-monitoring","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132274.1149068,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-master-apicast","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132274.2495165,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-multitenant-assets-s3","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132274.5827897,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-recaptcha","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132274.7018359,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-smtp","SecretStore":"/vault-mgmt"}
{"level":"info","ts":1648132274.9040606,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"3scale-saas/system-zync","SecretStore":"/vault-mgmt"}

/kind feature
/priority important-soon
/assign

/approve


usb: disable tps6598x interrupts

Restore the interrupt masks on transition to the next state. The masks
are not restored on the USB-C port used by the hypervisor. This prevents
an interrupt storm in the guest when the other USB-C port is exposed to
the guest. The tps6598x interrupt line is shared amoung both ports.

Can we just unconditionally do this on init? If m1n1 isn't using/handling these IRQs it should just disable them by default.

Mac OS seems to rely on the default config or iboot for the pd controller's interrupt config. When the interrupts are disabled in m1n1 the port is dead.
We could declare that HV needs port 0 and only disable interrupts it.

We've run into things like this in the past, so I think I'm going to rework how we do subsystem shutdowns a bit. I'll discriminate between "shutdown for kboot" and "shutdown for chainload"; the latter tries to restore state to whatever iBoot leaves to make macOS (or another m1n1) happy, while the former leaves things in the sanest state for Linux. Let me think for a bit how I want to do this :)

I think the sanest state for chainload and linux boot does not differ in this case. Leaving the interrupts in the default config looks sane to me. The Problem is the hv guest. It wouldn't be a problem there either if we were not using one port for the hv or if both ports were not sharing the same interrupt line.
Kept now mostly within m1n1. The only required proxy change is that the other USB iodev gets disabled in hv.init() so m1n1 knows in hv_init for which port it should restore the interrupt mask.
Also in this PR some minor python hv fixes and removal of the hiding of the second usb-c port.

I don't like the idea of leaving IRQs enabled for Linux (the sane state for IRQ hardware is leaving stuff masked), but we can shave that yak later. Other than the comment this looks good, feel free to mark it ready.

Interrupts are now only restored for the guest and for chainloading (not via chainload.py -c though)
Writes to the tps6598x were not reliable. I've both failures to clear IntMask and to restore it to the boot values. Apparently "solved" by adding udelay(120) after i2c writes.
HV works now on both USB-C ports and the other port is usable in Mac OS.


Replace temporary project name (Taffy) to new (Doto) in documents

User Story:
Some of the project documents is still using temporary name Taffy. Name Taffy is expired.
Acceptance Criteria:
Find and Replace the name Taffy into Doto.
Following document has name Taffy:

Doto/Code_of_conduct.md

Any other documents that has Taffy please edit and add them in.

The document Code_of_conduct was only one that uses Taffy, thus, only required to change that file to meet the acceptance criteria


Fix relative header paths.

When using with CMake, which builds in a separate directory and uses the -I flag for include directories, I found that some paths cannot work.

Maybe try using the cmake setup in #33 ?


I improved the FLIR camera mode as a personal project, how can I get it considered for addition?

Of course I couldn't just create a new branch for a pull request (unless I just don't understand something obvious). It's probably best that I don't just paste everything here, but maybe a pastebin link?
Anyway, what I changed:
*Highlighted entities are separate from other opaque renderables, meaning that trees and map geometry do not render with ugly polygons and retain their textures
*Fixed infrared emitters becoming darker or invisible in low-light areas, FLIR image is consistent across maps and lightings
*Fixed visible color affecting IR signature, making black props invisible (ish)
*Fixed sky becoming white and distracting in IR
*Added Bokeh DOF to soften image, adjusted bloom
*Set environment and entities to different DrawColor passes, so their brightness and contrast can be altered independently (needed to keep white map geometry from being as bright as entities)

Create a fork and push your changes to it. Then you can pull request them here.

@thegrb93 Figured it out, thanks.


Support for multiple applicant comments. One comment per income source.

This PR modifies the existing additional_info column of the cbv_flows table from string column to a JSONB column. The JSON object is a hash consisting of keys which reference applicant payment account_id to an end user supplied comment.
Ticket
Resolves FFS-1087
Changes

Added migration that sets the default column value to an empty object e.g. {}
Adds new functionality to the Payment Details Controllers
Adds a comment box on the payment details page
Wraps the table component on the payment_details page with a form.
Adds unit and integration tests
Navigating back to the payment details page preserves the comment

Context for reviewers
The continue button for the payment_details page now acts a form submission which submits a form to itself. Upon updating the comment for the respective payment details the user is redirected to the jobs page where they can add another source of income.
Testing

I'd like to add a few more test cases.


Adding utility to mock environment variables

Adding a utility to test scenarios with custom env variables.
Originally implemented for removal of system-lambda (as part of #2184), but I want to use it in a current PR I am doing now.

closes #1942


PlacementAndLoadBalancing outdated values

In "Resource governance" article
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-resource-governance
I found two outdated parameters for PlacementAndLoadBalancing section:
CpuPercentageNodeCapacity
MemoryPercentageNodeCapacity
Actual values:

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

ID: 19a961bb-1091-be9f-f9bb-895abf625e39
Version Independent ID: fa7dc2a2-6901-1efe-8921-4d2f673ac7b5
Content: Azure Service Fabric resource governance for containers and services
Content Source: articles/service-fabric/service-fabric-resource-governance.md
Service: service-fabric
GitHub Login: @aljo-microsoft
Microsoft Alias: aljo, subramar

@fbuser1 Thanks for the feedback! We are currently investigating and will update you shortly.

@fbuser1 I have assigned the issue to the content author to investigate further and update the document as appropriate.

https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-resource-governance#cluster-setup-for-enabling-resource-governance
direct link to section with outdated code

@fbuser1 this issue has been reported to the Azure Portal team and hasw been priortized to be completed by the end of the year. Thank you for your feedback!
#please-close

Hi, in which way is this related to Azure Portal? Is this a bug on the documentation or not? If this isn't, what is this about? Does the portal have wrong names?  How should we work with the policies?


missing constraint type in migration

Elixir version
1.14.3
Database and Version
any
Ecto Versions
current
Database Adapter and Versions (postgrex, myxql, etc)
any
Current behavior
https://github.com/elixir-ecto/ecto_sql/blob/8d4328638aeb5821c1a0fa55454c97cd21171fa0/lib/ecto/adapter/migration.ex#L13-L24
seems to be missing {:create %Constraint{}} and {:drop, %Constraint{}, mode} and co.
Expected behavior
The command type should cover all possible cases.

Thanks for the reports @ruslandoga!


"Sync to notion" not work in the zotero 7

As title

Hi @ccwanggl, I'm still working on support for Zotero 7.
Can you give me more details about exactly what's not working? When you click "Sync to Notion" does it not do anything, or do you see an error message?

Hi @dvanoni, I met this problem too, I click "Sync to Notion" in Zotero, it shows successful . as screenshot followed, but I didn't  find it in my Notion.  In a few days ago, it was working.  I don't know why this happen. My Zotero version is 6.0.26.

sorry for delay reply.
It does not do anything, no any message come out

Thanks, @ccwanggl. I'll look into this as I work on support for Zotero 7.
In the meantime, if you do need to use Notero, please continue to use Zotero 6 for now. I'll post an update here when I release a new version of Notero that supports Zotero 7.


refactor(renderer): Extract the renderer to a new library

affects: tessellate-fragment, tessellate-renderer

Looks good so far. I'd like to add a commit to clean up the dependencies a bit and to fix the failing tests.

Please go ahead :)

Changes Unknown when pulling c822205687b8fc282eab3f157e2c65685234b30d on extract-tesselate-renderer into ** on master**.

👍

Changes Unknown when pulling 9be9941e29df4156224ea6985c0525dd32a9845c on extract-tesselate-renderer into ** on master**.


xbuild throw error (Fedora 23)

Hello, I use Neovim on Fedora 23 and when I try to install omnisharp-vim with Vim Plug, when I start xbuild I get an error in the output . I searched a little bit and found that the problem is that mono doesn't support .NET 4.5.2 but I'm not sure, am I doing something wrong?

I was experiencing same problem on Ubuntu Xenial (16.04), using Mono installed via default repository.
I've managed to get over this problem by installing Mono from official Mono project.
After doing so, just typing 'xbuild' and hitting enter made things go on.

We now have an integrated installer which downloads and extracts the latest OmniSharp-roslyn binaries - no need to build.


Dead link replacement

This link generates a 404:
https://kubevirt.io/user-guide/docs/latest/administration/intro.html#cluster-side-add-on-deployment
I suggest moving to think link.
https://kubevirt.io/user-guide/#/installation/installation

/hold cancel
/approve


The Status enumeration should be directly equatable

Overriding valueOf and returning the code should do it. Add a test.

A test I'm thinking of is usage in an === expression and in a switch block.


Can't get it to work for pyre

I get the error:
File "/home/vandalk/.local/lib/python3.9/site-packages/deppth/compression.py", line 197, in decompress
    return lzf.decompress(chunk, chunk_size).ljust(chunk_size, b'\x00')
AttributeError: module 'lzf' has no attribute 'decompress'

In the README you warn that "You may need to install C++ build tools to get this dependency to install correctly." on the lzf module section of the "Dependencies". So I assume the command is failing because lzf didn't install correctly? But what are these c++ build tools and how do I install them?
I'm on Manjaro Linux, but I can also do this on windows if it is required.

Oh nevermind, I was able to do it by installing "pip install python-lzf" instead of "pip install lzf"


fix(image-builder): print request errors

Fixes #1980
Before
$ packit build in-image-builder ttomecek-anaconda-installer-s3-1
2023-05-25 10:11:30.002 utils.py          ERROR  400 Client Error: Bad Request for url: https://console.redhat.com/api/image-builder/v1/compose
Unexpected exception occurred,
please fill an issue here:
https://github.com/packit/packit/issues

After:
$ packit build in-image-builder ttomecek-anaconda-installer-s3-1
2023-05-25 14:19:57.350 vm_image_build.py ERROR  Image Builder Errors: {"errors":[{"detail":"request body has an error: doesn't match schema
#/components/schemas/ComposeRequest: Error at \"/distribution\": value \"fedora-rawhide\" is not one of the allowed values\nSchema:\n  {\n    \"enum\": [\n
\"rhel-8\",\n      \"rhel-84\",\n      \"rhel-85\",\n      \"rhel-86\",\n      \"rhel-87\",\n      \"rhel-9\",\n      \"rhel-90\",\n
\"rhel-91\",\n      \"rhel-92\",\n      \"centos-8\",\n      \"centos-9\",\n      \"fedora-35\",\n      \"fedora-36\",\n      \"fedora-37\",\n
\"fedora-38\"\n    ],\n    \"type\": \"string\"\n  }\n\nValue:\n  \"fedora-rawhide\"\n","title":"400"}]}
2023-05-25 14:19:57.350 utils.py          ERROR

Since IB pretty-prints json, it can be quite verbose: I don't think that's a problem in CLI.
TODO:

[x] Write new tests or update the old ones to cover new functionality.

RELEASE NOTES BEGIN
Unsuccessful Image Builder requests now provide error details so you can fix the Image configuration.
RELEASE NOTES END

Am I cursed? What the F are these errors?!
In other words, I'm going to calm down and investigate :D

Failed to download source from https://src.fedoraproject.org/rpms/python-ogr/blob/main/f/python-ogr.spec: ConnectionError(ProtocolError('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')))

Thanks

recheck


Bump deps

Based on https://github.com/camunda/camunda-modeler/pull/2064, this updates our app as well as app test dependencies.

@barmac maybe you can reproduce this as well? Not urgent of course #springcleaning 🧹

@barmac maybe you can reproduce this as well? Not urgent of course #springcleaning 🧹


Is Email popup supposed to be docked to the right side of brower?

One of the benefits with the enhanced email function is that you can move to other records as required.  In addition you are supposed to have the ability to have multiple pop up windows open for email.  I have researched the enhanced email docs articles but cannot seem to be able to execute these functions.   I am using Chrome and have cleared the cache as suggested on the other issues for this article.

@hburgh1 Please provide a link to the documentation that you are referring to.

Doesn’t Github provide the URL where the comment was made?
Harry Burgh
267 229 2914

From: Peter Hecke<EMAIL_ADDRESS>Sent: Thursday, April 9, 2020 9:34:03 PM
To: MicrosoftDocs/dynamics-365-customer-engagement<EMAIL_ADDRESS>Cc: Harry Burgh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Is Email popup supposed to be docked to the right side of brower? (#1714)
@hburgh1https://github.com/hburgh1 Please provide a link to the documentation that you are referring to.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/dynamics-365-customer-engagement/issues/1714#issuecomment-611832079, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDA4NRY77AAESEJFQNJDALRLZZQXANCNFSM4MDKV3DA.

@hburgh1 GitHub should include the URL in the issue, but there is none here. We need a related URL to determine what writer owns the documentation in question.


add faster subTB

self.subtb_loss_fast(log_p_F, log_p_B, log_F_preds, clip_log_R, batch.traj_lens)
  Median: 59.95 ms
  IQR:    0.29 ms (59.84 to 60.13)
  17 measurements, 1 runs per measurement, 1 thread
<torch.utils.benchmark.utils.common.Measurement object at 0x7f89941df130>
self.subtb_cum(log_p_F, log_p_B, log_F_preds, clip_log_R, batch.traj_lens)
  Median: 16.43 ms
  IQR:    0.12 ms (16.41 to 16.53)
  7 measurements, 10 runs per measurement, 1 thread

subtb_diff is the mse of the loss between the two implementations.
Diff is not zero because I precompute P_F - P_B, doing cross(P_F) - cross(P_B) instead of cross(P_F - P_B) yields the exact same results.

(squash)


Run tests in parallel

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 97.321%. Remained the same when pulling 13b33438ed3981436fd4169f88db8de5a3d2021f on parallel-testing into 8da6db352d9e9ce2eaa0386ad47df496c49806a3 on main.


(SP: ) Fix coop details buttons

Fix profile buttons at cooperation details
Actual result:

Figma (link):

Hi!
Can I get this opportunity to fix this issue, thanks


Add potential payout to portfolio

Coverage increased (+0.01%) to 31.715% when pulling 2470687a7c64130569b8c708e39196dca8c45c46 on qingweibinary:qingwei/portfolio_potential_payout into 8138f8f494f9f3749191aa05c22ad48979f9571a on binary-com:master.

Coverage increased (+0.01%) to 31.715% when pulling 2470687a7c64130569b8c708e39196dca8c45c46 on qingweibinary:qingwei/portfolio_potential_payout into 8138f8f494f9f3749191aa05c22ad48979f9571a on binary-com:master.