bug: instructions on https://millionjs.org/docs/api/extra/morph doesn't work

Describe the bug
The example from https://millionjs.org/docs/api/extra/morph doesn't work because it cannot find the morph function.
To Reproduce

create a html page
copy and paste the script example from https://millionjs.org/docs/installation
replace the contents with https://millionjs.org/docs/api/extra/morph taking care to use the full URL for the import
run in Chrome
see the JavaScript error in the console

Expected behavior
Examples should be copy-and-pasteable ;-)
Additional context
Looking at the other extensions, it seems there are additional files that might be needed, so I guessed at the following:
import { m, patch, createElement } from "https://cdn.skypack.dev/million";
import { morph } from "https://cdn.skypack.dev/million/morph"; // GUESS
alert("million"); // THIS WORKS
const node1 = document.createElement("div");
const node2 = document.createElement("div");
node2.textContent = "Hello World";

morph(node2, node1); // THIS FAILS

morph("
Goodbye World
", node2);

Hey! Sorry for the late response. On this issue now

Fixed in #274

Thanks @aidenybai


Read TDM /TDX files to pandas dataframe

Hi,
I would like to read TDM and TDX files with python, store the data in a pandas dataframe, modify and plot it and later export it.
First I tried to get the given example code running:
import TDMtermite
import re
import json
try :
jack = TDMtermite.tdmtermite(b'samples/SineData.tdm',b'samples/SineData.tdx')
except RuntimeError as e :
print("failed to load/decode TDM files: " + str(e))
list ids of channelgroups
grpids = jack.get_channelgroup_ids()
grpids = [x.decode() for x in grpids]
print("list of channelgroups: ",grpids)
for grp in grpids :
# obtain meta data of channelgroups
grpinfo = jack.get_channelgroup_info(grp.encode())
print( json.dumps(grpinfo,sort_keys=False,indent=4) )

# write this channelgroup to file
try :
    grpname = re.sub('[^A-Za-z0-9]','',grpinfo['name'])
    grpfile = "channelgroup_" + str(grp) + "_" + str(grpname) + ".csv"
    jack.print_channelgroup(grp.encode(),      # id of group to be printed
                            grpfile.encode(),  # filename
                            True,              # include metadata as fileheader
                            ord(' ')           # delimiter char
                            )
except RuntimeError as e :
    print("failed to print channelgroup: " + str(grp) + " : " + str(e))

=============================
This raises the error:
File "TDMtermite.pyx", line 40, in TDMtermite.tdmtermite.print_channelgroup
TypeError: print_channelgroup() takes exactly 5 positional arguments (4 given)
I do not really get how to access the data read in with TDMtermite and convert it to a pandas dataframe.
Could you give me some advice please?
BR
Bert

Sorry for the really bad formatting, I tried to fix it but couldn't


After 0.30, it takes endless time to build nushell on windows wsl

After I upgrade shadow-rs from 0.29 to 0.31(or 0.30), it takes endless time to build nushell project
 Updating crates.io index
     Locking 1 package to latest compatible version
    Updating shadow-rs v0.29.0 -> v0.31.1
   Compiling shadow-rs v0.31.1
   Compiling nu-cmd-lang v0.96.2 (/home/windsoilder/projects/nushell/crates/nu-cmd-lang)
    Building [=======================> ] 451/454: nu-cmd-lang(build)

And I notice that there are some zombie processes while building it, it works fine on 0.29

After confirmed, it can't be reproduce on windows nor mac.

@WindSoilder
From version 0.29.0 to 0.30.0 of shadow-rs, the main addition was the ability to retrieve values with the command 'cargo metadata --format-version 1'. Detailed comparison link: https://github.com/baoyachi/shadow-rs/compare/v0.29.0...v0.30.0
To reproduce the issue caused by the change from version 0.29.0 to 0.30.0 of shadow-rs, follow these steps:

First, enter the Winnow WSL system and in the terminal, run this command to check if it can successfully retrieve the value. If it does not succeed, first check for network issues:
~ cargo metadata --format-version 1

Lock the shadow-rs version for both dependencies and build-dependencies in your Cargo.toml file to version 0.30.0.
[dependencies]
...
shadow-rs = { version = "=0.30", default-features = false }

[build-dependencies]
shadow-rs = { version = "=0.30", default-features = false }

Run cargo build to see if the problem you mentioned occurs.

You'll need to perform these steps on your machine. If you encounter any issues or need further assistance, feel free to ask.

Hmm...It's strange that I can't reproduce it today.  Sorry for the disturb, I will close it


[Task]: Add module instances in Git file structure

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

Covered in #26469


Is it possiable for fastlane to auto download all crash logs and dsym them?

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Currenlty with Xcode -> Organizer, you have to select each version of your app for it to download the crash data. Can fastlane automate this so i can 1) script it to auto download all crash data for all versions as they exist and 2) be able to dsym them after using fastlane refresh_dsyms?

@rcmpayne We do not currently have this feature in fastlane. Just curious (since I don't use those very heavily) but how would you be planning to view/use the logs after downloading them with fastlane? 😊


Neovide Support

Hi @scottmckendry
Is there a way to also support TUI like Neovide?
Using Neovide, the telescope UI looks very messy with the borders.

Compared to neovim:

Originally posted by @idelice in https://github.com/scottmckendry/cyberdream.nvim/issues/42#issuecomment-2119926577

This can be resolved by setting vim.g.neovide_floating_shadow = false somewhere in your config.
@idelice FYI 🙂
https://neovide.dev/configuration.html?highlight=shadow#floating-shadow


Show amount of data per species on homepage

In GitLab by @marcrr on Aug 7, 2018, 14:49
Suggestion: when you unfold a species by clicking on the photo on the Bgee homepage, you get a very short summary of information, e.g.
Canis lupus
6 RNA-seq libraries
3 anatomical structures
Mus musculus
133 RNA-seq libraries
6095 Affymetrix chips
706 EST libraries
37654 in situ hybridization experiments
3254 anatomical structures
This way I see immediately that dog will give me no results in TopAnat and is mostly useless in fact...

In GitLab by @smoretti on Aug 7, 2018, 14:52
In case of for example 3 anatomical structures, we should maybe add something like "3 anatomical structures covered" to specify that there are many more anatomical structures?

In GitLab by @marcrr on Aug 7, 2018, 14:58
I think it's pretty obvious that it's what's covered in the database, no? But we can add that, yes.

In GitLab by @SFonsecaCosta on Aug 8, 2018, 08:50
I think is a good idea, but what about relate just number of experiments with Anatomical structure in the very short summary?
In Bgee we can search for unique gene (Gene search) or pass a list of genes (TopAnat - Gene Expression Enrichment) but at the very beginning nothing emphasizes anatomical structures.
Let's assume I want to do research and I have interest in look brain and RNA-Seq data for adult mice. How I obtain this data in the intuitive way on Bgee without provide any gene? (I have to download all info from all RNA-Seq?, but this is not my aim).
If the data is easily available and intuitive I can look a "particular set of the genes (instead 1 gene)" directly on the files (respective summary statistics for each one), this would be a step to use Bgee in the direction of research tool not just as a validation tool. This is just a idea, I don't know what you think @smoretti @marcrr @vrechdelaval

This info could be displayed as a structure like "heatmap" that display sources against stage (we never have more than 50, right? ) so that can work.
The "user" just click on green button and obtain all experiments for this particular case + all libraries. (The difference here is we are given the opportunity to search on bgee using anatomical structure instead a unique gene).
As we discuss before in the future would be possible the user download all experiments or particular library related with filter created at the very beginning.

In GitLab by @SFonsecaCosta on Aug 8, 2018, 08:56
All this just have in consideration the web page (I don't have in consideration R package that by change allow to create this filters).
I'm just looking the biologist perspective using bgee in more easy and intuitive way.

In GitLab by @marcrr on Aug 8, 2018, 09:20
Thanks @SFonsecaCosta, nice ideas. Some of them would probably be better on a species-specific page than on the homepage?
Just a note: be careful when writing "biologist" to mean "doesn't know to use a computer". That's less and less correct, and many of our users or potential users are at ease in R.

In GitLab by @SFonsecaCosta on Aug 8, 2018, 09:44
Yes, I mean when you click on species to see more details @marcrr
Ok. Thank you for the note. :)
Other point is can we display an anatomical enrichment graphic, where we plot pAcc (perturbation accumulation (pAcc) against over-representation analysis (pORA) or in this case using enrichment methods --> this type of graphic is often used to represent pathways maybe we can adapt for our case in order to summarize the more higher anatomical terms enriched . This graphic provided by bgee can be used a posteriori in papers???? (maybe)
Just to conclude, how about plot cumulative function for specific list of genes (provided by the user) for all libraries after filter, for example, after anatomical structure filter.

In GitLab by @vrechdelaval on Aug 8, 2018, 09:44
Thanks @SFonsecaCosta! I am not in favour of putting to much things in home page. As @marcrr said, we could have species-specific page with more information.

In GitLab by @SFonsecaCosta on Aug 8, 2018, 14:32
Maybe a different issue, but what about remove this redundant info from the web page (mouse)?
if we search a specific gene for a specific specie we already know that we are looking Mus musculus, so when we expand Developmental stage(s) we don't need this information. We already discuss this @smoretti what you think @vrechdelaval .

In GitLab by @marcrr on Aug 8, 2018, 14:44
My opinion:
If it's easy, nice idea.
If it's complicated, super low priority.

In GitLab by @smoretti on Aug 8, 2018, 14:48
It would make the database a bit lighter, as well as the data sent by bgee API to fill the table.
Should be easy but has to be done when stages are inserted in the database.

In GitLab by @vrechdelaval on Sep 3, 2018, 16:20
See https://gitlab.sib.swiss/Bgee/bgee_apps/issues/126

In GitLab by @marcrr on Jun 20, 2019, 08:59
moved to Roadmap suggestions

In GitLab by @marcrr on Jun 20, 2019, 08:59
closed


refactor: Simplify recent_senders code.

This reduces our dependency on message_list code (via
message_util), and it makes moving streams/topics and
deleting messages more performant.
For every single message that was being updated or
deleted, the previous code was basically re-computing
lots of things, including having to iterate through
every message in memory to find the messages matching
your topic.
Now everything basically happens in O(1) time.
The only O(N) computation is that we now eagerly
re-compute the max message id every time you process a
message. The N here is the number of messages that the
particular sender has sent to the particular
stream/topic combination, so it should always be quite
small. We pay a little cost on the write event to make
the reads faster (and reads happen inside of loops in
typeahead code).
The main change that we make here from a data
standpoint is that we just keep track of all
message_ids for all senders. The storage overhead here
should be negligible.  By keeping track of our own
messages, we don't have to punt to other code for
update/delete situations.
There is similar code in recent_topics that I think can
be improved in similar ways, and it would allow us to
eliminate functions like this one:
export function get_messages_in_topic(stream_id, topic) {
    return message_list.all
        .all_messages()
        .filter(
            (x) =>
                x.type === "stream" &&
                x.stream_id === stream_id &&
                x.topic.toLowerCase() === topic.toLowerCase(),
        );
}

I just re-pushed so that the max_id calculation is lazy.  I also tweaked a name in the run_test label for the new test.

If you renamed a topic on master now (or moved it another stream), which had 10k messages from the same bot, or just 10k messages from anybody, that would be a likely performance problem.

This is ready for review again.  I am hoping @amanagr can review.  I am confident enough in my changes that you can merge it before his review, but I think the important follow-up here is to do the same things with recent_topics, and this change doesn't have any true urgency in terms of fending off conflicts or advancing on the kill-off-dependencies mission.

This does make sense to me. Looks great!

This is ready for review again.  I believe I have addressed the problem that @amanagr found in the calling code.

LGTM!

Native operations that are technically O(n) are wicked fast at the 10k scale in JS.

You can insert the following code after IdTracker to simulate roughly a million operations, and it finishes under a second on my couple-years-old laptop (FF).  Our biggest batch size is 1000, I believe.
 43 const idt = new IdTracker();
 44 const t1 = performance.now();
 45 const n = 333333;
 46 for (let i = 1; i <= n; ++i) {
 47     idt.add(i);
 48 }
 49 for (let i = 1; i <= n; ++i) {
 50     idt.remove(i);
 51 }
 52 for (let i = 1; i <= n; ++i) {
 53     idt.add(i);
 54 }
 55 const res = [];
 56 for (let i = n; i > n - 10; --i) {
 57     res.push(idt.max_id());
 58     idt.remove(i);
 59 }
 60
 61 const t2 = performance.now();
 62 const elapsed = t2 - t1;
 63 console.log(elapsed);
 64 console.log(res);

I also tried 100 million operations, which took 65s and didn't blow anything up.  Basically, each add/remove operations is about a microsecond.  And when you calculate max_id() you only pay the O(n) penalty for the one runaway bot, and you only pay it on the first keystroke (so not quadratic).

You can also insert the following code to convince yourself that the cost of max_id() for a topic that has a runaway bot is about a millisecond:
 43 const idt = new IdTracker();
 44 const n = 10000;
 45 for (let i = 1; i <= n; ++i) {
 46     idt.add(i);
 47 }
 48 const res = [];
 49
 50 const t1 = performance.now();
 51 for (let i = n; i > n - 100; --i) {
 52     res.push(idt.max_id());
 53     idt.remove(i); // invalidate cache
 54 }
 55
 56 const t2 = performance.now();
 57 const elapsed = t2 - t1;
 58 console.log(elapsed);
 59 console.log(res);

I think a heap would actually be an inferior data structure here, even if it ran natively and didn't introduce dependencies.  The heap would have log(N) inserts log(N) removals, whereas my implementation does both in O(1).  We mostly do inserts.  It's true that my "peek-at-the-max" operation is O(N), vs. O(1) for a heap, but I can amortize it until the next removal, and removals are rare.  A heap is a nice data structure when you have roughly the same amount of inserts and removes over time, and the speed of the O(1) pop operation justifies the log(N) costs of inserts and removals.  But we never actually pop here; we just peek.  And we generally do more inserts than removals.

(most recent push is just rebasing off of latest master)

This is ready for review.  (The only changes in the last two weeks are rebases.)

Merged, thanks @showell!


Document required CSP values

"Content Security Policy (CSP) is a computer security standard introduced to prevent cross-site scripting (XSS), clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context."
https://en.wikipedia.org/wiki/Content_Security_Policy
A site with a CSP tag — which, ideally, should be every site — should whitelist individual domains that are needed for functionality.
The ones I've found so far for office.js, by manual testing, are:
script-src 'self' https://appsforoffice.microsoft.com:* https://ajax.aspnetcdn.com:* https://browser.pipe.aria.microsoft.com:*

Can we get a canonical list for this?

Hi @richnew10,
Here's the response I received from our product team:
"https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges shows all the IP ranges and domains Microsoft Office uses, use which includes our CDN networks as well.
When I check, Office CDN uses <IP_ADDRESS> and this is not part the IP list, but is part of the o365 list. So, hopefully the customer can take this list and allow traffic to come from IP/domains. This is also not a static list and should be kept in-sync to account for changes. "

Thanks for chasing. I'm not asking about network ACLs; that's not how CSP works.
CSP is a directive that has a webpage tell the browser which origins — e.g., appsforoffice.microsoft.com — should be usable for various kinds of action, e.g., loading script content, or connecting websockets.
The list your product team provided is not sufficient or precise enough for CSP. For example, it lists
ajax.aspnetcdn.com

as "Default Optional; Notes: Office 365 Video CDNs", but office.js loads code from that domain, and omitting it from CSP will cause an error when loading the add-in. On the reverse side,
passwordreset.microsoftonline.com

is listed as required, but that origin will never be accessed from an Outlook add-in or from office.js, and arguably that's exactly the kind of security safeguard that CSP is intended to provide!
What I'm specifically asking for is a list of domains/URLs that the contents of office.js will try to load, and are necessary for office.js to function, and secondarily a mechanism for finding out when that list changes.
You can probably find this out by grepping for https in office.js, and applying a little reasoning.
I have found the following empirically:
https://appsforoffice.microsoft.com:*
https://ajax.aspnetcdn.com:*
https://browser.pipe.aria.microsoft.com:*

Are there more?

Hi @richnew10,, thanks for bringing this up. I don't have anything to share yet, but just wanted to let you know we're looking into how to handle CSP documentation going forward. I'll leave this issue open until we have a resolution.

Internal bug


BSRCH function

pdblp.py
BCon.start(): adding //blp/exrsrc service
BCon.sbrch(): implemented
test_pdblp.py
test_bsrch(): implemented
updated test_bdib(): intraday data older than 6M are not accessible. Using 2017-06-10 instead
test_parser.py
please disregard. All tests were failing for me (evenprior to my changes). So I just added  skip.
flake8 passes without any issue. All tests in test_pdblp.py are passing.
#11

This looks good. Could you please just remove the skip decorator from the parsing tests and squash the history into one commit? (I'm curious why this is failing for you, possibly because you aren't using pyparsing >= 2.2.0)

You are right, upgrading to pyparsing 2.2.0 fixed the remaining tests. I removed the skip from test_parser.
Now all tests are passing.
It is the first time I used squashing, seems that I touched too many of old commits as well ;(
I hope you can merge it now.

Okay cleaned something up and merged. Thanks looks great! This closes issue #11 .

@MarekOzana not sure why you aren't being credited for this on the contributors page. I'm looking into it, but think maybe it has to do with emails https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

So it seems like this is because the @outlook email used in the commits is not associated with your account. The easiest way is to link the email to your account with https://github.com/settings/emails. Not sure if this matters to you but just thought I'd pass the info along in case.

Thanks Matthew. I've update e-mail settings now.
/Marek


QT: EnableHighDpiScaling is breaking ui on Linux

The AA_EnableHighDpiScaling attribute being set on the QApplication on startup is breaking the UI on Linux Rocky 8.7 on a couple different 2560x1440 screens.
I have not found any reason for this yet, it seems to not accurately calculate size hints with this setting on. The addons run through the dcc QApplications run fine.
https://github.com/ynput/ayon-launcher/blob/de19dc09fdc57050f62775e0b477ecccb8fded4d/common/ayon_common/ui_utils.py#L24

Another workaround is setting an environment variable QT_FONT_DPI=96.
I think for now I will use this, until I run into issues with 4k screens. I believe this is only an issue with X and might disappear on Wayland.
More information here:
https://stackoverflow.com/questions/59947058/why-doesnt-qtaa-disablehighdpiscaling-disable-high-dpi-scaling-and-why-does
https://bugreports.qt.io/browse/QTBUG-67928


feat: add metadata to the manifest

Closes #865
This PR adds the mimetype, filename, and createdAt timestamp to the manifest.
As discussed in the Codex client meeting, the mimetype is extracted from the content-type header of the request, and the filename is extracted from the content-disposition header.
I updated the test 'node shows used and available space' test because the space.quotaUsedBytes is now 65602 bytes, i.e., 10 bytes more due to the added metadata (I guess).

Also, I would suggest adding serving these metadata (mainly content type and filename) for the data download using the already used Content-Disposition header, unless I missed it somewhere already?

Yes I thought about it this morning, will try to add it this afternoon.

Okay so @benbierens helped to figure out what was the problem.
The test file concerned but this issue was testecbug.nim.
The test was hanging because the store stream was expecting more data than was available, resulting in the error: 'stream boundary not yet reached!'
The issue arose because I added the Content-Length header to the download endpoint. By removing the header, the error is resolved.
@gmega I think this PR is ready to be merged.


56 feature expose balances of badges for users in api

This has been closed in preference of #130 that takes care of getting the contracts and API up to version 5.0.


Confusing "Type" in GitHub's form schema

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
What part(s) of the article would you like to see updated?
https://github.com/github/docs/blob/954e58c470ffce11cd94b1c1fc2efedb41e73690/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md#L66-L67
Problem
I guess for most people, "hash" is the return value of a hash function.
But here, it seems to mean "dictionary", aka "associative array".
Suggestion
Please consider an appropriate term, like "dictionary".
Additional information
No response

@Lemmingh Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

I hope y'all still ain't trying to get what's mine

they believe that using the hash type communicates the concept better

I'm afraid I don't understand.
Describing an "associative array" as "hash" is definitely wrong.
It violates established terms in computer science
A sane data structure textbook would define the term "hash" as:

(NOUN) A value produced by a hash function.

(VERB) To calculate a hash value.

A textbook would say:

attributes:
  label: 'Proposal'
  description: 'A clear and concise description of your idea.'

The attributes contains an "associative array" (aka "dictionary", "map", etc.), which is a key-value pair collection where each key may appear at most once. An "associative array" is usually implemented as some kind of "hash table" or "binary search tree".

Given that "associative array" is cryptic for those without computer science background, many textbooks choose "dictionary" as the primary term, that is:

"dictionary" (aka "map", "associative array", etc.)

A schema should express abstract data types, not implementation details
The "hash" type probably comes from something in your back-end code.

Abstract data types are logical shapes and operations, independent of implementation.
The YAML spec revision 1.2.2 uses "mapping":

The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique.

Note that "map" is also an alias of "associative array", an abstract concept.

In short, you cannot say a wrong term is better than a correct term.

The actions documentation uses Map:
https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions

Hi! Im participating in Hacktoberfest and I'd like to know if this issue is counted in Hacktoberfest and if I can work on it?

I wouldn't. This appears to be waiting on the internal team.

👋 @Anika-Roy Thanks for your willingness to work on this. As @jsoref mentioned, this one is waiting for a bit more information from our internal team. For now, I'm going to remove the help wanted label so it doesn't show up on our board until we've confirmed it with our team.
We are participating in Hacktoberfest! 🎃 Feel free to head over to the help wanted board and pick up any of our open issues. 💛


Merge Sort

Write a merge sort algorithm.

@Saloni6111  can you please assign me this ticket ?

@Saloni6111 can you please assign me this ticket ?

Yes, it's already assigned to you. Please go ahead!


Shutting down cluster in self-contained EXASOL for taking a snapshot

For our development process, we'd like to create a pre-migrated and ready-to-use Exasol image.
The plan to achieve this is to start a exasol/docker-db:6.0.0-d1sc container, run the migrations against it and then docker commit the result.
Unfortunately, when I naively do this, an error is thrown:
docker run -it --privileged exasol/docker-db:migrated                                                                                [22:41:31]
[2017-04-27 20:41:32] stage0: Run stage 'stage0'
[2017-04-27 20:41:32] stage0: Run service environment_conf
[2017-04-27 20:41:32] stage0: Run service license_check
[2017-04-27 20:41:32] stage0: Run service next_stage
[2017-04-27 20:41:32] stage0: Current environment settings:
[2017-04-27 20:41:32] stage0: >>> [('COS_CONF_DIR', '/exa'),
[2017-04-27 20:41:32] stage0: >>>  ('COS_DIRECTORY', '/usr/opt/EXASuite-6/EXAClusterOS-6.0.0'),
[2017-04-27 20:41:32] stage0: >>>  ('EXA_NODE_ID', '11'),
[2017-04-27 20:41:32] stage0: >>>  ('HOME', '/'),
[2017-04-27 20:41:32] stage0: >>>  ('HOSTNAME', 'n11'),
[2017-04-27 20:41:32] stage0: >>>  ('LANG', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_ADDRESS', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_COLLATE', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_CTYPE', 'en_US.utf8'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_IDENTIFICATION', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_MEASUREMENT', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_MESSAGES', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_MONETARY', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_NAME', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_NUMERIC', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_PAPER', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_TELEPHONE', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('LC_TIME', 'C'),
[2017-04-27 20:41:32] stage0: >>>  ('PATH',
[2017-04-27 20:41:32] stage0: >>>   '/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/bin:/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/sbin:/usr/opt/EXASuite-6/EXARuntime-6.0.0/bin:/usr/opt/EXASuite-6/EXARuntime-6.0.0/sbin:/bin:/sbin:/usr/bin:/usr/sbin'),
[2017-04-27 20:41:32] stage0: >>>  ('PWD', '/'),
[2017-04-27 20:41:32] stage0: >>>  ('RE_PATH', '/usr/opt/EXASuite-6/EXARuntime-6.0.0'),
[2017-04-27 20:41:32] stage0: >>>  ('SHLVL', '1'),
[2017-04-27 20:41:32] stage0: >>>  ('TERM', 'xterm')]
[2017-04-27 20:41:32] stage0: You have following license limits:
[2017-04-27 20:41:32] stage0: >>>     Database memory (GiB):        200 Main memory (RAM) usable by databases
[2017-04-27 20:41:32] stage0: >>>             Cluster nodes:          1 Number of usable cluster nodes
[2017-04-27 20:41:32] stage0: >>>   Database raw size (GiB):  unlimited Raw Size of Databases (see Value RAW_OBJECT_SIZE in System Tables)
[2017-04-27 20:41:32] stage0: >>>   Database mem size (GiB):  unlimited Compressed Size of Databases (see Value MEM_OBJECT_SIZE in System Tables)
[2017-04-27 20:41:32] stage0: >>>           Expiration date:  unlimited Date of license expiration
[2017-04-27 20:41:32] stage0: Next stage will be 'stage1'.
[2017-04-27 20:41:33] stage1: Run stage 'stage1'
[2017-04-27 20:41:33] stage1: Run service node_options
[2017-04-27 20:41:33] stage1: Run service node_etc_cos
[2017-04-27 20:41:33] stage1: Run service name_resolution
[2017-04-27 20:41:33] stage1: Run service sysctl
[2017-04-27 20:41:33] stage1: Run service diskconf
[2017-04-27 20:41:33] stage1: Run service broadcast_peers
[2017-04-27 20:41:33] stage1: Run service root_bashrc
[2017-04-27 20:41:33] stage1: Run service cored_command
[2017-04-27 20:41:33] stage1: Run service next_stage
[2017-04-27 20:41:33] stage1: Current node id is '11'
[2017-04-27 20:41:33] stage1: Current node options are:
[2017-04-27 20:41:33] stage1: >>> [('disks',
[2017-04-27 20:41:33] stage1: >>>   <config at 0x7fa355ea64f0: [('default', <config at 0x7fa355ea6618: [('name', 'default'), ('devices', [('dev.1.data', 'dev.1.meta')])]>)]>),
[2017-04-27 20:41:33] stage1: >>>  ('docker_volume', '/home/ec2-user/cl4/n11'),
[2017-04-27 20:41:33] stage1: >>>  ('exposed_ports', [(8888, 8899), (6583, 6594)]),
[2017-04-27 20:41:33] stage1: >>>  ('hostname', 'n11'),
[2017-04-27 20:41:33] stage1: >>>  ('id', '11'),
[2017-04-27 20:41:33] stage1: >>>  ('private_ip', '<IP_ADDRESS>'),
[2017-04-27 20:41:33] stage1: >>>  ('private_net', '<IP_ADDRESS>/16'),
[2017-04-27 20:41:33] stage1: >>>  ('public_ip', ''),
[2017-04-27 20:41:33] stage1: >>>  ('public_net', '')]
[2017-04-27 20:41:33] stage1: Current node UUID is 'FCCB197144B0CB8C2703E5A4AEB06FBED87D83A3' (copied)
[2017-04-27 20:41:33] stage1: /etc/hosts content:
[2017-04-27 20:41:33] stage1: >>> # hosts is generated by exainit
[2017-04-27 20:41:33] stage1: >>> <IP_ADDRESS> localhost localhost.localdomain
[2017-04-27 20:41:33] stage1: >>> <IP_ADDRESS> n11
[2017-04-27 20:41:33] stage1: /etc/resolv.conf content:
[2017-04-27 20:41:33] stage1: >>> # resolv.conf is disabled by exainit
[2017-04-27 20:41:33] stage1: Following sysctl parameters have incorrect values:
[2017-04-27 20:41:33] stage1:                    net.core.rmem_default: '4194304' != None
[2017-04-27 20:41:33] stage1:                    net.core.wmem_default: '524288' != None
[2017-04-27 20:41:33] stage1:                        net.ipv4.tcp_rmem: '4096        87380   1048576' != None
[2017-04-27 20:41:33] stage1:                        net.core.rmem_max: '4194304' != None
[2017-04-27 20:41:33] stage1:                       kernel.threads-max: '274432' != '127664'
[2017-04-27 20:41:33] stage1:                        net.ipv4.tcp_wmem: '4096        16384   4194304' != None
[2017-04-27 20:41:33] stage1:                        net.core.wmem_max: '1048576' != None
[2017-04-27 20:41:33] stage1:              net.core.netdev_max_backlog: '1000' != None
[2017-04-27 20:41:33] stage1: Following nodes are registered: <IP_ADDRESS>:10001
[2017-04-27 20:41:33] stage1: Call cored with following command: '/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/cos_cored -n 11 --renice -10 --auth-sock-dir /var/lock --oom-adjustment -5 -m <IP_ADDRESS> -s <IP_ADDRESS> -t 10001 -l /exa/logs/cored /usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/exainit.py stage2'
[2017-04-27 20:41:33] stage1: Next stage will be 'stage2'.
[2017-04-27 20:41:33] Starting with PID 1
[2017-04-27 20:41:33] Core Daemon v6.0.0  (build 14100)
[2017-04-27 20:41:33] Using multicast address <IP_ADDRESS>.
[2017-04-27 20:41:33] Receive socket is bind to interface eth0.
Log_E: [2017-04-27 20:41:33] <140037177502144> unix_auth.cc:48 prepare_authentication(): connect() to /var/run/ecos_unix_auth failed, super_cored running?! : (111) Connection refused
Log_E: [2017-04-27 20:41:33] <140037177502144> unix_auth.cc:77 do_unix_service_authentication(): prepare_authentication() failed
[2017-04-27 20:41:33] Could not authenticate to master authentication process.
Log_E: [2017-04-27 20:41:33] <140037177502144> cos_cored.cc:570 do_rest(): Caught COS::exception: e_failed - ERROR 00000: action failed

backtracedecode <<EOBT
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/lib/libCOS.so(_ZN3COS9exceptionC1ERKS0_+0x75) [0x7f5cf0a4b185]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/lib/libCOS.so(_ZN3COS9unix_authC1ENS_4srefINS_14auth_containerENS_12serializableEEENS1_INS_20service_registrationENS_9algorithmEEESsSss+0x2e8) [0x7f5cf0a3ee78]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/lib/libCosCore.so(_ZN3COS4core20core_membership_algoC1ENS_4srefINS0_11core_configENS_12serializableEEENS2_INS_9intercomm19membership_protocolENS_9algorithmEEERKSt6vectorISsSaISsEEjsiSst+0xada) [0x7f5cf05ff05a]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/cos_cored() [0x40efdf]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/cos_cored() [0x4107e5]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/cos_cored() [0x40bbd9]
/usr/opt/EXASuite-6/EXARuntime-6.0.0/lib/libc.so.6(__libc_start_main+0xf0) [0x7f5cef9ad320]
/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/cos_cored() [0x40c6fa]
EOBT

I'm guessing that the cluster has to be shutdown properly before docker commiting, so it has a chance to properly reinitialize the next time.
Could that be the case? If so, how do I properly shut down the cluster in the d1sc container?
Would I also need to delete some files that might prevent the next startup? I saw e.g. that the IP address (which might be different on the next start) seems to be persisted somewhere.
Thanks a lot for your continued support!

Any ideas on this one?

I have commited a small fix, it should work now.

Perfect! I just tried it and can confirm that this allows properly restarting the Docker container.
Thanks a lot @ooke!


docs(light variant): code snippet, overflow menu, tile

Need to add docs similar to input pages about the correct usage of the --light variants for these components:

[x] code snippet: https://github.com/carbon-design-system/carbon/pull/4342
[ ] overflow menu: https://github.com/carbon-design-system/carbon/pull/4347
[ ] tile: https://github.com/carbon-design-system/carbon/pull/4335

Note: Include a don't on not using same color background with same color containers

[ ] Also double check kit has this function as well

Code snippet usage docs now has the light variant in the modifiers section.
https://www.carbondesignsystem.com/components/code-snippet/usage#modifiers


How can I get battery charging status?

Hi I am using AgileX tracer robot and I want to get battery status and charging info of the robot?
Would it be possible? How should I achieve that status info?
Thank you in advance!

I'm having the same problem.
scout_mini_omni_demo.cpp sample code can run normally, so I added the following code:
auto SensorState = scout->GetCommonSensorState();
std::cout << "Battery information (power, health, voltage, current, temperature): "
<< SensorState.bms_basic_state.battery_soc1<< ", "
<< SensorState.bms_basic_state.battery_soh<< ", "
<< SensorState.bms_basic_state.voltage<< ", "
<< SensorState.bms_basic_state.current<< ", "
<< SensorState.bms_basic_state.temperature
<< std::endl;
The output shows:
Battery information (power, health, voltage, current, temperature): , , 0, 0, 0
What's going on here?


Perhaps some updates needed?

You wrote on the page:
"As the additional coexistence modes, (i.e. Skype for Business with Teams collaboration and Skype for Business with Teams collaboration and meetings), are become progressively fully available in the next few months,"
This seems to be available already. So perhaps that need some updates...?

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

ID: 006dc464-2228-0d91-8726-223770c91411
Version Independent ID: 28877a22-b558-4da6-551b-9bcd9bac96c4
Content: Microsoft Teams upgrade from Skype for Business
Content Source: Teams/upgrade-and-coexistence-of-skypeforbusiness-and-teams.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Petri-X Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Petri-X The author is doing a full rewrite of this article. Thanks for your feedback.


Remote jupyter server failures are not diagnosable

Was helping somebody today and their default kernel spec was invalid. There's no way to tell from the Jupyter extension.
We need at least the console output from the jupyter server. I had tried adding this to jupyter a long time ago and they were hesitant.
Maybe we could tell the user to look at the console output instead.

Closing this issue as there's nothing to be done here,


ref: main exp workflow (run,show,diff,apply)

Splits and improves #1926

exp run/show/diff/apply Descs and Options
related updates to the guides and other refs (index and API)

I left out the examples in this PR b/c it's getting too big.

LGTM @shcheklein @dberenbaum @pmrowla ? Examples will be coming in a separate PR (this is big enough). The remaining commands also have their own PR (#2243).

OK guys I'm going to merge this. There will be more iterations in case anyone has more comments. Thanks!


(maint) Use Ruby 2 style caller()

In Ruby 2, and JRuby 9k, Kernel#caller got a new optional argument that
controls how many frames to go back when constructing the call stack.
In most cases where we call caller we also throw away most of the
call stack. This has performance implications for every Ruby environment
and especially for JRuby.
Most of the time this doesn't matter because we are getting the call
stack for error reporting, however in at least one case this
information is used for non-fatal warnings.

My last PRs reminded me that I had this branch laying around.
I broke out the PuppetStack part because that needed more work/might be controversial, if I can finish it up in a couple hours I'll open something for that too.

This is the PuppetStack work I was alluding to https://github.com/puppetlabs/puppet/pull/7754. Did not push it to this PR since its considerably more risky and needs more vetting.

Yeah I had added the same to my rubocop PR, but had to remove it since I was targeting 5.5.x.
Can you retarget this for 6.4.x?

I made a new pr here (gave it the correct branch name).


chore: github action to build the operator every week

This adds a github action to build and push the operator
image to quay every Monday.
Signed-off-by: N Balachandran<EMAIL_ADDRESS>

/hold


support go1.23 for tidb master branch

/hold
wait for PR https://github.com/pingcap/tiflow/pull/11607.

/unhold


test #427 with gz-cmake#436

test #427 with gz-cmake#436
add a .github/ci/dependencies.yaml to build
gz-* dependencies from source

the workflow passed, but it seemed to fail uploading to codecov


Should dataset contributions to Olympus be limited to experimental results (e.g. wetlab experiments)?

Totally fine if so

Reading the manuscript in more depth, it seems like the answer is yes (i.e. focus on datasets produced via autonomous experimentation).


Restrict reported overlaps to enforced policies

Previously, informed OperatorPolicies could report that they were overlapping, but in those cases it is not necessary to prevent the policies from operating normally. Now, only overlapping enforced policies will be considered invalid.
Refs:

https://issues.redhat.com/browse/ACM-12207

  KinD tests (latest) Attempt 1
  [FAIL] Testing OperatorPolicy Test CRD deletion delayed because of a finalizer [It] Initially behaves correctly as musthave [supports-hosted]
  /home/runner/work/config-policy-controller/config-policy-controller/test/e2e/case38_install_operator_test.go:2673

• [FAILED] [18.070 seconds]
Testing OperatorPolicy Test CRD deletion delayed because of a finalizer [It] Initially behaves correctly as musthave [supports-hosted]
/home/runner/work/config-policy-controller/config-policy-controller/test/e2e/case38_install_operator_test.go:2657

  Timeline >>
  STEP: Creating the parent object @ 06/18/24 17:40:28.261
  STEP: Creating the child object with the owner reference @ 06/18/24 17:40:28.385
  STEP: Verifying the child object exists @ 06/18/24 17:40:28.39
  STEP: Waiting for a CRD to appear, which should indicate the operator is installing @ 06/18/24 17:40:28.458
  [FAILED] in [It] - /home/runner/work/config-policy-controller/config-policy-controller/test/e2e/case38_install_operator_test.go:2673 @ 06/18/24 17:40:34.525
  [FAILED] in [AfterAll] - /home/runner/work/config-policy-controller/config-policy-controller/test/e2e/e2e_suite_test.go:198 @ 06/18/24 17:40:34.59
  Debug info for failure.
  policy JSON: {
    "apiVersion": "policy.open-cluster-management.io/v1beta1",
    "kind": "OperatorPolicy",
    "metadata": {
      "annotations": {
        "policy.open-cluster-management.io/parent-policy-compliance-db-id": "124",
        "policy.open-cluster-management.io/policy-compliance-db-id": "64"
      },
      "creationTimestamp": "2024-06-18T17:40:28Z",
      "generation": 2,
      "labels": {
        "policy.open-cluster-management.io/cluster-name": "managed",
        "policy.open-cluster-management.io/cluster-namespace": "managed"
      },
      "name": "oppol-mustnothave",
      "namespace": "managed",
      "ownerReferences": [
        {
          "apiVersion": "policy.open-cluster-management.io/v1",
          "kind": "Policy",
          "name": "parent-policy",
          "uid": "a9ab7e5c-74f6-4267-aafa-7901a0709af2"
        }
      ],
      "resourceVersion": "8885",
      "uid": "d4baf786-3a4e-4a8e-8b92-9bb8da163215"
    },
    "spec": {
      "complianceConfig": {
        "catalogSourceUnhealthy": "Compliant",
        "deploymentsUnavailable": "NonCompliant",
        "upgradesAvailable": "Compliant"
      },
      "complianceType": "musthave",
      "remediationAction": "enforce",
      "removalBehavior": {
        "clusterServiceVersions": "Delete",
        "customResourceDefinitions": "Delete",
        "operatorGroups": "DeleteIfUnused",
        "subscriptions": "Delete"
      },
      "severity": "medium",
      "subscription": {
        "channel": "stable-3.10",
        "name": "project-quay",
        "namespace": "operator-policy-testns",
        "source": "operatorhubio-catalog",
        "sourceNamespace": "olm"
      },
      "upgradeApproval": "Automatic"
    },
    "status": {
      "compliant": "Compliant",
      "conditions": [
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "CatalogSource was found",
          "reason": "CatalogSourcesFound",
          "status": "False",
          "type": "CatalogSourcesUnhealthy"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:32Z",
          "message": "ClusterServiceVersion (quay-operator.v3.10.6) - install strategy completed with no errors",
          "reason": "InstallSucceeded",
          "status": "True",
          "type": "ClusterServiceVersionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:33Z",
          "message": "Compliant; the policy spec is valid, the OperatorGroup matches what is required by the policy, the Subscription matches what is required by the policy, no InstallPlans requiring approval were found, ClusterServiceVersion (quay-operator.v3.10.6) - install strategy completed with no errors, no CRDs were found for the operator, all operator Deployments have their minimum availability, CatalogSource was found",
          "reason": "Compliant",
          "status": "True",
          "type": "Compliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:33Z",
          "message": "no CRDs were found for the operator",
          "reason": "RelevantCRDNotFound",
          "status": "True",
          "type": "CustomResourceDefinitionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:32Z",
          "message": "all operator Deployments have their minimum availability",
          "reason": "DeploymentsAvailable",
          "status": "True",
          "type": "DeploymentCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:33Z",
          "message": "no InstallPlans requiring approval were found",
          "reason": "NoInstallPlansRequiringApproval",
          "status": "True",
          "type": "InstallPlanCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the OperatorGroup matches what is required by the policy",
          "reason": "OperatorGroupMatches",
          "status": "True",
          "type": "OperatorGroupCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the Subscription matches what is required by the policy",
          "reason": "SubscriptionMatches",
          "status": "True",
          "type": "SubscriptionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the policy spec is valid",
          "reason": "PolicyValidated",
          "status": "True",
          "type": "ValidPolicySpec"
        }
      ],
      "relatedObjects": [
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "CatalogSource",
            "metadata": {
              "name": "operatorhubio-catalog",
              "namespace": "olm"
            }
          },
          "reason": "Resource found as expected"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "ClusterServiceVersion",
            "metadata": {
              "name": "quay-operator.v3.10.6",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "06e9a002-3319-4048-863a-343cfc9fb749"
          },
          "reason": "InstallSucceeded"
        },
        {
          "compliant": "UnknownCompliancy",
          "object": {
            "apiVersion": "apiextensions.k8s.io/v1",
            "kind": "CustomResourceDefinition",
            "metadata": {
              "name": "-"
            }
          },
          "reason": "No relevant CustomResourceDefinitions found"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "apps/v1",
            "kind": "Deployment",
            "metadata": {
              "name": "quay-operator-tng",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "343f6ceb-fe82-411f-8338-f4ecdae88dfb"
          },
          "reason": "Deployment Available"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "InstallPlan",
            "metadata": {
              "name": "install-9rdpk",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "5c983ad4-7432-4609-80be-44f5e8ceec86"
          },
          "reason": "The InstallPlan is Complete"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1",
            "kind": "OperatorGroup",
            "metadata": {
              "name": "operator-policy-testns-vcd8w",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "createdByPolicy": true,
            "uid": "0707f5eb-3d45-4317-98ef-19937c986d42"
          },
          "reason": "Resource found as expected"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "Subscription",
            "metadata": {
              "name": "project-quay",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "createdByPolicy": true,
            "uid": "0af4d88e-62ca-4907-b34d-9c613988602b"
          },
          "reason": "Resource found as expected"
        }
      ],
      "resolvedSubscriptionLabel": "project-quay.operator-policy-testns"
    }
  }
  wanted related objects: [{Properties:<nil> Object:{Metadata:{Name:quayregistries.quay.redhat.com Namespace:} Kind:CustomResourceDefinition APIVersion:apiextensions.k8s.io/v1} Compliant:Compliant Reason:Resource found as expected}]
  wanted condition: {Type:CustomResourceDefinitionCompliant Status:True ObservedGeneration:0 LastTransitionTime:0001-01-01 00:00:00 +0000 UTC Reason:RelevantCRDFound Message:there are CRDs present for the operator}

  Debug info for failure.
  policy JSON: {
    "apiVersion": "policy.open-cluster-management.io/v1beta1",
    "kind": "OperatorPolicy",
    "metadata": {
      "annotations": {
        "policy.open-cluster-management.io/parent-policy-compliance-db-id": "124",
        "policy.open-cluster-management.io/policy-compliance-db-id": "64"
      },
      "creationTimestamp": "2024-06-18T17:40:28Z",
      "generation": 2,
      "labels": {
        "policy.open-cluster-management.io/cluster-name": "managed",
        "policy.open-cluster-management.io/cluster-namespace": "managed"
      },
      "name": "oppol-mustnothave",
      "namespace": "managed",
      "ownerReferences": [
        {
          "apiVersion": "policy.open-cluster-management.io/v1",
          "kind": "Policy",
          "name": "parent-policy",
          "uid": "a9ab7e5c-74f6-4267-aafa-7901a0709af2"
        }
      ],
      "resourceVersion": "8873",
      "uid": "d4baf786-3a4e-4a8e-8b92-9bb8da163215"
    },
    "spec": {
      "complianceConfig": {
        "catalogSourceUnhealthy": "Compliant",
        "deploymentsUnavailable": "NonCompliant",
        "upgradesAvailable": "Compliant"
      },
      "complianceType": "musthave",
      "remediationAction": "enforce",
      "removalBehavior": {
        "clusterServiceVersions": "Delete",
        "customResourceDefinitions": "Delete",
        "operatorGroups": "DeleteIfUnused",
        "subscriptions": "Delete"
      },
      "severity": "medium",
      "subscription": {
        "channel": "stable-3.10",
        "name": "project-quay",
        "namespace": "operator-policy-testns",
        "source": "operatorhubio-catalog",
        "sourceNamespace": "olm"
      },
      "upgradeApproval": "Automatic"
    },
    "status": {
      "compliant": "Compliant",
      "conditions": [
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "CatalogSource was found",
          "reason": "CatalogSourcesFound",
          "status": "False",
          "type": "CatalogSourcesUnhealthy"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:32Z",
          "message": "ClusterServiceVersion (quay-operator.v3.10.6) - install strategy completed with no errors",
          "reason": "InstallSucceeded",
          "status": "True",
          "type": "ClusterServiceVersionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:33Z",
          "message": "Compliant; the policy spec is valid, the OperatorGroup matches what is required by the policy, the Subscription matches what is required by the policy, no InstallPlans requiring approval were found, ClusterServiceVersion (quay-operator.v3.10.6) - install strategy completed with no errors, there are CRDs present for the operator, all operator Deployments have their minimum availability, CatalogSource was found",
          "reason": "Compliant",
          "status": "True",
          "type": "Compliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:32Z",
          "message": "there are CRDs present for the operator",
          "reason": "RelevantCRDFound",
          "status": "True",
          "type": "CustomResourceDefinitionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:32Z",
          "message": "all operator Deployments have their minimum availability",
          "reason": "DeploymentsAvailable",
          "status": "True",
          "type": "DeploymentCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:33Z",
          "message": "no InstallPlans requiring approval were found",
          "reason": "NoInstallPlansRequiringApproval",
          "status": "True",
          "type": "InstallPlanCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the OperatorGroup matches what is required by the policy",
          "reason": "OperatorGroupMatches",
          "status": "True",
          "type": "OperatorGroupCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the Subscription matches what is required by the policy",
          "reason": "SubscriptionMatches",
          "status": "True",
          "type": "SubscriptionCompliant"
        },
        {
          "lastTransitionTime": "2024-06-18T17:40:28Z",
          "message": "the policy spec is valid",
          "reason": "PolicyValidated",
          "status": "True",
          "type": "ValidPolicySpec"
        }
      ],
      "relatedObjects": [
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "CatalogSource",
            "metadata": {
              "name": "operatorhubio-catalog",
              "namespace": "olm"
            }
          },
          "reason": "Resource found as expected"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "ClusterServiceVersion",
            "metadata": {
              "name": "quay-operator.v3.10.6",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "06e9a002-3319-4048-863a-343cfc9fb749"
          },
          "reason": "InstallSucceeded"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "apiextensions.k8s.io/v1",
            "kind": "CustomResourceDefinition",
            "metadata": {
              "name": "quayregistries.quay.redhat.com"
            }
          },
          "properties": {
            "uid": "44176670-9905-43b7-8dca-cb6af293a5c9"
          },
          "reason": "Resource found as expected"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "apps/v1",
            "kind": "Deployment",
            "metadata": {
              "name": "quay-operator-tng",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "343f6ceb-fe82-411f-[8338](https://github.com/open-cluster-management-io/config-policy-controller/actions/runs/9569421187/job/26381922868?pr=269#step:10:8339)-f4ecdae88dfb"
          },
          "reason": "Deployment Available"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "InstallPlan",
            "metadata": {
              "name": "install-9rdpk",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "uid": "5c983ad4-7432-4609-80be-44f5e8ceec86"
          },
          "reason": "The InstallPlan is Complete"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1",
            "kind": "OperatorGroup",
            "metadata": {
              "name": "operator-policy-testns-vcd8w",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "createdByPolicy": true,
            "uid": "0707f5eb-3d45-4317-98ef-19937c986d42"
          },
          "reason": "Resource found as expected"
        },
        {
          "compliant": "Compliant",
          "object": {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "Subscription",
            "metadata": {
              "name": "project-quay",
              "namespace": "operator-policy-testns"
            }
          },
          "properties": {
            "createdByPolicy": true,
            "uid": "0af4d88e-62ca-4907-b34d-9c613988602b"
          },
          "reason": "Resource found as expected"
        }
      ],
      "resolvedSubscriptionLabel": "project-quay.operator-policy-testns"
    }
  }
  << Timeline

  [FAILED] Failed after 1.028s.
  The function passed to Consistently failed at /home/runner/work/config-policy-controller/config-policy-controller/test/e2e/case38_install_operator_test.go:141 with:
  Expected
      <bool>: false
  to be true
  In [It] at: /home/runner/work/config-policy-controller/config-policy-controller/test/e2e/case38_install_operator_test.go:2673 @ 06/18/24 17:40:34.525```

</details>


#149 Add Cake.Graph to Cake.Recipe to add task graphs to documentation

Adds web files (js, css, cshtml files) and two tasks for Cake.Graph with dependencies wired up to documentation tasks so that the json files which describe the tasks are recreated when documentation is produced.

Fixes #149

@wozzo your changes have been merged, thanks for your contribution 👍


[PE-D][Tester C] Tasks disappear when tank view command is used

Screenshot when tank view command is used correctly :

I understand that the user can make tasks reappear with list tasks but it looks like an unintentional side-effect as this is not shown/listed in the UG that the tasks would disappear upon entering this command. This might create confusion for the user. Even the "feed fish" task as shown below disappears but it is not assigned to a specific tank.
Maybe a labelled diagram or more specific mention in the UG would be useful?

UG Screenshot where there is no specific mention of this happening:

Labels: severity.Medium type.FeatureFlaw
original: cjyothika/ped#4

https://github.com/bokuanT/tp/blob/branch-UserGuide/docs/UserGuide.md#viewing-a-tank-tank-view


(intermediate value).slice is not a function

I am getting this error at runtime whne using angular-cli with a target of es5
the code in question in typescript is
this.allowedFields = [ ...new Set(this.allowedFields) ].sort((a,b) => { return a.toLowerCase() > b.toLowerCase() ? 1 : -1});
Am I doing something wrong  - or is it a bug ?

@jmls can you provide a minimal (and pure JavaScript) test case, showcasing the error? The information you provided doesn't say much.
I'm going to close it, as I don't think there's any issue in this project.

having the same issue.

@emreavsar can you post a full stack trace of an error

This code:
// does not work with es6-set in es5, but works with es6 native set
let configurationIds: number[] = [... new Set(necessaryPreventionTopicConfigurations.map(config => config.id))];

Leads to this error:
ERROR Error: Uncaught (in promise): TypeError: (intermediate value).slice is not a function
TypeError: (intermediate value).slice is not a function
    at PatientDataComponent.prepareObservations (patient-data.component.ts:128)
    at SafeSubscriber.eval [as _next] (patient-data.component.ts:61)
    at SafeSubscriber.__tryOrUnsub (Subscriber.js:239)
    at SafeSubscriber.next (Subscriber.js:186)
    at Subscriber._next (Subscriber.js:127)
    at Subscriber.next (Subscriber.js:91)
    at DistinctUntilChangedSubscriber._next (distinctUntilChanged.js:104)
    at DistinctUntilChangedSubscriber.Subscriber.next (Subscriber.js:91)
    at MapSubscriber._next (map.js:85)
    at MapSubscriber.Subscriber.next (Subscriber.js:91)
    at PatientDataComponent.prepareObservations (patient-data.component.ts:128)
    at SafeSubscriber.eval [as _next] (patient-data.component.ts:61)
    at SafeSubscriber.__tryOrUnsub (Subscriber.js:239)
    at SafeSubscriber.next (Subscriber.js:186)
    at Subscriber._next (Subscriber.js:127)
    at Subscriber.next (Subscriber.js:91)
    at DistinctUntilChangedSubscriber._next (distinctUntilChanged.js:104)
    at DistinctUntilChangedSubscriber.Subscriber.next (Subscriber.js:91)
    at MapSubscriber._next (map.js:85)
    at MapSubscriber.Subscriber.next (Subscriber.js:91)
    at resolvePromise (zone.js:824)
    at eval (zone.js:876)
    at ZoneDelegate.invokeTask (zone.js:425)
    at Object.onInvokeTask (core.js:4747)
    at ZoneDelegate.invokeTask (zone.js:424)
    at Zone.runTask (zone.js:192)
    at drainMicroTaskQueue (zone.js:602)
    at <anonymous>

With _ (http://underscorejs.org/), without using the Set, I can achieve the same with:
let configurationIds: number[] = _.uniq(necessaryPreventionTopicConfigurations, function (config) {
        return config.id;
    })
    .map(config => config.id);

@emreavsar it looks as issue in  transpiler that transforms the code into valid ECMAScript and not in es6-set. What exactly transpiler you're using?
Can you prepare a smallest possible setup that reproduces the issue (so single one-line ts file, with configured build and run commands)?

You can easily confirm that without any transpilation above construct will work without issues.
e.g. in Node v8:
const Set = require('es6-set/polyfill');
[...new Set(['foo', 'bar', 3])]; // resolves with [ 'foo', 'bar', 3


limit_push_down is not working properly with OFFSET

Describe the bug
limit_push_down tries to push a limit to TableScan when OFFSET is without LIMIT, which makes all the result disappeared.
OFFSET without LIMIT is allowed in Postgres.
To Reproduce
in limit_push_down.rs, add this test code:
`#[test]
fn limit_pushdown_should_not_pushdown_limit_with_offset_only() -> Result<()> {
    let table_scan = test_table_scan()?;
    let plan = LogicalPlanBuilder::from(table_scan)
        .offset(10)?
        .build()?;

    // Should not push any limit down to table provider
    // When it has a select
    let expected = "Offset: 10\
    \n  TableScan: test projection=None";

    assert_optimized_plan_eq(&plan, expected);

    Ok(())
}

`
The problem is here in the code, which adds a limit when OFFSET doesnt have one:

Expected behavior
The test case should pass. When OFFSET is without LIMIT, then no limit should pushed down to TableScan.
Additional context
I was trying to implement the OFFSET physical plan.

Any idea on how to handle this? I was thinking adding another boolean attribute has_limit inside LogicalPlan::OffsetPlan, and handle the case when there is no limit in limit_push_down.

How about add another LogicalPlan LimitWithOffset. So that the three LogicalPlan used in different cases:

Limit: without offset
Offset: without limit
LimitWithOffset: offset + limit

Then in the limit_push_down, we need to handle two cases: Limit and LimitWithOffset.
For Limit, the push down logic is roughly the same as before; for LimitWithOffset, we adjust the limit pushed down.

What about consolidating Limit and Offset into LimitWithOffset (both logical and physical plans), with optional limit or offset:
  limit: Option<usize>,
  offset: Option<usize>

Then when a limit / offset is pushed down, it can be transformed from Limit(limit, offset) to Limit(limit+offset, 0) ?


unable to compile on Android using the guide.

Get the Following error when running the command on termux on Android 14.

javac -cp ".:$ANDROID_HOME/platforms/android-11/android.jar" ImeiManager.java Main.java
error: file not found: ImeiManager.java Usage: javac <options> <source files> use --help for a list of possible options
Kindly advice.

Were you able to change the IMEI on android 14?

I have this same problem, Android 13

Get the Following error when running the command on termux on Android 14.
javac -cp ".:$ANDROID_HOME/platforms/android-11/android.jar" ImeiManager.java Main.java
error: file not found: ImeiManager.java Usage: javac <options> <source files> use --help for a list of possible options
Kindly advice.

Use ANDRAX/NETHUNTER with CUSTOM kernel and firmware

The file you are trying to execute is not compatible with your operating system architecture. Your phone has a stock kernel, but requires a custom kernel to run. Find a flashed kernel with firmware for your device, install ANDRAX/NetHunter or work as root on Termux and everything will work


The chart can crash sometimes when viewing chart value trackball

Unfortunately the call stack does not have a level where I could catch it. Maybe it's the interference of the listview up-down scroll vs the chart's up-down pan? It comes when long pressing for a chart trackball and then immediately swipe up-down over the chart.
Opened Syncfusion issue: https://github.com/syncfusion/flutter-widgets/issues/463
======== Exception caught by gesture ===============================================================
The following _CastError was thrown while handling a gesture:
Null check operator used on a null value

When the exception was thrown, this was the stack:
#0      getNearestChartPoints (package:syncfusion_flutter_charts/src/chart/common/common.dart:1644:59)
#1      TrackballRenderingDetails.generateAllPoints (package:syncfusion_flutter_charts/src/chart/user_interaction/trackball.dart:897:13)
#2      TrackballBehavior.show (package:syncfusion_flutter_charts/src/chart/user_interaction/trackball.dart:436:36)
#3      TrackballBehaviorRenderer.onTouchMove (package:syncfusion_flutter_charts/src/chart/user_interaction/trackball.dart:572:52)
#4      ContainerArea._performLongPressMoveUpdate (package:syncfusion_flutter_charts/src/chart/base/chart_base.dart:3206:18)
#5      ContainerArea.build.<anonymous closure>.<anonymous closure> (package:syncfusion_flutter_charts/src/chart/base/chart_base.dart:2307:25)
#6      LongPressGestureRecognizer._checkLongPressMoveUpdate.<anonymous closure> (package:flutter/src/gestures/long_press.dart:756:85)
#7      GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:193:24)
#8      LongPressGestureRecognizer._checkLongPressMoveUpdate (package:flutter/src/gestures/long_press.dart:756:11)
#9      LongPressGestureRecognizer.handlePrimaryPointer (package:flutter/src/gestures/long_press.dart:652:9)
#10     PrimaryPointerGestureRecognizer.handleEvent (package:flutter/src/gestures/recognizer.dart:558:9)
#11     PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:94:12)
#12     PointerRouter._dispatchEventToRoutes.<anonymous closure> (package:flutter/src/gestures/pointer_router.dart:139:9)
#13     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:400:8)
#14     PointerRouter._dispatchEventToRoutes (package:flutter/src/gestures/pointer_router.dart:137:18)
#15     PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:123:7)
#16     GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:440:19)
#17     GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:420:22)
#18     RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:278:11)
#19     GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:374:7)
#20     GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:338:5)
#21     GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:296:7)
#22     GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:279:7)
#26     _invoke1 (dart:ui/hooks.dart:185:10)
#27     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:293:7)
#28     _dispatchPointerDataPacket (dart:ui/hooks.dart:98:31)
(elided 3 frames from dart:async)
Handler: "onLongPressMoveUpdate"
Recognizer: LongPressGestureRecognizer#26cf0
  debugOwner: GestureDetector
  state: possible

Supposedly 19.4.55 would fix this but I still see the seriesRendererDetails.visibleDataPoints!.isNotEmpty == true clause in the show function of the trackball.dart.

20.1.56 still has this crash. When will ti be fixed?

With the latest code I don't experience the crash any more.


Bug (?): escaping newline in prompts?

With promptfoo==0.56.0 and the below promptfooconfig.yaml:
prompts: blah\n\nblah

Running promptfoo eval --verbose with OpenAI, I see this:
Calling OpenAI API: {...,"messages":[{"role":"user","content":"blah\\n\\nblah"}],...}

I am sort of just checking, but when sending content to OpenAI, we should be escaping the newline like \\n? I would think we don't want to escape the newlines:
>>> print("blah\\n\\nblah")
blah\n\nblah
>>> print("blah\n\nblah")
blah

blah

This is actually just YAML working as intended (you can try it on any yaml->json converter).  If you wrap it in quotes, it will use the actual newline character:
prompts: "blah\n\nblah"

TIL of this behavior, thanks for sharing! This Stack Overflow question helped me understand it too.
Trying out the quoted route as suggested, I confirmed the \n isn't escaped:
prompts: "blah\n\nblah"

Calling OpenAI API: {...,"messages":[{"role":"user","content":"blah\n\nblah"}],...}

As this isn't actually a bug after all, going to close this out. Thanks again 👍

An aside, is this is also equivalent to:
prompts: >-
  blah

  blah


[FEATURE] Tower blocks game

Description
We need to form the tower with the help of blocks.Block should be placed upon block with same size else size of block goes on reducing.
Game points:Score will be displayed as how long our tower is.
Screenshots
No response
Additional information
No response

wave @SimranLahrani842
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.

Assign me @panwar8279

Hi @SimranLahrani842 , I am assigning this task to you. Kindly complete within a week. Good luck!


MainLoop requires further refactoring and testing

Main loop contains methods that are way too complex and big, requires breaking down, refactoring and testing.

Broke down in to more manageable chunks, but is still far from ideal. It is probably better to revisit the overall architecture and separate PlanktonControl.xaml.cs from the underlying model first.


Edits

Category

[X] Content fix

Updates.

Docs Build status updates of commit 80f69cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/microsoft365-maturity-model--communication.md
:bulb:Suggestion
View
Details

Community/benefits-of-using-powershell-with-sharepoint.md
:white_check_mark:Succeeded
View

Community/information-architecture-managed-metadata-vs-lookup-column.md
:white_check_mark:Succeeded
View

Community/media/microsoft365-maturity-model--communication/Microsoft365MaturityModel-Communication.png
:white_check_mark:Succeeded
View

Community/should-I-store-my-files-in-Teams-or-SharePoint-An-understanding-of-behind-the-scenes.md
:white_check_mark:Succeeded
View

Community/working-with-modern-clientside-pages-using-pnp-powershell.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--communication.md

Line 37, Column 0: [Suggestion-disallowed-heading] Heading 'Feedback' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Revert Prelude change

@parsonsmatt suggested that the implicit import of the custom prelude would be confusing to beginners. Instead we should just keep explicit imports of Cardano.Prelude.

This is also includes updating the Usage section of the README


[SPARK-16587] [CORE] The annotation for the abstract Class 'BlockTransferMessage' missing several kind of messages.

# What changes were proposed in this pull request?
Currently, the Messages used by shuffle: OpenBlock, UploadBlock, RegisterExecutor has a simple introduction for the usage, while the other three (StreamHandle, RegisterDriver, HearBeat) haven' t.
This PR added them.
# How was this patch tested?
Please let some commuters to review the added annotation to judge them.

Can one of the admins verify this patch?

I'm not clear if this matches the intent of the other docs. I'd close this unless we can get a clearer picture of the intent of these messages.

Hm, not sure what to do here. Unless we can get an informed double-check on the correctness of this, I think I'd just not do it.

@f7753 I think just listing the message types here is not super useful. Yes, new messages were added and not mentioned in the documentation, but then adding just "foo is used by bar" doesn't really help in understanding the protocol at all.
Could you close this PR please?


Rendering of the 'Position' function is wrong

The SQL signature is
position(substring in string)

and we're rendering the parameters separated by a colon.

Similar problem to https://github.com/zio/zio-sql/issues/208


[TB-3267] minor edits for bookmark bottom sheet

What 🕵 🔍
edits for bookmark bottom sheet
Can be reviewed commit by commit

Codecov Report

Merging #57 (dda4bf7) into main (4791da3) will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
- Coverage   50.23%   50.10%   -0.13%
==========================================
  Files          54       54
  Lines        1941     1946       +5
==========================================
  Hits          975      975
- Misses        966      971       +5

Impacted Files
Coverage Δ

lib/src/linden/xassets.dart
4.34% <0.00%> (-0.06%)
:arrow_down:

lib/src/linden/xcolors.dart
35.71% <0.00%> (-0.26%)
:arrow_down:

lib/src/linden/xsizes.dart
54.28% <0.00%> (-0.79%)
:arrow_down:

lib/src/widget/bottom_sheet/bottom_sheet_base.dart
0.00% <0.00%> (ø)

lib/src/widget/button/app_ghost_button.dart
45.00% <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 4791da3...dda4bf7. Read the comment docs.


Disable signing artifacts for PRs and develop

Pull Request Description
Added *-sign-artifacts to disable/enable signing. By default it is true, except for PRs and develop.
Important Notes
#11082
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] Unit tests have been written where possible.

Please be gentle, my Rust is rusty.

1h15' -> 26'

So opening non-notarized/unsigned Enso app will show a big red error on MacOS. The only possibility is to enable opening such files via https://support.apple.com/en-us/102445#openanyway, right-click and open anyway.
@jdunkerley is this acceptable?

For me that's OK, as long as this is limited to PR builds. Faster PR checks are a big deal, and we shouldn't publish those builds anyway. For occasional debugging purposes the extra step to open is not a big deal.


Error in project Xamarin.IOS compile

Description
Installing on all platforms, Android, IOS and in the Portable project, when compiling for the IOS version the following error occurs:
Could not link assemblies. Reason: Error while processing references of 'app.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
For Android the project is compiled without problems.
Xamarin. forms = <IP_ADDRESS>7729

Version with issue: <IP_ADDRESS>0
Last known good version: <IP_ADDRESS>0
Platform: Xamarin.IOS

Hi,
For those of you with the same problem, the solution for me was to upgrade to the latest version of Mono on the Mac.


Gemfile with source blocks partly working

I have a Gemfile with two sources which looks like this:
source "xxx"
source 'https://rubygems.org'

gem 'a'
gem 'mygem'
gem 'c'
# [...]

when I ran bundle with the latest bundler (1.8.3) it said I should provide a block to source to let it know where to pull gems from, this is a really nice feature I wanted so I jumped on it and tried to change my Gemfile to:
source "xxx" do
  gem 'mygem'
end

source 'https://rubygems.org'

gem 'a'
gem 'c'

and then I ran bundle, until then everything is fine, it exited without error and the gem in and outside the block were listed on the output.
Now comes my problems ^^
$ bundle install
[...]
Bundle complete! 46 Gemfile dependencies, 99 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

$ bundle check
Resolving dependencies...
Bundler can't satisfy your Gemfile's dependencies.
Install missing gems with `bundle install`.

$ bundle exec irb
Could not find gem mygem' in rubygems repository http://<myrepo_url>.
Source does not contain any versions of 'mygem'
Run `bundle install` to install missing gems.

Did I do something wrong ?
PS: I tried to put the source with block at the end of the file but it changed nothing, same error.

I have the same issue.

Same here

Thanks for the report. Would any of you be able to test out a fix?
https://github.com/TimMoore/bundler/tree/revert-local-rubygems
Clone that repo, check out the revert-local-rubygems branch, then run rake install to install the patched version.

it works for me with your branch :)

Bundler 1.8.4 has been released with this fix.

thanks :)

@TimMoore the new version seems to work - partly.
Running bundle exec rails s starts the process with inconsistent versions of the gems in the block.
Not the versions in the Gemfile.lock
Reverting to a Gemfile without blocks solves the issue.

@fracklen could you create a new issue with the details from bundle env (replacing any private credentials with dummy credentials)? Also include any other details that might be relevant... for example, what versions of the gems are being used instead of the locked versions?

1.8.4 fixed the problem for me.

I'm using version 1.10.6 of bundler and it doesn't find the gems declared in a source block.

Please open a new ticket after following following ISSUES.md.
On Fri, Jul 31, 2015 at 7:00 PM, Vladimir Carballo
<EMAIL_ADDRESS>wrote:

I'm using version 1.10.6 of bundler and it doesn't find the gems declared in a source block.
Reply to this email directly or view it on GitHub:
https://github.com/bundler/bundler/issues/3432#issuecomment-126849094


Please add firebase storage api support for angularfire2

Hi,
By reading the current version angularfire2's docs and source code, I could not find any clue to how to use Storage from AngularFire.  Has Firebase storage API been supported from angularfire2?

Hi @jnupeter, we will be adding support in the future. Follow #213.

Is there an update on the status of this issue? I would like to be able to access images on Firebase via AngularFire2. If Firebase storage support has not been implemented in AngularFire2. What is the best practice to access content such as images via AngularFire2? Thanks!

needed feature hope that will be soon

@kabdessamad1 Issue#940 is a great start for that....it's on the horizon....but no definite timetable.
In the meantime, here's how you can access the storage api right now: https://github.com/angular/angularfire2/issues/946#issuecomment-299639239


Allow for custom types and interfaces

Type safety is currently being hardcoded in the code base. This makes it impossible for customers to interact with custom types.
While this isn't an issue for the final production build, customers will have a hard time to extend
The following 2 examples illustrate the problem in our code base:

Customise facade layer
The facade layer contains a direct reference to the OCC models. Customers who have extended the product model, will not get any type safety for these new interfaces.

import { Product } from '../../occ/occ-models/occ.models';

export class ProductService {
  get(productCode: string, forceReload = false): Observable<Product> {}
}

Custom components
The component use the facade layer to get entities from the backend, and have added the typesafe models to the observed stream data. This is convenient both for the view logic as well as for business logic. Customers who extend this cannot benefit from custom types.

import { Product } from '@spartacus/core';

export class ProductDetailsComponent implements OnChanges {

  ngOnChanges() {
    this.product$ = this.productService.get(this.productCode)
  }

}

In order to provide for custom type safety, we should do the following:

move our interfaces to a library, i.e. @spartacus/types
reference the interfaces from the new library, both from the core and storefront library
add a tsconfig path configuration

Customers can then introduce custom interfaces which extend the default interfaces provided by Spartacus. This requires a path configuration, so that the typescript compiler knows where to load default and customer interfaces from.
An additional desired side effect of this approach is that we can update the typing library with each backend release. Having a specific version dependency will work towards a model where the dependency setup will dictate the backend version we're using.

Moving this back as it's not required before launch. Customers can create custom types by extending the default types.
interface CustomProduct extends Product {
  magic?: string;
}

@Injectable()
export class CustomProductService extends ProductService {
  get(productCode: string): Observable<CustomProduct> {
    const product: CustomProduct = { code: productCode, magic: 'Tobi 😉'};
    return of(product);
  }
}

During the work on product scopes, @dunqan has done some more work around this topic. Unfortunately ng-packagr doesn't export the symbols in the root. If it would (something we'll investigate going forward), we could do the following:
declare module '@spartacus/core' {
  interface Product {
    magic?: string;
  }
}

Alternatively, or on top of this, we can alter our core layer, with generics, so that customers can invoke a service with custom type, i.e.:
constructor(protected currentProductService: CurrentProductService<MyProductType>) {}

The latter might give additional benefits, but will effect the entire core model.


Add array reshape rev

Closes https://github.com/EnzymeAD/Enzyme.jl/issues/310

Codecov Report

Merging #380 (464a81c) into main (08cc624) will decrease coverage by 1.75%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #380      +/-   ##
==========================================
- Coverage   76.09%   74.33%   -1.76%
==========================================
  Files          17       17
  Lines        4074     3904     -170
==========================================
- Hits         3100     2902     -198
- Misses        974     1002      +28

Impacted Files
Coverage Δ

src/compiler.jl
75.45% <ø> (+0.69%)
:arrow_up:

src/compiler/orcv1.jl
0.00% <0.00%> (-80.77%)
:arrow_down:

src/compiler/utils.jl
43.54% <0.00%> (-36.14%)
:arrow_down:

src/compiler/interpreter.jl
90.90% <0.00%> (-9.10%)
:arrow_down:

src/compiler/validation.jl
58.80% <0.00%> (-6.22%)
:arrow_down:

src/compiler/orcv2.jl
66.32% <0.00%> (-6.06%)
:arrow_down:

src/pmap.jl
83.33% <0.00%> (-1.29%)
:arrow_down:

src/typeanalysis.jl
90.00% <0.00%> (-0.91%)
:arrow_down:

src/typetree.jl
86.55% <0.00%> (-0.55%)
:arrow_down:

src/Enzyme.jl
86.54% <0.00%> (-0.15%)
:arrow_down:

... and 2 more

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 08cc624...464a81c. Read the comment docs.


Compose Material3 1.2.0 release version is very poor

fun PullToRefreshSample() {
    var itemCount by remember { mutableStateOf(15) }
    val state = rememberPullToRefreshState()
    if (state.isRefreshing) {
        LaunchedEffect(true) {
            // fetch something
            delay(1500)
            itemCount += 5
            state.endRefresh()
        }
    }
    Box(Modifier.nestedScroll(state.nestedScrollConnection)) {
        LazyColumn(Modifier.fillMaxSize()) {
            if (!state.isRefreshing) {
                items(itemCount) {
                    ListItem({ Text(text = "Item ${itemCount - it}") })
                }
            }
        }
        PullToRefreshContainer(
            modifier = Modifier.align(Alignment.TopCenter),
            state = state,
        )
    }
}

The display of the refresh header and the triggering of the refresh operation are very difficult to control.
I still choose to use your library

fun PullToRefreshSample() {
    var itemCount by remember { mutableStateOf(15) }
    val state = rememberPullToRefreshState()
    if (state.isRefreshing) {
        LaunchedEffect(true) {
            // fetch something
            delay(1500)
            itemCount += 5
            state.endRefresh()
        }
    }
    Box(Modifier.nestedScroll(state.nestedScrollConnection)) {
        LazyColumn(Modifier.fillMaxSize()) {
            if (!state.isRefreshing) {
                items(itemCount) {
                    ListItem({ Text(text = "Item ${itemCount - it}") })
                }
            }
        }
        PullToRefreshContainer(
            modifier = Modifier.align(Alignment.TopCenter),
            state = state,
        )
    }
}

The display of the refresh header and the triggering of the refresh operation are very difficult to control.
I still choose to use your library

Because pullToRefreshState cannot be directly controlled in viewmodel

You can use state.startRefresh() to trigger it directly.

You don't understand me. The old version of PullToRefresh triggered refresh through the onRefresh callback, but now it uses state.isRefreshing. That is to say, the current version of state.isRefreshing not only indicates whether the current UI displays the refresh key state, but also indicates that the refresh action is to be triggered.
Two versions of the API are used below to implement the same function:
old example:
@Composable
fun Example() {
    val viewModel = remember {
        ViewModel().also {
            val needAutoRefresh = true // If needed
            if (needAutoRefresh) {
                it.refresh()
            }
        }
    }
    val state = rememberPullRefreshState(refreshing = viewModel.isLoading, onRefresh = {
        viewModel.refresh()
    })
    Box {
        Column {
            Text(text = viewModel.text)
            Button(onClick = {
                viewModel.refresh()
            }) {
                Text(text = "refresh")
            }
        }

        PullRefreshIndicator(
            refreshing = viewModel.isLoading,
            state = state,
            modifier = Modifier.align(Alignment.TopCenter),
        )
    }
}

class ViewModel {

    var isLoading by mutableStateOf(false)

    var text by mutableStateOf("")

    fun refresh() {
        isLoading = true
        viewModelScope.launch {
            // fetch something
            delay(1500)
            text = "hello"
            isLoading = false
        }
    }
}

new example:
@Composable
fun Example() {

    val state = rememberPullToRefreshState()

    val viewModel = remember {
        ViewModel().also {
            val needAutoRefresh = true // If needed
            if (needAutoRefresh) {
                state.startRefresh()
            }
        }
    }

    if (state.isRefreshing) {
        LaunchedEffect(true) {
            viewModel.refresh(state)
        }
    }

    Box {
        Column {
            Text(text = viewModel.text)
            Button(onClick = {
                state.startRefresh()
            }) {
                Text(text = "refresh")
            }
        }

        PullToRefreshContainer(
            modifier = Modifier.align(Alignment.TopCenter),
            state = state,
        )
    }
}

class ViewModel {

    var text by mutableStateOf("")

    fun refresh(state: PullToRefreshState) {
        viewModelScope.launch {
            // fetch something
            delay(1500)
            text = "hello"
            state.endRefresh()
        }
    }
}

I think the old version is better than the new version. The API and isLoading status of the new version must only be controlled through PullRefreshState and cannot be uniformly placed in viewModel

See https://github.com/Omico/androidx-compose-material3-pullrefresh/commit/04e019da3a923d68d111cc0bf5a2141dc711966f
I hope this is what you are struggling with.
By the way, I'm not working for Google.
If there is some issue that you feel uncomfortable with Jetpack Compose Material.
You should send an issue to Google via https://issuetracker.google.com/issues/new?component=742043&template=1590761

See 04e019d
I hope this is what you are struggling with.
By the way, I'm not working for Google. If there is some issue that you feel uncomfortable with Jetpack Compose Material. You should send an issue to Google via https://issuetracker.google.com/issues/new?component=742043&template=1590761

Thank you, you are very enthusiastic

发现你是国人，😄

I support that in the new implementation from Google it is very difficult to control the state of the indicator, because they themselves violate their Jetpack Compose ideologies .
The idea with andRefreshing/ startRefreshing seems to be bad, because it is very difficult to make it compatible with VIewModel. Previous implementation seems to be more intelligently designed


Feature/flow-tree-view

Description
This PR should implement the flows tree view feature requested here: #5627. For the initial structure I took inspiration from the work of @Rishabhg71 (#5996). Then, I tried to reuse the component FlowTable that handles a lot of stuff already such as the sorting, selection, highlighting etc.
I am opening this draft PR so you can check what I am doing.
https://github.com/mitmproxy/mitmproxy/assets/100372313/ea60af1a-1914-4112-8f6a-57d494ceb55c
Checklist

[ ] Adjust UI
[ ] Adjust sorting since now is "global"
[ ] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

Hello @mhils , I saw the sorting has been initially implemented in the state, so for the tree view now is "global" (as we can see in the recording). Basically, if I sort by time in the first table I sort by time in the other tables as well, which is not the best. What do you think?  Should we consider refining this behavior? In case of change, I must understand properly the logic behind it to avoid to break something :)

Judging from the video this looks interesting and I can see this being helpful. But that's not a tree and you can achieve similar things by filtering for a given host. The way I understand the linked issue is that if you have hundreds of flows in deeply nested routes such as /api/*/*/*/* there is no high-level way to view this structure to understand it and look at sub-routes etc.

I'd be inclined to say that this should be possible without a third-party library.
But more importantly, the flow table is a really core UX element and we shouldn't rush to implement things here. For example, it could also make sense to have this tree in a dedicated sidebar with checkboxes for individual path parts. Have we looked at what other tools do here in terms of UX?

I'd be inclined to say that this should be possible without a third-party library.
But more importantly, the flow table is a really core UX element and we shouldn't rush to implement things here. For example, it could also make sense to have this tree in a dedicated sidebar with checkboxes for individual path parts. Have we looked at what other tools do here in terms of UX?

yes regarding the third-party library it's fine! For the tree, you mean that we could have a tree on one side where we can select the paths we want to display in the table?
Ex.

Mitmproxy.com
- Mitmproxy.com/1
-Mitmproxy.com/1/1
- Mitmproxy.com/2
example.com
google.com

we can select the parent Mitmproxy and display just this subtree in the table? basically acting like a filter. correct ?

Yes, basically that. I'm not saying it's a better UI/UX, just pointing out there are other options and we should look at existing work. :)

Yes, basically that. I'm not saying it's a better UI/UX, just pointing out there are other options and we should look at existing work. :)

yes yes, you're right. I can define a prototype and then send you the result to get a feedback :)

My suggestion would be to look at what others are doing and write that up. Before writing a single line of code. 😉

@mhils So far, I've only encountered examples where they provide the possibility to switch between the two modalities through a button. That's also the way I prefer the most! However, from what I've seen, it's quite challenging to reuse some of the table components because they are specifically designed for use with a table. So, if we want to proceed in this manner, we'll need to implement some new components and handle the filters in a different way(this is probably the hardest part). Otherwise, we can move forward with your idea, which seems a bit easier to implement and probably won't require too many changes (we just need to decide where to display this tree with the checkboxes).

So far, I've only encountered examples where they provide the possibility to switch between the two modalities through a button.

Could you please share screenshots and name the tools? Because all I've ever seen (e.g. Burp, ZAP, Charles) has this as a sidebar that allows you to filter the table. I can't really imagine how what you describe is supposed to work. The tree can have an arbitrary number of levels and on each level you could have a mix of sub-levels and then also the flows at the current level? How does the UX work? It would also be hard to virtualize this list mix I would assume.


Add the template code to the first custom file created, no matter the name

Fixes https://github.com/microsoft/pxt-microbit/issues/5367
It's frustrating to not have something to work off of if it's your first time creating custom blocks. Including our "creating blocks" template should not depend on that file's name being custom.ts. However, for those that are making a lot of custom blocks, having a template in every new file that you make would be frustrating to deal with. Thus, we've changed it so that we are no longer special casing custom.ts. For the first custom file that you make, no matter the name, the template will be included in that file. Any subsequent custom files made will have the Add your code here comment as is the current behavior.
Upload target: https://makecode.microbit.org/app/6b84da6b59b4491ed7055b51c377ce774d5774e0-f63aae8ed5

@jwunderl, yeah, it was just a me thing/possibly a race condition that I was hitting. As you suggested, when I switched over to blocks, the category was there as expected. It also looks like I'm not running into the same problem with the upload target, so I'm guessing it was just some weirdness I saw locally.

@jwunderl, yeah, it was just a me thing/possibly a race condition that I was hitting. As you suggested, when I switched over to blocks, the category was there as expected. It also looks like I'm not running into the same problem with the upload target, so I'm guessing it was just some weirdness I saw locally.

Interesting, weird that it sounded like it was working nicely for custom.ts. maybe we have some special cased logic for ignoring caches related to custom.ts or something along those lines, would have to check; thanks for info!


VRPTW: vehicle.route is duplicate information

Maybe we can have javascript side calculate this? To avoid increasing the json payload size.
    @JsonProperty(access = JsonProperty.Access.READ_ONLY)
    /**
     * @return route of the vehicle
     */
    public List<Location> getRoute() {

Addressed in https://github.com/TimefoldAI/timefold-quickstarts/pull/53.


Parsing error tsconfig.json

Hi,
i am getting the following error at the beginning of each file
Parsing error: Cannot read file '........../src/tsconfig.json'.eslint
Can you help me?
I'm on WSL 2 (Ubuntu)

You need to open the project at the root folder in VSCode.