md-colors not getting bundled

Using aurelia-cli. Installed materialize-css and bridge as described (http://aurelia-ui-toolkits.github.io/demo-materialize/#/installation).
When I load the resulting page, there is an extra request for http://localhost/app/dist/node_modules/aurelia-materialize-bridge/dist/amd/colors/md-colors.js.
I have added an extra build step to copy index.html and bundles into a dist directory, so node_modules is not available at this url and the request gets a 404. I can see in the vendor_bundle.js that most of the other md-xyz scripts are bundled, but md-colors is not.
In fact, even:
define('aurelia-materialize-bridge/colors/colorValueConverters',["exports"], function ...

from colorValueConverters.js is included in the vendor bundle, but md-colors.js is not.
au --version: 0.19.0
"aurelia-materialize-bridge": "^0.15.0",
"materialize-css": "^0.97.7",

@kottmast
That happens when I forget to add things to global exports.. 😃
Sorry about that and thanks for mentioning, I willl add it in.
If you need it immediately you could edit the file node_modules/aurelia-materialize_bridge/dist/amd/index.js and add './colors/md-colors' to the define here and add _mdColors to the function parameters in this line - the two entries must have the same position in their arrays.
Short form:
define([ ... , './colors/md-colors', ... ], function(... ,_mdColors, ...);

Finally, copy these lines and change them to this:
  Object.keys(_mdColors).forEach(function (key) {
    if (key === "default") return;
    Object.defineProperty(exports, key, {
      enumerable: true,
      get: function () {
        return _mdColors[key];
      }
    });
  });

This is not tested but should work in principle (at least this is how AMD works). 😃


[Bug]: Search Filter

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When I have typed the name of a book into the search bar and no matching book is found, there is no feedback or result shown. This creates confusion for the user, as they don't know if the search is still processing, if there was an error, or if the book simply doesn't exist in the database.
Expected behavior
Display a pop-up card or message notifying the user that the book was not found.
Add ScreenShots
No response
On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Is there an existing issue for this?

[x]  I have searched the existing issues

Describe the bug
When I have typed the name of a book into the search bar and no matching book is found, there is no feedback or result shown. This creates confusion for the user, as they don't know if the search is still processing, if there was an error, or if the book simply doesn't exist in the database.
Expected behavior
Display a pop-up card or message notifying the user that the book was not found.
Add ScreenShots
No response
On which device are you experiencing this bug?
No response
Record

[x]  I have read the Contributing Guidelines
[x]  I'm a GSSOC'24 contributor
[x]  I have starred the repository

Hello @darshinihoney, Go for it
All the Best


Channel set() broken

Steps to reproduce
dac.channels[6].volt.set(1.5)
Expected behaviour
Setting of voltage
Actual behaviour
File "", line 1, in
dac.channels[6].volt.set(1.5)
File "c:\users\lab2\documents\python\qcodes\qcodes\instrument\parameter.py", line 482, in set_wrapper
e.args = e.args + ('setting {} to {}'.format(self, value),)
File "c:\users\lab2\documents\python\qcodes\qcodes\instrument\parameter.py", line 413, in set_wrapper
try:
File "c:\users\lab2\documents\python\qcodes\qcodes\instrument\parameter.py", line 538, in validate
if self.vals is not None:
File "c:\users\lab2\documents\python\qcodes\qcodes\instrument_drivers\Harvard\FZJ_Decadac.py", line 457, in validate
if not (self._parent._min_volt <= value <= self._parent._max_volt):
File "c:\users\lab2\documents\python\qcodes\qcodes\utils\helpers.py", line 395, in getattr
# needed to prevent infinite loops!
AttributeError: ("'DacChannel' object and its delegates have no attribute '_min_volt'", 'setting DecaDac_Slot1_Chan1_volt to 1.5')

This error occurs because you didn't set the "switch_pos"-Parameter. The switch position specifies the range of the voltage:

left: -10 V to 0 V
mid: 0 V to 10 V
right: -10 V to 10 V

The first thing I can do, is to optimize the error message so the error reason gets clearer. Additionally I can add a new parameter to the constructor so that it's mandatory to set the switch position. Alternatively I can set the switch position by default, but I don't think this would be the best way, do you?

@reneotten Please test if the problem is really solved because I don't have the hardware needed to test it myself.

Seems to work now.  Maybe set _switch_pos on init to None and add an error in the get method if one tries to get it before it is set.

Right now switch_pos has to be set after the init, would be nice if it is passable as keyword arg

Also maybe add a warning in the reset method if the default is set.


Unknown Source Names - nvim_lsp

Hi there, I am struggling to install the plugin and have tried a few differnet ways. Each time if I run :CmpStatus the nvim_lsp plugin is listed as an unknown source.
local on_windows = vim.loop.os_uname().version:match 'Windows'

local function join_paths(...)
  local path_sep = on_windows and '\\' or '/'
  local result = table.concat({ ... }, path_sep)
  return result
end

vim.cmd [[set runtimepath=$VIMRUNTIME]]

local temp_dir = vim.loop.os_getenv 'TEMP' or '/tmp'

vim.cmd('set packpath=' .. join_paths(temp_dir, 'nvim', 'site'))

local package_root = join_paths(temp_dir, 'nvim', 'site', 'pack')
local install_path = join_paths(package_root, 'packer', 'start', 'packer.nvim')
local compile_path = join_paths(install_path, 'plugin', 'packer_compiled.lua')

local function load_plugins()
  require('packer').startup {
    {
      'wbthomason/packer.nvim',
      'neovim/nvim-lspconfig',
      'hrsh7th/cmp-nvim-lsp',
      'hrsh7th/nvim-cmp',
      'hrsh7th/cmp-buffer'
    },
    config = {
      package_root = package_root,
      compile_path = compile_path,
    },
  }
end

local cmp = require 'cmp'

cmp.setup {
  sources = cmp.config.sources({
    { name = 'nvim_lsp' },
  }, {
    { name = 'buffer' },
  })
}

local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = require('cmp_nvim_lsp').update_capabilities(capabilities)

if vim.fn.isdirectory(install_path) == 0 then
  vim.fn.system { 'git', 'clone', 'https://github.com/wbthomason/packer.nvim', install_path }
  load_plugins()
  require('packer').sync()
  vim.cmd [[autocmd User PackerComplete ++once lua load_config()]]
else
  load_plugins()
  require('packer').sync()
end

I can see that the plugin is in the folder. and that it successfully discovers the buffer one, so I am at a loss.
 Directory of C:\Users\<USER>\AppData\Local\Temp\nvim\site\pack\packer\start

27/05/2022  12:10    <DIR>          .
27/05/2022  12:10    <DIR>          ..
27/05/2022  12:10    <DIR>          cmp-buffer
27/05/2022  12:10    <DIR>          cmp-nvim-lsp
27/05/2022  11:53    <DIR>          nvim-cmp
27/05/2022  11:29    <DIR>          nvim-lspconfig
27/05/2022  11:29    <DIR>          packer.nvim
               0 File(s)              0 bytes
               7 Dir(s)  209,480,146,944 bytes free

I am running on Windows NVIM version 7.

I think this anwsers my question?
https://github.com/hrsh7th/nvim-cmp/issues/290

This was all a red hering and every worked as expected.

because is loaded after the first insert mode, try to enter in insert mode, then test again to verify is worked or not.


[WIKI] Update the wiki pages

Hi, I am currently trying the new version and so far I am happy to see that Android is working nicely now, though I am having some trouble with iOS now (that was okay before 👍 )
I am writing this cause I saw some improvement that could be done on the wiki page and I can't make a PR for that so here they are :
in the Page :
https://github.com/react-native-kit/react-native-track-player/wiki/API
TrackPlayer.registerPlaybackService(() => require('service.js'));

Should be
TrackPlayer.registerPlaybackService(() => require('./service.js'));

// service.js
module.exports = async function() {
    // ...
}

Should be more detailed (had to go see the example to see what was supposed to be here)
// service.js
module.exports = async function() {
    // For example this three events will allow to pause, play and stop from notification.
   // You can find all the possible events in https://github.com/react-native-kit/react-native-track-player/wiki/Documentation#events

  TrackPlayer.addEventListener('remote-play', () => {
    TrackPlayer.play();
  });

  TrackPlayer.addEventListener('remote-pause', () => {
    TrackPlayer.pause();
  });

  TrackPlayer.addEventListener('remote-stop', () => {
    TrackPlayer.destroy();
  });
}

You actually explain it again in https://github.com/react-native-kit/react-native-track-player/wiki/API#playback-service maybe make a link to it directly would be a good idea
Thanks a lot for you library

The reason why I create an empty playback service is that the module won't run until you register one. In case someone is starting now step by step, it won't crash on Android.

@Guichaguri sorry about that then. Thanks for the details 👍

No, you're right. I should at least write "we'll see use this later" or something like that.

@Guichaguri Should I close this or leave it open  ?


[AI Gateway] OpenAI compat endpoints

@G4brym, mind taking a quick look to make sure I'm not making anything up?
Tested locally and worked fine for me.


⚠ SceneTime has degraded performance

In 07e712a, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1207 ms

Resolved: SceneTime performance has improved in 20ff6f5 after 6 minutes.


iroha_crypto panic

when I try to decode 04000001aeeba99f825cf8e4e6d7270b30fd927aa4c5b030df2ff891f28c2cc5b6d5d7990000  hex string with parity_scale_decoder I get a panic like this:
thread 'main' panicked at crypto/src/signature/ed25519.rs:31:31:
range end index 32 out of range for slice of length 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This happens on v2.0.0-pre-rc.21.3 branch so it may not be a problem anymore

Still happens on main. Need to make the conversions to arrays in iroha_crypto fallible


Replace BookeoEnum.from_str() with native Enum functionality

BookeoEnum class in schemas.py implements a from_str() method, which is unnecessary.
Replace references to this method with Subclass["value"] calls as seen here.

Turns out I already did this when I swapped over to Pydantic, whoops.


[20.03] slirp4netns 0.4.3 -> 0.4.5

Contains backport of #82902 + bump to 0.4.5.
Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2020-1983 (the CVE is for libslirp which is vendored in this version of slirp4netns)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@mmilata did you also bump master to 0.4.5? feels weird to have release-20.03 ahead of master.

Master was updated from 0.4.4 to 1.0.0.


Unable to find a specification for RACarousel

Hi I'm on Xcode 10.2.1 and try to install RACarousel using CocoaPods but I encounter this error while installing. Then I search CocoaPods library but I am not able to find RACarousel
[!] Unable to find a specification for `RACarousel`

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

@thunpisit the workspace is currently in development as is the repo, it should be ready for beta testing soon. The Pod is not ready yet.

Gotcha, thank you for the response.

@thunpisit the library has been updated and linked to a pod now.

@realityworks When I try to install pod 'CircularCarousel' it said,
[!] Unable to find a specification for `CircularCarousel`

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

Since it is a new Repo, have you done a 'pod repo update'?


Resolved Forgot_password error #96

Fixes: #96
Proposed Changes

Changed done in settings.py file

Additional Info

Made a new gmail ID. Password and Username in the settings.py file

Screenshots
Password Reset done!

Hey @Kajol-Kumari , I've resolved the issue of forgot_password , Kindly take a look at the changes..

Good Work @kritikaparmar-programmer :+1:


Support generating schemes with testable reference from different project

We're generating multiple projects, each has a build target and a test target. In order to run all the tests, we had to create each scheme for each test target in each project, and execute each of them.
It would be great if XcodeGen could generate scheme with references to test targets from other projects, so that running all tests can be done with just building one scheme.

Hi! I am at the same situation.
I also need to add test target from a framework (located in the same workspace as my applicaiton target) into build scheme of app target for all the tests to be run by one cmd+U press)

I have the same need.
I create multiple projects by having separate XcodGen config files for each project. xcodegen generate is called separately for each config. I want to create a scheme which runs the unit tests of each project. Xcode itself allows me to do that, but XcodGen validator does not:
5 Spec validations errors:
- Scheme "AllTests" has invalid build target "TestOfProjectA"
...

After checking the content of the schemes a bit, I assume this feature is out of scope for XcodeGen as the scheme reference the external project by using the BlueprintIdentifier which is declared in the external project.
Hopefully we will see progress of #168 at some point.

@thii @valnoc For now I will create the scheme manually (one time) in the workspace. It's shared with the team and works also after project regenerations as the the IDs stay the same after project regenerations.

@thii @valnoc For now I will create the scheme manually (one time) in the workspace. It's shared with the team and works also after project regenerations as the the IDs stay the same after project regenerations.

Hi! I do it the same way as you - by sharing this schema with the team. Anyway, this feature could be rather helpful, i think)


Use prepare shop helper in all e2e

Problem
Right now we have prepare_shop utils that create a basic store, we want to extend this function to allow creating a more flexible shop config and use it in all tests.
General Assumptions
Channels

[ ] creating more than 1 channel (with different currencies)
[ ] setting stock/payment/order

Warehouses

[ ] creating more than 1 warehouse

Shipping zones

[ ] creating more than 1 shipping zone
[ ] adding many countries to the shipping zone

Shipping methods (shippingPriceCreate)

[ ] possibility of creating 2 or more shipping methods with different prices
[ ] possibility to add postal code rules
[ ] possibility to set min/max order weight, delivery time

Shop

[ ] possibility to update shop settings

Taxes

[ ] possibility to update strategy, priceEnterWithTaxes, country rate

https://github.com/saleor/saleor/pull/14779


We need horizontal trees in craft recipes

In one of moretrees craft recipe, a specific node is required, moretrees:jungle_trunk_sideways. This name is an alias for moreblocks:horizontal_jungle_tree, which was a node from moreblocks, removed more than a year ago. We should add this node back along with its craft recipe.

https://github.com/MinetestForFun/minetest-minetestforfun-server/commit/399ece08b6a32c55f8934bc7762ee0b96309bd9c


LVS-13789 added a guard statement to stop errors on empty input

Apparently I don't have write permission on this repo, so can't merge it...


Unify CachedDbAccess/ForCopy to one struct

Addressed some of the items in https://github.com/kaspanet/rusty-kaspa/issues/60


Will animation composition be supported?

It doesn't seem to be in the Build Target Comparison table, but looks like something polyfillable.

This is covered by "Additive animation" in the table, it will be implemented eventually.

Just a note - additive animation is now slated for level 1 of the spec and hence will eventually be implemented in web-animations-1.


"Go" button hangs over page edge on mobile

Can I also submit an issue for Android's terrible clipboard support

note to self: check this after newest version of base is applied to arxiv.org/search-beta (footer styling is telling me that recent updates have not yet been applied).

New layout to be implemented by ARXIVNG-337:

Oh, that's gorgeous

Nice fix for the pagination button alignment, too

Thanks for noticing! It was an opportunistic fix.


v0.2.2

Change log:

[Update] Bump dependencies to latest

Homebridge to 1.7.0
Node to 20.10.0

Hopefully next release will have time to work on some of your issues guys!
☕ in the meantime any donation paypal.me/MinaMoanes would be much appreciated and would help me continue investing time to support the plugin ;)

Great work!
Would it be possible to add the addition items to support garage door
opener?
I added the changes in the discussion section of your repository?
Like to share for others.
Vince
On Sun., Dec. 3, 2023, 12:15 p.m. Mina Moanes, @.***>
wrote:

Change log:

[Update] Bump dependencies to latest

Homebridge to 1.7.0
Node to 20.10.0

Hopefully next release will have time to work on some of your issues guys!
☕ in the meantime any donation paypal.me/MinaMoanes would be much
appreciated and would help me continue investing time to support the plugin
;)
You can view, comment on, or merge this pull request online at:
https://github.com/minamoanes/homebridge-homekit-control/pull/12
Commit Summary

d92f0a7
https://github.com/minamoanes/homebridge-homekit-control/pull/12/commits/d92f0a70b18b5e7e231346d76d4198ec323761bb
[Update] Bump dependencies to latest

File Changes
(4 files
https://github.com/minamoanes/homebridge-homekit-control/pull/12/files)

M package-lock.json
https://github.com/minamoanes/homebridge-homekit-control/pull/12/files#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519
(6866)
M package.json
https://github.com/minamoanes/homebridge-homekit-control/pull/12/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
(40)
M src/HKClient.ts
https://github.com/minamoanes/homebridge-homekit-control/pull/12/files#diff-b8cc8444b84c04dc9175207515834d87f6ad2c92e26f22118365f0e03cad906e
(6)
M src/HttpWrapper.ts
https://github.com/minamoanes/homebridge-homekit-control/pull/12/files#diff-093d83a25d7b0a1b85ed4dd5a6f4a2d90e0c6ba65dcc935d5b43ada6328f7464
(10)

Patch Links:

https://github.com/minamoanes/homebridge-homekit-control/pull/12.patch

https://github.com/minamoanes/homebridge-homekit-control/pull/12.diff

—
Reply to this email directly, view it on GitHub
https://github.com/minamoanes/homebridge-homekit-control/pull/12, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AM4Q7GRK23FN2L7STGZNYLLYHSXTZAVCNFSM6AAAAABAE5NOFCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZDENRSHE4DONQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76656

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76854

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/79645

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120247


Throw error when no auth mechanism is matched

https://github.com/prometheus/alertmanager/blob/d5b8e1028695866d52abd36fcf1973b1fdc9c807/notify/impl.go#L254
In case we are asked to auth and no auth mechanism matched and returned from function, we should return error saying something like: "No mechanism matched server offer: 250-AUTH NTLM"

Great catch @danielkucera. Would you like to propose a PR for that?

I have no env to test this so I would propose someone else to develop this...


Add 'provideIn' for the service

Current behavior
When the translater is defined in a library, and used in others module, the code/package will not be touched by the angular compiler, so packer (in my case Rollup)  has no metadata available.
Expected behavior
ngx-translate is included in the build process
What is the motivation / use case for changing the behavior?
I'm still trying to figure out, what has exactly changed between Angular 5 and Angular 6, but I think this could be a reason. The referring modules aren't seeing the TranslateService.
How do you think that we should implement this?
In Angular 6 (see Angular), the service should be now made available as:
@Injectable({ provideIn: 'root'})
export class TranslateService { […] }

Thanks for answering, I see your point.
I don't reference your service directly, I reference a wrapper service in the module which is using your service in ngx-translate. I don't get it, why Angular thinks now, ngx-translate isn't used and doesn't compile it.


Upgrade service mesh related apps

WHY
Current Istio version is EOL
Istio to 1.20.5
Acceptance criteria
GIVEN workload with Otomi public service
WHEN I upgrade Otomi
THEN I can still request from that public URL
GIVEN Otomi SHELL
WHEN I upgrade Otomi
THENI can still access the shell as a team member
GIVEN RabbitMQ in workload catalog
WHEN I upgrade Otomi
THEN I can still create and instance of RabbitMQ
Definition of done

[x] Relevant PRs are merged
[x] Tested by peer
[ ] Updated documentation reviewed by peer
[ ] Short demo video recorded and stored on google drive (if applicable)

Isito upgraded


renaming with split window causes Atom to hang

Using Atom 1.3.2 on a Mac:

Open a Dart file.
Right-click on the tab and choose "Split right"
Rename a Dart variable.

This causes Atom to hang. Eventually I get a "the application is not responding" dialog.
I found that upgrading to Atom 1.4 fixed this issue.

Possibly relevant: I have autoformat on save turned on.

Hmm, I can repro this in atom 1.3.1, but not in atom 1.4.

Yes, that's right.

Yeah, I think this is uncovering a bug on the atom.workspace.open() call. Atom is not returning from that call when I have two panes open during a refactoring. I've worked around a bug in this API call before. Looks like this particular issue is fixed in 1.4.

I'm going to close this out as atom 1.4 is now the stable version.


Question about .nyc_output and window.coverage

I am trying to generate HTML report from window.__coverage__ object, with partial success. It seams that easiest way to to this would be using nyc, which as I see only supports creating report from existing .nyc_output folder.
Is there a straightforward way to get .nyc_output folder from __coverage__ object? If not, what would be the right direction to go?
Thanks for reading this ✌

@miloss if you simply output the contents of window.__coverage__ (assuming it's in Istanbul 1.0 format) to .nyc_output/out.json, you should be able to run nyc report --reporter=html to get an HTML report.
Would this do the trick for you?

Yes, that worked perfectly. Thank you so much 👏
You think this would be worth adding to documentation? Or is this way of getting coverage (from browser/global object) not really recommended in the long term?


[Bug]: Hamburger menu links don't not work on Safari

Version
master
What browsers are you seeing the problem on?
Safari
Describe the bug
When using:
[params.navItems]
pt = { href = "/pt", title = "Português", target = "_self" }
en = { href = "/en", title = "English", target = "_self" }
fr = { href = "/fr", title = "Français", target = "_self" }
The links are correctly displayed on a desktop screen. Hamburger menu links also work perfectly.
Testing on iOS Safari or MacOS Safari, the links won't work when the hamburger menu is displayed.
If we rotate the screen, the options work again (outside the hamburger menu).
There is no error message in the console. It seems to be related to how Safari handles z-index.
Example build with problems:
https://inovamakers.com/en/
To Reproduce
Open Safari on iPhone or macOS.
Make the hamburger menu show up. In the desktop, you can narrow the window to force it.
Open the hamburger menu. Try to click on English, Português or Français options. Nothing happens.

After testing, I found that this is indeed a bug related to Safari and I've fixed it. Thanks for pointing this out! 👍🏼


⚠ Bofrost.lu has degraded performance

In 3396cc8, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1420 ms

Resolved: Bofrost.lu performance has improved in 7765ba2.


lostfilm.tv changed system again

from: http://www.lostfilm.tv/browse.php?cat=145
to: http://www.lostfilm.tv/series/Game_of_Thrones
as result: Игра престолов / Game of Thrones status changed: Not Found

That means that there was not changed :)
You can edit this topic, end decrease the latest downloaded episode.
And rerun check.

oh, sorry, it's started worked after next check. Looks like you was expecting something like that from them and monittorent was prepared :)


Calendar link is wrong

Description
Clicking on the Calendar link (either the icon at the bottom or the menu item at the top) takes me to a link that does not exist:

Steps to reproduce issue
Click on calendar icon / menu item.
Details
Wrong link seems to be hardcoded.  I can't see an option to change.

Sorry - totally wrong place!  Closing.


WASM Interface

While I am workin on finishing up #173, I drafted up some stuff here which allows us to wrap the user's infer implementation with custom logic. I don't know if this would actually work though. For the user it would look like:
use carton_wasm_interface::infer;

#[infer]
fn infer(in_: Vec<(String, Tensor)>) -> Vec<(String, Tensor)> {
    // ...
}

The reason this work around is needed is because the .wit interface needs to be implemented in the same place the bindings are generated. Now we can implement stuff like conversions for candle and returning a pointer (and managing it's lifetime) easily.
Let me know if you have any thoughts! I'm hoping it makes developing wasm models more ergonomic.

I think the high level idea makes sense.

I drafted up some stuff here which allows us to wrap the user's infer implementation with custom logic. I don't know if this would actually work though.

Since we ultimately need to expose multiple functions from user code, what if we structure it as a trait instead of as an attribute macro? That also has the benefit of allowing types to be a little more flexible (e.g. something like impl IntoIterator<Item = (S, Tensor)> where S: Into<String> instead of Vec<(String, Tensor)>). The user then has to register an implementation of this trait (see below).

The reason this work around is needed is because the .wit interface needs to be implemented in the same place the bindings are generated.

What if our "registration" macro uses wit_bindgen::generate! internally? That way the expanded code will generate and implement the bindings in the same place.
For example:
use carton_wasm_interface::{Model, register_model};

struct SomeUserModel;

impl Model for SomeUserModel {
    fn infer(...) -> ... {
        // ...
    }
    // ...
}

register_model!(SomeUserModel);

The macro would expand to something like:
wit_bindgen::generate!({
    world: "model",
    // Either use an absolute path here or pass in the wit file using the `inline` param
    path: "...",
    exports: {
        world: CartonExportedModel
    }
});
struct CartonExportedModel;
impl Guest for CartonExportedModel {
    fn infer(in: Vec<(String, Tensor)>) -> Vec<(String, Tensor)> {
        // We can do type conversions here
        SomeUserModel::infer(...)
    }
}

I don't think we even need a proc macro to implement this and we can just use declarative macros instead.
What do you think?

I definitely like the trait a lot more. I'm still debating if the macro should expand in the user's code or ours. If it's in the users code we don't need to deal with initializing the module, if it's in our code, we can be more flexible with implementing stuff, since we wouldn't need to define them in the macro.

Expanding it in the user's code (as in my comment above) also has the benefit of not requiring the trait to be object safe.
If we wanted to store a user's trait implementation and expose it to the wit_bindgen::generate! macro as a non-generic struct in our code, we'd likely need to wrap the user's trait implementation in a Box<dyn Model>. Calling methods on that requires object safety which removes flexibility for generics in the trait (e.g. impl IntoIterator<...>).
(The approach in my comment above also has the benefit of not requiring dynamic dispatch, but that almost certainly doesn't matter in this case)

@leifu1128 just wanted to check if you had a chance to work on this more. Thanks!


[Suggestion] - Support single-node Jira deployments

Suggestion
It would be nice if the Jira chart supported single-node deployments. You don't always need the hassle and additional costs of additional volumes etc.

Make "shared home" optional. When it's disabled, don't create the shared-home volume, its corresponding volume mount, and the JIRA_SHARED_HOME env var.
Enable separation of liveness and readiness probes. Let us configure the readiness probe so that it only checks the tcpSocket. Jira has a nice loading splash screen, let us see that. Move the /status health check to liveness probe.

Product
Jira
Code of Conduct

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

Closing in favor of https://github.com/atlassian/data-center-helm-charts/issues/459


The repo not works

Following your comments your, repository to download your grpc-swagger-springdoc-openapi library not works

Readme Note: This dependency not working for public. I will serve with maven central repo as soon as possible. (Sorry for that.)

I actually didn't any upload jar on central maven so i dont know how to upload actually. But if u need i try to upload this project on central maven as soon as possible (probably in this week).

An alternative suggestion: You can download source codes and mvn clean install on local machine and u can use another project with local mvn created repo.


[stable/anchore-engine] Update images to latest versions

anchore/anchore-engine:v0.7.2
anchore/enterprise:v2.3.1
anchore/enterprise-ui:v2.3.1
Signed-off-by: Brady Todhunter<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @zhill

/lgtm


Does not seem to be working in

SELECT @@version:  Microsoft Azure SQL Data Warehouse - 10.0.11038.0 Apr 21 2020 19:42:42 Copyright (c) Microsoft Corporation
DBCC SHOWRESULTCACHESPACEUSED;
Returns:
Msg 104311, Level 16, State 1, Line 44
Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.
Completion time: 2020-05-11T15:35:45.4713251+01:00

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

ID: 66637528-2d6c-4798-db89-3abd393f75a4
Version Independent ID: 21f933e5-a3d4-46a8-9f3e-b2f9e14e6647
Content: DBCC SHOWRESULTCACHESPACEUSED (Transact-SQL) - SQL Server
Content Source: docs/t-sql/database-console-commands/dbcc-showresultcachespaceused-transact-sql.md
Product: sql
Technology: data-warehouse
GitHub Login: @XiaoyuMSFT
Microsoft Alias: xiaoyul

Digging a bit more I have found that the RESULT_SET_CACHING was not enabled (via ALTER DATABASE [DB] SET RESULT_SET_CACHING ON;).
Once enabled the DBCC command started working. The error message should read "RESULT_SET_CACHING is OFF" rather than incorrect DBCC statement. It may be worth amending as the message is misleading.

@Robert-Kostecki -- Robert, thank you for your feedback and researches.
@XiaoyuMSFT -- Xiaoyu, please look into this issue.

@Robert-Kostecki Hi Robert, I am sorry for the delay in response. I am checking to see if we can update the error statement.

@Robert-Kostecki Hi Robert, I am sorry for the delay in response. I am checking to see if we can update the error statement.

#assign:julieMSFT

#assign:julieMSFT

No probs Julie!

No probs Julie!

@Robert-Kostecki Hi Robert, I am still trying to get a date for this update. I am going to go ahead and close this issue and update you once the update happens. The @notification mechanism continues to work even after an item is closed, in case further communication is needed. We hope to hear from you again.

DevOps work item

#please-close

Perfect - thank you.


Revert "python311Packages.google-auth: 2.17.3 -> 2.18.1"

Reverts NixOS/nixpkgs#232663
Breaking change during the breaking changes freeze.
https://github.com/NixOS/nixpkgs/pull/232663#issuecomment-1554046979

#232752 fixes the issue.


InternalException about Generalized Variables

There is no A in bar's telescope because A was not used in bar's telescope. However, we can't just set allowGeneralized = false when resolving the body because we should accept foo.
We can generate more generalized variables after we resolve the body, but this sounds not good:

The newly generated variables won't be appended to the LocalCtx of the meta which is in the telescope

IMO bodies should not use generalized variables.

But I think we can make it work for generalized

So I reopen this.


Add ability to scan multiple repositories at once

Context
If you want to manually scan more than one repository at once, you need to do them in separate invocations.
$ detect-secrets-server scan https://github.com/Yelp/detect-secrets
$ detect-secrets-server scan https://github.com/Yelp/detect-secrets-server

It would be convenient if you could specify more than one repository inline.
$ detect-secrets-server scan https://github.com/Yelp/detect-secrets https://github.com/Yelp/detect-secrets-server

This way, you could chain it with other CLI tools.
$ detect-secrets-server list | xargs detect-secrets-server scan

Proposed Fix
As described above.

I found myself trying to scan passing in the same config file I used to add. Seems like that should be sufficient?

@chetmancini : which version of detect-secrets-server are you referring to? I think v0.1 supported config files in scan, but not v0.2 IIRC.

Interesting. I'm using the latest version. I'm brand new and am trying to setup this up first time to scan multiple repos. I'm still getting up to speed but will see if I can help enhance anything down the road.

How curious.
Could you provide your example invocation for posterity?

Sure. I was thinking I could pass the repos.yaml file as the parameter to scanning, so you could have your configuration passed directly into the scan process.
# add them
$ detect-secrets-server add --config examples/repos.yaml
# scan them
$ detect-secrets-server scan --config examples/repos.yaml

@domanchi  Any update on multiple repo scanning in 2.0? eagerly awaiting this enhancement

@chetmancini : Ah yes, that was the original intent. Since this is a server-side tool, configuration files allow source controlled declaration of repositories to scan. I agree that feature is a "nice-to-have", rather than a much needed improvement due to this.
@akshayatplivo : You're always welcome to help contribute to this repository! My bandwidth is quite limited to work on this, but I had previously flagged this as a good first issue, so maybe this is a good opportunity to get your feet wet. 😃


Update docs output path

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Prototype Pollution vulnerability

🐛 Bug Report
A Prototype Pollution vulnerability has been raised by Snyk and it is affecting all versions of immer.
The vulnerability seems to be on the following line
Find more details here
Environment
All immer versions

Solved and released in 8.0.1

Solved and released in 8.0.1

Were only applyPatches affected, or regular, recommended use of immer too, transitively affected?
(just wondering how urgent it is to push new version of depending software into production)

Were only applyPatches affected, or regular, recommended use of immer too, transitively affected?
(just wondering how urgent it is to push new version of depending software into production)

Just patches, and only if you can't trust the source of the patches. E.g.
someone could construct / alter patches in his browser session, send them
to the server, and then they can potentially be used later to break another
client that receives those patches if they are passed along unvalidated.
On Thu, Jan 21, 2021 at 4:38 AM Dima Tisnek<EMAIL_ADDRESS>wrote:

Were only applyPatches affected, or regular, recommended use of immer
too, transitively affected?
(just wondering how urgent it is to push new version of depending software
into production)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/738#issuecomment-764286104, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBBKYMLCFJ77S67DQ3LS26VUJANCNFSM4WJEPJAQ
.

Just patches, and only if you can't trust the source of the patches. E.g.
someone could construct / alter patches in his browser session, send them
to the server, and then they can potentially be used later to break another
client that receives those patches if they are passed along unvalidated.
On Thu, Jan 21, 2021 at 4:38 AM Dima Tisnek<EMAIL_ADDRESS>wrote:

Were only applyPatches affected, or regular, recommended use of immer
too, transitively affected?
(just wondering how urgent it is to push new version of depending software
into production)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/738#issuecomment-764286104, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBBKYMLCFJ77S67DQ3LS26VUJANCNFSM4WJEPJAQ
.


components option should support readonly object

Vue.js version
2.0.0
Reproduction Link

Steps to reproduce
// components/index.js export Foo, Bar etc.
import * as components from './components';

export default {
  name: 'app',
  components
};

What is Expected?
Show ok without errors.
What is actually happening?
Browser throw error components has only getter.
Reasons
function normalizeComponents (options) {
  if (options.components) {
    var components = options.components;
    var def;
    for (var key in components) {
      var lower = key.toLowerCase();
      if (isBuiltInTag(lower) || config.isReservedTag(lower)) {
        "development" !== 'production' && warn(
          'Do not use built-in or reserved HTML elements as component ' +
          'id: ' + key
        );
        continue
      }
      def = components[key];
      if (isPlainObject(def)) {
        // should create or clone new components object inside Vue
        // instead of old one
        components[key] = Vue$3.extend(def);
      }
    }
  }
}

@xiaoping0x could you please provide a JSFiddle/JSBin/Codepen to demonstrate your issue ?

It seems because webpack 2 treats an imported object as read only.

@ktsn I think this is a ES-spec conforming behavior. http://exploringjs.com/es6/ch_modules.html#sec_imports-as-views-on-exports also here http://www.ecma-international.org/ecma-262/6.0/index.html#sec-module-namespace-exotic-objects


High DPi (4k) not supported

Brief Description:
Operating System (OS and version): Ubuntu 16.04 x64
OpenBazaar version (shown on About OpenBazaar page in menu): 1.1.7
Hardware: Dell XPS 15 9550
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Always
Steps to reproduce:

Start OpenBazzar

Observed Behavior: Everything is too small
Expected Behavior: The UI must adapt to scaling factor set in Ubuntu Settings.
Additional info (links, images, etc go here):

Thanks for reporting this issue.
Some responsiveness is on the roadmap for v2. For example, in v2 the plan is for the grid of listings to be expandable to the full width of the window.
At this time, we don't have any plans to retro-fit v1 with this functionality.

Why was this closed? It's still an issue... The text and buttons are crazy small on my machine..

@stevenroose Because v1 will not receive major updates, all the effort is done for v2 (this should be fixed in v2)

Oh, v2 has a separate repo. That makes it clear :) Thanks!

Looks like https://github.com/OpenBazaar/openbazaar-desktop/issues/435 added support
But out of the box things could still use improvement: https://github.com/OpenBazaar/openbazaar-desktop/issues/1612


Make PluginSkeleton up to date with the latest changes made in Sylius

The symfony.lock file was added to prevent loading already managed configurations.
Symfony 6 fix: https://github.com/Sylius/PluginSkeleton/pull/387/files#diff-de1ec58376e3b692293daadf74c4531cac5eac13a4764d571a3bbeddf77ae135R14
The Webpack configuration has been unified and all JavaScript dependencies have been replaced with sylius-ui/frontend.
Newly created Doctrine migrations will be placed in the migrations directory. Before, it didn't work as all new migrations were placed in the vendor directory.

Thank you, Kevin! :1st_place_medal:


how to run after use yarn build

can anyone please provide or guide how to use application after build by using
yarn build
the app is working fine when I use yarn dev  but after using the build command
I don't know how to run.

Hi @codingbeast, I assume you want to build an artefact? We don't use yarn for that, we use nix for building.
Examples:
For Mac
sh ./scripts/build-installer-unix.sh --build-id ${number}

For Linux
nix-build -Q release.nix -A "${cluster}.installer.x86_64-linux" --argstr buildNum "$BUILDKITE_BUILD_NUMBER" -o csl-daedalus

But you can check the shell scripts located under ./scripts/

@michalrus  Can you please help me with how to create a Windows and Mac installer?

Sure!
Windows installer – has to be built on Linux (!)
$ cd daedalus/
$ nix-build -A windows-installer --argstr target "x86_64-windows" --argstr cluster "mainnet"

It will be in result/.
macOS installer – has to be built on macOS
$ cd daedalus/
$ scripts/build-installer-unix.sh --clusters mainnet

It will be in installers/csl-daedalus/daedalus-...-0.pkg.


Feature/airdrop vision pipeline

Added vision/airdrop_vision_pipeline.py

airdrop_pipeline(), which is a simpler version of the flyover pipeline that works slightly differently

Updated vision/README.md

Apparently I have to re-request a review even though the only thing I did was merge develop in

It happened again


New: Create load report

This PR adds the new Create load report sample in Utility network category. The issue on DT: common-samples/issues/2594
Link to the branch: here. Apologies for the wrong branch name - it was too late when I realized that I wasn't on the right branch

Thanks for the suggestions. I agree with and applied all of them and updated the screenshot. Please take another look!

From Friday's review

The upper half of the list doesn't need to be reorder-able. Instead, making it alphabetically ordered make more sense.
Good to use abbreviations
Clear dict when removed

From Jennifer: need to set includeBarriers to false.

Reset button is just resetting the values in report but not changing the list of selected phases. Is this expected?

Yep it is expected. Reset button only resets the load report summaries but not the phase table.

If the above mentioned behavior is expected, what is the purpose of even resetting those values, are they tend to change on different runs?

In a real world use case, the value will change on each run, since the electric utility network updates in real-time. But our demo doesn't change because the demo network is static.
I didn't find a doc that describes such use case in specific, but here is a similar one with the water network.


[BUG]: Two method are not existing for zarinpal driver, and only work on idpay.

Hello @AmirrezaNasiri  ✌🏻
Describe the bug
Two method are not existing for zarinpal driver,  and only work on idpay.
To Reproduce
Steps to reproduce the behavior:

Set default gateway to zarinpal in config/toman.php
Create Toman request:

 Toman::amount(10000)
            ->orderId('123')
            ->mobile('a valid mobile number')
            ->email('a valid email')
            ->callback('a valid site route')
            ->description('description of this payment')
            ->name('JalalLinuX')
            ->request();

See exception:

Method Evryn\\LaravelToman\\PendingRequest::orderId does not exist.

Now comment ->orderId('123')

 Toman::amount(10000)
            // ->orderId('123')
            ->mobile('a valid mobile number')
            ->email('a valid email')
            ->callback('a valid site route')
            ->description('description of this payment')
            ->name('JalalLinuX')
            ->request();

See exception:

Method Evryn\\LaravelToman\\PendingRequest::name does not exist.

Expected behavior
This package a multi pay driver package and it should have the same usage. but orderId, name method only work for idpay driver.
Screenshots

Exact Versions:

Laravel: 8.54
PHP: 7.4
Package: 2.0.1

Hi @jalallinux :)
Thanks for the issue submission. This is actually a discussable topic; The way we should generalize the package API and I've struggled with the issue when I was working on it.
I chose to follow driver-specific requirements for requests and callbacks and yet generalize some common parts of them; So developers can understand which driver expects what kind of inputs and considerations explicitly. This can for instance prevent depending on the non-existence $request->orderId() in the callback requests when the gateway has switched from IDPay to Zarinpal - because there is no definition of orderId in Zarinpal.
A developer can also use their own strategy design pattern to make gateways interchangeable easily. So my +1 goes for this architecture.
On the other hand, it's about the easiness of usage. A similar package for the study is Laravel Socialite, which generalizes callbacks (same in our case) and puts its related logic up to the developer itself. Though its providers are not completely interchangeable either (because of lack of the common attributes), and we also have the same issue for requesting side, I guess it's a +1 for this architecture too.
To summarize, I'm not sure about either of them. Developers need their own logic for interchangeability for both of them. I'm gonna keep this issue open - This is an interesting topic.


[contracts] Verify that end_game function is secure

Need to check if the calldata send is actually valid, if player did contribute to hyperstructure and was in the epochs

write tests


need login???

get this mnessage when try to join meeting:
"The conference has not yet started because no
moderators have yet arrived. If you'd like to become
a moderator please log-in. Otherwise, please wait."
The package was working for a long time but now is asking for a password or log-in
can I get help

Hello! Now authentication has been introduced to meet.jit.si. Check out this blog post: https://jitsi.org/blog/authentication-on-meet-jit-si/.


On Location changed error

I get this error which is making my app crash and its really a drawback in our app as it happens at critical moments:
FATAL EXCEPTION:
java.lang.NullPointerException
at org.osmdroid.views.overlay.mylocation.GpsMyLocationProvider.onLocationChanged(GpsMyLocationProvider.java:143)
at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:300)
at android.location.LocationManager$ListenerTransport.access$000(LocationManager.java:215)
at android.location.LocationManager$ListenerTransport$1.handleMessage(LocationManager.java:231)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5333)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:895)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:711)
at dalvik.system.NativeStart.main(Native Method)
Please help me resolve it

duplicate of #543 see that issue for the solution.

wait, different stack trace reopening

#486 duplicate of this ticket. I think the newer version fixes it.

Im using the version 5.6.2,
On Tue, Jan 24, 2017 at 4:05 PM, spyhunter99<EMAIL_ADDRESS>wrote:

#486 https://github.com/osmdroid/osmdroid/issues/486 duplicate of this
ticket. I think the newer version fixes it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/550#issuecomment-274847686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFTMTH6aTJBIlwToqAiJgB7b2KGnFzazks5rViEvgaJpZM4LsWr8
.

--
Alfie

So the 5.6.3 fixes it?

yes.

Ok, will update it. Thanks

well technically it was fixed in 5.6. strange that you ran into it again. That line number does not align with the current code base, so it was probably with an older version that 5.6

Well, ill update to 5.6.3 and see what happens
On Tue, Jan 24, 2017 at 4:25 PM, spyhunter99<EMAIL_ADDRESS>wrote:

well technically it was fixed in 5.6. strange that you ran into it again.
That line number does not align with the current code base, so it was
probably with an older version that 5.6
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/550#issuecomment-274854477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFTMTHTBnD11Ef-JTXlA5r0KYYGtcrJjks5rViYHgaJpZM4LsWr8
.

--
Alfie

operation timeout. please reopen or comment back if you have further questions


Adds markdown syntax fixes

Checklist

[x] the individual contributor license agreement is signed

Description of change

Coverage decreased (-0.02%) to 22.886% when pulling 0e0cb6f7163bf3d94a58dbd73c9e491c542d1492 on vertein:mdFixes into 3b32c77387735ce296eee482640f0b6ff1a4d157 on apetro:slurp-in-documentation.


Rule Collection Prority Number Convention and Guideline

I'm looking for document on rule collection priority number,

Range
Incremental by 1, 10, 100?
Best Pracitce

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

ID: 474ba3cb-afa1-4ec5-37df-6553a5523dbb
Version Independent ID: 56096558-1943-3f6b-9609-7722200272fb
Content: What is Azure Firewall?
Content Source: articles/firewall/overview.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

@RonnieQuan , Thank you for your feedback. We will investigate and get back to you shortly.
@vhorne , Can you please take a look at this new doc idea?

Updated https://docs.microsoft.com/en-us/azure/firewall/rule-processing with some additional info
#please-close


CPAN modules that require non-base system libs are not supported

I attempted to create a Perl-based image from an application that requires the GD module, which depends upon libgd. I tried using the perl-516-centos7 s2i image for this purpose.
The cpanm approach to adding and building modules failed due to the absence of the gd-devel RPM in the builder, but this problem also exists in the resulting image. In the output below, you can see that even if I use cpanm on a CentOS 7 host to build and vendor-ize the GD module into my source repo, it still fails for lack of the needed libraries:
bash-4.2$ ldd /opt/app-root/src/Vendor/lib/perl5/x86_64-linux-thread-multi/auto/GD/GD.so
	linux-vdso.so.1 =>  (0x00007ffdfcc48000)
	libXpm.so.4 => not found
	libX11.so.6 => not found
	libjpeg.so.62 => not found
	libfontconfig.so.1 => not found
	libfreetype.so.6 => not found
	libpng15.so.15 => not found
	libz.so.1 => /lib64/libz.so.1 (0x00007fbfb6b2b000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fbfb6828000)
	libgd.so.2 => not found
	libc.so.6 => /lib64/libc.so.6 (0x00007fbfb6467000)
	/lib64/ld-linux-x86-64.so.2 (0x0000560035716000)

Many of the CPAN modules depend upon system libraries in order to function properly, and currently there is no way to specify RPMs that must be installed - both in the build environment and the completed image - to enable these modules to function.
One possible solution may be to specify a named file (similar to the cpanfile) where devs can list the RPMs that are required by their CPAN modules.

That's great idea and I know about this deficiency. But It's common problem for all images and I'd like to see the same API (e.g. a file name and its format) in all other CentoOS-based images. And also there is a possibility that it will not work in OpenShift image builder because it would require root privilege when building an application image from an s2i-ready base image and that's not allowed for security reasons. At least I think it's so.
@mfojitk, what's your opinion?

@ppisar @nhr the problem is that we run assemble as non-root user, so we won't be able to install the packages you specify in the file. The solution for this today is that you have to create your own Docker image with all dependencies installed. If we get many requests to add gd lib we should install it in the base image. @bparees right?

@mfojtik +1
btw @nhr I suggest you use the centos/perl-520-centos7 image instead, just for currency reasons.

Docker 1.10 can do user name spacing. Finally. With this feature, we OpenShift could support assembling as root. Couldn't?

@ppisar they are not the namespaces we were hoping for, so we can't enable root user by default.


feat: support full backup

ref: https://github.com/longhorn/longhorn/issues/7070

Add BackupCount in BackupVolume, so we can calculate the interval to achieve periodically full backup
Add NewlyUploadedDataSize  and ReUploadedDataSize to each Backup. So user can know the data transfer size for each Backup to trace the cost.
Add Parameters to the Backup Config.

If the backup has the parameter backup-mode: full, it will pretend there is no last backup, and backup all the blocks of the current volume.

Dependent PR:

https://github.com/longhorn/go-common-libs/pull/26

CI failed, will consult @FrankYang0529
Error response from daemon: {"message":"client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}
Starting NFS server
Warning: failed to get default registry endpoint from daemon (Error response from daemon: {"message":"client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}). Using system default: https://index.docker.io/v1/
Error response from daemon: {"message":"client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}


Use the new TypeIs feature to update the notna/notnull/isna/isnull type guards

[x] Closes #911
[x] Tests added: Please use assert_type() to assert the type of any return value

Thanks @gandhis1, not sure though if the CI has triggered on the last commit.

I think this change isn't quite correct: https://github.com/pandas-dev/pandas-stubs/issues/1009. The return value of this function doesn't actually discriminate the type, because some float are NaN and others aren't.


Access Source from Sink

Hello,
I have a question regarding accessing the underlying source of a sink, in my case, I'm using a Decoder. It appears that some functions implemented in Source, such as total_duration(), are not available in Sink (assuming that it's possible to query the currently playing source).
I was also wondering if it's possible to modify the source in real-time, for instance, by applying filters? If not, one potential solution I considered is to reconstruct the source and seek it back to the previous position. Though, I am curious if there might be a more efficient approach.

such as total_duration(), are not available in Sink

correct, I speculate because a sink can have multiple sources in it and it would be unclear what total_duration() should return. That can easily be solved but no one has had the time or need I think. You can easily adress it by checking total_duration before you push something into a Sink.

I was also wondering if it's possible to modify the source in real-time, for instance, by applying filters?

You can certainly build something that does that using rodio. It would be a bit of work. Take a look at the Source trait. Anything implementing Source can be played by a sink. The object implementing Source is free to do whatever it wants in its implementation as long as it can give the Sink a sample when it asks for one.
You can set up some communication to your Source implementing object to control what it does from outside the Sink.
Have you however taken a look at https://crates.io/crates/kira? Its a bit less extensible then rodio but has real time modification of the filters/effects applied to a source as a main goal.

oh and take a look at periodic_access for an example of how its used open the source for Sink.


fixed typo in pip install to fix issue #355

previously was "pip install azure-mgmt-powerblembedded"
fixed to "...powerbi..."

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/power-bi.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/power-bi.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Disk offering doesn't change when resize operation is performed

ISSUE TYPE
Bug/Enhancement/Improvement request/
COMPONENT NAME
Component: UI/API/Usage
CLOUDSTACK VERSION
Cloudstack version 4.18
SUMMARY
Disk offering doesn't change when the resize operation is performed
https://cloudstack.apache.org/api/apidocs-4.18/apis/resizeVolume.html
Steps to reproduce the issue

Create a data disk with offering 5gb ( Small disk offering)

Click on the Resize

Navigate volume> select the disk and click on Resize option

or execute the resizeVolume api call
https://cloudstack.apache.org/api/apidocs-4.18/apis/resizeVolume.html

Provide the new disk size let's say 10gb

Cloudstack resizes the data disk to 10gb, successfully but doesn't change the disk offering to custom disk offering

Actual behavior
According to docs
http://docs.cloudstack.apache.org/en/<IP_ADDRESS>/adminguide/storage.html?highlight=disk resize#resizing-volumes
Additionally, using the resizeVolume API, a data volume can be moved from a static disk offering to a custom disk offering with the size specified. This functionality allows those who might be billing by certain volume sizes or disk offerings to stick to that model, while providing the flexibility to migrate to whatever custom size is necessary.
Even for the resizevolume api call is  disk offering id is not mandatory
https://cloudstack.apache.org/api/apidocs-4.18/apis/resizeVolume.html

Not changing the disk offering id could lead billing issue if the end user considers disk offering for billing
If we take a look at the Database entries the offering id remains the same even after the resize is done, ideally it should change to a custom disk offering
Usage_event table
The offering_id=3 is not  updated when a volume.resize is performed
mysql> use cloud;
mysql> select * from usage_event where resource_id=41 \G;
*************************** 1. row ***************************
           id: 146
         type: VOLUME.CREATE
   account_id: 2
      created: 2023-12-28 05:19:12
      zone_id: 1
  resource_id: 41
resource_name: ty
  offering_id: 3
  template_id: NULL
         size:<PHONE_NUMBER>
resource_type: NULL
    processed: 0
 virtual_size: NULL
*************************** 2. row ***************************
           id: 147
         type: VOLUME.RESIZE
   account_id: 2
      created: 2023-12-28 05:19:29
      zone_id: 1
  resource_id: 41
resource_name: ty
  offering_id: 3
  template_id: NULL
         size:<PHONE_NUMBER>
resource_type: NULL
    processed: 0
 virtual_size: NULL

mysql> use cloud_usage;
mysql>select * from cloud_usage where usage_type=6

              id: 235
         zone_id: 1
      account_id: 2
       domain_id: 1
     description: Volume Id: 41 usage time (DiskOffering: 3)
   usage_display: 0.499999 Hrs
      usage_type: 6
       raw_usage: 0.49999913573265076
  vm_instance_id: NULL
         vm_name: NULL
     offering_id: 3
     template_id: NULL
        usage_id: 41
            type: NULL
            size:<PHONE_NUMBER>
      network_id: NULL
      start_date: 2023-12-28 05:45:14
        end_date: 2023-12-28 06:15:14
    virtual_size: NULL
       cpu_speed: NULL
       cpu_cores: NULL
          memory: NULL
quota_calculated: 0
       is_hidden: 0

mysql> select * from usage_volume where volume_id=41 \G;
*************************** 1. row ***************************
              id: 29
       volume_id: 41
         zone_id: 1
      account_id: 2
       domain_id: 1
disk_offering_id: 3
     template_id: NULL
            size:<PHONE_NUMBER>
         created: 2023-12-28 05:19:12
         deleted: 2023-12-28 05:19:29
*************************** 2. row ***************************
              id: 30
       volume_id: 41
         zone_id: 1
      account_id: 2
       domain_id: 1
disk_offering_id: 3
     template_id: NULL
            size:<PHONE_NUMBER>
         created: 2023-12-28 05:19:29
         deleted: NULL
2 rows in set (0.00 sec)

Expected behavior
Cloudstack should update the disk offering to custom disk offering in UI and the databases (Cloud and cloud_usag)
mysql> select * from disk_offering where id=6 \G;
*************************** 1. row ***************************
                         id: 6
                       name: Custom
                       uuid: 9cc36337-08a4-4b00-9360-22353fa3503f
               display_text: Custom Disk
                  disk_size: 0
                       tags: NULL
                recreatable: 0
          use_local_storage: 0
                unique_name: Cloud.Com-Custom
                 customized: 1
                    removed: NULL
                    created: 2023-12-26 11:01:13
                   sort_key: 0
           display_offering: 1
            customized_iops: NULL
                   min_iops: NULL
                   max_iops: NULL
            bytes_read_rate: NULL
        bytes_read_rate_max: NULL
 bytes_read_rate_max_length: NULL
           bytes_write_rate: NULL
       bytes_write_rate_max: NULL
bytes_write_rate_max_length: NULL
             iops_read_rate: NULL
         iops_read_rate_max: NULL
  iops_read_rate_max_length: NULL
            iops_write_rate: NULL
        iops_write_rate_max: NULL
 iops_write_rate_max_length: NULL
                      state: Active
              hv_ss_reserve: NULL
                 cache_mode: NULL
          provisioning_type: thin
       disk_size_strictness: 0
               compute_only: 0
                    encrypt: 0

There is no issue observed if change offeringfor volume is performed
https://cloudstack.apache.org/api/apidocs-4.18/apis/changeOfferingForVolume.html

as far as I know, size is just a property of disk offering.
disk offering has other properties, for instance, storage type, QoS, service offering, etc.
I think the disk offering id should not be changed to the id of customized disk offering.
@kiranchavala do you know if there is any issues caused by it ?
cc @kiranchavala @DaanHoogland @sureshanaparti
what's your opinion ?

as far as I know, size is just a property of disk offering. disk offering has other properties, for instance, storage type, QoS, service offering, etc. I think the disk offering id should not be changed to the id of customized disk offering. @kiranchavala do you know if there is any issues caused by it ?

If changing disk size is allowed, this also must have been a property of the diskoffering. If it is not allowed in the offering and it succeeds anyway, i think this is a bug. Disks can also be changed by changing the offering, but I am not sure what the effects of that are. I agree that offering should not implicitly change on resize, only explicitly, if the user asks so.

as far as I know, size is just a property of disk offering. disk offering has other properties, for instance, storage type, QoS, service offering, etc. I think the disk offering id should not be changed to the id of customized disk offering. @kiranchavala do you know if there is any issues caused by it ?

If changing disk size is allowed, this also must have been a property of the diskoffering. If it is not allowed in the offering and it succeeds anyway, i think this is a bug.

but it is not mentioned in @kiranchavala 's description

Disks can also be changed by changing the offering, but I am not sure what the effects of that are. I agree that offering should not implicitly change on resize, only explicitly, if the user asks so.

yes @DaanHoogland
I think this is not a bug.
since resizeVolume API supports diskofferingid parameter, it could be a UI improvement to specify disk offering when resize a volume.

the disk offering selection was present before.
it has been removed in #5008
@harikrishna-patnala do you remember why it is removed ? thanks

@weizhouapache Agree with you this is not a bug, probably we only need to update the document what Kiran is pointing out !!!
Regarding the removal of selection of diskoffering on resize form is to make only single point to change the diskoffering using changeOfferingForVolume. There is an action icon for changing the offering.

@weizhouapache Agree with you this is not a bug, probably we only need to update the document what Kiran is pointing out !!!
Regarding the removal of selection of diskoffering on resize form, it is to make only single point to change the diskoffering using changeOfferingForVolume. There is an action icon for changing the offering.

cool, thanks a lot @harikrishna-patnala
@kiranchavala @DaanHoogland
let's close this if there is no objections ?

closing
@kiranchavala
as Hari mentioned, please use changeOfferingForVolume to change the disk  offering of volume


Make docker run interactive

At the moment dgoss fails to keep running images that require interactive mode.
INFO: Starting docker container
docker run -d -v /tmp/tmp.o2kbIGZivm:/goss example.org:4567/my/project/base-image:1.0.20180317
INFO: Container ID: 1615c39b
INFO: Sleeping for 0.2
INFO: Running Tests
Error response from daemon: Container 1615c39be6e5ba62e2a732f6edb99ad09011729d96cd64c09368457e305eb7e1 is not running
INFO: Deleting container

The reason being is that container starts successfully and then stops imidietly. This merge request fixes the issue.
INFO: Starting docker container
INFO: Container ID: 6ed49ec7
INFO: Sleeping for 0.2
INFO: Running Tests
Package: msodbcsql: installed: matches expectation: [true]
Package: msodbcsql: version: matches expectation: [["<IP_ADDRESS>-1"]]

Total Duration: 0.010s
Count: 2, Failed: 0, Skipped: 0
INFO: Deleting container

Does dgoss run -i ... not work?

Yes, it does! Thanks for responding so quickly. I missed that ${@:2} passes all the parameters. Sorry. This PR can be closed.


Add prefer object spread instead of object assign.(closes #30)

Solution proposal to close #30  - "Prefer object spread instead of Object.assign() .
Added the plugin with the desired rule for the MOXY eslint configuration.

After everything is done, please squash your commits into a single one and follow https://conventionalcommits.org/ guidelines.
Additionally, this is a breaking change because code that doesn't use spread but should will now not pass linting. Therefore, be sure to include BREAKING CHANGE: <reason> in the body of the commit.

All good. Could you please squash all the commits into a single one?

Be sure that include Closes issue #30.

👍


ImportError: cannot import name 'LoginView'

Getting this error when running any python manage.py command.
Using version 4.0.0 with Python (3.4.7) and Django (1.9.13).
Stack trace:
  File "manage.py", line 6, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.4/site-packages/django/core/management/__init__.py", line 327, in execute
    django.setup()
  File "/usr/local/lib/python3.4/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/local/lib/python3.4/site-packages/django/apps/registry.py", line 115, in populate
    app_config.ready()
  File "/usr/local/lib/python3.4/site-packages/axes/apps.py", line 8, in ready
    from django.contrib.auth.views import LoginView
ImportError: cannot import name 'LoginView'```

Thanks!

Hi! Can you try the most recent version please and let me know if you're still seeing this error?

Upgraded to 4.4.0. Still getting the error.

Which django version are you using?

The lowest supported django version is 1.11


[BUG] CMC loss in the master

Describe the bug
Hi, it seems in trainer, the CMC loss is not working.
# loss += self.compute_cmc_loss(
#     clip_emb_reshape, clip_emb_mask, clip_emb_lens,
#     sent_emb_reshape, sent_emb_mask, sent_emb_lens)

Hi,
it's turned off during validation for performance reasons. During training it's active.
If you want to make sure it's working, you could change one of the configurations and set     loss_cycle_cons: 0   near the top of the file, then check how the performance changes.

Oh, that's right. I didn't notice it's in the eval part. Thanks!

Since the latest update CMC will work correctly both on training and validation.


Workspaces -- Phase 2

NOTE: No changes have yet been made to the public API of the package.
This introduces the JSON format support for the stable workspace API. This is not intended to be a feature complete PR but rather represents the infrastructure necessary for pending feature additions via future PRs.
Development Plan:
Phase 1 (#13598) - Public API (not exposed until phase 3) and format agnostic reading/writing support
Phase 2 (this PR)- JSON format reader/writer for existing format (includes change tracking support)
Phase 3 - Integration into @schematics/angular package and exposure of public API
Phase 4 - Query API additions (e.g., finding specific project target names/builders)

Sorry for the triple approve. Github was 500'ing.


Missing equal sign in Dockerfile

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

the equal sign is optional, see https://docs.docker.com/engine/reference/builder/#env

@bradrydzewski Thank you.
All other ENV-s are with equal sign.


Guest shares host by default

This proposal would change the default behavior of the Loader constructor such that it creates a useful guest Loader by default, by sharing the host’s global object, static memos, and hooks. Loader constructor options override these behaviors selectively.
The motivation for this case is to provide a direct answer to @guybedford and @lucacasonato who proposed that one of the requirements for WASM is the ability to defer execution of a WASM module such that it be linked in a new module graph, possibly in multiple module graphs. This aligns well with the needs for Hot Module Replacement.
I propose as a straw-man that this framing of the Loader API would make possible a very clear way to express the designed intent:
import static 'x.wasm';
for (let i = 0; i < poolSize; i++) {
  new Loader().import('x.wasm');
}

The import static declaration would defer execution but populate the static module record memo of the host’s realm loader with x.wasm and its transitive dependencies. The guest compartments would inherit these static module records by default.
Developing beyond this idea, host virtualization hooks on the loader can interpose to provide alternate linkage or fall through to the host. In this example, the new loader would inherit the instance of 'y.wasm', which we presume 'x.wasm' imports. Consequently, the new loader has its own instance of x.wasm and an instance of y.wasm shared with the host.
new Loader({
  loadHook(fullSpecifier) {
    if (fullSpecifier === 'y.wasm') {
      return { instance: fullSpecifier };
    } else {
      return { record: fullSpecifier };
    }
  },
}).import('x.wasm');

I think this change needs more care. We need to preserve a way for a Loader to borrow the host load hook and not borrow the static module record cache for Hot Module Replacement or other kinds of reloading, like one might see with a test watcher.

We need to figure out the identity issue for modules blocks as well. Here is a long thread on the topic: https://github.com/tc39/proposal-js-module-blocks/issues/58

This change is not ready to land because it fails to adequately account for the case where a guest compartment needs a fresh static record memo (so it can reload) and also reuse the host’s loader’s load hooks. (I’ve made the mistake of conflating the effects of loadHook and memo sharing.) The options need to be orthogonal and the design directions come in two flavors.
A: Share by default (which I suspect to be more common)
B: Detach by default (which is generally safer)

Adopt host globals or create new globals

A

adopt: new Loader()
create: new Loader({ globals: {} })

B

adopt: new Loader({ shareGlobal: true })
create: new Loader()
create: new Loader({ globals: {} })

Adopt, override, or omit resolveHook

A:

adopt: new Loader()
override: new Loader({ resolveHook })
omit: new Loader({ resolveHook: null })

B

adopt: new Loader({ shareResolveHook: true })
override: new Loader({ resolveHook })
omit: new Loader()

Adopt, override, or omit loadHook

A

adopt: new Loader()
override: new Loader({ loadHook })
omit: new Loader({ loadHook: null })

B

adopt: `new Loader({ shareLoadHook: true })
override: new Loader({ loadHook })
omit: new Loader()

Adopt or detach static module record memo

A

adopt: new Loader()
override: new Loader({ detach: true })

B

adopt: new Loader({ shareRecords: true })
override: new Loader()

I think I would like to convince this group that option B is generally better, even though detached global by default will be surprising the to majority of users. On the other hand, I suspect that attaching the static module record by default will also have surprising negative effects. We could pursue a hybrid, but I know that my mind at least has a hobgoblin.
Please let me know what you think and I’ll update this change to reflect the general favor of the champion group.

It occurs to me, we could also reify Loader.loadHook and Loader.resolveHook so they can be passed from host to guest. This would mean revealing the intrinsic host-defined versions of these functions and allowing guest code to call them directly, which I suspect is undesirable. I can’t contemplate passing the memos in this way though.

It occurs to me, we could also reify Loader.loadHook and Loader.resolveHook so they can be passed from host to guest.

This is basically how Node's experimental loader API works. In that it basically passes defaultLoad/defaultResolve to the load/resolve hooks so that you can call them to delegate to host behaviour.
This API could do something similar i.e.:
interface LoaderOptions {
    loadHook: (
        specifier: string,
        hostLoadHook: (specifier: string) => Promise<ModuleDescriptor>
    ) => Promise<ModuleDescriptor>
}

const loader = new Loader({
    async loadHook(specifier, hostLoadHook) {
        // Delegate to host when needed
        if (specifier.startsWith("node:")) {
            return await hostLoadHook(specifier);
        }
        // Load it myself
    },
});

I’ve rebased this so it can land ahead of #48, so the inevitable naming bikeshed can commence at a later date.

What's the behavior of the following expressions when they share a global?
a: globalThis === new Compartment().globalThis
b: globalThis.eval === new Compartment().globalThis.eval
c: new Compartment({ loadHook: () => { throw new Error() } }).eval('import("" + Math.random())')

What's the behavior of the following expressions when they share a global?
a: globalThis === new Compartment().globalThis

true

b: globalThis.eval === new Compartment().globalThis.eval

true

c: new Compartment({ loadHook: () => { throw new Error() } }).eval('import("" + Math.random())')

[object Promise] (eventually rejected with Error(), possibly "Compartment could not load ${random}" with cause: new Error())

What's the behavior of the following expressions when they share a global?
a: globalThis === new Compartment().globalThis

true

b: globalThis.eval === new Compartment().globalThis.eval

true

c: new Compartment({ loadHook: () => { throw new Error() } }).eval('import("" + Math.random())')

[object Promise] (eventually rejected with Error(), possibly "Compartment could not load ${random}" with cause: new Error())

Then this looks strange to me. If the inner eval and the outer eval is the same function, how can you know the dynamic import performed should be in the child compartment or the incubator compartment?

Then this looks strange to me. If the inner eval and the outer eval is the same function, how can you know the dynamic import performed should be in the child compartment or the incubator compartment?

My understanding is that the global environment record (for evaluated scripts) and module environment records (for evaluated modules) will need to keep a marker to the intrinsic eval and separately the intrinsic Loader. The intrinsic eval is used for distinguishing indirect from direct eval, and the loader is used for import syntax regardless of the intrinsic evaluator. We will of course have to take care to make this true in our proposed spec text.

Then this looks strange to me. If the inner eval and the outer eval is the same function, how can you know the dynamic import performed should be in the child compartment or the incubator compartment?

My understanding is that the global environment record (for evaluated scripts) and module environment records (for evaluated modules) will need to keep a marker to the intrinsic eval and separately the intrinsic Loader. The intrinsic eval is used for distinguishing indirect from direct eval, and the loader is used for import syntax regardless of the intrinsic evaluator. We will of course have to take care to make this true in our proposed spec text.

Sorry I still do not understand 😂 because you can pass the eval around, then how do you figure out if it should be run in the child compartment or the incubator compartment?
For example, I have an intrinsic eval from the Realm A, and in the Realm A there are compartments Root, A, and B. As you said, the eval keeps the same identity in the compartment Root, A, and B.
Then what will happen if I pass the eval to the Realm B and execute eval("import('path')")? Which loader will it trigger?

Then this looks strange to me. If the inner eval and the outer eval is the same function, how can you know the dynamic import performed should be in the child compartment or the incubator compartment?

My understanding is that the global environment record (for evaluated scripts) and module environment records (for evaluated modules) will need to keep a marker to the intrinsic eval and separately the intrinsic Loader. The intrinsic eval is used for distinguishing indirect from direct eval, and the loader is used for import syntax regardless of the intrinsic evaluator. We will of course have to take care to make this true in our proposed spec text.

Sorry I still do not understand 😂 because you can pass the eval around, then how do you figure out if it should be run in the child compartment or the incubator compartment?
For example, I have an intrinsic eval from the Realm A, and in the Realm A there are compartments Root, A, and B. As you said, the eval keeps the same identity in the compartment Root, A, and B.
Then what will happen if I pass the eval to the Realm B and execute eval("import('path')")? Which loader will it trigger?

And now I understand the nature of the question! And I find that I do not have an answer, short of abandoning the notion of Compartments with shared globals. I hope the brain trust will join me in pondering a solution.

Are we talking about direct or indirect eval? Indirect eval should unquestionably be associated with that eval function's context of origin.
If we're talking direct eval, I see only two issues:

Does code from compartment A executing an eval(src) expression with an eval function from compartment B recognize it as an original eval function, such that it interprets the expression as a direct eval.

If no, then that expression is interpreted as an indirect eval function. To compartment A, this is just a function call to a function defined elsewhere. That eval function cares only about its compartment of origin.
If yes, then once we've decided to interpret it as a direct eval expression, the eval function in question no longer has any further influence whatsoever on the execution beyond this decision. The direct eval is a special code in the scope of the code in which it appears, just as an if statement is a special form in the scope of the code in which it appears.

And now I understand the nature of the question! And I find that I do not have an answer, short of abandoning the notion of Compartments with shared globals. I hope the brain trust will join me in pondering a solution.

Is the idea that eval(...) always uses the same loader the evaluating code? If so then wouldn't we just add a similar notion to current realm but for the current loader.
i.e. More specifically we would have an operations like GetFunctionRealm except called GetFunctionLoader. eval would not have a [[Loader]] slot so effectively "step 4" would be executed delegating to essentially the caller.

I'm jumping into the middle without having absorbed enough context first. I may be missing or misunderstanding the real question.

It is perhaps not a fundamental hole in the notion of shared-globals, but at this moment I see no way that eval('import("x")') or compartment.evaluate('import("x")') would not fall through the floor to the compartment that first created the global environment. This of course poses no problem at all for module code, but would be at least a mild aberration for eval.

As @erights points out, direct and indirect eval require separate consideration.
For direct eval, a sensible answer may be possible because the script is evaluated in the module, which in turn has the correct loader associated with it.
For indirect eval, my previous answer stands. The only answer I can imagine is that the dynamic import would invoke the loader associated with the compartment that first created the global environment.

And now I understand the nature of the question! And I find that I do not have an answer, short of abandoning the notion of Compartments with shared globals. I hope the brain trust will join me in pondering a solution.

Is the idea that eval(...) always uses the same loader the evaluating code? If so then wouldn't we just add a similar notion to current realm but for the current loader.
i.e. More specifically we would have an operations like GetFunctionRealm except called GetFunctionLoader. eval would not have a [[Loader]] slot so effectively "step 4" would be executed delegating to essentially the caller.

What you propose is clearly necessary. The crux is that the eval object’s [[Loader]] is presumably set to the loader that created it, not one of the loaders that shares it.

For direct eval, good. Is that settled? Are there remaining open questions? Well, one: which eval functions count as an original eval function when deciding whether an eval(src) expression should be treated as a direct eval expression. But once that is decided, if it is a direct eval, are there any further open questions?

For indirect eval, my previous answer stands. The only answer I can imagine is that the dynamic import would invoke the loader associated with the compartment that first created the global environment.

Where does the eval function in question come from? What created it?

In any case, for indirect eval, it must not matter where it is called from. All that matters is where it was created.

As a further clarification, a direct eval does not call the eval function bound to the eval variable. That eval function's identity is used to make this decision. Afterwards, that eval function is irrelevant and has no influence.

I think we’re in agreement about what the behavior must be, assuming that we make it possible to create a guest compartment that shares its global environment its host (the topic of this change). The question is whether that is acceptable.
That is to say, assuming const guest = new host.globalThis.Compartment({ ... }) such that the guest compartment shares the host compartment's global environment, guest.globalThis === host.globalThis, guest.globalThis.eval === host.globalThis.eval, and the eval function’s [[Compartment]] slot is the host. With this arrangement, direct eval effects an import in the guest compartment and indirect eval imports in the host compartment.

Consider the expression eval('import("x")'),

If that expression exists within a program we evaluate that program with guest.evaluate(program),

Look up eval in the lexical scope of the program. We find guest.globalThis.eval, which is originally host.globalThis.eval. Look up the intrinsic eval of the execution environment, which is host.globalThis.eval. These objects are identical, so we proceed to interpret the expression as a direct eval. Look up the intrinsic loader of the execution environment, which is guest, so we import x in guest.

If that expression exists within a module 'y' and guest.import('y'). Same effect as previous. We import x in guest.

Consider the expression (0, eval)('import("x")),

If that expression exists within a program we evaluate that program with guest.evaluate(program),

The LHS is not the identifier eval, so this is indirect eval. We look up eval in lexical scope, find host.globalThis.eval, look up its [[Compartment]], find that it’s host, and so we import x of host.

If that expression exists within a module 'y' and guest.import('y'). Same effect as previous. We import x in host.

My tentative opinion is that this is unfortunate but acceptable. The only known alternative is to not provide a shared-global mode. I do not speak for every champion, but I for one would be willing to pitch either option.

Does code from compartment A executing an eval(src) expression with an eval function from compartment B recognize it as an original eval function, such that it interprets the expression as a direct eval.

For Realm, the answer is No (it is an indirect eval when eval is from another Realm). So I think it should be the same for compartments.

In any case, for indirect eval, it must not matter where it is called from. All that matters is where it was created.

Yes, it should be bounded to where it was created, but the problem is we want to share globals, which means the child compartment will have the same eval as the parent one.

The only known alternative is to not provide a shared-global mode.

One of the possible solution is to give up the rootComp.globalThis === childComp.globalThis constraint.
Let's make the child compartment an exotic object, and fall through all queries besides eval Function Compartment to the parent compartment. In this way, each compartment will have its own evaluators and still "share" the global in some way.

This change is not ready to land because it fails to adequately account for the case where a guest compartment needs a fresh static record memo (so it can reload) and also reuse the host’s loader’s load hooks. (I’ve made the mistake of conflating the effects of loadHook and memo sharing.) The options need to be orthogonal and the design directions come in two flavors.
A: Share by default (which I suspect to be more common) B: Detach by default (which is generally safer)

Adopt host globals or create new globals

A1

adopt: new Compartment()
create: new Compartment({ globals: {} })

A2

adopt: new Compartment()
create: new Compartment({ detachGlobals: true })
create: new Compartment({ detachGlobals: true, globals: {x, y z} })

B

adopt: new Compartment({ shareGlobal: true })
create: new Compartment()
create: new Compartment({ globals: {} })
create: new Compartment({ globals: {x, y z} })

Adopt, override, or omit resolveHook

A:

adopt: new Compartment()
override: new Compartment({ resolveHook })
omit: new Compartment({ resolveHook: null })

B

adopt: new Compartment({ shareResolveHook: true })
override: new Compartment({ resolveHook })
omit: new Compartment()

Adopt, override, or omit loadHook

A

adopt: new Compartment()
override: new Compartment({ loadHook })
omit: new Compartment({ loadHook: null })

B

adopt: `new Compartment({ shareLoadHook: true })
override: new Compartment({ loadHook })
omit: new Compartment()

Adopt or detach static module record memo

A

adopt: new Compartment()
override: new Compartment({ detach: true })

B

adopt: new Compartment({ shareRecords: true })
override: new Compartment()

I think I would like to convince this group that option B is generally better, even though detached global by default will be surprising the to majority of users. On the other hand, I suspect that attaching the static module record by default will also have surprising negative effects. We could pursue a hybrid, but I know that my mind at least has a hobgoblin.
Please let me know what you think and I’ll update this change to reflect the general favor of the champion group.

I’ve moved this question to a topic #65


Remove bin logging

The current configuration of bin logging makes the in container DB very
slow.  If users want bin logging or more HA configuration then they
really should rely on an external database that is properly tuned.

https://github.com/rancher/rancher/issues/4722