Why doesn't Widgets in Flutter have enabled/disabled property/function?

Hi, I am wondering why there is no SIMPLE enabled/disabled method/property on Widgets like buttons and TextField?
I have seen many people requested this feature and it has been years since the first requests were made.
I am honestly wondering what would be the issue behind this? Is there a technically difficulty in implementing this BASIC feature?

TextField has an enabled param: https://api.flutter.dev/flutter/material/TextField/enabled.html
To disable a button, just set the onPressed param to null:
ElevatedButton(
  child: Text('disabled'),
  onPressed: null,
),

@Jayvd
There's a way to enable and disable as described above. Also this PR which added the said functionality to the TextField. If this answers your question, then you may go ahead and close this.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Converting between Global Pose and Submap Pose in the protobuf

The issue stems from a similar question I asked in Editing Cell Values From a known Global pose #1792. I figured I would simply the question here for what may provide a quicker response. Answering this question may allow me to close both of these questions.
If I have a pixel in the global frame with a given x, y, how do I know the x, y value in each submap frame? I have started with:
io::ProtoStreamReader reader(pbstreamFileToOpen);
io::ProtoStreamDeserializer deserializer(&reader);
mapping::proto::PoseGraph pose_graph_proto = deserializer.pose_graph();
mapping::proto::Trajectory trajectory_proto = *pose_graph_proto.mutable_trajectory(trajectoryID);

mapping::proto::SerializedData proto;
while (deserializer.ReadNextSerializedData(&proto)) {
  if(proto.has_submap()) {
    auto submapGlobalPose = transform::ToRigid3(trajectory_proto.submap(submapId).pose());  // Is global the correct assumption?
  }
}

The assumption is that this should give me a transformation from the global map, to the submap. The global map origin from what I understand is the same as the origin of submap 0. Therefore there is no transformation from global map to submap 0, but on other submaps, there should be. From the linked issue at the top, I believe this is where the origin of my issue exists. I have no problem pinpointing cells in submap 0 from the global map, but once I move onto other submaps, I start getting many errors. It leads me to believe that my assumptions about the code above are wrong.
UPDATE:
It looks like I may need to update the Global map frame to the local, and then to the submap frame. It looks like I can get the local pose from inside the while above by:
auto submap = proto.submap();
auto localSubmapPose = transform::ToRigid3(submap.submap_2d().local_pose());

The question is then, how do I determine the global to local transform, or vice versa, and how to determine the local to submap? I assume I am supposed to do transforms in the order of Global -> Local -> Submap. In short, how do I go from Global position to a submap frame position.

I found the solution to my own issue. It seems that no transform is needed at all. My suspicion is that the pbstream already holds the matched version of the submaps.

I found the solution to my own issue. It seems that no transform is needed at all. My suspicion is that the pbstream already holds the matched version of the submaps.


Tape storage re-use

Is it possible to reuse the storage that was allocated for the Tape Vec? Based on my digging it doesn't look to be possible in the current state.
If I am right about this not being possible at the moment, It feels like it isn't supported due to the tape type in this package being Peekable<IntoIter<>> but this looks like it could be solved by using a Peekable<Drain<>>?
Let me know if I am on the right track with this...

That sounds reasonable, I like the idea:) definitely worth a try

I think the reason this didn't happen is lifetimes. since the tape has a lifetime bound to it's elements the re-use would make the borrowchedker think the life times are related:
let a: &'a[u8] = b"42";
let mut reusable_tape = make_new_tape();;
parse(a, &mut reusable_tape);
// reusable_tape: Tape<'a>
do_stuff_with(reusable_tape);
reusable_tape.clear()
let a: &'b[u8] = b"43";
parse(b, &mut reusable_tape);
// reusable_tape: Tape<'b> <= lifetime conflict! 'a now needs to be 'b or wider

I was able to modify the library to support this by adding an additional lifetime on the tape, I'll open a PR with the changes shortly but it was pretty straightforward to implement. The tape type now looks like this:
pub type Tape<'tape, 'input> = Peekable<Drain<'tape, Node<'input>>>;
pub trait Deserialize<'input> {
    fn from_tape<'tape>(tape: &mut Tape<'tape, 'input>) -> simd_json::Result<Self>
    where
        Self: Sized + 'input;
/// etc...
}

This also required modifying every deserializer implementation to match the trait lifetime changes. After the changes I can reuse a tape like so (roughly):
simd_json::fill_tape(json_msg, buffers, tape)?;
let mut itr = tape.0.drain(..).peekable();
let item = MyStruct::from_tape(&mut itr);
println!("item: {:?}", item);
let tape = tape.reset();
simd_json::fill_tape(second_json_msg, buffers, tape)?;
let mut itr = tape.0.drain(..).peekable();
let item = MyStruct::from_tape(&mut itr);
println!("other item: {:?}", item);

The only downside of this is that any existing deserializer implementations need to be updated with the new signatur


fix: allow space at docstring parse

close #47
Signed-off-by: cutecutecat<EMAIL_ADDRESS>

Thanks!


"Maximum call stack size exceeded" on package installation

Prerequisites

Put an X between the brackets on this line if you have done all of the following:

[x] Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
[x] Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
[x] Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
[x] Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
[x] Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When I try to install packages (not all - some work, some don't) I get the error npm ERR! Maximum call stack size exceeded. In my example I tried to install linter-eslint.
Steps to Reproduce

Try to install linter-eslint via apm oder atom gui

Expected behavior:
Normal installation of the package
Actual behavior:
Following error message appears:
><EMAIL_ADDRESS>postinstall /tmp/apm-install-dir-120321-10641-y7v7fv.6n4qc/node_modules/linter-eslint/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>No longer maintained - Use lodash probably
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
Aborted (core dumped)
npm WARN enoent ENOENT: no such file or directory, open '/tmp/apm-install-dir-120321-10641-y7v7fv.6n4qc/package.json'
npm WARN apm-install-dir-120321-10641-y7v7fv.6n4qc No description
npm WARN apm-install-dir-120321-10641-y7v7fv.6n4qc No repository field.
npm WARN apm-install-dir-120321-10641-y7v7fv.6n4qc No README data
npm WARN apm-install-dir-120321-10641-y7v7fv.6n4qc No license field.

npm ERR! Maximum call stack size exceeded

Reproduces how often:
100% of the time I try to install the package linter-eslint
Versions
Installed atom via apt-get today.
apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.45.0
python 2.7.17
git 2.20.1

Atom    : 1.45.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0

Pop!_OS 19.10
GNOME 3.34.2

Additional Information
Also appears when I try to install the following packages:

prettier-atom
language-babel

If I missed some informations please let me know!

@emha So I'm on Pop!_OS 19.10 as well with the same issue

I have the same issue here, on PopOS 20.04...

@emha @GoulvenC Do you think this would receive more attention if it was in the linter-eslint repo?
Note: I reached out to system76 for any guidance they might be able to provide since this seems isolated to Pop!

@emha @GoulvenC Do you think this would receive more attention if it was in the linter-eslint repo?
Note: I reached out to system76 for any guidance they might be able to provide since this seems isolated to Pop!

Thank you for doing that!
I think the problem is not addressed by linter-eslint as there are other packages like language-babel with the same error.

A coworker and I are both on Pop!_OS 20.04 LTS and can install linter-eslint with no issue so this may be an issue with something either upstream or a configuration issue.

I'm on Ubuntu 18.04 LTS and have the same issue.

FYI, just updated Atom to 1.48.0 (x64) and was able to install linter-eslint through Settings->Install
It's a miracle. I had many hours trying to solve this!

FYI, just updated Atom to 1.48.0 (x64) and was able to install linter-eslint through Settings->Install
It's a miracle. I had many hours trying to solve this!

Nice hint! I ended up with a complete fresh install of Pop-OS 20.04 as I also hat other issues caused by the upgrade to the 20.04 version. The clean install also fixed the atom problem.


Enable CFG and Spectre mitigations for all IIS projects

See https://github.com/Microsoft/IIS.ServiceMonitor/pull/46/files

Fixed in #17. Individual projects now need to use the latest commit of the submodule. We will start with ServiceMonitor.


image to csv export

CSV export for images for via the FeatureTableContextMenu. Exported via a matrix.
Made MobilityScan extend Scan, but it's all default implementations and none of them need extra objects.
Add option to show the best mobility scan of IMS traces.

Hey Steffen, the clustering-20130919.jar file should not be needed anymore, the dependenci is updated in build.gradle

Oops, my bad. I thought it was the other way round. I'll remove it.

Thanks Steffen


[QUESTION] Videos for testing

What is your question?
Was watching a recent livestream that had over 3.5M live viewers. It is a great video to use to test the performance of the script.
Link to video: https://www.youtube.com/watch?v=sThZ4TZ_Py4
Do you have any other examples like that video to test upon?

https://github.com/xenova/chat-downloader/blob/2a5b3f50d57beb36595ae838d989df4235b80124/chat_downloader/sites/youtube.py#L70
The code is always tested on each commit so I'm not sure what else would you like to be tested?

@BleachedGorilla Thanks for the info 👍  As @mikelei8291 mentioned, I try to keep an up-to-date list of URLs for testing in the _TESTS list (same way yt-dlp does it).
Since the video is ~9h long, we can't run it everytime for testing. That being said, I ran it once on my computer and everything seems to work fine. If you would like to do the same in future, you can run it with the --testing flag (which will pause if it encounters anything strange).
I'll close the issue for now, but feel free to ask any other questions.


Module pkg_recourses not found on Python 12

System OS
MacOS
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
v4.2.3
Expected Behavior vs Actual Behavior
Throws this error both on pip or pipx:
ModuleNotFoundError: No module named 'pkg_resources'
Steps to reproduce - Ensure to include actual links!
pipx run spotdl download "https://open.spotify.com/track/5a1iz510sv2W9Dt1MvFd5R?si=e4513e7be634406f"
Traceback
Traceback (most recent call last):
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/bin/spotdl", line 5, in <module>
    from spotdl import console_entry_point
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/__init__.py", line 13, in <module>
    from spotdl.console import console_entry_point
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/console/__init__.py", line 5, in <module>
    from spotdl.console.entry_point import console_entry_point
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/console/entry_point.py", line 10, in <module>
    from spotdl.console.download import download
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/console/download.py", line 7, in <module>
    from spotdl.download.downloader import Downloader
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/download/downloader.py", line 21, in <module>
    from spotdl.providers.audio import (
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/providers/audio/__init__.py", line 5, in <module>
    from spotdl.providers.audio.bandcamp import BandCamp
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/providers/audio/bandcamp.py", line 10, in <module>
    from spotdl.providers.audio.base import AudioProvider
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/providers/audio/base.py", line 15, in <module>
    from spotdl.utils.formatter import (
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/spotdl/utils/formatter.py", line 15, in <module>
    import pykakasi
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/pykakasi/__init__.py", line 44, in <module>
    from .kakasi import Kakasi, PyKakasiException, UnknownCharacterException
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/pykakasi/kakasi.py", line 11, in <module>
    from .kanji import JConv
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/pykakasi/kanji.py", line 10, in <module>
    from .properties import Configurations
  File "/Users/alireza/.local/pipx/.cache/71f313dd4461cbb/lib/python3.12/site-packages/pykakasi/properties.py", line 8, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

Other details
Python version is 12 and this spotdl version had to support it.

Thanks. That resolved the issue.


Request: all outputs of weather.text

I am making a website where part of the background changes based on the current weather conditions and the javascript I've written makes that decision based on the weather conditions. Is there anywhere I can find all of the possible outputs from calling weather.text so I can write my if statements correctly?

These are all the condition codes - https://developer.yahoo.com/weather/documentation.html#codes.


Re-write formatters against new API

For 3.0 the https://github.com/cucumber/cucumber/blob/master/lib/cucumber/formatter/legacy_api/adapter.rb should be removed, and all formatters that ship with Cucumber should go through the new, test-case based API.
Altogether there are:

progress (#859)
pretty
html
json (#851)
json_pretty (is the same as json)
junit (#855)
stepdefs (#859)
usage (#859)
debug can be removed - only for help writing old-API formatters
rerun done in (83a0c75cbaa3ded4a5c2f596cbfdcd257fa73cb0)

I think the progress formatter is the place to start, as there's a lot of shared code in all the console formatters. If you want to tackle one, please create a ticket and reference this ticket.

Pretty re-write investment may be best placed into https://github.com/cucumber/cucumber-pretty-formatter

Charlie Rudolph has just dropped the pretty formatter from cucumber-js altogether, and just just pretty-printing failures.
As much fun as it is writing pretty formatters, I think we should give serious consideration to doing the same, and giving ourselves a clean slate for these.

💖 🌈 hooray!


Auto approve/import

Name of Defective Feature
Approving/Importing
System Settings (Required)
ToolKit Version:
Operating System (Mac/Windows/Etc):
Browser (Chrome/Firefox/Safari):
Browser Version:
Other Extensions:
Export of Toolkit Settings (Bottom Left of Settings Page)
[paste settings here]

Steps to Reproduce the Behavior
Please write down the steps necessary to reproduce teh behavior you're seeing. Please be as thorough as possible.

Expected Behavior
What did you expect would happen after completing the steps?
Scheduled transactions must be approved.  When was the last time you rejected a scheduled transaction that you scheduled?  If the accounts section of the toolkit allowed me to AUTOMATICALLY approve scheduled transactions, I would check it!
Imported transactions must be approved.  They are imported from the bank, and other than just letting you know that the import has been done, I don't see the value of say yes, please import.  If the accounts section allowed me to AUTOMATICALLY import (and approve) transactions, I would check it!
Actual Behavior
What actually happened after you completed the steps.

@hmspain
Features under consideration and the general status of the project and roadmap is on our Trello Board. Feel free to vote and comment. To suggest a new feature, please visit the YNAB Forum for Extensions and create a new thread titled "Toolkit Feature Request: [a short description of the feature]". Forum user @bluebird8203 is managing the features there and will make sure it ends up in Trello.

I tried :-).  Sorry, I didn't follow the subject "Toolkit Feature Request: [a short description of the feature]", but hope it works.
Harrison Spain
<EMAIL_ADDRESS>
On Jul 7, 2017, at 5:22 AM, David Baldon<EMAIL_ADDRESS>wrote:
@hmspain
Features under consideration and the general status of the project and roadmap is on our Trello Board. Feel free to vote and comment. To suggest a new feature, please visit the YNAB Forum for Extensions and create a new thread titled "Toolkit Feature Request: [a short description of the feature]". Forum user @bluebird8203 is managing the features there and will make sure it ends up in Trello.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

No worries. Hopefully @bluebird8203 will find the post and create the request on the Trello board. The reason for the subject format is to help identify feature requests. You can change the tile by clicking the little gear to the left of the title and then selecting Edit.
Closing this issue since the request has been made on the forum.


Missing Docker NPM Dependency - Pip3

Specs

Leon version: 1.0.0-beta.4
OS (or browser) version: Rocky Linux the-factory.localdomain 4.18.0-348.2.1.el8_5.x86_64 #1 SMP Mon Nov 15 20:49:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
(if using Docker) Complete "npm run docker:check" output:

[kuuchuu@the-factory leon]$ npm run docker:check

><EMAIL_ADDRESS>docker:check /docker/leon
> docker run --rm -it leonai/leon npm run check

><EMAIL_ADDRESS>check /app
> babel-node scripts/run-check.js

Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
⠋
---

.: CHECKING :.

➡ node --version
✔ v14.18.2

➡ npm --version
✔ 6.14.15

➡ pipenv --version
✔ pipenv, version 2021.11.23

➡ pipenv --where
✔ /app/bridges/python

➡ pipenv run python --version
✔ Python 3.9.5

➡ pipenv run python bridges/python/main.py scripts/assets/query-object.json
✔ {"package": "leon", "module": "randomnumber", "action": "run", "lang": "en", "input": "Give me a random number", "entities": [], "output": {"type": "end", "codes": ["success"], "speech": 42, "options": {}}}

➡ NLP model state
✔ Found and valid

➡ Amazon Polly TTS
✔ Configured

➡ Google Cloud TTS/STT
❗ Google Cloud TTS/STT is not yet configured

➡ Watson TTS
❗ Watson TTS is not yet configured

➡ Offline TTS
❗ Cannot find bin/flite/flite. You can setup the offline TTS by running: "npm run setup:offline-tts"

➡ Watson STT
❗ Watson STT is not yet configured

➡ Offline STT
❗ Cannot find bin/deepspeech/lm.binary. You can setup the offline STT by running: "npm run setup:offline-stt"

---

.: REPORT :.

➡ Here is the diagnosis about your current setup
✔ Run
✔ Run modules
✔ Reply you by texting
✔ Amazon Polly text-to-speech
❗ Google Cloud text-to-speech
❗ Watson text-to-speech
❗ Offline text-to-speech
❗ Google Cloud speech-to-text
❗ Watson speech-to-text
❗ Offline speech-to-text

✔ Hooray! Leon can run correctly
➡ If you have some yellow warnings, it is all good. It means some entities are not yet configured

Expected Behavior
Leon successfully installs
Actual Behavior
[kuuchuu@the-factory leon]$ npm run docker:build

><EMAIL_ADDRESS>docker:build /docker/leon
> docker build -t leonai/leon .

Sending build context to Docker daemon  4.339MB
Step 1/12 : FROM node:14-alpine
 ---> 590973483ea0
Step 2/12 : ENV IS_DOCKER true
 ---> Using cache
 ---> 4ebeab1fba16
Step 3/12 : WORKDIR /app
 ---> Using cache
 ---> 6e0aadcd6bb3
Step 4/12 : RUN apk add --no-cache --no-progress     ca-certificates     python3     git     tzdata
 ---> Using cache
 ---> dd37fbc38811
Step 5/12 : RUN pip3 install --no-cache-dir --progress-bar off pipenv
 ---> Running in 076b600c423f
/bin/sh: pip3: not found
The command '/bin/sh -c pip3 install --no-cache-dir --progress-bar off pipenv' returned a non-zero code: 127
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR<EMAIL_ADDRESS>docker:build: `docker build -t leonai/leon .`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>docker:build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kuuchuu/.npm/_logs/2021-12-03T07_36_07_908Z-debug.log

How Do We Reproduce?
run npm run docker:build
Extra (like a sample repo to reproduce the issue, etc.)
Issue fixed by including py3-pip inside Dockerfile:
RUN apk add --no-cache --no-progress \
    ca-certificates \
    python3 \
    py3-pip \
    git \
    tzdata

Also, I made modifications to the .env file, such as the timezone, and the changes did not seem to take. "The current time zone is Africa/Abidjan" rather than mine, which is America/Chicago

Same problem, pip3 doesn't install.

:wave: Hi @Kuuchuu and @tomlawesome,
Thanks for reporting. Can you please try to pull Leon from the develop branch and retry?

This should be fixed with the develop branch. Closing this issue.


This GitHub Action greets every user who opens a pull request or an issue if the body of the comment is not empty.

@san-coding something for you.

currently fails because I still don't have write access to this repository will work just after merging this I guess if it doesn't I'll check and update with new commits.

wait, @sudhay23 make @sridhar-5 a collaborator/maintainer

yeah I was about to ask for the same thing. I was waiting to install a GitHub application onto this repository.

@sudhay23

wait, @sudhay23 make @sridhar-5 a collaborator/maintainer

come to discord guys, WhatsApp is down


[DEP] Remove BKFilter BaseTransformer, redesign equivalent series transformer

removes deprecated BaseTransformer BKFilter and adapts the BaseSeriesTransformer so it does not require statsmodels to do pointless conversions to and from data frames
part of #1611

Cant see anything off, but what strange code. Are the imports really just for datatype stuff rather than any actual processing?

yes its baffling, statsmodels has some strange things. Output tested identical


Container crash leaves iptables DOCKER / POSTROUTING chain in unclean state

Hi there,
we observed an issue yesterday on Docker 1.6.2 (not sure if it's fixed by docker/libnetwork#301  docker/docker#13957 , but probably not), running on Ubuntu 14.04
A container mysteriously crashed, so I restarted it via docker-compose up -d. Container was configured to expose internal port 8080 as external port 1336. Now came the curious part: From the host, the container was reachable under localhost:1336, but NOT under $HOST_PRIVATE_IP:1336
This was a situation that "shouldn't ever happen" as we saw it and took us quite a few hours to find out. Finally, we found the culprit in the iptables:
Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
[...]
MASQUERADE  tcp  --  ip-172-17-0-154.eu-west-1.compute.internal  ip-172-17-0-154.eu-west-1.compute.internal  tcp dpt:http-alt
[...]
MASQUERADE  tcp  --  ip-172-17-0-212.eu-west-1.compute.internal  ip-172-17-0-212.eu-west-1.compute.internal  tcp dpt:http-alt

Chain DOCKER (2 references)
target     prot opt source               destination
DNAT       tcp  --  anywhere             anywhere             tcp dpt:1336 to:<IP_ADDRESS>:8080
[...]
DNAT       tcp  --  anywhere             anywhere             tcp dpt:1336 to:<IP_ADDRESS>:8080

Docker apparently never cleaned up the old DNAT entry, so it was conflicting with the newer one and shadowing it.
The docker daemon was never restarted throughout the whole issue and investigation (mainly because we wanted to find the culprit). We could not find out what exactly crashed the container - but not the daemon - though.
If this is somehow still an issue, it seems rather easy to fix by always checking for duplicate external port configurations (which should never happen) when inserting the iptable rules. I'm unfortunately not too deep within the codebase, so I can't fix this and don't know if it's still an issue.
Best,
Dominik

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@falschparker82 This most likely should not be a problem in 1.7.1 because we do remove all the port mapping iptable rules when the container stops. And from what you are saying it looks like your container  crashed while the daemon was still running. In that situation the daemon should always be able to detect the container going down(gracefully or ungracefully) and trigger the cleanup. Can you please try 1.7.1 and let us know?

@falschparker82 have you been able to test of this is resolved with 1.7.1? Thanks!

I'm using AWS elastic beanstalk which runs docker 1.6.2, and seems like I'm also affected by this. Took me hours to figure out the problem.
As it's hard for us to update beanstalk's docker version, is there any workaround for this? What I can do is running some commands before starting up the docker containers.
Also is it safe to just manually remove all iptables forwarding entries that point to old docker containers?

I'm also seeing this issue (or something similar) with 1.8.1:
docker version
Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 19:47:52 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:49:29 UTC 2015
 OS/Arch:      linux/amd64

I used docker-compose up. After stopping the containers the iptables entries are still there:
docker-compose up

root@dev:/etc# iptables -L -n -v
Chain INPUT (policy ACCEPT 149 packets, 14268 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 ACCEPT     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
    0     0 ACCEPT     all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 DROP       all  --  docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain OUTPUT (policy ACCEPT 130 packets, 34005 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>          tcp dpt:5000
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
    0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379

docker-test  docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

CONTAINER ID        IMAGE                COMMAND                  CREATED              STATUS                            PORTS               NAMES
59dc811cc019        dockertest_web       "/bin/sh -c 'python a"   About a minute ago   Exited (137) 6 seconds ago                            dockertest_web_1
9f772dea80aa        redis                "/entrypoint.sh redis"   About a minute ago   Exited (0) 16 seconds ago                             dockertest_redis_1

Entries are still here:

iptables -L -n -v
Chain INPUT (policy ACCEPT 64 packets, 6578 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
0     0 DOCKER     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
0     0 ACCEPT     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
0     0 ACCEPT     all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
0     0 DROP       all  --  docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
Chain OUTPUT (policy ACCEPT 42 packets, 9837 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain DOCKER (1 references)
pkts bytes target     prot opt in     out     source               destination
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379

Another `docker-compose up`:

iptables -L -n -v
Chain INPUT (policy ACCEPT 317 packets, 32548 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
0     0 DOCKER     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
0     0 ACCEPT     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
0     0 ACCEPT     all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
0     0 DROP       all  --  docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
Chain OUTPUT (policy ACCEPT 283 packets, 58144 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain DOCKER (1 references)
pkts bytes target     prot opt in     out     source               destination
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:6379
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:6379
0     0 ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>          tcp dpt:3000
0     0 ACCEPT     tcp  --  !docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>          tcp dpt:80
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:3000
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:3000
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:3000
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:3000
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp dpt:3000
0     0 ACCEPT     tcp  --  docker0 docker0  <IP_ADDRESS>          <IP_ADDRESS>          tcp spt:3000

I'm also not sure why icc=true by default on the docker daemon. It seems no isolation is being provided though the docker-compose docs state that: "Define the services that make up your app in docker-compose.yml so they can be run together in an isolated environment:". It seems that this is not true, or I am overlooking something.

I am running this on my Mac using virtualbox. I created the docker vm with docker-machine.

@falschparker82 @peterkuiper I'm also running 1.6.2 and ran into this same issue twice this week.  Have you been able to figure out any workarounds for this? Thanks

@retornam No I haven't. I just removed the vm and started over. I'm not sure if this was a one-time thing or if I'm still having this problem. If I am I'm just ignoring it :) Have you tried running 1.8.x?

I'm having similar issues with 1.7.1 on CentOS 7. I'm unable to update to docker 1.8.2 because we're running registry 2.1.1 (backed by NFS) and this issue is a blocker.

We have a user seeing this on Docker 1.7.1 on CoreOS. Confirmed that restarting Docker resolves the issue.

What repro steps does the Docker team need to investigate this? It seems pretty easy to have a running container crash and have the daemon not clean up its rules.

@carmstrong I'm not entirely sure a reproducible case for 1.7.x is helpful, unless it's still reproducible on 1.9.x, given that we don't perform back ports to older releases. However, if you're having a minimal test-case, perhaps someone is able to see if it's still reproducible on 1.9.x

Docker version 1.9.1, build a34a1d5
We have come into this issue right now. After some investigations we found exact the same - port forwarding rules still in iptables since container has been crashed hours ago.

Yes I was able to reproduce this with latest master.
I closed the shell where the cotnainer with exposed ports was running and I see libnetwork is not being informed of the container going down. So no cleanup is happening.
The only logs showing are:
DEBU[0577] Closing buffered stdin pipe
DEBU[0577] attach: stdin: end
DEBU[0577] attach: stderr: end
DEBU[0577] attach: stdout: end

USER POLL
The best way to get notified of updates is to use the Subscribe button on this page.
Please don't use "+1" or "I have this too" comments on issues. We automatically
collect those comments to keep the thread short.
The people listed below have upvoted this issue by leaving a +1 comment:
@LRancez

+1

Seeing the same issue on Docker 1.7.1 in CoreOS. Had to manually do a docker run and bind to different  IP/port pairs in order to figure out what was the issue. At the end, I backed up iptables and manually deleted the offending entries and it worked.

This no longer happens in recent docker versions.
If the container crashes, containerd will notify the daemon which in turn will ask libnetwork to release the resources held by the container.
Tested killing the container pid in 1.11.2 and 1.12.1 and the corresponding rules in the nat table are correctly removed.
I think this issue can now be closed.

@aboch Nice, thank you!


Error message needs improvement

The error message when running this code:
from numba import jit
import numba
import numpy

f = numpy.zeros(shape=(3,3,3))

@jit(nopython=True)
def explorethisx(inar, x):
    places = []
    places.append((x,0))
    x1,y1 = x,0
    s = numba.int64(0)
    co = 0
    #for _ in range( 799):

    while co != numba.int16(799):
        co += 1
        a1,a2,a3 = 999,999,999
        a1 = inar[y1 + 1][x1-1][1]
        a2 = inar[y1 + 1][x1][1]
        a3 = inar[y1 + 1][x1 + 1][1]
        m = a1
        ch = -1
        if m > a2:
            m = a2
            ch = 0
        if m > a3:
            m = a3
            ch = 1
        x1 = x1 + ch
        y1 = y1 + 1
        s += inar[y1][x1][1]
        places.append((x1,y1))
    return [s, places]

print explorethisx(f,3)

does not indicate what line number the error is happening on, or what the problem is:
Traceback (most recent call last):
  File "test.py", line 35, in <module>
    print explorethisx(f,3)
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/dispatcher.py", line 309, in _compile_for_args
    raise e
numba.errors.TypingError: Caused By:
Traceback (most recent call last):
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/compiler.py", line 228, in run
    stage()
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/compiler.py", line 442, in stage_nopython_frontend
    self.locals)
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/compiler.py", line 795, in type_inference_stage
    typemap, restype, calltypes = infer.unify()
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/typeinfer.py", line 819, in unify
    check_var(var)
  File "/Users/stan/anaconda/lib/python2.7/site-packages/numba/typeinfer.py", line 806, in check_var
    raise TypingError("Undefined variable '%s'" % (var,))
TypingError: Undefined variable '$313.3'

Failed at nopython (nopython frontend)
Undefined variable '$313.3'

An identical issue has been posted on StackOverflow
Just in case you're wondering what caused this: It's because of the shape-mismatch inside the return [s, places].
A minimal example to reproduce the issue is
from numba import jit

@jit(nopython=True)
def test():
    return [1, [1,2]]

test()

I added a patch at https://github.com/stuartarchibald/numba/commit/c64fcde5c53328266c74d5ddf711306645346a36 which will make the original traceback look like:
Traceback (most recent call last):
  File "issue2237.py", line 43, in <module>
    print(explorethisx(f,3))
  File "<path>numba/numba/dispatcher.py", line 330, in _compile_for_args
    raise e
  File "<path>numba/numba/dispatcher.py", line 307, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "<path>numba/numba/dispatcher.py", line 579, in compile
    cres = self._compiler.compile(args, return_type)
  File "<path>numba/numba/dispatcher.py", line 80, in compile
    flags=flags, locals=self.locals)
  File "<path>numba/numba/compiler.py", line 779, in compile_extra
    return pipeline.compile_extra(func)
  File "<path>numba/numba/compiler.py", line 362, in compile_extra
    return self._compile_bytecode()
  File "<path>numba/numba/compiler.py", line 738, in _compile_bytecode
    return self._compile_core()
  File "<path>numba/numba/compiler.py", line 725, in _compile_core
    res = pm.run(self.status)
  File "<path>numba/numba/compiler.py", line 248, in run
    raise patched_exception
  File "<path>numba/numba/compiler.py", line 240, in run
    stage()
  File "<path>numba/numba/compiler.py", line 454, in stage_nopython_frontend
    self.locals)
  File "<path>numba/numba/compiler.py", line 882, in type_inference_stage
    typemap, restype, calltypes = infer.unify()
  File "<path>numba/numba/typeinfer.py", line 912, in unify
    check_var(var)
  File "<path>numba/numba/typeinfer.py", line 899, in check_var
    raise TypingError(msg % (var, val, loc))
numba.errors.TypingError: Failed at nopython (nopython frontend)
Undefined variable '$238.3', operation: build_list(items=[Var(s, issue2237.py (19)), Var(places, issue2237.py (16))]), location: issue2237.py (41)

and @MSeifert04's minimal reproducer look like:
numba.errors.TypingError: Failed at nopython (nopython frontend)
Undefined variable '$0.5', operation: build_list(items=[Var($const0.1, issue2237.py (5)), Var($0.4, issue2237.py (5))]), location: issue2237.py (5)

if this is considered sufficient to mark the issue fixed I'll add tests and open a PR.

I think that's a good start.  It likely won't be clear to a new user what the problem is, but they will know where it is.  Converting the error into something easier to understand is much harder, and probably beyond the scope of this ticket anyway.

Thanks @seibert. I agree, this is merely a start and creating a better message that contextually describes the problem is another issue. The noted patch is a simple improvement in that it reports the location and operation that caused the problem, I've opened a PR for it https://github.com/numba/numba/pull/2741.


Add AST Functionality

First implementation of the AST-checker, which can search through Java-Files for unwanted:

Loop statements
Conditional statements
Function-based statements
Local class statements
Exception handling statememts
Synchronisation statements

I realize now, that apart from assertThatFile(Path) and assertThatDirectory(Path) another solution might be, as discussed some weeks ago:

assertThat(Path).asFile().hasNo(...) and assertThat(Path).asDirectory().hasNo(...)
assertThat(Path).withConfiguration(AstAssertConfiguration).hasNo(...)

or some similar APIs.
The fluent API and the configuration+builder have the advantage that they are extensible without combinatorial explosion.
Here, it would be easy to add using(Version.JAVA_17) or similar.
The config+builder has the advantage that they can be specified once and then used for every assertion.
But then again, how many of such assertThat statements do we expect a project to have? I would assume that this is 0 or 1 in 99% of the cases, as chaining is always possible.
We can also consider if varargs is a useful addition to hasNo(...).
Please tell me what you think about the suggestions; it would be very interesting to hear of other use cases than students should not be allowed to use any loops. Because this is larger ion scope, so it would be good to know what users might need and expect. Could you ask the users (exercise creators at TUM for EIST/Patterns/PGdP/...) what would be helpful? Maybe @JohannesStoehr has some suggestions as well, he knows both Ares and many instructors fairly well.

Sadly had no time to do a full review, but I hope it helps anyway.
Huge Thanks to @Strohgelaender for reviewing! Much appreciated 👍


Accept authentication via remote_user header

Hey All,
I was wondering if there was a way, or if it could be a feature request, to allow using the built in HTTP authorization for HTTP access based on a passed REMOTE_USER header.
Use case is I already have authentication setup in front of kibana(proxied by Apache) using our orgs kerberos and 2FA authentication.  I'd rather be able to keep the 2FA and just pass the user to Kibana/elastic and have it use the built in HTTP roles backend.

Yes, but for some reason isn't in the docs - I think this needs fixing. Unless they're planning on removing it?!
There is something in the config, or read the docs where the code originally came from: https://docs.search-guard.com/latest/proxy-authentication


[Enhencement](File Reader) delete old file_reader

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.29 seconds
stream load tsv:          474 seconds loaded<PHONE_NUMBER>9 Bytes, about 150 MB/s
stream load json:         40 seconds loaded<PHONE_NUMBER> Bytes, about 56 MB/s
stream load orc:          67 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230228161539_clickbench_pr_105920.html

run buildall


Fixed miner issue at classifier module

Some detectors doesn't detect face as a result there is no 'face' key at object dictionary which raise error.
The key is checked before using.
ERROR:root:'face'   File "/repo/libs/classifiers/classifier.py", line 21, in object_post_process     if object['face'] is not None and classifier_score > self.min_threshold: KeyError: 'face'

@pgrill
@renzodgc


add Alignment.fromstring; remove polymorphism in AlignedSent

This is a possible resolution for #1129

Overall, looks good to me.

@stevenbird Thanks for the new PR. It looks good.

@alvations – I think I inadvertently removed util.py in a different commit. Sorry about that.

AlignedSent.alignment_error_rate() is another polymorphic method; it works with both AlignedSent and Alignment. I think it should only be the latter.

@stevenbird Agree that AlignedSent.alignment_error_rate() should just work with Alignment. #1129 also discusses the possibility of making it a module function. That could be done in this PR, or I could write something after this PR goes in.

Thanks @hoontw, I will do that.

I've added some assertions to produce earlier errors in case people pass an alignment string instead of an Alignment to AlignedSent.

I don't understand why nltk.metrics.recall is not returning None here:
File "...nltk/test/translate.doctest", line 187, in translate.doctest
Failed example:
    recall(Alignment([]), als.alignment)
Expected:
    None
Got nothing

NB len(Alignment([])) == 0

@stevenbird Because a None return value is not printed in the console. Try print(recall(Alignment([]), als.alignment))

I see, thanks @hoontw.
@alvations – would you mind reviewing this PR and merging it if it's ok please?

@stevenbird Looks great! Thanks for cleaning up the polymorphism and the related functions.
@hoontw @kmike Thanks for the reviews.

Now let me try and see whether I can fit in RIBES into the BLEU code. I sort of need it too =) And also a PhraseTable class.


[suggestion] please make drones and turrets not spawn in the void locust

if you have any turrets with you, they'll immediately die when going to the void locust because of the void fog. please make them only spawn in the voidling boss fight when in the deep void.

Done in the latest update.


cb cross package, deadlines

looking for review (@dskinner?), mostly for libsio/cb*
anticipating need to discuss deadlines for capture
the auhal stuff is still only compiled and not yet exported by sio, no need for AUHAL expertise to review unless you want.

all test pass, need to move on to dependent work.   still not exported via top level sio, so merging.


Unrolling circ.to_instruction() removes conditions

Information

Qiskit Terra version: 0.12.0
Python version: 3.6.10
Operating system: macOS Mojave 10.14.6

What is the current behavior?
Building a gate definition that incorporates conditional gates, adding to a circuit and transpiling removes the conditions, changing the outcome
Steps to reproduce the problem
from qiskit import QuantumCircuit, transpile, Aer, execute

box = QuantumCircuit(2, 2)
box.x(0)
box.measure(0, 0)
box.x(1).c_if(box.cregs[0], 0)
box.measure(1, 1)

print(box)

qc = QuantumCircuit(2, 2)
qc.append(box.to_instruction(), qc.qregs[0], qc.cregs[0])

print(qc)

b = Aer.get_backend("qasm_simulator")
qc2 = transpile(qc, b)

print(qc2)

job = execute([box, qc], b)
print(job.result().get_counts(box))
print(job.result().get_counts(qc))

Output:
        ┌───┐┌─┐
q_0: |0>┤ X ├┤M├──────────
        └───┘└╥┘ ┌───┐ ┌─┐
q_1: |0>──────╫──┤ X ├─┤M├
              ║  └─┬─┘ └╥┘
              ║ ┌──┴──┐ ║
 c_0: 0 ══════╩═╡     ╞═╬═
                │ = 0 │ ║
 c_1: 0 ════════╡     ╞═╩═
                └─────┘
        ┌───────────┐
q_0: |0>┤0          ├
        │           │
q_1: |0>┤1          ├
        │  Circuit0 │
 c_0: 0 ╡0          ╞
        │           │
 c_1: 0 ╡1          ╞
        └───────────┘
        ┌───┐┌─┐
q_0: |0>┤ X ├┤M├───
        ├───┤└╥┘┌─┐
q_1: |0>┤ X ├─╫─┤M├
        └───┘ ║ └╥┘
 c_0: 0 ══════╩══╬═
                 ║
 c_1: 0 ═════════╩═

{'01': 1024}
{'11': 1024}

What is the expected behavior?
Building an Instruction from a QuantumCircuit and unrolling should produce the same circuit.
Suggested solutions
Inspecting the instructions in the decomposition shows that they still have the correct data in the condition field, so the error is suspected to be in the unroller but not certain.
NOTE: it is possible to add a c_if to qc.append(...) which is preserved. In theory, to solve this correctly, Qiskit would need to support having multiple conditions, or rather conditions on multiple registers. May be worth looking at this after #1160 is solved to allow conditions to be arbitrary lists of bits. Or allow purely classical operations to allow the appropriate bit manipulation.

This looks like a case of #2784 . In https://github.com/Qiskit/qiskit-terra/blob/4dd47cf/qiskit/transpiler/passes/basis/decompose.py#L66 , inst.condition is set correctly, but apply_operation_back only respects the condition keyword argument.

Thanks @kdk for pointing this out! Resolving #2784 does fix this issue, and the circuits match! Opened a PR for it :)

duplicated #2784


Fix "roulette is now allowed" spam after bulk subgifts

Fixes #958
Also condenses some very blatant code duplication into one method.
Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[x] Documentation in docs/ or install-docs/ was updated, if applicable

Does this also fix my issue for a single sub? 🤔 https://github.com/pajbot/pajbot/issues/944

Probably


Not warning about missing types field

Take the following package.json
{
	"exports": {
		".": {
			"require": "./dist/index.cjs",
			"import": "./dist/index.js"
		}
	},
}

It didn't warn about a missing top level types field or a missing types field in the exports map, it did however warn about a missing types field in the exports map when adding a top level types field

This is kinda intentional because some libraries don't publish types and relies on @types/* packages instead. Or if they don't publish JS at all, e.g. normalizecss.
It does warn when there's a top-level "types" field and none in "exports" because it signals the intent that you do ship types, but your library won't work with "moduleResolution": "bundler", so publint fills in the gap of this missing compatibility.

Ah that makes sense :pray:


Update database drivers

sqlite3 is fetched from GitHub because the maintainers haven't yet published a node-gyp update to npm: https://github.com/mapbox/node-sqlite3/issues/1493

This makes me slightly nervous.  Our automated security will no longer detect as it wont be able to parse npm package version from a repo.
Is that not the case?  Is there a way we can wait/take an alternative approach that doesn't mean using git repo and instead use the npm package?

This makes me slightly nervous. Our automated security will no longer detect as it wont be able to parse npm package version from a repo. Is that not the case?

I don't know what the automated security scanner's capabilities are.

Is there a way we can wait/take an alternative approach that doesn't mean using git repo and instead use the npm package?

We could fork the sqlite3 package (or migrate to better-sqlite3), but that will cause even worse problems. (Users expect npm i sqlite3 to add sqlite support; if we use a different package that will no longer be true.)

I don't know what the automated security scanner's capabilities are.

The synk stuff for example checks npm version number IE if exploit is found in 0.0.1 then it suggests ( by way of PR ) upgrading to the fixed version.  Afaik if we stop using the npm package and use github repo in package.json IE removing "sqlite3": "^5.0.2"`` then synk wont be able to check our package / reference it for security related issues..
I'm not super passionate about this but I think having the security tools is important and useful.

Note that the reason for updating sqlite3 is to fix a security vulnerability in the latest published version. I'm subscribed to the sqlite3 bug, so as soon as a new version is published I will switch back to fetching the package from npm.


Measurement tool

Hello All
is there some documentation or example regarding Measurement tool?
I need to measure the distance between two (or more) points and measure the area.
Thanks.

Nobody need/use this?


Upgrade NullAway 0.10.19 -> 0.10.21

This PR contains the following updates:

Package
Type
Update
Change

NullAway

patch
0.10.19 -> 0.10.21

NullAway
compile
patch
0.10.19 -> 0.10.21

Release Notes

uber/NullAway (NullAway)
v0.10.21
Compare Source
IMPORTANT: This release fixes a crash when running against <2.24.0 release of
Error Prone (see #894) introduced in NullAway v0.10.20 and another crash related to
Checker Framework (see #895) introduced in NullAway v0.10.19.

Fix backwards-incompatible calls to ASTHelpers.hasDirectAnnotationWithSimpleName (#894)
Downgrade to Checker Framework 3.40.0 (#895)

v0.10.20
Compare Source

Fix JSpecify support on JDK 21 (#869)
Build / CI tooling upgrades for NullAway itself:

Update to WALA 1.6.3 (#887)
Update to Error Prone 2.24.1 (#888)

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade NullAway 0.10.19 -> 0.10.20

See:
- https://github.com/uber/NullAway/blob/master/CHANGELOG.md
- https://github.com/uber/NullAway/releases/tag/v0.10.20
- https://github.com/uber/NullAway/compare/v0.10.19...v0.10.20

Version 0.10.21 LGTM too.


[AutoRelease] t2-servicebus-2022-08-25-39352(Do not merge)

100
Live test fail, detailed info is in pipeline log(search keyword FAILED)!!!
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1021
BuildTargetingString
azure-mgmt-servicebus
Skip.CreateApiReview
true

issue link:100


Migrating to modules (and away from namespaces)

Closes #4.
(The last half of which is no longer required, since we still support all those forms when targeting ES6 now, provided you choose a non-ES6 module kind.)

I copied and updated this PR into #185 in appendices/Modules.md. When that PR merges we should probably close this one.

Cool, I'll just close this one now.


minor changes to utils.py

refactor the direct use of call to args[0] instead of calling API method .value() for bool var
refactor is_bool, is_int, is_num so there is no code duplication
add few space to comply with PEP 8

Looks good to me!

Ok, let's merge then. @Wout4 feel free to merge immediately after having a look. One person's approval is plenty for these kind of changes.


CodeBLEU: the order of normalized variables might affect the data flow match score

Please take a look at the following example:

ref = "
if ( db . getCollectionNames () . contains ( collectionName ) ) {
db . getCollection ( collectionName ) . drop () ;
mongoDBCollections . remove ( collectionName ) ;
}"
example1 = "
if ( ( collectionName != null ) && ( ! ( db . getCollectionNames () . contains ( collectionName ) ) ) ) {
db . getCollection ( collectionName ) . drop () ;
mongoDBCollections . remove ( collectionName ) ;
}"
example2 = "
if ( ( ( db ) != null ) && ( ! ( db . getCollectionNames () . contains ( collectionName ) ) ) ) {
db . getCollection ( collectionName ) . drop () ;
mongoDBCollections . remove ( collectionName ) ;
}"

For example 1 here is the data flow graph and score:

ref dfg:
[('db', 2, 'comesFrom', [], []), ('collectionName', 10, 'comesFrom', [], []), ('db', 14, 'comesFrom', ['db'], [2]), ('collectionName', 18, 'comesFrom', ['collectionName'], [10]), ('collectionName', 29, 'comesFrom', ['collectionName'], [10])]
cand dfg:
[('collectionName', 3, 'comesFrom', [], []), ('db', 11, 'comesFrom', [], []), ('collectionName', 19, 'comesFrom', ['collectionName'], [3]), ('db', 25, 'comesFrom', ['db'], [11]), ('collectionName', 29, 'comesFrom', ['collectionName'], [3]), ('collectionName', 40, 'comesFrom', ['collectionName'], [3])]
Normalized ref dfg:
[('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_1', 'comesFrom', ['var_1'])]
Normalized cand dfg:
[('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_0', 'comesFrom', ['var_0']), ('var_0', 'comesFrom', ['var_0'])]
0.709 | 0.973 | 0.875 | 0.800 > 0.839
83.91522695531542

For example 2, here is the data flow graph and score

ref dfg:
[('db', 2, 'comesFrom', [], []), ('collectionName', 10, 'comesFrom', [], []), ('db', 14, 'comesFrom', ['db'], [2]), ('collectionName', 18, 'comesFrom', ['collectionName'], [10]), ('collectionName', 29, 'comesFrom', ['collectionName'], [10])]
cand dfg:
[('db', 4, 'comesFrom', [], []), ('db', 13, 'comesFrom', ['db'], [4]), ('collectionName', 21, 'comesFrom', [], []), ('db', 27, 'comesFrom', ['db'], [4]), ('collectionName', 31, 'comesFrom', ['collectionName'], [21]), ('collectionName', 42, 'comesFrom', ['collectionName'], [21])]
Normalized ref dfg:
[('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_1', 'comesFrom', ['var_1'])]
Normalized cand dfg:
[('var_0', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_1', 'comesFrom', ['var_1'])]
0.675 | 0.973 | 0.875 | 1.000 > 0.881
88.08105911288919

You can see data flow match for ex1 is 0.8 and 1.0 for ex2. Based on the algorithm, they should have the same score 1.0 because they both cover all the data flows in reference. The difference is because of the order of variables after normalization, i.e. var_0 in ex1 is var_1 in ex2. Is it an unexpected behavior?
Thanks!

Hi, thanks for your question. I wonder if there is some data format error in your examples because I wrote a test file to repeat the behavior, but I got two 1.0 match scores.
The test script is:
import dataflow_match
ref = ["if ( db . getCollectionNames () . contains ( collectionName ) ) { db . getCollection ( collectionName ) . drop () ; mongoDBCollections . remove ( collectionName ) ; }"]
example1 = "if ( ( collectionName != null ) && ( ! ( db . getCollectionNames () . contains ( collectionName ) ) ) ) { db . getCollection ( collectionName ) . drop () ; mongoDBCollections . remove ( collectionName ) ; }"
example2 = "if ( ( ( db ) != null ) && ( ! ( db . getCollectionNames () . contains ( collectionName ) ) ) ) { db . getCollection ( collectionName ) . drop () ; mongoDBCollections . remove ( collectionName ) ; }"
print('======================= example:1 =======================')
score1 = dataflow_match.calc_dataflow_match(ref, example1, 'c_sharp')
print('======================= example:2 =======================')
score2 = dataflow_match.calc_dataflow_match(ref, example2, 'c_sharp')
print('======================= DF match score =======================')
print(score1, score2)
And I print the DFGs and normalized DFGs during the calculation. The final output is:
======================= example:1 =======================
Reference DFG: [('db', 2, 'comesFrom', [], []), ('collectionName', 10, 'comesFrom', [], []), ('db', 14, 'comesFrom', ['db'], [2]), ('collectionName', 18, 'comesFrom', ['collectionName'], [10])]
Candidate DFG: [('collectionName', 3, 'comesFrom', [], []), ('db', 11, 'comesFrom', [], []), ('collectionName', 19, 'comesFrom', ['collectionName'], [3]), ('db', 25, 'comesFrom', ['db'], [11]), ('collectionName', 29, 'comesFrom', ['collectionName'], [3]), ('collectionName', 40, 'comesFrom', ['collectionName'], [3])]
Normalized reference DFG: [('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1'])]
Normalized candidate DFG: [('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_0', 'comesFrom', ['var_0']), ('var_0', 'comesFrom', ['var_0'])]
======================= example:2 =======================
Reference DFG: [('db', 2, 'comesFrom', [], []), ('collectionName', 10, 'comesFrom', [], []), ('db', 14, 'comesFrom', ['db'], [2]), ('collectionName', 18, 'comesFrom', ['collectionName'], [10])]
Candidate DFG: [('db', 4, 'comesFrom', [], []), ('db', 13, 'comesFrom', ['db'], [4]), ('collectionName', 21, 'comesFrom', [], []), ('db', 27, 'comesFrom', ['db'], [4]), ('collectionName', 31, 'comesFrom', ['collectionName'], [21]), ('collectionName', 42, 'comesFrom', ['collectionName'], [21])]
Normalized reference DFG: [('var_0', 'comesFrom', []), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1'])]
Normalized candidate DFG: [('var_0', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', []), ('var_0', 'comesFrom', ['var_0']), ('var_1', 'comesFrom', ['var_1']), ('var_1', 'comesFrom', ['var_1'])]
======================= DF match score =======================
1.0 1.0
which shows both of the data-flow match scores are 1.0.

Hi, thanks for your response!
First, it is actually a piece of java code, so you might want to change
score1 = dataflow_match.calc_dataflow_match(ref, example1, 'c_sharp') to java.
Second, can I ask which version of tree-sitter you are using? I got this error while trying to run the test script with code in this repo, when I specified the language to Java:

ValueError: Incompatible Language version 11. Must be between 13 and 13

Thanks!

Hi, thanks for your response!
First, the example is actually java snippet rather than c_sharp.
Second, can I ask which version of tree-sitter you are using? It seems the version will affect the results? I got different scores with 0.2.1

Hi,
(1) I switched to java, and the problem you mentioned occurred. The normalized method is nontrivial and the current method relies on the order of variables before normalization. The best way is probably to enumerate all normalized numbers and calculate the maximum match score, but this is unrealistic. Actually, it is a hard problem to calculate the semantic match score, which needs a deep understanding of the code snippet. In the future, we may use the scores generated with deep models (such as BERTScore) as a supplement to BLEU-style scores for the semantic match.
(2)The version of tree-sitter we are using is 0.1.1. Different versions may affect the result because of the language change.


[Bug] LuckPerms API: Get prefix provide an NPE

Hello, I'm trying to get Prefix of Player with LuckPerms API.
I tried this:  user.getCachedData().getMetaData().getPrefix();
and it provides an NPE on this line.
I'm using purpur 1.16.5 as server software.
Latest build of LP.

I imagine user is probably null.
https://luckperms.net/wiki/Developer-API-Usage#obtaining-a-user-instance

I imagine user is probably null.
https://luckperms.net/wiki/Developer-API-Usage#obtaining-a-user-instance

I tried this, but I have same problem


Question about a alarm

Great little tool ! I really don't know much about python but I tried to compile the code for alarm sounds and although I can get it to work it bugs things out. At the top of the script I added :
from playsound import playsound
then in the helltide section I added the code for the playsound wave file, and it works but the timer then bugs out.
def update_timer(self):
        next_event, is_active = get_next_helltide_event(self.helltide_times)
        if next_event:
            now = datetime.utcnow().replace(tzinfo=pytz.utc)
            if is_active:
                remaining_time = (next_event + timedelta(hours=1)) - now
                self.label.config(text=f"Helltide Active: {str(timedelta(seconds=round(remaining_time.total_seconds())))}")
                playsound('Helltide-Alarm.wav')
            else:
                remaining_time = next_event - now
                self.label.config(text=f"Until Next Helltide: {str(timedelta(seconds=round(remaining_time.total_seconds())))}")

And for the Boss, an alert like 5 minutes before the pop would be great, but no clue on if that's possible. Any help would be great! Thanks

I was actually going to add an alert sound already so I would just hold tight until I update, it wont be that difficult.


Implement healthchecks; switch to v1 for admission hooks api

Codecov Report

Merging #46 (5c159df) into master (790a613) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #46   +/-   ##
=======================================
  Coverage   76.79%   76.79%
=======================================
  Files           8        8
  Lines         418      418
=======================================
  Hits          321      321
  Misses         63       63
  Partials       34       34

Impacted Files
Coverage Δ

core/dragnetwebhook.go
0.00% <ø> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #46 (5c159df) into master (790a613) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #46   +/-   ##
=======================================
  Coverage   76.79%   76.79%
=======================================
  Files           8        8
  Lines         418      418
=======================================
  Hits          321      321
  Misses         63       63
  Partials       34       34

Impacted Files
Coverage Δ

core/dragnetwebhook.go
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


Test changes for "Use local locks where possible for local temp tables."

Description
[Describe what this change achieves - Guidelines below (please delete the guidelines after writing the PR description)]

What is the change? This is best described in terms of “Currently, Babelfish does X. With this change it now does Y.” Think of “What did it used to do?” and “What does it do now?”

Why was the change made? What drove our desire to put effort into the change?
How was the code changed should only appear for large commits. This can serve as a rough roadmap to what’s contained in the commit. It should be very high level; if it’s directly referencing code it’s probably too detailed. It’s also critical that this section of a commit message does not try to replace proper code documentation (ie, block comments or README files). Generally, this section should only appear if the commit itself is large enough that it’s helpful to provide a roadmap to someone looking at the commit.
The last descriptive piece is the “title” for the commit: the very first line of the commit message, which should typically be less than 80 characters. A good title is critical, because it’s the only thing that shows up in places like the Github commit listing. No one’s got time to read through full commit messages when trying to find a single commit out of dozens.

Issues Resolved
[List any issues this PR will resolve]
Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 73.339%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
42902

Relevant Lines:
58498

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 73.342%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
42966

Relevant Lines:
58583

💛  - Coveralls


Question about 360 degree OBB

Hey there! Nice work on this project and accompanying blog post!
I've been working on a project using YOLOv5 OBB, which I see you've mentioned as inspiration in this project's README. As I'm sure you've seen, the author of YOLOv5 OBB has gone MIA. Because this code base resembles YOLOv5 OBB so much, I was wondering if you might have some insight/advice on a problem I'm working on:
My dataset contains objects with a distinct orientation -- there's both a clear top and bottom to these objects. I'd like to use a YOLO model to find the orientation of these objects given their top and bottoms. One way I thought of doing this was tweaking the model code to predict angles within [-180, 180) degrees (360 degrees). However, it looks like someone had a similar idea a few years ago and asked the original YOLOv5 OBB author about this here. He explains that "the angle range of [0, 360) will lead to ambiguity problems (the results of a rectangular frame rotated 180 degrees in place and rotated 360 degrees are exactly the same), which is not conducive to network learning," and his advice is then to "add 4 additional channels to the detect class, specifically used to predict the order of the four points of the rotating frame to determine the head of the object." I've spent some time combing through the YOLO model code, and I can't get an actionable grasp on what he means.
I know that the DOTA dataset (used to benchmark YOLOv5 OBB) orders obb points as top left, bottom left, bottom right, top right. I've done the same with my dataset. As he said, I'd imagine there must be a way including training the model to predict the order of the points of a detected bounding box, but I'm not totally sure of how to do that or where to include that in the Detect class code. After your time with this code, do you have any advice or guidance you would be willing to offer me? Thanks in advance!

@dorgun please comment when you have time and ideas regarding the question.


[saas]: (feat): First Org Flow, Dummy User Dashboard

#4  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @alifarooq9 and the rest of your teammates on  Graphite


db: Set sslmode to require for the clouddot deployment

GCP succeeded in run 5, and aws in run 6. Merging


CI cmake_macos_cpu fails with UnsatisfiableError

🐛 Describe the bug
The latest main branch fails on cmake_macos_cpu with:
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:

Specifications:

  - pytorch=1.12.0.dev20220313 -> python[version='>=3.8,<3.9.0a0']

Your python: python=3.9

If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.

The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package mkl conflicts for:
numpy -> mkl[version='>=2018.0.0,<2019.0a0|>=2018.0.1,<2019.0a0|>=2018.0.2,<2019.0a0|>=2018.0.3,<2019.0a0|>=2019.1,<2020.0a0|>=2019.3,<2020.0a0|>=2019.4,<2020.0a0|>=2021.2.0,<2022.0a0|>=2021.3.0,<2022.0a0|>=2021.4.0,<2022.0a0']
pytorch=1.12.0.dev20220313 -> mkl[version='>=2018']

Package blas conflicts for:
numpy -> blas[version='*|*|1.0|1.0',build='mkl|openblas|mkl|openblas']
pytorch=1.12.0.dev20220313 -> blas=[build=mkl]

Package tzdata conflicts for:
numpy -> python[version='>=3.10,<3.11.0a0'] -> tzdata
python=3.9 -> tzdata

Versions
Latest main branch 05b5e8c

Hmm, something tells me this problem is broader than just python-3.9... trying to debug right now


Example test case for Swift 2.2 to Swift 3.0

first question, is this undebt only work for python code? if it work for other language that is "pyparsing grammar object"
for example in current swift 2.2, it is written like below
if let x = y, a = b where a == x {
how to use "undebt" to parse above line to below line?
if let x = y, let a = b, a == x {

Hi @steve21124 good question. Undebt can work on any language. It is a find-and-replace tool based on a grammar which you define (in python) and then run on your desired input (in any language).

Thank you for the quick response. do you have some tips to get started to solve one example issues above?

@steve21124 I would suggest looking through the various examples provided with Undebt. They should give you an idea of how to write pattern files.

@steve21124 In #28 @ajm188 just added an implementation of the pattern you're looking for in the examples packaged with Undebt. You can take a look here: https://github.com/Yelp/undebt/blob/master/undebt/examples/swift.py


Bree/10tier3workloads

Description
This is a quick implementation of adding a tier 3.  Things like automatically performing additive deployments aren't available yet and will need to be considered when re-architecting the system.
Changes include adding tier3 variables where possible to be used for a quick deployment,  as well as a template set, and a script for deploying a tier 3.   deploy_t3.sh scrapes together various sections of other scripts to automate the deployment and application of the tier.
Issue reference
The issue this PR will close: #10
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles or validates correctly
[X] BASH scripts have been validated using shellcheck
[X] All tests pass (manual and automated)
[X] The documentation is updated to cover any new or changed features
[X] Markdown files have been linted using the recommended linter. (See .vscode/extensions.json.)
[X] Relevant issues are linked to this PR

be sure to update the PR title to something descriptive, this is what makes it into the git log 👍

Do you want some help updating the guidance? I can assist on that.

Wait, it's already there. I missed it the first time. Sorry. 😄


problem when start cluster

when start a cluster, I account the problem as follow:
Unexpected startup failure: An unexpected error occurred while setting up the cluster. If the problem persists, please try again and contact Databricks.
How can I solve this problem? Thanks for your help.

The detail information is:
Unable to add 1 container to the cluster. Will attempt to retry: false. Reason: Unexpected startup failure

You probably don't have quota with the cloud provider. Click the "Event Logs" for the cluster and click the failure to see details.

It says that 'ADD_NODES_FAILED: Unable to add 1 container to the cluster. Will attempt to retry: false. Reason: Unexpected startup failure. Internal error message: Timeout while placing nodes.' Does it mean that I don't have quota with the cloud provider? Thanks for your help.

Hm. That could mean that it wasn't able to provision the node. That isn't a quota problem, I believe. Can you try again?


ISPN-9357 404 returned from REST for caches with object storage and non…

…-string keys
https://issues.jboss.org/browse/ISPN-9357

Included in #6137


[Bug]: Filepicker doesn't show files in it's pop-up when the user goes to a query page and comes back

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When i upload a file in filepicker and go to the query/api page and come back, I can see the number of files uploaded in the button but don't see the files in the pop-up.
Either reset the filepicker or show the files uploaded, the current state is weird.
Steps To Reproduce

Upload a file to filepicker
Navigate to query page
Come back to the widget
Open the pop-up
See that the file is not shown

Loom -

Environment
Production
Version
Cloud

similar to #11129

Stats

Stat
Values

Reach
400

Effort (months)
1


[CRASH]  RCNConfigFetch.m - Line 113

Unity editor version: 2020.3.13f1
Firebase Unity SDK version: 8.7.0
Source you installed the SDK: .unitypackage
Problematic Firebase Component: RemoteConfig (Auth, Database, etc.)
Other Firebase Components in use: Analytics,RemoteConfig,Messaging,Crashlytics
Additional SDKs you are using:Facebook,Facebook Audience Network, Admost Mediation
Platform you are using the Unity editor on: Mac
Platform you are targeting: iOS
Scripting Runtime: IL2CPP

Crashlytics crash details;
Crashed: IL2CPP Threadpool worker
0  libobjc.A.dylib                0x2840 objc_retain + 16
1  libsystem_blocks.dylib         0x197c _Block_object_assign + 240
2  libsystem_blocks.dylib         0x175c _Block_copy + 252
3  libdispatch.dylib              0x632b8 _dispatch_Block_copy + 28
4  libdispatch.dylib              0x7cbc dispatch_async$VARIANT$mp + 52
5  CFNetwork                      0x15ce0 CFHTTPCookieCopyName + 2348
6  FirebaseRemoteConfig           0x11f7c -[RCNConfigFetch recreateNetworkSession] + 113 (RCNConfigFetch.m:113)
7  FirebaseRemoteConfig           0x9d70 -[FIRRemoteConfig configSettings] + 545 (FIRRemoteConfig.m:545)
8  UnityFramework                 0x1d0a674 firebase::remote_config::internal::RemoteConfigInternal::GetConfigSettings() const + 40
9  UnityFramework                 0x1d0ddb8 Firebase_RemoteConfig_FirebaseRemoteConfigInternal_GetConfigSettings + 20
10 UnityFramework                 0x21d03a0 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
11 UnityFramework                 0x21d0330 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
12 UnityFramework                 0x20032b4 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
13 UnityFramework                 0xeb08c RuntimeInvoker_TrueVoid_t700C6383A2A510C2CF4DD86DABD5CA9FF70ADAC5(void ()(), MethodInfo const, void*, void**) + 44728 (Il2CppInvokerTable.cpp:44728)
14 UnityFramework                 0x1ce8820 il2cpp::vm::Runtime::Invoke(MethodInfo const*, void*, void**, Il2CppException**) + 76156
15 UnityFramework                 0x14eda64 scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 2350092
16 UnityFramework                 0x14f881c ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 2394564
17 UnityFramework                 0x150479c MonoBehaviour::InvokeMethodOrCoroutineChecked(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingExceptionPtr*) + 2443588
18 UnityFramework                 0x1504a1c MonoBehaviour::InvokeMethodOrCoroutineChecked(ScriptingMethodPtr, ScriptingObjectPtr) + 2444228
19 UnityFramework                 0x14f9564 Scripting::SendScriptingMessage(GameObject&, char const*, ScriptingObjectPtr) + 2397964
20 UnityFramework                 0x14f9298 Scripting::BroadcastScriptingMessage(GameObject&, char const*, ScriptingObjectPtr) + 2397248
21 UnityFramework                 0x1563518 GameObject_CUSTOM_BroadcastMessage(ScriptingBackendNativeObjectPtrOpaque*, ScriptingBackendNativeStringPtrOpaque*, ScriptingBackendNativeObjectPtrOpaque*, int) + 2832064
22 UnityFramework                 0x230b5e8 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
23 UnityFramework                 0x2e89b4c flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
24 UnityFramework                 0x2ee3028 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
25 UnityFramework                 0x2f81440 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
26 UnityFramework                 0x2e8a1f0 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
27 UnityFramework                 0x2e8a02c flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
28 UnityFramework                 0x2e99a78 flatbuffers::IDLOptions::IDLOptions() (.cold.1) +<PHONE_NUMBER>
29 UnityFramework                 0xeb6e0 RuntimeInvoker_FalseSByte_t928712DD662DC29BA4FAAE8CE2230AFB23447F0B(void ()(), MethodInfo const, void*, void**) + 44909 (Il2CppInvokerTable.cpp:44909)
30 UnityFramework                 0x1cb7760 worker_thread(void*) + 2596
31 UnityFramework                 0x1cde8ec il2cpp::vm::ThreadStart(void*) + 35400
32 UnityFramework                 0x1cb8f8c il2cpp::os::Thread::RunWrapper(void*) + 8784
33 UnityFramework                 0x1cbb820 il2cpp::os::ThreadImpl::ThreadStartWrapper(void*) + 19172
34 libsystem_pthread.dylib        0x2458 _pthread_start + 116
35 libsystem_pthread.dylib        0xab0 thread_start + 8
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Steps to reproduce:
-Open the game and crash.
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? %50
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
As soon as you open the app screen goes gray and after 10 seconds shuts down.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

Hi @ygttiramisu, thanks for reporting. We'll try to investigate and see what we can find.

Hi @argzdev! Is there any update about the issue?

Hi @ygttiramisu,
In order to identify what's causing this issue, could you provide a minimal, reproducible example of your project along with the complete steps to replicate this behavior?


track the emergence of openshift using graphical techniques

In this PR we added a notebook where we used centrality algorithms like PageRank and Betweenness centrality to identify emerging projects and user groups in connection to well-known projects.
Using examples of well-known projects, we were able to track the emergence of OpenShift as the downstream of Kubernetes. We include a comparative study of different algorithms & representation techniques for this task.
closes #174
closes #173

@oindrillac any objections to me merging this?

@cdolfi None, please go ahead. Thanks!


Added toInteger fn

@grewalr Why is there three commits with the message Added toInteger fn and two commits with the message Removed passed scenarios from blacklist? It seems like a consequence of some merging/rebasing; can this be cleaned up?

 I'll take a look at aggregating those commits.


About the original audio files

Hi, I'm greatly admiring and grateful for the quality of the dataset and your team's efforts behind it.
I wonder to know how can I access the original audio data? In the Index File, you list the song name and the artist. So only I can do is to search the audio on some music apps?

Sorry for the late reply!
Yes, because of the copyright issue, we cannot release the audio files. The only way to can do is to search for each song name and get the song from online platform, if you have right to download those files in legal.


Updated VsTestV3 task to version - 3.210.0

Task name: VsTestV3
Description:
Updated TestAgent version from {17144597} to {18241129}
https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=18241129&view=results
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) N
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

/azp run

/azp run


Chore/changelogs

Include missing changelogs and generate changelog per package when publishing.

Fixed same issue like in https://github.com/lmc-eu/code-quality-tools/pull/44 => merging.


Fix update timer

Turns out that we just needed to write the updated config to the config file for it to update. Fixes #79

Coverage increased (+0.04%) to 65.365% when pulling 42abf16036f1abcd7e50495a8c19bc95e857f826 on fix-update-timer into f628ed1e517ebd5d3f7982a3981a25bc825f909a on master.

Updates included in #87


Exit Code 1

Every time I click play, it loads then tells me that the game has crashed because of a unexpected issue, I'm not sure why it's doing this. I tired playing Additive 1.20.6 and it works perfectly fine

I figured out the problem!


Add journald logging datatypes on non-Linux

These need to be available in some cases.

Can we just use https://github.com/obsidiansystems/rhyolite/pull/7 instead?

IIRC depending on journald in cabal prevents mac support so using a cabal flag as #7 does allows you to choose this at the dependency level.

As I commented on https://github.com/obsidiansystems/rhyolite/commit/345a0e2da57c906d93d1b10d3d8a34ff14e71d2d, I think that turning of a compiler error into a runtime error was a bad idea, and that was the domino that necessitates this. @3noch's proposal to be static and explicit (say what you mean in the CPP) is I think the right approach, and in the opposite direction.

I don't see how introducing a cabal flag improves the situation besides making things more confusing. The issue was introduced in https://github.com/obsidiansystems/rhyolite/commit/345a0e2da57c906d93d1b10d3d8a34ff14e71d2d. I guess it's debatable whether it should be a runtime error or a type error though...

Are users ever expected to write code that uses this constructor? If so, I'd rather not force CPP into user code, but if not we can revert https://github.com/obsidiansystems/rhyolite/commit/345a0e2da57c906d93d1b10d3d8a34ff14e71d2d and replace with another approach.

What happened to this commit, I wonder: https://github.com/obsidiansystems/rhyolite/commit/9146836b34307498ff93e2db819b183781992958 @luigy

Haha we've implemented the same thing multiple times!

Closing in favor of #38


group_concat is incorrectly declared as String, instead of String?

First of all, thank you for a great library!

what you were trying to do
I'm using this select on @DriftDatabase(queries) :

select
    first_table.name as some_name,
    first_table.id as some_id,
    group_concat(second_table.name) as names
from first_table
    left join second_table on second_table.some_id = first_table.id
group by first_table.id

what you would have expected to happen
I expected to get a table of some_name, some_id, names even with null names

what actually happened
I'm getting null for all data, not even an empty list, if I don't wrap group_concat in IFNULL:

IFNULL(group_concat(second_table.name), '') as names

The first SQL is working correctly outside of drift:

some_name
some_id
names

qwer
1
A,B

asdf
2
NULL

zxcv
3
NULL

Thanks, fixed in bdf0dc998597c7ef0477b6c57385c4c0173f20a1.


The call to Connect broke responses when proxies are involved

Thanks so much for getting involved.
Please make 2 small changes:

This project uses tabs (not spaces) please change your PR to use tabs for indentation

For efficiency, please change the 3 LINQ method calls to 1 FirstOrDefault call
hostIP = host.AddressList.FirstOrDefault(a => a.AddressFamily == AddressFamily.InterNetwork);
if (hostIP != null)
    ...

Once you make these changes and we verify with a couple manual tests we'd be happy to merge this.
Thanks again @nojan1 for contributing!

Good catch on the LINQ issue! Wasn't aware Visual Studio used spaces by default...I think it is fixed now though.

I am going to go ahead and merge this.  We found an issue during testing but it's in the existing code so we are going to look into fixing it.


nftables: 0.8 -> 0.8.2

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft -h got 0 exit code
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft --help got 0 exit code
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft -v and found version 0.8.2
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft --version and found version 0.8.2
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft -h and found version 0.8.2
ran /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin/nft --help and found version 0.8.2
found 0.8.2 with grep in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2
found 0.8.2 in filename of file in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2

cc "@wkennington"

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘nftables-0.8.2’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/os-specific/linux/nftables/default.nix:23 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2
shrinking /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/sbin/nft
gzipping man pages under /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/sbin
patching script interpreter paths in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2
checking for references to /tmp/nix-build-nftables-0.8.2.drv-0 in /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2...
moving /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/sbin/* to /nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2/bin
/nix/store/ahcr1zyg4sp38rwch6vvvziwm9afj2ja-nftables-0.8.2

Success on aarch64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2
shrinking /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2/sbin/nft
gzipping man pages under /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2/share/man/
strip is /nix/store/viv0il4zpdqj4p7yamwbmn2k9pb8dcnv-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2/sbin
patching script interpreter paths in /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2
checking for references to /build in /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2...
moving /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2/sbin/* to /nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2/bin
/nix/store/vj4pf8mlk84majyrqikscz24bh417lxi-nftables-0.8.2


Docs links return 404

Hi, the docs links in the readme (https://invenia.github.io/LibPQ.jl/stable/ and https://invenia.github.io/LibPQ.jl/dev/) currently return 404.
Also, it looks like the CI badge should be updated to use GitHub Actions instead of Travis.

Hi, the docs links in the readme (invenia.github.io/LibPQ.jl/stable and invenia.github.io/LibPQ.jl/dev) currently return 404.
Also, it looks like the CI badge should be updated to use GitHub Actions instead of Travis.

Seems that the repository was recently moved, check https://iamed2.github.io/LibPQ.jl/stable/ out

Thanks @pankgeorg

Looks like this was fixed in cb89002d774c27c317de09118f78010d76262d95 - thanks @iamed2


Copilot natural language chat agent

Create a copilot chat agent to do most of the actions we do in the VSCode extension but using natural language

POS-10


Always exclude stub variables from selection

Since we can use polars selectors, like polars.selectors.all(), we need to remove stub variables from selection. Otherwise, we will erroneously try to include them in things like spanners.

I think this is resolved by https://github.com/posit-dev/great-tables/pull/49 (in v0.1.1)


ESM and CommonJS release

This does much better compatibility between ESM and CommonJS modules in the JS ecosystem. I also found some functions not getting exported correctly. Not sure how tests ever passed. Also, I have the test be ESM and the bench be CJS just to make sure they stay working. The source is TS now though.
I'm going to have a look at usearch next.
Please squash. :)

Don't approve this just yet. I went to use this same logic on usearch and had issues. I think I may go to plain prebuild rather prebuildify.


Pre-release stage should include link to generated PR

The Update security-partners-dotnet task generates a PR with the changes for the release. It would be helpful if it also included a link to the PR in the output to easily navigate to the PR (and cross-reference for troubleshooting purposes).

FYI @MichaelSimons, @mthalman we will ask @ali-turan7 to help us with this and onboard him onto the project

The response to the request for the establishment of a PR is recorded and parsed. The PR URL is built and printed using the information obtained.


Add README and supported python versions to PyPI description

Fix #256.

Per #259, updated operating system classifiers so users are aware Windows is not currently supported.

@kwlzn Good catch, updated PR to appropriately.

LGTM!

merged! thanks @johnthagen!