[SPARK-48374][PYTHON][TESTS][FOLLOW-UP] Explicitly enable ANSI mode for non-ANSI build

What changes were proposed in this pull request?
This PR proposes to explicitly set ANSI mode in test_toArrow_error test.
Why are the changes needed?
To make non-ANSI build passing https://github.com/apache/spark/actions/runs/9342888897/job/25711689943:

======================================================================
FAIL [0.180s]: test_toArrow_error (pyspark.sql.tests.connect.test_parity_arrow.ArrowParityTests.test_toArrow_error)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/__w/spark/spark/python/pyspark/sql/tests/test_arrow.py", line 1207, in test_toArrow_error
    with self.assertRaises(ArithmeticException):
AssertionError: ArithmeticException not raised

----------------------------------------------------------------------
Ran 88 tests in 17.797s

Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
Manually.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.


How to rotate the pointer cursor with the thumbstick and control teleport facing direction

Being able to rotate the cursor pointer so when you teleport you are then facing in that direction is a useful feature that is used in many games and experiences. A tutorial showing how to do this would be good.

https://www.youtube.com/watch?v=wndyI-pcQS8


Add manual cron job buttons

Following last semester's month-long cron outage, we should have some way for admins to manually trigger cron jobs so that we don't run into issues where reservation statuses are horribly out of date (see #1274). We'd have to look into the process for triggering rake tasks via web request (e.g. does it have to be written as a separate controller action vs lib task...).

Does this seem like the appropriate way to do this? Also - should this feature be accessible from Admin dropdown in the navbar at the top of the screen?

This answer seems to be the most relevant to me; you're going to want to create a set of controller actions that run various rake tasks. Alternatively we might just offer the option to trigger either the hourly tasks or the daily tasks (using the tasks we set up for Heroku), limiting it to two actions.
In terms of placement, we can just place the buttons inside the settings page so that we don't have to worry about setting up a separate view for this. How does that sound?

This might be bundled into #1328, just FYI.

If we do set this up, it should probably be restricted to superusers.

It seems like the best way to do this might be by moving rake task functionality to jobs (like Active Jobs), switching the scheduled tasks to run those jobs, and then being able to run those jobs from the settings page.

That sounds like the perfect way to solve this, it also ties into #1302. I'll review the PR now.


Run tor browser

Can you add support tor browser? Or may be create new image.

Are you talking about https://www.torproject.org/projects/torbrowser.html?

I've added the Tor browser to https://feathub.com/jlesage/docker-apps/


Refactor RealmService

[ ] Method create(_:completion:) won't be used. So it needs to be deleted.
[ ] Method fetch(_:predicate:sorted:completion:) should't be generic.

Hi, I am thinking maybe you cam just use EasyRealm?

Hi, I am thinking maybe you cam just use EasyRealm?

The main idea is to use services, so we can isolate third-party frameworks from the rest of the app.
If we use EasyRealm, we must import it everywhere. So if you can isolate it in some kind of service, maybe we can use it.

Why do we need it at all? =) Can you show me a chunk of code from the app where you would use it and how?

Haha, I think the main purpose for EasyRealm and RealmService are equal, so maybe only need one existence. so my idea is bad and conflict to this issue.
You are right, we don't need it at all. I will try use this as a reference and extract some part of code that could be combine.

@5SMNOONMS5 I'll be waiting for your PR =)


[QUESTION] Which parameter should I set in helm-chart to pass tolerations to the daemonsets: longhorn-csi-plugin and engine-image-ei?

Question
Hi! I've been trying using Longhorn but I faced with the following problem: I can't pass tolerations to the daemonsets which are created automatically - longhorn-csi-plugin and engine-image-ei.
Could you tell me which option in helm-chart should I configure to fix this issue?
My current config is:
defaultSettings:
  taintToleration: "infra=true:NoSchedule,node=true:NoSchedule"

longhornManager:
  tolerations:
    - key: "infra"
      operator: "Exists"
    - key: "node"
      operator: "Exists"

longhornDriver:
  tolerations:
    - key: "infra"
      operator: "Exists"
  nodeSelector:
    type: infra

longhornUI:
  tolerations:
    - key: "infra"
      operator: "Exists"
  nodeSelector:
    type: "infra"

Environment:

Longhorn version: 1.1.2
Kubernetes version: 1.20
Node config

OS type and version N/A
CPU per node: N/A
Memory per node: N/A
Disk type N/A
Network bandwidth and latency between the nodes: N/A

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Hybrid (Rancher in Hetzner cloud + some dedicated machines)

You could refer to the #2664
Could you copy the output kubectl get settings taint-toleration -n longhorn-system to here?
Or you could check the value at Longhorn GUI Kubernetes Taint Toleration.

kubectl get settings taint-toleration -n longhorn-system

Hi @jenting! Thank you for quick reply.
The result of the command above is:
kubectl get settings taint-toleration -n longhorn-system
NAME               VALUE   AGE
taint-toleration           24h

How can I configure this setting via helm-chart? I thought this
defaultSettings:
  taintToleration: "infra=true:NoSchedule,node=true:NoSchedule"

should make it work, shouldn't it?

Yes, but since we have issue #2570.
So, a fresh install is okay, but once the setting CR be created before updating the taint-toleration, it'll no work.
I'd suggest changing it via GUI now.

Thank you. Your advice has helped me.
Closing an issue.


Update sceneanalysiseffect_sceneanalyzed.md

Add link to the args (sceneanalyzedeventargs) returned when the event fires for quick lookup

@drewbatgit :

Looks like an extra space was prepended to the opening "---" delimiter of the metadata block. Remove before merging?
PR otherwise passed checklist review. Please review for technical accuracy, etc., and approve/merge if appropriate.


Design changed when changed the version from 8.4 to 9.1 in 5s

Hai, i checked an react-example: in Iphone5s device version:8.4,with the same 5s device, when i changed the version to 9.1 I got a design problem, and i have doubt that how to fix the same font view for different devices,
I  am using:
react-native: 0.11.4

Hi there! Please post this to StackOverflow with more details, thanks!


KeyError: 'bridgeid'

I run HA 2022.4.7 in a Docker container (Intel NUC11, Ubuntu 20.04.4 LTS).
I am not sure when this started, but after every restart I see this in the logs:
2022-04-27 17:10:01 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 74, in _async_process_pending_flows
await gather_with_concurrency(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 192, in gather_with_concurrency
return await gather(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 190, in sem_task
return await task
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 205, in async_init
flow, result = await task
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 232, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data, init_done)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 335, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/components/hue/config_flow.py", line 241, in async_step_ssdp
self.bridge = await self._get_bridge(
File "/usr/src/homeassistant/homeassistant/components/hue/config_flow.py", line 75, in _get_bridge
bridge = await discover_bridge(
File "/usr/local/lib/python3.9/site-packages/aiohue/discovery.py", line 35, in discover_bridge
bridge_id = await is_hue_bridge(host, websession)
File "/usr/local/lib/python3.9/site-packages/aiohue/discovery.py", line 82, in is_hue_bridge
return normalize_bridge_id(data["bridgeid"])
KeyError: 'bridgeid'

I've seen this post in the official community - so I am not the only one with this message.

Then maybe it‘s the Node-Red extension „ node-red-contrib-amazon-echo-oztourer“. It emulates a Hue bridge in Node-Red.

Yep, that is the answer. It emulates a Hue bridge but it doesn't do that 100% exactly like a Hue bridge.
Our discovery in HA discovers the emulated bridge and tries to query it, resulting in this error.
Best way would be if those emulator projects just fix their response but we'll try to workaround it in our discovery code.

Same error here and it was node-red-contrib-amazon-echo 0.1.10.  Removed my experimental flows and that node from Node-RED, restarted HA and...


try enable i18n

I had learned from https://gohugo.io/content-management/multilingual/ and try to enable i18n for Chinese.
This pr is about project structure but not translation for specific content. Hence I leave a Chinese in page as "施工中"(which means WIP for Chinese).
as a part of #251

preview at https://deploy-preview-271--tag-env-sustainability.netlify.app/zh/landscape/

@rootfs , @leonardpahlke could you please help with this PR?

Will take a look at it tomorrow

cc @cjyabraham @chalin

Drive by comments ...

IMHO, "Cloud Native Sustainability Week" should be under events. By moving it, that would resolve the top-nav spacing issue :)
Given the maintenance overhead, for other projects, we usually want folks to commit to maintaining language translations for a while before bring it in.
Also, there are some Korean pages. If this site starts officially using the multilingual feature, then the Korean pages should be "upgraded" to us that features.

Also, there is a way to set this up so that any given language whose page translations are missing fall back to en.

IMHO, "Cloud Native Sustainability Week" should be under events. By moving it, that would resolve the top-nav spacing issue :)

Lets do that. We put it on the front page since folks were searching for this, and this lowered the barrier to find the resource. Now the week is over, we can move it. Is there a way to perseve the link? tag-env-sustainability.cncf.io/cloud-native-sustainability-week/ after we moved the page?

You can use an alias in the frontmatter of the page.

Also, there is a way to set this up so that any given language whose page translations are missing fall back to en.

I think that might be a strange UX. It would mean someone who deliberately chooses Chinese goes instead to the English page.
Currently if a page is missing and someone chooses Chinese, it takes them to the homepage of the site in Chinese, which I think makes more sense (assume we translate the homepage). At that point the user can see in the nav what pages are available in that language.

Thanks @leonardpahlke , @cjyabraham and @chalin
Sorry for replay late. I am quite busy in recently, and as I contribute to open source in my personal time...
I suppose we have items here as todo:

We need to move the week into event, and keep alias ref https://bwaycer.github.io/hugo_tutorial.hugo/extras/aliases/
for this, I suppose Leo can open a ticket. (let's see who has time to make it, as thanks giving is near by)
I do agree that we need to contribute into specific folder's for different language. Which means:

Sustainable computing is a global things, hence we need i18n as we don't want language becomes blocker between our communication.
Technologically we will need to restructure our folder with EN for English?
For our audience, it will look strange as just one or two pages in native language and rest of them in English.
for this, I suppose we need one task for EN folder, and a kind of PR template to enable i18n for a language. (which means i18n team should contribute to native language content 1st then enable the i18n option on website?)

For this PR, maybe I should close it?
it will be a good place as our discussion for i18n related things, and others can reference later on?

issue opened: https://github.com/cncf/tag-env-sustainability/issues/278

@leonardpahlke , I try to follow @cjyabraham 's suggestion create an en folder and move the contents. But there some lint issue. I suppose I need to add skip lint in those files?

@guidemetothemoon @leonardpahlke , I don't mind to ref https://github.com/cncf/tag-env-sustainability/commit/7d314130232afcaba82b55f340dbcb33bbc5210e#diff-6dbf3e19d9e5049af0f8b9e1727da1c04a899297cf6a835bdde0e0ad7b3d62d7R54 to add technological wordings. but we still find people's name in our meet up page. Hence is there any way to skip cSpell checking? as there will be people's name and adding people's name as glossary is too wired.
any other suggestion?

Thanks @SamYuan1990 for working on this!! 🙌

Sustainable computing is a global things, hence we need i18n as we don't want language becomes blocker between our communication.

yes, in the last meeting we also had voices about adding content in Spanish. I am sure there are also folks that would like to add content in German and other languages. +1 adding multi language support across the website and follow the glossary folder structure to achive this, as previously proposed. We can update the folder structure with this PR. Governance wise, we could discuss a content translator role in the TAG (but we will do that outside of this PR).

I don't mind to ref https://github.com/cncf/tag-env-sustainability/commit/7d314130232afcaba82b55f340dbcb33bbc5210e#diff-6dbf3e19d9e5049af0f8b9e1727da1c04a899297cf6a835bdde0e0ad7b3d62d7R54 to add technological wordings like Istio. but we still find people's name in our meet up page. Hence is there any way to skip cSpell checking? as there will be people's name and adding people's name as glossary is too wired.
any other suggestion?

@guidemetothemoon perhaps you can answer this one best.

@leonardpahlke @SamYuan1990 We've recently refactored QA checks for pull requests, where spelling validation hasn't properly worked until now... but now it does, which is the reason for why you get more errors on modified files. I have a plan to run all those validations towards existing files in the repo to just fix most of the issues for what already exists in the repo, but I haven't come that far yet.
Regarding the names: it doesn't look like cSpell is very good at recognizing names and there's no easy, straightforward way to ignore those so I'm currently looking into ways to resolve this scenario in a more efficient manner. Since I'm planning to run these validations towards existing files in the repo in the coming days I would say it's ok just to merge the changes with the failing spelling check since those will be fixed anyway in a subsequent PR. Or if the PR will still be active for some days then those will be resolved by themselves once I publish the PR that will resolve these issues.
P.S. the tool did raise some meaningful errors that would be great to update if you will be doing any further updates in this PR (f.ex. "timewindow" or "manufactural") 😊

Option one: keep this PR open and wait @guidemetothemoon to check all existing wording and then rebase.
Option two: I am fix this PR with all missing wording. No matter it's name or .... but I can fix typo or keep everything to Istio. Then @guidemetothemoon check all the files later on?
May I know we are on same page, as if both of us make correction on files, we will conflicts aren't we?

@SamYuan1990 almost what I was thinking, but to avoid conflicts I can suggest following:

If the QA checks is the only blocker for merging this PR then we can merge it as is and I will fix the raised QA errors in the subsequent PR;
or
You can resolve the errors as part of this PR and temporary add the names to our custom dictionary (basically option two that you mentioned), as explained here: https://github.com/cncf/tag-env-sustainability/blob/main/writing-style.md#fixing-qa-errors . Once I add a more efficient solution for handling the spell check of names I will clean up what's needed in a subsequent PR, after this PR is merged, to avoid conflicts;

I hope it made it a bit clearer? What do you think?

Sounds good to me thanks @SamYuan1990 :)

@SamYuan1990 I've published a PR which contains further improvements to the QA checks and establishes the baseline for existing content: #289
Once it's merged the amount of build errors in your PR should also be reduced. I've also tried to handle the spell check of names as optimal as possible, but it's a challenging string to filter completely so in some cases you may still need to add an ignore field to filter out the specific name, as described here: https://github.com/cncf/tag-env-sustainability/blob/ebee70989abac87b8f8b5df405a4a0bbd0869c88/writing-style.md
If you still experience any errors after #289 is merged, please let me know and I can add a change suggestions directly on your PR to fix it asap.
Thanks!

It's a bit hard to follow what this PR is trying to do without reading through all the comments. Perhaps keeping the PR name and description up-to-date would be helpful for anyone trying to review.
I have read through the comments, however, so it seems that this PR is for moving all files into /en/, which works fine. Could you remove the website/content/en/landscape/_index.zh.md file, since that's not the correct filename format anyway, right? I assume that was just leftover from previous commits.

but if so, btw @leonardpahlke , @cjyabraham may I know any comments for Korean content? Honestly I can't speak Korean, should I make a Korean folder? so I can just move existing content in to a Korean folder.  Or others can make it in another pr? after this PR been merged?

Yes, if we have content in korean already, lets create the folder. FYI @sysnet4admin @seokho-son

Yes, if we have content in korean already, lets create the folder. FYI @sysnet4admin @seokho-son

please let me know if a ko folder is needed and nice to cover in this PR. @cjyabraham

Personally, I don't see the need for an empty ko folder in this PR. Any team who submits ko translations can include that in their PR. Either way is fine, however, and I'd prioritize getting this PR merged.

Thanks!


Is it possible to use Giskard for computer vision / images?

Checklist

[x] I've searched the project's issues.

❓ Question

As in title, is it possible to use Giskard for computer vision, i.e. image datases? I am using HuggingFace for vision CNN models (ResNet, ConvNeXt etc.) and would like to test them.

Thanks for the question @j-adamczyk ! We're in the process of working on support computer vision. Would be great to get your feedback on our upcoming work.

Will report back once support is added

@luca-martial Any chance you are starting to work on this for computer vision? I would be happy to research the state-of-the art about perturbation methods for binary classification for CV let's say to get started. Let me know if this could help. :ok_hand:

@luca-martial Any chance you are starting to work on this for computer vision? I would be happy to research the state-of-the art about perturbation methods for binary classification for CV let's say to get started. Let me know if this could help. 👌

@yassineAlouini Thanks for suggesting this! We'll get back to you asap with more info!

@luca-martial Any chance you are starting to work on this for computer vision? I would be happy to research the state-of-the art about perturbation methods for binary classification for CV let's say to get started. Let me know if this could help. 👌

Hey @yassineAlouini, now we have a dedicated repo for CV: https://github.com/Giskard-AI/giskard-vision

@luca-martial Any chance you are starting to work on this for computer vision? I would be happy to research the state-of-the art about perturbation methods for binary classification for CV let's say to get started. Let me know if this could help. 👌

Hey @yassineAlouini, now we have a dedicated repo for CV: https://github.com/Giskard-AI/giskard-vision

That's great news!


Cleanup RNGs in toy datasets

The existing code fails if (for instance) a StableRNG is passed (because Random.seed!(StableRNG(...)) doesn't work)
This commit makes sure that the two following cases will work (as arguments to the rng= keyword)

pass nothing or an integer --> get a MersenneTwister (seeded if an integer is passed)
pass any AbstractRNG --> use that in all random calls

Codecov Report

Merging #326 into dev will decrease coverage by 0.32%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #326      +/-   ##
==========================================
- Coverage   82.65%   82.33%   -0.33%
==========================================
  Files          30       30
  Lines        2070     2060      -10
==========================================
- Hits         1711     1696      -15
- Misses        359      364       +5

Impacted Files
Coverage Δ

src/data/datasets_synthetic.jl
96.33% <100.00%> (+0.37%)
:arrow_up:

src/measures/finite.jl
95.62% <0.00%> (-3.13%)
:arrow_down:

src/data/datasets.jl
86.11% <0.00%> (-2.78%)
:arrow_down:

src/composition/networks.jl
65.56% <0.00%> (-1.32%)
:arrow_down:

src/hyperparam/one_dimensional_range_methods.jl
96.42% <0.00%> (-0.24%)
:arrow_down:

src/composition/composites.jl
90.67% <0.00%> (-0.15%)
:arrow_down:

src/resampling.jl
88.88% <0.00%> (-0.15%)
:arrow_down:

src/interface/univariate_finite.jl
100.00% <0.00%> (ø)

src/composition/arrows.jl
27.27% <0.00%> (+2.27%)
:arrow_up:

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 553e137...7f0eda6. Read the comment docs.


Bug in Razor code in the Generic Smart Form Example (fix included)

Mobius V5.03.01 Hybrid
DNN v.9.10.02
2SXC v12.10.0
Running the Generic Smart Form example without modification results in the following error:
Message:Customer Send mail failed: d:\Websites\dnn-9-10-2\Website\Portals\0\2sxc\MobiusForms5\live\email-templates\EmailToCustomerWithData.cs(24): error CS1061: 'System.Collections.Generic.Dictionary<string,object>' does not contain a definition for 'Subject' and no extension method 'Subject' accepting a first argument of type 'System.Collections.Generic.Dictionary<string,object>' could be found (are you missing a using directive or an assembly reference?)
Replacing line 24:
" + data.Subject + @"
with
" + data["Subject"] + @"
appears to fix the problem (no errors and the output looks correct).

@maaaximum

Thank you very much for fixing this.

Thank you very much for fixing this.


Upload JSON - what structure do we need to use?

I'm trying to automate the creation / updating of catalogs dynamically but the 'upload JSON' option has zero information / documentation about what this data structure should be - where / how do I find this info?

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

ID: 531e88be-7ca0-d290-d9f1-80ff8bd1f820
Version Independent ID: e6c155c1-0362-b600-a94b-57d0d12c5363
Content: Catalogs - PlayFab
Content Source: playfab-docs/features/commerce/items/catalogs.md
Product: playfab
GitHub Login: @joannaleecy
Microsoft Alias: joanlee

If you manually create a sample catalog, you can then export the catalog to JSON to get the format.  Not optimal, but doable.

Also found this repo which was very useful:
https://github.com/richjoslin/GoogleSheetsToPlayFab


Could not pass event InventoryCloseEvent to RewardsLite v3.1.8

I'm getting an error in console anytime a player closes an inventory - either a chest, a menu, or their inventory. It spams the whole console so it makes it completely unusable.
Here's the error: https://pastebin.com/pQt81LRv
I'm running v3.1.8 on Paper 1.20.6, so I am unable to use older versions of the plugin since it's not backward compatible.

I am running v3.1.8 on Purpur 1.20.4 and I get the same error
https://pastebin.com/Q8B1HY3u

This bug has been fixed in RewardsLite version 3.1.10.


Fuel scooping triggers Ship Refuelled multiple times

Hi,
I've found that fuel scooping can trigger the Ship Refuelled event multiple times during a single scooping session.  It seems that the Journal records the scooping in (roughly) 5 tonne intervals, which kicks off the event each time.  Here's an excerpt from my testing last night:-
{ "timestamp":"2017-04-19T22:20:02Z", "event":"FuelScoop", "Scooped":5.003216, "Total":22.701246 }
{ "timestamp":"2017-04-19T22:20:15Z", "event":"FuelScoop", "Scooped":5.000847, "Total":27.702089 }
{ "timestamp":"2017-04-19T22:20:29Z", "event":"FuelScoop", "Scooped":4.297902, "Total":32.000000 }

As you can see, these are about 13-14 seconds apart, and roughly 5 tonnes each.  This was a single scooping session with a 6C fuel scoop, not maxing out the scoop rate.  I may try to run my tank nearer to empty and go for a longer scoop at max rate and see what the results are.
I'm not sure if you can record these and report the added totals at the end, say if no scooping entries for 20 seconds or something.  However, if it's based on 5 tonne intervals, then it would depend heavily on the rate at which you can scoop; a lower scoop rate would mean a longer time interval.
I can't immediately see an easy way around this, but maybe you can come up with something?  I'll keep thinking about it and maybe I'll get some bright idea to suggest. :)
Darkcyde.

This isn't the type of thing that I'm prepared to take on in EDDI.  The change from a single entry to multiple entries for the same event should be raised as a bug with Frontier so that they can fix it at source.


Add docker-toolbox on windows workarounds.

Signed-off-by: Ozzy Osborne<EMAIL_ADDRESS>

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


site: add WebEngage for surveys

Enhancement Request
https://dashboard.webengage.com/accounts/14507c325/integrations

It's in prod.


Analyze dartpad

Description
This fixes the sample code analysis to treat dartpad snippets in the same way as snippet snippets, which it wasn't until now (the snippet generator was treating them as "samples"), and some errors crept in. This PR also fixes those errors.
Also, added a --verbose option to the sample analyzer.
Tests

Added a test for dartpad snippets in the test for the sample analyzer tool.

Breaking Change

[X] No, this is not a breaking change.

No, they shouldn't need to do anything special.


fix(web-components): select bugfix

when no options available the 'no options found' item cannot be selected

Summary of the changes
Can't have cursor event and pointer CSS changes on the same element, so I created a <span> to wrap the li option on a different layer, only when options not available, not when 'retry' is available.
Related issue
#2390

I think it looks a little bit confusing now, as it looks like you can click\select the "Loading error", as it has the cursor:pointer styling. maybe need to consider a solution where it just doesn't update the value?

Please make the commit message summary more descriptive of the change made

Approved, but raised new issue (not introduced by this change) https://github.com/mi6/ic-ui-kit/issues/2959


Add Jetbrains Space

Would be great if it would support Jetbrains Space as well: https://www.jetbrains.com/space/

It's been two years, I wonder if it will be ever implemented.


Loading moment as module and add to window

I'm using SystemJS to load moment as a dependency.
However I also require another library which depends on moment being defined as window.moment.
Is there a way to achieve this without this type of hack?
System.import('moment').then(function (moment) {
	window.moment = moment;
	System.import('./app');
});

That hack is probably the right thing to do, TBH. Some module systems break when we do export the global. We'd have to make it some kind of  option that gets passed in, which feels just as hacky and seems like it would be hard to get right across all the different module loaders.

So checking if window is defined and only registering it in that case is not a viable solution?

Apparently that causes issues for certain RequireJS scenarios. We used to always set it on the window no matter what and got a lot of pushback. I could certainly be convinced that when we changed it, we caused more problems than we fixed, but for better or for worse, it was a really explicit decision and switching it back seems painful in itself. We deprecated the require-but-also-global stuff in #1214 and #1220, where we logged that window.moment= stuff was deprecated in the presence of require and added an option to the require args to turn it off. The next release, we removed that option and made its behavior the default.
One option we could almost certainly support is a forceGlobal option in the require args. Basically the opposite of the change we made when we deprecated the global set (see here). I don't know enough about SystemJS to know if it could take advantage of that.
See also #2831.

A force global flag would be nice.
But I don't know yet if SystemJS can also pass these require flags - I will need to take a look at the docs.

You can enforce moment to be loaded as a global by SystemJS with the meta configuration:
System.config({
  meta: {
    'moment': { format: 'global' }
  }
});

Alternatively, if Moment isn't running as a global, you can configure in SystemJS moment to be a global for the global that is running:
System.config({
  meta: {
    'path/to/global-file.js': {
      globals: {
        moment: 'moment'
      }
    }
  }
});

both cases are handled through SystemJS, and not concerns for Moment itself though.

@guybedford This is awesome! Thanks for the info!

@olee how are you initially loading moment? I don't know anything about System.js but I've been getting a lot of questions about it lately so I'm trying to add this information to the docs.
Looking at the system.js docs, it looks like it's just
System.import('moment.js')

or
System.import('moment-with-locales.js')

That right?

This has been documented in PR moment/momentjs.com#310.
@guybedford  - did I get this one right? I'm just going off of your docs and what was said here.
Otherwise I think we're good to go.

Thanks @maggiepint, it looks great to me.


Getting an issue - "Window cleaned up before response" while trying to close the zoid instance

I am getting "Window cleaned up before response" while I try to close the exisiting zoid instance.

a similar issue, I am getting is "Target window is closed"
zoid.js:2424 Uncaught Error: Target window is closed     at zoid.js:2424     at zoid.js:2425     at Function.ZalgoPromise.try (zoid.js:306)     at send (zoid.js:2420)     at zoid.js:2069     at _loop (zoid.js:192)     at ZalgoPromise._proto.dispatch (zoid.js:210)     at ZalgoPromise._proto.then (zoid.js:223)     at TripStore.crossDomainFunctionWrapper [as classicCallbackFunction] (zoid.js:2056)     at TripStore.setCurrentTripById (Trip.store.ts:276)     at executeAction (mobx.module.js:713)     at TripStore.res (mobx.module.js:701)     at ZoidIframe.onTripChanged (ZoidIframe.tsx:75)     at Object.onTripChanged (ZoidIframe.tsx:61)     at zoid.js:1958     at _loop (zoid.js:192)     at ZalgoPromise._proto.dispatch (zoid.js:210)     at ZalgoPromise._proto.then (zoid.js:223)     at Object.handler (zoid.js:1957)     at zoid.js:2238     at Function.ZalgoPromise.try (zoid.js:306)     at Object.RECEIVE_MESSAGE_TYPES.postrobot_message_request (zoid.js:2235)     at receive_receiveMessage (zoid.js:2312)     at zoid.js:4147     at zoid.js:4156

Can you share a demo page where I can repro?


https://github.com/josnick/lab1-git-race

*Added comments to HelloController class
*Added comments to HelloControllerUnitTest class


Refactoring around CountryList

Preamble
See #315.
Description
This trims code around the CountryList quite a bit and starts the move from scss to styled-components. It also starts to tackle the binding of style <> functionality around classes by extract the style from some of them so that their functional role can be refactored away separately.
From the outside perspective, this is a no-op.
Types of changes

[x] Refactor
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have used ESLint & Prettier to follow the code style of this project.
~[ ] I have updated the documentation accordingly.~
~[ ] I have added tests to cover my changes.~
[x] All new and existing tests passed.

Did cursory QA in Chrome and Firefox to ensure that no regression seeped in, nothing to report.

As in #315, it's a no-op from an outside perspective, I'll just go ahead and carry on. :rocket:

Coverage increased (+0.4%) to 94.118% when pulling 07a70352318e016cccc7c2f3e37e304d5cf01341 on refactor-country-list into 3964ba1df35cd634be4613836552cde50980a098 on master.

:tada: This PR is included in version 8.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


All options are showing in 2.7.4

My current mission has "Nova Default" selected for Timeline Configuration. When I go to write a post, I have options for Mission Day, Date, Stardate, Time, and Timeline. I believe I should only be seeing either Date or Timeline.
When I select other options in the Mission edit page, I still have all of the above options showing.

v1.2.0 released with support for Nova 2.7.5+ and PHP 8.


Configurable behavior for non-supported upgrade

In a case if network activates an upgrade above current's node version:

Show a warning if current node's version is below a network's version. If node was upgraded after the network upgrade, show a warning indicating a dirty node's state. (enabled by default)
Shut down the node. (disabled by default)

Codecov Report

Merging #543 into develop2 will decrease coverage by 0.10%.
The diff coverage is 20.00%.

@@             Coverage Diff              @@
##           develop2     #543      +/-   ##
============================================
- Coverage     43.74%   43.63%   -0.11%
============================================
  Files           161      162       +1
  Lines          9940     9978      +38
============================================
+ Hits           4348     4354       +6
- Misses         5178     5209      +31
- Partials        414      415       +1

Impacted Files
Coverage Δ

gossip/sfc_index.go
46.06% <0.00%> (-1.06%)
:arrow_down:

gossip/store.go
63.09% <ø> (ø)

gossip/store_network_version.go
0.00% <0.00%> (ø)

version/version.go
50.00% <33.33%> (-21.43%)
:arrow_down:

gossip/service.go
47.55% <42.85%> (-1.00%)
:arrow_down:

gossip/config.go
100.00% <100.00%> (ø)

evmcore/tx_pool.go
74.73% <0.00%> (-0.91%)
:arrow_down:

inter/ascii_scheme.go
81.90% <0.00%> (+1.90%)
:arrow_up:

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 b379b36...5047115. Read the comment docs.


Closing tag '[/]' at position 73 has nothing to close

Hello, I try this tool but get error when first trying.
$ python3 main.py -u https://example.com
Traceback (most recent call last):
File "main.py", line 15, in
check_host(args)
File "/root/pinkerton/src/pinkerton/main.py", line 25, in check_host
print(f"[bold white on green]> Connected sucessfully with {url}[/] [/]")
File "/usr/local/lib/python3.7/dist-packages/rich/init.py", line 73, in print
return write_console.print(*objects, sep=sep, end=end)
File "/usr/local/lib/python3.7/dist-packages/rich/console.py", line 1643, in print
highlight=highlight,
File "/usr/local/lib/python3.7/dist-packages/rich/console.py", line 1501, in _collect_renderables
renderable, emoji=emoji, markup=markup, highlighter=_highlighter
File "/usr/local/lib/python3.7/dist-packages/rich/console.py", line 1396, in render_str
emoji_variant=self._emoji_variant,
File "/usr/local/lib/python3.7/dist-packages/rich/markup.py", line 170, in render
) from None
rich.errors.MarkupError: closing tag '[/]' at position 73 has nothing to close

I have the same issue

same issue

Sadly same issue😥

same

Same issue

yep same issue

just remove last [/] at the line 25 on src/pinkerton/main.py
from:
print(f"[bold white on green]> Connected sucessfully with {url}[/] [/]")
into:
print(f"[bold white on green]> Connected sucessfully with {url}[/]")

I have now committed a fix for this issue, can you check if it's working? @w4h4z etc...
Sorry for making you wait so long, I arrived to my home today only

Can confirm making the change recommended by @dimazarno worked. Thanks!

Thanks for confirming @IronLion267, I'll close this issue because the problem is already fixed. Thanks to everyone too!
Best regards,
oppsec.


Long logical ID (>100 characeters) breaks AWS::Lambda::Permission

What happened?
My CDK stack creates an AWS::Lambda::Permission resource with a long logical ID:
StockBotApiGatewayGETeventualexecutionsexecutionIdhistoryexecutionseventsintegrationPermission3C1EE9F9
This then results in an error:
  aws:lambda:Permission (StockBotApiGatewayGETeventualexecutionsexecutionIdhistoryexecutionseventsintegrationPermission3C1EE9F9):
    error: aws:lambda/permission:Permission resource 'StockBotApiGatewayGETeventualexecutionsexecutionIdhistoryexecutionseventsintegrationPermission3C1EE9F9' has a problem: expected length of statement_id to be in the range (1 - 100), got StockBotApiGatewayGETeventualexecutionsexecutionIdhistoryexecutionseventsintegrationPermission3C1EE9F9. Examine values at 'Permission.StatementId'.

Expected Behavior
Pulumi should probably truncate the name to avoid this problem.
Steps to reproduce
I'm not 100% sure where my code is creating this. I believe it's for when I configure an API GW v2 to trigger my Lambda:
import { HttpApi } from "@aws-cdk/aws-apigatewayv2-alpha";
import { HttpIamAuthorizer } from "@aws-cdk/aws-apigatewayv2-authorizers-alpha";
import { HttpLambdaIntegration } from "@aws-cdk/aws-apigatewayv2-integrations-alpha";

const handler= new aws_lambda.Function(this, "F", { .. });

new HttpApi(this, "Gateway", {
  apiName: `my-api`,
  defaultIntegration: new HttpLambdaIntegration("default", handler),
});

Output of pulumi about
CLI
Version      3.53.1
Go Version   go1.19.5
Go Compiler  gc

Plugins
NAME    VERSION
aws     5.28.0
nodejs  unknown

Host
OS       darwin
Version  13.1
Arch     arm64

This project is written in nodejs: executable='/Users/samgoodwin/.nvm/versions/node/v16.14.2/bin/node' version='v16.14.2'

Current Stack: sam-g/stock-bot/stock-bot

TYPE                 URN
pulumi:pulumi:Stack  urn:pulumi:stock-bot::stock-bot::pulumi:pulumi:Stack::stock-bot-stock-bot

Found no pending operations associated with stock-bot

Backend
Name           pulumi.com
URL            https://app.pulumi.com/sam-g
User           sam-g
Organizations  sam-g

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

For the record, my Permission Resource does not contain a Statement ID. I'm assuming that it is being defaulted to the logical ID? This is problematic because logical IDs can be longer than Statement IDs are allowed to be.

This does look like an autonaming issue, thanks for finding this!


Add ability to configure docker-sys bridge via cloud-init

RancherOS Version: (ros os version) 1.0.1
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.) qemu-kvm
This was discussed briefly last week in irc, but currently  the system-docker's networking is managed statically via assets/docker/cni/bridge.d/bridge.conf. It would be useful to be able to configure this via cloud-init.
In our use-case we have networks that clash with the default range. The current workaround is to modify it and build a custom iso/image.

Tested with RancherOS v1.2.0-rc2.
@mrbobbytables
Now you can use the following command to modify the system-docker network.
You can also use this command if you want to modify the system-docker network based on rancheros v1.2.0-rc2
ros os upgrade -i rancher/os:v1.2.0-rc2 --append "rancher.system_docker.subnet=<IP_ADDRESS>/16"

The above workaround  works only in v1.2.0.
try sudo ros os upgrade --append 'rancher.system_docker.bip=<IP_ADDRESS>/16' instead.
(see https://github.com/rancher/os/issues/2422#issuecomment-408013093)


StoreDevtoolsModule.instrumentStore not compatible with AOT

StoreDevtoolsModule.instrumentOnlyWithExtension()  works with AOT.
StoreDevtoolsModule.instrumentStore not compatible with AOT
getting an error of:
ERROR in Error encountered resolving symbol values statically. Calling function 'StoreDevtoolsModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in C:/msweb/studiotouch/src/app/app.module.ts, resolving symbol AppModule in C:/msweb/studiotouch/src/app/app.module.ts

And we rely on instrumentStore as we need to provide maxAge, otherwise our dev tools will not work (large data set)
can we please fix it so it works just like instrumentOnlyWithExtension
angular-cli: 1.0.0-beta.25.5
node: 6.5.0
os: win32 x64
@angular/common: 2.4.3
@angular/compiler: 2.4.3
@angular/core: 2.4.3
@angular/forms: 2.4.3
@angular/http: 2.4.3
@angular/platform-browser: 2.4.3
@angular/platform-browser-dynamic: 2.4.3
@angular/router: 3.2.1
@angular/compiler-cli: 2.4.3
@angular/language-service: 2.4.3

thanks as always,
Sean

@born2net the issue is in src/instrument.ts. There is two function calls not supported by AOT (it can't analyze them statically). This file contains the method you are using.
I've fixed this and it worked (AOT succeeded) with instrumentStore() but I won't have a PR until later when I am home and can run all the tests (run out of time for now).
This is the commit
In the meantime, if this is blocking you, clone that fork, npm install, and build the release with
npm run build:js && npm run build:umd && npm run build:uglify
Then the release folder is what it goes in your node_modules/@ngrx/store-devtools in your project.
AOT should build fine.
If you encounter other issues, or have suggestions, post them here, as we want a good PR. I haven't contributed to this project before.

TX SO MUCH.
No problem I will wait for the final commit, let me know when ready and I will test.
TX again,
Sean!!!!

I am ready to test whenever needed...

Great! I just got home.
I should have said "later tonight" my bad. Looking into this right now.

@born2net ok! Nothing like working from your own machine. Tests are passing fine. (Better to be safe).
I tested this on a project, before fix, same issue. After fix, all works and AOT completes.
You can go ahead and test in your project with the instructions I posted earlier or I can publish you a temporary build to test and use as it might take a bit (days to weeks?) for a contributor to accept my PR and version it.

great, so I can test now?
pushed  to npm?

Closed PR for now. Needs work. I was troubleshooting further before giving you a build, it works with ngc (in one project I use rollup and ngc, this is the same bundler store dev tools uses to create the build).
But with angular-cli (in another project), it doesn't work. I was testing this before giving you the build, by running the ng serve --aot command on that second project.
After troubleshooting further, I'm suspecting the issue for this is in this line as you can see it is the main difference between instrumentStore() and the instrumentOnlyWithExtension method.
This one uses useValue, I've run into that in the past and using a factory (as you can see in all the other providers), fixes it with AOT when exporting that factory outside the class. But, as I was attempting to do this, I run into the issue that this provided value depends on options when instrumenting the store InstrumentStore(options). [
This usually is not a problem:
function myFactory(options) {
  return function() {
    return options;
  }
}

but that requires useFactory: myFactory(options) in the same line instead of useValue, which is also a method call that can't be statically analyzed/resolved, causing the same issue.
If anyone has any ideas, or leads, that would be awesome. Off to bed now :dizzy_face:

A potential fix (but would be a breaking change) would be for the user to pass a factory into instrumentStore instead of a plain object.
import {StoreDevtoolsModule} from '@ngrx/store-devtools';

export function createInstrumentOptions() {
    return {
      maxAge: 5,
      monitor: monitorReducer
    }
}
@NgModule({
  imports: [
    StoreModule.provideStore(rootReducer),
    // Note that you must instrument after importing StoreModule
    StoreDevtoolsModule.instrumentStore(createInstrumentOptions)
  ]
})
export class AppModule { }

+1

or maybe create a new function if you don't want a  breaking change.
something like:  StoreDevtoolsModuleWithFactory

could also modify the existing function to accept either a function OR the plain object since that still works with JIT. Ill fork and see how it looks

@juanlizarazo you could use DI to pass the options into the fatory

A workaround for now is to use the STORE_DEVTOOLS_CONFIG token to override the options
import { STORE_DEVTOOLS_CONFIG } from '@ngrx/store-devtools/src/config';

export function noMonitor() {
  return null;
}

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    StoreModule.provideStore(rootReducer),
    StoreDevtoolsModule.instrumentOnlyWithExtension(),
  ],
  providers: [
    {
      provide: STORE_DEVTOOLS_CONFIG, useValue: {
        maxAge: 20,
        monitor: noMonitor
      }
    }
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

@brandonroberts that works GREAT!!!!
we can use this now!!!!

Reposting
import { STORE_DEVTOOLS_CONFIG } from '@ngrx/store-devtools/src/config';

export function noMonitor() {
  return null;
}

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule,
    StoreModule.provideStore(rootReducer),
    StoreDevtoolsModule.instrumentOnlyWithExtension()
  ],
  providers: [
    {
      provide: STORE_DEVTOOLS_CONFIG, useValue: {
        maxAge: 20,
        monitor: noMonitor
      }
    }
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

if there is a solution ill close my PR

Here is a link to the closed PR if interested in my thought. https://github.com/ngrx/store-devtools/pull/50

@deebloo I think a solution is needed for those who don't want to use the plugin, but it needs to be backwards compatible with using an object/function similar to what @ngrx/store does.

yes that works, we can close the PR!!!!
TX Guys!

if you want me to keep the bug open let me know

You can close it. Those who search will still be able to reference it

ok

I will open a bug to add to docs...

Sweet!

you could use DI to pass the options into the factory
@deebloo I tried, similar to what you were doing in your PR but most tests were breaking as they expect the exception to be thrown even before the provider object is returned.

Definitively adding a new method would be best or introducing a breaking change, as you guys suggest. I was working towards a patch to get it to work without api breaking changes, new features through exposed "public" methods and keeping the existing test contracts.

I will open a bug to add to docs...
@born2net Even better! you can submit a PR updating the docs.

Wondering why this issue was closed? It doesn't provide a solution when someone wants to use store-log-monitor. This only works with the chrome extension, right? Although the suggested solution works like a charm (thanks @brandonroberts!), it's probably not a solution if you want to debug things cross-browser. And I must say, I like the Angular 2 implementation of the monitor more then the chrome extension, but that might just be me :).

I can re-open if needed, let me know guys...

I'll keep it open until a solution for both options is supported with the latest iteration of AOT


fix update group method

The method did not work as built because the groupUpdate mutation uses that new format for taking that identifier input.
@eochoa260 can you fix the test fixtures in this branch?

The method did not work as built because the groupUpdate mutation uses that new format for taking that identifier input.
@eochoa260 can you fix the test fixtures in this branch?

Ah yeah, I forgot to update it to use IdentifierInput.  And definitely, I'll update the fixtures after my meetings this morning.

Outstanding things we need to manually test:

can we remove graphql.String from IdentifierInput ?
Should GroupInput.Members be nullable?
Should GroupInput.Teams be nullable?

Codecov Report

Merging #48 (2cfea0b) into main (79abd7b) will increase coverage by 0.00%.
The diff coverage is 73.68%.

@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   52.46%   52.46%
=======================================
  Files          18       18
  Lines        1805     1803    -2
=======================================
- Hits          947      946    -1
+ Misses        754      751    -3
- Partials      104      106    +2

Impacted Files
Coverage Δ

common.go
72.72% <50.00%> (+6.06%)
:arrow_up:

group.go
75.58% <100.00%> (-1.84%)
:arrow_down:

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 79abd7b...2cfea0b. Read the comment docs.


Add a check that the code is formatted

This will prevent merge conflicts in future PRs.

Oops, the current code couldn't pass the check:
https://github.com/open-spaced-repetition/fsrs-optimizer-burn/actions/runs/5921927221/job/16055163357


Course page

Create course page with description and list of sections below.
Design deppends on #28 and #29.

[ ] Web
[ ] Mobile
[ ] BLoC (?)

I will implement this, what do you think about it @tenhobi ?

@Kenny11CZ yep, do it. In the database, there is already courses section, so use it for the data storage. Sections should be in it's collection. And each section should have collections Materials and Exercises.
Btw. for now, don't care about the percentage indicator.


refactor: rename CompactString to CompactStr

Preparatory step for #2620.
This PR purely changes names of types and methods:

CompactString -> CompactStr
Atom::to_compact_string -> to_compact_str
Atom::into_compact_string -> into_compact_str

Have split this into a separate PR as the diff is large, but it does absolutely nothing but renaming (I've checked the whole diff twice, so feel free not to check it again!). This should make it easier to see the content of the substantive change in #2620.

#2619  👈
main

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

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Mar 5, 11:24 PM EST: @Boshen started a stack merge that includes this pull request via Graphite.


[BUG] infinite heap allocation, if model interface not an IReactiveObject, and [Bind, WhenPropertyChanged] used

Describe the bug
this issue occurs, if you used two-way binding on an interface that not inherit from IReactiveObject
everything will work fine until you listen to these changes with any listener eg, WhenPropertyChanged
you will get heap allocation issue due to infinite loop notifications,
so at this stage, you must make your Model interface inherit from IReactiveObject
like
this.Bind(ViewModel, vm => vm.DatabaseServices.Name, v => v.Username.Text)
                    .DisposeWith(d);

this.ViewModel.WhenPropertyChanged(vm => vm.DatabaseServices.Name, false)
    .Subscribe(_ =>
    {
        // ➜ this will called infinite times
    }).DisposeWith(d);

Steps To Reproduce

Use This Repository
Try to run the app, and it will hang due to an infinite notification loop at
To make it work

Environment

OS:       Windows 10, Version	10.0.19042 Build 19042
Version   13.3.2
Device:   Laptop

Additional context
I just do not know if this is a bug, or it is just an intention behavior, or it is current limitations
but I will report it anyway, may be some one face the same issue

WhenPropertyChanged is not a reactiveui extension method. WhenAnyValue is


Fix for TypeError: can't convert Hash into Integer when calling Product.count with latest activeresource

The Countable mixin doesn't work with activeresource@master because of this pull request that was merged in January: rails/activeresource#96. This PR adds a test to expose this issue as well as a fix.
In short, the problem is that the call to get(:count) now no longer removes the root from the response properly, so the return value is now {"count" => 16} instead of 16 (assuming there are 16 of the resource). To fix it, I added some code to check if the value returned from get(:count) is a Hash instead of a number, and remove the root manually. I've also posted a comment on the offending PR about the new problem it caused here: https://github.com/rails/activeresource/pull/96#issuecomment-234991786

Can you squash? then we can ship

squashed

Hello, i've got the same error with a fresh install of rails 5 and shopify api, do i have to do some extra config ?

looks like we haven't shipped the gem yet. For the time being use a github dependency


Refactor notification-client usage to interface

Includes factory pattern to initialize and obtain latest instance.
Includes handling change for configuration allowing client to be
utilized and customized from any service.
Signed-off-by: Trevor Conn<EMAIL_ADDRESS>

I think that interfaces are great and that they should be used when needed. But I don't think this is the case. We have only one client type (http) and this will not change anytime soon. We are making the code more complex without any immediate gain.
I should propose to remove the interface and that the notification_client package only exports a function like:
 func SendNotification(host string, port int, n Notification) error {

This will also remove the need in the package using this to have a notifications_client instance to be able to call the function (or having a global instance in the package)

Ok, I understand.
What it still does not make sense to me is to have a global configuration in the package and a global instance ( support/notifications-client/client.go:87).
Why not having a function like:
func NewNotificationsHttpClient(host string, port int) NotificationClient

@feclare Well, in effect what we have right now in core-metadata is a global instance -- not even an interface but an instance.
core/metadata/init.go: line 34
var notificationsClient = notifications.NotificationsClient{}
The host and port are then set on lines 73 and 74 of that same file, equivalent to passing them when initializing the type as you show above. My refactoring effects this same thing, initializing the settings in a notifications config that is encapsulated within the notification_client package (allowing for on the fly updates later BTW) and providing a public way to access the current instance of the NotificationClient throughout the application -- whether it be a mock or an actual implementation.
I separated the config into its own type because I considered the question of whether or not some other service may want to utilize the Notification service. This could be an unnecessary consideration but stems from the fact that the name "Notification Service" is very general. What kind of notification? From whom to where? Any service could conceivably need to send a "notification" of some kind.
It sounds to me like your main concern is the new signature is too verbose, going from this:
notificationsClient.SendNotification(notification)
to this:
notifications.GetNotificationsClient().SendNotification(notification)
I'll concede that, and if you have suggestions for how to make the signature more terse without sacrificing readability, let me know. You will see this pattern all over the place in the holding area I linked to above.

@feclare - thanks for your good review and continued input on this.  Let's discuss this in an upcoming working group meeting as a potential global issue that we need to address (I am in the process of redoing Notification in Go right now and will have to address there too).  Let's develop the issue and get that into the system separate from this PR.


Fix status and restarts in sys v script

Status detection is broken in the sysv init script if another Java process is running on the same instance, switch to using a more detailed status of proc check.

Closed by #27


i use define in custom vite plugin, but it not work in runtime project ~

Describe the bug
i use `define` in custom vite plugin, and `JSON.stringify`. but it can't find `process` in runtime project.

vite version is: 2.4.0

docs: https://vitejs.dev/config/#define

Reproduction
in vite-plugin-custom
function vitePluginCustom() {
  return {
    define: {
      test: JSON.stringify({ abc: 123 })
    }
  }
}

module.exports = vitePluginCustom

in project main.js
console.log(process.env.test);

System Info
Uncaught ReferenceError: process is not defined

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

maybe need set define into config, and use process.env as key
function vitePluginCustom() {
  return {
    config: {
      define: {
        'process.env': {
          abc: 123
        }
      }
    }
  }
}

module.exports = vitePluginCustom


Testing a windows application in Ruby with a new window opening.

So i am trying to automate a series of smoke tests for an ERP solution using WinAppDriver. We have tested it with selenium and doing so means that we can create new sessions for the windows that load as it has nested windows for the login and a new window that opens at the end of the login process but as the names used are reused multiple times.
Using Appium we can find things by their automation id's which is so much better but when the login process finishes it can't register the new window and then exits. We are trying to create a new desktop session for the new window but it keeps giving us the following run time error, with  the code just after.

 module Helper
  def new_window
    @opts =
     {
         caps: {
          platformName: "WINDOWS",
        platform: "WINDOWS",
        deviceName: "mydevice",
        app: "Root"
      },
         appium_lib:
          {
              wait_timeout: 30,
              wait_interval: 1
          }
      }

        $DesktopSession = Appium::Driver.new(:remote, :url => "http://<IP_ADDRESS>:4723", :desired_capabilities => @opts)
        # $DesktopSession.find_elements(:name, 'IFS Applications')[0]
    end

end

Obviously we are using Ruby and the ruby docs have not been updated to the appium format. If anyone has any ideas could you please drop me a line as this is a blocker for us at the moment.

Hi @ChrisYarland-Price,
Can you provide any additional logs/information? There should be an Appium window with the server side logs present--if you could share that, it would be helpful.
Thanks


Visualizer: Shareable grammars as URL

It's nice that the visualizer currently remembers the lasted grammar I worked on and the example I used with it (in local storage).
I would love to see a generated URL in the style of:
http://esprima.org/demo/parse.html?code=var my %3D Grammar%3B
(I would rather like to see # instead of ? but that's the general idea)
to share my grammar (and examples) with others and remember multiple grammars in my bookmarks. It's also a neat thing when reporting bugs for Ohm.

+1

Done. Give it a try and let me know what you think!

Wow! First report: It completely crashed my (Chrome) browser! All the windows, all tabs (100+).

On Feb 11, 2016, at 6:20 AM, Patrick Dubroy<EMAIL_ADDRESS>wrote:
Done. Give it a try and let me know what you think!
—
Reply to this email directly or view it on GitHub https://github.com/cdglabs/ohm/issues/58#issuecomment-182884108.

Oh, btw. I always like a "default grammar" when you came to the visualizer instead of an empty canvas.
Would be nice to get some example when I go straight to: http://cdglabs.org/ohm/visualizer/

Well, and the encoding for the URL is somewhat verbose. One character - in example or grammar - results in ~4 characters in the URL. Not that pleasant for (real) grammars like ES5, etc.
Maybe that is what crashed my browser: I had a long grammar (SL) in LocalStorage.

Uh...very weird. I did test with the ES5 grammar and a very large input string, no problems.
And it should be totally ignoring your grammar in localStorage...I decided not to try to load them, because it would just be some code that would be temporary that we'd want to delete later...and I figured it wasn't worth it.

Re-opening as the previous fix didn't work properly in Firefox and Safari.
Given the length of some "real" grammars (e.g., the ES6 grammar is >23k chars), we will probably need to implement this with a real backend.

Re-opening as the previous fix didn't work properly in Firefox and Safari.
Given the length of some "real" grammars (e.g., the ES6 grammar is >23k chars), we will probably need to implement this with a real backend.


doc: Fix inconsistent json description

Noticed this during SDK testing. All other extension layers mention Khronos in the description.

CI Vulkan-ExtensionLayer build queued with queue ID 24884.

CI Vulkan-ExtensionLayer build # 672 running.

CI Vulkan-ExtensionLayer build # 672 passed.


Reduce Instance Profile Permissions for AWS Shoot Clusters

Story

As user/provider I want to grant the worker nodes as few permissions as possible, so that the attack surface is as minimal as possible (against active hacking, but also accidental exposure).

Motivation
Security.
Acceptance Criteria

[ ] Investigate whether we can be more specific with ec2:Describe* and reduce this (potentially only to cluster-owned resources with the tags)
[ ] Investigate whether we can drop ecr:* (after a deprecation period, because it is an incompatible change and in violation of https://kubernetes.io/docs/concepts/containers/images "Kubernetes has native support for [ECR]"; Gardener doesn't need it anymore, but the customer might store and access images in/from ECR without having a proper ImagePullSecret)

Implementation Proposal
Change the instance profile, but consider the plans for out-of-tree cloud providers and whether or not the kubelet will eventually not need any relevant access anymore in the (near?) future, which might make it not worthwhile investigating whether ec2:Describe* can be reduced to a more specific policy.
Release Notes
- Your worker nodes for AWS clusters have now minimal permissions allowing access to only this cluster.

Definition of Done

[ ] Knowledge is distributed: Have you spread your knowledge in pair programming/code review?
[ ] Unit tests are provided: Have you written automated unit tests?
[ ] Integration tests are provided: Have you written automated integration tests?
[ ] Minimum API exposure: If you have added/changed public API, was it really necessary/is it minimal?
[ ] Operations guide: Have you updated the operations guide about ops-relevant changes?
[ ] User documentation: Have you updated the READMEs/docs/how-tos about user-relevant changes?

@marwinski Ping... any update here or new insights via Kinvolk?

Update: we have done some investigations and here are the results in a nutshell:

the credentials provided by the metadata service correspond to the role in the instance profile
all other information does not appear to be critical as it does not reveal information on the account or other instances (ec2, volumes, ...)
the metadata service appears to be read-only - no modifications appear to be possible at least on AWS
the kubelet requires access to the metadata service

As for 2. above the only real problematic statement appears to be "ec2:Describe*" as this reveals a lot of information about the whole account. The cloud provider code for AWS appears only to use two of those (and they might not even be used from the kubelet).
I am not sure the ecr: roles are needed anymore.

Thanks, I can work with that and have sharpened the user story, used the default template and added the release notes and DoD.
However, I am sceptical whether we should do that, simply because on both points the out-of-tree cloud providers might help us in a much safer way:

EC2: Out-of-tree cloud providers will make permissions for the kubelet most likely obsolete and we might even drop them for good, so why investigate at all? Reducing the permissions is difficult (which is why we haven't done it in the past), because it requires code scanning and/or experimentation (which may accidentally miss and therefore remove permissions that are required under certain circumstances).
ECR: While the Gardener doesn't need ECR anymore, the user may still store and access private images from ECR, so we can't reduce these permissions without risking breaking running clusters. Also, removing this, is actually in violation of https://kubernetes.io/docs/concepts/containers/images that states:

"Kubernetes has native support for [ECR]"

@marwinski Next time please be as specific as possible, otherwise the ticket will remain in limbo until it gets more clearly spec'ed out. Thanks! In regards to ECR and out-of-tree cloud providers could you please a look and advice. I have the feeling that we shouldn't waste too much time on the first (ECR) if out-of-tree cloud providers are full reality and may not do the latter (ECR), for which I don't know what the plans are when out-of-tree cloud providers are done.

Updated implementation proposal from issue #275.


Debug prints regorganization

Problem statement
I see lot of places where the code looks like this:
if Debug {
    log.Println("absolute path", fa)
}

Event though it is trivial and debug only, it contributes into the code size overall reducing readability.
Proposition.
I would consider moving it out into just one function that supports some kind of log levels or I would just use an existing logging library.
Thoughts?

even when it uses a logging library, there would still need to be if guards or lazy evaluation of arguments to get any real benefit from it.
The one immediate benefit I see would be colors for levels

How about using the following constructs:
func logDebug(...) bool {
 log.Printf(....)
}

_ := Debug && logDebug("message")

Then we could move the logDebug() func to any logger available out there. For instance rs/zerolog seems an efficient, yet simple, one.
For the json.MarshalIndent() stuff, another wrapper would be appropriate, e.g:
func logDebugAsJson(v) bool {
 bbb, _ := json.MarshalIndent(v)
 log.Printf(string(b))
return true
}

This would make code more readable and test coverage analysis more accurate.
Another useful point is to enable debug for a given module. Currently, all go-openapi packages are guided by the same env variable SWAGGER_DEBUG.
Debugging text would be clearer if we could support things like export SWAGGER_DEBUG=go-swagger:validate:runtime.


Merging https://github.com/chef/chef/pull/2707

Merging https://github.com/chef/chef/pull/2707

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@habermann24

Please sign the CLA here.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@haberbyte

Please sign the CLA here.


Fix handling of index holes in PyDiGraph pickling

This commit fixes an issue with pickling (and by extension deepcopy)
PyDiGraph or PyDAG objects that have holes in their node id lists.
Previously the node ids would not be preserved across pickling leading
to a compacted list instead of the original node ids. For example, if
you had a PyDiGraph with node ids [0, 1, 3] after pickling/deepcopy the
node ids would be [0, 1, 2] but otherwise identical. This commit fixes
this issue by adding a check for holes to __setstate__ method and
incrementing the node id to reproduce a 1:1 mapping with the original
node ids prior to pickling.

I'm marking this as on hold because this depends on #115 before we can safely remove it. Currently this bug is actually being used by users to workaround #27, so the reordering is a feature. Once there is a fix in place for #27 users will no longer need to run deepcopy()  or to pickle objects to compact node indices for doing an isomorphism check. But we don't want to accidentally merge this until that is fixed

Coverage increased (+0.06%) to 90.363% when pulling 205985676b5b5967d6736be593e9948a2a55e480 on mtreinish:fix-deepcopy-index into b86f889b67765b5419676b1a71bb4c4605e73f74 on Qiskit:master.


Update astral-sh uv to 0.2.18

Description of changes
https://github.com/astral-sh/uv/releases/tag/0.2.18

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hi, thanks for the update but we first have to merge https://github.com/NixOS/nixpkgs/pull/322953 (updating ruff to 0.5).
However, this is breaking many downstram changes because of CLI changes. We'll probably have to wait a bit.

conflicts with #323861


Fix readme title

Is there a reason you used a PR here, instead of simply pushing the commit?

No good reason other than the habit of not pushing directly to the master branch.

I am assuming that you would suggest that I make the changes with GitHub GUI and commit/push the changes directly to master, is that correct? @randomir

Yes, I would suggest trivial changes* like this are pushed directly to master. You don't have to use GitHub/GUI at all.
I would say PRs are useful for:

aggregating multiple commits in a single referenceable unit of work (bug fix, feature)
documenting units of work, i.e. providing rationale or context, in relation to some opened issues
providing forum for discussion and review

PRs are not useful and clutter the git history with zero information "merge commits" when they contain simple/uninteresting commits (commits that don't need to be reviewed, justified of referenced).

*) trivial changes: tweaks to readme/docs/comments/code formatting which do not require review and/or discussion forum (like pull request page).


Make routing optional

Routing with this package can be quite tricky. It seems that with Laravel 5.7 it doesn't work at all - at least I didn't manage to get it to work.
This PR doesn't fix the issues, but introduces an config option to disable the routing functionality of this package (you have to manage the routing yourself then).

@develpr It would be great if you get some spare time to look into this PR. Contains new improvements and support to other functionalities.
Great work @wertmenschen
Thanks :)

Amazing! Thank you so much for taking the time to work on this.


Fixed streched logo

Fixes #120
After changes:
https://github.com/Anushkabh/krishiconnect/assets/99901964/bf4d3d1d-8cd3-4b1d-929c-bf064a5736be

@Anushkabh Can you look into this PR


Dead links

The docs have a few dead links (found through https://github.com/raviqqe/muffet):

http://docs.honeytrap.io/images/favicon.png (favicon, linked everywhere)
https://docs.honeytrap.io/docs/concepts/overview/what-is-honeytrap/ (linked from https://docs.honeytrap.io/)
https://docs.honeytrap.io/docs/setup/docker-compose/landing/ and https://docs.honeytrap.io/docs/setup/go/install-agent/ (linked from https://docs.honeytrap.io/docs/concepts/framework/architecture/)
https://docs.honeytrap.io/docs/setup/sensor/config-firewall.md (linked from https://docs.honeytrap.io/docs/setup/sensor/setup-prerequisites/)

Finally, all pages link to the Kubernetes license (https://git.k8s.io/website/LICENSE), which probably should be replaced with a direct link to the CC website.

Hi CapacitorSet,
Thanks for notifying us. Dead links will be fixed in coming pull request.

Fixed, thanks!


compress ttl dumps

Compress ttl dumps at rest, resulting in about 90% reduction of the file size (~50mb -> 5mb).

cf the updated README:
compression is configurable per task. default is false:
{
  "http://redpencil.data.gift/id/jobs/concept/JobOperation/deltas/deltaDumpFileCreation/leidinggevenden" : {
    "dcatDataSetSubject": "http://data.lblod.info/datasets/delta-producer/dumps/LeidinggevendenCacheGraphDump",
    "targetGraph": "http://redpencil.data.gift/id/deltas/producer/loket-leidinggevenden-producer",
    "fileBaseName": "dump-leidinggevenden",
    "targetDcatGraph": "optional graph where the information of the data set should reside",
    "targetFilesGraph": "optional graph where the meta data of the ttl should reside"
    "targetFilesGraph": "optional graph where the meta data of the ttl should reside",
    "compression": "optional, default false. If true, dumps are compressed as *.ttl.gz"
  }
}


🐛 Bug Report: Database Password visible in DevTools

📜 Description
When using the DevTools plugin, on the Config tab we can see the database password in clear text when we use the following in our app-config.yaml:
connection:
       host: <IP_ADDRESS>
       user: postgres
       password: postgres
       port: 5432

👍 Expected behavior
When using the Config tab in the DevTools plugin the database password should be replaced by the text <secret> like other sensitive configuration data
Note: when using a connection string like postgres://postgres:postgres@<IP_ADDRESS>:5432 this is not visible and masked with <secret>
👎 Actual Behavior with Screenshots
When using the DevTools plugin, on the Config tab we can see the database password in clear text when we use the following in our app-config.yaml:
connection:
       host: <IP_ADDRESS>
       user: postgres
       password: postgres
       port: 5432

Which results in this on the Config tab of the DevTools plugin:

👟 Reproduction steps

Install the DevTools plugin: https://github.com/backstage/backstage/tree/master/plugins/devtools
Update the backend.database.connection section in your app-config.yaml to look like this (ideally with valid config for your environment):

connection:
       host: <IP_ADDRESS>
       user: postgres
       password: postgres
       port: 5432

Start up Backstage: yarn dev
Navigate to the Config tab in the DevTools plugin: http://localhost:3000/devtools/config
Scroll down to the backend.database.connection section

Notice: You can see the password in clear text
📃 Provide the context for the Bug.
From a security perspective we should not be able to see this information in clear text as they could be exploited
🖥 Your Environment
Not really applicable, this isn't an environment specific bug.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Here is the code where we mark it as secret but doesn't seem to apply to the object usage:
https://github.com/backstage/backstage/blob/85b3e4fcc17ce7950fcdf9ef8321b48982f11b00/packages/backend-common/config.d.ts#L71-L79

woops - think that this is a bit of a footgun that we should make sure that if an object is set as secret that visibility should descend to the children which would be different to how the frontend visibility works, but I think that's ok.

Sorry, for highjacking this issue:
The same applies to the providers.microsoftGraphOrg.x.clientSecret. clientSecret is also marked as secret for visibility.
Fun fact: secret visibility works for auth.providers and integrations.github.

Thanks for reporting @jgrumboe can you log that as an issue of its own along with links to the code you mentioned, please?

I created https://github.com/backstage/backstage/issues/18006 as a ticket to fix this issue


[BUG] - Search API returns socket exception

Describe the bug
We run the Azure cognitive search api to create indexrs and get the below exception:
-> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
2021-05-31T00:20:00.7280530Z  ---> System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
2021-05-31T00:20:00.7281464Z  ---> System.Net.Sockets.SocketException (995): The I/O operation has been aborted because of either a thread exit or an application request.
at Azure.Search.Documents.Indexes.SearchIndexerClient.CreateIndexerAsync(SearchIndexer indexer, CancellationToken cancellationToken)

Expected behavior
What is the expected behavior? An indexer created
Actual behavior (include Exception or Stack Trace)
What is the actual behavior? exception thrown
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

call the indexer creation

Environment:

Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
IDE and version : [e.g. Visual Studio 16.3]
nuget v11.1.1
Azure.search.documents

full stack trace:
2021-05-31T00:20:00.7278125Z Unhandled exception. System.AggregateException: Retry failed after 4 tries. (The operation was canceled.) (The operation was canceled.) (The operation was canceled.) (The operation was canceled.)
2021-05-31T00:20:00.7279288Z  ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
2021-05-31T00:20:00.7280530Z  ---> System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
2021-05-31T00:20:00.7281464Z  ---> System.Net.Sockets.SocketException (995): The I/O operation has been aborted because of either a thread exit or an application request.
2021-05-31T00:20:00.7282059Z    --- End of inner exception stack trace ---
2021-05-31T00:20:00.7282582Z    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
2021-05-31T00:20:00.7283452Z    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token)
2021-05-31T00:20:00.7284044Z    at System.Net.Security.SslStream.<FillBufferAsync>g__InternalFillBufferAsync|215_0[TReadAdapter](TReadAdapter adap, ValueTask`1 task, Int32 min, Int32 initial)
2021-05-31T00:20:00.7285284Z    at System.Net.Security.SslStream.ReadAsyncInternal[TReadAdapter](TReadAdapter adapter, Memory`1 buffer)
2021-05-31T00:20:00.7286108Z    at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
2021-05-31T00:20:00.7286584Z    --- End of inner exception stack trace ---
2021-05-31T00:20:00.7287098Z    at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
2021-05-31T00:20:00.7288046Z    at System.Net.Http.HttpConnectionPool.SendWithNtConnectionAuthAsync(HttpConnection connection, HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
2021-05-31T00:20:00.7290288Z    at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
2021-05-31T00:20:00.7290893Z    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
2021-05-31T00:20:00.7291470Z    at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
2021-05-31T00:20:00.7292060Z    at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async)
2021-05-31T00:20:00.7292542Z    at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message)
2021-05-31T00:20:00.7293074Z    at Azure.Core.Pipeline.RequestActivityPolicy.ProcessNextAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean isAsync)
2021-05-31T00:20:00.7293673Z    at Azure.Core.Pipeline.RequestActivityPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean isAsync)
2021-05-31T00:20:00.7294261Z    at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
2021-05-31T00:20:00.7294828Z    at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7295385Z    at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
2021-05-31T00:20:00.7295924Z    at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7296457Z    at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
2021-05-31T00:20:00.7296912Z    --- End of inner exception stack trace ---
2021-05-31T00:20:00.7297336Z    at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
2021-05-31T00:20:00.7298061Z    at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7298617Z    at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7299175Z    at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7299725Z    at Azure.Core.Pipeline.HttpPipelineSynchronousPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
2021-05-31T00:20:00.7300249Z    at Azure.Search.Documents.IndexersRestClient.CreateAsync(SearchIndexer indexer, CancellationToken cancellationToken)
2021-05-31T00:20:00.7300846Z    at Azure.Search.Documents.Indexes.SearchIndexerClient.CreateIndexerAsync(SearchIndexer indexer, CancellationToken cancellationToken)

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@amitkub - can you provide more details on this -

How often are you hitting this issue?
Does the operation succeed on retry?

Also, please look at the discussion and workaround discussed in #9212. See if modifying the Transport and Retry properties on SearchClientOptions resolves the issue.

Retry didn't work
I will try to change the transport in the next few days and confirm if this works or not.

@amitkub, did you get a chance to try the workarounds. Specifically, modifying both the Transport and Retry properties on SearchClientOptions?


Problems with DoubleDot from classicaldotsystem

Hello,
I tried simulating a DoubleDot analog to the classical_triple_dot.ipynb example notebook.
%matplotlib inline
import matplotlib.pyplot as plt

import numpy as np
from qtt.simulation.classicaldotsystem import ClassicalDotSystem, DoubleDot

DotSystem = DoubleDot()

# addition energy
DotSystem.Eadd = np.array([54.0, 52.8])

# chemical potential at zero gate voltage
DotSystem.mu0 = np.array([120.0, 100.0])

# coulomb repulsion (!order is important: (1,2), (1,3), (2,3)) (lexicographic ordering)
DotSystem.alpha = np.array([[1.0, 0.25], [0.25, 1.0]])
# virtual gate matrix, mapping gates to chemical potentials
DotSystem.W = np.array([6.0])

#Define gate plane
P1 = 25.987333
P2 = 83.0536667
ref_value = [P1, P2]
gatevalues = np.array(ref_value)
charge_state = DotSystem.calculate_ground_state(gatevalues)

But I get the following error:

I think the reason is that by creating an instance of  DoubleDot  the method makebasis is called twice with different parameters. The first call is in the init method of  ClassicalDotSystem with the parmeters self.makebasis(ndots=ndots, maxelectrons=maxelectrons). And the second call is in the  init method of DoubleDot with the parmeters self.makebasis(ndots=2). The first call creates a numpy array with shape (16,2) from which the variable _coulomb_energy inherits it shape but the second call overrides the variable basis with a array of shape (9,2). Therefore the shapes between the parameters basis and _coulomb_energy don´t match anymore, which results in the error.
As a possible solution I added the parameter maxelectrons to the class DoubleDot analog to the class TripleDot.
Code before:
class DoubleDot(ClassicalDotSystem):
    """ Classical simulation of double dot """

    def __init__(self, name='doubledot', **kwargs):
        super().__init__(name=name, ndots=2, ngates=2, **kwargs)

        self.makebasis(ndots=2)

Code after:
class DoubleDot(ClassicalDotSystem):
    """ Classical simulation of double dot """

    def __init__(self, name='doubledot', maxelectrons=3, **kwargs):
        super().__init__(name=name, ndots=2, ngates=2, maxelectrons=maxelectrons, **kwargs)

        self.makebasis(ndots=2, maxelectrons=maxelectrons)

My code is now working but is it correct to call the method makebasis  twice and if yes why?
Maybe the better solution would be to remove the second call if it is unnecessary.

Hello @fabian-fuchs You are right. This call to makebasis should come from the parent class only and not (again) from the subclass. I'll create a bug report.

@fabian-fuchs a fix is merged to the dev branch.


Time correlation example : Not ready to merge

Example for one time correlation with real XPCS data. Plot the correlation functions

Why closed? Are we abandoning this example or moving it to a notebook?

Actually there is an issue with the  1 time correlation code. So this PR was not ready to merge. Again I started  to look at that issue once I finish with it we will be able to put an example or move it to a notebook.


Docker Code

Acceptance Criteria

Docker Environment and File Set up for project

Completed and created a yaml file for docker compose.


Hook and observer ordering for on_remove/on_replace should be inverted

Bevy version
0.15.0-rc.3 (exists before as well)
What you did
When adding a component, the order of hooks and observers are:

on_add hook
on_add observers
on_insert hook
on_insert observers

When removing a component, the order of hooks and observers are:

on_replace hook
on_replace observers
on_remove hook
on_remove observers

What went wrong
The remove ordering matches the add ordering, while it would be more natural for it to be inverted – running observers before hooks, that is.
Additional information
Note that this bug is to provoke discussion. The current behaviour may be considered correct as well. So this bug should be used to discuss the matter and make a decision so that the decision is then documented for posterity.

Flecs also runs on_remove hooks after OnRemove observers

@maniwani and I agree that the current behavior is a bug.


GenericList.getItems() does not return any list item having null value.

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: <IP_ADDRESS>
[ ] ACS AEM Commons Version: 3.17.0
[ ] Reproducible on Latest? yes (based on code)

Expected Behavior
GenericList.getItems() should return any item having null value similar to .../_jcr_content.list.json.
This will make it consistent as well as useful, where user may want to add an item having null value.
e.g., Dropdown Option as "Select" or "None". This dropdown option can be used to remove the previously selected value, if required.
Actual Behavior
GenericList.getItems() does not return any item having null value.
Whereas .../_jcr_content.list.json on the list page returns all items including item having null value.
Steps to Reproduce

Create a Generic List

Add multiple items, including one or more item having null value but with title (e.g., "None")

Access the list page path suffixed with /_jcr_content.list.json. This will provide all items having non-null title.

Write Java code to use Generic List API. e..g,
PageManager pageManager = resourceResolver.adaptTo(PageManager.class);
Page listPage = pageManager.getPage("/etc/acs-commons/lists/targets"); // e.g., /etc/acs-commons/lists/targets is our list
GenericList list = listPage.adaptTo(GenericList.class);
///Check output of list.getItems();

Links
NA

Fixed in v4.5.2

Hi David, i'm still having the same issue with latest acs commons package- 4.11.2. I see a blank screen in UI and the below error in logs: org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=acs-commons/components/utilities/genericlist, superType=null,

Hi David, i'm still having the same issue with latest acs commons package- 4.11.2. I see a blank screen in UI and the below error in logs: org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=acs-commons/components/utilities/genericlist, superType=null,

Was this expected to be fixed in 4.11.2?

Was this expected to be fixed in 4.11.2?

I see it got fixed based of the release notes in 4.11.2
https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md

I see it got fixed based of the release notes in 4.11.2
https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md

The shaded guava or the versioned clientlibs ? Those are the only 2 items
in 4.11.2, no?
On Wed, Jan 13, 2021 at 9:10 PM prasanna9936<EMAIL_ADDRESS>wrote:

I see it got fixed based of the release notes in 4.11.2
https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2248#issuecomment-759877638,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALCOXFTG4NCTYSJP27LVXDSZZHAHANCNFSM4L3O2QJQ
.

The shaded guava or the versioned clientlibs ? Those are the only 2 items
in 4.11.2, no?
On Wed, Jan 13, 2021 at 9:10 PM prasanna9936<EMAIL_ADDRESS>wrote:

I see it got fixed based of the release notes in 4.11.2
https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2248#issuecomment-759877638,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALCOXFTG4NCTYSJP27LVXDSZZHAHANCNFSM4L3O2QJQ
.

There is a full list in this link, https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md and search for #2248.

There is a full list in this link, https://raw.githubusercontent.com/Adobe-Consulting-Services/acs-aem-commons/master/CHANGELOG.md and search for #2248.

Oh - that was (allegedly) fixed back in 4.5.2 (last April).. maybe something regressed that fix since then ..?

Oh - that was (allegedly) fixed back in 4.5.2 (last April).. maybe something regressed that fix since then ..?

Yeah looks like it. Because that link has more than 100+ defects which can't be addressed in one release .

Yeah looks like it. Because that link has more than 100+ defects which can't be addressed in one release .

Correct. The change log is a running list of changer per release. Each release has a section in the chnagelog, newest at the top. Top of the chnagelog has a link to a web site that explains the format.
But I guess the important thing is the bug still exists and we need to be fixed :)

Correct. The change log is a running list of changer per release. Each release has a section in the chnagelog, newest at the top. Top of the chnagelog has a link to a web site that explains the format.
But I guess the important thing is the bug still exists and we need to be fixed :)

Yeah the bug exists, i'm more than happy to try any other ideas to isolate the problem to ACS. Let me know if you need some help in reproducing the issue.

Yeah the bug exists, i'm more than happy to try any other ideas to isolate the problem to ACS. Let me know if you need some help in reproducing the issue.

This is with 5.3.2 installed:


Table usage POST Entity Already Exists

You can reproduce this by running test_ometa_table_api

my bad, messing up the delete


Not enough DJ Khaled quotes

Stumbled across this project. Title says it all.

Feel free to send a pull-request with more DJ Khaled quotes 🙏


Support for Iceberg update and deletion vectors

Feature Request / Improvement
Looks like that when I run an Update or a Delete for an Iceberg table, once I generate the Delta metadata, the updates and deletes are lost.
There are already current issues that track deletion vectors, but not updates.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Closing in favor of https://github.com/apache/incubator-xtable/issues/339


[stable/prometheus-operator] prometheus-operator chart mounting invalid configuration that doesn't exist

**Describe **
Prometheus Operator alert manager mounts a config that doesn't exist.
Which chart:
Prometheus-operator chart:5.0.13
What happened:
When I provide secrets alertmanager.alertmanagerSpec.secrets to alertmanager and set this field alertmanager.alertmanagerSpec.useExistingSecret to false.
I also mounted a new secret (which is fine), the issue is that it doesn't create a default config (because I have set this field to false alertmanager.alertmanagerSpec.useExistingSecret ) but mounts its name in the configurations which eventually cause issue in alert manager pod because it tries to mount those configs that don't exist.
What you expected to happen:
I should not mount the default configuration in the config because I have set false to this parameter alertmanager.alertmanagerSpec.useExistingSecret.

its not stale

not stale

not stale

not stale

not stale


Question: Pass model name specification in factory

Hi:
I had to fork the repo and specify the module name in lib/passkit/factory.rb to prevent an uninitialized constant Pass error
I'm not sure if that is a bug or something missing from my configuration.
module Passkit
  class Factory
    class << self
      def create_pass(pass_class, generator = nil)
        pass = Passkit::Pass.create!(klass: pass_class, generator: generator)
        Passkit::Generator.new(pass).generate_and_sign
      end
    end
  end
end

@AlanMcCann this is an old issue so I'm not sure if you still need an answer but in the screenshot you have Pass.create! and in the code snipped you have Passkit::Pass.create. Were you able to resolve this issue?

I am not sure how this could happen, but adding the Passkit namespace won't hurt. I just added it and pushed to main.


helppppppp

Describe your problem here.
im using ver 0.6.3
sooo i was doing stage stuf and i wote some code for the "scripts" folder in mod folder, and this happned

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x86/x32
Did you edit anything in this build? If so, mention or summarize your changes.
i edit nothin

it was my stage!!!!!! AAAAAAAAAAAAAAAHHHHHHHHHHHHH       🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶🥶

Well
that was disappointing

tru